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

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

Advertisement

Quick Links

Download this manual See also: User Manual, Quick Manual
User's Manual
AudioCodes Mediant™ Family of Media Gateways & Session Border Controllers
Mediant 800B
Gateway & E-SBC
Version 7.2

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 800B

Summary of Contents for AudioCodes Mediant 800B

  • Page 1 User’s Manual AudioCodes Mediant™ Family of Media Gateways & Session Border Controllers Mediant 800B Gateway & E-SBC Version 7.2...

  • Page 3: Table Of Contents

    Configuring Web Session and Access Settings ............. 70 Changing Login Password for Administrator and Monitor Users ......71 Configuring Secured (HTTPS) Web ............... 72 Web Login Authentication using Smart Cards ............73 Configuring Web and Telnet Access List ............... 73 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 4 Mediant 800B Gateway & E-SBC CLI-Based Management ..................75 Getting Familiar with CLI ..................75 7.1.1 Understanding Configuration Modes ............... 75 7.1.2 Using CLI Shortcuts ....................76 7.1.3 Common CLI Commands ..................78 7.1.4 Configuring Tables through CLI ................79 7.1.5...
  • Page 5 12.12.1 Configuring Native VLAN for OSN Server .............162 12.12.2 Disabling Internal Switch Port for OSN ..............163 12.13 Multiple Routers Support ..................163 13 Security ......................165 13.1 Configuring Firewall Settings ................165 13.2 Configuring General Security Settings ..............169 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 6 Mediant 800B Gateway & E-SBC 13.3 Intrusion Detection System .................. 170 13.3.1 Enabling IDS ......................170 13.3.2 Configuring IDS Policies ..................171 13.3.3 Assigning IDS Policies ...................175 13.3.4 Viewing IDS Alarms ....................177 14 Media ........................ 179 14.1 Configuring Voice Settings ................... 179 14.1.1 Configuring Voice Gain (Volume) Control .............179...
  • Page 7 15.7.3.1 Configuring HTTP Proxy Hosts ............. 287 15.7.4 Configuring an HTTP-based EMS Service ............289 15.8 E9-1-1 Support for Microsoft Skype for Business ..........291 15.8.1 About E9-1-1 Services ...................291 15.8.2 Microsoft Skype for Business and E9-1-1 .............292 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 8 15.8.2.2 Adding ELINs to the Location Information Server ......... 294 15.8.2.3 Passing Location Information to the PSTN Emergency Provider ..295 15.8.3 AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN .....296 15.8.3.1 Detecting and Handling E9-1-1 Calls ............ 296 15.8.3.2 Pre-empting Existing Calls for E9-1-1 Calls ..........
  • Page 9 23.3 Configuring a Gateway Routing Policy Rule ............499 23.4 Alternative Routing for Tel-to-IP Calls ..............501 23.4.1 IP Destinations Connectivity Feature ..............501 23.4.2 Alternative Routing Based on IP Connectivity ............502 23.4.3 Alternative Routing Based on SIP Responses ............504 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 10 Mediant 800B Gateway & E-SBC 23.4.4 Alternative Routing upon SIP 3xx with Multiple Contacts ........507 23.4.5 PSTN Fallback .......................508 23.5 Alternative Routing for IP-to-Tel Calls ..............508 23.5.1 Alternative Routing to Trunk upon Q.931 Call Release Cause Code ....508 23.5.2 Alternative Routing to an IP Destination upon a Busy Trunk ........510 23.5.3 Alternative Routing upon ISDN Disconnect ............512...
  • Page 11 27.13.3.2 Call Termination before Call Establishment .......... 607 27.13.3.3 Ring Detection Timeout ................. 607 27.14 Remote PBX Extension between FXO and FXS Devices ........607 27.14.1 Dialing from Remote Extension (Phone at FXS) ...........608 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 12 Mediant 800B Gateway & E-SBC 27.14.2 Dialing from PBX Line or PSTN ................609 27.14.3 Message Waiting Indication for Remote Extensions ..........609 27.14.4 Call Waiting for Remote Extensions ..............609 27.14.5 FXS Gateway Configuration ..................610 27.14.6 FXO Gateway Configuration ..................611 Session Border Controller Application..............613 28 SBC Overview ....................
  • Page 13 37.5 Call Forking ......................723 37.5.1 Initiating SIP Call Forking ..................723 37.5.2 Configuring SIP Forking Initiated by SIP Proxy .............723 37.5.3 Configuring Call Forking-based IP-to-IP Routing Rules ........724 37.6 Call Survivability ....................724 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 14 Mediant 800B Gateway & E-SBC 37.6.1 Enabling Auto-Provisioning of Subscriber-Specific Information of BroadWorks Server for Survivability ......................724 37.6.2 Configuring BroadSoft's Shared Phone Line Call Appearance for Survivability ...725 37.6.3 Configuring Call Survivability for Call Centers ............727 37.6.4 Enabling Survivability Display on Aastra IP Phones ..........729 37.7 Alternative Routing on Detection of Failed SIP Response ........
  • Page 15 46.2.3.1 Installing License Key through Web Interface ........800 46.2.3.2 Installing License Key through CLI ............801 46.3 Upgrading SBC Capacity Licenses by License Pool Manager Server ....802 46.4 Software Upgrade Wizard ..................804 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 16 Mediant 800B Gateway & E-SBC 47 Backing Up and Loading Configuration File ..........811 48 Automatic Provisioning .................. 813 48.1 Automatic Configuration Methods ................ 813 48.1.1 DHCP-based Provisioning ..................813 48.1.1.1 Provisioning from HTTP Server using DHCP Option 67 ....... 814 48.1.1.2 Provisioning from TFTP Server using DHCP Option 66 .......
  • Page 17 60.2.1 Syslog Message Format ..................930 60.2.1.1 Event Representation in Syslog Messages .......... 933 60.2.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ..934 60.2.1.3 Syslog Fields for Answering Machine Detection (AMD) ....... 935 60.2.1.4 SNMP Alarms in Syslog Messages ............935 60.2.2 Enabling Syslog .....................936...
  • Page 18 Mediant 800B Gateway & E-SBC 60.2.4 Configuring Syslog Debug Level ................936 60.2.5 Configuring Reporting of Management User Activities ..........937 60.2.6 Viewing Syslog Messages ..................939 60.3 Configuring Debug Recording ................940 60.3.1 Configuring the Debug Recording Server Address ..........940 60.3.2 Collecting Debug Recording Messages ..............941 60.3.3 Debug Capturing on Physical VoIP Interfaces ............942...
  • Page 19 67.11.9.2 Tone Detection Parameters ..............1175 67.11.9.3 Metering Tone Parameters ..............1176 67.11.10 Telephone Keypad Sequence Parameters ........... 1177 67.11.11 FXO and FXS Parameters ................1181 67.11.12 Trunk Groups and Routing Parameters ............1185 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 20 Mediant 800B Gateway & E-SBC 67.11.13 IP Connectivity Parameters ................1192 67.11.14 Alternative Routing Parameters ..............1194 67.11.15 Number Manipulation Parameters ..............1196 67.12 SBC Parameters ....................1207 67.12.1 Supplementary Services ..................1223 67.13 IP Media Parameters ..................1223 67.14 Services ......................1228 67.14.1 SIP-based Media Recording Parameters ............

  • Page 21: Weee Eu Directive

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

  • Page 22: Related Documentation

    Mediant 800B Gateway & E-SBC Related Documentation Manual Name SIP Release Notes Mediant 800B Gateway and E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SBC Design Guide Recommended Security Guidelines Configuration Note...
  • Page 23 Some of the features listed in this document are available only if the relevant License Key has been purchased from AudioCodes and installed on the device. For a list of License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 24 IpProfile_SBCISUPVariant; WebLoginBlockAutoComplete; EnforcePasswordComplexity; AUPDCliScriptURL; TrunkLifeLineType. 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 25: Introduction

    Product 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 26: Typographical Conventions

    Mediant 800B Gateway & E-SBC Note: For maximum call capacity figures, see 'Channel Capacity' on page 1239. 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.

  • Page 27: Sbc Application

    The Media Realm can be associated with the SIP entity, by assigning the Media Realm to the IP Group of the SIP entity, or by assigning it to the SIP Interface associated with the SIP entity. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 28 Mediant 800B Gateway & E-SBC Configuration Terms Description The SRD is a logical representation of your entire SIP-based VoIP network (Layer 5) containing groups of SIP users and servers. The SRD is in effect, the foundation of your configuration to which all other previously mentioned configuration entities are associated.
  • Page 29 401) is typically relevant for INVITE messages forwarded by the device to a "serving" IP Group. Registration is for REGISTER messages, which are initiated by the device on behalf of the "serving" SIP entity. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 30 Mediant 800B Gateway & E-SBC The associations between the configuration entities are summarized in the following figure: Figure 1-1: Association of Configuration Entities The main configuration entities and their involvement in the call processing is summarized in following figure. The figure is used only as an example to provide basic understanding of the configuration terminology.

  • Page 31: Gateway Application

    SRD topology, the device automatically assigns the SRD to newly created configuration entities. Thus, in such scenarios, there is no need to get involved with SRD configuration. Multiple SRDs are required only for multi-tenant deployments. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 32 Mediant 800B Gateway & E-SBC Configuration Terms Description IP Profiles The IP Profile is an optional configuration entity that defines a wide range of call settings for a specific SIP entity (IP Group). The IP Profile includes signaling and media related settings, for example, jitter buffer, silence suppression, voice coders, fax signaling method, SIP header support (local termination if not supported), and media security method.

  • Page 33: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 35: 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 36 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 37: 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 24 (255.255.255.0) Default Gateway 192.168.0.1 Underlying Device vlan 1 Interface Name O+M+C Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 38 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 39: Configuring Voip Lan Interface For Oamp

    Ethernet cable. Change the IP address and subnet mask of your computer to correspond with the default OAMP IP address and subnet mask of the device. Access the Web interface: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 40 Mediant 800B Gateway & E-SBC On your computer, start a Web browser and in the URL address field, enter the default 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").

  • Page 41: Cli

    (config-network)# 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 42 Mediant 800B Gateway & E-SBC Exit the IP Interfaces table: (network-if-0)# exit Exit the Network configuration mode: (config-network)# 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 43: Management Tools

    Part II Management Tools...

  • Page 45: Introduction

    Configuration ini file - see 'INI File-Based Management' on page 95 Note: • Some configuration settings can only be done using a specific management tool. • For a list and description of all the configuration parameters, see 'Configuration Parameters Reference' on page 973. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 46 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 47: Web-Based Management

    (Versions 5.02 or later) • Google Chrome (Version 50 or later)  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 7.2 Mediant 800B Gateway & E-SBC...

  • Page 48: Accessing The Web Interface

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

  • Page 49: Areas Of The Gui

    The areas of the Web interface's GUI are shown in the figure below and described in the subsequent table. Figure 6-2: Main Areas of the Web Interface GUI Table 6-1: Description of the Web GUI Areas Item # Description Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 50 Mediant 800B Gateway & E-SBC Item # Description Company logo. Menu bar containing the menus. Toolbar providing frequently required command buttons.  Save: Saves configuration changes to the device's flash memory (without resetting the device). If you make a configuration change, the button is surrounded by a red-colored border as a reminder to save your settings to flash memory, by clicking the button.

  • Page 51: Accessing Configuration Pages From Navigation Tree

    The items of the Navigation tree depend on the menu-tab combination, selected from the menu bar and tab bar, respectively. The menus and their respective tabs are listed below:  Setup menu: • IP Network tab • Signaling & Media tab Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 52 Mediant 800B Gateway & E-SBC • Administration tab  Monitor menu: Monitor tab  Troubleshoot menu: Troubleshoot tab When you open the Navigation tree, folders containing commonly required items are opened by default, allowing quick access to their pages. Items that open pages containing tables provide the following indications in the Navigation tree: ...

  • Page 53: Configuring Stand-Alone Parameters

    Modify the parameter's value as desired. Click Apply; the changes are saved to the device's volatile memory (RAM). Save the changes to the device's non-volatile memory (flash): • If a device reset is not required: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 54: Configuring Table Parameters

    Mediant 800B Gateway & E-SBC On the toolbar, click Save; a confirmation message box appears: Figure 6-4: Save Configuration Confirmation Box Click Yes to confirm; the changes are save to flash memory. • If a device reset is required: On the toolbar, click Reset; the Maintenance Actions page opens.

  • Page 55: Adding Table Rows

    Configure the parameters of the row as desired. For information on configuring parameters that are assigned a value which is a row referenced from another table, see 'Assigning a Row from Another Table' on page 56. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 56: Modifying Table Rows

    Mediant 800B Gateway & E-SBC Click Apply to add the row to the table or click Cancel to ignore your configuration. If the Save button is surrounded by a red border, you must save your settings to flash memory, otherwise they are discarded if the device resets (without a save to flash) or powers off.

  • Page 57: Deleting Table Rows

    If you enter a valid value, the colored border is removed from the field. If you leave the parameter at the invalid value and click Apply, the parameter reverts to its previous value.  Mandatory parameters assigned a value which is a row referenced from another table: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 58 Mediant 800B Gateway & E-SBC • Adding a row: If you have not assigned the parameter with a row from another table and you click Apply, an error message is displayed at the bottom of the dialog box, as shown in the example below: If you click Cancel, the dialog box closes and the row is not added to the table.

  • Page 59: Viewing Table Rows

    You can sort table rows by any column and in ascending order (e.g., 1, 2 and 3 / a, b, and c) or descending order (e.g., 3, 2, and 1 / c, b, and a). By default, most tables are sorted by the Index column and in ascending order. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 60: Changing Index Position Of Table Rows

    Mediant 800B Gateway & E-SBC  To sort table rows by column: Click the name of the column by which you want to sort the table rows; the up-down arrows appear alongside the column name and the up button is displayed in a darker...

  • Page 61: Searching Table Entries

    The search key for a parameter value can include alphanumerics and certain characters (see note below). The key can be a complete value or a partial value. The following are examples of search keys for searching values:  "10.102.1.50" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 62 Mediant 800B Gateway & E-SBC  "10.15."  "abc.com"  "ITSP ABC" When the device completes the search, it displays a list of found results based on the search key. Each possible result, when clicked, opens the page on which the parameter or value is located.

  • Page 63: Creating A Login Welcome Message

    When you hover your mouse over a parameter's field, a pop-up appears with a short description of the parameter, as shown in the following example: Figure 6-16: Viewing Context-Sensitive Help for a Parameter Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 64: Logging Off The Web Interface

    Mediant 800B Gateway & E-SBC 6.1.10 Logging Off the Web Interface The following procedure describes how to log off the Web interface.  To log off the Web interface: On the menu bar, from the 'Admin' drop-down list, click Log Out; the following...

  • Page 65: Configuring Management User Accounts

    Access Settings' on page 70). By default, the device is pre-configured with the following two user accounts: Table 6-6: Default User Accounts User Level Username Password (Case-Sensitive) (Case-Sensitive) Security Administrator "Admin" "Admin" Monitor "User" "User" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 66 Mediant 800B Gateway & E-SBC Note: • For security, it's recommended that you change the default username and password of the default users. • To restore the device to the default users (and with their default usernames and passwords), configure the ini file ResetWebPassword parameter to 1. If you have configured any other accounts, they are deleted.
  • Page 67 New = (Default) User is required to change its password on the next login. When the user logs in to the Web interface, the user is immediately prompted to change the current password. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 68 Mediant 800B Gateway & E-SBC Parameter Description  Valid = User can log in to the Web interface as normal.  Failed Login = The 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 Session and Access Settings' on page 70).

  • Page 69: Displaying Login Information Upon Login

    Click Apply. Once enabled, each time you login to the device, the Login Information window is displayed, as shown in the example below: Figure 6-20: Login Information Window To close the window, click Close. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 70: Viewing Logged-In User Information

    Mediant 800B Gateway & E-SBC Viewing Logged-In User Information The username of the currently logged in user is displayed in the top-right corner of the Web interface. If you click the username (e.g., "Admin"), a pop-up callout appears: Figure 6-21: Logged-in User Information The following information is displayed: ...

  • Page 71: Changing Login Password For Administrator And Monitor Users

    Management User Accounts' on page 65). • You can only change the password if the duration configured in the 'Password Change Interval' has elapsed (see 'Configuring Web Session and Access Settings' on page 70). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 72: Configuring Secured (Https) Web

    Mediant 800B Gateway & E-SBC  To change the login password: Open the Web Settings page (Setup menu > Administration tab > Web & CLI folder > Web Settings). Figure 6-24: Changing Login Password for Administrator and Monitor User Levels In the 'Current Password' field, type in your current login password.

  • Page 73: Web Login Authentication Using Smart Cards

    This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative.  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader.
  • Page 74 Mediant 800B Gateway & E-SBC  To add IP addresses to the Access List: Open the Access List table (Setup menu > Administration tab > Web & CLI folder > Access List). Figure 6-25: Access List - Adding IP Address In the 'Add an authorized IP address' field, configure an IP address, and then click Add New Entry;...

  • Page 75: Cli-Based Management

    Password: <Enable mode password> The Enable mode prompt is "#". Note: The default password for accessing the Enable mode is "Admin" (case- sensitive). To change this password, use the CLIPrivPass ini file parameter. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 76: Using Cli Shortcuts

    Mediant 800B Gateway & E-SBC The Enable mode groups the configuration commands under the following command sets: • configure network: Contains IP network-related commands (e.g., interface and dhcp-server): # configure network (config-network)# • configure voip: Contains voice-over-IP related commands (e.g., ip-group, sbc,...
  • Page 77 Space Bar at the --More- Displays the next screen of output. You can configure the size of the -prompt displayed output, as described in 'Configuring Displayed Output Lines in CLI Terminal Window' on page 85. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 78: Common Cli Commands

    Mediant 800B Gateway & E-SBC 7.1.3 Common CLI Commands The following table contains descriptions of common CLI commands. Table 7-2: Common CLI Commands Command Description Provides a way to execute commands in other command sets without taking the time to exit the current command set. The following example shows the do...

  • Page 79: Configuring Tables Through Cli

    Failure reason of a run command. The failure message is identical to the notification failure message sent by Syslog. For example, an invalid Syslog server IP address is displayed in the CLI as follows: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 80: Enabling Cli

    Mediant 800B Gateway & E-SBC (logging)# syslog-ip 1111.1.1.1 Parameter 'SyslogServerIP' does NOT accept the IP-Address: 1111.1.1.1, illegal IPAddress. Configuration failed Command Failed!  "Invalid command" message: The command may not be valid in the current command mode, or you may not have entered sufficient characters for the command to be recognized.

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

    CLI Settings), and then do the following: From the 'Enable SSH Server' drop-down list, select Enable. Paste the public key that you copied in Step 1.d into the 'Admin Key' field, as shown below: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 82 Mediant 800B Gateway & E-SBC For additional security, you can configure the 'Public Key' field to Enable. This ensures that SSH access is only possible by using the RSA key and not by username and password. Configure the other SSH parameters as required. For a description of these parameters, see 'SSH Parameters' on page 1017.

  • Page 83: Configuring Maximum Telnet/Ssh Sessions

    Establish a Telnet or SSH session using the device's OAMP IP address. 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 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 84: Viewing Current Cli Sessions

    Mediant 800B Gateway & E-SBC At the Password prompt, type the password, and then press Enter: Password: Admin At the prompt, type the following, and then press Enter: > enable At the prompt, type the password again, and then press Enter:...

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

    When this mode is configured, each time you change the height of the terminal window using your mouse (i.e., dragging one of the window's borders or corners), the number of displayed output command lines is changed accordingly. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 86 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 87: Snmp-Based Management

    8. SNMP-Based Management SNMP-Based Management The device provides an embedded SNMP agent that lets you manage it using AudioCodes Element Management System (EMS) or a third-party SNMP manager. The SNMP agent supports standard and proprietary Management Information Base (MIBs). All supported MIB files are supplied to customers as part of the release.
  • Page 88 Mediant 800B Gateway & E-SBC Note: • SNMP community strings are applicable only to SNMPv1 and SNMPv2c; SNMPv3 uses username-password authentication along with an encryption key (see 'Configuring SNMP V3 Users' on page 92). • You can enhance security by configuring Trusted Managers (see 'Configuring SNMP Trusted Managers' on page 91).

  • Page 89: Configuring Snmp Trap Destinations With Ip Addresses

    SNMPv3 destination. By default, traps are sent unencrypted using SNMPv2. The following procedure describes how to configure SNMP trap destinations through the Web interface. You can also configure it through ini file (SNMPManager) or CLI (configure system > snmp trap-destination). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 90 Mediant 800B Gateway & E-SBC  To configure SNMP trap destinations: Open the SNMP Trap Destinations table (Setup menu > Administration tab > SNMP folder > SNMP Trap Destinations). Figure 8-3: SNMP Trap Destinations Table Configure the SNMP trap manager according to the table below.

  • Page 91: Configuring An Snmp Trap Destination With Fqdn

    (as long as the community string is correct). The following procedure describes how to configure SNMP Trusted Managers through the Web interface. You can also configure it through ini file (SNMPTrustedMgr_x) or CLI (configure system > snmp settings > trusted-managers). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 92: Enabling Snmp Traps For Web Activity

    Mediant 800B Gateway & E-SBC  To configure SNMP Trusted Managers: Open the SNMP Trusted Managers table (Setup menu > Administration tab > SNMP folder > SNMP Trusted Managers). Figure 8-4: SNMP Trusted Managers Table Configure an IP address (in dotted-decimal notation) for one or more SNMP Trusted Managers.
  • Page 93 [0] None (default)  [1] DES [SNMPUsers_PrivProtocol]  [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 password Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 94 Mediant 800B Gateway & E-SBC Parameter Description auth-key or long hex string. Keys are always persisted as long hex strings and keys are localized. [SNMPUsers_AuthKey] Privacy Key Privacy key. Keys can be entered in the form of a text password or long hex string.

  • Page 95: Ini File-Based Management

    An exception is Index fields, which are mandatory. • The Format line must end with a semicolon ";".  Data line(s): Contain the actual values of the columns (parameters). The values are interpreted according to the Format line. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 96 Mediant 800B Gateway & E-SBC • The first word of the Data line must be the table’s string name followed by the Index field. • Columns must be separated by a comma ",". • A Data line must end with a semicolon ";".

  • Page 97: General Ini File Formatting Rules

    (!), for example: !CpMediaRealm 1 = "ITSP", "Voice", "", 60210, 2, 6030, 0, "", ""; • To restore the device to default settings through the ini file, see 'Restoring Factory Defaults' on page 833. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 98: 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 99 $0$<plain text>: Password can be entered in plain text; useful for configuring a new password. When the ini file is loaded to the device and then later saved from the device to a PC, the password is displayed obscured (i.e., $1$<obscured password>). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 100: Ini Viewer And Editor Utility

    Mediant 800B Gateway & E-SBC INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any Windows-based PC.

  • Page 101: General System Settings

    Part III General System Settings...

  • Page 103: Configuring Ssl/Tls Certificates

    You can configure the device to check whether a peer's certificate has been revoked, using the OCSP. When OCSP is enabled, the device queries the OCSP server for revocation information whenever a Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 104 Mediant 800B Gateway & E-SBC peer certificate is received (IPSec, TLS client mode, or TLS server mode with mutual authentication). Note: • The device does not query OCSP for its own certificate. • Some PKIs do not support OCSP, but generate Certificate Revocation Lists (CRLs).
  • Page 105 Note: Each row must be configured with a unique index. [TLSContexts_Index] Name Defines an arbitrary name to easily identify the row. name The valid value is a string of up to 31 characters. [TLSContexts_Name] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 106 Mediant 800B Gateway & E-SBC Parameter Description TLS Version Defines the supported SSL/TLS protocol version. Clients attempting to communicate with the device using a different tls-version TLS version are rejected. [TLSContexts_TLSVersion]  [0] Any - Including SSLv3 = (Default) SSL 3.0 and all TLS versions are supported.

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

    From the 'Signature Algorithm' drop-down list, select the hash function algorithm (SHA-1, SHA-256, or SHA-512) with which to sign the certificate. Fill in the rest of the request fields according to your security provider's instructions. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 108 Mediant 800B Gateway & E-SBC Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-1: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request.
  • Page 109 The certificate replacement process can be repeated whenever necessary (e.g., the new certificate expires). • You can also load the device certificate through the device's Automatic Provisioning mechanism, using the HTTPSCertFileName ini file parameter. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 110: Viewing Certificate Information

    Mediant 800B Gateway & E-SBC 10.3 Viewing Certificate Information You can view information of TLS certificates installed on the device for each TLS Context, as described in the following procedure.  To view certificate information: Open the TLS Contexts table (see 'Configuring TLS Certificate Contexts' on page 103).

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

    After the files successfully load to the device, save the configuration with a device reset. Verify that the private key is correct: Open the TLS Contexts table. Select the required TLS Context index row. Click the Certificate Information link located below the table. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 112: Generating Private Keys For Tls Contexts

    Mediant 800B Gateway & E-SBC Make sure that the 'Private key' field displays "OK"; otherwise, consult with your security administrator. Figure 10-5: Verifying Private Key 10.5 Generating Private Keys for TLS Contexts You can let the device generate the private key for a TLS Context. The private key can be generated for CSR or self-signed certificates.

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

    Certificate link located below the table; the Context Certificates page appears. Under the Certificate Signing Request group, in the 'Subject Name [CN]' field, enter the fully-qualified DNS name (FQDN) as the certificate subject. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Scroll down the page to the Generate New Private Key and Self-signed Certificate group: Figure 10-8: Generate new private key and self-signed certificate Group Click Generate Self-Signed Certificate; a message appears requesting you to confirm generation.
  • Page 115 Save certificates to a folder on your PC: Select the required certificate, click Export, and then in the Export Certificate dialog box, browse to the folder on your PC where you want to save the file and click Export. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 116: Configuring Mutual Tls Authentication

    Mediant 800B Gateway & E-SBC 10.8 Configuring Mutual TLS Authentication This section describes how to configure mutual (two-way) TLS authentication. 10.8.1 TLS for SIP Clients When Secure SIP (SIPS) is implemented using TLS, it is sometimes required to use two- way (mutual) authentication between the device and a SIP user agent (client).

  • Page 117: Configuring Tls Server Certificate Expiry Check

    Open the TLS Contexts table (see 'Configuring TLS Certificate Contexts' on page 103). Select the required TLS Context index row, and then click the Change Certificate link located below the table; the Context Certificates page appears. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 118 Mediant 800B Gateway & E-SBC Scroll down the page to the TLS Expiry Settings group: Figure 10-12: TLS Expiry Settings Group In the 'TLS Expiry Check Start' field, enter the number of days before the installed TLS server certificate is to expire when the device sends an SNMP trap event to notify of this.

  • Page 119: Date And Time

    In the 'NTP Authentication Key Identifier' field, configure the NTP authentication key identifier. • In the 'NTP Authentication Secret Key' field, configure the secret authentication key shared between the device and the NTP server. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 120: Configuring Date And Time Manually

    Mediant 800B Gateway & E-SBC Verify that the device has received the correct date and time from the NTP server. The date and time is displayed in the 'UTC Time' read-only field under the Time Zone group. Note: If the device does not receive a response from the NTP server, it polls the NTP server for 10 minutes.

  • Page 121: Configuring Daylight Saving Time

    Figure 11-4: Configuring Daylight Savings From the 'Day Light Saving Time' (DayLightSavingTimeEnable) drop-down list, select Enable. From the 'DST Mode' drop-down list, select the range type for configuring the start and end dates for DST: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 122 Mediant 800B Gateway & E-SBC • Day of year: The range is configured by exact date (day number of month), for example, from March 30 to October 30. If 'DST Mode' is set to Day of year, in the 'Start Time' (DayLightSavingTimeStart) and 'End Time' (DayLightSavingTimeEnd) drop-down lists, configure the period for which DST is relevant.

  • Page 123: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 125: Network

    The areas of the Network view is shown in the example below and described in the subsequent table. Note: The below figure is used only as an example; your device may show different Ethernet Groups and Ethernet ports. Figure 12-1: Network View (Example) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 126 Mediant 800B Gateway & E-SBC Table 12-1: Description of Network View Item # Description Configures and displays IP Interfaces. The IP Interface appears as an icon, displaying the application type ("OCM" for OAMP, "C" for Control, and "M" for Media), row index number, name, and IP address, as shown in the...
  • Page 127 To open the Ethernet Groups table, click any Ethernet Group icon, and then from the drop- down menu, choose View Ethernet Group List. You can then view and edit all the Ethernet Groups in the table. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 128: Configuring Physical Ethernet Ports

    Mediant 800B Gateway & E-SBC Item # Description Configures and displays the device's Ethernet ports. To configure an Ethernet port: Click the required port icon, and then from the drop-down menu, choose Edit; the Physical Ports table opens with a dialog box for editing the Ethernet port.
  • Page 129 By default, the value is "User Port #<row index>". port-description [PhysicalPortsTable_PortDescription] Note: Each row must be configured with a unique name. Mode (Read-only) Displays the mode of the port.  mode [0] Disable  [1] Enable (default) [PhysicalPortsTable_Mode] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 130: Configuring Ethernet Port Groups

    Mediant 800B Gateway & E-SBC Parameter Description Speed and Duplex Defines the speed and duplex mode of the port.  speed-duplex [0] 10BaseT Half Duplex  [1] 10BaseT Full Duplex [PhysicalPortsTable_SpeedDuplex]  [2] 100BaseT Half Duplex  [3] 100BaseT Full Duplex ...
  • Page 131 Click Apply, and then save your settings to flash memory. Table 12-3: Ethernet Groups Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number for the table row. Name (Read-only) Displays the Ethernet Group number. group [EtherGroupTable_Group] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 132: Configuring Underlying Ethernet Devices

    Mediant 800B Gateway & E-SBC Parameter Description Mode Defines the mode of operation of the ports in the Ethernet Group. This applies only to Ethernet Groups containing two ports. mode  [2] 1RX/1TX = (Default) At any given time, only one of the ports in [EtherGroupTable_Mode] the Ethernet Group transmits and receives packets.
  • Page 133 Open the Ethernet Devices table (Setup menu > IP Network tab > Core Entities folder > Ethernet Devices). Click New; the following dialog box appears: Configure an Ethernet Device according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 134 Mediant 800B Gateway & E-SBC Table 12-4: Ethernet Devices Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [DeviceTable_Index] Note: Each row must be configured with a unique index. Name Defines a name for the Ethernet Device. The name is used to...

  • Page 135: Configuring Ip Network Interfaces

    Ethernet connectivity between the two devices. For more information on HA and the Maintenance interface, see Configuring High Availability on page 743.  IP address (IPv4 or IPv6) and subnet mask (prefix length) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 136 Mediant 800B Gateway & E-SBC  To configure Quality of Service (QoS), see 'Configuring the QoS Settings' on page 154.  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 ...
  • Page 137 VLAN associated with a physical Ethernet port (Ethernet underlying-dev Group). To configure Ethernet Devices, see Configuring Underlying [InterfaceTable_UnderlyingDevi Ethernet Devices on page 132. By default, no value is defined. Note: The parameter is mandatory. IP Address Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 138 Mediant 800B Gateway & E-SBC Parameter Description Interface Mode Defines the method that the interface uses to acquire its IP address. mode  [3] IPv6 Manual Prefix = IPv6 manual prefix IP address [InterfaceTable_InterfaceMode] assignment. The IPv6 prefix (higher 64 bits) is set manually while the interface ID (the lower 64 bits) is derived from the device's MAC address.

  • Page 139: Assigning Ntp Services To Application Types

    Syslog server and falls back to a "safe mode", using a single interface without VLANs. Ensure that you view the Syslog messages that the device sends in system startup to see if any errors occurred. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 140: Networking Configuration Examples

    Mediant 800B Gateway & E-SBC 12.5.3 Networking Configuration Examples This section provides configuration examples of networking interfaces. 12.5.3.1 One VoIP Interface for All Applications This example describes the configuration of a single VoIP interface for all applications: IP Interfaces table: Configured with a single interface for OAMP, Media and Control:...

  • Page 141: Voip Interfaces For Combined Application Types

    For packets sent with DiffServ value of 26, set VLAN priority to 4 ♦ For packets sent with DiffServ value of 10, set VLAN priority to 2 • Layer-3 QoS values are assigned: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 142: Voip Interfaces With Multiple Default Gateways

    Mediant 800B Gateway & E-SBC ♦ For Media Service class, the default DiffServ value is set to 46 ♦ For Control Service class, the default DiffServ value is set to 40 ♦ For Gold Service class, the default DiffServ value is set to 26 ♦...
  • Page 143 [StaticRouteTable_Description] Destination Defines the IP address of the destination host/network. The destination can be a single host or a whole subnet, depending on destination the prefix length configured for this routing rule. [StaticRouteTable_Destination] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 144: Configuration Example Of Static Ip Routes

    Mediant 800B Gateway & E-SBC Parameter Description Prefix Length Defines the Classless Inter-Domain Routing (CIDR)-style representation of a dotted-decimal subnet notation of the prefix-length destination host/network. The CIDR-style representation uses a [StaticRouteTable_PrefixLength] suffix indicating the number of bits that are set in the dotted- decimal format.

  • Page 145: Troubleshooting The Static Routes Table

    The IP address specified in the 'Gateway' field is unreachable from the IP network interface associated with the static route.  The same destination has been configured in two different static routing rules.  More than 30 static routes have been configured. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 146: Network Address Translation Support

    Mediant 800B Gateway & E-SBC Note: If a static route is required to access OAMP applications (for remote management, for example) and the route is not configured correctly, the route is not added and the device is not accessible remotely. To restore connectivity, the device must be accessed locally from the OAMP subnet and the required routes be configured.

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

    In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Note: The feature is applicable only to the Gateway application. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 148: Configuring Nat Translation Per Ip Interface

    Mediant 800B Gateway & E-SBC 12.7.1.2 Configuring NAT Translation per IP Interface The NAT Translation table lets you configure up to 32 network address translation (NAT) rules for translating source IP addresses per VoIP interface (SIP control and RTP media traffic) into NAT IP addresses (global - public) when the device is located behind NAT.

  • Page 149: Remote Ua Behind Nat

    NAT firewall and the device (for whatever reason) is unable to identify NAT using its regular NAT Detection mechanism. This feature is enabled per specific calls using IP Groups. To configure this feature, use the 'Always Use Source Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Address' parameter in the IP Groups table (see 'Configuring IP Groups' on page 344). If this feature is disabled, the device's NAT detection is according to the settings of the global parameter, 'SIP NAT Detection' parameter (see below procedure).
  • Page 151 ("A No-Op Payload Format for RTP"). The IETF document defines a No-Op payload format for RTP. The draft defines the RTP payload type as dynamic. You can configure the payload type as described in the following procedure (default is 120). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 152 Mediant 800B Gateway & E-SBC  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).  To configure the No-Op packet feature: Enable the feature, using the NoOpEnable ini file parameter.
  • Page 153 716. Once a WebRTC session (WebSocket) is established for SIP signaling between the device and the WebRTC client, the client's IP address needs to be discovered by the SBC device using the ICE technique. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    12.8 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 155: Configuring Quality Of Service

    Bronze Telnet Management Bronze Management Bronze Web server (HTTP) SNMP GET/SET Management Bronze Web server (HTTPS) Management Bronze RTP traffic Media Media Premium RTCP traffic Media Media Premium T.38 traffic Media Media Premium Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 156 Mediant 800B Gateway & E-SBC Application Traffic / Network Types Class-of-Service (Priority) Control Control Premium SIP over TLS (SIPS) Control Control Premium Syslog Management Bronze SNMP Traps Management Bronze DNS client Varies according to DNS settings: Depends on traffic type: ...

  • Page 157: Configuring Diffserv-To-Vlan Priority Mapping

    Figure 12-12: QoS Mapping Table - Add Dialog Box Configure a DiffServ-to-VLAN priority mapping rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 158: Configuring Icmp Messages

    Mediant 800B Gateway & E-SBC Table 12-18: QoS Mapping Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. Note: Each row must be configured with a unique index. Differentiated Services Defines a DiffServ value.

  • Page 159: Dns

    Open the Internal DNS table (Setup menu > IP Network tab > DNS folder > Internal DNS). Click New; the following dialog box appears: Figure 12-14: Internal DNS Table - Add Dialog Box Configure a DNS rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 160: Configuring The Internal Srv Table

    Mediant 800B Gateway & E-SBC Table 12-19: Internal DNS Table Parameter Description Parameter Description Index Defines an index number for the new table row. Note: Each row must be configured with a unique index. Domain Name Defines the host name to be translated.
  • Page 161 By default, no value is defined. [Srv2Ip_Dns1/2/3] Priority (1-3) Defines the priority of the target host. A lower value means that it is more preferred. priority-1|2|3 By default, no value is defined. [Srv2Ip_Priority1/2/3] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 162: Open Solution Network (Osn) Server

    Mediant 800B Gateway & E-SBC Parameter Description Weight (1-3) Defines a relative weight for records with the same priority. weight-1|2|3 By default, no value is defined. [Srv2Ip_Weight1/2/3] Port (1-3) Defines the TCP or UDP port on which the service is to be found.

  • Page 163: Disabling Internal Switch Port For Osn

    Using multiple router support, the device can utilize these router messages to change its next hop and establish the best path. Note: Multiple Routers support is an integral feature that doesn’t require configuration. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 164 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 165: Security

    Configuring Firewall Allowed Rules on page 755. The following procedure describes how to configure firewall rules through the Web interface. You can also configure it through ini file (AccessList) or CLI (configure network > access-list). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 166 Mediant 800B Gateway & E-SBC  To configure a firewall rule: Open the Firewall table (Setup menu > IP Network tab > Security folder> Firewall). Click New; the following dialog box appears: Figure 13-1: Firewall Table - Add Dialog Box Configure a firewall rule according to the parameters described in the table below.
  • Page 167 Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment. Byte Rate Defines the expected traffic rate (bytes per second), i.e., the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 168 Mediant 800B Gateway & E-SBC Parameter Description byte-rate allowed bandwidth for the specified protocol. In addition to this field, the 'Burst Bytes' field provides additional allowance such [AccessList_Byte_Rate] that momentary bursts of data may utilize more than the defined byte rate, without being interrupted.

  • Page 169: Configuring General Security Settings

    TLS all the way to the destination (over multiple hops), configure the 'Enable SIPS' (EnableSIPS) parameter to Enable on the Transport Settings page (Setup menu > Signaling & Media tab > SIP Definitions folder > Transport Settings): Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 170: Intrusion Detection System

    Mediant 800B Gateway & 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 171: Configuring Ids Policies

    You can also configure it through ini file or CLI:  IDS Policy table: IDSPolicy (ini file) or configure voip > ids policy (CLI)  IDS Rules table: IDSRule (ini file) or configure voip > ids rule (CLI) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 172 Mediant 800B Gateway & E-SBC  To configure an IDS Policy: Open the IDS Policies table (Setup menu > Signaling & Media tab > Intrusion Detection folder > IDS Policies); the table displays the pre-configured IDS policies: Figure 13-3: IDS Policies Table with Default Rules Click New;...
  • Page 173 Any SIP parser error  Message Policy match (see 'Configuring SIP Message Policy Rules')  Basic headers not present  Content length header not present (for TCP)  Header overflow  [3] Authentication failure = Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 174 Mediant 800B Gateway & E-SBC Parameter Description  Local authentication ("Bad digest" errors)  Remote authentication (SIP 401/407 is sent if original message includes authentication)  [4] Dialog establish failure =  Classification failure (see 'Configuring Classification Rules' on page 657). This also applies to calls rejected by the...

  • Page 175: Assigning Ids Policies

    Open the IDS Matches table (Setup menu > Signaling & Media tab > Intrusion Detection folder > IDS Matches). Click New; the following dialog box appears: Figure 13-6: IDS Matches Table - Add Dialog Box Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 176 Mediant 800B Gateway & E-SBC The figure above shows a configuration example where the IDS Policy "SIP Trunk" is applied to SIP Interfaces 1 and 2, and to all source IP addresses outside of subnet 10.1.0.0/16 and IP address 10.2.2.2.

  • Page 177: Viewing Ids Alarms

    The IP address is displayed only if the 'Threshold Scope' parameter is set to IP or IP+Port; otherwise, only the alarm is displayed.  To view the blacklist: # show voip ids blacklist active For example: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 178 Mediant 800B Gateway & E-SBC Active blacklist entries: 10.33.5.110(NI:0) remaining 00h:00m:10s in blacklist Where SI is the SIP Interface and NI is the network interface. The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This occurs only if you have configured Syslog (see 'Enabling Syslog' on page 936).

  • Page 179: Media

    To enable silence suppression using the Web interface: Open the Voice Settings page (Setup menu > Signaling & Media tab > Media folder > Voice Settings). Figure 14-2: Enabling Silence Suppression From the 'Silence Suppression' drop-down list (EnableSilenceCompression), select Enable. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 180: Configuring Echo Cancellation

    Mediant 800B Gateway & E-SBC Click Apply. 14.1.3 Configuring Echo Cancellation The device supports adaptive linear (line) echo cancellation according to G.168-2002. Echo cancellation is a mechanism that removes echo from the voice channel. Echoes are reflections of the transmitted signal.

  • Page 181: Fax And Modem Capabilities

    For a detailed description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 973.  To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Setup menu > Signaling & Media tab > Media folder > Fax/Modem/CID Settings). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 182: Fax/Modem Operating Modes

    Mediant 800B Gateway & E-SBC Configure the parameters, as required. Click Apply. 14.2.1 Fax/Modem Operating Modes The device supports two modes of operation:  Fax/modem negotiation that is not performed during the establishment of the call.  Voice-band data (VBD) mode for V.152 implementation (see 'V.152 Support' on page 194): fax/modem capabilities are negotiated between the device and the remote endpoint at the establishment of the call.

  • Page 183: Fax Relay Mode

    On the Fax/Modem/CID Settings page, configure the following optional parameters: • 'Fax Relay Redundancy Depth' (FaxRelayRedundancyDepth) • 'Fax Relay Enhanced Redundancy Depth' (FaxRelayEnhancedRedundancyDepth) • 'Fax Relay ECM Enable' (FaxRelayECMEnable) • 'Fax Relay Max Rate' (FaxRelayMaxRate) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 184 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 185: Fax / Modem Transport Mode

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

  • Page 186: Fax Fallback

    Mediant 800B Gateway & E-SBC  To configure fax / modem transparent mode: Open the Gateway General Settings page (Setup menu > Signaling & Media tab > Gateway folder > Gateway General Settings), and then from the 'Fax Signaling Method' drop-down list (IsFaxUsed), select G.711 Transport: Click Apply.
  • Page 187 Tip: When the remote (non-AudioCodes) gateway uses the G.711 coder for voice and doesn’t change the coder payload type for fax or modem transmission, it is recommended to use the Bypass mode with the following configuration: •...

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

    'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) - 'Configuring the Dynamic Jitter Buffer' on page 195. 'Silence Suppression' (EnableSilenceCompression) - 'Configuring Silence Suppression' on page 179. 'Echo Canceller' (EnableEchoCanceller) - see 'Configuring Echo Cancellation' on page 180. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Note: This mode can be used for fax, but is not recommended for modem transmission. Instead, use the Bypass (see 'Fax/Modem Bypass Mode' on page 186) or Transparent with Events modes (see 'Fax / Modem Transparent with Events Mode' on page 188) for modem.

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

    Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0). Set the ini file parameter, V34FaxTransportType to 1 (Relay). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 192: Fax Relay For Sg3 Fax Machines

    Mediant 800B Gateway & E-SBC  To allow V.34 fax relay over T.38:  Set the 'SIP T.38 Version' parameter to Version 3 (SIPT38Version = 3).  To force V.34 fax machines to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode:...

  • Page 193: Modem Relay

    Modem Relay purpose. This is also in accordance to DOD UCR 2008 specification: "The AS-SIP signaling appliance MUST advertise the “NoAudio” payload type to interoperate with a “Modem Relay- Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Preferred” endpoint that immediately transitions to the Modem Relay state without first transmitting voice information in the Audio state." Note: • The V.150.1 Modem Relay feature is available only if the device is installed with a License Key that includes this feature.

  • Page 195: Configuring Rtp/Rtcp Settings

    At the minimum value of 0, the buffer tracks delays only to compensate for clock drift and quickly decays back to the minimum level. This optimizes the delay performance but at the expense of a higher Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 196: Comfort Noise Generation

    Mediant 800B Gateway & E-SBC error rate. The default settings of 10 msec Minimum delay and 10 Optimization Factor should provide a good compromise between delay and error rate. The jitter buffer ‘holds’ incoming packets for 10 msec before making them available for decoding into voice. The coder polls frames from the buffer at regular intervals in order to produce continuous speech.

  • Page 197: Configuring Dtmf Transport Types

    INFO messages. To enable the mode: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the 'First Tx DTMF Option' parameter to INFO Cisco (FirstTxDTMFOption = Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 198 Mediant 800B Gateway & E-SBC Note: DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF).  Using NOTIFY messages according to IETF Internet-Draft draft-mahy-sipping- signaled-digits-01: DTMF digits are sent to the remote side using NOTIFY messages.

  • Page 199: Configuring Rfc 2833 Payload

    UDP port range and then associate the Media Realm with a specific IP Group, for example. However, the port range of the Media Realm must be within the range configured by the BaseUDPPort parameter. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 200: Event Detection And Notification Using X-Detect Header

    Mediant 800B Gateway & E-SBC The following procedure describes how to configure the RTP base UDP port through the Web interface.  To configure the RTP base UDP port: Open the RTP/RTCP Settings page (Setup menu > Signaling & Media tab > Media folder >...
  • Page 201 For more information on SIT detection, see SIT Event Detection on page 202.  To configure beep detection, see Detecting Answering Machine Beep on page 203.   Set the IsFaxUsed parameter to any value other Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 202: Sit Event Detection

    Mediant 800B Gateway & E-SBC Event Subtype Description and Required Configuration Type than 0. - or -  Set the IsFaxUsed parameter to 0 and the FaxTransportMode parameter to any value other than 0.  modem Set the VxxModemTransportType parameter to 3.

  • Page 203: Detecting Answering Machine Beeps

    The following example shows a SIP call flow of the device's AMD and event detection feature, whereby the device detects an answering machine and the subsequent start and end of the greeting message, enabling the third-party application server to know Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 204 Mediant 800B Gateway & E-SBC when to play a recorded voice message to an answering machine: Upon detection of the answering machine, the device sends the following SIP INFO message to the application server: INFO sip:sipp@172.22.2.9:5060 SIP/2.0 Via: SIP/2.0/UDP 172.22.168.249;branch=z9hG4bKac1566945480 Max-Forwards: 70 From: sut <sip:3000@172.22.168.249:5060>;tag=1c1505895240...

  • Page 205: Answering Machine Detection (Amd)

    In contrast, when an answering machine answers the call, there is constant speech (answering message) followed by a beep to leave a voice-mail message. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 206 AudioCodes sales representative for more information on this service. You will be typically required to provide AudioCodes with a database of recorded voices (calls) in the language on which the device's AMD feature can base its voice detector algorithms.
  • Page 207 Table 14-4: Approximate AMD High Detection Sensitivity - Parameter Suite 1 (Based on North American English) Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 0 (Best for Answering Machine) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 208: Configuring Amd

    Mediant 800B Gateway & E-SBC Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 15 (Best for Live Calls) 14.5.1 Configuring AMD You can configure AMD for all calls using global AMD parameters or for specific calls using IP Profiles.

  • Page 209: Enabling Ip-To-Tel Call Disconnection Upon Detection Of Answering Machine

    You can configure the required Gain Slope in decibels per second using the 'AGC Slope' parameter and the required signal energy threshold using the 'AGC Target Energy' parameter. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 210: Configuring Media (Srtp) Security

    Mediant 800B Gateway & E-SBC When the AGC first detects an incoming signal, it begins operating in Fast Mode, which allows the AGC to adapt quickly when a conversation starts. This means that the Gain Slope is 8 dB/sec for the first 1.5 seconds. After this period, the Gain Slope is changed to the user-defined value.
  • Page 211 Gateway calls and IpProfile_SBCMediaSecurityBehaviour parameter for SBC calls. For example, if negotiation of the cipher suite fails or if incoming calls exclude encryption information, the device can be configured to reject the calls. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 212: Srtp Using Dtls Protocol

    Mediant 800B Gateway & E-SBC Note: • For a detailed description of the SRTP parameters, see 'Configuring IP Profiles' on page 405 and 'SRTP Parameters' on page 1013. • When SRTP is used, the channel capacity may be reduced. The procedure below describes how to configure SRTP through the Web interface.
  • Page 213 > sbc-dtls-mtu) to define the maximum transmission unit (MTU) size for the DTLS handshake. Note: • The 'Cipher Server' parameter must be configured to "ALL". • The device does not support forwarding of DTLS transparently between endpoints. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 214 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 215: Services

    Option 51 IP Address Lease Time Option 1 Subnet Mask Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 216 Mediant 800B Gateway & E-SBC DHCP Option Code DHCP Option Name Option 2 Time Offset Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following: ...
  • Page 217 Defines the IP address (IPv4) of the primary DNS server that the DHCP server assigns to the DHCP client. The value is sent dns-server-1 in DHCP Option 6 (Domain Name Server). [DhcpServer_DNSServer1] The default value is 0.0.0.0. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 218 Mediant 800B Gateway & E-SBC Parameter Description DNS Server 2 Defines the IP address (IPv4) of the secondary DNS server that the DHCP server assigns to the DHCP client. The value is sent dns-server-2 in DHCP Option 6 (Domain Name Server).
  • Page 219 [0] DNS names = (Default) The 'SIP server' parameter is configured with an FQDN of the SIP server.  [1] IP address = The 'SIP server' parameter configured with an IP address of the SIP server. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 220: 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 221: Configuring Additional Dhcp Options

    Click New; the following dialog box appears: Figure 15-3: DHCP Option Table - Add Dialog Box Configure additional DHCP Options for the DHCP server according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 222 Mediant 800B Gateway & E-SBC Table 15-4: DHCP Option Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. dhcp option Note: Each row must be configured with a unique index. [DhcpOption_Index] DHCP Server Index Associates the DHCP Option table entry with a DHCP server that you configured in 'Configuring the DHCP Server' on page 215.

  • Page 223: Configuring Static Ip Addresses For Dhcp Clients

    'Configuring the DHCP Server' on page 215. dhcp-server-number Note: Currently, only one DHCP server (Index 0) can be [DhcpStaticIP_DhcpServerIndex] configured and therefore, the parameter is always set at 0. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 224: Viewing And Deleting Dhcp Clients

    Mediant 800B Gateway & E-SBC Parameter Description IP Address Defines the "reserved", static IP address (IPv4) to assign the DHCP client. ip-address The default is 0.0.0.0. [DhcpStaticIP_IPAddress] MAC Address Defines the DHCP client by MAC address (in hexadecimal format). mac-address The valid value is a string of up to 20 characters.

  • Page 225: 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 226 Mediant 800B Gateway & E-SBC The device can record calls between two IP Groups, or between an IP Group and a Trunk Group for Gateway calls. 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.
  • Page 227 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 m=audio 6030 RTP/AVP 8 96 c=IN IP4 10.33.8.70 a=ptime:20 a=sendonly a=label:2 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 --boundary_ac1fffff85b Content-Type: application/rs-metadata Content-Disposition: recording-session <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 228: Enabling Sip-Based Media Recording

    Mediant 800B Gateway & E-SBC <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <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">...

  • Page 229: Configuring Sip Recording Rules

    Note: For an SBC RTP-SRTP session, the recorded IP Group must be set to the RTP leg if recording is required to be RTP, or set to the SRTP leg if recording is required to be SRTP. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 230: Configuring Sip User Part For Srs

    Mediant 800B Gateway & E-SBC Parameter Description Recorded Source Prefix Defines calls to record based on source number or URI. recorded-src-prefix By default, all source numbers or URIs are defined (*). [SIPRecRouting_RecordedSourcePrefix] Recorded Destination Prefix Defines calls to record based on destination number or URI.

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

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

  • Page 232: Radius-Based Services

    Mediant 800B Gateway & E-SBC 15.3 RADIUS-based Services The device supports Remote Authentication Dial In User Service (RADIUS) by acting as a RADIUS client. You can use RADIUS for the following:  Authentication and authorization of management users (login username and password) to gain access to the device's management interface.
  • Page 233 (up to 1 local port).  To configure a RADIUS server: Open the RADIUS Servers table (Setup menu > IP Network tab > RADIUS & LDAP folder > RADIUS Servers). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 234 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-9: RADIUS Servers Table - Add Dialog Box Configure a RADIUS server according to the parameters described in the table below. Click Apply. Table 15-7: RADIUS Servers Table Parameter Descriptions...

  • Page 235: Configuring Interface For Radius Communication

    The Vendor ID must be the same as the Vendor ID set on the third-party RADIUS server. See the example for setting up a third-party RADIUS server in 'Setting Up a Third-Party RADIUS Server' on page 237. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 236: Radius-Based Management User Authentication

    Mediant 800B Gateway & E-SBC  To configure the RADIUS Vendor ID: Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder > Authentication Server). Figure 15-11: Configuring RADIUS Vendor ID Under the RADIUS group, in the 'RADIUS VSA Vendor ID' field, enter the same vendor ID number as set on the third-party RADIUS server.

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

    Service-Type = Login-User, ACL-Auth-Level = ACL-Auth-UserLevel Record and retain the IP address, port number, shared secret code, vendor ID, and VSA access level identifier (if access levels are implemented) used by the RADIUS server. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 238: Configuring Radius-Based User Authentication

    Mediant 800B Gateway & E-SBC 15.3.6.2 Configuring RADIUS-based User Authentication The following procedure describes how to configure RADIUS-based login authentication. For a detailed description of the RADIUS parameters, see 'RADIUS Parameters' on page 1230.  To configure RADIUS-based login authentication: Open the Authentication Server page (Setup menu >...

  • Page 239: Securing Radius Communication

    Web interface's login screen. However, authentication with the RADIUS server can also be done immediately after the user enters the URL, if the URL also contains the login credentials. example: http://10.4.4.112/Forms/RadiusAuthentication?WSBackUserName=John&WSBackPasswor d=1234 Note: This feature allows up to five simultaneous users only. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 240: Radius-Based Cdr Accounting

    Mediant 800B Gateway & E-SBC 15.3.7 RADIUS-based CDR Accounting Once you have configured a RADIUS server(s) for accounting in 'Configuring RADIUS Servers' on page 232, you need to enable and configure RADIUS-based CDR accounting (see 'Configuring RADIUS Accounting' on page 915).

  • Page 241: Enabling The Ldap Service

    Open the LDAP Settings page (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Settings). Figure 15-18: Enabling LDAP From the 'LDAP Service' drop-down list, select Enable. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 15.4.2 Enabling LDAP-based Web/CLI User Login Authentication and Authorization The LDAP service can be used for authenticating and authorizing device management users (Web and CLI), based on the user's login username and password (credentials). At the same, it can also be used to determine users' management access levels (privileges).
  • Page 243  [1] Sequential = The device first queries one of the LDAP servers and if the DN object is not found or the search fails, it queries the second LDAP server. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 244: Configuring Ldap Servers

    Mediant 800B Gateway & E-SBC Parameter Description DN Search Method Defines the method for querying the Distinguished Name (DN) objects within each LDAP server. search-dn-method  [0] Sequential = (Default) The query is done in each DN [LdapServerGroups_SearchDnsMet object, one by one, until a result is returned. For example, a hod] search for the DN object record "JohnD"...
  • Page 245 By default, no value is defined and the device uses the OAMP [LdapConfiguration_Interface] network interface, configured in the IP Interfaces table. To configure IP network interfaces, see 'Configuring IP Network Interfaces' on page 135. Note: The parameter is mandatory. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 246 Mediant 800B Gateway & E-SBC Parameter Description Use TLS Enables the device to encrypt the username and password (for Control and Management related queries) using TLS when use-tls sending them to the LDAP server. [LdapConfiguration_useTLS]  [0] No = (Default) Username and password are sent in clear- text format.
  • Page 247  The parameter is mandatory.  By default, the device sends the password in clear-text format. You can enable the device to encrypt the password using TLS (see the 'Use SSL' parameter below). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Parameter Description LDAP Bind DN Defines the LDAP server's bind Distinguished Name (DN) or username. bind-dn  LDAP-based SIP queries: The DN is used as the username [LdapConfiguration_LdapConfBi during connection and binding to the LDAP server. The DN is ndDn] used to uniquely name an AD object.

  • Page 249: Configuring The Ldap Search Filter Attribute

    (and excludes others). This is configured by the 'LDAP Authentication Filter' parameter, as described in the following procedure. You can use the dollar ($) sign to represent the username. For example, Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 250: Configuring Access Level Per Management Groups Attributes

    Mediant 800B Gateway & E-SBC the filter can be configured as "(sAMAccountName=$)", where if the user attempts to log in with the username "SueM", the LDAP search is done only for the attribute sAMAccountName that equals "SueM".  Attribute (e.g., "memberOf") to return from objects that match the filter criteria: The attribute is configured by the 'Management Attribute' parameter in the LDAP Servers table (see 'Configuring LDAP Servers' on page 244).
  • Page 251 The following procedure describes how to configure an access level per management groups through the Web interface. You can also configure it through ini file (MgmntLDAPGroups) or CLI (configure system > ldap mgmt-ldap-groups). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 252: Configuring The Device's Ldap Cache

    Mediant 800B Gateway & E-SBC  To configure management groups and corresponding access level: Open the LDAP Servers table (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Servers). In the table, select the row of the LDAP server for which you want to configure management groups with a corresponding access level, and then click the Management LDAP Groups link located below the table;...
  • Page 253 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 254: Refreshing The Ldap Cache

    Mediant 800B Gateway & E-SBC Note: • The LDAP Cache feature is applicable only to LDAP-based SIP queries (Control). • The maximum LDAP cache size is 10,000 bytes. • The device can save up to six LDAP Attributes in the cache per user (search LDAP key).
  • Page 255 (e.g., telephoneNumber=1004). Click Refresh; if a request with the specified key exists in the cache, a request is sent to the LDAP server for the Attributes associated in the cache with the search key. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 256: Clearing The Ldap Cache

    Mediant 800B Gateway & E-SBC 15.4.8.2 Clearing the LDAP Cache You can remove (clear) all LDAP entries in the device's LDAP cache for a specific LDAP Server Group, as described in the following procedure.  To clear the LDAP cache: Open the LDAP Settings page (Setup menu >...

  • Page 257: Configuring Local Database For Management User Authentication

    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). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 258 Mediant 800B Gateway & E-SBC The LDAP server's entry data structure schema in the example is as follows:  DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: Figure 15-30: Base Path (DN) in LDAP Server...
  • Page 259 (where the attribute's value equals the username): Figure 15-31: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-32: User's memberOf Attribute Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 260 Mediant 800B Gateway & E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-33: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...

  • Page 261: Enabling Ldap Searches For Numbers With Characters

    15.4.11 Enabling LDAP Searches for Numbers with Characters Typically, the device performs LDAP searches in the AD for complete numbers where the digits are adjacent to one another (e.g., 5038234567). However, if the number is defined in the AD with Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 262: Ad-Based Routing For Microsoft Skype For Business

    Mediant 800B Gateway & E-SBC characters (such as spaces, hyphens and periods) separating the digits (e.g., 503-823 4567), the LDAP query returns a failed result. To enable the device to search the AD for numbers that may contain characters between its digits, you need to specify the Attribute (up to five) for which you want to apply this functionality, using the LDAPNumericAttributes parameter.
  • Page 263 "MOBILE" (MOBILE:<mobile_number>): used to match a routing rule based on query results of the mobile number (MSLDAPMobileNumAttributeName) • "LDAP_ERR": used to match a routing rule based on a failed query result when no attribute is found in the AD Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 264 Mediant 800B Gateway & E-SBC Note: These prefixes are involved only in the routing and manipulation processes; they are not used as the final destination number. The device uses the Tel-to-IP Routing table to route the call based on the LDAP query result.
  • Page 265 Figure 15-39: Querying AD in Skype for Business Environment Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page 252 for the LDAP query process. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 266: Configuring Ad-Based Routing Rules

    Mediant 800B Gateway & E-SBC 15.4.12.2 Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries.  To configure LDAP-based IP routing for Skype for Business: Configure the LDAP server parameters, as described in 'Configuring LDAP Servers' on page 244.
  • Page 267 10.33.45.100) upon successful AD query result for the Mobile attribute.  Rule 5: Sends call to IP address of device (10.33.45.80) if AD query failure (e.g., no response from LDAP server or attribute not found). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 268: Querying The Ad For Calling Name

    Mediant 800B Gateway & E-SBC  Rule 6: Sends query for original destination number of received call to the LDAP server.  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases •...

  • Page 269: Least Cost Routing

    If four matching routing rules are located in the routing table and each one is assigned a different Cost Group as listed in the table above, then the rule assigned Cost Group "D" is selected. Note Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 270 Mediant 800B Gateway & E-SBC 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.

  • Page 271: Configuring Lcr

    (CostGroupTable) or CLI (configure voip > sip-definition least- cost-routing cost-group).  To configure a Cost Group: Open the Cost Groups table (Setup menu > Signaling & Media tab > SIP Definitions folder Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 272 Mediant 800B Gateway & E-SBC > Least Cost Routing > Cost Groups). Click New; the following dialog box appears: Configure a Cost Group according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.
  • Page 273 The valid value range is 0-65533. The default is 0. [CostGroupTimebands_ConnectionCost] Note: The entered value must be a whole number (i.e., not a decimal). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 274: Assigning Cost Groups To Routing Rules

     Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM. User's Manual Document #: LTRT-10298...
  • Page 275 Defines an index number for the new table row. [HTTPRemoteServices_Index] Note:  Each row must be configured with a unique index.  The parameter is mandatory. Name Defines an arbitrary name to easily identify the row. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 276 [2] Topology Status = Topology status service (e.g., change in configuration).  [3] Capture = Recording of signaling and RTP packets, which can be sent to a remote host, for example, to a Syslog server or AudioCodes SEM. Note: ...
  • Page 277 Online Certificate Status Protocol (OCSP) server whether the certificate has been revoked. This is also configured for the associated TLS Context. Note: The parameter is applicable only if the connection is HTTPS. Timeouts Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 278: Configuring Remote Http Hosts

    Mediant 800B Gateway & E-SBC Parameter Description Response Timeout Defines the TCP response timeout (in seconds) from the remote host. If one of the remote hosts does not respond to a request within the rest-timeout specified timeout, the device closes the corresponding socket and [HTTPRemoteServices_TimeO attempts to connect to the next remote host.
  • Page 279 (Read-only) Displays the status of the connection with the remote host. http-host-state  "Connected": The hosts is connected.  "Disconnected": The host is disconnected.  "Not In Service": Configuration of the host is invalid. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 280: Enabling Topology Status Services

    You can employ a remote, third-party Routing server to handle call routing decisions in deployments consisting of multiple AudioCodes devices. The Routing server can be used to handle SBC, Tel-to-IP, and IP-to-Tel calls. Employing a Routing server replaces the need for the device's routing tables (IP-to-IP Routing table for SBC calls, and Tel-to-IP Routing table and IP- to-Tel Routing table for Tel-to-IP and IP-to-Tel calls respectively) to determine call destination.
  • Page 281 IP Group (Proxy Set) is unavailable, detected by the keep-alive mechanism, or when the CAC thresholds permitted per IP Group have been crossed. For Trunk Groups, the device reports when the trunk's physical state indicates that the trunk is unavailable. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 282 Mediant 800B Gateway & E-SBC  Credentials for Authentication: The Routing Server can provide user (e.g., IP Phone caller) credentials (username-password) in the Get Route response, which can be used by the device to authenticate outbound SIP requests if challenged by the outbound peer, for example, Microsoft Skype for Business (per RFC 2617 and RFC 3261).

  • Page 283: Http-Based Proxy Services

     HTTP-based EMS Services for AudioCodes Equipment behind NAT: You can configure the device to act as an HTTP Proxy that enables AudioCodes EMS to manage AudioCodes equipment (such as IP Phones) over HTTP when the equipment is located behind NAT (e.g., in the LAN) and EMS is located in a public domain (e.g., in the WAN).

  • Page 284: Enabling The Http Proxy Application

    The HTTP Interfaces table lets you configure up to 10 HTTP Interfaces. An HTTP Interface represents a local, listening interface for receiving HTTP/S requests from HTTP-based (Web) clients such as managed equipment (e.g., IP Phones) and/or AudioCodes EMS management tool for HTTP/S-based services.
  • Page 285 This is also configured for the associated TLS Context. Note: The parameter is applicable only if the connection protocol is HTTPS (defined using the 'Protocol' parameter, above). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 286: Configuring Http Proxy Services

    Mediant 800B Gateway & E-SBC 15.7.3 Configuring HTTP Proxy Services The HTTP Proxy Services table lets you configure up to 10 HTTP Proxy Services. The following procedure describes how to configure HTTP Proxy Services through the Web interface. You can also configure it through ini file (HTTPProxyService) or CLI (configure network >...

  • Page 287: Configuring Http Proxy Hosts

    Open the HTTP Proxy Services table (Setup menu > IP Network tab > HTTP Proxy folder > HTTP Proxy Services). In the table, select the required HTTP Proxy Service index row, and then click the HTTP Proxy Hosts link located below the table; the HTTP Proxy Hosts table appears. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 288 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-52: HTTP Proxy Hosts Table - Add Dialog Box Configure an HTTP Proxy Host according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.

  • Page 289: Configuring An Http-Based Ems Service

    Open the EMS Services table (Setup menu > IP Network tab > HTTP Proxy folder > EMS Services). Click New; the following dialog box appears: Figure 15-53: EMS Services Table - Add Dialog Box Configure an EMS Service according to the parameters described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 290 Mediant 800B Gateway & E-SBC Click Apply, and then save your settings to flash memory. Table 15-24: EMS Services Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [EMSService_Index] Note:  Each row must be configured with a unique index.

  • Page 291: E9-1-1 Support For Microsoft Skype For Business

    E9-1-1 caller. This section describes the E9-1-1 solution provided by Microsoft Skype for Business and AudioCodes' device's ELIN interworking capabilities, which provides the SIP Trunk or ISDN (or CAMA) connectivity to the E9-1-1 emergency service provider. This section also describes the configuration of the device for interoperating between the Skype for Business environment and the E9-1-1 emergency provider.

  • Page 292: Microsoft Skype For Business And E9-1-1

    Mediant 800B Gateway & E-SBC The VoIP user dials 9-1-1. AudioCodes' ELIN device eventually sends the call to the emergency service provider over the PSTN or SIP Trunk (PSAP server). The emergency service provider identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network.
  • Page 293 WAP / SSID is currently serving the soft-client. The LIS queries the published locations for a location and if a match is found, returns the location information to the client. The matching order is as follows: • WAP BSSID Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 294: Adding Elins To The Location Information Server

    Mediant 800B Gateway & E-SBC • LLDP switch / port • LLDP switch • Subnet • MAC address This logic ensures that for any client that is connected by a wireless connection, a match is first attempted based on the hardware address of its connected access point. The logic is for the match to be based on the most detailed location.

  • Page 295: Passing Location Information To The Pstn Emergency Provider

    The figure below illustrates the use of ERLs and ELINs, with an E9-1-1 call from floor 2 at the branch office: The table below shows an example of designating ERLs to physical areas (floors) in a building and associating each ERL with a unique ELIN. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 296: Audiocodes Elin Device For Skype For Business E9-1-1 Calls To Pstn

    PSAP, based on ELIN-address match lookup in the emergency service provider's ALI database. The figure below illustrates an AudioCodes ELIN device deployed in the Skype for Business environment for handling E9-1-1 calls between the Enterprise and the emergency service provider.
  • Page 297 From: "voip_911_user1"<sip:voip_911_user1@contoso.com>;epid=1D19090AED;tag=d 04d65d924 To: <sip:911;phone-context=Redmond@192.168.1.12;user=phone> CSeq: 8 INVITE Call-ID: e6828be1-1cdd-4fb0-bdda-cda7faf46df4 VIA: SIP/2.0/TLS 192.168.0.244:57918;branch=z9hG4bK528b7ad7 CONTACT: <sip:voip_911_user1@contoso.com;opaque=user:epid:R4bCDaUj51a06PUbkraS0 QAA;gruu>;text;audio;video;image PRIORITY: emergency CONTENT-TYPE: multipart/mixed; boundary= ------ =_NextPart_000_4A6D_01CAB3D6.7519F890 geolocation: <cid:voip_911_user1@contoso.com>;inserted- by="sip:voip_911_user1@contoso .com" Message-Body: ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/sdp ; charset=utf-8 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 298: Pre-Empting Existing Calls For E9-1-1 Calls

    Mediant 800B Gateway & E-SBC o=- 0 0 IN IP4 Client s=session c=IN IP4 Client t=0 0 m=audio 30684 RTP/AVP 114 111 112 115 116 4 3 8 0 106 97 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000...

  • Page 299: Psap Callback To Skype For Business Clients For Dropped E9-1-1 Calls

    If the first ELIN in the list is being used by another active call, the device skips to the next ELIN in the list, and so on until it finds an ELIN that is not being used and sends this ELIN. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 300: Location Based Emergency Routing

    Note: Location-based emergency routing is applicable only to the Gateway application. 15.8.4 Configuring AudioCodes ELIN Device This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Skype for Business environment. 15.8.4.1 Enabling the E9-1-1 Feature By default, the ELIN device feature for E9-1-1 emergency call handling in a Skype for Business environment is disabled.

  • Page 301: Configuring The E9-1-1 Callback Timeout

    IP-to-IP Routing table for routing between the emergency callers' IP Group and the PSAP server's IP Group. The only special configuration is to define the emergency number (e.g., 911) in the 'Destination Username Prefix' parameter of the IP Group belonging to Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 302: Configuring Location-Based Emergency Routing

    Mediant 800B Gateway & E-SBC the E9-1-1 callers. The following example shows IP-to-IP routing rules for E9-1-1 in a Skype for Business environment: Figure 15-58: Example of IP-to-IP Routing Rules for Skype for Business E9-1-1 15.8.4.5 Configuring Location-Based Emergency Routing The device identifies the geographical location of emergency callers by their ELIN numbers, which is present in the PIDF-LO XML body of received SIP INVITE messages.
  • Page 303 ELIN numbers: Figure 15-60: Configuring Destination Number Manipulation Rules for Location-Based Emergency Routing Index 0 manipulates the destination number for London emergency callers; Index 1 manipulates the destination number for Manchester emergency callers. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 304: Viewing The Elin Table

    Mediant 800B Gateway & E-SBC 15.8.4.6 Viewing the ELIN Table To view the ELIN table:  # show voip e911 ELIN Time Count Index Call From ------------------------------------------------------------ 4257275678 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616...

  • Page 305: Quality Of Experience

    16.1 Reporting Voice Quality of Experience to SEM 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 306: Configuring Clock Synchronization Between Device And Sem

    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 307: Configuring Quality Of Experience Profiles

    (i.e., change in color state). Hysteresis is used to avoid false reports being sent by the device. Hysteresis is used only for threshold crossings toward a lesser severity (i.e., from Red to Yellow, Red to Green, or Yellow to Green). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 308  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). To configure the SEM server's address, see 'Configuring the SEM Server' on page 305.
  • Page 309 [3] High = Pre-configured high sensitivity thresholds. Reporting is done for small fluctuations in parameter values. In the Quality of Experience Profile table, select the row for which you want to configure QoE Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 310 Mediant 800B Gateway & E-SBC thresholds, and then click the Quality of Experience Color Rules link located below the table; the Quality of Experience Color Rules table appears. Click New; the following dialog box appears: Figure 16-4: Quality of Experience Color Rules Table - Dialog Box Configure a rule according to the parameters described in the table below.
  • Page 311 For example, if you configure the 'Major Threshold (Red)' parameter to 2 and the 'Major Hysteresis (Red)' parameter to 0.1 (for MOS), the device considers a threshold crossing to Yellow only if the MOS crosses 2.1 (i.e., 2 + 0.1). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 312: Configuring Bandwidth Profiles

    Mediant 800B Gateway & E-SBC 16.3 Configuring Bandwidth Profiles The Bandwidth Profile table lets you configure up to 486 Bandwidth Profiles. A Bandwidth Profile defines bandwidth utilization thresholds for audio and/or video traffic (incoming and outgoing), which if crossed can result in various actions (discussed later in the section). Bandwidth Profiles enhance the device's monitoring of bandwidth utilization.
  • Page 313 You can also configure it through ini file (BWProfile) or CLI (configure voip > qoe bw- profile).  To configure a Bandwidth Profile: Open the Bandwidth Profile table (Setup menu > Signaling & Media tab > Media folder > Quality of Experience > Bandwidth Profile). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 314 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 16-6: Bandwidth Profile Table - Dialog Box Configure a rule according to the parameters described in the table below. Click Apply, and then reset the device with a save to flash memory.

  • Page 315: Configuring Quality Of Service Rules

    Exceeded). If you configure these SIP response codes in the Alternative Routing Reasons table (see 'Configuring SIP Response Codes for Alternative Routing Reasons' on page 677) and the device rejects a call, it searches in the IP-to-IP Routing table for an alternative routing rule. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 316 Mediant 800B Gateway & E-SBC When the device rejects calls to an IP Group based on a Quality of Service rule, it raises an SNMP alarm (acIpGroupNoRouteAlarm). The alarm is also raised upon a keep-alive failure with the IP Group. For more information, refer to the SNMP Reference Guide.
  • Page 317 InVoice Quality, you must configure the parameter to Alternative IP Profile. If the threshold is crossed (i.e., poor call quality), the device changes the IP Profile for the specific call only (during the call). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 318 Mediant 800B Gateway & E-SBC Parameter Description Calls Reject Duration Defines the duration (in minutes) for which the device rejects calls to the IP Group if the rule is matched. calls-reject-duration The default is 5. [QualityOfServiceRules_CallsRejectDuration] Note: The parameter is applicable only if the 'Rule Action' parameter is configured to Reject Calls.

  • Page 319: Control Network

    You can also configure it through ini file (CpMediaRealm) or CLI (configure voip > realm).  To configure a Media Realm: Open the Media Realms table (Setup menu > Signaling & Media tab > Core Entities folder > Media Realms). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 320 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-1: Media Realms Table - Add Dialog Box Configure the Media Realm according to the parameters described in the table below. Click Apply. Table 17-1: Media Realms table Parameter Descriptions...
  • Page 321 However, you can configure the device to use the same port for RTP and T.38 packets, by configuring the T38UseRTPPort parameter to 1. For more information on local UDP port range, see Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 322: Configuring Remote Media Subnets

    Mediant 800B Gateway & E-SBC Parameter Description 'Configuring RTP Base UDP Port' on page 199. Default Media Realm Defines the Media Realm as the default Media Realm. The default Media Realm is used for SIP Interfaces and IP Groups is-default for which you have not assigned a Media Realm.
  • Page 323 Open the Media Realms table (see 'Configuring Media Realms' on page 319). Select the Media Realm row for which you want to add Remote Media Subnets, and then click the Remote Media Subnet link located below the table; the Remote Media Subnet table appears. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 324 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-3: Remote Media Subnet Table - Add Dialog Box Configure the Remote Media Subnet according to the parameters described in the table below. Click Apply. Table 17-2: Remote Media Subnet Table Parameter Descriptions...

  • Page 325: Configuring Media Realm Extensions

    Web interface. You can also configure it through ini file (MediaRealmExtension) or CLI (configure voip > voip-network realm-extension).  To configure a Media Realm Extension: Open the Media Realms table (see 'Configuring Media Realms' on page 319). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 326 Mediant 800B Gateway & E-SBC Select the Media Realm for which you want to add Remote Media Extensions, and then click the Media Realm Extension link located below the table; the Media Realm Extension table appears. Click New; the following dialog box appears:...

  • Page 327: Configuring Srds

    VoIP network (Layer 5). For example, if your VoIP deployment consists of an Enterprise IP PBX (LAN), a SIP Trunk (WAN), and far-end users (WAN), you would only need a single SRD. The single SRD would be assigned to three different SIP Interfaces, where each SIP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 328 Mediant 800B Gateway & E-SBC Interface would represent a specific Layer-3 network (IP PBX, SIP Trunk, or far-end users) in your environment. The following figure provides an example of such a deployment: Figure 17-6: Deployment using a Single SRD Note: •...
  • Page 329 However, calls can be routed between the SRD and other Shared SRDs. For more information on SRD Sharing Policy, see Multiple SRDs for Multi- tenant Deployments on page 333. Note: The parameter is applicable only to the SBC application. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 330 Mediant 800B Gateway & E-SBC Parameter Description SBC Operation Mode Defines the device's operational mode for the SRD.  sbc-operation-mode [0] B2BUA = (Default) Device operates as a back-to-back user agent (B2BUA), changing the call identifiers and headers between the [SRD_SBCOperationMo inbound and outbound legs.
  • Page 331 [0] Disable = The device rejects REGISTER requests from new users that were not authenticated by a proxy server.  [1] Enable = (Default) The device accepts REGISTER requests from new users even if they were not authenticated by a proxy server, and Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 332: Filtering Tables In Web Interface By Srd

    Mediant 800B Gateway & E-SBC Parameter Description registers the user in its registration database. Note:  Regardless of the parameter, the device always accepts registration refreshes from users that are already registered in its database.  For a SIP Interface that is associated with the SRD, if the...

  • Page 333: Multiple Srds For Multi-Tenant Deployments

    Policy. Routing Policies allow each SRD (or tenant) to have its own routing rules, manipulation rules, Least Cost Routing (LCR) rules, and/or LDAP-based routing configuration. However, not all multi-tenant deployments need multiple Routing Policies Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 334: Cloning Srds

    Mediant 800B Gateway & E-SBC and typically, their configuration is not required. Isolated SRDs are more relevant only when each tenant requires its own dedicated Routing Policy to create separate, dedicated routing "tables"; for all other scenarios, SRDs can be Shared. For more information on Routing Policies, see 'Configuring SBC Routing Policy Rules' on page 680.

  • Page 335: Color-Coding Of Srds In Web Interface

    SRD in tables where the SRD is configured or assigned. This is applied throughout the Web interface. The following example shows SRDs assigned with unique color codes. Figure 17-9: Color-Coding of SRDs Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 336: Automatic Configuration Based On Srd

    Mediant 800B Gateway & E-SBC 17.2.5 Automatic Configuration based on SRD To facilitate configuration and eliminate possible flaws in configuration due to invalid associations between configuration entities, the Web interface automatically configures configuration entities based on SRD:  If you delete an SRD (in the SRDs table) that is associated with other configuration entities in other tables, the device automatically deletes the associated table rows.
  • Page 337  To configure a SIP Interface: Open the SIP Interfaces table (Setup menu > Signaling & Media tab > Core Entities folder > SIP Interfaces). Click New; the following dialog box appears: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 338 Mediant 800B Gateway & E-SBC Configure a SIP Interface according to the parameters described in the table below. Click Apply. Table 17-5: SIP Interfaces table Parameter Descriptions Parameter Description Assigns an SRD to the SIP Interface. If only one SRD is configured in the SRDs table, the SRD is assigned to the SIP Interface by default.
  • Page 339 6000 to 6999, the SIP port can either be less than 6000 or greater than 6999.  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 340 Mediant 800B Gateway & E-SBC Parameter Description Encapsulating Protocol Defines the type of incoming traffic (SIP messages) expected on the SIP Interface. encapsulating-protocol  [0] No Encapsulation (default) = Regular (non-WebSocket) traffic. [SIPInterface_Encapsulating  [1] WebSocket = Traffic received on the SIP Interface is identified...
  • Page 341 SIP Interface.  For more information on direct media, see Direct Media on page 626.  The parameter is applicable only to the SBC application. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 342 Mediant 800B Gateway & E-SBC Parameter Description Security TLS Context Name Assigns a TLS Context (SSL/TLS certificate) to the SIP Interface. tls-context-name The default TLS Context ("default" at Index 0) is assigned to the SIP Interface by default. [SIPInterface_TLSContext] Note: ...
  • Page 343 By default, no value is defined (i.e., the number of allowed user registrations is unlimited). [SIPInterface_MaxNumOfRe gUsers] Note: The parameter is applicable only to the SBC application. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 344: Configuring Ip Groups

    Mediant 800B Gateway & E-SBC 17.4 Configuring IP Groups The IP Groups table lets you configure up to 102 IP Groups. An IP Group represents a SIP entity in the network with which the device communicates. This can be a server (e.g., IP PBX or ITSP) or a group of users (e.g., LAN IP phones).
  • Page 345 Name Defines an arbitrary name to easily identify the row. name The valid value is a string of up to 40 characters. [IPGroup_Name] Note: Each row must be configured with a unique name. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 346 Mediant 800B Gateway & E-SBC Parameter Description Topology Location Defines the display location of the IP Group in the Topology view.  topology-location [0] Down = (Default) The IP Group element is displayed on the lower border of the view.
  • Page 347 The valid value is a string of up to 100 characters. By default, no value is defined. Note:  If the parameter is not configured, the value of the global parameter, Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 348 Mediant 800B Gateway & E-SBC Parameter Description ProxyName is used instead (see 'Configuring Proxy and Registration Parameters' on page 375).  The parameter overrides inbound message manipulation rules that manipulate the host name in Request-URI, To, and/or From SIP headers. If you configure the parameter and you want to manipulate...
  • Page 349 Classification rules to classify incoming SIP dialogs to these IP Groups. If the parameter is enabled, the device is unable to correctly classify incoming INVITEs to their Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 350 Mediant 800B Gateway & E-SBC Parameter Description appropriate IP Groups.  Classification by Proxy Set occurs only if classification based on the device's registration database fails (i.e., the INVITE is not from a registered user). SBC Operation Mode Defines the device's operational mode for the IP Group.
  • Page 351  [1] To  [2] Request-URI  [3] P-Asserted - First Header  [4] P-Asserted - Second Header  [5] P-Preferred  [6] Route  [7] Diversion  [8] P-Associated-URI  [9] P-Called-Party-ID Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 352 Mediant 800B Gateway & E-SBC Parameter Description  [10] Contact  [11] Referred-by Note:  The parameter is applicable only when classification is done according to the Classification table.  If the configured SIP header does not exist in the incoming INVITE message, the classification of the message to a source IP Group fails.
  • Page 353 Call Setup Rules Set ID Assigns a Call Setup Rule Set ID to the IP Group. The device runs the Call Setup rule immediately before the routing stage (i.e., only after the call-setup-rules-set-id Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 354 Mediant 800B Gateway & E-SBC Parameter Description [IPGroup_CallSetupRules classification and manipulation stages). SetId] By default, no value is assigned. To configure Call Setup Rules, see Configuring Call Setup Rules on page 387. Quality of Experience QoE Profile Assigns a Quality of Experience Profile rule.
  • Page 355 User Information table (see SBC User Information for SBC User Database on page 794). This is applicable only to User- type IP Groups.  Authenticates SIP severs. This is applicable only to Server-type IP Groups. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 356 Mediant 800B Gateway & E-SBC Parameter Description Authentication Method List Defines SIP methods received from the IP Group that must be challenged by the device when the device acts as an Authentication authentication-method-list server. If no methods are configured, the device doesn't challenge any [IPGroup_MethodList] methods.

  • Page 357: Configuring Proxy Sets

    To use a configured Proxy Set, you need to assign it to an IP Group in the IP Groups table (see 'Configuring IP Groups' on page 344). When the device sends INVITE messages to Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 358 Mediant 800B Gateway & E-SBC an IP Group, it sends it to the address configured for the Proxy Set. You can assign the same Proxy Set to multiple IP Groups (belonging to the same SRD). You can also enable the device to classify incoming SBC SIP dialogs to IP Groups, based on Proxy Set.
  • Page 359 336. SBC IPv4 SIP Interface Assigns an IPv4-based SIP Interface for SBC calls to the Proxy Set. sbcipv4-sip-int-name Note:  [ProxySet_SBCIPv4SIPInterfa At least one SIP Interface must be assigned to the Proxy Set. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 360 Mediant 800B Gateway & E-SBC Parameter Description  ceName] The parameter appears only if you have configured a network interface with an IPv4 address in the IP Interfaces table (see Configuring IP Network Interfaces on page 135).  To configure SIP Interfaces, see 'Configuring SIP Interfaces' on page 336.
  • Page 361 The device switches back to the primary proxy whenever it becomes available. Note:  To enable this functionality, you must also enable the Proxy Keep-Alive feature (see the 'Proxy Keep-Alive' parameter in this table). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 362 Mediant 800B Gateway & E-SBC Parameter Description  The Homing option can only be used if the 'Proxy Keep-Alive' parameter is set to Using Options. Proxy Hot Swap Enables the Proxy Hot-Swap feature, whereby the device switches to a redundant proxy upon a failure in the primary proxy (no is-proxy-hot-swap response is received).
  • Page 363 NAPTR response. If the NAPTR query fails, an SRV query is done according to the configured transport type. If the configured proxy address contains a domain name with a port (e.g., Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 364 Mediant 800B Gateway & E-SBC Parameter Description domain.com:5080), the device performs a regular DNS A-record query. If the transport type is configured for the proxy address, a NAPTR query is not performed.  [3] Microsoft Skype for Business = SRV query as required by Microsoft when the device is deployed in a Microsoft Skype for Business environment.

  • Page 365: Building And Viewing Sip Entities In Topology View

    "LAN": Indicates the internal network (e.g., inside the Enterprise) To modify a demarcation name, do the following: Click the demarcation name; the name becomes editable in a text box, as shown in the example below: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 366 Mediant 800B Gateway & E-SBC Item # Description Type a name as desired, and then click anywhere outside of the text box to apply the name. You can use demarcation to visually separate your voice network to provide a clearer understanding of your topology.
  • Page 367 To add a Media Realm, do the following: Click the Add Media Realm plus icon. The icon appears next to existing Media Realms, or as when no Media Realms exist on a topology Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 368 Mediant 800B Gateway & E-SBC Item # Description border, or as when there are no Media Realms at all. The Media Realms table opens with a new dialog box for adding a Media Realm to the next available index row.
  • Page 369 Topology View, displaying the new Trunk Group and a line connecting it to the associated port, as shown in the example below: For more information on configuring Trunk Groups, see Configuring Trunk Groups on page 477. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 370 Mediant 800B Gateway & E-SBC Item # Description Displays the device's hardware configuration concerning telephony (Tel/PSTN) trunks and ports (e.g., FXS, FXO, BRI and E1/T1). It also displays the number of ports. The ports are displayed as round icons, as shown in Item #6 above.

  • Page 371: Sip Definitions

    You can also configure it through ini file (Account) or CLI (configure voip > sip-definition account).  To configure an Account: Open the Accounts table (Setup menu > Signaling & Media tab > SIP Definitions folder > Accounts). Click New; the following dialog box appears: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 372 Mediant 800B Gateway & E-SBC Configure an account according to the parameters described in the table below. Click Apply. Once you have configured Accounts, you can register or un-register them, as described below:  To register or un-register an Account: In the table, select the required Account entry row.
  • Page 373 [1] Regular = Regular registration process. For more information, see 'Regular Registration Mode' on page 374.  [2] GIN = Registration for legacy PBXs, using Global Identification Number (GIN). For more information, see 'Single Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 374: Regular Registration Mode

    Mediant 800B Gateway & E-SBC Parameter Description Registration for Multiple Phone Numbers using GIN' on page 374. Note:  Gateway application: To enable registration, you also need to set the 'Registration Mode' parameter to Per Account in the Trunk Group Settings table (see Configuring Trunk Group Settings on page 479).

  • Page 375: Configuring Proxy And Registration Parameters

    18.2 Configuring Proxy and Registration Parameters The Proxy & Registration page allows you to configure the Proxy server and registration parameters. For a description of the parameters appearing on this page, see 'Configuration Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 376: Sip Message Authentication Example

    The REGISTER request is sent to a Registrar/Proxy server for registration: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c17940 To: <sip: 122@10.1.1.200> Call-ID: 634293194@10.1.1.200 User-Agent: Sip-Gateway/Mediant 800B Gateway and E- SBC/v.7.20A.000.038 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Upon receipt of this request, the Registrar/Proxy returns a 401 Unauthorized...
  • Page 377 • 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 378: Configuring Sip Message Manipulation

    Mediant 800B Gateway & E-SBC Authorization: Digest, username: 122, realm="audiocodes.com”, nonce="11432d6bce58ddf02e3b5e1c77c010d2", uri=”10.2.2.222”, response=“b9c45d0234a5abf5ddf5c704029b38cf” Upon receiving this request and if accepted by the Proxy, the Proxy returns a 200 OK response, completing the registration transaction: SIP/2.0 200 OK Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c23940...
  • Page 379 Condition) use the condition configured for rule 0 ('Row Rule' configured to Use Current Condition). For more information, see the description of the 'Row Rule' parameter in this section. Figure 18-1: Configuration Example of Message Manipulation Rules using Same Condition Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 380 Mediant 800B Gateway & E-SBC The figure below illustrates a SIP message manipulation example: Figure 18-2: SIP Header Manipulation Example User's Manual Document #: LTRT-10298...
  • Page 381 Open the Message Manipulations page (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Manipulations). Click New; the following dialog box appears: Figure 18-3: Message Manipulations Table - Add Dialog Box Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 382 Mediant 800B Gateway & E-SBC Configure a Message Manipulation rule according to the parameters described in the table below. Click Apply. An example of configured message manipulation rules are shown in the figure below: Figure 18-4: Example of Configured Message Manipulation Rules ...
  • Page 383 [6] Remove Prefix = Removes value from the beginning of the string (string element only).  [7] Normalize = Removes unknown SIP message elements before forwarding the message. Action Value Defines a value that you want to use in the manipulation. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 384: Configuring Sip Message Policy Rules

    Mediant 800B Gateway & E-SBC Parameter Description action-value The default value is a string (case-insensitive) in the following syntax: [MessageManipulations_ActionV  alue] string/<message-element>/<call-param> +  string/<message-element>/<call-param> For example:  'itsp.com'  header.from.url.user  param.call.dst.user  param.call.dst.host + '.com'  param.call.src.user + '<' + header.from.url.user + '@' + header.p-asserted-id.url.host + '>'...
  • Page 385 Note: Each row must be configured with a unique name. Limits Max Message Length Defines the maximum SIP message length. max-message-length The valid value is up to 32,768 characters. The default is 32,768. [MessagePolicy_MaxMessageLength] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 386 Mediant 800B Gateway & E-SBC Parameter Description Max Header Length Defines the maximum SIP header length. max-header-length The valid value is up to 512 characters. The default is 512. [MessagePolicy_MaxHeaderLength] Max Body Length Defines the maximum SIP message body length. This is the value of the Content-Length header.

  • Page 387: Configuring Call Setup Rules

     Dial Plan queries: For SBC calls, you can use Call Setup rules to query the Dial Plan table (see Configuring Dial Plans on page 697) for a specified search key in a Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 388 Mediant 800B Gateway & E-SBC specified Dial Plan to obtain the corresponding Dial Plan tag. Call Setup rules can also change (modify) the name of the obtained tag. The device can then route the call using an IP-to-IP Routing rule (in the IP-to-IP Routing table) that has a matching tag (source or destination).
  • Page 389 Server Groups on page 242.  Dial Plan: Specifies a Dial Plan (name) in which to search for a defined search key. To configure Dial Plans, see Configuring Dial Plans on page on page 697. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 390 Mediant 800B Gateway & E-SBC Parameter Description To configure the search key, use the 'Search Key' parameter (see below). Note: The parameter is applicable only if the 'Query Type' parameter is configured to any value other than None. Search Key Defines the key to query.
  • Page 391 [20] Run Rules Set = Performs a different Rule Set ID, specified in the 'Action Value' parameter (below)  [21] Exit = Stops the Rule Set ID and returns a result ("True" or "False"). . Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 392: Call Setup Rule Examples

    Mediant 800B Gateway & E-SBC Parameter Description Action Value Defines a value that you want to use in the action. action-value The valid value is a string of up to 300 characters (case- insensitive). [CallSetupRules_ActionValue] Examples:  '+9723976'+ldap.attr.alternateNumber  '9764000' ...
  • Page 393 The destination tag is then used as a matching characteristics in the IP-to-IP Routing table. • Call Setup Rules table: ♦ 'Rules Set ID': 4 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 394 Mediant 800B Gateway & E-SBC ♦ 'Query Type': LDAP ♦ 'Query Target': LDAP-DC-CORP ♦ 'Search Key': 'telephoneNumber='+param.call.dst.user ♦ 'Attributes to Get': ofiSBCRouting ♦ 'Row Role': Use Current Condition ♦ 'Condition': ldap.found exists ♦ 'Action Subject': dsttags ♦ 'Action Type': Modify ♦...

  • Page 395: Coders And Profiles

    In the IP Profile associated with the SIP entity (see Configuring IP Profiles on page 405): • Assign the Coder Group (using the IpProfile_SBCExtensionCodersGroupName parameter). • Enable the use of the Coder Group for transcoding (by configuring the IpProfile_SBCAllowedCodersMode parameter to Restriction or Restriction and Preference). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 396 For supported audio coders, see 'Supported Audio Coders' on page 398. • Some coders are license-dependent and are available only if purchased from AudioCodes and included in the License Key installed on your device. For more information, contact your AudioCodes sales representative. •...
  • Page 397 [0] 0 = Bandwidth Efficient  [1] 1 = Octet Aligned (default) Note: The AMR payload type can be configured globally using the AmrOctetAlignedEnable parameter. However, the Coder Group configuration overrides the global parameter. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 398: Supported Audio Coders

    Mediant 800B Gateway & E-SBC 19.1.1 Supported Audio Coders The table below lists the coders supported by the device. Table 19-2: Supported Audio Coders Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression [1] 10, [2] 20, [3] 30, [4] 40,...
  • Page 399 20 (default), 40, 60, 80, [43] 16 Dynamic and 100 (default 77) silk-wb [36] T.38 t-38 T.38 Over RTP Dynamic (default 106) t-38-over-rtp [43] Opus 20 (default), 40, 60, 80, Dynamic (default 111) opus [40] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 400: Configuring Various Codec Attributes

    Mediant 800B Gateway & E-SBC 19.1.2 Configuring Various Codec Attributes The following procedure describes how to configure various coder attributes such as bitrate.  To configure codec attributes: Open the Coder Settings page (Setup menu > Signaling & Media tab > Coders &...
  • Page 401  To configure an Allowed Audio Coders Group: Open the Allowed Audio Coders Groups table (Setup menu > Signaling & Media tab > Coders & Profiles folder > Allowed Audio Coders Groups). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 402 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 19-4: Allowed Audio Coders Groups table - Add Dialog Box Configure a name for the Allowed Audio Coders Group according to the parameters described in the table below.

  • Page 403: Configuring Allowed Video Coder Groups

    AllowedVideoCoders) or CLI (configure voip > coders-and-profiles allowed-video- coders-groups; configure voip > coders-and-profiles allowed-video-coders <group index/coder index>).  To configure an Allowed Video Coders Group: Open the Allowed Video Coders Groups table (Setup menu > Signaling & Media tab Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 404 Mediant 800B Gateway & E-SBC > Coders & Profiles folder > Allowed Video Coders Groups). Click New; the following dialog box appears: Figure 19-6: Allowed Video Coders Groups Table - Add Dialog Box Configure a name for the Allowed Video Coders Group according to the parameters described in the table below.

  • Page 405: Configuring Ip Profiles

    AlwaysUseRouteTable parameter is set to 1). The following procedure describes how to configure IP Profiles through the Web interface. You can also configure it through ini file (IPProfile) or CLI (configure voip > coders-and- profiles ip-profile). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 406 Mediant 800B Gateway & E-SBC  To configure an IP Profile: Open the IP Profiles table (Setup menu > Signaling & Media tab > Coders & Profiles folder > IP Profiles). Click New; the following dialog box appears: Figure 19-8: IP Profiles Table - Add Dialog Box Configure an IP Profile according to the parameters described in the table below.
  • Page 407 [1] Enable = The answer crypto line contains (or excludes) an MKI value according to the selected crypto line in the offer. For example, assume that the device receives an INVITE containing the following two crypto lines in SDP: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 408 Mediant 800B Gateway & E-SBC Parameter Description a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:TAaxNnQt8/qLQMnDuG4vxYfWl6K7eBK/ufk04pR4|2^ 31|1:1 a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:bnuYZnMxSfUiGitviWJZmzr7OF3AiRO0l5Vnh0kH|2^ The first crypto line includes the MKI parameter "1:1". In the 200 OK response, the device selects one of the crypto lines (i.e., '2' or '3'). Typically, it selects the first line that supports the crypto suite.
  • Page 409 [1] Yes = The device removes the lifetime field from the 'a=crypto' attribute. Note: If you configure the parameter to Yes, the following IP Profile parameters must be configured as follows:  IpProfile_EnableSymmetricMKI configured to Enable [1]. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 410 Mediant 800B Gateway & E-SBC Parameter Description  IpProfile_MKISize configured to 0.  IpProfile_SBCEnforceMKISize configured to Enforce [1]. SBC Early Media Remote Early Media Defines whether the remote side can accept early media or not.  sbc-rmt-early-media-supp [0] Not Supported = Early media is not supported.
  • Page 411 [0] No = UA does not support local ringback tone. The device sends 18x with delayed SDP to the UA. [IpProfile_SBCRemoteCanPl  [1] Yes = (Default) UA supports local ringback tone. For the ayRingback] device's handling of this remote UA support, see Interworking SIP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 412 Mediant 800B Gateway & E-SBC Parameter Description Early Media on page 641. Generate RTP Enables the device to generate "silence" RTP packets to the SIP entity until it detects audio RTP packets from the SIP entity. The parameter sbc-generate-rtp provides support for interworking with SIP entities that wait for the first [IPProfile_SBCGenerateRTP incoming packets before sending RTP (e.g., early media used for...
  • Page 413 IP Profile "IP-PBX-1", for calls amongst endpoints associated with IP Profile "IP-PBX-2", and for calls between endpoints associated with IP Profile "IP-PBX-1" and IP Profile "IP-PBX-2". Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 414 Mediant 800B Gateway & E-SBC Parameter Description The valid value is a string of up to 16 characters. By default, no value is defined. For more information on direct media, see Direct Media on page 626. RFC 2833 Mode Defines the handling of RFC 2833 SDP offer-answer negotiation for the SIP entity associated with the IP Profile.
  • Page 415 Defines how the device handles RTCP packets during call sessions for the SIP entity associated with the IP Profile. This is useful for sbc-rtcp-mode interworking RTCP between SIP entities. For example, this may be Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 416 Mediant 800B Gateway & E-SBC Parameter Description [IPProfile_SBCRTCPMode] necessary when incoming RTCP is not compatible with the destination SIP entity's (this IP Profile) RTCP support. In such a scenario, the device can generate the RTCP and send it to the SIP entity.
  • Page 417 Enables RTCP-based feedback indication in outgoing SDPs sent to the SIP entity associated with the IP Profile. sbc-rtcp-feedback The parameter supports indication of RTCP-based feedback, [IPProfile_SBCRTCPFeedba according to RFC 5124, during RTP profile negotiation between two Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 418 Mediant 800B Gateway & E-SBC Parameter Description communicating SIP entities. RFC 5124 defines an RTP profile (S)AVPF for (secure) real-time communications to provide timely feedback from the receivers to a sender. For more information on RFC 5124, see http://tools.ietf.org/html/rfc5124. Some SIP entities may require RTP secure-profile feedback negotiation (AVPF/SAVPF) in the SDP offer/answer exchange, while other SIP entities may not support it.
  • Page 419 The valid range is 150 to 2,000. The default is 250. [IpProfile_JitterBufMaxDelay] Voice Echo Canceler Enables the device's Echo Cancellation feature (i.e., echo from voice calls is removed). echo-canceller  [0] Disable [IpProfile_EnableEchoCance Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 420 Mediant 800B Gateway & E-SBC Parameter Description  ller] [1] Line (default)  [2] Acoustic For a detailed description of the Echo Cancellation feature, see Configuring Echo Cancellation on page 180. Note:  The corresponding global parameter is EnableEchoCanceller. Input Gain Defines the pulse-code modulation (PCM) input gain control (in decibels).
  • Page 421 [1] Supported only with SDP = re-INVITE is supported, but only with SDP. If the incoming re-INVITE arrives without SDP, the device creates an SDP and adds it to the outgoing re-INVITE.  [2] Supported = (Default) re-INVITE is supported with or without Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 422 Mediant 800B Gateway & E-SBC Parameter Description SDP. Remote Delayed Offer Defines whether the remote endpoint supports delayed offer (i.e., Support initial INVITEs without an SDP offer).  sbc-rmt-delayed-offer [0] Not Supported = Initial INVITE requests without SDP are not supported.
  • Page 423 Defines the handling of ISUP data for interworking between SIP and SIP-I endpoints. sbc-isup-body-handling  [0] Transparent = (Default) ISUP data is passed transparently (as [IpProfile_SBCISUPBodyHa is) between endpoints (SIP-I to SIP-I calls). ndling] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 424 Mediant 800B Gateway & E-SBC Parameter Description  [1] Remove = ISUP body is removed from INVITE messages.  [2] Create = ISUP body is added to outgoing INVITE messages. For more information on interworking SIP and SIP-I, see Interworking SIP and SIP-I Endpoints on page 713.
  • Page 425  [0] Standard = (Default) The SIP entity supports INVITE messages containing Replaces headers. The device forwards the INVITE message containing the Replaces header to the SIP entity. The Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 426 Mediant 800B Gateway & E-SBC Parameter Description device may change the value of the Replaces header to reflect the call identifiers of the leg.  [1] Handle Locally = The SIP entity does not support INVITE messages containing Replaces headers. The device terminates the received INVITE containing the Replaces header and establishes a new call between the SIP entity and the new call party.
  • Page 427 [0] Transparent = (Default) Device forwards SDP as is. [IPProfile_SBCRemoteHoldF  [1] Send Only = Device sends SDP with 'a=sendonly'. ormat]  [2] Send Only Zero ip = Device sends SDP with 'a=sendonly' and 'c=0.0.0.0'. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 428 Mediant 800B Gateway & E-SBC Parameter Description  [3] Inactive = Device sends SDP with 'a=inactive'.  [4] Inactive Zero ip = Device sends SDP with 'a=inactive' and 'c=0.0.0.0'.  [5] Not Supported = Used when remote side cannot identify a call- hold message.
  • Page 429 (answering) fax, and does not support renegotiation if it is the originating fax.  [2] No = The SIP entity does not support fax re-negotiation upon fax detection when it is the originating or terminating fax. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 430 Mediant 800B Gateway & E-SBC Parameter Description Note:  This feature is applicable only when both SIP entities do not fully support fax detection (receive or send) and negotiation: one SIP entity must be assigned an IP Profile where the parameter is set to [1] or [2], while the peer SIP entity must be assigned an IP Profile where the parameter is set to [2].
  • Page 431 RFC2198PayloadType parameter.  For the Gateway application only: The RTP redundancy dynamic payload type can be included in the SDP, by using the EnableRTPRedundancyNegotiation parameter.  The corresponding global parameter is RTPRedundancyDepth. Gateway Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 432 Mediant 800B Gateway & E-SBC Parameter Description Early Media Enables the Early Media feature for sending media (e.g., ringing) before the call is established. early-media  [0] Disable (default) [IpProfile_EnableEarlyMedia]  [1] Enable  Digital: The device sends a SIP 18x response with SDP, allowing the media stream to be established before the call is answered.
  • Page 433 Alerting message from the ISDN. It sends a 180+SDP response, signaling to the calling party to open a voice channel to hear the played ringback tone.  The corresponding global parameter is PlayRBTone2IP. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 434 Mediant 800B Gateway & E-SBC Parameter Description Progress Indicator to IP Defines the progress indicator (PI) sent to the IP.  prog-ind-to-ip [-1] = (Default) Not configured:  Analog: Default values are used (1 for FXO interfaces and 0 for [IpProfile_ProgressIndicator2 FXS interfaces).
  • Page 435 SIP entity associated with the IP Profile. If the call-limit number of concurrent calls reaches this limit, the device rejects any [IpProfile_CallLimit] new incoming and outgoing calls belonging to this IP Profile. The parameter can also be set to the following: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 436 Mediant 800B Gateway & E-SBC Parameter Description  [-1] = (Default) No limitation on calls.  [0] = All calls are rejected. Gateway DTMF Is DTMF Used Enables DTMF signaling.  [IpProfile_IsDTMFUsed] [0] Disable = (Default)  [1] Enable First Tx DTMF Option Defines the first preferred transmit DTMF negotiation method.
  • Page 437 [2] Event Only = The originating fax detects CNG and a fax session is started by the originating fax, using the Re-INVITE message. Typically, T.38 fax session starts when the preamble signal is Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 438 Mediant 800B Gateway & E-SBC Parameter Description detected by the answering fax. Some SIP devices do not support the detection of this fax signal on the answering fax and thus, in these cases, it is possible to configure the device to start the T.38 fax session when the CNG tone is detected by the originating fax.

  • Page 439: Configuring Tel Profile

    [2] 2 to [7]7 = Optional Parameter Suites that you can create based on any language (16 sensitivity levels, from 0 to 15). This requires a customized AMD Sensitivity file that needs to be installed on the device. For more information, contact your AudioCodes sales representative. Note: ...
  • Page 440 Mediant 800B Gateway & E-SBC The following procedure describes how to configure Tel Profiles through the Web interface. You can also configure it through ini file (TelProfile) or CLI (configure voip/coders-and- profiles tel-profile).  To configure a Tel Profile: Open the Tel Profiles table (Setup menu > Signaling & Media tab > Coders &...
  • Page 441 1007766 as the destination number, then after the call is answered it waits 1.5 seconds ('p') and plays the rest of the number (100) as DTMF digits. Additional examples: 1664wpp102, 66644ppp503, and 7774w100pp200. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 442 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter Note:  For the parameter to take effect, a device reset is required.  Analog interfaces: The called number can include characters 'p' (1.5 seconds pause) and 'd' (detection of dial tone). If character 'd' is used, it must be the first 'digit' in the called number.
  • Page 443 The valid range is 0 to 254. The default is 0 seconds for analog interfaces and 10 seconds for digital interfaces. Note that the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 444 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter Web interface denotes the default value (for analog and digital interfaces) as a string value of "255". Note:  The selected busy or reorder tone is according to the SIP release cause code received from IP.
  • Page 445 The current disconnect duration is configured by the CurrentDisconnectDuration parameter.  The current disconnect threshold (FXO only) is configured by the CurrentDisconnectDefaultThreshold parameter.  The frequency at which the analog line voltage is sampled is configured by the TimeToSampleAnalogLineVoltage parameter. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 446 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter  The corresponding global parameter is EnableCurrentDisconnect. DID Wink Enables Direct Inward Dialing (DID) using Wink-Start signaling, typically used for signaling between an E-911 switch and the enable-did-wink PSAP. [TelProfile_EnableDIDWink] ...
  • Page 447  [TelProfile_EnableEarlyMedia] [0] Disable (default)  [1] Enable  Digital: The device sends a SIP 18x response with SDP, allowing the media stream to be established before the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 448 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter call is answered.  Analog: The device sends a SIP 183 Session Progress response with SDP instead of a 180 Ringing, allowing the media stream to be established before the call is answered.
  • Page 449 For more information on Jitter Buffer, see 'Configuring the Dynamic Jitter Buffer' on page 195. Note:  For data (fax and modem) calls, configure the parameter to  The corresponding global parameter is DJBufOptFactor. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 450 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter Analog MWI MWI Analog Lamp Enables the visual display of message waiting indications (MWI). mwi-analog-lamp  [0] Disable (default). [TelProfile_MWIAnalog]  [1] Enable = Enables visual MWI by supplying line voltage of approximately 100 VDC to activate the phone's lamp.
  • Page 451 For FXO interfaces, a constant of 100 msec must be added to the required hook-flash period. For example, to generate a 450 msec hook-flash, configure the parameter to 550.  The corresponding global parameter is FlashHookPeriod. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 452 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 453: Gateway Application

    Part V Gateway Application...

  • Page 455: Introduction

    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. 20.1 Call Processing Summary The device's call processing for Gateway calls is shown in the following flowcharts. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 456 Mediant 800B Gateway & E-SBC  IP-to-Tel Call: Figure 20-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-10298...
  • Page 457 User's Manual 20. Introduction  Tel-to-IP Call: Figure 20-2: Tel-to-IP Call Processing Flowchart Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 458 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 459: Digital Pstn

    Release Note). • The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. • 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.
  • Page 460 Mediant 800B Gateway & E-SBC  To configure trunks: Open the Trunk Settings page (Setup menu > Signaling & Media tab > Gateway folder > Trunks & Groups > Trunks). 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 461: Tdm And Timing

    PSTN line interface. For a full description of the clock parameters, see 'PSTN Parameters' on page 1126.  To configure synchronization based on clock from PSTN line: Open the TDM Bus Settings page (Setup menu > Signaling & Media tab > Media Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 462: Configuring Internal Clock As Clock Source

    Mediant 800B Gateway & E-SBC folder > TDM Bus Settings), and then do the following: Figure 21-2: Configuring TDM Bus From the 'TDM Bus Clock Source' drop-down list (TDMBusClockSource), select Network to recover the clock from the line interface. In the 'TDM Bus Local Reference' field (TDMBusLocalReference), enter the trunk from which the clock is derived.

  • Page 463: Configuring Cas State Machines

    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 Apply, and then reset the device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 464 Mediant 800B Gateway & E-SBC Note: • 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 465: Configuring Digital Gateway Parameters

    Open the Digital Gateway Settings page (Setup menu > Signaling & Media tab > Gateway folder > Digital Gateway > Digital Gateway Settings). Figure 21-4: Digital Gateway Parameters Page Configure the parameters as required. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 466: Tunneling Applications

    Mediant 800B Gateway & E-SBC 21.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 21.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal...
  • Page 467 TrunkGroup 1 = 0,0,0,1,31,1000,1; TrunkGroup 1 = 0,1,1,1,31,2000,1; TrunkGroup 1 = 0,2,2,1,31,3000,1; TrunkGroup 1 = 0,3,3,1,31,4000,1; TrunkGroup 1 = 0,0,0,16,16,7000,2; TrunkGroup 1 = 0,1,1,16,16,7001,2; TrunkGroup 1 = 0,2,2,16,16,7002,2; TrunkGroup 1 = 0,3,3,16,16,7003,2; [/TrunkGroup] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 468 Mediant 800B Gateway & E-SBC [ AudioCodersGroups ] FORMAT AudioCodersGroups_Index = AudioCodersGroups_Name; AudioCodersGroups 0 = "AudioCodersGroups_0"; AudioCodersGroups 1 = "AudioCodersGroups_1"; [ \AudioCodersGroups ] [ AudioCoders ] AudioCoders 0 = "AudioCodersGroups_0", 0, 0, 3, 7, -1, 0, ""; AudioCoders 1 = "AudioCodersGroups_1", 0, 7, 2, 90, 56, 0, "";...

  • Page 469: Dsp Pattern Detector

    This is used, for example, to enable two QSIG subscribers connected to the same or different QSIG PBX to communicate with each other over an IP network. Tunneling is supported in both directions (Tel-to-IP and IP-to-Tel). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 470 Mediant 800B Gateway & E-SBC The term tunneling means that messages are transferred ‘as is’ to the remote side without being converted (QSIG > SIP > QSIG). The advantage of tunneling over QSIG-to-SIP interworking is that by using interworking, QSIG functionality can only be partially achieved.

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

    Switch. The default value of the Interface ID is identical to the number of the physical T1 trunk (0 for the first trunk, 1 for the second T1 trunk, and so on, up to the maximum number of trunks). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 472: Working With Dms-100 Switches

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

  • Page 473: Creating An Nfas-Related Trunk Configuration

    The device supports the following ISDN overlap dialing methods:  Collects ISDN called party number digits and then sends the SIP INVITE to the IP side Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC with the complete destination number (see 'Collecting ISDN Digits and Sending Complete Number in SIP' on page 474)  Interworks ISDN overlap dialing with SIP, according to RFC 3578 (see 'Interworking ISDN Overlap Dialing with SIP According to RFC 3578' on page 475) Note: ISDN overlap dialing is applicable to PRI and BRI.

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

    IP-to-Tel calls: • ISDNTxOverlap: Enables IP-to-Tel overlap dialing and defines how the device receives the collected digits from the IP side - in SIP re-INVITE [1] or INFO messages [2]. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC • TimeBetweenDigits: Defines the maximum time (in seconds) that the device waits between digits received from the IP side. When the time expires, the device uses the collected digits to dial the called destination number.

  • Page 477: Trunk Groups

    'Configuring Trunk Group Settings' on page 479).  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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 478 Mediant 800B Gateway & E-SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the telephony interface module for which you want to define the Trunk Group. module [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 479: Configuring Trunk Group Settings Table

    To configure Trunk Group settings: Open the Trunk Group Settings table (Setup menu > Signaling & Media tab > Gateway folder > Trunks & Groups > Trunk Group Settings). Click New; the following dialog box appears: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 480 Mediant 800B Gateway & E-SBC Configure a Trunk Group according to the parameters described in the table below. Click Apply. Table 22-2: Trunk Group Settings Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row.
  • Page 481 Supplementary Services table (see Configuring Multi-Line Extensions and Supplementary Services on page 575), allowing the routing of IP-to-Tel calls to specific BRI endpoints according to extension number. This option Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 482 Mediant 800B Gateway & E-SBC Parameter Description is applicable only to FXS and BRI interfaces.  [11] By Dest Number & Ascending = The device allocates a channels to incoming IP-to-Tel calls as follows: The device attempts to route the call to the channel that is associated with the destination (called) number.
  • Page 483 Proxy and Registration Parameters' on page 375), the routing rules in the Tel-to-IP Routing table take precedence over the selected Serving IP Group ID. MWI Interrogation Type Defines message waiting indication (MWI) QSIG-to-IP interworking Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 484 Mediant 800B Gateway & E-SBC Parameter Description mwi-interrogation-type for interrogating MWI supplementary services:  [TrunkGroupSettings_MWIInt [255] Not configured. errogationType]  [0] None = Disables the feature.  [1] Use Activate Only = MWI Interrogation messages are not sent and only "passively" responds to MWI Activate requests from the PBX.

  • Page 485: Routing

    SRD. As one of the attributes of a SIP Interface is an SRD and as you can configure multiple SIP Interfaces per SRD, the specific SIP Interface not only determines the above-mentioned attributes, but also the SRD for routing the call. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 486 Mediant 800B Gateway & E-SBC The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call.
  • Page 487 The following procedure describes how to configure Tel-to-IP routing rules through the Web interface. You can also configure it through ini file (Prefix) or CLI (configure voip > gateway routing tel2ip-routing). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 488 Mediant 800B Gateway & E-SBC  To configure Tel-to-IP routing rules: Open the Tel-to-IP Routing table (Setup menu > Signaling & Media tab > Gateway folder > Routing > Tel > IP Routing). Click New; the following dialog box appears: Figure 23-2: Tel-to-IP Routing Table - Add Dialog Box Configure a routing rule according to the parameters described in the table below.
  • Page 489 100 to 199 and ends with 100, 101 or 105. To denote any prefix, use the asterisk (*) symbol (default) or to denote calls without a calling number, use the $ sign. For a description of Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 490 Mediant 800B Gateway & E-SBC Parameter Description available notations, see 'Dialing Plan Notation for Routing and Manipulation Tables' on page 969. The number can include up to 50 digits. Destination Phone Prefix Defines the prefix and/or suffix of the called (destination) telephone number.
  • Page 491 (e.g., voice coder) per routing rule. To configure IP Profiles, see [PREFIX_ProfileName] 'Configuring IP Profiles' on page 405. Destination Port Defines the destination port to where you want to route the call. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 492 Mediant 800B Gateway & E-SBC Parameter Description dst-port [PREFIX_DestPort] Transport Type Defines the transport layer type used for routing the call:  transport-type [-1] = (Default) Not configured and the transport type is according to the settings of the global parameter, [PREFIX_TransportType] SIPTransportType.
  • Page 493 Cost Groups. For example, if the 'Default Call Cost' parameter in the Routing Policy is configured to Lowest Cost, even if the device locates matching routing rules that are assigned Cost Groups, the first-matched routing Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 494: Configuring Ip-To-Tel Routing Rules

    Mediant 800B Gateway & E-SBC Parameter Description rule without an assigned Cost Group is considered as the lowest cost route and thus, chosen as the preferred route. Charge Code Assigns a Charge Code to the routing rule for generating metering pulses (Advice of Charge).
  • Page 495 You can change this and apply number manipulation before processing the routing rule (see the RouteModeIP2Tel parameter). To configure number manipulation, see 'Configuring Source/Destination Number Manipulation' on page 513. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 496 Mediant 800B Gateway & E-SBC The following procedure describes how to configure IP-to-Tel routing rules through the Web interface. You can also configure it through ini file (PSTNPrefix) or CLI (configure voip > gateway routing ip2tel-routing).  To configure IP-to-Tel routing rules: Open the IP-to-Tel Routing table (Setup menu >...
  • Page 497 The source IP address can include the following wildcards:  "x": denotes single digits. For example, 10.8.8.xx represents all the addresses between 10.8.8.10 and 10.8.8.99.  "*": denotes any number between 0 and 255. For Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 498 Mediant 800B Gateway & E-SBC Parameter Description example, 10.8.8.* represents all addresses between 10.8.8.0 and 10.8.8.255. Source Phone Prefix Defines the prefix or suffix of the calling (source) telephone number. src-phone-prefix The prefix can include up to 49 digits. You can use special [PstnPrefix_SourcePrefix] notations for denoting the prefix.

  • Page 499: Configuring A Gateway Routing Policy Rule

    You can also configure it through ini file (GwRoutingPolicy) or CLI (configure voip > gateway routing gw-routing-policy).  To edit the Routing Policy rule: Open the Routing Policies table (Setup menu > Signaling & Media tab > Gateway folder > Routing > Routing Policies). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 500 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 23-4: Routing Policies Table - Edit Dialog Box Configure the Routing Policy rule according to the parameters described in the table below. Click Apply. Table 23-5: Routing Policies Table Parameter Descriptions...

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

    The device supports the following methods for checking the connectivity of IP destinations:  Network Connectivity: The device checks the network connectivity of the IP destination configured by the 'Alt Routing Tel to IP Connectivity Method' parameter: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 502: Alternative Routing Based On Ip Connectivity

    Mediant 800B Gateway & E-SBC • SIP OPTIONS: The device sends "keep-alive" SIP OPTIONS messages to the IP destination. If the device receives a SIP 200 OK in response, it considers the destination as available. If the destination does not respond to the OPTIONS message, then it is considered unavailable.
  • Page 503 IP connectivity.  To configure alternative Tel-to-IP routing based on IP connectivity: In the Tel-to-IP Routing table (see 'Configuring Tel-to-IP Routing Rules' on page 485), add alternative Tel-to-IP routing rules for specific calls. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 504: Alternative Routing Based On Sip Responses

    Mediant 800B Gateway & E-SBC Open the Routing Settings page (Setup menu > Signaling & Media tab > Gateway folder > Routing > Routing Settings): Figure 23-7: Configuring Alternative Tel-to-IP Routing based on Connectivity Under the Alternative Route group, do the following: From the 'Enable Alt Routing Tel to IP' (Tel2IPEnable) drop-down list, select Enable to enable alternative Tel-to-IP routing based on IP connectivity.
  • Page 505 (using the same INVITE) with the next configured (redundant) proxy in the list, and so on until an available redundant proxy is located. Once an available proxy is located, the device can operate in one of the following modes (configured by the ProxyRedundancyMode parameter): Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 506 Mediant 800B Gateway & E-SBC • Parking mode: The device continues operating with the redundant proxy (now active) until the next failure occurs, after which it switches to the next redundant proxy. • Homing mode: The device always attempts to operate with the primary proxy. In other words, it switches back to the primary proxy whenever it's available again.

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

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

  • Page 508: Pstn Fallback

    Mediant 800B Gateway & E-SBC 23.4.5 PSTN Fallback The PSTN Fallback feature enables the device to re-route a Tel-to-IP call to the legacy PSTN using one of its trunks if the IP destination is unavailable. For example, if poor voice quality is detected over the IP network, the device attempts to re-route the call to the PSTN.
  • Page 509 Configure Q.931 cause codes that invoke alternative IP-to-Tel routing: Open the Reasons for IP-to-Tel Alternative Routing table (Setup menu > Signaling & Media tab > Gateway folder > Routing > Alternative Routing Reasons > Reasons for IP > Tel). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 23-13: Reasons for IP-to-Tel Alternative Routing Table - Add Dialog Box Configure a Q.931 release cause code for alternative routing according to the parameters described in the table below.
  • Page 511 (i.e., IP address, port and transport type). Note:  If you do not specify a port, the device uses UDP port 5060.  When configured with a user@host, the original destination number is replaced by the user part. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 512: Alternative Routing Upon Isdn Disconnect

    SIP Trunk. This is configured using the ini file parameter, TR104FXOSwitchover. Note: For more information on this application, please contact your AudioCodes sales representative. User's Manual...

  • Page 513: Manipulation

    Source Phone Number Manipulation for Tel-to-IP Calls (up to 120 entries) • Destination Phone Number Manipulation for Tel-to-IP Calls (up to 120 entries)  IP-to-Tel calls: • Source Phone Number Manipulation for IP-to-Tel Calls (up to 120 entries) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 514 Mediant 800B Gateway & E-SBC • Destination Phone Number Manipulation for IP-to-Tel Calls (up to 120 entries) Configuration of number manipulation rules includes two areas:  Match: Defines the matching characteristics of the incoming call (e.g., prefix of destination number).
  • Page 515 Table 24-1: Configuration Examples of Source Phone Number Manipulation for Tel-to-IP Calls Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 516 Mediant 800B Gateway & E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Stripped Digits From Left Stripped Digits From Right Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Below is a description of each rule: ...
  • Page 517 The default is Any (i.e., any IP Group). [_SrcIPGroupID] Note: The parameter is applicable only to the Destination Phone Number Manipulation for IP-to-Tel Calls table and Source Phone Number Manipulation for IP-to-Tel Calls table. Action Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 518 Mediant 800B Gateway & E-SBC Parameter Description Stripped Digits From Left Defines the number of digits to remove from the left of the telephone number prefix. For example, if you enter 3 and the phone number is remove-from-left 5551234, the new phone number is 1234.

  • Page 519: Manipulating Number Prefix

    = location (number of digits counted from the left of the number) of a specific string in the original destination or source number. • l = number of digits that this string includes.  y = prefix to add at the specified location. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 520: Sip Calling Name Manipulations

    Mediant 800B Gateway & E-SBC For example, assume that you want to manipulate an incoming IP call with destination number "+5492028888888" (i.e., area code "202" and phone number "8888888") to the number "0202158888888". To perform such manipulation, the following configuration is...
  • Page 521 Figure 24-3: Calling Name Manipulation for IP-to-Tel Calls Table (Example) - Add Dialog Box Configure a manipulation rule according to the parameters described in the table below. Click Apply. Table 24-4: Calling Name Manipulation Tables Parameter Descriptions Parameter Description Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 522 Mediant 800B Gateway & E-SBC Parameter Description General Index Defines an index number for the new table row. [_Index] Note: Each row must be configured with a unique index. Name Defines an arbitrary name to easily identify the row. manipulation-name The valid value is a string of up to 20 characters.

  • Page 523: Configuring Redirect Number Ip To Tel

    Resource-Priority, or History-Info headers, which is then added to the Redirecting Number Information Element (IE) in the ISDN Setup message sent to the Tel side. This also includes the reason for the call redirection. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 524 Mediant 800B Gateway & E-SBC  Redirect Number Tel to IP table: Defines Tel-to-IP redirect number manipulation. You can manipulate the prefix of the redirect number received from the Tel side, in the outgoing SIP Diversion, Resource-Priority, or History-Info headers sent to the IP side.
  • Page 525 Defines the redirect telephone number prefix. redirect-prefix The default value is the asterisk (*) symbol (i.e., any number prefix). [_RedirectPrefix] Source Trunk Group ID Defines the Trunk Group from where the Tel call is received. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 526 Mediant 800B Gateway & E-SBC Parameter Description src-trunk-group-id To denote any Trunk Group, leave this field empty. The value -1 indicates that this field is ignored in the rule. [_SrcTrunkGroupID] Note: The parameter is applicable only to the Redirect Number Tel-to- IP table.
  • Page 527 Note: If you configure the parameter to Restricted and the 'AssertedIdMode' parameter to Add P-Asserted-Identity, the From header in the INVITE message includes the following: From: 'anonymous' <sip: anonymous@anonymous.invalid> and 'privacy: id' header. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 24.6 Manipulating Redirected and Diverted Numbers for Call Diversion You can configure manipulation rules to manipulate the Diverted-to and Diverting numbers received in the incoming Call Redirection Facility message for call diversion, which is interworked to outgoing SIP 302 responses.

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

    > Manipulation > Phone Contexts). Click New; the following dialog box appears: Figure 24-5: Phone Contexts Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 530 Mediant 800B Gateway & E-SBC Note: • You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'. In such a configuration, a Tel-to-IP call uses the first matching rule in the table. • To add the incoming SIP 'phone-context' parameter as a prefix to the outgoing...

  • Page 531: Configuring Release Cause Mapping

    To configure a SIP-to-ISDN release cause mapping rule: Open the Release Cause Mapping from SIP to ISDN table (Setup menu > Signaling & Media tab > Gateway folder > Manipulation > Release Cause SIP > ISDN). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 24-6: Release Cause Mapping from SIP to ISDN Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply.

  • Page 533: Isdn-To-Sip Release Cause Mapping

    T Q.850 release cause code (call failure) to SIP response code mapping rules. The table lets you override the default ISDN-to-SIP release cause mappings, listed in 'Fixed Mapping of ISDN Release Reason to SIP Response' on page 535. When the device receives an Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 534 Mediant 800B Gateway & E-SBC ISDN cause code from the PSTN side, it searches the table for a matching ISDN cause code. If found, the device sends the corresponding SIP response to the IP. If the ISDN cause code is not configured in the table, the default, fixed ISDN-to-SIP release reason mapping is used.

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

    503* Service unavailable Facility not subscribed 503* Service unavailable Incoming calls barred within CUG Forbidden Bearer capability not authorized Forbidden Bearer capability not presently available Service unavailable Service/option not available 503* Service unavailable Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 536: Configuring Isdn-To-Isdn Release Cause Mapping

    Mediant 800B Gateway & E-SBC ISDN Release Description Description Reason Response Bearer capability not implemented Not implemented Channel type not implemented 480* Temporarily unavailable Requested facility not implemented 503* Service unavailable Only restricted digital information bearer 503* Service unavailable capability is available...
  • Page 537 Table 24-12: Release Cause Mapping ISDN to ISDN Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [CauseMapIsdn2Isdn_Index] Note: Each row must be configured with a unique index. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 538: Reason Header

    Mediant 800B Gateway & E-SBC Parameter Description Orig. Q.850 Causes Defines the originally received ISDN Q.850 cause code. For example, you can enter "127" (without q850-causes apostrophes) to represent cause code 127 [CauseMapIsdn2Isdn_OrigIsdnReleaseCause] Interworking, Unspecified. The valid value (cause code) is 1 to 127.
  • Page 539 1/1 - International number in ISDN/Telephony numbering plan  1/2 - National number in ISDN/Telephony numbering plan  1/4 - Subscriber (local) number in ISDN/Telephony numbering plan  9/4 - Subscriber (local) number in Private numbering plan Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 540 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 541: Configuring Dtmf And Dialing

    998 can never be matched. But when the digit map is 99s|998, then after dialing the first two 9 digits, the device waits another two seconds within which the caller can enter the digit 8. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 542: External Dial Plan File

    Mediant 800B Gateway & E-SBC Below is an example of a digit map pattern containing eight rules: DigitMapping = 11xS|00[1- 7]xxx|8xxxxxxx|#xxxxxxx|*xx|91xxxxxxxxxx|9011x|xx.T In the example, the rule "00[1-7]xxx" denotes dialed numbers that begin with 00, and then any digit from 1 through 7, followed by three digits (of any number). Once the device receives these digits, it does not wait for additional digits, but starts sending the collected digits (dialed number) immediately.

  • Page 543: Configuring Hook Flash

    (in msec) for detection of a hook-flash event from an FXS interface. Detection is guaranteed for hook-flash periods of at least 60 msec (when configuring the period to 25). The device ignores hook-flash signals lasting a shorter period of time. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 544 Mediant 800B Gateway & E-SBC ♦ 'Max. Flash-Hook Detection Period' (FlashHookPeriod): Defines the maximum hook-flash period (in msec) for Tel and IP sides for FXS and FXO interfaces. For more information, see the Telprofile_FlashHookPeriod parameter in Configuring Tel Profiles on page 439.

  • Page 545: Configuring Supplementary Services

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

  • Page 547: Call Pickup

    (suspending the call) and then reconnected again (resuming the call). If the phone user does not resume the call within a user-defined interval (configured by the HeldTimeout parameter), the device releases the call. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 548: Consultation Feature

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

  • Page 549: Consultation Transfer For Qsig Path Replacement

    Q.931 Disconnect messages to the PBX, notifying the PBX that it can disconnect the ISDN calls (of user "A"). This feature is enabled by the QSIGPathReplacementMode parameter. Note: The feature is applicable only to digital interfaces. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 550: Blind Call Transfer

    Mediant 800B Gateway & E-SBC 26.5.3 Blind Call Transfer Blind call transfer is done (using SIP REFER messages) after a call is established between call parties A and B, and party A decides to immediately transfer the call to C without first speaking to C.

  • Page 551: Enabling Call Forwarding

    594. 26.6.2 Call Forward Reminder Ring The device supports the Call Forward Reminder Ring feature for FXS interfaces whereby the device's FXS endpoint emits a short ring burst when a third-party Application server Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 552 Mediant 800B Gateway & E-SBC (e.g., softswitch) forwards an incoming call to another destination. The ring is emitted only when the endpoint is in on-hook state. The feature is useful in that it notifies the endpoint user that a call forwarding service is currently being performed.

  • Page 553: Call Forward Reminder (Off-Hook) Special Dial Tone

    The special dial tone is used as a result of the device receiving a SIP NOTIFY message from a third-party softswitch providing the call forwarding service with the following SIP Alert-Info header: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 554: Bri Call Forwarding

    Mediant 800B Gateway & E-SBC Alert-Info: <http://127.0.0.1/Tono-Espec-Invitacion>;lpi- aviso=Desvio-Inmediato This special tone is a stutter dial tone (Tone Type = 15), as defined in the CPT file (see 'Call Progress Tones File' on page 775). The FXS phone user, connected to the device, activates the call forwarding service by dialing a special number (e.g., *21*xxxxx) and as a result, the device sends a regular SIP...
  • Page 555 INVITE sip:*72100@10.33.8.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.5:5060;branch=z9hG4bKWDSUKUHWFEXQSVOUVJGM From: <sip:400@10.33.2.5;user=phone>;tag=DUOROSXSOYJJLNBFRQTG To: <sip:*72100@10.33.8.53;user=phone> Call-ID: GMNOVQRRXUUCYCQSFAHS@10.33.2.5 CSeq: 1 INVITE Contact: <sip:400@10.33.2.5:5060> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE User-Agent: Sip Message Generator V1.0.0.5 User-to-User: 31323334;pd=4 Content-Type: application/sdp Content-Length: 155 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 556: Enabling Call Waiting

    Mediant 800B Gateway & E-SBC 26.7 Enabling Call Waiting The Call Waiting feature enables busy FXS endpoints connected to the device to accept an additional (second) call. If an incoming IP call is designated to a busy port, the called FXS endpoint hears a call waiting tone (several configurable short beeps) and can view the Caller ID of the incoming call (for Bellcore and ETSI Caller IDs).

  • Page 557: Message Waiting Indication

    ISDN PRI NI-2 Message Waiting Notification (MWN), sent in the ISDN Facility IE message. This is applicable when the device is connected to a PBX through an ISDN PRI trunk configured to NI-2. This is configured by setting the VoiceMailInterface parameter to [9]. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 558: Caller Id

    Mediant 800B Gateway & E-SBC  QSIG MWI: The device supports the interworking of QSIG MWI to IP (in addition to interworking of SIP MWI NOTIFY to QSIG Facility MWI messages). This provides interworking between an ISDN PBX with voice mail capabilities and a softswitch, which requires information on the number of messages waiting for a specific user.

  • Page 559: Debugging A Caller Id Detection On Fxo

    Verify that the correct FXO coefficient type is configured (see the CountryCoefficients parameter in 'Configuring FXS/FXO Coefficient Types' on page 600), as the device is unable to recognize caller ID signals that are distorted. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 560: Caller Id On The Ip Side

    Mediant 800B Gateway & E-SBC Connect a phone to the analog line of the PBX (instead of to the device's FXO interface) and verify that it displays the caller ID. If the above does not solve the problem, you need to record the caller ID signal (and send it to AudioCodes), as described below.

  • Page 561: Three-Way Conferencing

    The device supports the following three-way conference modes:  Conference Managed by External, AudioCodes Conferencing (Media) Server: The conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.
  • Page 562 Mediant 800B Gateway & E-SBC ♦ Configure the device with an Inbound Manipulation rule that is applied to calls received from the third-party network entity so that the device considers conference calls as regular calls and forwards them to the Conference server without getting involved in the conferencing setup.

  • Page 563: Emergency E911 Phone Number Services

    (e.g., police) to the caller's location. Typically, the dialed emergency number is routed to the appropriate PSAP by the telephone company's switch, known as a 911 Selective Router (or E911 tandem switch). If Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC the PSAP receives calls from the telephone company on old-style digital trunks, they are specially formatted Multi-Frequency (MF) trunks that pass only the calling party's number (known as Automatic Number Identification - ANI). Once the PSAP receives the call, it searches for the physical address that is associated with the calling party's telephone number (in the Automatic Location Identification database - ALI).
  • Page 565 Typically, the MF spills are sent from the E911 tandem switch to the PSAP, as shown in the table below: Table 26-1: Dialed MF Digits Sent to PSAP Digits of Calling Number Dialed MF Digits 8 digits "nnnnnnnn" (ANI) "KPnnnnnnnnST" 12 digits "nnnnnnnnnnnn" (ANI) "KPnnnnnnnnnnnnSTP" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 566 Mediant 800B Gateway & E-SBC Digits of Calling Number Dialed MF Digits 12 digits ANI and 10 digits PANI "KPnnnnnnnnnnnnSTKPmmmmmmmmmmST" two digits "nn" "KPnnSTP" The MF KP, ST, and STP digits are mapped as follows:  * for KP ...

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

    PSAP, the device generates a SIP INFO message that includes a "hookflash" body, or sends RFC 2833 hookflash Telephony event (according to the HookFlashOption parameter). Following the "hookflash" Wink signal, the PSAP sends DTMF digits. These digits are Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 568 Mediant 800B Gateway & E-SBC detected by the device and forwarded to the IP, using RFC 2833 telephony events (or inband, depending on the device's configuration). Typically, this Wink signal followed by the DTMF digits initiates a call transfer. For supporting the E911 service, used the following configuration parameter settings: ...
  • Page 569 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.7.20A.000.038 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 Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC t=0 0 m=audio 4000 RTP/AVP 8 0 101 a=rtpmap:8 pcma/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv  Example B: The detection of a Wink signal generates the following SIP INFO message: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060...

  • Page 571: Multilevel Precedence And Preemption

    Table 26-3: MLPP Call Priority Levels (Precedence) and DSCP Configuration Parameters MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header 0 (lowest) routine MLPPRoutineRTPDSCP priority MLPPPriorityRTPDSCP immediate MLPPImmediateRTPDSCP flash MLPPFlashRTPDSCP flash-override MLPPFlashOverRTPDSCP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 572 Mediant 800B Gateway & E-SBC MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header 9 (highest) flash-override-override MLPPFlashOverOverRTPDSCP The device automatically interworks the network identity digits (NI) in the ISDN Q.931 Precedence Information Element (IE) to the network domain subfield of the INVITE's Resource-Priority header, and vice versa.

  • Page 573: Mlpp Preemption Events In Sip Reason Header

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

  • Page 574: Precedence Ring Tone

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

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

    Progress Indicator in the Setup Ack bit (0x10000=65536). Therefore, the recommended value is 0x10000 + 0 x1000 = 65536 + 4096 = 69632 (i.e., set the ISDNInCallsBehavior parameter to 69632). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 576 Mediant 800B Gateway & E-SBC The following procedure describes how to configure the Supplementary Services table through the Web interface. You can also configure it through ini file (ISDNSuppServ) or CLI (configure voip > gateway digital isdn-supp-serv).  To configure endpoint supplementary services: Open the Supplementary Services table (Setup menu >...
  • Page 577 Determines whether the endpoint sends its Caller ID information to the IP when a call is made. presentation-restricted  [0] Allowed = The device sends the string defined in [ISDNSuppServ_IsPresentationRestricted] the 'Caller ID' field when this endpoint makes a Tel-to- Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 578: 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 579 In the Charge Codes table, configure Charge Codes (see 'Configuring Charge Codes' on page 580). In the Tel-to-IP Routing table, assign the Charge Code index to the relevant Tel-to-IP routing rule (see 'Configuring Tel-to-IP Routing Rules' on page 485). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 580: Configuring Charge Codes

    Mediant 800B Gateway & E-SBC • AOC in Tel-to-IP Direction: Open the Supplementary Services Settings page, and then configure the 'AoC Support' parameter to Enable to send AOC to IP. Figure 26-15: Configuring AOC Method • AOC in IP-to-Tel Direction: Open the Supplementary Services page, and then...
  • Page 581 Once the call is established, the device generates a pulse for pulse-interval-<1-4> each pulse interval. [ChargeCode_PulseInterval<1-4>] Pulses On Answer (1 - 4) Defines the number of pulses that the device generates upon call answer. pulses-on-answer-<1-4> [ChargeCode_PulsesOnAnswer<1- 4>] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 582: Configuring Voice Mail

    Mediant 800B Gateway & E-SBC 26.18 Configuring Voice Mail The Voice Mail Settings page lets you configure voice mail. For more information on voice mail, refer to the CPE Configuration Guide for Voice Mail User's Manual. For a detailed description of the voice mail parameters, see 'Voice Mail Parameters' on page 1094.

  • Page 583: Converting Accented Characters From Ip To Tel

    (analog or digital). Typically, the device receives the caller ID and calling name in Unicode characters (in the SIP INVITE message). Unicode characters consist of two bytes, while ASCII characters consist of one byte. Accented characters are used in various Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 584 Mediant 800B Gateway & E-SBC languages such as German. An example of such a character is the umlaut (or diaeresis), which consists of two dots placed over a letter, as in ä. The importance of this conversion feature is that it allows PSTN entities that do not support accented characters, to receive ASCII characters.
  • Page 585 The valid value is a string of up to four characters. [CharConversion_ConvertedOutput] The valid value is up to four ASCII characters. This can include any ASCII character - alphanumerical (e.g., a, A, 6) and/or symbols (e.g., !, ?, _, &). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 586 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 587: Analog Gateway

    To configure keypad sequences: Open the Keypad Features page (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Keypad Features). Figure 27-1: Configuring Phone Key Sequences to Activate Various Services Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 588: Configuring Metering Tones

    Mediant 800B Gateway & E-SBC Configure the keypad features as required. Click Apply. 27.2 Configuring Metering Tones The FXS interfaces can generate 12/16 KHz metering pulses toward the Tel side (e.g., for connection to a pay phone or private meter). Tariff pulse rate is according to the device's Charge Codes table.

  • Page 589: Configuring Authentication

    For all endpoints: Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP Definitions folder > Proxy & Registration), and then configure the 'Authentication Mode' (AuthenticationMode) parameter to Per Endpoint: Figure 27-4: Enabling Authentication per Endpoint Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 590 Mediant 800B Gateway & E-SBC • Endpoints per Trunk Group: Open the Trunk Group Settings table (see 'Configuring Trunk Group Settings' on page 479), and then for the required Trunk Group ID, configure the 'Registration Mode' parameter to Per Endpoint (TrunkGroupSettings_RegistrationMode).

  • Page 591: Configuring Automatic Dialing

    [TargetOfChannel_Index] Module (Read-only) Displays the module number on which the port is located. [TargetOfChannel_Module] Port (Read-only) Displays the port number. port [TargetOfChannel_Port] Port Type (Read-only) Displays the port type (FXS or FXO). [TargetOfChannel_PortType] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 592: Configuring Caller Display Information

    Mediant 800B Gateway & E-SBC Parameter Description Destination Phone Number Defines the destination telephone number to automatically dial. dst-number [TargetOfChannel_Destination] Auto Dial Status Enables automatic dialing.  auto-dial-status [0] Disable = Automatic dialing for the specific port is disabled. [TargetOfChannel_Type] ...
  • Page 593 [CallerDisplayInfo_Port] Port Type (Read-only) Displays the port type (FXS or FXO). [CallerDisplayInfo_PortType] Caller Display Display String Defines the Caller ID string. display-string The valid value is a string of up to 18 characters. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 594: Configuring Call Forward

    Mediant 800B Gateway & E-SBC Parameter Description [CallerDisplayInfo_DisplayString] Note: If you configure the parameter to "Private" or "Anonymous", Caller ID is restricted and the settings of the 'Presentation' parameter is ignored. Presentation Enables the sending of the caller ID string.
  • Page 595 'No Reply Time' field.  [5] Don't Disturb = Immediately reject incoming calls. Call Forward Forward Destination Defines the telephone number or URI (<number>@<IP address>) to where the call is forwarded. destination Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 596: Configuring Caller Id Permissions

    Mediant 800B Gateway & E-SBC Parameter Description [FwdInfo_Destination] Note: If the parameter is configured with only a telephone number and a Proxy isn't used, this forwarded-to phone number must be specified in the Tel-to-IP Routing table (see 'Configuring Tel-to-IP Routing Rules' on page 485).

  • Page 597: Configuring Call Waiting

    The section is applicable only to FXS interfaces. The following procedure describes how to configure call waiting per port through the Web interface. You can also configure it through ini file (CallWaitingPerPort) or CLI (configure voip > gateway analog call-waiting). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 598: Rejecting Anonymous Calls

    Mediant 800B Gateway & E-SBC  To enable call waiting per port: Open the Call Waiting table (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Call Waiting). Select the row corresponding to the port that you want to configure, and then click Edit;...

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

    4 when a call is received from a calling (source) number with prefix 2. Configure distinctive ringing and call waiting tones per port according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 600: Fxs/Fxo Coefficient Types

    Mediant 800B Gateway & E-SBC Table 27-7: Tone index Table Parameter Description Parameter Description Index Defines the table index entry. Up to 50 entries can be defined. FXS Port First Defines the first port in the FXS port range. fxs-port-first...

  • Page 601: Fxo Operating Modes

    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. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 602 Mediant 800B Gateway & E-SBC One-stage dialing incorporates the following FXO functionality:  Waiting for Dial Tone: Enables the device to dial the digits to the Tel side only after detecting a dial tone from the PBX line. The ini file parameter IsWaitForDialTone is used to configure this operation.

  • Page 603: Two-Stage Dialing

    DID wink enables the originating end to seize the line by going off-hook. It waits for acknowledgment 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 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & 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 605: Collecting Digits Mode

    Refer-To header), and then drops the line (on-hook). Note that the time between flash to dial is according to the WaitForDialTime parameter. • PBX performs the transfer internally  Hold / Transfer toward the IP side: The FXO device doesn't initiate hold / transfer as Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 606: Call Termination On Fxo Devices

    Mediant 800B Gateway & E-SBC 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. 27.13.3 Call Termination on FXO Devices This section describes the device's call termination capabilities for its FXO interfaces: ...

  • Page 607: Call Termination Before Call Establishment

    To call a remote office worker, a PBX user or a PSTN caller simply dials the PBX extension that is mapped to the remote FXS port. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC This section provides an example on how to implement a remote telephone extension through the IP network, using FXO andFXS interfaces. In this configuration, the FXO device routes calls received from the PBX to the ‘Remote PBX Extension’ connected to the FXS device.

  • Page 609: Dialing From Pbx Line Or Pstn

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

  • Page 610: Fxs Gateway Configuration

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

  • Page 611: Fxo Gateway Configuration

    IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. Figure 27-18: FXO Tel-to-IP Routing Configuration In the FXO Settings page (see 'Configuring FXO Parameters' on page 588), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 612 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 613: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 615: Sbc Overview

    (B2BUA) leg routing: • Strips all incoming SIP Via header fields and creates a new Via value for the outgoing message. • Each leg has its own Route/Record Route set. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 616: B2Bua And Stateful Proxy Operating Modes

    Mediant 800B Gateway & E-SBC • User-defined manipulation of SIP To, From, and Request-URI host names. • Generates a new SIP Call-ID header value (different between legs). • Changes the SIP Contact header and sets it to the device's address.
  • Page 617 SIP specific headers (e.g., Replaces) or in the message bodies (e.g. Dialog Info in an XML body).  In some setups, the SIP client authenticates using a hash that is performed on one or Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 618 Mediant 800B Gateway & E-SBC more of the headers that B2BUA changes (removes). Therefore, implementing B2BUA would cause authentication to fail.  For facilitating debugging procedures, some administrators require that the value in the Call-ID header remains unchanged between the inbound and outbound SBC legs.

  • Page 619: Call Processing Of Sip Dialog Requests

    URLs are determined, the user and host parts of the URLs can be used as matching rule characteristics for classification, message manipulation, and call routing. • All SIP requests (e.g., INVITE) except REGISTER: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 620 Mediant 800B Gateway & E-SBC ♦ Source URL: Obtained from the From header. If the From header contains the value 'Anonymous', the source URL is obtained from the P-Preferred- Identity header. If the P-Preferred-Identity header does not exist, the source URL is obtained from the P-Asserted-Identity header.

  • Page 621: User Registration

    The device provides a dynamic registration database that it updates according to registration requests traversing it. Each database entry for a user represents a binding between an AOR (obtained from the SIP To header), optional additional AORs, and one or Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 622: Classification And Routing Of Registered Users

    Mediant 800B Gateway & E-SBC more contacts (obtained from the SIP Contact headers). Database bindings are added upon successful registration responses from the proxy server (SIP 200 OK). The device removes database bindings in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero).

  • Page 623: General Registration Request Processing

     The graceful period is also used before removing a user from the registration database when the device receives a successful unregister response (200 OK) from Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 624: Registration Restriction Control

    Mediant 800B Gateway & E-SBC the registrar/proxy server. This is useful in scenarios, for example, in which users (SIP user agents) such as IP Phones erroneously send unregister requests. Instead of immediately removing the user from the registration database upon receipt of a...

  • Page 625: Media Anchoring

    The Media Realm assigned to the leg's IP Group (in the IP Groups table) is used. If not assigned to the IP Group, the Media Realm assigned to the leg's SIP Interface (in the SIP Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 626: Direct Media

    Mediant 800B Gateway & E-SBC Interfaces table) is used. The following figure provides an example of SDP handling for a call between a LAN IP Phone 10.2.2.6 and a remote IP Phone 212.179.1.13 on the WAN. Figure 28-3: SDP Offer/Answer Example 28.5.2 Direct Media...
  • Page 627 Microsoft Server (direct media is required in the Skype for Business environment). For more information, see 'Configuring IP Groups' on page 344. IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 628: Restricting Audio Coders

    Mediant 800B Gateway & E-SBC Direct Media' parameter is set to Enable (SIPInterface_SBCDirectMedia = 1). IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Direct Media' parameter Enable When Single (SIPInterface_SBCDirectMedia = 2), and the endpoints are located behind the same NAT.

  • Page 629: Coder Transcoding

    Since this coder was not included in the original incoming SDP offer from the LAN IP phone, the device performs G.729-G.711 transcoding between the inbound and outbound legs. Figure 28-5: Transcoding using Extended Coders (Example) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 630 Mediant 800B Gateway & E-SBC Note: • • If you assign a SIP entity an Allowed Audio Coders Group for coder restriction (allowed coders) and a Coders Group for extension coders, the allowed coders take precedence over the extension coders. In other words, if an extension coder is not listed as an allowed coder, the device does not add the extension coder to the SDP offer.
  • Page 631 In the IP Profiles table, configure the IP Profile associated with the SIP entity: Assign the Coders Group to the IP Profile, using the 'Extension Coders Group' parameter (SBCExtensionCodersGroupName). Enable extension coders by configuring the 'Allowed Coders Mode' parameter to Restriction or Restriction and Preference. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 632: Transcoding Mode

    Mediant 800B Gateway & E-SBC Note: • To implement transcoding, you must configure the number of required DSP channels for transcoding (for example, MediaChannels = 120). Each transcoding session uses two DSP resources. • The transcoding mode can be configured globally, using the TranscodingMode parameter or for specific calls, using the IP Profiles table.

  • Page 633: Srtp-Rtp And Srtp-Srtp Transcoding

    (negotiate) BFCP streams between clients. The BFCP stream is identified in the SDP as 'm=application <port> UDP/BFCP' and a dedicated UDP port is used for the BFCP streams. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 634: Interworking Miscellaneous Media Handling

    Mediant 800B Gateway & E-SBC 28.5.9 Interworking Miscellaneous Media Handling This section describes various interworking features relating to media handling. 28.5.9.1 Interworking DTMF Methods The device supports interworking between various DTMF methods such as RFC 2833, In- Band DTMF’s, and SIP INFO (Cisco\Nortel\Korea). By default, the device allows the remote user agents to negotiate (in case of RFC 2833) and passes DTMF without intervention.

  • Page 635: Interworking Crypto Lifetime Field

    (i.e., after 200 OK) and within a user-defined interval. If detected, it can then handle the subsequent fax renegotiation by sending re-INVITE messages to both SIP entities (originating and terminating faxes). For more information, see the parameter in 'Configuring IP Profiles' on page 405. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 636: Limiting Sbc Call Duration

    Mediant 800B Gateway & E-SBC Note: The voice-related coder configuration (Allowed and Extension coders) is independent of the fax-related coder configuration, with the exception of the G.711 coder. If the G.711 coder is restricted by the Allowed Audio Coders Groups table, it is not used for fax processing even if it is listed in the Coder Groups table for faxes.

  • Page 637: User Authentication Based On Radius

    SIP method. The configuration method for assigning specific SIP message handling modes to UAs, includes configuring an IP Profile with the required interworking mode, and then assigning the IP Profile to the relevant IP Group. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 638: Interworking Sip 3Xx Redirect Responses

    Mediant 800B Gateway & E-SBC This section describes some of the device's support for handling SIP methods to ensure interoperability. 28.9.1 Interworking SIP 3xx Redirect Responses The device supports interworking of SIP 3xx redirect responses. By default, the device's handling of SIP 3xx responses is to send the Contact header unchanged. However, some SIP UAs may support different versions of the SIP 3xx standard while others may not even support SIP 3xx.

  • Page 639: Local Handling Of Sip 3Xx

    Routing table rules. (where the 'Call Trigger' field is set to 3xx). It is also possible to specify the IP Group that sent the 3xx request as matching criteria for the re-routing rule in this table ('ReRoute IP Group ID' field). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 28.9.2 Interworking SIP Diversion and History-Info Headers This device can be configured to interwork between the SIP Diversion and History-Info headers. This is important, for example, to networks that support the Diversion header but not the History-Info header, or vice versa. Therefore, mapping between these headers is crucial for preserving the information in the SIP dialog regarding how and why (e.g., call...

  • Page 641: Interworking Sip Prack Messages

    28.9.6 Interworking SIP Early Media The device supports early media. Early media is when the media flow starts before the SIP call is established (i.e., before the 200 OK response). This occurs when the first SDP offer- Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 642 Mediant 800B Gateway & E-SBC answer transaction completes. The offer-answer options can be included in the following SIP messages:  Offer in first INVITE, answer on 180, and no or same answer in the 200 OK  Offer in first INVITE, answer on 180, and a different answer in the 200 OK (not standard) ...
  • Page 643 Media RTP Detection Mode', '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-8: SBC Early Media RTP 18x without SDP Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 644: Interworking Sip Re-Invite Messages

    Mediant 800B Gateway & E-SBC Figure 28-9: Early Media RTP - SIP 18x with SDP 28.9.7 Interworking SIP re-INVITE Messages The device supports interworking of SIP re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs.

  • Page 645: Interworking Sip Update Messages

    Interworking the play of the held tone for IP entities that cannot play held tones locally. This is configured by the IP Profile parameter, 'SBC Play Held Tone'.  Interworking generation of held tone where the device generates the tone to the held Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 646: Interworking Sip Via Headers

    Mediant 800B Gateway & E-SBC party instead of the call hold initiator. This is configured by the IP Profile parameter, 'SBC Reliable Held Tone Source'. To configure IP Profiles, see 'Configuring IP Profiles' on page 405. 28.9.12 Interworking SIP Via Headers The device supports the interworking of SIP Via headers between SIP entities.

  • Page 647: Enabling The Sbc Application

    Open the Applications Enabling page (Setup menu > Signaling & Media tab > Core Entities folder > Applications Enabling). From the 'SBC Application' drop-down list, select Enable: Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 648 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 649: Utilizing Gateway Channel Resources For Sbc

    To support the feature, the License Key installed on your device must include the "TDMtoSBC" feature key; otherwise, to purchase the feature, contact your AudioCodes sales representative to upgrade your License Key. • The maximum number of SBC sessions that can be supported is according to the device's maximum SBC capacity (see 'Channel Capacity' on page 1239).
  • Page 650 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 651: Configuring General Sbc Settings

    XML body. Below is an example of an XML body where the call-id, tags, and URIs have been replaced by the device: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="10" state="partial" entity="sip:alice@example.com"> <dialog id="zxcvbnm3" call-id="67402270@10.132.10.150" local-tag="1c137249965" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 652 Mediant 800B Gateway & E-SBC remote-tag="CCDORRTDRKIKWFVBRWYM" direction="initiator"> <state event="replaced">terminated</state> </dialog> <dialog id="sfhjsjk12" call-id="67402270@10.132.10.150" local-tag="1c137249965" remote-tag="CCDORRTDRKIKWFVBRWYM" direction="receiver"> <state reason="replaced">confirmed</state> <replaces call-id="67402270@10.132.10.150" local-tag="1c137249965" remote-tag="CCDORRTDRKIKWFVBRWYM"/> <referred-by> sip:bob-is-not-here@vm.example.net </referred-by> <local> <identity display="Jason Forster"> sip:jforsters@home.net </identity> <target uri="sip:alice@pc33.example.com"> <param pname="+sip.rendering" pval="yes"/> </target> </local> <remote> <identity display="Cathy Jones">...

  • Page 653: Configuring Admission Control

    (e.g., of 200). Requests that reach the user-defined call limit (maximum concurrent calls and/or call rate) are sent to an alternative route if configured in the IP-to-IP Routing table. If no alternative Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 654 Mediant 800B Gateway & E-SBC routing rule exists, the device rejects the SIP request with a SIP 480 "Temporarily Unavailable" response. Note: The device applies the CAC rule for the incoming leg immediately after the Classification process. If the call/request is rejected at this stage, no routing is performed.
  • Page 655 Reserved call capacity must be less than the maximum capacity (limit) configured for the CAC rule (see the 'Limit' parameter below).  The total reserved call capacity configured for all CAC rules must be within the device's total call capacity support. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 656 Mediant 800B Gateway & E-SBC Parameter Description Limit Defines the maximum number of concurrent SIP dialogs per IP Group, SIP Interface or SRD. You can also use the following special values: limit  [0] 0 = Block all these dialogs.

  • Page 657: Routing Sbc

    Open the SBC General Settings (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings). From the 'Unclassified Calls' drop-down list, select Reject to reject unclassified calls or Allow to accept unclassified calls: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 658 Mediant 800B Gateway & E-SBC Click Apply. If the parameter is set to Allow, the incoming SIP dialog is assigned to an IP Group as follows: The device determines on which SIP listening port (e.g., 5061) the incoming SIP dialog request was received and the SIP Interface configured with this port (in the SIP Interfaces table).
  • Page 659 Proxy Set feature). • The device saves incoming SIP REGISTER messages in its registration database. If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 660 Mediant 800B Gateway & E-SBC The flowchart below illustrates the classification process: Figure 33-1: Classification Process (Identifying IP Group or Rejecting Call) The following procedure describes how to configure Classification rules through the Web interface. You can also configure it through ini file (Classification) or CLI (configure voip >...
  • Page 661 SIP dialog. src-sip-interface-name The default is Any (i.e., all SIP Interfaces belonging to the [Classification_SrcSIPInterfaceName] SRD assigned to the rule). Note: The SIP Interface must belong to the SRD assigned Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 662 Mediant 800B Gateway & E-SBC Parameter Description to the rule (see the 'SRD' parameter in the table). Source IP Address Defines a source IP address as a matching characteristic for the incoming SIP dialog. src-ip-address The valid value is an IP address in dotted-decimal notation.
  • Page 663 SRD's assigned Routing Policy. By default, no value is defined. To configure Routing Policies, see 'Configuring SBC Routing Policy Rules' on page 680. Source IP Group Assigns an IP Group to the matched incoming SIP dialog. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Parameter Description src-ip-group-name By default, no value is defined. [Classification_SrcIPGroupName] To configure IP Groups, see 'Configuring IP Groups' on page 344. Note: The IP Group must be associated with the assigned SRD (see the 'SRD' parameter in the table).

  • Page 665: Configuring Message Condition Rules

    Message Manipulations Quick Reference Guide. The following procedure describes how to configure Message Condition rules through the Web interface. You can also configure it through ini file (ConditionTable) or CLI (configure voip > sbc routing condition-table). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC  To configure a Message Condition rule: Open the Message Conditions table (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Conditions). Click New; the following dialog box appears: Figure 33-3: Message Conditions Table - Add Dialog Box Configure a Message Condition rule according to the parameters described in the table below.
  • Page 667 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 668 Mediant 800B Gateway & E-SBC To configure and apply an IP-to-IP Routing rule, the rule must be associated with a Routing Policy. The Routing Policy associates the routing rule with an SRD(s). Therefore, the Routing Policy lets you configure routing rules for calls belonging to specific SRD(s).
  • Page 669 For more information on tags, see 'Configuring Dial Plans' on Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 670 Mediant 800B Gateway & E-SBC page 697. Note: Call forking is not applicable to LDAP-based IP-to-IP routing rules. The following procedure describes how to configure IP-to-IP routing rules through the Web interface. You can also configure it through ini file (IP2IPRouting) or CLI (configure voip >...
  • Page 671 Reasons' on page 677). However, if no response, ICMP, or a SIP 408 response is received, the device attempts to use the alternative route even if no entries are configured in the Alternative Routing Reasons table. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 672 Mediant 800B Gateway & E-SBC Parameter Description  Multiple alternative route entries can be configured (e.g., Index 1 is the main route - Route Row - and indices 2 through 4 are configured as alternative routes). Match Source IP Group Defines the IP Group from where the IP call is received (i.e., the...
  • Page 673 Broken RTP Connection feature is enabled (IpProfile_DisconnectOnBrokenConnection parameter is configured to [2]), you can use this option as an explicit matching characteristics to route the call to an alternative destination. Therefore, for alternative routing upon Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 674 Mediant 800B Gateway & E-SBC Parameter Description broken RTP detection, position the routing rule configured with this option above the regular routing rule associated with the call. Such a configuration setup ensures that the device uses this alternative routing rule only when RTP broken connection is detected.
  • Page 675 The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in this table). For more information, see 'Configuring SBC Routing Policy Rules' on page 680. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 676 Mediant 800B Gateway & E-SBC Parameter Description Destination SIP Interface Defines the destination SIP Interface to where the call is sent. dst-srd-id By default, no value is defined. [IP2IPRouting_DestSIPInterfaceN To configure SIP Interfaces, see 'Configuring SIP Interfaces' on ame] page 336.

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

    Typically, the device performs alternative routing when there is no response at all to an INVITE message. This is done after a user-defined number of INVITE re-transmissions, configured by the SIPMaxRtx parameter. In such a scenario, the device issues itself the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 678 Mediant 800B Gateway & E-SBC SIP response code 408 (Request Timeout). Alternative routing is only done if you have configured the response code in the Alternative Routing Reasons table. You can also configure alternative routing for the following proprietary response codes, if configured in the table, that are issued by the device itself: ...
  • Page 679 Unavailable; [504] Server Timeout; [505] Version Not Supported; [513] Message Too Large; [600] Busy Everywhere; [603] Decline; [604] Does Not Exist Anywhere; [606] Not Acceptable; [805] Admission Failure; [806] Media Limits Exceeded; [818] Signalling Limits Exceeded. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 680: Configuring Sbc Routing Policy Rules

    Mediant 800B Gateway & E-SBC 33.5 Configuring SBC Routing Policy Rules The Routing Policies table lets you configure up to 41 Routing Policy rules. A Routing Policy determines the routing and manipulation (inbound and outbound) rules per SRD in a multiple SRD configuration topology.
  • Page 681 If the device receives incoming calls (e.g., INVITE) from users that have already been classified and registered in the device's registration database, the device ignores the Classification table and uses the Routing Policy that was determined for the user during the initial classification process. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 682 Mediant 800B Gateway & E-SBC The following procedure describes how to configure Routing Policies rules through the Web interface. You can also configure it through ini file (SBCRoutingPolicy) or CLI (configure voip > sbc routing sbc-routing-policy).  To configure a Routing Policy rule: Open the Routing Policies table (Setup menu >...
  • Page 683 1. Therefore, a call of 1 minute cost 7 units. Therefore, for calls under one minute, "Weekend A" carries the lower cost. However, if the average call duration is more than one minute, "Weekend B" carries the lower cost. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 684 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 685: Sbc Manipulations

    IP Groups respectively (if any, in the IP Groups 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 686 Mediant 800B Gateway & 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 687: Configuring Ip-To-Ip Inbound Manipulations

    Routing Policy ("Default_SBCRoutingPolicy"), when only one Routing Policy is required, the device automatically assigns the default Routing Policy to the routing rule. If you are implementing LDAP-based routing (with or without Call Setup Rules) and/or Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 688 Mediant 800B Gateway & E-SBC Least Cost Routing (LCR), you need to configure these settings for the Routing Policy (regardless of the number of Routing Policies employed). For more information on Routing Policies, see 'Configuring SBC Routing Policy Rules' on page 680.
  • Page 689 [2] REGISTER = Only REGISTER messages.  [3] SUBSCRIBE = Only SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 690 Mediant 800B Gateway & E-SBC Parameter Description Source IP Group Defines the IP Group from where the incoming INVITE is received. CLI: src-ip-group-name The default is Any (i.e., any IP Group). [IPInboundManipulation_Sr cIpGroupName] Source Username Prefix Defines the prefix of the source SIP URI user name (usually in the CLI: src-user-name-prefix From header).

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

    IP Groups, respectively. The following procedure describes how to configure Outbound Manipulations rules through the Web interface. You can also configure it through ini file (IPOutboundManipulation) or CLI (configure voip > sbc manipulation ip-outbound-manipulation). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 692 Mediant 800B Gateway & E-SBC  To configure Outbound Manipulation rules: Open the Outbound Manipulations table (Setup menu > Signaling & Media tab > SBC folder > Manipulation > Outbound Manipulations). Click New; the following dialog box appears: Figure 34-3: Outbound Manipulations Table- Add Dialog Box Configure an Outbound Manipulation rule according to the parameters described in the table below.
  • Page 693 The default value is the asterisk (*) symbol (i.e., any source [IPOutboundManipulation_Src username prefix). The prefix can be a single digit or a range of UsernamePrefix] digits. For available notations, see 'Dialing Plan Notation for Routing and Manipulation' on page 969. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 694 Mediant 800B Gateway & E-SBC Parameter Description Note: If you need to manipulate calls of many different source URI user names, you can use tags (see 'Source Tags' parameter below) instead of this parameter. Source Host Defines the source SIP URI host name - full name, typically in the From header.
  • Page 695 Destination URI, you can configure the parameter to a string of up 49 characters. If you set the 'Manipulated Item' parameter to Calling Name, you can configure the parameter to a string of up 36 characters. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 696 Mediant 800B Gateway & E-SBC Parameter Description Suffix to Add Defines the number or string to add at the end of the manipulated item. For example, if you enter '01' and the user name is "john", the suffix-to-add new user name is "john01".

  • Page 697: Configuring Dial Plans

    The Dial Plan itself is a set of dial plan rules having the following attributes:  Prefix: The prefix is matched against the source and/or destination number of the incoming SIP dialog-initiating request. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 698 Mediant 800B Gateway & E-SBC  Tag: The tag corresponds to the matched prefix of the source and/or destination number and is the categorization result. You can use various syntax notations to configure the prefix numbers in dial plan rules.
  • Page 699 Plan). Click New; the following dialog box appears: Figure 35-2: Dial Plan Table - Add Dialog Box Configure a Dial Plan name according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 700 Mediant 800B Gateway & E-SBC Table 35-2: Dial Plan Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [DialPlans_Index] Note: Each row must be configured with a unique index. Name Defines an arbitrary name to easily identify the row.

  • Page 701: Importing And Exporting Dial Plans

    Web client. The CLI lets you import and export Dial Plans from and to a remote server. The following procedures describe how to export configured Dial Plans.  To export all configured dial plan rules:  Web interface (to a local folder): Open the Dial Plan table. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 702 Mediant 800B Gateway & E-SBC From the 'Action' drop-down menu, choose Export; the following dialog box appears: Figure 35-4: Exporting Dial Plan Select the Save File option, and then click OK; the file is saved to the default folder on your PC for downloading files.
  • Page 703 Open the Dial Plan table. Select the required Dial Plan, and then click the Dial Plan Rule link; the Dial Plan Rule table opens, displaying all the rules of the selected Dial Plan. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 704: Creating Dial Plan Files

    Mediant 800B Gateway & E-SBC From the 'Action' drop-down menu, choose Import; the following dialog box appears: Figure 35-6: Importing Dial Plan Rules for Specific Dial Plan Use the Browse button to select the Dial Plan file on your PC, and then click OK.

  • Page 705: Using Dial Plan Tags For Ip-To-Ip Routing

    Dial Plan in Step 1. The tags are assigned under the Match group, using the following parameters: • 'Source Tags' parameter (IP2IPRouting_SrcTags): tag denoting the calling user • 'Destination Tags' parameter (IP2IPRouting_DestTags): tag denoting the called user Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 706: Dial Plan Backward Compatibility

    Mediant 800B Gateway & E-SBC 35.3.1 Dial Plan Backward Compatibility Note: This section is for backward compatibility only. It is recommended to migrate your Dial Plan configuration to the latest Dial Plan feature (see 'Using Dial Plan Tags for IP-to-IP Routing' on page 705).

  • Page 707: Using Dial Plan Tags For Outbound Manipulation

    Dial Plan in Step 1. The tags are assigned using the following parameters: • 'Source Tags' parameter (IPOutboundManipulation_SrcTags): tag denoting the calling users • 'Destination Tags' parameter (IPOutboundManipulation_DestTags): tag denoting the called users Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 708: Using Dial Plan Tags For Call Setup Rules

    Mediant 800B Gateway & E-SBC 35.5 Using Dial Plan Tags for Call Setup Rules You can use Dial Plan tags in Call Setup rules, configured in the Call Setup Rules table (see Configuring Call Setup Rules on page 387). The Call Setup rule can be assigned to an IP Group and is processed by the device for the classified source IP Group immediately before the routing process (i.e., Classification >...

  • Page 709: Configuring Malicious Signatures

    (i.e., IP Group). To configure Message Policies, see 'Configuring SIP Message Policy Rules'. The following procedure describes how to configure Malicious Signatures through the Web interface. You can also configure it through ini file (MaliciousSignatureDB) or CLI (configure voip > sbc malicious-signature-database). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 710 Mediant 800B Gateway & E-SBC  To configure a Malicious Signature: Open the Malicious Signature table (Setup menu > Signaling & Media tab > SBC folder > Malicious Signature). Click New; the following dialog box appears: Figure 36-1: Malicious Signature Table - Add Dialog Box Configure a Malicious Signature according to the parameters described in the table below.

  • Page 711: Advanced Sbc Features

    Experience (QoE).  To configure SBC emergency call preemption: In the Message Conditions table (see 'Configuring Message Condition Rules' on page 665), configure a Message Condition rule to identify incoming emergency calls. See Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 712: Emergency Call Routing Using Ldap To Obtain Elin

    Mediant 800B Gateway & E-SBC above for examples. Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings), and then scroll down to the Call Priority and Preemption group: Figure 37-2: Configuring Emergency SBC Call Preemption From the 'Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable call preemption.

  • Page 713: Enabling Interworking Of Sip And Sip-I Endpoints

    SIP-I is SIP encapsulated with ISUP and the interworking is between SIP signaling and ISUP signaling. This allows you to deploy the device in a SIP environment where part of the call path involves the PSTN. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 714 Mediant 800B Gateway & E-SBC The SIP-I sends calls, originating from the SS7 network, to the SIP network by adding ISUP messaging in the SIP INVITE message body. The device can receive such a message from the SIP-I and remove the ISUP information before forwarding the call to the SIP endpoint.
  • Page 715 'Configuring SIP Message Manipulation' on page 378). For a complete description of the ISUP manipulation syntax, refer to the SIP Message Manipulation Reference Guide. In addition, you can use AudioCodes proprietary SIP header X-AC-Action in Message Manipulation rules to support the following call actions (e.g., SIP-I SUS and RES messages) for the ISUP SPIROU variant: ...

  • Page 716: Webrtc

    The WebRTC feature is a license-dependent feature and is available only if it is included in the License Key that is installed on the device. For ordering the feature, please contact your AudioCodes sales representative. • The maximum concurrent WebRTC sessions (signaling-over-secure WebSocket and media-over-DTLS) supported by the device is 500.
  • Page 717 WebRTC components and the device's interworking of these components between the WebRTC client and the SIP user agent: The call flow process for interworking WebRTC with SIP endpoints by the device is illustrated below and subsequently described: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 718: Sip Over Websocket

    Mediant 800B Gateway & E-SBC The WebRTC client uses a Web browser to visit the Web site page. The Web page receives Web page elements and JavaScript code for WebRTC from the Web hosting server. The JavaScript code runs locally on the Web browser.
  • Page 719 The SIP messages over WebSocket are indicated by the "ws" value, as shown in the example below of a SIP REGISTER request received from a client: REGISTER sip:10.132.10.144 SIP/2.0 Via: SIP/2.0/WS v6iqlt8lne5c.invalid;branch=z9hG4bK7785666 Max-Forwards: 69 To: <sip:101@10.132.10.144> From: "joe" <sip:101@10.132.10.144>;tag=ub50pqjgpr Call-ID: fhddgc3kc3hhu32h01fghl CSeq: 81 REGISTER Contact: <sip:0bfr9fd5@v6iqlt8lne5c.invalid;transport=ws>;reg- id=1;+sip.instance="<urn:uuid:4405bbe2-cf06-4c27-9c59- Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 720: Configuring Webrtc

    For the WebRTC deployment environment, you need to install a signed certificate by a Certificate Authority (CA) on you Web server machine (hosting the WebRTC JavaScript) and on your AudioCodes SBC device (i.e., WebSocket server). Note: • Google announced a security policy change that impacts new versions of the Chrome Web browser.
  • Page 721 Configure an IP Profile for the WebRTC clients: Open the IP Profiles table (see 'Configuring IP Profiles' on page 405). Do the following: ♦ From the 'ICE Mode' drop-down list (IPProfile_SBCIceMode), select Lite to Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 722 Mediant 800B Gateway & E-SBC enable ICE. ♦ From the 'RTCP Mux' drop-down list (IPProfile_SBCRTCPMux), select Supported to enable RTCP multiplexing. ♦ From the 'RTCP Feedback' drop-down list (IPProfile_SBCRTCPFeedback), select Feedback On to enable RTCP feedback. Figure 37-8: Configuring WebRTC-related Parameters for IP Profile Click Apply.

  • Page 723: Call Forking

    INVITE-initiating UA and disregards subsequently received 18x forking responses (with or without SDP).  Sequential: The device forwards all 18x responses to the INVITE-initiating UA, sequentially (one after another). If 18x arrives with an offer only, only the first offer is Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 724: Configuring Call Forking-Based Ip-To-Ip Routing Rules

    Mediant 800B Gateway & E-SBC forwarded to the INVITE-initiating UA.  To configure the call forking mode: Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings). From the 'Forking Handling Mode' drop-down list (SBCForkingHandlingMode), select the required mode: Click Apply.

  • Page 725: Configuring Broadsoft's Shared Phone Line Call Appearance For Survivability

    When the BroadSoft application server switch (AS) fails or does not respond, or when the network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 726 Mediant 800B Gateway & E-SBC The feature is supported by configuring a primary extension and associating it with secondary extensions (i.e., shared lines) so that incoming calls to the primary extension also ring at the secondary extensions. The call is established with the first extension to answer the call and consequently, the ringing at the other extensions stop.

  • Page 727: Configuring Call Survivability For Call Centers

    The SBC can handle a sequence of up to five users, after which the session is timed out and the call is dropped. Figure 37-12: Normal Operation in Call Center Application Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 728 Mediant 800B Gateway & E-SBC Figure 37-13: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Groups table (see 'Configuring IP Groups' on page 344), add IP Groups for the following entities: •...

  • Page 729: Enabling Survivability Display On Aastra Ip Phones

    <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument>  To enable survivability display on Aastra phones: Load an ini file to the device that includes the following parameter setting: SBCEnableSurvivabilityNotice = 1 Version 7.2 Mediant 800B Gateway & E-SBC...

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

    25%. ISPs can therefore offer service level agreements (SLAs) to their customers based on the VoIPerfect feature. For more information, contact your AudioCodes sales representative. In addition, by ensuring high call quality even in adverse network conditions, VoIPerfect may reduce costs for ISPs such...
  • Page 731 The advantage of the Opus coder is that its' bit rate can change dynamically according to bandwidth availability. This mode is useful for unstable networks, allowing Opus to dynamically adapt to adverse network conditions. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 732 Mediant 800B Gateway & E-SBC Configuration of the Enterprise SBC: • Coders Group with Opus • Allowed Audio Coders Group with Opus • IP Profile: ♦ Extension Coders Group: Coders Group with Opus ♦ Allowed Audio Coders: Allowed Audio Coders Group with Opus ♦...

  • Page 733: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 735: Crp Overview

      Basic call routing between Test call agent registering users and device, or any other route to responding server  Short number dialog (short numbers are learned dynamically in the registration process) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 736 Mediant 800B Gateway & E-SBC Survivability Quality of Experience/Service Security  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...

  • Page 737: Crp Configuration

    Open the Applications Enabling page (Setup menu > Signaling & Media tab > Core Entities folder > Applications Enabling). From the 'CRP Application' drop-down list, select Enable. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 738: Configuring Call Survivability Mode

    Mediant 800B Gateway & E-SBC 39.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters.

  • Page 739: Pre-Configured Ip Groups

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

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

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

  • Page 741: 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 742). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 742: Configuring Pstn Fallback

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

  • Page 743: High Availability System

    Part VIII High Availability System...

  • Page 745: Ha Overview

    Device Switchover upon Failure on page 746. • 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 746: Device Switchover Upon Failure

    Mediant 800B Gateway & E-SBC Note: If the active unit runs an earlier version (e.g., 7.0) than the redundant unit (e.g., 7.2), the redundant unit is downgraded to the same version as the active unit (e.g., 7.0). Thus, under normal operation, one of the devices is in active state while the other is in redundant state, where both devices share the same configuration and software.

  • Page 747: Viewing Ha Status On Monitor Web Page

    "Operational": The device is in HA mode  "Stand Alone": HA is configured, but the Redundant device is missing and HA is currently unavailable You can change the name of each device, as described in the following procedure: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 748 Mediant 800B Gateway & E-SBC  To define a name for the device: Open the HA Settings page (Setup menu > IP Network tab > Core Entities folder > HA Settings). In the 'HA Device Name' field, enter a name for the active device.

  • Page 749: Ha Configuration

     (Recommended Physical Connectivity) If the Maintenance ports of both devices are connected directly to each other without intermediation of switches, configure the mode to 2RX/1TX: Figure 41-1: Rx/Tx Mode for Direct Connection Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 750: Configuring The Ha Devices

    Mediant 800B Gateway & 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 41-2: Redundancy Mode for Two Isolated Switches ...

  • Page 751: Step 1: Configure The First Device

    Make sure that the Maintenance interface uses an Ethernet Device and Ethernet Group that is not used by any other IP network interface. The Ethernet Group is associated with the Ethernet Device, which is assigned to the interface. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 752 Mediant 800B Gateway & E-SBC The IP Interfaces table below shows an example where the Maintenance interface is configured with Ethernet Device "vlan 2" (which is associated with Ethernet Group "GROUP_2"), while the other interface is assigned "vlan 1" (associated with Ethernet Group "GROUP_1"):...

  • Page 753: Step 2: Configure The Second Device

    For more information on the HA Preempt feature, see 'Device Switchover upon Failure' on page 746. Burn the configuration to flash without a reset. Power down the device. Continue to 'Step 3: Initialize HA on the Devices' on page 754. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 41.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 755: Configuring Firewall Allowed Rules

    The figure below displays an example of the required firewall rules, where 10.31.4.61 is the Maintenance interface of the redundant device and 10.31.4.62 is the Maintenance interface of the active device. "HA_IF" is the name of the Maintenance interface. Figure 41-7: Allowed Firewall Rules for HA Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 756: Monitoring Ip Entity And Ha Switchover Upon Ping Failure

    Mediant 800B Gateway & E-SBC 41.4 Monitoring IP Entity and HA Switchover upon Ping Failure The device can monitor a specified network entity, using pings. If the device does not receive a ping response from the entity, a switchover to the redundant device occurs. The switchover happens only if a ping was initially successful and then a subsequent ping failed.
  • Page 757 "Disabled by Eth groups error": when the number of Ethernet Groups in the redundant device becomes less than in the active device, the ping mechanism is disabled.  “Failed to be activated": Internal error (failed activating the ping mechanism). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 758 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 759: Ha Maintenance

    'Configuring the HA Devices' on page 750. 42.3 Forcing a Switchover If required, you can force a switchover between active and redundant devices. For more information, see 'High Availability Maintenance' on page 767. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 760: Software Upgrade

    Mediant 800B Gateway & E-SBC 42.4 Software Upgrade You can perform the following types of software upgrades on the HA system:  Software Upgrade with Device Reset: Both active and redundant devices burn and reboot with the new software version. This method is quick and simple, but it disrupts traffic (i.e., traffic affecting).

  • Page 761: Maintenance

    Part IX Maintenance...

  • Page 763: Basic Maintenance

    Timeout' field (see next step). During this interval, no new traffic is accepted. If no traffic exists and the time has not yet expired, the device resets immediately. • No: Reset begins immediately, regardless of traffic. Any existing traffic is immediately terminated. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 764: Remotely Resetting Device Using Sip Notify

    Remotely Resetting Device using SIP NOTIFY The device can be remotely reset upon the receipt of a SIP NOTIFY that contains an Event header that is set to 'check-sync;reboot=true' (proprietary to AudioCodes), as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...

  • Page 765: Locking And Unlocking The Device

    'Gateway Operational State' read-only field displays "LOCKED" and the device does not process any calls.  To unlock the device:  Click the UNLOCK button; the device unlocks immediately and accepts new incoming calls. The 'Gateway Operational State' read-only field displays "UNLOCKED". Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 766: Saving Configuration

    Mediant 800B Gateway & E-SBC 43.4 Saving Configuration When you configure parameters and tables in the Web interface and then click the Apply button on the pages in which the configurations are done, changes are saved to the device's volatile memory (RAM). These changes revert to their previous settings if the device subsequently resets (hardware or software) or powers down.

  • Page 767: High Availability Maintenance

    When resetting the Redundant device, the HA mode becomes temporarily unavailable.  To reset the Redundant device: Open the High Availability Maintenance page: • Toolbar: Click the Actions button, and then from the drop-down menu, choose Switchover. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 768 Mediant 800B Gateway & E-SBC • Navigation tree: Setup menu > Administration tab > Maintenance folder > High Availability Maintenance. Figure 44-2: Resetting Redundant Device click Reset; a confirmation box appears requesting you to confirm. Click OK. User's Manual Document #: LTRT-10298...

  • Page 769: Channel Maintenance

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

  • Page 770: Locking And Unlocking Trunk Groups

    Mediant 800B Gateway & E-SBC 45.4 Locking and Unlocking Trunk Groups You can lock a Trunk Group to take its trunks (and their channels) out of service. When you initiate a lock, the device rejects all new incoming calls for the Trunk Group and immediately terminates active calls (busy channels), eventually taking the entire Trunk Group out of service.

  • Page 771: Disconnecting Active Calls

    You can forcibly disconnect all active calls, or disconnect specific calls based on Session  To disconnect calls through CLI:  Disconnect all active calls: # clear voip calls  Disconnect active calls belonging to a specified Session ID: # clear voip calls <Session ID> Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 772: Configuring Name For Telephony Ports

    Mediant 800B Gateway & E-SBC 45.6 Configuring Name for Telephony Ports 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 773: Software Upgrade

    CLI - see Loading Auxiliary Files through CLI on page 775  TFTP - see Loading Auxiliary Files through ini File using TFTP  EMS (Software Manager) – refer to the EMS User’s Manual Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 774: Loading Auxiliary Files Through Web Interface

    Mediant 800B Gateway & E-SBC Note: • You can automatically load Auxiliary files from a remote server using the device's Automatic Update mechanism (see Automatic Update Mechanism). • Saving Auxiliary files to flash memory may disrupt traffic on the device. To avoid this, disable all traffic on the device by performing a graceful lock as described in 'Locking and Unlocking the Device' on page 765.

  • Page 775: Loading Auxiliary Files Through Cli

    46.1.3 Call Progress Tones File The Call Progress Tones (CPT) and Distinctive Ringing (analog interfaces only) Auxiliary file contains definitions of the CPT (levels and frequencies) that are detected and generated by the device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 776 (in any standard text editor) to suit your specific requirements and then convert the modified ini file into binary dat file format, using AudioCodes DConvert utility. For more information, refer to the DConvert Utility User's Guide.
  • Page 777 1 to 128 Hz). • Signal Level [-dBm]: Level of the tone for AM tones. • AM Factor [steps of 0.02]: Amplitude modulation factor (valid range from 1 to 50). Recommended values from 10 to 25. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 778: Distinctive Ringing

    Mediant 800B Gateway & E-SBC Note: • When the same frequency is used for a continuous tone and a cadence tone, the 'Signal On Time' parameter of the continuous tone must have a value that is greater than the 'Signal On Time' parameter of the cadence tone. Otherwise, the continuous tone is detected instead of the cadence tone.
  • Page 779 #Regular North American Ringing Pattern [Ringing Pattern #0] Ring Type=0 Freq [Hz]=20 First Ring On Time [10msec]=200 First Ring Off Time [10msec]=400 #GR-506-CORE Ringing Pattern 1 [Ringing Pattern #1] Ring Type=1 Freq [Hz]=20 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 780: Prerecorded Tones File

    For SBC calls, the PRT file supports only the ringback tone and hold tone. The prerecorded tones can be created using standard third-party, recording utilities such as Adobe Audition, and then combined into a single file (PRT file) using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide.

  • Page 781: Cas Files

    Creating a Dial Plan file is similar for all Dial Plan features. The main difference is the syntax used in the Dial Plan file and the method for selecting the Dial Plan index. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 782: Dialing Plans For Digit Collection

    Plans as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Load the converted file to the device, as described in 'Loading Auxiliary Files' on page 773.
  • Page 783 • 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 784: Dial Plan Prefix Tags For Ip-To-Tel Routing

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplans.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Install the converted file on the device, as described in 'Loading Auxiliary Files' on page 773.
  • Page 785 Specify the Dial Plan (configured with the prefix tags) by index number (e.g., 1) that you want to use: Open the Routing Settings page (Setup menu > Signaling & Media tab > Gateway folder > Routing > Routing Settings). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 786 Mediant 800B Gateway & E-SBC In the 'IP-to-Tel Tagging Destination Dial Plan Index' field, enter the Dial Plan index that you want to use for prefix tags for called number prefixes. In the 'IP-to-Tel Tagging Source Dial Plan Index' field, enter the Dial Plan index that you want to use for prefix tags for calling number prefixes.

  • Page 787: Obtaining Ip Destination From Dial Plan File

    The "DialPlan" string is case-sensitive. 46.1.6.5 Modifying ISDN-to-IP Calling Party Number You can use the Dial Plan file to change the Calling Party Number value (source number) of the incoming ISDN call when sending to IP. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 788 Mediant 800B Gateway & E-SBC Note: The feature is applicable only to digital interfaces. Use the following syntax in the Dial Plan file: <ISDN Calling Party Number>,0,<new calling number>  <ISDN Calling Party Number>: Calling party number (or its prefix) received in the ISDN call SETUP message.

  • Page 789: Viewing Information Of Installed Dial Plan File

    Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP Definitions folder > Proxy & Registration). From the 'Enable User-Information Usage' drop-down list (EnableUserInfoUsage), select Enable: Figure 46-5: Enabling User Info Table Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 790: Gateway User Information For Pbx Extensions And "Global" Numbers

    Mediant 800B Gateway & E-SBC Note: The 'Enable User-Information Usage' parameter appears in the Web interface only if the device's License Key is defined with far-end users. Reset the device with a save-to-flash for your settings to take effect; the User Info table now appears in the Web interface.
  • Page 791 Open the GW User Info table (Setup menu > Signaling & Media tab > Gateway folder > User Information). Click New; the following dialog box appears: Figure 46-6: GW User Info Table - Add Dialog Box Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 792 Mediant 800B Gateway & E-SBC Configure a user according to the table below. Click Apply. To register a user, select the user's table entry, and then from the Action drop-down list , choose Register. To un-register a user, select the user, and then from the Action drop-down list , choose Un-Register.
  • Page 793 Password is the password (string of up to 20 characters) for registering the user when authentication is necessary Each line in the file represents a mapping rule of a single PBX extension user. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 794: User Information File For Sbc User Database

    Mediant 800B Gateway & E-SBC Note: • Make sure that there are no spaces between the values. • Make sure that the last line in the User Info file ends with a carriage return (i.e., by pressing the <Enter> key).
  • Page 795 Assigns an IP Group to the user and is used as the Request- URI source host part for the AOR in the database. [SBCUserInfoTable_IPGroupName] To configure IP Groups, see 'Configuring IP Groups' on page 344. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 796 Mediant 800B Gateway & E-SBC Parameter Description Status (Read-only field) Displays the status of the user - "Registered" or "Not Registered". [SBCUserInfoTable_Status] 46.1.7.3.2 Configuring SBC User Info Table through CLI The SBC User Info table can be configured in the CLI using the following commands: ...

  • Page 797: Viewing The Installed User Info File Name

    You can view the name of the User Info file currently installed on the device, through the device's CLI (in Enable mode): # debug auxilary-files user-info info For example: # debug auxilary-files user-info info User Info File Name MyUsers.txt Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 798: Amd Sensitivity File

    The XML-to-binary format conversion can be done using AudioCodes DConvert utility. For more information on using this utility, refer to DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.

  • Page 799: Obtaining License Key For Feature Upgrade

    Before you can install a new License Key, you need to obtain a License Key file for your device with the required features from your AudioCodes representative. The 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 800: Installing The License Key

    Mediant 800B Gateway & E-SBC 46.2.3 Installing the License Key After you have received your License Key file from your AudioCodes representative, you can install it on the device as described in this section. Note: When you install a new License Key, it is loaded to the device's non-volatile flash memory and overwrites the previously installed License Key.

  • Page 801: Installing License Key Through Cli

    To install the License Key through CLI, use the following commands:  To install the License Key: (config-system)# feature-key <"string enclosed in double quotation marks">  To view the License Key: show system feature-key Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 802: Upgrading Sbc Capacity Licenses By License Pool Manager Server

    Manager Server The device can receive SBC capacity licenses from a centralized pool of SBC resources managed by the License Pool Manager Server running on AudioCodes EMS. The License Pool Manager Server can dynamically allocate and de-allocate SBC capacity licenses from the pool to devices in the network to meet capacity demands of each device whenever required.
  • Page 803 Manager Server that exceeds the maximum SBC session capacity that can be supported by the device. The device sets the capacity to its maximum (and values beyond the device’s capability are not applied) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 804: Software Upgrade Wizard

    Mediant 800B Gateway & E-SBC Note: • No configuration is required on the device; the License Pool Manager Server controls the allocation/de-allocation of its resource pool to the managed devices. For more information on the License Pool Manager Server, refer to the EMS User's Manual.
  • Page 805 User's Manual 46. Software Upgrade Note: • You can obtain the latest software files from AudioCodes Web site at http://www.audiocodes.com/downloads. • When you start the wizard, the rest of the Web interface is unavailable. After the files are successfully installed with a device reset, access to the full Web interface is restored.
  • Page 806 Mediant 800B Gateway & E-SBC • Navigation tree: Setup menu > Administration tab > Maintenance folder > Software Upgrade. Figure 46-13: Starting Software Upgrade Wizard Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Note: •...
  • Page 807 Click Browse, and then navigate to and select the new ini file. Click Load File; the device loads the ini file. • Restore configuration to factory defaults: Clear the 'Use existing configuration' check box. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 808 Mediant 800B Gateway & E-SBC • Retain the existing configuration (default): Select the 'Use existing configuration' check box. Figure 46-15: Load an INI File in the Software Upgrade Wizard Note: If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file) and thereby, overwrite values...
  • Page 809 .cmp software version and other files that you may also have installed: Figure 46-17: Software Upgrade Process Completed (Example) Click End Process to close the wizard; the Web Login page appears, allowing you to log in to your upgraded device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 810 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 811: Backing Up And Loading Configuration File

    Figure 47-1: Saving Configuration File using Configuration File Page To load an ini file to the device: Click the Browse button, navigate to and select the file, and then click Open; the file name is displayed next to the Browse button. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 812 Mediant 800B Gateway & E-SBC 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 username and password.

  • Page 813: Automatic Provisioning

    Open the Network Settings page (Setup menu > IP Network tab > Advanced folder > Network Settings). From the 'Enable DHCP" drop-down list, select Enable. Figure 48-1: Enabling DHCP Client Functionality Click Apply. To activate the DHCP process, reset the device. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & 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 815: Provisioning From Tftp Server Using Dhcp Option 66

    Provisioning the device from a third-party TFTP server is suitable when the network in which the device is deployed includes a provisioning TFTP server for all network equipment, without the capability of distinguishing between AudioCodes and non- AudioCodes devices. Upon startup, the device checks for DHCP Option 66 in the DHCP response received from the DHCP server.

  • Page 816: Http-Based Provisioning

    Mediant 800B Gateway & E-SBC Enable the device to include DHCP Option 66 in DHCP Option 55 (Parameter Request List) when requesting TFTP provisioning parameters from a DHCP server, using the following ini file parameter: DHCPRequestTFTPParams = 1 Reset the device with a save-to-flash for your settings to take effect.

  • Page 817: Ftp-Based Provisioning

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

  • Page 818: Files Provisioned By Automatic Update

    Mediant 800B Gateway & E-SBC 48.2.1 Files Provisioned by Automatic Update You can use the Automatic Update feature to update the device with any of the following files:  Software file (cmp)  Auxiliary files (e.g., Call Progress Tones, SSL Certificates, SSL Private Key) ...

  • Page 819: Mac Address Placeholder In Configuration File Name

    Use the keywords listed in the table below to specify each file type. For example, to specify ini, Feature Key, and CPT files: • ini File: AupdFilesList = 'ini', 'fk', 'cpt' • CLI: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 820 Mediant 800B Gateway & E-SBC # configure system (config-system)# automatic update (automatic-update)# template-files-list ini,fk,cpt Define the URL address of the provisioning server on which the files (specified in Step 1) are located for download, using the TemplateUrl parameter. When you configure the URL, you must include the file type placeholder, "<FILE>", which represents the...

  • Page 821: 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 822: Querying Provisioning Server For Updated Files

    Mediant 800B Gateway & E-SBC  Basic Access Authentication: The device provides its username and password to the HTTP server. The username and password is configured in the URL that you define for downloading the file: • ini file: AutoCmpFileUrl = 'https://<username>:<password>@<IP address or domain name>/<file name>'...
  • Page 823 Update process. Once they are downloaded, the device discards their configured URLs. To update these files again, you need to configure their URL addresses and filenames again. Below is an example of how to configure URLs for some of these files: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 824: File Download Sequence

    Mediant 800B Gateway & E-SBC Auxiliary Files: ♦ ini: CptFileURL = 'https://www.company.com/call_progress.dat' FeatureKeyURL = 'https://www.company.com/License_Key.txt' ♦ CLI: (config-system)# automatic-update (automatic-update)# call-progress-tones http://www.company.com/call_progress.dat (automatic-update)# tls-root-cert https://company.com/root.pem Software (.cmp) File: ♦ ini: CmpFileUrl = 'https://www.company.com/device/v.7.20A.000.038.cmp' ♦ CLI: (config-system)# automatic-update (automatic-update)# firmware https://www.company.com/device/v.7.20A.000.038.cmp Note: •...

  • Page 825: Cyclic Redundancy Check On Downloaded Configuration Files

    Get request during the Automatic Update process, the provisioning server sends the new file to the device. This occurs as the timestamp between the previously downloaded file and this new file is different (determined by the HTTP If-Modified-Since header in the Get Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 826: Automatic Update Configuration Examples

    Mediant 800B Gateway & E-SBC request). Therefore, the CRC feature can be used to prevent the device from installing such files. For enabling CRC, use the ini file parameter AUPDCheckIfIniChanged or CLI command, configure system > automatic-update > crc-check regular. By default, CRC is disabled. For more information on the parameter, see 'Automatic Update Parameters' on page 984.

  • Page 827: Automatic Update From Remote Servers

    Set up an FTPS server and copy the Feature Key file to the server. Configure the device with the URL path of the Feature Key file: ♦ ini File: FeatureKeyURL = 'ftps://root:wheel@ftpserver.corp.com/feature_key.txt' ♦ CLI: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 828: Automatic Update For Mass Deployment

    Mediant 800B Gateway & E-SBC # configure system (config-system)# automatic update (automatic-update)# feature-key 'ftps://root:wheel@ftpserver.corp.com/feature_key.txt' Software (.cmp) and ini files: Set up an HTTP Web server and copy the .cmp and configuration files to the server. Configure the device with the URL paths of the .cmp and ini files: ♦...
  • Page 829 Configure the device with the IP address of the DNS server for resolving the domain name (e.g., http://www.company.com) that is used in the URL for the provisioning server. This is done in the IP Interfaces table: ♦ ini File: [ InterfaceTable ] FORMAT InterfaceTable_Index = Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 830 Mediant 800B Gateway & E-SBC InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] ♦ CLI: # configure network (config-network)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100...

  • Page 831: 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 832 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 833: Restoring Factory Defaults

    IP Interfaces table (see 'Configuring IP Network Interfaces' on page 135), as described in the procedure below. This may be important, for example, to maintain connectivity with the device (through the OAMP interface) after factory defaults have been applied. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 834: Restoring Defaults Using Hardware Reset Button

    Mediant 800B Gateway & E-SBC  To restore factory defaults through Web interface: Open the Configuration File page: • Toolbar: From the Actions drop-down menu, choose Configuration File. • Navigation tree: Setup menu > Administration tab > Maintenance folder >...

  • Page 835: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 837: System Status

    The Monitor page displays the following groups of information:  Device Information pane: • 'Address': IP address of the device's OAMP interface • 'Firmware': Software version currently running on the device • 'Type': Name of the device Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 838 Mediant 800B Gateway & E-SBC • 'HA Status': High-Availability (HA) status of the device, if configured for HA. For more information, see Viewing HA Status on Monitor Web Page on page 747.  SBC Call Statistics: • Active Calls: Total number of SBC calls. The corresponding SNMP performance monitoring MIB is PM_gwInINVITEDialogs.
  • Page 839 AIS Alarm: Alarm Indication Handset Offhook: Channel is off- Signal (AIS), also known as hook, but there is no active RTP (blue) the Blue Alarm session D-Channel Alarm: D-channel alarm (orange) NFAS Alarm (dark orange) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 840: Viewing Port Information

    Mediant 800B Gateway & E-SBC Item # Description If you click a port, a shortcut menu appears with commands allowing you to do the following:  Reset channel (Analog ports only): Resets the analog port (see Resetting an Analog Channel on page 769) ...
  • Page 841 Call ID number of the call (SIP Call-ID header). Call Originator Caller:  "TEL": Call made from Tel side (i.e., the port)  "IP": Call made from IP side Source Tel Number Telephone number of the caller. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 842 Mediant 800B Gateway & E-SBC Field Description Destination Tel Number Telephone number of the called party. Redirect Calling Number Telephone number of the redirected number. Remote Signaling IP IP address used for SIP on the IP side. Remote RTP (IP:Port) IP address and port used for RTP on the IP side.
  • Page 843 "1": Reversed  "2": N\A Note: The parameter is applicable only to analog interfaces. Line polarity Line polarity:  "0": Positive  "1": Negative Note: The parameter is applicable only to analog interfaces. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 844 Mediant 800B Gateway & E-SBC Field Description Message Waiting Indication MWI status:  "0": Off  "1": On Note: The parameter is applicable only to analog interfaces. RTP/RTCP Channel Identifier Channel identifier number. RTP Direction Direction of RTP:  "Tx & Rx": both directions (transmit and...

  • Page 845: Reporting Dsp Utilization Through Snmp Mib

    SNMP MIB table, acPMDSPUsage. You can also configure low and high DSP utilization thresholds this MIB, that crossed, SNMP trap event, acPerformanceMonitoringThresholdCrossing is sent by the device. For more information on this MIB, refer to the SNMP Reference Guide. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 846 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 847: Viewing Carrier-Grade Alarms

     Major (orange)  Minor (yellow) Source Component of the device from which the alarm was raised. Description Brief description of the alarm. Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised. Date Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 848: Viewing History Alarms

    Mediant 800B Gateway & E-SBC 53.2 Viewing History Alarms You can view all SNMP alarms, in the Web interface's Alarms History table, that have been raised (active alarms) as well as cleared (resolved). One of the benefits of this is that you can view alarms that may have been raised and then cleared on a continuous basis.
  • Page 849 Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised.  To delete all the alarms in the table: Click the Delete History Table button; a confirmation message box appears. Click OK to confirm. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 850 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 851: Viewing Management User Activity Logs

    Username of the user account that performed the activity. Interface Protocol used for connecting to the management interface (e.g., Telnet, SSH, Web, or HTTP). Client IP address of the client PC from where the user accessed the management interface. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 852 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 853: Viewing Performance Monitoring

    From the 'Trunk' drop-down list, select the trunk for which you want to view active channels. For more graph functionality, see the following table: Table 55-1: Additional Graph Functionality for Trunk Utilization Button Description Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 854: Viewing Call Success And Failure Ratio

    Mediant 800B Gateway & E-SBC Button Description Add button Displays additional trunks in the graph. Up to five trunks can be displayed simultaneously. To view another trunk, click the button and then from the new 'Trunk' drop-down list, select the required trunk.
  • Page 855 If there is no data for the charts, the chart appears gray and "No Data" is displayed to the right of the chart.  To refresh the charts:  Click Refresh.  To reset the counters:  Click Reset Counters. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 856: Viewing Average Call Duration

    Mediant 800B Gateway & E-SBC 55.3 Viewing Average Call Duration You can view the number of currently active calls and the average call duration (ACD) in the Web interface's Average Call Duration page. You can filter display by a specific SRD or IP Group.

  • Page 857: Configuring Performance Profiles

    Yellow: Indicates fair call quality  Red: Indicates poor call quality When the threshold of a voice metric is crossed, the device changes the alarm severity and corresponding color-coded quality state of the call: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 858 Mediant 800B Gateway & E-SBC  Minor Threshold (Yellow): Lower threshold that indicates changes from Green or Red to Yellow.  Major Threshold (Red): Higher threshold that indicates changes from Green or Yellow to Red. The device also uses hysteresis to determine whether the threshold has indeed being crossed.
  • Page 859 Defines a configuration entity type to which you want to apply the rule. entity  [0] Global = (Default) The device calculates call metrics [PerformanceProfile_Entity] for all calls.  [1] SRD = Assigns an SRD. To specify the SRD, use the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 860 Mediant 800B Gateway & E-SBC Parameter Description 'SRD' parameter (see below).  [2] IP Group = Assigns an IP Group. To specify the IP Group, use the 'IP Group' parameter (see below). IP Group Assigns an IP Group to the rule.

  • Page 861: Configuring Packetsmart Agent For Network Monitoring

    VoIP networks. By providing real-time monitoring of live traffic, PacketSmart can identify any network issues as they arise that may impact VoIP quality, enabling service providers to address issues prior to customer complaints. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 862 Mediant 800B Gateway & E-SBC Note: • The PacketSmart feature is a license-dependent feature and is available only if it is included in the License Key installed on the device. For ordering the feature, please contact your AudioCodes sales representative.

  • Page 863: Viewing Voip Status

     GWAPP_REASON_NOT_RELEVANT (0)  GWAPP_NORMAL_CALL_CLEAR (16)  GWAPP_NORMAL_UNSPECIFIED (31) And the internal reasons:  RELEASE_BECAUSE_UNKNOWN_REASON  RELEASE_BECAUSE_REMOTE_CANCEL_CALL  RELEASE_BECAUSE_MANUAL_DISC  RELEASE_BECAUSE_SILENCE_DISC Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 864 Mediant 800B Gateway & E-SBC Counter Description  RELEASE_BECAUSE_DISCONNECT_CODE Note: When the duration of the call is zero, the release reason GWAPP_NORMAL_CALL_CLEAR increments the 'Number of Failed Calls due to No Answer' counter. The rest of the release reasons increment the 'Number of Failed Calls due to Other Failures' counter.

  • Page 865: Viewing Sbc Registered Users

    You can view information on the current call routing method used by the device. The information includes the IP address (or FQDN) of the Proxy server with which the device routes the call. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 866: Viewing Registration Status

    Mediant 800B Gateway & E-SBC  To view call routing status:  Open the Call Routing Status table (Monitor menu > Monitor tab > VoIP Status folder > Call Routing Status). Figure 56-3: Viewing Call Routing Status Table 56-3: Call Routing Status Table Description...
  • Page 867 Status: "REGISTERED" or "NOT REGISTERED" Phone Number Status Displays the registration status of BRI endpoints:  Phone Number: Phone number of endpoint.  Gateway Port: module/port number of endpoint.  Status: "REGISTERED" or "NOT REGISTERED" Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 868: Viewing Ip Connectivity

    Mediant 800B Gateway & E-SBC 56.5 Viewing IP Connectivity You can view on-line, read-only network diagnostic connectivity information on destination IP addresses configured in the Tel-to-IP Routing table (see 'Configuring Tel-to-IP Routing Rules' on page 485). Note: The table is applicable only to the Gateway application.

  • Page 869: Viewing Gateway Cdr History

    Figure 56-5: Gateway CDR History Table  CLI: • All CDR history: # show voip calls history gw • CDR history for a specific SIP session ID: # show voip calls history gw <session ID> Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 870 Mediant 800B Gateway & E-SBC Table 56-6: Gateway CDR History Table Field Description Call End Time Displays the time at which the call ended. The time is displayed in the format, hh:mm:ss, where hh is the hour, mm the minutes and ss the seconds (e.g., 15:06:36).

  • Page 871: Viewing Sbc Cdr History

    "Incoming"  "Outgoing" Remote IP Displays the IP address of the call party. For an "Incoming" call, this is the source IP address; for an "Outgoing" call, this is the destination IP address. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 872 Mediant 800B Gateway & E-SBC Field Description Duration Displays the duration of the call, displayed in the format hh:mm:ss, where hh is hours, mm minutes and ss seconds. For example, 00:01:20 denotes 1 minute and 20 seconds. Termination Reason Displays the reason for the call being released (ended). For example, "NORMAL_CALL_CLEAR"...

  • Page 873: Viewing Pstn Status

    Table 57-1: Description of Color-Coded Icons for Trunk Status Trunk Icon Color Label Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 57-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 875 To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Monitor menu > Monitor tab > PSTN Status folder > NFAS Group & D-Channel Status). Figure 57-1: NFAS Group & D-Channel Status Page Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 876 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 877: Viewing Network Status

    Navigation tree: Monitor menu > Monitor tab > Network Status folder > Ethernet Port Information. • Monitor home page: Click an Ethernet port on the graphical display of the device (see 'Viewing Device Status on Monitor Page' on page 837). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 878: Viewing Static Routes Status

    Mediant 800B Gateway & E-SBC Table 58-1: Ethernet Port Information Table Description Parameter Description Port Name Displays the name of the port. Active Displays whether the port is active ("Yes") or not ("No"). Speed Displays the speed of the Ethernet port.

  • Page 879: Reporting Information To External Party

    The type of RTCP XR report event (VQReportEvent) supported by the device is VQSessionReport (SessionReport). The device can include local and remote metrics in the RTCP XR. Local metrics are generated by the device while remote metrics are provided by Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 880 Mediant 800B Gateway & E-SBC the remote endpoint. The following table lists the supported voice metrics (parameters) published in the RTCP XR. Table 59-1: RTCP XR Published VoIP Metrics Metric Parameter Description CallID Call ID - call ID from the SIP dialog...
  • Page 881 MOS-LQ - estimated mean opinion score for listening voice quality on a scale from 1 to 5, in which 5 represents excellent and 1 represents unacceptable MOSLQEstAlg MOS-LQ Est. Algorithm - name (string) of the algorithm used to estimate MOSLQ Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 882 Mediant 800B Gateway & E-SBC Metric Parameter Description MOSCQ MOS-CQ - estimated mean opinion score for conversation voice quality on a scale from 1 to 5, in which 5 represents excellent and 1 represents unacceptable MOSCQEstAlg MOS-CQ Est. Algorithm - name (string) of the algorithm used to...
  • Page 883 Under the RTCP-XR Collection Server group, configure the following: • (Gateway Application Only) 'Gateway RTCP XR Report Mode' (RTCPXRReportMode) - enables RTCP XR reports and defines the interval at which they are sent. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 884: Generating Call Detail Records

    Mediant 800B Gateway & E-SBC • (SBC Application Only) 'SBC RTCP XR Report Mode' (SBCRtcpXrReportMode) - enables the sending of RTCP XR reports of QoE metrics at the end of each call session (i.e., after a SIP BYE). Figure 59-2: Configuring RTCP XR Collection Server Using the PublicationIPGroupID ini file parameter, define the IP Group to where you want to send the RTCP XR.
  • Page 885 EPTyp Endpoint type: "SBC" String SIPMethod SIP message type String (up to 10 characters) SIPCallId Unique ID of call String (up to 50 characters) Unique Session ID String (up to 10 SessionId characters) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 886 Mediant 800B Gateway & E-SBC CDR Field Description CDR Report Type Format (SBCReportType) LegId Unique ID number of the call leg "CALL_START", String (decimal) within a specific call session. "CALL_CONNECT" and "CALL_END" A basic call consists of two legs (incoming leg and outgoing leg) and thus, two leg IDs are generated for the session, one for each leg.
  • Page 887 "RELEASE_BECAUSE_UN MATCHED_CAPABILITIES"  FORWARDED:  "RELEASE_BECAUSE_FOR WARD"  GENERAL_FAILED: Any other reason Calls with duration:  NORMAL_CALL_CLEAR:  "GWAPP_NORMAL_CALL_ CLEAR"  "ABNORMALLY_TERMINAT ED": Anything else N/A - Reasons not belonging to above categories. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 888 Mediant 800B Gateway & E-SBC CDR Field Description CDR Report Type Format (SBCReportType) SetupTime Call setup time String (up to 35 characters) ConnectTime Call connect time "CALL_CONNECT" String (up to 35 and "CALL_END" characters) ReleaseTime Call release time "CALL_END" String (up to 35...

  • Page 889: Cdr Fields For Sbc Media

    The default CDR fields for SBC media are listed in the following table. The media CDRs are published for each active media stream, thereby allowing multiple media CDRs, where each media CDR has a unique call ID corresponding to the signaling CDR. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 890 Mediant 800B Gateway & E-SBC There are three different CDR types (SBCReportType), which are sent to the CDR server at different stages of the SIP dialog session:  "MEDIA_START": CDR is sent upon an INVITE message.  "UPDATE": CDR is sent upon a re-INVITE message (e.g., the established call is placed on hold by one of the call parties).
  • Page 891 Remote packet loss information is unavailable) RTPdelay 0 to 10000 ms (-1 if Average RTP delay of the entire stream information is unavailable) 0 to 40000 samples (-1 if RTP jitter RTPjitter unavailable) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 892: Cdr Fields For Sbc Local Storage

    Mediant 800B Gateway & E-SBC CDR Field Range Description TxRTPssrc 0 to 0xFFFFFFFF Tx RTP SSRC RxRTPssrc 0 to 0xFFFFFFFF Local RTP SSRC LocalRFactor 0 to 120 (127 if information is Local conversation quality unavailable) Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided.
  • Page 893 SIP Interface Name SIPInterfaceId Proxy Set Name ProxySetId IP Profile Name IpProfileId Media Realm Name MediaRealmId Direct Media DirectMedia SIP Termination Reason SIPTrmReason SIP Termination Description SIPTermDesc Caller Display ID Caller Callee Display ID Callee Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 894: Cdr Fields For Gateway Application

    Mediant 800B Gateway & E-SBC 59.2.1.4 CDR Fields for Gateway Application The CDRs generated by the device for Gateway calls include media and signaling CDR fields. The default CDR fields are listed in the table below. The CDR can be one of the following report types (GWReportType field), depending at which stage of the SIP dialog it was sent: ...
  • Page 895 SourceIp Source IP address DestIp Destination IP address Source phone number type Source phone number plan SrcPhoneNum Source phone number SrcNumBeforeMap Source number before manipulation Destination phone number type Destination phone number plan Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 896 Mediant 800B Gateway & E-SBC CDR Field Description GWReportType (CDR Report Type) DstPhoneNum Destination phone number DstNumBeforeMap Destination number before manipulation Durat Call duration "CALL_END" Coder Selected coder "CALL_CONNE CT" and "CALL_END" Intrv Packet interval "CALL_END" RtpIp RTP IP address "CALL_END"...
  • Page 897 N/A - Reasons not belonging to above categories RedirectNumBefor Redirect number before manipulation "CALL_END" eMap SrdId SRD name SIP Interface name SIPInterfaceId ProxySetId Proxy Set name IpProfileId IP Profile name MediaRealmId Media Realm name Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 898 Mediant 800B Gateway & E-SBC CDR Field Description GWReportType (CDR Report Type) SigTransportType SIP signaling transport type (UDP, TCP, or TLS) TxRTPIPDiffServ Media IP DiffServ "CALL_END" TxSigIPDiffServ Signaling IP DiffServ LocalRFactor Local R-factor "CALL_END" Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided.
  • Page 899 "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"  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS"  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 900 Mediant 800B Gateway & E-SBC  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED"  "GWAPP_NON_SELECTED_USER_CLEARING"  "GWAPP_INVALID_NUMBER_FORMAT"...

  • Page 901: Cdr Fields For Gateway Local Storage

    Table 59-6: Default CDR Fields for Locally Stored Gateway CDRs CDR Field Title Report type GWReportType Port number SIP session identifier SessionId Leg ID LegId Physical trunk number Trunk Selected B-channel BChan Trunk Group ID Endpoint type EPTyp Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 902 Mediant 800B Gateway & E-SBC CDR Field Title Call originator Orig Source IP address SourceIp Destination IP address DestIp Source phone number type Source phone number plan Source phone number SrcPhoneNum Source number before manipulation SrcNumBeforeMap Destination phone number type...
  • Page 903  U - unknown Information relating to AMD that shows the success that the answering type (probability) was correctly detected SIP call termination reason (BYE, CANCEL, or SIPTrmReason SIP error codes, e.g., 404) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 904: Customizing Cdrs For Gateway Calls

    Mediant 800B Gateway & E-SBC CDR Field Title Q.850 protocol termination reason (0-127). PstnTermReason Remote IP address of the incoming RTP stream LatchedRtpIp that the device "latched" on to as a result of the RTP latching mechanism for NAT traversal.
  • Page 905 [6] RADIUS Gateway = Customizes CDR field names (RADIUS Attribute prefix names) for CDRs (media and signaling) sent in RADIUS accounting requests.  [9] Local Storage Gateway = Customizes CDR fields (media and signaling) that are stored locally on the device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 906 Mediant 800B Gateway & E-SBC Parameter Description Field Type Defines the CDR field (column) that you want to customize. col-type [300] CDR Type (default); [301] Call ID; [302] Session ID; [303] Report Type; [304] Media Type; [305] Accounting Status Type; [306] [GWCDRFormat_FieldType] H323 ID;...
  • Page 907  Local Input Packets: 47  Local Output Packets: 48 If you configure the value to 0 and the RADIUS Attribute is not any of the ones listed above, the configuration is invalid. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 908: Customizing Cdrs For Sbc Calls

    Mediant 800B Gateway & E-SBC 59.2.3 Customizing CDRs for SBC Calls The SBC CDR Format table lets you customize SBC-related CDRs that are generated by the device for the following:  CDRs (media and SIP signaling) sent in Syslog messages. For CDRs sent in Syslog messages, you can customize the name of the CDR field.
  • Page 909 CDR field depends on the settings of the 'CDR Type' col-type parameter: [SBCCDRFormat_FieldType]  For all types: [300] CDR Type (default); [301] Call ID; [302] Session ID; [303] Report Type; [304] Media Type; [305] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 910 Mediant 800B Gateway & E-SBC Parameter Description Accounting Status Type; [306] H323 ID; [307] RADIUS Call ID; [308] Blank; [309] Global Session ID; [310] Leg ID.  Syslog SBC, Local Storage SBC, and RADIUS SBC: [400] Endpoint Type; [401] Call Orig; [402] Source IP; [403] Destination IP;...
  • Page 911  Local Input Packets: 47  Local Output Packets: 48 If you configure the value to 0 and the RADIUS Attribute is not any of the ones listed above, the configuration is invalid. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 912: Configuring Cdr Reporting

    Mediant 800B Gateway & E-SBC 59.2.4 Configuring CDR Reporting To enable and configure CDR reporting, follow the procedure below. For detailed descriptions of the parameters, see 'Syslog, CDR and Debug Parameters' on page 1001.  To configure CDR reporting: Enable the Syslog feature for sending log messages generated by the device to a collecting log message server.
  • Page 913 Any file extension name can be used, but as the file content is in CSV format, it is recommended to use the .csv file extension. • protocol: protocol over which the file is sent (tftp, http, or https). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 914 Mediant 800B Gateway & E-SBC For example: copy storage-history cdr-storage-history my_cdrs.csv to tftp://company.com/cdrs The following procedure describes how to configure local CDR storage through the Web interface.  To configure local CDR storage: Open the Call Detail Record Settings page (Troubleshoot menu > Troubleshoot tab >...

  • Page 915: Configuring Radius Accounting

    The example shows the attribute in numeric format (32-bit number in 4 bytes). Figure 59-13: Example of Standard RADIUS Attribute Collected by Wireshark  Vendor-specific RADIUS attributes: RADIUS attributes that are specific to the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 916 Mediant 800B Gateway & E-SBC device (company) are referred to as Vendor-specific attributes (VSA). The CDR of VSAs are sent with a general RADIUS ID of 26 to indicate that they are vendor- specific (non-standard). In addition, the company's registered vendor ID (as registered with the Internet Assigned Numbers Authority or IANA) is also included in the packet.
  • Page 917 Stop h323-setup- Setup time in NTP String h323-setup- Start time format 1 time=09:33:26.621 Mon Dec 2014 Stop h323-call- Originator of call: String h323-call- Start origin origin=answer  "answer": Call Stop originated from Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 918 Mediant 800B Gateway & E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID the IP side (Gateway) or incoming leg (SBC)  "originate": Call originated from the Tel side (Gateway) or outgoing leg (SBC) h323-call-type Protocol type or...
  • Page 919 (for SBC calls, applicable only if media anchoring) acct-output- (Standard) Number of octets Numeric - Stop octets sent for that call duration (for SBC calls, applicable only if media anchoring) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 920 Mediant 800B Gateway & E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID acct-session-id (Standard) A unique String 34832 Start accounting identifier - match Stop start & stop acct-session- (Standard) For how many Numeric - Stop...
  • Page 921 User's Manual 59. Reporting Information to External Party (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 922: Querying Device Channel Resources Using Sip Options

    Mediant 800B Gateway & E-SBC 59.4 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 923: Diagnostics

    Part XI Diagnostics...

  • Page 925: Syslog And Debug Recording

    CDRs. Disabling a rule is useful, for example, if you no longer require the rule, but may need it in the future. Thus, instead of deleting the rule entirely, you can simply disable it. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 926 Mediant 800B Gateway & E-SBC Note: • If you want to configure a Log Filter rule that logs Syslog messages to a Syslog server (i.e., not to a Debug Recording server), you must enable Syslog functionality, using the 'Enable Syslog' (EnableSyslog) parameter (see 'Enabling Syslog' on page 936).
  • Page 927 For example, to specify IP Groups 1, 3 and 9, configure the parameter to "1,3,9" (without apostrophes).  Trunks/FXO/FXS pertaining to a module, using the syntax module number/port or port, for example: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 928 Mediant 800B Gateway & E-SBC Parameter Description  "1/2" (without apostrophes), means module 1, port 2  "1/[2-4]" (without apostrophes), means module 1, ports 2 through 4  The exclamation (!) wildcard character can be used for excluding a specific configuration entity from the filter. For example, to...

  • Page 929: Filtering Ip Network Traces

    HTTP. When the IP Trace option is selected, only the ‘Value’ parameter is applicable; the 'Syslog' and 'Capture Type' parameters are not relevant. The 'Value' parameter configures the Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 930: Configuring Syslog

    Mediant 800B Gateway & E-SBC Wireshark-like filtering expressions for your IP trace. The following Wireshark-like expressions are supported: Table 60-2: Supported Wireshark-like Expressions for 'Value' Parameter Expression Description ip.src, ip.dst Source and destination IP address ip.addr IP address - up to two IP addresses can be entered ip.proto...
  • Page 931 #0:DIGIT_EV [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237][SID:2ed1c8:96:5] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE: [S=301][SID:2ed1c8:96:5] (lgr_flow)(625) #0:DIGIT_EV [File: Line:-1] You can disable the inclusion of the message sequence Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 932 Mediant 800B Gateway & E-SBC Message Item Description number in Syslog messages, by setting the 'CDR Syslog Sequence Number' parameter to Disable (see 'Configuring Syslog' on page 936). Log Number Ignore this number; it has been replaced by the Message (lgr)(number) Sequence Number (described previously).

  • Page 933: Event Representation In Syslog Messages

    Invalid CID Error Invalid G723 Code Invalid payload length Invalid RTCP Packet Invalid SID Length Transmitter Received Illegal Command Lost Fax Frames In High Speed Mode Lost Modem Frames In High Speed Mode Misalignment Error Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 934: Identifying Audiocodes Syslog Messages Using Facility Levels

    Unknown Aggregation Payload Type Invalid Routing Flag Received 60.2.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.

  • Page 935: Syslog Fields For Answering Machine Detection (Amd)

    Info1:/ Additional Info2:/ Additional Info3 The Messages’ Severity is as follows: Table 60-6: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Critical RecoverableMsg Major RecoverableMsg Minor RecoverableMsg Warning Notice Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 936: Enabling Syslog

    Mediant 800B Gateway & E-SBC ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Indeterminate Notice Cleared Notice  Cleared Alarms: CLEAR-ALARM: <Alarm Name>; Textual Description: <Textual Description>; Severity <Alarm Severity>; Source <Alarm Source>; Unique ID: <Alarm Unique ID >; If exists Additional Info1:/ Additional Info2:/ Additional Info3: 60.2.2 Enabling Syslog...

  • Page 937: Configuring Reporting Of Management User Activities

    The following example shows a Web-user activity log (indicating a login action) with the above-mentioned information: 14:07:46.300 : 10.15.7.95 : Local 0 :NOTICE : [S=3149] [BID=3aad56:32] Activity Log: WEB: Successful login at 10.15.7.95:80. User: Admin. Session: HTTP (10.13.22.54) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 938 Mediant 800B Gateway & E-SBC The device can report the following user activities:  Modifications of individual parameters, for example: 14:33:00.162 : 10.15.7.95 : Local 0 :NOTICE : [S=3403] [BID=3aad56:32] Activity Log: Max Login Attempts was changed from '3' to '2'. User: Admin. Session: HTTP (10.13.22.54) ...

  • Page 939: Viewing Syslog Messages

    When debug recording is enabled and Syslog messages are also included in the debug recording, to view Syslog messages using Wireshark, you must install AudioCodes' Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and displayed using the "acsyslog" filter (instead of the regular "syslog"...

  • Page 940: Configuring Debug Recording

    You can select the Syslog messages displayed on the 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. 60.3 Configuring Debug Recording This section describes how to configure debug recording and how to collect debug recording packets.

  • Page 941: Collecting Debug Recording Messages

    Click Apply. 60.3.2 Collecting Debug Recording Messages To collect debug recording packets, use the open source packet capturing program, Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Note: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...

  • Page 942: Debug Capturing On Physical Voip Interfaces

    Note that the source IP address of the messages is always the OAMP IP address of the device. The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: 60.3.3 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets).
  • Page 943 TFTP or FTP server: # debug capture voip physical stop <TFTP/FTP server IP address> If no IP address is defined, the capture is saved on the device for later retrieval. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 944 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 945: 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 7.2 Mediant 800B Gateway & E-SBC...
  • Page 946 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

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

    The files may assist you in identifying the cause of the crash. The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. You can then provide the files to AudioCodes support team for troubleshooting. ...
  • Page 948 Mediant 800B Gateway & E-SBC  To delete the core dump file:  Navigate to the root CLI directory (enable mode), and then enter the following command: # clear debug-file The following procedure describes how to retrieve the debug file from the device through the Web interface.

  • Page 949: Fxo Line Testing

    You can also view the above information through the Web interface (see 'Viewing Port Information' on page 840). Note: Analog line testing is traffic affecting and therefore, do the test only for monitoring and when there are no active calls in progress. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 950 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 951: Testing Sip Signaling Calls

    You can also configure it through ini file (Test_Call) or CLI (configure troubleshoot > test- call test-call-table).  To configure a test call: Open the Test Call Rules table (Troubleshooting tab > Troubleshooting menu > Test Call folder > Test Call Rules). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 952 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 64-1: Test Call Rules Table - Add Dialog Box Configure a test call according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.
  • Page 953 "GW" and one to "SBC" for the 'Application Type'. If the parameter is set to "SBC", the device uses the SIP Interface set to "SBC".  [0] GW (default) = Gateway application  [2] SBC = SBC application Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 954 Mediant 800B Gateway & E-SBC Parameter Description Destination Transport Type Defines the transport type for outgoing calls.  dst-transport [-1] = Not configured (default)  [0] UDP [Test_Call_DestTransportType]  [1] TCP  [2] TLS Note: The parameter is applicable only if the 'Route By' parameter is set to Dest Address.
  • Page 955 To configure the DTMF signaling type (e.g., out-of-band or in- band) use the 'DTMF Transport Type' parameter (see 'Configuring DTMF Transport Types' on page 197).  The parameter is applicable only if you configure 'Call Party' to Caller. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 956: Starting And Stopping Test Calls

    Mediant 800B Gateway & E-SBC Parameter Description Schedule Interval Defines the interval (in minutes) between automatic outgoing test calls. schedule-interval The valid value range is 0 to 100000. The default is 0 (i.e., [Test_Call_ScheduleInterval] scheduling is disabled). Note: The parameter is applicable only if you configure 'Call Party' to Caller.
  • Page 957 Elapsed Time Duration of the test call since it was started (or restarted). Status (brief description) as displayed in the 'Test Status' field Test Status (see 'Viewing Test Call Status' on page 956). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 958: Configuring Dtmf Tones For Test Calls

    Mediant 800B Gateway & E-SBC Statistics Field Description Detailed Status Displays a detailed description of the test call status:  "Idle": Test call is currently not active.  "Scheduled - Established Calls: <number of established calls>, ASR: <ASR>%": Test call is planned to run...

  • Page 959: Configuring Basic Test Call

    Figure 64-4: Incoming Test Call Example  To configure basic call testing: Open the Test Call Settings page (Troubleshooting tab > Troubleshooting menu > Test Call folder > Test Call Settings). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 960: Configuring Sbc Test Call With External Proxy

    Mediant 800B Gateway & E-SBC In the 'Test Call ID' field, enter a prefix for the simulated endpoint: Figure 64-5: Configuring Basic Test Calls Click Apply. Note: • The Basic Test Call feature tests incoming calls only and is initiated only upon receipt of incoming calls with the configured prefix.

  • Page 961: Test Call Configuration Examples

    IP-to-IP routing through a proxy server. 64.8 Test Call Configuration Examples Below are a few examples of test call configurations.  Single Test Call Scenario: This example describes the configuration of a simple test Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 962 Mediant 800B Gateway & E-SBC call scenario that includes a single test call between a simulated test endpoint on the device and a remote endpoint. Figure 64-8: Single Test Call Example • Test Call Rules table configuration: ♦ Endpoint URI: "101"...
  • Page 963 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 964 Mediant 800B Gateway & 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 965: Pinging A Remote Host Or Ip Address

    IPv4 address. The ping is done using the following CLI command: # ping <IPv4 ip address or host name> source [voip] interface For a complete description of the ping command, refer to the CLI Reference Guide. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 966 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 967: Appendix

    Part XII Appendix...

  • Page 969: Dialing Plan Notation For Routing And Manipulation

    4 to 8, and suffix is 234, 235, or 236. The entered value would be the following: [4-8](23[4,5,6]). [n-m] or (n-m) Represents a range of numbers. Examples:  To depict prefix numbers from 5551200 to 5551300: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 970 Mediant 800B Gateway & E-SBC Notation Description  [5551200-5551300]#  To depict prefix numbers from 123100 to 123200:  123[100-200]#  To depict prefix and suffix numbers together:  03(100): for any number that starts with 03 and ends with 100.
  • Page 971 "x" wildcards (e.g., xx165xxxxx#); the prefix to add to the number would include the HEX values (e.g., +49 \287303\29 165-). Below is a list of common ASCII characters and their corresponding HEX values: ASCII Character HEX Value Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 972 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10298...

  • Page 973: Configuration Parameters Reference

    The default is 0.0.0.0 (i.e., the device can be accessed from any IP address). For example: WebAccessList_0 = 10.13.2.66 WebAccessList_1 = 10.13.77.7 For a description of the parameter, see 'Configuring Web and Telnet Access List' on page 73. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 974: Web Parameters

    Mediant 800B Gateway & E-SBC 67.1.2 Web Parameters The Web parameters are described in the table below. Table 67-2: Web Parameters Parameter Description Enable web access from all interfaces Enables Web access from any of the device's IP network interfaces. The feature applies to HTTP and HTTPS web-access-from-all-interfaces protocols.
  • Page 975 ("Admin" and "Admin" respectively), and deletes all other users that may have been configured.  [0] = (Default) Password and username retain their values.  [1] = Password and username are reset. Note: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 976: Telnet Parameters

    Mediant 800B Gateway & E-SBC Parameter Description  For the parameter to take effect, a device reset is required.  You cannot reset the username and password through the Web interface (by loading an ini file or on the AdminPage). To reset the username and password: ...

  • Page 977: Ini File Parameters

    $1$<obscured password> (e.g., $1$S3p+fno=).  [1] = Enable. All passwords are hidden and replaced by an asterisk (*). 67.1.5 SNMP Parameters The SNMP parameters are described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 978 > snmp trap > auto- Enables the device to send NAT keep-alive traps to the port send-keep-alive of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP [SendKeepAliveTrap] communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 979 [0] (Check box cleared) = Disabled (default)  [1] (Check box selected) = Enabled IP Address Defines the IP address of the remote host used as an SNMP Manager. The device sends SNMP traps to this IP address. ip-address Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 980 Mediant 800B Gateway & E-SBC Parameter Description [SNMPManagerTableIP_x] Enter the IP address in dotted-decimal notation, e.g., 108.10.1.255. Trap Port Defines the port number of the remote SNMP Manager. The device sends SNMP traps to this port. port The valid SNMP trap port range is 100 to 4000. The default [SNMPManagerTrapPort_x] port is 162.

  • Page 981: Serial Parameters

    'myauthkey', and ReadWriteGroup2. For a description of the table, see 'Configuring SNMP V3 Users' on page 92. 67.1.6 Serial Parameters The serial interface parameters are described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 982: Auxiliary And Configuration File Name Parameters

    Mediant 800B Gateway & E-SBC Table 67-6: Serial Parameters Parameter Description [DisableRS232] Enables the device's RS-232 (serial) port.  [0] = Enabled  [1] = (Default) Disabled The RS-232 serial port can be used to change the networking parameters and view error/notification messages. To establish serial communication with the device, see 'Establishing a CLI Session' on page Note: For the parameter to take effect, a device reset is required.
  • Page 983 0 is Trunk 1. Dial Plan File Defines the name of the Dial Plan file. This file should be created using AudioCodes DConvert utility (refer to DConvert Utility User's [DialPlanFileName] Guide). For the ini file, the name must be enclosed by single apostrophes, for example, 'dial_plan.dat'.

  • Page 984: Automatic Update Parameters

    Mediant 800B Gateway & E-SBC 67.1.8 Automatic Update Parameters The automatic update of software and configuration files parameters are described in the table below. Table 67-8: Automatic Update of Software and Configuration Files Parameters Parameter Description General Automatic Update Parameters CLI path: configure system >...
  • Page 985 [1] = Enable CRC for the entire file, including line order (i.e., same text must be on the same lines). If there are differences between the files, the device installs the downloaded file. If there are no differences, the device discards the newly downloaded file. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 986 Mediant 800B Gateway & E-SBC Parameter Description  [2] = Enable CRC for individual lines only. Same as option [1], except that the CRC ignores the order of lines (i.e., same text can be on different lines). tftp-block-size Defines the size of the TFTP data blocks (packets) when downloading a file from a TFTP server for the Automatic Update mechanism.
  • Page 987 [TLSCertFileUrl] Note: For the parameter to take effect, a device reset is required. tls-private-key Defines the URL address of the server on which the TLS private key file is located. [TLSPkeyFileUrl] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 988: Networking Parameters

    Mediant 800B Gateway & E-SBC Parameter Description [UserInfoFileURL] Defines the name of the User Information file and the URL address (IP address or FQDN) of the server on which the file is located. For example: http://server_name/file, https://server_name/file Note: The maximum length of the URL address is 99 characters.

  • Page 989: Multiple Voip Network Interfaces And Vlan Parameters

    [1] = OAMP (default)  [0] = Control Note: For the parameter to take effect, a device reset is required. 67.2.3 Routing Parameters The IP network routing parameters are described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 990: Open Solution Network (Osn) Parameters

    Mediant 800B Gateway & E-SBC Table 67-11: IP Network Routing Parameters Parameter Description Send ICMP Unreachable Enables sending of ICMP Unreachable messages. Messages  [0] Enable = (Default) Device sends these messages. configure network >  [1] Disable = Device does not send these messages.

  • Page 991: Quality Of Service Parameters

    [1] Enable For more information, refer to the SBA Installation and Maintenance Manual. Note: The feature will only be supported when AudioCodes SBA supports Skype for Business. Please contact your sales representative if you need more information. 67.2.5 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below.

  • Page 992: Nat Parameters

    Mediant 800B Gateway & E-SBC Parameter Description Profiles on page 439. Note: If the functionality is configured for a specific profile, the settings of this global parameter is ignored for calls associated with the profile. Control Premium QoS Global parameter defining the DiffServ value for Premium Control CoS content (Call Control applications).

  • Page 993: Dns 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 994: Dhcp Parameters

    Mediant 800B Gateway & E-SBC Parameter Description Internal DNS Table The table defines the internal DNS table for resolving host names into IP addresses. configure network > dns dns-to-ip The format of the ini file table parameter is: [DNS2IP] [Dns2Ip]...
  • Page 995 The format of the ini file table parameter is as follows: [ DhcpVendorClass ] FORMAT DhcpVendorClass_Index = DhcpVendorClass_DhcpServerIndex, DhcpVendorClass_VendorClassId; [ \DhcpVendorClass ] For a detailed description of the table, see Configuring the Vendor Class Identifier on page 220. DHCP Option Table Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 996: Ntp And Daylight Saving Time Parameters

    Mediant 800B Gateway & E-SBC Parameter Description DHCP Option table Defines additional DHCP Options that the device's DHCP server can use to service its DHCP clients. configure network > dhcp- server option The format of the ini file table parameter is as follows:...
  • Page 997 End Time / Day of Month Defines the date and time when DST ends. For a description of the format of this value, see the DayLightSavingTimeStart parameter. configure system > clock > summer-time > end [DayLightSavingTimeEnd] Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 998: Debugging And Diagnostics Parameters

    Mediant 800B Gateway & E-SBC Parameter Description Offset Defines the DST offset (in minutes). configure system > clock > The valid range is 0 to 120. The default is 60. summer-time > offset Note: The offset setting is applied only on the hour. For example, if...

  • Page 999: Sip Test Call Parameters

    [0] Disable [IgnoreBRILOSAlarm]  [1] Enable (default) Note: The parameter is applicable only to BRI interfaces. 67.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 1000 Mediant 800B Gateway & E-SBC Table 67-19: SIP Test Call Parameters Parameter Description Test Call DTMF String Defines the DTMF tone that is played for answered test calls (incoming and outgoing). configure troubleshoot > test-call settings > testcall- The DTMF string can be up to 15 strings. The default is "3212333". If no dtmf-string string is defined (empty), DTMF is not played.

  • Page 1001: Syslog, Cdr And Debug Parameters

     [4] Start & End & Connect Call = CDR report is sent to Syslog at the start, at connection, and at the end of each call. Note: Version 7.2 1001 Mediant 800B Gateway & E-SBC...
  • Page 1002 Mediant 800B Gateway & E-SBC Parameter Description  For the SBC application, the parameter enables only signaling- related CDRs. To enable media-related CDRs for SBC calls, use the MediaCDRReportLevel parameter.  The CDR Syslog message complies with RFC 3164 and is identified by: Facility = 17 (local1) and Severity = 6 (Informational).
  • Page 1003 (1). When the CPU usage decreases to 20% less than the threshold (e.g., 50%), the debug level changes to Detailed (5). Note: The device does not increase the debug level to a level that is Version 7.2 1003 Mediant 800B Gateway & E-SBC...
  • Page 1004 Mediant 800B Gateway & E-SBC Parameter Description higher than what you configured for the 'Debug Level' parameter. Syslog Facility Number Defines the Facility level (0 through 7) of the device’s Syslog messages, according to RFC 3164. This allows you to identify Syslog [SyslogFacility] messages generated by the device.
  • Page 1005 Core Dump file. [CoreDumpDestIP] By default, no IP address is defined. Logging Filters Table Logging Filters Table The table defines log filtering rules for Syslog messages and debug recordings. configure troubleshoot > Version 7.2 1005 Mediant 800B Gateway & E-SBC...

  • Page 1006: Resource Allocation Indication Parameters

    Mediant 800B Gateway & E-SBC Parameter Description logging logging-filters The format of the ini file table parameter is: [LoggingFilters] [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_FilterType, LoggingFilters_Value, LoggingFilters_LogDestination, LoggingFilters_CaptureType, LoggingFilters_Mode; [ \LoggingFilters ] For a detailed description of the table, see 'Configuring Log Filter Rules' on page 925.

  • Page 1007: Packetsmart Parameters

    Assigns an IP network interface (configured in the IP Interfaces table) that handles the voice traffic. configure system > packetsmart monitor Note: For the parameter to take effect, a device reset is required. voip interface-if [PacketSmartMonitorInterface] Version 7.2 1007 Mediant 800B Gateway & E-SBC...

  • Page 1008: Ha Parameters

    Mediant 800B Gateway & E-SBC Parameter Description Network Interface Assigns an IP network interface (configured in the IP Interfaces table) for communicating with the PacketSmart server. This is configure system > typically the OAMP interface. packetsmart network voip interface-if Note: For the parameter to take effect, a device reset is required.

  • Page 1009: Security Parameters

    [HAPingRetries] The valid value is 0 to 100. The default 2. 67.5 Security Parameters This subsection describes the device's security parameters. Version 7.2 1009 Mediant 800B Gateway & E-SBC...

  • Page 1010: General Security Parameters

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

  • Page 1012: Https Parameters

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

  • Page 1013: Srtp Parameters

    IP Profile. Offered SRTP Cipher Suites Defines the offered crypto suites (cipher encryption algorithms) for SRTP. configure voip > media  security > offer-srtp-cipher [0] All = (Default) All available crypto suites. Version 7.2 1013 Mediant 800B Gateway & E-SBC...

Table of Contents