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

AudioCodes Mediant 3000 User Manual

Gateway & enterprise sbc, family of media gateways & session border controllers
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
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, User Manual
User's Manual
AudioCodes Family of Media Gateways & Session Border Controllers (SBC)
Mediant™ 3000 Gateway &
Enterprise SBC
Version 6.8

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 User's Manual AudioCodes Family of Media Gateways & Session Border Controllers (SBC) Mediant™ 3000 Gateway & Enterprise SBC Version 6.8...

  • Page 3: Table Of Contents

    Configuring VoIP LAN Interface for OAMP ............. 35 Web Interface ......................35 CLI .......................... 37 BootP/TFTP Server ....................39 Configuring an IP Address for Mediant 3000 HA ..........41 Web Interface ......................42 EMS ........................43 Management Tools ....................47 Introduction ....................... 49 Web-Based Management ..................
  • Page 4 Mediant 3000 CLI-Based Management ..................81 Enabling CLI ......................81 8.1.1 Enabling Telnet for CLI .................... 81 8.1.2 Enabling SSH with RSA Public Key for CLI ............. 82 Establishing a CLI Session ..................84 Configuring Maximum Telnet/SSH Sessions ............85 Command Shell ......................
  • Page 5 14.4 IPSec and Internet Key Exchange ............... 170 14.4.1 Enabling IPSec ......................171 14.4.2 Configuring IP Security Proposal Table ..............171 14.4.3 Configuring IP Security Associations Table ............173 15 Media ........................ 177 15.1 Configuring Voice Settings ................... 177 15.1.1 Configuring Voice Gain (Volume) Control .............178 Version 6.8 Mediant 3000...
  • Page 6 Mediant 3000 15.1.2 Echo Cancellation ....................178 15.2 Fax and Modem Capabilities ................179 15.2.1 Fax/Modem Operating Modes ................180 15.2.2 Fax/Modem Transport Modes ................181 15.2.2.1 T.38 Fax Relay Mode ................181 15.2.2.2 G.711 Fax / Modem Transport Mode ............ 183 15.2.2.3 Fax Fallback ..................184 15.2.2.4 Fax/Modem Bypass Mode ..............
  • Page 7 19.5 Configuring SIP Message Policy Rules ..............317 20 Coders and Profiles ..................321 20.1 Configuring Default Coders .................. 321 20.2 Configuring Coder Groups ................... 325 20.3 Configuring Tel Profile ..................326 20.4 Configuring IP Profiles ..................329 Version 6.8 Mediant 3000...
  • Page 8 Mediant 3000 Gateway Application .....................357 21 Introduction ..................... 359 22 Digital PSTN ..................... 361 22.1 Configuring Trunk Settings ................... 361 22.2 TDM and Timing ....................363 22.2.1 Configuring TDM Bus Settings ................363 22.2.2 Configuring Digital PCM Settings ................364 22.2.3 Configuring System Timing ...................364 22.2.4 Clock Settings ......................365...
  • Page 9 27.5.2.1 About E9-1-1 Services ................463 27.5.2.2 Microsoft Lync Server 2010 and E9-1-1 ..........464 27.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 27.5.2.4 Configuring AudioCodes ELIN Gateway ..........472 27.6 Multilevel Precedence and Preemption ..............475 27.6.1 MLPP Preemption Events in SIP Reason Header ..........477...
  • Page 10 Mediant 3000 28.3.1 Initial Registration Request Processing ..............489 28.3.2 SBC Users Registration Database ................490 28.3.3 Routing using Users Registration Database............490 28.3.4 Registration Refreshes ..................490 28.3.5 Registration Restriction Control ................491 28.4 SBC Media Handling .................... 492 28.4.1 Media Anchoring without Transcoding (Transparent) ...........493 28.4.2 Media Anchoring with Transcoding ...............494...
  • Page 11 30.1 Initialization Process .................... 562 30.2 Configuration Stages .................... 563 30.3 Blade Failure Detection ..................564 31 Network Interfaces and Mediant 3000 High Availability ....... 565 31.1 Mediant 3000 Internal Link ................... 565 31.2 Example of Multiple Interface Configuration ............565 32 Physical Network Separation Mode ...............
  • Page 12 39.2.5 HTTP-based Provisioning ..................624 39.2.6 Loading Files Securely by Disabling TFTP ............625 39.2.7 FTP- or NFS-based Provisioning ................625 39.2.8 Provisioning using AudioCodes EMS ..............625 39.3 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 626 39.3.1 Files Provisioned by Automatic Update ..............626 39.3.2 File Location for Automatic Update ...............626...
  • Page 13 46.1 Syslog Message Format ..................693 46.1.1 Event Representation in Syslog Messages ............694 46.1.2 Unique Device Identification in Syslog Messages ..........696 46.1.3 Identifying AudioCodes Syslog Messages using Facility Levels ......696 46.1.4 Syslog Fields for Answering Machine Detection ...........697 46.1.5 SNMP Alarms in Syslog Messages ...............697 46.2 Enabling Syslog ....................
  • Page 14 Mediant 3000 47 Self-Testing ...................... 707 48 Creating Core Dump and Debug Files upon Device Crash ......709 49 Testing SIP Signaling Calls ................711 49.1 Configuring Test Call Endpoints ................711 49.2 Starting and Stopping Test Calls ................715 49.3 Viewing Test Call Statistics ..................
  • Page 15 51.14.3 Least Cost Routing Parameters ................968 51.14.4 Call Setup Rules Parameters ................970 52 SBC and DSP Channel Capacity ..............971 52.1 Signaling-Media Sessions & User Registrations ..........971 52.2 Mediant 3000 ....................... 972 52.2.1 Mediant 3000 Full Chassis ..................973 Version 6.8 Mediant 3000...
  • Page 16 Mediant 3000 52.2.2 Mediant 3000 16 E1 / 21 T1 ..................974 52.2.3 Mediant 3000 with Single T3 .................975 52.2.4 Mediant 3000 DSP Template Mix Feature ............976 53 Technical Specifications ................977 User's Manual Document #: LTRT-89738...

  • Page 17: Weee Eu Directive

    Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our Web site at https://www.audiocodes.com/services-support/maintenance-and-support.
  • Page 18 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 19 If any open source software is provided in object code, and its accompanying license requires that it be provided in source code as well, Buyer may receive such source code by contacting AudioCodes, by following the instructions available on AudioCodes website.
  • Page 20 PstnPrefix_SourceAddress; ResetWebPassword; KeepAliveTrapPort; SSHMaxLoginAttempts; EnablePChargingVector  New parameters: CustomerSN  89738 Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form site https://online.audiocodes.com/documentation-feedback.

  • Page 21: 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 22 Mediant 3000 The device supports a wide variety of VoIP and cellular vocoders, standards-compliant signaling and call control, and is based on AudioCodes' VoIPerfect™ architecture core technology. The device supports a broad selection of voice processing related algorithms such as G.711, G.723.1, G.729A Vocoders, G.168-2000 compliant echo cancellation, T.38 real-time Fax over IP, a wide selection of in-band and out-of-band tone detection and generation, as well as signaling protocol support including ISDN PRI.

  • Page 23: Functional Block Diagrams

    For more details on the HA system, see ''HA Overview'' on page 561. 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 24 Mediant 3000 User's Manual Document #: LTRT-89738...

  • Page 25: 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, NOTIFY,PRACK,REFER,INFO Version 6.8 Mediant 3000...
  • Page 26 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 27 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 28 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 29: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 31: Introduction

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

  • Page 33: Default Oamp Ip Address

    TP-6310 or TP-8410 blade in Slot 1: 10.1.10.10 Private IP Address  TP-6310 or TP-8410 blade in Slot 3: 10.1.10.11 (only for HA mode) Prefix Length 255.255.0.0 (16) Default Gateway 0.0.0.0 VLAN ID Interface Name "O+M+C" Version 6.8 Mediant 3000...
  • Page 34 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 35: Configuring Voip Lan Interface For Oamp

    Bootstrap Protocol (BootP) - see BootP/TFTP Server on page Note: This section describes how to change the default LAN 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 41. Web Interface The following procedure describes how to change the IP address of the OAMP on the VoIP-LAN interface, using the Web-based management tool (Web interface).
  • Page 36 Mediant 3000 Change the IP address and subnet mask of your computer to correspond with the default OAMP 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 37: Cli

    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 4-4: Serial Connection with PC for CLI Communication for TP-6310 Figure 4-5: Serial Connection with PC for CLI Communication for TP-8410 Version 6.8 Mediant 3000...
  • Page 38 Mediant 3000 Establish serial communication with the device using a terminal emulator program such as HyperTerminal, with the following communication port settings: • Baud Rate: 115,200 bps • Data Bits: 8 • Parity: None • Stop Bits: 1 • Flow Control: None At the prompt, type the login username (default is "Admin"...

  • Page 39: 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 40 Mediant 3000 Click Apply to save the new client. Power down and then power up the device. This enables the device to receive its new networking parameters through the BootP process. User's Manual Document #: LTRT-89738...

  • Page 41: Configuring 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 42: Web Interface

    Mediant 3000 Web Interface The following procedure 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 43: Ems

    The following procedure describes how to initially assign a global IP address to Mediant 3000 HA using AudioCodes EMS management tool.  To initially assign a global IP address to Mediant 3000 HA using the EMS: Power down the chassis. Ensure that both blades are connected to the network.
  • Page 44 Mediant 3000 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 5-2: Adding a Region Verify that Mediant 3000 is up and running, by pinging its IP address.
  • Page 45 User's Manual 5. Configuring an IP Address for Mediant 3000 HA Open the IP Interface Settings screen - in the Navigation pane, click the device name, and then VoIP, Network, IP Interface Settings. Figure 5-4: IP Interface Settings Table In the table, select the OamAndMediaAndControl interface row, and then in the Configuration pane, click IP interface Settings;...
  • Page 46 Mediant 3000 Add once again the Mediant 3000 under your Region to the EMS with the new global IP address that you defined above. Right-click the active blade, and then choose Configuration > Upload; the EMS server synchronizes with the blade's configuration settings.

  • Page 47: Management Tools

    Part II Management Tools...

  • Page 49: Introduction

    Throughout this manual, whenever a parameter is mentioned, its corresponding Weband ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 727. Version 6.8 Mediant 3000...
  • Page 50 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 51: Web-Based Management

    • Some Web interface pages and/or parameters are available only for certain hardware configurations or software features. The software features are determined by the installed Software License Key (see ''Software License Key'' on page 607). Version 6.8 Mediant 3000...

  • Page 52: Getting Acquainted With The Web Interface

    Mediant 3000 Getting Acquainted with the Web Interface This section provides a description of the Web interface. 7.1.1 Computer Requirements The client computer requires the following to work with the Web interface of the device:  A network connection to the device ...

  • Page 53: Accessing The Web Interface

    /etc/hosts on UNIX or C:\Windows\System32\Drivers\ETC\hosts on Windows; then use the host name in the URL (e.g., https://ACL_280152). Below is an example of a host file: 127.0.0.1 localhost 10.31.4.47 ACL_280152 Version 6.8 Mediant 3000...

  • Page 54: Areas Of The Gui

    Mediant 3000 7.1.3 Areas of the GUI The areas of the Web interface's GUI are shown in the figure below and described in the subsequent table. Figure 7-2: Main Areas of the Web Interface GUI Table 7-1: Description of the Web GUI Areas...

  • Page 55: Toolbar Description

    If you modify a parameter on a page that takes effect only after a device reset, after you click the Submit button, the toolbar displays "Reset". This is a reminder that you need to later save your settings to flash memory and reset the device. Version 6.8 Mediant 3000...

  • Page 56: Navigation Tree

    Mediant 3000 7.1.5 Navigation Tree The Navigation tree is located in the Navigation pane and displays a tree-like structure of menus pertaining to the selected tab on the Navigation bar. You can drill-down to the required page item level to open its corresponding page in the Work pane.

  • Page 57: Showing / Hiding The Navigation Pane

     To show the Navigation pane, click the right-pointing arrow ; the pane is displayed and the button is replaced by the left-pointing arrow button. Figure 7-5: Show and Hide Button (Navigation Pane in Hide View) Version 6.8 Mediant 3000...

  • Page 58: Working With Configuration

    Mediant 3000 7.1.6 Working with Configuration Pages The configuration pages contain the parameters for configuring the device and are displayed in the Work pane. 7.1.6.1 Accessing Pages The configuration pages are accessed by clicking the required page item in the Navigation tree.
  • Page 59 The button appears with a down-pointing or up-pointing arrow, indicating that it can be collapsed or expanded when clicked, respectively. Figure 7-7: Expanding and Collapsing Parameter Groups Version 6.8 Mediant 3000...

  • Page 60: Modifying And Saving Parameters

    Mediant 3000 7.1.6.3 Modifying and Saving Parameters When you modify a parameter value on a page, the Edit icon appears to the right of the parameter. This indicates that the parameter has been modified, but has yet to be applied (submitted).

  • Page 61: Working With Tables

    Selected index row entry for editing, deleting and showing configuration. Displays the full configuration of the selected row when you click the Show/Hide button. Links to access additional configuration tables related to the current configuration. Version 6.8 Mediant 3000...

  • Page 62: Searching For Configuration Parameters

    Mediant 3000 Some tables also provide the Up and Down buttons for changing the position (index number) of a selected table row. These buttons become available only if the table contains more than one row. You can also define the number of rows to display on the page and to navigate between pages displaying multiple rows.
  • Page 63 Figure 7-12: Searched Result Screen Table 7-5: 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 Version 6.8 Mediant 3000...

  • Page 64: Creating A Login Welcome Message

    Mediant 3000 7.1.8 Creating a Login Welcome Message You can create a Welcome message box that is displayed on the Web Login page. The figure below displays an example of a Welcome message: Figure 7-13: User-Defined Web Welcome Message after Login To enable and create a Welcome message, use the WelcomeMessage table ini file parameter, as described in the table below.

  • Page 65: Getting Help

    Instead of clicking the Help button for each page you open, you can open it once for a page and then simply leave it open. Each time you open a different page, the Help topic pertaining to that page is automatically displayed. Version 6.8 Mediant 3000...

  • Page 66: Logging Off The Web Interface

    Mediant 3000 7.1.10 Logging Off the Web Interface The following procedure describes how to log off the Web interface.  To log off the Web interface: On the toolbar, click the Log Off icon; the following confirmation message box appears: Figure 7-15: Log Off Confirmation Box Click OK;...

  • Page 67: Viewing The Home Page

    Gateway Operational State: • "LOCKED": device is locked (i.e. no new calls are accepted) • "UNLOCKED": device is not locked • "SHUTTING DOWN": device is currently shutting down To perform these operations, see ''Basic Maintenance'' on page 577. Version 6.8 Mediant 3000...
  • Page 68 Mediant 3000  High Availability: Status of the device's HA mode (see Viewing HA Status on Home Page on page  Active Board Slot Number: Slot number with the active blade if the device is in HA mode; otherwise, this field is unavailable...

  • Page 69: Configuring Web User Accounts

    Note: At least one Security Administrator user must exist. Master Read / write privileges for all pages. Can create all user types, including additional Master users and Security Administrators. It can delete all users except the last Security Administrator. Version 6.8 Mediant 3000...
  • Page 70 Mediant 3000 Numeric User Level Representation Privileges in RADIUS Administrator Read / write privileges for all pages, except security-related pages (read-only). Monitor No access to security-related and file-loading pages; read-only access to all other pages. No Access No access to any page.

  • Page 71: Basic User Accounts Configuration

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

  • Page 72: Advanced User Accounts Configuration

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

  • Page 76: Displaying Login Information Upon Login

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

  • Page 77: Configuring Web Security Settings

    Open the WEB Security Settings page (Configuration tab > System menu > Management > WEB Security Settings). Set the 'Secured Web Connection (HTTPS)' parameter to HTTPS Only. Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 580. Version 6.8 Mediant 3000...

  • Page 78: Web Login Authentication Using Smart Cards

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

  • Page 79: Configuring Web And Telnet Access List

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

  • Page 80: Mediant

    Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 81: Cli-Based Management

    Secured (i.e, SSL). Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 730. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 3000...

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

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

  • Page 84: Establishing A Cli Session

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

  • Page 85: Configuring Maximum Telnet/Ssh Sessions

    To configure the maximum number of concurrent Telnet/SSH sessions: Open the Telnet/SSH Settings page (Configuration tab > System menu > Management > Telnet/SSH Settings). In the 'Maximum Telnet Sessions' field, enter the maximum number of concurrent sessions. Click Submit. Version 6.8 Mediant 3000...

  • Page 86: Command Shell

    Mediant 3000 Command Shell The Command Shell interface is used mainly to display current configuration and performance. 8.4.1 Getting Familiar with the Command Shell This section provides a description on how to work with the CLI. This includes basic navigation commands and accessing subdirectories.

  • Page 87: Status Commands

    />sh tdm status Trunk 00: Active Trunk 01: Active Trunk 02: Not Configured />sh tdm perf DS1 Trunk Statistics (statistics for 948 seconds): Trunk # B-Channel Call count RTP packet RTP packet Activity utilization Seconds 2865 149743 3017 Version 6.8 Mediant 3000...
  • Page 88 Mediant 3000 />sh dsp status DSP firmware: 491096AE8 Version:0660.03 Used=0 Free=480 Total=480 DSP device Active Used=16 Free= 0 Total=16 DSP device Active Used=16 Free= 0 Total=16 DSP device Active Used=16 Free= 0 Total=16 DSP device Active Used=16 Free= 0 Total=16...

  • Page 89: Ping Command

    Reply from 10.31.2.10: bytes=0 time<0ms Reply from 10.31.2.10: bytes=0 time<0ms Ping statistics for 10.31.2.10: Packets:Sent = 4, Received = 4, Lost 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Version 6.8 Mediant 3000...

  • Page 90: Test Call (Tc) Commands

    Mediant 3000 8.4.4 Test Call (TC) Commands The Test Call commands can be used to simulate an IP-to-PSTN call. Note: Only one test call can be activated at a given time. Table 8-4: Test Call Command Command Short Format Sub-Commands...

  • Page 91: Management Commands

    Retrieves the full ini file from the device and allows loading a new ini file directly in the CLI session. Note: The argument view displays the file, page by page. The argument get displays the file without breaks. Version 6.8 Mediant 3000...

  • Page 92: Pstn Commands

    Mediant 3000 8.4.7 PSTN Commands The commands under the PSTN directory allow you to perform various PSTN actions. Table 8-8: PSTN CLI Command Command Short Format Arguments Description PstnLoopCommands PS/PH/PLC <TrunkId> Activates a loopback on a specific trunk <LoopCode> and B-channel. For loopback on the <BChannel>...
  • Page 93 User's Manual 8. CLI-Based Management Sub-Command Arguments Description LDapSetDebugmode <mode> Sets the LdapDebugLevelMode parameter. Possible levels 0-3. LDapGetDebugmode Gets the LdapDebugLevelMode parameter value Version 6.8 Mediant 3000...
  • Page 94 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 95: Snmp-Based Management

    SNMP Manager. All supported MIB files are supplied to customers as part of the release. AudioCodes EMS is an advanced solution for standards-based management that covers all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of the device.

  • Page 96: Enabling Snmp And Configuring Snmp Community Strings

    Mediant 3000 Enabling SNMP and Configuring SNMP Community Strings The SNMP Community String page lets you configure up to five read-only and up to five read-write SNMP community strings and to configure the community string that is used for sending traps.

  • Page 97: Configuring Snmp Trap Destinations

    Manager. The device sends SNMP traps to this IP address. Trap Port Defines the port number of the remote SNMP Manager. [SNMPManagerTrapPort_x] The device sends SNMP traps to this port. The valid value range is 100 to 4000. The default is 162. Version 6.8 Mediant 3000...

  • Page 98: Configuring Snmp Trusted Managers

    Mediant 3000 Parameter Description Web: Trap User Associates a trap user with the trap destination. This [SNMPManagerTrapUser] determines the trap format, authentication level, and encryption level.  v2cParams (default) = SNMPv2 user community string  SNMPv3 user configured in ''Configuring SNMP V3...

  • Page 99: Configuring Snmp V3 Users

    Authentication Protocol Authentication protocol of the SNMP v3 user. [SNMPUsers_AuthProtocol]  [0] None (default)  [1] MD5  [2] SHA-1 Privacy Protocol Privacy protocol of the SNMP v3 user. [SNMPUsers_PrivProtocol]  [0] None (default)  [1] DES Version 6.8 Mediant 3000...
  • Page 100 Mediant 3000 Parameter Description  [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. Keys are always persisted as long hex strings and keys are localized.

  • Page 101: Ini File-Based Management

    = value ; this is a comment line ; for example: [System Parameters] SyslogServerIP = 10.13.2.69 EnableSyslog = 1 For general ini file formatting rules, see ''General ini File Formatting Rules'' on page 103. Version 6.8 Mediant 3000...

  • Page 102: Configuring Table Ini File Parameters

    Mediant 3000 10.1.2 Configuring Table ini File Parameters The table ini file parameters allow you to configure tables, which include multiple parameters (columns) and row entries (indices). When loading an ini file to the device, it's recommended to include only tables that belong to applications that are to be configured (dynamic tables of other applications are empty, but static tables are not).

  • Page 103: General Ini File Formatting Rules

    CallProgressTonesFileName = 'cpt_usa.dat'.  The parameter name is not case-sensitive.  The parameter value is not case-sensitive, except for coder names.  The ini file must end with at least one carriage return. Version 6.8 Mediant 3000...

  • Page 104: Configuring An Ini File

    Thus, all previous configuration is overridden.  AudioCodes AcBootP utility: Bootstrap Protocol (BootP) with TFTP is used to load the file. The device updates its configuration according to the loaded ini file, and applies default values to parameters that were not included in the loaded ini file. Thus, all previous configuration is overridden.

  • Page 105: Secured Encoded 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 106: Ini Viewer And Editor Utility

    10.6 INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any Windows-based PC.

  • Page 107: General System Settings

    Part III General System Settings...

  • Page 109: Configuring Ssl/Tls Certificates

    Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 3000...
  • Page 110 Mediant 3000 To use a TLS Context for SIPS, you can assign it to a Proxy Set and/or SIP Interface associated with the IP Group for which you want to employ TLS certificates. When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows: ...
  • Page 111 [5] TLSv1.0 and TLSv1.2 = TLS 1.2 and TLS 1.0 only.  [6] TLSv1.1 and TLSv1.2 = TLS 1.2 and TLS 1.1 only  [7] TLSv1.0 TLSv1.1 and TLSv1.2 = TLS 1.2, TLS 1.1 and TLS 1.0 only (excludes SSL 3.0). Version 6.8 Mediant 3000...
  • Page 112 Mediant 3000 Parameter Description DTLS Version Defines the Datagram Transport Layer Security (DTLS) version, which is used to negotiate keys for WebRTC calls. [TLSContexts_DTLSVersion]  [0] Any (default)  [1] DTLSv1.0  [2] DTLSv1.2 Note: The parameter is applicable only to the SBC application.

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

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

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

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

  • Page 115: Generating Private Keys For Tls Contexts

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

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

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

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

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

  • Page 118: Configuring Mutual Tls Authentication

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

  • Page 119: Tls For Remote Device Management

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

  • Page 120: Configuring Tls Server Certificate Expiry Check

    Mediant 3000 11.1.7 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure device send notification...

  • Page 121: Date And Time

    If the device is configured to obtain the date and time from an SNTP server, the fields on this page are read-only, displaying the received date and time. • After performing a hardware reset, the date and time are returned to their defaults and thus, should be updated. Version 6.8 Mediant 3000...

  • Page 122: Configuring Automatic Date And Time Using Sntp

    Mediant 3000 12.2 Configuring Automatic Date and Time using SNTP The device's Simple Network Time Protocol (SNTP) client functionality generates requests and reacts to the resulting responses using the NTP Version 3 protocol definitions (according to RFC 1305). Through these requests and responses, the device, as an NTP client, synchronizes the system time to a time source within the network, thereby eliminating any potential issues should the local system clock 'drift' during operation.

  • Page 123: Configuring Daylight Saving Time

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

  • Page 125: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 127: Network

    After reconfiguration has completed, connect the device to the new network and restart it. As a result, the remote configuration process that occurs in the new network uses a valid Ethernet configuration Version 6.8 Mediant 3000...

  • Page 128: Ethernet Interface Redundancy

    Mediant 3000 13.2 Ethernet Interface Redundancy The device supports an Ethernet redundancy scheme. At the beginning of the start-up procedure, the device tests whether the ‘primary’ Ethernet interface is connected, by checking the existence of the Ethernet link carrier. If it's connected, the start-up procedure commences as usual.

  • Page 129: Configuring Ip Network Interfaces

    VLAN ID (VLAN ID to which incoming, untagged packets are assigned). You can also configure Quality of Service (QoS) by assigning VLAN priorities and Differentiated Services (DiffServ) for the supported Class of Service (CoS). For configuring Quality of Service (QoS), see ''Configuring the QoS Settings'' on page 140. Version 6.8 Mediant 3000...
  • Page 130 Mediant 3000  Default Gateway: Traffic from this interface destined to a subnet that does not meet any of the routing rules (local or static) are forwarded to this gateway (as long as the application type is allowed on this interface).
  • Page 131 Specifically, instead of using eight-bit address blocks, it uses the variable-length subnet masking technique to allow allocation on arbitrary-length prefixes. The prefix length for IPv4 must be set to a value from 0 to 30. The Version 6.8 Mediant 3000...
  • Page 132 Mediant 3000 Parameter Description prefix length for IPv6 must be set to a value from 0 to 64. Web/EMS: Default Gateway Defines the IP address of the default gateway for the interface. When [InterfaceTable_Gateway] traffic is sent from this interface to an unknown destination (i.e., not in the same subnet and not defined for any static routing rule), it is forwarded to this default gateway.

  • Page 133: Assigning Ntp Services To Application Types

    [0] Disable (default).  [1] Enable. Notes:  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 134 Mediant 3000  The network interface types can be combined: • Example 1: ♦ One combined OAMP-Media-Control interface with an IPv4 address • Example 2: ♦ One OAMP interface with an IPv4 address ♦ One or more Control interfaces with IPv4 addresses ♦...

  • Page 135: Networking Configuration Examples

    0.0.0.0 ManagementIF Manual Control IPv4 200.200.85.14 200.200.85.1 myControlIF Manual Media IPv4 211.211.85.14 211.211.85.1 myMediaIF Manual VLANs are required and the Native VLAN ID is the same VLAN ID as the Management interface (configured for Index 0): Version 6.8 Mediant 3000...

  • Page 136: Voip Interfaces For Combined Application Types

    Mediant 3000 • 'VLAN Mode' is set to Enable. • 'Native VLAN ID' field is set to "1". Static Route table: A routing rule is required to allow remote management from a host in 176.85.49.0 / 24: Table 13-5: Example Static Route Table...

  • Page 137: Voip Interfaces With Multiple Default Gateways

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

  • Page 139: Configuration Example Of Static Ip Routes

     The static route's Gateway address in the Static Route table is in the same subnet as the IP address of the IP network interface in the Interface table. Figure 13-2: Example of using Static Route Version 6.8 Mediant 3000...

  • Page 140: Troubleshooting The Routing Table

    Mediant 3000 13.4.2 Troubleshooting the Routing Table When adding a new static route to the Static Route table, the added rule passes a validation test. If errors are found, the static route is rejected and not added to the table.
  • Page 141 Varies according to the interface Depends on traffic type: type associated with NTP (see  Control: Premium control ''Assigning NTP Services to  Management: Bronze Application Types'' on page 133):  OAMP  Control NFSServers_VlanType in the Gold NFSServers table Version 6.8 Mediant 3000...

  • Page 142: Configuring Icmp Messages

    Mediant 3000  To configure QoS: Open the QoS Settings page (Configuration tab > VoIP menu > Network > QoS Settings). Under the Priority Settings group, configure the VLAN priorities (Layer-2 QoS) per CoS. Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS.

  • Page 143: Dns

    DNS server for the related IP network interface (see ''Configuring IP Network Interfaces'' on page 129). The following procedure describes how to configure the DNS table in the Web interface. You can also this using the table ini file parameter, DNS2IP. Version 6.8 Mediant 3000...
  • Page 144 Mediant 3000  To configure the internal DNS table: Open the Internal DNS Table page (Configuration tab > VoIP menu > Network > DNS > Internal DNS Table). Click Add; the following dialog box appears: Figure 13-4: Internal DNS Table - Add Record Dialog Box Configure the DNS rule, as required.

  • Page 145: Configuring The Internal Srv Table

    Click Add; the following dialog box appears: Figure 13-5: Internal SRV Table Page Configure an SRV rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...

  • Page 146: Configuring Nfs Settings

    Mediant 3000 Table 13-12: Internal SRV Table Parameter Descriptions Parameter Description Domain Name Defines the host name to be translated. [Srv2Ip_InternalDomain] The valid value is a string of up to 31 characters. Transport Type Defines the transport type. [Srv2Ip_TransportType] ...
  • Page 147 The VLAN type for accessing the remote file system. [NFSServers_VlanType]  [0] OAMP  [1] Media (default) Note: This parameter applies only if VLANs are enabled or if Multiple IPs is configured (see ''Configuring IP Network Interfaces'' on page 129). Version 6.8 Mediant 3000...

  • Page 148: Network Address Translation Support

    Mediant 3000 13.9 Network Address Translation Support Network Address Translation (NAT) is a mechanism that maps internal IP addresses (and ports) used within a private network to global IP addresses and vice versa, providing transparent routing to end hosts. The primary advantages of NAT include (1) reduction in...

  • Page 149: Configuring Stun

    STUN is applicable only to UDP connections (not TCP and TLS). • STUN can’t be used when the device is located behind a symmetric NAT. • Use either the STUN server IP address (STUNServerPrimaryIP) or domain name (STUNServerDomainName) method, with priority to the first one. Version 6.8 Mediant 3000...

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

    Mediant 3000  To enable STUN: Open the Application Settings page (Configuration tab > System menu > Application Settings). Figure 13-8: STUN Parameters in Application Settings Page From the 'Enable STUN' (EnableSTUN) drop-down list, select Enable to enable the STUN feature.
  • Page 151 Defines the optional starting port range (0-65535) of the IP [NATTranslation_SourceStartPort] interface, used as matching criteria for this NAT rule. If not configured, the match is done on the entire port range. Only IP addresses and ports of matched source ports will be replaced. Version 6.8 Mediant 3000...

  • Page 152: Remote Ua Behind Nat

    Mediant 3000 Parameter Description Source End Port Defines the optional ending port range (0-65535) of the IP [NATTranslation_SourceEndPort] interface, used as matching criteria for this NAT rule. If not configured, the match is done on the entire port range. Only IP addresses and ports of matched source ports will be replaced.
  • Page 153 NAT and always sends the media packets to the UA using the IP address:port obtained from the first received SIP message.  NAT Is Used: NAT is always performed. The device considers the UA as located Version 6.8 Mediant 3000...
  • Page 154 Mediant 3000 behind NAT and always sends the media packets to the UA using the source address obtained from the first media packet received from the UA. In this mode, the device does not send any packets until it receives the first packet from the UA (in order to obtain the IP address).

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

    13. Network 13.10 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).
  • Page 156 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 157: Security

    Action Upon Match: Block • If you are using the High Availability feature and you have configured "block" rules, ensure that you also add "allow" rules for HA traffic. For more information, see Configuring Firewall Allowed Rules. Version 6.8 Mediant 3000...
  • Page 158 Mediant 3000 The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList.  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security >...
  • Page 159 Defines the network interface to which you want to apply the rule. [AccessList_Interface_x] This is applicable if you enabled the 'Use Specific Interface' field. The list displays interface names as defined in the Interface table in ''Configuring IP Network Interfaces'' on page 129. Version 6.8 Mediant 3000...
  • Page 160 Mediant 3000 Parameter Description Packet Size Defines the maximum allowed packet size. [AccessList_Packet_Size] The valid range is 0 to 65535. Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment.

  • Page 161: Configuring General Security Settings

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

  • Page 162: Intrusion Detection System

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

  • Page 163: Enabling Ids

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

  • Page 167: Assigning Ids Policies

    !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This [IDSMatch_ProxySet] indicates the Proxy Sets from where the attacks are coming from. The following syntax is supported: Version 6.8 Mediant 3000...

  • Page 168: Viewing Ids Alarms

    Mediant 3000 Parameter Description  A comma-separated list of Proxy Set IDs (e.g., 1,3,4)  A hyphen "-" indicates a range of Proxy Sets (e.g., 3,4-7 means IDs 3, and 4 through 7)  A prefix of an exclamation mark "!" means negation of the set (e.g.,...
  • Page 169 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.8 Mediant 3000...

  • Page 170: Ipsec And Internet Key Exchange

    Mediant 3000 14.4 IPSec and Internet Key Exchange IP security (IPSec) and Internet Key Exchange (IKE) protocols are part of the IETF standards for establishing a secured IP connection between two applications (also referred to as peers). Providing security services at the IP layer, IPSec and IKE are transparent to IP applications.

  • Page 171: Enabling Ipsec

    3DES SHA1 Group 1 (786 bit) 3DES Group 1 (786 bit) Proposal 3 Note: You can also configure the IP Security Proposals table using the table ini file parameter IPsecProposalTable (see ''Security Parameters'' on page 763). Version 6.8 Mediant 3000...
  • Page 172 Mediant 3000  To configure IP Security Proposals: Open the IP Security Proposal Table page (Configuration tab > VoIP menu > Security > IPSec Proposal Table). Click Add; the following dialog box appears: Figure 14-11: IP Security Proposals Table - Add Record Dialog Box Configure the parameters, as required.

  • Page 173: Configuring Ip Security Associations Table

    For security, once the IKE pre-shared key is configured, it is not displayed in any of the device's management tools. • You can also configure the IP Security Associations table using the table ini file parameter IPsecSATable (see ''Security Parameters'' on page 763). Version 6.8 Mediant 3000...
  • Page 174 Mediant 3000  To configure the IPSec Association table: Open the IP Security Associations Table page (Configuration tab > VoIP menu > Security > IPSec Association Table). Click Add; the following dialog box appears: Figure 14-12: IP Security Associations Table Page - Add Record Dialog Box Configure the parameters, as required (for a description of these parameters, see the table below).
  • Page 175 The default is 0 (i.e., the value is ignored). Dead Peer Detection Mode Defines dead peer detection (DPD), according to RFC 3706. [IPsecSATable_DPDmode]  [0] DPD Disabled (default)  [1] DPD Periodic = DPD is enabled with message exchanges at regular intervals Version 6.8 Mediant 3000...
  • Page 176 Mediant 3000 Parameter Name Description  [2] DPD on demand = DPD is enabled with on-demand checks - message exchanges as needed (i.e., before sending data to the peer). If the liveliness of the peer is questionable, the device sends a DPD message to query the status of the peer.

  • Page 177: Media

    Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 15-1: Voice Settings Page Configure the Voice parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 580. Version 6.8 Mediant 3000...

  • Page 178: Configuring Voice Gain (Volume) Control

    Mediant 3000 15.1.1 Configuring Voice Gain (Volume) Control 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).

  • Page 179: Fax And Modem Capabilities

    EchoCancellerAggressiveNLP - enables Aggressive NLP at the first 0.5 second of the call 15.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. Version 6.8 Mediant 3000...

  • Page 180: Fax/Modem Operating Modes

    Mediant 3000 Notes: • Unless otherwise specified, the configuration parameters mentioned in this section are available on this page. • Some SIP parameters override these fax and modem parameters. For example, the IsFaxUsed parameter and V.152 parameters in Section ''V.152 Support'' on page 194.

  • Page 181: Fax/Modem Transport Modes

    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. Version 6.8 Mediant 3000...
  • Page 182 To indicate T.38 over RTP, the SDP body uses "udptl" (Facsimile UDP Transport Layer) in the 'a=ftmp' line. The device supports T.38 over RTP according to this standard as well as according to AudioCodes proprietary method:  Call Parties belong to AudioCodes Devices: AudioCodes proprietary T.38-over- User's Manual Document #: LTRT-89738...

  • Page 183: Fax / Modem Transport Mode

    RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...

  • Page 184: Fax Fallback

    Mediant 3000 A ‘gpmd’ attribute is added to the SDP according to the following format:  For G.711 A-law: a=gpmd:0 vbd=yes;ecan=on (or off for modems)  For G.711 µ-law: a=gpmd:8 vbd=yes;ecan=on (or off for modems) The following parameters are ignored and automatically set to Events Only: ...
  • Page 185 Tip: When the remote (non-AudioCodes) gateway uses the G.711 coder for voice and doesn’t change the coder payload type for fax or modem transmission, it is recommended to use the Bypass mode with the following configuration: •...

  • Page 186: 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 187: Fax / Modem Transparent Mode

    Coders table - (Configuration tab > VoIP menu > Coders and Profiles > Coders). 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) - RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). 'Echo Canceller' (EnableEchoCanceller) - Voice Settings page. Version 6.8 Mediant 3000...

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

    Mediant 3000 Note: This mode can be used for fax, but is not recommended for modem transmission. Instead, use the Bypass (see ''Fax/Modem Bypass Mode'' on page 184) or Transparent with Events modes (see ''Fax / Modem Transparent with Events Mode'' on page 186) for modem.

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

    To use T.38 mode for V.34 and T.30 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to T.38 Relay (FaxTransportMode = 1). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Version 6.8 Mediant 3000...

  • Page 190: Fax Relay For Sg3 Fax Machines

    Mediant 3000 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). Set the ini file parameter, V34FaxTransportType to 1 (Relay).
  • Page 191 1938931006 1938930708 IN IP4 10.8.6.55 s=Phone-Call c=IN IP4 10.8.6.55 t=0 0 m=audio 6010 RTP/AVP 18 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 telephone-event/8000 a=fmtp:97 0-15 a=ptime:20 a=sendrecv m=image 6012 udptl t38 a=T38FaxVersion:3 a=T38MaxBitRate:33600 a=T38FaxMaxBuffer:1024 a=T38FaxMaxDatagram:122 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy Version 6.8 Mediant 3000...

  • Page 192: Modem Relay

    • 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 193: Simultaneous Negotiation Of Fax (T.38) And Modem (V.150.1) Relay

    To support this functionality, you need to configure a Coders Group (in the Coders Group table - see ''Configuring Coder Groups'' on page 325) that includes the T.38, V.150, and G.711/VBD coders. Version 6.8 Mediant 3000...

  • Page 194: Support

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

  • Page 195: Configuring Rtp/Rtcp Settings

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

  • Page 196: Comfort Noise Generation

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

  • Page 197: Dual-Tone Multi-Frequency Signaling

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

  • Page 198: Configuring Rfc 2833 Payload

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

  • Page 199: Configuring Rtp Base Udp Port

    Figure 15-6: RTP Based UDP Port in RTP/RTCP Settings Page Set the 'RTP Base UDP Port' parameter to the required value. Click Submit. Reset the device for the settings to take effect. Version 6.8 Mediant 3000...

  • Page 200: Configuring Ip Media Settings

    AudioCodes sales representative for more information on this service. You will be typically required to provide AudioCodes with a database of recorded voices (calls) in the language on which the device's AMD feature can base its voice detector algorithms. The data needed for an accurate calibration should be recorded under the following guidelines: ...
  • Page 201 The device supports up to eight AMD algorithm suites called Parameter Suites, where each suite defines a range of detection sensitivity levels. Sensitivity levels refer to how accurately, based on AudioCodes voice detection algorithms, the device can detect whether a human or machine has answered the call. Each level supports a different detection sensitivity to human and machine.
  • Page 202 Mediant 3000 Approximate AMD High Detection Sensitivity - Parameter Suite 1 (Based on North American English) Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 0 (Best for Answering Machine) 15 (Best for Live Calls)

  • Page 203: Detecting Answering Machine Beeps

    INFO sip:sipp@172.22.2.9:5060 SIP/2.0 Via: SIP/2.0/UDP 172.22.168.249;branch=z9hG4bKac1566945480 Max-Forwards: 70 From: sut <sip:3000@172.22.168.249:5060>;tag=1c1505895240 To: sipp <sip:sipp@172.22.2.9:5060>;tag=1 Call-ID: 1-29758@172.22.2.9 CSeq: 1 INFO Contact: <sip:56700@172.22.168.249> Supported: em,timer,replaces,path,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO ,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.6.80A.227.005 Content-Type: application/x-detect Content-Length: 30 Version 6.8 Mediant 3000...

  • Page 204: Configuring Amd

    Mediant 3000 Type= AMD SubType= AUTOMATA Upon detection by the device of the start of voice (i.e., the greeting message of the answering machine), the device sends the following INFO message to the application server: INFO sip:sipp@172.22.2.9:5060 SIP/2.0 Via: SIP/2.0/UDP 172.22.168.249;branch=z9hG4bKac482466515 Max-Forwards: 70 From: sut <sip:3000@172.22.168.249:5060>;tag=1c419779142...

  • Page 205: Enabling Ip-To-Tel Call Disconnection Upon Detection Of Answering

    You can enable this feature for all calls (globally) using the AMDmode parameter, or for specific calls using IP Profiles where the IP Profile parameter 'AMD Mode' (IpProfile_AmdMode) is set to [1] Disconnect on AMD (see 'Configuring IP Profiles' on page 329). Version 6.8 Mediant 3000...

  • Page 206: Automatic Gain Control (Agc)

    Mediant 3000 15.4.2 Automatic Gain Control (AGC) Automatic Gain Control (AGC) adjusts the energy of the output signal to a required level (volume). This feature compensates for near-far gain differences. AGC estimates the energy of the incoming signal from the IP or PSTN, determined by the 'AGC Redirection' parameter, calculates the essential gain, and then performs amplification.

  • Page 207: Configuring Various Codec Attributes

    Open the General Media Settings page (Configuration tab > VoIP menu > Media > General Media Settings). Configure the parameters as required, and then click click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 580. Version 6.8 Mediant 3000...

  • Page 208: Configuring Dsp Templates

    Mediant 3000 15.6 Configuring DSP Templates The DSP Template determines the coders that can be used by the device and various other functionalities. For a list of DSP templates and the maximum number of channels supported by each coder, see DSP Templates. You can select a single DSP Template or you can select two DSP Templates and define the percentage of DSP resources allocated per DSP Template.

  • Page 209: Configuring Media (Srtp) Security

    Notes: • For a detailed description of the SRTP parameters, see ''SRTP Parameters'' on page 765. • When SRTP is used, the channel capacity may be reduced. Version 6.8 Mediant 3000...
  • Page 210 Mediant 3000  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Figure 15-10: Media Security Page Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required.

  • Page 211: Services

    • For the maximum number of concurrent sessions that the device can record, contact your AudioCodes sales representative. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons.
  • Page 212 Mediant 3000 The device can record calls between two IP Groups, or between an IP Group and a Trunk Group (for Gateway calls). The type of calls to record can be specified by source and/or destination prefix number or SIP Request-URI, as well as by call initiator. The side ("leg") on which the recording is done must be specified.
  • Page 213 <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>1</label> Version 6.8 Mediant 3000...

  • Page 214: Enabling Sip-Based Media Recording

    Mediant 3000 </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label> </stream> </recording> --boundary_ac1fffff85b— 16.1.1 Enabling SIP-based Media Recording The following procedure describes how to enable the SIP-based media Recording feature. Once you have enabled this feature, your SIP Recording Routing rules (configured in ''Configuring SIP Recording Routing Rules'' on page 214) become active.

  • Page 215: Configuring Sip User Part For Srs

    Open the SIP Recording page (Configuration tab > VoIP menu > Services > SIP Recording). In the 'Recording Server (SRS) Destination Username' field, enter a user part value (string of up to 50 characters). Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...

  • Page 216: Interworking Sip-Based Media Recording With Third-Party Vendors

    SIP message, typically in the INVITE and the first 18x response. If the device receives a SIP message with Genesys SIP header, it adds the header's information to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server, as shown below: <ac:GenesysUUID...

  • Page 217: Radius Authentication

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

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

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

  • Page 219: Configuring Radius Authentication

    RADIUS Server' on page 218. • If the RADIUS server response does not include the access level attribute: In the 'Default Access Level' field, enter the default access level that is applied to all users authenticated by the RADIUS server. Version 6.8 Mediant 3000...

  • Page 220: Securing Radius Communication

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

  • Page 221: Ldap-Based Management And Sip Services

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

  • Page 222: Enabling The Ldap Service

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

  • Page 223: Configuring Ldap Servers

    Services > LDAP > LDAP Configuration Table). Click Add; the following dialog box appears: Figure 16-6: LDAP Configuration Table - Add Record Configure an LDAP server according to the parameters described in the table below. Click Submit. Version 6.8 Mediant 3000...
  • Page 224 Mediant 3000 LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [LdapConfiguration_In Note: Each table row must be configured with a unique index. dex] LDAP Server IP Defines the IP address of the LDAP server (in dotted-decimal notation, CLI: server-ip e.g., 192.10.1.255).
  • Page 225 (i.e., the 'Type' parameter is set to Management).  If this functionality is not used, the device assigns the user the configured default access level. For more information, see 'Configuring Access Level per Management Groups Attributes' on page 228. Version 6.8 Mediant 3000...

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

    Mediant 3000 Parameter Description Use SSL Enables the device to encrypt the username and password (for Control CLI: and Management related queries) using TLS when sending them to the [LdapConfiguration_us LDAP server. eTLS]  [0] No = (Default) Username and password are sent in clear-text format.

  • Page 227: Configuring The Ldap Search Filter Attribute

    The search filter is applicable only to LDAP-based login authentication and authorization queries. • The search filter is a global setting that applies to all LDAP-based login authentication and authorization queries, across all configured LDAP servers. Version 6.8 Mediant 3000...

  • Page 228: Configuring Access Level Per Management Groups Attributes

    Mediant 3000  To configure the LDAP search filter for management users: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 16-8: LDAP Settings Page - LDAP Search Filter Under LDAP Settings, in the 'LDAP Authentication Filter' parameter, enter the LDAP search filter attribute for searching the login username for user authentication.
  • Page 229 Defines an index number for the new table record. [MgmntLDAPGroups_ Note: Each table row must be configured with a unique index. GroupIndex] Level Defines the access level of the group(s). [MgmntLDAPGroups_L  [0] Operator (Default) evel]  [1] Admin  [2] Security Admin Version 6.8 Mediant 3000...

  • Page 230: Configuring Ldap Search Methods

    Mediant 3000 Parameter Description Groups Defines the attribute names of the groups in the LDAP server. [MgmntLDAPGroups_ The valid value is a string of up to 256 characters. To define multiple Group] groups, separate each group name with a semicolon (;).
  • Page 231 If for the first LDAP query, the result fails for at least one attribute and is successful for at least one, the partial result is cached. However, for subsequent queries, the device does not use the partially cached result, but does a new query with the LDAP server again. Version 6.8 Mediant 3000...
  • Page 232 Mediant 3000 The following procedure describes how to configure the device's LDAP cache in the Web interface. For a full description of the cache parameters, see 'LDAP Parameters' on page 962.  To configure the LDAP cache: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP >...

  • Page 233: Configuring Local Database For Management User Authentication

    Server Timeout' drop-down list, select one of the following: ♦ Deny Access: User is denied access to the management platform. ♦ Verify Access Locally (default): The device verifies the user's credentials in the Web Users table. Click Submit. Version 6.8 Mediant 3000...

  • Page 234: Ldap-Based Login Authentication Example

    Mediant 3000 16.3.10 LDAP-based Login Authentication Example To facilitate your understanding on LDAP entry data structure and how to configure the device to use and obtain information from this LDAP directory, a brief configuration example is described in this section. The example applies to LDAP-based user login authentication and authorization (access level), and assumes that you are familiar with other aspects of LDAP configuration (e.g., LDAP server's address).
  • Page 235 (where the attribute's value equals the username): Figure 16-15: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 16-16: User's memberOf Attribute Version 6.8 Mediant 3000...
  • Page 236 Mediant 3000  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 16-17: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
  • Page 237 The management group and its corresponding access level is configured in the Management LDAP Groups table (see 'Configuring Access Level per Management Groups Attributes' on page 228): Figure 16-21: Configuring Management Group Attributes for Determining Access Level Version 6.8 Mediant 3000...

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

    Mediant 3000 16.3.11 Active Directory-based Routing for Microsoft Lync Typically, enterprises wishing to deploy the Microsoft® Lync™ Server are faced with a complex, call routing dial plan when migrating users from their existing PBX or IP PBX to the Lync Server platform. As more and more end-users migrate to the new voice system, dialing plan management and PBX link capacity can be adversely impacted.
  • Page 239 Mediation Server (which then routes the call to the Lync client). PBX / IP PBX: If the Lync client is not found in the AD, it routes the call to the PBX / IP PBX. Version 6.8 Mediant 3000...
  • Page 240 Mediant 3000 Mobile number: If the Lync client (or Mediation Server) is unavailable (e.g., SIP response 404 "Not Found" upon INVITE sent to Lync client), and the PBX / IP PBX is also unavailable, the device routes the call to the user's mobile number (if exists in the AD).

  • Page 241: Configuring Ad-Based Routing Rules

    "LDAP" for denoting the IP address of the LDAP server. For alternative routing, enable the alternative routing mechanism and configure corresponding SIP reasons for alternative routing. For this feature, alternative routing starts from the table row located under the LDAP query row. Version 6.8 Mediant 3000...
  • Page 242 Mediant 3000 SBC application: Configure AD-based IP-to-IP routing rules: Open the IP-to-IP Routing Table page (Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table). For more information, see Configuring SBC IP-to-IP Routing Rules. Configure query-result routing rules for each IP domain (private, PBX / IP PBX,...

  • Page 243: Querying The Ad For Calling Name

    If the source (calling) number of the Tel-to-IP call matches the PBX / MOBILE (e.g., "telephoneNumber" and "mobile") number in the AD server, the device uses the resultant Display Name instead of the keyword(s). Version 6.8 Mediant 3000...

  • Page 244: Least Cost Routing

    Mediant 3000 For example, assume the following configuration in the Calling Name Manipulation Table for Tel-to-IP Calls:  'Source Prefix' field is set to "4".  'Prefix to Add' field is set to "$LDAP-PBX Office". If the calling number is 4046 and the resultant LDAP query display name is "John Doe", the device sends the INVITE message with the following From header: From: John Doe <sip:4064@company.com>...
  • Page 245 LCR routing rules (with Cost Groups assigned), the routing rule without a Cost Group is considered the lowest cost route. • The following Cost Groups are configured: Cost Group Connection Cost Minute Cost 1. "A" 2. "B" Version 6.8 Mediant 3000...
  • Page 246 Mediant 3000 • The Cost Groups are assigned to routing rules: Routing Index Dest Phone Prefix Destination IP Cost Group x.x.x.x "A' x.x.x.x "B" x.x.x.x x.x.x.x "B" The device calculates the optimal route in the following index order: 3, 1, 2, and then 4, due to the following logic: •...

  • Page 247: Configuring Lcr

    Table 16-3: Routing Rule Groups Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [RoutingRuleGroups_Index] Note: Only one index entry can be configured. LCR Enable Enables the LCR feature: [RoutingRuleGroups_LCREnable]  [0] Disabled (default)  [1] Enabled Version 6.8 Mediant 3000...

  • Page 248: Configuring Cost Groups

    Mediant 3000 Parameter Description LCR Call Length Defines the average call duration (in minutes) and is used to [RoutingRuleGroups_LCRAverage calculate the variable portion of the call cost. This is useful, for CallLength] example, when the average call duration spans over multiple time bands.

  • Page 249: Configuring Time Bands For Cost Groups

    Select a Cost Group for which you want to assign Time Bands, and then click the Time Band link located below the table; the Time Band table for the selected Cost Group appears. Click Add; the following dialog box appears: Version 6.8 Mediant 3000...

  • Page 250: Assigning Cost Groups To Routing Rules

    Mediant 3000 Configure a Time Band according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 16-5: Time Band Table Description Parameter Description Index Defines an index number for the new table record.

  • Page 251: Configuring Call Setup Rules

    SBC IP-to-IP routing - see Configuring SBC IP-to-IP Routing Rules on page  Tel-to-IP routing rules - see Configuring Outbound IP Routing Table on page  IP-to-Tel routing rules - see ''Configuring Inbound IP Routing Table'' on page Version 6.8 Mediant 3000...
  • Page 252 Mediant 3000 If an incoming call matches the characteristics of a routing rule, the device first runs the assigned Call Setup Rules Set ID. The device uses the routing rule to route the call, depending on the result of the Call Setup Rules Set ID: ...
  • Page 253 [1] Use Previous Condition = The Condition configured for the rule located directly above this rule in the Call Setup table must be matched in order to perform the configured action. This option lets you configure multiple actions for the same Condition. Version 6.8 Mediant 3000...
  • Page 254 Mediant 3000 Parameter Description Condition Defines the condition that must exist for the device to [CallSetupRules_Condition] perform the action. The valid value is a string of up to 200 characters (case- insensitive). Regular Expression (regex) can also be used, for example: ...

  • Page 255: Call Setup Rule Examples

    Call Setup Rules table configuration: ♦ 'Rules Set ID': 2 ♦ 'Attributes to Query': ‘telephoneNumber=’ + param.call.src.user ♦ 'Attributes to Get': displayName ♦ 'Row Role': Use Current Condition ♦ 'Condition': ldap.attr. displayName exists ♦ 'Action Subject': param.call.src.name Version 6.8 Mediant 3000...
  • Page 256 Mediant 3000 ♦ 'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName • Routing table configuration: A single routing rule is assigned the Call Setup Rule Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 2  Example 3: This example configures the device to route the incoming call according to whether or not the source number of the incoming call also exists in the AD server.

  • Page 257: Quality Of Experience

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

  • Page 258: Configuring Clock Synchronization Between Device And Sem

    In other words, you need to configure them with the same NTP server. The NTP server can be one of the following:  AudioCodes EMS server (also acting as an NTP server)  Third-party, external NTP server Once you have determined the NTP server, all the elements--device, SEM, and EMS--must be configured with the same NTP server address.
  • Page 259  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 258.
  • Page 260 Mediant 3000 Configure a QoE Profile according to the parameters described in the table below. Click Submit. Table 17-1: Quality of Experience Profile Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [QOEProfile_Index] Profile Name Defines an arbitrary name to easily identify the QoE Profile.
  • Page 261 SEM indicating this change. Note: If the monitored parameter crosses two thresholds at once (e.g., from Green to Red), the device ignores the hysteresis value and reports the call state change to the SEM. Version 6.8 Mediant 3000...

  • Page 262: Configuring Bandwidth Profiles

    Mediant 3000 Parameter Description Yellow Red Threshold Defines the parameter threshold values between Yellow [QOEColorRules_YellowRedThres (medium quality) and Red (poor quality) states. hold] The valid threshold values are as follows:  MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.
  • Page 263 Defines the outgoing video traffic threshold (in Kbps). [BWProfile_EgressVideoBandwidth] Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth [BWProfile_TotalEgressBandwidth] threshold (in Kbps). Version 6.8 Mediant 3000...
  • Page 264 Mediant 3000 Parameter Description Total Ingress Bandwidth Defines the total (video and audio) incoming bandwidth [BWProfile_TotalIngressBandwidth] threshold (in Kbps). Warning Threshold Defines the threshold (in percentage) of the bandwidth [BWProfile_WarningThreshold] thresholds that if exceeded is considered a Warning alarm (Green-Yellow threshold). This applies to any of the configured bandwidth thresholds.

  • Page 265: Configuring Media Enhancement Profiles

    The following procedure describes how to configure Media Enhancement Profiles in the Web interface. You can also configure Media Enhancement Profiles using other management platforms:  Media Enhancement Profile table: Table ini file parameter, MediaEnhancementProfile  Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules Version 6.8 Mediant 3000...
  • Page 266 Mediant 3000  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Click Add; the following dialog box appears: Figure 17-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below.
  • Page 267 Defines an alternative IP Profile ID for the IP Group that is associated [MediaEnhancementRules with this rule, if this rule is applied. This parameter is applicable only if _ActionValue] the 'Rule Action' parameter is set to Alternative IP Profile. Version 6.8 Mediant 3000...
  • Page 268 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 269: Control Network

    The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm. Version 6.8 Mediant 3000...
  • Page 270 Mediant 3000  To configure a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > VoIP Network > Media Realm Configuration). Click Add; the following dialog box appears: Figure 18-1: Media Realm Page - Add Record Dialog Box Configure the Media Realm according to the parameters described in the table below.
  • Page 271 6000, the RTCP port and T.38 port for the session is 6001 and 6002, respectively. However, you can configure the device to use the same port for RTP and T.38 packets, by setting the T38UseRTPPort parameter to 1. Version 6.8 Mediant 3000...

  • Page 272: Configuring Remote Media Subnets

    Mediant 3000 Parameter Description Default Media Realm Defines the Media Realm as the default Media Realm. This [CpMediaRealm_IsDefault] default Media Realm is used when no Media Realm is configured for an IP Group or SRD for a specific call. ...
  • Page 273 Click Add; the following dialog box appears: Figure 18-3: Remote Media Subnet - Add Record Configure the Remote Media Subnet according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...
  • Page 274 Mediant 3000 Table 18-2: Remote Media Subnet Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [RemoteMediaSubnet_Remote MediaSubnetIndex] Sub-Realm Name Defines an arbitrary name to easily identify the Remote Media [RemoteMediaSubnet_Remote Subnet. MediaSubnetName] The valid value is a string of up to 20 characters.

  • Page 275: Configuring Srds

    Gateway application and Configuring SBC IP-to-IP Routing Rules on page for the SBC application) The following procedure describes how to configure SRDs in the Web interface. You can also configure this using the table ini file parameter, SRD. Version 6.8 Mediant 3000...
  • Page 276 Mediant 3000  To configure an SRD: Open the SRD Table page (Configuration tab > VoIP menu > VoIP Network > SRD Table). Click Add; the following dialog box appears: Figure 18-4: SRD Settings Page Configure an SRD according to the parameters described in the table below.
  • Page 277 500 "Server Internal Error" response to the remote end. Max. Number of Registered Users Maximum number of users belonging to this SRD that [SRD_MaxNumOfRegUsers] can register with the device. By default, no limitation exists for registered users Version 6.8 Mediant 3000...
  • Page 278 Mediant 3000 Parameter Description Enable Un-Authenticated Registrations Enables the device to accept REGISTER requests and [SRD_EnableUnAuthenticatedRegistrations] register them in its registration database from new users that have not been authenticated by a proxy/registrar server (due to proxy down) and thus, re- routed to a User-type IP Group.

  • Page 279: Configuring Sip Interfaces

    Open the SIP Interface Table page (Configuration tab > VoIP menu > VoIP Network > SIP Interface Table). Click Add; the following dialog box appears: Configure a SIP Interface according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...
  • Page 280 Mediant 3000 Table 18-4: SIP Interface Table Parameter Descriptions Parameter Description Index Defines an index for the new table record. [SIPInterface_Index] The valid value is 0 to 31. Interface Name Defines an arbitrary name to easily identify the SIP Interface.
  • Page 281 SIP request (OPTIONS, REGISTER, or INVITE) has [SIPInterface_ClassificationFailure failed the SBC Classification process. ResponseType] The valid value can be a SIP response code from 400 through 699, or it can be set to 0 to not send any response at all. The Version 6.8 Mediant 3000...
  • Page 282 Mediant 3000 Parameter Description default response code is 500 (Server Internal Error). This feature is important for preventing Denial of Service (DoS) attacks, typically initiated from the WAN. Malicious attackers can use SIP scanners to detect ports used by SIP devices.

  • Page 283: Configuring Ip Groups

    If different SRDs are configured in the IP Group and Proxy Set tables, the SRD defined for the Proxy Set takes precedence. The following procedure describes how to configure IP Groups in the Web interface. You can also configure IP Groups using the table ini file parameter, IPGroup. Version 6.8 Mediant 3000...
  • Page 284 Mediant 3000  To configure an IP Group: Open the IP Group Table page (Configuration tab > VoIP menu > VoIP Network > IP Group Table). Click Add; the following dialog box appears: Figure 18-5: IP Group Table - Add Dialog Box Configure an IP Group according to to the parameters described in the table below.
  • Page 285 SIP Group Name Defines the SIP Request-URI host name in INVITE and REGISTER [IPGroup_SIPGroupName] messages sent to this IP Group, or the host name in the From header of INVITE messages received from this IP Group. In other Version 6.8 Mediant 3000...
  • Page 286 Mediant 3000 Parameter Description words, it replaces the original host name. The valid value is a string of up to 100 characters. The default is an empty field. Notes:  If this parameter is not configured, the value of the global parameter, ProxyName is used instead (see ''Configuring Proxy and Registration Parameters'' on page 307).
  • Page 287 Assigns a Bandwidth Profile rule. For configuring Bandwidth [IPGroup_BWProfile] Profiles, see ''Configuring Bandwidth Profiles'' on page 262. Media Enhancement Profile Assigns a Media Enhancement Profile rule. For configuring Media [IPGroup_MediaEnhancement Enhancement Profiles, see ''Configuring Media Enhancement Profiles'' on page 265. Profile] Version 6.8 Mediant 3000...
  • Page 288 Mediant 3000 Parameter Description Always Use Source Address Enables the device to always send SIP requests and responses, [IPGroup_AlwaysUseSourceA within a SIP dialog, to the source IP address received in the ddr] previous SIP message packet. This feature is especially useful in...
  • Page 289 [2] Always Enable = Survivability mode is always enabled. The communication with the Serving IP Group is always considered as failed. The device uses its database for routing calls between the clients of the User-type IP Group. Version 6.8 Mediant 3000...
  • Page 290 Mediant 3000 Parameter Description  [3] Always Terminate Register = The registration messages received from the clients are saved in the device's registration database without forwarding them to the proxy server. Upon receipt of the registration message, the device returns a SIP 200 OK to the client.
  • Page 291 IPGroup_InboundManSet parameter) that manipulate the host name in Request-URI, To, and/or From SIP headers. If you want to manipulate the host name using message manipulation rules in any of these SIP headers, you must apply your manipulation rule Version 6.8 Mediant 3000...
  • Page 292 Mediant 3000 Parameter Description (Manipulation Set ID) to the IP Group as an Outbound Message Manipulation Set (see the IPGroup_OutboundManSet parameter), when the IP Group is the destination of the call. Outbound Message Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the outbound message.
  • Page 293 INVITE to an IP Group (source IP Group) in the Classification table. Once classified, the device uses the parameter for routing the call. For example, if set to To, the URI in Version 6.8 Mediant 3000...
  • Page 294 Mediant 3000 Parameter Description the To header of the incoming INVITE is used as a matching characteristic for classifying the call to an IP Group in the Classification table. Once classified, the device uses the URI in the To header as the destination.
  • Page 295 'Authentication Mode' parameter is set to SBC as Server (i.e., authentication of servers).  To specify the SIP request types (e.g., INVITE) that must be challenged by the device, use the 'Authentication Method List' parameter. Version 6.8 Mediant 3000...

  • Page 296: Configuring Proxy Sets

    Mediant 3000 18.6 Configuring Proxy Sets The Proxy Sets table lets you configure up to 100 Proxy Sets. A Proxy Set defines the destination address (IP address or FQDN) and transport type (e.g., UDP) of a SIP server (e.g., Proxy). Each Proxy Set can be configured with up to 10 addresses configured as an IP address and/or DNS host name (FQDN), enabling you to implement load balancing and redundancy between multiple servers.
  • Page 297 The address can be defined as an IP address in dotted-decimal notation (e.g., 201.10.8.1) or FQDN. You can also specify the port in the following format:  IPv4 address: <IP address>:<port> (e.g., 201.10.8.1:5060)  IPv6 address: <[IPV6 address]>:<port> (e.g., [2000::1:200:200:86:14]:5060) Version 6.8 Mediant 3000...
  • Page 298 Mediant 3000 Parameter Description Transport Type Defines the transport type for communicating with the Proxy server. [ProxyIp_TransportType]  [0] UDP  [1] TCP  [2] TLS  [-1] = Undefined Note: If this parameter is not defined, the settings of the global parameter SIPTransportType is used.
  • Page 299 The valid range is -1 to 255. The default is -1 (i.e., the settings of [ProxySet_FailureDetectionRetr the global parameter SIPMaxRtxis applied). ansmissions] Note: The parameter is applicable only if the 'Proxy Keep-Alive' parameter is set to Using Options. Version 6.8 Mediant 3000...
  • Page 300 Mediant 3000 Parameter Description Web: Proxy Load Balancing Enables the Proxy Load Balancing mechanism per Proxy Set. Method  [0] Disable = Load Balancing is disabled (default) EMS: Load Balancing Method  [1] Round Robin = A list of all possible Proxy IP addresses is [ProxySet_ProxyLoadBalanci compiled.
  • Page 301 'Transport Type' parameter is set to UDP, the device uses UDP to communicate with the proxy and no TLS Context is used. For more information about how certificates are associated with calls and for configuring TLS Contexts, see Configuring SSL/TLS Certificates on page 109. Version 6.8 Mediant 3000...
  • Page 302 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 303: Sip Definitions

    'UserName' and 'Password' parameters on the Proxy & Registration page The following procedure describes how to configure Accounts in the Web interface. You can also configure Accounts using the table ini file parameter, Account. Version 6.8 Mediant 3000...
  • Page 304 Mediant 3000  To configure an Account: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Configure an account according to the parameters described in the table below.
  • Page 305  If this parameter is not configured, the 'Contact User' parameter in the IP Group table is used instead.  If registration fails, the user part in the INVITE Contact header contains the source party number. Version 6.8 Mediant 3000...

  • Page 306: Regular Registration Mode

    Mediant 3000 Parameter Description Application Type Defines the application type: [Account_ApplicationType]  [0] GW/IP2IP = (Default) Gateway and IP-to-IP application.  [2] SBC = SBC application. 19.2.1 Regular Registration Mode When you configure the registration mode in the Account table to Regular, the device sends REGISTER requests to the Serving IP Group.

  • Page 307: Configuring Proxy And Registration Parameters

    For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 727. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see ''Viewing Registration Status'' on page 660. Version 6.8 Mediant 3000...
  • Page 308 Mediant 3000  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Configure the parameters as required. Click Submit.  To register or un-register the device to a Proxy/Registrar: ...

  • Page 309: 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 310 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.80.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”, nonce="11432d6bce58ddf02e3b5e1c77c010d2",...

  • Page 311: Configuring Sip Message Manipulation

    P-Asserted-Identity header can be copied to the From header), call's parameter values  Deletion of SIP body (e.g., if a message body is not supported at the destination network this body is removed)  Translating one SIP response code to another Version 6.8 Mediant 3000...
  • Page 312 Mediant 3000  Topology hiding (generally present in SIP headers such as Via, Record Route, Route and Service-Route).  Configurable identity hiding (information related to identity of subscribers, for example, P-Asserted-Identity, Referred-By, Identity and Identity-Info)  Apply conditions per rule - the condition can be on parts of the message or call’s parameters ...
  • Page 313 Click Add; the following dialog box appears: Figure 19-3: Message Manipulations Table - Add Record Dialog Box Configure a Message Manipulation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...
  • Page 314 Mediant 3000 An example of configured message manipulation rules are shown in the figure below: Figure 19-4: Message Manipulations Page  Index 0: Adds the suffix ".com" to the host part of the To header.  Index 1: Changes the user part of the From header to the user part of the P-Asserted- ...
  • Page 315 Current Condition is used. For example, if Index 3 is configured to Use Current Condition and Index 4 and 5 are configured to Use Previous Condition, Index 4 and 5 use the condition configured for Index 3. A configuration example Version 6.8 Mediant 3000...
  • Page 316 Mediant 3000 Parameter Description is shown in the beginning of this section. The option allows you to use the same condition for multiple manipulation rules. Notes:  When configured to Use Previous Condition, the 'Message Type' and 'Condition' parameters are not applicable and if configured are ignored.

  • Page 317: Configuring Sip Message Policy Rules

    Click Add; the following dialog box appears: Figure 19-5: Message Policy Table - Add Record Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...
  • Page 318 Mediant 3000 Table 19-3: Message Policy Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [MessagePolicy_Index] Max Message Length Defines the maximum SIP message length. [MessagePolicy_MaxMessageLength] The valid value is up to 32,768 characters. The default is 32,768.
  • Page 319 CLI: body-list-type specified in the 'Body List' parameter (above). [MessagePolicy_BodyListType]  [0] Policy Blacklist =The specified SIP body is rejected.  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; the others are rejected. Version 6.8 Mediant 3000...
  • Page 320 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 321: Coders And Profiles

    Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 20-1: Coders Table Page Configure coders according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Version 6.8 Mediant 3000...
  • Page 322 Mediant 3000 Table 20-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder. [CodersGroup0_Name] Note: Each coder type (e.g., G.729) can be configured only once in the table. Packetization Time Defines the packetization time (in msec) for the coder. The...
  • Page 323 [6] 19.85  [7] 23.05  [8] 23.85 (default)   [0] Variable [0] Disable EVRC 20 (default), 40,60, 80, Dynamic (0- (default) [Evrc] 127)  [1] Enable  [1] 1/8  [3] 1/2  [4] Full Version 6.8 Mediant 3000...
  • Page 324 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 325: Configuring Coder Groups

    Profiles > Coders Group Settings). Figure 20-2: Coder Group Settings Page Configure the Coder Group according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Version 6.8 Mediant 3000...

  • Page 326: Configuring Tel Profile

    Mediant 3000 Table 20-3: Coder Group Settings Table Parameter Descriptions Parameter Description Coder Group ID Defines an ID for the Coder Group. [CodersGroupX_Index] Coder Name Defines the coder type. [CodersGroupX_Name] Note: Each coder type (e.g., G.729) can be configured only once in the table.
  • Page 327 3. If the coder lists of both the IP Profile and Tel Profile apply to the same call, only the coders common to both are used. The order of the coders is determined by the preference. Web: Fax Signaling Method IsFaxUsed [TelProfile_IsFaxUsed] Version 6.8 Mediant 3000...
  • Page 328 Mediant 3000 Tel Profile Parameter Global Parameter Web: Enable Digit Delivery EnableDigitDelivery [TelProfile_EnableDigitDelivery] Web: Time For Reorder Tone TimeForReorderTone [TelProfile_TimeForReorderTone] Web: Disconnect Call on Detection of DisconnectOnBusyTone Busy Tone [TelProfile_DisconnectOnBusyTone] Web: Enable Voice Mail Delay VoiceMailInterface This is useful for disabling voice mail services per Trunk...

  • Page 329: Configuring Ip Profiles

    IP Profile that you assigned in the IP Group table.  If you assign different IP Profiles to all of the above-mentioned tables and one table is set to the default IP Profile, the device uses the IP Profile that is not the default. Version 6.8 Mediant 3000...

  • Page 330: Mediant

    Mediant 3000 Many of the parameters in the IP Profile table have a corresponding "global" parameter. For calls that are not associated with any IP Profile, the settings of the "global" parameters are applied. Note: IP Profiles can also be implemented when using a Proxy server (when the AlwaysUseRouteTable parameter is set to 1).
  • Page 331 Note: The corresponding global parameter is PremiumServiceClassMediaDiffServ. Web: Signaling DiffServ Defines the DiffServ value for Premium Control CoS content (Call [IpProfile_SigIPDiffServ] Control applications). The valid range is 0 to 63. The default is 40. Note: The corresponding global parameter is PremiumServiceClassControlDiffServ. Version 6.8 Mediant 3000...
  • Page 332 Mediant 3000 Parameter Description Web: RTP Redundancy Depth Enables the device to generate RFC 2198 redundant packets. [IpProfile_RTPRedundancyDep This can be used for packet loss where the missing information (audio) can be reconstructed at the receiver's end from the redundant data that arrives in subsequent packets. This is required, for example, in wireless networks where a high percentage (up to 50%) of packet loss can be experienced.
  • Page 333 [1] Enable = The answer crypto line contains (or excludes) an MKI value according to the selected crypto line in the offer. For example, assume that the device receives an INVITE containing the following two crypto lines in SDP: a=crypto:2 AES_CM_128_HMAC_SHA1_80 Version 6.8 Mediant 3000...
  • Page 334 Mediant 3000 Parameter Description inline:TAaxNnQt8/qLQMnDuG4vxYfWl6K7eBK/ufk04pR 4|2^31|1:1 a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:bnuYZnMxSfUiGitviWJZmzr7OF3AiRO0l5Vnh0k H|2^31 The first crypto line includes the MKI parameter "1:1". In the 200 OK response, the device selects one of the crypto lines (i.e., '2' or '3'). Typically, it selects the first line that supports the crypto suite.
  • Page 335 Enables the detection of the fax calling tone (CNG) and defines [IpProfile_CNGmode] the detection method.  [0] Disable = (Default) The originating fax does not detect CNG; the device passes the CNG signal transparently to the remote side. Version 6.8 Mediant 3000...
  • Page 336 Mediant 3000 Parameter Description  [1] Relay = The originating fax detects CNG. The device sends CNG packets to the remote side according to T.38 (if IsFaxUsed is set to 1) and the fax session is started. A SIP Re-INVITE message is not sent and the fax session starts by the terminating fax.
  • Page 337 It is sent only if PI is set to 1 or 8 in the received Proceeding or Alerting PRI messages. Sending 183 response also depends on the ReleaseIP2ISDNCallOnProgressWithCause parameter, which must be set to any value other than 2.  See also the IgnoreAlertAfterEarlyMedia parameter. This Version 6.8 Mediant 3000...
  • Page 338 Mediant 3000 Parameter Description parameter allows, for example, to interwork Alert with PI to SIP 183 with SDP instead of 180 with SDP.  You can also configure early SIP 183 response immediately upon the receipt of an INVITE, using the EnableEarly183 parameter.
  • Page 339 [1] INFO (Nortel) = Sends DTMF digits according to IETF Internet-Draft draft-choudhuri-sip-info-digit-00.  [2] NOTIFY = Sends DTMF digits according to IETF Internet- Draft draft-mahy-sipping-signaled-digits-01.  [3] INFO (Cisco) = Sends DTMF digits according to the Cisco format. Version 6.8 Mediant 3000...
  • Page 340 Mediant 3000 Parameter Description  [4] RFC 2833 (Default) = The device:  negotiates RFC 2833 payload type using local and remote SDPs.  sends DTMF packets using RFC 2833 payload type according to the payload type in the received SDP.
  • Page 341 (16 sensitivity levels, from 0 to 15). This requires a customized AMD Sensitivity file that needs to be installed on the device. For more information, contact your AudioCodes sales representative. Notes:  To configure the detection sensitivity level, use the 'AMD Sensitivity Level' parameter.
  • Page 342 Mediant 3000 Parameter Description call upon detection of an answering machine.  [1] Disconnect on AMD = Device disconnects call upon detection of an answering machine. It disconnects the call only after receipt of an ISDN Connect from the Tel side. In such a...
  • Page 343 SDP 'm=' line (e.g., 'm=audio'). The device permits only media types that appear in both the SDP offer and this configured list. If no common media types exist between the SDP offer and this list, the device drops the call. Version 6.8 Mediant 3000...
  • Page 344 Mediant 3000 Parameter Description The valid value is a string of up to 64 characters. To configure multiple media types, separate the strings with a comma, e.g., "media, audio" (without quotes). By default, no media types are configured (i.e., all media types are permitted).
  • Page 345 [1] Add = Adds a P-Asserted-Identity header. The header's values are taken from the source URL.  [2] Remove = Removes the P-Asserted-Identity header. Notes:  This parameter affects only the initial INVITE request.  The corresponding global parameter is SBCAssertIdentity. Version 6.8 Mediant 3000...
  • Page 346 Mediant 3000 Parameter Description Web: Diversion Mode Defines the device’s handling of the SIP Diversion header for this [IpProfile_SBCDiversionMode] SIP entity. For more information on interworking of the History- Info and Diversion headers, see Interworking SIP Diversion and History-Info Headers on page 506.
  • Page 347 PRACK are rejected. Calls destined to these endpoints are also required to support PRACK.  [3] Transparent (default) = The device does not intervene with the PRACK process and forwards the request as is. Version 6.8 Mediant 3000...
  • Page 348 Mediant 3000 Parameter Description Web: Session Expires Mode Defines the required session expires mode for this SIP entity. [IpProfile_SBCSessionExpiresMo  [0] Transparent = (Default) The device does not interfere with the session expires negotiation.  [1] Observer = If the SIP Session-Expires header is present, the device does not interfere, but maintains an independent timer for each leg to monitor the session.
  • Page 349 IP-to-IP Routing table (the 'Call Trigger' field must be set to 3xx). Notes:  When this parameter is changed from 1 to 0, new 3xx Contact headers remain unchanged. However, requests with the Version 6.8 Mediant 3000...
  • Page 350 Mediant 3000 Parameter Description special prefix continue using the device's database to locate the new destination.  Only one database entry is supported for the same host, port, and transport combination. For example, the following URLs cannot be distinguished by the device: ...
  • Page 351 'SBC Remote Hold Format' parameter is set to send- only, send only 0.0.0.0, or not supported. Web: Remote Hold Format Defines the format of the SDP in the re-INVITE for call hold that [IPProfile_SBCRemoteHoldForm the device sends to the held party. Version 6.8 Mediant 3000...
  • Page 352 Mediant 3000 Parameter Description  [0] Transparent = Device forwards SDP as is.  [1] Send Only = Device sends SDP with 'a=sendonly'.  [2] Send Only Zero ip = Device sends SDP with 'a=sendonly' and 'c=0.0.0.0'.  [3] Inactive = Device sends SDP with 'a=inactive'.
  • Page 353 (enabling ptime transrating if the other side uses a different ptime). If the 'SDP Ptime Answer' parameter is configured to Remote Answer [0] or Original Offer [1] and the 'Preferred Ptime' parameter is configured to a non-zero value, the configured value Version 6.8 Mediant 3000...
  • Page 354 Mediant 3000 Parameter Description is used as the ptime in the SDP offer. The valid range is 0 to 200. The default is 0 (i.e., a preferred ptime is not used). Web: Use Silence Suppression Defines silence suppression support for this SIP entity.
  • Page 355 Delay' (DJBufMinDelay) and 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed.  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. Version 6.8 Mediant 3000...
  • Page 356 Mediant 3000 Parameter Description Web: Remote Renegotiate on Enables local handling of fax detection and negotiation by the Fax Detection device on behalf of the SIP entity (to which the IP Profile is assigned). This applies to faxes sent immediately upon the CLI: sbc-rmt-renegotiate-on-fax- establishment of a voice channel (i.e., after 200 OK).

  • Page 357: Gateway Application

    Part V Gateway Application...

  • Page 359: 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.8 Mediant 3000...
  • Page 360 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 361: Digital Pstn

    E1 Euro ISDN and E1 CAS (subject to the constraints in the device's Release Notes). • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk. Version 6.8 Mediant 3000...
  • Page 362 Mediant 3000  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). Figure 22-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 363: Tdm And Timing

    For a description of these parameters, see ''PSTN Parameters'' on page 865.  To configure the TDM Bus settings: Open the TDM page (Configuration tab > VoIP menu > TDM & Timing > TDM). Configure the parameters as required. Click Submit. Version 6.8 Mediant 3000...

  • Page 364: Configuring Digital Pcm Settings

    Mediant 3000 Save the changes to flash memory, see ''Saving Configuration'' on page 580. 22.2.2 Configuring Digital PCM Settings The Digital PCM Settings page allows you to configure the PCM companding law in input/output TDM bus, and PCM and ABCD patterns. For a description of these parameters, see ''PSTN Parameters'' on page 865.

  • Page 365: Clock Settings

    (TMMode) to LineSync to use the line interface clock. For E1/T1 trunks only: Set the PSTN trunk to recover/derive clock from/to the remote side of the PSTN trunk (i.e. clock slave or clock master): In the Trunk Settings page, Version 6.8 Mediant 3000...

  • Page 366: Configuring Bits Synchronization Mode

    Mediant 3000 set the 'Clock Master' parameter (ClockMaster) to one of the following: • Recovered - to recover clock (i.e. slave) • Generated - to transmit clock (i.e. master) Notes: • When operating with SDH/OC-3 PSTN, the following parameters are not applicable: 'TDM Bus Local Reference', 'TDM Bus PSTN Auto FallBack Clock', 'Auto Clock Trunk Priority', and 'TDM Bus PSTN Auto Clock Reverting'.

  • Page 367: Configuring Internal Clock As Clock Source

    For E1/T1 trunks only, set the line to drive the clock on all trunks: In the Trunk Settings page, set the 'Clock Master' parameter (ClockMaster) to Generated (for all trunks). If the device has BITS capability, then in the System Timing page, set the 'Timing Module Mode' parameter (TMMode) to StandAlone (default). Version 6.8 Mediant 3000...

  • Page 368: Configuring Transmission Settings

    T3/DS3 or SONET/SDH). For a description of the parameters related to transmission type, see ''PSTN Parameters'' on page 865. Notes: • Transmission settings are applicable only to Mediant 3000 with TP-6310. • When applying your settings, traffic disturbances may be experienced. ...

  • Page 369: Configuring Cas State Machines

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

  • Page 371: Configuring Digital Gateway Parameters

    [-1] Default = Default value - use value from CAS state machine. 22.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 727. Version 6.8 Mediant 3000...
  • Page 372 Mediant 3000  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab > VoIP menu > GW and IP to IP > Digital Gateway > Digital Gateway Parameters). Figure 22-8: Digital Gateway Parameters Page Configure the parameters as required.

  • Page 373: Tunneling Applications

    By utilizing the ‘Profiles’ mechanism (see ''Coders and Profiles'' on page 321), you can configure the TDM Tunneling feature to choose different settings based on a timeslot or groups of timeslots. For example, you can use low-bit-rate vocoders to transport voice and Version 6.8 Mediant 3000...
  • Page 374 Mediant 3000 ‘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.
  • Page 375 FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce; 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, Version 6.8 Mediant 3000...

  • Page 376: Dsp Pattern Detector

    Mediant 3000 TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 22.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 377 INFO message with Setup Ack encapsulated in its MIME body. The PBX sends QSIG Information messages (to complete the Called Party Number) only after it receives the Setup Ack. The device relays these Information messages encapsulated in SIP INFO messages to the remote party. Version 6.8 Mediant 3000...

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

    Mediant 3000 22.7 ISDN Non-Facility Associated Signaling (NFAS) In regular T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B- channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24. ISDN Non-Facility Associated Signaling (NFAS) enables the use of a single D-channel to control multiple PRI interfaces.

  • Page 379: Working With Dms-100 Switches

    NFASGroupNumber_0 = 1 NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1 NFASGroupNumber_3 = 1 DchConfig_0 = 0 ;Primary T1 trunk DchConfig_1 = 2 ;B-Channel NFAS trunk DchConfig_2 = 2 ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk Version 6.8 Mediant 3000...

  • Page 380: Creating An Nfas-Related Trunk Configuration

    Mediant 3000 22.7.3 Creating an NFAS-Related Trunk Configuration The procedures for creating and deleting an NFAS group must be performed in the correct order, as described below.  To create an NFAS Group: If there’s a backup (‘secondary’) trunk for this group, it must be configured first.

  • Page 381: Isdn Overlap Dialing

    Relevant parameters (described in ''PSTN Parameters'' on page 865):  ISDNRxOverlap_x = 1 (can be configured per trunk)  TimeBetweenDigits  MaxDigits  MuteDTMFInOverlap  DigitMapping For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 361. Version 6.8 Mediant 3000...

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

    Mediant 3000 22.8.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 With overlap dialing disabled, the device expects to receive the digits all at once (enbloc) or with very little delay between digits and then sends the complete number in a single message.

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

    STM-1 signal level. The device supports the asynchronous VC-12 mapping (mapping of E1s into VC12s and multiplexing of 63 VC12 into an STM-1 frame). Relevant parameters: • PSTNTransmissionType - set to 'Optical SONET or SDH' (1). Version 6.8 Mediant 3000...
  • Page 384 Mediant 3000 • SDHFbrGrp_SDHSONETMode - set to 'STM1' (1) • SDHFbrGrp_Mapping_Type - set to 'Asynchronous TU12 and E1' (1)  OC-3 interface: provides short range SONET OC-3 interface compliant to GR-253- CORE and ANSI T1.105. The interface operates at 155.52 Mbps over a single-mode fiber span.

  • Page 385: Trunk Numbering (Klm Numbering)

    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). 22.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.
  • Page 386 Mediant 3000 Trunk ETSI GR-253 Timeslots TUG-3 TUG-2 TU-12 TUG-3 TUG-2 TU-12 TUG-3 TUG-2 TU-12 User's Manual Document #: LTRT-89738...

  • Page 387: T1 Trunk Enumeration (Sonet Mappings)

    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. Table 22-5: OC-3 Numbering Conversion Table Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 Version 6.8 Mediant 3000...
  • Page 388 Mediant 3000 Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 User's Manual Document #: LTRT-89738...
  • Page 389 User's Manual 22. Digital PSTN Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 Version 6.8 Mediant 3000...
  • Page 390 Mediant 3000 Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 User's Manual Document #: LTRT-89738...

  • Page 391: Trunk Group

    ''Configuring Trunk Group Settings'' on page 393).  To register the Trunk Groups, click the Register button, located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Version 6.8 Mediant 3000...
  • Page 392 Mediant 3000 Table 23-1: Trunk Group Table Parameter Descriptions Parameter Description From Trunk Defines the starting physical Trunk number in the Trunk Group. [TrunkGroup_FirstTrunkId] The number of listed Trunks depends on the device's hardware configuration. To Trunk Defines the ending physical Trunk number in the Trunk Group.

  • Page 393: Configuring Trunk Group Settings

    Open the Trunk Group Settings page (Configuration tab > VoIP menu > GW and IP to IP > Trunk Group > Trunk Group Settings). Configure a Trunk Group according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...
  • Page 394 Mediant 3000 Table 23-2: Trunk Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. [TrunkGroupSettings_TrunkGro upId] Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the [TrunkGroupSettings_ChannelS channels of the Trunk Group.
  • Page 395 From: <sip:101@GatewayName>;tag=1c862422082 To: <sip:101@GatewayName> Call-ID: 9907977062512000232825@10.33.37.78 CSeq: 3 REGISTER Contact: <sip:101@10.33.37.78>;expires=3600 Expires: 3600 User-Agent: Sip-Gateway/v.6.80A.011.002 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Group table (see ''Configuring IP Groups'' on page 283). Notes: Version 6.8 Mediant 3000...
  • Page 396 Mediant 3000 Parameter Description  If this parameter is not configured, the registration is performed according to the global registration parameter, ChannelSelectMode.  To enable Trunk Group registration, set the global parameter, IsRegisterNeeded to 1. This is unnecessary for 'Per Account' registration mode.
  • Page 397  "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Version 6.8 Mediant 3000...
  • Page 398 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 399: Manipulation

    Rule: Defines the matching characteristics of the incoming call (e.g., prefix of destination number).  Action: Defines the action that is done if the incoming call matches the characteristics of the rule (e.g., removes a user-defined number of digits from the left of the number). Version 6.8 Mediant 3000...
  • Page 400 Mediant 3000 The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it applies the manipulation configured for that rule. In other words, a rule at the top of the table takes precedence over a rule defined lower down in the table.
  • Page 401 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 Prefix to Add Version 6.8 Mediant 3000...
  • Page 402 Mediant 3000 Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Suffix to Add Number of Digits to Leave Allowed Restricted Presentation Table 24-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
  • Page 403 Defines the number of digits to remove from the right of the telephone Right number prefix. For example, if you enter 3 and the phone number is EMS: Number Of Stripped 5551234, the new phone number is 5551. Version 6.8 Mediant 3000...
  • Page 404 Mediant 3000 Parameter Description Digits [RemoveFromRight] Web: Prefix to Add Defines the number or string that you want added to the front of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 9 and the phone number [Prefix2Add] is 1234, the new number is 91234.
  • Page 405 If this field is set to Restricted and the 'Asserted Identity Mode' (AssertedIdMode) parameter is set to Add P-Asserted-Identity, the From header in the INVITE message includes the following: From: 'anonymous' <sip: anonymous@anonymous.invalid> and 'privacy: id' header. Version 6.8 Mediant 3000...

  • Page 406: Manipulating Number Prefix

    Mediant 3000 24.3 Manipulating Number Prefix The device supports a notation for adding a prefix where part of the prefix is first extracted from a user-defined location in the original destination or source number. This notation is entered in the 'Prefix to Add' field in the Number Manipulation tables (see ''Configuring Source/Destination Number Manipulation'' on page 399): x[n,l]y...

  • Page 407: Sip Calling Name Manipulations

    Web interface. You can also configure these rules using the the following management tools:  Calling Name Manipulation Table for Tel-to-IP Calls table: table ini file parameter, CallingNameMapTel2Ip  Calling Name Manipulation Table for IP-to-Tel Calls table: table ini file parameter, CallingNameMapIp2Tel Version 6.8 Mediant 3000...
  • Page 408 Mediant 3000  To configure calling name manipulation rules: Open the required calling name manipulations page (Configuration tab > VoIP menu > GW and IP to IP > Manipulations > Calling Name IP->Tel or Calling Name Tel- >IP). Click Add; the following dialog box appears:...
  • Page 409 Operation (Action) Web: Stripped Digits From Defines the number of characters to remove from the left of the calling Left name. For example, if you enter 3 and the calling name is EMS: Number Of Stripped Version 6.8 Mediant 3000...

  • Page 410: Configuring Redirect Number Ip To Tel

    Mediant 3000 Parameter Description Digits "company:john", the new calling name is "pany:john". [_RemoveFromLeft] Web: Stripped Digits From Defines the number of characters to remove from the right of the calling Right name. For example, if you enter 3 and the calling name is EMS: Number Of Stripped "company:name", the new name is "company:n".
  • Page 411 The valid value is a string of up to 20 characters. Matching Characteristics - Rule Web/EMS: Destination Prefix Defines the destination (called) telephone number prefix. [_DestinationPrefix] The default value is the asterisk (*) symbol (i.e., any number). For manipulating the diverting and redirected numbers for call Version 6.8 Mediant 3000...
  • Page 412 Mediant 3000 Parameter Description diversion, you can use the strings "DN" and "RN" to denote the destination prefix of these numbers. For more information, see Manipulating Redirected and Diverted Numbers for Call Diversion on page 414. Web/EMS: Redirect Prefix Defines the redirect telephone number prefix.
  • Page 413 [-1] Not Configured = (Default) Value received from PSTN/IP is [_NumberPlan] used  [0] Unknown  [1] E.164 Public  [9] Private For more information on available NPI/TON values, see Numbering Plans and Type of Number on page 424. Version 6.8 Mediant 3000...

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

    Mediant 3000 24.6 Manipulating Redirected and Diverted Numbers for Call Diversion You can configure manipulation rules to manipulate the Diverted-to and Diverting numbers received in the incoming Call Redirection Facility message for call diversion, which is interworked to outgoing SIP 302 responses. This feature is applicable to the Euro ISDN and QSIG variants, and to IP-to-Tel calls.

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

    Click Submit, and then save ("burn") your settings to flash memory. Note: You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'. In such a configuration, a Tel-to-IP call uses the first matching rule in the table. Version 6.8 Mediant 3000...
  • Page 416 Mediant 3000 Table 24-6: Phone Context Table Parameter Description Parameter Description Index Defines an index number for the new table record. [PhoneContext_Index] Add Phone Context As Prefix Determines whether the received SIP 'phone-context' parameter is [AddPhoneContextAsPrefix] added as a prefix to the outgoing ISDN Setup message with called and calling numbers.

  • Page 417: Configuring Release Cause Mapping

    Click Add; the following dialog box appears: Figure 24-6: Release Cause Mapping - Add Record Configure a mapping rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...
  • Page 418 Mediant 3000 Table 24-7: Release Cause Mapping Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [CauseMapSip2Isdn_Index] [CauseMapIsdn2Sip_Index] Sip Response Defines the SIP response code (e.g., 406). [CauseMapSip2Isdn_SipResponse] [CauseMapIsdn2Sip_SipResponse] Q.850 Causes Defines the ISDN Q.850 cause code (e.g., 6).

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

    User busy Not acceptable here Normal, unspecified Bad Event Normal, unspecified Request Pending Normal, unspecified Server internal error Temporary failure Not implemented Network out of order Bad gateway Network out of order Service unavailable Temporary failure Version 6.8 Mediant 3000...
  • Page 420 Mediant 3000 ISDN Release SIP Response Description Description Reason Server timeout Recovery on timer expiry 505* Version not supported Interworking Busy everywhere User busy Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order * Messages and responses were created because the ‘ISUP to SIP Mapping’...

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

    Server internal error User Congestion Server internal error No circuit available Service unavailable Network out of order Service unavailable Permanent Frame Mode Connection Service unavailable Out-of-Service Permanent Frame Mode Connection Service unavailable Operational Temporary failure Service unavailable Version 6.8 Mediant 3000...
  • Page 422 Mediant 3000 ISDN Release Description Description Reason Response Switching equipment congestion Service unavailable Access information discarded 502* Bad gateway Requested channel not available 503* Service unavailable Precedence Call Blocked Not Acceptable Here Resource unavailable Service unavailable QoS unavailable 503* Service unavailable...
  • Page 423 Implemented - Passed On Protocol error Server internal error Uknown Error Bad Request Interworking unspecified Server internal error * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft doesn’t specify their cause code mapping. Version 6.8 Mediant 3000...

  • Page 424: Reason Header

    Mediant 3000 24.8.3 Reason Header The device supports the SIP Reason header according to RFC 3326. The Reason header conveys information describing the disconnection cause of a call:  Sending Reason header: If a call is disconnected from the Tel side (ISDN), the Reason header is set to the received Q.850 cause in the appropriate message...
  • Page 425 1/1 - International number in ISDN/Telephony numbering plan  1/2 - National number in ISDN/Telephony numbering plan  1/4 - Subscriber (local) number in ISDN/Telephony numbering plan  9/4 - Subscriber (local) number in Private numbering plan Version 6.8 Mediant 3000...
  • Page 426 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 427: 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.  Matching Characteristics: One or more characteristics can be defined for the rule: Version 6.8 Mediant 3000...
  • Page 428 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 429 ''Alternative Routing for Tel-to-IP Calls'' on page 443.  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine with calculating the cost of using a service (Tel-to-IP call) and relaying that information Version 6.8 Mediant 3000...
  • Page 430 Mediant 3000 to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule. Note: You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table.
  • Page 431  This parameter is not applicable if outbound proxy routing is used.  For number manipulation, see ''Configuring Source/Destination Number Manipulation'' on page 399. Route Name Defines an arbitrary name to easily identify the routing rule. Version 6.8 Mediant 3000...
  • Page 432 Mediant 3000 Parameter Description [PREFIX_RouteName] The valid value is a string of up to 20 characters. By default, no value is defined. Matching Call Characteristics Web: Src. IP Group ID Defines the IP Group from where the incoming IP call is received.
  • Page 433 0.0.0.0.  For routing calls between phones connected to the device (i.e., local routing), enter the device's IP address.  When the device's IP address is unknown (e.g., when DHCP is used), enter IP address 127.0.0.1. Version 6.8 Mediant 3000...
  • Page 434 Mediant 3000 Parameter Description  When using domain names, enter the DNS server's IP address or alternatively, configure these names in the Internal DNS table (see ''Configuring the Internal DNS Table'' on page 143). Web: Port Defines the destination port to where you want to route the call.
  • Page 435 2, 3, and 4 with Forking Group "1": The device sends the call according to index entry 1 only and ignores the other index entries even if the destination is unavailable and alternative routing is enabled. This is because the subsequent Version 6.8 Mediant 3000...
  • Page 436 Mediant 3000 Parameter Description index entries are defined with a Forking Group number that is lower than that of index entry 1.  Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with Forking Group "1": The device first sends the call according to...

  • Page 437: Configuring Inbound Ip Routing Table

    SNMP trap, GWAPP_TRAP_BUSYOUT_LINK notifying of the out-of-service state for the specific trunk number. When the physical trunk is physically reconnected, this trap is sent notifying of the back-to-service state. Version 6.8 Mediant 3000...
  • Page 438 Mediant 3000 Notes: • You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table. • If your deployment includes calls of many different called (source) and/or calling (destination) numbers that need to be routed to the same destination, you can employ user-defined prefix tags to represent these numbers.
  • Page 439 The prefix can include up to 49 digits. Note: If the P-Asserted-Identity header is present in the incoming INVITE message, the value of this parameter is compared to the P-Asserted-Identity URI host name (and not the From header). Version 6.8 Mediant 3000...
  • Page 440 Mediant 3000 Parameter Description Web: Source IP Address Defines the source IP address of the incoming IP call that can [PstnPrefix_SourceAddress] be used for routing decisions. The IP address must be configured in dotted-decimal notation (e.g., 10.8.8.5); not as an FQDN.
  • Page 441 This IP Group can later be used for outbound IP routing and as the 'Serving IP Group' in the Account table for obtaining authentication user name/password for this call. For configuring registration accounts in the Account table, see ''Configuring Account Table'' on page 303. Version 6.8 Mediant 3000...

  • Page 442: Ip Destinations Connectivity Feature

    Mediant 3000 25.4 IP Destinations Connectivity Feature The device can be configured to check the integrity of the connectivity to IP destinations of Tel-to-IP routing rules in the Outbound IP Routing table. The IP Connectivity feature can be used for the Alternative Routing feature, whereby the device attempts to re-route calls from unavailable Tel-to-IP routing destinations to available ones (see ''Alternative Routing Based on IP Connectivity'' on page 443).

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

    IP connectivity status, see ''IP Destinations Connectivity Feature'' on page 442. The table below shows an example of alternative routing where the device uses an available alternative routing rule in the Outbound IP Routing table to re-route the initial Tel- to-IP call. Version 6.8 Mediant 3000...

  • Page 444: Alternative Routing Based On Sip Responses

    Mediant 3000 Table 25-4: Alternative Routing based on IP Connectivity Example Destination IP Connectivity IP Destination Rule Used? Phone Prefix Status Main Route 10.33.45.68 "No Connectivity" Alternative Route #1 10.33.45.70 "QoS Low" Alternative Route #2 10.33.45.72 "ok" The steps for configuring alternative Tel-to-IP routing based on IP connectivity are summarized below.
  • Page 445 Homing mode: The device always attempts to operate with the primary proxy. In other words, it switches back to the primary proxy whenever it's available again. If none of the proxy servers respond, the device goes over the list again. Version 6.8 Mediant 3000...
  • Page 446 Mediant 3000 Note: The device assumes that all the proxy servers belonging to the Proxy Set are synchronized with regards to registered users. Thus, when the device locates an available proxy using the Hot Swap feature, it does not re-register the users; new registration (refresh) is done as normal.

  • Page 447: Alternative Routing Upon Sip 3Xx With Multiple Contacts

    (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 437. Version 6.8 Mediant 3000...

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

    Mediant 3000 25.6 Alternative Routing for IP-to-Tel Calls The device supports alternative IP-to-Tel call routing, as described in this section. 25.6.1 Alternative Routing to Trunk upon Q.931 Call Release Cause Code You can configure up to 10 ISDN Q.931 release cause codes, which if received from the Tel side, the device routes the IP-to-Tel call to an alternative Trunk Group, if configured.

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

    All trunks are busy or unavailable The following procedure describes how to configure Forward on Busy Trunks in the Web interface. also configure this using table file parameter, ForwardOnBusyTrunkDest or CLI command, configure voip/gw routing fwd-on-bsy-trk-dst. Version 6.8 Mediant 3000...
  • Page 450 Mediant 3000  To configure a Forward on Busy Trunk Destination rule: Open the Forward on Busy Trunk Destination page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Forward on Busy Trunk). Click Add; the following dialog box appears:...

  • Page 451: Alternative Routing Upon Isdn Disconnect

    If no alternative route has been configured and the Disconnect message is received with PI, the device forwards the subsequent early media to the IP side. The device disconnects the IP call only upon receipt of the subsequent Release message. Version 6.8 Mediant 3000...
  • Page 452 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 453: Configuring Dtmf And Dialing

    Open the DTMF & Dialing page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > DTMF & Dialing). Figure 26-1: DTMF & Dialing Page Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 580. Version 6.8 Mediant 3000...

  • Page 454: Dialing Plan Features

    Mediant 3000 26.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 26.1.1 Digit Mapping Digit map pattern rules are used for Tel-to-IP ISDN overlap dialing (by setting the ISDNRxOverlap parameter to 1) to reduce the dialing period. For more information on digit maps for ISDN overlapping, see ISDN Overlap Dialing on page 381.

  • Page 455: External Dial Plan File

    Dial Plan. 26.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see ''Dial Plan File'' on page 593. Version 6.8 Mediant 3000...
  • Page 456 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 457: Configuring Supplementary Services

    Click Submit, 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 580. Version 6.8 Mediant 3000...

  • Page 458: Call Hold And Retrieve

    Mediant 3000 27.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 459: Consultation Transfer For Qsig Path Replacement

    • IP-to-Tel call: destination number of the original call. • If the UseReferredByForCallingNumber parameter is set to 1, the source number is taken from the SIP Referred-By header if included in the received SIP REFER message. Version 6.8 Mediant 3000...

  • Page 460: Call Forward

    Mediant 3000 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.
  • Page 461 (i.e., does not send MWI Interrogation messages). • Send MWI Interrogation message, but don't use its result. Instead, wait for MWI Activate requests from the PBX. • Send MWI Interrogation message, use its result, and use the MWI Activate requests. Version 6.8 Mediant 3000...

  • Page 462: Emergency E911 Phone Number Services

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

  • Page 463: About E9-1-1 Services

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

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

    Mediant 3000 27.5.2.2 Microsoft Lync Server 2010 and E9-1-1 Microsoft Lync Server 2010 enables Enterprise voice users to access its unified communications platform from virtually anywhere and through many different devices. This, together with a deployed MLTS, poses a challenge for E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller.
  • Page 465 Once done, it can automatically locate clients within a network. You can add addresses individually to the LIS or in a batch using a comma- separated value (CSV) file containing the column formats listed in the table below. Version 6.8 Mediant 3000...
  • Page 466 Mediant 3000 Table 27-1: Columns in the LIS Database Network Columns Element <BSSID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNum Wireless berSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<City>, access point <State>,<PostalCode>,<Country> <Subnet>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNum Subnet berSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<City>, <State>,<PostalCode>,<Country> <ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location>,<CompanyName> Port ,<HouseNumber>,<HouseNumberSuffix>,…<PreDirectional>,<StreetName>,<StreetS uffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> <ChassisID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseN Switch umberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<Cit y>,<State>,<PostalCode>,<Country> 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>...

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

    ELIN when dialing 9-1-1. 27.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 468 Mediant 3000 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. Figure 27-5: AudioCodes ELIN Gateway for E9-1-1 in Lync Server 2010 Environment 27.5.2.3.1 Detecting and Handling E9-1-1 Calls The ELIN Gateway identifies E9-1-1 calls and translates their incoming E9-1-1 calling numbers into ELIN numbers, sent toward the PSAP.
  • Page 469 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 470 Mediant 3000 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 de>twoway</ms:ConferenceMode><LocationPolicyTagID...
  • Page 471 If all the ELINs in the list are in use by active calls, the ELIN Gateway selects the ELIN number as follows: The ELIN with the lowest count (i.e., lowest number of active calls currently using this ELIN). Version 6.8 Mediant 3000...

  • Page 472: Configuring Audiocodes Elin Gateway

    27.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. 27.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 473 Manchester police department, which is +44161999. The international code, +44 for England is used for IP routing considerations, but can be omitted depending on your specific network environment. The above example scenario is configured as follows: Version 6.8 Mediant 3000...
  • Page 474 Mediant 3000 Enable location-based emergency routing, by loading an ini file to the device with the following parameter setting: E911Gateway = 2 In the Destination Phone Number Manipulation Table for IP-to-Tel Calls (Configuration tab > VoIP menu > GW and IP to IP > Manipulations > Dest Number IP->Tel), add the following two rules for manipulating the destination number...

  • Page 475: Multilevel Precedence And Preemption

    Table 27-4: MLPP Call Priority Levels (Precedence) and DSCP Configuration Parameters MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header 0 (lowest) routine MLPPRoutineRTPDSCP priority MLPPPriorityRTPDSCP immediate MLPPImmediateRTPDSCP flash MLPPFlashRTPDSCP flash-override MLPPFlashOverRTPDSCP 9 (highest) flash-override-override MLPPFlashOverOverRTPDSCP Version 6.8 Mediant 3000...
  • Page 476 Mediant 3000 The device automatically interworks the network identity digits (NI) in the ISDN Q.931 Precedence Information Element (IE) to the network domain subfield of the INVITE's Resource-Priority header, and vice versa. The SIP Resource-Priority header contains two fields, namespace and priority. The namespace is subdivided into two subfields, network- domain and precedence-domain.

  • Page 477: Mlpp Preemption Events In Sip Reason Header

    The device receives SIP requests with preemption reason cause=5 in the following cases: • The softswitch performs a network preemption of an active call - the following sequence of events occurs: The softswitch sends the device a SIP BYE request with this Reason cause code. Version 6.8 Mediant 3000...

  • Page 478: Precedence Ring Tone

    The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call), using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
  • Page 479 The device supports various methods for AOC:  Tel-to-IP direction: The device converts the AOC messages received in the EURO ISDN Facility IE messages into SIP INFO and BYE messages using AudioCodes proprietary SIP AOC header.  IP-to-Tel direction provides optional methods: •...

  • Page 480: Configuring Charge Codes

    Mediant 3000 27.9 Configuring Charge Codes The Charge Codes table lets you configure metering tones Advice of Charge (AOC) services for Euro ISDN trunks (see Advice of Charge Services for Euro ISDN on page 478). You can configure up to 25 different Charge Codes, where each table row represents a Charge Code.
  • Page 481 User's Manual 27. Configuring Supplementary Services Parameter Description Pulse Interval Defines the time interval between pulses (in tenths of a second). [ChargeCode_PulseInterval<1-4>] Pulses On Answer Defines the number of pulses sent on answer. [ChargeCode_PulsesOnAnswer<1- 4>] Version 6.8 Mediant 3000...

  • Page 482: Configuring Voice Mail

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

  • Page 483: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 485: Sbc Overview

    Modifies SIP To, From, and Request-URI host names (must be configured using the Message Manipulations table). • Generates a new SIP Call-ID header value (different between legs). • Changes the SIP Contact header to the device's own address. Version 6.8 Mediant 3000...

  • Page 486: Sip Network Definitions

    Mediant 3000 • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following: •...
  • Page 487 ''SBC Manipulations'' on page 548. 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 311. Version 6.8 Mediant 3000...
  • Page 488 Mediant 3000 The flowchart below illustrates the SBC process: Figure 28-1: Routing Process User's Manual Document #: LTRT-89738...

  • Page 489: User Registration

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

  • Page 490: Sbc Users Registration Database

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

  • Page 491: Registration Restriction Control

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

  • Page 492: Sbc Media Handling

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

  • Page 493: Media Anchoring Without Transcoding (Transparent)

    Realm, then this is the associated Media Realm; otherwise, the leg's SRD Media Realm is the associated one. The figure below illustrates an example of SDP handling for a call between a LAN IP Phone 10.2.2.6 and a remote IP Phone 212.179.1.13 on the WAN. Figure 28-3: SDP Offer/Answer Example Version 6.8 Mediant 3000...

  • Page 494: Media Anchoring With Transcoding

    Mediant 3000 28.4.2 Media Anchoring with Transcoding The device performs transcoding when there are no common coders between the two user agents (i.e., the SDP answer from one user agent doesn't include any coder included in the offer previously sent by the other user agent). For transcoding, the device can be...

  • Page 495: No Media Anchoring

    The No Media Anchoring feature is typically implemented in the following scenarios:  The device is located within the LAN.  Calls between two SIP UAs in the same LAN and signaling is sent to a SIP proxy server (or hosted IP PBX) located in the WAN. Version 6.8 Mediant 3000...
  • Page 496 Mediant 3000  The device does not need to perform NAT traversal (for media) and all the users are in the same domain. Figure 28-5: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring feature include the following: ...

  • Page 497: Transcoding Modes

    IP Profile table. Note: To implement transcoding, you must configure the number of required DSP channels for transcoding (for example, MediaChannels = 120). Each transcoding session uses two DSP resources. Version 6.8 Mediant 3000...

  • Page 498: Restricting Coders

    Mediant 3000 28.4.5 Restricting Coders The SBC Allowed Coders (coders restriction) feature determines the coders that can be used for a specific SBC leg. This provides greater control over bandwidth by enforcing the use of specific coders (allowed coders groups) while preventing the use of other coders.
  • Page 499 In the IP Profile table, select this Coders Group in the 'Extension Coders Group ID' parameter. In the IP Profile table, enable this feature by setting the 'Allowed Coders Mode' parameter to Restriction or Restriction and Preference. Version 6.8 Mediant 3000...

  • Page 500: Prioritizing Coder List In Sdp Offer

    Mediant 3000 28.4.7 Prioritizing Coder List in SDP Offer In addition to restricting the use of coders with Allowed coders, you can prioritize the coders listed in the SDP offer. This feature is referred to as Coder Preference. This is done on both SBC legs: ...

  • Page 501: Multiple Rtp Media Streams Per Call Session

    The chosen DTMF method determines (for each leg) which DTMF method is used for sending DTMF’s. If the device interworks between different DTMF methods and one of the methods is In-band\RFC 2833, detection and generation of DTMF methods requires DSP allocation. Version 6.8 Mediant 3000...

  • Page 502: Fax Negotiation And Transcoding

    Mediant 3000 28.5 Fax Negotiation and Transcoding The device can allow fax transmissions to traverse transparently without transcoding or it can handle the fax as follows:  Allow interoperability between different fax machines, supporting fax transcoding if required.  Restrict usage of specific fax coders to save bandwidth, enhance performance, or comply with supported coders.

  • Page 503: Sip Authentication Server Functionality

    The device's Authentication server functionality is configured per IP Group, using the 'Authentication Mode' parameter in the IP Group table (see ''Configuring IP Groups'' on page 283). Note: This feature is applicable only to Mediant 3000 in Simplex mode. Version 6.8 Mediant 3000...

  • Page 504: User Authentication Based On Radius

    Mediant 3000 28.7.2 User Authentication based on RADIUS The device can authenticate SIP clients (users) using a remote RADIUS server. The device supports the RADIUS extension for digest authentication of SIP clients, according to draft- sterman-aaa-sip-01. Based on this standard, the device generates the nonce (in contrast to RFC 5090, where it is done by the RADIUS server).
  • Page 505 The classification, manipulation, and routing processes are done exactly like any other INVITE handling. The special prefix can be used for specific routing rules for 3xx resultant INVITEs. The prefix is removed before the resultant INVITE is sent to the destination. Figure 28-6: SIP 3xx Response Handling Version 6.8 Mediant 3000...

  • Page 506: Local Handling Of Sip 3Xx

    Mediant 3000 The process of this feature is described using an example: The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User@IPPBX:5060;transport=tcp;param=a>;q=0.5). The device replaces the Contact header value with the special prefix and database key value as user part, and with the device's URL as host part (e.g., Contact: <sip:Prefix_Key_User@SBC:5070;transport=udp>;q=0.5).

  • Page 507: Interworking Sip Refer Messages

    The handling of REFER can be configured for all calls, using the global parameter SBCReferBehavior. For configuring different REFER handling options for different UAs (i.e., IP Groups), use the IP Profile table parameter, 'SBC Remote Refer Behavior'. Version 6.8 Mediant 3000...

  • Page 508: Interworking Sip Prack Messages

    Mediant 3000  Local handling of REFER: This option is used for UAs that do not support REFER. Upon receipt of a REFER request, instead of forwarding it to the IP Group, the device handles it locally. It generates a new INVITE to the alternative destination according to the rules in the IP-to-IP Routing table (where the 'Call Trigger' field is set to REFER).
  • Page 509 IP Profile parameters, 'SBC Remote Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Version 6.8 Mediant 3000...
  • Page 510 Mediant 3000 Figure 28-7: SBC Early Media RTP 18x without SDP Figure 28-8: Early Media RTP - SIP 18x with SDP User's Manual Document #: LTRT-89738...

  • Page 511: Interworking Sip Re-Invite Messages

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

  • Page 512: Interworking Call Hold

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

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

    You can configure whether REGISTER messages from secondary lines are terminated on the device or forwarded transparently (as is), using the SBCSharedLineRegMode parameter. • The LED indicator of a shared line may display the wrong current state. Version 6.8 Mediant 3000...

  • Page 514: Call Survivability For Call Centers

    Mediant 3000  To configure the Shared Line feature: In the IP Group table (see ''Configuring IP Groups'' on page 283), add a Server-type IP Group for the BroadWorks server. In the IP Group table, add a User-type IP Group for the IP phone users and set the...
  • Page 515 In the Classification table (see ''Configuring Classification Rules'' on page 529), add rules to classify incoming calls that are received from the entities listed in Step 1, to IP Groups. Version 6.8 Mediant 3000...
  • Page 516 Mediant 3000 In the SBC IP-to-IP Routing table (see ''Configuring SBC IP-to-IP Routing Rules'' on page 537), add the following IP-to-IP routing rules: • For normal operation: ♦ Routing from TDM Gateway to Application server. ♦ Routing from Application server to call center agents.

  • Page 517: Survivability Mode Display On Aastra Ip Phones

    The device can also fork INVITE messages received for a Request-URI of a specific contact (user), belonging to the destination IP Group User-type, registered in the database to all other users located under the same AOR as the specific contact. This is configured using the SBCSendInviteToAllContacts parameter. Version 6.8 Mediant 3000...

  • Page 518: Sip Forking Initiated By Sip Proxy Server

    Mediant 3000 28.10.2 SIP Forking Initiated by SIP Proxy Server The device can handle SIP forking responses received from a proxy server in response to an INVITE forwarded by the device from a UA. In other words, received responses with a different SIP To header 'tag' parameter for the request forwarded by the device.

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

    28.12 Active SBC Call Continuity during HA Blade Switchover The device maintains active SBC call sessions during a blade switchover when in High Availability mode. Upon active blade failure, the standby blade takes over and current SBC calls are maintained and not disconnected. Version 6.8 Mediant 3000...
  • Page 520 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 521: Sbc Configuration

    B. User B can then press a pre-configured key sequence to answer the call. The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP Version 6.8 Mediant 3000...
  • Page 522 Mediant 3000 clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself; not that of the involved SIP clients. This is due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements.

  • Page 523: Configuring Admission Control

    In this setup, the SRD offers a shared pool for unreserved call capacity of 10 [i.e., 40 – (10 + 20)]. If IP Group ID 1 needs to handle 15 calls, it is guaranteed 10 calls and the remaining 5 is provided from the SRD's shared pool. If the SDR's shared pool is currently Version 6.8 Mediant 3000...
  • Page 524 Mediant 3000 empty and resources for new calls are required, the quota is taken from the device's total capacity, if available. For example, if IP Group ID 1 needs to handle 21 calls, it's guaranteed 10, the SRD's shared pool provides another 10, and the last call is provided from the device's total call capacity support (e.g., of 200).
  • Page 525 Defines the maximum number of concurrent SIP dialogs per user belonging to the specified IP Group or SRD. You can also [SBCAdmissionControl_LimitPerU ser] use the following special values:  [0] 0 = Block all these dialogs.  [-1] -1 = (Default) Unlimited. Version 6.8 Mediant 3000...
  • Page 526 Mediant 3000 Parameter Description Rate Defines the rate (in seconds) at which tokens are added to the [SBCAdmissionControl_Rate] token bucket per second (i.e., token rate). The default is 0 (i.e., unlimited rate). Notes:  You must first configure the Maximum Burst parameter (see below) before configuring the Rate parameter.

  • Page 527: Configuring Allowed Audio Coder Groups

    Open the Allowed Audio Coders Group page (Configuration tab > VoIP menu > SBC > Allowed Audio Coders Group). Figure 29-4: Allowed Audio Coders Group Page Configure an Allowed Audio Coders Group according to the parameters described in Version 6.8 Mediant 3000...

  • Page 528: Configuring Allowed Video Coder Groups

    Mediant 3000 the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 29-2: Allowed Audio Coders Group Table Parameter Descriptions Parameter Description Allowed Coders Group ID Defines an index number for the new table record.

  • Page 529: Routing Sbc

    Proxy Set. The Proxy Set is assigned to the IP Group in the IP Group table. If classification based on Proxy Set fails (or classification based on Proxy Set is disabled), the device proceeds to classification based on the Classification table. Version 6.8 Mediant 3000...
  • Page 530 Mediant 3000 Note: • For security, it is recommended to classify SIP dialogs based on Proxy Set only if the IP address of the Server-type IP Group is unknown. In other words, if the Proxy Set associated with the IP Group is configured with an FQDN. In such cases, the device classifies incoming SIP dialogs to the IP Group based on the DNS-resolved IP address.
  • Page 531 If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination. The following procedure describes how to configure Classification rules in the Web interface. You can also configure Classification rules using the table ini file parameter, Classification. Version 6.8 Mediant 3000...
  • Page 532 Mediant 3000  To configure a Classification rule: Open the Classification Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Click Add; the following dialog box appears: Figure 29-6: Classification Table Page Configure the Classification rule according to the parameters described in the table below.
  • Page 533 URI. This is done in the IP Group table, using the 'Source URI Input' parameter. For more information on how the device obtains this URI, see ''SIP Dialog Initiation Process'' on page 486. The default is the asterisk (*) symbol, which represents any source host prefix. Version 6.8 Mediant 3000...

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

    Mediant 3000 Parameter Description Note: For REGISTER requests, the source URL is obtained from the To header. Destination Username Prefix Defines the prefix of the destination Request-URI user part of the incoming SIP dialog. [Classification_DestUsernamePrefix] The default is the asterisk (*) symbol, which represents any destination username.

  • Page 535: Configuring Message Condition Rules

    For a description on SIP message manipulation syntax, refer to the SIP Message Manipulations Quick Reference Guide. The following procedure describes how to configure Message Condition rules in the Web interface. You can also configure Message Condition rules using the table ini file parameter, ConditionTable. Version 6.8 Mediant 3000...
  • Page 536 Mediant 3000  To configure a Message Condition rule: Open the Message Condition Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Message Condition Table). Click Add; the following dialog box appears: Figure 29-7: Condition Table Page - Add Record Dialog Box Configure a Message Condition rule according to the parameters described in the table below.

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

    Request-URI user part (by default, "acgateway- <prefix destination>", for example, acgateway-200). The device removes this prefix before sending it to the Tel side. To configure this prefix string, use the GWDirectRoutePrefix ini file parameter. Version 6.8 Mediant 3000...
  • Page 538 Mediant 3000 The IP-to-IP Routing table also provides the following features:  Alternative routing or load balancing: In addition to the alternative routing/load balancing provided by the Proxy Set associated with the destination IP Group, the table allows the configuration of alternative routes whereby if a route fails, the next adjacent (below) rule in the table that is configured as 'Alt Route Ignore/Consider Inputs' are used.
  • Page 539 For more information on prefix tags, see ''Dial Plan Prefix Tags for SBC IP-to-IP Routing'' on page 597. Version 6.8 Mediant 3000...
  • Page 540 Mediant 3000 Note: Call forking is not applicable to LDAP-based IP-to-IP routing rules. The following procedure describes how to configure IP-to-IP routing rules in the Web interface. You can also configure IP-to-IP routing rules using the table ini file parameter, IP2IPRouting.
  • Page 541 ''Interworking SIP REFER Messages'' on page 507, respectively. This parameter functions together with the 'Call Trigger' field (see below). The default is -1 (i.e., not configured). Call Trigger Defines the reason (i.e, trigger) for re-routing the SIP [IP2IPRouting_Trigger] request: Version 6.8 Mediant 3000...
  • Page 542 Mediant 3000 Parameter Description  [0] Any = (Default) This routing rule is used for all scenarios (re-routes and non-re-routes).  [1] 3xx = Re-routes the request if it was triggered as a result of a SIP 3xx response. ...
  • Page 543 SRD associated with the Source IP Group (configured in the IP Group table, see ''Configuring IP Groups'' on page 283). If this table does not define an IP Group but only an SRD, the first IP Version 6.8 Mediant 3000...
  • Page 544 Mediant 3000 Parameter Description Group associated with this SRD (in the IP Group table) is used.  If the destination IP Group ID is of SERVER type, the request is routed according to the IP Group addresses.  If the destination IP Group ID is of USER type, the request is routed according to the IP Group specific database (i.e., only to registered users of the selected...
  • Page 545 Cost Group Assigns a Cost Group to the routing rule for determining the cost of the call. To configure Cost Groups, see ''Configuring [IP2IPRouting_CostGroup] Cost Groups'' on page 248. By default, no Cost Group is defined. Version 6.8 Mediant 3000...

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

    Mediant 3000 29.5.4 Configuring SIP Response Codes for Alternative Routing Reasons The SBC Alternative Routing Reasons table lets you configure up to 20 SIP response codes for call release (termination) reasons. If a call (outgoing SIP dialog-initiating methods, e.g., INVITE, OPTIONS, and SUBSCRIBE messages) is released as a result of a...
  • Page 547 Figure 29-10: Alternative Routing Reasons Table - Add Record Configure a SIP response code for alternative routing according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 3000...

  • Page 548: Sbc Manipulations

    Mediant 3000 Table 29-7: SBC Alternative Routing Reasons Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [SBCAlternativeRoutingReasons_Index] Release Cause Defines a SIP response code for triggering the [SBCAlternativeRoutingReasons_ReleaseCause] device's alternative routing mechanism. 29.6 SBC Manipulations This section describes the configuration of the manipulation rules for the SBC application.
  • Page 549 The SIP message manipulations in the example above (contributing to typical topology hiding) are as follows:  Inbound source SIP URI user name from "7000" to "97000": From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe  Source IP Group name (i.e., SIP URI host name) from "10.2.2.6" to "IP_PBX": Version 6.8 Mediant 3000...

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

    Mediant 3000 From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe  Inbound destination SIP URI user name from "1000" to 9721000": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0...
  • Page 551 Note: Additional manipulation can only be done on a different SIP URI, source or destination, to the rule configured in the row above as configured by the 'Manipulated URI' parameter (see below). Version 6.8 Mediant 3000...
  • Page 552 Mediant 3000 Parameter Description Manipulation Purpose Defines the purpose of the manipulation: [IPInboundManipulation_Manipulati  [0] Normal = (Default) Inbound manipulations affect the onPurpose] routing input and source and/or destination number.  [1] Routing input only = Inbound manipulations affect the routing input only, retaining the original source and destination number.

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

    Operation (Action) - if the incoming call matches the characteristics of the rule, the device manipulates the source or destination SIP URI user part or calling name of the SIP dialog (e.g., removes user-defined number of characters from the left of the SIP URI user part). Version 6.8 Mediant 3000...
  • Page 554 Mediant 3000 Note: SIP URI host name (source and destination) manipulations can also be configured in the IP Group table. These manipulations are simply host name substitutions with the names configured for the source and destination IP Groups, respectively. The following procedure describes how to configure IP-to-IP Outbound Manipulation rules in the Web interface.
  • Page 555 ''Configuring Message Condition Rules'' on page 535. Request Type Defines the SIP request type to which the manipulation rule [IPOutboundManipulation_RequestT is applied. ype]  [0] All = (Default) all SIP messages.  [1] INVITE = All SIP messages except REGISTER and Version 6.8 Mediant 3000...
  • Page 556 Mediant 3000 Parameter Description SUBSCRIBE.  [2] REGISTER = Only SIP REGISTER messages.  [3] SUBSCRIBE = Only SIP SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER.
  • Page 557 Restriction is done only after user number manipulation (if any).  The device identifies an incoming user as restricted if one of the following exists:  From header user is "anonymous".  P-Asserted-Identity and Privacy headers contain Version 6.8 Mediant 3000...
  • Page 558 Mediant 3000 Parameter Description the value "id". User's Manual Document #: LTRT-89738...

  • Page 559: High-Availability System

    Part VII High-Availability System...

  • Page 561: Ha Overview

    User's Manual 30. 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 562: 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). Its PSTN and Gigabit Ethernet (GbE) interfaces are connected to the active VoP blade in Slot 1 of the front panel.

  • Page 563: 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.8...

  • Page 564: Blade Failure Detection

    Mediant 3000 30.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 565: Network Interfaces And Mediant 3000 High Availability

    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 566 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) Table 31-3: Example of Multiple Interfaces for Mediant 3000 HA in Interface Table Primary / Prefix Secondar Inde...

  • Page 567: 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 568 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 32-1: Separate Physical Network Interfaces User's Manual...

  • Page 569: Configuring Physical Network Separation

    Click Submit, and then reset the device (see ''Basic Maintenance'' on page 577). Change the cabling so that the OAMP and Control networks are cabled to the PEM’s relevant Ethernet ports (refer to the Installation Manual). Version 6.8 Mediant 3000...

  • Page 570: Disabling 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 571 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 572 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 573: Viewing Ha Status On Home Page

    When the device is configured for HA mode, the Home page displays the chassis with two VoIP blades (TP-6310 or TP-8410) and two SA/M3K Alarms, Status and Synchronization ("SAT") blades, as shown in the figure below: Figure 33-1: Home Page for Mediant 3000 HA Device Table 33-1: Indications of HA on Home Page Parameter...
  • Page 574 Mediant 3000  "Operational: SA Card Error": Malfunction in SAT blade  "Operational: RTM Card Error": Malfunction in RTM blade The Active blade is indicated by the following:  The darker-shaded blade in the graphical display of the device's chassis.

  • Page 575: Maintenance

    Part VIII Maintenance...

  • Page 577: Basic Maintenance

    After you reset the device, the Web GUI is displayed in Basic view (see ''Displaying Navigation Tree in Basic and Full View'' on page 56).  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 577). Version 6.8 Mediant 3000...

  • Page 578: Remotely Resetting Device Using Sip Notify

    Mediant 3000 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). • No: Resets the device without saving the current configuration to flash (discards all unsaved modifications).

  • Page 579: 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. 34.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 580: Saving Configuration

    Mediant 3000 Click OK to confirm device lock; if you set 'Graceful Option' to Yes, a lock icon is delayed and a window appears displaying the number of remaining calls and time. If you set 'Graceful Option' to No, the lock process begins immediately. The 'Gateway Operational State' field displays "LOCKED".

  • Page 581: 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.8 Mediant 3000...
  • Page 582 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 583: Resetting Channels

    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.8 Mediant 3000...
  • Page 584 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 585: Locking And Unlocking Trunk Groups

    • "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Version 6.8 Mediant 3000...
  • Page 586 Mediant 3000 Note: • If the device is reset, a locked Trunk Group remains locked. If the device is reset while graceful lock is in progress, the Trunk Group is forced to lock immediately after the device finishes its reset.

  • Page 587: Software Upgrade

    The Auxiliary files listed in the ini file are then automatically loaded through 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. Version 6.8 Mediant 3000...
  • Page 588 Mediant 3000 Notes: • You can schedule automatic loading of updated auxiliary files using HTTP/HTTPS, FTP, or NFS. For more information on automatic updates, see Automatic Update Mechanism. • Auxiliary file upload through TFTP is not supported by HA mode.

  • Page 589: 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 590 Mediant 3000  Cadence: A repeating sequence of on and off sounds. Up to four different sets of on/off periods can be specified.  Burst: A single sound followed by silence. Only the 'First Signal On time' and 'First Signal Off time' should be specified. All other on and off periods must be set to zero.
  • Page 591 High Freq Level [-dBm]=32 (use 32 only if a single tone is required) First Signal On Time [10msec]=300; the dial tone is detected after 3 sec First Signal Off Time [10msec]=0 Second Signal On Time [10msec]=0 Second Signal Off Time [10msec]=0 Version 6.8 Mediant 3000...

  • Page 592: Prerecorded Tones File

     Channels: mono Once created, the PRT file must then be loaded to the device, using AudioCodes' AcBootP utility or the Web interface (see ''Loading Auxiliary Files'' on page 587). 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 593: Dial Plan File

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Load the converted file to the device, as described in ''Loading Auxiliary Files'' on page 587.
  • Page 594 • To use the Dial Plan file, you must also use a special CAS .dat file that supports this feature. For more information, contact your AudioCodes sales representative. • For E1 CAS MFC-R2 variants, which don't support terminating digit for the called party number, usually I-15, the Dial Plan file and the DigitMapping parameter are ignored.

  • Page 595: Dial Plan Prefix Tags For Routing

    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 587.
  • Page 596 Mediant 3000 local calls and international calls would need to be routed to different SIP trunks. Thus, instead of configuring many routing rules for each call destination type, you can simply configure two routing rules, one with a unique prefix tag representing the different local area codes and the other with a prefix tag representing international calls.
  • Page 597 The local calls and international calls would need to be routed to different SIP trunks. Thus, instead of configuring many routing rules for each call destination type, you can simply Version 6.8 Mediant 3000...
  • Page 598 Mediant 3000 configure two routing rules, one with a unique prefix tag representing the different local area codes and the other with a prefix tag representing international calls. Note: When using prefix tags, you need to configure manipulation rules to remove the tags before the device sends the calls to their destinations.

  • Page 599: Obtaining Ip Destination From Dial Plan File

    Tel-to-IP/IP-to-IP Calls (Gateway application): In the Outbound IP Routing table, do the following: In the 'Destination Address' field, enter the required Dial Plan index using the following syntax: DialPlan<index> Where "DialPlan0" denotes [PLAN1] in the Dial Plan file, "DialPlan1" denotes [PLAN2], and so on. Version 6.8 Mediant 3000...

  • Page 600: Modifying Isdn-To-Ip Calling Party Number

    Mediant 3000 Note: The "DialPlan" string is case-sensitive. 38.1.4.5 Modifying ISDN-to-IP Calling Party Number The device can use the Dial Plan file to change the Calling Party Number value (source number) of the incoming ISDN call when sending to IP. For this feature, the Dial Plan file supports the following syntax: <ISDN Calling Party Number>,0,<new calling number>...

  • Page 601: User Information File

    IP PBX extension number 402 (calling / SIP From) that is destined to IP PBX extension number 403 (called / SIP To), the device changes both these numbers into their "global" numbers 638002 and 638003, respectively. Version 6.8 Mediant 3000...

  • Page 602: Mediant

    Mediant 3000  Registering Users: The device can register each PBX user configured in the User Info table. For each user, the device sends a SIP REGISTER to an external IP-based Registrar server, using the "global" number in the From/To headers. If authentication is necessary for registration, the device sends the user's username and password, configured in the User Info table, in the SIP MD5 Authorization header.
  • Page 603 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 Version 6.8 Mediant 3000...

  • Page 604: User Information File For Sbc User Database

    Mediant 3000  UserName is the username (string of up to 40 characters) for registering the user when authentication is necessary  Password is the password (string of up to 20 characters) for registering the user when authentication is necessary Each line in the file represents a mapping rule of a single PBX extension user.
  • Page 605 Defines the IP Group ID to which the user belongs and is used as [SBCUserInfoTable_IPGroupID] the Request-URI source host part for the AOR in the database. Status (Read-only field) Displays the status of the user - "Registered" or [SBCUserInfoTable_Status] "Not Registered". Version 6.8 Mediant 3000...

  • Page 606: Amd Sensitivity File

    The XML-to-binary format conversion can be done using AudioCodes DConvert utility. For more information on using this utility, refer to the DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.

  • Page 607: 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 608: 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 609: Installing Software License Key Using Web Interface

    In the 'Current Key' field, select the entire text string and copy it to any standard text file (e.g., Notepad). Save the text file with any file name and file extension (e.g., key.txt) to a folder on your computer. Version 6.8 Mediant 3000...
  • Page 610 Open the Software License Key file and check that the "S/N" line appears. If it does not appear, contact AudioCodes. Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]".

  • Page 611: Installing Software License Key Using Acbootp

    38. Software Upgrade 38.2.2.2 Installing Software License Key using AcBootP The following procedure describes how to install a Software License Key using AudioCodes AcBootP utility. Notes: • When loading the Software License Key file, a cmp file must also be loaded during this BootP process.
  • Page 612 Mediant 3000 The previously active blade (now in redundant mode) installs and burns the file to its flash memory with a reset. Therefore, both blades now run the new software version. An HA switchover occurs from the active blade (i.e., the initial redundant blade) to the redundant blade (i.e., the initial active device) to return the blades to their...
  • Page 613 If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
  • Page 614 Mediant 3000 Figure 38-7: Software Upgrade Wizard - Load CMP File Note: At this stage, you can quit the Software Upgrade Wizard without having to reset the device, by clicking Cancel . However, if you continue with the wizard and start loading the cmp file, the upgrade process must be completed with a device reset.
  • Page 615 (and do not select an ini file). • Restore configuration to factory defaults: Clear the 'Use existing configuration' check box (and do not select an ini file). Figure 38-9: Software Upgrade Wizard – Load INI File Version 6.8 Mediant 3000...
  • Page 616 Mediant 3000 When you have completed loading all the desired files, click Next until the last wizard page appears (the FINISH button is highlighted in the left pane): Figure 38-10: Software Upgrade Wizard – Files Loaded Click Reset to burn the files to the device's flash memory; the "Burn and reset in progress"...

  • Page 617: Backing Up And Loading Configuration File

    From the Navigation tree, click the Maintenance tab, click the Software Update menu, and then click Configuration File. • On the toolbar, click Device Actions, and then from the drop-down menu, choose Load Configuration File or Save Configuration File. Figure 38-12: Configuration File Page Version 6.8 Mediant 3000...
  • Page 618 Mediant 3000 To save the ini file to a folder on your computer: Click the Save INI File button; the File Download dialog box appears. Click the Save button, navigate to the folder where you want to save the file, and then click Save.

  • Page 619: Automatic Update Mechanism

    TFTP server. Thus, the device can obtain its network parameters from BootP or DHCP servers, and its software and configuration files from a different TFTP server (preconfigured in the ini configuration file). Version 6.8 Mediant 3000...
  • Page 620 Mediant 3000 If BootP/DHCP servers are not found or when the device is reset using the Web interface or SNMP, it retains its network parameters and attempts to load the cmp file and/or configuration files from a preconfigured TFTP server. If a preconfigured TFTP server does not exist, the device operates using the existing software and configuration files on its flash memory.

  • Page 621: Local Configuration Server With Bootp/Tftp

    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 622 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; User's Manual...

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

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

  • Page 624: Http-Based Provisioning

    Mediant 3000 This method loads the configuration file to the device as a one-time action. The download is only repeated if the device is manually restored to factory defaults (by pressing the hardware reset button while the Ethernet cable is not connected) and DHCP is enabled (see note below).

  • Page 625: Loading Files Securely By Disabling Tftp

    NFS v2/v3 is also supported. 39.2.8 Provisioning using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections. 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 626: Http/S-Based Provisioning Using The Automatic Update Feature

    Mediant 3000 39.3 HTTP/S-Based Provisioning using the Automatic Update Feature The Automatic Update feature can be used for automatic provisioning of the device through HTTP/S. Automatic provisioning is useful for large-scale deployment of devices. In some cases, the devices are shipped to the end customer directly from the manufacturer. In other cases, they may pass through a staging warehouse.

  • Page 627: Triggers For Automatic Update

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

  • Page 628: Access Authentication With Http Server

    Mediant 3000 To enable this feature through the Web interface: 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.
  • Page 629 For example, if you set AupdHttpUserAgent = <NAME>;<VER>, the device sends the following User-Agent header: Mozilla/4.0 (compatible; AudioCodes; Mediant; 6.80.200.001) If the provisioning server has relevant files available for the device, the following occurs, depending on file type and configuration: •...

  • Page 630: File Download Sequence

    Mediant 3000 • One-time File Download: This is applicable to software (.cmp) and Auxiliary (e.g., call progress tone / CPT) files. The device downloads these files only once, regardless of how many times the device may repeat the Automatic Update process.

  • Page 631: Cyclic Redundancy Check On Downloaded Configuration Files

    For enabling CRC, use the ini file parameter AUPDCheckIfIniChanged or CLI command, configure system > automatic-update > crc-check regular. By default, CRC is disabled. For more information on the parameter, see Automatic Update Parameters. Version 6.8 Mediant 3000...

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

    Mediant 3000 39.3.8 MAC Address Automatically Inserted in Configuration File Name You can configure the file name of the configuration file (ini) in the URL to automatically include the MAC address of the device. As described in 'File Location for Automatic Update' on page 626, the file name is included in the configured URL of the provisioning server where the file is located.
  • Page 633 (automatic-update)# voice-configuration 'http://www.company.com/config.ini' Enable Cyclical Redundancy Check (CRC) on downloaded ini file: ♦ ini File: AUPDCheckIfIniChanged = 1 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# crc-check regular Power down and then power up the device. Version 6.8 Mediant 3000...

  • Page 634: Automatic Update From Nfs, Ftp And Http Servers

    Mediant 3000 39.3.9.2 Automatic Update from NFS, FTP and HTTP Servers This example describes how to configure the Automatic Update feature where files are stored and downloaded from different file server types. The example scenario includes the following:  NFS server (Version 2) at 10.13.2.10 for storing the CPT file.

  • Page 635: Automatic Update For Mass Deployment

    Device queries the provisioning server daily at 24:00 (midnight) for software, configuration and auxiliary files.  HTTP-based provisioning server at www.company.com for storing the files.  DNS server at 80.179.52.100 for resolving the domain name of the provisioning server. Version 6.8 Mediant 3000...
  • Page 636 Mediant 3000  To set up automatic provisioning for mass provisioning (example): Create an ini file named "master_configuration.ini" with the following settings: Common configuration for all devices: # Check for updates daily at 24:00 AutoUpdatePredefinedTime = '24:00' # CPT file update: CptFileURL = 'https://www.company.com/call_progress.dat'...

  • Page 637: 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 638: Restoring Defaults Using An Ini File

    Mediant 3000 40.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 617).

  • Page 639: Status, Performance Monitoring And Reporting

    Part IX Status, Performance Monitoring and Reporting...

  • Page 641: System Status

    Navigation menu tree: Status & Diagnostics tab > System Status menu > Ethernet Port Info • On the Home page, click any Ethernet port on the graphical display of the device (see ''Viewing the Home Page'' on page 67) Version 6.8 Mediant 3000...
  • Page 642 Mediant 3000 When Physical Network Separation is enabled on Mediant 3000 with TP-8410 (using the parameter EnableNetworkPhysicalSeparation - see Networking Parameters on page 742), the Ethernet Port Information page displays the ports for the Control, OAMP, and Media network interfaces, as shown below:...

  • Page 643: 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 41-2: Timing Module Information Page Version 6.8 Mediant 3000...

  • Page 644: Viewing Hardware Components Status

    Mediant 3000 41.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 645: Carrier-Grade Alarms

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

  • Page 647: Performance Monitoring

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

  • Page 648: Viewing Trunk Utilization

    Mediant 3000 43.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 649 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.8 Mediant 3000...

  • Page 650: Viewing Quality Of Experience

    Mediant 3000 43.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 651 From the 'Type' drop-down list, select the SIP message type: • Invite - INVITE • Subscribe - SUBSCRIBE • Other - all SIP messages To refresh the charts, click Refresh. To reset the counters, click Reset Counters. Version 6.8 Mediant 3000...

  • Page 652: Viewing Average Call Duration

    Mediant 3000 43.4 Viewing Average Call Duration The Average Call Duration page displays information about a specific SRD or IP Group. This page includes two graphs:  Upper graph: displays the number of calls (INVITEs).  Lower graph: displays the average call duration.

  • Page 653: Voip Status

    Label Description Description Gray Disabled Disabled Disabled Green Active - OK No Alarms No Alarms (Working) Yellow RAI Alarm No Alarms RAI Alarm (Protection) LOS / LOF Alarm LOS/LOF/MS- LOS/LOF/AIS Alarm AIS/MS-RDI Alarm Blue AIS Alarm Version 6.8 Mediant 3000...
  • Page 654 Mediant 3000 Icon Color Trunk 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 655: Viewing Nfas Groups And D-Channel Status

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

  • Page 656: Viewing Active Ip Interfaces

    Mediant 3000  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 44-3: NFAS Group & D-Channel Status Page 44.3...

  • Page 657: Viewing Static Routes Status

    Open the Basic Statistics page (Status & Diagnostics tab > VoIP Status menu > Performance Statistics). Figure 44-5: Basic Statistics Page The duration that the displayed statistics were collected is displayed in seconds above the table. To reset the performance statistics to zero, click the Reset Statistics button. Version 6.8 Mediant 3000...

  • Page 658: Viewing Call Counters

    Mediant 3000 44.6 Viewing Call Counters The IP to Tel Calls Count page and Tel to IP Calls Count page provide you with statistical information on incoming (IP-to-Tel) and outgoing (Tel-to-IP) calls. The statistical information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call Call Detail Record or CDR message is sent).
  • Page 659 15 minute period. Attempted Fax Calls Indicates the number of attempted fax calls. Counter Indicates the number of successful fax calls. Successful Fax Calls Counter Version 6.8 Mediant 3000...

  • Page 660: Viewing Registered Users

    Mediant 3000 44.7 Viewing Registered Users You can view SAS and SBC users listed in the device's Users Registration database. The list shows each Address of Record (AOR) and its corresponding contact. The contact's registration status is also shown: ...

  • Page 661: Viewing Proxy Set Status

    "Load Balancing: Proxy load balancing mode, as configured by the ProxySet_ProxyRedundancyMode parameter. For more information, see Configuring Proxy Sets. Keep Alive Displays whether the Proxy Keep-Alive feature is enabled ("Enabled") or disabled ("Disabled"), as configured by the ProxySet_EnableProxyKeepAlive parameter (see Configuring Proxy Sets). Version 6.8 Mediant 3000...
  • Page 662 Mediant 3000 Parameter Description Address Displays the IP address of the proxy server. This can be the IP address as configured in dotted-decimal notation for the Proxy Set, or the resolved IP address of a DNS query if an FQDN is configured for the Proxy Set.

  • Page 663: Viewing Ip Connectivity

    OK = Remote side responds to periodic connectivity queries.  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). Version 6.8 Mediant 3000...
  • Page 664 Mediant 3000 Column Name Description  Disable = The connectivity option is disabled, i.e., parameter 'Alt Routing Tel to IP Mode' (AltRoutingTel2IPMode ini) is set to 'None' or 'QoS'. Quality Status Determines the QoS (according to packet loss and delay) of the IP address.

  • Page 665: Reporting Information To External Party

    Start timestamp in the RTCP XR indicates the start of the media segment; the End timestamp indicates the time of the last sent periodic RTCP XR (typically, up to 5 seconds before reported segment ends). Version 6.8 Mediant 3000...
  • Page 666 Mediant 3000 Table 45-1: RTCP XR Published VoIP Metrics Group Metric Name General Start Timestamp Stop Timestamp Call-ID Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration...
  • Page 667 CallID=20328634741612201520943@172.17.116.201 LocalID: <sip:1000@172.17.116.201> RemoteID: <sip:2000@172.17.116.202;user=phone> OrigID: <sip:1000@172.17.116.201> LocalAddr: IP=172.17.116.201 Port=6000 SSRC=0x54c62a13 RemoteAddr: IP=172.17.116.202 Port=6000 SSRC=0x243220dd LocalGroup: RemoteGroup: LocalMAC: 00:90:8f:57:d9:71 LocalMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z SessionDesc: PT=8 PD=PCMA SR=8000 FD=20 PLC=3 SSUP=Off JitterBuffer: JBA=3 JBR=0 JBN=7 JBM=10 JBX=300 Version 6.8 Mediant 3000...
  • Page 668 Mediant 3000 PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=6325 GMIN=16 Delay: RTD=0 ESD=11 Signal: SL=-34 NL=-67 RERL=17 QualityEst: RLQ=93 MOSLQ=4.1 MOSCQ=4.10 RemoteMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z JitterBuffer: JBA=3 JBR=0 JBN=0 JBM=0 JBX=300 PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=0 GMIN=16...

  • Page 669: Generating Call Detail Records

    RTP packet, where the device "latches" on to the RTP media and obtains the IP address of the SIP UA. From this point on, the device publishes CDRs with this correct IP address instead of the NAT IP address. Version 6.8 Mediant 3000...

  • Page 670: Configuring Cdr Reporting

    Mediant 3000 45.2.1 Configuring CDR Reporting The following procedure describes how to configure CDR reporting.  To configure CDR reporting: Enable the Syslog feature for sending log messages generated by the device to a collecting log message server. For more information, see ''Enabling Syslog'' on page 697.
  • Page 671 "RMT" - remote TrmReason Termination reason String of up to 40 characters TrmReasonCategory Termination reason category: String of up to 17 characters Calls with duration 0 (i.e., not connected):  NO_ANSWER:  "GWAPP_NORMAL_CALL_CLEA R"  "GWAPP_NO_USER_RESPONDI Version 6.8 Mediant 3000...
  • Page 672 Mediant 3000 CDR Field Name Description Format NG"  "GWAPP_NO_ANSWER_FROM_ USER_ALERTED"  BUSY:  " GWAPP_USER_BUSY"  NO_RESOURCES:  "GWAPP_RESOUUCE_UNAVAIL ABLE_UNSPECIFIED"  "RELEASE_BECAUSE_NO_CON FERENCE_RESOURCES_LEFT"  "RESOURCE_BECAUSE_NO_TR ANSCODING_RESOURCES_LEF T"  "RELEASE_BECAUSE_GW_LOC KED"  NO_MATCH:  "RELEASE_BECAUSE_UNMATC HED_CAPABILITIES"  FORWARDED:  "RELEASE_BECAUSE_FORWAR D"...

  • Page 673: Cdr Fields For Sbc Media

    CDRs, where each media CDR has a unique call ID corresponding to the signaling CDR. Table 45-3: CDR Fields for SBC Media CDR Field Name Description MediaReportType Report type (media start, update, or end) Version 6.8 Mediant 3000...
  • Page 674 Mediant 3000 CDR Field Name Description SIPCallId Unique call ID Channel CID MediaType Media type (audio, video, or text) Coder Coder name Coder packet interval PacketInterval LocalRtpIp Local RTP IP address LocalRtpPort Local RTP port Remote RTP IP address RemoteRtpIp...

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

    DestIp Destination IP address Source phone number type Note: This field is applicable only to the Gateway application. Source phone number plan Note: This field is applicable only to the Gateway application. SrcPhoneNum Source phone number Version 6.8 Mediant 3000...
  • Page 676 Mediant 3000 Field Name Description SrcNumBeforeMap Source number before manipulation Destination phone number type Note: This field is applicable only to the Gateway application. Destination phone number plan Note: This field is applicable only to the Gateway application. DstPhoneNum Destination phone number...
  • Page 677 SRD ID name SIPInterfaceId SIP interface ID ProxySetId Proxy Set ID IpProfileId IP Profile ID name MediaRealmId Media Realm name SigTransportType SIP signaling transport type (UDP, TCP, or TLS) TxRTPIPDiffServ Media IP DiffServ TxSigIPDiffServ Signaling IP DiffServ Version 6.8 Mediant 3000...
  • Page 678 Mediant 3000 Field Name Description LocalRFactor Local R-factor Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable.

  • Page 679: Release Reasons In Cdr

    "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED" Version 6.8 Mediant 3000...
  • Page 680 Mediant 3000  "GWAPP_NON_SELECTED_USER_CLEARING"  "GWAPP_INVALID_NUMBER_FORMAT"  "GWAPP_FACILITY_REJECT"  "GWAPP_RESPONSE_TO_STATUS_ENQUIRY"  "GWAPP_NORMAL_UNSPECIFIED"  "GWAPP_CIRCUIT_CONGESTION"  "GWAPP_USER_CONGESTION"  "GWAPP_NO_CIRCUIT_AVAILABLE"  "GWAPP_NETWORK_OUT_OF_ORDER"  "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" •...

  • Page 681: Configuring Radius Accounting

    Example Name Attribute Format (VSA) ID Request Attributes user-name (Standard) Account number or String 5421385747 Start calling party number up to 15 or blank digits Stop long nas-ip- (Standard) IP address of the Numeric 192.168.14.43 Start Version 6.8 Mediant 3000...
  • Page 682 Mediant 3000 Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID address requesting device Stop service-type (Standard) Type of service Numeric 1: login Start requested Stop h323- SIP call identifier Up to h323-incoming- Start incoming- conf-id=38393530 conf-id...
  • Page 683 (SBC) called- (Standard) Destination phone String 8004567145 Start station-id number (Gateway call) or Destination URI (SBC call) calling- (Standard) Calling Party String 5135672127 Start station-id Number (ANI) (Gateway call) or Stop Source URI (SBC call) Version 6.8 Mediant 3000...
  • Page 684 Mediant 3000 Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID acct-status- (Standard) Account Request Numeric 1 Start type Type - start (1) or stop (2) Stop Note: ‘start’ isn’t supported on the Calling Card application. acct-delay- (Standard) No.
  • Page 685 (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 (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 Version 6.8 Mediant 3000...

  • Page 686: Event Notification Using X-Detect Header

    Mediant 3000 45.4 Event Notification using X-Detect Header The device can notify a remote party of the occurrence (or detection) of certain events in the media stream. The device detects events and notifies their occurrence, using the SIP X-Detect message header and only when establishing a SIP dialog.
  • Page 687 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" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 Version 6.8 Mediant 3000...
  • Page 688 Mediant 3000 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Request=CPT,FAX SIP/2.0 200 OK Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone>;tag=1c19282 Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:101@10.33.2.53> X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone>...

  • Page 689: Querying Device Channel Resources Using Sip Options

    In the example above, "telchs" specifies the number of available channels and the number of occupied channels (100 channels are occupied and 140 channels are available). Note: This feature is applicable only to the Gateway / IP-to-IP application. Version 6.8 Mediant 3000...
  • Page 690 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 691: Diagnostics

    Part X Diagnostics...

  • Page 693: Syslog And Debug Recordings

    Syslog message, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- Version 6.8 Mediant 3000...

  • Page 694: Event Representation In Syslog Messages

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

  • Page 696: Unique Device Identification In Syslog Messages

    Syslog messages includes the following unique string for the device:  The main operations and events of the Mediant 3000 High Availability (HA) 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 697: Syslog Fields For Answering 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: Table 46-4: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Critical RecoverableMsg Major...

  • Page 698: Enabling Syslog

    Mediant 3000 46.2 Enabling Syslog The following procedure describes how to enable and configure Syslog. Notes: • For configuring CDR reporting, see ''Configuring CDR Reporting'' on page 670. • For viewing Syslog messages in the Web interface, see ''Viewing Syslog Messages'' on page 704.

  • Page 699: Configuring Web Operations To Report To Syslog

    Debug recording is collected only on the device's OAMP interface.  To configure and activate debug recording: Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings). Figure 46-3: Logging Settings Page Version 6.8 Mediant 3000...

  • Page 700: Filtering Syslog Messages And Debug Recordings

    Mediant 3000 Configure the debug capturing server using the 'Debug Recording Destination IP' and 'Debug Recording Destination Port' parameters. From the 'Debug Recording Status' drop-down list, select Start to start the debug recording or Stop to end the recording. Click Submit.
  • Page 701 For IP trace expressions, see ''Filtering IP Network Traces'' on page Syslog Enables Syslog messages for the defined logging filter: [LoggingFilters_Syslog]  [0] Disable (default)  [1] Enable Note: This parameter is not applicable when 'Filter Type' is set to IP Trace. Version 6.8 Mediant 3000...
  • Page 702 Mediant 3000 Parameter Description Capture Type Enables debug recordings for the defined logging filter and defines [LoggingFilters_CaptureType] what to record:  [0] None (default)  [1] Signaling = Information related to signaling such as SIP signaling messages, Syslog, CDR, and the device's internal processing messages.

  • Page 703: Filtering Ip Network Traces

    == 1.1.1.1 and ip.dst == 3.3.3.3 ip.src == 2.2.2.2 and ip.dst == 3.3.3.3 Note: If the 'Value' field is not defined, the device records all IP traffic types. Version 6.8 Mediant 3000...

  • Page 704: Viewing Syslog Messages

    Syslog server. • You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting. ...

  • Page 705: Collecting Debug Recording Messages

    User's Manual 46. Syslog and Debug Recordings 46.7 Collecting Debug Recording Messages To collect debug recording packets, use the open source program Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...

  • Page 706: Mediant

    Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 707: 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.8 Mediant 3000...
  • Page 708 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

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

    The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. The files can then be sent to AudioCodes support team for troubleshooting. ...
  • Page 710 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89738...

  • Page 711: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. However, this number can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call.
  • Page 712 Mediant 3000 Configure a test call according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 49-1: Test Call Table Parameter Descriptions Parameter Description General Tab Endpoint URI Defines the endpoint's URI. This can be defined as a user or [Test_Call_EndpointURI] user@host.
  • Page 713 A value of -1 means that the parameter value is automatically calculated according to the values of the 'Calls per Second' and 'Maximum Channels for Session' parameters. Note: This parameter is applicable only if 'Call Party' is set to Caller. Version 6.8 Mediant 3000...
  • Page 714 Mediant 3000 Parameter Description Calls per Second Defines the number of calls per second. [Test_Call_CallsPerSecond] Note: This parameter is applicable only if 'Call Party' is set to Caller. Test Mode Defines the test session mode. [Test_Call_TestMode]  [0] Once = (Default) The test runs until the lowest value between the following is reached: ...

  • Page 715: Starting And Stopping Test Calls

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

  • Page 717: Configuring Dtmf Tones For Test Calls

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

  • Page 718: Configuring Basic Test Call

    Mediant 3000 49.5 Configuring Basic Test Call The Basic Test Call feature tests incoming Gateway calls from a remote SIP endpoint to a simulated test endpoint on the device. The only required configuration is to assign a prefix number (test call ID) to the simulated endpoint. All incoming calls with this called (destination) prefix number is identified as a test call and sent to the simulated endpoint.

  • Page 719: Configuring Sbc Test Call With External Proxy

    The device receives the call from the proxy server. As the 'Test Call ID' parameter is set to "101", the device identifies the incoming call as a test call and sends it directly to the simulated test endpoint "101". Version 6.8 Mediant 3000...

  • Page 720: Test Call Configuration Examples

    Mediant 3000  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Parameters'' on page 754): Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings).
  • Page 721 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 722 Mediant 3000  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and pas,sword) process of a simulated test endpoint on the device with an external proxy/registrar server. This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another.

  • Page 723: Appendix

    Part XI Appendix...

  • Page 725: Dialing Plan Notation For Routing And Manipulation

    [100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc.  03(5xx): for any number that starts with 03 and ends with 5xx. Version 6.8 Mediant 3000...
  • Page 726 Mediant 3000 Notation Description  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.  Only numerical ranges are supported (not alphabetical letters).

  • Page 727: Configuration Parameters Reference

    When this duration expires, the password of the Web user must be [WebUserPassChangeInt changed. erval] The valid value is 0 to 100000, where 0 means that the password is always valid. The default is 1140. Note: This parameter is applicable only when using the Web Users Version 6.8 Mediant 3000...
  • Page 728 Mediant 3000 Parameter Description 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 729 = 1, and reset the device with a flash burn (set acSysActionSetResetControl to 1 and acSysActionSetReset to 2) Change the username and password in the acSysWEBAccessEntry table. Use the following format: Username acSysWEBAccessUserName: old/pass/new Password acSysWEBAccessUserCode: username/old/new Version 6.8 Mediant 3000...

  • Page 730: Telnet Parameters

    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 731: Ini File Parameters

    [SendKeepAliveTrap] Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 732 Mediant 3000 Parameter Description parameter. Note: For this parameter to take effect, a device reset is required. EMS: Keep Alive Trap Port Defines the port of the SNMP network management station to which [KeepAliveTrapPort] the device sends keep-alive traps. The valid range is 0 to 65534. The default is 1161.
  • Page 733 The valid SNMP trap port range is 100 to 4000. The default port is 162. Web: Trap Enable Enables the sending of traps to the corresponding SNMP manager. [SNMPManagerTrapSendin  [0] Disable = Sending is disabled. gEnable_x]  [1] Enable = (Default) Sending is enabled. Version 6.8 Mediant 3000...
  • Page 734 Mediant 3000 Parameter Description Web: Trap User Defines the SNMPv3 USM user or SNMPv2 user to associate with the [SNMPManagerTrapUser_x trap destination. This determines the trap format, authentication level, and encryption level. By default, it is associated with the SNMPv2 user (SNMP trap community string).
  • Page 735 User's Manual 51. Configuration Parameters Reference Version 6.8 Mediant 3000...

  • Page 736: Serial Parameters

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

  • Page 737: 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 738: Automatic Update Parameters

    The valid value is a string of up to 511 characters. By default, this parameter is not defined. In other words, the User-Agent header is set to "Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>)”, where the tags are replaced with actual values. Notes: ...
  • Page 739 A higher value does not necessarily mean better performance.  The block size should be small enough to avoid IP fragmentation in the client network (i.e., below MTU).  This feature is applicable only to TFTP servers that support this option. Version 6.8 Mediant 3000...
  • Page 740 Mediant 3000 Parameter Description [ResetNow] Invokes an immediate device reset. This option can be used to activate offline (i.e., not on-the-fly) parameters that are loaded using the parameter IniFileUrl.  [0] = (Default) The immediate restart mechanism is disabled. ...
  • Page 741 Defines the name of the User Information file and the path to the server (IP address or FQDN) on which it is located. For example: http://server_name/file, https://server_name/file Note: The maximum length of the URL address is 99 characters. Version 6.8 Mediant 3000...

  • Page 742: Networking Parameters

    Mediant 3000 51.2 Networking Parameters This subsection describes the device's networking parameters. 51.2.1 Ethernet Parameters The Ethernet parameters are described in the table below. Table 51-9: Ethernet Parameters Parameter Description EMS: Physical Defines the Ethernet connection mode type. Configuration ...
  • Page 743 Notes:  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 744: Routing Parameters

    Mediant 3000 Parameter Description [EnableNTPasOAM] Defines the application type for Network Time Protocol (NTP) services.  [1] = OAMP (default)  [0] = Control Note: For this parameter to take effect, a device reset is required. [VLANSendNonTaggedOnNative] Determines whether to send non-tagged packets on the native VLAN.

  • Page 745: Quality Of Service Parameters

    IP Profile table, see ''Configuring IP Profiles'' on page 329. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 3000...

  • Page 746: Nat And Stun Parameters

    Mediant 3000 Parameter Description Web: Control Premium QoS Global parameter that defines the DiffServ value for Premium EMS: Premium Service Class Control CoS content (Call Control applications). You can also Control Diff Serv configure this functionality per specific calls, using IP Profiles [PremiumServiceClassControlDi (IpProfile_SigIPDiffServ).
  • Page 747 1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.
  • Page 748 Mediant 3000 Parameter Description  [0] = Disable IP address translation.  [1] = (Default) Enable IP address translation. When enabled, the device compares the source IP address of the first incoming packet to the remote IP address stated in the opening of the channel.

  • Page 749: Nfs Parameters

    Dns2Ip 0 = DnsName, 1.1.1.1, 2.2.2.2, 3.3.3.3, ; For a detailed description of this table, see ''Configuring the Internal DNS Table'' on page 143. Internal SRV Table Web: Internal SRV Table This table parameter defines the internal SRV table for resolving host Version 6.8 Mediant 3000...

  • Page 750: Dhcp Parameters

    Mediant 3000 Parameter Description EMS: DNS Information names into DNS A-Records. Three different A-Records can be assigned [SRV2IP] to a host name. Each A-Record contains the host name, priority, weight, and port. The format of this parameter is as follows:...

  • Page 751: Ntp And Daylight Saving Time Parameters

     [0] Disable (default) [DayLightSavingTimeEnable]  [1] Enable Web: Start Time / Day of Defines the date and time when daylight saving begins. This value Month Start can be configured using any of the following formats: Version 6.8 Mediant 3000...
  • Page 752 Mediant 3000 Parameter Description  EMS: Start Day of year - mm:dd:hh:mm, where: [DayLightSavingTimeStart]  mm denotes month  dd denotes date of the month  hh denotes hour  mm denotes minutes For example, "05:01:08:00" denotes daylight saving starting from May 1 at 8 A.M.

  • Page 753: Debugging And Diagnostics Parameters

    The valid range is 0 to 45. The default is 7 seconds. Note: This feature helps overcome connection problems caused by some LAN routers or IP configuration parameters' modifications by a DHCP server. Version 6.8 Mediant 3000...

  • Page 754: Sip Test Call Parameters

    Mediant 3000 Parameter Description [EnableAutoRAITransmitBER] Enables the device to send a remote alarm indication (RAI) when the bit error rate (BER) is greater than 0.001.  [0] Disable (default)  [1] Enable 51.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below.

  • Page 755: Syslog, Cdr And Debug Parameters

    [0] None = (Default) CDRs are not used.  [1] End Call = CDR is sent to the Syslog server at the end of each call.  [2] Start & End Call = CDR report is sent to Syslog at the start and Version 6.8 Mediant 3000...
  • Page 756 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the 'acsyslog' filter instead of the regular 'syslog' filter.
  • Page 757 EMS: SyslogFacility messages, according to RFC 3164. This allows you to identify Syslog [SyslogFacility] messages generated by the device. This is useful, for example, if you collect the device’s and other equipments’ Syslog messages, at one Version 6.8 Mediant 3000...
  • Page 758 Mediant 3000 Parameter Description single server. The device’s Syslog messages can easily be identified and distinguished from other Syslog messages by its Facility level. Therefore, in addition to filtering Syslog messages according to IP address, the messages can be filtered according to Facility level.
  • Page 759 The format of the ini file table parameter is: [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_FilterType, LoggingFilters_Value, LoggingFilters_Syslog, LoggingFilters_CaptureType; [ \LoggingFilters ] For a detailed description of this table, see ''Filtering Syslog Messages and Debug Recordings'' on page 700. Version 6.8 Mediant 3000...

  • Page 760: Heartbeat Packet Parameters

    Mediant 3000 51.3.4 Heartbeat Packet Parameters The Heartbeat packet parameters are described in the table below. The device sends a heartbeat packet to ensure that the far-end is passing traffic. Table 51-21: Heartbeat Packet Parameters Parameter Description EMS: APS IP Address...

  • Page 761: Bootp Parameters

    BootP requests. Notes:  For this parameter to take effect, a device reset is required.  When working with DHCP (i.e., the parameter DHCPEnable is set to 1), the selective BootP feature must be disabled. Version 6.8 Mediant 3000...
  • Page 762 Mediant 3000 Parameter Description [BootPDelay] Defines the interval between the device's startup and the first BootP/DHCP request that is issued by the device.  [1] = (Default) 1 second  [2] = 3 second  [3] = 6 second ...

  • Page 763: 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. For a detailed description of this table, see ''Configuring Firewall Settings'' on page 157. Version 6.8 Mediant 3000...

  • Page 764: Https Parameters

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

  • Page 765: Srtp Parameters

    (6 * 84). The DSP-depopulated blade is used for configurations with 21 spans and less. Therefore, no capacity reduction occurs in these sizes for T1 configurations (504/24 = 21 T1s). However, only 15 E1s instead of 16 (504/32 = 15.75) may be available. Version 6.8 Mediant 3000...
  • Page 766 Mediant 3000 Parameter Description Web/EMS: Media Security Global parameter that defines the handling of SRTP (when the Behavior EnableMediaSecurity parameter is set to 1). You can also [MediaSecurityBehaviour] configure this functionality per specific calls, using IP Profiles (IpProfile_MediaSecurityBehaviour). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page 329.
  • Page 767 IP Profile table, see ''Configuring IP Profiles'' on page 329. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 3000...

  • Page 768: Tls Parameters

    Mediant 3000 51.4.4 TLS Parameters The Transport Layer Security (TLS) parameters are described in the table below. Table 51-27: TLS Parameters Parameter Description Web: TLS Contexts Table Defines SSL/TLS certificates. CLI: configure system > tls # The format of the ini file table parameter is as follows:...
  • Page 769 (‘*’) to replace parts of the domain name. The valid range is a string of up to 49 characters. Note: This parameter is applicable only if the parameter PeerHostNameVerificationMode is set to 1 or 2. Version 6.8 Mediant 3000...

  • Page 770: Ssh Parameters

    Mediant 3000 Parameter Description Web: TLS Expiry Check Start Defines the number of days before the installed TLS server [TLSExpiryCheckStart] certificate is to expire at which the device must send a trap (acCertificateExpiryNotifiaction) to notify of this. The valid value is 0 to 3650. The default is 60.

  • Page 771: Ids Parameters

    Defines IDS Policies. [IDSPolicy] 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 163. Version 6.8 Mediant 3000...

  • Page 772: Ipsec Parameters

    Mediant 3000 Parameter Description IDS Rule Table Web: IDS Rule Table Defines rules for 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_DenyThreshold, IDSRule_DenyPeriod;...
  • Page 773 In the example above, two proposals are defined:  Proposal 0: AES, SHA1, DH group 2  Proposal 1: 3DES, SHA1, DH group 2 Note: For a detailed description of this table, see ''Configuring IP Security Proposal Table'' on page 171. Version 6.8 Mediant 3000...

  • Page 774: Quality Of Experience Parameters

    The Quality of Experience (QoE) parameters are described in the table below. Table 51-31: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of AudioCodes primary Session Experience CLI: configure voip/qoe Manager (SEM) server to where the quality experience reports are configuration/server-ip sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
  • Page 775 The format of the ini file table parameter is as follows: [MediaEnhancementRules] [MediaEnhancementRules] FORMAT MediaEnhancementRules_Index = MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of this table, see ''Configuring Media Enhancement Profiles'' on page 265. Version 6.8 Mediant 3000...

  • Page 776: Control Network Parameters

    Mediant 3000 51.6 Control Network Parameters 51.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 51-32: Proxy, Registration and Authentication SIP Parameters Parameter Description IP Group Table Web: IP Group Table This table configures IP Groups.
  • Page 777 Note: If this parameter is disabled and the ProxyName parameter is not configured, the proxy's IP address is used as the host name in the REGISTER Request-URI. Version 6.8 Mediant 3000...
  • Page 778 Mediant 3000 Parameter Description Web: Redundancy Mode Determines whether the device switches back to the primary EMS: Proxy Redundancy Mode Proxy after using a redundant Proxy. [ProxyRedundancyMode]  [0] Parking = (Default) The device continues working with a redundant (now active) Proxy until the next failure, after which it works with the next redundant Proxy.
  • Page 779 [1] SRV = If the Proxy IP address parameter contains a domain name without port definition (e.g., ProxyIP = domain.com), an SRV query is performed. The SRV query returns up to four Proxy host names and their weights. The Version 6.8 Mediant 3000...
  • Page 780 Mediant 3000 Parameter Description device then performs DNS A-record queries for each Proxy host name (according to the received weights) to locate up to four Proxy IP addresses. Thus, if the first SRV query returns two domain names and the A-record queries return two IP addresses each, no additional searches are performed.
  • Page 781 Balancing) in the ini file, use the ProxySet parameter. Proxy Set Table Web: Proxy Set Table This table parameter defines the Proxy Set ID table. This EMS: Proxy Set includes, for example, Proxy keep-alive and load balancing and Version 6.8 Mediant 3000...
  • Page 782 Mediant 3000 Parameter Description [ProxySet] redundancy mechanisms. The format of the ini file table parameter is as follows: [ ProxySet ] FORMAT ProxySet_Index = ProxySet_ProxyName, ProxySet_EnableProxyKeepAlive, ProxySet_ProxyKeepAliveTime, ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap, ProxySet_SRD, ProxySet_ClassificationInput, ProxySet_ProxyRedundancyMode, ProxySet_DNSResolveMethod, ProxySet_KeepAliveFailureResp, ProxySet_SuccessDetectionRetries, ProxySet_SuccessDetectionInterval, ProxySet_FailureDetectionRetransmissions; [ \ProxySet ] For a description of this table, see ''Configuring Proxy Sets'' on page 296.
  • Page 783 Defines the time interval (in seconds) after which a registration request is re-sent if registration fails with a 4xx response or if [RegistrationRetryTime] there is no response from the Proxy/Registrar server. The default is 30 seconds. The range is 10 to 3600. Version 6.8 Mediant 3000...
  • Page 784 Mediant 3000 Parameter Description Web: Registration Time Threshold Defines a threshold (in seconds) for re-registration timing. If EMS: Time Threshold this parameter is greater than 0, but lower than the computed [RegistrationTimeThreshold] re-registration timing (according to the parameter RegistrationTimeDivider), the re-registration timing is set to the...
  • Page 785 B-channel.  [1] Per Gateway = (Default) Single registration and authentication for the entire device. This is typically used for and digital modules. Note: This parameter is applicable only to the Gateway application. Version 6.8 Mediant 3000...
  • Page 786 Mediant 3000 Parameter Description Web: Set Out-Of-Service On Enables setting the , trunk, or entire device (i.e., all endpoints) Registration Failure to out-of-service if registration fails. EMS: Set OOS On Registration Fail  [0] Disable (default) [OOSOnRegistrationFail]  [1] Enable If the registration is per endpoint (i.e., AuthenticationMode is...
  • Page 787 CRLF keep-alive sequences. EMS: Ping Pong Keep Alive Time Defines the periodic interval (in seconds) after which a “ping” [PingPongKeepAliveTime] (double-CRLF) keep-alive is sent to a proxy/registrar, using the CRLF Keep-Alive mechanism. Version 6.8 Mediant 3000...
  • Page 788 Mediant 3000 Parameter Description The default range is 5 to 2,000,000. The default is 120. The device uses the range of 80-100% of this user-defined value as the actual interval. For example, if the parameter value is set to 200 sec, the interval used is any random time between 160 to 200 seconds.

  • Page 789: Network Application Parameters

    The valid value is 10 to 65,000. The default is 60. Notes:  Simple ACKs such as keepalives are not considered data packets.  TCP keepalive is enabled per SIP Interface in the SIP Interface table. Version 6.8 Mediant 3000...
  • Page 790 Mediant 3000 Parameter Description [TCPKeepAliveInterval] Defines the interval (in sec) between consecutive keep-alive probes, regardless of what the connection has exchanged in the meantime. The valid value is 10 to 65,000. The default is 10. Note: TCP keepalive is enabled per SIP Interface in the SIP Interface table.
  • Page 791 The format of the ini file table parameter is as follows: EMS: Remote Media [RemoteMediaSubnet] Subnet FORMAT RemoteMediaSubnet_Index = RemoteMediaSubnet_Realm, [SubRealm] RemoteMediaSubnet_RemoteMediaSubnetIndex, RemoteMediaSubnet_RemoteMediaSubnetName, RemoteMediaSubnet_PrefixLength, RemoteMediaSubnet_AddressFamily, RemoteMediaSubnet_DstIPAddress, RemoteMediaSubnet_QOEProfileName, RemoteMediaSubnet_BWProfileName; [\RemoteMediaSubnet] For a detailed description of this table, see ''Configuring Remote Media Subnets'' on page 272. Version 6.8 Mediant 3000...

  • Page 792: 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 793 PL=<receive packet loss>  JI=<jitter in ms>  LA=<latency in ms> Below is an example of the X-RTP-Stat header in a SIP BYE message: BYE sip:302@10.33.4.125 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.126;branch=z9hG4bKac2127550866 Max-Forwards: 70 From: <sip:401@10.33.4.126;user=phone>;tag=1c2113553324 To: <sip:302@company.com>;tag=1c991751121 Call-ID: 991750671245200001912@10.33.4.125 Version 6.8 Mediant 3000...
  • Page 794 Mediant 3000 Parameter Description CSeq: 1 BYE X-RTP-Stat: PS=207;OS=49680;;PR=314;OR=50240;PL=0;JI=600;LA=40 Supported: em,timer,replaces,path,resource- priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRAC K,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.6.2A.008.006 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0 Web/EMS: PRACK Mode Determines the PRACK (Provisional Acknowledgment) mechanism [PrackMode] mode for SIP 1xx reliable responses. ...
  • Page 795 Disconnect Time The new session expiry timeout is calculated by subtracting the [SessionExpiresDisconne configured value from the original timeout as specified in the Session- ctTime] Expires header. However, the new timeout must be greater than or Version 6.8 Mediant 3000...
  • Page 796 Mediant 3000 Parameter Description equal to one-third (1/3) of the Session-Expires value. If the refresher does not send a refresh request within the new timeout, the device disconnects the session (i.e., sends a SIP BYE). For example, if you configure the parameter to 32 seconds and the Session-Expires value is 180 seconds, the session timeout occurs 148 seconds (i.e., 180 minus 32) after the last session refresh.
  • Page 797 RTP using the bypass payload type (and no mid-call VBD or T.38 Re-INVITEs occur).  [1] = If the IsFaxUsed parameter is set to 1, the channel opens with Version 6.8 Mediant 3000...
  • Page 798 Mediant 3000 Parameter Description the FaxTransportMode parameter set to 1 (relay). This is required to detect mid-call fax tones and to send T.38 Re-INVITE messages upon fax detection. If the remote party supports T.38, the fax is relayed over T.38.
  • Page 799 For TLS, persistent connection may reduce the number of costly TLS handshakes to establish security associations, in addition to the initial TCP connection set up. Note: If the destination is a Proxy server, the TCP/TLS connection is persistent regardless of the settings of this parameter. Version 6.8 Mediant 3000...
  • Page 800 Mediant 3000 Parameter Description Web/EMS: TCP Timeout Defines the Timer B (INVITE transaction timeout timer) and Timer F [SIPTCPTimeout] (non-INVITE transaction timeout timer), as defined in RFC 3261, when the SIP transport type is TCP. The valid range is 0 to 40 sec. The default is 64 * SipT1Rtx parameter value.
  • Page 801 If a 'tgrp' value is specified in incoming messages, it is ignored.  [2] Send and Receive = The functionality of outgoing SIP messages is identical to the functionality described for option [1]. In addition, for incoming SIP INVITEs, if the Request-URI includes a Version 6.8 Mediant 3000...
  • Page 802 Mediant 3000 Parameter Description 'tgrp' parameter, the device routes the call according to that value (if possible). The Contact header in the outgoing SIP INVITE (Tel-to- IP call) contains "tgrp=<source trunk group ID>;trunk- context=<gateway IP address>”. The <source trunk group ID> is the Trunk Group ID where incoming calls from Tel is received.
  • Page 803 Record (AOR). For example, in call transfer where user A is talking to user B, and user A wants to transfer the call to user C. User A sends a REFER to user C: REFER sip:C@domain.com SIP/2.0 From: sip:A@domain.com;tag=99asd To: sip:C@domain.com Version 6.8 Mediant 3000...
  • Page 804 When configured, the string <UserAgentDisplayInfo 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 User's Manual Document #: LTRT-89738...
  • Page 805 This parameter is useful in the following call scenario example: Party A calls party B and coder G.711 is chosen. Party B is put on-hold while Party A blind transfers Party B to Party Version 6.8 Mediant 3000...
  • Page 806 Mediant 3000 Parameter Description Party C answers and Party B is made un-hold. However, as Party C supports only G.729 coder, re-negotiation of the supported coder is required. Note: This parameter is applicable only to the Gateway application. Web: Multiple Packetization...
  • Page 807 To header.  [2] P-Called-Party-ID header = Obtains the destination number from the P-Called-Party-ID header. Web/EMS: Enable Reason Enables the usage of the SIP Reason header. Header  [0] Disable [EnableReasonHeader]  [1] Enable (default) Version 6.8 Mediant 3000...
  • Page 808 Mediant 3000 Parameter Description Web/EMS: Gateway Name Defines a name for the device (e.g., device123.com). This name is [SIPGatewayName] used as the host part of the SIP URI in the From header. If not specified, the device's IP address is used instead (default).
  • Page 809 'rport' parmeter. Web: Enable X-Channel Determines whether the SIP X-Channel header is added to SIP Header messages for providing information on the physical Trunk/B-channel EMS: X Channel Header on which the call is received or placed. Version 6.8 Mediant 3000...
  • Page 810 Mediant 3000 Parameter Description  [XChannelHeader] [0] Disable = (Default) X-Channel header is not used.  [1] Enable = X-Channel header is generated by the device and sent in INVITE messages and 180, 183, and 200 OK SIP responses. The header includes the Trunk number, B-channel, and the device's IP address.
  • Page 811 27. This cause is mapped, by default, to SIP 502.  For mapping SIP-to-Q.931 and Q.931-to-SIP release causes, see Configuring Release Cause Mapping on page 417.  For a list of SIP responses-Q.931 release cause mapping, see Version 6.8 Mediant 3000...
  • Page 812 Mediant 3000 Parameter Description ''Alternative Routing to Trunk upon Q.931 Call Release Cause Code'' on page 448. Web: Enable Microsoft Enables the modification of the called and calling number for numbers Extension received with Microsoft's proprietary "ext=xxx" parameter in the SIP INVITE URI user part.
  • Page 813 In case of an MLPP call, the device uses the value of this parameter plus 1 as the index of the ringback tone in the CPT file (e.g., if this value is set to 1, then the index is 2, i.e., 1 + 1). Version 6.8 Mediant 3000...
  • Page 814 Mediant 3000 Parameter Description Web: Reanswer Time EMS: Regret Time Defines the time period the device waits for an MFC R2 Resume [RegretTime] (Reanswer) signal once a Suspend (Clear back) signal is received from the PBX. If this timer expires, the call is released. Note that this is applicable only to the MFC-R2 CAS Brazil variant.
  • Page 815 (i.e. Manipulation Set ID is set to -1). Notes:  This parameter is used only if the Outbound Message Manipulation Set parameter of the destination IP Group is not set.  This parameter is applicable only to the Gateway application. Version 6.8 Mediant 3000...
  • Page 816 Mediant 3000 Parameter Description Out-of-Service (Busy Out) Parameters Web/EMS: Enable Busy Out Enables the Busy Out feature. [EnableBusyOut]  [0] Disable (Default)  [1] Enable When Busy Out is enabled and certain scenarios exist, the device does the following: ...
  • Page 817 Graceful out-of-service enabled: The device rejects new incoming calls and only when all channels are idle (when graceful period ends or when all channels become idle before graceful period ends, whichever occurs first), does the device send an alarm on the trunk. Version 6.8 Mediant 3000...
  • Page 818 Mediant 3000 Parameter Description When connectivity is restored for the Busy Out feature or the Trunk Group is unlocked, the device clears the alarm. Note: For partially configured trunks (only some channels configured), this option only rejects new calls for the trunk; no alarm is sent.
  • Page 819 SIP message and the first retransmission of the same message. [msec] The default is 500. EMS: T1 RTX Note: The time interval between subsequent retransmissions of the [SipT1Rtx] same SIP message starts with SipT1Rtx. For INVITE requests, it is Version 6.8 Mediant 3000...
  • Page 820 Mediant 3000 Parameter Description multiplied by two for each new retransmitted message. For all other SIP messages, it is multiplied by two until SipT2Rtx. For example, assuming SipT1Rtx = 500 and SipT2Rtx = 4000:  The first retransmission is sent after 500 msec.
  • Page 821 The format of the ini file table parameter is as follows: [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Policy, MessagePolicy_MaxMessageLength, MessagePolicy_MaxHeaderLength, MessagePoliy_MaxBodyLength, MessagePolicy_MaxNumHeaders, MessagePolicy_MaxNumBodies, MessagePolicy_SendRejection, MessagePolicy_MethodListType, MessagePolicy_MethodList, MessagePolicy_BodyListType, MessagePolicy_BodyList; [/MessagePolicy] For a detailed description of this table, see Configuring SIP Message Policy Rules. Version 6.8 Mediant 3000...

  • Page 822: Coders And Profile Parameters

    Mediant 3000 51.8 Coders and Profile Parameters The profile parameters are described in the table below. Table 51-35: Profile Parameters Parameter Description Coders Table / Coder Groups Table Web: Coders Table/Coder This table parameter defines the device's coders. Each group can consist Group Settings of up to 10 coders.
  • Page 823 (TrunkGroup parameter). Therefore, 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 the ini file table parameter is as follows: Version 6.8 Mediant 3000...
  • Page 824 Mediant 3000 Parameter Description [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_TimeForReorderTone, TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode;...

  • Page 825: Channel Parameters

    IP Profile table, see ''Configuring IP Profiles'' on page or Tel Profile table, see Configuring Tel Profiles on page 326. Note: If this functionality is configured for a specific profile, the settings of this global parameter is ignored for calls associated Version 6.8 Mediant 3000...
  • Page 826 Mediant 3000 Parameter Description with the profile. Web: Network Echo Suppressor Enables the network Acoustic Echo Suppressor feature on SBC Enable calls. This feature removes echoes and sends only the near-end’s [AcousticEchoSuppressorSupport desired speech signal to the network (i.e., to the far-end party).

  • Page 827: Coder Parameters

    G.729EV coder. This parameter is defined per [G729EVMaxBitRate] session and is equal for all the parties. The initial generation bit rate is the minimum between the MaxBitRate and the MBS values.  [0] 8 KBPS (default) Version 6.8 Mediant 3000...
  • Page 828 Mediant 3000 Parameter Description  [1] 12 KBPS  [2] 14 KBPS  [3] 16 KBPS  [4] 18 KBPS  [5] 20 KBPS  [6] 22 KBPS  [7] 24 KBPS  [8] 26 KBPS  [9] 28 KBPS ...
  • Page 829  [0] 3.95 Kbps  [1] 5.75 Kbps  [2] 7.75 Kbps  [3] 9.80 Kbps  [4] 12.8 Kbps  [5] 16.8 Kbps  [6] 20.6 Kbps  [7] 23.8 Kbps  [8] 27.8 Kbps(default) Version 6.8 Mediant 3000...
  • Page 830 Mediant 3000 Parameter Description  [9] 34.2 Kbps  [10] 42.2 Kbps DSP Templates Table Web: DSP Template Mix Table This table parameter allows the device to use a combination of EMS: VoP Media Provisioning > two DSP templates and determines the percentage of DSP General Settings resources allocated per DSP template.

  • Page 831: Dtmf Parameters

    NTEs (RFC 4733/2833 DTMF relay) to the IP side, regardless of the DTMF signal duration on the TDM side. The range is -1 to 200,000,000 msec. The default is -1 (i.e., NTE stops only upon detection of an End event). Version 6.8 Mediant 3000...

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

    Mediant 3000 51.9.4 RTP, RTCP and T.38 Parameters The RTP, RTCP and T.38 parameters are described in the table below. Table 51-39: RTP/RTCP and T.38 Parameters Parameter Description Web: Dynamic Jitter Buffer Minimum Global parameter that defines the minimum delay (in msec) of Delay the device's dynamic Jitter Buffer.
  • Page 833 Virtual Router Redundancy Protocol (VRRP) for redundancy, then set this parameter to 0 or 2. EMS: Enable Media UDP Checksum Enables the device to insert a non-zero UDP layer checksum Version 6.8 Mediant 3000...
  • Page 834 Mediant 3000 Parameter Description [EnableMediaUDPChecksum] on outgoing packets for UDP streams carrying media content (audio and video).  [0] = (Default) Disable - the outgoing UDP packets carry the value of 0x00 (i.e., no checksum) in the UDP checksum field of the UDP header.
  • Page 835 Defines the IP address of the Event State Compositor (ESC). EMS: Esc IP The device sends RTCP XR reports to this server, using SIP [RTCPXREscIP] PUBLISH messages, according to Internet-Draft draft-ietf- sipping-rtcp-summary-13. The address can be configured as a Version 6.8 Mediant 3000...
  • Page 836 Mediant 3000 Parameter Description numerical IP address or as a domain name. Note:  Instead of sending RTCP XR to an ESC server, you can send RTCP XR to an IP Group (see the PublicationIPGroupID parameter).  This parameter is applicable only to the Gateway application.

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

    Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 329. Web: V.32 Modem Transport Type Determines the V.32 modem transport type. EMS: V32 Transport  [0] Disable = Transparent. Version 6.8 Mediant 3000...
  • Page 838 Mediant 3000 Parameter Description  [V32ModemTransportType] [2] Enable Bypass (default)  [3] Events Only = Transparent with Events. Notes:  This parameter applies only to V.32 and V.32bis modems.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 329.
  • Page 839 [8] 21600bps = 21.6 kbps  [9] 24000bps = 24 kbps  [10] 26400bps = 26.4 kbps  [11] 28800bps = 28.8 kbps  [12] 31200bps = 31.2 kbps  [13] 33600bps = 33.6 kbps (default) Notes: Version 6.8 Mediant 3000...
  • Page 840 Mediant 3000 Parameter Description  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 SDP T38MaxBitRate parameter. The negotiated T38MaxBitRate is the minimum rate supported between the local and remote endpoints.
  • Page 841 RTP and for T38 must be different. Therefore, set the T38UseRTPPort parameter to 0. Web/EMS: T.38 Max Datagram Defines the maximum size of a T.38 datagram that the device Size can receive. This value is included in the outgoing SDP when Version 6.8 Mediant 3000...
  • Page 842 Mediant 3000 Parameter Description [T38MaxDatagramSize] T.38 is used. The valid range is 120 to 600. The default is 560. Web/EMS: T38 Fax Max Buffer Defines the maximum size (in bytes) of the device's T.38 buffer. [T38FaxMaxBufferSize] This value is included in the outgoing SDP when T.38 is used for fax relay over IP.
  • Page 843 The value range is 8 to 32. The default is 8. axWindowSize] Web: SPRT Transport Ch.3 Max Defines the maximum payload size for V.150.1 SPRT Transport Payload Size Channel 3. [V1501SPRTTransportChannel3M The range is 140 to 256. The default is 140. axPayloadSize] Version 6.8 Mediant 3000...

  • Page 844: Dtmf And Hook-Flash Parameters

    Mediant 3000 51.10.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below. Table 51-41: DTMF and Hook-Flash Parameters Parameter Description Hook-Flash Parameters Web/EMS: Hook-Flash Code Defines the digit pattern used by the PBX to indicate a Hook Flash [HookFlashCode] event.
  • Page 845 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). Version 6.8 Mediant 3000...
  • Page 846 Mediant 3000 Parameter Description  When TxDTMFOption is set to 0, the RFC 2833 payload type is set according to the parameter RFC2833PayloadType for both transmit and receive.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_FirstTxDtmfOption and IpProfile_SecondTxDtmfOption).

  • Page 847: Digit Collection And Dial Plan Parameters

    The digit map pattern can contain up to 52 options (rules), each separated by a vertical bar (|). The maximum length of the entire digit pattern is 152 characters. The available notations include the following: Version 6.8 Mediant 3000...
  • Page 848 Mediant 3000 Parameter Description  [n-m]: Range of numbers (not letters).  . (single dot): Repeat digits until next notation (e.g., T).  x: Any single digit.  T: Dial timeout (configured by the TimeBetweenDigits parameter).  S: Short timer (configured by the TimeBetweenDigits parameter;...

  • Page 849: Voice Mail Parameters

    Redirect number reason to the SIP 'cause' parameter in the Request-URI. Redirecting Reason >> SIP Response Code Unknown >> 404 User busy >> 486 No reply >> 408 Deflection >> 487/480 Unconditional >> 302 Version 6.8 Mediant 3000...
  • Page 850 Mediant 3000 Parameter Description 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. [WaitForBusyTime] Defines the time (in msec) that the device waits to detect busy and/or reorder tones.
  • Page 851 The valid value is a string. Digit Patterns The following digit pattern parameters apply only to voice mail applications that use the DTMF communication method. For the available pattern syntaxes, refer to the CPE Configuration Guide for Voice Mail. Version 6.8 Mediant 3000...
  • Page 852 Mediant 3000 Parameter Description Web: Forward on Busy Digit Defines the digit pattern used by the PBX to indicate 'call forward Pattern (Internal) on busy' when the original call is received from an internal EMS: Digit Pattern Forward On extension.

  • Page 853: Supplementary Services Parameters

    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 message to SIP 200 OK with the P-Asserted-Identity Version 6.8 Mediant 3000...
  • Page 854 Mediant 3000 Parameter Description header. In the opposite direction, if the ISDN device receives a 200 OK with P-Asserted-Identity header, it interworks it to the Connected party number and name in the Q.931 Connect message, including its privacy. Web/EMS: Use Destination As...

  • Page 855: Call Waiting Parameters

    To use this service, the devices at both ends must support this option.  For the device to respond to SIP 3xx responses with a new SIP request (forwarding the original request), set this parameter to Enable. Version 6.8 Mediant 3000...

  • Page 856: Call Hold Parameters

    Mediant 3000 51.10.5.4 Call Hold Parameters The call hold parameters are described in the table below. Table 51-47: Call Hold Parameters Parameter Description Web/EMS: Enable Hold Global parameter that enables the interworking of the Hold/Retrieve [EnableHold] supplementary service from ISDN PRI to SIP. You can also configure this functionality per specific calls, using IP Profiles (IpProfile_EnableHold).

  • Page 857: Call Transfer Parameters

    After the KeyBlindTransfer DTMF digits sequence is dialed, the current call is put on hold (using a Re-INVITE message), a dial tone is played to the channel, and then the phone number collection starts. Version 6.8 Mediant 3000...
  • Page 858 Mediant 3000 Parameter Description After the destination phone number is collected, it is sent to the transferee in a SIP REFER request in a Refer-To header. The call is then terminated and a confirmation tone is played to the channel. If the phone number collection fails due to a mismatch, a reorder tone is played to the channel.

  • Page 859: Mlpp And Emergency Call Parameters

    Web: Emergency Special Release Enables the device to send a SIP 503 "Service Unavailable" Cause response if an emergency call cannot be established (i.e., [EmergencySpecialReleaseCause] rejected). This can occur, for example, due to the PSTN (for Version 6.8 Mediant 3000...
  • Page 860 Mediant 3000 Parameter Description example, the destination is busy or not found) or ELIN Gateway (for example, lack of resources or an internal error).  [0] = Disable (default)  [1] = Enable Web/EMS: Emergency Numbers Defines a list of “emergency” numbers.
  • Page 861 MLPP Service Domain obtained from the Precedence IE. The valid value is 6 hexadecimal digits. The default is ‘000000’. Note: This parameter is applicable only to the MLPP NI-2 ISDN variant with CallPriorityMode set to 1. Version 6.8 Mediant 3000...
  • Page 862 Mediant 3000 Parameter Description Defines the MLPP network identifier (i.e., International prefix or [MLPPNetworkIdentifier] Telephone Country Code/TCC) for IP-to-ISDN calls, according to the UCR 2008 and ITU Q.955 specifications. The valid range is 1 to 999. The default is 1 (i.e., USA).
  • Page 863 [MLPPFlashOverOverRTPDSCP] The valid range is -1 to 63. The default is -1. Note: If set to -1, the DiffServ value is taken from the global parameter PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call. Version 6.8 Mediant 3000...

  • Page 864: Call Cut-Through Parameters

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

  • Page 865: Pstn Parameters

    Timeslots 1 to 31 of each trunk are mapped to DSP channels.  [6] E1 TRANSPARENT 30 = Transparent protocol, where no signaling is provided by the device. Timeslots 1 to 31, excluding Version 6.8 Mediant 3000...
  • Page 866 Mediant 3000 Parameter Description time slot 16 of all trunks are mapped to DSP channels.  [7] E1 MFCR2 = Common E1 MFC/R2 CAS protocols (including line signaling and compelled register signaling).  [8] E1 CAS = Common E1 CAS protocols (including line signaling and MF/DTMF address transfer).
  • Page 867 E1: E1 CRC4 MultiFrame Format extended G.706B (same as c)  T1: T1 Extended Super Frame with CRC6 (same as D)  [1] Super Frame = T1 SuperFrame Format (as B).  [a] E1 FRAMING DDF = E1 DoubleFrame Format - CRC4 is Version 6.8 Mediant 3000...
  • Page 868 Mediant 3000 Parameter Description forced to off  [b] E1 FRAMING MFF CRC4 = E1 CRC4 MultiFrame Format - CRC4 is always on  [c] E1 FRAMING MFF CRC4 EXT = E1 CRC4 MultiFrame Format extended G.706B - auto negotiation is on. If the negotiation fails, it changes automatically to CRC4 off (ddf) ...
  • Page 869 Defines static TDM hair-pinning (cross-connection) performed at initialization. The connection is between trunks with an option to exclude a single B-channel in each trunk. Format example: T0-T1/B3,T2-T3,T4-T5/B2. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 3000...

  • Page 870: Tdm Bus And Clock Timing Parameters

    Mediant 3000 Parameter Description Web: Enable TDM Tunneling Enables TDM tunneling. EMS: TDM Over IP  [0] Disable (default) [EnableTDMoverIP]  [1] Enable When TDM Tunneling is enabled, the originating device automatically initiates SIP calls from all enabled B-channels pertaining to E1/T1/J1 spans that are configured with the 'Transparent' protocol.
  • Page 871  [0] Manual (default)  [1] Auto Non-Revertive  [2] Auto Revertive Web: TDM Bus Fallback Clock Determines the fallback clock source on which the device Source synchronizes in the event of a clock failure. Version 6.8 Mediant 3000...
  • Page 872 Mediant 3000 Parameter Description  EMS: TDM Bus Fallback Clock [4] Network (default) [TDMBusFallbackClock]  [8] H.110_A  [9] H.110_B  [10] NetReference1  [11] NetReference2 Web/EMS: TDM Bus Master- Defines the SC/MVIP/H.100/H.110. Slave Selection  [0] SlaveMode = (Default) Slave mode (another device must...
  • Page 873 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 874 Mediant 3000 Parameter Description  [5] T12 Web: T1 External Reference Defines the transmission power between the timing module on the Transmit Line Build Out SAT blade and the T1 external reference clock (External Reference EMS: T1 Line Build Out Transmit Line Build Out).

  • Page 875: 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' CASTableIndex_5 = 0 Version 6.8 Mediant 3000...
  • Page 876 Mediant 3000 Parameter Description 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. Defines the CAS file name (e.g., 'E_M_WinkTable.dat') that [CASFileName_x] defines the CAS protocol, where x denotes the CAS file ID (0-7).
  • Page 877 [-1] Default = Default value. Web: Digit Signaling System Defines which Signaling System to use in both directions [CASStateMachineDigitSignalin (detection\generation). gSystem]  [0] DTMF = DTMF signaling.  [1] MF = (Default) MF signaling.  [-1] Default = Default value. Version 6.8 Mediant 3000...

  • Page 878: Isdn Parameters

    Mediant 3000 51.10.6.4 ISDN Parameters The ISDN parameters are described in the table below. Table 51-55: ISDN Parameters Parameter Description Web: ISDN Termination Side Determines the ISDN termination side. EMS: Termination Side  [0] User side = (Default) ISDN User Termination Equipment [TerminationSide] (TE) side.
  • Page 879 Otherwise, the Channel ID is sent only if the device requires changing the proposed Channel ID.  [4096] USER SETUP ACK = (Default) The Setup Ack message is sent by the SIP Gateway application layer and not automatically by the PSTN stack. Version 6.8 Mediant 3000...
  • Page 880 Mediant 3000 Parameter Description  [8192] CHAN ID IN CALL PROC = The device sends Channel ID in a Q.931 Call Proceeding message.  [65536] PROGR IND IN SETUP ACK = (Default) The device includes Progress Indicator (PI=8) in Setup Ack message if an empty called number is received in an incoming Setup message.
  • Page 881 Note: This option is applicable only to QSIG.  [2147483648] 5ESS National Mode For Bch Maintenance = Use the National mode of AT&T 5ESS for B-channel maintenance. Notes:  To configure the device to support several ISDNIBehavior Version 6.8 Mediant 3000...
  • Page 882 Mediant 3000 Parameter Description features, enter a summation of the individual feature values. For example, to support both [512] and [2048] features, set the parameter ISDNIBehavior is set to 2560 (i.e., 512 + 2048).  When configuring in the Web interface, to select the options click the arrow button and then for each required option select 1 to enable.
  • Page 883 IA5 character in the called_nb, and is not restricted to extended digits only (i.e., 0-9,*,#).  [16384] DLCI REVERSED OPTION = Behavior bit used in the IUA interface groups to indicate that the reversed format Version 6.8 Mediant 3000...
  • Page 884 Mediant 3000 Parameter Description of the DLCI field must be used. Note: When using the ini file to configure the device to support several ISDNOutCallsBehavior features, add the individual feature values. For example, to support both [2] and [16] features, set ISDNOutCallsBehavior = 18 (i.e., 2 + 16).

  • Page 885: Ds3 Parameters

    User's Manual 51. Configuration Parameters Reference 51.10.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. Table 51-56: DS3 Parameters Parameter Description DS3 Settings Table [DS3Config] This table parameter configures the DS3 (T3) interfaces. This...

  • Page 886: Sdh/Sonet Parameters

    51.10.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. Table 51-57: SDH/SONET Parameters Parameter Description Web/EMS: Transmission Type Defines the PSTN transmission type for the device.
  • Page 887 Notes:  For this parameter to take effect, a device reset is required.  This parameter is applicable only when the SDHFbrGrp_Protected parameter is set to 1.  When configured in Revertive mode, the Wait-to-Restore time Version 6.8 Mediant 3000...
  • Page 888 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 889: Isdn And Cas Interworking Parameters

    SIP message for routing [MinOverlapDigitsForRouting Tel-to-IP calls. The valid value range is 0 to 49. The default is 1. Note: This parameter is applicable when the ISDNRxOverlap parameter is set to [2] or [3]. Version 6.8 Mediant 3000...
  • Page 890 Mediant 3000 Parameter Description Web/EMS: ISDN Overlap IP to Enables ISDN overlap dialing for IP-to-Tel calls. This feature is part Tel Dialing of ISDN-to-SIP overlap dialing according to RFC 3578. [ISDNTxOverlap]  [1] Through SIP = The device sends the first received digits from the initial INVITE to the Tel side in an ISDN Setup message.
  • Page 891 SIP messages. The ISDN Setup message is tunneled using SIP INVITE, all mid-call messages are tunneled using SIP INFO, and ISDN Disconnect/Release message is tunneled using SIP BYE messages. The raw data from the ISDN Version 6.8 Mediant 3000...
  • Page 892 Mediant 3000 Parameter Description is inserted into a proprietary SIP header (X-ISDNTunnelingInfo) or a dedicated message body (application/isdn) in the SIP messages. Notes:  For this feature to function, you must set the parameter ISDNDuplicateQ931BuffMode to 128 (i.e., duplicate all messages).
  • Page 893 The valid value range is 0 to 36. The default is 0. This feature operates as follows: If an isub parameter is received in the Request-URI, for example, INVITE sip:9565645;isub=1234@host.domain:user=phone SIP/2.0 then the isub value is sent in the ISDN Setup message as the Version 6.8 Mediant 3000...
  • Page 894 Mediant 3000 Parameter Description destination subaddress. If the isub parameter is not received in the user part of the Request-URI, the device searches for it in the URI parameters of the To header, for example, To: "Alex" <sip: 9565645@host.domain;isub=1234> If present, the isub value is sent in the ISDN Setup message as the destination subaddress.
  • Page 895 [1] Enable = The CPC is relayed between SIP and PRI. If enabled, the CPC received in the Originating Line Information (OLI) IE of an incoming ISDN Setup message is relayed to the From/P-Asserted-Identity headers using the 'cpc' parameter in the Version 6.8 Mediant 3000...
  • Page 896 Mediant 3000 Parameter Description outgoing INVITE message, and vice versa. For example (calling party is a payphone): From:<sip:2000;cpc=payphone@10.8.23.70>;tag=1c18 06157451 Note: This feature is applicable only to the NI-2 PRI and E1_MFC_R2 variants. Defines the interworking between the SIP INVITE's User-to-User [UserToUserHeaderFormat] header and the ISDN User-to-User (UU) IE data.
  • Page 897  This parameter is applicable to ISDN protocols.  This parameter is used together with the PlayRBTone2Trunk parameter.  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Version 6.8 Mediant 3000...
  • Page 898 Mediant 3000 Parameter Description Web/EMS: PSTN Alert Timeout Defines the Alert Timeout (ISDN T301 timer) in seconds for [TrunkPSTNAlertTimeout_x] outgoing calls to PSTN, per trunk. This timer is used between the time that an ISDN Setup message is sent to the Tel side (IP-to-Tel call establishment) and a Connect message is received.
  • Page 899 For example: '1,2,4,10,12,6'. [SendIEonTG] Notes:  You can configure different IE data for Trunk Groups by defining this parameter for different IP Profile IDs (using the parameter IPProfile), and then assigning the required IP Profile ID in the Version 6.8 Mediant 3000...
  • Page 900 Mediant 3000 Parameter Description Inbound IP Routing table (PSTNPrefix).  When IP Profiles are used for configuring different IE data for Trunk Groups, this parameter is ignored. Web: Enable User-to-User IE Enables transfer of User-to-User (UU) IE from ISDN PRI to SIP.
  • Page 901 Trunk Groups, by using the parameter EnableTransferAcrossTrunkGroups.  The device initiates the ECT process after receiving a SIP REFER message only for trunks that are configured to User side.  [3] = Supports CAS Normal transfer. When a SIP REFER Version 6.8 Mediant 3000...
  • Page 902 Mediant 3000 Parameter Description message is received, the device performs a Blind Transfer by executing a CAS Wink, dialing the Refer-to number to the switch, and then releasing the call.  [4] = Supports QSIG Single Step transfer: IP-to-Tel: When a SIP REFER message is received, the device performs a transfer by sending a Facility message to the PBX, initiating Single Step transfer.
  • Page 903 [1] Enable = (Default) The device sends a SIP REFER message to the remote call party if ECT/TBCT Facility messages are received from the ISDN side (e.g., from a PBX). [DisableFallbackTransferToT Enables "hairpin" TDM transfer upon ISDN (ECT, RLT, or TBCT) Version 6.8 Mediant 3000...
  • Page 904 Mediant 3000 Parameter Description call transfer failure. When this feature is enabled and an ISDN call transfer failure occurs, the device sends a SIP NOTIFY message with a SIP 603 Decline response.  [0] = (Default) The device performs a hairpin TDM transfer upon ISDN call transfer.

  • Page 905: Answer And Disconnect Supervision Parameters

    To activate this feature, set the EnableDSPIPMDetectors parameter to 1.  This feature is applicable only when the protocol type is CAS. Web/EMS: Max Call Duration Defines the maximum duration (in minutes) of a call. If this duration Version 6.8 Mediant 3000...
  • Page 906 Mediant 3000 Parameter Description (min) is reached, the device terminates the call. This feature is useful for [MaxCallDuration] ensuring available resources for new calls, by ensuring calls are properly terminated. The valid range is 0 to 35,791. The default is 0 (i.e., no limitation).
  • Page 907 [1] Enable = (Default) Call is released upon detection of busy or reorder (fast busy) tone. Notes:  This parameter is applicable only to CAS protocols.  This parameter is also applicable to the IP-to-IP application.  This parameter can also be configured in a Tel Profile. Version 6.8 Mediant 3000...

  • Page 908: Tone Parameters

    Mediant 3000 51.10.9 Tone Parameters This subsection describes the device's tone parameters. 51.10.9.1 Telephony Tone Parameters The telephony tone parameters are described in the table below. Table 51-60: Tone Parameters Parameter Description [PlayHeldToneForIP2IP] Enables playing a held tone to an IP-to-IP leg instead of placing it on hold.
  • Page 909 (No User Responding), the device plays the user-defined tone to the Tel side. The user-defined tone is configured when creating the PRT file, using AudioCodes DConvert utility. The tone must be assigned to the "acSpecialConditionTone" (Tone Type 21) option in DConvert.
  • Page 910 Mediant 3000 Parameter Description of a 183 response does not cause the device configured for CAS to play a ringback tone (unless the SIP183Behaviour parameter is set to 1). The device configured for ISDN operates according to the LocalISDNRBSource parameter:...
  • Page 911 If a 180 response is received, but the 'early media' voice channel is not opened, the device configured for CAS plays a ringback tone to the PSTN. The device configured for ISDN operates according to the LocalISDNRBSource parameter: Version 6.8 Mediant 3000...
  • Page 912 Mediant 3000 Parameter Description  If LocalISDNRBSource is set to 1, the device plays a ringback tone and sends an ISDN Alert with PI = 8 to the ISDN (unless the ProgressIndicator2ISDN_x parameter is configured differently).  If LocalISDNRBSource is set to 0, the device doesn't play a ringback tone.

  • Page 913: Tone Detection Parameters

    SITQ850Cause, which determines the Q.850 cause value specified in the SIP Reason header that is included in a 4xx response when a SIT tone is detected on an IP-to-Tel call. To disconnect IP-to-CAS calls when a SIT tone is detected, Version 6.8 Mediant 3000...

  • Page 914: Metering Tone Parameters

    Mediant 3000 Parameter Description the following parameters must be configured:  SITDetectorEnable = 1  UserDefinedToneDetectorEnable = 1  DisconnectOnBusyTone = 1 (applicable for busy, reorder, and SIT tones) Notes:  For this parameter to take effect, a device reset is required.

  • Page 915: Trunk Groups And Routing Parameters

    This table parameter configures and activates the device's EMS: SIP Endpoints > Phones Trunk channels. This is done by defining telephone numbers [TrunkGroup] and assigning them to Trunk Groups. The format of the ini file table parameter is as follows: Version 6.8 Mediant 3000...
  • Page 916 Mediant 3000 Parameter Description [TrunkGroup] FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_FirstTrunkId, TrunkGroup_FirstBChannel, TrunkGroup_LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileId, TrunkGroup_LastTrunkId, TrunkGroup_Module; [\TrunkGroup] Notes:  Trunk Group ID 1 is denoted as 0 in the table.  For a description of this table, seeConfiguring Trunk Group Table on page 391.
  • Page 917 IP side, the outgoing source number (and display name) are set to "100" and Presentation is set to Allowed (0).  If 'From: <sip:400@101.102.103.104>' is received from the IP side, the outgoing source number is set Version 6.8 Mediant 3000...
  • Page 918 Mediant 3000 Parameter Description to "400" and Presentation is set to Restricted (1).  [2] Preferred = If a display name is received from the IP side, the display name of the IP side is used as the Tel source number. If no display name is received from the IP side, this setting does not affect the Tel source number.
  • Page 919 Proxies or Proxy Sets, it is unnecessary to configure the Proxy IP addresses in the routing table. The device allows SIP calls received from the Proxy IP addresses even if these addresses are not configured in the routing table. Version 6.8 Mediant 3000...
  • Page 920 Mediant 3000 Parameter Description Web/EMS: Filter Calls to IP Enables filtering of Tel-to-IP calls when a Proxy is used. [FilterCalls2IP]  [0] Don't Filter = (Default) The device doesn't filter calls when using a Proxy.  [1] Filter = Filtering is enabled.
  • Page 921 INVITE to a specific IP Group or to a fax server according to the Outbound IP Routing table rules. This option is applicable only to ISDN. Note: This parameter has replaced the EnableFaxRerouting parameter. For backward compatibility, the Version 6.8 Mediant 3000...
  • Page 922 Mediant 3000 Parameter Description EnableFaxRerouting parameter set to 1 is equivalent to the FaxReroutingMode parameter set to 1. [FaxReroutingDelay] Defines the maximum time interval (in seconds) that the device waits for CNG detection before re-routing calls identified as fax calls to fax destinations (terminating fax machine).
  • Page 923 Defines the interval (in seconds) to wait before sending [ForkingDelayTimeForInvite] INVITE messages to the other members of the forking group. The INVITE is immediately sent to the first member. The valid value range is 0 to 40. The default is 0 (i.e., send immediately). Version 6.8 Mediant 3000...

  • Page 924: Ip Connectivity Parameters

    Mediant 3000 51.10.11 IP Connectivity Parameters The IP connectivity parameters are described in the table below. Table 51-64: IP Connectivity Parameters Parameter Description Web: Enable Alt Routing Tel to IP Enables the Alternative Routing feature for Tel-to-IP calls. EMS: Enable Alternative Routing ...

  • Page 925: Alternative Routing Parameters

     [2] Proxy = Proxy list is used to locate a redundant route. Note: To implement the Redundant Routing Mode mechanism, you first need to configure the parameter AltRouteCauseTEL2IP (Reasons for Alternative Routing table). Version 6.8 Mediant 3000...
  • Page 926 Mediant 3000 Parameter Description [DisconnectCallwithPIifAlt] Defines when the device sends the IP-to-Tel call to an alternative route (if configured) when it receives an ISDN Q.931 Disconnect message from the Tel side.  [0] (Default) = The device forwards early media to the IP side if Disconnect includes PI, and disconnects the call when a Release message is received.

  • Page 927: Number Manipulation Parameters

    Source number of the original call if it is a Tel-to-IP call  Destination number of the original call if it is an IP-to-Tel call This source number can also be used as the value for the Version 6.8 Mediant 3000...
  • Page 928 Mediant 3000 Parameter Description '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. Note: This manipulation does not affect IP-to-Trunk Group routing rules.
  • Page 929 [3] Network Provided = CPN set by network. Note: This parameter is applicable only if the Remote Party ID (RPID) header is enabled. Web: Send Screening Indicator Overrides the screening indicator of the calling party's number for Version 6.8 Mediant 3000...
  • Page 930 Mediant 3000 Parameter Description to ISDN IP-to-Tel ISDN calls. EMS: Screening Indicator To  [-1] Not Configured = (Default) Not configured (interworking ISDN from IP to ISDN). [ScreeningInd2ISDN]  [0] User Provided = user provided, not screened.  [1] User Passed = user provided, verified and passed.
  • Page 931 For example: After receiving a Called Number of 555, NPI of 1 and TON of 3, the modified number becomes 13555. This number can later be used for manipulation and routing. Web: Add NPI and TON to Determines whether the NPI and TON values are added as the Version 6.8 Mediant 3000...
  • Page 932 Mediant 3000 Parameter Description Redirect Number prefix to the Redirect number in INVITE messages' Diversion or [AddNPIandTON2RedirectNum History-Info headers, for ISDN Tel-to-IP calls. ber]  [0] Yes (Default)  [1] No Web: IP to Tel Remove Routing Determines whether or not the device removes the prefix (as...
  • Page 933 [ CallingNameMapIp2Tel ] FORMAT CallingNameMapIp2Tel_Index = CallingNameMapIp2Tel_ManipulationName, CallingNameMapIp2Tel_DestinationPrefix, CallingNameMapIp2Tel_SourcePrefix, CallingNameMapIp2Tel_CallingNamePrefix, CallingNameMapIp2Tel_SourceAddress, CallingNameMapIp2Tel_RemoveFromLeft, CallingNameMapIp2Tel_RemoveFromRight, CallingNameMapIp2Tel_LeaveFromRight, CallingNameMapIp2Tel_Prefix2Add, CallingNameMapIp2Tel_Suffix2Add; [ \CallingNameMapIp2Tel ] For a detailed description of this table, see ''Configuring SIP Calling Name Manipulation'' on page 407. Version 6.8 Mediant 3000...
  • Page 934 Mediant 3000 Parameter Description Calling Name Manipulations Tel-to-IP Table This table parameter configures rules for manipulating the calling [CallingNameMapTel2Ip] name (caller ID) for Tel-to-IP calls. This can include modifying or removing the calling name. [ CallingNameMapTel2Ip ] FORMAT CallingNameMapTel2Ip_Index =...
  • Page 935 Manipulation Table for Tel > IP Tel-to-IP calls. The format of the ini file table parameter is as Calls follows: EMS: SIP Manipulations > [SourceNumberMapTel2Ip] Source Telcom to IP FORMAT SourceNumberMapTel2Ip_Index = [SourceNumberMapTel2IP] SourceNumberMapTel2Ip_ManipulationName, SourceNumberMapTel2Ip_DestinationPrefix, SourceNumberMapTel2Ip_SourcePrefix, Version 6.8 Mediant 3000...
  • Page 936 Mediant 3000 Parameter Description SourceNumberMapTel2Ip_SourceAddress, SourceNumberMapTel2Ip_NumberType, SourceNumberMapTel2Ip_NumberPlan, SourceNumberMapTel2Ip_RemoveFromLeft, SourceNumberMapTel2Ip_RemoveFromRight, SourceNumberMapTel2Ip_LeaveFromRight, SourceNumberMapTel2Ip_Prefix2Add, SourceNumberMapTel2Ip_Suffix2Add, SourceNumberMapTel2Ip_IsPresentationRestricted, NumberMapTel2Ip_SrcTrunkGroupID, NumberMapTel2Ip_SrcIPGroupID; [\SourceNumberMapTel2Ip] For a detailed description of this table, see ''Configuring Source/Destination Number Manipulation'' on page 399. Redirect Number IP -to-Tel Table Web: Redirect Number IP -> Tel...
  • Page 937 SIP Phone-Context Mapping Rules'' on page 415. Web/EMS: Add Phone Context Determines whether the received Phone-Context parameter is As Prefix added as a prefix to the outgoing ISDN Setup message withCalled [AddPhoneContextAsPrefix] and Calling numbers.  [0] Disable (default)  [1] Enable Version 6.8 Mediant 3000...

  • Page 938: Sbc Parameters

    [NumOfSubscribes] sessions permitted on the device. The valid value is any value between 0 and the maximum supported SUBSCRIBE sessions. When set to -1, the device uses the default value. For more information, contact your AudioCodes sales representative. Notes: ...
  • Page 939 [SBCSessionRefreshingPolic BYE was sent by one of the UAs. The SIP Session-Expires header conveys the lifetime of the session, which is sent in re-INVITE or UPDATE requests (session refresh requests). The 'refresher=' parameter in the Session- Version 6.8 Mediant 3000...
  • Page 940 Mediant 3000 Parameter Description Expires header (sent in the initial INVITE or subsequent 2xx response) indicates who sends the session refresh requests. If the parameter contains the value 'uac', the device performs the refreshes; if the parameter contains the value 'uas', the remote proxy performs the refreshes.
  • Page 941  [1] Sip = The "sip" URI is used. [SBCDiversionUriType]  [2] Tel = The "tel" URI is used. Note: The parameter is applicable only if the Diversion header is Version 6.8 Mediant 3000...
  • Page 942 Mediant 3000 Parameter Description used. The SBCDiversionMode and SBCHistoryInfoMode parameters in the IP Profile table determine the call redirection (diversion) SIP header to use - History-Info or Diversion. Web: SBC Server Auth Mode Defines whether authentication of the SIP client is done locally (by [SBCServerAuthMode] the device) or by a RADIUS server.
  • Page 943 (after the device forwards the REGISTER [SBCProxyRegistrationTime] message). When set to 0, the device sends the Expires header's value as received from the user to the proxy. The valid range is 0 to 2,000,000 seconds. The default is 0. Version 6.8 Mediant 3000...
  • Page 944 Mediant 3000 Parameter Description Web: SBC Survivability Defines the duration of the periodic registrations between the user Registration Time and the device, when the device is in survivability state (i.e., when [SBCSurvivabilityRegistration REGISTER requests cannot be forwarded to the proxy and are Time] terminated by the device).
  • Page 945 (UA). The RTP packets do not traverse the device. Instead, the two SIP UAs establish a direct RTP/SRTP flow between one another. Signaling continues to traverse the device with minimal intermediation and involvement to enable certain SBC abilities such Version 6.8 Mediant 3000...
  • Page 946 Mediant 3000 Parameter Description as routing  [0] Disable = (Default) All calls traverse the device (i.e., no direct media). If No Media Anchoring is enabled for an SRD (in the SRD table), then calls between endpoints belonging to that SRD use No Media Anchoring.
  • Page 947 RTP mode or any other media such as coders, is different and has not been negotiated between the user agents.  [2] Never = Media synchronization is never performed. Web/EMS: SBC Fax Detection Defines the duration (in seconds) for which the device attempts to Version 6.8 Mediant 3000...
  • Page 948 Mediant 3000 Parameter Description Timeout detect fax (CNG tone) immediately upon the establishment of a voice session. The interval starts from the establishment of the CLI: configure voip/sbc general- voice call. setting/sbc-fax-detection- timeout The valid value is 1 to any integer. The default is 10.
  • Page 949 IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_RequestType, IP2IPRouting_MessageCondition, IP2IPRouting_ReRouteIPGroupID, IP2IPRouting_Trigger, IP2IPRouting_CallSetupRulesSetId, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions, IP2IPRouting_GroupPolicy, IP2IPRouting_CostGroup; [ \IP2IPRouting ] For a detailed description of this table, see ''Configuring SBC IP-to- IP Routing Rules'' on page 537. Version 6.8 Mediant 3000...
  • Page 950 Mediant 3000 Parameter Description SBC Alternative Routing Reasons Table Web: SBC Alternative Routing This table parameter configures the SBC Alternative Routing Reasons Reasons table. The format of the ini file table parameter is as EMS: Alternative Routing follows: Reasons [ SBCAlternativeRoutingReasons ]...

  • Page 951: Standalone Survivability Parameters

    Defines the local TCP port used to send/receive SIP messages EMS: Local SIP TCP Port for the SAS application. The SIP entities in the local network [SASLocalSIPTCPPort] need to send the registration requests to this port. When Version 6.8 Mediant 3000...
  • Page 952 Mediant 3000 Parameter Description forwarding the requests to the proxy ('Normal Mode'), this port serves as the source port. The valid range is 1 to 65,534. The default is 5080. Web: SAS Local SIP TLS Port Defines the local TLS port used to send/receive SIP messages EMS: Local SIP TLS Port for the SAS application.
  • Page 953 Defines the SIP response upon receipt of a SUBSCRIBE [SASSubscribeResponse] message when SAS is in Emergency mode. For example, if this parameter is set to "200", then SAS sends a SIP 200 OK in response to a SUBSCRIBE message, when in Emergency mode. Version 6.8 Mediant 3000...
  • Page 954 Mediant 3000 Parameter Description The valid value is 200 to 699. The default is 489. Web: Enable ENUM Enables SAS to perform ENUM (E.164 number to URI mapping) [SASEnableENUM] queries when receiving INVITE messages in SAS emergency mode.  [0] Disable (default) ...
  • Page 955 SAS routing rules. The format of the ini file table parameter is as follows: [IP2IPRouting] FORMAT IP2IPRouting_Index = IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions; [\IP2IPRouting] For example: IP2IPRouting 1 = -1, *, *, *, *, 0, -1, -1, , 0, -1, 0; Version 6.8 Mediant 3000...

  • Page 956: Ip Media Parameters

    Mediant 3000 51.13 IP Media Parameters The IP media parameters are described in the table below. Table 51-69: IP Media Parameters Parameter Description Web: Number of Media Channels Defines the maximum number of DSP channels allocated for EMS: Media Channels...
  • Page 957  [12] 12 = 4.50 dB/sec  [13] 13 = 5.00 dB/sec  [14] 14 = 5.50 dB/sec  [15] 15 = 6.00 dB/sec  [16] 16 = 7.00 dB/sec  [17] 17 = 8.00 dB/sec Version 6.8 Mediant 3000...
  • Page 958 Mediant 3000 Parameter Description  [18] 18 = 9.00 dB/sec  [19] 19 = 10.00 dB/sec  [20] 20 = 11.00 dB/sec  [21] 21 = 12.00 dB/sec  [22] 22 = 13.00 dB/sec  [23] 23 = 14.00 dB/sec ...
  • Page 959 IP Profile. EMS: Time Out Defines the timeout (in msec) between receiving Connect [AMDTimeout] messages from the ISDN and sending AMD results. The valid range is 1 to 30,000. The default is 2,000 (i.e., 2 seconds). Version 6.8 Mediant 3000...
  • Page 960 Mediant 3000 Parameter Description Web/EMS: AMD Beep Detection Determines the AMD beep detection mode. This mode detects Mode the beeps played at the end of an answering machine message, [AMDBeepDetectionMode] by using the X-Detect header extension. The device sends a SIP INFO message containing the field values Type=AMD and SubType=Beep.
  • Page 961 [PDThreshold] Defines the number of consecutive patterns to trigger the pattern detection event. The valid range is 0 to 31. The default is 5. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 3000...

  • Page 962: Services

    Mediant 3000 51.14 Services 51.14.1 SIP-based Media Recording Parameters The SIP-based media recording parameters are described in the table below. Table 51-70: SIP-based Media Recording Parameters Parameter Description Web: SIP Recording Application Enables the SIP-based Media Recording feature: [EnableSIPRec] ...

  • Page 963: Radius Parameters

    Web: AAA Indications Determines the Authentication, Authorization and Accounting (AAA) EMS: Indications indications. CLI: aaa-indications  [0] None = (Default) No indications. [AAAIndications]  [3] Accounting Only = Only accounting indications are used. General RADIUS Parameters Version 6.8 Mediant 3000...
  • Page 964 Mediant 3000 Parameter Description Web: Use RADIUS for Enables RADIUS queries for Web and Telnet login authentication. Web/Telnet Login When enabled, logging into the device's Web and Telnet embedded EMS: Web Use Radius servers is done through a RADIUS server. The device communicates...

  • Page 965: Ldap Parameters

    [1] Parallel = (Default) The device queries the LDAP servers at the same time. Web: LDAP Authentication Defines the LDAP search filter attribute for searching the login Filter username in the directory's subtree for LDAP-based user Version 6.8 Mediant 3000...
  • Page 966 Mediant 3000 Parameter Description CLI: configure voip > ldap > authentication and authorization. auth-filter You can use the dollar ($) sign to represent the username. For [LDAPAuthFilter] example, if this parameter is set to "(sAMAccountName=$)" and the user logs in with the username "SueM", the LDAP query is run for sAMAccountName=SueM.
  • Page 967 [ LdapServersSearchDNs ] ldap-servers-search-dns FORMAT LdapServersSearchDNs_Index = [LdapServersSearchDNs] LdapServersSearchDNs_Base_Path, LdapServersSearchDNs_LdapConfigurationIndex, LdapServersSearchDNs_SearchDnInternalIndex; [ \LdapServersSearchDNs ] For a detailed description of this table, see 'Configuring LDAP DNs (Base Paths) per LDAP Server' on page 226. Management LDAP Groups Table Version 6.8 Mediant 3000...

  • Page 968: Least Cost Routing Parameters

    Mediant 3000 Parameter Description Web: Management LDAP Defines the users group attribute in the AD and corresponding Groups Table management access level. CLI: configure voip > ldap > [ MgmntLDAPGroups ] mgmt-ldap-groups FORMAT MgmntLDAPGroups_Index = [MgmntLDAPGroups] MgmntLDAPGroups_LdapConfigurationIndex, MgmntLDAPGroups_GroupIndex, MgmntLDAPGroups_Level, MgmntLDAPGroups_Group;...
  • Page 969 Cost Groups. EMS: Time Band [CostGroupTimebands] Provisioning > Time Band FORMAT CostGroupTimebands_TimebandIndex = [CostGroupTimebands] CostGroupTimebands_StartTime, CostGroupTimebands_EndTime, CostGroupTimebands_ConnectionCost, CostGroupTimebands_MinuteCost; [\CostGroupTimebands] Note: For a detailed description of this table, see ''Configuring Time Bands for Cost Groups'' on page 249. Version 6.8 Mediant 3000...

  • Page 970: Call Setup Rules Parameters

    Mediant 3000 51.14.4 Call Setup Rules Parameters The Call Setup Rules parameters are described in the table below. Table 51-72: Call Setup Rules Parameters Parameter Description Web: Call Setup Rules This table parameter defines Call Setup Rules that the device runs at...

  • Page 971: Sbc And Dsp Channel Capacity

    • The number of channels refers to the maximum channel capacity of the device. • For additional DSP templates, contact your AudioCodes sales representative. • To select the DSP Template that you want to use on the device, see Configuring DSP Templates on page 208.

  • Page 972: Mediant 3000

    The capacity figures listed in the table below are accurate at the time of publication of this document. However, these figures may change due to a later software update. For the latest figures, please contact your AudioCodes sales representative. •...

  • Page 973: Mediant 3000 Full Chassis

    User's Manual 52. SBC and DSP Channel Capacity 52.2.1 Mediant 3000 Full Chassis The table below lists the supported channel capacity per DSP firmware template. Table 52-2: DSP Firmware Templates DSP Template Supplementary Capabilities Number of Channels 2016 2016 1764...

  • Page 974: Mediant 3000 16 E1 / 21 T1

    Mediant 3000 52.2.2 Mediant 3000 16 E1 / 21 T1 The DSP templates for 16 E1 / 21 T1 are shown in the table below. Notes: • For each IP-to-IP transcoding call, two DSP channels are required. • For each IP-to-IP call, one DSP channel is required.

  • Page 975: Mediant 3000 With Single T3

    Number of Channels T.38 Version 3 52.2.3 Mediant 3000 with Single T3 The DSP templates for Mediant 3000 with a single T3 interface are shown in the table below. Table 52-4: DSP Firmware Templates for Mediant 3000 with Single T3...

  • Page 976: Mediant 3000 Dsp Template Mix Feature

    MS-RTA (WB) T.38 Version 3 52.2.4 Mediant 3000 DSP Template Mix Feature 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 977: Technical Specifications

    (SFP) transceiver, using 850 nm wavelength E1/T1 Up to 63 E1 and 84 T1 interfaces. Note: Applicable only to Mediant 3000 with TP-8410 blade. 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.
  • Page 978 Mediant 3000 Function Specification Voice and Tone  RTP/RTCP per RFC 3550/3551 VoIP Standards Compliance  DTMF over RTP per RFC 4733 Voice Compression G.711 PCM at 64 kbps µ-law/A-law; G.722; AMR; AMR-WB (G.722.2); EVRC; EVRC-B (4GV); G.723.1 MP-MLQ at 5.3 or 6.3 kbps; G.726 at (Independent dynamic 32 kbps ADPCM;...
  • Page 979 LAN status, Swap ready Connectors Rear Panel 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. Version 6.8 Mediant 3000...
  • Page 980 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). Note: Applicable only to Mediant 3000 with TP-6310. T3 Interface Up to three SMB Tx/Rx connector pairs - receives RG-179/U coaxial cables terminated with 75-ohm male SMB connectors (not supplied) Note: Applicable only to Mediant 3000 with TP-6310.
  • Page 981 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 Version 6.8...
  • Page 982 Mediant 3000 Function Specification  UL 60950-1 Safety and EMC Standards  FCC part 15 Class A  CE mark (EN 55022 Class A, EN 60950-1, EN 55024, EN 300 386) Environmental NEBS Level 3, GR-63-Core, GR-1089-Core, Type 1 & 3, ETS 300 019...
  • Page 983 User's Manual 53. Technical Specifications This page is intentionally left blank. Version 6.8 Mediant 3000...
  • Page 984 Website: https://www.audiocodes.com/ ©2017 AudioCodes Ltd. All rights reserved. AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, User Management Pack, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One Voice and CloudBond are trademarks or registered trademarks of AudioCodes Limited.

Table of Contents