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

AudioCodes Mediant 3000 User Manual

Enterprise session border controller / voip digital media gateway
Hide thumbs Also See for Mediant 3000:
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
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, User Manual
Enterprise Session Border Controller
VoIP Digital Media Gateway
Mediant™ 3000
User's Manual
Version 6.6

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Mediant 3000 and is the answer not in the manual?

Questions and answers

Related Manuals for AudioCodes Mediant 3000

Summary of Contents for AudioCodes Mediant 3000

  • Page 1 Enterprise Session Border Controller VoIP Digital Media Gateway Mediant™ 3000 User's Manual Version 6.6...

  • Page 3: Table Of Contents

    Getting Started with Initial Connectivity ..............27 Assigning the OAMP IP Address ..............29 Web Interface ......................29 BootP/TFTP Server ....................31 CLI .......................... 32 Assigning an IP Address for Mediant 3000 HA ............34 2.4.1 Web Interface ......................35 2.4.2 EMS ......................... 36 Management Tools ....................41...
  • Page 4 Mediant 3000 Web Login Authentication using Smart Cards ............77 Configuring Web and Telnet Access List ............... 78 Configuring RADIUS Settings ................79 CLI-Based Management ..................81 Enabling CLI using Telnet ..................81 Enabling CLI using SSH and RSA Public Key ............81 Establishing a CLI Session ..................
  • Page 5 12.3.3 Configuring IP Security Associations Table ............152 12.4 Intrusion Detection System .................. 156 12.4.1 Enabling IDS ......................156 12.4.2 Configuring IDS Policies ..................157 12.4.3 Assigning IDS Policies ...................160 12.4.4 Viewing IDS Alarms ....................162 13 Media ........................ 165 13.1 Configuring Voice Settings ................... 165 Version 6.6 Mediant 3000...
  • Page 6 Mediant 3000 13.1.1 Configuring Voice Gain (Volume) Control .............165 13.1.2 Silence Suppression (Compression) ..............166 13.1.3 Echo Cancellation ....................166 13.2 Fax and Modem Capabilities ................168 13.2.1 Fax/Modem Operating Modes ................169 13.2.2 Fax/Modem Transport Modes ................169 13.2.2.1 T.38 Fax Relay Mode ................169 13.2.2.2 G.711 Fax / Modem Transport Mode ............
  • Page 7 21 Digital PSTN ..................... 297 21.1 Configuring Trunk Settings ................... 297 21.2 TDM and Timing ....................300 21.2.1 Configuring TDM Bus Settings ................300 21.2.2 Configuring Digital PCM Settings ................300 21.2.3 Configuring System Timing ...................301 21.2.4 Clock Settings ......................301 Version 6.6 Mediant 3000...
  • Page 8 Mediant 3000 21.2.4.1 Recovering Clock from PSTN Line Interface ........302 21.2.4.2 Configuring BITS Synchronization Mode ..........303 21.2.4.3 Configuring Internal Clock as Clock Source ......... 304 21.3 Configuring Transmission Settings ..............304 21.4 Configuring CAS State Machines ................. 306 21.5 Configuring Digital Gateway Parameters .............
  • Page 9 26.5.2.1 About E9-1-1 Services ................382 26.5.2.2 Microsoft Lync Server 2010 and E9-1-1 ..........383 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 ..........392 26.6 Multilevel Precedence and Preemption ..............393 26.6.1 MLPP Preemption Events in SIP Reason Header ..........396...
  • Page 10 Mediant 3000 28.4.7 Prioritizing Coder List in SDP Offer ...............417 28.4.8 SRTP-RTP and SRTP-SRTP Transcoding ............417 28.4.9 Multiple RTP Media Streams per Call Session .............418 28.4.10 Interworking DTMF Methods .................418 28.5 Fax Negotiation and Transcoding ................ 419 28.6 Limiting SBC Call Duration ................... 419 28.7 SIP Authentication Server for SBC Users ............
  • Page 11 34.2 Configuration Stages .................... 505 34.3 Blade Failure Detection ..................506 35 Network Interfaces for HA ................507 35.1 Mediant 3000 Internal Link ................... 507 35.2 Example of Multiple Interface Configuration ............507 36 Physical Network Separation Mode ............... 509 36.1 Configuring Physical Network Separation ............
  • Page 12 42.4.4 TFTP Configuration using DHCP Option 66 ............559 42.4.5 HTTP-based Automatic Updates ................559 42.4.6 Configuration using FTP or NFS ................560 42.4.7 Configuration using AudioCodes EMS ..............560 42.5 Loading Files Securely (Disabling TFTP) ............. 561 42.6 Remotely Triggering Auto Update using SIP NOTIFY ......... 561...
  • Page 13 48.2.2.3 CDR Fields for Gateway/IP-to-IP Application ........596 48.2.2.4 Release Reasons in CDR ..............600 48.3 Configuring RADIUS Accounting ................. 603 48.4 Event Notification using X-Detect Header ............606 48.5 Querying Device Channel Resources using SIP OPTIONS ........ 608 Version 6.6 Mediant 3000...
  • Page 14 49.1 Syslog Message Format ..................611 49.1.1 Event Representation in Syslog Messages ............612 49.1.2 Unique Device Identification in Syslog Messages ..........614 49.1.3 Identifying AudioCodes Syslog Messages using Facility Levels ......614 49.1.4 Syslog Fields for Automatic Machine Detection ............615 49.1.5 SNMP Alarms in Syslog Messages ...............615 49.2 Configuring Syslog Settings .................
  • Page 15 53.11.9.2 Tone Detection Parameters ..............811 53.11.9.3 Metering Tone Parameters ..............812 53.11.10 Trunk Groups and Routing Parameters ............813 53.11.11 IP Connectivity Parameters ................819 53.11.12 Alternative Routing Parameters ...............820 53.11.13 Number Manipulation Parameters ..............822 53.12 Least Cost Routing Parameters ................831 Version 6.6 Mediant 3000...
  • Page 16 53.18 Automatic Update Parameters ................856 54 DSP Templates ....................859 54.1.1 Mediant 3000 Full Chassis ..................859 54.1.2 Mediant 3000 16 E1 / 21 T1 ..................860 54.1.3 Mediant 3000 with Single T3 .................862 54.1.4 DSP Template Mix Feature for Mediant 3000 ............863 55 Selected Technical Specifications ..............

  • Page 17: Mediant

    Each abbreviation, unless widely used, is spelled out in full when first used. Throughout this manual, unless otherwise specified, the following naming conventions are used:  The term device refers to the Mediant 3000 housing either TP-8410 or TP-6310 blades  The term blade refers to the TP-8410 blade or TP-6310 blade Version 6.6...

  • Page 18: Document #: Ltrt

    This device includes cryptographic software written by Eric Young (eay@cryptsoft.com). 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 19: Overview

    User's Manual 1. Overview Overview The Mediant 3000 (hereafter referred to as device) is a SIP-based Voice-over-IP (VoIP) media gateway, offering an integrated voice media gateway functionality for voice, data, and fax streaming over IP networks. The device addresses mid-density applications deployed in IP networks, by delivering up to 2,016 simultaneous voice channels.

  • Page 20: Functional Block Diagrams

    For more details on the HA system, see HA Overview' on page 20. Functional Block Diagrams The functional block diagrams of the Mediant 3000 with the TP-6310 blade and with the TP-8410 blade are shown in the figures below, respectively:...
  • Page 21 User's Manual 1. Overview Figure 1-2: Mediant 3000/TP-6310 Functional Block Diagram Version 6.6 Mediant 3000...
  • Page 22 Mediant 3000 Figure 1-3: Mediant 3000/TP-8410 Functional Block Diagram User's Manual Document #: LTRT-89729...

  • Page 23: Sip Overview

    Figure 1-4: SIP Call Flow  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 3000/v.6.60.010.006 Supported: 100rel,em Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE, Version 6.6 Mediant 3000...
  • Page 24 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 3000/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 25 F5 ACK - 10.8.201.108 to 10.8.201.10: ACK sip:2000@10.8.201.161;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacZYpJWxZ 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 3000/v.6.60.010.006 CSeq: 18153 ACK Supported: 100rel,em Content-Length: 0 Note: Phone 6000 goes on-hook and device 10.8.201.108 sends a BYE to device 10.8.201.161 and a voice path is established.
  • Page 26 Mediant 3000 Reader's Note User's Manual Document #: LTRT-89729...

  • Page 27: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 29: Assigning The Oamp Ip Address

    This section describes how to change the default OAMP IP address for Mediant 3000 Simplex mode. For Mediant 3000 High Availability (HA) mode, see Assigning an IP Address for Mediant 3000 HA on page 34. Web Interface The procedure below describes how to assign an OAMP IP address using the Web interface.
  • Page 30 Mediant 3000 Figure 2-1: Cabling Ethernet Port Change the IP address and subnet mask of your computer to correspond with the default IP address and subnet mask of the device. 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;...

  • Page 31: 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 32: Cli

    Mediant 3000  To assign an IP address using BootP/TFTP: Start the AcBootP utility. Select the Preferences tab, and then set the 'Timeout' field to "50". Select the Client Configuration tab, and then click the Add New Client button. Figure 2-4: BootP Client Configuration Screen Configure the following fields: •...
  • Page 33 Connect the RS-232 port of the device to the serial communication port on your computer. For more information, refer to the Hardware Installation Manual. Figure 2-5: Cabling for Serial Interface – Mediant 3000 with TP-6310 Figure 2-6: Cabling for Serial Interface – Mediant 3000 with TP-8410...

  • Page 34: Assigning An Ip Address For Mediant 3000 Ha

    AudioCodes EMS management tool - see 'EMS' on page The Mediant 3000 HA houses two TP-6310 blades or two TP-8410 blades, where one is active while the other is redundant (or in standby). Each of these two blades has a different private IP address, which is used for initial configuration, maintenance, or fallback in case of a major device problem which prevents it from operating in HA mode.

  • Page 35: Web Interface

    2.4.1 Web Interface The procedure below describes how to initially assign a global (public) IP address to Mediant 3000 HA using AudioCodes AcBootP utility and the Web interface.  To initially assign a global IP address to Mediant 3000 HA:...

  • Page 36: Ems

    IP address. This allows the blades to send reports to a Syslog server in case of major device failure. 2.4.2 The procedure below describes how to initially assign a global IP address to Mediant 3000 HA using AudioCodes EMS management tool. ...
  • Page 37 IP addresses (after approximately 15 seconds). Using AudioCodes EMS, configure the active blade's new local IP address: Add a region for your Mediant 3000 (refer to the EMS User's Guide). Figure 2-8: Adding a Region Verify that Mediant 3000 is up and running, by pinging its IP address.
  • Page 38 In the MG Tree, under the Region that you added, right-click the device, and then from the shortcut menu, choose Remove MG to delete it from the EMS. Add once again the Mediant 3000 under your Region to the EMS with the new global IP address that you defined above.
  • Page 39 IP address. This allows the blades to send reports to a Syslog server in case of major device failure. Version 6.6 Mediant 3000...
  • Page 40 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 41: Management Tools

    Part II Management Tools...

  • Page 43: 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 44 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 45: Web-Based Management

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

  • Page 46: Accessing The Web Interface

    Mediant 3000 4.1.2 Accessing the Web Interface The procedure below describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see 'Computer Requirements' on page 45). In the Web browser, specify the IP address of the device (e.g., http://10.1.10.10); the...

  • Page 47: Areas Of The Gui

    Figure 4-2: Main Areas of the Web Interface GUI 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 48.

  • Page 48: Toolbar Description

    Mediant 3000 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 520). Note: This icon is grayed out when not applicable to the currently opened page.

  • Page 49: Navigation Tree

    Page item: last level (lowest level in a menu) - contained within a menu or submenu Figure 4-4: Navigating in Hierarchical Menu Tree (Example) Note: The figure above is used only as an example. The displayed menus depend on supported features based on the Software License Key installed on your device. Version 6.6 Mediant 3000...

  • Page 50: Displaying Navigation Tree In Basic And Full View

    Mediant 3000 4.1.5.1 Displaying Navigation Tree in Basic and Full View You can view an expanded or reduced display of the Navigation tree. This affects the number of displayed menus and submenus in the tree. The expanded (Full) view displays all the menus pertaining to the selected configuration tab;...

  • Page 51: 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 69). If a page is read-only, "Read-Only Mode" is displayed at the bottom of the page. Version 6.6 Mediant 3000...

  • Page 52: Viewing Parameters

    Mediant 3000 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 53: 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 517. Version 6.6 Mediant 3000...

  • Page 54: Working With Tables

    Mediant 3000 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 Configuration' on page 520).
  • Page 55 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 3000...
  • Page 56 Mediant 3000 Item # Button Show/Hide Toggles between displaying and hiding the full configuration of a 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 57: 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 3000...

  • Page 58: Working With Scenarios

    Mediant 3000 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 59 '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 3000...

  • Page 60: Accessing A Scenario

    Mediant 3000 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...

  • Page 61: 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 3000...

  • Page 62: Saving A Scenario To A Pc

    Mediant 3000 • 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 63: Loading A Scenario To The Device

    ScenarioFileName (see Web and Telnet Parameters on page 653). 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 64: Quitting Scenario Mode

    Mediant 3000 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 63). • Loading an ini file with the ScenarioFileName parameter set to no value (i.e., ScenarioFileName = "").

  • Page 65: 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 3000...

  • Page 66: Getting Help

    Mediant 3000 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 67: Viewing The Home Page

    "UNLOCKED": device is not locked • "SHUTTING DOWN": device is currently shutting down To perform these operations, see 'Basic Maintenance' on page 517.  High Availability: Status of the device's HA mode (see 'Viewing HA Status on Home Version 6.6 Mediant 3000...
  • Page 68 Mediant 3000 Page' on page 513)  Active Board Slot Number: Slot number with the active blade if the device is in HA mode; otherwise, this field is unavailable To view real-time status of the device's hardware components (chassis slots with blades, fans, power supplies, and PEMs), click any area (except the alarms, Ethernet, and PSTN icons) on the graphical display of the chassis.

  • Page 69: Configuring Web User Accounts

    Read / write privileges for all pages. It can create all user Administrator types and is the only one that can create the first Master user. Note: There must be at least one Security Administrator. Administrator Read / write privileges for all pages except security- Version 6.6 Mediant 3000...
  • Page 70 Mediant 3000 User Access Numeric Privileges Level Representation* related pages, which are read-only. Monitor No access to security-related and file-loading pages; read-only access to other pages. No Access No access to any page. Note: This access level is not applicable when using advanced Web user account configuration in the Web Users table.

  • Page 71: Basic User Accounts Configuration

    When you log in to the Web interface, the username and password string values are case-sensitive, according to your configuration. • Up to two users can be logged in to the Web interface at the same time, and they can be of the same user. Version 6.6 Mediant 3000...
  • Page 72 Mediant 3000  To configure the two pre-configured Web user accounts: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). If you are logged in as Security Administrator, both Web user accounts are displayed (as shown below). If you are logged in with the second user account, only the details of this user account are displayed.

  • Page 73: Advanced User Accounts Configuration

    Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). Under the Web Users Table group, click the Create Table button. • Subsequent access: Configuration tab > System menu > Web User Accounts. Version 6.6 Mediant 3000...
  • Page 74 Mediant 3000 The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"): Figure 4-26: Web Users Table Page Click the Add button; the following dialog box is displayed: Figure 4-27: Web Users Table - Add Record Dialog Box Add a user as required.
  • Page 75 The default is according to the settings of the 'Deny Authentication Timer' parameter (see 'Configuring Web Security Settings' on page 77). Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Version 6.6 Mediant 3000...

  • Page 76: Displaying Login Information Upon Login

    Mediant 3000 Parameter Description Web: User Level Defines the user's access level.  Monitor = (Default) Read-only user. This user can only view Web pages and access to security-related pages is denied.  Admin = Read/write privileges for all pages, except security-related pages including the Web Users table where this user has only read-only privileges.

  • Page 77: Configuring Web Security Settings

    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 78: Configuring Web And Telnet Access List

    Mediant 3000 Configuring Web and Telnet Access List The Web & Telnet Access List page is used to define IP addresses (up to ten) that are permitted to access the device's Web, Telnet, and SSH interfaces. Access from an undefined IP address is denied. If no IP addresses are defined, this security feature is inactive and the device can be accessed from any IP address.

  • Page 79: Configuring Radius Settings

    Open the RADIUS Settings page (Configuration tab > System menu > Management submenu > RADIUS Settings). Figure 4-32: RADIUS Parameters Page Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 520. Version 6.6 Mediant 3000...
  • Page 80 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 81: 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 Version 6.6 Mediant 3000...
  • Page 82 Mediant 3000 PuTTY, which downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty/. 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 83: 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 3000...

  • Page 84: Cli Commands

    Mediant 3000 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 85 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 3000...
  • Page 86 Mediant 3000 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 87: 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 3000...

  • Page 88: Management Commands

    Mediant 3000 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 89: 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 Version 6.6 Mediant 3000...

  • Page 90: Ldap Commands

    Mediant 3000 Command Short Arguments Description Format options for AlarmSendCode include the 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>...

  • Page 91: 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 3000...

  • Page 92: Configuring Snmp Trap Destinations

    Mediant 3000 To save the changes to flash memory, see 'Saving Configuration' on page 520. 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 93 (default) = SNMPv2 user community string  SNMPv3 user configured in 'Configuring SNMP V3 Users' on page Trap Enable Activates the sending of traps to the SNMP Manager. [SNMPManagerTrapSen  [0] Disable dingEnable_x]  [1] Enable (Default) Version 6.6 Mediant 3000...

  • Page 94: Configuring Snmp Trusted Managers

    Mediant 3000 Configuring SNMP Trusted Managers The SNMP Trusted Managers page allows you to configure up to five SNMP Trusted Managers, based on IP addresses. By default, the SNMP agent accepts SNMP Get and Set requests from any IP address, as long as the correct community string is used in the request.

  • Page 95: Configuring Snmp V3 Users

    The valid range is 0 to 9. User Name Name of the SNMP v3 user. This name must be unique. [SNMPUsers_Username] Authentication Protocol Authentication protocol of the SNMP v3 user. [SNMPUsers_AuthProtoc  [0] None (default)  [1] MD5  [2] SHA-1 Version 6.6 Mediant 3000...
  • Page 96 Mediant 3000 Parameter Description Privacy Protocol Privacy protocol of the SNMP v3 user. [SNMPUsers_PrivProtocol  [0] None (default)  [1] DES  [2] 3DES  [3] AES-128  [4] AES-192  [5] AES-256 Authentication Key Authentication key. Keys can be entered in the form of a text [SNMPUsers_AuthKey] password or long hex string.

  • Page 97: 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 E-SBC and gateways within VoP networks, covering all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of AudioCodes' families of E-SBC and gateways.
  • Page 98 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 99: 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 3000...
  • Page 100 Mediant 3000 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 101: 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 102: 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 103: General System Settings

    Part III General System Settings...

  • Page 105: 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 3000...

  • Page 106: Loading A Private Key

    Mediant 3000 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 107 (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 3000...

  • Page 108: Mutual Tls Authentication

    Mediant 3000 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 109: Self-Signed Certificates

    (in bits), and then click Generate self-signed; after a few seconds, a message appears displaying the new subject name. Save the configuration with a device reset (see 'Saving Configuration' on page 520) for the new certificate to take effect. Version 6.6 Mediant 3000...

  • Page 110: Tls Server Certificate Expiry Check

    Mediant 3000 TLS Server Certificate Expiry Check The device can periodically check the validation date of the installed TLS server certificate. This periodic check interval is user-defined. In addition, within a user-defined number of days before the installed TLS server certificate expires, the device can be configured to send the SNMP trap, acCertificateExpiryNotifiaction to notify of the impending certificate expiration.

  • Page 111: Date And Time

    If required, the clock update is performed by the client as the final step of the update process. The update is performed in such a way as to be transparent to the end users. For instance, the response of the server may indicate that the clock is running too fast on the Version 6.6 Mediant 3000...
  • Page 112 Mediant 3000 client. 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 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 113: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 115: Network

    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 Ethernet switchover occurs only once during the start-up procedure (at the beginning). If Version 6.6 Mediant 3000...

  • Page 116: Configuring Ip Network Interfaces

    Mediant 3000 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. The device switches over from one Ethernet port to the other each time an Ethernet link carrier-loss is detected on the active Ethernet port, and if the Ethernet link of the other port is operational.
  • Page 117 To configure firewall rules (access list) for allowing or blocking packets received from specific IP network interfaces, see 'Configuring Firewall Settings' on page 145. • The Multiple Interface table can also be configured using the table ini file parameter, InterfaceTable (see 'Networking Parameters' on page 643). Version 6.6 Mediant 3000...
  • Page 118 Mediant 3000  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 119 (the lower 64 bits) is derived from the device's MAC address.  [4] IPv6 Manual = IPv6 manual IP address (128 bits) assignment.  [10] IPv4 Manual = IPv4 manual IP address (32 bits) assignment. Note: For valid configuration, see Multiple Interface Table Configuration Version 6.6 Mediant 3000...
  • Page 120 Mediant 3000 Parameter Description Rules on page 122. Web/EMS: IP Address Defines the IPv4/IPv6 IP address in dotted-decimal notation. [InterfaceTable_IPAd Note: For valid configuration, see Multiple Interface Table Configuration dress] Rules on page 122. Web/EMS: Prefix Defines the prefix length of the related IP address. This is a Classless...
  • Page 121 VLAN ID 1, set this parameter to a value other than any VLAN ID in the table. Network Physical Enables physical separation (dedicated ports) for each network type Separation (Media, Control, and OAMP). [EnableNetworkPhysicalS  [0] Disable (default). eparation]  [1] Enable. Notes: Version 6.6 Mediant 3000...

  • Page 122: Assigning Ntp Services To Application Types

    Mediant 3000 Parameter Description  This parameter is applicable only to Mediant 3000 with TP-8410.  For this parameter to take effect, a device reset is required.  When the parameter is enabled, VLANs are not supported (i.e., VlANMode is set to 1).

  • Page 123: Troubleshooting The Multiple Interface Table

    Trying to access the device with VLAN tags while booting from BootP/DHCP.  Trying to access the device with untagged traffic when VLANs are on and Native VLAN is not configured properly.  The IP Routing table is not configured properly. Version 6.6 Mediant 3000...

  • Page 124: Networking Configuration Examples

    Mediant 3000 11.3.4 Networking Configuration Examples This section provides configuration examples of networking interfaces. 11.3.4.1 One VoIP Interface for All Applications This example describes the configuration of a single VoIP interface for all applications: Multiple Interface table: Configured with a single interface for OAMP, Media and...

  • Page 125: Voip Interfaces For Combined Application Types

    Management interface (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 3000...

  • Page 126: Voip Interfaces With Multiple Default Gateways

    Mediant 3000 Example of IP Routing Table Destination IP Gateway IP Interface Prefix Length Metric Address Address Name 176.85.49.0 192.168.0.10 The NTP application is configured (using the ini file) to serve as OAMP applications: EnableNTPasOAM = 1 11.3.4.4 VoIP Interfaces with Multiple Default Gateways Below is a configuration example using default gateways per IP network interface.
  • Page 127 The CIDR-style representation uses a suffix indicating the number of bits that are set in the dotted- decimal format. For example, 16 is synonymous with subnet 255.255.0.0. Version 6.6 Mediant 3000...

  • Page 128: Interface Column

    Mediant 3000 Parameter Description The address of the host/network you want to reach is determined by an AND operation that is applied to the fields 'Destination IP Address' and 'Prefix Length'. For example, to reach the network 10.8.x.x, enter 10.8.0.0 in the 'Destination IP Address' field and 16 in the 'Prefix Length'. As a result of the AND operation, the value of the last two octets in the 'Destination IP Address' field is ignored.

  • Page 129: Routing Table Configuration Summary And Guidelines

    Syslog server reporting the problem. Common routing rule configuration errors may include the following:  The IP address specified in the 'Gateway IP Address' field is unreachable from the Version 6.6 Mediant 3000...

  • Page 130: Configuring Quality Of Service

    Mediant 3000 interface specified in the 'Interface Name' field.  The same destination is configured in two different routing rules.  More than 30 routing rules have been configured. Note: If an IP routing rule is required to access OAMP applications (for remote management, for example) and the route is not configured correctly, the route is not added and the device is not accessible remotely.
  • Page 131 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 520). Version 6.6 Mediant 3000...

  • Page 132: Disabling Icmp Redirect Messages

    Mediant 3000 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 645).
  • Page 133 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 3000...

  • Page 134: Configuring The Internal Srv Table

    Mediant 3000 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 135: Configuring Nfs Settings

    Note that an NFS file server can share multiple file systems. There must be a separate row for each remote file system shared by the NFS file server that needs to be accessed by the device. Version 6.6 Mediant 3000...
  • Page 136 Mediant 3000  To add remote NFS file systems: 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 Configure the NFS parameters according to the table below.

  • Page 137: Network Address Translation Support

    Configuring NAT Translation per IP Interface on page 140. If NAT is not configured by any of the above-mentioned methods, the device sends the packet according to its IP address configured in the Multiple Interface table. Version 6.6 Mediant 3000...

  • Page 138: Configuring Stun

    Mediant 3000 Note: The priority list above is applicable only to the Gateway/IP-to-IP application. The 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 11.9.1.1 Configuring STUN...

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

    Figure 11-12: Configuring Static NAT IP Address in SIP General Parameters Page In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation. Click Submit. Save the setting to the device's flash memory with a device reset (see 'Saving Configuration' on page 520). Version 6.6 Mediant 3000...

  • Page 140: Configuring Nat Translation Per Ip Interface

    Mediant 3000 11.9.1.3 Configuring NAT Translation per IP Interface The NAT Translation table defines network address translation (NAT) rules for translating source IP addresses per VoIP interface (SIP control and RTP media traffic) into NAT IP addresses (global or public), when the device is located behind NAT. This allows, for example, the separation of VoIP traffic between different ITSP’s, and topology hiding of...

  • Page 141: Remote Ua Behind Nat

    RTP No-Op packets according to the avt-rtp-noop draft - see 'No-Op Packets' on page The figure below illustrates a typical network architecture where the remote UA is located behind NAT: Figure 11-14: Remote UA behind NAT Version 6.6 Mediant 3000...

  • Page 142: First Incoming Packet Mechanism

    Mediant 3000 11.9.2.1 First Incoming Packet Mechanism If the remote device resides behind a NAT device, it’s possible that the device can activate the RTP/RTCP/T.38 streams to an invalid IP address / UDP port. To avoid such cases, the device automatically compares the source address of the first received incoming RTP/RTCP/T.38 stream with the IP address and UDP port of the remote device when the...

  • Page 143: Robust Receipt Of Media Streams

    11. Network 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 144 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 145: 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 669). Version 6.6 Mediant 3000...
  • Page 146 Mediant 3000  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 147 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 3000...
  • Page 148 Mediant 3000 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 149: Configuring General Security Settings

    Providing security services at the IP layer, IPSec and IKE are transparent to IP applications. IPSec and IKE are used together to provide security for control and management (e.g., SNMP and Web) protocols, but not for media (i.e., RTP, RTCP and T.38). Version 6.6 Mediant 3000...

  • Page 150: Enabling Ipsec

    Mediant 3000 IKE is used to obtain the Security Associations (SA) between peers (the device and the application it’s trying to contact). The SA contains the encryption keys and profile used by IPSec to encrypt the IP stream. IKE negotiation comprises the following two phases: ...

  • Page 151: 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 3000...

  • Page 152: Configuring Ip Security Associations Table

    Mediant 3000 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 153 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 3000...
  • Page 154 Mediant 3000 Parameter Name Description certificates, see 'Replacing the Device's Certificate' on page 105. 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 155 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 3000...

  • Page 156: Intrusion Detection System

    Mediant 3000 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 157: Configuring Ids Policies

    Intrusion Detection and Prevention > Policy Table). Figure 12-7: IDS Policy Table with Default Rules Add a Policy name: Click Add. Figure 12-8: IDS Policy Table - Add Record Configure the parameters as described in the following table, and then click Submit. Version 6.6 Mediant 3000...
  • Page 158 Mediant 3000 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 159 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 3000...

  • Page 160: Assigning Ids Policies

    Mediant 3000 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 161 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 157. [IDSMatch_Policy] Version 6.6 Mediant 3000...

  • Page 162: Viewing Ids Alarms

    Mediant 3000 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 163 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 3000...
  • Page 164 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 165: Media

    The device allows you to configure the level of the received (input gain) Tel-to-IP signal and the level of the transmitted (output gain) IP-to-Tel signal. The gain can be set between -32 and 31 decibels (dB). The procedure below describes how to configure gain control using the Web interface: Version 6.6 Mediant 3000...

  • Page 166: Silence Suppression (Compression)

    Mediant 3000  To configure gain control using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media submenu > Voice Settings). Figure 13-2: Voice Volume Parameters in Voice Settings Page Configure the following parameters: •...
  • Page 167 • ECHybridLoss - defines the four-wire to two-wire worst-case Hybrid loss • ECNLPMode - defines the echo cancellation Non-Linear Processing (NLP) mode • EchoCancellerAggressiveNLP - enables Aggressive NLP at the first 0.5 second of the call Version 6.6 Mediant 3000...

  • Page 168: Fax And Modem Capabilities

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

  • Page 169: Fax/Modem Operating Modes

    You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). This parameter does not affect the actual transmission rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). Version 6.6 Mediant 3000...
  • Page 170 Mediant 3000 When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders.

  • Page 171: Fax / Modem Transport Mode

    When the device initiates a fax session using G.711, a ‘gpmd’ attribute is added to the SDP according to the following format:  For G.711A-law: a=gpmd:0 vbd=yes;ecan=on  For G.711 µ-law: a=gpmd:8 vbd=yes;ecan=on In this mode, the 'Fax Transport Mode' (FaxTransportMode) parameter is ignored and automatically set to Disable (transparent mode). Version 6.6 Mediant 3000...

  • Page 172: Fax/Modem Bypass Mode

    Mediant 3000  To configure fax fallback mode:  In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to Fax Fallback (IsFaxUsed = 3). 13.2.2.4 Fax/Modem Bypass Mode...

  • Page 173: 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 174: Fax / Modem Transparent With Events Mode

    Mediant 3000 Set the ini file parameter, BellModemTransportType to 2 (Bypass). Set the ini file parameter, NSEMode parameter to 1 (enables NSE). Set the ini file parameter, NSEPayloadType parameter to 100. 13.2.2.6 Fax / Modem Transparent with Events Mode In this mode, fax and modem signals are transferred using the current voice coder with the following automatic adaptations: ...

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

    T38 Version 0 relay mode, i.e., fallback to T.38 (see 'Relay Mode for T.30 and V.34 Faxes' on page 176) To configure whether to pass V.34 over T38 fax relay, or use Bypass over the High Bit Rate coder (e.g. PCM A-Law), use the 'V.34 Fax Transport Type' parameter (V34FaxTransportType). Version 6.6 Mediant 3000...

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

    Mediant 3000 You can use the 'SIP T38 Version' parameter (SIPT38Version) in the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters) to configure one of the following:  Pass V.34 over T.38 fax relay using bit rates of up to 33,600 bps ('SIP T38 Version' is set to Version 3).

  • Page 177: Fax Relay For Sg3 Fax Machines

    Set the 'SIP T38 Version' parameter to Version 3 (SIPT38Version = 3). Set the 'Fax Relay Max Rate' parameter (RelayMaxRate) to 33,600bps (default). Set the 'CNG Detector Mode' parameter (CNGDetectorMode) to Disable (default). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Version 6.6 Mediant 3000...
  • Page 178 Mediant 3000 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). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0).

  • Page 179: Modem Relay

    V.150.1 Software License Key. • The V.150.1 feature has been tested with certain IP phones. For more details, please contact your AudioCodes sales representative. • The V.150.1 SSE Tx payload type is according to the offered SDP of the remote side.

  • Page 180: Simultaneous Negotiation Of Fax (T.38) And Modem (V.150.1) Relay

    Mediant 3000 Set the 'Profile Number' parameter (V1501AllocationProfile) to the amount of DSP channels allocated for regular voice and V.150.1 Modem Relay capability. Once the V.150.1 session has been negotiated and activated by SIP, a Modem Relay DSP channel is allocated alongside the existing allocated voice DSP channel.

  • Page 181: Fax Transmission Behind Nat

    T.38 packets to the terminating fax machine upon receipt of a re-INVITE with T.38 only in the SDP, or T.38 and audio media in the SDP. This feature is configured using the T38FaxSessionImmediateStart parameter. The No-Op packets are enabled using the NoOpEnable and NoOpInterval parameters. Version 6.6 Mediant 3000...

  • Page 182: Configuring Rtp/Rtcp Settings

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

  • Page 183: Comfort Noise Generation

    > RTP/RTCP Settings). The relevant parameters are listed under the 'General Settings' group, as shown below: Figure 13-7: Comfort Noise Parameter in RTP/RTCP Settings Page Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Click Submit to apply your changes. Version 6.6 Mediant 3000...

  • Page 184: Dual-Tone Multi-Frequency Signaling

    Mediant 3000 13.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 13.3.3.1 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint. These methods and their configuration are configured in the DTMF &...

  • Page 185: Configuring Rfc 2833 Payload

    'RFC 2833 RX Payload Type' (RFC2833RxPayloadType) - defines the Rx RFC 2833 DTMF relay dynamic payload type. • 'RFC 2198 Payload Type' (RFC2198PayloadType) - defines the RTP redundancy packet payload type according to RFC 2198. Click Submit to apply your settings. Version 6.6 Mediant 3000...

  • Page 186: Configuring Rtp Base Udp Port

    The maximum (when all channels are required) UDP port range is calculated as follows:  Mediant 3000/TP-6310: BaseUDPport to (BaseUDPport + 4031*10) - for example, if the BaseUDPPort is set to 6,000, then the UDP port range is 6,000 to 46,310 ...

  • Page 187: Configuring Ip Media Settings

    The beep detection timeout and beep detection sensitivity are configurable using the AMDBeepDetectionTimeout and AMDBeepDetectionSensitivity parameters, respectively. To enable the AMD beep detection, the X-Detect header in the received INVITE message must include “Request=AMD”, and the AMDBeepDetectionMode Version 6.6 Mediant 3000...
  • Page 188 Mediant 3000 parameter must be set to 1 or 2. If set to 1, the beep is detected only after Answering Machine detection. If set to 2, the beep is detected even if the Answering Machine was not detected. ...
  • Page 189 The device's AMD feature is based on voice detection for North American 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 190 Mediant 3000 The SIP call flows below show an example of implementing the device's AMD feature. This scenario example allows a third-party Application server to play a recorded voice message to an answering machine. 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...

  • Page 191: Automatic Gain Control (Agc)

    > IPMedia Settings). The AGC parameters are shown in the figure below: Figure 13-11: AGC Parameters in IPMedia Settings Page Configure the following parameters: • 'Enable AGC' (EnableAGC) - Enables the AGC mechanism. • 'AGC Slope' (AGCGainSlope) - Determines the AGC convergence rate. Version 6.6 Mediant 3000...

  • Page 192: Configuring Various Codec Attributes

    Mediant 3000 • '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. Note: Below are additional AGC parameters: •...

  • Page 193: Configuring Dsp Templates

    If no entries are defined, the device uses the default DSP template (i.e., Template 0). • A single DSP Template can also be configured using the ini file parameter, DSPVersionTemplateNumber. • The DSP Templates table can also be configured using the table ini file parameter, DSPTemplates. Version 6.6 Mediant 3000...

  • Page 194: Configuring Media Realms

    Mediant 3000  To select a DSP Template(s): To use a single DSP Template: Open the General Settings page (Configuration tab > VoIP menu > Media > General Media Settings). Figure 13-13: Defining Single DSP Template in General Settings Page In the 'DSP Version Template Number' field, enter the required DSP Template number.
  • Page 195 Once you have configured a Media Realm, you can configure it with the following:  Quality of Experience parameters for reporting to AudioCodes SEM server used for monitoring the quality of calls (see Configuring Quality of Experience Parameters per Media Realm on page 197) ...
  • Page 196  The available UDP port range is calculated using the BaseUDPport parameter:  Mediant 3000/TP-6310: BaseUDPport to BaseUDPport + 4031*10. For example, if BaseUDPPort is 6000 (default), then the available port range is 6000-46310  Mediant 3000/TP-8410: BaseUDPport to BaseUDPport + 4031*10 ...

  • Page 197: Configuring Quality Of Experience Per Media Realm

    The QoE feature is available only if the device is installed with the relevant Software License Key. • To configure the address of the AudioCodes Session Experience Manager (SEM) server to where the device reports the QoE, see 'Configuring SEM Server for Media Quality of Experience' on page 202.
  • Page 198 Mediant 3000 then click the Quality Of Experience link; the Quality Of Experience page appears. Click the Add button; the following dialog box appears: Figure 13-16: Quality of Experience Page - Add Record Dialog Box The figure above shows value thresholds for the MOS parameter, which are assigned using pre-configured values of the Low Sensitivity profile.
  • Page 199 Note: This field is applicable only if the 'Yellow Red Operation' field is set to Activate 2198. Version 6.6 Mediant 3000...

  • Page 200: Configuring Bandwidth Management Per Media Realm

    Mediant 3000 13.7.2 Configuring Bandwidth Management per Media Realm Bandwidth management enables you to configure bandwidth utilization thresholds per Media Realm which when exceeded, the device can do one of the following:  Generate an appropriate SNMP alarm, which is cleared when the bandwidth utilization returns to normal.
  • Page 201 Defines the bandwidth threshold in bytes per second (Bps). [BWManagement_Threshold] The default is 0. Hysteresis Defines the bandwidth fluctuation (change) from the threshold [BWManagement_Hysteresis] value at which the device performs the configured action. The default is 0. Version 6.6 Mediant 3000...

  • Page 202: Configuring Server For Media Quality Of Experience

    13.8 Configuring Server for Media Quality of Experience The device can be configured to report voice (media) quality of experience to AudioCodes Session Experience Manager (SEM) server, a plug-in for AudioCodes EMS. The reports include real-time metrics of the quality of the actual call experience and processed by the SEM.

  • Page 203: Configuring Media Security

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

  • Page 205: 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 643. Version 6.6 Mediant 3000...

  • Page 206: Configuring The Device's Ldap Cache

    Mediant 3000  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 207 LDAP server again. • For a full description of the cache parameters, see 'Configuration Parameters Reference' on page 643. Version 6.6 Mediant 3000...

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

    Mediant 3000  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 209 "PRIVATE" (PRIVATE:<private_number>): used to match a routing rule based on query results of the private number (MSLDAPPrivateNumAttributeName) • "OCS" (OCS:<Lync_number>): used to match a routing rule based on query results of the Lync client number (MSLDAPOCSNumAttributeName) Version 6.6 Mediant 3000...
  • Page 210 Mediant 3000 • "PBX" (PBX:<PBX_number>): used to match a routing rule based on query results of the PBX / IP PBX number (MSLDAPPBXNumAttributeName) • "MOBILE" (MOBILE:<mobile_number>): used to match a routing rule based on query results of the mobile number (MSLDAPMobileNumAttributeName) •...

  • Page 211: Configuring Ad-Based Routing Rules

    The procedure below describes how to configure Tel-to-IP routing based on LDAP queries.  To configure LDAP-based Tel-to-IP routing for Lync Server 2010: Configure the LDAP server parameters, as described in 'Configuring the LDAP Server' on page 205. Configure the AD attribute names used in the LDAP query: Version 6.6 Mediant 3000...
  • Page 212 Mediant 3000 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. For the Gateway/IP-to-IP application: Configure AD-based Tel-to-IP routing rules: Open the Outbound IP Routing Table page (Configuration tab >...
  • Page 213 Rule 6: Sends query for original destination number of received call to the LDAP server.  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases • LDAP functionality is disabled. Version 6.6 Mediant 3000...

  • Page 214: Querying The Ad For Calling Name

    Mediant 3000 • LDAP query is successful but call fails (due to, for example, busy line) to all the relevant attribute destinations (private, Lync, PBX, and mobile), and a relevant Tel-to-IP Release Reason (see Alternative Routing for Tel-to-IP Calls on page 368) or SBC Alternative Routing Reason (see Configuring Alternative Routing Reasons on page 453) has been configured.

  • Page 215: Least Cost Routing

    Note that for one minute, Cost Groups "A" and "D" are identical, but due to the average call duration, Cost Group "D" is cheaper. Therefore, average call duration is an important factor in determining the cheapest routing role. Version 6.6 Mediant 3000...
  • Page 216 Mediant 3000 Below are a few examples of how you can implement LCR:  Example 1: This example uses two different Cost Groups for routing local calls and international calls: Two Cost Groups are configured as shown below: Cost Group...

  • Page 217: Configuring Lcr

    Cost Groups in the Outbound IP Routing table. Note: The Routing Rule Groups table can also be configured using the table ini file parameter, RoutingRuleGroups. Version 6.6 Mediant 3000...
  • Page 218 Mediant 3000  To enable LCR: Open the Routing Rule Groups Table page (Configuration tab > VoIP menu > Services submenu > Least Cost Routing > Routing Rule Groups Table). Click the Add button; the Add Record dialog box appears: Figure 14-7: Routing Rule Groups Table - Add Record Configure the parameters as required.

  • Page 219: Configuring Cost Groups

    Defines the table index entry. [CostGroupTable_Inde Cost Group Name Defines an arbitrary name for the Cost Group. [CostGroupTable_Cost The valid value is a string of up to 30 characters. GroupName] Note: Each Cost Group must have a unique name. Version 6.6 Mediant 3000...

  • Page 220: Configuring Time Bands For Cost Groups

    Mediant 3000 Parameter Description Default Connect Cost Defines the call connection cost (added as a fixed charge to the call) for [CostGroupTable_Defa a call outside the time bands. ultConnectionCost] The valid value range is 0-65533. The default is 0. Note: When calculating the cost of a call, if the current time of the call is not within a time band configured for the Cost Group, then this default connection cost is used.

  • Page 221: Assigning Cost Groups To Routing Rules

    Once you have configured your Cost Groups, you need to assign them to routing rules:  Gateway/IP-to-IP application: Outbound IP Routing table - see Configuring Outbound IP Routing Table on page  SBC application: IP-to-IP Routing table - see Configuring SBC IP-to-IP Routing on page Version 6.6 Mediant 3000...
  • Page 222 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 223: 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 520). Version 6.6 Mediant 3000...
  • Page 224 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 225: Control Network

    SIP Interface table, instead of navigating to the SIP Interface Table page as described in 'Configuring SIP Interface Table' on page 227. • The SRD table can also be configured using the table ini file parameter, SRD. Version 6.6 Mediant 3000...
  • Page 226 Mediant 3000  To configure SRDs: Open the SRD Settings page (Configuration tab > VoIP menu > Control Network submenu > SRD Table). Figure 16-1: SRD Settings Page From the 'SRD Index' drop-down list, select an index for the SRD, and then configure it according to the table below.

  • Page 227: Configuring Sip Interface Table

    Using different SIP listening ports for a single or for multiple IP network interfaces.  Differentiating between applications by creating SIP Interfaces per application.  Separating signaling traffic between networks (e.g., different customers) to use different routing tables, manipulations, SIP definitions, and so on. Version 6.6 Mediant 3000...
  • Page 228 Mediant 3000 Note: The SIP Interface table can also be configured using the table ini file parameter, SIPInterface.  To configure the SIP Interface table: Open the SIP Interface Table page (Configuration tab > VoIP menu > Control Network submenu > SIP Interface Table).
  • Page 229 NAT server or simply to check that the aliveEnable] connection to the IP entity is available. CLI: tcp-keepalive-  enable [0] No (default)  [1] Yes Note: For configuring TCP keepalive, use the following ini file parameters: TCP TCPKeepAliveTime, TCPKeepAliveInterval, and TCPKeepAliveRetry. Version 6.6 Mediant 3000...

  • Page 230: Configuring Ip Groups

    Mediant 3000 Parameter Description Classification Failure Defines the SIP response code that the device sends if a received SIP Response Type request (OPTIONS, REGISTER, or INVITE) has failed the SBC classification process. [SIPInterface_Classific ationFailureResponseT The valid value can be a SIP response code from 400 through 699, or it ype] can be set to 0 to not send any response at all.
  • Page 231 [1] User = Represents a group of users such as IP phones and softphones where their location is dynamically obtained by the device when REGISTER requests and responses traverse (or are terminated) by the device. These users are considered remote (far- Version 6.6 Mediant 3000...
  • Page 232 Mediant 3000 Parameter Description end) users. Typically, this IP Group is configured with a Serving IP Group that represents an IP-PBX, Application or Proxy server that serves this User-type IP Group. Each SIP request sent by a user of this IP Group is proxied to the Serving IP Group.
  • Page 233 For this parameter to take effect, a device reset is required.  If the Media Realm is later deleted from the Media Realm table, then this value becomes invalid.  For configuring Media Realms, see Configuring Media Realms on Version 6.6 Mediant 3000...
  • Page 234 Mediant 3000 Parameter Description page 194. 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 263. Gateway Parameters Always Use Route Table Defines the Request-URI host name in outgoing INVITE messages.
  • Page 235 Proxy Set ID. xySet]  [0] Disable  [1] Enable (default) This classification occurs only if classification according to the device's database fails to (i.e., received INVITE is not from a registered user). Version 6.6 Mediant 3000...
  • Page 236 Mediant 3000 Parameter Description The classification proceeds with checking whether the INVITE's IP address (if host names, then according to the dynamically resolved IP address list) is defined for a Proxy Set ID (in the Proxy Set table). If a Proxy Set ID has such an IP address, the device classifies the INVITE as belonging to the IP Group associated with this Proxy Set.
  • Page 237 Server-type IP Group), 3) User Information file, or 4) sends request to users requesting credentials (only if authenticating User-type IP Group).  [2] SBC as Server = The device authenticates as a server (using the User Information file). Version 6.6 Mediant 3000...

  • Page 238: Configuring Proxy Sets Table

    Mediant 3000 Parameter Description Authentication Method Defines SIP methods that the device must challenge. Multiple entries are List separated by the backslash "\". If you set this parameter to an empty [IPGroup_MethodList] value, no methods are challenged. The default value is "INVITE\REGISTER".
  • Page 239 To the Trunk Group's Serving IP Group ID, as defined in the Trunk Group Settings table.  According to the Outbound IP Routing Table if the parameter PreferRouteTable is set to 1.  To the default Proxy. Version 6.6 Mediant 3000...
  • Page 240 Mediant 3000 Parameter Description Typically, when IP Groups are used, there is no need to use the default Proxy and all routing and registration rules can be configured using IP Groups and the Account tables (see 'Configuring Account Table' on page 243).
  • Page 241 Proxy IP address. The Random Weights Load Balancing is not used in the following scenarios:  The Proxy Set includes more than one Proxy IP address.  The only Proxy defined is an IP address and not an FQDN. Version 6.6 Mediant 3000...
  • Page 242 Mediant 3000 Parameter Description  SRV is not enabled (DNSQueryType).  The SRV response includes several records with a different Priority value. Web/EMS: Is Proxy Enables the Proxy Hot-Swap redundancy mode. Hot-Swap  [0] No (default) [ProxySet_IsProxyH  [1] Yes...

  • Page 243: Sip Definitions

    • The Account table can also be configured using the table ini file parameter, Account.  To configure Accounts: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions submenu > Account Table). Version 6.6 Mediant 3000...
  • Page 244 Mediant 3000 Figure 17-1: Account Table Page In the 'Add' field, enter the desired table row index, and then click Add. A new row appears. Configure the Account parameters according to the table below. Click the Apply button to save your changes.
  • Page 245 ContactUser@<device's IP address>. Notes:  If this parameter is not configured, the 'Contact User' parameter in the IP Group table is used instead.  If registration fails, then the user part in the INVITE Contact header Version 6.6 Mediant 3000...

  • Page 246: Configuring Proxy And Registration Parameters

    Mediant 3000 Parameter Description contains the source party number. Application Type Defines the application type: [Account_Applicat  [0] GW/IP2IP = (Default) Gateway and IP-to-IP application. ionType]  [2] SBC = SBC application. 17.3 Configuring Proxy and Registration Parameters The Proxy & Registration page allows you to configure the Proxy server and registration parameters.
  • Page 247 Register button located on the page in which these entities are configured:   Trunk Groups - Trunk Group Table page (see Configuring Trunk Group Table on page 325)  Accounts - Account table (see 'Configuring Account Table' on page 243) Version 6.6 Mediant 3000...

  • Page 248: Sip Message Authentication Example

    • 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 249 At this time, a new REGISTER request is issued with the following response: 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=1c23940 To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 Server: Audiocodes-Sip-Gateway/Mediant 3000/v.6.60.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”, nonce="11432d6bce58ddf02e3b5e1c77c010d2",...

  • Page 250: Configuring Sip Message Manipulation

    Mediant 3000 17.4 Configuring SIP Message Manipulation The Message Manipulations page allows you to define up to 100 SIP message manipulation rules. Each manipulation rule can be assigned any Manipulation Set ID (0 to 19), enabling you to create groups (sets) of manipulation rules whereby rules of a group are configured with the same Manipulation Set ID number.
  • Page 251 They can only be modified and only on requests that initiate new dialogs. Mandatory SIP headers include To, From, Via, CSeq, Call- Id, and Max-Forwards. • The Message Manipulations table can also be configured using the table ini file parameter, MessageManipulations. Version 6.6 Mediant 3000...
  • Page 252 Mediant 3000  To configure SIP message manipulation rules: Open the Message Manipulations page (Configuration tab > VoIP menu > SIP Definitions submenu > Msg Policy & Manipulation > Message Manipulations). Click the Add button; the following dialog box appears: Figure 17-4: Message Manipulations Table - Add Record Dialog Box Configure the SIP message manipulation rule as required.
  • Page 253 [6] Remove Prefix = removes value from the beginning of the string (string element only). Action Value Defines a value (string) that you want to use in the manipulation. [MessageManipulation The syntax is as follows: s_ActionValue]  string/<message-element>/<call-param> +  string/<message-element>/<call-param> For example:  'itsp.com'  header.from.url.user Version 6.6 Mediant 3000...

  • Page 254: Configuring Sip Message Policy Rules

    Mediant 3000 Parameter Description  param.call.dst.user  param.call.dst.host + '.com'  param.call.src.user + '<' + header.from.url.user + '@' + header.p- asserted-id.url.host + '>' Note: Only single quotation marks must be used. Row Role Determines which condition must be used for the rule of this table row.
  • Page 255 Note: The device supports up to 20 SIP Record-Route headers that can be received in a SIP INVITE request or 200 OK response. If it receives more than this, it responds with a SIP 513 'Message Too Large' response. Version 6.6 Mediant 3000...
  • Page 256 Mediant 3000 Parameter Description Max Num Bodies Defines the maximum number of bodies (e.g., SDP) in the SIP message. [MessagePolicy_MaxN The valid value is any number up to 8. The default is 8. umBodies] Send Rejection Determines whether the device sends a 400 "Bad Request" response if a [MessagePolicy_SendR message request is rejected.

  • Page 257: Coders And Profiles

    Profiles, see 'Configuring Coder Groups' on page 260. • For information on V.152 and implementation of T.38 and VBD coders, see 'Supporting V.152 Implementation' on page 180. • The Coders table can also be configured using the table ini file parameter, CodersGroup. Version 6.6 Mediant 3000...
  • Page 258 Mediant 3000  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 259  [7] 23.05  [8] 23.85 (default)   [0] Variable [0] Disable EVRC 20 (default), 40,60, 80, 100 Dynamic (0- (default) [Evrc] 127)  [1] Enable  [1] 1/8  [3] 1/2  [4] Full Version 6.6 Mediant 3000...

  • Page 260: Configuring Coder Groups

    Mediant 3000 Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression  [0] Variable EVRC-B (4GV) 20 (default), 40, 60, 80, Dynamic (0- (default) [EvrcB] 100, 120 127)  [1] 1/8  [2] 1/4  [3] 1/2 ...

  • Page 261: Configuring Tel Profile

    G.711 coder, you can configure a Tel Profile with this coder and assign it to these channels. Tel Profiles are assigned to channels in the Trunk Group Table (see Configuring the Trunk Group Table on page 325)). The procedure below describes how to configure Tel Profiles using the Web interface. Version 6.6 Mediant 3000...
  • Page 262 Mediant 3000 Note: Tel Profiles can also be configured using the table ini file parameter, TelProfile (see 'Configuration Parameters Reference' on page 643)  To configure Tel Profiles: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu >...

  • Page 263: 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 643). Version 6.6 Mediant 3000...
  • Page 264 Mediant 3000  To configure IP Profiles: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > IP Profile Settings). Figure 18-4: IP Profile Settings Page From the 'Profile ID' drop-down list, select the IP Profile index.
  • Page 265 Web: Echo Canceler For a description, see the global parameter [IpProfile_EnableEchoCanceller EnableEchoCanceller. Web: Input Gain For a description, see the global parameter InputGain. [IpProfile_InputGain] Web: Voice Volume For a description, see the global parameter VoiceVolume. [IpProfile_VoiceVolume] Version 6.6 Mediant 3000...
  • Page 266 Mediant 3000 Parameter Description Web: Symmetric MKI Negotiation For a description, see the global parameter [IpProfile_EnableSymmetricMKI EnableSymmetricMKI. Web: MKI Size For a description, see the global parameter [IpProfile_MKISize] SRTPTxPacketMKISize. Gateway Parameters Web: Fax Signaling Method For a description, see the global parameter IsFaxUsed.
  • Page 267 For a description, see the global parameter EnableHold. [IpProfile_EnableHold] For a description, see the global parameter EnableEarly183. [IpProfile_EnableEarly183] [IpProfile_EarlyAnswerTimeout] For a description, see the global parameter EarlyAnswerTimeout. SBC Parameters Web: Transcoding Mode For a description, see the global parameter TranscodingMode. [IpProfile_TranscodingMode] Version 6.6 Mediant 3000...
  • Page 268 Mediant 3000 Parameter Description Web: Extension Coders Group ID Defines the Coder Group ID used for Extended (additional) [IpProfile_SBCExtensionCoders coders added to the outgoing leg for this profile. This is used GroupID] when transcoding is required between two IP entities (i.e., the SDP answer from one doesn’t include any coder included in the...
  • Page 269 If one of the above transcoding prerequisites is not met, then:  any value other than “As is” is discarded.  if the incoming offer is SRTP, force transcoding, coder transcoding, and DTMF extensions are not applied. Version 6.6 Mediant 3000...
  • Page 270 Mediant 3000 Parameter Description Web: RFC 2833 Behavior Determines the RFC 2833 SDP offer\answer negotiation. [IpProfile_SBCRFC2833Behavio  [0] As is = (Default) The device does not intervene in the RFC 2833 negotiation.  [1] Extend = Each outgoing offer\answer includes RFC 2833 in the offered SDP (the device adds RFC 2833 only if the incoming offer does not include RFC 2833).
  • Page 271 [0] Not Supported = (Default) UA does not support receipt of RFC3960] 18x messages with delayed RTP. For the device's handling of this remote UA support, see Interworking SIP Early Media.  [1] Supported = UA is capable of receiving 18x messages with delayed RTP. Version 6.6 Mediant 3000...
  • Page 272 Mediant 3000 Parameter Description Web: SBC Multiple 18x Support Determines whether multiple 18x responses (including 180 [IpProfile_SBCRemoteMultiple1 Ringing, 181 Call is Being Forwarded, 182 Call Queued, and 8xSupport] 183 Session Progress) are forwarded to the caller.  [0] Not Supported = Only the first 18x response is forwarded to the caller.
  • Page 273 The value range is 96 to 127. The default is 0 (i.e., the device forwards the received payload type as is). Web: SBC User Registration Time For a description, see the global parameter [IpProfile_SBCUserRegistration SBCUserRegistrationTime. Time] Version 6.6 Mediant 3000...
  • Page 274 Mediant 3000 Parameter Description Web: SBC Remote Hold Format Defines the format of the SDP in the re-INVITE for call hold that [IPProfile_SBCRemoteHoldFor the device sends to the held party. mat]  [0] transparent = Device forwards SDP as is.

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

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

  • Page 277: 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 3000...
  • Page 278 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 279: 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 3000...

  • Page 280: Theory Of Operation

    Mediant 3000  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 281: Proxy Sets

    Figure 20-2: IP-to-IP Routing/Registration/Authentication of Remote IP-PBX Users (Example) 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 Version 6.6 Mediant 3000...

  • Page 282: Inbound And Outbound Ip Routing Rules

    Mediant 3000 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 device uses its database for routing calls between the clients of the User-type IP Group.

  • Page 283: 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 3000...
  • Page 284 Mediant 3000 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 285: Step 1: Enable The Ip-To-Ip Capabilities

    The number of media channels represents the number of digital signaling processors (DSP) channels that the device allocates to IP-to-IP calls. The remaining DSP channels can be used for PSTN calls. Two IP media channels are used per IP-to-IP call. Version 6.6 Mediant 3000...

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

    Mediant 3000  To configure the number of media channels: Open the IP Media Settings page (Configuration tab > VoIP menu > IP Media > IP 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"...
  • Page 287 From the 'Proxy Set ID' drop-down list, select 2. In the 'Proxy Address' column, enter the IP addresses of the ITSP-B SIP trunk (e.g., "216.182.224.202" and "216.182.225.202"). From the 'Transport Type' drop-down list corresponding to the IP address entered above, select UDP. Version 6.6 Mediant 3000...

  • Page 288: Step 5: Configure The Ip Groups

    Mediant 3000 In the 'Enable Proxy Keep Alive' drop-down list, select "Using Options", and then in the '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.
  • Page 289 No Serving IP Groups are defined for ITSP-A and ITSP-B. Instead, the Outbound IP Routing table (see 'Step 9: Configure Outbound IP Routing' on page 294) is used to configure outbound IP call routing for calls originating from these ITSP IP Groups. Version 6.6 Mediant 3000...

  • Page 290: Step 6: Configure The Account Table

    Mediant 3000 20.2.6 Step 6: Configure the Account Table The Account table is used by the device to register to an ITSP on behalf of the IP-PBX. As described previously, the ITSP requires registration and authentication to provide service. For the example, the Served IP Group is the IP-PBX (IP Group ID #3) and the Serving IP Groups are the two ITSPs (IP Groups #1 and #2).
  • Page 291 Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Configure Profile ID #1 for the IP-PBX (as shown below): From the 'Profile ID' drop-down list, select 1. From the 'Coder Group' drop-down list, select Coder Group 1. Version 6.6 Mediant 3000...

  • Page 292: Step 8: Configure Inbound Ip Routing

    Mediant 3000 Click Submit. Figure 20-14: Defining IP Profile ID 1 Configure Profile ID #2 for the ITSP's: From the 'Profile ID' drop-down list, select 2. From the 'Coder Group' drop-down list, select Coder Group 2. Click Submit. 20.2.8 Step 8: Configure Inbound IP Routing This step defines how to configure the device for routing inbound (i.e., received) IP-to-IP...
  • Page 293 'Trunk Group ID': enter "1" to route these calls to the Trunk Group ID configured for the Trunk connected to the device and interfacing with the local PSTN. • 'Source IP Group ID': enter "-1" to indicate that these calls are not assigned to any source IP Group. Version 6.6 Mediant 3000...

  • Page 294: Step 9: Configure Outbound Ip Routing

    Mediant 3000 20.2.9 Step 9: Configure Outbound IP Routing This step defines how to configure the device for routing outbound (i.e., sent) IP-to-IP calls. In our example scenario, calls from both ITSP's must be routed to the IP-PBX, while outgoing calls from IP-PBX users must be routed according to destination. If the calls are destined to the Japanese market, then they are routed to ITSP-B;...
  • Page 295 'Dest IP Group ID': select 4 to indicate the destination IP Group to where the calls must be sent, i.e., to remote IP-PBX users. • 'IP Profile ID': enter "1" to indicate the IP Profile configured for G.711. Version 6.6 Mediant 3000...

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

    Mediant 3000 20.2.10 Step 10: Configure Destination Phone Number Manipulation This step defines how to manipulate the destination phone number. The IP-PBX users in our example scenario use a 4-digit extension number. The incoming calls from the ITSP's have different prefixes and different lengths. This manipulation leaves only the four digits of the user's destination number coming from the ITSP's.

  • Page 297: Digital Pstn

    For a description of the trunk parameters, see 'PSTN Parameters' on page 766. Notes: • During trunk deactivation, trunk configuration cannot be performed. • A stopped trunk cannot also be activated and a trunk cannot be deactivated if it has been stopped. Version 6.6 Mediant 3000...
  • Page 298 Mediant 3000  To configure the 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 299 E1/T1 trunk to provide the device’s clock or enable ‘TDM Bus PSTN Auto Clock’ in the TDM Bus Settings page (see 'TDM and Timing' on page 300). • To delete a previously configured trunk, set the parameter 'Protocol Type' to 'None'. Version 6.6 Mediant 3000...

  • Page 300: Tdm And Timing

    Mediant 3000 21.2 TDM and Timing This section describes the configuration of the TDM and clock timing parameters. Note: If you are modifying multiple pages, perform a device reset (if required) only after you have completed modifying all the required pages (and not after each page).

  • Page 301: Configuring System Timing

    BITS synchronization (see Configuring BITS Synchronization Mode on page 303)  Internal clock (see 'Configuring Internal Clock as Clock Source' on page 304) Note: When the device is used in a ‘non-span’ configuration, the internal device clock must be used (as explained above). Version 6.6 Mediant 3000...

  • Page 302: Recovering Clock From Pstn Line Interface

    Mediant 3000 21.2.4.1 Recovering Clock from PSTN Line Interface This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line (Trunk/STM-1/OC-3/T3) interface. For a full description of the clock parameters, see 'PSTN Parameters' on page 766.

  • Page 303: Configuring Bits Synchronization Mode

    When both BITS reference clock sources fail, the device enters into clock holdover. Version 6.6 Mediant 3000...

  • Page 304: Configuring Internal Clock As Clock Source

    T3/DS3 or SONET/SDH). For a description of the parameters related to transmission type, see 'PSTN Parameters' on page 766. Notes: • Transmission settings are applicable only to Mediant 3000 with TP-6310. • When applying your settings, traffic disturbances may be experienced. User's Manual...
  • Page 305 Device' on page 517). For SDH/SONET, to view the KLM Numbering Mapping Table page, click Go to the KLM Mapping Table button. For a description on KLM numbering, see 'Trunk Numbering (KLM Numbering)' on page 319. Version 6.6 Mediant 3000...

  • Page 306: Configuring Cas State Machines

    Mediant 3000 21.4 Configuring CAS State Machines The CAS State Machine page allows you to modify various timers and other basic parameters to define the initialization of the CAS state machine without changing the state machine itself (no compilation is required). The change doesn't affect the state machine itself, but rather the configuration.
  • Page 307 Defines which Signaling System to use in both directions (detection\generation). [CasStateMachineDigitSign alingSystem]  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 6.6 Mediant 3000...

  • Page 308: Configuring Digital Gateway Parameters

    Mediant 3000 21.5 Configuring Digital Gateway Parameters The Digital Gateway Parameters page allows you to configure miscellaneous digital parameters. For a description of these parameters, see 'Configuration Parameters Reference' on page 643.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab > VoIP menu > GW and IP to IP submenu >...

  • Page 309: Tunneling Applications

    ‘Transparent’ coder to transport data (e.g., for D-channel). You can also use Profiles to assign ToS (for DiffServ) per source - a timeslot carrying data or signaling is assigned a higher priority value than a timeslot carrying voice. Version 6.6 Mediant 3000...
  • Page 310 Mediant 3000 For tunneling of E1/T1 CAS trunks, set the protocol type to 'Raw CAS' (ProtocolType = 3 / 9) and enable RFC 2833 CAS relay mode ('CAS Transport Type' parameter is set to 'CAS RFC2833 Relay'). Note: For TDM over IP, the parameter CallerIDTransportType must be set to '0' (disabled), i.e., transparent.
  • Page 311 CodersGroup0 0 = g7231; 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,$$,$$,$$,$$,$$,$$,$$ Version 6.6 Mediant 3000...

  • Page 312: Dsp Pattern Detector

    Mediant 3000 TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 21.6.1.1 DSP Pattern Detector For TDM tunneling applications, you can use the DSP pattern detector feature to initiate the echo canceller at call start. The device can be configured to support detection of a specific one-byte idle data pattern transmitted over digital E1/T1 timeslots.

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

    Web interface (see 'Configuring Trunk Settings' on page 297). The parameter ‘DchConfig_x = Trunk_type’ defines the type of NFAS trunk. Trunk_type is set to 0 for the primary trunk, to 1 for the backup trunk, and to 2 for an ordinary NFAS Version 6.6 Mediant 3000...

  • Page 314: Nfas Interface Id

    Mediant 3000 trunk. ‘x’ denotes the physical trunk ID (0 to the maximum number of trunks). You can also use the Web interface (see 'Configuring Trunk Settings' on page 297). For example, to assign the first four T1 trunks to NFAS group #1, in which trunk #0 is the...

  • Page 315: Creating An Nfas-Related Trunk Configuration

    • All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure it. Version 6.6 Mediant 3000...

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

    Mediant 3000 21.7.4 Performing Manual D-Channel Switchover in NFAS Group If an NFAS group is configured with two D-channels (Primary and Backup), you can do a manual switchover between these D-channels.  To manually switchover from active to standby D-channel: Open the NFAS Group &...

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

     ISDNRxOverlap = 2  ISDNTxOverlap  ISDNOutCallsBehavior = 2  MinOverlapDigitsForRouting  TimeBetweenDigits  MaxDigits  DigitMapping  MuteDTMFInOverlap For configuring ISDN overlap dialing using the Web interface, see 'Configuring Trunk Settings' on page 297. Version 6.6 Mediant 3000...

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

    Mediant 3000 21.9 Redirect Number and Calling Name (Display) The following tables define the device's redirect number and calling name (Display) support for various ISDN variants according to NT (Network Termination) / TE (Termination Equipment) interface direction: Calling Name (Display)

  • Page 319: Trunk Numbering (Klm Numbering)

    Timeslots scheme according to ITU-T G.707 clause 7.3.9. (Hardware timeslots) Once the scheme has been selected, the corresponding table is automatically determined for 63 or 84 tributaries (trunks). Note: This section is only applicable to Mediant 3000 with the TP-6310 blade(s). Version 6.6 Mediant 3000...

  • Page 320: E1 Trunk Enumeration (Sdh Mappings)

    Mediant 3000 21.10.1.1 E1 Trunk Enumeration (SDH Mappings) The following table is used for converting internal STM-1 (KLM) numbering to sequential trunk numbering for API references. The three numbers - TUG3 ('K'), TUG2 ('L') and TU ('M') - set the position of the E1 (V-12) trunk inside the STM-1 frame.
  • Page 321 User's Manual 21. Digital PSTN Trunk ETSI GR-253 Timeslots TUG- TUG-2 TU-12 TUG-3 TUG-2 TU-12 TUG-3 TUG-2 TU-12 Version 6.6 Mediant 3000...

  • Page 322: T1 Trunk Enumeration (Sonet Mappings)

    Mediant 3000 21.10.1.2 T1 Trunk Enumeration (Sonet Mappings) The following table is used for converting internal OC-3 numbering to sequential trunk numbering for API references. The three numbers - STS-1 (K), TUG2 (L) and TU (M) - set the position of the T1 (V-1.5) trunk inside the OC-3 frame.
  • Page 323 User's Manual 21. Digital PSTN Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 Version 6.6 Mediant 3000...
  • Page 324 Mediant 3000 Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 User's Manual Document #: LTRT-89729...

  • Page 325: Trunk Group

    Configure the Trunk Group as required. For a description of the parameters, see the table below. Click Submit to apply your changes. To save the changes to the flash memory, see 'Saving Configuration' on page 520. To register the Trunk Groups, click the Register button. To unregister the Trunk Version 6.6 Mediant 3000...
  • Page 326 Mediant 3000 Groups, click Unregister. The registration method for each Trunk Group is according to the 'Registration Mode' parameter in the Trunk Group Settings page (see 'Configuring Trunk Group Settings' on page 327). Trunk Group Table Parameters Parameter Description From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 327: Configuring Trunk Group Settings

    [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 Version 6.6 Mediant 3000...
  • Page 328 Mediant 3000 Parameter Description ascending again.  [2] Ascending = The lowest available channel in the Trunk Group is selected, and if unavailable, the next higher channel is selected.  [3] Cyclic Descending = The next available channel in descending cyclic order is selected.
  • Page 329 IP Group table (see 'Configuring IP Groups' on page 230). Notes:  If this parameter is not configured, the INVITE messages are sent to the default Proxy or according to the Outbound IP Routing Table (see 'Configuring Outbound IP Routing Table' on page Version 6.6 Mediant 3000...
  • Page 330 Mediant 3000 Parameter Description 355).  If the PreferRouteTable parameter is set to 1 (see 'Configuring Proxy and Registration Parameters' on page 246), the routing rules in the Outbound IP Routing table take precedence over the selected Serving IP Group ID.

  • Page 331: Manipulation

    1 and "55" for rule index 2, the device uses rule index 1 for numbers that start with 551 and uses rule index 2 for numbers that start with 550, 552, 553, and so on until 559. Version 6.6 Mediant 3000...
  • Page 332 Mediant 3000 However, if you configure the source prefix number as "55" for rule index 1 and "551" for rule index 2, the device applies rule index 1 to all numbers that start with 55, including numbers that start with 551. If the device doesn't find a matching rule, no manipulation is done on the call.
  • Page 333 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 Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Version 6.6 Mediant 3000...
  • Page 334 Mediant 3000 Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Number Manipulation Parameters Description Parameter Description Matching Characteristics (Rule) Web: Destination Prefix Defines the destination (called) telephone number prefix and/or suffix.
  • Page 335 Defines the number of digits that you want to keep from the right of Digits to Leave the phone number. For example, if you enter 4 and the phone number [LeaveFromRight] is 00165751234, then the new number is 1234. Version 6.6 Mediant 3000...
  • Page 336 Mediant 3000 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 337: 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 3000...

  • Page 338: Sip Calling Name Manipulations

    Mediant 3000 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 339 Notes:  This parameter is applicable only to the Calling Name Manipulations Tel2IP table.  The value -1 indicates that this field is ignored in the rule.  This parameter is applicable only to Tel-to-IP calls. Version 6.6 Mediant 3000...
  • Page 340 Mediant 3000 Parameter Description Web: Source IP Group ID Defines the IP Group from where the IP call originated. Notes:  This parameter is applicable only to the Calling Name Manipulations Tel2IP table.  The value -1 indicates that this field is ignored in the rule.
  • Page 341 User's Manual 23. Manipulation Parameter Description EMS: Prefix/Suffix To Add For example, if you enter 00 and calling name is "company:name", the new name is "company:name00". Version 6.6 Mediant 3000...

  • Page 342: Configuring Redirect Number Ip To Tel

    Mediant 3000 23.5 Configuring Redirect Number IP to Tel You can configure rules for manipulating the redirect number received in the incoming message:  IP-to-Tel redirect number manipulation: You can manipulate the value of the received SIP Diversion, Resource-Priority, or History-Info headers, which is then added to the Redirecting Number Information Element (IE) in the ISDN Setup message sent to the Tel side.
  • Page 343 For IP-to-IP call routing, this parameter is not relevant. Source IP Group ID Defines the IP Group from where the IP call originated. Typically, the [SrcIPGroupID] IP Group of an incoming INVITE is determined or classified by the Version 6.6 Mediant 3000...
  • Page 344 Mediant 3000 Parameter Description Inbound IP Routing Table. If not used (i.e., any IP Group), leave the field empty. Notes:  This parameter is applicable only to the Redirect Number Tel > IP table.  This parameter is applicable only to the IP-to-IP application.

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

    Diverted-to number and Diverting number. The Diverted-to number (i.e., new destination) is mapped to the user part in the Contact header of the SIP 302 response. The Diverting number is mapped to the user part in the Diversion header of the SIP 302 response. Version 6.6 Mediant 3000...

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

    Mediant 3000 These two numbers can be manipulated by entering the following special strings in the 'Destination Prefix' field of the Redirect Number Tel -> IP manipulation table:  "RN" - used in the rule to manipulate the Redirected number (i.e., originally called number or Diverting number).
  • Page 347 ISDN Setup message with called and [AddPhoneContextAsPre calling numbers. fix]  [0] Disable (default)  [1] Enable Defines the Number Plan Indicator (NPI). [PhoneContext_Npi]  [0] Unknown (default)  [1] E.164 Public  [9] Private Version 6.6 Mediant 3000...

  • Page 348: Configuring Release Cause Mapping

    Mediant 3000 Parameter Description For a detailed list of the available NPI/TON values, see Numbering Plans and Type of Number on page 353. Defines the Type of Number (TON). [PhoneContext_Ton]  If you selected Unknown as the NPI, you can select Unknown [0].

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

    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 Version 6.6 Mediant 3000...
  • Page 350 Mediant 3000 ISDN Release Description Description Response Reason Not acceptable Service/option not implemented Proxy authentication Call rejected required Request timeout Recovery on timer expiry Conflict Temporary failure Gone Number changed w/o diagnostic Length required Interworking Request entity too long Interworking...

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

    Service unavailable QoS unavailable 503* Service unavailable 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 Version 6.6 Mediant 3000...
  • Page 352 Mediant 3000 ISDN Release Description Description Reason Response Bearer capability not implemented Not implemented Channel type not implemented 480* Temporarily unavailable Requested facility not implemented 503* Service unavailable Only restricted digital information bearer 503* Service unavailable capability is available Service or option not implemented...

  • Page 353: Reason Header

    5551234. Abbreviated [6] The support of this code is network dependent. The number provided in this information element presents a shorthand representation of the complete number in the specified numbering plan as supported by the network. Version 6.6 Mediant 3000...
  • Page 354 Mediant 3000 Description 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. PISN Specific [3] Level 0 Regional (local) [4] A private local extension number, e.g., 2200.

  • Page 355: Routing

    If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call. The matching characteristics of the incoming call can be one or more of the following: Version 6.6 Mediant 3000...
  • Page 356 Mediant 3000  Source IP Group (to which the call belongs)  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 ...
  • Page 357 IP address, or use an FQDN that resolves into two IP addresses. For more information on alternative routing, see 'Alternative Routing for Tel-to-IP Calls' on page 368. Version 6.6 Mediant 3000...
  • Page 358 Mediant 3000 Notes: • Outbound IP routing can be performed before or after number manipulation. This is configured using the RouteModeTel2IP parameter, as described below. • The Outbound IP Routing Table can also be configured using the table ini file parameter, Prefix.
  • Page 359 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 3000...
  • Page 360 Mediant 3000 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 361 Defines the transport layer type for sending the IP call: Type  [-1] Not Configured [PREFIX_Transport  [0] UDP Type]  [1] TCP  [2] TLS Note: When set to Not Configured (-1), the transport type defined by the SIPTransportType parameter is used. Version 6.6 Mediant 3000...
  • Page 362 Mediant 3000 Parameter Description Web: Dest IP Group Defines the IP Group to where you want to route the call. The SIP INVITE message is sent to the IP address defined for the Proxy Set ID associated EMS: Destination IP with the IP Group.

  • Page 363: Configuring Inbound Ip Routing Table

    For IP-to-Tel routing: This table is used to route incoming IP calls to Trunk Groups. The specific channel pertaining to the Trunk Group to which the call is routed is determined according to the Trunk Group's channel selection mode. The channel Version 6.6 Mediant 3000...
  • Page 364 Mediant 3000 selection mode can be defined per Trunk Group (see 'Configuring Trunk Group Settings' on page 327) or for all Trunk Groups using the global parameter ChannelSelectMode. Configuration of IP-to-Tel/IP-to-IP routing rules includes two areas:  Matching Characteristics: Defines the characteristics of the incoming IP call (e.g., IP Group from which the call is received).
  • Page 365 'Dialing Plan Notation for Routing and Manipulation Tables' on page 641. The prefix can include up to 49 digits. Web: Source IP Address Defines the source IP address of the incoming IP call that can be used Version 6.6 Mediant 3000...
  • Page 366 Mediant 3000 Parameter Description [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: ...

  • Page 367: Ip Destinations Connectivity Feature

    IP destination, it is resolved into an IP address by a DNS server. The device checks network connectivity and QoS of the resolved IP address. If the DNS host name is unresolved, the device considers the connectivity of the IP destination as unavailable. Version 6.6 Mediant 3000...

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

    Mediant 3000 You can view the connectivity status of IP destinations in the following Web interface pages:  Outbound IP Routing Table: The connectivity status of the IP destination per routing rule is displayed in the 'Status' column. For more information, see 'Configuring Outbound IP Routing Table' on page 355.

  • Page 369: Alternative Routing Based On Sip Responses

    IP destination configured for this alternative routing rule. The table below shows an example of alternative routing where the device uses the first available alternative routing rule to re-route the initial, unsuccessful Tel-to-IP call destination. Version 6.6 Mediant 3000...
  • Page 370 Mediant 3000 Alternative Routing based on SIP Response Code Example Destination IP Destination SIP Response Rule Used? Phone Prefix 408 Request Main Route 10.33.45.68 Timeout Alternative Route 486 Busy Here 10.33.45.70 Alternative Route 200 OK 10.33.45.72  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.

  • Page 371: Pstn Fallback

    (i.e., its IP address) to a specific Trunk Group connected to the PSTN. This configuration is necessary as the re-routed call is now considered an IP-to-Tel call. For configuring IP-to-Tel routing rules, see 'Configuring the Inbound IP Routing Table' on page 363. Version 6.6 Mediant 3000...

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

    Mediant 3000 24.6 Alternative Routing for IP-to-Tel Calls The device supports alternative IP-to-Tel call routing, as described in this section. 24.6.1 Alternative Routing to Trunk upon Q.931 Call Release Cause Code You can configure the device to do alternative IP-to-Tel call routing based on the received ISDN Q.931 cause code.

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

    SIP Diversion header of 3xx messages exists:  “out-of-service” - all trunks are unavailable/disconnected  "unavailable": All trunks are busy or unavailable Note: You can also configure the Forward on Busy Trunk Destination table using the table ini file parameter, ForwardOnBusyTrunkDest. Version 6.6 Mediant 3000...
  • Page 374 Mediant 3000  To configure Forward on Busy Trunk Destination rules: Open the Forward on Busy Trunk Destination page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Forward on Busy Trunk). Figure 24-9: Forward on Busy Trunk Destination Page The figure above displays a configuration that forwards IP-to-Tel calls destined for Trunk Group ID 1 to destination IP address 10.13.5.67 if the conditions mentioned...

  • Page 375: Configuring Dtmf And Dialing

    Digit string (i.e., dialed number) matches one of the patterns defined in the digit map. Digit map (pattern) rules are defined using the DigitMapping parameter. The digit map pattern can contain up to 52 options (rules), each separated by a vertical bar ("|"). The Version 6.6 Mediant 3000...

  • Page 376: External Dial Plan File

    Mediant 3000 maximum length of the entire digit pattern is 152 characters. The available notations are described in the table below: Digit Map Pattern Notations Notation Description [n-m] Range of numbers (not letters). (single dot) Repeat digits until next notation (e.g., T).

  • Page 377: 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 520. Version 6.6 Mediant 3000...

  • Page 378: Call Hold And Retrieve

    Mediant 3000 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 379: 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 3000...

  • Page 380: Call Forward

    Mediant 3000 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 381: Emergency E911 Phone Number Services

    The preemption is done only if the incoming IP-to-Tel call is identified as an emergency call. The device identifies emergency calls by one of the following:  The destination number of the IP call matches one of the numbers defined by the Version 6.6 Mediant 3000...

  • Page 382: Enhanced 9-1-1 Support For Lync Server 2010

    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 383: Microsoft Lync Server 2010 And E9-1-1

    E9-1-1, the location data that is stored on the client is sent during an emergency call. This stored location information is acquired automatically from the Microsoft Location Information Server (LIS). The LIS stores the location of each network Version 6.6 Mediant 3000...
  • Page 384 Mediant 3000 element in the enterprise. Immediately after the Lync 2010 client registration process or when the operating system detects a network connection change, each Lync 2010 client submits a request to the LIS for a location. If the LIS is able to resolve a location address for the client request, it returns the address in a location response.
  • Page 385 (CSV) file containing the column formats listed in the table below. Columns in the LIS Database Network Element Columns <BSSID>,<Description>,<Location>,<CompanyName>,<HouseNumber Wireless access point >,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffi x>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> <Subnet>,<Description>,<Location>,<CompanyName>,<HouseNumber> ,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix Subnet >,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> <ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location>,<Co mpanyName>,<HouseNumber>,<HouseNumberSuffix>,…<PreDirection Port al>,<StreetName>,<StreetSuffix>,<PostDirectional>,<City>,<State>,<Po stalCode>,<Country> <ChassisID>,<Description>,<Location>,<CompanyName>,<HouseNumb Switch er>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSu ffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> Version 6.6 Mediant 3000...
  • Page 386 Mediant 3000 For the ELIN number to be included in the SIP INVITE (XML-based PIDF-LO message) sent by the Mediation Server to the ELIN Gateway, the Administrator must add the ELIN number to the <CompanyName> column (shown in the table above in bold typeface). As the ELIN Gateway supports up to five ELINs per PIDF-LO, the <CompanyName>...

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

    ELIN when dialing 9-1-1. 26.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN The Microsoft Mediation Server sends the location information of the E9-1-1 caller in the XML-based PIDF-LO body contained in the SIP INVITE message.
  • Page 388 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 389 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 390 Mediant 3000 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> <ca:PC>98052</ca:PC></ca:civicAddress></gp:location- info><gp:usage-rules><bp:retransmission- allowed>true</bp:retransmission-allowed></gp:usage- rules></gp:geopriv><ms:msftE911PidfExtn><ms:ConferenceUri>sip:+142 55550199@contoso.com;user=phone</ms:ConferenceUri><ms:ConferenceMo...
  • Page 391 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 number as follows: Version 6.6 Mediant 3000...

  • Page 392: 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 393: Multilevel Precedence And Preemption

    MLPP subscriber. When an MLPP subscriber that belongs to a particular domain places a precedence call to another MLPP subscriber that belongs to the same domain, MLPP service can Version 6.6 Mediant 3000...
  • Page 394 Mediant 3000 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 395 If the network-domain field in the Resource-Priority header is any value other than "uc", then the device sets the Precedence Level field to "0 1 0 0" (i.e., "routine"). This can be modified using the EnableIp2TelInterworkingtable field of the ini file parameter, ResourcePriorityNetworkDomains. Version 6.6 Mediant 3000...

  • Page 396: Mlpp Preemption Events In Sip Reason Header

    Mediant 3000 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 used. This is configured using the RPRequired parameter. • For a complete list of the MLPP parameters, see 'MLPP and Emergency Call Parameters' on page 760.

  • Page 397: 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 355). Version 6.6 Mediant 3000...

  • Page 398: Configuring Voice Mail

    Mediant 3000 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 643. Notes: • The Voice Mail Settings page is available only for CAS interfaces.

  • Page 399: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 401: Introduction

    For guidelines on how to deploy your E-SBC device based on network topology, refer to the SBC Design Guide document. • For SBC functionality, the Software License Key installed on the device must include the SBC feature. Version 6.6 Mediant 3000...
  • Page 402 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 403: Sbc Overview

    IP-PBX.  Survivability: • Routing calls to alternative routes such as the PSTN. • Routing calls between user agents in the local network using a dynamic database (built according to registrations of SIP user agents). Version 6.6 Mediant 3000...

  • Page 404: Sip Network Definitions

    Mediant 3000  Routing: • IP-to-IP routing translations of SIP, UDP, TCP, TLS (when extensive transcoding is not required). • Load balancing and redundancy of SIP servers. • Routing according to Request-URI\Specific IP address\Proxy\FQDN. • Alternative routing. • Routing between different Layer-3 networks (e.g., LAN and WAN).
  • Page 405 'SBC Manipulations' on page 455. SIP message manipulations: You can configure SIP message manipulation rules that can add, remove, and/or modify SIP headers and parameters. For more information, see 'Configuring SIP Message Manipulation' on page 250. Version 6.6 Mediant 3000...

  • Page 406: User Registration And Internal Database

    Mediant 3000 The flowchart below illustrates the SBC process: Figure 28-1: Routing Process 28.3 User Registration and Internal Database To allow registrations to traverse the SBC, the device must be configured with at least one User-type IP Group. These IP Groups represent a group of user agents that share the following characteristics: ...

  • Page 407: Initial Registration Request Processing

    The device manages a dynamic database that is updated according to registration requests that traverse the SBC. Each database entry represents a binding between an AOR and one or more contact. Database bindings are added upon successful registration Version 6.6 Mediant 3000...

  • Page 408: Routing Using Internal Database

    Mediant 3000 responses. For specific registrations, the AOR is obtained from the SIP To header and the contact is taken from the SIP Contact header. Database bindings are removed in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero) ...

  • Page 409: Registration Restriction Control

    (e.g. audio, fax, modem, DTMF). Each offer/answer may create more than one media session of different types (e.g. audio and fax). In a SIP dialog, multiple offer/answer transactions may occur, each may change the media sessions characteristics (e.g. IP Version 6.6 Mediant 3000...
  • Page 410 Mediant 3000 address, port, coders, media types, and RTP mode). The media capabilities exchanged in an offer/answer transaction include the following:  Media types (Audio, Secure Audio, Video, Fax, Text...)  IP addresses and ports of the media flow ...

  • Page 411: Media Anchoring Without Transcoding (Transparent)

    IP Group). Therefore, to allow user agents of different IP Groups to communicate with each other (regardless of their capabilities), an extended coders table with at least one coder that is supported by each IP Groups' user agents needs to be Version 6.6 Mediant 3000...
  • Page 412 Mediant 3000 assigned to each IP Group. Therefore, each offer destined to specific IP Groups include this coder. In the scenario depicted in the figure below, the IP phone on the LAN side initiates a call to the IP phone on the WAN. The initial SDP offer (from the LAN leg) includes codec G.711 as its supported codec.

  • Page 413: No Media Anchoring

    IP address, coders  Opening voice channels and allocation of IP media ports are not required The No Media Anchoring feature is typically implemented in the following scenarios:  SBC device is located within the LAN. Version 6.6 Mediant 3000...
  • Page 414 Mediant 3000  Calls between two SIP UA's in the same LAN and signals are sent to a SIP proxy server (or hosted IP PBX) located in the WAN. Figure 28-5: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring include the following: ...

  • Page 415: Transcoding Modes

    The Allowed Coders process is as follows: The device receives an incoming SIP message with SDP (offer) and checks the offered coders. The source (first) leg may have Allowed Coders (i.e. list of coders that can be used - enforced). Version 6.6 Mediant 3000...

  • Page 416: Coder Transcoding

    Mediant 3000 The device checks for common coders between the SDP offered coders and the Allowed Coders Group list. For example, assume the following:  The SDP coder offer includes the following coders: G.729, G.711, and G.723.  The source (first) leg includes the following Allowed Coders: G.711 and G.729.

  • Page 417: Prioritizing Coder List In Sdp Offer

    SDP offer\answer.  SBC legs negotiate only RTP media lines; SRTP media lines are removed from the incoming offer\answer.  Each SDP offer\answer is extended (if not already) to two media lines for RTP and SRTP. Version 6.6 Mediant 3000...

  • Page 418: Multiple Rtp Media Streams Per Call Session

    Mediant 3000 If after SDP offer\answer negotiation, one SBC leg uses RTP while the other uses SRTP, then the device performs RTP-SRTP transcoding. To translate between RTP and SRTP, the following prerequisites must be met:  At least one supported SDP "crypto" attribute.

  • Page 419: Fax Negotiation And Transcoding

    This is configured using the IP Group table parameter, MethodList. If the message is received without an Authorization header, the device "challenges" the client by sending a 401 or 407 SIP response. The client then resends the request Version 6.6 Mediant 3000...

  • Page 420: Interworking Sip Signaling

    403 "Forbidden" response. If the user is successfully identified, the SIP message request is processed. Note: This feature is applicable only to Mediant 3000 in Simplex mode. 28.8 Interworking SIP Signaling The device supports interworking of SIP signaling messages to ensure interoperability between communicating SIP UAs or entities.
  • Page 421 Upon receipt of the new request from the FEU, the device replaces the Request-URI with destination address (e.g., RequestURI: sip:Prefix_User@IPPBX:5070;transport=tcp;param=a). The device removes the user prefix from the Request-URI, and then sends this Request-URI destination (e.g., RequestURI: sip:User@IPPBX:5070;transport=tcp;param=a). Version 6.6 Mediant 3000...

  • Page 422: Local Handling Of Sip 3Xx

    Mediant 3000 28.8.1.2 Local Handling of SIP 3xx The device can handle SIP 3xx responses on behalf of the dialog-initiating UA and retry the request (e.g., INVITE) using one or more alternative URIs included in the 3xx response. The new request includes SIP headers from the initial request such as Diversion, History- Info, P-Asserted-Id, and Priority.

  • Page 423: Interworking Sip Refer Messages

    Mandatory: PRACK is required for these UAs. Calls from UAs that do not support PRACK are rejected. Calls destined to these UAs are also required to support PRACK.  Transparent (default): The device does not intervene with the PRACK process and forwards the request as is. Version 6.6 Mediant 3000...

  • Page 424: Interworking Sip Session Timer

    Mediant 3000 28.8.5 Interworking SIP Session Timer The device supports interworking of the SIP signaling keep-alive mechanism. The SIP standard provides a signaling keep-alive mechanism using re-INVITE and UPDATE messages. In certain setups, keep-alive may be required by some SIP UAs while for others it may not be supported.
  • Page 425 User's Manual 28. SBC Overview Figure 28-7: SBC Early Media RTP 18x without SDP Figure 28-8: Early Media RTP - SIP 18x with SDP Version 6.6 Mediant 3000...

  • Page 426: Interworking Sip Re-Invite Messages

    Mediant 3000 28.8.7 Interworking SIP re-INVITE Messages The device supports interworking of SIP re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs. The device does not forward re-INVITE requests to IP Groups that do not support it.

  • Page 427: Interworking Call Hold

    Contact associated with the dialed phone number or extension number in the registration database. Below is an example of an XML body received from the BroadWorks server: <?xml version="1.0" encoding="utf-8"?> <BroadsoftDocument version="1.0" content="subscriberData"> <phoneNumbers> <phoneNumber>2403645317</phoneNumber> <phoneNumber>4482541321</phoneNumber> </phoneNumbers> <aliases> Version 6.6 Mediant 3000...

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

    Mediant 3000 <alias>sip:bob@broadsoft.com</alias> <alias>sip:rhughes@broadsoft.com</alias> </aliases> <extensions> <extension>5317</extension> <extension>1321</extension> </extensions> </BroadSoftDocument> 28.9.2 BroadSoft's Shared Phone Line Call Appearance for SBC Survivability The device can provide redundancy for BroadSoft's Shared Call Appearance feature. When the BroadSoft application server switch (AS) fails or does not respond, or when the network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients.
  • Page 429 Set the 'Remove From Right' field to "1" to remove the last digit of the extensions (e.g., 601 is changed to 60). • Set the 'Suffix to Add' field to "0" to add 0 to the end of the manipulated number (e.g., 60 is changed to 600). Version 6.6 Mediant 3000...

  • Page 430: Call Survivability For Call Centers

    Mediant 3000 28.9.3 Call Survivability for Call Centers The device supports call survivability for call centers. When a communication failure (e.g., in the network) occurs with the remote voice application server responsible for handling the call center application (such as IVR), the device routes the incoming calls received from the customer (i.e., from the TDM gateway) to the call center agents.
  • Page 431 The 'Destination IP Group ID' field is set to the IP Group of the call center agents. The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure 28-13: Routing Rule Example for Call Center Survivability Version 6.6 Mediant 3000...

  • Page 432: Survivability Mode Display On Aastra Ip Phones

    Mediant 3000 28.9.4 Survivability Mode Display on Aastra IP Phones If the SBC device is deployed in an Enterprise network with Aastra IP phones and connectivity with the WAN fails, the device provides call survivability by enabling communication between IP phone users within the LAN enterprise. In such a scenario, the device can be configured to notify the IP phones that it is currently operating in Survivability mode.

  • Page 433: Sip Forking Initiated By Sip Proxy Server

    The re-INVITE is sent without an offer to the INVITE-initiating UA. This causes the UA to send an offer which is forwarded to the UA that confirmed the call. The media synchronization process is enabled by the EnableSBCMediaSync parameter. Version 6.6 Mediant 3000...

  • Page 434: Alternative Routing On Detection Of Failed Sip Response

    Mediant 3000 28.11 Alternative Routing on Detection of Failed SIP Response The device can detect failure of a sent SIP response (e.g., TCP timeout, and UDP ICMP). In such a scenario, the device re-sends the response to an alternative destination. This support is in addition to alternative routing if the device detects failed SIP requests.

  • Page 435: Sbc Configuration

    Open the General Settings page (Configuration tab > VoIP menu > SBC > General Settings). Figure 29-1: General Settings Page Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 520. Version 6.6 Mediant 3000...

  • Page 436: Configuring Admission Control

    Mediant 3000 29.2 Configuring Admission Control The Admission Control page allows you to define up to 100 rules for limiting the number of concurrent calls (SIP dialogs). These call limits can be applied per SRD, IP Group, SIP request type (e.g., INVITEs), SIP dialog direction (e.g., inbound), and/or per user (identified by its registered contact).
  • Page 437  [0] All = (Default) Includes the total number of all dialogs.  [1] INVITE  [2] SUBSCRIBE  [3] Other Request Direction Defines the direction of the SIP request to which the rule applies. Version 6.6 Mediant 3000...

  • Page 438: Configuring Allowed Coder Groups

    Mediant 3000 Parameter Description  [SBCAdmissionControl [0] Both = (Default) Rule applies to inbound and outbound SIP _RequestDirection] dialogs.  [1] Inbound = Rule applies only to inbound SIP dialogs.  [2] Outbound = Rule applies only to outbound SIP dialogs.
  • Page 439 From the 'Allowed Coders Group ID' drop-down list, select an ID for the Allowed Coder Group. In the Coder Name table, select coders for the Allowed Coder Group. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 520. Version 6.6 Mediant 3000...

  • Page 440: Routing Sbc

    Mediant 3000 29.4 Routing SBC This section describes the configuration of the routing entities for the SBC application. These include the following:  Classification rules - see 'Configuring the Classification Rules' on page  Condition rules - see 'Configuring Condition Rules' on page ...
  • Page 441 'Classification Failure Response Type' parameter in the SIP Interface table (see 'Configuring SIP Interface Table' on page 227). The flowchart below illustrates the classification process: Figure 29-4: Classification Process (Identifying IP Group or Rejecting Call) Version 6.6 Mediant 3000...
  • Page 442 Mediant 3000 Notes: • Incoming REGISTER messages are saved in the device’s registration database and sent to a destination only if they are associated with a source User-type IP Group. • The Classification table can also be configured using the table ini file parameter, Classification.
  • Page 443 If this routing rule is not required, leave the field empty. The asterisk (*) symbol can be used to depict any source host prefix. Note: For REGISTER requests, the source URL is obtained from the To header. Version 6.6 Mediant 3000...

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

    Mediant 3000 Parameter Description Destination Username Defines the prefix of the destination Request-URI user part of the Prefix incoming SIP dialog. Note: The prefix can be a single digit or a range of digits. For available [Classification_DestUs notations, see 'Dialing Plan Notation for Routing and Manipulation' on ernamePrefix] page 641.

  • Page 445: Configuring Condition Rules

    For a detailed description of the syntax for configuring SIP message manipulation rules, refer to SIP Message Manipulations Quick Reference Guide. • The Condition table can also be configured using the table ini file parameter, ConditionTable. Version 6.6 Mediant 3000...

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

    Mediant 3000  To configure Condition rules: Open the Condition Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Condition Table). Click the Add button; the following dialog box appears: Figure 29-6: Condition Table Page - Add Record Dialog Box Configure the rule as required.
  • Page 447 Inputs' are used. The alternative routes rules can be set to enforce the input matching criteria or to ignore any matching criteria. Alternative routing occurs upon one of the following conditions: • A request sent by the device is responded with one of the following: Version 6.6 Mediant 3000...
  • Page 448 Mediant 3000 ♦ SIP response code (i.e., 4xx, 5xx, and 6xx SIP responses) configured in the SBC Alternative Routing Reasons table (see 'Configuring Alternative Routing Reasons' on page 453). ♦ SIP 408 Timeout or no response (after timeout). • The DNS resolution includes IP addresses that the device has yet to try (for the current call).
  • Page 449 Request URI) user part. You can use special notations for denoting [IP2IPRouting_DestUse the prefix. For example, to denote any prefix, use the asterisk (*) symbol; rnamePrefix] to denote calls without a user part in the URI, use the $ sign. For Version 6.6 Mediant 3000...
  • Page 450 Mediant 3000 Parameter Description available notations, see 'Dialing Plan Notation for Routing and Manipulation' on page 641. The default is * (i.e., any prefix). Destination Host Defines the host part of the incoming SIP dialog’s destination URI [IP2IPRouting_DestHos (usually the Request-URI). If this rule is not required, leave the field empty.
  • Page 451 SRD is determined according to the source SRD associated with the Source IP Group (configured in the IP Group table, see 'Configuring IP Groups' on page 230). If this table does not Version 6.6 Mediant 3000...
  • Page 452 Mediant 3000 Parameter Description define an IP Group but only an SRD, then the first IP Group associated with this SRD (in the IP Group table) is used.  If the selected destination IP Group ID is type SERVER, the request is routed according to the IP Group addresses.

  • Page 453: Configuring Alternative Routing Reasons

    Alternative routing rules are configured in the IP-to-IP Routing table where the 'Alternative Route Options' parameter is set to Alt Route Ignore Inputs or Alt Route Consider Inputs. For more information, see 'Configuring SBC IP-to-IP Routing' on page 446. Version 6.6 Mediant 3000...
  • Page 454 Mediant 3000 Notes: • Alternative routing occurs even if this table is not configured upon scenarios where no response, ICMP, or a SIP 408 response is received. • SIP requests pertaining to an SRD or IP Group that reach the call limit...

  • Page 455: Sbc Manipulations

    IP Groups respectively (if any, in the IP Group table). Below is an example of a call flow and consequent SIP URI manipulations:  Incoming INVITE from LAN: INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 Via: SIP/2.0/UDP 10.2.2.6;branch=z9hGLLLLLan From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe To: <sip:1000@10.2.2.3;user=phone> Call-ID: USELLLAN@10.2.2.3 Version 6.6 Mediant 3000...
  • Page 456 Mediant 3000 CSeq: 1 INVITE Contact: <sip:7000@10.2.2.3> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 ...

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

    This manipulation can be done for source or destination IP Groups (see 'Configuring IP Groups' on page 230). • The IP to IP Inbound Manipulation table can also be configured using the table ini file parameter, IPInboundManipulation. Version 6.6 Mediant 3000...
  • Page 458 Mediant 3000  To configure IP-to-IP inbound manipulation rules: Open the IP to IP Inbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Inbound). Click the Add button; the following dialog box appears:...
  • Page 459 For example, if you enter 3 and the user name is "john", the new [IPInboundManipulatio n_RemoveFromRight] user name is "j". Note: If both 'Remove From Right' and 'Leave From Right' parameters are configured, the 'Remove From Right' setting is applied first. Version 6.6 Mediant 3000...

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

    Mediant 3000 Parameter Description Leave From Right Defines the number of characters that you want retained from the right of [IPInboundManipulatio the user name. n_LeaveFromRight] Note: If both 'Remove From Right' and 'Leave From Right' parameters are configured, the 'Remove From Right' setting is applied first.
  • Page 461 URI (either source or destination) to the rule configured in the row above (configured by the 'Manipulated URI' parameter). Source IP Group ID Defines the IP Group from where the INVITE is received. [IPOutboundManipulati For any Source IP Group, enter the value -1. on_SrcIPGroupID] Version 6.6 Mediant 3000...
  • Page 462 Mediant 3000 Parameter Description Destination IP Group ID Defines the IP Group to where the INVITE is to be sent. [IPOutboundManipulati For any Destination IP Group, enter the value -1. on_DestIPGroupID] Source Username Prefix Defines the prefix of the source SIP URI user name (usually in the From [IPOutboundManipulati header).
  • Page 463 The device identifies an incoming user as restricted if one of the following exists:  From header user is anonymous.  P-Asserted-Identity and Privacy headers contain the value "id". Note: All restriction logic is performed after the user number has been manipulated. Version 6.6 Mediant 3000...
  • Page 464 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 465: Stand-Alone Survivability Application

    Part VII Stand-Alone Survivability Application...

  • Page 467: 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 469. Note: It is recommended to implement the SAS outbound mode. Version 6.6 Mediant 3000...

  • Page 468: Sas Outbound Mode

    Mediant 3000 30.1.1 SAS Outbound Mode This section describes the SAS outbound mode, which includes the following states:  Normal state (see 'Normal State' on page 468)  Emergency state (see 'Emergency State' on page 468) 30.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 469: Sas Redundant Mode

    UAs, you can configure 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 3000...

  • Page 470: Normal State

    Mediant 3000 30.1.2.1 Normal State In normal state, the UAs register and operate directly with the external proxy. Figure 30-3: SAS Redundant Mode in Normal State (Example) 30.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 471: Sas Routing

    30.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 30-5: Flowchart of INVITE from UA's in SAS Normal State Version 6.6 Mediant 3000...
  • Page 472 Mediant 3000 The flowchart below displays the routing logic for SAS in normal state for INVITE messages received from the external proxy: Figure 30-6: Flowchart of INVITE from Primary Proxy in SAS Normal State User's Manual Document #: LTRT-89729...

  • Page 473: Sas Routing In Emergency State

    User's Manual 30. Overview 30.2.2 SAS Routing in Emergency State The flowchart below shows the routing logic for SAS in emergency state: Figure 30-7: Flowchart for SAS Emergency State Version 6.6 Mediant 3000...
  • Page 474 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 475: 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 476 Mediant 3000  To configure common SAS settings: Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand Alone Survivability). Define the port used for sending and receiving SAS messages. This can be any of the following port types: •...
  • Page 477 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 31-2: Defining SAS Proxy Server Click Submit to apply your settings. Version 6.6 Mediant 3000...

  • Page 478: Configuring Sas Outbound Mode

    Mediant 3000 31.2 Configuring SAS Outbound Mode This section describes how to configure the SAS outbound mode. These settings are in addition to the ones described in 'Configuring Common SAS Parameters' on page 475. Note: The VoIP CPEs (such as IP phones or residential gateways) need to be...

  • Page 479: Configuring Gateway Application With Sas

    Figure 31-3: Enabling Proxy Server for Gateway Application Click Submit. Open the Proxy Sets Table page (Configuration tab > VoIP menu > Control Network submenu > Proxy Sets Table). From the 'Proxy Set ID' drop-down list, select 0. Version 6.6 Mediant 3000...
  • Page 480 Mediant 3000 In the first 'Proxy Address' field, enter the IP address and port of the device (in the format x.x.x.x:port). This is the port as defined in the 'SAS Local UDP/TCP/TLS Port' field (see 'Configuring Common SAS Parameters' on page 475).

  • Page 481: Gateway With Sas Redundant Mode

    This is the same port as defined in the 'SAS Local UDP/TCP/TLS Port' field (see 'Configuring Common SAS Parameters' on page 475). From the 'Proxy Redundancy Mode' drop-down list, select Homing. Figure 31-7: Defining Proxy Servers for Gateway Application Click Submit. Version 6.6 Mediant 3000...

  • Page 482: Advanced Sas Configuration

    Mediant 3000 Disable the use of user=phone in the SIP URL: Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions submenu > General Parameters). From the 'Use user=phone in SIP URL' drop-down list, select No. This instructs the Gateway application not to use user=phone in SIP URL and therefore, REGISTER and INVITE messages use SIP URI.

  • Page 483: Manipulating Destination Number Of Incoming Invite

    To overcome this and successfully route the call, you can define manipulation rules to change the INVITE's destination number so that it matches that of the registered user in the database. This is done using the IP to IP Inbound Manipulation table. Version 6.6 Mediant 3000...
  • Page 484 Mediant 3000 For example, in SAS emergency state, assume an incoming INVITE has a destination number "7001234" which is destined to a user registered in the SAS database as "552155551234". In this scenario, the received destination number needs to be manipulated to the number "552155551234".
  • Page 485 For example, if you enter 3 and the user name is "john", the new n_RemoveFromRight] user name is "j". Note: If both 'Remove From Right' and 'Leave From Right' parameters are configured, the 'Remove From Right' setting is applied first. Version 6.6 Mediant 3000...

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

    Mediant 3000 Parameter Description Leave From Right Defines the number of characters that you want retained from the right of [IPInboundManipulatio the user name. n_LeaveFromRight] Note: If both 'Remove From Right' and 'Leave From Right' parameters are configured, the 'Remove From Right' setting is applied first.
  • Page 487 For example, to denote any prefix, use the asterisk (*) symbol; to denote calls without a user part in the URI, use the $ sign. For available notations, see 'Dialing Plan Notation for Routing and Manipulation' on page 641. Version 6.6 Mediant 3000...
  • Page 488 Mediant 3000 Parameter Description The default is * (i.e., any prefix). Source Host Defines the host part of the incoming SIP dialog's source URI (usually [IP2IPRouting_SrcHost the From URI). If this rule is not required, leave the field empty. To denote any host name, use the asterisk (*) symbol (default).
  • Page 489 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 3000...
  • Page 490 Mediant 3000 Parameter Description table, see 'Configuring IP Groups' on page 230). 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 491: 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 3000...

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

    Mediant 3000 In the 'SAS Emergency Numbers' field, enter an emergency number in each field box. Figure 31-10: Configuring SAS Emergency Numbers Click Submit to apply your changes. 31.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 493: Replacing Contact Header For Sip Messages

    'SAS/SBC Registered Users page, as described in 'Viewing Registered Users' on page 585. Note: You can increase the maximum number of registered SAS users, by implementing the SAS Cascading feature, as described in 'SAS Cascading' on page 495. Version 6.6 Mediant 3000...
  • Page 494 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 495: Sas Cascading

    SAS Routing table. In this example, a call is routed from SAS Gateway (A) user to a user on SAS Gateway (B). Figure 32-1: SAS Cascading Using SAS Routing Table - Example  SAS Redundancy mode: If users cannot be distinguished (i.e., associated to a Version 6.6 Mediant 3000...
  • Page 496 Mediant 3000 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. Each SAS gateway serves as the redundant SAS gateway (“redundant SAS proxy server”) for the previous SAS gateway (in a one-way...

  • Page 497: Ip Media Capabilities

    Part VIII IP Media Capabilities...

  • Page 499: 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 Note: This feature is supported only by Mediant 3000 Simplex (not HA). Version 6.6 Mediant 3000...

  • Page 500: Using Rfc 4240 - Netann 2-Party Conferencing

    Mediant 3000 33.2 Using RFC 4240 - NetAnn 2-Party Conferencing Transcoding bridges (or translates) between two remote network locations, each of which uses a different coder and/or a different DTMF and fax transport types. The device supports IP-to-IP transcoding. It creates a transcoding call that is similar to a dial-in, two- party conference call.

  • Page 501: High Availability System

    Part IX High Availability System...

  • Page 503: Ha Overview

    User's Manual 34. HA Overview HA Overview The High Availability architecture of the Mediant 3000 provides the following main functionality:  Redundant Active/Standby configuration  Support for both TP-6310 and TP-8410 blades  One or many global device IP addresses ...

  • Page 504: Initialization Process

    Mediant 3000 The RTMs on the rear of the chassis is according to implemented blade:  TP-8410: the RTM-8410 is located in Slot 2. The RTM-8410 connects to Trunks 1 through 42 (or 1 through 16). The PSTN and Gigabit Ethernet (GbE) interfaces are connected to the active VoP blade in Slot 1 of the front panel.

  • Page 505: Configuration Stages

    OAMP interface. This allows the device's blade to send reports to a Syslog server in case of major device failure.  The Mediant 3000 HA is loaded from flash (when loading from BootP/TFTP on first configuration setup, HA is disabled). Version 6.6 Mediant 3000...

  • Page 506: Blade Failure Detection

    Mediant 3000 34.3 Blade Failure Detection Upon detection of a blade failure, the following occurs:  Active blade failure: the redundant (standby) blade issues a switch-over operation. As part of this switch-over operation, the failed blade is reset and the previously redundant blade becomes the active blade in Simplex mode until a redundant blade is detected.

  • Page 507: Network Interfaces For Ha

    Active module in Slot 1 and the Redundant module in Slot 3). Each blade in the Mediant 3000 system boots as standalone. The blade is also assigned its own private address (which may have been acquired via BootP/DHCP or configured manually) which is used for maintenance only (prior to entering HA mode).
  • Page 508 211.211.85.1 Private IP Addresses of the Blades 192.168.85.15 Blade in Slot 1 (received from BootP) 192.168.85.16 Blade in Slot 3 (received from BootP) Example of Multiple Interfaces for Mediant 3000 HA in Multiple Interface Table Application Interface Prefix VLAN Interface...

  • Page 509: Physical Network Separation Mode

    Physical Network Separation can be configured in the Web (or by using the ini file parameter EnableNetworkPhysicalSeparation). Notes: • Physical Network Separation is supported only for Mediant 3000 housing TP-8410. • Physical Network Separation supports three interfaces (OAMP, Control, and Media) and all three must be configured when operating in Physical Network Separation mode.
  • Page 510 Mediant 3000 For more information on cabling these interfaces, refer to the Hardware Installation Manual. The figure below illustrates the connectivity of the device when operating in network physical interfaces separation mode. Figure 36-1: Separate Physical Network Interfaces User's Manual...

  • Page 511: Configuring Physical Network Separation

    Verify that the Syslog displays the following message: "Updating Flash to work in Network Separation Mode in the next Boot". If the Mediant 3000 is in High Availability (HA) mode, remove the blade that you configured above, and then repeat steps 1 through 5 for the second blade (using the identical ini file).

  • Page 512: Disabling Physical Network Separation

    Verify that the Syslog displays the following message: "Updating Flash to work in Non Network Separation Mode in the next Boot". If the Mediant 3000 is in High Availability (HA) mode, remove the blade that you configured above, insert the second blade, and then repeat steps 1 through 6 for the second blade (using the identical ini file).

  • Page 513: Viewing Ha Status On Home Page

    VoIP blades (TP-6310 or TP-8410) and two SA/M3K Alarms, Status and Synchronization ("SAT") blades, as shown in the figure below: Figure 37-1: Home Page for Mediant 3000 HA Device The status of the HA mode is indicated in the General Information pane: ...
  • Page 514 Mediant 3000 The Active blade is indicated by the following:  The darker-shaded blade in the graphical display of the device's chassis.  The color of the ACT icon: • (gray): Single blade (i.e., Simplex mode) • (green): Active blade (HA mode) •...

  • Page 515: Maintenance

    Part X Maintenance...

  • Page 517: Basic Maintenance

    'Toolbar Description' on page 48) 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 50). Version 6.6 Mediant 3000...

  • Page 518: Remotely Resetting Device Using Sip Notify

    Mediant 3000  To reset the device: Open the Maintenance Actions page (see 'Basic Maintenance' on page 517). 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 519: 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. 38.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 520: Saving Configuration

    Mediant 3000  To unlock the device: Open the Maintenance Actions page (see 'Maintenance Actions' on page 517). 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 67).

  • Page 521: 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 3000...
  • Page 522 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 523: High Availability Maintenance

    Under the 'Switch Over' group, click Switch Over; a confirmation box appears requesting you to confirm. Click OK.  To reset the Redundant blade: Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK. Version 6.6 Mediant 3000...
  • Page 524 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 525: 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 3000...
  • Page 526 Mediant 3000 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 527: 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 528 Mediant 3000 Signal Off time' should be specified. All other on and off periods must be set to zero. 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.

  • Page 529: Prerecorded Tones File

    Prerecorded Tones (PRT) file can be used. If a specific prerecorded tone exists in the PRT file, it takes precedence over the same tone that exists in the CPT file and is played instead of it. Version 6.6 Mediant 3000...

  • Page 530: 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 525). 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 531: 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 525.
  • Page 532 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 525.

  • Page 533: 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 3000...
  • Page 534 Mediant 3000  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 535: Obtaining Ip Destination From Dial Plan File

    The second number must always be set to "0".  The third number is a string of up to 12 characters containing the mapped number that is used as the URI user part in the From and Contact headers of the outgoing INVITE. Version 6.6 Mediant 3000...

  • Page 536: User Information File

    855)  Automatic update mechanism - using the UserInfoFileURL parameter, e.g., UserInfoFileUrl = 'http://192.168.0.250/Audiocodes/ UserInformationFile.txt' (see 'Automatic Update Mechanism' on page 553) 41.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 537 'Registration Mode' parameter set to Per Endpoint (AuthenticationMode is set to 0). The User Info file is a text-based file that you can create using any text-based program such as Notepad. To add mapping rules to this file, use the following syntax: Version 6.6 Mediant 3000...

  • Page 538: User Information File For Sbc User Database

    Mediant 3000 [ 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  DisplayName is the Caller ID (string of up to 30 characters) of the PBX extension ...

  • Page 539: 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 540 Mediant 3000 <NUMBEROFLEVELS>8</NUMBEROFLEVELS> <AMDSENSITIVITYLEVEL> <!-- Level 0 --> <AMDCOEFFICIENTA>15729</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>58163</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>32742</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 1 --> <AMDCOEFFICIENTA>19923</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>50790</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>30720</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 2 --> <AMDCOEFFICIENTA>10486</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>57344</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>25600</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL> <!-- Level 3 --> <AMDCOEFFICIENTA>8389</AMDCOEFFICIENTA> <AMDCOEFFICIENTB>62259</AMDCOEFFICIENTB> <AMDCOEFFICIENTC>23040</AMDCOEFFICIENTC> </AMDSENSITIVITYLEVEL> <AMDSENSITIVITYLEVEL>...
  • Page 541 User's Manual 41. Software Upgrade <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> </PARAMETERSUIT> </AMDSENSITIVITY> Version 6.6 Mediant 3000...

  • Page 542: 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 543: 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 544: Installing Software License Key Using Web Interface

    Mediant 3000 41.2.2.1 Installing Software License Key using Web Interface The procedure below describes how to install the Software License Key using the Web interface.  To install the Software License Key using the Web interface: Open the Software Upgrade Key Status page (Maintenance tab > Software Update menu >...

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

    "[LicenseKeys]". Verify that the content of the file has not been altered. 41.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 546: Software Upgrade Wizard

    (see 'Basic Maintenance' on page 517). 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 547 If you want to load only a .cmp file, then click the Reset button to reset the device with the newly loaded .cmp file, utilizing the existing configuration (ini) and auxiliary files. To load additional files, skip to the next Step. Version 6.6 Mediant 3000...
  • Page 548 Mediant 3000 Note: Device reset may take a few minutes depending on cmp file version (this may even take up to 10 minutes). Click the Next button; the wizard page for loading an ini file appears. You can now perform one of the following: •...

  • Page 549: Hitless Software Upgrade

    Click OK; the Web interface becomes active, reflecting the upgraded device. 41.3.1 Hitless Software Upgrade The Mediant 3000 HA system allows you to upgrade the software (SW) version (i.e., cmp file) running on the device without disrupting current calls. This non-affecting traffic upgrade feature is referred to as Hitless Software Upgrade.
  • Page 550 Mediant 3000 Both blades now operate with the new SW version and a switchback is issued to return the system to its original state. The previously Active blade now becomes active, and the previously Redundant blade resets once more to return to redundant state.

  • Page 551: Backing Up And Loading Configuration File

    Click the Load INI File button, and then at the prompt, click OK; the device uploads the ini file and then resets (from the cmp version stored on the flash memory). Once complete, the Web Login screen appears, requesting you to enter your user name and password. Version 6.6 Mediant 3000...
  • Page 552 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 553: 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 3000...
  • Page 554 Mediant 3000 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 555: Obtaining An Ip Address Using Dhcp

    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. For each device, preconfigure the following parameter (DHCP / DNS are assumed): IniFileURL = 'http://www.corp.com/master_configuration.ini' Version 6.6 Mediant 3000...
  • Page 556 Mediant 3000 Create a file named master_configuration.ini with the following text: # Common configuration for all devices # ------------------------------------ CptFileURL = 'http://www.corp.com/call_progress.dat' # Check for updates every 60 minutes AutoUpdateFrequency = 60 # Additional configuration per device # ----------------------------------- # Each device loads a file named based on its MAC address # (e.g., config_00908F033512.ini)

  • Page 557: 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 558: 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; 42.4.3 Configuration using DHCP Option 67 This method is suitable for deployments where DHCP server configuration is possible at the customer site.

  • Page 559: Tftp Configuration Using Dhcp Option 66

    42.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 560: Configuration Using Ftp Or Nfs

    NFS v2/v3 is also supported. 42.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 561: Loading Files Securely (Disabling Tftp)

    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. Version 6.6 Mediant 3000...
  • Page 562 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 563: Restoring Factory Defaults

    Restoring Defaults using CLI The device can be restored to factory defaults using CLI, as described in the procedure below. Note: Restoring factory defaults using CLI is supported only by Mediant 3000 Simplex.  To restore factory defaults using CLI:...

  • Page 564: Restoring Defaults Using An Ini File

    Mediant 3000 43.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 551).

  • Page 565: Status, Performance Monitoring And Reporting

    Part XI Status, Performance Monitoring and Reporting...

  • Page 567: System Status

    Ethernet port connections. This includes information such as activity status, duplex mode, and speed. Note: The Ethernet Port Information page also be accessed from the Home page (see 'Viewing the Home Page' on page 67). Version 6.6 Mediant 3000...
  • Page 568 Open the Ethernet Port Information page (Status & Diagnostics tab > System Status menu > Ethernet Port Information). When Physical Network Separation is enabled on Mediant 3000 with TP-8410 (using the parameter EnableNetworkPhysicalSeparation - see Networking Parameters on page 643),...

  • Page 569: Viewing Timing Module Information

    This page appears only if the device is in HA mode.  To view the timing module information:  Open the Timing Module Information page (Status & Diagnostics tab > VoIP Status menu > Timing Module Information). Figure 44-2: Timing Module Information Page Version 6.6 Mediant 3000...

  • Page 570: Viewing Hardware Components Status

    Mediant 3000 44.4 Viewing Hardware Components Status The Components Status page provides read-only, real-time status of the device's chassis components such as slot occupants, fans, and power supply units. Note: You can also access this page from the Home page (see 'Viewing the Home Page' on page 67).

  • Page 571: Carrier-Grade Alarms

    Open the Alarms History page (Status & Diagnostics tab > System Status menu > Carrier-Grade Alarms > Alarms History). For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) Version 6.6 Mediant 3000...
  • Page 572 Mediant 3000 • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised  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.

  • Page 573: 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 3000...

  • Page 574: Viewing Trunk Utilization

    Mediant 3000 46.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. Notes: •...
  • Page 575 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 3000...

  • Page 576: Viewing Quality Of Experience

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

  • Page 577: Viewing Average Call Duration

    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 3000...
  • Page 578 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 579: Voip Status

    Trunk Icon Color Label Description Description Gray Disabled Disabled Disabled Green Active - OK No Alarms (Working) No Alarms Yellow RAI Alarm No Alarms RAI Alarm (Protection) LOS / LOF Alarm LOS/LOF/MS- LOS/LOF/AIS Alarm AIS/MS-RDI Alarm Version 6.6 Mediant 3000...
  • Page 580 Mediant 3000 Icon Color Trunk Blue AIS Alarm Light Orange D-Channel Alarm DS3 Not Configured Dark Orange NFAS Alarm 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...

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

    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 47-3: NFAS Group & D-Channel Status Page Version 6.6 Mediant 3000...

  • Page 582: Viewing Active Ip Interfaces

    Mediant 3000 47.3 Viewing Active IP Interfaces The IP Interface Status page displays the device's active IP interfaces that are listed in the Multiple Interface Table page (see 'Configuring IP Network Interfaces' on page 116).  To view the active IP network interfaces: ...
  • Page 583 Number of Calls Indicates the number of calls that failed as a result of a busy line. It is Terminated due to a incremented as a result of the following release reason: Busy Line GWAPP_USER_BUSY (17) Version 6.6 Mediant 3000...
  • Page 584 Mediant 3000 Counter Description Number of Calls Indicates the number of calls that weren't answered. It's incremented Terminated due to No as a result of one of the following release reasons: Answer  GWAPP_NO_USER_RESPONDING (18)  GWAPP_NO_ANSWER_FROM_USER_ALERTED (19)  GWAPP_NORMAL_CALL_CLEAR (16) (when the call duration is...

  • Page 585: Viewing Registered Users

    "NO"= Registration is not per device  Accounts Registration Status: registration status based on the Accounts table (configured in 'Configuring Account Table' on page 243): • Group Type: type of served group - Trunk Group or IP Group Version 6.6 Mediant 3000...

  • Page 586: Viewing Call Routing Status

    Mediant 3000 • Group Name: name of the served group, if applicable • Status: indicates whether or not the group is registered ("Registered" or "Unregistered") Note: The registration mode (i.e., per device, endpoint, account. or no registration) is configured in the Trunk Group Settings table (see 'Configuring Trunk Group Settings' on page 327) or using the TrunkGroupSettings ini file parameter.

  • Page 587: Viewing Ip Connectivity

    Method periodically (ICMP ping or SIP OPTIONS request). Connectivity The status of the IP address' connectivity according to the method in the Status 'Connectivity Method' field.  OK = Remote side responds to periodic connectivity queries. Version 6.6 Mediant 3000...
  • Page 588 Mediant 3000 Column Name Description  Lost = Remote side didn't respond for a short period.  Fail = Remote side doesn't respond.  Init = Connectivity queries not started (e.g., IP address not resolved).  Disable = The connectivity option is disabled, i.e., parameter 'Alt Routing Tel to IP Mode' (AltRoutingTel2IPMode ini) is set to 'None' or 'QoS'.

  • Page 589: 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 3000...
  • Page 590 Mediant 3000 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 591 '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 3000...

  • Page 592: Generating Call Detail Records

    Mediant 3000 48.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 593: Cdr Field Description

    Destination UDP port DestPort TransportType Transport type:    SrcURI Source URI SrcURIBeforeMap Source URI before manipulation DstURI Destination URI DstURIBeforeMap Destination URI before manipulation Durat Call duration TrmSd Termination side (local or remote) Termination reason TrmReason Version 6.6 Mediant 3000...
  • Page 594 Mediant 3000 CDR Field Name Description TrmReasonCategory Termination reason category:  Calls with duration 0 (i.e., not connected):  NO_ANSWER - GWAPP_NORMAL_CALL_CLEAR, GWAPP_NO_USER_RESPONDING, GWAPP_NO_ANSWER_FROM_USER_ALERTED  BUSY - GWAPP_USER_BUSY  NO_RESOURCES - GWAPP_RESOUUCE_UNAVAILABLE_UNSPECIFIED, RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES _LEFT, RESOURCE_BECAUSE_NO_TRANSCODING_RESOURC ES_LEFT, RELEASE_BECAUSE_GW_LOCKED  NO_MATCH - RELEASE_BECAUSE_UNMATCHED_CAPABILITIES ...

  • Page 595: Cdr Fields For Sbc Media

    |SIPInterfaceId |ProxySetId |IpProfileId (name) |MediaRealmId (name) |DirectMedia |SIPTrmReason [S=3] |CALL_END |SBC |170369730753201211288@10.132.10.245 |0 |RMT |10.132.10.245 |5060 |10.132.10.250 |5070 |UDP |103@audiocodes.com |103@audiocodes.com |101@10.132.10.250 |101@10.132.10.250 |0 |RMT |GWAPP_NORMAL_CALL_CLEAR |NO_ANSWER |06:13:54.950 UTC Thu Mar 02 2012 | |06:14:01.175 UTC Thu Mar 02 2012 |-1 | | |40 |2 () |0 (5070SRD) |2 |3 |0 () |0 (lanmedia) |no |CANCEL 48.2.2.2 CDR Fields for SBC Media...

  • Page 596: Cdr Fields For Gateway/Ip-To-Ip Application

    Mediant 3000 CDR Field Name Description OutPackets Number of sent packets LocalPackLoss Local packet loss RemotePackLoss Remote packet loss RTPdelay RTP delay RTPjitter RTP jitter TxRTPssrc Tx RTP SSRC RxRTPssrc Local RTP SSRC LocalRFactor Local conversation quality RemoteRFactor Remote conversation quality...
  • Page 597 RtpIp Port Remote RTP port TrmSd Initiator of call release (IP, Tel, or Unknown) TrmReason SIP call termination reason (see 'Release Reasons in CDR' on page 600) Fax transaction during call InPackets Number of incoming packets Version 6.6 Mediant 3000...
  • Page 598 Mediant 3000 Field Name Description OutPackets Number of outgoing packets PackLoss Local packet loss Number of outgoing lost packets RemotePackLoss SIPCalld Unique SIP call ID SetupTime Call setup time ConnectTime Call connect time ReleaseTime Call release time RTPdelay RTP delay...
  • Page 599 Information relating to the Automatic Machine Detection (AMD) feature:  V - voice  A - answer machine  S - silence  U - unknown Information relating to AMD that shows the success that the answering type (probability) was correctly detected Version 6.6 Mediant 3000...

  • Page 600: Release Reasons In Cdr

    Mediant 3000 Field Name Description SIPTrmReason SIP call termination reason (BYE, CANCEL, or SIP error codes, e.g., 404) SipTermDesc Description of SIP termination reason:  SIP Reason header, if exists, for example: SIP ;cause=200 ;text="Call completed elsewhere".  If no SIP Reason header exists, the description is taken from the reason text, if exists, of the SIP response code, for example: "417...
  • Page 601 "GWAPP_NETWORK_OUT_OF_ORDER"  "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" Version 6.6 Mediant 3000...
  • Page 602 Mediant 3000  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS"  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST"  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED"  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING"  "GWAPP_MESSAGE_TYPE_NON_EXISTENT"...

  • Page 603: Configuring Radius Accounting

    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 h323- SIP call identifier Up to 32 Start Acc incoming- octets Stop Acc Version 6.6 Mediant 3000...
  • Page 604 Mediant 3000 Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. conf-id h323-remote- IP address of the Numeric Stop Acc address remote gateway h323-conf-id H.323/SIP call Up to 32 Start Acc identifier octets Stop Acc h323-setup-...
  • Page 605 Below is an example of RADIUS Accounting, where the non-standard parameters are preceded with brackets: Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213 nas-port-type = 0 acct-status-type = 2 acct-input-octets = 4841 acct-output-octets = 8800 acct-session-time = 1 acct-input-packets = 122 acct-output-packets = 220 Version 6.6 Mediant 3000...

  • Page 606: Event Notification Using X-Detect Header

    Mediant 3000 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 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP...
  • Page 607 The absence of the X-Detect header indicates that no detections are available. Each time the device detects a supported event, the event is notified to the remote party by sending an INFO message with the following message body: • Content-Type: application/X-DETECT Version 6.6 Mediant 3000...

  • Page 608: Querying Device Channel Resources Using Sip Options

    Mediant 3000 • 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 Max-Forwards: 70 From: "anonymous"...

  • Page 609: Diagnostics

    Part XII Diagnostics...

  • Page 611: 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 3000...

  • Page 612: Event Representation In Syslog Messages

    Mediant 3000 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 613 Packet Header Error RTP Packet Loss Counts the number of BFI Frames Received From The Host No Available Release Descriptor RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Version 6.6 Mediant 3000...

  • Page 614: Unique Device Identification In Syslog Messages

    Invalid Routing Flag Received 49.1.2 Unique Device Identification in Syslog Messages The Syslog messages include a unique string to identify the device. Mediant 3000 High Availability (HA) main operations and events are sent to the Syslog with the prefix "M3K_HA". All Syslog messages and events of the redundant TP-6310 blade are sent to the Syslog by the active TP-6310 blade with the "Redundant module message"...

  • Page 615: Syslog Fields For Automatic Machine Detection

    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 616: Configuring Syslog Settings

    Mediant 3000 49.2 Configuring Syslog Settings The procedure below describes how to configure Syslog. This includes defining the Syslog server address as well as selecting the activities on the device (for example, a parameter value change) that you want reported to the server.

  • Page 617: Configuring Debug Recording

    Syslog messages for IP Groups 1 through 4. For each filter criteria, you can enable or disable Syslog messages and debug recording. Debug recording can also be filtered using various filtering criteria such as SIP signaling or signaling and media. Version 6.6 Mediant 3000...
  • Page 618 Mediant 3000  To configure logging filtering rules: Open the Logging Filters Table page (Configuration tab > System menu > Logging > Logging Filters Table). Click the Add button; the Add Record dialog box appears: Figure 49-2: Logging Filters Table - Add Record Dialog Box Configure the logging filter, as required.

  • Page 619: Filtering Ip Network Traces

    When the IP Trace option is selected, only the ‘Value’ parameter is applicable; the 'Syslog' and 'Capture Type' parameters are not relevant. The 'Value' parameter configures the Wireshark-like filtering expressions for your IP trace. The following Wireshark-like expressions are supported: Version 6.6 Mediant 3000...
  • Page 620 Mediant 3000 Supported Wireshark-like Expressions for 'Value' Parameter Expression Description ip.src, ip.dst Source and destination IP address ip.addr IP address - up to two IP addresses can be entered ip.proto IP protocol type (PDU) entered as an enumeration value (e.g., 1 is ICMP, 6 is TCP, 17 is UDP)

  • Page 621: Viewing Syslog Messages

    You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting.  To activate the Web interface's Message Log: Enable Syslog (see 'Configuring Syslog' on page 616).

  • Page 622: Collecting Debug Recording Messages

    Mediant 3000 49.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: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...
  • Page 623 User's Manual 49. Syslog and Debug Recordings 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 624 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 625: 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 3000...
  • Page 626 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 627: 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 662).
  • Page 628 Mediant 3000 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 629 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 3000...

  • Page 630: Starting, Stopping And Restarting Test Calls

    Mediant 3000 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 631: 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 3000...

  • Page 632: Configuring Dtmf Tones For Test Calls

    Mediant 3000  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 630).

  • Page 633: Configuring Basic Test Call

    For a full description of this parameter, see 'SIP Test Call Parameters' on page 662. • This call test is done on all SIP interfaces. • This call test is applicable only to the Gateway/IP-to-IP application. Version 6.6 Mediant 3000...

  • Page 634: Configuring Sbc Test Call With External Proxy

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

  • Page 635: Test Call Configuration Examples

    Figure 51-8: Single Test Call Example • Test Call table configuration: ♦ Endpoint URI: "101" ♦ Called URI: "201" ♦ Route By: Dest Address Version 6.6 Mediant 3000...
  • Page 636 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 637 Called URI: "itsp" ♦ Route By: Dest Address ♦ Destination Address: "10.13.4.12" (this is the IP address of the device itself) ♦ Auto Register: Enable ♦ User Name: "testuser" ♦ Password: "12345" ♦ Call Party: Caller Version 6.6 Mediant 3000...
  • Page 638 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 639: Appendix

    Part XIII Appendix...

  • Page 641: 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 3000...
  • Page 642 Mediant 3000 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 643: Configuration Parameters Reference

    This table parameter configures the Multiple Interface table. The format Table of this parameter is as follows: EMS: IP Interface [InterfaceTable] Settings FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, [InterfaceTable] InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingInterface; Version 6.6 Mediant 3000...
  • Page 644  For this parameter to take effect, a device reset is required.  This parameter is applicable only to Mediant 3000 with TP-8410.  When the parameter is enabled, user VLANs are not supported (i.e., VlANMode is set to 1).

  • Page 645: Routing Parameters

    [0] Disable = (Default) ICMP Redirect messages are handled by the device.  [1] Enable = ICMP Redirect messages are ignored. Static IP Routing Table Web/EMS: IP Routing Defines up to 30 static IP routing rules for the device. These rules can Version 6.6 Mediant 3000...

  • Page 646: Quality Of Service Parameters

    Mediant 3000 Parameter Description Table be associated with IP interfaces defined in the Multiple Interface table [StaticRouteTable] (InterfaceTable parameter). The routing decision for sending the 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.
  • Page 647 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 3000...

  • Page 648: Nat And Stun Parameters

    Mediant 3000 53.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 649: 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. NFS Table Version 6.6 Mediant 3000...

  • Page 650: Dns Parameters

    Mediant 3000 Parameter Description 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 651: 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 3000...

  • Page 652: Ntp And Daylight Saving Time Parameters

    Mediant 3000 53.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 111.

  • Page 653: 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 3000...
  • Page 654 Mediant 3000 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 655 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 63. Version 6.6 Mediant 3000...
  • Page 656 Mediant 3000 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 657: 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 3000...
  • Page 658 Mediant 3000 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 659 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 3000...

  • Page 660: Serial Parameters

    Mediant 3000 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 95.

  • Page 661: Debugging And Diagnostics Parameters

    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 3000...

  • Page 662: Sip Test Call Parameters

    Mediant 3000 53.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 663: Syslog, Cdr And Debug Parameters

    [3] Connect & End Call = CDR report is sent to Syslog at connection and at the end of each call.  [4] Start & End & Connect Call = CDR report is sent to Syslog at Version 6.6 Mediant 3000...
  • Page 664 Mediant 3000 Parameter Description the start, at connection, and at the end of each call. Notes:  For the SBC application, this parameter enables only signaling- related CDRs. To enable media-related CDRs for SBC calls, use the MediaCDRReportLevel parameter. ...
  • Page 665  (2) Subnet Mask  (3) Default Gateway IP Address  (4) ActivityListToLog  [ll] Login and Logout = Every login and logout attempt. For example: ActivityListToLog = 'pvc', 'afl', 'dr', 'fb', 'swu', 'ard', 'naa', 'spc' Version 6.6 Mediant 3000...

  • Page 666: Heartbeat Packet Parameters

    Mediant 3000 Parameter Description Note: For the ini file, values must be enclosed in single quotation marks. Enables ISDN traces of Facility Information Elements (IE) for ISDN call [FacilityTrace] diagnostics. This allows you to trace all the parameters contained in the Facility IE and view them in the Syslog.

  • Page 667: Resource Allocation Indication Parameters

    The BootP parameters are described in the table below. The BootP parameters are special 'hidden' parameters. Once defined and saved in the device's flash memory, they are used even if they don't appear in the ini file. Version 6.6 Mediant 3000...
  • Page 668 Mediant 3000 BootP Parameters Parameter Description [BootPRetries] Note: For this parameter to take effect, a device reset is required. This parameter is used to: Defines the number of BootP Defines the number of DHCP requests that the device sends packets that the device sends. If during start-up.

  • Page 669: Security Parameters

    ‘mgmt.customer.com’ destined to TCP ports 0 to 80 on interface OAMP (OAMP). Rule #22 blocks traffic from the subnet 10.4.xxx.yyy destined to ports 4000 to 9000. Note: For a description of this table, see 'Configuring Firewall Settings' on page 145. Version 6.6 Mediant 3000...

  • Page 670: Https Parameters

    Mediant 3000 53.4.2 HTTPS Parameters The Secure Hypertext Transport Protocol (HTTPS) parameters are described in the table below. HTTPS Parameters Parameter Description Web: Secured Web Determines the protocol used to access the Web interface. Connection (HTTPS)  [0] HTTP and HTTPS (default).

  • Page 671: Srtp Parameters

    [3] Preferable - Single Media = The device sends SDP with a single media ('m=') line only (e.g., m=audio 6000 RTP/AVP 4 0 70 96) with RTP/AVP and crypto keys. The remote UA can respond with SRTP or Version 6.6 Mediant 3000...
  • Page 672 Mediant 3000 Parameter Description RTP parameters:  If the remote SIP UA does not support SRTP, it uses RTP and ignores the crypto lines.  In the opposite direction, if the device receives an SDP offer with a single media (as shown above), it responds with SRTP (RTP/SAVP) if the EnableMediaSecurity parameter is set to 1.
  • Page 673 Enables authentication on transmitted RTP packets in a secured RTP Authentication On session. Transmitted RTP  [0] Enable (default) Packets  [1] Disable EMS: RTP AuthenticationDisable Tx [RTPAuthenticationDis ableTx] Web: Disable Encryption Enables encryption on transmitted RTP packets in a secured RTP On Transmitted RTP Version 6.6 Mediant 3000...

  • Page 674: Tls Parameters

    Mediant 3000 Parameter Description Packets session. EMS: RTP  [0] Enable (default) EncryptionDisable Tx  [1] Disable [RTPEncryptionDisable Web: Disable Encryption Enables encryption on transmitted RTCP packets in a secured RTP On Transmitted RTCP session. Packets  [0] Enable (default) EMS: RTCP ...
  • Page 675 Defines the Subject Name that is compared with the name defined in the Subject Name remote side certificate when establishing TLS connections. [TLSRemoteSubjectNa If the SubjectAltName of the received certificate is not equal to any of the defined Proxies Host names/IP addresses and is not marked as 'critical', Version 6.6 Mediant 3000...

  • Page 676: Ssh Parameters

    Mediant 3000 Parameter Description the Common Name (CN) of the Subject field is compared with this value. If not equal, the TLS connection is not established. If the CN uses a domain name, the certificate can also use wildcards (‘*’) to replace parts of the domain name.

  • Page 677: Ipsec Parameters

    Internet Key Exchange (IKE) and IP Security (IPSec) EMS: IPSec SA Table protocols. You can define up to 20 IPSec peers. [IPSecSATable] The format of this parameter is as follows: [ IPsecSATable ] FORMAT IPsecSATable_Index = IPsecSATable_RemoteEndpointAddressOrName, Version 6.6 Mediant 3000...

  • Page 678: Ocsp Parameters

    Mediant 3000 Parameter Description IPsecSATable_AuthenticationMethod, IPsecSATable_SharedKey, IPsecSATable_SourcePort, IPsecSATable_DestPort, IPsecSATable_Protocol, IPsecSATable_Phase1SaLifetimeInSec, IPsecSATable_Phase2SaLifetimeInSec, IPsecSATable_Phase2SaLifetimeInKB, IPsecSATable_DPDmode, IPsecSATable_IPsecMode, IPsecSATable_RemoteTunnelAddress, IPsecSATable_RemoteSubnetIPAddress, IPsecSATable_RemoteSubnetPrefixLength, IPsecSATable_InterfaceName; [ \IPsecSATable ] For example: IPsecSATable 1 = 0, 10.3.2.73, 0, 123456789, 0, 0, 0, 0, 28800, 3600, ; In the above example, a single IPSec/IKE peer (10.3.2.73) is configured.

  • Page 679: Ids Parameters

    The format of the ini file parameter is: [ IDSPolicy ] FORMAT IDSPolicy_Index = IDSPolicy_Name, IDSPolicy_Description; [ \IDSPolicy ] For a detailed description of this table, see 'Configuring IDS Policies' on page 157. IDS Rule Table Version 6.6 Mediant 3000...

  • Page 680: Radius Parameters

    Mediant 3000 Parameter Description Web: IDS Rule Table Defines rules for the IDS Policies. [IDSRule] The format of the ini file parameter is: [ IDSRule ] FORMAT IDSRule_Index = IDSRule_Policy, IDSRule_RuleID, IDSRule_Reason, IDSRule_ThresholdScope, IDSRule_ThresholdWindow, IDSRule_MinorAlarmThreshold, IDSRule_MajorAlarmThreshold, IDSRule_CriticalAlarmThreshold; [ \IDSRule ] For a detailed description of this table, see 'Configuring IDS Policies' on page 157.
  • Page 681 (authentication) response doesn't include an access level attribute. [DefaultAccessLevel] The valid range is 0 to 255. The default is 200 (i.e., Security Administrator). Web: Device Behavior Defines the device's response upon a RADIUS timeout. Upon RADIUS Timeout Version 6.6 Mediant 3000...

  • Page 682: Sip Media Realm Parameters

    Mediant 3000 Parameter Description  [BehaviorUponRadiusTi [0] Deny Access = Denies access. meout]  [1] Verify Access Locally = (Default) Checks password locally. Web: Local RADIUS Determines the device's mode of operation regarding the timer Password Cache Mode (configured by the parameter RadiusLocalCacheTimeout) that...
  • Page 683 For a detailed description of this table, see 'Configuring Bandwidth Management per Media Realm' on page 200. Quality of Experience Parameters Web: Server IP Defines the IP address of AudioCodes Session Experience Manager CLI: server-ip (SEM) server to where the quality experience reports are sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
  • Page 684 Mediant 3000 Parameter Description Web: Connection Mode Defines the connection between the device and the SEM. [QOEConnectionMode]  [0] Server = The device receives connection from the server.  [1] Client (default) = The device connects to the SEM. ...

  • Page 685: Control Network Parameters

    Enables the use of a SIP proxy server. EMS: Proxy Used  [0] No = (Default) Proxy isn't used and instead, the internal routing [IsProxyUsed] table is used.  [1] Yes = Proxy server is used. Define the IP address of the proxy Version 6.6 Mediant 3000...
  • Page 686 Mediant 3000 Parameter Description server in the Proxy Sets table (see 'Configuring Proxy Sets Table' on page 238). Notes:  If you are not using a proxy server, you must define outbound IP call routing rules in the Outbound IP Routing Table (described in Configuring Outbound IP Routing Table on page 355).
  • Page 687 Enables the use of DNS Naming Authority Pointer (NAPTR) and Type Service Record (SRV) queries to resolve Proxy and Registrar servers [DNSQueryType] and to resolve all domain names that appear in the SIP Contact and Record-Route headers.  [0] A-Record (default) Version 6.6 Mediant 3000...
  • Page 688 Mediant 3000 Parameter Description  [1] SRV  [2] NAPTR If set to A-Record [0], no NAPTR or SRV queries are performed. If set to SRV [1] and the Proxy/Registrar IP address parameter, Contact/Record-Route headers, or IP address defined in the Routing tables contain a domain name, an SRV query is performed.
  • Page 689  [2] Full = Caches all challenges from the proxies. Notes:  This parameter is applicable only to the Gateway IP-to-IP application.  Challenge Caching is used with all proxies and not only with the Version 6.6 Mediant 3000...
  • Page 690 Mediant 3000 Parameter Description active one. Proxy IP Table Web: Proxy IP Table This table parameter configures the Proxy Set table with Proxy Set IDs, EMS: Proxy IP each with up to five Proxy server IP addresses (or fully qualified domain [ProxyIP] name/FQDN).
  • Page 691 EnableProxyKeepAlive is set to 2 (REGISTER). Typically, the device registers every 3,600 sec (i.e., one hour). The device resumes registration according to the parameter RegistrationTimeDivider. The valid range is 10 to 2,000,000. The default is 180. Version 6.6 Mediant 3000...
  • Page 692 Mediant 3000 Parameter Description Web: Re-registration Defines the re-registration timing (in percentage). The timing is a Timing [%] percentage of the re-register timing set by the Registrar server. EMS: Time Divider The valid range is 50 to 100. The default is 50.
  • Page 693 Use of the "*" Contact header field value allows a registering UA to remove all bindings associated with an address-of-record (AOR) without knowing their precise values. Note: The REGISTER-specific Contact header field value of "*" applies Version 6.6 Mediant 3000...
  • Page 694 Mediant 3000 Parameter Description to all registrations, but it can only be used if the Expires header field is present with a value of "0". Web/EMS: Add Empty Enables the inclusion of the SIP Authorization header in initial Authorization Header registration (REGISTER) requests sent by the device.

  • Page 695: Network Application Parameters

    TCP, and TLS) and associated with a specific IP interface and an SRD [SIPInterface] ID. The format of this parameter is as follows: [SIPInterface] FORMAT SIPInterface_Index = SIPInterface_NetworkInterface, SIPInterface_ApplicationType, SIPInterface_UDPPort, SIPInterface_TCPPort, SIPInterface_TLSPort, SIPInterface_SRD, SIPInterface_MessagePolicy, SIPInterface_TLSMutualAuthentication, SIPInterface_TCPKeepaliveEnable, SIPInterface_ClassificationFailureResponseType; Version 6.6 Mediant 3000...
  • Page 696 Mediant 3000 Parameter Description [\SIPInterface] Note: For a detailed description of this table, see 'Configuring SIP Interface Table' on page 227. TCP Keep Alive Idle Time Defines the interval (in sec) between the last data packet sent and the first keep-alive probe to send.

  • Page 697: 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 698 Mediant 3000 Parameter Description [MaxActiveCalls] the maximum number of calls). Web: QoS statistics in SIP Enables the device to include call quality of service (QoS) statistics in Release Call SIP BYE and SIP 200 OK response to BYE, using the proprietary SIP [QoSStatistics] header X-RTP-Stat.
  • Page 699 SIP 183 upon receipt of an ISDN Call Proceeding message.  This feature can also be configured in an IP Profile. [IgnoreAlertAfterEarlyM Determines the device's interworking of Alerting messages from PRI to edia] SIP.  [0] = Disabled (default)  [1] = Enabled Version 6.6 Mediant 3000...
  • Page 700 Mediant 3000 Parameter Description When enabled, if the device sends a 183 response with an SDP (due to a received ISDN Progress or Proceeding with PI messages) and an Alerting message is then received from the Tel side (with or without Progress Indicator), the device does not send an additional 18x response, and the voice channel remains open.
  • Page 701 [2] G.711 Transport = Initiates fax/modem using the coder G.711 A- law/Mu-law with adaptations (see Note below).  [3] Fax Fallback = Initiates T.38 fax relay. If the T.38 negotiation fails, the device re-initiates a fax session using the coder G.711 A- Version 6.6 Mediant 3000...
  • Page 702 Mediant 3000 Parameter Description law/µ-law with adaptations (see the Note below). Notes:  Fax adaptations (for options 2 and 3):  Echo Canceller = On  Silence Compression = Off  Echo Canceller Non-Linear Processor Mode = Off  Dynamic Jitter Buffer Minimum Delay = 40 ...
  • Page 703 Enables the reuse of the same TCP connection for all calls to the same Connection Reuse destination. [EnableTCPConnection  [0] Disable = Uses a separate TCP connection for each call. Reuse]  [1] Enable = (Default) Uses the same TCP connection for all calls. Version 6.6 Mediant 3000...
  • Page 704 Mediant 3000 Parameter Description Notes:  This parameter must be left at its default value (and not set to 0).  For the SAS application, this feature is configured using the SASConnectionReuse parameter. Web: Fake TCP alias Enables the re-use of the same TCP/TLS connection for sessions with [FakeTCPalias] the same user, even if the "alias"...
  • Page 705 Upon receiving a request with History-Info, the UAS checks the policy in the request. If a 'session', 'header', or 'history' policy tag is found, the (final) response is sent without History-Info; otherwise, it is copied from the request. Version 6.6 Mediant 3000...
  • Page 706 Mediant 3000 Parameter Description Web: Use Tgrp Determines whether the SIP 'tgrp' parameter is used. This SIP Information parameter specifies the Trunk Group to which the call belongs EMS: Use SIP Tgrp (according to RFC 4904). For example, the SIP message below...
  • Page 707 Group ID 56: INVITE sip:123456@192.168.1.2;dtg=56;user=phone SIP/2.0 Note: If the Trunk Group is not found based on the 'dtg' parameter, the Inbound IP Routing Table is used instead for routing the call to the appropriate Trunk Group. Version 6.6 Mediant 3000...
  • Page 708 Mediant 3000 Parameter Description Web/EMS: Enable GRUU Determines whether the Globally Routable User Agent URIs (GRUU) [EnableGRUU] mechanism is used, according to RFC 5627. This is used for obtaining a GRUU from a registrar and for communicating a GRUU to a peer within a dialog.
  • Page 709 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 3000/v.6.40.010.006 The maximum string length is 50 characters. Note: The software version number and preceding forward slash (/) cannot be modified.
  • Page 710 Mediant 3000 Parameter Description application. Web: Send All Coders on Enables coder re-negotiation in the sent re-INVITE for retrieving an on- Retrieve hold call. [SendAllCodersOnRetri  [0] Disable = (Default) Sends only the initially chosen coder when eve] the call was first established and then put on-hold.
  • Page 711 'id', the calling number is assumed restricted. Determines the SIP header used for obtaining the called number [SelectSourceHeaderFor (destination) for IP-to-Tel calls. CalledNumber]  [0] Request-URI header = (Default) Obtains the destination number from the user part of the Request-URI. Version 6.6 Mediant 3000...
  • Page 712 Mediant 3000 Parameter Description  [1] To header = Obtains the destination number from the user part of the To header.  [2] P-Called-Party-ID header = Obtains the destination number from the P-Called-Party-ID header. Web/EMS: Forking Determines how the device handles the receipt of multiple SIP 18x Handling Mode forking responses for Tel-to-IP calls.
  • Page 713 IP address, reflected in the From header of the SIP INVITE. Therefore, even customers blocking their Caller ID can be identified by the service provider. Typically, if the device receives a call with blocked Caller ID Version 6.6 Mediant 3000...
  • Page 714 Mediant 3000 Parameter Description from the PSTN side (e.g., Trunk connected to a PBX), it sends an INVITE to the IP with a From header as follows: From: “anonymous” <anonymous@anonymous.invalid>. This is in accordance with RFC 3325. However, when this parameter is set to 1, the device replaces the "anonymous.invalid"...
  • Page 715 'Transparent' (even if the coder is not included in the coder list). The initiated INVITE includes the following SDP attribute: a=rtpmap:97 CLEARMODE/8000 The default payload type is set according to the CodersGroup Version 6.6 Mediant 3000...
  • Page 716 Mediant 3000 Parameter Description parameter. If the Transparent coder is not defined, the default is set to 56. The payload type is negotiated with the remote side, i.e., the selected payload type is according to the remote side selection. The receiving device must include the 'Transparent' coder in its coder list.
  • Page 717 [1] Enable = If all the trunks pertaining to Trunk Group #1 are down or busy, the device does not respond to received SIP OPTIONS. Web: Comfort Noise Enables negotiation and usage of Comfort Noise (CN). Generation Negotiation  [0] Disable EMS: Comfort Noise Version 6.6 Mediant 3000...
  • Page 718 Mediant 3000 Parameter Description  Generation [1] Enable (default) [ComfortNoiseNegotiati The use of CN is indicated by including a payload type for CN on the media description line of the SDP. The device can use CN with a codec whose RTP time stamp clock rate is 8,000 Hz (G.711/G.726). The static payload type 13 is used.
  • Page 719 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). Version 6.6 Mediant 3000...
  • Page 720 Mediant 3000 Parameter Description Web/EMS: Media IP Determines the preferred RTP media IP addressing version for outgoing Version Preference SIP calls. This is indicated in the "c=" field (Connection Information) of [MediaIPVersionPrefere the SDP. nce]  [0] Only IPv4 = (Default) offer includes only IPv4 media IP addresses.
  • Page 721 To configure the method for setting digital trunks to Out-Of-Service, use the DigitalOOSBehavior parameter. Web/EMS: Graceful Busy Defines the timeout interval (in seconds) for Out-of-Service graceful Out Timeout [sec] shutdown mode for busy trunks (per trunk) if communication fails with a Version 6.6 Mediant 3000...
  • Page 722 Mediant 3000 Parameter Description [GracefulBusyOutTimeo Proxy server (or Proxy Set). In such a scenario, the device rejects new calls from the PSTN (Serving Trunk Group), but maintains currently active calls for this user-defined timeout. Once this timeout elapses, the device terminates currently active calls and takes the trunk out of service (sending the PSTN busy-out signal).
  • Page 723 This table parameter configures SIP message policy rules for blocking Table (blacklist) unwanted incoming SIP messages or allowing (whitelist) [MessagePolicy] receipt of desired messages.The format of this parameter is as follows: [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Policy, MessagePolicy_MaxMessageLength, Version 6.6 Mediant 3000...

  • Page 724: Coders And Profile Parameters

    Mediant 3000 Parameter Description 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'. 53.9 Coders and Profile Parameters The profile parameters are described in the table below.
  • Page 725 (which are typically configured separately Telephony Profile using their individual, "global" parameters). You can later assign these [TelProfile] Tel Profile IDs to other elements such as in the Trunk Group TableEndpoint Phone Number table (TrunkGroup parameter). Therefore, Version 6.6 Mediant 3000...
  • Page 726 Mediant 3000 Parameter Description 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,...

  • Page 727: Channel Parameters

    The voice parameters are described in the table below. Voice Parameters Parameter Description Web/EMS: Input Gain Defines the pulse-code modulation (PCM) input gain control (in [InputGain] decibels). This parameter sets the level for the received (PSTN- to-IP) signal. Version 6.6 Mediant 3000...
  • Page 728 Mediant 3000 Parameter Description 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. Web: Voice Volume Defines the voice gain control (in decibels). This parameter sets EMS: Volume (dB) the level for the transmitted (IP-to-PSTN) signal.
  • Page 729 [3] = 3 dB EMS: ECN lp Mode Defines the echo cancellation Non-Linear Processing (NLP) [ECNLPMode] mode.  [0] = (Default) NLP adapts according to echo changes  [1] = Disables NLP  [2] = Silence output NLP Version 6.6 Mediant 3000...

  • Page 730: Coder Parameters

    Mediant 3000 Parameter Description Note: This parameter can also be configured in a Tel Profile. Enables the Aggressive NLP at the first 0.5 second of the call. [EchoCancellerAggressiveNLP  [0] = Disable  [1] = (Default) Enable. The echo is removed only in the first half of a second of the incoming IP signal.
  • Page 731 Determines the format of the RTP header for VBR coders. Format  [0] = (Default) Payload only (no header, TOC, or m-factor) - [VBRCoderHeaderFormat] similar to RFC 3558 Header Free format.  [1] = Supports RFC 2658 - 1 byte for interleaving header Version 6.6 Mediant 3000...
  • Page 732 Mediant 3000 Parameter Description (always 0), TOC, no m-factor.  [2] = Payload including TOC only, allow m-factor.  [3] = RFC 3558 Interleave/Bundled format. EMS: VBR Coder Hangover Defines the required number of silence frames at the beginning of...

  • Page 733: Dtmf Parameters

    The valid range is -10 to 10 dB. The default is 0 dB. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 3000...

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

    Mediant 3000 Parameter Description EMS: DTMF Inter Interval Defines the time (in msec) between generated DTMF digits to (msec) PSTN side (if TxDTMFOption = 1, 2 or 3). [DTMFInterDigitInterval] The default is 100 msec. The valid range is 0 to 32767.
  • Page 735 PT value for both parties. Web: RFC 2198 Payload Type Defines the RTP redundancy packet payload type according to EMS: Redundancy Payload RFC 2198. Type The range is 96 to 127. The default is 104. [RFC2198PayloadType] Version 6.6 Mediant 3000...
  • Page 736 Mediant 3000 Parameter Description Note: This parameter is applicable only if the parameter 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.
  • Page 737 The range of possible UDP ports is 6,000 to 64,000. The default base UDP port is 6000. Once this parameter is configured, the UDP port range (lower to upper boundary) is calculated as follows:  Mediant 3000/TP-6310: BaseUDPport to (BaseUDPport + 4031*10)  Mediant 3000/TP-8410: BaseUDPport to (BaseUDPport + 4031*10) Notes: ...
  • Page 738 Mediant 3000 Parameter Description Disables RTCP traffic when there is no RTP traffic. This feature is [RTCPActivationMode] useful, for example, to stop RTCP traffic that is typically sent when calls are put on hold (by an INVITE with 'a=inactive' in the SDP).

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

    EMS: V22 Transport  [2] Enable Bypass (default) [V22ModemTransportType]  [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. Version 6.6 Mediant 3000...
  • Page 740 Mediant 3000 Parameter Description  Type [0] Disable = Disable (Transparent) EMS: V23 Transport  [2] Enable Bypass (default) [V23ModemTransportType]  [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.
  • Page 741 [5] 14400 = 14.4 kbps (maximum for T38 Version 0)  [6] 16800bps = 16.8 kbps  [7] 19200bps = 19.2 kbps  [8] 21600bps = 21.6 kbps  [9] 24000bps = 24 kbps  [10] 26400bps = 26.4 kbps Version 6.6 Mediant 3000...
  • Page 742 Mediant 3000 Parameter Description  [11] 28800bps = 28.8 kbps  [12] 31200bps = 31.2 kbps  [13] 33600bps = 33.6 kbps (default) Notes:  The rate is negotiated between both sides (i.e., the device adapts to the capabilities of the remote side). Negotiation of the T.38 maximum supported fax data rate is provided in SIP’s...
  • Page 743  Set the Modem transport type to Bypass mode (VxxModemTransportType is set to 2) for all modems.  Configure the gateway parameter NSEPayloadType = 100.  This parameter can also be configured in an IP Profile. Version 6.6 Mediant 3000...
  • Page 744 Mediant 3000 Parameter Description EMS: NSE Payload Type Defines the NSE payload type for Cisco Bypass compatible mode. [NSEPayloadType] The valid range is 96-127. The default is 105. Note: Cisco gateways usually use NSE payload type of 100. EMS: T38 Use RTP Port...
  • Page 745 The range is 132 to 256. The default is 132. el2MaxPayloadSize] Web: SPRT Transport Ch.2 Defines the maximum window size of SPRT transport channel 2. Max Window Size The value range is 8 to 32. The default is 8. [V1501SPRTTransportChann el2MaxWindowSize] Version 6.6 Mediant 3000...

  • Page 746: Dtmf And Hook-Flash Parameters

    Mediant 3000 Parameter Description Web: SPRT Transport Ch.3 Defines the maximum payload size for V.150.1 SPRT Transport Max Payload Size Channel 3. [V1501SPRTTransportChann The range is 140 to 256. The default is 140. el3MaxPayloadSize] 53.11.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below.
  • Page 747 When out-of-band DTMF transfer is used ([1], [2], [3], or [5]), the parameter DTMFTransportType is automatically set to 0 (DTMF digits are erased from the RTP stream).  When RFC 2833 (4) is selected, the device: Negotiates RFC 2833 payload type using local and remote Version 6.6 Mediant 3000...
  • Page 748 Mediant 3000 Parameter Description SDPs. Sends DTMF packets using RFC 2833 payload type according to the payload type in the received SDP. Expects to receive RFC 2833 packets with the same payload type as configured by the parameter RFC2833PayloadType. Removes DTMF digits in transparent mode (as part of the voice stream).

  • Page 749: Digit Collection And Dial Plan Parameters

    The valid value range is 0 to 7, defining the Dial Plan index [Plan x] in the Dial Plan file. The default is -1 (disabled). For more information on this feature, see 'Modifying ISDN-to-IP Calling Party Number' on page 535. Version 6.6 Mediant 3000...
  • Page 750 Mediant 3000 Parameter Description Web: Digit Mapping Rules Defines the digit map pattern (used to reduce the dialing period EMS: Digit Map Pat terns when ISDN overlap dialing). If the digit string (i.e., dialed number) [DigitMapping] matches one of the patterns in the digit map, the device stops collecting digits and establishes a call with the collected number.

  • Page 751: Voice Mail Parameters

    >> 302 Others >> 302 If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason. Version 6.6 Mediant 3000...
  • Page 752 Mediant 3000 Parameter Description [WaitForBusyTime] Defines the time (in msec) that the device waits to detect busy and/or reorder tones. This feature is used for semi-supervised PBX call transfers (i.e., the LineTransferMode parameter is set to 2). The valid value range is 0 to 20000 (i.e., 20 sec). The default is 2000 (i.e., 2 sec).
  • Page 753 Defines the digit pattern used by the PBX to indicate 'call forward on Digit Pattern (Internal) busy' when the original call is received from an internal extension. EMS: Digit Pattern The valid range is a 120-character string. Forward On Busy [DigitPatternForwardOn Busy] Version 6.6 Mediant 3000...
  • Page 754 Mediant 3000 Parameter Description Web: Forward on No Defines the digit pattern used by the PBX to indicate 'call forward on Answer Digit Pattern no answer' when the original call is received from an internal (Internal) extension. EMS: Digit Pattern The valid range is a 120-character string.

  • Page 755: Supplementary Services Parameters

    Privacy header includes the value 'id' ('Privacy: id'). Otherwise, for allowed Caller ID, 'Privacy: none' is used. If Caller ID is restricted (received from PSTN / Tel or configured in the device), the From header is set to <anonymous@anonymous.invalid>. Version 6.6 Mediant 3000...
  • Page 756 Mediant 3000 Parameter Description The 200 OK response can contain the connected party CallerID - Connected Number and Connected Name. For example, if the call is answered by the device, the 200 OK response includes the P- Asserted-Identity with Caller ID. The device interworks (in some ISDN variants), the Connected Party number and name from Q.931 Connect...

  • Page 757: Call Waiting Parameters

    [1] Enable (default) Notes:  To support interworking of the Hold/Retrieve supplementary service from SIP to ISDN (Euro ISDN), set the parameter EnableHold2ISDN to 1.  This parameter can also be configured in an IP Profile. Version 6.6 Mediant 3000...

  • Page 758: Call Transfer Parameters

    Mediant 3000 Parameter Description Web/EMS: Hold Format Determines the format of the SDP in the Re-INVITE hold request. [HoldFormat]  [0] 0.0.0.0 = (Default) The SDP "c=" field contains the IP address "0.0.0.0" and the "a=inactive" attribute.  [1] Send Only = The SDP "c=" field contains the device's IP address and the "a=sendonly"...
  • Page 759 Redirection Number, the Calling Number is replaced with the received redirect number in the sent INVITE message. If the timeout expires, the device sends the INVITE without changing the calling number. Notes: Version 6.6 Mediant 3000...

  • Page 760: Mlpp And Emergency Call Parameters

    Mediant 3000 Parameter Description  The suspension of the INVITE message occurs for all calls.  This parameter is applicable to QSIG. Web: IP2IP Transfer Determines the interworking of incoming mid-call SIP REFER messages Mode to outgoing REFER messages, for calls pertaining to the IP-to-IP [IP2IPTransfermode] application.
  • Page 761 Defines up to 32 user-defined MLPP network domain names rkDomains] (namespaces). This value is used in the AS-SIP Resource-Priority header of the outgoing SIP INVITE request. This parameter is used in combination with the MLPPDefaultNamespace parameter, where you Version 6.6 Mediant 3000...
  • Page 762 Mediant 3000 Parameter Description need to enter the table row index as its value. This parameter is also used for mapping the Resource-Priority field value of the SIP Resource-Priority header to the ISDN PRI Precedence Level IE. The mapping is configured by the field, EnableIp2TelInterworking: ...
  • Page 763  [1] Enable = (Default) Adds the SIP resource-priority tag in the SIP Require header. Note: This parameter is applicable only to MLPP priority call handling (i.e., only when the CallPriorityMode parameter is set to 1). Version 6.6 Mediant 3000...
  • Page 764 Mediant 3000 Parameter Description Multiple Differentiated Services Code Points (DSCP) per MLPP Call Priority Level (Precedence) Parameters The MLPP service allows placement of priority calls, where properly validated users can preempt (terminate) lower-priority phone calls with higher-priority calls. For each MLPP call priority level, the DSCP can be set to a value from 0 to 63.

  • Page 765: Call Cut-Through Parameters

    RTP packets (per the selected bypass coder), but with a different RTP payload type (103). You can change this payload type by using the ModemBypassPayloadType parameter. When TTY Version 6.6 Mediant 3000...

  • Page 766: Pstn Parameters

    Mediant 3000 Parameter Description signal transmission ends, reverse switching from bypass coder to regular voice coder is performed.  [2] = Relay (signals sent over the EVRC/B or AMR codec) - TTY phone device transfer using In-Band Relay mode for TTY signal transport.
  • Page 767 Notes:  For this parameter to take effect, a device reset is required.  When both the parameters ISDNDmsTimerT310 and ISDNTimerT310 are configured, the value of the parameter ISDNTimerT310 prevails. Version 6.6 Mediant 3000...
  • Page 768 Mediant 3000 Parameter Description [ISDNDMSTimerT310] Defines the override T310 timer for the DMS-100 ISDN variant. T310 defines the timeout between the receipt of a Proceeding message and the receipt of an Alerting/Connect message. The valid range is 10 to 30. The default is 10 (seconds).
  • Page 769 When the device is locked from the Web interface, this parameter changes to 0.  To define the administrative state per trunk, use the TrunkAdministrativeState parameter. [TrunkAdministrativeState_x Defines the administrative state per trunk, where x denotes the Version 6.6 Mediant 3000...
  • Page 770 Mediant 3000 Parameter Description trunk number.  [0] = Lock the trunk; stops trunk traffic to configure the trunk protocol type.  [1] = shutting down (read only).  [2] = (Default) Unlock the trunk; enables trunk traffic. Web/EMS: Line Build Out Overwrites the Framer's XPM register values.

  • Page 771: Tdm Bus And Clock Timing Parameters

    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 Note: This parameter is applicable only if the parameter Version 6.6 Mediant 3000...
  • Page 772 Mediant 3000 Parameter Description TDMBusClockSource is set to 4 and the parameter TDMBusPSTNAutoClockEnable is set to 0. Web/EMS: TDM Bus Enable Defines the automatic fallback of the clock. This sets the fallback Fallback clock method between primary and secondary BITS clock [TDMBusEnableFallback] references.
  • Page 773 Synchronization or Line Synchronization modes (refer to the parameter TMMode).  This parameter is applicable to Mediant 3000 systems housing TP-8410 blades. For Mediant 3000 systems housing TP-6310 blades, configure this parameter to [0] to use a 12 ppm reference.
  • Page 774 Mediant 3000 Parameter Description  [1] External = External, where each blade is synchronized from one of the PSTN interfaces (without using the SAT timing module). This must be selected for the BITS Synchronization mode.  [2] LineSync = Line Synchronization mode - synchronizes the device with one of the PSTN interfaces.

  • Page 775: Cas Parameters

    Defines the CAS Dial Plan name per trunk. EMS: Dial Plan Name The range is up to 11 characters. [CASTrunkDialPlanName_x] For example, the below configures E1_MFCR2 trunk with a single protocol (Trunk 5): ProtocolType_5 = 7 CASFileName_0='R2_Korea_CP_ANI.dat' Version 6.6 Mediant 3000...
  • Page 776 Mediant 3000 Parameter Description CASTableIndex_5 = 0 DialPlanFileName = 'DialPlan_USA.dat' CASTrunkDialPlanName_5 = 'AT_T' Note: The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. [CASFileName_x] Defines the CAS file name (e.g., 'E_M_WinkTable.dat') that defines the CAS protocol, where x denotes the CAS file ID (0-7).

  • Page 777: Isdn Parameters

    Description Web: ISDN Termination Side Determines the ISDN termination side. EMS: Termination Side  [0] User side = (Default) ISDN User Termination Equipment [TerminationSide] (TE) side.  [1] Network side = ISDN Network Termination (NT) side. Version 6.6 Mediant 3000...
  • Page 778 Mediant 3000 Parameter Description Note: Select 'User side' when the PSTN or PBX side is configured as 'Network side' and vice versa. If you don't know the device's ISDN termination side, choose 'User side'. If the D- channel alarm is indicated, choose 'Network Side'.
  • Page 779 Progress Indicator (PI=8) in Setup Ack message if an empty called number is received in an incoming Setup message. This option is applicable to the overlap dialing mode. The device also plays a dial tone (for TimeForDialTone) until the next Version 6.6 Mediant 3000...
  • Page 780 Mediant 3000 Parameter Description called number digits are received. By default, this is bit is set.  [2147483648] USER SCREEN INDICATOR = When the device receives two Calling Number IE's in the Setup message, the device, by default, uses only one of the numbers according to the following: ...
  • Page 781 [2] = Data calls with interworking indication use 64 kbps B- channels (physical only).  [8] REVERSE CHAN ALLOC ALGO = Channel ID allocation algorithm.  [16] = The device clears down the call if it receives a NOTIFY Version 6.6 Mediant 3000...
  • Page 782 Mediant 3000 Parameter Description message specifying 'User-Suspended'. A NOTIFY (User- Suspended) message is used by some networks (e.g., in Italy or Denmark) to indicate that the remote user has cleared the call, especially in the case of a long distance voice call.
  • Page 783 QSIG ISDN protocol standard. This is applicable only when configuration is QSI.  [64] NS BEHAVIOUR2 FAC REJECT = When this bit is set, the device answers with a Facility IE message with the Reject Version 6.6 Mediant 3000...

  • Page 784: Ds3 Parameters

    Note: For this parameter to take effect, a device reset is required. 53.11.6.5 DS3 Parameters The DS3 parameters are described in the table below. Note: DS3 interface is applicable only to Mediant 3000 with TP-6310. DS3 Parameters Parameter Description DS3 Settings Table [DS3Config] This table parameter configures the DS3 (T3) interfaces.
  • Page 785 Determines the DS3 interface Administrative status. When the interface Administrative status is set to Down, all 28 underlying [DS3Config_AdminState] DS1 interfaces are unavailable.  [1] Up = (Default) Administrative status Up.  [2] Down = Administrative status Down (currently, not supported). Version 6.6 Mediant 3000...

  • Page 786: Sdh/Sonet Parameters

    Mediant 3000 53.11.6.6 SDH/SONET Parameters The SDH/SONET parameters are described in the table below. Note: SDH/SONET interface is applicable only to Mediant 3000 with TP-6310. SDH/SONET Parameters Parameter Description Web/EMS: Transmission Type Defines the PSTN transmission type for the device.
  • Page 787 Web: APS Direction Mode Determines the Automatic Protection Switch (APS) mode for the EMS: Fiber Group APS fiber group: Direction Mode  [0] = (Default) Unidirectional APS mode. [SDHFbrGrp_APS_DirMode]  [1] = Bidirectional APS mode. Notes: Version 6.6 Mediant 3000...

  • Page 788: Isdn And Cas Interworking Parameters

    Notes:  For this parameter to take effect, a device reset is required.  This parameter is applicable only to Mediant 3000/TP-6310.  This parameter is relevant only when the parameter TDMBusType is set to acFRAMERS (2), and PSTNTransmissionType is set to Optical SONET or SDH Transmission type (1).
  • Page 789 Request-URI.  [2] Through SIP = Interworking of ISDN Overlap Dialing to SIP, based on RFC 3578. The device interworks ISDN to SIP by sending digits each time they are received (from Setup and subsequent Info Version 6.6 Mediant 3000...
  • Page 790 Mediant 3000 Parameter Description Q.931 messages) to the IP, using subsequent SIP INVITE messages. Notes:  When option [2] is configured, you can define the minimum number of overlap digits to collect before sending the first SIP message for routing the call, using the MinOverlapDigitsForRouting parameter.
  • Page 791 To enable this function, set the ISDNDuplicateQ931BuffMode parameter to 128 (i.e., duplicate all messages).  To define the format of encapsulated QSIG messages, use the QSIGTunnelingMode parameter.  Tunneling according to ECMA-355 is applicable to all ISDN variants Version 6.6 Mediant 3000...
  • Page 792 Mediant 3000 Parameter Description (in addition to the QSIG protocol).  For more information on QSIG tunneling, see 'QSIG Tunneling' on page 312. [QSIGTunnelingMode] Defines the format of encapsulated QSIG message data in the SIP message MIME body.  [0] = (Default) ASCII presentation of Q.931 QSIG message.
  • Page 793 Web: Release Cause This table parameter maps ISDN Q.850 Release Causes to SIP Mapping Table responses. EMS: ISDN to SIP The format of this parameter is as follows: Cause Mapping [CauseMapISDN2SIP] [CauseMapISDN2SIP] FORMAT CauseMapISDN2SIP_Index = CauseMapISDN2SIP_IsdnReleaseCause, Version 6.6 Mediant 3000...
  • Page 794 Mediant 3000 Parameter Description CauseMapISDN2SIP_SipResponse; [\CauseMapISDN2SIP] Where,  IsdnReleaseCause = Q.850 Release Cause  SipResponse = SIP Response For example: CauseMapISDN2SIP 0 = 50,480; CauseMapISDN2SIP 0 = 6,406; When a Release Cause is received (from the PSTN side), the device searches this mapping table for a match.
  • Page 795 [0] No PI = PI is not sent to ISDN.  [1] PI = 1; [8] PI = 8: The PI value is sent to PSTN in Q.931/Proceeding and Alerting messages. Typically, the PSTN/PBX cuts through the audio channel without playing local ringback tone, Version 6.6 Mediant 3000...
  • Page 796 Mediant 3000 Parameter Description enabling the originating party to hear remote Call Progress Tones or network announcements. Note: The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Web: Set PI in Rx...
  • Page 797 IP-to-Tel calls. EMS: Enable AOC Determines whether ISDN Advice of Charge (AOC) messages are [EnableAOC] interworked with SIP.  [0] = (Default) Not used.  [1] = AOC messages are interworked to SIP (in receive direction) Version 6.6 Mediant 3000...
  • Page 798 Mediant 3000 Parameter Description and sent to the PSTN in the transmit direction. The device supports both the receipt and sending of ISDN (Euro ISDN) AOC messages:  AOC messages can be received during a call (Facility messages) or at the end of a call (Disconnect or Release messages). The device converts the AOC messages into SIP INFO (during a call) and BYE (end of a call) messages, using a proprietary AOC SIP header.
  • Page 799 PSTN Protocol Transfer Method (Described Below) E1 Euro ISDN [1] ECT [2] or InBand [5] E1 QSIG [21], Single Step Transfer [4], Path T1 QSIG [23] Replacement Transfer [2], or InBand [5] Version 6.6 Mediant 3000...
  • Page 800 Mediant 3000 Parameter Description T1 NI2 ISDN [10], TBCT [2] or InBand [5] T1 4ESS ISDN [11], T1 5ESS 9 ISDN [12] T1 DMS-100 ISDN [14] RTL [2] or InBand [5] T1 RAW CAS [3], T1 [1] CAS NFA DMS-100 or [3] CAS Normal...
  • Page 801 [0] Audio 3.1 (default) [ISDNTransferCapabilit  [1] Speech y_x]  [2] Data Notes:  If this parameter is not configured or is set to -1, Audio 3.1 capability is used.  The Audio 7 option is currently not supported. Version 6.6 Mediant 3000...
  • Page 802 Mediant 3000 Parameter Description  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. [TransferCapabilityFor Defines the ISDN Transfer Capability for data calls. DataCalls]  [0] = (Default) ISDN Transfer Capability for data calls is 64k unrestricted (data).

  • Page 803: Answer And Disconnect Supervision Parameters

    [1] Yes = The device sends a SIP 200 OK (in response to an INVITE Detection message) when speech, fax, or modem is detected. [EnableVoiceDetection]  [0] No = (Default) The device sends a SIP 200 OK only after it completes dialing. Version 6.6 Mediant 3000...
  • Page 804 Mediant 3000 Parameter Description Typically, this feature is used only when early media (enabled using the EnableEarlyMedia parameter) is used to establish the voice path before the call is answered. Notes:  To activate this feature, set the EnableDSPIPMDetectors parameter to 1.
  • Page 805 SIP BYE message to terminate the call. If the alarm is cleared before this timeout expires, the call is not terminated, but continues as normal. The range is 1 to 3600. The default is 0 (20 for E1 and 40 for T1). Version 6.6 Mediant 3000...

  • Page 806: Tone Parameters

    Mediant 3000 Parameter Description Web: Disconnect Call on Determines whether a call is disconnected upon detection of a busy Busy Tone Detection tone (for ISDN). (ISDN)  [0] Disable = (Default) Do not disconnect call upon detection of busy EMS: Isdn Disconnect tone.
  • Page 807 1) If the device receives a 180 Ringing response (with or without SDP) and the LocalISDNRBSource parameter is set to 1, it plays a ringback tone and sends an ISDN Alert with PI = 8 (unless the ProgressIndicator2ISDN_x parameter is configured differently). Version 6.6 Mediant 3000...
  • Page 808 Mediant 3000 Parameter Description 2) If the LocalISDNRBSource parameter is set to 0, the device doesn't play a ringback tone and an Alert message without PI is sent to the ISDN. In this case, the PBX / PSTN plays the ringback tone to the originating terminal.
  • Page 809 (due to a previous 183 early media response or due to an SDP in the current 180 response), the device plays a local ringback tone if there are no prior received RTP packets. The device stops playing the local ringback tone as Version 6.6 Mediant 3000...
  • Page 810 Mediant 3000 Parameter Description soon as it starts receiving RTP packets. At this stage, if the device receives additional 18x responses, it does not resume playing the local ringback tone. Note that for ISDN trunks, this option is applicable only if LocalISDNRBSource is set to 1.

  • Page 811: Tone Detection Parameters

    IP-to-Tel call. To disconnect IP-to-CAS calls when a SIT tone is detected, the following parameters must be configured:  SITDetectorEnable = 1  UserDefinedToneDetectorEnable = 1  DisconnectOnBusyTone = 1 (applicable for busy, reorder, and Version 6.6 Mediant 3000...

  • Page 812: Metering Tone Parameters

    Mediant 3000 Parameter Description SIT tones) Notes:  For this parameter to take effect, a device reset is required.  The IP-to-ISDN call is disconnected on detection of a SIT tone only in call alert state. If the call is in connected state, the SIT does not disconnect the call.

  • Page 813: Trunk Groups And Routing Parameters

    This table parameter configures the rules for channel allocation per EMS: SIP Routing > Hunt Trunk Group. The format of this parameter is as follows: Group [TrunkGroupSettings] [TrunkGroupSettings] FORMAT TrunkGroupSettings_Index = TrunkGroupSettings_TrunkGroupId, TrunkGroupSettings_ChannelSelectMode, TrunkGroupSettings_RegistrationMode, TrunkGroupSettings_GatewayName, TrunkGroupSettings_ContactUser, TrunkGroupSettings_ServingIPGroup, Version 6.6 Mediant 3000...
  • Page 814 Mediant 3000 Parameter Description TrunkGroupSettings_MWIInterrogationType, TrunkGroupSettings_TrunkGroupName; [\TrunkGroupSettings] For example: TrunkGroupSettings 0 = 1, 0, 5, branch-hq, user, 1, 255, ; TrunkGroupSettings 1 = 2, 1, 0, localname, user1, 2, 255, ; Note: For a description of this table, see 'Configuring Trunk Group Settings' on page 327.
  • Page 815 Tel-to-IP and IP-to-IP calls. The format of this parameter is as EMS: SIP Routing > Tel to follows: [PREFIX] [Prefix] FORMAT PREFIX_Index = PREFIX_DestinationPrefix, PREFIX_DestAddress, PREFIX_SourcePrefix, PREFIX_ProfileId, PREFIX_MeteringCode, PREFIX_DestPort, PREFIX_SrcIPGroupID, PREFIX_DestHostPrefix, PREFIX_DestIPGroupID, PREFIX_SrcHostPrefix, PREFIX_TransportType, PREFIX_SrcTrunkGroupID, PREFIX_DestSRD, PREFIX_CostGroup, PREFIX_ForkingGroup; Version 6.6 Mediant 3000...
  • Page 816 Mediant 3000 Parameter Description [\PREFIX] For example: PREFIX 0 = *, domain.com, *, 0, 255, $$, -1, , 1, , -1, -1, -1,,; PREFIX 1 = 20, 10.33.37.77, *, 0, 255, $$, -1, , 2, , 0, -1,,; Note: For a detailed description of this table, see 'Configuring Outbound IP Routing Table' on page 355.
  • Page 817 ISDN Transit Network Selection Information Element (TNS IE) in the outgoing ISDN Setup message (if the EnableCIC parameter is set to 1). The TNS IE identifies the requested transportation networks and allows different providers equal access support, based on customer choice. Version 6.6 Mediant 3000...
  • Page 818 Mediant 3000 Parameter Description For example, as a result of receiving the below INVITE, the destination number after number manipulation is cic+167895550001: INVITE sip:5550001;cic=+16789@172.18.202.60:5060;user=phone SIP/2.0 Note: After the cic prefix is added, the Inbound IP Routing Table can be used to route this call to a specific Trunk Group. The Destination Number IP to Tel Manipulation table must be used to remove this prefix before placing the call to the ISDN.

  • Page 819: Ip Connectivity Parameters

    Web: Max Allowed Packet Defines the packet loss (in percentage) at which the IP connection is Loss for Alt Routing [%] considered a failure and Alternative Routing mechanism is activated. [IPConnQoSMaxAllowed The default is 20%. Version 6.6 Mediant 3000...

  • Page 820: Alternative Routing Parameters

    Mediant 3000 Parameter Description Web: Max Allowed Delay Defines the transmission delay (in msec) at which the IP connection is for Alt Routing [msec] considered a failure and the Alternative Routing mechanism is [IPConnQoSMaxAllowed activated. Delay] The range is 100 to 10,000. The default is 250.
  • Page 821 TCP, if Trunk Group ID 2 is unavailable: ForwardOnBusyTrunkDest 1 = 2, 112@10.13.4.12:5060;transport=tcp; Note: For a detailed description of this table, see 'Alternative Routing to IP Destination upon Busy Trunk' on page 373. Version 6.6 Mediant 3000...

  • Page 822: Number Manipulation Parameters

    Mediant 3000 53.11.13 Number Manipulation Parameters The number manipulation parameters are described in the table below. Number Manipulation Parameters Parameter Description Enables the manipulation of the called party (destination) number [ManipulateIP2PSTNRefer according to the SIP Refer-To header received by the device for TDM (PSTN) blind transfer.
  • Page 823 Tel, the redirect reason is set to the [SetTel2IpRedirectReason value of this parameter before the device sends it on to the IP.  [-1] Not Configured (default)  [0] Unkown  [1] Busy  [2] No Reply  [3] Network Busy Version 6.6 Mediant 3000...
  • Page 824 Mediant 3000 Parameter Description  [4] Deflection  [9] DTE out of Order  [10] Forwarding DTE  [13] Transfer  [14] PickUp  [15] Systematic/Unconditional Web: Send Screening Overrides the calling party's number (CPN) screening indication in the Indicator to IP received ISDN SETUP message for Tel-to-IP calls.
  • Page 825 [AddTrunkGroupAsPrefix  [0] No (default) ToSource]  [1] Yes Web: Replace Empty Determines whether the internal channel number is used as the Destination with B-channel destination number if the called number is missing. Phone Number Version 6.6 Mediant 3000...
  • Page 826 Mediant 3000 Parameter Description  EMS: Replace Empty Dst [0] No (default) With Port Number  [1] Yes [ReplaceEmptyDstWithPo Note: This parameter is applicable only to Tel-to-IP calls and if the rtNumber] called number is missing. [CopyDestOnEmptySourc Determines whether the destination number is copied to the source number if no source number is present, for Tel-to-IP calls.
  • Page 827 Configures rules for manipulating the calling name (caller ID) in the [CallingNameMapIp2Tel] received SIP message for IP-to-Tel calls. This can include modifying or removing the calling name. The format of this table ini file parameter is as follows: [ CallingNameMapIp2Tel ] FORMAT CallingNameMapIp2Tel_Index = CallingNameMapIp2Tel_DestinationPrefix, CallingNameMapIp2Tel_SourcePrefix, Version 6.6 Mediant 3000...
  • Page 828 Mediant 3000 Parameter Description CallingNameMapIp2Tel_CallingNamePrefix, CallingNameMapIp2Tel_SourceAddress, CallingNameMapIp2Tel_RemoveFromLeft, CallingNameMapIp2Tel_RemoveFromRight, CallingNameMapIp2Tel_LeaveFromRight, CallingNameMapIp2Tel_Prefix2Add, CallingNameMapIp2Tel_Suffix2Add; [ \CallingNameMapIp2Tel ] Note: For a detailed description of this table, see 'Configuring SIP Calling Name Manipulation' on page 338. Calling Name Manipulations Tel-to-IP Table This table parameter configures rules for manipulating the calling name [CallingNameMapTel2Ip] (caller ID) for Tel-to-IP calls.
  • Page 829 [PerformAdditionalIP2TEL table (SourceNumberMapIP2Tel parameter). This enables you to SourceManipulation] configure only a few manipulation rules for complex number manipulation requirements (that generally require many rules).  [0] = Disable (default) Version 6.6 Mediant 3000...
  • Page 830 Mediant 3000 Parameter Description  [1] = Enable Source Phone Number Manipulation for Tel-to-IP Calls Table Web: Source Phone This table parameter manipulates the source phone number for Tel-to- Number Manipulation Table IP calls. The format of this parameter is as follows: for Tel >...

  • Page 831: Least Cost Routing Parameters

    The default call cost [RoutingRuleGroups] determines whether routing rules that are not configured with a Cost Group are considered as a higher or lower cost route compared to other matching routing rules that are assigned Cost Groups. Version 6.6 Mediant 3000...

  • Page 832: Ldap Parameters

    Mediant 3000 Parameter Description [ RoutingRuleGroups ] FORMAT RoutingRuleGroups_Index = RoutingRuleGroups_LCREnable, RoutingRuleGroups_LCRAverageCallLength, RoutingRuleGroups_LCRDefaultCost; [ \RoutingRuleGroups ] Note: For a detailed description of this table, see 'Enabling LCR and Configuring Default LCR' on page 217. Web: Cost Group Table This table parameter configures the Cost Groups for LCR, where...
  • Page 833 The valid value range is 0 to 86400. The default is 3000. Time [LDAPServerMaxRespon dTime] [LDAPDebugMode] Determines whether to enable the LDAP task debug messages. This is used for providing debug information regarding LDAP tasks. The valid value range is 0 to 3. The default is 0. Version 6.6 Mediant 3000...
  • Page 834 Mediant 3000 Parameter Description Web: MS LDAP OCS Defines the name of the attribute that represents the user OCS Number attribute name number in the Microsoft AD database. EMS: LDAP ocs Number The valid value is a string of up to 49 characters. The default is Attribute Name "msRTCSIP-PrimaryUserAddress".

  • Page 835: Sbc Parameters

    If the received header’s original value is 0, the message is not passed on and is rejected.  If the received header’s original value is less than this parameter's value, the header’s value is decremented before being sent on. Version 6.6 Mediant 3000...
  • Page 836 Mediant 3000 Parameter Description  If the received header’s original value is greater than the parameter's value, the header’s value is replaced by the user- defined parameter’s value. The valid value range is 1-70. The default is 10. Web: SBC Session-Expires Defines the SBC session refresh timer (in seconds) in the Session- Expires header of outgoing INVITE messages.
  • Page 837 INVITE to the device, which the device then sends to the correct destination.  [2] Handle Locally = The device handles SIP 3xx responses on behalf of the dialog-initiating UA and retries the request (e.g., Version 6.6 Mediant 3000...
  • Page 838 Mediant 3000 Parameter Description INVITE) using one or more alternative URIs included in the 3xx response. The device sends the new request to the alternative destination according to the IP-to-IP Routing table (the 'Call Trigger' field must be set to 3xx).
  • Page 839 When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following XML body: Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> Version 6.6 Mediant 3000...
  • Page 840 Mediant 3000 Parameter Description </LMIDocument> Web: SBC GRUU Mode Determines the Globally Routable User Agent (UA) URI (GRUU) [SBCGruuMode] support, according to RFC 5627.  [0] None = No GRUU is supplied to users.  [1] As Proxy = (Default) The device provides same GRUU types as the proxy provided the device’s GRUU clients.
  • Page 841 [0] Only if Required = (Default) Do not force transcoding. Many of the media settings (such as gain control) are not implemented on the voice stream. The SBC application passes packets RTP to RTP without any processing. Version 6.6 Mediant 3000...
  • Page 842 Mediant 3000 Parameter Description  [1] Force = Forces transcoding on the outgoing SBC leg. The device's SBC application interworks the media by implementing DSP transcoding. Note: This parameter can also be configured in an IP Profile. Web: SBC Preferences...
  • Page 843 Note: For a detailed description of this table, see 'Configuring Allowed Coder Groups' on page 438. Classification Table Web: Classification Table This table parameter configures the Classification table. This table EMS: SBC Classification classifies incoming SIP dialogs to Source IP Groups. The format of Version 6.6 Mediant 3000...
  • Page 844 Mediant 3000 Parameter Description [Classification] this parameter is as follows: [ Classification ] FORMAT Classification_Index = Classification_MessageCondition, Classification_SrcSRDID, Classification_SrcAddress, Classification_SrcPort, Classification_SrcTransportType, Classification_SrcUsernamePrefix, Classification_SrcHost, Classification_DestUsernamePrefix, Classification_DestHost, Classification_ActionType, Classification_SrcIPGroupID; [ \Classification ] For example: Classification 1 = 1, , 10.8.6.15, 5060, 2, *, *, *, *, 1, 4;...
  • Page 845 EMS: IP to IP Outbound (source and/or destination) of the outbound SIP dialog message. The Manipulation format of this parameter is as follows: [IPOutboundManipulation] FORMAT IPOutboundManipulation_Index = IPOutboundManipulation_IsAdditionalManipulation, IPOutboundManipulation_SrcIPGroupID, IPOutboundManipulation_DestIPGroupID, IPOutboundManipulation_SrcUsernamePrefix, IPOutboundManipulation_SrcHost, IPOutboundManipulation_DestUsernamePrefix, IPOutboundManipulation_DestHost, IPOutboundManipulation_RequestType, IPOutboundManipulation_ReRouteIPGroupID, Version 6.6 Mediant 3000...

  • Page 846: Standalone Survivability Parameters

    Mediant 3000 Parameter Description IPOutboundManipulation_Trigger, IPOutboundManipulation_ManipulatedURI, IPOutboundManipulation_RemoveFromLeft, IPOutboundManipulation_RemoveFromRight, IPOutboundManipulation_LeaveFromRight, IPOutboundManipulation_Prefix2Add, IPOutboundManipulation_Suffix2Add, IPOutboundManipulation_PrivacyRestrictionMode; For example: IPOutboundManipulation 1 = 0, 2, 4, "*", "*", "*", "*", 0, -1, 0, 0, 0, 0, 255, "", "", 0; Note: For a detailed description of this table, see 'Configuring IP-to- IP Outbound Manipulations' on page 460.
  • Page 847 If no such redundant SAS exists, the SAS sends the request to its default gateway (configured by the parameter SASDefaultGatewayIP). The valid range is -1 to 5. The default is -1 (i.e., no redundant Proxy Version 6.6 Mediant 3000...
  • Page 848 Mediant 3000 Parameter Description Set). Web/EMS: SAS Block Determines whether the device rejects SIP INVITE requests received Unregistered Users from unregistered SAS users. This applies to SAS Normal and [SASBlockUnRegUsers] Emergency modes.  [0] Un-Block = (Default) Allow INVITE from unregistered SAS users.
  • Page 849 EMS: Stand-Alone Request-URI user part of incoming INVITE messages and of incoming Survivability REGISTER request AoR (To header), before saving it to the registered [SASRegistrationManip users database. The format of this table parameter is as follows: Version 6.6 Mediant 3000...

  • Page 850: Ip Media Parameters

    Mediant 3000 Parameter Description ulation] [SASRegistrationManipulation] FORMAT SASRegistrationManipulation_Index = SASRegistrationManipulation_RemoveFromRight, SASRegistrationManipulation_LeaveFromRight; [\SASRegistrationManipulation] For example, the manipulation rule below routes an INVITE with Request-URI header "sip:7184002@10.33.4.226" to user "4002@10.33.4.226" (i.e., keep only four digits from right of user part): SASRegistrationManipulation 0 = 0, 4;...
  • Page 851 [0] 0 = (Default) AGC works on signals from the TDM side. [AGCRedirection]  [1] 1 = AGC works on signals from the IP side. Web: AGC Target Energy Defines the signal energy value (dBm) that the AGC attempts to EMS: Target Energy attain. Version 6.6 Mediant 3000...
  • Page 852 Mediant 3000 Parameter Description [AGCTargetEnergy] The valid range is 0 to -63 dBm. The default is -19 dBm. EMS: Minimal Gain Defines the minimum gain (in dB) by the AGC when activated. [AGCMinGain] The range is 0 to -31. The default is -20.
  • Page 853 The valid value is 0 to 3, where 0 (default) is the least sensitive. EMS: Beep Detection Sensitivity [AMDBeepDetectionSen sitivity] Web: AMD mode Enables the device to disconnect the IP-to-Tel call upon detection of CLI: amd-mode an answering machine on the Tel side (i.e., AMD). In such a scenario, Version 6.6 Mediant 3000...
  • Page 854 Mediant 3000 Parameter Description [AMDmode] the device sends a SIP BYE message upon AMD.  [0] = (Default) Device does not disconnect call upon detection of an answering machine.  [1] = Device disconnects call upon detection of an answering machine.

  • Page 855: 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 856: Automatic Update Parameters

    Mediant 3000 53.18 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Note: Auxiliary file upload through TFTP is not supported by HA mode. Automatic Update of Software and Configuration Files Parameters...
  • Page 857 Note: For this parameter to take effect, a device reset is required. [TLSCertFileUrl] Defines the name of the TLS certificate file and the URL from where it can be downloaded. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 3000...
  • Page 858 Mediant 3000 Parameter Description [TLSPkeyFileUrl] Defines the URL for downloading a TLS private key file using the Automatic Update facility. [UserInfoFileURL] Defines the name of the User Information file and the path to the server (IP address or FQDN) on which it is located.

  • Page 859: Dsp Templates

    Mediant 3000 full chassis – see 'Mediant 3000 Full Chassis' on page  Mediant 3000 with 16 E1 / 21 T1 – see 'Mediant 3000 16 E1 / 21 T1' on page  Mediant 3000 with single T3 – see 'Mediant 3000 with Single T3' on page ...

  • Page 860: Mediant 3000 16 E1 / 21 T1

    SPEEX WB T.38 Version 3 54.1.2 Mediant 3000 16 E1 / 21 T1 The DSP templates for Mediant 3000 16 E1 / 21 T1 are shown in the table below. Notes: • For each IP-to-IP transcoding call, two DSP channels are required.
  • Page 861 User's Manual 54. DSP Templates DSP Firmware Templates for Mediant 3000 16 E1 / 21 T1 DSP Template Supplementary Capabilities Number of Channels Voice Coder AMR-WB EVRC EVRC-B G.711 A/µ-law PCM G.722 G.723.1 G.726 ADPCM G.727 G.729 A, B GSM EFR...

  • Page 862: Mediant 3000 With Single T3

    Mediant 3000 54.1.3 Mediant 3000 with Single T3 The DSP templates for Mediant 3000 with a single T3 interface are shown in the table below. DSP Firmware Templates for Mediant 3000 with Single T3 DSP Template Supplementary Capabilities Number of Channels...

  • Page 863: Dsp Template Mix Feature For Mediant 3000

    User's Manual 54. DSP Templates 54.1.4 DSP Template Mix Feature for Mediant 3000 The device can operate (and be loaded) with up to two DSP templates. The channel capacity per DSP template is approximately 50%, with alignment to the number of DSP's present in the device.
  • Page 864 Mediant 3000 Reader's Notes User's Manual Document #: LTRT-89729...

  • Page 865: Selected Technical Specifications

    User's Manual 55. Selected Technical Specifications Selected Technical Specifications The section lists the technical specifications of the Mediant 3000. Note: All specifications in this document are subject to change without prior notice. Technical Specifications Function Specification Trunk & Channel Capacity...
  • Page 866 OC-3/STM-1 PSTN 1+1 Protected STM-1/OC-3 interface. Two 155.54 Mbps single-mode optical SFP transceiver module, using 1310 nm wavelength. Note: Applicable only to Mediant 3000 with TP-6310 blade. T3/DS3 PSTN Up to three Mini-SMB T3/DS3 (44.736 Mbps, 75 Ohm coax) interfaces.
  • Page 867 480 channels: SDRAM - 256 MB (applicable only to device's Control Processor housing TP-8410) Memory  2016 channels: SDRAM - 512 MB AudioCodes AC491 VoIP DSP @ 300 MHz Signal Processors LED Indicators LED Indications on Visual status indications and alarms: Power, Fan Tray, ACT/Fail, E1/T1 Front Panel status, Ethernet status, Swap ready Version 6.6...
  • Page 868 E1/T1 Interface Two 100-pin SCSI connectors for Trunks 1-25 and 43-67. Two 68-pin SCSI connectors for Trunks 26-42 and 68-84. Note: Applicable only to Mediant 3000 with TP-8410. STM-1/OC-3 Interface Two fiber optical 155.54-Mbps SFP modules (1+1 redundancy). The SFP modules accept twin single-mode fiber optic cables terminated with LC-type connectors (not supplied).
  • Page 869 Enclosure  Dimensions (H x W x D): 88 x 482.6 x 296.8 mm (3.5 x 19 x 11.87 inch), including mounting brackets  Two middle mounting brackets (optional) Weight (Fully 10.4 kg (23 lbs) Populated) Version 6.6 Mediant 3000...
  • Page 870 19-inch rack mounting, shelf mounting, or desktop mounting Hot Swap Full blade hot-swap supported for media processing blades according to PICMG 2.1. Host Interface Via Packet interface using AudioCodes’ proprietary TPNCP or standard control protocols Regulatory Compliance Telecommunication FCC part 68, TBR4 and TBR13 Standards ...
  • Page 871 User's Manual 55. Selected Technical Specifications Reader's Notes Version 6.6 Mediant 3000...
  • Page 872 User's Manual Ver. 6.6 www.audiocodes.com...

Table of Contents