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

AudioCodes Mediant 800B MSBR User Manual

Multi-service business router; session border controller
Hide thumbs Also See for Mediant 800B MSBR:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Quick Manual
Mediant™ 800B MSBR
Multi-Service Business Router
Session Border Controller
User's Manual
Version 6.8
September 2014
Document # LTRT-12813

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Mediant 800B MSBR and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for AudioCodes Mediant 800B MSBR

Summary of Contents for AudioCodes Mediant 800B MSBR

  • Page 1 Mediant™ 800B MSBR Multi-Service Business Router Session Border Controller User's Manual Version 6.8 September 2014 Document # LTRT-12813...

  • Page 3: Table Of Contents

    Limiting OAMP Access to a Specific WAN Interface ..........72 Web Login Authentication using Smart Cards ............72 Configuring Web and Telnet Access List ............... 73 CLI-Based Management ..................75 Getting Familiar with CLI ..................75 Version 6.8 Mediant 800B MSBR...
  • Page 4 Mediant 800B MSBR 9.1.1 Understanding Configuration Modes ............... 75 9.1.2 Using CLI Shortcuts ....................76 9.1.3 Common CLI Commands ..................77 9.1.4 Configuring Tables in CLI ..................78 9.1.5 Understanding CLI Error Messages ................ 79 Enabling CLI ......................79 9.2.1 Enabling Telnet for CLI ....................
  • Page 5 18.1 Configuring Voice Settings ................... 173 18.1.1 Configuring Voice Gain (Volume) Control .............173 18.1.2 Silence Suppression (Compression) ..............174 18.1.3 Echo Cancellation ....................174 18.2 Fax and Modem Capabilities ................176 18.2.1 Fax/Modem Operating Modes ................177 18.2.2 Fax/Modem Transport Modes ................177 Version 6.8 Mediant 800B MSBR...
  • Page 6 Mediant 800B MSBR 18.2.2.1 T.38 Fax Relay Mode ................177 18.2.2.2 G.711 Fax / Modem Transport Mode ............ 180 18.2.2.3 Fax Fallback ..................180 18.2.2.4 Fax/Modem Bypass Mode ..............181 18.2.2.5 Fax / Modem NSE Mode ............... 182 18.2.2.6 Fax / Modem Transparent with Events Mode ........183 18.2.2.7 Fax / Modem Transparent Mode ............
  • Page 7 23.3 Configuring Tel Profile ..................311 23.4 Configuring IP Profiles ..................314 24 Introduction ..................... 345 25 Digital PSTN ..................... 347 25.1 Configuring Trunk Settings ................... 347 25.2 TDM and Timing ....................350 25.2.1 Configuring TDM Bus Settings ................350 Version 6.8 Mediant 800B MSBR...
  • Page 8 Mediant 800B MSBR 25.2.2 Clock Settings ......................350 25.2.2.1 Recovering Clock from PSTN Line Interface ........351 25.2.2.2 Configuring Internal Clock as Clock Source ......... 351 25.3 Configuring CAS State Machines ................. 352 25.4 Configuring Digital Gateway Parameters ............. 354 25.5 Tunneling Applications ..................355 25.5.1 TDM Tunneling ......................355...
  • Page 9 30.11.4.1 About E9-1-1 Services ................449 30.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........450 30.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 30.11.4.4 Configuring AudioCodes ELIN Gateway ..........459 30.12 Multilevel Precedence and Preemption ..............461 30.12.1 MLPP Preemption Events in SIP Reason Header ..........464...
  • Page 10 Mediant 800B MSBR 31.3 Configuring FXO Settings ..................476 31.4 Configuring Authentication ................... 477 31.5 Configuring Automatic Dialing ................478 31.6 Configuring Caller Display Information ..............480 31.7 Configuring Call Forward ..................481 31.8 Configuring Caller ID Permissions ............... 483 31.9 Configuring Call Waiting ..................
  • Page 11 37.3 Configuring SBC IP-to-IP Routing ................ 552 37.4 Configuring SIP Response Codes for Alternative Routing Reasons ....561 38 SBC Manipulations ..................563 38.1 Configuring IP-to-IP Inbound Manipulations ............565 38.2 Configuring IP-to-IP Outbound Manipulations ............568 Version 6.8 Mediant 800B MSBR...
  • Page 12 Mediant 800B MSBR 39 CRP Overview ....................575 40 CRP Configuration ..................577 40.1 Enabling the CRP Application ................577 40.2 Configuring Call Survivability Mode ..............578 40.3 Pre-Configured IP Groups ..................579 40.4 Pre-Configured IP-to-IP Routing Rules ..............580 40.4.1 Normal Mode ......................580...
  • Page 13 Contents 47.1.2 HTTP-based Provisioning ..................632 47.1.3 FTP- or NFS-based Provisioning ................633 47.1.4 Provisioning using AudioCodes EMS ..............633 47.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 634 47.2.1 Files Provisioned by Automatic Update ..............634 47.2.2 File Location for Automatic Update ...............635 47.2.3 Triggers for Automatic Update ................636...
  • Page 14 57.1 Syslog Message Format ..................715 57.1.1 Event Representation in Syslog Messages ............716 57.1.2 Unique Device Identification in Syslog Messages ..........718 57.1.3 Identifying AudioCodes Syslog Messages using Facility Levels ......718 57.1.4 SNMP Alarms in Syslog Messages ...............719 57.2 Enabling Syslog ....................719 57.3 Configuring Web Operations to Report to Syslog ..........
  • Page 15 67.4.7 IDS Parameters .....................803 67.4.8 OCSP Parameters ....................804 67.5 Quality of Experience Parameters ............... 805 67.6 Control Network Parameters ................807 67.6.1 IP Group, Proxy, Registration and Authentication Parameters ......807 67.6.2 Network Application Parameters ................819 Version 6.8 Mediant 800B MSBR...
  • Page 16 Mediant 800B MSBR 67.7 General SIP Parameters ..................821 67.8 Coders and Profile Parameters ................849 67.9 Channel Parameters .................... 851 67.9.1 Voice Parameters ....................851 67.9.2 Coder Parameters ....................854 67.9.3 DTMF Parameters ....................855 67.9.4 RTP, RTCP and T.38 Parameters .................856 67.10 Gateway and IP-to-IP Parameters ...............
  • Page 17 User's Manual Contents 68.2 Channel Capacity and Capabilities ..............1017 69 Technical Specifications ................1021 Version 6.8 Mediant 800B MSBR...
  • Page 18 Mediant 800B MSBR This page is intentionallt left blank. User's Manual Document #: LTRT-12813...

  • Page 19: Weee Eu Directive

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

  • Page 20: Related Documentation

    Security measures should be done in accordance with your organization’s security policies. For basic security guidelines, refer to AudioCodes Recommended Security Guidelines document. Note: Throughout this manual, unless otherwise specified, the term device refers to your AudioCodes products.
  • 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: Documentation Feedback

    Mediant 800B MSBR Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads. User's Manual Document #: LTRT-12813...

  • Page 23: Overview

    Symmetric High-Speed Digital Subscriber Line (SHDSL) - supports up to four copper wire pairs according to G.991.2, acting as a remote-terminal CPE device. Both ATM and EFM modes are supported. In the ATM mode, a variety of protocols are Version 6.8 Mediant 800B MSBR...
  • Page 24 Mediant 800B MSBR supported, including PPPoE, PPPoA, and RFC 2684 in both bridged (Ethernet-over- ATM) and routed (IP-over-ATM) variants. In the EFM mode, the SHDSL port functions as a logical Ethernet device.  ADSL2+ / VDSL2 (RJ-11 port interfaces) ...
  • Page 25 Part I Getting Started with Initial Connectivity...

  • Page 27: 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 36. Version 6.8 Mediant 800B MSBR...
  • Page 28 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 29: 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 800B MSBR...
  • Page 30 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 31: Configuring Voip Lan Interface For Oamp

    IP address of the device; the Web interface's Web Login screen appears: 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. Version 6.8 Mediant 800B MSBR...
  • Page 32 Mediant 800B MSBR Open the Interface Table page (Configuration tab > VoIP menu > Network > IP Interfaces Table). 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: •...

  • Page 33: Cli

    Access the VoIP configuration mode: # configure voip Access the Interface table: (config-voip)# interface network-if 0 Configure the IP address: (network-if-0)# ip-address <IP address> Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Version 6.8 Mediant 800B MSBR...
  • Page 34 Mediant 800B MSBR Configure the Default Gateway address: (network-if-0)# gateway <IP address> Exit the Interface table: (network-if-0)# exit 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.

  • Page 35: 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 800B MSBR...

  • Page 36: Configuring The Device's Dhcp Server

    Mediant 800B 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 37 (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 800B MSBR...
  • Page 38 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 39: Enabling Remote Management From Wan

    From the 'Allow WAN access to HTTPS’ or 'Allow WAN access to HTTP' drop- down list, select Enable. Click Submit, and then reset the device with a flash burn for your settings to take effect. Version 6.8 Mediant 800B MSBR...

  • Page 40: Remote Telnet-Based Management

    Mediant 800B 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 41 Part II Management Tools...

  • Page 43: 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 763. Version 6.8 Mediant 800B MSBR...
  • Page 44 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 45: Web-Based Management

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

  • Page 46: Accessing The Web Interface

    Mediant 800B 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 45). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 47: Areas Of The Gui

    ''Navigation Tree'' on page 48. 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 51. Version 6.8 Mediant 800B MSBR...

  • Page 48: Toolbar Description

    Mediant 800B 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 592).

  • Page 49: 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 800B MSBR...

  • Page 50: Showing / Hiding The Navigation Pane

    Mediant 800B 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 51: 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 800B MSBR...
  • Page 52 Mediant 800B 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 53: Modifying And Saving Parameters

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

  • Page 54: Working With Tables

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

  • Page 55: Searching For Configuration Parameters

    The search key can include the full parameter name (e.g., "EnableSyslog") or a substring of it (e.g., "sys"). If you search for a substring, all parameters containing the specified substring in their names are listed in the search result. Version 6.8 Mediant 800B MSBR...
  • Page 56 Mediant 800B MSBR  To search for a parameter: On the Navigation bar, click the Search tab; the Search engine appears in the Navigation pane. In the field alongside the Search button, enter the parameter name or a substring of the name for which you want to search.

  • Page 57: 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 800B MSBR...

  • Page 58: Getting Help

    Mediant 800B 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 59: Logging Off The Web Interface

    Figure 8-15: Log Off Confirmation Box Click OK; you are logged off the Web session and the Web Login dialog box appears enabling you to re-login, if required. Version 6.8 Mediant 800B MSBR...

  • Page 60: Viewing The Home Page

    Mediant 800B MSBR Viewing the Home Page The Home page is displayed when you access the device's Web interface. The Home page provides you with a graphical display of the device's front panel, showing color-coded status icons for various operations device.
  • Page 61 AIS Alarm: Alarm Indication Handset Offhook: Channel is off- Signal (AIS), also known as hook, but there is no active RTP (blue) the Blue Alarm session D-Channel Alarm: D-channel alarm (orange) NFAS Alarm (dark orange) Version 6.8 Mediant 800B MSBR...
  • Page 62 Mediant 800B MSBR Item # Description If you click a port, a shortcut menu appears with commands allowing you to do the following:  Reset channel (Analog ports only): Resets the analog port (see Resetting an Analog Channel on page 595) ...

  • Page 63: Assigning A Port Name

    Click the required port icon; a shortcut menu appears: From the shortcut menu, choose Update Port Info; a text box appears: Figure 8-16: Text Box for Entering Port Name Type a brief description for the port, and then click Apply Port Info. Version 6.8 Mediant 800B MSBR...

  • Page 64: Configuring Web User Accounts

    Mediant 800B 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 800B MSBR...
  • Page 66 Mediant 800B 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 800B MSBR...
  • Page 68 Mediant 800B 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 default is according to the settings of the 'Deny Authentication Timer' parameter (see ''Configuring Web Security Settings'' on page 71). Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Version 6.8 Mediant 800B MSBR...

  • Page 70: Displaying Login Information Upon Login

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

  • Page 71: Configuring Web Security Settings

    Figure 8-21: Web Security Settings Page 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 592. Version 6.8 Mediant 800B MSBR...

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

    - what the user has (i.e., the physical card) and what the user knows (i.e., the login password). 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. User's Manual Document #: LTRT-12813...

  • Page 73: Configuring Web And Telnet Access List

    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. Figure 8-23: Web & Telnet Access List Table Version 6.8 Mediant 800B MSBR...
  • Page 74 Mediant 800B MSBR To delete authorized IP addresses, select the Delete Row check boxes corresponding to the IP addresses that you want to delete, and then click Delete Selected Addresses; the IP addresses are removed from the table and these IP addresses can no longer access the Web and Telnet interfaces.

  • 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 800B 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

    (session closed) display Displays the configuration of current configuration set. help Displays a short help how-to string. history Displays a list of previously run commands. list Displays the available command list of the current command-set. Version 6.8 Mediant 800B MSBR...

  • Page 78: Configuring Tables In Cli

    Mediant 800B MSBR Command Description | <filter> Applied to a command output. The filter should be typed after the command with a pipe mark (|). Supported filters:  include <word> – filter (print) lines which contain <word>  exclude <word> – filter lines which does not contain <word>...

  • Page 79: Understanding Cli Error Messages

    Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 767. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 800B MSBR...

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

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

  • Page 82: Establishing A Cli Session

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

  • Page 83: Viewing Current Cli Sessions

    The session ID is a unique identification of each currently logged in user. You can view the session ID by running the show users command (see ''Viewing Current CLI Sessions'' on page 83). Note: The session from which the command is run cannot be terminated. Version 6.8 Mediant 800B MSBR...

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

    Mediant 800B MSBR Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be specified from 0 to 65,535, or determined by re-sizing the terminal window by mouse- dragging the window's border.
  • Page 85 To configure how much time to wait for a TACACS+ response before failing the authentication: (config-data)# tacacs-server timeout <in seconds>  To configure the device's data-router WAN interface through which communication with the TACACS+ server is done: (config-data)# tacacs-server source data source-address interface <interface name> Version 6.8 Mediant 800B MSBR...
  • Page 86 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 87: 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 88 Mediant 800B MSBR For detailed descriptions of the SNMP parameters, see ''SNMP Parameters'' on page 768.  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String).

  • Page 89: Configuring Snmp Trap Destinations

    The device sends SNMP traps to this port. The valid value range is 100 to 4000. The default is 162. Web: Trap User Associates a trap user with the trap destination. This [SNMPManagerTrapUser] determines the trap format, authentication level, and Version 6.8 Mediant 800B MSBR...

  • Page 90: Configuring Snmp Trusted Managers

    Mediant 800B MSBR Parameter Description encryption level.  v2cParams (default) = SNMPv2 user community string  SNMPv3 user configured in ''Configuring SNMP V3 Users'' on page Trap Enable Activates the sending of traps to the SNMP Manager. [SNMPManagerTrapSendingEnable_x]  [0] Disable ...

  • Page 91: Configuring Snmp V3 Users

    Name of the SNMP v3 user. This name must be unique. CLI: username [SNMPUsers_Username] Authentication Protocol Authentication protocol of the SNMP v3 user. CLI: auth-protocol  [0] None (default) [SNMPUsers_AuthProtocol]  [1] MD5  [2] SHA-1 Privacy Protocol Privacy protocol of the SNMP v3 user. Version 6.8 Mediant 800B MSBR...
  • Page 92 Mediant 800B MSBR Parameter Description  CLI: priv-protocol [0] None (default) [SNMPUsers_PrivProtocol]  [1] DES  [2] 3DES  [3] AES-128  [4] AES-192  [5] AES-256 Authentication Key Authentication key. Keys can be entered in the form of a text CLI: auth-key password or long hex string.

  • Page 93: 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 800B MSBR...
  • Page 94 Mediant 800B 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 95 ♦ 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 800B MSBR...
  • Page 96 Mediant 800B 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 97 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 800B MSBR...

  • Page 98: Tr-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 99: 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 100 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 101: Ini File-Based Management

    The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME].  Format line: Specifies the columns of the table (by their string names) that are to be Version 6.8 Mediant 800B MSBR...
  • Page 102 Mediant 800B MSBR configured. • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed. • Columns must be separated by a comma ",".

  • Page 103: General Ini File Formatting Rules

    Save the file with the ini file extension name (e.g., myconfiguration.ini). Load the file to the device. For loading the ini file to the device, see ''Loading an ini File to the Device'' on page 104. Version 6.8 Mediant 800B MSBR...

  • Page 104: Loading An Ini File To The Device

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

    $0$<plain text>: Password can be entered in plain text; useful for configuring a new password. When the ini file is loaded to the device and then later saved from the device to a PC, the password is displayed obscured (i.e., $1$<obscured password>). Version 6.8 Mediant 800B MSBR...

  • Page 106: 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 107 Part III General System Settings...

  • Page 109: Configuring Ssl/Tls Certificates

    Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 800B MSBR...
  • Page 110 Mediant 800B 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 111 SSL 2.0-compatible handshake and then switch to the highest TLS version supported by both peers.  [1] 1 = Only TLS 1.0 is used. Clients attempting to contact the device using any other version are rejected. Version 6.8 Mediant 800B MSBR...
  • Page 112 Mediant 800B 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 113: Assigning Csr-Based Certificates To Tls Contexts

    Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 13-2: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request. Version 6.8 Mediant 800B MSBR...

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

    Mediant 800B MSBR When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below:...

  • Page 115: Generating Private Keys For Tls Contexts

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

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

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

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

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

  • Page 118: Configuring Mutual Tls Authentication

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

  • Page 119: Tls For Remote Device Management

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

  • Page 120: Configuring Tls Server Certificate Expiry Check

    Mediant 800B MSBR 13.8 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure device send...

  • Page 121: Date And Time

    "1". For USA New York, the UTC/GMT offset is -5 hours and therefore, the offset is a minus value and configured as "-5". To configure Daylight Saving Time (DST), see 'Configuring Daylight Saving Time' on page 123. Version 6.8 Mediant 800B MSBR...
  • Page 122 Mediant 800B MSBR 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 cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication.

  • Page 123: Configuring Daylight Saving Time

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

  • Page 125: Configuring Power Over Ethernet

    ''Viewing Ethernet Port Information'' on page 662. The following procedure describes how to configure PoE in the Web interface. You can also configure this using the table ini file parameter, POETable or CLI command, configure system/poe. Version 6.8 Mediant 800B MSBR...
  • Page 126 Mediant 800B MSBR  To configure PoE: Open the Power Over Ethernet Settings page (Configuration tab > System menu > Power over Ethernet Settings). Figure 15-1: Power Over Ethernet Settings Page Select the 'Index' radio button corresponding to the required LAN port.
  • Page 127 Part IV General VoIP Configuration...

  • Page 129: Network

    Figure 16-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 800B MSBR...

  • Page 130: Configuring Ip Network Interfaces

    Mediant 800B MSBR Table 16-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 131 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 800B MSBR...
  • Page 132 Mediant 800B 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 133 (Optional) Defines the primary DNS server's IP address (in dotted- CLI: primary-dns decimal notation), which is used for translating domain names into [InterfaceTable_PrimaryDNSS IP addresses for the interface. erverIPAddress] By default, no IP address is defined. Version 6.8 Mediant 800B MSBR...
  • Page 134 Mediant 800B 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 [InterfaceTable_SecondaryDN names into IP addresses for the interface. SServerIPAddress] By default, no IP address is defined.

  • Page 135: 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 800B MSBR...

  • Page 136: Networking Configuration Examples

    Mediant 800B MSBR 16.2.3 Networking Configuration Examples This section provides configuration examples of networking interfaces. 16.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 137: 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 Version 6.8 Mediant 800B MSBR...

  • Page 138: Voip Interfaces With Multiple Default Gateways

    Mediant 800B MSBR • Layer-3 QoS values are assigned: ♦ 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 139: 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 800B MSBR...

  • Page 140: Configuration Example Of Static Ip Routes

    Mediant 800B MSBR Table 16-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 141: Troubleshooting The Routing Table

    The IP address specified in the 'Gateway' field is unreachable from the IP network interface associated with the static route.  The same destination is configured in two different static routes.  More than 30 static routes have been configured. Version 6.8 Mediant 800B MSBR...

  • Page 142: Configuring Quality Of Service

    Mediant 800B MSBR Note: If a static route is required to access OAMP applications (for remote management, for example) and the route is not configured correctly, the route is not added and the device is not accessible remotely. To restore connectivity, the device must be accessed locally from the OAMP subnet and the required routes be configured.
  • Page 143 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. [DiffServToVlanPriority_DiffServ] VLAN Priority Defines the VLAN priority level. CLI: vlan-priority The valid value is 0 to 7. [DiffServToVlanPriority_VlanPriority] Version 6.8 Mediant 800B MSBR...

  • Page 144: Dns

    Mediant 800B MSBR Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS. Figure 16-6: QoS Settings Page - Differentiated Services 16.5 You can use the device's embedded domain name server (DNS) or an external, third-party DNS to translate domain names into IP addresses. This is useful if domain names are used as the destination in call routing.

  • Page 145: Configuring The Internal Srv Table

    16.5.2 Configuring the Internal SRV Table The Internal SRV table resolves host names to DNS A-Records. Three different A-Records can be assigned to each host name, where each A-Record contains the host name, priority, weight, and port. Version 6.8 Mediant 800B MSBR...
  • Page 146 Mediant 800B MSBR Note: If you configure the Internal SRV table, the device initially attempts to resolve a domain name using this table. If the domain is not configured in the table, the device performs a Service Record (SRV) resolution using an external DNS server, configured in the Interface table (see ''Configuring IP Network Interfaces'' on page 130).

  • Page 147: Open Solution Network (Osn) Server

    When set to 0 (default), the OSN uses the OAMP VLAN ID. When set to any other value, it specifies a VLAN configured in the Ethernet Device table (see ''Configuring Underlying Ethernet Devices'' on page 129), which is assigned to a Media and/or Control application in the Interface table. Version 6.8 Mediant 800B MSBR...

  • Page 148: Disabling Internal Switch Port For Osn

    Mediant 800B MSBR 16.6.2 Disabling Internal Switch Port for OSN You can enable (default) or disable the Ethernet port of the device's internal switch that interfaces with the OSN. You can view the port status (Up or Down) by running the...

  • Page 149: Network Address Translation Support

    The primary advantages of NAT include (1) reduction in the number of global IP addresses required in a private network (global IP addresses are only used to connect to the Internet) and (2) better network security by hiding the internal architecture. Version 6.8 Mediant 800B MSBR...

  • Page 150: Device Located Behind Nat

    Mediant 800B MSBR The design of SIP creates a problem for VoIP traffic to pass through NAT. SIP uses IP addresses and port numbers in its message body. However, the NAT server is unable to modify the SIP messages and thus, can’t change local addresses to global addresses.

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

    You can also configure Bandwidth Profiles using the table ini file parameter, NATTranslation or CLI command, voip-network NATTranslation.  To configure NAT translation rules: Open the NAT Translation Table page (Configuration tab > VoIP menu > VoIP Network > NAT Translation Table). Version 6.8 Mediant 800B MSBR...
  • Page 152 Mediant 800B MSBR Click Add; the following dialog box appears: Figure 16-12: NAT Translation Table Page Configure a NAT translation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.

  • Page 153: Remote Ua Behind Nat

    To resolve this NAT traversal problem, the device offers the following features:  First Incoming Packet Mechanism - see ''First Incoming Packet Mechanism'' on page  RTP No-Op packets according to the avt-rtp-noop draft - see ''No-Op Packets'' on page Version 6.8 Mediant 800B MSBR...
  • Page 154 Mediant 800B MSBR The figure below illustrates a typical network architecture where the remote UA is located behind NAT: Figure 16-13: Remote UA behind NAT 16.8.2.2.1 First Incoming Packet Mechanism In scenarios where the remote user agent (UA) resides behind a NAT server, it’s possible that the device, if not configured for NAT traversal, will send the media (RTP, RTCP and T.38) streams to an invalid IP address / UDP port (i.e., private IP address:port of UA and...
  • Page 155 T.38 No-Op: T.38 No-Op packets are sent only while a T.38 session is activated. Sent packets are a duplication of the previously sent frame (including duplication of the sequence number). Note: Receipt of No-Op packets is always supported. Version 6.8 Mediant 800B MSBR...

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

    16.9 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 157 'Timeout To Relatch RTCP' ♦ 'Fax Relay Rx/Tx Timeout' Click Submit, and then save ("burn") your settings to flash memory. For a detailed description of the robust media parameters, see ''General Security Parameters'' on page 794. Version 6.8 Mediant 800B MSBR...

  • Page 158: Multiple Routers Support

    Mediant 800B MSBR 16.10 Multiple Routers Support Multiple routers support is designed to assist the device when it operates in a multiple routers network. The device learns the network topology by responding to Internet Control Message Protocol (ICMP) redirections and caches them as routing rules (with expiration time).

  • Page 159: 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 800B MSBR...
  • Page 160 Mediant 800B 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 17-1: Firewall Settings Page - Add Record Configure a Firewall rule according to the parameters described in the table below.
  • Page 161 The list displays interface names as defined in the Interface table [AccessList_Interface_x] in ''Configuring IP Network Interfaces'' on page 130. Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. Version 6.8 Mediant 800B MSBR...
  • Page 162 Mediant 800B MSBR Parameter Description [AccessList_Packet_Size] 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 163: 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 800B MSBR...

  • Page 164: Intrusion Detection System

    Mediant 800B MSBR 17.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 165: 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 17-4: IDS Policy Table with Default Rules Version 6.8 Mediant 800B MSBR...
  • Page 166 Mediant 800B MSBR Click Add; the following dialog box appears: Figure 17-5: IDS Policy Table - Add Record Configure an IDS Policy name according to the parameters described in the table below. Click Submit. Table 17-3: IDS Policy Table Parameter Descriptions...
  • Page 167 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 545)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response) Version 6.8 Mediant 800B MSBR...
  • Page 168 Mediant 800B 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 169: 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 800B MSBR...
  • Page 170 Mediant 800B 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 171: Viewing Ids Alarms

    # show voip security ids active-alarm match <IDS Match Policy ID> rule <IDS Rule ID> The IP address is displayed only if the 'Threshold Scope' parameter is set to IP or IP+Port; otherwise, only the alarm is displayed. Version 6.8 Mediant 800B MSBR...
  • Page 172 Mediant 800B MSBR  To view the blacklist: # show voip security ids blacklist active For example: Active blacklist entries: 10.33.5.110(NI:0) remaining 00h:00m:10s in blacklist Where SI is the SIP Interface and NI is the network interface. The device also sends IDS notifications and alarms in Syslog messages to a Syslog server.

  • Page 173: Media

    • 'Voice Volume' (VoiceVolume) - Defines the voice gain control (in decibels) of the transmitted signal. • 'Input Gain' (InputGain) - Defines the PCM input gain control (in decibels) of the received signal. Click Submit. Version 6.8 Mediant 800B MSBR...

  • Page 174: Silence Suppression (Compression)

    Mediant 800B MSBR 18.1.2 Silence Suppression (Compression) Silence suppression (compression) is a method for conserving bandwidth on VoIP calls by not sending packets when silence is detected. The device uses its VAD feature to detect periods of silence in the voice channel during an established call. When silence is detected, it stops sending packets in the channel.
  • Page 175 ECHybridLoss - defines the four-wire to two-wire worst-case Hybrid loss • ECNLPMode - defines the echo cancellation Non-Linear Processing (NLP) mode • EchoCancellerAggressiveNLP - enables Aggressive NLP at the first 0.5 second of the call Version 6.8 Mediant 800B MSBR...

  • Page 176: Fax And Modem Capabilities

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

  • Page 177: Fax/Modem Operating Modes

    You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). This parameter does not affect the actual transmission rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). Version 6.8 Mediant 800B MSBR...
  • Page 178 Mediant 800B MSBR When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders.
  • Page 179 RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...

  • Page 180: Fax / Modem Transport Mode

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

  • Page 181: Fax/Modem Bypass Mode

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

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

    Definitions > General Parameters), set the 'Fax Signaling Method' parameter to No Fax (IsFaxUsed = 0). In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Version 6.8 Mediant 800B MSBR...

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

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

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

    Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, V34FaxTransportType to 2 (Bypass). Version 6.8 Mediant 800B MSBR...

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

    Mediant 800B MSBR 18.2.3.2 Relay Mode for T.30 and V.34 Faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode.  To use T.38 mode for V.34 and T.30 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Relay (FaxTransportMode = 1).

  • Page 187: Modem Relay

    SIP INVITE and 200 OK, using the SDP body according to the USA Department of Defense (DoD) UCR-2008, Change 2 specification. This eliminates the need for sending a re-INVITE to negotiate V.150.1. The device sends an INVITE’s SDP offer in a Version 6.8 Mediant 800B MSBR...

  • Page 188: 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 189: Support

    SDP offer containing G.729 and “regular” G.711 coders, it sends an SDP answer containing G.729 and G.711 VBD coders, allowing subsequent bypass (passthrough) sessions if fax / modem signals are detected during the call. Version 6.8 Mediant 800B MSBR...

  • Page 190: Fax Transmission Behind Nat

    Mediant 800B MSBR 18.2.7 Fax Transmission behind NAT The device supports transmission from fax machines (connected to the device) located inside (behind) a Network Address Translation (NAT). Generally, the firewall blocks T.38 (and other) packets received from the WAN, unless the device behind the NAT sends at least one IP packet from the LAN to the WAN through the firewall.

  • Page 191: Comfort Noise Generation

    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: Figure 18-4: Comfort Noise Parameter in RTP/RTCP Settings Page Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Version 6.8 Mediant 800B MSBR...

  • Page 192: Dual-Tone Multi-Frequency Signaling

    Mediant 800B MSBR Click Submit. Note: This feature is applicable only to the Gateway application. 18.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 18.3.3.1 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint.

  • Page 193: Configuring Rfc 2833 Payload

    RTP/RTCP Settings). The relevant parameters are listed under the 'General Settings' group, as shown below: Figure 18-5: RFC 2833 Payload Parameters in RTP/RTCP Settings Page Configure the following parameters: • 'RTP Redundancy Depth' (RTPRedundancyDepth) - enables the device to generate RFC 2198 redundant packets. Version 6.8 Mediant 800B MSBR...

  • Page 194: Configuring Rtp Base Udp Port

    Mediant 800B MSBR • 'Enable RTP Redundancy Negotiation' (EnableRTPRedundancyNegotiation) - enables the device to include the RTP redundancy dynamic payload type in the SDP, according to RFC 2198. • 'RFC 2833 TX Payload Type' (RFC2833TxPayloadType) - defines the Tx RFC 2833 DTMF relay dynamic payload type.

  • Page 195: Configuring Ip Media Settings

    'AGC Minimum Gain' (AGCMinGain) - Defines the minimum gain (in dB) by the AGC when activated. • 'AGC Maximum Gain' (AGCMaxGain) - Defines the maximum gain (in dB) by the AGC when activated. • 'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. Version 6.8 Mediant 800B MSBR...

  • Page 196: Configuring Various Codec Attributes

    Mediant 800B MSBR When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. This parameter can either be the global parameter or per IP Profile. Click Submit. 18.5 Configuring Various Codec Attributes The following codec attribute settings can be configured in the General Media Settings page: ...

  • Page 197: Configuring Media (Srtp) Security

    'Encryption On Transmitted RTCP Packets'. When the device is the answering side, the device adjusts these parameters according to the remote offering. Unsupported session parameters are ignored, and do not cause a call failure. Below is an example of crypto attributes usage: a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:PsKoMpHlCg+b5X0YLuSvNrImEh/dAe Version 6.8 Mediant 800B MSBR...
  • Page 198 Mediant 800B MSBR a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:IsPtLoGkBf9a+c6XVzRuMqHlDnEiAd The device also supports symmetric MKI negotiation, whereby it can be configured to forward the MKI size received in the SDP offer crypto line in the SDP answer crypto line. To configure the device's mode of operation if negotiation of the cipher suite fails, use the 'Media Security Behavior' parameter.

  • Page 199: Services

    • For the maximum number of concurrent sessions that the device can record, contact your AudioCodes sales representative. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons.
  • Page 200 Mediant 800B MSBR The siprec protocol specifies the use of SIP, SDP, and RTP to establish a Recording Session (RS) from the Session Recording Client (SRC), which is on the path of the Communication Session (CS), to a Session Recording Server (SRS) at the recording equipment.
  • Page 201 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 a=ptime:20 a=sendonly a=label:2 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 Version 6.8 Mediant 800B MSBR...

  • Page 202: Enabling Sip-Based Media Recording

    Mediant 800B MSBR --boundary_ac1fffff85b Content-Type: application/rs-metadata Content-Disposition: recording-session <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52">...

  • Page 203: Configuring Sip Recording Routing Rules

    RTP, or set to the SRTP leg if recording is required to be SRTP. Recorded Source Prefix Defines calls to record based on source number or CLI: recorded-src-prefix URI. [SIPRecRouting_RecordedSourcePrefix] Version 6.8 Mediant 800B MSBR...

  • Page 204: Configuring Sip User Part For Srs

    Mediant 800B MSBR Parameter Description Recorded Destination Prefix Defines calls to record based on destination CLI: recorded-dst-prefix number or URI. [SIPRecRouting_RecordedDestinationPrefix] Peer IP Group ID Defines the peer IP Group that is participating in CLI: peer-ip-group-id the call. [SIPRecRouting_PeerIPGroupID] Caller...

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

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

  • Page 206: Radius Authentication

    Mediant 800B MSBR 19.2 RADIUS Authentication You can enhance security for your device by implementing Remote Authentication Dial-In User Service (RADIUS - RFC 2865) for authenticating multiple management user accounts of the device’s embedded Web and Telnet (CLI) servers. Thus, RADIUS also prevents unauthorized access to your device.
  • Page 207 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 208: Configuring Radius Authentication

    Mediant 800B MSBR 19.2.2 Configuring RADIUS Authentication The following procedure describes how to configure the RADIUS feature in the Web interface. For a detailed description of the RADIUS parameters, see ''RADIUS Parameters'' on page 1007. Note: By default, the device communicates with the RADIUS server through the OAMP network interface.

  • Page 209: Securing Radius Communication

    To configure the device to use HTTPS, set the 'Secured Web Connection (HTTPS)' parameter to HTTPS Only, in the WEB Security Settings page (Configuration tab > System menu > Management > WEB Security Settings). Version 6.8 Mediant 800B MSBR...

  • Page 210: Authenticating Radius In The Url

    Mediant 800B MSBR 19.2.4 Authenticating RADIUS in the URL RADIUS authentication is typically done after the user accesses the Web interface by entering only the device's IP address in the Web browser's URL field (for example, http://10.13.4.12/), and then entering the username and password credentials in the Web interface login screen.
  • Page 211 Local users database (Web Users table) for authenticating users instead of the LDAP server (for example, when a communication problem occurs with the server). For more information, see ''Configuring Local Database for Management User Authentication'' on page 223. Version 6.8 Mediant 800B MSBR...

  • Page 212: Enabling The Ldap Service

    Mediant 800B MSBR 19.3.1 Enabling the LDAP Service Before you can configure LDAP support, you need to enable the LDAP service.  To enable LDAP: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings).
  • Page 213 Note: If the response time expires, you can configure the device to use its local database (Web Users table) for authenticating the user. For more information, see ''Configuring Local Database for Management User Authentication'' on page 223. Version 6.8 Mediant 800B MSBR...
  • Page 214 Mediant 800B MSBR Parameter Description LDAP Server Domain Name Defines the domain name (FQDN) of the LDAP server. The CLI: domain-name device tries to connect to the LDAP server according to the IP [LdapConfiguration_LdapConf address listed in the received DNS query. If there is no...
  • Page 215 (Read-only) Displays the connection status with the LDAP server. CLI: connection-status  "Not Applicable" [LdapConfiguration_Connectio  "LDAP Connection Broken" nStatus]  "Connecting"  "Connected" Note: For more information about a disconnected LDAP connection, see your Syslog messages generated by the device. Version 6.8 Mediant 800B MSBR...

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

    Mediant 800B MSBR 19.3.4 Configuring LDAP DNs (Base Paths) per LDAP Server The LDAP Search DN Table table lets you configure LDAP base paths. The table is a "child" of the LDAP Configuration table (see ''Configuring LDAP Servers'' on page 212) and configuration is done per LDAP server.

  • Page 217: Configuring The Ldap Search Filter Attribute

    Configuration table (see ''Configuring LDAP Servers'' on page 212) and configuration is done per LDAP server. For each LDAP server, you can configure up to three table row entries of LDAP group(s) and their corresponding access level. Version 6.8 Mediant 800B MSBR...
  • Page 218 Mediant 800B MSBR Notes: • The Management LDAP Groups table is applicable only to LDAP-based login authentication and authorization queries. • If the LDAP response received by the device includes multiple groups of which the user is a member and you have configured different access levels for some of these groups, the device assigns the user the highest access level.
  • Page 219 Defines the attribute names of the groups in the LDAP server. [MgmntLDAPGroups_Group] The valid value is a string of up to 256 characters. To define multiple groups, separate each group name with a semicolon (;). Version 6.8 Mediant 800B MSBR...

  • Page 220: Configuring Ldap Search Methods

    Mediant 800B MSBR 19.3.7 Configuring LDAP Search Methods You can configure the device's method for searching the LDAP server(s) for the configured DN objects:  DN Search Method between Two LDAP Servers: When two LDAP servers are implemented, the device runs an LDAP query to search for DN object records on both LDAP servers.
  • Page 221 LDAP server again. The following procedure describes how to configure the device's LDAP cache in the Web interface. For a full description of the cache parameters, see ''LDAP Parameters'' on page 1009. Version 6.8 Mediant 800B MSBR...
  • Page 222 Mediant 800B MSBR  To configure the LDAP cache: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 19-13: LDAP Settings Page - Cache Parameters Under LDAP Cache, do the following: From the 'LDAP Cache Service' drop-down list, select Enable to enable LDAP cache.

  • Page 223: Configuring Local Database For Management User Authentication

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

  • Page 224: Ldap-Based Login Authentication Example

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

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

    Mediant 800B MSBR 19.3.11 Active Directory-based Routing for Microsoft Lync Typically, enterprises wishing to deploy the Microsoft® Lync™ Server are faced with a complex, call routing dial plan when migrating users from their existing PBX or IP PBX to the Lync Server platform. As more and more end-users migrate to the new voice system, dialing plan management and PBX link capacity can be adversely impacted.
  • Page 229 Mobile number: If the Lync client (or Mediation Server) is unavailable (e.g., SIP response 404 "Not Found" upon INVITE sent to Lync client), and the PBX / IP PBX is also unavailable, the device routes the call to the user's mobile number (if exists in the AD). Version 6.8 Mediant 800B MSBR...
  • Page 230 Mediant 800B MSBR Alternative route: If the call routing to all the above fails (e.g., due to unavailable destination - call busy), the device can route the call to an alternative destination if an alternative routing rule is configured. "Redundant" route: If the query failed (i.e., no attribute found in the AD), the device uses the routing rule matching the "LDAP_ERR"...

  • Page 231: Configuring Ad-Based Routing Rules

    Lync clients, and mobile), using the LDAP keywords (case-sensitive) in the Destination Username Prefix field: ♦ PRIVATE: Private number ♦ OCS: Lync client number ♦ PBX: PBX / IP PBX number ♦ MOBILE: Mobile number Version 6.8 Mediant 800B MSBR...
  • Page 232 Mediant 800B MSBR ♦ LDAP_ERR: LDAP query failure Configure a routing rule for routing the initial call (LDAP query) to the LDAP server, by setting the 'Destination Type' field to LDAP for denoting the IP address of the LDAP server.

  • Page 233: Querying The Ad For Calling Name

    Notes: • The Calling Name Manipulation Table for Tel-to-IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value. Version 6.8 Mediant 800B MSBR...

  • Page 234: Least Cost Routing

    Mediant 800B MSBR 19.4 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how to configure it. 19.4.1 Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost.
  • Page 235 Index 3 - no Cost Group is assigned, but as the Default Cost parameter is set to Min, it is selected as the cheapest route • Index 4 - Cost Group "B" is only second-matched rule (Index 1 is the first) Version 6.8 Mediant 800B MSBR...

  • Page 236: Configuring Lcr

    Mediant 800B MSBR  Example 3: This example shows how the cost of a call is calculated if the call spans over multiple time bands: Assume a Cost Group, "CG Local" is configured with two time bands, as shown below:...
  • Page 237 1. Therefore, a call of 1 minute cost 7 units. Therefore, for calls under one minute, "Weekend A" carries the lower cost. However, if the average call duration is more than one minute, then "Weekend B" carries the lower cost. Version 6.8 Mediant 800B MSBR...

  • Page 238: Configuring Cost Groups

    Mediant 800B MSBR Parameter Description Default Cost Determines whether routing rules in the Outbound IP Routing CLI: lcr-default-cost table without an assigned Cost Group are considered a higher [RoutingRuleGroups_LCRDefault cost or lower cost route compared to other matched routing Cost] rules that are assigned Cost Groups.

  • Page 239: Configuring Time Bands For Cost Groups

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

  • Page 240: Assigning Cost Groups To Routing Rules

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

  • Page 241: Configuring Call Setup Rules

    SBC IP-to-IP routing - see Configuring SBC IP-to-IP Routing Rules on page  Tel-to-IP routing rules - see Configuring Outbound IP Routing Table on page  IP-to-Tel routing rules - see Configuring Inbound IP Routing Table on page Version 6.8 Mediant 800B MSBR...
  • Page 242 Mediant 800B MSBR If an incoming call matches the characteristics of a routing rule, the device first runs the assigned Call Setup Rules Set ID. The device uses the routing rule to route the call, depending on the result of the Call Setup Rules Set ID: ...
  • Page 243 (attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called number is the same as the number in the attribute "msRTCSIP-PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Version 6.8 Mediant 800B MSBR...
  • Page 244 Mediant 800B MSBR Parameter Description Action Subject Defines the element (header, parameter, or body) upon CLI: action-subject which you want to perform the action. [CallSetupRules_ActionSubject] The valid value is a string of up to 100 characters (case- insensitive). Examples: ...

  • Page 245: Call Setup Rule Examples

    ♦ 'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName • Routing table configuration: A single routing rule is assigned the Call Setup Rule Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 2 Version 6.8 Mediant 800B MSBR...
  • Page 246 Mediant 800B MSBR  Example 3: This example configures the device to route the incoming call according to whether or not the source number of the incoming call also exists in the AD server. The device queries the AD server for the attribute record, "telephoneNumber" whose value is the same as the received source number (e.g., telephoneNumber=4064").

  • Page 247: 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 248: 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 249  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 247.
  • Page 250 Mediant 800B MSBR Table 20-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. CLI: name The valid value is a string of up to 20 characters.
  • Page 251 SEM indicating this change. Note: If the monitored parameter crosses two thresholds at once (e.g., from Green to Red), the device ignores the hysteresis value and reports the call state change to the SEM. Version 6.8 Mediant 800B MSBR...

  • Page 252: Configuring Bandwidth Profiles

    Mediant 800B MSBR Parameter Description Yellow Red Threshold Defines the parameter threshold values between CLI: yellow-red-threshold Yellow (medium quality) and Red (poor quality) states. [QOEColorRules_YellowRedThreshold] The valid threshold values are as follows:  MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10)
  • Page 253 The valid value is a string of up to 20 characters. Egress Audio Bandwidth 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] Version 6.8 Mediant 800B MSBR...
  • Page 254 Mediant 800B MSBR Parameter Description Egress Video Bandwidth Defines the outgoing video traffic threshold (in Kbps). CLI: egress-video-bandwidth [BWProfile_EgressVideoBandwidth] 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).

  • Page 255: Configuring Media Enhancement Profiles

    Web interface. You can also configure Media Enhancement Profiles using other management platforms:  Media Enhancement Profile table: Table ini file parameter, MediaEnhancementProfile or CLI command, configure voip/qoe media-enhancement  Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules or CLI command, configure voip/qoe media-enhancement-rules Version 6.8 Mediant 800B MSBR...
  • Page 256 Mediant 800B MSBR  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Click Add; the following dialog box appears: Figure 20-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below.
  • Page 257 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 800B MSBR...
  • Page 258 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 259: 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 800B MSBR...
  • Page 260 Mediant 800B 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 21-1: Media Realm Page - Add Record Dialog Box Configure the Media Realm according to the parameters described in the table below.
  • Page 261 QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 248. 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 252. Version 6.8 Mediant 800B MSBR...

  • Page 262: Configuring Remote Media Subnets

    Mediant 800B MSBR 21.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 252, respectively.
  • Page 263 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 800B MSBR...

  • Page 264: Configuring Srds

    Mediant 800B MSBR 21.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 265 Media Realms in the 'Media Realm Name' field of the Media Realm table (see ''Configuring Media Realms'' on page 259). Note: If the Media Realm is later deleted from the Media Realm table, this value becomes invalid in the SRD table. Version 6.8 Mediant 800B MSBR...
  • Page 266 Mediant 800B MSBR Parameter Description Media Anchoring Enables the Media Anchoring feature (Anti- CLI: intra-srd-media-anchoring Tromboning) per SRD, whereby RTP (media) flows [SRD_IntraSRDMediaAnchoring] directly between the call parties (i.e., does not traverse the device).  [0] Enable = (Default) RTP traverses the device and each leg uses a different coder or coder parameters.

  • Page 267: Configuring Sip Interfaces

    > SIP Interface Table). Click Add; the following dialog box appears: Configure a SIP Interface according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B MSBR...
  • Page 268 Mediant 800B MSBR Table 21-4: SIP Interface Table Parameter Descriptions Parameter Description Index Defines an index for the new table record. [SIPInterface_Index] 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.
  • Page 269 [SIPInterface_TCPKeepaliveE nable] to check that the connection to the IP entity is available.  [0] Disable (default)  [1] Enable Note: For configuring TCP keepalive, use the following ini file parameters: TCPKeepAliveTime, TCPKeepAliveInterval, and TCPKeepAliveRetry. Version 6.8 Mediant 800B MSBR...

  • Page 270: Configuring Ip Groups

    Mediant 800B MSBR Parameter Description Classification Failure Response Defines the SIP response code that the device sends if a received Type SIP request (OPTIONS, REGISTER, or INVITE) fails the SBC CLI: Classification process. classification_fail_response_typ 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.
  • Page 271 Proxy Set takes precedence. The following procedure describes how to configure IP Groups in the Web interface. You can also configure IP Groups using the table ini file parameter, IPGroup or CLI command, configure voip > control-network ip-group. Version 6.8 Mediant 800B MSBR...
  • Page 272 Mediant 800B MSBR  To configure an IP Group: Open the IP Group Table page (Configuration tab > VoIP menu > VoIP Network > IP Group Table). Click Add; the following dialog box appears: Figure 21-5: IP Group Table - Add Dialog Box Configure an IP Group according to to the parameters described in the table below.
  • Page 273 Proxy Set ID Assigns a Proxy Set ID to the IP Group. All INVITE CLI: proxy-set-id messages destined to this IP Group are sent to the IP [IPGroup_ProxySetId] address configured for the Proxy Set. Notes: Version 6.8 Mediant 800B MSBR...
  • Page 274 Mediant 800B MSBR Parameter Description  The Proxy Set is applicable only to Server-type IP Groups.  The SRD configured for this Proxy Set in the Proxy Set table is automatically assigned to this IP Group (see the 'SRD' field below).
  • Page 275 Message Manipulation rules configured in the Message Manipulations table. The Message Manipulation rule obtains this value from the IP Group, by using the following syntax: param.ipg.<src|dst>.user-defined.<0>. The valid value is a string of up to 30 characters. Version 6.8 Mediant 800B MSBR...
  • Page 276 Mediant 800B MSBR Parameter Description For configuring Message Manipulation rules, see ''Configuring SIP Message Manipulation'' on page 299. CLI: Msg-Man-User-Defined-String2 Defines a value for the SIP user part that can be used in [IPGroup_MsgManUserDef2] Message Manipulation rules configured in the Message Manipulations table.
  • Page 277 Upon receipt of the registration message, the device returns a SIP 200 OK to the client. Version 6.8 Mediant 800B MSBR...
  • Page 278 Mediant 800B MSBR Parameter Description Notes:  This parameter is applicable only to the IP-to-IP application.  This parameter is applicable only to User-type IP Groups. Serving IP Group ID If configured, INVITE messages initiated from the IP Group CLI: serving-ip-group-id are sent to this Serving IP Group (range 1 to 9).
  • Page 279 [2]. SBC Client Forking Mode Defines call forking of INVITE messages to up to five CLI: enable-sbc-client-forking separate SIP outgoing legs for User-type IP Groups. This occurs if multiple contacts are registered under the same Version 6.8 Mediant 800B MSBR...
  • Page 280 Mediant 800B MSBR Parameter Description [IPGroup_EnableSBCClientForking] AOR in the device's registration database.  [0] Sequential = (Default) Sequentially sends the INVITE to each contact. If there is no answer from the first contact, it sends the INVITE to the second contact, and so on until a contact answers.
  • Page 281 Defines the shared password for authenticating the IP CLI: password Group, when the device acts as an Authentication server. IPGroup_Password] The valid value is a string of up to 51 characters. By default, no password is defined. Version 6.8 Mediant 800B MSBR...

  • Page 282: Configuring Proxy Sets

    Mediant 800B MSBR Parameter Description Notes:  This parameter is applicable only to Server-type IP Groups and when the 'Authentication Mode' parameter is set to SBC as Server (i.e., authentication of servers).  To specify the SIP request types (e.g., INVITE) that must be challenged by the device, use the 'Authentication Method List' parameter.
  • Page 283 The address can be defined as an IP address in dotted- [ProxyIp_IpAddress] decimal notation (e.g., 201.10.8.1) or FQDN. You can also specify the port using the following format:  IPv4 address: <IP address>:<port> (e.g., 201.10.8.1:5060)  IPv6 address: <[IPV6 address]>:<port> (e.g., Version 6.8 Mediant 800B MSBR...
  • Page 284 Mediant 800B MSBR Parameter Description [2000::1:200:200:86:14]:5060) Transport Type Defines the transport type for communicating with the CLI: voip-network proxy-ip > transport-type Proxy server. [ProxyIp_TransportType]  [0] UDP  [1] TCP  [2] TLS  [-1] = Undefined Note: If this parameter is not configured, the setting of the global parameter, SIPTransportType is used.
  • Page 285  [1] Round Robin = A list of all possible Proxy IP [ProxySet_ProxyLoadBalancingMethod] addresses is compiled. This list includes all IP addresses per Proxy Set after necessary DNS resolutions (including NAPTR and SRV, if Version 6.8 Mediant 800B MSBR...
  • Page 286 Mediant 800B MSBR Parameter Description configured). After this list is compiled, the Proxy Keep-Alive mechanism (according to parameters EnableProxyKeepAlive and ProxyKeepAliveTime) tags each entry as 'offline' or 'online'. Load balancing is only performed on Proxy servers that are tagged as 'online'. All outgoing messages are equally distributed across the list of IP addresses.
  • Page 287 Proxy Set according to its IP address, port, and transport type. Notes:  This parameter is applicable only if the IP Group table's parameter, 'Classify by Proxy Set' is set to Enable.  This parameter is applicable only to the SBC application. Version 6.8 Mediant 800B MSBR...
  • Page 288 Mediant 800B MSBR Parameter Description Web/EMS: TLS Context Index Assigns a TLS Context (SSL/TLS certificate) to the CLI: tls-context-index Proxy Set. The TLS Context is assigned by index [ProxySet_TLSContext] number, as configured in the TLS Contexts table.  Incoming calls: If the 'Transport Type' parameter...

  • Page 289: Assign Wan Interface To Voip Traffic

    Click Submit, and then reset the device for your setting to take effect. 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"): Version 6.8 Mediant 800B MSBR...
  • Page 290 Mediant 800B MSBR Open the SIP Interface Table page (see ''Configuring SIP Interfaces'' on page 267) and configure SIP interfaces on the WAN interface. Figure 21-8: Assigning SIP Interface to WAN Open the Media Realm Table page (see ''Configuring Media Realms'' on page 259) and configure media interfaces on the WAN interface.

  • Page 291: 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 800B MSBR...
  • Page 292 Mediant 800B 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 293 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 and IP-to-IP application. [Account_ApplicationType]  [2] SBC = SBC application. Version 6.8 Mediant 800B MSBR...

  • Page 294: Regular Registration Mode

    Mediant 800B MSBR 22.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 295 User's Manual 22. SIP Definitions The figure below illustrates an incoming call using GIN: Version 6.8 Mediant 800B MSBR...

  • Page 296: Configuring Proxy And Registration Parameters

    Mediant 800B MSBR 22.3 Configuring Proxy and Registration Parameters The Proxy & Registration page allows you to configure the Proxy server and registration parameters. For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 763.

  • Page 297: 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 800B 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 298 • 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 299: Configuring Sip Message Manipulation

    Manipulation on SIP message type (Method, Request/Response, and Response type)  Addition of new SIP headers  Removal of SIP headers ("black list")  Modification of SIP header components such as values, header values (e.g., URI Version 6.8 Mediant 800B MSBR...
  • Page 300 Mediant 800B MSBR value of the P-Asserted-Identity header can be copied to the From header), call's parameter values  Deletion of SIP body (e.g., if a message body is not supported at the destination network this body is removed) ...
  • Page 301 Figure 22-3: Message Manipulations Table - Add Record Dialog Box Configure a Message Manipulation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B MSBR...
  • Page 302 Mediant 800B MSBR An example of configured message manipulation rules are shown in the figure below: Figure 22-4: Message Manipulations Page  Index 0: Adds the suffix ".com" to the host part of the To header.  Index 1: Changes the user part of the From header to the user part of the P-Asserted- ...
  • Page 303 The default value is a string (case-insensitive) in the following syntax:  string/<message-element>/<call-param> +  string/<message-element>/<call-param> For example:  'itsp.com'  header.from.url.user  param.call.dst.user  param.call.dst.host + '.com'  param.call.src.user + '<' + header.from.url.user + '@' + header.p-asserted-id.url.host + '>' Version 6.8 Mediant 800B MSBR...

  • Page 304: Configuring Sip Message Policy Rules

    Mediant 800B MSBR Parameter Description Note: Only single quotation marks must be used. Row Role Determines which condition must be used for the CLI: row-role rule of this table row. [MessageManipulations_RowRole]  [0] Use Current Condition = The condition entered in this row must be matched in order to perform the defined action (default).
  • Page 305 Note: The device supports up to 20 SIP Record-Route headers that can be received in a SIP INVITE request or a 200 OK response. If it receives more than this, it responds with a SIP 513 'Message Too Large' response. Version 6.8 Mediant 800B MSBR...
  • Page 306 Mediant 800B MSBR Parameter Description Max Num Bodies Defines the maximum number of bodies (e.g., SDP) in the CLI: max-num-bodies SIP message. [MessagePolicy_MaxNumBodies] The valid value is any number up to 8. The default is 8. Send Rejection Determines whether the device sends a 400 "Bad CLI: send-rejection Request"...

  • Page 307: Coders And Profiles

    You can also configure this table using the table ini file parameter, CodersGroup0 or CLI command, configure voip > coders-and-profiles coders-group.  To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 23-1: Coders Table Page Version 6.8 Mediant 800B MSBR...
  • Page 308 Mediant 800B MSBR Configure coders according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 23-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder.
  • Page 309 30 (default), 60, 90, 120 silk-nb 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] Version 6.8 Mediant 800B MSBR...

  • Page 310: Configuring Coder Groups

    Mediant 800B MSBR Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression T.38 Over RTP Dynamic (90 - 127); Default 106 23.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).

  • Page 311: 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 800B MSBR...
  • Page 312 Mediant 800B 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 23-4: Tel Profile Table Parameters and Corresponding Global Parameters...
  • Page 313 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 EnableEchoCanceller CLI: echo-canceller [TelProfile_EnableEC] Web: Enable AGC EnableAGC CLI: enable-agc [TelProfile_EnableAGC] Version 6.8 Mediant 800B MSBR...

  • Page 314: Configuring Ip Profiles

    Mediant 800B MSBR Tel Profile Parameter Global Parameter Web: EC NLP Mode ECNLPMode CLI: echo-canceller-nlp-mode [TelProfile_ECNlpMode] Analog Web: Enable Polarity Reversal EnableReversalPolarity CLI: polarity-rvrsl [TelProfile_EnableReversePolarity] Web: Enable Current Disconnect EnableCurrentDisconnect CLI: current-disconnect [TelProfile_EnableCurrentDisconnect] Web: MWI Analog Lamp MWIAnalogLamp CLI: mwi-analog-lamp...
  • Page 315 Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Configure an IP Profile according to the parameters described in the table below. Version 6.8 Mediant 800B MSBR...
  • Page 316 Mediant 800B MSBR Click Submit, and then save ("burn") your settings to flash memory. Table 23-5: IP Profile Settings Table Parameter Descriptions Parameter Description Common Web: Index Defines an index number for the new table record. [IpProfile_Index] Web: Profile Name Defines an arbitrary name to easily identify the IP Profile.
  • Page 317 Web: Echo Canceler Enables echo cancellation (i.e., echo from voice calls is CLI: echo-canceller removed). [IpProfile_EnableEchoCanceller]  [0] Disable  [1] Line (default)  [2] Acoustic Notes:  For more information on the Echo Cancellation feature, Version 6.8 Mediant 800B MSBR...
  • Page 318 Mediant 800B MSBR Parameter Description see Echo Cancellation on page 174.  The corresponding global parameter is EnableEchoCanceller. Web: Disconnect on Broken Connection Enables the device to release the call if RTP packets are CLI: disconnect-on-broken-connection not received within a user-defined timeout, configured by [IpProfile_DisconnectOnBrokenConne the BrokenConnectionEventTimeout parameter.
  • Page 319 SRTP-to-SRTP flows or override the MKI size during negotiation. This can be done on the inbound or outbound leg.  The corresponding global parameter is SRTPTxPacketMKISize. Web: Reset SRTP Upon Re-key Enables synchronization of the SRTP state between the Version 6.8 Mediant 800B MSBR...
  • Page 320 Mediant 800B MSBR Parameter Description CLI: reset-srtp-upon-re-key device and a server when a new SRTP key is generated [IpProfile_ResetSRTPStateUponRekey upon a SIP session expire. This feature ensures that the roll-over counter (ROC), one of the parameters used in the SRTP encryption/decryption process of the SRTP packets is synchronized on both sides for transmit and receive packets.
  • Page 321 This option is useful, for example, when the originating fax is located behind a firewall that blocks incoming T.38 packets on ports that have not yet received T.38 packets from the internal network (i.e., originating fax). Version 6.8 Mediant 800B MSBR...
  • Page 322 Mediant 800B MSBR Parameter Description To also send a Re-INVITE message upon detection of a fax CNG tone in this mode, set the parameter 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.
  • Page 323 PI is set to 1 or 8 in the received Proceeding, Alerting, or Progress PRI messages. See also the ProgressIndicator2IP parameter, which if set to 1 or 8, the device behaves as if it received the ISDN Version 6.8 Mediant 800B MSBR...
  • Page 324 Mediant 800B MSBR Parameter Description messages with the PI.  CAS: See the ProgressIndicator2IP parameter.  ISDN: Sending a 183 response depends on the ISDN PI. It is sent only if PI is set to 1 or 8 in the received Proceeding or Alerting PRI messages.
  • Page 325 (as shown above) from the SIP entity, it responds with SRTP (RTP/SAVP) if the EnableMediaSecurity parameter is set to 1. If SRTP is not supported (i.e., EnableMediaSecurity is set to 0), it responds with RTP. Version 6.8 Mediant 800B MSBR...
  • Page 326 Mediant 800B MSBR Parameter Description  If two 'm=' lines are received in the SDP offer, the device prefers the SAVP (secure audio video profile), regardless of the order in the SDP. Notes:  This parameter is applicable only when the EnableMediaSecurity parameter is set to 1.
  • Page 327 SendIEonTG parameter .  You can configure different IE data for Trunk Groups by configuring this parameter for different IP Profiles and then assigning the required IP Profile ID in the Inbound IP Routing table (PSTNPrefix). Version 6.8 Mediant 800B MSBR...
  • Page 328 Mediant 800B MSBR Parameter Description  This feature is similar to that of the EnableISDNTunnelingIP2Tel parameter. If both parameters are configured, the EnableISDNTunnelingIP2Tel parameter takes precedence.  The corresponding global parameter is AddIEinSetup. Web: QSIG Tunneling Enables QSIG tunneling-over-SIP for this SIP entity. This...
  • Page 329 (such as Extension coders). Notes:  To implement transcoding, you must configure the number of required DSP channels for transcoding (using the MediaChannels parameter). Each transcoding session uses two DSP resources.  The corresponding global parameter is TranscodingMode. Version 6.8 Mediant 800B MSBR...
  • Page 330 Mediant 800B MSBR Parameter Description Allowed Media Types Defines media types permitted for this SIP entity. The CLI: sbc-allowed-media-types media type appears in the SDP 'm=' line (e.g., 'm=audio'). [IPProfile_SBCAllowedMediaTypes] The device permits only media types that appear in both the SDP offer and this configured list.
  • Page 331 [0] As Is = (Default) The device does not attempt to interwork any special DTMF method.  [1] In Band  [2] INFO - Cisco  [3] INFO - Nortel  [4] INFO - Lucent = INFO, Korea Version 6.8 Mediant 800B MSBR...
  • Page 332 Mediant 800B MSBR Parameter Description Note: If the device interworks between different DTMF methods and one of the methods is in-band DTMF packets (RFC 2833), detection and generation of DTMF methods requires DSP resources. Web: P-Asserted-Identity Defines the device's handling of the SIP P-Asserted- CLI: sbc-assert-identity Identity header for this SIP entity.
  • Page 333 Web: PRACK Mode Defines the device's handling of SIP PRACK messages CLI: sbc-prack-mode for this SIP entity. [IpProfile_SbcPrackMode]  [1] Optional = PRACK is optional. If required, the device performs the PRACK process on behalf of the Version 6.8 Mediant 800B MSBR...
  • Page 334 Mediant 800B MSBR Parameter Description SIP entity.  [2] Mandatory = PRACK is required for this SIP entity. Calls from endpoints that do not support PRACK are rejected. Calls destined to these endpoints are also required to support PRACK. ...
  • Page 335 Redirect server in the LAN, and the Redirect server replies with a SIP 3xx response to a PBX in the LAN in the Contact header. If the device sends Version 6.8 Mediant 800B MSBR...
  • Page 336 Mediant 800B MSBR Parameter Description this response as is (i.e., with the original Contact header), the FEU is unable to reach the new destination.  [0] Transparent = (Default) The device forwards the received SIP 3xx response as is, without changing the Contact header (i.e.,transparent handling).
  • Page 337 Defines the duration (in seconds) of the periodic CLI: sbc-usr-reg-time registrations that occur between the users of this SIP [IpProfile_SBCUserRegistrationTime] entity and the device (the device responds with this value to the user in the Expires header). Version 6.8 Mediant 800B MSBR...
  • Page 338 Mediant 800B MSBR Parameter Description The valid range is 0 to 2,000,000 seconds. The default is 0. When set to 0, the device does not change the Expires header's value received in the user’s REGISTER request. If no Expires header is received in the REGISTER message and this parameter is set to 0, the Expires header's value is set to 180 seconds, by default.
  • Page 339 [0] Transparent (default) = Forward as is. [IpProfile_SBCUseSilenceSupp]  [1] Add = Enable silence suppression for each relevant coder listed in the SDP.  [2] Remove = Disable silence suppression for each relevant coder listed in the SDP. Version 6.8 Mediant 800B MSBR...
  • Page 340 Mediant 800B MSBR Parameter Description Web: Play RBT To Transferee Enables the device to play a ringback tone to the CLI: sbc-play-rbt-to-xferee transferred party (transferee) during a blind call transfer, [IpProfile_SBCPlayRBTToTransferee] for this SIP entity (which does not support such a tone generation during call transfer).
  • Page 341 Minimum Delay' (DJBufMinDelay) and 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed.  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. Version 6.8 Mediant 800B MSBR...
  • Page 342 Mediant 800B MSBR Parameter Description Web: Remote Renegotiate on Fax Enables local handling of fax detection and negotiation by Detection the device on behalf of the SIP entity (to which the IP Profile is assigned). This applies to faxes sent immediately CLI: sbc-rmt-renegotiate-on-fax-detect upon the establishment of a voice channel (i.e., after 200...
  • Page 343 Part V Gateway Application...

  • Page 345: Introduction

    Mediant 800B MSBR 24. Introduction Introduction This section describes configuration of the Gateway application. The Gateway application refers to IP-to-Tel (PSTN for digital interfaces) call routing and vice versa. Notes: • The IP-to-IP application has been superseded by the SBC application.
  • Page 346 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 347: Digital Pstn

    Mediant 800B MSBR 25. Digital PSTN Digital PSTN This section describes the configuration of the public switched telephone network (PSTN) related parameters. 25.1 Configuring Trunk Settings The Trunk Settings page allows you to configure the device's trunks. This includes selecting the PSTN protocol and configuring related parameters.
  • Page 348 Mediant 800B 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 349 Mediant 800B MSBR 25. Digital PSTN Note: If the Trunk scroll bar displays all available trunks, the scroll bar buttons are unavailable. After you have selected a trunk, the following is displayed: • The read-only 'Module ID' field displays the module number to which the trunk belongs.

  • Page 350: Tdm And Timing

    Mediant 800B MSBR 25.2 TDM and Timing This section describes the configuration of the TDM and clock timing parameters. 25.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 907.

  • Page 351: Recovering Clock From Pstn Line Interface

    Mediant 800B MSBR 25. Digital PSTN 25.2.2.1 Recovering Clock from PSTN Line Interface This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line interface. For a full description of the clock parameters, see ''PSTN Parameters'' on page 907.

  • Page 352: Configuring Cas State Machines

    Mediant 800B MSBR 25.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 353 Mediant 800B MSBR 25. Digital PSTN Table 25-1: CAS State Machine Parameters Description Parameter Description Generate Digit On Time Generates digit on-time (in msec). [CasStateMachineGenerateDigitOnTi The value must be a positive value. The default is -1 (use value from CAS state machine).

  • Page 354: Configuring Digital Gateway Parameters

    Mediant 800B MSBR 25.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 763.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 355: Tunneling Applications

    Mediant 800B MSBR 25. Digital PSTN 25.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 25.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal...
  • Page 356 Mediant 800B MSBR By utilizing the ‘Profiles’ mechanism (see ''Coders and Profiles'' on page 307), you can configure the TDM Tunneling feature to choose different settings based on a timeslot or groups of timeslots. For example, you can use low-bit-rate vocoders to transport voice and ‘Transparent’...
  • Page 357 Mediant 800B MSBR 25. Digital PSTN [ CodersGroup0 ] FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce; CodersGroup0 0 = g7231; CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume,...

  • Page 358: Dsp Pattern Detector

    Mediant 800B MSBR TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 25.5.1.1 DSP Pattern Detector For TDM tunneling applications, you can use the DSP pattern detector feature to initiate the echo canceller at call start. The device can be configured to support detection of a specific one-byte idle data pattern transmitted over digital E1/T1 timeslots.
  • Page 359 Mediant 800B MSBR 25. Digital PSTN message is ‘application/QSIG’. The device also adds a Content-Disposition header in the following format: Content-Disposition: signal; handling=required. QSIG tunneling is done as follows:  Call setup (originating device): The QSIG Setup request is encapsulated in the SIP INVITE message without being altered.

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

    Mediant 800B MSBR 25.6 ISDN Non-Facility Associated Signaling (NFAS) In regular T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B- channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.

  • Page 361: Working With Dms-100 Switches

    Mediant 800B MSBR 25. Digital PSTN To define an explicit Interface ID for a T1 trunk (that is different from the default), use the following parameters:  ISDNIBehavior_x = 512 (x = 0 to the maximum number of trunks identifying the device's physical trunk) ...

  • Page 362: Creating An Nfas-Related Trunk Configuration

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

  • Page 363: Collecting Isdn Digits And Sending Complete Number In Sip

    Mediant 800B MSBR 25. Digital PSTN ISDN Overlap Dialing with SIP According to RFC 3578'' on page 364) Note: ISDN overlap dialing is applicable to PRI and BRI. 25.7.1 Collecting ISDN Digits and Sending Complete Number in SIP The device can support an overlap dialing mode whereby the device collects the called party number digits from ISDN Q.931 Information messages or DTMF signals, and then...

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

    Mediant 800B MSBR 25.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 The device supports the interworking of ISDN overlap dialing to SIP and vice versa, according to RFC 3578.  Interworking ISDN overlap dialing to SIP (Tel to IP): The device sends collected digits each time it receives them (initially from the ISDN Setup message and then from subsequent Q.931 Information messages) to the IP side, using subsequent SIP...

  • Page 365: Trunk Group

    Mediant 800B MSBR 26. Trunk Group Trunk Group This section describes the configuration of the device's channels, which includes assigning them to Trunk Groups. 26.1 Configuring Trunk Group Table The Trunk Group table lets you configure up to 120 Trunk Groups. A Trunk Group is a logical group of physical trunks and channels.
  • Page 366 Mediant 800B MSBR Table 26-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 367: Configuring Hunt Group Settings

    Mediant 800B MSBR 26. Trunk Group Parameter Description page 367). Trunk Group ID Defines the Trunk Group ID for the specified channels. The CLI: trunk-group-id same Trunk Group ID can be assigned to more than one group [TrunkGroup_TrunkGroupNum] of channels. If an IP-to-Tel call is assigned to a Trunk Group, the IP call is routed to the channel(s) pertaining to that Trunk Group ID.
  • Page 368 Mediant 800B MSBR Table 26-2: Hunt Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_TrunkGroupI Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to CLI: channel-select-mode the channels of the Trunk Group.
  • Page 369 Mediant 800B MSBR 26. Trunk Group Parameter Description  For the second incoming call, the first channel of Trunk 1 is selected.  For the third incoming call, the second channel of Trunk 0 is selected.  [9] Ring to Hunt Group = The device allocates IP-to-Tel calls to all the FXS ports (channels) in the Hunt Group.
  • Page 370 Mediant 800B MSBR Parameter Description by assigning them to a Trunk Group and configuring the Trunk Group registration mode to 'Don't Register'.  [5] Per Account = Registrations are sent (or not) to an IP Group, according to the settings in the Account table (see ''Configuring Registration Accounts'' on page 291).
  • Page 371 Mediant 800B MSBR 26. Trunk Group Parameter Description Gateway Name Defines the host name for the SIP From header in INVITE CLI: gateway-name messages and for the From/To headers in REGISTER [TrunkGroupSettings_GatewayNam requests. Note: If this parameter is not configured, the global parameter, SIPGatewayName is used.
  • Page 372 Mediant 800B MSBR Parameter Description MWI Interrogation Type Defines MWI QSIG-to-IP interworking for interrogating MWI CLI: mwi-interrogation-type supplementary services: [TrunkGroupSettings_MWIInterrogatio  [255] Not Configured nType]  [0] None = Disables the feature.  [1] Use Activate Only = MWI Interrogation messages are not sent and only "passively"...

  • Page 373: Manipulation

    Mediant 800B MSBR 27. Manipulation Manipulation This section describes the configuration of various manipulation processes. 27.1 Configuring General Settings The General Settings page allows you to configure general manipulation parameters. For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 763.
  • Page 374 Mediant 800B MSBR 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. The additional manipulation is performed on the initially manipulated number.
  • Page 375 Mediant 800B MSBR 27. Manipulation  To configure a number manipulation rule: Open the required Number Manipulation page (Configuration tab > VoIP menu > GW and IP to IP > Manipulations > Dest Number IP->Tel, Dest Number Tel->IP, Source Number IP->Tel, or Source Number Tel->IP); the relevant Manipulation table page is displayed.
  • Page 376 Mediant 800B MSBR Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 27-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
  • Page 377 Mediant 800B MSBR 27. Manipulation Parameter Description Asserted-Identity URI host name (instead of the From header). Web: Destination Host Defines the Request-URI host name prefix of the incoming SIP INVITE Prefix message. CLI: dst-host-prefix Notes: [_DestHost]  This parameter is applicable only to the number manipulation tables for IP-to-Tel calls.
  • Page 378 Mediant 800B MSBR Parameter Description 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 CLI: suffix-to-add is 1234, the new number is 123400.

  • Page 379: Manipulating Number Prefix

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

  • Page 380: Sip Calling Name Manipulations

    Mediant 800B MSBR 27.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 381 Mediant 800B MSBR 27. Manipulation  To configure calling name manipulation rules: Open the required calling name manipulations page (Configuration tab > VoIP menu > GW and IP to IP > Manipulations > Calling Name IP->Tel or Calling Name Tel- >IP).
  • Page 382 Mediant 800B MSBR Parameter Description Web: Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. 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 761.

  • Page 383: Configuring Redirect Number Ip To Tel

    Mediant 800B MSBR 27. Manipulation Parameter Description Digits "company:john", the new calling name is "pany:john". CLI: remove-from-left [_RemoveFromLeft] Web: Stripped Digits From Defines the number of characters to remove from the right of the calling Right name. For example, if you enter 3 and the calling name is EMS: Number Of Stripped "company:name", the new name is "company:n".
  • Page 384 Mediant 800B MSBR Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
  • Page 385 Mediant 800B MSBR 27. Manipulation Parameter Description Web/EMS: Destination Prefix Defines the destination (called) telephone number prefix. CLI: dst-prefix The default value is the asterisk (*) symbol (i.e., any number). [_DestinationPrefix] For manipulating the diverting and redirected numbers for call diversion, you can use the strings "DN"...
  • Page 386 Mediant 800B MSBR Parameter Description CLI: dst-host-prefix incoming SIP INVITE message. [_DestHost] The default value is the asterisk (*) symbol (i.e., any prefix). Note: This parameter is applicable only to the Redirect Number IP-to- Tel table. Operation (Action) Web: Stripped Digits From...

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

    Mediant 800B MSBR 27. Manipulation Parameter Description Web: NPI Defines the Numbering Plan Indicator (NPI). EMS: Number Plan  [-1] Not Configured = (Default) Value received from PSTN/IP is CLI: npi used [_NumberPlan]  [0] Unknown  [1] E.164 Public ...

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

    Mediant 800B MSBR 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 27.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
  • Page 389 Mediant 800B MSBR 27. Manipulation Note: You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'. In such a configuration, a Tel-to-IP call uses the first matching rule in the table. Table 27-6: Phone Context Table Parameter Description...

  • Page 390: Configuring Release Cause Mapping

    Mediant 800B MSBR 27.8 Configuring Release Cause Mapping The release cause mapping tables let you configure rules to map up to 12 different ISDN ITU-T Q.850 release cause codes (call failure) to SIP response codes, and vice versa. These tables allow you to override the default ISDN-SIP release cause mappings, described in ''Fixed Mapping of ISDN Release Reason to SIP Response'' on page 392 and ''Fixed Mapping of SIP Response to ISDN Release Reason'' on page 391.

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

    Mediant 800B MSBR 27. Manipulation Table 27-7: Release Cause Mapping Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [CauseMapSip2Isdn_Index] [CauseMapIsdn2Sip_Index] Sip Response Defines the SIP response code (e.g., 406). CLI: sip-response [CauseMapSip2Isdn_SipResponse] [CauseMapIsdn2Sip_SipResponse] Q.850 Causes...

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

    Mediant 800B MSBR ISDN Release SIP Response Description Description Reason Too many hops Interworking Address incomplete Invalid number format Ambiguous Unallocated number Busy here User busy Not acceptable here Normal, unspecified Server internal error Temporary failure Not implemented Network out of order...
  • Page 393 Mediant 800B MSBR 27. Manipulation ISDN Release Description Description Reason Response Non-selected user clearing Not found Destination out of order Bad gateway Address incomplete Address incomplete Facility rejected Not implemented Response to status enquiry 501* Not implemented Normal unspecified Temporarily unavailable...

  • Page 394: Reason Header

    Mediant 800B MSBR ISDN Release Description Description Reason Response Invalid transit network selection 502* Bad gateway Invalid message Service unavailable Mandatory information element is 409* Conflict missing Message type non-existent or not 480* Temporarily not available implemented Message not compatible with call state...

  • Page 395: Mapping Pstn Release Cause To Sip Response

    Mediant 800B MSBR 27. Manipulation 27.8.4 Mapping PSTN Release Cause to SIP Response The device's FXO interface interoperates between the SIP network and the PSTN/PBX. This interoperability includes the mapping of PSTN/PBX Call Progress tones to SIP 4xx or 5xx responses for IP-to-Tel calls. The converse is also true - for Tel-to-IP calls, the SIP 4xx or 5xx responses are mapped to tones played to the PSTN/PBX.
  • Page 396 Mediant 800B MSBR Description Private [9] Unknown [0] A private number, but with no further information about the numbering plan. Level 2 Regional [1] Level 1 Regional [2] A private number with a location, e.g., 3932200. PISN Specific [3] Level 0 Regional (local) [4] A private local extension number, e.g., 2200.

  • Page 397: Routing

    Mediant 800B MSBR 28. Routing Routing This section describes the configuration of call routing rules. 28.1 Configuring General Routing Parameters The Routing General Parameters page allows you to configure general routing parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 763.
  • Page 398 Mediant 800B MSBR • Source and destination Request-URI host name prefix  Destination: If the call matches the configured characteristics, the device routes the call to an IP destination. If no characteristics match is found in the table, the call is rejected.
  • Page 399 Mediant 800B MSBR 28. Routing Note: When using a proxy server, you do not need to configure this table, unless you require one of the following: • Fallback (alternative) routing if communication is lost with the proxy server. • IP security, whereby the device routes only received calls whose source IP addresses are defined in this table.
  • Page 400 Mediant 800B MSBR 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. Note: You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table.
  • Page 401 Mediant 800B MSBR 28. Routing  Rule 9 (IP-to-IP rule): If an incoming IP call from Source IP Group 2 with domain.com as source host prefix in its SIP Request-URI, the IP call is sent to IP address 10.33.45.65. Table 28-1: Example of Tel-to-IP Source Phone Number Manipulation Rules...
  • Page 402 Mediant 800B MSBR Parameter Description used.  For number manipulation, see ''Configuring Source/Destination Number Manipulation'' on page 373. 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.
  • Page 403 Mediant 800B MSBR 28. Routing Parameter Description  "LDAP_ERR" = LDAP query failure For more information, see Routing Based on LDAP Active Directory Queries on page 210.  If you want to configure re-routing of ISDN Tel-to-IP calls to fax destinations, you need to enter the value string "FAX"...

  • Page 404: Group And Therefore, This Routing Rule Is Ignored. However, If

    Mediant 800B MSBR Parameter Description Prefix' field, enter 00 and in the 'Dest IP Address' field, enter 0.0.0.0.  For routing calls between phones connected to the device (i.e., local routing), enter the device's IP address.  When the device's IP address is unknown (e.g., when DHCP is used), enter IP address 127.0.0.1.
  • Page 405 Mediant 800B MSBR 28. Routing Parameter Description SIP Interface. To configure SRD's, see Configuring SRDs on page 264. IP Profile ID Assigns an IP Profile ID to this IP destination call. This allows you CLI: ip-profile-id to assign numerous configuration attributes (e.g., voice codes) per [PREFIX_ProfileId] routing rule.

  • Page 406: Configuring Inbound Ip Routing Table

    Mediant 800B MSBR Parameter Description alternative routing is enabled. This is because the subsequent index entries are defined with a Forking Group number that is lower than that of index entry 1.  Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with...
  • Page 407 Mediant 800B MSBR 28. Routing The Inbound IP Routing table provides two configuration areas:  Matching characteristics of incoming IP call, for example, prefix of destination number.  Operation (destination), for example, sends to a specific Trunk Group. If the incoming call matches the characteristics of a rule, the call is sent to the destination configured for that rule.

  • Page 408: Route Name

    Mediant 800B MSBR  To configure IP-to-Tel or inbound IP routing rules: Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing). Figure 28-3: Inbound IP Routing Table The previous figure displays the following configured routing rules: •...

  • Page 409: Cli: Src-Host-Prefix

    Mediant 800B MSBR 28. Routing Parameter Description Web: Source Host Prefix Defines the prefix of the URI host name in the From header of CLI: src-host-prefix the incoming SIP INVITE message. [PstnPrefix_SrcHostPrefix] By default, no value is defined (i.e., not used in routing rule). To denote any prefix, use the asterisk (*) wildcard.

  • Page 410: Ip Destinations Connectivity Feature

    Mediant 800B MSBR Parameter Description [PstnPrefix_SrcSRDID] routing rule, if the 'Source IP Group ID' parameter (see below) is defined and it is associated with a different SRD, the incoming SIP call is rejected. If the 'Source IP Group ID' parameter is not defined, the SRD's default IP Group is used. If there is no valid source IP Group, the call is rejected.
  • Page 411 Mediant 800B MSBR 28. Routing  Network Connectivity: The device checks the network connectivity of the IP destination configured by the 'Alt Routing Tel to IP Connectivity Method' parameter: • SIP OPTIONS: The device sends "keep-alive" SIP OPTIONS messages to the IP destination.

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

    Mediant 800B MSBR 28.5 Alternative Routing for Tel-to-IP Calls The device supports various alternative Tel-to-IP call routing methods, as described in this section. 28.5.1 Alternative Routing Based on IP Connectivity You can configure the device to route Tel-to-IP calls to an alternative IP destination when the connectivity state of an IP destination is unavailable.

  • Page 413: Alternative Routing Based On Sip Responses

    Mediant 800B MSBR 28. Routing The steps for configuring alternative Tel-to-IP routing based on IP connectivity are summarized below.  To configure alternative Tel-to-IP routing based on IP connectivity: In the Outbound IP Routing table, add alternative Tel-to-IP routing rules for specific calls.
  • Page 414 Mediant 800B MSBR Depending on configuration, the alternative routing is done using one of the following configuration entities:  Outbound IP Routing Rules: You configure alternative routing rules for a specific routing rule in the Outbound IP Routing table. If the destination of the "main" routing rule is unavailable, the device searches the table for the next matching rule (e.g.,...

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

    Mediant 800B MSBR 28. Routing The steps for configuring alternative Tel-to-IP routing based on SIP response codes are summarized below.  To configure alternative Tel-to-IP routing based on SIP response codes: Configure SIP response codes (call failure reasons) that invoke alternative Tel-to-IP routing: Open the Reasons for Tel-to-IP Alternative Routing page (Configuration tab >...

  • Page 416: Pstn Fallback

    Mediant 800B MSBR the device does not try to redirect the call to the next contact and drops the call.  The device redirects the call to the first contact listed in the Contact header. If the contact responds with a SIP response that is configured in the Reasons for Tel-to-IP Alternative Routing table (see ''Alternative Routing Based on SIP Responses'' on page 413), the device tries to redirect the call to the next contact, and so on.

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

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

    Mediant 800B MSBR  To configure alternative Trunk Group routing based on Q.931 cause codes: In the Proxy & Registration page, set the 'Redundant Routing Mode' parameter to Routing Table so that the device uses the Inbound IP Routing table for alternative routing.
  • Page 419 Mediant 800B MSBR 28. Routing 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: ...

  • Page 420: Alternative Routing Upon Isdn Disconnect

    Mediant 800B MSBR 28.6.3 Alternative Routing upon ISDN Disconnect You can configure when the device sends a call to an alternative route if it receives an ISDN Q.931 Disconnect message with a Progress Indicator (PI) IE from the Tel side for IP- to-Tel calls.

  • Page 421: Configuring Dtmf And Dialing

    Mediant 800B MSBR 29. Configuring DTMF and Dialing Configuring DTMF and Dialing The DTMF & Dialing page is used to configure parameters associated with dual-tone multi- frequency (DTMF) and dialing. For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 763.

  • Page 422: Dialing Plan Features

    Mediant 800B MSBR 29.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 29.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 362.
  • Page 423 Mediant 800B MSBR 29. Configuring DTMF and Dialing receives these digits, it does not wait for additional digits, but starts sending the collected digits (dialed number) immediately. Notes: • If you want the device to accept/dial any number, ensure that the digit map contains the rule "xx.T";...

  • Page 424: External Dial Plan File

    Mediant 800B MSBR 29.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 606. User's Manual Document #: LTRT-12813...

  • Page 425: Configuring Supplementary Services

    Mediant 800B MSBR 30. Configuring Supplementary Services Configuring Supplementary Services This section describes SIP supplementary services that can enhance your telephone service. Notes: • All call participants must support the specific supplementary service that is used. • When working with certain application servers (such as BroadSoft’s BroadWorks)
  • Page 426 Mediant 800B MSBR  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). 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.

  • Page 427: Call Hold And Retrieve

    Mediant 800B MSBR 30. Configuring Supplementary Services 30.1 Call Hold and Retrieve Initiating Call Hold and Retrieve:  Active calls can be put on-hold by pressing the phone's hook-flash button.  The party that initiates the hold is called the holding party; the other party is called the held party.
  • Page 428 Mediant 800B 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 429: Call Pickup

    Mediant 800B MSBR 30. Configuring Supplementary Services A ends call with C; A hears a held tone. B ends call with D. B retrieves call with A. Notes: • If a party that is placed on hold (e.g., B in the above example) is called by another party (e.g., D), then the on-hold party receives a call waiting tone instead of the...

  • Page 430: Consultation Feature

    Mediant 800B MSBR 30.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 431: Consultation Transfer For Qsig Path Replacement

    Mediant 800B MSBR 30. Configuring Supplementary Services ETSI TS 183 036, Section G.2 (Explicit Communication Transfer – ECT). Call transfer is enabled using the EnableTransfer and EnableHoldtoISDN parameters. The Explicit Call Transfer (ECT, according to ETS-300-367, 368, 369) supplementary service is supported for BRI and PRI trunks. This service provides the served user who has two calls to ask the network to connect these two calls together and release its connection to both parties.

  • Page 432: Call Forward

    Mediant 800B MSBR • Tel-to-IP call: source number of the original call. • 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.

  • Page 433: Call Forward Reminder Ring

    Mediant 800B MSBR 30. Configuring Supplementary Services 30.6.1 Call Forward Reminder Ring The device supports the Call Forward Reminder Ring feature for FXS interfaces, whereby the device's FXS endpoint emits a short ring burst, only in onhook state, when a third-party Application Server (e.g., softswitch) forwards an incoming call to another destination.

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

    Mediant 800B MSBR  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. To cancel the special dial tone and playing the regular dial tone, the received SIP NOTIFY message must contain the following headers: ...

  • Page 435: Call Waiting

    Mediant 800B MSBR 30. Configuring Supplementary Services  SuppServCodeCFB - Call Forward on Busy  SuppServCodeCFBDeact - Call Forward on Busy Deactivation  SuppServCodeCFNR - Call Forward on No Reply  SuppServCodeCFNRDeact - Call Forward on No Reply Deactivation Note: These codes must be defined according to the settings of the softswitch (i.e.,...

  • Page 436: Message Waiting Indication

    Mediant 800B MSBR To indicate Call Waiting, the device sends a 182 Call Queued response. The device identifies Call Waiting when a 182 Call Queued response is received. Note: The Call Waiting feature is applicable only to FXS/FXO interfaces. 30.8 Message Waiting Indication The device supports Message Waiting Indication (MWI) according to IETF RFC 3842.
  • Page 437 Mediant 800B MSBR 30. Configuring Supplementary Services MWI messages. This is configured by setting the VoiceMailInterface parameter to 8.  ISDN PRI NI-2: The device support the interworking of the SIP MWI NOTIFY messages to ISDN PRI NI-2 Message Waiting Notification (MWN), sent in the ISDN Facility IE message.

  • Page 438: Caller Id

    Mediant 800B MSBR 30.9 Caller ID This section describes the device's Caller ID support. Note: The Caller ID feature is applicable only to FXS/FXO interfaces. 30.9.1 Caller ID Detection / Generation on the Tel Side By default, generation and detection of Caller ID to the Tel side is disabled. To enable Caller ID, set the parameter EnableCallerID to 1.

  • Page 439: Caller Id On The Ip Side

    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 440: 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 441 Mediant 800B MSBR 30. Configuring Supplementary Services Notes: • Three-way conferencing using an external conference server is supported only by FXS interfaces. • Instead of using the flash-hook button to establish a three-way conference call, you can dial a user-defined hook-flash code (e.g., "*1"), configured by the HookFlashCode parameter.

  • Page 442: Emergency E911 Phone Number Services

    Mediant 800B MSBR 30.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 443 Mediant 800B MSBR 30. Configuring Supplementary Services PSAP with all collected MF digits in the SIP From header as one string. The FXS device generates a mid-call wink signal (two subsequent polarity reversals) toward the E911 tandem switch upon either detection of an RFC 2833 "hookflash"...
  • Page 444 Mediant 800B MSBR Typically, the MF spills are sent from the E911 tandem switch to the PSAP, as shown in the table below: Table 30-1: Dialed MF Digits Sent to PSAP Digits of Calling Number Dialed MF Digits 8 digits "nnnnnnnn" (ANI) "KPnnnnnnnnST"...

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

    Mediant 800B MSBR 30. Configuring Supplementary Services 30.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines The device's FXO interface can interwork SIP emergency E911 calls from the Service Provider's IP network to the analog PSAP DID lines. The standards that define this interface include TR-TSY-000350 or Bellcore’s GR-350-Jun2003.
  • Page 446 Mediant 800B MSBR inband, depending on the device's configuration). Typically, this Wink signal followed by the DTMF digits initiates a call transfer. For supporting the E911 service, used the following configuration parameter settings:  Enable911PSAP = 1 (also forces the EnableDIDWink and EnableReversalPolarity) ...
  • Page 447 Mediant 800B MSBR 30. Configuring Supplementary Services  KP is for .  ST is for #.  STP is for B. The MF duration of all digits, except for the KP digit is 60 msec. The MF duration of the KP digit is 120 msec.

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

    Mediant 800B MSBR 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 CSeq:2 INFO...

  • Page 449: 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 450: Microsoft Lync Server 2010 And E9-1-1

    Mediant 800B MSBR The PSTN identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network. 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.
  • Page 451 Mediant 800B MSBR 30. Configuring Supplementary Services The gathering of location information in the Lync Server 2010 network is illustrated in the figure below: Figure 30-6: Microsoft Lync Server 2010 Client Acquiring Location Information The Administrator provisions the LIS database with the location of each network element in the Enterprise.
  • Page 452 Mediant 800B MSBR The LIS queries the published locations for a location and if a match is found, returns the location information to the client. The matching order is as follows: • WAP BSSID • LLDP switch / port •...
  • Page 453 Mediant 800B MSBR 30. Configuring Supplementary Services number to the <CompanyName> column (shown in the table above in bold typeface). As the ELIN Gateway supports up to five ELINs per PIDF-LO, the <CompanyName> column can be populated with up to this number of ELINs, each separated by a semicolon. The digits of each ELIN can be separated by hyphens (xxx-xxx-xxx) or they can be adjacent (xxxxxxxxx).

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

    ELIN when dialing 9-1-1. 30.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN The Microsoft Mediation Server sends the location information of the E9-1-1 caller in the XML-based PIDF-LO body contained in the SIP INVITE message.
  • Page 455 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 456 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 457 Mediant 800B MSBR 30. Configuring Supplementary Services a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=ptime:20 ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/pidf+xml Content-ID: <voip_911_user1@contoso.com> <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:bp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ms="urn:schema:Rtc.LIS.msftE911PidfExtn.2008" entity="sip:voip_911_user1@contoso.com"><tuple id="0"><status><gp:geopriv><gp:location- info><ca:civicAddress><ca:country>US</ca:country><ca:A1>WA</ca:A1> <ca:A3>Redmond</ca:A3><ca:RD>163rd</ca:RD><ca:STS>Ave</ca:STS><ca: POD>NE</ca:POD><ca:HNO>3910</ca:HNO><ca:LOC>40/4451</ca:LOC> <ca:NAM>1111-222-333; 1234567890 </ca:NAM> <ca:PC>98052</ca:PC></ca:civicAddress></gp:location- info><gp:usage-rules><bp:retransmission- allowed>true</bp:retransmission-allowed></gp:usage-...

  • Page 458: Sip Invite Message

    Mediant 800B MSBR In the ELIN table of the ELIN Gateway, the temporarily stored From header value of the SIP INVITE message originally received from the E9-1-1 caller is used for PSAP callback. When the PSAP makes a callback to the E9-1-1 caller, the ELIN Gateway translates the called number (i.e., ELIN) received from the PSAP to the corresponding E9-1-1 caller's...

  • Page 459: Configuring Audiocodes Elin Gateway

    30.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. 30.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.
  • Page 460 Mediant 800B MSBR Note: This also configured using file parameter, EmergencySpecialReleaseCause.  To enable SIP response 503 upon failed E911: Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). From the 'Emergency Special Release Cause' drop-down list, select Enable.

  • Page 461: Multilevel Precedence And Preemption

    Mediant 800B MSBR 30. Configuring Supplementary Services In the Destination Phone Number Manipulation Table for IP-to-Tel Calls (Configuration tab > VoIP menu > GW and IP to IP > Manipulations > Dest Number IP->Tel), add the following two rules for manipulating the destination number...
  • Page 462 Mediant 800B MSBR Notes: • MLPP is supported on ISDN PRI and BRI interfaces. • The device provides MLPP interworking between SIP and ISDN (both directions). • For Trunk Groups configured with call preemption, all must be configured to MLPP [1] or all configured to Emergency [2].
  • Page 463 Mediant 800B MSBR 30. Configuring Supplementary Services Notes: • If the received ISDN message contains NI digits that are not listed in the translation table, the device sets the network-domain to "uc" in the outgoing SIP message. • If the received SIP message contains a network-domain value that is not listed in the translation table, the device sets the NI digits to "0000"...

  • Page 464: Mlpp Preemption Events In Sip Reason Header

    Mediant 800B MSBR 30.12.1 MLPP Preemption Events in SIP Reason Header The device sends the SIP Reason header (as defined in RFC 4411) to indicate the reason and type of a preemption event. The device sends a SIP BYE or CANCEL request, or SIP...

  • Page 465: Precedence Ring Tone

    Mediant 800B MSBR 30. Configuring Supplementary Services 30.12.2 Precedence Ring Tone You can assign a ring tone that is defined in the CPT file to be played when a precedence call is received from the IP side. This is configured by the PrecedenceRingingType parameter.
  • Page 466 Mediant 800B MSBR Note: To allow the end-user to hear a dial tone when picking up the BRI phone, it is recommended to set the Progress Indicator in the Setup Ack bit (0x10000=65536). Therefore, the recommended value is 0x10000 + 0 x1000 = 65536 + 4096 = 69632 (i.e., set the ISDNInCallsBehavior parameter to 69632).
  • Page 467 Mediant 800B MSBR 30. Configuring Supplementary Services The figure below displays an example of multiple-line extensions configured in the Supplementary Services table: Figure 30-11: Supplementary Services Table Page You can register and un-register an endpoint configured in the table. The registration method is according to the 'Registration Mode' parameter located in the Trunk Group Settings page (see ''Configuring Hunt Group Settings'' on page 367).

  • Page 468: 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 469 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 470: Configuring Charge Codes

    Mediant 800B MSBR 30.17 Configuring Charge Codes The Charge Codes table lets you configure metering tones that the device generates to the Tel side on its FXS interfaces, and for Advice of Charge (AOC) services for Euro ISDN trunks (see Advice of Charge Services for Euro ISDN on page 468). To enable the generation of metering tones, see Configuring Metering Tones on page 474.
  • Page 471 Mediant 800B MSBR 30. Configuring Supplementary Services Parameter Description  It is mandatory that the last time period of each rule end at midnight (00). This prevents undefined time frames in a day. Pulse Interval Defines the time interval between pulses (in tenths of a CLI: pulse-interval-<1-4>...

  • Page 472: Configuring Voice Mail

    Mediant 800B MSBR 30.18 Configuring Voice Mail The Voice Mail Settings page allows you to configure the voice mail parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 763. Notes: • The Voice Mail Settings page is available only for FXO and CAS interfaces.

  • Page 473: Analog Gateway

    Mediant 800B MSBR 31. Analog Gateway Analog Gateway This section describes configuration of analog settings. 31.1 Configuring Keypad Features The Keypad Features page enables you to activate and deactivate the following features directly from the connected telephone's keypad:  Call Forward ...

  • Page 474: Configuring Metering Tones

    Mediant 800B 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 31-1: Keypad Features Page Configure the keypad features as required.
  • Page 475 Mediant 800B MSBR 31. Analog Gateway Notes: • The Metering Tones page is available only for FXS interfaces. • Charge Code rules can be assigned to routing rules in the Outbound IP Routing table (see ''Configuring Outbound IP Routing Table'' on page 397). When a new call is established, the Outbound IP Routing table is searched for the destination IP address.

  • Page 476: Configuring Fxo Settings

    Mediant 800B MSBR 31.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 763. Note: The FXO Settings page is available only for FXO interfaces.

  • Page 477: Configuring Authentication

    Mediant 800B MSBR 31. Analog Gateway 31.4 Configuring Authentication The Authentication table lets you configure an authentication username and password per device FXS and FXO port. Notes: • For configuring whether authentication is done per port or for the entire device, use the parameter AuthenticationMode.

  • Page 478: Configuring Automatic Dialing

    Mediant 800B MSBR Parameter Description [Authentication_Index] Port (Read-only) Displays the port number. 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).
  • Page 479 Mediant 800B MSBR 31. Analog Gateway Table 31-2: Automatic Dialing Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number on the table [TargetOfChannel_Index] netry. Module (Read-only) Displays the module number on which the port is located. [TargetOfChannel_Module] Port (Read-only) Displays the port number.

  • Page 480: Configuring Caller Display Information

    Mediant 800B MSBR 31.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 481: Configuring Call Forward

    Mediant 800B MSBR 31. Analog Gateway Parameter Description Note: If you set this parameter to "Private" or "Anonymous", Caller ID is restricted and the settings of the 'Presentation' parameter is ignored. Presentation Enables the sending of the caller ID string.
  • Page 482 Mediant 800B MSBR 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. Table 31-4: Call Forward Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table record.

  • Page 483: Configuring Caller Id Permissions

    Mediant 800B MSBR 31. Analog Gateway 31.8 Configuring Caller ID Permissions The Caller ID Permissions table lets you enable per port, Caller ID generation for FXS interfaces and Caller ID detection for FXO interfaces. Note: If Caller ID permissions is not configured for a port in this table, its Caller ID generation / detection is determined according to the global parameter, 'Enable Call ID' in the Supplementary Services page (Configuration tab >...

  • Page 484: Configuring Call Waiting

    Mediant 800B MSBR 31.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 485: Rejecting Anonymous Calls

    Mediant 800B MSBR 31. Analog Gateway Parameter Description [CallWaitingPerPort_PortType] Call Waiting Configuration Enables call waiting for the port. CLI: enable-call-waiting  [0] Disable [CallWaitingPerPort_IsEnabled]  [1] Enable = Enables call waiting for the port. When the device receives a call on a busy port, it responds with a SIP 182 response (not with a 486 busy).
  • Page 486 Mediant 800B MSBR  To configure distinctive ringing and call waiting per FXS port: Open the Tone Index Table page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Tone Index). Click Add; the following dialog box appears:...

  • Page 487: Fxs/Fxo Coefficient Types

    Mediant 800B MSBR 31. Analog Gateway 31.12 FXS/FXO Coefficient Types The FXS Coefficient and FXO Coefficient types used by the device can be one of the following:  US line type of 600 ohm AC impedance and 40 V RMS ringing voltage for REN = 2 ...

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

    Mediant 800B MSBR 31.13.1 FXO Operations for IP-to-Tel Calls The FXO device provides the following operating modes for IP-to-Tel calls:  One-stage dialing (see ''One-Stage Dialing'' on page 488) • Waiting for dial tone (see ''Two-Stage Dialing'' on page 489) •...

  • Page 489: Two-Stage Dialing

    Mediant 800B MSBR 31. Analog Gateway  Answer Supervision: The Answer Supervision feature enables the FXO device to determine when a call is connected, by using one of the following methods: • Polarity Reversal: the device sends a 200 OK in response to an INVITE only when it detects a polarity reversal.

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

    Mediant 800B MSBR example, a company has a PBX with extensions 555-1000 to 555-1999, and a caller dials 555-1234, the local central office (CO) would forward, for example, only 234 to the PBX. The PBX would then ring extension 234.

  • Page 491: Collecting Digits Mode

    Mediant 800B MSBR 31. Analog Gateway 31.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 31-11: Call Flow for Collecting Digits Mode 31.13.2.3...

  • Page 492: Call Termination On Fxo Devices

    Mediant 800B MSBR without replaces), it generates a new INVITE according to the Refer-To header. 31.13.3 Call Termination on FXO Devices This section describes the device's call termination capabilities for its FXO interfaces:  Calls terminated by a PBX (see ''Call Termination by PBX'' on page 492) ...

  • Page 493: Call Termination Before Call Establishment

    Mediant 800B MSBR 31. Analog Gateway 31.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 494: Dialing From Remote Extension (Phone At Fxs)

    Mediant 800B MSBR below)  FXS interfaces for the 'remote PBX extension'  Analog phones (POTS)  PBX (one or more PBX loop start lines)  LAN network 31.14.1 Dialing from Remote Extension (Phone at FXS) The following procedure describes how to dial from the 'remote PBX extension' (i.e., phone connected to the FXS interface).

  • Page 495: Message Waiting Indication For Remote Extensions

    Mediant 800B MSBR 31. Analog Gateway 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. 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).

  • Page 496: Fxs Gateway Configuration

    Mediant 800B MSBR 31.14.5 FXS Gateway Configuration The following procedure describes how to configure the FXS interface (at the 'remote PBX extension').  To configure the FXS interface: In the Trunk Group table (see Configuring Trunk Group Table), assign the phone numbers 100 to 104 to the device's endpoints.

  • Page 497: Fxo Gateway Configuration

    Mediant 800B MSBR 31. Analog Gateway 31.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 (see Configuring Trunk Group Table on page 365), assign the phone numbers 200 to 204 to the device’s FXO endpoints.
  • Page 498 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...
  • Page 499 Part VI Session Border Controller Application...

  • Page 501: Sbc Overview

    Mediant 800B MSBR 32. SBC Overview SBC Overview This section provides a detailed description of the device's SBC application. Notes: • For guidelines on how to deploy your E-SBC device, refer to the E-SBC Design Guide document. • The SBC feature is available only if the device is installed with a Software License Key that includes this feature.

  • Page 502: Sip Network Definitions

    Mediant 800B MSBR • Changes the SIP Contact header to the device's own address. • 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 503 Mediant 800B MSBR 32. SBC Overview ♦ Destination URL: The destination URL is obtained from the Request-URI. • REGISTER dialogs: ♦ Source URL: The source URL is obtained from the To header. ♦ Destination URL: The destination URL is obtained from the Request-URI.

  • Page 504: User Registration

    Mediant 800B MSBR The flowchart below illustrates the SBC process: Figure 32-1: Routing Process 32.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 505: Initial Registration Request Processing

    Mediant 800B MSBR 32. SBC Overview Typically, the device is configured as the user agent's outbound proxy and the device is configured (using the IP-to-IP Routing table) to route requests received from this IP Group to the serving proxy and vice versa. Survivability can be achieved using the alternative routing feature.

  • Page 506: Routing Using Users Registration Database

    Mediant 800B MSBR  Timeout of the Expires header value (in scenarios where the user agent did not send a refresh registration request). Note: The device's Users Registration database poses the following restrictions: • The same contact cannot belong to more than one AOR.

  • Page 507: Registration Restriction Control

    Mediant 800B MSBR 32. SBC Overview 32.3.5 Registration Restriction Control The device provides flexibility in controlling user registration:  Limiting Number of Registrations: You can limit the number of users that can register with the device per IP Group and/or SRD. By default, no limitation exists for registered users.

  • Page 508: Media Anchoring Without Transcoding (Transparent)

    Mediant 800B MSBR  IP addresses and ports of the media flow  Media flow mode (send receive, receive only, send only, inactive)  Media coders (coders and their characteristics used in each media flow)  Other (standard or proprietary) media and session characteristics...

  • Page 509: Media Anchoring With Transcoding

    Mediant 800B MSBR 32. SBC Overview  Session connection attribute ('c=' field)  Media connection attribute ('c=' field)  Media port number  RTCP media attribute IP address and port Each SBC leg allocates and uses the device's local ports (e.g., for RTP\RTCP\fax). The local ports are allocated from a Media Realm associated with each leg.
  • Page 510 Mediant 800B MSBR as its supported codec. Since this is sent to a Destination IP Group that is configured with an extended coder list, on the WAN leg the device adds another supported codec G.729 to the SDP, which is now offered to the WAN IP phone. The WAN IP phone chooses the extended codec (G.729) in its SDP answer to the device's WAN leg.

  • Page 511: No Media Anchoring

    Mediant 800B MSBR 32. SBC Overview  PRACK and UPDATE transactions can also be used for initiating subsequent offer\answer transactions before the INVITE 200 OK response.  In a SIP dialog life time, media characteristics after originally determined by the first offer\answer transaction can be changed by using subsequent offer\answer transactions.

  • Page 512: Transcoding Modes

    Mediant 800B MSBR  Reduces CPU usage (no media handling)  Avoids interference in SDP negotiation and header manipulation on RTP/SRTP The device handles the No Media Anchoring process as follows: Identifies a No Media Anchoring call according to configuration and the call’s properties (such as source, destination, IP Group, and SRD).

  • Page 513: Restricting Coders

    Mediant 800B MSBR 32. SBC Overview sides of the session have negotiated without SBC intervention (for example, coder extension). The transcoding mode can be configured globally, using the TranscodingMode parameter or for specific calls, using the IP Profile table. Note: To implement transcoding, you must configure the number of required DSP channels for transcoding (for example, MediaChannels = 120).
  • Page 514 Mediant 800B MSBR For example, assume the following:  The SDP coder offer includes the following coders: G.729, G.711, and G.723.  The incoming leg includes the following Allowed coders: G.711 and G.729. The device selects the common coders, i.e., G.711 and G.729 (with changed preferred coder priority - highest for G.711).

  • Page 515: Prioritizing Coder List In Sdp Offer

    Mediant 800B MSBR 32. SBC Overview Coders Group for extension coders. In the IP Profile table, select this Coders Group in the 'Extension Coders Group ID' parameter. In the IP Profile table, enable this feature by setting the 'Allowed Coders Mode' parameter to Restriction or Restriction and Preference.

  • Page 516: Multiple Rtp Media Streams Per Call Session

    Mediant 800B MSBR 32.4.9 Multiple RTP Media Streams per Call Session The device's SBC application supports multiple RTP media streams per SBC call session. Up to five different media types can be included in a session:  Audio (m=audio) ...

  • Page 517: Limiting Sbc Call Duration

    Mediant 800B MSBR 32. SBC Overview Settings table).  SBCFaxOfferMode: determines the fax coders sent in the outgoing SDP offer.  SBCFaxAnswerMode: determines the fax coders sent in the outgoing SDP answer.  IPProfile_SBCRemoteRenegotiateOnFaxDetection: You can also configure the device to detect for faxes (CNG tone) immediately after the establishment of a voice channel (i.e., after 200 OK) and within a user-defined interval.

  • Page 518: User Authentication Based On Radius

    Mediant 800B MSBR The device challenges the received SIP message only if it is configured as a SIP method (e.g., INVITE) for authorization. This is configured in the IP Group table, using the 'Authentication Method List' parameter. If the message is received without a SIP Authorization header, the device "challenges"...

  • Page 519: Interworking Sip 3Xx Redirect Responses

    Mediant 800B MSBR 32. SBC Overview 32.8.1 Interworking SIP 3xx Redirect Responses The device supports interworking of SIP 3xx redirect responses. By default, the device's handling of SIP 3xx responses is to send the Contact header unchanged. However, some SIP UAs may support different versions of the SIP 3xx standard while others may not even support SIP 3xx.

  • Page 520: Local Handling Of Sip 3Xx

    Mediant 800B MSBR The prefix is removed before the resultant INVITE is sent to the destination. Figure 32-6: SIP 3xx Response Handling The process of this feature is described using an example: The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User@IPPBX:5060;transport=tcp;param=a>;q=0.5).

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

    Mediant 800B MSBR 32. SBC Overview 32.8.2 Interworking SIP Diversion and History-Info Headers This device can be configured to interwork between the SIP Diversion and History-Info headers. This is important, for example, to networks that support the Diversion header but not the History-Info header, or vice versa.

  • Page 522: Interworking Sip Prack Messages

    Mediant 800B MSBR peer PBXs  Advanced routing rules for the new, initiated INVITE  Forwarding early media after REFER while attempting to avoid transcoding (by sending session update)  Interoperate with environments were different SIP UAs lack basic SIP functionality such as re-INVITE, UPDATE, PRACK, Delayed Offer, re-INVITE without SDP ...
  • Page 523 Mediant 800B MSBR 32. SBC Overview  Early Media Enabling: The device supports the interworking of early media between SIP UAs that support early media and those that do not support receipt of early media. Early media can arrive in provisional responses to an INVITE request. The device forwards the request of early media for IP Groups that support this capability;...

  • Page 524: Interworking Sip Re-Invite Messages

    Mediant 800B MSBR Figure 32-8: Early Media RTP - SIP 18x with SDP 32.8.7 Interworking SIP re-INVITE Messages The device supports interworking of SIP re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs.

  • Page 525: Interworking Sip Update Messages

    Mediant 800B MSBR 32. SBC Overview 32.8.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 526: Call Survivability

    Mediant 800B MSBR 32.9 Call Survivability This section describes various call survivability features supported by the SBC device. 32.9.1 Auto-Provisioning of Subscriber-Specific Information for BroadWorks Server for Survivability This feature enables SBC user registration for interoperability with BroadSoft BroadWorks server to provide call survivability in case of connectivity failure with the BroadWorks server, for example, due to a WAN failure.
  • Page 527 Mediant 800B MSBR 32. SBC Overview network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients. This feature is supported by configuring a primary extension and associating it with secondary extensions (i.e., shared lines) so that incoming calls to the primary extension...

  • Page 528: Call Survivability For Call Centers

    Mediant 800B MSBR • Set the 'Source IP Group' field to the IP Group ID that you created for the users (e.g., 2). • Set the 'Source Username Prefix' field to represent the secondary extensions (e.g., 601 and 602). •...
  • Page 529 Mediant 800B MSBR 32. SBC Overview  To configure call survivability for a call center application: In the IP Group table (see ''Configuring IP Groups'' on page 270), add IP Groups for the following entities: • TDM Gateway (Server-type IP Group). This entity forwards the customer calls through the device to the Application server.

  • Page 530: Survivability Mode Display On Aastra Ip Phones

    Mediant 800B MSBR The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure 32-13: Routing Rule Example for Call Center Survivability 32.9.4 Survivability Mode Display on Aastra IP Phones...

  • Page 531: Call Forking

    Mediant 800B MSBR 32. SBC Overview 32.10 Call Forking This section describes various Call Forking features supported by the device. 32.10.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 532: Call Forking-Based Ip-To-Ip Routing Rules

    Mediant 800B MSBR initiating UA is not relevant, and media synchronization is needed between the two UAs. Media synchronization is done by sending a re-INVITE request immediately after the call is established. The re-INVITE is sent without an offer to the INVITE-initiating UA. This causes the UA to send an offer which is forwarded to the UA that confirmed the call.

  • Page 533: Enabling The Sbc Application

    Mediant 800B MSBR 33. Enabling the SBC Application Enabling the SBC Application Before you can start configuring the SBC, you must first enable the SBC application. Once enabled, the Web interface displays the menus and parameter fields relevant to the SBC application.
  • Page 534 Mediant 800B MSBR This page is intentionaly left blank. User's Manual Document #: LTRT-12813...

  • Page 535: Configuring General Settings

    Mediant 800B MSBR 34. Configuring General Settings Configuring General Settings The General Settings page allows you to configure general SBC parameters. For a description of these parameters, see ''SBC Parameters'' on page 983.  To configure general parameters: Open the General Settings page (Configuration tab > VoIP menu > SBC > General Settings).
  • Page 536 Mediant 800B MSBR due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements. The device resolves this by replacing the call identifiers received from the application server with the correct call identifiers (e.g., user A and user B). Thus, users subscribed to the service can receive relevant NOTIFY messages from the device and use the service.
  • Page 537 Mediant 800B MSBR 34. Configuring General Settings <target uri="sip:line3@host3.example.net"> <param pname="actor" pval="attendant"/> <param pname="automaton" pval="false"/> </target> </remote> </dialog> </dialog-info> Version 6.8 Mediant 800B MSBR...
  • Page 538 Mediant 800B MSBR This page is intentionaly left blank. User's Manual Document #: LTRT-12813...

  • Page 539: Configuring Admission Control

    Mediant 800B MSBR 35. Configuring Admission Control Configuring Admission Control The Admission Control table lets you configure up to 100 Call Admission Control rules (CAC). CAC rules define the maximum number of concurrent calls (SIP dialogs) permitted per IP Group or SRD, and per user (identified by its registered contact) belonging to these entities.
  • Page 540 Mediant 800B 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 486 "Busy Here"...
  • Page 541 Mediant 800B MSBR 35. Configuring Admission Control Parameter Description  CLI: limit-type [0] IP Group (default) [SBCAdmissionControl_LimitType]  [1] SRD IP Group ID Defines the IP Group to which you want to CLI: ip-group-id apply the rule. [SBCAdmissionControl_IPGroupID] The default value is -1 (i.e., all IP Groups).
  • Page 542 Mediant 800B MSBR Parameter Description Rate Defines the rate at which tokens are added to CLI: rate the token bucket per second (i.e., token rate). [SBCAdmissionControl_Rate] One token is added to the bucket every 1000 divided by the value of this parameter (in milliseconds).

  • Page 543: Configuring Coder Groups

    Mediant 800B MSBR 36. Configuring Coder Groups Configuring Coder Groups 36.1 Configuring Allowed Audio Coder Groups The Allowed Audio Coders Group table lets you configure up to five Allowed Audio Coders Groups. An Allowed Audio Coders Group defines a list of audio media coders that can be used for a specific SIP entity.

  • Page 544: Configuring Allowed Video Coder Groups

    Mediant 800B MSBR 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. Table 36-1: Allowed Audio Coders Group Table Parameter Descriptions...

  • Page 545: Routing Sbc

    Mediant 800B MSBR 37. Routing SBC Routing SBC This section describes the configuration of the routing entities for the SBC application. These include the following:  Classification rules - see ''Configuring Classification Rules'' on page 545  Message Condition rules - see ''Configuring Message Condition Rules'' on page 551 ...
  • Page 546 Mediant 800B MSBR Classification Stage 3 - Classification Table: If classification based on Proxy Set fails (or disabled), the device uses the Classification table to classify the SIP dialog to an IP Group. If it locates a Classification rule whose characteristics (such as source IP address) match the incoming SIP dialog, the SIP dialog is assigned to the associated IP Group.
  • Page 547 Mediant 800B MSBR 37. Routing SBC The flowchart below illustrates the classification process: Figure 37-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 548 Mediant 800B MSBR  To configure a Classification rule: Open the Classification Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Click Add; the following dialog box appears: Figure 37-2: Classification Table Page Configure the Classification rule according to the parameters described in the table below.
  • Page 549 Mediant 800B MSBR 37. Routing SBC Parameter Description wildcards:  "x" wildcard: represents single digits. For example, 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.  Asterisk (*) wildcard: represents any number between 0 and 255. For example, 10.8.8.* represents all addresses between 10.8.8.0 and 10.8.8.255.

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

    Mediant 800B MSBR Parameter Description Destination Host Defines the prefix of the destination Request-URI host CLI: dst-host name of the incoming SIP dialog request. [Classification_DestHost] The default is the asterisk (*) symbol, which represents any destination host prefix. Operation Rule - Action...

  • Page 551: Configuring Message Condition Rules

    Mediant 800B MSBR 37. Routing SBC Index Source URI Input Destination URI Input P-Called-Party-ID Route In this example, a match exists only for Classification Rule #1. This is because the source (1111) and destination (2000) username prefixes match those in the INVITE's P-Called-...

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

    Mediant 800B MSBR  To configure a Message Condition rule: Open the Message Condition Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Message Condition Table). Click Add; the following dialog box appears: Figure 37-3: Condition Table Page - Add Record Dialog Box Configure a Message Condition rule according to the parameters described in the table below.
  • Page 553 Mediant 800B MSBR 37. Routing SBC If the characteristics of an incoming call do not match the first rule in the table, the call characteristics are compared to those of the second rule, and so on until a matching rule is located.
  • Page 554 Mediant 800B MSBR The IP-to-IP Routing table also provides the following features:  Alternative routing or load balancing: In addition to the alternative routing/load balancing provided by the Proxy Set associated with the destination IP Group, the table allows the configuration of alternative routes whereby if a route fails, the next adjacent (below) rule in the table that is configured as 'Alt Route Ignore/Consider Inputs' are used.
  • Page 555 Mediant 800B MSBR 37. Routing SBC The LCR feature can also be employed with call forking. The device calculates a maximum call cost for each Forking group and routes the call to the Forking group with the lowest cost. Thus, even if the call can successfully be routed to the main routing rule, a different routing rule can be chosen (even an alternative route, if configured) based on LCR.
  • Page 556 Mediant 800B MSBR Click Submit, and then save ("burn") your settings to flash memory. Table 37-3: IP-to-IP Routing Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [IP2IPRouting_Index] Route Name Defines an arbitrary name to easily identify the IP-to-IP CLI: route-name routing rule.
  • Page 557 Mediant 800B MSBR 37. Routing SBC Parameter Description Message Condition Assigns a SIP message Condition rule. To configure [IP2IPRouting_MessageCondition] Condition rules, see ''Configuring Message Condition Rules'' CLI: message-condition on page 551. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect [IP2IPRouting_ReRouteIPGroupID] response (e.g., 3xx) or REFER message.
  • Page 558 Mediant 800B MSBR Parameter Description destination address. If the fields 'Destination Port' and 'Destination Transport Type' are configured, the incoming Request-URI parameters are overridden and these fields take precedence.  [4] Hunt Group = Used for call center survivability. For more information, see ''Call Survivability for Call Centers'' on page 528.
  • Page 559 Mediant 800B MSBR 37. Routing SBC Parameter Description are defined in this table, the destination SRD is determined according to the source SRD associated with the Source IP Group (configured in the IP Group table, see ''Configuring IP Groups'' on page 270). If this table...
  • Page 560 Mediant 800B 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 561: Configuring Sip Response Codes For Alternative Routing Reasons

    Mediant 800B MSBR 37. Routing SBC Parameter Description Cost Group Assigns a Cost Group to the routing rule for determining the [IP2IPRouting_CostGroup] cost of the call. To configure Cost Groups, see ''Configuring CLI: cost-group Cost Groups'' on page 238. By default, no Cost Group is defined.
  • Page 562 Mediant 800B MSBR parameter, SBCAlternativeRoutingReasons or CLI command, configure voip > sbc routing sbc-alt-routing-reasons.  To configure SIP reason codes for alternative IP routing: Open the SBC Alternative Routing Reasons page (Configuration tab > VoIP menu > SBC > Routing SBC > Alternative Routing Reasons).

  • Page 563: Sbc Manipulations

    Mediant 800B MSBR 38. SBC Manipulations SBC Manipulations This section describes the configuration of the manipulation rules for the SBC application. Note: For additional manipulation features, see the following: • ''Configuring SIP Message Policy Rules''. • ''Configuring SIP Message Manipulation'' on page 299.
  • Page 564 Mediant 800B MSBR Contact: <sip:7000@10.2.2.3> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20  Outgoing INVITE to WAN: INVITE sip: 9721000@ITSP;user=phone;x=y;z=a SIP/2.0...

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

    Mediant 800B MSBR 38. SBC Manipulations INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone> 38.1 Configuring IP-to-IP Inbound Manipulations The IP to IP Inbound Manipulation table lets you configure up to 100 IP-to-IP Inbound Manipulation rules.
  • Page 566 Mediant 800B 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 567 Mediant 800B MSBR 38. SBC Manipulations Parameter Description [IPInboundManipulation_Manipula routing input and source and/or destination number. tionPurpose]  [1] Routing input only = Inbound manipulations affect the routing input only, retaining the original source and destination number.  [2] Shared Line = Used for the Shared-Line Appearance feature.

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

    Mediant 800B MSBR Parameter Description tedURI] SIP URI user part.  [1] Destination = Manipulation is done on the destination SIP 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.
  • Page 569 Mediant 800B MSBR 38. SBC Manipulations Note: SIP URI host name (source and destination) manipulations can also be configured in the IP Group table. These manipulations are simply host name substitutions with the names configured for the source and destination IP Groups, respectively.
  • Page 570 Mediant 800B MSBR Parameter Description Matching Characteristics - Rule Additional Manipulation Determines whether additional manipulation is done for the CLI: is-additional-manipulation table entry rule listed directly above it. [IPOutboundManipulation_IsAdditio  [0] No = (Default) Regular manipulation rule - not done in nalManipulation] addition to the rule above it.
  • Page 571 Mediant 800B MSBR 38. SBC Manipulations Parameter Description CLI: request-type is applied. [IPOutboundManipulation_Request  [0] All = (Default) all SIP messages. Type]  [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.  [2] REGISTER = Only SIP REGISTER messages.
  • Page 572 Mediant 800B MSBR Parameter Description Remove From Right Defines the number of digits to remove from the right of the CLI: remove-from-right manipulated item prefix. For example, if you enter 3 and the [IPOutboundManipulation_Remove user name is "john", the new user name is "j".
  • Page 573 Part VII Cloud Resilience Package...

  • Page 575: 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 576 Mediant 800B MSBR Survivability Quality of Experience/Service Security numbers are learned dynamically in the registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line...

  • Page 577: Crp Configuration

    Mediant 800B MSBR 40. CRP Configuration CRP Configuration This section describes configuration specific to the CRP application. As CRP has similar functionality to the SBC application, for configuration that is common to the SBC, which is not covered in this section, see the following SBC sections: ...

  • Page 578: Configuring Call Survivability Mode

    Mediant 800B MSBR 40.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 579: Pre-Configured Ip Groups

    Mediant 800B MSBR 40. CRP Configuration  Always Emergency: The CRP routes the calls between the branch users themselves as if connectivity failure has occurred with the IP PBX. The CRP also registers the branch users in its registration database.

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

    Mediant 800B MSBR 40.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 578.

  • Page 581: Emergency Mode

    Mediant 800B MSBR 40. CRP Configuration 40.4.2 Emergency Mode The pre-configured IP-to-IP routing rules for the Emergency CRP call survivability mode are shown in the table below: Table 40-3: Pre-Configured IP-to-IP Routing Rules for Emergency Mode Mode Index Source IP...

  • Page 582: Configuring Pstn Fallback

    Mediant 800B MSBR 40.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 583 Part VIII Data-Router Configuration...

  • Page 585: 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 586 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...
  • Page 587 Part IX Maintenance...

  • Page 589: Basic Maintenance

    Mediant 800B MSBR 42. Basic Maintenance Basic Maintenance The Maintenance Actions page allows you to perform the following:  Reset the device - see ''Resetting the Device'' on page 589  Lock and unlock the device - see ''Locking and Unlocking the Device'' on page 591 ...

  • Page 590: Remotely Resetting Device Using Sip Notify

    Mediant 800B MSBR  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 589). 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 591: Locking And Unlocking The Device

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

    Mediant 800B MSBR Click the LOCK button; a confirmation message box appears requesting you to confirm device lock. Figure 42-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 593: Disconnecting Active Calls

    Mediant 800B MSBR 43. Disconnecting Active Calls Disconnecting Active Calls You can forcibly disconnect all active (established) calls or disconnect specific calls based on their Session ID. This is done in the CLI using the following commands (from basic command mode): ...
  • Page 594 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 595: Resetting Channels

    Mediant 800B MSBR 44. Resetting Channels Resetting Channels 44.1 Resetting an Analog Channel You can inactivate (reset) an FXO or FXS analog channel. This is sometimes useful, for example, when the device (FXO) is connected to a PBX and the communication between the two can't be disconnected (e.g., when using reverse polarity).
  • Page 596 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 597: Disabling Analog Ports

    Mediant 800B MSBR 45. Disabling Analog Ports Disabling Analog Ports You can disable an analog port (FXS or FXO) on the device. When disabled, the port cannot be used and no signaling is transmitted through the port. In addition, the LED of the analog port is lit red.
  • Page 598 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 599: Software Upgrade

    Mediant 800B MSBR 46. Software Upgrade Software Upgrade This chapter describes various software update procedures. 46.1 Loading Auxiliary Files Various Auxiliary files can be installed on the device. These Auxiliary files provide the device with additional configuration settings. The table below lists the different types of...

  • Page 600: 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 601 Mediant 800B MSBR 46. Software Upgrade Note: Only the dat file format can be loaded to the device. You can create up to 32 different Call Progress Tones, each with frequency and format attributes. The frequency attribute can be single or dual-frequency (in the range of 300 to 1980 Hz) or an Amplitude Modulated (AM).
  • Page 602 Mediant 800B MSBR ♦ Continuous (1) ♦ Cadence (2) ♦ Burst (3) • 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 603: Distinctive Ringing

    Mediant 800B MSBR 46. Software Upgrade Tone Form =1 (continuous) Low Freq [Hz]=440 High Freq [Hz]=0 Low Freq Level [-dBm]=10 (-10 dBm) High Freq Level [-dBm]=32 (use 32 only if a single tone is required) First Signal On Time [10msec]=300; the dial tone is detected after...

  • Page 604: Prerecorded Tones File

    Mediant 800B MSBR • 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.

  • Page 605: Cas Files

    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 606: 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 599.
  • Page 607 • To use the Dial Plan file, you must also use a special CAS .dat file that supports this feature. For more information, contact your AudioCodes sales representative. • For E1 CAS MFC-R2 variants, which don't support terminating digit for the called party number, usually I-15, the Dial Plan file and the DigitMapping parameter are ignored.

  • Page 608: 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 599.
  • Page 609 Mediant 800B MSBR 46. Software Upgrade local calls and international calls would need to be routed to different SIP trunks. Thus, instead of configuring many routing rules for each call destination type, you can simply configure two routing rules, one with a unique prefix tag representing the different local area codes and the other with a prefix tag representing international calls.
  • Page 610 Mediant 800B 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 611 Mediant 800B MSBR 46. Software Upgrade configure two routing rules, one with a unique prefix tag representing the different local area codes and the other with a prefix tag representing international calls. Note: When using prefix tags, you need to configure manipulation rules to remove the tags before the device sends the calls to their destinations.

  • Page 612: Obtaining Ip Destination From Dial Plan File

    Mediant 800B MSBR Open the IP-to-IP Routing table (Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table), and then click Add. Click the Rule tab, and then enter the prefix tag in the 'Source Username Prefix' or 'Destination Username Prefix' fields (e.g., "LOCL", without the quotes).

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

    Mediant 800B MSBR 46. Software Upgrade 46.1.4.5 Modifying ISDN-to-IP Calling Party Number The device can use the Dial Plan file to change the Calling Party Number value (source number) of the incoming ISDN call when sending to IP. For this feature, the Dial Plan file supports the following syntax: <ISDN Calling Party Number>,0,<new calling number>...

  • Page 614: User Information File

    Mediant 800B MSBR 46.1.5 User Information File This section describes the User Info table and how to configure the table. 46.1.5.1 Enabling the User Info Table Before you can use the User Info table, you need to enable the User Info functionality as described in the following procedure.
  • Page 615 Mediant 800B MSBR 46. Software Upgrade Registrar server, using the "global" number in the From/To headers. If authentication is necessary for registration, the device sends the user's username and password, configured in the User Info table, in the SIP MD5 Authorization header.
  • Page 616 Mediant 800B MSBR Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 592. To register a user, select the user's table entry, and then from the Action button's drop- down list , choose Register. To un-register a user, select the user, and then from the Action button's drop-down list , choose Un-Register.
  • Page 617 Mediant 800B MSBR 46. Software Upgrade  To view a specific entry (example): (sip-def-proxy-and-reg)# user-info gw-user-info <index, e.g., 0> (gw-user-info-0)# display pbx-ext (405) global-phone-num (405) display-name (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered)  To search a user by pbx-ext: (sip-def-proxy-and-reg)# user-info find <pbx-ext e.g., 405>...

  • Page 618: User Information File For Sbc User Database

    Mediant 800B MSBR 402 , 638002 , Lee , leem, 4321 403 , 638003 , Sue , suer, 8790 404 , 638004 , John , johnd, 7694 405 , 638005 , Pam , pame, 3928 406 , 638006 , Steve , steveg, 1119...
  • Page 619 Mediant 800B MSBR 46. Software Upgrade Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 592. To register a user, select the user's table entry, and then from the Action button's drop- down list, choose Register. To un-register a user, select the user, and then from the Action button's drop-down list, choose Un-Register.
  • Page 620 Mediant 800B MSBR ip-group-id (1) status (not-resgistered)  To view a specific entry (example): (sip-def-proxy-and-reg)# user-info sbc-user-info <index, e.g., 0> (sbc-user-info-0)# display local-user (JohnDee) username (userJohn) password (s3fn+fn=) ip-group-id (1) status (not-resgistered)  To search a user by local-user: (sip-def-proxy-and-reg)# user-info find <local-user, e.g., JohnDoe>...

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

    CLI - see Installing Software License Key using CLI on page 624  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 623: Installing Software License Key Using Web Interface

    Mediant 800B MSBR 46. Software Upgrade 46.2.2.1 Installing Software License Key using Web Interface The following procedure describes how to install the Software License Key in the Web interface.  To install the Software License Key in the Web interface: Open the Software Upgrade Key Status page (Maintenance tab >...

  • Page 624: 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 625: 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 626 Mediant 800B MSBR  To load files using the Software Upgrade Wizard: Make sure that you have installed a new Software License Key (see Software License Key on page 621) that is compatible with the software version to be installed.
  • Page 627 Mediant 800B MSBR 46. Software Upgrade Note: At this stage, you can quit the Software Upgrade Wizard without having to reset the device, by clicking Cancel . However, if you continue with the wizard and start loading the cmp file, the upgrade process must be completed with a device reset.
  • Page 628 Mediant 800B 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 629: Backing Up And Loading Configuration File

    Mediant 800B MSBR 46. Software Upgrade When the device finishes the installation process and resets, the following wizard page is displayed, showing the installed software version and other files (ini file and auxiliary files) that you may also have installed: Figure 46-10: Software Upgrade Process Completed Successfully Click End Process to close the wizard;...
  • Page 630 Mediant 800B MSBR  To save or load an ini file: Open the Configuration File page by doing one of the following: • From the Navigation tree, click the Maintenance tab, click the Software Update menu, and then click Configuration File.

  • Page 631: Automatic Provisioning Mechanisms

    Mediant 800B MSBR 47. Automatic Provisioning Mechanisms Automatic Provisioning Mechanisms This chapter describes the device's automatic provisioning mechanisms. 47.1 Automatic Configuration Methods The table below summarizes the automatic provisioning methods supported by the device: Automatic Provisioning Methods BootP / TFTP...

  • Page 632: Http-Based Provisioning

    Mediant 800B MSBR 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 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server"...

  • Page 633: Ftp- Or Nfs-Based Provisioning

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

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

    Mediant 800B 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 635: File Location For Automatic Update

    Mediant 800B MSBR 47. Automatic Provisioning Mechanisms ♦ Startup Script: The file updates the device's configuration according to the file's configuration settings and sets all other parameters that are not included in the file to factory defaults. The file causes two device resets in order to apply the settings.

  • Page 636: Triggers For Automatic Update

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

  • Page 637: Querying Provisioning Server For Updated Files

    For example, if you set AupdHttpUserAgent = <NAME>;<VER>, the device sends the following User-Agent header: Mozilla/4.0 (compatible; AudioCodes; Mediant; 6.80.200.001) If the provisioning server has relevant files available for the device, the following occurs, depending on file type and configuration: Version 6.8...
  • Page 638 Mediant 800B MSBR • File Download upon each Automatic Update process: This is applicable to software (.cmp), CLI Script, Startup Script files. In the sent HTTP Get request, the device uses the HTTP If-Modified-Since header to determine whether to download these files. The header contains the date and time (timestamp) of when the device last downloaded the file from the specific URL.

  • Page 639: File Download Sequence

    Mediant 800B MSBR 47. Automatic Provisioning Mechanisms Software (.cmp) File: ♦ ini: CmpFileUrl = 'https://www.company.com/device/v.6.80A.227.005.cmp' ♦ CLI: (config-system)# automatic-update (automatic-update)# firmware https://www.company.com/device/v.6.80A.227.005.cmp Notes: • For one-time file download, the HTTP Get request sent by the device does not include the If-Modified-Since header. Instead, the HTTP-User-Agent header can be used in the HTTP Get request to determine whether firmware update is required.

  • Page 640: Cyclic Redundancy Check On Downloaded Configuration Files

    Mediant 800B MSBR Notes: • If you have configured one-time software file (.cmp) download (configured by the ini file parameter CmpFileURL or CLI command configure system > automatic- update > firmware), the device will only apply the file if one-time software updates are enabled.

  • Page 641: Automatic Update Configuration Examples

    Mediant 800B MSBR 47. Automatic Provisioning Mechanisms Location for Automatic Update' on page 635, the file name is included in the configured URL of the provisioning server where the file is located. Including the MAC address in the file name is useful if you want the device to download a file that is unique to the device.

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

    Mediant 800B MSBR ♦ ini File: AutoUpdateFrequency = 1440 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 1440 Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# auto-firmware 'http://www.company.com/sw.cmp'...
  • Page 643 Mediant 800B MSBR 47. Automatic Provisioning Mechanisms NFSServers_AuthType, NFSServers_UID, NFSServers_GID, NFSServers_VlanType; NFSServers 0 = "10.31.2.10", "/usr/share/public/", 2, 1, 0, 1, 1; [ \NFSServers ] Configure the device with the URL path of the CPT file: ♦ ini File: CptFileURL = 'file://10.31.2.10/usr/share/public/usa_tones.dat'...

  • Page 644: Automatic Update For Mass Deployment

    Mediant 800B MSBR • ini File: AutoUpdateFrequency = '03:00' • CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 03:00 47.2.9.3 Automatic Update for Mass Deployment This example describes how to configure the Automatic Update feature for updating multiple devices (i.e., mass deployment) using an HTTP provisioning server. In this example, all the devices are configured to download the same "master"...
  • Page 645 Mediant 800B MSBR 47. Automatic Provisioning Mechanisms 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 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.

  • Page 646: 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 647 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 648: 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 641), and place it on your provisioning server (to where the Redirect server redirects the device).

  • Page 649: Using Zero Configuration With Automatic Update

    Mediant 800B MSBR 47. Automatic Provisioning Mechanisms Set up a DHCP server for assigning an IP address to the device's WAN Ethernet interface. Power down and then power up the device to trigger Zero Configuration. Cable the device to the WAN network.
  • Page 650 Mediant 800B MSBR The device attempts to download the files from the URLs (provisioning servers) according to the Automatic Update settings. The method for connecting to the provisioning server(s) and for determining whether the file(s) must be downloaded is described in 'Querying HTTP Provisioning Server for Updated Files' on page 637.

  • Page 651: Automatic Provisioning Using Usb Flash Drive

    Mediant 800B MSBR 47. Automatic Provisioning Mechanisms 47.4 Automatic Provisioning using USB Flash Drive The device can be automatically provisioned using an external USB hard drive or flash drive (disk on key) connected to its USB port. In order to do this, you need to create a CLI script file named "ac_autorun.txt"...
  • Page 652 Mediant 800B MSBR 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 MSBR(conf-if-GE 0/0)# exit MSBR(config-data)# exit MSBR# configure system MSBR(config-system)# cli-terminal MSBR(cli-terminal)# activate defaults exit help history list pwd quit MSBR(cli-terminal)# set ssh on MSBR(cli-terminal)#...

  • Page 653: Restoring Factory Defaults

    Mediant 800B MSBR 48. Restoring Factory Defaults Restoring Factory Defaults You can restore the device's configuration to factory defaults using one of the following methods:  CLI (see ''Restoring Defaults using CLI'' on page 653)  Hardware reset pinhole button (see Restoring Defaults using Hardware Reset Button on page 654) ...

  • Page 654: Restoring Defaults Using Hardware Reset Button

    Mediant 800B 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 655: Automatic Archiving Of Configuration File

    Mediant 800B MSBR 49. Automatic Archiving of Configuration File Automatic Archiving of Configuration File You can configure the device to automatically save a configuration file each time you modify the device's configuration. The archived file can be saved to a user-defined URL of a remote server (TFTP or HTTP/S), or to a USB storage device attached to the device.
  • Page 656 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 657: Usb Storage Capabilities

    Mediant 800B MSBR 50. USB Storage Capabilities USB Storage Capabilities The device supports USB storage using an external USB hard drive or flash disk (disk on key) connected to its USB port. The storage capabilities are configured using the CLI and include the following: ...
  • Page 658 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...
  • Page 659 Part X Status, Performance Monitoring and Reporting...

  • Page 661: System Status

    Mediant 800B MSBR 51. System Status System Status This section describes how to view various system statuses. 51.1 Viewing Device Information The Device Information page displays hardware and software information about the device. This page also lists any Auxiliary files that have been installed on the device and allows you to remove them.

  • Page 662: Viewing Ethernet Port Information

    Mediant 800B 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 663 Mediant 800B MSBR 51. System Status Parameter Description Power Over Ethernet Displays whether Power over Ethernet (PoE) is active on the port. Status Power Over Ethernet Displays the power allocated to the port. Allocated Power Power Budget Displays the power budget.
  • Page 664 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 665: Carrier-Grade Alarms

    Mediant 800B MSBR 52. Carrier-Grade Alarms Carrier-Grade Alarms This section describes how to view the following types of alarms:  Active alarms - see ''Viewing Active Alarms'' on page 665  Alarm history - see ''Viewing Alarm History'' on page 666 52.1...

  • Page 666: Viewing Alarm History

    Mediant 800B MSBR 52.2 Viewing Alarm History The Alarms History page displays a list of alarms that have been raised and traps that have been cleared.  To view the list of history alarms:  Open the Alarms History page (Status & Diagnostics tab > System Status menu >...

  • Page 667: Performance Monitoring

    Mediant 800B MSBR 53. Performance Monitoring Performance Monitoring This section describes how to view performance monitoring. 53.1 Viewing MOS per Media Realm The MOS Per Media Realm page displays statistics on Media Realms (configured in ''Configuring Media Realms'' on page 259). This page provides two graphs: ...

  • Page 668: Viewing Trunk Utilization

    Mediant 800B MSBR 53.2 Viewing Trunk Utilization The Trunk Utilization page provides an X-Y graph that displays the number of active channels per trunk over time. The x-axis indicates the time; the y-axis indicates the number of active trunk channels.

  • Page 669: Viewing Quality Of Experience

    Mediant 800B MSBR 53. Performance Monitoring 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 670 Mediant 800B MSBR  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 53-3: Quality Of Experience Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view QoE for an SRD or IP Group.

  • Page 671: Viewing Average Call Duration

    Mediant 800B MSBR 53. Performance Monitoring 53.4 Viewing Average Call Duration The Average Call Duration page displays information about a specific SRD or IP Group. This page includes two graphs:  Upper graph: displays the number of calls (INVITEs). ...

  • Page 672: Network Monitoring (Probing) Two Devices

    The device can be configured to monitor the quality of the network path (network quality monitoring - NQM) between it and other AudioCodes devices. The path monitoring is done by sending packets from a "sender" device to a "responder" device and then calculating the round-trip time (RTT), packet loss (PL), and jitter.
  • Page 673 Mediant 800B MSBR 53. Performance Monitoring This feature is configured using the CLI. Below is a list of some of the CLI commands. For a full list and description of the related CLI commands, refer to the CLI Reference Guide.
  • Page 674 Mediant 800B MSBR (sender-table-0)# set source-interface-name NQM_WAN name of network interface to send packets from Note: If you want to output packets to the WAN interface, simply set NQM_WAN as the source interface name; otherwise, set the interface name to a specific interface name listed in the network interface table.
  • Page 675 Mediant 800B MSBR 53. Performance Monitoring  To view NQM results:  On the sender termination device, type the following command to view eight result rows of sender "0": # show system nqm 0 8 Figure 53-6: Example of NQM Resullts Version 6.8...
  • Page 676 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 677: Voip Status

    Mediant 800B MSBR 54. VoIP Status VoIP Status This section describes how to view VoIP status and statistics. 54.1 Viewing Trunks & Channels Status The Trunks & Channels Status page displays the status of the device's trunks and corresponding channels. It also enables you to view trunk configuration and channel information.
  • Page 678 Mediant 800B 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 679: Viewing Analog Port Information

    Mediant 800B MSBR 54. VoIP Status 54.2 Viewing Analog Port Information The Home page allows you to view detailed information on selected FXS and FXO analog ports such as RTP/RTCP and voice settings.  To view information on an analog port: Open the Home page.

  • Page 680: Viewing Active Ip Interfaces

    Mediant 800B MSBR  To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure 54-4: NFAS Group & D-Channel Status Page 54.4...

  • Page 681: Viewing Static Routes Status

    Mediant 800B MSBR 54. VoIP Status 54.6 Viewing Static Routes Status The IP Routing Status Table page displays the status of the static routes. These are routes configured in the Static Route table (see ''Configuring Static IP Routing'' on page 139) and routes through the Default Gateway.

  • Page 682: Viewing Call Counters

    Mediant 800B MSBR 54.8 Viewing Call Counters The IP to Tel Calls Count page and Tel to IP Calls Count page provide you with statistical information on incoming (IP-to-Tel) and outgoing (Tel-to-IP) calls. The statistical information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call Call Detail Record or CDR message is sent).
  • Page 683 Mediant 800B MSBR 54. VoIP Status Counter Description increment the 'Number of Failed Calls due to Other Failures' counter. Percentage of The percentage of established calls from attempted calls. Successful Calls (ASR) Number of Calls Indicates the number of calls that failed as a result of a busy line. It is...

  • Page 684: Viewing Registered Users

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

  • Page 685: Viewing Registration Status

    Mediant 800B MSBR 54. VoIP Status 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 291).

  • Page 686: Viewing Call Routing Status

    Mediant 800B MSBR 54.11 Viewing Call Routing Status The Call Routing Status page provides you with information on the current routing method used by the device. This information includes the IP address and FQDN (if used) of the Proxy server with which the device currently operates.

  • Page 687: Viewing Ip Connectivity

    Mediant 800B MSBR 54. VoIP Status 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 Table'' on page 397).
  • Page 688 Mediant 800B MSBR Column Name Description  Disable = The connectivity option is disabled, i.e., parameter 'Alt Routing Tel to IP Mode' (AltRoutingTel2IPMode ini) is set to 'None' or 'QoS'. Quality Status Determines the QoS (according to packet loss and delay) of the IP address.

  • Page 689: Reporting Information To External Party

    Mediant 800B MSBR 55. Reporting Information to External Party Reporting Information to External Party This section describes features for reporting various information to an external party. 55.1 Configuring RTCP XR RTP Control Protocol Extended Reports (RTCP XR) is a VoIP management control that defines a set of metrics containing information for assessing VoIP call quality and for diagnosing problems.
  • Page 690 Mediant 800B MSBR Group Metric Name Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Loss Density Burst Gap Loss Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold Delay...
  • Page 691 Mediant 800B MSBR 55. Reporting Information to External Party Call-ID: 441338942842012155836@10.8.61.16 CSeq: 1 PUBLISH Contact: <sip:10.8.61.16:5060> Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Event: vq-rtcpxr Expires: 3600 User-Agent: Audiocodes-Sip-Gateway-Mediant /v.6.80A.227.005 Content-Type: application/vq-rtcpxr Content-Length: 710 VQIntervalReport CallID=13746175212842012155835@10.8.61.16 LocalID: <sip:12345@10.8.61.16> RemoteID: <sip:54321@10.8.61.18> OrigID: <sip:12345@10.8.61.16> LocalAddr: IP=10.8.61.16 Port=6110 SSRC=0xce110633 RemoteAddr: IP=10.8.61.18 Port=6050 SSRC=0xffffffff...

  • Page 692: Generating Call Detail Records

    Mediant 800B MSBR Under the RTCP XR Settings group, configure the following: • 'Enable RTCP XR' (VQMonEnable) - enables voice quality monitoring and RTCP • 'Burst Threshold' (VQMonBurstHR) - defines the voice quality monitoring excessive burst alert threshold. • 'Delay Threshold' (VQMonDelayTHR) - defines the voice quality monitoring excessive delay alert threshold.

  • Page 693: Configuring Cdr Reporting

    Mediant 800B MSBR 55. Reporting Information to External Party 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.
  • Page 694 Mediant 800B MSBR Table 55-2: CDR Fields for SBC Signaling CDR Field Name Description Format SBCReportType Report Type: String  "CALL_START"  "CALL_CONNECT"  "CALL_END"  "DIALOG_START"  "DIALOG_END" EPTyp Endpoint type: String  "SBC" SIPMethod SIP message type String of up to 10 characters...
  • Page 695 Mediant 800B MSBR 55. Reporting Information to External Party 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: ...

  • Page 696: Cdr Fields For Sbc Media

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

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

    Mediant 800B MSBR 55. Reporting Information to External Party CDR Field Name Description LocalRtpIp Local RTP IP address LocalRtpPort Local RTP port RemoteRtpIp Remote RTP IP address RemoteRtpPort Remote RTP port InPackets Number of received packets Number of sent packets...
  • Page 698 Mediant 800B MSBR Field Name Description Trunk Physical trunk number Note: This field is applicable only to the Gateway application. BChan Selected B-channel Note: This field is applicable only to the Gateway application. SIP conference ID ConId Note: This field is applicable only to the Gateway application.
  • Page 699 Mediant 800B MSBR 55. Reporting Information to External Party Field Name Description 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'' on page...
  • Page 700 Mediant 800B MSBR Field Name Description Amount 0-999999 Data is stored per call and sent in the syslog as follows:  currency-type: amount multiplier for currency charge (euro or usd)  recorded-units: for unit charge (1-999999) Mult 0,001-1000 (in steps of 10) (See explanation above.)

  • Page 701: Release Reasons In Cdr

    Mediant 800B MSBR 55. Reporting Information to External Party Field Name Description SipTermDesc Description of SIP termination reason:  SIP Reason header, if exists, for example: SIP ;cause=200 ;text="Call completed elsewhere".  If no SIP Reason header exists, the description is taken from the reason text, if exists, of the SIP response code, for example: "417...
  • Page 702 Mediant 800B MSBR  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS"  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"...
  • Page 703 Mediant 800B MSBR 55. Reporting Information to External Party  "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"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION" ...

  • Page 704: Configuring Radius Accounting

    Mediant 800B MSBR 55.3 Configuring RADIUS Accounting The device can send accounting data of SIP calls as call detail records (CDR) to a RADIUS Accounting server. The device can send the accounting messages to the RADIUS server upon call release, call connection and release, or call setup and release. For a list of the CDR attributes, see the table following the procedure below.
  • Page 705 Mediant 800B MSBR 55. Reporting Information to External Party Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. time format 1 Stop Acc h323-call- The call’s originator: String Answer, Start Acc origin Answering (IP) or Originate etc...
  • Page 706 Mediant 800B MSBR Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. acct-output- Number of octets sent Numeric - Stop Acc octets for that call duration (Gateway call) acct-session- A unique accounting String 34832 Start Acc...

  • Page 707: Event Notification Using X-Detect Header

    Mediant 800B MSBR 55. Reporting Information to External Party (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 55.4 Event Notification using X-Detect Header The device can notify a remote party of the occurrence (or detection) of certain events in the media stream.
  • Page 708 Mediant 800B 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 709 Mediant 800B MSBR 55. Reporting Information to External Party CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Request=CPT,FAX SIP/2.0 200 OK Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone>;tag=1c19282 Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:101@10.33.2.53> X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906...

  • Page 710: Querying Device Channel Resources Using Sip Options

    Mediant 800B 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 711: Obtaining Status And Performance Using A Usb Flash Drive

    Mediant 800B MSBR 56. 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 651.
  • Page 712 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...
  • Page 713 Part XI Diagnostics...

  • Page 715: Syslog And Debug Recordings

    Mediant 800B MSBR 57. Syslog and Debug Recordings Syslog and Debug Recordings Syslog is an event notification protocol that enables a device to send event notification messages across IP networks to event message collectors, also known as Syslog servers. The device contains an embedded Syslog client, which sends error reports / events that it generates to a remote Syslog server using the IP / UDP protocol.

  • Page 716: Event Representation In Syslog Messages

    Mediant 800B MSBR Message Item Description numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14.
  • Page 717 Mediant 800B MSBR 57. Syslog and Debug Recordings Table 57-2: Syslog Error Name Descriptions Error Abbreviation Error Name Description Invalid Accumulated Packets Counter Invalid Channel ID Invalid Header Length Invalid Codec Type Unknown Aggregation Payload Type Invalid Routing Flag Received...

  • Page 718: 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 719: Snmp Alarms In Syslog Messages

    Mediant 800B MSBR 57. Syslog and Debug Recordings 57.1.4 SNMP Alarms in Syslog Messages SNMP alerts are sent to the Syslog server using the following formats:  Raised Alarms: RAISE-ALARM: <Alarm Name>; Textual Description: <Textual Description>; Severity <Alarm Severity>; Source <Alarm Source>; Unique ID: <Alarm Unique ID >.

  • Page 720: Configuring Web Operations To Report To Syslog

    Mediant 800B 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 721: Configuring Debug Recording

    Mediant 800B MSBR 57. Syslog and Debug Recordings  To define Web activities to report to Syslog server: Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Under the Activity Types to Report via Activity Log Messages group, select the Web actions to report to the Syslog server.

  • Page 722: Filtering Syslog Messages And Debug Recordings

    Mediant 800B MSBR From the 'Debug Recording Status' drop-down list, select Start to start the debug recording or Stop to end the recording. Click Submit. For a detailed description of these parameters, see ''Syslog, CDR and Debug Parameters'' on page 788.
  • Page 723 Mediant 800B MSBR 57. Syslog and Debug Recordings Parameter Description  CLI: filter-type [1] Any (default) [LoggingFilters_FilterType]  [2] Trunk ID = Filters according to a specified Trunk ID (applicable only to the Gateway application)  [3] Trunk Group ID = Filters according to a specified Trunk Group ID (applicable only to the Gateway application) ...

  • Page 724: Filtering Ip Network Traces

    Mediant 800B MSBR Parameter Description Capture Type Enables debug recordings for the defined logging filter and defines CLI: capture-type what to record: [LoggingFilters_CaptureType]  [0] None (default)  [1] Signaling = Information related to signaling such as SIP signaling messages, Syslog, CDR, and the device's internal processing messages.

  • Page 725: 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 726: Collecting Debug Recording Messages

    Close the Message Log page by accessing any another page in the Web interface. 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: •...
  • Page 727 Mediant 800B MSBR 57. Syslog and Debug Recordings The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: For ISDN trace messages, the additional header, "NetBricks Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below:...

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

    Calling party number: '201' Called party number: '102' Sending complete For CAS trace messages, the additional header "CAS Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below: AUDIOCODES DEBUG RECORDING CAS Trace Timer: 1145504439...

  • Page 729: Debug Capturing On Physical Voip Interfaces

    Mediant 800B MSBR 57. Syslog and Debug Recordings 57.9 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets). The captured traffic can be saved in a PCAP-format file (suitable for Wireshark) to a TFTP (default) or an FTP server.

  • Page 730: Configuring Termination Of Debug Capture Upon Event

    Mediant 800B 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 731: Self-Testing

    Mediant 800B MSBR 58. Self-Testing Self-Testing The device features the following self-testing modes to identify faulty hardware components:  Detailed Test (Configurable): This test verifies the correct functioning of the different hardware components on the device. This test is done when the device is taken out of service (i.e., not in regular service for processing calls).
  • Page 732 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 733: 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 734 Mediant 800B 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 735: Re-Initializing Device With "Purified" Configuration

    Mediant 800B MSBR 60. Re-initializing Device with "Purified" Configuration Re-initializing Device with "Purified" Configuration You can apply a "purified" version of the current configuration to enable proper functioning of the device. This is useful when the device has correct configuration, but for some or other reason it does not function properly.
  • Page 736 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 737: Analog Line Testing

    Mediant 800B MSBR 61. Analog Line Testing Analog Line Testing 61.1 FXO Line Testing The device can test the telephone lines connected to its FXO ports, using the SNMP acAnalogFxoLineTestTable 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: ...
  • Page 738 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 739: 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 740 Mediant 800B 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 741 Mediant 800B MSBR 62. Testing SIP Signaling Calls Parameter Description Route By Defines the type of routing method. This applies to incoming and CLI: route-by outgoing calls. [Test_Call_RouteBy]  [0] GW Tel2IP = (Default) Calls are matched by (or routed to) an SRD and Application type (defined in the SRD and Application Type parameters below).
  • Page 742 Mediant 800B MSBR Parameter Description Bandwidth Profile Assigns a Bandwidth Profile to the test call. To configure CLI: bandwidth-profile Bandwidth Profiles, see ''Configuring Bandwidth Profiles'' on page [Test_Call_BWProfile] 252. Authentication Tab Note: These parameters are applicable only if the Call Party parameter is set to Caller.
  • Page 743 Mediant 800B MSBR 62. Testing SIP Signaling Calls Parameter Description Test Mode Defines the test session mode. CLI: test-mode  [0] Once = (Default) The test runs until the lowest value [Test_Call_TestMode] between the following is reached:  Maximum channels is reached for the test session, configured by 'Maximum Channels for Session'.

  • Page 744: Starting And Stopping Test Calls

    Mediant 800B MSBR 62.2 Starting and Stopping Test Calls The following procedure describes how to start, stop, and restart test calls.  To start, stop, and restart a test call: In the Test Call table, select the required test call entry; the Actions button appears above the table.
  • Page 745 Mediant 800B MSBR 62. Testing SIP Signaling Calls Click the Show/Hide button; the call statistics are displayed in the Test Statistics pane located below the table, as shown below: Figure 62-2: Viewing Test Call Statistics The 'Test Statistics' pane displays the following test session information: ...

  • Page 746: Configuring Dtmf Tones For Test Calls

    Mediant 800B MSBR • "Done - Established Calls: <number of established calls>, ASR: <%>": test call has been successfully completed (or was prematurely stopped by clicking the Drop Call command) and shows the following: ♦ Total number of test calls that were established.

  • Page 747: Configuring Basic Test Call

    Mediant 800B MSBR 62. Testing SIP Signaling Calls 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.

  • Page 748: Configuring Sbc Test Call With External Proxy

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

  • Page 749: Test Call Configuration Examples

    Mediant 800B MSBR 62. Testing SIP Signaling Calls  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Parameters'' on page 787): Open the Test Call Settings page (Configuration tab > System menu > Test Call >...
  • Page 750 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 751 Mediant 800B MSBR 62. Testing SIP Signaling Calls  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 752 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 753: Data-Router Debugging

    Mediant 800B MSBR 63. Data-Router Debugging Data-Router Debugging # ping <ip address> source voip interface [interface name] repeat size [YL] in ipv4 you can ping from both voip or data interfaces 63.1 Loopback on WAN Interface Debugging You can perform loopback testing on the WAN interface for debugging purposes. Loopback debugging can be activated on any WAN interface (name or type).

  • Page 754: Performing A Traceroute

    Mediant 800B 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 755: Pinging A Remote Host Or Ip Address

    Mediant 800B MSBR 64. Pinging a Remote Host or IP Address Pinging a Remote Host or IP Address You can verify the network connectivity with a remote host or IP address by pinging the network entity.  IPv4: The ping to an IPv4 address can be done from any of the device's VoIP or data- router interfaces that is configured with an IPv4 address.
  • Page 756 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...

  • Page 757: Troubleshooting Using A Usb Flash Drive

    Mediant 800B MSBR 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 651.
  • Page 758 Mediant 800B MSBR This page is intentionally left blank. User's Manual Document #: LTRT-12813...
  • Page 759 Part XII Appendix...

  • Page 761: Dialing Plan Notation For Routing And Manipulation

    Mediant 800B MSBR 66. Dialing Plan Notation for Routing and Manipulation Dialing Plan Notation for Routing and Manipulation The device supports flexible dialing plan notations for denoting the prefix and/or suffix source and/or destination numbers and SIP URI user names in the routing and manipulation tables.
  • Page 762 Mediant 800B MSBR Notation Description  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.

  • Page 763: Configuration Parameters Reference

    Mediant 800B MSBR 67. Configuration Parameters Reference Configuration Parameters Reference The device's VoIP functionality (not data-routing functionality) configuration parameters, default values, and their descriptions are documented in this section. Note: Parameters and values enclosed in square brackets [...] represent the ini file parameters and their enumeration values.

  • Page 764: Web Parameters

    Mediant 800B MSBR Parameter Description Web: Web and Telnet This table configures up to ten IP addresses that are permitted to Access List Table access the device's Web interface and Telnet interfaces. Access from EMS: Web Access an undefined IP address is denied. When no IP addresses are defined Addresses in this table, this security feature is inactive (i.e., the device can be...
  • Page 765 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Deny Authentication Timer Defines the duration (in seconds) for which login to the EMS: WEB Deny Authentication Timer Web interface is denied from a specific IP address (for all [DenyAuthenticationTimer] users) when the number of failed login attempts has exceeded the maximum.
  • Page 766 Mediant 800B MSBR Parameter Description [ResetWebPassword] Resets the username and password of the primary ("Admin") and secondary ("User") accounts to their default settings ("Admin" and "Admin" respectively), and deletes all other users that may have been configured.  [0] = (Default) Password and username retain their values.

  • Page 767: Telnet Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.1.3 Telnet Parameters The Telnet parameters are described in the table below. Table 67-3: Telnet Parameters Parameter Description Web: Embedded Telnet Server Enables the device's embedded Telnet server. Telnet is disabled by EMS: Server Enable default for security.

  • Page 768: Snmp Parameters

    Mediant 800B MSBR Parameter Description password> (e.g., $1$S3p+fno=).  [1] Enable = All passwords are hidden and replaced by an asterisk (*). 67.1.5 SNMP Parameters The SNMP parameters are described in the table below. Table 67-5: SNMP Parameters Parameter Description Web: Enable SNMP Enables SNMP.
  • Page 769 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description required. [acUserInputAlarmDescription] Defines the description of the input alarm. Defines the severity of the input alarm. [acUserInputAlarmSeverity] [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).
  • Page 770 Mediant 800B MSBR Parameter Description Web: Trap User Defines the SNMPv3 USM user or SNMPv2 user to CLI: trap-user associate with the trap destination. This determines the [SNMPManagerTrapUser_x] trap format, authentication level, and encryption level. By default, it is associated with the SNMPv2 user (SNMP trap community string).

  • Page 771: Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description security level authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2. For a description of this table, see ''Configuring SNMP V3 Users'' on page 91. 67.1.6 TR-069 Parameters The TR-069 parameters are described in the table below.

  • Page 772: Serial Parameters

    Mediant 800B MSBR Parameter Description Web: Password Defines the login password that the device uses for CLI: acs-password authenticated access to the ACS. [TR069AcsPassword] The valid value is a string of up to 256 characters. By default, no password is defined.

  • Page 773: Auxiliary And Configuration File Name Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Note: For this parameter to take effect, a device reset is required. EMS: Data Defines the RS-232 data bit. [SerialData]  [7] = 7-bit  [8] = (Default) 8-bit Note: For this parameter to take effect, a device reset is required.

  • Page 774: Automatic Update 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 User's Guide). [DialPlanFileName] [UserInfoFileName] Defines the name (and path) of the file containing the User Information data.
  • Page 775 The valid value is a string of up to 511 characters. By default, this parameter is not defined. In other words, the User-Agent header is set to "Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>)”, where the tags are replaced with actual values. Notes: ...
  • Page 776 Mediant 800B 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 777 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description CLI: voice-configuration Defines the name of the ini file and the path to the server (IP [IniFileURL] address or FQDN) on which it is located. The ini file can be loaded using HTTP/HTTPS.

  • Page 778: Networking Parameters

    Mediant 800B MSBR 67.2 Networking Parameters This subsection describes the device's networking parameters. 67.2.1 Multiple VoIP Network Interfaces and VLAN Parameters The IP network interfaces and VLAN parameters are described in the table below. Table 67-10: IP Network Interfaces and VLAN Parameters...

  • Page 779: Open Solution Network (Osn) Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.2.3 Open Solution Network (OSN) Parameters The OSN server parameters are described in the table below. Table 67-12: OSN Parameters Parameter Description Web: OSN Native VLAN Defines the OSN Native VLAN ID. The valid value is 0 to 4000. When set to 0 (default), the OSN uses the CLI: configure system >...

  • Page 780: Nat And Stun Parameters

    Mediant 800B MSBR Parameter Description [PremiumServiceClassMediaDiffServ] parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page 314. 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.

  • Page 781: Nfs Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description For more information on handling calls from UAs behind NAT, see ''First Incoming Packet Mechanism'' on page 154. Web: NAT IP Address Defines the global (public) IP address of the device to enable static NAT EMS: Static NAT IP between the device and the Internet.

  • Page 782: Dns Parameters

    Mediant 800B MSBR 67.2.7 DNS Parameters The Domain name System (DNS) parameters are described in the table below. Table 67-16: DNS Parameters Parameter Description Internal DNS Table Web: Internal DNS Table This table parameter defines the internal DNS table for resolving host EMS: DNS Information names into IP addresses.

  • Page 783: Ntp And Daylight Saving Time Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  For a detailed description of DHCP, see ''DHCP-based Provisioning'' on page 631.  This parameter is a "hidden" parameter. Once defined and saved to flash memory, its value doesn't revert to default even if the parameter doesn't appear in the ini file.
  • Page 784 Mediant 800B MSBR Parameter Description Web: NTP Authentication Key Defines the NTP authentication key identifier for authenticating NTP Identifier messages. The identifier must match the value configured on the CLI: configure system > ntp > NTP server. The NTP server may have several keys configured for auth-key-id different clients;...

  • Page 785: Power Over Ethernet Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.2.10 Power over Ethernet Parameters The power-over-Ethernet (PoE) parameters are described in the table below. Table 67-19: PoE Parameters Parameter Description Web: Power over Ethernet This table enables PoE (IEEE 802.3af-2003 and IEEE 802.3at) per LAN...
  • Page 786 Mediant 800B MSBR Parameter Description Web: Enable LAN Watchdog Enables the LAN watchdog feature, which detects any logical [EnableLanWatchDog] network failure.  [0] Disable (default)  [1] Enable & Reset = Enables LAN watchdog. If the device detects a network failure, the device resets.

  • Page 787: Sip Test Call Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Manual. Web: Delay After Reset [sec] Defines the time interval (in seconds) that the device's operation is CLI: delay-after-reset delayed after a reset. [GWAppDelayTime] The valid range is 0 to 45. The default is 7 seconds.

  • Page 788: Syslog, Cdr And Debug Parameters

    Mediant 800B MSBR Parameter Description Web: SBC Test ID Defines the SBC test call prefix (ID) for identifying SBC test calls that CLI: sbc-test-id traverse the device to register with an external routing entity such as an [SBCtestID] IP PBX or proxy server.
  • Page 789 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  By default, logs are also sent to the RS-232 serial port. For how to establish serial communication with the device, refer to the Installation Manual. Web/EMS: Syslog Server IP Defines the IP address (in dotted-decimal notation) of the computer Address on which the Syslog server is running.
  • Page 790 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 791 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Debug Level High Defines the threshold (in percentage) for automatically switching to a Threshold different debug level, depending on CPU usage. The parameter is CLI: debug-level-high- applicable only if the 'Syslog CPU Protection' parameter is enabled.
  • Page 792 Mediant 800B MSBR Parameter Description Maintenance Actions page. Note: For this option to take effect, a device reset is required.  [fb] Flash Memory Burning = Saving configuration with burn to flash (in the Maintenance Actions page).  [swu] Device Software Update = Software updates (i.e., loading of cmp file) through the Software Upgrade Wizard.

  • Page 793: Resource Allocation Indication Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Debug Recording Status Activates or de-activates debug recording. CLI: configure system >  [0] Stop (default) logging > dbg-rec-status  [1] Start [DebugRecordingStatus] Web: Enable Core Dump Enables the automatic generation of a Core Dump file upon a device [EnableCoreDump] crash.

  • Page 794: Security Parameters

    Mediant 800B MSBR Parameter Description [RAILowThreshold] Defines the low threshold percentage of total calls that are active (busy endpoints). When the percentage of the device's busy endpoints falls below this low threshold, the device sends an SNMP acBoardCallResourcesAlarm alarm trap with a 'cleared' alarm status.
  • Page 795 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description receives at least a minimum number of consecutive packets (configured by New<media type>StreamPackets) from a different source(s) and the device has not received packets from the current stream for a user-defined period (TimeoutToRelatch<media type>Msec), it latches onto the next...

  • Page 796: Https Parameters

    Mediant 800B MSBR Parameter Description another stream. The valid range is any value from 0. The default is 200. Timeout To Relatch SRTP Defines a period (msec) during which if no packets are received [TimeoutToRelatchSRTPMsec] from the current SRTP session, the channel can re-latch onto another stream.

  • Page 797: Srtp Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  For this parameter to take effect, a device reset is required.  If the installed Software License Key includes the Strong Encryption feature, the default of this parameter is changed to ‘RC4:EXP’, enabling RC-128bit encryption.
  • Page 798 Mediant 800B MSBR Parameter Description Web: Master Key Identifier Global parameter that defines the size (in bytes) of the Master Key (MKI) Size Identifier (MKI) in SRTP Tx packets. You can also configure this EMS: Packet MKI Size functionality per specific calls, using IP Profiles CLI: SRTP-tx-packet-MKI-size (IpProfile_MKISize).
  • Page 799 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Aria Protocol Support Enables ARIA algorithm cipher encryption for SRTP. This is an CLI: ARIA-protocol-support alternative option to the existing support for the AES algorithm. [AriaProtocolSupport] ARIA is a symmetric key block cipher algorithm standard developed by the Korean National Security Research Institute.

  • Page 800: Tls Parameters

    Mediant 800B MSBR 67.4.4 TLS Parameters The Transport Layer Security (TLS) parameters are described in the table below. Table 67-27: TLS Parameters Parameter Description TLS Contexts Table Web: TLS Contexts Table Defines SSL/TLS certificates. CLI: configure system > tls #...
  • Page 801 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description server or client for the TLS connection. When the device receives a remote certificate and this parameter is not disabled, the IP address from which the certificate is received is compared with the addresses defined for the Proxy Sets.

  • Page 802: Ssh Parameters

    Mediant 800B 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 803: Taacs+ Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Note: The last SSH login information is cleared when the device is reset. Web: Max Login Attempts Defines the maximum SSH login attempts allowed for entering an CLI: ssh-max-login-attempts incorrect password by an administrator before the SSH session is rejected.

  • Page 804: Ocsp Parameters

    Mediant 800B MSBR Parameter Description [EnableIDS] Note: For this parameter to take effect, a device reset is required. 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.

  • Page 805: Quality Of Experience Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  CLI: enable [1] Enable [OCSPEnable] For a description of OCSP, see Configuring Certificate Revocation Checking (OCSP). Web: Primary Server IP Defines the IP address of the OCSP server. EMS: OCSP Server IP The default IP address is 0.0.0.0.
  • Page 806 Mediant 800B MSBR Parameter Description Web: Quality of Experience This table parameter defines Quality of Experience Profiles. Profile The format of the ini file table parameter is as follows: CLI: configure voip/qoe qoe- [QOEProfile] profile FORMAT QOEProfile_Index = QOEProfile_Name, [QOEProfile] QOEProfile_SensitivityLevel;...

  • Page 807: Control Network Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Media Enhancement This table parameter defines Media Enhancement Rules. Rules The format of the ini file table parameter is as follows: CLI: configure voip/qoe [MediaEnhancementRules] media-enhancement-rules FORMAT MediaEnhancementRules_Index = [MediaEnhancementRules]...
  • Page 808 Mediant 800B MSBR Parameter Description Authentication per Port Table Web: Authentication Table This table parameter defines a user name and password for EMS: SIP Endpoints > authenticating each device port. The format of the ini file table Authentication parameter is as follows:...
  • Page 809 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web/EMS: Proxy Name Defines the Home Proxy domain name. If specified, this name CLI: proxy-name is used as the Request-URI in REGISTER, INVITE and other [ProxyName] SIP messages, and as the host part of the To header in INVITE messages.
  • Page 810 Mediant 800B MSBR Parameter Description parameter EnableProxyKeepAlive to 1 or 2. Web/EMS: Prefer Routing Table Determines whether the device's internal routing table takes CLI: prefer-routing-table precedence over a Proxy for routing calls. [PreferRouteTable]  [0] No = (Default) Only a Proxy server is used to route calls.
  • Page 811 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description performed. The device uses the first host name received from the SRV query. The device then performs a DNS A- record query for the host name to locate an IP address.
  • Page 812 Mediant 800B MSBR Parameter Description uses the OPTIONS request as a keep-alive message with its primary and redundant SIP proxy servers (i.e., the EnableProxyKeepAlive parameter is set to 1).  [0] No = (Default) Device's IP address is used in keep-alive OPTIONS messages.
  • Page 813 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [1] INVITE Only = Challenges issued for INVITE requests are cached. This prevents a mixture of REGISTER and INVITE authorizations.  [2] Full = Caches all challenges from the proxies.
  • Page 814 Mediant 800B MSBR Parameter Description Notes:  This parameter is applicable only to the Gateway application.  The device sends a REGISTER request for each channel or for the entire device (according to the AuthenticationMode parameter). Web/EMS: Registrar Name Defines the Registrar domain name. If specified, the name is CLI: registrar-name used as the Request-URI in REGISTER messages.
  • Page 815 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description messages when the parameter 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.
  • Page 816 Mediant 800B MSBR Parameter Description Trying provisional response (indicative of a home proxy server failure). Note: This parameter is applicable only to the Gateway application. Web: ReRegister On Connection Enables the device to perform SIP re-registration upon Failure TCP/TLS connection failure.
  • Page 817 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  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] ...
  • Page 818 Mediant 800B MSBR Parameter Description When the device sends a REGISTER message, the Route header includes either the Proxy's FQDN, or IP address and port according to the configured Proxy Set, for example: Route: <sip:10.10.10.10;lr;transport=udp> Route: <sip: pcscf- gm.ims.rr.com;lr;transport=udp> EMS: Ping Pong Keep Alive...

  • Page 819: Network Application Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Max Generated Register Rate Defines the maximum number of user register requests that the CLI: configure voip/sip-definition device can send to a proxy (or registrar) server per second. proxy-and-registration/max-gen-reg- This feature is useful in that it can be used to prevent an...
  • Page 820 Mediant 800B MSBR Parameter Description  TCP keepalive is enabled per SIP Interface in the SIP Interface table. [TCPKeepAliveInterval] Defines the interval (in sec) between consecutive keep-alive probes, regardless of what the connection has exchanged in the meantime. The valid value is 10 to 65,000. The default is 10.

  • Page 821: General Sip Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Remote Media This table parameter defines Remote Media Subnets. Subnet The format of the ini file table parameter is as follows: EMS: Remote Media [RemoteMediaSubnet] Subnet FORMAT RemoteMediaSubnet_Index = RemoteMediaSubnet_Realm, CLI: configure voip >...
  • Page 822  '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 Defines the maximum size (in Kbytes) for each SIP message that can Message Length [KB] be sent over the network. The device rejects messages exceeding this [MaxSIPMessageLength] user-defined size.
  • Page 823 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description The X-RTP-Stat header contains the following fields:  PS=<voice packets sent>  OS=<voice octets sent>  PR=<voice packets received>  OR=<voice octets received>  PL=<receive packet loss>  JI=<jitter in ms>...
  • Page 824 Mediant 800B MSBR Parameter Description  This parameter is applicable only to the Gateway application. Web/EMS: Enable Early 183 Global parameter that enables the device to send SIP 183 responses CLI: early-183 with SDP to the IP upon receipt of INVITE messages. You can also...
  • Page 825 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [1] = The device sends a SIP 4xx response when the EnableEarlyMedia parameter is set to 0.  [2] = The device always sends a SIP 4xx response, even if he EnableEarlyMedia parameter is set to 1.
  • Page 826 Mediant 800B MSBR Parameter Description  [1] Don’t reply OPTIONS = The device does not respond to SIP OPTIONS received from the proxy associated with Trunk Group 1 when all its trunks are down.  [2] Don’t send Keep-Alive = The device does not send keep-alive messages to the proxy associated with Trunk Group 1 when all its trunks are down.
  • Page 827 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [1] = Enable. The device assumes that the G.711 coder received in the INVITE SDP offer is a VBD coder. For example, if the device is configured with G.729 and G.711 VBD coders and it receives an INVITE with an SDP offer containing G.729 and “regular”...
  • Page 828 Mediant 800B MSBR Parameter Description [LocalSIPPort] Web: SIP TCP Local Port Defines the local TCP port for SIP messages. EMS: TCP Local SIP Port The valid range is 1 to 65535. The default is 5060. CLI: sip-tcp-local-port [TCPLocalSIPPort] Web: SIP TLS Local Port Defines the local TLS port for SIP messages.
  • Page 829 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description EnableTCPConnectionReuse parameter to 1. Web/EMS: Reliable Enables setting of all TCP/TLS connections as persistent and Connection Persistent Mode therefore, not released. CLI: reliable-conn-persistent  [0] = (Default) Disable. All TCP connections (except those that are...
  • Page 830 Mediant 800B MSBR Parameter Description Web: Enable Remote Party Enables Remote-Party-Identity headers for calling and called numbers for Tel-to-IP calls. EMS: Enable RPI Header  [0] Disable (default). CLI: remote-party-id  [1] Enable = Remote-Party-Identity headers are generated in SIP [EnableRPIheader] INVITE messages for both called and calling numbers.
  • Page 831 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description number / name is not associated with the call, the 'tgrp' parameter isn't included. If a 'tgrp' value is specified in incoming messages, it is ignored.  [2] Send and Receive = The functionality of outgoing SIP messages is identical to the functionality described for option [1].

  • Page 832: According To The Inbound Ip Routing Table

    Mediant 800B MSBR Parameter Description “tgrp=ccdata;trunk-context=dsn.mil”. If the Bearer Capability IE contains “Speech”, the INVITE in this case does not contain tgrp and trunk-context parameters. Note: IP-to-Tel configuration (using the PSTNPrefix parameter) overrides the 'tgrp' parameter in incoming INVITE messages.
  • Page 833 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Record (AOR). For example, in call transfer where user A is talking to user B, and user A wants to transfer the call to user C. User A sends a REFER to user C: REFER sip:C@domain.com SIP/2.0...
  • Page 834 EMS: User Agent Display value>/software version' is used, for example: Info User-Agent: myproduct/v.6.80A.227.005 CLI: user-agent-info If not configured, the default string, <AudioCodes product- [UserAgentDisplayInfo] name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 800B MSBR/v.6.80A.227.005 The maximum string length is 50 characters.
  • Page 835 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description INVITE sent to the call made un-hold (retrieved). The used coder is therefore, re-negotiated. This parameter is useful in the following call scenario example: Party A calls party B and coder G.711 is chosen.
  • Page 836 Mediant 800B MSBR Parameter Description response to indicate how long the service is expected to be unavailable to the requesting SIP client. The device maintains a list 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.
  • Page 837 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [EnableReasonHeader] [1] Enable (default) Web/EMS: Gateway Name Defines a name for the device (e.g., device123.com). This name is CLI: gw-name used as the host part of the SIP URI in the From header. If not [SIPGatewayName] specified, the device's IP address is used instead (default).
  • Page 838 Mediant 800B MSBR Parameter Description even customers blocking their Caller ID can be identified by the service provider. Typically, if the device receives a call with blocked Caller ID from the PSTN side (e.g., Trunk connected to a PBX), it sends an INVITE to the IP with a From header as follows: From: “anonymous”...
  • Page 839 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Enable X-Channel Determines whether the SIP X-Channel header is added to SIP Header messages for providing information on the physical Trunk/B-channel EMS: X Channel Header on which the call is received or placed.
  • Page 840 Mediant 800B MSBR Parameter Description Web: IP to IP Application Enables the IP-to-IP Call Routing application. CLI: enable-ip2ip  [0] Disable (default) [EnableIP2IPApplication]  [1] Enable Note: For this parameter to take effect, a device reset is required. Web: Enable RFC 4117 Enables transcoding of calls according to RFC 4117.
  • Page 841 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [UseSIPURIForDiversionH [0] = 'tel:' (default) eader]  [1] = 'sip:' [TimeoutBetween100And1 Defines the timeout (in msec) between receiving a 100 Trying response and a subsequent 18x response. If a 18x response is not received within this timeout period, the call is disconnected.
  • Page 842 Mediant 800B MSBR Parameter Description and even if the codec’s SCE is disabled, CNG occurs. If the ComfortNoiseNegotiation parameter is disabled, then the device does not send “CN” in the SDP. However, if the codec’s SCE is enabled, then CNG occurs.
  • Page 843 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description If the call is a regular incoming call and the FXS user on-hooks the phone without intending to disconnect the call, the softswitch does not disconnect the call (during the regret time).
  • Page 844 Mediant 800B MSBR Parameter Description  Configure E1/T1 Transparent protocol type (set the ProtocoType parameter to 5 or 6).  Enable the TDM-over-IP feature (set the EnableTDMoverIP parameter to 1).  To configure the RTP Only mode per trunk, use the RTPOnlyModeForTrunk_x parameter.
  • Page 845 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description For RO that is included in a 4xx response when SIT-RO (Reorder - System [SITQ850CauseForRO] Busy Special Information Tone) is detected from the Tel for IP-to-Tel calls. The valid range is 0 to 127. The default is -1 (not configured).
  • Page 846 Mediant 800B MSBR Parameter Description  Analog: See the LifeLineType parameter for complementary optional behavior.  Digital: The Busy Out behavior depends on the PSTN protocol type.  Digital: The Busy-Out condition can also be applied to a specific Trunk Group. If there is no connectivity to the Serving IP Group of a...
  • Page 847 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  This parameter is applicable only to digital interfaces.  To configure the method for setting Out-of-Service state per trunk, use the DigitalOOSBehaviorForTrunk_x parameter.  To configure the timeout interval (in seconds) for Out-of-Service...
  • Page 848 Mediant 800B MSBR Parameter Description Web: Number of RTX Defines the number of retransmitted INVITE/REGISTER messages Before Hot-Swap before the call is routed (hot swap) to another Proxy/Registrar. EMS: Proxy Hot Swap Rtx The valid range is 1 to 30. The default is 3.

  • Page 849: Coders And Profile Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.8 Coders and Profile Parameters The profile parameters are described in the table below. Table 67-36: Profile Parameters Parameter Description Coders Table / Coder Groups Table Web: Coders Table/Coder This table parameter defines the device's coders. Each group can consist Group Settings of up to 10 coders.
  • Page 850 Mediant 800B MSBR Parameter Description IpProfile_IsDTMFUsed, IpProfile_PlayRBTone2IP, IpProfile_EnableEarlyMedia, IpProfile_ProgressIndicator2IP, IpProfile_EnableEchoCanceller, IpProfile_CopyDest2RedirectNumber, IpProfile_MediaSecurityBehaviour, IpProfile_CallLimit, IpProfile_DisconnectOnBrokenConnection, IpProfile_FirstTxDtmfOption, IpProfile_SecondTxDtmfOption, IpProfile_RxDTMFOption, IpProfile_EnableHold, IpProfile_InputGain, IpProfile_VoiceVolume, IpProfile_AddIEInSetup, IpProfile_SBCExtensionCodersGroupID, IpProfile_MediaIPVersionPreference, IpProfile_TranscodingMode, IpProfile_SBCAllowedMediaTypes, IpProfile_SBCAllowedCodersGroupID, IpProfile_SBCAllowedVideoCodersGroupID, IpProfile_SBCAllowedCodersMode, IpProfile_SBCMediaSecurityBehaviour, IpProfile_SBCRFC2833Behavior, IpProfile_SBCAlternativeDTMFMethod, IpProfile_SBCAssertIdentity, IpProfile_AMDSensitivityParameterSuit, IpProfile_AMDSensitivityLevel, IpProfile_AMDMaxGreetingTime, IpProfile_AMDMaxPostSilenceGreetingTime, IpProfile_SBCDiversionMode, IpProfile_SBCHistoryInfoMode, IpProfile_EnableQSIGTunneling, IpProfile_SBCFaxCodersGroupID,...

  • Page 851: Channel Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description The format of the ini file table parameter is as follows: [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay,...
  • Page 852 Mediant 800B MSBR Parameter Description Note: If this functionality is configured for a specific profile, the settings of this global parameter is ignored for calls associated with the profile. EMS: Payload Format Determines the bit ordering of the G.726/G.727 voice CLI: G726-voice-payload-format payload format.
  • Page 853 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Attenuation Intensity Defines the acoustic echo suppressor signals identified as CLI: acoustic-echo-suppressor- echo attenuation intensity. attenuation-intensity The valid range is 0 to 3. The default is 0. [AcousticEchoSuppAttenuationIntensity] Web: Max ERL Threshold - DB...

  • Page 854: Coder Parameters

    Mediant 800B MSBR Parameter Description The valid range is 0 to 1023. The default is 0. Web: Answer Detector Silence Time Currently, not supported. [AnswerDetectorSilenceTime] Web: Answer Detector Redirection Currently, not supported. [AnswerDetectorRedirection] Web: Answer Detector Sensitivity Defines the Answer Detector sensitivity.

  • Page 855: Dtmf Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.9.3 DTMF Parameters The dual-tone multi-frequency (DTMF) parameters are described in the table below. Table 67-39: 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 856: Rtp, Rtcp And T.38 Parameters

    Mediant 800B MSBR Parameter Description [NTEMaxDuration] the DTMF signal duration on the TDM side. The range is -1 to 200,000,000 msec. The default is -1 (i.e., NTE stops only upon detection of an End event). 67.9.4 RTP, RTCP and T.38 Parameters The RTP, RTCP and T.38 parameters are described in the table below.
  • Page 857 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [1] Enable When enabled, the device includes in the SDP message the RTP payload type "RED" and the payload type configured by the parameter RFC2198PayloadType. a=rtpmap:<PT> RED/8000 Where <PT> is the payload type as defined by RFC2198PayloadType.
  • Page 858 Mediant 800B MSBR Parameter Description [EnableDetectRemoteMACChange] Determines whether the device changes the RTP packets according to the MAC address of received RTP packets and according to Gratuitous Address Resolution Protocol (GARP) messages.  [0] = Nothing is changed.  [1] = If the device receives RTP packets with a different...
  • Page 859 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description EMS: No Op Payload Type Defines the payload type of No-Op packets. CLI: no-operation-interval The valid range is 96 to 127 (for the range of Dynamic RTP [RTPNoOpPayloadType] Payload Type for all types of non hard-coded RTP Payload types, refer to RFC 3551).
  • Page 860 Mediant 800B MSBR Parameter Description shorter than this interval, RTCP XR is sent only at the end of the call. The valid value range is 0 to 65,535. The default is 5,000. Web: Disable RTCP XR Interval Determines whether RTCP report intervals are randomized or...

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

    Mediant 800B MSBR 67. Configuration Parameters Reference 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-41: Fax and Modem Parameters Parameter Description Web: Fax Transport Mode Determines the fax transport mode used by the device.
  • Page 862 Mediant 800B MSBR Parameter Description  EMS: V32 Transport [2] Enable Bypass (default) CLI: V32-modem-transport-type  [3] Events Only = Transparent with Events. [V32ModemTransportType] Notes:  This parameter applies only to V.32 and V.32bis modems.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType).
  • Page 863 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description CLI: configure voip > sip- interval, it ends the voice session and sends a T.38 or VBD re- definition general-settings > fax- INVITE message to the IP side and processes the fax. If the...
  • Page 864 Mediant 800B MSBR Parameter Description V.34 / T.38 fax relay. For non-T.38 V.34 supporting devices, configuration greater than 14.4 kbps is truncated to 14.4 kbps. Web: Fax Relay ECM Enable Enables Error Correction Mode (ECM) mode during fax relay. EMS: Relay ECM Enable ...
  • Page 865 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description EMS: Basic Packet Interval Defines the basic frame size used during fax/modem bypass CLI: modem-bypass-output-gain sessions. [FaxModemBypassBasicRTPP  [0] = (Default) Determined internally acketInterval]  [1] = 5 msec (not recommended) ...
  • Page 866 Mediant 800B MSBR Parameter Description Web/EMS: T.38 Max Datagram Defines the maximum size of a T.38 datagram that the device can Size receive. This value is included in the outgoing SDP when T.38 is CLI: t38-mx-datagram-sz used. [T38MaxDatagramSize] The valid range is 120 to 600. The default is 560.

  • Page 867: Dtmf And Hook-Flash Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description originating fax does not wait for an answer, but immediately starts sending T.38 packets to the terminating fax machine. Note: To enable No-Op packet transmission, use the NoOpEnable and NoOpInterval parameters.
  • Page 868 Mediant 800B MSBR Parameter Description Web/EMS: Hook-Flash Code For analog interfaces: Defines the digit pattern that when CLI: hook-flash-code received from the Tel side, indicates a Hook Flash event. [HookFlashCode] For digital interfaces: Defines the digit pattern used by the PBX to indicate a Hook Flash event.
  • Page 869 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Min. Flash-Hook Detection Defines the minimum time (in msec) for detection of a hook-flash Period [msec] event. Detection is guaranteed for hook-flash periods of at least EMS: Min Flash Hook Time 60 msec (when setting the minimum time to 25).
  • Page 870 Mediant 800B MSBR Parameter Description  [3] INFO (Cisco) = Sends DTMF digits according to Cisco format.  [4] RFC 2833.  [5] INFO (Korea) = Sends DTMF digits according to Korea Telecom format. The format of the ini file table parameter is as follows: [TxDTMFOption] FORMAT TxDTMFOption_Index = TxDTMFOption_Type;...
  • Page 871 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web/EMS: Enable Digit Delivery Enables the Digit Delivery feature whereby DTMF digits are sent to IP to the destination IP address after the Tel-to-IP call is answered. CLI: digit-delivery-2ip  [0] Disable (default).

  • Page 872: Digit Collection And Dial Plan Parameters

    Mediant 800B MSBR Parameter Description [ReplaceNumberSignWithEscape escape character (%23) in outgoing SIP messages for Tel-to-IP Char] calls.  [0] Disable (default).  [1] Enable = All number signs #, received in the dialed DTMF digits are replaced in the outgoing SIP Request-URI and To headers with the escape sign %23.
  • Page 873 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description alPlanIndex] The valid value range is 0 to 7, defining the Dial Plan index [Plan x] in the Dial Plan file. The default is -1 (disabled). For more information on this feature, see ''Modifying ISDN-to-IP Calling Party Number'' on page 613.

  • Page 874: Voice Mail Parameters

    Mediant 800B MSBR Parameter Description Notes:  Instead of using this parameter, Digit Mapping rules can be configured.  For FXS/FXO interfaces: Dialing ends when any of the following scenarios occur:  Maximum number of digits is dialed  Interdigit Timeout (TimeBetweenDigits) expires ...
  • Page 875 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description This is implemented for sending unsolicited SIP NOTIFY messages received from the Voice Mail server to an IP Group (configured using the NotificationIPGroupID parameter).  [8] ETSI = Euro ISDN, according to ETS 300 745-1 V1.2.4, section 9.5.1.1.
  • Page 876 Mediant 800B MSBR Parameter Description the PBX, dials the digits (that are received in the Refer-To header), and then immediately releases the line (i.e., on- hook). The PBX performs the transfer internally.  E1/T1 CAS: When a SIP REFER message is received,...
  • Page 877 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description 3) Install the IPMDetector DSP option Feature License Key. SMDI Parameters Web/EMS: Enable SMDI Enables Simplified Message Desk Interface (SMDI) interface on [SMDI] the device.  [0] Disable = (Default) Normal serial ...
  • Page 878 Mediant 800B MSBR Parameter Description message: SUBSCRIBE sip:company.com... Instead of: SUBSCRIBE sip:10.33.10.10... Note: If this parameter is not configured, the MWI SUBSCRIBE message is sent to the MWI server as defined by the MWIServerIP parameter. [NotificationIPGroupID] Defines the IP Group ID to which the device sends SIP NOTIFY MWI messages.
  • Page 879 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Forward on Busy Digit Defines the digit pattern used by the PBX to indicate 'call forward Pattern (External) on busy' when the original call is received from an external line EMS: VM Digit Pattern On Busy (not an internal extension).

  • Page 880: Supplementary Services Parameters

    Mediant 800B MSBR 67.10.5 Supplementary Services Parameters This subsection describes the device's supplementary telephony services parameters. 67.10.5.1 Caller ID Parameters The caller ID parameters are described in the table below. Table 67-45: Caller ID Parameters Parameter Description Caller ID Permissions Table...
  • Page 881 Mediant 800B MSBR 67. Configuration Parameters Reference 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 480.
  • Page 882 Mediant 800B MSBR Parameter Description ETSIVMWITypeOneStandard parameter.  If you define Caller ID Type as NTT [2], you need to define the NTT DID signaling form (FSK or DTMF) using the NTTDIDSignallingForm parameter. Web: Enable FXS Caller ID Enables the interworking of Calling Party Category (cpc) code Category Digit For Brazil Telecom from SIP INVITE messages to FXS Caller ID first digit.
  • Page 883 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description [AnalogCallerIDTimingMode] rings.  [1] = The device attempts to find an optimized timing to generate the Caller ID according to the selected Caller ID type. Notes:  This parameter is applicable only to FXS interfaces.
  • Page 884 Mediant 800B MSBR Parameter Description from Q.931 Connect message to SIP 200 OK with the P- Asserted-Identity header. In the opposite direction, if the ISDN device receives a 200 OK with P-Asserted-Identity header, it interworks it to the Connected party number and name in the Q.931 Connect message, including its privacy.

  • Page 885: Call Waiting Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.10.5.2 Call Waiting Parameters The call waiting parameters are described in the table below. Table 67-46: Call Waiting Parameters Parameter Description Web/EMS: Enable Call Waiting Enables the Call Waiting feature. CLI: call-waiting ...
  • Page 886 Mediant 800B MSBR Parameter Description Web: Number of Call Waiting Defines the number of call waiting indications that are played to Indications the called telephone that is connected to the device for Call EMS: Call Waiting Number of Waiting. Indications The valid range is 1 to 100 indications.

  • Page 887: Call Forwarding Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description <sip:4505656002@192.168.13.40:5060>;tag=1455352915 To: <sip:06@192.168.13.2:5060> Call-ID:0010-0008@192.168.13.2 CSeq:342168303 INFO Content-Length:28 Content-Type:application/broadsoft play tone CallWaitingTone1 67.10.5.3 Call Forwarding Parameters The call forwarding parameters are described in the table below. Table 67-47: Call Forwarding Parameters Parameter...

  • Page 888: Message Waiting Indication Parameters

    Mediant 800B MSBR Parameter Description Notes:  These parameters are applicable only to FXS interfaces.  For a description of this feature, see Call Forward Reminder Ring on page 433. Web/EMS: Enable NRT Enables endpoint subscription for Ring reminder event notification Subscription feature.
  • Page 889 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web/EMS: MWI Display Enables sending MWI information to the phone display. CLI: enable-mwi  [0] Disable = (Default) MWI information isn't sent to display. [MWIDisplay]  [1] Enable = The device generates an MWI message (determined by the parameter CallerIDType), which is displayed on the MWI display.

  • Page 890: Call Hold Parameters

    Mediant 800B MSBR Parameter Description  [3] = ETSI VMWI before ring LR_DT_AS  [4] = ETSI VMWI not ring related DT_AS  [5] = ETSI VMWI not ring related RP_AS  [6] = ETSI VMWI not ring related LR_DT_AS Note: For this parameter to take effect, a device reset is required.

  • Page 891: Call Transfer Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description CLI: call-hold-remnd-rng duration specified by this parameter. If the user off-hooks the phone, the [CHRRTimeout] call becomes active. The valid range is 0 to 600. The default is 30. Notes: ...
  • Page 892 Mediant 800B MSBR Parameter Description Web: Transfer Prefix Defines the string that is added as a prefix to the EMS: Logical Prefix For Transferred transferred/forwarded called number when the REFER/3xx Call message is received. CLI: transfer-prefix Notes: [xferPrefix]  The number manipulation rules apply to the user part of the Refer-To and/or Contact URI before it is sent in the INVITE message.
  • Page 893 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description interfaces. EMS: Blind Transfer Disconnect Defines the duration (in milliseconds) for which the device Timeout waits for a disconnection from the Tel side after the Blind CLI: blind-xfer-disc-tmo Transfer Code (KeyBlindTransfer) has been identified. When...

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

    Mediant 800B MSBR Parameter Description Web: IP2IP Transfer Mode Determines the interworking of incoming mid-call SIP REFER CLI: ip2ip-transfer-mode messages to outgoing REFER messages, for calls pertaining [IP2IPTransfermode] to the IP-to-IP application.  [0] Disable = (Default) Upon receipt of a REFER message, the device sends an INVITE to the refer-to destination with or without the Replaces header.
  • Page 895 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 896: Mlpp And Emergency Call Parameters

    Mediant 800B MSBR Parameter Description [ConferenceCode] (Enable3WayConference is set to 1). The valid range is a 25-character string. The default is “!” (Hook- Flash). Note: If the FlashKeysSequenceStyle parameter is set to 1 or 2, the setting of the ConferenceCode parameter is overridden.
  • Page 897 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  CLI: call-prio-mode [0] Disable (default). [CallPriorityMode]  [1] MLPP = MLPP Priority Call handling is enabled. MLPP prioritizes call handling whereby the relative importance of various kinds of communications is strictly defined, allowing higher precedence communication at the expense of lower precedence communications.
  • Page 898 Mediant 800B MSBR Parameter Description (for example, lack of resources or an internal error).  [0] = Disable (default)  [1] = Enable EMS: Enable 911 PSAP Enables the support for the E911 DID protocol, according to the [Enable911PSAP] Bellcore GR-350-CORE standard. This protocol defines signaling between E911 Tandem Switches and the PSAP, using analog loop-start lines.
  • Page 899 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Note: If the ISDN message contains a Precedence IE, the device automatically interworks the "network identity" digits in the IE to the network domain subfield in the Resource-Priority header. For more information, see Multilevel Precedence and Preemption on page 461.
  • Page 900 Mediant 800B MSBR Parameter Description Precedence Level value, the default value is used in the Resource-Priority header of the outgoing SIP INVITE request. In this scenario, the character string is sent without translation to a numerical value. Web: MLPP DiffServ...
  • Page 901 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description "000000". Note: This parameter is applicable only to the MLPP NI-2 ISDN variant with CallPriorityMode set to 1. Web/EMS: Precedence Ringing Defines the index of the Precedence Ringing tone in the Call Type Progress Tones (CPT) file.

  • Page 902: Call Cut-Through Parameters

    Mediant 800B MSBR Parameter Description CLI: dscp-4-mlpp-prio The valid range is -1 to 63. The default is -1. [MLPPPriorityRTPDSCP] Note: If set to -1, the DiffServ value is taken from the global parameter PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call.

  • Page 903: Automatic Dialing Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Note: This feature is applicable only to FXS interfaces. CLI: cut-through-anable Enables PSTN CAS channels/endpoints to receive incoming IP calls even [DigitalCutThrough] if the B-channels are in off-hook state.  [0] Disabled (default) ...

  • Page 904: Direct Inward Dialing Parameters

    Mediant 800B MSBR Parameter Description Automatic dialing FORMAT TargetOfChannel_Index = TargetOfChannel_Destination, CLI: configure voip/gw TargetOfChannel_Type, TargetOfChannel_Module, analoggw automatic- TargetOfChannel_Port, TargetOfChannel_HotLineToneDuration; dialing [\TargetOfChannel] [TargetOfChannel] For example, the below configuration defines automatic dialing of phone number 911 when the phone connected to Port 1 of Module 1 is off-hooked for over 10 seconds: TargetOfChannel 0 = 911, 1, 1, 1 ,10;...
  • Page 905 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description an off-hook state. A polarity change from normal to reversed is generated after a user-defined time (configured by the TimeBetweenDIDWinks parameter). DTMF/MF digits are collected by the device only after this polarity change. Digits that arrive between the first Wink and the polarity change are ignored as they always contain the same number.

  • Page 906: Isdn Bri Parameters

    Mediant 800B MSBR Parameter Description signal. The format of the ini file table parameter is as follows: [EnableDID] FORMAT EnableDID_Index = EnableDID_IsEnable, EnableDID_Port, EnableDID_Module; [\EnableDID] Where,  IsEnable = Enables [1] or disables [0] (default) Japan NTT Modem DID support.

  • Page 907: Pstn Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: Call Forward on Busy Defines the prefix code for deactivating Call Forward on Busy Deactivation Deactivation sent to the softswitch. EMS: Code Call Forward on The valid value is a string. By default, no value is defined.
  • Page 908 Mediant 800B MSBR Parameter Description  [7] E1 MFCR2 = Common E1 MFC/R2 CAS protocols (including line signaling and compelled register signaling).  [8] E1 CAS = Common E1 CAS protocols (including line signaling and MF/DTMF address transfer).  [9] E1 RAW CAS ...
  • Page 909 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description the Trunk ID and 0 is the first trunk). For more information, see the ProtocolType parameter. [ISDNTimerT310] Defines the T310 override timer for DMS, Euro ISDN, and ISDN NI- 2 variants. An ISDN timer is started when a Q.931 Call Proceeding message is received.
  • Page 910 Mediant 800B MSBR Parameter Description  [3] Only ISDN Q.931 Messages Trace  [4] Layer 3 ISDN No Duplication Trace Web/EMS: Framing Method Determines the physical framing method for the trunk. CLI: framing  [0] Extended Super Frame = (Default) Depends on protocol...
  • Page 911 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web/EMS: Line Code Selects B8ZS or AMI for T1 spans, and HDB3 or AMI for E1 spans. CLI: line-code  [0] B8ZS = (Default) B8ZS line code (for T1 trunks only).

  • Page 912: Tdm Bus And Clock Timing Parameters

    Mediant 800B MSBR Parameter Description CLI: iso8859-charset Defines the ISO 8859 character set type (languages) for [ISO8859CharacterSet] representing the alphanumeric string of the calling name (caller ID) in the forwarded message, for IP-to-Tel and Tel-to-IP calls.  [0] No Accented = Proprietary method where incoming INVITE messages with any accented characters (e.g., ‫...
  • Page 913 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description with CAS protocols. Web/EMS: TDM Bus Clock Defines the clock source to which the device synchronizes. Source  [1] Internal = (Default) Generate clock from local source. [TDMBusClockSource]  [4] Network = Recover clock from PSTN line.

  • Page 914: Cas Parameters

    Mediant 800B MSBR Parameter Description  [0] Disable (default)  [1] Enable Notes:  For this parameter to take effect, a device reset is required.  This parameter is applicable only when the TDMBusPSTNAutoClockEnable parameter is set to 1. Web: Auto Clock Trunk Priority...
  • Page 915 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description CASFileName_0 = 'E_M_WinkTable.dat' CASFileName_1 = 'E_M_ImmediateTable.dat' CASTableIndex_0 = 0 CASTableIndex_1 = 0 CASTableIndex_2 = 1 CASTableIndex_3 = 1 Notes:  You can define CAS tables per B-channel using the parameter CASChannelIndex.
  • Page 916 Mediant 800B MSBR Parameter Description variants: ProtocolType_5 = 8 CASFILENAME_2='E1_R2D' CASFILENAME_7= E_M_ImmediateTable_A-Bit.txt' CasChannelIndex_5 = ‘1-10:2,11-20:7,21-31:2’ Notes:  To configure this parameter, the trunk must first be stopped.  Only one of these formats can be implemented; not both.  When this parameter is not configured, a single CAS table for the entire trunk is used, configured by the parameter CASTableIndex.

  • Page 917: Isdn Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description 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.
  • Page 918 Mediant 800B MSBR Parameter Description  [BchannelNegotiation] [1] Exclusive (default)  [2] Any Notes:  For some ISDN variants, when 'Any' (2) is selected, the Setup message excludes the Channel Identification IE.  The Any' (2) option is applicable only if the following conditions are met: ...
  • Page 919 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description follows:  Network provided, Network provided: the first calling number is used  Network provided, User provided: the second one is used  User provided, Network provided: the first one is used ...
  • Page 920 Mediant 800B MSBR Parameter Description ETSI.  [65536] EXPLICIT PRES SCREENING = The calling party number (octet 3a) is always present even when presentation and screening are at their default. Note: This option is applicable only to ETSI, NI-2, and 5ESS.
  • Page 921 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: General Call Control Behavior Bit-field for determining several general CC behavior EMS: General CC Behavior options. To select the options, click the arrow button, and CLI: isdn-bits-cc-behavior then for each required option, select 1 to enable. The default [ISDNGeneralCCBehavior] is 0 (i.e., disable).
  • Page 922 Mediant 800B MSBR Parameter Description specification (default behavior). Note: When using the ini file to configure the device to support several ISDNGeneralCCBehavior features, add the individual feature values. For example, to support both [16] and [32] features, set ISDNGeneralCCBehavior = 48 (i.e., 16 + 32).
  • Page 923 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description support several ISDNOutCallsBehavior features, add the individual feature values. For example, to support both [2] and [16] features, set ISDNOutCallsBehavior = 18 (i.e., 2 + 16). [ISDNOutCallsBehavior_x] Same as the description for parameter ISDNOutCallsBehavior, but for a specific trunk ID.
  • Page 924 Mediant 800B MSBR Parameter Description interface bri <module/port>) point-to-point (P2P) mode. [BriTEIConfigP2P_x] The valid value is 0 to 63, 127. The default is 0.  Network Side:  0-63: Static TEI is accepted.  127: Any possible TEI is accepted. Dynamic TEI allocation is supported.

  • Page 925: Isdn And Cas Interworking Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description number. With NFAS, you can use a single D-channel to control multiple PRI interfaces. Notes:  For this parameter to take effect, a device reset is required.  This parameter is applicable only to T1 ISDN protocols.
  • Page 926 Mediant 800B MSBR Parameter Description device sends its value (i.e. date and time) in the ISDN Connect Date / Time IE. If the 200 OK does not include this header, the device uses its internal, local date and time for the Date / Time IE, which it adds to the sent ISDN Connect message.
  • Page 927 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description SIP INVITE messages. Notes:  When option [2] is configured, you can define the minimum number of overlap digits to collect before sending the first SIP message for routing the call, using the MinOverlapDigitsForRouting parameter.
  • Page 928 Mediant 800B MSBR Parameter Description SIP using a proprietary SIP header.  [2] Using Body = Enable ISDN Tunneling from ISDN PRI to SIP using a dedicated message body. When ISDN Tunneling is enabled, the device sends all ISDN PRI messages using the correlated SIP messages.
  • Page 929 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Note: This parameter is applicable only if the QSIG Tunneling 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.
  • Page 930 Mediant 800B MSBR Parameter Description (in the sent ISDN Setup message). This feature is only applicable for IP-to-ISDN calls. The valid value range is 0 to 36. The default is 0. This feature operates as follows: If an isub parameter is received in the Request-URI, for example, INVITE sip:9565645;isub=1234@host.domain:user=phone...
  • Page 931 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  MFC-R2: ANI II digits. The device supports the Brazilian and Argentinian variants. This regional support is configured using the CallingPartyCategoryMode. The CPC is denoted in the SIP INVITE message using the 'cpc=' parameter in the From or P-Asserted-Identity headers.
  • Page 932 Mediant 800B MSBR Parameter Description  This parameter is applicable only to the E1 MFC-R2 variant. CLI: usr2usr-hdr-frmt Defines the interworking between the SIP INVITE's User-to-User [UserToUserHeaderFormat] header and the ISDN User-to-User (UU) IE data.  [0] = (Default) SIP header format: X-UserToUser.
  • Page 933 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Note: The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Web/EMS: Progress Indicator Determines the Progress Indicator (PI) to ISDN per trunk. to ISDN ...
  • Page 934 Mediant 800B MSBR Parameter Description Note: The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Web: B-Channel Negotiation Determines the ISDN B-channel negotiation mode, per trunk. EMS: B-Channel Negotiation  [-1] Not Configured = (Default) Use per device configuration of For Trunk Mode the BChannelNegotiation parameter.
  • Page 935 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description If enabled, the CIC code (received in an INVITE Request-URI) is included in a TNS IE in the ISDN Setup message. For example: INVITE sip:555666;cic=2345@100.2.3.4 sip/2.0. Notes:  This feature is supported only for SIP-to-ISDN calls.
  • Page 936 Mediant 800B MSBR Parameter Description Note: The interworking of ISDN User-to-User IE to SIP INFO is applicable only to the Euro ISDN, QSIG, and 4ESS PRI variants. Web: Enable User-to-User IE Enables interworking of SIP user-to-user information (UUI) to User- for IP to Tel to-User IE in ISDN Q.931 messages.
  • Page 937 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description E1 QSIG [21], Single Step Transfer [4], Path T1 QSIG [23] Replacement Transfer [2], or InBand [5] T1 NI2 ISDN [10], TBCT [2] or InBand [5] T1 4ESS ISDN [11], T1 5ESS 9 ISDN [12]...
  • Page 938 Mediant 800B MSBR Parameter Description is received from the PBX, a SIP REFER message is sent to the IP side.  [5] = IP-to-Tel Blind Transfer mode supported for ISDN (PRI/BRI) protocols and implemented according to AT&T Toll Free Transfer Connect Service (TR 50075) “Courtesy Transfer- Human-No Data”.
  • Page 939 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  CLI: isdn-xfer-cab [0] Audio 3.1 (default) [ISDNTransferCapability_x]  [1] Speech  [2] Data Notes:  If this parameter is not configured or is set to -1, Audio 3.1 capability is used.
  • Page 940 Mediant 800B MSBR Parameter Description Update with CallTranferComplete or CallTransferUpdate invoke application CLI: qsig-xfer-update protocol data units (APDU) to SIP UPDATE messages with P- [EnableQSIGTransferUpdate] Asserted-Identity and optional Privacy headers. This feature is supported for IP-to-Tel and Tel-to-IP calls. ...

  • Page 941: Answer And Disconnect Supervision Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description CLI: configure voip > gw CauseMapISDN2SIP_IsdnReleaseCause, manipulations CauseMapISDN2SIP_SipResponse; CauseMapIsdn2Sip [\CauseMapISDN2SIP] [CauseMapISDN2SIP] Release Cause Mapping from SIP to ISDN Table Web: Release Cause Mapping This table parameter maps SIP responses to Q.850 Release Table Causes.
  • Page 942 Mediant 800B MSBR Parameter Description CLI: mx-call-duration duration is reached, the device terminates the call. This [MaxCallDuration] feature is useful for ensuring available resources for new calls, by ensuring calls are properly terminated. The valid range is 0 to 35,791. The default is 0 (i.e., no limitation).
  • Page 943 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Web: Broken Connection Timeout Defines the time period (in 100-msec units) after which a EMS: Broken Connection Event call is disconnected if an RTP packet is not received.
  • Page 944 Mediant 800B MSBR Parameter Description  [1] Enable Web: Trunk Alarm Call Disconnect Defines the duration (in seconds) to wait after an E1/T1 Timeout trunk "Red" alarm (LOS / LOF) is raised, before the device CLI: trk-alrm-call-disc-to disconnects the SIP call. If this timeout expires and the...
  • Page 945 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Notes:  For this parameter to take effect, a device reset is required.  To take advantage of this new feature, configure all FXO lines as a single Trunk Group with ascending or...

  • Page 946: Tone Parameters

    Mediant 800B MSBR Parameter Description  For this parameter to take effect, a device reset is required. EMS: Current Disconnect Duration Defines the duration (in msec) of the current disconnect CLI: current-disconnect-duration pulse. [CurrentDisconnectDuration] The range is 200 to 1500. The default is 900.
  • Page 947 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: SIP Hold Behavior Enables the device to handle incoming re-INVITE messages with the CLI: sip-hold-behavior "a=sendonly" attribute in the SDP, in the same way as if an [SIPHoldBehavior] "a=inactive" is received in the SDP. When enabled, the device plays a held tone to the Tel phone and responds with a SIP 200 OK containing the "a=recvonly"...
  • Page 948 Mediant 800B MSBR Parameter Description [HotLineToneDuration] Notes:  This parameter is applicable to FXS and FXO interfaces.  You can define the Hotline duration per FXS/FXO port using the Automatic Dialing table. Web/EMS: Reorder Tone For analog interfaces: Defines the duration (in seconds) that the Duration [sec] device plays a busy or reorder tone before releasing the line.
  • Page 949 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 configuring multiple codes, separate the codes by commas (without spaces).
  • Page 950 Mediant 800B MSBR Parameter Description response (with or without SDP). Note that the receipt of a 183 response does not cause the device configured for CAS to play a ringback tone (unless the SIP183Behaviour parameter is set to 1). The device configured for ISDN operates according to...
  • Page 951 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description responses, it does not resume playing the local ringback tone. Note that for ISDN trunks, this option is applicable only if the LocalISDNRBSource parameter is set to 1. Note: This parameter is applicable to the Gateway and IP-to-IP applications.
  • Page 952 Mediant 800B MSBR Parameter Description to the originating terminal. Note that the receipt of a 183 response results in an ISDN Progress message (unless SIP183Behaviour is set to 1). If SIP183Behaviour is set to 1 (183 is handled the same way as a 180 with SDP), the device sends an Alert message with PI = 8 without playing a ringback tone.

  • Page 953: Tone Detection Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Tone Index Table Web: Tone Index Table This table parameter configures the Tone Index table, which allows EMS: Analog Gateway you to define distinctive ringing and call waiting tones per FXS Provisioning >...

  • Page 954: Metering Tone Parameters

    Mediant 800B MSBR Parameter Description  ISDNDisconnectOnBusyTone = 1 (applicable for Busy, Reorder and SIT tones) Another parameter for handling the SIT tone is SITQ850Cause, which determines the Q.850 cause value specified in the SIP Reason header that is included in a 4xx response when a SIT tone is detected on an IP-to-Tel call.
  • Page 955 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description file included in SIP INFO messages, which is always sent before 200 0K. The device ignores tariffs sent after the call is established.  [3] SIP RAW Data Provided = (Proprietary method of Cirpack) Advice-of-Charge service toward the PSTN.

  • Page 956: Telephone Keypad Sequence Parameters

    Mediant 800B MSBR Parameter Description [\ChargeCode] Where,  EndTime = Period (1 - 4) end time.  PulseInterval = Period (1 - 4) pulse interval.  PulsesOnAnswer = Period (1 - 4) pulses on answer. For example: ChargeCode 1 = 7,30,1,14,20,2,20,15,1,0,60,1;...
  • Page 957 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [0] = Disable (default)  [1] = Enable For example, if this parameter is enabled and the prefix string for the external line is defined as "9" (using the parameter Prefix2ExtLine) and the FXS user wants to make a call to destination "123", the device collects and sends all the dialed...
  • Page 958 Mediant 800B MSBR Parameter Description CLI: flash-key-seq-tmout button (Flash Hook + Digit mode - when the parameter [FlashKeysSequenceTimeout] FlashKeysSequenceStyle is set to 1 or 2). The valid range is 100 to 5,000. The default is 2,000. Keypad Feature - Call Forward Parameters...

  • Page 959: Fxo And Fxs Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description dial tone is heard. Dial the telephone number to which the phone automatically dials after a configurable delay (terminate the number with #); a confirmation tone is heard. Web: Hot-line Deactivate...
  • Page 960 Mediant 800B MSBR Parameter Description EMS: Country Coefficients USA or Europe (TBR21) standards. CLI: fxs-country-coefficients  [66] Europe = TBR21 [FXSCountryCoefficients]  [70] USA = (Default) United States Note: For this parameter to take effect, a device reset is required.
  • Page 961 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [IsWaitForDialTone] [0] No  [1] Yes (default) When one-stage dialing and this parameter are enabled, the device dials the phone number (to the PSTN/PBX line) only after it detects a dial tone.
  • Page 962 Mediant 800B MSBR Parameter Description Caller ID Caller ID. EMS: Rings Before Caller ID  [0] 0 = Before first ring. CLI: rings-b4-det-callerid  [1] 1 = (Default) After first ring. [RingsBeforeCallerID]  [2] 2 = After second ring. Web/EMS: Guard Time...

  • Page 963: Trunk Groups And Routing Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description [PulseDialGenerationInterDigi Defines the inter-digit duration (time between consecutively dialed tTime] digits) for FXO pulse dial generation. The valid value range is 300 to 1500 (in msec). The default is 700. Note: For this parameter to take effect, a device reset is required.
  • Page 964 Mediant 800B MSBR Parameter Description  All channels and trunks configured without a Trunk Group for all Trunk Groups channels that are configured without a Trunk Group ID,.  [0] By Dest Phone Number  [1] Cyclic Ascending (default) ...
  • Page 965 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description the received Tel Display Name is not empty).  [3] Original = Similar to option [2], except that the operation is done before regular calling number manipulation. Web/EMS: Use Display Name as...

  • Page 966: [Prefix_Srcipgroupid]

    Mediant 800B MSBR Parameter Description routing [PREFIX] [Prefix] FORMAT PREFIX_Index = PREFIX_RouteName, PREFIX_DestinationPrefix, PREFIX_DestAddress, PREFIX_SourcePrefix, PREFIX_ProfileId, PREFIX_MeteringCode, PREFIX_DestPort, PREFIX_SrcIPGroupID, PREFIX_DestHostPrefix, PREFIX_DestIPGroupID, PREFIX_SrcHostPrefix, PREFIX_TransportType, PREFIX_SrcTrunkGroupID, PREFIX_DestSRD, PREFIX_CostGroup, PREFIX_ForkingGroup, PREFIX_CallSetupRulesSetId; [\PREFIX] For a detailed description of this table, see ''Configuring Outbound IP Routing Table'' on page 397.
  • Page 967 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description otherwise, the call is rejected. Therefore, the difference between this option and option [1] is that this option is concerned only about numerical IP addresses that are defined in the tables.
  • Page 968 Mediant 800B MSBR Parameter Description Trunk Group based on this parameter's value.  [0] No (default)  [1] Yes For digital interfaces: The SIP 'cic' parameter enables the transmission of the 'cic' parameter from the SIP network to the ISDN. The 'cic' parameter is a three- or four-digit code...
  • Page 969 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description message is sent to the PSTN. If the EnableComfortTone parameter is set to 1, a comfort tone is played to the PSTN. When the timeout expires, the device sends an INVITE to a specific IP Group or to a fax server according to the Outbound IP Routing table rules.

  • Page 970: Ip Connectivity Parameters

    Mediant 800B MSBR Parameter Description other words, for an INVITE message, the device can receive up to 20 forking responses from the Proxy server. The valid range is 0 to 30. The default is 30. Web: Tel2IP Call Forking Mode...

  • Page 971: Alternative Routing Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Connectivity Method querying the connectivity status of a destination IP address. EMS: Alternative Routing  [0] ICMP Ping = (Default) Internet Control Message Protocol Telephone to IP Connection (ICMP) ping messages.
  • Page 972 Mediant 800B MSBR Parameter Description drops the call. Web/EMS: Redundant Routing Determines the type of redundant routing mechanism when a call Mode can’t be completed using the main route. CLI: redundant-routing-m  [0] Disable = No redundant routing is used. If the call can’t be...
  • Page 973 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description FORMAT AltRouteCauseTel2IP_Index = AltRouteCauseTel2IP_ReleaseCause; [\AltRouteCauseTel2IP] For example: AltRouteCauseTel2IP 0 = 486; (Busy Here) AltRouteCauseTel2IP 1 = 480; (Temporarily Unavailable) AltRouteCauseTel2IP 2 = 408; (No Response) For a detailed description of this table, see ''Alternative Routing Based on SIP Responses'' on page 413.

  • Page 974: Number Manipulation Parameters

    Mediant 800B MSBR 67.10.15 Number Manipulation Parameters The number manipulation parameters are described in the table below. Table 67-72: Number Manipulation Parameters Parameter Description [ManipulateIP2PSTNReferTo] Enables the manipulation of the called party (destination) number according to the SIP Refer-To header received by the device for TDM (PSTN) blind transfer.
  • Page 975 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description manipulation on the source number (i.e., just before sending to the Tel side). Web: Tel2IP Default Redirect Determines the default redirect reason for Tel-to-IP calls when no Reason redirect reason (or “unknown”) exists in the received Q931 ISDN CLI: tel-to-ip-dflt-redir-rsn Setup message.
  • Page 976 Mediant 800B MSBR Parameter Description  [1] Busy  [2] No Reply  [3] Network Busy  [4] Deflection  [9] DTE out of Order  [10] Forwarding DTE  [13] Transfer  [14] PickUp  [15] Systematic/Unconditional Note: This parameter is applicable only to digital PSTN interfaces (ISDN).
  • Page 977 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Notes:  For digital interfaces: If the incoming ISDN-to-IP call includes a Redirect Number, this number is overridden by the new called number if this parameter is set to [1] or [2].
  • Page 978 Mediant 800B MSBR Parameter Description  Phone Number [0] No (default) EMS: Replace Empty Dst With  [1] Yes Port Number Note: This parameter is applicable only to Tel-to-IP calls and if the CLI: empty-dst-w-bch-nb called number is missing. [ReplaceEmptyDstWithPortNu...
  • Page 979 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [0] No = (Default) Don't change numbers. Web/EMS: Swap Redirect and 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 [SwapRedirectNumber] redirect number instead of the called number.
  • Page 980 Mediant 800B MSBR Parameter Description CallingNameMapIp2Tel_ManipulationName, CallingNameMapIp2Tel_DestinationPrefix, CallingNameMapIp2Tel_SourcePrefix, CallingNameMapIp2Tel_CallingNamePrefix, CallingNameMapIp2Tel_SourceAddress, CallingNameMapIp2Tel_RemoveFromLeft, CallingNameMapIp2Tel_RemoveFromRight, CallingNameMapIp2Tel_LeaveFromRight, CallingNameMapIp2Tel_Prefix2Add, CallingNameMapIp2Tel_Suffix2Add; [ \CallingNameMapIp2Tel ] For a detailed description of this table, see ''Configuring SIP Calling Name Manipulation'' on page 380. Calling Name Manipulations Tel-to-IP Table CLI: configure voip > gw...
  • Page 981 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Manipulation destination number, and this additional rule is also configured in the CLI: prfm-ip-to-tel-dst-map manipulation table (NumberMapIP2Tel parameter). This enables you to configure only a few manipulation rules for complex number...
  • Page 982 Mediant 800B MSBR Parameter Description rules).  [0] = Disable (default)  [1] = Enable Source Phone Number Manipulation for Tel-to-IP Calls Table Web: Source Phone Number This table parameter manipulates the source phone number for Tel- Manipulation Table for Tel >...

  • Page 983: Sbc Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Tel to IP FORMAT RedirectNumberMapTel2Ip_Index = CLI: configure voip > gw RedirectNumberMapTel2Ip_ManipulationName, manipulations redirect- RedirectNumberMapTel2Ip_DestinationPrefix, number-map-tel2ip RedirectNumberMapTel2Ip_RedirectPrefix, [RedirectNumberMapTel2IP] RedirectNumberMapTel2Ip_RemoveFromLeft, RedirectNumberMapTel2Ip_RemoveFromRight, RedirectNumberMapTel2Ip_LeaveFromRight, RedirectNumberMapTel2Ip_Prefix2Add, RedirectNumberMapTel2Ip_Suffix2Add, RedirectNumberMapTel2Ip_IsPresentationRestricted, RedirectNumberMapTel2Ip_SrcTrunkGroupID, RedirectNumberMapTel2Ip_SrcIPGroupID; [\RedirectNumberMapTel2Ip] For a description of this table, see ''Configuring Redirect Number Manipulation'' on page 383.
  • Page 984 Mediant 800B MSBR Parameter Description  CLI: crp-survivability-mode [0] Standard Mode (default) [CRPSurvivabilityMode]  [1] Always Emergency Mode  [2] Auto-answer REGISTER CLI: crp-gw-fallback Enables fallback routing from the proxy server to the Gateway [CRPGatewayFallback] (PSTN).  [0] = Disable (default) ...
  • Page 985 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description chosen. In case of any other SRD, then the first IP Group associated with this SRD is chosen as the source IP Group or the call. If no IP Group is associated with this SRD, the call is rejected.
  • Page 986 Mediant 800B MSBR Parameter Description  If the received header’s original value is less than this parameter's value, the header’s value is decremented before being sent on.  If the received header’s original value is greater than the parameter's value, the header’s value is replaced by the user- defined parameter’s value.
  • Page 987 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description [SBCUserRegistrationGraceTi The valid value is 0 to 300 (i.e., 5 minutes). The default is 0. Web/EMS: Handle P-Asserted- Global parameter that defines the handling of the SIP P-Asserted- Identity Identity header. You can also configure this functionality per CLI: p-assert-id specific calls, using IP Profiles (IpProfile_SBCAssertIdentity).
  • Page 988 Mediant 800B MSBR Parameter Description settings of this global parameter is ignored for calls associated with the IP Profile. [SBCEnforceMediaOrder] Enables the device to include all previously negotiated media lines within the current session ('m=' line) in the SDP offer-answer exchange (RFC 3264).
  • Page 989 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Proxy-Authenticate header as the authentication challenge response. Web: Authentication Quality of Defines the authentication and integrity level of quality of Protection protection (QoP) for digest authentication offered to the client. CLI: auth-qop When the device challenges a SIP request (e.g., INVITE), it...
  • Page 990 Mediant 800B MSBR Parameter Description the server sends a SIP 200 OK response. If the expiry time was unchanged by the server, the device applies this feature and changes the expiry time in the SIP 200 OK response before forwarding it to the user; otherwise, the device does not change the expiry time.
  • Page 991 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description 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> Web: SBC Dialog-Info 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.
  • Page 992 Mediant 800B MSBR Parameter Description Public-GRUU: sip:userA@domain.com;gr=unique-id Web: Bye Authentication Enables authenticating a SIP BYE request before disconnecting CLI: sbc-bye-auth the call. This feature prevents, for example, a scenario in which [SBCEnableByeAuthentication] the SBC SIP client receives a BYE request from a third-party...
  • Page 993 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description settings of this global parameter is ignored for calls associated with the IP Profile. Web: SBC Preferences Mode Determines the order of the Extension coders (coders added if [SBCPreferencesMode] there are no common coders between SDP offered coders and Allowed coders) and Allowed coders (configured in the Allowed Coders Group table) in the outgoing SIP message (in the SDP).
  • Page 994 Mediant 800B MSBR Parameter Description discarded. Web: Gateway Direct Route Defines the prefix destination Request-URI user part that is Prefix appended to the original user part for alternative IP-to-IP call CLI: configure voip/sbc general- routing from SBC to Gateway (Tel) interfaces.
  • Page 995 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description [AllowedCodersGroupX] FORMAT AllowedCodersGroup_Index = AllowedCodersGroup_Name; [\AllowedCodersGroup] Where X represents the index number. For a detailed description of this table, see ''Configuring Allowed Audio Coder Groups'' on page 543. Allowed Video Coders Table...
  • Page 996 Mediant 800B MSBR Parameter Description [IP2IPRouting] [ IP2IPRouting ] FORMAT IP2IPRouting_Index = IP2IPRouting_RouteName, IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_RequestType, IP2IPRouting_MessageCondition, IP2IPRouting_ReRouteIPGroupID, IP2IPRouting_Trigger, IP2IPRouting_CallSetupRulesSetId, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions, IP2IPRouting_GroupPolicy, IP2IPRouting_CostGroup; [ \IP2IPRouting ] For a detailed description of this table, see ''Configuring SBC IP- to-IP Routing Rules'' on page 552.

  • Page 997: Standalone Survivability Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: IP to IP Outbound This table parameter configures the IP to IP Outbound Manipulation Manipulation table. This table allows you to manipulate the SIP EMS: IP to IP Outbound URI user part (source and/or destination) of the outbound SIP Manipulation dialog message.
  • Page 998 Mediant 800B MSBR Parameter Description EMS: Default Gateway IP When an incoming SIP INVITE is received and the destination CLI: sas-default-gw-ip Address-Of-Record is not included in the SAS database, the [SASDefaultGatewayIP] request is immediately sent to this default gateway. The address can be configured as an IP address (dotted- decimal notation) or as a domain name (up to 49 characters).
  • Page 999 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description example: Record-Route: <sip:server10.biloxi.com;lr> Web: SAS Proxy Set Defines the Proxy Set (index number) used in SAS Normal EMS: Proxy Set mode to forward REGISTER and INVITE requests from users CLI: sas-proxy-set that are served by the SAS application.
  • Page 1000 Mediant 800B MSBR Parameter Description logic (same as option [0]), but when in Normal mode incoming REGISTER requests are ignored.  [3] Auto-answer REGISTER = When in Normal mode, the device responds to received REGISTER requests by sending a SIP 200 OK (instead of relaying the registration requests to a Proxy), and enters the registrations in its SAS database.
  • Page 1001 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Web: SAS Entering Emergency Determines for which sent SIP message types the device enters Mode SAS Emergency mode if no response is received for them from CLI: sas-enter-emg-mode the proxy server.

  • Page 1002: Ip Media Parameters

    Mediant 800B MSBR Parameter Description [\IP2IPRouting] For example: IP2IPRouting 1 = -1, *, *, *, *, 0, -1, -1, , 0, -1, 0; 67.13 IP Media Parameters The IP media parameters are described in the table below. Table 67-75: IP Media Parameters...
  • Page 1003 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description [BipOnConference] heard).  [0] Disable  [1] Enable (default) Web: Enable Conference DTMF Determines the device logic once a DTMF is received on Clamping any conference participant. If enabled, the DTMF is not CLI: conf-dtmf-clamping regenerated toward the other conference participants.
  • Page 1004 Mediant 800B MSBR Parameter Description  [13] 13 = 5.00 dB/sec  [14] 14 = 5.50 dB/sec  [15] 15 = 6.00 dB/sec  [16] 16 = 7.00 dB/sec  [17] 17 = 8.00 dB/sec  [18] 18 = 9.00 dB/sec ...

  • Page 1005: Services

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description  [1] Enable Energy Detector Quality Factor Defines the Energy Detector's sensitivity level. CLI: energy-detector-sensitivity The valid range is 0 to 10, where 0 is the lowest sensitivity [EnergyDetectorQualityFactor] and 10 the highest sensitivity. The default is 4.
  • Page 1006 Mediant 800B MSBR Parameter Description setting/siprec-server-dest- user part is defined. username [SIPRecServerDestUsername] SIP Recording Routing Table Web: SIP Recording Routing Defines SIP Recording Routing rules (calls to record). table The format of the ini file table parameter is as follows:...

  • Page 1007: Radius And Ldap Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference 67.14.2 RADIUS and LDAP Parameters 67.14.2.1 General Parameters The general RADIUS and LDAP parameters are described in the table below. Table 67-77: General RADIUS and LDAP Parameters Parameter Description Web: Use Local Users Database Defines when the device uses its local user database (Web Users CLI: configure system >...
  • Page 1008 Mediant 800B MSBR Parameter Description CLI: accounting-server-ip [RADIUSAccServerIP] Web: Accounting Port Defines the port of the RADIUS accounting server. CLI: accounting-port The default is 1646. [RADIUSAccPort] Web/EMS: RADIUS Determines when the RADIUS accounting messages are sent to the Accounting Type RADIUS accounting server.

  • Page 1009: Ldap Parameters

    Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description RADIUS Authentication Parameters Web: Password Local Cache Defines the device's mode of operation regarding the timer Mode (configured by the parameter RadiusLocalCacheTimeout) that CLI: local-cache-mode determines the validity of the username and password (verified by [RadiusLocalCacheMode] the RADIUS server).
  • Page 1010 Mediant 800B MSBR Parameter Description required. CLI: search-dns-in-parallel Defines the method of how the device queries the DN [LDAPSearchDNsinParallel] object within each LDAP server.  [0] Sequential = (Default) The query is done in each DN object, one by one, until a result is returned.
  • Page 1011 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description CLI: ldap-private-nm-attr Defines the name of the attribute that represents the user's [MSLDAPPrivateNumAttributeName] private number in the AD. If this value equals the value of the MSLDAPPrimaryKey or MSLDAPSecondaryKey parameter, then the device queries the AD for the destination number in this private attribute name;...

  • Page 1012: Least Cost Routing Parameters

    Mediant 800B MSBR Parameter Description [ \LdapConfiguration ] For a detailed description of this table, see ''Configuring LDAP Servers'' on page 212. LDAP Server Search DN Table Web: LDAP Search DN Table Defines the full base path (i.e., distinguished name / DN) CLI: configure voip >...
  • Page 1013 Mediant 800B MSBR 67. Configuration Parameters Reference Parameter Description Provisioning > Cost Group and a call rate (charge per minute). CLI: configure voip > [ CostGroupTable ] services least-cost-routing FORMAT CostGroupTable_Index = cost-group CostGroupTable_CostGroupName, [CostGroupTable] CostGroupTable_DefaultConnectionCost, CostGroupTable_DefaultMinuteCost; [ \CostGroupTable ] For example: CostGroupTable 2 = "Local Calls", 2, 1;...

Table of Contents