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

AudioCodes Media 800 MSBR User Manual

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

Advertisement

Quick Links

Download this manual
Mediant™ 800 MSBR
Multi-Service Business Router
Session Border Controller
User's Manual
Version 6.6
April 2013
Document # LTRT-12809

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Media 800 MSBR

Summary of Contents for AudioCodes Media 800 MSBR

  • Page 1 Mediant™ 800 MSBR Multi-Service Business Router Session Border Controller User's Manual Version 6.6 April 2013 Document # LTRT-12809...

  • Page 3: Table Of Contents

    User's Manual Contents Table of Contents Overview ......................21 Getting Started with Initial Connectivity ..............23 Assigning the VoIP LAN OAMP Address ............25 Web Interface ......................25 CLI .......................... 27 Assigning Data-Router LAN and WAN IP Addresses ........29 Configuring Data-Routing LAN Interface ..............29 3.1.1 CLI ...........................
  • Page 4 Mediant 800 MSBR 5.3.2 Advanced User Accounts Configuration ..............67 Displaying Login Information upon Login ............... 70 Configuring Web Security Settings ................ 71 Limiting OAMP Access to a Specific WAN Interface ..........72 Web Login Authentication using Smart Cards ............72 Configuring Web and Telnet Access List ...............
  • Page 5 User's Manual Contents 13 Configuring Power over Ethernet ..............109 General VoIP Configuration ..................111 14 Network ......................113 14.1 Configuring IP Network Interfaces ............... 113 14.1.1 Assigning NTP Services to Application Types ............117 14.1.2 Multiple Interface Table Configuration Rules............117 14.1.3 Troubleshooting the Multiple Interface Table ............118 14.1.4 Networking Configuration Examples ..............118 14.1.4.1 One VoIP Interface for All Applications ..........
  • Page 6 Mediant 800 MSBR 16.2.2.3 Fax Fallback ..................157 16.2.2.4 Fax/Modem Bypass Mode ..............158 16.2.2.5 Fax / Modem NSE Mode ............... 159 16.2.2.6 Fax / Modem Transparent with Events Mode ........160 16.2.2.7 Fax / Modem Transparent Mode ............160 16.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......
  • Page 7 User's Manual Contents 20 SIP Definitions ....................225 20.1 Configuring SIP Parameters ................225 20.2 Configuring Account Table ................... 225 20.3 Configuring Proxy and Registration Parameters ..........228 20.3.1 SIP Message Authentication Example ..............230 20.4 Configuring SIP Message Manipulation ............... 232 20.5 Configuring SIP Message Policy Rules ..............
  • Page 8 Mediant 800 MSBR 23.6.4 Performing Manual D-Channel Switchover in NFAS Group ........292 23.7 ISDN Overlap Dialing ................... 292 23.7.1 Collecting ISDN Digits and Sending Complete Number in SIP ......292 23.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 ....293 23.8 Redirect Number and Calling Name (Display) .............
  • Page 9 28.11.4.1 About E9-1-1 Services ................376 28.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........377 28.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 28.11.4.4 Configuring AudioCodes ELIN Gateway ..........386 28.12 Multilevel Precedence and Preemption ..............388 28.12.1 MLPP Preemption Events in SIP Reason Header ..........390...
  • Page 10 Mediant 800 MSBR 29.14.1.3 DID Wink ....................413 29.14.2 FXO Operations for Tel-to-IP Calls ................414 29.14.2.1 Automatic Dialing .................. 414 29.14.2.2 Collecting Digits Mode................415 29.14.2.3 FXO Supplementary Services ............... 415 29.14.3 Call Termination on FXO Devices .................416 29.14.3.1 Calls Termination by PBX ..............416 29.14.3.2 Call Termination before Call Establishment ..........
  • Page 11 User's Manual Contents 30.8.10 Interworking Delayed Offer ..................448 30.8.11 Interworking Call Hold ....................449 30.9 Call Survivability ....................449 30.9.1 Auto-Provisioning of Subscriber-Specific Information for BroadWorks Server for Survivability.........................449 30.9.2 BroadSoft's Shared Phone Line Call Appearance for SBC Survivability....450 30.9.3 Call Survivability for Call Centers ................451 30.9.4 Survivability Mode Display on Aastra IP Phones ..........453 30.10 Call Forking ......................
  • Page 12 Mediant 800 MSBR 35 SAS Configuration ..................503 35.1 General SAS Configuration .................. 503 35.1.1 Enabling the SAS Application ................503 35.1.2 Configuring Common SAS Parameters ..............503 35.2 Configuring SAS Outbound Mode ................ 506 35.3 Configuring SAS Redundant Mode ..............506 35.4 Configuring Gateway Application with SAS ............
  • Page 13 User's Manual Contents 42.2 Configuring Matching Rules ................. 551 42.3 Configuring Traffic Shaping .................. 554 42.4 Configuring DSCP Settings .................. 557 42.5 Configuring 802.1p Settings ................. 559 43 VPN ........................561 43.1 Configuring IPSec ....................561 43.2 Configuring L2TP Server ..................563 43.3 Creating VPN Users .....................
  • Page 14 51.3.1 DHCP-based Configuration Server ...............659 51.3.2 HTTP-based Automatic Updates ................659 51.3.3 Configuration using FTP or NFS ................660 51.3.4 Configuration using AudioCodes EMS ..............660 51.4 Loading Files Securely by Disabling TFTP ............660 51.5 Remotely Triggering Auto Update using SIP NOTIFY ......... 661 51.6 Configuring Zero Configuration ................
  • Page 15 User's Manual Contents 55 Carrier-Grade Alarms ..................673 55.1 Viewing Active Alarms ..................673 55.2 Viewing Alarm History ..................673 56 Performance Monitoring ................. 675 56.1 Viewing MOS per Media Realm ................675 56.2 Viewing Trunk Utilization ..................676 56.3 Viewing Quality of Experience ................677 56.4 Viewing Average Call Duration ................
  • Page 16 Mediant 800 MSBR 60.1.3 Identifying AudioCodes Syslog Messages using Facility Levels ......722 60.1.4 SNMP Alarms in Syslog Messages ...............723 60.2 Configuring Syslog Settings ................. 723 60.3 Configuring Debug Recording ................724 60.4 Filtering Syslog Messages and Debug Recordings ..........725 60.4.1 Filtering IP Network Traces ...................727...
  • Page 17 User's Manual Contents 66.4.1 General Parameters ....................779 66.4.2 HTTPS Parameters ....................780 66.4.3 SRTP Parameters ....................781 66.4.4 TLS Parameters .....................784 66.4.5 SSH Parameters ....................786 66.4.6 OCSP Parameters ....................787 66.4.7 IDS Parameters .....................788 66.5 RADIUS Parameters .................... 789 66.6 SIP Media Realm Parameters ................792 66.7 Control Network Parameters ................
  • Page 18 Mediant 800 MSBR 66.14 SBC and CRP Parameters ................... 968 66.15 Standalone Survivability Parameters ..............980 66.16 IP Media Parameters ................... 984 66.17 Auxiliary and Configuration File Name Parameters ..........988 66.18 Automatic Update Parameters ................989 67 DSP Templates ....................993 68 Technical Specifications ................

  • Page 19: Weee Eu Directive

    This document is subject to change without notice. Date Published: April-28-2013 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

    The scope of this document does not fully cover security aspects for deploying the device in your environment. Security measures should be done in accordance with your organization’s security policies. For basic security guidelines, you should refer to AudioCodes Recommended Security Guidelines document. Note: Before configuring the device, ensure that it is installed correctly as instructed in the Hardware Installation Manual.

  • Page 21: Overview

    User's Manual 1. Overview Overview The Mediant 800 Multi-Service Business Router (MSBR) is a networking device that combines multiple service functions such as a Media Gateway, Session Border Controller (SBC), Data Router and Firewall, LAN switch, WAN access, Stand Alone Survivability (SAS) and an integrated general-purpose server.
  • Page 22 Mediant 800 MSBR The device is optimized for wire-speed delivery of data, providing up to 12 Ethernet LAN ports for connecting equipment such as computers and IP phones. These ports are divided into Gigabit Ethernet and Fast Ethernet interfaces (the number depends on the ordered configuration), and provide power-over-Ethernet (PoE) capabilities.

  • Page 23: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 25: Assigning The Voip Lan Oamp Address

    User's Manual 2. Assigning the VoIP LAN OAMP Address Assigning the VoIP LAN OAMP Address The device is shipped with a factory default IP address for its operations, administration, maintenance, and provisioning (OAMP) VoIP LAN interface, as shown in the table below: Default VoIP OAMP IP Address IP Address Value...
  • Page 26 Mediant 800 MSBR Figure 2-1: Connecting to LAN Port Ensure that your computer is configured to automatically obtain an IP address. The device has an embedded DHCP server, which by default allocates an IP address to a connected computer. Access the Web interface: On your computer, start a Web browser and in the URL address field, enter the default IP address of the device;...

  • Page 27: Cli

    User's Manual 2. Assigning the VoIP LAN OAMP Address The procedure below describes how to assign a VoIP LAN IP address, using CLI.  To assign a LAN IP address using CLI: Connect the RS-232 port of the device to the serial communication port on your computer.
  • Page 28 Mediant 800 MSBR At the prompt, type the following command to set the prefix length, and then press Enter: (network-if-0)# set prefix-length <prefix length, e.g., 16> At the prompt, type the following command to set the Default Gateway, and then press Enter: (network-if-0)# set gateway <IP address>...

  • Page 29: Assigning Data-Router Lan And Wan Ip Addresses

    User's Manual 3. Assigning Data-Router LAN and WAN IP Addresses Assigning Data-Router LAN and WAN IP Addresses Once you have changed the VoIP LAN IP address to suit your networking scheme, you need to configure the data-router LAN IP address and/or WAN IP address. You can setup your device for Web management access using one of the following interfaces: ...

  • Page 30: Cli

    Mediant 800 MSBR 3.1.1 The procedure below describes how to configure the data-router LAN IP address using CLI.  To assign a data-router LAN IP address using CLI: Establish serial communication with the device. At the prompt, type the following command to access the data-router interface, and then press Enter: # configure data At the prompt, type the following command to access the VLAN 1 LAN switch...

  • Page 31: Configuring Device's Dhcp Server

    User's Manual 3. Assigning Data-Router LAN and WAN IP Addresses Figure 3-2: Defining LAN Data Routing IP Address Click OK to save your settings. Configuring Device's DHCP Server The device is supplied with an enabled embedded DHCP server for the LAN, and with default IP pool addresses relating to the default subnet LAN.

  • Page 32: Assigning A Wan Ip Address

    Mediant 800 MSBR If required, refresh the address by disconnecting the cable and then reconnecting it again, or by performing the following in Windows’ command line interface: ipconfig /release ipconfig /renew Assigning a WAN IP Address If you require remote management through the WAN interface, then follow the procedure described below.

  • Page 33: Assign Wan Interface To Voip Traffic

    User's Manual 3. Assigning Data-Router LAN and WAN IP Addresses From the 'Routing Mode' drop-down list, select NAPT. Select the 'Default Route' check box. Click OK. Assign WAN Interface to VoIP Traffic If you require remote management through the WAN interface, then follow the procedure described in this section.

  • Page 34: Configuring Quality Of Service

    Mediant 800 MSBR Figure 3-6: Assigning SIP Interface to WAN Open the Media Realm Table page (Configuration tab > VoIP menu > Media submenu > Media Realm Configuration) and configure media interfaces on the WAN interface. Figure 3-7: Assigning WAN Interface to Media Realm Configure SRDs and associate them with these SIP signaling and media interfaces.

  • Page 35: Defining Voip Tx Traffic Shaping Classes

    User's Manual 3. Assigning Data-Router LAN and WAN IP Addresses Click the New button; the following page appears. Figure 3-9: Selecting Device for Traffic Shaping From the 'Device' drop-down list, select Default WAN device, and then click OK; the following page appears: Figure 3-10: Defining Traffic Shaping In the ‘Tx Bandwidth’...

  • Page 36: Defining Voip Traffic Matching Rules

    Mediant 800 MSBR Figure 3-12: Defining Shaping Class (for VoIP Tx Traffic) Configure the following: From the 'Queue Priority' drop-down list, select 0 (Highest), i.e., the highest priority. In the 'Bandwidth - Reserved' field, enter "1000" (i.e., 1 Mbps). From the 'Maximum' drop-down list, select Unlimited. From the 'Policy' drop-down list, select Priority.
  • Page 37 User's Manual 3. Assigning Data-Router LAN and WAN IP Addresses • Outbound TCP connections from WAN port 5060-5061 sent to any destination must be matched to Traffic Shaping class “VOIP Tx”. Outbound packets on this connection will originate from an arbitrary port, but will be destined to port 5060- 5061.
  • Page 38 Mediant 800 MSBR Figure 3-16: Defining Incoming SIP Ports In the 'Service Name' field, enter the service, and then click New Server Ports; the following page appears. Figure 3-17: Defining SIP Ports (e.g. TCP) Define the TCP and UDP protocol and their ports, and then click OK. Click OK again.
  • Page 39 User's Manual 3. Assigning Data-Router LAN and WAN IP Addresses Figure 3-19: Matching Rule for Received RTP Traffic The final traffic matching rule configuration for WAN Tx RTP and SIP signaling is shown below. Figure 3-20: Traffic Matching Rule for WAN Tx/Rx RTP and SIP Signaling Version 6.6 Mediant 800 MSBR...

  • Page 40: Configuring Virtual Routing And Forwarding

    Mediant 800 MSBR Configuring Virtual Routing and Forwarding The Virtual Routing and Forwarding (VRF) Lite feature enables the ability to use a single physical router as several logical routers. Each VRF is associated with its own routing table. To create fully separated logical routers on the same physical router, every interface can be mapped to a specified VRF and static routes can be added to it.

  • Page 41: Management Tools

    Part II Management Tools...

  • Page 43: Introduction

    Embedded HTTP/S-based Web server - see 'Web-based Management' on page  Command Line Interface (CLI) - see 'CLI-Based Management' on page  AudioCodes Element Management System - see EMS-Based Management on page  Simple Network Management Protocol (SNMP) browser software - see 'SNMP-Based Management' on page ...
  • Page 44 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 45: Web-Based Management

    User's Manual 5. Web-Based Management Web-Based Management The device provides an embedded Web server (hereafter referred to as Web interface), supporting fault management, configuration, accounting, performance, and security (FCAPS), including the following:  Full configuration  Software and configuration upgrades ...

  • Page 46: Accessing The Web Interface

    Mediant 800 MSBR 5.1.2 Accessing the Web Interface The procedure below describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see 'Computer Requirements' on page 45). In the Web browser, specify the IP address of the device (e.g., http://10.1.10.10); the Web interface's Login window appears, as shown below: Figure 5-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, user name and...

  • Page 47: Toolbar Description

    Figure 5-2: Areas of Web GUI Description of the Web GUI Areas Item # Description Displays AudioCodes (corporate) logo image. Displays the product name. Toolbar, providing frequently required command buttons. For more information, see 'Toolbar Description' on page 47. Displays the username of the Web user that is currently logged in.

  • Page 48: Navigation Tree

    Mediant 800 MSBR Icon Button Description Name Note: This icon is grayed out when not applicable to the currently opened page. Burn Saves parameter settings to flash memory (see 'Saving Configuration' on page 624). Device Opens a drop-down list with frequently needed commands: Actions ...

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

    User's Manual 5. Web-Based Management Figure 5-4: Navigating in Hierarchical Menu Tree (Example) Note: The figure above is used only as an example. The displayed menus depend on supported features based on the Software License Key installed on your device. 5.1.5.1 Displaying Navigation Tree in Basic and Full View You can view an expanded or reduced display of the Navigation tree.

  • Page 50: Showing / Hiding The Navigation Pane

    Mediant 800 MSBR Figure 5-5: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 5.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

    User's Manual 5. Web-Based Management 5.1.6 Working with Configuration Pages The configuration pages contain the parameters for configuring the device and are displayed in the Work pane. 5.1.6.1 Accessing Pages The configuration pages are accessed by clicking the required page item in the Navigation tree.
  • Page 52 Mediant 800 MSBR display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. 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.

  • Page 53: Modifying And Saving Parameters

    User's Manual 5. Web-Based Management 5.1.6.3 Modifying and Saving Parameters When you modify a parameter value on a page, the Edit symbol appears to the right of the parameter. This indicates that the parameter has been modified, but has yet to be applied (submitted).

  • Page 54: Working With Tables

    Mediant 800 MSBR Figure 5-10: Value Reverts to Previous Valid Value 5.1.6.4 Working with Tables This section describes how to work with configuration tables, which are provided in basic or enhanced design, depending on the configuration page. 5.1.6.4.1 Basic Design Tables A few of the tables in the Web interface are in basic design format.
  • Page 55 User's Manual 5. Web-Based Management 5.1.6.4.2 Enhanced Design Tables Most of the tables in the Web interface are designed in the enhanced table format. The figure below displays a typical table in the enhanced design format and the subsequent table describes its command buttons and areas. Figure 5-12: Displayed Details Pane Enhanced Table Design Description Item #...

  • Page 56: Searching For Configuration Parameters

    Mediant 800 MSBR Item # Button Links to access additional configuration tables related to the current configuration. If the configuration of an entry row is invalid, the index of the row is highlighted in red, as shown below: Figure 5-13: Invalid Configuration with Index Highlighted in Red The table also enables you to define the number of rows to display on the page and to navigate between pages displaying multiple rows.
  • Page 57 User's Manual 5. Web-Based Management  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 58: Creating A Login Welcome Message

    Mediant 800 MSBR 5.1.8 Creating a Login Welcome Message You can create a Welcome message box that is displayed on the Web Login page for logging in to the Web interface. The figure below displays an example of a Welcome message: Figure 5-16: User-Defined Web Welcome Message after Login To enable and create a Welcome message, use the WelcomeMessage table ini file...

  • Page 59: Getting Help

    User's Manual 5. Web-Based Management 5.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 60: Logging Off The Web Interface

    Mediant 800 MSBR 5.1.10 Logging Off the Web Interface The procedure below describes how to log off the Web interface.  To log off the Web interface: On the toolbar, click the Log Off icon; the following confirmation message box appears: Figure 5-18: Log Off Confirmation Box Click OK;...
  • Page 61 User's Manual 5. Web-Based Management In addition to the color-coded status information depicted on the graphical display of the device, the Home page displays various read-only information in the General Information pane:  IP Address: IP address of the device ...
  • Page 62 Mediant 800 MSBR Item # Description (green) synchronized RAI Alarm: Remote Alarm Indication (RAI), also known (yellow) as the Yellow Alarm LOS/LOF Alarm: Loss due Not Connected: No FXO line is to LOS (Loss of Signal) or connected to this port or port out of (red) LOF (Loss of Frame) service due to Serial Peripheral...

  • Page 63: Assigning A Port Name

    User's Manual 5. Web-Based Management Item # Description  (green): Link is working  (gray): Link is not configured  (red): Link error To view detailed port information, click the port icon (see Viewing Ethernet Port Information on page 671). Fast Ethernet LAN port status icons.

  • Page 64: Configuring Web User Accounts

    Mediant 800 MSBR Figure 5-20: Text Box for Entering Port Name Type a brief description for the port, and then click Apply Port Info. Configuring Web User Accounts You can create up to 10 Web user accounts for the device. Up to five Web users can simultaneously be logged in to the device's Web interface.

  • Page 65: Basic User Accounts Configuration

    User's Manual 5. Web-Based Management By default, the device is pre-configured with the following two Web user accounts: Pre-configured Web User Accounts User Access Level Username Password (Case-Sensitive) (Case-Sensitive) Security Administrator Admin Admin Monitor User User After you log in to the Web interface, the username is displayed on the toolbar. If the Web session is idle (i.e., no actions are performed) for more than five minutes, the Web session expires and you are once again requested to login with your username and password.
  • Page 66 Mediant 800 MSBR Notes: • The access level of the Security Administrator cannot be modified. • The access level of the second user account can be modified only by the Security Administrator. • The username and password can be a string of up to 19 characters. When you log in to the Web interface, the username and password string values are case-sensitive, according to your configuration.

  • Page 67: Advanced User Accounts Configuration

    User's Manual 5. Web-Based Management To change the access level of the optional, second account: Under the Account Data for User: User group, from the 'Access Level' drop- down list, select a new access level user. Click Change Access Level; the new access level is applied immediately. 5.3.2 Advanced User Accounts Configuration This section describes advanced Web user account configuration.
  • Page 68 Mediant 800 MSBR  To add Web user accounts with advanced settings: Open the Web Users Table page: • Upon initial access: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). Under the Web Users Table group, click the Create Table button. •...
  • Page 69 User's Manual 5. Web-Based Management Parameter Description  At least two numbers  At least two signs (e.g., the dollar "$" sign)  No spaces in the string  At least four characters different to the previous password Web: Status Defines the status of the Web user.

  • Page 70: Displaying Login Information Upon Login

    Mediant 800 MSBR Parameter Description Web: Block Duration Defines the duration (in seconds) for which the user is blocked when CLI: block-time the user exceeds a user-defined number of failed login attempts. This is configured by the 'Deny Access On Fail Count' parameter (see 'Configuring Web Security Settings' on page 71).

  • Page 71: Configuring Web Security Settings

    User's Manual 5. Web-Based Management Figure 5-24: Login Information Window Configuring Web Security Settings The WEB Security Settings page is used to define a secure Web access communication method. For a description of these parameters, see 'Web and Telnet Parameters' on page 762.

  • 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-12809...

  • Page 73: Configuring Web And Telnet Access List

    User's Manual 5. Web-Based Management  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader. Access the device using the following URL: https://<host name or IP address>; the device prompts for a username and password. Enter the password only.

  • Page 74: Configuring Radius Settings

    Mediant 800 MSBR 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. To save the changes to flash memory, see 'Saving Configuration' on page 624. Notes: •...

  • Page 75: Cli-Based Management

    User's Manual 6. CLI-Based Management CLI-Based Management This section provides an overview of the CLI-based management and configuration relating to CLI management. The device's CLI-based management interface can be accessed using the RS-232 serial port or by using Secure SHell (SSH) or Telnet through the Ethernet interface.

  • Page 76: Enabling Cli Using Ssh And Rsa Public Key

    Mediant 800 MSBR Enabling CLI using SSH and RSA Public Key The device's CLI can be accessed using Telnet. However, 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 77 User's Manual 6. CLI-Based Management Figure 6-3: SSH Settings - Pasting Public RSA Key in 'Admin Key' Field For additional security, you can set the 'Require Public Key' to Enable. This ensures that SSH access is only possible by using the RSA key and not by using user name and password.

  • Page 78: Establishing A Cli Session

    Mediant 800 MSBR Establishing a CLI Session The procedure below describes how to establish a CLI session with the device. Notes: • The default login username and password are both "Admin" (case- sensitive). • Only the primary User Account, which has Security Administration access level (200) can access the device using Telnet.

  • Page 79: Configuring Tacacs+ For Cli Login

    User's Manual 6. CLI-Based Management Configuring TACACS+ for CLI Login This section describes how to enable and configure Terminal Access Controller Access- Control System (TACACS+). TACACS+ is a security protocol for centralized username and password verification. TACACS+ can be used for validating users attempting to gain access to the device through CLI.
  • Page 80 Mediant 800 MSBR The procedure below describes how to configure TACACS+ through CLI.  To configure TACACS+ through the CLI: Establish serial communication with the device. At the prompt, type the following command to access the data interface and then press Enter: # configure data At the prompt, type the TACACS+ commands, as required, to enable and configure...

  • Page 81: Snmp-Based Management

    User's Manual 7. SNMP-Based Management SNMP-Based Management The device provides an embedded SNMP Agent to operate with a third-party SNMP Manager (e.g., element management system or EMS) for operation, administration, maintenance, and provisioning (OAMP) of the device. The SNMP Agent supports standard Management Information Base (MIBs) and proprietary MIBs, enabling a deeper probe into the interworking of the device.

  • Page 82: Configuring Snmp Trap Destinations

    Mediant 800 MSBR Configure the SNMP community strings parameters according to the table below. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 624. To delete a community string, select the Delete check box corresponding to the community string that you want to delete, and then click Submit.

  • Page 83: Configuring Snmp Trusted Managers

    User's Manual 7. SNMP-Based Management SNMP Trap Destinations Parameters Description Parameter Description Web: SNMP Manager Enables the SNMP Manager to receive traps and checks the validity of [SNMPManagerIsUsed_x the configured destination (IP address and port number).  [0] (check box cleared) = (Default) Disables SNMP Manager ...

  • Page 84: Configuring Snmp V3 Users

    Mediant 800 MSBR Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address. Define an IP address in dotted-decimal notation. Click Submit to apply your changes. To save the changes, see 'Saving Configuration' on page 624.
  • Page 85 User's Manual 7. SNMP-Based Management SNMP V3 Users Parameters Parameter Description Index The table index. [SNMPUsers_Index] The valid range is 0 to 9. User Name Name of the SNMP v3 user. This name must be unique. CLI: username [SNMPUsers_Username] Authentication Protocol Authentication protocol of the SNMP v3 user.
  • Page 86 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 87: Ems-Based Management

    User's Manual 8. EMS-Based Management EMS-Based Management AudioCodes Element Management System (EMS) is an advanced solution for standards- based management of MSBRs within VoP networks, covering all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of AudioCodes' families of MSBRs.
  • Page 88 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 89: Cwmp Based Management

    User's Manual 9. TR-069 CWMP Based Management TR-069 CWMP Based Management The device supports TR-069 CPE WAN Management Protocol (CWMP) based management, which is used for remote management of CPE devices. This allows the device to be configured and monitored from a management application running on a remote Auto-Configuration Server (ACS).
  • Page 90 Mediant 800 MSBR Communication between ACS and CPE is defined via Remote Procedure Call (RPC) methods. TR-069 defines a generic mechanism by which an ACS can read or write parameters to configure a CPE and monitor CPE status and statistics. It also defines the mechanism for file transfer and firmware/software management.
  • Page 91 User's Manual 9. TR-069 CWMP Based Management • SetParameterAttributes: Used by the ACS to modify attributes associated with CPE parameter(s). • GetParameterAttributes: Used by the ACS to read the attributes associated with CPE parameter(s). • AddObject: Used by the ACS to create a new instance of a multi-instance object—a collection of parameters and/or other objects for which multiple instances are defined.

  • Page 92: 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 93 Configures voice coder used by specific FXS line. ♦ 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 Version 6.6 Mediant 800 MSBR...

  • Page 94: Configuring Tr-069

    Mediant 800 MSBR • InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP: Configures SIP parameters specific to the UA such as Proxy server. • InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.RTP: Configures various RTP parameters for the FXS lines such as RTCP and SRTP. Configuring TR-069 The CWMP/TR-069 Settings page is used to enable and configure TR-069. Notes: For a description of the TR-069 parameters, see 'TR-069 Parameters' on page 769.

  • Page 95: Ini File-Based Management

    User's Manual 10. INI File-Based Management INI File-Based Management The device can be configured using an ini file, which is a text-based file with an ini file extension name that can be created using any standard text-based editor such as Notepad.
  • Page 96 Mediant 800 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 97: General Ini File Formatting Rules

    User's Manual 10. INI File-Based Management CodersGroup0 0 = g711Alaw64k, 20, 0, 255, 0; CodersGroup0 1 = eg711Ulaw, 10, 0, 71, 0; [ \CodersGroup0 ] Note: Do not include read-only parameters in the table ini file parameter as this can cause an error when attempting to load the file to the device.

  • Page 98: Modifying An Ini File

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

  • Page 99: General System Settings

    Part III General System Settings...

  • Page 101: Configuring Certificates

    User's Manual 11. Configuring Certificates Configuring Certificates The Certificates page allows you to configure X.509 certificates, which are used for secure management of the device, secure SIP transactions, and other security applications. Note: The device is shipped with an active TLS setup. Thus, configure certificates only if required.

  • Page 102: Loading A Private Key

    Mediant 800 MSBR Copy the text and send it to your security provider. The security provider, also known as Certification Authority or CA, signs this request and then sends you a server certificate for the device. Save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE"...
  • Page 103 User's Manual 11. Configuring Certificates load them over a physically-secure connection such as a back-to-back Ethernet cable connected directly to the managing computer.  To replace the device's private key: Your security administrator should provide you with a private key in either textual PEM (PKCS #7) or PFX (PKCS #12) format.

  • Page 104: Mutual Tls Authentication

    Mediant 800 MSBR 11.3 Mutual TLS Authentication By default, servers using TLS provide one-way authentication. The client is certain that the identity of the server is authentic. When an organizational PKI is used, two-way authentication may be desired - both client and server should be authenticated using X.509 certificates.

  • Page 105: Configuring Certificate Revocation Checking (Ocsp)

    User's Manual 11. Configuring Certificates  To change the subject name and regenerate the self-signed certificate: Before you begin, ensure the following: • You have a unique DNS name for the device (e.g., dns_name.corp.customer.com). This name is used to access the device and should therefore, be listed in the server certificate.

  • Page 106: Loading Certificate Chain For Trusted Root

    Mediant 800 MSBR send the SNMP trap, acCertificateExpiryNotifiaction to notify of the impending certificate expiration.  To configure TLS certificate expiry checks and notification: Open the Certificates page (see 'Replacing the Device's Certificate' on page 101). In the 'TLS Expiry Check Start' field, enter the number of days before the installed TLS server certificate is to expire at which the device must send a trap to notify of this.

  • Page 107: Date And Time

    User's Manual 12. Date and Time Date and Time The date and time of the device can be configured manually or it can be obtained automatically from a Simple Network Time Protocol (SNTP) server. 12.1 Configuring Date and Time Manually The date and time of the device can be configured manually.
  • Page 108 Mediant 800 MSBR to the counter, causing the clock to update quicker and catch up to the correct time. The advantage of this method is that it does not introduce any disparity in the system time that is noticeable to an end user or that could corrupt call timeouts and timestamps. The procedure below describes how to configure SNTP.

  • Page 109: Configuring Power Over Ethernet

    User's Manual 13. Configuring Power over Ethernet Configuring Power over Ethernet The device supports Power over Ethernet (PoE) according to the IEEE 802.3af-2003 standards, providing power on the Ethernet lines through all the LAN ports. The ports can transfer electrical power, along with the usual data, over the Ethernet cable to connected equipment (e.g., IP phones) that are capable of receiving PoE.
  • Page 110 Mediant 800 MSBR The procedure below describes how to configure PoE through the Web interface.  To configure PoE through the Web interface: Open the Power Over Ethernet Settings page (Configuration tab > System menu > Power over Ethernet Settings). Figure 13-1: Power Over Ethernet Settings Page Select the 'Index' radio button corresponding to the required LAN port.

  • Page 111: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 113: Network

    User's Manual 14. Network Network This section describes the network-related configuration. 14.1 Configuring IP Network Interfaces You can configure a single VoIP network interface for all applications, which includes OAMP (management traffic), call control (SIP messages), and media (RTP traffic), or you can configure multiple logical, IP network interfaces for these applications.
  • Page 114 Mediant 800 MSBR You can configure up to 12 interfaces, consisting of up to 11 Control and Media interfaces and 1 OAMP interface. The default VoIP interface is as follows:  Application type: OAMP + Media + Control  IP address: 192.168.0.2 with prefix length 24 (i.e., subnet mask 255.255.255.0) ...
  • Page 115 User's Manual 14. Network Click Done to validate the interface. If the interface is not valid (e.g., if it overlaps with another interface in the table or if it does not adhere to the other rules as summarized in 'Multiple Interface Table Configuration Summary and Guidelines' on page 117), a warning message is displayed.
  • Page 116 Mediant 800 MSBR Parameter Description CLI: gateway traffic is sent from this interface to an unknown destination (i.e., not in the [InterfaceTable_Gate same subnet and not defined for any static routing rule), it is forwarded to way] this default gateway. Notes: For valid configuration, see 'Multiple Interface Table Configuration Rules' on page 117.

  • Page 117: Assigning Ntp Services To Application Types

    User's Manual 14. Network Parameter Description used as the interface to the WAN, then you need to define NAT rules (using the NATTranslation parameter) to translate the VoIP LAN IP addresses (defined in the Multiple Interface table and associated with SIP and media interfaces) into global, public IP addresses.

  • Page 118: Troubleshooting The Multiple Interface Table

    Mediant 800 MSBR Notes: • When configuring the network interfaces and VLANs in the Multiple Interface table using the Web interface, it is recommended to check that your configuration is valid, by clicking the Done button in the Multiple Interface Table page. •...

  • Page 119: Voip Interface Per Application Type

    User's Manual 14. Network IP Routing table: Two routes are configured for directing traffic for subnet 201.201.0.0/16 to 192.168.11.10, and all traffic for subnet 202.202.0.0/16 to 192.168.11.1: Example of IP Routing Table Destination IP Gateway IP Prefix Length Metric Interface Name Address Address 201.201.0.0...

  • Page 120: Voip Interfaces With Multiple Default Gateways

    Mediant 800 MSBR Example of VoIP Interfaces of Combined Application Types in Multiple Interface Table Application Prefix VLAN Interface Index IP Address Gateway Type Length Name OAMP 192.168.0.2 192.168.0.1 Mgmt Media & 200.200.85.14 200.200.85.1 MediaCntrl1 Control Media & 200.200.86.14 200.200.86.1 MediaCntrl2 Control IP Routing table: A routing rule is required to allow remote management from a host...

  • Page 121: Configuring The Ip Routing Table

    User's Manual 14. Network 14.2 Configuring the IP Routing Table The IP Routing Table page allows you to define up to 30 static IP routing rules for the device. These rules can be associated with a network interface (defined in the Multiple Interface table) and therefore, the routing decision is based on the source subnet/VLAN.
  • Page 122 Mediant 800 MSBR IP Routing Table Description Parameter Description Destination IP Address Defines the IP address of the destination host/network. The CLI: destination destination can be a single host or a whole subnet, depending on [StaticRouteTable_Destinatio the Prefix Length configured for this routing rule. Prefix Length Defines the Classless Inter-Domain Routing (CIDR)-style CLI: prefix-length...

  • Page 123: Interface Column

    User's Manual 14. Network 14.2.1 Interface Column This example describes the configuration of static IP routing rules. Configure network interfaces in the Multiple Interface table, as shown below: Configured Network Interfaces in Multiple Interface Table Applicati Prefix Index IP Address Gateway VLAN ID Interface Name on Type...

  • Page 124: Configuring Quality Of Service

    Mediant 800 MSBR configure a routing rule, the device sends a notification message to the Syslog server reporting the problem. Common routing rule configuration errors may include the following:  The IP address specified in the 'Gateway IP Address' field is unreachable from the interface specified in the 'Interface Name' field.
  • Page 125 User's Manual 14. Network Application Traffic / Network Types Class-of-Service (Priority) RTCP traffic Media Premium media T.38 traffic Media Premium media Control Premium control SIP over TLS (SIPS) Control Premium control Syslog Management Bronze SNMP Traps Management Bronze Varies according to DNS settings: Depends on traffic type: DNS client ...

  • Page 126: Dns

    Mediant 800 MSBR Configure the desired DiffServ (Layer-3 QoS) values for the following traffic classes: • Media Premium QoS: this affects Media RTP packets sent by the VoIP towards the LAN. • Control Premium QoS: this affects Control Protocol (SIP) packets sent by the VoIP towards the LAN.

  • Page 127: Configuring The Internal Srv Table

    User's Manual 14. Network  To configure the internal DNS table: Open the Internal DNS Table page (Configuration tab > VoIP menu > Network submenu > DNS submenu > Internal DNS Table). Click Add; the following dialog box appears: Figure 14-5: Internal DNS Table - Add Record Dialog Box Configure the DNS rule, as required.
  • Page 128 Mediant 800 MSBR Notes: • If the Internal SRV table is configured, the device initially attempts to resolve a domain name using this table. If the domain name isn't found, the device performs a Service Record (SRV) resolution using an external DNS server configured in the Multiple Interface table (see 'Configuring IP Network Interfaces' on page 113).

  • Page 129: Configuring Nfs Settings

    User's Manual 14. Network Parameter Description Transport Type Defines the transport type. CLI: transport-type  [0] UDP (default) [Srv2Ip_TransportType]  [1] TCP  [2] TLS DNS Name (1-3) Defines the first, second or third DNS A-Record to which the host CLI: dns-name-1|2|3 name is translated.
  • Page 130 Mediant 800 MSBR Figure 14-7: Add Record Dialog Box for NFS Configure the NFS parameters according to the table below. Click the Submit button; the remote NFS file system is immediately applied, which can be verified by the appearance of the 'NFS mount was successful' message in the Syslog server.

  • Page 131: Network Address Translation Support

    User's Manual 14. Network Parameter Description Authentication Type Authentication method used for accessing the remote file system. CLI: authentication-type  [0] Null [NFSServers_AuthType]  [1] Unix (default) User ID User ID used in authentication when using Unix. CLI: uid The valid range is 0 to 65537. The default is 0. [NFSServers_UID] Group ID Group ID used in authentication when using Unix.

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

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

  • Page 133: Configuring Nat Translation Per Ip Interface

    User's Manual 14. Network 14.6.1.2 Configuring NAT Translation per IP Interface The NAT Translation table defines network address translation (NAT) rules for translating source IP addresses per VoIP interface (SIP control and RTP media traffic) into NAT IP addresses (global or public), when the device is located behind NAT. This allows, for example, the separation of VoIP traffic between different ITSP’s, and topology hiding of internal IP addresses to the “public”...

  • Page 134: Remote Ua Behind Nat

    Mediant 800 MSBR NAT Translation Table Parameters Parameter Description Index Defines the table index entry. This table can include up to 32 CLI: index entries. [NATTranslation_Index] Source Interface Name Defines the name of the IP interface, as appears in the Multiple CLI: SourceIPInterfaceName Interface table.

  • Page 135: First Incoming Packet Mechanism

    User's Manual 14. Network Figure 14-11: Remote UA behind NAT 14.6.2.1 First Incoming Packet Mechanism If the remote device resides behind a NAT device, it’s possible that the device can activate the RTP/RTCP/T.38 streams to an invalid IP address / UDP port. To avoid such cases, the device automatically compares the source address of the first received incoming RTP/RTCP/T.38 stream with the IP address and UDP port of the remote device when the session was initially opened.

  • Page 136: Robust Receipt Of Media Streams

    14.7 Robust Receipt of Media Streams The “robust-media” mechanism is an Audiocodes proprietary mechanism to filter out unwanted media (i.e., RTP, RTCP, and T.38) streams that are sent to the same port number on the device. In practice, the media RTP/RTCP ports may receive additional multiple unwanted media streams as result of traces of previous calls, call control errors, or deliberate attacks.

  • Page 137: Security

    User's Manual 15. Security Security This section describes the VoIP security-related configuration. 15.1 Configuring Firewall Settings The device provides an internal firewall that enables you to configure network traffic filtering rules (access list). You can add up to 50 firewall rules. The access list offers the following firewall possibilities: ...
  • Page 138 Mediant 800 MSBR  To add firewall rules: Open the Firewall Settings page (Configuration tab > VoIP menu > Security submenu > Firewall Settings). Click the Add button; the following dialog box appears: Figure 15-1: Firewall Settings Page - Add Record Configure the firewall parameters, as required.
  • Page 139 User's Manual 15. Security The firewall rules in the above configuration example do the following:  Rules 1 and 2: Typical firewall rules that allow packets ONLY from specified IP addresses (e.g., proxy servers). Note that the prefix length is configured. ...
  • Page 140 Mediant 800 MSBR Parameter Description Protocol Defines the protocol type (e.g., UDP, TCP, ICMP, ESP or 'Any') or CLI: protocol the IANA protocol number in the range of 0 (Any) to 255. [AccessList_Protocol] Note: This field also accepts the abbreviated strings 'SIP' and 'HTTP'.

  • Page 141: Configuring General Security Settings

    User's Manual 15. Security 15.2 Configuring General Security Settings The General Security Settings page is used to configure various security features. For a description of the parameters appearing on this page, refer 'Configuration Parameters Reference' on page 755.  To configure the general security parameters: Open the General Security Settings page (Configuration tab >...

  • Page 142: Intrusion Detection System

    Mediant 800 MSBR 15.3 Intrusion Detection System The device can be configured to detect malicious attacks on its system and send SNMP traps if malicious activity is identified. The Intrusion Detection System (IDS) is an important feature for Enterprises to ensure legitimate calls are not being adversely affected by attacks and to prevent Theft of Service and unauthorized access.

  • Page 143: Configuring Ids Policies

    User's Manual 15. Security 15.3.2 Configuring IDS Policies Configuring IDS policies is a two-stage process done in the following tables: IDS Policy table: Defines a name and description for the policy. You can define up to 20 policies. IDS Rules table: Defines the actual IDS rules per policy. Each policy can be configured with up to 20 rules.
  • Page 144 Mediant 800 MSBR IDS Policy Table Parameters Parameter Description Index Defines the table row number for the policy. CLI: policy [IDSPolicy_Index] Name Defines a name for the policy. CLI: rule The valid value is a string of up to 20 characters. [IDSPolicy_Description] Description Defines an arbitrary description of the policy.
  • Page 145 User's Manual 15. Security IDS Rule Table Parameters Parameter Description Index Defines the table row number for the rule. CLI: rule-id [IDSRule_RuleID] Reason Defines the type of intrusion attack (malicious event). CLI: reason  [0] Any = All events listed below are considered as attacks and [IDSRule_Reason] are counted together.

  • Page 146: Assigning Ids Policies

    Mediant 800 MSBR Parameter Description Minor-Alarm Threshold Defines the threshold that if crossed a minor severity alarm is sent. CLI: minor-alrm-thr The valid range is 1 to 1,000,000. A value of 0 or -1 means not [IDSRule_MinorAlarmThre defined. shold] Major-Alarm Threshold Defines the threshold that if crossed a major severity alarm is sent.
  • Page 147 User's Manual 15. Security IDS Match Table Parameters Parameter Description Index Defines the table row number for the rule. [IDSMatch_Index] SIP Interface Defines the SIP Interface(s) to which you want to assign the IDS CLI: sip-interface policy. This indicates the SIP Interfaces that are being attacked. The [IDSMatch_SIPInterface] entered value must be the ID of the SIP Interface.

  • Page 148: Viewing Ids Alarms

    Mediant 800 MSBR 15.3.4 Viewing IDS Alarms The device uses SNMP (and Syslog) to notify the detection of malicious attacks. The trap displays the IDS Policy and Rule, and the Policy-Match index. The device sends the SNMP alarm, acIDSPolicyAlarm whenever a threshold of a specific IDS Policy rule is crossed.
  • Page 149 User's Manual 15. Security Type Description Syslog String   Classification failure establish-classify-fail Dialog Establishment   Routing failure establish-route-fail Failure   Other local rejects (prior to SIP 180 response) establish-local-reject   Remote rejects (prior to SIP 180 response) establish-remote-reject ...
  • Page 150 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 151: Media

    User's Manual 16. Media Media This section describes the media-related configuration. 16.1 Configuring Voice Settings The Voice Settings page configures various voice parameters such as voice volume, silence suppression, and DTMF transport type. For a detailed description of these parameters, see 'Configuration Parameters Reference' on page 755. ...

  • Page 152: Silence Suppression (Compression)

    Mediant 800 MSBR 16.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 153 User's Manual 16. Media  To configure echo cancellation using the Web interface: Configure line echo cancellation: Open the Voice Settings page (Configuration tab > VoIP menu > Media submenu > Voice Settings). Set the 'Echo Canceller' field (EnableEchoCanceller) to Enable. Enable acoustic echo cancellation for SBC calls: In the Voice Settings page, configure the following parameters: ♦...

  • Page 154: Fax And Modem Capabilities

    Mediant 800 MSBR 16.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 155: Fax/Modem Operating Modes

    User's Manual 16. Media 16.2.1 Fax/Modem Operating Modes The device supports two modes of operation:  Fax/modem negotiation that is not performed during the establishment of the call.  Voice-band data (VBD) mode for V.152 implementation (see 'V.152 Support' on page 166): fax/modem capabilities are negotiated between the device and the remote endpoint at the establishment of the call.
  • Page 156 Mediant 800 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 157: Fax / Modem Transport Mode

    User's Manual 16. Media 16.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 158: Fax/Modem Bypass Mode

    Mediant 800 MSBR  To configure fax fallback mode:  In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to Fax Fallback (IsFaxUsed = 3). 16.2.2.4 Fax/Modem Bypass Mode In this proprietary mode, when fax or modem signals are detected, the channel automatically switches from the current voice coder to a high bit-rate coder, according to the 'Fax/Modem Bypass Coder Type' parameter (FaxModemBypassCoderType).

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

    Mediant 800 MSBR Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, BellModemTransportType to 2 (Bypass). Set the ini file parameter, NSEMode parameter to 1 (enables NSE). Set the ini file parameter, NSEPayloadType parameter to 100. 16.2.2.6 Fax / Modem Transparent with Events Mode In this mode, fax and modem signals are transferred using the current voice coder with the following automatic adaptations:...

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

    User's Manual 16. Media Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0). Set the ini file parameter, BellModemTransportType to 0 (transparent mode).

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

    Mediant 800 MSBR To configure whether to pass V.34 over T38 fax relay, or use Bypass over the High Bit Rate coder (e.g. PCM A-Law), use the 'V.34 Fax Transport Type' parameter (V34FaxTransportType). You can use the 'SIP T38 Version' parameter (SIPT38Version) in the Advanced Parameters page (Configuration tab >...

  • Page 163: Fax Relay For Sg3 Fax Machines

    User's Manual 16. Media  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). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0).

  • Page 164: Modem Relay

    Contact: <sip:318@10.8.6.55:5060> Supported: em,100rel,timer,replaces,path,resource-priority,sdp- anat Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Remote-Party-ID: <sip:318@10.8.211.250>;party=calling;privacy=off;screen=no;screen- ind=0;npi=1;ton=0 Remote-Party-ID: <sip:2001@10.8.211.250>;party=called;npi=1;ton=0 User-Agent: Audiocodes-Sip-Gateway-/v.6.00A.013.007 Content-Type: application/sdp Content-Length: 433 o=AudiocodesGW 1938931006 1938930708 IN IP4 10.8.6.55 s=Phone-Call c=IN IP4 10.8.6.55 t=0 0 m=audio 6010 RTP/AVP 18 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no...

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

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

  • Page 166: Support

    Mediant 800 MSBR methods for CED tone transfer and sends both answering tone types. Only when the answering tone is detected, does the device send the fax or modem. To support this functionality, you need to configure a Coders Group (in the Coders Group table - see 'Configuring Coder Groups' on page 242) that includes the T.38, V.150, and G.711/VBD coders.

  • Page 167: Fax Transmission Behind Nat

    User's Manual 16. Media 16.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 168: Comfort Noise Generation

    Mediant 800 MSBR In certain scenarios, the Optimization Factor is set to 13: One of the purposes of the Jitter Buffer mechanism is to compensate for clock drift. If the two sides of the VoIP call are not synchronized to the same clock source, one RTP source generates packets at a lower rate, causing under-runs at the remote Jitter Buffer.

  • Page 169: Dual-Tone Multi-Frequency Signaling

    User's Manual 16. Media 16.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 16.3.3.1 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint. These methods and their configuration are configured in the DTMF & Dialing page (Configuration tab >...

  • Page 170: Configuring Rfc 2833 Payload

    Mediant 800 MSBR Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the '1st Tx DTMF Option' parameter to INFO (Cisco) (TxDTMFOption = 3). Note: In this mode, DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF).

  • Page 171: Configuring Rtp Base Udp Port

    User's Manual 16. Media 16.3.4 Configuring RTP Base UDP Port You can configure the range of UDP ports for RTP, RTCP, and T.38. The UDP port range can be configured using media realms in the Media Realm table, allowing you to assign different port ranges (media realms) to different interfaces.

  • Page 172: Configuring Ip Media Settings

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

  • Page 173: Configuring Analog Settings

    User's Manual 16. Media 16.5 Configuring Analog Settings The Analog Settings page allows you to configure various analog parameters. For a detailed description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 755. This page also selects the type (USA or Europe) of FXS and/or FXO coefficient information.

  • Page 174: Configuring Media Realms

    Once you have configured a Media Realm, you can configure it with the following:  Quality of Experience parameters for reporting to AudioCodes SEM server used for monitoring the quality of calls (see Configuring Quality of Experience Parameters per Media Realm on page 176) ...
  • Page 175 User's Manual 16. Media  To define a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > Media submenu > Media Realm Configuration). Click the Add button; the following appears: Figure 16-10: Media Realm Page - Add Record Dialog Box Configure the parameters as required.

  • Page 176: Configuring Quality Of Experience Per Media Realm

    Mediant 800 MSBR Parameter Description  BaseUDPport to BaseUDPport + 255*10  Port ranges over 60,000 must not be used. Number of Media Defines the number of media sessions associated with the range of ports. Session Legs This is the number of media sessions available in the port range. For CLI: session-leg example, 100 ports correspond to 10 media sessions, since ports are [CpMediaRealm_Medi...
  • Page 177 The QoE feature is available only if the device is installed with the relevant Software License Key. • To configure the address of the AudioCodes Session Experience Manager (SEM) server to where the device reports the QoE, see 'Configuring SEM Server for Media Quality of Experience' on page 181.
  • Page 178 Mediant 800 MSBR SEM indicating this change. If the value changes to 3.3, it sends a yellow state (i.e., medium quality); if the value changes to 3.5, it sends a green state. Configure the parameters as required. See the table below for a description of each parameter.

  • Page 179: Configuring Bandwidth Management Per Media Realm

    User's Manual 16. Media Parameter Description Green Yellow Operation Defines the action that is done if the green-yellow threshold is CLI: green-yellow-operation crossed. [QOERules_GreenYellowOpera  [1] Notify = (Default) Device sends a report to the SEM tion] server.  [2] Activate 2198 = RTP redundancy packets are sent to the relevant call leg.
  • Page 180 Mediant 800 MSBR Thus, up to two thresholds can be configured per Media Realm; one for each state transition. Notes: • This feature is available only if the device is installed with the relevant Software License Key. • For your bandwidth management settings to take effect, you must reset the device.

  • Page 181: Configuring Server For Media Quality Of Experience

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

  • Page 182: Configuring Media Security

    Mediant 800 MSBR 16.9 Configuring Media Security The device supports Secured RTP (SRTP) according to RFC 3711. SRTP is used to encrypt RTP and RTCP transport for protecting VoIP traffic. SRTP requires a key exchange mechanism that is performed according to RFC 4568 – “Session Description Protocol (SDP) Security Descriptions for Media Streams”.
  • Page 183 User's Manual 16. Media  To configure media security: Open the Media Security page (Configuration tab > VoIP menu > Media submenu > Media Security). Figure 16-14: Media Security Page Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 624.
  • Page 184 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 185: Services

    User's Manual 17. Services Services This section describes configuration for various supported services. 17.1 Routing Based on LDAP Active Directory Queries The device supports Lightweight Directory Access Protocol (LDAP), enabling call routing decisions based on information stored on a third-party LDAP server (or Microsoft’s Active Directory™...

  • Page 186: Configuring The Device's Ldap Cache

    Mediant 800 MSBR  To configure the LDAP server parameters: Open the LDAP Settings page (Configuration tab > VoIP menu > Services submenu > LDAP Settings). Figure 17-1: LDAP Settings Page The read-only 'LDAP Server Status' field displays one of the following possibilities: •...
  • Page 187 User's Manual 17. Services The handling of LDAP queries with the LDAP cache is shown in the flowchart below: Figure 17-2: LDAP Query Process with Local LDAP Cache The LDAP Settings page is used for configuring the LDAP cache parameters. Notes: •...

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

    Mediant 800 MSBR  To configure the LDAP cache parameters: Open the LDAP Settings page (Configuration tab > VoIP menu > Services submenu > LDAP Settings). Figure 17-3: LDAP Settings Page - Cache Parameters Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 624.
  • Page 189 User's Manual 17. Services Parameters for Configuring Query Attribute Key Query or Query Result Parameter Queried User Domain (Attribute) in AD Example MSLDAPPBXNumAttribute PBX or IP PBX number (e.g., telephoneNumber= Name "telephoneNumber" - default) +3233554447 MSLDAPOCSNumAttribute msRTCSIP- Mediation Server / Lync client number (e.g., Name line=john.smith@compan "msRTCSIP-line")
  • Page 190 Mediant 800 MSBR • "PBX" (PBX:<PBX_number>): used to match a routing rule based on query results of the PBX / IP PBX number (MSLDAPPBXNumAttributeName) • "MOBILE" (MOBILE:<mobile_number>): used to match a routing rule based on query results of the mobile number (MSLDAPMobileNumAttributeName) •...

  • Page 191: Configuring Ad-Based Routing Rules

    User's Manual 17. Services The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 17-4: LDAP Query Flowchart Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page for the LDAP query process.
  • Page 192 Mediant 800 MSBR Figure 17-5: LDAP Parameters for Microsoft Lync Server 2010 Configure the LDAP attribute names as desired. For the Gateway/IP-to-IP application: Configure AD-based Tel-to-IP routing rules: Open the Outbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP submenu >...
  • Page 193 User's Manual 17. Services The table below shows an example for configuring AD-based Tel-to-IP routing rules in the Outbound IP Routing Table: AD-Based Tel-to-IP Routing Rule Configuration Examples Index Dest. Phone Prefix Dest. IP Address PRIVATE: 10.33.45.60 PBX: 10.33.45.65 OCS: 10.33.45.68 MOBILE: 10.33.45.100...

  • Page 194: Querying The Ad For Calling Name

    Mediant 800 MSBR  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases • LDAP functionality is disabled. • LDAP query is successful but call fails (due to, for example, busy line) to all the relevant attribute destinations (private, Lync, PBX, and mobile), and a relevant Tel-to-IP Release Reason (see Alternative Routing for Tel-to-IP Calls on page 341) or SBC Alternative Routing Reason (see Configuring Alternative Routing...

  • Page 195: Least Cost Routing

    User's Manual 17. Services 17.2 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how to configure it. 17.2.1 Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost.
  • Page 196 Mediant 800 MSBR Below are a few examples of how you can implement LCR:  Example 1: This example uses two different Cost Groups for routing local calls and international calls: Two Cost Groups are configured as shown below: Cost Group Connection Cost Minute Cost 1.

  • Page 197: Configuring Lcr

    User's Manual 17. Services  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: Connection Cost Group Time Band...
  • Page 198 Mediant 800 MSBR  To enable LCR: Open the Routing Rule Groups Table page (Configuration tab > VoIP menu > Services submenu > Least Cost Routing > Routing Rule Groups Table). Click the Add button; the Add Record dialog box appears: Figure 17-7: Routing Rule Groups Table - Add Record Configure the parameters as required.

  • Page 199: Configuring Cost Groups

    User's Manual 17. Services Parameter Description Default Cost Determines whether routing rules in the Outbound IP Routing table CLI: lcr-default-cost without an assigned Cost Group are considered a higher cost or lower [RoutingRuleGroups_L cost route compared to other matched routing rules that are assigned CRDefaultCost] Cost Groups.

  • Page 200: Configuring Time Bands For Cost Groups

    Mediant 800 MSBR Cost Group Table Description Parameter Description Index Defines the table index entry. [CostGroupTable_Inde Cost Group Name Defines an arbitrary name for the Cost Group. CLI: cost-group-name The valid value is a string of up to 30 characters. [CostGroupTable_Cost Note: Each Cost Group must have a unique name.
  • Page 201 User's Manual 17. Services Figure 17-9: Time Band Table - Add Record Configure the parameters as required. For a description of the parameters, see the table below. Click Submit; the entry is added to the Time Band table for the relevant Cost Group. Time Band Table Description Parameter Description...

  • Page 202: Assigning Cost Groups To Routing Rules

    Mediant 800 MSBR 17.2.2.4 Assigning Cost Groups to Routing Rules Once you have configured your Cost Groups, you need to assign them to routing rules:  Gateway/IP-to-IP application: Outbound IP Routing table - see Configuring Outbound IP Routing Table on page ...

  • Page 203: Enabling Applications

    User's Manual 18. Enabling Applications Enabling Applications The device supports the following main applications:  Stand-Alone Survivability (SAS) application (see SAS Overview on page 495)  Session Border Control (SBC) application (see SBC Overview on page 425)  Cloud Resilience Package (see CRP Overview on page 487) ...
  • Page 204 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 205: Control Network

    User's Manual 19. Control Network Control Network This section describes configuration of the network at the SIP control level. 19.1 Configuring SRD Table The SRD Settings page allows you to configure up to 32 signaling routing domains (SRD). An SRD is configured with a unique name and assigned a Media Realm. Additional SBC attributes such as media anchoring and user registration can also be configured.
  • Page 206 Mediant 800 MSBR  To configure SRDs: Open the SRD Settings page (Configuration tab > VoIP menu > Control Network submenu > SRD Table). Figure 19-1: SRD Settings Page From the 'SRD Index' drop-down list, select an index for the SRD, and then configure it according to the table below.

  • Page 207: Configuring Sip Interface Table

    User's Manual 19. Control Network Parameter Description  Opening voice channels and allocation of IP media ports are not required.  When two UA's pertain to the same SRD and this parameter is set to [1], and one of the UA's is defined as a foreign user (example, “follow me service”) located on the WAN while the other UA is located on the LAN, then calls between these two UA's can’t be established until this parameter is set to 0, as the device doesn’t interfere in the SIP...
  • Page 208 Mediant 800 MSBR  Separating signaling traffic between networks (e.g., different customers) to use different routing tables, manipulations, SIP definitions, and so on. Note: The SIP Interface table can also be configured using the table ini file parameter, SIPInterface or the CLI command, configure voip > control- network sip-interface.
  • Page 209 User's Manual 19. Control Network Parameter Description Application Type Defines the application type associated with the SIP Interface. [SIPInterface_Applicati  [0] GW/IP2IP (default) = Gateway / IP-to-IP application. onType]  [1] SAS = Stand-Alone Survivability (SAS) application. CLI: application-type  [2] SBC = SBC application.

  • Page 210: Configuring Ip Groups

    Mediant 800 MSBR Parameter Description TCP Keepalive Enable Enables the TCP Keep-Alive mechanism with the IP entity on this SIP interface. TCP keepalive can be used, for example, to keep a NAT entry [SIPInterface_TCPKeep open for clients located behind a NAT server or simply to check that the aliveEnable] connection to the IP entity is available.
  • Page 211 User's Manual 19. Control Network  Call routing rules: • Outgoing IP calls (IP-to-IP or Tel-to-IP): The IP Group identifies the source of the call and is used as the destination of the outgoing IP call (defined in the Outbound IP Routing Table). For Tel-to-IP calls, the IP Group (Serving IP Group) can be used as the IP destination to where all SIP dialogs that are initiated from a Trunk Group are sent (defined in Configuring Hunt Group Settings on page 297).
  • Page 212 Mediant 800 MSBR IP Group Parameters Parameter Description Common Parameters Type Defines the type of IP Group: CLI:type  [0] Server = Used when the destination address, configured by the [IPGroup_Type] Proxy Set, of the IP Group (e.g., ITSP, Proxy, IP-PBX, or Application server) is known.
  • Page 213 User's Manual 19. Control Network Parameter Description Proxy Set ID Assigns a Proxy Set ID to the IP Group. All INVITE messages destined CLI: proxy-set-id to this IP Group are sent to the IP address configured for the Proxy Set. [IPGroup_ProxySetId] Notes: ...
  • Page 214 Mediant 800 MSBR Parameter Description Assigns an SRD to the IP Group. CLI: srd The default is 0. [IPGroup_SRD] Notes:  For this parameter to take effect, a device reset is required.  To configure SRDs, see Configuring SRD Table on page 205. ...
  • Page 215 User's Manual 19. Control Network Parameter Description CLI: re-routing-mode is received) or transfer (i.e., a SIP REFER request is received). [IPGroup_SIPReRouting  [-1] Not Configured (Default) Mode]  [0] Standard = INVITE messages that are generated as a result of Transfer or Redirect are sent directly to the URI, according to the Refer-To header in the REFER message or Contact header in the 3xx response.
  • Page 216 Mediant 800 MSBR Parameter Description are set to the value of the ‘SIP Group Name’ parameter defined for the Serving IP Group. Notes:  This parameter is applicable only to the IP-to-IP application.  If the PreferRouteTable parameter is set to 1, the routing rules in the Outbound IP Routing Table take precedence over this ‘Serving IP Group ID’...
  • Page 217 User's Manual 19. Control Network Parameter Description  [9] P-Called-Party-ID  [10] Contact Notes:  This parameter is applicable only when classification is done according to the Classification table.  If the configured SIP header does not exist in the incoming INVITE message, the classification of the message to a source IP Group fails.
  • Page 218 Mediant 800 MSBR Parameter Description Registration Mode Defines the registration mode for the IP Group: CLI: registration-mode  [0] User initiates registrations (default) [IPGroup_RegistrationM  [1] SBC initiate registrations = Used when the device serves as a ode] client (e.g., with an IP PBX). This functions only with User Info file. ...

  • Page 219: Configuring Proxy Sets Table

    User's Manual 19. Control Network 19.4 Configuring Proxy Sets Table The Proxy Sets Table page allows you to define Proxy Sets. A Proxy Set is a group of Proxy servers defined by IP address or fully qualified domain name (FQDN). You can define up to 32 Proxy Sets, each with up to five Proxy server addresses.
  • Page 220 Mediant 800 MSBR From the 'Proxy Set ID' drop-down list, select an ID for the desired group. Configure the Proxy parameters, as required. For a description of the parameters, see the table below. Click Submit. To save the changes to flash memory, see 'Saving Configuration' on page 624. Proxy Sets Table Parameters Parameter Description...
  • Page 221 User's Manual 19. Control Network Parameter Description Proxies.  When a port number is specified (e.g., domain.com:5080), DNS NAPTR/SRV queries aren't performed, even if ProxyDNSQueryType is set to 1 or 2. Transport Type Defines the transport type of the proxy server. CLI: control-network ...
  • Page 222 Mediant 800 MSBR Parameter Description  Method [2] Random Weights CLI: control-network When the Round Robin algorithm is used, a list of all possible Proxy IP proxy-set > proxy- addresses is compiled. This list includes all IP addresses per Proxy Set, load-balancing- after necessary DNS resolutions (including NAPTR and SRV, if method...
  • Page 223 User's Manual 19. Control Network Parameter Description [ProxySet_ProxySet_ Notes: SRD]  For this parameter to take effect, a device reset is required.  To configure SRDs, see Configuring SRD Table on page 205. Web/EMS: Defines how the device classifies an IP call to the Proxy Set. Classification Input ...
  • Page 224 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 225: Sip Definitions

    User's Manual 20. SIP Definitions SIP Definitions This section describes configuration of SIP parameters. 20.1 Configuring SIP Parameters Many of the stand-alone SIP parameters associated with various features can be configured in the following pages:  SIP General Parameters page: Provides SIP parameters for configuring general SIP features.
  • Page 226 Mediant 800 MSBR  To configure Accounts: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions submenu > Account Table). In the 'Add' field, enter the desired table row index, and then click Add. A new row appears.
  • Page 227 User's Manual 20. SIP Definitions Parameter Description Username Defines the digest MD5 Authentication user name. CLI: user-name The valid value is a string of up to 50 characters. [Account_Userna Password Defines the digest MD5 Authentication password. CLI: password The valid value is a string of up to 50 characters. [Account_Passwo Note: After you click the Apply button, this password is displayed as an asterisk (*).

  • Page 228: Configuring Proxy And Registration Parameters

    Mediant 800 MSBR 20.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 755. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Endpoint Registration Status on page 689.
  • Page 229 User's Manual 20. SIP Definitions  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions submenu > Proxy & Registration). Figure 20-1: Proxy & Registration Page Configure the parameters as required. Click Submit to apply your changes.

  • Page 230: Sip Message Authentication Example

    • The password from the ini file is "AudioCodes". • The equation to be evaluated is "122:audiocodes.com:AudioCodes". According to the RFC, this part is called A1. • The MD5 algorithm is run on this equation and stored for future usage.
  • Page 231 At this time, a new REGISTER request is issued with the following response: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c23940 To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 Server: Audiocodes-Sip-Gateway/Mediant 800 MSBR/v.6.60.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”, nonce="11432d6bce58ddf02e3b5e1c77c010d2",...

  • Page 232: Configuring Sip Message Manipulation

    Mediant 800 MSBR 20.4 Configuring SIP Message Manipulation The Message Manipulations page allows you to define up to 100 SIP message manipulation rules. Each manipulation rule can be assigned any Manipulation Set ID (0 to 19), enabling you to create groups (sets) of manipulation rules whereby rules of a group are configured with the same Manipulation Set ID number.
  • Page 233 User's Manual 20. SIP Definitions The figure below illustrates a SIP message manipulation example: Figure 20-2: SIP Header Manipulation Example Notes: • For a detailed description of the syntax for configuring SIP message manipulation rules, refer to SIP Message Manipulations Quick Reference Guide.
  • Page 234 Mediant 800 MSBR headers. They can only be modified and only on requests that initiate new dialogs. Mandatory SIP headers include To, From, Via, CSeq, Call- Id, and Max-Forwards. • The Message Manipulations table can also be configured using the table ini file parameter, MessageManipulations or CLI command, configure voip >...
  • Page 235 User's Manual 20. SIP Definitions Message Manipulations Parameters Parameter Description Index Defines the table row index for the rule. [MessageManipulation The valid value is 0 to 99. The default is 0. s_Index] Note: Each rule must be configured with a unique index. Manipulation Set ID Defines a Manipulation Set ID for the rule.

  • Page 236: Configuring Sip Message Policy Rules

    Mediant 800 MSBR Parameter Description  [6] Remove Prefix = removes value from the beginning of the string (string element only). Action Value Defines a value (string) that you want to use in the manipulation. CLI: action-value The syntax is as follows: [MessageManipulation ...
  • Page 237 User's Manual 20. SIP Definitions Note: The Message Policy table can also be configured using the table ini file parameter, MessagePolicy or the CLI command, configure voip > sbc message-policy.  To configure SIP message policy rules: Open the Message Policy Table page (Configuration tab > VoIP menu > SIP Definitions >...
  • Page 238 Mediant 800 MSBR Parameter Description Max Body Length Defines the maximum SIP message body length. This is the value of the CLI: max-body-length Content-Length header. [MessagePolicy_MaxB The valid value is up to 1,024 characters. The default is 1,024. odyLength] Max Num Headers Defines the maximum number of SIP headers.

  • Page 239: Coders And Profiles

    User's Manual 21. Coders and Profiles Coders and Profiles This section describes configuration of the coders and SIP profiles parameters. 21.1 Configuring Coders The Coders page allows you to configure up to 10 voice coders for the device. Each coder can be configured with packetization time (ptime), bit rate, payload type, and silence suppression.
  • Page 240 Mediant 800 MSBR  To configure the device's coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles submenu > Coders). Figure 21-1: Coders Table Page From the 'Coder Name' drop-down list, select the required coder. From the 'Packetization Time' drop-down list, select the packetization time (in msec) for the selected coder.
  • Page 241 User's Manual 21. Coders and Profiles Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression   [0] 5.3 [0] Disable G.723.1 30 (default), 60, 90, 120, (default) [g7231]  [1] Enable  [1] 6.3   [0] 16 [0] Disable G.726 10, 20 (default), 30, 40, 50,...

  • Page 242: Configuring Coder Groups

    Mediant 800 MSBR 21.2 Configuring Coder Groups The Coder Group Settings page allows you to define up to 10 groups of coders (termed Coder Groups). For each Coder Group, you can define up to 10 coders configured with packetization time (ptime), rate, payload type, and silence suppression. The first coder in the Coder Group table has the highest priority and is used by the device whenever possible.

  • Page 243: Configuring Tel Profile

    User's Manual 21. Coders and Profiles From the 'Silence Suppression' drop-down list, enable or disable the silence suppression option for the coder you selected. Repeat steps 3 through 7 for the next coders (optional). Repeat steps 2 through 8 for the next coder group (optional). Click Submit to apply your changes.
  • Page 244 Mediant 800 MSBR  To configure Tel Profiles: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > Tel Profile Settings). From the 'Profile ID' drop-down list, select the Tel Profile index. In the 'Profile Name' field, enter an arbitrary name that enables you to easily identify the Tel Profile.

  • Page 245: Configuring Ip Profiles

    User's Manual 21. Coders and Profiles preference. Configure the parameters as required. For a description of each parameter, refer to the corresponding "global" parameter. Click Submit to apply your changes. 21.4 Configuring IP Profiles The IP Profile Settings table allows you to define up to nine IP Profiles. An IP Profile is a set of special call configuration behaviors relating to signaling (e.g., SIP message terminations such as REFER) and media (e.g., coder used) applied to specific IP calls (inbound and/or outbound).
  • Page 246 Mediant 800 MSBR  To configure IP Profiles: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > IP Profile Settings). From the 'Profile ID' drop-down list, select the IP Profile index. In the 'Profile Name' field, enter an arbitrary name that allows you to easily identify the IP Profile.
  • Page 247 User's Manual 21. Coders and Profiles Table 21-1: IP Profile Parameters Description Parameter Description Web: Profile ID Defines a unique index number for the IP Profile. [IpProfile_Index] Web: Profile Name (Optional) Defines a descriptive name for the IP Profile. [IpProfile_ProfileName] Common Parameters Web: RTP IP DiffServ For a description, see the global parameter...
  • Page 248 Mediant 800 MSBR Parameter Description Web: Enable Early Media For a description, see the global parameter EnableEarlyMedia. [IpProfile_EnableEarlyMedia] Web: Copy Destination Number to For a description, see the global parameter Redirect Number CopyDest2RedirectNumber. [IpProfile_CopyDest2RedirectN umber] Web: Media Security Behavior For a description, see the global parameter [IpProfile_MediaSecurityBehavi MediaSecurityBehaviour.
  • Page 249 User's Manual 21. Coders and Profiles Parameter Description Web: Second Tx DTMF Option For a description, see the global parameter TxDTMFOption. [IpProfile_SecondTxDtmfOption Web: Declare RFC 2833 in SDP For a description, see the global parameter RxDTMFOption. [IpProfile_RxDTMFOption] Web: Add IE In SETUP For a description, see the global parameter AddIEinSetup.
  • Page 250 Mediant 800 MSBR Parameter Description of the coders in the incoming SDP offer according to their order of appearance in the Allowed Coders Group list. This option also retains all the coders received in the SDP offer.  [2] Restriction and Preference = Performs both Restriction and Preference.
  • Page 251 User's Manual 21. Coders and Profiles Parameter Description Web: Media Security Behavior Determines the transcoding method between SRTP and RTP [IpProfile_SBCMediaSecurityBe and enforce an SBC leg to use SRTP or RTP. haviour]  [0] As is = (Default) No special handling for RTP\SRTP is done.
  • Page 252 Mediant 800 MSBR Parameter Description Web: SBC Fax Behavior Defines the negotiation method for fax offer. [IpProfile_SBCFaxBehavior]  [0] = (Default) Pass fax transparently, without interference.  [1] = Handle fax according to fax settings in the IP Profile for all offer-answer transactions (including the initial INVITE).
  • Page 253 User's Manual 21. Coders and Profiles Parameter Description Web: SBC Remote Early Media Defines whether the destination UA sends RTP immediately after it sends 18x response. [IpProfile_SBCRemoteEarlyMed  [0] Immediate = (Default) Remote client sends RTP iaRTP] immediately after it sends 18x response with early media. Device forwards 18x and RTP as is.
  • Page 254 Mediant 800 MSBR Parameter Description Web: SBC Remote Re-Invite Determines whether the destination UA of the re-INVITE Support request supports re-INVITE messages and if so, whether it [IpProfile_SBCRemoteReinviteS supports re-INVITE with or without SDP. upport]  [0] Not Supported = re-INVITE is not supported and the device does not forward re-INVITE requests.
  • Page 255 User's Manual 21. Coders and Profiles Parameter Description Web: SBC RFC2833 DTMF Defines the RFC 2833 DTMF Payload Type for a specific SBC Payload Type Value leg. This enables the interworking of the DTMF payload type for [IpProfile_SBC2833DTMFPayloa RFC 2833 between different SBC call legs. For example, if two dType] entities require different DTMF payload types, the SDP offer received by the device from one entity is forwarded to the...
  • Page 256 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

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

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

  • Page 259: Ip-To-Ip Routing Overview

    User's Manual 22. IP-to-IP Routing Overview IP-to-IP Routing Overview This section describes configuration of the Gateway and IP-to-IP applications. The Gateway application refers to IP-to-Tel (PSTN) call routing and vice versa. The IP-to-IP application refers to call routing of calls received from the IP and forwarded to an IP destination.

  • Page 260: Theory Of Operation

    Mediant 800 MSBR The IP-to-IP call routing capability is feature-rich, allowing interoperability with different ITSPs:  Easy and smooth integration with multiple ITSP SIP trunks.  Supports SIP registration and authentication with ITSP servers (on behalf of the enterprise's IP telephony system) even if the enterprise's IP telephony system does no support registration and authentication.

  • Page 261: Proxy Sets

    User's Manual 22. IP-to-IP Routing Overview The figure below provides a simplified illustration of the device's handling of IP-to-IP call routing: Figure 22-1: Basic Schema of the Device's IP-to-IP Call Handling The basic IP-to-IP call handling process can be summarized as follows: Incoming IP calls are identified as belonging to a specific logical entity in the network referred to as a Source IP Group, according to Inbound IP Routing rules.
  • Page 262 Mediant 800 MSBR 401/407 responses, if needed, is done by the Serving IP Group (e.g., IP-PBX). The device forwards these responses directly to the remote SIP users. For a call to a registered remote user, the device searches its dynamic database using the Request URI for an entry that matches a registered AOR or Contact.

  • Page 263: Inbound And Outbound Ip Routing Rules

    User's Manual 22. IP-to-IP Routing Overview 22.1.3 Inbound and Outbound IP Routing Rules The device's IP-to-IP call routing is performed using the following two routing rule stages: Inbound IP Routing Mapping Rule: Identifies the received call as an IP-to-IP call based on various characteristics such as the call's source IP address, and assigns it to an IP Group.
  • Page 264 Mediant 800 MSBR between the IP-PBX, and two ITSP's and the local PSTN.  The enterprise has an IP-PBX located behind a Firewall/NAT: • IP-PBX IP address: 10.15.4.211 • Transport protocol: UDP • Voice coder: G.711 • IP-PBX users: 4-digit length extension number and served by two ITSPs. •...
  • Page 265 User's Manual 22. IP-to-IP Routing Overview Figure 22-5: SIP Trunking Setup Scenario Example The steps for configuring the device according to the scenario above can be summarized as follows:  Enable the IP-to-IP feature (see 'Step 1: Enable the IP-to-IP Capabilities' on page 266).

  • Page 266: Step 1: Enable The Ip-To-Ip Capabilities

    Mediant 800 MSBR 22.2.1 Step 1: Enable the IP-to-IP Capabilities This step describes how to enable the device's IP-to-IP application.  To enable IP-to-IP capabilities: Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling submenu > Applications Enabling). From the 'IP to IP Application' drop-down list, select Enable.

  • Page 267: Step 4: Configure The Proxy Sets

    User's Manual 22. IP-to-IP Routing Overview • In the 'Phone Number' field, enter any phone number (logical) for this Trunk (e.g. 1000). • In the 'Trunk Group ID' field, enter "1" as the ID for this Trunk Group. Configure the Trunk in the Trunk Settings page (Configuration tab > VoIP menu > PSTN >...
  • Page 268 Mediant 800 MSBR Figure 22-7: Proxy Set ID #1 for ITSP-A Configure Proxy Set ID #2 for ITSP-B: From the 'Proxy Set ID' drop-down list, select 2. In the 'Proxy Address' column, enter the IP addresses of the ITSP-B SIP trunk (e.g., "216.182.224.202"...

  • Page 269: Step 5: Configure The Ip Groups

    User's Manual 22. IP-to-IP Routing Overview In the 'Enable Proxy Keep Alive' drop-down list, select Using Options. This is used in Survivability mode for remote IP-PBX users. Figure 22-9: Proxy Set ID #3 for the IP-PBX 22.2.5 Step 5: Configure the IP Groups This step describes how to create the IP Groups for the following entities in the network: ...

  • Page 270: Step 6: Configure The Account Table

    Mediant 800 MSBR Contact User = name that is sent in the SIP Request Contact header for this IP Group (e.g., ITSP-B). Define IP Group #3 for the IP-PBX: From the 'Type' drop-down list, select Server. In the 'Description' field, type an arbitrary name for the IP Group (e.g., IP-PBX). From the 'Proxy Set ID' drop-down lists, select 3 (represents the IP address, configured in , for communicating with this IP Group).

  • Page 271: Step 7: Configure Ip Profiles For Voice Coders

    User's Manual 22. IP-to-IP Routing Overview • In the 'Username', enter the SIP username for authentication supplied by ITSP-A (e.g., itsp_a). • In the 'Password' field, enter the SIP password for authentication supplied by ITSP-A (e.g., 12345). • In the 'Register' field, enter "1" to enable registration with ITSP-A. Configure Account ID #2 for IP-PBX registration) with ITSP-B Registrar server: •...

  • Page 272: Step 8: Configure Inbound Ip Routing

    Mediant 800 MSBR Figure 22-12: Defining Coder Group ID 2 Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Configure Profile ID #1 for the IP-PBX (as shown below): From the 'Profile ID' drop-down list, select 1. From the 'Coder Group' drop-down list, select Coder Group 1.
  • Page 273 User's Manual 22. IP-to-IP Routing Overview  To configure inbound IP routing: Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP submenu > Routing submenu > IP to Trunk Group Routing). Figure 22-14: Defining Inbound IP Routing Rules Index #1: routes calls with prefix 9 (i.e., local calls) dialed from IP-PBX users to the local PSTN:...

  • Page 274: Step 9: Configure Outbound Ip Routing

    Mediant 800 MSBR Index #5: identifies all IP calls received from IP-PBX remote users: • 'Source Host Prefix': enter "PBXuser". This is the host name that appears in the From header of the Request URI received from remote IP-PBX users. •...

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

    User's Manual 22. IP-to-IP Routing Overview Configure Index #4 to route IP calls received from the IP-PBX to ITSP-A: • 'Source IP Group ID': select 3 to indicate received (inbound) calls identified as belonging to the IP Group configured for the IP-PBX. •...
  • Page 276 Mediant 800 MSBR Configure Index #2 to manipulate destination number of IP calls received from ITSP-B. The phone number of calls received with prefix 0200 (i.e., from ITSP-B) are removed except for the last four digits: • 'Destination Prefix': enter the prefix "0200". •...

  • Page 277: Digital Pstn

    User's Manual 23. Digital PSTN Digital PSTN This section describes the configuration of the public switched telephone network (PSTN) related parameters. 23.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. This page also provides the following features: ...
  • Page 278 Mediant 800 MSBR  To configure the trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN submenu > 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 279 User's Manual 23. 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 280: Tdm And Timing

    Mediant 800 MSBR 23.2 TDM and Timing This section describes the configuration of the TDM and clock timing parameters. 23.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 894. ...

  • Page 281: Recovering Clock From Pstn Line Interface

    User's Manual 23. Digital PSTN 23.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 (Trunk) interface. For a full description of the clock parameters, see 'PSTN Parameters' on page 894. ...

  • Page 282: Configuring Cas State Machines

    Mediant 800 MSBR 23.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 283 User's Manual 23. Digital PSTN • The modification of the CAS state machine occurs at the CAS application initialization only for non-default values (-1). • For more information on the CAS Protocol table, refer to the CAS Protocol Table Configuration Note. CAS State Machine Parameters Description Parameter Description...

  • Page 284: Configuring Digital Gateway Parameters

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

  • Page 285: Tunneling Applications

    User's Manual 23. Digital PSTN 23.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 23.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 routing (without Proxy control) capabilities to receive voice and data streams from TDM (E1/T1/J1/) spans or individual timeslots, convert them into packets, and then transmit them over the IP network (using point-to-point or point-to-multipoint device distributions).
  • Page 286 Mediant 800 MSBR For tunneling of E1/T1 CAS trunks, set the protocol type to 'Raw CAS' (ProtocolType = 3 / 9) and enable RFC 2833 CAS relay mode ('CAS Transport Type' parameter is set to 'CAS RFC2833 Relay'). Note: For TDM over IP, the parameter CallerIDTransportType must be set to '0' (disabled), i.e., transparent.
  • Page 287 User's Manual 23. Digital PSTN TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile 1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$; TelProfile 2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$; [\TelProfile] Originating Side: ;E1_TRANSPARENT_31 ProtocolType_0 = 5 ProtocolType_1 = 5 ProtocolType_2 = 5 ProtocolType_3 = 5 ;Channel selection by Phone number.

  • Page 288: Dsp Pattern Detector

    Mediant 800 MSBR TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 23.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 289: Isdn Non-Facility Associated Signaling (Nfas)

    User's Manual 23. Digital PSTN sent) to IP. The 200 OK response includes an encapsulated QSIG Call Proceeding message (without waiting for a Call Proceeding message from the Tel side). If tunneling is disabled and the incoming INVITE includes a QSIG body, a 415 response is sent.

  • Page 290: Nfas Interface Id

    Mediant 800 MSBR trunk. ‘x’ denotes the physical trunk ID (0 to the maximum number of trunks). You can also use the Web interface (see 'Configuring Trunk Settings' on page 277). For example, to assign the first four T1 trunks to NFAS group #1, in which trunk #0 is the primary trunk and trunk #1 is the backup trunk, use the following configuration: NFASGroupNumber_0 = 1 NFASGroupNumber_1 = 1...

  • Page 291: Creating An Nfas-Related Trunk Configuration

    User's Manual 23. Digital PSTN For example, if four T1 trunks on a device are configured as a single NFAS group with Primary and Backup T1 trunks that is used with a DMS-100 switch, the following parameters should be used: NFASGroupNumber_0 = 1 NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1...

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

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

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

    User's Manual 23. Digital PSTN The device stops collecting digits (from the ISDN) upon the following scenarios:  The device receives a Sending Complete IE in the ISDN Setup or Information messages, indicating no more digits.  The timeout between received digits expires (configured by the TimeBetweenDigits parameter).

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

    Mediant 800 MSBR 23.8 Redirect Number and Calling Name (Display) The following tables define the device's redirect number and calling name (Display) support for various ISDN variants according to NT (Network Termination) / TE (Termination Equipment) interface direction: Calling Name (Display) NT/TE Interface DMS-100 NI-2...

  • Page 295: Trunk Group

    User's Manual 24. Trunk Group Trunk Group This section describes the configuration of the device's channels, which entails assigning them numbers and Trunk Group IDs. 24.1 Configuring Trunk Group Table The Trunk Group Table page allows you to define up to 120 Trunk Groups. A Trunk Group is a logical group of physical trunks and channels that are assigned a Trunk Group ID.
  • Page 296 Mediant 800 MSBR Trunk Group Table Parameters Parameter Description Module Defines the module (i.e., FXS, FXO, PRI, or BRI) for which you want CLI: module to define the Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group. The CLI: first-trunk-id number of listed Trunks depends on the device's hardware [TrunkGroup_FirstTrunkI...

  • Page 297: Configuring Hunt Group Settings

    User's Manual 24. Trunk Group 24.2 Configuring Hunt Group Settings The Hunt Group Settings allows you to configure the following per Trunk Group:  Channel select method by which IP-to-Tel calls are assigned to the Trunk Group's channels.  Registration method for registering Trunk Groups to selected Serving IP Group IDs. Notes: •...
  • Page 298 Mediant 800 MSBR Parameter Description Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the CLI: channel-select-mode channels of the Trunk Group. [TrunkGroupSettings_Ch  [0] By Dest Phone Number = The channel is selected according annelSelectMode] to the called (destination) number.
  • Page 299 User's Manual 24. Trunk Group Parameter Description applicable only to FXS interfaces.  [10] Select Trunk by ISDN SuppServ Table = The BRI port/module is selected according to the settings in the ISDN Supplementary Services table (see Configuring ISDN BRI Supplementary Services on page 392), allowing the routing of IP- to-Tel calls to specific BRI endpoints.
  • Page 300 Mediant 800 MSBR Parameter Description The "SipGroupName" in the Request-URI is configured in the IP Group table (see 'Configuring IP Groups' on page 210). Notes:  If this parameter is not configured, the registration is performed according to the global registration parameter, ChannelSelectMode.
  • Page 301 User's Manual 24. Trunk Group Parameter Description Trunk Group Name Defines a name for the Trunk Group. This name represents the CLI: trunk-group-name Trunk Group in the SIP 'tgrp' parameter of the outgoing INVITE [TrunkGroupSettings_Tr messages (according to RFC 4904). For example: unkGroupName] sip:+16305550100;tgrp=TG-1;trunk-context=+1- 630@isp.example.net;user=phone...
  • Page 302 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 303: Manipulation

    User's Manual 25. Manipulation Manipulation This section describes the configuration of various manipulation processes. 25.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 755.
  • Page 304 Mediant 800 MSBR and so on until 559. However, if you enter 55 in Index 1 and 551 in Index 2, the device applies rule 1 to all numbers that start with 55, including numbers that start with 551. You can perform a second "round" (additional) of destination (NumberMapIP2Tel parameter) and source (SourceNumberMapIP2Tel parameter) number manipulations for IP-to-Tel calls on an already manipulated number.
  • Page 305 User's Manual 25. Manipulation  To configure number manipulation rules: Open the required Number Manipulation page (Configuration tab > VoIP menu > GW and IP to IP submenu > Manipulations submenu > 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 306 Mediant 800 MSBR Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Number Manipulation Parameters Description...
  • Page 307 User's Manual 25. Manipulation Parameter Description message, then the value of this parameter is compared to the P- Asserted-Identity URI host name (instead of the From header). Web: Destination Host Defines the Request-URI host name prefix of the incoming SIP Prefix INVITE message.
  • Page 308 Mediant 800 MSBR Parameter Description [Prefix2Add] Web: Suffix to Add Defines the number or string that you want added to the end of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone CLI: suffix-to-add number is 1234, the new number is 123400.

  • Page 309: Manipulating Number Prefix

    User's Manual 25. Manipulation Parameter Description the From header in the INVITE message includes the following: From: 'anonymous' <sip: anonymous@anonymous.invalid> and 'privacy: id' header. 25.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.

  • Page 310: Sip Calling Name Manipulations

    Mediant 800 MSBR In this configuration example, the following manipulation process occurs: The prefix is calculated as 020215. The first seven digits from the left are removed from the original number, thereby changing the number to 8888888. The prefix that was previously calculated is then added. 25.4 SIP Calling Name Manipulations The Calling Name Manipulations Tel2IP and Calling Name Manipulations IP2Tel tables...
  • Page 311 User's Manual 25. Manipulation  To configure calling name manipulation rules: Open the required Calling Name Manipulations page (Configuration tab > VoIP menu > GW and IP to IP submenu > Manipulations > Calling Name IP->Tel or Calling Name Tel->IP). Click the Add button;...
  • Page 312 Mediant 800 MSBR Parameter Description Web: Source Trunk Group Defines the source Trunk Group ID for Tel-to-IP calls. To denote all Trunk Groups, leave this field empty. CLI: src-trunk-group-id Notes:  This parameter is applicable only to the Calling Name Manipulations Tel2IP table.

  • Page 313: Configuring Redirect Number Ip To Tel

    User's Manual 25. Manipulation Parameter Description Web/EMS: Number of Defines the number of characters that you want to keep from the right Digits to Leave of the calling name. For example, if you enter 4 and the calling name CLI: num-of-digits-to-leave is "company:name", the new name is "name".
  • Page 314 Mediant 800 MSBR  To configure redirect number manipulation rules: Open the required redirect number manipulation table (Configuration tab > VoIP menu > GW and IP to IP submenu > Manipulations > Redirect Number Tel > IP or Redirect Number IP > Tel). Click the Add button;...
  • Page 315 User's Manual 25. Manipulation Parameter Description  This parameter is applicable only to the Redirect Number Tel > IP table.  This parameter is applicable only to the IP-to-IP application.  The value -1 indicates that it is ignored in the rule. Web/EMS: Source IP Defines the IP address of the caller.

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

    Mediant 800 MSBR Parameter Description CLI: suffix-to-add redirect number. For example, if you enter 00 and the redirect number [Suffix2Add] is 1234, the new number is 123400. Web: Presentation Enables caller ID. EMS: Is Presentation  Not Configured = Privacy is determined according to the Caller ID Restricted table (see Configuring Caller Display Information on page 404).

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

    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.20A.043.001 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 25.7 Mapping NPI/TON to SIP Phone-Context The Phone-Context table page allows you to map Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter. The 'phone-context' parameter appears in the standard SIP headers where a phone number is used (i.e.,...
  • Page 318 Mediant 800 MSBR For example, for a Tel-to-IP call with NPI/TON set as E164 National (values 1/2), the device sends the following SIP INVITE URI: sip:12365432;phone-context= na.e.164.nt.com This is configured for entry 3 in the figure below. In the opposite direction (IP-to-Tel call), if the incoming INVITE contains this 'phone-context' (e.g.

  • Page 319: Configuring Release Cause Mapping

    User's Manual 25. Manipulation Parameter Description  [PhoneContext_Npi] [0] Unknown (default)  [1] E.164 Public  [9] Private For a detailed list of the available NPI/TON values, see Numbering Plans and Type of Number on page 325. Defines the Type of Number (TON). CLI: ton ...

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

    Mediant 800 MSBR  To configure Release Cause mapping: Open the Release Cause Mapping page (Configuration tab > VoIP menu > GW and IP to IP submenu > Manipulations > Release Cause Mapping). Figure 25-6: Release Cause Mapping Page In the 'Release Cause Mapping from ISDN to SIP' group, map different Q.850 Release Causes to SIP Responses.
  • Page 321 User's Manual 25. Manipulation ISDN Release Description Description Response Reason required Request timeout Recovery on timer expiry Conflict Temporary failure Gone Number changed w/o diagnostic Length required Interworking Request entity too long Interworking Request URI too long Interworking Unsupported media type Service/option not implemented Bad extension Interworking...

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

    Mediant 800 MSBR 25.8.2 Fixed Mapping of ISDN Release Reason to SIP Response The following table describes the mapping of ISDN release reason to SIP response. Mapping of ISDN Release Reason to SIP Response ISDN Release Description Description Reason Response Unallocated number Not found No route to network...
  • Page 323 User's Manual 25. Manipulation ISDN Release Description Description Reason Response Bearer capability not implemented Not implemented Channel type not implemented 480* Temporarily unavailable Requested facility not implemented 503* Service unavailable Only restricted digital information bearer 503* Service unavailable capability is available Service or option not implemented Not implemented Invalid call reference value...

  • Page 324: Reason Header

    Mediant 800 MSBR 25.8.3 Reason Header The device supports the SIP Reason header according to RFC 3326. The Reason header conveys information describing the disconnection cause of a call:  Sending Reason header: If a call is disconnected from the Tel side (ISDN), the Reason header is set to the received Q.850 cause in the appropriate message (BYE/CANCEL/final failure response) and sent to the SIP side.

  • Page 325: Numbering Plans And Type Of Number

    User's Manual 25. Manipulation 25.9 Numbering Plans and Type of Number The IP-to-Tel destination or source number manipulation tables allow you to classify numbers by their Numbering Plan Indication (NPI) and Type of Number (TON). The device supports all NPI/TON classifications used in the ETSI ISDN variant, as shown in the table below: NPI/TON Values for ETSI ISDN Variant Description...
  • Page 326 Mediant 800 MSBR For NI-2 and DMS-100 ISDN variants, the valid combinations of TON and NPI for calling and called numbers include (Plan/Type):  0/0 - Unknown/Unknown  1/1 - International number in ISDN/Telephony numbering plan  1/2 - National number in ISDN/Telephony numbering plan ...

  • Page 327: Routing

    User's Manual 26. Routing Routing This section describes the configuration of call routing rules. 26.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 755.
  • Page 328 Mediant 800 MSBR  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. The destination can be any of the following: •...
  • Page 329 User's Manual 26. Routing Notes: 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 330 Mediant 800 MSBR Notes: • Outbound IP routing can be performed before or after number manipulation. This is configured using the RouteModeTel2IP parameter, as described below. • The Outbound IP Routing Table can also be configured using the table ini file parameter, Prefix or CLI command, configure voip > gw routing tel2ip-routing.
  • Page 331 User's Manual 26. Routing Example of Tel-to-IP Source Phone Number Manipulation Rules Parameter Rule Rule 2 Rule 3 Rule 4 Rule 5 Rule 6 Rule 7 Rule 8 Rule 9 Src. IP Group ID Src. Trunk Group ID Src. Host domain.c Prefix Src.
  • Page 332 Mediant 800 MSBR Parameter Description Web: Src. IP Group Defines the IP Group from where the incoming IP call is received. Typically, the IP Group of an incoming INVITE is determined according to the Inbound EMS: Source IP IP Routing Table. Group ID Notes: CLI: src-ip-group-id...
  • Page 333 User's Manual 26. Routing Parameter Description the destination phone prefix. For more information regarding this feature, see the FaxReroutingMode parameter. Web/EMS: Source Defines the prefix and/or suffix of the calling (source) telephone number. Phone Prefix You can use special notations for denoting the prefix. For example, [100- CLI: src-phone-prefix 199](100,101,105) denotes a number that starts with 100 to 199 and ends [PREFIX_SourcePr...
  • Page 334 Mediant 800 MSBR Parameter Description  [2] TLS Note: When set to Not Configured (-1), the transport type defined by the SIPTransportType parameter is used. Web: Dest IP Group Defines the IP Group to where you want to route the call. The SIP INVITE message is sent to the IP address defined for the Proxy Set ID associated EMS: Destination IP with the IP Group.
  • Page 335 User's Manual 26. Routing Parameter Description Forking Group Defines a forking group ID for the routing rule. This enables forking of CLI: forking-group incoming Tel calls to two or more IP destinations. The device sends [PREFIX_ForkingGr simultaneous INVITE messages and handles multiple SIP dialogs until one oup] of the calls is answered.

  • Page 336: Configuring Inbound Ip Routing Table

    Mediant 800 MSBR 26.3 Configuring Inbound IP Routing Table The Inbound IP Routing Table page allows you to configure up to 24 inbound call routing rules:  For IP-to-IP routing: The table is used to identify an incoming call as an IP-to-IP call and subsequently, to assign the call to an IP Group, referred to as a source IP Group.
  • Page 337 User's Manual 26. Routing  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 submenu > Routing > IP to Trunk Group Routing). Figure 26-3: Inbound IP Routing Table The previous figure displays the following configured routing rules: •...
  • Page 338 Mediant 800 MSBR Parameter Description Web: Source Host Prefix Defines the From URI host name prefix of the incoming SIP INVITE CLI: src-host-prefix message. If this routing rule is not required, leave the field empty. [SrcHostPrefix] Notes:  The asterisk (*) wildcard can be used to depict any prefix. ...
  • Page 339 User's Manual 26. Routing Parameter Description Operation (Destination) Web: Trunk Group ID For IP-to-Tel calls: Defines the Trunk Group to where the incoming SIP CLI: trunk-group-id call is sent. [TrunkGroupId] For IP-to-IP calls: Identifies the call as an IP-to-IP call if this parameter is set to -1.

  • Page 340: Ip Destinations Connectivity Feature

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

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

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

  • Page 342: Alternative Routing Based On Sip Responses

    Mediant 800 MSBR Notes: • Alternative routing based on IP connectivity is applicable only when a proxy server is not used. • As the device searches the Outbound IP Routing table for a matching rule starting from the top, you must configure the main routing rule above the alternative routing rules.
  • Page 343 User's Manual 26. Routing Depending on configuration, the alternative routing is done using one of the following configuration entities:  Outbound IP Routing Rules: You can configure up to two alternative routing rules in the table. If the initial, main routing rule destination is unavailable, the device searches the table (starting from the top) for the next call matching rule (e.g., destination phone number), and if available attempts to re-route the call to the IP destination configured for this alternative routing rule.

  • Page 344: Pstn Fallback

    Mediant 800 MSBR 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: Enable alternative routing based on SIP responses, by setting the 'Redundant Routing Mode' parameter to one of the following: •...

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

    User's Manual 26. Routing 26.6 Alternative Routing for IP-to-Tel Calls The device supports alternative IP-to-Tel call routing, as described in this section. 26.6.1 Alternative Routing to Trunk upon Q.931 Call Release Cause Code You can configure the device to do alternative IP-to-Tel call routing based on the received ISDN Q.931 cause code.

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

    Mediant 800 MSBR Notes: • You can configure up to two alternative routing rules in the Inbound IP Routing table. • If a Trunk is disconnected or not synchronized, the device issues itself the internal Cause Code No. 27. This cause code is mapped (by default) to SIP 502.
  • Page 347 User's Manual 26. Routing  To configure Forward on Busy Trunk Destination rules: Open the Forward on Busy Trunk Destination page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Forward on Busy Trunk). Figure 26-8: Forward on Busy Trunk Destination Page The figure above displays a configuration that forwards IP-to-Tel calls destined for Trunk Group ID 1 to destination IP address 10.13.5.67 if the conditions mentioned earlier exist.
  • Page 348 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 349: Configuring Dtmf And Dialing

    User's Manual 27. 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 755. ...

  • Page 350: Dialing Plan Features

    Mediant 800 MSBR 27.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 27.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 292.

  • Page 351: External Dial Plan File

    User's Manual 27. Configuring DTMF and Dialing Notes: • If you want the device to accept/dial any number, ensure that the digit map contains the rule "xx.T"; otherwise, dialed numbers not defined in the digit map are rejected. • If you are using an external Dial Plan file for dialing plans (see 'Dialing Plans for Digit Collection' on page 634), the device first attempts to locate a matching digit pattern in the Dial Plan file, and if not found, then attempts to locate a matching digit pattern in the Digit Map (configured by...
  • Page 352 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 353: Configuring Supplementary Services

    User's Manual 28. 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) in client server mode (the application server controls all supplementary services and keypad features by itself), the device's supplementary services must be disabled.
  • Page 354 Mediant 800 MSBR Figure 28-1: Supplementary Services Page Configure the parameters as required. Click Submit to apply your changes, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server.

  • Page 355: Call Hold And Retrieve

    User's Manual 28. Configuring Supplementary Services 28.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 356 Mediant 800 MSBR Figure 28-2: Double Hold SIP Call Flow User's Manual Document #: LTRT-12809...

  • Page 357: Call Pickup

    User's Manual 28. Configuring Supplementary Services The flowchart above describes the following "double" call-hold scenario: A calls B and establishes a voice path. A places B on hold; A hears a dial tone and B hears a held tone. A calls C and establishes a voice path. B places A on hold;...

  • Page 358: Consultation Feature

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

  • Page 359: Consultation Transfer For Qsig Path Replacement

    User's Manual 28. Configuring Supplementary Services Note: For FXS interfaces, the device can also handle call transfers using SIP INVITE and re-INVITE messages, instead of REFER messages. This is useful when communicating with SIP UAs that do not support the receipt of REFER messages.

  • Page 360: Call Forward

    Mediant 800 MSBR The device sends a Q.931 Setup message to "C". This feature enables manipulating the called party number in this outgoing Setup message. The manipulation is done as follows: If you configure a value for the xferPrefix parameter, then this value (string) is added as a prefix to the number in the Refer-To header.

  • Page 361: Call Forward Reminder Ring

    User's Manual 28. Configuring Supplementary Services The served party (FXS interface) can be configured through the Web interface (see Configuring Call Forward on page 405) or ini file to activate one of the call forward modes. These modes are configurable per endpoint. Notes: •...

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

    Mediant 800 MSBR e.g., a softswitch is used to forward calls intended for the endpoint, to another destination. This is useful in that it reminds the FXS user of this service. This feature does not involve device subscription (SIP SUBSCRIBE) to the AS. Activation/deactivation of the service is notified by the server.

  • Page 363: Bri Call Forwarding

    User's Manual 28. Configuring Supplementary Services 28.6.4 BRI Call Forwarding The device supports call forwarding (CF) services initiated by ISDN Basic BRI phones connected to it. Upon receipt of an ISDN Facility message for call forward from the BRI phone, the device sends a SIP INVITE to the softswitch with a user-defined code in the SIP To header, representing the reason for the call forward.

  • Page 364: Message Waiting Indication

    For more information on IP voice mail configuration, refer to the IP Voice Mail CPE Configuration Guide. • For creating a CPT file using AudioCodes CPTWizard utility, refer to CPTWizard Utility User's Guide. To configure MWI, use the following parameters: ...
  • Page 365 User's Manual 28. Configuring Supplementary Services  VoiceMailInterface  EnableVMURI The device supports the following MWI features for its digital PSTN interfaces:  For BRI interfaces: This feature provides support for MWI on BRI phones connected to the device and using the Euro ISDN BRI variant. When this feature is activated and a voice mail message is recorded to the mail box of a BRI extension, the softswitch sends a notification to the device.

  • Page 366: Caller Id

    Mediant 800 MSBR 28.9 Caller ID This section describes the device's Caller ID support. Note: The Caller ID feature is applicable only to FXS/FXO interfaces. 28.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 367: 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 368: Three-Way Conferencing

    The device supports the following conference modes (configured by the parameter 3WayConferenceMode):  Conferencing managed by an external, AudioCodes Conference (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 369: Emergency E911 Phone Number Services

    User's Manual 28. 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 370: Fxs Device Emulating Psap Using Did Loop-Start Lines

    Mediant 800 MSBR 28.11.1 FXS Device Emulating PSAP using DID Loop-Start Lines The device's FXS interface can be configured to emulate PSAP (using DID loop start lines), according to the Telcordia GR-350-CORE specification. Figure 28-4: FXS Device Emulating PSAP using DID Loop-Start Lines The call flow of an E911 call to the PSAP is as follows: The E911 tandem switch seizes the line.
  • Page 371 User's Manual 28. Configuring Supplementary Services The following parameters need to be configured:  EnableDIDWink = 1  EnableReversalPolarity = 1  PolarityReversalType = 1  FlashHookPeriod = 500 (for 500 msec "hookflash" mid-call Wink)  WinkTime = 250 (for 250 msec signalling Wink generated by the FXS device after it detects the line seizure) ...

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

    Mediant 800 MSBR For example, if ANI and PANI are received, the SIP INVITE contains the following From header: From: <sip:*nnnnnnnnnnnn#*mmmmmmmmmm#@10.2.3.4>;tag=1c14 Note: It is possible to remove the * and # characters, using the device's number manipulation rules. If the device receives the SIP INFO message below, it then generates a "hookflash" mid- call Wink signal: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via:...
  • Page 373 User's Manual 28. Configuring Supplementary Services When an IP phone subscriber dials 911, the device receives the SIP INVITE message and makes a call to the PSAP as follows: The FXO device seizes the line. PSAP sends a Wink signal (250 msec) to the device. Upon receipt of the Wink signal, the device dials MF digits after a user-defined time (WaitForDialTime) containing the caller's ID (ANI) obtained from the SIP headers From or P-Asserted-Identity.
  • Page 374 Mediant 800 MSBR Dialed Number by Device Depending on Calling Number Digits of Calling Digits of Displayed Number Number Dialed MF Digits Number (ANI) MF dialed "KPnnnnnnnnST" "nnnnnnnn" None "KPnnnnnnnnnnnnSTP" "nnnnnnnnnnnn" "KPnnnnnnnnnnnnSTKPmmmmmmmmmmS "nnnnnnnnnnnn" "mmmmmmmmmm" (pANI) T" None "KPnnSTP" "nn" MF dialed "KPnST" "n"...

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

    From: "0123456789" <sip:333333444444@audiocodes.com>;tag=1c771623824 To: <sip:301@10.33.37.79;user=phone> Call-ID: 77162335841200014153@10.33.37.78 CSeq: 1 INVITE Contact: <sip:101@10.33.37.78> Supported: em,100rel,timer,replaces,path Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO ,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-FXO/v.6.00A.020.077 Privacy: none P-Asserted-Identity: "0123456789" <sip:3333344444@audiocodes.com> Content-Type: application/sdp Content-Length: 253 o=AudiocodesGW 771609035 771608915 IN IP4 10.33.37.78 s=Phone-Call c=IN IP4 10.33.37.78 t=0 0...

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

    User's Manual 28. Configuring Supplementary Services Figure 28-6: Call Flow of E9-1-1 to PSTN-Based Emergency Services Provider The VoIP user dials 9-1-1. The call is eventually sent to the PSTN through a PSTN Gateway. 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.
  • Page 378 Mediant 800 MSBR when the operating system detects a network connection change, each Lync 2010 client submits a request to the LIS for a location. If the LIS is able to resolve a location address for the client request, it returns the address in a location response. Each client then caches this information.
  • Page 379 User's Manual 28. Configuring Supplementary Services For a Lync 2010 client that moves inside the corporate network such as a soft phone on a laptop that connects wirelessly to the corporate network, Lync Server 2010 can determine which subnet the phone belongs to or which WAP / SSID is currently serving the soft-client.
  • Page 380 Mediant 800 MSBR Network Element Columns er>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSu ffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> For the ELIN number to be included in the SIP INVITE (XML-based PIDF-LO message) sent by the Mediation Server to the ELIN Gateway, the Administrator must add the ELIN number to the <CompanyName> column (shown in the table above in bold typeface). As the ELIN Gateway supports up to five ELINs per PIDF-LO, the <CompanyName>...
  • Page 381 ELIN when dialing 9-1-1. 28.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 382 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 383 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 384 Mediant 800 MSBR a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=ptime:20 ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/pidf+xml Content-ID: <voip_911_user1@contoso.com> <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:bp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ms="urn:schema:Rtc.LIS.msftE911PidfExtn.2008" entity="sip:voip_911_user1@contoso.com"><tuple id="0"><status><gp:geopriv><gp:location- info><ca:civicAddress><ca:country>US</ca:country><ca:A1>WA</ca:A1> <ca:A3>Redmond</ca:A3><ca:RD>163rd</ca:RD><ca:STS>Ave</ca:STS><ca: POD>NE</ca:POD><ca:HNO>3910</ca:HNO><ca:LOC>40/4451</ca:LOC> <ca:NAM>1111-222-333; 1234567890 </ca:NAM> <ca:PC>98052</ca:PC></ca:civicAddress></gp:location- info><gp:usage-rules><bp:retransmission- allowed>true</bp:retransmission-allowed></gp:usage- rules></gp:geopriv><ms:msftE911PidfExtn><ms:ConferenceUri>sip:+142 55550199@contoso.com;user=phone</ms:ConferenceUri><ms:ConferenceMo de>twoway</ms:ConferenceMode><LocationPolicyTagID...
  • Page 385 User's Manual 28. Configuring Supplementary Services ELIN Gateway to translate the ELIN number back into the E9-1-1 caller's extension number. 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 extension number as matched in the ELIN table.

  • Page 386: Configuring Audiocodes Elin Gateway

    28.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. 28.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 387 User's Manual 28. Configuring Supplementary Services To support this requirement, the ELIN Gateway can be configured to send the 503 "Service Unavailable" release cause code instead of SIP 4xx if an emergency call cannot be established. To enable this support, the following ini file parameter setting must be done: Note: This also...

  • Page 388: Multilevel Precedence And Preemption

    Mediant 800 MSBR  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump 28.12 Multilevel Precedence and Preemption The device supports Multilevel Precedence and Preemption (MLPP) service. MLPP is a call priority scheme, which does the following: ...
  • Page 389 User's Manual 28. Configuring Supplementary Services The device automatically interworks the network identity digits (NI) in the ISDN Q.931 Precedence Information Element (IE) to the network domain subfield of the INVITE's Resource-Priority header, and vice versa. The SIP Resource-Priority header contains two fields, namespace and priority.

  • Page 390: Mlpp Preemption Events In Sip Reason Header

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

  • Page 391: Precedence Ring Tone

    User's Manual 28. Configuring Supplementary Services • 480 (Temporarily Unavailable), 486 (User Busy), 488 (Not Acceptable Here) - Due to incoming calls being preempted by another call. The device receives SIP requests with preemption reason cause=5 in the following cases: •...

  • Page 392: Configuring Isdn Supplementary Services

    Mediant 800 MSBR 28.14 Configuring ISDN Supplementary Services The ISDN Supp Services Table page allows you to configure supplementary services for Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) phones connected to the device. This feature enables the device to route IP-to-Tel calls (including voice and fax) to specific BRI ports (channels).
  • Page 393 User's Manual 28. Configuring Supplementary Services Configure the parameters as described in the table below. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 624. To register the BRI endpoints, click the Register button. To unregister the BRI endpoints, click Unregister.

  • Page 394: Advice Of Charge Services For Euro Isdn

    Mediant 800 MSBR 28.15 Advice of Charge Services for Euro ISDN Advice of charge (AOC) is a pre-billing function that tasks the rating engine with calculating the cost of using a service and relaying that information back to the customer thus, allowing users to obtain charging information for all calls during the call (AOC-D) or at the end of the call (AOC-E), or both.

  • Page 395: Configuring Voice Mail

    User's Manual 28. Configuring Supplementary Services 28.16 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 755. Notes: • The Voice Mail Settings page is available only for FXO and CAS interfaces.
  • Page 396 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 397: Analog Gateway

    User's Manual 29. Analog Gateway Analog Gateway This section describes configuration of analog settings. Note: The Analog Gateway submenu appears only if the device is installed with an FXS or FXO module. 29.1 Configuring Keypad Features The Keypad Features page enables you to activate and deactivate the following features directly from the connected telephone's keypad: ...

  • Page 398: Configuring Metering Tones

    Mediant 800 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 29-1: Keypad Features Page Configure the keypad features as required. Click Submit to apply your changes.

  • Page 399: Configuring Charge Codes

    User's Manual 29. Analog Gateway  To configure Metering tones: Open the Metering Tones page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Metering Tones). Figure 29-2: Metering Tones Page Configure the Metering tones parameters as required. For a description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 755.

  • Page 400: Configuring Fxo Settings

    Mediant 800 MSBR  To configure the Charge Codes: Open the Charge Codes Table page (Configuration tab > VoIP menu > GW and IP to IP submenu > Analog Gateway submenu > Charge Codes). Alternatively, you can access this page from the Metering Tones page (see 'Configuring Metering Tones' on page 398).

  • Page 401: Configuring Authentication

    User's Manual 29. Analog Gateway Note: The FXO Settings page is available only for FXO interfaces.  To configure the FXO parameters: Open the FXO Settings page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > FXO Settings). Figure 29-4: FXO Settings Page Configure the parameters as required.

  • Page 402: Configuring Automatic Dialing

    Mediant 800 MSBR  To configure authentication credentials per port: Set the parameter 'Registration Mode' (AuthenticationMode) to Per Endpoint. This can be configured in any of the following pages: • Proxy & Registration page (see 'Configuring Proxy and Registration Parameters' on page 228).
  • Page 403 User's Manual 29. Analog Gateway  To configure automatic dialing per port: Open the Automatic Dialing page (Configuration tab > VoIP menu > GW and IP to IP submenu > Analog Gateway > Automatic Dialing). Figure 29-6: Automatic Dialing Page The first table entry in the figure above enables Hotline automatic dialing for an FXS port, whereby if the port is off-hooked for over 15 seconds, the device automatically dials 911.

  • Page 404: Configuring Caller Display Information

    Mediant 800 MSBR Parameter Description Hotline Dial Tone Duration Defines the duration (in seconds) after which the destination CLI: hotline-dia-ltone-duration phone number is automatically dialed. This is applicable only if [TargetOfChannel_HotLineTon the port has been configured for Hotline (i.e., 'Auto Dial Status' is eDuration] set to Hotline).

  • Page 405: Configuring Call Forward

    User's Manual 29. Analog Gateway Caller Display Parameter Description Parameter Description Gateway Port Displays the port per module. CLI: port [CallerDisplayInfo_Port] [CallerDisplayInfo_Module] Caller ID/Name Defines the Caller ID string. CLI: display-string The valid value is a string of up to 18 characters. [CallerDisplayInfo_DisplayStrin Presentation Enables the sending of the caller ID string.
  • Page 406 Mediant 800 MSBR  To configure Call Forward per port: Open the Call Forward Table page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Call Forward). Figure 29-8: Call Forward Table Page Configure the table as required. For descriptions of the parameters, see the table below.

  • Page 407: Configuring Caller Id Permissions

    User's Manual 29. Analog Gateway 29.9 Configuring Caller ID Permissions The Caller ID Permissions table allows you to enable per port, Caller ID generation for FXS interfaces and Caller ID detection for FXO interfaces. Notes: • 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 408: Configuring Call Waiting

    Mediant 800 MSBR 29.10 Configuring Call Waiting The Call Waiting table allows you to enable or disable call waiting per FXS port. Notes: • This page is applicable only to FXS interfaces. • 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 409: Rejecting Anonymous Calls

    User's Manual 29. Analog Gateway Parameter Description signal. When the device detects a hook-flash from the FXS port, the device switches to the waiting call. The device that initiated the waiting call plays a call waiting ringback tone to the calling party after a 182 response is received.
  • Page 410 Mediant 800 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 the Add button; the following dialog box appears: Figure 29-11: Tone Index Table Page The figure above shows a configuration example for using distinctive ringing and call waiting tones of Index #9 ('Priority Index' 1) in the CPT file for FXS endpoints 1 to 4...

  • Page 411: Fxs/Fxo Coefficient Types

    User's Manual 29. Analog Gateway 29.13 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 412: Fxo Operations For Ip-To-Tel Calls

    Mediant 800 MSBR 29.14.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 412) • Waiting for dial tone (see 'Two-Stage Dialing' on page 413) •...

  • Page 413: Two-Stage Dialing

    User's Manual 29. 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 414: Fxo Operations For Tel-To-Ip Calls

    Mediant 800 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. DID wink enables the originating end to seize the line by going off-hook.

  • Page 415: Collecting Digits Mode

    User's Manual 29. Analog Gateway 29.14.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 29-14: Call Flow for Collecting Digits Mode 29.14.2.3 FXO Supplementary Services The FXO supplementary services include the following: ...

  • Page 416: Call Termination On Fxo Devices

    PBX / CO must be recorded and its frequencies analyzed. Adding a reorder tone to the CPT file can be done using AudioCodes CPTWizard utility (refer to the CPTWizard Utility User's Guide). This method is slightly less reliable than the previous one.

  • Page 417: Call Termination Before Call Establishment

    User's Manual 29. Analog Gateway 29.14.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 418: Dialing From Remote Extension (Phone At Fxs)

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

  • Page 419: Message Waiting Indication For Remote Extensions

    User's Manual 29. Analog Gateway There is one-to-one mapping between PBX lines and FXS device ports. Each PBX line is routed to the same phone (connected to the FXS device). The call disconnects when the phone connected to the FXS device is on-hooked. 29.15.3 Message Waiting Indication for Remote Extensions The device supports the relaying of Message Waiting Indications (MWI) for remote extensions (and voice mail applications).

  • Page 420: Fxs Gateway Configuration

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

  • Page 421: Fxo Gateway Configuration

    User's Manual 29. Analog Gateway 29.15.6 FXO Gateway Configuration The procedure below describes how to configure the FXO interface (to which the PBX is directly connected).  To configure the FXO interface: In the Trunk Group Table page (see , assign the phone numbers 200 to 204 to the device’s FXO endpoints.
  • Page 422 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 423: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 425: Sbc Overview

    User's Manual 30. 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 based on network topology, refer to the SBC Design Guide document. •...

  • Page 426: Sip Network Definitions

    Mediant 800 MSBR application can overcome interoperability problems between SIP user agents. This is achieved by the following: • Manipulation of SIP URI user and host parts. • Connection to ITSP SIP trunks on behalf of an IP-PBX - the device can register and utilize user and password to authenticate for the IP-PBX.
  • Page 427 User's Manual 30. SBC Overview ♦ Destination URL: The destination URL is obtained from the Request-URI. Note: You can determine the SIP header from where the device obtains the source URL in the incoming SIP request. This is done in the IP Group table using the 'Source URI Input' parameter.

  • Page 428: User Registration And Internal Database

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

  • Page 429: Initial Registration Request Processing

    User's Manual 30. 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 430: Routing Using Internal Database

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

  • Page 431: Registration Restriction Control

    User's Manual 30. SBC Overview This feature is enabled only if a REGISTER message is sent to an IP Group destination type, configured in the IP-to-IP Routing table. 30.3.6 Registration Restriction Control The device provides flexibility in controlling user registration: ...
  • Page 432 Mediant 800 MSBR address, port, coders, media types, and RTP mode). The media capabilities exchanged in an offer/answer transaction include the following:  Media types (Audio, Secure Audio, Video, Fax, Text...)  IP addresses and ports of the media flow ...

  • Page 433: Media Anchoring Without Transcoding (Transparent)

    User's Manual 30. SBC Overview 30.4.1 Media Anchoring without Transcoding (Transparent) To direct the RTP to flow through the device (for NAT traversal, firewall and security), all IP address fields in the SDP are modified:  Origin: IP address, session and version id ...
  • Page 434 Mediant 800 MSBR assigned to each IP Group. Therefore, each offer destined to specific IP Groups include this coder. In the scenario depicted in the figure below, the IP phone on the LAN side initiates a call to the IP phone on the WAN. The initial SDP offer (from the LAN leg) includes codec G.711 as its supported codec.

  • Page 435: No Media Anchoring

    User's Manual 30. 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 436 Mediant 800 MSBR Figure 30-5: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring include the following:  Saves network bandwidth  Reduces CPU usage (no RTP/SRTP handling)  Avoids interference in SDP negotiation and header manipulation on RTP/SRTP The No Media Anchoring process is 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 437: Transcoding Modes

    User's Manual 30. SBC Overview 30.4.4 Transcoding Modes The device supports the configuration of the voice transcoding mode (media negotiation) between the two SBC legs. The device can be configured to perform transcoding only when necessary. Typically, the SBC passes RTP packets transparently (RTP-to-RTP) between the two user agents.

  • Page 438: Coder Transcoding

    Mediant 800 MSBR For example, assume the following:  The SDP coder offer includes the following coders: G.729, G.711, and G.723.  The source (first) leg includes the following Allowed Coders: G.711 and G.729. The device selects the common coders, i.e., G.711 and G.729 (with changed preferred coder priority - highest for G.711).

  • Page 439: Prioritizing Coder List In Sdp Offer

    User's Manual 30. SBC Overview a=ptime:20 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no In the SDP, the "m=audio 6010 RTP/AVP 8 0 96 18" line shows that the coder priority has changed - G.711A-law ("8") and then G.711U-law ("0") - and that the Extension coder G.729 ("18") has been added.

  • Page 440: Multiple Rtp Media Streams Per Call Session

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

  • Page 441: Fax Negotiation And Transcoding

    User's Manual 30. SBC Overview methods is In-band\RFC 2833, detection and generation of DTMF methods requires DSP allocation. 30.5 Fax Negotiation and Transcoding The device can allow fax transmissions to traverse transparently without transcoding or it can handle the fax as follows: ...

  • Page 442: Interworking Sip Signaling

    Mediant 800 MSBR If the message is received without an Authorization header, the device "challenges" the client by sending a 401 or 407 SIP response. The client then resends the request with an Authorization header (containing the user name and password). The device validates the SIP message according to the settings of the parameters, AuthNonceDuration, AuthChallengeMethod and AuthQOP.
  • Page 443 User's Manual 30. SBC Overview The device enforces this by modifying each Contact in the 3xx response as follows:  Changes the host part to the device's IP address – this change causes the remote user agent to send the INVITE to the device. ...

  • Page 444: Local Handling Of Sip 3Xx

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

  • Page 445: Interworking Sip Refer Messages

    User's Manual 30. SBC Overview Parameter Value SIP Header Present in Received SIP Message HistoryInfoMode = Diversion History-Info Both removed. Remove removed. removed. DiversionMode = Remove 30.8.3 Interworking SIP REFER Messages The device supports interworking of SIP REFER messages. SIP UAs may support different versions of the REFER standard while others may not even support REFER.

  • Page 446: Interworking Sip Session Timer

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

  • Page 448: Interworking Sip Re-Invite Messages

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

  • Page 449: Interworking Call Hold

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

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

    Mediant 800 MSBR <alias>sip:rhughes@broadsoft.com</alias> </aliases> <extensions> <extension>5317</extension> <extension>1321</extension> </extensions> </BroadSoftDocument> 30.9.2 BroadSoft's Shared Phone Line Call Appearance for SBC Survivability The device can provide redundancy for BroadSoft's Shared Call Appearance feature. When the BroadSoft application server switch (AS) fails or does not respond, or when the network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients.

  • Page 451: Call Survivability For Call Centers

    User's Manual 30. SBC Overview  To configure the Shared Line feature: In the IP Group table (see 'Configuring IP Groups' on page 210), add a Server-type IP Group for the BroadWorks server. In the IP Group table, add a User-type IP Group for the IP phone users and set the 'Enable SBC Client Forking' parameter to Yes so that the device forks incoming calls to all contacts under the same AOR that are registered in the device's registration database.
  • Page 452 Mediant 800 MSBR Figure 30-11: Normal Operation in Call Center Application Figure 30-12: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Group table (see 'Configuring IP Groups' on page 210), add IP Groups for the following entities: •...

  • Page 453: Survivability Mode Display On Aastra Ip Phones

    User's Manual 30. SBC Overview ♦ The 'Destination Type' field is set to Hunt Group, which is specifically used for call center survivability. ♦ The 'Destination IP Group ID' field is set to the IP Group of the call center agents.

  • Page 454: Call Forking

    Mediant 800 MSBR </LocalModeStatus> </LMIDocument> 30.10 Call Forking This section describes various Call Forking features supported by the device. 30.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 thedevice'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 455: Alternative Routing On Detection Of Failed Sip Response

    User's Manual 30. SBC Overview final response, then it is possible that the SDP answer that was forwarded to the INVITE- 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.
  • Page 456 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 457: Sbc Configuration

    User's Manual 31. SBC Configuration SBC Configuration This section describes the configuration of the SBC application. Note: For the SBC application, the following requirements must be met: • The SBC application must be enabled (see 'Enabling Applications' on page 203). •...

  • Page 458: Configuring Admission Control

    Mediant 800 MSBR 31.2 Configuring Admission Control The Admission Control page allows you to define up to 100 rules for limiting the number of concurrent calls (SIP dialogs). These call limits can be applied per SRD, IP Group, SIP request type (e.g., INVITEs), SIP dialog direction (e.g., inbound), and/or per user (identified by its registered contact).
  • Page 459 User's Manual 31. SBC Configuration  To configure Admission Control rules: Open the Admission Control page (Configuration tab > VoIP menu > SBC > Admission Control). Click the Add button; the following dialog box appears: Figure 31-2: Admission Control Page - Add Record Dialog Box Configure the rule as required.

  • Page 460: Configuring Allowed Coder Groups

    Mediant 800 MSBR Parameter Description Request Direction Defines the direction of the SIP request to which the rule applies. CLI: request-direction  [0] Both = (Default) Rule applies to inbound and outbound SIP [SBCAdmissionControl dialogs. _RequestDirection]  [1] Inbound = Rule applies only to inbound SIP dialogs. ...

  • Page 461: Routing Sbc

    User's Manual 31. SBC Configuration Notes: • Each coder can appear only once per Allowed Coder Group. • Allowed Coder Groups are applicable only to audio media. • Allowed Coder Groups can be assigned to IP Profiles (see 'Configuring IP Profiles' on page 245). •...

  • Page 462: Configuring Classification Rules

    Mediant 800 MSBR 31.4.1 Configuring Classification Rules The Classification table enables you to configure up to 100 Classification rules. Classification rules are used to classify incoming SIP dialog-initiating requests (e.g., INVITE messages) to source IP Groups from where the SIP dialog request originated. The identified IP Group is later used in the manipulation and routing processes.
  • Page 463 User's Manual 31. SBC Configuration Note: If classification for a SIP request fails and the device is configured to reject unclassified calls, the device can send a specific SIP response code per SIP interface, configured by the 'Classification Failure Response Type' parameter in the SIP Interface table (see 'Configuring SIP Interface Table' on page 207).
  • Page 464 Mediant 800 MSBR The Classification table provides two configuration areas:  Matching characteristics of incoming IP call, for example, source IP address.  Operation - classifies call to an IP Group. If the incoming call matches the characteristics of a rule, then the call is classified to the IP Group configured for that rule.
  • Page 465 User's Manual 31. SBC Configuration Parameter Description CLI: src-ip-address incoming SIP dialog. [Classification_SrcAdd Notes: ress]  If this parameter is not configured or is configured as an asterisk (*), then any source IP address is accepted.  The IP address can include the "x" wildcard to represent single digits. For example: 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.

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

    Mediant 800 MSBR Parameter Description Message Condition Assigns a Condition rule which can also be used to classify the incoming CLI: message-condition SIP dialog. [Classification_Messag Note: Condition rules are configured in the Condition Table (see eCondition] 'Configuring Condition Rules' on page 467). Operation Rule Source IP Group ID Defines an IP Group to which the incoming SIP dialog request is...

  • Page 467: Configuring Condition Rules

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

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

    Mediant 800 MSBR Figure 31-6: Condition Table Page - Add Record Dialog Box Configure the rule as required. For a description of the parameters, see the table below. Click Submit. The figure below shows an example of the Condition table configured with the following rules: ...
  • Page 469 User's Manual 31. SBC Configuration  Request-URI of incoming SIP dialog initiating requests.  ENUM query.  Hunt Group - used for call survivability (see 'Call Survivability for Call Centers' on page 451).  IP address (in dotted-decimal notation or FQDN - NAPTR/SRV/A-Record resolutions) according to a specified Dial Plan index listed in the loaded Dial Plan file.
  • Page 470 Mediant 800 MSBR receipt of 3xx or REFER and where the device handles the requests locally (instead of forwarding the 3xx or REFER to the destination).  Least cost routing (LCR): If the LCR feature is enabled, the device searches the routing table for matching routing rules and then selects the one with the lowest call cost.
  • Page 471 User's Manual 31. SBC Configuration IP-to-IP Routing Table Parameters Description Parameter Description Matching Characteristics Source IP Group ID Selects the IP Group from where the IP-to-IP call originated. Typically, [IP2IPRouting_SrcIPGro the IP Group of an incoming SIP dialog is determined (or classified) upID] using the ‘Classification’...
  • Page 472 Mediant 800 MSBR Parameter Description The default is -1 (i.e., not configured). Call Trigger Defines the reason (i.e, trigger) for re-routing the SIP request: [IP2IPRouting_Trigger]  [0] Any = (Default) This routing rule is used for all scenarios (re- CLI: trigger routes and non-re-routes).
  • Page 473 User's Manual 31. SBC Configuration Parameter Description If the destination IP Group is of USER type, the device searches for a match between the Request-URI (of the received SIP dialog) to an AOR registration record in the device's database. The SIP dialog is then sent to the IP address of the registered contact.

  • Page 474: Configuring Alternative Routing Reasons

    Mediant 800 MSBR Parameter Description  nsportType] [0] UDP CLI: dst-transport-type  [1] TCP  [2] TLS Note: When this parameter is set to -1, the transport type is determined by the parameter SIPTransportType. Alternative Route Determines whether this routing rule is the main routing rule or an Options alternative routing rule (to the rule defined directly above it in the table).

  • Page 475: Sbc Manipulations

    User's Manual 31. SBC Configuration Notes: • Alternative routing occurs even if this table is not configured upon scenarios where no response, ICMP, or a SIP 408 response is received. • SIP requests pertaining to an SRD or IP Group that reach the call limit (maximum concurrent calls and/or call rate) as defined in the Call Admission table are sent to an alternative route if configured in the IP-to- IP Routing table for the SRD or IP Group.
  • Page 476 Mediant 800 MSBR Figure 31-11: SIP URI Manipulation in IP-to-IP Routing You can also restrict source user identity in outgoing SIP dialogs in the Outbound Manipulation table (using the column PrivacyRestrictionMode). The device identifies an incoming user as restricted if one of the following exists: ...

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

    User's Manual 31. SBC Configuration Contact: <sip:7000@212.179.1.12> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 5 IN IP4 212.179.1.11 s=Phone-Call c=IN IP4 212.179.1.11 t=0 0 m=audio 8000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 The SIP message manipulations in the example above (contributing to typical topology hiding) are as follows: ...
  • Page 478 Mediant 800 MSBR  Manipulated source URI user part are done on the following SIP headers: From, P- Asserted-Identity (if exists), P-Preferred-Identity (if exists), and Remote-Party-ID (if exists) The IP to IP Inbound Manipulation table provides two configuration areas:  Matching characteristics (Rule) of incoming call, for example, source host name.
  • Page 479 User's Manual 31. SBC Configuration Parameter Description [IPInboundManipulatio the rule above it). n_IsAdditionalManipula  [1] Yes = If the above row entry rule matched the call, consider this tion] row entry as a match as well and perform the manipulation specified by this rule.

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

    Mediant 800 MSBR Parameter Description Manipulated URI Determines whether the source or destination SIP URI user part is CLI: manipulated-uri manipulated. [IPInboundManipulatio  [0] Source = (Default) Manipulation is done on the source SIP URI n_ManipulatedURI] user part.  [1] Destination = Manipulation is done on the destination SIP URI user part.
  • Page 481 User's Manual 31. SBC Configuration Notes: • Manipulated destination SIP URI user names are done on the following SIP headers: Request URI, To, and Remote-Party-ID (if exists). • Manipulated source SIP URI user names are done on the following SIP headers: From, P-Asserted (if exists), P-Preferred (if exists), and Remote-Party-ID (if exists) •...
  • Page 482 Mediant 800 MSBR Parameter Description  manipulation [0] No = (Default) Regular manipulation rule - not done in addition to [IPOutboundManipulati the rule above it. on_IsAdditionalManipu  [1] Yes = If the previous table row entry rule matched the call, lation] consider this row entry as a match as well and perform the manipulation specified by this rule.
  • Page 483 User's Manual 31. SBC Configuration Parameter Description  This parameter functions together with the 'Call Trigger' parameter (see below).  For more information on interworking of SIP 3xx redirect responses or REFER messages, see 'Interworking SIP 3xx Redirect Responses' on page and 'Interworking SIP REFER Messages' on page 445, respectively.
  • Page 484 Mediant 800 MSBR Parameter Description  If a P-Asserted-Identity header exists (either in the incoming SIP dialog or added by the device), a Privacy header is added with the value "id".  [2] Restrict = The user identity is restricted (the restricted presentation is as mentioned above).

  • Page 485: Cloud Resilience Package Application

    Part VII Cloud Resilience Package Application...

  • Page 487: Crp Overview

    User's Manual 32. CRP Overview CRP Overview The device's Cloud Resilience Package (CRP) application enhances cloud-based or hosted communications environments by ensuring survivability, high voice quality and security at enterprise branch offices and cloud service customer premises. CRP is designed to be deployed at customer sites and branches of: ...
  • Page 488 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 489: Crp Configuration

    User's Manual 33. CRP Configuration CRP Configuration This section describes configuration specific to the CRP application. As CRP has similar functionality to the SBC application, for configuration common to the SBC, which is not covered in this section, see the following SBC sections: ...

  • Page 490: Configuring Call Survivability Mode

    Mediant 800 MSBR 33.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 491: Pre-Configured Ip Groups

    User's Manual 33. 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. Figure 15: CRP in Always Emergency Mode ...

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

    Mediant 800 MSBR 33.4 Pre-Configured IP-to-IP Routing Rules 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 490. Notes: • The IP-to-IP Routing table is read-only. •...

  • Page 493: Stand-Alone Survivability Application

    Part VIII Stand-Alone Survivability Application...

  • Page 495: Sas Overview

    User's Manual 34. SAS Overview SAS Overview The device's Stand-Alone Survivability (SAS) feature ensures telephony communication continuity (survivability) for enterprises using hosted IP services (such as IP Centrex) or IP- PBX in cases of failure of these entities. In case of failure of the IP Centrex, IP-PBX servers (or even WAN connection and access Internet modem), the enterprise typically loses its internal telephony service at any branch, between its offices, and with the external environment.

  • Page 496: Sas Outbound Mode

    Mediant 800 MSBR 34.1.1 SAS Outbound Mode This section describes the SAS outbound mode, which includes the following states:  Normal state (see 'Normal State' on page 496)  Emergency state (see 'Emergency State' on page 496) 34.1.1.1 Normal State In normal state, SAS receives REGISTER requests from the enterprise's UAs and forwards them to the external proxy (i.e., outbound proxy).

  • Page 497: Sas Redundant Mode

    User's Manual 34. SAS Overview Figure 34-2: SAS Outbound Mode in Emergency State (Example) When emergency state is active, SAS continuously attempts to communicate with the external proxy, using keep-alive SIP OPTIONS. Once connection to the proxy returns, the device exits SAS emergency state and returns to SAS normal state, as explained in 'Exiting Emergency and Returning to Normal State' on page 498.

  • Page 498: Normal State

    Mediant 800 MSBR 34.1.2.1 Normal State In normal state, the UAs register and operate directly with the external proxy. Figure 34-3: SAS Redundant Mode in Normal State (Example) 34.1.2.2 Emergency State If the UAs detect that their primary (external) proxy does not respond, they immediately register to SAS and start routing calls to it.

  • Page 499: Sas Routing

    User's Manual 34. SAS Overview 34.2 SAS Routing This section provides flowcharts describing the routing logic for SAS in normal and emergency states. 34.2.1 SAS Routing in Normal State The flowchart below displays the routing logic for SAS in normal state for INVITE messages received from UAs: Figure 34-5: Flowchart of INVITE from UA's in SAS Normal State The flowchart below displays the routing logic for SAS in normal state for INVITE...
  • Page 500 Mediant 800 MSBR Figure 34-6: Flowchart of INVITE from Primary Proxy in SAS Normal State User's Manual Document #: LTRT-12809...

  • Page 501: Sas Routing In Emergency State

    User's Manual 34. SAS Overview 34.2.2 SAS Routing in Emergency State The flowchart below shows the routing logic for SAS in emergency state: Figure 34-7: Flowchart for SAS Emergency State Version 6.6 Mediant 800 MSBR...
  • Page 502 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 503: Sas Configuration

    Note: The SAS application is available only if the device is installed with the SAS Software License Key. If your device is not installed with the SAS feature, contact your AudioCodes representative.  To enable the SAS application: Open the Applications Enabling page (Configuration tab > VoIP menu >...
  • Page 504 Mediant 800 MSBR  To configure common SAS settings: Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand Alone Survivability). Define the port used for sending and receiving SAS messages. This can be any of the following port types: •...
  • Page 505 User's Manual 35. SAS Configuration • Outbound mode: In SAS normal state, SAS forwards REGISTER and INVITE messages received from the UAs to the proxy servers defined in this Proxy Set. • Redundant mode and only if UAs don't support homing: SAS sends keep- alive messages to this proxy and if it detects that the proxy connection has resumed, it ignores the REGISTER messages received from the UAs, forcing them to send their messages directly to the proxy.

  • Page 506: Configuring Sas Outbound Mode

    Mediant 800 MSBR 35.2 Configuring SAS Outbound Mode This section describes how to configure the SAS outbound mode. These settings are in addition to the ones described in 'Configuring Common SAS Parameters' on page 503. Note: The VoIP CPEs (such as IP phones or residential gateways) need to be defined so that their proxy and registrar destination addresses and ports are the same as that configured for the device's SAS IP address and SAS local SIP port.

  • Page 507: Configuring Gateway Application With Sas

    User's Manual 35. SAS Configuration 35.4 Configuring Gateway Application with SAS If you want to run both the Gateway and SAS applications on the device, the configuration described in this section is required. The configuration steps depend on whether the Gateway application is operating with SAS in outbound mode or SAS in redundant mode.

  • Page 508: Gateway With Sas Redundant Mode

    Mediant 800 MSBR Figure 35-4: Defining Proxy Server for Gateway Application Click Submit. Disable use of user=phone in SIP URL: Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions submenu > General Parameters). From the 'Use user=phone in SIP URL' drop-down list, select No. This instructs the Gateway application not to use user=phone in the SIP URL and therefore, REGISTER and INVITE messages use SIP URI.
  • Page 509 User's Manual 35. SAS Configuration  To configure Gateway application with SAS redundant mode: Define the proxy servers for the Gateway application: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions submenu > Proxy & Registration). From the 'Use Default Proxy' drop-down list, select Yes.

  • Page 510: Advanced Sas Configuration

    CSeq: 1 REGISTER Contact: <sip: 976653434@10.10.10.10:5050>;expires=180 Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Expires: 180 User-Agent: Audiocodes-Sip-Gateway-/v. Content-Length: 0 After manipulation, SAS registers the user in its database as follows:  AOR: 976653434@10.33.4.226  Associated AOR: 3434@10.33.4.226 (after manipulation, in which only the four digits from the right of the URI user part are retained) ...

  • Page 511: Manipulating Destination Number Of Incoming Invite

    User's Manual 35. SAS Configuration Figure 35-8: Manipulating User Part in Incoming REGISTER Click Submit. Notes: • The device first does manipulation according to the Remove From Right parameter and only then according to the Leave From Right parameter. • Only one manipulation rule can be configured.
  • Page 512 Mediant 800 MSBR  To manipulate the destination number in SAS emergency state: Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand Alone Survivability). From the 'SAS Inbound Manipulation Mode' (SASInboundManipulationMode) drop- down list, select Emergency Only. Click Submit;...
  • Page 513 User's Manual 35. SAS Configuration Parameter Description Source Username Prefix Defines the prefix of the source SIP URI user name (usually in the From CLI: src-user-name- header). prefix For any prefix, enter the asterisk "*" symbol (default). [IPInboundManipulatio Note: The prefix can be a single digit or a range of digits. For available n_SrcUsernamePrefix] notations, see 'Dialing Plan Notation for Routing and Manipulation' on page 753.

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

    Mediant 800 MSBR Parameter Description Prefix to Add Defines the number or string that you want added to the front of the user CLI: prefix-to-add name. For example, if you enter 'user' and the user name is "john", the [IPInboundManipulatio new user name is "userjohn".
  • Page 515 User's Manual 35. SAS Configuration Figure 35-9: Add Record Dialog Box of SAS IP2IP Routing Page Configure the rule according to the table below. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 624. Note: The following parameters are not applicable to SAS and must be ignored: •...
  • Page 516 Mediant 800 MSBR Parameter Description prefix available notations, see 'Dialing Plan Notation for Routing and Manipulation' on page 753. The default is * (i.e., any prefix). Source Host Defines the host part of the incoming SIP dialog's source URI (usually [IP2IPRouting_SrcHost the From URI).
  • Page 517 User's Manual 35. SAS Configuration Parameter Description Operation Routing Rule Destination Type Determines the destination type to which the outgoing SIP dialog is sent. [IP2IPRouting_DestTyp  [0] IP Group = (Default) The SIP dialog is sent to the IP Group’s Proxy Set (SERVER-type IP Group) or registered contact from the CLI: dst-type database (if USER-type IP Group).
  • Page 518 Mediant 800 MSBR Parameter Description table, see 'Configuring IP Groups' on page 210). If this table does not define an IP Group but only an SRD, then the first IP Group associated with this SRD (in the IP Group table) is used. ...

  • Page 519: Blocking Calls From Unregistered Sas Users

    User's Manual 35. SAS Configuration Parameter Description  For IP-to-IP alternative routing, configure alternative routing reasons upon receipt of 4xx, 5xx, and 6xx SIP responses (see Configuring Alternative Routing Reasons on page 474). However, if no response, ICMP, or a SIP 408 response is received, the device attempts to use the alternative route even if no entries are configured in the ‘SBC Alternative Routing Reasons’...

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

    Mediant 800 MSBR In the 'SAS Emergency Numbers' field, enter an emergency number in each field box. Figure 35-10: Configuring SAS Emergency Numbers Click Submit to apply your changes. 35.5.6 Adding SIP Record-Route Header to SIP INVITE You can configure SAS to add the SIP Record-Route header to SIP requests (e.g. INVITE) received from enterprise UAs.

  • Page 521: Replacing Contact Header For Sip Messages

    User's Manual 35. SAS Configuration  To re-use TCP connection sessions in SAS Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand Alone Survivability). From the ‘SAS Connection Reuse' drop-down list, select Enable. Click Submit to apply your changes. 35.5.8 Replacing Contact Header for SIP Messages You can configure SAS to change the SIP Contact header so that it points to the SAS host.

  • Page 522: Viewing Registered Sas Users

    Mediant 800 MSBR 35.6 Viewing Registered SAS Users You can view all the users that are registered in the SAS registration database. This is displayed in the 'SAS/SBC Registered Users page, as described in 'Viewing Registered Users' on page 688. Note: You can increase the maximum number of registered SAS users, by implementing the SAS Cascading feature, as described in 'SAS Cascading'...

  • Page 523: Sas Cascading

    User's Manual 36. SAS Cascading SAS Cascading The SAS Cascading feature allows you to increase the number of SAS users above the maximum supported by the SAS gateway. This is achieved by deploying multiple SAS gateways in the network. For example, if the SAS gateway supports up to 600 users, but your enterprise has 1,500 users, you can deploy three SAS gateways to accommodate all users: the first SAS gateway can service 600 registered users, the second SAS gateway the next 600 registered users, and the third SAS gateway the rest (i.e., 300 registered...
  • Page 524 Mediant 800 MSBR  SAS Redundancy mode: If users cannot be distinguished (i.e., associated to a specific SAS gateway), then the SAS Redundancy feature is used to configure SAS Cascading. This mode routes the call in a loop fashion, from one SAS gateway to the next, until the user is located.

  • Page 525: Ip Media Capabilities

    Part IX IP Media Capabilities...

  • Page 527: Transcoding Using Third-Party Call Control

    User's Manual 37. Transcoding using Third-Party Call Control Transcoding using Third-Party Call Control The device supports transcoding using a third-party call control Application server. This support is provided by the following:  Using RFC 4117 (see 'Using RFC 4117' on page 527) Note: Transcoding can also be implemented using the IP-to-IP application and SBC application.
  • Page 528 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 529: Data-Router Configuration

    Part X Data-Router Configuration...

  • Page 531: Introduction

    Management interfaces (Web, CLI and SNMP), and SIP (when using the device’s VoIP component). For a complete list of features supported only on the default VRF, please contact AudioCodes. For a detailed description of CLI configuration, refer to the MSBR Series CLI Reference Guide.
  • Page 532 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 533: Getting Acquainted With Data Configuration

    User's Manual 39. Getting Acquainted with Data Configuration Pages Getting Acquainted with Data Configuration Pages This section provides you with an overview on working with the data-routing configuration pages. 39.1 Working with Tables Throughout the data section of the Web interface, various configuration icons are provided in the configuration tables.

  • Page 534: Using The Configuration Buttons

    Mediant 800 MSBR 39.2 Using the Configuration Buttons Throughout the Data section of the Web interface, various buttons appear in the configuration pages, as described in the table below: Description of the Main Configuration Buttons Button Name Description Applies and saves the settings. Apply Applies the settings.

  • Page 535: Wan Access

    User's Manual 40. WAN Access WAN Access The WAN Access menu allows you to configure your WAN (Internet) connection. When subscribing to a broadband service, your Internet Service Provider (ISP) should provide you information regarding the method by which you are connecting to the Internet. The device can connect to the broadband service (WAN), using one of the following methods: ...
  • Page 536 Mediant 800 MSBR  To configure the Internet (WAN) connection: Open the Settings page (Configuration tab > Data menu > WAN Access submenu > Settings); the following page appears: Figure 40-1: WAN Access From the 'Connection Type' drop-down list, select the required WAN connection type: •...

  • Page 537: Configuring Shdsl Wan Interface

    User's Manual 40. WAN Access • 'Layer 2 Tunneling Protocol (L2TP)': Figure 40-4: L2TP WAN Connection Type Specify the following: ♦ L2TP Server Host Name or IP Address ♦ Login User Name ♦ Login Password ♦ Internet Protocol - select the method used by your ISP for assigning an IP address For advanced WAN settings, click the Click here for Advanced Settings link.
  • Page 538 Mediant 800 MSBR Figure 40-5: SHDSL Line Mode Page Click New Group to add a new SHDSL wire. Figure 40-6: Adding a New Group Note: When using EFM, only one wire-pair group can be defined. Configure the annex, line rate, and pair numbers as provided by your ISP, and then click OK.
  • Page 539 User's Manual 40. WAN Access Figure 40-7: SHDSL RJ-45 Wire Pinouts Click the SHDSL Line Settings link to refresh the status display and wait for the line to synchronize. Ensure that the group status displays "RUNNING" before proceeding to the next step. If EFM mode was selected, skip the following steps and proceed to 'Configuring Ethernet WAN Interface' on page 535.

  • Page 540: Configuring Adsl/2+ And Vdsl2 Wan Interface

    Mediant 800 MSBR Select the required IP encapsulation method, and then click Next. Figure 40-10: Configuring Internet Connection Select a unique sub-interface number for the new connection. Configure the VPI, VCI, encapsulation variant and class-of-service parameters as provided by your ISP. Note that the VPI/VCI combination must be unique in an SHDSL group.

  • Page 541: Configuring 3G/3.5G Cellular Wan Access

     Sierra Wireless AirCard 308 Note: To check for any additional supported 3G cellular modems, contact your AudioCodes sales representative. To configure a 3G cellular WAN connection, use the following CLI command: configure data > interface cellular 0/0 Version 6.6...

  • Page 542: Configuring Multiple Wan Backup

    Mediant 800 MSBR 40.5 Configuring Multiple WAN Backup You can configure a multiple WAN backup scheme for your device, where multiple WAN interfaces can serve as backups for the primary (or a backup) WAN interface. You can assign up to three WAN interfaces (e.g., optic fiber, VDSL, and 3G modem) to a backup WAN group.

  • Page 543: Firewall And Acl

    User's Manual 41. Firewall and ACL Firewall and ACL The Firewall and ACL menu allows you to configure various security applications. The device's security suite includes comprehensive and robust security services: Stateful Packet Inspection Firewall, user authentication protocols and password protection mechanisms.
  • Page 544 Mediant 800 MSBR The Port Forwarding item enables you to define the applications that require special handling by the device. This allows you to select the application's protocol (or add a new protocol) and the local IP address of the computer that will be using or providing the service.

  • Page 545: Configuring Website Restrictions

    User's Manual 41. Firewall and ACL provide the service (the "server"). Note that unless an additional external IP address has been added, only one LAN computer can be assigned to provide a specific service or application. From the 'Protocol' drop-down list, select Any or specify the type of protocol. Add a new one by selecting User Defined and then add a new Service representing the protocol (see 'Configuring Protocols' on page 579).

  • Page 546: Configuring Nat

    Mediant 800 MSBR 41.3 Configuring NAT The device features a configurable Network Address Translation (NAT) and Network Address Port Translation (NAPT) mechanism, allowing you to control the network addresses and ports of packets routed through the device. When enabling multiple computers on your network to access the Internet using a fixed number of public IP addresses, you can define static NAT/NATP rules which map (translate) LAN IP addresses (LAN computers) to NAT IP addresses and/or ports.
  • Page 547 User's Manual 41. Firewall and ACL Defines a NAT LAN IP address pool: Under the 'NAT LAN IP Address Pool' group, click the New IP Pool link; the following page appears: Figure 41-8: NAT LAN IP Address Pool From the 'Network Object Type' drop-down list, select between 'IP Range' or 'IP Subnet', and then enter the information respectively.

  • Page 548: Configuring The Access List

    Mediant 800 MSBR • NAPT: The NAPT address into which the original IP address is translated. The drop-down list displays all of your available NAPT addresses/ranges, from which you can select an entry. If you want to add a single address or a sub-range from the given pool/range, select User Defined to add a new Network Object representing the new host (see 'Configuring Network Objects' on page 580).
  • Page 549 User's Manual 41. Firewall and ACL Add rules to the Access List group: Under the Access List name that you defined (in Step 2), click the New Entry link; the following page appears for defining a rule: Figure 41-12: Adding an Access List Rules The Matching' and 'Operation' groups define the operation to be executed when matching conditions apply.

  • Page 550: Configuring Advanced Filtering

    Mediant 800 MSBR Click OK to save your changes; the Access Lists table re-appears, displaying the defined rules under the Access List Rule ID: Figure 41-13: Added Access List Rules The order of the rules appearing under a specific Access List name represents both the order in which they are defined and the sequence by which they are applied.

  • Page 551: Qos

    User's Manual 42. QoS The device's Quality of Service (QoS) provides the capability to provide better service to selected network traffic. This is achieved by shaping the traffic and processing higher priority traffic before lower priority traffic. The QoS menu provides the following items: ...
  • Page 552 Mediant 800 MSBR The device supports two priority marking methods for packet prioritization:  DSCP (see 'Configuring DSCP Settings' on page 557).  802.1p Priority (see 'Configuring 802.1p Settings' on page 559). The matching of packets by rules is connection-based, known as Stateful Packet Inspection (SPI), using the same connection-tracking mechanism used by the device's firewall.
  • Page 553 User's Manual 42. QoS Figure 42-3: Adding a Traffic Priority Rule Under the 'Matching' group, define characteristics of the packets matching the QoS rule: • Source Address: source address of packets sent or received by the device. The drop-down list allows you to specify a computer (address or a name) or group of computers on which you want to apply the rule.

  • Page 554: Configuring Traffic Shaping

    Mediant 800 MSBR • Set DSCP: Select this check box if you want to change the DSCP value (hexadecimal) on packets matching the rule, prior to routing them further. • Set Priority: Select this check box if you want to change a priority (where zero is the lowest and seven the highest) of the packets matching the rule.
  • Page 555 User's Manual 42. QoS  To configure traffic shaping: Click the Traffic Shaping item (Configuration tab > Data menu > QoS submenu > Traffic Shaping); the following page appears: Figure 42-4: Configuring Traffic Shaping Click the New Entry link; the following page appears. Figure 42-5: Adding Device for Traffic Shaping From the 'Device' drop-down list, select the interface for which you want to shape the traffic.
  • Page 556 Mediant 800 MSBR Figure 42-7: Adding Tx Shaping Class In the 'Name' field, enter a new Tx traffic shaping class name (e.g., Class A), and then click OK to save the settings; the class is added to the table. Figure 42-8: Class Name Added to Table Click the newly added class name;...

  • Page 557: Configuring Dscp Settings

    User's Manual 42. QoS according to packet's priority, which can be defined explicitly by a DSCP value or by a 802.1p value.  FIFO: The "First In, First Out" priority queue. This queue ignores any previously-marked priority that packets may have. ...
  • Page 558 Mediant 800 MSBR  To add, edit or delete DSCP settings: Click the DSCP Settings item (Configuration tab > Data menu > QoS submenu > DSCP Settings); the following page appears: Figure 42-10: Configuring DSCP Settings To edit an existing entry, click the corresponding Edit icon.

  • Page 559: Configuring 802.1P Settings

    User's Manual 42. QoS 42.5 Configuring 802.1p Settings The IEEE 802.1p priority marking method is a standard for prioritizing network traffic at the data link/Mac sub-layer. 802.1p traffic is simply classified and sent to the destination, with no bandwidth reservations established. The 802.1p header includes a 3-bit prioritization field, which allows packets to be grouped into eight levels of priority (0-7), where level 7 is the highest.
  • Page 560 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 561: Vpn

    User's Manual 43. VPN The VPN menu allows you to configure Virtual Private Networking (VPN) over the Internet, and includes the following items:  IPSec (see 'Configuring IPsec' on page 561)  L2TP (see 'Configuring L2TP Server' on page 563) 43.1 Configuring IPSec Internet Protocol Security (IPSec) is a series of guidelines for the protection of Internet...
  • Page 562 Mediant 800 MSBR To enable dropping of packets that are recognized (by their sequence number) as already been received, select the 'Anti-Replay Protection' check box. Configure the device's IPSec public keys: Click the Settings button; the following page appears. Figure 43-2: Recreating IPSec Public Key Click the Recreate Key button to recreate the public key, or the Refresh button to refresh the displayed key.

  • Page 563: Configuring L2Tp Server

    User's Manual 43. VPN 43.2 Configuring L2TP Server The device can act as a Layer 2 Tunneling Protocol Server (L2TP Server), accepting L2TP client connection requests.  To configure L2PT: Click the L2TP item (Configuration tab > Data menu > VPN submenu > L2TP); the following page appears: Figure 43-4: Configuring VPN L2TP Server Under the 'Server' group, perform the following:...

  • Page 564: Creating Vpn Users

    Mediant 800 MSBR to-Point Encryption mode: Stateless or Stateful. Under the 'Remote Address Range' group, in the 'Start IP Address' and 'End IP Address' fields, specify the range of IP addresses that are granted by the L2TP server to the L2TP client. Note: The server settings must be compatible with the client settings, described in 'Configuring Network Connections' on page 583.
  • Page 565 User's Manual 43. VPN Under the 'General' group, configure the following parameters: Full Name: remote user's full name. User Name: name that a user uses to access your network. New Password: user's password. Retype New Password: if a new password is assigned, type it again to verify its correctness.
  • Page 566 Mediant 800 MSBR Under the 'Security Logging' group, configure the following parameters: • Security Log Buffer Size: size of the security log buffer in Kilobytes. • Remote Security Notify Level: remote security notification level - None, Error, Warning, and Information. •...

  • Page 567: Data Services

    User's Manual 44. Data Services Data Services The Data Services submenu allows you to configure various services (applications), and includes the following menus:  DNS Server (see 'Configuring DNS Server' on page 567)  DHCP Server (see 'Configuring DHCP Server' on page 568) 44.1 Configuring DNS Server Domain Name System (DNS) provides a service that translates domain names into IP...

  • Page 568: Configuring Dhcp Server

    Mediant 800 MSBR 44.2 Configuring DHCP Server Your device's Dynamic Host Configuration Protocol (DHCP) server makes it possible to easily add computers that are configured as DHCP clients to the home network. It provides a mechanism for allocating IP addresses and delivering network configuration parameters to such hosts.
  • Page 569 User's Manual 44. Data Services Note: If a device is listed as "Disabled" in the 'Service' column, then DHCP services are not being provided to hosts connected to the network through that device. This means that the device does not assign IP addresses to these computers, which is useful if you wish to work with static IP addresses only.
  • Page 570 Mediant 800 MSBR computer. This feature ensures that IP addresses that are not in use become available for other computers on the network. • Provide Host Name If Not Specified by Client: If the DHCP client does not have a host name, the device automatically assigns one. •...
  • Page 571 User's Manual 44. Data Services You can also view a list of computers currently recognized by the DHCP server:  To view a list of computers currently recognized by the DHCP server and to add a new computer with a static IP address: Click the DHCP Server item (Configuration tab >...
  • Page 572 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 573: Data Routing

    User's Manual 45. Data Routing Data Routing The Data Routing submenu allows you to configure the device's routing rules, and includes the following items:  General Routing (see 'Configuring General Routing Settings' on page 573)  Dynamic Routing (see 'Configuring Dynamic Routing' on page 576) 45.1 Configuring General Routing You can choose to setup your device to use static or dynamic routing.
  • Page 574 Mediant 800 MSBR ♦ Netmask: network mask is used in conjunction with the destination to determine when a route is used. ♦ Gateway: enter the device's IP address. ♦ Metric: measurement of a route's preference. Typically, the lowest metric is the most preferred route.
  • Page 575 User's Manual 45. Data Routing To add a DSCP-based policy route: Under the 'DSCP-Based Policy Routing' group, click the New Route link; the following page appears: Figure 45-5: Adding DSCP-Based Route From the 'Device' drop-down list, select the network device. In the 'DSCP' field, specify the DSCP value.

  • Page 576: Configuring Dynamic Routing

    Mediant 800 MSBR To enable Internet Group Management Protocol (IGMP) multicasting: Under the 'Internet Group Management Protocol (IGMP)' group, select the 'Enabled' check box. When a host sends a request to join a multicast group, the device listens and intercept the group's traffic, forwarding it to the subscribed host.
  • Page 577 User's Manual 45. Data Routing  To configure dynamic routing: Click the Dynamic Routing item (Configuration tab > Data menu > Data Routing submenu > Dynamic Routing); the following page appears: Figure 45-7: Page Displaying Area for Configuration File Create a configuration file for the protocol daemon and also for Zebra. Zebra is Quagga's IP routing management daemon which provides kernel routing table updates, interface lookups, and redistribution of routes between the routing protocols.
  • Page 578 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 579: Objects And Rules

    User's Manual 46. Objects and Rules Objects and Rules The Objects and Rules submenu allows you to configure objects and rules. Once defined, they can later be used in other configurations (e.g., in Access List rules). This submenu includes the following items: ...

  • Page 580: Configuring Network Objects

    Mediant 800 MSBR Click the New Server Ports link; the following page appears: Figure 46-3: Defining Service Server Ports From the 'Protocol' drop-down list, select any of the protocols available, or add a new one by selecting Other. Enter the relevant information, and then click OK to save the settings. 46.2 Configuring Network Objects Network Objects is a method used to logically define a set of LAN hosts according to...
  • Page 581 User's Manual 46. Objects and Rules Click the New Entry link; the following page appears: Figure 46-6: Defining Network Object Type From the 'Network Object Type' drop-down list, select a network object type; the page displays the respective fields for entering the relevant information. The group definition can be according to one of the following: •...
  • Page 582 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 583: Configuring Network Connections

    User's Manual 47. Configuring Network Connections Configuring Network Connections The device supports various network connections, both physical and logical. The Data System > Connections item enables you to configure the various parameters for your physical connections, the LAN and WAN, and create new connections, using tunneling protocols over existing connections such as PPP and VPN.

  • Page 584: Network Connection Wizard

    Mediant 800 MSBR  To access the Network Connection list table:  Click the Connections item (Configuration tab > Data menu > Data System submenu > Connections); the following page appears: Figure 47-1: Configuring Network Connections The page displays the configured WAN and LAN connections: ...
  • Page 585 User's Manual 47. Configuring Network Connections Select the Internet Connection option, and then click Next; the following wizard page appears: Figure 47-3: Defining Internet Connection Type Select the required Internet connection type, click Next, and then follow the instructions provided by the wizard. The tree-like structure of the Internet Connection options are shown below: Figure 47-4: Internet Connection Types ♦...
  • Page 586 Mediant 800 MSBR • For configuring a VPN-over-Internet connection: Select the Connect to a Virtual Private Network over the Internet option, and then click Next; the following wizard page appears: Figure 47-5: Defining Virtual Private Network over Internet Select the VPN connection type, click Next, and then follow the instructions provided by the wizard.
  • Page 587 User's Manual 47. Configuring Network Connections • For manually configuring a new connection: Select the Advanced Connection option, and then click Next; the following wizard page appears: Select the required connection type, click Next, and then follow the instructions provided by the wizard. Version 6.6 Mediant 800 MSBR...

  • Page 588: Lan Switch

    Mediant 800 MSBR The Advanced Connection wizard tree is illustrated below: Figure 47-7: Advanced Connection Wizard Tree When the wizard completes the initial configuration (by clicking Finish), the new connection type appears listed in the Network Connections page. 47.2 LAN Switch The LAN Switch interface represents all the device's ports.
  • Page 589 User's Manual 47. Configuring Network Connections that arrive at a port are tagged with the VLAN number that appears under the PVID (Port VLAN Identifier) column. Figure 47-9: Switch Tab You can edit the configuration of each port by clicking the corresponding Edit icon.

  • Page 590: Wan Ethernet

    Mediant 800 MSBR Select the 'STP' check box to enable the Spanning Tree Protocol on the device. You should use this to ensure that there are no loops in your network configuration, and apply these settings in case your network consists of multiple switches, or other bridges apart from those created by the device.

  • Page 591: Manual Wan Ip Address

    User's Manual 47. Configuring Network Connections  To configure a DHCP connection: In the Connections page, click the New icon; the Connection Wizard opens. Select the Internet Connection option, and then click Next; the Internet connection options are displayed. Select the Ethernet Connection option, and then click Next; the following page appears.

  • Page 592: Point-To-Point Protocol Over Ethernet (Pppoe)

    Mediant 800 MSBR Figure 47-15: Selecting Internet Ethernet Connection Select the Manual IP Address Configuration option, and then click Next; a summary of the new connection is shown. Figure 47-16: Manual IP Address Configuration Enter the IP address, subnet mask, default gateway, and DNS server addresses in their respective fields.
  • Page 593 User's Manual 47. Configuring Network Connections Select the Point-to-Point Protocol over Ethernet (PPPoE) option, and then click Next. Figure 47-18: Selecting Underlying Device Select the underlying device for which you want to create the connection, and then click Next. Figure 47-19: Defining PPPoE Properties In the 'Login User Name' and 'Login Password' fields, enter the PPPoE username and password provided by your ISP, and then click Next;...
  • Page 594 Mediant 800 MSBR • PPP Authentication: PPP currently supports four authentication protocols: Password Authentication Protocol (PAP), Challenge Handshake Authentication Protocol (CHAP), and Microsoft CHAP version 1 and 2. Select the authentication protocols that the device may use when negotiating with a PPP server. Select all the protocols if no information is available about the server's authentication protocols.

  • Page 595: Cellular 3G

    User's Manual 47. Configuring Network Connections 47.3.4 Cellular 3G The device supports a 3G cellular WAN connection, using a USB modem. For more information regarding this support, see 'Configuring 3G/3.5G Cellular WAN Access' on page 541.  To create a 3G cellular connection: In the Connections page, click the New icon;...

  • Page 596: Lan-Wan Bridge

    Mediant 800 MSBR  To create a LAN bridge: In the Connections page, click the New icon; the Connection Wizard opens. Select the Advanced Connection option, and then click Next; the Advanced Connection page appears. Select the Network Bridging option, and then click Next; the following page appears. Figure 47-22: Selecting LAN Interfaces for Bridge Connection Add new connections or remove existing ones, by selecting or clearing their respective check boxes.

  • Page 597: Virtual Lan Interface (Vlan)

    User's Manual 47. Configuring Network Connections 47.6 Virtual LAN Interface (VLAN) A virtual LAN interface enables you to group workstations together into one broadcast domain, even if they are not located on the same LAN segment. The device allows you to create virtual Ethernet-based networks according to the IEEE 802.1Q standard.
  • Page 598 Mediant 800 MSBR Note: If the created virtual network is intended for VLAN-unaware hosts, it is recommended that you select the 'Untagged' option. In the 'VLAN Ports' group, select the LAN bridge ports on which you want to enable the VLAN. Click Next;...

  • Page 599: Layer 2 Tunneling Protocol (L2Tp)

    User's Manual 47. Configuring Network Connections Map the required 802.1p CoS value to a DSCP value, and then click OK; the new value pair appears in the table. Click OK to save the settings. 47.7 Layer 2 Tunneling Protocol (L2TP) Layer 2 Tunneling Protocol (L2TP) is an extension to the PPP protocol, enabling your device to create VPN connections.
  • Page 600 Mediant 800 MSBR The following procedure describes how to create a L2TP VPN connection.  To create a L2TP VPN connection: In the Connections page, click the New icon; the Connection Wizard opens. Select the Connect to a Virtual Private Network over the Internet option, and then click Next.
  • Page 601 User's Manual 47. Configuring Network Connections Click Next; the following is displayed if successfully configured: Figure 47-34: L2TP Successfully Added Select the 'Edit the Newly Created Connection' check box if you want to edit the new connection after clicking Finish. Click Finish to save the settings;...
  • Page 602 Mediant 800 MSBR • PPP Authentication: PPP currently supports four authentication protocols: Password Authentication Protocol (PAP), Challenge Handshake Authentication Protocol (CHAP), and Microsoft CHAP version 1 and 2. Select the authentication protocols that the device may use when negotiating with a PPP server. Select all the protocols if no information is available about the server's authentication protocols.

  • Page 603: Layer 2 Tunneling Protocol Server (L2Tp Server)

    User's Manual 47. Configuring Network Connections 47.8 Layer 2 Tunneling Protocol Server (L2TP Server) The device can act as a Layer 2 Tunneling Protocol Server (L2TP Server), accepting L2TP client connection requests.  To create an L2TP server: In the Connections page, click the New icon;...

  • Page 604: Internet Protocol Security (Ipsec)

    Mediant 800 MSBR option to disable L2TP protection by IPSec. Click Next; the following is displayed if successfully configured: Figure 47-40: L2TP Server Added Successfully Note that the attention message alerting that there are no users with VPN permissions. Select the 'Edit the Newly Created Connection' check box, and then click Finish. Figure 47-41: Defining Advanced L2TP Properties Click the Click here to create VPN users link to define remote users that will be granted access to your home network.
  • Page 605 User's Manual 47. Configuring Network Connections Figure 47-42: Selecting VPN Type for IPSec Select the VPN Client or Point-To-Point option, and then click Next. Figure 47-43: Selecting IPSec Select the Internet Protocol Security Server (IPSec) option, and then click Next. Figure 47-44: Defining IPSec Properties In the 'Host Name or IP Address of Destination Gateway' field, enter the host or IP address of the destination gateway.
  • Page 606 Mediant 800 MSBR • IP Range – 'From IP Address' and 'To IP Address' fields appear. Specify the IP range. In the 'Shared Secret' field, enter the IPSec shared secret, which is the encryption key jointly decided upon with the network you are trying to access. Click Next;...
  • Page 607 User's Manual 47. Configuring Network Connections • Encapsulation Type: Select between 'Tunneling' or 'Transport' encapsulation. 'Transport' encapsulation is performed between two gateways (no subnets), and therefore needs no explicit configuration. 'Tunneling' requires that you configure the following parameters: ♦ Local Subnet: Define your local endpoint, by selecting one of the following options: ...
  • Page 608 Mediant 800 MSBR ♦ IPSec Automatic Phase 1 – Peer Authentication: Figure 47-47: IPSec Tab - IPSec Automatic Phase 1  Mode: Select the IPSec mode – either 'Main Mode' or 'Aggressive Mode'. Main mode is a secured but slower mode, which presents negotiable propositions according to the authentication algorithms that you select in the check boxes.
  • Page 609 User's Manual 47. Configuring Network Connections  Group Description Attribute: Select the Diffie-Hellman (DH) group description(s). Diffie-Hellman is a public-key cryptography scheme that allows two parties to establish a shared secret over an insecure communications channel. ♦ IPSec Automatic Phase 2 – Key Definition: Figure 47-48: IPSec Tab - IPSec Automatic Phase 2 ...

  • Page 610: Internet Protocol Security Server (Ipsec Server)

    Mediant 800 MSBR  Security Parameter Index (SPI): A 32 bit value that together with an IP address and a security protocol, uniquely identifies a particular security association. The local and remote values must be coordinated with their respective values on the IPSec peer. ...

  • Page 611: General Routing Encapsulation (Gre)

    User's Manual 47. Configuring Network Connections Figure 47-52: IPSec Shared Secret Key Enter the IPSec shared secret, which is the encryption key jointly decided upon with the network you are trying to access, and then click Next; the following is displayed if successfully configured: Figure 47-53: IPSec Connection Added Successfully Select the 'Edit the Newly Created Connection' check box if you want to edit the new...

  • Page 612: Gre Example Scenario

    Mediant 800 MSBR Figure 47-55: GRE Connection Successfully Added Select the 'Edit the Connection' check box if you want to edit the new connection after clicking Finish. Click Finish to save the settings; the new GRE tunnel is added to the network connections list.
  • Page 613 User's Manual 47. Configuring Network Connections Figure 47-57: Example Scenario Setup To create a tunnel, each MSBR device must be made aware of the other's WAN IP address (the information must be exchanged).  To configure a GRE tunnel: Create a GRE tunnel for device "A": In the Connections page, click the New icon.

  • Page 614: Editing Existing Connections

    Mediant 800 MSBR Figure 47-59: Defining GRE Tunnel for Device B Enter 10.71.81.191 as the tunnel's remote endpoint IP address. Enter 192.168.30.100 as the local interface IP address. Enter 192.168.1.0 as the IP address of the remote network that will be accessed via the tunnel, and 255.255.255.0 as the subnet mask.
  • Page 615 User's Manual 47. Configuring Network Connections Select the Settings tab: Figure 47-61: Editing Network Connection - Settings Tab • Network: select whether the parameters you are configuring relate to a WAN, LAN or DMZ connection. • Physical Address: physical address of the network card used for your network. Some cards allow you to change this address.
  • Page 616 Mediant 800 MSBR such an IP address and subnet mask. • DNS Server: Domain Name System (DNS) is the method by which Web site domain names are translated into IP addresses: ♦ Obtain DNS Server Address Automatically - configure the connection to automatically obtain a DNS server address, or specify such an address manually, according to the information provided by your ISP.
  • Page 617 User's Manual 47. Configuring Network Connections Select the Advanced tab: Figure 47-63: Editing Network Connection - Advanced Tab • Internet Connection Firewall: Your device's firewall helps protect your computer by preventing unauthorized users from gaining access to it through a network such as the Internet.
  • Page 618 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 619: Maintenance

    Part XI Maintenance...

  • Page 621: Basic Maintenance

    User's Manual 48. Basic Maintenance Basic Maintenance The Maintenance Actions page allows you to perform the following:  Reset the device - see 'Resetting the Device' on page  Lock and unlock the device - see 'Locking and Unlocking the Device' on page ...

  • Page 622: Remotely Resetting Device Using Sip Notify

    Mediant 800 MSBR  To reset the device: Open the Maintenance Actions page (see 'Basic Maintenance' on page 621). 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 623: 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. 48.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 624: Saving Configuration

    Mediant 800 MSBR  To unlock the device: Open the Maintenance Actions page (see 'Maintenance Actions' on page 621). Under the 'LOCK / UNLOCK' group, click the UNLOCK button. Unlock starts immediately and the device accepts new incoming calls. Note: The Home page's General Information pane displays whether the device is locked or unlocked (see 'Viewing the Home Page' on page 60).

  • Page 625: Resetting Channels

    User's Manual 49. Resetting Channels Resetting Channels 49.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 626 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 627: Software Upgrade

    User's Manual 50. Software Upgrade Software Upgrade The Software Update menu allows you to do the following:  Load Auxiliary files (see 'Loading Auxiliary Files' on page 627)  Load a Software License Key (see 'Software License Key' on page 644) ...
  • Page 628 Mediant 800 MSBR Notes: • You can schedule automatic loading of updated auxiliary files using HTTP/HTTPS. For more information on automatic updates, see 'Automatic Update' on page 655. • When loading an ini file using this Web page, parameters that are excluded from the loaded ini file retain their current settings (incremental).

  • Page 629: 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 630 Mediant 800 MSBR ♦ [3] Busy Tone ♦ [4] Congestion Tone ♦ [6] Warning Tone ♦ [7] Reorder Tone ♦ [8] Confirmation Tone ♦ [9] Call Waiting Tone - heard by the called party ♦ [15] Stutter Dial Tone ♦ [16] Off Hook Warning Tone ♦...

  • Page 631: Distinctive Ringing

    User's Manual 50. Software Upgrade • Signal Level [-dBm]: Level of the tone for AM tones. • AM Factor [steps of 0.02]: Amplitude modulation factor (valid range from 1 to 50). Recommended values from 10 to 25. Notes: • When the same frequency is used for a continuous tone and a cadence tone, the 'Signal On Time' parameter of the continuous tone must have a value that is greater than the 'Signal On Time' parameter of the cadence tone.
  • Page 632 Mediant 800 MSBR  [Ringing Pattern #X]: Contains the Xth ringing pattern definition (starting from 0 and not exceeding the number of Distinctive Ringing patterns defined in the first section minus 1) using the following keys: • Ring Type: Must be equal to the Ringing Pattern number. •...

  • Page 633: Cas Files

    User's Manual 50. Software Upgrade #GR-506-CORE Ringing Pattern 1 [Ringing Pattern #1] Ring Type=1 Freq [Hz]=20 First Ring On Time [10msec]=200 First Ring Off Time [10msec]=400 #GR-506-CORE Ringing Pattern 2 [Ringing Pattern #2] Ring Type=2 Freq [Hz]=20 First Ring On Time [10msec]=80 First Ring Off Time [10msec]=40 Second Ring On Time [10msec]=80 Second Ring Off Time [10msec]=400...

  • Page 634: Dialing Plans For Digit Collection

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

  • Page 636: Dial Plan Prefix Tags For Ip-To-Tel Routing

    Mediant 800 MSBR Notes: • The Dial Plan file must not contain overlapping prefixes. Attempting to process an overlapping configuration by the DConvert utility results in an error message specifying the problematic line. • The Dial Plan index can be selected globally for all calls (as described in the previous procedure), or per specific calls using Tel Profiles.
  • Page 637 User's Manual 50. Software Upgrade The example configuration below assumes a scenario where multiple prefixes exist for local and long distance calls:  To use Dial Plan file routing tags: Load an ini file to the device that selects Dial Plan index (e.g., 1) for routing tags, as shown below: IP2TelTaggingDestDialPlanIndex = 0 Define the external Dial Plan file with two routing tags (as shown below):...

  • Page 638: Obtaining Ip Destination From Dial Plan File

    Mediant 800 MSBR 50.1.3.4 Obtaining IP Destination from Dial Plan File You can use a Dial Plan index listed in a loaded Dial Plan file for determining the IP destination of Tel-to-IP /IP-to-IP calls and SBC calls. This enables the mapping of called numbers to IP addresses (in dotted-decimal notation) or FQDNs (up to 15 characters).

  • Page 639: User Information File

    'UserInformationFile.txt' (see 'Auxiliary and Configuration File Name Parameters' on page 988)  Automatic update mechanism - using the UserInfoFileURL parameter, e.g., UserInfoFileUrl = 'http://192.168.0.250/Audiocodes/ UserInformationFile.txt' (see 'Automatic Update' on page 655) Note: Instead of using a User Info file, you can configure the User Info table using the CLI, as described in 'Configuring User Info Table using CLI' on page 642.

  • Page 640: User Information File For Pbx Extensions And "Global" Numbers

    Mediant 800 MSBR 50.1.4.1 User Information File for PBX Extensions and "Global" Numbers The User Info file contains a User Info table that can be used for the following Gateway- related:  Mapping (Manipulating) PBX Extension Numbers with Global Phone Numbers: maps PBX extension number, connected to the device, with any "global"...

  • Page 641: User Information File For Sbc User Database

    User's Manual 50. Software Upgrade √ 'Enable Registration' parameter set to Enable (IsRegisterNeeded is set to √ 'Registration Mode' parameter set to Per Endpoint (AuthenticationMode is set to 0). • For FXS ports, when the device needs to send a new SIP request with the Authorization header (e.g., after receiving a SIP 401 response), it uses the username and password configured in the Authentication table (see 'Configuring Authentication per Port' on page 401).

  • Page 642: Configuring User Info Table Using Cli

    Mediant 800 MSBR  Registering each user to an external registrar server.  Authenticating (for any SIP request and as a client) each user if challenged by an external server.  Authenticating as a server incoming user requests (for SBC security). If the device registers on behalf of users and the users do not perform registration, any SIP request destined to the user is routed to the Proxy Set associated with the user’s IP Group.

  • Page 643: Enabling The User Info Table

    User's Manual 50. Software Upgrade username (userJohn) password (s3fn+fn=) ip-group-id (1) status (not-resgistered) ---- sbc-user-info-1 ---- local-user (SuePark) username (userSue) password (t6sn+un=) ip-group-id (1) status (not-resgistered) • Gateway: (sip-def-proxy-and-reg)# user-info gw-user-info display ---- gw-user-info-0 ---- pbx-ext (405) global-phone-num (405) display-name (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered)

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

    CLI – see 'Installing the Software License Key using CLI' on page  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non-volatile flash memory and overwrites the previously installed Software License Key.
  • Page 646 Mediant 800 MSBR As a precaution, backup the Software License Key currently installed on the device. If the new Software License Key does not comply with your requirements, you can re- load this backup to restore the device's original capabilities. In the 'Current Key' field, select the entire text string and copy it to any standard text file (e.g., Notepad).

  • Page 647: Installing The 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 648: Software Upgrade Wizard

    (see 'Basic Maintenance' on page 621). Notes: • You can get the latest software files from AudioCodes Web site at http://www.audiocodes.com/downloads. • Before upgrading the device, it is recommended that you save a copy of the device's configuration settings (i.e., ini file and data file) to your...
  • Page 649 User's Manual 50. Software Upgrade  To load files using the Software Upgrade Wizard: Stop all traffic on the device using the Graceful Lock feature (refer to the warning bulletin above). Open the Software Upgrade wizard, by performing one of the following: •...
  • Page 650 Mediant 800 MSBR • Load a new ini file: Click Browse, navigate to the ini file, and then click Send File; the ini file is loaded to the device and you're notified as to a successful loading. • Retain the existing configuration (ini file): Do not select an ini file, and ensure that the 'Use existing configuration' check box is selected (default).

  • Page 651: Backing Up And Loading Configuration File

    User's Manual 50. Software Upgrade Click OK; the Web interface becomes active, reflecting the upgraded device. 50.4 Backing Up and Loading Configuration File You can save a copy/backup of the device's current configuration settings as an ini file to a folder on your computer, using the Configuration File page.
  • Page 652 Mediant 800 MSBR Click the Save button, navigate to the folder in which you want to save the file on your PC, and then click Save; the device saves the Data ini file to the selected folder. User's Manual Document #: LTRT-12809...
  • Page 653 User's Manual 50. Software Upgrade To load the Voice ini file to the device, do the following: Click the Browse button, navigate to the folder where the ini file is located, select the file, and then click Open; the name and path of the file appear in the field beside the Browse button.
  • Page 654 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 655: Automatic Update

    User's Manual 51. Automatic Update Automatic Update 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. Configuration may occur at the staging warehouse or at the end-customer premises.

  • Page 656: Configuring Automatic Update

    Mediant 800 MSBR  Periodically (e.g., every 60 minutes), configured by the ini file parameter AutoUpdateFrequency.  Upon startup but before the device is operational, if the Secure Startup feature is enabled (see 'Loading Files Securely by Disabling TFTP' on page 660). ...
  • Page 657 User's Manual 51. Automatic Update Create a file named master_configuration.ini with the following text: # Common configuration for all devices # ------------------------------------ CptFileURL = 'http://www.corp.com/call_progress.dat' # Check for updates every 60 minutes AutoUpdateFrequency = 60 # Additional configuration per device # ----------------------------------- # Each device loads a file named based on its MAC address # (e.g., config_00908F033512.ini)

  • Page 658: Obtaining Ip Address Automatically Using Dhcp

    Mediant 800 MSBR # Note: The cmp file isn’t updated since it's disabled by default (AutoUpdateCmpFile). Notes: • The Automatic Update mechanism assumes that the external Web server conforms to the HTTP standard. If the Web server ignores the If- Modified-Since header, or doesn’t provide the current date and time during the HTTP 200 OK response, the device may reset itself repeatedly.

  • Page 659: Automatic Configuration Methods

    60; max-lease-time 60; class "gateways" { match if(substring(hardware, 1, 3) = 00:90:8f); subnet 10.31.0.0 netmask 255.255.0.0 { pool { allow members of "audiocodes"; range 10.31.4.53 10.31.4.75; filename "SIP_F6.60A.217.003.cmp –fb;device.ini"; option routers 10.31.0.1; option subnet-mask 255.255.0.0; 51.3.2 HTTP-based Automatic Updates An HTTP/S server can be placed in the customer's network where configuration and software updates are available for download.

  • Page 660: Configuration Using Ftp Or Nfs

    NFS v2/v3 is also supported. 51.3.4 Configuration using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections. As soon as a registered device contacts the EMS server through SNMP, the EMS server handles all required configuration automatically, upgrading software as needed.

  • Page 661: Remotely Triggering Auto Update Using Sip Notify

    Under the Misc Parameters group, set the 'SIP Remote Reset' parameter to Enable. Click Submit. Notes: • This SIP Event header value is proprietary to AudioCodes. • This feature does not trigger the Zero Configuration feature. Version 6.6 Mediant 800 MSBR...

  • Page 662: Configuring Zero Configuration

    Once the device is powered up and connectivity to the WAN established, it automatically sends an HTTP request to AudioCodes HTTPS Redirect server. If the device's MAC address is listed on the server, the server responds to the device with an HTTP Redirect response containing the URL of the HTTP/S server (typically, a provisioning server maintained by the Service Provider) where the configuration file is located.
  • Page 663 Web interface or through SOAP/XML interface (that may be integrated with the Service Provider’s provisioning system). For more information, contact AudioCodes support. If the regular Automatic Update process succeeds, the device repeats the Zero Configuration process only if it undergoes a reset to factory defaults.
  • Page 664 Enable Zero Configuration (default), by running the following command: # configure system (config-system># automatic-update (automatic-update)# set zero-conf <on|off> Configure the URL of AudioCodes HTTPS Redirect server, by running the following command: (automatic-update)# set zero-conf-server <URL> The default URL is https://redirect.audiocodes.com/<MAC address>.

  • Page 665: Restoring Factory Defaults

    User's Manual 52. 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 665)  Hardware reset pinhole button (see Restoring Defaults using Hardware Reset Button on page 666) ...

  • Page 666: Restoring Defaults Using Hardware Reset Button

    Mediant 800 MSBR 52.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 667: Usb Storage Capabilities

    User's Manual 53. USB Storage Capabilities USB Storage Capabilities The device enables USB storage using an external USB hard drive or flash disk (disk on key) connected to its USB port. The storage capabilities include the following:  Saving network captures to the USB, using the following CLI command: # debug capture data physical stop usb ...
  • Page 668 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 669: Status, Performance Monitoring And Reporting

    Part XII Status, Performance Monitoring and Reporting...

  • Page 671: System Status

    User's Manual 54. System Status System Status This section describes how to view various system statuses. 54.1 Viewing Device Information The Device Information page displays various hardware and software information of the device. This page also lists any Auxiliary files that have been installed on the device and allows you to remove them.
  • Page 672 Mediant 800 MSBR  To view Ethernet port information:  Open the Ethernet Port Information page (Status & Diagnostics tab > System Status menu > Ethernet Port Information). Ethernet Port Information Parameters Parameter Description Active Displays whether the port is active or not. Speed Displays the speed (in Mbps) of the Ethernet port.

  • Page 673: Carrier-Grade Alarms

    User's Manual 55. 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  Alarm history - see 'Viewing Alarm History' on page 55.1 Viewing Active Alarms The Active Alarms page displays a list of currently active alarms.
  • Page 674 Mediant 800 MSBR For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised  Description: brief explanation of the alarm ...

  • Page 675: Performance Monitoring

    User's Manual 56. Performance Monitoring Performance Monitoring This section describes how to view performance monitoring. 56.1 Viewing MOS per Media Realm The MOS Per Media Realm page displays statistics on Media Realms (configured in 'Configuring Media Realms' on page 174). This page provides two graphs: ...

  • Page 676: Viewing Trunk Utilization

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

  • Page 677: Viewing Quality Of Experience

    User's Manual 56. Performance Monitoring For more graph functionality, see the following table: 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 678: Viewing Average Call Duration

    Mediant 800 MSBR  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 56-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 679: 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 680 You can periodically poll the device for the latest VoIP quality metrics and specify thresholds for the quality metrics mentioned above. If these thresholds are crossed, the device generates the following SNMP traps to Audiocodes EMS or third-party SNMP-based manager: ...
  • Page 681 User's Manual 56. Performance Monitoring The following procedure describes how to quickly configure network quality probing.  To configure network quality probing: Configure the "sender termination" side: Bind a WAN interface to the NQM service: (config-system) bind GigabitEthernet 0/0 nqm Note: The chosen WAN interface should be the interface on which the NQM packets are planned to flow bi-directionally and binding is necessary to create...
  • Page 682 Mediant 800 MSBR Configure the "responder termination" side: Bind a WAN interface to the NQM service: (config-system) bind GigabitEthernet 0/0 nqm Note: The chosen WAN interface should be the interface on which the NQM packets are planned to flow bi-directionally and binding is necessary to create the corresponding static NAT rules.

  • Page 683: Voip Status

    User's Manual 57. VoIP Status VoIP Status This section describes how to view VoIP status and statistics. 57.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 684: Viewing Analog Port Information

    Mediant 800 MSBR The status of the channels is depicted by color-coded icons, as described in the table below: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls Green Active Call in progress (RTP traffic) and no alarms...

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

    User's Manual 57. VoIP Status appears. From the shortcut menu, choose Port Settings; the Basic Channel Information page appears with the Basic tab selected (displayed in green): Figure 57-3: Basic Channel Information Page To view additional channel information, click the required tab - SIP, RTP/RTCP, and Voice Settings.

  • Page 686: Viewing Active Ip Interfaces

    Mediant 800 MSBR 57.4 Viewing Active IP Interfaces The IP Interface Status page displays the device's active IP interfaces that are listed in the Multiple Interface Table page (see 'Configuring IP Network Interfaces' on page 113).  To view the active IP network interfaces: ...
  • Page 687 User's Manual 57. VoIP Status  To view IP-to-Tel and Tel-to-IP call counters:  Open the Call Counters page that you want to view (Status & Diagnostics tab > VoIP Status menu > IP to Tel Calls Count or Tel to IP Calls Count); the figure below shows the IP to Tel Calls Count page.

  • Page 688: Viewing Registered Users

    Mediant 800 MSBR Counter Description Number of Calls Indicates the number of calls that weren't answered. It's incremented Terminated due to No as a result of one of the following release reasons: Answer  GWAPP_NO_USER_RESPONDING (18)  GWAPP_NO_ANSWER_FROM_USER_ALERTED (19)  GWAPP_NORMAL_CALL_CLEAR (16) (when the call duration is zero) Number of Calls...

  • Page 689: Viewing Registration Status

    User's Manual 57. VoIP Status Figure 57-7: SAS/SBC Registered Users Page SAS/SBC Registered Users Parameters Column Name Description Address of An address-of-record (AOR) is a SIP or SIPS URI that points to a domain with Record a location service that can map the URI to another URI (Contact) where the user might be available.

  • Page 690: Viewing Call Routing Status

    Mediant 800 MSBR  Accounts Registration Status: registration status based on the Accounts table (configured in 'Configuring Account Table' on page 225): • Group Type: type of served group - Trunk Group or IP Group • Group Name: name of the served group, if applicable •...

  • Page 691: Viewing Ip Connectivity

    User's Manual 57. VoIP Status Parameter Description  IP address and FQDN (if exists) of the Proxy server with which the device currently operates.  N/A = Proxy server isn't defined. State  OK = Communication with the Proxy server is in order. ...
  • Page 692 Mediant 800 MSBR Column Name Description  IP address resolved from the host name defined as the destination IP address in the Outbound IP Routing Table. Host Name Host name (or IP address) as defined in the Outbound IP Routing Table. Connectivity The method according to which the destination IP address is queried Method...

  • Page 693: Data Status

    User's Manual 58. Data Status Data Status This section describes how to view data-touter status and statistics. 58.1 Viewing WAN Status The WAN Status item allows you to view the WAN access status and Internet connection.  To view the status of the WAN connection: ...

  • Page 694: Viewing Network Connection Statistics

    Mediant 800 MSBR 58.2 Viewing Network Connection Statistics The Network Connections page displays a table summarizing the monitored connection data. The device constantly monitors traffic within the local network and between the local network and the Internet. You can view statistical information about data received from and transmitted to the Internet (WAN) and to computers in the local network (LAN).

  • Page 695: Viewing Logged Security Events

    User's Manual 58. Data Status 58.3 Viewing Logged Security Events The Security Log item displays a list of firewall-related events, including attempts to establish inbound and outbound connections, attempts to authenticate through an administrative interface (Web or Telnet terminal), firewall configuration and system start-up. ...
  • Page 696 Mediant 800 MSBR Figure 58-4: Log Settings Page • Accepted Events group: ♦ Accepted Incoming Connections: generates a log message for each successful attempt to establish an inbound connection to the home network. ♦ Accepted Outgoing Connections: generates a log message for each successful attempt to establish an outgoing connection to the public network.

  • Page 697: Viewing Qos Queues Statistics

    User's Manual 58. Data Status 58.4 Viewing QoS Queues Statistics You can view an accurate, real-time information on the traffic moving through your defined device classes. For example, the amount of packets sent, dropped or delayed are just a few of the parameters that you can monitor per shaping class. ...
  • Page 698 Mediant 800 MSBR By default, all log messages are displayed one after another, sorted by their order of posting by the device (latest on top). You can sort the messages according to the column titles 'Time', 'Component', or 'Severity', by clicking the column header. You can also filter the log messages by the component that generated them or by their severity, providing a more refined list.

  • Page 699: Reporting Information To External Party

    User's Manual 59. Reporting Information to External Party Reporting Information to External Party This section describes features for reporting various information to an external party. 59.1 RTP Control Protocol Extended Reports (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 700 Mediant 800 MSBR Group Metric Name Jitter Buffer Nominal Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Gap Loss Burst Loss Density Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold Delay Round Trip Delay End System Delay...
  • Page 701 User's Manual 59. Reporting Information to External Party  To configure RTCP XR: Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). The RTCP XR parameters are listed under the 'RTCP XR Settings' group, as shown below: Figure 59-1: RTCP XR Parameters in RTP/RTCP Settings Page Configure the RTCP XR parameters, as required: •...

  • Page 702: Generating Call Detail Records

    Mediant 800 MSBR 59.2 Generating Call Detail Records The Call Detail Record (CDR) contains vital statistic information on calls made from the device. The device can be configured to generate and report CDRs for various stages of the call, including SIP messages and/or media. You can configure when CDRs for a call are generated, for example, only at the end of the call or only at the start and end of the call.

  • Page 703: Cdr Field Description

    User's Manual 59. Reporting Information to External Party 59.2.2 CDR Field Description This section describes the CDR fields that are generated by the device. 59.2.2.1 CDR Fields for SBC Signaling The CDR fields for SBC signaling are listed in the table below. The signaling CDRs are published for each SBC leg.
  • Page 704 Mediant 800 MSBR CDR Field Name Description TrmReasonCategory Termination reason category:  Calls with duration 0 (i.e., not connected):  NO_ANSWER - GWAPP_NORMAL_CALL_CLEAR, GWAPP_NO_USER_RESPONDING, GWAPP_NO_ANSWER_FROM_USER_ALERTED  BUSY - GWAPP_USER_BUSY  NO_RESOURCES - GWAPP_RESOUUCE_UNAVAILABLE_UNSPECIFIED, RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES _LEFT, RESOURCE_BECAUSE_NO_TRANSCODING_RESOURC ES_LEFT, RELEASE_BECAUSE_GW_LOCKED  NO_MATCH - RELEASE_BECAUSE_UNMATCHED_CAPABILITIES ...

  • Page 705: 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 59.2.2.2 CDR Fields for SBC Media...

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

    Mediant 800 MSBR CDR Field Name Description OutPackets Number of sent packets LocalPackLoss Local packet loss RemotePackLoss Remote packet loss RTPdelay RTP delay RTPjitter RTP jitter TxRTPssrc Tx RTP SSRC RxRTPssrc Local RTP SSRC LocalRFactor Local conversation quality RemoteRFactor Remote conversation quality LocalMosCQ Local MOS for conversation Remote MOS for conversation...
  • Page 707 User's Manual 59. Reporting Information to External Party Field Name Description EPTyp Endpoint type:    EANDM  ISDN    IPMEDIA  NETANN  STREAMING  TRANSPARENT  MSCML  VXML  IP2IP Orig Call originator:  LCL (Tel side) ...
  • Page 708 Mediant 800 MSBR Field Name Description OutPackets Number of outgoing packets PackLoss Local packet loss Number of outgoing lost packets RemotePackLoss SIPCalld Unique SIP call ID SetupTime Call setup time ConnectTime Call connect time ReleaseTime Call release time RTPdelay RTP delay RTPjitter RTP jitter RTPssrc...
  • Page 709 User's Manual 59. Reporting Information to External Party Field Name Description TrmReasonCategory Termination reason category:  Calls with duration 0 (i.e., not connected):  NO_ANSWER - GWAPP_NORMAL_CALL_CLEAR, GWAPP_NO_USER_RESPONDING, GWAPP_NO_ANSWER_FROM_USER_ALERTED  BUSY - GWAPP_USER_BUSY  NO_RESOURCES - GWAPP_RESOUUCE_UNAVAILABLE_UNSPECIFIED, RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT, RESOURCE_BECAUSE_NO_TRANSCODING_RESOURCES_LE FT, RELEASE_BECAUSE_GW_LOCKED ...

  • Page 710: Release Reasons In Cdr

    Mediant 800 MSBR 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 Unknown Resource-Priority".
  • Page 711 User's Manual 59. Reporting Information to External Party  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED"...
  • Page 712 Mediant 800 MSBR  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST"  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED"  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING"  "GWAPP_MESSAGE_TYPE_NON_EXISTENT"  "GWAPP_MESSAGE_STATE_INCONSISTENCY"...

  • Page 713: Configuring Radius Accounting

    User's Manual 59. Reporting Information to External Party 59.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.
  • Page 714 Mediant 800 MSBR Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. h323-remote- IP address of the Numeric Stop Acc address remote gateway h323-conf-id H.323/SIP call Up to 32 Start Acc identifier octets Stop Acc h323-setup- Setup time in NTP String Start Acc...
  • Page 715 User's Manual 59. Reporting Information to External Party Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. acct-delay- No. of seconds tried Numeric Start Acc time in sending a particular Stop Acc record acct-input- Number of octets Numeric Stop Acc octets...

  • Page 716: Querying Device Channel Resources Using Sip Options

    Mediant 800 MSBR called-station-id = 201 calling-station-id = 202 // Accounting non-standard parameters: (4923 33) h323-gw-id = (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 59.4...

  • Page 717: Diagnostics

    Part XIII Diagnostics...

  • Page 719: Syslog And Debug Recordings

    User's Manual 60. 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 720: Event Representation In Syslog Messages

    Mediant 800 MSBR Message Item Description (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14.
  • Page 721 User's Manual 60. Syslog and Debug Recordings The table below lists these unique event abbreviations: 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 Simple Aggregation Packets Lost Command Checksum Error...

  • Page 722: 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 60.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 723: Snmp Alarms In Syslog Messages

    If additional information exists in the alarm, then these are also added: Additional Info1:/ Additional Info2:/ Additional Info3 The Messages’ Severity is as follows: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) RecoverableMsg Critical Major RecoverableMsg...

  • Page 724: Configuring Debug Recording

    Mediant 800 MSBR  To configure Syslog : Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Figure 60-1: Syslog Settings Page Enable the Syslog feature by setting the 'Enable Syslog' to Enable. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port' parameters.

  • Page 725: Filtering Syslog Messages And Debug Recordings

    User's Manual 60. Syslog and Debug Recordings  To configure and activate debug recording: Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings). Figure 60-2: Logging Settings Page Configure the debug capturing server using the 'Debug Recording Destination IP' and 'Debug Recording Destination Port' parameters.
  • Page 726 Mediant 800 MSBR Notes: • To configure the Syslog debug level, use the 'Debug Level' parameter (see 'Configuring Syslog' on page 723). • The Logging Filters table can also be configured using the table ini file parameter, LoggingFilters or the CLI command configure system > logging >...

  • Page 727: Filtering Ip Network Traces

    User's Manual 60. Syslog and Debug Recordings Parameter Description Value Defines the value of the selected filtering type in the 'Filter Type' parameter. CLI: value The value can be the following: [LoggingFilters_Val  A single value  A range, using a hyphen "-" between the two values, e.g., "1-3" ...

  • Page 728: Viewing Syslog Messages

    You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting. User's Manual Document #: LTRT-12809...
  • Page 729 User's Manual 60. Syslog and Debug Recordings  To activate the Web interface's Message Log: Enable Syslog (see 'Configuring Syslog' on page 723). Open the Message Log page (Status & Diagnostics tab > System Status menu > Message Log); the Message Log page is displayed and the log is activated. Figure 60-4: Message Log Page The displayed logged messages are color-coded as follows: •...

  • Page 730: Collecting Debug Recording Messages

    Mediant 800 MSBR 60.6 Collecting Debug Recording Messages To collect debug recording packets, the open source program Wireshark is used. AudioCodes proprietary plug-in files for Wireshark, which are shipped in your software kit, are also required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...
  • Page 731 User's Manual 60. 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 732: Capturing Voip And Data-Router Network 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 733: Self-Testing

    User's Manual 61. 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 734 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 735: Analog Line Testing

    User's Manual 62. Analog Line Testing Analog Line Testing The device can test the telephone lines connected to its FXS and FXO ports, using the SNMP acAnalogFxsLineTestTable table acAnalogFxoLineTestTable table respectively. These tests provide various line measurements. In addition to these tests (detailed below), a keep-alive test is also done every 100 msec on each of the analog ports to detect communication problems with the analog equipment and overheating of the FXS ports.
  • Page 736 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 737: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. This maximum can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. • The Test Call Endpoint table can also be configured using the table ini file parameter Test_Call (see 'SIP Test Call Parameters' on page 773) or CLI command, configure system >...
  • Page 738 Mediant 800 MSBR description of these parameters. Click Submit to apply your settings. Test Call Table Parameters Parameter Description General Tab Endpoint URI Defines the endpoint's URI. This can be defined as a user or user@host. [Test_Call_Endpoin The device identifies this endpoint only by the URI's user part. The URI's tURI] host part is used in the SIP From header in REGISTER requests.
  • Page 739 User's Manual 63. Testing SIP Signaling Calls Parameter Description Application Type Defines the application type for the endpoint. This, in effect, associates the [Test_Call_Applicat IP Group and SRD to a specific SIP interface. ionType]  [0] GW & IP2IP (default) CLI: application-type ...

  • Page 740: Starting, Stopping And Restarting Test Calls

    Mediant 800 MSBR Parameter Description Test Mode Defines the test session mode. [Test_Call_TestMo  [0] Once = (Default) The test runs until the lowest value between the following is reached: CLI: test-mode  Maximum channels is reached for the test session, configured by 'Maximum Channels for Session'.

  • Page 741: Viewing Test Call Statistics

    User's Manual 63. Testing SIP Signaling Calls The status of the test call is displayed in the 'Test Status' field of the Test Call table:  "Idle": test call is not active.  "Scheduled": test call is planned to run (according to 'Schedule Interval' parameter settings) ...

  • Page 742: Configuring Dtmf Tones For Test Calls

    Mediant 800 MSBR  Remote Disconnections Count: Number of calls that were disconnected by the remote side.  Average CPS: The average calls per second.  Test Status: Displays the status (brief description) as displayed in the 'Test Status' field (see 'Starting, Stopping and Restarting Test Calls' on page 740). ...

  • Page 743: Configuring Basic Test Call

    User's Manual 63. Testing SIP Signaling Calls  To configure the played DTMF signal to answered test call: Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 63-3: Test Call Settings Page In the 'Test Call DTMF String' field, enter the DTMF string (up to 15 digits).

  • Page 744: Configuring Sbc Test Call With External Proxy

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

  • Page 745: Test Call Configuration Examples

    User's Manual 63. Testing SIP Signaling Calls  To configure SBC call testing: Configure the test call parameters: Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 63-7: Test Call Settings Page In the 'Test Call ID' field, enter a prefix number for the simulated test endpoint on the device.
  • Page 746 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 747 User's Manual 63. Testing SIP Signaling Calls • Test Call table configuration at Device B: ♦ Endpoint URI: "201" ♦ Call Party: Caller ♦ Maximum Channels for Session: "3" (this setting configures three endpoints - "201", "202" and "203)  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and password) process of a simulated test endpoint on the device with an external proxy/registrar server.
  • Page 748 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 749: Running Data-Router Diagnostic Tests

    User's Manual 64. Running Data-Router Diagnostic Tests Running Data-Router Diagnostic Tests The Diagnostics item can assist you in testing network connectivity and viewing statistics such as the number of packets transmitted and received, round-trip time and success status. This page allows you to run network connectivity tests (ping), query the physical address (MAC) of a host, and run a trace route test.
  • Page 750 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 751: Appendix

    Part XIV Appendix...

  • Page 753: Dialing Plan Notation For Routing And Manipulation

    User's Manual 65. 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 754 Mediant 800 MSBR Notation Description Notes:  The value n must be less than the value m.  Only numerical ranges are supported (not alphabetical letters).  For suffix ranges, the starting (n) and ending (m) numbers in the range must have the same number of digits.

  • Page 755: Configuration Parameters Reference

    User's Manual 66. 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. Notes: Parameters and values enclosed in square brackets [...] represent the ini file parameters and their enumeration values.

  • Page 756: Routing Parameters

    Mediant 800 MSBR 66.1.2 Routing Parameters The IP network routing parameters are described in the table below. IP Network Routing Parameters Parameter Description Static IP Routing Table Web/EMS: IP Routing Defines up to 30 static VoIP IP routing rules for the device. These rules Table can be associated with IP interfaces defined in the Multiple Interface CLI: configure voip >...

  • Page 757: Nat And Stun Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description  For this parameter to take effect, a device reset is required.  For a description of this table, see Configuring Quality of Service on page Layer-3 Class of Service (TOS/DiffServ) Parameters Web: Media Premium Defines the DiffServ value for Premium Media CoS content.

  • Page 758: Nfs Parameters

    Mediant 800 MSBR Parameter Description [StaticNatIP] Web/EMS: Inbound Media Enables the receipt of media streams whose IP address/port are not Latch Mode configured for the channel. CLI: inbound-media-latch-  [0] Strict = Accepts only the media stream configured for the mode channel.

  • Page 759: Dns Parameters

    User's Manual 66. Configuration Parameters Reference 66.1.6 DNS Parameters The Domain name System (DNS) parameters are described in the table below. 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 760: Ntp And Daylight Saving Time Parameters

    Mediant 800 MSBR Parameter Description  For this parameter to take effect, a device reset is required.  After you enable the DHCP server, do the following: Enable DHCP and save the configuration. Perform a cold reset using the device's hardware reset button (soft reset using the Web interface doesn't trigger the DHCP procedure and this parameter reverts to 'Disable').

  • Page 761: Power Over Ethernet Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description Daylight Saving Time Parameters Web: Day Light Saving Enables daylight saving time. Time  [0] Disable (default) EMS: Mode  [1] Enable CLI: summer-time [DayLightSavingTimeEn able] Web: Start Time or Day of Defines the date and time when daylight saving begins.

  • Page 762: Management Parameters

    Mediant 800 MSBR Parameter Description [ \POETable ] Where:  Index = Port number (where 0 is Port 1)  PortEnable = enables [1] or disables [0] IEEE 802.3af-2003 PoE  PortPower = defines maximum power consumption Note: For a description of this parameter, see 'Configuring Power over Ethernet' on page 109.

  • Page 763: Web Parameters

    User's Manual 66. Configuration Parameters Reference 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.
  • Page 764 Mediant 800 MSBR Parameter Description Web: Deny Authentication Defines the duration (in seconds) for which login to the Web interface Timer is denied from a specific IP address (for all users) when the number of EMS: WEB Deny failed login attempts has exceeded the maximum. This maximum is Authentication Timer defined by the DenyAccessOnFailCount parameter.

  • Page 765: Telnet Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description acSysActionSetResetControl to 1 and acSysActionSetReset to Change the username and password in the acSysWEBAccessEntry table. Use the following format: Username acSysWEBAccessUserName: old/pass/new Password acSysWEBAccessUserCode: username/old/new [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface.

  • Page 766: Snmp Parameters

    Mediant 800 MSBR Parameter Description Disconnect The valid range is any value. The default is 0. CLI: idle-timeout Note: For this parameter to take effect, a device reset is required. [TelnetServerIdleDisconn ect] 66.2.4 SNMP Parameters The SNMP parameters are described in the table below. SNMP Parameters Parameter Description...
  • Page 767 User's Manual 66. Configuration Parameters Reference Parameter Description [acUserInputAlarmSeverity] Defines the severity of the input alarm. [AlarmHistoryTableMaxSize] Defines the maximum number of rows in the Alarm History table. This parameter can be controlled by the Config Global Entry Limit MIB (located in the Notification Log MIB). The valid range is 50 to 1000.
  • Page 768 Mediant 800 MSBR Parameter Description CLI: manager-host-name The resolved IP address replaces the last entry in the Trap [SNMPTrapManagerHostNam Manager table (defined by the SNMPManagerTableIP parameter) and the last trap manager entry of snmpTargetAddrTable in the snmpTargetMIB. For example: 'mngr.corp.mycompany.com'. The valid range is a string of up to 99 characters.

  • Page 769: Cli Parameters

    User's Manual 66. Configuration Parameters Reference 66.2.5 CLI Parameters The command-line interface (CLI) parameters are described in the table below. CLI Parameters Parameter Description CLI: aaa authentication Enables the Terminal Access Controller Access-Control System login tacacs+ (TACACS+) remote authentication protocol and user authentication for [TacPlusEnable] CLI login.
  • Page 770 Mediant 800 MSBR Parameter Description Web: Protocol Defines the protocol used for the TR-069 connection.  CLI: protocol [0] HTTP (default)  [1] HTTPS [TR069Protocol] Web: Port Defines the local HTTP/S port used for TR-069. CLI: port The valid range is 0 to 65535. The default is 82. [TR069HTTPPort] Note: For this parameter to take effect, a device reset is required.

  • Page 771: Serial Parameters

    User's Manual 66. Configuration Parameters Reference 66.2.7 Serial Parameters The RS-232 serial parameters are described in the table below. Serial Parameters Parameter Description [DisableRS232] Enables the device's RS-232 (serial) port.  [0] = Enabled  [1] = (Default) Disabled The RS-232 serial port can be used to change the networking parameters and view error/notification messages.

  • Page 772: Debugging And Diagnostics Parameters

    Mediant 800 MSBR 66.3 Debugging and Diagnostics Parameters This subsection describes the device's debugging and diagnostic parameters. 66.3.1 General Parameters The general debugging and diagnostic parameters are described in the table below. General Debugging and Diagnostic Parameters Parameter Description CLI: enablesecsyslog Enables the reporting of security-related events for the data-router [EnableSecSyslog] networking.

  • Page 773: Sip Test Call Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description  [0] = (Default) Lifeline is activated upon power outage.  [1] = Lifeline is activated upon power outage.  [2] = Lifeline is activated upon a power outage, network failure (logical link disconnection), or when the Trunk Group is in Busy Out state (see the EnableBusyOut parameter).

  • Page 774: Syslog, Cdr And Debug Parameters

    Mediant 800 MSBR Parameter Description defined. Notes:  This parameter is only for testing incoming calls destined to this prefix number.  This feature is applicable to all applications (GW/IP-to-IP and SBC). 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 [SBCtestID]...
  • Page 775 User's Manual 66. Configuration Parameters Reference Parameter Description Notes:  If you enable Syslog, you must enter an IP address of the Syslog server (using the SyslogServerIP parameter).  Syslog messages may increase the network traffic.  To configure Syslog SIP message logging levels, use the GwDebugLevel parameter.
  • Page 776 Mediant 800 MSBR Parameter Description identified by: Facility = 17 (local1) and Severity = 6 (Informational).  This mechanism is active only when Syslog is enabled (i.e., the parameter EnableSyslog is set to 1). Web: Media CDR Report Enables media-related CDRs of SBC calls to be sent to a Syslog Level server and determines the call stage at which they are sent.
  • Page 777 User's Manual 66. Configuration Parameters Reference Parameter Description Therefore, in addition to filtering Syslog messages according to IP address, the messages can be filtered according to Facility level.  [16] = (Default) local use 0 (local0)  [17] = local use 1 (local1) ...

  • Page 778: Resource Allocation Indication Parameters

    Mediant 800 MSBR Parameter Description for OAMP. CLI: isdn-facility-trace Enables ISDN traces of Facility Information Elements (IE) for ISDN call [FacilityTrace] diagnostics. This allows you to trace all the parameters contained in the Facility IE and view them in the Syslog. ...

  • Page 779: Security Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description 'acBoardCallResourcesAlarm' Alarm Trap is sent. [RAIHighThreshold] Defines the high threshold percentage of total calls that are active (busy endpoints). When the percentage of the device's busy endpoints exceeds this high threshold, the device sends the SNMP acBoardCallResourcesAlarm alarm trap with a 'major' alarm status.

  • Page 780: Https Parameters

    Mediant 800 MSBR Parameter Description Web/EMS: Internal This table parameter defines the device's access list (firewall), which Firewall Parameters defines network traffic filtering rules. CLI: configure voip > The format of this parameter is as follows: access-list [AccessList] [AccessList] FORMAT AccessList_Index = AccessList_Source_IP, AccessList_Source_Port, AccessList_PrefixLen, AccessList_Source_Port, AccessList_Start_Port, AccessList_End_Port, AccessList_Protocol, AccessList_Use_Specific_Interface, AccessList_Interface_ID,...

  • Page 781: Srtp Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description default of this parameter is changed to ‘RC4:EXP’, enabling RC- 128bit encryption.  The value ‘ALL’ can be configured only if the “Strong Encryption” Software License Key is enabled. Web: HTTP Determines the authentication mode used for the Web interface. Authentication Mode ...
  • Page 782 Mediant 800 MSBR Parameter Description RTP parameters:  If the remote SIP UA does not support SRTP, it uses RTP and ignores the crypto lines.  In the opposite direction, if the device receives an SDP offer with a single media (as shown above), it responds with SRTP (RTP/SAVP) if the EnableMediaSecurity parameter is set to 1.
  • Page 783 User's Manual 66. Configuration Parameters Reference Parameter Description the SDP answer (even if the SRTPTxPacketMKISize parameter is set to any value other than 0). Notes:  To enable symmetric MKI, the SRTPTxPacketMKISize parameter must be set to any value other than 0. ...

  • Page 784: Tls Parameters

    Mediant 800 MSBR Parameter Description Web: Disable Encryption Enables encryption on transmitted RTP packets in a secured RTP On Transmitted RTP session. Packets  [0] Enable (default) EMS: RTP  [1] Disable EncryptionDisable Tx CLI: RTP-encryption- disable-tx [RTPEncryptionDisable Web: Disable Encryption Enables encryption on transmitted RTCP packets in a secured RTP On Transmitted RTCP session.
  • Page 785 User's Manual 66. Configuration Parameters Reference Parameter Description Web: TLS Client Re- Defines the time interval (in minutes) between TLS Re-Handshakes Handshake Interval initiated by the device. EMS: TLS Re The interval range is 0 to 1,500 minutes. The default is 0 (i.e., no TLS Handshake Interval Re-Handshake).

  • Page 786: Ssh Parameters

    Mediant 800 MSBR Parameter Description [RequireStrictCert] certificate is authorized to negotiate a secure TLS connection.  [0] Disable (default)  [1] Enable Web/EMS: TLS Remote Defines the Subject Name that is compared with the name defined in the Subject Name remote side certificate when establishing TLS connections.

  • Page 787: Ocsp Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description [SSHRequirePublicKey] Note: To define the key size, use the TLSPkeySize parameter. Web: Max Payload Size Defines the maximum uncompressed payload size (in bytes) EMS: SSH Max Payload Size for SSH packets. CLI: ssh-max-payload-size The valid value is 550 to 32768.

  • Page 788: Ids Parameters

    Mediant 800 MSBR Parameter Description Web: Default Response When Determines the default OCSP behavior when the server cannot be Server Unreachable contacted. EMS: OCSP Default Response  [0] Reject = (Default) Rejects peer certificate. CLI: default-response  [1] Allow = Allows peer certificate. [OCSPDefaultResponse] 66.4.7 IDS Parameters The Intrusion Detection System (IDS) parameters are described in the table below.

  • Page 789: Radius Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description Web: IDS Match Table Defines target rules per IDS Policy. [IDSMatch] The format of the ini file parameter is: [ IDSMatch ] FORMAT IDSMatch_Index = IDSMatch_SIPInterface, IDSMatch_ProxySet, IDSMatch_Subnet, IDSMatch_Policy; [ \IDSMatch ] For a detailed description of this table, see 'Assigning IDS Policies' on page 146.
  • Page 790 Mediant 800 MSBR Parameter Description  [1] Enable Notes:  For RADIUS login authentication to function, you also need to set the following parameters:  EnableRADIUS = 1 (Enable)  WebAuthMode = 0 (Basic Mode)  RADIUS authentication requires HTTP basic authentication, where the username and password are transmitted in clear text over the network.
  • Page 791 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Local RADIUS Password Defines the time (in seconds) the locally stored user name and Cache Timeout password (verified by the RADIUS server) are valid. When this CLI: local-cache-timeout time expires, the user name and password become invalid and a [RadiusLocalCacheTimeout] must be re-verified with the RADIUS server.

  • Page 792: Sip Media Realm Parameters

    For a detailed description of this table, see 'Configuring Bandwidth Management per Media Realm' on page 179. Quality of Experience Parameters Web: Server IP Defines the IP address of AudioCodes Session Experience Manager CLI: server-ip (SEM) server to where the quality experience reports are sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
  • Page 793 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Port Defines the port of the SEM server. [QOEPort] The valid value range is 0 to 65534. The default is 5000. Web: Interface Name Defines the IP network interface on which the quality experience reports are sent.

  • Page 794: Control Network Parameters

    Mediant 800 MSBR 66.7 Control Network Parameters 66.7.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Proxy, Registration and Authentication SIP Parameters Parameter Description IP Group Table Web: IP Group Table This table configures IP Groups.
  • Page 795 User's Manual 66. Configuration Parameters Reference Parameter Description Account Table Web: Account Table This table parameter configures the Account table for registering and/or EMS: SIP Endpoints > authenticating (digest) Trunk Groups or IP Groups (e.g., an IP-PBX) to Account another Serving IP Group (e.g., an Internet Telephony Service Provider CLI: configure voip >...
  • Page 796 Mediant 800 MSBR Parameter Description Web: Redundancy Mode Determines whether the device switches back to the primary Proxy after EMS: Proxy Redundancy using a redundant Proxy. Mode  [0] Parking = (Default) The device continues working with a CLI: redundancy-mode redundant (now active) Proxy until the next failure, after which it [ProxyRedundancyMod works with the next redundant Proxy.
  • Page 797 User's Manual 66. Configuration Parameters Reference Parameter Description  [2] Routing Table = Uses the Routing table to locate the destination and then sends a new INVITE to this destination. Notes:  This parameter is applicable only to the Gateway / IP-to-IP application.
  • Page 798 Mediant 800 MSBR Parameter Description and their weights. The device then performs DNS A-record queries for each Proxy host name (according to the received weights) to locate up to four Proxy IP addresses. Therefore, if the first SRV query returns two domain names and the A-record queries return two IP addresses each, no additional searches are performed.
  • Page 799 User's Manual 66. Configuration Parameters Reference Parameter Description Authentication Mode Key Agreement (AKA) Digest Authentication is used. CLI: mutual-authentication  [0] Optional = (Default) Incoming requests that don't include AKA [MutualAuthenticationM authentication information are accepted. ode]  [1] Mandatory = Incoming requests that don't include AKA authentication information are rejected.
  • Page 800 Mediant 800 MSBR Parameter Description balancing and redundancy mechanisms (if a Proxy Set contains more than one proxy address). The format of this parameter is as follows: [ProxySet] FORMAT ProxySet_Index = ProxySet_EnableProxyKeepAlive, ProxySet_ProxyKeepAliveTime, ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap, ProxySet_SRD, ProxySet_ClassificationInput, ProxySet_ProxyRedundancyMode; [\ProxySet] For example: ProxySet 0 = 0, 60, 0, 0, 0, , 1;...
  • Page 801 User's Manual 66. Configuration Parameters Reference Parameter Description parameter EnableProxyKeepAlive must be set to 0.  When a specific transport type is defined using the parameter RegistrarTransportType, a DNS NAPTR query is not performed even if the parameter DNSQueryType is set to 2. Web/EMS: Registrar Determines the transport layer used for outgoing SIP dialogs initiated by Transport Type...
  • Page 802 Mediant 800 MSBR Parameter Description [RegisterOnInviteFailure When enabled, the device immediately expires its re-registration timer and commences re-registration to the same Proxy upon any of the following scenarios:  The response to an INVITE request is 407 (Proxy Authentication Required) without an authentication header included. ...
  • Page 803 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Set Out-Of-Service Enables setting the endpoint, trunk, or entire device (i.e., all endpoints) On Registration Failure to out-of-service if registration fails. EMS: Set OOS On  [0] Disable (default) Registration Fail ...
  • Page 804 Mediant 800 MSBR Parameter Description Authorization: Digest username=alice_private@home1.net, realm=”home1.net”, nonce=””, response=”e56131d19580cd833064787ecc” Note: This registration header is according to the IMS 3GPP TS24.229 and PKT-SP-24.220 specifications. Web: Add initial Route Enables the inclusion of the SIP Route header in initial registration or Header re-registration (REGISTER) requests sent by the device.

  • Page 805: Network Application Parameters

    User's Manual 66. Configuration Parameters Reference 66.7.2 Network Application Parameters The SIP network application parameters are described in the table below. SIP Network Application Parameters Parameter Description Signaling Routing Domain Table Web: SRD Settings This table parameter configures the Signaling Routing Domain (SRD) EMS: SRD Table table.

  • Page 806: General Sip Parameters

    (if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Defines the maximum size (in Kbytes) for each SIP message that can Message Length [KB] be sent over the network.
  • Page 807 User's Manual 66. Configuration Parameters Reference Parameter Description UDP port defined in the Via header. If the Via header contains the 'rport' parameter, the response is sent to the UDP port from where the SIP request is received.  [1] = Enabled. SIP responses are sent to the UDP port from where SIP requests are received even if the 'rport' parameter is not present in the Via header.
  • Page 808 Mediant 800 MSBR Parameter Description The X-RTP-Stat header provides the following statistics:  Number of received and sent voice packets  Number of received and sent voice octets  Received packet loss, jitter (in ms), and latency (in ms) The X-RTP-Stat header contains the following fields: ...
  • Page 809 User's Manual 66. Configuration Parameters Reference Parameter Description Digital: The inclusion of the SDP in the 18x response depends on the ISDN Progress Indicator (PI). The SDP is sent only if PI is set to 1 or 8 in the received Proceeding, Alerting, or Progress PRI messages. See also the ProgressIndicator2IP parameter, which if set to 1 or 8, the device behaves as if it received the ISDN messages with the PI.
  • Page 810 Mediant 800 MSBR Parameter Description When enabled, if the device sends a 183 response with an SDP (due to a received ISDN Progress or Proceeding with PI messages) and an Alerting message is then received from the Tel side (with or without Progress Indicator), the device does not send an additional 18x response, and the voice channel remains open.
  • Page 811 User's Manual 66. Configuration Parameters Reference Parameter Description Expires Disconnect Time (sends a SIP BYE) if the refresher did not send a refresh request before one-third (1/3) of the session expires time, or before the time configured CLI: session-exp- by this parameter (the minimum of the two). disconnect-time The valid range is 0 to 32 (in seconds).
  • Page 812 Mediant 800 MSBR Parameter Description  [IsFaxUsed] [1] T.38 Relay = Initiates T.38 fax relay.  [2] G.711 Transport = Initiates fax/modem using the coder G.711 A- law/Mu-law with adaptations (see Note below).  [3] Fax Fallback = Initiates T.38 fax relay. If the T.38 negotiation fails, the device re-initiates a fax session using the coder G.711 A- law/µ-law with adaptations (see the Note below).
  • Page 813 User's Manual 66. Configuration Parameters Reference Parameter Description upon fax detection. If the remote party supports T.38, the fax is relayed over T.38. Notes:  If VBD coder negotiation fails at call start and if the IsFaxUsed parameter is set to 1 (or 3), then the channel opens with the FaxTransportMode parameter set to 1 (relay) to allow future detection of fax tones and sending of T.38 Re-INVITES.
  • Page 814 Mediant 800 MSBR Parameter Description is set to 0 (i.e., UDP), the connection fails. Web/EMS: Enable TCP Enables the reuse of the same TCP connection for all calls to the same Connection Reuse destination. CLI: tcp-conn-reuse  [0] Disable = Uses a separate TCP connection for each call. [EnableTCPConnection ...
  • Page 815 User's Manual 66. Configuration Parameters Reference Parameter Description From Header Contact SIP headers. EMS: Is User Phone In  [0] No = (Default) Doesn't add 'user=phone' string. From  [1] Yes = 'user=phone' string is part of the From and Contact CLI: phone-in-from-hdr headers.
  • Page 816 Mediant 800 MSBR Parameter Description User Agent Server (UAS) Behavior:  The History-Info header is sent only in the final response.  Upon receiving a request with History-Info, the UAS checks the policy in the request. If a 'session', 'header', or 'history' policy tag is found, the (final) response is sent without History-Info;...
  • Page 817 User's Manual 66. Configuration Parameters Reference Parameter Description outgoing INVITE includes “tgrp=ccdata;trunk-context=dsn.mil”. If the Bearer Capability IE contains “Speech”, the INVITE in this case does not contain tgrp and trunk-context parameters.  [4] Hotline Extended = Interworks the ISDN Setup message’s hotline "OffHook Indicator"...
  • Page 818 Mediant 800 MSBR Parameter Description Group ID 56: INVITE sip:123456@192.168.1.2;dtg=56;user=phone SIP/2.0 Note: If the Trunk Group is not found based on the 'dtg' parameter, the Inbound IP Routing Table is used instead for routing the call to the appropriate Trunk Group. Web/EMS: Enable GRUU Determines whether the Globally Routable User Agent URIs (GRUU) CLI: enable-gruu...
  • Page 819 EMS: User Agent Display value>/software version' is used, for example: Info User-Agent: myproduct/v.6.40.010.006 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 800 MSBR/v.6.40.010.006 The maximum string length is 50 characters.
  • Page 820 Mediant 800 MSBR Parameter Description  [0] = (Default) Coder negotiation is given higher priority to the remote UA's list of supported coders.  [1] = Coder negotiation is given higher priority to the device's (local) supported coders list.  Note: This parameter is applicable only to the Gateway/IP-to-IP application.
  • Page 821 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: retry-aftr-time The time range is 0 to 3,600. The default is 0. [RetryAfterTime] Web/EMS: Fake Retry Determines whether the device, upon receipt of a SIP 503 response After [sec] without a Retry-After header, behaves as if the 503 response included a CLI: fake-retry-after Retry-After header and with the period (in seconds) specified by this [FakeRetryAfter]...
  • Page 822 Mediant 800 MSBR Parameter Description this header. If P-Asserted-Identity is selected and the Privacy header is set to 'id', the calling number is assumed restricted. CLI: src-hdr-4-called-nb Determines the SIP header used for obtaining the called number [SelectSourceHeaderFor (destination) for IP-to-Tel calls. CalledNumber] ...
  • Page 823 User's Manual 66. Configuration Parameters Reference Parameter Description  [EnableReasonHeader] [1] Enable (default) Web/EMS: Gateway Defines a name for the device (e.g., device123.com). This name is used Name as the host part of the SIP URI in the From header. If not specified, the CLI: gw-name device's IP address is used instead (default).
  • Page 824 Mediant 800 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 825 User's Manual 66. 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 on EMS: X Channel Header which the call is received or placed. CLI: x-channel-header ...
  • Page 826 Mediant 800 MSBR Parameter Description  Once a 200 OK is received in response to a REGISTER message, the REGISTER message is not considered in this maximum count limit.  This parameter applies only to outgoing REGISTER messages (i.e., incoming is unlimited). ...
  • Page 827 User's Manual 66. Configuration Parameters Reference Parameter Description responses, see Mapping PSTN Release Cause to SIP Response on page 324.  When the Trunk is disconnected or is not synchronized, the internal cause is 27. This cause is mapped, by default, to SIP 502. ...
  • Page 828 Mediant 800 MSBR Parameter Description Mode] trunks pertaining to Trunk Group #1 are down or busy.  [0] Disable (default)  [1] Enable = If all the trunks pertaining to Trunk Group #1 are down or busy, the device does not respond to received SIP OPTIONS. Web: Comfort Noise Enables negotiation and usage of Comfort Noise (CN).
  • Page 829 User's Manual 66. Configuration Parameters Reference Parameter Description Web/EMS: First Call Defines the index of the first ringback tone in the CPT file. This option Ringback Tone ID enables an Application server to request the device to play a distinctive CLI: 1st-call-rbt-id ringback tone to the calling party according to the destination of the call.
  • Page 830 Mediant 800 MSBR Parameter Description Notes:  This parameter is applicable only if the parameter RegretTime is configured.  This parameter is applicable only to FXS interfaces. Web: PSTN Alert Timeout Digital: Defines the Alert Timeout (in seconds) for calls sent to the EMS: Trunk PSTN Alert PSTN.
  • Page 831 User's Manual 66. Configuration Parameters Reference Parameter Description [SITQ850Cause] detected on an IP-to-Tel call. The valid range is 0 to 127. The default is 34. Note: For mapping specific SIT tones, you can use the SITQ850CauseForNC, SITQ850CauseForIC, SITQ850CauseForVC, and SITQ850CauseForRO parameters. Web/EMS: SIT Q850 Defines the Q.850 cause value specified in the SIP Reason header that Cause For NC...
  • Page 832 Mediant 800 MSBR Parameter Description Web/EMS: Enable Busy Enables the Busy Out feature.  [0] Disable (Default) CLI: busy-out  [1] Enable [EnableBusyOut] When Busy Out is enabled and certain scenarios exist, the device does the following: Analog: The FXS port behaves according to the settings of the FXSOOSBehavior parameter such as playing a reorder tone when the phone is off-hooked, or changing the line polarity.
  • Page 833 User's Manual 66. Configuration Parameters Reference Parameter Description Service Behavior per trunk. EMS: Digital OOS  [-1] Not Configured = (Default) Use the settings of the Behavior For Trunk Value DigitalOOSBehavior parameter for per device. CLI: dig-oos-behavior  [0] Default = Uses default behavior for each trunk (see note below). [DigitalOOSBehaviorFor ...
  • Page 834 Mediant 800 MSBR Parameter Description Web: SIP T1 Defines the time interval (in msec) between the first transmission of a Retransmission Timer SIP message and the first retransmission of the same message. [msec] The default is 500. EMS: T1 RTX Note: The time interval between subsequent retransmissions of the CLI: t1-re-tx-time same SIP message starts with SipT1Rtx.

  • Page 835: Coders And Profile Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description Message Policy Table Web: Message Policy This table parameter configures SIP message policy rules for blocking Table (blacklist) unwanted incoming SIP messages or allowing (whitelist) CLI: configure voip > sbc receipt of desired messages.The format of this parameter is as follows: message-policy [MessagePolicy] [MessagePolicy]...
  • Page 836 Mediant 800 MSBR Parameter Description Notes:  For a list of supported coders and a detailed description of this table, see Configuring Coders on page 239.  The coder name is case-sensitive. IP Profile Table Web: IP Profile This table parameter configures the IP Profile table. Each IP Settings Profile ID includes a set of parameters (which are typically EMS: Protocol...
  • Page 837 User's Manual 66. Configuration Parameters Reference Parameter Description IpProfile_SBCRemoteEarlyMediaResponseType, IpProfile_SBCRemoteEarlyMediaSupport, IpProfile_EnableSymmetricMKI, IpProfile_MKISize, IpProfile_SBCEnforceMKISize, IpProfile_SBCRemoteEarlyMediaRTP, IpProfile_SBCRemoteSupportsRFC3960, IpProfile_SBCRemoteCanPlayRingback, IpProfile_EnableEarly183, IpProfile_EarlyAnswerTimeout, IpProfile_SBC2833DTMFPayloadType, IpProfile_SBCUserRegistrationTime, IpProfile_ResetSRTPStateUponRekey, IpProfile_AmdMode, IpProfile_SBCReliableHeldToneSource, IpProfile_SBCPlayHeldTone, IpProfile_SBCRemoteHoldFormat, IpProfile_DelayTimeForInvite; [\IPProfile] Note: For a description of this table, see 'Configuring IP Profiles' on page 245. Tel Profile Table Web: Tel Profile This table parameter configures the Tel Profile table.

  • Page 838: Mediant 800 Msbr

    Mediant 800 MSBR Parameter Description  For a description of this parameter, see Configuring Tel Profiles on page 243.  For a detailed description of each parameter, see its corresponding "global" parameter. TelProfile Field Web Name Global Parameter TelProfile_ProfileName Profile Name TelProfile_TelPreferenc Profile Preference TelProfile_CodersGrou...

  • Page 839: Channel Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description TelProfile_Enable911P Enable 911 PSAP Enable911PSAP TelProfile_SwapTelToIp Swap Tel To IP Phone SwapTEl2IPCalled&Cal PhoneNumbers Numbers lingNumbers TelProfile_EnableAGC Enable AGC EnableAGC TelProfile_ECNlpMode EC NLP Mode ECNLPMode TelProfile_DigitalCutThr DigitalCutThrough ough TelProfile_EnableFXOD EnableFXODoubleAns oubleAnswer TelProfile_CallPriorityM CallPriorityMode 66.10 Channel Parameters This subsection describes the device's channel parameters.
  • Page 840 Mediant 800 MSBR Parameter Description Web: Enable Answer Detector Currently, not supported. [EnableAnswerDetector] Web: Answer Detector Activity Defines the time (in 100-msec resolution) between activating the Delay Answer Detector and the time that the detector actually starts to CLI: answer-detector- operate.
  • Page 841 User's Manual 66. Configuration Parameters Reference Parameter Description side. Web: Attenuation Intensity Defines the acoustic echo suppressor signals identified as echo CLI: acoustic-echo-suppressor- attenuation intensity. attenuation-intensity The valid range is 0 to 3. The default is 0. [AcousticEchoSuppAttenuati onIntensity] Web: Max ERL Threshold - DB Defines the acoustic echo suppressor maximum ratio between CLI: acoustic-echo-suppressor- signal level and returned echo from the phone (in decibels).

  • Page 842: Coder Parameters

    Mediant 800 MSBR 66.10.2 Coder Parameters The coder parameters are described in the table below. Coder Parameters Parameter Description Silk Tx Inband FEC Enables forward error correction (FEC) for the SILK coder. CLI: silk-tx-inband-fec  [0] Disable (default) [SilkTxInbandFEC]  [1] Enable Silk Max Average Bit Rate Defines the maximum average bit rate for the SILK coder.

  • Page 843: Dtmf Parameters

    User's Manual 66. Configuration Parameters Reference 66.10.3 DTMF Parameters The dual-tone multi-frequency (DTMF) parameters are described in the table below. 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 844: Rtp, Rtcp And T.38 Parameters

    Mediant 800 MSBR Parameter Description duration the DTMF signal duration on the TDM side. [NTEMaxDuration] The range is -1 to 200,000,000 msec. The default is -1 (i.e., NTE stops only upon detection of an End event). 66.10.4 RTP, RTCP and T.38 Parameters The RTP, RTCP and T.38 parameters are described in the table below.
  • Page 845 User's Manual 66. Configuration Parameters Reference Parameter Description  [EnableRTPRedundancyNeg [0] Disable (default) otiation]  [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>...
  • Page 846 Mediant 800 MSBR Parameter Description payload type is used for receive and for transmit. [EnableDetectRemoteMACC Determines whether the device changes the RTP packets hange] according to the MAC address of received RTP packets and according to Gratuitous Address Resolution Protocol (GARP) messages.
  • Page 847 User's Manual 66. 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 848: Gateway And Ip-To-Ip Parameters

    Mediant 800 MSBR Parameter Description  [0] UDP  [1] TCP  [2] TLS Note: When set to [-1], the value of the SIPTransportType parameter is used. Web: RTCP XR Collection Defines the IP address of the Event State Compositor (ESC). The Server device sends RTCP XR reports to this server, using SIP PUBLISH EMS: Esc IP...
  • Page 849 User's Manual 66. Configuration Parameters Reference Parameter Description  CLI: V21-modem-transport- [3] Events Only = Transparent with Events type Note: This parameter can also be configured in an IP Profile. [V21ModemTransportType] Web: V.22 Modem Transport Determines the V.22 modem transport type. Type ...
  • Page 850 Mediant 800 MSBR Parameter Description  The device also sends T.38 re-INVITE if the CNGDetectorMode parameter is set to [2], regardless of the FaxCNGMode parameter settings. Web/EMS: CNG Detector Determines whether the device detects the fax calling tone (CNG). Mode ...
  • Page 851 User's Manual 66. Configuration Parameters Reference Parameter Description  [3] 9600 = 9.6 kbps  [4] 12000 = 12.0 kbps  [5] 14400 = 14.4 kbps (default)  [6] 16800bps = 16.8 kbps  [7] 19200bps = 19.2 kbps  [8] 21600bps = 21.6 kbps ...
  • Page 852 Mediant 800 MSBR Parameter Description type [ModemBypassPayloadType] EMS: Relay Volume (dBm) Defines the fax gain control. CLI: volume The range is -18 to -3, corresponding to -18 dBm to -3 dBm in 1-dB [FaxModemRelayVolume] steps. The default is -6 dBm fax gain control. Web/EMS: Fax Bypass Output Defines the fax bypass output gain control.
  • Page 853 User's Manual 66. Configuration Parameters Reference Parameter Description  This feature can be used only if the VxxModemTransportType parameter is set to 2 (Bypass).  If NSE mode is enabled, the SDP contains the following line: 'a=rtpmap:100 X-NSE/8000'.  To use this feature: ...
  • Page 854 Mediant 800 MSBR Parameter Description [CEDTransferMode] Determines the fax CED tone transfer mode.  [0] = (Default) The device transfers the CED tone in relay mode and starts the fax session immediately.  [1] = The device transfers the CED tone in either voice or bypass mode and starts the fax session on V21 preamble.

  • Page 855: Dtmf And Hook-Flash Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description Web: SPRT Transport Ch.2 Defines the maximum payload size for V.150.1 SPRT Transport Max Payload Size Channel 2. CLI: SPRT-transport-channel2- The range is 132 to 256. The default is 132. max-payload-size [V1501SPRTTransportChann el2MaxPayloadSize] Web: SPRT Transport Ch.2 Defines the maximum window size of SPRT transport channel 2.
  • Page 856 Mediant 800 MSBR Parameter Description  [5] INFO (Lucent) = Sends proprietary SIP INFO message with Hook-Flash indication. The device sends the INFO message as follows: Content-Type: application/hook-flash Content-Length: 11 signal=hf  [6] INFO (NetCentrex) = Sends proprietary SIP INFO message with Hook-Flash indication.
  • Page 857 User's Manual 66. Configuration Parameters Reference Parameter Description hook-flash, set this parameter to 550.  This parameter can also be configured in a Tel Profile. DTMF Parameters EMS: Use End of DTMF Determines when the detection of DTMF events is notified. CLI: notify-on-sig-end ...
  • Page 858 Mediant 800 MSBR Parameter Description Sends DTMF packets using RFC 2833 payload type according to the payload type in the received SDP. Expects to receive RFC 2833 packets with the same payload type as configured by the parameter RFC2833PayloadType. Removes DTMF digits in transparent mode (as part of the voice stream).
  • Page 859 User's Manual 66. Configuration Parameters Reference Parameter Description a dial tone before it starts playing DTMF digits. For example, if the called number is '1007766p100', the device places a call with 1007766 as the destination number, then after the call is answered it waits 1.5 seconds ('p') and plays the rest of the number (100) as DTMF digits.

  • Page 860: Digit Collection And Dial Plan Parameters

    Mediant 800 MSBR 66.11.3 Digit Collection and Dial Plan Parameters The digit collection and dial plan parameters are described in the table below. Digit Collection and Dial Plan Parameters Parameter Description Web/EMS: Dial Plan Index Defines the Dial Plan index to use in the external Dial Plan file. The CLI: dial-plan-index Dial Plan file is loaded to the device as a .dat file (converted using [DialPlanIndex]...
  • Page 861 User's Manual 66. Configuration Parameters Reference Parameter Description specific rule is defined after a more general rule. For example, if the digit map is 99|998, then the digit collection is terminated after the first two 9 digits are received. Therefore, the second rule of 998 can never be matched.

  • Page 862: Voice Mail Parameters

    Mediant 800 MSBR Parameter Description user or for the endpoint telephone number. Note: These symbols can always be used as the first digit of a dialed number even if you disable this parameter. 66.11.4 Voice Mail Parameters The voice mail parameters are described in the table below. For more information on the Voice Mail application, refer to the CPE Configuration Guide for Voice Mail.
  • Page 863 User's Manual 66. Configuration Parameters Reference Parameter Description Others >> 302 If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason. [WaitForBusyTime] Defines the time (in msec) that the device waits to detect busy and/or reorder tones.
  • Page 864 Mediant 800 MSBR Parameter Description device waits for connection of the transferred call and then completes the call transfer by releasing the line. If speech is not detected, the transfer is cancelled, the device sends a SIP NOTIFY message with a failure reason in the NOTIFY body (such as 486 if busy tone detected) and generates an additional hook-flash toward the FXO line to restore connection to the original call.
  • Page 865 User's Manual 66. Configuration Parameters Reference Parameter Description Web: MWI Suffix Pattern Defines the digit code used by the device as a suffix for 'MWI On Digit EMS: MWI Suffix Code Pattern' and 'MWI Off Digit Pattern'. This suffix is added to the CLI: mwi-suffix-pattern generated DTMF string after the extension number.
  • Page 866 Mediant 800 MSBR Parameter Description Web: Forward on No Defines the digit pattern used by the PBX to indicate 'call forward on Answer Digit Pattern no answer' when the original call is received from an internal (Internal) extension. EMS: Digit Pattern The valid range is a 120-character string.
  • Page 867 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Forward on No Defines the digit pattern used by the PBX to indicate 'call forward with Reason Digit Pattern no reason' when the original call is received from an external line (not (External) an internal extension).

  • Page 868: Supplementary Services Parameters

    Mediant 800 MSBR 66.11.5 Supplementary Services Parameters This subsection describes the device's supplementary telephony services parameters. 66.11.5.1 Caller ID Parameters The caller ID parameters are described in the table below. Caller ID Parameters Parameter Description Caller ID Permissions Table Web: Caller ID This table parameter enables (per port) Caller ID generation (for FXS Permissions Table interfaces) and detection (for FXO interfaces).
  • Page 869 User's Manual 66. Configuration Parameters Reference Parameter Description Display Information on page 404. Web/EMS: Enable Caller Enables Caller ID.  [0] Disable (default) CLI: enable-caller-id  [1] Enable [EnableCallerID] If the Caller ID service is enabled, then for FXS interfaces, calling number and Display text (from IP) are sent to the device's port.
  • Page 870 Mediant 800 MSBR Parameter Description From (or P-Asserted-Id) header: From:<sip:+551137077801;cpc=payphone@10.20.7.35>;tag=53 The calling number manipulation removes "+55" (leaving 10 digits), and then adds the prefix 7, the cpc code for payphone user. Therefore, the Caller ID number that is sent to the FXS port, in this example is 71137077801.
  • Page 871 User's Manual 66. Configuration Parameters Reference Parameter Description  One Sub Standard [0] = (Default) ETSI between rings. CLI: etsi-callerid-type-one-  [1] = ETSI before ring DT_AS. sub-standard  [2] = ETSI before ring RP_AS. [ETSICallerIDTypeOneSu  [3] = ETSI before ring LR_DT_AS. bStandard] ...

  • Page 872: Call Waiting Parameters

    Mediant 800 MSBR Parameter Description CLI: caller-ID-transport- remain in the voice stream. type  [1] Relay = (Currently not applicable.) [CallerIDTransportType]  [3] Mute = (Default) The caller ID signal is detected from the Tel/PSTN side and then erased from the voice stream. Note: Caller ID detection is applicable only to FXO interfaces.
  • Page 873 User's Manual 66. Configuration Parameters Reference Parameter Description side, FXS only).  FXS interfaces: The EnableHold parameter must be enabled on both the calling and the called side.  Analog interfaces: You can use the table parameter CallWaitingPerPort to enable Call Waiting per port. ...

  • Page 874: Call Forwarding Parameters

    Mediant 800 MSBR Parameter Description EMS: First Call Waiting Defines the index of the first Call Waiting Tone in the CPT file. This Tone ID feature enables the called party to distinguish between different call [FirstCallWaitingToneID] origins (e.g., external versus internal calls). There are three ways to use the distinctive call waiting tones: ...
  • Page 875 User's Manual 66. Configuration Parameters Reference Parameter Description option. Call Forwarding Table Web: Call Forwarding This table parameter configures call forwarding of IP-to-Tel calls (using Table SIP 302 response) to other device ports or an IP destination, based on EMS: Analog Gateway the device's port to which the call was originally routed.

  • Page 876: Message Waiting Indication Parameters

    Mediant 800 MSBR 66.11.5.4 Message Waiting Indication Parameters The message waiting indication (MWI) parameters are described in the table below. MWI Parameters Parameter Description Web: Enable MWI Enables Message Waiting Indication (MWI). EMS: MWI Enable  [0] Disable (default). CLI: enable-mwi ...
  • Page 877 User's Manual 66. Configuration Parameters Reference Parameter Description  [2] TLS Note: When set to ‘Not Configured’, the value of the parameter SIPTransportType is used. Web: MWI Subscribe Defines the MWI subscription expiration time in seconds. Expiration Time The default is 7200 seconds. The range is 10 to 2,000,000. EMS: MWI Expiration Time CLI: mwi-subs-expr-...

  • Page 878: Call Hold Parameters

    Mediant 800 MSBR 66.11.5.5 Call Hold Parameters The call hold parameters are described in the table below. Call Hold Parameters Parameter Description Web/EMS: Enable Hold For digital interfaces: Enables interworking of the Hold/Retrieve CLI: hold supplementary service from PRI to SIP. [EnableHold] For analog interfaces: Enables the Call Hold feature that allows users, connected to the device, to place a call on hold (or remove from hold).

  • Page 879: Call Transfer Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description [DisableReminderRing] or a waiting call when the phone is returned to on-hook position.  [0] = (Default) The reminder ring feature is active. In other words, if a call is on hold or there is a call waiting and the phone is changed from offhook to onhook, the phone rings (for a duration defined by the CHRRTimeout parameter) to "remind"...
  • Page 880 Mediant 800 MSBR Parameter Description Web: Transfer Prefix IP 2 Defines the prefix that is added to the destination number received in the SIP Refer-To header (for IP-to-Tel calls). This parameter is applicable to CLI: xfer-prefix-ip2tel FXO/CAS blind transfer modes, i.e., LineTransferMode = 1, 2 or 3, and [XferPrefixIP2Tel] TrunkTransferMode = 1 or 3 (for CAS).
  • Page 881 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: replace-tel2ip- Defines the maximum duration (timeout) to wait between call Setup and calnum-to Facility with Redirecting Number for replacing the calling number (for Tel- [ReplaceTel2IPCallingN to-IP calls). umTimeout] The valid value range is 0 to 10,000 msec. The default is 0. The interworking of the received Setup message to a SIP INVITE is suspended when this parameter is set to any value greater than 0.

  • Page 882: Three-Way Conferencing Parameters

    Determines the mode of operation when the 3-Way Conference feature Conference Mode is used. EMS: 3 Way Mode  [0] AudioCodes Media Server = (Default) The Conference-initiating CLI: 3w-conf-mode INVITE (sent by the device) uses the ConferenceID concatenated [3WayConferenceMode] 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 883: Mlpp And Emergency Call Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description Web: Establish Defines the DTMF digit pattern, which upon detection generates the Conference Code conference call when three-way conferencing is enabled EMS: Establish Code (Enable3WayConference is set to 1). CLI: estb-conf-code The valid range is a 25-character string. The default is “!” (Hook-Flash). [ConferenceCode] Note: If the FlashKeysSequenceStyle parameter is set to 1 or 2, the setting of the ConferenceCode parameter is overridden.
  • Page 884 Mediant 800 MSBR Parameter Description when, for example, congestion occurs in a network.  [2] Emergency = Preemption of IP-to-Tel E911 emergency calls. If the device receives an E911 call and there are unavailable channels to receive the call, the device terminates one of the channel calls and sends the E911 call to that channel.
  • Page 885 User's Manual 66. Configuration Parameters Reference Parameter Description Notes:  This parameter is applicable only to FXO interfaces.  This parameter can also be configured in a Tel Profile. Web/EMS: Emergency Defines a list of “emergency” numbers. Numbers For FXS: When one of these numbers is dialed, the outgoing INVITE CLI: emerg-nbs message includes the SIP Priority and Resource-Priority headers.
  • Page 886 Mediant 800 MSBR Parameter Description EnableIp2TelInterworking:  Disabled: The network-domain field in the Resource-Priority header is set to "0 1 0 0" (i.e., "routine") in the Precedence Level field.  Enabled: The network-domain field in the Resource-Priority header is set in the Precedence Level field according to Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value).
  • Page 887 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: mlpp-norm-ser-dmn ‘FFFFFF’, the Resource-Priority header is set to the MLPP Service [MLPPNormalizedServic Domain obtained from the Precedence IE. eDomain] The valid value is 6 hexadecimal digits. The default is ‘000000’. Note: This parameter is applicable only to the MLPP NI-2 ISDN variant with CallPriorityMode set to 1.
  • Page 888 Mediant 800 MSBR Parameter Description Require header.  [1] Enable = (Default) Adds the SIP resource-priority tag in the SIP Require header. Note: This parameter is applicable only to MLPP priority call handling (i.e., only when the CallPriorityMode parameter is set to 1). Multiple Differentiated Services Code Points (DSCP) per MLPP Call Priority Level (Precedence) Parameters The MLPP service allows placement of priority calls, where properly validated users can preempt...

  • Page 889: Call Cut-Through Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description PDSCP] 66.11.5.9 Call Cut-Through Parameters The call cut-through parameters are described in the table below. Call Cut-Through Parameters Parameter Description Web: Enable Calls Cut Enables FXS endpoints to receive incoming IP calls while the port is in Through off-hook state.

  • Page 890: Automatic Dialing Parameters

    Mediant 800 MSBR 66.11.5.10 Automatic Dialing Parameters The automatic dialing upon off-hook parameters are described in the table below. Automatic Dialing Parameters Parameter Description Automatic Dialing Table Web: Automatic Dialing This table parameter defines telephone numbers that are automatically Table dialed when a specific FXS or FXO port is off-hooked.
  • Page 891 User's Manual 66. Configuration Parameters Reference Parameter Description Enable911PSAP parameter is set to 1.  [2] Double Wink = Double-wink signaling. The FXS interface generates the first wink upon detection of an off-hook state in the line. The second wink is generated after a user-defined interval (configured by the TimeBetweenDIDWinks parameter), after which the DTMF/MF digits are collected by the device.

  • Page 892: Isdn Bri Parameters

    Mediant 800 MSBR Parameter Description EnableDID_Module; [\EnableDID] Where,  IsEnable = Enables [1] or disables [0] (default) Japan NTT Modem DID support.  Port = Port number.  Module = Module number. For example: EnableDID 0 = 1,1,2; (DID is enabled on Port 1 of Module 2) Note: This parameter is applicable only to FXS interfaces.
  • Page 893 User's Manual 66. Configuration Parameters Reference Parameter Description Unconditional the softswitch. [SuppServCodeCFU] The valid value is a string. The default is an empty string. Note: The string must be enclosed in single apostrophe (e.g., ‘*72’). Web/EMS: Call Forward Defines the prefix code for deactivating Call Forward Unconditional Unconditional Deactivation sent to the softswitch.

  • Page 894: Pstn Parameters

    Mediant 800 MSBR 66.11.6 PSTN Parameters This subsection describes the device's PSTN parameters. 66.11.6.1 General Parameters The general PSTN parameters are described in the table below. General PSTN Parameters Parameter Description Web/EMS: Protocol Type Defines the PSTN protocol for all the Trunks. To configure the CLI: protocol protocol type for a specific Trunk, use the ini file parameter [ProtocolType]...
  • Page 895 User's Manual 66. Configuration Parameters Reference Parameter Description (similar to ETSI).  [20] T1 HKT ISDN = ISDN PRI (T1) protocol for the Hong Kong - HKT.  [21] E1 QSIG = ECMA 143 QSIG over E1  [22] E1 TNZ = ISDN PRI protocol for Telecom New Zealand (similar to ETSI) ...
  • Page 896 Mediant 800 MSBR Parameter Description Notes:  Instead of configuring this parameter, it is recommended to use the parameter ISDNTimerT310.  This parameter is applicable only to Nortel DMS and Nortel MERIDIAN PRI variants (ProtocolType = 14 and 35). [ISDNTimerT301] Defines the override T301 timer (in seconds).
  • Page 897 User's Manual 66. Configuration Parameters Reference Parameter Description  [D] T1 FRAMING ESF CRC6 = T1 Extended SuperFrame with CRC6  [E] T1 FRAMING F72 = T1 72-Frame multiframe (SLC96)  [F] T1 FRAMING ESF CRC6 J2 = J1 Extended SuperFrame with CRC6 (Japan) Note: This parameter is not configurable for BRI interfaces;...

  • Page 898: Tdm Bus And Clock Timing Parameters

    Mediant 800 MSBR Parameter Description  [1] = shutting down (read only).  [2] = (Default) Unlock the trunk; enables trunk traffic. Web/EMS: Line Build Out Loss Defines the line build out loss for the selected T1 trunk. CLI: line-build-out-loss ...
  • Page 899 User's Manual 66. Configuration Parameters Reference Parameter Description spans. Web/EMS: Idle PCM Pattern Defines the PCM Pattern that is applied to the E1/T1 timeslot (B- CLI: idle-pcm-pattern channel) when the channel is idle. [IdlePCMPattern] The range is 0 to 255. The default is set internally according to the Law select 1 (0xFF for Mu-Law;...

  • Page 900: Cas Parameters

    Mediant 800 MSBR Parameter Description the next trunk. Note that initially, the device attempts to recover the clock from the trunk defined by the parameter TDMBusLocalReference. Notes:  For this parameter to take effect, a device reset is required.  This parameter is relevant only if the parameter TDMBusClockSource is set to 4.
  • Page 901 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: cas-delimiters-types Defines the digits string delimiter padding usage per trunk. [CASDelimitersPaddingUsag  [0] = (Default) Default address string padding: '*XXX#' (where XXX is the digit string that begins with '*' and ends with '#', when using padding).
  • Page 902 Mediant 800 MSBR Parameter Description T1 CAS trunk (Trunk 5) with several CAS variants: ProtocolType_5 = 7 CASFILENAME_0='E_M_FGBWinkTable.dat' CASFILENAME_1='E_M_FGDWinkTable.dat' CASFILENAME_2='E_M_WinkTable.txt' CasChannelIndex_5 = ‘0,0,0,1,1,1,2,2,2,0,0,0,1,1,1,0,1,2,0,2,1,2,2 ,2’ CASDelimitersPaddingUsage_5 = 1  CAS table per channel group: Each channel group is separated by a colon and each channel is separated by a comma.

  • Page 903: Isdn Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description [CASStateMachineMaxNumO address digits is stopped. fIncomingAddressDigits] The value must be an integer. The default is -1. Web: MAX Incoming ANI Digits Defines the limitation for the maximum ANI digits that need to be collected.
  • Page 904 Mediant 800 MSBR Parameter Description Web/EMS: B-channel Determines the ISDN B-Channel negotiation mode. Negotiation  [0] Preferred CLI: b-ch-negotiation  [1] Exclusive (default) [BchannelNegotiation]  [2] Any Notes:  This parameter is applicable only to ISDN protocols.  For some ISDN variants, when 'Any' (2) is selected, the Setup message excludes the Channel Identification IE.
  • Page 905 User's Manual 66. Configuration Parameters Reference Parameter Description  For more information on NFAS, see 'ISDN Non-Facility Associated Signaling (NFAS)' on page 289. Web: Enable ignoring ISDN Allows the device to ignore ISDN Disconnect messages with PI 1 Disconnect with PI or 8.
  • Page 906 Mediant 800 MSBR Parameter Description  User provided, user provided: the first one is used When this bit is configured, the device behaves as follows:  Network provided, Network provided: the first calling number is used  Network provided, User provided: the second one is used ...
  • Page 907 User's Manual 66. Configuration Parameters Reference Parameter Description on receipt of Q.931 Status with incompatible state. Otherwise, no action is taken (default).  [262144] STATUS ERROR CAUSE = Clear call on receipt of Status according to cause value.  [524288] ACCEPT A LAW =A-Law is also accepted in 5ESS. ...
  • Page 908 Mediant 800 MSBR Parameter Description QSIG standard (ETS 300-172) and other ETSI-based standards (ETS 300-102 and ETS 300-403) in the conversion of B-channel ID values into timeslot values:  In 'regular ETSI' standards, the timeslot is identical to the B-channel ID value, and the range for both is 1 to 15 and 17 to 31.
  • Page 909 User's Manual 66. Configuration Parameters Reference Parameter Description A-Law in outgoing voice calls. Note: This option is applicable only to the Korean variant.  [128] DIAL WITH KEYPAD = The device uses the Keypad IE to store the called number digits instead of the CALLED_NB Note: This option is applicable only to the Korean variant (Korean network).

  • Page 910: Isdn And Cas Interworking Parameters

    Mediant 800 MSBR Parameter Description [PSTNExtendedParams] Determines the bit map for special PSTN behavior parameters:  [0] = (Default) Applicable for NI-2 ISDN and QSIG "Networking Extensions". This bit (i.e., bit #0) is responsible for the Invoke ID size:  If this bit is not set (default), then the Invoke ID size is always one byte, with a value of 01 to 7f.
  • Page 911 User's Manual 66. Configuration Parameters Reference Parameter Description Web/EMS: Min Routing Defines the minimum number of overlap digits to collect (for ISDN Overlap Digits overlap dialing) before sending the first SIP message for routing Tel-to- CLI: min-dg-b4-routing IP calls. [MinOverlapDigitsForR The valid value range is 0 to 49.
  • Page 912 Mediant 800 MSBR Parameter Description  For enabling ISDN overlap dialing for IP-to-Tel calls, use the ISDNTxOverlap parameter.  The x in the ini file parameter denotes the trunk number, where 0 is Trunk 1.  For more information on ISDN overlap dialing, see 'ISDN Overlap Dialing' on page 292.
  • Page 913 User's Manual 66. Configuration Parameters Reference Parameter Description in the proprietary SIP header, x-isdntunnelinginfo, or a dedicated message body (application/isdn) in the SIP message and then sends the data in an ISDN message to the PSTN. If the raw data in this SIP header is suffixed with the string "ADDE", then the raw data is extracted and added as Informational Elements (IE) in the outgoing Q.931 message.
  • Page 914 Mediant 800 MSBR Parameter Description  This parameter is applicable also to QSIG BRI.  If the parameter is disabled, the device plays a held tone to the Tel side when a SIP request with 0.0.0.0 or "inactive" in SDP is received. An appropriate CPT file with the held tone should be used.
  • Page 915 User's Manual 66. Configuration Parameters Reference Parameter Description destination subaddress. If the isub parameter is not present in the Request-URI header nor To header, the device does the following:  If the called number (that appears in the user part of the Request-URI) starts with zero (0), for example, INVITE sip:05694564@host.domain:user=phone SIP/2.0 then the device maps this called number to the destination...
  • Page 916 Mediant 800 MSBR Parameter Description Cause Mapping FORMAT CauseMapSIP2ISDN_Index = CLI: configure voip > gw CauseMapSIP2ISDN_SipResponse, manipulations CauseMapSIP2ISDN_IsdnReleaseCause; CauseMapSip2Isdn [\CauseMapSIP2ISDN] [CauseMapSIP2ISDN] Where,  SipResponse = SIP Response  IsdnReleaseCause = Q.850 Release Cause For example: CauseMapSIP2ISDN 0 = 480,50; CauseMapSIP2ISDN 0 = 404,3; When a SIP response is received (from the IP side), the device searches this mapping table for a match.
  • Page 917 User's Manual 66. Configuration Parameters Reference Parameter Description Note: This parameter is applicable for Tel-to-IP and IP-to-Tel calls. Web/EMS: Remove CLI Determines (for IP-to-Tel calls) whether the Calling Number and Calling when Restricted Name IEs are removed from the ISDN Setup message if the CLI: rmv-cli-when-restr presentation is set to Restricted.
  • Page 918 Mediant 800 MSBR Parameter Description message is received.  [0] = (Default) Connect message isn't sent after SIP 183 Session Progress message is received.  [1] = Connect message is sent after SIP 183 Session Progress message is received. Web: Local ISDN Determines whether the ringback tone is played to the ISDN by the Ringback Tone Source PBX/PSTN or by the device, per trunk.
  • Page 919 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: call-re-rte-mode Determines whether ISDN call rerouting (call forward) is performed by [CallReroutingMode] the PSTN instead of by the SIP side. This call forwarding is based on Call Deflection for Euro ISDN (ETS-300-207-1) and QSIG (ETSI TS 102 393).
  • Page 920 Mediant 800 MSBR Parameter Description  [EnableDSPIPMDetecto For this parameter to take effect, a device reset is required.  The device's Software License Key must contain the 'IPMDetector' DSP option.  When enabled (1), the number of available channels is reduced. Web: Add IE in SETUP Adds an optional Information Element (IE) data (in hex format) to ISDN EMS: IE To Be Added In...
  • Page 921 User's Manual 66. Configuration Parameters Reference Parameter Description  To interwork the UUIE header from SIP-to-ISDN messages with the 4ESS ISDN variant, the ISDNGeneralCCBehavior parameter must be set to 16384. [Enable911LocationIdI Enables interworking of Emergency Location Identification from SIP to P2Tel] PRI.
  • Page 922 Mediant 800 MSBR Parameter Description  [2] = Supports ISDN (PRI/BRI) transfer - Release Link Trunk (RLT) (DMS-100), Two B Channel Transfer (TBCT) (NI2), Explicit Call Transfer (ECT) (EURO ISDN), and Path Replacement (QSIG). When a SIP REFER message is received, the device performs a transfer by sending Facility messages to the PBX with the necessary information on the call's legs to be connected.
  • Page 923 User's Manual 66. Configuration Parameters Reference Parameter Description the parameter options, refer to the parameter TrunkTransferMode. [EnableTransferAcross Determines whether the device allows ISDN ECT, RLT or TBCT IP-to- TrunkGroups] Tel call transfers between B-channels of different Trunk Groups.  [0] = (Default) Disable - ISDN call transfer is only between B- channels of the same Trunk Group.
  • Page 924 Mediant 800 MSBR Parameter Description  ansfer] [0] Disable = Rejects ISDN transfer requests.  [1] Enable = (Default) The device sends a SIP REFER message to the remote call party if ECT/TBCT Facility messages are received from the ISDN side (e.g., from a PBX). [DisableFallbackTransf Enables "hairpin"...

  • Page 925: Answer And Disconnect Supervision Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2 CSeq:2 INFO Content-Type: application/broadsoft Content-Length: 17 event flashhook Note: This parameter is applicable only to T1 CAS protocols. 66.11.8 Answer and Disconnect Supervision Parameters The answer and disconnect supervision parameters are described in the table below. Answer and Disconnect Parameters Parameter Description...
  • Page 926 Mediant 800 MSBR Parameter Description  This parameter is applicable to IP-to-Tel and Tel-to-IP calls.  This parameter is applicable only to ISDN and CAS protocols. Web/EMS: Disconnect Determines whether the device disconnects a call when a dial tone is on Dial Tone detected from the PBX.
  • Page 927 User's Manual 66. Configuration Parameters Reference Parameter Description EnableSilenceCompression and FarEndDisconnectSilenceMethod to 1. Web: Silence Detection Defines the duration of the silence period (in seconds) after which the Period [sec] call is disconnected. EMS: Silence Detection The range is 10 to 28,800 (i.e., 8 hours). The default is 120 seconds. Time Out Note: For this parameter to take effect, a device reset is required.
  • Page 928 Mediant 800 MSBR Parameter Description  Digital interfaces: This parameter is applicable only to CAS protocols.  Analog interfaces: This parameter is applicable only to FXO interfaces.  This parameter is also applicable to the IP-to-IP application.  This parameter can also be configured in a Tel Profile. Polarity (Current) Reversal for Call Release (Analog Interfaces) Parameters [SetDefaultLinePolarity Defines the FXO line polarity, required for DID signaling.

  • Page 929: Tone Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description EMS: Polarity Reversal Defines the voltage change slope during polarity reversal or wink. Type  [0] = (Default) Soft reverse polarity. CLI: polarity-reversal-  [1] = Hard reverse polarity. type Notes: [PolarityReversalType] ...
  • Page 930 Mediant 800 MSBR Parameter Description receives a re-INVITE with 'a=inactive' in the SDP from the party initiating the call hold. The held tone must be configured in the CPT file. Note: This parameter is applicable only to the IP-to-IP application. Web: SIP Hold Behavior Enables the device to handle incoming re-INVITE messages with CLI: sip-hold-behavior...
  • Page 931 User's Manual 66. Configuration Parameters Reference Parameter Description Note: This parameter is applicable only to FXO interfaces. Web: Hotline Dial Tone Defines the duration (in seconds) of the hotline dial tone. If no Duration digits are received during this duration, the device initiates a call EMS: Hot Line Tone Duration to a user-defined number (configured in the Automatic Dialing CLI: hotline-dt-dur...
  • Page 932 Mediant 800 MSBR Parameter Description tone is played to the user. The valid range is -1 to 2,147,483,647. The default is 600. Notes:  A negative value indicates that the tone is played infinitely.  This parameter is applicable only to analog interfaces. Web: Play Busy Tone to Tel Enables the device to play a busy or reorder tone to the PSTN CLI: play-bsy-tone-2tel...
  • Page 933 User's Manual 66. Configuration Parameters Reference Parameter Description device issues a Progress message (unless SIP183Behaviour is set to 1). If the SIP183Behaviour parameter is set to 1, the 183 response is handled the same way as a 180 Ringing response. ...
  • Page 934 Mediant 800 MSBR Parameter Description CAS, it doesn't play a ringback tone. No Progress Indicator (PI) is sent to the ISDN unless the ProgressIndicator2ISDN_x parameter is configured differently.  [1] Play on Local = When the device is configured for CAS, it plays a local ringback tone to the PSTN upon receipt of a SIP 180 Ringing response (with or without SDP).
  • Page 935 User's Manual 66. Configuration Parameters Reference Parameter Description a local ringback tone if there are no prior received RTP packets. The device stops playing the local ringback tone as soon as it starts receiving RTP packets. At this stage, if the device receives additional 18x responses, it does not resume playing the local ringback tone.

  • Page 936: Tone Detection Parameters

    Mediant 800 MSBR Parameter Description the Progress message is received after a SIP REFER.  This parameter is applicable only if the parameter SendISDNTransferOnConnect is set to 1. Web: MFC R2 Category Defines the tone for MFC R2 calling party category (CPC). The EMS: R2 Category parameter provides information on the calling party such as CLI: mfcr2-category...
  • Page 937 User's Manual 66. Configuration Parameters Reference Parameter Description EMS: SIT Enable Enables SIT detection according to the ITU-T recommendation CLI: SIT-detector-enable E.180/Q.35. [SITDetectorEnable]  [0] = Disable (default)  [1] = Enable To disconnect IP-to-ISDN calls when a SIT tone is detected, the following parameters must be configured: ...

  • Page 938: Metering Tone Parameters

    Mediant 800 MSBR 66.11.9.3 Metering Tone Parameters The metering tone parameters are described in the table below. Metering Tone Parameters Parameter Description Web: Generate Determines the method used to configure the metering tones that are Metering Tones generated to the Tel side. EMS: Metering Mode ...

  • Page 939: Telephone Keypad Sequence Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description  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; ChargeCode 2 = 5,60,1,14,20,1,0,60,1; ChargeCode 3 = 0,60,1; ChargeCode 0 = 6, 3, 1, 12, 2, 1, 18, 5, 2, 0, 2, 1;...
  • Page 940 Mediant 800 MSBR Parameter Description 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 digits, including the prefix string, as "9123"...
  • Page 941 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Forward Unconditional Defines the keypad sequence to activate the immediate call EMS: Call Forward forward option. Unconditional CLI: fwd-unconditional [KeyCFUnCond] Web: Forward No Answer Defines the keypad sequence to activate the forward on no EMS: Call Forward No Answer answer option.

  • Page 942: General Fxo Parameters

    Mediant 800 MSBR Parameter Description dials after a configurable delay (terminate the number with #); a confirmation tone is heard. Web: Hot-line Deactivate Defines the keypad sequence to deactivate the delayed hotline EMS: Hot Line Deactivation option. After the sequence is pressed, a confirmation tone is CLI: hotline-deact heard.
  • Page 943 User's Manual 66. Configuration Parameters Reference Parameter Description  [CountryCoefficients] [66] Europe = TBR21  [70] USA = (Default) United States Note: For this parameter to take effect, a device reset is required. CLI: fxo-dc-termination Defines the FXO line DC termination (i.e., resistance). [FXODCTermination] ...
  • Page 944 Mediant 800 MSBR Parameter Description device dials the phone number (to the PSTN/PBX line) only after it detects a dial tone. If this parameter is disabled, the device immediately dials the phone number after seizing the PSTN/PBX line without 'listening' for a dial tone. Notes: ...

  • Page 945: Trunk Groups And Routing Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description detecting 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 Between Defines the time interval (in seconds) after a call has ended Calls...
  • Page 946 Mediant 800 MSBR Parameter Description EMS: SIP Routing > Hunt Trunk Group. The format of this parameter is as follows: Group [TrunkGroupSettings] CLI: configure voip > gw FORMAT TrunkGroupSettings_Index = hunt-or-trunk-group trunk- TrunkGroupSettings_TrunkGroupId, group-setting TrunkGroupSettings_ChannelSelectMode, [TrunkGroupSettings] TrunkGroupSettings_RegistrationMode, TrunkGroupSettings_GatewayName, TrunkGroupSettings_ContactUser, TrunkGroupSettings_ServingIPGroup, TrunkGroupSettings_MWIInterrogationType, TrunkGroupSettings_TrunkGroupName;...
  • Page 947 User's Manual 66. Configuration Parameters Reference Parameter Description of the incoming INVITE message is used.  [1] Layer 3 Source IP = The actual IP address (Layer 3) from where the SIP packet was received is used. Web: Use Source Number Determines the use of Tel Source Number and Display Name for As Display Name Tel-to-IP calls.
  • Page 948 Mediant 800 MSBR Parameter Description Outbound IP Routing Table Web: Outbound IP Routing This table parameter configures the Outbound IP Routing Table for Table routing Tel-to-IP and IP-to-IP calls. The format of this parameter is as EMS: SIP Routing > Tel to follows: [PREFIX] CLI: configure voip >...
  • Page 949 User's Manual 66. Configuration Parameters Reference Parameter Description addresses (in dotted-decimal notation format) that are defined in the Outbound IP Routing Table table or Proxy Set table, and rejects all other incoming calls. In addition, if an FQDN is defined in the routing table or Proxy Set table, the call is allowed to be sent only if the resolved DNS IP address appears in one of these tables;...
  • Page 950 Mediant 800 MSBR Parameter Description appropriate 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 used in routing tables to identify the network that serves the remote user when a call is routed over many different networks.

  • Page 951: Ip Connectivity Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description set to 1. [FaxReroutingDelay] Defines the maximum time interval (in seconds) that the device waits for CNG detection before re-routing calls identified as fax calls to fax destinations (terminating fax machine). The valid value range is 1-10. The default is 5. Web: ENUM Resolution Defines the ENUM service for translating telephone numbers to IP CLI: enum-service-domain...

  • Page 952: Alternative Routing Parameters

    Mediant 800 MSBR Parameter Description  CLI: alt-rte-tel2ip-method [1] SIP OPTIONS = The remote destination is considered offline if [AltRoutingTel2IPConnM the latest OPTIONS transaction timed out. Any response to an ethod] OPTIONS request, even if indicating an error, brings the connectivity status to online.
  • Page 953 User's Manual 66. Configuration Parameters Reference Parameter Description  [1] = Enable Web/EMS: Alternative Defines the duration (in milliseconds) for which the device plays a Routing Tone Duration tone to the endpoint on each attempt for Tel-to-IP alternative routing. [ms] When the device finishes playing the tone, a new SIP INVITE CLI: alt-rte-tone-duration message is sent to the new IP destination.

  • Page 954: Number Manipulation Parameters

    Mediant 800 MSBR Parameter Description routing fwd-on-bsy-trk-dest The format of this parameter is as follows: [ForwardOnBusyTrunkD [ForwardOnBusyTrunkDest] est] FORMAT ForwardOnBusyTrunkDest_Index = ForwardOnBusyTrunkDest_TrunkGroupId, ForwardOnBusyTrunkDest_ForwardDestination; [\ForwardOnBusyTrunkDest] For example, the below configuration forwards IP-to-Tel calls to destination user “112” at host IP address 10.13.4.12, port 5060, using transport protocol TCP, if Trunk Group ID 2 is unavailable: ForwardOnBusyTrunkDest 1 = 2, 112@10.13.4.12:5060;transport=tcp;...
  • Page 955 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Use EndPoint Number Enables the use of the B-channel number as the calling number (sent in As Calling Number Tel2IP the From field of the INVITE) instead of the number received in the EMS: Use EP Number As Q.931 Setup message, for Tel-to-IP calls.
  • Page 956 Mediant 800 MSBR Parameter Description Web: Set IP-to-TEL Defines the redirect reason for IP-to-Tel calls. If redirect (diversion) Redirect Reason information is received from the IP, the redirect reason is set to the CLI: ip2tel-redir-reason value of this parameter before the device sends it on to the Tel. [SetIp2TelRedirectReason ...
  • Page 957 User's Manual 66. Configuration Parameters Reference Parameter Description Web: Send Screening Overrides the screening indicator of the calling party's number for IP-to- Indicator to ISDN Tel ISDN calls. EMS: Screening Indicator  [-1] Not Configured = (Default) Not configured (interworking from IP To ISDN to ISDN).
  • Page 958 Mediant 800 MSBR Parameter Description manipulation of the original calling party number, using the Tel2IPSourceNumberMappingDialPlanIndex parameter), but before the regular calling or redirect number manipulation:  If a redirect number exists, it replaces the calling party number. If there is no redirect number, the calling number is left unchanged.
  • Page 959 User's Manual 66. Configuration Parameters Reference Parameter Description [AddNPIandTON2CallingN call. umber] For example: After receiving a Calling Number of 555, NPI of 1, and TON of 3, the modified number becomes 13555. This number can later be used for manipulation and routing. Web: Add NPI and TON to Determines whether NPI and TON are added to the Called Number for Called Number...
  • Page 960 Mediant 800 MSBR Parameter Description [SwapTel2IPCalled&Callin Determines whether the device swaps the calling and called numbers gNumbers] received from the Tel side (for Tel-to-IP calls). The SIP INVITE message contains the swapped numbers.  [0] = (Default) Disabled  [1] = Swap calling and called numbers Note: This parameter can also be configured in a Tel Profile.
  • Page 961 User's Manual 66. Configuration Parameters Reference Parameter Description CallingNameMapTel2Ip_DestinationPrefix, CallingNameMapTel2Ip_SourcePrefix, CallingNameMapTel2Ip_CallingNamePrefix, CallingNameMapTel2Ip_SrcTrunkGroupID, CallingNameMapTel2Ip_SrcIPGroupID, CallingNameMapTel2Ip_RemoveFromLeft, CallingNameMapTel2Ip_RemoveFromRight, CallingNameMapTel2Ip_LeaveFromRight, CallingNameMapTel2Ip_Prefix2Add, CallingNameMapTel2Ip_Suffix2Add; [ \CallingNameMapTel2Ip ] Note: For a detailed description of this table, see 'Configuring SIP Calling Name Manipulation' on page 310. Destination Phone Number Manipulation for IP-to-Tel Calls Table Web: Destination Phone This table parameter manipulates the destination number of IP-to-Tel Number Manipulation Table...
  • Page 962 Mediant 800 MSBR Parameter Description SrcIPGroupID; [\NumberMapTel2Ip] For example: NumberMapTel2Ip 0 = 01,$$,*,0,0,2,$$,$$,971,$$,$$,$$,$$; NumberMapTel2Ip 1 = 10,10,*,255,255,3,0,5,100,$$,255,$$,$$; Note: For a detailed description of this table, see 'Configuring Source/Destination Number Manipulation' on page 303. Source Phone Number Manipulation for IP-to-Tel Calls Table Web: Source Phone This parameter table manipulates the source number for IP-to-Tel calls.
  • Page 963 User's Manual 66. Configuration Parameters Reference Parameter Description SourceNumberMapTel2Ip_IsPresentationRestricted, NumberMapTel2Ip_SrcTrunkGroupID, NumberMapTel2Ip_SrcIPGroupID; [\SourceNumberMapTel2Ip] For example: SourceNumberMapTel2Ip 0 = 22,03,$$,0,0,$$,2,$$,667,$$,0,$$,$$; SourceNumberMapTel2Ip 0 = 10,10,*,255,255,3,0,5,100,$$,255,$$,$$; Note: For a detailed description of this table, see 'Configuring Source/Destination Number Manipulation' on page 303. Redirect Number IP -to-Tel Table Web: Redirect Number IP ->...

  • Page 964: Least Cost Routing Parameters

    Mediant 800 MSBR Parameter Description Phone Context Table Web: Phone Context Table This table parameter configures the Phone Context table. This EMS: SIP Manipulations > parameter maps NPI and TON to the SIP 'phone-context' parameter, Phone Context and vice versa. CLI: configure voip >...

  • Page 965: Ldap Parameters

    User's Manual 66. Configuration Parameters Reference Parameter Description For example: CostGroupTable 2 = "Local Calls", 2, 1; Note: For a detailed description of this table, see 'Configuring Cost Groups' on page 199. Web: Cost Group > Time This table parameter configures time bands and associates them Band Table with Cost Groups.
  • Page 966 Mediant 800 MSBR Parameter Description CLI: password For example: LDAPBindDN = "CN=Search [LDAPBindDN] user,OU=Labs,DC=OCSR2,DC=local" Note: The DN is used to uniquely name an Active Directory object. Web: LDAP Search Dn Defines up to three search DNs for LDAP search queries. These are EMS: Search DN the DN subtrees where the search is done.
  • Page 967 User's Manual 66. Configuration Parameters Reference Parameter Description Web: MS LDAP MOBILE Defines the name of the attribute that represents the user Mobile Number attribute name number in the Microsoft AD database. CLI: ldap-mobile-nm-attr The valid value is a string of up to 49 characters. The default is [MSLDAPMobileNumAttri "mobile".

  • Page 968: Sbc And Crp Parameters

    Mediant 800 MSBR 66.14 SBC and CRP Parameters The SBC and CRP parameters are described in the table below. SBC and CRP Parameters Parameter Description CRP-Specific Parameters Web: CRP Application Enables the CRP application. CLI: enable-crp  [0] Disable (default) [EnableCRPApplication] ...
  • Page 969 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: unclassified-calls processed. [AllowUnclassifiedCalls]  [0] Reject = Call is rejected if classification fails.  [1] Allow = (Default) If classification fails, the incoming packet is assigned to a source IP Group (and subsequently processed) as follows: ...
  • Page 970 Mediant 800 MSBR Parameter Description  [SBCAssertIdentity] [0] Don't Care = (Default) P-Asserted Identity header is not affected.  [1] Add P-Asserted-Identity Header = Adds a P-Asserted-Identity header. The header's values are taken from the source URL.  [2] Remove P-Asserted-Identity Header = Removes the P- Asserted-Identity header.
  • Page 971 User's Manual 66. Configuration Parameters Reference Parameter Description Note: This parameter can be configured in an IP Profile. CLI: sbc-xfer-prefix When the SBCReferBehavior is set to 1, the device, while [SBCXferPrefix] interworking the SIP REFER message, adds the prefix "T~&R-" to the user part of the URI in the Refer-To header.
  • Page 972 Mediant 800 MSBR Parameter Description  This parameter can also be configured as an IP Profile.  For more information on SIP 3xx Redirect response handling, see 'Handling SIP 3xx Redirect Responses' on page 442. Web: Enforce Media Order Enables the device to arrange media lines (‘m=’ line) in the SDP offer according to the previous offer-answer exchange (RFC 3264).
  • Page 973 User's Manual 66. Configuration Parameters Reference Parameter Description Web: SBC User Registration Defines the duration (in seconds) of the periodic registrations Time between the user and the device (the device responds with this value CLI: sbc-usr-reg-time to the user). When set to 0, the device does not change the Expires [SBCUserRegistrationTim header's value received in the user’s REGISTER request.
  • Page 974 Mediant 800 MSBR Parameter Description  [4] Both = The device provides temporary and public GRUU to users. (Currently not supported.) This parameter allows the device to act as a GRUU server for its SIP UA clients, providing them with public GRUU’s, according to RFC 5627.
  • Page 975 User's Manual 66. Configuration Parameters Reference Parameter Description  When No Media Anchoring is enabled:  Manipulation is not done on SDP data (offer/answer transaction) such as ports and IP addresses.  Opening voice channels and allocation of IP media ports are not required.
  • Page 976 Mediant 800 MSBR Parameter Description added at the end of the coder list.  [1] Include Extensions = Extension coders and Allowed coders are arranged according to their order of appearance in the Allowed Coders Group table. Note: If the SBCExtensionCodersGroupID parameter of the IP Profile table is set to None, then this parameter is not applicable.
  • Page 977 User's Manual 66. Configuration Parameters Reference Parameter Description SBCAdmissionControl_RequestDirection, SBCAdmissionControl_Limit, SBCAdmissionControl_LimitPerUser, SBCAdmissionControl_Rate, SBCAdmissionControl_MaxBurst; [\SBCAdmissionControl] For example, the below configuration allows a maximum of 10 concurrent SIP INVITEs for IP Group 1: SBCAdmissionControl 1 = 0, 1, -1, 1, 0, 10, -1, 0, 0; Note: For a detailed description of this table, see 'Configuring Admission Control' on page 458.
  • Page 978 Mediant 800 MSBR Parameter Description Note: For a detailed description of this table, see 'Configuring Classification Rules' on page 462. Condition Table Web: Condition Table This table parameter configures Condition rules for SIP messages CLI: configure voip > sbc using the same syntax as used in the SIP Message Manipulation routing condition-table table.
  • Page 979 User's Manual 66. Configuration Parameters Reference Parameter Description IP to IP Inbound Manipulation Table Web: IP to IP Inbound This table parameter configures the IP to IP Inbound Manipulation Manipulation table. This table allows you to manipulate the SIP URI user part EMS: IP to IP Inbound (source and/or destination) of the inbound SIP dialog message.

  • Page 980: Standalone Survivability Parameters

    Mediant 800 MSBR Parameter Description Note: For a detailed description of this table, see 'Configuring IP-to- IP Outbound Manipulations' on page 480. 66.15 Standalone Survivability Parameters The Stand-alone Survivability (SAS) parameters are described in the table below. SAS Parameters Parameter Description Web: Enable SAS Enables the Stand-Alone Survivability (SAS) feature.
  • Page 981 User's Manual 66. Configuration Parameters Reference Parameter Description Web: SAS Connection Enables the re-use of the same TCP connection for sessions with the Reuse same user in the SAS application. CLI: sas-connection-reuse  [0] Disable [SASConnectionReuse]  [1] Enable (default) The device can use the same TCP connection for multiple SIP requests / responses for a specific SIP UA.
  • Page 982 Mediant 800 MSBR Parameter Description SAS users. CLI: sas-contact-replace Enables the device to change the SIP Contact header so that it points [SASEnableContactRepl to the SAS host and therefore, the top-most SIP Via header and the ace] Contact header point to the same host. ...
  • Page 983 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: sas-emerg-nb includes one of the emergency numbers (in the SIP user part), it [SASEmergencyNumber forwards the INVITE to the default gateway (configured by the parameter SASDefaultGatewayIP), i.e., the device itself, which sends the call directly to the PSTN.

  • Page 984: Ip Media Parameters

    Mediant 800 MSBR Parameter Description "4002@10.33.4.226" (i.e., keep only four digits from right of user part): SASRegistrationManipulation 0 = 0, 4; Note: For a detailed description of this table, see 'Manipulating URI user part of Incoming REGISTER' on page 510. Web: SAS IP-to-IP Routing Table [IP2IPRouting] This table parameter configures the IP-to-IP Routing table for SAS...
  • Page 985 User's Manual 66. Configuration Parameters Reference Parameter Description For more information on Transcoding, see NetAnn Interface. Conferencing Parameters Web/EMS: Conference ID Defines the Conference Identification string. CLI: conf-id The valid value is a string of up to 16 characters. The default is "conf". [ConferenceID] Note: To join a conference, the INVITE URI must include the Conference ID string preceded by the number of the participants in...
  • Page 986 Mediant 800 MSBR Parameter Description  [AGCGainSlope] [1] 1 = 0.50 dB/sec  [2] 2 = 0.75 dB/sec  [3] 3 = 1.00 dB/sec (default)  [4] 4 = 1.25 dB/sec  [5] 5 = 1.50 dB/sec  [6] 6 = 1.75 dB/sec ...
  • Page 987 User's Manual 66. Configuration Parameters Reference Parameter Description adaptation Note: For this parameter to take effect, a device reset is required. [AGCDisableFastAdapta tion] Energy Detector Parameters Enable Energy Detector Enables the Energy Detector feature. This feature generates events CLI: energy-detector- (notifications) when the signal received from the PSTN is higher or enable lower than a user-defined threshold (defined by the...

  • Page 988: Auxiliary And Configuration File Name Parameters

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

  • Page 989: Automatic Update Parameters

    User's Manual 66. Configuration Parameters Reference 66.18 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Automatic Update of Software and Configuration Files Parameters Parameter Description General Automatic Update Parameters [AutoUpdateCmpFile] Enables the Automatic Update mechanism for the cmp file.
  • Page 990 Mediant 800 MSBR Parameter Description  [0] = (Default) The immediate restart mechanism is disabled.  [1] = The device immediately resets after an ini file with this parameter set to 1 is loaded. Software/Configuration File URL Path for Automatic Update Parameters CLI: firmware Defines the name of the cmp file and the path to the server (IP address [CmpFileURL]...
  • Page 991 User's Manual 66. Configuration Parameters Reference Parameter Description CLI: tls-root-cert Defines the name of the TLS trusted root certificate file and the URL [TLSRootFileUrl] from where it can be downloaded. Note: For this parameter to take effect, a device reset is required. CLI: tls-cert Defines the name of the TLS certificate file and the URL from where it [TLSCertFileUrl]...
  • Page 992 Mediant 800 MSBR Reader's Notes User's Manual Document #: LTRT-12809...

  • Page 993: Dsp Templates

    The device supports the following DSP firmware capabilities. Notes: • Installation and use of voice coders is subject to obtaining the appropriate license and royalty payments. • For additional DSP templates, contact your AudioCodes representative. Channel Capacity and Capabilities Advanced DSP Capabilities Telephony Channels Sessions...
  • Page 994 The Conference Participants column lists the number of participants in one or more conference (bridge), where each conference may include three or more participants. Conferences are supported on all above configurations. Please contact AudioCodes for the maximum number of participants per configuration. User's Manual...

  • Page 995: Technical Specifications

    The device's technical specifications are listed in the table below. Notes: • All specifications in this document are subject to change without prior notice. • The compliance and regulatory information can be downloaded from AudioCodes Web site at http://www.audiocodes.com/library. Technical Specifications Function Specification Capacity  RTP-RTP: 60 SBC Sessions ...
  • Page 996 Mediant 800 MSBR Function Specification Independent dynamic vocoder selection per channel Echo Cancellation G.165 and G.168-2002, with 32, 64 or 128 msec tail length Quality Enhancement Dynamic programmable jitter buffer, VAD, CNG DTMF/MF Tones Packet-side or PSTN-side detection and generation, RFC 2833 compliant DTMF relay and Call Progress tones Detection and Generation IP Transport VoIP (RTP/RTCP) per IETF RFC 3550 and 3551, IPv6...
  • Page 997 Control and Management Control Protocols SIP-TCP, SIP-UDP, SIP-TLS and SIP-MSCML* Cloud Resilience Package (CRP) and Standalone Survivability (SAS) for service continuity  AudioCodes' Element Management System (EMS) Operations & Management  Embedded HTTP Web Server, SNMP V2/V3  Telnet, SSH, TR-069 ...
  • Page 998 Mediant 800 MSBR Function Specification  Rapid Spanning Tree Protocol / RSTP (802.1D-2004 and 802.1w)  LAN switch ports with non-blocking switching performance  Up to four RJ-45 10/100/1000Base-T (Gigabit Ethernet) LAN ports  Eight RJ-45 10/100Base-TX (Fast Ethernet) LAN ports ...
  • Page 999 User's Manual 68. Technical Specifications Function Specification  Extensive list of ALG-modules combined with SPI for error-free configuration and maximum security  Port-forwarding and DMZ support for local applications and hosts  Website Restriction allows static URL-based blocking of public/extranet websites ...
  • Page 1000 Mediant 800 MSBR Function Specification  RFC 2406 ESP - IPsec Encryption  RFC 2407 IPsec DOI  RFC 2408 ISAKMP  RFC 2409 IKE  RFC 2410 IPsec Encryption – NULL  RFC 2411  RFC 2412 OAKLEY Hardware Specifications Single universal AC power supply 100-240V, 1.5A, 50-60 Hz Power Supply Physical Dimensions...
  • Page 1001 User's Manual 68. Technical Specifications Reader's Notes Version 6.6 1001 Mediant 800 MSBR...
  • Page 1002 User's Manual Ver. 6.6 www.audiocodes.com...

Table of Contents