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 & enterprise sbc (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: Quick Manual
User's Manual
AudioCodes Mediant™ Family of Media Gateways & Session Border Controllers
Mediant 800B Gateway
& Enterprise SBC (E-SBC)
Version 7.2

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

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 & Enterprise SBC (E-SBC) Version 7.2...

  • Page 3: Table Of Contents

    6.2.2 Customizing the Product Name ................74 6.2.3 Customizing the Favicon ..................74 6.2.4 Creating a Login Welcome Message ............... 76 Configuring Additional Management Interfaces ............. 76 Configuring Management User Accounts .............. 79 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 4 Mediant 800B Gateway & E-SBC Displaying Login Information upon Login ............... 83 Viewing Logged-In User Information ..............84 Configuring Web Session and Access Settings ............. 84 Changing Login Password for Administrator and Monitor Users ......86 Configuring Secured (HTTPS) Web ............... 86 6.10 Web Login Authentication using Smart Cards ............
  • Page 5 12.11.2 Configuring the Internal SRV Table ...............171 12.12 Open Solution Network (OSN) Server ..............173 12.12.1 Configuring Native VLAN for OSN Server .............173 12.12.2 Disabling Internal Switch Port for OSN ..............174 12.13 Multiple Routers Support ..................174 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 6 Mediant 800B Gateway & E-SBC 13 Security ......................175 13.1 Configuring Firewall Settings ................175 13.2 Configuring General Security Settings ..............180 13.3 Intrusion Detection System .................. 181 13.3.1 Enabling IDS ......................181 13.3.2 Configuring IDS Policies ..................182 13.3.3 Assigning IDS Policies ...................186 13.3.4 Viewing IDS Alarms ....................188...
  • Page 7 15.6.4 Configuring QoS-Based Routing by Routing Server ..........297 15.7 HTTP-based Proxy Services ................299 15.7.1 Enabling the HTTP Proxy Application ..............300 15.7.2 Debugging Remote HTTP Services ..............300 15.7.3 Configuring HTTP Interfaces .................300 15.7.4 Configuring HTTP Proxy Services .................302 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 8 15.8.2.2 Adding ELINs to the Location Information Server ......... 310 15.8.2.3 Passing Location Information to the PSTN Emergency Provider ..311 15.8.3 AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN .....312 15.8.3.1 Detecting and Handling E9-1-1 Calls ............ 312 15.8.3.2 Pre-empting Existing Calls for E9-1-1 Calls ..........
  • Page 9 22.7 ISDN Overlap Dialing ................... 512 22.7.1 Collecting ISDN Digits and Sending Complete Number in SIP ......512 22.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 ....513 22.8 Redirect Number and Calling Name (Display) ............. 514 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 10 Mediant 800B Gateway & E-SBC 23 Trunk Groups ....................517 23.1 Configuring Trunk Groups ..................517 23.2 Configuring Trunk Group Settings Table .............. 519 24 Routing ......................525 24.1 Configuring Tel-to-IP Routing Rules ..............525 24.2 Configuring IP-to-Tel Routing Rules ..............534 24.3 Configuring a Gateway Routing Policy Rule ............
  • Page 11 28.9 Configuring Call Waiting ..................641 28.10 Rejecting Anonymous Calls ................. 642 28.11 Configuring FXS Distinctive Ringing and Call Waiting Tones per Source/Destination Number ..................643 28.12 FXS/FXO Coefficient Types ................. 644 28.13 FXO Operating Modes ..................645 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 12 Mediant 800B Gateway & E-SBC 28.13.1 FXO Operations for IP-to-Tel Calls ................645 28.13.1.1 One-Stage Dialing ................. 646 28.13.1.2 Two-Stage Dialing ................. 647 28.13.1.3 DID Wink ....................647 28.13.2 FXO Operations for Tel-to-IP Calls ................648 28.13.2.1 Automatic Dialing .................. 648 28.13.2.2 Collecting Digits Mode................649 28.13.2.3 FXO Supplementary Services ...............
  • Page 13 36.3.2 Using Dial Plan Tags for Routing Destinations .............761 36.3.3 Dial Plan Backward Compatibility ................764 36.4 Using Dial Plan Tags for Outbound Manipulation ..........765 36.5 Using Dial Plan Tags for Call Setup Rules ............766 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 14 Mediant 800B Gateway & E-SBC 36.6 Using Dial Plan Tags for Message Manipulation ..........766 37 Configuring Malicious Signatures ..............767 38 Advanced SBC Features ................. 769 38.1 Configuring Call Preemption for SBC Emergency Calls ........769 38.2 Emergency Call Routing using LDAP to Obtain ELIN .......... 770 38.3 Enabling Interworking of SIP and SIP-I Endpoints ..........
  • Page 15 47.6.2 Dialing Plans for Digit Collection ................840 47.6.3 Dial Plan Prefix Tags for IP-to-Tel Routing............843 47.6.4 Obtaining IP Destination from Dial Plan File ............845 47.6.5 Modifying ISDN-to-IP Calling Party Number............845 47.6.6 Viewing Information of Installed Dial Plan File ............847 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 16 Mediant 800B Gateway & E-SBC 47.7 User Information File .................... 847 47.7.1 Enabling the User Info Table .................847 47.7.2 Gateway User Information for PBX Extensions and "Global" Numbers ....848 47.7.2.1 Configuring GW User Info Table through Web Interface ...... 849 47.7.2.2 Configuring GW User Info Table through CLI ........
  • Page 17 60.1 Viewing Tel-IP Call Counters ................945 60.2 Viewing SBC Registered Users ................947 60.3 Viewing Proxy Set Status ..................947 60.4 Viewing Registration Status ................. 949 60.5 Viewing IP Connectivity ..................951 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 18 64.2.1 Syslog Message Format ..................1012 64.2.1.1 Event Representation in Syslog Messages ........1015 64.2.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ..1016 64.2.1.3 Syslog Fields for Answering Machine Detection (AMD) ..... 1017 64.2.1.4 SNMP Alarms in Syslog Messages ............. 1017 64.2.2 Enabling Syslog ....................
  • Page 19 72.3.1 General Parameters ................... 1082 72.3.2 SIP Test Call Parameters ................... 1084 72.3.3 Syslog, CDR and Debug Parameters ..............1085 72.3.4 Resource Allocation Indication Parameters............1091 72.3.5 PacketSmart Parameters ..................1091 72.4 HA Parameters ....................1092 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 20 Mediant 800B Gateway & E-SBC 72.5 Security Parameters ................... 1094 72.5.1 General Security Parameters ................1094 72.5.2 HTTPS Parameters .................... 1097 72.5.3 SRTP Parameters ....................1097 72.5.4 TLS Parameters ....................1100 72.5.5 SSH Parameters ....................1102 72.5.6 IDS Parameters ....................1103 72.5.7 OCSP Parameters ....................
  • Page 21 72.14.4 Call Setup Rules Parameters ................1327 72.14.5 HTTP-based Services ..................1328 72.14.6 HTTP Proxy Parameters ..................1329 73 Channel Capacity ..................1331 73.1 Channel Capacity and Capabilities ..............1332 74 Technical Specifications ................1335 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 22 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 23: 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 24 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 25 Buyer may receive such source code by contacting AudioCodes, by following the instructions available on AudioCodes website.
  • Page 26 Mediant 800B Gateway & E-SBC LTRT Description  New parameters: IPGroup_SBCKeepOriginalCallID; IPGroup_SBCDialPlanName; IPGroup_CallSetupRulesSetId; CallSetupRules_QueryType; CallSetupRules_QueryTarget; IpProfile_SBCVoiceQualityEnhancement; IpProfile_SBCMaxOpusBW; IpProfile_SBCISUPVariant; WebLoginBlockAutoComplete; EnforcePasswordComplexity; AUPDCliScriptURL; TrunkLifeLineType.  Updated sections: Changing Index Position of Table Rows; Searching for 10621 Configuration Parameters; Configuring TLS Certificate Contexts (IPSec removed);...
  • Page 27 Recording (max.); Configuring Remote Web Services (QoS routing); Centralized Third-Party Routing Server (QoS); Configuring Proxy Sets; Configuring CAS State Machines (note); Alternative Routing Based on IP Connectivity; Configuring SBC IP-to-IP Routing; Configuring IP Group Sets Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 28 Mediant 800B Gateway & E-SBC LTRT Description (dial plan tags); Configuring Dial Plans; Software Upgrade; Installing License Key through Web Interface; Upgrading SBC Capacity Licenses by License Pool Manager Server; Configuring RADIUS Accounting (typo); Configuring DTMF Tones for Test Calls; Configuring Basic Test Calls; Configuring SBC Test Call with External Proxy (removed);...
  • Page 29 (phys link); AudioCoders_Sce (global parameter removed); IpProfile_SCE (removed); IpProfile_SBCRemoteReferBehavior (new option 5); IPProfile_SBCRemoteHoldFormat (new option 6); IP2IPRouting_InternalAction; SBCCDRFormat_Title (max. char.); WebUsers (CLI name); EnableWebAccessFromAllInterfaces; FaxBypassPayloadType; ModemBypassPayloadType; EnableSilenceCompression (removed)  New parameters: SIPInterface_AdditionalUDPPorts; IPProfile_SBCSupportMultipleDTMFMethods; AdditionalManagementInterfaces; EnableWebAccessFromAllInterfaces; DefaultTerminalWindowHeight; ActiveAlarmTableMaxSize; SBCRemoveSIPSFromNonSecuredTransport Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 30 Mediant 800B Gateway & E-SBC Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads. User's Manual...

  • Page 31: Introduction

    User's Manual 1. Introduction Introduction This User's Manual describes how to configure and manage your AudioCodes product (hereafter, referred to as device). This document is intended for the professional person responsible for installing, configuring and managing the device. Product Overview The Mediant 800 Media Gateway &...

  • Page 32: Typographical Conventions

    Mediant 800B Gateway & E-SBC Typographical Conventions This document uses the following typographical conventions to convey information: Table 1-1: Typographical Conventions Convention Description Example Boldface font Used for the following Web Click the Add button. interface elements:  Buttons ...
  • Page 33 SIP Trunking service provider, the SRD of the SIP Trunk would be configured as a Shared Sharing Policy. SRDs whose resources are not shared, would be configured with an Isolated Sharing Policy. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 34 Mediant 800B Gateway & E-SBC Configuration Terms Description IP Profile 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 buffervoice coders, fax signaling method, SIP header support (local termination if not supported), and media security method.
  • Page 35 "serving" IP Group. Registration is for REGISTER messages, which are initiated by the device on behalf of the "serving" SIP entity. The associations between the configuration entities are summarized in the following figure: Figure 1-1: Association of Configuration Entities Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 36: Gateway Application

    Mediant 800B Gateway & E-SBC 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. Depending on configuration and network topology, the call process may include additional stages or a different order of stages.
  • Page 37 Trunk Group, or calling or called telephone number prefix and suffix. The SIP entity can be denoted by an IP Group or other IP destinations such as IP address, FQDN, E.164 Telephone Number Mapping (ENUM service), and Lightweight Directory Access Protocol (LDAP). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 38 Mediant 800B Gateway & E-SBC Configuration Terms Description IP-to-Tel (Trunk Group) IP-to-Tel routing rules are used to route incoming IP calls to Trunk Routing Rules Groups. The specific channel pertaining to the Trunk Group to which the call is routed can also be configured.

  • Page 39: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

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

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

  • Page 45: 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. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 46 Mediant 800B Gateway & E-SBC Access the Web interface: On your computer, start a Web browser and in the URL address field, enter the default IP address of the device; 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 47: 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 48 Mediant 800B Gateway & E-SBC Apply your settings: (network-if-0)# activate Cable the device to your network. You can now access the device's management interface using this new OAMP IP address. User's Manual Document #: LTRT-10632...

  • Page 49: Management Tools

    Part II Management Tools...

  • Page 51: Introduction

    Configuration ini file - see 'INI File-Based Management' on page 105 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 1055. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 52 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 53: 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 54: 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 55: Areas Of The Gui

    6.1.3 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 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 56 Mediant 800B Gateway & E-SBC Table 6-1: Description of the Web GUI Areas 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).

  • Page 57: Accessing Configuration Pages From Navigation Tree

    For example, the home page of the Setup menu - Administration tab combination is the Time & Date page.  Folders: (Callout #2) Folders group items of similar functionality. To open and close a folder, simply click the folder name. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 58 Mediant 800B Gateway & E-SBC  Items: (Callout #3) Items open configuration pages. In some cases, an item may be listed under a sub-item. An item can open a page containing stand-alone parameters or a table. If it opens a page with stand-alone parameters, the item is displayed in italics.

  • Page 59: Configuring Stand-Alone Parameters

    If you change the value of a parameter that is displayed with a lightning-bolt icon (as shown in the example below), you must save your settings to flash memory with a device reset for your changes to take effect. When you change such a parameter and Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 60 Mediant 800B Gateway & E-SBC then click Apply, the Reset button on the toolbar is encircled by a red border. If you click the button, the Maintenance Actions page opens, which provides commands for doing this (see 'Basic Maintenance' on page 821).

  • Page 61: Configuring Table Parameters

    Position of Table Rows' on page 68). Action Drop-down menu providing commands (e.g., Register and Un- Register). Note: The button appears only in certain tables (e.g., Accounts table). Added table rows displaying only some of the table parameters (columns). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 62: Adding Table Rows

    Mediant 800B Gateway & E-SBC Item # Button Detailed view of a selected row, displaying all parameters. Link to open the "child" table of the "parent" table. A link appears only if the table has a "child" table. The "child" table is opened for the selected row.
  • Page 63 The table (e.g., IP Groups table) and dialog box in which the Add new option was selected is minimized to the bottom-left corner of the Web interface and a dialog box appears for adding a new row in the referenced-table (e.g., Proxy Sets table). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 64: Modifying Table Rows

    Mediant 800B Gateway & E-SBC Configure the referenced-row and click Apply; the referenced-table (e.g., Proxy Sets table) closes and you are returned to the dialog box in which you selected the Add new option (e.g., IP Groups table), where the newly added row now appears selected.

  • Page 65: Invalid Value Indications

    'Index' column of the row. ♦ Page title of the table. The total number of invalid rows in the table is also displayed with the icon. ♦ Item in the Navigation tree that opens the table. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 66 Mediant 800B Gateway & E-SBC For example, if you do not configure the 'SIP Interface' field (mandatory) for Proxy Set #0, the Invalid Line icons are displayed for the Proxy Sets table, as shown below: Figure 6-11: Invalid Line (Row) Icons ...

  • Page 67: Viewing Table Rows

    Displays the last table page (i.e., page with last index row) Currently displayed table page. To open a specific table page, enter the page number and then press the Enter key. Total number of table pages. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 68: Sorting Tables By Column

    Mediant 800B Gateway & E-SBC 6.1.6.7 Sorting Tables by Column 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.

  • Page 69: Searching Table Entries

    You can search in the Web interface for parameter names (standalone or table parameters) and values. The search key can include the full parameter name (Web or ini file name) or a substring of it. If you search for a substring, all parameters containing the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 70 Mediant 800B Gateway & E-SBC substring in their names are listed in the search result. For example, to search for the parameter 'Telnet Server TCP Port', you can use any of the following search keys:  "Telnet Server TCP Port" (Web name) ...

  • Page 71: Getting Help

    The product name also affects other management interfaces. • In addition to Web-interface customization, you can customize the following to reference your company instead of AudioCodes: √ SNMP Interface: Product system OID (see the SNMPSysOid parameter) and trap Enterprise OID (see the SNMPTrapEnterpriseOid parameter).

  • Page 72: Replacing The Corporate Logo

    Mediant 800B Gateway & E-SBC 6.2.1 Replacing the Corporate Logo You can replace the default corporate logo image (i.e., AudioCodes logo) that is displayed in the Web interface. The logo appears in the following Web areas:  Web Login screen: Figure 6-20: Corporate Logo on Web Login Screen ...

  • Page 73: Replacing The Corporate Logo With Text

    WebLogoText = < your text > Load the ini file using the Auxiliary Files page (see Loading Auxiliary Files on page 831). Reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 74: Customizing The Product Name

    6.2.3 Customizing the Favicon You can replace the default favicon (i.e., AudioCodes) with your own personalized favicon. Depending on the browser, the favicon is displayed in various areas of your browser, for example, in the URL address bar, on the page tab, and when bookmarked:...
  • Page 75 The logo image file type can be ICO, GIF, or PNG. • The maximum size of the image file can be 16 Kbytes. • Ignore the ini Parameters option, which is located on the left pane of the Admin page. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 76: Creating A Login Welcome Message

    Mediant 800B Gateway & E-SBC 6.2.4 Creating a Login Welcome Message You can create a personalized welcome message that is displayed on the Web Login screen. The message always begins with the title "Note" and has a color background, as...
  • Page 77 Note: Each row must be configured with a unique index. erfaces_Index] Interface Name Assigns an IP network interface (from the IP Interfaces table) to the management interface. interface-name For more information on IP network interfaces, see Configuring IP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 78 Mediant 800B Gateway & E-SBC Parameter Description [AdditionalManagementInt Network Interfaces on page 146. erfaces_InterfaceName] Note:  Only Control- and/or Media-type IP network interfaces can be associated with additional management interfaces.  An IP network interface can be associated with only one additional management interface.

  • Page 79: Configuring Management User Accounts

    Access Settings' on page 84). 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 80 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 81 Additional Master users can be added, edited and deleted only by Master users.  If only one Master user exists, it can be deleted only by itself.  Master users can add, edit, and delete Security Administrators (except the last Security Administrator). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 82 Mediant 800B Gateway & E-SBC Parameter Description  Only Security Administrator and Master users can add, edit, and delete Administrator and Monitor users. SSH Public Key Defines a Secure Socket Shell (SSH) public key for RSA public-key authentication (PKI) of the remote user when logging into the device's public-key CLI through SSH.

  • Page 83: Displaying Login Information Upon Login

    Open the Web Settings page (Setup menu > Administration tab > Web & CLI folder > Web Settings). Under the Security group, from the 'Display Last Login Information' drop-down list, select Enable. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 84: Viewing Logged-In User Information

    Mediant 800B Gateway & E-SBC Once enabled, each time you login to the device, the Login Information window is displayed, as shown in the example below: Figure 6-31: Login Information Window To close the window, click Close. Viewing Logged-In User Information The username of the currently logged in user is displayed in the top-right corner of the Web interface.
  • Page 85 (previous step). Click Apply. For a detailed description of the above parameters, see 'Web Parameters' on page 1056. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Changing Login Password for Administrator and Monitor Users If you are logged in as a user with Administrator level or Monitor level, you can change your login password by performing the following procedure. Note: •...

  • Page 87: 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 88 Mediant 800B Gateway & E-SBC Note: • Configure the IP address of the computer from which you are currently logged into the device as the first authorized IP address in the Access List. If you configure any other IP address, access from your computer will be immediately denied.

  • Page 89: Cli-Based Management

    'Telnet Server TCP Port': Enter the port number of the embedded Telnet server. • 'Telnet Server Idle Timeout': Enter the duration of inactivity in the Telnet session after which the session automatically ends. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Click Apply, and then reset the device with a save-to-flash for your settings to take effect. For a detailed description of the Telnet parameters, see 'Telnet Parameters' on page 1061. 7.1.2 Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text.
  • Page 91 Under the 'Authentication parameters' group, click Browse and then locate the private key file that you created and saved in Step 4. Connect to the device with SSH using the username "Admin"; RSA key negotiation Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 92: Configuring Maximum Telnet/Ssh Sessions

    Mediant 800B Gateway & E-SBC occurs automatically and no password is required.  To configure RSA public keys for Linux (using OpenSSH 4.3): Run the following command to create a new key in the admin.key file and to save the public portion to the admin.key.pub file:...

  • Page 93: Viewing Current Cli Sessions

    The current session from which this show command was run is displayed with an asterisk (*). Note: The device can display management sessions of up to 24 hours. After this time, the duration counter is reset. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 94: Terminating A User's Cli Session

    Mediant 800B Gateway & E-SBC Terminating a User's CLI Session You can terminate users that are currently logged in to the device's CLI. This applies to users logged in to the CLI through RS-232 (console), Telnet, or SSH.  To terminate the CLI session of a specific CLI user: Establish a CLI session with the device.
  • Page 95 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 96 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 97: 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 98 Mediant 800B Gateway & E-SBC For detailed descriptions of the SNMP parameters, see 'SNMP Parameters' on page 1062.  To configure SNMP community strings: Open the SNMP Community Settings page (Setup menu > Administration tab > SNMP folder > SNMP Community Settings).

  • Page 99: 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 100 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-2: SNMP Trap Destinations Table Configure the SNMP trap manager according to the table below.

  • Page 101: 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 102: 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-3: SNMP Trusted Managers Table Configure an IP address (in dotted-decimal notation) for one or more SNMP Trusted Managers.
  • Page 103 [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 104 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 105: 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 106 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 107: 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 913. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 108: 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 109 $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 110: 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 111: General System Settings

    Part III General System Settings...

  • Page 113: 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 114 Mediant 800B Gateway & E-SBC peer certificate is received (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 115 [5] TLSv1.0 and TLSv1.2 = Only TLS 1.0 and TLS 1.2.  [6] TLSv1.1 and TLSv1.2 = Only TLS 1.1 and TLS 1.2.  [7] TLSv1.0 TLSv1.1 and TLSv1.2 = Only TLS 1.0, TLS 1.1 and TLS 1.2 (excludes SSL 3.0). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 116 Mediant 800B Gateway & E-SBC Parameter Description DTLS Version Defines the Datagram Transport Layer Security (DTLS) version, which is used to negotiate keys for WebRTC calls. [TLSContexts_DTLSVersion]  [0] Any (default)  [1] DTLSv1.0  [2] DTLSv1.2 For more information on WebRTC, see WebRTC on page 774.

  • Page 117: 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 118 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 119 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 120: Viewing Certificate Information

    Mediant 800B Gateway & E-SBC 10.3 Viewing Certificate Information You can view information of TLS certificates installed on the device per TLS Context.  To view certificate information: Open the TLS Contexts table (see 'Configuring TLS Certificate Contexts' on page 113).

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

    Click the Certificate Information link located below the table. Make sure that the 'Private key' field displays "OK"; otherwise (i.e., displays "Does not match certificate"), consult with your security administrator. Figure 10-5: Verifying Private Key Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 122: Generating Private Keys For Tls Contexts

    Mediant 800B Gateway & E-SBC 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.  To generate a new private key for a TLS Context: Open the TLS Contexts table (see 'Configuring TLS Certificate Contexts' on page 113).

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

    Certificate link located below the table; the Change 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 124: Importing Certificates 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 125 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 126: 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 127: Configuring Tls Server Certificate Expiry Check

    Open the TLS Contexts table (see 'Configuring TLS Certificate Contexts' on page 113). Select the required TLS Context index row, and then click the Change Certificate link located below the table; the Change Certificates page appears. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 128 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 129: 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 130: 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 131: 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 132 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 133: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 135: 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 136 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 137 To open the Ethernet Groups table, click any Ethernet Group icon, and then from the drop- down menu, choose View List. You can then view and edit all the Ethernet Groups in the table. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 138: 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 139 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 140: 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 141 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 142: 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 143 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 144 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 145 Group. For example, if VLAN 1 is configured with the highest MTU (100 bytes) out of all your VLANs, you can configure an untagged VLAN with an MTU value of either 100 bytes or greater. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 146: Configuring Ip Network Interfaces

    Mediant 800B Gateway & E-SBC 12.5 Configuring IP Network Interfaces You can configure a single VoIP network interface for all applications, including OAMP (management traffic), call control (SIP signaling messages), and media (RTP traffic), or you can configure multiple logical, IP network interfaces for these applications. You may need to logically separated network segments for these applications for administration and security.
  • Page 147 IP Interfaces). Click New; the following dialog box appears: Figure 12-3: IP Interfaces Table - Dialog Box Configure the IP network interface according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 148 Mediant 800B Gateway & E-SBC Note: • If you modify the OAMP interface's address, after clicking Apply you will lose connectivity with the device and need to access the device with the new address. • If you edit or delete an IP interface, current calls using the interface are immediately terminated.
  • Page 149 When traffic is sent from this interface to an unknown destination gateway (i.e., not in the same subnet and not defined for any static routing [InterfaceTable_Gateway] rule), it is forwarded to this default gateway. By default, no value is defined. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 150: Assigning Ntp Services To Application Types

    Mediant 800B Gateway & E-SBC Parameter Description Primary DNS Defines the primary DNS server's IP address (in dotted-decimal notation), which is used for translating domain names into IP primary-dns addresses for the interface. [InterfaceTable_PrimaryDNSSe By default, no IP address is defined.

  • Page 151: Networking Configuration Examples

    VLAN ID and default gateway: Table 12-8: Example of VoIP Interfaces per Application Type in IP Interfaces table Application Interface Prefix Default Ethernet Index IP Address Name Type Mode Length Gateway Device Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 152: Voip Interfaces For Combined Application Types

    Mediant 800B Gateway & E-SBC Application Interface Prefix Default Ethernet Index IP Address Name Type Mode Length Gateway Device OAMP IPv4 192.168.0.2 192.168.0.1 ManagementIF Manual Control IPv4 200.200.85.14 200.200.85.1 myControlIF Manual Media IPv4 211.211.85.14 211.211.85.1 myMediaIF Manual Static Routes table: A routing rule is required to allow remote management from a host in 176.85.49.0 / 24:...

  • Page 153: Voip Interfaces With Multiple Default Gateways

    The Static Routes table lets you configure up to 30 static IP routing rules. Static routes let you communicate with LAN networks that are not located behind the Default Gateway that is specified for an IP network interface in the IP Interfaces table, from which the packets Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 154 Mediant 800B Gateway & E-SBC are sent. Before sending an IP packet, the device searches the Static Routes table for an entry that matches the requested destination host/network. If an entry is found, the device sends the packet to the gateway that is configured for the static route. If no explicit entry is found, the packet is sent to the Default Gateway as configured for the IP interface in the IP Interfaces table.

  • Page 155: Configuration Example Of Static Ip Routes

     The static route in the Static Routes table must be associated with the IP network interface in the IP Interfaces table. This is done by configuring the 'Ethernet Output Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 156: Troubleshooting The Static Routes Table

    Mediant 800B Gateway & E-SBC Name' field in the Static Routes table to the same value as configured in the 'Ethernet Device' field in the IP Interfaces table.  The static route's Gateway address in the Static Routes table is in the same subnet as the IP address of the IP network interface in the IP Interfaces table.

  • Page 157: Network Address Translation Support

    If NAT is not configured by any of the above-mentioned methods, the device sends the packet according to its IP address configured in the IP Interfaces table. Note: The priority list above is applicable only to Gateway calls. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC The figure below illustrates the NAT problem faced by SIP networks when the device is located behind a NAT: Figure 12-5: Device behind NAT and NAT Issues 12.7.1.1 Configuring a Static NAT IP Address for All Interfaces You can configure a global (public) IP address of the router to enable static NAT between the device and the Internet for all network interfaces.

  • Page 159: Configuring Nat Translation Per Ip Interface

    Interfaces table) to the rule. Outgoing packets sent from the src-interface-name specified network interface are NAT'ed. [NATTranslation_SrcIPInterfaceName] By default, no value is defined. To configure IP network interfaces, see 'Configuring IP Network Interfaces' on page 146. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 160: Remote Ua Behind Nat

    Mediant 800B Gateway & E-SBC Parameter Description Source Start Port Defines the optional starting port range (0-65535) of the IP interface, used as matching criteria for the NAT rule. If not src-start-port configured, the match is done on the entire port range. Only...

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

    UA. When the UA is located behind NAT, although the UA sends its private IP address:port in the original SIP message (INVITE), the device receives the media packets with a source address of a public IP address:port (i.e., Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 162 Mediant 800B Gateway & E-SBC allocated by the NAT server). Therefore, to ensure that the media reaches the UA, the device must send it to the public address. The device identifies whether the UA is located behind NAT by comparing the source IP address of the first received media packet with the IP address and UDP port of the first received SIP message (INVITE) when the SIP session was started.
  • Page 163 STUN binding requests sent on the RTP and RTCP ports. ICE tries each candidate and selects the one that works (i.e., media can flow between the clients). The following figure shows a simple illustration of ICE: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 164 Mediant 800B Gateway & E-SBC The device's support for ICE-Lite means that it does not initiate the ICE process. Instead, it supports remote endpoints that initiate ICE to discover their workable public IP address with the device. Therefore, the device supports the receipt of STUN binding requests for connectivity checks of ICE candidates and responds to them with STUN responses.

  • Page 165: 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 166: Configuring Quality Of Service

    Mediant 800B Gateway & E-SBC ♦ 'Fax Relay Rx/Tx Timeout' Click Apply, and then save your settings to flash memory. 12.9 Configuring Quality of Service This section describes how to configure Layer-2 and Layer-3 Quality of Service (QoS). 12.9.1 Configuring Class-of-Service QoS The QoS Settings page lets you configure Layer-3 Class-of-Service Quality of Service (QoS).
  • Page 167 Defines the DiffServ value for Premium Control CoS content (Call Control applications). control-qos The valid range is 0 to 63. The default is 40. [PremiumServiceClassControlDiffServ] Note: You can also configure the the parameter per IP Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Parameter Description Profile (IpProfile_SigIPDiffServ) or Tel Profile (TelProfile_SigIPDiffServ). Gold QoS Defines the DiffServ value for Gold CoS content (streaming applications). gold-qos The valid range is 0 to 63. The default is 26. [GoldServiceClassDiffServ] Bronze QoS Defines the DiffServ value for Bronze CoS content (OAMP applications).

  • Page 169: Configuring Icmp Messages

    To enable sending and receipt of ICMP Redirect messages, configure the 'Send and Received ICMP Redirect Messages' parameter to Enable. • To enable sending of ICMP Destination Unreachable messages, configure the 'Send ICMP Unreachable Messages' parameter to Enable. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 170: Dns

    Mediant 800B Gateway & E-SBC 12.11 DNS You can use the device's embedded domain name server (DNS) or an external, third-party DNS to translate domain names into IP addresses. This is useful if domain names are used as the destination in call routing. The device supports the configuration of the following DNS types: ...

  • Page 171: Configuring The Internal Srv Table

    Web interface. You can also configure it through ini file (SRV2IP) or CLI (configure network > dns srv2ip).  To configure the device's SRV table: Open the Internal SRV table (Setup menu > IP Network tab > DNS folder > Internal SRV). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 172 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 12-15: Internal SRV Table - Add Dialog Box Configure an SRV rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.

  • Page 173: Open Solution Network (Osn) Server

    VLAN configured in the Ethernet Devices table (see 'Configuring Underlying Ethernet Devices' on page 142), which is assigned to a Media and/or Control application in the IP Interfaces table. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 174: Disabling Internal Switch Port For Osn

    Mediant 800B Gateway & E-SBC 12.12.2 Disabling Internal Switch Port for OSN You can enable or disable the Ethernet port of the device's internal switch, which interfaces with the OSN server. If the port is not blocked, you can optionally access the OSN server through any Ethernet port on the device's front panel (instead of through the OSN module's Ethernet ports located on the rear panel).

  • Page 175: Security

    (block) the packet. Once a rule in the table is located, subsequent rules further down the table are ignored. If the end of the table is reached without a match, the packet is accepted. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 176 Mediant 800B Gateway & E-SBC Note: • The rules configured by the Firewall table apply to a very low-level network layer and overrides all other security-related configuration. Thus, if you have configured higher-level security features (e.g., on the Application level), you must also configure firewall rules to permit this necessary traffic.
  • Page 177 ‘Source IP’. The default is 0 (i.e., applies to all packets). You must change this value to any of the above options. Note: A value of 0 applies to all packets, regardless of the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 178 Mediant 800B Gateway & E-SBC Parameter Description defined IP address. Therefore, you must set the parameter to a value other than 0. Start Port Defines the first UDP/TCP port in the range of ports on the device on which the incoming packet is received. From the start-port perspective of the remote IP entity, this is the destination port.
  • Page 179 Action Upon Match Allow Allow Allow Allow Block The firewall rules in the above configuration example do the following:  Rules 1 and 2: Typical firewall rules that allow packets ONLY from specified IP Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 180: Configuring General Security Settings

    Mediant 800B Gateway & E-SBC addresses (e.g., proxy servers). Note that the prefix length is configured.  Rule 3: A more "advanced” firewall rule - bandwidth rule for ICMP, which allows a maximum bandwidth of 40,000 bytes/sec with an additional allowance of 50,000 bytes.

  • Page 181: Intrusion Detection System

    (threshold) before an SNMP trap is sent. Each policy is then applied to a target under attack (SIP interface) and/or source of attack (Proxy Set and/or subnet address). 13.3.1 Enabling IDS The following procedure describes how to enable IDS. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 182: Configuring Ids Policies

    Mediant 800B Gateway & E-SBC  To enable IDS: Open the IDS General Settings page (Setup menu > Signaling & Media tab > Intrusion Detection folder >IDS General Settings). Figure 13-2: Enabling IDS From the 'Intrusion Detection System' drop-down list, select Enable.
  • Page 183 The valid value is a string of up to 100 characters. [IDSPolicy_Description] In the IDS Policies table, select the required IDS Policy row, and then click the IDS Rule link located below the table; the IDS Rule table opens. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 184 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 13-5: IDS Rule Table - Add Dialog Box The figure above shows a configuration example: If 15 malformed SIP messages ('Reason') are received within a period of 30 seconds ('Threshold Window'), a minor alarm is sent ('Minor-Alarm Threshold').
  • Page 185 Critical-Alarm Threshold Defines the threshold that if crossed a critical severity alarm is sent. critical-alrm-thr The valid range is 1 to 1,000,000. A value of 0 or -1 means not [IDSRule_CriticalAlarmThreshold] defined. Deny Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 186: Assigning Ids Policies

    Mediant 800B Gateway & E-SBC Parameter Description Deny Threshold Defines the threshold that if crossed, the device blocks (blacklists) the remote host (attacker). deny-thr The default is -1 (i.e., not configured). [IDSRule_DenyThreshold] Note: The parameter is applicable only if the 'Threshold Scope' parameter is set to IP or IP+Port.
  • Page 187 !10.1.0.0/16 & !10.2.2.2: includes all addresses except those of subnet 10.1.0.0/16 and IP address 10.2.2.2. Note that the exclamation mark "!" appears before each subnet.  10.1.0.0/16 & !10.1.1.1: includes subnet 10.1.0.0/16, except IP address 10.1.1.1. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 188: Viewing Ids Alarms

    Mediant 800B Gateway & E-SBC Parameter Description Policy Assigns an IDS Policy (configured in 'Configuring IDS Policies' on page 182). policy [IDSMatch_Policy] 13.3.4 Viewing IDS Alarms For the IDS feature, the device sends the following SNMP traps:  Traps that notify the detection of malicious attacks: •...
  • Page 189  establish-malicious- signature-db-reject   Requests and responses without a matching flow-no-match-tu Abnormal Flow transaction user (except ACK requests)  flow-no-match-  Requests and responses without a matching transaction transaction (except ACK requests) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 190 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 191: Media

    The device also supports acoustic echo cancellation for SBC calls. These echoes are composed of undesirable acoustical reflections (non-linear) of the received signal (i.e., from the speaker) which find their way from multiple reflections such as walls and windows into Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 192 Mediant 800B Gateway & E-SBC the transmitted signal (i.e., microphone). Therefore, the party at the far end hears his / her echo. The device removes these echoes and sends only the near-end’s desired speech signal to the network (i.e., to the far-end party). The echo is composed of a linear part and a nonlinear part.

  • Page 193: Fax And Modem Capabilities

    VBD (or T.38) is automatically performed and no additional SIP signaling is required. If negotiation fails (i.e., no match is achieved for any of the transport capabilities), fallback to existing logic occurs (according to the Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 194: Fax/Modem Transport Modes

    Mediant 800B Gateway & E-SBC parameter IsFaxUsed). 14.2.2 Fax/Modem Transport Modes The device supports the following transport modes for fax per modem type (V.22/V.23/Bell/V.32/V.34):  T.38 fax relay (see 'T.38 Fax Relay Mode' on page 194)  G.711 Transport: switching to G.711 when fax/modem is detected (see 'G.711 Fax / Modem Transport Mode' on page 196) ...
  • Page 195 The device supports Fax-over-IP (FoIP) transmission using T.38 over RTP, whereby the T.38 payload is encapsulated in the RTP packet, instead of being sent in dedicated T.38 packets (out-of-band). To configure this support, set the coder type to T.38 Over RTP. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 196: Fax / Modem Transport Mode

    RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...

  • Page 197: Fax Fallback

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

  • Page 198: Fax/Modem Bypass Mode

    Mediant 800B Gateway & E-SBC Click Apply. 14.2.2.4 Fax/Modem Bypass Mode In this proprietary mode, when fax or modem signals are detected, the channel automatically switches from the current voice coder to a high bit-rate coder, according to the 'Fax/Modem Bypass Coder Type' parameter (FaxModemBypassCoderType). The channel is also automatically reconfigured with the following fax / modem adaptations: ...

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

    Mediant 800B Gateway & E-SBC Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, BellModemTransportType to 2 (Bypass). Set the ini file parameter, NSEMode parameter to 1 (enables NSE). Set the ini file parameter, NSEPayloadType parameter to 100.

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

    Bypass mechanism for V.34 fax transmission (see 'Bypass Mechanism for V.34 Fax Transmission' on page 202)  T.38 Version 0 relay mode, i.e., fallback to T.38 (see 'Relay Mode for T.30 and V.34 Faxes' on page 203) Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC To configure whether to pass V.34 over T.38 fax relay, or use Bypass over the High Bit Rate coder (e.g. PCM A-Law), use the 'V.34 Fax Transport Type' parameter (V34FaxTransportType). You can use the 'SIP T.38 Version' parameter (SIPT38Version) to configure one of the following: ...

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

    'CNG Detector Mode' (CNGDetectorMode) to Disable (default). 'V.21 Modem Transport Type' to Disable (V21ModemTransportType = 0). 'V.22 Modem Transport Type' to Disable (V22ModemTransportType = 0). 'V.23 Modem Transport Type' to Disable (V23ModemTransportType = 0). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 204 Mediant 800B Gateway & E-SBC 'V.32 Modem Transport Type' to Disable (V32ModemTransportType = 0). 'V.34 Modem Transport Type' to Disable (V34ModemTransportType = 0). 'CED Transfer Mode' to Fax Relay or VBD (CEDTransferMode = 0). (Applicable only to the Gateway application.) Set the ini file parameter, V34FaxTransportType to 1 (i.e., relay).

  • Page 205: Modem Relay

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

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

    Mediant 800B Gateway & E-SBC 14.2.5 Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay The device can negotiate fax relay (T.38) and modem relay (V.150.1) sessions in the same, already established call channel. Fax relay sessions require bypass answering tone (CED) while modem relay requires RFC 2833 answering tone.

  • Page 207: Configuring The Dynamic Jitter Buffer

    BFI packets simultaneously, so that the Jitter Buffer returns to its normal condition. The following procedure describes how to configure the jitter buffer using the Web interface. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 208: Comfort Noise Generation

    Mediant 800B Gateway & E-SBC  To configure jitter buffer using the Web interface: Open the RTP/RTCP Settings page (Setup menu > Signaling & Media menu > Media folder > RTP/RTCP Settings). The relevant parameters are listed under the General group, as shown below:...
  • Page 209 Set the ini file parameter, DTMFTransportType to 2 (i.e., transparent).  Using INFO message according to Korea mode: DTMF digits are sent to the remote side in INFO messages. To enable this mode: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 210: Configuring Rfc 2833 Payload

    Mediant 800B Gateway & E-SBC Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the 'First Tx DTMF Option' parameter to INFO Cisco (FirstTxDTMFOption = Note: DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF).

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

    It can also be used to detect silence, or the beep sound played by an answering machine to indicate the end of the greeting message after which a voice message can be left. For more information on AMD, see 'Answering Machine Detection (AMD)' on Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 212 Mediant 800B Gateway & E-SBC page 217.  Call Progress Tone (CPT): Detects whether a specific tone, defined in the installed CPT file is received from the call. It can be used to detect the beep sound played by an answering machine (as mentioned above), Special Information Tones (SIT) which indicate call failure with a recorded announcement describing the call failure, and the busy, reorder and ring tones.

  • Page 213: Sit Event Detection

    Frequency Frequency Tones (SITs) Duration Duration Duration Name (Hz) (ms) (Hz) (ms) (Hz) (ms) No circuit found 985.2 1428.5 1776.7 Operator intercept 913.8 1370.6 1776.7 Vacant circuit (non 985.2 1370.6 1776.7 registered number) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 214: Detecting Answering Machine Beeps

    Mediant 800B Gateway & E-SBC Special Description First Tone Second Tone Third Tone Information Frequency Frequency Frequency Tones (SITs) Duration Duration Duration Name (Hz) (ms) (Hz) (ms) (Hz) (ms) Reorder (system 913.8 1428.5 1776.7 busy) 913.8 1370.6 1776.7 985.2 1370.6 1776.7...

  • Page 215: Sip Call Flow Examples Of Event Detection And Notification

    INFO sip:sipp@172.22.2.9:5060 SIP/2.0 Via: SIP/2.0/UDP 172.22.168.249;branch=z9hG4bKac482466515 Max-Forwards: 70 From: sut <sip:3000@172.22.168.249:5060>;tag=1c419779142 To: sipp <sip:sipp@172.22.2.9:5060>;tag=1 Call-ID: 1-29753@172.22.2.9 CSeq: 1 INFO Contact: <sip:56700@172.22.168.249> Supported: em,timer,replaces,path,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,I NFO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.7.20A.000.038 Content-Type: application/x-detect Content-Length: 34 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 216 Mediant 800B Gateway & E-SBC Type= PTT SubType= SPEECH-START Upon detection of the end of voice (i.e., end of the greeting message of the answering machine), the device sends the following 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=z9hG4bKac482466515...

  • Page 217: Answering Machine Detection (Amd)

    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 218 Interferences, for example, could include background noises of other people talking, spikes, and car noises. Once you have provided AudioCodes with your database of recordings, AudioCodes compiles it into a loadable file. For a brief description of the file format and for installing the file on the device, see 'AMD Sensitivity File' on page 856.

  • Page 219: Configuring Amd

    Trunk Group. This is achieved by configuring AMD for a specific IP Profile and then assigning the IP Profile to a Trunk Group in the IP-to-Tel Routing table (see Configuring IP-to-Tel Routing Rules on page 534). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC  To configure AMD for all calls: Open the DSP Settings page (Setup menu > Signaling & Media tab > Media folder > DSP Settings): From the 'IPMedia Detectors' drop-down list (EnableDSPIPMDetectors), select Enable to enable AMD.

  • Page 221: Automatic Gain Control (Agc)

    'AGC Target Energy' - Defines the signal energy value (dBm) that the AGC attempts to attain. • 'AGC Minimum Gain' (AGCMinGain) - Defines the minimum gain (in dB) by the AGC when activated. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 222: Configuring Media (Srtp) Security

    Mediant 800B Gateway & E-SBC • 'AGC Maximum Gain' (AGCMaxGain) - Defines the maximum gain (in dB) by the AGC when activated. • 'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force.
  • Page 223 From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP. Configure the other SRTP parameters as required. 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 224: Srtp Using Dtls Protocol

    Mediant 800B Gateway & E-SBC 14.7.1 SRTP using DTLS Protocol For SBC calls, you can configure the device to use the Datagram Transport Layer Security (DTLS) protocol to secure UDP-based media streams (according to RFC 4347 and 6347) for specific SIP entities, using IP Profiles. DTLS allows datagram-based applications to communicate in a way that is designed to prevent eavesdropping, tampering or message forgery.
  • Page 225 > 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 226 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 227: 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 228 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 229 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 230 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 231 [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 232: 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 233: 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 234 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 227.

  • Page 235: Configuring Static Ip Addresses For Dhcp Clients

    'Configuring the DHCP Server' on page 227. 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 236: 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 237: 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 238 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 239 100 SIPRec Redundancy sessions to enable the SRS redundancy feature and support the number of recorded sessions. For more information and for ordering the feature, please contact your AudioCodes sales representative. The device initiates a recording session by sending an INVITE message to the SRS when the recorded call is connected.
  • Page 240 Mediant 800B Gateway & E-SBC • <group id>: Logging Session ID (displayed as [SID:nnnnn] in Syslog), converted from decimal to hex. This number remains the same even if the call is forwarded or transferred. This is important for recorded calls.

  • Page 241: Enabling Sip-Based Media Recording

    The following procedure describes how to enable the SIP-based media Recording feature.  To enable SIP-based media recording: Open the SIP Recording Settings page (Setup menu > Signaling & Media tab > SIP Recording folder > SIP Recording Settings). Figure 15-7: Enabling SIPRec Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 242: Configuring Sip Recording Rules

    Mediant 800B Gateway & E-SBC From the 'SIP Recording Application' drop-down list, select Enable. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Note: SIPRec is a license-dependant feature and is available only if it is included in the License Key installed on the device.
  • Page 243  [0] Both = (Default) Caller can be peer or [SIPRecRouting_Caller] recorded side  [1] Recorded Party (in Gateway, IP-to-Tel call)  [2] Peer Party (in Gateway, Tel-to-IP call) Recording Server Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 244: Configuring Sip User Part For Srs

    Mediant 800B Gateway & E-SBC Parameter Description Recording Server (SRS) IP Group Defines the IP Group of the recording server (SRS). srs-ip-group-name By default, no value is defined.. [SIPRecRouting_SRSIPGroupName] Note:  The parameter is mandatory.  The SIP Interface used for communicating with the SRS is according to the SRD assigned to the SRS IP Group (in the IP Groups table).

  • Page 245: Genesys

    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 246: 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 247 (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 248 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-10: 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 249: 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 251. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 250: 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-12: 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 251: 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 252: 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 1322.  To configure RADIUS-based login authentication: Open the Authentication Server page (Setup menu >...

  • Page 253: 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 254: 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 246, you need to enable and configure RADIUS-based CDR accounting (see 'Configuring RADIUS Accounting' on page 998).

  • Page 255: Enabling The Ldap Service

    Open the LDAP Settings page (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Settings). Figure 15-19: 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 256: 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 257  [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 258: 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 259 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 146. Note: The parameter is mandatory. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 260 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 261  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 262: 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 263: 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 264: 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 258).
  • Page 265 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 266: 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 267 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 268: 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 entries. • The device can save up to six LDAP Attributes in the cache per user (search LDAP key).
  • Page 269 (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 270: 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 271: 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 272 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-31: Base Path (DN) in LDAP Server...
  • Page 273 (where the attribute's value equals the username): Figure 15-32: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-33: User's memberOf Attribute Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 274 Mediant 800B Gateway & E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-34: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...

  • Page 275: 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 276: 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 277 "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 278 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 279 Figure 15-40: 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 266 for the LDAP query process. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 280: 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 258.
  • Page 281 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 282: 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 283: 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 284 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 285: 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 286 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 287 THU, FRI, or SAT).  hh and mm denote the time of day, where hh is the hour (00- 23) and mm the minutes (00-59) For example, SAT:22:00 denotes Saturday at 10 pm. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 288: Assigning Cost Groups To Routing Rules

    Mediant 800B Gateway & E-SBC Parameter Description End Time Defines the day and time of day until when this time band is applicable. For a description of the valid values, see the end-time parameter above. [CostGroupTimebands_EndTime] Connection Cost Defines the call connection cost during the time band. This is added as a fixed charge to the call.
  • Page 289  Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM.  QoS: Call routing based on QoS. For more information, see Configuring QoS-Based Routing by Routing Server on page 297.
  • Page 290 [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.  [5] QoS = QoS-based call routing. For more information, see Configuring QoS-Based Routing by Routing Server on page 297.
  • Page 291 Assigns a TLS Context for connection with the remote host. rest-tls-context By default, no value is defined. [HTTPRemoteServices_TLSCo To configure TLS Contexts, see 'Configuring TLS Certificate Contexts' on ntext] page 113. Note: The parameter is applicable only if the connection is HTTPS. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 292: Configuring Remote Http Hosts

    Mediant 800B Gateway & E-SBC Parameter Description Verify Certificate Enables certificate verification when connection with the host is based on HTTPS. rest-verify-  [0] Disable = (Default) No certificate verification is done. certificates  [1] Enable = The device verifies the authentication of the certificate [HTTPRemoteServices_VerifyC received from the HTTPS peer.
  • Page 293 "closed" (by timeout or by the remote host) and connections are updated accordingly. In addition, the device periodically (every 15 minutes) performs DNS name resolution to ensure that the list of resolved IP Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 294: 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 295 API commands. The following figure provides an example of information exchange between devices and a Routing server for routing calls: Figure 15-46: Example of Call Routing Information Exchange between Devices and Routing Server Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 296 Mediant 800B Gateway & E-SBC The Routing server can also manipulate call data such as calling name, if required. It can also create new IP Groups and associated configuration entities, if necessary for routing. Multiple Routing servers can also be employed, whereby each device in the chain path can use a specific Routing server.

  • Page 297: Configuring Qos-Based Routing By Routing Server

    Open the Web Service Settings page (Setup menu > IP Network tab > Web Services folder > Web Service Settings), and then do the following: From the 'Quality Status' drop-down list (RoutingServerQualityStatus), select Enable to enable QoS-based routing. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 298 Mediant 800B Gateway & E-SBC In the 'Quality Status Rate' field (RoutingServerQualityStatusRate), enter the rate (in sec) at which the device sends QoS reports. Figure 15-50: Enabling QoS-Based Routing via Routing Server Click Apply. Open the Remote Web Services table (see Configuring Remote Web Services on page 297...

  • Page 299: 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 300: 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 301 [0] HTTP (default)  [1] HTTPS [HTTPInterface_Protocol] HTTP Port Defines the local, listening HTTP port. http-port The valid value is 0 to 65534. The default is 0. [HTTPInterface_Port] Note: The parameter is mandatory. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 302: Configuring Http Proxy Services

    Mediant 800B Gateway & E-SBC Parameter Description Security TLS Context Assigns a TLS Context for the connection with the HTTP Proxy service. tls-context By default, the default TLS Context (Index 0) is assigned. [HTTPInterface_TLSContext] To configure TLS Contexts, see 'Configuring TLS Certificate Contexts' on page 113.

  • Page 303: Configuring Http Proxy Hosts

    You can configure up to 50 HTTP Proxy hosts; up to 5 HTTP Proxy hosts per HTTP Proxy Service. The following procedure describes how to configure HTTP Remote hosts through the Web interface. You can also configure it through ini file (HTTPProxyHost) or CLI (configure network > http-proxy http-proxy-host). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 304 Mediant 800B Gateway & E-SBC  To configure an HTTP Proxy Host: 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;...

  • Page 305: 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-55: EMS Services Table - Add Dialog Box Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 306 Mediant 800B Gateway & E-SBC Configure an EMS Service according to the parameters described in the table below. 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.

  • Page 307: 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 308: Microsoft Skype For Business And E9-1-1

    Mediant 800B Gateway & E-SBC The VoIP user dials 9-1-1. AudioCodes' ELIN device 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 309 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 310: 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 311: 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 312: 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 313 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 314: 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 315: 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 316: 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 317: 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 318: 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-60: 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 319 ELIN numbers: Figure 15-62: 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 320: 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 321 Contact: <sip:john.doe@10.33.221.57:5061;transport=tls> Event: presence Expires: 0 User-Agent: sur1-vg1.ecarecenters.net/v.7.20A.001.080 SIP-If-Match: 2545777538-1-1 Content-Length: 0 The following figure shows a basic illustration of the device's integration into Microsoft Skype for Business Presence feature for third-party endpoints. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 322: Configuring Skype For Business Server For Presence

    Mediant 800B Gateway & E-SBC 15.9.1 Configuring Skype for Business Server for Presence On the Skype for Business Server side, you need to define the device in the Skype for Business Topology as a Trusted Application. Note: • Detailed configuration of Skype for Business Server is beyond the scope of this document.

  • Page 323: Configuring The Device For Skype For Business Presence

    Configure a Proxy Set to define the address of the Skype for Business Server (see Configuring Proxy Sets on page 380). Make sure you configure the following: • 'TLS Context Name': Assign the TLS Context that you configured in Step 2 (above). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 324 Mediant 800B Gateway & E-SBC • 'Proxy Address': Configure the address (FQDN or IP address). • 'Transport Type': TLS Configure an IP Group to represent the Skype for Business Server (see Configuring IP Groups on page 365). Make sure that you assign it with the Proxy Set that you configured in Step 3 (above).

  • Page 325: 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 326: 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 327: 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 328  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 325.
  • Page 329 [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 330 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 331 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 332: 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 333 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 334 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 335: 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 728) 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 336 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 337 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 338 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 339: 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 340 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 341 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 'Configuring RTP Base UDP Port' on page 210. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 342: Configuring Remote Media Subnets

    Mediant 800B Gateway & E-SBC Parameter Description 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 343 Open the Media Realms table (see 'Configuring Media Realms' on page 339). 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 344 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 345: 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 339). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 346 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 347: Configuring Srds

    (Layer 5) consisting of groups of SIP users and servers. The SRD is associated with all the configuration entities (e.g., SIP Interfaces and IP Groups) required for routing calls within the network. Typically, only a single SRD is required (recommended) for most Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 348 Mediant 800B Gateway & E-SBC deployments. Multiple SRDs are only required for multi-tenant deployments, where the physical device is "split" into multiple logical devices. For more information on multi-tenant architecture, see 'Multiple SRDs for Multi-tenant Deployments' on page 353. As the device is shipped with a default SRD ("DefaultSRD" at Index 0), if your deployment requires only one SRD, you can use the default SRD instead of creating a new one.
  • Page 349 Open the SRDs table (Setup menu > Signaling & Media tab > Core Entities folder > SRDs). Click New; the following dialog box appears: Figure 17-7: SRDs Table - Add Dialog Box Configure an SRD according to the parameters described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 350 Mediant 800B Gateway & E-SBC Click Apply. Table 17-4: SRDs table Parameter Descriptions Parameter Description General Index Defines an index for the new table row. [SRD_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.
  • Page 351 IP address. The verification is performed before any of the device's call handling processes (i.e., Classification, Manipulation and Routing). Note:  The parameter is applicable only to calls belonging to User-type IP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 352 Mediant 800B Gateway & E-SBC Parameter Description Groups.  The feature is not applicable to REGISTER requests.  The option, Accept Registered Users from Same Source [2] does not apply to registration refreshes. These requests are accepted even if the source address is different to that registered with the device.

  • Page 353: Filtering Tables In Web Interface By Srd

    CPU, memory and interface allocations should be optimized so as not to waste resources for small-sized tenants on the one hand, and not to allocate too many instances for a single Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 354 Mediant 800B Gateway & E-SBC tenant/customer on the other. For example, it would be a waste to allocate a capacity of 100 concurrent sessions to a small tenant for which 10 concurrent sessions suffice. In a multi-tenant deployment, each tenant is represented by a dedicated SRD. The different Layer-3 networks (e.g., LAN IP-PBX users, WAN SIP Trunk, and WAN far-end users) of...

  • Page 355: Cloning Srds

    <unique clone ID>_<original SRD index>_CopyOf_<name, or index if no name, of original SRD>. For example, if you clone SRD "SIP-Trunk" at index 2, the new SRD clone is assigned the name, "36454371_2_CopyOf_SIP-Trunk". Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC The SRD clone has identical settings as the original SRD. In addition, all configuration entities associated with the original SRD are also cloned and these clones are associated with the SRD clone. The naming convention of these entities is the same as the SRD clone (see above) and all have the same unique clone ID ("36454371"...

  • Page 357: Automatic Configuration Based On Srd

     SBC application: • IP-to-IP Routing rules for specifying the destination SIP Interface to where you want to route the call. For more information, see Configuring SBC IP-to-IP Routing Rules on page 709. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 358 Mediant 800B Gateway & E-SBC • Classification rules for specifying the SIP Interface as a matching characteristic of the incoming call. This is especially useful for the single SRD-configuration topology, where each SIP Interface represents a Layer-3 network (SIP entity).
  • Page 359 The port must be different from ports configured for RTP traffic (i.e., ports configured for Media Realms). For example, if the RTP port range is 6000 to 6999, the SIP port can either be less than 6000 or greater than 6999. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 360 Mediant 800B Gateway & E-SBC Parameter Description  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). TCP Port Defines the device's listening port for SIP signaling traffic over TCP.
  • Page 361 SIP scanners to detect ports used by SIP devices. These scanners scan devices by sending UDP packets containing a SIP request to a range of specified IP addresses, listing those that return a valid SIP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 362 Mediant 800B Gateway & E-SBC Parameter Description response. Once the scanner finds a device that supports SIP, it extracts information from the response and identifies the type of device (IP address and name) and can execute DoS attacks. A way to defend the device against such attacks is to not send a SIP reject response to these unclassified "calls"...
  • Page 363  [0] Accept All = Accepts requests from registered and unregistered users.  [1] Accept Registered Users = Accepts requests only from users registered with the device. Requests from users not registered are Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 364 Mediant 800B Gateway & E-SBC Parameter Description rejected.  [2] Accept Registered Users from Same Source = Accepts requests only from registered users whose source address is the same as that registered with the device (during the REGISTER message process). All other requests are rejected. The device verifies whether the IP address and port are different only if the transport protocol is UDP;...

  • Page 365: Configuring Ip Groups

    (e.g., MOS) can be applied per IP Group. For example, if MOS is considered poor, calls belonging to this IP Group can be rejected. To configure Quality of Experience Profiles, see 'Configuring Quality of Experience Profiles' on page 327. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 366 Mediant 800B Gateway & E-SBC  Bandwidth Profile: Bandwidth utilization thresholds can be applied per IP Group. For example, if bandwidth thresholds are crossed, the device can reject any new calls on this IP Group. To configure Bandwidth Profiles, see 'Configuring Bandwidth Profiles' on page 332.
  • Page 367 NAT. In this case, the device must be defined with a global IP address.  [2] Gateway = (Applicable only to the SBC application.) In scenarios where the device receives requests to and from a gateway Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 368 Mediant 800B Gateway & E-SBC Parameter Description representing multiple users. This IP Group type is necessary for any of the following scenarios:  The IP Group cannot be defined as a Server-type since its address is initially unknown and therefore, a Proxy Set cannot be configured for it.
  • Page 369 (Read-only) Indicates whether the IP Group was created by a third-party routing server: [IPGroup_CreatedByRouti  ngServer] [0] No  [1] Yes For more information on the third-party routing server feature, see Centralized Third-Party Routing Server on page 294. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 370 Mediant 800B Gateway & E-SBC Parameter Description Used By Routing Server Enables the IP Group to be used by a third-party routing server for call routing decisions. used-by-routing-server  [0] Not Used (default) [IPGroup_UsedByRouting  [1] Used Server] For more information on the third-party routing server feature, see Centralized Third-Party Routing Server on page 294.
  • Page 371  [2] Sequential Available Only = Sequentially sends the INVITE only to available contacts (i.e., not busy). If there is no answer from the first Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 372 Mediant 800B Gateway & E-SBC Parameter Description available contact, it sends the INVITE to the second contact, and so on until a contact answers. If no contact answers, the call fails or is routed to an alternative destination, if configured.
  • Page 373  [0] From  [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 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 374 Mediant 800B Gateway & E-SBC Parameter Description  [9] P-Called-Party-ID  [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 375 Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the inbound leg. inbound-mesg- By default, no value is defined. manipulation-set To configure Message Manipulation rules, see Configuring SIP Message Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 376 Mediant 800B Gateway & E-SBC Parameter Description [IPGroup_InboundManSet] Manipulation on page 413. Note:  The parameter is applicable only to the SBC application.  The IPGroup_SIPGroupName parameter overrides inbound message manipulation rules (assigned to the IPGroup_InboundManSet parameter) that manipulate the host name in Request-URI, To, and/or From SIP headers.
  • Page 377 In the case of failed REGISTER refresh requests from users that are already bound to a registrar, no "hot-swap" occurs for that request; only for subsequent refresh requests. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 378 Mediant 800B Gateway & E-SBC Parameter Description  When using the User Info table (see SBC User Information for SBC User Database on page 852), registrar "stickiness" is supported only when the user initiates the REGISTER request. Therefore, you must configure the 'Registration Mode' parameter of the IP Group (User- type) to which the user belongs, to User Initiates Registration.
  • Page 379 Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway). GW Group Registered (Read-only field) Displays whether the IP Group entity (gateway) is Status registered with the device ("Registered" or "Not Registered"). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 380: Configuring Proxy Sets

    Mediant 800B Gateway & E-SBC Parameter Description Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway). 17.5 Configuring Proxy Sets The Proxy Sets table lets you configure up to 102 Proxy Sets. A Proxy Set defines the address and transport type (e.g., UDP or TCP) of a SIP server (e.g., SIP proxy and SIP...
  • Page 381 Click New; the following dialog box appears: Figure 17-11: Proxy Address Table - Add Dialog Box Configure the address of the Proxy Set according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 382 Mediant 800B Gateway & E-SBC Table 17-7: Proxy Sets Table and Proxy Address Table Parameter Description Parameter Description Assigns an SRD to the Proxy Set. voip-network proxy-set > srd-id Note:  [ProxySet_SRDName] The parameter is mandatory and must be configured first before you can configure the other parameters in the table.
  • Page 383 UsePingPongKeepAlive parameter.  If you enable this Proxy Keep-Alive feature, the device can operate with multiple proxy servers (addresses) for redundancy and load balancing (see the 'Proxy Load Balancing Method' Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 384 Mediant 800B Gateway & E-SBC Parameter Description parameter). Proxy Keep-Alive Time Defines the interval (in seconds) between keep-alive messages sent by the device when the Proxy Keep-Alive feature is enabled (see the proxy-keep-alive-time 'Proxy Keep-Alive' parameter in this table). [ProxySet_ProxyKeepAliveTim The valid range is 5 to 2,000,000.
  • Page 385 IP address entries in the list occurs, all load statistics are erased and balancing starts over again.  [2] Random Weights = The outgoing requests are not distributed equally among the Proxies. The weights are received from the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 386 Mediant 800B Gateway & E-SBC Parameter Description DNS server, using SRV records. The device sends the requests in such a fashion that each proxy receives a percentage of the requests according to its' assigned weight. A single FQDN should be configured as a proxy IP address. Random Weights Load Balancing is not used in the following scenarios: ...
  • Page 387 Defines an index number for the new table row. proxy-ip-index Note: Each row must be configured with a unique index. [ProxyIp_ProxyIpIndex] Proxy Address Defines the address of the proxy. Up to 10 addresses can be configured per Proxy Set. The address Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 388 Mediant 800B Gateway & E-SBC Parameter Description proxy-address can be defined as an IP address in dotted-decimal notation (e.g., 201.10.8.1) or FQDN. You can also specify the port using the [ProxyIp_IpAddress] following format:  IPv4 address: <IP address>:<port> (e.g., 201.10.8.1:5060) ...

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

    Click the demarcation name; the name becomes editable in a text box, as shown in the example below: Type a name as desired, and then click anywhere outside of the text box to apply the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 390 Mediant 800B Gateway & E-SBC Item # Description name. You can use demarcation to visually separate your voice network to provide a clearer understanding of your topology. This is especially useful for IP Groups, SIP Interfaces, and Media Realms, where you can display them on the top or bottom border of the Topology view (as shown in the figure below for callouts #1 and #2, respectively).
  • Page 391 The Media Realms table opens with a new dialog box for adding a Media Realm to the next available index row. Configure the Media Realm as desired, and then click Apply; the Media Realms table closes and you are returned to the Topology View, displaying the new Media Realm. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 392 Mediant 800B Gateway & E-SBC Item # Description For more information on configuring Media Realms, see 'Configuring Media Realms' on page 339. Configured IP Groups. Each IP Group is displayed using the following "IP Group [Server]" or "IP Group [User]" titled icon (depending on whether it's a Server- or User-type IP Group...
  • Page 393 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 517. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 394 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 395: 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 396 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 397 INVITE messages sent to the "serving" IP Group. If the device receives a SIP 401 (Unauthorized) in response to a sent INVITE, the device checks for a matching "serving" and "served" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 398 Mediant 800B Gateway & E-SBC Parameter Description entry in the table. If a matching row exists, the device authenticates the INVITE by providing the corresponding MD5 authentication username and password to the "serving" IP Group.  [1] Regular = Regular registration process. For more information, see 'Regular Registration Mode' on page 400.
  • Page 399 Note: The parameter is applicable only if you have enabled the Registrar Stickiness feature (in this table):  'Register' parameter to Regular or GIN.  'Registrar Stickiness' parameter to Enable. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 400: Regular Registration Mode

    Mediant 800B Gateway & E-SBC Parameter Description Reg Event Package Subscription Enables the device to subscribe to the registration event package service (as defined in RFC 3680) with the reg-event-package-subscription registrar server (Serving IP Group) to which the Account [Account_RegEventPackageSubscription] is successfully registered and binded, when the Registrar Stickiness feature is enabled.
  • Page 401 'gin'. The Supported header contains the token 'path' and the URI in the Contact header contains the parameter 'bnc' without a user part: Contact: <sip:198.51.100.3;bnc>; The figure below illustrates the GIN registration process: The figure below illustrates an incoming call using GIN: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 402: Registrar Stickiness

    Mediant 800B Gateway & E-SBC 18.1.3 Registrar Stickiness You can enable the Registrar Stickiness feature per Account. Registrar Stickiness binds an Account to one of the IP addresses (configured or DNS-resolved) in the Proxy Set associated with the Serving IP Group. Once an Account registers successfully to one of the IP addresses (i.e., SIP registrar server) in the Proxy Set, the device routes all subsequent...

  • Page 403: Sip Message Authentication Example

    • The password from the ini file is "AudioCodes". • The equation to be evaluated is "122:audiocodes.com:AudioCodes". According to the RFC, this part is called A1. • The MD5 algorithm is run on this equation and stored for future usage.

  • Page 404: Configuring Call Setup Rules

    At this time, a new REGISTER request is issued with the following response: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c23940 To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 Server: Audiocodes-Sip-Gateway/Mediant 800B Gateway and E- SBC/v.7.20A.000.038 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”,...
  • Page 405 If assigned to an IP Group, the device processes the Call Setup rule for the classified source IP Group immediately before the routing process. If assigned to a routing rule only, the device first locates a matching routing rule for the incoming call, processes the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 406 Mediant 800B Gateway & E-SBC assigned Call Setup Rules Set ID, and then routes the call according to the destination configured for the routing rule. The device uses the routing rule to route the call, depending on the result of the Call Setup Rules Set ID: ...
  • Page 407 Server Groups on page 256.  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 751. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 408 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 409 [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 410: 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 411 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 412 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 413: Sip Message Manipulation

    These elements can include SIP headers, SIP header parameters, and SDP body fields. The SIP message manipulation feature supports the following:  Manipulation on SIP message type (Method, Request/Response, and Response type) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 414 Mediant 800B Gateway & E-SBC  Addition of new SIP headers  Removal of SIP headers ("black list")  Modification of SIP header components such as values, header values (e.g., URI value of the P-Asserted-Identity header can be copied to the From header), call's parameter values ...
  • Page 415 User's Manual 19. SIP Message Manipulation The figure below illustrates a SIP message manipulation example: Figure 19-2: SIP Header Manipulation Example Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 416 Mediant 800B Gateway & E-SBC Note: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide. • For the SBC application, Inbound message manipulation is done only after the Classification, inbound/outbound number manipulations, and routing processes.
  • Page 417 Index 3. A configuration example is shown in the beginning of this section. The option allows you to use the same condition for multiple manipulation rules. Note:  When configured to Use Previous Condition, the 'Message Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 418 Mediant 800B Gateway & E-SBC Parameter Description Type' and 'Condition' parameters are not applicable and if configured are ignored.  When multiple manipulation rules apply to the same header, the next rule applies to the resultant string of the previous rule.

  • Page 419: Configuring Message Condition Rules

    Web interface. You can also configure it through ini file (ConditionTable) or CLI (configure voip > sbc routing condition-table).  To configure a Message Condition rule: Open the Message Conditions table (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Conditions). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 420: Configuring Sip Message Policy Rules

    Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 19-5: Message Conditions Table - Add Dialog Box Configure a Message Condition rule according to the parameters described in the table below. Click Apply. An example of configured Message Condition rules is shown in the figure below: Figure 19-6: Example of Configured SIP Message Conditions ...
  • Page 421 You can also configure it through ini file (MessagePolicy) or CLI (configure voip > message message-policy).  To configure SIP Message Policy rules: Open the Message Policies table (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Policies). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 422 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 19-7: Message Policies Table - Add Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Apply. Table 19-3: Message Policies Table Parameter Descriptions...
  • Page 423 SIP Body Blacklist-Whitelist Policy Body List Defines the SIP body type (i.e., value of the Content- Type header) to blacklist or whitelist. For example, body-list application/sdp. [MessagePolicy_BodyList] The values of the parameter are case-sensitive. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 424: Configuring Pre-Parsing Manipulation Rules

    Mediant 800B Gateway & E-SBC Parameter Description Body List Type Defines the policy (blacklist or whitelist) for the SIP body specified in the 'Body List' parameter (above). body-list-type  [0] Policy Blacklist =The specified SIP body is [MessagePolicy_BodyListType] rejected. ...
  • Page 425 Manipulation Rules table appears. Click New; the following dialog box appears: Figure 19-9: Pre-Parsing Manipulation Rules Table - Add Dialog Box Configure a rule according to the parameters described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 426 Mediant 800B Gateway & E-SBC Click New, and then save your settings to flash memory. Pre-Parsing Manipulation Rules Table Parameter Descriptions Parameter Description Match Index Defines an index number for the new table row. [PreParsingManipulationRules_R Note: Each row must be configured with a unique index.

  • Page 427: Coders And Profiles

    In the IP Profile associated with the SIP entity (see Configuring IP Profiles on page 436): • 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 428 For supported audio coders, see 'Supported Audio Coders' on page 429. • 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 429: Supported Audio Coders

    Note: The AMR payload type can be configured globally using the AmrOctetAlignedEnable parameter. However, the Coder Group configuration overrides the global parameter. 20.1.1 Supported Audio Coders The table below lists the coders supported by the device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 430 Mediant 800B Gateway & E-SBC Table 20-2: Supported Audio Coders Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression [1] 10, [2] 20, [3] 30, [4] 40, [5] 50, [6] 60, [8] 80, [9] 90, [10] 100, [12] 120 ...

  • Page 431: Configuring Various Codec Attributes

     To configure codec attributes: Open the Coder Settings page (Setup menu > Signaling & Media tab > Coders & Profiles folder > Coder Settings). Configure the following parameters: • AMR coder: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 432: Configuring Allowed Audio Coder Groups

    Mediant 800B Gateway & E-SBC ♦ 'AMR Payload Format' (AmrOctetAlignedEnable): Defines the AMR payload format type: • SILK coder (Skype's default audio codec): ♦ 'Silk Tx Inband FEC': Enables forward error correction (FEC) for the SILK coder. ♦ 'Silk Max Average Bit Rate': Defines the maximum average bit rate for the SILK coder.
  • Page 433 Click New; the following dialog box appears: Figure 20-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. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 434 Mediant 800B Gateway & E-SBC Click Apply. Select the new row that you configured, and then click the Allowed Audio Coders link located below the table; the Allowed Audio Coders table opens. Click New; the following dialog box appears: Figure 20-5: Allowed Audio Coders Table - Add Dialog Box Configure coders for the Allowed Audio Coders Group according to the parameters described in the table below.

  • Page 435: Configuring Allowed Video Coder Groups

    Click New; the following dialog box appears: Figure 20-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. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 436: Configuring Ip Profiles

    Mediant 800B Gateway & E-SBC Click Apply. Select the new row that you configured, and then click the Allowed Video Coders link located below the table; the Allowed Video Coders table opens. Click New; the following dialog box appears: Figure 20-7: Allowed Video Coders Table - Add Dialog Box Configure coders for the Allowed Video Coders Group according to the parameters described in the table below.
  • Page 437 You can also configure it through ini file (IPProfile) or CLI (configure voip > coders-and- profiles ip-profile).  To configure an IP Profile: Open the IP Profiles table (Setup menu > Signaling & Media tab > Coders & Profiles folder > IP Profiles). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 438 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 20-8: IP Profiles Table - Add Dialog Box Configure an IP Profile according to the parameters described in the table below. Click Apply. Table 20-5: IP Profiles Table Parameter Descriptions...
  • Page 439 For example, assume that the device receives an INVITE containing the following two crypto lines in SDP: 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 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 440 Mediant 800B Gateway & E-SBC Parameter Description 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 441 Note: If you configure the parameter to Yes, the following IP Profile parameters must be configured as follows:  IpProfile_EnableSymmetricMKI configured to Enable [1].  IpProfile_MKISize configured to 0.  IpProfile_SBCEnforceMKISize configured to Enforce [1]. SBC Early Media Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 442 Mediant 800B Gateway & E-SBC Parameter Description 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.  [1] Supported = (Default) Early media is supported.
  • Page 443 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 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 444 Mediant 800B Gateway & E-SBC Parameter Description [IPProfile_SBCGenerateRTP incoming packets before sending RTP (e.g., early media used for ringback tone or IVR) during media negotiation.  [0] None (Default) = Silence packets are not generated.  [1] Until RTP Detected = The device generates silence RTP packets to the SIP entity upon receipt of a SIP response (183 with SDP) from the SIP entity.
  • Page 445 Profile "IP-PBX-1" and IP Profile "IP-PBX-2". 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 670. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 446 Mediant 800B Gateway & E-SBC Parameter Description Note: If you enable direct media for the IP Profile, make sure that your Media Realm provides sufficient ports, as media may traverse the device for mid-call services (e.g., call transfer). RFC 2833 Mode Defines the handling of RFC 2833 SDP offer-answer negotiation for the SIP entity associated with the IP Profile.
  • Page 447 SIP re-INVITE (or UPDATE) from the SIP entity to where the SIP INFO is being sent (and keep sending the DTMF digits using the RFC 2833 method). This is done using AudioCodes proprietary SIP header X-AC-Action and a Message Manipulation rule (inbound)
  • Page 448 Mediant 800B Gateway & E-SBC Parameter Description recommended that the settings of the switched IP Profile are identical (except for the 'Send Multiple DTMF Methods' parameter) to the initial IP Profile in order to avoid any possible call handling errors.
  • Page 449  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. ICE Mode Enables Interactive Connectivity Establishment (ICE) Lite for the SIP entity associated with the IP Profile. ICE is a methodology for NAT...
  • Page 450 Mediant 800B Gateway & E-SBC Parameter Description a peer with a public IP address and port that can be used to connect to a remote peer.  [0] Disable (default)  [1] Lite For more information on ICE Lite, see ICE Lite.
  • Page 451 VoIPerfect on page 788). Voice Quality Enhancement Enables the device to detect speech and network quality (packet loss and bandwidth reduction) and triggers the device to overcome adverse sbc-voice-quality- conditions to ensure high call quality. enhancement Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 452 Mediant 800B Gateway & E-SBC Parameter Description  [IpProfile_SBCVoiceQualityE [0] Disable (default) nhancement]  [1] Enable Note: The parameter is applicable only to the VoIPerfect feature (see VoIPerfect on page 788). Max Opus Bandwidth Defines the VoIPerfect mode of operation, which is based on the Opus coder.
  • Page 453 [1] Add = History-Info header is converted to a Diversion header.  [2] Remove = Removes the Diversion header and the conversion to the History-Info header depends on the SBCHistoryInfoMode parameter. For more information on interworking of the History-Info and Diversion Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 454 Mediant 800B Gateway & E-SBC Parameter Description headers, see Interworking SIP Diversion and History-Info Headers on page 684. Note: If the Diversion header is used, you can specify the URI type (e.g., "tel:") to use in the header, using the SBCDiversionUriType parameter.
  • Page 455 SIP request and adds itself as the top-most listed Via header in the outgoing message sent to the SIP entity. Keep Incoming Routing Enables interworking SIP Record-Route headers between SIP entities. Headers The parameter defines the device's handling of Record-Route headers Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 456 Mediant 800B Gateway & E-SBC Parameter Description sbc-keep-routing-headers for request/response messages sent to the the SIP entity associated with the IP Profile. [IpProfile_SBCKeepRouting  Headers] [-1] According to Operation Mode = (Default) Depends on the setting of the 'Operation Mode' in the IP Group or SRDs table: ...
  • Page 457 NAT TCP Registration Time Defines the registration time (in seconds) that the device includes in register responses, in response to SIP REGISTER requests from sbc-usr-tcp-nat-reg-time users belonging to the SIP entity associated with the IP Profile. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 458 Mediant 800B Gateway & E-SBC Parameter Description [IpProfile_SBCUserBehindTc The parameter applies only to users that are located behind NAT and pNATRegistrationTime] whose communication type is TCP. The registration time is inserted in the Expires header in the outgoing response sent to the user.
  • Page 459 The 'Remote Early Media RTP Behavior parameter is set to Delayed (used in the Skype for Business environment), and transfer target sends a 183 Session Progress with SDP offer. If early media from the transfer target has already been detected, the Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 460 Mediant 800B Gateway & E-SBC Parameter Description transferee receives RTP stream from the transfer target. If it has not been detected, the device generates a ringback tone to the transferee and stops the tone generation once RTP has been detected from the transfer target.
  • Page 461 0.0.0.0, not supported, or transparent (when the incoming SDP is 'sendonly'). SBC Fax Fax Coders Group Assigns a Coder Group which defines the supported fax coders for fax Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 462 Mediant 800B Gateway & E-SBC Parameter Description sbc-fax-coders-group-name negotiation for the SIP entity associated with the IP Profile. To configure Coder Groups, see Configuring Coder Groups on page 427. [IpProfile_SBCFaxCodersGr oupName] Note:  The parameter is applicable only if you set the IpProfile_SBCFaxBehavior parameter to a value other than [0].
  • Page 463  [2] Reroute = (SBC application only) The device ends the call and searches the IP-to-IP Routing table for a matching rule and if found, generates a new INVITE to the corresponding destination Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 464 Mediant 800B Gateway & E-SBC Parameter Description (i.e., alternative routing). You can configure a routing rule whose matching characteristics is explicitly for calls with broken RTP connections. This is done using the Call Trigger parameter, as described in Configuring SBC IP-to-IP Routing Rules on page 709.
  • Page 465 ISDN: Sending a 183 response depends on the ISDN PI. It is sent only if PI is set to 1 or 8 in the received Proceeding or Alerting messages. Sending 183 response also depends on the ReleaseIP2ISDNCallOnProgressWithCause parameter, Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 466 Mediant 800B Gateway & E-SBC Parameter Description which must be set to any value other than 2.  See also the IgnoreAlertAfterEarlyMedia parameter. The parameter allows, for example, to interwork Alert with PI to SIP 183 with SDP instead of 180 with SDP.
  • Page 467 This is used to cut-through the voice path before the remote party answers the call. This allows the originating party to listen to network call progress tones such as ringback tone or other Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 468 Mediant 800B Gateway & E-SBC Parameter Description network announcements.  Digital: For IP-to-Tel calls, if the parameter EnableEarlyMedia is set to 1, the device sends 180 Ringing with SDP in response to an ISDN Alerting or it sends a 183 Session Progress...
  • Page 469  [3] INFO (Cisco) = Sends DTMF digits according to the Cisco format.  [4] RFC 2833 = (Default) The device:  negotiates RFC 2833 payload type using local and remote SDPs. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 470 Mediant 800B Gateway & E-SBC Parameter Description  sends DTMF packets using RFC 2833 payload type according to the payload type in the received SDP.  expects to receive RFC 2833 packets with the same payload type as configured by the parameter RFC2833PayloadType.
  • Page 471 [3] Events Only = Transparent with Events. For a detailed description of the parameter per modem type, see the relevant global parameter (listed above). NSE Mode Enables Cisco's compatible fax and modem bypass mode, Named Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 472 [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 473: Configuring Tel Profile

    Trunk Group table (see Configuring Trunk Groups on page 517)). 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). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 474 Mediant 800B Gateway & E-SBC  To configure a Tel Profile: Open the Tel Profiles table (Setup menu > Signaling & Media tab > Coders & Profiles folder > Tel Profiles). Click New; the following dialog box appears: Figure 20-9: Tel Profiles Table - Add Dialog Box Configure a Tel Profile according to the parameters described in the table below.
  • Page 475 1.5 seconds ('p') and plays the rest of the number (100) as DTMF digits. Additional examples: 1664wpp102, 66644ppp503, and 7774w100pp200. Note:  For the parameter to take effect, a device reset is required. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 476 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter  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 477 The valid range is 0 to 254. The default is 0 seconds for analog interfaces and 10 seconds for digital interfaces. Note that the Web interface denotes the default value (for analog and digital interfaces) as a string value of "255". Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 478 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter Note:  The selected busy or reorder tone is according to the SIP release cause code received from IP.  The parameter is applicable to CAS.  The parameter is also applicable to ISDN when the PlayBusyTone2ISDN parameter is set to 2.
  • Page 479 Disconnect Pulse' after the call is released from the IP side. Note:  The parameter is applicable to FXS and FXO interfaces.  The current disconnect duration is configured by the CurrentDisconnectDuration parameter.  The current disconnect threshold (FXO only) is configured Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 480 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter by the CurrentDisconnectDefaultThreshold parameter.  The frequency at which the analog line voltage is sampled is configured by the TimeToSampleAnalogLineVoltage parameter.  The corresponding global parameter is EnableCurrentDisconnect. DID Wink...
  • Page 481 The valid range is 0 to 63. The default is 40. [TelProfile_SigIPDiffServ] Note:  For more information on DiffServ, see 'Configuring Class-of- Service QoS' on page 166.  The corresponding global parameter is Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 482 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter PremiumServiceClassControlDiffServ. Enable Early Media Enables the Early Media feature, which sends media (e.g., ringing) before the call is established. early-media  [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 call is answered.
  • Page 483 The default is 300. [TelProfile_JitterBufMaxDelay] Dynamic Jitter Buffer Optimization Factor Defines the Dynamic Jitter Buffer frame error/delay optimization factor. jitter-buffer-optimization-factor The valid range is 0 to 12. The default factor is 10. [TelProfile_JitterBufOptFactor] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 484 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter For more information on Jitter Buffer, see 'Configuring the Dynamic Jitter Buffer' on page 207. Note:  For data (fax and modem) calls, configure the parameter to  The corresponding global parameter is DJBufOptFactor.
  • Page 485 IP. For the analog side, it defines the following: [TelProfile_FlashHookPeriod]  FXS interfaces:  Maximum hook-flash detection period. A longer signal is considered an off-hook or on-hook event.  Hook-flash generation period upon detection of a SIP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 486 Mediant 800B Gateway & E-SBC Tel Profile Parameter Global Parameter INFO message containing a hook-flash signal.  FXO interfaces: Hook-flash generation period. The valid range is 25 to 3,000. The default is 700. Note:  The parameter is applicable to FXS and FXO interfaces ...

  • Page 487: Gateway Application

    Part V Gateway Application...

  • Page 489: 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. 21.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 490 Mediant 800B Gateway & E-SBC  IP-to-Tel Call: Figure 21-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-10632...
  • Page 491 User's Manual 21. Introduction  Tel-to-IP Call: Figure 21-2: Tel-to-IP Call Processing Flowchart Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 492 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 493: 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 494 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 495: Tdm And Timing

    22.2.1.1 Recovering Clock from PSTN Line Interface This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line interface. For a full description of the clock parameters, see 'PSTN Parameters' on page 1214. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 496: Configuring Internal Clock As Clock Source

    Mediant 800B Gateway & E-SBC  To configure synchronization based on clock from PSTN line: Open the TDM Bus Settings page (Setup menu > Signaling & Media tab > Media folder > TDM Bus Settings), and then do the following:...

  • Page 497: 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 498 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 499: Configuring Digital Gateway Parameters

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

  • Page 500: Tunneling Applications

    Mediant 800B Gateway & E-SBC 22.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 22.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 501 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 502 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 503: Dsp Pattern Detector

    (commonly called Ringdown circuits). No dialing is necessary; the user simply picks up the handset or pushes a button and a dedicated line is seized. Thus, many turrets have multiple handsets Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 504 Mediant 800B Gateway & E-SBC and multi-channel speaker units, allowing immediate connection with multiple parties (e.g., 30 channels). These channels remain constantly open throughout the trading day. Today, private wire services are evolving from digital TDM architectures to IP-based architectures. The device can be used for interworking between these two architectures, where you have the PSTN switch (PBX) using the E1/T1 CAS protocol on one side, and a SIP-based private wire (turret system) trunk on the other side.
  • Page 505 <xsd:sequence> <xsd:choice> <xsd:element ref="ringDown" /> <xsd:element ref="hookSwitch" /> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xsd:choice> </xsd:sequence> <xsd:anyAttribute namespace="##other" processContents="lax" /> </xsd:complexType> <xsd:element name="pwSignal" type="pwSignallingType"/> <!-- ringDown --> <xsd:complexType name="ringDownType"> <xsd:sequence> <xsd:any namespace="##other" minOccurs="0" Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 506 Mediant 800B Gateway & E-SBC maxOccurs="unbounded" processContents="lax" /> </xsd:sequence> <xsd:attribute name="signal" type="ringDownSignalType" use="required"/> <xsd:anyAttribute namespace="##other" processContents="lax" /> </xsd:complexType> <xsd:element name="ringDown" type="ringDownType"/> <!-- hookSwitch --> <xsd:complexType name="hookSwitchType"> <xsd:sequence> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xsd:sequence> <xsd:attribute name="signal" type="hookSwitchSignalType" use="required"/> <xsd:anyAttribute namespace="##other" processContents="lax" />...
  • Page 507 E1 or T1 CAS Trunk. Make sure that you select the CAS table file that you loaded in the previous step, in the 'CAS Table per Trunk' field: Figure 22-9: Selecting CAS File for Trunk - Private Wire Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 508: Qsig Tunneling

    Mediant 800B Gateway & E-SBC In the Trunk Group table (see Configuring Trunk Groups on page 517), configure the Trunk Group ID for the E1/T1 CAS Trunk, as shown in the following example: Figure 22-10: Configuring Trunk Group for Private Wire...

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

    The device supports up to 12 NFAS groups. Each group can comprise up to 10 T1 trunks and each group must contain different T1 trunks. Each T1 trunk is called an "NFAS member". The T1 trunk whose D-channel is used for signaling is called the "Primary NFAS Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 510: Nfas Interface Id

    Mediant 800B Gateway & E-SBC Trunk". The T1 trunk whose D-channel is used for backup signaling is called the "Backup NFAS Trunk". The primary and backup trunks each carry 23 B-channels while all other NFAS trunks each carry 24 B-channels.

  • Page 511: Working With Dms-100 Switches

    Stop or delete (by setting ProtocolType to 0, i.e., 'None') all NFAS (‘slave’) trunks. Stop or delete (by setting ProtocolType to 0, i.e., 'None') the backup trunk if a backup trunk exists. Stop or delete (by setting ProtocolType to 0, i.e., 'None') the primary trunk. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Note: • All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure 22.6.4 Performing Manual D-Channel Switchover in NFAS Group...

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

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

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

    Mediant 800B Gateway & E-SBC • MinOverlapDigitsForRouting: Defines the minimum number of overlap digits to collect from the Tel side before the device can send the first SIP message (INVITE) for routing the call to the IP side. • MaxDigits: Defines the maximum number of collected digits that can be received from the Tel side (if ISDN Sending Complete IE is not received).
  • Page 515 4/5ESS Euro ISDN QSIG TE-to-NT Table 22-3: Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Yes* * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 516 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 517: Trunk Groups

    'Configuring Trunk Group Settings' on page 519).  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 518 Mediant 800B Gateway & E-SBC Table 23-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 519: 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 520 Mediant 800B Gateway & E-SBC Configure a Trunk Group according to the parameters described in the table below. Click Apply. Table 23-2: Trunk Group Settings Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row.
  • Page 521 [10] Select Trunk by Supp-Serv Table = The BRI port/module is selected according to the settings in the Supplementary Services table (see Configuring Multi-Line Extensions and Supplementary Services on page 618), allowing the routing of IP-to-Tel calls to Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 522 Mediant 800B Gateway & E-SBC Parameter Description specific BRI endpoints according to extension number. This option 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 523 If the PreferRouteTable parameter is set to 1 (see 'Configuring Proxy and Registration Parameters' on page 402), the routing rules in the Tel-to-IP Routing table take precedence over the selected Serving IP Group ID. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 524 Mediant 800B Gateway & E-SBC Parameter Description MWI Interrogation Type Defines message waiting indication (MWI) QSIG-to-IP interworking for interrogating MWI supplementary services: mwi-interrogation-type  [255] Not configured. [TrunkGroupSettings_MWIInt  [0] None = Disables the feature. errogationType]  [1] Use Activate Only = MWI Interrogation messages are not sent and only "passively"...

  • Page 525: 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 526 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 527 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 528 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 24-2: Tel-to-IP Routing Table - Add Dialog Box Configure a routing rule according to the parameters described in the table below.
  • Page 529 For example, [100-199](100,101,105) denotes a number that [PREFIX_SourcePrefix] starts with 100 to 199 and ends with 100, 101 or 105. To denote any prefix, use the asterisk (*) symbol (default) or to denote calls Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 530 Mediant 800B Gateway & E-SBC Parameter Description without a calling number, use the $ sign. For a description of available notations, see 'Dialing Plan Notation for Routing and Manipulation Tables' on page 1051. The number can include up to 50 digits.
  • Page 531 Assigns an IP Profile to the routing rule in the outgoing direction. The IP Profile allows you to assign various configuration attributes ip-profile-id (e.g., voice coder) per routing rule. To configure IP Profiles, see [PREFIX_ProfileName] 'Configuring IP Profiles' on page 436. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 532 Mediant 800B Gateway & E-SBC Parameter Description Destination Port Defines the destination port to where you want to route the call. 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...
  • Page 533 Cost Groups are considered as a higher or lower cost route compared to matching routing rules that are assigned Cost Groups. For example, if the 'Default Call Cost' parameter in the Routing Policy is configured to Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Parameter Description Lowest Cost, even if the device locates matching routing rules that are assigned Cost Groups, the first-matched routing rule without an assigned Cost Group is considered as the lowest cost route and thus, chosen as the preferred route.
  • Page 535 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 555. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 536 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 537 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 example, 10.8.8.* represents all addresses between Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 538 Mediant 800B Gateway & E-SBC Parameter Description 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. For example, [100- 199](100,101,105) denotes a number that starts with 100 to 199 and ends with 100, 101 or 105.

  • Page 539: 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 540 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 24-4: Routing Policies Table - Edit Dialog Box Configure the Routing Policy rule according to the parameters described in the table below. Click Apply. Table 24-5: Routing Policies Table Parameter Descriptions...

  • Page 541: 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 542: 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 543 Tel-to-IP Routing table to re-route the initial Tel-to-IP call. Table 24-6: Alternative Routing based on IP Connectivity Example Destination IP Connectivity IP Destination Rule Used? Phone Prefix Status Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 544: Alternative Routing Based On Sip Responses

    Mediant 800B Gateway & E-SBC Destination IP Connectivity IP Destination Rule Used? Phone Prefix Status Main Route 10.33.45.68 "No Connectivity" Alternative Route #1 10.33.45.70 "QoS Low" Alternative Route #2 10.33.45.72 "ok" The following procedure describes how to configure alternative Tel-to-IP routing based on IP connectivity.
  • Page 545 If the destination of a routing rule in the Tel-to-IP Routing table is an IP Group, the device routes the call to the IP destination configured for the Proxy Set associated with the IP Group. If the first IP destination of the Proxy Set is unavailable, Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 546 Mediant 800B Gateway & E-SBC the device attempts to re-route the call to the next proxy destination, and so on until an available IP destination is located. To enable the Proxy Redundancy feature for a Proxy Set, set the IsProxyHotSwap parameter to 1 and the EnableProxyKeepAlive parameter to 1.

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

    3xx responses using one of the following methods:  The device tries each contact sequentially, listed in the Contact headers, until a successful destination is found. If a contact responds with a SIP 486 or 600, the Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 548: Pstn Fallback

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

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

    For analog interfaces: For information on mapping PSTN release causes to SIP responses, see PSTN Release Cause to SIP Response Mapping. • For mapping SIP-to-Q.931 and Q.931-to-SIP release causes, see Configuring Release Cause Mapping on page 573. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 550 Mediant 800B Gateway & E-SBC The following procedure describes how to configure alternative routing reasons for IP-to- Tel calls through the Web interface. You can also configure it through ini file (AltRouteCauseIP2Tel) or CLI (configure voip > gateway routing alt-route-cause-ip2tel).

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

    The figure above displays a configuration that forwards IP-to-Tel calls destined for Trunk Group ID 1 to destination IP address 10.13.5.67 if conditions mentioned earlier exist. Configure a rule according to the parameters described in the table below. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 552: Alternative Routing Upon Isdn Disconnect

    Mediant 800B Gateway & E-SBC Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Table 24-10: Forward on Busy Trunk Destination Parameter Descriptions Parameter Description Index Defines an index number for the new table row.

  • Page 553: Alternative Routing From Fxo To Ip

    SIP Trunk. This is configured using the ini file parameter, TR104FXOSwitchover. For more information on this application, please contact your AudioCodes sales representative. Version 7.2...
  • Page 554 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 555: 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 556 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 557 Table 25-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 558 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 559 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. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 560 Mediant 800B Gateway & E-SBC Parameter Description Action 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 561: Manipulating Number Prefix

    The notation is entered in the 'Prefix to Add' field in the Number Manipulation tables (see 'Configuring Source/Destination Number Manipulation' on page 555): x[n,l]y... Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 562: Sip Calling Name Manipulations

    Mediant 800B Gateway & E-SBC where,  x = any number of characters/digits to add at the beginning of the number (i.e. first digits in the prefix).  [n,l] = defines the location in the original destination or source number where the digits y are added: •...
  • Page 563 To configure calling name manipulation rules: Open the required calling name manipulations table (Setup menu > Signaling & Media tab > Gateway folder > Manipulation > Calling Name IP->Tel or Calling Name Tel->IP). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 564 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 25-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.
  • Page 565 For example, if you enter 3 and the calling name is "company:john", the new calling name is "pany:john". [_RemoveFromLeft] Stripped Characters From Defines the number of characters to remove from the right of the calling Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 566: Configuring Redirect Number Ip To Tel

    Mediant 800B Gateway & E-SBC Parameter Description Right name. remove-from-right For example, if you enter 3 and the calling name is "company:name", the new name is "company:n". [_RemoveFromRight] Number of Characters to Defines the number of characters that you want to keep from the right Leave of the calling name.
  • Page 567 Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables. manipulation-name The valid value is a string of up to 40 characters. [_ManipulationName] Match Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 568 Mediant 800B Gateway & E-SBC Parameter Description Destination Prefix Defines the destination (called) telephone number prefix. dst-prefix The default value is the asterisk (*) symbol (i.e., any number). [_DestinationPrefix] For manipulating the diverting and redirected numbers for call diversion, you can use the strings "DN" and "RN" to denote the destination prefix of these numbers.
  • Page 569 [-1] Not Configured = (Default) Value received from PSTN/IP is used  [0] Unknown [_NumberPlan]  [1] E.164 Public  [9] Private For more information on available NPI/TON values, see Numbering Plans and Type of Number on page 581. Presentation Enables caller ID. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Parameter Description  is-presentation-restricted Not Configured = Privacy is determined according to the Caller ID table (see Configuring Caller Display Information on page 636). [_IsPresentationRestricted]  [0] Allowed = Sends Caller ID information when a call is made using these destination / source prefixes.

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

    CLI (configure voip > gateway manipulation phone-context-table).  To configure NPI/TON-SIP phone-context mapping rules: Open the Phone Contexts table (Setup menu > Signaling & Media tab > Gateway folder > Manipulation > Phone Contexts). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 572 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 25-5: Phone Contexts Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply. Note: • You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'.

  • Page 573: Configuring Release Cause Mapping

    The parameter defines a default ISDN cause code that is always used, except when the following Release Causes are received: Normal Call Clearing (16), User Busy (17), No User Responding (18) or No Answer from User (19). Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC The following procedure describes how to configure SIP-to-ISDN release cause mapping through the Web interface. You can also configure it through ini file (CauseMapSIP2ISDN) or CLI (configure voip > gateway manipulation cause-map-sip2isdn).  To configure a SIP-to-ISDN release cause mapping rule: Open the Release Cause Mapping from SIP to ISDN table (Setup menu >...
  • Page 575 Temporary failure Server timeout Recovery on timer expiry 505* Version not supported Interworking Busy everywhere User busy Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does not specify their cause code mapping. 25.8.2 ISDN-to-SIP Release Cause Mapping 25.8.2.1 Configuring ISDN-to-SIP Release Cause Mapping The Release Cause Mapping from ISDN to SIP table lets you configure up to 12 ISDN ITU- T Q.850 release cause code (call failure) to SIP response code mapping rules.

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

    Temporarily unavailable Call rejected Forbidden Number changed w/o diagnostic Gone Redirection Bad Request Exchange Routing Error Bad Request Non-selected user clearing Not found Destination out of order Bad gateway Address incomplete Address incomplete Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 578 Mediant 800B Gateway & E-SBC ISDN Release Description Description Reason Response Facility rejected Not implemented Response to status enquiry 501* Not implemented Normal unspecified Temporarily unavailable Circuit Congestion Server internal error User Congestion Server internal error No circuit available Service unavailable...

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

    When the device receives an ISDN cause code from the PSTN side, it searches the table for a matching ISDN cause code. If found, the device changes the cause code to the corresponding ISDN cause code. If the ISDN cause Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 580 Mediant 800B Gateway & E-SBC code is not configured in the table, the originally received ISDN cause code is used. If the new ISDN cause code also appears in the Release Cause Mapping ISDN to SIP table (see 'Configuring ISDN-to-SIP Release Cause Mapping' on page 576), the device maps it to the corresponding SIP response code, which it sends to the IP side.

  • Page 581: Reason Header

    16135551234. National-Level1 Regional [2] A public number in complete national E.164 format, e.g., 6135551234. Network-PSTN Specific [3] The type of number "network specific number" is used to indicate administration / service number Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 582 Mediant 800B Gateway & E-SBC Description specific to the serving network, e.g., used to access an operator. Subscriber-Level0 Regional A public number in complete E.164 format representing a local subscriber, e.g., 5551234. Abbreviated [6] The support of this code is network dependent. The...

  • Page 583: 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 584: 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 585: 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 586 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 473.

  • Page 587: 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 588 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 589: 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 590: 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 591: 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 592: Blind Call Transfer

    Mediant 800B Gateway & E-SBC 27.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 593: Enabling Call Forwarding

    638. 27.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 594 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 595: 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 596: Remote Handling Of 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 834). 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 597 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 598: Local Handling Of Bri Call Forwarding

    Mediant 800B Gateway & E-SBC 27.6.6 Local Handling of BRI Call Forwarding You can configure the device to handle BRI call forwarding per BRI extension line, using the Supplementary Services table. Upon receipt of an ISDN Facility message from the BRI phone user, the device retrieves and stores the user's call forwarding information.

  • Page 599: Enabling Call Waiting

    To enable and configure call waiting: Open the Supplementary Services Settings page (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services Settings). Figure 27-7: Configuring Call Waiting Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 600: Message Waiting Indication

    Mediant 800B Gateway & E-SBC From the 'Enable Call Waiting' drop-down list (EnableCallWaiting), select Enable. Configure call waiting indication and call waiting ringback tones in the Call Progress Tones file (see 'Call Progress Tones File' on page 834). You can configure up to four call waiting indication tones (see the FirstCallWaitingToneID parameter).
  • Page 601 • Send MWI Interrogation message, but don't use its result. Instead, wait for MWI Activate requests from the PBX. • Send MWI Interrogation message, use its result, and use the MWI Activate requests. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 602: Caller Id

    Mediant 800B Gateway & E-SBC 27.9 Caller ID This section describes the device's Caller ID support. Note: The Caller ID feature is applicable only to FXS/FXO interfaces. 27.9.1 Enabling Caller ID Generation and Detection on Tel Side The device's Caller ID support depends on the type of analog interface: ...

  • Page 603: Debugging A Caller Id Detection On Fxo

    ID. If the above does not solve the problem, you need to record the caller ID signal (and send it to AudioCodes), as described below.  To record the caller ID signal using the debug recording mechanism: Access the FAE page (by appending "FAE"...

  • Page 604: 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 605 (e.g., "*1"), configured by the HookFlashCode parameter. • Three-way conferencing is applicable only to FXS and BRI interfaces. • Three-way conferencing support for the BRI phones connected to the device complies with ETS 300 185. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 606 Mediant 800B Gateway & E-SBC The following example demonstrates three-way conferencing using the device's local, on- board conferencing feature. In the example, telephone "A" connected to the device establishes a three-way conference call with two remote IP phones, "B" and "C": A establishes a regular call with B.

  • Page 607: Emergency E911 Phone Number Services

    The wink can be delayed by configuring the parameter DelayBeforeDIDWink to 200 (for 200 msec or a higher value). The switch detects the wink and then sends the MF Spill digits with ANI and (optional) Pseudo-ANI (P ANI). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 608 Mediant 800B Gateway & E-SBC The FXS device collects the MF digits, and then sends a SIP INVITE message to the PSAP with all collected MF digits in the SIP From header as one string. The FXS device generates a mid-call wink signal (two subsequent polarity reversals) toward the E911 tandem switch upon either detection of an RFC 2833 "hookflash"...
  • Page 609 If the device receives the SIP INFO message below, it then generates a "hookflash" mid- call Wink signal: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: port1vega1 <sip:06@192.168.13.2:5060> To: <sip:4505656002@192.168.13.40:5060>;tag=132878796- 1040067870294 Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2 CSeq:2 INFO Content-Type: application/broadsoft Content-Length: 17 event flashhook Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 27.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines The device's FXO interface can interwork SIP emergency E911 calls from the Service Provider's IP network to the analog PSAP DID lines. The standards that define this interface include TR-TSY-000350 or Bellcore’s GR-350-Jun2003.
  • Page 611 "mmmmmmmmmm" (pANI) None "KPnnSTP" "nn" MF dialed "KPnST" "n" For example: "From: <sip:8>@xyz.com>" generates device MF spill of KP 8 ST Table notes:  For all other cases, a SIP 484 response is sent. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 612 Mediant 800B Gateway & E-SBC  KP is for .  ST is for #.  STP is for B. The MF duration of all digits, except for the KP digit is 60 msec. The MF duration of the KP digit is 120 msec.

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

    Figure 27-13: Emergency Numbers The device identifies the IP-to-Tel call as an emergency call if the destination number matches one of these configured emergency numbers. For E911, you must configure the parameter to "911". Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 614: Multilevel Precedence And Preemption

    Mediant 800B Gateway & E-SBC Note: • The device also identifies emergency calls if the Priority header of the incoming SIP INVITE message contains the “emergency” value. • This feature is applicable to the following interfaces: √ √ ISDN √...
  • Page 615 Department of Defense (DoD) Unified Capabilities (UC) Requirements (UCR 2008, Changes 3) document, as shown below: Table 27-4: NI Digits in ISDN Precedence Level IE Network Domain in SIP Resource-Priority Header 0000 0001 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 616 Mediant 800B Gateway & E-SBC Level IE Network Domain in SIP Resource-Priority Header 0002 0003 nato Note: • If the received ISDN message contains NI digits that are not listed in the translation table, the device sets the network-domain to "uc" in the outgoing SIP message.

  • Page 617: Mlpp Preemption Events In Sip Reason Header

    The softswitch sends the device a SIP 488 (Not Acceptable Here) response code with this Reason cause code. The device initiates the release procedures for the B-channel associated with the call request and maps the preemption cause to ISDN Cause = #8 ‘Preemption’. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 618: Precedence Ring Tone

    Mediant 800B Gateway & E-SBC The device deactivates any user signaling (e.g., ringback tone) and when the call is terminated, it sends a SIP ACK message to the softswitch. 27.12.2 Precedence Ring Tone You can assign a ring tone that is defined in the CPT file to be played when a precedence call is received from the IP side.
  • Page 619 (configure voip > gateway digital isdn-supp-serv).  To configure endpoint supplementary services: Open the Supplementary Services table (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 620 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 27-14: Supplementary Services Table - Add Dialog Box Configure a supplementary service according to the parameters described in the table below. Click Apply. You can also register and un-register an endpoint configured in the table: ...
  • Page 621 The parameter is applicable only to BRI interfaces.  To enable BRI call forwarding services, see the BRICallForwardHandling parameter. For more information on configuring local handling of BRI call forwarding, see Local Handling of BRI Call Forwarding on page 598. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 622: Detecting Collect Calls

    Mediant 800B Gateway & E-SBC Parameter Description CFU Phone Number Defines the phone number for BRI Call Forward Unconditional (CFU) services. The device always cfu-to_phone-number forwards the call to this number. [ISDNSuppServ_CFU2PhoneNumber] Note:  The parameter is applicable only to BRI interfaces.

  • Page 623: Advice Of Charge Services For Euro Isdn

    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 624: Configuring Charge Codes

    Mediant 800B Gateway & E-SBC ♦ charging-info="currency" or "pulse" If "currency", the following parameters are available: ♦ currency=<string> ♦ currency-type="iso4217-a" or <string> ♦ amount=<number> ♦ multiplier=("0.001","0.01","0.1","1","10","100","1000") If "pulse", the following parameter is available: ♦ recorded-units=<number> • TELES proprietary method •...
  • Page 625 > Routing > Charge Codes). Click New; the following dialog box appears: Figure 27-17: Charge Codes Table - Add Dialog Box Configure a Charge Code according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 626: Configuring Voice Mail

    Mediant 800B Gateway & E-SBC Table 27-7: Charge Codes Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [ChargeCode_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.
  • Page 627 • 'Forward on No Answer Digit Pattern Internal' (DigitPatternForwardOnNoAnswer): Defines the digit pattern to indicate 'call forward on no answer' when the original call is received from an internal extension. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 628: Converting Accented Characters From Ip To Tel

    Mediant 800B Gateway & E-SBC • 'Forward on Do Not Disturb Digit Pattern Internal' (DigitPatternForwardOnDND): Defines the digit pattern to indicate 'call forward on do not disturb' when the original call is received from an internal extension. • 'Forward on No Reason Digit Pattern Internal' (DigitPatternForwardNoReason): Defines the digit pattern to indicate 'call forward with no reason' when the original call is received from an internal extension.
  • Page 629 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 630 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 631: Analog Gateway

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

  • Page 632: Configuring Metering Tones

    Mediant 800B Gateway & E-SBC Configure the keypad features as required. Click Apply. 28.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 633: 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 28-4: Enabling Authentication per Endpoint Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 634 Mediant 800B Gateway & E-SBC • Endpoints per Trunk Group: Open the Trunk Group Settings table (see 'Configuring Trunk Group Settings' on page 519), and then for the required Trunk Group ID, configure the 'Registration Mode' parameter to Per Endpoint (TrunkGroupSettings_RegistrationMode).

  • Page 635: 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 636: 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 637 [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 638: 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 639 '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 640: 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 525).

  • Page 641: 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 642: 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 643: 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 644: Fxs/Fxo Coefficient Types

    Mediant 800B Gateway & E-SBC Table 28-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 645: Fxo Operating Modes

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

  • Page 646: One-Stage Dialing

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

  • Page 647: 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 648: 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 649: 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 650: 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. 28.13.3 Call Termination on FXO Devices This section describes the device's call termination capabilities for its FXO interfaces: ...

  • Page 651: 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 652: 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 653: 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 654: Fxs Gateway Configuration

    Mediant 800B Gateway & E-SBC 28.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 655: Fxo Gateway Configuration

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

  • Page 657: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 659: 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 660: 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 661 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 662 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 663: 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 664 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 665: 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 666: 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 667: 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 668: 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 669: 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 670: 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 29-3: SDP Offer/Answer Example 29.5.2 Direct Media...
  • Page 671 Microsoft Server (direct media is required in the Skype for Business environment). For more information, see 'Configuring IP Groups' on page 365. 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 672: 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 673: Coder Transcoding

    SDP answer from the WAN IP phone includes the G.729 coder as the chosen coder. 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. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 674 Mediant 800B Gateway & E-SBC Figure 29-5: Transcoding using Extended Coders (Example) 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.
  • Page 675 G.729 and G.726, but removes the G.711 coder as it does not appear in the Allowed Audio Coders Group for coder restriction. m=audio 6050 RTP/AVP 18 96 96 a=rtpmap:18 G729/8000 a=rtpmap:96 G726-32/8000 a=fmtp:4 annexa=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 676: Transcoding Mode

    Mediant 800B Gateway & E-SBC a=ptime:20 a=sendrecv The device includes only the G.729 and G.726 coders in the SDP offer that it sends from the outgoing leg to the outbound SIP entity. The G.729 is listed first as the Allowed Audio Coders Group for coder restriction takes precedence over the extension coder.

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

    It supports the negotiation of up to five media streams ('m=' line) in the SDP offer/answer model per session. The media can include a combination of any of the following types:  Audio, indicated in the SDP as 'm=audio' Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 678: Interworking Miscellaneous Media Handling

    Mediant 800B Gateway & E-SBC  Video, indicated in the SDP as 'm=video'  Text, indicated in the SDP as 'm=text'  Fax, indicated in the SDP as 'm=image'  Binary Floor Control Protocol (BFCP), indicated in the SDP as 'm=application <port>...

  • Page 679: Interworking Rtp-Rtcp Multiplexing

    SIP entity. The IP Profiles table also defines the negotiation method used between the incoming and outgoing fax legs, using the following fax-related parameters:  IPProfile_SBCFaxBehavior: defines the offer negotiation method - pass fax Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 680: Limiting Sbc Call Duration

    Mediant 800B Gateway & E-SBC transparently, negotiate fax according to fax settings in IP Profile, or enforce remote UA to first establish a voice channel before fax negotiation.  IPProfile_SBCFaxCodersGroupName: defines the supported fax coders (from the Coder Groups table).

  • Page 681: User Authentication Based On Radius

    The SIP client sends the SIP request with the Authorization header to the device. The device sends an Access-Request message to the RADIUS server. The RADIUS server verifies the client's credentials and sends an Access-Accept (or Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 682: Interworking Sip Signaling

    Mediant 800B Gateway & E-SBC Access-Reject) response to the device. The device accepts the SIP client's request (sends a SIP 200 OK or forwards the authenticated request) or rejects it (sends another SIP 407 to the SIP client). To configure this feature, set the SBCServerAuthMode ini file parameter to 2.

  • Page 683: 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 684: Interworking Sip Diversion And History-Info Headers

    Mediant 800B Gateway & E-SBC 29.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 685: Interworking Sip Prack Messages

    29.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 686 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 687 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 29-8: SBC Early Media RTP 18x without SDP Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 688: Interworking Sip Re-Invite Messages

    Mediant 800B Gateway & E-SBC Figure 29-9: Early Media RTP - SIP 18x with SDP 29.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 689: 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 690: 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 436. 29.9.12 Interworking SIP Via Headers The device supports the interworking of SIP Via headers between SIP entities.

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

  • Page 693: 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 1331).
  • Page 694 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 695: 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 696 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 697: 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 698 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 699 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 700 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 701: 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 702 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 703 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 704 Mediant 800B Gateway & E-SBC The flowchart below illustrates the classification process: Figure 34-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 705 Assigns a SIP Interface to the rule as a matching characteristic for the incoming 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). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 706 Mediant 800B Gateway & E-SBC Parameter Description Note: The SIP Interface must belong to the SRD assigned 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.
  • Page 707 Routing Policy is specified to override the SRD's assigned Routing Policy. By default, no value is defined. To configure Routing Policies, see 'Configuring SBC Routing Policy Rules' on page 730. Version 7.2 Mediant 800B Gateway & E-SBC...

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

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

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

    IP Group - the destination is the address configured for the Proxy Set associated with the IP Group.  IP Group Set - the destination can be based on multiple IP Groups for load balancing, Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 710 Mediant 800B Gateway & E-SBC where each call may be sent to a different IP Group within the IP Group Set depending on the IP Group Set's definition.  Routing tag - the device sends the call to an IP Group (or IP Group Set) based on a destination Dial Plan tag that corresponds to the destination (called) prefix number.
  • Page 711 SIP response code (i.e., 4xx, 5xx, and 6xx SIP responses) configured in the Alternative Routing Reasons table (see 'Configuring SIP Response Codes for Alternative Routing Reasons' on page 728). ♦ SIP 408 Timeout or no response (after timeout). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 712 Mediant 800B Gateway & E-SBC • The DNS resolution includes IP addresses that the device has yet to try (for the current call). Messages are re-routed with the same SIP Call-ID and CSeq header fields (increased by 1). Note: If the Proxy Set (see Configuring Proxy Sets on page 380) associated with the...
  • Page 713 You can also configure it through ini file (IP2IPRouting) or CLI (configure voip > sbc routing ip2ip-routing).  To configure an IP-to-IP routing rule: Open the IP-to-IP Routing table (Setup menu > Signaling & Media tab > SBC folder > Routing > IP-to-IP Routing). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 714 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 34-3: IP-to-IP Routing Table - Add Dialog Box Configure an IP-to-IP routing rule according to the parameters described in the table below. Click Apply. Table 34-2: IP-to-IP Routing Table Parameter Descriptions...
  • Page 715 Routing Policy (in the 'Routing Policy' parameter in this table). For more information, see 'Configuring SBC Routing Policy Rules' on page 730. Request Type Defines the SIP dialog request type (SIP Method) of the incoming SIP dialog. request-type Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 716 Mediant 800B Gateway & E-SBC Parameter Description  [IP2IPRouting_RequestType] [0] All (default)  [1] INVITE  [2] REGISTER  [3] SUBSCRIBE  [4] INVITE and REGISTER  [5] INVITE and SUBSCRIBE  [6] OPTIONS Source Username Prefix Defines the prefix of the user part of the incoming SIP dialog's source URI (usually the From URI).
  • Page 717 SIP 3xx redirect responses or REFER ame] messages. For more information, see 'Interworking SIP 3xx Redirect Responses' on page 682 and 'Interworking SIP REFER Messages' on page 684, respectively. The parameter functions Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 718 Mediant 800B Gateway & E-SBC Parameter Description together with the 'Call Trigger' parameter (in the table). The default is Any (i.e., any IP Group). Note: The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in this table).
  • Page 719 The parameter is applicable only if the 'Destination Type' parameter is configured to IP Group.  The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 720 Mediant 800B Gateway & E-SBC Parameter Description this table). For more information, see 'Configuring SBC Routing Policy Rules' on page 730. Destination SIP Interface Defines the destination SIP Interface to where the call is sent. dest-sip-interface-name By default, no value is defined.
  • Page 721 Defines the destination Dial Plan tag, which is used to determine the destination IP Group. routing-tag-name The default value is "default", meaning that the device uses the [IP2IPRouting_RoutingTagName] first tag name in the Dial Plan rule that is configured without a Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 722: Configuring Rerouting Of Calls To Fax Destinations

    Mediant 800B Gateway & E-SBC Parameter Description value. For example, if the Dial Plan rule is configured with tags "Country=England;City=London;Essex", the default tag is "Essex". For more information, see Using Dial Plan Tags for Routing Destinations on page page 761.
  • Page 723 IP-to-IP Routing Rule #0 - routes voice calls from IP Group #0 to IP Group #1: Match Source IP Group HQ (IP Group #0) Call Trigger Initial Only ReRoute IP Group Voice (IP Group #1) Action Destination Type IP Group Destination IP Group Voice (IP Group #1) Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 724: Configuring Specific Udp Ports Using Tag-Based Routing

    Mediant 800B Gateway & E-SBC • IP-to-IP Routing Rule #1 - routes fax calls from IP Group #0 to IP Group #2: Match Source IP Group HQ (IP Group #0) Call Trigger Fax Rerouting Action Destination Type IP Group Destination IP Group Fax (IP Group #2) 34.2.2 Configuring Specific UDP Ports using Tag-based Routing...
  • Page 725 IP Group for the second IP PBX ("Type" and "Port" tags are later used to identify the IP PBX and assign it a local UDP port 6002 on the leg interfacing with the proxy server): General Index Name PBX-2 Type Server SBC Advanced Tags Type=PBX;Port=6002 Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 726 Mediant 800B Gateway & E-SBC • IP Group for the third IP PBX ("Type" and "Port" tags are later used to identify the IP PBX and assign it a local UDP port 6003 on the leg interfacing with the proxy...
  • Page 727 Routes calls from the ITSP (identified by the source tag name-value "Type=ITSP") to the IP PBXs (identified by the specific port assigned to the IP PBX by the value of the destination tag name "Port"): General Index Name ITSP-to-PBX Match Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Source Tag Type=ITSP Action Destination Type Destination Tag Routing Tag Name Port 34.3 Configuring SIP Response Codes for Alternative Routing Reasons The Alternative Routing Reasons table lets you configure up to 20 SIP response codes for call release (termination) reasons.
  • Page 729 [4] 4xx; [5] 5xx; [6] 6xx; [400] Bad Request; [402] [SBCAlternativeRoutingReasons_ReleaseCause] 402 Payment Required; [403] Forbidden; [404] Not Found; [405] Method Not Allowed; [406] Not Acceptable; [408] Request Timeout (Default); [409] Conflict; [410] Gone; [413] Request Too Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 730: Configuring Sbc Routing Policy Rules

    Mediant 800B Gateway & E-SBC Parameter Description Large; [414] Request URI Too Long; [415] Unsupported Media; [420] Bad Extension; [421] Extension Required; [423] Session Interval Too Small; [480] Unavailable; [481] Transaction Not Exist; [482] Loop Detected; [483] Too Many Hops;...
  • Page 731 SRD that is assigned to the SIP Interface. Once the call has been successfully classified to an IP Group, the Routing Policy assigned to the associated SRD is used. However, if a Routing Policy is configured in Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 732 Mediant 800B Gateway & E-SBC the Classification table, it overrides the Routing Policy assigned to the SRD. The regular manipulation (inbound and outbound) and routing processes are done according to the associated Routing Policy. Note: • The Classification table is used only if classification by registered user in the device's users registration database or by Proxy Set fails.
  • Page 733 Cost Groups are unavailable. Note: If multiple matched routing rules without an assigned Cost Group exist, the device selects the first matched rule in the table. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 734: Configuring Ip Group Sets

    Mediant 800B Gateway & E-SBC Parameter Description LCR Call Duration Defines the average call duration (in minutes) and is used to calculate the variable portion of the call cost. This is useful, for lcr-call-length example, when the average call duration spans over multiple time [SBCRoutingPolicy_LCRAvera bands.
  • Page 735 IP Group for each call. The device selects the first IP Group [IPGroupSet_Policy] in the table (i.e., lowest index) for the first call and the next consecutive IP Groups for the next calls. For example, first call to IP Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 736 Mediant 800B Gateway & E-SBC Parameter Description Group at Index 0, second call to IP Group at Index 2, third call to IP Group at Index 3, and so on. If an IP Group is offline, the device selects the next consecutive IP Group. Once the last IP Group in the...
  • Page 737 IP Group being selected as the destination weight of the call. [IPGroupSetMember_Weight] The valid value is 1 to 9. The default is 1. Note: The parameter is applicable only if you configure the 'Policy' parameter to Random Weight. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 738 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 739: 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 740 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 741: 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 742 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 730.
  • Page 743 [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 744 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 745: 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 746 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 35-3: Outbound Manipulations Table- Add Dialog Box Configure an Outbound Manipulation rule according to the parameters described in the table below.
  • Page 747 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 1051. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 748 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 749 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 750 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 751: Configuring Dial Plans

    Dial Plan for a rule that matches the destination number. If matching dial plan rules are found, the tags configured for these rules are used in the routing and/or manipulation processes as source and/or destination tags. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 752 Mediant 800B Gateway & E-SBC Note: When tags are used in the IP-to-IP Routing table to determine destination IP Groups (i.e., 'Destination Type' parameter configured to Destination Tag), the device searches the Dial Plan for a matching destination (called) prefix number only.
  • Page 753  For incoming calls with prefix number "53124", the rule with tag C is chosen (longest suffix - C has three digits, B two digits and A one digit): Prefix 53([2-4]) 53([01-99]) 53([001-999]) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 754 Mediant 800B Gateway & E-SBC  For incoming calls with prefix number "53124", the rule with tag B is chosen (suffix is more specific for digit "4"): Prefix 53([2-4]) 53(4),B Dial Plans are configured using two tables with parent-child type relationship: ...
  • Page 755 Note: Each row must be configured with a unique index. index [DialPlanRule_RuleIndex] Name Defines a descriptive name, which is used when associating the row in other tables. name The valid value is a string of up to 15 characters. [DialPlanRule_Name] Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 756 Mediant 800B Gateway & E-SBC Parameter Description Prefix Defines the prefix number of the source or destination number. prefix The valid value is up to 50 characters. The following syntax can be used: [DialPlanRule_Prefix]  0-9: Specific digit.  x: Wildcard denoting any digit from 0 through 9.

  • Page 757: Importing And Exporting Dial Plans

    Select the Save File option, and then click OK; the file is saved to the default folder on your PC for downloading files.  CLI (to a remote server): (config-voip)# sbc dial-plan-rule export-csv-to <Dial Plan name or index> <URL of server> Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 758 Mediant 800B Gateway & E-SBC For example: (config-voip)# sbc dial-plan-rule export-csv-to 0 http://10.8.8.20/upload/index_0_Dial_Plans.csv The following procedures describe how to import a Dial Plan file.  To overwrite all existing Dial Plans with imported Dial Plan file:  Web interface (from a local folder): Open the Dial Plan table.

  • Page 759: Creating Dial Plan Files

     Prefix: Source or destination number prefix.  Tag: Result of the user categorization and can be used as matching characteristics for routing and outbound manipulation For example: DialPlanName,Name,Prefix,Tag PLAN1,rule_100,5511361xx,A PLAN1,rule_101,551136184[4000-9999]#,B MyDialPlan,My_rule_200,5511361840000#,itsp_1 MyDialPlan,My_rule_201,66666#,itsp_2 Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 36.3 Using Dial Plan Tags for IP-to-IP Routing You can use Dial Plan tags with IP-to-IP Routing rules in the IP-to-IP Routing table, where tags can be used for the following:  Matching routing rules by source and/or destination prefix numbers (see Using Dial Plan Tags for Matching Routing Rules on page 760) ...

  • Page 761: Using Dial Plan Tags For Routing Destinations

    The device searches the IP Groups table and IP Group Set table for an IP Group whose 'Tags' parameter is configured with the same tag as selected from the Dial Plan rule. If found, the device routes the call to this IP Group. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 762 Mediant 800B Gateway & E-SBC The following figure displays the device's SIP dialog processing when Dial Plan tags are used to determine the destination IP Group: Figure 36-7: SIP Dialog Handling for Tag-Based Routing The following procedure describes how to configure routing to destination IP Groups determined by Dial Plan tags.
  • Page 763 "Holland" is the tag name without a value. If an additional tag name is configured, for example, "Holland;France", the setting is invalid. √ Tag names with values (i.e., name=value) must be unique within a Dial Plan Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 764: Dial Plan Backward Compatibility

    Mediant 800B Gateway & E-SBC rule. In the above example, "Country=England" is a tag name with value. Configuring the parameter with "Country=England;Country=Scotland" is invalid. A valid configuration would be "Country=England;Country1=Scotland". • Configure the 'Routing Tag Name' parameter with only the name of the tag (i.e., without the value, if exists).

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

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

    Mediant 800B Gateway & E-SBC • 'Destination Tags' parameter (IPOutboundManipulation_DestTags): tag denoting the called users 36.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 404).

  • Page 767: 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 768 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 37-1: Malicious Signature Table - Add Dialog Box Configure a Malicious Signature according to the parameters described in the table below.

  • Page 769: Advanced Sbc Features

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

  • Page 770: 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 38-2: Configuring Emergency SBC Call Preemption From the 'Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable call preemption.

  • Page 771: 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 772 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 773 'Configuring SIP Message Manipulation' on page 413). 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 774: Webrtc

    Mediant 800B Gateway & E-SBC 38.4 WebRTC The device supports interworking of Web Real-Time Communication (WebRTC) and SIP- based VoIP communication. The device interworks WebRTC calls made from a Web browser (WebRTC client) and the SIP destination. The device provides the media interface to WebRTC.
  • Page 775 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 776: 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 777 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 778: 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 779 From the 'TLS Context Name' drop-down list, assign the TLS Context that you configured in Step 1 (e.g., "WebRTC"). Figure 38-7: Configuring SIP Interface for WebRTC Clients Click Apply. Configure an IP Profile for the WebRTC clients: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 780 Mediant 800B Gateway & E-SBC Open the IP Profiles table (see 'Configuring IP Profiles' on page 436). Do the following: ♦ From the 'ICE Mode' drop-down list (IPProfile_SBCIceMode), select Lite to enable ICE. ♦ From the 'RTCP Mux' drop-down list (IPProfile_SBCRTCPMux), select Supported to enable RTCP multiplexing.

  • Page 781: Call Forking

    UAs are handled by the device; SDP offers from these UAs are answered with an "inactive" media. The device supports two forking modes:  Latch On First: The device forwards only the first received 18x response to the Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC 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 forwarded to the INVITE-initiating UA.

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

    For example, assume primary extension number 600 is shared with secondary extensions 601 and 602. In the case of an incoming call to 600, all three phone extensions ring simultaneously, Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 784 Mediant 800B Gateway & E-SBC using the device's call forking feature as described in 'Configuring SIP Forking Initiated by SIP Proxy' on page 781. Note that incoming calls specific to extensions 601 or 602 ring only at these specific extensions.

  • Page 785: 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 38-12: Normal Operation in Call Center Application Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 786 Mediant 800B Gateway & E-SBC Figure 38-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 365), add IP Groups for the following entities: •...

  • Page 787: 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 788: 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 789 Extension Coders Group: Coders Group with G.711 ♦ Allowed Audio Coders: Allowed Audio Coders Group with G.711 ♦ Allowed Coders Mode: Restriction ♦ RTCP Feedback: Feedback On ♦ Voice Quality Enhancement: Enable • Alternative IP Profile: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 790 Mediant 800B Gateway & E-SBC ♦ Extension Coders Group: Coders Group with Opus ♦ Allowed Audio Coders: Allowed Audio Coders Group with Opus ♦ Allowed Coders Mode: Restriction ♦ RTP Redundancy Mode: Enable ♦ RTCP Feedback: Feedback On ♦ Voice Quality Enhancement: Enable ♦...

  • Page 791: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 793: 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 794 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 795: 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 796: Configuring Call Survivability Mode

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

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

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

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

  • Page 799: Emergency Mode

    Route Row #2 [CRP Proxy] IP Group #3 [CRP Route Row Gateway] #3 [CRP IP Group #2 [CRP Proxy] Route Row Gateway] #3 [CRP IP Group #1 [CRP Users] Alternative Gateway] Route Ignore Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 800: Configuring Pstn Fallback

    Mediant 800B Gateway & E-SBC Mode Index Source IP Request Type Destination Destination IP Destination Alternative Group Type Group Address Route Options Inputs Note: • The destination for the routing rule at Index 2 is the source IP Group (i.e., from where the REGISTER message is received).

  • Page 801: High-Availability System

    Part VIII High-Availability System...

  • Page 803: Ha Overview

    Device Switchover upon Failure on page 804. • 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 804: 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 805: 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 806 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 807: Ha Configuration

    Maintenance interface with two ports. The required receive (Rx) and transmit (TX) mode for the port pair in the Ethernet Group used by the Maintenance interface is as follows (not applicable to Mediant VE): Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 808 Mediant 800B Gateway & E-SBC  (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 42-1: Rx/Tx Mode for Direct Connection  If the two devices are connected through two (or more) isolated LAN switches (i.e.,...

  • Page 809: Configuring The Ha Devices

    Connect your PC to the device using a local, direct physical cable connection and then access the Web interface using the default OAMP network address. For more information on initial access, see Assigning the OAMP IP Address on page Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 810 Mediant 800B Gateway & E-SBC Open the IP Interfaces table (see 'Configuring IP Network Interfaces' on page 146). Change the default OAMP network settings to suit your networking scheme. Configure the Control and Media network interfaces, as required. Add the HA Maintenance interface (i.e., the MAINTENANCE Application Type).

  • Page 811: Step 2: Configure The Second Device

    Configure the same Ethernet port Tx / Rx mode of the Ethernet Group used by the Maintenance interface as configured for the first device. Configure HA parameters in the HA Settings page: In the 'HA Remote Address' field, enter the Maintenance IP address of the first device. Version 7.2 Mediant 800B Gateway & E-SBC...

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

    Mediant 800B Gateway & E-SBC Enable the HA Preempt feature by configuring the 'Preempt Mode' parameter to Enable, and then setting the priority level of the device in the 'Preempt Priority' field. Make sure that you configure different priority levels for the two devices.

  • Page 813: Configuring Firewall Allowed Rules

    Packet Byte Byte Index Source IP End Port Protocol Specific Upon Port Length Port Name Size Rate Burst Interface Match Various rules for basic traffic. 10.31.4.61 Enable HA_IF Allow 10.31.4.62 Enable HA_IF Allow Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 814 Mediant 800B Gateway & E-SBC Action Source Prefix Start Interface Packet Byte Byte Index Source IP End Port Protocol Specific Upon Port Length Port Name Size Rate Burst Interface Match 10.31.4.61 2442 2442 Enable HA_IF Allow 10.31.4.62 2442 65535 Enable...

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

    In the 'Source Interface Name' field, enter the device's IP network interface from where you want to ping the destination entity. • In the 'Ping Timeout' field, enter the timeout for which the ping request waits for a response. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 816 Mediant 800B Gateway & E-SBC • In the 'Ping Retries' field, enter the number of ping requests that the device sends after no ping response is received from the destination, before it considers the destination as unavailable. Figure 42-7: Configuring HA Network Reachability Click Apply.

  • Page 817: Ha Maintenance

    'Configuring the HA Devices' on page 809. 43.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 825. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 818: Software Upgrade

    Mediant 800B Gateway & E-SBC 43.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 819: Maintenance

    Part IX Maintenance...

  • Page 821: 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 822: 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 823: 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 824: Saving Configuration

    Mediant 800B Gateway & E-SBC 44.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 825: 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 826 Mediant 800B Gateway & E-SBC • Navigation tree: Setup menu > Administration tab > Maintenance folder > High Availability Maintenance. Figure 45-2: Resetting Redundant Device click Reset; a confirmation box appears requesting you to confirm. Click OK. User's Manual Document #: LTRT-10632...

  • Page 827: 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 828: Locking And Unlocking Trunk Groups

    Mediant 800B Gateway & E-SBC 46.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 829: 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 830: Configuring Name For Telephony Ports

    Mediant 800B Gateway & E-SBC 46.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 831: Auxiliary Files

    CLI - see Loading Auxiliary Files through CLI on page 833  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 832: 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 823.

  • Page 833: Loading Auxiliary Files Through Cli

    Click the Delete button corresponding to the file that you want deleted; a confirmation message box appears. Click OK to confirm. Reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 834: Call Progress Tones File

    (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 835 Carrier Freq [Hz]: Frequency of the carrier signal for AM tones. • Modulation Freq [Hz]: Frequency of the modulated signal for AM tones (valid range from 1 to 128 Hz). • Signal Level [-dBm]: Level of the tone for AM tones. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 836: Distinctive Ringing

    Mediant 800B Gateway & E-SBC • AM Factor [steps of 0.02]: Amplitude modulation factor (valid range from 1 to 50). Recommended values from 10 to 25. 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.
  • Page 837 An example of various ringing signals definition is shown below: [NUMBER OF DISTINCTIVE RINGING PATTERNS] Number of Ringing Patterns=3 #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 Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 838: Prerecorded Tones File

    Audition), and then combined into a single and loadable PRT file (.dat) using the latest version of AudioCodes DConvert utility (refer to the DConvert Utility User's Guide). Once created, you need to install the PRT file on the device (flash memory), using the Web interface (see 'Loading Auxiliary Files' on page 831) or CLI.

  • Page 839: Cas Files

    Each Dial Plan index must begin with a Dial Plan name enclosed in square brackets "[...]" on a new line.  Each line under the Dial Plan index defines a rule.  Empty lines are ignored. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 840: 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 831.
  • Page 841 • 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 842 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 831.

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

    The following procedure describes how to configure IP-to-Tel routing using prefix tags.  To configure IP-to-Tel routing using prefix tags: Configure a Dial Plan file with prefix tags, and then load the file to the device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 844 Mediant 800B Gateway & E-SBC 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).

  • Page 845: Obtaining Ip Destination From Dial Plan File

    The "DialPlan" string is case-sensitive. 47.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 846 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 847: 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 47-5: Enabling User Info Table Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 848: 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 849: Configuring Gw User Info Table Through Web Interface

    User Info file.  To configure the GW User Info table through the Web interface: Open the GW User Info table (Setup menu > Signaling & Media tab > Gateway folder > User Information). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 850 Mediant 800B Gateway & E-SBC Click New; the following dialog box appears: Figure 47-6: GW User Info Table - Add Dialog Box 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.

  • Page 851: Configuring Gw User Info Table Through Cli

    Web interface - see 'Loading Auxiliary Files' on page 831  ini file, using the UserInfoFileName parameter - see 'Auxiliary and Configuration File Name Parameters' on page 1067  Automatic Update mechanism, using the UserInfoFileURL parameter - see Automatic Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 852: User Information File For Sbc User Database

    Mediant 800B Gateway & E-SBC Update Mechanism To add mapping rules to the User Info file, use the following syntax: [ GW ] FORMAT PBXExtensionNum,GlobalPhoneNum,DisplayName,UserName,Password Where:  [ GW ] indicates that this part of the file is the GW User Info table ...

  • Page 853: Configuring Sbc User Info Table Through Web Interface

    Un-Register. Table 47-3: SBC User Info Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [SBCUserInfoTable_Index] Note: Each row must be configured with a unique index. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 854: Configuring Sbc User Info Table Through Cli

    Mediant 800B Gateway & E-SBC Parameter Description Local User Defines the user and is used as the Request-URI user part for the AOR in the database. [SBCUserInfoTable_LocalUser] The valid value is a string of up to 10 characters. Username Defines the username for registering the user when authentication is necessary.

  • Page 855: Configuring Sbc User Info Table In Loadable Text File

    To modify the SBC User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Below is an example of a configured User Info file: [ SBC ] FORMAT LocalUser,UserName,Password,IPGroupID Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 856: Viewing The Installed User Info File Name

    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 857: License Key

    License Key The License Key determines the device's supported features and call capacity, as ordered from your AudioCodes sales representative. You can upgrade or change your device's supported features and capacity, by purchasing and installing a new License Key that match your requirements.

  • Page 858: Installing A New License Key

     Serial Number: Device's serial number.  Board Type: AudioCodes internal identification number of the type of your device.  Remote License Server / Remote License Server IP: For more information, see Upgrading SBC Capacity Licenses by License Pool Manager Server on page 865.

  • Page 859: Installing A License Key String

    The License Key page uses color-coded icons to indicate the changes between the previous License Key and the newly loaded License Key (for more information, see Installing License Key through Web Interface on page 864). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 860: Installing A License Key File

    Mediant 800B Gateway & E-SBC Click Apply New License Key; the following message box appears: Figure 48-4: Apply New License Key Message Click Reset; the device begins to save the file to flash memory with a reset and the following progress message box appears:...
  • Page 861 Figure 48-7: Apply New License Key Message Click Reset; the device begins to save the file to flash memory with a reset and the following progress message box appears: Figure 48-8: Reset in Progress for License Key Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 862 Mediant 800B Gateway & E-SBC When installation completes, the following message box appears: Figure 48-9: Reset and Save-to-Flash Success Message Clock Close to close the message box; you are logged out of the Web interface and prompted to log in again. The features and capabilities displayed on the License Key page now reflect the newly installed License Key.
  • Page 863 HA switchover mechanism. When you click the button, the process starts and a message box is displayed indicating the installation progress: Figure 48-10: Hitless License Key Upgrade - Progress When installation completes, the following message box appears: Figure 48-11: Hitless License Upgrade Successfully Completed Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 864: Installing License Key Through Cli

    Mediant 800B Gateway & E-SBC • Non-Hitless Upgrade: Installs the License Key simultaneously on both devices where both undergo a reset and therefore, current calls are terminated. When you click the button, the process starts and the following progress message box...

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

    Manager Server The device can receive SBC capacity (session) 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 licenses from the pool to devices in the network to meet capacity demands of each device, whenever required.
  • Page 866 Mediant 800B Gateway & E-SBC an SBC license for the device, it sends it to the device. If the device's installed License Key already includes SBC capacity figures, the SBC license allocated from the pool is simply added to it (but up to the device's maximum supported capacity capabilities). For...

  • Page 867: Backing Up The License Key

    Viewing the Device's Product Key The Product Key identifies a specific purchase of your device installation for the purpose of subsequent communication with AudioCodes (e.g., for support and software upgrades). The Product Key is your chassis' serial number--"S/N(Product Key)"--which also appears on the product label affixed to the chassis.
  • Page 868 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 869: Software Upgrade Wizard

    HA state. Only the initial redundant deviceundergoes a reset to return to redundant state. 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 870 Mediant 800B Gateway & E-SBC  cmp file: copy firmware from <URL>  ini or Auxiliary file: copy <ini file or auxiliary file> from <URL>  CLI script file: copy cli-script from <URL>  HA devices: • Hitless Software Upgrade: # copy firmware from <URL and file name>...
  • Page 871 Click Load File; the device begins to install the .cmp file and a progress bar displays the status of the loading process: Figure 49-2: CMP File Loading Progress Bar When the file is loaded, a message is displayed to inform you. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 872 Mediant 800B Gateway & E-SBC If your device is in HA mode, select one of the following upgrade options: • Hitless Upgrade (default) • System Reset Upgrade See the description of these methods in the beginning of this section. Note: If you select the Hitless Upgrade option, the wizard can only be used to upload a .cmp file;...
  • Page 873 .cmp software version and other files that you may also have installed: Figure 49-5: 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 874 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

  • Page 875: Configuration File

    Loading a Configuration File The following procedure describes how to load a configuration file from a folder on your PC to the device. You can load any of the following configuration file types:  ini file Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 876 Mediant 800B Gateway & E-SBC  CLI Script file  CLI Startup Script file Warning: • When loading an ini file as described in this section, parameters not included in the ini file are restored to default settings. If you want to keep the device's current...

  • Page 877: 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 51-1: Enabling DHCP Client Functionality Click Apply. To activate the DHCP process, reset the device. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 878: 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 879: 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 880: 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 881: Ftp-Based Provisioning

    878 is that the protocol in the URL is "ftp" (instead of "http"). 51.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 882: Files Provisioned By Automatic Update

    Mediant 800B Gateway & E-SBC 51.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 883: Mac Address Placeholder In Configuration File Name

    URL address of the provisioning server it uses a placeholder for the file names which is replaced by hardcoded file names and extensions according to file type, as described in more detail below. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 884 Mediant 800B Gateway & E-SBC Note: • Unlike the parameters that define specific URLs for Auxiliary files (e.g., CptFileURL), the file template feature always retains the URLs after each automatic update process. Therefore, with the file template the device always attempts to download the files upon each automatic update process.

  • Page 885: 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: Version 7.2...

  • Page 886: Access Authentication With Http Server

    Mediant 800B Gateway & E-SBC NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost> From: sip:sipsak@<srchost> CSeq: 10 NOTIFY Call-ID: 1234@<srchost> Event: check-sync;reboot=false To enable the feature: Open the Gateway Advanced Settings page (Setup menu > Signaling & Media tab > Gateway folder > Gateway Advanced Settings).
  • Page 887 AutoCmpFileUrl or CLI command, configure system > automatic-update > auto-firmware <URL>. The device uses the same configured URL to download the .cmp file for each subsequent Automatic Update process. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 888 Mediant 800B Gateway & E-SBC You can also enable the device to run a CRC on the downloaded configuration file (ini) to determine whether the file has changed in comparison to the previously downloaded file. Depending on the CRC result, the device can install or discard the downloaded file.

  • Page 889: File Download Sequence

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

  • Page 890: Cyclic Redundancy Check On Downloaded Configuration Files

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

  • Page 891: Automatic Update Configuration Examples

    Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' Automatic Update of Call Progress Tone file: ♦ ini File: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 892: Automatic Update From Remote Servers

    Mediant 800B Gateway & E-SBC CptFileURL = 'https://www.company.com/call_progress.dat' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# call-progress-tones 'http://www.company.com/call_progress.dat' Automatic Update of ini configuration file: ♦ ini File: IniFileURL = 'https://www.company.com/config.ini' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# voice-configuration 'http://www.company.com/config.ini'...

  • Page 893: Automatic Update For Mass Deployment

    "<MAC>" in the URL, as described in 'MAC Address Placeholder in Configuration File Name' on page 883.  Device queries the provisioning server daily at 24:00 (midnight) for software, configuration and Auxiliary files.  HTTP-based provisioning server at www.company.com for storing the files. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 894 Mediant 800B Gateway & E-SBC  DNS server at 80.179.52.100 for resolving the domain name of the provisioning server.  To set up automatic provisioning for mass provisioning (example): Create a "master" configuration file template named "master_configuration.ini" or "master_startup.txt" with the following settings: •...
  • Page 895 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 Power down and then power up the device. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 896 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

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

  • Page 899: Sbc Configuration Wizard

    SBC Configuration Wizard, their new settings are used. • On some wizard pages, the availability of certain fields depends on the selected application. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 900: Starting The Sbc Configuration Wizard

    Figure 53-1: SBC Configuration Wizard - Welcome Page If desired, the SBC Configuration Wizard allows you to share usage statistics with AudioCodes in order to help us improve our software. To agree, select the 'Report usage statistics' check box, and then fill in the subsequent fields.

  • Page 901: General Setup Page

    SIP REGISTER, SUBSCRIBE and NOTIFY messages. If you selected the SIP Trunk application in Step 1, do the following: From the 'IP-PBX' drop-down list, select the IP PBX model. If the model is not listed, select Generic IP-PBX. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 902 Mediant 800B Gateway & E-SBC From the 'SIP-Trunk' drop-down list, select the SIP trunk provider. If the provider is not listed, select Generic SIP Trunk. To generate a configuration template based on the individual properties of the selected IP PBX and SIP Trunk, instead of using the existing template for the specific combination, select the 'Override template' check box.

  • Page 903: System Page

    DNS server and the IP PBX or ITSP require the use of hostnames instead of IP addresses. Select the 'Apply local DNS' check box, and then configure the following parameters: Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 904: Interfaces Page

    Mediant 800B Gateway & E-SBC ♦ 'Domain Name': Domain name to resolve into an IP address. ♦ 'First IP address': IP address of the domain name. ♦ 'Secondary IP address': Second IP address of the domain name (optional). For more information on configuring the device's DNS table, see Configuring the Internal DNS Table on page 170.

  • Page 905: Ip-Pbx Page

    IP PBX. The field is applicable only when the device is connected to a router that performs NAT.  To configure IP PBX settings: Under the IP-PBX group, configure the following: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 906 Mediant 800B Gateway & E-SBC • 'Address': Configure the IP address (or hostname) of the IP PBX. Note that for the One port: WAN network topology, when the device is assigned a public IP address, you must use the public IP address (of the Enterprise router) instead of the private address of the IP PBX, and configure the Enterprise router to forward VoIP traffic from the device to the IP PBX.

  • Page 907: Sip Trunk Page

    Under the SIP Trunk group, configure the following: • 'Address': Configures the IP address or hostname of the SIP Trunk. • 'Backup Address': (Optional) Configures the backup IP address or hostname of the SIP Trunk. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 908 Mediant 800B Gateway & E-SBC • 'SIP Domain': Configures the SIP domain name for communicating with the SIP Trunk. The domain name is used in the following SIP message headers: ♦ Outbound calls: Request-URI and To headers ♦ Inbound calls: From header •...

  • Page 909: Number Manipulation Page

    'Password': Password for communication with ARM. Click Next; the Remote Users (FEU) page appears (see Remote Users Page on page 910). The example below changes the number "+15033311432" to "03311432":  Prefix: "+1503" Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 910: Remote Users Page

    Mediant 800B Gateway & E-SBC  Remove:"4"  Add: "0" 53.8 Remote Users Page The Remote Users (FEU) wizard page configures the remote users settings. Note: This page is applicable only to IP PBXs that support such configuration. Figure 53-8: SBC Configuration Wizard - Remote Users Page ...

  • Page 911: Summary Page

    You can later load the file to the device (see Loading an ini File to the Device on page 875). Click Next; the Congratulations page appears (see Congratulations Page on page 912). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 912: Congratulations Page

    Mediant 800B Gateway & E-SBC 53.10 Congratulations Page The Congratulations wizard page is the last wizard page and allows you to complete configuration. Figure 53-10: SBC Configuration Wizard - Congratulations Page  To complete the SBC Configuration Wizard: Click Apply & Reset to apply configuration to the device or click Save INI File to save configuration as an ini file on your PC.

  • Page 913: Restoring Factory Defaults

    IP Interfaces table (see 'Configuring IP Network Interfaces' on page 146), 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 914: 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 915: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 917: System Status

    Product Key, which identifies the specific device purchase. The Product Key also appears on the product label that is affixed to the chassis, as "S/N(Product Key)". For more information, see Viewing the Device's Product Key on page 867. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 918: Viewing Device Status On Monitor Page

    Mediant 800B Gateway & E-SBC Parameter Description Board Type Product name of the device. Device Up Time Duration that the device has been up and running since the last reset. The duration is displayed in the following format: dd:hh:mm:ss:100th of a second Device Administrative State Administrative status ("Unlocked"...
  • Page 919 The displayed number and type of telephony interfaces depends on the ordered hardware configuration. • For a description of the Monitor page when the device is in High Availability (HA) mode, see HA Status Display on Monitor Web Page on page 805. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 920 Mediant 800B Gateway & E-SBC Table 55-1: Description of Graphical Display of Device Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green = No alarms  Red = Critical alarm ...

  • Page 921: Viewing Port Information

    From the shortcut menu, choose Port Status. • For digital ports: The Trunks & Channel Status page appears (see Viewing Trunk and Channel Status on page 955). Click a channel; the following page appears with the Basic tab selected: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 922 Mediant 800B Gateway & E-SBC • For analog ports: The following page appears with the Basic tab selected: Figure 55-3: Viewing Analog Port Status To view additional channel information, click the required tab - SIP, RTP/RTCP, and Voice Settings. Table 55-2: Port Status Description...
  • Page 923 See above. Endpoint ID ID of endpoint:  "Not Available" Call Duration Call duration (in seconds) from when call was established. Call Type Type of call:  "Voice": Voice call  "Fax": Fax call Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 924 Mediant 800B Gateway & E-SBC Field Description Call Destination IP address of called party. Coder Coder type used for the call. Last Current Disconnect Duration Duration of the disconnect signal. Note: The parameter is applicable only to analog interfaces. Line Current Line current (in mA).
  • Page 925 Displays the volume gain (in dB). Voice Volume Displays the voice volume gain (in dB). DTMF Transport Type Displays the DTMF transport type. Enabled Detectors Displays enabled detectors (e.g., AMD). Fax Transport Type Displays the fax transport type. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 926 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

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

  • Page 929: 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 Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 930: Viewing History Alarms

    Mediant 800B Gateway & E-SBC 57.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 931 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 932 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

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

  • Page 935: 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 59-1: Additional Graph Functionality for Trunk Utilization Button Description Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 936: 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 937 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 938: Viewing Average Call Duration

    Mediant 800B Gateway & E-SBC 59.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 939: 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 940 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 941 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 942 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 943: 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 944 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 945: 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 946 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 947: Viewing Sbc Registered Users

    You can view the status of Proxy Sets that are used in your call routing topology. Proxy Sets that are not associated with any routing rule are not displayed. To configure proxy Sets, see Configuring Proxy Sets on page 380. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 948 Mediant 800B Gateway & E-SBC  To view Proxy Set status:  Open the Active Proxy Set Status page (Monitor menu > Monitor tab > VoIP Status folder > Proxy Sets Status). Figure 60-3: Viewing Proxy Sets Status Table 60-3: Proxy Sets Status Table Description...

  • Page 949: Viewing Registration Status

    Trunk Group Settings table (see Configuring Trunk Group Settings on page 519) or using the TrunkGroupSettings ini file parameter.  To view registration status:  Open the Registration Status table (Monitor menu > Monitor tab > VoIP Status folder > Registration Status). Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 950 Mediant 800B Gateway & E-SBC Table 60-4: Registration Status Table Description Parameter Description Registered Per Gateway Registration status of the device as one entity:  "YES"  "NO" Note: The parameter is applicable only to the Gateway application. Ports Registration Status...

  • Page 951: Viewing Ip Connectivity

    'Alternative Routing Based on IP Connectivity' on page 542. Quality Status Displays the QoS (according to packet loss and delay) of the destination:  "Unknown": Recent quality information isn't available.  "OK" Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 952: Viewing Gateway Cdr History

    Mediant 800B Gateway & E-SBC Column Name Description  "Poor" Note:  The parameter is applicable only if the parameter 'Alt Routing Tel to IP Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).  The parameter is reset if two minutes elapse without a call to the destination.

  • Page 953: Viewing Sbc Cdr History

    4,096 CDRs. If the table reaches maximum capacity of entries and a new CDR is added, the last CDR entry is removed from the table. Note: If the device is reset, all CDRs are deleted from memory and from the table. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 954 Mediant 800B Gateway & E-SBC  To view SBC CDR history:  Web: Open the SBC CDR History table (Monitor menu > Monitor tab > VoIP Status folder > SBC CDR History). Figure 60-6: SBC CDR History Table  CLI: •...

  • Page 955: Viewing Pstn Status

    Table 61-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 956: 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 61-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 957 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 61-1: NFAS Group & D-Channel Status Page Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 958 Mediant 800B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10632...

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

  • Page 960: Viewing Static Routes Status

    Mediant 800B Gateway & E-SBC Table 62-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 961: 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 962 Mediant 800B Gateway & E-SBC the remote endpoint. The following table lists the supported voice metrics (parameters) published in the RTCP XR. Table 63-1: RTCP XR Published VoIP Metrics Metric Parameter Description CallID Call ID - call ID from the SIP dialog...
  • Page 963 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 964 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 965 RTCP XR reports. • (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 966: 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 63-2: Configuring RTCP XR Collection Server Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
  • Page 967 EPTyp Endpoint type: "SBC" String SIPMethod SIP message type String (up to 10 characters) Unique ID of call String (up to 50 SIPCallId characters) SessionId Unique Session ID String (up to 10 characters) Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 968 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 969 "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 970 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 971: 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 972 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 973 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 974: 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 975 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 976: Cdr Fields For Gateway Application

    Mediant 800B Gateway & E-SBC 63.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 977 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 978 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 979 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 980 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 981 "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 982 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 983: Cdr Fields For Gateway Local Storage

    Table 63-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 984 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 985  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 986: 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 987 [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 988 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 989  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 990: Customizing Cdrs For Sbc Calls

    Mediant 800B Gateway & E-SBC 63.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 991 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 992 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 993 [0] Standard = (Default) For standard RADIUS Attributes. [SBCCDRFormat_RadiusType]  [1] Vendor Specific = For vendor-specific RADIUS Attributes (VSA). Note: The parameter is applicable only for RADIUS accounting (i.e., 'CDR Type' parameter configured to RADIUS SBC). Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 994: Configuring Cdr Reporting

    Mediant 800B Gateway & E-SBC Parameter Description RADIUS Attribute ID Defines an ID for the RADIUS Attribute. For VSAs, this represents the VSA ID; for standard Attributes, this represents the Attribute ID radius-id (first byte of the Attribute). [SBCCDRFormat_RadiusID] The valid value is 0 to 255 (one byte). The default is 0.

  • Page 995: Storing Cdrs On The Device

    CSV file viewed in a text editor (Notepad): Figure 63-11: CSV File of CDRs in Text Editor (Notepad) To view the CDR column headers corresponding to the CDR data in the CSV file, run the following CLI command: Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 996 Mediant 800B Gateway & E-SBC  SBC CDRs: (config-system)# cdr (cdr)# cdr-format show-title local-storage-sbc session id,report type,call duration, call end time, call connect time,call start time, call originator, termination reason, call id, srce uri, dest uri  Gateway CDRs: (config-system)# cdr (cdr)# cdr-format show-title local-storage-gw You can do the following with locally saved CDR files (*.csv), through the CLI (root menu):...
  • Page 997 For customizing CDR fields for SBC calls, see Customizing CDRs for SBC Calls on page 990. • For customizing CDR fields for Gateway calls, see Customizing CDRs for Gateway Calls on page 986. Version 7.2 Mediant 800B Gateway & E-SBC...

  • Page 998: Configuring Radius Accounting

    Mediant 800B Gateway & E-SBC 63.3 Configuring RADIUS Accounting The device can send accounting data of SIP calls as call detail records (CDR) to a RADIUS Accounting server. CDR-based accounting messages can be sent upon call release, call connection and release, or call setup and release. This section lists the CDR attributes for RADIUS accounting.
  • Page 999 RADIUS accounting messages are sent to the RADIUS accounting server. • From the 'AAA Indications' drop-down list (AAAIndications), select whether you want Authentication, Authorization and Accounting (AAA) indications. Version 7.2 Mediant 800B Gateway & E-SBC...
  • Page 1000 Mediant 800B Gateway & E-SBC For a detailed description of the parameters, see 'RADIUS Parameters' on page 1322. Figure 63-16: Configuring RADIUS Accounting Click Apply, and then reset the device with a save-to-flash for your settings to take effect. The table below lists the RADIUS Accounting CDR attributes included in the communication packets transmitted between the device and a RADIUS server.
  • Page 1001 Terminator of the String call-terminator=yes Stop call:  "yes": Call terminated by the Tel side (Gateway) or outgoing leg (SBC)  "no": Call terminated by the IP side (Gateway) or incoming leg Version 7.2 1001 Mediant 800B Gateway & E-SBC...
  • Page 1002 Mediant 800B Gateway & E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID (SBC) terminator Terminator of the String terminator=originate Stop call:  "answer": Call originated from the IP side (Gateway) or incoming leg (SBC) ...
  • Page 1003 = 1 acct-input-packets = 122 acct-output-packets = 220 called-station-id = 201 calling-station-id = 202 // Accounting non-standard parameters: (4923 33) h323-gw-id = (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 Version 7.2 1003 Mediant 800B Gateway & E-SBC...

  • Page 1004: Querying Device Channel Resources Using Sip Options

    Mediant 800B Gateway & E-SBC 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 63.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.

  • Page 1005: Diagnostics

    Part XI Diagnostics...

  • Page 1007: 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 1007 Mediant 800B Gateway & E-SBC...
  • Page 1008 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 1018).
  • Page 1009 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 1009 Mediant 800B Gateway & E-SBC...
  • Page 1010 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 1011: 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 1011 Mediant 800B Gateway & E-SBC...

  • Page 1012: Configuring Syslog

    Mediant 800B Gateway & E-SBC Wireshark-like filtering expressions for your IP trace. The following Wireshark-like expressions are supported: Table 64-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...

Table of Contents