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

Advertisement

Quick Links

See also: User Manual , Quick Manual
User
's Man
nual  
 
Ente
rprise S
Session
Analo
og & D
igital V
Me
edian
 
n Borde
er Contr
VoIP Me
edia Ga
nt 80
00B 
roller 
ateway
 
Gat
tewa
ay &
& E‐S
SBC
Vers
sion 6
6.8 
Novem
mber 201
14 
Docum
ment # LT
TRT‐1028 8 6 

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 800B

Summary of Contents for AudioCodes Mediant 800B

  • Page 1 User 's Man nual       Ente rprise S Session n Borde er Contr roller  Analo og & D igital V VoIP Me edia Ga ateway   edian nt 80 00B  tewa ay & & E‐S Vers sion 6 6.8  Novem mber 201 14  Docum ment # LT TRT‐1028 8 6 ...

  • Page 3: Table Of Contents

    Getting Familiar with CLI ..................67 7.1.1 Understanding Configuration Modes ...............67 7.1.2 Using CLI Shortcuts ....................68 7.1.3 Common CLI Commands ..................69 7.1.4 Configuring Tables in CLI ..................70 7.1.5 Understanding CLI Error Messages ................70 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 4 Mediant 800B Gateway and E-SBC Enabling CLI ......................71 7.2.1 Enabling Telnet for CLI ....................71 7.2.2 Enabling SSH with RSA Public Key for CLI.............71 Establishing a CLI Session ................... 73 Configuring Maximum Telnet/SSH Sessions ............74 Viewing and Terminating Current CLI Sessions ............ 74 Configuring Displayed Output Lines in CLI Terminal Window .......
  • Page 5 14.2.2.1 T.38 Fax Relay Mode ................161 14.2.2.2 G.711 Fax / Modem Transport Mode .............163 14.2.2.3 Fax Fallback ...................164 14.2.2.4 Fax/Modem Bypass Mode..............165 14.2.2.5 Fax / Modem NSE Mode ................166 14.2.2.6 Fax / Modem Transparent with Events Mode ........167 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 6 Mediant 800B Gateway and E-SBC 14.2.2.7 Fax / Modem Transparent Mode ............167 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......168 14.2.3 V.34 Fax Support ....................168 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........169 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ............169 14.2.3.3 V.34 Fax Relay for SG3 Fax Machines ..........170...
  • Page 7 19.2 Configuring Coder Groups .................. 300 19.3 Configuring Tel Profile ..................301 19.4 Configuring IP Profiles ..................304 Gateway Application .....................329 20 Introduction ..................... 331 21 Digital PSTN ..................... 333 21.1 Configuring Trunk Settings ................. 333 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 8 Mediant 800B Gateway and E-SBC 21.2 TDM and Timing ....................335 21.2.1 Configuring TDM Bus Settings ................335 21.2.2 Clock Settings ......................336 21.2.2.1 Recovering Clock from PSTN Line Interface .........336 21.2.2.2 Configuring Internal Clock as Clock Source...........337 21.3 Configuring CAS State Machines ............... 337 21.4 Configuring Digital Gateway Parameters ............
  • Page 9 26.11.4 Enhanced 9-1-1 Support for Lync Server 2010 .............434 26.11.4.1 About E9-1-1 Services ................434 26.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........435 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 ..........443 26.12 Multilevel Precedence and Preemption ............... 446 26.12.1 MLPP Preemption Events in SIP Reason Header ..........448...
  • Page 10 Mediant 800B Gateway and E-SBC 27.2 Configuring Metering Tones ................459 27.3 Configuring FXO Settings ................... 459 27.4 Configuring Authentication .................. 460 27.5 Configuring Automatic Dialing ................462 27.6 Configuring Caller Display Information..............463 27.7 Configuring Call Forward ..................465 27.8 Configuring Caller ID Permissions ..............
  • Page 11 29.5.3 Configuring SBC IP-to-IP Routing .................532 29.5.4 Configuring SIP Response Codes for Alternative Routing Reasons .....541 29.6 SBC Manipulations ..................... 543 29.6.1 Configuring IP-to-IP Inbound Manipulations ............545 29.6.2 Configuring IP-to-IP Outbound Manipulations ............548 Cloud Resilience Package ..................553 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 12 Mediant 800B Gateway and E-SBC 30 CRP Overview ....................555 31 CRP Configuration ..................557 31.1 Enabling the CRP Application ................557 31.2 Configuring Call Survivability Mode ..............558 31.3 Pre-Configured IP Groups .................. 559 31.4 Pre-Configured IP-to-IP Routing Rules ............... 560 31.4.1 Normal Mode ......................560...
  • Page 13 41.1.1.2 Provisioning from TFTP Server using DHCP Option 66 ......629 41.1.2 HTTP-based Provisioning ..................629 41.1.3 FTP- or NFS-based Provisioning ................630 41.1.4 Provisioning using AudioCodes EMS ..............630 41.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 631 41.2.1 Files Provisioned by Automatic Update ..............631 41.2.2 File Location for Automatic Update ...............631...
  • Page 14 Mediant 800B Gateway and E-SBC 43 Automatic Archiving of Configuration File ........... 643 44 USB Storage Capabilities ................645 Status, Performance Monitoring and Reporting ..........647 45 System Status ....................649 45.1 Viewing Device Information ................649 45.2 Viewing Ethernet Port Information ..............650 46 Carrier-Grade Alarms ..................
  • Page 15 50 Syslog and Debug Recordings ..............697 50.1 Syslog Message Format ..................697 50.1.1 Event Representation in Syslog Messages ............698 50.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......700 50.1.3 SNMP Alarms in Syslog Messages ...............701 50.2 Enabling Syslog ....................701 50.3 Configuring Web Operations to Report to Syslog ..........
  • Page 16 Mediant 800B Gateway and E-SBC 56.2.7 NFS Parameters ....................752 56.2.8 DNS Parameters ....................753 56.2.9 DHCP Parameters ....................754 56.2.10 NTP and Daylight Saving Time Parameters ............756 56.3 Debugging and Diagnostics Parameters ............. 757 56.3.1 General Parameters ....................758 56.3.2 SIP Test Call Parameters ..................759 56.3.3 Syslog, CDR and Debug Parameters ..............760...
  • Page 17 56.14.4 Call Setup Rules Parameters ................990 57 SBC and DSP Channel Capacity ..............991 57.1 Signaling-Media Sessions & User Registrations ..........991 57.2 Channel Capacity and Capabilities ..............993 58 Technical Specifications ................997 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 18 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 19: 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 20: 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 21 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 22 Mediant 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 23: 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 24 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 25: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 27: 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 28 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 29: 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 "O+M+C" Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 30 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 31: Configuring Voip Lan Interface For Oamp

    IP address of the device; the Web interface's Web Login screen appears: Figure 4-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 32 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 109.

  • Page 33: Cli

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

  • Page 35: Management Tools

    Part II Management Tools...

  • Page 37: 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 733. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 38 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 39: 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 40: 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 39). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...

  • Page 41: Areas Of The Gui

    ''Navigation Tree'' on page 43. 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 45. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 42: 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 584).

  • Page 43: 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 44: 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 45: 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 46 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 47: 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 584). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 48: 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 49 - Displays the previous page  - Displays the first page Defines the number of rows to display per page. You can select 5 or 10, where the default is 10. Displays the currently displayed page number. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 50: Searching For Configuration Parameters

    Mediant 800B Gateway and E-SBC 6.1.7 Searching for Configuration Parameters You can locate the exact Web page on which a specific parameter appears, by using the Search feature. To search for a Web parameter, you must use the ini file parameter name as the search key.

  • Page 51: 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 52: 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 53: 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 54 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 55 (gray): Link is not configured  (red): Link error To view detailed port information, click the port icon (see Viewing Ethernet Port Information on page 650). Fast Ethernet port status icons. See Item 6 for a description. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 56: 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 57 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 58: 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 59 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 60: 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 61  Failed Access = This state is automatically set for users that exceed a user-defined number of failed login attempts, set by the 'Deny Access on Fail Count' parameter (see ''Configuring Web Security Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 62 Mediant 800B Gateway and E-SBC Parameter Description Settings'' on page 64). These users can log in only after a user- defined timeout configured by the 'Block Duration' parameter (see below) or if their status is changed (to New or Valid) by a System Administrator or Master.

  • Page 63: 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 64: 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-10286...

  • Page 65: 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 66 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 67: Cli-Based Management

    Enable mode upon initial login. For configuring user access levels, see Configuring Web User Accounts on page 56. • 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 68: 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 69: Common Cli Commands

    Displays the available command list of the current command-set. | <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 70: 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 71: Enabling Cli

    OpenSSH pre-installed; Windows-based PCs require an SSH client software such as PuTTY, which downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty. By default, SSH uses the same username and password as the Telnet and Web server. SSH supports 1024/2048-bit RSA public keys, providing carrier-grade security. Follow the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 72 Mediant 800B Gateway and E-SBC instructions below to configure the device with an administrator RSA key as a means of strong authentication.  To enable SSH and configure RSA public keys for Windows (using PuTTY SSH software): Start the PuTTY Key Generator program, and then do the following: Under the 'Parameters' group, do the following: ♦...

  • Page 73: Establishing A Cli Session

    ''Configuring Web User Accounts'' on page 56.  To establish a CLI session with the device: Connect the device to the network. Establish a Telnet or SSH session using the device's OAMP IP address. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 74: Configuring Maximum Telnet/Ssh Sessions

    Mediant 800B Gateway and E-SBC Log in to the session using the username and password assigned to the Admin user of the Web interface: At the Username prompt, type the username, and then press Enter: Username: Admin At the Password prompt, type the password, and then press Enter:...
  • Page 75 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 76: 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 77: 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 78: 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 79 (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 80: 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 81: 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 82 Mediant 800B Gateway and E-SBC Parameter Description  [0] None (default) CLI: priv-protocol [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 83: 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 84 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 85: 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 86. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 86: 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 87: Configuring Password Display In Ini File

    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 88 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 89: General System Settings

    Part III General System Settings...

  • Page 91: 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 92 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 93 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 94 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 95: 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 96: 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 97: 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 98: 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 99: 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 100: 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 101: 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 91). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 102: 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 103: Date And Time

    "1". For USA New York, the UTC/GMT offset is -5 hours and therefore, the offset is a minus value and configured as "-5". To configure Daylight Saving Time (DST), see 'Configuring Daylight Saving Time' on page 105. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 104 Mediant 800B Gateway and E-SBC You can also configure the device to authenticate and validate the NTP messages received from the NTP server. Authentication is done using an authentication key with the MD5 cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication.

  • Page 105: Configuring Daylight Saving Time

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

  • Page 107: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 109: Network

    You can also configure these ports using the table ini file parameter, PhysicalPortsTable or CLI command, configure voip/physical-port. Note: All the LAN ports have the same MAC address. This is the MAC address of the device itself. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 110 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 111: Configuring Ethernet Port Groups

    Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group. To remove the port, either set the 'Member' field to None or to a different port. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 112 Mediant 800B Gateway and E-SBC  To configure Ethernet Groups: Open the Ethernet Group Settings page (Configuration tab > VoIP menu > Network > Ethernet Groups Table). If the port that you want to assign to a specific Ethernet Group is already associated...

  • Page 113: 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 114 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 115: Configuring Ip Network Interfaces

    For configuring Quality of Service (QoS), see ''Configuring the QoS Settings'' on page 126.  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 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 116 Mediant 800B Gateway and E-SBC  Primary and secondary domain name server (DNS) addresses (optional)  Underlying Ethernet Device: Layer-2 bridging device and assigned a VLAN ID. As the Ethernet Device is associated with an Ethernet Port Group, this is useful for setting trusted and un-trusted networks on different physical Ethernet ports.
  • Page 117 Specifically, instead of using eight-bit address blocks, it uses the variable-length subnet masking technique to allow allocation on arbitrary-length prefixes. The prefix length for IPv4 must be set to a value from 0 to 30. The Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 118: Assigning Ntp Services To Application Types

    Mediant 800B Gateway and E-SBC Parameter Description 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. CLI: gateway When traffic is sent from this interface to an unknown destination [InterfaceTable_Gateway] (i.e., not in the same subnet and not defined for any static routing...

  • Page 119: 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 120: 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 121 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 122: 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 123 'Destination' field is ignored. To reach a specific host, enter its IP address in the 'Destination' field and 32 in the 'Prefix Length' field. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 124: Configuration Example Of Static Ip Routes

    Mediant 800B Gateway and E-SBC Parameter Description Gateway Defines the IP address of the Gateway (next hop) used for traffic CLI: gateway destined to the subnet/host defined in the 'Destination' / 'Prefix [StaticRouteTable_Gateway] Length' field. Notes:  The Gateway's address must be in the same subnet as the IP address of the network interface that is associated with the static route (using the 'Device Name' parameter - see above).

  • Page 125: 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 126: 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 127 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 128: 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 129 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 130: 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 131 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 132: 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 133: 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. Table 12-17: NFS Table Parameter Descriptions Parameter Description Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 134: Network Address Translation Support

    Mediant 800B Gateway and E-SBC 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 135: Configuring A Static Nat Ip Address For All Interfaces

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

  • Page 136: Configuring Nat Translation Per Ip Interface

    Mediant 800B Gateway and E-SBC In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. 12.11.1.2 Configuring NAT Translation per IP Interface...

  • Page 137: Remote Ua Behind Nat

    Use Source Address' parameter in the IP Group table (see ''Configuring IP Groups'' on page 263). If this feature is disabled, the device's NAT detection is according to the settings of the global parameter, 'SIP NAT Detection' parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 12.11.2.2 Media (RTP/RTCP/T.38) When a remote UA initiates a call and is not located behind a NAT server, the device sends the RTP (or RTCP, T.38) packets to the remote UA using the IP address / UDP port in the SIP message (Contact header).
  • Page 139 T.38 No-Op: T.38 No-Op packets are sent only while a T.38 session is activated. Sent packets are a duplication of the previously sent frame (including duplication of the sequence number). Note: Receipt of No-Op packets is always supported. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 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. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).
  • Page 141 'Timeout To Relatch RTCP' ♦ 'Fax Relay Rx/Tx Timeout' Click Submit, and then save ("burn") your settings to flash memory. For a detailed description of the robust media parameters, see ''General Security Parameters'' on page 767. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 142: Multiple Routers Support

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

  • Page 143: 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 576. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 144 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 145 ''Configuring IP Network Interfaces'' on page 115. Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 146 Mediant 800B Gateway and E-SBC Parameter Description 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. In addition to this field, the...

  • Page 147: 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 148: 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 149: 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 150 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 151 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 525)  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 152 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 153: 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 154 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 155: Viewing Ids Alarms

    To view the blacklist: # show voip security ids blacklist active For example: Active blacklist entries: 10.33.5.110(NI:0) remaining 00h:00m:10s in blacklist Where SI is the SIP Interface and NI is the network interface. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 156 Mediant 800B Gateway and E-SBC The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This only occurs if you have configured Syslog (see ''Enabling Syslog'' on page 701). An example of a Syslog message with IDS alarms and notifications is shown below:...

  • Page 157: 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 158: 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 159: 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 173. • For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 733. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 160 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-10286...

  • Page 161: Fax/Modem Operating Modes

    You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 162 Mediant 800B Gateway and E-SBC 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. 14.2.2.1.1 Switching to T.38 Mode using SIP Re-INVITE In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal...

  • Page 163: Fax / Modem Transport Mode

    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 164: Fax Fallback

    Mediant 800B Gateway and E-SBC  Echo Canceller = off  Silence Compression = off  Echo Canceller Non-Linear Processor Mode = off  Dynamic Jitter Buffer Minimum Delay = 40  Dynamic Jitter Buffer Optimization Factor = 13 After a few seconds upon detection of fax V.21 preamble or super G3 fax signals, the device sends a second Re-INVITE enabling the echo canceller (the echo canceller is disabled only on modem transmission).

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

    Fax (IsFaxUsed = 0). In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Version 6.8 Mediant 800B Gateway and E-SBC...

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

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

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

    Set the ini file parameter, V34FaxTransportType to 2 (Bypass). 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. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 170: Fax Relay For Sg3 Fax Machines

    Mediant 800B Gateway and E-SBC  To use T.38 mode for V.34 and T.30 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Relay (FaxTransportMode = 1). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0).

  • Page 171: 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 172: 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 173: Support

    NAT for the answering fax machine. The originating fax does not wait for an answer, but immediately starts sending T.38 packets to the terminating fax machine upon receipt of a re-INVITE with T.38 only in the SDP, or T.38 and audio media in the SDP. This feature is Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 174: Configuring Rtp/Rtcp Settings

    Mediant 800B Gateway and E-SBC configured using the T38FaxSessionImmediateStart parameter. The No-Op packets are enabled using the NoOpEnable and NoOpInterval parameters. 14.3 Configuring RTP/RTCP Settings This section describes configuration relating to Real-Time Transport Protocol (RTP) and RTP Control Protocol (RTCP).

  • Page 175: Comfort Noise Generation

    Figure 14-4: Comfort Noise Parameter in RTP/RTCP Settings Page Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Click Submit. Note: This feature is applicable only to the Gateway application. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 176: 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 177: 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 178: 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 local UDP ports for RTP, RTCP, and T.38 media streams. The range of possible UDP ports that can be used, depending on configuration, is 6,000 through to 65,535.

  • Page 179: Configuring Ip Media Settings

    'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. 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 180: Configuring Various Codec Attributes

    Mediant 800B Gateway and E-SBC 14.5 Configuring Various Codec Attributes The following codec attribute settings can be configured in the General Media Settings page:  AMR coder: • 'Payload Format': Defines the AMR payload format type.  SILK coder (Skype's default audio codec): •...

  • Page 181: Configuring Media (Srtp) Security

    770. • When SRTP is used, the channel capacity may be reduced.  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 182 Mediant 800B Gateway and E-SBC Security). Figure 14-10: Media Security Page Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 584.

  • Page 183: Services

    Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Option 66 TFTP Server Name Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 184 Mediant 800B Gateway and E-SBC DHCP Option Code DHCP Option Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
  • Page 185 Defines the IP address (IPv4) of the NetBIOS WINS server CLI: netbios-server that is available to a Microsoft DHCP client. The value is sent [DhcpServer_NetbiosNameServer] in DHCP Option 44 (NetBIOS Name Server). The default value is 0.0.0.0. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 186 Mediant 800B Gateway and E-SBC Parameter Description Web: NetBIOS Node Type Defines the node type of the NetBIOS WINS server for a CLI: netbios-node-type Microsoft DHCP client. The value is sent in DHCP Option 46 [DhcpServer_NetbiosNodeType] (NetBIOS Node Type). ...

  • Page 187: Configuring The Vendor Class Identifier

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

  • Page 188: Configuring Additional Dhcp Options

    Mediant 800B Gateway and E-SBC Click Add; the following dialog box appears: Figure 15-2: DHCP Vendor Class Table - Add Record Dialog Box Configure a VCI for the DHCP server according to the parameters described in the table below. Click Submit.
  • Page 189  [1] IP address = IPv4 address.  [2] Hexadecimal = Hexadecimal-encoded string. For example, if you set the 'Value' parameter to "company.com", you need to set the 'Type' parameter to ASCII. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 190: Configuring Static Ip Addresses For Dhcp Clients

    Mediant 800B Gateway and E-SBC Parameter Description Web: Value Defines the value of the DHCP Option. For example, if you are CLI: value using Option 66, this parameter is used for specifying the TFTP [DhcpOption_Value] provisioning server (e.g., http://192.168.3.155:5000/provisioning/). The valid value is a string of up to 256 characters. By default, no value is defined.

  • Page 191: Viewing And Deleting Dhcp Clients

    # show voip dhcp mac  To view DHCP clients that have been blacklisted from DHCP implementation (due to duplicated IP addresses in the network, where another device is using the same IP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 192 Mediant 800B Gateway and E-SBC address as the one assigned to the client): # show voip dhcp black-list  To view or delete DHCP clients: Open the DHCP Servers page (Configuration tab > VoIP menu > Services > DHCP Severs).

  • Page 193: Sip-Based Media Recording

    Session (RS) from the Session Recording Client (SRC), which is on the path of the Communication Session (CS), to a Session Recording Server (SRS) at the recording equipment. 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 194 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 195 <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>1</label> Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 196: Enabling Sip-Based Media Recording

    Mediant 800B Gateway and E-SBC </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label> </stream> </recording> --boundary_ac1fffff85b— 15.2.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 196) become active.
  • Page 197 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 198: 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 199: Radius Authentication

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

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

     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 201: 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 202: 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 203: Ldap-Based Management And Sip Services

    The device then assigns the user the access level configured for that group (in 'Configuring Access Level per Management Groups Attributes' on page 210). The location in the directory where you want to search for the user's member group(s) is configured using the following: Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 204: Enabling The Ldap Service

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

  • Page 205: 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 Note: Each table row must be configured with a unique index. dex] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 206 Mediant 800B Gateway and E-SBC Parameter Description 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. apConfServerIp] Note: If you want to use an FQDN for the LDAP server, leave this parameter undefined and configure the FQDN in the 'LDAP Server Domain Name' parameter (see below).
  • Page 207 (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 210. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 208: 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 209: Configuring The Ldap Search Filter Attribute

    To configure the LDAP search filter for management users: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 15-13: LDAP Settings Page - LDAP Search Filter Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 210: Configuring Access Level Per Management Groups Attributes

    Mediant 800B Gateway and E-SBC Under LDAP Settings, in the 'LDAP Authentication Filter' parameter, enter the LDAP search filter attribute for searching the login username for user authentication. Click Submit. 15.4.6 Configuring Access Level per Management Groups Attributes The Management LDAP Groups table lets you configure LDAP group objects and their corresponding management user access level.

  • Page 211: Configuring Ldap Search Methods

    You can configure the device's method for searching the LDAP server(s) for the configured DN objects:  DN Search Method between Two LDAP Servers: When two LDAP servers are implemented, the device runs an LDAP query to search for DN object records on both Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 212: Configuring The Device's Ldap Cache

    Mediant 800B Gateway and E-SBC LDAP servers. You can configure how the device queries the DN object record between the two LDAP servers: • Parallel Search: The device queries the LDAP servers simultaneously. • Sequential Search: The device first queries one of the LDAP servers, and if the DN object is not found, it queries the second LDAP server.
  • Page 213 LDAP server again. The following procedure describes how to configure the device's LDAP cache in the Web interface. For a full description of the cache parameters, see 'LDAP Parameters' on page 989. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 214: Configuring Local Database For Management User Authentication

    Mediant 800B Gateway and E-SBC  To configure the LDAP cache: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 15-17: LDAP Settings Page - Cache Parameters Under LDAP Cache, do the following: From the 'LDAP Cache Service' drop-down list, select Enable to enable LDAP cache.
  • Page 215 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 216: Ldap-Based Login Authentication Example

    Mediant 800B Gateway and E-SBC 15.4.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 217 (where the attribute's value equals the username): Figure 15-20: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-21: User's memberOf Attribute Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 218 Mediant 800B Gateway and E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-22: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
  • Page 219 The management group and its corresponding access level is configured in the Management LDAP Groups table (see 'Configuring Access Level per Management Groups Attributes' on page 210): Figure 15-26: Configuring Management Group Attributes for Determining Access Level Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 15.4.11 Active Directory-based Routing for Microsoft Lync Typically, enterprises wishing to deploy the Microsoft® Lync™ Server are faced with a complex, call routing dial plan when migrating users from their existing PBX or IP PBX to the Lync Server platform.
  • Page 221 Mediation Server (which then routes the call to the Lync client). PBX / IP PBX: If the Lync client is not found in the AD, it routes the call to the PBX / IP PBX. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 222 Mediant 800B Gateway and E-SBC Mobile number: If the Lync client (or Mediation Server) is unavailable (e.g., SIP response 404 "Not Found" upon INVITE sent to Lync client), and the PBX / IP PBX is also unavailable, the device routes the call to the user's mobile number (if exists in the AD).

  • Page 223: Configuring Ad-Based Routing Rules

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

  • Page 225: Querying The Ad For Calling Name

    'Prefix to Add' field is set to "$LDAP-PBX Office". If the calling number is 4046 and the resultant LDAP query display name is "John Doe", the device sends the INVITE message with the following From header: From: John Doe <sip:4064@company.com> Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 226: Least Cost Routing

    Mediant 800B Gateway and E-SBC Notes: • The Calling Name Manipulation Table for Tel-to-IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value.
  • Page 227 Note that for one minute, Cost Groups "A" and "D" are identical, but due to the average call duration, Cost Group "D" is cheaper. Therefore, average call duration is an important factor in determining the cheapest routing role. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 228 Mediant 800B Gateway and E-SBC Below are a few examples of how you can implement LCR:  Example 1: This example uses two different Cost Groups for routing local calls and international calls: Two Cost Groups are configured as shown below:...

  • Page 229: Configuring Lcr

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

  • Page 231: Configuring Cost Groups

    Note: When calculating the cost of a call, if the current time of the call is not within a time band configured for the Cost Group, then this default connection cost is used. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 232: Configuring Time Bands For Cost Groups

    Mediant 800B Gateway and E-SBC Parameter Description Default Minute Cost Defines the call charge per minute for a call outside the time CLI: default-minute-cost bands. [CostGroupTable_DefaultMinuteC The valid value range is 0-65533. The default is 0. ost] Note: When calculating the cost of a call, if the current time of the call is not within a time band configured for the Cost Group, then this default charge per minute is used.

  • Page 233: Assigning Cost Groups To Routing Rules

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

  • Page 234: Configuring Call Setup Rules

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

  • Page 238: Call Setup Rule Examples

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

  • Page 241: 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 242: Configuring Clock Synchronization Between Device And Sem

    In other words, you need to configure them with the same NTP server. The NTP server can be one of the following:  AudioCodes EMS server (also acting as an NTP server)  Third-party, external NTP server Once you have determined the NTP server, all the elements--device, SEM, and EMS--must be configured with the same NTP server address.
  • Page 243  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 242.
  • Page 244 Mediant 800B Gateway and E-SBC Table 16-1: Quality of Experience Profile Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [QOEProfile_Index] Profile Name Defines an arbitrary name to easily identify the QoE Profile. CLI: name The valid value is a string of up to 20 characters.
  • Page 245 MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.  Delay values are in msec.  Packet Loss values are in percentage (%).  Jitter is in msec.  Echo measures the Residual Echo Return Loss (RERL) in dB. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 246: Configuring Bandwidth Profiles

    Mediant 800B Gateway and E-SBC Parameter Description Yellow Red Hysteresis Defines the fluctuation (change) from the value configured for the CLI: yellow-red-hysteresis Yellow-Red threshold. When the threshold is exceeded by this [QOEColorRules_YellowRedH hysteresis value, the device sends a report to the SEM indicating ysteresis] this change.
  • Page 247 CLI: egress-video-bandwidth [BWProfile_EgressVideoBandwidth] Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). CLI: ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth CLI: total-egress-bandwidth threshold (in Kbps). [BWProfile_TotalEgressBandwidth] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 248 Mediant 800B Gateway and E-SBC Parameter Description Total Ingress Bandwidth Defines the total (video and audio) incoming bandwidth CLI: total-ingress-bandwidth threshold (in Kbps). [BWProfile_TotalIngressBandwidth] Warning Threshold Defines the threshold (in percentage) of the bandwidth CLI: warning-threshold thresholds that if exceeded is considered a Warning alarm [BWProfile_WarningThreshold] (Green-Yellow threshold).

  • Page 249: Configuring Media Enhancement Profiles

     Media Enhancement Profile table: Table ini file parameter, MediaEnhancementProfile or CLI command, configure voip/qoe media-enhancement  Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules or CLI command, configure voip/qoe media-enhancement-rules Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 250 Mediant 800B Gateway and E-SBC  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Click Add; the following dialog box appears: Figure 16-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below.
  • Page 251 Defines an alternative IP Profile ID for the IP Group that CLI: value is associated with this rule, if this rule is applied. This [MediaEnhancementRules_ActionValue] parameter is applicable only if the 'Rule Action' parameter is set to Alternative IP Profile. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 252 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 253: 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 254 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 255 QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 242. BW Profile Assigns a Bandwidth Profile to the Media Realm. For CLI: bw-profile configuring Bandwidth Profiles, see ''Configuring Bandwidth [CpMediaRealm_BWProfile] Profiles'' on page 246. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 256: Configuring Remote Media Subnets

    Mediant 800B Gateway and E-SBC 17.2 Configuring Remote Media Subnets Remote Media Subnets define destination subnets for media (RTP/SRTP) traffic on a specific Media Realm. Each Remote Media Subnet can be assigned different call quality (Quality of Experience Profile) and bandwidth utilization (Bandwidth Profile) profiles. These profiles are configured in ''Configuring Quality of Experience Profiles'' on page ''Configuring Bandwidth Profiles'' on page 246, respectively.
  • Page 257 [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 258: 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 259 WAN and the other on the LAN. The reason for this is that in Media Anchoring, the device does not interfere in the SIP signaling such as manipulation of IP Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 260: Configuring Sip Interfaces

    Mediant 800B Gateway and E-SBC Parameter Description addresses, which is necessary for calls between LAN and WAN.  When the global parameter SBCDirectMedia is disabled, Media Anchoring can only be enabled for calls between endpoints belonging to the same SRD.
  • Page 261 SIP Interfaces can share the same port - no port overlapping). TCP Port Defines the listening TCP port. CLI: tcp-port The valid range is 1 to 65534. The default is 5060. [SIPInterface_TCPPort] Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 262 Mediant 800B Gateway and E-SBC Parameter Description  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).

  • Page 263: 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 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 264 Mediant 800B Gateway and E-SBC PBX or ITSP) or it can be a group of users (e.g., LAN IP phones). For servers, the IP Group is typically used to define the server's IP address by associating it with a Proxy Set (see Configuring Proxy Sets on page 274).
  • Page 265 User-type IP Group. Each SIP request sent by a user of this IP Group is proxied to the Serving IP Group. For registrations, the device updates its internal database with the AOR and contacts of Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 266 Mediant 800B Gateway and E-SBC Parameter Description the users. Digest authentication using SIP 401/407 responses (if needed) is performed by the Serving IP Group. The device forwards these responses directly to the SIP users. To route a call to a registered user, a rule must be configured in the Outbound IP Routing table or SBC IP-to-IP Routing table.
  • Page 267 If this parameter is not configured (default), these headers are populated with the device's dotted-decimal IP address of the network interface on which the message is sent. Note: To ensure proper device handling, this parameter should be a valid FQDN. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 268 Mediant 800B Gateway and E-SBC Parameter Description QoE Profile Assigns a Quality of Experience Profile rule. For configuring Quality of CLI: qoe-profile Experience Profiles, see ''Configuring Quality of Experience Profiles'' [IPGroup_QOEProfile] on page 242. Bandwidth Profile Assigns a Bandwidth Profile rule. For configuring Bandwidth Profiles, CLI: bandwidth-profile see ''Configuring Bandwidth Profiles'' on page 246.
  • Page 269 User-type IP Group enters into Survivability mode in which the device uses its database for routing calls between the clients of the User-type IP Group. In Survivability mode, the RTP packets between the clients always traverse through the device, and new Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 270 Mediant 800B Gateway and E-SBC Parameter Description registrations can also be processed. When the Serving IP Group is available again, the device returns to normal mode, sending INVITE and REGISTER messages to the Serving IP Group.  [2] Always Enable = Survivability mode is always enabled. The communication with the Serving IP Group is always considered as failed.
  • Page 271 Note: This parameter is applicable only if the 'Authentication Mode' parameter is set to SBC as Server [2]. SBC Client Forking Mode Defines call forking of INVITE messages to up to five separate SIP Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 272 Mediant 800B Gateway and E-SBC Parameter Description CLI: enable-sbc-client- outgoing legs for User-type IP Groups. This occurs if multiple contacts forking are registered under the same AOR in the device's registration [IPGroup_EnableSBCClient database. Forking]  [0] Sequential = (Default) Sequentially sends the INVITE to each contact.
  • Page 273 'Authentication Mode' parameter is set to SBC as Server (i.e., authentication of servers).  To specify the SIP request types (e.g., INVITE) that must be challenged by the device, use the 'Authentication Method List' parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 274: Configuring Proxy Sets

    Mediant 800B Gateway and E-SBC 17.6 Configuring Proxy Sets The Proxy Sets table lets you configure up to 50 Proxy Sets. A Proxy Set defines the destination address (IP address or FQDN) and transport type (e.g., UDP) of a SIP server (e.g., Proxy).
  • Page 275 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. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 276 Mediant 800B Gateway and E-SBC Parameter Description Proxy Name Defines an arbitrary name to easily identify the Proxy Set. CLI: proxy-name The valid value is a string of up to 20 characters. [ProxySet_ProxyName] DNS Resolve Method Defines the DNS query record type for resolving the Proxy server's CLI: dns-resolve-method host name into an IP address.
  • Page 277 Proxy server to is-proxy-hot-swap redundant Proxies when no response is received from the primary. [ProxySet_IsProxyHotSwap]  [0] No (default)  [1] Yes = The device sends the SIP INVITE/REGISTER message Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 278 Mediant 800B Gateway and E-SBC Parameter Description to the first address (Proxy/Registrar server) listed in the Proxy Set. If a SIP response is received and this response code is defined in the 'Keep Alive Failure Response' parameter (above), the device assumes the Proxy as down and sends the message again;...
  • Page 279 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 91. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 280 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 281: 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 282 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 283 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 284: 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 285: Configuring Proxy And Registration Parameters

    For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 733. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Endpoint Registration Status on page 668. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 286 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 287: 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 288: 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 289 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 290 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 291 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. [MessageManipulations_Ma The valid value is a string of up to 16 characters. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 292 Mediant 800B Gateway and E-SBC Parameter Description 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 [MessageManipulations_Ma...
  • Page 293 This option allows you to configure multiple actions for the same condition. Note: When multiple manipulations rules apply to the same header, the next rule applies to the result string of the previous rule. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 294: Configuring Sip Message Policy Rules

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

  • Page 297: Coders And Profiles

    To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Configure coders according to the parameters described in the table below. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 298 Mediant 800B Gateway and E-SBC 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. CLI: name Note: Each coder type (e.g., G.729) can be configured only once [CodersGroup0_Name] in the table.
  • Page 299 Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 T.38 [t38fax] T.38 Version 3 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 300: Configuring Coder Groups

    Mediant 800B Gateway and E-SBC 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). Each Coder Group can include up to 10 coders.

  • Page 301: Configuring Tel Profile

    Trunk Group Table (see Configuring Trunk Group Table on page 351)). 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 302 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 303 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 304: 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 305 Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Configure an IP Profile according to the parameters described in the table below. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 306 Mediant 800B Gateway and E-SBC 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. [IpProfile_Index] Web: Profile Name Defines an arbitrary name to easily identify the IP Profile.
  • Page 307  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. To overcome this, set the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 308 Mediant 800B Gateway and E-SBC Parameter Description DisconnectOnBrokenConnection parameter to 0; the device doesn't detect RTP packets arriving from the original source IP address and switches (after 300 msec) to the RTP packets arriving from the new source IP address.
  • Page 309 CLI: jitter-buffer-max-delay Buffer. [IpProfile_JitterBufMaxDelay] The valid range is 150 to 2,000. The default is 250. Web: Coders Group ID Defines coders supported by this SIP entity, by assigning a Coders CLI: coders-group-id Group. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 310 Mediant 800B Gateway and E-SBC Parameter Description [IpProfile_CodersGroupID] The value, Default Coders Group represents the coders configured in the Coders table (see Configuring Coders on page 297). All other optional values (e.g., Coders Group 1), represent the coders defined for the specific Coder Group configured in the Coder Group Settings table (see Configuring Coder Groups on page 300).
  • Page 311 G.711 -Law). The parameters defining payload type for the 'old' Bypass mode FaxBypassPayloadType and ModemBypassPayloadType are not used with NSE Bypass. The bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval parameter. The SDP contains the following line: 'a=rtpmap:100 X-NSE/8000'. Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 312 Mediant 800B Gateway and E-SBC Parameter Description  When enabled, the following conditions must also be met:  The Cisco gateway must include the following definition: 'modem passthrough nse payload-type 100 codec g711alaw'.  Set the Modem transport type to Bypass mode (VxxModemTransportType is set to 2) for all modems.
  • Page 313 Setup message, for IP-to-Tel calls. Thus, even if there is no SIP number Diversion or History header in the incoming INVITE message, the [IpProfile_CopyDest2RedirectN outgoing Q.931 Setup message will contain a redirect number. umber]  [0] Disable (default). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 314 Mediant 800B Gateway and E-SBC Parameter Description  [1] After Manipulation = Copies the called number after manipulation. The device first performs IP-to-Tel destination phone number manipulation, and only then copies the manipulated called number to the redirect number sent in the Q.931 Setup message to the Tel.
  • Page 315 The corresponding global parameter is TxDTMFOption. Web: Second Tx DTMF Option Defines the second preferred transmit DTMF negotiation method. CLI: second-tx-dtmf-option For a description, see IpProfile_FirstTxDtmfOption (above). [IpProfile_SecondTxDtmfOption Note: The corresponding global parameter is TxDTMFOption Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 316 Mediant 800B Gateway and E-SBC Parameter Description Web: Rx DTMF Option Enables the device to declare the RFC 2833 'telephony-event' CLI: rx-dtmf-option parameter in the SDP. [IpProfile_RxDTMFOption]  [0] Not Supported  [3] Supported (default) The device is always receptive to RFC 2833 DTMF relay packets.
  • Page 317 IP Groups includes this coder. Note: To configure Coders Groups, see Configuring Coder Groups on page 300. Web: Transcoding Mode Defines the voice transcoding mode (media negotiation) for this Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 318 Mediant 800B Gateway and E-SBC Parameter Description CLI: transcoding-mode SIP entity. [IpProfile_TranscodingMode]  [0] Only if Required = (Default) Transcoding is done only when necessary. Many of the media settings (such as gain control) are not implemented on the voice stream. The device forwards RTP packets transparently (RTP-to-RTP), without processing them.
  • Page 319 [IpProfile_SBCAlternativeDTMF When RFC 2833 negotiation fails, the device uses this parameter Method] to define the DTMF method for the leg.  [0] As Is = (Default) The device does not attempt to interwork Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 320 Mediant 800B Gateway and E-SBC Parameter Description any special DTMF method.  [1] In Band  [2] INFO - Cisco  [3] INFO - Nortel  [4] INFO - Lucent = INFO, Korea Note: If the device interworks between different DTMF methods...
  • Page 321 PRACK process and forwards the request as is. Web: Session Expires Mode Defines the required session expires mode for this SIP entity. CLI: sbc-session-expires-mode  [0] Transparent = (Default) The device does not interfere with [IpProfile_SBCSessionExpiresM Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 322 Mediant 800B Gateway and E-SBC Parameter Description ode] the session expires negotiation.  [1] Observer = If the SIP Session-Expires header is present, the device does not interfere, but maintains an independent timer for each leg to monitor the session. If the session is not refreshed on time, the device disconnects the call.
  • Page 323 However, requests with the special prefix continue using the device's database to locate the new destination.  Only one database entry is supported for the same host, port, and transport combination. For example, the following URLs Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 324 Mediant 800B Gateway and E-SBC Parameter Description cannot be distinguished by the device:  sip:10.10.10.10:5060;transport=tcp;param=a  sip:10.10.10.10:5060;transport=tcp;param=b  The database entry expires two hours after the last use.  The maximum number of destinations (i.e., database entries) is  The corresponding global parameter is SBC3xxBehavior.
  • Page 325 [2] Send Only Zero ip = Device sends SDP with 'a=sendonly' and 'c=0.0.0.0'.  [3] Inactive = Device sends SDP with 'a=inactive'.  [4] Inactive Zero ip = Device sends SDP with 'a=inactive' and Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 326 Mediant 800B Gateway and E-SBC Parameter Description 'c=0.0.0.0'.  [5] Not Supported = Used when remote side cannot identify a call-hold message. The device terminates the received call-hold message (re-INVITE / UPDATE) and sends a 200 OK to the initiator of the call hold. The device plays a held tone to the held party if the 'SBC Play Held Tone' parameter is set to Yes.
  • Page 327 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 328 Mediant 800B Gateway and E-SBC Parameter Description Web: Jitter Compensation Enables the on-demand jitter buffer for SBC calls. This jitter buffer CLI: sbc-jitter-compensation can be used when other functionality such as voice transcoding are [IpProfile_SBCJitterCompensati not done on the call. This jitter buffer is useful when incoming packets are received at inconsistent intervals (i.e., packet delay...

  • Page 329: Gateway Application

    Part V Gateway Application...

  • Page 331: 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 332 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 333: 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 334 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 335: Tdm And Timing

    For a description of these parameters, see ''PSTN Parameters'' on page 880.  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 336: 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 584. 21.2.2 Clock Settings In a traditional TDM service network such as PSTN, both ends of the TDM connection must be synchronized.

  • Page 337: 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 581). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 338 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 339 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 340: 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 733.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 341: 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 342 Mediant 800B Gateway and E-SBC By utilizing the ‘Profiles’ mechanism (see ''Coders and Profiles'' on page 297), 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 343 [ 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 344: 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 345: 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 346: 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 347: 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 348: 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 349: Collecting Isdn Digits And Sending Complete Number In Sip

    Q.931 Information messages) to the IP side, using subsequent SIP INVITE messages. You can also define the minimum number of overlap digits to collect before sending the first SIP message (INVITE) for routing the call, using the MinOverlapDigitsForRouting parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC  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 all subsequent INVITEs received, the device sends a SIP 484 "Address Incomplete"...

  • Page 351: Trunk Group

    ''Configuring Hunt Group Settings'' on page 353).  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 352 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 353: 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 354 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 355 Group, according to the settings in the Account table (see ''Configuring Registration Accounts'' on page 281). 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 356 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 263).
  • Page 357 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 456. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 358 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 359: 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 360 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 361 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 362 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 363 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 364 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 365: 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 366: 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 367 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 731. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 368 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 369: 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 370 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 371 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 372 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 373: 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 374: 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 375: 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 376 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 377: 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 378: 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 379 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 380 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 381: 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 382: 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 383: 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 384 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 385 FQDN to resolve into two IP addresses. For more information on alternative routing, see ''Alternative Routing for Tel-to-IP Calls'' on page 398.  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 386 Mediant 800B Gateway and E-SBC with calculating the cost of using a service (Tel-to-IP call) and relaying that information to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule. Note: You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table.
  • Page 387 [1] Route calls after manipulation = Calls are routed after the number manipulation rules are applied. Notes:  This parameter is not applicable if outbound proxy routing is used.  For number manipulation, see ''Configuring Source/Destination Number Manipulation'' on page 359. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 388 Mediant 800B Gateway and E-SBC Parameter Description Route Name Defines an arbitrary name to easily identify the routing rule. CLI: route-name The valid value is a string of up to 20 characters. By default, no [PREFIX_RouteName] value is defined. Matching Call Characteristics Web: Src.

  • Page 389: Notations, See ''Dialing Plan Notation For Routing And Manipulation

    'Dest Phone Prefix' field, enter 00 and in the 'Dest IP Address' field, enter 0.0.0.0.  For routing calls between phones connected to the device (i.e., Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC Parameter Description local routing), enter the device's IP address.  When the device's IP address is unknown (e.g., when DHCP is used), enter IP address 127.0.0.1.  When using domain names, enter the DNS server's IP address or alternatively, configure these names in the Internal DNS table (see ''Configuring the Internal DNS Table'' on page 128).
  • Page 391 1 only and ignores the other index entries even if the destination is unavailable and alternative routing is enabled. This is because the subsequent index entries are defined with a Forking Group number that is Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 392: Configuring Inbound Ip Routing Table

    Mediant 800B Gateway and E-SBC Parameter Description lower than that of index entry 1.  Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with Forking Group "1": The device first sends the call according to index entries 1, 3, and 4 (all belonging to Forking Group "1"),...
  • Page 393 The following procedure describes how to configure Inbound IP Routing rules in the Web interface. You can also configure Inbound IP Routing rules using the table ini file parameter, PSTNPrefix or CLI command, configure voip > gw routing ip2tel-routing. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 394: Route Name

    Mediant 800B Gateway and E-SBC  To configure IP-to-Tel or inbound IP routing rules: Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing).

  • Page 395: Cli: Src-Host-Prefix

    Defines the SRD from where the incoming packet is received. CLI: src-srd-id Note: When the incoming INVITE matches the SRD in the [PstnPrefix_SrcSRDID] routing rule, if the 'Source IP Group ID' parameter (see below) Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 396: Ip Destinations Connectivity Feature

    Mediant 800B Gateway and E-SBC Parameter Description is defined and it is associated with a different SRD, the incoming SIP call is rejected. If the 'Source IP Group ID' parameter is not defined, the SRD's default IP Group is used. If there is no valid source IP Group, the call is rejected.
  • Page 397 IP Connectivity: This page displays a more informative connectivity status of the IP destinations used in Tel-to-IP routing rules in the Outbound IP Routing table. For viewing this page, see ''Viewing IP Connectivity'' on page 670. Version 6.8 Mediant 800B Gateway and E-SBC...

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

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

  • Page 399: Alternative Routing Based On Sip Responses

    Alternative Routing table and 3) configuring an alternative routing rule. Note: The device also plays a tone to the endpoint whenever an alternative route is used. This tone played for a user-defined time, configured by the AltRoutingToneDuration parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 400 Mediant 800B Gateway and E-SBC Depending on configuration, the alternative routing is done using one of the following configuration entities:  Outbound IP Routing Rules: You configure alternative routing rules for a specific routing rule in the Outbound IP Routing table. If the destination of the "main" routing rule is unavailable, the device searches the table for the next matching rule (e.g.,...

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

    The device tries each contact sequentially, listed in the Contact headers, until a successful destination is found. If a contact responds with a SIP 486 or 600, the device does not try to redirect the call to the next contact and drops the call. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 402: Pstn Fallback

    Mediant 800B Gateway and E-SBC  The device tries each contact sequentially, listed in the Contact headers. If a SIP 6xx Global Failure response is received during this process (e.g., 600 Busy Everywhere), the device does not try to redirect the call to the next contact and drops the call.

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

    The following procedure describes how to configure alternative routing reasons for IP-to- Tel calls in the Web interface. You can also configure alternative routing reasons for IP-to- Tel calls using the table ini file parameter, AltRouteCauseIP2Tel or CLI command, configure voip/gw routing alt-route-cause-ip2tel. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC  To configure alternative Trunk Group routing based on Q.931 cause codes: In the Proxy & Registration page, set the 'Redundant Routing Mode' parameter to Routing Table so that the device uses the Inbound IP Routing table for alternative routing.
  • Page 405 FQDN, or a SIP Request-URI user name and host part (i.e., user@host). The following syntax can also be used: host:port;transport=xxx (i.e., IP address, port and transport type). Note: When configured with a user@host, the original destination number is replaced by the user part. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 406: Alternative Routing Upon Isdn Disconnect

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

  • Page 407: 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 584. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 408: 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 348.
  • Page 409 (TimeBetweenDigits parameter), it sends the collected digits. Therefore, this ensures that calls are not rejected as a result of their digit pattern not been completed in the Dial Plan. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 410: External Dial Plan File

    Mediant 800B Gateway and E-SBC 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 600. User's Manual Document #: LTRT-10286...

  • Page 411: Configuring Supplementary Services

    ''Configuration Parameters Reference'' on page 733.  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 412: 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 584.
  • Page 413 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 414: 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 415: 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 416: 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 417: Call Forward

    The served party (FXS interface) can be configured through the Web interface (see Configuring Call Forward on page 465) 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 418: 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 419: 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 420: 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 421: Message Waiting Indication

    MWIServerIP, or MWISubscribeIPGroupID and ProxySet  MWIAnalogLamp  MWIDisplay  StutterToneDuration  EnableMWISubscription  MWIExpirationTime  SubscribeRetryTime  SubscriptionMode  CallerIDType (determines the standard for detection of MWI signals)  ETSIVMWITypeOneStandard  BellcoreVMWITypeOneStandard  VoiceMailInterface  EnableVMURI Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 422 Mediant 800B Gateway and E-SBC 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 423: 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 424: 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 425: 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 426: 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 427: 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 428 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 429: 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 430 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 431 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 432: 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 433 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 434: 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 435: 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 436 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 437 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 438 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 439: 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 440 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 441 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 442: Sip Invite Message

    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 443: 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 444 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 445 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616 22:11:45 0 4258359777 ------------ Current Time: 22:12:40  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 446: Multilevel Precedence And Preemption

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

  • Page 448: Mlpp Preemption Events In Sip Reason Header

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

  • Page 449: Precedence Ring Tone

    200 OK is received from the remote destination. When a 200 OK is received, a double answer is sent from the FXO line. • Ensure that the PSTN side is configured to identify this double-answer signal. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 26.14 Configuring Multi-Line Extensions and Supplementary Services The Supplementary Services table lets you configure up to 100 supplementary services for endpoints connected to the device. These endpoints include analog FXS phones and Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) phones. This table lets you configure multiple phone line extension numbers per FXS/BRI port.
  • Page 451 Defines the port number on the module to which the endpoint is CLI: port connected. [ISDNSuppServ_Port] User ID Defines the User ID for registering the endpoint to a third-party CLI: user-id softswitch for authentication and/or billing. [ISDNSuppServ_UserId] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 452: Detecting Collect Calls

    The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call), using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
  • Page 453 User's Manual 26. Configuring Supplementary Services  Tel-to-IP direction: The device converts the AOC messages received in the EURO ISDN Facility IE messages into SIP INFO and BYE messages using AudioCodes proprietary SIP AOC header.  IP-to-Tel direction provides optional methods: •...

  • Page 454: Configuring Charge Codes

    Mediant 800B Gateway and E-SBC 26.17 Configuring Charge Codes The Charge Codes table lets you configure metering tones that the device generates to the Tel side on its FXS interfaces, and for Advice of Charge (AOC) services for Euro ISDN trunks (see Advice of Charge Services for Euro ISDN on page 452).
  • Page 455 (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 456: 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 733. Notes: • The Voice Mail Settings page is available only for FXO and CAS interfaces.

  • Page 457: 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 932. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 458 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 459: Configuring Metering Tones

    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 733. Note: The FXO Settings page is available only for FXO interfaces. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 460: 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 461 (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 462: 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 463: 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 464 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 465: 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 466: 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 467: 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 468: 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 469: 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 470: 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 471: Fxo Operating Modes

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

  • Page 472: 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 473: 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 474: 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 475: 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 476: Call Termination On Fxo Devices

    Mediant 800B Gateway and E-SBC 27.13.3 Call Termination on FXO Devices This section describes the device's call termination capabilities for its FXO interfaces:  Calls terminated by a PBX (see ''Call Termination by PBX'' on page 476)  Calls terminated before call establishment (see ''Call Termination before Call Establishment'' on page 477) ...

  • Page 477: 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 478: 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 479: Message Waiting Indication For Remote Extensions

    Upon detection of an MWI message, the FXO device sends a SIP NOTIFY message to the IP side. When receiving this NOTIFY message, the remote FXS device generates an MWI signal toward its Tel side. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 480: Call Waiting For Remote Extensions

    Mediant 800B Gateway and E-SBC 27.14.4 Call Waiting for Remote Extensions When the FXO device detects a Call Waiting indication (FSK data of the Caller Id - CallerIDType2) from the PBX, it sends a proprietary INFO message, which includes the caller identification to the FXS device.

  • Page 481: 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 459), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 482 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 483: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 485: 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 486: 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 487 ''SBC Manipulations'' on page 543. 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 288. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 488: 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 489: 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 490: 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 491: 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 492: 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 493: 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 494 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 495: 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 496: 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 497: 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 498 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 499: 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 500: 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 501: Limiting Sbc Call Duration

    The device challenges the received SIP message only if it is configured as a SIP method (e.g., INVITE) for authorization. This is configured in the IP Group table, using the 'Authentication Method List' parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 502: User Authentication Based On Radius

    Mediant 800B Gateway and E-SBC If the message is received without a SIP Authorization header, the device "challenges" the client by sending a SIP 401 or 407 response. The client then resends the request with an Authorization header (containing the user name and password).

  • Page 503: Interworking Sip 3Xx Redirect Responses

    The prefix ("T~&R_") remains in the user part for the classification, manipulation, and routing mechanisms. The classification, manipulation, and routing processes are done exactly like any other INVITE handling. The special prefix can be used for specific routing rules for 3xx resultant INVITEs. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 504: Local Handling Of Sip 3Xx

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

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

    REFER standard while others may not even support REFER. This feature supports the following:  Attended, unattended, and semi-attended call transfers  Sending INVITE, REFER-notifications, BYE, PRACK and Session Timer on behalf of Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 506: Interworking Sip Prack Messages

    Mediant 800B Gateway and E-SBC peer PBXs  Advanced routing rules for the new, initiated INVITE  Forwarding early media after REFER while attempting to avoid transcoding (by sending session update)  Interoperate with environments were different SIP UAs lack basic SIP functionality such as re-INVITE, UPDATE, PRACK, Delayed Offer, re-INVITE without SDP ...
  • Page 507 Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: 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 508: Interworking Sip Re-Invite Messages

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

  • Page 509: Interworking Delayed Offer

    Interworking generation of held tone where the device generates the tone to the held party instead of the call hold initiator. This is configured by the IP Profile parameter, 'SBC Reliable Held Tone Source'. For configuring IP Profiles, see ''Configuring IP Profiles'' on page 304. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 510: Call Survivability

    Mediant 800B Gateway and E-SBC 28.9 Call Survivability This section describes various call survivability features supported by the SBC device. 28.9.1 Auto-Provisioning of Subscriber-Specific Information for BroadWorks Server for Survivability This feature enables SBC user registration for interoperability with BroadSoft BroadWorks server to provide call survivability in case of connectivity failure with the BroadWorks server, for example, due to a WAN failure.

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

    In the IP Group table, add a User-type IP Group for the IP phone users and set the 'SBC Client Forking Mode' parameter to Parallel so that the device forks incoming calls to all contacts under the same AOR registered in the device's registration database. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 512: Call Survivability For Call Centers

    Mediant 800B Gateway and E-SBC In the IP-to-IP Routing table (see ''Configuring SBC IP-to-IP Routing Rules'' on page 532), add a rule for routing calls between the above configured IP Groups. In the IP to IP Inbound Manipulation table (see ''Configuring IP-to-IP Inbound Manipulations'' on page 545), add a manipulation rule for the secondary extensions (e.g., 601 and 602) so that they also register to the device's database under the...
  • Page 513 The 'Destination Type' field is set to Hunt Group, which is specifically used for call center survivability. ♦ The 'Destination IP Group ID' field is set to the IP Group of the call center agents. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 514 Mediant 800B Gateway and E-SBC 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 User's Manual...

  • Page 515: Survivability Mode Display On Aastra Ip Phones

    (user), belonging to the destination IP Group User-type, registered in the database to all other users located under the same AOR as the specific contact. This is configured using the SBCSendInviteToAllContacts parameter. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 516: Sip Forking Initiated By Sip Proxy Server

    Mediant 800B Gateway and E-SBC 28.10.2 SIP Forking Initiated by SIP Proxy Server The device can handle SIP forking responses received from a proxy server in response to an INVITE forwarded by the device from a UA. In other words, received responses with a different SIP To header 'tag' parameter for the request forwarded by the device.

  • Page 517: 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 518 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 519: 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 520 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 521 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 522: 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 523 Click Submit, and then reset the device with a save ("burn") to flash memory. Table 29-2: Allowed Audio Coders Group Table Parameter Descriptions Parameter Description Allowed Coders Group ID Defines an index number for the new table record. [AllowedCodersGroupX] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 524: Configuring Allowed Video Coder Groups

    Mediant 800B Gateway and E-SBC Parameter Description Coder Name Defines the audio coder. This can be a pre-defined coder or a CLI: name user-defined coder. The valid value for user-defined coders is a [AllowedCodersGroupX_Name] string of up to 25 characters (case-insensitive). For example, "HD.123"...

  • Page 525: Configuring Classification Rules

    IP Group. In addition, if the Classification rule is defined as a whitelist, the SIP dialog is allowed and proceeds with the manipulation, routing and other SBC processes. If the Classification rule is defined as a blacklist, the SIP dialog is denied. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 526 Mediant 800B Gateway and E-SBC If the classification process fails, the device rejects or allows the call, depending on the setting of the 'Unclassified Calls' parameter (on the General Settings page - Configuration tab > VoIP menu > SBC > General Settings). If this parameter is set to Allow, the incoming SIP dialog is assigned to an IP Group as follows: The device checks on which SIP listening port (e.g., 5061) the incoming SIP dialog...
  • Page 527 The following procedure describes how to configure Classification rules in the Web interface. You can also configure Classification rules using the table ini file parameter, Classification or CLI command, configure voip > sbc routing classification. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 528 Mediant 800B Gateway and E-SBC  To configure a Classification rule: Open the Classification Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Click Add; the following dialog box appears: Figure 29-6: Classification Table Page Configure the Classification rule according to the parameters described in the table below.
  • Page 529 The default is the asterisk (*) symbol, which represents any destination username. 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 731. Version 6.8 Mediant 800B Gateway and E-SBC...

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

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

  • Page 531: Configuring Message Condition Rules

    The following procedure describes how to configure Message Condition rules in the Web interface. You can also configure Message Condition rules using the table ini file parameter, ConditionTable or CLI command, configure voip > sbc routing condition-table. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC  To configure a Message Condition rule: Open the Message Condition Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Message Condition Table). Click Add; the following dialog box appears: Figure 29-7: Condition Table Page - Add Record Dialog Box Configure a Message Condition rule according to the parameters described in the table below.
  • Page 533 Request-URI user part (by default, "acgateway- <prefix destination>", for example, acgateway-200). The device removes this prefix before sending it to the Tel side. To configure this prefix string, use the GWDirectRoutePrefix ini file parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 534 Mediant 800B Gateway and E-SBC The IP-to-IP Routing table also provides the following features:  Alternative routing or load balancing: In addition to the alternative routing/load balancing provided by the Proxy Set associated with the destination IP Group, the table allows the configuration of alternative routes whereby if a route fails, the next adjacent (below) rule in the table that is configured as 'Alt Route Ignore/Consider Inputs' are used.
  • Page 535 Routing SBC > IP-to-IP Routing Table). Click Add; the following dialog box appears: Figure 29-9: IP-to-IP Routing Table - Add Record Dialog Box Configure an IP-to-IP routing rule according to the parameters described in the table below. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 536 Mediant 800B Gateway and E-SBC Click Submit, and then save ("burn") your settings to flash memory. Table 29-6: IP-to-IP Routing Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [IP2IPRouting_Index] Route Name Defines an arbitrary name to easily identify the IP-to-IP CLI: route-name routing rule.
  • Page 537 Request-URI. If the fields 'Destination Port' and 'Destination Transport Type' are configured, the incoming Request-URI parameters are overridden and these fields take precedence.  [3] ENUM = An ENUM query is sent to include the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 538 Mediant 800B Gateway and E-SBC Parameter Description destination address. If the fields 'Destination Port' and 'Destination Transport Type' are configured, the incoming Request-URI parameters are overridden and these fields take precedence.  [4] Hunt Group = Used for call center survivability. For more information, see ''Call Survivability for Call Centers'' on page 512.
  • Page 539 [IP2IPRouting_DestTransportType]  [-1] Not Configured (default) CLI: dst-transport-type  [0] UDP  [1] TCP  [2] TLS Note: If this parameter is not configured, the transport type is determined by the SIPTransportType parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 540 Mediant 800B Gateway and E-SBC Parameter Description Alternative Route Options Determines whether this routing rule is the main routing rule [IP2IPRouting_AltRouteOptions] or an alternative routing rule (to the rule defined directly CLI: alt-route-options above it in the table).  [0] Route Row (default) = Main routing rule - the device first attempts to route the call to this route if the incoming SIP dialog's input characteristics matches this rule.

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

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

  • Page 543: Sbc Manipulations

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

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

    The following procedure describes how to configure IP-to-IP Inbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPInboundManipulation or CLI command, configure voip > sbc manipulations ip-inbound- manipulation. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 546 Mediant 800B Gateway and E-SBC  To configure an IP-to-IP Inbound Manipulation rule: Open the IP to IP Inbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Inbound). Click Add; the following dialog box appears:...
  • Page 547 [IPInboundManipulation_Manipula  [0] Source = (Default) Manipulation is done on the source tedURI] SIP URI user part.  [1] Destination = Manipulation is done on the destination SIP URI user part. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC Parameter Description Operation Rule - Action Remove From Left Defines the number of digits to remove from the left of the user CLI: remove-from-left name prefix. For example, if you enter 3 and the user name is [IPInboundManipulation_Remove "john", the new user name is "n".
  • Page 549 Determines whether additional manipulation is done for CLI: is-additional-manipulation the table entry rule listed directly above it. [IPOutboundManipulation_IsAdditional  [0] No = (Default) Regular manipulation rule - not Manipulation] done in addition to the rule above it. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 550 Mediant 800B Gateway and E-SBC Parameter Description  [1] Yes = If the previous table row entry rule matched the call, consider this row entry as a match as well and perform the manipulation specified by this rule. Note: Additional manipulation can only be done on a...
  • Page 551 Defines the number of digits to remove from the right of CLI: remove-from-right the manipulated item prefix. For example, if you enter 3 [IPOutboundManipulation_RemoveFro and the user name is "john", the new user name is "j". mRight] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 552 Mediant 800B Gateway and E-SBC Parameter Description Leave From Right Defines the number of digits to keep from the right of the CLI: leave-from-right manipulated item. [IPOutboundManipulation_LeaveFrom Right] Prefix to Add Defines the number or string to add in the front of the CLI: prefix-to-add manipulated item.

  • Page 553: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 555: 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 556 Mediant 800B Gateway and E-SBC Survivability Quality of Experience/Service Security registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...

  • Page 557: 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 558: 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 559: 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 263. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 560: 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 558.

  • Page 561: 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 562). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 562: 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 563: High-Availability System

    Part VIII High-Availability System...

  • Page 565: Ha Overview

    Device Switchover upon Failure on page 566. • 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 566: 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 567: 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 568 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 569: 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 570: 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 571: Step 1: Configure The First Device

    Ethernet Device "vlan 2" (which is associated with Ethernet Port Group "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 Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 572 Mediant 800B Gateway and E-SBC If the connection is through a switch, the packets of both interfaces should generally be untagged. In such a scenario, set the Native VLAN ID of each Ethernet Port Group so that it is the same as the VLAN ID set for each interface assigned to that Ethernet Port Group.

  • Page 573: Step 2: Configure The Second Device

    (configured in Step 1: Configure the First Device on page 571). 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 574: 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 575: Configuration While Ha Is Operational

    After it synchronizes with the active device, it initiates a switchover and becomes the new active device (the former active device resets and becomes the new redundant device). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 576: Configuring Firewall Allowed Rules

    Mediant 800B Gateway and E-SBC 33.3 Configuring Firewall Allowed Rules If you add firewall rules in the Firewall Settings page (see ''Configuring Firewall Settings'' on page 143) that block specified traffic, you also need to add rules that ensure traffic related to the HA feature is allowed.

  • Page 577: 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 618. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 578 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 579: Maintenance

    Part IX Maintenance...

  • Page 581: Basic Maintenance

    Description'' on page 42) 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 43). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 582: 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 581). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...

  • Page 583: 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 584: Saving Configuration

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

  • Page 585: High Availability Maintenance

    Open the High Availability Maintenance page (Maintenance tab > Maintenance menu > High Availability Maintenance). Figure 36-1: High Availability Maintenance Page Under the 'Switch Over' group, click Switch Over; a confirmation box appears requesting you to confirm. Click OK. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 586 Mediant 800B Gateway and E-SBC  To reset the Redundant device: Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK. User's Manual Document #: LTRT-10286...

  • Page 587: 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 588 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 589: 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 590 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 591: Disabling Analog Ports

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

  • Page 593: 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 594 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 595: 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 596 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 597: 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 598 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 599: 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 600: 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 593.
  • Page 601 • 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 602 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 593.

  • Page 603: 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 604 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 605 [ 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 606: 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 607: 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 608: 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 609 Authentication table (see Configuring Authentication per Port on page 460). 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 610 Mediant 800B Gateway and E-SBC 40.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 611 (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 612: User Information File For Sbc User Database

    Mediant 800B Gateway and E-SBC 40.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 613 Register. To un-register a user, select the user, and then from the Action button's drop-down list, choose Un-Register. Table 40-3: SBC User Info Table Parameter Descriptions Parameter Description Index Defines an index for the new table record. [SBCUserInfoTable_Index] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 614 Mediant 800B Gateway and E-SBC Parameter Description 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. Username Defines the username for registering the user when [SBCUserInfoTable_Username] authentication is necessary.
  • Page 615 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 616: 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 617: 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 618: 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 619: Software Upgrade Wizard

    If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
  • Page 620 Mediant 800B Gateway and E-SBC The following procedure describes how to load files using the Web interface's Software Upgrade Wizard. Alternatively, you can load files using the CLI:  cmp file: copy firmware from <URL>  ini or auxiliary file: copy <ini file or auxiliary file>...
  • Page 621 See the description of these methods in the beginning of this section. Note: If you select the Hitless Upgrade option, the wizard can only be used to upload a .cmp file; Auxiliary and ini files cannot be uploaded. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 622 Mediant 800B Gateway and E-SBC If you want to load additional files, skip this step and continue with the next step. If you only want to load a .cmp file, click Reset ; the device burns the .cmp file to its flash memory and then resets.
  • Page 623 Enter your login username and password, and then click Login; a message box appears informing you of the new .cmp file version. Click OK; the Web interface becomes active, reflecting the upgraded device. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 624: Backing Up And Loading Configuration File

    Mediant 800B Gateway and E-SBC 40.4 Backing Up and Loading Configuration File You can save a copy/backup of the device's current configuration settings as an ini file to a folder on your computer, using the Configuration File page. The saved file includes only parameters that were modified and parameters with other than default values.
  • Page 625 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 626 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 627: Automatic Update Mechanism

    To activate the DHCP process, perform a cold reset by pressing the device's hardware reset button. A soft reset using the Web interface doesn't trigger the DHCP process and if done, this parameter reverts to Disable. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 628: Provisioning From Http Server Using Dhcp Option 67

    Mediant 800B Gateway and E-SBC The following shows an example of a configuration file for a Linux DHCP server (dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server"...

  • Page 629: Provisioning From Tftp Server Using Dhcp Option 66

    HTTP server for file updates. HTTP(S) is not sensitive to NAT devices, enabling configuration whenever needed without on-site intervention. For additional security, the URL may contain a different port, and username and password. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 630: Ftp- Or Nfs-Based Provisioning

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

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

    The Automatic Update feature is done per file and configured by specifying the file name and URL address of the provisioning server where the file is located. For a description of the parameters used to configure URLs per file, see Automatic Update Parameters. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 632: Triggers For Automatic Update

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

  • Page 633: Access Authentication With Http Server

    <MAC> - device's MAC address • <VER> - software version currently installed on the device, e.g., "6.80.200.001" • <CONF> - configuration version, as configured in the ini file parameter, INIFileVersion or CLI command, configuration-version Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 634 Mediant 800B Gateway and E-SBC The device automatically populates these tag variables with actual values in the sent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<MAC>;<VER>;<CONF>). For example, if you set AupdHttpUserAgent = <NAME>;<VER>, the device sends the following User-Agent header: Mozilla/4.0 (compatible; AudioCodes; Mediant; 6.80.200.001)

  • Page 635: File Download Sequence

    If you use the ResetNow parameter in an ini file for periodic automatic provisioning with non-HTTP (e.g., TFTP) and without CRC, the device resets after every file download. Therefore, use this parameter with caution and only if necessary for your deployment requirements. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 636: Cyclic Redundancy Check On Downloaded Configuration Files

    Mediant 800B Gateway and E-SBC Notes: • For ini file downloads, by default, parameters not included in the file are set to defaults. To retain the current settings of these parameters, set the SetDefaultOnINIFileProcess parameter to 0. • If you have configured one-time software file (.cmp) download (configured by the ini file parameter CmpFileURL or CLI command configure system >...

  • Page 637: Automatic Update Configuration Examples

    Automatic Update is done every 24 hours (1440 minutes): ♦ ini File: AutoUpdateFrequency = 1440 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 1440 Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' ♦ CLI: Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC # configure system (config-system)# automatic update automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' Automatic Update of Call Progress Tone file: ♦ ini File: CptFileURL = 'https://www.company.com/call_progress.dat' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# call-progress-tones 'http://www.company.com/call_progress.dat' Automatic Update of ini configuration file: ♦...

  • Page 639: Automatic Update For Mass Deployment

    Device queries the provisioning server daily at 24:00 (midnight) for software, configuration and auxiliary files.  HTTP-based provisioning server at www.company.com for storing the files.  DNS server at 80.179.52.100 for resolving the domain name of the provisioning server. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 640 Mediant 800B Gateway and E-SBC  To set up automatic provisioning for mass provisioning (example): Create an ini file named "master_configuration.ini" with the following settings: Common configuration for all devices: # Check for updates daily at 24:00 AutoUpdatePredefinedTime = '24:00' # CPT file update: CptFileURL = 'https://www.company.com/call_progress.dat'...

  • Page 641: 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 642: Restoring Defaults Using Hardware Reset Button

    Mediant 800B Gateway and E-SBC 42.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 643: Automatic Archiving Of Configuration File

    To configure configuration-file archiving, use the following CLI command (root level):  Archiving to a remote server: # write-and-backup to <URL path with file name>  Archiving to a USB: # write-and-backup to usb:///<file name> Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 644 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 645: 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 646 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 647: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 649: System Status

    To delete a loaded file:  Click the Delete button corresponding to the file that you want to delete. Deleting a file takes effect only after device reset (see ''Resetting the Device'' on page 581). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 650: Viewing Ethernet Port Information

    Mediant 800B Gateway and E-SBC 45.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information about the Ethernet Port Group connections.  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu >...

  • Page 651: 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 652: Viewing Alarm History

    Mediant 800B Gateway and E-SBC 46.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 653: 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 654: Viewing Trunk Utilization

    Mediant 800B Gateway and E-SBC 47.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 655: 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 656 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 47-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 657: 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 658 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 659: Voip Status

    Disabled Gray 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 660: 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 48-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 661: Viewing Nfas Groups And D-Channel Status

    For more information, see ''Performing Manual D-Channel Switchover in NFAS Group'' on page 348. Note: This page is applicable only to T1 ISDN protocols supporting NFAS, and only if the NFAS group is configured with two D-channels. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 662: Viewing Active Ip Interfaces

    Mediant 800B Gateway and E-SBC  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 48-4: NFAS Group & D-Channel Status Page 48.4...

  • Page 663: Viewing Static Routes Status

    Viewing Performance Statistics The Basic Statistics page provides read-only, device performance statistics. This page is refreshed every 60 seconds. The duration that the currently displayed statistics has been collected is displayed above the statistics table. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 664: Viewing Cdr History

    Mediant 800B Gateway and E-SBC  To view performance statistics:  Open the Basic Statistics page (Status & Diagnostics tab > VoIP Status menu > Performance Statistics). Figure 48-6: Basic Statistics Page The duration that the displayed statistics were collected is displayed in seconds above the table.

  • Page 665: Viewing Call Counters

    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 666 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 667: 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 668: 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 669: 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 383)  SBC calls: SBC IP-to-IP Routing table (Configuring SBC IP-to-IP Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 670: Viewing Ip Connectivity

    Mediant 800B Gateway and E-SBC Parameter Description Routing Rules on page 532)  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 671  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 672 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 673: 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 674 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 Gap Loss Burst Loss Density Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold...
  • Page 675 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 49-1: RTCP XR Parameters in RTP/RTCP Settings Page Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 676: 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 677: Cdr Field Description

    Call duration (Durat CDR field) - call duration (elapsed time) from call connect  Call time is based on SetupTime, ConnectTime and ReleaseTime CDR fields Table 49-2: CDR Fields for SBC Signaling CDR Field Name Description Format Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 678 Mediant 800B Gateway and E-SBC CDR Field Name Description Format SBCReportType Report Type: String  "CALL_START"  "CALL_CONNECT"  "CALL_END"  "DIALOG_START"  "DIALOG_END" EPTyp Endpoint type: String  "SBC" SIPMethod SIP message type String of up to 10 characters...
  • Page 679  "no" SIPTrmReason SIP call termination reason (BYE, String of up to 12 characters. CANCEL, or SIP error codes, e.g., 404) SipTermDesc Description of SIP termination reason: String of up to 26 characters Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 680: Cdr Fields For Sbc Media

    Mediant 800B Gateway and E-SBC CDR Field Name Description Format  SIP Reason header, if exists, for example: SIP ;cause=200 ;text="Call completed elsewhere".  If no SIP Reason header exists, the description is taken from the reason text, if exists, of the SIP response code, for example: "417 Unknown...

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

    The CDR fields for the Gateway / IP-to-IP application are listed in the table below. Table 49-4: CDR Fields for Gateway/IP-to-IP Application Field Name Description GWReportType Report type:  CALL_START  CALL_CONNECT  CALL_END Port number Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 682 Mediant 800B Gateway and E-SBC Field Name Description SessionId SIP session identifier Trunk Physical trunk number Note: This field is applicable only to the Gateway application. BChan Selected B-channel Note: This field is applicable only to the Gateway application. ConId SIP conference ID Note: This field is applicable only to the Gateway application.
  • Page 683 Note: This field is applicable only to the Gateway application. SrcHost Source host name SrcHostBeforeMap Source host name before manipulation DstHost Destination host name DstHostBeforeMap Destination host name before manipulation IP Group description LocalRtpIp Remote RTP IP address LocalRtpPort Local RTP port Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 684 Mediant 800B Gateway and E-SBC Field Name Description Amount 0-999999 Data is stored per call and sent in the syslog as follows:  currency-type: amount multiplier for currency charge (euro or usd)  recorded-units: for unit charge (1-999999) Mult 0,001-1000 (in steps of 10) (See explanation above.)

  • Page 685: Release Reasons In Cdr

    "RELEASE_BECAUSE_NOANSWER"  "RELEASE_BECAUSE_UNKNOWN_REASON"  "RELEASE_BECAUSE_REMOTE_CANCEL_CALL"  "RELEASE_BECAUSE_UNMATCHED_CAPABILITIES"  "RELEASE_BECAUSE_UNMATCHED_CREDENTIALS"  "RELEASE_BECAUSE_UNABLE_TO_HANDLE_REMOTE_REQUEST"  "RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT"  "RELEASE_BECAUSE_CONFERENCE_FULL"  "RELEASE_BECAUSE_VOICE_PROMPT_PLAY_ENDED"  "RELEASE_BECAUSE_VOICE_PROMPT_NOT_FOUND"  "RELEASE_BECAUSE_TRUNK_DISCONNECTED"  "RELEASE_BECAUSE_RSRC_PROBLEM"  "RELEASE_BECAUSE_MANUAL_DISC"  "RELEASE_BECAUSE_SILENCE_DISC"  "RELEASE_BECAUSE_RTP_CONN_BROKEN"  "RELEASE_BECAUSE_DISCONNECT_CODE"  "RELEASE_BECAUSE_GW_LOCKED" Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 686 Mediant 800B Gateway and E-SBC  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS"  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"...

  • Page 687: Configuring Radius Accounting

    Accounting server. The device can send the accounting messages to the RADIUS server upon call release, call connection and release, or call setup and release. For a list of the CDR attributes, see the table following the procedure below. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 688 Mediant 800B Gateway and E-SBC  To configure RADIUS accounting: Open the RADIUS Parameters page (Configuration tab > VoIP menu > SIP Definitions > RADIUS Parameters Settings). Figure 49-3: RADIUS Accounting Parameters Page Set the 'Enable RADIUS Access Control' parameter to Enable.
  • Page 689 Number of octets sent Numeric - Stop Acc octets for that call duration (Gateway call) acct-session- A unique accounting String 34832 Start Acc identifier - match start Stop Acc & stop Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 690 Mediant 800B Gateway and E-SBC Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. acct-session- For how many Numeric - Stop Acc time seconds the user received the service acct-input- Number of packets Numeric - Stop Acc...

  • Page 691: Event Notification Using X-Detect Header

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

  • Page 694: Querying Device Channel Resources Using Sip Options

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

  • Page 695: Diagnostics

    Part XI Diagnostics...

  • Page 697: 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 698: 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 699 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 700: Identifying Audiocodes Syslog Messages Using Facility Levels

    Mediant 800B Gateway and E-SBC 50.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 701: Snmp Alarms In Syslog Messages

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

  • Page 702: 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 50-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 703: 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 760. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 704: Filtering Syslog Messages And Debug Recordings

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

  • Page 706: Filtering Ip Network Traces

    Mediant 800B Gateway and E-SBC Parameter Description  [2] Signaling & Media = Signaling and media (RTP/RTCP/T.38).  [3] Signaling & Media & PCM = Signaling, media, and PCM (voice signals from and to TDM).  [4] PSTN trace = ISDN and CAS traces - applicable only for Trunk-related filters.

  • Page 707: Viewing Syslog Messages

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

  • Page 708: Collecting Debug Recording Messages

    Mediant 800B Gateway and E-SBC 50.7 Collecting Debug Recording Messages To collect debug recording packets, use the open source program Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...
  • Page 709 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 710: Debug Capturing On Physical Voip Interfaces

    Mediant 800B Gateway and E-SBC 50.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 711: 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 712 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

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

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

  • Page 715: Analog Line Testing

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

  • Page 716: Fxs Line Testing

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

  • Page 717: 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 718 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 54-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
  • Page 719 '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 720 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 721: 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 722). Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 722: Viewing Test Call Statistics

    Mediant 800B Gateway and E-SBC 54.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 721), you can also view a more detailed status description which includes test call statistics.

  • Page 723: Configuring Dtmf Tones For Test Calls

    Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 54-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 724: Configuring Basic Test Call

    Mediant 800B Gateway and E-SBC 54.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 725: Configuring Sbc Test Call With External Proxy

    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 726: 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 759): Open the Test Call Settings page (Configuration tab > System menu > Test Call >...
  • Page 727 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 728 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 729: Appendix

    Part XII Appendix...

  • Page 731: Dialing Plan Notation For Routing And Manipulation

    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.  03(abc): for any number that starts with 03 and ends with abc. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 732 Mediant 800B Gateway and E-SBC Notation Description  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.

  • Page 733: 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 734: 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 735 '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 736 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 737: Telnet Parameters

    Table 56-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 738: Snmp Parameters

    The valid range is a string of up to 64 characters. [SendKeepAliveTrap] Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 739 Determines the validity of the parameters (IP address and port [SNMPManagerIsUsed_x] number) of the corresponding SNMP Manager used to receive SNMP traps.  [0] (Check box cleared) = Disabled (default)  [1] (Check box selected) = Enabled Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 740 Mediant 800B Gateway and E-SBC Parameter Description Web: IP Address Defines the IP address of the remote host used as an SNMP EMS: Address Manager. The device sends SNMP traps to this IP address. CLI: ip-address Enter the IP address in dotted-decimal notation, e.g., [SNMPManagerTableIP_x] 108.10.1.255.

  • Page 741: Serial Parameters

    Note: For this parameter to take effect, a device reset is required. EMS: Parity Defines the RS-232 polarity. [SerialParity]  [0] = (Default) None  [1] = Odd  [2] = Even Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 742 Mediant 800B Gateway and E-SBC Parameter Description EMS: Stop Defines the RS-232 stop bit. [SerialStop]  [1] = (Default) 1-bit (default)  [2] = 2-bit Note: For this parameter to take effect, a device reset is required. EMS: Flow Control Defines the RS-232 flow control.

  • Page 743: 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 744: Automatic Update Parameters

    Mediant 800B Gateway and E-SBC 56.1.8 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Table 56-8: Automatic Update of Software and Configuration Files Parameters Parameter Description General Automatic Update Parameters CLI: configure Enables the Automatic Update mechanism for the cmp file.
  • Page 745 A higher value does not necessarily mean better performance.  The block size should be small enough to avoid IP fragmentation in the client network (i.e., below MTU).  This feature is applicable only to TFTP servers that support this option. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 746 Mediant 800B Gateway and E-SBC Parameter Description [ResetNow] Invokes an immediate device reset. This option can be used to activate offline (i.e., not on-the-fly) parameters that are loaded using the parameter IniFileUrl.  [0] = (Default) The immediate restart mechanism is disabled.

  • Page 747: Networking Parameters

    Defines the transmit (Tx) and receive (Rx) settings for the Ethernet port Settings groups. The format of this parameter is as follows: CLI: configure voip/ether- [EtherGroupTable] group FORMAT EtherGroupTable_Index = EtherGroupTable_Group, [EtherGroupTable] EtherGroupTable_Mode, EtherGroupTable_Member1, EtherGroupTable_Member2; Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 748 Mediant 800B Gateway and E-SBC Parameter Description [\EtherGroupTable] For a description of this parameter, see Configuring Ethernet Port Groups on page 111. Note: For this parameter to take effect, a device reset is required. User's Manual Document #: LTRT-10286...

  • Page 749: Multiple Voip Network Interfaces And Vlan Parameters

    Defines up to 30 static IP routes for the device. Table The format of the ini file table parameter is as follows: CLI: configure voip > static [ StaticRouteTable ] [StaticRouteTable] FORMAT StaticRouteTable_Index = StaticRouteTable_DeviceName, StaticRouteTable_Destination, StaticRouteTable_PrefixLength, StaticRouteTable_Gateway, StaticRouteTable_Description; Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 750: Open Solution Network (Osn) Parameters

    Mediant 800B Gateway and E-SBC Parameter Description [ \StaticRouteTable ] For a description of this parameter, see ''Configuring Static IP Routes'' on page 122. 56.2.4 Open Solution Network (OSN) Parameters The OSN server parameters are described in the table below.

  • Page 751: Nat Parameters

    UA, does it determine whether the UA is behind NAT.  [1] NAT Is Not Used = (Default) NAT feature is disabled. The device always sends the media packets to the remote UA using Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 752: Nfs Parameters

    1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.

  • Page 753: Dns Parameters

    SRV2IP_Weight1, SRV2IP_Port1, SRV2IP_Dns2, SRV2IP_Priority2, SRV2IP_Weight2, SRV2IP_Port2, SRV2IP_Dns3, SRV2IP_Priority3, SRV2IP_Weight3, SRV2IP_Port3; [\SRV2IP] For example: SRV2IP 0 = SrvDomain,0,Dnsname1,1,1,500,Dnsname2,2,2,501,$$,0,0,0; For a detailed description of this table, see ''Configuring the Internal SRV Table'' on page 130. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 754: Dhcp Parameters

    Mediant 800B Gateway and E-SBC 56.2.9 DHCP Parameters The Dynamic Host Control Protocol (DHCP) parameters are described in the table below. Table 56-17: DHCP Parameters Parameter Description Web: Enable DHCP Enables DHCP client EMS: DHCP Enable functionality. [DHCPEnable]  [0] Disable (default) ...
  • Page 755 [ DhcpOption ] [DhcpOption] FORMAT DhcpOption_Index = DhcpOption_DhcpServerIndex, DhcpOption_Option, DhcpOption_Type, DhcpOption_Value, DhcpOption_ExpandValue; [ \DhcpOption ] For a detailed description of this table, see Configuring Additional DHCP Options on page 188. DHCP Static IP Table Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 756: Ntp And Daylight Saving Time Parameters

    Mediant 800B Gateway and E-SBC Parameter Description Web: DHCP Static IP Defines static "reserved" IP addresses that the device's table DHCP server allocates to specific DHCP clients defined by CLI: configure voip > MAC address. dhcp static-ip <index> The format of the ini file table parameter is as follows:...

  • Page 757: Debugging And Diagnostics Parameters

    Note: The offset setting is applied only on the hour. For example, if you configure this parameter at 15:42, the device applies the setting only at 16:00. 56.3 Debugging and Diagnostics Parameters This subsection describes the device's debugging and diagnostic parameters. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 758: General Parameters

    Mediant 800B Gateway and E-SBC 56.3.1 General Parameters The general debugging and diagnostic parameters are described in the table below. Table 56-19: General Debugging and Diagnostic Parameters Parameter Description EMS: Enable Diagnostics Determines the method for verifying correct functioning of the [EnableDiagnostics] different hardware components on the device.

  • Page 759: Sip Test Call Parameters

    This can be any string of up to 15 characters. By default, no number is defined. Notes:  This parameter is only for testing incoming calls destined to this Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 760: Syslog, Cdr And Debug Parameters

    Mediant 800B Gateway and E-SBC Parameter Description prefix number.  This feature is applicable to all applications (Gateway and SBC). Web: SBC Test ID Defines the SBC test call prefix (ID) for identifying SBC test calls that CLI: sbc-test-id traverse the device to register with an external routing entity such as an [SBCtestID] IP PBX or proxy server.
  • Page 761 A CDR is also sent upon termination (end) of the media in the call. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 762 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 763 Note: For this option to take effect, a device reset is required.  [fb] Flash Memory Burning = Saving configuration with burn to flash (in Maintenance Actions page).  [swu] Device Software Update = Software updates (i.e., loading Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 764 Mediant 800B Gateway and E-SBC Parameter Description of cmp file) through the Software Upgrade Wizard.  [ard] Access to Restricted Domains = Access to restricted Web pages:  (1) ini parameters (AdminPage)  (2) General Security Settings  (3) Configuration File ...

  • Page 765: Resource Allocation Indication Parameters

    The range is 0 to 100%. The default is 90%. [RAILoopTime] Defines the time interval (in seconds) that the device periodically checks call resource availability. The valid range is 1 to 200. The default is 10. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 766: Ha Ping Parameters

    Mediant 800B Gateway and E-SBC 56.3.5 HA Ping Parameters The High Availability (HA) Ping parameters are described in the table below. Table 56-23: HA Ping Parameters Parameter Description Web: HA Network Enables the pinging of an active IP network destination in HA mode to Reachability test reachability from one of the device's IP network interfaces.

  • Page 767: Security Parameters

     [2] Dynamic-Strict = Device latches onto the first stream. If it receives at least a minimum number of consecutive packets Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 768 Mediant 800B Gateway and E-SBC Parameter Description (configured by New<media type>StreamPackets) all from the same source which is different to the first stream and the device has not received packets from the current stream for a user- defined period (TimeoutToRelatch<media type>Msec), it latches onto the next packet received from any other stream.

  • Page 769: Https Parameters

    Determines the authentication mode used for the Web interface. EMS: Web Authentication Mode  [0] Basic Mode =Basic authentication (clear text) is used. CLI: http-auth-mode  [1] Web Based Authentication = (Default) Digest [WebAuthMode] authentication (MD5) is used. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 770: Srtp Parameters

    Mediant 800B Gateway and E-SBC Parameter Description Note: If you enable RADIUS login (i.e., the WebRADIUSLogin parameter is set to 1), you must set the WebAuthMode parameter to Basic Mode [0]. Web: Requires Client Certificates Determines whether client certificates are required for HTTPS for HTTPS connection connection.
  • Page 771 Transmitted RTP Packets RTP session. EMS: RTP  [0] Enable (default) AuthenticationDisable Tx  [1] Disable CLI: RTP-authentication- disable-tx [RTPAuthenticationDisableTx] Web: Disable Encryption On Enables encryption on transmitted RTP packets in a secured RTP Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 772: Tls Parameters

    Mediant 800B Gateway and E-SBC Parameter Description Transmitted RTP Packets session. EMS: RTP EncryptionDisable  [0] Enable (default)  [1] Disable CLI: RTP-encryption-disable-tx [RTPEncryptionDisableTx] Web: Disable Encryption On Enables encryption on transmitted RTCP packets in a secured Transmitted RTCP Packets RTP session.
  • Page 773 Determines whether the device, when acting as a client for TLS Certificate connections, verifies the Server certificate. The certificate is EMS: Verify Server Certificate verified with the Root CA information. CLI: tls-vrfy-srvr-cert  [0] Disable (default) Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 774 Mediant 800B Gateway and E-SBC Parameter Description  [VerifyServerCertificate] [1] Enable Note: If Subject Name verification is necessary, the parameter PeerHostNameVerificationMode must be used as well. Web: Strict Certificate Extension Enables the validation of the extensions (keyUsage and Validation extentedKeyUsage) of peer certificates. This validation ensures...

  • Page 775: Ssh Parameters

    Defines the maximum SSH login attempts allowed for entering an CLI: ssh-max-login-attempts incorrect password by an administrator before the SSH session is [SSHMaxLoginAttempts] rejected. The valid range is 1 to 3. the default is 3. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 776: Ids Parameters

    Mediant 800B Gateway and E-SBC 56.4.6 IDS Parameters The Intrusion Detection System (IDS) parameters are described in the table below. Table 56-29: IDS Parameters Parameter Description Web: Intrusion Detection Enables the IDS feature. System (IDS)  [0] Disable (default) CLI: enable-ids ...

  • Page 777: Quality Of Experience Parameters

    The Quality of Experience (QoE) parameters are described in the table below. Table 56-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 778 Mediant 800B Gateway and E-SBC Parameter Description Bandwidth Profile Table Web: Bandwidth Profile This table parameter defines Bandwidth Profiles. CLI: configure voip/qoe bw- The format of the ini file table parameter is as follows: profile [BWProfile] [BWProfile] FORMAT BWProfile_Index = BWProfile_Name,...

  • Page 779: Control Network Parameters

    Module = Module number, where 1 denotes the module in Slot 1  Port = Port number, where 1 denotes the Port 1 of the module For example: Authentication 1 = lee,1552,1,2; (user name "lee" with Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 780 Mediant 800B Gateway and E-SBC Parameter Description password 1552 for authenticating Port 2 of Module 1) For a description o this table, see Configuring Authentication on page 460. Note: The indexing of this parameter starts at 0. Account Table Web: Account Table This table parameter configures the Account table for EMS: SIP Endpoints >...
  • Page 781 Web: SIP ReRouting Mode Determines the routing mode after a call redirection (i.e., a 3xx EMS: SIP Re-Routing Mode SIP response is received) or transfer (i.e., a SIP REFER CLI: sip-rerouting-mode request is received). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 782 Mediant 800B Gateway and E-SBC Parameter Description  [0] Standard = (Default) INVITE messages that are [SIPReroutingMode] generated as a result of Transfer or Redirect are sent directly to the URI, according to the Refer-To header in the REFER message, or Contact header in the 3xx response.
  • Page 783 Notes:  This parameter is applicable only to the Gateway application.  This parameter is applicable only if single device registration is used (i.e., the parameter AuthenticationMode is set to authentication per gateway). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 784 Mediant 800B Gateway and E-SBC Parameter Description  Instead of configuring this parameter, the Authentication table can be used (see Authentication on page 460). Web/EMS: Password Defines the password for Basic/Digest authentication with a CLI: password-4-auth Proxy/Registrar server. A single password is used for all device [Password] ports.
  • Page 785 Defines the IP address (or FQDN) and port number (optional) EMS: Registrar IP of the Registrar server. The IP address is in dotted-decimal CLI: ip-addrr-rgstrr notation, e.g., 201.10.8.1:<5080>. [RegistrarIP] Notes:  This parameter is applicable only to the Gateway Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 786 Mediant 800B Gateway and E-SBC Parameter Description application.  If not specified, the REGISTER request is sent to the primary Proxy server.  When a port number is specified, DNS NAPTR/SRV queries aren't performed, even if the parameter DNSQueryType is set to 1 or 2.
  • Page 787 Web: ReRegister On Connection Enables the device to perform SIP re-registration upon Failure TCP/TLS connection failure. EMS: Re Register On Connection  [0] Disable (default) Failure  [1] Enable CLI: reg-on-conn-failure [ReRegisterOnConnectionFailure] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 788 Mediant 800B Gateway and E-SBC Parameter Description Web: Gateway Registration Name Defines the user name that is used in the From and To EMS: Name headers in SIP REGISTER messages. If no value is specified CLI: gw-registration-name (default) for this parameter, the UserName parameter is used [GWRegistrationName] instead.
  • Page 789 Route: <sip: pcscf- gm.ims.rr.com;lr;transport=udp> EMS: Ping Pong Keep Alive Enables the use of the carriage-return and line-feed sequences [UsePingPongKeepAlive] (CRLF) Keep-Alive mechanism, according to RFC 5626 “Managing Client-Initiated Connections in the Session Initiation Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 790 Mediant 800B Gateway and E-SBC Parameter Description Protocol (SIP)” for reliable, connection-orientated transport types such as TCP.  [0] Disable (default)  [1] Enable The SIP user agent/client (i.e., device) uses a simple periodic message as a keep-alive mechanism to keep their flow to the proxy or registrar alive (used for example, to keep NAT bindings open).

  • Page 791: Network Application Parameters

    Defines the number of unacknowledged keep-alive probes to send before considering the connection down. The valid value is 1 to 100. The default is 5. Note: TCP keepalive is enabled per SIP Interface in the SIP Interface table. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 792 Mediant 800B Gateway and E-SBC Parameter Description NAT Translation Table Web: NAT Translation This table parameter defines NAT rules for translating source IP Table addresses per VoIP interface (SIP control and RTP media traffic) into CLI: configure voip > voip- NAT IP addresses.

  • Page 793: 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 794 Mediant 800B Gateway and E-SBC Parameter Description Web: Reject Cancel after Determines whether the device accepts or rejects a SIP CANCEL Connect request received after the receipt of a 200 OK, during an established CLI: reject-cancel-after- call. connect  [0] = (Default) Accepts the CANCEL, by responding with a 200 OK [RejectCancelAfterConnec and terminating the call session.
  • Page 795 ISDN Progress or Proceeding with PI messages) and an Alerting message is then received from the Tel side (with or without Progress Indicator), the device does not send an additional 18x Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 796 Mediant 800B Gateway and E-SBC Parameter Description response, and the voice channel remains open. However, if the device did not send a 183 with an SDP and it receives an Alert without PI, the device sends a 180 (without SDP). If it receives an Alert with PI it sends a 183with an SDP.
  • Page 797 Request-URI.  The proxy server is determined by the Proxy Set that is associated with the Serving IP Group defined for the Trunk Group in the Trunk Group Settings table. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 798 Mediant 800B Gateway and E-SBC Parameter Description Web: TDM Over IP Defines the minimal number of SIP dialogs that must be established Minimum Calls For Trunk when using TDM Tunneling to consider the specific trunk as active. Activation When using TDM Tunneling, if calls from this defined number of B- EMS: TDM Over IP Min channels pertaining to a specific Trunk fail (i.e., SIP dialogs are not...
  • Page 799 5070, the port number is not changed. An example of a SIP From header with the default port is shown Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 800 Mediant 800B Gateway and E-SBC Parameter Description below: From: <sip:+4000@10.8.4.105:5060;user=phone>;tag=f25419a 96a;epid=009FAB8F3E  [0] Disable (default)  [1] Enable Web/EMS: Enable SIPS Enables secured SIP (SIPS URI) connections over multiple hops. CLI: enable-sips  [0] Disable (default) [EnableSIPS]  [1] Enable When the SIPTransportType parameter is set to 2 (i.e., TLS) and the...
  • Page 801 History-Info as is, adds the reason of the failure response to the last entry, and concatenates a new destination to it (if an additional request is sent). The order of the reasons is as follows: Q.850 Reason SIP Reason SIP Response code Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 802 Mediant 800B Gateway and E-SBC Parameter Description  Upon receiving the final response (success or failure), the device searches for a Redirect reason in the History-Info (i.e., 3xx/4xx SIP reason). If found, it is passed to ISDN according to the following...
  • Page 803 Inbound IP Routing table is used for routing the call. Below is an example of an INVITE Request-URI with the 'tgrp' parameter, indicating that the IP call should be routed to Trunk Group Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 804 Mediant 800B Gateway and E-SBC Parameter Description INVITE sip:200;tgrp=7;trunk- context=example.com@10.33.2.68;user=phone SIP/2.0 Notes:  For enabling routing based on the 'tgrp' parameter, the UseSIPTgrp parameter must be set to 2.  For IP-to-Tel routing based on the 'dtg' parameter (instead of the 'tgrp' parameter), use the parameter UseBroadsoftDTG.
  • Page 805 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 806 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: SDP Session Defines the value of the Owner line ('o' field) in outgoing SDP Owner messages. CLI: sdp-session-owner The valid range is a string of up to 39 characters. The default is [SIPSDPSessionOwner] "AudiocodesGW".
  • Page 807 200 OK responses to REGISTER requests. CLI: p-associated-uri-hdr When enabled, the first URI in the P-Associated-URI header is used in [EnablePAssociatedURIHe subsequent requests as the From/P-Asserted-Identity headers value. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 808 Mediant 800B Gateway and E-SBC Parameter Description  ader] [0] Disable (default)  [1] Enable Note: P-Associated-URIs in registration responses is handled only if the device is registered per endpoint (using the User Information file). Web/EMS: Source Number Determines from which SIP header the source (calling) number is Preference obtained in incoming INVITE messages.
  • Page 809 EMS: P Asserted User Defines a 'representative number' (up to 50 characters) that is used as Name the user part of the Request-URI in the P-Asserted-Identity header of CLI: p-assrtd-usr-name an outgoing INVITE for Tel-to-IP calls. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 810 Mediant 800B Gateway and E-SBC Parameter Description [PAssertedUserName] The default is null. EMS: Use URL In Refer To Defines the source for the SIP URI set in the Refer-To header of Header outgoing REFER messages. [UseAORInReferToHeader  [0] = (Default) Use SIP URI from Contact header of the initial call.
  • Page 811 Note: For this parameter to take effect, a device reset is required. Note: This parameter is no longer valid and must not be used. [IP2IPTranscodingMode] Defines the voice transcoding mode (media negotiation) between two user agents for the IP-to-IP application. This parameter must always Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 812 Mediant 800B Gateway and E-SBC Parameter Description be set to 1 when using the IP-to-IP application.  [0] Only if Required = Do not force transcoding. Many of the media settings (such as gain control) are not implemented on the voice stream.
  • Page 813 SCE of the codec is enabled. If the remote UA responds with a “CN” in the SDP, then CNG occurs; otherwise, CNG does not occur.  If the device is the receiver and the remote SIP UA does not send a Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 814 Mediant 800B Gateway and E-SBC Parameter Description “CN” in the SDP, then no CNG occurs. If the remote side sends a “CN”, the device attempts to be compatible with the remote side and even if the codec’s SCE is disabled, CNG occurs.
  • Page 815  [0] Disable (default)  [1] Transmit & Receive = Send and receive RTP packets.  [2] Transmit Only= Send RTP packets only.  [3] Receive Only= Receive RTP packets only. Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 816 Mediant 800B Gateway and E-SBC Parameter Description  To activate the RTP Only feature without using ISDN / CAS signaling, you must do the following:  Configure E1/T1 Transparent protocol type (set the ProtocoType parameter to 5 or 6). ...
  • Page 817 Proxy Keep-Alive mechanism) and no other alternative route exists to send the call.  The IP Connectivity mechanism is enabled (using the AltRoutingTel2IPEnable parameter) and there is no connectivity to any destination IP address. Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 818 Mediant 800B Gateway and E-SBC Parameter Description  Analog: The FXSOOSBehavior parameter determines the behavior of the FXS endpoints when a Busy Out or Graceful Lock occurs.  Analog: FXO endpoints during Busy Out and Lock are inactive.  Analog: See the LifeLineType parameter for complementary optional behavior.
  • Page 819 For all other SIP messages, it is multiplied by two until SipT2Rtx. For example, assuming SipT1Rtx = 500 and SipT2Rtx = 4000:  The first retransmission is sent after 500 msec. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 820 Mediant 800B Gateway and E-SBC Parameter Description  The second retransmission is sent after 1000 (2*500) msec.  The third retransmission is sent after 2000 (2*1000) msec.  The fourth retransmission and subsequent retransmissions until SIPMaxRtx are sent after 4000 (2*2000) msec.

  • Page 821: Coders And Profile Parameters

    [ \CodersGroup0 ] [ CodersGroup1 ] FORMAT CodersGroup1_Index = CodersGroup1_Name, CodersGroup1_pTime, CodersGroup1_rate, CodersGroup1_PayloadType, CodersGroup1_Sce; CodersGroup1 0 = Transparent, 20, 0, 56, 0; CodersGroup1 1 = g726, 20, 0, 23, 0; [ \CodersGroup1 ] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 822 Mediant 800B Gateway and E-SBC Parameter Description Notes:  For a list of supported coders and a detailed description of this table, see Configuring Default Coders on page 297.  For configuring Coder Groups, see ''Configuring Coder Groups'' on page 300.

  • Page 823: Channel Parameters

    For a description of this parameter, see Configuring Tel Profiles on page 301. 56.9 Channel Parameters This subsection describes the device's channel parameters. 56.9.1 Voice Parameters The voice parameters are described in the table below. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 824 Mediant 800B Gateway and E-SBC Table 56-35: Voice Parameters Parameter Description Web/EMS: Input Gain Global parameter that defines the pulse-code modulation CLI: input-gain (PCM) input (received) gain control level (in decibels). You [InputGain] can also configure this functionality per specific calls, using IP Profiles (IpProfile_InputGain) or Tel Profiles.
  • Page 825 [ECNLPMode]  [0] = (Default) NLP adapts according to echo changes  [1] = Disables NLP  [2] = Silence output NLP Note: This parameter can also be configured in a Tel Profile. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 826: Coder Parameters

    Mediant 800B Gateway and E-SBC Parameter Description CLI: echo-canceller-aggressive-NLP Enables the Aggressive NLP at the first 0.5 second of the [EchoCancellerAggressiveNLP] call.  [0] = Disable  [1] = (Default) Enable. The echo is removed only in the first half of a second of the incoming IP signal.

  • Page 827: Dtmf Parameters

    The valid range is -10 to 10 dB. The default is 0 dB. Note: For this parameter to take effect, a device reset is required. EMS: DTMF Inter Interval Defines the time (in msec) between generated DTMF digits to Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 828 Mediant 800B Gateway and E-SBC Parameter Description (msec) PSTN side (if TxDTMFOption = 1, 2 or 3). CLI: inter-digit-interval The valid range is 0 to 32767. The default is 100. [DTMFInterDigitInterval] EMS: DTMF Length (msec) Defines the time (in msec) for generating DTMF tones to the PSTN [DTMFDigitLength] side (if TxDTMFOption = 1, 2 or 3).

  • Page 829: 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 830 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 831 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 832 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 833 (i.e., after a SIP BYE). The RTCP [SBCRtcpXrReportMode] XR is sent in the SIP PUBLISH message.  [0] Disable (default)  [1] End of Call Note: This parameter is applicable only to the SBC application. Version 6.8 Mediant 800B Gateway and E-SBC...

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

    Mediant 800B Gateway and E-SBC 56.10 Gateway and IP-to-IP Parameters 56.10.1 Fax and Modem Parameters The fax and modem parameters are described in the table below. Table 56-39: Fax and Modem Parameters Parameter Description Web: Fax Transport Mode Determines the fax transport mode used by the device.
  • Page 835 ''Configuring IP Profiles'' on page 304. 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 836 Mediant 800B Gateway and E-SBC Parameter Description Web: Fax Detect Timeout Since Defines a timeout (in msec) for detecting fax from the Tel side Connect (msec) during an established voice call. The interval starts from when the voice call is established. If the device detects a fax tone CLI: configure voip >...
  • Page 837 [FaxBypassOutputGain] Web/EMS: Modem Bypass Output Defines the modem bypass output gain control. Gain The range is -31 dB to +31 dB, in 1-dB steps. The default is 0 [ModemBypassOutputGain] (i.e., no gain). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 838 Mediant 800B Gateway and E-SBC Parameter Description EMS: Basic Packet Interval Defines the basic frame size used during fax/modem bypass CLI: modem-bypass-output-gain sessions. [FaxModemBypassBasicRTPPac  [0] = (Default) Determined internally ketInterval]  [1] = 5 msec (not recommended)  [2] = 10 msec ...
  • Page 839 T.38 (and other) packets received from the WAN, unless the device behind NAT sends at least one IP packet from the LAN to the WAN through the firewall. If the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 840 Mediant 800B Gateway and E-SBC Parameter Description 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 841: Dtmf And Hook-Flash Parameters

    Where 16 is the DTMF code for hook flash.  [7] INFO (HUAWEI) = Sends a SIP INFO message with Hook-Flash indication. The device sends the INFO message as follows: Content-Length: 17 Content-Type: application/sscc event=flashhook Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 842 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 843 IpProfile_SecondTxDtmfOption). For configuring IP Profiles, see ''Configuring IP Profiles'' on page 304. [DisableAutoDTMFMute] Enables the automatic muting of DTMF digits when out-of-band DTMF transmission is used.  [0] = (Default) Automatic mute is used. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 844 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 845: 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 846 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 600.

  • Page 847: 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 848 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 849 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 850 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 851 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 852 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 853: 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 854 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 855  [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 856 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 857 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 858: Call Waiting Parameters

    Mediant 800B Gateway and E-SBC 56.10.5.2 Call Waiting Parameters The call waiting parameters are described in the table below. Table 56-44: Call Waiting Parameters Parameter Description Web/EMS: Enable Call Waiting Enables the Call Waiting feature. CLI: call-waiting  [0] Disable [EnableCallWaiting] ...
  • Page 859 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 860: 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 56.10.5.3 Call Forwarding Parameters The call forwarding parameters are described in the table below. Table 56-45: Call Forwarding Parameters Parameter Description Web: Enable Call Enables the Call Forwarding feature.

  • Page 861: 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 862 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 863: 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 864: 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 865 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 866 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 867: Multi-Line Extensions And Supplementary Services Parameters

    EMS: 3 Way Mode feature is used. CLI: 3w-conf-mode  [0] AudioCodes Media Server = (Default) The Conference- [3WayConferenceMode] 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 868 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 869: 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 870 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 871 (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 872 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 873 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 874 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 875: 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 876: 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 877: 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 878 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 879: 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 880: Pstn Parameters

    Mediant 800B Gateway and E-SBC 56.10.6 PSTN Parameters This subsection describes the device's PSTN parameters. 56.10.6.1 General Parameters The general PSTN parameters are described in the table below. Table 56-56: General PSTN Parameters Parameter Description Web: Trunk Name Defines an arbitrary name for a trunk (where x denotes the trunk CLI: name (config-voip >...
  • Page 881 ISDN Alerting, Progress, or Connect message is received within the duration of T310 timer, the call clears. The valid value range is 0 to 600 seconds. The default is 0 (i.e., use the default timer value according to the protocol's Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 882 Mediant 800B Gateway and E-SBC Parameter Description specifications). Notes:  For this parameter to take effect, a device reset is required.  When both the parameters ISDNDmsTimerT310 and ISDNTimerT310 are configured, the value of the parameter ISDNTimerT310 prevails. [ISDNDMSTimerT310] Defines the override T310 timer for the DMS-100 ISDN variant.
  • Page 883 [0] = Lock the trunk; stops trunk traffic to configure the trunk protocol type.  [1] = Shutting down (read only).  [2] = (Default) Unlock the trunk; enables trunk traffic. Notes:  For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 884 Mediant 800B Gateway and E-SBC Parameter Description  When the device is locked from the Web interface, this parameter changes to 0.  To define the administrative state per trunk, use the TrunkAdministrativeState parameter. [TrunkAdministrativeState_x] Defines the administrative state per trunk, where x denotes the trunk number.
  • Page 885 (a, e, i, o, and u, respectively).  [1] Western European (Default)  [2] Central European  [3] South European  [4] North European  [5] Cyrillic  [6] Arabic  [7] Hebrew  [8] Turkish Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 886: Tdm Bus And Clock Timing Parameters

    Mediant 800B Gateway and E-SBC 56.10.6.2 TDM Bus and Clock Timing Parameters The TDM Bus parameters are described in the table below. Table 56-57: TDM Bus and Clock Timing Parameters Parameter Description TDM Bus Parameters Web/EMS: PCM Law Select Determines the type of pulse-code modulation (PCM) companding [PCMLawSelect] algorithm law in input and output TDM bus.
  • Page 887 100 indicates that the device does not perform a fallback to the [AutoClockTrunkPriority] trunk (typically, used to mark untrusted source of clock). Note: Fallback is enabled when the TDMBusPSTNAutoClockEnable parameter is set to 1. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 888: Cas Parameters

    Mediant 800B Gateway and E-SBC 56.10.6.3 CAS Parameters The Common Channel Associated (CAS) parameters are described in the table below. Note that CAS is not applicable to BRI interfaces. Table 56-58: CAS Parameters Parameter Description Web: CAS Transport Type Determines the ABCD signaling transport type over IP.
  • Page 889  Only one of these formats can be implemented; not both.  When this parameter is not configured, a single CAS table for the entire trunk is used, configured by the parameter CASTableIndex. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 890 Mediant 800B Gateway and E-SBC Parameter Description [CASTablesNum] Defines how many CAS protocol configurations files are loaded. The valid range is 1 to 8. Note: For this parameter to take effect, a device reset is required. CAS State Machines Parameters Note: For configuring the CAS State Machine table using the Web interface, see ''Configuring CAS State Machines'' on page 337.

  • Page 891: Isdn Parameters

    - calling equipment is not ISDN. Web/EMS: B-channel Negotiation Determines the ISDN B-Channel negotiation mode. CLI: b-ch-negotiation  [0] Preferred [BchannelNegotiation]  [1] Exclusive (default)  [2] Any Notes:  This parameter is applicable only to ISDN Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 892 Mediant 800B Gateway and E-SBC Parameter Description protocols.  For some ISDN variants, when 'Any' (2) is selected, the Setup message excludes the Channel Identification IE.  The Any' (2) option is applicable only if the following conditions are met: ...
  • Page 893 Network provided, User provided: the first one is used  User provided, Network provided: the second one is used  User provided, user provided: the first one is used When this bit is configured, the device behaves Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 894 Mediant 800B Gateway and E-SBC Parameter Description as follows:  Network provided, Network provided: the first calling number is used  Network provided, User provided: the second one is used  User provided, Network provided: the first one is used ...
  • Page 895 5ESS for B-channel maintenance. Notes:  To configure the device to support several ISDNIBehavior features, enter a summation of the individual feature values. For example, to support both [512] and [2048] features, set the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 896 Mediant 800B Gateway and E-SBC Parameter Description parameter ISDNIBehavior is set to 2560 (i.e., 512 + 2048).  When configuring in the Web interface, to select the options click the arrow button and then for each required option select 1 to enable.
  • Page 897 Law in outgoing voice calls. When disabled, the device sends G.711-A-Law in outgoing voice calls. Note: This option is applicable only to the Korean variant.  [128] DIAL WITH KEYPAD = The device uses Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 898 Mediant 800B Gateway and E-SBC Parameter Description the Keypad IE to store the called number digits instead of the CALLED_NB IE. Note: This option is applicable only to the Korean variant (Korean network). This is useful for Korean switches that don't accept the CALLED_NB IE.
  • Page 899 0-63: Static TEI is used.  127: Dynamic TEI allocation is supported (TEI request procedure initiated). Note: The value 127 replaces the previous configuration requirement to set the ISDNIBehavior parameter to NS EXPLICIT INTERFACE ID (1). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 900 Mediant 800B Gateway and E-SBC Parameter Description CLI: tei-config-p2mp Defines the BRI TEI when in point-to-multipoint (P2MP) mode. (config-voice > interface bri The valid value is 0 to 63, 127. The default is 127. <module/port>)  Network Side: Not applicable - In network side in P2MP [BriTEIConfigP2MP_x] configuration, any TEI must be accepted.

  • Page 901: Isdn And Cas Interworking Parameters

    INVITEs. Note: When IP-to-Tel overlap dialing is enabled, to send ISDN Setup messages without the Sending Complete IE, the ISDNOutCallsBehavior parameter must be set to USER SENDING COMPLETE (2). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 902 Mediant 800B Gateway and E-SBC Parameter Description Web: Enable Receiving of Determines the receiving (Rx) type of ISDN overlap dialing for Tel- Overlap Dialing to-IP calls, per trunk. CLI: ovrlp-rcving-type  [0] None = (Default) Disabled. [ISDNRxOverlap_x]  [1] Local receiving = ISDN Overlap Dialing - the complete number is sent in the INVITE Request-URI user part.
  • Page 903 ADDE1C269FAA 06 800100820100A10F020136 0201F0A00702010102021F69 then it is added as an IE to the outgoing Q.931 message as 1C269FAA 06 800100820100A10F020136 0201F0A00702010102021F69, where, for example, "1C269F" is a 26 byte length Facility IE. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 904 Mediant 800B Gateway and E-SBC Parameter Description Note: This feature is similar to that of the AddIEinSetup parameter. If both parameters are configured, the x-isdntunneling parameter takes precedence. Web/EMS: Enable QSIG Global parameter that enables QSIG tunneling-over-SIP for all calls.
  • Page 905 ISUBNumberOfDigits parameter. The default value of ISUBNumberOfDigits is 0, thus, if this parameter is not configured, and 1) and 2) scenarios (described above) have not provided an isub value, the subaddress remains empty. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 906 Mediant 800B Gateway and E-SBC Parameter Description Web: Default Cause Mapping Defines a single default ISDN release cause that is used (in ISDN- From ISDN to SIP to-IP calls) instead of all received release causes, except when the CLI: dflt-cse-map-isdn2sip following Q.931 cause values are received: Normal Call Clearing...
  • Page 907 Note: This parameter is applicable for Tel-to-IP and IP-to-Tel calls. Web/EMS: Remove CLI when Determines (for IP-to-Tel calls) whether the Calling Number and Restricted Calling Name IEs are removed from the ISDN Setup message if the Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 908 Mediant 800B Gateway and E-SBC Parameter Description CLI: rmv-cli-when-restr presentation is set to Restricted. [RemoveCLIWhenRestricted]  [0] No = (Default) IE's are not removed.  [1] Yes = IE's are removed. Web/EMS: Remove Calling Enables the device to remove the Calling Name from SIP-to-ISDN Name calls for all trunks.
  • Page 909 [1] = Supports partial retrieval of Redirect Number (number only) from the Facility IE in ISDN Setup messages. This is applicable to Redirect Number according to ECMA-173 Call Diversion Supplementary Services. Note: To enable this feature, the parameter Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 910 Mediant 800B Gateway and E-SBC Parameter Description ISDNDuplicateQ931BuffMode must be set to 1. CLI: call-re-rte-mode Determines whether ISDN call rerouting (call forward) is performed [CallReroutingMode] by the PSTN instead of by the SIP side. This call forwarding is based on Call Deflection for Euro ISDN (ETS-300-207-1) and QSIG (ETSI TS 102 393).
  • Page 911 Enables interworking of Emergency Location Identification from SIP to PRI.  [0] = Disabled (default)  [1] = Enabled When enabled, the From header received in the SIP INVITE is translated into the following ISDN IE's: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 912 Mediant 800B Gateway and E-SBC Parameter Description  Emergency Call Control.  Generic Information - to carry the Location Identification Number information.  Generic Information - to carry the Calling Geodetic Location information. Note: This capability is applicable only to the NI-2 ISDN variant.
  • Page 913 "C" prior to call transfer. The device handles this feature as follows:  IP-to-Tel (user side): When a SIP REFER message is received, the device initiates a transfer by sending a Facility message to the PBX. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 914 Mediant 800B Gateway and E-SBC Parameter Description  Tel-to-IP (network side): When a Facility message initiating an out-of-band blind transfer is received from the PBX, the device sends a SIP REFER message to the IP side (if the EnableNetworkISDNTransfer parameter is set to 1).
  • Page 915 Asserted-Identity and Privacy headers in the received SIP INFO message.  To include the P-Asserted-Identity header in outgoing SIP UPDATE messages, set the AssertedIDMode parameter to Add P-Asserted-Identity. EMS: CAS Detection Of Hook Enables sending Wink signal toward CAS trunks. Flash Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 916: Answer And Disconnect Supervision Parameters

    Mediant 800B Gateway and E-SBC Parameter Description  [0] = Disable (default) CLI: is-cas-sndhook-flsh [CASSendHookFlash]  [1] = Enable If the device receives a mid-call SIP INFO message with flashhook event body (as shown below) and this parameter is set to 1, the device generates a wink signal toward the CAS trunk.
  • Page 917 Tel side only when the call duration is greater than or equal to the minimum call duration. Notes:  This parameter is applicable to IP-to-Tel and Tel-to-IP calls.  This parameter is applicable only to ISDN and CAS protocols. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 918 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Disconnect on Dial Determines whether the device disconnects a call when a dial Tone tone is detected from the PBX. CLI: disc-on-dial-tone  [0] Disable = (Default) Call is not released. [DisconnectOnDialTone] ...
  • Page 919 [0] Disable = Call is not disconnected upon detection of a busy End Tones tone. CLI: disc-on-bsy-tone-c  [1] Enable = (Default) Call is released upon detection of busy [DisconnectOnBusyTone] or reorder (fast busy) tone. Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 920 Mediant 800B Gateway and E-SBC Parameter Description  Digital interfaces: This parameter is applicable only to CAS protocols.  Analog interfaces: This parameter is applicable only to FXO interfaces.  This parameter is also applicable to the IP-to-IP application. ...
  • Page 921 The valid range is 100 to 2500 msec. The default is 1000 msec. Notes:  This parameter is applicable only to FXO interfaces.  For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 922: Tone Parameters

    Mediant 800B Gateway and E-SBC 56.10.9 Tone Parameters This subsection describes the device's tone parameters. 56.10.9.1 Telephony Tone Parameters The telephony tone parameters are described in the table below. Table 56-62: Tone Parameters Parameter Description CLI: help-tone-4-ip2ip Enables playing a held tone to an IP-to-IP leg instead of placing it [PlayHeldToneForIP2IP] on hold.
  • Page 923 Defines the duration (in seconds) of the reorder tone played to the Tone Duration [sec] PSTN side after the IP call party releases the call, for the Cut- CLI: cut-thru-reord-dur Through feature. After the tone stops playing, an incoming call is Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 924 Tel side. The user-defined tone is configured when creating the PRT file, using AudioCodes DConvert utility. The tone must be assigned to the "acSpecialConditionTone" (Tone Type 21) option in DConvert. The parameter can be configured with up to 10 release codes.
  • Page 925 (due to a previous 183 early media response or due to an SDP in the current 180 response), the device configured for ISDN / CAS doesn't play the ringback tone; PI = 8 is Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 926 Mediant 800B Gateway and E-SBC Parameter Description sent in an ISDN Alert message (unless the ProgressIndicator2ISDN_x parameter is configured differently). If a 180 response is received, but the 'early media' voice channel is not opened, the device configured for CAS plays a ringback tone to the PSTN. The device...
  • Page 927 Global parameter that enables the device to play a ringback tone to EMS: Play Ring Back Tone To the IP side for IP-to-Tel calls. You can also configure this functionality per specific calls, using IP Profiles Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 928 Mediant 800B Gateway and E-SBC Parameter Description CLI: play-rbt-2ip (IpProfile_PlayRBTone2IP). For a detailed description of this [PlayRBTone2IP] parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page 304. 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 929: Tone Detection Parameters

    If the call is in connected state, the SIT does not disconnect the call. Detection of busy or reorder tones disconnect these calls also in call connected state. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 930: Metering Tone Parameters

    Mediant 800B Gateway and E-SBC Parameter Description  For IP-to-CAS calls, detection of busy, reorder, or SIT tones disconnect the call in any call state. EMS: UDT Detector Frequency Defines the deviation (in Hz) allowed for the detection of each Deviation signal frequency.
  • Page 931 To associate a configured Charge Code to an outgoing Tel-to-IP call, use the Outbound IP Routing table.  To configure the Charge Codes table using the Web interface, see Configuring Charge Codes Table on page 454. Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 932: Telephone Keypad Sequence Parameters

    Mediant 800B Gateway and E-SBC 56.10.10 Telephone Keypad Sequence Parameters The telephony keypad sequence parameters are described in the table below. Table 56-65: Telephone Keypad Sequence Parameters Parameter Description Web/EMS: Call Pickup Key Defines the keying sequence for performing a call pick-up. Call...
  • Page 933 Defines the keypad sequence to activate the forward on no EMS: Call Forward No Answer answer option. CLI: fwd-no-answer [KeyCFNoAnswer] Web: Forward On Busy Defines the keypad sequence to activate the forward on busy EMS: Call Forward Busy option. CLI: fwd-on-busy [KeyCFBusy] Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 934 Mediant 800B Gateway and E-SBC Parameter Description Web: Forward On Busy or No Defines the keypad sequence to activate the forward on 'busy Answer or no answer' option. EMS: CF Busy Or No Answer CLI: fwd-busy-or-no-ans [KeyCFBusyOrNoAnswer] Web: Do Not Disturb...

  • Page 935: Fxo And Fxs Parameters

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

  • Page 939: Trunk Groups And Routing Parameters

    The format of the ini file table parameter is as follows: group trunk-group-setting [TrunkGroupSettings] [TrunkGroupSettings] FORMAT TrunkGroupSettings_Index = TrunkGroupSettings_TrunkGroupId, TrunkGroupSettings_ChannelSelectMode, TrunkGroupSettings_RegistrationMode, TrunkGroupSettings_GatewayName, TrunkGroupSettings_ContactUser, TrunkGroupSettings_ServingIPGroup, TrunkGroupSettings_MWIInterrogationType, TrunkGroupSettings_TrunkGroupName; [\TrunkGroupSettings] For a description of this table, see ''Configuring Hunt Group Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 940 Mediant 800B Gateway and E-SBC Parameter Description Settings'' on page 353. 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  All Trunk Groups configured without a channel select...
  • Page 941 The domain name is used instead of a Proxy name or IP address in the 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 383. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 942 Mediant 800B Gateway and E-SBC Parameter Description [RouteModeTel2IP] Outbound IP Routing Table 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 943 Note: This parameter is applicable only to digital interfaces. CLI: etsi-diversion Determines the method in which the Redirect Number is [EnableETSIDiversion] sent to the Tel side.  [0] = (Default) Q.931 Redirecting Number Information Element (IE). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 944 Mediant 800B Gateway and E-SBC Parameter Description  [1] = ETSI DivertingLegInformation2 in a Facility IE. Web: Add CIC Determines whether to add the Carrier Identification Code CLI: add-cic (CIC) as a prefix to the destination phone number for IP-to- [AddCicAsPrefix] Tel calls.
  • Page 945 If the first received response is 180 without SDP, the device responds according to the PlayRBTone2TEL parameter and processes the subsequent 18x forking responses. Note: Regardless of this parameter setting, once a SIP 200 Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 946: Ip Connectivity Parameters

    Mediant 800B Gateway and E-SBC Parameter Description OK response is received, the device uses the RTP information and re-opens the voice stream, if necessary. Web: Forking Timeout Defines the timeout (in seconds) that is started after the first CLI: forking-timeout...

  • Page 947: Alternative Routing Parameters

    However, if a contact [UseAltRouteReasonsFor3xx] responds with a 486 or 600, the device does not try to redirect the call to next contact, and drops the call. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 948 Mediant 800B Gateway and E-SBC Parameter Description  [1] No if 6xx = Upon receipt of a 3xx response, the device tries each contact, one by one, listed in the Contact headers. However, if a 6xx Global Failure response is received during this process (e.g., 600 Busy Everywhere) the device does not try to...
  • Page 949 For a detailed description of this table, see ''Alternative Routing to Trunk upon Q.931 Call Release Cause Code'' on page 403. Forward On Busy Trunk Destination Table Web/EMS: Forward On Busy This table parameter configures the Forward On Busy Trunk Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 950: Number Manipulation Parameters

    Mediant 800B Gateway and E-SBC Parameter Description Trunk Destination Destination table. This table allows you to define an alternative IP CLI: configure voip > gw routing destination if a trunk is busy for IP-to-Tel calls. fwd-on-bsy-trk-dest The format of the ini file table parameter is as follows:...
  • Page 951 Defines the redirect reason for IP-to-Tel calls. If redirect (diversion) Reason information is received from the IP, the redirect reason is set to the CLI: ip2tel-redir-reason value of this parameter before the device sends it on to the Tel. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 952 Mediant 800B Gateway and E-SBC Parameter Description  [-1] Not Configured (default) [SetIp2TelRedirectReason]  [0] Unkown  [1] Busy  [2] No Reply  [3] Network Busy  [4] Deflection  [9] DTE out of Order  [10] Forwarding DTE ...
  • Page 953 [1] Yes = Add Trunk Group ID as prefix to called number. Notes:  This option can be used to define various routing rules.  To use this feature, you must configure the Trunk Group IDs (see Configuring Trunk Group Table on page 351). Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 954 Mediant 800B Gateway and E-SBC Parameter Description Web: Add Trunk ID as Prefix Determines whether or not the slot number/port number/Trunk ID is EMS: Add Port ID As Prefix added as a prefix to the called (destination) number for Tel-to-IP CLI: trk-id-as-prefix calls.
  • Page 955 The valid range is an 8-character string. By default, no value is defined. Web: Add Number Plan and Determines whether the TON/PLAN parameters are included in the Type to RPI Header Remote-Party-ID (RPID) header. EMS: Add Ton 2 RPI  [0] No Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 956 Mediant 800B Gateway and E-SBC Parameter Description  [1] Yes (default) CLI: np-n-type-to-rpi-hdr [AddTON2RPI] If the Remote-Party-ID header is enabled (EnableRPIHeader = 1) and AddTON2RPI = 1, it's possible to configure the calling and called number type and number plan using the Number Manipulation tables for Tel-to-IP calls.
  • Page 957 This parameter table manipulates the source number for IP-to-Tel Manipulation Table for IP > calls. The format of the ini file table parameter is as follows: Tel Calls [SourceNumberMapIp2Tel] EMS: SIP Manipulations > FORMAT SourceNumberMapIp2Tel_Index = Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 958 Mediant 800B Gateway and E-SBC Parameter Description Source IP to Telcom SourceNumberMapIp2Tel_ManipulationName, CLI: configure voip > gw SourceNumberMapIp2Tel_DestinationPrefix, manipulations SourceNumberMapIp2Tel_SourcePrefix, SourceNumberMapIp2Tel SourceNumberMapIp2Tel_SourceAddress, [SourceNumberMapIP2Tel] SourceNumberMapIp2Tel_NumberType, SourceNumberMapIp2Tel_NumberPlan, SourceNumberMapIp2Tel_RemoveFromLeft, SourceNumberMapIp2Tel_RemoveFromRight, SourceNumberMapIp2Tel_LeaveFromRight, SourceNumberMapIp2Tel_Prefix2Add, SourceNumberMapIp2Tel_Suffix2Add, SourceNumberMapIp2Tel_IsPresentationRestricted; [\SourceNumberMapIp2Tel] For a detailed description of this table, see ''Configuring Source/Destination Number Manipulation'' on page 359.
  • Page 959 SIP Phone-Context Mapping Rules'' on page 374. Web/EMS: Add Phone Determines whether the received Phone-Context parameter is added Context As Prefix as a prefix to the outgoing ISDN Setup message with (for digital Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 960 Mediant 800B Gateway and E-SBC Parameter Description CLI: add-ph-cntxt-as-pref interfaces) Called and Calling numbers. [AddPhoneContextAsPrefix]  [0] Disable (default)  [1] Enable User's Manual Document #: LTRT-10286...

  • Page 961: Sbc Parameters

    SRD, the call is rejected. Web: SBC No Answer Timeout Defines the timeout (in seconds) for SBC outgoing (outbound CLI: sbc-no-arelt-timeout IP routing) SIP INVITE messages. If the called IP party does Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 962 Mediant 800B Gateway and E-SBC Parameter Description [SBCAlertTimeout] not answer the call within this user-defined interval, the device disconnects the session. The device starts the timeout count upon receipt of a SIP 180 Ringing response from the called party. If no other SIP response (for example, 200 OK) is received thereafter within this timeout, the call is released.
  • Page 963 CLI: configure voip/sbc general- Registration database. setting/sbc-usr-reg-grace-time The valid value is 0 to 300 (i.e., 5 minutes). The default is 0. [SBCUserRegistrationGraceTime Web/EMS: Handle P-Asserted- Global parameter that defines the handling of the SIP P- Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 964 Mediant 800B Gateway and E-SBC Parameter Description Identity Asserted-Identity header. You can also configure this CLI: p-assert-id functionality per specific calls, using IP Profiles [SBCAssertIdentity] (IpProfile_SBCAssertIdentity). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page 304.
  • Page 965 This parameter is used to provide replay protection (i.e., ensures that old communication streams are not used in replay attacks). The valid value range is 30 to 600. The default is 300. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 966 Mediant 800B Gateway and E-SBC Parameter Description Web: Authentication Challenge Defines the type of server-based authentication challenge. Method  [0] 0 = (Default) Send SIP 401 "Unauthorized" with a CLI: auth-chlng-mthd WWW-Authenticate header as the authentication challenge [AuthChallengeMethod] response. ...
  • Page 967 Aastra IP phones display the message, "Stand Alone Mode" on their LCD screens. Survivability mode occurs when connectivity with the WAN fails and as a result, the device enables communication between IP phone users within the LAN Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 968 Mediant 800B Gateway and E-SBC Parameter Description enterprise.  [0] = Disable  [1] = Enable When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following...
  • Page 969  [1] Enable = All SBC calls use the No Media Anchoring feature (i.e., direct media). Note: For more information on No Media Anchoring, see ''No Media Anchoring (Anti Tromboning)'' on page 495. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 970 Mediant 800B Gateway and E-SBC Parameter Description Web: Transcoding Mode Global parameter that defines the voice transcoding mode CLI: transcoding-mode (media negotiation). You can also configure this functionality [TranscodingMode] per specific calls, using IP Profiles (IpProfile_TranscodingMode). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see Configuring IP Profiles on page 304.
  • Page 971 (SIP CLI: configure voip > sbc sbc- dialogs). admission-control The format of the ini file table parameter is as follows: [SBCAdmissionControl] [SBCAdmissionControl] FORMAT SBCAdmissionControl_Index = SBCAdmissionControl_AdmissionControlName, SBCAdmissionControl_LimitType, SBCAdmissionControl_IPGroupID, SBCAdmissionControl_SRDID, SBCAdmissionControl_RequestType, SBCAdmissionControl_RequestDirection, SBCAdmissionControl_Limit, SBCAdmissionControl_LimitPerUser, Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 972 Mediant 800B Gateway and E-SBC Parameter Description SBCAdmissionControl_Rate, SBCAdmissionControl_MaxBurst, SBCAdmissionControl_Reservation; [\SBCAdmissionControl] For a detailed description of this table, see ''Configuring Admission Control'' on page 519. Allowed Audio Coders Table Web: Allowed Audio Coders This table parameter defines Allowed Coders Groups, which CLI: configure voip >...
  • Page 973 Manipulation dialog message. The format of the ini file table parameter is as CLI: configure voip > sbc follows: manipulations ip-inbound- [IPInboundManipulation] manipulation FORMAT IPInboundManipulation_Index = [IPInboundManipulation] IPInboundManipulation_ManipulationName IPInboundManipulation_IsAdditionalManipulation, IPInboundManipulation_ManipulatedURI, IPInboundManipulation_ManipulationPurpose, IPInboundManipulation_SrcIPGroupID, IPInboundManipulation_SrcUsernamePrefix, Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 974: Standalone Survivability Parameters

    Mediant 800B Gateway and E-SBC Parameter Description IPInboundManipulation_SrcHost, IPInboundManipulation_DestUsernamePrefix, IPInboundManipulation_DestHost, IPInboundManipulation_RequestType, IPInboundManipulation_RemoveFromLeft, IPInboundManipulation_RemoveFromRight, IPInboundManipulation_LeaveFromRight, IPInboundManipulation_Prefix2Add, IPInboundManipulation_Suffix2Add; [\IPInboundManipulation] For a detailed description of this table, see ''Configuring IP-to- IP Inbound Manipulations'' on page 545. IP to IP Outbound Manipulation Table Web: IP to IP Outbound...
  • Page 975  User A sends a REGISTER message to SAS with transport=TCP.  User B sends an INVITE message to A using SAS. In this scenario, the SAS application forwards the INVITE Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 976 Mediant 800B Gateway and E-SBC Parameter Description request using the TCP connection that User A initially opened with the REGISTER message. Web/EMS: Enable Record-Route Determines whether the device's SAS application adds the SIP CLI: record-route Record-Route header to SIP requests. This ensures that SIP...
  • Page 977 (in the SIP user part), it forwards the INVITE to the default gateway (configured by the parameter SASDefaultGatewayIP), i.e., the device itself, which sends the call directly to the PSTN. This is Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 978 Mediant 800B Gateway and E-SBC Parameter Description important for routing emergency numbers such as 911 (in North America) directly to the PSTN. This is applicable to SAS operating in Normal and Emergency modes. Up to four emergency numbers can be defined, where each number can be up to four digits.

  • Page 979: Ip Media Parameters

    The application server sends a regular SIP INVITE message with a SIP URI that includes this identifier string and a “play=” parameter that identifies the necessary announcement. The default is ‘annc’. Example 1: INVITE sip: annc@10.2.3.4;play=http://localhost/1. Example 2: INVITE sip: annc@10.2.3.4;play=http://10.2.3.4/Annc/ello.wav. Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 980 Mediant 800B Gateway and E-SBC Parameter Description Web: Transcoding ID Defines the Transcoding identification string (up to 16 [TranscodingID] characters) used for identifying an incoming Transcoding call. The default is ‘trans’. For more information on Transcoding, see NetAnn Interface. Conferencing Parameters Web/EMS: Conference ID Defines the Conference Identification string.
  • Page 981 Defines the minimum gain (in dB) by the AGC when EMS: Minimal Gain activated. CLI: AGC-min-gain The range is 0 to -31. The default is -20. [AGCMinGain] Note: For this parameter to take effect, a device reset is Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 982 Mediant 800B Gateway and E-SBC Parameter Description required. Web: AGC Maximum Gain Defines the maximum gain (in dB) by the AGC when EMS: Maximal Gain activated. CLI: AGC-max-gain The range is 0 to 18. The default is 15. [AGCMaxGain] Note: For this parameter to take effect, a device reset is required.

  • Page 983: Services

    LDAP- or RADIUS-based management-user login CLI: configure system > authentication. mgmt-auth > use-local-  [0] When No Auth Server Defined = (Default) When no users-db LDAP/RADIUS server is configured (or as fallback if the server is Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 984: Radius Parameters

    Mediant 800B Gateway and E-SBC Parameter Description [MgmtLocalDatabaseBe inaccessible). havior]  [1] Always = Always first verify the user's credentials in the Web Users table, and if not found, then search the LDAP/RADIUS server. Web: Behavior upon Defines the device's response when a connection timeout occurs with Authentication Server the LDAP/RADIUS server.
  • Page 985 [0] Absolute Expiry Timer = When you access a Web page, the timeout doesn't reset, instead it continues decreasing.  [1] Reset Timer Upon Access = (Default) Upon each access to a Web page, the timeout always resets (reverts to the initial value Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 986: Ldap Parameters

    Mediant 800B Gateway and E-SBC Parameter Description configured by RadiusLocalCacheTimeout). Web: Password Local Defines the time (in seconds) the locally stored username and Cache Timeout password (verified by the RADIUS server) are valid. When this time CLI: local-cache-timeout expires, the username and password become invalid and a must be re- [RadiusLocalCacheTime verified with the RADIUS server.
  • Page 987 MSLDAPPrimaryKey or MSLDAPSecondaryKey parameter, then the device queries the AD for the destination number in this private attribute name; otherwise, this parameter is not used as a search key. The default is "msRTCSIP-PrivateLine". Version 6.8 Mediant 800B Gateway and E-SBC...
  • Page 988 Mediant 800B Gateway and E-SBC Parameter Description Web: MS LDAP DISPLAY Defines the attribute name that represents the Calling Name in the Name Attribute Name AD for LDAP queries based on calling number. CLI: ldap-display-nm-attr The valid value is a string of up to 49 characters. The default is [MSLDAPDisplayNameAtt "displayName".

  • Page 989: Least Cost Routing Parameters

    Cost Group is configured with a name, fixed call connection charge, Provisioning > Cost Group and a call rate (charge per minute). CLI: configure voip > [ CostGroupTable ] services least-cost-routing FORMAT CostGroupTable_Index = cost-group CostGroupTable_CostGroupName, [CostGroupTable] CostGroupTable_DefaultConnectionCost, CostGroupTable_DefaultMinuteCost; [ \CostGroupTable ] Version 6.8 Mediant 800B Gateway and E-SBC...

  • Page 990: Call Setup Rules Parameters

    Mediant 800B Gateway and E-SBC Parameter Description For example: CostGroupTable 2 = "Local Calls", 2, 1; Note: For a detailed description of this table, see ''Configuring Cost Groups'' on page 231. Web: Cost Group > Time This table parameter configures time bands and associates them with Band Table Cost Groups.

  • Page 991: 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 992 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 993: 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 994 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 995 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 996 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10286...

  • Page 997: 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 58-1: Technical Specifications Function Specification Telephony Interfaces ...
  • Page 998 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 Transport Mediation SIP over UDP to SIP over TCP or SIP over TLS, IPv4 to IPv6 ,v.34...
  • Page 999 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 1000 User's Manual Ver. 6.8 www.audiocodes.com...

Table of Contents