AudioCodes Mediant 2000 User Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Gateway
  5. Mediant 2000
  6. User manual
AudioCodes Mediant 2000 User Manual

AudioCodes Mediant 2000 User Manual

Voip media gateway
Hide thumbs Also See for Mediant 2000:
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
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Installation Manual
Mediant™ 2000
VoIP Media Gateway
Digital PSTN Lines
User's Manual
Version 6.6
February 2015
Document # LTRT-68822

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 2000

Summary of Contents for AudioCodes Mediant 2000

  • Page 1 Mediant™ 2000 VoIP Media Gateway Digital PSTN Lines User's Manual Version 6.6 February 2015 Document # LTRT-68822...

  • Page 3: Table Of Contents

    4.3.2 Advanced User Accounts Configuration ..............63 Displaying Login Information upon Login ............... 66 Configuring Web Security Settings ................ 67 Web Login Authentication using Smart Cards ............68 Configuring Web and Telnet Access List ............... 68 Version 6.6 Mediant 2000...
  • Page 4 Mediant 2000 Configuring RADIUS Settings ................70 CLI-Based Management ..................71 Enabling CLI using Telnet ..................71 Enabling CLI using SSH and RSA Public Key ............71 Establishing a CLI Session ..................73 CLI Commands ...................... 74 5.4.1 Status Commands ....................74 5.4.2...
  • Page 5 13.1.1 Configuring Voice Gain (Volume) Control .............153 13.1.2 Silence Suppression (Compression) ..............154 13.1.3 Echo Cancellation ....................154 13.2 Fax and Modem Capabilities ................155 13.2.1 Fax/Modem Operating Modes ................156 13.2.2 Fax/Modem Transport Modes ................156 13.2.2.1 T.38 Fax Relay Mode ................156 Version 6.6 Mediant 2000...
  • Page 6 Mediant 2000 13.2.2.2 G.711 Fax / Modem Transport Mode ............ 158 13.2.2.3 Fax Fallback ..................158 13.2.2.4 Fax/Modem Bypass Mode ..............159 13.2.2.5 Fax / Modem NSE Mode ............... 160 13.2.2.6 Fax / Modem Transparent with Events Mode ........161 13.2.2.7 Fax / Modem Transparent Mode ............
  • Page 7 21.6 ISDN Non-Facility Associated Signaling (NFAS) ..........272 21.6.1 NFAS Interface ID ....................273 21.6.2 Working with DMS-100 Switches ................273 21.6.3 Creating an NFAS-Related Trunk Configuration ...........274 21.6.4 Performing Manual D-Channel Switchover in NFAS Group ........275 21.7 ISDN Overlap Dialing ................... 275 Version 6.6 Mediant 2000...
  • Page 8 Mediant 2000 21.7.1 Collecting ISDN Digits and Sending Complete Number in SIP ......275 21.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 ....276 21.8 Redirect Number and Calling Name (Display) ............. 277 22 Trunk Group ....................279 22.1 Configuring Trunk Group Table ................279 22.2 Configuring Trunk Group Settings ................
  • Page 9 User's Manual Contents 26.5.2.2 Microsoft Lync Server 2010 and E9-1-1 ..........340 26.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 26.5.2.4 Configuring AudioCodes ELIN Gateway ..........348 26.6 Multilevel Precedence and Preemption ..............349 26.6.1 MLPP Preemption Events in SIP Reason Header ..........352 26.6.2 Precedence Ring Tone ..................353...
  • Page 10 34.4.4 TFTP Configuration using DHCP Option 66 ............429 34.4.5 HTTP-based Automatic Updates ................429 34.4.6 Configuration using FTP or NFS ................430 34.4.7 Configuration using AudioCodes EMS ..............430 34.5 Loading Files Securely (Disabling TFTP) ............. 431 34.6 Remotely Triggering Auto Update using SIP NOTIFY ......... 432 35 Restoring Factory Defaults ................
  • Page 11 41 Syslog and Debug Recordings ..............475 41.1 Syslog Message Format ..................475 41.1.1 Event Representation in Syslog Messages ............476 41.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......478 41.1.3 Syslog Fields for Automatic Machine Detection ............478 41.1.4 SNMP Alarms in Syslog Messages ...............479 41.2 Configuring Syslog Settings .................
  • Page 12 Mediant 2000 42 Self-Testing ...................... 487 43 Testing SIP Signaling Calls ................489 43.1 Configuring Test Call Endpoints ................489 43.1.1 Starting, Stopping and Restarting Test Calls............492 43.1.2 Viewing Test Call Statistics..................493 43.2 Configuring DTMF Tones for Test Calls ............... 494 43.3 Configuring Basic Test Call ..................
  • Page 13 45.14 Standalone Survivability Parameters ..............682 45.15 IP Media Parameters ................... 687 45.16 Auxiliary and Configuration File Name Parameters ..........692 45.17 Automatic Update Parameters ................693 46 DSP Templates ....................695 47 Selected Technical Specifications ..............697 Version 6.6 Mediant 2000...
  • Page 14 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 15: Weee Eu Directive

    This document is subject to change without notice. Date Published: February-22-2015 Trademarks AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect, VoIPerfectHD, What’s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or...

  • Page 16: Related Documentation

    • By default, the device supports export-grade (40-bit and 56-bit) encryption due to US government restrictions on the export of security technologies. To enable 128- bit and 256-bit encryption on your device, contact your AudioCodes sales representative. • This device includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
  • Page 17 Serial port interface removed; Restoring defaults updated; Blade specifications removed. 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 on our Web site at http://www.audiocodes.com/downloads.
  • Page 18 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 19: Overview

    Overview This manual provides you with the information for installing, configuring, and operating the Mediant 2000 SIP gateway (referred to throughout this manual as device). The device is a SIP-based Voice-over-IP (VoIP) media gateway. The device enables voice, fax, and data traffic to be sent over the same IP network.

  • Page 20: Sip Overview

    Mediant 2000 The figure below illustrates a typical device applications VoIP network: SIP Overview Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol used on the gateway for creating, modifying, and terminating sessions with one or more participants. These sessions can include Internet telephone calls, media announcements, and conferences.
  • Page 21 F1 INVITE - 10.8.201.108 to 10.8.201.161: INVITE sip:2000@10.8.201.161;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: <sip:6000@10.8.201.108>;tag=1c5354 To: <sip:2000@10.8.201.161> Call-ID: 534366556655skKw-6000--2000@10.8.201.108 CSeq: 18153 INVITE Contact: <sip:8000@10.8.201.108;user=phone> User-Agent: Audiocodes-Sip-Gateway/Mediant 2000/v.6.60.010.006 Supported: 100rel,em Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE, NOTIFY,PRACK,REFER,INFO Content-Type: application/sdp Content-Length: 208 o=AudiocodesGW 18132 74003 IN IP4 10.8.201.108 s=Phone-Call c=IN IP4 10.8.201.108...
  • Page 22 F2 TRYING - 10.8.201.161 to 10.8.201.108: SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: <sip:6000@10.8.201.108>;tag=1c5354 To: <sip:2000@10.8.201.161> Call-ID: 534366556655skKw-6000--2000@10.8.201.108 Server: Audiocodes-Sip-Gateway/Mediant 2000/v.6.60.010.006 CSeq: 18153 INVITE Content-Length: 0  F3 RINGING 180 - 10.8.201.161 to 10.8.201.108: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: <sip:6000@10.8.201.108>;tag=1c5354...
  • Page 23  F6 BYE - 10.8.201.108 to 10.8.201.10: BYE sip:2000@10.8.201.161;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud From: <sip:6000@10.8.201.108>;tag=1c5354 To: <sip:2000@10.8.201.161>;tag=1c7345 Call-ID: 534366556655skKw-6000--2000@10.8.201.108 User-Agent: Audiocodes-Sip-Gateway/Mediant 2000/v.6.60.010.006 CSeq: 18154 BYE Supported: 100rel,em Content-Length: 0  F7 OK 200 - 10.8.201.10 to 10.8.201.108: SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud...
  • Page 24 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 25: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 27: Assigning The Oamp Lan Ip Address

    Connect one of the Ethernet ports located on the rear panel (labeled ETH) directly to the network interface of your computer, using a straight-through Ethernet cable. Change the IP address and subnet mask of your computer to correspond with the default IP address and subnet mask of the device. Version 6.6 Mediant 2000...
  • Page 28 Mediant 2000 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 Login screen appears: Figure 2-1: Web Login Screen In the 'Username' and 'Password' fields, enter the default login user name ("Admin"...

  • Page 29: Bootp/Tftp Server

    BootP/TFTP Server You can assign an IP address to the device using BootP/TFTP protocols. This can be done using the AudioCodes AcBootP utility (supplied) or any standard compatible BootP server. Note: You can also use the AcBootP utility to load the software file (.cmp) and configuration file (.ini).

  • Page 30: Cli

    Mediant 2000 Physically reset the device by powering it down and then up again. This enables the device to receive its new networking parameters through the BootP process. Repeat steps 2 through 6 for the device's second module (if used).

  • Page 31: Management Tools

    Part II Management Tools...

  • Page 33: Introduction

    Embedded HTTP/S-based Web server - see 'Web-based Management' on page  Command Line Interface (CLI) - see 'CLI-Based Management' on page  AudioCodes Element Management System - see EMS-Based Management on page  Simple Network Management Protocol (SNMP) browser software - see 'SNMP-Based Management' on page ...
  • Page 34 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 35: Web-Based Management

    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. 4.1.2 Accessing the Web Interface The procedure below describes how to access the Web interface. Version 6.6 Mediant 2000...

  • Page 36: Areas Of The Gui

    Mediant 2000  To access the Web interface: Open a standard Web browser (see 'Computer Requirements' on page 35). In the Web browser, specify the IP address of the device (e.g., http://10.1.10.10); the Web interface's Login window appears, as shown below:...
  • Page 37 4. Web-Based Management Description of the Web GUI Areas Item # Description Displays AudioCodes (corporate) logo image. Displays the product name. Toolbar, providing frequently required command buttons. For more information, see 'Toolbar Description' on page 38. Displays the username of the Web user that is currently logged in.

  • Page 38: Toolbar Description

    Mediant 2000 4.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see 'Saving Configuration' on page 396). Note: This icon is grayed out when not applicable to the currently opened page.

  • Page 39: Navigation Tree

    The expanded (Full) view displays all the menus pertaining to the selected configuration tab; the reduced (Basic) view displays only commonly used menus. This is relevant when using the configuration tabs Version 6.6 Mediant 2000...

  • Page 40: Showing / Hiding The Navigation Pane

    Mediant 2000 (i.e., Configuration, Maintenance, and Status & Diagnostics) on the Navigation bar. The advantage of the Basic view is that it prevents "cluttering" of the Navigation tree with menus that may not be required.  To toggle between Full and Basic view: ...

  • Page 41: Working With Configuration

    Certain pages may not be accessible or may be read-only, depending on the access level of your Web user account (see 'Configuring Web User Accounts' on page 60). If a page is read-only, "Read-Only Mode" is displayed at the bottom of the page. Version 6.6 Mediant 2000...

  • Page 42: Viewing Parameters

    Mediant 2000 4.1.6.2 Viewing Parameters Some pages allow you to view a reduced or expanded display of parameters. The Web interface provides two methods for displaying page parameters:  Displaying "basic" and "advanced" parameters - see 'Displaying Basic and Advanced Parameters' on page ...

  • Page 43: Modifying And Saving Parameters

    When you click Submit, modifications to parameters with on-the-fly capabilities are immediately applied to the device and take effect. Parameters displayed on the page with the lightning symbol take effect only after a device reset. For resetting the device, see 'Resetting the Device' on page 393. Version 6.6 Mediant 2000...

  • Page 44: Working With Tables

    Mediant 2000 Note: Parameters saved to the volatile memory (by clicking Submit), revert to their previous settings after a hardware or software reset, or if the device is powered down. Therefore, 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...
  • Page 45 Edit Edits the selected row. Delete Removes the selected row from the table. When you click this button, a confirmation box appears requesting you to confirm deletion. Click Delete to accept deletion. Version 6.6 Mediant 2000...
  • Page 46 Mediant 2000 Item # Button Toggles between displaying and hiding the full configuration of a Show/Hide selected row. This configuration is displayed below the table (see Item #6) and is useful for large tables that cannot display all its columns in the work pane.

  • Page 47: Searching For Configuration Parameters

    In the searched list, click the required parameter (green link) to open the page on which the parameter appears; the relevant page opens in the Work pane and the searched parameter is highlighted in the page for easy identification, as shown in the figure below: Figure 4-15: Searched Result Screen Version 6.6 Mediant 2000...

  • Page 48: Working With Scenarios

    Mediant 2000 Search Description Item # Description Search field for entering search key and Search button for activating the search process. Search results listed in Navigation pane. Found parameter, highlighted on relevant Web page 4.1.8 Working with Scenarios The Web interface allows you to create your own menu (Scenario) of up to 20 pages, selected from the menus in the Navigation tree (i.e., pertaining to the Configuration,...
  • Page 49 'Step Name' field for defining a name for a Scenario Step. Save & Finish button to save your Scenario. Selected parameter(s) that you want added to a Scenario Step. Next button to add the current Step to the Scenario and enables you to add additional Steps. Version 6.6 Mediant 2000...

  • Page 50: Accessing A Scenario

    Mediant 2000 Notes: • You can add up to 20 Steps per Scenario, where each Step can contain up to 25 parameters. • When in Scenario mode, the Navigation tree is in 'Full' display (i.e., all menus are displayed in the Navigation tree) and the configuration pages are in 'Advanced Parameter List' display (i.e., all parameters are shown in the pages).

  • Page 51: Editing A Scenario

    In the Navigation tree, select the required Step; the corresponding page opens in the Work pane. To add parameters, select the check boxes corresponding to the desired parameters. To remove parameters, clear the check boxes corresponding to the desired parameters. Click Next. Version 6.6 Mediant 2000...

  • Page 52: Saving A Scenario To A Pc

    Mediant 2000 • Edit Step Name: In the Navigation tree, select the required Step. In the 'Step Name' field, modify the Step name. On the page, click Next. • Edit Scenario Name: In the 'Scenario Name' field, edit the Scenario name.

  • Page 53: Loading A Scenario To The Device

    ScenarioFileName (see Web and Telnet Parameters on page 513). The Scenario file must be located in the same folder as the ini file. For information on using AudioCodes AcBootP utility, refer to AcBootP Utility User's Guide.

  • Page 54: Quitting Scenario Mode

    Mediant 2000 Note: You can also delete a Scenario using the following alternative methods: • Loading an empty dat file (see 'Loading a Scenario to the Device' on page 53). • Loading an ini file with the ScenarioFileName parameter set to no value (i.e., ScenarioFileName = "").

  • Page 55: 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.6 Mediant 2000...

  • Page 56: Getting Help

    Mediant 2000 4.1.10 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 57: Viewing The Home Page

    Displays the highest severity of an active alarm raised (if any) by the device:  Green = No alarms  Red = Critical alarm  Orange = Major alarm  Yellow = Minor alarm To view the active alarms, click this Alarms area to open the Active Alarms page Version 6.6 Mediant 2000...
  • Page 58 Mediant 2000 Item # Description (see Viewing Active Alarms on page 439). Blade Activity icon:  (green): Initialization sequence terminated successfully Blade Fail icon:  (gray): Normal functioning  (red): Blade failure T1/E1 Trunk Status icons for trunks 1 through 8.

  • Page 59: Assigning A Port Name

     To switch modules: In the Home page, click anywhere on the module to which you want to switch, as shown below: Figure 4-25: Click Module to which you want to Switch Version 6.6 Mediant 2000...

  • Page 60: Configuring Web User Accounts

    Mediant 2000 A confirmation message box appears requesting you to confirm switching of modules. Figure 4-26: Confirmation Message Box for Switching Modules Click OK; the Web Login screen of the switched module's Web interface appears. Enter the login username and password, and then click Login.

  • Page 61: Basic User Accounts Configuration

    For the Security Administrator, you can change only the username and password; not its access level. For the Monitor user, you can change username and password as well as access level (Administrator, Monitor, or No Access). Version 6.6 Mediant 2000...
  • Page 62 Mediant 2000 Notes: • The access level of the Security Administrator cannot be modified. • The access level of the second user account can be modified only by the Security Administrator. • The username and password can be a string of up to 19 characters. When you log in to the Web interface, the username and password string values are case- sensitive, according to your configuration.

  • Page 63: Advanced User Accounts Configuration

    (The Security Administrator users and Master users can change their passwords in the Web Users table and in the Web Security Settings page.) • This table can only be configured using the Web interface. Version 6.6 Mediant 2000...
  • Page 64 Mediant 2000  To add Web user accounts with advanced settings: Open the Web Users Table page: • Upon initial access: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). Under the Web Users Table group, click the Create Table button.
  • Page 65 Web interface. The valid value is 0 to 100000. The default is according to the settings of the 'Session Timeout' global parameter (see 'Configuring Web Security Settings' on page 67). Version 6.6 Mediant 2000...

  • Page 66: Displaying Login Information Upon Login

    Mediant 2000 Parameter Description Web: Block Duration Defines the duration (in seconds) for which the user is blocked when the user exceeds a user-defined number of failed login attempts. This is configured by the 'Deny Access On Fail Count' parameter (see 'Configuring Web Security Settings' on page 67).

  • Page 67: Configuring Web Security Settings

    Open the WEB Security Settings page (Configuration tab > System menu > Management submenu > WEB Security Settings). Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 396. Version 6.6 Mediant 2000...

  • Page 68: 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 69: Mediant

    PC is denied. • Delete your PC's IP address last from the 'Web & Telnet Access List page. If it is deleted before the last, subsequent access to the device from your PC is denied. Version 6.6 Mediant 2000...

  • Page 70: Configuring Radius Settings

    Mediant 2000 Configuring RADIUS Settings The RADIUS Settings page is used for configuring the Remote Authentication Dial In User Service (RADIUS) accounting parameters. For a description of these parameters, see 'Configuration Parameters Reference' on page 503.  To configure RADIUS: Open the RADIUS Settings page (Configuration tab >...

  • Page 71: Cli-Based Management

    TCP, providing methods for key exchange, authentication, encryption, and authorization. SSH requires appropriate client software for the management PC. Most Linux distributions have OpenSSH pre-installed; Windows-based PCs require an SSH client software such as PuTTY, which downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty/. Version 6.6 Mediant 2000...
  • Page 72 Mediant 2000 By default, SSH uses the same username and password as the Telnet and Web server. SSH supports 1024/2048-bit RSA public keys, providing carrier-grade security. Follow the instructions below to configure the device with an administrator RSA key as a means of strong authentication.

  • Page 73: Establishing A Cli Session

    Establish a Telnet or SSH session with the device using its OAMP IP address. Log in to the session using the username and password assigned to the Admin user of the Web interface. At the login prompt, type the username, and then press Enter: login: Admin Version 6.6 Mediant 2000...

  • Page 74: Cli Commands

    Mediant 2000 At the password prompt, type the password, and then press Enter: password: Admin After logging in, the current directory (root), available commands, available subdirectories, and a welcome message are displayed at the CLI prompt: login: Admin password: ready. Type "exit" to close the connection.
  • Page 75 DSP device 9: Inactive DSP device 10: Inactive DSP device 11: Inactive DSP device 12: Active Used=16 Free= 0 Total=16 DSP device 13: Active Used=16 Free= 0 Total=16 DSP device 14: Active Used=16 Free= 0 Total=16 Version 6.6 Mediant 2000...
  • Page 76 Mediant 2000 DSP device 15: Active Used=16 Free= 0 Total=16 DSP device 16: Active Used=16 Free= 0 Total=16 DSP device 17: Active Used=16 Free= 0 Total=16 DSP device 18: Inactive PSEC - DSP firmware: AC491IPSEC Version: 0660.03 CONFERENCE - DSP firmware: AC491256C Version: 0660.03 />sh dsp perf...

  • Page 77: Ping Command

    | set src | set cid | set DTMFs | display | connect Table 5: Sub-Commands of Test (TC) Command Sub-Command Arguments Description set dest <number> Sets the Destination Number for the test call. Version 6.6 Mediant 2000...

  • Page 78: Management Commands

    Mediant 2000 Sub-Command Arguments Description set src <number> Sets the Source Number for the test call. set cid <display string> Sets the Display Name for the test call. set DTMFs <DTMF pattern> Sets the pattern of DTMFs that is played to the PSTN side after the test call is connected.

  • Page 79: Configuration Commands

    2 = LINE_PAYLOAD_LOOP (whole trunk only)  3 = LOCAL_ALL_CHANNELS_LOOP (whole trunk only) PstnSendAlarm PS/PH/PSA <TrunkId> Sends an alarm signal at the Tx interface <AlarmSendCode> or on a specific Trunk ID. The valid value options for AlarmSendCode include the Version 6.6 Mediant 2000...

  • Page 80: Ldap Commands

    Mediant 2000 Command Short Arguments Description Format following:  0 = NO_ALARMS (means stop sending AIS)  1 = AIS_ALARM  2 = STOP_RAI_ALARM  3 = SEND_RAI_ALARM DeleteCasFile PS/CAS/DC <TableIndex> Deletes all the device's CAS files when <TableIndex> is set to -1 (other options are currently not supported).

  • Page 81: Snmp-Based Management

    Open the SNMP Community String page (Configuration tab > System menu > Management submenu > SNMP submenu > SNMP Community String). Configure the SNMP community strings parameters according to the table below. Click Submit to apply your changes. Version 6.6 Mediant 2000...

  • Page 82: Configuring Snmp Trap Destinations

    Mediant 2000 To save the changes to flash memory, see 'Saving Configuration' on page 396. To delete a community string, select the Delete check box corresponding to the community string that you want to delete, and then click Submit. SNMP Community String Parameters Description...

  • Page 83: Configuring Snmp Trusted Managers

    Security can be enhanced by using Trusted Managers, which is an IP address from which the SNMP agent accepts and processes SNMP requests. Notes: The SNMP Trusted Managers table can also be configured using the table ini file parameter, SNMPTrustedMgr_x (see 'SNMP Parameters' on page 517). Version 6.6 Mediant 2000...

  • Page 84: Configuring Snmp V3 Users

    Mediant 2000  To configure SNMP Trusted Managers: Open the SNMP Trusted Managers page (Configuration tab > System menu > Management submenu > SNMP submenu > SNMP Trusted Managers). Figure 6-2: 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.
  • Page 85 Keys are always persisted as long hex strings and keys are localized. Group The group with which the SNMP v3 user is associated. [SNMPUsers_Group]  [0] Read-Only (default)  [1] Read-Write  [2] Trap Note: All groups can be used to send traps. Version 6.6 Mediant 2000...
  • Page 86 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 87: Ems-Based Management

    User's Manual 7. EMS-Based Management EMS-Based Management AudioCodes Element Management System (EMS) is an advanced solution for standards- based management of gateways within VoP networks, covering all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of AudioCodes' families of gateways.
  • Page 88 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 89: 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 Version 6.6 Mediant 2000...
  • Page 90 Mediant 2000 configured. • 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 91: General Ini File Formatting Rules

    • Load Auxiliary Files - see 'Loading Auxiliary Files' on page  AudioCodes AcBootP utility, which uses Bootstrap Protocol (BootP) and acts as a TFTP server. For information on using the AcBootP utility, refer to AcBootP Utility User's Guide. ...

  • Page 92: Modifying An Ini File

    The file may be loaded to the device using TFTP or 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 93: General System Settings

    Part III General System Settings...

  • Page 95: Configuring Certificates

    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 9-1: Certificate Signing Request Group Version 6.6 Mediant 2000...

  • Page 96: Loading A Private Key

    Mediant 2000 Copy the text and send it to your security provider. The security provider, also known as Certification Authority or CA, signs this request and then sends you a server certificate for the device. Save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE"...
  • Page 97 (at the top of the page) the 'Private key' read-only field displays "OK"; otherwise, consult your security administrator. If the device was originally operating in HTTPS mode and you disabled it in Step 2, then enable it by setting the 'Secured Web Connection (HTTPS)' field to HTTPS Only. Version 6.6 Mediant 2000...

  • Page 98: Mutual Tls Authentication

    Mediant 2000 Mutual TLS Authentication By default, servers using TLS provide one-way authentication. The client is certain that the identity of the server is authentic. When an organizational PKI is used, two-way authentication may be desired - both client and server should be authenticated using X.509 certificates.
  • Page 99 Notes: • The device does not query OCSP for its own certificate. • Some PKIs do not support OCSP but generate Certificate Revocation Lists (CRLs). For such cases, set up an OCSP server such as OCSPD. Version 6.6 Mediant 2000...

  • Page 100: Self-Signed Certificates

    Mediant 2000 Self-Signed Certificates The device is shipped with an operational, self-signed server certificate. The subject name for this default certificate is 'ACL_nnnnnnn', where nnnnnnn denotes the serial number of the device. However, this subject name may not be appropriate for production and can be changed while still using self-signed certificates.

  • Page 101: Date And Time

    The client slowly robs bits from the clock counter to update the clock to the correct time. If the clock is running too slow, then in an effort to catch the clock up, bits are added Version 6.6 Mediant 2000...
  • Page 102 Mediant 2000 to the counter, causing the clock to update quicker and catch up to the correct time. The advantage of this method is that it does not introduce any disparity in the system time that is noticeable to an end user or that could corrupt call timeouts and timestamps.

  • Page 103: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 105: Network

    If this interface is connected, the whole start-up procedure is performed using it. If both interfaces are not connected, the start-up procedure commences using the parameters, tables, and software residing on the device's non-volatile memory. Note that Version 6.6 Mediant 2000...

  • Page 106: Configuring Ip Network Interfaces

    Mediant 2000 Ethernet switchover occurs only once during the start-up procedure (at the beginning). If the Ethernet interface fails after the selection is made, the device does not switch over to the second port. After start-up is complete and the operational software is running, the device continues to use the Ethernet port used for software upload.
  • Page 107 To configure firewall rules (access list) for allowing or blocking packets received from specific IP network interfaces, see 'Configuring Firewall Settings' on page 133. • The Multiple Interface table can also be configured using the table ini file parameter, InterfaceTable (see 'Networking Parameters' on page 503). Version 6.6 Mediant 2000...
  • Page 108 Mediant 2000  To configure IP network interfaces: Open the IP Settings page (Configuration tab > VoIP menu > Network submenu > IP Settings). Figure 11-2: IP Settings Page (Single Network Interface) Note: The IP Settings page appears only in the following circumstances: •...
  • Page 109 The CIDR-style presentation is the latest method for interpretation of IP addresses. Specifically, instead of using eight-bit address blocks, it uses the variable- length subnet masking technique to allow allocation on arbitrary-length prefixes. Version 6.6 Mediant 2000...
  • Page 110 Mediant 2000 Parameter Description The prefix length for IPv4 can range from 0 to 30. Note: For valid configuration, see Multiple Interface Table Configuration Rules on page 111. Web/EMS: Gateway Defines the IP address of the default gateway for the interface. When [InterfaceTable_Gate traffic is sent from this interface to an unknown destination (i.e., not in the...

  • Page 111: Assigning Ntp Services To Application Types

    One or more combined Media-Control interfaces with IPv4 addresses.  Each network interface can be configured with a Default Gateway. The address of the Default Gateway must be in the same subnet as the associated interface. Additional Version 6.6 Mediant 2000...

  • Page 112: Troubleshooting The Multiple Interface Table

    Mediant 2000 static routing rules can be configured in the IP Routing table.  The interface name must be configured (mandatory) and unique for each interface, and can include up to 16 characters.  For IPv4 addresses, the 'Interface Mode' column must be set to IPv4 Manual (numeric value 10).

  • Page 113: One Voip Interface For All Applications

    Management interface (configured for Index 0): • 'VLAN Mode' is set to Enable. • 'Native VLAN ID' field is set to "1". IP Routing table: A routing rule is required to allow remote management from a host in 176.85.49.0 / 24: Version 6.6 Mediant 2000...

  • Page 114: Voip Interfaces For Combined Application Types

    Mediant 2000 Example IP Routing Table Destination IP Gateway IP Interface Prefix Length Metric Address Address Name 176.85.49.0 192.168.0.1 All other parameters are set to their respective default values. The NTP application remains with its default application types. 11.3.4.3 VoIP Interfaces for Combined Application Types...

  • Page 115: Configuring The Ip Routing Table

    If no explicit entry is found, the packet is sent to the default gateway.  To configure static IP routing: Open the IP Routing Table page (Configuration tab > VoIP menu > Network submenu > IP Routing Table). Figure 11-5: IP Routing Table Page Version 6.6 Mediant 2000...
  • Page 116 Mediant 2000 In the Add a new table entry table, add a new static routing rule according to the parameters described in the table below. Click Add New Entry; the new routing rule is added to the IP routing table.

  • Page 117: Interface Column

    'Interface Name' field.  The 'Metric; field must be set to 1.  For the configuration settings to take effect, you must reset the device with a "burn" to flash memory. Version 6.6 Mediant 2000...

  • Page 118: Troubleshooting The Routing Table

    Mediant 2000 11.4.3 Troubleshooting the Routing Table When adding a new static routing rule, the added rule passes a validation test. If errors are found, the routing rule is rejected and is not added to the IP Routing table. Failed routing validations may result in limited connectivity (or no connectivity) to the destinations specified in the incorrect routing rule.
  • Page 119 Open the QoS Settings page (Configuration tab > VoIP menu > Network submenu > QoS Settings). Configure the QoS parameters as required. Click Submit to apply your changes. Save the changes to flash memory (see 'Saving Configuration' on page 396). Version 6.6 Mediant 2000...

  • Page 120: Disabling Icmp Redirect Messages

    Mediant 2000 11.6 Disabling ICMP Redirect Messages You can configure the device's handling of ICMP Redirect messages. These messages can either be rejected (ignored) or permitted. Note: You can also configure this feature using the ini file parameter DisableICMPRedirects (see 'Routing Parameters' on page 505).
  • Page 121 Defines the third IP address (in dotted-decimal format notation) to [Dns2Ip_ThirdIpAddress] which the host name is translated. Fourth IP Address Defines the fourth IP address (in dotted-decimal format notation) [Dns2Ip_FourthIpAddress] to which the host name is translated. Version 6.6 Mediant 2000...

  • Page 122: Configuring The Internal Srv Table

    Mediant 2000 11.7.2 Configuring the Internal SRV Table The Internal SRV Table page resolves host names to DNS A-Records. Three different A- Records can be assigned to each host name, where each A-Record contains the host name, priority, weight, and port.

  • Page 123: Configuring Nfs Settings

    Open the Application Settings page (Configuration tab > System menu > Application Settings). Under the 'NFS Settings' group, click the NFS Table button; the NFS Table page appears. Click the Add button; the Add Record dialog box appears: Figure 11-9: Add Record Dialog Box for NFS Version 6.6 Mediant 2000...
  • Page 124 Mediant 2000 Configure the NFS parameters according to the table below. Click the Submit button; the remote NFS file system is immediately applied, which can be verified by the appearance of the 'NFS mount was successful' message in the Syslog server.

  • Page 125: Network Address Translation Support

    IP address configured in the Multiple Interface table. he figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 11-10: Device behind NAT and NAT Issues Version 6.6 Mediant 2000...

  • Page 126: Configuring Stun

    Mediant 2000 11.9.1.1 Configuring STUN Simple Traversal of UDP through NATs (STUN), based on RFC 3489 is a client / server protocol that solves most of the NAT traversal problems. The STUN server operates in the public Internet and the STUN clients are embedded in end-devices located behind NAT.

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

    The device's NAT traversal mechanism replaces the source IP address of SIP messages sent from a specified VoIP interface to a public IP address. Note: The NAT Translation table can also be configured using the table ini file parameter, NATTranslation. Version 6.6 Mediant 2000...
  • Page 128 Mediant 2000  To configure NAT translation rules: Open the NAT Translation Table page (Configuration tab > VoIP menu > Control Network submenu > NAT Translation Table). Click the Add button; the following dialog box appears: Figure 11-13: NAT Translation Table Page Configure the parameters as required.

  • Page 129: Remote Ua Behind Nat

    To enable NAT resolution using the First Incoming Packet mechanism: Open the General Media Settings page (Configuration tab > VoIP menu > Media > General Media Settings). Set the 'NAT Traversal' parameter to Enable. Click Submit. Version 6.6 Mediant 2000...

  • Page 130: No-Op Packets

    Receipt of No-Op packets is always supported. 11.10 Robust Receipt of Media Streams The “robust-media” mechanism is an AudioCodes proprietary mechanism to filter out unwanted media (i.e., RTP, RTCP, and T.38) streams that are sent to the same port number on the device. In practice, the media RTP/RTCP ports may receive additional multiple unwanted media streams as result of traces of previous calls, call control errors, or deliberate attacks.

  • Page 131: Multiple Routers Support

    Multiple Routers support is an integral feature that doesn’t require configuration. 11.12 IP Multicasting The device supports IP Multicasting level 1, according to RFC 2236 (i.e., IGMP version 2) for RTP channels. The device is capable of transmitting and receiving multicast packets. Version 6.6 Mediant 2000...
  • Page 132 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 133: Security

    - Start Port - End Port: 0-65535 - Protocol: Any - Action Upon Match: Block • You can also configure the firewall settings using the table ini file parameter, AccessList (see 'Security Parameters' on page 528). Version 6.6 Mediant 2000...
  • Page 134 Mediant 2000  To add firewall rules: Open the Firewall Settings page (Configuration tab > VoIP menu > Security submenu > Firewall Settings). Click the Add button; the following dialog box appears: Figure 12-1: Firewall Settings Page - Add Record Configure the firewall parameters, as required.
  • Page 135 Defines the destination UDP/TCP end port (on this device) to where [AccessList_End_Port] packets are sent. The valid range is 0 to 65535. Note: When the protocol type isn't TCP or UDP, the entire range must be provided. Version 6.6 Mediant 2000...
  • Page 136 Mediant 2000 Parameter Description Protocol Defines the protocol type (e.g., UDP, TCP, ICMP, ESP or 'Any') or [AccessList_Protocol] the IANA protocol number in the range of 0 (Any) to 255. Note: This field also accepts the abbreviated strings 'SIP' and 'HTTP'.

  • Page 137: Configuring General Security Settings

    IPSec to encrypt the IP stream. IKE negotiation comprises the following two phases:  Main Mode (creates a secured channel for the Quick mode by obtaining a "master" encryption key, without any prior keys, and authenticates the peers to each other): Version 6.6 Mediant 2000...

  • Page 138: Enabling Ipsec

    Mediant 2000 • SA negotiation: The peers negotiate their capabilities using up to four proposals. Each proposal includes the Encryption method, Authentication algorithm, and the Diffie-Hellman (DH) group. The master key’s lifetime is also negotiated. • Key exchange (DH): The DH protocol creates the master key. DH requires both peers to agree on certain mathematical parameters, known as the "group".

  • Page 139: Configuring Ip Security Proposal Table

    Defines the length of the key created by the DH protocol for up to four [IPsecProposalTable_DH proposals. For the ini file parameter, X denotes the proposal number Group] (0 to 3).  [0] Group 1 (768 Bits) = DH-786-Bit  [1] Group 2 (1024 Bits) (default) = DH-1024-Bit Version 6.6 Mediant 2000...

  • Page 140: Configuring Ip Security Associations Table

    Mediant 2000 If no proposals are defined, the default settings (shown in the following table) are applied. Default IPSec/IKE Proposals Proposal Encryption Authentication DH Group Proposal 0 3DES SHA1 Group 2 (1024 bit) Proposal 1 3DES Group 2 (1024 bit)
  • Page 141 Defines the method for peer authentication during IKE main mode. [IPsecSATable_Authentic  [0] Pre-shared Key (default) ationMethod]  [1] RSA Signature = in X.509 certificate Note: For RSA-based authentication, both peers must be provisioned with certificates signed by a common CA. For more information on Version 6.6 Mediant 2000...
  • Page 142 Mediant 2000 Parameter Name Description certificates, see 'Replacing the Device's Certificate' on page 95. Shared Key Defines the pre-shared key (in textual format). Both peers must use [IPsecSATable_SharedK the same pre-shared key for the authentication process to succeed. Notes: ...
  • Page 143 Note: This parameter is applicable only if the Operational Mode is set to Tunnel. Interface Name Assigns a network interface to this IPSec rule. The network interfaces [IPsecSATable_Interface are defined in the Multiple Interface table ('Interface Name' column) in Name] 'Configuring IP Network Interfaces' on page Version 6.6 Mediant 2000...

  • Page 144: Intrusion Detection System

    Mediant 2000 12.4 Intrusion Detection System The device can be configured to detect malicious attacks on its system and send SNMP traps if malicious activity is identified. The Intrusion Detection System (IDS) is an important feature for Enterprises to ensure legitimate calls are not being adversely affected by attacks and to prevent Theft of Service and unauthorized access.

  • Page 145: Configuring Ids Policies

    Intrusion Detection and Prevention > Policy Table). Figure 12-6: IDS Policy Table with Default Rules Add a Policy name: Click Add. Figure 12-7: IDS Policy Table - Add Record Configure the parameters as described in the following table, and then click Submit. Version 6.6 Mediant 2000...
  • Page 146 Mediant 2000 Table 12-1: IDS Policy Table Parameters Parameter Description Index Defines the table row number for the policy. CLI: policy [IDSPolicy_Index] Name Defines a name for the policy. CLI: rule The valid value is a string of up to 20 characters.
  • Page 147 Defines the threshold interval (in seconds) during which the device CLI: threshold-window counts the attacks to check if a threshold is crossed. The counter is [IDSRule_ThresholdWindo automatically reset at the end of the interval. The valid range is 1 to 1,000,000. The default is 1. Version 6.6 Mediant 2000...

  • Page 148: Assigning Ids Policies

    Mediant 2000 Parameter Description Minor-Alarm Threshold Defines the threshold that if crossed a minor severity alarm is sent. CLI: minor-alrm-thr The valid range is 1 to 1,000,000. A value of 0 or -1 means not [IDSRule_MinorAlarmThre defined. shold] Major-Alarm Threshold Defines the threshold that if crossed a major severity alarm is sent.
  • Page 149 10.1.0.0/16 and IP address 10.2.2.2. Note that the exclamation mark "!" appears before each subnet.  10.1.0.0/16 & !10.1.1.1: includes subnet 10.1.0.0/16, except IP address 10.1.1.1. Policy Selects the IDS policy, configured in 'Configuring IDS Policies' on CLI: policy page 145. [IDSMatch_Policy] Version 6.6 Mediant 2000...

  • Page 150: Viewing Ids Alarms

    Mediant 2000 12.4.4 Viewing IDS Alarms The device uses SNMP (and Syslog) to notify the detection of malicious attacks. The trap displays the IDS Policy and Rule, and the Policy-Match index. The device sends the SNMP alarm, acIDSPolicyAlarm whenever a threshold of a specific IDS Policy rule is crossed.
  • Page 151 Remote rejects (prior to SIP 180 response) establish-remote-reject   Requests and responses without a matching flow-no-match-tu Abnormal Flow transaction user (except ACK requests)  flow-no-match-  Requests and responses without a matching transaction transaction (except ACK requests) Version 6.6 Mediant 2000...
  • Page 152 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 153: Media

    'Voice Volume' (VoiceVolume) - Defines the voice gain control (in decibels) for IP- to-Tel • 'Input Gain' (InputGain) - Defines the PCM input gain control (in decibels) for Tel- to-IP Click Submit to apply your settings. Version 6.6 Mediant 2000...

  • Page 154: Silence Suppression (Compression)

    Mediant 2000 13.1.2 Silence Suppression (Compression) Silence suppression (compression) is a method for conserving bandwidth on VoIP calls by not sending packets when silence is detected. The device uses its VAD feature to detect periods of silence in the voice channel during an established call. When silence is detected, it stops sending packets in the channel.

  • Page 155: Fax And Modem Capabilities

    'Configuration Parameters Reference' on page 503.  To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Configuration tab > VoIP menu > Media submenu > Fax/Modem/CID Settings). Figure 13-5: Fax/Modem/CID Settings Page Configure the parameters, as required. Version 6.6 Mediant 2000...

  • Page 156: Fax/Modem Operating Modes

    Mediant 2000 Click Submit to apply your changes. 13.2.1 Fax/Modem Operating Modes The device supports two modes of operation:  Fax/modem negotiation that is not performed during the establishment of the call.  Voice-band data (VBD) mode for V.152 implementation (see 'V.152 Support' on page 164): fax/modem capabilities are negotiated between the device and the remote endpoint at the establishment of the call.

  • Page 157: Mediant

    In the Fax/Modem/CID Settings page, set the 'Fax Transport Mode' parameter to RelayEnable (FaxTransportMode = 1). Configure the following optional parameters: • 'Fax Relay Redundancy Depth' (FaxRelayRedundancyDepth) • 'Fax Relay Enhanced Redundancy Depth' (FaxRelayEnhancedRedundancyDepth) • 'Fax Relay ECM Enable' (FaxRelayECMEnable) Version 6.6 Mediant 2000...

  • Page 158: Fax / Modem Transport Mode

    Mediant 2000 • 'Fax Relay Max Rate' (FaxRelayMaxRate) 13.2.2.2 G.711 Fax / Modem Transport Mode In this mode, when the terminating device detects fax or modem signals (CED or AnsAM), it sends a Re-INVITE message to the originating device, requesting it to re-open the channel in G.711 VBD with the following adaptations:...

  • Page 159: Fax/Modem Bypass Mode

    Configure the following optional parameters: • 'Fax/Modem Bypass Coder Type' (FaxModemBypassCoderType). • 'Fax Bypass Payload Type' (FaxBypassPayloadType) - in the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). • ModemBypassPayloadType (ini file). Version 6.6 Mediant 2000...

  • Page 160: Fax / Modem Nse Mode

    INVITE messages are sent. The voice channel is optimized for fax/modem transmission (same as for usual bypass mode). The parameters defining payload type for AudioCodes proprietary Bypass mode -- 'Fax Bypass Payload Type' (RTP/RTCP Settings page) and ModemBypassPayloadType (ini file) -- are not used with NSE Bypass.

  • Page 161: Fax / Modem Transparent With Events Mode

    In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to No Fax (IsFaxUsed = 0). In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Version 6.6 Mediant 2000...

  • Page 162: Rfc 2833 Ans Report Upon Fax/Modem Detection

    Mediant 2000 Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0).

  • Page 163: Bypass Mechanism For V.34 Fax Transmission

    Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0). Version 6.6 Mediant 2000...

  • Page 164: Support

    Mediant 2000 13.2.4 V.152 Support The device supports the ITU-T recommendation V.152 (Procedures for Supporting Voice- Band Data over IP Networks). Voice-band data (VBD) is the transport of modem, facsimile, and text telephony signals over a voice channel of a packet network with a codec appropriate for such signals.

  • Page 165: Configuring Rtp/Rtcp Settings

    - only when the Jitter Buffer is completely empty or completely full. When such condition occurs, the correction is performed by dropping several voice packets simultaneously or by adding several BFI packets simultaneously, so that the Jitter Buffer returns to its normal condition. Version 6.6 Mediant 2000...

  • Page 166: Comfort Noise Generation

    Mediant 2000 The procedure below describes how to configure the jitter buffer using the Web interface.  To configure jitter buffer using the Web interface: Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media submenu > RTP/RTCP Settings). The relevant parameters are listed under the...

  • Page 167: Dual-Tone Multi-Frequency Signaling

    Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the '1st Tx DTMF Option' parameter to Not Supported (TxDTMFOption = 0). Set the ini file parameter, DTMFTransportType to 2 (i.e., transparent). Version 6.6 Mediant 2000...

  • Page 168: Configuring Rfc 2833 Payload

    Mediant 2000  Using INFO message according to Korea mode: DTMF digits are sent to the remote side in INFO messages. To enable this mode, define the following: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0).

  • Page 169: Rtp Multiplexing (Throughpacket)

    The device's RTP Multiplexing (ThroughPacket™) feature is AudioCodes proprietary method for aggregating RTP streams from several channels when the device operates with another AudioCodes device. This feature reduces the bandwidth overhead caused by the attached Ethernet, IP, UDP, and RTP headers and reduces the packet/data transmission rate.

  • Page 170: Configuring Rtp Base Udp Port

    Mediant 2000 Click Submit. Reset the device for the settings to take effect. 13.3.5 Configuring RTP Base UDP Port You can configure the range of UDP ports for RTP, RTCP, and T.38. The UDP port range can be configured using media realms in the Media Realm table, allowing you to assign different port ranges (media realms) to different interfaces.

  • Page 171: Configuring Ip Media Settings

    To enable the AMD beep detection, the X-Detect header in the received INVITE message must include “Request=AMD”, and the AMDBeepDetectionMode parameter must be set to 1 or 2. If set to 1, the beep is detected only after Answering Version 6.6 Mediant 2000...
  • Page 172 Mediant 2000 Machine detection. If set to 2, the beep is detected even if the Answering Machine was not detected.  Using the Call Progress Tone detector: To enable this detection mode, the X- Detect header in the received INVITE message must include “Request=CPT”, and one or several beep tones (Tone Type #46) must be configured in the regular CPT file.
  • Page 173 English. If you want to implement AMD in a different language or region, you must provide AudioCodes with a database of recorded voices in the language on which the device's AMD mechanism can base its voice detector algorithms for detecting these voices.
  • Page 174 Mediant 2000 Upon detection by the device of the answering machine, the device sends a SIP INFO message to the Application server: INFO sip:sipp@172.22.2.9:5060 SIP/2.0 Via: SIP/2.0/UDP 172.22.168.249;branch=z9hG4bKac1566945480 Max-Forwards: 70 From: sut <sip:3000@172.22.168.249:5060>;tag=1c1505895240 To: sipp <sip:sipp@172.22.2.9:5060>;tag=1 Call-ID: 1-29758@172.22.2.9 CSeq: 1 INFO Contact: <sip:56700@172.22.168.249>...

  • Page 175: Automatic Gain Control (Agc)

    'AGC Slope' (AGCGainSlope) - Determines the AGC convergence rate. • 'AGC Redirection' (AGCRedirection) - Determines the AGC direction. • 'AGC Target Energy' - Defines the signal energy value (dBm) that the AGC attempts to attain. Click Submit to apply your settings. Version 6.6 Mediant 2000...

  • Page 176: Configuring Dsp Templates

    Mediant 2000 Note: Below are additional AGC parameters: • AGCMinGain - Defines the minimum gain (in dB) by the AGC when activated • AGCMaxGain - Defines the maximum gain (in dB) by the AGC when activated. • AGCDisableFastAdaptation - Enables the AGC Fast Adaptation mode 13.5...

  • Page 177: Configuring Media Realms

    If different Media Realms are assigned to an IP Group and to an SRD, the IP Group’s Media Realm takes precedence. • For this setting to take effect, a device reset is required. • The Media Realm table can also be configured using the table ini file parameter, CpMediaRealm. Version 6.6 Mediant 2000...
  • Page 178 Mediant 2000  To define a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > Media submenu > Media Realm Configuration). Click the Add button; the following appears: Figure 13-15: Media Realm Page - Add Record Dialog Box Configure the parameters as required.

  • Page 179: Configuring Bandwidth Management Per Media Realm

    This feature is available only if the device is installed with the relevant Software License Key. • For your bandwidth management settings to take effect, you must reset the device. • You can also use the BWManagement ini file parameter to configure bandwidth management per Media Realm. Version 6.6 Mediant 2000...
  • Page 180 Mediant 2000  To configure bandwidth management rules per Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > Media submenu > Media Realm Configuration). Select the Media Realm for which you want to configure bandwidth management rules, and then click the Bandwidth Management link;...

  • Page 181: Configuring Media Security

    Notes: • For a detailed description of the SRTP parameters, see SRTP Parameters on page 530. • When SRTP is used, the channel capacity may be reduced. Version 6.6 Mediant 2000...
  • Page 182 Mediant 2000  To configure media security: Open the Media Security page (Configuration tab > VoIP menu > Media submenu > Media Security). Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 396.

  • Page 183: Services

    The LDAP Settings page is used for configuring the LDAP server parameters. For a full description of these parameters, see 'Configuration Parameters Reference' on page 503. Version 6.6 Mediant 2000...

  • Page 184: Configuring The Device's Ldap Cache

    Mediant 2000  To configure the LDAP server parameters: Open the LDAP Settings page (Configuration tab > VoIP menu > Services submenu > LDAP Settings). Figure 14-1: LDAP Settings Page The read-only 'LDAP Server Status' field displays one of the following possibilities: •...
  • Page 185 LDAP server again. • For a full description of the cache parameters, see 'Configuration Parameters Reference' on page 503. Version 6.6 Mediant 2000...

  • Page 186: Active Directory Based Tel-To-Ip Routing For Microsoft Lync

    Mediant 2000  To configure the LDAP cache parameters: Open the LDAP Settings page (Configuration tab > VoIP menu > Services submenu > LDAP Settings). Figure 14-3: LDAP Settings Page - Cache Parameters Configure the parameters as required. Click Submit to apply your changes.
  • Page 187 MSLDAPPrivateNumAttributeName, only if the query key (primary or secondary) is equal to its value. If the query is found: The AD returns up to four attributes - Lync / OCS, PBX / IP PBX, private (only if it equals Primary or Secondary key), and mobile. Version 6.6 Mediant 2000...
  • Page 188 Mediant 2000 The device adds unique prefix keywords to the query results in order to identify the query type (i.e., IP domain). These prefixes are used as the prefix destination number value in the Outbound IP Routing table to denote the IP domains: •...

  • Page 189: Configuring Ad-Based Routing Rules

    Configure the AD attribute names used in the LDAP query: Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions submenu > Advanced Parameters). Figure 14-5: LDAP Parameters for Microsoft Lync Server 2010 Configure the LDAP attribute names as desired. Version 6.6 Mediant 2000...
  • Page 190 Mediant 2000 Configure AD-based Tel-to-IP routing rules: Open the Outbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP submenu > Routing > Tel to IP Routing). For more information, see Configuring Outbound IP Routing Table on page 309.

  • Page 191: Querying The Ad For Calling Name

    • The Calling Name Manipulation Table for Tel -> IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value. Version 6.6 Mediant 2000...

  • Page 192: Least Cost Routing

    Mediant 2000 14.2 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how to configure it. 14.2.1 Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost.
  • Page 193 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.6 Mediant 2000...

  • Page 194: Configuring Lcr

    Mediant 2000  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: Connection...
  • Page 195 [0] Lowest Cost = If the device locates other matching LCR routing rules, this routing rule is considered the lowest cost route and therefore, it is selected as the route to use (default.)  [1] Highest Cost = If the device locates other matching LCR routing Version 6.6 Mediant 2000...

  • Page 196: Configuring Cost Groups

    Mediant 2000 Parameter Description rules, this routing rule is considered as the highest cost route and therefore, is not used or used only if the other cheaper routes are unavailable. Note: If more than one valid routing rule without a defined Cost Group exists, the device selects the first-matched rule.

  • Page 197: Configuring Time Bands For Cost Groups

    Click the Add button; the Add Record dialog box appears: Configure the parameters as required. For a description of the parameters, see the table below. Click Submit; the entry is added to the Time Band table for the relevant Cost Group. Version 6.6 Mediant 2000...

  • Page 198: Assigning Cost Groups To Routing Rules

    Mediant 2000 Time Band Table Description Parameter Description Index Defines the table index entry. [CostGroupTimebands _TimebandIndex] Start Time Defines the day and time of day from when this time band is applicable. [CostGroupTimebands The format is ddd:hh:mm (e.g., sun:06:00), where: _StartTime] ...

  • Page 199: Enabling Applications

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling submenu > Applications Enabling). From the relevant application drop-down list, select Enable. Save (burn) the changes to the device's flash memory with a device reset (see 'Saving Configuration' on page 396). Version 6.6 Mediant 2000...
  • Page 200 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 201: Control Network

    Open the SRD Settings page (Configuration tab > VoIP menu > Control Network submenu > SRD Table). From the 'SRD Index' drop-down list, select an index for the SRD, and then configure it according to the table below. Version 6.6 Mediant 2000...

  • Page 202: Configuring Sip Interface Table

    Mediant 2000 Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 396. SRD Table Parameters Parameter Description SRD Name Mandatory descriptive name of the SRD. [SRD_Name] The valid value can be a string of up to 21 characters.
  • Page 203 Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). TLS Port Defines the listening TLS port. [SIPInterface_TLSPort] The valid range is 1 to 65534. The default is 5061. Notes: Version 6.6 Mediant 2000...

  • Page 204: Configuring Ip Groups

    Mediant 2000 Parameter Description  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). Assigns an SRD ID to the SIP Interface.
  • Page 205 > IP Group Table). Click the Add button: the following dialog box appears: Configure the IP Group parameters according to the table below. Click Submit. To save the changes to flash memory, see 'Saving Configuration' on page 396. Version 6.6 Mediant 2000...
  • Page 206 Mediant 2000 IP Group Parameters Parameter Description Common Parameters Type Defines the type of IP Group: [IPGroup_Type]  [0] Server = Used when the destination address, configured by the Proxy Set, of the IP Group (e.g., ITSP, Proxy, IP-PBX, or Application server) is known.
  • Page 207 For configuring Media Realms, see Configuring Media Realms on page 177. IP Profile ID Assigns an IP Profile to the IP Group. [IPGroup_ProfileId] The default is 0. Note: To configure IP Profiles, see 'Configuring IP Profiles' on page 235. Gateway Parameters Version 6.6 Mediant 2000...
  • Page 208 Mediant 2000 Parameter Description Always Use Route Table Defines the Request-URI host name in outgoing INVITE messages. [IPGroup_AlwaysUseRo  [0] No (default). uteTable]  [1] Yes = The device uses the IP address (or domain name) defined in the Outbound IP Routing Table (see Configuring the Outbound IP...

  • Page 209: Configuring Proxy Sets Table

    204). When the device sends an INVITE message to an IP Group, it is sent to the IP address or domain name defined for the Proxy Set that is associated with the IP Group. In other words, the Proxy Set represents the destination of the call. Typically, for IP-to-IP call Version 6.6 Mediant 2000...
  • Page 210 Mediant 2000 routing, at least two Proxy Sets are defined for call destination – one for each leg (IP Group) of the call (i.e., both directions). For example, one Proxy Set for the Internet Telephony Service provider (ITSP) interfacing with one 'leg' of the device and another Proxy Set for the second SIP entity (e.g., ITSP) interfacing with the other 'leg' of the device.
  • Page 211 Defines the transport type of the proxy server. [ProxyIp_TransportT  [0] UDP ype]  [1] TCP  [2] TLS  [-1] = Undefined Note: If no transport type is selected, the value of the global parameter Version 6.6 Mediant 2000...
  • Page 212 Mediant 2000 Parameter Description SIPTransportType is used. Web/EMS: Enable Enables the Keep-Alive mechanism with the Proxy server(s). Proxy Keep Alive  [0] Disable (default). [ProxySet_EnablePr  [1] Using Options = Enables Keep-Alive with Proxy using SIP OPTIONS oxyKeepAlive] messages. ...
  • Page 213 Defines the SRD associated with the Proxy Set ID. [ProxySet_ProxySet_ The default is SRD 0. SRD] Notes:  For this parameter to take effect, a device reset is required.  To configure SRDs, see Configuring SRD Table on page 201. Version 6.6 Mediant 2000...
  • Page 214 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 215: Sip Definitions

    Of-Service if the OOSOnRegistrationFail parameter is set to 1 (see 'Proxy & Registration Parameters' on page 218). Notes: • For viewing Account registration status, see Viewing Endpoint Registration Status on page 452. • The Account table can also be configured using the table ini file parameter, Account. Version 6.6 Mediant 2000...
  • Page 216 Mediant 2000  To configure Accounts: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions submenu > Account Table). In the 'Add' field, enter the desired table row index, and then click Add. A new row appears.
  • Page 217 Group table is used instead.  If registration fails, then the user part in the INVITE Contact header contains the source party number. Application Type Defines the application type: [Account_Applicat  [0] GW/IP2IP = (Default) Gateway and IP-to-IP application. ionType] Version 6.6 Mediant 2000...

  • Page 218: Configuring Proxy And Registration Parameters

    Mediant 2000 17.3 Configuring Proxy and Registration Parameters The Proxy & Registration page allows you to configure the Proxy server and registration parameters. For a description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 503.

  • Page 219: 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 2000/v.6.60.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 220 • 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 221: Configuring Sip Message Manipulation

    IP Group (in the IP Group table). In other words, manipulation can be done per destination IP Group. If this parameter is not configured, see below. According to the settings of the "global" parameter, GWOutboundManipulationSet. If this parameter is not configured, no manipulation is done. Version 6.6 Mediant 2000...
  • Page 222 Mediant 2000 The figure below illustrates a SIP message manipulation example: Figure 17-1: SIP Header Manipulation Example Notes: • For a detailed description of the syntax for configuring SIP message manipulation rules, refer to SIP Message Manipulations Quick Reference Guide.
  • Page 223 Manipulation Set ID is used to assign the manipulation rules to an IP s_ManSetID] Group (in the IP Group table) for inbound and/or outbound messages. The valid value is 0 to 19. The default is 0. Matching Characteristics Version 6.6 Mediant 2000...
  • Page 224 Mediant 2000 Parameter Description Message Type Defines the SIP message type that you want to manipulate. [MessageManipulation The valid value is a string denoting the SIP message. s_MessageType] For example:  Empty = rule applies to all messages  Invite = rule applies to all INVITE requests and responses ...

  • Page 225: Configuring Sip Message Policy Rules

    Option to send 400 "Bad Request" response if message request is rejected  Blacklist and whitelist for defined SIP methods (e.g., INVITE)  Blacklist and whitelist for defined SIP bodies Note: The Message Policy table can also be configured using the table ini file parameter, MessagePolicy. Version 6.6 Mediant 2000...
  • Page 226 Mediant 2000  To configure SIP message policy rules: Open the Message Policy Table page (Configuration tab > VoIP menu > SIP Definitions > Msg Policy & Manipulation > Message Policy Table). Click the Add button; the Add Record dialog box appears:...
  • Page 227 [0] Policy Blacklist =The specified SIP body (in the 'Body List' field) is istType] rejected by the policy.  [1] Policy Whitelist = (Default) The specified SIP body (in the 'Body List' field) is allowed by the policy. Version 6.6 Mediant 2000...
  • Page 228 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 229: Coders And Profiles

    'Configuring Coder Groups' on page 232. • For information on V.152 and implementation of T.38 and VBD coders, see 'Supporting V.152 Implementation' on page 164. • The Coders table can also be configured using the table ini file parameter, CodersGroup. Version 6.6 Mediant 2000...
  • Page 230 Mediant 2000  To configure the device's coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles submenu > Coders). Figure 18-1: Coders Table Page From the 'Coder Name' drop-down list, select the required coder. From the 'Packetization Time' drop-down list, select the packetization time (in msec) for the selected coder.
  • Page 231 15 (default) Dynamic (0- [iLBC] 100, 120 127)  [1] Enable 30 (default), 60, 90, 120  [0] Disable Transparent 10, 20 (default), 40, 60, 80, Dynamic (0- [Transparent] 100, 120 127)  [1] Enable T.38 [t38fax] Version 6.6 Mediant 2000...

  • Page 232: Configuring Coder Groups

    Mediant 2000 18.2 Configuring Coder Groups The Coder Group Settings page allows you to define up to 10 groups of coders (termed Coder Groups). For each Coder Group, you can define up to 10 coders configured with packetization time (ptime), rate, payload type, and silence suppression. The first coder in the Coder Group table has the highest priority and is used by the device whenever possible.

  • Page 233: Configuring Tel Profile

    Trunk Group Table on page 279)). The procedure below describes how to configure Tel Profiles using the Web interface. Note: Tel Profiles can also be configured using the table ini file parameter, TelProfile (see 'Configuration Parameters Reference' on page 503) Version 6.6 Mediant 2000...
  • Page 234 Mediant 2000  To configure Tel Profiles: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > Tel Profile Settings). Figure 18-3: Tel Profile Settings Page From the 'Profile ID' drop-down list, select the Tel Profile index.

  • Page 235: Configuring Ip Profiles

    [0] don’t declare RFC 2833; [1] declare RFC 2833 payload type is SDP. • You can also configure IP Profiles using the table ini file parameter, IPProfile (see Configuration Parameters Reference on page 503). Version 6.6 Mediant 2000...
  • Page 236 Mediant 2000  To configure IP Profiles: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > IP Profile Settings). From the 'Profile ID' drop-down list, select the IP Profile index. In the 'Profile Name' field, enter an arbitrary name that allows you to easily identify the IP Profile.
  • Page 237 For a description, see the global parameter [IpProfile_MKISize] SRTPTxPacketMKISize. Gateway Parameters Web: Fax Signaling Method For a description, see the global parameter IsFaxUsed. [IpProfile_IsFaxUsed] Web: Play Ringback Tone to IP For a description, see the global parameter PlayRBTone2IP. [IpProfile_PlayRBTone2IP] Version 6.6 Mediant 2000...
  • Page 238 Mediant 2000 Parameter Description Web: Enable Early Media For a description, see the global parameter EnableEarlyMedia. [IpProfile_EnableEarlyMedia] Web: Copy Destination Number to For a description, see the global parameter Redirect Number CopyDest2RedirectNumber. [IpProfile_CopyDest2RedirectN umber] Web: Media Security Behavior For a description, see the global parameter [IpProfile_MediaSecurityBehavi MediaSecurityBehaviour.
  • Page 239 For a description, see the global parameter [IpProfile_EnableQSIGTunnelin EnableQSIGTunneling. Web: Enable Hold For a description, see the global parameter EnableHold. [IpProfile_EnableHold] [IpProfile_EnableEarly183] For a description, see the global parameter EnableEarly183. [IpProfile_EarlyAnswerTimeout] For a description, see the global parameter EarlyAnswerTimeout. Version 6.6 Mediant 2000...
  • Page 240 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 241: Gateway And Ip-To-Ip Application

    Part V Gateway and IP-to-IP Application...

  • Page 243: Introduction

    IP-to-Tel refers to calls received from the IP network and destined to the PSTN/PBX (i.e., telephone connected directly or indirectly to the device); Tel-to-IP refers to calls received from the PSTN/PBX, and destined for the IP network. Version 6.6 Mediant 2000...
  • Page 244 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 245: Ip-To-Ip Routing Application

    180\182\183\200\4xx uses the same logic and same limitations, in some cases the result may be a different response code.  OPTIONS: terminated at each leg independently.  INFO: only specific INFO’s (such as DTMF) are handled; other types are omitted. Version 6.6 Mediant 2000...

  • Page 246: Theory Of Operation

    Mediant 2000  UPDATE: terminated at each leg independently and may cause only changes in the RTP flow - Hold\Retrieve are the only exceptions that traverse the two legs.  Re-INVITE: terminated at each leg independently and may cause only changes in the RTP flow - Hold\Retrieve are the only exceptions that traverse the two legs.

  • Page 247: Proxy Sets

    AOR or Contact. Once an entry is found, the IP destination is obtained and a SIP request is then sent to the user. Figure 20-2: IP-to-IP Routing/Registration/Authentication of Remote IP-PBX Users (Example) Version 6.6 Mediant 2000...

  • Page 248: Inbound And Outbound Ip Routing Rules

    Mediant 2000 The device also supports the IP-to-IP call routing Survivability mode feature (see the figure below) for User-type IP Groups. The device stores in its database REGISTER messages sent by the clients of the User-type IP Group. If communication with the Serving IP Group (e.g., IP-PBX) fails, the User-type IP Group enters into Survivability mode in which the...

  • Page 249: Accounts

    Using SIP trunks, the IP-PBX connects (via the device) to two different ITSP's: • ITSP-A: ♦ Implements Proxy servers with fully qualified domain names (FQDN): "Proxy1.ITSP-A" and "Proxy2.ITSP-B", using TLS. ♦ Allocates a range of PSTN numbers beginning with +1919, which is Version 6.6 Mediant 2000...
  • Page 250 Mediant 2000 assigned to a range of IP-PBX users. ♦ Voice coder: G.723. • ITSP-B: ♦ Implements Proxy servers with IP addresses 216.182.224.202 and 216.182.225.202, using TCP. ♦ Allocates a range of PSTN numbers beginning with 0200, which is assigned to a range of IP-PBX users.

  • Page 251: Step 1: Enable The Ip-To-Ip Capabilities

    Media Settings). Figure 20-6: Defining Required Media Channels In the 'Number of Media Channels' field, enter the required number of media channels (in the example above, "120" to enable up to 60 IP-to-IP calls). Click Submit. Version 6.6 Mediant 2000...

  • Page 252: Step 3: Define A Trunk Group For The Local Pstn

    Mediant 2000 Save the settings to flash memory ("burn") with a device reset (see 'Saving Configuration' on page 396). 20.2.3 Step 3: Define a Trunk Group for the Local PSTN For incoming and outgoing local PSTN calls with the IP-PBX, you need to define the Trunk Group ID (#1) for the T1 ISDN trunk connecting the device to the local PSTN.
  • Page 253 'Proxy Load Balancing Method' drop-down list, select Round Robin. Figure 20-9: Proxy Set ID #2 for ITSP-B Configure Proxy Set ID #3 for the IP-PBX: From the 'Proxy Set ID' drop-down list, select 3. Version 6.6 Mediant 2000...

  • Page 254: Step 5: Configure The Ip Groups

    Mediant 2000 In the 'Proxy Address' column, enter the IP address of the IP-PBX (e.g., "10.15.4.211"). From the 'Transport Type' drop-down list corresponding to the IP address entered above, select UDP". In the 'Enable Proxy Keep Alive' drop-down list, select Using Options. This is used in Survivability mode for remote IP-PBX users.

  • Page 255: Step 6: Configure The Account Table

    Figure 20-11: Defining Accounts for Registration Configure Account ID #1 for IP-PBX authentication and registration with ITSP-A: • In the 'Served IP Group' field, enter "3" to indicate that authentication is performed on behalf of IP Group #3 (i.e., the IP-PBX). Version 6.6 Mediant 2000...

  • Page 256: Step 7: Configure Ip Profiles For Voice Coders

    Mediant 2000 • In the 'Serving IP Group' field, enter "1" to indicate that registration/authentication is with IP Group #1 (i.e., ITSP-A). • In the 'Username', enter the SIP username for authentication supplied by ITSP-A (e.g., itsp_a). • In the 'Password' field, enter the SIP password for authentication supplied by ITSP-A (e.g., 12345).

  • Page 257: Step 8: Configure Inbound Ip Routing

    This step defines how to configure the device for routing inbound (i.e., received) IP-to-IP calls. The table in which this is configured uses the IP Groups that you defined in 'Step 5: Configure the IP Groups' on page 254. Version 6.6 Mediant 2000...
  • Page 258 Mediant 2000  To configure inbound IP routing: Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP submenu > Routing submenu > IP to Trunk Group Routing). Figure 20-15: Defining Inbound IP Routing Rules Index #1: routes calls with prefix 9 (i.e., local calls) dialed from IP-PBX users to the...

  • Page 259: Step 9: Configure Outbound Ip Routing

    'Source IP Group ID': select 3 to indicate received (inbound) calls identified as belonging to the IP Group configured for the IP-PBX. • 'Dest Phone Prefix': enter "+81" to indicate calls to Japan (i.e., with prefix +81). Version 6.6 Mediant 2000...

  • Page 260: Step 10: Configure Destination Phone Number Manipulation

    Mediant 2000 • 'Source Phone Prefix': enter the asterisk (*) symbol to indicate all sources. • 'Dest IP Group ID': select 1 to indicate the destination IP Group to where the calls must be sent, i.e., to ITSP-A. • 'IP Profile ID': enter "1" to indicate the IP Profile configured for G.711.

  • Page 261: Digital Pstn

    E1 Euro ISDN and E1 CAS (subject to the constraints in the device's Release Notes). • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk. Version 6.6 Mediant 2000...
  • Page 262 Mediant 2000  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN submenu > Trunk Settings). Figure 21-1: Trunk Settings Page (Partial Display) On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: •...

  • Page 263: Tdm And Timing

    For a description of these parameters, see 'PSTN Parameters' on page 619.  To configure the TDM Bus settings: Open the TDM page (Configuration tab > VoIP menu > TDM > TDM Bus Settings). Figure 21-3: TDM Bus Settings Page Configure the parameters as required. Version 6.6 Mediant 2000...

  • Page 264: Clock Settings

    Mediant 2000 Click Submit to apply your changes. Save the changes to flash memory, see 'Saving Configuration' on page 396. 21.2.2 Clock Settings In a traditional TDM service network such as PSTN, both ends of the TDM connection must be synchronized. If synchronization is not achieved, voice frames are either dropped (to prevent a buffer overflow condition) or inserted (to prevent an underflow condition).

  • Page 265: Configuring Internal Clock As Clock Source

    Settings page, by clicking the trunk number in the 'Related Trunks' field, and in the Trunk Settings page, select the required Trunk number icon, and then click Apply Trunk Settings. Click Submit, and then reset the device (see 'Resetting the Device' on page 393). Version 6.6 Mediant 2000...
  • Page 266 Mediant 2000 Notes: • Don't modify the default values unless you fully understand the implications of the changes and know the default values. Every change affects the configuration of the state machine parameters and the call process related to the trunk you are using with this state machine.

  • Page 267: Configuring Digital Gateway Parameters

    Open the Digital Gateway Parameters page (Configuration tab > VoIP menu > GW and IP to IP submenu > Digital Gateway submenu > Digital Gateway Parameters). Figure 21-5: Digital Gateway Parameters Page Configure the parameters as required. Version 6.6 Mediant 2000...

  • Page 268: Tunneling Applications

    Mediant 2000 Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 396. 21.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 21.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network.
  • Page 269 TrunkGroup 1 = 0,3,3,1,31,4000,1; TrunkGroup 1 = 0,0,0,16,16,7000,2; TrunkGroup 1 = 0,1,1,16,16,7001,2; TrunkGroup 1 = 0,2,2,16,16,7002,2; TrunkGroup 1 = 0,3,3,16,16,7003,2; [/TrunkGroup] [ CodersGroup0 ] FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce; CodersGroup0 0 = g7231; Version 6.6 Mediant 2000...
  • Page 270 Mediant 2000 CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile 1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$; TelProfile 2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$;...

  • Page 271: Dsp Pattern Detector

    QSIG message until a SIP 200 OK response is received. If the originating device receives a 4xx, 5xx, or 6xx response, it disconnects the QSIG call with a ‘no route to destination’ cause. Version 6.6 Mediant 2000...

  • Page 272: Isdn Non-Facility Associated Signaling (Nfas)

    Mediant 2000  Call setup (terminating device): After the terminating device receives a SIP INVITE request with a 'Content-Type: application/QSIG', it sends the encapsulated QSIG Setup message to the Tel side and sends a 200 OK response (no 1xx response is sent) to IP.

  • Page 273: Nfas Interface Id

    InterfaceID #0 for the Primary trunk  InterfaceID #1 for the Backup trunk  InterfaceID #2 for a 24 B-channel T1 trunk  InterfaceID #3 for a 24 B-channel T1 trunk, and so on for subsequent T1 trunks Version 6.6 Mediant 2000...

  • Page 274: Creating An Nfas-Related Trunk Configuration

    Mediant 2000 For example, if four T1 trunks on a device are configured as a single NFAS group with Primary and Backup T1 trunks that is used with a DMS-100 switch, the following parameters should be used: NFASGroupNumber_0 = 1...

  • Page 275: Performing Manual D-Channel Switchover In Nfas Group

    Note that when at least one digit is received in the ISDN Setup message, the device stops playing a dial tone. The device stops collecting digits (from the ISDN) upon the following scenarios:  The device receives a Sending Complete IE in the ISDN Setup or Information Version 6.6 Mediant 2000...

  • Page 276: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578

    Mediant 2000 messages, indicating no more digits.  The timeout between received digits expires (configured by the TimeBetweenDigits parameter).  The maximum number of received digits has been reached (configured by the MaxDigits parameter).  A match is found with the defined digit map (configured by the DigitMapping parameter).

  • Page 277: Redirect Number And Calling Name (Display)

    NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Yes* * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 6.6 Mediant 2000...
  • Page 278 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 279: Trunk Group

    To register the Trunk Groups, click the Register button. To unregister the Trunk Groups, click Unregister. The registration method for each Trunk Group is according to the 'Registration Mode' parameter in the Trunk Group Settings page (see Version 6.6 Mediant 2000...
  • Page 280 Mediant 2000 'Configuring Trunk Group Settings' on page 281). Trunk Group Table Parameters Parameter Description From Trunk Defines the starting physical Trunk number in the Trunk Group. The [TrunkGroup_FirstTrunkI number of listed Trunks depends on the device's hardware configuration. To Trunk Defines the ending physical Trunk number in the Trunk Group.

  • Page 281: Configuring Trunk Group Settings

    If the channel is unavailable (e.g., busy), the call is put on call waiting (if call waiting is enabled and no other call is on call waiting); otherwise, the call is released. Version 6.6 Mediant 2000...
  • Page 282 Mediant 2000 Parameter Description  [1] Cyclic Ascending = The next available channel in the Trunk Group, in ascending cyclic order is selected. After the device reaches the highest channel number in the Trunk Group, it selects the lowest channel number in the Trunk Group, and then starts ascending again.
  • Page 283 If the device is configured globally to register Per Endpoint and an channel group includes four channels to register Per Gateway, the device registers all channels except the first four channels. The group of these four channels sends a single registration request. Version 6.6 Mediant 2000...
  • Page 284 Mediant 2000 Parameter Description Serving IP Group ID Assigns an IP Group to where INVITE messages received from this [TrunkGroupSettings_Se Trunk Group are sent. The actual destination to where these INVITE rvingIPGroup] messages are sent is according to the Proxy Set ID associated with the IP Group.
  • Page 285 NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. Note: This parameter appears in the table only if the VoiceMailInterface parameter is set to 3 (QSIG). Configuring Voice Mail on page 354. Version 6.6 Mediant 2000...
  • Page 286 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 287: Manipulation

    For example, if you enter 551 in Index 1 and 55 in Index 2, the device applies rule 1 to numbers that start with 551 and applies rule 2 to numbers that start with 550, 552, 553, Version 6.6 Mediant 2000...
  • Page 288 Mediant 2000 and so on until 559. However, if you enter 55 in Index 1 and 551 in Index 2, the device applies rule 1 to all numbers that start with 55, including numbers that start with 551. You can perform a second "round" (additional) of destination (NumberMapIP2Tel parameter) and source (SourceNumberMapIP2Tel parameter) number manipulations for IP-to-Tel calls on an already manipulated number.
  • Page 289 Rule 5: When the destination number has the prefix 6, 7, or 8 (e.g., 85262146), source number prefix 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix Version 6.6 Mediant 2000...
  • Page 290 Mediant 2000 Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed...
  • Page 291 For example, if you enter 9 and the phone number [Prefix2Add] is 1234, the new number is 91234. Web: Suffix to Add Defines the number or string that you want added to the end of the Version 6.6 Mediant 2000...
  • Page 292 Mediant 2000 Parameter Description EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone [Suffix2Add] number is 1234, the new number is 123400. Web/EMS: Number of Defines the number of digits that you want to keep from the right of Digits to Leave the phone number.

  • Page 293: Manipulating Number Prefix

    In this configuration example, the following manipulation process occurs: The prefix is calculated as 020215. The first seven digits from the left are removed from the original number, thereby changing the number to 8888888. The prefix that was previously calculated is then added. Version 6.6 Mediant 2000...

  • Page 294: Sip Calling Name Manipulations

    Mediant 2000 23.4 SIP Calling Name Manipulations The Calling Name Manipulations Tel2IP and Calling Name Manipulations IP2Tel tables allow you to configure up to 120 manipulation rules for manipulating the calling name (i.e., caller ID) in SIP messages. This can include modifying or removing the calling name. SIP calling name manipulation is applicable to Tel-to-IP and IP-to-Tel calls.
  • Page 295 The source IP address can include the 'x' wildcard to represent single digits. For example: 10.8.8.xx represents all IP addresses between 10.8.8.10 to 10.8.8.99.  The source IP address can include the asterisk (*) wildcard to represent any number between 0 and 255. For example, 10.8.8.* Version 6.6 Mediant 2000...

  • Page 296: Configuring Redirect Number Ip To Tel

    Mediant 2000 Parameter Description represents all IP addresses between 10.8.8.0 and 10.8.8.255. Web: Source Host Prefix Defines the URI host name prefix of the incoming SIP INVITE message in the From header. Notes:  This parameter is applicable only to the Calling Name Manipulations IP2Tel table.
  • Page 297 Click the Rule tab, and then configure the matching characteristics. For a description of the parameters, see the table below. Click the Action tab, and then configure the manipulation operation. For a description of the parameters, see the table below. Click Submit to apply your settings. Version 6.6 Mediant 2000...
  • Page 298 Mediant 2000 Redirect Number Manipulation Parameters Description Parameter Description Matching Characteristics (Rule) Web/EMS: Redirect Prefix Defines the redirect telephone number prefix. To denote any number, [RedirectPrefix] use the wildcard asterisk (*) symbol. Web/EMS: Destination Defines the destination (called) telephone number prefix. To denote Prefix any number, use the wildcard asterisk (*) symbol.
  • Page 299 [4] or Abbreviated [6]. Notes:  This parameter is applicable only to the Redirect Number IP > Tel table.  For more information on available NPI/TON values, see Numbering Plans and Type of Number on page 307. Version 6.6 Mediant 2000...

  • Page 300: Manipulating Redirected And Diverted Numbers For Call Diversion

    Mediant 2000 Parameter Description Web: NPI Defines the Numbering Plan Indicator (NPI). EMS: Number Plan  [0] Unknown (default) [NumberPlan]  [9] Private  [1] E.164 Public  [-1] Not Configured = value received from PSTN/IP is used Notes: ...

  • Page 301: Mapping Npi/Ton To Sip Phone-Context

    Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.20A.043.001 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 23.7 Mapping NPI/TON to SIP Phone-Context The Phone-Context table page allows you to map Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter. The 'phone-context' parameter appears in the standard SIP headers where a phone number is used (i.e.,...

  • Page 302: Configuring Release Cause Mapping

    Mediant 2000 table below. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 396. Notes: • You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'. In such a configuration, a Tel-to-IP call uses the first matching rule in the table.

  • Page 303: Fixed Mapping Of Sip Response To Isdn Release Reason

    In the 'Release Cause Mapping from SIP to ISDN' group, map different SIP Responses to Q.850 Release Causes. Click Submit to apply your changes. 23.8.1 Fixed Mapping of SIP Response to ISDN Release Reason The following table describes the mapping of SIP response to ISDN release reason. Version 6.6 Mediant 2000...
  • Page 304 Mediant 2000 Mapping of SIP Response to ISDN Release Reason ISDN Release Description Description Response Reason 400* Bad request Normal, unspecified Unauthorized Call rejected Payment required Call rejected Forbidden Call rejected Not found Unallocated number Method not allowed Service/option unavailable...

  • Page 305: Fixed Mapping Of Isdn Release Reason To Sip Response

    Network out of order Service unavailable Temporary failure Service unavailable Switching equipment congestion Service unavailable Access information discarded 502* Bad gateway Requested channel not available 503* Service unavailable Resource unavailable Service unavailable QoS unavailable 503* Service unavailable Version 6.6 Mediant 2000...
  • Page 306 Mediant 2000 ISDN Release Description Description Reason Response Facility not subscribed 503* Service unavailable Incoming calls barred within CUG Forbidden Bearer capability not authorized Forbidden Bearer capability not presently available Service unavailable Service/option not available 503* Service unavailable Bearer capability not implemented...

  • Page 307: Reason Header

    Subscriber [4] A public number in complete E.164 format representing a local subscriber, e.g., 5551234. Abbreviated [6] The support of this code is network dependent. The number provided in this information element Version 6.6 Mediant 2000...
  • Page 308 Mediant 2000 Description presents a shorthand representation of the complete number in the specified numbering plan as supported by the network. Private [9] Unknown [0] A private number, but with no further information about the numbering plan. Level 2 Regional [1] Level 1 Regional [2] A private number with a location, e.g., 3932200.

  • Page 309: Routing

    Source and destination Request-URI host name prefix • Source Trunk Group (from where the call is received) • Source (calling) and destination (called) telephone number prefix and suffix • Source and destination Request-URI host name prefix Version 6.6 Mediant 2000...
  • Page 310 Mediant 2000  Destination: If the call matches the configured characteristics, the device routes the call to an IP destination. If no characteristics match is found in the table, the call is rejected. The destination can be any of the following: •...
  • Page 311 FQDN that resolves into two IP addresses. For more information on alternative routing, see 'Alternative Routing for Tel-to-IP Calls' on page 322. Notes: • Outbound IP routing can be performed before or after number manipulation. This is configured using the RouteModeTel2IP parameter, as described below. Version 6.6 Mediant 2000...
  • Page 312 Mediant 2000 • The Outbound IP Routing Table can also be configured using the table ini file parameter, Prefix.  To configure Tel-to-IP or outbound IP routing rules: Open the Outbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP submenu >...
  • Page 313 Defines the IP Group from where the incoming IP call is received. Typically, the IP Group of an incoming INVITE is determined according to the Inbound EMS: Source IP IP Routing Table. Group ID Notes: [PREFIX_SrcIPGrou Version 6.6 Mediant 2000...
  • Page 314 Mediant 2000 Parameter Description  pID] This parameter is applicable only to the IP-to-IP routing application.  To denote all IP Groups, leave this field empty.  If this IP Group has a Serving IP Group, then all calls from this IP Group are sent to the Serving IP Group.
  • Page 315 IP Group. Group ID Notes: [PREFIX_DestIPGro  If you select an IP Group, you do not need to configure a destination IP upID] address. However, if both parameters are configured in this table, the Version 6.6 Mediant 2000...
  • Page 316 Mediant 2000 Parameter Description INVITE message is sent only to the IP Group (and not the defined IP address).  If the destination is a User-type IP Group, the device searches for a match between the Request-URI (of the received INVITE) to an AOR registration record in the device's database.

  • Page 317: Configuring Inbound Ip Routing Table

    Trunk Group's channel selection mode. The channel selection mode can be defined per Trunk Group (see 'Configuring Trunk Group Settings' on page 281) or for all Trunk Groups using the global parameter ChannelSelectMode. Version 6.6 Mediant 2000...
  • Page 318 Mediant 2000 The Inbound IP Routing Table provides two configuration areas:  Matching characteristics of incoming IP call, for example, prefix of destination number.  Operation (destination), for example, sends to a specific Trunk Group. If the incoming call matches the characteristics of a rule, then the call is sent to the destination configured for that rule.
  • Page 319 Defines the source IP address of the incoming IP call that can be used [SourceAddress] for routing decisions. The IP address can be configured in dotted-decimal notation (e.g., 10.8.8.5) or as an FQDN. If the address is an FQDN, DNS resolution is done according to the DNSQueryType parameter. Notes: Version 6.6 Mediant 2000...

  • Page 320: Ip Destinations Connectivity Feature

    Mediant 2000 Parameter Description  The source IP address is obtained from the Contact header in the INVITE message.  You can configure from where the source IP address is obtained, using the SourceIPAddressInput parameter.  The source IP address can include the following wildcards: ...
  • Page 321 IP Connectivity: This page displays a more informative connectivity status of the IP destinations used in Tel-to-IP routing rules in the Outbound IP Routing table. For viewing this page, see 'Viewing IP Connectivity' on page 454. Version 6.6 Mediant 2000...

  • Page 322: Alternative Routing For Tel-To-Ip Calls

    Mediant 2000 24.5 Alternative Routing for Tel-to-IP Calls The device supports various alternative Tel-to-IP call routing methods, as described in this section. 24.5.1 Alternative Routing Based on IP Connectivity You can configure the device to do alternative Tel-to-IP call routing based on IP connectivity.

  • Page 323: Alternative Routing Based On Sip Responses

    Tel-to-IP call destination. Alternative Routing based on SIP Response Code Example Destination IP Destination SIP Response Rule Used? Phone Prefix 408 Request 10.33.45.68 Main Route Timeout Alternative Route 486 Busy Here 10.33.45.70 Alternative Route 200 OK 10.33.45.72 Version 6.6 Mediant 2000...
  • Page 324 Mediant 2000  Proxy Sets: Proxy Sets are used for Server-type IP Groups (e.g., an IP PBX) and define the actual IP destination (IP address or FQDN) of the server. As you can define up to five IP destinations per Proxy Set, the device supports proxy redundancy, which works together with the alternative routing feature.

  • Page 325: Pstn Fallback

    Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). To enable alternative routing based on Q.931 cause code, you need to define this cause code in the Reasons for Alternative Routing table. Version 6.6 Mediant 2000...

  • Page 326: Alternative Routing To An Ip Destination Upon A Busy Trunk

    Mediant 2000  To configure alternative Trunk Group routing based on Q.931 cause codes: In the Proxy & Registration page, set the 'Redundant Routing Mode' parameter to Routing Table so that the device uses the Inbound IP Routing table for alternative routing.
  • Page 327 FQDN, or a SIP Request-URI user name and host part (i.e., user@host). The following syntax can also be used: host:port;transport=xxx (i.e., IP address, port and transport type). Note: When configured with a user@host, the original destination number is replaced by the user part. Version 6.6 Mediant 2000...
  • Page 328 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 329: Configuring Dtmf And Dialing

    > DTMF & Supplementary submenu > DTMF & Dialing). Figure 25-1: DTMF & Dialing Page Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 396. Version 6.6 Mediant 2000...

  • Page 330: Dialing Plan Features

    Mediant 2000 25.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 25.1.1 Digit Mapping Digit map pattern rules are used for Tel-to-IP ISDN overlap dialing (by setting the ISDNRxOverlap parameter to 1) to reduce the dialing period. For more information on digit maps for ISDN overlapping, see ISDN Overlap Dialing on page 275.
  • Page 331 (TimeBetweenDigits parameter), it sends the collected digits. Therefore, this ensures that calls are not rejected as a result of their digit pattern not been completed in the Dial Plan. Version 6.6 Mediant 2000...

  • Page 332: External Dial Plan File

    Mediant 2000 25.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see 'Dial Plan File' on page 404. User's Manual Document #: LTRT-68822...

  • Page 333: Configuring Supplementary Services

    Click Submit to apply your changes, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server. To save the changes to flash memory, see 'Saving Configuration' on page 396. Version 6.6 Mediant 2000...

  • Page 334: Call Hold And Retrieve

    Mediant 2000 26.1 Call Hold and Retrieve Call Hold and Retrieve:  The party that initiates the hold is called the holding party; the other party is called the held party. The device can't initiate Call Hold, but it can respond to hold requests and as such, it's a held party.

  • Page 335: Consultation Transfer For Qsig Path Replacement

    This source number can also be used as the value for the 'Source Prefix' field in the IP-to-Tel Destination Phone Number Manipulation table. The local IP address is used as the value for the 'Source IP Address' field. Version 6.6 Mediant 2000...

  • Page 336: Call Forward

    Mediant 2000 Note: Manipulation using the ManipulateIP2PSTNReferTo parameter does not affect IP-to-Trunk Group routing rules. 26.3 Call Forward The device supports Call Deflection (ETS-300-207-1) for Euro ISDN and QSIG (ETSI TS 102 393) for Network and User sides, which provides IP-ISDN interworking of call forwarding (call diversion) when the device receives a SIP 302 response.
  • Page 337 (i.e., does not send MWI Interrogation messages). • Send MWI Interrogation message, but don't use its result. Instead, wait for MWI Activate requests from the PBX. • Send MWI Interrogation message, use its result, and use the MWI Activate requests. Version 6.6 Mediant 2000...

  • Page 338: Emergency E911 Phone Number Services

    E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller. This section describes the E9-1-1 solution provided by Microsoft Lync Server 2010 (hereafter referred to as Lync Server 2010), and the deployed AudioCodes ELIN Gateway which provides the ISDN (or CAMA) connectivity to the PSTN-based E9-1-1 emergency providers.

  • Page 339: About E9-1-1 Services

    ALI databases. The E9-1-1 Selective Router sends the call to the appropriate PSAP based on the retrieved location information from the ALI. The PSAP operator dispatches the relevant emergency services to the E9-1-1 caller. Version 6.6 Mediant 2000...

  • Page 340: Microsoft Lync Server 2010 And E9-1-1

    Mediant 2000 26.5.2.2 Microsoft Lync Server 2010 and E9-1-1 Microsoft Lync Server 2010 enables Enterprise voice users to access its unified communications platform from virtually anywhere and through many different devices. This, together with a deployed MLTS, poses a challenge for E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller.
  • Page 341 When the client returns to any previously stored location, the client is automatically set to that location. A user can also manually select any location stored in the local users table and manage existing entries. Version 6.6 Mediant 2000...
  • Page 342 Mediant 2000 26.5.2.2.2 Adding ELINs to the Location Information Server As mentioned in the previous section, the Administrator needs to populate the Location Information Server (LIS) database with a network wire map, which maps the Enterprise's network elements to civic addresses. Once done, it can automatically locate clients within a network.
  • Page 343 In the table above, a unique IP subnet is associated per ERL. This is useful if you implement different subnets between floors. Therefore, IP phones, for example, on a specific floor are in the same subnet and therefore, use the same ELIN when dialing 9-1-1. Version 6.6 Mediant 2000...

  • Page 344: Audiocodes Elin Gateway For Lync Server 2010 E9-1-1 Calls To Pstn

    PSAP, based on ELIN-address match lookup in the Emergency Services provider's ALI database. The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN.
  • Page 345 ELIN is disregarded and no longer used (for PSAP callback). Therefore, table entries of only the most recently terminated E9-1-1 callers are considered in the ELIN table. The maximum entries in the ELIN table depend on the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment: •...
  • Page 346 Mediant 2000 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=ptime:20 ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/pidf+xml Content-ID: <voip_911_user1@contoso.com> <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:bp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ms="urn:schema:Rtc.LIS.msftE911PidfExtn.2008" entity="sip:voip_911_user1@contoso.com"><tuple id="0"><status><gp:geopriv><gp:location- info><ca:civicAddress><ca:country>US</ca:country><ca:A1>WA</ca:A1> <ca:A3>Redmond</ca:A3><ca:RD>163rd</ca:RD><ca:STS>Ave</ca:STS><ca: POD>NE</ca:POD><ca:HNO>3910</ca:HNO><ca:LOC>40/4451</ca:LOC> <ca:NAM>1111-222-333; 1234567890 </ca:NAM>...
  • Page 347 ELIN in the list, and so on until it finds an ELIN that is not being used and sends this ELIN.  If all the ELINs in the list are in use by active calls, the ELIN Gateway selects the ELIN Version 6.6 Mediant 2000...

  • Page 348: Configuring Audiocodes Elin Gateway

    26.5.2.4 Configuring AudioCodes ELIN Gateway This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment. 26.5.2.4.1 Enabling the E9-1-1 Feature By default, the E9-1-1 feature in the ELIN Gateway for Lync Server 2010 is disabled.

  • Page 349: Multilevel Precedence And Preemption

    (MLPP domain ID). The domain specifies the collection of devices and resources that are associated with an MLPP subscriber. When an MLPP subscriber that belongs to a particular domain places a precedence call to Version 6.6 Mediant 2000...
  • Page 350 Mediant 2000 another MLPP subscriber that belongs to the same domain, MLPP service can preempt the existing call that the called MLPP subscriber is on for a higher- precedence call. MLPP service availability does not apply across different domains. MLPP is typically used in the military where, for example, high-ranking personnel can preempt active calls during network stress scenarios such as a national emergency or degraded network situations.
  • Page 351 This can be modified using the EnableIp2TelInterworkingtable field of the ini file parameter, ResourcePriorityNetworkDomains. Notes: • If required, you can exclude the "resource-priority” tag from the SIP Require header in INVITE messages for Tel-to-IP calls when MLPP priority call handling is Version 6.6 Mediant 2000...

  • Page 352: Mlpp Preemption Events In Sip Reason Header

    Mediant 2000 used. This is configured using the RPRequired parameter. • For a complete list of the MLPP parameters, see 'MLPP and Emergency Call Parameters' on page 613. 26.6.1 MLPP Preemption Events in SIP Reason Header The device sends the SIP Reason header (as defined in RFC 4411) to indicate the reason and type of a preemption event.

  • Page 353: Precedence Ring Tone

    'Pulses On Answer' - number of charging units in first generated AOC-D Facility message Assign the charge code index to the desired routing rule in the Outbound IP Routing table (see 'Configuring Outbound IP Routing Table' on page 309). Version 6.6 Mediant 2000...

  • Page 354: Configuring Voice Mail

    Mediant 2000 26.8 Configuring Voice Mail The Voice Mail Settings page allows you to configure the voice mail parameters. For a description of these parameters, see 'Configuration Parameters Reference' on page 503. Notes: • The Voice Mail Settings page is available only for CAS interfaces.

  • Page 355: Stand-Alone Survivability Application

    Part VI Stand-Alone Survivability Application...

  • Page 357: Overview

    SAS in emergency state. This mode can be implemented, for example, for proxies that accept only SIP messages that are sent directly from the UAs. For more information, see 'SAS Redundant Mode' on page 359. Note: It is recommended to implement the SAS outbound mode. Version 6.6 Mediant 2000...

  • Page 358: Sas Outbound Mode

    Mediant 2000 27.1.1 SAS Outbound Mode This section describes the SAS outbound mode, which includes the following states:  Normal state (see 'Normal State' on page 358)  Emergency state (see 'Emergency State' on page 358) 27.1.1.1 Normal State In normal state, SAS receives REGISTER requests from the enterprise's UAs and forwards them to the external proxy (i.e., outbound proxy).

  • Page 359: Sas Redundant Mode

    SAS to ignore messages received from UAs in normal state (the 'SAS Survivability Mode' parameter must be set to 'Always Emergency' / 2) and thereby, “force” the UAs to switch back to their primary proxy. Version 6.6 Mediant 2000...

  • Page 360: Normal State

    Mediant 2000 27.1.2.1 Normal State In normal state, the UAs register and operate directly with the external proxy. Figure 27-3: SAS Redundant Mode in Normal State (Example) 27.1.2.2 Emergency State If the UAs detect that their primary (external) proxy does not respond, they immediately register to SAS and start routing calls to it.

  • Page 361: Sas Routing

    27.2.1 SAS Routing in Normal State The flowchart below displays the routing logic for SAS in normal state for INVITE messages received from UAs: Figure 27-5: Flowchart of INVITE from UA's in SAS Normal State Version 6.6 Mediant 2000...
  • Page 362 Mediant 2000 The flowchart below displays the routing logic for SAS in normal state for INVITE messages received from the external proxy: Figure 27-6: Flowchart of INVITE from Primary Proxy in SAS Normal State User's Manual Document #: LTRT-68822...

  • Page 363: Sas Routing In Emergency State

    User's Manual 27. Overview 27.2.2 SAS Routing in Emergency State The flowchart below shows the routing logic for SAS in emergency state: Figure 27-7: Flowchart for SAS Emergency State Version 6.6 Mediant 2000...
  • Page 364 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 365: Sas Configuration

    Note: The SAS application is available only if the device is installed with the SAS Software License Key. If your device is not installed with the SAS feature, contact your AudioCodes representative.  To enable the SAS application: Open the Applications Enabling page (Configuration tab > VoIP menu >...

  • Page 366: Configuring Common Sas Parameters

    Mediant 2000 28.1.2 Configuring Common SAS Parameters The procedure below describes how to configure SAS settings that are common to all SAS modes. This includes various SAS parameters as well as configuring the Proxy Set for the SAS proxy (if required). The SAS Proxy Set ID defines the address of the UAs' external proxy.
  • Page 367 The selected Proxy Set ID number must be the same as that specified in the 'SAS Proxy Set' field in the 'SAS Configuration page (see Step 6). • Do not use Proxy Set ID 0. In the 'Proxy Address' field, enter the IP address of the external proxy server. Version 6.6 Mediant 2000...

  • Page 368: Configuring Sas Outbound Mode

    Mediant 2000 From the 'Enable Proxy Keep Alive' drop-down list, select Using Options. This instructs the device to send SIP OPTIONS messages to the proxy for the keep- alive mechanism. Figure 28-2: Defining SAS Proxy Server Click Submit to apply your settings.

  • Page 369: Configuring Sas Redundant Mode

    The Gateway application must use the same SAS operation mode as the SIP UAs. For example, if the UAs use the SAS application as a redundant proxy (i.e., SAS redundancy mode), then the Gateway application must do the same. Version 6.6 Mediant 2000...

  • Page 370: Gateway With Sas Outbound Mode

    Mediant 2000 28.4.1 Gateway with SAS Outbound Mode The procedure below describes how to configure the Gateway application with SAS outbound mode.  To configure Gateway application with SAS outbound mode: Define the proxy server address for the Gateway application: Open the Proxy &...

  • Page 371: Gateway With Sas Redundant Mode

    In the second 'Proxy Address' field, enter the IP address and port of the device (in the format x.x.x.x:port). This is the same port as defined in the 'SAS Local UDP/TCP/TLS Port' field (see 'Configuring Common SAS Parameters' on page 366). Version 6.6 Mediant 2000...

  • Page 372: Advanced Sas Configuration

    Mediant 2000 From the 'Proxy Redundancy Mode' drop-down list, select Homing. Figure 28-7: Defining Proxy Servers for Gateway Application Click Submit. Disable the use of user=phone in the SIP URL: Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions submenu >...
  • Page 373 (e.g., "4") to leave from the right side of the user part. This field defines the number of digits to retain from the right side of the user part; all other digits in the user part are removed. Figure 28-8: Manipulating User Part in Incoming REGISTER Click Submit. Version 6.6 Mediant 2000...

  • Page 374: Manipulating Destination Number Of Incoming Invite

    Mediant 2000 Notes: • The device first does manipulation according to the Remove From Right parameter and only then according to the Leave From Right parameter. • Only one manipulation rule can be configured. • You can also configure SAS registration manipulation using the table ini file parameter, SASRegistrationManipulation.
  • Page 375 [3] SUBSCRIBE = Only SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. Manipulated URI Determines whether the source or destination SIP URI user part is Version 6.6 Mediant 2000...

  • Page 376: Sas Routing Based On Ip-To-Ip Routing Table

    Mediant 2000 Parameter Description [IPInboundManipulatio manipulated. n_ManipulatedURI]  [0] Source = (Default) Manipulation is done on the source SIP URI user part.  [1] Destination = Manipulation is done on the destination SIP URI user part. Operation Rule (Action) Remove From Left...
  • Page 377 To save the changes to flash memory, see 'Saving Configuration' on page 396. Note: The following parameters are not applicable to SAS and must be ignored: • 'Source IP Group ID' • 'Destination IP Group ID' • 'Destination SRD ID' • 'Alternative Route Options' Version 6.6 Mediant 2000...
  • Page 378 Mediant 2000 SAS IP-to-IP Routing Table Parameters Parameter Description Matching Characteristics Source Username Prefix Defines the prefix of the user part of the incoming SIP dialog's source [IP2IPRouting_SrcUser URI (usually the From URI). You can use special notations for denoting namePrefix] the prefix.
  • Page 379 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 Version 6.6 Mediant 2000...
  • Page 380 Mediant 2000 Parameter Description table, see 'Configuring IP Groups' on page 204). If this table does not define an IP Group but only an SRD, then the first IP Group associated with this SRD (in the IP Group table) is used.

  • Page 381: Blocking Calls From Unregistered Sas Users

    (Gateway application). Note: The port of the device is defined in the 'SIP UDP/TCP/TLS Local Port' field in the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Version 6.6 Mediant 2000...

  • Page 382: Adding Sip Record-Route Header To Sip Invite

    Mediant 2000 In the 'SAS Emergency Numbers' field, enter an emergency number in each field box. Figure 28-10: Configuring SAS Emergency Numbers Click Submit to apply your changes. 28.5.6 Adding SIP Record-Route Header to SIP INVITE You can configure SAS to add the SIP Record-Route header to SIP requests (e.g. INVITE) received from enterprise UAs.

  • Page 383: Replacing Contact Header For Sip Messages

    Contact header. Thus, the top-most Via header and the Contact header point to different hosts.  [1]: Enable - SAS changes the Contact header so that it points to the SAS host and therefore, the top-most Via header and the Contact header point to the same host. Version 6.6 Mediant 2000...

  • Page 384: Viewing Registered Sas Users

    Mediant 2000 28.6 Viewing Registered SAS Users You can view all the users that are registered in the SAS registration database. This is displayed in the 'SAS/SBC Registered Users page, as described in 'Viewing Registered Users' on page 451. Note:...

  • Page 385: Sas Cascading

    The figure below illustrates an example of a SAS Cascading call flow configured using the SAS Routing table. In this example, a call is routed from SAS Gateway (A) user to a user on SAS Gateway (B). Figure 29-1: SAS Cascading Using SAS Routing Table - Example Version 6.6 Mediant 2000...
  • Page 386 Mediant 2000  SAS Redundancy mode: If users cannot be distinguished (i.e., associated to a specific SAS gateway), then the SAS Redundancy feature is used to configure SAS Cascading. This mode routes the call in a loop fashion, from one SAS gateway to the next, until the user is located.

  • Page 387: Ip Media Capabilities

    Part VII IP Media Capabilities...

  • Page 389: Transcoding Using Third-Party Call Control

    In the example below, an Application Server sends a special INVITE that consists of two media lines to perform transcoding between G.711 and G.729: m=audio 20000 RTP/AVP 0 c=IN IP4 A.example.com m=audio 40000 RTP/AVP 18 c=IN IP4 B.example.com Version 6.6 Mediant 2000...

  • Page 390: Mediant

    Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 391: Maintenance

    Part VIII Maintenance...

  • Page 393: 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.6 Mediant 2000...

  • Page 394: Remotely Resetting Device Using Sip Notify

    Mediant 2000  To reset the device: Open the Maintenance Actions page (see 'Basic Maintenance' on page 393). 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 395: Locking And Unlocking The Device

    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. 31.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 396: Saving Configuration

    Mediant 2000  To unlock the device: Open the Maintenance Actions page (see 'Maintenance Actions' on page 393). Under the 'LOCK / UNLOCK' group, click the UNLOCK button. Unlock starts immediately and the device accepts new incoming calls. Note: The Home page's General Information pane displays whether the device is locked or unlocked (see 'Viewing the Home Page' on page 57).

  • Page 397: Restarting A B-Channel

    If a voice call is currently in progress on the B-channel, it is disconnected when the B-channel is restarted. • B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2). • B-channel restart does not affect the B-channel's configuration. Version 6.6 Mediant 2000...
  • Page 398 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 399: Software Upgrade

    TFTP: This is done by specifying the name of the Auxiliary file in an ini file (see Auxiliary and Configuration Files Parameters) and then loading the ini file to the device. The Auxiliary files listed in the ini file are then automatically loaded through Version 6.6 Mediant 2000...
  • Page 400 Mediant 2000 TFTP during device startup. If the ini file does not contain a specific auxiliary file type, the device uses the last auxiliary file of that type that was stored on its non-volatile memory. Notes: • You can schedule automatic loading of updated auxiliary files using HTTP/HTTPS, FTP, or NFS.

  • Page 401: 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 402 Mediant 2000 The burst tone is detected after the off time is completed. You can specify several tones of the same type. These additional tones are used only for tone detection. Generation of a specific tone conforms to the first definition of the specific tone.

  • Page 403: Prerecorded Tones File

    CPT file and is played instead of it. Note: The PRT are used only for generation of tones. Detection of tones is performed according to the CPT file. Version 6.6 Mediant 2000...

  • Page 404: Cas Files

     Channels: mono Once created, the PRT file can then be loaded to the device using AudioCodes' AcBootP utility or the Web interface (see 'Loading Auxiliary Files' on page 399). The prerecorded tones are played repeatedly. This allows you to record only part of the tone and then play the tone for the full duration.

  • Page 405: Dialing Plans For Digit Collection

    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. Install the converted file on the device, as described in 'Loading Auxiliary Files' on page 399.
  • Page 406 Plans, as required. Save the file with the ini file extension name (e.g., mydialplans.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Install the converted file on the device, as described in 'Loading Auxiliary Files' on page 399.

  • Page 407: Dial Plan Prefix Tags For Ip-To-Tel Routing

    Number of dial plan (text)  Dial string prefix (ranges can be defined in brackets)  User-defined routing tag (text) The example configuration below assumes a scenario where multiple prefixes exist for local and long distance calls: Version 6.6 Mediant 2000...
  • Page 408 Mediant 2000  To use Dial Plan file routing tags: Load an ini file to the device that selects Dial Plan index (e.g., 1) for routing tags, as shown below: IP2TelTaggingDestDialPlanIndex = 0 Define the external Dial Plan file with two routing tags (as shown below): •...

  • Page 409: Obtaining Ip Destination From Dial Plan File

    The Dial Plan index used in the Dial Plan file for this feature is defined by the Tel2IPSourceNumberMappingDialPlanIndex parameter. An example of such a configuration in the Dial Plan file is shown below: [ PLAN1 ] ; specific received number changed to 04343434181. Version 6.6 Mediant 2000...

  • Page 410: User Information File

    692)  Automatic update mechanism - using the UserInfoFileURL parameter, e.g., UserInfoFileUrl = 'http://192.168.0.250/Audiocodes/ UserInformationFile.txt' (see 'Automatic Update Mechanism' on page 423) 33.1.5.1 User Information File for PBX Extensions and "Global" Numbers The User Info file contains a User Info table that can be used for the following Gateway- related: ...
  • Page 411 Notepad. To add mapping rules to this file, use the following syntax: [ GW ] FORMAT PBXExtensionNum,GlobalPhoneNum,DisplayName,UserName,Password Where:  PBXExtensionNum is the PBX extension number (up to 10 characters)  GlobalPhoneNum is the "global" phone number (up to 20 characters) for the IP side Version 6.6 Mediant 2000...

  • Page 412: Enabling The User Info Table

    The file is created in .xml format and installed on the device as a binary file (with a .dat extension). The XML to binary file format is processed by AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide.
  • Page 413 <AMDCOEFFICIENTB>62259</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>23040</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 4 --> <AMDCOEFFICIENTA>10486</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>50790</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>28160</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 5 --> <AMDCOEFFICIENTA>6291</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>58982</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>23040</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 6 --> <AMDCOEFFICIENTA>7864</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>58982</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>12800</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 7 --> <AMDCOEFFICIENTA>7340</AMDCOEFFICIENTA> Version 6.6 Mediant 2000...
  • Page 414 Mediant 2000 <AMDCOEFFICIENTB>64717</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>3840</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> </PARAMETERSUIT> <PARAMETERSUIT> <PARAMETERSUITID>2</PARAMETERSUITID> <!-- Second language/country --> <NUMBEROFLEVELS>3</NUMBEROFLEVELS> <AMDSENSITIVITYLEVEL> <!-- Level 0 --> <AMDCOEFFICIENTA>15729</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>58163</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>32742</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 1 --> <AMDCOEFFICIENTA>5243</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>9830</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>24320</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 2 --> <AMDCOEFFICIENTA>13107</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>61440</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>26880</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL>...

  • Page 415: 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 416: Installing The Software License Key

    AudioCodes AcBootP utility - see Installing Software License Key using AcBootP 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 417: Installing Software License Key Using Web Interface

    Software License Key file is located on your computer. Click Load File; the new key is installed on the device. If the Software License Key is valid, it is burned to the device's flash memory and displayed in the 'Current Key' field. Version 6.6 Mediant 2000...

  • Page 418: Installing Software License Key Using Bootp/Tftp

    Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]". Verify that the content of the file has not been altered. 33.2.2.2 Installing Software License Key using BootP/TFTP The procedure below describes how to install a Software License Key using AudioCodes AcBootP utility. Notes: •...

  • Page 419: Software Upgrade Wizard

    (see 'Basic Maintenance' on page 393). Notes: • You can get the latest software files from AudioCodes Web site at http://www.audiocodes.com/downloads. • Before upgrading the device, it is recommended that you save a copy of the device's configuration settings (i.e., ini file) to your computer.
  • Page 420 Mediant 2000 • On the toolbar, click Device Actions, and then choose Software Upgrade Wizard. Figure 33-4: Start Software Upgrade Wizard Screen Click the Start Software Upgrade button; the wizard starts, requesting you to browses to a .cmp file for uploading.
  • Page 421 Click End Process to close the wizard; the Web Login dialog box appears. Enter your login user name and password, and then click OK; a message box appears informing you of the new .cmp file. Click OK; the Web interface becomes active, reflecting the upgraded device. Version 6.6 Mediant 2000...

  • Page 422: Backing Up And Loading Configuration File

    Mediant 2000 33.4 Backing Up and Loading Configuration File You can save a copy/backup of the device's current configuration settings as an ini file to a folder on your computer, using the Configuration File page. The saved ini file includes only parameters that were modified and parameters with other than default values.

  • Page 423: Automatic Update

    If there is no reply from a BootP server and if DHCP is enabled (DHCPEnable = 1), the device initiates a standard DHCP procedure to configure its network parameters. Version 6.6 Mediant 2000...
  • Page 424 Mediant 2000 After changing the network parameters, the device attempts to load the device's firmware file (cmp) and various configuration files from the TFTP server’s IP address received from the BootP/DHCP server. If a TFTP server’s IP address isn’t received, the device attempts to load the cmp file and / or configuration files from a preconfigured TFTP server.

  • Page 425: Obtaining Ip Address Automatically Using Dhcp

    IniFileURL settings. As a safeguard to an unintended burn-to-flash when resetting the device, if the device is configured for Automatic Updates, the 'Burn To FLASH' field under the Reset Configuration group in the Web interface's Maintenance Actions page is automatically set to No by default. Version 6.6 Mediant 2000...
  • Page 426 Mediant 2000 Note: For a description of all the Automatic Update ini file parameters, see Automatic Update Parameters on page 693.  To configure the Automatic Update feature (ini file example): Setup a Web server (e.g., http://www.corp.com) and place all the required configuration files on this server.

  • Page 427: Automatic Configuration Methods

    Local configuration server with BootP/TFTP provides an easy and efficient method for automatic configuration, where configuration occurs at a staging warehouse, as described below: Install AudioCodes AcBootP/TFTP utility program on a computer located in a staging warehouse. Prepare a standard configuration ini file and place it in the TFTP directory.

  • Page 428: Dhcp-Based Configuration Server

    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"; range 10.31.4.53 10.31.4.75; filename "SIP_F6.60A.217.003.cmp –fb;device.ini"; option routers 10.31.0.1; option subnet-mask 255.255.0.0; 34.4.3 Configuration using DHCP Option 67 This method is suitable for deployments where DHCP server configuration is possible at the customer site.

  • Page 429: Tftp Configuration Using Dhcp Option 66

    34.4.4 TFTP Configuration using DHCP Option 66 This method is suitable when the customer's network 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 430: Configuration Using Ftp Or Nfs

    NFS v2/v3 is also supported. 34.4.7 Configuration 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. As soon as a registered device contacts the EMS server through SNMP, the EMS server handles all required configuration automatically, upgrading software as needed.

  • Page 431: Loading Files Securely (Disabling Tftp)

    /conf/sar bootp Note: Once Secure Startup has been enabled, it can only be disabled by setting EnableSecureStartup to 0 using the CLI. Loading a new ini file using BootP/TFTP is not possible until EnableSecureStartup is disabled. Version 6.6 Mediant 2000...

  • Page 432: Remotely Triggering Auto Update Using Sip Notify

    Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). Under the Misc Parameters group, set the 'SIP Remote Reset' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. User's Manual Document #: LTRT-68822...

  • Page 433: Restoring Factory Defaults

    At the prompt, type the following command to reset the device to default settings, and then press Enter: /CONFiguration> RestoreFactorySettings At the prompt, type the following command to confirm reset to default settings, and then press Enter: /CONFiguration> RestoreFactorySettings APPROVED Version 6.6 Mediant 2000...

  • Page 434: Restoring Defaults Using An Ini File

    Mediant 2000 35.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 422).

  • Page 435: Status, Performance Monitoring And Reporting

    Part IX Status, Performance Monitoring and Reporting...

  • Page 437: 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 393). Version 6.6 Mediant 2000...

  • Page 438: Viewing Ethernet Port Information

    Mediant 2000 36.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information on the Ethernet port connections. Note: The Ethernet Port Information page can also be accessed from the Home page (see 'Viewing the Home Page' on page 57).

  • Page 439: Carrier-Grade Alarms

    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 Version 6.6 Mediant 2000...
  • Page 440 Mediant 2000  Description: brief explanation of the alarm  Date: date and time that the alarm was generated You can view the next 20 alarms (if exist), by clicking the Go to page button.  To delete all the alarms in the table: Click the Delete History Table button;...

  • Page 441: 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.6 Mediant 2000...

  • Page 442: Viewing Trunk Utilization

    Mediant 2000 38.2 Viewing Trunk Utilization The Trunk Utilization page provides an X-Y graph that displays the number of active channels per trunk over time. The x-axis indicates the time; the y-axis indicates the number of active trunk channels. Note: If you navigate to a different page, the data displayed in the graph and all its settings are cleared.
  • Page 443 Instead of using the 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; the maximum resolution is about an hour. Version 6.6 Mediant 2000...
  • Page 444 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 445: Voip Status

    The status of the trunks is depicted by color-coded icons, as described in the table below: Description of Color-Coded Icons for Trunk Status Trunk Icon Color Label Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Version 6.6 Mediant 2000...
  • Page 446 Mediant 2000 Icon Color Trunk Purple Lower Layer Down (DS3 physical layer is disabled) The status of the channels is depicted by color-coded icons, as described in the table below: Description of Color-Coded Icons for Channel Status Icon Color Label...

  • Page 447: Viewing Nfas Groups And D-Channel Status

    For more information, see 'Performing Manual D-Channel Switchover in NFAS Group' on page 275. Note: This page is applicable only to T1 ISDN protocols supporting NFAS, and only if the NFAS group is configured with two D-channels. Version 6.6 Mediant 2000...

  • Page 448: Viewing Active Ip Interfaces

    Mediant 2000  To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure 39-3: NFAS Group & D-Channel Status Page 39.3...

  • Page 449: Viewing Performance Statistics

    Open the Call Counters page that you want to view (Status & Diagnostics tab > VoIP Status menu > IP to Tel Calls Count or Tel to IP Calls Count); the figure below shows the IP to Tel Calls Count page. Figure 39-5: Calls Count Page Version 6.6 Mediant 2000...
  • Page 450 Mediant 2000 The fields in this page are described in the following table: Call Counters Description Counter Description Number of Attempted Indicates the number of attempted calls. It is composed of established Calls and failed calls. The number of established calls is represented by the 'Number of Established Calls' counter.

  • Page 451: Viewing Registered Users

    URI to another URI (Contact) where the user might be available. Contact SIP URI that can be used to contact that specific instance of the User Agent for subsequent requests. Version 6.6 Mediant 2000...

  • Page 452: Viewing Registration Status

    Mediant 2000 39.7 Viewing Registration Status The Registration Status page displays whether the device as a whole and SIP Accounts are registered to a SIP Registrar/Proxy server.  To view the registration status:  Open the Registration Status page (Status & Diagnostics tab > VoIP Status menu >...

  • Page 453: Viewing Call Routing Status

    IP address and FQDN (if exists) of the Proxy server with which the device currently operates.  N/A = Proxy server isn't defined. State  OK = Communication with the Proxy server is in order.  Fail = No response from any of the defined Proxies. Version 6.6 Mediant 2000...

  • Page 454: Viewing Ip Connectivity

    Mediant 2000 39.9 Viewing IP Connectivity The IP Connectivity page displays on-line, read-only network diagnostic connectivity information on all destination IP addresses configured in the Outbound IP Routing Table page (see 'Configuring Outbound IP Routing Table' on page 309). Note: The information in columns 'Quality Status' and 'Quality Info' (per IP address) is reset if two minutes elapse without a call to that destination.
  • Page 455 Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).  This parameter is reset if no QoS information is received for 2 minutes. DNS Status DNS status can be one of the following:  DNS Disable  DNS Resolved  DNS Unresolved Version 6.6 Mediant 2000...
  • Page 456 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 457: Reporting Information To External Party

    Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Payload Type Session Description Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Silence Suppression State Jitter Buffer Jitter Buffer Adaptive Jitter Buffer Rate Version 6.6 Mediant 2000...
  • Page 458 Mediant 2000 Group Metric Name Jitter Buffer Nominal Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Gap Loss Burst Loss Density Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold...
  • Page 459 'RTCP XR Collection Server Transport Type' (RTCPXRESCTransportType) - determines the transport layer for outgoing SIP dialogs initiated by the device to the RTCP XR Collection Server. Click Submit. Reset the device for the settings to take effect. Version 6.6 Mediant 2000...

  • Page 460: Generating Call Detail Records

    Mediant 2000 40.2 Generating Call Detail Records The Call Detail Record (CDR) contains vital statistic information on calls made from the device. The device can be configured to generate and report CDRs for various stages of the call, including SIP messages and/or media. You can configure when CDRs for a call are generated, for example, only at the end of the call or only at the start and end of the call.

  • Page 461: Cdr Field Description

    ISDN    IPMEDIA  NETANN  STREAMING  TRANSPARENT  MSCML  VXML  IP2IP Orig Call originator:  LCL (Tel side)  RMT (IP side) SourceIp Source IP address DestIp Destination IP address Version 6.6 Mediant 2000...
  • Page 462 Mediant 2000 Field Name Description Source phone number type Note: This field is applicable only to the Gateway application. Source phone number plan Note: This field is applicable only to the Gateway application. Source phone number SrcPhoneNum SrcNumBeforeMap Source number before manipulation Destination phone number type Note: This field is applicable only to the Gateway application.
  • Page 463 ABNORMALLY_TERMINATED - Anything else  N/A - Reasons not belonging to above categories RedirectNumBeforeM Redirect number before manipulation SrdId SRD ID name SIPInterfaceId SIP interface ID ProxySetId Proxy Set ID IpProfileId IP Profile ID name MediaRealmId Media Realm name Version 6.6 Mediant 2000...

  • Page 464: Release Reasons In Cdr

    Mediant 2000 Field Name Description SigTransportType SIP signaling transport type (UDP, TCP, or TLS) TxRTPIPDiffServ Media IP DiffServ TxSigIPDiffServ Signaling IP DiffServ LocalRFactor Local R-factor RemoteRFactor Remote R-factor LocalMosCQ Local MOS for conversation quality RemoteMosCQ Remote MOS for conversation quality...
  • Page 465  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED"  "GWAPP_NON_SELECTED_USER_CLEARING"  "GWAPP_INVALID_NUMBER_FORMAT"  "GWAPP_FACILITY_REJECT"  "GWAPP_RESPONSE_TO_STATUS_ENQUIRY"  "GWAPP_NORMAL_UNSPECIFIED"  "GWAPP_CIRCUIT_CONGESTION"  "GWAPP_USER_CONGESTION"  "GWAPP_NO_CIRCUIT_AVAILABLE"  "GWAPP_NETWORK_OUT_OF_ORDER" Version 6.6 Mediant 2000...
  • Page 466 Mediant 2000  "GWAPP_NETWORK_TEMPORARY_FAILURE"  "GWAPP_NETWORK_CONGESTION"  "GWAPP_ACCESS_INFORMATION_DISCARDED"  "GWAPP_REQUESTED_CIRCUIT_NOT_AVAILABLE"  "GWAPP_RESOURCE_UNAVAILABLE_UNSPECIFIED"  "GWAPP_PERM_FR_MODE_CONN_OUT_OF_S"  "GWAPP_PERM_FR_MODE_CONN_OPERATIONAL"  "GWAPP_PRECEDENCE_CALL_BLOCKED" • "RELEASE_BECAUSE_PREEMPTION_ANALOG_CIRCUIT_RESERVED_FOR_ REUSE" • "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED"  "GWAPP_BC_NOT_AUTHORIZED"  "GWAPP_BC_NOT_PRESENTLY_AVAILABLE"  "GWAPP_SERVICE_NOT_AVAILABLE"  "GWAPP_CUG_OUT_CALLS_BARRED"  "GWAPP_CUG_INC_CALLS_BARRED"  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS" ...

  • Page 467: Configuring Radius Accounting

    15 Stop Acc or blank digits long nas-ip- IP address of the Numeric 192.168.14. Start Acc address requesting device Stop Acc service-type Type of service Numeric 1: login Start Acc requested Stop Acc Version 6.6 Mediant 2000...
  • Page 468 Mediant 2000 Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. h323- SIP call identifier Up to 32 Start Acc incoming- octets Stop Acc conf-id h323-remote- IP address of the Numeric Stop Acc address remote gateway h323-conf-id H.323/SIP call...
  • Page 469 = 8800 acct-session-time = 1 acct-input-packets = 122 acct-output-packets = 220 called-station-id = 201 calling-station-id = 202 // Accounting non-standard parameters: (4923 33) h323-gw-id = (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 Version 6.6 Mediant 2000...

  • Page 470: Event Notification Using X-Detect Header

    Mediant 2000 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 40.4 Event Notification using X-Detect Header The device supports the sending of notifications to a remote party notifying the occurrence (or detection) of certain events on the media stream.
  • Page 471 Type = [AMD | CPT | FAX | PTT…] • Subtype = xxx (according to the defined subtypes of each type) Below is an example of SIP messages using the X-Detect header: INVITE sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Version 6.6 Mediant 2000...

  • Page 472: Querying Device Channel Resources Using Sip Options

    Mediant 2000 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Request=CPT,FAX SIP/2.0 200 OK Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone>;tag=1c19282 Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:101@10.33.2.53> X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0...

  • Page 473: Diagnostics

    Part X Diagnostics...

  • Page 475: Syslog And Debug Recordings

    A skip in the number sequence of messages indicates a loss of message packets. For example, in the below Syslog message generation, messages 238 through 300 were not received. In other words, three Syslog messages were lost Version 6.6 Mediant 2000...

  • Page 476: Event Representation In Syslog Messages

    Mediant 2000 Message Item Description (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [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.
  • Page 477 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.6 Mediant 2000...

  • Page 478: Identifying Audiocodes Syslog Messages Using Facility Levels

    Mediant 2000 41.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 479: Snmp Alarms In Syslog Messages

    If additional information exists in the alarm, then these are also added: Additional Info1:/ Additional Info2:/ Additional Info3 The Messages’ Severity is as follows: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) RecoverableMsg Critical Major RecoverableMsg...

  • Page 480: Configuring Debug Recording

    Mediant 2000  To configure Syslog : Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Enable the Syslog feature by setting the 'Enable Syslog' to Enable. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port' parameters.

  • Page 481: Filtering Syslog Messages And Debug Recordings

    Click the Add button; the Add Record dialog box appears: Figure 41-2: Logging Filters Table - Add Record Dialog Box Configure the logging filter, as required. See the table below for a description of the parameters. Click Submit to save your changes. Version 6.6 Mediant 2000...
  • Page 482 Mediant 2000 Notes: • To configure the Syslog debug level, use the 'Debug Level' parameter (see 'Configuring Syslog' on page 479). • The Logging Filters table can also be configured using the table ini file parameter, LoggingFilters. Logging Filters Table Parameters Description...

  • Page 483: Filtering Ip Network Traces

    Transport layer for destination port and, &&, ==, <, > Between expressions Below are examples of configured expressions for the 'Value' parameter:  udp && ip.addr==10.8.6.55  ip.src==10.8.6.55 && udp.port>=5000 and udp.port<6000  ip.dst==10.8.0.1/16  ip.addr==10.8.6.40 Version 6.6 Mediant 2000...

  • Page 484: Viewing Syslog Messages

    Syslog server. • 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. ...

  • Page 485: Collecting Debug Recording Messages

    41. Syslog and Debug Recordings 41.6 Collecting Debug Recording Messages To collect debug recording packets, the open source program Wireshark is used. AudioCodes proprietary plug-in files for Wireshark, which are shipped in your software kit, are also required. Notes: •...

  • Page 486: Mediant

    Mediant 2000 For ISDN trace messages, the additional header, "NetBricks Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below: AUDIOCODES DEBUG RECORDING NetBricks Trace System time: 3559 Direction: Message received from internal server queue (73) From (Entity origination ID): DL_D (DL LAPD Q.921) (100)

  • Page 487: Self-Testing

    This is a short test phase in which the only error detected and reported is failure in initializing hardware components or malfunction in running hardware components. If an error is detected, an error message is sent to the Syslog. Version 6.6 Mediant 2000...
  • Page 488 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 489: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. This maximum can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. • The Test Call Endpoint table can also be configured using the table ini file parameter Test_Call (see 'SIP Test Call Parameters' on page 522).
  • Page 490 Mediant 2000 Configure the test endpoint parameters as desired. See the table below for a description of these parameters. Click Submit to apply your settings. Test Call Table Parameters Parameter Description General Tab Endpoint URI Defines the endpoint's URI. This can be defined as a user or user@host.
  • Page 491 Note: This parameter is applicable only if 'Call Party' is set to Caller. Calls per Second Defines the number of calls per second. [Test_Call_CallsPer Note: This parameter is applicable only if 'Call Party' is set to Caller. Second] Version 6.6 Mediant 2000...

  • Page 492: Starting, Stopping And Restarting Test Calls

    Mediant 2000 Parameter Description Test Mode Defines the test session mode. [Test_Call_TestMo  [0] Once = (Default) The test runs until the lowest value between the following is reached:  Maximum channels is reached for the test session, configured by 'Maximum Channels for Session'.

  • Page 493: Viewing Test Call Statistics

    Call Attempts: The number of calls that were attempted.  Total Established Calls: The total number of calls that were successfully established.  Total Failed Attempts: The total number of calls that failed to be established. Version 6.6 Mediant 2000...

  • Page 494: Configuring Dtmf Tones For Test Calls

    Mediant 2000  Remote Disconnections Count: Number of calls that were disconnected by the remote side.  Average CPS: The average calls per second.  Test Status: Displays the status (brief description) as displayed in the 'Test Status' field (see 'Starting, Stopping and Restarting Test Calls' on page 492).

  • Page 495: Configuring Basic Test Call

    The Basic Test Call feature tests incoming calls only and is initiated only upon receipt of incoming calls with the configured prefix. • For a full description of this parameter, see 'SIP Test Call Parameters' on page 522. • This call test is done on all SIP interfaces. Version 6.6 Mediant 2000...

  • Page 496: Test Call Configuration Examples

    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 497 This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another. Version 6.6 Mediant 2000...
  • Page 498 Mediant 2000 Figure 43-7: Test Call Registration Example This example assumes that you have configured your device for communication between LAN phone users such as IP Groups to represent the device (10.13.4.12) and the proxy server, and IP-to-IP routing rules to route calls between these IP Groups.

  • Page 499: Appendix

    Part XI Appendix...

  • Page 501: Dialing Plan Notation For Routing And Manipulation

    03(abc): for any number that starts with 03 and ends with abc.  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. Version 6.6 Mediant 2000...
  • Page 502 Mediant 2000 Notation Description Notes:  The value n must be less than the value m.  Only numerical ranges are supported (not alphabetical letters).  For suffix ranges, the starting (n) and ending (m) numbers in the range must have the same number of digits. For example, (23-34) is correct, but (3-12) is not.

  • Page 503: Configuration Parameters Reference

     [0] = Disable  [1] = (Default) Enable For more information on Ethernet interface redundancy, see Ethernet Interface Redundancy on page 105. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 2000...

  • Page 504: Multiple Voip Network Interfaces And Vlan Parameters

    Mediant 2000 45.1.2 Multiple VoIP Network Interfaces and VLAN Parameters The IP network interfaces and VLAN parameters are described in the table below. IP Network Interfaces and VLAN Parameters Parameter Description Multiple Interface Table Web: Multiple Interface This table parameter configures the Multiple Interface table. The format...

  • Page 505: Routing Parameters

    Web/EMS: IP Routing Defines up to 30 static IP routing rules for the device. These rules can Table be associated with IP interfaces defined in the Multiple Interface table (InterfaceTable parameter). The routing decision for sending the Version 6.6 Mediant 2000...

  • Page 506: Quality Of Service Parameters

    Mediant 2000 Parameter Description [StaticRouteTable] outgoing IP packet is based on the source subnet/VLAN. If not associated with an IP interface, the static IP rule is based on destination IP address. When the destination of an outgoing IP packet does not match one of...
  • Page 507 The valid range is 0 to 63. The default is 26. [GoldServiceClassDiffS erv] Web: Bronze QoS Defines the DiffServ value for the Bronze CoS content (OAMP EMS: Bronze Service applications). Class Diff Serv The valid range is 0 to 63. The default is 10. [BronzeServiceClassDiff Serv] Version 6.6 Mediant 2000...

  • Page 508: Nat And Stun Parameters

    Mediant 2000 45.1.5 NAT and STUN Parameters The Network Address Translation (NAT) and Simple Traversal of UDP through NAT (STUN) parameters are described in the table below. NAT and STUN Parameters Parameter Description STUN Parameters Web: Enable STUN Enables Simple Traversal of UDP through NATs (STUN).

  • Page 509: Nfs Parameters

    Defines the start of the range of numbers used for local UDP ports used [NFSBasePort] by the NFS client. The maximum number of local ports is maximum channels plus maximum NFS servers. The valid range is 0 to 65535. The default is 47000. Version 6.6 Mediant 2000...

  • Page 510: Dns Parameters

    Mediant 2000 Parameter Description NFS Table Web: NFS Table This table parameter defines up to 16 NFS file systems so that the EMS: NFS Settings device can access a remote server's shared files and directories for [NFSServers] loading cmp, ini, and auxiliary files (using the Automatic Update mechanism).

  • Page 511: Dhcp Parameters

    When set to 0, the DHCP lease renewal is disabled. Otherwise, the renewal time is divided by this factor. Some DHCP-enabled routers perform better when set to 4. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 2000...

  • Page 512: Ntp And Daylight Saving Time Parameters

    Mediant 2000 45.1.9 NTP and Daylight Saving Time Parameters The Network Time Protocol (NTP) and daylight saving time parameters are described in the table below. 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 101.

  • Page 513: Management Parameters

    When this duration expires, the password of the Web user [WebUserPassChangeIn must be changed. terval] The valid value is 0 to 100000, where 0 means that the password is always valid. The default is 1140. Version 6.6 Mediant 2000...
  • Page 514 Mediant 2000 Parameter Description Note: This parameter is applicable only when using the Web Users table, where the default value of the 'Password Age' parameter in the Web Users table inherits this parameter's value. Web: User inactivity timer Defines the duration (in days) for which a user has not logged in to the...
  • Page 515 Defines the file name of the Scenario file to be loaded to the device. The file name must have the .dat extension and can be up to 47 characters. For loading a Scenario using the Web interface, see Loading a Scenario to the Device on page 53. Version 6.6 Mediant 2000...
  • Page 516 Mediant 2000 Parameter Description [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface. The format of this parameter is as follows: [WelcomeMessage ] FORMAT WelcomeMessage_Index = WelcomeMessage_Text [\WelcomeMessage]...

  • Page 517: Telnet Parameters

    Enables keep-alive traps and sends them every 9/10 of the time as defined by the NATBindingDefaultTimeout parameter.  [0] = Disable  [1] = Enable Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 2000...
  • Page 518 Mediant 2000 Parameter Description Defines the base product system OID. [SNMPSysOid] The default is eSNMP_AC_PRODUCT_BASE_OID_D. Note: For this parameter to take effect, a device reset is required. [SNMPTrapEnterpriseOid] Defines the Trap Enterprise OID. The default is eSNMP_AC_ENTERPRISE_OID. The inner shift of the trap in the AcTrap subtree is added to the end of the OID in this parameter.
  • Page 519 Trusted managers can work with all community strings. SNMP V3 Users Table Web/EMS: SNMP V3 Users This parameter table defines SNMP v3 users. The format of this [SNMPUsers] parameter is as follows: [SNMPUsers] FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol, SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, SNMPUsers_Group; [\SNMPUsers] Version 6.6 Mediant 2000...

  • Page 520: Debugging And Diagnostics Parameters

    Mediant 2000 Parameter Description For example: 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. Note: For a description of this table, see 'Configuring SNMP V3 Users' on page 84.
  • Page 521 LAN routers or IP configuration parameters' modifications by a DHCP server. [EnableAutoRAITransmi Enables the device to send a remote alarm indication (RAI) when the bit tBER] error rate (BER) is greater than 0.001.  [0] Disable (default)  [1] Enable Version 6.6 Mediant 2000...

  • Page 522: Sip Test Call Parameters

    Mediant 2000 45.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below. SIP Test Call Parameters Parameter Description Web: Test Call DTMF Defines the DTMF tone that is played for answered test calls (incoming String and outgoing).
  • Page 523 [7] 7 = This option is recommended when the device is running under "heavy" traffic. In this mode:  The Syslog debug level automatically changes between level 5, level 1, and level 0, depending on the device's CPU consumption so that VoIP traffic isn’t affected. Version 6.6 Mediant 2000...
  • Page 524 Mediant 2000 Parameter Description  Syslog messages are bundled into a single UDP packet, after which they are sent to a Syslog server (bundling size is determined by the MaxBundleSyslogLength parameter). Bundling reduces the number of UDP Syslog packets, thereby improving CPU utilization.
  • Page 525 The format of this parameter is as [LoggingFilters] follows: [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_Type, LoggingFilters_Value, LoggingFilters_Syslog, LoggingFilters_CaptureType; [ \LoggingFilters ] Note: For a detailed description of this table, see 'Filtering Syslog Messages and Debug Recordings' on page 481. Version 6.6 Mediant 2000...

  • Page 526: Resource Allocation Indication Parameters

    Mediant 2000 45.3.4 Resource Allocation Indication Parameters The Resource Allocation Indication (RAI) parameters are described in the table below. RAI Parameters Parameter Description Enables RAI alarm generation if the device's busy endpoints exceed a [EnableRAI] user-defined threshold.  [0] = (Default) Disable RAI (Resource Available Indication) service.
  • Page 527 Vendor Specific Information fields, refer to the AcBootP Utility User's Guide. The AcBootP utility displays this information in the 'Client Info' column. Notes:  For this parameter to take effect, a device reset is required.  This option is not available on DHCP servers. Version 6.6 Mediant 2000...

  • Page 528: Security Parameters

    Mediant 2000 45.4 Security Parameters This subsection describes the device's security parameters. 45.4.1 General Parameters The general security parameters are described in the table below. General Security Parameters Parameter Description [EnableSecureStartup] Enables the Secure Startup mode. In this mode, downloading the ini file to the device is restricted to a URL provided in initial configuration (see the parameter IniFileURL) or using DHCP.

  • Page 529: Https Parameters

    Notes:  For this parameter to take effect, a device reset is required.  For a description on implementing client certificates, see 'Client Certificates' on page 98. Version 6.6 Mediant 2000...

  • Page 530: Srtp Parameters

    Mediant 2000 Parameter Description [HTTPSRootFileName] Defines the name of the HTTPS trusted root certificate file to be loaded using TFTP. The file must be in base64-encoded PEM (Privacy Enhanced Mail) format. The valid range is a 47-character string. Note: This parameter is applicable only when the device is loaded using BootP/TFTP.
  • Page 531 Web/EMS: SRTP offered Defines the offered crypto suites (cipher encryption algorithms) for Suites SRTP. [SRTPofferedSuites]  [0] = (Default) All available crypto suites.  [1] CIPHER SUITES AES CM 128 HMAC SHA1 80 = device uses Version 6.6 Mediant 2000...
  • Page 532 Mediant 2000 Parameter Description AES-CM encryption with a 128-bit key and HMAC-SHA1 message authentication with a 80-bit tag.  [2] CIPHER SUITES AES CM 128 HMAC SHA1 32 = device uses AES-CM encryption with a 128-bit key and HMAC-SHA1 message authentication with a 32-bit tag.

  • Page 533: Tls Parameters

    If DNSName is used, the certificate can also use wildcards (‘*’) to replace parts of the domain name. If the SubjectAltName is not marked as ‘critical’ and there is no match, the CN value of the SubjectName field is compared with the parameter Version 6.6 Mediant 2000...
  • Page 534 Mediant 2000 Parameter Description TLSRemoteSubjectName. If a match is found, the connection is established. Otherwise, the connection is terminated. Note: If you set this parameter to [2] (Server & Client), for this functionality to operate, you also need to set the SIPSRequireClientCertificate parameter to [1] (Enable).

  • Page 535: Ssh Parameters

    Web: Max Login Defines the maximum SSH login attempts allowed for entering an Attempts incorrect password by an administrator before the SSH session is [SSHMaxLoginAttempt rejected. The valid range is 1 to 3. the default is 3. Version 6.6 Mediant 2000...

  • Page 536: Ipsec Parameters

    Mediant 2000 45.4.6 IPSec Parameters The Internet Protocol security (IPSec) parameters are described in the table below. IPSec Parameters Parameter Description IPSec Parameters Web: Enable IP Security Enables IPSec on the device. EMS: IPSec Enable  [0] Disable (default) [EnableIPSec] ...

  • Page 537: Ocsp Parameters

    Web: Default Response Determines the default OCSP behavior when the server cannot be When Server contacted. Unreachable  [0] Reject = (Default) Rejects peer certificate. EMS: OCSP Default  [1] Allow = Allows peer certificate. Response [OCSPDefaultRespons Version 6.6 Mediant 2000...

  • Page 538: Ids Parameters

    Mediant 2000 45.4.8 IDS Parameters The Intrusion Detection System (IDS) parameters are described in the table below. Table 45-1: IDS Parameters Parameter Description Web: Intrusion Detection Enables the IDS feature. System (IDS)  [0] Disable (default) CLI: enable-ids  [1] Enable [EnableIDS] Note: For this parameter to take effect, a device reset is required.

  • Page 539: Radius Parameters

    1 in order to force the use of HTTPS, since the transport is encrypted.  If using RADIUS authentication to log into the CLI, only the primary Web User Account, which has Security Administration access level, can access the device's CLI (see 'Configuring Web User Accounts' Version 6.6 Mediant 2000...
  • Page 540 Mediant 2000 Parameter Description on page 60). Web: RADIUS Defines the IP address of the RADIUS authentication server. Authentication Server IP Note: For this parameter to take effect, a device reset is required. Address EMS: RADIUS Auth Server IP [RADIUSAuthServerIP] Web: RADIUS Defines the port of the RADIUS Authentication Server.

  • Page 541: Sip Media Realm Parameters

    Bandwidth Management per Media Realm Table Web: Bandwidth This table parameter defines bandwidth management rules per Media Management Realm. [BWManagement] The format of this parameter is as follows: [ BWManagement ] FORMAT BWManagement_Index = BWManagement_MediaRealmIndex, BWManagement_ThresholdIndex, BWManagement_RuleAction, BWManagement_Threshold, BWManagement_Hysteresis; Version 6.6 Mediant 2000...

  • Page 542: Control Network Parameters

    Mediant 2000 Parameter Description [ \BWManagement ] Where ThresholdIndex is the bandwidth threshold rule type:  [0] High Threshold Rule  [1] Critical Threshold Rule Notes:  For this parameter to take effect, a device reset is required.  This table can include up to two row entries (where 0 is the first index).
  • Page 543 [1] Homing = The device always tries to work with the primary Proxy server (i.e., switches back to the primary Proxy whenever it's available). Note: To use this Proxy Redundancy mechanism, you need to enable the keep-alive with Proxy option, by setting the parameter Version 6.6 Mediant 2000...
  • Page 544 Mediant 2000 Parameter Description EnableProxyKeepAlive to 1 or 2. Web: Proxy IP List Defines the time interval (in seconds) between each Proxy IP list Refresh Time refresh. EMS: IP List Refresh The range is 5 to 2,000,000. The default interval is 60.
  • Page 545 If the Proxy IP address parameter contains a domain name with port definition (e.g., ProxyIP = domain.com:5080), the device performs a regular DNS A-record query. If a specific Transport Type is defined, a NAPTR query is not Version 6.6 Mediant 2000...
  • Page 546 Mediant 2000 Parameter Description performed. Note: When enabled, NAPTR/SRV queries are used to discover Proxy servers even if the parameter DNSQueryType is disabled. Web/EMS: Use Gateway Determines whether the device uses its IP address or gateway name in Name for OPTIONS keep-alive SIP OPTIONS messages.
  • Page 547 EMS: Is Register Needed  [0] Disable = (Default) The device doesn't register to Proxy/Registrar [IsRegisterNeeded] server.  [1] Enable = The device registers to Proxy/Registrar server when the device is powered up and at every user-defined interval (configured Version 6.6 Mediant 2000...
  • Page 548 Mediant 2000 Parameter Description by the parameter RegistrationTime). Note: The device sends a REGISTER request for each channel or for the entire device (according to the AuthenticationMode parameter). Web/EMS: Registrar Defines the Registrar domain name. If specified, the name is used as Name the Request-URI in REGISTER messages.
  • Page 549 (i.e., AuthenticationMode is set to 0), the user name is set to the channel's phone number. Web/EMS: Registration Determines the device's registration and authentication method. Mode  [0] Per Endpoint = Registration and authentication is performed Version 6.6 Mediant 2000...
  • Page 550 Mediant 2000 Parameter Description [AuthenticationMode] separately for each B-channel.  [1] Per Gateway = (Default) Single registration and authentication for the entire device. This is typically used for and digital modules. Web: Set Out-Of-Service Enables setting the , trunk, or entire device (i.e., all endpoints) to out-of- On Registration Failure service if registration fails.
  • Page 551 For example, if the parameter value is set to 200 sec, the interval used is any random time between 160 to 200 seconds. This prevents an “avalanche” of keep-alive by multiple SIP UAs to a specific server. Version 6.6 Mediant 2000...

  • Page 552: Network Application Parameters

    Mediant 2000 45.7.2 Network Application Parameters The SIP network application parameters are described in the table below. SIP Network Application Parameters Parameter Description Signaling Routing Domain Table Web: SRD Settings This table parameter configures the Signaling Routing Domain (SRD) EMS: SRD Table table.

  • Page 553: General Sip Parameters

    (if Automatic Update has been enabled on the device)  '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 Message Length [KB] be sent over the network.
  • Page 554 Mediant 2000 Parameter Description The valid value range is 1 to 50. The default is 50. [SIPForceRport] Determines whether the device sends SIP responses to the UDP port from where SIP requests are received even if the 'rport' parameter is not present in the SIP Via header.
  • Page 555 Alert + PI to SIP 183 + SDP instead of 180 + SDP.  You can also configure early SIP 183 response immediately upon receipt of an INVITE, using the EnableEarly183 parameter. Version 6.6 Mediant 2000...
  • Page 556 Mediant 2000 Parameter Description  This feature can also be configured as an IP Profile and/or Tel Profile. Web/EMS: Enable Early Enables the device to send SIP 183 responses with SDP to the IP upon receipt of INVITE messages. This parameter is applicable to IP-to-Tel (ISDN) and IP-to-IP calls, and applies to all calls.
  • Page 557 Defines the user part value of the Request-URI for outgoing SIP [OPTIONSUserPart] OPTIONS requests. If no value is configured, the configuration parameter ‘Username’ valueis used. A special value is ‘empty’, indicating that no user part in the Request- Version 6.6 Mediant 2000...
  • Page 558 Mediant 2000 Parameter Description URI (host part only) is used. The valid range is a 30-character string. The default is an empty string (‘’). Web: TDM Over IP Defines the minimal number of SIP dialogs that must be established Minimum Calls For Trunk when using TDM Tunneling to consider the specific trunk as active.
  • Page 559 [1] TCP  [2] TLS (SIPS) Notes:  It's recommended to use TLS for communication with a SIP Proxy and not for direct device-to-device communication.  For received calls (i.e., incoming), the device accepts all these protocols. Version 6.6 Mediant 2000...
  • Page 560 Mediant 2000 Parameter Description  The value of this parameter is also used by the SAS application as the default transport layer for outgoing SIP calls. Web: SIP UDP Local Port Defines the local UDP port for SIP messages. EMS: Local SIP Port The valid range is 1 to 65534.
  • Page 561 Enables Remote-Party-Identity headers for calling and called numbers Party ID for Tel-to-IP calls. EMS: Enable RPI Header  [0] Disable (default). [EnableRPIheader]  [1] Enable = Remote-Party-Identity headers are generated in SIP INVITE messages for both called and calling numbers. Version 6.6 Mediant 2000...
  • Page 562 Mediant 2000 Parameter Description Web: Enable History-Info Enables usage of the History-Info header. Header  [0] Disable (default) EMS: Enable History Info  [1] Enable [EnableHistoryInfo] User Agent Client (UAC) Behavior:  Initial request: The History-Info header is equal to the Request-URI.
  • Page 563 INVITE Request-URI and Contact header includes “tgrp=ccdata;trunk-context=dsn.mil”. If the Bearer Capability IE contains “Speech”, the INVITE in this case does not contain tgrp and trunk-context parameters. Note: IP-to-Tel configuration (using the PSTNPrefix parameter) overrides the 'tgrp' parameter in incoming INVITE messages. Version 6.6 Mediant 2000...
  • Page 564 Mediant 2000 Parameter Description Web/EMS: TGRP Routing Determines the precedence method for routing IP-to-Tel calls - Precedence according to the Inbound IP Routing Table or according to the SIP 'tgrp' [TGRProutingPrecedenc parameter.  [0] = (Default) IP-to-Tel routing is determined by the Inbound IP Routing Table (PSTNPrefix parameter).
  • Page 565 EMS: User Agent Display value>/software version' is used, for example: Info User-Agent: myproduct/v.6.40.010.006 [UserAgentDisplayInfo] If not configured, the default string, <AudioCodes product- name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 2000/v.6.40.010.006 The maximum string length is 50 characters. Version 6.6...
  • Page 566 Mediant 2000 Parameter Description Note: The software version number and preceding forward slash (/) cannot be modified. Therefore, it is recommended not to include a forward slash in the parameter's value (to avoid two forward slashes in the SIP header, which may cause problems).
  • Page 567 Determines the device usage of the P-Associated-URI header. This Associated-URI Header header can be received in 200 OK responses to REGISTER requests. [EnablePAssociatedURI When enabled, the first URI in the P-Associated-URI header is used in Header] subsequent requests as the From/P-Asserted-Identity headers value. Version 6.6 Mediant 2000...
  • Page 568 Mediant 2000 Parameter Description  [0] Disable (default)  [1] Enable Note: P-Associated-URIs in registration responses is handled only if the device is registered per endpoint (using the User Information file). Web/EMS: Source Determines from which SIP header the source (calling) number is Number Preference obtained in incoming INVITE messages.
  • Page 569 (An alternative method for obtaining the list of supported capabilities is by using SIP OPTIONS, which is not supported by every SIP agent.)  [0] Disable = (Default) The device sends the initial INVITE message Version 6.6 Mediant 2000...
  • Page 570 Mediant 2000 Parameter Description with an SDP.  [1] Enable = The device sends the initial INVITE message without an SDP. [DisableCryptoLifeTimeI Enables the device to send "a=crypto" lines without the lifetime nSDP] parameter in the SDP. For example, if the SDP contains "a=crypto:12 AES_CM_128_HMAC_SHA1_80 inline:hhQe10yZRcRcpIFPkH5xYY9R1de37ogh9G1MpvNp|2^31", it...
  • Page 571 Progress message with SDP in response to only the first received ISDN Proceeding or Progress message after a call is placed to PBX/PSTN over the trunk. Note: This parameter can also be configured per IP Profile (using the Version 6.6 Mediant 2000...
  • Page 572 Mediant 2000 Parameter Description IPProfile parameter) and Tel Profile (using the TelProfile parameter). [EnableRekeyAfter181] Enables the device to send a re-INVITE with a new (different) SRTP key (in the SDP) if a SIP 181 response is received ("call is being forwarded").
  • Page 573 INVITE request.  [0] = 100 Trying response is sent upon receipt of a Proceeding message from the PSTN.  [1] = (Default) 100 Trying response is sent immediately upon receipt of INVITE request. Version 6.6 Mediant 2000...
  • Page 574 Mediant 2000 Parameter Description [TransparentCoderPres Determines the format of the Transparent coder representation in the entation] SDP.  [0] = clearmode (default)  [1] = X-CCD [IgnoreRemoteSDPMKI] Determines whether the device ignores the Master Key Identifier (MKI) if present in the SDP received from the remote side.
  • Page 575 To configure the RTP Only mode per trunk, use the RTPOnlyModeForTrunk_x parameter.  If per trunk configuration (using the RTPOnlyModeForTrunk_x parameter) is set to a value other than the default, the RTPOnlyMode parameter value is ignored. Version 6.6 Mediant 2000...
  • Page 576 Mediant 2000 Parameter Description [RTPOnlyModeForTrunk Enables the RTP Only feature per trunk, where ID denotes the trunk number (0 is the first trunk). For more information, see the RTPOnlyMode parameter. Note: For using the global parameter (i.e., setting the RTP Only feature for all trunks), set this parameter to -1 (default).
  • Page 577 DigitalOOSBehavior parameter for per device. [DigitalOOSBehaviorFor  [0] Default = Uses default behavior for each trunk (see note below). Trunk_x]  [1] Service = Sends ISDN In or Out of Service (only for ISDN protocols that support Service message). Version 6.6 Mediant 2000...
  • Page 578 Mediant 2000 Parameter Description  [2] D-Channel = Takes D-Channel down or up (ISDN only).  [3] Alarm = Sends or clears PSTN AIS Alarm (ISDN and CAS).  [4] Block = Blocks trunk (CAS only). Notes:  This parameter is applicable only if the parameter EnableBusyOut is set to 1.
  • Page 579 The format of this parameter is as follows: [MessagePolicy] [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Policy, MessagePolicy_MaxMessageLength, MessagePolicy_MaxHeaderLength, MessagePoliy_MaxBodyLength, MessagePolicy_MaxNumHeaders, MessagePolicy_MaxNumBodies, MessagePolicy_SendRejection, MessagePolicy_MethodListType, MessagePolicy_MethodList, MessagePolicy_BodyListType, MessagePolicy_BodyList; [/MessagePolicy] Note: For a detailed description of this table, see 'Configuring SIP Message Policy Rules'. Version 6.6 Mediant 2000...

  • Page 580: Coders And Profile Parameters

    Mediant 2000 45.9 Coders and Profile Parameters The profile parameters are described in the table below. Profile Parameters Parameter Description Coders Table / Coder Groups Table Web: Coders Table/Coder This table parameter defines the device's coders. Each group can consist Group Settings of up to 10 coders.
  • Page 581 Tel Profiles allow you to apply the same settings of a group of parameters to multiple channels, or apply specific settings to different channels. The format of this parameter is as follows: [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, Version 6.6 Mediant 2000...
  • Page 582 Mediant 2000 Parameter Description TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP, TelProfile_TimeForReorderTone, TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode; [\TelProfile] Notes:  For a description of this parameter, see Configuring Tel Profiles on page 233.

  • Page 583: Channel Parameters

    (IP-to-PSTN) signal. [VoiceVolume] The valid range is -32 to 31 dB. The default is 0 dB. Note: This parameter can also be configured in an IP Profile and/or a Tel Profile. Version 6.6 Mediant 2000...
  • Page 584 Mediant 2000 Parameter Description EMS: Payload Format Determines the bit ordering of the G.726/G.727 voice payload [VoicePayloadFormat] format.  [0] = (Default) Little Endian  [1] = Big Endian Note: To ensure high voice quality when using G.726/G.727, both communicating ends should use the same endianness format.
  • Page 585 Note: For this parameter to take effect, a device reset is required. Defines the number of spectral coefficients added to an SID [RTPSIDCoeffNum] packet being sent according to RFC 3389. The valid values are [0] (default), [4], [6], [8] and [10]. Version 6.6 Mediant 2000...

  • Page 586: Coder Parameters

    Mediant 2000 45.10.2 Coder Parameters The coder parameters are described in the table below. Coder Parameters Parameter Description Enables the EVRC voice activity detector. [EnableEVRCVAD]  [0] = Disable (default)  [1] = Enable Note: Supported for EVRC and EVRC-B coders.

  • Page 587: Dtmf Parameters

    The valid range is -31 to 0 dB. The default is -11 dB. [DTMFVolume] Note: This parameter can also be configured in a Tel Profile. Web: DTMF Generation Twist Defines the range (in decibels) between the high and low Version 6.6 Mediant 2000...

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

    Mediant 2000 Parameter Description EMS: DTMF Twist Control frequency components in the DTMF signal. Positive decibel values [DTMFGenerationTwist] cause the higher frequency component to be stronger than the lower one. Negative values cause the opposite effect. For any parameter value, both components change so that their average is constant.
  • Page 589 RTPRedundancyDepth is set to 1. Web: Packing Factor N/A. Controlled internally by the device according to the selected EMS: Packetization Factor coder. [RTPPackingFactor] Web/EMS: Basic RTP Packet N/A. Controlled internally by the device according to the selected Interval coder. [BasicRTPPacketInterval] Version 6.6 Mediant 2000...
  • Page 590 Mediant 2000 Parameter Description Web: RTP Directional Control N/A. Controlled internally by the device according to the selected [RTPDirectionControl] coder. Web/EMS: RFC 2833 TX Defines the Tx RFC 2833 DTMF relay dynamic payload type. Payload Type The valid range is 96 to 99, and 106 to 127. The default is 96. The [RFC2833TxPayloadType] 100, 102 to 105 range is allocated for proprietary usage.
  • Page 591 (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 Version 6.6 Mediant 2000...
  • Page 592 Mediant 2000 Parameter Description parameter. EMS: No Op Payload Type Defines the payload type of No-Op packets. [RTPNoOpPayloadType] The valid range is 96 to 127 (for the range of Dynamic RTP Payload Type for all types of non hard-coded RTP Payload types, refer to RFC 3551).

  • Page 593: Gateway And Ip-To-Ip Parameters

    [3] Events Only = Transparent with Events Note: This parameter can also be configured in an IP Profile. Web: V.23 Modem Transport Determines the V.23 modem transport type. Type  [0] Disable = Disable (Transparent) EMS: V23 Transport Version 6.6 Mediant 2000...
  • Page 594 Mediant 2000 Parameter Description  [V23ModemTransportType] [2] Enable Bypass (default)  [3] Events Only = Transparent with Events Note: This parameter can also be configured in an IP Profile. Web: V.32 Modem Transport Determines the V.32 modem transport type. Type ...
  • Page 595 The valid range is 1, 2, or 3 coder payloads. The default is 1 coder [FaxModemBypassM] payload. Determines whether the device sends RFC 2833 ANS/ANSam [FaxModemNTEMode] events upon detection of fax and/or modem Answer tones (i.e., CED tone).  [0] = Disabled (default)  [1] = Enabled Version 6.6 Mediant 2000...
  • Page 596 Mediant 2000 Parameter Description Note: This parameter is applicable only when the fax or modem transport type is set to bypass or Transparent-with-Events. Web/EMS: Fax Bypass Defines the fax bypass RTP dynamic payload type. Payload Type The valid range is 96 to 120. The default is 102.
  • Page 597 This option can only be used to relay fax signals, as the device sends T.38 Re-INVITE on detection of any fax/modem Answer tone (2100 Hz, amplitude modulated 2100 Hz, or 2100 Hz with phase reversals). The modem signal Version 6.6 Mediant 2000...

  • Page 598: Dtmf And Hook-Flash Parameters

    Mediant 2000 Parameter Description fails when using T.38 for fax relay. Note: This parameters is applicable only if the parameter IsFaxUsed is set to 1 (T.38 Relay) or 3 (Fax Fallback). Web: T38 Fax Session Enables fax transmission of T.38 "no-signal" packets to the Immediate Start terminating fax machine.
  • Page 599 [\TxDTMFOption] Where Type is:  [0] Not Supported = (Default) No negotiation - DTMF digits are sent according to the parameters DTMFTransportType and RFC2833PayloadType.  [1] INFO (Nortel) = Sends DTMF digits according to IETF Internet- Version 6.6 Mediant 2000...
  • Page 600 Mediant 2000 Parameter Description Draft draft-choudhuri-sip-info-digit-00.  [2] NOTIFY = Sends DTMF digits according to IETF Internet-Draft draft-mahy-sipping-signaled-digits-01.  [3] INFO (Cisco) = Sends DTMF digits according to Cisco format.  [4] RFC 2833.  [5] INFO (Korea) = Sends DTMF digits according to Korea Telecom format.

  • Page 601: Digit Collection And Dial Plan Parameters

    DConvert utility). The Dial Plan index can be defined globally or per Tel Profile. The valid value range is 0 to 7, where 0 denotes PLAN1, 1 denotes PLAN2, and so on. The default is -1, indicating that no Dial Plan Version 6.6 Mediant 2000...
  • Page 602 Mediant 2000 Parameter Description file is used. Notes:  If this parameter is configured to select a Dial Plan index, the settings of the parameter DigitMapping are ignored.  If this parameter is configured to select a Dial Plan index from...

  • Page 603: Voice Mail Parameters

    Voice Mail server to an IP Group (configured using the NotificationIPGroupID parameter).  [8] ETSI = Euro ISDN, according to ETS 300 745-1 V1.2.4, section 9.5.1.1. Enables MWI interworking from IP to Tel, typically used for BRI phones. Version 6.6 Mediant 2000...
  • Page 604 Mediant 2000 Parameter Description Note: To disable voice mail per Trunk Group, you can use a Tel Profile with the EnableVoiceMailDelay parameter set to disabled (0). This eliminates the phenomenon of call delay on Trunks not implementing voice mail when voice mail is enabled using this global parameter.
  • Page 605 Web: MWI Source Defines the calling party's phone number used in the Q.931 MWI Number Setup message to PSTN. If not configured, the channel's phone EMS: MWI Source Name number is used as the calling number. [MWISourceNumber] Version 6.6 Mediant 2000...
  • Page 606 Mediant 2000 Parameter Description Defines the IP Group ID used when subscribing to an MWI server. [MWISubscribeIPGroupI The 'The SIP Group Name' field value of the IP Group table is used as the Request-URI host name in the outgoing MWI SIP SUBSCRIBE message.
  • Page 607 The valid range is a 120-character string. Reason External [DigitPatternForwardNo ReasonExt] Web: Internal Call Digit Defines the digit pattern used by the PBX to indicate an internal call. Pattern The valid range is a 120-character string. EMS: Digit Pattern Internal Call [DigitPatternInternalCall Version 6.6 Mediant 2000...

  • Page 608: Supplementary Services Parameters

    Mediant 2000 Parameter Description Web: External Call Digit Defines the digit pattern used by the PBX to indicate an external call. Pattern The valid range is a 120-character string. EMS: Digit Pattern External Call [DigitPatternExternalCal Web: Disconnect Call Defines a digit pattern that when received from the Tel side, indicates Digit Pattern the device to disconnect the call.
  • Page 609 FORMAT RejectAnonymousCallPerPort_Index = RejectAnonymousCallPerPort_Enable; [\RejectAnonymousCallPerPort] Where,  Enable = accept [0] (default) or reject [1] incoming anonymous calls. For example: RejectAnonymousCallPerPort 0 = 0; RejectAnonymousCallPerPort 1 = 1; Note: This parameter is applicable only to FXS interfaces. Version 6.6 Mediant 2000...

  • Page 610: Call Waiting Parameters

    Mediant 2000 45.11.5.2 Call Waiting Parameters The call waiting parameters are described in the table below. Call Waiting Parameters Parameter Description Web/EMS: Enable Call Enables the Call Waiting feature. Waiting  [0] Disable [EnableCallWaiting]  [1] Enable (Default) If enabled and the device initiates a Tel-to-IP call to a destination that is busy, it plays a call waiting ringback tone to the caller.

  • Page 611: Call Transfer Parameters

    The number manipulation rules apply to the user part of the Refer-To and/or Contact URI before it is sent in the INVITE message.  This parameter can be used to apply different manipulation rules to differentiate transferred number from the originally dialed number. Version 6.6 Mediant 2000...
  • Page 612 Mediant 2000 Parameter Description Web: Transfer Prefix IP 2 Defines the prefix that is added to the destination number received in the SIP Refer-To header (for IP-to-Tel calls). This parameter is applicable to [XferPrefixIP2Tel] CAS blind transfer modes, i.e., LineTransferMode = 1, 2 or 3, and TrunkTransferMode = 1 or 3 (for CAS).

  • Page 613: Mlpp And Emergency Call Parameters

    The incoming SIP INVITE message contains the “emergency” value in the Priority header. Notes:  This parameter is applicable to CAS, and ISDN.  MLPP and Emergency services can also be configured in a Tel Profile. Version 6.6 Mediant 2000...
  • Page 614 Mediant 2000 Parameter Description  For more information, see 'Pre-empting Existing Call for E911 IP-to- Tel Call' on page 338. Emergency E911 Parameters [E911Gateway] Enables Enhanced 9-1-1(E9-1-1) support for ELIN handling in Microsoft Lync Server 2010 environment.  [0] = Disable (default) ...
  • Page 615 Tone Duration preemption tone to the Tel and IP sides if a call is preempted. [PreemptionToneDurati The valid range is 0 to 60. The default is 3. Note: If set to 0, no preemption tone is played. Version 6.6 Mediant 2000...
  • Page 616 Mediant 2000 Parameter Description Web: MLPP Normalized Defines the MLPP normalized service domain string. If the device Service Domain receives an MLPP ISDN incoming call, it uses the parameter (if different EMS: Normalized Service from ‘FFFFFF’) as a Service domain in the SIP Resource-Priority Domain header in outgoing INVITE messages.
  • Page 617 The valid range is -1 to 63. The default is -1. [MLPPFlashOverOverRT Note: If set to -1, the DiffServ value is taken from the global parameter PDSCP] PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call. Version 6.6 Mediant 2000...

  • Page 618: Call Cut-Through Parameters

    Mediant 2000 45.11.5.7 Call Cut-Through Parameters The call cut-through parameters are described in the table below. Call Cut-Through Parameters Parameter Description [DigitalCutThrough] Enables PSTN CAS channels/endpoints to receive incoming IP calls even if the B-channels are in off-hook state. ...

  • Page 619: Pstn Parameters

    [17] E1 AUSTEL ISDN = ISDN PRI protocol for the Australian Telecom.  [18] E1 HKT ISDN = ISDN PRI (E1) protocol for the Hong Kong - HKT.  [19] E1 KOR ISDN = ISDN PRI protocol for Korean Operator Version 6.6 Mediant 2000...
  • Page 620 Mediant 2000 Parameter Description (similar to ETSI).  [20] T1 HKT ISDN = ISDN PRI (T1) protocol for the Hong Kong - HKT.  [21] E1 QSIG = ECMA 143 QSIG over E1  [22] E1 TNZ = ISDN PRI protocol for Telecom New Zealand (similar to ETSI) ...
  • Page 621 ID (where x denotes the Trunk ID and 0 is the first Trunk). Web/EMS: Clock Master Determines the Tx clock source of the E1/T1 line. [ClockMaster]  [0] Recovered = (Default) Generate the clock according to the Rx of the E1/T1 line. Version 6.6 Mediant 2000...
  • Page 622 Mediant 2000 Parameter Description  [1] Generated = Generate the clock according to the internal TDM bus. Note: The source of the internal TDM bus clock is determined by the parameter TDMBusClockSource. [ClockMaster_x] Same as the description for parameter ClockMaster, but for a specific Trunk ID (where x denotes the Trunk ID and 0 is the first Trunk).

  • Page 623: Tdm Bus And Clock Timing Parameters

    This parameter is applicable only when using PSTN interface with CAS protocols. Web/EMS: TDM Bus Clock Determines the clock source to which the device synchronizes. Source  [1] Internal = (Default) Generate clock from local source. Version 6.6 Mediant 2000...
  • Page 624 Mediant 2000 Parameter Description  [TDMBusClockSource] [4] Network = Recover clock from PSTN line. Web/EMS: TDM Bus Local Defines the physical Trunk ID from which the device recovers Reference (receives) its clock synchronization. [TDMBusLocalReference] The range is 0 to the maximum number of Trunks. The default is...

  • Page 625: Cas Parameters

    Web: CAS Table per Trunk Defines the CAS protocol per trunk from a list of CAS protocols EMS: Trunk CAS Table Index defined by the parameter CASFileName_x. [CASTableIndex_x] For example, the below configuration specifies Trunks 0 and 1 to Version 6.6 Mediant 2000...
  • Page 626 Mediant 2000 Parameter Description use the E&M Winkstart CAS (E_M_WinkTable.dat) protocol, and Trunks 2 and 3 to use the E&M Immediate Start CAS (E_M_ImmediateTable.dat) protocol: CASFileName_0 = 'E_M_WinkTable.dat' CASFileName_1 = 'E_M_ImmediateTable.dat' CASTableIndex_0 = 0 CASTableIndex_1 = 0 CASTableIndex_2 = 1...
  • Page 627 In some cases, when the state machine handles the ANI [CASStateMachineCollectAN collection (not related to MFCR2), you can enable the state machine to collect ANI or discard ANI.  [0] No = Don't collect ANI.  [1] Yes = Collect ANI. Version 6.6 Mediant 2000...

  • Page 628: Isdn Parameters

    Mediant 2000 Parameter Description  [-1] Default = Default value. Web: Digit Signaling System Defines which Signaling System to use in both directions [CASStateMachineDigitSigna (detection\generation). lingSystem]  [0] DTMF = DTMF signaling.  [1] MF = (Default) MF signaling. ...
  • Page 629 Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters can be used. Web/EMS: Incoming Calls Determines the bit-field used to determine several behavior Behavior options that influence how the ISDN Stack INCOMING calls [ISDNInCallsBehavior] behave. Version 6.6 Mediant 2000...
  • Page 630 Mediant 2000 Parameter Description  [32] DATA CONN RS = The device automatically sends a Q.931 Connect (answer) message on incoming Tel calls (Q.931 Setup).  [64] VOICE CONN RS = The device sends a Connect (answer) message on incoming Tel calls.
  • Page 631 ECMA standards); otherwise, OBJECT IDENTIFIER ASN.1 type is used. Note: This option is applicable only to QSIG.  [2147483648] 5ESS National Mode For Bch Maintenance = Use the National mode of AT&T 5ESS for B-channel maintenance. Version 6.6 Mediant 2000...
  • Page 632 Mediant 2000 Parameter Description Notes:  To configure the device to support several ISDNIBehavior features, enter a summation of the individual feature values. For example, to support both [512] and [2048] features, set the parameter ISDNIBehavior is set to 2560 (i.e., 512 + 2048).
  • Page 633 IA5 character in the called_nb, and is not restricted to extended digits only (i.e., 0-9,*,#).  [16384] DLCI REVERSED OPTION = Behavior bit used in the IUA interface groups to indicate that the reversed format of the Version 6.6 Mediant 2000...
  • Page 634 Mediant 2000 Parameter Description DLCI field must be used. Note: When using the ini file to configure the device to support several ISDNOutCallsBehavior features, add the individual feature values. For example, to support both [2] and [16] features, set ISDNOutCallsBehavior = 18 (i.e., 2 + 16).

  • Page 635: Isdn And Cas Interworking Parameters

    Note: When IP-to-Tel overlap dialing is enabled, to send ISDN Setup messages without the Sending Complete IE, the ISDNOutCallsBehavior parameter must be set to USER SENDING COMPLETE (2). Web: Enable Receiving Determines the receiving (Rx) type of ISDN overlap dialing for Tel-to-IP Version 6.6 Mediant 2000...
  • Page 636 Mediant 2000 Parameter Description of Overlap Dialing calls, per trunk. [ISDNRxOverlap_x]  [0] None = (Default) Disabled.  [1] Local receiving = ISDN Overlap Dialing - the complete number is sent in the INVITE Request-URI user part. The device receives ISDN called number that is sent in the 'Overlap' mode.
  • Page 637 IE to the outgoing Q.931 message as 1C269FAA 06 800100820100A10F020136 0201F0A00702010102021F69, where, for example, "1C269F" is a 26 byte length Facility IE. Note: This feature is similar to that of the AddIEinSetup parameter. If both parameters are configured, the x-isdntunneling parameter takes precedence. Version 6.6 Mediant 2000...
  • Page 638 Mediant 2000 Parameter Description Web/EMS: Enable QSIG Enables QSIG tunneling-over-SIP for all calls. This is according to IETF Tunneling Internet-Draft draft-elwell-sipping-qsig-tunnel-03 and ECMA-355 and [EnableQSIGTunneling] ETSI TS 102 345.  [0] Disable (default).  [1] Enable = Enable QSIG tunneling from QSIG to SIP and vice versa.
  • Page 639 ISDN Setup message then contains y digits from the end of the called number. The y number of digits can be configured using the ISUBNumberOfDigits parameter. The default value of ISUBNumberOfDigits is 0, thus, if this parameter Version 6.6 Mediant 2000...
  • Page 640 Mediant 2000 Parameter Description is not configured, and 1) and 2) scenarios (described above) have not provided an isub value, the subaddress remains empty. Web: Default Cause Defines a single default ISDN release cause that is used (in ISDN-to-IP Mapping From ISDN to calls) instead of all received release causes, except when the following Q.931 cause values are received: Normal Call Clearing (16), User Busy...
  • Page 641 ISDN Setup message (including the Calling Name) with an ISDN "REQUESTED_FAC_NOT_SUBSCRIBED" failure. This parameter can be set to Enable (1) to remove the “Calling Name” from SIP-to-ISDN calls and allow the call to proceed. Version 6.6 Mediant 2000...
  • Page 642 Mediant 2000 Parameter Description Web: Remove Calling Enables the device to remove the Calling Name per trunk for SIP-to- Name ISDN calls. EMS: Remove Calling  [-1] Use Global Parameter = (Default) Settings of the global Name For Trunk Mode parameter RemoveCallingName are used.
  • Page 643 Inbound IP Routing Table (PSTNPrefix ini file parameter) a rule to route the redirected call (using the user part from the 302 Contact header) to the same Trunk Group from where the incoming Tel-to-IP call was received. Version 6.6 Mediant 2000...
  • Page 644 Mediant 2000 Parameter Description EMS: Enable CIC Determines whether the Carrier Identification Code (CIC) is relayed to [EnableCIC] ISDN.  [0] = (Default) Do not relay the Carrier Identification Code (CIC) to ISDN.  [1] = CIC is relayed to the ISDN in Transit Network Selection (TNS) If enabled, the CIC code (received in an INVITE Request-URI) is included in a TNS IE in the ISDN Setup message.
  • Page 645 When enabled, the From header received in the SIP INVITE is translated into the following ISDN IE's:  Emergency Call Control.  Generic Information - to carry the Location Identification Number information.  Generic Information - to carry the Calling Geodetic Location Version 6.6 Mediant 2000...
  • Page 646 Mediant 2000 Parameter Description information. Note: This capability is applicable only to the NI-2 ISDN variant. Defines the duration (in seconds) that the device waits for an ISDN [EarlyAnswerTimeout] Connect message from the called party (Tel side), started from when it sends a Setup message.
  • Page 647 TrunkTransferMode_X. Determines the trunk transfer mode per trunk (where x is the Trunk ID). [TrunkTransferMode_X For configuring trunk transfer mode for all trunks and for a description of the parameter options, refer to the parameter TrunkTransferMode. Version 6.6 Mediant 2000...
  • Page 648 Mediant 2000 Parameter Description [EnableTransferAcross Determines whether the device allows ISDN ECT, RLT or TBCT IP-to- TrunkGroups] Tel call transfers between B-channels of different Trunk Groups.  [0] = (Default) Disable - ISDN call transfer is only between B- channels of the same Trunk Group.
  • Page 649 CAS trunk. The CAS wink signal is done by changing the A bit from 1 to 0, and then back to 1 for 450 msec. INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: <sip:06@192.168.13.2:5060> <sip:4505656002@192.168.13.40:5060>;tag=132878796- 1040067870294 Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2 CSeq:2 INFO Version 6.6 Mediant 2000...

  • Page 650: Answer And Disconnect Supervision Parameters

    Mediant 2000 Parameter Description Content-Type: application/broadsoft Content-Length: 17 event flashhook Note: This parameter is applicable only to T1 CAS protocols. 45.11.8 Answer and Disconnect Supervision Parameters The answer and disconnect supervision parameters are described in the table below. Answer and Disconnect Parameters...
  • Page 651 This parameter is applicable only for DSP templates 2 and 3. ncePeriod]  For this parameter to take effect, a device reset is required. Web: Silence Detection Determines the silence detection method. Method  [0] None = Silence detection option is disabled. [FarEndDisconnectSile Version 6.6 Mediant 2000...
  • Page 652 Mediant 2000 Parameter Description  nceMethod] [1] Packets Count = According to packet count. Note: For this parameter to take effect, a device reset is required. [FarEndDisconnectSile Defines the threshold of the packet count (in percentages) below which nceThreshold] is considered silence by the device.

  • Page 653: Tone Parameters

     [0] Don't Play = (Default) Immediately sends an ISDN Disconnect message.  [1] Play when Disconnecting = Sends an ISDN Disconnect message with PI = 8 and plays a busy or reorder tone to the Version 6.6 Mediant 2000...
  • Page 654 Mediant 2000 Parameter Description PSTN (depending on the release cause).  [2] Play before Disconnect = Delays the sending of an ISDN Disconnect message for a user-defined time (configured by the TimeForReorderTone parameter) and plays a busy or reorder tone to the PSTN. This is applicable only if the call is released from the IP [Busy Here (486) or Not Found (404)] before it reaches the Connect state;...
  • Page 655 PSTN plays the ringback tone to the originating terminal. Note that the receipt of a 183 response does not cause the device to play a ringback tone; the device sends a Progress message (unless SIP183Behaviour is set to 1). If Version 6.6 Mediant 2000...
  • Page 656 Mediant 2000 Parameter Description the SIP183Behaviour parameter is set to 1, the 183 response is handled the same way as a 180 Ringing response.  [2] Prefer IP = Plays according to 'Early Media'. If a SIP 180 response is received and the voice channel is already open...

  • Page 657: Tone Detection Parameters

    Tone Detection Parameters The signal tone detection parameters are described in the table below. Tone Detection Parameters Parameter Description EMS: DTMF Enable Enables the detection of DTMF signaling. [DTMFDetectorEnable]  [0] = Disable  [1] = Enable (default) Version 6.6 Mediant 2000...
  • Page 658 Mediant 2000 Parameter Description EMS: MF R1 Enable Enables the detection of MF-R1 signaling. [MFR1DetectorEnable]  [0] = Disable (default)  [1] = Enable EMS: R1.5 Detection Standard Determines the MF-R1 protocol used for detection. [R1DetectionStandard]  [0] = ITU (default) ...

  • Page 659: Metering Tone Parameters

    ChargeCode 3 = 0,60,1; ChargeCode 0 = 6, 3, 1, 12, 2, 1, 18, 5, 2, 0, 2, 1; Note: To associate a configured Charge Code to an outgoing Tel-to-IP call, use the Outbound IP Routing Table. Version 6.6 Mediant 2000...

  • Page 660: Trunk Groups And Routing Parameters

    Mediant 2000 45.11.10 Trunk Groups and Routing Parameters The routing parameters are described in the table below. Routing Parameters Parameter Description Trunk Group Table Web: Trunk Group Table This table parameter configures and activates the device's Trunk EMS: SIP Endpoints >...
  • Page 661 Name is used as the Tel Display Name. If no Display Name is received from IP, the Tel Display Name remains empty.  [1] Yes = If an IP Display Name is received, it is used as the Tel Version 6.6 Mediant 2000...
  • Page 662 Mediant 2000 Parameter Description Source Number and also as the Tel Display Name, and Presentation is set to Allowed (0). If no Display Name is received from IP, the IP Source Number is used as the Tel Source Number and Presentation is set to Restricted (1).
  • Page 663 Note: When no Proxy is used, this parameter must be disabled and filtering is according to the Outbound IP Routing Table. Determines the Dial Plan index in the external Dial Plan file (.dat) in Version 6.6 Mediant 2000...
  • Page 664 Mediant 2000 Parameter Description [IP2TelTaggingDestDialPl which string labels ("tags") are defined for tagging incoming IP-to-Tel anIndex] calls. The special “tag” is added as a prefix to the called party number, and then the Inbound IP Routing Table uses this “tag”...
  • Page 665 Defines the maximum time interval (in seconds) that the device waits for CNG detection before re-routing calls identified as fax calls to fax destinations (terminating fax machine). The valid value range is 1-10. The default is 5. Version 6.6 Mediant 2000...

  • Page 666: Ip Connectivity Parameters

    Mediant 2000 45.11.11 IP Connectivity Parameters The IP connectivity parameters are described in the table below. IP Connectivity Parameters Parameter Description Web: Enable Alt Routing Enables the Alternative Routing feature for Tel-to-IP calls. Tel to IP  [0] Disable = (Default) Disables the Alternative Routing feature.

  • Page 667: Alternative Routing Parameters

    FORMAT AltRouteCauseTel2IP_Index = AltRouteCauseTel2IP_ReleaseCause; [\AltRouteCauseTel2IP] For example: AltRouteCauseTel2IP 0 = 486; (Busy Here) AltRouteCauseTel2IP 1 = 480; (Temporarily Unavailable) AltRouteCauseTel2IP 2 = 408; (No Response) Note: For a detailed description of this table, see 'Alternative Routing Version 6.6 Mediant 2000...
  • Page 668 Mediant 2000 Parameter Description Based on SIP Responses' on page 323. Reasons for Alternative IP-to-Tel Routing Table Web: Reasons for This table parameter configures call failure reason values received Alternative IP-to-Tel from the PSTN side (in Q.931 presentation). If a call is released as a...

  • Page 669: Number Manipulation Parameters

    Q.931 Setup message is set to "17" instead of "12345". Note: When enabled, this feature is applied after routing and manipulation on the source number (i.e., just before sending to the Tel side). Version 6.6 Mediant 2000...
  • Page 670 Mediant 2000 Parameter Description Web: Tel2IP Default Determines the default redirect reason for Tel-to-IP calls when no Redirect Reason redirect reason (or “unknown”) exists in the received Q931 ISDN Setup [Tel2IPDefaultRedirectRea message. The device includes this default redirect reason in the SIP son] History-Info header of the outgoing INVITE.
  • Page 671 The device first copies the original called number to the SIP Diversion header, and then performs Tel- to-IP destination phone number manipulation. Therefore, this allows you to have different numbers for the called (i.e., SIP To header) and Version 6.6 Mediant 2000...
  • Page 672 Mediant 2000 Parameter Description redirect (i.e., SIP Diversion header) numbers. Notes:  If the incoming ISDN-to-IP call includes a Redirect Number, this number is overridden by the new called number if this parameter is set to [1] or [2]. ...
  • Page 673 Trunk Group, the prefix "21" is removed from the original number, and therefore, only "100" remains. Notes:  This parameter is applicable only if number manipulation is performed after call routing for IP-to-Tel calls (i.e., RouteModeIP2Tel parameter is set to 0). Version 6.6 Mediant 2000...
  • Page 674 Mediant 2000 Parameter Description  Similar operation (of removing the prefix) is also achieved by using the usual number manipulation rules.  [0] No = (Default) Don't change numbers. Web/EMS: Swap Redirect and Called Numbers  [1] Yes = Incoming ISDN call that includes a redirect number...
  • Page 675 Source/Destination Number Manipulation' on page 287. EMS: Perform Additional Enables additional destination number manipulation for IP-to-Tel calls. IP2TEL Destination The additional manipulation is done on the initially manipulated Manipulation destination number, and this additional rule is also configured in the Version 6.6 Mediant 2000...
  • Page 676 Mediant 2000 Parameter Description [PerformAdditionalIP2TEL manipulation table (NumberMapIP2Tel parameter). This enables you to DestinationManipulation] configure only a few manipulation rules for complex number manipulation requirements (that generally require many rules).  [0] = Disable (default)  [1] = Enable Destination Phone Number Manipulation for Tel-to-IP Calls Table...
  • Page 677 RedirectNumberMapIp2Tel_Suffix2Add, RedirectNumberMapIp2Tel_IsPresentationRestricted; [\RedirectNumberMapIp2Tel] For example: RedirectNumberMapIp2Tel 1 = *, 88, *, , , 1, 1, 2, 0, 255, 9, , 255; Note: For a description of this table, see Configuring Redirect Number Manipulation on page 296. Version 6.6 Mediant 2000...
  • Page 678 Mediant 2000 Parameter Description Redirect Number Tel-to-IP Table Web: Redirect Number Tel - This table parameter manipulates the Redirect Number for Tel-to-IP > IP calls. The format of this parameter is as follows: EMS: Redirect Number Map [RedirectNumberMapTel2Ip] Tel to IP...

  • Page 679: Least Cost Routing Parameters

    Cost Groups. EMS: Time Band [CostGroupTimebands] Provisioning > Time Band FORMAT CostGroupTimebands_TimebandIndex = [CostGroupTimebands] CostGroupTimebands_StartTime, CostGroupTimebands_EndTime, CostGroupTimebands_ConnectionCost, CostGroupTimebands_MinuteCost; [\CostGroupTimebands] Note: For a detailed description of this table, see 'Configuring Time Bands for Cost Groups' on page 197. Version 6.6 Mediant 2000...

  • Page 680: Ldap Parameters

    Mediant 2000 45.13 LDAP Parameters The Lightweight Directory Access Protocol (LDAP) parameters are described in the table below. For more information on routing based on LDAP, see 'Routing Based on LDAP Active Directory Queries' on page 183. LDAP Parameters Parameter...
  • Page 681 Defines the name of the attribute used as a query search key for the destination number in the AD. This is used instead of the "PBX" [MSLDAPPrimaryKey] attribute name (configured by the MSLDAPPBXNumAttributeName parameter). The default is not configured. Version 6.6 Mediant 2000...

  • Page 682: Standalone Survivability Parameters

    Mediant 2000 Parameter Description Defines the name of the attribute used as the second query search [MSLDAPSecondaryKey] key for the destination number in the AD, if the primary search key or PBX search is not found. LDAP Cache Service Enables the LDAP cache service.
  • Page 683 Registered Users EMS: Redundant Proxy database. Each time a new SIP request arrives, the SAS application checks whether the user is listed in the registration database. If the Version 6.6 Mediant 2000...
  • Page 684 Mediant 2000 Parameter Description [RedundantSASProxySe user is located in the database, the request is sent to the user. If the user is not found, the request is forwarded to the next redundant SAS defined in the Redundant SAS Proxy Set. If that SAS Proxy IP appears in the Via header of the request, it is not forwarded (thereby, preventing loops in the request's course).
  • Page 685 IP to IP Inbound Manipulation table. onMode]  [0] None (default)  [1] Emergency Only Notes:  Inbound manipulation applies only to INVITE requests.  For more information on SAS inbound manipulation, see 'Manipulating Destination Number of Incoming INVITE' on page Version 6.6 Mediant 2000...
  • Page 686 Mediant 2000 Parameter Description 374. SAS Registration Manipulation Table Web: SAS Registration This table parameter configures the SAS Registration Manipulation Manipulation table. This table is used by the SAS application to manipulate the SIP EMS: Stand-Alone Request-URI user part of incoming INVITE messages and of incoming...

  • Page 687: Ip Media Parameters

     [15] 15 = 6.00 dB/sec  [16] 16 = 7.00 dB/sec  [17] 17 = 8.00 dB/sec  [18] 18 = 9.00 dB/sec  [19] 19 = 10.00 dB/sec  [20] 20 = 11.00 dB/sec Version 6.6 Mediant 2000...
  • Page 688 Mediant 2000 Parameter Description  [21] 21 = 12.00 dB/sec  [22] 22 = 13.00 dB/sec  [23] 23 = 14.00 dB/sec  [24] 24 = 15.00 dB/sec  [25] 25 = 20.00 dB/sec  [26] 26 = 25.00 dB/sec ...
  • Page 689 X-Detect header extension. The device sends a SIP INFO message containing the field values Type=AMD and SubType=Beep. This feature allows users of certain third-party, Application server to leave a voice message after an answering machine plays the “beep”.  [0] Disabled (default) Version 6.6 Mediant 2000...
  • Page 690 Mediant 2000 Parameter Description  [1] Start After AMD  [2] Start Immediately Web: Answer Machine Defines the AMD beep detection timeout (i.e., the duration that the Detector Beep Detection beep detector functions from when detection is initiated). This is used Timeout for detecting beeps at the end of an answering machine message.
  • Page 691 [PDThreshold] Defines the number of consecutive patterns to trigger the pattern detection event. The valid range is 0 to 31. The default is 5. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 2000...

  • Page 692: Auxiliary And Configuration File Name Parameters

    0 is Trunk 1. 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 693: Automatic Update Parameters

    Defines the name of the cmp file and the path to the server (IP address or FQDN) from where the device can load the cmp file and update itself. The cmp file can be loaded using HTTP/HTTPS, FTP, FTPS, or NFS. For example: http://192.168.0.1/filename Version 6.6 Mediant 2000...
  • Page 694 Mediant 2000 Parameter Description Notes:  For this parameter to take effect, a device reset is required.  When this parameter is configured, the device always loads the cmp file after it is reset.  The cmp file is validated before it's burned to flash. The checksum of the cmp file is also compared to the previously burnt checksum to avoid unnecessary resets.

  • Page 695: Dsp Templates

    Installation and use of voice coders is subject to obtaining the appropriate license and royalty payments. • The number of channels refers to the maximum channel capacity of the device. • For additional DSP templates, contact your AudioCodes representative. DSP Firmware Templates DSP Template Number of Channels Default Setting...
  • Page 696 Mediant 2000 Reader's Notes User's Manual Document #: LTRT-68822...

  • Page 697: Selected Technical Specifications

    User's Manual 47. Selected Technical Specifications Selected Technical Specifications The technical specifications of the Mediant 2000 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.
  • Page 698 Mediant 2000 Function Specification Answer Detector Answer detection Answer Machine Detects whether voice or an answering machine is answering the call. Detector Note: When implementing Answer Machine Detector, channel capacity may be reduced. Call Progress Tone 32 tones: single tone, dual tones or AM tones, programmable Detection and frequency &...
  • Page 699 DC Power Consumption  4 spans: 32.8 W  8 spans: 36.4 W  Operating Temp: 0 to 40°C (32 to 104°F) Environmental (DC)  Short Term Operating Temp (per NEBS): 0 to 55°C (32 to 131°F) Version 6.6 Mediant 2000...
  • Page 700 NEBS Level 3: GR-63-Core, GR-1089-Core, Type 1 & 3. Approved Environmental for DC powered version  Complies with ETS 301019; ETS 300019-1, -2, -3. (T 1.1, T 2.3, T3.2)  Approved for AudioCodes or DC powered versions User's Manual Document #: LTRT-68822...
  • Page 702 User's Manual Ver. 6.6 www.audiocodes.com...

Table of Contents