AudioCodes Mediant 2600 User Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Controller
  5. Mediant 2600
  6. User manual

AudioCodes Mediant 2600 User Manual

Enterprise session border, e-sbc, family of session border controllers
Hide thumbs Also See for Mediant 2600:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
Table of Contents

Advertisement

Quick Links

Download this manual
User's Manual
AudioCodes Mediant™ Family of Session Border Controllers (SBC)
Mediant 2600
Enterprise Session Border (E-SBC)
Version 6.8

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 2600

Summary of Contents for AudioCodes Mediant 2600

  • Page 1 User's Manual AudioCodes Mediant™ Family of Session Border Controllers (SBC) Mediant 2600 Enterprise Session Border (E-SBC) Version 6.8...

  • Page 3: Table Of Contents

    Understanding Configuration Modes ............... 61 7.1.2 Using CLI Shortcuts ....................62 7.1.3 Common CLI Commands ..................63 7.1.4 Configuring Tables in CLI ..................64 7.1.5 Understanding CLI Error Messages ................ 65 Enabling CLI ......................65 Version 6.8 Mediant 2600 E-SBC...
  • Page 4 Mediant 2600 E-SBC 7.2.1 Enabling Telnet for CLI .................... 65 7.2.2 Enabling SSH with RSA Public Key for CLI ............. 66 Establishing a CLI Session ..................68 Configuring Maximum Telnet/SSH Sessions ............68 Viewing and Terminating Current CLI Sessions ............ 69 Configuring Displayed Output Lines in CLI Terminal Window .......
  • Page 5 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......164 14.2.3 V.34 Fax Support ....................165 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........165 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ........... 165 14.2.4 V.152 Support ......................166 14.3 Configuring RTP/RTCP Settings ................168 Version 6.8 Mediant 2600 E-SBC...
  • Page 6 Mediant 2600 E-SBC 14.3.1 Configuring the Dynamic Jitter Buffer ..............168 14.3.2 Dual-Tone Multi-Frequency Signaling ..............169 14.3.2.1 Configuring DTMF Transport Types ............169 14.3.2.2 Configuring RFC 2833 Payload ............171 14.3.3 Configuring RTP Base UDP Port ................171 14.3.4 Automatic Gain Control (AGC) ................172 14.4 Configuring Various Codec Attributes ..............
  • Page 7 20.4.5 Restricting Coders ....................331 20.4.6 Coder Transcoding ....................331 20.4.7 Prioritizing Coder List in SDP Offer ...............333 20.4.8 SRTP-RTP and SRTP-SRTP Transcoding ............333 20.4.9 Multiple RTP Media Streams per Call Session .............334 20.4.10 Interworking DTMF Methods .................334 Version 6.8 Mediant 2600 E-SBC...
  • Page 8 Mediant 2600 E-SBC 20.5 Fax Negotiation and Transcoding ................ 335 20.6 Limiting SBC Call Duration ................... 335 20.7 SBC Authentication ....................336 20.7.1 SIP Authentication Server Functionality ..............336 20.7.2 User Authentication based on RADIUS ..............337 20.8 Interworking SIP Signaling ................... 337 20.8.1 Interworking SIP 3xx Redirect Responses ............337...
  • Page 9 28.2 Resetting the Redundant Unit ................426 29 Disconnecting Active Calls ................427 30 Software Upgrade .................... 429 30.1 Loading Auxiliary Files ..................429 30.1.1 Call Progress Tones File ..................430 30.1.2 Prerecorded Tones File ..................433 Version 6.8 Mediant 2600 E-SBC...
  • Page 10 31.1.3 Provisioning from TFTP Server using DHCP Option 66 ........453 31.1.4 HTTP-based Provisioning ..................453 31.1.5 FTP-based Provisioning ..................454 31.1.6 Provisioning using AudioCodes EMS ..............454 31.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 455 31.2.1 Files Provisioned by Automatic Update ..............455 31.2.2 File Location for Automatic Update ...............455...
  • Page 11 39 Syslog and Debug Recordings ..............501 39.1 Syslog Message Format ..................501 39.1.1 Event Representation in Syslog Messages ............502 39.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......504 39.1.3 SNMP Alarms in Syslog Messages ...............504 39.2 Enabling Syslog ....................505 39.3 Configuring Web Operations to Report to Syslog ..........
  • Page 12 Mediant 2600 E-SBC 42 Dialing Plan Notation for Routing and Manipulation ........531 43 Configuration Parameters Reference ............533 43.1 Management Parameters ..................533 43.1.1 General Parameters ....................533 43.1.2 Web Parameters ....................533 43.1.3 Telnet Parameters ....................536 43.1.4 ini File Parameters ....................537 43.1.5 SNMP Parameters ....................537...
  • Page 13 User's Manual Contents 44 SBC Channel Capacity ..................639 44.1 Signaling-Media Sessions & User Registrations ..........639 44.2 Channel Capacity and Capabilities ..............641 45 Technical Specifications ................643 Version 6.8 Mediant 2600 E-SBC...
  • Page 14 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...
  • Page 15 Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our Web site at https://www.audiocodes.com/services-support/maintenance-and-support.
  • Page 16 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 17 Inserted in Configuration File Name; Viewing Call Routing Status (removed); Creating Core Dump and Debug Files upon Device Crash (reset)  New sections: Viewing Proxy Set Status  Updated parameters: NATTranslation_SourceStartPort; NATTranslation_SourceEndPort; NATTranslation_TargetStartPort; NATTranslation_TargetEndPort; IpProfile_SBCUseSilenceSupp; DisableSNMP; Version 6.8 Mediant 2600 E-SBC...
  • Page 18 IsCiscoSCEMode; EnableBusyOut; EnableSilenceCompression (removed); UseDisplayNameAsSourceNumber  New parameters: IpProfile_SBCAdaptRFC2833BWToVoiceCoderBW; ActiveAlarmTableMaxSize; NoAlarmForDisabledPort; SBCRemoveSIPSFromNonSecuredTransport Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form site https://online.audiocodes.com/documentation-feedback.

  • Page 19: Overview

    User's Manual 1. Overview Overview AudioCodes' Mediant 2600 E-SBC (hereafter referred to as device) is a member of AudioCodes family of Enterprise Session Border Controllers (E-SBC), enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks. The device is a fully featured enterprise-class SBC provides a secured voice network deployment based on a Back-to-Back User Agent (B2BUA) implementation.
  • Page 20 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 21: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 23: Introduction

    User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 6.8 Mediant 2600 E-SBC...
  • Page 24 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 25: Default Oamp Ip Address

    OAMP + Media + Control IP Address 192.168.0.2 - this IP address is assigned to the first Ethernet Port Group (top-left ports 1 & 2) Prefix Length 255.255.255.0 (24) Default Gateway 192.168.0.1 Underlying Device Interface Name "O+M+C" Version 6.8 Mediant 2600 E-SBC...
  • Page 26 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 27: Configuring Voip Lan Interface For Oamp

    Access the Web interface: On your computer, start a Web browser and in the URL address field, enter the default IP address of the device; the Web interface's Web Login screen appears: Figure 4-1: Web Login Screen Version 6.8 Mediant 2600 E-SBC...
  • Page 28 Mediant 2600 E-SBC In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table) and then configure the device's physical Ethernet port-pair (group) that you want to later assign to the OAMP interface.

  • Page 29: Cli

    Access the Interface table: (config-voip)# interface network-if 0 Configure the IP address: (network-if-0)# ip-address <IP address> Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Configure the Default Gateway address: (network-if-0)# gateway <IP address> Version 6.8 Mediant 2600 E-SBC...
  • Page 30 Mediant 2600 E-SBC Apply your settings: (network-if-0)# activate Exit the Interface table: (network-if-0)# exit Exit the VoIP configuration mode: (config-voip)# exit Reset the device with a flash burn: # reload now Cable the device to your network. You can now access the device's management interface using this new OAMP IP address.

  • Page 31: Management Tools

    Part II Management Tools...

  • Page 33: Introduction

    Web, CLI, and ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 533. Version 6.8 Mediant 2600 E-SBC...
  • Page 34 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 35: Web-Based Management

    Microsoft™ Internet Explorer™ (Version 6.0 and later) • ® Mozilla Firefox (Versions 5 through 9.0)  Recommended screen resolutions: 1024 x 768 pixels, or 1280 x 1024 pixels Note: Your Web browser must be JavaScript-enabled to access the Web interface. Version 6.8 Mediant 2600 E-SBC...

  • Page 36: Accessing The Web Interface

    Mediant 2600 E-SBC 6.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see ''Computer Requirements'' on page 35). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 37: Areas Of The Gui

    ''Navigation Tree'' on page 39. Work pane, displaying the configuration page of the selected menu in the Navigation tree. This is where configuration is done. For more information, see ''Working with Configuration Pages'' on page 41. Version 6.8 Mediant 2600 E-SBC...

  • Page 38: Toolbar Description

    Mediant 2600 E-SBC 6.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Table 6-2: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see ''Saving Configuration'' on page 424).

  • Page 39: Navigation Tree

    The expanded view displays all the menus pertaining to the selected configuration tab; the reduced view displays only commonly used menus.  To display a reduced menu tree, select the Basic option (default). Version 6.8 Mediant 2600 E-SBC...

  • Page 40: Showing / Hiding The Navigation Pane

    Mediant 2600 E-SBC  To display all menus and submenus, select the Advanced option. Figure 6-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 6.1.5.2 Showing / Hiding the Navigation Pane You can hide the Navigation pane to provide more space for elements displayed in the Work pane.

  • Page 41: Working With Configuration

     Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. Version 6.8 Mediant 2600 E-SBC...
  • Page 42 Mediant 2600 E-SBC The figure below shows an example of a page displaying basic parameters only. If you click the Advanced Parameter List button (shown below), the page will also display the advanced parameters. Figure 6-6: Toggling between Basic and Advanced View Notes: •...

  • Page 43: Modifying And Saving Parameters

    Thus, to ensure parameter changes (whether on-the-fly or not) are retained, save ('burn') them to the device's non-volatile memory, i.e., flash (see ''Saving Configuration'' on page 424). Version 6.8 Mediant 2600 E-SBC...

  • Page 44: Working With Tables

    Mediant 2600 E-SBC If you enter an invalid parameter value (e.g., not in the range of permitted values) and then click Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts to its previous value and is highlighted in red, as shown in the...

  • Page 45: Searching For Configuration Parameters

    The search key can include the full parameter name (e.g., "EnableSyslog") or a substring of it (e.g., "sys"). If you search for a substring, all parameters containing the specified substring in their names are listed in the search result. Version 6.8 Mediant 2600 E-SBC...
  • Page 46 Mediant 2600 E-SBC  To search for a parameter: On the Navigation bar, click the Search tab; the Search engine appears in the Navigation pane. In the field alongside the Search button, enter the parameter name or a substring of the name for which you want to search.

  • Page 47: Creating A Login Welcome Message

    WelcomeMessage 2 = "********* This is a Welcome message **"; WelcomeMessage 3 = "*********************************"; [\WelcomeMessage] Each index row represents a line of text in the Welcome message box. Up to 20 lines (or rows) of text can be defined. Version 6.8 Mediant 2600 E-SBC...

  • Page 48: Getting Help

    Mediant 2600 E-SBC 6.1.9 Getting Help The Web interface provides you with context-sensitive Online Help. The Online Help provides brief descriptions of parameters pertaining to the currently opened page.  To view the Help topic of a currently opened page: On the toolbar, click the Help button;...

  • Page 49: Viewing The Home Page

    "SHUTTING DOWN": device is currently shutting down To perform these operations, see ''Basic Maintenance'' on page 421.  High Availability: Status of the device's HA mode (see HA Status on the Home Page on page 405) Version 6.8 Mediant 2600 E-SBC...
  • Page 50 Mediant 2600 E-SBC The table below describes the areas of the Home page. Table 6-7: Home Page Description Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green: No alarms ...

  • Page 51: Configuring Web User Accounts

    Administrators. It can delete all users except the last Security Administrator. Administrator Read / write privileges for all pages, except security- related pages (read-only). Monitor No access to security-related and file-loading pages; read-only access to all other pages. Version 6.8 Mediant 2600 E-SBC...
  • Page 52 Mediant 2600 E-SBC Numeric User Level Representation in Privileges RADIUS No Access No access to any page. Note: This access level is not applicable when using advanced Web user account configuration in the Web Users table. By default, the device is pre-configured with the following two Web user accounts:...

  • Page 53: Basic User Accounts Configuration

    (as shown below). If you are logged in with the second user account, only the details of this user account are displayed. Figure 6-16: Web User Accounts Page (for Users with 'Security Administrator' Privileges) Version 6.8 Mediant 2600 E-SBC...

  • Page 54: Advanced User Accounts Configuration

    Mediant 2600 E-SBC To change the username of an account: In the 'User Name' field, enter the new user name. Click Change User Name; if you are currently logged in to the Web interface with this account, the 'Web Login' dialog box appears.
  • Page 55 Defines the Web user's username. CLI: user The valid value is a string of up to 40 alphanumeric characters, including the period ".", underscore "_", and hyphen "-" signs. Web: Password Defines the Web user's password. Version 6.8 Mediant 2600 E-SBC...
  • Page 56 Mediant 2600 E-SBC Parameter Description CLI: password The valid value is a string of 8 to 40 ASCII characters, which must adhere to the following guidelines:  Include at least eight characters.  Include at least two letters that are upper case (e.g., A).
  • Page 57 If only one Master user exists, it can be deleted only by itself.  Master users can add, edit, and delete Security Administrators (but cannot delete the last Security Administrator).  Only Security Administrator and Master users can add, edit, and delete Administrator and Monitor users. Version 6.8 Mediant 2600 E-SBC...

  • Page 58: Displaying Login Information Upon Login

    Mediant 2600 E-SBC Displaying Login Information upon Login The device can display login information immediately upon Web login.  To enable display of user login information upon a successful login: Open the Web Security Settings page (Configuration tab > System menu >...

  • Page 59: Web Login Authentication Using Smart Cards

    This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative.  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader.

  • Page 60: Configuring Web And Telnet Access List

    Mediant 2600 E-SBC Configuring Web and Telnet Access List The Web & Telnet Access List page is used to define IP addresses (up to ten) that are permitted to access the device's Web, Telnet, and SSH interfaces. Access from an undefined IP address is denied.

  • Page 61: Cli-Based Management

    This mode allows you to view various information (using the show commands) and activate various debugging capabilities. Welcome to AudioCodes CLI Username: Admin Password: >...

  • Page 62: Using Cli Shortcuts

    Mediant 2600 E-SBC The Enable mode groups the configuration commands under the following command sets: • config-system: Provides the general and system related configuration commands, for example, Syslog configuration. This set is accessed by typing the following command: # configure system (config-system)# •...

  • Page 63: Common Cli Commands

    Displays the available command list of the current command-set. list | <filter> Applied to a command output. The filter should be typed after the command with a pipe mark (|). Supported filters:  include <word> – filter (print) lines which contain <word> Version 6.8 Mediant 2600 E-SBC...

  • Page 64: Configuring Tables In Cli

    Mediant 2600 E-SBC Command Description  exclude <word> – filter lines which does not contain <word>  grep <options> - filter lines according to grep common Unix utility options  egrep <options> - filter lines according to egrep common Unix utility options ...

  • Page 65: Understanding Cli Error Messages

    Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 536. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 2600 E-SBC...

  • Page 66: Enabling Ssh With Rsa Public Key For Cli

    Mediant 2600 E-SBC 7.2.2 Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text. To overcome this, Secure SHell (SSH) is used, which is the de-facto standard for secure CLI.
  • Page 67 'Admin Key' field. Click Submit. Connect to the device with SSH, using the following command: ssh -i admin.key xx.xx.xx.xx where xx.xx.xx.xx is the device's IP address. RSA-key negotiation occurs automatically and no password is required. Version 6.8 Mediant 2600 E-SBC...

  • Page 68: Establishing A Cli Session

    Mediant 2600 E-SBC Establishing a CLI Session The device's CLI can be accessed using any of the following methods:  RS-232: The device can be accessed through its RS-232 serial port, by connecting a VT100 terminal to it or using a terminal emulation program (e.g., HyperTerminal) with a PC.

  • Page 69: Viewing And Terminating Current Cli Sessions

    # clear user <session ID> When this command is run, it ends the Telnet/SSH session (logs out the RS-232 session) and displays the CLI login prompt. Note: The session from which the command is run cannot be terminated. Version 6.8 Mediant 2600 E-SBC...

  • Page 70: Configuring Displayed Output Lines In Cli Terminal Window

    Mediant 2600 E-SBC Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be specified from 0 to 65,535, or determined by re-sizing the terminal window by mouse- dragging the window's border.

  • Page 71: Snmp-Based Management

    SNMP Manager. All supported MIB files are supplied to customers as part of the release. AudioCodes EMS is an advanced solution for standards-based management that covers all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of the device.
  • Page 72 Mediant 2600 E-SBC  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String). Configure SNMP community strings according to the table below. Click Submit, and then save ("burn") your settings to flash memory.

  • Page 73: Configuring Snmp Trap Destinations

    Management > SNMP > SNMP Trap Destinations). Figure 8-1: SNMP Trap Destinations Page Configure the SNMP trap manager parameters according to the table below. Select the check box corresponding to the SNMP Manager that you wish to enable. Click Submit. Version 6.8 Mediant 2600 E-SBC...
  • Page 74 Mediant 2600 E-SBC Note: Only row entries whose corresponding check boxes are selected are applied when clicking Submit; otherwise, settings revert to their defaults. Table 8-2: SNMP Trap Destinations Parameters Description Parameter Description Web: SNMP Manager Enables the SNMP Manager to receive traps and checks...

  • Page 75: Configuring Snmp Trusted Managers

    Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address. Define an IP address in dotted-decimal notation. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 2600 E-SBC...

  • Page 76: Configuring Snmp V3 Users

    Mediant 2600 E-SBC Configuring SNMP V3 Users The SNMP v3 Users table lets you configure up to 10 SNMP v3 users for authentication and privacy. The following procedure describes how to configure SNMP v3 users in the Web interface. You can also configure this using the table ini file parameter, SNMPUsers or CLI command, configure system >...
  • Page 77 Group The group with which the SNMP v3 user is associated. CLI: group  [0] Read-Only (default) [SNMPUsers_Group]  [1] Read-Write  [2] Trap Note: All groups can be used to send traps. Version 6.8 Mediant 2600 E-SBC...
  • Page 78 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 79: Ini File-Based Management

    The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME].  Format line: Specifies the columns of the table (by their string names) that are to be configured. Version 6.8 Mediant 2600 E-SBC...
  • Page 80 Mediant 2600 E-SBC • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed. • Columns must be separated by a comma ",".

  • Page 81: General Ini File Formatting Rules

    For loading the ini file to the device, see ''Loading an ini File to the Device'' on page 82. Note: To restore the device to default settings using the ini file, see ''Restoring Factory Defaults'' on page 467. Version 6.8 Mediant 2600 E-SBC...

  • Page 82: Loading An Ini File To The Device

    The file may be loaded to the device using HTTP. These protocols are not secure and are vulnerable to potential hackers. To overcome this security threat, the AudioCodes DConvert utility allows you to binary-encode (encrypt) the ini file before loading it to the device.

  • Page 83: Configuring Password Display In Ini File

    PC, the password is displayed obscured (i.e., $1$<obscured password>). INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any...
  • Page 84 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 85: General System Settings

    Part III General System Settings...

  • Page 87: Configuring Ssl/Tls Certificates

    Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 2600 E-SBC...
  • Page 88 Mediant 2600 E-SBC When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows:  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for...
  • Page 89 [5] TLSv1.0 and TLSv1.2 = TLS 1.2 and TLS 1.0 only.  [6] TLSv1.1 and TLSv1.2 = TLS 1.2 and TLS 1.1 only  [7] TLSv1.0 TLSv1.1 and TLSv1.2 = TLS 1.2, TLS 1.1 and TLS 1.0 only (excludes SSL 3.0). Version 6.8 Mediant 2600 E-SBC...
  • Page 90 Mediant 2600 E-SBC Parameter Description Web: Cipher Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher CLI: ciphers-server list format). [TLSContexts_Serve The default is AES:RC4. For valid values, visit the OpenSSL website at rCipherString] https://www.openssl.org/docs/man1.0.2/apps/ciphers.html. Web: Cipher Client Defines the supported cipher suite for TLS clients.

  • Page 91: Assigning Csr-Based Certificates To Tls Contexts

    Fill in the rest of the request fields according to your security provider's instructions. Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-2: Certificate Signing Request Group Version 6.8 Mediant 2600 E-SBC...

  • Page 92: Assigning Externally Created Private Keys To Tls Contexts

    Mediant 2600 E-SBC Copy the text and send it to your security provider (CA) to sign this request. When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below:...

  • Page 93: Generating Private Keys For Tls Contexts

    TLS Contexts page; the Context Certificates page appears. Scroll down to the Generate new private key and self-signed certificate group: Figure 10-5: Generate new private key and self-signed certificate Group Version 6.8 Mediant 2600 E-SBC...

  • Page 94: Creating Self-Signed Certificates For Tls Contexts

    Mediant 2600 E-SBC From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys: • • 1024 (default) • 2048 • 4096 Click Generate Private Key; a message appears requesting you to confirm key generation.

  • Page 95: Importing Certificates And Certificate Chain Into Trusted Certificate Store

    Open the TLS Contexts page (Configuration tab > System menu > TLS Contexts). In the TLS Contexts table, select the required TLS Context index row, and then click the Context Trusted-Roots button, located at the bottom of the TLS Contexts page; the Trusted Certificates page appears. Version 6.8 Mediant 2600 E-SBC...

  • Page 96: Configuring Mutual Tls Authentication

    Mediant 2600 E-SBC Click the Import button, and then select the certificate file to load. Figure 10-9: Importing Certificate into Trusted Certificates Store Click OK; the certificate is loaded to the device and listed in the Trusted Certificates store. You can also do the following with certificates that are in the Trusted Certificates store: ...

  • Page 97: Tls For Remote Device Management

    The root certificate can also be loaded via the Automatic Update facility, using the HTTPSRootFileName ini file parameter. • You can enable the device to check whether a peer's certificate has been revoked by an OCSP server, per TLS Context (see 'Configuring TLS Certificate Contexts' on page 87). Version 6.8 Mediant 2600 E-SBC...

  • Page 98: Configuring Tls Server Certificate Expiry Check

    Mediant 2600 E-SBC 10.1.8 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure device send...

  • Page 99: Date And Time

    "1". For USA New York, the UTC/GMT offset is -5 hours and therefore, the offset is a minus value and configured as "-5". To configure Daylight Saving Time (DST), see 'Configuring Daylight Saving Time' on page 101. Version 6.8 Mediant 2600 E-SBC...
  • Page 100 Mediant 2600 E-SBC You can also configure the device to authenticate and validate the NTP messages received from the NTP server. Authentication is done using an authentication key with the MD5 cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication.

  • Page 101: Configuring Daylight Saving Time

    If the current date falls within the DST period, verify that it has been successful applied to the device's current date and time. You can view the device's date and time in the Regional Settings page (see 'Configuring Date and Time Manually' on page 99). Version 6.8 Mediant 2600 E-SBC...
  • Page 102 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 103: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 105: Network

    # show voip ports Port Num Port Name MAC Address Speed Duplexity Link Status Native VLAN ------- -------- ------------ ----- -------- ---------- ---------- GE_1 00:1e:67:11:7c:28 100Mbps FULL GE_2 00:1e:67:11:7c:29 100Mbps FULL DOWN Version 6.8 Mediant 2600 E-SBC...
  • Page 106 Mediant 2600 E-SBC The following procedure describes how to configure the Ethernet ports in the Web interface. You can also configure these ports using the table ini file parameter, PhysicalPortsTable or CLI command, configure voip/physical-port. Note: The device provides two MAC addresses for the LAN ports, which are allocated as follows: a MAC address for ports GE_1 through GE_4, and another MAC address for ports GE_5 through GE_8.

  • Page 107: Configuring Ethernet Port Groups

    Device to the IP network interface in the Interface table (see 'Configuring IP Network Interfaces' on page 112). This enables physical separation of network interfaces, providing a higher level of segregation of sub-networks. Equipment connected to different physical Version 6.8 Mediant 2600 E-SBC...
  • Page 108 Mediant 2600 E-SBC ports is not accessible to one another; the only connection between them can be established by cross connecting them with media streams (VoIP calls). The port names (strings) displayed in the Ethernet Group Settings table represent the physical ports on the device.
  • Page 109 Note: Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group. To remove the port, either set this field to None or to a different port. Version 6.8 Mediant 2600 E-SBC...

  • Page 110: Configuring Underlying Ethernet Devices

    Mediant 2600 E-SBC 12.3 Configuring Underlying Ethernet Devices The Ethernet Device table lets you configure up to 48 Ethernet Devices (underlying devices). An Ethernet Device represents a Layer-2 bridging device and is assigned with a VLAN ID. An Ethernet Device is associated with an IP network interface in the Interface table ('Underlying Device' field) and/or with a static route in the Static Route table ('Device Name' field).
  • Page 111 Route table ('Device Name' field - see ''Configuring Static IP Routing'' on page 119). By default, the device automatically assigns a name using the following syntax: "dev <next available table row index>" (e.g., "dev 3"). Version 6.8 Mediant 2600 E-SBC...

  • Page 112: Configuring Ip Network Interfaces

    Mediant 2600 E-SBC 12.4 Configuring IP Network Interfaces You can configure a single VoIP network interface for all applications, including OAMP (management traffic), call control (SIP signaling messages), and media (RTP traffic), or you can configure multiple logical, IP network interfaces for these applications. You may need to logically separated network segments for these applications for administration and security.
  • Page 113 Configure the IP network interface according to the parameters described in the table below. Click Submit. To view configured network interfaces that are currently active, click the IP Interface Status Table button. For more information, see ''Viewing Active IP Interfaces'' on page 481. Version 6.8 Mediant 2600 E-SBC...
  • Page 114 Mediant 2600 E-SBC Table 12-4: Interface Table Parameters Description Parameter Description Table parameters Index Table index row of the interface. CLI: network-if The range is 0 to 47. [InterfaceTable_Index] Web: Application Type Defines the applications allowed on the interface. EMS: Application Types ...

  • Page 115: Assigning Ntp Services To Application Types

    OAMP interface can be combined with Media and Control.  At least one Control interface must be configured.  At least one Media interface must be configured.  Multiple Media and/or Control interfaces can be configured with an IPv6 address. Version 6.8 Mediant 2600 E-SBC...

  • Page 116: Networking Configuration Examples

    Mediant 2600 E-SBC  The network interface types can be combined: • Example 1: ♦ One combined OAMP-Media-Control interface with an IPv4 address • Example 2: ♦ One OAMP interface with an IPv4 address ♦ One or more Control interfaces with IPv4 addresses ♦...

  • Page 117: Voip Interface Per Application Type

    Interfac Default Underlyin Interface IP Address Lengt n Type e Mode Gateway g Device Name OAMP IPv4 192.168.0.2 192.168.0.1 Mgmt Manual Media & IPv4 200.200.85.14 200.200.85. MediaCntrl1 Control Manual Media & IPv4 200.200.86.14 200.200.86. MediaCntrl2 Version 6.8 Mediant 2600 E-SBC...
  • Page 118 Mediant 2600 E-SBC Prefix Inde Applicatio Interfac Default Underlyin Interface IP Address Lengt n Type e Mode Gateway g Device Name Control Manual Media & IPv6 2000::1:200:200:86:1 V6CntrlMedia Control Manual Static Route table: A routing rule is required to allow remote management from a host in 176.85.49.0/24:...

  • Page 119: Voip Interfaces With Multiple Default Gateways

     To configure a static IP route: Open the Static Route Table page (Configuration tab > VoIP menu > Network > Static Route Table). Click Add; the following dialog box appears: Version 6.8 Mediant 2600 E-SBC...
  • Page 120 Mediant 2600 E-SBC Configure a static route according to the parameters described in the table below. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Note: You can delete only static routing rules that are inactive.

  • Page 121: Configuration Example Of Static Ip Routes

     The static route in the Static Route table is associated with the IP network interface in the Interface table, using the 'Device Name' and 'Underlying Device' parameters, respectively. Version 6.8 Mediant 2600 E-SBC...

  • Page 122: Troubleshooting The Routing Table

    Mediant 2600 E-SBC  The static route's Gateway address in the Static Route table is in the same subnet as the IP address of the IP network interface in the Interface table. Figure 12-6: Example of using Static Route 12.5.2 Troubleshooting the Routing Table When adding a new static route to the Static Route table, the added rule passes a validation test.

  • Page 123: Configuring Quality Of Service

    Depends on traffic type:   OAMP Control: Premium Control   Control Management: Bronze Varies according to the interface Depends on traffic type: type associated with NTP (see  Control: Premium control ''Assigning NTP Services to Version 6.8 Mediant 2600 E-SBC...
  • Page 124 Mediant 2600 E-SBC Application Traffic / Network Types Class-of-Service (Priority)  Application Types'' on page 115): Management: Bronze  OAMP  Control The following procedure describes how to configure DiffServ-to-VLAN priority mapping in the Web interface. You can also configure this using the table ini file parameter, DiffServToVlanPriority or CLI command configure voip >...

  • Page 125: Configuring Icmp Messages

    To enable or disable sending and receipt of ICMP Redirect messages, use the 'Send and Receive ICMP Redirect Messages' parameter. To enable or disable the sending of ICMP Destination Unreachable messages, use the 'Send ICMP Unreachable Messages' parameter. Click Submit. Version 6.8 Mediant 2600 E-SBC...

  • Page 126: Dns

    Mediant 2600 E-SBC 12.8 You can use the device's embedded domain name server (DNS) or an external, third-party DNS to translate domain names into IP addresses. This is useful if domain names are used as the destination in call routing. The device supports the configuration of the following DNS types: ...

  • Page 127: Configuring The Internal Srv Table

    You can also configure this using the table ini file parameter, SRV2IP or CLI command, configure voip > voip-network dns srv2ip.  To configure an SRV rule: Open the Internal SRV Table page (Configuration tab > VoIP menu > Network > DNS > Internal SRV Table). Version 6.8 Mediant 2600 E-SBC...
  • Page 128 Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 12-11: Internal SRV Table Page Configure an SRV rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.

  • Page 129: Network Address Translation Support

    IP address configured in the Interface table. The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 12-12: Device behind NAT and NAT Issues Version 6.8 Mediant 2600 E-SBC...

  • Page 130: Configuring A Static Nat Ip Address For All Interfaces

    Mediant 2600 E-SBC 12.9.1.1 Configuring a Static NAT IP Address for All Interfaces You can configure a global (public) IP address of the router to enable static NAT between the device and the Internet for all network interfaces. Thus, the device replaces the source IP address for media of all outgoing SIP messages sent on any of its network interfaces to this public IP address.
  • Page 131 If not configured, the ports are not replaced. Matching [NATTranslation_TargetStartPort source ports are replaced with the target ports. This address is set in the SIP Via and Contact headers, as well as in the o= and c= SDP fields. Version 6.8 Mediant 2600 E-SBC...

  • Page 132: Remote Ua Behind Nat

    Mediant 2600 E-SBC Parameter Description Target End Port Defines the optional, ending port range (0-65535) of the global CLI: TargetEndPort address. If not configured, the ports are not replaced. Matching [NATTranslation_TargetEndPort] source ports are replaced with the target ports. This address is set in the SIP Via and Contact headers, as well as in the o= and c= SDP fields.
  • Page 133 UA. In this mode, the device does not send any packets until it receives the first packet from the UA (in order to obtain the IP address). Version 6.8 Mediant 2600 E-SBC...
  • Page 134 Mediant 2600 E-SBC  To enable NAT resolution using the First Incoming Packet mechanism: Open the General Settings page (Configuration tab > VoIP menu > Media > General Media Settings). Set the 'NAT Mode parameter to one of the following: •...

  • Page 135: Robust Receipt Of Media Streams By Media Latching

    12. Network 12.10 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).
  • Page 136 Mediant 2600 E-SBC ♦ 'New RTCP Stream Packets' ♦ 'New SRTP Stream Packets' ♦ 'New SRTCP Stream Packets' • Define a period (msec) during which if no packets are received from the current media session, the channel can re-latch onto another stream: ♦...

  • Page 137: Multiple Routers Support

    Using multiple router support, the device can utilize these router messages to change its next hop and establish the best path. Note: Multiple Routers support is an integral feature that doesn’t require configuration. Version 6.8 Mediant 2600 E-SBC...
  • Page 138 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 139: Security

    Configuring Firewall Allowed Rules on page 413. The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList or the CLI command, configure voip/access-list. Version 6.8 Mediant 2600 E-SBC...
  • Page 140 Mediant 2600 E-SBC  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security > Firewall Settings). Click Add; the following dialog box appears: Figure 13-1: Firewall Settings Page - Add Record Configure a Firewall rule according to the parameters described in the table below.
  • Page 141 [0] Disable (default)  [1] Enable Notes:  If enabled, then in the 'Interface Name' field (described below), select the interface to which the rule is applied.  If disabled, then the rule applies to all interfaces. Version 6.8 Mediant 2600 E-SBC...
  • Page 142 Mediant 2600 E-SBC Parameter Description Interface Name Defines the network interface to which you want to apply the CLI: network-interface-name rule. This is applicable if you enabled the 'Use Specific [AccessList_Interface_x] Interface' field. The list displays interface names as defined in the Interface table in ''Configuring IP Network Interfaces'' on page 112.

  • Page 143: Configuring General Security Settings

    TLS all the way to the destination (over multiple hops), set the 'Enable SIPS' (EnableSIPS) parameter to Enable in the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Version 6.8 Mediant 2600 E-SBC...

  • Page 144: Intrusion Detection System

    Mediant 2600 E-SBC 13.3 Intrusion Detection System The device's Intrusion Detection System (IDS) feature detects malicious attacks on the device and reacts accordingly. A remote host is considered malicious if it has reached or exceeded a user-defined threshold (counter) of specified malicious attacks.

  • Page 145: Enabling Ids

    Open the IDS Policy Table page (Configuration tab > VoIP menu > Security > Intrusion Detection and Prevention > Policy Table); the table shows the pre- configured IDS policies: Figure 13-3: IDS Policy Table with Default Rules Version 6.8 Mediant 2600 E-SBC...
  • Page 146 Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 13-4: IDS Policy Table - Add Record Configure an IDS Policy name according to the parameters described in the table below. Click Submit. Table 13-3: IDS Policy Table Parameter Descriptions...
  • Page 147 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 361)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response) Version 6.8 Mediant 2600 E-SBC...
  • Page 148 Mediant 2600 E-SBC Parameter Description  [5] Abnormal flow =  Requests and responses without a matching transaction user (except ACK requests)  Requests and responses without a matching transaction (except ACK requests) Threshold Scope Defines the source of the attacker to consider in the device's CLI: threshold-scope detection count.

  • Page 149: Assigning Ids Policies

    !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This CLI: proxy-set indicates the Proxy Sets from where the attacks are coming from. The Version 6.8 Mediant 2600 E-SBC...

  • Page 150: Viewing Ids Alarms

    Mediant 2600 E-SBC Parameter Description [IDSMatch_ProxySet] following syntax is supported:  A comma-separated list of Proxy Set IDs (e.g., 1,3,4)  A hyphen "-" indicates a range of Proxy Sets (e.g., 3,4-7 means IDs 3, and 4 through 7) ...
  • Page 151   Message exceeds a user-defined maximum malformed-invalid- Malformed message length (50K) msg-len Messages   Any SIP parser error malformed-parse-error   Message policy match malformed-message- policy  Basic headers not present  malformed-miss- Version 6.8 Mediant 2600 E-SBC...
  • Page 152 Mediant 2600 E-SBC Type Description Syslog String  Content length header not present (for TCP) header   Header overflow malformed-miss- content-len  malformed-header- overflow   Local authentication ("Bad digest" errors) auth-establish-fail Authentication Failure   Remote authentication (SIP 401/407 is sent if...

  • Page 153: Media

    (bi-directional 2-wire to 4-wire converting device). An estimated echo signal is built by feeding the decoder output signal to an RLS-like adaptive filter, which adapts itself to the characteristics of the echo path. The ‘estimated Version 6.8 Mediant 2600 E-SBC...
  • Page 154 Mediant 2600 E-SBC echo signal’ (the output of this filter) is then subtracted from the input signal (which is the sum of the desired input signal and the undesired echo) to provide a clean signal. To suppress the remaining residual echo, a Non Linear Processor (NLP) is used, as well as a double-talk (two people speak at the same time) detector that prevents false adaptation during near-end speech.
  • Page 155 ECHybridLoss - defines the four-wire to two-wire worst-case Hybrid loss • ECNLPMode - defines the echo cancellation Non-Linear Processing (NLP) mode • EchoCancellerAggressiveNLP - enables Aggressive NLP at the first 0.5 second of the call Version 6.8 Mediant 2600 E-SBC...

  • Page 156: Fax And Modem Capabilities

    Mediant 2600 E-SBC 14.2 Fax and Modem Capabilities This section describes the device's fax and modem capabilities and corresponding configuration. The fax and modem configuration is done in the Fax/Modem/CID Settings page. Notes: • Unless otherwise specified, the configuration parameters mentioned in this section are available on this page.

  • Page 157: Fax/Modem Operating Modes

    You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). This parameter does not affect the actual transmission rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). Version 6.8 Mediant 2600 E-SBC...
  • Page 158 Mediant 2600 E-SBC When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders.
  • Page 159 RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...

  • Page 160: Fax / Modem Transport Mode

    Device answers a call: If the SDP offer from the remote party contains the 'fmtp' attribute with "AcUdpTl", the device answers with the same attribute and employs AudioCodes proprietary T.38-over-RTP mode; otherwise, the standard mode is used. Note: If both T.38 (regular) and T.38 Over RTP coders are negotiated between the call parties, the device uses T.38 Over RTP.

  • Page 161: Fax/Modem Bypass Mode

    Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, BellModemTransportType to 2 (Bypass). Version 6.8 Mediant 2600 E-SBC...

  • Page 162: Fax / Modem Nse Mode

    Tip: When the remote (non-AudioCodes) gateway uses the G.711 coder for voice and doesn’t change the coder payload type for fax or modem transmission, it is recommended to use the Bypass mode with the following configuration: •...

  • Page 163: Fax / Modem Transparent With Events Mode

    Set the 'V.32 Modem Transport Type' parameter to Events Only (V32ModemTransportType = 3). Set the 'V.34 Modem Transport Type' parameter to Events Only (V34ModemTransportType = 3). Set the ini file parameter, BellModemTransportType to 3 (transparent with events). Version 6.8 Mediant 2600 E-SBC...

  • Page 164: Fax / Modem Transparent Mode

    Mediant 2600 E-SBC 14.2.2.7 Fax / Modem Transparent Mode In this mode, fax and modem signals are transferred using the current voice coder without notifications to the user and without automatic adaptations. It's possible to use Profiles (see ''Coders and Profiles'' on page 293) to apply certain adaptations to the channel used for fax / modem.

  • Page 165: Fax Support

    Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). 14.2.3.2 Relay Mode for T.30 and V.34 Faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode. Version 6.8 Mediant 2600 E-SBC...

  • Page 166: Support

    Mediant 2600 E-SBC  To use T.38 mode for V.34 and T.30 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Relay (FaxTransportMode = 1). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0).
  • Page 167 SDP offer containing G.729 and “regular” G.711 coders, it sends an SDP answer containing G.729 and G.711 VBD coders, allowing subsequent bypass (passthrough) sessions if fax / modem signals are detected during the call. Version 6.8 Mediant 2600 E-SBC...

  • Page 168: Configuring Rtp/Rtcp Settings

    Mediant 2600 E-SBC 14.3 Configuring RTP/RTCP Settings This section describes configuration relating to Real-Time Transport Protocol (RTP) and RTP Control Protocol (RTCP). 14.3.1 Configuring the Dynamic Jitter Buffer Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate, voice quality is perceived as good.

  • Page 169: Dual-Tone Multi-Frequency Signaling

    RTP stream according to RFC 2833. To enable this mode, define the following: Set the 'Declare RFC 2833 in SDP' parameter to Yes (RxDTMFOption = 3). Set the '1st Tx DTMF Option' parameter to RFC 2833 (TxDTMFOption = 4). Version 6.8 Mediant 2600 E-SBC...
  • Page 170 Mediant 2600 E-SBC Note: To set the RFC 2833 payload type with a value other than its default, use the RFC2833PayloadType parameter. The device negotiates the RFC 2833 payload type using local and remote SDP and sends packets using the payload type from the received SDP.

  • Page 171: Configuring Rfc 2833 Payload

    Within the port range, the device allocates the UDP ports in "jumps" (spacing) of 5 (default) or 10, configured by the UdpPortSpacing parameter. For example, if the port range starts at 6000 and the UDP port spacing is 10, the available ports include 6000, 6010, 6020, 6030, and so on. Version 6.8 Mediant 2600 E-SBC...

  • Page 172: Automatic Gain Control (Agc)

    Mediant 2600 E-SBC The port range is calculated using the following equation: BaseUDPPort to 65,535 Where, BaseUDPPort is a parameter for configuring the lower boundary of the UDP port range (default is 6000). For example, if the base UDP port is set to 6000, the port range is 6000 to 65,535.
  • Page 173 'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. This parameter can either be the global parameter or per IP Profile. Click Submit. Version 6.8 Mediant 2600 E-SBC...

  • Page 174: Configuring Various Codec Attributes

    Mediant 2600 E-SBC 14.4 Configuring Various Codec Attributes The following codec attribute settings can be configured in the General Media Settings page:  AMR coder: • 'Payload Format': Defines the AMR payload format type.  SILK coder (Skype's default audio codec): •...
  • Page 175 Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 424. Version 6.8 Mediant 2600 E-SBC...
  • Page 176 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 177: Services

    IP Address Lease Time Option 1 Subnet Mask Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Version 6.8 Mediant 2600 E-SBC...
  • Page 178 Mediant 2600 E-SBC DHCP Option Code DHCP Option Name Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
  • Page 179 Web: DNS Server 2 Defines the IP address (IPv4) of the secondary DNS server CLI: dns-server-2 that the DHCP server assigns to the DHCP client. The value [DhcpServer_DNSServer2] is sent in DHCP Option 6 (Domain Name Server). Version 6.8 Mediant 2600 E-SBC...
  • Page 180 Mediant 2600 E-SBC Parameter Description Web: NetBIOS Name Server Defines the IP address (IPv4) of the NetBIOS WINS server CLI: netbios-server that is available to a Microsoft DHCP client. The value is sent [DhcpServer_NetbiosNameServer] in DHCP Option 44 (NetBIOS Name Server).

  • Page 181: Configuring The Vendor Class Identifier

    The VCI is a string that identifies the vendor and functionality of a DHCP client to the DHCP server. For example, Option 60 can show the unique type of hardware (e.g., "AudioCodes 440HD IP Phone") or firmware of the DHCP client. The DHCP server can then differentiate between DHCP clients and process their requests accordingly.

  • Page 182: Configuring Additional Dhcp Options

    Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 15-2: DHCP Vendor Class Table - Add Record Dialog Box Configure a VCI for the DHCP server according to the parameters described in the table below. Click Submit. Table 15-3: DHCP Vendor Class Table Parameter Descriptions...
  • Page 183  [1] IP address = IPv4 address.  [2] Hexadecimal = Hexadecimal-encoded string. For example, if you set the 'Value' parameter to "company.com", you need to set the 'Type' parameter to ASCII. Version 6.8 Mediant 2600 E-SBC...

  • Page 184: Configuring Static Ip Addresses For Dhcp Clients

    Mediant 2600 E-SBC Parameter Description Web: Value Defines the value of the DHCP Option. For example, if you are CLI: value using Option 66, this parameter is used for specifying the TFTP [DhcpOption_Value] provisioning server (e.g., http://192.168.3.155:5000/provisioning/). The valid value is a string of up to 256 characters. By default, no value is defined.

  • Page 185: Viewing And Deleting Dhcp Clients

    To view DHCP clients: # show voip dhcp clients  To view DHCP clients according to IP address: # show voip dhcp ip  To view DHCP clients according to MAC address: # show voip dhcp mac Version 6.8 Mediant 2600 E-SBC...
  • Page 186 Mediant 2600 E-SBC  To view DHCP clients that have been blacklisted from DHCP implementation (due to duplicated IP addresses in the network, where another device is using the same IP address as the one assigned to the client): # show voip dhcp black-list ...

  • Page 187: Sip-Based Media Recording

    • For the maximum number of concurrent sessions that the device can record, contact your AudioCodes sales representative. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons.
  • Page 188 Mediant 2600 E-SBC The device can record calls between two IP Groups. The type of calls to record can be specified by source and/or destination prefix number or SIP Request-URI, as well as by call initiator. The side ("leg") on which the recording is done must be specified. Specifying the leg is important as it determines the various call media attributes of the recorded RTP (or SRTP) such as coder type.
  • Page 189 0-15 m=audio 6030 RTP/AVP 8 96 c=IN IP4 10.33.8.70 a=ptime:20 a=sendonly a=label:2 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 --boundary_ac1fffff85b Content-Type: application/rs-metadata Content-Disposition: recording-session <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> Version 6.8 Mediant 2600 E-SBC...

  • Page 190: Enabling Sip-Based Media Recording

    Mediant 2600 E-SBC <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>1</label> </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label>...
  • Page 191 [SIPRecRouting_RecordedSourcePrefix] Recorded Destination Prefix Defines calls to record based on destination CLI: recorded-dst-prefix number or URI. [SIPRecRouting_RecordedDestinationPrefix] Peer IP Group ID Defines the peer IP Group that is participating in CLI: peer-ip-group-id the call. [SIPRecRouting_PeerIPGroupID] Version 6.8 Mediant 2600 E-SBC...
  • Page 192 Mediant 2600 E-SBC Parameter Description Caller Defines which calls to record according to which CLI: caller party is the caller. [SIPRecRouting_Caller]  [0] Both (default) = Caller can be peer or recorded side  [1] Recorded Party  [2] Peer Party...

  • Page 193: Configuring Sip User Part For Srs

    SIP message, typically in the INVITE and the first 18x response. If the device receives a SIP message with Genesys SIP header, it adds the header's information to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server, as shown below: <ac:GenesysUUID...
  • Page 194 Mediant 2600 E-SBC Note: For calls sent from the device to Avaya equipment, the device can generate the Avaya UCID, if required. To configure this support, use the following parameters: • 'UUI Format' in the IP Group table - enables Avaya support.

  • Page 195: Radius Authentication

    Set up a RADIUS server (third-party) to communicate with the device - see 'Setting Up a Third-Party RADIUS Server' on page  Configure the device as a RADIUS client for communication with the RADIUS server - see 'Configuring RADIUS Authentication' on page Version 6.8 Mediant 2600 E-SBC...

  • Page 196: Setting Up A Third-Party Radius Server

     To set up a third-party RADIUS server (e.g., FreeRADIUS): Define the AudioCodes device as an authorized client of the RADIUS server, with the following: • Predefined shared secret (password used to secure communication between the device and the RADIUS server) •...

  • Page 197: Configuring Radius Authentication

    • If the RADIUS server response does not include the access level attribute: In the 'Default Access Level' field, enter the default access level that is applied to all users authenticated by the RADIUS server. Version 6.8 Mediant 2600 E-SBC...

  • Page 198: Securing Radius Communication

    Mediant 2600 E-SBC Configure RADIUS timeout handling: From the 'Behavior upon Authentication Server Timeout' drop-down list, select the option if the RADIUS server does not respond within five seconds: ♦ Deny Access: device denies user login access. ♦ Verify Access Locally: device checks the username and password configured locally for the user (in the Web User Accounts page or Web Users table), and if correct, allows access.

  • Page 199: Ldap-Based Management And Sip Services

    (Operator, Admin, or Security Admin). This is known as the user authorization stage. To determine the access level, the device searches the LDAP directory for groups of which the user is a member, for example: CN=\# Support Dept,OU=R&D Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=a bc,DC=com Version 6.8 Mediant 2600 E-SBC...

  • Page 200: Enabling The Ldap Service

    Mediant 2600 E-SBC The device then assigns the user the access level configured for that group (in 'Configuring Access Level per Management Groups Attributes' on page 206). The location in the directory where you want to search for the user's member group(s) is configured using the following: •...

  • Page 201: Enabling Ldap-Based Web/Cli User Login Authentication And Authorization

    You can also configure this using the table ini file parameter, LdapConfiguration or CLI command, configure voip/ldap/ldap-configuration.  To configure an LDAP server: Open the LDAP Configuration Table page (Configuration tab > VoIP menu > Services > LDAP > LDAP Configuration Table). Version 6.8 Mediant 2600 E-SBC...
  • Page 202 Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 15-11: LDAP Configuration Table - Add Record Configure an LDAP server according to the parameters described in the table below. Click Submit. LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
  • Page 203 [1] OAM Interface = The OAMP interface (may be combined with other applications such as Control and Media) in the IP Interfaces table is used. For configuring IP network interfaces, see Configuring IP Network Interfaces. Version 6.8 Mediant 2600 E-SBC...

  • Page 204: Configuring Ldap Dns (Base Paths) Per Ldap Server

    Mediant 2600 E-SBC Parameter Description Type Defines whether the LDAP server is used for SIP-related queries or CLI: type management login authentication-related queries. [LdapConfiguration_Ty  [0] Control (Default)  [1] Management Note: If you use the same LDAP server for both management and SIP (Control) related applications, the device establishes different LDAP sessions for each application.

  • Page 205: Configuring The Ldap Search Filter Attribute

    "SueM".  Attribute (e.g., "memberOf") to return from objects that match the filter criteria: The attribute is configured by the 'Management Attribute' parameter in the LDAP Configuration table (see 'Configuring LDAP Servers' on page 201). Version 6.8 Mediant 2600 E-SBC...

  • Page 206: Configuring Access Level Per Management Groups Attributes

    Mediant 2600 E-SBC Therefore, the LDAP response includes only the groups of which the specific user is a member. Notes: • The search filter is applicable only to LDAP-based login authentication and authorization queries. • The search filter is a global setting that applies to all LDAP-based login authentication and authorization queries, across all configured LDAP servers.
  • Page 207 Figure 15-14: Management LDAP Groups Table - Add Record Configure a group name(s) with a corresponding access level according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 2600 E-SBC...

  • Page 208: Configuring Ldap Search Methods

    Mediant 2600 E-SBC Management LDAP Groups Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [MgmntLDAPGroups_ Note: Each table row must be configured with a unique index. GroupIndex] Level Defines the access level of the group(s).

  • Page 209: Configuring The Device's Ldap Cache

    Improves routing decision performance by using local cache for subsequent LDAP queries  Reduces number of queries performed on an LDAP server and corresponding bandwidth consumption  Provides partial survivability in case of intermittent LDAP server failure (or network isolation) Version 6.8 Mediant 2600 E-SBC...
  • Page 210 Mediant 2600 E-SBC The handling of LDAP queries with the LDAP cache is shown in the flowchart below: Figure 15-16: LDAP Query Process with Local LDAP Cache Note: If for the first LDAP query, the result fails for at least one attribute and is successful for at least one, the partial result is cached.

  • Page 211: Configuring Local Database For Management User Authentication

    Web Users table. To configure local Web/CLI users in the Web Users table, see Configuring Web User Accounts. Notes: • This feature is applicable to LDAP and RADIUS servers. • This feature is applicable only to user management authentication. Version 6.8 Mediant 2600 E-SBC...
  • Page 212 Mediant 2600 E-SBC  To use the Web Users table for authenticating management users: Open the Authentication Settings page (Configuration tab > System menu > Management > Authentication Settings). Figure 15-18: Authentication Settings Page - Local Database for Login Authentication Under General Login Authentication Settings: •...

  • Page 213: Ldap-Based Login Authentication Example

    The LDAP server's entry data structure schema in the example is as follows:  DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: Figure 15-19: Base Path (DN) in LDAP Server Version 6.8 Mediant 2600 E-SBC...
  • Page 214 Mediant 2600 E-SBC  Search Attribute Filter: (sAMAccountName=$). The login username is found based on this attribute (where the attribute's value equals the username): Figure 15-20: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the...
  • Page 215 The search attribute filter based on username is configured by the 'LDAP Authentication Filter' parameter in the LDAP Settings page (see 'Configuring the LDAP Search Filter Attribute' on page 205): Figure 15-24: Configuring Search Attribute Filter Version 6.8 Mediant 2600 E-SBC...
  • Page 216 Mediant 2600 E-SBC  The group management attribute is configured by the 'Management Attribute' parameter in the LDAP Configuration table: Figure 15-25: Configuring Management Attribute  The management group and its corresponding access level is configured in the Management LDAP Groups table (see 'Configuring Access Level per Management...

  • Page 217: Active Directory-Based Routing For Microsoft Lync

    Primary or Secondary key. MSLDAPPrimaryKey Primary Key query search instead of PBX msRTCSIP-PrivateLine= key - can be any AD attribute +3233554480 MSLDAPSecondaryKey Secondary Key query key search if Primary Key fails - can be any attribute Version 6.8 Mediant 2600 E-SBC...
  • Page 218 Mediant 2600 E-SBC The process for querying the AD and subsequent routing based on the query results is as follows: If the Primary Key is configured, it uses the defined string as a primary key instead of the one defined in MSLDAPPBXNumAttributeName. It requests the attributes which are described below.
  • Page 219 "LDAP_ERR" prefix destination number value. The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 15-27: LDAP Query Flowchart Version 6.8 Mediant 2600 E-SBC...

  • Page 220: Configuring Ad-Based Routing Rules

    Mediant 2600 E-SBC Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page for the LDAP query process. 15.4.11.2 Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries.
  • Page 221 AD server. When the AD replies, the device searches the table, from the first rule down, for the matching destination phone prefix (i.e., "PRIVATE:, "PBX:", "OCS:", "MOBILE:", and "LDAP_ERR:"), and then sends the call to the appropriate destination. Version 6.8 Mediant 2600 E-SBC...

  • Page 222: Least Cost Routing

    Mediant 2600 E-SBC 15.5 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how to configure it. 15.5.1 Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost.
  • Page 223 Index 3 - no Cost Group is assigned, but as the Default Cost parameter is set to Min, it is selected as the cheapest route • Index 4 - Cost Group "B" is only second-matched rule (Index 1 is the first) Version 6.8 Mediant 2600 E-SBC...

  • Page 224: Configuring Lcr

    Mediant 2600 E-SBC  Example 3: This example shows how the cost of a call is calculated if the call spans over multiple time bands: Assume a Cost Group, "CG Local" is configured with two time bands, as shown below:...
  • Page 225 1. Therefore, a call of 1 minute cost 7 units. Therefore, for calls under one minute, "Weekend A" carries the lower cost. However, if the average call duration is more than one minute, then "Weekend B" carries the lower cost. Version 6.8 Mediant 2600 E-SBC...

  • Page 226: Configuring Cost Groups

    Mediant 2600 E-SBC Parameter Description Default Cost Determines whether routing rules in the Outbound IP Routing CLI: lcr-default-cost table without an assigned Cost Group are considered a higher [RoutingRuleGroups_LCRDefaul cost or lower cost route compared to other matched routing tCost] rules that are assigned Cost Groups.

  • Page 227: Configuring Time Bands For Cost Groups

    Time Band link located below the table; the Time Band table for the selected Cost Group appears. Click Add; the following dialog box appears: Configure a Time Band according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 2600 E-SBC...

  • Page 228: Assigning Cost Groups To Routing Rules

    Mediant 2600 E-SBC Table 15-10: Time Band Table Description Parameter Description Index Defines an index number for the new table record. CLI: timeband-index Note: Each table row must be configured with a unique index. [CostGroupTimebands_Timeba ndIndex] Start Time Defines the day and time of day from when this time band is CLI: start-time applicable.

  • Page 229: Configuring Call Setup Rules

    If an Exit Action Type is not configured and the device has run all the rules in the Set ID, the default Action Value of the Set ID is "True" (i.e., use the current routing rule). Version 6.8 Mediant 2600 E-SBC...
  • Page 230 Mediant 2600 E-SBC  Rule's condition is not met: The device runs the next rule in the Set ID. When the device reaches the end of the Set ID and no Exit was performed, the Set ID ends with a "True" result.
  • Page 231 Defines the element (header, parameter, or body) upon CLI: action-subject which you want to perform the action. [CallSetupRules_ActionSubject] The valid value is a string of up to 100 characters (case- insensitive). Examples:  header.from contains '1234' Version 6.8 Mediant 2600 E-SBC...
  • Page 232 Mediant 2600 E-SBC Parameter Description  param.call.dst.user (called number)  param.call.src.user (calling number)  param.call.src.name (calling name)  param.call.redirect (redirect number)  param.call.src.host (source host)  param.call.dst.host (destination host) Action Type Defines the type of action to perform. CLI: action-type ...

  • Page 233: Call Setup Rule Examples

    ♦ 'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName • Routing table configuration: A single routing rule is assigned the Call Setup Rule Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 2 Version 6.8 Mediant 2600 E-SBC...
  • Page 234 Mediant 2600 E-SBC  Example 3: This example configures the device to route the incoming call according to whether or not the source number of the incoming call also exists in the AD server. The device queries the AD server for the attribute record, "telephoneNumber" whose value is the same as the received source number (e.g., telephoneNumber=4064").

  • Page 235: Quality Of Experience

    The device can be configured to report voice (media) Quality of Experience (QoE) to AudioCodes' Session Experience Manager (SEM) server, a plug-in for AudioCodes EMS. The reports include real-time metrics of the quality of the actual call experience, which are then processed by the SEM.

  • Page 236: Configuring Clock Synchronization Between Device And Sem

    In other words, you need to configure them with the same NTP server. The NTP server can be one of the following:  AudioCodes EMS server (also acting as an NTP server)  Third-party, external NTP server Once you have determined the NTP server, all the elements--device, SEM, and EMS--must be configured with the same NTP server address.
  • Page 237 User's Manual 16. Quality of Experience  Yellow: Indicates medium call quality  Red: Indicates poor call quality Version 6.8 Mediant 2600 E-SBC...
  • Page 238  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 236.
  • Page 239 Click Submit, and then save ("burn") your settings to flash memory. Table 16-2: Quality of Experience Color Rules Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. CLI: index [QOEColorRules_ColorRuleIndex] Version 6.8 Mediant 2600 E-SBC...
  • Page 240 Mediant 2600 E-SBC Parameter Description Monitored Parameter Defines the parameter to monitor and report. CLI: monitored-parameter  [0] MOS (default) [QOEColorRules_monitoredParam  [1] Delay  [2] Packet Loss  [3] Jitter  [4] RERL [Echo] Direction Defines the monitoring direction.

  • Page 241: Configuring Bandwidth Profiles

    Hysteresis is used to avoid false reports. The following procedure describes how to configure Bandwidth Profiles in the Web interface. You can also configure Bandwidth Profiles using the table ini file parameter, BWProfile or CLI command, configure voip/qoe bw-profile. Version 6.8 Mediant 2600 E-SBC...
  • Page 242 Mediant 2600 E-SBC  To configure Bandwidth Profiles: Open the Bandwidth Profile page (Configuration tab > VoIP menu > Quality of Experience > Bandwidth Profile). Click Add; the following dialog box appears: Figure 16-4: Bandwidth Profile Page - Add Record...
  • Page 243 If enabled, an alarm is sent if one of the following scenarios occurs:  Warning threshold is exceeded (Warning severity - Yellow threshold).  Any configured bandwidth threshold is exceeded (Major severity - Red threshold). Version 6.8 Mediant 2600 E-SBC...

  • Page 244: Configuring Media Enhancement Profiles

    Mediant 2600 E-SBC 16.4 Configuring Media Enhancement Profiles Media Enhancement Profiles provides support for access control and media quality enhancements based on call quality measurements (configured in ''Configuring Quality of Experience Profiles'' on page 236) and bandwidth utilization (configured in ''Configuring Bandwidth Profiles'' on page 241).
  • Page 245 Figure 16-6: Media Enhancement Rules - Add Record Configure a Media Enhancement Rule according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Version 6.8 Mediant 2600 E-SBC...
  • Page 246 Mediant 2600 E-SBC Table 16-5: Media Enhancement Rules Table Parameter Descriptions Parameter Description Index Defines the index of the table row entry. CLI: rule-index [MediaEnhancementRules_RuleIndex] Trigger Defines the monitored metrics parameter or bandwidth CLI: trigger associated with this rule. [MediaEnhancementRules_Trigger] ...

  • Page 247: Control Network

    If you modify a Media Realm currently being used by a call, the device does not perform Quality of Experience for the call. If you delete the Media Realm during the call, the device maintains the call until the call parties end the call. Version 6.8 Mediant 2600 E-SBC...
  • Page 248 Mediant 2600 E-SBC The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm or CLI command, configure voip/voip-network realm.  To configure a Media Realm: Open the Media Realm Table page (Configuration tab >...
  • Page 249 If the parameter is not configured, then the first Media Realm in the table is used as default.  If the table is not configured, the default Media Realm includes all the configured media interfaces. Version 6.8 Mediant 2600 E-SBC...
  • Page 250 Mediant 2600 E-SBC Parameter Description QoE Profile Assigns a QoE Profile to the Media Realm. For configuring CLI: qoe-profile QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 236. BW Profile Assigns a Bandwidth Profile to the Media Realm. For...

  • Page 251: Configuring Remote Media Subnets

    > Media Realm Configuration). Select the Media Realm index row for which you want to add Remote Media Subnets, and then click the Remote Media Subnet link located below the table; the Remote Media Subnet table appears. Version 6.8 Mediant 2600 E-SBC...
  • Page 252 Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 17-3: Remote Media Subnet - Add Record Configure the Remote Media Subnet according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.

  • Page 253: Configuring Srds

    Define it as a Classification rule for incoming SIP requests (see ''Configuring Classification Rules'' on page 361)  Use it as a destination IP-to-IP routing rule (see Configuring SBC IP-to-IP Routing Rules on page 368) Version 6.8 Mediant 2600 E-SBC...
  • Page 254 Mediant 2600 E-SBC The following procedure describes how to configure SRDs in the Web interface. You can also configure this using the table ini file parameter, SRD or CLI command, configure voip > voip-network srd.  To configure an SRD: Open the SRD Table page (Configuration tab >...
  • Page 255 Note: Regardless of the parameter, the device always accepts registration refreshes from users that are already registered in its database. Version 6.8 Mediant 2600 E-SBC...

  • Page 256: Configuring Sip Interfaces

    Mediant 2600 E-SBC 17.4 Configuring SIP Interfaces The SIP Interface table lets you configure up to 500 SIP Interfaces. A SIP Interface defines a listening port and type (UDP, TCP, or TLS) for SIP signaling traffic on a specific logical IP network interface (configured in the Interface table).
  • Page 257  This port must be outside of the RTP port range.  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). Version 6.8 Mediant 2600 E-SBC...
  • Page 258 Mediant 2600 E-SBC Parameter Description Assigns an SRD ID to the SIP Interface (configured in CLI: srd ''Configuring SRDs'' on page 253). [SIPInterface_SRD] The default is 0. Notes:  You can assign the same SRD ID to up to two SIP Interfaces of the same application type.
  • Page 259 IP Group is applied to the outgoing call.  If both the SIP Interface and IP Group associated with the incoming call are assigned a Message Manipulation Set, the one assigned to the SIP Interface is applied first. Version 6.8 Mediant 2600 E-SBC...

  • Page 260: Configuring Ip Groups

    Mediant 2600 E-SBC 17.5 Configuring IP Groups The IP Group table lets you configure up to 200 IP Groups. An IP Group represents a SIP entity in the network with which the device communicates. This can be a server (e.g., IP PBX or ITSP) or it can be a group of users (e.g., LAN IP phones).
  • Page 261 To route a call to a registered user, a rule must be configured in the SBC IP-to-IP Routing table. The device searches the dynamic database (by using the request URI) for an entry that matches a Version 6.8 Mediant 2600 E-SBC...
  • Page 262 Mediant 2600 E-SBC Parameter Description registered AOR or Contact. Once an entry is found, the IP destination is obtained from this entry, and a SIP request is sent to the destination. The device also supports NAT traversal for the SIP clients located behind NAT.
  • Page 263 Inbound IP Routing table can be used to identify the source IP Group from where the INVITE message was received. If this parameter is not configured (default), these headers are populated with the device's dotted-decimal IP address of the network Version 6.8 Mediant 2600 E-SBC...
  • Page 264 Mediant 2600 E-SBC Parameter Description interface on which the message is sent. Note: To ensure proper device handling, this parameter should be a valid FQDN. UUI Format Enables the generation of the Avaya UCID value, adding it to the outgoing INVITE sent to this IP Group.
  • Page 265 Defines the maximum number of users in this IP Group that can Users register with the device. By default, no limitation exists for registered CLI: max-num-of-reg-users users. [IPGroup_MaxNumOfRegUser Note: This field is applicable only to User-type IP Groups. Version 6.8 Mediant 2600 E-SBC...
  • Page 266 Mediant 2600 E-SBC Parameter Description Inbound Message Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the inbound message. To configure CLI: inbound-mesg- Message Manipulation rules, see Configuring SIP Message manipulation-set Manipulation on page 284.
  • Page 267 This parameter is applicable only when classification is done according to the Classification table.  If the configured SIP header does not exist in the incoming INVITE message, the classification of the message to a source IP Version 6.8 Mediant 2600 E-SBC...
  • Page 268 Mediant 2600 E-SBC Parameter Description Group fails.  If the device receives an INVITE as a result of a REFER request or a 3xx response, then the incoming INVITE is routed according to the Request-URI. The device identifies such INVITEs according to a specific prefix in the Request-URI header, configured by the SBCXferPrefix parameter.

  • Page 269: Configuring Proxy Sets

    (addresses) configured for the Proxy Set are online or offline. If offline, the device will not route the call to the specific proxy. You can configure the device to send either SIP OPTIONS or REGISTER messages for the keep-alive. The keep-alive feature is required Version 6.8 Mediant 2600 E-SBC...
  • Page 270 Mediant 2600 E-SBC when using the proxy load-balancing or redundancy feature. For load-balancing, the device performs keep-alive on all proxies. For Parking-type redundancy, the device performs keep-alive only on the currently active proxy. For Homing-type redundancy, the device performs keep-alive on the current proxy as well as the "main" proxy. When using SIP OPTIONS, you can configure the device to consider the proxy as offline if specific SIP response codes are received from the keep-alive messages.
  • Page 271 The address can be defined as an IP address in dotted-decimal [ProxyIp_IpAddress] notation (e.g., 201.10.8.1) or FQDN. You can also specify the port in the following format:  IPv4 address: <IP address>:<port> (e.g., 201.10.8.1:5060)  IPv6 address: <[IPV6 address]>:<port> (e.g., [2000::1:200:200:86:14]:5060) Version 6.8 Mediant 2600 E-SBC...
  • Page 272 Mediant 2600 E-SBC Parameter Description Transport Type Defines the transport type for communicating with the Proxy CLI: voip-network proxy-ip > server. transport-type  [0] UDP [ProxyIp_TransportType]  [1] TCP  [2] TLS  [-1] = Undefined Note: If this parameter is not defined, the setting of the global parameter SIPTransportType is used.
  • Page 273 The valid range is 1 to 30. The default is 10. Note: The parameter is applicable only if the 'Proxy Keep-Alive' parameter is set to Using Options. Failure Detection Retransmissions Defines the maximum number of UDP retransmissions that the Version 6.8 Mediant 2600 E-SBC...
  • Page 274 Mediant 2600 E-SBC Parameter Description fail-detect-rtx device sends to an offline proxy, before the device considers the proxy as being offline. [ProxySet_FailureDetectionRetrans missions] The valid range is -1 to 255. The default is -1 (i.e., the settings of the global parameter SIPMaxRtxis applied).
  • Page 275 'Transport Type' parameter is set to UDP, the device uses UDP to communicate with the proxy and no TLS Context is used. For more information about how certificates are associated with calls and for configuring TLS Contexts, see Configuring SSL/TLS Certificates on page 87. Version 6.8 Mediant 2600 E-SBC...
  • Page 276 Mediant 2600 E-SBC User's Manual Document #: LTRT-42060...

  • Page 277: Sip Definitions

    Proxy & Registration page The following procedure describes how to configure Accounts in the Web interface. You can also configure Accounts using the table ini file parameter, Account or CLI command, configure voip > sip-definition account. Version 6.8 Mediant 2600 E-SBC...
  • Page 278 Mediant 2600 E-SBC  To configure an Account: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Figure 18-1: Account Table - Add Record Configure an account according to the parameters described in the table below.

  • Page 279: Regular Registration Mode

    GIN-based registration of users to a SIP registrar on behalf of a SIP PBX. In effect, the PBX registers with the service provider, just as a directly hosted SIP endpoint would register. However, because a PBX has multiple user agents, it needs to register a Version 6.8 Mediant 2600 E-SBC...
  • Page 280 Mediant 2600 E-SBC contact address on behalf of each of these. Rather than performing a separate registration procedure for each user agents, GIN registration mode does multiple registrations using a single REGISTER transaction. According to this mechanism, the PBX delivers to the service provider in the Contact...

  • Page 281: Configuring Proxy And Registration Parameters

    ''Viewing Registration Status'' on page 483.  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Configure the parameters as required. Click Submit. Version 6.8 Mediant 2600 E-SBC...

  • Page 282: Sip Message Authentication Example

    The REGISTER request is sent to a Registrar/Proxy server for registration: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c17940 To: <sip: 122@10.1.1.200> Call-ID: 634293194@10.1.1.200 User-Agent: Sip-Gateway/Mediant 2600 E-SBC/v.6.80.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Upon receipt of this request, the Registrar/Proxy returns a 401 Unauthorized response: SIP/2.0 401 Unauthorized...
  • Page 283 • The password from the ini file is "AudioCodes". • The equation to be evaluated is "122:audiocodes.com:AudioCodes". According to the RFC, this part is called A1. • The MD5 algorithm is run on this equation and stored for future usage.

  • Page 284: Configuring Sip Message Manipulation

    Mediant 2600 E-SBC Contact: <sip:122@10.1.1.200>; expires="Thu, 26 Jul 2012 10:34:42 GMT"; action=proxy; q=1.00 Contact: <122@10.1.1.200:>; expires="Tue, 19 Jan 2038 03:14:07 GMT"; action=proxy; q=0.00 Expires: Thu, 26 Jul 2012 10:34:42 GMT 18.4 Configuring SIP Message Manipulation The Message Manipulations table lets you configure up to 200 Message Manipulation rules.
  • Page 285 Current Condition). For more information, see the description of the 'Row Rule' parameter in this section. Figure 18-2: Configuration Example of Message Manipulation Rules using Same Condition The figure below illustrates a SIP message manipulation example: Figure 18-3: SIP Header Manipulation Example Version 6.8 Mediant 2600 E-SBC...
  • Page 286 Mediant 2600 E-SBC Notes: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide. • Inbound message manipulation is done only after the Classification, inbound/outbound number manipulations, and routing processes.
  • Page 287 Note: Currently, SIP 100 Trying messages cannot be manipulated. Condition Defines the condition that must exist for the rule to apply. CLI: condition The valid value is a string (case-insensitive). [MessageManipulations_Co For example: Version 6.8 Mediant 2600 E-SBC...
  • Page 288 Mediant 2600 E-SBC Parameter Description  ndition] header.from.url.user== '100' (indicates that the user part of the From header must have the value "100")  header.contact.param.expires > '3600'  header.to.url.host contains 'domain'  param.call.dst.user != '100' Operation Action Subject Defines the SIP header upon which the manipulation is performed.

  • Page 289: Configuring Sip Message Policy Rules

    MessagePolicy or the CLI command, configure voip > sbc message-policy.  To configure SIP Message Policy rules: Open the Message Policy Table page (Configuration tab > VoIP menu > SIP Definitions > Msg Policy & Manipulation > Message Policy Table). Version 6.8 Mediant 2600 E-SBC...
  • Page 290 Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 18-6: Message Policy Table - Add Record Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
  • Page 291 'Body List' parameter (above). [MessagePolicy_BodyListType]  [0] Policy Blacklist =The specified SIP body is rejected.  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; the others are rejected. Version 6.8 Mediant 2600 E-SBC...
  • Page 292 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 293: Coders And Profiles

    You can also configure this table using the table ini file parameter, CodersGroup0 or CLI command, configure voip > coders-and-profiles coders-group.  To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Version 6.8 Mediant 2600 E-SBC...
  • Page 294 Mediant 2600 E-SBC Configure coders according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 19-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder.
  • Page 295 30 (default), 60, 90, 120 silk-nb 20 (default), 40, 60, 80, Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 T.38 [t38fax] T.38 Version 3 [t38fax] Version 6.8 Mediant 2600 E-SBC...

  • Page 296: Configuring Coder Groups

    Mediant 2600 E-SBC 19.2 Configuring Coder Groups The Coder Group Settings table lets you configure up to 10 Coder Groups. A Coder Group is a set of configured coders (coder type, packetization time, rate, payload type, and silence suppression). Each Coder Group can include up to 10 coders.

  • Page 297: Configuring Ip Profiles

    The following procedure describes how to configure IP Profiles in the Web interface. You can also configure IP Profiles using the table ini file parameter, IPProfile or the CLI command, configure voip > coders-and-profiles ip-profile. Version 6.8 Mediant 2600 E-SBC...
  • Page 298 Mediant 2600 E-SBC  To configure an IP Profile: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Figure 19-3: IP Profile Table - Add Record Configure an IP Profile according to the parameters described in the table below.
  • Page 299 CLI: echo-canceller  [0] Disable [IpProfile_EnableEchoCancell  [1] Line (default)  [2] Acoustic Notes:  For more information on the Echo Cancellation feature, see Echo Cancellation on page 153.  The corresponding global parameter is EnableEchoCanceller Version 6.8 Mediant 2600 E-SBC...
  • Page 300 Mediant 2600 E-SBC Parameter Description Web: Disconnect on Broken Defines the device's handling of calls when RTP packets (media) Connection are not received within a user-defined timeout (configured by the CLI: disconnect-on-broken- BrokenConnectionEventTimeout parameter). connection  [0] Ignore = The call is maintained despite no media and is [IpProfile_DisconnectOnBrok released when signaling ends the call (i.e., SIP BYE).
  • Page 301 MKI parameter is not included in the crypto line in the SDP answer (even if the SRTPTxPacketMKISize parameter is set to any value other than 0). Note: The corresponding global parameter is EnableSymmetricMKI. Version 6.8 Mediant 2600 E-SBC...
  • Page 302 Mediant 2600 E-SBC Parameter Description Web: MKI Size Defines the size (in bytes) of the Master Key Identifier (MKI) in CLI: mki-size SRTP Tx packets. [IpProfile_MKISize] The valid value is 0 to 4. The default is 0 (i.e., new keys are generated without MKI).
  • Page 303 Allowed Video Coders Group ID. By default, no Allowed Video Coders Group is assigned (i.e., all video coders are allowed). To configure Allowed Video Coders Groups, see Configuring Allowed Video Coder Groups on page 360. Version 6.8 Mediant 2600 E-SBC...
  • Page 304 Mediant 2600 E-SBC Parameter Description Web: Allowed Coders Mode Defines the mode of the Allowed Coders feature for this SIP entity. CLI: sbc-allowed-coders-mode  [0] Restriction = In the incoming SDP offer, the device uses only [IpProfile_SBCAllowedCodersM Allowed coders; the rest are removed from the SDP offer (i.e.,...
  • Page 305 [1] Add = Adds a P-Asserted-Identity header. The header's values are taken from the source URL.  [2] Remove = Removes the P-Asserted-Identity header. Notes:  This parameter affects only the initial INVITE request.  The corresponding global parameter is SBCAssertIdentity. Version 6.8 Mediant 2600 E-SBC...
  • Page 306 Mediant 2600 E-SBC Parameter Description Web: Diversion Mode Defines the device’s handling of the SIP Diversion header for this CLI: sbc-diversion-mode SIP entity. For more information on interworking of the History-Info [IpProfile_SBCDiversionMode] and Diversion headers, see Interworking SIP Diversion and History-Info Headers on page 339.
  • Page 307 [0] Not Supported = UPDATE message is not supported. upport]  [1] Supported Only After Connect = UPDATE message is supported only after the call is connected.  [2] Supported = (Default) UPDATE message is supported during call setup and after call establishment. Version 6.8 Mediant 2600 E-SBC...
  • Page 308 Mediant 2600 E-SBC Parameter Description Web: Remote re-INVITE Defines whether the destination UA of the re-INVITE request CLI: sbc-rmt-re-invite-supp supports re-INVITE messages and if so, whether it supports re- [IpProfile_SBCRemoteReinvite INVITE with or without SDP. Support]  [0] Not Supported = re-INVITE is not supported and the device does not forward re-INVITE requests.
  • Page 309 Progress are forwarded to the caller, for this SIP entity. 8xSupport]  [0] Not Supported = Only the first 18x response is forwarded to the caller.  [1] Supported = (Default) Multiple 18x responses are forwarded to the caller. Version 6.8 Mediant 2600 E-SBC...
  • Page 310 Mediant 2600 E-SBC Parameter Description Web: Remote Early Media Defines the SIP provisional response type - 180 or 183 - for Response Type forwarding early media to the caller, for this SIP entity. CLI: sbc-rmt-early-media-resp  [0] Transparent = (Default) All early media response types are [IpProfile_SBCRemoteEarlyMed supported;...
  • Page 311 (re-INVITE / UPDATE) and sends a 200 OK to the initiator of the call hold. The device plays a held tone to the held party if the 'SBC Play Held Tone' parameter is set to Yes. Version 6.8 Mediant 2600 E-SBC...
  • Page 312 Mediant 2600 E-SBC Parameter Description Web: Remote Replaces Enables the device to handle incoming INVITEs containing the Behavior Replaces header for the SIP entity (which does not support the CLI: sbc-rmt-replaces-behavior header) associated with the IP Profile. The Replaces header is...
  • Page 313 Ptime' parameter (see below) if it is configured to a non-zero value. Note: Regardless of the settings of this parameter, if a non-zero value is configured for the 'Preferred Ptime' parameter (see below), it is used as the ptime in the SDP offer. Version 6.8 Mediant 2600 E-SBC...
  • Page 314 Mediant 2600 E-SBC Parameter Description Web: Preferred Ptime Defines the packetization time (ptime) in msec for the SIP entity CLI: sbc-preferred-ptime associated with the IP Profile, in the outgoing SDP offer. [IpProfile_SBCPreferredPTime] If the 'SDP Ptime Answer' parameter (see above) is configured to...
  • Page 315 Delay' (DJBufMinDelay) and 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed.  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. Version 6.8 Mediant 2600 E-SBC...
  • Page 316 Mediant 2600 E-SBC Parameter Description Web: Remote Renegotiate on Enables local handling of fax detection and negotiation by the Fax Detection device on behalf of the SIP entity (to which the IP Profile is assigned). This applies to faxes sent immediately upon the CLI: sbc-rmt-renegotiate-on-fax- establishment of a voice channel (i.e., after 200 OK).

  • Page 317: Session Border Controller Application

    Part V Session Border Controller Application...

  • Page 319: Sbc Overview

    Each leg has its own Route/Record Route set. • Modifies SIP To, From, and Request-URI host names (must be configured using the Message Manipulations table). • Generates a new SIP Call-ID header value (different between legs). Version 6.8 Mediant 2600 E-SBC...

  • Page 320: Sip Network Definitions

    Mediant 2600 E-SBC • Changes the SIP Contact header to the device's own address. • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following: •...

  • Page 321: Sip Dialog Initiation Process

    Hunt Group - used for call survivability. • IP address (in dotted-decimal notation or FQDN - NAPTR/SRV/A-Record resolutions) according to a specified Dial Plan index listed in the loaded Dial Plan file. • LDAP server or LDAP query result. Version 6.8 Mediant 2600 E-SBC...
  • Page 322 Mediant 2600 E-SBC For more information, see ''Configuring SBC IP-to-IP Routing Rules'' on page 368. Manipulating SIP URI user part (source and destination) of inbound and/or outbound SIP dialog requests: You can configure rules for manipulating the SIP URI user part (source and destination) on the inbound and/or outbound leg. For more information, see ''SBC Manipulations'' on page 380.

  • Page 323: User Registration

    By default, the Contact header in the outgoing REGISTER is populated with a unique contact generated by the device and associated with the specific registration. Alternatively, the original user can be retained in the Contact header and used in the outgoing REGISTER request (using the SBCKeepContactUserinRegister parameter). Version 6.8 Mediant 2600 E-SBC...

  • Page 324: Sbc Users Registration Database

    Mediant 2600 E-SBC 20.3.2 SBC Users Registration Database The device manages a dynamic Users Registration database that is updated according to registration requests that traverse it. Each database entry for a user represents a binding between an AOR (obtained from the SIP To header) and one or more contact (obtained from the SIP Contact headers).

  • Page 325: Registration Restriction Control

    The flowchart below depicts the process for blocking unregistered users. When the call is rejected, the device sends a SIP 500 (Server Internal Error) response to the remote end. Figure 20-2: Blocking Incoming Calls from Unregistered Users Version 6.8 Mediant 2600 E-SBC...

  • Page 326: Sbc Media Handling

    Mediant 2600 E-SBC 20.4 SBC Media Handling Media behavior includes anything related to the establishment, management and termination of media sessions within the SIP protocol. Media sessions are created using the SIP "offer"/"answer" mechanism. If successful, the result is a bi-directional media (RTP) flow (e.g.

  • Page 327: Media Anchoring Without Transcoding (Transparent)

    (i.e., the SDP answer from one user agent doesn't include any coder included in the offer previously sent by the other user agent). For transcoding, the device can be configured to add media capabilities to user agents pertaining to a specific IP Group, and Version 6.8 Mediant 2600 E-SBC...
  • Page 328 Mediant 2600 E-SBC then perform transcoding in cases where the selected coder in the answer SDP is not one that appears in the original offer. The capabilities that can be added are one or more of the device's supported coders...

  • Page 329: No Media Anchoring

    The device does not need to perform NAT traversal (for media) and all the users are in the same domain. Figure 20-5: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring feature include the following: Version 6.8 Mediant 2600 E-SBC...

  • Page 330: Transcoding Modes

    Mediant 2600 E-SBC  Saves network bandwidth  Reduces CPU usage (no media handling)  Avoids interference in SDP negotiation and header manipulation on RTP/SRTP The device handles the No Media Anchoring process as follows: Identifies a No Media Anchoring call according to configuration and the call’s properties (such as source, destination, IP Group, and SRD).

  • Page 331: Restricting Coders

    Allowed Coders list and the order of priority is first according to the Allowed Coders list. 20.4.6 Coder Transcoding The device can add coders, referred to as Extension coders to the SDP offer in the outgoing leg. Version 6.8 Mediant 2600 E-SBC...
  • Page 332 Mediant 2600 E-SBC For example, assume the following:  The SDP coder offer includes the following coders: G.729, G.711, and G.723.  The incoming leg includes the following Allowed coders: G.711 and G.729. The device selects the common coders, i.e., G.711 and G.729 (with changed preferred coder priority - highest for G.711).

  • Page 333: Prioritizing Coder List In Sdp Offer

    This is relevant when the MKI and Symmetric MKI parameters are enabled. In other words, both sides need to both encrypt and decrypt the outgoing and incoming SRTP packets, respectively. Channel (DSP) resources are not required for RTP and SRTP transcoding. Version 6.8 Mediant 2600 E-SBC...

  • Page 334: Multiple Rtp Media Streams Per Call Session

    Mediant 2600 E-SBC 20.4.9 Multiple RTP Media Streams per Call Session The device's SBC application supports multiple RTP media streams per SBC call session. Up to five different media types can be included in a session:  Audio (m=audio) ...

  • Page 335: Fax Negotiation And Transcoding

    You can define a maximum allowed duration (in minutes) for SBC calls. If an established call reaches this user-defined limit, the device terminates the call. This feature ensures calls are properly terminated, allowing available resources for new calls. This feature is configured using the MaxCallDuration parameter. Version 6.8 Mediant 2600 E-SBC...

  • Page 336: Sbc Authentication

    Mediant 2600 E-SBC 20.7 SBC Authentication The device can authenticate SIP servers and SBC users (clients). The different methods of support for this functionality is described in the following subsections. 20.7.1 SIP Authentication Server Functionality The device can function as an Authentication server for authenticating received SIP message requests, based on HTTP authentication Digest with MD5.

  • Page 337: User Authentication Based On Radius

    LAN and the new contact is on the WAN). In such a scenario, the device enables the user to reach the WAN contact and overcome NAT problems.  Enforce certain SBC policies (e.g., call admission control, header manipulation, and transcoding) on the resultant INVITE. Version 6.8 Mediant 2600 E-SBC...
  • Page 338 Mediant 2600 E-SBC The device enforces this by modifying each Contact in the 3xx response as follows:  Changes the host part to the device's IP address – this change causes the remote user agent to send the INVITE to the device.

  • Page 339: Local Handling Of Sip 3Xx

    HistoryInfoMode = Not present. History-Info History-Info added to Diversion. Disable converted to Diversion. DiversionMode = Add HistoryInfoMode = Add Diversion History-Info Headers are synced and sent. converted to converted to DiversionMode = Add History-Info. Diversion. Version 6.8 Mediant 2600 E-SBC...

  • Page 340: Interworking Sip Refer Messages

    Mediant 2600 E-SBC Parameter Value SIP Header Present in Received SIP Message HistoryInfoMode = Diversion removed. History-Info Both removed. Remove removed. DiversionMode = Remove 20.8.3 Interworking SIP REFER Messages The device supports interworking of SIP REFER messages. SIP UAs may support different versions of the REFER standard while others may not even support REFER.

  • Page 341: Interworking Sip Session Timer

    IP Profile parameters, 'SBC Remote Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Figure 20-7: SBC Early Media RTP 18x without SDP Version 6.8 Mediant 2600 E-SBC...
  • Page 342 Mediant 2600 E-SBC Figure 20-8: Early Media RTP - SIP 18x with SDP User's Manual Document #: LTRT-42060...

  • Page 343: Interworking Sip Re-Invite Messages

    The interworking of delayed offer is configured using the IP Profile parameter 'SBC Remote Delayed Offer Support'. Note: For this feature to function properly, a valid Extension Coders Group ID needs to be configured for IP Profiles that do not support delayed offer. Version 6.8 Mediant 2600 E-SBC...

  • Page 344: Interworking Call Hold

    Mediant 2600 E-SBC 20.8.11 Interworking Call Hold The device supports the interworking of call hold / retrieve requests between IP entities supporting different call hold capabilities:  Interworking SDP call hold formats. This is configured by the IP Profile parameter, 'SBC Remote Hold Format'.

  • Page 345: Call Survivability

    Below is an example of an XML body received from the BroadWorks server: <?xml version="1.0" encoding="utf-8"?> <BroadsoftDocument version="1.0" content="subscriberData"> <phoneNumbers> <phoneNumber>2403645317</phoneNumber> <phoneNumber>4482541321</phoneNumber> </phoneNumbers> <aliases> <alias>sip:bob@broadsoft.com</alias> <alias>sip:rhughes@broadsoft.com</alias> </aliases> <extensions> <extension>5317</extension> <extension>1321</extension> </extensions> </BroadSoftDocument> Version 6.8 Mediant 2600 E-SBC...

  • Page 346: Broadsoft's Shared Phone Line Call Appearance For Sbc Survivability

    Mediant 2600 E-SBC 20.9.2 BroadSoft's Shared Phone Line Call Appearance for SBC Survivability The device can provide redundancy for BroadSoft's Shared Call Appearance feature. When the BroadSoft application server switch (AS) fails or does not respond, or when the network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients.

  • Page 347: Call Survivability For Call Centers

    The SBC can handle a sequence of up to five users, after which the session is timed out and the call is dropped. Figure 20-11: Normal Operation in Call Center Application Version 6.8 Mediant 2600 E-SBC...
  • Page 348 Mediant 2600 E-SBC Figure 20-12: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Group table (see ''Configuring IP Groups'' on page 260), add IP Groups for the following entities: •...

  • Page 349: Survivability Mode Display On Aastra Ip Phones

    When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following XML body: Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument> Version 6.8 Mediant 2600 E-SBC...

  • Page 350: Call Forking

    Mediant 2600 E-SBC 20.10 Call Forking This section describes various Call Forking features supported by the device. 20.10.1 Initiating SIP Call Forking The SBC device supports call forking of an incoming call to multiple SBC users (destinations). Call forking is supported by the device's capability of registering multiple SIP client user phone contacts (mobile and fixed-line extensions) under the same Address of Record (AOR) in its registration database.

  • Page 351: Call Forking-Based Ip-To-Ip Routing Rules

    If the device does not receive a SIP ACK in response to this, it sends a new 200 OK to the next alternative destination. This new destination can be the next given IP address resolved from a DNS from the Contact or Record-Route header in the request related to the response. Version 6.8 Mediant 2600 E-SBC...
  • Page 352 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 353: Sbc Configuration

    (LAN), of the status of another SIP client in the LAN. For example, user B can subscribe to an application server for call pick-up service, whereby if user A's phone rings, the application server notifies user B. User B can then press a pre-configured key sequence to answer the call. Version 6.8 Mediant 2600 E-SBC...
  • Page 354 Mediant 2600 E-SBC The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself;...

  • Page 355: Configuring Admission Control

    SRD and its associated IP Groups are as follows:  SRD reserved call capacity: 40  IP Group ID 1 reserved call capacity: 10  IP Group ID 2 reserved call capacity: 20 Version 6.8 Mediant 2600 E-SBC...
  • Page 356 Mediant 2600 E-SBC In this setup, the SRD offers a shared pool for unreserved call capacity of 10 [i.e., 40 – (10 + 20)]. If IP Group ID 1 needs to handle 15 calls, it is guaranteed 10 calls and the remaining 5 is provided from the SRD's shared pool.
  • Page 357 CLI: limit-per-user user belonging to the specified IP Group or SRD. You can also [SBCAdmissionControl_LimitPer use the following special values: User]  [0] 0 = Block all these dialogs.  [-1] -1 = (Default) Unlimited. Version 6.8 Mediant 2600 E-SBC...
  • Page 358 Mediant 2600 E-SBC Parameter Description Rate Defines the rate (in seconds) at which tokens are added to the CLI: rate token bucket per second (i.e., token rate). [SBCAdmissionControl_Rate] The default is 0 (i.e., unlimited rate). Notes:  You must first configure the Maximum Burst parameter (see below) before configuring the Rate parameter.

  • Page 359: Configuring Allowed Audio Coder Groups

     To configure an Allowed Coders Group: Open the Allowed Audio Coders Group page (Configuration tab > VoIP menu > SBC > Allowed Audio Coders Group). Figure 21-4: Allowed Audio Coders Group Page Version 6.8 Mediant 2600 E-SBC...

  • Page 360: Configuring Allowed Video Coder Groups

    Mediant 2600 E-SBC Configure an Allowed Audio Coders Group according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 21-2: Allowed Audio Coders Group Table Parameter Descriptions...

  • Page 361: Routing Sbc

    Proxy Set. The Proxy Set is assigned to the IP Group in the IP Group table. If classification based on Proxy Set fails (or classification based on Proxy Set is disabled), the device proceeds to classification based on the Classification table. Version 6.8 Mediant 2600 E-SBC...
  • Page 362 Mediant 2600 E-SBC Note: • For security, it is recommended to classify SIP dialogs based on Proxy Set only if the IP address of the Server-type IP Group is unknown. In other words, if the Proxy Set associated with the IP Group is configured with an FQDN. In such cases, the device classifies incoming SIP dialogs to the IP Group based on the DNS-resolved IP address.
  • Page 363 The following procedure describes how to configure Classification rules in the Web interface. You can also configure Classification rules using the table ini file parameter, Classification or CLI command, configure voip > sbc routing classification. Version 6.8 Mediant 2600 E-SBC...
  • Page 364 Mediant 2600 E-SBC  To configure a Classification rule: Open the Classification Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Click Add; the following dialog box appears: Figure 21-6: Classification Table Page Configure the Classification rule according to the parameters described in the table below.
  • Page 365 URI, see ''SIP Dialog Initiation Process'' on page 321. The default is the asterisk (*) symbol, which represents any source host prefix. Note: For REGISTER requests, the source URL is obtained from the To header. Version 6.8 Mediant 2600 E-SBC...

  • Page 366: Classification Based On Uri Of Selected Header Example

    Mediant 2600 E-SBC Parameter Description Destination Username Prefix Defines the prefix of the destination Request-URI user part CLI: dst-user-name-prefix of the incoming SIP dialog. [Classification_DestUsernamePrefi The default is the asterisk (*) symbol, which represents any destination username. The prefix can be a single digit or a range of digits.

  • Page 367: Configuring Message Condition Rules

    The following procedure describes how to configure Message Condition rules in the Web interface. You can also configure Message Condition rules using the table ini file parameter, ConditionTable or CLI command, configure voip > sbc routing condition-table. Version 6.8 Mediant 2600 E-SBC...

  • Page 368: Configuring Sbc Ip-To-Ip Routing

    Mediant 2600 E-SBC  To configure a Message Condition rule: Open the Message Condition Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Message Condition Table). Click Add; the following dialog box appears: Figure 21-7: Condition Table Page - Add Record Dialog Box Configure a Message Condition rule according to the parameters described in the table below.
  • Page 369 Alternative routing or load balancing: In addition to the alternative routing/load balancing provided by the Proxy Set associated with the destination IP Group, the table allows the configuration of alternative routes whereby if a route fails, the next Version 6.8 Mediant 2600 E-SBC...
  • Page 370 Mediant 2600 E-SBC adjacent (below) rule in the table that is configured as 'Alt Route Ignore/Consider Inputs' are used. The alternative routes rules can be set to enforce the input matching criteria or to ignore any matching criteria. Alternative routing occurs upon one of the following conditions: •...
  • Page 371 IP2IPRouting or CLI command, configure voip > sbc routing ip2ip-routing.  To configure an IP-to-IP routing rule: Open the IP-to-IP Routing Table page (Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table). Version 6.8 Mediant 2600 E-SBC...
  • Page 372 Mediant 2600 E-SBC Click Add; the following dialog box appears: Figure 21-10: IP-to-IP Routing Table - Add Record Dialog Box Configure an IP-to-IP routing rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
  • Page 373 Defines the SIP dialog request type of the incoming SIP [IP2IPRouting_RequestType] dialog. CLI: request-type  [0] All (default)  [1] INVITE  [2] REGISTER  [3] SUBSCRIBE  [4] INVITE and REGISTER  [5] INVITE and SUBSCRIBE  [6] OPTIONS Version 6.8 Mediant 2600 E-SBC...
  • Page 374 Mediant 2600 E-SBC Parameter Description Message Condition Assigns a SIP message Condition rule. To configure [IP2IPRouting_MessageCondition] Condition rules, see ''Configuring Message Condition Rules'' CLI: message-condition on page 367. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect [IP2IPRouting_ReRouteIPGroupID] response (e.g., 3xx) or REFER message.
  • Page 375 The default is -1. Notes:  This parameter is only relevant if the parameter 'Destination Type' is set to IP Group. However, regardless of the settings of the parameter 'Destination Version 6.8 Mediant 2600 E-SBC...
  • Page 376 Mediant 2600 E-SBC Parameter Description Type', the IP Group is still used - only for determining the IP Profile or outgoing SRD. If neither IP Group nor SRD are defined in this table, the destination SRD is determined according to the source SRD associated with the Source IP Group (configured in the IP Group table, see ''Configuring IP Groups'' on page 260).
  • Page 377 ‘SBC Alternative Routing Reasons’ table.  Multiple alternative route entries can be configured (e.g., Index 1 is the main route - Route Row - and indices 2 through 4 are configured as alternative routes). Version 6.8 Mediant 2600 E-SBC...

  • Page 378: Configuring Sip Response Codes For Alternative Routing Reasons

    Mediant 2600 E-SBC Parameter Description Group Policy Defines whether the routing rule includes call forking. CLI: group-policy  [0] None (default) = Call uses only this route (even if [IP2IPRouting_GroupPolicy] Forking Group members are configured in the rows below it).
  • Page 379 Table 21-7: SBC Alternative Routing Reasons Table Parameter Descriptions Parameter Description Index Defines an index number for the new table [SBCAlternativeRoutingReasons_Index] record. Release Cause Defines a SIP response code for triggering the CLI: rel-cause device's alternative routing mechanism. [SBCAlternativeRoutingReasons_ReleaseCause] Version 6.8 Mediant 2600 E-SBC...

  • Page 380: Sbc Manipulations

    Mediant 2600 E-SBC 21.6 SBC Manipulations This section describes the configuration of the manipulation rules for the SBC application. Note: For additional manipulation features, see the following: • ''Configuring SIP Message Policy Rules''. • ''Configuring SIP Message Manipulation'' on page 284.
  • Page 381  Inbound source SIP URI user name from "7000" to "97000": From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe  Source IP Group name (i.e., SIP URI host name) from "10.2.2.6" to "IP_PBX": From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe Version 6.8 Mediant 2600 E-SBC...

  • Page 382: Configuring Ip-To-Ip Inbound Manipulations

    Mediant 2600 E-SBC  Inbound destination SIP URI user name from "1000" to 9721000": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone>...
  • Page 383  [1] Routing input only = Inbound manipulations affect the routing input only, retaining the original source and destination number.  [2] Shared Line = Used for the Shared-Line Appearance Version 6.8 Mediant 2600 E-SBC...
  • Page 384 Mediant 2600 E-SBC Parameter Description feature. This manipulation is for registration requests to change the destination number of the secondary extension numbers to the primary extension. For more information, see ''BroadSoft's Shared Phone Line Call Appearance for SBC Survivability'' on page 346.

  • Page 385: Configuring Ip-To-Ip Outbound Manipulations

    SIP URI host name (source and destination) manipulations can also be configured in the IP Group table. These manipulations are simply host name substitutions with the names configured for the source and destination IP Groups, respectively. Version 6.8 Mediant 2600 E-SBC...
  • Page 386 Mediant 2600 E-SBC The following procedure describes how to configure IP-to-IP Outbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPOutboundManipulation or CLI command, configure voip > sbc manipulations ip- outbound-manipulation.
  • Page 387 Defines the SIP request type to which the manipulation rule is CLI: request-type applied. [IPOutboundManipulation_Requ  [0] All = (Default) all SIP messages. estType]  [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.  [2] REGISTER = Only SIP REGISTER messages. Version 6.8 Mediant 2600 E-SBC...
  • Page 388 Mediant 2600 E-SBC Parameter Description  [3] SUBSCRIBE = Only SIP SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect CLI: re-route-ip-group-id response (e.g., 3xx) or REFER message.
  • Page 389 Restriction is done only after user number manipulation (if any).  The device identifies an incoming user as restricted if one of the following exists:  From header user is "anonymous".  P-Asserted-Identity and Privacy headers contain the value "id". Version 6.8 Mediant 2600 E-SBC...
  • Page 390 Mediant 2600 E-SBC Parameter Description User's Manual Document #: LTRT-42060...

  • Page 391: Cloud Resilience Package

    Part VI Cloud Resilience Package...

  • Page 393: Crp Overview

    Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
  • Page 394 Mediant 2600 E-SBC Survivability Quality of Experience/Service Security  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications)  Call waiting (if supported by IP phone) One of the main advantages of CRP is that it enables quick-and-easy configuration.

  • Page 395: Crp Configuration

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'CRP Application' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 2600 E-SBC...

  • Page 396: Configuring Call Survivability Mode

    Mediant 2600 E-SBC 23.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.

  • Page 397: Pre-Configured Ip Groups

    The IP Groups can be edited, except for the fields listed above, which are read-only. • For accessing the IP Group table and for a description of its parameters, see ''Configuring IP Groups'' on page 260. Version 6.8 Mediant 2600 E-SBC...

  • Page 398: Pre-Configured Ip-To-Ip Routing Rules

    Mediant 2600 E-SBC 23.4 Pre-Configured IP-to-IP Routing Rules For the CRP application, the IP-to-IP Routing table is pre-configured with IP-to-IP routing rules. These rules depend on the configured Call Survivability mode, as described in ''Configuring Call Survivability Mode'' on page 396.

  • Page 399: Emergency Mode

    For the routing rule of Index 2, the destination is the source IP Group (i.e., from where the REGISTER message was received). Index 7 appears only if the CRPGatewayFallback parameter is enabled (see Configuring PSTN Fallback on page 400). Version 6.8 Mediant 2600 E-SBC...

  • Page 400: Configuring Pstn Fallback

    Mediant 2600 E-SBC 23.5 Configuring PSTN Fallback You can enable the CRP to route emergency calls (or PSTN-intended calls) such as "911" from the Proxy server (IP Group 2) to the PSTN (IP Group 3). In addition, for calls from the...

  • Page 401: High Availability System

    Part VII High Availability System...

  • Page 403: Ha Overview

    Once loaded to the redundant device, the redundant device reboots to apply the new configuration and/or software. Thus, under normal operation, one of the devices is in active state while the other is in redundant state, where both devices share the same configuration and software. Any Version 6.8 Mediant 2600 E-SBC...

  • Page 404: Device Switchover Upon Failure

    Mediant 2600 E-SBC subsequent configuration update or software upgrade on the active device is also done on the redundant device. In the active device, all logical interfaces (i.e., Media, Control, OAMP, and Maintenance) are active. In the redundant device, only the Maintenance interface is active, which is used for connectivity to the active device.

  • Page 405: Ha Status On The Home Page

    In the 'HA Device Name' field, enter a name for the active device. Click Submit. Note: Once the devices are running in HA mode, you can change the name of the redundant device, through the active device only, in the 'Redundant HA Device Name' field. Version 6.8 Mediant 2600 E-SBC...
  • Page 406 Mediant 2600 E-SBC The Home page also displays the HA operational status of the device to which you are currently logged in. This is displayed in the 'High Availability' field under the General Information pane:  "Not Operational": HA is not configured or the installed Software License Key does not include the HA feature ...

  • Page 407: Ha Configuration

     For Geographical HA (both units are located far from each other), 2Rx/1Tx port mode connected to a port aggregation switch is the recommended option: Figure 25-1: Rx/Tx Mode for Geographical HA Version 6.8 Mediant 2600 E-SBC...

  • Page 408: Configuring The Ha Devices

    Mediant 2600 E-SBC  If the Maintenance ports of both devices are connected directly to each other without intermediation of switches, configure the mode to 2RX/1TX: Figure 25-2: Rx/Tx Mode for Direct Connection  If the two devices are connected through two (or more) isolated LAN switches (i.e.,...

  • Page 409: Step 1: Configure The First Device

    Make sure that the MAINTENANCE interface uses an Ethernet Port Group that is not used by any other network interface. The Ethernet Port Group is associated with the Ethernet Device assigned to the interface in the 'Underlying Interface' field. Version 6.8 Mediant 2600 E-SBC...
  • Page 410 Mediant 2600 E-SBC The Interface table below shows an example where the Maintenance interface is assigned to Ethernet Device "vlan 2" (which is associated with Ethernet Port Group "GROUP_2") in the 'Underlying Device' field, while the other interface is assigned to "vlan 1"...

  • Page 411: Step 2: Configure The Second Device

    Enable and then setting the priority level of this second device in the 'HA Priority' field. Burn the configuration to flash without a reset. Power down the device. Continue to ''Step 3: Initialize HA on the Devices'' on page for completing the HA configuration. Version 6.8 Mediant 2600 E-SBC...

  • Page 412: Step 3: Initialize Ha On The Devices

    Mediant 2600 E-SBC 25.1.2.3 Step 3: Initialize HA on the Devices Once you have configured both devices for HA as described in the previous sections, follow the procedure below to complete and initialize HA so that the devices become operational in HA. This last stage applies to both devices.

  • Page 413: Configuration While Ha Is Operational

    TCP source and destination port IDs are not symmetric.  HTTP protocol for file transferring (e.g., Rule #7 in the figure below).  HTTP protocol for file transferring after switchover (e.g., Rule #8 - same as Rule #7 - in the figure below). Version 6.8 Mediant 2600 E-SBC...
  • Page 414 Mediant 2600 E-SBC The figure below displays an example of the required firewall rules. In this example, 10.31.4.61 is the Maintenance interface of the redundant device and 10.31.4.62 is the Maintenance interface of the active device. "HA_IF" is the name of the Maintenance interface.

  • Page 415: Monitoring Ip Entity And Ha Switchover Upon Ping Failure

    Click Submit. If this feature is operational, the status of the connectivity to the pinged destination is displayed in the read-only 'Monitor Destination Status' field:  “Enabled": Ping is sent as configured. Version 6.8 Mediant 2600 E-SBC...
  • Page 416 Mediant 2600 E-SBC  "Disabled by configuration and HA state": HA and ping are not configured.  "Disabled by HA state": same as above.  "Disabled by configuration”: same as above.  “Disabled by invalid configuration": invalid configuration, for example, invalid interface name or destination address (destination address must be different than a local address and from the redundant device's Maintenance address).

  • Page 417: Ha Maintenance

    The previously active device burns and resets with the new software version. The previously active device switches over to become the active device. For more information on upgrading the software, see ''Software Upgrade Wizard'' on page 444. Version 6.8 Mediant 2600 E-SBC...
  • Page 418 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 419: Maintenance

    Part VIII Maintenance...

  • Page 421: Basic Maintenance

    Description'' on page 38) to indicate that a device reset is required. • After you reset the device, the Web GUI is displayed in Basic view (see ''Displaying Navigation Tree in Basic and Full View'' on page 39). Version 6.8 Mediant 2600 E-SBC...
  • Page 422 Mediant 2600 E-SBC  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 421). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: • Yes: The device's current configuration is saved (burned) to the flash memory prior to reset (default).

  • Page 423: Remotely Resetting Device Using Sip Notify

    Under the Misc Parameters group, set the 'SIP Remote Rest' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. 27.3 Locking and Unlocking the Device The Lock and Unlock option allows you to lock the device so that it doesn't accept any new calls and maintains only the current calls.

  • Page 424: Saving Configuration

    Mediant 2600 E-SBC Click the LOCK button; a confirmation message box appears requesting you to confirm device lock. Figure 27-4: Device Lock Confirmation Message Box Click OK to confirm device lock; if you set 'Graceful Option' to Yes, a lock icon is delayed and a window appears displaying the number of remaining calls and time.

  • Page 425: High Availability Maintenance

    Toolbar: Click the Device Actions button, and then choose Switch Over Figure 28-1: High Availability Maintenance Page Under the 'Switch Over' group, click Switch Over; a confirmation box appears requesting you to confirm. Click OK. Version 6.8 Mediant 2600 E-SBC...

  • Page 426: Resetting The Redundant Unit

    Mediant 2600 E-SBC 28.2 Resetting the Redundant Unit You can reset the Redundant device, if necessary. Note: When resetting the Redundant device, the HA mode becomes temporarily unavailable.  To reset the Redundant device: Open the High Availability Maintenance page: •...

  • Page 427: Disconnecting Active Calls

    Session ID. This is done in the CLI using the following commands (from basic command mode):  Disconnects all active calls: # clear voip calls  Disconnects active calls belonging to a specified Session ID: # clear voip calls <Session ID> Version 6.8 Mediant 2600 E-SBC...
  • Page 428 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 429: Software Upgrade

    ''Locking and Unlocking the Device'' on page 423. • For deleting auxiliary files, see ''Viewing Device Information'' on page 473. Version 6.8 Mediant 2600 E-SBC...

  • Page 430: Call Progress Tones File

    AudioCodes DConvert utility. For a description on converting a CPT ini file into a binary dat file, refer to the DConvert Utility User's Guide.
  • Page 431 Low Freq Level [-dBm]: Generation level 0 dBm to -31 dBm in dBm (not relevant to AM tones). • High Freq Level: Generation level of 0 to -31 dBm. The value should be set to 32 in the case of a single tone (not relevant to AM tones). Version 6.8 Mediant 2600 E-SBC...
  • Page 432 Mediant 2600 E-SBC • First Signal On Time [10 msec]: 'Signal On' period (in 10 msec units) for the first cadence on-off cycle. For continuous tones, this parameter defines the detection period. For burst tones, it defines the tone's duration.

  • Page 433: Prerecorded Tones File

    Up to 40 tones (totaling approximately 10 minutes) can be stored in a single PRT file on the device's flash memory. The prerecorded tones are prepared offline using standard third-party recording utilities and combined into a single file, using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).

  • Page 434: Dial Plan Prefix Tags For Routing

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Load the converted file to the device, as described in ''Loading Auxiliary Files'' on page 429.
  • Page 435 Click the Action tab, and then in the 'Remove from Left' or 'Remove from Right' fields (depending on whether you added the tag at the beginning or end of the URI user part, respectively), enter the number of characters making up the tag. Version 6.8 Mediant 2600 E-SBC...

  • Page 436: Obtaining Ip Destination From Dial Plan File

    Mediant 2600 E-SBC 30.1.3.3 Obtaining IP Destination from Dial Plan File You can use a Dial Plan index listed in a loaded Dial Plan file for determining the IP destination of SBC calls. This enables the mapping of called numbers to IP addresses (in dotted-decimal notation) or FQDNs (up to 15 characters).
  • Page 437 The valid value is a string of up to 10 characters. Username Defines the username for registering the user when [SBCUserInfoTable_Username] authentication is necessary. The valid value is a string of up to 40 characters. Version 6.8 Mediant 2600 E-SBC...
  • Page 438 Mediant 2600 E-SBC Parameter Description Password Defines the password for registering the user when authentication [SBCUserInfoTable_Password] is necessary. The valid value is a string of up to 20 characters. IP Group ID Defines the IP Group ID to which the user belongs and is used as [SBCUserInfoTable_IPGroupID] the Request-URI source host part for the AOR in the database.
  • Page 439 URI source host part for the AOR in the database Note: To modify the SBC User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Version 6.8 Mediant 2600 E-SBC...

  • Page 440: Software License Key

    Before you can install a new Software License Key, you need to obtain a Software License Key file for your device with the required features from your AudioCodes representative. The Software License Key is an encrypted key in string format that is associated with the device's serial number ("S/N") and supplied in a text-based file.

  • Page 441: Installing The Software License Key

    CLI - see Installing Software License Key using CLI on page  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non- volatile flash memory and overwrites the previously installed Software License Key.
  • Page 442 Mediant 2600 E-SBC Back up the Software License Key currently installed on the device, as a precaution. If the new Software License Key does not comply with your requirements, you can re- load this backup to restore the device's original capabilities.

  • Page 443: Installing Software License Key Using Cli

    Open the Software License Key file and check that the "S/N" line appears. If it does not appear, contact AudioCodes. Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]".

  • Page 444: Software Upgrade Wizard

    Mediant 2600 E-SBC 30.3 Software Upgrade Wizard The Web interface's Software Upgrade Wizard lets you easily upgrade the device's software version (.cmp file). The wizard also provides you the option to load other files such as an ini file and auxiliary files (e.g., Call Progress Tone / CPT file). However, loading a .cmp file is mandatory through the wizard and before you can load any other type of file,...
  • Page 445 If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
  • Page 446 Mediant 2600 E-SBC • On the toolbar, click Device Actions, and then choose Software Upgrade Wizard. Figure 30-3: Start Software Upgrade Wizard Screen Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Figure 30-4: Software Upgrade Wizard - Load CMP File...
  • Page 447 If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file running on the device) and thereby, overwrite values previously configured for these parameters. Version 6.8 Mediant 2600 E-SBC...
  • Page 448 Mediant 2600 E-SBC • Retain the existing configuration (default): Select the 'Use existing configuration' check box to use the current configuration (and do not select an ini file). • Restore configuration to factory defaults: Clear the 'Use existing configuration' check box (and do not select an ini file).

  • Page 449: Backing Up And Loading Configuration File

    # copy cli-script to <URL of TFTP/HTTP/HTTPS server> For example:  Remote server: # copy cli-script to tftp://192.168.0.3/config-device1.txt Note: When loading an ini file using the Configuration File page, parameters not included in the ini file are reset to default settings. Version 6.8 Mediant 2600 E-SBC...
  • Page 450 Mediant 2600 E-SBC  To save or load an ini file: Open the Configuration File page by doing one of the following: • From the Navigation tree, click the Maintenance tab, click the Software Update menu, and then click Configuration File.

  • Page 451: Automatic Update Mechanism

    To activate the DHCP process, reset the device. The following shows an example of a configuration file for a Linux DHCP server (dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to Version 6.8 Mediant 2600 E-SBC...

  • Page 452: Provisioning From Http Server Using Dhcp Option 67

    Mediant 2600 E-SBC 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server" directive may be used). ddns-update-style ad-hoc; default-lease-time 60; max-lease-time 60; class "gateways" { match if(substring(hardware, 1, 3) = 00:90:8f); subnet 10.31.0.0 netmask 255.255.0.0 { pool { allow members of "audiocodes";...

  • Page 453: Provisioning From Tftp Server Using Dhcp Option 66

    This method is suitable when the network in which the device is deployed contains a provisioning TFTP server for all network equipment, without being able to distinguish between AudioCodes and non-AudioCodes devices. Upon startup, the device searches for Option 66 in the DHCP response from the DHCP server.

  • Page 454: Ftp-Based Provisioning

    URL is "ftp" (instead of "http"). 31.1.6 Provisioning using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections.

  • Page 455: Http/S-Based Provisioning Using The Automatic Update Feature

    URL address of the provisioning server where the file is located. For a description of the parameters used to configure URLs per file, see Automatic Update Parameters. Below are examples for configuring the file names and their URLs for Automatic Update: Version 6.8 Mediant 2600 E-SBC...

  • Page 456: Triggers For Automatic Update

    Upon receipt of an SNMP request from the provisioning server. • Upon receipt of a special SIP NOTIFY message from the provisioning server. The NOTIFY message includes an Event header with the AudioCodes proprietary value, "check-sync;reboot=false", as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...

  • Page 457: Access Authentication With Http Server

    • <MAC> - device's MAC address • <VER> - software version currently installed on the device, e.g., "6.80.200.001" • <CONF> - configuration version, as configured in the ini file parameter, INIFileVersion or CLI command, configuration-version Version 6.8 Mediant 2600 E-SBC...
  • Page 458 Mediant 2600 E-SBC The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld-<NAME>;<VER>(<MAC>), the device sends the following User-Agent header: User-Agent: MyWorld-Mediant;6.8.200.001(00908F1DD0D3)

  • Page 459: File Download Sequence

    Periodic software file (.cmp) download One-time software file (.cmp) download Auxiliary file(s) The following files automatically instruct the device to reset:  Periodic software file (.cmp)  One-time software file (.cmp) Version 6.8 Mediant 2600 E-SBC...

  • Page 460: Cyclic Redundancy Check On Downloaded Configuration Files

    Mediant 2600 E-SBC When multiple files requiring a reset are downloaded, the device resets only after it has downloaded and installed all the files. However, you can explicitly instruct the device to immediately reset for the following files:  ini file: Use the ResetNow in file parameter...

  • Page 461: Mac Address Automatically Inserted In Configuration File Name

    (e.g., http://www.company.com) that is used in the URL of the provisioning server. You configure this in the Interface table: • ini File: [ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, Version 6.8 Mediant 2600 E-SBC...

  • Page 462: Automatic Update From Remote Servers

    Mediant 2600 E-SBC InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] • CLI: # configure voip (config-voip)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100 Configure the device with the following Automatic Update settings: Automatic Update is done every 24 hours (1440 minutes): ♦...
  • Page 463 "root" and password "wheel".  HTTP server at www.company.com for storing the ini configuration file.  DNS server at 80.179.52.100 for resolving the domain names of the provisioning servers (FTPS and HTTP). Version 6.8 Mediant 2600 E-SBC...
  • Page 464 Mediant 2600 E-SBC  To set up Automatic Provisioning for files stored on different server types (example): VP file: Set up an FTPS server and copy the VP file to the server. Configure the device with the URL path of the VP file: VPFileUrl = 'ftps://root:wheel@ftpserver.corp.com/vp.dat'...

  • Page 465: Automatic Update For Mass Deployment

    Copy the master_configuration.ini file as well as the CPT and .cmp files to the HTTP- based provisioning server. Configure each device with the following: URL of the master_configuration.ini file for Automatic Update: ♦ ini File: IniFileURL = 'http://www.company.com/master_configuration.ini' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# voice-configuration 'http://www.company.com/master_configuration.ini' Version 6.8 Mediant 2600 E-SBC...
  • Page 466 Mediant 2600 E-SBC Configure the device with the IP address of the DNS server for resolving the domain name (e.g., http://www.company.com) that is used in the URL for the provisioning server. This is done in the Interface table: ♦ ini File:...

  • Page 467: Restoring Factory Defaults

    # enable At the prompt, type the password again, and then press Enter: # Password: Admin At the prompt, type the following to reset the device to default settings, and then press Enter: # write factory Version 6.8 Mediant 2600 E-SBC...

  • Page 468: Restoring Defaults Using An Ini File

    Mediant 2600 E-SBC 32.2 Restoring Defaults using an ini File You can restore the device to factory default settings by loading an empty ini file to the device. This is done using the Web interface's Configuration File page (see ''Backing Up and Loading Configuration File'' on page 449).

  • Page 469: Saving Current Configuration To A File And Sending It To Remote Destination

    HTTP/S). The configuration settings in the file are based only on CLI commands. This is done through CLI:  Creating a Configuration file and saving it on a remote server: # write-and-backup to <URL path with file name> For example: # write-and-backup to tftp://192.168.0.3/config-device1.txt Version 6.8 Mediant 2600 E-SBC...
  • Page 470 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 471: Status, Performance Monitoring And Reporting

    Part IX Status, Performance Monitoring and Reporting...

  • Page 473: System Status

    To delete a loaded file:  Click the Delete button corresponding to the file that you want to delete. Deleting a file takes effect only after device reset (see ''Resetting the Device'' on page 421). Version 6.8 Mediant 2600 E-SBC...

  • Page 474: Viewing Ethernet Port Information

    Mediant 2600 E-SBC 34.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information about the Ethernet Port Group connections.  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu >...

  • Page 475: Performance Monitoring

    As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 2600 E-SBC...

  • Page 476: Viewing Quality Of Experience

    Mediant 2600 E-SBC 35.2 Viewing Quality of Experience The Quality Of Experience page provides statistical information on calls per SRD or IP Group. The statistics can be further filtered to display incoming and/or outgoing call direction, and type of SIP dialog (INVITE, SUBSCRIBE, or all).

  • Page 477: Viewing Average Call Duration

    Figure 35-3: Average Call Duration Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view information for an SRD or IP Group. From the 'Index' drop-down list, select the SRD or IP Group index. Version 6.8 Mediant 2600 E-SBC...
  • Page 478 Mediant 2600 E-SBC Use the Zoom In button to increase the displayed time resolution or the Zoom Out button to decrease it. Instead of using these zoom buttons, you can use the slide ruler. As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds;...

  • Page 479: Carrier-Grade Alarms

    The Alarms History page displays a list of alarms that have been raised and traps that have been cleared.  To view the list of history alarms:  Open the Alarms History page (Status & Diagnostics tab > System Status menu > Carrier-Grade Alarms > Alarms History). Version 6.8 Mediant 2600 E-SBC...
  • Page 480 Mediant 2600 E-SBC For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised ...

  • Page 481: Voip Status

    "Active": Static route is used by the device.  "Inactive": Static route is not used. When the destination IP address is not on the same segment with the next hop, or the interface does not exist, the route state changes to "Inactive". Version 6.8 Mediant 2600 E-SBC...

  • Page 482: Viewing Registered Users

    Mediant 2600 E-SBC  To view the status of static IP routing:  Open the IP Routing Status Table page (Status & Diagnostics tab > VoIP Status menu >Static Route Status). Figure 37-1: IP Routing Status Table Page 37.4 Viewing Registered Users You can view SBC users listed in the device's Users Registration database.

  • Page 483: Viewing Registration Status

    Open the Active Proxy Set Status page (Monitor menu > Monitor tab > VoIP Status folder > Proxy Sets Status). Figure 37-3: Viewing Proxy Sets Status Table 37-1: Proxy Sets Status Table Description Parameter Description Proxy Set ID Displays the Proxy Set ID. Version 6.8 Mediant 2600 E-SBC...
  • Page 484 Mediant 2600 E-SBC Parameter Description Mode Displays the Proxy Sets' operational mode:  "Parking" or "Homing": Redundancy mode, as configured by the ProxySet_ProxyRedundancyMode parameter.  "Load Balancing: Proxy load balancing mode, as configured by the ProxySet_ProxyRedundancyMode parameter. For more information, see Configuring Proxy Sets.

  • Page 485: Reporting Information To External Party

    Start Timestamp Stop Timestamp Call-ID Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Version 6.8 Mediant 2600 E-SBC...
  • Page 486 Mediant 2600 E-SBC Group Metric Name Silence Suppression State Jitter Buffer Jitter Buffer Adaptive Jitter Buffer Rate Jitter Buffer Nominal Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Gap Loss...
  • Page 487 LocalMAC: 00:90:8f:2e:3c:67 LocalMetrics: Timestamps: START=2012-04-28T15:58:36Z STOP=2012-04- 28T15:58:36Z SessionDesc: PT=8 PD=PCMA SR=8000 FD=20 PLC=3 SSUP=Off JitterBuffer: JBA=3 JBR=0 JBN=0 JBM=0 JBX=300 PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=0 GMIN=16 Delay: RTD=0 ESD=0 QualityEst: DialogID:13746175212842012155835@10.8.61.16;to- tag=1c252030485; from-tag=1c1374725246 Version 6.8 Mediant 2600 E-SBC...
  • Page 488 Mediant 2600 E-SBC  To configure RTCP XR: Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). The RTCP XR parameters are listed under the RTCP XR Settings group: Figure 38-1: RTCP XR Parameters in RTP/RTCP Settings Page Under the RTCP XR Settings group, configure the following: •...

  • Page 489: Generating Call Detail Records

    OK responses (call connect) and BYE messages (call end). If you want to enable the generation of CDRs for non-call SIP dialogs (such as SUBSCRIBE, OPTIONS, and REGISTER), use the EnableNonCallCdr parameter. 38.2.2 CDR Field Description This section describes the CDR fields that are generated by the device. Version 6.8 Mediant 2600 E-SBC...

  • Page 490: Cdr Fields For Sbc Signaling

    Mediant 2600 E-SBC 38.2.2.1 CDR Fields for SBC Signaling The CDR fields for SBC signaling are listed in the table below. A typical SBC session consists of two SBC legs. Each leg generates its own signaling CDRs. Each leg generates three CDR types: at call start (SBCReportType=CALL_START),...
  • Page 491 String of up to 35 characters ConnectTime Call connect time String of up to 35 characters ReleaseTime Call release time String of up to 35 characters RedirectReason Redirect reason String of up to 15 characters Version 6.8 Mediant 2600 E-SBC...
  • Page 492 Mediant 2600 E-SBC CDR Field Name Description Format RedirectURINum Redirection URI String of up to 41 characters RedirectURINumBeforeMap Redirect URI number before manipulation String of up to 41 characters TxSigIPDiffServ Signaling IP DiffServ String of up to 15 characters IPGroup...

  • Page 493: Cdr Fields For Sbc Media

    Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable. LocalMosCQ Local MOS for conversation RemoteMosCQ Remote MOS for conversation Version 6.8 Mediant 2600 E-SBC...

  • Page 494: Configuring Radius Accounting

    Mediant 2600 E-SBC CDR Field Name Description TxRTPIPDiffServ Media IP DiffServ LatchedRtpIp Remote IP address of the incoming RTP stream that the device "latched" on to as a result of the RTP latching mechanism for NAT traversal. LatchedRtpPort Remote RTP port of the incoming RTP stream that the device "latched"...
  • Page 495 Stop h323- Connect time in String h323-connect- Stop connect-time NTP format time=09:33:37.657 UTC Mon Dec 08 2015 h323- Disconnect time in String Stop disconnect- NTP format time Version 6.8 Mediant 2600 E-SBC...
  • Page 496 Mediant 2600 E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID h323- Disconnect cause Numeric h323-disconnect- Stop disconnect- code (Q.850) cause=16 cause h323-gw-id Name of the String h323-gw-id=<SIP Start gateway ID string> Stop sip-call-id SIP Call ID...
  • Page 497 Stop Response Attributes h323-return- The reason for Numeric 0 Request accepted Stop code failing authentication (0 = ok, other number failed) acct- (Standard) A unique accounting String Stop identifier – match Version 6.8 Mediant 2600 E-SBC...
  • Page 498 Mediant 2600 E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID session-id start & stop Below is an example of RADIUS Accounting, where the non-standard parameters are preceded with brackets: Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213...

  • Page 499: Diagnostics

    Part X Diagnostics...

  • Page 501: Syslog And Debug Recordings

    Syslog message, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: Version 6.8 Mediant 2600 E-SBC...

  • Page 502: Event Representation In Syslog Messages

    Mediant 2600 E-SBC Message Item Description [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237][SID:1034099026] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE:...
  • Page 503 No Available Release Descriptor RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Invalid Header Length Invalid Codec Type Unknown Aggregation Payload Type Invalid Routing Flag Received Version 6.8 Mediant 2600 E-SBC...

  • Page 504: Identifying Audiocodes Syslog Messages Using Facility Levels

    Mediant 2600 E-SBC 39.1.2 Identifying AudioCodes Syslog Messages using Facility Levels The device’s Syslog messages can easily be identified and distinguished from Syslog messages from other equipment, by setting its Facility level. The Facility levels of the device's Syslog messages are numerically coded with decimal values. Facility level may use any of the "local use"...

  • Page 505: Enabling Syslog

    DebugLevelHighThreshold: Defines the threshold (in percentage) for automatically switching to a different debug level, depending on CPU usage. For more information about this functionality, refer to the parameter's description in Syslog, CDR and Debug Parameters on page 560. Click Submit. Version 6.8 Mediant 2600 E-SBC...

  • Page 506: Configuring Web Operations To Report To Syslog

    Mediant 2600 E-SBC 39.3 Configuring Web Operations to Report to Syslog You can define the operations (activities) in the Web interface that must be reported to the Syslog server. The following procedure describes how to configure this in the Web interface.

  • Page 507: Configuring Debug Recording

    The following procedure describes how to configure Logging Filter rules in the Web interface. You can also configure Logging Filter rules using the table ini file parameter, LoggingFilters or the CLI command configure system > logging > logging-filters. Version 6.8 Mediant 2600 E-SBC...
  • Page 508 Mediant 2600 E-SBC  To configure a logging filtering rule: Open the Logging Filters Table page (Configuration tab > System menu > Logging > Logging Filters Table). Click Add; the following dialog box appears: Figure 39-4: Logging Filters Table - Add Record Dialog Box Configure a logging filter according to the parameters described in the table below.

  • Page 509: Filtering Ip Network Traces

    IP protocol type (PDU) entered as an enumeration value (e.g., 1 is ICMP, 6 is TCP, 17 is UDP) udp, tcp, icmp, sip, ldap, http, https Single expressions for protocol type udp.port, tcp.port Transport layer Version 6.8 Mediant 2600 E-SBC...

  • Page 510: Viewing Syslog Messages

    • You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting. User's Manual...
  • Page 511 Blue - recoverable error message (i.e., non-fatal error) • Black - notice message  To stop and clear the Message Log:  Close the Message Log page by accessing any another page in the Web interface. Version 6.8 Mediant 2600 E-SBC...

  • Page 512: Collecting Debug Recording Messages

    Mediant 2600 E-SBC 39.7 Collecting Debug Recording Messages To collect debug recording packets, use the open source program Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...

  • Page 513: Debug Capturing On Physical Voip Interfaces

    TFTP or FTP server: # debug capture voip physical stop <TFTP/FTP server IP address> If no IP address is defined, the capture is saved on the device for later retrieval. Version 6.8 Mediant 2600 E-SBC...
  • Page 514 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 515: Creating Core Dump And Debug Files Upon Device Crash

    The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. The files can then be sent to AudioCodes support team for troubleshooting. ...
  • Page 516 Mediant 2600 E-SBC The following procedure describes how to retrieve the debug file from the device in the Web interface.  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button.

  • Page 517: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. However, this number can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call or CLI command, configure system >...
  • Page 518 Mediant 2600 E-SBC Configure a test call according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 41-1: Test Call Table Parameter Descriptions Parameter Description General Tab Endpoint URI Defines the endpoint's URI.
  • Page 519 A value of -1 means that the parameter value is automatically calculated according to the values of the 'Calls per Second' and 'Maximum Channels for Session' parameters. Note: This parameter is applicable only if 'Call Party' is set to Caller. Version 6.8 Mediant 2600 E-SBC...
  • Page 520 Mediant 2600 E-SBC Parameter Description Calls per Second Defines the number of calls per second. CLI: calls-per-second Note: This parameter is applicable only if 'Call Party' is set to [Test_Call_CallsPerSecond] Caller. Test Mode Defines the test session mode. CLI: test-mode ...

  • Page 521: Starting And Stopping Test Calls

    To view statistics of a test call: Open the Test Call Table page (Configuration tab > System menu > Test Call > Test Call Table). Select the test call table entry whose call statistics you want to view. Version 6.8 Mediant 2600 E-SBC...
  • Page 522 Mediant 2600 E-SBC Click the Show/Hide button; the call statistics are displayed in the Test Statistics pane located below the table, as shown below: Figure 41-2: Viewing Test Call Statistics The 'Test Statistics' pane displays the following test session information: ...

  • Page 523: Configuring Dtmf Tones For Test Calls

    Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 41-3: DTMF in Test Call Settings Page In the 'Test Call DTMF String' field, enter the DTMF string (up to 15 digits). Click Submit. Version 6.8 Mediant 2600 E-SBC...

  • Page 524: Configuring Sbc Test Call With External Proxy

    Mediant 2600 E-SBC 41.5 Configuring SBC Test Call with External Proxy The SBC Test Call feature tests incoming SBC SIP call flow between a simulated test endpoint on the device and a remote SIP endpoint, when registration and routing is done through an external proxy/registrar server such as a hosted IP PBX in the WAN.

  • Page 525: Test Call Configuration Examples

    Figure 41-6: Single Test Call Example • Test Call table configuration: ♦ Endpoint URI: "101" ♦ Called URI: "201" ♦ Route By: Dest Address ♦ Destination Address: "10.30.40.01" ♦ Call Party: Caller ♦ Test Mode: Once Version 6.8 Mediant 2600 E-SBC...
  • Page 526 The test call is done between two AudioCodes devices - Device A and Device B - with simulated test endpoints. This eliminates the need for phone users, who would otherwise need to answer and end calls many times for batch testing.
  • Page 527 Called URI: "itsp" ♦ Route By: Dest Address ♦ Destination Address: "10.13.4.12" (this is the IP address of the device itself) ♦ Auto Register: Enable ♦ User Name: "testuser" ♦ Password: "12345" ♦ Call Party: Caller Version 6.8 Mediant 2600 E-SBC...
  • Page 528 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 529: Appendix

    Part XI Appendix...

  • Page 531: Dialing Plan Notation For Routing And Manipulation

    03(100): for any number that starts with 03 and ends with 100.  [100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc. Version 6.8 Mediant 2600 E-SBC...
  • Page 532 Mediant 2600 E-SBC Notation Description  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.

  • Page 533: Configuration Parameters Reference

    This feature applies to HTTP and HTTPS protocols. CLI: web-access-from-all-interfaces  [0] = (Default) Disable – Web access is only through the [EnableWebAccessFromAllInterface OAMP interface.  [1] = Enable - Web access is through any network Version 6.8 Mediant 2600 E-SBC...
  • Page 534 Mediant 2600 E-SBC Parameter Description interface. Note: For the parameter to take effect, a device reset is required. Web: Password Change Interval Defines the duration (in minutes) of the validity of Web login [WebUserPassChangeInterval] passwords. When this duration expires, the password of the Web user must be changed.
  • Page 535  SNMP (restores default users and retains other configured users: 1) Set acSysGenericINILine to WEBPasswordControlViaSNMP = 1, and reset the device with a flash burn (set acSysActionSetResetControl to 1 and Version 6.8 Mediant 2600 E-SBC...

  • Page 536: Telnet Parameters

    Mediant 2600 E-SBC Parameter Description acSysActionSetReset to 1). 2) Change the username and password in the acSysWEBAccessEntry table. Use the following format: Username acSysWEBAccessUserName: old/pass/new Password acSysWEBAccessUserCode: username/old/new [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface.

  • Page 537: Ini File Parameters

    CLI: disable  [0] Enable = (Default) SNMP is enabled. [DisableSNMP]  [1] Disable = SNMP is disabled and no traps are sent. CLI: port Defines the device's local (LAN) UDP port used for SNMP Version 6.8 Mediant 2600 E-SBC...
  • Page 538 The valid range is a string of up to 64 characters. [SendKeepAliveTrap] Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 539 ID is generated according to RFC 3411. Web: SNMP Trap Destination Parameters EMS: Network > SNMP Managers Table CLI: configure system/snmp trap destination Note: Up to five SNMP trap managers can be defined. Version 6.8 Mediant 2600 E-SBC...
  • Page 540 Mediant 2600 E-SBC Parameter Description SNMP Manager Determines the validity of the parameters (IP address and port [SNMPManagerIsUsed_x] number) of the corresponding SNMP Manager used to receive SNMP traps.  [0] (Check box cleared) = Disabled (default)  [1] (Check box selected) = Enabled...
  • Page 541 SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1; The example above configures user 'v3admin1' with security level authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2. For a description of this table, see ''Configuring SNMP V3 Users'' on page 76. Version 6.8 Mediant 2600 E-SBC...

  • Page 542: Serial Parameters

    Mediant 2600 E-SBC 43.1.6 Serial Parameters The RS-232 serial parameters are described in the table below. Table 43-6: Serial Parameters Parameter Description [DisableRS232] Enables the device's RS-232 (serial) port.  [0] = Enabled  [1] = (Default) Disabled The RS-232 serial port can be used to change the networking parameters and view error/notification messages.

  • Page 543: Auxiliary And Configuration File Name Parameters

    Note: For this parameter to take effect, a device reset is required. Web: Dial Plan File Defines the name (and path) of the Dial Plan file. This file should be EMS: Dial Plan File Name created using AudioCodes DConvert utility (refer to DConvert Utility [DialPlanFileName] User's Guide). [UserInfoFileName] Defines the name (and path) of the file containing the User Information data.

  • Page 544: Automatic Update Parameters

    Mediant 2600 E-SBC 43.1.8 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Table 43-8: Automatic Update of Software and Configuration Files Parameters Parameter Description General Automatic Update Parameters CLI: configure Enables the Automatic Update mechanism for the cmp file.
  • Page 545  [2] = Enable CRC for individual lines only. Same as option [1], except that the CRC ignores the order of lines (i.e., same text can be on different lines). Version 6.8 Mediant 2600 E-SBC...
  • Page 546 Mediant 2600 E-SBC Parameter Description CLI: config-system > Defines the size of the TFTP data blocks (packets) when automatic-update tftp-block- downloading a file from a TFTP server for the Automatic Update size mechanism. This is in accordance to RFC 2348. TFTP block size is [AUPDTftpBlockSize] the physical packet size (in bytes) that a network can transmit.
  • Page 547 Defines the name of the User Information file and the path to the server (IP address or FQDN) on which it is located. For example: http://server_name/file, https://server_name/file Note: The maximum length of the URL address is 99 characters. Version 6.8 Mediant 2600 E-SBC...

  • Page 548: Networking Parameters

    Mediant 2600 E-SBC 43.2 Networking Parameters This subsection describes the device's networking parameters. 43.2.1 Ethernet Parameters The Ethernet parameters are described in the table below. Table 43-9: Ethernet Parameters Parameter Description Physical Ports Settings Table Web: Physical Ports This table parameter configures the physical Ethernet ports...

  • Page 549: Multiple Voip Network Interfaces And Vlan Parameters

    Table table parameter is as follows: CLI: configure voip > static [ StaticRouteTable ] [StaticRouteTable] FORMAT StaticRouteTable_Index = StaticRouteTable_DeviceName, StaticRouteTable_Destination, StaticRouteTable_PrefixLength, StaticRouteTable_Gateway, StaticRouteTable_Description; [ \StaticRouteTable ] See also ''Configuring Static IP Routes'' on page 119. Version 6.8 Mediant 2600 E-SBC...

  • Page 550: Quality Of Service Parameters

    Mediant 2600 E-SBC 43.2.4 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below. Table 43-12: QoS Parameters Parameter Description Layer-2 Class Of Service (CoS) Parameters (VLAN Tag Priority Field) Web: DiffServ Table This table parameter configures DiffServ-to-VLAN Priority mapping.

  • Page 551: Nat Parameters

    Incoming SIP messages are processed as received from [SIPNatDetection] endpoints that are not located behind NAT and sent according to the SIP standard.  [1] Enable (default) = Enables the device's NAT Detection mechanism. Version 6.8 Mediant 2600 E-SBC...
  • Page 552 1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.

  • Page 553: Dns Parameters

    SRV2IP_TransportType, SRV2IP_Dns1, SRV2IP_Priority1, SRV2IP_Weight1, SRV2IP_Port1, SRV2IP_Dns2, SRV2IP_Priority2, SRV2IP_Weight2, SRV2IP_Port2, SRV2IP_Dns3, SRV2IP_Priority3, SRV2IP_Weight3, SRV2IP_Port3; [\SRV2IP] For example: SRV2IP 0 = SrvDomain,0,Dnsname1,1,1,500,Dnsname2,2,2,501,$$,0,0,0; For a detailed description of this table, see ''Configuring the Internal SRV Table'' on page 127. Version 6.8 Mediant 2600 E-SBC...

  • Page 554: Dhcp Parameters

    Mediant 2600 E-SBC 43.2.7 DHCP Parameters The Dynamic Host Control Protocol (DHCP) parameters are described in the table below. Table 43-15: DHCP Parameters Parameter Description Web: Enable DHCP Enables DHCP client functionality. EMS: DHCP Enable  [0] Disable (default) [DHCPEnable] ...
  • Page 555 The format of the ini file table parameter is as follows: [ DhcpStaticIP ] FORMAT DhcpStaticIP_Index = DhcpStaticIP_DhcpServerIndex, DhcpStaticIP_IPAddress, DhcpStaticIP_MACAddress; [ \DhcpStaticIP ] For a detailed description of this table, see Configuring Static IP Addresses for DHCP Clients on page 184. Version 6.8 Mediant 2600 E-SBC...

  • Page 556: Ntp And Daylight Saving Time Parameters

    Mediant 2600 E-SBC 43.2.8 NTP and Daylight Saving Time Parameters The Network Time Protocol (NTP) and daylight saving time parameters are described in the table below. Table 43-16: NTP and Daylight Saving Time Parameters Parameter Description NTP Parameters Note: For more information on Network Time Protocol (NTP), see ''Simple Network Time Protocol Support'' on page 99.
  • Page 557 The valid range is 0 to 120. The default is 60. [DayLightSavingTimeOffset] Note: The offset setting is applied only on the hour. For example, if you configure this parameter at 15:42, the device applies the setting only at 16:00. Version 6.8 Mediant 2600 E-SBC...

  • Page 558: Debugging And Diagnostics Parameters

    Mediant 2600 E-SBC 43.3 Debugging and Diagnostics Parameters This subsection describes the device's debugging and diagnostic parameters. 43.3.1 General Parameters The general debugging and diagnostic parameters are described in the table below. Table 43-17: General Debugging and Diagnostic Parameters Parameter...

  • Page 559: Sip Test Call Parameters

    Test_Call_CalledURI, Test_Call_RouteBy, Test_Call_IPGroupID, Test_Call_DestAddress, Test_Call_DestTransportType, Test_Call_SRD, Test_Call_ApplicationType, Test_Call_AutoRegister, Test_Call_UserName, Test_Call_Password, Test_Call_CallParty, Test_Call_MaxChannels, Test_Call_CallDuration, Test_Call_CallsPerSecond, Test_Call_TestMode, Test_Call_TestDuration, Test_Call_Play, Test_Call_ScheduleInterval, Test_Call_QOEProfile, Test_Call_BWProfile; [ \Test_Call ] For a description of this table, see ''Configuring Test Call Endpoints'' on page 517. Version 6.8 Mediant 2600 E-SBC...

  • Page 560: Syslog, Cdr And Debug Parameters

    Mediant 2600 E-SBC 43.3.3 Syslog, CDR and Debug Parameters The Syslog, CDR and debug parameters are described in the table below. Table 43-19: Syslog, CDR and Debug Parameters Parameter Description Web: Enable Syslog Determines whether the device sends logs and error messages (e.g., EMS: Syslog enable CDRs) generated by the device to a Syslog server.
  • Page 561 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the 'acsyslog' filter instead of the regular 'syslog' filter.
  • Page 562 Mediant 2600 E-SBC Parameter Description Web: Syslog CPU Protection Enables the protection of the device's CPU resources during debug reporting, ensuring voice traffic is unaffected. If CPU resources drop CLI: configure (i.e., high CPU usage) to a critical level (threshold), the device...
  • Page 563 The default is 925. CLI: configure system > logging > dbg-rec-dest-port [DebugRecordingDestPort] Debug Recording Status Activates or de-activates debug recording. CLI: configure system >  [0] Stop (default) logging > dbg-rec-status  [1] Start [DebugRecordingStatus] Version 6.8 Mediant 2600 E-SBC...

  • Page 564: Resource Allocation Indication Parameters

    Mediant 2600 E-SBC Parameter Description Web: Enable Core Dump Enables the automatic generation of a Core Dump file upon a device [EnableCoreDump] crash.  [0] Disable (default)  [1] Enable Note: For the parameter to take effect, a device reset is required.

  • Page 565: Ha Ping Parameters

    IP network interfaces. If no [HAPingEnabled] reply is received from a ping and the previous ping was successful, a switchover occurs to the redundant device.  [0] Disabled (default)  [1] Enabled Version 6.8 Mediant 2600 E-SBC...
  • Page 566 Mediant 2600 E-SBC Parameter Description Web: HA Network Defines the IP address of the destination that the device pings. Reachability Destination The default is 0.0.0.0. Address [HAPingDestination] Web: HA Network Defines the device's IP network interface from where the ping is sent.

  • Page 567: Security Parameters

    IP address and SSRC for RTCP/RTP and based on IP address only for T.38, the packet is accepted immediately. Note: If a packet from the original (first latched onto) IP address:port is received at any time, the device latches onto this stream. Version 6.8 Mediant 2600 E-SBC...
  • Page 568 Mediant 2600 E-SBC Parameter Description  [2] Dynamic-Strict = Device latches onto the first stream. If it receives at least a minimum number of consecutive packets (configured by New<media type>StreamPackets) all from the same source which is different to the first stream and the device has not received packets from the current stream for a user- defined period (TimeoutToRelatch<media type>Msec), it...

  • Page 569: Https Parameters

    [1] Web Based Authentication = (Default) Digest [WebAuthMode] authentication (MD5) is used. Note: If you enable RADIUS login (i.e., the WebRADIUSLogin parameter is set to 1), you must set the WebAuthMode parameter to Basic Mode [0]. Version 6.8 Mediant 2600 E-SBC...

  • Page 570: Srtp Parameters

    Mediant 2600 E-SBC Parameter Description Web: Requires Client Certificates Determines whether client certificates are required for HTTPS for HTTPS connection connection. CLI: req-client-cert  [0] Disable = (Default) Client certificates are not required. [HTTPSRequireClientCertificate]  [1] Enable = Client certificates are required. The client certificate must be preloaded to the device and its matching private key must be installed on the managing PC.
  • Page 571 Profile table, see ''Configuring IP Profiles'' on page 297. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 2600 E-SBC...

  • Page 572: Tls Parameters

    Mediant 2600 E-SBC 43.4.4 TLS Parameters The Transport Layer Security (TLS) parameters are described in the table below. Table 43-25: TLS Parameters Parameter Description Web: TLS Contexts Table Defines SSL/TLS certificates. CLI: configure system > tls # The format of the ini file table parameter is as follows:...
  • Page 573 (‘*’) to replace parts of the domain name. The valid range is a string of up to 49 characters. Note: This parameter is applicable only if the parameter PeerHostNameVerificationMode is set to 1 or 2. Version 6.8 Mediant 2600 E-SBC...
  • Page 574 Mediant 2600 E-SBC Parameter Description Web: TLS Expiry Check Start Defines the number of days before the installed TLS server CLI: expiry-check-start certificate is to expire at which the device must send a trap [TLSExpiryCheckStart] (acCertificateExpiryNotifiaction) to notify of this.

  • Page 575: Ssh Parameters

    SSH session is [SSHMaxLoginAttempts] rejected. The valid range is 1 to 5. The default is 3. Note: The new setting takes effect only for new subsequent SSH connections. Version 6.8 Mediant 2600 E-SBC...

  • Page 576: Ids Parameters

    Mediant 2600 E-SBC 43.4.6 IDS Parameters The Intrusion Detection System (IDS) parameters are described in the table below. Table 43-27: IDS Parameters Parameter Description Web: Intrusion Detection Enables the IDS feature. System (IDS)  [0] Disable (default) CLI: enable-ids ...

  • Page 577: Quality Of Experience Parameters

    The Quality of Experience (QoE) parameters are described in the table below. Table 43-28: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of AudioCodes primary Session Experience CLI: configure voip/qoe Manager (SEM) server to where the quality experience reports are configuration/server-ip sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
  • Page 578 Mediant 2600 E-SBC Parameter Description Bandwidth Profile Table Web: Bandwidth Profile This table parameter defines Bandwidth Profiles. CLI: configure voip/qoe bw- The format of the ini file table parameter is as follows: profile [BWProfile] [BWProfile] FORMAT BWProfile_Index = BWProfile_Name, BWProfile_EgressAudioBandwidth,...

  • Page 579: Control Network Parameters

    The format of the ini file table parameter is as follows: [Account] FORMAT Account_Index = Account_ServedTrunkGroup, Account_ServedIPGroup, Account_ServingIPGroup, Account_Username, Account_Password, Account_HostName, Account_Register, Account_ContactUser, Account_ApplicationType; [\Account] For a detailed description of this table, see ''Configuring Registration Accounts'' on page 277. Version 6.8 Mediant 2600 E-SBC...
  • Page 580 Mediant 2600 E-SBC Parameter Description Proxy Registration Parameters Web/EMS: Proxy Name Defines the Home Proxy domain name. If specified, this name CLI: proxy-name is used as the Request-URI in REGISTER, INVITE and other SIP messages, and as the host part of the To header in INVITE [ProxyName] messages.
  • Page 581 Transport Type is defined, a NAPTR query is not performed. Notes:  This functionality can be configured per Proxy Set in the Proxy Set table (see ''Configuring Proxy Sets'' on page 269).  When enabled, NAPTR/SRV queries are used to discover Version 6.8 Mediant 2600 E-SBC...
  • Page 582 Mediant 2600 E-SBC Parameter Description Proxy servers even if the parameter DNSQueryType is disabled. Web/EMS: Use Gateway Name for Determines whether the device uses its IP address or string OPTIONS name ("gateway name") in keep-alive SIP OPTIONS messages CLI: use-gw-name-for-opt (host part of the Request-URI).
  • Page 583 The valid range is 0 to 2,000,000. The default is 0. Web: ReRegister On Connection Enables the device to perform SIP re-registration upon Failure TCP/TLS connection failure. EMS: Re Register On Connection  [0] Disable (default) Failure Version 6.8 Mediant 2600 E-SBC...
  • Page 584 Mediant 2600 E-SBC Parameter Description  CLI: reg-on-conn-failure [1] Enable [ReRegisterOnConnectionFailure] CLI: expl-un-reg Enables the device to perform explicit unregisters. [UnregistrationMode]  [0] Disable (default)  [1] Enable = The device sends an asterisk ("*") value in the SIP Contact header, instructing the Registrar server to remove all previous registration bindings.
  • Page 585 CPU caused by sending many registration requests at a given time. The valid value is 30 to 300 register requests per second. The Version 6.8 Mediant 2600 E-SBC...
  • Page 586 Mediant 2600 E-SBC Parameter Description default is 150. For configuration examples, see the description of the GeneratedRegistersInterval parameter. Generated Registers interval Defines the rate (in seconds) at which the device sends user register requests (REGISTER messages). The parameter is gen-reg-int...

  • Page 587: Network Application Parameters

    Defines the interval (in sec) between consecutive keep-alive probes, regardless of what the connection has exchanged in the meantime. The valid value is 10 to 65,000. The default is 10. Note: TCP keepalive is enabled per SIP Interface in the SIP Interface table. Version 6.8 Mediant 2600 E-SBC...
  • Page 588 Mediant 2600 E-SBC Parameter Description [TCPKeepAliveRetry] Defines the number of unacknowledged keep-alive probes to send before considering the connection down. The valid value is 1 to 100. The default is 5. Note: TCP keepalive is enabled per SIP Interface in the SIP Interface table.

  • Page 589: General Sip Parameters

    Event [EnableSIPRemoteReset header.  [0] Disable (default)  [1] Enable The action depends on the Event header value:  'check-sync;reboot=false': triggers the regular Automatic Update feature (if Automatic Update has been enabled on the device) Version 6.8 Mediant 2600 E-SBC...
  • Page 590 Parameter Description  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Defines the maximum size (in Kbytes) for each SIP message that can be Message Length [KB] sent over the network. The device rejects messages exceeding this user- [MaxSIPMessageLength defined size.
  • Page 591 Session- disconnect-time Expires header. However, the new timeout must be greater than or equal [SessionExpiresDiscon to one-third (1/3) of the Session-Expires value. If the refresher does not Version 6.8 Mediant 2600 E-SBC...
  • Page 592 Mediant 2600 E-SBC Parameter Description nectTime] send a refresh request within the new timeout, the device disconnects the session (i.e., sends a SIP BYE). For example, if you configure the parameter to 32 seconds and the Session-Expires value is 180 seconds, the session timeout occurs 148 seconds (i.e., 180 minus 32) after the last session refresh.
  • Page 593 Defines the local UDP port for SIP messages. EMS: Local SIP Port The valid range is 1 to 65534. The default is 5060. CLI: sip-udp-local-port [LocalSIPPort] Web: SIP TCP Local Port Defines the local TCP port for SIP messages. Version 6.8 Mediant 2600 E-SBC...
  • Page 594 Mediant 2600 E-SBC Parameter Description EMS: TCP Local SIP Port The valid range is 1 to 65535. The default is 5060. CLI: sip-tcp-local-port [TCPLocalSIPPort] Web: SIP TLS Local Port Defines the local TLS port for SIP messages. EMS: TLS Local SIP Port The valid range is 1 to 65535.
  • Page 595 GRUU from a registrar and for communicating a GRUU to a peer within a dialog.  [0] Disable (default)  [1] Enable A GRUU is a SIP URI that routes to an instance-specific UA and can be Version 6.8 Mediant 2600 E-SBC...
  • Page 596 Mediant 2600 E-SBC Parameter Description reachable from anywhere. There are a number of contexts in which it is desirable to have an identifier that addresses a single UA (using GRUU) rather than the group of UA’s indicated by an Address of Record (AOR).
  • Page 597 43. Configuration Parameters Reference Parameter Description Info User-Agent: myproduct/v.6.80.010.006 CLI: user-agent-info If not configured, the default string, <AudioCodes product- [UserAgentDisplayInfo] name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 2600 E- SBC/v.6.80.010.006 The maximum string length is 50 characters. Note: The software version number and preceding forward slash (/) cannot be modified.
  • Page 598 Mediant 2600 E-SBC Parameter Description CLI: 3xx-behavior response is received for an outgoing INVITE request. The device can [3xxBehavior] either use the same call identifiers (Call-ID, To, and From tags) or change them in the new initiated INVITE.  [0] Forward = (Default) Use different call identifiers for a redirected INVITE message.
  • Page 599 [0] Disable (default)  [1] Enable Web/EMS: Enable Determines whether the device sets the Contact header of outgoing Contact Restriction INVITE requests to ‘anonymous’ for restricted calls. CLI: contact-restriction  [0] Disable (default) [EnableContactRestricti  [1] Enable Version 6.8 Mediant 2600 E-SBC...
  • Page 600 Mediant 2600 E-SBC Parameter Description EMS: Use URL In Refer Defines the source for the SIP URI set in the Refer-To header of outgoing To Header REFER messages. [UseAORInReferToHead  [0] = (Default) Use SIP URI from Contact header of the initial call.
  • Page 601 Number Manipulation tables to leave only the last 3 digits (for example) for sending to a PBX. EMS: Use SIP URI For Defines the URI format in the SIP Diversion header. Version 6.8 Mediant 2600 E-SBC...
  • Page 602 Mediant 2600 E-SBC Parameter Description  Diversion Header [0] = 'tel:' (default) [UseSIPURIForDiversio  [1] = 'sip:' nHeader] [TimeoutBetween100An Defines the timeout (in msec) between receiving a 100 Trying response d18x] and a subsequent 18x response. If a 18x response is not received within this timeout period, the call is disconnected.
  • Page 603 Defines manipulation rules for SIP header messages. The format of the Manipulations ini file table parameter is as follows: EMS: Message [ MessageManipulations] Manipulations FORMAT MessageManipulations_Index = CLI: configure voip > sbc MessageManipulations_ManSetID, manipulations message- MessageManipulations_MessageType, manipulations MessageManipulations_Condition, [MessageManipulations] MessageManipulations_ActionSubject, MessageManipulations_ActionType, MessageManipulations_ActionValue, MessageManipulations_RowRole; Version 6.8 Mediant 2600 E-SBC...
  • Page 604 Mediant 2600 E-SBC Parameter Description [\MessageManipulations] For example, the below configuration changes the user part of the SIP From header to 200: MessageManipulations 1 = 0, Invite.Request, , Header.From.Url.User, 2, 200, 0; For a detailed description of this table, see Configuring SIP Message Manipulation on page 284.

  • Page 605: Coders And Profile Parameters

    IP Groups. The format of the ini file table parameter is profile as follows: [IPProfile] [IPProfile] FORMAT IpProfile_Index = IpProfile_ProfileName, IpProfile_IpPreference, IpProfile_CodersGroupID, IpProfile_IsFaxUsed, IpProfile_JitterBufMinDelay, IpProfile_JitterBufOptFactor, IpProfile_IPDiffServ, IpProfile_SigIPDiffServ, IpProfile_SCE, IpProfile_RTPRedundancyDepth, IpProfile_RemoteBaseUDPPort, IpProfile_CNGmode, IpProfile_VxxTransportType, IpProfile_NSEMode, Version 6.8 Mediant 2600 E-SBC...
  • Page 606 Mediant 2600 E-SBC Parameter Description IpProfile_IsDTMFUsed, IpProfile_PlayRBTone2IP, IpProfile_EnableEarlyMedia, IpProfile_ProgressIndicator2IP, IpProfile_EnableEchoCanceller, IpProfile_CopyDest2RedirectNumber, IpProfile_MediaSecurityBehaviour, IpProfile_CallLimit, IpProfile_DisconnectOnBrokenConnection, IpProfile_FirstTxDtmfOption, IpProfile_SecondTxDtmfOption, IpProfile_RxDTMFOption, IpProfile_EnableHold, IpProfile_InputGain, IpProfile_VoiceVolume, IpProfile_AddIEInSetup, IpProfile_SBCExtensionCodersGroupID, IpProfile_MediaIPVersionPreference, IpProfile_TranscodingMode, IpProfile_SBCAllowedMediaTypes, IpProfile_SBCAllowedCodersGroupID, IpProfile_SBCAllowedVideoCodersGroupID, IpProfile_SBCAllowedCodersMode, IpProfile_SBCMediaSecurityBehaviour, IpProfile_SBCRFC2833Behavior, IpProfile_SBCAlternativeDTMFMethod, IpProfile_SBCAssertIdentity, IpProfile_AMDSensitivityParameterSuit, IpProfile_AMDSensitivityLevel, IpProfile_AMDMaxGreetingTime, IpProfile_AMDMaxPostSilenceGreetingTime, IpProfile_SBCDiversionMode, IpProfile_SBCHistoryInfoMode, IpProfile_EnableQSIGTunneling, IpProfile_SBCFaxCodersGroupID,...

  • Page 607: Channel Parameters

    This feature removes echoes and sends only the near-end’s desired CLI: acoustic-echo- speech signal to the network (i.e., to the far-end party). suppressor-enable  [0] Disable (default) [AcousticEchoSuppressorSu  [1] Enable pport] Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 2600 E-SBC...
  • Page 608 Mediant 2600 E-SBC Parameter Description Web: Echo Canceller Type Defines the echo canceller type. CLI: echo-canceller-type  [0] Line echo canceller = (Default) Echo canceller for Tel side. [EchoCancellerType]  [1] Acoustic Echo suppressor - netw = Echo canceller for IP side.

  • Page 609: Coder Parameters

    RFC 3558 Header Free format. [VBRCoderHeaderFormat]  [1] = Supports RFC 2658 - 1 byte for interleaving header (always 0), TOC, no m-factor.  [2] = Payload including TOC only, allow m-factor.  [3] = RFC 3558 Interleave/Bundled format. Version 6.8 Mediant 2600 E-SBC...

  • Page 610: Dtmf Parameters

    Mediant 2600 E-SBC Parameter Description EMS: VBR Coder Hangover Defines the required number of silence frames at the beginning of CLI: VBR-coder-hangover each silence period when using the VBR coder silence [VBRCoderHangover] suppression. The range is 0 to 255. The default is 1.

  • Page 611: Rtp, Rtcp And T.38 Parameters

    IP Profile table, see Configuring IP Profiles on page 297. Note: If this functionality is configured for a specific profile, the settings of this global parameter is ignored for calls associated with the profile. Version 6.8 Mediant 2600 E-SBC...
  • Page 612 Mediant 2600 E-SBC Parameter Description Web: RTP Redundancy Depth Global parameter that enables the device to generate RFC EMS: Redundancy Depth 2198 redundant packets. You can also configure this CLI: RTP-redundancy-depth functionality per specific calls, using IP Profiles [RTPRedundancyDepth] (IpProfile_RTPRedundancyDepth). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see Configuring IP Profiles on page 297.
  • Page 613 (no RTP/T.38 traffic) when No- Op packet transmission is enabled. The valid range is 20 to 65,000 msec. The default is 10,000. Note: To enable No-Op packet transmission, use the NoOpEnable parameter. Version 6.8 Mediant 2600 E-SBC...
  • Page 614 Mediant 2600 E-SBC Parameter Description EMS: No Op Payload Type Defines the payload type of No-Op packets. CLI: no-operation-interval The valid range is 96 to 127 (for the range of Dynamic RTP [RTPNoOpPayloadType] Payload Type for all types of non hard-coded RTP Payload types, refer to RFC 3551).

  • Page 615: Sbc Parameters

    [1] Allow = If classification fails, the incoming packet is assigned to a source IP Group (and subsequently processed) as follows:  The source SRD is determined according to the SIP Interface to where the SIP-initiating dialog request is sent. Version 6.8 Mediant 2600 E-SBC...
  • Page 616 [NumOfSubscribes] The valid value is any value between 0 and the maximum supported SUBSCRIBE sessions. When set to -1, the device uses the default value. For more information, contact your AudioCodes sales representative. Notes: ...
  • Page 617 Note: The time values of the Session-Expires (session refresh interval) and Min-SE (minimum session refresh interval) headers can be configured using the SBCSessionExpires and SBCMinSE parameters, respectively. Web: User Registration Grace Defines additional time (in seconds) to add to the registration expiry Version 6.8 Mediant 2600 E-SBC...
  • Page 618 Mediant 2600 E-SBC Parameter Description Time time of registered users in the device's Users Registration CLI: configure voip/sbc general- database. setting/sbc-usr-reg-grace-time The valid value is 0 to 300 (i.e., 5 minutes). The default is 0. [SBCUserRegistrationGraceTi Web/EMS: Handle P-Asserted- Global parameter that defines the handling of the SIP P-Asserted- Identity Identity header.
  • Page 619 The valid value range is 30 to 600. The default is 300. Web: Authentication Challenge Defines the type of server-based authentication challenge. Method  [0] 0 = (Default) Send SIP 401 "Unauthorized" with a WWW- CLI: auth-chlng-mthd Authenticate header as the authentication challenge response. Version 6.8 Mediant 2600 E-SBC...
  • Page 620 Mediant 2600 E-SBC Parameter Description  [AuthChallengeMethod] [1] 1 = Send SIP 407 "Proxy Authentication Required" with a Proxy-Authenticate header as the authentication challenge response. Web: Authentication Quality of Defines the authentication and integrity level of quality of protection Protection (QoP) for digest authentication offered to the client.
  • Page 621 When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following XML body: Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> Version 6.8 Mediant 2600 E-SBC...
  • Page 622 Mediant 2600 E-SBC Parameter Description <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument> Web: SBC Dialog-Info Enables the interworking of dialog information (parsing of call Interworking identifiers in XML body) in SIP NOTIFY messages received from a CLI: configure voip/sbc general- remote application server.
  • Page 623 IP Profile table, see Configuring IP Profiles on page 297. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 2600 E-SBC...
  • Page 624 Mediant 2600 E-SBC Parameter Description Web: SBC Preferences Mode Determines the order of the Extension coders (coders added if [SBCPreferencesMode] there are no common coders between SDP offered coders and Allowed coders) and Allowed coders (configured in the Allowed Coders Group table) in the outgoing SIP message (in the SDP).
  • Page 625 (SIP dialogs). CLI: configure voip > sbc sbc- The format of the ini file table parameter is as follows: admission-control [SBCAdmissionControl] [SBCAdmissionControl] FORMAT SBCAdmissionControl_Index = SBCAdmissionControl_AdmissionControlName, SBCAdmissionControl_LimitType, SBCAdmissionControl_IPGroupID, SBCAdmissionControl_SRDID, SBCAdmissionControl_RequestType, SBCAdmissionControl_RequestDirection, SBCAdmissionControl_Limit, SBCAdmissionControl_LimitPerUser, SBCAdmissionControl_Rate, SBCAdmissionControl_MaxBurst, SBCAdmissionControl_Reservation; Version 6.8 Mediant 2600 E-SBC...
  • Page 626 Mediant 2600 E-SBC Parameter Description [\SBCAdmissionControl] For a detailed description of this table, see ''Configuring Admission Control'' on page 355. Allowed Audio Coders Table Web: Allowed Audio Coders This table parameter defines Allowed Coders Groups, which CLI: configure voip > sbc...
  • Page 627 The format of the ini file table parameter is as follows: CLI: configure voip > sbc [IPInboundManipulation] manipulations ip-inbound- FORMAT IPInboundManipulation_Index = manipulation IPInboundManipulation_ManipulationName [IPInboundManipulation] IPInboundManipulation_IsAdditionalManipulation, IPInboundManipulation_ManipulatedURI, IPInboundManipulation_ManipulationPurpose, IPInboundManipulation_SrcIPGroupID, IPInboundManipulation_SrcUsernamePrefix, IPInboundManipulation_SrcHost, IPInboundManipulation_DestUsernamePrefix, IPInboundManipulation_DestHost, IPInboundManipulation_RequestType, IPInboundManipulation_RemoveFromLeft, IPInboundManipulation_RemoveFromRight, IPInboundManipulation_LeaveFromRight, Version 6.8 Mediant 2600 E-SBC...

  • Page 628: Ip Media Parameters

    Mediant 2600 E-SBC Parameter Description IPInboundManipulation_Prefix2Add, IPInboundManipulation_Suffix2Add; [\IPInboundManipulation] For a detailed description of this table, see ''Configuring IP-to-IP Inbound Manipulations'' on page 382. IP to IP Outbound Manipulation Table Web: IP to IP Outbound This table parameter configures the IP to IP Outbound Manipulation Manipulation table.
  • Page 629 The valid range is 0 to -63 dBm. The default is -19 dBm. CLI: AGC-target-energy [AGCTargetEnergy] Web: AGC Minimum Gain Defines the minimum gain (in dB) by the AGC when activated. EMS: Minimal Gain The range is 0 to -31. The default is -20. CLI: AGC-min-gain Version 6.8 Mediant 2600 E-SBC...

  • Page 630: Services

    Mediant 2600 E-SBC Parameter Description [AGCMinGain] Note: For this parameter to take effect, a device reset is required. Web: AGC Maximum Gain Defines the maximum gain (in dB) by the AGC when activated. EMS: Maximal Gain The range is 0 to 18. The default is 15.

  • Page 631: Radius And Ldap Parameters

    [0] Disable (Default) CLI: enable  [1] Enable [EnableRADIUS] Note: For this parameter to take effect, a device reset is required. Web: Accounting Server Defines the IP address of the RADIUS accounting server. IP Address CLI: accounting-server-ip Version 6.8 Mediant 2600 E-SBC...
  • Page 632 Mediant 2600 E-SBC Parameter Description [RADIUSAccServerIP] Web: Accounting Port Defines the port of the RADIUS accounting server. CLI: accounting-port The default is 1646. [RADIUSAccPort] Web/EMS: RADIUS Determines when the RADIUS accounting messages are sent to the Accounting Type RADIUS accounting server.

  • Page 633: Ldap Parameters

    The valid range is 1 to 30. The default is 10. 43.12.2.3 LDAP Parameters The Lightweight Directory Access Protocol (LDAP) parameters are described in the table below. LDAP Parameters Parameter Description Web: LDAP Service Enables the LDAP feature. CLI: configure  [0] Disable (default) Version 6.8 Mediant 2600 E-SBC...
  • Page 634 Mediant 2600 E-SBC Parameter Description  voip/ldap/enable [1] Enable [LDAPServiceEnable] Note: For this parameter to take effect, a device reset is required. CLI: search-dns-in-parallel Defines the method of how the device queries the DN object within [LDAPSearchDNsinParalle each LDAP server.
  • Page 635 LDAP Configuration Table Web: LDAP Configuration Defines the LDAP servers. Table [ LdapConfiguration ] CLI: configure voip > ldap > FORMAT LdapConfiguration_Index = ldap-configuration LdapConfiguration_LdapConfServerIp, [LdapConfiguration] LdapConfiguration_LdapConfServerPort, LdapConfiguration_LdapConfServerMaxRespondTime, LdapConfiguration_LdapConfServerDomainName, LdapConfiguration_LdapConfPassword, LdapConfiguration_LdapConfBindDn, LdapConfiguration_LdapConfInterfaceType, LdapConfiguration_Type, LdapConfiguration_MngmAuthAtt, Version 6.8 Mediant 2600 E-SBC...

  • Page 636: Least Cost Routing Parameters

    Mediant 2600 E-SBC Parameter Description LdapConfiguration_ConnectionStatus; [ \LdapConfiguration ] For a detailed description of this table, see 'Configuring LDAP Servers' on page 201. LDAP Server Search DN Table Web: LDAP Search DN Defines the full base path (i.e., distinguished name / DN) to the Table objects in the AD where the query is done, per LDAP server.

  • Page 637: Call Setup Rules Parameters

    [CallSetupRules] [ CallSetupRules ] FORMAT CallSetupRules_Index = CallSetupRules_RulesSetID, CallSetupRules_AttributesToQuery, CallSetupRules_AttributesToGet, CallSetupRules_RowRole, CallSetupRules_Condition, CallSetupRules_ActionSubject, CallSetupRules_ActionType, CallSetupRules_ActionValue; [ \CallSetupRules ] Note: For a detailed description of this table, see ''Configuring Call Setup Rules'' on page 229. Version 6.8 Mediant 2600 E-SBC...
  • Page 638 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 639: Sbc Channel Capacity

    • The number of channels refers to the maximum channel capacity of the device. • For additional DSP templates, contact your AudioCodes sales representative. 44.1 Signaling-Media Sessions & User Registrations The table below lists the maximum capacity. This includes SIP signaling sessions, SBC sessions, and registered users.
  • Page 640 The capacity figures listed in the table below are accurate at the time of publication of this document. However, these figures may change due to a later software update. For the latest figures, please contact your AudioCodes sales representative. •...

  • Page 641: Channel Capacity And Capabilities

    Profile 2: G.711, G.726, G.729, G.723.1, AMR-NB, T.38 with fax detection, in- band signaling, and Silence Compression. • Acoustic Echo Suppressor reduces performance by about 30%. For more information, contact your AudioCodes sales representative. • MPM is the optional, Media Processing Module which provides additional DSPs, allowing greater capacity Version 6.8...
  • Page 642 Mediant 2600 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-42060...

  • Page 643: Technical Specifications

    The device's technical specifications are listed in the table below. Notes: • All specifications in this document are subject to change without prior notice. • The compliance and regulatory information can be downloaded from AudioCodes Web site at http://www.audiocodes.com/library. Table 45-1: Technical Specifications Function Specification Networking Interfaces ...
  • Page 644 Mediant 2600 E-SBC Function Specification Hardware Specifications  CPU. E-SBC CPU AMC Module  LAN sub-module providing eight 1000Base-T (Gigabit Ethernet) LAN ports, operating in pairs for 1+1 LAN redundancy (one port active; the other standby). Supports auto-negotiation, half- and full-duplex modes, and straight-through and crossover cable detection.
  • Page 645 User's Manual 45. Technical Specifications This page is intentionally left blank. Version 6.8 Mediant 2600 E-SBC...
  • Page 646 Website: https://www.audiocodes.com/ ©2017 AudioCodes Ltd. All rights reserved. AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, User Management Pack, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One Voice and CloudBond are trademarks or registered trademarks of AudioCodes Limited.

Table of Contents