AudioCodes Mediant 500L MSBR User Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Network Router
  5. Mediant 500L MSBR
  6. User manual

AudioCodes Mediant 500L MSBR User Manual

Multi-service business router
Hide thumbs Also See for Mediant 500L MSBR:
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

See also: User Manual , Installation Manual
User's Manual
Multi-Service Business Router
Enterprise Session Border Controller
Mediant 500L MSBR
Version 6.8

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 500L MSBR

Summary of Contents for AudioCodes Mediant 500L MSBR

  • Page 1 User's Manual Multi-Service Business Router Enterprise Session Border Controller Mediant 500L MSBR Version 6.8...

  • Page 3: Table Of Contents

    8.3.1 Basic User Accounts Configuration .................65 8.3.2 Advanced User Accounts Configuration ..............67 Displaying Login Information upon Login .............. 71 Configuring Web Security Settings ............... 71 Limiting OAMP Access to a Specific WAN Interface ..........72 Version 6.8 Mediant 500L MSBR...
  • Page 4 Mediant 500L MSBR Web Login Authentication using Smart Cards............73 Configuring Web and Telnet Access List .............. 73 CLI-Based Management ..................75 Getting Familiar with CLI ..................75 9.1.1 Understanding Configuration Modes ...............75 9.1.2 Using CLI Shortcuts ....................76 9.1.3 Common CLI Commands ..................77 9.1.4...
  • Page 5 16.3.1 Enabling IDS ......................171 16.3.2 Configuring IDS Policies ..................171 16.3.3 Assigning IDS Policies ...................175 16.3.4 Viewing IDS Alarms ....................176 17 Media ........................ 179 17.1 Configuring Voice Settings ................. 179 17.1.1 Configuring Voice Gain (Volume) Control .............179 Version 6.8 Mediant 500L MSBR...
  • Page 6 Mediant 500L MSBR 17.1.2 Silence Suppression (Compression) ..............179 17.1.3 Configuring Echo Cancellation ................180 17.2 Fax and Modem Capabilities ................181 17.2.1 Fax/Modem Operating Modes ................181 17.2.2 Fax/Modem Transport Modes ................182 17.2.2.1 T.38 Fax Relay Mode ................182 17.2.2.2 G.711 Fax / Modem Transport Mode .............184 17.2.2.3 Fax Fallback ...................185...
  • Page 7 21.3.1 SIP Message Authentication Example ..............311 21.4 Configuring SIP Message Manipulation .............. 313 21.5 Configuring SIP Message Policy Rules............... 320 22 Coders and Profiles ..................323 22.1 Configuring Default Coders ................323 22.2 Configuring Coder Groups .................. 326 Version 6.8 Mediant 500L MSBR...
  • Page 8 Mediant 500L MSBR 22.3 Configuring Tel Profile ..................327 22.4 Configuring IP Profiles ..................332 Gateway Application .....................355 23 Introduction ..................... 357 24 Digital PSTN ..................... 359 24.1 Configuring Trunk Settings ................. 359 24.2 TDM and Timing ....................362 24.2.1 Configuring TDM Bus Settings ................362 24.2.2 Clock Settings ......................362...
  • Page 9 29.11.4 Enhanced 9-1-1 Support for Lync Server 2010 .............459 29.11.4.1 About E9-1-1 Services ................459 29.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........460 29.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 29.11.4.4 Configuring AudioCodes ELIN Gateway ..........469 29.12 Multilevel Precedence and Preemption ............... 472 29.12.1 MLPP Preemption Events in SIP Reason Header ..........474...
  • Page 10 Mediant 500L MSBR 30 Analog Gateway ....................485 30.1 Configuring Keypad Features ................485 30.2 Configuring Metering Tones ................487 30.3 Configuring FXO Settings ................... 488 30.4 Configuring Authentication .................. 489 30.5 Configuring Automatic Dialing ................490 30.6 Configuring Caller Display Information..............492 30.7 Configuring Call Forward ..................
  • Page 11 36.3 Configuring SBC IP-to-IP Routing ............... 564 36.4 Configuring SIP Response Codes for Alternative Routing Reasons ....573 37 SBC Manipulations ..................575 37.1 Configuring IP-to-IP Inbound Manipulations ............577 37.2 Configuring IP-to-IP Outbound Manipulations ............. 581 Cloud Resilience Package ..................587 Version 6.8 Mediant 500L MSBR...
  • Page 12 Mediant 500L MSBR 38 CRP Overview ....................589 39 CRP Configuration ..................591 39.1 Enabling the CRP Application ................591 39.2 Configuring Call Survivability Mode ..............592 39.3 Pre-Configured IP Groups .................. 593 39.4 Pre-Configured IP-to-IP Routing Rules ............... 594 39.4.1 Normal Mode ......................594...
  • Page 13 47.1.1 DHCP-based Provisioning ..................647 47.1.2 HTTP-based Provisioning ..................648 47.1.3 FTP-based Provisioning ..................649 47.1.4 Provisioning using AudioCodes EMS ..............649 47.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 650 47.2.1 Files Provisioned by Automatic Update ..............650 47.2.2 File Location for Automatic Update ...............651 47.2.3 Access Authentication with HTTP Server ..............652...
  • Page 14 57.1 Syslog Message Format ..................733 57.1.1 Event Representation in Syslog Messages ............734 57.1.2 Unique Device Identification in Syslog Messages ..........736 57.1.3 Identifying AudioCodes Syslog Messages using Facility Levels ......736 57.1.4 SNMP Alarms in Syslog Messages ...............737 57.2 Enabling Syslog ....................737 57.3 Configuring Web Operations to Report to Syslog ..........
  • Page 15 67.2.7 NTP and Daylight Saving Time Parameters ............802 67.3 Debugging and Diagnostics Parameters ............. 804 67.3.1 General Parameters ....................804 67.3.2 SIP Test Call Parameters ..................806 67.3.3 Syslog, CDR and Debug Parameters ..............807 67.3.4 Resource Allocation Indication Parameters............812 Version 6.8 Mediant 500L MSBR...
  • Page 16 Mediant 500L MSBR 67.3.5 PacketSmart Parameters..................813 67.4 Security Parameters ................... 814 67.4.1 General Security Parameters ................814 67.4.2 HTTPS Parameters ....................816 67.4.3 SRTP Parameters ....................817 67.4.4 TLS Parameters .....................820 67.4.5 SSH Parameters ....................822 67.4.6 TAACS+ Parameters .....................823 67.4.7 IDS Parameters .....................823 67.4.8 OCSP Parameters ....................825...
  • Page 17 67.14.3 Least Cost Routing Parameters ................1032 67.14.4 Call Setup Rules Parameters ................1033 68 SBC and DSP Channel Capacity ..............1035 68.1 Signaling-Media Sessions & User Registrations ..........1035 68.2 Channel Capacity and Capabilities ..............1037 69 Technical Specifications ................1039 Version 6.8 Mediant 500L MSBR...
  • Page 18 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 19: Weee Eu Directive

    Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our Web site at www.audiocodes.com/support.

  • Page 20: Related Documentation

    Mediant 500L MSBR Related Documentation Manual Name SIP CPE Release Notes Mediant 500L MSBR Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP User's Guide CWMP TR-069 & TR-104 Reference Guide SBC Design Guide...
  • Page 21 The device's installed Software License Key does not include the MSFT feature key, which enables the device to operate in a Microsoft Lync Server environment. If necessary, you can order this feature key separately from your AudioCodes sales representative. Notes: •...

  • Page 22: Document Revision Record

    Mediant 500L MSBR Document Revision Record LTRT Description 10460 Initial document release for Version 6.8. 10463 Screenshot updated for example of SIP message manipulation rules; available video coders not based on license key; AupdHttpUserAgent parameter updated; RFC updated for CDR Syslog message (RFC 3164); core dump procedure updated; HA Settings page screenshot updated for configuring HA;...

  • Page 23: Documentation Feedback

    User's Manual Notices 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. Version 6.8 Mediant 500L MSBR...
  • Page 24 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 25: Overview

    HTTP/S-based embedded Web server. The user-friendly Web interface allows remote configuration using any standard Web browser (such as Microsoft™ Internet Explorer™). Note: For maximum call capacity figures, see ''SBC and DSP Channel Capacity'' on page 1035. Version 6.8 Mediant 500L MSBR...
  • Page 26 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 27: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 29: Introduction

    IP address to correspond with your networking scheme. Device management can be done though the VoIP-LAN OAMP, WAN, and/or LAN interface. Note: By default, the device's embedded DHCP server is enabled. For more information, see Configuring the Device's DHCP Server on page 38. Version 6.8 Mediant 500L MSBR...
  • Page 30 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 31: Default Oamp Ip Address

    The table below lists the device's default IP address. Table 3-1: Default VoIP LAN IP Address for OAMP IP Address Value Application Type OAMP + Media + Control IP Address 192.168.0.2 Prefix Length 255.255.255.0 (24) Default Gateway 192.168.0.1 Underlying Device Interface Name "Voice" Version 6.8 Mediant 500L MSBR...
  • Page 32 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 33: Configuring Voip Lan Interface For Oamp

    Figure 4-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Open the Interface Table page (Configuration tab > VoIP menu > Network > IP Interfaces Table). Version 6.8 Mediant 500L MSBR...

  • Page 34: Cli

    Mediant 500L MSBR Select the 'Index' radio button corresponding to the OAMP + Media + Control application type, and then click Edit. Change the IP address to correspond with your network IP addressing scheme, for example: • IP Address: 10.8.6.86 •...
  • Page 35 Exit the VoIP configuration mode: (config-voip)# exit Reset the device with a flash burn: # reload now Cable the device to your network. You can now access the device's management interface using this new OAMP IP address. Version 6.8 Mediant 500L MSBR...
  • Page 36 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 37: Configuring Data-Router's Lan And Wan

    (config-data)# interface vlan 1 Configure the IP address and subnet: (conf-if-VLAN 1)# ip address <IP address> <subnet> For example: (conf-if-VLAN 1)# ip address 10.8.6.85 255.255.255.0 Save your settings with a flash burn: (conf-if-VLAN 1)# do write Version 6.8 Mediant 500L MSBR...

  • Page 38: Configuring The Device's Dhcp Server

    Mediant 500L MSBR Configuring the Device's DHCP Server By default, the device's embedded DHCP server is enabled for the LAN, and with default IP pool addresses relating to the default subnet LAN. You can disable the DHCP server, or modify the IP address pool. The DHCP server allocates this spool of IP addresses to the computers connected to its LAN interface.
  • Page 39 (config-if-GE 0/0)# no shutdown Exit the interface: (config-if-GE 0/0)# exit Configure the default route: (config-data)# ip route 0.0.0.0 0.0.0.0 100.33.2.106 GigabitEthernet 0/0 Exit the data-router configuration mode: (config-data)# exit Save the configuration to flash: # write Version 6.8 Mediant 500L MSBR...
  • Page 40 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 41: Enabling Remote Management From Wan

    Enable. Click Submit, and then reset the device with a flash burn for your settings to take effect. Enable the data-router firewall on the WAN (see Step 3 in the CLI-based configuration above). Version 6.8 Mediant 500L MSBR...

  • Page 42: Remote Telnet-Based Management

    Mediant 500L MSBR Remote Telnet-based Management This procedure describes how to enable remote Telnet-based management from the WAN.  To enable remote Telnet management from WAN:  CLI: Access the System configuration mode: # configure system Type the following command: <config-system># cli-terminal...

  • Page 43: Management Tools

    Part II Management Tools...

  • Page 45: Introduction

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

  • Page 47: Web-Based Management

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

  • Page 48: Accessing The Web Interface

    Mediant 500L MSBR 8.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 47). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 49: Areas Of The Gui

    ''Navigation Tree'' on page 50. Work pane, displaying the configuration page of the selected menu in the Navigation tree. This is where configuration is done. For more information, see ''Working with Configuration Pages'' on page 53. Version 6.8 Mediant 500L MSBR...

  • Page 50: Toolbar Description

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

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

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

  • Page 52: Showing / Hiding The Navigation Pane

    Mediant 500L MSBR  To display all menus and submenus, select the Advanced option. Figure 8-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 8.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 53: Working With Configuration

     Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. Version 6.8 Mediant 500L MSBR...
  • Page 54 Mediant 500L MSBR 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 8-6: Toggling between Basic and Advanced View Notes: •...

  • Page 55: Modifying And Saving Parameters

    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 figure below: Figure 8-9: Value Reverts to Previous Valid Value Version 6.8 Mediant 500L MSBR...

  • Page 56: Working With Tables

    Mediant 500L MSBR 8.1.6.4 Working with Tables Many of the Web configuration pages provide tables for configuring various functionalities of the device. The figure below and subsequent table describe the areas of a typical configuration table: Figure 8-10: Displayed Details Pane...

  • Page 57: Searching For Configuration Parameters

    • Link (in green) to the Web page on which the parameter appears • Brief description of the parameter • Menu navigation path to the Web page on which the parameter appears Version 6.8 Mediant 500L MSBR...
  • Page 58 Mediant 500L MSBR In the searched list, click the required parameter (green link) to open the page on which the parameter appears; the relevant page opens in the Work pane and the searched parameter is highlighted in the page for easy identification, as shown in the...

  • Page 59: Creating A Login Welcome Message

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

  • Page 60: Getting Help

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

  • Page 61: Viewing The Home Page

    "LOCKED": device is locked (i.e. no new calls are accepted) • "UNLOCKED": device is not locked • "SHUTTING DOWN": device is currently shutting down To perform these operations, see ''Basic Maintenance'' on page 603. The table below describes the areas of the Home page. Version 6.8 Mediant 500L MSBR...
  • Page 62 Mediant 500L MSBR Table 8-7: Home Page Description Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green = No alarms  Red = Critical alarm  Orange = Major alarm ...

  • Page 63: Assigning A Port Name

    Open the Home page. Click the required port icon; a shortcut menu appears: From the shortcut menu, choose Update Port Info; a text box appears: Type a brief description for the port, and then click Apply Port Info. Version 6.8 Mediant 500L MSBR...

  • Page 64: Configuring Web User Accounts

    Mediant 500L MSBR 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 65: 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 6.8 Mediant 500L MSBR...
  • Page 66 Mediant 500L MSBR  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 67: 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 8-18: Web Users Table Page Version 6.8 Mediant 500L MSBR...
  • Page 68 Mediant 500L MSBR Click Add; the following dialog box is displayed: Figure 8-19: Web Users Table - Add Record Dialog Box Configure a Web user according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
  • Page 69 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 Security Settings'' on page 71). Version 6.8 Mediant 500L MSBR...
  • Page 70 Mediant 500L MSBR Parameter Description Web: Block Duration Defines the duration (in seconds) for which the user is blocked when CLI: block-duration the user exceeds a user-defined number of failed login attempts. This is configured by the 'Deny Access On Fail Count' parameter (see ''Configuring Web Security Settings'' on page 71).

  • Page 71: Displaying Login Information Upon Login

    Management > Web Security Settings). Set the 'Secured Web Connection (HTTPS)' parameter to HTTPS Only. Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 606. Version 6.8 Mediant 500L MSBR...

  • Page 72: Limiting Oamp Access To A Specific Wan Interface

    Mediant 500L MSBR Limiting OAMP Access to a Specific WAN Interface You can limit the access of OAMP applications (such as HTTP, HTTPS, Telnet, and SSH) to a specific WAN interface. This OAMP-interface binding can then be associated with a Virtual Routing and Forwarding (VRF).

  • Page 73: 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 74 Mediant 500L MSBR To add an authorized IP address, in the 'Add an authorized IP address' field, enter the required IP address, and then click Add New Entry; the IP address you entered is added as a new entry to the Web & Telnet Access List table.

  • Page 75: Cli-Based Management

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

  • Page 76: Using Cli Shortcuts

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

  • Page 77: Common Cli Commands

    GigabitEthernet interface configuration while in the virtual-LAN interface command set: (config)# interface vlan 1 (conf-if-VLAN 1)# do show interfaces GigabitEthernet 0/0 Undoes an issued command or disables a feature. Enter no before the command: # no debug log Version 6.8 Mediant 500L MSBR...

  • Page 78: Configuring Tables In Cli

    Mediant 500L MSBR Command Description activate Activates a command. When you enter a configuration command in the CLI, the command is not applied until you enter the activate and exit commands. Note: Offline configuration changes require a reset of the device. A reset can be performed at the end of the configuration changes.
  • Page 79 The following command is run for this example: (config-voip)# sip-definition account 1 insert Note: This behavior when inserting table rows is applicable only to tables that do not have "child" tables (sub-tables). Version 6.8 Mediant 500L MSBR...

  • Page 80: Understanding Cli Error Messages

    Mediant 500L MSBR 9.1.5 Understanding CLI Error Messages The CLI provides feedback on commands by displaying informative messages:  Failure reason of a run command. The failure message is identical to the notification failure message sent by Syslog. For example, an invalid Syslog server IP address is displayed in the CLI as follows: (logging)# syslog-ip 1111.1.1.1...

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

    Figure 9-2: Selecting Public RSA Key in PuTTY Open the Telnet/SSH Settings page (Configuration tab > System menu > Management > Telnet/SSH Settings), and then do the following: Set the 'Enable SSH Server' parameter to Enable. Version 6.8 Mediant 500L MSBR...
  • Page 82 Mediant 500L MSBR Paste the public key that you copied in Step 1.d into the 'Admin Key' field, as shown below: Figure 9-3: SSH Settings - Pasting Public RSA Key in 'Admin Key' Field For additional security, you can set the 'Require Public Key' to Enable. This ensures that SSH access is only possible by using the RSA key and not by using user name and password.

  • Page 83: Establishing A Cli Session

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

  • Page 84: Viewing Current Cli Sessions

    Mediant 500L MSBR Viewing Current CLI Sessions You can view users that are currently logged in to the device's CLI. This applies to users logged in to the CLI through RS-232 (console), Telnet, or SSH. For each logged-in user, the following is displayed: the type of interface (console, Telnet, or SSH), user's username, remote IP address from where the user logged in, and the duration (days and time) of the session.

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

    When this mode is configured, each time you change the height of the terminal window using your mouse (i.e., dragging one of the window's borders or corners), the number of displayed output command lines is changed accordingly. Version 6.8 Mediant 500L MSBR...

  • Page 87: Configuring Tacacs+ For Cli Login

    To configure the IP address of the TACACS+ server (up to two servers can be configured): (config-data)# tacacs-server host <IP address>  To configure the TCP port number for the TACACS+ service: (config-data)# tacacs-server port <port> Version 6.8 Mediant 500L MSBR...
  • Page 88 Mediant 500L MSBR  To configure the shared secret between the TACACS+ server and the device: (config-data)# tacacs-server key <password>  To configure how much time to wait for a TACACS+ response before failing the authentication: (config-data)# tacacs-server timeout <in seconds>...
  • Page 89 User's Manual 9. CLI-Based Management This page is intentionally left blank. Version 6.8 Mediant 500L MSBR...

  • Page 91: 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 92 Mediant 500L MSBR  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String). Figure 10-1: SNMP Community String Page Configure SNMP community strings according to the table below.

  • Page 93: Configuring Snmp Trap Destinations

    Management > SNMP > SNMP Trap Destinations). Figure 10-2: SNMP Trap Destinations Page Configure the SNMP trap manager parameters according to the table below. Select the check box corresponding to the SNMP Manager that you wish to enable. Click Submit. Version 6.8 Mediant 500L MSBR...

  • Page 94: Configuring Snmp Trusted Managers

    Mediant 500L MSBR Note: Only row entries whose corresponding check boxes are selected are applied when clicking Submit; otherwise, settings revert to their defaults. Table 10-2: SNMP Trap Destinations Parameters Description Parameter Description Web: SNMP Manager Enables the SNMP Manager to receive traps and checks...
  • Page 95 Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address. Define an IP address in dotted-decimal notation. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500L MSBR...

  • Page 96: Configuring Snmp V3 Users

    Mediant 500L MSBR 10.4 Configuring SNMP V3 Users The SNMP v3 Users table lets you configure up to 10 SNMP v3 users for authentication and privacy. The following procedure describes how to configure SNMP v3 users in the Web interface.
  • Page 97 Group The group with which the SNMP v3 user is associated. CLI: group  [0] Read-Only (default) [SNMPUsers_Group]  [1] Read-Write  [2] Trap Note: All groups can be used to send traps. Version 6.8 Mediant 500L MSBR...
  • Page 98 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 99: Based Management

    (CPE) and the Auto Configuration Servers (ACS). The TR- 069 connection to the ACS can be done on the LAN or WAN interface. The protocol stack looks as follows: Table 11-1: TR-069 Protocol Stack CPE/ACS Management Application RPC Methods SOAP HTTP SSL/TLS TCP/IP Version 6.8 Mediant 500L MSBR...
  • Page 100 Mediant 500L MSBR Communication is typically established by the CPE; hence, messages from CPE to ACS are typically carried in HTTP requests, and messages from ACS to CPE in HTTP responses. Figure 11-1: TR-069 Session Example Communication between ACS and CPE is defined via Remote Procedure Call (RPC) methods.
  • Page 101 ♦ Firmware Upgrade Image (File Type = 1) - cmp file. ♦ Vendor Configuration File (File Type = 3) - output of show running- config CLI command, which includes Data and Voice configuration. Version 6.8 Mediant 500L MSBR...
  • Page 102 Mediant 500L MSBR The CPE responds to the Download method, indicating successful or unsuccessful completion via one of the following: ♦ A DownloadResponse with the Status argument set to zero (indicating success), or a fault response to the Download request (indicating failure).
  • Page 103 Inform: A CPE must call this method to initiate a transaction sequence whenever a connection to an ACS is established. • TransferComplete: Informs the ACS of the completion (either successful or unsuccessful) of a file transfer initiated by an earlier Download or Upload method call. Version 6.8 Mediant 500L MSBR...

  • Page 104: 104

    FXS interfaces (lines) only. TR-104 defines a "data model" template for TR-069 enabled devices. The "data model" that is applicable to the AudioCodes device is defined in the DSL Forum TR-104 – "DSLHome™ Provisioning Parameters for VoIP CPE"...

  • Page 105: Configuring Tr-069

    InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.Line.{i}.Callin gFeatures: Configures voice parameters per FXS line such as caller ID. ♦ InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.Line.{i}.SIP: Configures username/password per FXS line. AudioCodes maps this object to the corresponding entry in the Authentication table • InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP: Configures SIP parameters specific to the UA such as Proxy server.
  • Page 106 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 107: 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 6.8 Mediant 500L MSBR...
  • Page 108 Mediant 500L MSBR  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 109: General Ini File Formatting Rules

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

  • Page 110: Configuring An Ini File

    Mediant 500L MSBR 12.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 111: Secured Encoded Ini File

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

  • Page 112: Configuring Password Display In Ini File

    Mediant 500L MSBR 12.5 Configuring Password Display in ini File Passwords can be displayed in the ini file in one of the following formats, configured by the INIPasswordsDisplayType ini file parameter:  Obscured: The password characters are concealed and displayed as encoded. The password is displayed using the syntax, $1$<obscured password>, for example,...

  • Page 113: Ini Viewer And Editor Utility

    12.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 114 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 115: General System Settings

    Part III General System Settings...

  • Page 117: Configuring Ssl/Tls Certificates

    Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 500L MSBR...
  • Page 118 Mediant 500L MSBR When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows:  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for...
  • Page 119  [5] 5 = TLS 1.2 and TLS 1.0 only.  [6] 6 = TLS 1.2 and TLS 1.1 only  [7] 7 = TLS 1.2, TLS 1.1 and TLS 1.0 only (excludes SSL 3.0). Version 6.8 Mediant 500L MSBR...
  • Page 120 Mediant 500L MSBR Parameter Description Web: Ciphers Server Defines the supported cipher suite for the TLS server (in CLI: ciphers-server OpenSSL cipher list format). [TLSContexts_ServerCipherString] For valid values, refer to URL http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).

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

    Figure 13-2: Certificate Signing Request Group 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). Version 6.8 Mediant 500L MSBR...
  • Page 122 Mediant 500L MSBR 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: -----BEGIN CERTIFICATE----- MIIDkzCCAnugAwIBAgIEAgAAADANBgkqhkiG9w0BAQQFADA/MQswCQYDVQQGEw JGUjETMBEGA1UEChMKQ2VydGlwb3N0ZTEbMBkGA1UEAxMSQ2VydGlwb3N0ZSBT ZXJ2ZXVyMB4XDTk4MDYyNDA4MDAwMFoXDTE4MDYyNDA4MDAwMFowPzELMAkGA1 UEBhMCRlIxEzARBgNVBAoTCkNlcnRpcG9zdGUxGzAZBgNVBAMTEkNlcnRpcG9z dGUgU2VydmV1cjCCASEwDQYJKoZIhvcNAQEBBQADggEOADCCAQkCggEAPqd4Mz iR4spWldGRx8bQrhZkonWnNm`+Yhb7+4Q67ecf1janH7GcN/SXsfx7jJpreWUL f7v7Cvpr4R7qIJcmdHIntmf7JPM5n6cDBv17uSW63er7NkVnMFHwK1QaGFLMyb FkzaeGrvFm4k3lRefiXDmuOe+FhJgHYezYHf44LvPRPwhSrzi9+Aq3o8pWDguJ uZDIUP1F1jMa+LPwvREXfFcUW+w== -----END CERTIFICATE----- Scroll down to the Upload certificates files from your computer group, click the Browse button corresponding to the 'Send Device Certificate...' field, navigate to the...

  • Page 123: 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 6.8 Mediant 500L MSBR...

  • Page 124: Generating Private Keys For Tls Contexts

    Mediant 500L MSBR 13.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 125: Creating Self-Signed Certificates For Tls Contexts

    Figure 13-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 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 13.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 127: Configuring Mutual Tls Authentication

    Certificates and Certificate Chain into Trusted Certificate Store'' on page 126). • Make sure that the TLS certificate is signed by a CA that the SIP client trusts so that the client can authenticate the device. Version 6.8 Mediant 500L MSBR...

  • Page 128: Tls For Remote Device Management

    Mediant 500L MSBR 13.7.2 TLS for Remote Device Management By default, servers using TLS provide one-way authentication. The client is certain that the identity of the server is authentic. When an organizational PKI is used, two-way authentication may be desired - both client and server should be authenticated using X.509 certificates.

  • Page 129: Configuring Tls Server Certificate Expiry Check

    In the 'TLS Expiry Check Period' field, enter the periodical interval (in days) for checking the TLS server certificate expiry date. By default, the device checks the certificate every 7 days. Click the Submit TLS Expiry Settings button. Version 6.8 Mediant 500L MSBR...
  • Page 130 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 131: Date And Time

    Saving Time (DST), see 'Configuring Daylight Saving Time' on page 133. You can also configure the device to authenticate and validate the NTP messages received from the NTP server. Authentication is done using an authentication key with the MD5 Version 6.8 Mediant 500L MSBR...
  • Page 132 Mediant 500L MSBR cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication. The following procedure describes how to configure SNTP. For detailed descriptions of the configuration parameters, see NTP and Daylight Saving Time Parameters on page 802.

  • Page 133: Configuring Daylight Saving Time

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

  • Page 135: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 137: Network

    Figure 15-1: Ethernet Device Table - Add Record Configure an Ethernet Device according to the parameters described in the table below. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500L MSBR...

  • Page 138: Configuring Ip Network Interfaces

    Mediant 500L MSBR Table 15-1: Ethernet Device Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [DeviceTable_Index] Note: Each table row must be configured with a unique index. VLAN ID Defines a VLAN ID.
  • Page 139 The following procedure describes how to configure the IP network interfaces in the Web interface. You can also configure IP network interfaces using the table ini file parameter, InterfaceTable or CLI command, configure voip/interface network-if. Version 6.8 Mediant 500L MSBR...
  • Page 140 Mediant 500L MSBR  To configure IP network interfaces: Open the Interface Table page (Configuration tab > VoIP menu > Network > IP Interfaces Table). Click Add; a dialog box appears. Configure the IP network interface according to the parameters described in the table below.
  • Page 141 (Optional) Defines the primary DNS server's IP address (in dotted- CLI: primary-dns decimal notation), which is used for translating domain names into IP [InterfaceTable_PrimaryDNS addresses for the interface. ServerIPAddress] By default, no IP address is defined. Version 6.8 Mediant 500L MSBR...
  • Page 142 Mediant 500L MSBR Parameter Description Web/EMS: Secondary DNS (Optional) Defines the secondary DNS server's IP address (in CLI: secondary-dns dotted-decimal notation), which is used for translating domain names [InterfaceTable_SecondaryD into IP addresses for the interface. NSServerIPAddress] By default, no IP address is defined.

  • Page 143: Assigning Ntp Services To Application Types

    Syslog server and falls back to a "safe mode", using a single interface without VLANs. Ensure that you view the Syslog messages that the device sends in system startup to see if any errors occurred. Version 6.8 Mediant 500L MSBR...

  • Page 144: Networking Configuration Examples

    Mediant 500L MSBR 15.2.3 Networking Configuration Examples This section provides configuration examples of networking interfaces. 15.2.3.1 One VoIP Interface for All Applications This example describes the configuration of a single VoIP interface for all applications: Interface table: Configured with a single interface for OAMP, Media and Control:...

  • Page 145: Voip Interfaces For Combined Application Types

    For packets sent with DiffServ value of 40, set VLAN priority to 6 ♦ For packets sent with DiffServ value of 26, set VLAN priority to 4 ♦ For packets sent with DiffServ value of 10, set VLAN priority to 2 • Layer-3 QoS values are assigned: Version 6.8 Mediant 500L MSBR...

  • Page 146: Voip Interfaces With Multiple Default Gateways

    Mediant 500L MSBR ♦ For Media Service class, the default DiffServ value is set to 46 ♦ For Control Service class, the default DiffServ value is set to 40 ♦ For Gold Service class, the default DiffServ value is set to 26 ♦...

  • Page 147: Configuring Static Ip Routes

    Configure a static route according to the parameters described in the table below. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Note: You can delete only static routing rules that are inactive. Version 6.8 Mediant 500L MSBR...
  • Page 148 Mediant 500L MSBR Table 15-11: Static Route Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [StaticRouteTable_Index] The valid value is 0 to 29. Note: Each table row must be configured with a unique index.

  • Page 149: Configuration Example Of Static Ip Routes

    The static route's Gateway address in the Static Route table is in the same subnet as the IP address of the IP network interface in the Interface table. Figure 15-4: Example of using a Static Route Version 6.8 Mediant 500L MSBR...

  • Page 150: Troubleshooting The Routing Table

    Mediant 500L MSBR 15.3.2 Troubleshooting the Routing Table When adding a new static route to the Static Route table, the added rule passes a validation test. If errors are found, the static route is rejected and not added to the table.
  • Page 151 Configure a DiffServ-to-VLAN priority mapping (Layer-2 QoS) according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 15-13: DiffServ Table Parameter Descriptions Parameter Description Version 6.8 Mediant 500L MSBR...

  • Page 152: Dns

    Mediant 500L MSBR Parameter Description Index Defines an index number for the new table record. Note: Each table row must be configured with a unique index. Differentiated Services Defines a DiffServ value. CLI: diff-serv The valid value is 0 to 63.

  • Page 153: Configuring The Internal Dns Table

    The IP address can be [Dns2Ip_FirstIpAddress] configured as an IPv4 and/or IPv6 address. Web: Second IP Address Defines the second IP address (in dotted-decimal format notation) CLI: second-ip-address to which the host name is translated. [Dns2Ip_SecondIpAddress] Version 6.8 Mediant 500L MSBR...

  • Page 154: Configuring The Internal Srv Table

    Mediant 500L MSBR Parameter Description Web: Third IP Address Defines the third IP address (in dotted-decimal format notation) to CLI: third-ip-address which the host name is translated. [Dns2Ip_ThirdIpAddress] Web: Fourth IP Address Defines the fourth IP address (in dotted-decimal format notation) to CLI: fourth-ip-address which the host name is translated.
  • Page 155 Defines the priority of the target host. A lower value means that it is CLI: priority-1|2|3 more preferred. [Srv2Ip_Priority1/2/3] Web: Weight (1-3) Defines a relative weight for records with the same priority. CLI: weight-1|2|3 [Srv2Ip_Weight1/2/3] Version 6.8 Mediant 500L MSBR...
  • Page 156 Mediant 500L MSBR Parameter Description Web: Port (1-3) Defines the TCP or UDP port on which the service is to be found. CLI: port-1|2|3 [Srv2Ip_Port1/2/3] User's Manual Document #: LTRT-10466...

  • Page 157: 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 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 15-9: Device behind NAT and NAT Issues 15.6.1.1 Configuring a Static NAT IP Address for All Interfaces You can configure a global (public) IP address of the router to enable static NAT between the device and the Internet for all network interfaces.

  • Page 159: Configuring Nat Translation Per Ip Interface

    Click Submit, and then save ("burn") your settings to flash memory. Table 15-16: NAT Translation Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. CLI: index Note: Each table row must be configured with a [NATTranslation_Index] unique index. Version 6.8 Mediant 500L MSBR...

  • Page 160: Remote Ua Behind Nat

    Mediant 500L MSBR Parameter Description Source Interface Name Defines the name of the IP interface, as configured in CLI: SourceIPInterfaceName the Interface table. [NATTranslation_SourceIPInterfaceName] Target IP Address Defines the global IP address. This address is set in CLI: TargetIPAddress the SIP Via and Contact headers as well as in the o= [NATTranslation_TargetIPAddress] and c= SDP fields.

  • Page 161: Media (Rtp/Rtcp/T.38)

    (not the UA) sends the first packet, it sends it to the address obtained from the SIP message and only after the device receives the first packet from the UA, does it determine whether the UA is behind NAT. Version 6.8 Mediant 500L MSBR...
  • Page 162 Mediant 500L MSBR  NAT Is Not Used: (Default) NAT feature is disabled. The device considers the UA as not located behind NAT and always sends the media packets to the UA using the IP address:port obtained from the first received SIP message.

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

    15.7 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).

  • Page 164: Multiple Routers Support

    Mediant 500L MSBR If you have set the InboundMediaLatchMode parameter to 1 or 2, scroll down to the Robust Settings group and do the following: • Define the minimum number of continuous media (RTP, RTCP, SRTP, and SRTCP) packets that need to be received by the channel before it can latch onto this new incoming stream: ♦...

  • Page 165: Security

    Action Upon Match: Block The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList or the CLI command, configure voip/access-list. Version 6.8 Mediant 500L MSBR...
  • Page 166 Mediant 500L MSBR  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security > Firewall Settings). Click Add; the following dialog box appears: Figure 16-1: Firewall Settings Page - Add Record Configure a Firewall rule according to the parameters described in the table below.
  • Page 167 This is applicable if you enabled the 'Use Specific [AccessList_Interface_x] Interface' field. The list displays interface names as defined in the Interface table in ''Configuring IP Network Interfaces'' on page 138. Packet Size Defines the maximum allowed packet size. CLI: packet-size Version 6.8 Mediant 500L MSBR...
  • Page 168 Mediant 500L MSBR Parameter Description [AccessList_Packet_Size] The valid range is 0 to 65535. Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment. Byte Rate Defines the expected traffic rate (bytes per second), i.e., the CLI: byte-rate allowed bandwidth for the specified protocol.

  • Page 169: Configuring General Security Settings

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

  • Page 170: Intrusion Detection System

    Mediant 500L MSBR 16.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 171: Enabling Ids

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

  • Page 175: Assigning Ids Policies

    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., !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Version 6.8 Mediant 500L MSBR...

  • Page 176: Viewing Ids Alarms

    Mediant 500L MSBR Parameter Description Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This CLI: proxy-set indicates the Proxy Sets from where the attacks are coming from. The [IDSMatch_ProxySet] following syntax is supported: ...
  • Page 177 The table below lists the Syslog text messages per malicious event: Table 16-6: Types of Malicious Events and Syslog Text String Type Description Syslog String Connection TLS authentication failure abuse-tls-auth-fail Abuse   Message exceeds a user-defined maximum malformed-invalid- Malformed Version 6.8 Mediant 500L MSBR...
  • Page 178 Mediant 500L MSBR Type Description Syslog String Messages message length (50K) msg-len   Any SIP parser error malformed-parse-error   Message policy match malformed-message- policy  Basic headers not present  malformed-miss-  Content length header not present (for TCP) header ...

  • Page 179: Media

    When silence is detected, it stops sending packets in the channel. The following procedure describes how to enable silence suppression using the Web interface. Version 6.8 Mediant 500L MSBR...

  • Page 180: Configuring Echo Cancellation

    Mediant 500L MSBR  To enable silence suppression using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 17-2: Enabling Silence Suppression in Voice Settings Page Set the 'Silence Suppression' (EnableSilenceCompression) field to Enable.

  • Page 181: Fax And Modem Capabilities

    VBD (or T.38) is automatically performed and no additional SIP signaling is required. If negotiation fails (i.e., no match is achieved for any of the transport capabilities), fallback to existing logic occurs (according to the parameter IsFaxUsed). Version 6.8 Mediant 500L MSBR...

  • Page 182: Fax/Modem Transport Modes

    Mediant 500L MSBR 17.2.2 Fax/Modem Transport Modes The device supports the following transport modes for fax per modem type (V.22/V.23/Bell/V.32/V.34):  T.38 fax relay (see ''T.38 Fax Relay Mode'' on page 182)  G.711 Transport: switching to G.711 when fax/modem is detected (see ''G.711 Fax / Modem Transport Mode'' on page 184) ...
  • Page 183 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 Version 6.8...

  • Page 184: Fax / Modem Transport Mode

    0-15  AudioCodes Call Party with non-AudioCodes Party: The device uses the standard T.38-over-RTP method, which encapsulates the T.38 payload only, without its headers (i.e., includes only fax data) in the sent RTP packet (RFC 4612). The T.38-over-RTP method also depends on call initiator: ...

  • Page 185: Fax Fallback

    'Fax/Modem Bypass Coder Type' parameter (FaxModemBypassCoderType). The channel is also automatically reconfigured with the following fax / modem adaptations:  Disables silence suppression  Enables echo cancellation for fax  Disables echo cancellation for modem  Performs certain jitter buffering optimizations Version 6.8 Mediant 500L MSBR...
  • Page 186 Tip: When the remote (non-AudioCodes) gateway uses the G.711 coder for voice and doesn’t change the coder payload type for fax or modem transmission, it is recommended to use the Bypass mode with the following configuration: •...

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

    Mediant 500L MSBR In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Events Only (FaxTransportMode = Set the 'V.21 Modem Transport Type' parameter to Events Only (V21ModemTransportType = 3). Set the 'V.22 Modem Transport Type' parameter to Events Only (V22ModemTransportType = 3).

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

    Use Fax-over-T.38 fallback to T.30, using up to 14,400 bps ('SIP T.38 Version' is set to Version 0). Note: The CNG detector is disabled in all the subsequent examples. To disable the CNG detector, set the 'CNG Detector Mode' parameter (CNGDetectorMode) to Disable. Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 17.2.3.1 Bypass Mechanism for V.34 Fax Transmission In this proprietary scenario, the device uses bypass (or NSE) mode to transmit V.34 faxes, enabling the full utilization of its speed.  To use bypass mode for T.30 and V.34 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Bypass (FaxTransportMode = 2).

  • Page 191: Fax Relay For Sg3 Fax Machines

    For example, the device sends or receives the following INVITE message, negotiating both audio and image media: INVITE sip:2001@10.8.211.250;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.6.55;branch=z9hG4bKac1938966220 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> Version 6.8 Mediant 500L MSBR...

  • Page 192: Modem Relay

    Mediant 500L MSBR 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 s=Phone-Call c=IN IP4 10.8.6.55 t=0 0 m=audio 6010 RTP/AVP 18 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no...

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

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

  • Page 194: Fax Transmission Behind Nat

    Mediant 500L MSBR of call capabilities is exchanged in the outgoing SDP. These capabilities include whether VBD is supported and associated RTP payload types ('gpmd' SDP attribute), supported codecs, and packetization periods for all codec payload types ('ptime' SDP attribute). After this initial negotiation, no Re-INVITE messages are necessary as both endpoints are synchronized in terms of the other side's capabilities.

  • Page 195: Configuring Rtp/Rtcp Settings

    BFI packets simultaneously, so that the Jitter Buffer returns to its normal condition. The following procedure describes how to configure the jitter buffer using the Web interface. Version 6.8 Mediant 500L MSBR...

  • Page 196: Comfort Noise Generation

    Mediant 500L MSBR  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' group, as shown below:...

  • Page 197: Dual-Tone Multi-Frequency Signaling

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

  • Page 198: Configuring Rfc 2833 Payload

    Mediant 500L MSBR Set the '1st Tx DTMF Option' parameter to INFO (Cisco) (TxDTMFOption = 3). Note: In this mode, DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF).

  • Page 199: Configuring Rtp Base Udp Port

    UDP port configured for a SIP Interface (see Configuring SIP Interfaces on page 283). For example, if your highest configured UDP port for a SIP Interface is 6060, you must configure the BaseUDPPort parameter to any value greater than 6060. Version 6.8 Mediant 500L MSBR...

  • Page 200: Configuring Ip Media Settings

    Mediant 500L MSBR 17.4 Configuring IP Media Settings This section describes the configuration of various IP media features. 17.4.1 Automatic Gain Control (AGC) Automatic Gain Control (AGC) adjusts the energy of the output signal to a required level (volume). This feature compensates for near-far gain differences. AGC estimates the energy of the incoming signal from the IP or Tel, determined by the 'AGC Redirection' parameter, calculates the essential gain, and then performs amplification.

  • Page 201: Configuring Various Codec Attributes

    General Media Settings). Figure 17-7: Codec Settings in General Media Settings Page Configure the parameters as required, and then click click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 606. Version 6.8 Mediant 500L MSBR...

  • Page 202: Configuring Analog Settings

    Mediant 500L MSBR 17.6 Configuring Analog Settings The Analog Settings page allows you to configure various analog parameters. For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 779. This page also selects the type (USA or Europe) of FXS and/or FXO coefficient information.
  • Page 203 Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 606. Version 6.8 Mediant 500L MSBR...
  • Page 204 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 205: Services

    IP Address Lease Time Option 1 Subnet Mask Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Version 6.8 Mediant 500L MSBR...
  • Page 206 Mediant 500L MSBR DHCP Option Code DHCP Option Name Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
  • Page 207 Defines the IP address (IPv4) of the secondary NTP server CLI: ntp-server-2 that the DHCP server assigns to the DHCP client. The value [DhcpServer_NTPServer2] is sent in DHCP Option 42 (Network Time Protocol Server). The default value is 0.0.0.0. Version 6.8 Mediant 500L MSBR...
  • Page 208 Mediant 500L MSBR Parameter Description Web: Time Offset Defines the Greenwich Mean Time (GMT) offset (in seconds) CLI: time-offset that the DHCP server assigns to the DHCP client. The value [DhcpServer_TimeOffset] is sent in DHCP Option 2 (Time Offset). The valid range is -43200 to 43200. The default is 0.

  • Page 209: Configuring The Vendor Class Identifier

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

  • Page 210: Configuring Additional Dhcp Options

    Mediant 500L MSBR 18.1.3 Configuring Additional DHCP Options The DHCP Option table lets you configure up to 10 additional DHCP Options that the DHCP server can use to service the DHCP client. These DHCP Options are included in the DHCPOffer response sent by the DHCP server.

  • Page 211: Configuring Static Ip Addresses For Dhcp Clients

    Static IP Table link located at the bottom of the page; the DHCP Static IP Table page opens. Click Add; the following dialog box appears: Configure a static IP address for a specific DHCP client according to the parameters described in the table below. Click Submit. Version 6.8 Mediant 500L MSBR...

  • Page 212: Viewing And Deleting Dhcp Clients

    Mediant 500L MSBR Table 18-5: DHCP Static IP Table Parameter Descriptions Parameter Description Web: Index Defines an index number for the new table record. CLI: dhcp static-ip <index> Note: Each table row must be configured with a unique index. [DhcpStaticIP_Index]...
  • Page 213 Select the table row index of the DHCP client that you want to delete. Click the Action button, and then from the drop-down menu, choose Delete; a confirmation message appears. Click OK to confirm deletion. Version 6.8 Mediant 500L MSBR...

  • Page 214: Sip-Based Media Recording

    • For the maximum number of concurrent sessions that the device can record, contact your AudioCodes sales representative. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons.
  • Page 215 Below is an example of an INVITE sent by the device to an SRS: INVITE sip:VSRP@1.9.64.253 SIP/2.0 Via: SIP/2.0/UDP 192.168.241.44:5060;branch=z9hG4bKac505782914 Max-Forwards: 10 From: <sip:192.168.241.44>;tag=1c505764207 To: <sip:VSRP@1.9.64.253> Call-ID: 505763097241201011157@192.168.241.44 CSeq: 1 INVITE Contact: <sip:192.168.241.44:5060>;src Supported: replaces,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Require: siprec User-Agent: Mediant /v.6.80A.227.005 Content-Type: multipart/mixed;boundary=boundary_ac1fffff85b Version 6.8 Mediant 500L MSBR...
  • Page 216 Mediant 500L MSBR Content-Length: 1832 --boundary_ac1fffff85b Content-Type: application/sdp o=AudiocodesGW 921244928 921244893 IN IP4 10.33.8.70 s=SBC-Call c=IN IP4 10.33.8.70 t=0 0 m=audio 6020 RTP/AVP 8 96 c=IN IP4 10.33.8.70 a=ptime:20 a=sendonly a=label:1 a=rtpmap:8 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...

  • Page 217: Enabling Sip-Based Media Recording

    IP Group 1 to IP Group 2 that have the destination number prefix "1800". The device records the calls from the leg interfacing with IP Group 2, sending the recorded media to IP Group 3 (i.e., the SRS). Version 6.8 Mediant 500L MSBR...
  • Page 218 Mediant 500L MSBR Configure a SIP recording route according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 18-6: SIP Recording Routing Parameter Descriptions Parameter Description Index Defines an index number for the new table record.

  • Page 219: Configuring Sip User Part For Srs

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

  • Page 221: Radius Authentication

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

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

    RADIUS servers, see ''Configuring Web User Accounts'' on page 64. # 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 223: Configuring Radius Authentication

    IP address. In the 'RADIUS Authentication Server Port' field, enter the RADIUS server’s port number. In the 'RADIUS Shared Secret' field, enter the shared secret used to authenticate the device to the RADIUS server. Version 6.8 Mediant 500L MSBR...

  • Page 224: Securing Radius Communication

    Mediant 500L MSBR In the 'RADIUS VSA Vendor ID' field, enter the same vendor ID number as set on the RADIUS server. When implementing Web user access levels, do one of the following: • If the RADIUS server response includes the access level attribute: In the 'RADIUS VSA Access Level Attribute' field, enter the code that indicates the access level attribute in the VSA section of the received RADIUS packet.

  • Page 225: Authenticating Radius In The Url

    However, authentication with the RADIUS server can also be done immediately after the user enters the URL, if the URL also contains the login credentials, example: http://10.4.4.112/Forms/RadiusAuthentication?WSBackUserName=John&WSBackPasswor d=1234 Note: This feature allows up to five simultaneous users only. Version 6.8 Mediant 500L MSBR...

  • Page 226: Ldap-Based Management And Sip Services

    Mediant 500L MSBR 18.4 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 227: Enabling The Ldap Service

    Figure 18-5: Enabling LDAP on the LDAP Settings Page Under LDAP Settings, from the 'LDAP Service' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 18.4.2 Enabling LDAP-based Web/CLI User Login Authentication and Authorization 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).
  • Page 229 Defines the LDAP server's bind Distinguished Name (DN) or CLI: bind-dn username. [LdapConfiguration_LdapCo  LDAP-based SIP queries: The DN is used as the username nfBindDn] during connection and binding to the LDAP server. The DN is Version 6.8 Mediant 500L MSBR...
  • Page 230 Mediant 500L MSBR Parameter Description used to uniquely name an AD object. Below are example parameter settings:  cn=administrator,cn=Users,dc=domain,dc=com  administrator@domain.com  domain\administrator  LDAP-based user login authentication: This parameter represents the login username entered by the user during a login attempt.

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

    Defines an index number for the new table record. CLI: set internal-index Note: Each table row must be configured with a unique [LdapServersSearchDNs_Index] index. Base Path Defines the full path (DN) to the objects in the AD where CLI: set base-path Version 6.8 Mediant 500L MSBR...

  • Page 232: Configuring The Ldap Search Filter Attribute

    Mediant 500L MSBR Parameter Description [LdapServersSearchDNs_Base_Path] the query is done. The valid value is a string of up to 256 characters. For example: OU=NY,DC=OCSR2,DC=local. In this example, the DN path is defined by the LDAP names, OU (organizational unit) and DC (domain component).

  • Page 233: Configuring Access Level Per Management Groups Attributes

    The device searches this LDAP response for the group names that you configured in the Management LDAP Groups table in order to determine the user's access level. If the device finds a group name, the user is assigned the corresponding access level and login Version 6.8 Mediant 500L MSBR...
  • Page 234 Mediant 500L MSBR is permitted; otherwise, login is denied. Once the LDAP response has been received (success or failure), the LDAP session terminates. The following procedure describes how to configure an access level per management groups in the Web interface. You can also configure this using the table ini file parameter, MgmntLDAPGroups or CLI command, configure voip >...

  • Page 235: Configuring Ldap Search Methods

    The advantage of enabling this feature includes the following:  Improves routing decision performance by using local cache for subsequent LDAP queries  Reduces number of queries performed on an LDAP server and corresponding bandwidth consumption Version 6.8 Mediant 500L MSBR...
  • Page 236 Mediant 500L MSBR  Provides partial survivability in case of intermittent LDAP server failure (or network isolation) The handling of LDAP queries with the LDAP cache is shown in the flowchart below: Figure 18-12: LDAP Query Process with Local LDAP Cache...

  • Page 237: Configuring Local Database For Management User Authentication

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

  • Page 239: Ldap-Based Login Authentication Example

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

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

    Primary or Secondary key. MSLDAPPrimaryKey Primary Key query search msRTCSIP-PrivateLine= instead of PBX key - can be +3233554480 any AD attribute MSLDAPSecondaryKey Secondary Key query key search if Primary Key fails - can be any attribute Version 6.8 Mediant 500L MSBR...
  • Page 244 Mediant 500L MSBR The process for querying the AD and subsequent routing based on the query results is as follows: If the Primary Key is configured, it uses the defined string as a primary key instead of the one defined in MSLDAPPBXNumAttributeName. It requests the attributes which are described below.
  • Page 245 The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 18-23: LDAP Query Flowchart Note: If you are using the device's local LDAP cache, see ''Configuring the Device's LDAP Cache'' on page for the LDAP query process. Version 6.8 Mediant 500L MSBR...

  • Page 246: Configuring Ad-Based Routing Rules

    Mediant 500L MSBR 18.4.11.2 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 228.
  • Page 247 Rule 5: Sends call to IP address of device (10.33.45.80) if AD query failure (e.g., no response from LDAP server or attribute not found).  Rule 6: Sends query for original destination number of received call to the LDAP server. Version 6.8 Mediant 500L MSBR...

  • Page 248: Querying The Ad For Calling Name

    Mediant 500L MSBR  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. • LDAP query is successful but call fails (due to, for example, busy line) to all the...

  • Page 249: Least Cost Routing

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

  • Page 251: Configuring Lcr

    Cost Groups in the Outbound IP Routing table. The following procedure describes how to enable LCR in the Web interface. You can also do this using the table ini file parameter, RoutingRuleGroups or CLI command, configure voip > services least-cost-routing routing-rule-groups. Version 6.8 Mediant 500L MSBR...
  • Page 252 Mediant 500L MSBR  To enable LCR: Open the Routing Rule Groups Table page (Configuration tab > VoIP menu > Services > Least Cost Routing > Routing Rule Groups Table). Click Add; the following dialog box appears: Figure 18-26: Routing Rule Groups Table - Add Record Enable LCR according to the parameters described in the table below.

  • Page 253: Configuring Cost Groups

    The valid value range is 0-65533. The default is 0. Note: When calculating the cost of a call, if the current time of the call is not within a time band configured for the Cost Group, then this default connection cost is used. Version 6.8 Mediant 500L MSBR...

  • Page 254: Configuring Time Bands For Cost Groups

    Mediant 500L MSBR Parameter Description Default Minute Cost Defines the call charge per minute for a call outside CLI: default-minute-cost the time bands. [CostGroupTable_DefaultMinuteCost] The valid value range is 0-65533. The default is 0. Note: When calculating the cost of a call, if the...

  • Page 255: Assigning Cost Groups To Routing Rules

    To use your configured Cost Groups, you need to assign them to routing rules:  Gateway application: Outbound IP Routing table - see Configuring Outbound IP Routing on page  SBC application: IP-to-IP Routing table - see Configuring SBC IP-to-IP Routing Rules on page Version 6.8 Mediant 500L MSBR...

  • Page 256: Configuring Call Setup Rules

    Mediant 500L MSBR 18.6 Configuring Call Setup Rules The Call Setup Rules table lets you configure up to 40 Call Setup rules. Call Setup rules define various sequences that are run upon the receipt of an incoming call (dialog) at call setup, before the device routes the call to its destination.
  • Page 257 10 Set IDs, where each Set ID can include up to 10 rules. The Set ID is used to assign the Call Setup rules to a routing rule in the routing table. The valid value is 0 to 9. The default is 0. Version 6.8 Mediant 500L MSBR...
  • Page 258 Mediant 500L MSBR Parameter Description Attributes To Query Defines the query string that the device sends to the LDAP CLI: attr-to-query server. [CallSetupRules_AttributesToQuery] The valid value is a string of up to 100 characters. Combined strings and values can be configured like in the Message Manipulations table, using the '+' operator.
  • Page 259 The valid value is a string of up to 300 characters (case- [CallSetupRules_ActionValue] insensitive). Examples:  '+9723976'+ldap.attr.alternateNumber  '9764000'  ldap.attr.displayName  true (if the 'Action Type' is set to Exit)  false (if the 'Action Type' is set to Exit) Version 6.8 Mediant 500L MSBR...

  • Page 260: Call Setup Rule Examples

    Mediant 500L MSBR 18.6.1 Call Setup Rule Examples Below are configuration examples for using Call Setup Rules.  Example 1: This example configures the device to replace (manipulate) the incoming call's source number with a number retrieved from the AD by an LDAP query. The device queries the AD server for the attribute record, "telephoneNumber"...
  • Page 261 Rules Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 3  'Destination IP Group ID': 3 (IP Group for Lync) ♦ Index 2:  'Destination IP Group ID': 4 (IP Group of PBX) Version 6.8 Mediant 500L MSBR...
  • Page 262 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 263: 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 264: 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 265  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 263.
  • Page 266 Mediant 500L MSBR Configure a QoE Profile according to the parameters described in the table below. Click Submit. Table 19-1: Quality of Experience Profile Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [QOEProfile_Index] Profile Name Defines an arbitrary name to easily identify the QoE Profile.
  • Page 267 SEM indicating this owHysteresis] change. Note: If the monitored parameter crosses two thresholds at once (e.g., from Green to Red), the device ignores the hysteresis value and reports the call state change to the SEM. Version 6.8 Mediant 500L MSBR...

  • Page 268: Configuring Bandwidth Profiles

    Mediant 500L MSBR Parameter Description Yellow Red Threshold Defines the parameter threshold values between Yellow (medium CLI: yellow-red-threshold quality) and Red (poor quality) states. [QOEColorRules_YellowRed The valid threshold values are as follows: Threshold]  MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.
  • Page 269 Defines the outgoing audio traffic threshold (in Kbps). CLI: egress-audio-bandwidth [BWProfile_EgressAudioBandwidth] Ingress Audio Bandwidth Defines the incoming audio traffic threshold (in Kbps). CLI: ingress-audio-bandwidth [BWProfile_IngressAudioBandwidth] Egress Video Bandwidth Defines the outgoing video traffic threshold (in Kbps). CLI: egress-video-bandwidth [BWProfile_EgressVideoBandwidth] Version 6.8 Mediant 500L MSBR...
  • Page 270 Mediant 500L MSBR Parameter Description Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). CLI: ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth CLI: total-egress-bandwidth threshold (in Kbps). [BWProfile_TotalEgressBandwidth] Total Ingress Bandwidth Defines the total (video and audio) incoming bandwidth CLI: total-ingress-bandwidth threshold (in Kbps).

  • Page 271: Configuring Media Enhancement Profiles

    Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules or CLI command, configure voip/qoe media-enhancement-rules  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Version 6.8 Mediant 500L MSBR...
  • Page 272 Mediant 500L MSBR Click Add; the following dialog box appears: Figure 19-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below. Click Submit. Table 19-4: Media Enhancement Profile Table Parameter Descriptions...
  • Page 273 Defines an alternative IP Profile ID for the IP Group that CLI: value is associated with this rule, if this rule is applied. This [MediaEnhancementRules_ActionValue] parameter is applicable only if the 'Rule Action' parameter is set to Alternative IP Profile. Version 6.8 Mediant 500L MSBR...
  • Page 274 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 275: Control Network

    The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm or CLI command, configure voip/voip-network realm. Version 6.8 Mediant 500L MSBR...
  • Page 276 Mediant 500L MSBR  To configure a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > VoIP Network > Media Realm Configuration). Click Add; the following dialog box appears: Figure 20-1: Media Realm Page - Add Record Dialog Box Configure the Media Realm according to the parameters described in the table below.
  • Page 277 QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 264. BW Profile Assigns a Bandwidth Profile to the Media Realm. For CLI: bw-profile configuring Bandwidth Profiles, see ''Configuring Bandwidth [CpMediaRealm_BWProfile] Profiles'' on page 268. Version 6.8 Mediant 500L MSBR...

  • Page 278: Configuring Remote Media Subnets

    Mediant 500L MSBR 20.2 Configuring Remote Media Subnets Remote Media Subnets define destination subnets for media (RTP/SRTP) traffic on a specific Media Realm. Each Remote Media Subnet can be assigned different call quality (Quality of Experience Profile) and bandwidth utilization (Bandwidth Profile) profiles. These profiles are configured in ''Configuring Quality of Experience Profiles'' on page ''Configuring Bandwidth Profiles'' on page 268, respectively.
  • Page 279 The default is 0.0.0.0. [RemoteMediaSubnet_DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the CLI: qoe-profile Remote Media Subnet. [RemoteMediaSubnet_QOEProfileName] BW Profile Name Assigns a Bandwidth Profile to the Remote CLI: bw-profile Media Subnet. [RemoteMediaSubnet_BWProfileName] Version 6.8 Mediant 500L MSBR...

  • Page 280: Configuring Srds

    Mediant 500L MSBR 20.3 Configuring SRDs The SRD table lets you configure up to 32 signaling routing domains (SRD). An SRD represents a logical VoIP network. Each logical or physical connection requires an SRD. For example, if the device interfaces with both the LAN and WAN, you would need to configure an SRD for each one.
  • Page 281 WAN and the other on the LAN. The reason for this is that in Media Anchoring, the device does not interfere in the SIP signaling such as manipulation of IP Version 6.8 Mediant 500L MSBR...
  • Page 282 Mediant 500L MSBR Parameter Description addresses, which is necessary for calls between LAN and WAN.  When the global parameter SBCDirectMedia is disabled, Media Anchoring can only be enabled for calls between endpoints belonging to the same SRD.  For more information on Media Anchoring, see No Media Anchoring (Anti-Tromboning) on page 522.

  • Page 283: Configuring Sip Interfaces

    Configure a SIP Interface according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 20-4: SIP Interface Table Parameter Descriptions Parameter Description Index Defines an index for the new table record. [SIPInterface_Index] Version 6.8 Mediant 500L MSBR...
  • Page 284 Mediant 500L MSBR Parameter Description Interface Name Defines an arbitrary name to easily identify the SIP Interface. CLI: interface-name The valid value is a string of up to 21 characters. [SIPInterface_InterfaceName] Network Interface Assigns a Control-type IP network interface to the SIP CLI: network-interface Interface.
  • Page 285 Note: For configuring TCP keepalive, use the following ini file parameters: TCPKeepAliveTime, TCPKeepAliveInterval, and TCPKeepAliveRetry. Classification Failure Response Type Defines the SIP response code that the device sends if a CLI: classification_fail_response_type received SIP request (OPTIONS, REGISTER, or INVITE) Version 6.8 Mediant 500L MSBR...
  • Page 286 Mediant 500L MSBR Parameter Description [SIPInterface_ClassificationFailureRes fails the SBC Classification process. ponseType] The valid value can be a SIP response code from 400 through 699, or it can be set to 0 to not send any response at all. The default response code is 500 (Server Internal Error).

  • Page 287: Configuring Ip Groups

    Incoming IP calls (IP-to-IP or IP-to-Tel): The IP Group identifies the source of the IP call. • The IP Group can be used to associate a number manipulation rule with specific calls identified by IP Group. Version 6.8 Mediant 500L MSBR...
  • Page 288 Mediant 500L MSBR 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 289 Group. If the REGISTER fails, no update is performed. If an UN- REGISTER request arrives, the IP address associated with the IP Group is deleted and therefore, no routing to the IP Group is done. Version 6.8 Mediant 500L MSBR...
  • Page 290 Mediant 500L MSBR Parameter Description Note: This field is applicable only to the SBC and. Description Defines a brief description for the IP Group. CLI: description The valid value is a string of up to 29 characters. The default is an [IPGroup_Description] empty field.
  • Page 291 This is interworked in to the SIP header as follows: User-to-User: 00FA080019001038F725B3;encoding=hex Note: To define the Network Node Identifier of the device for Avaya UCID, use the 'Network Node ID' (NetworkNodeId) parameter. QoE Profile Assigns a Quality of Experience Profile rule. For configuring Quality Version 6.8 Mediant 500L MSBR...
  • Page 292 Mediant 500L MSBR Parameter Description CLI: qoe-profile of Experience Profiles, see ''Configuring Quality of Experience [IPGroup_QOEProfile] Profiles'' on page 264. Bandwidth Profile Assigns a Bandwidth Profile rule. For configuring Bandwidth CLI: bandwidth-profile Profiles, see ''Configuring Bandwidth Profiles'' on page 268.
  • Page 293 IP address is unknown is that IP address forgery (commonly known as IP spoofing) is more difficult than malicious SIP message tampering and therefore, using a Classification rule without an IP address offers a weaker form of Version 6.8 Mediant 500L MSBR...
  • Page 294 Mediant 500L MSBR Parameter Description security. When classification is based on Proxy Set, the Classification table for the specific IP Group is ignored.  If you have assigned the same Proxy Set to multiple IP Groups, disable the parameter and instead, use Classification rules to classify incoming SIP dialogs to these IP Groups.
  • Page 295 URIs. [IPGroup_SourceUriInput]  [-1] Not Configured (default)  [0] From  [1] To  [2] Request-URI  [3] P-Asserted - First Header  [4] P-Asserted - Second Header  [5] P-Preferred Version 6.8 Mediant 500L MSBR...
  • Page 296 Mediant 500L MSBR Parameter Description  [6] Route  [7] Diversion  [8] P-Associated-URI  [9] P-Called-Party-ID  [10] Contact  [11] Referred-by Notes:  This parameter is applicable only when classification is done according to the Classification table. ...

  • Page 297: Configuring Proxy Sets

    Set' parameter in the IP Group table. For configuring IP Groups, see ''Configuring IP Groups'' on page 287. Note: For classifying incoming SIP dialogs to IP Groups, it is highly recommended to use ONLY the Classification table (see Configuring Classification Rules on page 555). Version 6.8 Mediant 500L MSBR...
  • Page 298 Mediant 500L MSBR The following procedure describes how to configure Proxy Sets in the Web interface. You can also configure Proxy Sets using the following management tools:  Proxy Set ID with IP addresses: table ini file parameter, ProxyIP or CLI command, configure voip >...
  • Page 299 15 IP addresses. However, the device supports up to 30 DNS-resolved IP addresses. If the device receives more than this number of DNS-resolved IP addresses, the device uses the first 30 IP addresses in the received list, and ignores the rest. Version 6.8 Mediant 500L MSBR...
  • Page 300 Mediant 500L MSBR Parameter Description Web/EMS: Enable Proxy Keep Enables the device's Proxy Keep-Alive mechanism, which checks Alive communication with the Proxy server. CLI: voip-network proxy-set >  [0] Disable (default). proxy-enable-keep-alive  [1] Using Options = Enables the Proxy Keep-Alive mechanism [ProxySet_EnableProxyKeep using SIP OPTIONS messages.
  • Page 301 To enable this functionality, you must also enable the Proxy Keep-Alive mechanism (using the 'Enable Proxy Keep Alive' parameter).  The Homing option can only be used if the 'Enable Proxy Keep Alive' parameter is set to Using Options. Version 6.8 Mediant 500L MSBR...
  • Page 302 Mediant 500L MSBR Parameter Description Web/EMS: SRD Index Assigns an SRD to the Proxy Set ID. CLI: voip-network proxy-set > The default is SRD 0. srd-id Notes: [ProxySet_ProxySet_SRD]  For this parameter to take effect, a device reset is required.

  • Page 303: Assign Wan Interface To Voip Traffic

    Figure 20-7: Selecting WAN Interface for VoIP Traffic From the 'WAN Interface Name' drop-down list, select the WAN interface for VoIP traffic. Click Submit, and then reset the device for your setting to take effect. Version 6.8 Mediant 500L MSBR...
  • Page 304 Mediant 500L MSBR Assign the selected WAN interface to SIP signaling and RTP (media) interfaces. This is done in the SIP Interface and Media Realm tables respectively (whereby the WAN interface is denoted as "WAN"): Open the SIP Interface Table page (see ''Configuring SIP Interfaces'' on page 283) and configure SIP interfaces on the WAN interface.

  • Page 305: Sip Definitions

    Accounts using the table ini file parameter, Account or CLI command, configure voip > sip-definition account.  To configure an Account: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Version 6.8 Mediant 500L MSBR...
  • Page 306 Mediant 500L MSBR Configure an account according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Once you have configured Accounts, you can register or un-register them, as described below: ...
  • Page 307 If registration fails, the user part in the INVITE Contact header contains the source party number. Application Type Defines the application type: CLI: application-type  [0] GW/IP2IP = (Default) Gateway application. [Account_ApplicationType]  [2] SBC = SBC application. Version 6.8 Mediant 500L MSBR...

  • Page 308: Regular Registration Mode

    Mediant 500L MSBR 21.2.1 Regular Registration Mode When you configure the registration mode in the Account table to Regular, the device sends REGISTER requests to the Serving IP Group. The host name (in the SIP From/To headers) and contact user (user in From/To and Contact headers) are taken from the configured Account table upon successful registration.

  • Page 309: Configuring Proxy And Registration Parameters

    For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 779. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see ''Viewing Registration Status'' on page 700. Version 6.8 Mediant 500L MSBR...
  • Page 310 Mediant 500L MSBR  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Figure 21-1: Proxy & Registration Page Configure the parameters as required.

  • Page 311: 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 500L MSBR/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 312 • 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 313: Configuring Sip Message Manipulation

    Message manipulation can be applied to all outbound calls (except for IP Groups that have been assigned a Manipulation Set ID). This is done by assigning a Manipulation Set ID to the "global" ini file parameter, GWOutboundManipulationSet. Version 6.8 Mediant 500L MSBR...
  • Page 314 Mediant 500L MSBR 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.
  • Page 315 User's Manual 21. SIP Definitions The figure below illustrates a SIP message manipulation example: Figure 21-3: SIP Header Manipulation Example Version 6.8 Mediant 500L MSBR...
  • Page 316 Mediant 500L MSBR 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 317 = 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. CLI: condition The valid value is a string (case-insensitive). [MessageManipulations_Conditi Version 6.8 Mediant 500L MSBR...
  • Page 318 Mediant 500L MSBR Parameter Description 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 CLI: action-subject performed.
  • Page 319 When configured to Use Previous Condition, the 'Message Type' and 'Condition' parameters are not applicable and if configured are ignored.  When multiple manipulation rules apply to the same header, the next rule applies to the resultant string of the previous rule. Version 6.8 Mediant 500L MSBR...

  • Page 320: Configuring Sip Message Policy Rules

    Mediant 500L MSBR 21.5 Configuring SIP Message Policy Rules The Message Policy table lets you configure up to 20 SIP Message Policy rules. SIP Message Policy rules are used to block (blacklist) unwanted incoming SIP messages or permit (whitelist) receipt of desired SIP messages. You can configure legal and illegal characteristics of a SIP message.
  • Page 321 SIP Body Blacklist-Whitelist Policy Body List Defines the SIP body type (i.e., value of the Content-Type CLI: body-list header) to blacklist or whitelist. For example, [MessagePolicy_BodyList] application/sdp. The values of this parameter are case-sensitive. Version 6.8 Mediant 500L MSBR...
  • Page 322 Mediant 500L MSBR Parameter Description Body List Type Defines the policy (blacklist or whitelist) for the SIP body CLI: body-list-type specified in the 'Body List' parameter (above). [MessagePolicy_BodyListType]  [0] Policy Blacklist =The specified SIP body is rejected.  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed;...

  • Page 323: Coders And Profiles

     To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 22-1: Coders Table Page Configure coders according to the parameters described in the table below. Version 6.8 Mediant 500L MSBR...
  • Page 324 Mediant 500L MSBR Click Submit, and then reset the device with a save ("burn") to flash memory. Table 22-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder. CLI: name Note: Each coder type (e.g., G.729) can be configured only once [CodersGroup0_Name] in the table.
  • Page 325 20 (default), 40, 60, 80, Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 T.38 [t38fax] T.38 Version 3 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 Version 6.8 Mediant 500L MSBR...

  • Page 326: Configuring Coder Groups

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

  • Page 327: Configuring Tel Profile

     To configure a Tel Profile: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > Tel Profile Settings). Click Add; the following dialog box appears: Version 6.8 Mediant 500L MSBR...
  • Page 328 Mediant 500L MSBR Configure a Tel Profile according to the parameters described in the table below. For a description of each parameter, refer to the corresponding "global" parameter. Click Submit, and then save ("burn") your settings to flash memory. Table 22-4: Tel Profile Table Parameters and Corresponding Global Parameters...
  • Page 329 Web: Signaling DiffServ PremiumServiceClassControlDiffServ CLI: signaling-diffserv [TelProfile_SigIPDiffServ] Web: Enable Early Media EnableEarlyMedia CLI: early-media [TelProfile_EnableEarlyMedia] Web: Progress Indicator to IP ProgressIndicator2IP CLI: prog-ind-to-ip [TelProfile_ProgressIndicator2IP] Channel Web: Dynamic Jitter Buffer Minimum DJBufMinDelay Delay CLI: jitter-buffer-minimum-delay [TelProfile_JitterBufMinDelay] Version 6.8 Mediant 500L MSBR...
  • Page 330 Mediant 500L MSBR Tel Profile Parameter Global Parameter Web: Dynamic Jitter Buffer Optimization DJBufOptFactor Factor CLI: jitter-buffer-optimization-factor [TelProfile_JitterBufOptFactor] Web: DTMF Volume DTMFVolume CLI: dtmf-volume [TelProfile_DtmfVolume] Web: Input Gain InputGain CLI: input-gain [TelProfile_InputGain] Web: Voice Volume VoiceVolume CLI: voice-volume [TelProfile_VoiceVolume] Web: Echo Canceler...
  • Page 331 CLI: fxo-ring-timeout Note: If this parameter is configured for a specific FXO [TelProfile_FXORingTimeout] port, Caller ID detection does not occur, and the RingBeforeCallerID and FXONumberOfRings parameters do not affect the outgoing INVITE for that FXO port. Version 6.8 Mediant 500L MSBR...

  • Page 332: Configuring Ip Profiles

    Mediant 500L MSBR 22.4 Configuring IP Profiles The IP Profile Settings table lets you configure up to 20 IP Profiles. An IP Profile is a set of parameters with user-defined settings relating to signaling (e.g., SIP message terminations such as REFER) and media (e.g., coder type). An IP Profile can later be assigned to specific IP calls (inbound and/or outbound).
  • Page 333 If the coder lists of both an IP Profile and a Tel Profile apply to the same call, only the coders common to both are used. The order of the coders is determined by the preference.  This parameter is applicable only to the Gateway application. Version 6.8 Mediant 500L MSBR...
  • Page 334 Mediant 500L MSBR Parameter Description Web: RTP IP DiffServ Defines the DiffServ value for Premium Media class of CLI: rtp-ip-diffserv service (CoS) content. [IpProfile_IPDiffServ] The valid range is 0 to 63. The default is 46. Note: The corresponding global parameter is PremiumServiceClassMediaDiffServ.
  • Page 335 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/Q Fuxw|2^31|1:1 If the device selects a crypto line that does not contain Version 6.8 Mediant 500L MSBR...
  • Page 336 Mediant 500L MSBR Parameter Description the MKI 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 337 FaxCNGMode to 1 or 2.  [2] Event Only = The originating fax detects CNG and a fax session is started by the originating fax, using the Re- INVITE message. Typically, T.38 fax session starts when Version 6.8 Mediant 500L MSBR...
  • Page 338 Mediant 500L MSBR Parameter Description the preamble signal is detected by the answering fax. Some SIP devices do not support the detection of this fax signal on the answering fax and thus, in these cases, it is possible to configure the device to start the T.38 fax session when the CNG tone is detected by the originating fax.
  • Page 339 Proceeding or Alerting PRI messages. Sending 183 response also depends on the ReleaseIP2ISDNCallOnProgressWithCause parameter, which must be set to any value other than  See also the IgnoreAlertAfterEarlyMedia parameter. This parameter allows, for example, to interwork Alert with PI Version 6.8 Mediant 500L MSBR...
  • Page 340 Mediant 500L MSBR Parameter Description to SIP 183 with SDP instead of 180 with SDP.  You can also configure early SIP 183 response immediately upon the receipt of an INVITE, using the EnableEarly183 parameter.  Analog: To send a 183 response, you must also set the ProgressIndicator2IP parameter to 1.
  • Page 341 If the number of concurrent calls reaches this [IpProfile_CallLimit] limit, the device rejects any new incoming and outgoing calls belonging to this IP Profile. This parameter can also be set to the following:  [-1] = (Default) No limitation on calls. Version 6.8 Mediant 500L MSBR...
  • Page 342 Mediant 500L MSBR Parameter Description  [0] = All calls are rejected. Note: For Gateway IP-to-IP calls, you can configure the device to route calls to an alternative IP Group when this maximum number of concurrent calls is reached. To do so,...
  • Page 343 All QSIG messages are sent as raw data in corresponding SIP messages using a dedicated message body. Notes:  QSIG tunneling must be enabled on originating and terminating devices.  To enable this function, set the Version 6.8 Mediant 500L MSBR...
  • Page 344 Mediant 500L MSBR Parameter Description ISDNDuplicateQ931BuffMode parameter to 128 (i.e., duplicate all messages).  To define the format of encapsulated QSIG messages, use the QSIGTunnelingMode parameter.  Tunneling according to ECMA-355 is applicable to all ISDN variants (in addition to the QSIG protocol).
  • Page 345 [1] SRTP = SBC legs negotiate only SRTP media lines, and RTP media lines are removed from the incoming SDP offer\answer.  [2] RTP = SBC legs negotiate only RTP media lines, and SRTP media lines are removed from the incoming offer\answer. Version 6.8 Mediant 500L MSBR...
  • Page 346 Mediant 500L MSBR Parameter Description  [3] Both = Each offer\answer is extended (if not already) to two media lines - one RTP and the other SRTP. If two SBC legs (after offer\answer negotiation) use different security types (i.e., one RTP and the other SRTP), the device performs RTP-SRTP transcoding.
  • Page 347 [1] Supported only with SDP = re-INVITE is supported, but only with SDP. If the incoming re-INVITE arrives without SDP, the device creates an SDP and adds it to the outgoing re-INVITE.  [2] Supported = (Default) re-INVITE is supported with or Version 6.8 Mediant 500L MSBR...
  • Page 348 Mediant 500L MSBR Parameter Description without SDP. Web: Remote Delayed Offer Support Defines whether the remote endpoint supports delayed offer CLI: sbc-rmt-delayed-offer (i.e., initial INVITEs without an SDP offer). [IpProfile_SBCRemoteDelayedOfferS  [0] Not Supported = Initial INVITE requests without SDP upport] are not supported.
  • Page 349 [1] 180 = Early media is sent as 180 response only.  [2] 183 = Early media is sent as 183 response only. Web: Remote Early Media Defines whether the remote side can accept early media or CLI: sbc-rmt-early-media-supp Version 6.8 Mediant 500L MSBR...
  • Page 350 Mediant 500L MSBR Parameter Description [IpProfile_SBCRemoteEarlyMediaSup not. port]  [0] Not Supported = Early media is not supported.  [1] Supported = (Default) Early media is supported. Web: Enforce MKI Size Enables MKI length negotiation for SRTP-to-SRTP flows CLI: sbc-enforce-mki-size between SIP networks (i.e., IP Groups).
  • Page 351  [0] Standard = (Default) The SIP entity supports INVITE messages containing Replaces headers. The device forwards the INVITE message containing the Replaces header to the SIP entity. The device may change the Version 6.8 Mediant 500L MSBR...
  • Page 352 Mediant 500L MSBR Parameter Description value of the Replaces header to reflect the call identifiers of the leg.  [1] Handle Locally = The SIP entity does not support INVITE messages containing Replaces headers. The device terminates the received INVITE containing the Replaces header and establishes a new call between the SIP entity and the new call party.
  • Page 353 [IpProfile_SBCJitterCompensation] inconsistent intervals (i.e., packet delay variation). The jitter buffer stores the packets and sends them out at a constant rate (according to the coder's settings).  [0] Disable (default) Version 6.8 Mediant 500L MSBR...
  • Page 354 Mediant 500L MSBR Parameter Description  [1] Enable Note: The jitter buffer parameters, 'Dynamic Jitter Buffer Minimum Delay' (DJBufMinDelay) and 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed. User's Manual...

  • Page 355: Gateway Application

    Part V Gateway Application...

  • Page 357: Introduction

    CO or the PBX) and connects to analog telephones, dial-up modems, and fax machines. The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. Version 6.8 Mediant 500L MSBR...
  • Page 358 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 359: Digital Pstn

    • The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. Version 6.8 Mediant 500L MSBR...
  • Page 360 Mediant 500L MSBR  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). 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 361 Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'. To save the changes to flash memory, see ''Saving Configuration'' on page 606. To reset the device, see ''Resetting the Device'' on page 603. Version 6.8 Mediant 500L MSBR...

  • Page 362: Tdm And Timing

    Mediant 500L MSBR 24.2 TDM and Timing This section describes the configuration of the TDM and clock timing parameters. 24.2.1 Configuring TDM Bus Settings The TDM page allows you to configure the device's Time-Division Multiplexing (TDM) bus settings. For a description of these parameters, see ''PSTN Parameters'' on page 934.

  • Page 363: Recovering Clock From Pstn Line Interface

     To configure internal clock as clock source: Set the clock source to be from the device's internal oscillator. In the TDM Bus Settings page, set the 'TDM Bus Clock Source' parameter (TDMBusClockSource) to Internal. Version 6.8 Mediant 500L MSBR...

  • Page 364: Configuring Cas State Machines

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

  • Page 366: Configuring Digital Gateway Parameters

    Mediant 500L MSBR 24.4 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 779.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 367: Tunneling Applications

    SIP INFO messages.  Call tear-down: The SIP connection is terminated once the QSIG call is complete. The Release Complete message is encapsulated in the SIP BYE message that terminates the session. Version 6.8 Mediant 500L MSBR...

  • Page 368: Isdn Overlap Dialing

    Mediant 500L MSBR  To enable QSIG tunneling: In the Digital Gateway Parameters page (Configuration tab > VoIP menu > GW and IP to IP > Digital Gateway > Digital Gateway Parameters), set the 'Enable QSIG Tunneling' parameter (EnableQSIGTunneling) to Enable on the originating and terminating devices.

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

    MaxDigits: Defines the maximum number of collected digits that can be received from the Tel side (if ISDN Sending Complete IE is not received). When the number of collected digits reaches the maximum, the device uses these digits for the called destination number. Version 6.8 Mediant 500L MSBR...
  • Page 370 Mediant 500L MSBR • TimeBetweenDigits: Defines the maximum time (in seconds) that the device waits between digits received from the Tel side. When the time expires, the device uses the collected digits to dial the called destination number. • MuteDTMFInOverlap: Enables the device to ignore in-band DTMF digits received during overlap dialing.

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

    NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Table 24-3: Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Yes* * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 6.8 Mediant 500L MSBR...
  • Page 372 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 373: Trunk Group

    ''Configuring Trunk Group Settings'' on page 375).  To register the Trunk Groups, click the Register button, located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Version 6.8 Mediant 500L MSBR...
  • Page 374 Mediant 500L MSBR Table 25-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the telephony interface module for which you want to CLI: module define the Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 375: Configuring Trunk Group Settings

    Open the Trunk Group Settings page (Configuration tab > VoIP menu > GW and IP to IP > Trunk Group > Trunk Group Settings). Configure a Trunk Group according to the parameters described in the table below. Version 6.8 Mediant 500L MSBR...
  • Page 376 Mediant 500L MSBR Click Submit, and then save ("burn") your settings to flash memory. Table 25-2: Trunk Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_Trun kGroupId]...
  • Page 377 Account table (see ''Configuring Registration Accounts'' on page 305). An example is shown below of a REGISTER message for registering 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 Version 6.8 Mediant 500L MSBR...
  • Page 378 Mediant 500L MSBR Parameter Description 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 287).
  • Page 379 Mail on page 482. Admin State (Read-only) Displays the administrators state:  "Locked": The Lock command has been chosen from the Action drop-down button.  "Unlocked": The Unlock command has been chosen from the Action drop-down button. Version 6.8 Mediant 500L MSBR...
  • Page 380 Mediant 500L MSBR Parameter Description Status (Read-only) Displays the current status of the trunks/channels in the Trunk Group:  "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).

  • Page 381: Manipulation

    551 and uses rule index 2 for numbers that start with 550, 552, 553, and so on until 559. 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 Version 6.8 Mediant 500L MSBR...
  • Page 382 Mediant 500L MSBR numbers that start with 551. If the device doesn't find a matching rule, no manipulation is done on the call.You can perform a second "round" (additional) of source and destination number manipulations for IP-to-Tel calls, on an already manipulated number. The initial and additional number manipulation rules are both configured in the number manipulation tables for Ip-to-Tel calls.
  • Page 383 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Version 6.8 Mediant 500L MSBR...
  • Page 384 Mediant 500L MSBR Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 26-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
  • Page 385 [Prefix2Add] Web: Suffix to Add Defines the number or string that you want added to the end of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone number Version 6.8 Mediant 500L MSBR...
  • Page 386 Mediant 500L MSBR Parameter Description CLI: suffix-to-add is 1234, the new number is 123400. [Suffix2Add] Web/EMS: Number of Defines the number of digits that you want to keep from the right of the Digits to Leave phone number. For example, if you enter 4 and the phone number is CLI: num-of-digits-to-leave 00165751234, then the new number is 1234.

  • Page 387: Manipulating Number Prefix

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

  • Page 388: Sip Calling Name Manipulations

    Mediant 500L MSBR 26.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 389 ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 777. The default value is the asterisk (*) symbol (i.e., any source prefix). Web: Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. Version 6.8 Mediant 500L MSBR...
  • Page 390 Mediant 500L MSBR Parameter Description CLI: calling-name-prefix You can use special notations for denoting the prefix. For example, to [_CallingNamePrefix] denote calls without a calling name, use the $ sign. For a description of available notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 777.

  • Page 391: Configuring Redirect Number Ip To Tel

    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. • The device uses the 'Redirect Prefix' parameter before it manipulates the prefixi. Version 6.8 Mediant 500L MSBR...
  • Page 392 Mediant 500L MSBR The following procedure describes how to configure redirect number manipulation rules in the Web interface. You can also configure these rules using the following management tools:  Redirect Number IP to Tel table: ini file parameter, RedirectNumberMapIp2Tel or CLI command, configure voip/gw manipulations redirect-number-map-ip2tel ...
  • Page 393 Defines the number of digits that you want to retain from the right of to Leave the redirect number. CLI: num-of-digits-to-leave [_LeaveFromRight] Web/EMS: Prefix to Add Defines the number or string that you want added to the front of the Version 6.8 Mediant 500L MSBR...
  • Page 394 Mediant 500L MSBR Parameter Description CLI: prefix-to-add redirect number. For example, if you enter 9 and the redirect number [_Prefix2Add] is 1234, the new number is 91234. Web/EMS: Suffix to Add Defines the number or string that you want added to the end of the CLI: suffix-to-add redirect number.

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

    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 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 26.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. The 'phone-context' parameter appears in the standard SIP headers where a phone number is used (i.e., Request-URI, To, From, and Diversion).

  • Page 397: Configuring Release Cause Mapping

    This parameter defines a default ISDN Cause that is always used except when the following Release Causes are received: Normal Call Clearing (16), User Busy (17), No User Responding (18) or No Answer from User (19). Version 6.8 Mediant 500L MSBR...
  • Page 398 Mediant 500L MSBR The following procedure describes how to configure ISDN-SIP release cause mapping in the Web interface. You can also configure this mapping using the following management platforms:  Release Cause Mapping from ISDN to SIP table: ini file parameter, CauseMapISDN2SIP or CLI command, configure voip >...

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

    Server internal error Temporary failure Not implemented Network out of order Bad gateway Network out of order Service unavailable Temporary failure Server timeout Recovery on timer expiry 505* Version not supported Interworking Busy everywhere User busy Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR ISDN Release SIP Response Description Description Reason Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does not specify their cause code mapping.
  • Page 401 409* Conflict implemented Information element non-existent or not 480* Not found implemented Invalid information elements contents 501* Not implemented Message not compatible with call state 503* Service unavailable Recovery of timer expiry Request timeout Version 6.8 Mediant 500L MSBR...

  • Page 402: Reason Header

    Mediant 500L MSBR ISDN Release Description Description Reason Response Protocol error Server internal error Interworking unspecified Server internal error * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft doesn’t specify their cause code mapping. 26.8.3 Reason Header The device supports the SIP Reason header according to RFC 3326.

  • Page 403: Numbering Plans And Type Of Number

    Level 2 Regional [1] Level 1 Regional [2] A private number with a location, e.g., 3932200. PISN Specific [3] Level 0 Regional (local) [4] A private local extension number, e.g., 2200. Version 6.8 Mediant 500L MSBR...
  • Page 404 Mediant 500L MSBR For NI-2 and DMS-100 ISDN variants, the valid combinations of TON and NPI for calling and called numbers include (Plan/Type):  0/0 - Unknown/Unknown  1/1 - International number in ISDN/Telephony numbering plan  1/2 - National number in ISDN/Telephony numbering plan ...

  • Page 405: Routing

    If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call. : Version 6.8 Mediant 500L MSBR...
  • Page 406 Mediant 500L MSBR  Matching Characteristics: One or more characteristics can be defined for the rule: • Source IP Group (to which the call belongs) • Source and destination Request-URI host name prefix • Source Trunk Group (from where the call is received) •...
  • Page 407 IP addresses. Instead of an IP address, you can use an FQDN to resolve into two IP addresses. For more information on alternative routing, see ''Alternative Routing for Tel-to-IP Calls'' on page 419. Version 6.8 Mediant 500L MSBR...
  • Page 408 Mediant 500L MSBR  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine with calculating the cost of using a service (Tel-to-IP call) and relaying that information to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule.
  • Page 409 Number Manipulation'' on page 381. Route Name Defines an arbitrary name to easily identify the routing rule. CLI: route-name The valid value is a string of up to 20 characters. By default, no [PREFIX_RouteName] value is defined. Version 6.8 Mediant 500L MSBR...
  • Page 410 Mediant 500L MSBR Parameter Description Matching Call Characteristics Web: Src. Trunk Group ID Defines the Trunk Group from where the call is received. EMS: Source Trunk Group ID To denote any Trunk Group, use the asterisk (*) symbol. CLI: src-trunk-group-id [PREFIX_SrcTrunkGroupID] Web: Dest.
  • Page 411 INVITE message is sent only to the IP Group (and not the defined IP address).  If the destination is a User-type IP Group, the device searches for a match between the Request-URI (of the received INVITE) Version 6.8 Mediant 500L MSBR...
  • Page 412 Mediant 500L MSBR Parameter Description to an AOR registration record in the device's database. The INVITE is then sent to the IP address of the registered contact.  If the parameter AlwaysUseRouteTable is set to 1 (see ''Configuring IP Groups'' on page 287), then the Request-URI host name in the INVITE message is set to the value defined for the parameter 'Dest.
  • Page 413 You can also use LDAP routing rules with standard routing rules for Forking Groups.  When the UseDifferentRTPportAfterHold parameter is enabled, every forked call is sent with a different RTP port. Thus, ensure Version 6.8 Mediant 500L MSBR...

  • Page 414: Configuring Inbound Ip Routing

    Mediant 500L MSBR Parameter Description that the device has sufficient available RTP ports for these forked calls. 27.3 Configuring Inbound IP Routing The Inbound IP Routing table lets you configure up to 120 inbound call routing rules:  For IP-to-IP routing: The table is used to identify an incoming call as an IP-to-IP call and subsequently, to assign the call to an IP Group, referred to as a source IP Group.
  • Page 415 4. This call is routed according to the outbound IP routing rules for this Source IP Group configured in the Outbound IP Routing table. Configure a routing rule according to the parameters described in the table below. Click Submit. Version 6.8 Mediant 500L MSBR...
  • Page 416 Mediant 500L MSBR Table 27-3: IP-to-Tel or Inbound IP Routing Table Parameter Description Parameter Description IP to Tel Routing Mode Determines whether to route the incoming IP call before or after CLI: configure voip/gw routing manipulation of destination number, configured in ''Configuring general-setting/ip2tel-rte-mode Source/Destination Number Manipulation'' on page 381.
  • Page 417 ChannelSelectMode.  Currently, this field can only be configured using the ini file. Web: IP Profile ID Assigns an IP Profile (configured in ''Configuring IP Profiles'' on CLI: ip-profile-id page 332) to the call. [PstnPrefix_ProfileId] Version 6.8 Mediant 500L MSBR...

  • Page 418: Ip Destinations Connectivity Feature

    Mediant 500L MSBR Parameter Description Web: Source IP Group ID For IP-to-Tel calls: Defines the IP Group associated with the CLI: src-ip-group-id incoming IP call. This is the IP Group that sent the INVITE [PstnPrefix_SrcIPGroupID] message. This IP Group can later be used as the 'Serving IP Group' in the Account table for obtaining authentication user name/password for this call.

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

    IP address. The connectivity status of the IP destination is displayed in the 'Status' column of the Outbound IP Routing table per routing rule. If it displays a status other than "ok", the device Version 6.8 Mediant 500L MSBR...

  • Page 420: Alternative Routing Based On Sip Responses

    Mediant 500L MSBR considers the IP destination as unavailable and attempts to re-route the call to an alternative destination. For more information on the IP connectivity methods and on viewing IP connectivity status, see ''IP Destinations Connectivity Feature'' on page 418.
  • Page 421 (configured by the HotSwapRtx parameter), the device attempts to communicate (using the same INVITE) with the next configured (redundant) proxy in the list, and so on until an available redundant proxy is located. Once an available proxy is located, Version 6.8 Mediant 500L MSBR...
  • Page 422 Mediant 500L MSBR the device can operate in one of the following modes (configured by the ProxyRedundancyMode parameter): • Parking mode: The device continues operating with the redundant proxy (now active) until the next failure occurs, after which it switches to the next redundant proxy.

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

    PSTN. This configuration is necessary as the re-routed call is now considered an IP-to-Tel call. For configuring IP-to-Tel routing rules, see ''Configuring the Inbound IP Routing'' on page 414. Note: The PSTN Fallback feature is applicable only to digital interfaces. Version 6.8 Mediant 500L MSBR...

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

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

  • Page 425: 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: Version 6.8 Mediant 500L MSBR...
  • Page 426 Mediant 500L MSBR  For digital interfaces: “out-of-service” - all trunks are unavailable/disconnected  "unavailable": • For digital interfaces: All trunks are busy or unavailable • For analog interfaces: All FXS / FXO lines pertaining to a Trunk Group are busy...

  • Page 427: Alternative Routing Upon Isdn Disconnect

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

  • Page 429: Configuring Dtmf And Dialing

    Open the DTMF & Dialing page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > DTMF & Dialing). Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 606. Version 6.8 Mediant 500L MSBR...

  • Page 430: Dialing Plan Features

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

  • Page 432: External Dial Plan File

    Mediant 500L MSBR 28.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 622. User's Manual Document #: LTRT-10466...

  • Page 433: Configuring Supplementary Services

    ''Configuration Parameters Reference'' on page 779.  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). Version 6.8 Mediant 500L MSBR...
  • Page 434 Mediant 500L MSBR Configure the parameters as required. 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 606.

  • Page 435: Call Hold And Retrieve

    (or any other hold tone) is played (over IP) by the remote party. You can also configure the device to keep a call on-hold for a user-defined time after which the call is disconnected, using the HeldTimeout parameter. Version 6.8 Mediant 500L MSBR...
  • Page 436 Mediant 500L MSBR The device also supports "double call hold" for FXS interfaces where the called party, which has been placed on-hold by the calling party, can then place the calling party on hold as well and make a call to another destination. The flowchart below provides an example of...

  • Page 437: Call Pickup

    Only one call can be suspended per trunk. If another suspend request is received from a BRI phone while there is already a suspended call (even if done by another BRI phone connected to the same trunk), the device rejects this suspend request. Version 6.8 Mediant 500L MSBR...

  • Page 438: Consultation Feature

    Mediant 500L MSBR 29.4 Consultation Feature The device's Consultation feature allows you to place one number on hold and make a second call to another party.  After holding a call (by pressing hook-flash), the holding party hears a dial tone and can then initiate a new call, which is called a Consultation call.

  • Page 439: Consultation Transfer For Qsig Path Replacement

    This called party number is then manipulated using the IP-to-Tel Destination Phone Number Manipulation table. The source number of the transferred call is taken from the original call, according to its initial direction: • Tel-to-IP call: source number of the original call. Version 6.8 Mediant 500L MSBR...

  • Page 440: Call Forward

    Mediant 500L MSBR • IP-to-Tel call: destination number of the original call. • If the UseReferredByForCallingNumber parameter is set to 1, the source number is taken from the SIP Referred-By header if included in the received SIP REFER message. 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.

  • Page 441: Call Forward Reminder Ring

    From and To: contain the same information, indicating the specific endpoint  Event: ua-profile  Content-Type: "application/simservs+xml"  Message body is the XML body and contains the “dial-tone-pattern” set to "special- condition-tone" (<ss:dial-tone-pattern>special-condition-tone</ss:dial-tone-pattern>), which is the special tone indication. Version 6.8 Mediant 500L MSBR...

  • Page 442: Call Forward Reminder Dial Tone (Off-Hook) Upon Spanish Sip Alert-Info

    Mediant 500L MSBR To cancel the special dial tone and playing the regular dial tone, the received SIP NOTIFY message must contain the following headers:  From and To: contain the same information, indicating the specific endpoint  Event: ua-profile ...

  • Page 443: Call Waiting

    The called party can accept the new call using hook-flash, and can toggle between the two calls.  To enable call waiting: Set the parameter EnableCallWaiting to 1. Set the parameter EnableHold to 1. Version 6.8 Mediant 500L MSBR...

  • Page 444: Message Waiting Indication

    Mediant 500L MSBR Define the Call Waiting indication and call waiting ringback tones in the Call Progress Tones file. You can define up to four call waiting indication tones (refer to the FirstCallWaitingToneID parameter). To configure the call waiting indication tone cadence, modify the following parameters:...
  • Page 445 BRI extension and a red light flashes on the BRI extension’s phone. Once the voice message is retrieved, the MWI light on the BRI phone turns off. This is configured by setting the VoiceMailInterface parameter to 8 (“ETSI”) and enabled by the EnableMWI parameter. Version 6.8 Mediant 500L MSBR...
  • Page 446 Mediant 500L MSBR  Euro-ISDN MWI: The device supports Euro-ISDN MWI for IP-to-Tel calls. The device interworks SIP MWI NOTIFY messages to Euro-ISDN Facility information element (IE) MWI messages. This is configured by setting the VoiceMailInterface parameter to 8. ...

  • Page 447: Caller Id

    PolarityReversalType: some Caller ID signals use reversal polarity and/or wink signals. In these scenarios, it is recommended to set PolarityReversalType to 1 (Hard) (FXS only).  The Caller ID interworking can be changed using the parameters UseSourceNumberAsDisplayName and UseDisplayNameAsSourceNumber. Version 6.8 Mediant 500L MSBR...

  • Page 448: Debugging A Caller Id Detection On Fxo

    ID. If the above does not solve the problem, you need to record the caller ID signal (and send it to AudioCodes), as described below.  To record the caller ID signal using the debug recording mechanism: Access the FAE page (by appending "FAE"...

  • Page 449: Three-Way Conferencing

    The device supports the following conference modes:  Conference Managed by External, AudioCodes Conferencing (Media) Server: The conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.
  • Page 450 Mediant 500L MSBR • The conference-initiating INVITE sent by the device uses only the ConferenceID as the Request-URI. The Conferencing server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants.
  • Page 451 Open the Supplementary Services page. Set 'Enable 3-Way Conference' to Enable (Enable3WayConference = 1). Set '3-Way Conference Mode' to On Board (3WayConferenceMode = 2). 'Flash Keys Sequence Style' Sequence Sequence (FlashKeysSequenceStyle = 1 or 2). Version 6.8 Mediant 500L MSBR...

  • Page 452: Emergency E911 Phone Number Services

    Mediant 500L MSBR 29.11 Emergency E911 Phone Number Services This section describes the device's support for emergency phone number services. The device supports the North American emergency telephone number system known as Enhanced 911 (E911), according to the TR-TSY-000350 and Bellcore's GR-350-Jun2003 standards.
  • Page 453 SipGtw = configured by the SIPGatewayName parameter  From header/user part = calling party number as received from the MF spill The ANI and the pseudo-ANI numbers are sent to the PSAP either in the From and/or P- AssertedID SIP header. Version 6.8 Mediant 500L MSBR...
  • Page 454 Mediant 500L MSBR Typically, the MF spills are sent from the E911 tandem switch to the PSAP, as shown in the table below: Table 29-1: Dialed MF Digits Sent to PSAP Digits of Calling Number Dialed MF Digits 8 digits "nnnnnnnn" (ANI) "KPnnnnnnnnST"...

  • Page 455: Fxo Device Interworking Sip E911 Calls From Service Provider's Ip Network To Psap Did Lines

    Following the "hookflash" Wink signal, the PSAP sends DTMF digits. These digits are detected by the device and forwarded to the IP, using RFC 2833 telephony events (or inband, depending on the device's configuration). Typically, this Wink signal followed by the DTMF digits initiates a call transfer. Version 6.8 Mediant 500L MSBR...
  • Page 456 Mediant 500L MSBR For supporting the E911 service, used the following configuration parameter settings:  Enable911PSAP = 1 (also forces the EnableDIDWink and EnableReversalPolarity)  HookFlashOption = 1 (generates the SIP INFO hookflash message) or 4 for RFC 2833 telephony event ...
  • Page 457 Contact: <sip:101@10.33.37.78> Supported: em,100rel,timer,replaces,path Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO ,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-FXO/v.6.80A.227.005 Privacy: none P-Asserted-Identity: "0123456789" <sip:3333344444@audiocodes.com> Content-Type: application/sdp Content-Length: 253 o=AudiocodesGW 771609035 771608915 IN IP4 10.33.37.78 s=Phone-Call c=IN IP4 10.33.37.78 t=0 0 m=audio 4000 RTP/AVP 8 0 101 Version 6.8 Mediant 500L MSBR...

  • Page 458: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls

    Mediant 500L MSBR a=rtpmap:8 pcma/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv  Example B: The detection of a Wink signal generates the following SIP INFO message: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: port1vega1 <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...

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

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

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

    Mediant 500L MSBR The E9-1-1 Selective Router determines the geographical location of the caller by requesting this information from an Automatic Location Identification (ALI) database based on the phone number or Automatic Number Identifier (ANI) of the 911 caller. Exact location information is also supplied by the Master Street Address Guide (MSAG) database, which is a companion database to the ALI database.
  • Page 461 When the client returns to any previously stored location, the client is automatically set to that location. A user can also manually select any location stored in the local users table and manage existing entries. Version 6.8 Mediant 500L MSBR...
  • Page 462 Mediant 500L MSBR 29.11.4.2.2 Adding ELINs to the Location Information Server As mentioned in the previous section, the Administrator needs to populate the Location Information Server (LIS) database with a network wire map, which maps the Enterprise's network elements to civic addresses. Once done, it can automatically locate clients within a network.
  • Page 463 911 callers within this ERL. The figure below illustrates the use of ERLs and ELINs, with an E9-1-1 call from floor 2 at the branch office: Figure 29-7: Implementing ERLs and ELINs for E9-1-1 in Lync Server 2010 Version 6.8 Mediant 500L MSBR...

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

    PSAP, based on ELIN-address match lookup in the Emergency Services provider's ALI database. The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN.
  • Page 465 ELIN is disregarded and no longer used (for PSAP callback). Therefore, table entries of only the most recently terminated E9-1-1 callers are considered in the ELIN table. The maximum entries in the ELIN table depend on the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment: •...
  • Page 466 Mediant 500L MSBR CSeq: 8 INVITE Call-ID: e6828be1-1cdd-4fb0-bdda-cda7faf46df4 VIA: SIP/2.0/TLS 192.168.0.244:57918;branch=z9hG4bK528b7ad7 CONTACT: <sip:voip_911_user1@contoso.com;opaque=user:epid:R4bCDaUj51a06PUbk raS0QAA;gruu>;text;audio;video;image PRIORITY: emergency CONTENT-TYPE: multipart/mixed; boundary= ------ =_NextPart_000_4A6D_01CAB3D6.7519F890 geolocation: <cid:voip_911_user1@contoso.com>;inserted- by="sip:voip_911_user1@contoso .com" Message-Body: ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/sdp ; charset=utf-8 o=- 0 0 IN IP4 Client s=session c=IN IP4 Client...
  • Page 467 However, if another E9-1-1 caller has subsequently been processed with the same ELIN number, then the PSAP callback is routed to this new E9-1-1 caller. Version 6.8 Mediant 500L MSBR...
  • Page 468 Mediant 500L MSBR In scenarios where the same ELIN number is being used by multiple E9-1-1 callers, upon receipt of a PSAP callback, the ELIN Gateway sends the call to the most recent E9-1-1 caller. For example, if the ELIN number "4257275678" is being used by three E9-1-1 callers, as shown in the table below, then when a PSAP callback is received, the ELIN Gateway sends it to the E9-1-1 caller with phone number "4258359555".

  • Page 469: Configuring Audiocodes Elin Gateway

    User's Manual 29. Configuring Supplementary Services 29.11.4.4 Configuring AudioCodes ELIN Gateway This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment. 29.11.4.4.1 Enabling the E9-1-1 Feature By default, the E9-1-1 feature in the ELIN Gateway for Lync Server 2010 is disabled. To...
  • Page 470 Mediant 500L MSBR 29.11.4.4.4 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 471 4257275678 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616 22:11:45 0 4258359777 ------------ Current Time: 22:12:40  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump Version 6.8 Mediant 500L MSBR...

  • Page 472: Multilevel Precedence And Preemption

    Mediant 500L MSBR 29.12 Multilevel Precedence and Preemption The device supports Multilevel Precedence and Preemption (MLPP) service. MLPP is a call priority scheme, which does the following:  Assigns a precedence level (priority level) to specific phone calls or messages.
  • Page 473 Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value): Table 29-8: Mapping of SIP Resource-Priority Header to PRI Precedence Level for MLPP MLPP Precedence Level PRI Precedence Level SIP Resource-Priority Header Field Routine Priority Immediate Flash Flash Override Version 6.8 Mediant 500L MSBR...

  • Page 474: Mlpp Preemption Events In Sip Reason Header

    Mediant 500L MSBR  If the network-domain field in the Resource-Priority header is any value other than "uc", then the device sets the Precedence Level field to "0 1 0 0" (i.e., "routine"). This can be modified using the EnableIp2TelInterworkingtable field of the ini file parameter, ResourcePriorityNetworkDomains.

  • Page 475: Precedence Ring Tone

    200 OK is received from the remote destination. When a 200 OK is received, a double answer is sent from the FXO line. • Ensure that the PSTN side is configured to identify this double-answer signal. Version 6.8 Mediant 500L MSBR...

  • Page 476: Configuring Multi-Line Extensions And Supplementary Services

    Mediant 500L MSBR 29.14 Configuring Multi-Line Extensions and Supplementary Services The Supplementary Services table lets you configure up to 100 supplementary services for endpoints connected to the device. These endpoints include analog FXS phones and Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) phones.
  • Page 477 Open the Supplementary Services Table page (Configuration tab > VoIP menu > GW and IP to IP > DTMF and Supplementary > Supp Services Table). Click Add; the following dialog box appears: Figure 29-10: Supplementary Services Table - Add Record Version 6.8 Mediant 500L MSBR...
  • Page 478 Mediant 500L MSBR Configure a supplementary service according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. The figure below displays an example of multiple-line extensions configured in the Supplementary Services table: Figure 29-11: Supplementary Services Table Page You can register and un-register an endpoint configured in the table.

  • Page 479: Detecting Collect Calls

    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 480 The device supports various methods for AOC:  Tel-to-IP direction: The device converts the AOC messages received in the EURO ISDN Facility IE messages into SIP INFO and BYE messages using AudioCodes proprietary SIP AOC header.  IP-to-Tel direction provides optional methods: •...

  • Page 481: Configuring Charge Codes

    IP > DTMF and Supplementary > Charge Codes). Figure 29-12: Charge Codes Table Page Configure a Charge Code according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500L MSBR...

  • Page 482: Configuring Voice Mail

    Mediant 500L MSBR Table 29-10: Charge Codes Table Parameter Descriptions Parameter Description Defines the end of the time period in a 24 hour format, hh. For End Time CLI: end-time-<1-4> example, "04" denotes 4 A.M. [ChargeCode_EndTime<1-4>] Notes:  The first time period always starts at midnight (00).
  • Page 483 User's Manual 29. Configuring Supplementary Services Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 606. Version 6.8 Mediant 500L MSBR...
  • Page 484 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 485: Analog Gateway

    • The activation of each feature remains in effect until it is deactivated (i.e., not deactivated after a call). • For a description of the keypad parameters, see ''Telephone Keypad Sequence Parameters'' on page 978. Version 6.8 Mediant 500L MSBR...
  • Page 486 Mediant 500L MSBR  To configure the keypad features Open the Keypad Features page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Keypad Features). Figure 30-1: Keypad Features Page Configure the keypad features as required.

  • Page 487: Configuring Metering Tones

    If you set the 'Generate Metering Tones' parameter to Internal Table, access the Charge Codes Table page by clicking the Charge Codes Table button. For more information on configuring the Charge Codes table, see ''Configuring Charge Codes'' on page 481. Version 6.8 Mediant 500L MSBR...

  • Page 488: Configuring Fxo Settings

    Mediant 500L MSBR 30.3 Configuring FXO Settings The FXO Settings page allows you to configure the device's specific FXO parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 779. Note: The FXO Settings page is available only for FXO interfaces.

  • Page 489: Configuring Authentication

    Click Submit, and then save ("burn") your settings to flash memory. Table 30-1: Authentication Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table record. [Authentication_Index] Port (Read-only) Displays the port number. Version 6.8 Mediant 500L MSBR...

  • Page 490: Configuring Automatic Dialing

    Mediant 500L MSBR Parameter Description CLI: port [Authentication_Port] Module (Read-only) Displays the module number on which the port is CLI: port-type located. [Authentication_Module] Port Type (Read-only) Displays the port type (FXS or FXO). [Authentication_PortType] User Name Defines the user name used for authenticating the port.
  • Page 491 Hotline (i.e., 'Auto Dial Status' is set to Hotline). The valid value is 0 to 60. The default is 16. Note: You can configure this Hotline interval for all ports, using the global parameter, HotLineToneDuration. Version 6.8 Mediant 500L MSBR...

  • Page 492: Configuring Caller Display Information

    Mediant 500L MSBR 30.6 Configuring Caller Display Information The Caller Display Information table lets you configure caller identification strings (Caller ID) per FXS and FXO port. this table also lets you enable the device to send the Caller ID to the IP when a call is made. The called party can use this information for caller identification.

  • Page 493: Configuring Call Forward

    Click Add; the following dialog box appears: Figure 30-5: Call Forward Table - Edit Record Configure call forwarding per port according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 500L MSBR...
  • Page 494 Mediant 500L MSBR Table 30-4: Call Forward Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table record. [FwdInfo_Index] Module (Read-only) Displays the module number on which the port is located. [FwdInfo_Module] Port (Read-only) Displays the port number.

  • Page 495: Configuring Caller Id Permissions

    (Read-only) Displays the port number. [EnableCallerId_Port] Port Type (Read-only) Displays the port type (e.g., FXS). [EnableCallerId_PortType] Caller ID Enables Caller ID generation (FXS) or detection (FXO) per port. CLI: caller-id  [0] Disable [EnableCallerId_IsEnabled]  [1] Enable Version 6.8 Mediant 500L MSBR...

  • Page 496: Configuring Call Waiting

    Mediant 500L MSBR 30.9 Configuring Call Waiting The Call Waiting table lets you enable or disable call waiting per FXS port. Notes: • You can enable or disable call waiting for all the device's ports using the global parameter, 'Enable Call Waiting' in the Supplementary Services page (Configuration tab >...
  • Page 497 When the device detects a hook-flash from the FXS port, the device switches to the waiting call. The device that initiated the waiting call plays a call waiting ringback tone to the calling party after a 182 response is received. Version 6.8 Mediant 500L MSBR...

  • Page 498: Rejecting Anonymous Calls

    Mediant 500L MSBR 30.10 Rejecting Anonymous Calls You can configure the device to reject anonymous calls received from the IP and destined port. This configured using file parameter, RejectAnonymousCallPerPort. If configured, when an FXS interface receives an anonymous call, the device rejects the call and responds with a SIP 433 (Anonymity Disallowed) response.

  • Page 499: Fxs/Fxo Coefficient Types

    The FXS Coefficient types provide best termination and transmission quality adaptation for two FXS line type interfaces. This parameter affects the following AC and DC interface parameters:  DC (battery) feed characteristics  AC impedance matching  Transmit gain  Receive gain  Hybrid balance Version 6.8 Mediant 500L MSBR...

  • Page 500: Fxo Operating Modes

    Mediant 500L MSBR  Frequency response in transmit and receive direction  Hook thresholds  Ringing generation and detection parameters  To select the FXO and FXS Coefficient types: Open the Analog Settings page (Configuration tab > VoIP menu > Media > Analog Settings).

  • Page 501: One-Stage Dialing

    Voice Detection: the device sends a 200 OK in response to an INVITE only when it detects the start of speech (fax or modem answer tone) from the Tel side. Note that the IPM detectors must be enabled. Version 6.8 Mediant 500L MSBR...

  • Page 502: Two-Stage Dialing

    Mediant 500L MSBR 30.13.1.2 Two-Stage Dialing Two-stage dialing is when the IP caller is required to dial twice. The caller initially dials to the FXO device and only after receiving a dial tone from the PBX (via the FXO device), dials the destination telephone number.

  • Page 503: Fxo Operations For Tel-To-Ip Calls

    Automatic Dialing Automatic dialing is defined using the Web interface's Automatic Dialing (TargetOfChannel ini file parameter) page, described in see ''Configuring Automatic Dialing'' on page 490. The SIP call flow diagram below illustrates Automatic Dialing. Version 6.8 Mediant 500L MSBR...

  • Page 504: Collecting Digits Mode

    Mediant 500L MSBR 30.13.2.2 Collecting Digits Mode When automatic dialing is not defined, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 30-11: Call Flow for Collecting Digits Mode 30.13.2.3 FXO Supplementary Services The FXO supplementary services include the following: ...

  • Page 505: Call Termination On Fxo Devices

    Note: This method operates correctly only if silence suppression is not used.  Protocol-based termination of the call from the IP side Note: The implemented disconnect method must be supported by the CO or PBX. Version 6.8 Mediant 500L MSBR...

  • Page 506: Call Termination Before Call Establishment

    Mediant 500L MSBR 30.13.3.2 Call Termination before Call Establishment The device supports the following call termination methods before a call is established:  Call termination upon receipt of SIP error response (in Automatic Dialing mode): By default, when the FXO device operates in Automatic Dialing mode, there is no method to inform the PBX if a Tel-to-IP call has failed (SIP error response - 4xx, 5xx or 6xx - is received).

  • Page 507: Dialing From Remote Extension (Phone At Fxs)

    ‘sent’ to the phone connected to the FXS device. Once the phone connected to the FXS device is off-hooked, the FXO device seizes the PBX line and the voice path is established between the phone and PBX. Version 6.8 Mediant 500L MSBR...

  • Page 508: Message Waiting Indication For Remote Extensions

    Mediant 500L MSBR There is one-to-one mapping between PBX lines and FXS device ports. Each PBX line is routed to the same phone (connected to the FXS device). The call disconnects when the phone connected to the FXS device is on-hooked.

  • Page 509: Fxs Gateway Configuration

    For the transfer to function in remote PBX extensions, Hold must be disabled at the FXS device (i.e., Enable Hold = 0) and hook-flash must be transferred from the FXS to the FXO (HookFlashOption = 4). Version 6.8 Mediant 500L MSBR...

  • Page 510: Fxo Gateway Configuration

    Mediant 500L MSBR 30.14.6 FXO Gateway Configuration The following procedure describes how to configure the FXO interface (to which the PBX is directly connected).  To configure the FXO interface: In the Trunk Group table page (see Configuring Trunk Group on page 373), assign the phone numbers 200 to 204 to the device’s FXO endpoints.

  • Page 511: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 513: Sbc Overview

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

  • Page 514: Sip Network Definitions

    Mediant 500L MSBR • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following: •...
  • Page 515 ''SBC Manipulations'' on page 575. SIP message manipulations: You can configure SIP message manipulation rules that can add, remove, and/or modify SIP headers and parameters. For more information, see ''Configuring SIP Message Manipulation'' on page 313. Version 6.8 Mediant 500L MSBR...

  • Page 516: User Registration

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

  • Page 517: Initial Registration Request Processing

     Successful de-registration responses (REGISTER with Expires header that equals zero).  Registration failure responses.  Timeout of the Expires header value (in scenarios where the user agent did not send a refresh registration request). Version 6.8 Mediant 500L MSBR...

  • Page 518: Routing Using Users Registration Database

    Mediant 500L MSBR Note: The device's Users Registration database poses the following restrictions: • The same contact cannot belong to more than one AOR. • Contacts with identical URIs and different ports and transport types are not supported (same key is created).

  • Page 519: Registration Restriction Control

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

  • Page 520: Sbc Media Handling

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

  • Page 521: Media Anchoring Without Transcoding (Transparent)

    The figure below illustrates an example of SDP handling for a call between a LAN IP Phone 10.2.2.6 and a remote IP Phone 212.179.1.13 on the WAN. Figure 31-3: SDP Offer/Answer Example Version 6.8 Mediant 500L MSBR...

  • Page 522: No Media Anchoring

    Mediant 500L MSBR 31.4.2 No Media Anchoring The No Media Anchoring (commonly referred to as Anti-Tromboning) feature enables the use of SBC signaling capabilities without handling the media (RTP/SRTP) flow between remote SIP user agents (UA). The media flow does not traverse the device. Instead, the two SIP UAs establish a direct media flow (i.e., direct call) between one another.

  • Page 523: Restricting Coders

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

  • Page 524: Prioritizing Coder List In Sdp Offer

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

  • Page 525: Multiple Rtp Media Streams Per Call Session

    If the message is received without a SIP Authorization header, the device "challenges" the client by sending a SIP 401 or 407 response. The client then resends the request with an Authorization header (containing the user name and password). Version 6.8 Mediant 500L MSBR...

  • Page 526: User Authentication Based On Radius

    Mediant 500L MSBR The device validates the SIP message according to the AuthNonceDuration, AuthChallengeMethod and AuthQOP parameters. ♦ If validation fails, the device rejects the message and sends a 403 (Forbidden) response to the client. ♦ If validation succeeds, the device verifies client identification. It checks that...

  • Page 527: Resultant Invite Traversing Device

    INVITE handling. The special prefix can be used for specific routing rules for 3xx resultant INVITEs. The prefix is removed before the resultant INVITE is sent to the destination. Figure 31-5: SIP 3xx Response Handling The process of this feature is described using an example: Version 6.8 Mediant 500L MSBR...

  • Page 528: Local Handling Of Sip 3Xx

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

  • Page 529: Interworking Sip Refer Messages

    INVITE is sent through the SBC application.  IP Group Name: The device sets the host part in the REFER message to the name configured for the IP Group in the IP Group table. Version 6.8 Mediant 500L MSBR...

  • Page 530: Interworking Sip Prack Messages

    Mediant 500L MSBR 31.7.4 Interworking SIP PRACK Messages The device supports interworking of SIP Provisional Response ACKnowledgement (PRACK) messages (18x). While some UAs may not support PRACK (RFC 3262) others may require it. The device can be configured to resolve this interoperable issue and enable sessions between such endpoints.

  • Page 531: Interworking Sip Early Media

    IP Profile parameters, 'SBC Remote Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Version 6.8 Mediant 500L MSBR...
  • Page 532 Mediant 500L MSBR Figure 31-6: SBC Early Media RTP 18x without SDP User's Manual Document #: LTRT-10466...

  • Page 533: Interworking Sip Re-Invite Messages

    SDP and only then forwards it to the destination endpoint. This interworking support is configured by the IP Profile parameter, 'SBC Remote Reinvite Support'. Version 6.8 Mediant 500L MSBR...

  • Page 534: Interworking Sip Update Messages

    Mediant 500L MSBR 31.7.8 Interworking SIP UPDATE Messages The device supports interworking of the SIP UPDATED message. This enables communication between UAs that generate UPDATE requests and those that do not support the receipt of UPDATE requests. The device does not forward UPDATE requests to IP Groups that do not support it.

  • Page 535: Call Survivability

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

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

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

  • Page 537: 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. Version 6.8 Mediant 500L MSBR...
  • Page 538 Mediant 500L MSBR Figure 31-10: Normal Operation in Call Center Application Figure 31-11: 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 287), add IP Groups for the following entities: •...

  • Page 539: Survivability Mode Display On Aastra Ip Phones

    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> 31.9 Call Forking This section describes various Call Forking features supported by the device. Version 6.8 Mediant 500L MSBR...

  • Page 540: Initiating Sip Call Forking

    Mediant 500L MSBR 31.9.1 Initiating SIP Call Forking The SBC device supports call forking of an incoming call to multiple SBC users (destinations). Call forking is supported by the device's capability of registering multiple SIP client user phone contacts (mobile and fixed-line extensions) under the same Address of Record (AOR) in its registration database.

  • Page 541: Sip Forking Initiated By Sip Proxy Server

    INVITE messages to all the specified destinations. It handles the multiple SIP dialogs until one of the calls is answered and then terminates the other SIP dialogs. For more information, see ''Configuring SBC IP-to-IP Routing Rules'' on page 564. Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 31.10 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 543: 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 6.8 Mediant 500L MSBR...
  • Page 544 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 545: Configuring General Settings

    SIP clients. This is due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements. Version 6.8 Mediant 500L MSBR...
  • Page 546 Mediant 500L MSBR 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). Thus, users subscribed to the service can receive relevant NOTIFY messages from the device and use the service.
  • Page 547 User's Manual 33. Configuring General Settings <param pname="actor" pval="attendant"/> <param pname="automaton" pval="false"/> </target> </remote> </dialog> </dialog-info> Version 6.8 Mediant 500L MSBR...
  • Page 548 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 549: Configuring Admission Control

    For example, if IP Group ID 1 needs to handle 21 calls, it's guaranteed 10, the SRD's shared pool provides another 10, and the last call is provided from the device's total call capacity support (e.g., of 200). Version 6.8 Mediant 500L MSBR...
  • Page 550 Mediant 500L MSBR 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 routing rule is located, the device rejects the SIP request with a SIP 480 "Temporarily Unavailable"...
  • Page 551 The default is 0 (i.e., unlimited rate). Notes:  You must first configure the Maximum Burst parameter (see below) before configuring the Rate parameter.  The token bucket feature is per IP Group, SRD, SIP request type, and SIP request direction. Version 6.8 Mediant 500L MSBR...
  • Page 552 Mediant 500L MSBR Parameter Description Maximum Burst Defines the maximum number of tokens (SIP dialogs) that the bucket CLI: max-burst can hold. The device only accepts a SIP dialog if a token exists in [SBCAdmissionControl_Ma the bucket. Once the SIP dialog is accepted, a token is removed xBurst] from the bucket.

  • Page 553: Configuring Coder Groups

    Figure 35-1: Allowed Audio Coders Group Page Configure an Allowed Audio Coders Group according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Version 6.8 Mediant 500L MSBR...

  • Page 554: Configuring Allowed Video Coder Groups

    Mediant 500L MSBR Table 35-1: Allowed Audio Coders Group Table Parameter Descriptions Parameter Description Allowed Coders Group ID Defines an index number for the new table record. [AllowedCodersGroupX] Coder Name Defines the audio coder. This can be a pre-defined coder or a CLI: name user-defined coder.

  • Page 555: Routing Sbc

    Proxy Set. The Proxy Set is assigned to the IP Group in the IP Group table. If classification based on Proxy Set fails (or classification based on Proxy Set is disabled), the device proceeds to classification based on the Classification table. Version 6.8 Mediant 500L MSBR...
  • Page 556 Mediant 500L MSBR Note: • For security, it is recommended to classify SIP dialogs based on Proxy Set only if the IP address of the Server-type IP Group is unknown. In other words, if the Proxy Set associated with the IP Group is configured with an FQDN. In such cases, the device classifies incoming SIP dialogs to the IP Group based on the DNS-resolved IP address.
  • Page 557 SIP response code per SIP interface. This is configured by the 'Classification Failure Response Type' parameter in the SIP Interface table (see ''Configuring SIP Interfaces'' on page 283). Version 6.8 Mediant 500L MSBR...
  • Page 558 Mediant 500L MSBR The flowchart below illustrates the classification process: Figure 36-1: Classification Process (Identifying IP Group or Rejecting Call) Note: The device saves incoming SIP REGISTER messages in its registration database. If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination.
  • Page 559 SRDs, see ''Configuring SRDs'' on page 280. [Classification_SrcSRDID] By default, no SRD is defined. Note: The SRDs are also associated with a port number as defined by the SIP Interface used by the SRD (see ''Configuring SIP Interfaces'' on page 283). Version 6.8 Mediant 500L MSBR...
  • Page 560 Mediant 500L MSBR Parameter Description Source IP Address Defines the source IP address (in dotted-decimal notation) CLI: src-ip-address of the incoming SIP dialog. [Classification_SrcAddress] The IP address can be configured using the following wildcards:  "x" wildcard: represents single digits. For example, 10.8.8.xx represents all the addresses between...

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

    This example assumes the following incoming INVITE message: INVITE sip:8000@10.33.4.226 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.226;branch=z9hG4bKVEBTDAHSUYRTEXEDEGJY From: <sip:100@10.33.4.226>;tag=YSQQKXXREVDPYPTNFMWG To: <sip:8000@10.33.4.226> Call-ID: FKPNOYRNKROIMEGBSSKS@10.33.4.226 CSeq: 1 INVITE Contact: <sip:100@10.33.4.226> 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 Version 6.8 Mediant 500L MSBR...

  • Page 562: Configuring Message Condition Rules

    Mediant 500L MSBR In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group ID Prefix Username Prefix 1111 2000 10.10.10.10 In the IP Group table, add the following IP Groups: Index Source URI Input...
  • Page 563 Defines the Condition rule of the SIP message. CLI: condition The valid value is a string. [ConditionTable_Condition] Note: User and host parts must be enclosed in single quotes. Description Defines a brief description of the Condition rule. CLI: description [ConditionTable_Description] Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 36.3 Configuring SBC IP-to-IP Routing The IP-to-IP Routing table lets you configure up to 500 SBC IP-to-IP routing rules. An IP- to-IP routing rule routes received SIP dialog messages (e.g., INVITE) to an IP destination. IP-to-IP Routing table lets you Configuration of IP-to-IP routing rules includes two areas: ...
  • Page 565 REFER messages. These rules are configured for destinations that do not support receipt of 3xx or REFER and where the device handles the requests locally (instead of forwarding the 3xx or REFER to the destination). Version 6.8 Mediant 500L MSBR...
  • Page 566 Mediant 500L MSBR  Least cost routing (LCR): If the LCR feature is enabled, the device searches the routing table for matching routing rules and then selects the one with the lowest call cost. The call cost of the routing rule is done by assigning it a Cost Group. For configuring Cost Groups, see ''Least Cost Routing'' on page 249.
  • Page 567 Source Username Prefix Defines the prefix of the user part of the incoming SIP [IP2IPRouting_SrcUsernamePrefix] dialog's source URI (usually the From URI). You can use CLI: src-user-name-prefix special notations for denoting the prefix. To denote calls Version 6.8 Mediant 500L MSBR...
  • Page 568 Mediant 500L MSBR Parameter Description without a user part in the URI, use the $ sign. For available notations, see ''Dialing Plan Notation for Routing and Manipulation'' on page 777. The default is the asterisk (*) symbol (i.e., any prefix). If this rule is not required, leave this field empty.
  • Page 569 [5] Dial Plan = The IP destination is determined by a Dial Plan index of the loaded Dial Plan file. The syntax of the Dial Plan index in the Dial Plan file is as follows: Version 6.8 Mediant 500L MSBR...
  • Page 570 Mediant 500L MSBR Parameter Description <destination / called prefix number>,0,<IP destination> Note that the second parameter "0" is ignored. An example of a configured Dial Plan (# 6) in the Dial Plan file is shown below: [ PLAN6 ] 200,0,10.33.8.52 ;...
  • Page 571 Defines the transport layer type for sending the call: [IP2IPRouting_DestTransportType]  [-1] Not Configured (default) CLI: dst-transport-type  [0] UDP  [1] TCP  [2] TLS Note: If this parameter is not configured, the transport type is determined by the SIPTransportType parameter. Version 6.8 Mediant 500L MSBR...
  • Page 572 Mediant 500L MSBR Parameter Description Alternative Route Options Determines whether this routing rule is the main routing rule [IP2IPRouting_AltRouteOptions] or an alternative routing rule (to the rule defined directly CLI: alt-route-options above it in the table).  [0] Route Row (default) = Main routing rule - the device first attempts to route the call to this route if the incoming SIP dialog's input characteristics matches this rule.

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

    IP-to-IP Routing table for the SRD or IP Group. If no alternative routing rule is located, the device automatically rejects the SIP request with a SIP 480 "Temporarily Unavailable" response. Version 6.8 Mediant 500L MSBR...
  • Page 574 Mediant 500L MSBR The following procedure describes how to configure the SBC Alternative Routing Reasons table in the Web interface. You can also configure this table using the table ini file parameter, SBCAlternativeRoutingReasons or CLI command, configure voip > sbc routing sbc-alt-routing-reasons.

  • Page 575: Sbc Manipulations

    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 CSeq: 1 INVITE Contact: <sip:7000@10.2.2.3> Version 6.8 Mediant 500L MSBR...
  • Page 576 Mediant 500L MSBR 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  Outgoing INVITE to WAN: INVITE sip: 9721000@ITSP;user=phone;x=y;z=a SIP/2.0...

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

    The following procedure describes how to configure IP-to-IP Inbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPInboundManipulation or CLI command, configure voip > sbc manipulations ip-inbound- manipulation. Version 6.8 Mediant 500L MSBR...
  • Page 578 Mediant 500L MSBR  To configure an IP-to-IP Inbound Manipulation rule: Open the IP to IP Inbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Inbound). Click Add; the following dialog box appears:...
  • Page 579 Determines whether the source or destination SIP URI user part is CLI: manipulated-uri manipulated. [IPInboundManipulation_Mani  [0] Source = (Default) Manipulation is done on the source SIP pulatedURI] URI user part.  [1] Destination = Manipulation is done on the destination SIP Version 6.8 Mediant 500L MSBR...
  • Page 580 Mediant 500L MSBR Parameter Description URI user part. Operation Rule - Action Remove From Left Defines the number of digits to remove from the left of the user CLI: remove-from-left name prefix. For example, if you enter 3 and the user name is [IPInboundManipulation_Rem "john", the new user name is "n".

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

    IPOutboundManipulation or CLI command, configure voip > sbc manipulations ip- outbound-manipulation.  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Outbound). Version 6.8 Mediant 500L MSBR...
  • Page 582 Mediant 500L MSBR Click Add; the following dialog box appears: Figure 37-3: IP to IP Outbound Manipulation Page - Add Dialog Box Configure an IP-to-IP outbound manipulation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
  • Page 583 [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect CLI: re-route-ip-group-id response (e.g., 3xx) or REFER message. This parameter is Version 6.8 Mediant 500L MSBR...
  • Page 584 Mediant 500L MSBR Parameter Description [IPOutboundManipulation_ReRout typically used for re-routing requests (e.g., INVITEs) when eIPGroupID] interworking is required for SIP 3xx redirect responses or REFER messages. The default is -1 (i.e., not configured). Notes:  This parameter functions together with the 'Call Trigger' parameter (see below).
  • Page 585 The device identifies an incoming user as restricted if one of the following exists:  From header user is anonymous.  P-Asserted-Identity and Privacy headers contain the value "id". Note: All restriction logic is performed after the user number has been manipulated. Version 6.8 Mediant 500L MSBR...
  • Page 586 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 587: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 589: Crp Overview

    Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
  • Page 590 Mediant 500L MSBR Survivability Quality of Experience/Service Security registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...

  • Page 591: Crp Configuration

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

  • Page 592: Configuring Call Survivability Mode

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

  • Page 593: Pre-Configured Ip Groups

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

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

    Mediant 500L MSBR 39.4 Pre-Configured IP-to-IP Routing Rules For the CRP application, the IP-to-IP Routing table is pre-configured with IP-to-IP routing rules. These rules depend on the configured Call Survivability mode, as described in ''Configuring Call Survivability Mode'' on page 592.

  • Page 595: Emergency Mode

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

  • Page 596: Configuring Pstn Fallback

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

  • Page 597: Data-Router Configuration

    Part VIII Data-Router Configuration...

  • Page 599: Introduction

    Web-based management for data-router functionality of the MSBR series products is not supported. Instead, CLI is used to configure this functionality. However, AudioCodes recommends using CLI scripting to configure all other functionality as well (i.e., VoIP and System) through the CLI.
  • Page 600 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 601: Maintenance

    Part IX Maintenance...

  • Page 603: Basic Maintenance

    ''Displaying Navigation Tree in Basic and Full View'' on page 51). • Upon reboot, the device restores the settings from its configuration file. However, if reboot attempts fail three times consecutively, the device resets the configuration file by restoring factory defaults before attempting to reboot. Version 6.8 Mediant 500L MSBR...
  • Page 604 Mediant 500L MSBR  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 603). 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 605: 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 606: Saving Configuration

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

  • Page 607: Disconnecting Active Calls

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

  • Page 609: Resetting Channels

    Open the Home page. Click the required FXS or FXO port icon; a shortcut menu appears. From the shortcut menu, choose Reset Channel; the channel is changed to inactive and the port icon is displayed in gray. Version 6.8 Mediant 500L MSBR...

  • Page 610: Restarting A B-Channel

    Mediant 500L MSBR 43.2 Restarting a B-Channel You can restart a specific B-channel belonging to an ISDN or CAS trunk, using the SNMP MIB variable, acTrunkISDNCommonRestartBChannel or the EMS management tool (refer to the EMS User's Manual). This may be useful, for example, for troubleshooting specific voice channels.

  • Page 611: Disabling Analog Ports

    By default, all the analog ports are enabled. To disable an analog port, use the following CLI command: (config-voip)# interface fxs-fxo (fxs-fxo)# analog-port-enable <module>/<port> [on|off] For example, to disable port 2 on module 1: (fxs-fxo)# analog-port-enable 1/2 off Version 6.8 Mediant 500L MSBR...
  • Page 612 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 613: Locking And Unlocking Trunk Groups

    If the device is reset, a locked Trunk Group remains locked. If the device is reset while graceful lock is in progress, the Trunk Group is forced to lock immediately after the device finishes its reset. Version 6.8 Mediant 500L MSBR...
  • Page 614 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 615: Software Upgrade

    The Auxiliary files listed in the ini file are then automatically loaded through TFTP during device startup. If the ini file does not contain a specific auxiliary file type, the device uses the last auxiliary file of that type that was stored on its non-volatile memory. Version 6.8 Mediant 500L MSBR...

  • Page 616: 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 617 ♦ [46] Beep Tone • Tone Modulation Type: Amplitude Modulated (1) or regular (0) • Tone Form: The tone's format can be one of the following: ♦ Continuous (1) ♦ Cadence (2) ♦ Burst (3) Version 6.8 Mediant 500L MSBR...
  • Page 618 Mediant 500L MSBR • Low Freq [Hz]: Frequency (in Hz) of the lower tone component in case of dual frequency tone, or the frequency of the tone in case of single tone. This is not relevant to AM tones. •...

  • Page 619: Distinctive Ringing

    Fourth (Burst) Ring On Time [10 msec]: 'Ring Off' period (in 10 msec units) for the fourth cadence on-off cycle. • Fourth (Burst) Ring Off Time [10 msec]: 'Ring Off' period (in 10 msec units) for the fourth cadence on-off cycle. Version 6.8 Mediant 500L MSBR...
  • Page 620 Mediant 500L MSBR Note: In SIP, the Distinctive Ringing pattern is selected according to the Alert-Info header in the INVITE message. For example: Alert-Info:<Bellcore-dr2>, or Alert-Info:<http://…/Bellcore-dr2> 'dr2' defines ringing pattern #2. If the Alert-Info header is missing, the default ringing tone (0) is played.

  • Page 621: Prerecorded Tones File

    PRT file on the device's flash memory. 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 622: Dial Plan File

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Load the converted file to the device, as described in ''Loading Auxiliary Files'' on page 615.
  • Page 623 ; Operator services starting with a star: *41, *42, *43. ; No additional digits are expected. *4[1-3],0 The following procedure provides a summary on how to create a Dial Plan file and select the required Dial Plan index. Version 6.8 Mediant 500L MSBR...

  • Page 624: Dial Plan Prefix Tags For Routing

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplans.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Install the converted file on the device, as described in ''Loading Auxiliary Files'' on page 615.
  • Page 625 Definitions > General Parameters), specify the Dial Plan indices (e.g., 1) where you configured the prefix tags: • Prefix tags for called number prefixes: 'IP-to-Tel Tagging Destination Dial Plan Index' parameter • Prefix tags for calling number prefixes: 'IP-to-Tel Tagging Source Dial Plan Index' parameter Version 6.8 Mediant 500L MSBR...
  • Page 626 Mediant 500L MSBR Open the Inbound IP Routing table (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing). From the 'IP-to-Tel Routing Mode' drop-down list, select Route calls before manipulation so that the device performs the routing processing before manipulation.
  • Page 627 (e.g., set 'Source IP Group ID' to "1"). From the 'Manipulated URI' drop-down list, select Source to add the tag to the calling URI user part, or Destination to add the tag to the called URI user part. Version 6.8 Mediant 500L MSBR...

  • Page 628: Obtaining Ip Destination From Dial Plan File

    Mediant 500L MSBR Click the Action tab, and then enter the Dial Plan index for which you configured your prefix tag, in the 'Prefix to Add' or 'Suffix to Add' fields, using the following syntax: $DialPlan<x>, where x is the Dial Plan index (0 to 7). For example, if the called number is 4252000555, the device manipulates it to LOCL4252000555.

  • Page 629: 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 615), AcBootP utility, or using the Auto-update mechanism from an external HTTP server. Version 6.8 Mediant 500L MSBR...

  • Page 630: User Information File

    Mediant 500L MSBR 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 631 If a User Info file is loaded to the device (as described in ''Configuring GW User Info Table in Loadable Text File'' on page 633), all previously configured entries are removed from the table in the Web interface and replaced with the entries from the loaded User Info file. Version 6.8 Mediant 500L MSBR...
  • Page 632 Mediant 500L MSBR  To configure the GW User Info table in the Web interface: Open the GW User Info Table page (Configuration tab > VoIP menu > SIP Definitions > User Information > GW User Info Table). Click Add: the following dialog box appears: Figure 46-2: GW User Info Table in Web Interface Configure the GW User Info table parameters according to the table below.
  • Page 633 To add mapping rules to the User Info file, use the following syntax: [ GW ] FORMAT PBXExtensionNum,GlobalPhoneNum,DisplayName,UserName,Password Where:  [ GW ] indicates that this part of the file is the GW User Info table Version 6.8 Mediant 500L MSBR...

  • Page 634: User Information File For Sbc User Database

    Mediant 500L MSBR  PBXExtensionNum is the PBX extension number (up to 10 characters)  GlobalPhoneNum is the "global" phone number (up to 20 characters) for the IP side  DisplayName is the Caller ID (string of up to 30 characters) of the PBX extension ...
  • Page 635 The valid value is a string of up to 20 characters. IP Group ID Defines the IP Group ID to which the user belongs and is used as [SBCUserInfoTable_IPGroupID] the Request-URI source host part for the AOR in the database. Version 6.8 Mediant 500L MSBR...
  • Page 636 Mediant 500L MSBR Parameter Description Status (Read-only field) Displays the status of the user - "Registered" or [SBCUserInfoTable_Status] "Not Registered". 46.1.5.3.2 Configuring SBC User Info Table in CLI The SBC User Info table can be configured in the CLI using the following commands: ...
  • Page 637 Make sure that there are no spaces between the values. • To modify the SBC User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Version 6.8 Mediant 500L MSBR...

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

    CLI - see Installing Software License Key using CLI on page 640  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non- volatile flash memory and overwrites the previously installed Software License Key.

  • Page 640: Installing Software License Key Using Cli

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

  • Page 641: Software Upgrade Wizard

    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 642 Mediant 500L MSBR  To load files using the Software Upgrade Wizard: Make sure that you have installed a new Software License Key (see Installing the Software License Key on page 638) that is compatible with the software version to be installed.
  • Page 643 If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file running on the device) and thereby, overwrite values previously configured for these parameters. Version 6.8 Mediant 500L MSBR...
  • Page 644 Mediant 500L MSBR • Retain the existing configuration (default): Select the 'Use existing configuration' check box to use the current configuration (and do not select an ini file). • Restore configuration to factory defaults: Clear the 'Use existing configuration' check box (and do not select an ini file).
  • Page 645 Click End Process to close the wizard; the Web Login dialog box appears. Enter your login username and password, and then click Login; a message box appears informing you of the new .cmp file version. Click OK; the Web interface becomes active, reflecting the upgraded device. Version 6.8 Mediant 500L MSBR...

  • Page 646: Backing Up And Loading Configuration File

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

  • Page 647: Automatic Provisioning

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

  • Page 648: Http-Based Provisioning

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

  • Page 649: Ftp-Based Provisioning

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

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

    Mediant 500L MSBR 47.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 651: File Location For Automatic Update

    For configuration files (Startup Script, and CLI Script), the file name in the URL can automatically contain the device's MAC address for enabling the device to download a file unique to the device. For more information, see ''MAC Address Automatically Inserted in Configuration File Name'' on page 657. Version 6.8 Mediant 500L MSBR...

  • Page 652: Access Authentication With Http Server

    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 653: Querying Provisioning Server For Updated Files

    INIFileVersion or CLI command, configuration-version The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld-<NAME>;<VER>(<MAC>), the device sends the following User-Agent header: User-Agent: MyWorld-Mediant;6.8.200.001(00908F1DD0D3)
  • Page 654 Mediant 500L MSBR Note: If you configure the AupdHttpUserAgent parameter with the <CONF> variable tag, you must reset the device with a burn-to-flash for your settings to take effect. If the provisioning server has relevant files available for the device, the following occurs, depending on file type and configuration: •...
  • Page 655 HTTPS with mutual authentication for secure transfer of the SSL Private Key. If the device receives an HTTP 301/302/303 redirect response from the provisioning server, it establishes a connection with the new server at the redirect URL and re- sends the HTTP Get request. Version 6.8 Mediant 500L MSBR...

  • Page 656: File Download Sequence

    Mediant 500L MSBR 47.2.6 File Download Sequence Whenever the Automatic Update feature is triggered (see ''Triggers for Automatic Update'' on page 652), the device attempts to download each file from the configured URLs, in the following order: CLI Script file Startup Script file Periodic software file (.cmp) download...

  • Page 657: Cyclic Redundancy Check On Downloaded Configuration Files

    The device automatically replaces the string with its hardware MAC address, resulting in a file name request that contains device's address, example, startup_00908F033512.txt. Therefore, you can configure all the devices with the same URL and file name. Version 6.8 Mediant 500L MSBR...

  • Page 658: Automatic Update Configuration Examples

    Mediant 500L MSBR 47.2.9 Automatic Update Configuration Examples This section provides a few examples on configuring the Automatic Update feature. 47.2.9.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 659: Automatic Update From Remote 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' ♦ CLI: Version 6.8 Mediant 500L MSBR...
  • Page 660 Mediant 500L MSBR # configure system (config-system)# automatic update (automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' (automatic-update)# startup-script https://company.com/files/startup_script.txt Configure the device with the IP address of the DNS server for resolving the domain names of the FTPS and HTTP servers: [ InterfaceTable ]...

  • Page 661: Automatic Update For Mass Deployment

    .cmp files to the HTTP-based provisioning server. Configure each device with the following: URL of the master configuration file: ♦ ini File: IniFileURL = 'http://www.company.com/master_configuration.ini' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# cli-script https://company.com/files/master_startup.txt Version 6.8 Mediant 500L MSBR...
  • Page 662 Mediant 500L MSBR Configure the device with the IP address of the DNS server for resolving the domain name (e.g., http://www.company.com) that is used in the URL for the provisioning server. This is done in the Interface table: ♦ ini File:...

  • Page 663: Zero Configuration

    AudioCodes sales representative on how to order the feature. The procedure typically requires you to return your device as a return merchandise authorization (RMA) so that AudioCodes can install the Software License Key file and Zero Configuration TLS Certificate on your device.
  • Page 664 This file can be the CLI Script file or the CLI Startup Script file. The type of file depends on your implementation of Zero Configuration and automatic provisioning, specific to your deployment needs. You can contact your AudioCodes sales representative for an explanation on various design concepts for implementing Zero Configuration.

  • Page 665: Configuring Zero Configuration

    The above configuration may be done through a third-party, Web-based management interface or SOAP/XML interface of your choosing, which may be integrated with the Service Provider’s provisioning system. For more information, contact AudioCodes support. Create a CLI-based configuration file containing settings relating only to the Automatic Update feature (see ''Automatic Update Configuration Examples'' on page 658), and place it on your provisioning server (to where the Redirect server redirects the device).
  • Page 666 Mediant 500L MSBR Power down and then power up the device to trigger Zero Configuration. Cable the device to the WAN network. User's Manual Document #: LTRT-10466...

  • Page 667: Using Zero Configuration With Automatic Update

    1.d), the file is not downloaded during this initial Automatic Update process. The Startup Script is downloaded only when the Automatic Update process is next triggered and the file on the provisioning server has been subsequently modified (determined by the HTTP If-Modified-Since header). Version 6.8 Mediant 500L MSBR...

  • Page 668: Automatic Provisioning Using Usb Flash Drive

    Mediant 500L MSBR Notes: • If the Automatic Update process succeeds, the device repeats the Zero Configuration process only if you reset the device to factory defaults. If the Automatic Update process fails, the device repeats the Zero Configuration process at the next device reset or power up.
  • Page 669 47. Automatic Provisioning exit reload now The CLI output of the above example which the device sends to the USB flash drive in the ac_output file is shown below: Welcome to AudioCodes CLI Username: Admin Password: MSBR> en Password: MSBR# configure data MSBR(config-data)# interface GigabitEthernet 0/0 MSBR(conf-if-GE 0/0)# ip address 100.0.10.10 255.255.0.0...
  • Page 670 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 671: Restoring Factory Defaults

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

  • Page 672: Restoring Defaults Using Hardware Reset Button

    Mediant 500L MSBR 48.2 Restoring Defaults using Hardware Reset Button The device's hardware reset pinhole button can be used to reset the device to default settings.  To restore default settings using the hardware reset pinhole button:  With a paper clip or any other similar pointed object, press and hold down the reset pinhole button, located on the front panel for at least 12 seconds (but no more than 25 seconds).

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

    # write-and-backup to <URL path with file name> For example: # write-and-backup to tftp://192.168.0.3/config-device1.txt  Creating a Configuration file and saving it on a USB stick plugged into the device: # write-and-backup to usb:///<file name> For example: # write-and-backup to usb:///config-device1.txt Version 6.8 Mediant 500L MSBR...
  • Page 674 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 675: Usb Storage Capabilities

    # copy voice-configuration from usb:///<ini configuration file name>  To save the current configuration to the USB: # copy voice-configuration to usb:///<ini configuration file name> Note: Only a single USB storage (formatted to FAT/FAT32) operation is supported at any given time. Version 6.8 Mediant 500L MSBR...
  • Page 676 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 677: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 679: System Status

    To delete a loaded file:  Click the Delete button corresponding to the file that you want to delete. Deleting a file takes effect only after device reset (see ''Resetting the Device'' on page 603). Version 6.8 Mediant 500L MSBR...

  • Page 680: Viewing Ethernet Port Information

    Mediant 500L MSBR 51.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information about the Ethernet Port connections.  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu >...

  • Page 681: Carrier-Grade Alarms

    For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised Version 6.8 Mediant 500L MSBR...
  • Page 682 Mediant 500L MSBR  Description: brief explanation of the alarm  Date: date and time that the alarm was generated To view the next 20 alarms (if exist), click the Go to page button.  To delete all the alarms in the table: Click the Delete History Table button;...

  • Page 683: Performance Monitoring

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

  • Page 684: Configuring Packetsmart For Network Monitoring

    The PacketSmart feature is a license-dependent feature and is available only if it is included in the Software License Key installed on the device. For ordering the feature, please contact your AudioCodes sales representative. • Before configuring the PacketSmart agent, configure the following: √...

  • Page 685: Viewing Trunk Utilization

    Open the Trunk Utilization page (Status & Diagnostics tab > Performance Monitoring menu > Trunk Utilization). Figure 53-3: Trunk Utilization Page From the 'Trunk' drop-down list, select the trunk for which you want to view active channels. For more graph functionality, see the following table: Version 6.8 Mediant 500L MSBR...
  • Page 686 Mediant 500L MSBR Table 53-1: Additional Graph Functionality for Trunk Utilization Button Description Add button Displays additional trunks in the graph. Up to five trunks can be displayed simultaneously in the graph. To view another trunk, click this button and then from the new 'Trunk' drop-down list, select the required trunk.

  • Page 687: Viewing Quality Of Experience

    Figure 53-4: Quality Of Experience Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view QoE for an SRD or IP Group. From the 'Index' drop-down list, select the SRD or IP Group index. Version 6.8 Mediant 500L MSBR...
  • Page 688 Mediant 500L MSBR From the 'Dir' drop-down list, select the call direction: • In - incoming calls • Out - outgoing calls • Both - incoming and outgoing calls From the 'Type' drop-down list, select the SIP message type: •...

  • Page 689: Viewing Average Call Duration

    As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 500L MSBR...
  • Page 690 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 691: Voip Status

    Table 54-1: Description of Color-Coded Icons for Trunk Status Trunk Icon Color Label Gray Disabled Green Active - OK RAI Alarm Yellow LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Purple Lower Layer Down (DS3 physical layer is disabled) Version 6.8 Mediant 500L MSBR...
  • Page 692 Mediant 500L MSBR The status of the channels is depicted by color-coded icons, as described in the table below: Table 54-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls...

  • Page 693: Viewing Analog Port Information

    Interface table (see ''Configuring IP Network Interfaces'' on page 138).  To view active IP network interfaces:  Open the IP Interface Status page (Status & Diagnostics tab > VoIP Status menu > IP Interface Status). Version 6.8 Mediant 500L MSBR...

  • Page 694: Viewing Ethernet Device Status

    Mediant 500L MSBR 54.4 Viewing Ethernet Device Status The Ethernet Device Status page displays the configured Ethernet Devices that have been successfully applied to the device. For configuring Ethernet Devices, see ''Configuring Underlying Ethernet Devices'' on page 137.  To view the configured and applied Ethernet Devices: ...

  • Page 695: Viewing Performance Statistics

    CDR history for a specific SIP session ID: # show voip calls history <session ID>  To view CDR history:  Open the CDR History page (Status & Diagnostics tab > VoIP Status menu > CDR History). Version 6.8 Mediant 500L MSBR...
  • Page 696 Mediant 500L MSBR Figure 54-7: CDR History Table Table 54-3: CDR History Table Field Description Call End Time Displays the time at which the call ended. The time is displayed in the format, hh:mm:ss, where hh is the hour, mm the minutes and ss the seconds (e.g., 15:06:36).

  • Page 697: Viewing Call Counters

     GWAPP_REASON_NOT_RELEVANT (0)  GWAPP_NORMAL_CALL_CLEAR (16)  GWAPP_NORMAL_UNSPECIFIED (31) And the internal reasons:  RELEASE_BECAUSE_UNKNOWN_REASON  RELEASE_BECAUSE_REMOTE_CANCEL_CALL  RELEASE_BECAUSE_MANUAL_DISC  RELEASE_BECAUSE_SILENCE_DISC  RELEASE_BECAUSE_DISCONNECT_CODE Note: When the duration of the call is zero, the release reason Version 6.8 Mediant 500L MSBR...
  • Page 698 Mediant 500L MSBR Counter Description GWAPP_NORMAL_CALL_CLEAR increments the 'Number of Failed Calls due to No Answer' counter. The rest of the release reasons increment the 'Number of Failed Calls due to Other Failures' counter. Percentage of The percentage of established calls from attempted calls.

  • Page 699: Viewing Registered Users

    SBC users: # show voip register db sbc list • SBC contacts of a specified AOR: # show voip register db sbc user <Address Of Record> • SAS users: # show voip register db sas list Version 6.8 Mediant 500L MSBR...

  • Page 700: Viewing Registration Status

    Mediant 500L MSBR 54.10 Viewing Registration Status The Registration Status page displays the registration status of the device's endpoints (such as FXS, FXO and BRI) and SIP Accounts, which are configured in the Accounts table (see ''Configuring Registration Accounts'' on page 305).

  • Page 701: Viewing Call Routing Status

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

  • Page 702: Viewing Ip Connectivity

    Mediant 500L MSBR 54.12 Viewing IP Connectivity The IP Connectivity page displays on-line, read-only network diagnostic connectivity information on all destination IP addresses configured in the Outbound IP Routing table (see ''Configuring Outbound IP Routing'' on page 405). 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 703 Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).  This parameter is reset if no QoS information is received for 2 minutes. DNS Status DNS status can be one of the following:  DNS Disable  DNS Resolved  DNS Unresolved Version 6.8 Mediant 500L MSBR...
  • Page 704 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 705: Reporting Information To External Party

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

  • Page 709: Generating Call Detail Records

    For CDR in RADIUS format, see ''Configuring RADIUS Accounting'' on page 721. Note: You can view the latest CDRs, which are stored on the device's memory, in the CDR History table. For more information, see 'Viewing CDR History' on page 695. Version 6.8 Mediant 500L MSBR...

  • Page 710: Configuring Cdr Reporting

    Mediant 500L MSBR 55.2.1 Configuring CDR Reporting The following procedure describes how to configure CDR reporting.  To configure CDR reporting: Enable the Syslog feature for sending log messages generated by the device to a collecting log message server. For more information, see ''Enabling Syslog'' on page 737.

  • Page 711: Gwapp_Normal_Call_Clear

    String of up to 40 characters TrmReasonCategory Termination reason category: String of up to 17 characters Calls with duration 0 (i.e., not connected):  NO_ANSWER:  "GWAPP_NORMAL_CALL_CLEA R"  "GWAPP_NO_USER_RESPONDI NG"  "GWAPP_NO_ANSWER_FROM_ USER_ALERTED"  BUSY: Version 6.8 Mediant 500L MSBR...
  • Page 712 Mediant 500L MSBR CDR Field Name Description Format  " GWAPP_USER_BUSY"  NO_RESOURCES:  "GWAPP_RESOUUCE_UNAVAIL ABLE_UNSPECIFIED"  "RELEASE_BECAUSE_NO_CON FERENCE_RESOURCES_LEFT"  "RESOURCE_BECAUSE_NO_TR ANSCODING_RESOURCES_LEF T"  "RELEASE_BECAUSE_GW_LOC KED"  NO_MATCH:  "RELEASE_BECAUSE_UNMATC HED_CAPABILITIES"  FORWARDED:  "RELEASE_BECAUSE_FORWAR D"  GENERAL_FAILED: Any other reason Calls with duration: ...

  • Page 713: Cdr Fields For Sbc Media

    CDR has a unique call ID corresponding to the signaling CDR. Table 55-3: CDR Fields for SBC Media CDR Field Name Description MediaReportType Report type (media start, update, or end) SIPCallId Unique call ID Channel CID MediaType Media type (audio, video, or text) Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR CDR Field Name Description Coder Coder name PacketInterval Coder packet interval LocalRtpIp Local RTP IP address LocalRtpPort Local RTP port RemoteRtpIp Remote RTP IP address RemoteRtpPort Remote RTP port InPackets Number of received packets OutPackets Number of sent packets...
  • Page 715 Note: This field is applicable only to the Gateway application. Destination phone number plan Note: This field is applicable only to the Gateway application. DstPhoneNum Destination phone number DstNumBeforeMap Destination number before manipulation Durat Call duration Version 6.8 Mediant 500L MSBR...
  • Page 716 Mediant 500L MSBR Field Name Description Coder Selected coder Intrv Packet interval RtpIp RTP IP address Port Remote RTP port TrmSd Initiator of call release (IP, Tel, or Unknown) TrmReason SIP call termination reason (see ''Release Reasons in CDR for Gateway...
  • Page 717 R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable. LocalMosCQ Local MOS for conversation quality RemoteMosCQ Remote MOS for conversation quality Version 6.8 Mediant 500L MSBR...

  • Page 718: Release Reasons In Cdr For Gateway Application

    Mediant 500L MSBR Field Name Description SigSourcePort SIP source port SigDestPort SIP destination port MediaType Media type - audio, video, or text SIPTrmReason SIP call termination reason (BYE, CANCEL, or SIP error codes, e.g., 404) SipTermDesc Description of SIP termination reason: ...

  • Page 719: Release_Because_Silence_Disc

     "GWAPP_NORMAL_UNSPECIFIED"  "GWAPP_CIRCUIT_CONGESTION"  "GWAPP_USER_CONGESTION"  "GWAPP_NO_CIRCUIT_AVAILABLE"  "GWAPP_NETWORK_OUT_OF_ORDER"  "GWAPP_NETWORK_TEMPORARY_FAILURE"  "GWAPP_NETWORK_CONGESTION"  "GWAPP_ACCESS_INFORMATION_DISCARDED"  "GWAPP_REQUESTED_CIRCUIT_NOT_AVAILABLE"  "GWAPP_RESOURCE_UNAVAILABLE_UNSPECIFIED"  "GWAPP_PERM_FR_MODE_CONN_OUT_OF_S"  "GWAPP_PERM_FR_MODE_CONN_OPERATIONAL"  "GWAPP_PRECEDENCE_CALL_BLOCKED" • "RELEASE_BECAUSE_PREEMPTION_ANALOG_CIRCUIT_RESERVED_FOR_ REUSE" • "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED" Version 6.8 Mediant 500L MSBR...
  • Page 720 Mediant 500L MSBR  "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"  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION" ...

  • Page 721: Configuring Radius Accounting

    Stop long nas-ip- IP address of the Numeric 192.168.14.43 Start address requesting device Stop service-type Type of service Numeric 1: login Start requested Stop h323- SIP call identifier Up to Start incoming- conf-id octets Stop Version 6.8 Mediant 500L MSBR...
  • Page 722 Mediant 500L MSBR Vendor Specific Attribute Attribute Value Attribute Purpose Example Number Name Format (VSA) h323- IP address of the Numeric - Stop remote- remote gateway address h323-conf-id H.323/SIP call Up to Start identifier octets Stop h323-setup- Setup time in NTP...
  • Page 723 Calling Card application. acct-delay- No. of seconds tried Numeric 5 Start time in sending a particular record Stop acct-input- Number of octets Numeric - Stop octets received for that call duration (Gateway call) Version 6.8 Mediant 500L MSBR...
  • Page 724 Mediant 500L MSBR Vendor Specific Attribute Attribute Value Attribute Purpose Example Number Name Format (VSA) acct-output- Number of octets Numeric - Stop octets sent for that call duration (Gateway call) acct- A unique accounting String 34832 Start session-id identifier - match start &...

  • Page 725: Event Notification Using X-Detect Header

    The IO* SIT tone is detected as VC The device can map these SIT tones to a Q.850 cause and then map them to SIP 5xx/4xx responses, using parameters SITQ850Cause, SITQ850CauseForNC, SITQ850CauseForIC, SITQ850CauseForVC, and SITQ850CauseForRO. Version 6.8 Mediant 500L MSBR...
  • Page 726 Mediant 500L MSBR Table 55-7: Special Information Tones (SITs) Reported by the device Special Description First Tone Second Tone Third Tone Information Frequency Frequency Frequency Tones (SITs) Duration Duration Duration Name (Hz) (ms) (Hz) (ms) (Hz) (ms) No circuit found 985.2...
  • Page 727 X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Response=CPT,FAX Content-Type: Application/X-Detect Content-Length: xxx Type = CPT Subtype = SIT Version 6.8 Mediant 500L MSBR...

  • Page 728: Querying Device Channel Resources Using Sip Options

    Mediant 500L MSBR 55.5 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 729: Obtaining Status And Performance Using A Usb Flash Drive

    Obtaining Status and Performance using a USB Flash Drive You can use a USB flash drive to obtain status and performance information of the device. For more information, see ''Automatic Provisioning using USB Flash Drive'' on page 668. Version 6.8 Mediant 500L MSBR...
  • Page 730 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 731: Diagnostics

    Part XI Diagnostics...

  • Page 733: Syslog And Debug Recordings

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

  • Page 734: Event Representation In Syslog Messages

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

  • Page 736: Unique Device Identification In Syslog Messages

    11/24 08:14:09.311 : 10.3.2.100 : WARNING : DATA: Failed to set device eth0 netmask: Cannot assign requested address 57.1.3 Identifying AudioCodes Syslog Messages using Facility Levels The device’s Syslog messages can easily be identified and distinguished from Syslog messages from other equipment, by setting its Facility level. The Facility levels of the device's Syslog messages are numerically coded with decimal values.

  • Page 737: Snmp Alarms In Syslog Messages

    For a detailed description on the Syslog parameters, see ''Syslog, CDR and Debug Parameters'' on page 807. • To configure the network interface (WAN or VoIP LAN OAMP) from where the device sends Syslog messages to a Syslog server, use the OampDefaultNetworkSource parameter. Version 6.8 Mediant 500L MSBR...
  • Page 738 Mediant 500L MSBR  To enable Syslog: Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Figure 57-1: Syslog Settings Page Enable the Syslog feature by setting 'Enable Syslog' to Enable. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port' parameters.

  • Page 739: Configuring Web Operations To Report To Syslog

    Under the Activity Types to Report via Activity Log Messages group, select the Web actions to report to the Syslog server. For more information, see ''Syslog, CDR and Debug Parameters'' on page 807. Figure 57-2: Web Activities to Report to Syslog Click Submit. Version 6.8 Mediant 500L MSBR...

  • Page 740: Configuring Debug Recording

    Mediant 500L MSBR 57.4 Configuring Debug Recording The device enables you to activate debug recording and send debug recording packets to a defined capturing server. When the debug recording is activated, the device duplicates all messages that are sent and/or received by it and then sends them to an external IP address.

  • Page 741: Filtering Syslog Messages And Debug Recordings

    Note: Each table row must be configured with a unique index. Filter Type Defines the filter type criteria. CLI: filter-type  [1] Any (default) [LoggingFilters_FilterType]  [2] Trunk ID = Filters according to a specified Trunk ID (applicable only to the Gateway application) Version 6.8 Mediant 500L MSBR...
  • Page 742 Mediant 500L MSBR Parameter Description  [3] Trunk Group ID = Filters according to a specified Trunk Group ID (applicable only to the Gateway application)  [4] Trunk & B-channel = Filters according to a specified Trunk and B-channel (applicable only to the Gateway application) ...

  • Page 743: Filtering Ip Network Traces

    For conditions requiring the "or" / "||" expression, add multiple table rows. For example, the 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: Version 6.8 Mediant 500L MSBR...
  • Page 744 Mediant 500L MSBR 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 Note: If the 'Value' field is not defined, the device records all IP traffic types. User's Manual Document #: LTRT-10466...

  • Page 745: Viewing Syslog Messages

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

  • Page 746: Collecting Debug Recording Messages

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

  • Page 747: Debug Capturing Voip And Data-Router Traffic

    TFTP or FTP server: # debug capture voip physical stop <TFTP/FTP server IP address> If no IP address is defined, the capture is saved on the device for later retrieval. Version 6.8 Mediant 500L MSBR...

  • Page 748: Configuring Termination Of Debug Capture Upon Event

    Mediant 500L MSBR 57.10 Configuring Termination of Debug Capture Upon Event You can configure the device to stop a debug-traffic capture on the device's physical network interfaces upon a user-defined event. This event can be a Syslog message or an interface state-change.

  • Page 749: Self-Testing

    Startup Test (automatic): This hardware test has minor impact in real-time. While this test is executed, the regular operation of the device is disabled. If an error is detected, an error message is sent to the Syslog. Version 6.8 Mediant 500L MSBR...
  • Page 750 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

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

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

  • Page 753: Re-Initializing Device With "Purified" Configuration

    When this command is run, the device 1) creates a CLI script file of the current configuration, 2) restores to factory defaults, 3) undergoes a reset, 4) applies (loads) the script file, and then 5) resets again (if required) for configuration settings to take effect. Version 6.8 Mediant 500L MSBR...
  • Page 754 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 755: Analog Line Testing

    Line polarity (0 = Positive; 1 = Negative)  Message Waiting Indication (0 = Off; 1 = On) Note: Use the Analog Line testing mechanism only for monitoring and never when there are calls in progress. Version 6.8 Mediant 500L MSBR...

  • Page 756: Fxs Line Testing

    Mediant 500L MSBR 61.2 FXS Line Testing The device can test the telephone lines that are connected to its FXS ports, using the SNMP acAnalogFxsLineTestTable table. These tests provide various line measurements. In addition to these tests, a keep-alive test is also done every 100 msec on each of the analog ports to detect communication problems with the analog equipment and overheating of the FXS ports.

  • Page 757: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. However, this number can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call or CLI command, configure system >...
  • Page 758 Mediant 500L MSBR  To configure a test call: Open the Test Call Table page (Configuration tab > System menu > Test Call > Test Call Table). Click Add; the following dialog box appears: Figure 62-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
  • Page 759 'Destination Address' or 'IP [Test_Call_AutoRegister] Group ID' parameter settings (see above).  [0] Disable (default)  [1] Enable Username Defines the authentication username. CLI: user-name By default, no username is defined. Version 6.8 Mediant 500L MSBR...
  • Page 760 Mediant 500L MSBR Parameter Description [Test_Call_UserName] Password Defines the authentication password. CLI: password By default, no password is defined. [Test_Call_Password] Test Settings Tab Call Party Defines whether the test endpoint is the initiator or receiving side CLI: call-party of the test call.

  • Page 761: Starting And Stopping Test Calls

    "Done": test call has been successfully completed (or was prematurely stopped by clicking the Drop Call command) A more detailed description of this field is displayed below the table when you click the Show/Hide button (see ''Viewing Test Call Statistics'' on page 762). Version 6.8 Mediant 500L MSBR...

  • Page 762: Viewing Test Call Statistics

    Mediant 500L MSBR 62.3 Viewing Test Call Statistics In addition to viewing a brief status description of the test call in the 'Test Status' field (as described in ''Starting, Stopping and Restarting Test Calls'' on page 761), you can also view a more detailed status description which includes test call statistics.

  • Page 763: Configuring Dtmf Tones For Test Calls

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

  • Page 764: Configuring Basic Test Call

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

  • Page 765: Configuring Sbc Test Call With External Proxy

    As the 'Test Call ID' parameter is set to "101", the device identifies the incoming call as a test call and sends it directly to the simulated test endpoint "101".  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Version 6.8 Mediant 500L MSBR...

  • Page 766: Test Call Configuration Examples

    Mediant 500L MSBR Parameters'' on page 806): Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 62-7: Test Call Settings Page In the 'Test Call ID' field, enter a prefix number for the simulated test endpoint on the device.
  • Page 767 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 768 Mediant 500L MSBR  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and pas,sword) process of a simulated test endpoint on the device with an external proxy/registrar server. This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another.

  • Page 769: Data-Router Debugging

    # debug ethernet loopback interface <interface name / type> For example: # debug ethernet loopback interface GigabitEthernet 0/0 The no debug command disables the loopback test. Note: All communication through the loopback WAN interface stops when this test is enabled. Version 6.8 Mediant 500L MSBR...

  • Page 770: Performing A Traceroute

    Mediant 500L MSBR 63.2 Performing a Traceroute You can use traceroute as a diagnostic tool for displaying the route (path) and measuring transit delays of packets across an IP network. The traceroute sends three requests to each hop on the way to the destination. Traceroute is done using the following CLI command: # traceroute ipv6 <X:X::X:X>...

  • Page 771: Pinging A Remote Host Or Ip Address

    # ping ipv6 <IPv6 address or host name> source data [vrf | source-address interface| interface] [size <max. IP packet size>] [repeat <1-300>] For a complete description of the ping command, refer to the CLI Reference Guide. Note: IPv6 ping is currently only supported on Ethernet and Fiber interfaces. Version 6.8 Mediant 500L MSBR...
  • Page 772 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 773: Troubleshooting Using A Usb Flash Drive

    65. Troubleshooting using a USB Flash Drive Troubleshooting using a USB Flash Drive You can use a USB flash drive for quick-and-easy troubleshooting of the device. For more information, see ''Automatic Provisioning using USB Flash Drive'' on page 668. Version 6.8 Mediant 500L MSBR...
  • Page 774 Mediant 500L MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10466...

  • Page 775: Appendix

    Part XII Appendix...

  • Page 777: Dialing Plan Notation For Routing And Manipulation

    03(abc): for any number that starts with 03 and ends with abc.  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or Version 6.8 Mediant 500L MSBR...
  • Page 778 Mediant 500L MSBR Notation Description 401 or 405. Notes:  The value n must be less than the value m.  Only numerical ranges are supported (not alphabetical letters).  For suffix ranges, the starting (n) and ending (m) numbers in the range must include the same number of digits.

  • Page 779: Configuration Parameters Reference

    By default, the device's data-router firewall blocks all ("any") incoming traffic on the WAN. Thus, to enable WAN access, you must also enable the data-router firewall: # configure data (config-data)# interface gigabitethernet 0/0 (conf-if-GE 0/0)# firewall enable Version 6.8 Mediant 500L MSBR...
  • Page 780 Mediant 500L MSBR Parameter Description Web: Allow WAN access to Enables WAN access to the management interface through SNMP. SNMP  [0] Disable (default) CLI: wan-snmp-allow  [1] Enable [AllowWanSNMP]  By default, the device's data-router firewall blocks all ("any") incoming traffic on the WAN.

  • Page 781: Web Parameters

    The valid value is 0 to 100000, where 0 means that login is not denied regardless of number of failed login attempts. The default is 60. Web: Display Login Information Enables display of user's login information on each successful [DisplayLoginInformation] login attempt.  [0] = Disable (default) Version 6.8 Mediant 500L MSBR...
  • Page 782 Mediant 500L MSBR Parameter Description  [1] = Enable [EnableMgmtTwoFactorAuthenti Enables Web login authentication using a third-party, smart cation] card.  [0] = Disable (default)  [1] = Enable When enabled, the device retrieves the Web user’s login username from the smart card, which is automatically displayed (read-only) in the Web Login screen;...

  • Page 783: Telnet Parameters

    The valid range is 1 to 5 sessions. The default is 2. [TelnetMaxSessions] Note: Before changing the value, make sure that not more than this number of sessions are currently active; otherwise, the new setting Version 6.8 Mediant 500L MSBR...

  • Page 784: Ini File Parameters

    Mediant 500L MSBR Parameter Description will not take effect. [CLIPrivPass] Defines the password to access the Enable configuration mode in the CLI. The valid value is a string of up to 50 characters. The default is "Admin". Notes:  The password is case-sensitive.
  • Page 785 Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 786 Mediant 500L MSBR Parameter Description [AlarmHistoryTableMaxSize] Defines the maximum number of rows in the Alarm History table. This parameter can be controlled by the Config Global Entry Limit MIB (located in the Notification Log MIB). The valid range is 50 to 1000. The default is 500.
  • Page 787 IP address, as long as the correct community string is used in the request. Security can be enhanced by using Trusted Managers, which is an IP address from which the SNMP agent accepts and processes SNMP requests. Version 6.8 Mediant 500L MSBR...

  • Page 788: Parameters

    Mediant 500L MSBR Parameter Description  If no values are assigned to these parameters any manager can access the device.  Trusted managers can work with all community strings. SNMP V3 Users Table Web/EMS: SNMP V3 Users This parameter table defines SNMP v3 users. The format of CLI: configure system >...
  • Page 789 Defines the debug mode level, which is the type of [TR069DebugMode] messages sent to the Syslog server. The valid value is between 0 and 3, where 0 (default) means no debug messages are sent and 3 is all message types are sent. Version 6.8 Mediant 500L MSBR...

  • Page 790: Serial Parameters

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

  • Page 791: Auxiliary And Configuration File Name Parameters

    0 is Trunk 1. Web: Dial Plan File Defines the name (and path) of the Dial Plan file. This file should be EMS: Dial Plan File Name created using AudioCodes DConvert utility (refer to DConvert Utility [DialPlanFileName] User's Guide). [UserInfoFileName] Defines the name (and path) of the file containing the User Information data.

  • Page 792: Automatic Update Parameters

    Mediant 500L MSBR 67.1.9 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Table 67-9: Automatic Update of Software and Configuration Files Parameters Parameter Description General Automatic Update Parameters CLI: configure Enables the Automatic Update mechanism for the cmp file.
  • Page 793  [2] = Enable CRC for individual lines only. Same as option [1], except that the CRC ignores the order of lines (i.e., same text can be on different lines). Version 6.8 Mediant 500L MSBR...
  • Page 794 Mediant 500L MSBR Parameter Description CLI: automatic-update > use- Enables the Automatic Update mechanism to use the same client- zero-conf-certs server certificate as used for the Zero Configuration feature, instead [AupdUseZeroConfCerts] of the "regular" certificate used for Automatic Update. ...
  • Page 795 Note: For this parameter to take effect, a device reset is required. CLI: tls-cert Defines the name of the TLS certificate file and the URL from where [TLSCertFileUrl] it can be downloaded. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500L MSBR...
  • Page 796 Mediant 500L MSBR Parameter Description CLI: tls-private-key Defines the URL for downloading a TLS private key file using the [TLSPkeyFileUrl] Automatic Update facility. [UserInfoFileURL] Defines the name of the User Information file and the path to the server (IP address or FQDN) on which it is located.

  • Page 797: Networking Parameters

    Note: For this parameter to take effect, a device reset is required. [EnableNTPasOAM] Defines the application type for Network Time Protocol (NTP) services.  [1] = OAMP (default)  [0] = Control Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500L MSBR...

  • Page 798: Routing Parameters

    Mediant 500L MSBR 67.2.2 Routing Parameters The IP network routing parameters are described in the table below. Table 67-11: IP Network Routing Parameters Parameter Description Static Route Table Web/EMS: Static Route Defines up to 30 static VoIP IP routes for the device.

  • Page 799: Nat Parameters

    UA. In this mode, the device does not send any packets until it receives the first packet from the UA (in order to obtain the IP address). For more information on handling calls from UAs behind NAT, see ''First Version 6.8 Mediant 500L MSBR...

  • Page 800: Dns Parameters

    SendKeepAliveTrap parameter is set out] 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. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.

  • Page 801: Dhcp Parameters

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

  • Page 802: Ntp And Daylight Saving Time Parameters

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

  • Page 804: Debugging And Diagnostics Parameters

    Mediant 500L MSBR 67.3 Debugging and Diagnostics Parameters This subsection describes the device's debugging and diagnostic parameters. 67.3.1 General Parameters The general debugging and diagnostic parameters are described in the table below. Table 67-17: General Debugging and Diagnostic Parameters Parameter...
  • Page 805 Enables the device to ignore LOS alarms received from the BRI CLI: ignore-bri-los-alarm user-side trunk and attempts to make a call (relevant for IP-to-Tel [IgnoreBRILOSAlarm] calls).  [0] Disable  [1] Enable (default) Note: This parameter is applicable only to BRI interfaces. Version 6.8 Mediant 500L MSBR...

  • Page 806: Sip Test Call Parameters

    Mediant 500L MSBR 67.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below. Table 67-18: SIP Test Call Parameters Parameter Description Web: Test Call DTMF Defines the DTMF tone that is played for answered test calls (incoming String and outgoing).

  • Page 807: Syslog, Cdr And Debug Parameters

     [4] Start & End & Connect Call = CDR report is sent to Syslog at the start, at connection, and at the end of each call. Notes: Version 6.8 Mediant 500L MSBR...
  • Page 808 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the ‘acsyslog’...
  • Page 809 Syslog messages according to IP address, the messages can be filtered according to Facility level.  [16] = (Default) local use 0 (local0)  [17] = local use 1 (local1)  [18] = local use 2 (local2)  [19] = local use 3 (local3) Version 6.8 Mediant 500L MSBR...
  • Page 810 Mediant 500L MSBR Parameter Description  [20] = local use 4 (local4)  [21] = local use 5 (local5)  [22] = local use 6 (local6)  [23] = local use 7 (local7) Web: CDR Session ID Enables or disables the inclusion of the sequence number (S=) in CLI: cdr-seq-num CDR Syslog messages.
  • Page 811 The format of the ini file table parameter is: [LoggingFilters] [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_FilterType, LoggingFilters_Value, LoggingFilters_Syslog, LoggingFilters_CaptureType; [ \LoggingFilters ] For a detailed description of this table, see ''Filtering Syslog Messages and Debug Recordings'' on page 741. Version 6.8 Mediant 500L MSBR...

  • Page 812: Resource Allocation Indication Parameters

    Mediant 500L MSBR 67.3.4 Resource Allocation Indication Parameters The Resource Allocation Indication (RAI) parameters are described in the table below. Table 67-20: RAI Parameters Parameter Description [EnableRAI] Enables Resource Available Indication (RAI) alarm generation if the device's busy endpoints exceed a user-defined threshold, configured by the RAIHighThreshold parameter.

  • Page 813: Packetsmart Parameters

    Assigns an IP network interface (configured in the IP Interface table) for communicating with the PacketSmart server. This is typically the OAMP configure system > interface. packetsmart network voip interface-if Note: For the parameter to take effect, a device reset is required. [PacketSmartNetworkInter face ] Version 6.8 Mediant 500L MSBR...

  • Page 814: Security Parameters

    Mediant 500L MSBR 67.4 Security Parameters This subsection describes the device's security parameters. 67.4.1 General Security Parameters The general security parameters are described in the table below. Table 67-21: General Security Parameters Parameter Description Firewall Table Web/EMS: Internal Firewall This table parameter defines the device's access list (firewall), Parameters which defines network traffic filtering rules.
  • Page 815 The valid range is any value from 0. The default is 200. Timeout To Relatch RTCP Defines a period (msec) during which if no packets are received from the current RTCP session, the channel can re-latch onto Version 6.8 Mediant 500L MSBR...

  • Page 816: Https Parameters

    Mediant 500L MSBR Parameter Description [TimeoutToRelatchRTCPMsec] another RTCP stream. The valid range is any value from 0. The default is 10,000. Fax Relay Rx/Tx Timeout Defines a period (sec) during which if no T.38 packets are received [FaxRelayTimeoutSec] or sent from the current T.38 fax relay session, the channel can re- latch onto another stream.

  • Page 817: Srtp Parameters

    IP Profiles EMS: Enable Symmetric MKI (IpProfile_EnableSymmetricMKI). For a detailed description of this CLI: symmetric-mki parameter and for configuring this functionality in the IP Profile [EnableSymmetricMKI] table, see ''Configuring IP Profiles'' on page 332. Version 6.8 Mediant 500L MSBR...
  • Page 818 Mediant 500L MSBR Parameter Description 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. Web/EMS: Offered SRTP Defines the offered crypto suites (cipher encryption algorithms) for Cipher Suites SRTP.
  • Page 819 Profile table, see ''Configuring IP Profiles'' on page 332. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 500L MSBR...

  • Page 820: Tls Parameters

    Mediant 500L MSBR 67.4.4 TLS Parameters The Transport Layer Security (TLS) parameters are described in the table below. Table 67-24: TLS Parameters Parameter Description TLS Contexts Table Web: TLS Contexts Table Defines SSL/TLS certificates. CLI: configure system > tls #...
  • Page 821 (‘*’) to replace parts of the domain name. The valid range is a string of up to 49 characters. Note: This parameter is applicable only if the parameter PeerHostNameVerificationMode is set to 1 or 2. Version 6.8 Mediant 500L MSBR...

  • Page 822: Ssh Parameters

    Mediant 500L MSBR Parameter Description Web: TLS Expiry Check Start Defines the number of days before the installed TLS server CLI: expiry-check-start certificate is to expire at which the device must send a trap [TLSExpiryCheckStart] (acCertificateExpiryNotification) to notify of this.

  • Page 823: Taacs+ Parameters

    Table 67-27: IDS Parameters Parameter Description Web: Intrusion Detection Enables the IDS feature. System (IDS)  [0] Disable (default) CLI: enable-ids  [1] Enable [EnableIDS] Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500L MSBR...
  • Page 824 Mediant 500L MSBR Parameter Description CLI: ids-clear-period Defines the interval (in seconds) after which an IDS alarm is cleared from [IDSAlarmClearPeriod] the Active Alarms table if no thresholds are crossed during this time. However, this "quiet" period must be at least twice the Threshold Window value.

  • Page 825: Ocsp Parameters

    Web: Default Response When Determines whether the device allows or rejects peer certificates Server Unreachable when the OCSP server cannot be contacted. EMS: OCSP Default  [0] Reject (default) Response  [1] Allow CLI: default-response [OCSPDefaultResponse] Version 6.8 Mediant 500L MSBR...

  • Page 826: Quality Of Experience Parameters

    Mediant 500L MSBR 67.5 Quality of Experience Parameters The Quality of Experience (QoE) parameters are described in the table below. Table 67-29: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of the primary Session Experience Manager CLI: configure voip/qoe (SEM) server to where the quality experience reports are sent.
  • Page 827 The format of the ini file table parameter is as follows: CLI: configure voip/qoe [MediaEnhancementRules] media-enhancement-rules FORMAT MediaEnhancementRules_Index = [MediaEnhancementRules] MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of this table, see ''Configuring Media Enhancement Profiles'' on page 271. Version 6.8 Mediant 500L MSBR...

  • Page 828: Control Network Parameters

    Mediant 500L MSBR 67.6 Control Network Parameters 67.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 67-30: Proxy, Registration and Authentication SIP Parameters Parameter Description IP Group Table Web: IP Group Table This table configures IP Groups.
  • Page 829 If this parameter is disabled and the device registers to an IP Group (i.e., proxy server), it uses the string configured by the ProxyName parameter as the host name in the REGISTER's Request-URI and uses the string configured by the IP Group Version 6.8 Mediant 500L MSBR...
  • Page 830 Mediant 500L MSBR Parameter Description table parameter, SIPGroupName as the host name in the To and From headers. If the IP Group is configured with a Proxy Set that has multiple IP addresses, all the REGISTER messages sent to these proxies are sent with the same host name.
  • Page 831 DNS A-record query.  If a specific Transport Type is configured, a NAPTR query is not performed.  To enable NAPTR/SRV queries for Proxy servers only, use the global parameter ProxyDNSQueryType, or use the proxy Set table. Version 6.8 Mediant 500L MSBR...
  • Page 832 Mediant 500L MSBR Parameter Description Web: Proxy DNS Query Type Global parameter that defines the DNS query record type for CLI: proxy-dns-query resolving the Proxy server's configured domain name (FQDN) [ProxyDNSQueryType] into an IP address.  [0] A-Record (default) = A-record DNS query.
  • Page 833 [2] Full = Caches all challenges from the proxies. Notes:  This parameter is applicable only to the Gateway application.  Challenge Caching is used with all proxies and not only with the active one. Version 6.8 Mediant 500L MSBR...
  • Page 834 Mediant 500L MSBR Parameter Description Proxy IP Table Web: Proxy IP Table This table parameter defines the Proxy Set table with Proxy EMS: Proxy IP Set IDs, each with up to 10 Proxy server IP addresses (or CLI: configure voip > voip-network FQDN).
  • Page 835 EnableProxyKeepAlive is set to 2 (REGISTER). Typically, the device registers every 3,600 sec (i.e., one hour). The device resumes registration according to the parameter RegistrationTimeDivider. The valid range is 10 to 2,000,000. The default is 180. Version 6.8 Mediant 500L MSBR...
  • Page 836 Mediant 500L MSBR Parameter Description Web: Re-registration Timing [%] Defines the re-registration timing (in percentage). The timing is EMS: Time Divider a percentage of the re-register timing set by the Registrar CLI: re-registration-timing server. [RegistrationTimeDivider] The valid range is 50 to 100. The default is 50.
  • Page 837 Notes:  This parameter is applicable only to the Gateway application.  The out-of-service method is configured using the FXSOOSBehavior parameter. CLI: expl-un-reg Enables the device to perform explicit unregisters. [UnregistrationMode]  [0] Disable (default) Version 6.8 Mediant 500L MSBR...
  • Page 838 Mediant 500L MSBR Parameter Description  [1] Enable = The device sends an asterisk ("*") value in the SIP Contact header, instructing the Registrar server to remove all previous registration bindings. The device removes SIP User Agent (UA) registration bindings in a Registrar, according to RFC 3261.
  • Page 839 CPU caused by sending many registration requests at a given time. The valid value is 30 to 300 register requests per second. The default is 150. For configuration examples, see the description of the GeneratedRegistersInterval parameter. Version 6.8 Mediant 500L MSBR...

  • Page 840: Network Application Parameters

    Mediant 500L MSBR Parameter Description Generated Registers interval Defines the rate (in seconds) at which the device sends user register requests (REGISTER messages). The parameter is gen-reg-int based on the maximum number of REGISTER messages that [GeneratedRegistersInterval] can be sent at this rate, configured by the MaxGeneratedRegistersRate parameter.
  • Page 841 [ NATTranslation ] FORMAT NATTranslation_Index = NATTranslation_SourceIPInterfaceName, NATTranslation_TargetIPAddress, NATTranslation_SourceStartPort, NATTranslation_SourceEndPort, NATTranslation_TargetStartPort, NATTranslation_TargetEndPort; [ \NATTranslation ] For a detailed description of this table, see ''Configuring NAT Translation per IP Interface'' on page 159. Media Realm Table Version 6.8 Mediant 500L MSBR...

  • Page 842: General Sip Parameters

    Mediant 500L MSBR Parameter Description Web: Media Realm Table This table parameter defines Media Realms. The Media Realm table EMS: Media Realm allows you to divide a Media-type interface (defined in the Interface CLI: configure voip > voip- table) into several realms, where each realm is specified by a UDP port network realm range.
  • Page 843  'check-sync;reboot=true': triggers a device reset  'cwmp-connect': triggers connection with TR-069 Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Message Defines the maximum size (in Kbytes) for each SIP message that Length [KB] can be sent over the network. The device rejects messages [MaxSIPMessageLength] exceeding this user-defined size.
  • Page 844 Mediant 500L MSBR Parameter Description Web: Max Number of Active Defines the maximum number of simultaneous active calls supported Calls by the device. If the maximum number of calls is reached, new calls EMS: Maximum Concurrent are not established. Calls The valid range is 1 to the maximum number of supported channels.
  • Page 845 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: This parameter is applicable only if the EnableEarlyMedia parameter is set to 1 (i.e., enabled). Version 6.8 Mediant 500L MSBR...
  • Page 846 Mediant 500L MSBR Parameter Description Web: 183 Message Behavior Digital: Defines the ISDN message that is sent when the 183 EMS: SIP 183 Behaviour Session Progress message is received for IP-to-Tel calls. Analog: CLI: 183-msg-behavior Defines the response of the device upon receipt of a SIP 183 [SIP183Behaviour] response.
  • Page 847 IP Profile table, see ''Configuring IP Profiles'' on page 332. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 500L MSBR...
  • Page 848 Mediant 500L MSBR Parameter Description [HandleG711asVBD] Enables the handling of G.711 as a G.711 Voice Band Data (VBD) coder.  [0] = (Default) Disable. The device negotiates G.711 as a regular audio coder and sends an answer only with G.729 coder. For example, if the device is configured with G.729 and G.711 VBD...
  • Page 849 (i.e., TCP or TLS) and EnableSIPS is enabled, TLS is used through the entire connection (over multiple hops). Note: If this parameter is enabled and the parameter SIPTransportType is set to 0 (i.e., UDP), the connection fails. Version 6.8 Mediant 500L MSBR...
  • Page 850 Mediant 500L MSBR Parameter Description Web/EMS: Enable TCP Enables the reuse of the same TCP connection for all calls to the Connection Reuse same destination. CLI: tcp-conn-reuse  [0] Disable = Uses a separate TCP connection for each call. [EnableTCPConnectionReus ...
  • Page 851 Enables Remote-Party-Identity headers for calling and called EMS: Enable RPI Header numbers for Tel-to-IP calls. CLI: remote-party-id  [0] Disable (default). [EnableRPIheader]  [1] Enable = Remote-Party-Identity headers are generated in SIP INVITE messages for both called and calling numbers. Version 6.8 Mediant 500L MSBR...
  • Page 852 Mediant 500L MSBR Parameter Description Web: Enable History-Info Enables usage of the History-Info header. Header  [0] Disable (default) EMS: Enable History Info  [1] Enable CLI: hist-info-hdr User Agent Client (UAC) Behavior: [EnableHistoryInfo]  Initial request: The History-Info header is equal to the Request- URI.
  • Page 853 Bearer Capability IE contains “Unrestricted 64k”, the outgoing INVITE Request-URI and Contact header includes “tgrp=ccdata;trunk-context=dsn.mil”. If the Bearer Capability IE contains “Speech”, the INVITE in this case does not contain tgrp and trunk-context parameters. Note: IP-to-Tel configuration (using the PSTNPrefix parameter) Version 6.8 Mediant 500L MSBR...
  • Page 854 Mediant 500L MSBR Parameter Description overrides the 'tgrp' parameter in incoming INVITE messages. Web/EMS: TGRP Routing Determines the precedence method for routing IP-to-Tel calls - Precedence according to the Inbound IP Routing table or according to the SIP CLI: tgrp-routing-prec 'tgrp' parameter.
  • Page 855 G.729. Web: User-Agent Information Defines the string that is used in the SIP User-Agent and Server EMS: User Agent Display Info response headers. When configured, the string CLI: user-agent-info <UserAgentDisplayInfo value>/software version' is used, for Version 6.8 Mediant 500L MSBR...
  • Page 856 Parameter Description [UserAgentDisplayInfo] example: 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 500L MSBR/v.6.80A.227.005 The maximum string length is 50 characters. Note: The software version number and preceding forward slash (/) cannot be modified.
  • Page 857 (Service Unavailable) responses to indicate an unavailable service. The Retry-After header is used with the 503 (Service Unavailable) response to indicate how long the service is expected to be unavailable to the requesting SIP client. The device maintains a list Version 6.8 Mediant 500L MSBR...
  • Page 858 Mediant 500L MSBR Parameter Description of available proxies, by using the Keep-Alive mechanism. The device checks the availability of proxies by sending SIP OPTIONS every keep-alive timeout to all proxies. If the device receives a SIP 503 response to an INVITE, it also marks that the proxy is out of service for the defined "Retry-After"...
  • Page 859 [0] Disable (default)  [1] Enable Web/EMS: Enable Contact Determines whether the device sets the Contact header of outgoing Restriction INVITE requests to ‘anonymous’ for restricted calls. CLI: contact-restriction  [0] Disable (default) [EnableContactRestriction]  [1] Enable Version 6.8 Mediant 500L MSBR...
  • Page 860 Mediant 500L MSBR Parameter Description CLI: anonymous-mode Determines whether the device's IP address is used as the URI host [AnonymousMode] part instead of "anonymous.invalid" in the INVITE's From header for Tel-to-IP calls.  [0] = (Default) If the device receives a call from the Tel with blocked caller ID, it sends an INVITE with From: “anonymous”<anonymous@anonymous.invalid>...
  • Page 861 The re-INVITE is sent immediately upon receipt of the 200 OK (when the call is answered).  [0] = Disable (default)  [1] = Enable Note: This parameter is applicable only if SRTP is used. Version 6.8 Mediant 500L MSBR...
  • Page 862 Mediant 500L MSBR Parameter Description [NumberOfActiveDialogs] Defines the maximum number of concurrent, outgoing SIP REGISTER dialogs. This parameter is used to control the registration rate. The valid range is 1 to 20. The default is 20. Notes:  Once a 200 OK is received in response to a REGISTER message, the REGISTER message is not considered in this maximum count limit.
  • Page 863 [1] Enable = If all the trunks pertaining to Trunk Group #1 are down, the device does not respond to received SIP OPTIONS. Web: Comfort Noise Enables negotiation and usage of Comfort Noise (CN) for Gateway Generation Negotiation calls. EMS: Comfort Noise Version 6.8 Mediant 500L MSBR...
  • Page 864 Mediant 500L MSBR Parameter Description  Generation [0] Disable CLI: com-noise-gen-nego  [1] Enable (default) [ComfortNoiseNegotiation] The use of CN is indicated by including a payload type for CN on the media description line of the SDP. The device can use CN with a codec whose RTP time stamp clock rate is 8,000 Hz (G.711/G.726).
  • Page 865 Call-ID: ConorCCR-0-LU-1229417827103300@dtas- stdn.fs5000group0-000.l CSeq: 1 INFO Contact: sip:10.20.7.70:5060 Content-Type: application/On-Hook (application/Off-Hook) Content-Length: 0 Notes:  This parameter is applicable only if the parameter RegretTime is configured.  This parameter is applicable only to FXS interfaces. Version 6.8 Mediant 500L MSBR...
  • Page 866 Mediant 500L MSBR Parameter Description Web: PSTN Alert Timeout Digital: Defines the Alert Timeout (in seconds) for calls sent to the EMS: Trunk PSTN Alert PSTN. This timer is used between the time a Setup message is sent Timeout to the Tel side (IP-to-Tel call establishment) and a Connect message CLI: pstn-alert-timeout is received.
  • Page 867 (i.e. Manipulation Set ID is set to -1). Notes:  This parameter is used only if the Outbound Message Manipulation Set parameter of the destination IP Group is not set.  This parameter is applicable only to the Gateway application. Version 6.8 Mediant 500L MSBR...
  • Page 868 Mediant 500L MSBR Parameter Description Out-of-Service (Busy Out) Parameters Web/EMS: Enable Busy Out Enables the Busy Out feature. CLI: busy-out  [0] Disable (Default) [EnableBusyOut]  [1] Enable When Busy Out is enabled and certain scenarios exist, the device does the following: ...
  • Page 869 Graceful out-of-service enabled: The device rejects new incoming calls. Only when all channels are idle (when graceful period ends or when all channels become idle before graceful period ends, whichever occurs first), does the device Version 6.8 Mediant 500L MSBR...
  • Page 870 Mediant 500L MSBR Parameter Description take the D-channel down. When connectivity is restored for the Busy Out feature or the Trunk Group is unlocked, the device brings the D-channels up again. Note: For partially configured trunks (only some channels configured), this option only rejects new calls for the trunk; the D- channel remains up.
  • Page 871 [4] Block = Blocks the trunk. For a detailed description, see option [4] of the DigitalOOSBehaviorForTrunk_x parameter (per trunk setting).  [5] Service and D-Channel = Sends ISDN Service messages to indicate out-of-service or in-service state and takes the D-channel Version 6.8 Mediant 500L MSBR...
  • Page 872 Mediant 500L MSBR Parameter Description down or brings it up. For a detailed description, see option [5] of the DigitalOOSBehaviorForTrunk_x parameter (per trunk setting). Notes:  When using the parameter to configure out-of-service behavior for all trunks, you must reset the device for the settings to take effect.
  • Page 873 The format of the ini file table parameter is as follows: [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Policy, MessagePolicy_MaxMessageLength, MessagePolicy_MaxHeaderLength, MessagePoliy_MaxBodyLength, MessagePolicy_MaxNumHeaders, MessagePolicy_MaxNumBodies, MessagePolicy_SendRejection, MessagePolicy_MethodListType, MessagePolicy_MethodList, MessagePolicy_BodyListType, MessagePolicy_BodyList; [/MessagePolicy] For a detailed description of this table, see Configuring SIP Message Policy Rules. Version 6.8 Mediant 500L MSBR...

  • Page 874: Coders And Profile Parameters

    Mediant 500L MSBR 67.8 Coders and Profile Parameters The profile parameters are described in the table below. Table 67-33: Profile Parameters Parameter Description IP Profile Table Web: IP Profile Settings This table parameter configures the IP Profile table. Each IP Profile ID EMS: Protocol Definition >...
  • Page 875 TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP, TelProfile_TimeForReorderTone, TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode; [\TelProfile] For a description of this parameter, see Configuring Tel Profiles on page 327. Version 6.8 Mediant 500L MSBR...

  • Page 876: Channel Parameters

    Mediant 500L MSBR 67.9 Channel Parameters This subsection describes the device's channel parameters. 67.9.1 Voice Parameters The voice parameters are described in the table below. Table 67-34: Voice Parameters Parameter Description Web/EMS: Input Gain Global parameter that defines the pulse-code modulation (PCM) CLI: input-gain input (received) gain control level (in decibels).
  • Page 877 CLI: echo-canceller-hybrid- returning from the hybrid. loss  [0] = (Default) 6 dB [ECHybridLoss]  [1] = N/A  [2] = 0 dB Version 6.8 Mediant 500L MSBR...

  • Page 878: Coder Parameters

    Mediant 500L MSBR Parameter Description  [3] = 3 dB EMS: ECN lp Mode Defines the echo cancellation Non-Linear Processing (NLP) mode. CLI: echo-canceller-NLP-  [0] = (Default) NLP adapts according to echo changes mode  [1] = Disables NLP [ECNLPMode] ...
  • Page 879 [1] = AMR frame according to RFC 3267 bundling.  [2] = AMR frame according to RFC 3267 interleaving.  [3] = AMR is passed using the AMR IF2 format. Note: Bandwidth Efficient mode is not supported; the mode is always Octet-aligned. Version 6.8 Mediant 500L MSBR...

  • Page 880: Dtmf Parameters

    Mediant 500L MSBR 67.9.3 DTMF Parameters The dual-tone multi-frequency (DTMF) parameters are described in the table below. Table 67-36: DTMF Parameters Parameter Description Web/EMS: DTMF Transport Determines the DTMF transport type. Type  [0] Mute DTMF = DTMF digits are removed from the voice CLI: DTMF-transport-type stream and are not relayed to remote side.

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

    Profile table, see Configuring IP Profiles on page 332. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 500L MSBR...
  • Page 882 Mediant 500L MSBR Parameter Description Web: Enable RTP Redundancy Enables the device to include the RTP redundancy dynamic Negotiation payload type in the SDP, according to RFC 2198. CLI: rtp-rdcy-nego-enbl  [0] Disable (default) [EnableRTPRedundancyNegotiation]  [1] Enable When enabled, the device includes in the SDP message the RTP payload type "RED"...
  • Page 883 [RTPNoOpPayloadType] Payload Type for all types of non hard-coded RTP Payload types, refer to RFC 3551). The default is 120. Note: When defining this parameter, ensure that it doesn't cause collision with other payload types. Version 6.8 Mediant 500L MSBR...
  • Page 884 Mediant 500L MSBR Parameter Description CLI: rtcp-act-mode Disables RTCP traffic when there is no RTP traffic. This [RTCPActivationMode] feature is useful, for example, to stop RTCP traffic that is typically sent when calls are put on hold (by an INVITE with 'a=inactive' in the SDP).
  • Page 885 (i.e., after a SIP BYE). The RTCP [SBCRtcpXrReportMode] XR is sent in the SIP PUBLISH message.  [0] Disable (default)  [1] End of Call Note: This parameter is applicable only to the SBC application. Version 6.8 Mediant 500L MSBR...

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

    Mediant 500L MSBR 67.10 Gateway and IP-to-IP Parameters 67.10.1 Fax and Modem Parameters The fax and modem parameters are described in the table below. Table 67-38: Fax and Modem Parameters Parameter Description Web: Fax Transport Mode Determines the fax transport mode used by the device.
  • Page 887 Defines a timeout (in msec) for detecting fax from the Tel side Connect (msec) during an established voice call. The interval starts from when the voice call is established. If the device detects a fax tone Version 6.8 Mediant 500L MSBR...
  • Page 888 Mediant 500L MSBR Parameter Description CLI: configure voip > sip-definition within the interval, it ends the voice session and sends a T.38 or general-settings > fax-detect- VBD re-INVITE message to the IP side and processes the fax. If timeout-since-connect the interval expires without any received fax event, the device ignores all subsequent fax events during the voice session.
  • Page 889 [0] = (Default) Determined internally ketInterval]  [1] = 5 msec (not recommended)  [2] = 10 msec  [3] = 20 msec Note: When set to 5 msec (1), the maximum number of simultaneous channels supported is 120. Version 6.8 Mediant 500L MSBR...
  • Page 890 Mediant 500L MSBR Parameter Description EMS: Dynamic Jitter Buffer Defines the Jitter Buffer delay (in milliseconds) during fax and Minimal Delay (dB) modem bypass session. CLI: jitter-buffer-minimum-delay The range is 0 to 150 msec. The default is 40. [FaxModemBypasDJBufMinDela EMS: Enable Inband Network Enables in-band network detection related to fax/modem.
  • Page 891 T.38 packets to the terminating fax machine. Note: To enable No-Op packet transmission, use the NoOpEnable and NoOpInterval parameters. Web: Profile Number Defines the V.150.1 profile, which determines how many DSP EMS: Allocation Profile channels support V.150.1. Version 6.8 Mediant 500L MSBR...
  • Page 892 Mediant 500L MSBR Parameter Description [V1501AllocationProfile] The value range is 0 to 20. The default is 0. Note: For this parameter to take effect, a device reset is required. Web/EMS: SSE Payload Type Rx Defines the V.150.1 (modem relay protocol) State Signaling CLI: V1501-SSE-payload-type-rx Event (SSE) payload type Rx.

  • Page 893: Dtmf And Hook-Flash Parameters

    Where 16 is the DTMF code for hook flash.  [7] INFO (HUAWEI) = Sends a SIP INFO message with Hook-Flash indication. The device sends the INFO message as follows: Content-Length: 17 Content-Type: application/sscc event=flashhook Version 6.8 Mediant 500L MSBR...
  • Page 894 Mediant 500L MSBR Parameter Description Notes:  The device can interwork DTMF HookFlashCode to SIP INFO messages with Hook Flash indication (for digital interfaces).  FXO interfaces support only the receipt of RFC 2833 Hook-Flash signals and INFO [1] type.
  • Page 895 IP network as DTMF signals, according to the settings of the TxDTMFOption parameter.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_FirstTxDtmfOption and IpProfile_SecondTxDtmfOption). For configuring IP Profiles, see ''Configuring IP Profiles'' on page 332. Version 6.8 Mediant 500L MSBR...
  • Page 896 Mediant 500L MSBR Parameter Description [DisableAutoDTMFMute] Enables the automatic muting of DTMF digits when out-of- band DTMF transmission is used.  [0] = (Default) Automatic mute is used.  [1] = No automatic mute of in-band DTMF. When this parameter is set to 1, the DTMF transport type is...
  • Page 897 EMS: Use Digit For Special DTMF are used for out-of-band DTMF signaling (using SIP CLI: special-digit-rep INFO/NOTIFY). [UseDigitForSpecialDTMF]  [0] Special = (Default) Uses the strings ‘*’ and ‘#’.  [1] Numeric = Uses the numerical values 10 and 11. Version 6.8 Mediant 500L MSBR...

  • Page 898: Digit Collection And Dial Plan Parameters

    Mediant 500L MSBR 67.10.3 Digit Collection and Dial Plan Parameters The digit collection and dial plan parameters are described in the table below. Table 67-40: Digit Collection and Dial Plan Parameters Parameter Description Web/EMS: Dial Plan Index Defines the Dial Plan index to use in the external Dial Plan file. The CLI: dial-plan-index Dial Plan file is loaded to the device as a .dat file (converted using...
  • Page 899 Notes:  The symbols can always be used as the first digit of a dialed number even if you disable this parameter.  This parameter is applicable only to FXS and FXO interfaces. Version 6.8 Mediant 500L MSBR...

  • Page 900: Voice Mail Parameters

    Mediant 500L MSBR 67.10.4 Voice Mail Parameters The voice mail parameters are described in the table below. For more information on the Voice Mail application, refer to the CPE Configuration Guide for Voice Mail. Table 67-41: Voice Mail Parameters Parameter...
  • Page 901 For this parameter to take effect, a device reset is required.  When the RS-232 connection is used for SMDI messages (Serial SMDI), it cannot be used for other applications, for example, to access the Command Line Interface (CLI). Version 6.8 Mediant 500L MSBR...
  • Page 902 Mediant 500L MSBR Parameter Description Web/EMS: SMDI Timeout Defines the time (in msec) that the device waits for an SMDI Call [SMDITimeOut] Status message before or after a Setup message is received. This parameter synchronizes the SMDI and analog CAS interfaces.
  • Page 903 (not EMS: VM Digit Pattern On an internal extension). No Answer Ext The valid range is a 120-character string. CLI: fwd-no-ans-dig-pat-ext [DigitPatternForwardOnNo AnswerExt] Version 6.8 Mediant 500L MSBR...
  • Page 904 Mediant 500L MSBR Parameter Description Web: Forward on Do Not Defines the digit pattern used by the PBX to indicate 'call forward on Disturb Digit Pattern do not disturb' when the original call is received from an external line (External) (not an internal extension).

  • Page 905: Supplementary Services Parameters

    FORMAT CallerDisplayInfo_Index = CallerDisplayInfo_DisplayString, CallerDisplayInfo_IsCidRestricted, CallerDisplayInfo_Module, CallerDisplayInfo_Port; [\CallerDisplayInfo] Where,  Module = Module number, where 1 denotes the module in Slot 1.  Port = Port number, where 1 denotes Port 1 of a module. For example: Version 6.8 Mediant 500L MSBR...
  • Page 906 Mediant 500L MSBR Parameter Description CallerDisplayInfo 0 = Susan C.,0,1,1; ("Susan C." is sent as the Caller ID for Port 1 of Module 1) CallerDisplayInfo 1 = Mark M.,0,1,2; ("Mark M." is sent as Caller ID for Port 2 of Module 1) For a detailed description of this table, see Configuring Caller Display Information on page 492.
  • Page 907 ID of the waiting call.  [0] = Caller ID type 2 isn't played.  [1] = (Default) Caller ID type 2 is played.  Note: This parameter is applicable only to FXS interfaces. Version 6.8 Mediant 500L MSBR...
  • Page 908 Mediant 500L MSBR Parameter Description EMS: Caller ID Timing Mode Determines when Caller ID is generated. CLI: caller-id-timing-mode  [0] = (Default) Caller ID is generated between the first two [AnalogCallerIDTimingMode] rings.  [1] = The device attempts to find an optimized timing to generate the Caller ID according to the selected Caller ID type.
  • Page 909 [1] Relay = (Currently not applicable.)  [3] Mute = (Default) The caller ID signal is detected from the Tel side and then erased from the voice stream. Note: Caller ID detection is applicable only to FXO interfaces. Version 6.8 Mediant 500L MSBR...

  • Page 910: Call Waiting Parameters

    Mediant 500L MSBR Parameter Description Reject Anonymous Calls Per Port Table CLI: configure voip > gw analoggw This table parameter determines whether the device rejects reject-anonymous-calls incoming anonymous calls per FXS port. If enabled, when a [RejectAnonymousCallPerPort] device's FXS interface receives an anonymous call, it rejects the call and responds with a SIP 433 (Anonymity Disallowed) response.
  • Page 911 (e.g., external versus internal calls). There are three ways to use the distinctive call waiting tones:  Playing the call waiting tone according to the SIP Alert-Info header in the received 180 Ringing SIP response. The value of Version 6.8 Mediant 500L MSBR...

  • Page 912: Call Forwarding Parameters

    Mediant 500L MSBR Parameter Description the Alert-Info header is added to the value of the FirstCallWaitingToneID parameter.  Playing the call waiting tone according to PriorityIndex in the ToneIndex table parameter.  Playing the call waiting tone according to the parameter “CallWaitingTone#' of a SIP INFO message.
  • Page 913 Retry Time [NRTSubscribeRetryTime] Web/EMS: Call Forward Defines the ringing tone type played when call forward notification is Ring Tone ID accepted. CLI: cfe-ring-tone-id The valid value range is 1 to 5. The default is 1. [CallForwardRingToneID] Version 6.8 Mediant 500L MSBR...

  • Page 914: Message Waiting Indication Parameters

    Mediant 500L MSBR 67.10.5.4 Message Waiting Indication Parameters The message waiting indication (MWI) parameters are described in the table below. Table 67-45: MWI Parameters Parameter Description Web: Enable MWI Enables Message Waiting Indication (MWI). EMS: MWI Enable  [0] Disable (default).
  • Page 915 EMS: Bellcore VMWI Type One Determines the Bellcore VMWI sub-standard. Standard  [0] = (Default) Between rings. CLI: bellcore-vmwi-type-one-  [1] = Not ring related. standard Note: For this parameter to take effect, a device reset is [BellcoreVMWITypeOneStandard] required. Version 6.8 Mediant 500L MSBR...

  • Page 916: Call Hold Parameters

    Mediant 500L MSBR 67.10.5.5 Call Hold Parameters The call hold parameters are described in the table below. Table 67-46: Call Hold Parameters Parameter Description Web/EMS: Enable Hold Global parameter that enables the Call Hold feature (analog interfaces) CLI: hold and interworking of the Hold/Retrieve supplementary service from ISDN [EnableHold] PRI to SIP.
  • Page 917 To Tel side: plays DTMF digits according to the received SIP INFO message(s). (The stopped held tone is not played again.)  To IP side: sends DTMF SIP INFO messages to an IP destination if it detects DTMF digits from the Tel side. Version 6.8 Mediant 500L MSBR...

  • Page 918: Call Transfer Parameters

    Mediant 500L MSBR 67.10.5.6 Call Transfer Parameters The call transfer parameters are described in the table below. Table 67-47: Call Transfer Parameters Parameter Description Web/EMS: Enable Transfer Enables the Call Transfer feature. CLI: enable-transfer  [0] Disable [EnableTransfer]  [1] Enable = (Default) The device responds to a REFER message with the Referred-To header to initiate a call transfer.
  • Page 919 INVITE message. If the timeout expires, the device sends the INVITE without changing the calling number. Notes:  The suspension of the INVITE message occurs for all calls.  This parameter is applicable to QSIG. Version 6.8 Mediant 500L MSBR...
  • Page 920 Mediant 500L MSBR Parameter Description Web: Call Transfer using re-INVITEs Enables call transfer using re-INVITEs. CLI: enable-call-transfer-using-  [0] Disable = (Default) Call transfer is done using REFER reinvites messages. [EnableCallTransferUsingReinvites]  [1] Enable = Call transfer is done by sending re-INVITE messages (instead of REFER).

  • Page 921: Multi-Line Extensions And Supplementary Services Parameters

    Web: 3-Way Conference Mode Defines the mode of operation for three-way conferencing. EMS: 3 Way Mode  [0] AudioCodes Media Server = (Default) The conference- CLI: 3w-conf-mode initiating INVITE sent by the device, uses the ConferenceID [3WayConferenceMode] concatenated with a unique identifier as the Request-URI.
  • Page 922 Mediant 500L MSBR Parameter Description conference is established on the device without the need of an external Conference server. You can limit the number of simultaneous, on-board 3-way conference calls, by using the MaxInBoardConferenceCalls parameter.  [3] Huawei Media Server = The conference is managed by an external, third-party Conferencing server.

  • Page 923: Mlpp And Emergency Call Parameters

    The device identifies emergency calls by one of the following:  The destination number of the IP call matches one of the numbers defined by the EmergencyNumbers parameter. (For E911, you must define this parameter with the value "911".) Version 6.8 Mediant 500L MSBR...
  • Page 924 Mediant 500L MSBR Parameter Description  The incoming SIP INVITE message contains the “emergency” value in the Priority header. Notes:  This parameter is applicable to FXS/FXO, CAS, and ISDN.  For FXO interfaces, the preemption is done only on existing IP-to-Tel calls.
  • Page 925 Enabled: The network-domain field in the Resource-Priority header is set in the Precedence Level field according to Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value). The domain name can be a string of up to 10 characters. Version 6.8 Mediant 500L MSBR...
  • Page 926 Mediant 500L MSBR Parameter Description 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;...
  • Page 927 Determines whether the SIP resource-priority tag is added in the [RPRequired] SIP Require header of the INVITE message for Tel-to-IP calls.  [0] Disable = Excludes the SIP resource-priority tag from the SIP Require header. Version 6.8 Mediant 500L MSBR...
  • Page 928 Mediant 500L MSBR Parameter Description  [1] Enable = (Default) Adds the SIP resource-priority tag in the SIP Require header. Note: This parameter is applicable only to MLPP priority call handling (i.e., only when the CallPriorityMode parameter is set to 1).

  • Page 929: Call Cut-Through Parameters

    If this parameter is disabled and the PSTN side remains in off-hook state after the IP call ends the call, the device releases the call after 60 seconds.  A special CAS table can be used to report call status events Version 6.8 Mediant 500L MSBR...

  • Page 930: Automatic Dialing Parameters

    Mediant 500L MSBR Parameter Description (Active/Idle) to the PSTN side during Cut Through mode.  This feature can also be configured in a Tel Profile and therefore, assigned to specific B-channels that use specific CAS tables. 67.10.5.11 Automatic Dialing Parameters The automatic dialing upon off-hook parameters are described in the table below.
  • Page 931 Double-wink signaling [2]: interval between the first and second wink  Wink and Polarity signaling [3]: interval between wink and polarity change The valid range is 100 to 2000. The default is 1000. Note: See the EnableDIDWink parameter for configuring the wink signaling type. Version 6.8 Mediant 500L MSBR...
  • Page 932 Mediant 500L MSBR Parameter Description Web/EMS: Delay Before Defines the time interval (in msec) between the detection of the off-hook DID Wink and the generation of the DID Wink. CLI: delay-b4-did-wink The valid range is 0 to 1,000. The default is 0.

  • Page 933: Isdn Bri Parameters

    Enables the device to indicate the type of call forwarding service in the Request-URI of the outgoing SIP INVITE message, using a [UseFacilityInRequest] proprietary header parameter "facility=<call forward service>".  [0] = (Default) Disable  [1] = Enable Version 6.8 Mediant 500L MSBR...

  • Page 934: Pstn Parameters

    [57] BRI IUA Note: The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. [ProtocolType_x] Defines the protocol type for a specific trunk ID (where x denotes the Trunk ID and 0 is the first trunk).
  • Page 935 For example, if one port is connected to a PBX and the other port to the PSTN, upon a power outage, calls originating from the PBX are routed directly to the PSTN Version 6.8 Mediant 500L MSBR...
  • Page 936 Mediant 500L MSBR Parameter Description (instead of to the IP network).  [0] = (Default) PSTN Fallback is activated only upon power outage.  [2] = PSTN Fallback is activated upon one of the following:  Power outage  Loss of IP network connectivity (i.e., no ping) Note: ...

  • Page 937: Tdm Bus And Clock Timing Parameters

    TDMBusClockSource is set to 4 and the parameter TDMBusPSTNAutoClockEnable is set to 0. Web/EMS: TDM Bus Enable Defines the automatic fallback of the clock. Fallback  [0] Manual (default) [TDMBusEnableFallback]  [1] Auto Non-Revertive  [2] Auto Revertive Version 6.8 Mediant 500L MSBR...
  • Page 938 Mediant 500L MSBR Parameter Description Web: TDM Bus Fallback Clock Determines the fallback clock source on which the device Source synchronizes in the event of a clock failure. EMS: TDM Bus Fallback Clock  [4] Network (default) [TDMBusFallbackClock]  [8] H.110_A ...

  • Page 939: Cas Parameters

    The range is up to 11 characters. CLI: cas-dial-plan-name For example, the below configures E1_MFCR2 trunk with a single [CASTrunkDialPlanName_x] protocol (Trunk 5): ProtocolType_5 = 7 CASFileName_0='R2_Korea_CP_ANI.dat' CASTableIndex_5 = 0 DialPlanFileName = 'DialPlan_USA.dat' CASTrunkDialPlanName_5 = 'AT_T' Version 6.8 Mediant 500L MSBR...
  • Page 940 Mediant 500L MSBR Parameter Description Note: The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. [CASFileName_x] Defines the CAS file name (e.g., 'E_M_WinkTable.dat') that defines the CAS protocol, where x denotes the CAS file ID (0-7).
  • Page 941 Web: Digit Signaling System Defines which Signaling System to use in both directions [CASStateMachineDigitSignalin (detection\generation). gSystem]  [0] DTMF = DTMF signaling.  [1] MF = (Default) MF signaling.  [-1] Default = Default value. Version 6.8 Mediant 500L MSBR...

  • Page 942: Isdn Parameters

    Mediant 500L MSBR 67.10.6.4 ISDN Parameters The ISDN parameters are described in the table below. Table 67-58: ISDN Parameters Parameter Description Web: ISDN Termination Side Determines the ISDN termination side. EMS: Termination Side  [0] User side = (Default) ISDN User Termination Equipment CLI: isdn-termination-side (TE) side.
  • Page 943 Response Behavior the behaviour of the Q.931 protocol. CLI: isdn-bits-ns-behavior  [0] = Disable (default). [ISDNIBehavior]  [1] NO STATUS ON UNKNOWN IE = Q.931 Status message isn't sent if Q.931 received message contains an Version 6.8 Mediant 500L MSBR...
  • Page 944 Mediant 500L MSBR Parameter Description unknown/unrecognized IE. By default, the Status message is sent. Note: This value is applicable only to ISDN variants in which sending of Status message is optional.  [2] NO STATUS ON INV OP IE = Q.931 Status message isn't sent if an optional IE with invalid content is received.
  • Page 945 ISDNGeneralCCBehavior features, add the individual feature values. For example, to support both [16] and [32] features, set ISDNGeneralCCBehavior = 48 (i.e., 16 + 32). Web/EMS: Outgoing Calls Determines several behaviour options (bit fields) that influence the Version 6.8 Mediant 500L MSBR...
  • Page 946 Mediant 500L MSBR Parameter Description Behavior behaviour of the ISDN Stack outgoing calls. To select options, click CLI: isdn-bits-outgoing-calls- the arrow button, and then for each required option, select 1 to behavior enable. The default is 0 (i.e., disable). [ISDNOutCallsBehavior] ...
  • Page 947 0-63: Static TEI is used.  127: Dynamic TEI allocation is supported (TEI request procedure initiated). CLI: tei-assign-trigger (config- Defines when to start the TEI assignment procedure. voice > interface bri The valid values are (bit-field parameter): <module/port>) Version 6.8 Mediant 500L MSBR...

  • Page 948: Isdn And Cas Interworking Parameters

    Mediant 500L MSBR Parameter Description  [BriTEIAssignTrigger_x] Bit#0: LAYER1_ACTIVATION  Bit#1: BRI_PORT_CONFIG  Bit#2: CALL_ESTABLISH The default is 0x02. Note: The parameter is applicable only to the User side (for Dynamic TEI). CLI: tei-remove-trigger (config- Defines the following: voice > interface bri ...
  • Page 949 ISDN Setup message to the IP side in the initial INVITE message. For each subsequently received ISDN Info Q.931 message, the device sends the collected digits to the IP side in INFO messages. Version 6.8 Mediant 500L MSBR...
  • Page 950 Mediant 500L MSBR Parameter Description Notes:  When option [2] or [3] is configured, you can define the minimum number of overlap digits to collect before sending the first SIP message for routing the call, using the MinOverlapDigitsForRouting parameter. ...
  • Page 951 [0] = (Default) ASCII presentation of Q.931 QSIG message.  [1] = Binary encoding of Q.931 QSIG message (according to ECMA-355, RFC 3204, and RFC 2025). Note: This parameter is applicable only if the QSIG Tunneling Version 6.8 Mediant 500L MSBR...
  • Page 952 Mediant 500L MSBR Parameter Description feature is enabled (using the EnableQSIGTunneling parameter). Web: Enable Hold to ISDN Enables SIP-to-ISDN interworking of the Hold/Retrieve EMS: Enable Hold 2 ISDN supplementary service. CLI: hold-to-isdn  [0] Disable (default) [EnableHold2ISDN]  [1] Enable Notes: ...
  • Page 953 Discriminator (pd) attribute (according to IETF Internet-Draft draft-johnston-sipping-cc-uui-04). For example: User-to- User=3030373435313734313635353b313233343b3834;pd  [2] = SIP header format: User-to-User with encoding=hex at the end and pd embedded as the first byte (according to IETF Internet-Draft draft-johnston-sipping-cc-uui-03). For example: User-to- Version 6.8 Mediant 500L MSBR...
  • Page 954 Mediant 500L MSBR Parameter Description 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. For example: SIP Header in text format: User-to-User=01800213027b712a;NULL;4582166;...
  • Page 955 Notes:  The option Any is only applicable 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. Version 6.8 Mediant 500L MSBR...
  • Page 956 Mediant 500L MSBR Parameter Description CLI: snd-isdn-ser-aftr-restart Enables the device to send an ISDN SERVice message per trunk [SendISDNServiceAfterResta upon device reset. The messsage (transmitted on the trunk's D- channel) indicates the availability of the trunk's B-channels (i.e., trunk in service).
  • Page 957 SIP INVITE to Q.931 Setup  SIP REFER to Q.931 Setup  SIP 200 OK to Q.931 Connect  SIP INFO to Q.931 User Information  SIP 18x to Q.931 Alerting  SIP BYE to Q.931 Disconnect Version 6.8 Mediant 500L MSBR...
  • Page 958 Mediant 500L MSBR Parameter Description Notes:  The interworking of ISDN User-to-User IE to SIP INFO is applicable only to the Euro ISDN, QSIG, and 4ESS PRI variants.  To interwork the UUIE header from SIP-to-ISDN messages with the 4ESS ISDN variant, the ISDNGeneralCCBehavior parameter must be set to 16384.
  • Page 959 DTMF transfer; otherwise, the device sends the INVITE according to regular transfer rules. After completing the in-band transfer, the device waits for the ISDN Disconnect message. If the Disconnect message is Version 6.8 Mediant 500L MSBR...
  • Page 960 Mediant 500L MSBR Parameter Description received during the first 5 seconds, the device sends a SIP NOTIFY with 200 OK message; otherwise, the device sends a NOTIFY with 4xx message.  [6] = Supports AT&T toll free out-of-band blind transfer for trunks configured with the 4ESS ISDN protocol.
  • Page 961 C. The PBX updates this by sending a QSIG Facility message with CallTranferComplete invoke APDU. The device interworks this message to a SIP UPDATE message containing a P-Asserted- Identity header with the number and name derived from the QSIG Version 6.8 Mediant 500L MSBR...
  • Page 962 Mediant 500L MSBR Parameter Description CallTranferComplete RedirectionNumber and RedirectionName. Notes:  For IP-to-Tel calls, the RedirectionNumber and RedirectionName in the CallTRansferComplete invoke is derived from the P-Asserted-Identity and Privacy headers in the received SIP INFO message.  To include the P-Asserted-Identity header in outgoing SIP UPDATE messages, set the AssertedIDMode parameter to Add P-Asserted-Identity.

  • Page 963: Answer And Disconnect Supervision Parameters

    10 seconds and an IP phone hangs up a call established with a BRI phone after 2 seconds. As the call duration is less than the minimum call duration, the device does not disconnect the call on the Tel side. However, it sends a SIP Version 6.8 Mediant 500L MSBR...
  • Page 964 Mediant 500L MSBR Parameter Description 200 OK immediately upon receipt of the BYE to disconnect from the IP phone. The call is disconnected from the Tel side only when the call duration is greater than or equal to the minimum call duration.
  • Page 965 Determines whether a call is disconnected upon detection Detection (ISDN) of a busy tone (for ISDN). EMS: Isdn Disconnect On Busy Tone  [0] Disable = (Default) Do not disconnect call upon CLI: disc-on-bsy-tone-i detection of busy tone. Version 6.8 Mediant 500L MSBR...
  • Page 966 Mediant 500L MSBR Parameter Description  [ISDNDisconnectOnBusyTone] [1] Enable = Disconnect call upon detection of busy tone. Notes:  This parameter is applicable only to ISDN protocols.  IP-to-ISDN calls are disconnected on detection of SIT tones only in call alert state. If the call is in connected state, the SIT does not disconnect the calls.
  • Page 967 350 msec above the parameter's value. For example, if this parameter is set to 400 msec, then the detection window is 300 to 750 msec.  For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500L MSBR...

  • Page 968: Tone Parameters

    Mediant 500L MSBR Parameter Description [CurrentDisconnectDefaultThreshold] Defines the line voltage threshold at which a current disconnect detection is considered. The valid range is 0 to 20 Volts. The default is 4 Volts. Notes:  This parameter is applicable only to FXO interfaces.
  • Page 969 This parameter can also be configured for a Tel Profile (in the Tel Profile table). Web: Time Before Reorder Defines the delay interval (in seconds) from when the device receives Tone [sec] a SIP BYE message (i.e., remote party terminates call) until the device Version 6.8 Mediant 500L MSBR...
  • Page 970 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. When...
  • Page 971 SDP message is received, the device cuts through the voice channel and doesn't play the ringback tone.  Digital Interfaces: Plays according to 'Early Media'. If a SIP 180 response is received and the voice channel is already open Version 6.8 Mediant 500L MSBR...
  • Page 972 Mediant 500L MSBR Parameter Description (due to a previous 183 early media response or due to an SDP in the current 180 response), the device configured for ISDN / CAS doesn't play the ringback tone; PI = 8 is sent in an ISDN Alert message (unless the ProgressIndicator2ISDN_x parameter is configured differently).
  • Page 973 This parameter is applicable only to digital PSTN interfaces. Web: Play Ringback Tone to Global parameter that enables the device to play a ringback tone to the IP side for IP-to-Tel calls. You can also configure this functionality Version 6.8 Mediant 500L MSBR...
  • Page 974 Mediant 500L MSBR Parameter Description EMS: Play Ring Back Tone per specific calls, using IP Profiles (IpProfile_PlayRBTone2IP). For a To IP detailed description of this parameter and for configuring this CLI: play-rbt-2ip functionality in the IP Profile table, see ''Configuring IP Profiles'' on [PlayRBTone2IP] page 332.

  • Page 975: Tone Detection Parameters

    If the call is in connected state, the SIT does not disconnect the call. Detection of busy or reorder tones disconnect these calls also in call connected state.  For IP-to-CAS calls, detection of busy, reorder, or SIT Version 6.8 Mediant 500L MSBR...

  • Page 976: Metering Tone Parameters

    Mediant 500L MSBR Parameter Description tones disconnect the call in any call state. EMS: UDT Detector Frequency Defines the deviation (in Hz) allowed for the detection of each Deviation signal frequency. CLI: UDT-detector-frequency- The valid range is 1 to 50. The default is 50.
  • Page 977 To associate a configured Charge Code to an outgoing Tel-to-IP call, use the Outbound IP Routing table.  To configure the Charge Codes table using the Web interface, see Configuring Charge Codes Table on page 481. Version 6.8 Mediant 500L MSBR...

  • Page 978: Telephone Keypad Sequence Parameters

    Mediant 500L MSBR 67.10.10 Telephone Keypad Sequence Parameters The telephony keypad sequence parameters are described in the table below. Table 67-64: Telephone Keypad Sequence Parameters Parameter Description Web/EMS: Call Pickup Key Defines the keying sequence for performing a call pick-up. Call...
  • Page 979 EMS: Call Forward Busy option. CLI: fwd-on-busy [KeyCFBusy] Web: Forward On Busy or No Defines the keypad sequence to activate the forward on 'busy Answer or no answer' option. EMS: CF Busy Or No Answer Version 6.8 Mediant 500L MSBR...
  • Page 980 Mediant 500L MSBR Parameter Description CLI: fwd-busy-or-no-ans [KeyCFBusyOrNoAnswer] Web: Do Not Disturb EMS: CF Do Not Disturb Defines the keypad sequence to activate the Do Not Disturb CLI: fwd-dnd option (immediately reject incoming calls). [KeyCFDoNotDisturb] To activate the required forward method from the telephone: Dial the user-defined sequence number on the keypad;...

  • Page 981: Fxo And Fxs Parameters

    EMS: Country Coefficients according to USA or TBR21 standard. CLI: fxo-country-coefficients  [66] Europe = TBR21 [CountryCoefficients]  [70] USA = (Default) United States Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500L MSBR...
  • Page 982 Mediant 500L MSBR Parameter Description CLI: fxo-dc-termination Defines the FXO line DC termination (i.e., resistance). [FXODCTermination]  [0] = (Default) DC termination is set to 50 Ohms.  [1] = DC termination set to 800 Ohms. The termination changes from 50 to 800 Ohms only when moving from onhook to offhook.
  • Page 983 Determines the number of rings before the device starts EMS: Rings Before Caller ID detecting Caller ID. CLI: rings-b4-det-callerid  [0] 0 = Before first ring. [RingsBeforeCallerID]  [1] 1 = (Default) After first ring. Version 6.8 Mediant 500L MSBR...
  • Page 984 Mediant 500L MSBR Parameter Description  [2] 2 = After second ring. Web/EMS: Guard Time Between Calls Defines the time interval (in seconds) after a call has ended CLI: guard-time-btwn-calls and a new call can be accepted for IP-to-Tel (FXO) calls.

  • Page 985: Trunk Groups And Routing Parameters

    FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_FirstTrunkId, TrunkGroup_FirstBChannel, TrunkGroup_LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileId, TrunkGroup_LastTrunkId, TrunkGroup_Module; [\TrunkGroup] For a description of this table, seeConfiguring Trunk Group on page 373. Note: Trunk Group ID 1 is denoted as 0 in the table. Version 6.8 Mediant 500L MSBR...
  • Page 986 Mediant 500L MSBR Parameter Description Trunk Group Settings Web: Trunk Group Settings This table parameter configures the rules for channel EMS: SIP Routing > Hunt Group allocation per Trunk Group. CLI: configure voip > gw hunt-or-trunk- The format of the ini file table parameter is as follows:...
  • Page 987 Source Number and Display Name are set to '100' and the Presentation is set to Allowed (0). When 'From: <sip:100@101.102.103.104>' is received, the outgoing Source Number is set to '100' and the Presentation is set to Restricted (1). Version 6.8 Mediant 500L MSBR...
  • Page 988 Mediant 500L MSBR Parameter Description Web: ENUM Resolution Defines the ENUM service for translating telephone numbers CLI: enum-service-domain to IP addresses or domain names (FQDN), for example, [EnumService] e164.arpa, e164.customer.net, or NRENum.net. The valid value is a string of up to 50 characters. The default is "e164.arpa".
  • Page 989 (i.e., number isn't listed in the table or a call restriction routing rule of IP address 0.0.0.0 is applied), the call is released. Note: When no proxy is used, this parameter must be disabled and filtering is according to the Outbound IP Routing table. Version 6.8 Mediant 500L MSBR...
  • Page 990 Mediant 500L MSBR Parameter Description Web: IP-to-Tel Tagging Destination Defines the Dial Plan index in the Dial Plan file for called Dial Plan Index prefix tags for representing called number prefixes in CLI: ip2tel-tagging-dst Inbound Routing rules. [IP2TelTaggingDestDialPlanIndex] The valid values are 0 to 7, where 0 denotes PLAN1, 1 denotes PLAN2, and so on.
  • Page 991 The valid value range is 1-10. The default is 5. Call Forking Parameters Web/EMS: Forking Handling Mode Determines how the device handles the receipt of multiple CLI: forking-handling SIP 18x forking responses for Tel-to-IP calls. The forking Version 6.8 Mediant 500L MSBR...
  • Page 992 Mediant 500L MSBR Parameter Description [ForkingHandlingMode] 18x response is the response with a different SIP to-tag than the previous 18x response. These responses are typically generated (initiated) by Proxy / Application servers that perform call forking, sending the device's originating INVITE (received from SIP clients) to several destinations, using the same Call ID.

  • Page 993: Ip Connectivity Parameters

    CLI: alt-rte-tel2ip-keep-alive [AltRoutingTel2IPKeepAliveTime] Web: Max Allowed Packet Loss for Defines the packet loss (in percentage) at which the IP Alt Routing [%] connection is considered a failure and Alternative Routing CLI: mx-pkt-loss-4-alt-rte mechanism is activated. Version 6.8 Mediant 500L MSBR...

  • Page 994: Alternative Routing Parameters

    Mediant 500L MSBR Parameter Description [IPConnQoSMaxAllowedPL] The default is 20%. Web: Max Allowed Delay for Alt Defines the transmission delay (in msec) at which the IP Routing [msec] connection is considered a failure and the Alternative Routing CLI: mx-all-dly-4-alt-rte mechanism is activated.
  • Page 995 EMS: Alt Route Cause IP to Tel result of one of these reasons, the device attempts to locate an CLI: configure voip > gw alternative Trunk Group for the call in the Inbound IP Routing table. Version 6.8 Mediant 500L MSBR...

  • Page 996: Number Manipulation Parameters

    Mediant 500L MSBR Parameter Description manipulations general-setting The format of the ini file table parameter is as follows: alt-route-cause-ip2tel [AltRouteCauseIP2Tel] [AltRouteCauseIP2Tel] FORMAT AltRouteCauseIP2Tel_Index = AltRouteCauseIP2Tel_ReleaseCause; [\AltRouteCauseIP2Tel] For example: AltRouteCauseIP2Tel 0 = 3 (No Route to Destination) AltRouteCauseIP2Tel 1 = 1...
  • Page 997 [15] Systematic/Unconditional = Call forward unconditional Web: Redirect Number SIP Determines the value of the Redirect Number screening indicator in to TEL ISDN Setup messages. EMS: Set IP To Tel  [-1] Not Configured (default) Redirect Screening Version 6.8 Mediant 500L MSBR...
  • Page 998 Mediant 500L MSBR Parameter Description  Indicator [0] User Provided CLI: redir-nb-si-2tel  [1] User Passed [SetIp2TelRedirectScreeni  [2] User Failed ngInd]  [3] Network Provided Note: This parameter is applicable only to digital PSTN interfaces (ISDN). Web: Set IP-to-TEL Defines the redirect reason for IP-to-Tel calls.
  • Page 999 [1] or [2].  You can also use this feature for IP-to-Tel calls, by configuring this parameter per IP Profile (IpProfile_CopyDest2RedirectNum). For more information, see Configuring IP Profiles on page 332. Version 6.8 Mediant 500L MSBR...
  • Page 1000 Mediant 500L MSBR Parameter Description CLI: rep-calling-w-redir Enables the replacement of the calling number with the redirect number disc-on-bsy-tone-i for ISDN-to-IP calls. [ReplaceCallingWithRedire  [0] = Disable (default) ctNumber]  [1] = The calling name is removed and left blank. The outgoing INVITE message excludes the redirect number that was used to replace the calling number.
  • Page 1001 Called Numbers  [1] Yes = Incoming ISDN call that includes a redirect number CLI: swap-rdr-n-called-nb (sometimes referred to as 'original called number') uses the redirect [SwapRedirectNumber] number instead of the called number. Version 6.8 1001 Mediant 500L MSBR...
  • Page 1002 Mediant 500L MSBR Parameter Description [UseReferredByForCalling Determines whether the device uses the number from the URI in the Number] SIP Referred-By header as the calling number in the outgoing Q.931 Setup message, when SIP REFER messages are received.  [0] = (Default) No ...
  • Page 1003 LDestinationManipulatio manipulation requirements (that generally require many rules).  [0] = Disable (default)  [1] = Enable Destination Phone Number Manipulation for Tel-to-IP Calls Table Version 6.8 1003 Mediant 500L MSBR...
  • Page 1004 Mediant 500L MSBR Parameter Description Web: Destination Phone This table parameter manipulates the destination number of Tel-to-IP Number Manipulation calls. The format of the ini file table parameter is as follows: Table for Tel > IP Calls [NumberMapTel2Ip] EMS: SIP Manipulations >...
  • Page 1005 The format of the ini file table parameter is as follows: EMS: Redirect Number [RedirectNumberMapTel2Ip] Map Tel to IP FORMAT RedirectNumberMapTel2Ip_Index = CLI: configure voip > gw RedirectNumberMapTel2Ip_ManipulationName, manipulations redirect- RedirectNumberMapTel2Ip_DestinationPrefix, number-map-tel2ip RedirectNumberMapTel2Ip_RedirectPrefix, [RedirectNumberMapTel2 RedirectNumberMapTel2Ip_RemoveFromLeft, RedirectNumberMapTel2Ip_RemoveFromRight, RedirectNumberMapTel2Ip_LeaveFromRight, RedirectNumberMapTel2Ip_Prefix2Add, RedirectNumberMapTel2Ip_Suffix2Add, RedirectNumberMapTel2Ip_IsPresentationRestricted, RedirectNumberMapTel2Ip_SrcTrunkGroupID, RedirectNumberMapTel2Ip_SrcIPGroupID; [\RedirectNumberMapTel2Ip] Version 6.8 1005 Mediant 500L MSBR...

  • Page 1006: Sbc Parameters

    Mediant 500L MSBR Parameter Description For a description of this table, see ''Configuring Redirect Number Manipulation'' on page 391. Phone Context Table Web: Phone Context Table This table parameter configures the Phone Context table. This EMS: SIP Manipulations > parameter maps NPI and TON to the SIP 'phone-context' parameter, Phone Context and vice versa.
  • Page 1007 If no other SIP response (for example, 200 OK) is received thereafter within this timeout, the call is released. The valid range is 0 to 3600 seconds. the default is 600. CLI: configure voip/sbc general- Defines the maximum number of concurrent SIP SUBSCRIBE Version 6.8 1007 Mediant 500L MSBR...
  • Page 1008 Mediant 500L MSBR Parameter Description setting/num-of-subscribes sessions permitted on the device. [NumOfSubscribes] The valid value is any value between 0 and the maximum supported SUBSCRIBE sessions. When set to -1, the device uses the default value. For more information, contact your AudioCodes sales representative.
  • Page 1009 IP Profile. Web: Keep original user in Determines whether the device replaces the Contact user with a Register unique Contact user in the outgoing message in response to a [SBCKeepContactUserinRegist REGISTER request. Version 6.8 1009 Mediant 500L MSBR...
  • Page 1010 Mediant 500L MSBR Parameter Description  [0] Disable = (Default) The device replaces the original Contact user with a unique Contact user, for example:  Received Contact: <sip:123@domain.com>  Outgoing (unique) Contact: <sip:FEU1_7_1@SBC>  [1] Enable = The original Contact user is retained and used in the outgoing REGISTER request.
  • Page 1011  [0] 0 = The device sends 'qop=auth' in the SIP response, requesting authentication (i.e., validates user by checking user name and password). This option does not authenticate the Version 6.8 1011 Mediant 500L MSBR...
  • Page 1012 Mediant 500L MSBR Parameter Description message body (i.e., SDP).  [1] 1 = The device sends 'qop=auth-int' in the SIP response, indicating required authentication and authentication with integrity (e.g., checksum). This option restricts the client to authenticating the entire SIP message, including the body, if present.
  • Page 1013 Enables the interworking of dialog information (parsing of call Interworking identifiers in XML body) in SIP NOTIFY messages received from CLI: configure voip/sbc general- a remote application server. setting/sbc-dialog-info-interwork  [0] Disable (default) [EnableSBCDialogInfoInterwor  [1] Enable Version 6.8 1013 Mediant 500L MSBR...
  • Page 1014 Mediant 500L MSBR Parameter Description king] For more information, see ''Interworking Dialog Information in SIP NOTIFY Messages'' on page 545. CLI: sbc-keep-call-id Enables the device to use the same call identification value [SBCKeepOriginalCallId] received in incoming messages for the call identification in outgoing messages.
  • Page 1015 [0] Disable = (Default) Device forwards the REGISTER messages as is (i.e., not terminated on the device).  [1] Enable = REGISTER messages of secondary lines are terminated on the device. Note: The device always forwards REGISTER messages of the Version 6.8 1015 Mediant 500L MSBR...

This manual is also suitable for:

Mediant 500 msbr

Table of Contents