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

Media gateway & enterprise session border controller (e-sbc)
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
985
986
987
988
989
990
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual
User's Manual
Mediant 3000
Media Gateway & Enterprise Session Border
Controller (E-SBC)
Version 7.0

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

Subscribe to Our Youtube Channel

Related Manuals for AudioCodes Mediant 3000

Summary of Contents for AudioCodes Mediant 3000

  • Page 1 User's Manual Mediant 3000 Media Gateway & Enterprise Session Border Controller (E-SBC) Version 7.0...

  • Page 3: Table Of Contents

    Configuring VoIP LAN Interface for OAMP ............. 47 Web Interface ....................... 47 CLI ........................49 BootP/TFTP Server ....................51 Configuring an IP Address for Mediant 3000 HA ..........53 Management Tools ....................57 Introduction ....................... 59 Web-Based Management .................. 61 Getting Acquainted with the Web Interface ............61 7.1.1...
  • Page 4 Mediant 3000 Configuring Web User Accounts ................82 7.3.1 Basic User Accounts Configuration .................83 7.3.2 Advanced User Accounts Configuration ..............85 Displaying Login Information upon Login .............. 89 Configuring Web Security Settings ............... 90 7.5.1 Configuring Secured (HTTPS) Web ................90 7.5.2 Configuring Web Session and Access Settings ............90...
  • Page 5 13.9.2 Remote UA behind NAT ..................169 13.9.2.1 SIP Signaling Messages ................169 13.9.2.2 Media (RTP/RTCP/T.38) ................169 13.10 Robust Receipt of Media Streams by Media Latching ......... 172 13.11 Multiple Routers Support ..................172 13.12 IP Multicasting ....................172 Version 7.0 Mediant 3000...
  • Page 6 Mediant 3000 14 Security ......................173 14.1 Configuring Firewall Settings ................173 14.2 Configuring General Security Settings ..............177 14.3 Intrusion Detection System ................. 178 14.3.1 Enabling IDS ......................179 14.3.2 Configuring IDS Policies ..................179 14.3.3 Assigning IDS Policies ...................183 14.3.4 Viewing IDS Alarms ....................184 14.4 IPSec and Internet Key Exchange ..............
  • Page 7 16.7.2.1 Gathering Location Information of Lync Clients for 911 Calls ....293 16.7.2.2 Adding ELINs to the Location Information Server ........295 16.7.2.3 Passing Location Information to the PSTN Emergency Provider ..296 16.7.3 AudioCodes ELIN Device for Lync Server E9-1-1 Calls to PSTN ......297 Version 7.0 Mediant 3000...
  • Page 8 16.7.3.3 PSAP Callback to Lync Clients for Dropped E9-1-1 Calls .....300 16.7.3.4 Selecting ELIN for Multiple Calls within Same ERL .......301 16.7.3.5 Location Based Emergency Routing ............302 16.7.4 Configuring AudioCodes ELIN Device ..............302 16.7.4.1 Enabling the E9-1-1 Feature ..............302 16.7.4.2 Configuring the E9-1-1 Callback Timeout ..........302 16.7.4.3 Configuring the SIP Release Cause Code for Failed E9-1-1 Calls ..303...
  • Page 9 24.4 SIP Calling Name Manipulations ................ 476 24.5 Configuring Redirect Number IP to Tel ............... 479 24.6 Manipulating Redirected and Diverted Numbers for Call Diversion ..... 483 24.7 Mapping NPI/TON to SIP Phone-Context ............484 24.8 Configuring Release Cause Mapping ..............486 Version 7.0 Mediant 3000...
  • Page 10 Mediant 3000 24.8.1 SIP-to-ISDN Release Cause Mapping ..............486 24.8.1.1 Configuring SIP-to-ISDN Release Cause Mapping .......486 24.8.1.2 Fixed Mapping of SIP Response to ISDN Release Reason ....487 24.8.2 ISDN-to-SIP Release Cause Mapping ..............488 24.8.2.1 Configuring ISDN-to-SIP Release Cause Mapping .......488 24.8.2.2 Fixed Mapping of ISDN Release Reason to SIP Response ....489 24.8.3 Configuring ISDN-to-ISDN Release Cause Mapping ..........491...
  • Page 11 28.9.12 Interworking SIP Via Headers ................578 28.9.13 Interworking SIP User-Agent Headers ..............578 28.9.14 Interworking SIP Record-Route Headers ..............578 28.9.15 Interworking SIP To-Header Tags in Multiple SDP Answers ........579 28.9.16 Interworking In-dialog SIP Contact and Record-Route Headers ......579 Version 7.0 Mediant 3000...
  • Page 12 Mediant 3000 29 Enabling the SBC Application ................ 581 30 Configuring General SBC Settings ..............583 30.1 Interworking Dialog Information in SIP NOTIFY Messages ......... 583 31 Configuring Admission Control ..............587 32 Configuring Coder Groups ................591 32.1 Configuring Allowed Audio Coder Groups ............591 32.2 Configuring Allowed Video Coder Groups ............
  • Page 13 Contents 37.2 Configuration Stages ..................656 37.3 Blade Failure Detection ..................658 38 Network Interfaces and Mediant 3000 High Availability ....... 659 38.1 Mediant 3000 Internal Link ................. 659 38.2 Example of Multiple Interface Configuration ............659 39 Physical Network Separation Mode ............... 661 39.1 Configuring Physical Network Separation ............
  • Page 14 46.1.4 HTTP-based Provisioning ..................714 46.1.4.1 Loading Files Securely by Disabling TFTP ..........715 46.1.5 FTP- or NFS-based Provisioning ................715 46.1.6 Provisioning using AudioCodes EMS ..............715 46.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 716 46.2.1 Files Provisioned by Automatic Update ..............716 46.2.2 File Location for Automatic Update ...............716...
  • Page 15 53.2.1.2 Unique Device Identification in Syslog Messages .........798 53.2.1.3 Maintaining Same Syslog SID/BID over Multiple Devices .....798 53.2.1.4 Identifying AudioCodes Syslog Messages using Facility Levels....798 53.2.1.5 Syslog Fields for Answering Machine Detection (AMD) ......799 53.2.1.6 SNMP Alarms in Syslog Messages ............799 53.2.2 Configuring Web User Activities to Report to Syslog ..........800...
  • Page 16 Mediant 3000 54 Self-Testing ...................... 807 55 Creating Core Dump and Debug Files upon Device Crash ......809 56 Testing SIP Signaling Calls ................811 56.1 Configuring Test Call Endpoints ................. 811 56.2 Starting and Stopping Test Calls ................ 816 56.3 Viewing Test Call Statistics .................
  • Page 17 58.14.1 SIP-based Media Recording Parameters ............1052 58.14.2 RADIUS and LDAP Parameters ................1053 58.14.2.1 General Parameters ................1053 58.14.2.2 RADIUS Parameters ................1054 58.14.2.3 LDAP Parameters ................1056 58.14.3 Least Cost Routing Parameters ................1058 58.14.4 Call Setup Rules Parameters ................1059 Version 7.0 Mediant 3000...
  • Page 18 59.1 Signaling-Media Sessions & User Registrations ..........1061 59.2 Mediant 3000....................1062 59.2.1 Mediant 3000 Full Chassis ..................1063 59.2.2 Mediant 3000 16 E1 / 21 T1 ................1064 59.2.3 Mediant 3000 with Single T3 ................1065 59.2.4 Mediant 3000 DSP Template Mix Feature ............1066 60 Technical Specifications ................

  • Page 19: Weee Eu Directive

    Notices Notice This document describes AudioCodes Mediant 3000 SIP Gateway & Enterprise Session Border Controller (E-SBC) housed with TP-8410 SIP blade(s) or TP-6310 SIP blade(s). Information contained in this document is believed to be accurate and reliable at the time of printing.

  • Page 20: Related Documentation

    Note: Throughout this manual, unless otherwise specified, the following naming conventions are used: • The term device refers to your AudioCodes product. • The term blade refers to the TP-8410 blade or TP-6310 blade. Note: Before configuring the device, ensure that it is installed correctly as instructed in the Hardware Installation Manual.
  • Page 21 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 22 Mediant 3000 Document Revision Record LTRT Description 89726 Initial document release for Version 7.0. 89728 New parameters: PhysicalSeparationConfiguration; IPGroup_UUIFormat; PM_EnableThresholdAlarms; PhysicalSeparationConfiguration; GWCDRFormat; NetworkNodeId. New features: locking/unlocking Trunk Groups (Locking and Unlocking Trunk Groups); Gateway CDR format customization. Updated parameter descriptions: Session Limit; Session Timeout;...
  • Page 23 Configuring SBC IP-to-IP Routing; Network Topology Types and Rx/Tx Ethernet Port Group Settings; Initial HA Configuration; Configuring RTCP XR; Configuring CDR Reporting; Customizing CDRs for SBC Calls; Storing CDRs on the Device; Configuring RADIUS Accounting; Interworking ISDN Overlap Dialing with SIP According to RFC 3578 Version 7.0 Mediant 3000...
  • Page 24 Mediant 3000 Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads. User's Manual Document #: LTRT-89730...

  • Page 25: Introduction

    Product 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 26 Mediant 3000 Figure 1-1: Mediant 3000 Typical Application The device's chassis provides a compact, rugged 19-inch rack mount unit, 2U high (3.5" or 89 mm), designed to meet NEBS level-3 requirements. The device is a four-slot chassis (four front and rear slots) that houses VoIP communication blades, synchronization and alarm blades, and rear transition modules (RTM).

  • Page 27: Functional Block Diagrams

    For more details on the HA system, see ''HA Overview'' on page 655. 1.1.1 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: Figure 1-2: Mediant 3000/TP-6310 Functional Block Diagram Version 7.0...

  • Page 28: Sip Overview

    Mediant 3000 Figure 1-3: Mediant 3000/TP-8410 Functional Block Diagram 1.1.2 SIP Overview Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol used on the E-SBC and gateway for creating, modifying, and terminating sessions with one or more participants. These sessions can include Internet telephone calls, media announcements, and conferences.
  • Page 29 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 Content-Type: application/sdp Content-Length: 208 o=AudiocodesGW 18132 74003 IN IP4 10.8.201.108 s=Phone-Call c=IN IP4 10.8.201.108...
  • Page 30 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 31 User's Manual 1. Introduction 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.  F6 BYE - 10.8.201.108 to 10.8.201.10: BYE sip:2000@10.8.201.161;user=phone SIP/2.0...

  • Page 32: Typographical Conventions

    Mediant 3000 Typographical Conventions This document uses the following typographical conventions to convey information: Table 1-1: Typographical Conventions Convention Description Example  Buttons in the Web interface. Boldface font Click the Add button.  Optional parameter values in the Web interface.

  • Page 33: Getting Familiar With Configuration Concepts And Terminology

    The Media Realm can be associated with the SIP entity, by assigning the Media Realm to the IP Group of the SIP entity, or by assigning it to the SIP Interface associated with the SIP entity. Version 7.0 Mediant 3000...
  • Page 34 Mediant 3000 Configuration Terms Description The SRD is a logical representation of your entire SIP-based VoIP network (Layer 5) containing groups of SIP users and servers. The SRD is in effect, the foundation of your configuration to which all other previously mentioned configuration entities are associated.
  • Page 35 "served" IP Group. Authentication (SIP 401) is typically relevant for INVITE messages forwarded by the device to a "serving" IP Group. Registration is for REGISTER messages, which are initiated by the device on behalf of the "serving" SIP entity. Version 7.0 Mediant 3000...
  • Page 36 Mediant 3000 The associations between the configuration entities are summarized in the following figure: Figure 1-5: Association of Configuration Entities The main configuration entities and their involvement in the call processing is summarized in following figure. The figure is used only as an example to provide basic understanding of the configuration terminology.

  • Page 37: Gateway Application

    The Media Realm can be associated with the SIP entity, by assigning the Media Realm to the IP Group of the SIP entity, or by assigning it to the SIP Interface associated with the SIP entity. Version 7.0 Mediant 3000...
  • Page 38 Mediant 3000 Configuration Terms Description SRDs The SRD is a logical representation of your entire VoIP network. The SRD is in effect, the foundation of your configuration to which all other previously mentioned configuration entities are associated. Typically, only a single SRD is required and this is the recommended configuration topology.
  • Page 39 The figure is used only as an example to provide basic understanding of the configuration terminology. Depending on configuration and network topology, the call process may include additional stages or a different order of stages. Figure 1-7: Gateway Configuration Terminology for Call Processing Version 7.0 Mediant 3000...
  • Page 40 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 41: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 43: 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 7.0 Mediant 3000...
  • Page 44 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 45: 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 Version 7.0 Mediant 3000...
  • Page 46 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 47: Configuring Voip Lan Interface For Oamp

    Bootstrap Protocol (BootP) - see BootP/TFTP Server on page 51 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 53. 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 48 Mediant 3000 Figure 4-2: LAN Connection to PC for Initial Connectivity for RTM-6310 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 49: Cli

    To configure the OAMP IP address in the 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 Version 7.0 Mediant 3000...
  • Page 50 Mediant 3000 Figure 4-5: Serial Connection with PC for CLI Communication for TP-8410 Establish serial communication (e.g., telnet) with the device using a terminal emulator program such as HyperTerminal, with the following communication port settings: • Baud Rate: 115,200 bps •...

  • Page 51: 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 52 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-89730...

  • Page 53: Configuring An Ip Address For Mediant 3000 Ha

    (HA) device. This can be done using BootP and the Web interface. 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 54 Mediant 3000 Add a BootP client for each blade with a new private IP address, as shown in the example below. Figure 5-1: Clients for each Blade Added in BootP Utility Power down the chassis. Power up the chassis and wait about 20-30 seconds, and then power down and power up the chassis once again within 15 seconds;...
  • Page 55 User's Manual 5. Configuring an IP Address for Mediant 3000 HA Note: If you want to change the global IP address at a later stage: • If the current and new global IP addresses are in different subnets, then it’s recommended to also define the private addresses of the blades in the same subnet as the new global IP address.
  • Page 56 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 57: Management Tools

    Part II Management Tools...

  • Page 59: 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 831. Version 7.0 Mediant 3000...
  • Page 60 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 61: Web-Based Management

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

  • Page 62: Accessing The Web Interface

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

  • Page 63: Areas Of The Gui

    Figure 7-2: Main Areas of the Web Interface GUI Table 7-1: Description of the Web GUI Areas Item # Description AudioCodes company logo. Product name. Toolbar, providing frequently required command buttons. For more information, see ''Toolbar Description'' on page 64.

  • Page 64: Toolbar Description

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

  • Page 65: Navigation Tree

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

  • Page 66: Showing / Hiding The Navigation Pane

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

  • Page 67: Working With Configuration

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

  • Page 69: Modifying And Saving Parameters

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

  • Page 70: Working With Tables

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

  • Page 71: Table Toolbar Description

    The button is available only if the table contains more than one row and is sorted according to 'Index' column; otherwise, the button is grayed out. For sorting tables, see ''Sorting Tables by Column'' on page 73.  The button appears only in certain tables. Version 7.0 Mediant 3000...

  • Page 72: Toggling Display Mode Of Table Dialog Boxes

    Mediant 3000 Button Name Moves a selected row one index up. The index number of the row changes according to its new position in the table. The row that previously occupied the index row and all rows below it are moved one index down in the table.

  • Page 73: Searching Table Entries

    Index column in ascending order (e.g., 1, 2, and 3), you can sort the rows by Index column in descending order (e.g., 3, 2, and 1). By default, most tables are sorted by Index column in ascending order. Version 7.0 Mediant 3000...

  • Page 74: Searching For Configuration Parameters

    Mediant 3000  To sort table rows by column: Click the heading name of the column that you want to sort the table rows by; the up- down arrows appear alongside the heading name and the up button is bolded (see...
  • Page 75 Figure 7-14: Searched Result Screen Table 7-6: 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 7.0 Mediant 3000...

  • Page 76: Creating A Login Welcome Message

    Mediant 3000 7.1.9 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-15: 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 77: 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 7.0 Mediant 3000...

  • Page 78: Logging Off The Web Interface

    Mediant 3000 7.1.11 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-17: Log Off Confirmation Box Click OK;...

  • Page 79: Viewing The Home Page

    Protocol Type: Signaling protocol currently used by the device (i.e. SIP)  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 Version 7.0 Mediant 3000...

  • Page 80: Mediant

    Mediant 3000 To perform these operations, see ''Basic Maintenance'' on page 669.  High Availability: Status of the device's HA mode (see Viewing HA Status on Home Page on page 665 HA Status on the Home Page)  Active Board Slot Number: Slot number with the active blade if the device is in HA mode;...
  • Page 81 (red): No power received by blade Slot status of installed blade in the chassis (SWAP Ready icon). 12 & 13 Power supply units (PS/DC/3K modules) icons (Power Supply Number 1 & 2 icons):  (green): Normal functioning  (red): Power failure Version 7.0 Mediant 3000...

  • Page 82: Configuring Web User Accounts

    Mediant 3000 Configuring Web User Accounts Web user accounts define users for the Web interface and CLI. User accounts permit login access to these interfaces as well as different levels of read and write privileges. Thus, user accounts prevent unauthorized access to these interfaces, permitting access only to users with correct credentials (i.e., username and password).

  • Page 83: Basic User Accounts Configuration

    The username and password can be a string of up to 19 characters and are case- sensitive. • When only the basic user accounts are being used, up to two users can be concurrently logged in to the Web interface, and they can be the same user. Version 7.0 Mediant 3000...
  • Page 84 Mediant 3000  To configure the two pre-configured Web user accounts: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). If you are logged in as Security Administrator, both Web user accounts are displayed (as shown below). If you are logged in with the second user account, only the details of this user account are displayed.

  • Page 85: Advanced User Accounts Configuration

    Subsequent access: Configuration tab > System menu > Web User Accounts. The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"): Figure 7-19: Web Users Table Page Version 7.0 Mediant 3000...
  • Page 86 Mediant 3000 Click Add; the following dialog box is displayed: Figure 7-20: Web Users Table - Add Record Dialog Box Configure a Web user according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.
  • Page 87 The valid value is 0 to 100000. A value of 0 means no timeout. The default value is according to the settings of the WebSessionTimeout global parameter (see ''Configuring Web Session and Access Settings'' on page 90). Version 7.0 Mediant 3000...
  • Page 88 Mediant 3000 Parameter Description Block Duration Defines the duration (in seconds) for which the user is blocked when the user exceeds a user-defined number of failed login attempts. This is configured by the 'Deny Access On Fail Count' parameter (see ''Configuring Web Session and Access Settings'' on page 90).

  • Page 89: Displaying Login Information Upon Login

    Management > Web Security Settings). From the 'Display Login Information' drop-down list, select Yes. Click Submit. Once enabled, the Login Information window is displayed upon a successful login, as shown in the example below: Figure 7-21: Login Information Window Version 7.0 Mediant 3000...

  • Page 90: Configuring Web Security Settings

    Mediant 3000 Configuring Web Security Settings This section describes how to secure Web-based management. 7.5.1 Configuring Secured (HTTPS) Web By default, the device allows remote management (client) through HTTP and HTTPS. However, you can enforce secure Web access communication by configuring the device to accept only HTTPS.
  • Page 91 'Deny Access On Fail Count': Number of failed login attempts after which the user is prevented access to the device for a user-defined duration (previous step). Click Submit. For a detailed description of the above parameters, see ''Web Parameters'' on page 831. Version 7.0 Mediant 3000...

  • Page 92: 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 93: Configuring Web And Telnet Access List

    IP addresses that you want to delete, and then click Delete Selected Addresses; the IP addresses are removed from the table and these IP addresses can no longer access the Web and Telnet interfaces. Version 7.0 Mediant 3000...
  • Page 94 Mediant 3000 To save the changes to flash memory, see ''Saving Configuration'' on page 672. Notes: • The first authorized IP address in the list must be your PC's (terminal) IP address; otherwise, access from your PC is denied. •...

  • Page 95: Cli-Based Management

    In the 'Telnet Server TCP Port' field, enter the port number for the embedded Telnet server. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. For a detailed description of the Telnet parameters, see ''Telnet Parameters'' on page 834. Version 7.0 Mediant 3000...

  • Page 96: 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 97 '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 7.0 Mediant 3000...

  • Page 98: Configuring Maximum Telnet/Ssh Sessions

    Mediant 3000 Configuring Maximum Telnet/SSH Sessions You can configure the maximum number of concurrent Telnet/SSH sessions (up to five) permitted on the device. Note: Before changing the setting, make sure that not more than this number of sessions are currently active; otherwise, the new setting will not take effect.

  • Page 99: Command Shell

    Instead of typing the full name of the subdirectory, you can simply type its abbreviated format. The abbreviated format is shown in upper case (i.e., capital letters). For example, for the MGmt subdirectory, you can simply type the following: />MG Version 7.0 Mediant 3000...

  • Page 100: Status Commands

    Mediant 3000 If you know the full path to a command inside one of the subdirectories, the short format can be used to run it directly. For example, to run the PERFormance command in the MGmt subdirectory, type the following: />MG/PERF...
  • Page 101 Peak KByte/s TX in this interval: 18 Peak KByte/s RX in this interval: 4 Discarded packets: 186 DHCP requests sent: 0 IPSec Security Associations: 0 />/mg/perf reset Done. />sh ip perf Networking Statistics (statistics for 2 seconds): Version 7.0 Mediant 3000...

  • Page 102: Ping Command

    Mediant 3000 IP KBytes TX: 2 IP KBytes RX: 4 IP KBytes TX per second: 0 IP KBytes RX per second: 1 IP Packets TX: 24 IP Packets RX: 71 IP Packets TX per second: 3 IP Packets RX per second: 12...

  • Page 103: Test Call (Tc) Commands

    Usage: TC set dest <number> TC set src <number> TC set cid <display string> TC set DTMFs <dtmf string> TC display TC connect [dest-number] [src number] [CID] [time] /SIP>tc display Test Call configuration Dest number: 402 Version 7.0 Mediant 3000...

  • Page 104: Management Commands

    Mediant 3000 number: 700 Cid display: TESTING DTMFs String 112233 Time After DTMF are sent: 20 sec /SIP>tc connect Start Test call. Receive ALERT Event Receive Connect Wait more 20 seconds before disconnecting Receive SS_TIMER_EV Event Send Release To Call...

  • Page 105: Pstn Commands

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

  • Page 106: Ldap Commands

    Mediant 3000 8.4.8 LDAP Commands The commands under the IPNetworking\OpenLdap directory allow you to perform various Lightweight Directory Access Protocol (LDAP) actions. Table 8-9: LDAP Commands Sub-Command Arguments Description LdapSTatus Displays the LDAP connection status. LdapSearch <search key> <attribute1> Searches an LDAP server. The parameters [<attribute 2>...

  • Page 107: 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 108: Configuring Snmp Community Strings

    Mediant 3000 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. The SNMP community string determines the access privileges (read-only or read-write) of SNMP clients to the device's SNMP.
  • Page 109 The valid value is a string of up to 19 characters that can include only the following: [SNMPTrapCommunityString]  Upper- and lower-case letters (a to z, and A to Z)  Numbers (0 to 9)  Hyphen (-)  Underline (_) For example, "Trap-comm_string1". The default is "trapuser". Version 7.0 Mediant 3000...

  • Page 110: Configuring Snmp Trap Destinations

    Mediant 3000 Configuring SNMP Trap Destinations The SNMP Trap Destinations table lets you to configure up to five SNMP trap managers. You can associate a trap destination with SNMPv2 users and specific SNMPv3 users. Associating a trap destination with SNMPv3 users sends encrypted and authenticated traps to the SNMPv3 destination.

  • Page 111: Configuring Snmp Trusted Managers

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

  • Page 112: Configuring Snmp V3 Users

    Mediant 3000 Configuring SNMP V3 Users The SNMPv3 Users table lets you configure up to 10 SNMP v3 users for authentication and privacy. The following procedure describes how to configure SNMP v3 users through the Web interface. You can also configure it through ini file (SNMPUsers).
  • Page 113 Keys are always persisted as long hex strings and keys are localized. [SNMPUsers_PrivKey] Group The group with which the SNMP v3 user is associated.  [0] Read-Only (default)  [1] Read-Write [SNMPUsers_Group]  [2] Trap Note: All groups can be used to send traps. Version 7.0 Mediant 3000...
  • Page 114 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 115: Ini File-Based Management

    (dynamic tables of other applications are empty, but static tables are not). The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME]. Version 7.0 Mediant 3000...
  • Page 116 Mediant 3000  Format line: Specifies the columns of the table (by their string names) that are to be configured. • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed.

  • Page 117: 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 7.0 Mediant 3000...

  • Page 118: Configuring An Ini File

    Mediant 3000 10.2 Configuring an ini File There are different methods that you can use for configuring the ini file before you load it to the device.  Modifying the device's current ini file. This method is recommended if you mainly need to change the settings of parameters that you have previously configured.

  • Page 119: Loading An Ini File To The Device

    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 120: Configuring Password Display In Ini File

    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 121: General System Settings

    Part III General System Settings...

  • Page 123: Configuring Ssl/Tls Certificates

    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:  Incoming calls: Version 7.0 Mediant 3000...
  • Page 124 Mediant 3000 Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for TLS ('Transport Type' parameter is set to TLS), the TLS Context assigned to the Proxy Set is used.
  • Page 125 [5] TLSv1.0 and TLSv1.2 = Only TLS 1.0 and TLS 1.2.  [6] TLSv1.1 and TLSv1.2 = Only TLS 1.1 and TLS 1.2.  [7] TLSv1.0 TLSv1.1 and TLSv1.2 = Only TLS 1.0, TLS 1.1 and TLS 1.2 (excludes SSL 3.0). Version 7.0 Mediant 3000...
  • Page 126 Mediant 3000 Parameter Description Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format). For valid values, refer to URL [TLSContexts_Server http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". CipherString] For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).

  • Page 127: 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 7.0 Mediant 3000...
  • Page 128 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 129: Assigning Externally Created Private Keys To Tls Contexts

    After the files successfully load to the device, save the configuration with a device reset. Open the TLS Contexts page again, select the TLS Context index row, and then verify that under the Certificate Information group, the 'Private key' field displays "OK"; otherwise, consult your security administrator. Version 7.0 Mediant 3000...

  • Page 130: Generating Private Keys For Tls Contexts

    Mediant 3000 11.4 Generating Private Keys for TLS Contexts The device can generate the private key for a TLS Context, as described in the following procedure. The private key can be generated for CSR or self-signed certificates.  To generate a new private key for a TLS Context: Open the TLS Contexts page (Configuration tab >...

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

    Figure 11-7: Generate new private key and self-signed certificate Group Click Generate Self-Signed Certificate; a message appears (after a few seconds) displaying the new subject name. Save the configuration with a device reset for the new certificate to take effect. Version 7.0 Mediant 3000...

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

    Mediant 3000 11.6 Importing Certificates and Certificate Chain into Trusted Certificate Store The device provides its own Trusted Root Certificate Store. This lets you manage certificate trust. You can add up to 20 certificates to the store per TLS Context (but this may be less depending on certificate file size).
  • Page 133 Save certificates to a file on your PC: Select the required certificate, click Export, and then in the Export Certificate dialog box, browse to the folder on your PC where you want to save the file and click Export. Version 7.0 Mediant 3000...

  • Page 134: Configuring Mutual Tls Authentication

    Mediant 3000 11.7 Configuring Mutual TLS Authentication This section describes how to configure mutual (two-way) TLS authentication. 11.7.1 TLS for SIP Clients When Secure SIP (SIPS) is implemented using TLS, it is sometimes required to use two- way (mutual) authentication between the device and a SIP user agent (client). When the device acts as the TLS server in a specific connection, the device demands the authentication of the SIP client’s certificate.
  • Page 135 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 123). Version 7.0 Mediant 3000...

  • Page 136: Configuring Tls Server Certificate Expiry Check

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

  • Page 137: Date And Time

    Open the Application Settings page (Configuration tab > System menu > Application Settings), and then scroll down to the 'NTP Settings' group: Figure 12-2: NTP Authentication Parameters on Application Settings Page Version 7.0 Mediant 3000...

  • Page 138: Configuring Date And Time Manually

    Mediant 3000 Configure NTP message authentication: • In the 'NTP Authentication Key Identifier' field, configure the NTP authentication key identifier. • In the 'NTP Authentication Secret Key' field, configure the secret authentication key shared between the device and the NTP server.

  • Page 139: Configuring The Time Zone

    Date), and then scroll down to the 'Time Zone' group: Figure 12-5: Configuring DST From the 'Daylight Saving Time' (DayLightSavingTimeEnable) drop-down list, select Enable From the 'DST Mode' drop-down list, select the range type for configuring the start and end dates for DST: Version 7.0 Mediant 3000...
  • Page 140 Mediant 3000 • Day of year: The range is configured by exact date (day number of month), for example, from March 30 to October 30. If 'DST Mode' is set to Day of year, in the 'Start Time' (DayLightSavingTimeStart) and 'End Time' (DayLightSavingTimeEnd) drop-down lists, configure the period for which DST is relevant.

  • Page 141: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 143: 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 7.0 Mediant 3000...

  • Page 144: 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 145: 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 Version 7.0 Mediant 3000...
  • Page 146 Mediant 3000 of Service (QoS), see ''Configuring the QoS Settings'' on page 157.  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 147 Defines the IPv4/IPv6 address, in dotted-decimal notation. [InterfaceTable_IPAddress] Prefix Length Defines the prefix length of the related IP address. This is a Classless Inter-Domain Routing (CIDR)-style representation of a dotted-decimal subnet notation. The CIDR-style representation uses a suffix indicating [InterfaceTable_PrefixLeng Version 7.0 Mediant 3000...
  • Page 148 Mediant 3000 Parameter Description the number of bits which are set in the dotted-decimal format. For example, 192.168.0.0/16 is synonymous with 192.168.0.0 and subnet 255.255.0.0. This CIDR lists the number of ‘1’ bits in the subnet mask (i.e., replaces the standard dotted-decimal representation of the subnet mask for IPv4 interfaces).
  • Page 149 [0] Disable (default).  [1] Enable. Notes:  The parameter is applicable only to Mediant 3000 with TP-8410.  For the 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 150: Assigning Ntp Services To Application Types

    Mediant 3000 Parameter Description  For the parameter to take effect, a device reset is required.  To enable the Physical Network Separation feature, use the EnableNetworkPhysicalSeparation parameter. 13.3.1 Assigning NTP Services to Application Types You can associate the Network Time Protocol (NTP) application with the OAMP or Control application type.

  • Page 151: Networking Configuration Examples

    Table 13-4: Example of VoIP Interfaces per Application Type in Interface Table Application Interface Prefix Default VLAN Interface Index IP Address Type Mode Length Gateway Name OAMP IPv4 192.168.85.14 0.0.0.0 ManagementI 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 Version 7.0 Mediant 3000...

  • Page 152: Voip Interfaces For Combined Application Types

    Mediant 3000 VLANs are required and the Native VLAN ID is the same VLAN ID as the Management interface (configured for Index 0): • '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:...

  • Page 153: Voip Interfaces With Multiple Default Gateways

    A separate Static Route table lets you configure static routing rules. Configuring the following static routing rules enables OAMP applications to access peers on subnet 17.17.0.0 through the gateway 192.168.0.1. Table 13-9: Separate Static Route Table Example Interface Destination Prefix Length Gateway Name 17.17.0.0 192.168.0.1 Mgmt Version 7.0 Mediant 3000...

  • Page 154: Configuring Static Ip Routes

    Mediant 3000 13.4 Configuring Static IP Routes The Static Route table lets you configure up to 30 static IP routing rules. Using static routes lets you communicate with LAN networks that are not located behind the Default Gateway specified for the IP network interface, configured in the Interface table, from which the packets are sent.

  • Page 155: Configuration Example Of Static Ip Routes

    10.1.1.x to this gateway and therefore, to the network in which the softswitch resides.  The static route in the Static Route table is associated with the IP network interface in the Interface table, using the 'Interface Name' fields. Version 7.0 Mediant 3000...

  • Page 156: Troubleshooting The Routing Table

    Mediant 3000  The static route's Gateway address in the Static Route table is in the same subnet as the IP address of the IP network interfacein the Interface table. Figure 13-3: Example of using a Static Route 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.

  • Page 157: Configuring Quality Of Service

    Management Bronze ICMP Management Determined by the initiator of the request ARP listener Determined by the initiator of the Network request SNMP Traps Management Bronze DNS client Varies according to DNS settings: Depends on traffic type: Version 7.0 Mediant 3000...
  • Page 158 Mediant 3000 Application Traffic / Network Types Class-of-Service (Priority)   OAMP Control: Premium Control   Control Management: Bronze Varies according to the interface Depends on traffic type: type associated with NTP (see  Control: Premium control ''Assigning NTP Services to ...

  • Page 159: Configuring Icmp Messages

    To enable or disable sending and receipt of ICMP Redirect messages, use the 'Send and Received ICMP Redirect Messages' parameter. To enable or disable the sending of ICMP Destination Unreachable messages, use the 'Send ICMP Unreachable Messages' parameter. Click Submit. Version 7.0 Mediant 3000...

  • Page 160: Dns

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

  • Page 161: Configuring The Internal Srv Table

    The following procedure describes how to configure the Internal SRV table through the Web interface. You can also configure it through ini file (SRV2IP).  To configure an SRV rule: Open the Internal SRV table (Configuration tab > VoIP menu > Network > DNS > Internal SRV Table). Version 7.0 Mediant 3000...
  • Page 162 Mediant 3000 Click Add; the following dialog box appears: Figure 13-6: Internal SRV Table - Add Row Dialog Box Configure an SRV rule according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.

  • Page 163: Configuring Nfs Settings

    Click Add, and then save ("burn") your settings to flash memory. The remote NFS file system is immediately applied, which can be verified by the appearance of the "NFS mount was successful" message in the Syslog server. Version 7.0 Mediant 3000...
  • Page 164 Mediant 3000 Notes: • To avoid terminating current calls, do not delete or edit a row while the device is currently accessing files on that remote NFS file system. • The combination of 'Host Or IP' and 'Root Path' must be unique for each row in the table.

  • Page 165: Network Address Translation Support

    If NAT is not configured by any of the above-mentioned methods, the device sends the packet according to its IP address configured in the Interface table. Note: The priority list above is applicable only to the Gateway calls. Version 7.0 Mediant 3000...

  • Page 166: Configuring Stun

    Mediant 3000 The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 13-8: Device behind NAT and NAT Issues 13.9.1.1 Configuring STUN Simple Traversal of UDP through NATs (STUN), based on RFC 3489 is a client / server protocol that solves most of the NAT traversal problems.

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

    The NAT Translation table lets you configure up to 32 network address translation (NAT) rules for translating source IP addresses per VoIP interface (SIP control and RTP media traffic) into NAT IP addresses (global - public), when the device is located behind NAT. The Version 7.0 Mediant 3000...
  • Page 168 Mediant 3000 device's NAT traversal mechanism replaces the source IP address of SIP messages sent from a specified VoIP interface to a public IP address. This allows, for example, the separation of VoIP traffic between different ITSP’s, and topology hiding of internal IP addresses from the “public”...

  • Page 169: Remote Ua Behind Nat

    When a remote UA initiates a call and is not located behind a NAT server, the device sends the RTP (or RTCP, T.38) packets to the remote UA using the IP address:port (UDP) indicated in the SDP body of the SIP message received from the UA. However, if the UA is Version 7.0 Mediant 3000...
  • Page 170 Mediant 3000 located behind NAT, the device sends the RTP with the IP address of the UA (i.e., private IP address) as the destination, instead of that of the NAT server. Thus, the RTP will not reach the UA. To resolve this NAT traversal problem, the device offers the following features: ...
  • Page 171 NAT for the answering fax machine. The originating fax does not wait for an answer, but immediately starts sending T.38 packets to the terminating fax machine upon receipt of a re-INVITE with T.38 only in the SDP, or T.38 and audio media in the SDP. This feature is Version 7.0 Mediant 3000...

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

    NoOpEnable and NoOpInterval parameters. 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.

  • Page 173: Security

    The following procedure describes how to configure Firewall rules through the Web interface. You can also configure it through ini file (AccessList).  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security > Version 7.0 Mediant 3000...
  • Page 174 Mediant 3000 Firewall Settings). Click Add; the following dialog box appears: Figure 14-1: Firewall Settings Table - Add Row Dialog Box Configure a Firewall rule according to the parameters described in the table below. Click Add, and then reset the device with a burn-to-flash for your settings to take effect.
  • Page 175 'Use Specific Interface' field. The list displays interface names as defined in the Interface table in [AccessList_Interface_x] ''Configuring IP Network Interfaces'' on page 145. Packet Size Defines the maximum allowed packet size. The valid range is 0 to 65535. Version 7.0 Mediant 3000...
  • Page 176 Mediant 3000 Parameter Description Note: When filtering fragmented IP packets, this field relates to the [AccessList_Packet_Size] overall (re-assembled) packet size, and not to the size of each fragment. Byte Rate Defines the expected traffic rate (bytes per second), i.e., the allowed bandwidth for the specified protocol.

  • Page 177: 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 7.0 Mediant 3000...

  • Page 178: 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 179: Enabling Ids

    To configure an IDS Policy: Open the IDS Policy table (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 7.0 Mediant 3000...
  • Page 180 Mediant 3000 Click Add; the following dialog box appears: Figure 14-4: IDS Policy Table - Add Row Dialog Box Configure an IDS Policy name according to the parameters described in the table below. Click Add. Table 14-3: IDS Policy Table Parameter Descriptions...
  • Page 181 Content length header not present (for TCP)  Header overflow  [3] Authentication failure =  Local authentication ("Bad digest" errors)  Remote authentication (SIP 401/407 is sent if original message includes authentication)  [4] Dialog establish failure = Version 7.0 Mediant 3000...
  • Page 182 Mediant 3000 Parameter Description  Classification failure (see ''Configuring Classification Rules'' on page 595)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response)  [5] Abnormal flow = ...

  • Page 183: Assigning Ids Policies

    A comma-separated list of SIP Interface IDs (e.g., 1,3,4)  A hyphen "-" indicates a range of SIP Interfaces (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., Version 7.0 Mediant 3000...

  • Page 184: Viewing Ids Alarms

    Mediant 3000 Parameter Description !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 indicates the Proxy Sets from where the attacks are coming from. The...
  • Page 185  malformed-miss- content-len  malformed-header- overflow   Local authentication ("Bad digest" errors) auth-establish-fail Authentication Failure   Remote authentication (SIP 401/407 is sent if auth-reject-response original message includes authentication)   Classification failure establish-classify-fail Dialog Version 7.0 Mediant 3000...

  • Page 186: Ipsec And Internet Key Exchange

    Mediant 3000 Type Description Syslog String   Establishment Routing failure establish-route-fail Failure   Other local rejects (prior to SIP 180 response) establish-local-reject   Remote rejects (prior to SIP 180 response) establish-remote- reject   Requests and responses without a matching...

  • Page 187: Enabling Ipsec

    You can also configure the IP Security Proposals table using the table ini file parameter IPsecProposalTable (see ''Security Parameters'' on page 867).  To configure IP Security Proposals: Open the IP Security Proposal table (Configuration tab > VoIP menu > Security > IPSec Proposal Table). Version 7.0 Mediant 3000...

  • Page 188: Configuring Ip Security Associations Table

    Mediant 3000 Click Add; the following dialog box appears: Figure 14-11: IP Security Proposals Table - Add Row Dialog Box Configure the parameters, as required. For a description of the parameters, see the table below. Click Add. To save the changes to flash memory, see ''Saving Configuration'' on page 672.
  • Page 189 You can also configure the IP Security Associations table using the table ini file parameter IPsecSATable (see ''Security Parameters'' on page 867).  To configure the IPSec Association table: Open the IP Security Associations table (Configuration tab > VoIP menu > Security > IPSec Association Table). Version 7.0 Mediant 3000...
  • Page 190 Mediant 3000 Click Add; the following dialog box appears: Figure 14-12: IP Security Associations Table - Add Row Dialog Box Configure the parameters, as required (for a description of these parameters, see the table below). In the above figure, a single IPSec/IKE peer (10.3.2.73) is configured.
  • Page 191 If the liveliness of the peer is questionable, the device sends a DPD message to query the status of the peer. If the device has no traffic to send, it never sends a DPD message. Version 7.0 Mediant 3000...
  • Page 192 Mediant 3000 Parameter Name Description Remote Tunnel Addr Defines the IP address of the peer router. [IPsecSATable_RemoteTu Note: The parameter is applicable only if the Operational Mode is set to nnelAddress] Tunnel. Remote Subnet Addr Defines the IP address of the remote subnet. Together with the Prefix...

  • Page 193: Media

    The following procedure describes how to configure gain control using the Web interface.  To configure gain control using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 15-1: Voice Volume Parameters in Voice Settings Page Version 7.0 Mediant 3000...

  • Page 194: Silence Suppression (Compression)

    Mediant 3000 Configure the following parameters: • 'Voice Volume' (VoiceVolume) - Defines the voice gain control (in decibels) of the transmitted signal. • 'Input Gain' (InputGain) - Defines the PCM input gain control (in decibels) of the received signal. Click Submit.
  • Page 195 • ECHybridLoss - defines the four-wire to two-wire worst-case Hybrid loss • ECNLPMode - defines the echo cancellation Non-Linear Processing (NLP) mode • EchoCancellerAggressiveNLP - enables Aggressive NLP at the first 0.5 second of the call Version 7.0 Mediant 3000...

  • Page 196: Fax And Modem Capabilities

    Mediant 3000 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. Notes: • Unless otherwise specified, the configuration parameters mentioned in this section are available on this page.

  • Page 197: Fax/Modem Operating Modes

    When fax transmission ends, the reverse switching from fax relay to voice is automatically performed at both the local and remote endpoints. You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). The parameter does not affect the actual transmission Version 7.0 Mediant 3000...
  • Page 198 Mediant 3000 rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy...
  • Page 199 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 200: Fax / Modem Transport Mode

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

  • Page 201: Fax/Modem Bypass Mode

    'Fax/Modem Bypass Coder Type' (FaxModemBypassCoderType). • 'Fax Bypass Payload Type' (FaxBypassPayloadType) - in the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). • ModemBypassPayloadType (ini file). • FaxModemBypassBasicRTPPacketInterval (ini file). • FaxModemBypasDJBufMinDelay (ini file). Version 7.0 Mediant 3000...

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

    In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Version 7.0 Mediant 3000...

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

    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, BellModemTransportType to 0 (transparent mode).

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

    Set the 'V.22 Modem Transport Type' parameter to Enable Bypass (V22ModemTransportType = 2). Set the 'V.23 Modem Transport Type' parameter to Enable Bypass (V23ModemTransportType = 2). Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Version 7.0 Mediant 3000...

  • Page 206: Relay Mode For T.30 And V.34 Faxes

    Mediant 3000 Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, V34FaxTransportType to 2 (Bypass). 15.2.3.2 Relay Mode for T.30 and V.34 Faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode.
  • Page 207 Max-Forwards: 70 From: <sip:318@10.8.6.55>;tag=1c1938956155 To: <sip:2001@10.8.211.250;user=phone> Call-ID: 193895529241200022331@10.8.6.55 CSeq: 1 INVITE Contact: <sip:318@10.8.6.55:5060> Supported: em,100rel,timer,replaces,path,resource-priority,sdp- anat Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Remote-Party-ID: <sip:318@10.8.211.250>;party=calling;privacy=off;screen=no;screen- ind=0;npi=1;ton=0 Remote-Party-ID: <sip:2001@10.8.211.250>;party=called;npi=1;ton=0 User-Agent: Audiocodes-Sip-Gateway-/v.6.80A.227.005 Content-Type: application/sdp Content-Length: 433 o=AudiocodesGW 1938931006 1938930708 IN IP4 10.8.6.55 Version 7.0 Mediant 3000...

  • Page 208: Modem Relay

    V.150.1 modem relay is applicable only to the Gateway application. • 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 209: 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 385) that includes the T.38, V.150, and G.711/VBD coders. Version 7.0 Mediant 3000...

  • Page 210: 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 211: 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 7.0 Mediant 3000...

  • Page 212: 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 213: Configuring Dtmf Transport Types

    (LBR) coders, the quality of the DTMF digits is reduced. To enable the mode: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the 'First Tx DTMF Option' parameter to Not Supported (FirstTxDTMFOption = 0). Version 7.0 Mediant 3000...

  • Page 214: Configuring Rfc 2833 Payload

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

  • Page 215: Configuring Rtp Base Udp Port

    (default is 6000) and number of channels is the maximum number of channels purchased from AudioCodes (included in the installed Software License Key). For example, if the base UDP port is set to 6000, the port range for 20 channels is:...

  • Page 216: Event Detection And Notification Using X-Detect Header

    Mediant 3000 Note: • The RTP port must be different from ports configured for SIP signaling traffic (i.e., ports configured for SIP Interfaces). For example, if the RTP port range is 6000 to 6999, the SIP port can either be less than 6000 or greater than 6999.

  • Page 217: Sit Event Detection

    Set the EnableDSPIPMDetectors parameter to 1. voice-end Note: PTT is currently not supported for SBC calls. 15.4.1 SIT Event Detection The device can detect and report the following Special Information Tones (SIT) types from the PSTN:  SIT-NC (No Circuit found) Version 7.0 Mediant 3000...

  • Page 218: Detecting Answering Machine Beeps

    Mediant 3000  SIT-IC (Operator Intercept)  SIT-VC (Vacant Circuit - non-registered number)  SIT-RO (Reorder - System Busy) There are additional three SIT tones that are detected as one of the above SIT tones:  The NC* SIT tone is detected as NC ...

  • Page 219: Sip Call Flow Examples Of Event Detection And Notification

    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,I NFO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.6.80A.227.005 Content-Type: application/x-detect Content-Length: 30 Type= AMD SubType= AUTOMATA Version 7.0 Mediant 3000...
  • Page 220 Mediant 3000 Upon detection 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 To: sipp <sip:sipp@172.22.2.9:5060>;tag=1 Call-ID: 1-29753@172.22.2.9...

  • Page 221: Answering Machine Detection (Amd)

    The device's default AMD feature is based on voice detection for North American English (see note below). It uses AudioCodes' sophisticated speech detection algorithms which are based on hundreds of real-life recordings of answered calls by live voice and answering machines in English.
  • Page 222 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.
  • Page 223 Calls) Table 15-5: 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) Version 7.0 Mediant 3000...

  • Page 224: Configuring Amd

    Mediant 3000 Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 15 (Best for Live Calls) 15.5.1 Configuring AMD You can configure AMD for all calls using the global AMD parameters, or for specific calls using IP Profiles.

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

    • 'AGC Minimum Gain' (AGCMinGain) - Defines the minimum gain (in dB) by the AGC when activated. • 'AGC Maximum Gain' (AGCMaxGain) - Defines the maximum gain (in dB) by the AGC when activated. Version 7.0 Mediant 3000...

  • Page 226: Configuring Various Codec Attributes

    Mediant 3000 • 'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. The parameter can either be the global parameter or per IP Profile.

  • Page 227: Configuring Dsp Templates

    You can also configure it through ini file (DSPTemplates).  To select a DSP Template: To use two DSP Templates: Open the DSP Templates page (Configuration tab > VoIP menu > Media > DSP Templates). Version 7.0 Mediant 3000...

  • Page 228: Configuring Media (Srtp) Security

    Mediant 3000 Click Add; the following dialog box appears: Figure 15-10: DSP Templates Table - Add Row Dialog Box Configure a DSP Template according to the parameters described in the table below. Click Add, and then reset the device with a burn-to-flash for your settings to take effect.
  • Page 229 For a detailed description of the SRTP parameters, see ''Configuring IP Profiles'' on page 391 and ''SRTP Parameters'' on page 869. • When SRTP is used, the channel capacity may be reduced. The procedure below describes how to configure SRTP through the Web interface. Version 7.0 Mediant 3000...
  • Page 230 Mediant 3000  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Figure 15-11: Media Security Page From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP.

  • Page 231: 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 232 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 233 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 m=audio 6030 RTP/AVP 8 96 c=IN IP4 10.33.8.70 a=ptime:20 a=sendonly a=label:2 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 --boundary_ac1fffff85b Content-Type: application/rs-metadata Content-Disposition: recording-session <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> Version 7.0 Mediant 3000...

  • Page 234: Enabling Sip-Based Media Recording

    Mediant 3000 <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <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>...
  • Page 235 By default, all source numbers or URIs are defined (*). [SIPRecRouting_Recorded SourcePrefix] Recorded Destination Defines calls to record based on destination number or URI. Prefix By default, all destination numbers or URIs are defined (*). [SIPRecRouting_Recorded DestinationPrefix] Version 7.0 Mediant 3000...

  • Page 236: Configuring Sip User Part For Srs

    X-Genesys-CallUUID header (which identifies the session) in the first 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' User's Manual...

  • Page 237: Avaya Ucid

    If the device receives a SIP INVITE from Avaya, it adds the UCID value, received in the User-to-User SIP header to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server. For example, if the received SIP header is: User-to-User: 00FA080019001038F725B3;encoding=hex...

  • Page 238: Radius-Based Services

    Mediant 3000 16.2 RADIUS-based Services The device supports Remote Authentication Dial In User Service (RADIUS), by acting as a RADIUS client. You can use RADIUS for the following:  Authentication and authorization of management users (login username and password) to gain access to the device's management interface.
  • Page 239 You can also configure it through ini file (RadiusServers). Note: To enable and configure RADIUS-based accounting, see ''Configuring RADIUS Accounting'' on page 779.  To configure a RADIUS server: Open the RADIUS Servers table (Configuration tab > System menu > Management > RADIUS Servers). Version 7.0 Mediant 3000...
  • Page 240 Mediant 3000 Click Add; the following dialog box appears: Figure 16-2: RADIUS Servers Table - Add Row Dialog Box Configure a RADIUS server according to the parameters described in the table below. Click Add. Table 16-2: RADIUS Servers Table Parameter Descriptions...

  • Page 241: Configuring Interface For Radius Communication

    (authorization). When a management user (client) tries to access the device, the device sends the RADIUS server the user's username and password for authentication. The RADIUS server replies with an acceptance Version 7.0 Mediant 3000...

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

    Mediant 3000 or a rejection notification. During the RADIUS authentication process, the device’s Web interface is blocked until an acceptance response is received from the RADIUS server. Note that communication between the device and the RADIUS server is done by using a shared secret, which is not transmitted over the network.

  • Page 243: Configuring Radius-Based User Authentication

    RADIUS servers, see ''Configuring Web User Accounts'' on page 82. # AudioCodes VSA dictionary VENDOR AudioCodes 5003 ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes VALUE ACL-Auth-Level ACL-Auth-UserLevel 50 VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100 VALUE ACL-Auth-Level ACL-Auth-SecurityAdminLevel 200 Define the list of users authorized to use the device, using one of the password authentication methods supported by the server implementation.
  • Page 244 Mediant 3000  To configure RADIUS parameters for login authentication: Open the Authentication Settings page (Configuration tab > System menu > Management > Authentication Settings). Figure 16-4: Authentication Settings Page - RADIUS Configuration From the 'Use RADIUS for Web/Telnet Login' drop-down list, select Enable to enable RADIUS authentication for Web and Telnet login.

  • Page 245: Securing Radius Communication

    16.2.6 RADIUS-based CDR Accounting Once you have configured a RADIUS server(s) for accounting in ''Configuring RADIUS Servers'' on page 238, you need to enable and configure RADIUS-based CDR accounting (see ''Configuring RADIUS Accounting'' on page 779). Version 7.0 Mediant 3000...

  • Page 246: Ldap-Based Management And Sip Services

    Mediant 3000 16.3 LDAP-based Management and SIP Services The device supports the Lightweight Directory Access Protocol (LDAP) application protocol and can operate with third-party, LDAP-compliant servers such as Microsoft Active Directory (AD). You can use LDAP for the following LDAP services: ...

  • Page 247: Enabling The Ldap Service

    The LDAP service can be used for authenticating and authorizing device management users (Web and CLI), based on the user's login username and password (credentials). At the same, it can also be used to determine users' management access levels (privileges). Version 7.0 Mediant 3000...

  • Page 248: Configuring Ldap Server Groups

    Mediant 3000 Before you can configure LDAP-based login authentication, you must enable this type of LDAP service, as described in the following procedure.  To enable LDAP-based login authentication: Open the Authentication Settings page (Configuration tab > System menu >...
  • Page 249 If the timeout expires, the cached entry is used only if there is no cache-entry- connectivity with the LDAP server. timeout The valid range is 0 to 35791. The default is 1200. If set to 0, the LDAP [LdapServersGroup_Cac entry is always valid. heEntryTimeout] Version 7.0 Mediant 3000...

  • Page 250: Configuring Ldap Servers

    Mediant 3000 Parameter Description Cache Entry Removal Defines the duration (in hours) after which the LDAP entry is deleted from Timeout the device's LDAP cache. cache-entry- The valid range is 0 to 596. The default is 0 (i.e., the entry is never removal-timeout deleted).
  • Page 251 User's Manual 16. Services Click Add; the following dialog box appears: Figure 16-8: LDAP Configuration Table - Add Row Dialog Box Configure an LDAP server according to the parameters described in the table below. Click Add. Version 7.0 Mediant 3000...
  • Page 252 Mediant 3000 Table 16-4: LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [LdapConfiguration_Inde Note: Each row must be configured with a unique index. LDAP Servers Group Assigns the LDAP server to an LDAP Server Group, configured in the LDAP Server Groups table (see ''Configuring LDAP Server Groups'' on page 248).
  • Page 253 Enables the device to encrypt the username and password (for Control and Management related queries) using TLS when sending them to the LDAP server. [LdapConfiguration_useT  [0] No = (Default) Username and password are sent in clear-text format. Version 7.0 Mediant 3000...

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

    Mediant 3000 Parameter Description  [1] Yes TLS Context Assigns a TLS Context for the connection with the LDAP server. [LdapConfiguration_Cont By default, no value is defined (None) and the device uses the default extName] TLS Context (ID 0). For configuring TLS Contexts, see ''Configuring TLS Certificate Contexts'' on page 123.

  • Page 255: Configuring The Ldap Search Filter Attribute

    The attribute is configured by the 'Management Attribute' parameter in the LDAP Configuration table (see ''Configuring LDAP Servers'' on page 250). Therefore, the LDAP response includes only the groups of which the specific user is a member. Version 7.0 Mediant 3000...

  • Page 256: Configuring Access Level Per Management Groups Attributes

    Mediant 3000 Notes: • The search filter is applicable only to LDAP-based login authentication and authorization queries. • The search filter is a global setting that applies to all LDAP-based login authentication and authorization queries, across all configured LDAP servers.
  • Page 257 Figure 16-11: Management LDAP Groups Table - Add Row Dialog Box Configure a group name(s) with a corresponding access level according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory. Version 7.0 Mediant 3000...

  • Page 258: Configuring The Device's Ldap Cache

    Mediant 3000 Table 16-6: Management LDAP Groups Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [MgmntLDAPGroups_Gr Note: Each row must be configured with a unique index. oupIndex] Level Defines the access level of the group(s).
  • Page 259 Whenever the device queries the LDAP server for new Attributes, the device includes all previously cached Attributes for that user in the sent query. • The LDAP Cache feature is applicable only to LDAP-based SIP queries (Control). Version 7.0 Mediant 3000...

  • Page 260: Configuring Local Database For Management User Authentication

    Mediant 3000 The following procedure describes how to configure the device's LDAP cache through the Web interface. For a full description of the cache parameters, see ''LDAP Parameters'' on page 1056.  To enable and configure the LDAP cache: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP >...

  • Page 261: Ldap-Based Login Authentication Example

    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). The LDAP server's entry data structure schema in the example is as follows: Version 7.0 Mediant 3000...
  • Page 262 Mediant 3000  DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: Figure 16-15: Base Path (DN) in LDAP Server User's Manual Document #: LTRT-89730...
  • Page 263 (where the attribute's value equals the username): Figure 16-16: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 16-17: User's memberOf Attribute Version 7.0 Mediant 3000...
  • Page 264 Mediant 3000  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 16-18: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...

  • Page 265: Enabling Ldap Searches For Numbers With Characters

    16.3.11 Enabling LDAP Searches for Numbers with Characters Typically, the device performs LDAP searches in the AD for complete numbers where the digits are adjacent to one another (e.g., 5038234567). However, if the number is defined in Version 7.0 Mediant 3000...

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

    Mediant 3000 the AD with characters (such as spaces, hyphens and periods) separating the digits (e.g., 503-823 4567), the LDAP query returns a failed result. To enable the device to search the AD for numbers that may contain characters between...
  • Page 267 "PBX" (PBX:<PBX_number>): used to match a routing rule based on query results of the PBX / IP PBX number (MSLDAPPBXNumAttributeName) • "MOBILE" (MOBILE:<mobile_number>): used to match a routing rule based on query results of the mobile number (MSLDAPMobileNumAttributeName) Version 7.0 Mediant 3000...
  • Page 268 Mediant 3000 • "LDAP_ERR": used to match a routing rule based on a failed query result when no attribute is found in the AD Note: These prefixes are involved only in the routing and manipulation processes; they are not used as the final destination number.

  • Page 269: Configuring Ad-Based Routing Rules

    The following procedure describes how to configure outbound IP routing based on LDAP queries.  To configure LDAP-based IP routing for Lync Server: Configure the LDAP server parameters, as described in ''Configuring LDAP Servers'' on page 250. Configure the AD attribute names used in the LDAP query: Version 7.0 Mediant 3000...
  • Page 270 Mediant 3000 Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). Figure 16-25: LDAP Parameters for Microsoft Lync Server 2010 Configure the LDAP attribute names as desired. Gateway application: Configure AD-based Tel-to-IP routing rules: Open the Tel-to-IP Routing table (Configuration tab >...
  • Page 271 Rule 6: Sends query for original destination number of received call to the LDAP server.  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases • LDAP functionality is disabled. Version 7.0 Mediant 3000...

  • Page 272: Querying The Ad For Calling Name

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

  • Page 273: Least Cost Routing

    This example shows four defined Cost Groups and the total call cost if the average call duration is 10 minutes: Table 16-10: Call Cost Comparison between Cost Groups for different Call Durations Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes 80.3 Version 7.0 Mediant 3000...
  • Page 274 Mediant 3000 If four matching routing rules are located in the routing table and each one is assigned a different Cost Group as listed in the table above, then the rule assigned Cost Group "D" is selected. Note that for one minute, Cost Groups "A" and "D" are identical, but due to the average call duration, Cost Group "D"...

  • Page 275: Configuring Lcr

    (charge per minute). Once configured, you can configure Time Bands per Cost Group. Up to 10 Cost Groups can be configured. The following procedure describes how to configure Cost Groups through the Web interface. You can also configure it through ini file (CostGroupTable). Version 7.0 Mediant 3000...

  • Page 276: Configuring Time Bands For Cost Groups

    Mediant 3000  To configure a Cost Group: Open the Cost Group table (Configuration tab > VoIP menu > Services > Least Cost Routing > Cost Group Table). Click Add; the following dialog box appears: Configure a Cost Group according to the parameters described in the table below.
  • Page 277 Defines the call connection cost during this time band. This is added as a fixed charge to the call. The valid value range is 0-65533. The default is 0. [CostGroupTimebands_ ConnectionCost] Note: The entered value must be a whole number (i.e., not a decimal). Version 7.0 Mediant 3000...

  • Page 278: Assigning Cost Groups To Routing Rules

    Mediant 3000 Parameter Description Minute Cost Defines the call cost per minute charge during this timeband. The valid value range is 0-65533. The default is 0. [CostGroupTimebands_ Note: The entered value must be a whole number (i.e., not a decimal).

  • Page 279: Http-Based Remote Services

     Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM. Notes: • You can configure only one HTTP Remote Service entry for Routing, for Call Status, and for Topology.
  • Page 280 Mediant 3000 The following procedure describes how to configure HTTP Remote Services through the Web interface. You can also configure it through ini file (HTTPRemoteServices).  To configure an HTTP-based service Open the HTTP Remote Services table (Configuration tab > VoIP menu > Services >...
  • Page 281 The valid value is 1 to 10. The default is 1. Username Defines the username for HTTP authentication. [HTTPRemoteServices_Aut The valid value is a string of up to 80 characters. The default is "user". hUserName] Version 7.0 Mediant 3000...

  • Page 282: Configuring Remote Http Hosts

    Mediant 3000 Parameter Description Password Defines the password for HTTP authentication. [HTTPRemoteServices_Aut The valid value is a string of up to 80 characters. The default is hPassword] "password". TLS Context Assigns a TLS Context for the connection with the HTTP service.
  • Page 283 If the address is an FQDN and the DNS resolution results in multiple IP addresses, the device device attempts to establish multiple connections (sessions) for each IP address. Only the first 10 resolved IP addresses are used regardless of the number of hosts. Version 7.0 Mediant 3000...

  • Page 284: Centralized Third-Party Routing Server

    16.5.3 Centralized Third-Party Routing Server You can employ a remote, third-party routing server to handle call routing decisions in deployments consisting of multiple AudioCodes devices. The routing server can be used to handle SBC and Tel-to-IP Gateway calls. Employing a routing server replaces the need for using the device's routing tables for determining the destination of calls (IP-to-IP Routing table for SBC calls and Tel-to-IP Routing table for Tel-to-IP calls).
  • Page 285 Alternatively, it may enable the device to return a failure response to the previous device in the route path chain and respond with an alternative route to this device. Version 7.0 Mediant 3000...
  • Page 286 Mediant 3000 Therefore, alternative routing can be implemented at any point in the route path.  Call status: The device can report call status to the routing server to indicate whether a call has successfully been established and/or failed (disconnected). The device can also report when an IP Group (Proxy Set) is unavailable, detected by the keep-alive mechanism, or when the CAC thresholds permitted per IP Group have been crossed.

  • Page 287: Configuring Call Setup Rules

    SBC IP-to-IP routing - see Configuring SBC IP-to-IP Routing Rules on page 603  Tel-to-IP routing rules - see Configuring Tel-to-IP Routing Rules on page 496  IP-to-Tel routing rules - see ''Configuring IP-to-Trunk Group Routing Rules'' on page Version 7.0 Mediant 3000...
  • Page 288 Mediant 3000 If an incoming call matches the characteristics of a routing rule, the device first runs the assigned Call Setup Rules Set ID before routing the call according to the rule. The device uses the routing rule to route the call, depending on the result of the Call Setup Rules Set ...
  • Page 289 (attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called number is the same as the number in the attribute "msRTCSIP- PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Version 7.0 Mediant 3000...

  • Page 290: Call Setup Rule Examples

    Mediant 3000 Parameter Description Action Subject Defines the element (header, parameter, or body) upon which you want to perform the action. The valid value is a string of up to 100 characters (case-insensitive). [CallSetupRules_ActionSub ject] Examples:  header.from contains '1234' (SBC calls only) ...
  • Page 291 'Action Type': Exit ♦ 'Action Value': false If the attribute record is found (i.e., condition is not met), the rule ends with a default exit result of true and uses the first routing rule (Lync). If the attribute Version 7.0 Mediant 3000...

  • Page 292: Enhanced 9-1-1 Support For Lync Server

    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 (hereafter referred to as Lync Server) and AudioCodes' device's ELIN interworking capabilities, which provides the SIP Trunk or ISDN (or CAMA) connectivity to the E9-1-1 emergency service provider.

  • Page 293: Microsoft Lync Server And E9-1-1

    16. Services The VoIP user dials 9-1-1. AudioCodes' ELIN device eventually sends the call to the emergency service provider over the PSTN or SIP Trunk (PSAP server). The emergency service provider identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network.
  • Page 294 Mediant 3000 Immediately after the Lync client registration process or when the operating system detects a network connection change, each Lync client submits a request to the LIS for a location. If the LIS is able to resolve a location address for the client request, it returns the address in a location response.

  • Page 295: Adding Elins To The Location Information Server

    (CSV) file containing the column formats listed in the table below. Table 16-16: Columns in the LIS Database Network Element Columns <BSSID>,<Description>,<Location>,<CompanyName>,<HouseNu mber>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,< Wireless access point StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Co untry> <Subnet>,<Description>,<Location>,<CompanyName>,<HouseNu mber>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,< Subnet StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Co untry> <ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location> Port ,<CompanyName>,<HouseNumber>,<HouseNumberSuffix>,…<Pr eDirectional>,<StreetName>,<StreetSuffix>,<PostDirectional>,<City Version 7.0 Mediant 3000...

  • Page 296: Passing Location Information To The Pstn Emergency Provider

    Mediant 3000 Network Element Columns >,<State>,<PostalCode>,<Country> <ChassisID>,<Description>,<Location>,<CompanyName>,<House Number>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName> Switch ,<StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<C ountry> For the ELIN number to be included in the SIP INVITE (XML-based PIDF-LO message) sent by the Mediation Server to the ELIN device, the administrator must add the ELIN number to the <CompanyName>...

  • Page 297: Audiocodes Elin Device For Lync Server E9-1-1 Calls To Pstn

    ELIN when dialing 9-1-1. 16.7.3 AudioCodes ELIN Device for Lync Server E9-1-1 Calls to PSTN 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 298: Detecting And Handling E9-1-1 Calls

    PSAP, based on ELIN-address match lookup in the emergency service provider's ALI database. The figure below illustrates an AudioCodes ELIN device deployed in the Lync Server environment for handling E9-1-1 calls between the Enterprise and the emergency service provider.
  • Page 299 0 0 IN IP4 Client s=session c=IN IP4 Client t=0 0 m=audio 30684 RTP/AVP 114 111 112 115 116 4 3 8 0 106 97 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:0 PCMU/8000 Version 7.0 Mediant 3000...

  • Page 300: Pre-Empting Existing Calls For E9-1-1 Calls

    Mediant 3000 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 xmlns="urn:schema:Rtc.Lis.LocationPolicyTagID.2008">user- tagid</LocationPolicyTagID ></ms:msftE911PidfExtn></status><timestamp>1991-09- 22T13:37:31.03</timestamp></tuple></presence> ------=_NextPart_000_4A6D_01CAB3D6.7519F890-- 16.7.3.2 Pre-empting Existing Calls for E9-1-1 Calls...

  • Page 301: Selecting Elin For Multiple Calls Within Same Erl

    ELIN in the list, and so on until it finds an ELIN that is not being used and sends this ELIN.  If all the ELINs in the list are in use by active calls, the device selects the ELIN number as follows: Version 7.0 Mediant 3000...

  • Page 302: Location Based Emergency Routing

    Location-based emergency routing is applicable only to the Gateway application. 16.7.4 Configuring AudioCodes ELIN Device This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server environment. 16.7.4.1 Enabling the E9-1-1 Feature By default, the ELIN device feature for E9-1-1 emergency call handling in a Lync environment is disabled.

  • Page 303: Configuring The Sip Release Cause Code For Failed E9-1-1 Calls

    (e.g., 911) in the 'Destination Username Prefix' parameter of the IP Group belonging to the E9-1-1 callers. The following example shows IP-to-IP routing rules for E9-1-1 in a Lync environment: Figure 16-32: Example of IP-to-IP Routing Rules for Lync E9-1-1 Version 7.0 Mediant 3000...

  • Page 304: Configuring Location-Based Emergency Routing

    Mediant 3000 16.7.4.5 Configuring Location-Based Emergency Routing The device identifies the geographical location of emergency callers by their ELIN numbers, which is present in the PIDF-LO XML body of received SIP INVITE messages. Therefore, you need to configure the device to route emergency calls to a destination (i.e., emergency center such as police) that is appropriate to the caller's ELIN number.

  • Page 305: Viewing The Elin Table

    Index 0 manipulates the destination number for London emergency callers; Index 1 manipulates the destination number for Manchester emergency callers. 16.7.4.6 Viewing the ELIN Table To view the ELIN table:  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump Version 7.0 Mediant 3000...
  • Page 306 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 307: 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 308: 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 309: Configuring Quality Of Experience Profiles

     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 the SEM Server'' on page 307.
  • Page 310 Mediant 3000 Note: For your convenience, the device provides pre-configured Quality of Experience Profiles. One of these pre-configured profiles is the default Quality of Experience Profile. Therefore, if you do not configure a Quality of Experience Profile, this default is used.
  • Page 311 Defines the parameter to monitor and report.  [0] MOS (default)  [1] Delay [QOEColorRules_monitoredPara  [2] Packet Loss  [3] Jitter  [4] RERL [Echo] Direction Defines the monitoring direction.  [0] Device Side (default)  [1] Remote Side [QOEColorRules_direction] Version 7.0 Mediant 3000...
  • Page 312 Mediant 3000 Parameter Description Sensitivity Level Defines the sensitivity level of the thresholds.  [0] User Defined = Need to define the thresholds in the parameters described below. [QOEColorRules_profile]  [1] Low = Pre-configured low sensitivity threshold values. Thus, reporting is done only if changes in parameters' values are significant.

  • Page 313: Configuring Bandwidth Profiles

    The following procedure describes how to configure Bandwidth Profiles through the Web interface. You can also configure it through ini file (BWProfile) .  To configure Bandwidth Profiles: Open the Bandwidth Profile page (Configuration tab > VoIP menu > Quality of Experience > Bandwidth Profile). Version 7.0 Mediant 3000...
  • Page 314 Mediant 3000 Click Add; the following dialog box appears: Figure 17-4: Bandwidth Profile Table - Add Row Dialog Box The figure above shows a configuration example where if the outgoing voice traffic threshold of 64,000 increases by 80% (70% warning threshold plus 10% hysteresis) to 115,200 (64,000 plus 51,200), a Yellow state occurs and an alarm is sent.
  • Page 315 [1] Enable If enabled, an alarm is sent if one of the following scenarios occurs:  Warning threshold is exceeded (Warning severity - Yellow threshold).  Any configured bandwidth threshold is exceeded (Major severity - Red threshold). Version 7.0 Mediant 3000...

  • Page 316: Configuring Media Enhancement Profiles

    Mediant 3000 17.4 Configuring Media Enhancement Profiles Media Enhancement Profiles provides support for access control and media quality enhancements based on call quality measurements (configured in ''Configuring Quality of Experience Profiles'' on page 309) and bandwidth utilization (configured in ''Configuring Bandwidth Profiles'' on page 313).
  • Page 317 Configure a Media Enhancement Rule according to the parameters described in the table below. Click Add, and then reset the device with a save ("burn") to flash memory. Table 17-5: Media Enhancement Rules Table Parameter Descriptions Parameter Description Version 7.0 Mediant 3000...
  • Page 318 Mediant 3000 Parameter Description Index Defines the index of the table row entry. [MediaEnhancementRules_RuleI ndex] Trigger Defines the monitored metrics parameter or bandwidth associated with this rule.  [0] MOS (default) [MediaEnhancementRules_Trigg  [1] Delay  [2] Packet Loss ...

  • Page 319: Control Network

    The following procedure describes how to configure Media Realms through the Web interface. You can also configure it through ini file (CpMediaRealm).  To configure a Media Realm: Open the Media Realm table (Configuration tab > VoIP menu > VoIP Network > Media Realm Table). Version 7.0 Mediant 3000...
  • Page 320 Mediant 3000 Click Add; the following dialog box appears: Figure 18-1: Media Realm Table - Add Row Dialog Box Configure the Media Realm according to the parameters described in the table below. Click Add. Table 18-1: Media Realm Table Parameter Descriptions...
  • Page 321 If the table is not configured, the default Media Realm includes all configured media interfaces. QoE Profile Assigns a QoE Profile to the Media Realm. By default, no value is defined (None). [CpMediaRealm_QoeP For configuring QoE Profiles, see ''Configuring Quality of Experience rofile] Profiles'' on page 309. Version 7.0 Mediant 3000...

  • Page 322: Configuring Remote Media Subnets

    Mediant 3000 Parameter Description BW Profile Assigns a Bandwidth Profile to the Media Realm. By default, no value is defined (None). [CpMediaRealm_BWPr For configuring Bandwidth Profiles, see ''Configuring Bandwidth Profiles'' on ofile] page 313. 18.1.1 Configuring Remote Media Subnets Remote Media Subnets define destination subnets for media (RTP/SRTP) traffic on a specific Media Realm.
  • Page 323 Defines the subnet mask in Classless Inter-Domain Routing (CIDR) notation. For example, 16 denotes 255.255.0.0. The default is 16. [RemoteMediaSubnet_ PrefixLength] Address Family Defines the IP address protocol.  [2] IPv4 (default)  [10] IPv6 [RemoteMediaSubnet_ AddressFamily] Version 7.0 Mediant 3000...

  • Page 324: Configuring Media Realm Extensions

    Mediant 3000 Parameter Description Destination IP Defines the IP address of the destination. The default is 0.0.0.0. [RemoteMediaSubnet_ DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the Remote Media Subnet. By default, no value is defined (None).
  • Page 325 For more information, see ''Configuring RTP Base UDP Port'' on page 215.  The port range must not overlap with any other media port range that you have configured in the table or in the Media Realm table. Version 7.0 Mediant 3000...

  • Page 326: Configuring Srds

    Mediant 3000 Parameter Description Port Range End Defines the last (upper) port in the range of media UDP ports for the Media Realm Extension. [MediaRealmExtension _PortRangeEnd] Note: It is unnecessary to configure the parameter. The device automatically populates the parameter with a value, calculated by the summation of the 'Number of Media Session Legs' parameter (multiplied by the port chunk size) and the 'Port Range Start' parameter.
  • Page 327 SRD. The single SRD would be assigned to three different SIP Interfaces, where each SIP Interface would represent a specific Layer-3 network (IP PBX, SIP Trunk, or far-end users) in your environment. The following figure provides an example of such a deployment: Figure 18-6: Deployment using a Single SRD Version 7.0 Mediant 3000...
  • Page 328 Mediant 3000 Notes: • It is recommended to use a single-SRD configuration topology, unless you are deploying the device in a multi-tenant environment, in which case, multiple SRDs are required. • Each SIP Interface, Proxy Set, and IP Group can be associated with only one SRD.
  • Page 329 SRD and other Isolated SRDs. However, calls can be routed between the SRD and other Shared SRDs. For more information on SRD Sharing Policy, see Multiple SRDs for Multi- tenant Deployments on page 332. Version 7.0 Mediant 3000...
  • Page 330 Mediant 3000 Parameter Description SBC Operation Mode Defines the device's operational mode for the SRD.  [0] B2BUA = (Default) Device operates as a back-to-back user agent (B2BUA), changing the call identifiers and headers between the [SRD_SBCOperationMod inbound and outbound legs.
  • Page 331 Enables the SRD to be used by a third-party routing server for call routing decisions.  [0] Not Used (default) [SIPInterface_UsedByRo  [1] Used utingServer] For more information on the third-party routing server feature, see ''Centralized Third-Party Routing Server'' on page 284. Version 7.0 Mediant 3000...

  • Page 332: Filtering Tables In Web Interface By Srd

    Mediant 3000 18.2.1 Filtering Tables in Web Interface by SRD When your configuration includes multiple SRDs, you can filter tables in the Web interface by a specific SRD. The filter is configured in the SRD Filter drop-down list, located on the Web interface's toolbar.
  • Page 333 Routing Policies, see ''Configuring SBC Routing Policy Rules'' on page 616. The figure below illustrates a multi-tenant architecture with Isolated SRD tenants ("A" and "B") and a Shared SRD tenant ("Data Center") serving as a SIP Trunk: Version 7.0 Mediant 3000...
  • Page 334 Mediant 3000 To facilitate multi-tenant configuration through CLI, you can access a specific tenant "view". Once in a specific tenant view, all configuration commands apply only to the currently viewed tenant. Only table rows (indexes) belonging to the viewed tenant can be modified.

  • Page 335: Cloning Srds

    Network Interface for valid configuration.  To clone an SRD:  Web interface: In the SRD table, select an SRD to clone, and then click the Clone button. Version 7.0 Mediant 3000...

  • Page 336: Color-Coding Of Srds In Web Interface

    Mediant 3000 18.2.4 Color-Coding of SRDs in Web Interface To easily identify your configured SRDs, the Web interface displays each SRD in a unique color. The color is automatically and randomly assigned to new SRDs, and is displayed in a box alongside the name of the SRD, in tables where the SRD is configured or assigned.

  • Page 337: Configuring Sip Interfaces

    If you edit any of the following fields of the associated SIP Interface: 'Application Type', 'UDP Port, 'TCP Port', 'TLS Port' or 'SRD' fields. • If you edit or delete a network interface in the Interface table that is associated with the SIP Interface. Version 7.0 Mediant 3000...
  • Page 338 Mediant 3000 The following procedure describes how to configure SIP interfaces through the Web interface. You can also configure it through ini file (SIPInterface).  To configure a SIP Interface: Open the SIP Interface table (Configuration tab > VoIP menu > VoIP Network > SIP Interface Table).
  • Page 339 6000 to 6999, the SIP port can either be less than 6000 or greater than 6999.  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). Version 7.0 Mediant 3000...
  • Page 340 Mediant 3000 Parameter Description Media Realm Assigns a Media Realm to the SIP Interface. By default, no value is defined (None). [SIPInterface_MediaReal For configuring Media Realms, see ''Configuring Media Realms'' on page 319. Note: If you later delete the assigned Media Realm in the Media Realm table, this value becomes None.
  • Page 341  [1] Enable = The device accepts REGISTER requests from new users even if they were not authenticated by a proxy server, and registers the user in its registration database. Version 7.0 Mediant 3000...
  • Page 342 Mediant 3000 Parameter Description Notes:  Regardless of the parameter, the device always accepts registration refreshes from users that are already registered in its database.  If configured to Disable or Enable, the parameter overrides the 'Enable Un-Authenticated Registrations' parameter settings of the SRD (in the SRD table) that is associated with the SIP Interface.

  • Page 343: Configuring Ip Groups

    (see Configuring Number Manipulation Tables on page 469).  Included in routing decisions by a third-party routing server. If deemed necessary for routing, the routing server can even create an IP Group. For more information, see Centralized Third-Party Routing Server on page 284. Version 7.0 Mediant 3000...
  • Page 344 Mediant 3000 You can also apply the device's Quality of Experience feature to IP Groups:  Quality of Experience Profile: Call quality monitoring based on thresholds for voice metrics (e.g., MOS) can be applied per IP Group. For example, if MOS is considered poor, calls belonging to this IP Group can be rejected.
  • Page 345 This IP Group type is necessary for any of the following scenarios:  The IP Group cannot be defined as a Server-type since its address is initially unknown and therefore, a Proxy Set cannot be Version 7.0 Mediant 3000...
  • Page 346 Mediant 3000 Parameter Description configured for it.  The IP Group cannot be defined as a User since the SIP Contact header of the incoming REGISTER does not represent a specific user. The Request-URI user part can change and therefore, the device is unable to identify an already registered user and therefore, adds an additional record to the database.
  • Page 347 Assigns a Quality of Experience Profile rule. By default, no value is defined (None). [IPGroup_QOEProfile] For configuring Quality of Experience Profiles, see ''Configuring Quality of Experience Profiles'' on page 309. Media Enhancement Assigns a Media Enhancement Profile rule. Version 7.0 Mediant 3000...
  • Page 348 Mediant 3000 Parameter Description By default, no value is defined (None). Profile For configuring Media Enhancement Profiles, see ''Configuring Media Enhancement Profiles'' on page 316. [IPGroup_MediaEnhance mentProfile] Bandwidth Profile Assigns a Bandwidth Profile rule. By default, no value is defined (None).
  • Page 349 496) as the Request-URI host name in outgoing INVITE messages, instead of the value configured in the 'SIP Group Name' field. Note: The parameter is applicable only to Server-type IP Groups. SBC Tab (SBC Application) Version 7.0 Mediant 3000...
  • Page 350 Mediant 3000 Parameter Description SBC Operation Mode Defines the device's operational mode for the IP Group.  [-1] Not Configured = (Default)  [0] B2BUA = Device operates as a back-to-back user agent (B2BUA), [IPGroup_SBCOperationM changing the call identifiers and headers between the inbound and ode] outbound legs.
  • Page 351 Message Manipulation on page 371. [IPGroup_OutboundManS Note: If you assign a Message Manipulation Set ID that includes rules for manipulating the host name in the Request-URI, To, and/or From SIP headers, the parameter overrides the IPGroup_SIPGroupName parameter. Version 7.0 Mediant 3000...
  • Page 352 Mediant 3000 Parameter Description Msg Man User Defined Defines a value for the SIP user part that can be used in Message String1 Manipulation rules configured in the Message Manipulations table. The Message Manipulation rule obtains this value from the IP Group, by using the following syntax: param.ipg.<src|dst>.user-defined.<0>.
  • Page 353 [5] P-Preferred  [6] Route  [7] Diversion  [8] P-Associated-URI  [9] P-Called-Party-ID  [10] Contact  [11] Referred-by Notes:  The parameter is applicable only when classification is done according to the Classification table. Version 7.0 Mediant 3000...
  • Page 354 Mediant 3000 Parameter Description  If the configured SIP header does not exist in the incoming INVITE message, the classification of the message to a source IP Group fails.  If the device receives an INVITE as a result of a REFER request or a 3xx response, then the incoming INVITE is routed according to the Request-URI.

  • Page 355: Configuring Proxy Sets

    IP address and/or DNS host name (FQDN), enabling you to implement load balancing and redundancy (Proxy Hot-Swap feature) between multiple servers. If you configure the address as an FQDN, you can configure the method (A-record DNS, SRV, or Version 7.0 Mediant 3000...
  • Page 356 Mediant 3000 NAPTR) for resolving the domain name to an IP address. The device supports up to 30 DNS-resolved IP addresses. (If the DNS resolution provides more than this number, the device uses the first 30 IP addresses in the received list and ignores the rest.) Each Proxy Set can be assigned a specific SSL/TLS certificate the (TLS Context), enabling you to use different TLS certificates per SIP entity (IP Group).
  • Page 357 Address Table link located below the table; the Proxy Address table opens. Click Add; the following dialog box appears: Figure 18-12: Proxy Address Table - Add Row Dialog Box Configure the address of the Proxy Set according to the parameters described in the table below. Click Add. Version 7.0 Mediant 3000...
  • Page 358 Mediant 3000 Table 18-7: Proxy Sets Table and Proxy Address Table Parameter Description Parameter Description Proxy Sets Table Index Defines an index number for the new table row. Note: Each row must be configured with a unique index. [ProxySet_Index] Assigns an SRD to the Proxy Set.
  • Page 359  [1] Homing = The device always attempts to operate with the primary proxy. The device switches back to the primary proxy whenever it becomes available. Version 7.0 Mediant 3000...
  • Page 360 Mediant 3000 Parameter Description Notes:  To enable this functionality, you must also enable the Proxy Keep-Alive feature (see the 'Proxy Keep-Alive' parameter in this table).  The Homing option can only be used if the 'Proxy Keep-Alive' parameter is set to Using Options.
  • Page 361 [1] IP + Port + Transport = Classifies calls to the Proxy Set according to onInput] IP address, port, and transport type. Notes:  The parameter is applicable only if the IP Group table's parameter, 'Classify by Proxy Set' is set to Enable (see Configuring IP Groups on Version 7.0 Mediant 3000...
  • Page 362 Mediant 3000 Parameter Description page 343).  The parameter is applicable only to the SBC application. TLS Context Index Assigns a TLS Context (SSL/TLS certificate) to the Proxy Set. By default, no TLS Context is assigned. If you assign a TLS Context, the...

  • Page 363: Sip Definitions

    You can also configure it through ini file (Account).  To configure an Account: Open the Account table (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Version 7.0 Mediant 3000...
  • Page 364 Mediant 3000 Configure an account according to the parameters described in the table below. Click Add. Once you have configured Accounts, you can register or un-register them, as described below:  To register or un-register an Account: In the table, select the required Account entry row.
  • Page 365 (GIN). For more information, see ''Single Registration for Multiple Phone Numbers using GIN'' on page 366. Notes:  Gateway application: To enable registration, you also need to set the 'Registration Mode' parameter to Per Account in the Trunk Group Settings Version 7.0 Mediant 3000...

  • Page 366: Regular Registration Mode

    Mediant 3000 Parameter Description table (see Configuring Trunk Group Settings on page 463).  The account registration is not affected by the IsRegisterNeeded parameter. Contact User Defines the AOR username. This appears in REGISTER From/To headers as ContactUser@HostName, and in INVITE/200 OK Contact headers as ContactUser@<device's IP address>.
  • Page 367 'gin'. The Supported header contains the token 'path' and the URI in the Contact header contains the parameter 'bnc' without a user part: Contact: <sip:198.51.100.3;bnc>; The figure below illustrates the GIN registration process: The figure below illustrates an incoming call using GIN: Version 7.0 Mediant 3000...

  • Page 368: Configuring Proxy And Registration Parameters

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

  • Page 369: Sip Message Authentication Example

    The REGISTER request is sent to a Registrar/Proxy server for registration: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c17940 To: <sip: 122@10.1.1.200> Call-ID: 634293194@10.1.1.200 User-Agent: Sip-Gateway/Mediant 3000/v.6.80A.227.005 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Upon receipt of this request, the Registrar/Proxy returns a 401 Unauthorized response: SIP/2.0 401 Unauthorized...
  • Page 370 • 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 371: Configuring Sip Message Manipulation

    The device also supports a built-in SIP message normalization feature that can be enabled per Message Manipulation rule. The normalization feature removes unknown SIP message elements before forwarding the message. These elements can include SIP headers, SIP header parameters, and SDP body fields. Version 7.0 Mediant 3000...
  • Page 372 Mediant 3000 The SIP message manipulation feature supports the following:  Manipulation on SIP message type (Method, Request/Response, and Response type)  Addition of new SIP headers  Removal of SIP headers ("black list")  Modification of SIP header components such as values, header values (e.g., URI...
  • Page 373 User's Manual 19. SIP Definitions The figure below illustrates a SIP message manipulation example: Figure 19-2: SIP Header Manipulation Example Version 7.0 Mediant 3000...
  • Page 374 Mediant 3000 Notes: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide. • For the SBC application, Inbound message manipulation is done only after the Classification, inbound/outbound number manipulations, and routing processes.
  • Page 375 = rule applies to SUBSCRIBE confirmation responses Note: Currently, SIP 100 Trying messages cannot be manipulated. Condition Defines the condition that must exist for the rule to apply. The valid value is a string (case-insensitive). [MessageManipulations_ Version 7.0 Mediant 3000...
  • Page 376 Mediant 3000 Parameter Description Condition] For example:  header.from.url.user== '100' (indicates that the user part of the From header must have the value "100")  header.contact.param.expires > '3600'  header.to.url.host contains 'domain'  param.call.dst.user != '100' Operation Action Subject Defines the SIP header upon which the manipulation is performed.

  • Page 377: Configuring Sip Message Policy Rules

    You can also configure it through ini file (MessagePolicy).  To configure SIP Message Policy rules: Open the Message Policy table (Configuration tab > VoIP menu > SIP Definitions > Msg Policy & Manipulation > Message Policy Table). Version 7.0 Mediant 3000...
  • Page 378 Mediant 3000 Click Add; the following dialog box appears: Figure 19-5: Message Policy Table - Add Row Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Add. Table 19-3: Message Policy Table Parameter Descriptions...
  • Page 379 Defines the policy (blacklist or whitelist) for the SIP body specified in the 'Body List' parameter (above).  [0] Policy Blacklist =The specified SIP body is rejected. [MessagePolicy_BodyLis  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; tType] the others are rejected. Version 7.0 Mediant 3000...
  • Page 380 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 381: Coders And Profiles

    Notes: • Some coders are license-dependent and are available only if purchased from AudioCodes and included in the Software License Key installed on your device. For more information, contact your AudioCodes sales representative. • Only the packetization time of the first coder in the coder list is declared in INVITE/200 OK SDP, even if multiple coders are defined.
  • Page 382 Mediant 3000  To configure coders: 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.
  • Page 383 8 or [g711AlawVbd] 50, 60, 80, 100, 120 Dynamic (default 118) G.711U-law_VBD 10, 20 (default), 30, 40, Dynamic [g711UlawVbd] 50, 60, 80, 100, 120 (default 110) G.722 20 (default), 40, 60, 80, 64 (default) [g722] 100, 120 Version 7.0 Mediant 3000...
  • Page 384 Mediant 3000 Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression   [0] 5.3 [0] Disable G.723.1 30 (default), 60, 90, 120, (default) [g7231]  [1] Enable  [1] 6.3   [0] 16 [0] Disable G.726...

  • Page 385: Configuring Coder Groups

    SDP offer. The added coder is referred to as an extension coder. For more information on extension coders, see Coder Transcoding on page 562. To apply a Coder Group for transcoding to a SIP entity: Version 7.0 Mediant 3000...
  • Page 386 Mediant 3000 Configure a Coder Group in the Coder Group Settings table (see description below). In the IP Profile associated with the SIP entity (see Configuring IP Profiles on page 391): • Assign the Coder Group (using the IpProfile_SBCExtensionCodersGroupID parameter).
  • Page 387 [CodersGroupX_CoderSpecific]  [0] 0 = Bandwidth Efficient  [1] 1 = Octet Aligned (default) Note: The AMR payload type can be configured globally using the AmrOctetAlignedEnable parameter. However, the Coder Group configuration overrides the global parameter. Version 7.0 Mediant 3000...

  • Page 388: Configuring Tel Profile

    Mediant 3000 20.3 Configuring Tel Profile The Tel Profile Settings table lets you configure up to nine Tel Profiles. A Tel Profile is a set of parameters with specific settings which can be assigned to specific calls. The Tel Profile Settings table includes a wide range of parameters for configuring the Tel Profile.
  • Page 389 Trunks that do not implement voice mail [TelProfile_EnableVoiceMailDelay] when voice mail is enabled using the global parameter. Dial Plan Index DialPlanIndex [TelProfile_DialPlanIndex] Swap Tel To IP Phone Numbers SwapTEl2IPCalled&CallingNumbers [TelProfile_SwapTelToIpPhoneNumbers] Digital Cut Through DigitalCutThrough [TelProfile_DigitalCutThrough] Call Priority Mode CallPriorityMode [TelProfile_CallPriorityMode] IP Related Version 7.0 Mediant 3000...
  • Page 390 Mediant 3000 Tel Profile Parameter Global Parameter Coders Group ID CodersGroup0 [TelProfile_CodersGroupID] RTP IP DiffServ PremiumServiceClassMediaDiffServ [TelProfile_IPDiffServ] Signaling DiffServ PremiumServiceClassControlDiffServ [TelProfile_SigIPDiffServ] Enable Early Media EnableEarlyMedia [TelProfile_EnableEarlyMedia] Progress Indicator to IP ProgressIndicator2IP [TelProfile_ProgressIndicator2IP] Channel Dynamic Jitter Buffer Minimum Delay DJBufMinDelay [TelProfile_JitterBufMinDelay]...

  • Page 391: Configuring Ip Profiles

    You can also configure it through ini file (IPProfile).  To configure an IP Profile: Open the IP Profile Settings table (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Version 7.0 Mediant 3000...
  • Page 392 Mediant 3000 Configure an IP Profile according to the parameters described in the table below. Click Add. Table 20-5: IP Profile Settings Table Parameter Descriptions Parameter Description Common Index Defines an index number for the new table row. Note: Each row must be configured with a unique index.
  • Page 393 [4] 4 = Previous four voice payload packets are added to the current packet.  [5] 5 = Previous five voice payload packets are added to the current packet. To use this RTP redundancy level, you need to set the DSPVersionTemplateNumber parameter to 4 or 7. The Version 7.0 Mediant 3000...
  • Page 394 Mediant 3000 Parameter Description coders that support this redundancy level include:  DSPVersionTemplateNumber = 4 (all coders)  DSPVersionTemplateNumber = 7 (only G.729 and iLBC coders) Notes:  When enabled, you can configure the payload type, using the RFC2198PayloadType parameter.
  • Page 395 If the device selects crypto line '2', it includes the MKI parameter in its answer SDP, for example: a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:R1VyA1xV/qwBjkEklu4kSJyl3wCtYeZLq1/QFuxw |2^31|1:1 If the device selects a crypto line that does not contain the MKI Version 7.0 Mediant 3000...
  • Page 396 Mediant 3000 Parameter Description parameter, then the MKI parameter is not included in the crypto line in the SDP answer (even if the SRTPTxPacketMKISize parameter is set to any value other than 0). Note: The corresponding global parameter is EnableSymmetricMKI.
  • Page 397 User's Manual 20. Coders and Profiles Parameter Description AudioCodes sales representative. Notes:  To configure the detection sensitivity level, use the 'AMD Sensitivity Level' parameter.  For more information on the AMD feature, see Answering Machine Detection (AMD) on page 221.
  • Page 398 Mediant 3000 Parameter Description  [-1] Not Configured = Applies the settings of the corresponding global parameter, MediaSecurityBehaviour. [IpProfile_MediaSecurityBehavi  [0] Preferable = (Default) The device initiates encrypted calls to our] this SIP entity. However, if negotiation of the cipher suite fails, an unencrypted call is established.
  • Page 399 For A-law: 'a=gpmd:8 vbd=yes;ecan=on'  For Mu-law: 'a=gpmd:0 vbd=yes;ecan=on'  When the parameter is set to 1, 2, or 3, the parameter FaxTransportMode is ignored.  When the parameter is set to 0, T.38 might still be used without Version 7.0 Mediant 3000...
  • Page 400 Mediant 3000 Parameter Description the control protocol's involvement. To completely disable T.38, set FaxTransportMode to a value other than 1.  For more information on fax transport methods, see Fax/Modem Transport Modes on page 197.  The corresponding global parameter is IsFaxUsed.
  • Page 401  The device sends a SIP 18x response with SDP, allowing the media stream to be established before the call is answered. Notes:  The inclusion of the SDP in the 18x response depends on the Version 7.0 Mediant 3000...
  • Page 402 Mediant 3000 Parameter Description ISDN Progress Indicator (PI). The SDP is sent only if PI is set to 1 or 8 in the received Proceeding, Alerting, or Progress PRI messages. See also the ProgressIndicator2IP parameter, which if set to 1 or 8, the device behaves as if it received the ISDN messages with the PI.
  • Page 403 To enable this function, set the ISDNDuplicateQ931BuffMode parameter to 128 (i.e., duplicate all messages).  To define the format of encapsulated QSIG messages, use the QSIGTunnelingMode parameter.  Tunneling according to ECMA-355 is applicable to all ISDN Version 7.0 Mediant 3000...
  • Page 404 Mediant 3000 Parameter Description variants (in addition to the QSIG protocol).  For more information on QSIG tunneling, see QSIG Tunneling on page 446.  The corresponding global parameter is EnableQSIGTunneling. Copy Destination Number to Enables the device to copy the called number, received in the SIP Redirect Number INVITE message, to the redirect number in the outgoing Q.931...
  • Page 405 Defines the required session expires mode for the SIP entity associated with the IP Profile.  [0] Transparent = (Default) The device does not interfere with [IpProfile_SBCSessionExpiresM the session expires negotiation. ode]  [1] Observer = If the SIP Session-Expires header is present, the Version 7.0 Mediant 3000...
  • Page 406 Mediant 3000 Parameter Description device does not interfere, but maintains an independent timer for each leg to monitor the session. If the session is not refreshed on time, the device disconnects the call.  [2] Not Supported = The device does not allow a session timer with this SIP entity.
  • Page 407 [1] Database URL = Changes the Refer-To header so that the re-routed INVITE is sent through the SBC: Before forwarding the REFER request, the device changes the host part to the device's IP address and adds a special Version 7.0 Mediant 3000...
  • Page 408 Mediant 3000 Parameter Description prefix ("T~&R_") to the Contact user part. The incoming INVITE is identified as a REFER-resultant INVITE according to this special prefix. The device replaces the host part in the Request-URI with the host from the REFER contact. The special prefix remains in the user part for regular classification, manipulation, and routing.
  • Page 409 URI and adds a special user prefix ("T~&R_”), which is then sent to the FEU. The FEU then sends a new INVITE to the device, which the device then sends to the Version 7.0 Mediant 3000...
  • Page 410 Mediant 3000 Parameter Description correct destination.  [2] Handle Locally = The device handles SIP 3xx responses on behalf of the dialog-initiating UA and retries the request (e.g., INVITE) using one or more alternative URIs included in the 3xx response. The device sends the new request to the alternative destination according to the IP-to-IP Routing table (the 'Call Trigger' field must be set to 3xx).
  • Page 411 Sequential, the device sends multiple SDP answers. Remote Early Media RTP Defines whether the destination UA sends RTP immediately after it Detection Mode sends a 18x response.  [0] By Signaling = (Default) Remote client sends RTP Version 7.0 Mediant 3000...
  • Page 412 Mediant 3000 Parameter Description [IpProfile_SBCRemoteEarlyMed immediately after it sends 18x response with early media. The iaRTP] device forwards 18x and RTP as is.  [1] By Media = After sending 18x response, the remote client waits before sending RTP (e.g., Microsoft Lync environment).
  • Page 413 [IpProfile_SBCKeepRoutingHea  [-1] According to Operation Mode = (Default) Depends on the ders] setting of the 'Operation Mode' in the IP Group or SRD table:  B2BUA: Device operates as if the parameter is set to Version 7.0 Mediant 3000...
  • Page 414 Mediant 3000 Parameter Description Disable [0].  Call State-full Proxy: Device operates as if the parameter is set to Enable [1].  [0] Disable = Device removes the Record-Route headers received in requests and responses from the other side, in the outgoing SIP message sent to the SIP entity.
  • Page 415 [2] Restriction and Preference = Performs both Restriction and Preference. Notes:  The parameter is applicable only if Allowed coders are assigned to the IP Profile (using the 'Allowed Coders' or 'Allowed Video Coders Group ID' parameters). Version 7.0 Mediant 3000...
  • Page 416 Mediant 3000 Parameter Description  For more information on the Allowed Coders feature, see Restricting Coders on page 561. Allowed Video Coders Assigns an Allowed Video Coders Group. This defines permitted video coders when forwarding video streams to the SIP entity associated with the IP Profile.
  • Page 417 SDP offer received by the device from one entity is forwarded to the destination entity with its payload type replaced with the configured payload type, and vice versa. The value range is 0 to 200. The default is 0 (i.e., the device Version 7.0 Mediant 3000...
  • Page 418 Mediant 3000 Parameter Description forwards the received payload type as is). Fax Coders Assigns a Coders Group to define the supported fax coders for fax negotiation for the SIP entity associated with the IP Profile. For configuring Coder Groups, see Configuring Coder Groups on page [IpProfile_SBCFaxCodersGroup 385.
  • Page 419 IP Profile sbc-use-silence-supp  [0] Transparent = (Default) Forward as is. [IpProfile_SBCUseSilenceSupp]  [1] Add = Enable silence suppression for each relevant coder listed in the SDP.  [2] Remove = Disable silence suppression for each relevant Version 7.0 Mediant 3000...
  • Page 420 Mediant 3000 Parameter Description coder listed in the SDP. RTP Redundancy Mode Enables interworking RTP redundancy negotiation support between SIP entities in the SDP offer-answer exchange (according sbc-rtp-red-behav to RFC 2198). The parameter defines the device's handling of RTP [IpProfile_SBCRTPRedundancy redundancy for the SIP entity associated with the IP Profile.
  • Page 421  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. SDP Handle RTCP Enables the interworking of the RTCP attribute, 'a=rtcp' (RTCP) in the SDP, for the SIP entity associated with the IP Profile. The...
  • Page 422 Mediant 3000 Parameter Description according to RFC 5124, during RTP profile negotiation between two communicating SIP entities. RFC 5124 defines an RTP profile (S)AVPF for (secure) real-time communications to provide timely feedback from the receivers to a sender. For more information on RFC 5124, see http://tools.ietf.org/html/rfc5124.

  • Page 423: Gateway Application

    Part V Gateway Application...

  • Page 425: 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 7.0 Mediant 3000...

  • Page 426: Call Processing Summary

    Mediant 3000 21.1 Call Processing Summary The device's call processing for Gateway calls is shown in the following flowcharts.  IP-to-Tel Call: Figure 21-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-89730...
  • Page 427 User's Manual 21. Introduction  Tel-to-IP Call: Figure 21-2: Tel-to-IP Call Processing Flowchart Version 7.0 Mediant 3000...
  • Page 428 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 429: Digital Pstn

    For example, 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 7.0 Mediant 3000...
  • Page 430 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 431 Apply to All Trunks to apply the changes to all trunks); the Stop Trunk button replaces Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'. To save the changes to flash memory, see ''Saving Configuration'' on page 672. To reset the device, see ''Resetting the Device'' on page 669. Version 7.0 Mediant 3000...

  • Page 432: Tdm And Timing

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

  • Page 433: Configuring System Timing

    PSTN line clock (see ''Recovering Clock from PSTN Line'' on page 434)  BITS synchronization (see Configuring BITS Synchronization Mode on page 435)  Internal clock (see ''Configuring Internal Clock as Clock Source'' on page 436) Version 7.0 Mediant 3000...

  • Page 434: Recovering Clock From Pstn Line Interface

    Mediant 3000 Note: When the device is used in a ‘non-span’ configuration, the internal device clock must be used (as explained above). 22.2.4.1 Recovering Clock from PSTN Line Interface This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line interface.

  • Page 435: Configuring Bits Synchronization Mode

    When one of the BITS reference clock sources fails, the device automatically switches to the secondary BITS reference source for the device. When a BITS reference clock source with a higher priority returns to service after failure, the device may either revert to the Version 7.0 Mediant 3000...

  • Page 436: Configuring Internal Clock As Clock Source

    Mediant 3000 higher-priority clock source or continue using the lower-priority clock source. When both BITS reference clock sources fail, the device enters into clock holdover.  To configure BITS reference clock source redundancy:  In the System Timing page, set the 'TDM Bus Enable Fallback' parameter (TDMBusEnableFallback) to one of the following: •...

  • Page 437: Configuring Transmission Settings

    T3/DS3 or SONET/SDH). For a description of the parameters related to transmission type, see ''PSTN Parameters'' on page 962. Notes: • Transmission settings are applicable only to Mediant 3000 with TP-6310. • When applying your settings, traffic disturbances may be experienced. ...
  • Page 438 Mediant 3000 Figure 22-5: Transmission Settings Page (SONET/SDH) Figure 22-6: Transmission Settings Page (DS3) Click the channel icon (SDH Link for SONET/SDH, or DS3 Number for DS3), and then define the transmission settings as required. Click Submit. Reset the device and save your settings to the flash memory (see ''Resetting the Device'' on page 669).

  • Page 439: Configuring Cas State Machines

    • The modification of the CAS state machine occurs at the CAS application initialization only for non-default values (-1). • For more information on the CAS Protocol table, refer to the CAS Protocol Table Configuration Note. Version 7.0 Mediant 3000...
  • Page 440 Mediant 3000 Table 22-1: CAS State Machine Parameters Description Parameter Description Generate Digit On Time Generates digit on-time (in msec). [CasStateMachineGenerate The value must be a positive value. The default is -1 (use value from DigitOnTime] CAS state machine). Generate Inter Digit Time Generates digit off-time (in msec).

  • Page 441: Configuring Digital Gateway Parameters

    User's Manual 22. Digital PSTN 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 831. Version 7.0 Mediant 3000...
  • Page 442 Mediant 3000  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab > VoIP menu > Gateway > Digital Gateway > Digital Gateway Parameters). Figure 22-8: Digital Gateway Parameters Page Configure the parameters as required.

  • Page 443: Tunneling Applications

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

  • Page 446: Dsp Pattern Detector

    Mediant 3000 TelProfile_MWIAnalog, TelProfile_MWIDisplay, 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 447 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 7.0 Mediant 3000...

  • Page 448: 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 449: 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 7.0 Mediant 3000...

  • Page 450: 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 451: Isdn Overlap Dialing

    Relevant parameters (described in ''PSTN Parameters'' on page 962):  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 429. Version 7.0 Mediant 3000...

  • Page 452: 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 453 Sending Complete IE, you must configure the ISDNOutCallsBehavior parameter to USER SENDING COMPLETE [2]. For more information on the above mentioned parameters, see PSTN Parameters on page 962. For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 429. Version 7.0 Mediant 3000...

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

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

  • Page 455: 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 applicable only 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 456 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-89730...

  • Page 457: T1 Trunk Enumeration (Sonet Mappings)

    The following table is used for converting internal OC-3 numbering to sequential trunk numbering for API references. The three numbers - STS-1 (K), TUG2 (L) and TU (M) - set the position of the T1 (V-1.5) trunk inside the OC-3 frame. Version 7.0 Mediant 3000...
  • Page 458 Mediant 3000 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 User's Manual Document #: LTRT-89730...
  • Page 459 User's Manual 22. Digital PSTN Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 Version 7.0 Mediant 3000...
  • Page 460 Mediant 3000 Trunk ETSI GR-253 Timeslots STS-1 VT1.5 STS-1 VT1.5 STS-1 VT1.5 User's Manual Document #: LTRT-89730...

  • Page 461: Trunk Groups

    ''Configuring Trunk Group Settings'' on page 463).  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 7.0 Mediant 3000...
  • Page 462 Mediant 3000 Table 23-1: Trunk Group Table Parameter Descriptions Parameter Description From Trunk Defines the starting physical Trunk number in the Trunk Group. The number of listed Trunks depends on the device's hardware configuration. [TrunkGroup_FirstTrunkId] To Trunk Defines the ending physical Trunk number in the Trunk Group. The number of listed Trunks depends on the device's hardware configuration.

  • Page 463: Configuring Trunk Group Settings Table

    Open the Trunk Group Settings table (Configuration tab > VoIP menu > Gateway > Trunk Group > Trunk Group Settings). Click Add; the following dialog box appears: Configure a Trunk Group according to the parameters described in the table below. Click Add. Version 7.0 Mediant 3000...
  • Page 464 Mediant 3000 Table 23-2: Trunk Group Settings Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [TrunkGroupSettings_Index Note: Each row must be configured with a unique index. Name Defines an arbitrary name to easily identify the row. The name represents the Trunk Group in the SIP 'tgrp' parameter in outgoing INVITE messages (according to RFC 4904).
  • Page 465 [5] Per Account = Registrations are sent (or not) to an IP Group, according to the settings in the Account table (see ''Configuring Registration Accounts'' on page 363). An example is shown below of a REGISTER message for registering Version 7.0 Mediant 3000...
  • Page 466 Mediant 3000 Parameter Description endpoint "101" using the registration Per Endpoint mode: REGISTER sip:SipGroupName SIP/2.0 Via: SIP/2.0/UDP 10.33.37.78;branch=z9hG4bKac862428454 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.227.005 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Group table (see ''Configuring IP Groups'' on page 343).
  • Page 467  "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 7.0 Mediant 3000...
  • Page 468 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 469: Manipulation

    1 and "55" for rule index 2, the device uses rule index 1 for numbers that start with 551 and uses rule index 2 for numbers that start with 550, 552, 553, and so on until 559. Version 7.0 Mediant 3000...
  • Page 470 Mediant 3000 However, if you configure the source prefix number as "55" for rule index 1 and "551" for rule index 2, the device applies rule index 1 to all numbers that start with 55, including numbers that start with 551. If the device doesn't find a matching rule, no manipulation is done on the call.
  • Page 471 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Suffix to Add Version 7.0 Mediant 3000...
  • Page 472 Mediant 3000 Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Number of Digits to Leave Presentation Allowed Restricted Table 24-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table row.
  • Page 473 If you selected 'Private' for the NPI, you can select Unknown [0], [NumberType] Level 2 Regional [1], Level 1 Regional [2], PISN Specific [3] or Level 0 Regional (Local) [4].  If you selected 'E.164 Public' for the NPI, you can select Unknown Version 7.0 Mediant 3000...
  • Page 474 Mediant 3000 Parameter Description [0], International [1], National [2], Network Specific [3], Subscriber [4] or Abbreviated [6]. The default is 'Unknown'. Notes:  The parameter is applicable only to number manipulation tables for IP-to-Tel calls.  TON can be used in the SIP Remote-Party-ID header by using the EnableRPIHeader and AddTON2RPI parameters.

  • Page 475: Manipulating Number Prefix

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

  • Page 476: Sip Calling Name Manipulations

    Mediant 3000 24.4 SIP Calling Name Manipulations The calling name manipulation tables lets you configure up to 120 manipulation rules for manipulating the calling name (i.e., caller ID) in SIP messages, for IP-to-Tel and Tel-to-IP calls. Manipulation includes modifying or removing the calling name. The calling name manipulation tables include the following: ...
  • Page 477 100, 101 or 105. You can also use the $ sign to denote calls without a calling number. For a description of available notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 827. Version 7.0 Mediant 3000...
  • Page 478 Mediant 3000 Parameter Description The default value is the asterisk (*) symbol (i.e., any source prefix). Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. You can use special notations for denoting the prefix. For example, to denote calls without a calling name, use the $ sign. For a description of...

  • Page 479: Configuring Redirect Number Ip To Tel

     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. Version 7.0 Mediant 3000...
  • Page 480 Mediant 3000 Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
  • Page 481 Stripped Digits From Left Defines the number of digits to remove from the left of the redirect number prefix. For example, if you enter 3 and the redirect number is 5551234, the new number is 1234. Version 7.0 Mediant 3000...
  • Page 482 Mediant 3000 Parameter Description [_RemoveFromLeft] Stripped Digits From Right Defines the number of digits to remove from the right of the redirect number prefix. For example, if you enter 3 and the redirect number is 5551234, the new number is 5551.

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

    After the above manipulation is done, the device sends the following outgoing SIP 302 response: SIP/2.0 302 Moved Temporarily Via: SIP/2.0/TLS 10.33.45.68;branch=z9hG4bKac54132643;alias From: "MP118 1" <sip:8001@10.33.45.68>;tag=1c54119560 To: <sip:6001@10.33.45.69;user=phone>;tag=1c664560944 Call-ID: 541189832710201115142@10.33.45.68 CSeq: 1 INVITE Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.80A.227.005 Version 7.0 Mediant 3000...

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

    Mediant 3000 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 24.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
  • Page 485 If you selected E.164 Public as the NPI, you can select one of the following:  [0] Unknown  [1] International  [2] National  [3] Network Specific  [4] Subscriber  [6] Abbreviated SIP Phone Context Defines the SIP 'phone-context' URI parameter. [PhoneContext_Context] Version 7.0 Mediant 3000...

  • Page 486: Configuring Release Cause Mapping

    Mediant 3000 24.8 Configuring Release Cause Mapping When a call is disconnected, the reason for the disconnection (or call failure) is sent by the side (IP or Tel) on which the call disconnection occurred. From the IP side, a SIP response is sent (e.g., 406);...

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

    Number changed w/o diagnostic Length required Interworking Request entity too long Interworking Request URI too long Interworking Unsupported media type Service/option not implemented Bad extension Interworking Temporarily unavailable No user responding Call leg/transaction doesn’t 481* Interworking exist Version 7.0 Mediant 3000...

  • Page 488: Isdn-To-Sip Release Cause Mapping

    Mediant 3000 ISDN Release SIP Response Description Description Reason 482* Loop detected Interworking Too many hops Interworking Address incomplete Invalid number format Ambiguous Unallocated number Busy here User busy Not acceptable here Normal, unspecified Server internal error Temporary failure Not implemented...

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

    Table 24-10: Mapping of ISDN Release Reason to SIP Response ISDN Release Description Description Reason Response Unallocated number Not found No route to network Not found No route to destination Not found Channel unacceptable Not acceptable Version 7.0 Mediant 3000...
  • Page 490 Mediant 3000 ISDN Release Description Description Reason Response Call awarded and being delivered in an Server internal error established channel Normal call clearing User busy Busy here No user responding Request timeout No answer from the user Temporarily unavailable Call rejected...

  • Page 491: Configuring Isdn-To-Isdn Release Cause Mapping

    ISDN cause code also appears in the Release Cause Mapping ISDN to SIP table (see ''Configuring ISDN-to-SIP Release Cause Mapping'' on page 488), the device maps it to the corresponding SIP response code, which it sends to the IP side. Version 7.0 Mediant 3000...
  • Page 492 Mediant 3000 Note: If the originally received ISDN cause code is configured in both the Release Cause ISDN to ISDN table and the Release Cause Mapping ISDN to SIP table, the mapping rule with the originally received code in the Release Cause Mapping ISDN to SIP table is ignored;...

  • Page 493: Reason Header

    If the message isn’t a final response, it is translated to a Q.850 cause. • When the Reason header is received twice (i.e., SIP Reason and Q.850), the Q.850 takes precedence over the SIP reason and is sent to the Tel side. Version 7.0 Mediant 3000...

  • Page 494: Numbering Plans And Type Of Number

    Mediant 3000 24.9 Numbering Plans and Type of Number The IP-to-Tel destination or source number manipulation tables allow you to classify numbers by their Numbering Plan Indication (NPI) and Type of Number (TON). The device supports all NPI/TON classifications used in the ETSI ISDN variant, as shown in the table...

  • Page 495: Routing

    To configure general routing parameters: Open the Routing General Parameters page (Configuration tab > VoIP menu > Gateway > Routing > General Parameters). Figure 25-1: Routing General Parameters Page Configure the parameters as required. Click Submit. Version 7.0 Mediant 3000...

  • Page 496: Configuring Tel-To-Ip Routing Rules

    Mediant 3000 25.2 Configuring Tel-to-IP Routing Rules The Tel-to-IP Routing table lets you configure up to 180 Tel-to-IP routing rules. Tel-to-IP routing rules are used to route calls from the Tel side to an IP destination. Configuration of Tel-to-IP routing rules includes two areas: ...
  • Page 497 SRD. As one of the attributes of a SIP Interface is an SRD and as you can configure multiple SIP Interfaces per SRD, the specific SIP Interface not only determines the above-mentioned attributes, but also the SRD for routing the call. Figure 25-2: Locating SRD Version 7.0 Mediant 3000...
  • Page 498 Mediant 3000 Note: When using a proxy server, it is unnecessary to configure routing rules in the Tel-to-IP Routing table, unless you require one of the following: • Fallback (alternative) routing when communication with the proxy server fails. • IP security, whereby the device routes only received calls whose source IP addresses are configured in the table.
  • Page 499 Trunk Group ID 4, the call is sent to the domain "itsp.com".  Rule 5 (block): For all callers (*), if the called phone number prefix is 00, the call is Version 7.0 Mediant 3000...
  • Page 500 Mediant 3000 rejected (IP address 0.0.0.0).  Rule 6, 7, and 8 (Forking Group): For all callers (*), if the called phone number prefix is 100, the call is sent to Rule 7 and 9 (belonging to Forking Group "1"). If their destinations are unavailable and alternative routing is enabled, the call is sent to Rule 8 (Forking Group "2").
  • Page 501 'SIP Group Name' parameter (configured in the IP Group table).  The parameter is used as the 'Serving IP Group' in the Account table for acquiring authentication username/password for this call (see ''Configuring Version 7.0 Mediant 3000...
  • Page 502 Mediant 3000 Parameter Description Registration Accounts'' on page 363).  For defining Proxy Sets, see ''Configuring Proxy Sets'' on page 355. Destination SIP Assigns a SIP Interface to the routing rule. The call is sent to its' destination Interface through this SIP interface.
  • Page 503 To enable Tel-to-IP call forking, set the 'Tel2IP Call Forking Mode' (Tel2IPCallForkingMode) parameter to Enable.  You can configure the device to immediately send the INVITE message to the first member of the Forking Group (as in normal operation) and then Version 7.0 Mediant 3000...
  • Page 504 Mediant 3000 Parameter Description only after a user-defined interval, send the INVITE messages simultaneously to the other members. If the device receives a SIP 4xx or 5xx in response to the first INVITE, it immediately sends INVITEs to all the other members, regardless of the interval.

  • Page 505: Configuring Ip-To-Trunk Group Routing Rules

    Trunk Group is out of service (e.g., physically disconnected). When the physical trunk is disconnected, the device sends the 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 Version 7.0 Mediant 3000...
  • Page 506 Mediant 3000 notifying of the back-to-service state. Notes: • You can configure up to three alternative routing rules per "main" routing rule in the 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 507 Interface associated with the default SRD (Index 0) is used. If there is no valid source IP Group, the call is rejected. Source IP Address Defines the source IP address of the incoming IP call. The IP address can be configured in dotted-decimal notation (e.g., Version 7.0 Mediant 3000...
  • Page 508 Mediant 3000 Parameter Description [PstnPrefix_SourceAddre 10.8.8.5) or as an FQDN. By default, no value is defined. Notes:  If the address is an FQDN, DNS resolution is done according to the DNSQueryType parameter.  The source IP address is obtained from the Contact header in the INVITE message.
  • Page 509 The device routes the call to the [PstnPrefix_CallSetupRul destination according to the routing rule's configured action, only after it esSetId] has performed the Call Setup rules. For configuring Call Setup rules, see ''Configuring Call Setup Rules'' on page 287. Version 7.0 Mediant 3000...

  • Page 510: Configuring A Gateway Routing Policy Rule

    Mediant 3000 25.4 Configuring a Gateway Routing Policy Rule The Gateway Routing Policy table lets you edit the default Gateway Routing Policy rule. The Routing Policy is used for Gateway call routing and defines the following:  LDAP server (LDAP Server Group) for LDAP-based call routing (LDAP and/or Call Setup Rules queries).

  • Page 511: Ip Destinations Connectivity Feature

    Network Connectivity: The device checks the network connectivity of the IP destination using one of the following methods configured by the 'Alt Routing Tel to IP Connectivity Method' parameter: • Ping: The device periodically (every seven seconds) pings the IP destination. Version 7.0 Mediant 3000...
  • Page 512 Mediant 3000 • SIP OPTIONS: The device sends "keep-alive" SIP OPTIONS messages to the IP destination. If the device receives a SIP 200 OK in response, it considers the destination as available. If the destination does not respond to the OPTIONS message, then it is considered unavailable.

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

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

  • Page 514: Alternative Routing Based On Sip Responses

    Mediant 3000  To configure alternative Tel-to-IP routing based on IP connectivity: In the Tel-to-IP Routing table, add alternative Tel-to-IP routing rules for specific calls. In the Routing General Parameters page (Configuration tab > VoIP menu > Gateway > Routing > General Parameters), do the following: Enable alternative routing based on IP connectivity, by setting the 'Enable Alt Routing Tel to IP AltRouting' (Tel2IPEnable) parameter to Enable.
  • Page 515 The steps for configuring alternative Tel-to-IP routing based on SIP response codes are summarized below.  To configure alternative Tel-to-IP routing based on SIP response codes: Configure SIP response codes (call failure reasons) that invoke alternative Tel-to-IP routing: Version 7.0 Mediant 3000...

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

    Mediant 3000 Open the Reasons for Tel-to-IP Alternative Routing page (Configuration tab > VoIP menu > Gateway > Routing > Alternative Reasons > Reasons for Tel- to-IP). Click Add; the following dialog box appears: Figure 25-8: Reasons for Tel-to-IP Alternative Routing Table - Add Row Dialog Box Configure a SIP response code for alternative routing according to the parameters described in the table below.

  • Page 517: Pstn Fallback

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

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

    Mediant 3000 25.7 Alternative Routing for IP-to-Tel Calls The device supports alternative IP-to-Tel call routing, as described in this section. 25.7.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 519: Alternative Routing To An Ip Destination Upon A Busy Trunk

    The device forwards calls using this table only if no alternative IP-to-Tel routing rule has been configured in the Inbound IP Routing table or alternative routing fails and the following reason(s) in the SIP Diversion header of 3xx messages exists:  “out-of-service” - all trunks are unavailable/disconnected Version 7.0 Mediant 3000...
  • Page 520 Mediant 3000  "unavailable": • All trunks are busy or unavailable The following procedure describes how to configure Forward on Busy Trunks through the Web interface. You can also configure it through ini file (ForwardOnBusyTrunkDest).  To configure a Forward on Busy Trunk Destination rule: Open the Forward on Busy Trunk Destination table (Configuration tab >...

  • Page 521: 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 7.0 Mediant 3000...
  • Page 522 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 523: Configuring Dtmf And Dialing

    Tel side by the device. When the number of collected digits reaches the maximum (or a digit map pattern is matched), the device uses these digits for the called destination number. Version 7.0 Mediant 3000...
  • Page 524 Mediant 3000  Inter-digit timeout expires (e.g., for open numbering schemes). This is defined using the TimeBetweenDigits parameter. This is the time that the device waits between each received digit. When this inter-digit timeout expires, the device uses the collected digits to dial the called destination number.

  • Page 525: 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 683. Version 7.0 Mediant 3000...

  • Page 526: Interworking Keypad Dtmfs For Sip-To-Isdn Calls

    Mediant 3000 26.2 Interworking Keypad DTMFs for SIP-to-ISDN Calls The device can interwork DTMF tones received from the IP to the PSTN, using the ISDN Keypad Facility information element (IE) in Q.931 INFORMATION messages. This feature is applicable only to the Euro ISDN variant (User side).

  • Page 527: 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 672. Version 7.0 Mediant 3000...

  • Page 528: 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 529: Consultation Transfer For Qsig Path Replacement

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

  • Page 530: Call Forward

    Mediant 3000 Note: Manipulation using the ManipulateIP2PSTNReferTo parameter does not affect IP-to-Trunk Group routing rules. 27.3 Call Forward The device supports Call Deflection (ETS-300-207-1) for Euro ISDN and QSIG (ETSI TS 102 393) for Network and User sides, which provides IP-ISDN interworking of call forwarding (call diversion) when the device receives a SIP 302 response.

  • Page 531: Message Waiting Indication

    The SIP NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. When a change in the status occurs (e.g., a new voice message is waiting or the user has retrieved a message from the voice mail), the PBX initiates an ISDN Setup Version 7.0 Mediant 3000...

  • Page 532: Emergency E911 Phone Number Services

    Mediant 3000 message with Facility IE containing an MWI Activate request, which includes the new number of voice messages waiting for the user. The device forwards this information to the softswitch by sending a SIP NOTIFY. Depending on PBX support, the MWIInterrogationType parameter can be configured to handle these MWI Interrogation messages in different ways.

  • Page 533: Multilevel Precedence And Preemption

    Table 27-1: 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 7.0 Mediant 3000...
  • Page 534 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 535: Mlpp Preemption Events In Sip Reason Header

    SIP:BYE - If an active call is being preempted by another call • CANCEL - If an outgoing call is being preempted by another call • 480 (Temporarily Unavailable), 486 (User Busy), 488 (Not Acceptable Here) - Due to incoming calls being preempted by another call. Version 7.0 Mediant 3000...

  • Page 536: Precedence Ring Tone

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

  • Page 537: Advice Of Charge Services For Euro Isdn

    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 538 Mediant 3000  To configure AOC: Make sure that the PSTN protocol for the trunk line is Euro ISDN and set to network side. Make sure that the date and time of the device is correct. For accuracy, it is recommended to use an NTP server to obtain the date and time.

  • Page 539: Configuring Charge Codes

    Cost Routing > Charge Codes). Click Add; the following dialog box appears: Figure 27-2: Charge Codes Table - Add Row Dialog Box Configure a Charge Code according to the parameters described in the table below. Click Add. Version 7.0 Mediant 3000...
  • Page 540 Mediant 3000 Table 27-4: Charge Codes Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [ChargeCode_Index] Note: Each row must be configured with a unique index. End Time (1 - 4) Defines the end of the time period in a 24 hour format, hh. For example, "04"...

  • Page 541: Configuring Voice Mail

    Open the Voice Mail Settings page (Configuration tab > VoIP menu > Gateway > Advanced Applications > Voice Mail Settings). Figure 27-3: Voice Mail Settings Page Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 672. Version 7.0 Mediant 3000...

  • Page 542: Converting Accented Characters From Ip To Tel

    Mediant 3000 27.11 Converting Accented Characters from IP to Tel The Char Conversion table lets you configure up to 40 Character Conversion rules. A Character Conversion rule maps (converts) accented characters (Unicode / UTF-8) received from the IP side into simple ASCII characters (ISO-8859) for sending to the Tel side.
  • Page 543 The valid value is a string of up to four characters. [CharConversion_Conver tedOutput] The valid value is up to four ASCII characters. This can include any ASCII character - alphanumerical (e.g., a, A, 6) and/or symbols (e.g., !, ?, _, &). Version 7.0 Mediant 3000...
  • Page 544 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 545: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 547: Sbc Overview

    For example, IP addresses of ITSPs' equipment (e.g. proxies, gateways, and application servers) can be hidden from outside parties. The device's topology hiding is provided by implementing back-to-back user agent (B2BUA) leg routing: Version 7.0 Mediant 3000...
  • Page 548 Mediant 3000 • Strips all incoming SIP Via header fields and creates a new Via value for the outgoing message. • Each leg has its own Route/Record Route set. • User-defined manipulation of SIP To, From, and Request-URI host names.

  • Page 549: B2Bua And Stateful Proxy Operating Modes

    IP Profile parameters (see ''Configuring IP Profiles'' on page 391):  IpProfile_SBCRemoteRepresentationMode: Contact and Record-Route headers  IpProfile_SBCKeepVIAHeaders: Via headers  IpProfile_SBCKeepUserAgentHeader: User-Agent headers  IpProfile_SBCKeepRoutingHeaders: Record-Route headers  IpProfile_SBCRemoteMultipleEarlyDialogs: To-header tags Version 7.0 Mediant 3000...
  • Page 550 Mediant 3000 Thus, the Stateful Proxy mode provides full SIP transparency (no topology hiding) or asymmetric topology hiding. Below is an example of a SIP dialog-initiating request when operating in Stateful Proxy mode for full transparency, showing all the incoming SIP headers retained in the outgoing INVITE message.
  • Page 551 IP PBX. The configuration is done using IP Groups and SRDs. • If Stateful Proxy mode is used only due to the debugging benefits, it is recommended to configure the device to only forward the Call-ID header unchanged Version 7.0 Mediant 3000...

  • Page 552: Call Processing Of Sip Dialog Requests

    Mediant 3000 28.3 Call Processing of SIP Dialog Requests The device processes incoming SIP dialog requests (SIP methods) such as INVITE, SUBSCRIBE, OPTIONS, REFER, INFO, UNSOLICITED NOTIFY, MESSAGE, and REGISTER. The process is summarized in the following figure and subsequently...
  • Page 553 For more information, see Stage 3. Applying IP-to-IP Outbound Manipulation: Depending on configuration, the device can apply an IP-to-IP Outbound Manipulation rule to the outbound dialog. This manipulates the user part of the Request-URI for source (e.g., in the SIP From Version 7.0 Mediant 3000...

  • Page 554: User Registration

    Mediant 3000 header) or destination (e.g., in the SIP To header) or calling name in the outbound SIP dialog. The manipulation rule is associated with the dialog, by configuring the rule with incoming matching characteristics such as source IP Group and destination host name.

  • Page 555: Classification And Routing Of Registered Users

    Request-URI in the INVITE message the device must search in the registration database:  Only by entire Request-URI (user@host), for example, "4709@joe.company.com".  By entire Request-URI, but if not found, by the user part of the Request-URI, for example, "4709". Version 7.0 Mediant 3000...

  • Page 556: General Registration Request Processing

    Mediant 3000 When an incoming INVITE is received for routing to a user and the user is located in the registration database, the device sends the call to the user's corresponding contact address specified in the database. Note: If the Request-URI contains the "tel:" URI or "user=phone" parameter, the device searches only for the user part.

  • Page 557: Registration Restriction Control

    SDP offer-answer mechanism. This is done mainly to anchor the media to the device (default) and also to change the negotiated media type, if configured. Some of the media handling features, which are described later in this section, include the following:  Media anchoring (default)  Direct media Version 7.0 Mediant 3000...

  • Page 558: Media Anchoring

    Mediant 3000  Audio coders restrictions  Audio coders transcoding  RTP-SRTP transcoding  DTMF translations  Fax translations and detection  Early media and ringback tone handling  Call hold translations and held tone generation  NAT traversal ...

  • Page 559: Direct Media

    ''Media Anchoring'' on page 558. Direct media offers the following benefits:  Saves network bandwidth  Reduces the device's CPU usage (as there is no media handling)  Avoids interference in SDP negotiation and header manipulation on RTP/SRTP Version 7.0 Mediant 3000...
  • Page 560 Mediant 3000 Direct media is typically implemented for calls between users located in the same LAN or domain, and where NAT traversal is not required and other media handling features such as media transcoding is not required. The following figure provides an example of direct media between LAN IP phones, while SIP signaling continues to traverse the device between LAN IP phones and the hosted WAN IP-PBX.

  • Page 561: Restricting Audio Coders

    G.711 is listed first, and sends the SIP message containing only the G.711 and G.729 coders in the SDP. The allowed coders are configured in the Allowed Audio Coders Group table. For more information, see ''Configuring Allowed Audio Coder Groups'' on page 591. Version 7.0 Mediant 3000...

  • Page 562: Coder Transcoding

    Mediant 3000 Note: If you assign the SIP entity an Allowed Coders Group for coder restriction and a Coders Group for extension coders (i.e., voice transcoding), the allowed coders take precedence over the extension coders. In other words, if an extension coder is not listed as an allowed coder, the device does not add the extension coder to the SDP offer.
  • Page 563 On the inbound leg for the incoming SDP offer: The device allows and keeps the coders in the SDP that also appear in the Allowed Audio Coders Group for coder restriction (i.e., G.711 and G.729). It changes the order of listed coders in the SDP so Version 7.0 Mediant 3000...
  • Page 564 Mediant 3000 that G.711 is listed first. The device removes the coders (i.e., G.723) from the SDP that do not appear in the Allowed Audio Coders Group for coder restriction. m=audio 6050 RTP/AVP 0 8 18 96 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000...

  • Page 565: Transcoding Mode

    Extension coders are added after the Allowed coders according to their order in the Allowed Coders Group, or the Allowed and Extension coders are arranged according to their position in the Allowed Coders Group. Version 7.0 Mediant 3000...

  • Page 566: Srtp-Rtp And Srtp-Srtp Transcoding

    Mediant 3000 28.5.7 SRTP-RTP and SRTP-SRTP Transcoding The device supports transcoding between SRTP and RTP. The device can also enforce specific SBC legs to use SRTP and/or RTP. The device’s handling of SRTP/RTP is configured using the IP Profile parameter, SBCMediaSecurityBehaviour, which provides the following options: ...

  • Page 567: Interworking Rtp Redundancy

    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. These coders include G.711 (A-Law or Mu-Law), VBD (G.711 A-Law or G.711 Mu-Law), and T38. Version 7.0 Mediant 3000...

  • Page 568: Limiting Sbc Call Duration

    Mediant 3000 Fax configuration is done in the Coder Group Settings table and IP Profile table. The Coder Group Settings table defines the supported coders, which is assigned to the IP Profile associated with the SIP entity. The IP Profile table also defines the negotiation method...

  • Page 569: User Authentication Based On Radius

    'Authentication Mode' parameter in the IP Group table (see ''Configuring IP Groups'' on page 343). Note: This feature is applicable only to Mediant 3000 in Simplex mode. 28.8.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.

  • Page 570: Interworking Sip Signaling

    Mediant 3000 To configure this feature, set the SBCServerAuthMode ini file parameter to 2. 28.9 Interworking SIP Signaling The device supports interworking of SIP signaling messages to ensure interoperability between communicating SIP UAs or entities. This is critical in network environments where the UAs on opposing SBC legs have different SIP signaling support.

  • Page 571: Local Handling Of Sip 3Xx

    Routing table rules. (where the 'Call Trigger' field is set to 3xx). It is also possible to specify the IP Group that sent the 3xx request as matching criteria for the re-routing rule in this table ('ReRoute IP Group ID' field). Version 7.0 Mediant 3000...

  • Page 572: Interworking Sip Diversion And History-Info Headers

    Mediant 3000 28.9.2 Interworking SIP Diversion and History-Info Headers This device can be configured to interwork between the SIP Diversion and History-Info headers. This is important, for example, to networks that support the Diversion header but not the History-Info header, or vice versa. Therefore, mapping between these headers is crucial for preserving the information in the SIP dialog regarding how and why (e.g., call...

  • Page 573: Interworking Sip Prack Messages

    28.9.6 Interworking SIP Early Media The device supports early media. Early media is when the media flow starts before the SIP call is established (i.e., before the 200 OK response). This occurs when the first SDP offer- Version 7.0 Mediant 3000...
  • Page 574 Mediant 3000 answer transaction completes. The offer-answer options can be included in the following SIP messages:  Offer in first INVITE, answer on 180, and no or same answer in the 200 OK  Offer in first INVITE, answer on 180, and a different answer in the 200 OK (not standard) ...
  • Page 575 IP Profile parameters, 'Remote Early Media RTP Detection Mode', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Figure 28-7: SBC Early Media RTP 18x without SDP Version 7.0 Mediant 3000...

  • Page 576: Interworking Sip Re-Invite Messages

    Mediant 3000 Figure 28-8: Early Media RTP - SIP 18x with SDP 28.9.7 Interworking SIP re-INVITE Messages The device supports interworking re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs. The device does not forward re-INVITE requests to IP Groups that do not support it.

  • Page 577: Interworking Sip Update Messages

    This is configured by the IP Profile parameter, 'SBC Play Held Tone'.  Interworking generation of held tone where the device generates the tone to the held party instead of the call hold initiator. This is configured by the IP Profile parameter, Version 7.0 Mediant 3000...

  • Page 578: Interworking Sip Via Headers

    Mediant 3000 'SBC Reliable Held Tone Source'. For configuring IP Profiles, see ''Configuring IP Profiles'' on page 391. 28.9.12 Interworking SIP Via Headers The device supports the interworking of SIP Via headers between SIP entities. For the outgoing message sent to a SIP entity, the device can remove or retain all the Via headers received in the incoming SIP request from the other side.

  • Page 579: Interworking Sip To-Header Tags In Multiple Sdp Answers

    The device supports the interworking of in-dialog, SIP Contact and Record-Route headers between SIP entities. Employing IP Profiles, you can configure this interworking feature per entity, using IpProfile_SBCRemoteRepresentationMode parameter (see ''Configuring IP Profiles'' on page 391). Version 7.0 Mediant 3000...

  • Page 580: Mediant

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

  • Page 581: Enabling The Sbc Application

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'SBC Application' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 7.0 Mediant 3000...
  • Page 582 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 583: Configuring General Sbc Settings

    The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP clients behind the device, the call dialog information sent by the application server reflects Version 7.0 Mediant 3000...
  • Page 584 Mediant 3000 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. The device resolves this by replacing the call identifiers received from the application server with the correct call identifiers (e.g., user A and user B).
  • Page 585 User's Manual 30. Configuring General SBC Settings sip:cjones@example.net </identity> <target uri="sip:line3@host3.example.net"> <param pname="actor" pval="attendant"/> <param pname="automaton" pval="false"/> </target> </remote> </dialog> </dialog-info> Version 7.0 Mediant 3000...
  • Page 586 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 587: Configuring Admission Control

    (e.g., of 200). Requests that reach the user-defined call limit (maximum concurrent calls and/or call rate) are sent to an alternative route, if configured in the IP-to-IP Routing table. If no alternative Version 7.0 Mediant 3000...
  • Page 588 Mediant 3000 routing rule is located, the device rejects the SIP request with a SIP 480 "Temporarily Unavailable" response. Note: The device applies the CAC rule for the incoming leg immediately after the Classification process. If the call/request is rejected at this stage, no routing is performed.
  • Page 589 CAC rule.  The total reserved call capacity configured for all the CAC rules must be within the device's total call capacity support. Limit Defines the maximum number of concurrent SIP dialogs per IP Group, Version 7.0 Mediant 3000...
  • Page 590 Mediant 3000 Parameter Description SIP Interface or SRD. You can also use the following special values:  [SBCAdmissionControl_L [0] 0 = Block all these dialogs. imit]  [-1] -1 = (Default) Unlimited. Limit Per User Defines the maximum number of concurrent SIP dialogs per user belonging to the specified IP Group, SIP Interface or SRD.

  • Page 591: Configuring Coder Groups

    The Allowed Audio Coders Group for coder restriction takes precedence over the Coder Group for extension coders. In other words, if an extension coder is not listed as an allowed coder, the device does not add the extension coder to the SDP offer. Version 7.0 Mediant 3000...

  • Page 592: Configuring Allowed Video Coder Groups

    Mediant 3000 The following procedure describes how to configure Allowed Audio Coder Groups through the Web interface. You can also configure it through ini file (AllowedCodersGroup).  To configure an Allowed Coders Group: Open the Allowed Audio Coders Group page (Configuration tab > VoIP menu > SBC >...
  • Page 593 The valid value for user-defined coders is a string of up to 25 characters (case-insensitive). For example, [AllowedVideoCodersGroupX_Na "WOW.789" (but without quotes). Note: Each coder type can be configured only once per Allowed Video Coders Group. Version 7.0 Mediant 3000...
  • Page 594 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 595: Routing Sbc

    SIP dialog arrived from a registered user. The device searches the database for a user that matches the address-of-record (AOR) and Contact of the incoming SIP message: Version 7.0 Mediant 3000...
  • Page 596 Mediant 3000 • Compares the SIP Contact header to the contact value of the user in the database. • Compares the URL in the SIP P-Asserted-Identity/From header to the registered address-of-record (AOR) in the database. If the device finds a matching registered user, it classifies the user to the IP Group associated with the user in the database.
  • Page 597 The following procedure describes how to configure Classification rules through the Web interface. You can also configure it through ini file (Classification).  To configure a Classification rule: Open the Classification table (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Version 7.0 Mediant 3000...
  • Page 598 Mediant 3000 Click Add; the following dialog box appears: Figure 33-2: Classification Table - Add Row Dialog Box Configure the Classification rule according to the parameters described in the table below. Click Add. Table 33-1: Classification Table Parameter Descriptions Parameter...
  • Page 599 [Classification_SrcHost] configure the SIP header from where the device obtains the source URI, in the IP Group table ('Source URI Input' parameter). For more information on how the device obtains this URI, see ''Call Processing of Version 7.0 Mediant 3000...
  • Page 600 Mediant 3000 Parameter Description SIP Dialog Requests'' on page 552. The default is the asterisk (*) symbol, which represents any source host prefix. Note: For REGISTER requests, the source URI is obtained from the To header. Destination Username Defines the prefix of the destination Request-URI user part as a matching Prefix characteristic for the incoming SIP dialog.

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

    Route: <sip:2000@10.10.10.10.10>,<sip:300@10.10.10.30> Supported: em,100rel,timer,replaces P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group Prefix Username Prefix 1111 2000 10.10.10.10 Version 7.0 Mediant 3000...

  • Page 602: Configuring Message Condition Rules

    Mediant 3000 In the IP Group table, add the following IP Groups: Index Source URI Input Destination URI Input P-Called-Party-ID Route In this example, a match exists only for Classification Rule #1. This is because the source (1111) and destination (2000) username prefixes match those in the INVITE's P-Called-...

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

    Note: User and host parts must be enclosed in single quotes. 33.3 Configuring SBC IP-to-IP Routing The IP-to-IP Routing table lets you configure up to 200 SBC IP-to-IP routing rules. Configuration of IP-to-IP routing rules includes two areas: Version 7.0 Mediant 3000...
  • Page 604 Mediant 3000  Rule: Defines the characteristics of the incoming SIP dialog message (e.g., IP Group from which the message is received).  Action: Defines the action that is done if the incoming call matches the characteristics of the rule (i.e., routes the call to the specified destination).
  • Page 605 SIP response code (i.e., 4xx, 5xx, and 6xx SIP responses) configured in the SBC Alternative Routing Reasons table (see ''Configuring SIP Response Codes for Alternative Routing Reasons'' on page 614). ♦ SIP 408 Timeout or no response (after timeout). Version 7.0 Mediant 3000...
  • Page 606 Mediant 3000 • The DNS resolution includes IP addresses that the device has yet to try (for the current call). Messages are re-routed with the same SIP Call-ID and CSeq header fields (increased by 1).  Re-routing of SIP requests: This table enables you to configure "re-routing" rules of requests (e.g., INVITEs) that the device sends upon receipt of SIP 3xx responses or...
  • Page 607 Assigns an SBC Routing Policy to the rule. The SBC Routing Policy associates the rule with an SRD(s). The SBC Routing Policy also defines default LCR settings as well as the LDAP servers used if the routing rule [IP2IPRouting_RoutingPol Version 7.0 Mediant 3000...
  • Page 608 Mediant 3000 Parameter Description icyName] is based on LDAP routing (and Call Setup Rules). If only one SBC Routing Policy is configured in the SBC Routing Policy table, the SBC Routing Policy is automatically assigned. If multiple SBC Routing Policies are configured, no value is assigned.
  • Page 609 For available notations, see ''Dialing Plan Notation for Routing and [IP2IPRouting_DestUsern Manipulation'' on page 827. amePrefix] The default is the asterisk (*) symbol (i.e., any prefix). If this rule is not required, leave this field empty. Version 7.0 Mediant 3000...
  • Page 610 Mediant 3000 Parameter Description Note: If you need to route calls of many different destination URI user names to the same destination, you can use tags (see 'Destination Tags' parameter below) instead of this parameter. Destination Host Defines the host part of the incoming SIP dialog’s destination URI (usually the Request-URI).
  • Page 611 This option is also used for alternative routing of an IP-to-IP route to the PSTN. In such a case, the IP-to-Tel routing rule must also be configured with the same call matching characteristics as this SBC Version 7.0 Mediant 3000...
  • Page 612 Mediant 3000 Parameter Description IP-to-IP routing rule.  [9] Routing Server = Device sends a request to a third-party routing server for an appropriate destination (next hop) for the matching call.  [10] All Users = Device checks whether the Request-URI (i.e., destination user) in the incoming INVITE is registered in its' users’...
  • Page 613 [1] Forking = Call uses this route and the routes of Forking Group members, if configured (in the rows below it). Note: Each Forking Group can contain up to 20 members. In other words, up to 20 routing rules can be configured for the same Forking Group. Version 7.0 Mediant 3000...

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

    Mediant 3000 Parameter Description Cost Group Assigns a Cost Group to the routing rule for determining the cost of the call. By default, no value is defined (None). [IP2IPRouting_CostGroup] For configuring Cost Groups, see ''Configuring Cost Groups'' on page 275.
  • Page 615 Defines an index number for the new table row. [SBCAlternativeRoutingR Note: Each row must be configured with a unique index. easons_Index] Release Cause Defines a SIP response code for triggering the device's alternative routing mechanism. [SBCAlternativeRoutingR easons_ReleaseCause] Version 7.0 Mediant 3000...

  • Page 616: Configuring Sbc Routing Policy Rules

    Mediant 3000 33.5 Configuring SBC Routing Policy Rules The SBC Routing Policy table lets you configure up to 33 SBC Routing Policy rules. A Routing Policy determines the routing and manipulation (inbound and outbound) rules per SRD in a multiple SRD configuration topology. The Routing Policy also configures the following: ...
  • Page 617 SRD is used. However, if a Routing Policy is configured in the Classification table, it overrides the Routing Policy assigned to the SRD. The regular manipulation (inbound and outbound) and routing processes are done according to the associated Routing Policy. Version 7.0 Mediant 3000...
  • Page 618 Mediant 3000 Notes: • The Classification table is used only if classification by registered user in the device's users registration database or by Proxy Set fails. • If the device receives incoming calls (e.g., INVITE) from users that have already...
  • Page 619 Therefore, a call of 1 minute cost 7 units. Therefore, for calls under one minute, "Weekend A" carries the lower cost. However, if the average call duration is more than one minute, "Weekend B" carries the lower cost. Version 7.0 Mediant 3000...
  • Page 620 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 621: Sbc Manipulations

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

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

    This manipulation can be done for source and destination IP Groups (see ''Configuring IP Groups'' on page 343). The following procedure describes how to configure IP-to-IP Inbound Manipulation rules through interface. also configure through file (IPInboundManipulation). Version 7.0 Mediant 3000...
  • Page 624 Mediant 3000  To configure an IP-to-IP Inbound Manipulation rule: Open the IP to IP Inbound Manipulation table (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP-to-IP Inbound). Click Add; the following dialog box appears: Figure 34-2: IP to IP Inbound Manipulation Table - Add Row Dialog Box Configure the IP-to-IP inbound manipulation rule according to the parameters described in the table below.
  • Page 625 827. Destination Host Defines the destination SIP URI host name - full name, typically located in the Request URI and To headers. [IPInboundManipulation The default is the asterisk (*) symbol (i.e., any destination host name). _DestHost] Version 7.0 Mediant 3000...
  • Page 626 Mediant 3000 Parameter Description Request Type Defines the SIP request type to which the manipulation rule is applied.  [0] All = (Default) All SIP messages. [IPInboundManipulation  [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE. _RequestType] ...

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

    The following procedure describes how to configure IP-to-IP Outbound Manipulation rules through interface. also configure through file (IPOutboundManipulation).  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation table (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP-to-IP Outbound). Version 7.0 Mediant 3000...
  • Page 628 Mediant 3000 Click Add; the following dialog box appears: Figure 34-3: IP to IP Outbound Manipulation Table- Add Row Dialog Box Configure an IP-to-IP outbound manipulation rule according to the parameters described in the table below. Click Add. Table 34-2: IP to IP Outbound Manipulation Table Parameter Description...
  • Page 629 The default value is the asterisk (*) symbol (i.e., any destination username prefix). The prefix can be a single digit or a range of digits. For [IPOutboundManipulation available notations, see ''Dialing Plan Notation for Routing and _DestUsernamePrefix] Version 7.0 Mediant 3000...
  • Page 630 Mediant 3000 Parameter Description Manipulation'' on page 827. Note: If you need to manipulate calls of many different destination URI user names, you can use tags (see 'Destination Tags' parameter below) instead of this parameter. Destination Host Defines the destination SIP URI host name - full name, typically located in the Request-URI and To headers.
  • Page 631 Determines user privacy handling (i.e., restricting source user identity in outgoing SIP dialogs).  [0] Transparent = (Default) No intervention in SIP privacy. [IPOutboundManipulation  [1] Don't change privacy = The user identity remains the same as in _PrivacyRestrictionMode] Version 7.0 Mediant 3000...
  • Page 632 Mediant 3000 Parameter Description the incoming SIP dialog. If a restricted number exists, the restricted presentation is normalized as follows:  From URL header: anonymous@anonymous.invalid.  If a P-Asserted-Identity header exists (either in the incoming SIP dialog or added by the device), a Privacy header is added with the value "id".

  • Page 633: Configuring Dial Plans

    The Dial Plan itself is a set of dial plan rules having the following attributes:  Prefix: The prefix is matched against the source and/or destination number of the incoming SIP dialog-initiating request. Version 7.0 Mediant 3000...
  • Page 634 Mediant 3000  Tag: The tag corresponds to the matched prefix of the source and/or destination number and is the categorization result. You can use various syntax notations for configuring the prefix numbers in dial plan rules. You can configure the prefix as a complete number (all digits) or as a partial number using some digits and various syntax notations (patterns) to allow the device to match a dial pan rule for similar source and/or destination numbers.
  • Page 635 [DialPlans_Name] In the Dial Plan table, select the row for which you want to configure dial plan rules, and then click the Dial Plan Rule link located below the table; the Dial Plan Rule table appears. Version 7.0 Mediant 3000...
  • Page 636 Mediant 3000 Click New; the following dialog box appears: Figure 35-3: Dial Plan Rule Table Configure a dial plan rule according to the parameters described in the table below. Click New, and then save ("burn") your settings to flash memory.

  • Page 637: Importing And Exporting Dial Plans

    Plans 1 and 2, the rules of Dial Plan 1 in the imported file replace the rules of Dial Plan 1 on the device, and the rules of Dial Plan 2 on the device are deleted (the Dial Plan itself remains). The Dial Plan names in the imported file must be Version 7.0 Mediant 3000...

  • Page 638: Creating Dial Plan Files

    Mediant 3000 identical to the existing Dial Plan names on the device; otherwise, the specific Dial Plan is not imported. For creating Dial Plans in a CSV file for import, see 'Creating Dial Plan Files for Import' on page 638.
  • Page 639 'Source Tags' parameter (IP2IPRouting_SrcTags): tag denoting the calling user • 'Destination Tags' parameter (IP2IPRouting_DestTags): tag denoting the called user An example of a routing rule using a destination tag "LOC" is shown below: Figure 35-4: Assigning Tag to Routing Rule Version 7.0 Mediant 3000...

  • Page 640: Dial Plan Backward Compatibility

    Mediant 3000 35.3.1 Dial Plan Backward Compatibility Note: This section is for backward compatibility only. It is recommended to migrate your Dial Plan configuration to the latest Dial Plan feature (see 'Using Dial Plan Tags for IP-to-IP Routing' on page 688).
  • Page 641 Click the Action tab, and then in the 'Remove from Left' or 'Remove from Right' fields (depending on whether you added the tag at the beginning or end of the URI user part, respectively), enter the number of characters making up the tag. Version 7.0 Mediant 3000...

  • Page 642: Using Dial Plan Tags For Outbound Manipulation

    Mediant 3000 35.4 Using Dial Plan Tags for Outbound Manipulation You can use Dial Plan tags to denote source and/or destination URI user names in Outbound Manipulation rules in the IP-to-IP Outbound Manipulation table. The following procedure describes how to configure Outbound Manipulation based on tags.

  • Page 643: Advanced Sbc Features

    To configure SBC emergency call preemption: In the Message Condition table, configure a Message Condition rule to identify incoming emergency calls. See above for examples. For more information on Message Conditions, see ''Configuring Message Condition Rules'' on page 602. Version 7.0 Mediant 3000...

  • Page 644: Emergency Call Routing Using Ldap To Obtain Elin

    Mediant 3000 Open the SBC General Settings page (Configuration tab > VoIP > SBC > SBC General Settings), and then scroll down the page to the Call Priority and Preemption group: Figure 36-2: Configuring Emergency SBC Call Preemption From the 'SBC Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable the SBC call preemption feature.

  • Page 645: Call Forking

    (UA), to a proxy server and the proxy server then forks the INVITE request to multiple UAs. Several UAs may answer and the device may therefore, receive several replies (responses) for the single INVITE request. Each response has a different 'tag' value in the SIP To header. Version 7.0 Mediant 3000...

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

    Mediant 3000 During call setup, forked SIP responses may result in a single SDP offer with two or more SDP answers. The device "hides" all the forked responses from the INVITE-initiating UA, except the first received response ("active" UA) and it forwards only subsequent requests and responses from this active UA to the INVITE-initiating UA.

  • Page 647: Call Survivability

    36.4.2 BroadSoft's Shared Phone Line Call Appearance for SBC Survivability The device can provide redundancy for BroadSoft's Shared Call Appearance feature. When the BroadSoft application server switch (AS) fails or does not respond, or when the Version 7.0 Mediant 3000...
  • Page 648 Mediant 3000 network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients. This feature is supported by configuring a primary extension and associating it with secondary extensions (i.e., shared lines) so that incoming calls to the primary extension also ring at the secondary extensions.

  • Page 649: Call Survivability For Call Centers

    The SBC can handle a sequence of up to five users, after which the session is timed out and the call is dropped. Figure 36-6: Normal Operation in Call Center Application Version 7.0 Mediant 3000...
  • Page 650 Mediant 3000 Figure 36-7: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Group table (see ''Configuring IP Groups'' on page 343), add IP Groups for the following entities: • TDM Gateway (Server-type IP Group). This entity forwards the customer calls through the device to the Application server.

  • Page 651: Survivability Mode Display On Aastra Ip Phones

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

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

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

  • Page 653: High-Availability Mode

    Part VII High-Availability Mode...

  • Page 655: Ha Overview

    User's Manual 37. 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 656: 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 657 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 7.0...

  • Page 658: Blade Failure Detection

    Mediant 3000 37.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 659: 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 660 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 38-3: Example of Multiple Interfaces for Mediant 3000 HA in Interface Table Primary / Prefix Applicatio Interfac...

  • Page 661: Physical Network Separation Mode

    The following figure illustrates the port allocation: Figure 39-1: Dedicated Port per Application Type in Physical Network Separation  Dedicated Port for OAMP and Dedicated Port for Media and Control: • Media and Control: Gigabit Ethernet port on RTM-8410. Version 7.0 Mediant 3000...

  • Page 662: Configuring Physical Network Separation

    OAMP: 10/100BaseT Ethernet ports labeled 2A (bottom PEM module) and 2B (top PEM module) 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 663: 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 664 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 665: 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 SAT (SA/M3K Alarms, Status and Synchronization) blades, as shown in the figure below: Figure 40-1: Home Page for Mediant 3000 HA Device Table 40-1: Indications of HA on Home Page Item #...
  • Page 666 Mediant 3000  "Not Operational: Global IP Not Defined": Global IP address is not configured  "Operational: Internal Error": Internal error in HA mode  "Operational: SA Card Error": Malfunction in SAT blade  "Operational: RTM Card Error": Malfunction in RTM blade The Active blade is indicated by the following: ...

  • Page 667: Maintenance

    Part VIII Maintenance...

  • Page 669: Basic Maintenance

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

  • Page 671: Remotely Resetting Device Using Sip Notify

    Under the Misc Parameters group, set the 'SIP Remote Rest' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. 41.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 672: Saving Configuration

    Mediant 3000 Click the LOCK button; a confirmation message box appears requesting you to confirm device lock. 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.

  • Page 673: High Availability Maintenance

    When resetting the Redundant unit, the HA mode becomes temporarily unavailable.  To reset the Redundant unit: Open the High Availability Maintenance page: • Navigation menu tree: Maintenance tab > Maintenance menu > High Availability Maintenance Version 7.0 Mediant 3000...
  • Page 674 Mediant 3000 • Toolbar: Click the Device Actions button, and then choose Reset Redundant Figure 42-2: High Availability Maintenance Page Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK. User's Manual Document #: LTRT-89730...

  • Page 675: Channel Maintenance

    The Trunk Group Settings table provides the following read-only fields related to locking and unlocking of a Trunk Group:  'Admin State': Displays the administrators state - "Locked" or "Unlocked"  'Status': Displays the current status of the channels in the Trunk Group: Version 7.0 Mediant 3000...
  • Page 676 Mediant 3000 • "In Service": Indicates that all channels in the Trunk Group are in service, for example, when the Trunk Group is unlocked or Busy Out state cleared (see the EnableBusyOut parameter for more information). • "Going Out Of Service": Appears as soon as you choose the Lock button and indicates that the device is starting to lock the Trunk Group and take channels out of service.

  • Page 677: Software Upgrade

    You can load Auxiliary files to the device using one of the following methods:  Web interface - see ''Loading Auxiliary Files through Web Interface'' on page 678  TFTP - see ''Loading Auxiliary Files through ini File using TFTP'' on page 679 Version 7.0 Mediant 3000...

  • Page 678: Loading Auxiliary Files Through Web Interface

    Mediant 3000 Notes: • You can schedule automatic loading of updated Auxiliary files using HTTP/HTTPS, FTP, or NFS. For more information, see Automatic Update Mechanism. • Saving Auxiliary files to flash memory may disrupt traffic on the device. To avoid this, disable all traffic on the device by performing a graceful lock as described in ''Locking and Unlocking the Device'' on page 671.

  • Page 679: Loading Auxiliary Files Through Ini File Using Tftp

    Figure 44-1: Loaded Files Listed on Device Information Page Click the Delete button corresponding to the file that you want to delete; a confirmation message box appears. Click OK to confirm deletion. Reset the device with a burn-to-flash for your settings to take effect. Version 7.0 Mediant 3000...

  • Page 680: 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 681 1 to 128 Hz). • Signal Level [-dBm]: Level of the tone for AM tones. • AM Factor [steps of 0.02]: Amplitude modulation factor (valid range from 1 to 50). Recommended values from 10 to 25. Version 7.0 Mediant 3000...

  • Page 682: Prerecorded Tones File

    For SBC calls, the PRT file supports only the ringback tone and hold tone. The prerecorded tones can be created using standard third-party, recording utilities such as Adobe Audition, and then combined into a single file (PRT file) using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).

  • Page 683: Cas Files

    Once created, you need to install the PRT file on the device. This can be done using AudioCodes' AcBootP utility or the Web interface (see ''Loading Auxiliary Files'' on page 677).

  • Page 684: Dialing Plans For Digit Collection

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

  • Page 686: Dial Plan Prefix Tags For Routing

    Mediant 3000 Notes: • The Dial Plan file must not contain overlapping prefixes. Attempting to process an overlapping configuration by the DConvert utility results in an error message specifying the problematic line. • The Dial Plan index can be selected globally for all calls (as described in the previous procedure), or per specific calls using Tel Profiles.
  • Page 687  Set this field to "LOCL" and the 'Trunk Group ID' field to 1 (local Trunk Group).  Set this field to "LONG" and the 'Trunk Group ID' field to 2 (long distance Trunk Group). Version 7.0 Mediant 3000...

  • Page 688: Obtaining Ip Destination From Dial Plan File

    Mediant 3000 ♦ Prefix tags for calling number prefixes: 'Source Phone Prefix'. Figure 44-2: Configuring Dial Plan File Label for IP-to-Tel Routing Configure manipulation rules to remove the prefix called tags: Open the Destination Phone Number Manipulation Table for IP-to-Tel Calls table (Configuration tab >...

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

    DConvert Utility User's Guide. You can load this *.dat file to the device using the Web interface (see ''Loading Auxiliary Files'' on page 677), AcBootP utility, or using the Auto-update mechanism from an external HTTP server. Version 7.0 Mediant 3000...

  • Page 690: User Information File

    Mediant 3000 Notes: • Tel-to-IP routing is performed on the original source number if the parameter 'Tel to IP Routing Mode' is set to 'Route calls before manipulation'. • Tel-to-IP routing is performed on the modified source number as defined in the Dial Plan file, if the parameter 'Tel To IP Routing Mode' is set to 'Route calls after manipulation'.
  • Page 691 User Info file.  To configure the GW User Info table through the Web interface: Open the GW User Info table (Configuration tab > VoIP menu > SIP Definitions > User Information > GW User Info Table). Version 7.0 Mediant 3000...
  • Page 692 Mediant 3000 Click Add; the following dialog box appears: Figure 44-3: GW User Info Table - Add Row Dialog Box Configure the GW User Info table parameters according to the table below. Click Add. To save the changes to flash memory, see ''Saving Configuration'' on page 672.

  • Page 693: User Information File For Sbc User Database

    You can use the SBC User Info table for the following:  Registering each user to an external registrar server.  Authenticating (for any SIP request and as a client) each user if challenged by an Version 7.0 Mediant 3000...
  • Page 694 Mediant 3000 external server.  Authenticating as a server incoming user requests (for SBC security). If the device registers on behalf of users and the users do not perform registration, any SIP request destined to the user is routed to the Proxy Set associated with the user’s IP Group.
  • Page 695 AOR in the database. [SBCUserInfoTable_IPGro upName] For configuring IP Groups, see ''Configuring IP Groups'' on page 343. Status (Read-only field) Displays the status of the user - "Registered" or "Not Registered". [SBCUserInfoTable_Statu Version 7.0 Mediant 3000...

  • Page 696: 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 DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.

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

    If you need a Software License Key for more than one device, repeat Step 1 for each device. Send the MAC address and/or serial number to your AudioCodes representative when requesting the required Software License Key. When you receive the new Software License Key file, check the file as follows: Open the file with any text-based program such as Notepad.

  • Page 699: Mediant

    If the Software License Key is valid, it is burned to the device's flash memory and displayed in the 'Current Key' field. Verify that the Software License Key was successfully installed, by doing one of the following: Version 7.0 Mediant 3000...

  • Page 700: Installing Software License Key Through Acbootp

    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 701: Software Upgrade Wizard

    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. Version 7.0 Mediant 3000...
  • Page 702 Mediant 3000 An HA switchover occurs from the active blade (i.e., the initial redundant blade) to the redundant blade (i.e., the initial active blade) to return the blades to their original HA state. Only the initial redundant blade undergoes a reset to return to redundant state.
  • Page 703 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 704 Mediant 3000 Click Start Software Upgrade; the wizard starts, prompting you to load a .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 705 If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file running on the device) and thereby, overwrite values previously configured for these parameters. Version 7.0 Mediant 3000...
  • Page 706 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 44-9: Software Upgrade Wizard - Files Loaded Click Reset to burn the files to the device's flash memory; the "Burn and reset in progress"...

  • Page 707: Backing Up And Loading Configuration File

    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. Version 7.0 Mediant 3000...
  • Page 708 Mediant 3000 To load the ini file to the device: Click the Browse button, navigate to the folder where the file is located, select the file, and then click Open; the name and path of the file appear in the field beside the Browse button.

  • Page 709: Automatic Provisioning

    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 7.0 Mediant 3000...
  • Page 710 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 711: Local Configuration Server With Bootp/Tftp

    Local configuration server with BootP/TFTP provides an easy and efficient method for automatic provisioning, where configuration occurs at a staging warehouse, as follows: 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 712 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 713: Provisioning From Http Server Using Dhcp Option 67

    46.1.3.2 Provisioning from TFTP Server using DHCP Option 66 This method is suitable when the network in which the device is deployed contains a provisioning TFTP server for all network equipment, without being able to distinguish between AudioCodes and non-AudioCodes devices. Version 7.0 Mediant 3000...

  • Page 714: Http-Based Provisioning

    Mediant 3000 Upon startup, the device searches for Option 66 in the DHCP response from the DHCP server. If Option 66 contains a valid IP address, the device attempts to download, through TFTP, a file that has a filename containing the device's MAC address (e.g., 00908f0130aa.ini).

  • Page 715: Loading Files Securely By Disabling Tftp

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

    Mediant 3000 46.2 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 717: 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 718: Access Authentication With Http Server

    <CONF>: configuration version, as configured by the ini file parameter, INIFileVersion The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) User's Manual Document #: LTRT-89730...
  • Page 719 Update process. Once they are downloaded, the device discards their configured URLs. To update these files again, you need to configure their URL addresses and filenames again. Below is an example of how to configure URLs for some of these files: Version 7.0 Mediant 3000...

  • Page 720: File Download Sequence

    Mediant 3000 Auxiliary Files: ♦ ini: CptFileURL = 'https://www.company.com/call_progress.dat' FeatureKeyURL = 'https://www.company.com/License_Key.txt' Software (.cmp) File: ♦ ini: CmpFileUrl = 'https://www.company.com/device/v.6.80A.227.005.cmp' Notes: • For one-time file download, the HTTP Get request sent by the device does not include the If-Modified-Since header. Instead, the HTTP-User-Agent header can be used in the HTTP Get request to determine whether firmware update is required.

  • Page 721: Cyclic Redundancy Check On Downloaded Configuration Files

    In such a setup, the provisioning server stores configuration files per device, where each file includes the MAC address of a specific device in its file name. Version 7.0 Mediant 3000...

  • Page 722: File Template For Automatic Provisioning

    Mediant 3000 To support this feature, you need to include the case-sensitive string, "<MAC>" anywhere in the configured file name of the URL, for example: IniFileURL = 'https://www.company.com/config_<MAC>.ini' The device automatically replaces the string with its hardware MAC address, resulting in a...
  • Page 723 Answering Machine Detection (AMD) amd.dat file pkey.pem SSL/TLS Private Key file sslp pkey<ID>.pem (for multi-certificate system) root.pem SSL/TLS Root Certificate file sslr root<ID>.pem (for multi-certificate system) cert.pem SSL/TLS Certificate file sslc cert<ID>.pem (for multi-certificate system) Version 7.0 Mediant 3000...

  • Page 724: Automatic Update Configuration Examples

    Mediant 3000 46.2.10 Automatic Update Configuration Examples This section provides a few examples on configuring the Automatic Update feature. 46.2.10.1 Automatic Update for Single Device This simple example describes how to configure the Automatic Update feature for updating a single device. In this example, the device queries the provisioning server for software, configuration and Auxiliary files every 24 hours.

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

    Set up an HTTP Web server and copy the .cmp and configuration files to the server. Configure the device with the URL paths of the .cmp and ini files: ♦ ini File: AutoCmpFileUrl = 'http://www.company.com/device/sw.cmp' IniFileURL = 'http://www.company.com/device/inifile.ini' Version 7.0 Mediant 3000...

  • Page 726: Automatic Update For Mass Deployment

    Mediant 3000 Configure the device with the IP address of the DNS server for resolving the domain names of the FTPS and HTTP servers: [ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice;...
  • Page 727 FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] Power down and then power up the device. Version 7.0 Mediant 3000...
  • Page 728 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 729: Restoring Factory Defaults

    Restoring Factory Defaults through CLI You can restore the device to factory defaults through CLI, as described in the following procedure. Note: Restoring factory defaults through CLI is supported only by Mediant 3000 Simplex.  To restore factory defaults through CLI:...

  • Page 730: Restoring Defaults Through Ini File

    Mediant 3000  To restore factory defaults through Web interface: Open the Configuration File page: • Toolbar: From the Device Actions drop-down list, choose Restore Defaults • Navigation Tree: Maintenance tab > Software Update > Configuration File Figure 47-1: Restoring Factory Defaults through Web To keep your current IP network settings, select the Preserve Network Configuration check box.

  • Page 731: Status, Performance Monitoring And Reporting

    Part IX Status, Performance Monitoring and Reporting...

  • Page 733: 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 79) Version 7.0 Mediant 3000...
  • Page 734 OAMP, Media and Control network interfaces. The following figure shows an example when dedicated ports are used for each traffic type: Figure 48-1: Ethernet Port Page for Physical Network Separation (Mediant 3000 with TP-8410) Table 48-1: Ethernet Port Information Parameters...

  • Page 735: Viewing Timing Module Information

    You can also access this page from the Home page (see ''Viewing the Home Page'' on page 79).  To view the status of the device's hardware components:  Open the Components Status page (Status & Diagnostics tab > System Status menu > Components Status). Version 7.0 Mediant 3000...
  • Page 736 Mediant 3000 User's Manual Document #: LTRT-89730...

  • Page 737: Carrier-Grade Alarms

     To view history alarms:  Open the Alarms History table (Status & Diagnostics tab > System Status menu > Carrier-Grade Alarms > Alarms History). Version 7.0 Mediant 3000...
  • Page 738 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 739: 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 7.0 Mediant 3000...

  • Page 740: Viewing Trunk Utilization

    Mediant 3000 50.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 741: Viewing Quality Of Experience

    Dialog Failed Attempts: displays the failed call attempts. This includes the number of calls and subscribes which were successfully and abnormally terminated.  Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer). Version 7.0 Mediant 3000...
  • Page 742 Mediant 3000  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 50-3: Quality Of Experience Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view QoE for an SRD or IP Group.

  • Page 743: Viewing Average Call Duration

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

  • Page 745: Voip Status

    Trunk Icon Color 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 Version 7.0 Mediant 3000...
  • Page 746 Mediant 3000 Icon Color Trunk AIS Alarm Blue 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 747: Viewing Nfas Groups And D-Channel Status

    For more information, see ''Performing Manual D-Channel Switchover in NFAS Group'' on page 450. 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 7.0 Mediant 3000...

  • Page 748: 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 51-3: NFAS Group & D-Channel Status Page 51.3...

  • Page 749: Viewing Performance Statistics

    The release reason can be viewed in the 'Termination Reason' field in the CDR message. You can reset the statistical data displayed on the page (i.e., refresh the display), by clicking the Reset Counters button located below the table. Version 7.0 Mediant 3000...
  • Page 750 Mediant 3000  To view IP-to-Tel and Tel-to-IP call counters:  Open the Call Counters page that you want to view (Status & Diagnostics tab > VoIP Status menu > IP to Tel Calls Count or Tel to IP Calls Count); the figure below shows the IP to Tel Calls Count page.

  • Page 751: Viewing Registered Users

    An AOR is a SIP or SIPS URI that points to a domain with a location service that can map the URI to another URI (contact) where the user might be available. A contact is a SIP URI Version 7.0 Mediant 3000...

  • Page 752: Viewing Registration Status

    Mediant 3000 that can be used to contact that specific instance of the user agent for subsequent requests.  To view registered SAS/SBC users in the Users Registration database:  Web: SAS/SBC Registered Users page (Status & Diagnostics tab > VoIP Status menu >...

  • Page 753: Viewing Call Routing Status

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

  • Page 754: Viewing Ip Connectivity

    Mediant 3000 51.10 Viewing IP Connectivity The IP Connectivity page displays on-line, read-only network diagnostic connectivity information on all destination IP addresses configured in the Tel-to-IP Routing table (see ''Configuring Tel-to-IP Routing Rules'' on page 496). Note: he information in columns 'Quality Status' and 'Quality Info' (per IP address) is reset if two minutes elapse without a call to that destination.
  • Page 755 Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).  The parameter is reset if no QoS information is received for 2 minutes. DNS Status DNS status can be one of the following:  DNS Disable  DNS Resolved  DNS Unresolved Version 7.0 Mediant 3000...
  • Page 756 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 757: Reporting Information To External Party

    You can configure the device to send RTXP XR at the end of each call and according to a user-defined interval between consecutive reports. Table 52-1: RTCP XR Published VoIP Metrics Group Metric Name General Start Timestamp Stop Timestamp Call-ID Version 7.0 Mediant 3000...
  • Page 758 Mediant 3000 Group Metric Name Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Silence Suppression State Jitter Buffer...
  • Page 759 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 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 Version 7.0 Mediant 3000...
  • Page 760 Mediant 3000 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 Delay: RTD=65535 ESD=0 QualityEst:  DialogID: 20328634741612201520943@172.17.116.201;to- tag=1c1690611502;from-tag=1c2032864069To configure RTCP XR: Open the RTP/RTCP Settings page (Configuration tab >...

  • Page 761: Generating Call Detail Records

    The default CDR fields for SBC signaling are listed in the table below. A typical SBC session consists of two SBC legs. Each leg generates its own signaling CDRs. Each leg generates three CDR types: at call start (SBCReportType=CALL_START), Version 7.0 Mediant 3000...
  • Page 762 Mediant 3000 connect time (SBCReportType=CALL_CONNECT) when call ends (SBCReportType=CALL_END). CDRs belonging to the same SBC session (both legs) have the same Session ID (SessionId CDR field). CDRs belonging to the same SBC leg have the same SIP Call ID (SIPCallId CDR field).
  • Page 763  "GWAPP_NORMAL_CA LL_CLEAR"  ABNORMALLY_TERMI NATED: Anything else N/A - Reasons not belonging to above categories. SetupTime Call setup time String of up to 35 characters ConnectTime Call connect time String of up to 35 characters Version 7.0 Mediant 3000...
  • Page 764 Mediant 3000 CDR Field Name Description Format ReleaseTime Call release time String of up to 35 characters RedirectReason Redirect reason String of up to 15 characters RedirectURINum Redirection URI String of up to 41 characters RedirectURINumBe Redirect URI number before...

  • Page 765: Cdr Fields For Sbc Media

    RemoteRtpPort Remote RTP port InPackets Number of received packets OutPackets Number of sent packets LocalPackLoss Local packet loss RemotePackLoss Remote packet loss RTPdelay RTP delay RTPjitter RTP jitter TxRTPssrc Tx RTP SSRC RxRTPssrc Local RTP SSRC Version 7.0 Mediant 3000...

  • Page 766: Cdr Fields For Gateway Application

    Mediant 3000 CDR Field Name Description LocalRFactor Local conversation quality 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 767 SIP call termination reason (see ''Release Reasons in CDR for Gateway Application'' on page 770) Fax transaction during call InPackets Number of incoming packets OutPackets Number of outgoing packets PackLoss Local packet loss RemotePackLoss Number of outgoing lost packets Version 7.0 Mediant 3000...
  • Page 768 Mediant 3000 Field Name Description SIPCalld Unique SIP call ID SetupTime Call setup time ConnectTime Call connect time ReleaseTime Call release time RTPdelay RTP delay RTPjitter RTP jitter RTPssrc Local RTP SSRC RemoteRTPssrc Remote RTP SSRC RedirectReason Redirect reason Redirection phone number type...
  • Page 769 127, meaning that information is unavailable. LocalMosCQ Local MOS for conversation quality RemoteMosCQ Remote MOS for conversation quality SigSourcePort SIP source port SigDestPort SIP destination port MediaType Media type - audio, video, or text Version 7.0 Mediant 3000...
  • Page 770 Mediant 3000 Field Name Description Information relating to the Automatic Machine Detection (AMD) feature:  V - voice  A - answer machine  S - silence  U - unknown Information relating to AMD that shows the success that the answering type...
  • Page 771  "GWAPP_NUMBER_CHANGED"  "GWAPP_NON_SELECTED_USER_CLEARING"  "GWAPP_INVALID_NUMBER_FORMAT"  "GWAPP_FACILITY_REJECT"  "GWAPP_RESPONSE_TO_STATUS_ENQUIRY"  "GWAPP_NORMAL_UNSPECIFIED"  "GWAPP_CIRCUIT_CONGESTION"  "GWAPP_USER_CONGESTION"  "GWAPP_NO_CIRCUIT_AVAILABLE"  "GWAPP_NETWORK_OUT_OF_ORDER"  "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" Version 7.0 Mediant 3000...

  • Page 772: Customizing Cdrs For Gateway Calls

    Mediant 3000 • "RELEASE_BECAUSE_PREEMPTION_ANALOG_CIRCUIT_RESERVED_FOR_ REUSE" • "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED"  "GWAPP_BC_NOT_AUTHORIZED"  "GWAPP_BC_NOT_PRESENTLY_AVAILABLE"  "GWAPP_SERVICE_NOT_AVAILABLE"  "GWAPP_CUG_OUT_CALLS_BARRED"  "GWAPP_CUG_INC_CALLS_BARRED"  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS"  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST" ...
  • Page 773 Configure the CDR according to the parameters described in the table below. Click Add. An example of CDR customization rules configured in the table is shown below: Figure 52-3: Example of CDR Customization Rules for Gateway Calls Version 7.0 Mediant 3000...
  • Page 774 Mediant 3000 Gateway CDR Format Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [GWCDRFormat_Index] Note: Each row must be configured with a unique index. CDR Type Defines the application type for which you want to customize CDRs.

  • Page 775: Customizing Cdrs For Sbc Calls

    If you configure the value to 0 and the RADIUS Attribute is not any of the ones listed above, the configuration is invalid. 52.2.3 Customizing CDRs for SBC Calls The SBC CDR Format table lets you customize SBC-related CDRs that are generated by the device for the following: Version 7.0 Mediant 3000...
  • Page 776 Mediant 3000  CDRs (media and SIP signaling) sent in Syslog messages. For CDRs sent in Syslog messages, you can customize the name of the CDR field. The table lets you configure up to 128 Syslog CDR customization rules. ...
  • Page 777 Factor; [176] Remote R Factor; [177] Local MOS CQ; [178] Remote MOS CQ; [179] AMD Decision; [180] AMD Decision Probability; [181] Latched RTP IP; [182]Latched RTP Port; [183] Latched T38 IP; [184] Latched T38 Port.  Syslog SBC and RADIUS SBC: [200] Source URI; [201] Destination Version 7.0 Mediant 3000...
  • Page 778 Mediant 3000 Parameter Description URI; [202] Source URI Before Manipulation; [203] Destination URI Before Manipulation; [204] Redirect URI; [205] Redirect URI Before Manipulation; [206] SIP Method; [207] Direct Media; [208] Source Username; [209] Destination Username; [210] Source Username Before Manipulation; [211] Destination Username Before Manipulation;...

  • Page 779: Configuring Cdr Reporting

    RADIUS accounting, see the table following the procedure below. RADIUS CDR attributes have the following format:  Standard RADIUS attributes (per RFC): A typical standard RADIUS attribute is shown below. The RADIUS attribute ID depends on the attribute. Figure 52-7: Typical Standard RADIUS Attribute Version 7.0 Mediant 3000...
  • Page 780 Mediant 3000 The following figure shows a standard RADIUS attribute collected by Wireshark. The bottom pane shows the RADIUS attribute information as sent in the packet; the upper pane is Wireshark's interpretation of the RADIUS information in a more readable format.
  • Page 781 SIP call identifier Up to 32 h323- Start Acc incoming- octets incoming- Stop Acc conf-id conf- id=3839353 h323-remote- IP address of the Numeric Stop Acc address remote gateway h323-conf-id H.323/SIP call Up to 32 Start Acc Version 7.0 Mediant 3000...
  • Page 782 Mediant 3000 Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID identifier octets Stop Acc h323-setup- Setup time in NTP String h323-setup- Start Acc time format 1 time=09:33: Stop Acc 26.621 Mon Dec 2014 h323-call- Originator of call:...
  • Page 783 (Standard) A unique accounting String 34832 Start Acc identifier - match start Stop Acc & stop acct-session- (Standard) For how many Numeric Stop Acc time seconds the user received the service Version 7.0 Mediant 3000...
  • Page 784 Mediant 3000 Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID acct-input- (Standard) Number of packets Numeric Stop Acc packets received during the call acct-oputput- (Standard) Number of packets Numeric Stop Acc packets sent during the call...
  • Page 785 (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 7.0 Mediant 3000...

  • Page 786: Querying Device Channel Resources Using Sip Options

    Mediant 3000 52.4 Querying Device Channel Resources using SIP OPTIONS The device reports its maximum and available channel resources in SIP 200 OK responses upon receipt of SIP OPTIONS messages. The device sends this information in the SIP X- Resources header with the following parameters: ...

  • Page 787: Diagnostics

    Part X Diagnostics...

  • Page 789: Syslog And Debug Recording

    Syslog'' on page 803). Enabling Syslog functionality is not required for rules that include Syslog messages in the DR sent to a Debug Recording server. • To configure the Syslog server's address, see ''Configuring Address of Syslog Version 7.0 Mediant 3000...
  • Page 790 Mediant 3000 Server'' on page 802. To configure additional, global Syslog settings, see Configuring Syslog on page 794. • To configure the Debug Recording server's address, see ''Configuring Address of Debug Recording Server'' on page 805. • To configure additional, global CDR settings such as at what stage of the call the CDR is generated (e.g., start and end of call), see Configuring CDR Reporting on...
  • Page 791 You can use the index number or string name to specify the configuration entity for the following 'Filter Types': Tel-to-IP, IP-to-Tel, IP Group, SRD, Classification, IP-to-IP Routing, or SIP Interface. For example, to specify IP Group at Index 2 with the name "SIP Trunk", Version 7.0 Mediant 3000...
  • Page 792 Mediant 3000 Parameter Description configure the parameter to either "2" or "SIP Trunk" (without apostrophes).  For IP trace expressions, see ''Filtering IP Network Traces'' on page 793. Log Destination Defines where the device sends the log file.  log-dest [0] Syslog Server = The device generates Syslog messages based on the configured log filter and sends them to a user-defined Syslog server.

  • Page 793: Filtering Ip Network Traces

    Wireshark condition "(ip.src == 1.1.1.1 or ip.src == 2.2.2.2) and ip.dst == 3.3.3.3" can be configured using the following two table row entries: ip.src == 1.1.1.1 and ip.dst == 3.3.3.3 ip.src == 2.2.2.2 and ip.dst == 3.3.3.3 Version 7.0 Mediant 3000...

  • Page 794: Configuring Syslog

    Mediant 3000 Notes: • If the 'Value' field is undefined, the device records all IP traffic types. • You cannot use ip.addr or udp/tcp.port together with ip.src/dst or udp/tcp.srcport/dstport. For example, "ip.addr==1.1.1.1 and ip.src==2.2.2.2" is an invalid configuration value. 53.2...
  • Page 795 96 is the number of times the device has reset.  5 is a unique SID session number (in other words, this is the fifth call session since the last device reset).  Gateway application: A call session is considered Version 7.0 Mediant 3000...

  • Page 796: Event Representation In Syslog Messages

    Forked legs and alternative legs share the same session number. Note: You can configure the device to maintain the same SID value for calls traversing multiple AudioCodes' devices. For more information, see ''Maintaining Same Syslog SID/BID over Multiple Devices'' on page 798.
  • Page 797 RTP Packet Loss Counts the number of BFI Frames Received From The Host No Available Release Descriptor RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Version 7.0 Mediant 3000...

  • Page 798: Unique Device Identification In Syslog Messages

    Syslog messages include 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 799: Syslog Fields For Answering Machine Detection (Amd)

    Raised Alarms: RAISE-ALARM: <Alarm Name>; Textual Description: <Textual Description>; Severity <Alarm Severity>; Source <Alarm Source>; Unique ID: <Alarm Unique ID >. If additional information exists in the alarm, then these are also added: Additional Info1:/ Additional Info2:/ Additional Info3 Version 7.0 Mediant 3000...

  • Page 800: Configuring Web User Activities To Report To Syslog

    Mediant 3000 The Messages’ Severity is as follows: Table 53-5: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Critical RecoverableMsg Major RecoverableMsg Minor RecoverableMsg Warning Notice Indeterminate Notice Cleared Notice  Cleared Alarms: CLEAR-ALARM: <Alarm Name>; Textual Description: <Textual Description>;...

  • Page 801: Configuring Syslog Debug Level

    In addition, you can enable the device to send multiple Syslog messages bundled into a single packet as well as enable a protection mechanism that automatically lowers the debug level when the device's CPU resources become low, ensuring sufficient CPU resources are available for processing voice traffic. Version 7.0 Mediant 3000...

  • Page 802: Configuring Address Of Syslog Server

    Mediant 3000  To configure the Syslog debug level: Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Figure 53-3: Configuring Syslog Debug Level From the 'Debug Level' (GwDebugLevel) drop-down list, select the desired debug level of the Syslog messages: •...

  • Page 803: Enabling Syslog

    When debug recording is enabled and Syslog messages are also included in the debug recording, to view Syslog messages using Wireshark, you must install AudioCodes' Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and displayed using the "acsyslog" filter (instead of the regular "syslog"...

  • Page 804: Viewing Web User Activity Logs

    • 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. 53.2.7 Viewing Web User Activity Logs If you have enabled the reporting of Web user activities, you can view logged activities in the Web interface's Activity Log table (read-only).

  • Page 805: Configuring Debug Recording

    Click Submit. 53.3.2 Collecting Debug Recording Messages To collect debug recording packets, use the open source packet capturing 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 806: Mediant

    In the Filter field, type "acdr" (see the figure below) to view the debug recording messages. Note that the source IP address of the messages is always the OAMP IP address of the device. The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: User's Manual...

  • Page 807: 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 7.0 Mediant 3000...
  • Page 808 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 809: 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. You can then provide the files to AudioCodes support team for troubleshooting. ...
  • Page 810 Mediant 3000 The following procedure describes how to retrieve the debug file from the device through the Web interface.  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button.

  • Page 811: 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 through the Web interface.
  • Page 812 Mediant 3000 Click Add; the following dialog box appears: Figure 56-1: Test Call Table - Add Row Dialog Box Configure a test call according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.
  • Page 813 Defines the transport type for outgoing calls. Type  [-1] = Not configured (default)  [0] UDP [Test_Call_DestTrans  [1] TCP portType]  [2] TLS Note: The parameter is applicable only if the 'Route By' parameter is set to [2] (Dest Address). Version 7.0 Mediant 3000...
  • Page 814 Mediant 3000 Parameter Description QoE Profile Assigns a QoE Profile to the test call. By default, no value is defined (None). [Test_Call_QOEProfil To configure QoE Profiles, see ''Configuring Quality of Experience Profiles'' on page 309. Bandwidth Profile Assigns a Bandwidth Profile to the test call.
  • Page 815 Defines the interval (in minutes) between automatic outgoing test calls. The valid value range is 0 to 100000. The default is 0 (i.e., scheduling is disabled). [Test_Call_ScheduleI nterval] Note: The parameter is applicable only if 'Call Party' is set to Caller. Version 7.0 Mediant 3000...

  • Page 816: Starting And Stopping Test Calls

    Mediant 3000 56.2 Starting and Stopping Test Calls The following procedure describes how to start, stop, and restart test calls.  To start, stop, and restart a test call: In the Test Call table, select the required test call entry; the Actions button appears above the table.

  • Page 817: Viewing Test Call Statistics

    Number of successfully answered calls out of the total number of calls attempted (ASR). • "Running (Calls: <number of active calls>, ASR: <%>)": test call has been started (i.e., the Dial command was clicked) and shows the following: Version 7.0 Mediant 3000...

  • Page 818: Configuring Dtmf Tones For Test Calls

    Mediant 3000 ♦ Number of currently active test calls. ♦ Number of successfully answered calls out of the total number of calls attempted (Answer Seizure Ratio or ASR). • "Receiving (<number of active calls>)": test call has been automatically activated by calls received for this configured test call endpoint from the configured remote endpoint.

  • Page 819: Configuring Basic Test Call

    For a full description of the parameter, see ''SIP Test Call Parameters'' on page 857. • The call test is done on all SIP Interfaces. • The call test is applicable only to the Gateway application. Version 7.0 Mediant 3000...

  • Page 820: Configuring Sbc Test Call With External Proxy

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

  • Page 821: Test Call Configuration Examples

    Test Mode: Once Alternatively, if you want to route the test call using the Tel-to-IP Routing table for the Gateway application, configure the following: • Test Call table configuration: ♦ Endpoint URI: 101@10.0.0.1 ♦ Route By: GW Tel2IP Version 7.0 Mediant 3000...
  • Page 822 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 823 Route By: Dest Address ♦ Destination Address: "10.13.4.12" (this is the IP address of the device itself) ♦ SIP Interface: SIPInterface_0 ♦ Auto Register: Enable ♦ User Name: "testuser" ♦ Password: "12345" ♦ Call Party: Caller Version 7.0 Mediant 3000...
  • Page 824 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 825: Appendix

    Part XI Appendix...

  • Page 827: Dialing Plan Notation For Routing And Manipulation

    An example for entering a combined prefix and suffix dial plan - assume you want to match a rule whose destination phone prefix is 4 to 8, and suffix is 234, 235, or 236. The entered value would be the following: [4-8](23[4,5,6]). [n-m] or (n-m) Represents a range of numbers. Examples: Version 7.0 Mediant 3000...
  • Page 828 Mediant 3000 Notation Description  To depict prefix numbers from 5551200 to 5551300:  [5551200-5551300]#  To depict prefix numbers from 123100 to 123200:  123[100-200]#  To depict prefix and suffix numbers together:  03(100): for any number that starts with 03 and ends with 100.
  • Page 829 "x" wildcards (e.g., xx165xxxxx#); the prefix to add to the number would include the HEX values (e.g., +49 \287303\29 165-). Below is a list of common ASCII characters and their corresponding HEX values: ASCII Character HEX Value Version 7.0 Mediant 3000...
  • Page 830 Mediant 3000 This page is intentionally left blank. User's Manual Document #: LTRT-89730...

  • Page 831: Configuration Parameters Reference

    Web Users table inherits the parameter's value. User Inactivity Timer Defines the duration (in days) for which a user has not logged in to the Web interface, after which the status of the user becomes inactive and Version 7.0 Mediant 3000...
  • Page 832 Mediant 3000 Parameter Description [UserInactivityTimer] can no longer access the Web interface. These users can only log in to the Web interface if their status is changed (to New or Valid) by a System Administrator or Master user. The valid value is 0 to 10000, where 0 means inactive. The default is 90.
  • Page 833 Up to 20 lines (or rows) of text can be defined.  The configured text message must be enclosed in double quotation marks (i.e., "...").  If the parameter is not configured, no Welcome message is Version 7.0 Mediant 3000...

  • Page 834: Telnet Parameters

    Mediant 3000 Parameter Description displayed. 58.1.3 Telnet Parameters The Telnet parameters are described in the table below. Table 58-3: Telnet Parameters Parameter Description Embedded Telnet Server Enables the device's embedded Telnet server. Telnet is disabled by default for security. ...

  • Page 835: Snmp Parameters

    The valid range is a string of up to 64 characters. Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This [SendKeepAliveTrap] 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 836 Mediant 3000 Parameter Description [PM_EnableThresholdAlarms] Enables the sending of the SNMP trap event, acPerformanceMonitoringThresholdCrossing which is sent every time the threshold (high and low) of a Performance Monitored object (e.g., acPMMediaRealmAttributesMediaRealmBytesTxHighThreshold) is crossed.  [0] = (Default) Disable  [1] = Enable Defines the base product system OID.
  • Page 837 The valid value is a string of up to 19 characters that can include [SNMPReadWriteCommunityStri only the following: ng_x]  Upper- and lower-case letters (a to z, and A to Z)  Numbers (0 to 9)  Hyphen (-)  Underline (_) For example, "Private-comm_string1". The default is "private". Version 7.0 Mediant 3000...

  • Page 838: Serial Parameters

    Mediant 3000 Parameter Description Trap Community String Defines the community string for SNMP traps. The valid value is a string of up to 19 characters that can include only the following: [SNMPTrapCommunityString]  Upper- and lower-case letters (a to z, and A to Z) ...

  • Page 839: Auxiliary And Configuration File Name Parameters

    Determines if all the device's parameters are set to their defaults before processing the updated ini file.  [0] = Disable - parameters not included in the downloaded ini file are not returned to default settings (i.e., retain their current settings).  [1] = Enable (default). Version 7.0 Mediant 3000...

  • Page 840: Automatic Update Parameters

    Dial Plan File Defines the name of the Dial Plan file. This file should be created using AudioCodes DConvert utility (refer to DConvert Utility User's Guide). [DialPlanFileName] For the ini file, the name must be enclosed by single apostrophes, for example, 'dial_plan.dat'.
  • Page 841 The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User- Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld- <NAME>;<VER>(<MAC>), the device sends the following User-Agent...
  • Page 842 Mediant 3000 Parameter Description effect.  The tags can be defined in any order.  The tags must be defined adjacent to one another (i.e., no spaces). Defines the filename and path (URL) to the provisioning server from where the software file (.cmp) can be downloaded, based on timestamp [AutoCmpFileUrl] for the Automatic Updated mechanism.
  • Page 843 The cmp file is validated before it's burned to flash. The checksum of the cmp file is also compared to the previously burnt checksum to avoid unnecessary resets.  The maximum length of the URL address is 255 characters. Version 7.0 Mediant 3000...
  • Page 844 Mediant 3000 Parameter Description Defines the name of the ini file and the path to the server (IP address or FQDN) on which it is located. The ini file can be loaded using [IniFileURL] HTTP/HTTPS, FTP, FTPS, or NFS. For example: http://192.168.0.1/filename...
  • Page 845 > Defines the list of file types in the File Template for automatic updates, to automatic-update > download from the provisioning server. template-files-list For more information, see File Template for Automatic Provisioning on [AupdFilesList] page 722. Version 7.0 Mediant 3000...

  • Page 846: Networking Parameters

    Mediant 3000 58.2 Networking Parameters This subsection describes the device's networking parameters. 58.2.1 Ethernet Parameters The Ethernet parameters are described in the table below. Table 58-9: Ethernet Parameters Parameter Description [EthernetPhyConfiguration Defines the Ethernet connection mode type.  [0] = 10Base-T half-duplex (Not applicable) ...
  • Page 847  For the parameter to take effect, a device reset is required.  The 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 848: Routing Parameters

    Mediant 3000 Parameter Description Note: If this parameter is not configured (i.e., default value is 1) and one of the interfaces has a VLAN ID set to 1, this interface is still considered the ‘Native’ VLAN. If you do not wish to have a ‘Native’ VLAN ID and want to use VLAN ID 1, set this parameter to a value other than any VLAN ID in the table.

  • Page 849: Quality Of Service Parameters

    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. Gold QoS Defines the DiffServ value for the Gold CoS content (Streaming applications). Version 7.0 Mediant 3000...

  • Page 850: Nat And Stun Parameters

    Mediant 3000 Parameter Description [GoldServiceClassDiffServ The valid range is 0 to 63. The default is 26. Bronze QoS Defines the DiffServ value for the Bronze CoS content (OAMP applications). The valid range is 0 to 63. The default is 10.
  • Page 851 (in seconds). Therefore, the parameter is applicable only if the SendKeepAliveTrap parameter is set to 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.

  • Page 852: Nfs Parameters

    Mediant 3000 Parameter Description Note: The NAT mechanism must be enabled for the parameter to take effect. To enable NAT, see the NATMode parameter). [EnableUDPPortTranslatio Enables UDP port translation.  [0] = (Default) Disables UDP port translation.  [1] = Enables UDP port translation. The device compares the source UDP port of the first incoming packet to the remote UDP port stated in the opening of the channel.

  • Page 853: Dns Parameters

    Each A-Record contains the host name, priority, weight, and port. [SRV2IP] The format of the ini file table parameter is: [SRV2IP] FORMAT SRV2IP_Index = SRV2IP_InternalDomain, SRV2IP_TransportType, SRV2IP_Dns1, SRV2IP_Priority1, SRV2IP_Weight1, SRV2IP_Port1, SRV2IP_Dns2, SRV2IP_Priority2, SRV2IP_Weight2, SRV2IP_Port2, SRV2IP_Dns3, SRV2IP_Priority3, SRV2IP_Weight3, SRV2IP_Port3; [\SRV2IP] For example: Version 7.0 Mediant 3000...

  • Page 854: Dhcp Parameters

    Mediant 3000 Parameter Description SRV2IP 0 = SrvDomain,0,Dnsname1,1,1,500,Dnsname2,2,2,501,$$,0,0,0; For a detailed description of the table, see ''Configuring the Internal SRV Table'' on page 161. 58.2.8 DHCP Parameters The Dynamic Host Control Protocol (DHCP) parameters are described in the table below.
  • Page 855 (e.g., FRI)  wk denotes week of the month (e.g., 03)  hh denotes hour (e.g., 23)  mm denotes minutes (e.g., 10) For example, "04:FRI/03:23:00" denotes Friday, the third week of Version 7.0 Mediant 3000...

  • Page 856: Debugging And Diagnostics Parameters

    Mediant 3000 Parameter Description April, at 11 P.M. The week field can be 1-5, where 5 denotes the last occurrence of the specified day in the specified month. For example, "04:FRI/05:23:00" denotes the last Friday of April, at 11 P.M.

  • Page 857: Sip Test Call Parameters

    This can be any string of up to 15 characters. By default, no number is defined. Notes:  The parameter is only for testing incoming calls destined to this prefix number.  This feature is applicable to all applications (Gateway and SBC). Version 7.0 Mediant 3000...

  • Page 858: Syslog, Cdr And Debug Parameters

    Mediant 3000 Parameter Description SBC Test ID Defines the SBC test call prefix (ID) for identifying SBC test calls that traverse the device to register with an external routing entity such as an sbc-test-id IP PBX or proxy server. [SBCtestID] The parameter functions together with the TestCallID parameter, which defines the prefix of the simulated endpoint.
  • Page 859 CDR with the MediaReportType field set to "Update" is sent, as the media was changed from voice to T.38. A CDR is also sent upon termination Version 7.0 Mediant 3000...
  • Page 860 Mediant 3000 Parameter Description (end) of the media in the call.  [4] Start & End & Update Media = Sends a CDR at the start of the media, upon an update in the media (if occurs), and at the end of the media.
  • Page 861 (e.g., INVITE). All logs that are generated by devices through which the specific call session has traversed, have the [SendAcSessionIDHeader same SID/BID, which is that of the device that initiated the call.  [0] Disable (default)  [1] Enable Version 7.0 Mediant 3000...
  • Page 862 Mediant 3000 Parameter Description For more information, see ''Maintaining Same Syslog SID/BID over Multiple Devices'' on page 798. Activity Types to Report Defines the operations (activities) performed in the Web interface that via Activity Log Messages are reported to a Syslog server.
  • Page 863 The format of the ini file table parameter is: configure voip > services cdr > cdr- [ GWCDRFormat ] format gw-cdr-format FORMAT GWCDRFormat_Index = GWCDRFormat_CDRType, [GWCDRFormat] GWCDRFormat_ColumnType, GWCDRFormat_Title, GWCDRFormat_RadiusType, GWCDRFormat_RadiusID; [ \GWCDRFormat ] For a detailed description of the table, see Customizing CDRs for Version 7.0 Mediant 3000...

  • Page 864: Heartbeat Packet Parameters

    Mediant 3000 Parameter Description Gateway Calls on page 772. SBC CDR Format Table SBC CDR Format Table The table defines CDR customization rules for SBC calls. The format of the ini file table parameter is: configure voip > services cdr > cdr-...

  • Page 865: Bootp Parameters

    [5] = 20 BootP retries, 60 sec.  [7] = 10 DHCP packets  [6] = 40 BootP retries, 120 sec.  [15] = 18 DHCP packets  [7] = 100 BootP retries, 300 sec.  [15] = BootP retries indefinitely. Version 7.0 Mediant 3000...
  • Page 866 Mediant 3000 Parameter Description [BootPSelectiveEnable] Enables the Selective BootP mechanism.  [1] = Enabled  [0] = Disabled (default) The Selective BootP mechanism (available from Boot version 1.92) enables the device's integral BootP client to filter unsolicited BootP/DHCP replies (accepts only BootP replies that contain the text 'AUDC' in the vendor specific information field).

  • Page 867: 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 the table, see ''Configuring Firewall Settings'' on page 173. Version 7.0 Mediant 3000...

  • Page 868: Https Parameters

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

  • Page 869: Srtp Parameters

    (IpProfile_EnableSymmetricMKI). For a detailed description of the parameter and for configuring this functionality in the IP Profile table, see [EnableSymmetricMKI] ''Configuring IP Profiles'' on page 391. Note: If this functionality is configured for a specific IP Profile, the settings Version 7.0 Mediant 3000...
  • Page 870 Mediant 3000 Parameter Description of this global parameter is ignored for calls associated with the IP Profile. Offered SRTP Cipher Defines the offered crypto suites (cipher encryption algorithms) for SRTP. Suites  [0] All = (Default) All available crypto suites.

  • Page 871: Tls Parameters

     Device acts as a server: The device does not request the client certificate.  [1] Enable =  Device acts as a client: Verification of the server certificate is required to establish the TLS connection. Version 7.0 Mediant 3000...
  • Page 872 Mediant 3000 Parameter Description  Device acts as a server: The device requires the receipt and verification of the client certificate to establish the TLS connection. Notes:  For the parameter to take effect, a device reset is required. ...

  • Page 873: Ssh Parameters

    Note: To define the key size, use the TLSPkeySize parameter. Max Payload Size Defines the maximum uncompressed payload size (in bytes) for SSH packets. The valid value is 550 to 32768. The default is 32768. [SSHMaxPayloadSize] Version 7.0 Mediant 3000...

  • Page 874: Ids Parameters

    Mediant 3000 Parameter Description Max Binary Packet Size Defines the maximum packet size (in bytes) for SSH packets. The valid value is 582 to 35000. The default is 35000. [SSHMaxBinaryPacketSi Maximum SSH Sessions Defines the maximum number of simultaneous SSH sessions.

  • Page 875: Ipsec Parameters

    The table defines the IPSec SA table. This table allows you to configure Table the Internet Key Exchange (IKE) and IP Security (IPSec) protocols. The format of the ini file table parameter is: [IPSecSATable] [ IPsecSATable ] FORMAT IPsecSATable_Index = IPsecSATable_RemoteEndpointAddressOrName, IPsecSATable_AuthenticationMethod, IPsecSATable_SharedKey, Version 7.0 Mediant 3000...

  • Page 876: Ocsp Parameters

    Mediant 3000 Parameter Description IPsecSATable_SourcePort, IPsecSATable_DestPort, IPsecSATable_Protocol, IPsecSATable_Phase1SaLifetimeInSec, IPsecSATable_Phase2SaLifetimeInSec, IPsecSATable_Phase2SaLifetimeInKB, IPsecSATable_DPDmode, IPsecSATable_IPsecMode, IPsecSATable_RemoteTunnelAddress, IPsecSATable_RemoteSubnetIPAddress, IPsecSATable_RemoteSubnetPrefixLength, IPsecSATable_InterfaceName; [ \IPsecSATable ] Note: For a detailed description of the table, see ''Configuring IP Security Associations Table'' on page 188. IPSec Proposal Table IP Security Proposal...

  • Page 877: Quality Of Experience Parameters

    SEM server. The valid value is a string representing the name of the TLS Context as [QoETLSContextName] configured in the 'Name' field of the TLS Contexts table. The default is the default TLS Context (ID 0). Version 7.0 Mediant 3000...
  • Page 878 Mediant 3000 Parameter Description QoE Report Mode Defines at what stage of the call the device sends the QoE data of the call to the SEM server.  [0] Report QoE During Call (default) [QoeReportMode]  [1] Report QoE At End Call...
  • Page 879 The format of the ini file table parameter is as follows: [MediaEnhancementRules] [MediaEnhancementRule FORMAT MediaEnhancementRules_Index = MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of the table, see ''Configuring Media Enhancement Profiles'' on page 316. Version 7.0 Mediant 3000...

  • Page 880: Control Network Parameters

    Mediant 3000 58.6 Control Network Parameters 58.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 58-33: Proxy, Registration and Authentication SIP Parameters Parameter Description IP Group Table IP Group Table This table configures IP Groups.
  • Page 881 The range is 5 to 2,000,000. The default interval is 60. [ProxyIPListRefreshTime] Enable Fallback to Determines whether the device falls back to the Tel-to-IP Routing table Routing Table for call routing when Proxy servers are unavailable. Version 7.0 Mediant 3000...
  • Page 882 Mediant 3000 Parameter Description  [0] Disable = (Default) Fallback is not used.  [1] Enable = The Tel-to-IP Routing table is used when Proxy servers [IsFallbackUsed] are unavailable. When the device falls back to the Tel-to-IP Routing table, it continues scanning for a Proxy.
  • Page 883 SIP proxy servers ions] (i.e., the EnableProxyKeepAlive parameter is set to 1).  [0] No = (Default) Device's IP address is used in keep-alive OPTIONS messages.  [1] Yes = Device's "gateway name" is used in keep-alive OPTIONS Version 7.0 Mediant 3000...
  • Page 884 Mediant 3000 Parameter Description messages.  [2] Server = Device's IP address is used in the From and To headers in keep-alive OPTIONS messages. User Name Defines the username for registration and Basic/Digest authentication with a Proxy/Registrar server. By default, no value is defined.
  • Page 885 Registrar IP Address Defines the IP address (or FQDN) and port number (optional) of the Registrar server. The IP address is in dotted-decimal notation, e.g., 201.10.8.1:<5080>. [RegistrarIP] Notes:  The parameter is applicable only to the Gateway application. Version 7.0 Mediant 3000...
  • Page 886 Mediant 3000 Parameter Description  If not specified, the REGISTER request is sent to the primary Proxy server.  When a port number is specified, DNS NAPTR/SRV queries aren't performed, even if the parameter DNSQueryType is set to 1 or 2.
  • Page 887 Registration Mode Determines the device's registration and authentication method.  [0] Per Endpoint = Registration and authentication is performed separately for each B-channel. [AuthenticationMode]  [1] Per Gateway = (Default) Single registration and authentication for Version 7.0 Mediant 3000...
  • Page 888 Mediant 3000 Parameter Description the entire device. This is typically used for and digital modules. Note: The parameter is applicable only to the Gateway application. Set Out-Of-Service On Enables setting the , trunk, or entire device (i.e., all endpoints) to out-of- Registration Failure service if registration fails.
  • Page 889 For example, if the parameter value is set to 200 sec, the interval used is any random time between 160 to 200 seconds. This prevents an “avalanche” of keep-alive by multiple SIP UAs to a specific server. Version 7.0 Mediant 3000...

  • Page 890: Network Application Parameters

    Mediant 3000 Parameter Description Max Generated Register Defines the maximum number of user register requests that the device Rate can send to a proxy (or registrar) server per second. This feature is useful in that it can be used to prevent an overload on the device's CPU...
  • Page 891 [ CpMediaRealm ] FORMAT CpMediaRealm_Index = CpMediaRealm_MediaRealmName, CpMediaRealm_IPv4IF, CpMediaRealm_IPv6IF, CpMediaRealm_PortRangeStart, CpMediaRealm_MediaSessionLeg, CpMediaRealm_PortRangeEnd, CpMediaRealm_IsDefault, CpMediaRealm_QoeProfile, CpMediaRealm_BWProfile; [ \CpMediaRealm ] For a detailed description of the table, see ''Configuring Media Realms'' on page 319. Remote Media Subnet Table Version 7.0 Mediant 3000...

  • Page 892: General Sip Parameters

    Mediant 3000 Parameter Description Remote Media Subnet Defines Remote Media Subnets. The format of the ini file table parameter is as follows: [SubRealm] [RemoteMediaSubnet] FORMAT RemoteMediaSubnet_Index = RemoteMediaSubnet_Realm, RemoteMediaSubnet_RemoteMediaSubnetIndex, RemoteMediaSubnet_RemoteMediaSubnetName, RemoteMediaSubnet_PrefixLength, RemoteMediaSubnet_AddressFamily, RemoteMediaSubnet_DstIPAddress, RemoteMediaSubnet_QOEProfileName, RemoteMediaSubnet_BWProfileName; [\RemoteMediaSubnet] For a detailed description of the table, see ''Configuring Remote Media Subnets'' on page 322.
  • Page 893 (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. Max SIP Message Length Defines the maximum size (in Kbytes) for each SIP message that can be [KB] sent over the network.
  • Page 894 Mediant 3000 Parameter Description Verify Received Enables the device to reject SIP requests (such as ACK, BYE, or re- RequestURI INVITE) whose user part in the Request-URI is different from the user part received in the Contact header of the last sent SIP request.
  • Page 895 When disabled, the device sends additional 18x responses as a result of receiving Alerting and Progress messages, regardless of whether or not a 18x response was already sent. Note: The parameter is applicable only if the EnableEarlyMedia Version 7.0 Mediant 3000...
  • Page 896 Mediant 3000 Parameter Description parameter is set to 1 (i.e., enabled). 183 Message Behavior Defines the ISDN message that is sent when the 183 Session Progress message is received for IP-to-Tel calls.  [0] Progress = (Default) The device sends a Progress message.
  • Page 897 The valid value range is 2000 to 4000. The default is 2000. [TDMoIPInviteRetryTime] Defines the time (in msec) between call release and a new INVITE when implementing the TDM tunneling application. The valid value range is 30,000 to 60,000. The default is 30,000. Version 7.0 Mediant 3000...
  • Page 898 Mediant 3000 Parameter Description Fax Signaling Method Global parameter that defines the SIP signaling method for establishing and transmitting a fax session when the device detects a fax. You can also configure this functionality per specific calls, using IP Profiles [IsFaxUsed] (IpProfile_IsFaxUsed).
  • Page 899 For the SAS application, this feature is configured using the SASConnectionReuse parameter. Fake TCP alias Enables the re-use of the same TCP/TLS connection for sessions with the same user, even if the "alias" parameter is not present in the SIP Via Version 7.0 Mediant 3000...
  • Page 900 Mediant 3000 Parameter Description header of the first INVITE.  [FakeTCPalias] [0] Disable = (Default) TCP/TLS connection reuse is done only if the "alias" parameter is present in the Via header of the first INVITE.  [1] Enable Note: To enable TCP/TLS connection re-use, set the EnableTCPConnectionReuse parameter to 1.
  • Page 901 Determines whether the SIP 'tgrp' parameter is used. This SIP parameter specifies the Trunk Group to which the call belongs (according to RFC 4904). For example, the SIP message below [UseSIPTgrp] indicates that the call belongs to Trunk Group ID 1: Version 7.0 Mediant 3000...
  • Page 902 Mediant 3000 Parameter Description INVITE sip::+16305550100;tgrp=1;trunk- context=example.com@10.1.0.3;user=phone SIP/2.0  [0] Disable = (Default) The 'tgrp' parameter isn't used.  [1] Send Only = The Trunk Group number or name (configured in the Trunk Group Settings table) is added to the 'tgrp' parameter value in the Contact header of outgoing SIP messages.
  • Page 903 Determines whether the Globally Routable User Agent URIs (GRUU) mechanism is used, according to RFC 5627. This is used for obtaining a GRUU from a registrar and for communicating a GRUU to a peer within [EnableGRUU] a dialog. Version 7.0 Mediant 3000...
  • Page 904 Mediant 3000 Parameter Description  [0] Disable (default)  [1] Enable A GRUU is a SIP URI that routes to an instance-specific UA and can be reachable from anywhere. There are a number of contexts in which it is desirable to have an identifier that addresses a single UA (using GRUU) rather than the group of UA’s indicated by an Address of Record (AOR).
  • Page 905 When configured, the string <UserAgentDisplayInfo value>/software version' is used, for example: [UserAgentDisplayInfo] User-Agent: myproduct/v.6.80A.227.005 If not configured, the default string, <AudioCodes product- name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 3000/v.6.80A.227.005 The maximum string length is 50 characters.
  • Page 906 Mediant 3000 Parameter Description [SendAllCodersOnRetriev call was first established and then put on-hold.  [1] Enable = Includes all supported coders in the SDP of the re- INVITE sent to the call made un-hold (retrieved). The used coder is therefore, re-negotiated.
  • Page 907 [1] To header = Obtains the destination number from the user part of the To header.  [2] P-Called-Party-ID header = Obtains the destination number from the P-Called-Party-ID header. Enable Reason Header Enables the usage of the SIP Reason header. Version 7.0 Mediant 3000...
  • Page 908 Mediant 3000 Parameter Description  [0] Disable  [1] Enable (default) [EnableReasonHeader] Gateway Name Defines a name for the device (e.g., device123.com). This name is 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 909 If the Via header includes the 'rport' parameter without a port value, the destination port of the response is the source port of the incoming request. If the Via header includes 'rport' with a port value (e.g., rport=1001), the Version 7.0 Mediant 3000...
  • Page 910 Mediant 3000 Parameter Description destination port of the response is the port indicated in the 'rport' parmeter. Enable X-Channel Header Determines whether the SIP X-Channel header is added to SIP messages for providing information on the physical Trunk/B-channel on which the call is received or placed.
  • Page 911 Microsoft's application) with the URI user part as INVITE sip:622125519100;ext=104@10.1.1.10 (or INVITE tel:622125519100;ext=104). If the parameter EnableMicrosofExt is enabled, the device modifies the called number by adding an "e" as the prefix, removing the "ext=" parameter, and adding the extension number Version 7.0 Mediant 3000...
  • Page 912 Mediant 3000 Parameter Description as the suffix (e.g., e622125519100104). Once modified, the device can then manipulate the number further, using the Number Manipulation tables to leave only the last 3 digits (for example) for sending to a PBX. [UseSIPURIForDiversionH Defines the URI format in the SIP Diversion header.
  • Page 913 The port is the same port as the local RTP port (configured by the BaseUDPPort parameter and the channel on which the call is received).  [0] Disable (default)  [1] Transmit & Receive = Send and receive RTP packets. Version 7.0 Mediant 3000...
  • Page 914 Mediant 3000 Parameter Description  [2] Transmit Only= Send RTP packets only.  [3] Receive Only= Receive RTP packets only. Notes:  To activate the RTP Only feature without using ISDN / CAS signaling, you must do the following: ...
  • Page 915 Keep-Alive mechanism) and no other alternative route exists to send the call.  The IP Connectivity mechanism is enabled (using the AltRoutingTel2IPEnable parameter) and there is no connectivity to any destination IP address. Notes:  The Busy Out behavior depends on the PSTN protocol type. Version 7.0 Mediant 3000...
  • Page 916 Mediant 3000 Parameter Description  The Busy Out condition is also applied per Trunk Group. This occurs if there is no connectivity to the Serving IP Group of a specific Trunk Group (configured in the Trunk Group Settings table). In such a scenario, all the physical trunks of the Trunk Group are set to the Busy Out condition.
  • Page 917 - Fully configured trunk (all channels): The device rejects new incoming calls and only takes the D-channel down. - Partially configured trunk (only some channels configured): The device rejects new incoming calls and sends out-of-service Service messages to all the configured channels (D-channel remains up). Version 7.0 Mediant 3000...
  • Page 918 Mediant 3000 Parameter Description  Graceful out-of-service enabled: The device rejects new incoming calls and does the following: - Fully configured trunk (all channels): > If all channels are idle when the graceful period begins, the device immediately takes the channels out-of-service without sending out-of-service Service messages and instead, only takes the D-channel down.
  • Page 919 SIP message starts with SipT1Rtx and is multiplied by two until SipT2Rtx. SIP Maximum RTX Defines the maximum number of UDP transmissions of SIP messages (first transmission plus retransmissions). The range is 1 to 30. The default is 7. [SIPMaxRtx] Version 7.0 Mediant 3000...

  • Page 920: Coders And Profile Parameters

    Mediant 3000 Parameter Description Number of RTX Before Defines the number of retransmitted INVITE/REGISTER messages Hot-Swap before the call is routed (hot swap) to another Proxy/Registrar. The valid range is 1 to 30. The default is 3. [HotSwapRtx] For example, if configured to 3 and no response is received from an IP destination, the device attempts another three times to send the call to the IP destination.
  • Page 921 IpProfile_EnableEchoCanceller, IpProfile_CopyDest2RedirectNumber, IpProfile_MediaSecurityBehaviour, IpProfile_CallLimit, IpProfile_DisconnectOnBrokenConnection, IpProfile_FirstTxDtmfOption, IpProfile_SecondTxDtmfOption, IpProfile_RxDTMFOption, IpProfile_EnableHold, IpProfile_InputGain, IpProfile_VoiceVolume, IpProfile_AddIEInSetup, IpProfile_SBCExtensionCodersGroupID, IpProfile_MediaIPVersionPreference, IpProfile_TranscodingMode, IpProfile_SBCAllowedMediaTypes, IpProfile_SBCAllowedCodersGroupID, IpProfile_SBCAllowedVideoCodersGroupID, IpProfile_SBCAllowedCodersMode, IpProfile_SBCMediaSecurityBehaviour, IpProfile_SBCRFC2833Behavior, IpProfile_SBCAlternativeDTMFMethod, IpProfile_SBCAssertIdentity, IpProfile_AMDSensitivityParameterSuit, IpProfile_AMDSensitivityLevel, IpProfile_AMDMaxGreetingTime, IpProfile_AMDMaxPostSilenceGreetingTime, IpProfile_SBCDiversionMode, IpProfile_SBCHistoryInfoMode, IpProfile_EnableQSIGTunneling, IpProfile_SBCFaxCodersGroupID, IpProfile_SBCFaxBehavior, IpProfile_SBCFaxOfferMode, IpProfile_SBCFaxAnswerMode, IpProfile_SbcPrackMode, IpProfile_SBCSessionExpiresMode, Version 7.0 Mediant 3000...
  • Page 922 Mediant 3000 Parameter Description IpProfile_SBCRemoteUpdateSupport, IpProfile_SBCRemoteReinviteSupport, IpProfile_SBCRemoteDelayedOfferSupport, IpProfile_SBCRemoteReferBehavior, IpProfile_SBCRemote3xxBehavior, IpProfile_SBCRemoteMultiple18xSupport, IpProfile_SBCRemoteEarlyMediaResponseType, IpProfile_SBCRemoteEarlyMediaSupport, IpProfile_EnableSymmetricMKI, IpProfile_MKISize, IpProfile_SBCEnforceMKISize, IpProfile_SBCRemoteEarlyMediaRTP, IpProfile_SBCRemoteSupportsRFC3960, IpProfile_SBCRemoteCanPlayRingback, IpProfile_EnableEarly183, IpProfile_EarlyAnswerTimeout, IpProfile_SBC2833DTMFPayloadType, IpProfile_SBCUserRegistrationTime, IpProfile_ResetSRTPStateUponRekey, IpProfile_AmdMode, IpProfile_SBCReliableHeldToneSource, IpProfile_GenerateSRTPKeys, IpProfile_SBCPlayHeldTone, IpProfile_SBCRemoteHoldFormat, IpProfile_SBCRemoteReplacesBehavior, IpProfile_SBCSDPPtimeAnswer, IpProfile_SBCPreferredPTime, IpProfile_SBCUseSilenceSupp, IpProfile_SBCRTPRedundancyBehavior, IpProfile_SBCPlayRBTToTransferee, IpProfile_SBCRTCPMode, IpProfile_SBCJitterCompensation, IpProfile_SBCRemoteRenegotiateOnFaxDetection, IpProfile_JitterBufMaxDelay, IpProfile_SBCUserBehindUdpNATRegistrationTime, IpProfile_SBCUserBehindTcpNATRegistrationTime,...

  • Page 923: Channel Parameters

    Determines the bit ordering of the G.726 voice payload format.  [VoicePayloadFormat] [0] = (Default) Little Endian  [1] = Big Endian Note: To ensure high voice quality when using G.726, both communicating ends should use the same endianness format. Version 7.0 Mediant 3000...
  • Page 924 Mediant 3000 Parameter Description Therefore, when the device communicates with a third-party entity that uses the G.726 voice coder and voice quality is poor, change the settings of the parameter (between Big Endian and Little Endian). MF Transport Type Currently, not supported.

  • Page 925: Coder Parameters

    Currently, not supported. [AnswerDetectorRedirection] Answer Detector Sensitivity Defines the Answer Detector sensitivity. The range is 0 (most sensitive) to 2 (least sensitive). The default is [AnswerDetectorSensitivity] 58.9.2 Coder Parameters The coder parameters are described in the table below. Version 7.0 Mediant 3000...
  • Page 926 Mediant 3000 Table 58-38: Coder Parameters Parameter Description G729EV local MBS Defines the maximal bit rate (in kilobits per second - Kbps) that can be used by the G.729EV coder for a specific channel. The [G729EVLocalMBS] parameter is defined per channel and may vary between the parties.
  • Page 927  [AmrOctetAlignedEnable] [0] Bandwidth Efficient  [1] Octet Aligned (default) Note: The AMR payload type can also be configured per Coder Group (see Configuring Coder Groups on page 385). The Coder Group configuration overrides the parameter. Version 7.0 Mediant 3000...
  • Page 928 Mediant 3000 Parameter Description [AMRCoderHeaderFormat] Determines the payload format of the AMR header.  [0] = Non-standard multiple frames packing in a single RTP frame. Each frame has a CMR and TOC header.  [1] = AMR frame according to RFC 3267 bundling.

  • Page 929: Dtmf Parameters

    The valid range is -10 to 10 dB. The default is 0 dB. Note: For the parameter to take effect, a device reset is required. Defines the time (in msec) between generated DTMF digits to the Tel side (if FirstTxDTMFOption = 1, 2 or 3). [DTMFInterDigitInterval] Version 7.0 Mediant 3000...

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

    Mediant 3000 Parameter Description The valid range is 0 to 32767. The default is 100. [DTMFDigitLength] Defines the time (in msec) for generating DTMF tones to the Tel side (if FirstTxDTMFOption = 1, 2 or 3). It also configures the duration that is sent in INFO (Cisco) messages.
  • Page 931 [EnableDetectRemoteMACCha Determines whether the device changes the RTP packets nge] according to the MAC address of received RTP packets and according to Gratuitous Address Resolution Protocol (GARP) messages. Version 7.0 Mediant 3000...
  • Page 932 Mediant 3000 Parameter Description  [0] = Nothing is changed.  [1] = If the device receives RTP packets with a different source MAC address (than the MAC address of the transmitted RTP packets), then it sends RTP packets to this MAC address and removes this IP entry from the device's ARP cache table.
  • Page 933 RTCPInterval.  [0] Disable = (Default) Randomize [DisableRTCPRandomize]  [1] Enable = No Randomize Defines the transport layer used for outgoing SIP dialogs initiated by the device to the RTCP XR Collection Server. [RTCPXRESCTransportType] Version 7.0 Mediant 3000...
  • Page 934 Mediant 3000 Parameter Description  [-1] Not Configured (default)  [0] UDP  [1] TCP  [2] TLS Notes:  When set to [-1], the value of the SIPTransportType parameter is used.  The parameter is applicable only to the Gateway application.

  • Page 935: Gateway Application Parameters

    [3] Events Only = Transparent with Events. Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 391. V.32 Modem Transport Type Determines the V.32 modem transport type. Version 7.0 Mediant 3000...
  • Page 936 Mediant 3000 Parameter Description  [0] Disable = Transparent.  [2] Enable Bypass (default) [V32ModemTransportType]  [3] Events Only = Transparent with Events. Notes:  The parameter applies only to V.32 and V.32bis modems.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType).
  • Page 937  [7] 19200bps = 19.2 kbps  [8] 21600bps = 21.6 kbps  [9] 24000bps = 24 kbps  [10] 26400bps = 26.4 kbps  [11] 28800bps = 28.8 kbps  [12] 31200bps = 31.2 kbps Version 7.0 Mediant 3000...
  • Page 938 Mediant 3000 Parameter Description  [13] 33600bps = 33.6 kbps (default) Notes:  The rate is negotiated between both sides (i.e., the device adapts to the capabilities of the remote side). Negotiation of the T.38 maximum supported fax data rate is provided in SIP’s SDP T38MaxBitRate parameter.
  • Page 939 T38 must be different. Therefore, set the T38UseRTPPort parameter to 0. T.38 Max Datagram Size Defines the maximum size of a T.38 datagram that the device can receive. This value is included in the outgoing SDP when T.38 is Version 7.0 Mediant 3000...
  • Page 940 Mediant 3000 Parameter Description [T38MaxDatagramSize] used. The valid range is 120 to 600. The default is 560. T38 Fax Max Buffer Defines the maximum size (in bytes) of the device's T.38 buffer. This value is included in the outgoing SDP when T.38 is used for fax relay over IP.
  • Page 941 The value range is 8 to 32. The default is 8. [V1501SPRTTransportChannel 2MaxWindowSize] SPRT Transport Ch.3 Max Defines the maximum payload size for V.150.1 SPRT Transport Payload Size Channel 3. The range is 140 to 256. The default is 140. [V1501SPRTTransportChannel 3MaxPayloadSize] Version 7.0 Mediant 3000...

  • Page 942: Dtmf And Hook-Flash Parameters

    Mediant 3000 58.10.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below. Table 58-42: DTMF and Hook-Flash Parameters Parameter Description Hook-Flash Parameters Hook-Flash Code Defines the digit pattern used by the PBX to indicate a Hook Flash event.
  • Page 943 Note: You can also configure the parameter per specific calls, using IP Profiles (IpProfile_SecondTxDtmfOption). For configuring IP Profiles, see ''Configuring IP Profiles'' on page 391. [DisableAutoDTMFMute] Enables the automatic muting of DTMF digits when out-of-band DTMF transmission is used. Version 7.0 Mediant 3000...
  • Page 944 Mediant 3000 Parameter Description  [0] = (Default) Automatic mute is used.  [1] = No automatic mute of in-band DTMF. When the parameter is set to 1, the DTMF transport type is set according to the parameter DTMFTransportType and the DTMF digits aren't muted if out-of-band DTMF mode is selected (FirstTxDTMFOption set to 1, 2 or 3).

  • Page 945: Digit Collection And Dial Plan Parameters

    Defines the Dial Plan index in the external Dial Plan file for the Tel- to-IP Source Number Mapping feature. [Tel2IPSourceNumberMapping DialPlanIndex] The valid value range is 0 to 7, defining the Dial Plan index [Plan x] in the Dial Plan file. The default is -1 (disabled). Version 7.0 Mediant 3000...
  • Page 946 Mediant 3000 Parameter Description For more information on this feature, see ''Modifying ISDN-to-IP Calling Party Number using Dial Plan File'' on page 689. Digit Mapping Rules Defines the digit map pattern (used to reduce the dialing period when ISDN overlap dialing). If the digit string (i.e., dialed number)

  • Page 947: Voice Mail Parameters

    Upon receipt of an ISDN Setup message with Redirect values, the device maps the Redirect phone number to the SIP 'target' parameter and the Redirect number reason to the SIP 'cause' parameter in the Request-URI. Redirecting Reason >> SIP Response Code Unknown >> 404 Version 7.0 Mediant 3000...
  • Page 948 Mediant 3000 Parameter Description User busy >> 486 No reply >> 408 Deflection >> 487/480 Unconditional >> 302 Others >> 302 If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason.
  • Page 949 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 7.0 Mediant 3000...
  • Page 950 Mediant 3000 Parameter Description Forward on Busy Digit Defines the digit pattern used by the PBX to indicate 'call forward on Pattern (Internal) busy' when the original call is received from an internal extension. The valid range is a 120-character string.

  • Page 951: Supplementary Services Parameters

    The 200 OK response can contain the connected party CallerID - Connected Number and Connected Name. For example, if the call is answered by the device, the 200 OK response includes the P-Asserted- Identity with Caller ID. The device interworks (in some ISDN variants), Version 7.0 Mediant 3000...

  • Page 952: Call Waiting Parameters

    Mediant 3000 Parameter Description the Connected Party number and name from Q.931 Connect message to SIP 200 OK with the P-Asserted-Identity 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.

  • Page 953: Call Hold Parameters

    [-1] = (Default) The call is placed on hold indefinitely until the initiator of the on hold retrieves the call again.  [0 - 2400] = Time to wait (in seconds) after which the call is released. Version 7.0 Mediant 3000...

  • Page 954: Call Transfer Parameters

    Mediant 3000 Parameter Description Determines whether the device sends DTMF signals (or DTMF SIP INFO message) when a call is on hold. [PlayDTMFduringHold]  [0] = (Default) Disable.  [1] = Enable - If the call is on hold, the device stops playing the Held tone (if it is played) and sends DTMF: ...

  • Page 955: Mlpp And Emergency Call Parameters

    Table 58-50: MLPP and Emergency E911 Call Parameters Parameter Description Call Priority Mode Defines priority call handling, for all calls.  [0] Disable (default).  [1] MLPP = MLPP Priority Call handling is enabled. MLPP prioritizes [CallPriorityMode] Version 7.0 Mediant 3000...
  • Page 956 Mediant 3000 Parameter Description call handling whereby the relative importance of various kinds of communications is strictly defined, allowing higher precedence communication at the expense of lower precedence communications. Higher priority calls override less priority calls when, for example, congestion occurs in a network.
  • Page 957 The format of this table ini file parameter is as follows: FORMAT ResourcePriorityNetworkDomains_Index = ResourcePriorityNetworkDomains_Name, ResourcePriorityNetworkDomains_EnableIp2TelInterworking; ResourcePriorityNetworkDomains 1 = dsn, 0; ResourcePriorityNetworkDomains 2 = dod, 0; ResourcePriorityNetworkDomains 3 = drsn, 0; ResourcePriorityNetworkDomains 5 = uc, 1; ResourcePriorityNetworkDomains 7 = cuc, 0; [ \ResourcePriorityNetworkDomains ] Version 7.0 Mediant 3000...
  • Page 958 Mediant 3000 Parameter Description Notes:  Indices 1, 2, 3, 5, and 7 cannot be modified and are defined for DSN, DOD, DRSN, UC, and CUC, respectively.  If the MLPPDefaultNamespace parameter is set to -1, interworking from PSTN NI digits is done automatically.
  • Page 959 Defines the RTP DSCP for MLPP Priority precedence call level. Priority 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 Version 7.0 Mediant 3000...

  • Page 960: Call Cut-Through Parameters

    Mediant 3000 Parameter Description [MLPPPriorityRTPDSCP] PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call. RTP DSCP for MLPP Defines the RTP DSCP for MLPP Immediate precedence call level. Immediate The valid range is -1 to 63. The default is -1.

  • Page 961: Tty/Tdd Parameters

    Table 58-53: Char Conversion Table Parameters Char Conversion Table Char Conversion Defines Unicode-to-ASCII character conversion rules. The format of the ini file table parameter is as follows: [CharConversion] [CharConversion] FORMAT CharConversion_Index = CharConversion_CharName, CharConversion_FirstByte, CharConversion_SecondByte, CharConversion_ConvertedOutput; Version 7.0 Mediant 3000...

  • Page 962: Pstn Parameters

    Mediant 3000 Char Conversion Table [\CharConversion] For a detailed description of the table, see ''Converting Accented Characters from IP to Tel'' on page 542. 58.10.6 PSTN Parameters This subsection describes the device's PSTN parameters. 58.10.6.1 General Parameters The general PSTN parameters are described in the table below.
  • Page 963 PRI protocols on different E1/T1 spans (no more than four simultaneous PRI variants). [ProtocolType_x] Defines the protocol type for a specific trunk ID (where x denotes the Trunk ID and 0 is the first trunk). For more information, see the ProtocolType parameter. Version 7.0 Mediant 3000...
  • Page 964 Mediant 3000 Parameter Description [ISDNTimerT310] Defines the T310 override timer for DMS, Euro ISDN, and ISDN NI- 2 variants. An ISDN timer is started when a Q.931 Call Proceeding message is received. The timer is stopped when a Q.931 Alerting, Connect, or Disconnect message is received from the other end.
  • Page 965 The parameter is applicable only to E1/T1 interfaces. [ClockMaster_x] Same as the description for parameter ClockMaster, but for a specific Trunk ID (where x denotes the Trunk ID and 0 is the first Trunk). Note: The parameter is applicable only to E1/T1 interfaces. Version 7.0 Mediant 3000...
  • Page 966 Mediant 3000 Parameter Description Line Code Selects B8ZS or AMI for T1 spans, and HDB3 or AMI for E1 spans.  [0] B8ZS = (Default) B8ZS line code (for T1 trunks only).  [1] AMI = AMI line code. [LineCode] ...

  • Page 967: Tdm Bus And Clock Timing Parameters

     [4] North European  [5] Cyrillic  [6] Arabic  [7] Hebrew  [8] Turkish 58.10.6.2 TDM Bus and Clock Timing Parameters The TDM Bus and clock timing parameters are described in the table below. Version 7.0 Mediant 3000...
  • Page 968 Mediant 3000 Table 58-55: TDM Bus and Clock Timing Parameters Parameter Description TDM Bus and BITS (Timing) Parameters TDM Bus Type Defines the TDM bus interface.  [TDMBusType] [2] Framers (default)  [4] H110 Note: Only one TDM bus interface can be enabled at a time, although more than one can physically exist on the device.
  • Page 969 TDMBusLocalReference. Notes:  For the parameter to take effect, a device reset is required.  The parameter is applicable only if the TDMBusClockSource parameter is set to 4. Version 7.0 Mediant 3000...
  • Page 970 Mediant 3000 Parameter Description TDM Bus PSTN Auto Clock Enables the PSTN trunk Auto-Fallback Reverting feature. If Reverting enabled and a trunk returning to service has an AutoClockTrunkPriority parameter value that is higher than the [TDMBusPSTNAutoClockRever priority of the local reference trunk (set in the...
  • Page 971 58. Configuration Parameters Reference Parameter Description parameter TMMode).  The parameter is applicable to Mediant 3000 systems housing TP-8410 blades. For Mediant 3000 systems housing TP-6310 blades, configure the parameter to [0] to use a 12 ppm reference. Timing Module Mode Determines the device's Timing Synchronization mode.

  • Page 972: Cas Parameters

    Mediant 3000 Parameter Description [TMReferenceValidationTime] resolution is 1 minute. Note: The parameter is applicable only for External timing (i.e., BITS) and Line timing references (refer to the parameter TMMode). 58.10.6.3 CAS Parameters The Common Channel Associated (CAS) parameters are described in the table below.
  • Page 973 To configure the parameter, the trunk must first be stopped.  Only one of these formats can be implemented; not both.  When the parameter is not configured, a single CAS table for the entire trunk is used, configured by the parameter Version 7.0 Mediant 3000...

  • Page 974: Isdn Parameters

    Mediant 3000 Parameter Description CASTableIndex. [CASTablesNum] Defines how many CAS protocol configurations files are loaded. The valid range is 1 to 8. Note: For the parameter to take effect, a device reset is required. CAS State Machines Parameters Note: For configuring the CAS State Machine table using the Web interface, see ''Configuring CAS State Machines'' on page 439.
  • Page 975 Determines the bit-field used to determine several behavior options that influence how the ISDN Stack INCOMING calls behave.  [32] DATA CONN RS = The device automatically sends a [ISDNInCallsBehavior] Q.931 Connect (answer) message on incoming Tel calls (Q.931 Setup). Version 7.0 Mediant 3000...
  • Page 976 Mediant 3000 Parameter Description  [64] VOICE CONN RS = The device sends a Connect (answer) message on incoming Tel calls.  [2048] CHAN ID IN FIRST RS = (Default) The device sends Channel ID in the first response to an incoming Q.931 Call Setup message.
  • Page 977 ECMA standards); otherwise, OBJECT IDENTIFIER ASN.1 type is used. Note: This option is applicable only to QSIG.  [2147483648] 5ESS National Mode For Bch Maintenance = Use the National mode of AT&T 5ESS for B-channel maintenance. Notes: Version 7.0 Mediant 3000...
  • Page 978 Mediant 3000 Parameter Description  To configure the device to support several ISDNIBehavior features, enter a summation of the individual feature values. For example, to support both [512] and [2048] features, set the parameter ISDNIBehavior is set to 2560 (i.e., 512 + 2048).
  • Page 979 (i.e., 0- 9,*,#).  [16384] DLCI REVERSED OPTION = Behavior bit used in the IUA interface groups to indicate that the reversed format of the DLCI field must be used. Version 7.0 Mediant 3000...
  • Page 980 Mediant 3000 Parameter Description 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 981: Ds3 Parameters

    For more information on NFAS, see ISDN Non-Facility Associated Signaling (NFAS) on page 448. 58.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 58-58: DS3 Parameters Parameter Description DS3 Settings Table [DS3Config] Defines the DS3 (T3) interfaces.

  • Page 982: Sdh/Sonet Parameters

    [1] Up = (Default) Administrative status Up.  [2] Down = Administrative status Down (currently, not supported). 58.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. User's Manual Document #: LTRT-89730...
  • Page 983 For the parameter to take effect, a device reset is required.  The setting of the parameter should be in coordination with the parameters SDHFbrGrp_SDHSONETMode and ProtocolType.  The parameter is applicable only when TDMBusType = acFRAMERS (2) and PSTNTransmissionType = Optical SONET Version 7.0 Mediant 3000...
  • Page 984 Mediant 3000 Parameter Description or SDH Transmission type(1).  When option [3] is selected, the clock source is automatically set to 'Local Board' (synchronization supplied by device) and cannot be changed.  For more details regarding the parameter, see the SDHFbrGrp_SdhSonetMode parameter.

  • Page 985: Isdn And Cas Interworking Parameters

     For the parameter to take effect, a device reset is required.  The parameter is applicable only to Mediant 3000/TP-6310.  The parameter is applicable only if the TDMBusType parameter is set to acFRAMERS (2), and PSTNTransmissionType is set to Optical SONET or SDH Transmission type (1).
  • Page 986 Mediant 3000 Parameter Description the SIP 200 OK includes the Date header, the device ignores its value. Notes:  This feature is applicable only to Tel-to-IP calls.  For IP-to-Tel calls, the parameter is not applicable. Only if the incoming ISDN Connect message contains the Date / Time IE does the device add the Date header to the sent SIP 200 OK message.
  • Page 987 Connect message to the ISDN (for Tel-to-IP calls). This is interworked from the P-Asserted-Identity header in SIP 200 The default is [0] (i.e., unknown). Enable ISDN Tunneling Enables ISDN Tunneling. Version 7.0 Mediant 3000...
  • Page 988 Mediant 3000 Parameter Description  [0] Disable (default). Tel to IP  [1] Using Header = Enable ISDN Tunneling from ISDN PRI to SIP using a proprietary SIP header. [EnableISDNTunnelingTe  [2] Using Body = Enable ISDN Tunneling from ISDN PRI to SIP using l2IP] a dedicated message body.
  • Page 989 ISDN Setup message). This feature is applicable only for IP-to-ISDN calls. 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, Version 7.0 Mediant 3000...
  • Page 990 Mediant 3000 Parameter Description 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 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"...
  • Page 991 [0] = (Default) SIP header format: X-UserToUser.  [1] = SIP header format: User-to-User with Protocol Discriminator (pd) attribute (according to IETF Internet-Draft draft-johnston-sipping-cc- uui-04). For example: User-to- User=3030373435313734313635353b313233343b3834;pd=4  [2] = SIP header format: User-to-User with encoding=hex at the end Version 7.0 Mediant 3000...
  • Page 992 Mediant 3000 Parameter Description and pd embedded as the first byte (according to IETF Internet-Draft draft-johnston-sipping-cc-uui-03). For example: User-to- User=043030373435313734313635353b313233343b3834; encoding=hex where "04" at the beginning of this message is the pd.  [3] = Interworks the SIP User-to-User header containing text format to ISDN UUIE in hexadecimal format, and vice versa.
  • Page 993 The option Any is applicable only if TerminationSide is set to 0 (i.e., User side).  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Enables the device to send an ISDN SERVice message per trunk upon Version 7.0 Mediant 3000...
  • Page 994 Mediant 3000 Parameter Description [SendISDNServiceAfterR device reset. The messsage (transmitted on the trunk's D-channel) estart] indicates the availability of the trunk's B-channels (i.e., trunk in service).  [0] = Disable (default)  [0] = Enable [SupportRedirectInFacility Determines whether the Redirect Number is retrieved from the Facility IE.
  • Page 995 When enabled, the From header received in the SIP INVITE is translated into the following ISDN IE's:  Emergency Call Control.  Generic Information - to carry the Location Identification Number information.  Generic Information - to carry the Calling Geodetic Location information. Version 7.0 Mediant 3000...
  • Page 996 Mediant 3000 Parameter Description Note: This capability is applicable only to the NI-2 ISDN variant. Global parameter that defines the duration (in seconds) that the device waits for an ISDN Connect message from the called party (Tel side), [EarlyAnswerTimeout] started from when it sends a Setup message. You can also configure this functionality per specific calls, using IP Profiles (IpProfile_EarlyAnswerTimeout).
  • Page 997 Note: For configuring trunk transfer mode per trunk, use the parameter TrunkTransferMode_x. [TrunkTransferMode_x] Determines the trunk transfer mode per trunk (where x denotes the Trunk number). For configuring trunk transfer mode for all trunks and for a description of the parameter options, refer to the parameter Version 7.0 Mediant 3000...
  • Page 998 Mediant 3000 Parameter Description TrunkTransferMode. [EnableTransferAcrossTr Determines whether the device allows ISDN ECT, RLT or TBCT IP-to-Tel unkGroups] call transfers between B-channels of different Trunk Groups.  [0] = (Default) Disable - ISDN call transfer is only between B-channels of the same Trunk Group.
  • Page 999 CAS trunk. The CAS wink signal is done by changing the A bit from 1 to 0, and then back to 1 for 450 msec. INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: <sip:06@192.168.13.2:5060> To: <sip:4505656002@192.168.13.40:5060>;tag=132878796- 1040067870294 Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2 CSeq:2 INFO Content-Type: application/broadsoft Version 7.0 Mediant 3000...

  • Page 1000: Answer And Disconnect Supervision Parameters

    Mediant 3000 Parameter Description Content-Length: 17 event flashhook Note: The parameter is applicable only to T1 CAS protocols. Release Cause Mapping from ISDN to SIP Table Release Cause Mapping This table parameter maps ISDN Q.850 Release Causes to SIP Table responses.
  • Page 1001 The default is 100 (i.e., 10000 msec or 10 seconds). [BrokenConnectionEvent Timeout] Notes:  The parameter is applicable only if the parameter DisconnectOnBrokenConnection is set to 1.  Currently, this feature functions only if Silence Suppression is disabled. Version 7.0 1001 Mediant 3000...
  • Page 1002 Mediant 3000 Parameter Description Disconnect Call on Determines whether calls are disconnected after detection of silence. Silence Detection  [1] Yes = The device disconnects calls in which silence occurs (in both call directions) for more than a user-defined time.

  • Page 1003: Tone Parameters

    Note: To enable the Cut-Through feature, use the DigitalCutThrough (for CAS channels) parameter. Play Busy Tone to Tel Enables the device to play a busy or reorder tone to the PSTN after Version 7.0 1003 Mediant 3000...
  • Page 1004 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. The parameter can be configured with up to 10 release codes.
  • Page 1005 Note: The parameter is applicable only to the Gateway application. Play Ringback Tone to Trunk Determines the playing method of the ringback tone to the trunk side, per trunk.  [-1] Not configured = (Default) The settings of the Version 7.0 1005 Mediant 3000...
  • Page 1006 Mediant 3000 Parameter Description [PlayRBTone2Trunk_x] PlayRBTone2Tel parameter is used.  [0] Don't Play = When the device is configured for ISDN / CAS, it doesn't play a ringback tone. No Progress Indicator (PI) is sent to the ISDN unless the ProgressIndicator2ISDN_x parameter is configured differently.

  • Page 1007: Tone Detection Parameters

    Subscriber priority. The value range is 1 to 15 (defining one of the MFC R2 tones). The default is 1. 58.10.9.2 Tone Detection Parameters The signal tone detection parameters are described in the table below. Version 7.0 1007 Mediant 3000...
  • Page 1008 Mediant 3000 Table 58-63: Tone Detection Parameters Parameter Description Enables the detection of DTMF signaling.  [DTMFDetectorEnable] [0] = Disable  [1] = Enable (default) Enables the detection of MF-R1 signaling.  [MFR1DetectorEnable] [0] = Disable (default)  [1] = Enable [R1DetectionStandard] Determines the MF-R1 protocol used for detection.

  • Page 1009: Metering Tone Parameters

     [5] SIP 2 TEL INTERWORKING = Enables IP-to-Tel AOC, using AudioCodes' proprietary SIP header, AOC. Note: The parameter is applicable only to ISDN Euro trunks for sending AOC Facility messages (see Advice of Charge Services for Euro ISDN on page 537).

  • Page 1010: Trunk Groups And Routing Parameters

    Mediant 3000 Parameter Description FORMAT ChargeCode_Index = ChargeCode_EndTime1, ChargeCode_PulseInterval1, ChargeCode_PulsesOnAnswer1, ChargeCode_EndTime2, ChargeCode_PulseInterval2, ChargeCode_PulsesOnAnswer2, ChargeCode_EndTime3, ChargeCode_PulseInterval3, ChargeCode_PulsesOnAnswer3, ChargeCode_EndTime4, ChargeCode_PulseInterval4, ChargeCode_PulsesOnAnswer4; [\ChargeCode] Note:To associate a configured Charge Code to an outgoing Tel-to-IP call, use the Tel-to-IP Routing table. 58.10.10 Trunk Groups and Routing Parameters The routing parameters are described in the table below.
  • Page 1011 [2] Overwrite = The Tel Source Number is used as the IP Source Number and also as the IP Display Name (even if the received Tel Display Name is not empty).  [3] Original = Similar to option [2], except that the operation is Version 7.0 1011 Mediant 3000...
  • Page 1012 Mediant 3000 Parameter Description done before regular calling number manipulation. Use Display Name as Source Determines the use of Source Number and Display Name for IP-to- Number Tel calls.  [0] No = (Default) If IP Display Name is received, the IP Source...

Table of Contents