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

AudioCodes Mediant 800B User Manual

Analog & digital voip media gateway
Hide thumbs Also See for Mediant 800B:
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
Table of Contents

Advertisement

Quick Links

See also: User Manual , Quick Manual
Mediant™ 800B Gateway & E-SBC
Enterprise Session Border Controller
Analog & Digital VoIP Media Gateway
User's Manual
Version 6.8
March 2014
Document # LTRT-10278

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 800B

Summary of Contents for AudioCodes Mediant 800B

  • Page 1 Mediant™ 800B Gateway & E-SBC Enterprise Session Border Controller Analog & Digital VoIP Media Gateway User's Manual Version 6.8 March 2014 Document # LTRT-10278...

  • Page 3: Table Of Contents

    Getting Familiar with CLI ..................65 7.1.1 Understanding Configuration Modes ............... 65 7.1.2 Using CLI Shortcuts ....................66 7.1.3 Common CLI Commands ..................67 7.1.4 Configuring Tables in CLI ..................68 7.1.5 Understanding CLI Error Messages ................ 69 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 4 Mediant 800B Gateway and E-SBC Enabling CLI ......................69 7.2.1 Enabling Telnet for CLI .................... 69 7.2.2 Enabling SSH with RSA Public Key for CLI ............. 70 Establishing a CLI Session ..................72 Configuring Maximum Telnet/SSH Sessions ............73 Viewing and Terminating Current CLI Sessions ............ 73 Configuring Displayed Output Lines in CLI Terminal Window .......
  • Page 5 14.2.2.3 Fax Fallback ..................162 14.2.2.4 Fax/Modem Bypass Mode ..............163 14.2.2.5 Fax / Modem NSE Mode ............... 164 14.2.2.6 Fax / Modem Transparent with Events Mode ........165 14.2.2.7 Fax / Modem Transparent Mode ............165 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 6 Mediant 800B Gateway and E-SBC 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......166 14.2.3 V.34 Fax Support ....................166 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........167 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ........... 168 14.2.3.3 V.34 Fax Relay for SG3 Fax Machines ..........168 14.2.4 V.150.1 Modem Relay ...................169...
  • Page 7 21.2.2.2 Configuring Internal Clock as Clock Source ......... 323 21.3 Configuring CAS State Machines ................. 323 21.4 Configuring Digital Gateway Parameters ............. 326 21.5 Tunneling Applications ..................327 21.5.1 TDM Tunneling ......................327 21.5.1.1 DSP Pattern Detector ................330 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 8 Mediant 800B Gateway and E-SBC 21.5.2 QSIG Tunneling .....................330 21.6 ISDN Non-Facility Associated Signaling (NFAS) ..........331 21.6.1 NFAS Interface ID ....................332 21.6.2 Working with DMS-100 Switches ................333 21.6.3 Creating an NFAS-Related Trunk Configuration ...........333 21.6.4 Performing Manual D-Channel Switchover in NFAS Group ........334 21.7 ISDN Overlap Dialing ...................
  • Page 9 26.11.4.1 About E9-1-1 Services ................420 26.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........421 26.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 26.11.4.4 Configuring AudioCodes ELIN Gateway ..........429 26.12 Multilevel Precedence and Preemption ..............431 26.12.1 MLPP Preemption Events in SIP Reason Header ..........433...
  • Page 10 Mediant 800B Gateway and E-SBC 27.10 Rejecting Anonymous Calls ................. 452 27.11 Configuring FXS Distinctive Ringing and Call Waiting Tones per Source/Destination Number ..................453 27.12 FXS/FXO Coefficient Types ................. 454 27.13 FXO Operating Modes ..................455 27.13.1 FXO Operations for IP-to-Tel Calls ................455 27.13.1.1 One-Stage Dialing .................
  • Page 11 31.3 Pre-Configured IP Groups ..................543 31.4 Pre-Configured IP-to-IP Routing Rules ..............544 31.4.1 Normal Mode ......................544 31.4.2 Emergency Mode ....................545 31.4.3 Auto Answer to Registrations ................545 31.5 Configuring PSTN Fallback .................. 546 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 12 Mediant 800B Gateway and E-SBC High-Availability System ..................547 32 HA Overview ....................549 32.1 Connectivity and Synchronization between Devices ..........549 32.2 Device Switchover upon Failure ................550 32.3 HA Status on the Home Page ................551 33 HA Configuration..................... 553 33.1 Initial HA Configuration ..................
  • Page 13 40.3.3 TFTP Configuration using DHCP Option 66 ............615 40.3.4 HTTP-based Automatic Updates ................615 40.3.5 Configuration using FTP or NFS ................616 40.3.6 Configuration using AudioCodes EMS ..............616 40.4 Loading Files Securely by Disabling TFTP ............616 41 Restoring Factory Defaults ................619 41.1 Restoring Defaults using CLI ................
  • Page 14 48 Syslog and Debug Recordings ..............669 48.1 Syslog Message Format ..................669 48.1.1 Event Representation in Syslog Messages ............670 48.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......672 48.1.3 SNMP Alarms in Syslog Messages ...............673 48.2 Enabling Syslog ....................673 48.3 Configuring Web Operations to Report to Syslog ..........
  • Page 15 54.6.1 IP Group, Proxy, Registration and Authentication Parameters ......748 54.6.2 Network Application Parameters ................760 54.7 General SIP Parameters ..................762 54.8 Coders and Profile Parameters ................789 54.9 Channel Parameters .................... 792 54.9.1 Voice Parameters ....................792 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 16 Mediant 800B Gateway and E-SBC 54.9.2 Coder Parameters ....................795 54.9.3 DTMF Parameters ....................795 54.9.4 RTP, RTCP and T.38 Parameters .................797 54.10 Gateway and IP-to-IP Parameters ............... 802 54.10.1 Fax and Modem Parameters .................802 54.10.2 DTMF and Hook-Flash Parameters ...............809 54.10.3 Digit Collection and Dial Plan Parameters .............813 54.10.4 Voice Mail Parameters ...................815...

  • Page 17: Weee Eu Directive

    User's Manual Notices Notice This document describes AudioCodes Mediant 800B Gateway & Enterprise Session Border Controller (E-SBC). Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.

  • Page 18: Related Documentation

    Mediant 800B Gateway and E-SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 800 Gateway and E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP Reference Guide SBC Design Guide Recommended Security Guidelines Configuration Note...
  • Page 19 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 20 Mediant 800B Gateway and E-SBC Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads. User's Manual...

  • Page 21: Overview

    User's Manual 1. Overview Overview AudioCodes' Mediant 800B Gateway and E-SBC (hereafter referred to as device) is a member of AudioCodes family of Enterprise Session Border Controllers (E-SBC), enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks.
  • Page 22 Mediant 800B Gateway and E-SBC The device provides up to 12 Ethernet ports (up to 4 Gigabit Ethernet ports and up to 8 Fast Ethernet ports). These ports operate in port-pair redundancy, providing up to 6 port- pair groups. The device allows full management through its HTTP/S-based embedded Web server. This user-friendly Web interface allows remote configuration using any standard Web browser (such as Microsoft™...

  • Page 23: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 25: Introduction

    User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 26 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 27: Default Oamp Ip Address

    Table 3-1: Default VoIP LAN IP Address for OAMP IP Address Value Application Type OAMP + Media + Control IP Address 192.168.0.2 Prefix Length 255.255.255.0 (24) Default Gateway 192.168.0.1 Underlying Device Interface Name "Voice" Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 28 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 29: Configuring Voip Lan Interface For Oamp

    IP address of the device; the Web interface's Web Login screen appears: Figure 4-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 30 Mediant 800B Gateway and E-SBC Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table) and then configure the device's physical Ethernet port-pair (group) that you want to later assign to the OAMP interface. For more information, see Configuring Physical Ethernet Ports on page 107.

  • Page 31: Cli

    Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Configure the Default Gateway address: (network-if-0)# gateway <IP address> Exit the Interface table: (network-if-0)# exit Exit the VoIP configuration mode: (config-voip)# exit Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 32 Mediant 800B Gateway and E-SBC Reset the device with a flash burn: # reload now Cable the device to your network. You can now access the device's management interface using this new OAMP IP address. User's Manual Document #: LTRT-10278...

  • Page 33: Management Tools

    Part II Management Tools...

  • Page 35: Introduction

    Web, CLI, and ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 707. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 36 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 37: Web-Based Management

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

  • Page 38: Accessing The Web Interface

    Mediant 800B Gateway and E-SBC 6.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see ''Computer Requirements'' on page 37). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 39: Areas Of The Gui

    ''Navigation Tree'' on page 41. Work pane, displaying the configuration page of the selected menu in the Navigation tree. This is where configuration is done. For more information, see ''Working with Configuration Pages'' on page 43. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 40: Toolbar Description

    Mediant 800B Gateway and E-SBC 6.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Table 6-2: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see ''Saving Configuration'' on page 568).

  • Page 41: Navigation Tree

    The expanded view displays all the menus pertaining to the selected configuration tab; the reduced view displays only commonly used menus.  To display a reduced menu tree, select the Basic option (default). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 42: Showing / Hiding The Navigation Pane

    Mediant 800B Gateway and E-SBC  To display all menus and submenus, select the Advanced option. Figure 6-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 6.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 43: Working With Configuration

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

  • Page 45: Modifying And Saving Parameters

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

  • Page 46: Working With Tables

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

  • Page 47: Searching For Configuration Parameters

    The search key can include the full parameter name (e.g., "EnableSyslog") or a substring of it (e.g., "sys"). If you search for a substring, all parameters containing the specified substring in their names are listed in the search result. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 48 Mediant 800B Gateway and E-SBC  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 49: Creating A Login Welcome Message

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

  • Page 50: Getting Help

    Mediant 800B Gateway and E-SBC 6.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 51: Logging Off The Web Interface

     To access the Home page:  On the toolbar, click the Home icon. Note: The displayed number and type of telephony interfaces depends on the ordered hardware configuration. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 52 Mediant 800B Gateway and E-SBC 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 53 (gray): Link is not configured  (red): Link error To view detailed port information, click the port icon (see Viewing Ethernet Port Information on page 625). Fast Ethernet port status icons. See Item 6 for a description. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 54: Assigning A Port Name

    Mediant 800B Gateway and E-SBC 6.2.1 Assigning a Port Name You can configure an arbitrary name or a brief description for each telephony port displayed on the Home page. This description is displayed as a tooltip when you hover your mouse over the port.
  • Page 55 In the 'Deny Authentication Timer' field, enter the interval (in seconds) that the user needs to wait before a new login attempt from the same IP address can be done after reaching the number of failed login attempts (defined in the previous step). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 56: Basic User Accounts Configuration

    Mediant 800B Gateway and E-SBC Notes: • For security, it's recommended that you change the default username and password of the pre-configured users (i.e., Security Administrator and Monitor users). • The Security Administrator user can change all attributes of all Web user accounts.
  • Page 57 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. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 58: Advanced User Accounts Configuration

    Mediant 800B Gateway and E-SBC 6.3.2 Advanced User Accounts Configuration The Web Users table lets you configure advanced Web user accounts. This configuration is relevant only if you need the following management schemes:  Enhanced security settings per Web user (e.g., limit session duration) ...
  • Page 59 'Deny Access on Fail Count' parameter (see ''Configuring Web Security Settings'' on page 62). These users can log in only after a user- defined timeout configured by the 'Block Duration' parameter (see Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 60 Mediant 800B Gateway and E-SBC Parameter Description below) or if their status is changed (to New or Valid) by a System Administrator or Master.  Old Account = This state is automatically set for users that have not accessed the Web interface for a user-defined number of days, set by the 'User Inactivity Timer' (see ''Configuring Web Security Settings'' on page 62).

  • Page 61: Displaying Login Information Upon Login

    From the 'Display Login Information' drop-down list, select Yes. Click Submit. Once enabled, the Login Information window is displayed upon a successful login, as shown in the example below: Figure 6-20: Login Information Window Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 62: Configuring Web Security Settings

    - 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-10278...

  • Page 63: Configuring Web And Telnet Access List

    IP address, and then click Add New Entry; the IP address you entered is added as a new entry to the Web & Telnet Access List table. Figure 6-22: Web & Telnet Access List Table Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 64 Mediant 800B Gateway and E-SBC To delete authorized IP addresses, select the Delete Row check boxes corresponding to the IP addresses that you want to delete, and then click Delete Selected Addresses; the IP addresses are removed from the table and these IP addresses can no longer access the Web and Telnet interfaces.

  • Page 65: Cli-Based Management

    Enable mode upon initial login. For configuring user access levels, see Configuring Web User Accounts on page 54. • The default password for accessing the Enable mode is "Admin" (case-sensitive). To change this password, use the CLIPrivPass ini file parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 66: Using Cli Shortcuts

    Mediant 800B Gateway and E-SBC The Enable mode groups the configuration commands under the following command sets: • config-system: Provides the general and system related configuration commands, for example, Syslog configuration. This set is accessed by typing the following command:...

  • Page 67: Common Cli Commands

    | <filter> Applied to a command output. The filter should be typed after the command with a pipe mark (|). Supported filters:  include <word> – filter (print) lines which contain <word> Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 68: Configuring Tables In Cli

    Mediant 800B Gateway and E-SBC Command Description  exclude <word> – filter lines which does not contain <word>  grep <options> - filter lines according to grep common Unix utility options  egrep <options> - filter lines according to egrep common Unix utility options ...

  • Page 69: Understanding Cli Error Messages

    For security, some organizations require the display of a proprietary notice upon starting a Telnet session. You can use the configuration ini file parameter, WelcomeMessage to configure such a message (see ''Creating a Login Welcome Message'' on page 49). Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC  To enable Telnet: Open the Telnet/SSH Settings page (Configuration tab > System menu > Management > Telnet/SSH Settings). Set the ‘Embedded Telnet Server’ parameter to Enable Unsecured or Enable Secured (i.e, SSL). Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 711.
  • Page 71 Under the 'Authentication parameters' group, click Browse and then locate the private key file that you created and saved in Step 4. Connect to the device with SSH using the username "Admin"; RSA key negotiation occurs automatically and no password is required. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 72: Establishing A Cli Session

    Mediant 800B Gateway and E-SBC  To configure RSA public keys for Linux (using OpenSSH 4.3): Run the following command to create a new key in the admin.key file and to save the public portion to the admin.key.pub file: ssh-keygen -f admin.key -N "" -b 1024 Open the admin.key.pub file, and then copy the encoded string from "ssh-rsa"...

  • Page 73: Configuring Maximum Telnet/Ssh Sessions

    When this command is run, it ends the Telnet/SSH session (logs out the RS-232 session) and displays the CLI login prompt. Note: The session from which the command is run cannot be terminated. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be specified from 0 to 65,535, or determined by re-sizing the terminal window by mouse- dragging the window's border.

  • Page 75: Snmp-Based Management

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

  • Page 76: Configuring Snmp Trap Destinations

    Mediant 800B Gateway and E-SBC  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String). Configure SNMP community strings according to the table below. Click Submit, and then save ("burn") your settings to flash memory.
  • Page 77 (default) = SNMPv2 user community string  SNMPv3 user configured in ''Configuring SNMP V3 Users'' on page Trap Enable Activates the sending of traps to the SNMP Manager. [SNMPManagerTrapSendingEnable_x]  [0] Disable  [1] Enable (Default) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 78: Configuring Snmp Trusted Managers

    Mediant 800B Gateway and E-SBC Configuring SNMP Trusted Managers The SNMP Trusted Managers table lets you configure up to five SNMP Trusted Managers based on IP addresses. By default, the SNMP agent accepts SNMP Get and Set requests from any IP address as long as the correct community string is used in the request.

  • Page 79: Configuring Snmp V3 Users

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

  • Page 81: Ini File-Based Management

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

  • Page 83: General Ini File Formatting Rules

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

  • Page 84: Loading An Ini File To The Device

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

  • Page 85: Ini Viewer And Editor Utility

    PC, the password is displayed obscured (i.e., $1$<obscured password>). INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any...
  • Page 86 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 87: General System Settings

    Part III General System Settings...

  • Page 89: Configuring Certificates

    Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 90 Mediant 800B Gateway and E-SBC When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows:  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for...
  • Page 91 TLS version supported by both peers.  [1] 1 = Only TLS 1.0 is used. Clients attempting to contact the device using any other version are rejected. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 92 Mediant 800B Gateway and E-SBC Parameter Description Web: Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher CLI: ciphers-server list format). [TLSContexts_Serve For valid values, refer to URL rCipherString] http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).

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

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

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

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

  • Page 95: Generating Private Keys For Tls Contexts

    Figure 10-5: Generate new private key and self-signed certificate Group From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys: • • 1024 (default) • 2048 Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC Click Generate Private Key; a message appears requesting you to confirm key generation. Click OK to confirm key generation; the device generates a new private key, indicated by a message in the Certificate Signing Request group.

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

    In the TLS Contexts table, select the required TLS Context index row, and then click the Context Trusted-Roots button, located at the bottom of the TLS Contexts page; the Trusted Certificates page appears. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 98: Configuring Mutual Tls Authentication

    Mediant 800B Gateway and E-SBC Click the Import button, and then select the certificate file to load. Figure 10-9: Importing Certificate into Trusted Certificates Store Click OK; the certificate is loaded to the device and listed in the Trusted Certificates store.

  • Page 99: Tls For Remote Device Management

    HTTPSRootFileName ini file parameter. • You can enable the device to check whether a peer's certificate has been revoked by an OCSP server, per TLS Context (see 'Configuring TLS Certificate Contexts' on page 89). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 100: Configuring Tls Server Certificate Expiry Check

    Mediant 800B Gateway and E-SBC 10.1.8 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure...

  • Page 101: Date And Time

    The client slowly robs bits from the clock counter to update the clock to the correct Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 102 Mediant 800B Gateway and E-SBC time. If the clock is running too slow, then in an effort to catch the clock up, bits are added 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.
  • Page 103 Verify that the device is set to the correct date and time. You can do this by viewing the date and time in the Regional Settings page, as described in ''Configuring Date and Time Manually'' on page 101. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 104 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 105: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 107: Network

    DOWN The following procedure describes how to configure the Ethernet ports in the Web interface. You can also configure these ports using the table ini file parameter, PhysicalPortsTable or CLI command, configure voip/physical-port. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 108 Mediant 800B Gateway and E-SBC  To configure the physical Ethernet ports: Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table). Select a port that you want to configure by clicking its table row, and then click Edit;...

  • Page 109: Configuring Ethernet Port Groups

    'Configuring Physical Ethernet Ports' on page 107. The following procedure describes how to configure Tx/Rx mode in the Web interface. You can also configure this using the table ini file parameter, EtherGroupTable or CLI command, configure voip/ether-group. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 110 Mediant 800B Gateway and E-SBC  To configure Ethernet Groups: Open the Ethernet Group Settings page (Configuration tab > VoIP menu > Network > Ethernet Groups Table). Select an Ethernet Group that you want to configure, and then click Edit; the following...

  • Page 111: Configuring Underlying Ethernet Devices

    IP network interface can it be deleted. The following procedure describes how to configure Ethernet devices in the Web interface. You can also configure this using the table ini file parameter, DeviceTable or CLI command, config-voip > interface network-dev. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 112 Mediant 800B Gateway and E-SBC  To configure an Ethernet Device: Open the Ethernet Device Table page (Configuration tab > VoIP menu > Network > Ethernet Device Table). Click Add; the following dialog box appears: Configure an Ethernet Device according to the parameters described in the table below.

  • Page 113: Configuring Ip Network Interfaces

    HA and the Maintenance interface, see Configuring High Availability on page 548.  IP address (IPv4 and IPv6) and subnet mask (prefix length)  For configuring Quality of Service (QoS), see ''Configuring the QoS Settings'' on page 124. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 114 Mediant 800B Gateway and E-SBC  Default Gateway: Traffic from this interface destined to a subnet that does not meet any of the routing rules (local or static) are forwarded to this gateway  Primary and secondary domain name server (DNS) addresses (optional) ...
  • Page 115 The CIDR- style presentation is the latest method for interpretation of IP addresses. Specifically, instead of using eight-bit address blocks, it uses the variable-length subnet masking technique to allow allocation on arbitrary-length prefixes. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 116: Assigning Ntp Services To Application Types

    Mediant 800B Gateway and E-SBC Parameter Description The prefix length for IPv4 must be set to a value from 0 to 30. The prefix length for IPv6 must be set to a value from 0 to 64. Web/EMS: Default Gateway Defines the IP address of the default gateway for the interface.

  • Page 117: Networking Configuration Examples

    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: Table 12-6: Example of Static Route Table Destination Prefix Length Gateway 201.201.0.0 192.168.11.10 202.202.0.0 192.168.11.1 The NTP applications remain with their default application types. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 118: Voip Interface Per Application Type

    Mediant 800B Gateway and E-SBC 12.4.3.2 VoIP Interface per Application Type This example describes the configuration of three VoIP interfaces; one for each application type: Interface table: Configured with three interfaces, each for a different application type, i.e., one for OAMP, one for Call Control, and one for RTP Media, and each with a...
  • Page 119 For Gold Service class, the default DiffServ value is set to 26 ♦ For Bronze Service class, the default DiffServ value is set to 10 Figure 12-5: Example of Layer-2 QoS in DiffServ Table Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 120: Voip Interfaces With Multiple Default Gateways

    Mediant 800B Gateway and E-SBC 12.4.3.4 VoIP Interfaces with Multiple Default Gateways Below is a configuration example using default gateways per IP network interface. In this example, the default gateway for OAMP is 192.168.0.1 and for Media and Control it is 200.200.85.1.
  • Page 121 For example, the value 16 represents subnet 255.255.0.0. The value must be 0 to 31 for IPv4 interfaces and a value of 0 to 64 for IPv6 interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 122: Configuration Example Of Static Ip Routes

    Mediant 800B Gateway and E-SBC Parameter Description The address of the host/network you want to reach is determined by an AND operation that is applied to the fields 'Destination' and 'Prefix Length'. For example, to reach the network 10.8.x.x, enter 10.8.0.0 in the 'Destination' field and 16 in the 'Prefix Length'. As a result of the AND operation, the value of the last two octets in the 'Destination' field is ignored.

  • Page 123: Troubleshooting The Routing Table

    To restore connectivity, the device must be accessed locally from the OAMP subnet and the required routes be configured. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 124: Configuring Quality Of Service

    Mediant 800B Gateway and E-SBC 12.6 Configuring Quality of Service The QoS Settings page lets you configure Layer-2 and Layer-3 Quality of Service (QoS). Differentiated Services (DiffServ) is an architecture providing different types or levels of service for IP traffic. DiffServ (according to RFC 2474), prioritizes certain traffic types based on priority, accomplishing a higher-level QoS at the expense of other traffic types.
  • Page 125 Defines the VLAN priority level. CLI: vlan-priority The valid value is 0 to 7. [DiffServToVlanPriority_VlanPriority] Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS. Figure 12-8: QoS Settings Page - Differentiated Services Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 126: Configuring Icmp Messages

    Mediant 800B Gateway and E-SBC 12.7 Configuring ICMP Messages Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol suite. It is used by network devices such as routers to send error messages indicating, for example, that a requested service is unavailable.
  • Page 127 Defines the second IP address (in dotted-decimal format notation) CLI: second-ip-address to which the host name is translated. [Dns2Ip_SecondIpAddress] Third IP Address Defines the third IP address (in dotted-decimal format notation) to CLI: third-ip-address which the host name is translated. [Dns2Ip_ThirdIpAddress] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 128: Configuring The Internal Srv Table

    Mediant 800B Gateway and E-SBC Parameter Description Fourth IP Address Defines the fourth IP address (in dotted-decimal format notation) to CLI: fourth-ip-address which the host name is translated. [Dns2Ip_FourthIpAddress] 12.8.2 Configuring the Internal SRV Table The Internal SRV table resolves host names to DNS A-Records. Three different A-Records can be assigned to each host name, where each A-Record contains the host name, priority, weight, and port.
  • Page 129 Weight (1-3) Defines a relative weight for records with the same priority. CLI: weight-1|2|3 [Srv2Ip_Weight1/2/3] Port (1-3) Defines the TCP or UDP port on which the service is to be found. CLI: port-1|2|3 [Srv2Ip_Port1/2/3] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 130: Open Solution Network (Osn) Server

    Mediant 800B Gateway and E-SBC 12.9 Open Solution Network (OSN) Server This section describes various networking settings for the OSN server. Notes: • The OSN is a customer-ordered item. • For information on cabling the OSN, refer to the device's Hardware Installation Manual.

  • Page 131: Configuring Nfs Settings

    The combination of 'Host Or IP' and 'Root Path' must be unique for each row in the table. For example, the table must include only one row with a Host/IP of 192.168.1.1 and Root Path of /audio. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 132: Network Address Translation Support

    Mediant 800B Gateway and E-SBC Table 12-17: NFS Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. Note: Each table row must be configured with a unique index. Host Or IP The domain name or IP address of the NFS server. If a domain name is CLI: host provided, a DNS server must be configured.

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

    The following procedure describes how to configure a static NAT address in the Web interface. You can also configure this using the ini file parameter, StaticNATIP or CLI command, configure voip > sip-definition general-settings > nat-ip-addr. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 134: Configuring Nat Translation Per Ip Interface

    Mediant 800B Gateway and E-SBC  To configure a single static NAT IP address: Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Figure 12-14: Configuring Static NAT IP Address in SIP General Parameters Page In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation.

  • Page 135: Remote Ua Behind Nat

    INVITE (to the endpoint), using the the source IP address of the packet (INVITE) initially received from the endpoint. This is especially useful in scenarios where the endpoint is located behind a NAT firewall and the device (for whatever Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC reason) is unable to identify NAT using its regular NAT Detection mechanism. This feature is enabled per specific calls using IP Groups. To configure this feature, use the 'Always Use Source Address' parameter in the IP Group table (see ''Configuring IP Groups'' on page 248).

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

    Receipt of No-Op packets is always supported. 12.12 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device.
  • Page 138 Mediant 800B Gateway and E-SBC Latching onto a new T.38 stream is reported in CDR using the CDR fields, LatchedT38Ip (new IP address) and LatchedT38Port (new port). In addition, the SIP PUBLISH message updates the latched RTP SSRC, for example: RemoteAddr: IP=10.33.2.55 Port=4000 SSRC=0x66d510ec...

  • Page 139: Multiple Routers Support

    Using multiple router support, the device can utilize these router messages to change its next hop and establish the best path. Note: Multiple Routers support is an integral feature that doesn’t require configuration. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 140 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 141: Security

    If you are using the High Availability feature and you have configured "block" rules, ensure that you also add "allow" rules for HA traffic. For more information, see Configuring Firewall Allowed Rules on page 559. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 142 Mediant 800B Gateway and E-SBC The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList or the CLI command, configure voip/access-list.  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab >...
  • Page 143 The list displays interface names as defined in the Interface table in [AccessList_Interface_x] ''Configuring IP Network Interfaces'' on page 113. Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 144 Mediant 800B Gateway and E-SBC Parameter Description [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment. Byte Rate Defines the expected traffic rate (bytes per second), i.e., the allowed CLI: byte-rate bandwidth for the specified protocol.

  • Page 145: Configuring General Security Settings

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

  • Page 146: Intrusion Detection System

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

  • Page 147: Enabling Ids

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

  • Page 151: Assigning Ids Policies

    A hyphen "-" indicates a range of SIP Interfaces (e.g., 3,4-7 means IDs 3, and 4 through 7)  A prefix of an exclamation mark "!" means negation of the set (e.g., !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 152: Viewing Ids Alarms

    Mediant 800B Gateway and E-SBC Parameter Description Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This CLI: proxy-set indicates the Proxy Sets from where the attacks are coming from. The [IDSMatch_ProxySet] following syntax is supported: ...
  • Page 153  malformed-header- overflow   Local authentication ("Bad digest" errors) auth-establish-fail Authentication Failure   Remote authentication (SIP 401/407 is sent if auth-reject-response original message includes authentication)   Classification failure establish-classify-fail Dialog Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 154 Mediant 800B Gateway and E-SBC Type Description Syslog String   Establishment Routing failure establish-route-fail Failure   Other local rejects (prior to SIP 180 response) establish-local-reject   Remote rejects (prior to SIP 180 response) establish-remote- reject  ...

  • Page 155: Media

    When silence is detected, it stops sending packets in the channel. The following procedure describes how to enable silence suppression using the Web interface. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 156: Echo Cancellation

    Mediant 800B Gateway and E-SBC  To enable silence suppression using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 14-2: Enabling Silence Suppression in Voice Settings Page Set the 'Silence Suppression' (EnableSilenceCompression) field to Enable.

  • Page 157: Fax And Modem Capabilities

    Some SIP parameters override these fax and modem parameters. For example, the IsFaxUsed parameter and V.152 parameters in Section ''V.152 Support'' on page 171. • For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 707. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 158 Mediant 800B Gateway and E-SBC  To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Configuration tab > VoIP menu > Media > Fax/Modem/CID Settings). Configure the parameters, as required. Click Submit. User's Manual Document #: LTRT-10278...

  • Page 159: Fax/Modem Operating Modes

    You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). This parameter does not affect the actual transmission rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 160 Mediant 800B Gateway and E-SBC 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 161 RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...

  • Page 162: Fax / Modem Transport Mode

    Mediant 800B Gateway and E-SBC 14.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 163: Fax/Modem Bypass Mode

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

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

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

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

    Mediant 800B Gateway and E-SBC Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0).

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

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

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

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

  • Page 169: Modem Relay

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

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

    Mediant 800B Gateway and E-SBC format to negotiate V.150 modem relay using the same port as RTP, as shown in the example below: a=cdsc:1 audio udpsprt 114\r\n a=cpar:a=sprtmap:114 v150mr/8000\r\n a=cpar:a=fmtp:114 mr=1;mg=0;CDSCselect=1;mrmods=1,3;jmdelay=no;versn=1.1\r\n\ You can configure the payload type for the outgoing SDP offer, using the NoAudioPayloadType parameter.

  • Page 171: Support

    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 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 172: Configuring Rtp/Rtcp Settings

    Mediant 800B Gateway and E-SBC least one IP packet from the LAN to the WAN through the firewall. If the firewall blocks T.38 packets sent from the termination IP fax, the fax fails. To overcome this, the device sends No-Op (“no-signal”) packets to open a pinhole in the NAT for the answering fax machine.

  • Page 173: Comfort Noise Generation

    RTP/RTCP Settings). The relevant parameters are listed under the 'General Settings' group, as shown below: Figure 14-4: Comfort Noise Parameter in RTP/RTCP Settings Page Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Click Submit. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 174: Dual-Tone Multi-Frequency Signaling

    Mediant 800B Gateway and E-SBC 14.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 14.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 &...

  • Page 175: Configuring Rfc 2833 Payload

    'RFC 2833 RX Payload Type' (RFC2833RxPayloadType) - defines the Rx RFC 2833 DTMF relay dynamic payload type. • 'RFC 2198 Payload Type' (RFC2198PayloadType) - defines the RTP redundancy packet payload type according to RFC 2198. Click Submit. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 176: Configuring Rtp Base Udp Port

    Mediant 800B Gateway and E-SBC 14.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 177: Configuring Ip Media Settings

    'AGC Target Energy' - Defines the signal energy value (dBm) that the AGC attempts to attain. When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. This parameter can either be the global parameter or per IP Profile. Click Submit. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 178: Configuring Various Codec Attributes

    Mediant 800B Gateway and E-SBC Note: Below are additional AGC parameters: • AGCMinGain - Defines the minimum gain (in dB) by the AGC when activated • AGCMaxGain - Defines the maximum gain (in dB) by the AGC when activated. •...

  • Page 179: Configuring Media (Srtp) Security

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

  • Page 181: Services

    Session (RS) from the Session Recording Client (SRC), which is on the path of the Communication Session (CS), to a Session Recording Server (SRS) at the recording equipment. The device functions as the SRC, sending recording sessions to a third-party SRS, as shown in the figure below. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 182 Mediant 800B Gateway and E-SBC The device can record calls between two IP Groups. The type of calls to record can be specified by source and/or destination prefix number or SIP Request-URI, as well as by call initiator. The side ("leg") on which the recording is done must be specified. This recording leg must be one that is interfacing with one of the IP Groups.
  • Page 183 </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 184: Enabling Sip-Based Media Recording

    Mediant 800B Gateway and E-SBC <label>1</label> </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label> </stream> </recording> --boundary_ac1fffff85b— 15.1.1 Enabling SIP-based Media Recording The following procedure describes how to enable the SIP-based media Recording feature. Once you have enabled this feature, your SIP Recording Routing rules (configured in ''Configuring SIP Recording Routing Rules'' on page 184) become active.
  • Page 185 SIP Interfaces are associated with the SRD - one for "SBC" and one for "GW &IP2IP" – the device uses the "SBC" SIP Interface. If no SBC SIP Interface type is configured, the device uses the “GW & IP2IP” interface. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 186: Configuring Sip User Part For Srs

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

  • Page 187: Radius Authentication

    FreeRADIUS, which can be downloaded from www.freeradius.org. Follow the instructions on this Web site for installing and configuring the server. If you use a RADIUS server from a different vendor, refer to its appropriate documentation. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 188 Mediant 800B Gateway and E-SBC  To set up a third-party RADIUS server (e.g., FreeRADIUS): Define the AudioCodes device as an authorized client of the RADIUS server, with the following: • Predefined shared secret (password used to secure communication between the device and the RADIUS server) •...

  • Page 189: Configuring Radius Authentication

    If the RADIUS server response does not include the access level attribute: In the 'Default Access Level' field, enter the default access level that is applied to all users authenticated by the RADIUS server. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 190: Securing Radius Communication

    Mediant 800B Gateway and E-SBC Configure RADIUS timeout handling: From the 'Behavior upon Authentication Server Timeout' drop-down list, select the option if the RADIUS server does not respond within five seconds: ♦ Deny Access: device denies user login access. ♦...

  • Page 191: Ldap-Based Management And Sip Services

    CN=\# Support Dept,OU=R&D Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=a bc,DC=com The device then assigns the user the access level configured for that group (in 'Configuring Access Level per Management Groups Attributes' on page 198). The Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 192: Enabling The Ldap Service

    Mediant 800B Gateway and E-SBC location in the directory where you want to search for the user's member group(s) is configured using the following: • Search base object (distinguished name or DN, e.g., "ou=ABC,dc=corp,dc=abc,dc=com"), which defines the location in the directory from where the LDAP search begins, and is configured in 'Configuring LDAP DNs (Base Paths) per LDAP Server' on page 196.

  • Page 193: Configuring Ldap Servers

    Configure an LDAP server according to the parameters described in the table below. Click Submit. LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [LdapConfiguration_In Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 194 Mediant 800B Gateway and E-SBC Parameter Description dex] Note: Each table row must be configured with a unique index. LDAP Server IP Defines the IP address of the LDAP server (in dotted-decimal notation, CLI: server-ip e.g., 192.10.1.255). [LdapConfiguration_Ld By default, no IP address is defined.
  • Page 195 (i.e., the 'Type' parameter is set to Management).  If this functionality is not used, the device assigns the user the configured default access level. For more information, see 'Configuring Access Level per Management Groups Attributes' on page 198. Version 6.8 Mediant 800B Gateway and E-SBC...

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

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

  • Page 197: Configuring The Ldap Search Filter Attribute

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

  • Page 198: Configuring Access Level Per Management Groups Attributes

    Mediant 800B Gateway and E-SBC  To configure the LDAP search filter for management users: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 15-8: LDAP Settings Page - LDAP Search Filter Under LDAP Settings, in the 'LDAP Authentication Filter' parameter, enter the LDAP search filter attribute for searching the login username for user authentication.
  • Page 199 Note: Each table row must be configured with a unique index. GroupIndex] Level Defines the access level of the group(s). [MgmntLDAPGroups_L  [0] Monitor (Default) evel]  [1] Security Administrator  [2] Administrator Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 200: Configuring Ldap Search Methods

    Mediant 800B Gateway and E-SBC Parameter Description Groups Defines the attribute names of the groups in the LDAP server. [MgmntLDAPGroups_ The valid value is a string of up to 256 characters. To define multiple Group] groups, separate each group name with a semicolon (;).
  • Page 201 However, for subsequent queries, the device does not use the partially cached result, but does a new query with the LDAP server again. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 202: Configuring Local Database For Management User Authentication

    Mediant 800B Gateway and E-SBC The following procedure describes how to configure the device's LDAP cache in the Web interface. For a full description of the cache parameters, see 'LDAP Parameters' on page 951.  To configure the LDAP cache: Open the LDAP Settings page (Configuration tab >...
  • Page 203 Server Timeout' drop-down list, select one of the following: ♦ Deny Access: User is denied access to the management platform. ♦ Verify Access Locally (default): The device verifies the user's credentials in the Web Users table. Click Submit. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 204: Ldap-Based Login Authentication Example

    Mediant 800B Gateway and E-SBC 15.3.10 LDAP-based Login Authentication Example To facilitate your understanding on LDAP entry data structure and how to configure the device to use and obtain information from this LDAP directory, a brief configuration example is described in this section. The example applies to LDAP-based user login authentication and authorization (access level), and assumes that you are familiar with other aspects of LDAP configuration (e.g., LDAP server's address).
  • Page 205 (where the attribute's value equals the username): Figure 15-15: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-16: User's memberOf Attribute Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 206 Mediant 800B Gateway and E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-17: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...

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

    PBX or IP PBX - users not yet migrated to Lync Server  Mobile - mobile number  Private - private telephone line for Lync users (in addition to the primary telephone line) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 208: Querying The Ad And Routing Priority

    Mediant 800B Gateway and E-SBC 15.3.11.1 Querying the AD and Routing Priority The device queries the AD using the initial destination number (i.e., called number). The query can return up to four user phone numbers, each pertaining to one of the IP domains (i.e., private number, Lync number, PBX / IP PBX number, and mobile number).
  • Page 209 Lync Server, if the PBX / IP PBX system is unavailable or has failed, the device uses the AD query result for the user’s mobile phone number, routing the call through the PSTN to the mobile destination. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 210: Configuring Ad-Based Routing Rules

    Mediant 800B Gateway and E-SBC The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 15-22: 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 211 LDAP server. For alternative routing, enable the alternative routing mechanism and configure corresponding SIP reasons for alternative routing. For this feature, alternative routing starts from the table row located under the LDAP query row. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 212 Mediant 800B Gateway and E-SBC 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...

  • Page 213: Querying The Ad For Calling Name

    The Calling Name Manipulation Table for Tel -> IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 214: Least Cost Routing

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

  • Page 216: Configuring Lcr

    Mediant 800B Gateway and E-SBC  Example 3: This example shows how the cost of a call is calculated if the call spans over multiple time bands: Assume a Cost Group, "CG Local" is configured with two time bands, as shown below:...
  • Page 217 (default.)  [1] Highest Cost = If the device locates other matching LCR routing rules, this routing rule is considered as the Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 218: Configuring Cost Groups

    Mediant 800B Gateway and E-SBC Parameter Description highest cost route and therefore, is not used or used only if the other cheaper routes are unavailable. Note: If more than one valid routing rule without a defined Cost Group exists, the device selects the first-matched rule.

  • Page 219: Configuring Time Bands For Cost Groups

    Click Submit, and then save ("burn") your settings to flash memory. Table 15-5: Time Band Table Description Parameter Description Index Defines an index number for the new table record. CLI: timeband-index Note: Each table row must be configured with a unique index. [CostGroupTimebands_Time Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 220: Assigning Cost Groups To Routing Rules

    Mediant 800B Gateway and E-SBC Parameter Description bandIndex] Start Time Defines the day and time of day from when this time band is CLI: start-time applicable. The format is DDD:hh:mm, where: [CostGroupTimebands_StartT  DDD is the day of the week, represented by the first three letters ime] of the day in upper case (i.e., SUN, MON, TUE, WED, THU,...

  • Page 221: Configuring Call Setup Rules

    If an Exit Action Type is not configured and the device has run all the rules in the Set ID, the default Action Value of the Set ID is "True" (i.e., use the current Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 222 Mediant 800B Gateway and E-SBC routing rule).  Rule's condition is not met: The device runs the next rule in the Set ID. When the device reaches the end of the Set ID and no Exit was performed, the Set ID ends with a "True"...
  • Page 223 (attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called number is the same as the number in the attribute "msRTCSIP-PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 224 Mediant 800B Gateway and E-SBC Parameter Description Action Subject Defines the element (header, parameter, or body) upon CLI: action-subject which you want to perform the action. [CallSetupRules_ActionSubject] The valid value is a string of up to 100 characters (case- insensitive).

  • Page 225: Call Setup Rule Examples

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

  • Page 227: Quality Of Experience

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

  • Page 228: Configuring Quality Of Experience Profiles

     Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 227.
  • Page 229 In the Quality of Experience Profile page, select the QoE Profile index row for which you want to configure QoE thresholds, and then click the Quality of Experience Color Rules link located below the table; the Quality of Experience Color Rules page appears. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 230 Mediant 800B Gateway and E-SBC Click Add; the following dialog box appears: Figure 16-3: Quality of Experience Page - Add Record Dialog Box The figure above shows a configuration example where if the MOS value changes by 0.1 (hysteresis) to 3.3 or 3.5, the Green-Yellow threshold is crossed. The device considers a change to 3.3 as a Yellow state (i.e., medium quality) and a change to 3.5...

  • Page 231: Configuring Bandwidth Profiles

    Alternative routing based on bandwidth utilization. If a call is rejected because of a crossed threshold, the device generates a SIP 806 response. You can configure this SIP response code as a reason for alternative routing (see ''Configuring SIP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 232 Mediant 800B Gateway and E-SBC Response Codes for Alternative Routing Reasons'' on page 524).  Send an SNMP alarm (acMediaRealmBWThresholdAlarm). The device clears the alarm when bandwidth utilization returns to normal (within the thresholds). The thresholds of Bandwidth Profiles use the same color-coding as the Quality of Experience Profile: ...
  • Page 233 Red state occurs. For example, assume this parameter is set to 10% and the configured bandwidth threshold is set to 64000 Kbps. If current bandwidth reaches 70,400 Kbps (additional 10%), the threshold is considered crossed. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 234: Configuring Media Enhancement Profiles

    Mediant 800B Gateway and E-SBC Parameter Description Generate Alarm Enables the generation of an SNMP alarm if the threshold CLI: generate-alarms (with the hysteresis) is crossed. [BWProfile_GenerateAlarms]  [0] Disable (default)  [1] Enable If enabled, an alarm is sent if one of the following scenarios occurs: ...
  • Page 235 Profile index row, and then click the Media Enhancement Rules link located below the table; the Media Enhancement Rules page appears. Click Add; the following dialog box appears: Figure 16-6: Media Enhancement Rules - Add Record Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 236 Mediant 800B Gateway and E-SBC Configure a Media Enhancement Rule according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 16-5: Media Enhancement Rules Table Parameter Descriptions...

  • Page 237: Control Network

    The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm or CLI command, configure voip/voip-network realm. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 238 Mediant 800B Gateway and E-SBC  To configure a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > VoIP Network > Media Realm Configuration). Click Add; the following dialog box appears: Figure 17-1: Media Realm Page - Add Record Dialog Box Configure the Media Realm according to the parameters described in the table below.

  • Page 239: Configuring Remote Media Subnets

    ''Configuring Bandwidth Profiles'' on page 231, respectively. Thus, you can apply these profiles to remote media subnets instead of Media Realms or IP Groups. You can configure up to five Remote Media Subnets per Media Realm. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 240 Mediant 800B Gateway and E-SBC The figure below illustrates an example for implementing Remote Media Subnets. IP Group #2 represents a SIP Trunk which routes international (USA and India) and local calls. As international calls are typically more prone to higher delay than local calls, different Quality of Experience Profiles are assigned to them.
  • Page 241 [RemoteMediaSubnet_DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the CLI: qoe-profile Remote Media Subnet. [RemoteMediaSubnet_QOEProfileName] BW Profile Name Assigns a Bandwidth Profile to the Remote CLI: bw-profile Media Subnet. [RemoteMediaSubnet_BWProfileName] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 242: Configuring Srds

    Mediant 800B Gateway and E-SBC 17.3 Configuring SRDs The SRD table lets you configure up to 32 signaling routing domains (SRD). An SRD represents a logical VoIP network. Each logical or physical connection requires an SRD. For example, if the device interfaces with both the LAN and WAN, you need to configure an SRD for each one.
  • Page 243 SRD, calls cannot be established if the following scenario exists: One of the endpoints is defined as a foreign user (for example, “follow me service”) and one endpoint is located on the WAN and the other on the LAN. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 244: Configuring Sip Interfaces

    Mediant 800B Gateway and E-SBC Parameter Description The reason for this is that in Media Anchoring, the device does not interfere in the SIP signaling such as manipulation of IP addresses, which is necessary for calls between LAN and WAN.
  • Page 245 This port must be outside of the RTP port range.  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 246 Mediant 800B Gateway and E-SBC Parameter Description TCP Port Defines the listening TCP port. CLI: tcp-port The valid range is 1 to 65534. The default is 5060. [SIPInterface_TCPPort] Notes:  This port must be outside of the RTP port range.
  • Page 247 If both the SIP Interface and IP Group associated with the incoming call are assigned a Message Manipulation Set, the one assigned to the SIP Interface is applied first.  This parameter is applicable only to SBC calls. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 248: Configuring Ip Groups

    Mediant 800B Gateway and E-SBC 17.5 Configuring IP Groups The IP Group table lets you configure up to 50 IP Groups. An IP Group represents a SIP entity in the network with which the device communicates. This can be a server (e.g., IP PBX or ITSP) or it can be a group of users (e.g., LAN IP phones).
  • Page 249 Configure an IP Group according to to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 17-5: IP Group Table Parameter Descriptions Parameter Description Common Parameters Index Defines an index for the new table record. [IPGroup_Index] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 250 Mediant 800B Gateway and E-SBC Parameter Description 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 251 For this parameter to take effect, a device reset is required.  If the Media Realm is deleted from the Media Realm table, this value becomes invalid. IP Profile ID Assigns an IP Profile to the IP Group. To configure IP Profiles, see Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 252 Mediant 800B Gateway and E-SBC Parameter Description CLI: ip-profile-id ''Configuring IP Profiles'' on page 288. [IPGroup_ProfileId] The default is 0. Local Host Name Defines the host name (string) that the device uses in the SIP CLI: local-host-name message's Via and Contact headers. This is typically used to define an [IPGroup_ContactName] FQDN as the host name.
  • Page 253 (i.e., a SIP REFER request is [IPGroup_SIPReRoutingMod received).  [-1] Not Configured (Default)  [0] Standard = INVITE messages that are generated as a result of Transfer or Redirect are sent directly to the URI, according to the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 254 Mediant 800B Gateway and E-SBC Parameter Description Refer-To header in the REFER message or Contact header in the 3xx response.  [1] Proxy = Sends a new INVITE to the Proxy. This is applicable only if a Proxy server is used and the parameter AlwaysSendtoProxy is set to 0.
  • Page 255 [IPGroup_OutboundManSet] Registration Mode Defines the registration mode for the IP Group: CLI: registration-mode  [0] User Initiates Registration (default) [IPGroup_RegistrationMode]  [1] SBC Initiates Registration = Used when the device serves as a Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 256 Mediant 800B Gateway and E-SBC Parameter Description client (e.g., with an IP PBX). This functions only with the User Info file.  [2] Registrations not Needed = The device adds users to its database in active state. Authentication Mode Defines the authentication mode.
  • Page 257 IP Group fails.  If the device receives an INVITE as a result of a REFER request or a 3xx response, then the incoming INVITE is routed according to Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 258: Configuring Proxy Sets

    Mediant 800B Gateway and E-SBC Parameter Description the Request-URI. The device identifies such INVITEs according to a specific prefix in the Request-URI header, configured by the SBCXferPrefix parameter. Therefore, in this scenario, the device ignores this parameter setting. Username Defines the shared username for authenticating the IP Group, when CLI: username the device acts as an Authentication server.
  • Page 259 The address can be defined as an IP address in dotted-decimal [ProxyIp_IpAddress] notation (e.g., 201.10.8.1) or FQDN. You can also specify the port in the following format:  IPv4 address: <IP address>:<port> (e.g., 201.10.8.1:5060)  IPv6 address: <[IPV6 address]>:<port> (e.g., Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 260 Mediant 800B Gateway and E-SBC Parameter Description [2000::1:200:200:86:14]:5060) Transport Type Defines the transport type for communicating with the Proxy server. CLI: voip-network proxy-ip >  [0] UDP transport-type  [1] TCP [ProxyIp_TransportType]  [2] TLS  [-1] = Undefined Note: If this parameter is not defined, the settings of the global parameter SIPTransportType is used.
  • Page 261 The Proxy Set includes more than one Proxy IP address.  The only Proxy defined is an IP address and not an FQDN.  SRV is not enabled (DNSQueryType).  The SRV response includes several records with a different Priority value. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 262 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Is Proxy Hot Swap Enables the Proxy Hot-Swap redundancy mechanism, which CLI: voip-network proxy-set > provides real-time switching from the primary Proxy server to is-proxy-hot-swap redundant Proxies when no response is received from the primary.
  • Page 263 UDP, the device uses UDP to communicate with the proxy and no TLS Context is used. For more information about how certificates are associated with calls and for configuring TLS Contexts, see Configuring SSL/TLS Certificates on page 89. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 264 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 265: Sip Definitions

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

  • Page 268: Regular Registration Mode

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

  • Page 269: Configuring Proxy And Registration Parameters

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

  • Page 271: 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 272: Configuring Sip Message Manipulation

    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 800B Gateway and E- SBC/v.6.60.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”,...
  • Page 273 Configurable identity hiding (information related to identity of subscribers, for example, P-Asserted-Identity, Referred-By, Identity and Identity-Info)  Apply conditions per rule - the condition can be on parts of the message or call’s parameters  Multiple manipulation rules on the same SIP message Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 274 Mediant 800B Gateway and E-SBC The figure below illustrates a SIP message manipulation example: Figure 18-1: SIP Header Manipulation Example Notes: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide.
  • Page 275 Defines an index number for the new table record. [MessageManipulations_Ind Note: Each rule must be configured with a unique index. Manipulation Name Defines an arbitrary name to easily identify the Message CLI: manipulation-name Manipulation rule. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 276 Mediant 800B Gateway and E-SBC Parameter Description [MessageManipulations_Ma The valid value is a string of up to 16 characters. nipulationName] Manipulation Set ID Defines a Manipulation Set ID for the rule. You can define the same CLI: manipulation-set-id Manipulation Set ID for multiple rules to create a group of rules. The...

  • Page 277: Configuring Sip Message Policy Rules

    Maximum number of bodies  Option to send 400 "Bad Request" response if message request is rejected  Blacklist and whitelist for defined methods (e.g., INVITE)  Blacklist and whitelist for defined bodies Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 278 Mediant 800B Gateway and E-SBC The following procedure describes how to configure Message Policy rules in the Web interface. You can also configure Message Policy rules using the table ini file parameter, MessagePolicy or the CLI command, configure voip > sbc message-policy.
  • Page 279 'Body List' parameter (above). [MessagePolicy_BodyListType]  [0] Policy Blacklist =The specified SIP body is rejected.  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; the others are rejected. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 280 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 281: Coders And Profiles

    You can also configure this table using the table ini file parameter, CodersGroup0 or CLI command, configure voip > coders-and-profiles coders-group.  To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 282 Mediant 800B Gateway and E-SBC Configure coders according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 19-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder.
  • Page 283 [1] Enable Default 65 30 (default), 60, 90, 120 silk-nb 20 (default), 40, 60, 80, Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 284: Configuring Coder Groups

    Mediant 800B Gateway and E-SBC Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression T.38 [t38fax] T.38 Version 3 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 19.2 Configuring Coder Groups The Coder Group Settings table lets you configure up to 10 Coder Groups. A Coder Group is a set of configured coders (coder type, packetization time, rate, payload type, and silence suppression).

  • Page 285: Configuring Tel Profile

    Trunk Group Table (see Configuring Trunk Group Table on page 337)). The following procedure describes how to configure Tel Profiles in the Web interface. You can also configure Tel Profiles using the table ini file parameter, TelProfile or CLI command, configure voip/coders-and-profiles tel-profile. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 286 Mediant 800B Gateway and E-SBC  To configure a Tel Profile: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > Tel Profile Settings). Click Add; the following dialog box appears: Configure a Tel Profile according to the parameters described in the table below. For a description of each parameter, refer to the corresponding "global"...
  • Page 287 Web: Dynamic Jitter Buffer Optimization Factor DJBufOptFactor CLI: jitter-buffer-optimization-factor [TelProfile_JitterBufOptFactor] Web: DTMF Volume DTMFVolume CLI: dtmf-volume [TelProfile_DtmfVolume] Web: Input Gain InputGain CLI: input-gain [TelProfile_InputGain] Web: Voice Volume VoiceVolume CLI: voice-volume [TelProfile_VoiceVolume] Web: Echo Canceler EnableEchoCanceller CLI: echo-canceller [TelProfile_EnableEC] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 288: Configuring Ip Profiles

    Mediant 800B Gateway and E-SBC Tel Profile Parameter Global Parameter Web: Enable AGC EnableAGC CLI: enable-agc [TelProfile_EnableAGC] Web: EC NLP Mode ECNLPMode CLI: echo-canceller-nlp-mode [TelProfile_ECNlpMode] Analog Web: Enable Polarity Reversal EnableReversalPolarity CLI: polarity-rvrsl [TelProfile_EnableReversePolarity] Web: Enable Current Disconnect EnableCurrentDisconnect CLI: current-disconnect...
  • Page 289 > coders-and-profiles ip-profile.  To configure an IP Profile: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 290 Mediant 800B Gateway and E-SBC Configure an IP Profile according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 19-5: IP Profile Settings Table Parameter Descriptions Parameter Description Common Web: Index Defines an index number for the new table record.
  • Page 291 Enables the device to release the call if RTP packets are not Connection received within a user-defined timeout, configured by the CLI: disconnect-on-broken-connection BrokenConnectionEventTimeout parameter. [IpProfile_DisconnectOnBrokenCon  [0] No nection]  [1] Yes (default) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 292 Mediant 800B Gateway and E-SBC Parameter Description Notes:  This feature is applicable only if the RTP session is used without Silence Compression. If Silence Compression is enabled, the device doesn't detect a broken RTP connection.  During a call, if the source IP address (from where the RTP packets are received) is changed without notifying the device, the device filters these RTP packets.
  • Page 293 ROC index (and other SRTP fields) as done by the server, resulting in a synchronized SRTP. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 294 Mediant 800B Gateway and E-SBC Parameter Description Notes:  If this feature is disabled and the server resets the ROC upon a re-key generation, one-way voice may occur.  The corresponding global parameter is ResetSRTPStateUponRekey. Generate SRTP keys mode Enables the device to generate a new SRTP key upon CLI: generate-srtp-keys receipt of a re-INVITE with this SIP entity.
  • Page 295 T.38 fax session when the CNG tone is detected by the originating fax. However, this mode is not recommended. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 296 Mediant 800B Gateway and E-SBC Parameter Description Note: The corresponding global parameter is CNGDetectorMode. Web: Vxx Modem Transport Type Defines the modem transport type. CLI: vxx-transport-type  [-1] Not Configured = The settings of the global [IpProfile_VxxTransportType] parameters are used: ...
  • Page 297 SIP 183 with SDP instead of 180 with SDP.  You can also configure early SIP 183 response immediately upon the receipt of an INVITE, using the EnableEarly183 parameter.  Analog: To send a 183 response, you must also set the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 298 Mediant 800B Gateway and E-SBC Parameter Description ProgressIndicator2IP parameter to 1. If set to 0, a 180 Ringing response is sent.  The corresponding global parameter is EnableEarlyMedia. Web: Progress Indicator to IP Defines the progress indicator (PI) sent to the IP.
  • Page 299 If this parameter is set to Preferable [3] and two 'm=' lines are received in the SDP offer, the device prefers the SAVP (secure audio video profile), regardless of the order in the SDP.  The corresponding global parameter is MediaSecurityBehaviour. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 300 Mediant 800B Gateway and E-SBC Parameter Description Web: Number of Calls Limit Defines the maximum number of concurrent calls (incoming CLI: call-limit and outgoing). If the number of concurrent calls reaches this [IpProfile_CallLimit] limit, the device rejects any new incoming and outgoing calls belonging to this IP Profile.
  • Page 301 Enables QSIG tunneling-over-SIP for this SIP entity. This is CLI: enable-qsig-tunneling according to IETF Internet-Draft draft-elwell-sipping-qsig- [IpProfile_EnableQSIGTunneling] tunnel-03 and ECMA-355 and ETSI TS 102 345.  [0] Disable (default).  [1] Enable = Enables QSIG tunneling from QSIG to SIP, Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 302 Mediant 800B Gateway and E-SBC Parameter Description and vice versa. All QSIG messages are sent as raw data in corresponding SIP messages using a dedicated message body. Notes:  QSIG tunneling must be enabled on originating and terminating devices. ...
  • Page 303 Web: Allowed Coders Group ID Assigns an Allowed Coders Group to this SIP entity. This CLI: sbc-allowed-coders-group-id defines audio (voice) coders that can be used for this SIP [IpProfile_SBCAllowedCodersGroupID entity. To configure Allowed Coders Groups, see Configuring Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 304 Mediant 800B Gateway and E-SBC Parameter Description Allowed Audio Coder Groups on page 506. For a description of the Allowed Coders feature, see ''Restricting Coders'' on page 481. Web: Allowed Video Coders Group ID Assigns an Allowed Video Coders Group to this SIP entity.
  • Page 305 History-Info and Diversion headers, see Interworking SIP Diversion and History-Info Headers on page 488.  [0] As Is = (Default) Diversion header is not handled.  [1] Add = History-Info header is converted to a Diversion header. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 306 Mediant 800B Gateway and E-SBC Parameter Description  [2] Remove = Removes the Diversion header and the conversion to the History-Info header depends on the settings of the SBCHistoryInfoMode parameter. Web: History-Info Mode Defines the device’s handling of the SIP History-Info header CLI: sbc-history-info-mode for this SIP entity.
  • Page 307 SDP, the device creates an SDP and adds it to the outgoing re-INVITE.  [2] Supported = (Default) re-INVITE is supported with or without SDP. Web: Remote Delayed Offer Support Defines whether the remote endpoint supports delayed offer Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 308 Mediant 800B Gateway and E-SBC Parameter Description CLI: sbc-rmt-delayed-offer (i.e., initial INVITEs without an SDP offer). [IpProfile_SBCRemoteDelayedOfferS  [0] Not Supported = Initial INVITE requests without SDP upport] are not supported.  [1] Supported = (Default) Initial INVITE requests without SDP are supported.
  • Page 309 [2] 183 = Early media is sent as 183 response only. Web: Remote Early Media Defines whether the remote side can accept early media or CLI: sbc-rmt-early-media-supp not. [IpProfile_SBCRemoteEarlyMediaSup  [0] Not Supported = Early media is not supported. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 310 Mediant 800B Gateway and E-SBC Parameter Description  port] [1] Supported = (Default) Early media is supported. Web: Enforce MKI Size Enables MKI length negotiation for SRTP-to-SRTP flows CLI: sbc-enforce-mki-size between SIP networks (i.e., IP Groups). This includes the [IpProfile_SBCEnforceMKISize] capability of modifying the MKI length on the inbound or outbound SBC call leg for this SIP entity.
  • Page 311 [1] Handle Locally = The SIP entity does not support INVITE with the Replaces header. The device terminates the received INVITE with the Replaces header and establishes a new call between the SIP entity and the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 312 Mediant 800B Gateway and E-SBC Parameter Description new call party. It then disconnects the call with the initial call party, by sending it a SIP BYE request. For example, assume that the device establishes a call between A and B. If B initiates a call transfer to C, the device receives an INVITE with the Replaces header from C.
  • Page 313 RTP periods. In other words, the device does not generate RTCP when there is no RTP traffic (such as when a call is on hold). Note: The corresponding global parameter is SBCRTCPMode. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 314 Mediant 800B Gateway and E-SBC Parameter Description Web: Jitter Compensation Enables the on-demand jitter buffer for SBC calls. This jitter CLI: sbc-jitter-compensation buffer can be used when other functionality such as voice [IpProfile_SBCJitterCompensation] transcoding are not done on the call. This jitter buffer is useful when incoming packets are received at inconsistent intervals (i.e., packet delay variation).

  • Page 315: Gateway Application

    Part V Gateway Application...

  • Page 317: Introduction

    CO or the PBX) and connects to analog telephones, dial-up modems, and fax machines. The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 318 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 319: Digital Pstn

    BRI trunks can operate with E1 or T1 trunks. • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 320 Mediant 800B Gateway and E-SBC  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: •...

  • Page 321: Tdm And Timing

    For a description of these parameters, see ''PSTN Parameters'' on page 848.  To configure the TDM Bus settings: Open the TDM page (Configuration tab > VoIP menu > TDM > TDM Bus Settings). Figure 21-2: TDM Bus Settings Page Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 322: Clock Settings

    Mediant 800B Gateway and E-SBC Configure the parameters as required. Click Submit. Save the changes to flash memory, see ''Saving Configuration'' on page 568. 21.2.2 Clock Settings In a traditional TDM service network such as PSTN, both ends of the TDM connection must be synchronized.

  • Page 323: Configuring Internal Clock As Clock Source

    Settings page, by clicking the trunk number in the 'Related Trunks' field, and in the Trunk Settings page, select the required Trunk number icon, and then click Apply Trunk Settings. Click Submit, and then reset the device (see ''Resetting the Device'' on page 565). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 324 Mediant 800B Gateway and E-SBC Notes: • The CAS state machine can only be configured using the Web-based management tool. • Don't modify the default values unless you fully understand the implications of the changes and know the default values. Every change affects the configuration of the state machine parameters and the call process related to the trunk you are using with this state machine.
  • Page 325 Defines which Signaling System to use in both directions [CasStateMachineDigitSignalingSyst (detection\generation).  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 326: Configuring Digital Gateway Parameters

    Mediant 800B Gateway and E-SBC 21.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 707.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 327: Tunneling Applications

    Time between successive INVITEs sent from the same trunk.  Time between call release and the new INVITE that is sent on the same channel. The call can be released if the device receives a 4xx or 5xx response. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 328 Mediant 800B Gateway and E-SBC By utilizing the ‘Profiles’ mechanism (see ''Coders and Profiles'' on page 281), you can configure the TDM Tunneling feature to choose different settings based on a timeslot or groups of timeslots. For example, you can use low-bit-rate vocoders to transport voice and ‘Transparent’...
  • Page 329 [ CodersGroup0 ] FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce; CodersGroup0 0 = g7231; CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 330: Dsp Pattern Detector

    Mediant 800B Gateway and E-SBC 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] 21.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.

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

    T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24. ISDN Non-Facility Associated Signaling (NFAS) enables the use of a single D-channel to control multiple PRI interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 332: Nfas Interface Id

    Mediant 800B Gateway and E-SBC Note: NFAS is applicable only to T1 trunks. With NFAS it is possible to define a group of T1 trunks, called an NFAS group, in which a single D-channel carries ISDN signaling messages for the entire group. The NFAS group’s B-channels are used to carry traffic such as voice or data.

  • Page 333: Working With Dms-100 Switches

    ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk 21.6.3 Creating an NFAS-Related Trunk Configuration The procedures for creating and deleting an NFAS group must be performed in the correct order, as described below. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC  To create an NFAS Group: If there’s a backup (‘secondary’) trunk for this group, it must be configured first. Configure the primary trunk before configuring any NFAS (‘slave’) trunk. Configure NFAS (‘slave’) trunks. ...

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

    Interworking SIP to ISDN overlap dialing (IP to Tel): For each received SIP INVITE pertaining to the same dialog session, the device sends an ISDN Setup message (and subsequent Q.931 Information messages) with the collected digits to the Tel side. For Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC all subsequent INVITEs received, the device sends a SIP 484 "Address Incomplete" response to the IP in order to maintain the current dialog session and to receive additional digits from subsequent INVITEs. Relevant parameters (described in ''PSTN Parameters'' on page 848): ...

  • Page 337: Trunk Group

    ''Configuring Hunt Group Settings'' on page 339).  To register the Trunk Groups, click the Register button, located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 338 Mediant 800B Gateway and E-SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the module (i.e., FXS, FXO, PRI, or BRI) for which you CLI: module want to define the Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 339: Configuring Hunt Group Settings

    Click Submit, and then save ("burn") your settings to flash memory. Table 22-2: Hunt Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_TrunkGr Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 340 Mediant 800B Gateway and E-SBC Parameter Description oupId] 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_Channel  [0] By Dest Phone Number = The channel is selected SelectMode] according to the called (destination) number.
  • Page 341 Group, according to the settings in the Account table (see ''Configuring Registration Accounts'' on page 265). An example is shown below of a REGISTER message for registering endpoint "101" using the registration Per Endpoint mode: REGISTER sip:SipGroupName SIP/2.0 Via: SIP/2.0/UDP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 342 Mediant 800B Gateway and E-SBC Parameter Description 10.33.37.78;branch=z9hG4bKac862428454 From: <sip:101@GatewayName>;tag=1c862422082 To: <sip:101@GatewayName> Call-ID: 9907977062512000232825@10.33.37.78 CSeq: 3 REGISTER Contact: <sip:101@10.33.37.78>;expires=3600 Expires: 3600 User-Agent: Sip-Gateway/v.6.60A.011.002 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Group table (see ''Configuring IP Groups'' on page 248).
  • Page 343 The SIP NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. Note: This parameter appears in the table only if the VoiceMailInterface parameter is set to 3 (QSIG). Configuring Voice Mail on page 440. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 344 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 345: Manipulation

    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. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 346 Mediant 800B Gateway and E-SBC You can perform a second "round" (additional) of source and destination number manipulations for IP-to-Tel calls, on an already manipulated number. The initial and additional number manipulation rules are both configured in the number manipulation tables for Ip-to-Tel calls.
  • Page 347 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix 1001 123451001# [30-40]x 2001 Source Prefix Stripped Digits from Left Stripped Digits from Right Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 348 Mediant 800B Gateway and E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 23-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
  • Page 349 Defines the number or string that you want added to the front of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 9 and the phone number CLI: prefix-to-add is 1234, the new number is 91234. [Prefix2Add] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 350 Mediant 800B Gateway and E-SBC Parameter Description Web: Suffix to Add Defines the number or string that you want added to the end of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone number CLI: suffix-to-add is 1234, the new number is 123400.

  • Page 351: Manipulating Number Prefix

    The prefix is calculated as 020215. The first seven digits from the left are removed from the original number, thereby changing the number to 8888888. The prefix that was previously calculated is then added. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 352: Sip Calling Name Manipulations

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

  • Page 355: Configuring Redirect Number Ip To Tel

     Manipulation operation (Action), for example, remove user-defined number of digits from the left of the redirect number. If the incoming call matches the characteristics of a rule, its manipulation action is applied. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 356 Mediant 800B Gateway and E-SBC Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
  • Page 357 P- Asserted-Identity URI host name (instead of to the From header). Web: Destination Host Prefix Defines the Request-URI host name prefix, which appears in the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 358 Mediant 800B Gateway and E-SBC Parameter Description CLI: dst-host-prefix incoming SIP INVITE message. [_DestHost] The default value is the asterisk (*) symbol (i.e., any prefix). Note: This parameter is applicable only to the Redirect Number IP-to- Tel table. Operation (Action)

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

    Number of Digits to Leave After the above manipulation is done, the device sends the following outgoing SIP 302 response: SIP/2.0 302 Moved Temporarily Via: SIP/2.0/TLS 10.33.45.68;branch=z9hG4bKac54132643;alias From: "MP118 1" <sip:8001@10.33.45.68>;tag=1c54119560 To: <sip:6001@10.33.45.69;user=phone>;tag=1c664560944 Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC Call-ID: 541189832710201115142@10.33.45.68 CSeq: 1 INVITE Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.20A.043.001 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 23.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.

  • Page 361: Configuring Release Cause Mapping

    PSTN. If no match is found, the default static mapping is used.  Release Cause Mapping from ISDN to SIP table: Maps ISDN cause codes to SIP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 362 Mediant 800B Gateway and E-SBC release codes. When a Release Cause is received from the PSTN, the device searches this table for a match. If the Q.850 Release Cause is found, the SIP response assigned to it is sent to the IP side. If no match is found, the default static mapping is used.

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

    Normal, unspecified Server internal error Temporary failure Not implemented Network out of order Bad gateway Network out of order Service unavailable Temporary failure Server timeout Recovery on timer expiry 505* Version not supported Interworking Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC ISDN Release SIP Response Description Description Reason Busy everywhere User busy Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does not specify their cause code mapping.
  • Page 365 Temporarily not available implemented Message not compatible with call state or message type non-existent or not 409* Conflict implemented Information element non-existent or not 480* Not found implemented Invalid information elements contents 501* Not implemented Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 366 Mediant 800B Gateway and E-SBC ISDN Release Description Description Reason Response Message not compatible with call state 503* Service unavailable Recovery of timer expiry Request timeout Protocol error Server internal error Interworking unspecified Server internal error * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft doesn’t specify their cause code mapping.

  • Page 367: Reason Header

    Cause' parameter. This parameter defines Q.931 release causes. Its default value is 3, which is mapped to the SIP 404 response. By changing its value to 34, the SIP 503 response is sent. Other causes can be used as well. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 368: Numbering Plans And Type Of Number

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

  • Page 369: Routing

    Source IP Group (to which the call belongs) • Source and destination Request-URI host name prefix • Source Trunk Group (from where the call is received) • Source (calling) and destination (called) telephone number prefix and suffix Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 370 Mediant 800B Gateway and E-SBC • Source and destination Request-URI host name prefix  Destination: If the call matches the configured characteristics, the device routes the call to an IP destination. If no characteristics match is found in the table, the call is rejected.
  • Page 371 (Tel-to-IP call) and relaying that information to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 372 Mediant 800B Gateway and E-SBC The following procedure describes how to configure Tel-to-IP or outbound IP routing rules in the Web interface. You can also configure these rules using the table ini file parameter, Prefix or CLI command, configure voip > gw routing tel2ip-routing.
  • Page 373 Matching Call Characteristics Web: Src. IP Group ID Defines the IP Group from where the incoming IP call is received. EMS: Source IP Group ID Typically, the IP Group of an incoming INVITE is determined Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 374 Mediant 800B Gateway and E-SBC Parameter Description CLI: src-ip-group-id according to the Inbound IP Routing Table. [PREFIX_SrcIPGroupID] Notes:  This parameter is applicable only to the Gateway's IP-to-IP routing application.  To denote all IP Groups, leave this field empty.
  • Page 375 Internal DNS table (see ''Configuring the Internal DNS Table'' on page 126). Web: Port Defines the destination port to where you want to route the call. EMS: Destination Port Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 376 Mediant 800B Gateway and E-SBC Parameter Description CLI: dst-port [PREFIX_DestPort] Web/EMS: Transport Type Defines the transport layer type for sending the IP call: CLI: transport-type  [-1] Not Configured [PREFIX_TransportType]  [0] UDP  [1] TCP  [2] TLS Note: When set to Not Configured (-1), the transport type defined by the SIPTransportType parameter is used.
  • Page 377 2 (Forking Group "3"). Even if index entry 2 is unavailable and alternative routing is enabled, the device ignores index entry 3 because it belongs to a Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 378: Configuring Inbound Ip Routing Table

    Mediant 800B Gateway and E-SBC Parameter Description Forking Group that is lower than index entry 2. Notes:  To enable Tel-to-IP call forking, set the 'Tel2IP Call Forking Mode' (Tel2IPCallForkingMode) parameter to Enable.  You can configure the device to immediately send the INVITE...
  • Page 379 Group configured in the Outbound IP Routing Table. Configure a routing rule according to the parameters described in the table below. Click Submit. Table 24-3: IP-to-Tel or Inbound IP Routing Table Parameter Description Parameter Description Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 380 Mediant 800B Gateway and E-SBC Parameter Description IP to Tel Routing Mode Determines whether to route the incoming IP call before or after CLI: configure voip/gw routing manipulation of destination number, configured in ''Configuring general-setting/ip2tel-rte-mode Source/Destination Number Manipulation'' on page 345.
  • Page 381 Currently, this field can only be configured using the ini file. Web: IP Profile ID Assigns an IP Profile (configured in ''Configuring IP Profiles'' on CLI: ip-profile-id page 288) to the call. [PstnPrefix_ProfileId] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 382: Ip Destinations Connectivity Feature

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

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

    • You can configure up to two alternative routing rules. • For configuring Tel-to-IP routing rules in the Outbound IP Routing table, see ''Configuring Outbound IP Routing Table'' on page 369. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 384 Mediant 800B Gateway and E-SBC The device searches for an alternative IP destination when any of the following connectivity states are detected with the IP destination of the initial Tel-to-IP routing rule:  No response received from SIP OPTIONS messages. This depends on the chosen method for checking IP connectivity.

  • Page 385: Alternative Routing Based On Sip Responses

    Table 24-5: Alternative Routing based on SIP Response Code Example Destination IP Destination SIP Response Rule Used? Phone Prefix 408 Request Main Route 10.33.45.68 Timeout 10.33.45.70 486 Busy Here Alternative Route #1 Alternative Route #2 10.33.45.72 200 OK Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 386 Mediant 800B Gateway and E-SBC  Proxy Sets: Proxy Sets are used for Server-type IP Groups (e.g., an IP PBX or proxy), which define the address (IP address or FQDN) of the server (see ''Configuring Proxy Sets'' on page 258). As you can configure multiple IP destinations per Proxy Set, the device supports proxy redundancy, which works together with the alternative routing feature.

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

    If a SIP 401 or 407 response is received from a contact, the device does not try to redirect the call to the next contact. Instead, the device continues with the regular authentication process, as indicated by these response types. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 388: Pstn Fallback

    Mediant 800B Gateway and E-SBC 24.5.4 PSTN Fallback The PSTN Fallback feature enables the device to re-route a Tel-to-IP call to the legacy PSTN using one of its trunks if the IP destination is unavailable. For example, if poor voice quality is detected over the IP network, the device attempts to re-route the call to the PSTN.
  • Page 389 Defines an index number for the new table record. [AltRouteCauseIP2Tel_Index] Release Cause Defines a Q.931 release code that if received, the device CLI: rel-cause attempts to route the call to an alternative destination (if [AltRouteCauseIP2Tel_ReleaseCause] configured). Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 24.6.2 Alternative Routing to an IP Destination upon a Busy Trunk The Forward on Busy Trunk Destination table lets you configure alternative routing rules for forwarding (i.e., call redirection) IP-to-Tel calls to an alternative IP destination using SIP 3xx responses.

  • Page 391: Alternative Routing Upon Isdn Disconnect

    If no alternative route has been configured and the Disconnect message is received with PI, the device forwards the subsequent early media to the IP side. The device disconnects the IP call only upon receipt of the subsequent Release message. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 392 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 393: Configuring Dtmf And Dialing

    Open the DTMF & Dialing page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > DTMF & Dialing). Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 568. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 394: Dialing Plan Features

    Mediant 800B Gateway and E-SBC 25.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 25.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 334.

  • Page 395: External Dial Plan File

    Dial Plan. 25.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see ''Dial Plan File'' on page 582. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 396 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 397: Configuring Supplementary Services

    ''Configuration Parameters Reference'' on page 707.  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 398: Call Hold And Retrieve

    Mediant 800B Gateway and E-SBC Configure the parameters as required. Click Submit, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server. To save the changes to flash memory, see ''Saving Configuration'' on page 568.
  • Page 399 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. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 400: Call Pickup

    Mediant 800B Gateway and E-SBC B places A on hold; B hears a dial tone. B calls D and establishes a voice path. A ends call with C; A hears a held tone. B ends call with D. B retrieves call with A.

  • Page 401: Consultation Feature

    REFER messages. This is useful when communicating with SIP UAs that do not support the receipt of REFER messages. This feature is applicable to FXS interfaces. To enable this support, use the EnableCallTransferUsingReinvites parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 402: Consultation Transfer For Qsig Path Replacement

    Mediant 800B Gateway and E-SBC The device also supports attended (consultation) call transfer for BRI phones (user side) connected to the device and using the Euro ISDN protocol. BRI call transfer is according to ETSI TS 183 036, Section G.2 (Explicit Communication Transfer – ECT). Call transfer is enabled using the EnableTransfer and EnableHoldtoISDN parameters.

  • Page 403: Call Forward

    The served party (FXS interface) can be configured through the Web interface (see Configuring Call Forward on page 449) or ini file to activate one of the call forward modes. These modes are configurable per endpoint. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 404: Call Forward Reminder Ring

    Mediant 800B Gateway and E-SBC Notes: • When call forward is initiated, the device sends a SIP 302 response with a contact that contains the phone number from the forward table and its corresponding IP address from the routing table (or when a proxy is used, the proxy’s IP address).

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

    INVITE with this number, the softswitch sends another SIP NOTIFY message with the following Alert-Info header: Alert-Info: <http://127.0.0.1/ Tono-Normal-Invitacion>; Aviso = Desvió-Inmediato From this point on, the device plays a normal dial tone to the FXS phone when it goes off- hook. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 406: Bri Call Forwarding

    Mediant 800B Gateway and E-SBC 26.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 407: 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 408 Mediant 800B Gateway and E-SBC  VoiceMailInterface  EnableVMURI The device supports the following digital PSTN-based MWI features:  ISDN BRI: The device supports MWI for its BRI phones, 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 409: Caller Id

    To debug a Caller ID detection on an FXO interface: Verify that the parameter EnableCallerID is set to 1. Verify that the caller ID standard (and substandard) of the device matches the standard (using parameters CallerIDType, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 410: Caller Id On The Ip Side

    Mediant 800B Gateway and E-SBC BellcoreCallerIDTypeOneSubStandard, and ETSICallerIDTypeOneSubStandard). Define the number of rings before the device starts the detection of caller ID (using the parameter RingsBeforeCallerID). Verify that the correct FXO coefficient type is selected (using the parameter CountryCoefficients), as the device is unable to recognize caller ID signals that are distorted.

  • Page 411: Three-Way Conferencing

    The device supports the following conference modes:  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 412: Emergency E911 Phone Number Services

    Mediant 800B Gateway and E-SBC This mode is configured by setting the 3WayConferenceMode parameter to 2. 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...

  • Page 413: Fxs Device Emulating Psap Using Did Loop-Start Lines

    IP address, the FXS device generates a 500-msec wink signal (double polarity reversals), and then (after a user-defined interval configured by the parameter WaitForDialTime), plays DTMF digits according to the transfer number received in the SIP Refer-To header URI userpart. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 414 Mediant 800B Gateway and E-SBC When the call is answered by the PSAP operator, the PSAP sends a SIP 200 OK to the FXS device, and the FXS device then generates a polarity reversal signal to the E911 switch. After the call is disconnected by the PSAP, the PSAP sends a SIP BYE to the FXS device, and the FXS device reverses the polarity of the line toward the tandem switch.

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

    The FXO device can be implemented instead of an E911 switch, by connecting directly to the PSAP DID loop-start lines. Figure 26-4: FXO Device Interfacing between E911 Switch and PSAP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 416 Mediant 800B Gateway and E-SBC 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.
  • Page 417 Below are two examples for a) INVITE messages and b) INFO messages generated by hook-flash.  Example A: INVITE message with ANI = 333333444444 and pseudo-ANI = 0123456789: INVITE sip:301@10.33.37.79;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.37.78;branch=z9hG4bKac771627168 Max-Forwards: 70 Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 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...
  • Page 419 For FXO interfaces, the preemption is done only on existing IP-to-Tel calls. In other words, if all the current FXO channels are busy with calls that were answered by the FXO device (i.e., Tel-to-IP calls), new incoming emergency IP-to- Tel calls are rejected. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    PSAP. The gathering of location information in the Lync Server 2010 network is illustrated in the figure below: Figure 26-6: Microsoft Lync Server 2010 Client Acquiring Location Information Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 422 Mediant 800B Gateway and E-SBC The Administrator provisions the LIS database with the location of each network element in the Enterprise. The location is a civic address, which can include contextual in-building and company information. In other words, it associates a specific network entity (for example, a WAP) with a physical location in the Enterprise (for example, Floor 2, Wing A, and the Enterprise's street address).
  • Page 423 PRI due to protocol limitations. To overcome this, Enterprises using PSTN Gateways can divide their office space into Emergency Response Locations (ERLs) and assign a dedicated Emergency Location Identification Number (ELIN) to each ERL (or zone). When Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 424 Mediant 800B Gateway and E-SBC Lync Server 2010 sends a SIP INVITE message with the PIDF-LO to the PSTN Gateway, it can parse the content and translate the calling number to an appropriate ELIN. The PSTN Gateway then sends the call to the PSTN with the ELIN number as the calling number.

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

    PSAP, based on ELIN-address match lookup in the Emergency Services provider's ALI database. The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN.
  • Page 426 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 427 E9-1-1 call. This feature is initiated only if the received SIP INVITE message contains a Priority header set to "emergency", as shown below: PRIORITY: emergency Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 428 Mediant 800B Gateway and E-SBC 26.11.4.3.3 PSAP Callback to Lync 2010 Clients for Dropped E9-1-1 Calls As the E9-1-1 service automatically provides all the contact information of the E9-1-1 caller to the PSAP, the PSAP operator can call back the E9-1-1 caller. This is especially useful in cases where the caller disconnects prematurely.

  • Page 429: Configuring Audiocodes Elin Gateway

    26.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. 26.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 430 Mediant 800B Gateway and E-SBC entity (for example, another ELIN Gateway), instead of retrying the call or returning the release call to the user. 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.

  • Page 431: Multilevel Precedence And Preemption

    Table 26-6: MLPP Call Priority Levels (Precedence) and DSCP Configuration Parameters MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header 0 (lowest) routine MLPPRoutineRTPDSCP priority MLPPPriorityRTPDSCP immediate MLPPImmediateRTPDSCP flash MLPPFlashRTPDSCP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 432 Mediant 800B Gateway and E-SBC MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header flash-override MLPPFlashOverRTPDSCP 9 (highest) flash-override-override MLPPFlashOverOverRTPDSCP 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.

  • Page 433: Mlpp Preemption Events In Sip Reason Header

    Defense Switched Network (DSN) network, the following SIP request messages and response codes for specific call scenarios have been identified for signaling this preemption cause: • SIP:BYE - If an active call is being preempted by another call Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 434: Precedence Ring Tone

    Mediant 800B Gateway and E-SBC • CANCEL - If an outgoing call is being preempted by another call • 480 (Temporarily Unavailable), 486 (User Busy), 488 (Not Acceptable Here) - Due to incoming calls being preempted by another call. The device receives SIP requests with preemption reason cause=5 in the following cases: •...

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

    Open the Supplementary Services Table page (Configuration tab > VoIP menu > GW and IP to IP > DTMF and Supplementary > Supp Services Table). Click Add; the following dialog box appears: Figure 26-9: Supplementary Services Table - Add Record Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 436 Mediant 800B Gateway and E-SBC Configure a supplementary service according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. The figure below displays an example of multiple-line extensions configured in the...

  • Page 437: Detecting Collect Calls

    D, and AOC-E messages are sent in the EURO ISDN Facility Information Element (IE) message. The device interworks these ISDN and SIP messages by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call) in AudioCodes proprietary SIP AOC header.

  • Page 438: Configuring Charge Codes

    Mediant 800B Gateway and E-SBC The device supports various methods for AOC:  The device generates the metering tones according to pulses and intervals configured in the Charge Code table (see ''Configuring Charge Codes'' on page 438), where: • 'End Time' - time at which the charge code ends.
  • Page 439 (00). This prevents undefined time frames in a day. Pulse Interval Defines the time interval between pulses (in tenths of a CLI: pulse-interval-<1-4> second). [ChargeCode_PulseInterval<1-4>] Pulses On Answer Defines the number of pulses sent on answer. CLI: pulses-on-answer-<1-4> [ChargeCode_PulsesOnAnswer<1- 4>] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 440: Configuring Voice Mail

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

  • Page 441: Analog Gateway

    The activation of each feature remains in effect until it is deactivated (i.e., not deactivated after a call). • For a description of the keypad parameters, see ''Telephone Keypad Sequence Parameters'' on page 896. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 442: Configuring Metering Tones

    Mediant 800B Gateway and E-SBC  To configure the keypad features Open the Keypad Features page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Keypad Features). Figure 27-1: Keypad Features Page Configure the keypad features as required.

  • Page 443: Configuring Fxo Settings

    The FXO Settings page allows you to configure the device's specific FXO parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 707. Note: The FXO Settings page is available only for FXO interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 444: Configuring Authentication

    Mediant 800B Gateway and E-SBC  To configure the FXO parameters: Open the FXO Settings page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > FXO Settings). Figure 27-3: FXO Settings Page Configure the parameters as required.
  • Page 445 (Read-only) Displays the port type (FXS or FXO). [Authentication_PortType] User Name Defines the user name used for authenticating the port. CLI: user-name [Authentication_UserId] Password Defines the password used for authenticating the port. CLI: password [Authentication_UserPassword] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 446: Configuring Automatic Dialing

    Mediant 800B Gateway and E-SBC 27.5 Configuring Automatic Dialing The Automatic Dialing table lets you configure telephone numbers that are automatically dialed when FXS or FXO ports go off-hook. The dialing can be done immediately upon off- hook, or after a user-defined interval after off-hook referred to as Hotline dialing.

  • Page 447: Configuring Caller Display Information

    The following procedure describes how to configure caller ID in the Web interface. You can also configure this using the table ini file parameter, CallerDisplayInfo or CLI command, configure voip > gw analoggw caller-display-info. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 448 Mediant 800B Gateway and E-SBC  To configure Caller display: Open the Caller Display Information page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Caller Display Information). Click Add; the following dialog box appears: Configure caller display per port according to the parameters described in the table below.

  • Page 449: Configuring Call Forward

    Port Type (Read-only) Displays the port type (FXS or FXO). [FwdInfo_PortType] Type Defines the condition upon which the call is forwarded. CLI: type  [0] Deactivate = (Default) Don't forward incoming calls. [FwdInfo_Type] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 450: Configuring Caller Id Permissions

    Mediant 800B Gateway and E-SBC Parameter Description  [1] On Busy = Forward incoming calls when the port is busy.  [2] Unconditional = Always forward incoming calls.  [3] No Answer = Forward incoming calls that are not answered within the time specified in the 'No Reply Time' field.

  • Page 451: Configuring Call Waiting

    The following procedure describes how to configure call waiting per port in the Web interface. You can also configure this using the table ini file parameter, CallWaitingPerPort or CLI command, configure voip > gw analoggw call-waiting. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 452: Rejecting Anonymous Calls

    Mediant 800B Gateway and E-SBC  To enable call waiting per port: Open the Call Waiting page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Call Waiting). Click Add; the following dialog box appears:...

  • Page 453: Configuring Fxs Distinctive Ringing And Call Waiting Tones Per Source/Destination Number

    Configure the table as required. For a description of the parameters, see the table below. Click Submit. Table 27-7: Tone index Table Parameter Description Parameter Description Index Defines the table index entry. Up to 50 entries can be defined. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 454: Fxs/Fxo Coefficient Types

    Mediant 800B Gateway and E-SBC Parameter Description FXS Port First Defines the first port in the FXS port range. CLI: fxs-port-first [ToneIndex_FXSPort_First] FXS Port Last Defines the last port in the FXS port range. CLI: fxs-port-last [ToneIndex_FXSPort_Last] Source Prefix Defines the prefix of the calling number.

  • Page 455: Fxo Operating Modes

    Waiting for dial tone (see ''Two-Stage Dialing'' on page 457) • Time to wait before dialing • Answer supervision  Two-stage dialing (see ''Two-Stage Dialing'' on page 457)  Dialing time: DID wink (see ''DID Wink'' on page 457) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 456: One-Stage Dialing

    Mediant 800B Gateway and E-SBC 27.13.1.1 One-Stage Dialing One-stage dialing is when the FXO device receives an IP-to-Tel call, off-hooks the PBX line connected to the telephone, and then immediately dials the destination telephone number. In other words, the IP caller doesn't dial the PSTN number upon hearing a dial tone.

  • Page 457: Two-Stage Dialing

    DID wink enables the originating end to seize the line by going off-hook. It waits for acknowledgement from the other end before sending digits. This serves as an integrity check that identifies a malfunctioning trunk and allows the network to send a re-order tone to the calling party. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC The "start dial" signal is a wink from the PBX to the FXO device. The FXO then sends the last four to five DTMF digits of the called number. The PBX uses these digits to complete the routing directly to an internal station (telephone or equivalent).

  • Page 459: Collecting Digits Mode

    Hold / Transfer toward the IP side: The FXO device doesn't initiate hold / transfer as a response to input from the Tel side. If the FXO receives a REFER request (with or without replaces), it generates a new INVITE according to the Refer-To header. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 460: 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 461: Call Termination Before Call Establishment

    PBX to the ‘Remote PBX Extension’ connected to the FXS device. The routing is transparent as if the telephone connected to the FXS device is directly connected to the PBX. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC The following is required:  FXO interfaces with ports connected directly to the PBX lines (shown in the figure below)  FXS interfaces for the 'remote PBX extension'  Analog phones (POTS)  PBX (one or more PBX loop start lines) ...

  • Page 463: Message Waiting Indication For Remote Extensions

    ID to the relevant port for display. The remote extension connected to the FXS device can toggle between calls using the Hook Flash button. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 464: Fxs Gateway Configuration

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

  • Page 465: Fxo Gateway Configuration

    IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. Figure 27-16: FXO Tel-to-IP Routing Configuration In the FXO Settings page (see ''Configuring FXO Parameters'' on page 443), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 466 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 467: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 469: Sbc Overview

    Each leg has its own Route/Record Route set. • Modifies SIP To, From, and Request-URI host names (must be configured using the Message Manipulations table). • Generates a new SIP Call-ID header value (different between legs). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 470: Sip Network Definitions

    Mediant 800B Gateway and E-SBC • Changes the SIP Contact header to the device's own address. • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents.
  • Page 471 ''SBC Manipulations'' on page 525. SIP message manipulations: You can configure SIP message manipulation rules that can add, remove, and/or modify SIP headers and parameters. For more information, see ''Configuring SIP Message Manipulation'' on page 272. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 472: User Registration

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

  • Page 473: Initial Registration Request Processing

    SIP Contact headers). Database bindings are added upon successful registration responses. Database bindings are removed in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero).  Registration failure responses. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 474: Routing Using Users Registration Database

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

  • Page 475: Registration Restriction Control

    (e.g. IP 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...) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 476: Media Anchoring Without Transcoding (Transparent)

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

  • Page 477: Media Anchoring With Transcoding

    SDP, which is now offered to the WAN IP phone. The WAN IP phone chooses the extended codec (G.729) in its SDP answer to the device's WAN leg. Since this codec was Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 478 Mediant 800B Gateway and E-SBC not included in the original incoming offer, the device performs transcoding (between G.729 and G.711) between its two legs, allowing the streaming of media to occur. Figure 28-4: Transcoding using Extended Coders (Example) For an SDP offer to provide an extended coder list to a remote user agent, the following prerequisites must be fulfilled: ...

  • Page 479: No Media Anchoring

    The No Media Anchoring feature is enabled for all calls (regardless of SRD), using the global parameter, SBCDirectMedia. You can also enable No Media Anchoring per SRD (in the SRD table), whereby calls belonging to this same SRD (source and destination) are Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 480: Transcoding Modes

    Mediant 800B Gateway and E-SBC handled as No Media Anchoring (direct media) calls. This occurs even if the global parameter is disabled. Notes: • No Media Anchoring can be used when the SBC does not do NAT traversal (for media) where all the users are in the same domain.

  • Page 481: Restricting Coders

    Allowed coders list and the order of priority is first according to the Allowed coders list. Assuming that the outgoing leg also includes Allowed coders and/or Extension coders: The device performs the Allowed coders procedure (common coders) between the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 482 Mediant 800B Gateway and E-SBC updated coder list and the outgoing leg's Allowed coders. The Extension coders procedure is performed before Allowed coders. Adding to the example, assume the following: • For the outgoing leg, the device selects the common coders G.711 and G.729 (explained in the example above).

  • Page 483: Prioritizing Coder List In Sdp Offer

    28.4.9 Multiple RTP Media Streams per Call Session The device's SBC application supports multiple RTP media streams per SBC call session. Up to five different media types can be included in a session:  Audio (m=audio)  Video (m=video) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 484: Interworking Dtmf Methods

    Mediant 800B Gateway and E-SBC  Text (m=text)  Fax (m=image) Therefore, the device can provide transcoding of various attributes in the SDP offer/answer (e.g., codec, port, and packetization time) per media type. If the device is unable to perform transcoding (for example, does not support the codec), it relays the SBC dialog transparently.

  • Page 485: Limiting Sbc Call Duration

    AuthChallengeMethod and AuthQOP parameters. ♦ If validation fails, the device rejects the message and sends a 403 (Forbidden) response to the client. ♦ If validation succeeds, the device verifies client identification. It checks that Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 486: User Authentication Based On Radius

    Mediant 800B Gateway and E-SBC the username and password received from the client is the same username and password in the device's User Information table / database (see ''SBC User Information for SBC User Database'' on page 594). If the client is not successfully authenticated after three attempts, the device sends a SIP 403 (Forbidden) response to the client.

  • Page 487: Resultant Invite Traversing Device

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

  • Page 488: Local Handling Of Sip 3Xx

    Mediant 800B Gateway and E-SBC The device replaces the Contact header value with the special prefix and database key value as user part, and with the device's URL as host part (e.g., Contact: <sip:Prefix_Key_User@SBC:5070;transport=udp>;q=0.5). The device sends this manipulated SIP 3xx response to the Far-End User (FEU).

  • Page 489: Interworking Sip Refer Messages

    IP Group in the IP Group table. 28.8.4 Interworking SIP PRACK Messages The device supports interworking of SIP Provisional Response ACKnowledgement (PRACK) messages (18x). While some UAs may not support PRACK (RFC 3262) others Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 490: Interworking Sip Session Timer

    Mediant 800B Gateway and E-SBC may require it. The device can be configured to resolve this interoperable issue and enable sessions between such endpoints. SIP PRACK handling is configured using the IP Profile parameter, 'SBC Prack Mode':  Optional: PRACK is optional for these UAs. If required, the device performs the PRACK process on behalf of the destination UA.
  • Page 491 User's Manual 28. SBC Overview Figure 28-7: SBC Early Media RTP 18x without SDP Figure 28-8: Early Media RTP - SIP 18x with SDP Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 492: Interworking Sip Re-Invite Messages

    Mediant 800B Gateway and E-SBC 28.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 493: Interworking Call Hold

    Below is an example of an XML body received from the BroadWorks server: <?xml version="1.0" encoding="utf-8"?> <BroadsoftDocument version="1.0" content="subscriberData"> <phoneNumbers> <phoneNumber>2403645317</phoneNumber> <phoneNumber>4482541321</phoneNumber> </phoneNumbers> <aliases> <alias>sip:bob@broadsoft.com</alias> Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC <alias>sip:rhughes@broadsoft.com</alias> </aliases> <extensions> <extension>5317</extension> <extension>1321</extension> </extensions> </BroadSoftDocument> 28.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 495: Call Survivability For Call Centers

    The SBC can handle a sequence of up to five users, after which the session is timed out and the call is dropped. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 496 Mediant 800B Gateway and E-SBC Figure 28-11: Normal Operation in Call Center Application Figure 28-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 248), add IP Groups for the following entities: •...
  • Page 497 The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure 28-13: Routing Rule Example for Call Center Survivability Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 498: Survivability Mode Display On Aastra Ip Phones

    Mediant 800B Gateway and E-SBC 28.9.4 Survivability Mode Display on Aastra IP Phones If the SBC device is deployed in an Enterprise network with Aastra IP phones and connectivity with the WAN fails, the device provides call survivability by enabling communication between IP phone users within the LAN enterprise.

  • Page 499: Sip Forking Initiated By Sip Proxy Server

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

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

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

  • Page 501: Sbc Configuration

    A's phone rings, the application server notifies user B. User B can then press a pre-configured key sequence to answer the call. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 502 Mediant 800B Gateway and E-SBC The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself;...

  • Page 503: Configuring Admission Control

    SRD and its associated IP Groups are as follows:  SRD reserved call capacity: 40  IP Group ID 1 reserved call capacity: 10  IP Group ID 2 reserved call capacity: 20 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 504 Mediant 800B Gateway and E-SBC In this setup, the SRD offers a shared pool for unreserved call capacity of 10 [i.e., 40 – (10 + 20)]. If IP Group ID 1 needs to handle 15 calls, it is guaranteed 10 calls and the remaining 5 is provided from the SRD's shared pool.
  • Page 505 IP Group or SRD. You can also [SBCAdmissionControl_LimitPerU use the following special values: ser]  [0] 0 = Block all these dialogs.  [-1] -1 = (Default) Unlimited. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 506: Configuring Allowed Audio Coder Groups

    Mediant 800B Gateway and E-SBC Parameter Description Rate Defines the rate at which tokens are added to the token bucket CLI: rate per second (i.e., token rate). One token is added to the bucket [SBCAdmissionControl_Rate] every 1000 divided by the value of this parameter (in milliseconds).
  • Page 507 The valid value for user-defined coders is a [AllowedCodersGroupX_Name] string of up to 25 characters (case-insensitive). For example, "HD.123" (without quotes). Note: Each coder type (e.g., G.729) can be configured only once per Allowed Coders Group. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 508: Configuring Allowed Video Coder Groups

    Mediant 800B Gateway and E-SBC 29.4 Configuring Allowed Video Coder Groups The Allowed Video Coders Group table lets you configure up to four Allowed Video Coders Groups. An Allowed Video Coders Group defines a list of video coders that can be used when forwarding video streams to a specific SIP entity.
  • Page 509 Interface table) and then classifies the SIP dialog with the first IP Group that is associated with this SRD. For example, if IP Groups 3 and 4 use the same SRD, the device classifies the call to IP Group 3. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 510 Mediant 800B Gateway and E-SBC 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. This is configured by the 'Classification Failure Response Type' parameter in the SIP Interface table (see ''Configuring SIP Interfaces'' on page 244).
  • Page 511 Note: The SRDs are also associated with a port number as defined by the SIP Interface used by the SRD (see ''Configuring SIP Interfaces'' on page 244). Source IP Address Defines the source IP address (in dotted-decimal notation) CLI: src-ip-address Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 512 Mediant 800B Gateway and E-SBC Parameter Description [Classification_SrcAddress] of the incoming SIP dialog. The IP address can be configured using the following wildcards:  "x" wildcard: represents single digits. For example, 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.

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

    P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group ID Prefix Username Prefix 1111 2000 10.10.10.10 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 514: Configuring Message Condition Rules

    Mediant 800B Gateway and E-SBC 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...

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

    Matching characteristics (Rule) - characteristics of incoming SIP message such as the IP Group from where the message was received.  Operation (Action) - if the incoming SIP message matches the characteristics of the rule, the device routes the message to the configured destination Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 516 Mediant 800B Gateway and E-SBC If the characteristics of an incoming call do not match the first rule in the table, the call characteristics are compared to those of the second rule, and so on until a matching rule is located.
  • Page 517 In this case, instead of setting the alternative route's 'Group Policy' to None, you must set it to Forking. The group members of the alternative route must be configured in the rows immediately below it. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 518 Mediant 800B Gateway and E-SBC The LCR feature can also be employed with call forking. The device calculates a maximum call cost for each Forking group and routes the call to the Forking group with the lowest cost. Thus, even if the call can successfully be routed to the main routing rule, a different routing rule can be chosen (even an alternative route, if configured) based on LCR.
  • Page 519 Defines the SIP dialog request type of the incoming SIP [IP2IPRouting_RequestType] dialog. CLI: request-type  [0] All (default)  [1] INVITE  [2] REGISTER  [3] SUBSCRIBE  [4] INVITE and REGISTER  [5] INVITE and SUBSCRIBE  [6] OPTIONS Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 520 Mediant 800B Gateway and E-SBC Parameter Description Message Condition Assigns a SIP message Condition rule. To configure [IP2IPRouting_MessageCondition] Condition rules, see ''Configuring Message Condition Rules'' CLI: message-condition on page 514. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect [IP2IPRouting_ReRouteIPGroupID] response (e.g., 3xx) or REFER message.
  • Page 521 'Destination Type' is set to IP Group. However, regardless of the settings of the parameter 'Destination Type', the IP Group is still used - only for determining the IP Profile or outgoing SRD. If neither IP Group nor SRD Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 522 Mediant 800B Gateway and E-SBC Parameter Description are defined in this table, the destination SRD is determined according to the source SRD associated with the Source IP Group (configured in the IP Group table, see ''Configuring IP Groups'' on page 248). If this table...
  • Page 523 [IP2IPRouting_GroupPolicy] Forking Group members are configured in the rows below it).  [1] Forking = Call uses this route and the routes of Forking Group members, if configured (in the rows below it). Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC Parameter Description Cost Group Assigns a Cost Group to the routing rule for determining the [IP2IPRouting_CostGroup] cost of the call. To configure Cost Groups, see ''Configuring CLI: cost-group Cost Groups'' on page 218. By default, no Cost Group is defined.

  • Page 525: Sbc Manipulations

    IP Group. Manipulated destination user and host are performed on the following SIP headers: Request-URI, To, and Remote-Party-ID (if exists). Manipulated source user and host are performed on the following SIP headers: From, P-Asserted (if exists), P- Preferred (if exists), and Remote-Party-ID (if exists). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 526 Mediant 800B Gateway and E-SBC Figure 29-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 527 INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone> Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 29.6.1 Configuring IP-to-IP Inbound Manipulations The IP to IP Inbound Manipulation table lets you configure up to 100 IP-to-IP Inbound Manipulation rules. An IP-to-IP Inbound Manipulation rule defines a manipulation sequence for the source or destination SIP URI user part of inbound SIP dialog requests. You can apply these manipulations to different SIP dialog message types (e.g., INVITE or...
  • Page 529 From header). [IPInboundManipulation_SrcHost] The default is the asterisk (*) symbol (i.e., any host name). Destination Username Prefix Defines the prefix of the destination SIP URI user name, CLI: dst-user-name-prefix usually located in the Request-URI. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 530 Mediant 800B Gateway and E-SBC Parameter Description [IPInboundManipulation_DestUser The default is the asterisk (*) symbol (i.e., any destination namePrefix] username prefix). Note: The prefix can be a single digit or a range of digits. For available notations, see ''Dialing Plan Notation for Routing and Manipulation'' on page 705.

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

    The following procedure describes how to configure IP-to-IP Outbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPOutboundManipulation or CLI command, configure voip > sbc manipulations ip- outbound-manipulation. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 532 Mediant 800B Gateway and E-SBC  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Outbound). Click Add; the following dialog box appears:...
  • Page 533 [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.  [2] REGISTER = Only SIP REGISTER messages.  [3] SUBSCRIBE = Only SIP SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 534 Mediant 800B Gateway and E-SBC Parameter Description  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect CLI: re-route-ip-group-id response (e.g., 3xx) or REFER message. This parameter is typically used for re-routing requests (e.g., INVITEs)
  • Page 535 The device identifies an incoming user as restricted if one of the following exists:  From header user is anonymous.  P-Asserted-Identity and Privacy headers contain the value "id". Note: All restriction logic is performed after the user number has been manipulated. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 536 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 537: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 539: Crp Overview

    Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
  • Page 540 Mediant 800B Gateway and E-SBC One of the main advantages of CRP is that it enables quick-and-easy configuration. This is accomplished by its pre-configured routing entities, whereby only minimal configuration is required, for example, defining IP addresses to get the device up and running and deployed in the network.

  • Page 541: Crp Configuration

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

  • Page 542: Configuring Call Survivability Mode

    Mediant 800B Gateway and E-SBC 31.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 543: Pre-Configured Ip Groups

    The IP Groups can be edited, except for the fields listed above, which are read-only. • For accessing the IP Group table and for a description of its parameters, see ''Configuring IP Groups'' on page 248. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 31.4 Pre-Configured IP-to-IP Routing Rules For the CRP application, the IP-to-IP Routing table is pre-configured with IP-to-IP routing rules. These rules depend on the configured Call Survivability mode, as described in ''Configuring Call Survivability Mode'' on page 542.

  • Page 545: Emergency Mode

    For the routing rule of Index 2, the destination is the source IP Group (i.e., from where the REGISTER message was received). Index 7 appears only if the CRPGatewayFallback parameter is enabled (see ''Configuring PSTN Fallback'' on page 546). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 546: Configuring Pstn Fallback

    Mediant 800B Gateway and E-SBC 31.5 Configuring PSTN Fallback You can enable the CRP to route emergency calls (or PSTN-intended calls) such as "911" from the Proxy server (IP Group 2) to the PSTN (IP Group 3). In addition, for calls from the...

  • Page 547: High-Availability System

    Part VIII High-Availability System...

  • Page 549: Ha Overview

    Device Switchover upon Failure on page 550. • HA is supported only on the Mediant 800B hardware platform (not Mediant 800). The figure below illustrates the Active-Redundant HA devices under normal operation. Communication between the two devices is through a Maintenance interface, having a unique IP address for each device.

  • Page 550: Device Switchover Upon Failure

    Mediant 800B Gateway and E-SBC subsequent configuration update or software upgrade on the active device is also done on the redundant device. In the active device, all logical interfaces (i.e., Media, Control, OAMP, and Maintenance) are active. In the redundant device, only the Maintenance interface is active, which is used for connectivity to the active device.

  • Page 551: Ha Status On The Home Page

    In the 'HA Device Name' field, enter a name for the active device. Click Submit. Note: Once the devices are running in HA mode, you can change the name of the redundant device, through the active device only, in the 'Redundant HA Device Name' field. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 552 Mediant 800B Gateway and E-SBC The Home page also displays the HA operational status of the device to which you are currently logged in. This is displayed in the 'High Availability' field under the General Information pane:  "Not Operational": HA is not configured or the installed Software License Key does not include the HA feature ...

  • Page 553: Ha Configuration

    Figure 33-1: Rx/Tx Mode for Geographical HA  If the Maintenance ports of both devices are connected directly to each other without intermediation of switches, configure the mode to 2RX/1TX: Figure 33-2: Rx/Tx Mode for Direct Connection Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 554: Configuring The Ha Devices

    Mediant 800B Gateway and E-SBC  If the two devices are connected through two (or more) isolated LAN switches (i.e., packets from one switch cannot traverse the second switch), configure the mode to 2RX/2TX: Figure 33-3: Redundancy Mode for Two Isolated Switches Notes: •...

  • Page 555: Step 1: Configure The First Device

    Ethernet Device assigned to the interface in the 'Underlying Device' field. The Interface table below shows an example where the Maintenance interface is assigned to Ethernet Device "vlan 2" (which is associated with Ethernet Port Group Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 556 Mediant 800B Gateway and E-SBC "GROUP_2") in the 'Underlying Device' field, while the other interface is assigned to "vlan 1" (associated with "GROUP_1"): Figure 33-4: Configured MAINTENANCE Interface in Interface Table If the connection is through a switch, the packets of both interfaces should generally be untagged.

  • Page 557: Step 2: Configure The Second Device

    (configured in Step 1: Configure the First Device on page 555). Burn the configuration to flash without a reset. Power down the device. Continue to ''Step 3: Initialize HA on the Devices'' on page for completing the HA configuration. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 558: Step 3: Initialize Ha On The Devices

    Mediant 800B Gateway and E-SBC 33.1.2.3 Step 3: Initialize HA on the Devices Once you have configured both devices for HA as described in the previous sections, follow the procedure below to complete and initialize HA so that the devices become operational in HA.

  • Page 559: Configuring Firewall Allowed Rules

    10.31.4.61 is the Maintenance interface of the redundant device and 10.31.4.62 is the Maintenance interface of the active device. "HA_IF" is the name of the Maintenance interface. Figure 33-7: Allowed Firewall Rules for HA Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 560 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 561: Ha Maintenance

    The previously active device burns and resets with the new software version. The previously active device switches over to become the active device. For more information on upgrading the software, see ''Software Upgrade Wizard'' on page 600. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 562 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 563: Maintenance

    Part IX Maintenance...

  • Page 565: Basic Maintenance

    Description'' on page 40) to indicate that a device reset is required. • After you reset the device, the Web GUI is displayed in Basic view (see ''Displaying Navigation Tree in Basic and Full View'' on page 41). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 566: Remotely Resetting Device Using Sip Notify

    Mediant 800B Gateway and E-SBC  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 565). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...

  • Page 567: 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. 35.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 568: Saving Configuration

    Mediant 800B Gateway and E-SBC  To unlock the device: Open the Maintenance Actions page (see ''Maintenance Actions'' on page 565). Under the 'LOCK / UNLOCK' group, click the UNLOCK button. Unlock starts immediately and the device accepts new incoming calls.

  • Page 569: High Availability Maintenance

    Under the 'Switch Over' group, click Switch Over; a confirmation box appears requesting you to confirm. Click OK.  To reset the Redundant device: Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 570 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 571: Disconnecting Active Calls

    Session ID. This is done in the CLI using the following commands (from basic command mode):  Disconnects all active calls: # clear voip calls  Disconnects active calls belonging to a specified Session ID: # clear voip calls <Session ID> Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 572 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 573: Resetting Channels

    B-channel is restarted. • B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2). • B-channel restart does not affect the B-channel's configuration. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 574 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 575: Software Upgrade

    TFTP during device startup. If the ini file does not contain a specific auxiliary file type, the device uses the last auxiliary file of that type that was stored on its non-volatile memory. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 576 Mediant 800B Gateway and E-SBC Notes: • You can schedule automatic loading of updated auxiliary files using HTTP/HTTPS. For more information on automatic updates, see Automatic Update Mechanism. • When loading an ini file using this Web page, parameters that are excluded from the loaded ini file retain their current settings (incremental).

  • Page 577: 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 578 Mediant 800B Gateway and E-SBC ♦ [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 ♦...

  • Page 579: Distinctive Ringing

    This cadence rings once during the ringing pattern. Otherwise, the cadence is interpreted as cyclic: it repeats for every ringing cycle.  Ring On Time: Specifies the duration of the ringing signal.  Ring Off Time: Specifies the silence period of the cadence. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 580 Mediant 800B Gateway and E-SBC The Distinctive Ringing section of the ini file format contains the following strings:  [NUMBER OF DISTINCTIVE RINGING PATTERNS]: Contains the following key: • 'Number of Distinctive Ringing Patterns' defining the number of Distinctive Ringing signals that are defined in the file.

  • Page 581: Prerecorded Tones File

    Up to 40 tones (totaling approximately 10 minutes) can be stored in a single PRT file on the device's flash memory. The prerecorded tones are prepared offline using third- party recording utilities and combined into a single file, using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).

  • Page 582: Cas Files

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

  • Page 585: Dial Plan Prefix Tags For Routing

    425207,0,LOCL 42529,0,LOCL 425200,0,LONG 425100,0,LONG ..Notes: • Called and calling prefix tags can be used in the same routing rule. • Dial Plan Prefix Tags are not applicable to FXS and FXO interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 586 Mediant 800B Gateway and E-SBC The following procedure describes how to configure IP-to-Tel routing using prefix tags.  To configure IP-to-Tel routing using prefix tags: Configure a Dial Plan file with prefix tags, and then load the file to the device.
  • Page 587 [ PLAN1 ] 42520[3-5],0,LOCL 425207,0,LOCL 42529,0,LOCL 425200,0,INTL 425100,0,INTL ..Note: Called and calling prefix tags can be used in the same routing rule. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 588: Obtaining Ip Destination From Dial Plan File

    Mediant 800B Gateway and E-SBC The following procedure describes how to configure IP-to-IP routing using prefix tags.  To configure IP-to-IP routing using prefix tags: Configure a Dial Plan file with prefix tags, and then load the file to the device.

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

    "0567811181,0,04343434181"), the received Calling Number Party of 0567811181 is changed to 04343434181 and sent to the IP with a SIP INVITE as follows: Via: SIP/2.0/UDP 211.192.160.214:5060;branch=z9hG4bK3157667347 From: <sip:04343434181@kt.co.kr:5060>;tag=de0004b1 To: sip:01066557573@kt.co.kr:5060 Call-ID: 585e60ec@211.192.160.214 CSeq: 1 INVITE Contact:<sip:04343434181@211.192.160.214:5060;transport=udp> Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 590: User Information File

    Mediant 800B Gateway and E-SBC The initial Dial Plan text file must be converted to *.dat file format using the DConvert utility. This is done by clicking the DConvert's Process Dial Plan File button. For more information, refer to DConvert Utility User's Guide.
  • Page 591 Authentication table (see Configuring Authentication per Port on page 444). To use the username and password configured in the User Info file, set the 'Password' parameter to any value other than its default value. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 592 Mediant 800B Gateway and E-SBC 39.1.5.2.1 Configuring GW User Info Table in Web Interface The following procedure describes how to configure and register users in the GW User Info table in the Web interface. Note: If a User Info file is loaded to the device (as described in ''Configuring GW User...
  • Page 593 (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered)  To search a user by pbx-ext: (sip-def-proxy-and-reg)# user-info find <pbx-ext e.g., 405> 405: Found at index 0 in GW user info table, not registered Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 594: User Information File For Sbc User Database

    Mediant 800B Gateway and E-SBC 39.1.5.2.3 Configuring GW User Info Table in Loadable Text File The GW User Info table can be configured as a User Info file using a text-based file (*.txt). This file can be created using any text-based program such as Notepad. You can load the User Info file using any of the following methods: ...
  • Page 595 Defines an index for the new table record. [SBCUserInfoTable_Index] Local User Defines the user and is used as the Request-URI user part for the [SBCUserInfoTable_LocalUser] AOR in the database. The valid value is a string of up to 10 characters. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 596 Mediant 800B Gateway and E-SBC Parameter Description Username Defines the username for registering the user when [SBCUserInfoTable_Username] authentication is necessary. The valid value is a string of up to 40 characters. Password Defines the password for registering the user when authentication [SBCUserInfoTable_Password] is necessary.
  • Page 597 URI source host part for the AOR in the database Note: To modify the SBC User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Version 6.8 Mediant 800B Gateway and E-SBC...

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

     CLI - see Installing Software License Key using CLI  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 600: Installing Software License Key Using Cli

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

  • Page 601: Software Upgrade Wizard

    When upgrading to a new software version, ensure that you have installed the new Software License Key. • 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 to your computer.
  • Page 602 Mediant 800B Gateway and E-SBC The following procedure describes how to load files using the Web interface's Software Upgrade Wizard. To load files in the CLI, use the following commands:  cmp file: copy firmware from <URL>  ini or auxiliary file: copy <ini file or auxiliary file>...
  • Page 603 Click Reset to complete the upgrade process; the device 'burns' the newly loaded files to flash memory and then resets. Note: Device reset may take a few minutes, depending on .cmp file version. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 604: Backing Up And Loading Configuration File

    Mediant 800B Gateway and E-SBC After the device resets, the End of Process wizard page appears, displaying the installed .cmp file and any other files (ini file and auxiliary files) that you may have installed at the same time: Figure 39-6: Software Upgrade Process Completed Successfully Click End Process to close the wizard;...
  • Page 605 Click the Load INI File button, and then at the prompt, click OK; the device uploads the file and then resets. Once complete, the Web Login screen appears, requesting you to enter your user name and password. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 606 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 607: Automatic Update Mechanism

    Below are examples for configuring the file names and their location for Automatic Update:  ini File: IniFileURL = 'http://www.corp.com/configuration.ini' CptFileURL = 'http://www.corp.com/call_progress.dat' AutoCmpFileUrl = 'http://www.corp.com/SIP_F6.80A.008.cmp  CLI: # configure system (config-system)# automatic update (automatic-update)# voice-configuration http://www.corp.com/configuration.ini (automatic-update)# cal-progress-tone http://www.corp.com/call_progress.dat (automatic-update)# auto-firmware http://www.corp.com/SIP_F6.80A.008.cmp Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 608: Triggering Automatic Update

    Upon receipt of an SNMP request from a provisioning server.  Upon receipt of a special SIP NOTIFY message (from a provisioning server) that includes an Event header with the AudioCodes proprietary value, "check- sync;reboot=false", as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...
  • Page 609 To enable this software (.cmp) file download method based on timestamp, use the ini file parameter, AutoCmpFileUrl or CLI command, auto-firmware. This parameter defines the software file name (.cmp) and the URL address where the file is located. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 610: Configuring Automatic Update

    Mediant 800B Gateway and E-SBC Note: When this method is used, there is typically no need for the provisioning server to check the device’s current firmware version (using the HTTP-User-Agent header). If the device receives an HTTP 301/302/303 redirect response from the provisioning server, it establishes a connection with the server at the new redirect URL and re- sends the HTTP Get request (see Step 2 above).
  • Page 611 The following ini file example can be used to activate the Automatic Update mechanism. # DNS is required for specifying domain names in URLs [ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 612: Automatic Configuration Methods

    Mediant 800B Gateway and E-SBC InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingInterface; InterfaceTable 0 = 6, 10, 10.13.4.12, 16, 10.13.0.1, 1, Mng, 10.1.1.11, 0.0.0.0, ; [ \InterfaceTable ] # Load an extra configuration ini file using HTTP IniFileURL = 'http://webserver.corp.com/Gateway/inifile.ini' # Load Call Progress Tones file using HTTPS CptFileUrl = 'https://10.31.2.17/usa_tones.dat'...

  • Page 613: Dhcp-Based Configuration Server

    DHCP server registers this host name to a DNS server, you can access the device (through a Web browser) using the URL, http://acl_<serial number> (instead of using the device's IP address). For example, if the device's MAC address is 00908f010280, the DNS name is acl_66176. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 614: Configuration Using Dhcp Option 67

    Mediant 800B Gateway and E-SBC Notes: • If, during operation, the device's IP address is changed as a result of a DHCP renewal, the device automatically resets. • If the DHCP server denies the use of the device's current IP address and specifies a different IP address (according to RFC 1541), the device must change its networking parameters.

  • Page 615: Tftp Configuration Using Dhcp Option 66

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

  • Page 616: Configuration Using Ftp Or Nfs

    NFS v2/v3 is also supported. 40.3.6 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 617 /conf/scp IniFileURL https://192.168.100.53/gateways.ini /conf/scp EnableSecureStartup 1 /conf/sar bootp Note: Once Secure Startup has been enabled, it can only be disabled by setting EnableSecureStartup to 0 using the CLI. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 618 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 619: Restoring Factory Defaults

    At the prompt, type the password again, and then press Enter: # Password: Admin At the prompt, type the following to reset the device to default settings, and then press Enter: # write factory Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 620: Restoring Defaults Using Hardware Reset Button

    Mediant 800B Gateway and E-SBC 41.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: ...

  • Page 621: Usb Storage Capabilities

     To save the current configuration to the USB: # copy voice-configuration to usb:///<ini configuration file name> Note: Only a single USB storage (formatted to FAT/FAT32) operation is supported at any given time. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 622 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 623: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 625: System Status

    Navigation menu tree: Status & Diagnostics tab > System Status menu > Ethernet Port Info • On the Home page, click any Ethernet port on the graphical display of the device (see ''Viewing the Home Page'' on page 51) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 626 Mediant 800B Gateway and E-SBC Table 43-1: Ethernet Port Information Parameters Parameter Description Active Displays whether the port is active ("Yes") or not ("No"). Speed Displays the speed (in Mbps) of the Ethernet port. Duplex Mode Displays whether the port is half- or full-duplex.

  • Page 627: Carrier-Grade Alarms

     Description: brief explanation of the alarm  Date: date and time that the alarm was generated You can view the next 20 alarms (if exist), by clicking the Go to page button. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 628: Viewing Alarm History

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

  • Page 629: Performance Monitoring

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

  • Page 630: Viewing Trunk Utilization

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

  • Page 631: Viewing Quality Of Experience

    Dialog Failed Attempts: displays the failed call attempts. This includes the number of calls and subscribes which were successfully and abnormally terminated.  Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 632 Mediant 800B Gateway and E-SBC  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 45-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 633: Viewing Average Call Duration

    As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 634 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 635: Voip Status

    Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Purple Lower Layer Down (DS3 physical layer is disabled) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 636: Viewing Analog Port Information

    Mediant 800B Gateway and E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 46-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls...

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

    To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure 46-4: NFAS Group & D-Channel Status Page Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 638: Viewing Active Ip Interfaces

    Mediant 800B Gateway and E-SBC 46.4 Viewing Active IP Interfaces The IP Interface Status page displays the device's active IP interfaces that are listed in the Interface table (see ''Configuring IP Network Interfaces'' on page 113).  To view active IP network interfaces: ...

  • Page 639: Viewing Performance Statistics

    The release reason can be viewed in the 'Termination Reason' field in the CDR message. You can reset the statistical data displayed on the page (i.e., refresh the display), by clicking the Reset Counters button located below the table. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 640 Mediant 800B Gateway and E-SBC  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 641: Viewing Registered Sas/Sbc Users

    An AOR is a SIP or SIPS URI that points to a domain with a location service that can map the URI to another URI (contact) where the user might be available. A contact is a SIP URI Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 642: Viewing Registration Status

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

  • Page 643: Viewing Call Routing Status

    Routing Table = Calls are routed using the routing table:  Gateway calls: Outbound IP Routing Table (Configuring Outbound IP Routing Table on page 369)  SBC calls: SBC IP-to-IP Routing table (Configuring SBC IP-to-IP Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 644: Viewing Ip Connectivity

    Mediant 800B Gateway and E-SBC Parameter Description Routing Rules on page 515)  Not Used = Proxy server isn't defined. IP Address  IP address and FQDN (if exists) of the Proxy server with which the device currently operates. ...
  • Page 645  This parameter is reset if no QoS information is received for 2 minutes. DNS Status DNS status can be one of the following:  DNS Disable  DNS Resolved  DNS Unresolved Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 646 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 647: Reporting Information To External Party

    Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Silence Suppression State Jitter Buffer Jitter Buffer Adaptive Jitter Buffer Rate Jitter Buffer Nominal Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 648 Mediant 800B Gateway and E-SBC Group Metric Name Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Loss Density Burst Gap Loss Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold...
  • Page 649 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: Figure 47-1: RTCP XR Parameters in RTP/RTCP Settings Page Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 650: Generating Call Detail Records

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

  • Page 651: Cdr Field Description

    Orig Call originator:  LCL - for local  RMT - for remote Caller Caller party (source) Called party (destination) Called SourceIp Source IP address SourcePort Source UDP port DestIp Destination IP address Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 652 Mediant 800B Gateway and E-SBC CDR Field Name Description DestPort Destination UDP port TransportType Transport type:    Source URI SrcURI SrcURIBeforeMap Source URI before manipulation DstURI Destination URI Destination URI before manipulation DstURIBeforeMap Durat Call duration TrmSd Termination side (local or remote)

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

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

    Mediant 800B Gateway and E-SBC CDR Field Name Description PacketInterval Coder packet interval LocalRtpIp Local RTP IP address LocalRtpPort Local RTP port RemoteRtpIp Remote RTP IP address Remote RTP port RemoteRtpPort InPackets Number of received packets OutPackets Number of sent packets...
  • Page 655 Note: This field is applicable only to the Gateway application. Destination phone number plan Note: This field is applicable only to the Gateway application. DstPhoneNum Destination phone number DstNumBeforeMap Destination number before manipulation Durat Call duration Coder Selected coder Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 656 Mediant 800B Gateway and E-SBC Field Name Description Intrv Packet interval RtpIp RTP IP address Port Remote RTP port TrmSd Initiator of call release (IP, Tel, or Unknown) SIP call termination reason (see ''Release Reasons in CDR'' on page TrmReason...
  • Page 657 Local R-factor RemoteRFactor Remote R-factor LocalMosCQ Local MOS for conversation quality RemoteMosCQ Remote MOS for conversation quality SigSourcePort SIP source port SigDestPort SIP destination port MediaType Media type - audio, video, or text Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 658: Release Reasons In Cdr

    Mediant 800B Gateway and E-SBC Field Name Description SIPTrmReason SIP call termination reason (BYE, CANCEL, or SIP error codes, e.g., 404) SipTermDesc Description of SIP termination reason:  SIP Reason header, if exists, for example: SIP ;cause=200 ;text="Call completed elsewhere".
  • Page 659  "GWAPP_NETWORK_OUT_OF_ORDER"  "GWAPP_NETWORK_TEMPORARY_FAILURE"  "GWAPP_NETWORK_CONGESTION"  "GWAPP_ACCESS_INFORMATION_DISCARDED"  "GWAPP_REQUESTED_CIRCUIT_NOT_AVAILABLE"  "GWAPP_RESOURCE_UNAVAILABLE_UNSPECIFIED"  "GWAPP_PERM_FR_MODE_CONN_OUT_OF_S"  "GWAPP_PERM_FR_MODE_CONN_OPERATIONAL"  "GWAPP_PRECEDENCE_CALL_BLOCKED" • "RELEASE_BECAUSE_PREEMPTION_ANALOG_CIRCUIT_RESERVED_FOR_ REUSE" • "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED"  "GWAPP_BC_NOT_AUTHORIZED"  "GWAPP_BC_NOT_PRESENTLY_AVAILABLE"  "GWAPP_SERVICE_NOT_AVAILABLE" Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 660: Configuring Radius Accounting

    Mediant 800B Gateway and E-SBC  "GWAPP_CUG_OUT_CALLS_BARRED"  "GWAPP_CUG_INC_CALLS_BARRED"  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS"  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST"  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED" ...
  • Page 661 Start Acc time format 1 Stop Acc h323-call- The call’s originator: String Answer, Start Acc origin Answering (IP) or Originate etc Stop Acc Originator (PSTN) h323-call- Protocol type or String VoIP Start Acc Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 662 Mediant 800B Gateway and E-SBC Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. type family used on this Stop Acc leg of the call h323- Connect time in NTP String Stop Acc connect-time format h323-...
  • Page 663 (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 664: Event Notification Using X-Detect Header

    Mediant 800B Gateway and E-SBC 47.4 Event Notification using X-Detect Header The device can notify a remote party of the occurrence (or detection) of certain events in the media stream. The device detects events and notifies their occurrence, using the SIP X-Detect message header and only when establishing a SIP dialog.
  • Page 665 Subtype = xxx (according to the defined subtypes of each type) Below is an example of SIP messages using the X-Detect header: INVITE sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 666: Querying Device Channel Resources Using Sip Options

    Mediant 800B Gateway and E-SBC To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Request=CPT,FAX SIP/2.0 200 OK Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone>;tag=1c19282 Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:101@10.33.2.53> X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906...

  • Page 667: Diagnostics

    Part XI Diagnostics...

  • Page 669: Syslog And Debug Recordings

    Syslog message, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 670: Event Representation In Syslog Messages

    Mediant 800B Gateway and E-SBC Message Item Description [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. 83 : 10.33.45.72 : NOTICE: [S=237][SID:1034099026] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE:...
  • Page 671 RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Invalid Header Length Invalid Codec Type Unknown Aggregation Payload Type Invalid Routing Flag Received Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 672: Identifying Audiocodes Syslog Messages Using Facility Levels

    Mediant 800B Gateway and E-SBC 48.1.2 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. Facility level may use any of the "local use"...

  • Page 673: Snmp Alarms In Syslog Messages

    For viewing Syslog messages in the Web interface, see ''Viewing Syslog Messages'' on page 679. • For a detailed description on the Syslog parameters, see ''Syslog, CDR and Debug Parameters'' on page 730. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 674: Configuring Web Operations To Report To Syslog

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

  • Page 675: Configuring Debug Recording

    From the 'Debug Recording Status' drop-down list, select Start to start the debug recording or Stop to end the recording. Click Submit. For a detailed description of these parameters, see ''Syslog, CDR and Debug Parameters'' on page 730. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 676: Filtering Syslog Messages And Debug Recordings

    Mediant 800B Gateway and E-SBC 48.5 Filtering Syslog Messages and Debug Recordings The device can filter Syslog messages and debug recording (DR) packets, which are sent to a Syslog server and packet capturing application (such as Wireshark), respectively. Filtering can be useful to reduce CPU consumption and minimize negative impact on VoIP performance.
  • Page 677 Syslog Enables Syslog messages for the defined logging filter: CLI: syslog  [0] Disable (default) [LoggingFilters_Syslog]  [1] Enable Note: This parameter is not applicable when 'Filter Type' is set to IP Trace. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 678: Filtering Ip Network Traces

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

  • Page 679: 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. Version 6.8...
  • Page 680 Mediant 800B Gateway and E-SBC  To activate the Web interface's Message Log: Enable Syslog (see ''Enabling Syslog'' on page 673). Open the Message Log page (Status & Diagnostics tab > System Status menu > Message Log); the Message Log page is displayed and the log is activated.

  • Page 681: Collecting Debug Recording Messages

    48. Syslog and Debug Recordings 48.7 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: •...
  • Page 682 Mediant 800B Gateway and E-SBC 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 683 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 684: Debug Capturing On Physical Voip Interfaces

    Mediant 800B Gateway and E-SBC 48.8 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets). The captured traffic can be saved in a PCAP-format file (suitable for Wireshark) to a TFTP (default) or an FTP server. The generated PCAP file is in the Extensible Record Format (ERF).

  • Page 685: Self-Testing

    Startup Test (automatic): This hardware test has minor impact in real-time. While this test is executed, the regular operation of the device is disabled. If an error is detected, an error message is sent to the Syslog. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 686 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 687: Enabling Debug File Upon Device Crash

    29[2].log The Debug file can be retrieved from the device and saved to a folder on a local PC. This file can be sent to AudioCodes support team for troubleshooting.  To configure Core Dump: Open the Debug Utilities page (Maintenance tab > Maintenance menu > Debug Utilities).
  • Page 688 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 689: Analog Line Testing

     Coefficients checksum  Message waiting indication status  Ring state  Reversal polarity state Note: Use the Analog Line testing mechanism only for monitoring and never when there are calls in progress. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 690 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 691: Testing Sip Signaling Calls

    The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call or CLI command, configure system > test-call > test-call-table. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 692 Mediant 800B Gateway and E-SBC  To configure a test call: Open the Test Call Table page (Configuration tab > System menu > Test Call > Test Call Table). Click Add; the following dialog box appears: Figure 52-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
  • Page 693 'Destination Address' or 'IP [Test_Call_AutoRegister] Group ID' parameter settings (see above).  [0] Disable (default)  [1] Enable Username Defines the authentication username. CLI: user-name By default, no username is defined. [Test_Call_UserName] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 694 Mediant 800B Gateway and E-SBC Parameter Description Password Defines the authentication password. CLI: password By default, no password is defined. [Test_Call_Password] Test Settings Tab Call Party Defines whether the test endpoint is the initiator or receiving side CLI: call-party of the test call.

  • Page 695: Starting And Stopping Test Calls

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

  • Page 696: Viewing Test Call Statistics

    Mediant 800B Gateway and E-SBC 52.3 Viewing Test Call Statistics In addition to viewing a brief status description of the test call in the 'Test Status' field (as described in ''Starting, Stopping and Restarting Test Calls'' on page 695), you can also view a more detailed status description which includes test call statistics.

  • Page 697: Configuring Dtmf Tones For Test Calls

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

  • Page 698: Configuring Basic Test Call

    Mediant 800B Gateway and E-SBC 52.5 Configuring Basic Test Call The Basic Test Call feature tests incoming Gateway calls from a remote SIP endpoint to a simulated test endpoint on the device. The only required configuration is to assign a prefix number (test call ID) to the simulated endpoint.
  • Page 699 The device receives the call from the proxy server. As the 'Test Call ID' parameter is set to "101", the device identifies the incoming call as a test call and sends it directly to the simulated test endpoint "101". Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 700: Test Call Configuration Examples

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

  • Page 703: Appendix

    Part XII Appendix...

  • Page 705: Dialing Plan Notation For Routing And Manipulation

    To depict prefix and suffix numbers together:  03(100): for any number that starts with 03 and ends with 100.  [100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 706 Mediant 800B Gateway and E-SBC Notation Description  03(abc): for any number that starts with 03 and ends with abc.  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405.

  • Page 707: Configuration Parameters Reference

    Web: Allow WAN access to Enables WAN access to the management interface through SSH.  [0] Disable (default) CLI: wan-ssh-allow  [1] Enable [AllowWanSSH] Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 708: Web Parameters

    Mediant 800B Gateway and E-SBC Parameter Description Web: Web and Telnet This table configures up to ten IP addresses that are permitted to Access List Table access the device's Web interface and Telnet interfaces. Access from EMS: Web Access an undefined IP address is denied. When no IP addresses are defined Addresses in this table, this security feature is inactive (i.e., the device can be...
  • Page 709 'Web User Accounts', 'Certificates', 'Regional Settings', 'Maintenance Actions' and all file-loading pages ('Load Auxiliary Files', 'Software Upgrade Wizard', and 'Configuration File'). Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 710 Mediant 800B Gateway and E-SBC Parameter Description [ResetWebPassword] Resets the username and password of the primary ("Admin") and secondary ("User") accounts to their default settings ("Admin" and "Admin" respectively), and deletes all other users that may have been configured. ...

  • Page 711: Telnet Parameters

    Table 54-4: ini File Parameters Parameter Description [INIPasswordsDisplayType] Defines how passwords are displayed in the ini file.  [0] Disable (default) = Passwords are obscured ("encoded"). The passwords are displayed in the following syntax: $1$<obscured Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 712: Snmp Parameters

    Mediant 800B Gateway and E-SBC Parameter Description password> (e.g., $1$S3p+fno=).  [1] Enable = All passwords are hidden and replaced by an asterisk (*). 54.1.5 SNMP Parameters The SNMP parameters are described in the table below. Table 54-5: SNMP Parameters...
  • Page 713 162. Web: Trap Enable Enables the sending of traps to the corresponding SNMP CLI: send-trap manager. [SNMPManagerTrapSendingEna  [0] Disable = Sending is disabled. ble_x]  [1] Enable = (Default) Sending is enabled. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 714 Mediant 800B Gateway and E-SBC Parameter Description Web: Trap User Defines the SNMPv3 USM user or SNMPv2 user to associate CLI: trap-user with the trap destination. This determines the trap format, [SNMPManagerTrapUser_x] authentication level, and encryption level. By default, it is associated with the SNMPv2 user (SNMP trap community string).

  • Page 715: Serial Parameters

    Note: For this parameter to take effect, a device reset is required. EMS: Flow Control Defines the RS-232 flow control. [SerialFlowControl]  [0] = (Default) None  [1] = Hardware Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 716: Auxiliary And Configuration File Name Parameters

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

  • Page 717: Automatic Update Parameters

    The valid value is a string of up to 511 characters. By default, this parameter is not defined. In other words, the User-Agent header is set to "Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>)”, where the tags are replaced with actual values. Notes: ...
  • Page 718 Mediant 800B Gateway and E-SBC Parameter Description  [0] = (Default) Do not check CRC. The file is loaded whenever the server provides it.  [1] = Check CRC for the entire file. Any change, including line order, causes the file to be re-processed.

  • Page 719: Networking Parameters

    Web: Physical Ports This table parameter configures the physical Ethernet ports Settings The format of this parameter is as follows: CLI: configure [ PhysicalPortsTable ] voip/physical-port FORMAT PhysicalPortsTable_Index = PhysicalPortsTable_Port, [PhysicalPortsTable] PhysicalPortsTable_Mode, PhysicalPortsTable_NativeVlan, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 720: Multiple Voip Network Interfaces And Vlan Parameters

    Mediant 800B Gateway and E-SBC Parameter Description PhysicalPortsTable_SpeedDuplex, PhysicalPortsTable_PortDescription, PhysicalPortsTable_GroupMember, PhysicalPortsTable_GroupStatus; [ \PhysicalPortsTable ] For example: PhysicalPortsTable 0 = GE_4_1, 1, 1, 4, "User Port #0", GROUP_1, Active; PhysicalPortsTable 1 = GE_4_2, 1, 1, 4, "User Port #1", GROUP_1, Redundant;...

  • Page 721: Routing Parameters

    Web: Block OSN Port Enables or disables the Ethernet port of the internal switch that CLI: configure system > interfaces with the OSN. interface osn > shutdown  [0] Enable (default) [OSNBlockPort]  [1] Disable Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 722: Quality Of Service Parameters

    Mediant 800B Gateway and E-SBC 54.2.5 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below. Table 54-13: QoS Parameters Parameter Description Layer-2 Class Of Service (CoS) Parameters (VLAN Tag Priority Field) Web: DiffServ Table This table parameter configures DiffServ-to-VLAN Priority EMS: QoS Settings –...

  • Page 723: Nat Parameters

    CLI: configure loading cmp, ini, and auxiliary files (using the Automatic Update system/nfs/servers mechanism). [NFSServers] The format of this table ini file parameter is as follows: [NFSServers] FORMAT NFSServers_Index = NFSServers_HostOrIP, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 724: Dns Parameters

    Mediant 800B Gateway and E-SBC Parameter Description NFSServers_RootPath, NFSServers_NfsVersion, NFSServers_AuthType, NFSServers_UID, NFSServers_GID, NFSServers_VlanType; [\NFSServers] For example: NFSServers 1 = 101.1.13, /audio1, 3, 1, 0, 1, 1; For a detailed description of this table, see ''Configuring NFS Settings'' on page 131.

  • Page 725: Dhcp Parameters

    Defines a second NTP server's address as an FQDN or an IP Address address (in dotted-decimal notation). This NTP is used for [NTPSecondaryServerIP] redundancy; if the primary NTP server fails, then this NTP server is used. The default IP address is 0.0.0.0. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 726 Mediant 800B Gateway and E-SBC Parameter Description Web: NTP UTC Offset Defines the Universal Time Coordinate (UTC) offset (in seconds) EMS: UTC Offset from the NTP server. CLI: utc-offset The default offset is 0. The offset range is -43200 to 43200.

  • Page 727: Debugging And Diagnostics Parameters

    For this parameter to take effect, a device reset is required.  LAN watchdog is applicable only if the Ethernet connection is full duplex. [LifeLineType] Defines the condition(s) upon which the Lifeline analog (FXS) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 728 Mediant 800B Gateway and E-SBC Parameter Description feature is activated. The Lifeline feature can be activated upon a power outage or network failure (i.e., loss of IP connectivity). Upon any of these conditions, the Lifeline feature provides PSTN connectivity and thus call continuity for the FXS phone users.

  • Page 729: Sip Test Call Parameters

    Test_Call_DestAddress, Test_Call_DestTransportType, Test_Call_SRD, Test_Call_ApplicationType, Test_Call_AutoRegister, Test_Call_UserName, Test_Call_Password, Test_Call_CallParty, Test_Call_MaxChannels, Test_Call_CallDuration, Test_Call_CallsPerSecond, Test_Call_TestMode, Test_Call_TestDuration, Test_Call_Play, Test_Call_ScheduleInterval, Test_Call_QOEProfile, Test_Call_BWProfile; [ \Test_Call ] For a description of this table, see ''Configuring Test Call Endpoints'' on page 691. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 730: Syslog, Cdr And Debug Parameters

    Mediant 800B Gateway and E-SBC 54.3.3 Syslog, CDR and Debug Parameters The Syslog, CDR and debug parameters are described in the table below. Table 54-21: Syslog, CDR and Debug Parameters Parameter Description Web: Enable Syslog Determines whether the device sends logs and error messages (e.g., EMS: Syslog enable CDRs) generated by the device to a Syslog server.
  • Page 731 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the 'acsyslog' filter instead of the regular 'syslog' filter.
  • Page 732 Mediant 800B Gateway and E-SBC Parameter Description system/logging/syslog-cpu- drops to a critical level, the device automatically lowers the debug protection level until CPU utilization returns to normal. In other words, if the debug level is [5] Detailed, it lowers it to [1] Basic (or [0] No Debug, if [SyslogCpuProtection] necessary);...
  • Page 733 The format of the ini file table parameter is: [LoggingFilters] [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_FilterType, LoggingFilters_Value, LoggingFilters_Syslog, LoggingFilters_CaptureType; [ \LoggingFilters ] For a detailed description of this table, see ''Filtering Syslog Messages Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 734: Resource Allocation Indication Parameters

    Mediant 800B Gateway and E-SBC Parameter Description and Debug Recordings'' on page 676. 54.3.4 Resource Allocation Indication Parameters The Resource Allocation Indication (RAI) parameters are described in the table below. Table 54-22: RAI Parameters Parameter Description Enables Resource Available Indication (RAI) alarm generation if the...
  • Page 735 For example, if you specify 2, the destination is declared as down after three consecutive ping requests fail to evoke a response from the destination. The valid value is 0 to 100. The default 2. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 736: Security Parameters

    Mediant 800B Gateway and E-SBC 54.4 Security Parameters This subsection describes the device's security parameters. 54.4.1 General Security Parameters The general security parameters are described in the table below. Table 54-24: General Security Parameters Parameter Description Web/EMS: Internal Firewall This table parameter defines the device's access list (firewall), Parameters which defines network traffic filtering rules.
  • Page 737 The valid range is any value from 0. The default is 200. Timeout To Relatch RTCP Defines a period (msec) during which if no packets are received [TimeoutToRelatchRTCPMsec] from the current RTCP session, the channel can re-latch onto Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 738: Https Parameters

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

  • Page 739: Srtp Parameters

    IP Profiles EMS: Enable Symmetric MKI (IpProfile_EnableSymmetricMKI). For a detailed description of this CLI: symmetric-mki parameter and for configuring this functionality in the IP Profile Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 740 Mediant 800B Gateway and E-SBC Parameter Description [EnableSymmetricMKI] table, see ''Configuring IP Profiles'' on page 288. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile.

  • Page 741: Tls Parameters

    EMS: SIPS Require Client authentication and certificate verification for TLS connections. Certificate  [0] Disable = (Default) [SIPSRequireClientCertificate]  Device acts as a client: Verification of the server’s certificate depends on the VerifyServerCertificate Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 742 Mediant 800B Gateway and E-SBC Parameter Description parameter.  Device acts as a server: The device does not request the client certificate.  [1] Enable =  Device acts as a client: Verification of the server certificate is required to establish the TLS connection.

  • Page 743: Ssh Parameters

    Defines the port number for the embedded SSH server. cli: ssh-port Range is any valid port number. The default port is 22. [SSHServerPort] Web/EMS: SSH Admin Key Defines the RSA public key for strong authentication for logging in Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 744: Ids Parameters

    Mediant 800B Gateway and E-SBC Parameter Description CLI: ssh-admin-key to the SSH interface (if enabled). [SSHAdminKey] The value should be a base64-encoded string. The value can be a maximum length of 511 characters. Web: Require Public Key Enables RSA public keys for SSH.

  • Page 745: Quality Of Experience Parameters

    The Quality of Experience (QoE) parameters are described in the table below. Table 54-30: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of AudioCodes primary Session Experience CLI: configure voip/qoe Manager (SEM) server to where the quality experience reports are configuration/server-ip sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
  • Page 746 Mediant 800B Gateway and E-SBC Parameter Description Redundant Server IP Defines the IP address of the secondary SEM server to where the quality experience reports are sent. This is applicable when the CLI: configure voip > qoe SEM/EMS server is in Geographical Redundancy HA mode.
  • Page 747 The format of the ini file table parameter is as follows: CLI: configure voip/qoe [MediaEnhancementRules] media-enhancement-rules FORMAT MediaEnhancementRules_Index = [MediaEnhancementRules] MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of this table, see ''Configuring Media Enhancement Profiles'' on page 234. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 748: Control Network Parameters

    Mediant 800B Gateway and E-SBC 54.6 Control Network Parameters 54.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 54-31: Proxy, Registration and Authentication SIP Parameters Parameter...
  • Page 749 Group (i.e., proxy server), it uses the string configured by the ProxyName parameter as the host name in the REGISTER's Request-URI and uses the string configured by the IP Group table parameter, SIPGroupName as the host name in the To Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 750 Mediant 800B Gateway and E-SBC Parameter Description and From headers. If the IP Group is configured with a Proxy Set that has multiple IP addresses, all the REGISTER messages sent to these proxies are sent with the same host name.
  • Page 751 If a specific Transport Type is configured, a NAPTR query is not performed.  To enable NAPTR/SRV queries for Proxy servers only, use the global parameter ProxyDNSQueryType, or use the proxy Set table. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 752 Mediant 800B Gateway and E-SBC Parameter Description Web: Proxy DNS Query Type Global parameter that defines the DNS query record type for CLI: proxy-dns-query resolving the Proxy server's configured domain name (FQDN) [ProxyDNSQueryType] into an IP address.  [0] A-Record (default) = A-record DNS query.
  • Page 753 EMS: Proxy IP Set IDs, each with up to 10 Proxy server IP addresses (or CLI: configure voip > voip-network FQDN). proxy-ip The format of the ini file table parameter is as follows: [ProxyIP] [ProxyIP] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 754 Mediant 800B Gateway and E-SBC Parameter Description FORMAT ProxyIp_Index = ProxyIp_IpAddress, ProxyIp_TransportType, ProxyIp_ProxySetId; [\ProxyIP] For a description of this table, see ''Configuring Proxy Sets'' on page 258. To configure the Proxy Set attributes (such as Proxy Load Balancing) in the ini file, use the ProxySet parameter.
  • Page 755 Registration Expires time is 3600, the device re-sends its registration request after 3600 x 70% (i.e., 2520 sec). Notes:  This parameter may be overridden if the parameter RegistrationTimeThreshold is greater than 0. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 756 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Registration Retry Time Defines the time interval (in seconds) after which a registration CLI: registration-retry-time request is re-sent if registration fails with a 4xx response or if [RegistrationRetryTime] there is no response from the Proxy/Registrar server.
  • Page 757 [UnregistrationMode]  [0] Disable (default)  [1] Enable = The device sends an asterisk ("*") value in the SIP Contact header, instructing the Registrar server to remove all previous registration bindings. The device Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 758 Mediant 800B Gateway and E-SBC Parameter Description removes SIP User Agent (UA) registration bindings in a Registrar, according to RFC 3261. Registrations are soft state and expire unless refreshed, but they can also be explicitly removed. A client can attempt to influence the expiration interval selected by the Registrar.
  • Page 759 CPU caused by the sending of many [MaxGeneratedRegistersRate] (for example, 1,000) registration requests to a proxy server at any given time. The valid value is 30 to 300 register requests per second. The default is 100. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 760: Network Application Parameters

    Mediant 800B Gateway and E-SBC 54.6.2 Network Application Parameters The SIP network application parameters are described in the table below. Table 54-32: SIP Network Application Parameters Parameter Description Signaling Routing Domain Table Web: SRD Settings This table parameter configures the Signaling Routing Domains (SRD).
  • Page 761 FORMAT RemoteMediaSubnet_Index = RemoteMediaSubnet_Realm, CLI: configure voip > voip- RemoteMediaSubnet_RemoteMediaSubnetIndex, network realm RemoteMediaSubnet_RemoteMediaSubnetName, remotemediasubnet RemoteMediaSubnet_PrefixLength, [SubRealm] RemoteMediaSubnet_AddressFamily, RemoteMediaSubnet_DstIPAddress, RemoteMediaSubnet_QOEProfileName, RemoteMediaSubnet_BWProfileName; [\RemoteMediaSubnet] For a detailed description of this table, see ''Configuring Remote Media Subnets'' on page 239. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 762: 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 763 LA=<latency in ms> Below is an example of the X-RTP-Stat header in a SIP BYE message: BYE sip:302@10.33.4.125 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.126;branch=z9hG4bKac2127550866 Max-Forwards: 70 From: <sip:401@10.33.4.126;user=phone>;tag=1c2113553324 To: <sip:302@company.com>;tag=1c991751121 Call-ID: 991750671245200001912@10.33.4.125 CSeq: 1 BYE Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 764 Mediant 800B Gateway and E-SBC Parameter Description X-RTP-Stat: PS=207;OS=49680;;PR=314;OR=50240;PL=0;JI=600;LA=40 Supported: em,timer,replaces,path,resource- priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRAC K,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.6.2A.008.006 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0 Web/EMS: PRACK Mode Determines the PRACK (Provisional Acknowledgment) mechanism CLI: prack-mode mode for SIP 1xx reliable responses.
  • Page 765 (the minimum of the two). [SessionExpiresDisconne The valid range is 0 to 32 (in seconds). The default is 32. ctTime] Web/EMS: Session Expires Determines the SIP method used for session-timer updates. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 766 Mediant 800B Gateway and E-SBC Parameter Description  Method [0] Re-INVITE = (Default) Uses re-INVITE messages for session- CLI: session-exp-method timer updates. [SessionExpiresMethod]  [1] UPDATE = Uses UPDATE messages. Notes:  The device can receive session-timer refreshes using both methods.
  • Page 767 T.38 Re-INVITES. In such a scenario, the FaxVBDBehavior parameter has no effect.  This feature can be used only if the remote party supports T.38 fax Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 768 Mediant 800B Gateway and E-SBC Parameter Description relay; otherwise, the fax fails. [NoAudioPayloadType] Defines the payload type of the outgoing SDP offer. The valid value range is 96 to 127 (dynamic payload type). The default is 0 (i.e. NoAudio is not supported). For example, if set to 120, the...
  • Page 769 [1] Yes = 'user=phone' string is part of the From and Contact CLI: phone-in-from-hdr headers. [IsUserPhoneInFrom] Web: Use Tel URI for Determines the format of the URI in the P-Asserted-Identity and P- Asserted Identity Preferred-Identity headers. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 770 Mediant 800B Gateway and E-SBC Parameter Description  CLI: uri-for-assert-id [0] Disable = (Default) 'sip:' [UseTelURIForAssertedID]  [1] Enable = 'tel:' Web: Tel to IP No Answer Defines the time (in seconds) that the device waits for a 200 OK...
  • Page 771 [4] Hotline Extended = Interworks the ISDN Setup message’s hotline "OffHook Indicator" Information Element (IE) to SIP INVITE’s Request-URI and Contact headers. (Note: For IP-to-ISDN calls, the device handles the call as described in option [3].) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 772 Mediant 800B Gateway and E-SBC Parameter Description  The device interworks ISDN Setup with an Off Hook Indicator of “Voice” to SIP INVITE Request-URI and Contact header with “tgrp=hotline;trunk-context=dsn.mil”.  The device interworks ISDN Setup with an Off Hook indicator of “Data”...
  • Page 773 2xx response, NOTIFY request, REFER request and its 2xx response. EMS: Is CISCO Sce Mode Determines whether a Cisco gateway exists at the remote side. [IsCiscoSCEMode]  [0] = (Default) No Cisco gateway exists at the remote side. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 774 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 800B Gateway and E-SBC/v.6.40.010.006 The maximum string length is 50 characters.
  • Page 775 The time range is 0 to 3,600. The default is 0. Web/EMS: Fake Retry After Determines whether the device, upon receipt of a SIP 503 response [sec] without a Retry-After header, behaves as if the 503 response included Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 776 Mediant 800B Gateway and E-SBC Parameter Description CLI: fake-retry-after a Retry-After header and with the period (in seconds) specified by this [FakeRetryAfter] parameter.  [0] Disable (default)  Any positive value (in seconds) for defining the period When enabled, this feature allows the device to operate with Proxy servers that do not include the Retry-After SIP header in SIP 503 (Service Unavailable) responses to indicate an unavailable service.
  • Page 777 [0] Disable (default) [EnableContactRestriction  [1] Enable CLI: anonymous-mode Determines whether the device's IP address is used as the URI host [AnonymousMode] part instead of "anonymous.invalid" in the INVITE's From header for Tel-to-IP calls. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 778 Mediant 800B Gateway and E-SBC Parameter Description  [0] = (Default) If the device receives a call from the Tel with blocked caller ID, it sends an INVITE with From: “anonymous”<anonymous@anonymous.invalid>  [1] = The device's IP address is used as the URI host part instead of "anonymous.invalid".
  • Page 779 The Transparent coder can be used on data calls. When the device receives a Setup message from the ISDN with 'TransferCapabilities = data', it can initiate a call using the coder 'Transparent' (even if the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 780 Mediant 800B Gateway and E-SBC Parameter Description coder is not included in the coder list). The initiated INVITE includes the following SDP attribute: a=rtpmap:97 CLEARMODE/8000 The default payload type is set according to the CodersGroup parameter. If the Transparent coder is not defined, the default is set to 56.
  • Page 781 Determines whether the device ignores the Master Key Identifier (MKI) if present in the SDP received from the remote side.  [0] Disable (default)  [1] Enable [TrunkStatusReportingMode Determines whether the device responds to SIP OPTIONS if all the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 782 Mediant 800B Gateway and E-SBC Parameter Description trunks pertaining to Trunk Group #1 are down.  [0] Disable (default)  [1] Enable = If all the trunks pertaining to Trunk Group #1 are down, the device does not respond to received SIP OPTIONS.
  • Page 783 (during the regret time). The INFO message format is as follows: INFO sip:12345@10.50.228.164:5082 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK_05_905924040- 90579 From: <sip:+551137077803@ims.acme.com.br:5080;user=phone>;tag=00 8277765 To: <sip:notavailable@unknown.invalid>;tag=svw-0-1229428367 Call-ID: ConorCCR-0-LU-1229417827103300@dtas- stdn.fs5000group0-000.l CSeq: 1 INFO Contact: sip:10.20.7.70:5060 Content-Type: application/On-Hook (application/Off-Hook) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 784 Mediant 800B Gateway and E-SBC Parameter Description Content-Length: 0 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 785 The Manipulation Set is defined using the MessageManipulations parameter. By default, no manipulation is done (i.e. Manipulation Set ID is set to -1). Note: This parameter is applicable only to the Gateway application. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 786 Mediant 800B Gateway and E-SBC Parameter Description [GWOutboundManipulationS Selects the Manipulation Set ID for manipulating all outbound INVITE messages. The Manipulation Set is defined using the MessageManipulations parameter. By default, no manipulation is done (i.e. Manipulation Set ID is set to -1).
  • Page 787 DigitalOOSBehaviorForTrunk_x parameter.  To configure the timeout interval (in seconds) for Out-of-Service graceful shutdown mode for busy trunks if communication fails with a Proxy server (or Proxy Set), use the GracefulBusyOutTimeout parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 788 Mediant 800B Gateway and E-SBC Parameter Description Web: Out-Of-Service Determines the behavior of FXS endpoints when a Busy Out condition Behavior exists. EMS:FXS OOS Behavior  [0] None = Silence is heard when the FXS endpoint goes off-hook. CLI: oos-behavior ...

  • Page 789: Coders And Profile Parameters

    10 coders. The first Coder Group is the default coder list and the EMS: Coders Group default Coder Group. CLI: configure voip > The format of the ini file table parameter is as follows: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 790 Mediant 800B Gateway and E-SBC Parameter Description coders-and-profiles [ CodersGroup<0-9> ] coders-group FORMAT CodersGroup0_Index = CodersGroup0_Name, [CodersGroup0] CodersGroup0_pTime, CodersGroup0_rate, [CodersGroup1] CodersGroup0_PayloadType, CodersGroup0_Sce; [CodersGroup2] [ \CodersGroup<0-9 ] [CodersGroup3] For example, below are defined two Coder Groups (0 and 1): [CodersGroup4] [ CodersGroup0 ]...
  • Page 791 The format of the ini file table parameter is as follows: [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP, TelProfile_TimeForReorderTone, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 792: Channel Parameters

    Mediant 800B Gateway and E-SBC Parameter Description TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode; [\TelProfile] For a description of this parameter, see Configuring Tel Profiles on page 285. 54.9 Channel Parameters This subsection describes the device's channel parameters.
  • Page 793 Web: Max ERL Threshold - DB Defines the acoustic echo suppressor maximum ratio CLI: acoustic-echo-suppressor-max- between signal level and returned echo from the phone (in decibels). [AcousticEchoSuppMaxERLThreshold] The valid range is 0 to 60. The default is 10. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 794 Mediant 800B Gateway and E-SBC Parameter Description Web: Min Reference Delay x10 msec Defines the acoustic echo suppressor minimum reference CLI: acoustic-echo-suppressor-min- delay (in 10-ms units). reference-delay The valid range is 0 to 40. The default is 0. [AcousticEchoSuppMinRefDelayx10ms] Web: Max Reference Delay x10 msec...

  • Page 795: Coder 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. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 796 Mediant 800B Gateway and E-SBC Parameter Description  [DTMFTransportType] [2] Transparent DTMF = DTMF digits remain in the voice stream.  [3] RFC 2833 Relay DTMF = (Default) DTMF digits are removed from the voice stream and are relayed to remote side according to RFC 2833.

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

    RTP payload type "RED" and the payload type configured by the parameter RFC2198PayloadType. a=rtpmap:<PT> RED/8000 Where <PT> is the payload type as defined by RFC2198PayloadType. The device sends the INVITE message with "a=rtpmap:<PT> RED/8000" and responds with Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 798 Mediant 800B Gateway and E-SBC Parameter Description a 18x/200 OK and "a=rtpmap:<PT> RED/8000" in the SDP. Notes:  For this feature to be functional, you must also set the parameter RTPRedundancyDepth to 1 (i.e., enabled).  Currently, the negotiation of “RED” payload type is not supported and therefore, it should be configured to the same PT value for both parties.
  • Page 799 Payload Type for all types of non hard-coded RTP Payload types, refer to RFC 3551). The default is 120. Note: When defining this parameter, ensure that it doesn't cause collision with other payload types. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 800 Mediant 800B Gateway and E-SBC Parameter Description CLI: rtcp-act-mode Disables RTCP traffic when there is no RTP traffic. This [RTCPActivationMode] feature is useful, for example, to stop RTCP traffic that is typically sent when calls are put on hold (by an INVITE with 'a=inactive' in the SDP).
  • Page 801 CLI: sbc-rtcpxr-report-mode the end of each call session (i.e., after a SIP BYE). The RTCP [SBCRtcpXrReportMode] XR is sent in the SIP PUBLISH message.  [0] Disable (default)  [1] End of Call Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 54.10 Gateway and IP-to-IP Parameters 54.10.1 Fax and Modem Parameters The fax and modem parameters are described in the table below. Table 54-39: Fax and Modem Parameters Parameter Description Web: Fax Transport Mode Determines the fax transport mode used by the device.
  • Page 803 ''Configuring IP Profiles'' on page 288. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 804 Mediant 800B Gateway and E-SBC Parameter Description Web: SIP T38 Version Determines the T.38 fax relay version. CLI: sip-t38-ver  [-1] Not Configured = (Default) No T.38 [SIPT38Version]  [0] Version 0  [3] Version 3 = T.38 Version 3 (V.34 over T.38) Note: For a description on V.34 over T.38 fax relay, see V.34...
  • Page 805  [1] = 5 msec (not recommended)  [2] = 10 msec  [3] = 20 msec Note: When set to 5 msec (1), the maximum number of simultaneous channels supported is 120. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 806 Mediant 800B Gateway and E-SBC Parameter Description EMS: Dynamic Jitter Buffer Defines the Jitter Buffer delay (in milliseconds) during fax and Minimal Delay (dB) modem bypass session. CLI: jitter-buffer-minimum-delay The range is 0 to 150 msec. The default is 40.
  • Page 807 NAT for the answering fax machine. The originating fax does not wait for an answer, but immediately starts sending T.38 packets to the terminating fax machine. Note: To enable No-Op packet transmission, use the NoOpEnable and NoOpInterval parameters. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 808 Mediant 800B Gateway and E-SBC Parameter Description Web: Profile Number Defines the V.150.1 profile, which determines how many DSP EMS: Allocation Profile channels support V.150.1. [V1501AllocationProfile] The value range is 0 to 20. The default is 0. Note: For this parameter to take effect, a device reset is required.

  • Page 809: Dtmf And Hook-Flash Parameters

    Where 16 is the DTMF code for hook flash.  [7] INFO (HUAWAEI) = Sends a SIP INFO message with Hook-Flash indication. The device sends the INFO message as follows: Content-Length: 17 Content-Type: application/sscc event=flashhook Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 810 Mediant 800B Gateway and E-SBC Parameter Description Notes:  The device can interwork DTMF HookFlashCode to SIP INFO messages with Hook Flash indication (for digital interfaces).  FXO interfaces support only the receipt of RFC 2833 Hook- Flash signals and INFO [1] type.
  • Page 811 IpProfile_SecondTxDtmfOption). For configuring IP Profiles, see ''Configuring IP Profiles'' on page 288. Enables the automatic muting of DTMF digits when out-of-band [DisableAutoDTMFMute] DTMF transmission is used.  [0] = (Default) Automatic mute is used. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 812 Mediant 800B Gateway and E-SBC Parameter Description  [1] = No automatic mute of in-band DTMF. When this parameter is set to 1, the DTMF transport type is set according to the parameter DTMFTransportType and the DTMF digits aren't muted if out-of-band DTMF mode is selected (TxDTMFOption set to 1, 2 or 3).

  • Page 813: Digit Collection And Dial Plan Parameters

    This parameter is applicable also to ISDN with overlap dialing.  For E1 CAS MFC-R2 variants (which don't support terminating digit for the called party number, usually I-15), this parameter and the DigitMapping parameter are ignored. Instead, you can define Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 814 Mediant 800B Gateway and E-SBC Parameter Description a Dial Plan template per trunk using the parameter CasTrunkDialPlanName_x (or in the Trunk Settings page).  This parameter can also be configured in a Tel Profile.  For more information on the Dial Plan file, see ''Dialing Plans for Digit Collection'' on page 582.

  • Page 815: Voice Mail Parameters

    Siemens Manufacturer Specific Information (MSI)  [7] IP2IP = The device's IP-to-IP application is used for interworking between an IP Voice Mail server and the device. This is implemented for sending unsolicited SIP NOTIFY Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 816 Mediant 800B Gateway and E-SBC Parameter Description messages received from the Voice Mail server to an IP Group (configured using the NotificationIPGroupID parameter).  [8] ETSI = Euro ISDN, according to ETS 300 745-1 V1.2.4, section 9.5.1.1. Enables MWI interworking from IP to Tel, typically used for BRI phones.
  • Page 817 1) Enable voice detection (i.e., set the EnableVoiceDetection parameter to 1). 2) Set the EnableDSPIPMDetectors parameter to 1. 3) Install the IPMDetector DSP option Feature License Key. SMDI Parameters Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 818 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Enable SMDI Enables Simplified Message Desk Interface (SMDI) interface on [SMDI] the device.  [0] Disable = (Default) Normal serial  [1] Enable (Bellcore)  [2] Ericsson MD-110  [3] NEC (ICS) Notes: ...
  • Page 819 Defines the digit pattern used by the PBX to indicate 'call forward Digit Pattern (Internal) with no reason' when the original call is received from an internal EMS: Digit Pattern Forward No extension. Reason The valid range is a 120-character string. CLI: fwd-no-rsn-dig-ptrn-int [DigitPatternForwardNoReaso Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 820 Mediant 800B Gateway and E-SBC Parameter Description Web: Forward on Busy Digit Defines the digit pattern used by the PBX to indicate 'call forward Pattern (External) on busy' when the original call is received from an external line (not EMS: VM Digit Pattern On Busy an internal extension).

  • Page 821: Supplementary Services Parameters

    Module = Module number, where 1 denotes the module in Slot 1.  Port = Port number, where 1 denotes Port 1 of a module. For example: CallerDisplayInfo 0 = Susan C.,0,1,1; ("Susan C." is sent as Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 822 Mediant 800B Gateway and E-SBC Parameter Description the Caller ID for Port 1 of Module 1) CallerDisplayInfo 1 = Mark M.,0,1,2; ("Mark M." is sent as Caller ID for Port 2 of Module 1) Notes:  The indexing of this table ini file parameter starts at 0.
  • Page 823  [1] = The device attempts to find an optimized timing to generate the Caller ID according to the selected Caller ID type. Notes:  This parameter is applicable only to FXS interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 824 Mediant 800B Gateway and E-SBC Parameter Description  If this parameter is set to 1 and used with distinctive ringing, the Caller ID signal doesn't change the distinctive ringing timing.  For this parameter to take effect, a device reset is required.
  • Page 825 Enable = accept [0] (default) or reject [1] incoming anonymous calls.  Port = Port number.  Module = Module number. For example: RejectAnonymousCallPerPort 0 = 0,1,1; RejectAnonymousCallPerPort 1 = 1,2,1; Note: This parameter is applicable only to FXS interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 826: Call Waiting Parameters

    Mediant 800B Gateway and E-SBC 54.10.5.2 Call Waiting Parameters The call waiting parameters are described in the table below. Table 54-44: Call Waiting Parameters Parameter Description Web/EMS: Enable Call Waiting Enables the Call Waiting feature. CLI: call-waiting  [0] Disable [EnableCallWaiting] ...
  • Page 827 Alert-Info:<http://…/Bellcore-dr2> (where "dr2" defines call waiting tone #2)  The SIP INFO message is according to Broadsoft's application server definition. Below is an example of such an INFO message: INFO sip:06@192.168.13.2:5060 SIP/2.0 Via:SIP/2.0/UDP 192.168.13.40:5060;branch=z9hG4bK040066422630 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 828: Call Forwarding Parameters

    Mediant 800B Gateway and E-SBC Parameter Description From: <sip:4505656002@192.168.13.40:5060>;tag=1455352915 To: <sip:06@192.168.13.2:5060> Call-ID:0010-0008@192.168.13.2 CSeq:342168303 INFO Content-Length:28 Content-Type:application/broadsoft play tone CallWaitingTone1 54.10.5.3 Call Forwarding Parameters The call forwarding parameters are described in the table below. Table 54-45: Call Forwarding Parameters Parameter Description Web: Enable Call Enables the Call Forwarding feature.

  • Page 829: Message Waiting Indication Parameters

    [1] Enable = Enables visual MWI by supplying line voltage of approximately 100 VDC to activate the phone's lamp. Notes:  This parameter is applicable only for FXS interfaces.  This parameter can also be configured in a Tel Profile. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 830 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: MWI Display Enables sending MWI information to the phone display. CLI: enable-mwi  [0] Disable = (Default) MWI information isn't sent to display. [MWIDisplay]  [1] Enable = The device generates an MWI message (determined by the parameter CallerIDType), which is displayed on the MWI display.

  • Page 831: Call Hold Parameters

    Web: Call Hold Reminder Defines the duration (in seconds) that the Call Hold Reminder Ring is Ring Timeout played. If a user hangs up while a call is still on hold or there is a call Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 832: Call Transfer Parameters

    Mediant 800B Gateway and E-SBC Parameter Description EMS: CHRR Timeout waiting, then the FXS interface immediately rings the extension for the CLI: call-hold-remnd-rng duration specified by this parameter. If the user off-hooks the phone, the [CHRRTimeout] call becomes active. The valid range is 0 to 600. The default is 30.
  • Page 833 EMS: Blind Transfer Add Prefix Determines whether the device adds the Blind Transfer code CLI: blind-xfer-add-prefix (defined by the KeyBlindTransfer parameter) to the dialed [KeyBlindTransferAddPrefix] destination number.  [0] Disable (default)  [1] Enable Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 834 Mediant 800B Gateway and E-SBC Parameter Description Note: This parameter is applicable only to FXO and FXS interfaces. EMS: Blind Transfer Disconnect Defines the duration (in milliseconds) for which the device Timeout waits for a disconnection from the Tel side after the Blind CLI: blind-xfer-disc-tmo Transfer Code (KeyBlindTransfer) has been identified.

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

    Determines the mode of operation when the 3-Way Conference Mode feature is used. EMS: 3 Way Mode  [0] AudioCodes Media Server = (Default) The Conference- CLI: 3w-conf-mode initiating INVITE (sent by the device) uses the ConferenceID [3WayConferenceMode] concatenated with a unique identifier as the Request-URI.
  • Page 836 Mediant 800B Gateway and E-SBC Parameter Description  [1] Non-AudioCodes Media Server = The Conference- initiating INVITE (sent by the device) uses only the ConferenceID as the Request-URI. The conference server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants.

  • Page 837: Mlpp And Emergency Call Parameters

    [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 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 838 Mediant 800B Gateway and E-SBC Parameter Description to that channel. The preemption is done only on a channel pertaining to the same Trunk Group for which the E911 call was initially destined and if the channel select mode (configured by the ChannelSelectMode parameter) is set to other than By Dest Phone Number (0).
  • Page 839 (namespaces). This value is used in the AS-SIP Resource- Priority header of the outgoing SIP INVITE request. This parameter is used in combination with the MLPPDefaultNamespace parameter, where you need to enter the table row index as its value. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 840 Mediant 800B Gateway and E-SBC Parameter Description This parameter is also used for mapping the Resource-Priority field value of the SIP Resource-Priority header to the ISDN PRI Precedence Level IE. The mapping is configured by the field, EnableIp2TelInterworking:  Disabled: The network-domain field in the Resource-Priority header is set to "0 1 0 0"...
  • Page 841 CallPriorityMode is set to 1 and a Precedence call is [PrecedenceRingingType] received from the IP side. The valid range is -1 to 16. The default is -1 (i.e., plays standard ringing tone). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 842 Mediant 800B Gateway and E-SBC Parameter Description Note: This parameter is applicable only to analog interfaces. EMS: E911 MLPP Behavior Defines the E911 (or Emergency Telecommunication CLI: e911-mlpp-bhvr Services/ETS) MLPP Preemption mode: [E911MLPPBehavior]  [0] = (Default) Standard Mode - ETS calls have the highest priority and preempt any MLPP call.

  • Page 843: Call Cut-Through Parameters

    When enabled, this feature operates as follows: A Tel-to-IP call is established (connected) by the device for a B- channel. The device receives a SIP BYE (i.e., IP side ends the call) and plays a Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 844: Automatic Dialing Parameters

    Mediant 800B Gateway and E-SBC Parameter Description reorder tone to the PSTN side for the duration set by the CutThroughTimeForReOrderTone parameter. The device releases the call towards the IP side (sends a SIP 200 OK). The PSTN side, for whatever reason, remains off-hook.

  • Page 845: Direct Inward Dialing Parameters

    2,000 msec. 4) Upon detection of a polarity reversal change, the FXO interface dials the DTMF (or MF) digits of the calling party (number that dialed 911) in the format "KP<ANI>ST" (*ANI#), Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 846 Mediant 800B Gateway and E-SBC Parameter Description where ANI is the calling number from the INVITE. If no polarity reversal, the FXO goes idle. For example: (Wink) KP911ST (Polarity Change) KP02963700ST Note: The Enable911PSAP parameter must be set to 1.

  • Page 847: Isdn Bri Parameters

    Deactivation sent to the softswitch. EMS: Code Call Forward on The valid value is a string. By default, no value is defined. No Reply Deactivation Note: The string must be enclosed in single apostrophe (e.g., ‘*72’). [SuppServCodeCFNRDeact] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 848: Pstn Parameters

    Mediant 800B Gateway and E-SBC 54.10.6 PSTN Parameters This subsection describes the device's PSTN parameters. 54.10.6.1 General Parameters The general PSTN parameters are described in the table below. Table 54-56: General PSTN Parameters Parameter Description Web/EMS: Protocol Type Defines the PSTN protocol for all the Trunks. To configure the...
  • Page 849 T310 defines the timeout between the receipt of a Proceeding message and the receipt of an Alerting/Connect message. The valid range is 10 to 30. The default is 10 (seconds). Notes:  Instead of configuring this parameter, it is recommended to use Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 850 Mediant 800B Gateway and E-SBC Parameter Description 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). The T301 timer is started when a Q.931 Alert message is received.
  • Page 851  [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. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 852 Mediant 800B Gateway and E-SBC Parameter Description  CLI: line-build-out-loss [0] 0 dB (default) [LineBuildOut.Loss]  [1] -7.5 dB  [2] -15 dB  [3] -22.5 dB Note: This parameter is applicable only to T1 trunks. Defines static TDM hair-pinning (cross-connection) performed at [TDMHairPinning] initialization.

  • Page 853: Tdm Bus And Clock Timing Parameters

    [0] Manual (default) [TDMBusEnableFallback]  [1] Auto Non-Revertive  [2] Auto Revertive Web: TDM Bus Fallback Clock Determines the fallback clock source on which the device Source synchronizes in the event of a clock failure. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 854 Mediant 800B Gateway and E-SBC Parameter Description  EMS: TDM Bus Fallback [4] Network (default) Clock  [8] H.110_A [TDMBusFallbackClock]  [9] H.110_B  [10] NetReference1  [11] NetReference2 Web/EMS: TDM Bus Net Defines the NetRef frequency (for both generation and Reference Speed synchronization).

  • Page 855: Cas Parameters

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

  • Page 858: Isdn Parameters

    Mediant 800B Gateway and E-SBC 54.10.6.4 ISDN Parameters The ISDN parameters are described in the table below. Table 54-59: ISDN Parameters Parameter Description Web: ISDN Termination Side Determines the ISDN termination side. EMS: Termination Side  [0] User side = (Default) ISDN User Termination CLI: isdn-termination-side Equipment (TE) side.
  • Page 859 [1] = PI 1 is added to a sent ISDN Setup message - call is not end-to-end ISDN.  [3] = PI 3 is added to a sent ISDN Setup message - calling equipment is not ISDN. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 860 Mediant 800B Gateway and E-SBC Parameter Description ISDN Flexible Behavior Parameters ISDN protocol is implemented in different switches/PBXs by different vendors. Several implementations may vary slightly from the specification. Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters can be used.
  • Page 861 [131072] STATUS INCOMPATIBLE STATE = Clears the call 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. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 862 Mediant 800B Gateway and E-SBC Parameter Description  [524288] ACCEPT A LAW =A-Law is also accepted in 5ESS.  [2097152] RESTART INDICATION = Upon receipt of a Restart message, acEV_PSTN_RESTART_CONFIRM is generated.  [4194304] FORCED RESTART = On data link (re)initialization, send RESTART if there is no call.
  • Page 863 Sending-Complete IE in the Setup message. This behavior is used when overlap dialing is not needed. When overlap dialing is needed, set this bit and the behavior is changed to suit the scenario, i.e., Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 864 Mediant 800B Gateway and E-SBC Parameter Description Sending-Complete IE is added when required in the Setup message for Enblock mode or in the last Digit with Overlap mode.  [16] USE MU LAW = The device sends G.711-m-Law in outgoing voice calls. When disabled, the device sends G.711-A-Law in outgoing voice calls.

  • Page 865: Isdn And Cas Interworking Parameters

    [2] Always Send Local Date and Time = The device always sends its local date and time (obtained from its internal clock) to PBXs in ISDN Q.931 Connect messages (Date / Time IE). It Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 866 Mediant 800B Gateway and E-SBC Parameter Description does this regardless of whether or not the incoming SIP 200 OK includes the Date header. If the SIP 200 OK includes the Date header, the device ignores its value. Notes:  This feature is applicable only to Tel-to-IP calls.
  • Page 867 When ISDN Tunneling is enabled, the device sends all ISDN PRI messages using the correlated SIP messages. The ISDN Setup message is tunneled using SIP INVITE, all mid-call messages are Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 868 Mediant 800B Gateway and E-SBC Parameter Description tunneled using SIP INFO, and ISDN Disconnect/Release message is tunneled using SIP BYE messages. The raw data from the ISDN is inserted into a proprietary SIP header (X-ISDNTunnelingInfo) or a dedicated message body (application/isdn) in the SIP messages.
  • Page 869 SIP 'isub' parameter according to RFC.  [1] = The device removes the ISDN Subaddress and does not include the 'isub' parameter in the Request-URI and does not process INVITEs with this parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 870 Mediant 800B Gateway and E-SBC Parameter Description [ISUBNumberOfDigits] Defines the number of digits (from the end) that the device takes from the called number (received from the IP) for the isub number (in the sent ISDN Setup message). This feature is only applicable for IP-to-ISDN calls.
  • Page 871 Web: Calling Party Category Defines the regional Calling Party Category (CPC) mapping variant Mode between SIP and PSTN for MFC-R2. CLI: cpc-mode  [0] None (default) [CallingPartyCategoryMode]  [1] Brazil R2  [2] Argentina R2 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 872 Mediant 800B Gateway and E-SBC Parameter Description Notes:  To enable CPC mapping, set the EnableCallingPartyCategory parameter to 1.  This parameter is applicable only to the E1 MFC-R2 variant. CLI: usr2usr-hdr-frmt Defines the interworking between the SIP INVITE's User-to-User [UserToUserHeaderFormat] header and the ISDN User-to-User (UU) IE data.
  • Page 873  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Web/EMS: PSTN Alert Timeout Defines the Alert Timeout (ISDN T301 timer) in seconds for Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 874 Mediant 800B Gateway and E-SBC Parameter Description CLI: pstn-alrt-timeout outgoing calls to PSTN, per trunk. This timer is used between the [TrunkPSTNAlertTimeout_x] time that an ISDN Setup message is sent to the Tel side (IP-to-Tel call establishment) and a Connect message is received. If Alerting is received, the timer is restarted.
  • Page 875 ''Configuring IP Profiles'' on page 288. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 876 Mediant 800B Gateway and E-SBC Parameter Description Web: Trunk Groups to Send IE Defines Trunk Group IDs (up to 50 characters) from where the EMS: List Of Trunk Groups To optional ISDN IE (defined by the parameter AddIEinSetup) is sent.
  • Page 877 (using Facility messages) to perform the transfer. Notes:  For RLT ISDN transfer, the parameter SendISDNTransferOnConnect must be set to 1.  The parameter SendISDNTransferOnConnect can be used to define if the TBCT/ECT transfer is performed after receipt Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 878 Mediant 800B Gateway and E-SBC Parameter Description of Alerting or Connect messages. For RLT, the transfer is always done after receipt of Connect (SendISDNTransferOnConnect is set to 1).  This transfer can be performed between B-channels from different trunks or Trunk Groups, by using the parameter EnableTransferAcrossTrunkGroups.
  • Page 879 ISDN transfer failure and subsequently performs a hairpin TDM connection or sends a SIP NOTIFY message with a SIP 603 response (depending whether hairpin is enabled or disabled, using the parameter DisableFallbackTransferToTDM). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 880 Mediant 800B Gateway and E-SBC Parameter Description The valid range is 1 to 10. The default is 4. Web/EMS: Enable Network Determines whether the device allows interworking of network-side ISDN Transfer received ECT/TBCT Facility messages (NI-2 TBCT - Two B-...

  • Page 881: Answer And Disconnect Supervision Parameters

    Enables the sending of SIP 200 OK upon detection of speech, EMS: Enable Voice Detection fax, or modem. CLI: answer-supervision  [1] Yes = The device sends a SIP 200 OK (in response to an Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 882 Mediant 800B Gateway and E-SBC Parameter Description [EnableVoiceDetection] INVITE message) when speech, fax, or modem is detected from the Tel side.  [0] No = (Default) The device sends a SIP 200 OK only after it completes dialing to the Tel side.
  • Page 883 [1] Packets Count = According to packet count. Note: For this parameter to take effect, a device reset is required. [FarEndDisconnectSilenceThre Defines the threshold of the packet count (in percentages) below shold] which is considered silence by the device. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 884 Mediant 800B Gateway and E-SBC Parameter Description The valid range is 1 to 100%. The default is 8%. Notes:  This parameter is applicable only if silence is detected according to packet count (FarEndDisconnectSilenceMethod is set to 1).  For this parameter to take effect, a device reset is required.
  • Page 885 The current disconnect duration is configured by the CurrentDisconnectDuration parameter. The current disconnect threshold (FXO only) is configured by the CurrentDisconnectDefaultThreshold parameter. The frequency at which the analog line voltage is sampled is configured by the TimeToSampleAnalogLineVoltage parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 886 Mediant 800B Gateway and E-SBC Parameter Description Note: This parameter can also be configured in a Tel Profile. EMS: Polarity Reversal Type Defines the voltage change slope during polarity reversal CLI: polarity-reversal-type or wink. [PolarityReversalType]  [0] = (Default) Soft reverse polarity.

  • Page 887: Tone Parameters

    (Tone Type #15). Both these tones are defined in the CPT file. The range is 1,000 to 60,000. The default is 2,000 (i.e., 2 seconds). Notes:  This parameter is applicable only to FXS interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 888 Mediant 800B Gateway and E-SBC Parameter Description  If you want to configure the duration of the confirmation tone to longer than 16 seconds, you must increase the value of the parameter TimeForDialTone accordingly.  The MWI tone takes precedence over the call forwarding reminder tone.
  • Page 889 Analog Interfaces: Plays a ringback tone to the Tel side of the call when a SIP 180/183 response is received.  Digital Interfaces: The device configured for CAS plays a local ringback tone to the PSTN upon receipt of a SIP 180 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 890 Mediant 800B Gateway and E-SBC Parameter Description Ringing response (with or without SDP). Note that the receipt of a 183 response does not cause the device configured for CAS to play a ringback tone (unless the SIP183Behaviour parameter is set to 1). The device...
  • Page 891 ISDN Alert with PI = 8 to the ISDN (unless the ProgressIndicator2ISDN_x parameter is configured differently).  If LocalISDNRBSource is set to 0, the device doesn't play a Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 892 Mediant 800B Gateway and E-SBC Parameter Description ringback tone. No PI is sent in the ISDN Alert message (unless the ProgressIndicator2ISDN_x parameter is configured differently). In this case, the PBX / PSTN plays a ringback tone to the originating terminal. Note that the receipt of a 183 response results in an ISDN Progress message (unless SIP183Behaviour is set to 1).

  • Page 893: Tone Detection Parameters

    Special Information Tone (SIT) detection. enable  [0] = Disable (default) [UserDefinedToneDetectorEnable]  [1] = Enable EMS: SIT Enable Enables SIT detection according to the ITU-T recommendation CLI: SIT-detector-enable E.180/Q.35. [SITDetectorEnable]  [0] = Disable (default) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 894: Metering Tone Parameters

    Mediant 800B Gateway and E-SBC Parameter Description  [1] = Enable To disconnect IP-to-ISDN calls when a SIT tone is detected, the following parameters must be configured:  SITDetectorEnable = 1  UserDefinedToneDetectorEnable = 1  ISDNDisconnectOnBusyTone = 1 (applicable for Busy,...
  • Page 895 ISDN) sends in AOC Facility messages to the PSTN (i.e., PBX). analoggw ChargeCode The format of the ini file table parameter is as follows: [ChargeCode] [ChargeCode] FORMAT ChargeCode_Index = ChargeCode_EndTime1, ChargeCode_PulseInterval1, ChargeCode_PulsesOnAnswer1, ChargeCode_EndTime2, ChargeCode_PulseInterval2, ChargeCode_PulsesOnAnswer2, ChargeCode_EndTime3, ChargeCode_PulseInterval3, ChargeCode_PulsesOnAnswer3, ChargeCode_EndTime4, ChargeCode_PulseInterval4, ChargeCode_PulsesOnAnswer4; Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 896: Telephone Keypad Sequence Parameters

    Mediant 800B Gateway and E-SBC Parameter Description [\ChargeCode] Where,  EndTime = Period (1 - 4) end time.  PulseInterval = Period (1 - 4) pulse interval.  PulsesOnAnswer = Period (1 - 4) pulses on answer. For example: ChargeCode 1 = 7,30,1,14,20,2,20,15,1,0,60,1;...
  • Page 897 1 and the 3WayConferenceMode parameter is set to 2. Note that the settings of the ConferenceCode parameter is ignored.  Flash + 4: Makes a call transfer. Note: This parameter is applicable only to FXS interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 898 Mediant 800B Gateway and E-SBC Parameter Description Web: Flash Keys Sequence Defines the Flash keys sequence timeout - the time (in msec) Timeout that the device waits for digits after the user presses the flash CLI: flash-key-seq-tmout button (Flash Hook + Digit mode - when the parameter [FlashKeysSequenceTimeout] FlashKeysSequenceStyle is set to 1 or 2).
  • Page 899 Web: Reject Anonymous Call Defines the keypad sequence that de-activates the reject Deactivate anonymous call option. After the sequence is pressed, a EMS: Reject Anonymous Call confirmation tone is heard. Deact [KeyRejectAnonymousCallDeact] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 900: General Fxo Parameters

    Mediant 800B Gateway and E-SBC 54.10.11 General FXO Parameters The general FXO and FXS parameters are described in the table below. Table 54-66: General FXO and FXS Parameters Parameter Description FXS Parameters Web: FXS Coefficient Type Determines the FXS line characteristics (AC and DC) EMS: Country Coefficients according to USA or Europe (TBR21) standards.
  • Page 901 The valid range (in milliseconds) is 0 to 20,000 (i.e., 20 seconds). The default is 1,000 (i.e., 1 second). Web: Ring Detection Timeout [sec] Defines the timeout (in seconds) for detecting the second ring Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 902 Mediant 800B Gateway and E-SBC Parameter Description EMS: Timeout Between Rings after the first detected ring. CLI: ring-detection-tout If automatic dialing is not used and Caller ID is enabled, the [FXOBetweenRingTime] device seizes the line after detection of the second ring signal (allowing detection of caller ID sent between the first and the second rings).

  • Page 903: Trunk Groups And Routing Parameters

    For a description of this table, see ''Configuring Hunt Group Settings'' on page 339. Web: Channel Select Mode Defines the method for allocating incoming IP-to-Tel calls to EMS: Channel Selection Mode a channel. This parameter applies to the following: CLI: ch-select-mode Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 904 Mediant 800B Gateway and E-SBC Parameter Description  [ChannelSelectMode] All Trunk Groups configured without a channel select mode in the Trunk Group Settings table (see ''Configuring Hunt Group Settings'' on page 339).  All channels and trunks configured without a Trunk Group for all Trunk Groups channels that are configured without a Trunk Group ID,.
  • Page 905 INVITE SIP URI. Web/EMS: Tel to IP Routing Mode For a description of this parameter, see ''Configuring CLI: tel2ip-rte-mode Outbound IP Routing Table'' on page 369. [RouteModeTel2IP] Outbound IP Routing Table Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 906 Mediant 800B Gateway and E-SBC Parameter Description Web: Outbound IP Routing Table This table parameter configures the Outbound IP Routing EMS: SIP Routing > Tel to IP Table for routing Tel-to-IP and IP-to-IP calls. CLI: configure voip > gw routing tel2ip-...
  • Page 907 Tel side.  [0] = (Default) Q.931 Redirecting Number Information Element (IE).  [1] = ETSI DivertingLegInformation2 in a Facility IE. Web: Add CIC Determines whether to add the Carrier Identification Code Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 908 Mediant 800B Gateway and E-SBC Parameter Description CLI: add-cic (CIC) as a prefix to the destination phone number for IP-to- [AddCicAsPrefix] Tel calls. When this parameter is enabled, the 'cic' parameter in the incoming SIP INVITE can be used for IP-to- Tel routing decisions.
  • Page 909 Proxy server performs call forking (Proxy server forwards the INVITE to multiple SIP User Agents). The device sends a SIP ACK and BYE in response to any additional SIP 2xx received from the Proxy within this timeout. Once this Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 910: Ip Connectivity Parameters

    Mediant 800B Gateway and E-SBC Parameter Description timeout elapses, the device ignores any subsequent SIP 2xx. The number of supported forking calls per channel is 20. In other words, for an INVITE message, the device can receive up to 20 forking responses from the Proxy server.

  • Page 911: Alternative Routing Parameters

    Contact header. If the contact responds with a SIP response that is defined in the Reasons for Tel-to-IP Alternative Routing table, the device tries Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 912 Mediant 800B Gateway and E-SBC Parameter Description to redirect the call to the next contact, and so on. If a contact responds with a response that is not configured in the table, the device does not try to redirect the call to the next contact, and drops the call.
  • Page 913 TCP, if Trunk Group ID 2 is unavailable: ForwardOnBusyTrunkDest 1 = 2, 112@10.13.4.12:5060;transport=tcp; For a detailed description of this table, see ''Alternative Routing to IP Destination upon Busy Trunk'' on page 390. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 914: Number Manipulation Parameters

    Mediant 800B Gateway and E-SBC 54.10.15 Number Manipulation Parameters The number manipulation parameters are described in the table below. Table 54-70: Number Manipulation Parameters Parameter Description [ManipulateIP2PSTNReferTo] Enables the manipulation of the called party (destination) number according to the SIP Refer-To header received by the device for TDM (PSTN) blind transfer.
  • Page 915 Tel, the redirect reason is set to the CLI: tel2ip-redir-reason value of this parameter before the device sends it on to the IP. [SetTel2IpRedirectReason]  [-1] Not Configured (default)  [0] Unkown Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 916 Mediant 800B Gateway and E-SBC Parameter Description  [1] Busy  [2] No Reply  [3] Network Busy  [4] Deflection  [9] DTE out of Order  [10] Forwarding DTE  [13] Transfer  [14] PickUp  [15] Systematic/Unconditional Note: This parameter is applicable only to digital PSTN interfaces (ISDN).
  • Page 917 [AddTrunkGroupAsPrefixTo  [0] No (default) Source]  [1] Yes Web: Replace Empty Determines whether the internal channel number is used as the Destination with B-channel destination number if the called number is missing. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 918 Mediant 800B Gateway and E-SBC Parameter Description  Phone Number [0] No (default) EMS: Replace Empty Dst With  [1] Yes Port Number Note: This parameter is applicable only to Tel-to-IP calls and if the CLI: empty-dst-w-bch-nb called number is missing.
  • Page 919 SIP message for IP-to-Tel calls. This can include modifying map-ip2tel or removing the calling name. The format of this table ini file [CallingNameMapIp2Tel] parameter is as follows: [ CallingNameMapIp2Tel ] FORMAT CallingNameMapIp2Tel_Index = Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 920 Mediant 800B Gateway and E-SBC Parameter Description CallingNameMapIp2Tel_ManipulationName, CallingNameMapIp2Tel_DestinationPrefix, CallingNameMapIp2Tel_SourcePrefix, CallingNameMapIp2Tel_CallingNamePrefix, CallingNameMapIp2Tel_SourceAddress, CallingNameMapIp2Tel_RemoveFromLeft, CallingNameMapIp2Tel_RemoveFromRight, CallingNameMapIp2Tel_LeaveFromRight, CallingNameMapIp2Tel_Prefix2Add, CallingNameMapIp2Tel_Suffix2Add; [ \CallingNameMapIp2Tel ] For a detailed description of this table, see ''Configuring SIP Calling Name Manipulation'' on page 352. Calling Name Manipulations Tel-to-IP Table CLI: configure voip >...
  • Page 921 (SourceNumberMapIP2Tel parameter). This [PerformAdditionalIP2TELS ourceManipulation] enables you to configure only a few manipulation rules for complex number manipulation requirements (that generally require many Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 922 Mediant 800B Gateway and E-SBC Parameter Description rules).  [0] = Disable (default)  [1] = Enable Source Phone Number Manipulation for Tel-to-IP Calls Table Web: Source Phone Number This table parameter manipulates the source phone number for Tel- Manipulation Table for Tel >...
  • Page 923 Determines whether the received Phone-Context parameter is added Context As Prefix as a prefix to the outgoing ISDN Setup message with (for digital CLI: add-ph-cntxt-as-pref interfaces) Called and Calling numbers. [AddPhoneContextAsPrefix]  [0] Disable (default)  [1] Enable Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 924: Sbc Parameters

    Mediant 800B Gateway and E-SBC 54.11 SBC Parameters The SBC and CRP parameters are described in the table below. Table 54-71: SBC and CRP Parameters Parameter Description CRP-specific Parameters Web: CRP Application Enables the CRP application. EMS: Enable CPR Application ...
  • Page 925  If the received header’s original value is greater than the parameter's value, the header’s value is replaced by the user-defined parameter’s value. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 926 Mediant 800B Gateway and E-SBC Parameter Description The valid value range is 1-70. The default is 10. Web: SBC Session-Expires Defines the SBC session refresh timer (in seconds) in the CLI: sbc-sess-exp-time Session-Expires header of outgoing INVITE messages. [SBCSessionExpires] The valid value range is 90 (according to RFC 4028) to 86400.
  • Page 927 IP Profile. [SBCEnforceMediaOrder] Enables the device to include all previously negotiated media lines within the current session ('m=' line) in the SDP offer- Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 928 Mediant 800B Gateway and E-SBC Parameter Description answer exchange (RFC 3264).  [0] Disable (default)  [1] Enable For example, assume a call (audio) has been established between two endpoints and one endpoint wants to subsequently send an image in the same call session. If this parameter is enabled, the endpoint includes the previously negotiated media type (i.e., audio) with the new negotiated media type (i.e.,...
  • Page 929 (i.e., do not all occur simultaneously). The device takes any random number between 0 and the value configured by this parameter, and then subtracts this random number from the original expiry time value. For example, Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 930 Mediant 800B Gateway and E-SBC Parameter Description assume that the original expiry time is 120 and this parameter is set to 10. If the device randomly chooses the number 5 (i.e., between 0 and 10), the resultant expiry time will be 115 (120 minus 5).
  • Page 931 [1] Enable = The device forwards the SIP authentication response (for the BYE request) to the request sender and waits for the user to authenticate it. The call is disconnected only if the authenticating server responds with a 200 OK. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 932 Mediant 800B Gateway and E-SBC Parameter Description Web: SBC Enable Subscribe Enables the device to send SIP 100 Trying responses upon Trying receipt of SUBSCRIBE or NOTIFY messages. CLI: configure voip > sbc general-  [0] Disable (Default) setting > set sbc-subs-try ...
  • Page 933 The valid value is a string of up to 16 characters. The default is "acgateway-<original prefix destination number>". For example, "acgateway-200". For more information, see Configuring SBC IP-to-IP Routing Rules on page 515. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 934 Mediant 800B Gateway and E-SBC Parameter Description CLI: sbc-media-sync Enables SBC media synchronization process for calls [EnableSBCMediaSync] established from SIP forking that is initiated by external proxy servers. It is possible that a call is established with the media not synchronized between the SBC legs. Media synchronization resolves this issue.
  • Page 935 Routing Rules'' on page 515. SBC Alternative Routing Reasons Table Web: SBC Alternative Routing This table parameter configures the SBC Alternative Routing Reasons Reasons table. The format of the ini file table parameter is as Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 936 Mediant 800B Gateway and E-SBC Parameter Description EMS: Alternative Routing Reasons follows: CLI: configure voip > sbc routing [ SBCAlternativeRoutingReasons ] sbc-alternative-routing-reasons FORMAT SBCAlternativeRoutingReasons_Index = [SBCAlternativeRoutingReasons SBCAlternativeRoutingReasons_ReleaseCause; [ \SBCAlternativeRoutingReasons ] For a detailed description of this table, see ''Configuring SIP Response Codes for Alternative Routing Reasons'' on page 524.

  • Page 937: Standalone Survivability Parameters

    20. Web: SAS Local SIP TCP Port Defines the local TCP port used to send/receive SIP messages EMS: Local SIP TCP Port for the SAS application. The SIP entities in the local network Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 938 Mediant 800B Gateway and E-SBC Parameter Description CLI: sas-local-sip-tcp-port need to send the registration requests to this port. When [SASLocalSIPTCPPort] forwarding the requests to the proxy ('Normal Mode'), this port serves as the source port. The valid range is 1 to 65,534. The default is 5080.
  • Page 939 SAS is in Emergency mode. For example, if this [SASSubscribeResponse] parameter is set to "200", then SAS sends a SIP 200 OK in response to a SUBSCRIBE message, when in Emergency Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 940 Mediant 800B Gateway and E-SBC Parameter Description mode. The valid value is 200 to 699. The default is 489. Web: Enable ENUM Enables SAS to perform ENUM (E.164 number to URI mapping) CLI: enable-enum queries when receiving INVITE messages in SAS emergency [SASEnableENUM] mode.

  • Page 941: Ip Media Parameters

    Table 54-73: IP Media Parameters Parameter Description Web: Number of Media Channels Defines the maximum number of DSP channels allocated for EMS: Media Channels various functionalities such as transcoding, IP conferencing, CLI: media-channels The default is 0. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 942 Mediant 800B Gateway and E-SBC Parameter Description [MediaChannels] Notes:  For this parameter to take effect, a device reset is required.  The SBC application does not require DSP channels. The SBC application uses DSP channels only if media transcoding is needed, where two DSP channels are used per transcoding session.
  • Page 943 [22] 22 = 13.00 dB/sec  [23] 23 = 14.00 dB/sec  [24] 24 = 15.00 dB/sec  [25] 25 = 20.00 dB/sec  [26] 26 = 25.00 dB/sec  [27] 27 = 30.00 dB/sec Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 944 Mediant 800B Gateway and E-SBC Parameter Description  [28] 28 = 35.00 dB/sec  [29] 29 = 40.00 dB/sec  [30] 30 = 50.00 dB/sec  [31] 31 = 70.00 dB/sec Web: AGC Redirection Determines the AGC direction. EMS: Redirection ...

  • Page 945: Services

    CLI: configure voip/services sip- [ SIPRecRouting ] recording sip-rec-routing FORMAT SIPRecRouting_Index = [SIPRecRouting] SIPRecRouting_RecordedIPGroupID, SIPRecRouting_RecordedSourcePrefix, SIPRecRouting_RecordedDestinationPrefix, SIPRecRouting_PeerIPGroupID, SIPRecRouting_PeerTrunkGroupID, SIPRecRouting_Caller, SIPRecRouting_SRSIPGroupID; [ \SIPRecRouting ] For a detailed description of this table, see ''Configuring SIP Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 946: Radius And Ldap Parameters

    Mediant 800B Gateway and E-SBC Parameter Description Recording Routing Rules'' on page 184. 54.14.2 RADIUS and LDAP Parameters 54.14.2.1 General Parameters The general RADIUS and LDAP parameters are described in the table below. General RADIUS and LDAP Parameters Parameter Description...
  • Page 947 Note: For this parameter to take effect, a device reset is required. EMS: RADIUS Auth Server Port CLI: auth-server-port [RADIUSAuthPort] Web: RADIUS Shared Defines the 'secret' used to authenticate the device to the RADIUS Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 948 Mediant 800B Gateway and E-SBC Parameter Description Secret server. This should be a cryptically strong password. EMS: RADIUS Auth Server Secret CLI: shared-secret [SharedSecret] RADIUS Authentication Parameters Web: Password Local Defines the device's mode of operation regarding the timer (configured...

  • Page 949: Ldap Parameters

    Defines the name of the attribute that represents the user PBX Number attribute name number in the Microsoft AD database. CLI: ldap-pbx-nm-attr The valid value is a string of up to 49 characters. The default is Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 950 Mediant 800B Gateway and E-SBC Parameter Description [MSLDAPPBXNumAttribut "telephoneNumber". eName] 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 951: Least Cost Routing Parameters

    Cost services least-cost-routing Group are considered as a higher or lower cost route compared to routing-rule-groups other matching routing rules that are assigned Cost Groups. [RoutingRuleGroups] [ RoutingRuleGroups ] FORMAT RoutingRuleGroups_Index = RoutingRuleGroups_LCREnable, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 952: Call Setup Rules Parameters

    Mediant 800B Gateway and E-SBC Parameter Description RoutingRuleGroups_LCRAverageCallLength, RoutingRuleGroups_LCRDefaultCost; [ \RoutingRuleGroups ] Note: For a detailed description of this table, see ''Enabling LCR and Configuring Default LCR'' on page 216. Web: Cost Group Table This table parameter configures the Cost Groups for LCR, where each...

  • Page 953: Sbc And Dsp Channel Capacity

    • The number of channels refers to the maximum channel capacity of the device. • For additional DSP templates, contact your AudioCodes sales representative. • To select the DSP Template that you want to use on the device, see Configuring DSP Templates.
  • Page 954 The capacity figures listed in the table below are accurate at the time of publication of this document. However, these figures may change due to a later software update. For the latest figures, please contact your AudioCodes sales representative. •...

  • Page 955: Channel Capacity And Capabilities

    38/32 22/28 212/218 Mix x 8 √ √ √ 1 x E1/T1 30/24 9/14 7/11 30/36 220/226 1 x E1 & √ 4 x BRI 1 x E1 & √ 4 x FXS Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 956 Mediant 800B Gateway and E-SBC Max. SBC Sessions Transcoding Sessions Telephony Channels From Profile 2 with Additional Advanced DSP Capabilities Interface Allocated Assembly for PSTN Mediant Mediant Profile Profile SILK 800B SILK G.722 NB / V.150.1 Enhancements Detectors iLBC 2 x E1 &...
  • Page 957 Conference Participants represents 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. For figures on the maximum number of participants per configuration, please contact your AudioCodes sales representative. •...
  • Page 958 Mediant 800B Gateway and E-SBC Reader's Notes User's Manual Document #: LTRT-10278...

  • Page 959: 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. Table 56-1: Technical Specifications Function Specification Telephony Interfaces ...
  • Page 960 Mediant 800B Gateway and E-SBC Function Specification Interoperability SIP B2BUA Full SIP transparency, mature and broadly deployed SIP stack SIP Interworking 3xx redirect, REFER, PRACK, Session Timer, Early media, Call hold, Delayed offer Registration Registration and authentication on behalf of an IP-PBX SIP over UDP to SIP over TCP or SIP over TLS, IPv4 to IPv6 ,v.34...
  • Page 961 Desktop or 19" rack mount Power 100-240V 1.5A 50-60 Hz  Operational: 5 to 40°C (41 to 104°F) Environmental  Storage: -25 to 85°C (-13 to 185°F)  Humidity: 10 to 90% non-condensing Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 962 User's Manual Ver. 6.8 www.audiocodes.com...

Table of Contents