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

AudioCodes Mediant 800B User Manual

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

Advertisement

Quick Links

Download this manual See also: User Manual, Quick Manual
User's Manual
Mediant 800B
Media Gateway & Enterprise Session Border
Controller (E-SBC)
Version 7.0

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 800B

Summary of Contents for AudioCodes Mediant 800B

  • Page 1 User's Manual Mediant 800B Media Gateway & Enterprise Session Border Controller (E-SBC) Version 7.0...

  • Page 3: Table Of Contents

    Configuring Web Session and Access Settings ............75 Web Login Authentication using Smart Cards ............75 Configuring Web and Telnet Access List ............... 76 CLI-Based Management ..................79 Getting Familiar with CLI ..................79 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 4 Mediant 800B Gateway and E- SBC 7.1.1 Understanding Configuration Modes ............... 79 7.1.2 Using CLI Shortcuts ....................80 7.1.3 Common CLI Commands ..................81 7.1.4 Configuring Tables through CLI ................82 7.1.5 Understanding CLI Error Messages ................ 83 Enabling CLI ......................84 7.2.1...
  • Page 5 14.2 Fax and Modem Capabilities ................180 14.2.1 Fax/Modem Operating Modes ................181 14.2.2 Fax/Modem Transport Modes ................181 14.2.3 V.34 Fax Support ....................189 14.2.4 V.150.1 Modem Relay ...................192 14.2.5 Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay ....193 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 6 Mediant 800B Gateway and E- SBC 14.2.6 V.152 Support ......................193 14.3 Configuring RTP/RTCP Settings ................194 14.3.1 Configuring the Dynamic Jitter Buffer ..............194 14.3.2 Comfort Noise Generation ..................195 14.3.3 Configuring DTMF Transport Types ..............196 14.3.4 Configuring RFC 2833 Payload ................197 14.3.5 Configuring RTP Base UDP Port ................198...
  • Page 7 15.9 Enhanced 9-1-1 Support for Lync Server ............. 297 15.9.1 About E9-1-1 Services ...................297 15.9.2 Microsoft Lync Server and E9-1-1 .................298 15.9.3 AudioCodes ELIN Device for Lync Server E9-1-1 Calls to PSTN ......302 15.9.4 Configuring AudioCodes ELIN Device ..............307 16 Quality of Experience ..................311 16.1 Reporting Voice Quality of Experience to SEM ............
  • Page 8 Mediant 800B Gateway and E- SBC 19 Coders and Profiles ..................387 19.1 Configuring Default Coders .................. 387 19.2 Configuring Coder Groups ................... 390 19.3 Configuring Tel Profile ..................392 19.4 Configuring IP Profiles ..................396 Gateway Application .....................431 20 Introduction ..................... 433 20.1 Call Processing Summary ..................
  • Page 9 26.11 Emergency E911 Phone Number Services ............547 26.11.1 FXS Device Emulating PSAP using DID Loop-Start Lines ........547 26.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines .........................550 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 10 Mediant 800B Gateway and E- SBC 26.11.3 Pre-empting Existing Calls for E911 IP-to-Tel Calls ..........553 26.12 Multilevel Precedence and Preemption ..............554 26.12.1 MLPP Preemption Events in SIP Reason Header ..........556 26.12.2 Precedence Ring Tone ..................557 26.13 Denial of Collect Calls ..................558 26.14 Configuring Multi-Line Extensions and Supplementary Services ......
  • Page 11 33.2 Configuring Message Condition Rules ..............652 33.3 Configuring SBC IP-to-IP Routing ................ 653 33.4 Configuring SIP Response Codes for Alternative Routing Reasons ....664 33.5 Configuring SBC Routing Policy Rules ..............666 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 12 Mediant 800B Gateway and E- SBC 34 SBC Manipulations ..................671 34.1 Configuring IP-to-IP Inbound Manipulations ............673 34.2 Configuring IP-to-IP Outbound Manipulations ............677 35 Advanced SBC Features ................. 683 35.1 Configuring Call Preemption for SBC Emergency Calls ........683 35.2 Emergency Call Routing using LDAP to Obtain ELIN ..........
  • Page 13 44.5 Backing Up and Loading Configuration File ............775 45 Automatic Provisioning .................. 777 45.1 Automatic Configuration Methods ................ 777 45.1.1 DHCP-based Provisioning ..................777 45.1.2 HTTP-based Provisioning ..................779 45.1.3 FTP- based Provisioning ..................780 45.1.4 Provisioning using AudioCodes EMS ..............780 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 14 Mediant 800B Gateway and E- SBC 45.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 781 45.2.1 Files Provisioned by Automatic Update ..............781 45.2.2 File Location for Automatic Update ...............781 45.2.3 Triggers for Automatic Update ................782 45.2.4 Access Authentication with HTTP Server ..............783 45.2.5 Querying Provisioning Server for Updated Files ...........783...
  • Page 15 58.4 Configuring DTMF Tones for Test Calls ............... 894 58.5 Configuring Basic Test Call .................. 894 58.6 Configuring SBC Test Call with External Proxy ........... 895 58.7 Test Call Configuration Examples ................ 897 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 16 Mediant 800B Gateway and E- SBC 59 Pinging a Remote Host or IP Address ............901 Appendix ........................903 60 Dialing Plan Notation for Routing and Manipulation ........905 61 Configuration Parameters Reference ............909 61.1 Management Parameters ..................909 61.1.1 General Parameters ....................909 61.1.2 Web Parameters ....................909...
  • Page 17 61.14.6 HTTP Proxy Parameters ..................1175 62 SBC and DSP Channel Capacity ..............1177 62.1 Signaling-Media Sessions & User Registrations ..........1177 62.2 Channel Capacity and Capabilities ..............1178 63 Technical Specifications ................1183 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 18 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 19: Weee Eu Directive

    This document is subject to change without notice. Date Published: January-11-2016 Trademarks AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNOM and CloudBond 365 are trademarks or registered trademarks of AudioCodes Limited All other products or trademarks are property of their respective owners.

  • Page 20: Related Documentation

    Mediant 800B Gateway and E- SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 800B Gateway and E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP User's Guide SBC Design Guide...
  • Page 21 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
  • Page 22 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 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.

  • Page 23: Introduction

    Product Overview AudioCodes' Mediant 800B Gateway and E-SBC (hereafter referred to as device) is a member of AudioCodes family of Enterprise Session Border Controllers (E-SBC), enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks.

  • Page 24: Typographical Conventions

    Mediant 800B Gateway and E- SBC  Up to 8 Basic Rate Interface (BRI) ports (supporting up to 16 voice channels). This is used for connecting ISDN terminal equipment such as ISDN telephones. It supports various ISDN BRI protocols such as ETSI 5ESS and QSIG over BRI.

  • Page 25: Getting Familiar With Configuration Concepts And Terminology

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

  • Page 29: Gateway Application

    The Media Realm can be associated with the SIP entity, by assigning the Media Realm to the IP Group of the SIP entity, or by assigning it to the SIP Interface associated with the SIP entity. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 30 Mediant 800B Gateway and E- SBC Configuration Terms Description SRDs The SRD is a logical representation of your entire VoIP network. The SRD is in effect, the foundation of your configuration to which all other previously mentioned configuration entities are associated.
  • Page 31 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. Figure 1-3: Gateway Configuration Terminology for Call Processing Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 32 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 33: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 35: Introduction

    User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 36 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 37: Default Oamp Ip Address

    Table 3-1: Default VoIP LAN IP Address for OAMP IP Address Value Application Type OAMP + Media + Control IP Address 192.168.0.2 Prefix Length 255.255.255.0 (24) Default Gateway 192.168.0.1 Underlying Device vlan 1 Interface Name O+M+C Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 38 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 39: Configuring Voip Lan Interface For Oamp

    Ethernet cable. Change the IP address and subnet mask of your computer to correspond with the default OAMP IP address and subnet mask of the device. Access the Web interface: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 40 Mediant 800B Gateway and E- SBC On your computer, start a Web browser and in the URL address field, enter the default IP address of the device; the Web interface's Web Login screen appears: Figure 4-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin").

  • Page 41: Cli

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

  • Page 43: Management Tools

    Part II Management Tools...

  • Page 45: Introduction

    Web, CLI, and ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 909. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 46 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 47: Web-Based Management

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

  • Page 48: Accessing The Web Interface

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

  • Page 49: Areas Of The Gui

    This is where configuration is done. For more information, see ''Working with Configuration Pages'' on page 53. 6.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 50: Navigation Tree

    Mediant 800B Gateway and E- SBC Table 6-2: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see ''Saving Configuration'' on page 732). Note: This icon is grayed out when not applicable to the currently opened page.
  • Page 51 The expanded view displays all the menus pertaining to the selected configuration tab; the reduced view displays only commonly used menus.  To display a reduced menu tree, select the Basic option (default). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 52 Mediant 800B Gateway and E- SBC  To display all menus and submenus, select the Advanced option. Figure 6-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 6.1.5.2 Showing / Hiding the Navigation Pane You can hide the Navigation pane to provide more space for elements displayed in the Work pane.

  • Page 53: Working With Configuration

     Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 54 Mediant 800B Gateway and E- SBC The figure below shows an example of a page displaying basic parameters only. If you click the Advanced Parameter List button (shown below), the page will also display the advanced parameters. Figure 6-6: Toggling between Basic and Advanced View Notes: •...
  • Page 55 Thus, to ensure parameter changes (whether on-the-fly or not) are retained, save ('burn') them to the device's non-volatile memory, i.e., flash (see ''Saving Configuration'' on page 732). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 56: Working With Tables

    Mediant 800B Gateway and E- SBC If you enter an invalid value (e.g., not in the range of permitted values) and then click Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts to its previous value and is highlighted in red, as shown in the...
  • Page 57 'Index' column; otherwise, the button is grayed out. For sorting tables, see ''Sorting Tables by Column'' on page 59.  The button appears only in certain tables. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 58 Mediant 800B Gateway and E- SBC Button Name Moves a selected row one index up. The index number of the row changes according to its new position in the table. The row that previously occupied the index row and all rows below it are moved one index down in the table.
  • Page 59 Index column in ascending order (e.g., 1, 2, and 3), you can sort the rows by Index column in descending order (e.g., 3, 2, and 1). By default, most tables are sorted by Index column in ascending order. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 60: Searching For Configuration Parameters

    Mediant 800B Gateway and E- SBC  To sort table rows by column: Click the heading name of the column that you want to sort the table rows by; the up- down arrows appear alongside the heading name and the up button is bolded (see...
  • Page 61 Table 6-6: Search Description Item # Description Search field for entering search key and Search button for activating the search process. Search results listed in Navigation pane. Found parameter, highlighted on relevant Web page Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 62: Creating A Login Welcome Message

    Mediant 800B Gateway and E- SBC 6.1.9 Creating a Login Welcome Message You can create a Welcome message box that is displayed on the Web Login page. The figure below displays an example of a Welcome message: Figure 6-15: User-Defined Web Welcome Message after Login To enable and create a Welcome message, use the WelcomeMessage table ini file parameter, as described in the table below.

  • Page 63: Getting Help

    Instead of clicking the Help button for each page you open, you can open it once for a page and then simply leave it open. Each time you open a different page, the Help topic pertaining to that page is automatically displayed. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 64: Logging Off The Web Interface

    Mediant 800B Gateway and E- SBC 6.1.11 Logging Off the Web Interface The following procedure describes how to log off the Web interface.  To log off the Web interface: On the toolbar, click the Log Off icon; the following confirmation message box...
  • Page 65 Module slot number. Module interface type (e.g., FXS, FXO, and DIGITAL). Module status icon:  (green): Module has been inserted or is correctly configured  (gray): Module was removed and "Reserved" is displayed Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 66 Mediant 800B Gateway and E- SBC Item # Description  (red): Module failure and "Failure" is displayed Port (trunk or channel) status icon. Icon Trunk Description Channel Description (Digital Module) (Analog Modules) Disable: Trunk not Idle: Channel is currently on-hook...

  • Page 67: Assigning A Port Name

    Master user. Note: At least one Security Administrator user must exits. Master Read / write privileges for all pages. Can create all user Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 68: Basic User Accounts Configuration

    Mediant 800B Gateway and E- SBC Numeric User Level Representation in Privileges RADIUS types, including additional Master users and Security Administrators. It can delete all users except the last Security Administrator. Administrator Read / write privileges for all pages, except security- related pages (read-only).
  • Page 69 (as shown below). If you are logged in with the second user account, only the details of this user account are displayed. Figure 6-19: WEB User Accounts Page (for Users with 'Security Administrator' Privileges) To change the username of an account: Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 70: Advanced User Accounts Configuration

    Mediant 800B Gateway and E- SBC In the 'User Name' field, enter the new user name. Click Change User Name; if you are currently logged in to the Web interface with this account, the 'Web Login' dialog box appears. Log in with your new user name.
  • Page 71 Note: Each row must be configured with a unique index. Username Defines the Web user's username. user-name The valid value is a string of up to 40 alphanumeric characters, including the period ".", underscore "_", and hyphen "-" signs. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 72 Mediant 800B Gateway and E- SBC Parameter Description Password Defines the Web user's password. password The valid value is a string of 8 to 40 ASCII characters, which must adhere to the following guidelines:  Include at least eight characters.
  • Page 73 Master users can add, edit, and delete Security Administrators (but cannot delete the last Security Administrator).  Only Security Administrator and Master users can add, edit, and delete Administrator and Monitor users. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 74: Displaying Login Information Upon Login

    Mediant 800B Gateway and E- SBC Displaying Login Information upon Login The device can display login information immediately upon Web login.  To enable display of user login information upon a successful login: Open the Web Security Settings page (Configuration tab > System menu >...

  • Page 75: Configuring Web Session And Access Settings

    (and other information, if required) from the CAC. The user attempting to access the device is only required to provide the login password. Typically, a TLS connection is established between the CAC and the device’s Web interface, and a RADIUS server is implemented to Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 76: Configuring Web And Telnet Access List

    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 77 • Delete your PC's IP address last from the 'Web & Telnet Access List page. If it is deleted before the last, subsequent access to the device from your PC is denied. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 78 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 79: Cli-Based Management

    ''Configuring Web User Accounts'' on page 67. • The default password for accessing the Enable mode is "Admin" (case-sensitive). To change this password, use the CLIPrivPass ini file parameter. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 80: Using Cli Shortcuts

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

  • Page 81: Common Cli Commands

    Displays a list of previously run commands. history list Displays the available command list of the current command-set. | <filter> Applied to a command output. The filter should be typed after the command with a pipe mark (|). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 82: Configuring Tables Through Cli

    Mediant 800B Gateway and E- SBC Command Description Supported filters:  include <word> – filter (print) lines which contain <word>  exclude <word> – filter lines which does not contain <word>  grep <options> - filter lines according to grep common Unix utility options ...

  • Page 83: Understanding Cli Error Messages

    Use "?" to determine your error.  "Incomplete command" message: You may not have entered all of the pertinent information required to make the command valid. Use "?" to determine your error. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 84: Enabling Cli

    Mediant 800B Gateway and E- SBC Enabling CLI By default, access to the device's CLI through Telnet and SSH is disabled. This section describes how to enable these protocols. 7.2.1 Enabling Telnet for CLI The following procedure describes how to enable Telnet. You can enable a secured Telnet that uses Secure Socket Layer (SSL) where information is not transmitted in the clear.
  • Page 85 For additional security, you can set the 'Require Public Key' to Enable. This ensures that SSH access is only possible by using the RSA key and not by using user name and password. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 86: Configuring Maximum Telnet/Ssh Sessions

    Mediant 800B Gateway and E- SBC Configure the other SSH parameters as required. For a description of these parameters, see ''SSH Parameters'' on page 950. Click Submit. Start the PuTTY Configuration program, and then do the following: In the 'Category' tree, drill down to Connection, then SSH, and then Auth; the 'Options controlling SSH authentication' pane appears.

  • Page 87: Establishing A Cli Session

    # show users console Admin local 0d00h03m15s telnet John 10.4.2.1 0d01h03m47s [2]* ssh Alex 192.168.121.234 12d00h02m34s The current session from which this show command was run is displayed with an asterisk (*). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 88: Terminating A User's Cli Session

    Mediant 800B Gateway and E- SBC Note: The device can display management sessions of up to 24 hours. After this time, the duration counter is reset. 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.

  • Page 89: Snmp-Based Management

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

  • Page 90: Configuring Snmp Community Strings

    Mediant 800B Gateway and E- SBC Configuring SNMP Community Strings The SNMP Community String page lets you configure up to five read-only and up to five read-write SNMP community strings and to configure the community string that is used for sending traps.
  • Page 91  [SNMPTrapCommunityString] Upper- and lower-case letters (a to z, and A to Z)  Numbers (0 to 9)  Hyphen (-)  Underline (_) For example, "Trap-comm_string1". The default is "trapuser". Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 92: Configuring Snmp Trap Destinations

    Mediant 800B Gateway and E- SBC Configuring SNMP Trap Destinations The SNMP Trap Destinations table lets you to configure up to five SNMP trap managers. You can associate a trap destination with SNMPv2 users and specific SNMPv3 users. Associating a trap destination with SNMPv3 users sends encrypted and authenticated traps to the SNMPv3 destination.

  • Page 93: Configuring Snmp Trusted Managers

    Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address. Define an IP address in dotted-decimal notation. Click Submit, and then save ("burn") your settings to flash memory. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 94: Configuring Snmp V3 Users

    Mediant 800B Gateway and E- SBC Configuring SNMP V3 Users The SNMPv3 Users table lets you configure up to 10 SNMP v3 users for authentication and privacy. The following procedure describes how to configure SNMP v3 users through the Web interface.
  • Page 95 Group The group with which the SNMP v3 user is associated.  group [0] Read-Only (default)  [1] Read-Write [SNMPUsers_Group]  [2] Trap Note: All groups can be used to send traps. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 96 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 97: Ini File-Based Management

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

  • Page 99: General Ini File Formatting Rules

    Creating a new ini file that includes only updated configuration: Open a text file editor such as Notepad. Add only the required parameters and their settings. Save the file with the ini file extension name (e.g., myconfiguration.ini). Version 7.0 Mediant 800B Gateway and E- SBC...

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

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

  • Page 102: Ini Viewer And Editor Utility

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

  • Page 103: General System Settings

    Part III General System Settings...

  • Page 105: Configuring Ssl/Tls Certificates

    (CSR)  Trusted root certificate authority (CA) store (for validating certificates) When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 106 Mediant 800B Gateway and E- SBC  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for TLS ('Transport Type' parameter is set to TLS), the TLS Context assigned to the Proxy Set is used.
  • Page 107 1.1 and TLS 1.2 (excludes SSL 3.0). Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format). ciphers-server For valid values, refer to URL [TLSContexts_ServerCipherString] http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 108 Mediant 800B Gateway and E- SBC Parameter Description For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS). The only ciphers available are RC4 and DES, and the cipher bit strength is limited to 56 bits.

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

    Fill in the rest of the request fields according to your security provider's instructions. Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-2: Certificate Signing Request Group Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 110 Mediant 800B Gateway and E- SBC Copy the text and send it to your security provider (CA) to sign this request. When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below:...

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

    Open the TLS Contexts page again, select the TLS Context index row, and then verify that under the Certificate Information group, the 'Private key' field displays "OK"; otherwise, consult your security administrator. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 112: Generating Private Keys For Tls Contexts

    Mediant 800B Gateway and E- SBC 10.4 Generating Private Keys for TLS Contexts The device can generate the private key for a TLS Context, as described in the following procedure. The private key can be generated for CSR or self-signed certificates.

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

    Figure 10-7: Generate new private key and self-signed certificate Group Click Generate Self-Signed Certificate; a message appears (after a few seconds) displaying the new subject name. Save the configuration with a device reset for the new certificate to take effect. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC 10.6 Importing Certificates and Certificate Chain into Trusted Certificate Store The device provides its own Trusted Root Certificate Store. This lets you manage certificate trust. You can add up to 20 certificates to the store per TLS Context (but this may be less depending on certificate file size).
  • Page 115 Save certificates to a file 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.0 Mediant 800B Gateway and E- SBC...

  • Page 116: Configuring Mutual Tls Authentication

    Mediant 800B Gateway and E- SBC 10.7 Configuring Mutual TLS Authentication This section describes how to configure mutual (two-way) TLS authentication. 10.7.1 TLS for SIP Clients When Secure SIP (SIPS) is implemented using TLS, it is sometimes required to use two- way (mutual) authentication between the device and a SIP user agent (client).
  • Page 117 HTTPSRootFileName ini file parameter. • You can enable the device to check whether a peer's certificate has been revoked by an OCSP server per TLS Context (see ''Configuring TLS Certificate Contexts'' on page 105). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 118: Configuring Tls Server Certificate Expiry Check

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

  • Page 119: Date And Time

    Open the Application Settings page (Configuration tab > System menu > Application Settings), and then scroll down to the 'NTP Settings' group: Figure 11-2: NTP Authentication Parameters on Application Settings Page Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 120 Mediant 800B Gateway and E- SBC Configure NTP message authentication: • 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.

  • Page 121: Configuring Date And Time Manually

    NTP server. • After performing a hardware reset, the date and time are returned to default values and thus, you should subsequently update the date and time. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 122: Configuring The Time Zone

    Mediant 800B Gateway and E- SBC 11.3 Configuring the Time Zone You can configure the time zone in which the device is deployed. This is referred to as the Coordinated Universal Time (UTC) time offset and defines how many hours the device is from Greenwich Mean Time (GMT).
  • Page 123 If the current date falls within the DST period, verify that it has been successful applied to the device's current date and time. You can view the device's date and time in the 'UTC Time' read-only field. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 124 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 125: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 127: Network

    You can also configure it through ini file (PhysicalPortsTable) or CLI (configure voip > physical-port).  To configure the physical Ethernet ports: Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 128 Mediant 800B Gateway and E- SBC Select a port that you want to configure by clicking its table row, and then clicking Edit; the following dialog box appears: Figure 12-1: Physical Ports Settings Table - Edit Row Dialog Box Configure the port according to the parameters described in the table below.

  • Page 129: Configuring Ethernet Port Groups

    Configuring Physical Ethernet Ports on page 127. The following procedure describes how to configure Ethernet Groups through the Web interface. You can also configure it through ini file (EtherGroupTable) or CLI (configure voip > ether-group). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 130 Mediant 800B Gateway and E- SBC Notes: • Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group. To remove the port, either set the 'Member' field to None or to a different port.
  • Page 131 Note: Before you can re-assign a port to a different Ethernet Group, [EtherGroupTable_Member2] you must first remove the port from its current Ethernet Group. To remove the port, either set this field to None or to a different port. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 132: Configuring Underlying Ethernet Devices

    Mediant 800B Gateway and E- SBC 12.3 Configuring Underlying Ethernet Devices The Ethernet Device table lets you configure Ethernet Devices. An Ethernet Device represents a Layer-2 bridging device and is assigned a VLAN ID and an Ethernet Port Group. Multiple Ethernet Devices can be associated with the same Ethernet Group.
  • Page 133 Interface table ('Underlying Device' field - see ''Configuring IP [DeviceTable_DeviceName] Network Interfaces'' on page 135) and/or with a static route in the Static Route table ('Device Name' field - see ''Configuring Static IP Routing'' on page 143). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 134 Mediant 800B Gateway and E- SBC Parameter Description Tagging Defines VLAN tagging per Ethernet Device.  tagging [0] Untagged = (Default of pre-configured Ethernet Device) The Ethernet Device accepts untagged packets as well as [DeviceTable_Tagging] packets with the same VLAN ID as configured for the Ethernet Device.

  • Page 135: Configuring Ip Network Interfaces

    HA and the Maintenance interface, see Configuring High Availability on page 710.  IP address (IPv4 and IPv6) and subnet mask (prefix length)  For configuring Quality of Service (QoS), see ''Configuring the QoS Settings'' on page 146. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 136 Mediant 800B Gateway and E- SBC  Default Gateway: Traffic from this interface destined to a subnet that does not meet any of the routing rules (local or static) are forwarded to this gateway  Primary and secondary domain name server (DNS) addresses (optional) ...
  • Page 137 8 (i.e., 11111111 00000000 00000000 00000000) and a subnet mask of 255.255.255.252 is represented by a prefix length of 30 (i.e., 11111111 11111111 11111111 11111100). The prefix length is a Classless Inter-Domain Routing (CIDR) style Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 138: Assigning Ntp Services To Application Types

    Mediant 800B Gateway and E- SBC Parameter Description presentation of a dotted-decimal subnet notation. The CIDR-style presentation is the latest method for interpretation of IP addresses. Specifically, instead of using eight-bit address blocks, it uses the variable-length subnet masking technique to allow allocation on arbitrary-length prefixes.

  • Page 139: Networking Configuration Examples

    Table 12-5: Example of Single VoIP Interface in Interface Table Application Interface Prefix Default Underlying Interface Index IP Address Type Mode Length Gateway Device Name OAMP, IPv4 192.168.0.2 192.168.0.1 myInterface Media & Control Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 140 Mediant 800B Gateway and E- SBC Static Route table: Two routes are configured for directing traffic for subnet 201.201.0.0/16 to 192.168.11.10, and all traffic for subnet 202.202.0.0/16 to 192.168.11.1: Table 12-6: Example of Static Route Table Destination Prefix Length Gateway 201.201.0.0...
  • Page 141 For Control Service class, the default DiffServ value is set to 40 ♦ For Gold Service class, the default DiffServ value is set to 26 ♦ For Bronze Service class, the default DiffServ value is set to 10 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 142 Mediant 800B Gateway and E- SBC 12.4.3.4 VoIP Interfaces with Multiple Default Gateways Below is a configuration example using default gateways per IP network interface. In this example, the default gateway for OAMP is 192.168.0.1 and for Media and Control it is 200.200.85.1.

  • Page 143: Configuring Static Ip Routes

    Configure a static route according to the parameters described in the table below. Click Add, and then reset the device with a burn-to-flash for your settings to take effect. Note: You can delete only static routing rules that are inactive. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 144: Configuration Example Of Static Ip Routes

    Mediant 800B Gateway and E- SBC Table 12-13: Static Route Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [StaticRouteTable_Index] The valid value is 0 to 29. Note: Each row must be configured with a unique index.

  • Page 145: Troubleshooting The Routing Table

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

  • Page 146: Configuring Quality Of Service

    Mediant 800B Gateway and E- SBC Note: If a static route is required to access OAMP applications (for remote management, for example) and the route is not configured correctly, the route is not added and the device is not accessible remotely. To restore connectivity, the device must be accessed locally from the OAMP subnet and the required routes be configured.
  • Page 147 Note: Each row must be configured with a unique index. Differentiated Services Defines a DiffServ value. diff-serv The valid value is 0 to 63. [DiffServToVlanPriority_DiffServ] VLAN Priority Defines the VLAN priority level. vlan-priority The valid value is 0 to 7. [DiffServToVlanPriority_VlanPriority] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 148: Configuring Icmp Messages

    Mediant 800B Gateway and E- SBC Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS. Figure 12-5: QoS Settings Page - Differentiated Services 12.7 Configuring ICMP Messages Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol suite.

  • Page 149: Dns

    Open the Internal DNS table (Configuration tab > VoIP menu > Network > DNS > Internal DNS Table). Click Add; the following dialog box appears: Figure 12-7: Internal DNS Table - Add Row Dialog Box Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 150: Configuring The Internal Srv Table

    Mediant 800B Gateway and E- SBC Configure the DNS rule, as required. For a description of the parameters, see the table below. Click Add; the DNS rule is added to the table. Table 12-16: Internal DNS Table Parameter Description Parameter...
  • Page 151 Defines the priority of the target host. A lower value means that it is more preferred. priority-1|2|3 By default, no value is defined. [Srv2Ip_Priority1/2/3] Weight (1-3) Defines a relative weight for records with the same priority. By default, no value is defined. weight-1|2|3 [Srv2Ip_Weight1/2/3] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 152: Open Solution Network (Osn) Server

    Mediant 800B Gateway and E- SBC Parameter Description Port (1-3) Defines the TCP or UDP port on which the service is to be found. port-1|2|3 By default, no value is defined. [Srv2Ip_Port1/2/3] 12.9 Open Solution Network (OSN) Server This section describes various networking settings for the OSN server.

  • Page 153: 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 Interface table. Note: The priority list above is applicable only to the Gateway calls. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 154 Mediant 800B Gateway and E- SBC The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 12-9: Device behind NAT and NAT Issues 12.10.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 155 Open the NAT Translation table (Configuration tab > VoIP menu > VoIP Network > NAT Translation Table). Click Add; the following dialog box appears: Figure 12-11: NAT Translation Table - Add Row Dialog Box Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 156: Remote Ua Behind Nat

    Mediant 800B Gateway and E- SBC Configure a NAT translation rule according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory. Table 12-18: NAT Translation Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row.
  • Page 157 IP address:port (i.e., allocated by the NAT server). Therefore, to ensure that the media reaches the UA, the device must send it to the public address. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 158 Mediant 800B Gateway and E- SBC 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. This is done for each media type--RTP, RTCP and T.38--and therefore, they can have different destination IP...
  • Page 159 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.0 Mediant 800B Gateway and E- SBC...
  • Page 160 Mediant 800B Gateway and 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 161: Robust Receipt Of Media Streams By Media Latching

    12. Network 12.11 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 162: Multiple Routers Support

    Mediant 800B Gateway and E- SBC If you have set the InboundMediaLatchMode parameter to 1 or 2, scroll down to the Robust Settings group and do the following: • Define the minimum number of continuous media (RTP, RTCP, SRTP, and...

  • Page 163: Security

    Configuring Firewall Allowed Rules on page 722. The following procedure describes how to configure Firewall rules through the Web interface. You can also configure it through ini file (AccessList) or CLI (configure voip > access-list). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 164 Mediant 800B Gateway and E- SBC  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security > Firewall Settings). Click Add; the following dialog box appears: Figure 13-1: Firewall Settings Table - Add Row Dialog Box Configure a Firewall rule according to the parameters described in the table below.
  • Page 165 This is applicable if you enabled the 'Use Specific network-interface-name Interface' field. The list displays interface names as defined in [AccessList_Interface_x] the Interface table in ''Configuring IP Network Interfaces'' on page 135. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 166 Mediant 800B Gateway and E- SBC Parameter Description Packet Size Defines the maximum allowed packet size. packet-size The valid range is 0 to 65535. [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment.

  • Page 167: Configuring General Security Settings

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

  • Page 168: Intrusion Detection System

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

  • Page 169: Enabling Ids

    Open the IDS Policy table (Configuration tab > VoIP menu > Security > Intrusion Detection and Prevention > Policy Table); the table shows the pre-configured IDS policies: Figure 13-3: IDS Policy Table with Default Rules Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 170 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 13-4: IDS Policy Table - Add Row Dialog Box Configure an IDS Policy name according to the parameters described in the table below. Click Add. Table 13-3: IDS Policy Table Parameter Descriptions...
  • Page 171  Header overflow  [3] Authentication failure =  Local authentication ("Bad digest" errors)  Remote authentication (SIP 401/407 is sent if original message includes authentication)  [4] Dialog establish failure = Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 172 Mediant 800B Gateway and E- SBC Parameter Description  Classification failure (see ''Configuring Classification Rules'' on page 645)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response)  [5] Abnormal flow = ...

  • Page 173: Assigning Ids Policies

    Configure a rule according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory. Table 13-5: IDS Match Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [IDSMatch_Index] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 174 Mediant 800B Gateway and E- SBC Parameter Description SIP Interface ID Defines the SIP Interface(s) to which you want to assign the IDS Policy. This indicates the SIP Interfaces that are being attacked. sip-interface The valid value is the ID of the SIP Interface. The following syntax is...

  • Page 175: Viewing Ids Alarms

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

  • Page 177: Media

    To configure gain control using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 14-1: Voice Volume Parameters in Voice Settings Page Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 178: Silence Suppression (Compression)

    Mediant 800B Gateway and E- SBC Configure the following parameters: • 'Voice Volume' (VoiceVolume) - Defines the voice gain control (in decibels) of the transmitted signal. • 'Input Gain' (InputGain) - Defines the PCM input gain control (in decibels) of the received signal.
  • Page 179 ECHybridLoss - defines the four-wire to two-wire worst-case Hybrid loss • ECNLPMode - defines the echo cancellation Non-Linear Processing (NLP) mode • EchoCancellerAggressiveNLP - enables Aggressive NLP at the first 0.5 second of the call Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 180: Fax And Modem Capabilities

    Mediant 800B Gateway and E- SBC 14.2 Fax and Modem Capabilities This section describes the device's fax and modem capabilities and corresponding configuration. The fax and modem configuration is done in the Fax/Modem/CID Settings page. Notes: • Unless otherwise specified, the configuration parameters mentioned in this section are available on this page.

  • Page 181: Fax/Modem Operating Modes

    You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). The parameter does not affect the actual transmission rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 182 Mediant 800B Gateway and E- SBC When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders.
  • Page 183 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 184 Device answers a call: If the SDP offer from the remote party contains the 'fmtp' attribute with "AcUdpTl", the device answers with the same attribute and employs AudioCodes proprietary T.38-over-RTP mode; otherwise, the standard mode is used. Note: If both T.38 (regular) and T.38 Over RTP coders are negotiated between the call parties, the device uses T.38 Over RTP.
  • Page 185 Set the 'V.23 Modem Transport Type' parameter to Enable Bypass (V23ModemTransportType = 2). Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 186 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 187 ''Coders and Profiles'' on page 387) to apply certain adaptations to the channel used for fax / modem. For example, to use the coder G.711, to set the jitter buffer optimization factor to 13, and to enable echo cancellation for fax and disable it for modem. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 188 Mediant 800B Gateway and E- SBC  To configure fax / modem transparent mode: In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to No Fax (IsFaxUsed = 0).

  • Page 189: Fax Support

    In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to T.38 Relay (FaxTransportMode = 1). Set the 'V.22 Modem Transport Type' parameter to Enable Bypass (V22ModemTransportType = 2). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 190 Mediant 800B Gateway and E- SBC Set the 'V.23 Modem Transport Type' parameter to Enable Bypass (V23ModemTransportType = 2). Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2).
  • Page 191 1938931006 1938930708 IN IP4 10.8.6.55 s=Phone-Call c=IN IP4 10.8.6.55 t=0 0 m=audio 6010 RTP/AVP 18 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 telephone-event/8000 a=fmtp:97 0-15 a=ptime:20 a=sendrecv m=image 6012 udptl t38 a=T38FaxVersion:3 a=T38MaxBitRate:33600 a=T38FaxMaxBuffer:1024 Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 192: Modem Relay

    Mediant 800B Gateway and E- SBC a=T38FaxMaxDatagram:122 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy 14.2.4 V.150.1 Modem Relay The device can be configured to transfer modem calls using a subset of the ITU-T V.150.1 Modem Relay protocol. The device also supports V.150.1 modem relay coder negotiation in the initial SIP INVITE and 200 OK, using the SDP body according to the USA Department of Defense (DoD) UCR-2008, Change 2 specification.

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

    SDP ‘pmft’ attribute. Omission of this attribute in the SDP content means that VBD mode is the preferred transport mechanism for voice-band data. To configure T.38 mode, use the CodersGroup parameter. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 194: Configuring Rtp/Rtcp Settings

    Mediant 800B Gateway and E- SBC Note: You can also configure the device to handle G.711 coders received in INVITE SDP offers as VBD coders, using the HandleG711asVBD parameter. For example, if the device is configured with G.729 and G.711 VBD coders and it receives an INVITE with an SDP offer containing G.729 and “regular”...

  • Page 195: Comfort Noise Generation

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

  • Page 196: Configuring Dtmf Transport Types

    Mediant 800B Gateway and E- SBC Note: This feature is applicable only to the Gateway application. 14.3.3 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint. The methods and their configuration can be configured in the DTMF &...

  • Page 197: Configuring Rfc 2833 Payload

    (EnableRTPRedundancyNegotiation) - enables the device to include the RTP redundancy dynamic payload type in the SDP, according to RFC 2198. • 'RFC 2833 TX Payload Type' (RFC2833TxPayloadType) - defines the Tx RFC 2833 DTMF relay dynamic payload type. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 198: Configuring Rtp Base Udp Port

    (default is 6000) and number of channels is the maximum number of channels purchased from AudioCodes (included in the installed Software License Key). For example, if the base UDP port is set to 6000, the port range is 6000 to 65,535.

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

    X-Detect: Request=[event type to detect]  X-Detect header in the SIP response message -- SIP 183 (for early dialogs) or 200 OK (for confirmed dialogs) -- sent by the device to the application server specifying which Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 200: Sit Event Detection

    Mediant 800B Gateway and E- SBC of the requested events it can detect (absence of the X-Detect header indicates that the device cannot detect any of the events): X-Detect: Response=[supported event types]  Each time the device detects the supported event, it sends an INFO message to the...

  • Page 201: Detecting Answering Machine Beeps

    14.4.2 Detecting Answering Machine Beeps The device supports the detection of the beep sound played by an answering machine to indicate the end of the answering machine's greeting message. This is useful in that the Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC device can then notify, for example, a third-party, application server that it can now leave a voice message on the answering machine. The device supports the following methods for detecting and reporting beeps: ...
  • Page 203 The device receives a SIP message containing the X-Detect header from the remote application requesting beep detection: INVITE sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 204: Answering Machine Detection (Amd)

    The device's default AMD feature is based on voice detection for North American English (see note below). It uses AudioCodes' sophisticated speech detection algorithms which are based on hundreds of real-life recordings of answered calls by live voice and answering machines in English.
  • Page 205 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 206 Mediant 800B Gateway and E- SBC The tables below show the success rates of the default, pre-installed AMD Sensitivity file (based on North American English) for correctly detecting "live" human voice and answering machine: Table 14-3: Approximate AMD Normal Detection Sensitivity - Parameter Suite 0 (Based on...

  • Page 207: Configuring Amd

    (AMDBeepDetectionSensitivity), enter the AMD beep detection sensitivity level. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. For a complete list of AMD-related parameters, see ''IP Media Parameters'' on page 1161. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC 14.5.2 Enabling IP-to-Tel Call Disconnection upon Detection of Answering Machine The device can disconnect an IP-to-Tel call upon detection of an answering machine on the Tel side. Once detected, the device disconnects the call after the receipt of an ISDN Connect from the Tel side and then sends a SIP BYE message to the IP side to disconnect the call.

  • Page 209: Configuring Various Codec Attributes

    This page also selects the type (USA or Europe) of FXS and/or FXO coefficient information. The FXS coefficient contains the analog telephony interface characteristics such as DC and AC impedance, feeding current, and ringing voltage. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 210: Configuring Media (Srtp) Security

    Mediant 800B Gateway and E- SBC  To configure the analog parameters: Open the Analog Settings page (Configuration tab > VoIP menu > Media > Analog Settings). Figure 14-11: Analog Settings Page Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 732.
  • Page 211 396 and ''SRTP Parameters'' on page 946. • When SRTP is used, the channel capacity may be reduced. The procedure below describes how to configure SRTP through the Web interface. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 212: Srtp Using Dtls Protocol

    Mediant 800B Gateway and E- SBC  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Figure 14-12: Media Security Page From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP.
  • Page 213 > sbc-dtls-mtu) to define the maximum transmission unit (MTU) size for the DTLS handshake. Notes: • The 'Cipher Server' parameter must be configured to "ALL". • The device does not support forwarding of DTLS transparently between endpoints. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 214 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 215: Services

    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.0 Mediant 800B Gateway and E- SBC...
  • Page 216 Mediant 800B Gateway and E- SBC DHCP Option Code DHCP Option Name Option 2 Time Offset Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following: ...
  • Page 217 IP address pool range used by the DHCP server start-address to allocate addresses. [DhcpServer_StartIPAddress] The default value is 192.168.0.100. Note: The IP address must belong to the same subnet as the associated interface’s IP address. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 218 Mediant 800B Gateway and E- SBC Parameter Description End IP Address Defines the ending IP address (IPv4 address in dotted-decimal format) of the IP address pool range used by the DHCP server end-address to allocate addresses. [DhcpServer_EndIPAddress] The default value is 192.168.0.149.
  • Page 219 Option 120 (SIP Server). After defining the parameter, use the 'SIP server type' parameter (see below) to define the type of address (FQDN or IP address). The valid value is a string of up to 256 characters. The default is 0.0.0.0. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 220: Configuring The Vendor Class Identifier

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

  • Page 221: Configuring Additional Dhcp Options

    In the table, select the row of the desired DHCP server for which you want to configure additional DHCP Options, and then click the DHCP Option Table link, located below the table; the DHCP Option table opens. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 222 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-3: DHCP Option Table - Add Row Dialog Box Configure additional DHCP Options for the DHCP server according to the parameters described in the table below.

  • Page 223: Configuring Static Ip Addresses For Dhcp Clients

    In the table, select the row of the desired DHCP server for which you want to configure static IP addresses for DHCP clients, and then click the DHCP Static IP Table link, located below the table; the DHCP Static IP table opens. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 224: Viewing And Deleting Dhcp Clients

    Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-4: DHCP Static IP Table - Add Row Dialog Box Configure a static IP address for a specific DHCP client according to the parameters described in the table below.
  • Page 225 Select the table row index of the DHCP client that you want to delete. Click the Action button, and then from the drop-down menu, choose Delete; a confirmation message appears. Click OK to confirm deletion. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 226: Sip-Based Media Recording

    Mediant 800B Gateway and E- SBC 15.2 SIP-based Media Recording The device can record SIP-based media call sessions traversing it for Gateway and SBC calls. The media recording support is in accordance with the Session Recording Protocol (siprec), which describes architectures for deploying session recording solutions and specifies requirements for extensions to SIP that will manage delivery of RTP media to a recording device.
  • Page 227 This is important for recorded calls. • <session id>: Originally recorded Call-ID, converted from decimal to hex. • <group-ref>: same as <group id>. • <participant id>: SIP From / To user. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 228 Mediant 800B Gateway and E- SBC • <nameID aor>: From/To user@host. • <send> and <recv>: ID's for the RTP/SRTP streams in hex - bits 0-31 are the same as group, bits 32-47 are the RTP port. • <stream id>: Same as <send> for each participant.

  • Page 229: Enabling Sip-Based Media Recording

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

  • Page 230: Configuring Sip Recording Rules

    Mediant 800B Gateway and E- SBC 15.2.2 Configuring SIP Recording Rules The SIP Recording table lets you configure up to 30 SIP-based media recording rules. A SIP Recording rule defines calls that you want to record. For an overview of this feature, see ''SIP-based Media Recording'' on page 226.

  • Page 231: Configuring Sip User Part For Srs

    Open the SIP Recording page (Configuration tab > VoIP menu > Services > SIP Recording). In the 'Recording Server (SRS) Destination Username' field, enter a user part value (string of up to 50 characters). Click Submit, and then save ("burn") your settings to flash memory. Version 7.0 Mediant 800B Gateway and E- SBC...

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

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

  • Page 233: Radius-Based Services

    All servers configured with non-zero Accounting ports form an Accounting redundancy group and the device sends accounting CDRs to one of them, depending on their availability. Below are example configurations: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 234 Mediant 800B Gateway and E- SBC  Only one RADIUS server is configured and used for authorization and accounting purposes (no redundancy). Therefore, both the Authorization and Accounting ports are defined.  Three RADIUS servers are configured: • Two servers are used for authorization purposes only, providing redundancy.
  • Page 235 [RadiusServers_SharedSecret] RADIUS server to verify the authentication of the RADIUS messages sent by the device (i.e., message integrity). The valid value is up to 48 characters. By default, no value is defined. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 236: Configuring Interface For Radius Communication

    Mediant 800B Gateway and E- SBC 15.3.3 Configuring Interface for RADIUS Communication The device can communicate with the RADIUS server through its' OAMP (default) or SIP Control network interface. To change the interface used for RADIUS traffic, use the RadiusTrafficType parameter.
  • Page 237 Below is an example of the clients.conf file (FreeRADIUS client configuration): # clients.conf - client configuration directives client 10.31.4.47 { secret = FutureRADIUS shortname = audc_device If access levels are required, set up a Vendor-Specific Attributes (VSA) dictionary for Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 238 Mediant 800B Gateway and E- SBC the RADIUS server and select an attribute ID that represents each user's access level. The example below shows a dictionary file for FreeRADIUS that defines the attribute "ACL-Auth-Level" with "ID=35". For the device's user access levels and their corresponding numeric representation in RADIUS servers, see ''Configuring Web User Accounts'' on page 67.
  • Page 239 Reset Timer Upon Access: upon each access to a Web page, the timer resets (reverts to the initial value configured in the previous step). ♦ Absolute Expiry Timer: when you access a Web page, the timer doesn’t reset, but continues its count down. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 240: Radius-Based Cdr Accounting

    Mediant 800B Gateway and E- SBC Configure when the Web Users table must be used to authenticate login users. From the 'Use Local Users Database' drop-down list, select one of the following: • When No Auth Server Defined (default): When no RADIUS server is configured or if a server is configured but connectivity with the server is down (if the server is up, the device authenticates the user with the server).

  • Page 241: Ldap-Based Management And Sip Services

    (Operator, Admin, or Security Admin). This is known as the user authorization stage. To determine the access level, the device searches the LDAP directory for groups of which the user is a member, for example: CN=\# Support Dept,OU=R&D Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=a bc,DC=com Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 242: Enabling The Ldap Service

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

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

    Web interface. You can also configure it through ini file (LDAPServersGroup) or CLI (configure voip/ldap/ldap-servers-group).  To configure an LDAP Server Group: Open the LDAP Server Groups table (Configuration tab > VoIP menu > Services > LDAP > LDAP Server Groups). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 244 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-12: LDAP Server Groups Table - Add Row Dialog Box Configure an LDAP Server Group according to the parameters described in the table below. Click Add.

  • Page 245: Configuring Ldap Servers

    LDAP Server Group in the LDAP Server Groups table (see ''Configuring LDAP Server Groups'' on page 243).  To configure an LDAP server: Open the LDAP Configuration Table (Configuration tab > VoIP menu > Services > LDAP > LDAP Configuration Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 246 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-13: LDAP Configuration Table - Add Row Dialog Box Configure an LDAP server according to the parameters described in the table below. Click Add. User's Manual...
  • Page 247 You can use the $ (dollar) sign in this value to enable the device to automatically replace the $ sign with the Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 248 Mediant 800B Gateway and E- SBC Parameter Description user's login password in the search filter, which it sends to the LDAP server for authenticating the user's username-password combination. For example, $. Notes:  The parameter is mandatory.  By default, the device sends the password in clear-text format.

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

    (or DN), where the search is to be done must be configured. For each LDAP server, you can configure up to three base paths. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 250: Configuring The Ldap Search Filter Attribute

    Mediant 800B Gateway and E- SBC The following procedure describes how to configure DNs per LDAP server through the Web interface. You can also configure it through ini file (LdapServersSearchDNs) or CLI (configure voip/ldap/ldap-servers-search-dns).  To configure an LDAP base path per LDAP server: Open the LDAP Configuration table (Configuration tab >...

  • Page 251: Configuring Access Level Per Management Groups Attributes

    Configuration table (see ''Configuring LDAP Servers'' on page 245) and configuration is done per LDAP server. For each LDAP server, you can configure up to three table row entries of LDAP group(s) and their corresponding access level. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 252 Mediant 800B Gateway and E- SBC Notes: • The Management LDAP Groups table is applicable only to LDAP-based login authentication and authorization queries. • If the LDAP response received by the device includes multiple groups of which the user is a member and you have configured different access levels for some of these groups, the device assigns the user the highest access level.
  • Page 253 Defines the attribute names of the groups in the LDAP server. groups The valid value is a string of up to 256 characters. To define multiple groups, separate each group name with a semicolon (;). [MgmntLDAPGroups_Group] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 254: Configuring The Device's Ldap Cache

    Mediant 800B Gateway and E- SBC 15.4.8 Configuring the Device's LDAP Cache The device can optionally store recent LDAP queries and responses with an LDAP server in its local cache. The cache is used for subsequent queries and/or in case of LDAP server failure.
  • Page 255 Click Refresh; if a request with the specified key exists in the cache, the request is resent to the LDAP server. To remove all LDAP entries in the cache, click Clear Group. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 256: Configuring Local Database For Management User Authentication

    Mediant 800B Gateway and E- SBC 15.4.9 Configuring Local Database for Management User Authentication You can configure the device to use its local database (Web Users table) to authenticate management users based on the username-password combination. You can configure the device to use the Web Users table upon the following scenarios: ...

  • Page 257: Ldap-Based Login Authentication Example

    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-20: Base Path (DN) in LDAP Server Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 258 Mediant 800B Gateway and E- SBC  Search Attribute Filter: (sAMAccountName=$). The login username is found based on this attribute (where the attribute's value equals the username): Figure 15-21: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the...
  • Page 259 The configuration to match the above LDAP data structure schema is as follows:  LDAP-based login authentication (management) is enabled in the LDAP Server Groups table (see ''Configuring LDAP Server Groups'' on page 243): Figure 15-24: Configuring LDAP Server Group for Management Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 260 Mediant 800B Gateway and E- SBC  The DN is configured in the LDAP Server Search Base DN table (see ''Configuring LDAP DNs (Base Paths) per LDAP Server'' on page 249): Figure 15-25: Configuring DN  The search attribute filter based on username is configured by the 'LDAP...

  • Page 261: Enabling Ldap Searches For Numbers With Characters

    As the device discards query results where the wildcard results in a digit, it selects 503- 823-4567 as the result. The correct query result is cached by the device for subsequent queries and/or in case of LDAP server failure. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC 15.4.12 Active Directory-based Routing for Microsoft Lync Typically, enterprises wishing to deploy the Microsoft® Lync™ Server are faced with a complex, call routing dial plan when migrating users from their existing PBX or IP PBX to the Lync Server platform.
  • Page 263 Mediation Server (which then routes the call to the Lync client). PBX / IP PBX: If the Lync client is not found in the AD, it routes the call to the PBX / IP PBX. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 264 Mediant 800B Gateway and E- SBC Mobile number: If the Lync client (or Mediation Server) is unavailable (e.g., SIP response 404 "Not Found" upon INVITE sent to Lync client), and the PBX / IP PBX is also unavailable, the device routes the call to the user's mobile number (if exists in the AD).
  • Page 265 Open the IP-to-IP Routing table (Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table). For more information, see Configuring SBC IP-to- IP Routing Rules on page 653. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 266 Mediant 800B Gateway and E- SBC Configure query-result routing rules for each IP domain (private, PBX / IP PBX, Lync clients, and mobile), using the LDAP keywords (case-sensitive) in the Destination Username Prefix field: ♦ PRIVATE: Private number ♦ OCS: Lync client number ♦...
  • Page 267 For example, assume the following configuration in the Calling Name Manipulation Table for Tel-to-IP Calls:  'Source Prefix' field is set to "4".  'Prefix to Add' field is set to "$LDAP-PBX Office". Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 268 Mediant 800B Gateway and E- SBC If the calling number is 4046 and the resultant LDAP query display name is "John Doe", the device sends the INVITE message with the following From header: From: John Doe <sip:4064@company.com> Notes: • The Calling Name Manipulation Table for Tel-to-IP Calls table uses the numbers before manipulation, as inputs.

  • Page 269: Least Cost Routing

    10 minutes: Table 15-15: Call Cost Comparison between Cost Groups for different Call Durations Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes 80.3 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 270 Mediant 800B Gateway and E- SBC 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.

  • Page 271: Configuring Lcr

    Time Bands per Cost Group. Up to 10 Cost Groups can be configured. The following procedure describes how to configure Cost Groups through the Web interface. You can also configure it through ini file (CostGroupTable) or CLI (configure voip > services least-cost-routing cost-group). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 272: Configuring Time Bands For Cost Groups

    Mediant 800B Gateway and E- SBC  To configure a Cost Group: Open the Cost Group table (Configuration tab > VoIP menu > Services > Least Cost Routing > Cost Group Table). Click Add; the following dialog box appears: Configure a Cost Group according to the parameters described in the table below.
  • Page 273 For example, SAT:22:00 denotes Saturday at 10 pm. 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] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 274: Assigning Cost Groups To Routing Rules

    Mediant 800B Gateway and E- SBC Parameter Description Connection Cost Defines the call connection cost during this time band. This is added as a fixed charge to the call. connection-cost The valid value range is 0-65533. The default is 0.

  • Page 275: Http-Based Remote Services

     Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM. Notes: • You can configure only one HTTP Remote Service entry for Routing, for Call Status, and for Topology.
  • Page 276 Mediant 800B Gateway and E- SBC The following procedure describes how to configure HTTP Remote Services through the Web interface. You can also configure it through ini file (HTTPRemoteServices).  To configure an HTTP-based service Open the HTTP Remote Services table (Configuration tab > VoIP menu > Services >...
  • Page 277 HTTP persistent connection messages to keep the connection open. Number of Sockets Defines how many sockets (connection) are established per remote host. [HTTPRemoteServices_NumOfSoc kets] The valid value is 1 to 10. The default is 1. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 278 Mediant 800B Gateway and E- SBC Parameter Description Username Defines the username for HTTP authentication. [HTTPRemoteServices_AuthUserN The valid value is a string of up to 80 characters. The default is ame] "user". Password Defines the password for HTTP authentication. [HTTPRemoteServices_AuthPass The valid value is a string of up to 80 characters.

  • Page 279: Configuring Remote Http Hosts

    The valid value is a string of up to 40 characters. By default, no value is defined. Notes:  Each row must be configured with a unique name.  The parameter is mandatory. Address Defines the address (IP address or FQDN) of the host. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 280: Centralized Third-Party Routing Server

    15.6.3 Centralized Third-Party Routing Server 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 and Tel-to-IP Gateway calls. Employing a routing server replaces the need for using the device's routing tables for determining the destination of calls (IP-to-IP Routing table for SBC calls and Tel-to-IP Routing table for Tel-to-IP calls).
  • Page 281 The device automatically updates (sends) the routing server of its' configuration topology regarding SIP routing-related entities (such as SRDs, SIP Interfaces, and IP Groups) that have been configured for use by the routing server. To enable their use by the routing Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 282 Mediant 800B Gateway and E- SBC server, you must configure the 'Used By Routing Server' parameter to Used for each configuration entity. For example, if you add a new SRD and enable it for use by the routing server, the device sends this information to the routing server. Routing of calls pertaining to routing-related entities that are disabled for use by the routing server (default) are handled only by the device (not the routing server).

  • Page 283: Http-Based Proxy Services

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

  • Page 284: Enabling The Http Proxy Application

    Mediant 800B Gateway and E- SBC 15.7.1 Enabling the HTTP Proxy Application Before you can configure HTTP-based proxy services, you must enable the HTTP Proxy application, as described in the following procedure. Once enabled, the Web interface displays menus in the Navigation pane that are relevant to the HTTP Proxy application.
  • Page 285 By default, the default TLS Context (Index 0) is assigned. [HTTPInterface_TLSConte For configuring TLS Contexts, see Configuring TLS Certificate Contexts on page 105. Note: The parameter is applicable only if the connection protocol is HTTPS (defined using the 'Protocol' parameter, above). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 286: Configuring Http Proxy Services

    Mediant 800B Gateway and E- SBC Parameter Description Verify Certificate Enables TLS certificate verification when the connection with the proxy service is based on HTTPS. verify-cert  [0] No = (Default) No certificate verification is done. [HTTPInterface_VerifyCert]  [1] Yes = The device verifies the authentication of the certificate received from the HTTPS peer.

  • Page 287: Configuring Http Proxy Hosts

    > http-proxy > http-proxy-host).  To configure an HTTP Proxy Host: Open the HTTP Proxy Services table (Configuration tab > VoIP menu > Services > HTTP Proxy > HTTP Proxy Services). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 288 Mediant 800B Gateway and E- SBC In the table, select the required HTTP Proxy Service index row, and then click the HTTP Proxy Hosts link, located below the table; the HTTP Proxy Hosts table appears. Click Add; the following dialog box appears:...

  • Page 289: Configuring An Http-Based Ems Service

    You can also configure it through ini file (EMSService) or CLI (configure system > http-proxy > ems-serv).  To configure an EMS Service: Open the EMS Services table (Configuration tab > VoIP menu > Services > HTTP Proxy > EMS Services). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 290 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 15-38: EMS Services Table - Add Row Dialog Box Configure an EMS Service according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.

  • Page 291: Configuring Call Setup Rules

    This is done using the 'Call Setup Rules Set ID' field in the routing table:  SBC IP-to-IP routing - see Configuring SBC IP-to-IP Routing Rules on page 653  Tel-to-IP routing rules - see Configuring Tel-to-IP Routing Rules on page 495 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 292 Mediant 800B Gateway and E- SBC  IP-to-Tel routing rules - see ''Configuring IP-to-Trunk Group Routing Rules'' on page If an incoming call matches the characteristics of a routing rule, the device first runs the assigned Call Setup Rules Set ID before routing the call according to the rule. The device uses the routing rule to route the call, depending on the result of the Call Setup Rules Set ...
  • Page 293 Regular Expression (regex) can also be used, for example:  ldap.attr.mobile exists (attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called number is the same as the number in the attribute Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 294 Mediant 800B Gateway and E- SBC Parameter Description "msRTCSIP-PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Action Subject Defines the element (header, parameter, or body) upon which you want to perform the action. action-subject...

  • Page 295: Call Setup Rule Examples

    Lync server; if the query fails, the device sends the call to the PBX. • Call Setup Rules table configuration: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 296 Mediant 800B Gateway and E- SBC ♦ 'Rules Set ID': 3 ♦ 'Attributes to Query': ‘telephoneNumber=’ + param.call.src.user ♦ 'Attributes to Get': telephoneNumber ♦ 'Row Role': Use Current Condition ♦ 'Condition': ldap.found !exists ♦ 'Action Subject': - ♦ 'Action Type': Exit ♦...

  • Page 297: Enhanced 9-1-1 Support For Lync Server

    E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller. This section describes the E9-1-1 solution provided by Microsoft Lync Server (hereafter referred to as Lync Server) 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.

  • Page 298: Microsoft Lync Server And E9-1-1

    Mediant 800B Gateway and E- SBC The VoIP user dials 9-1-1. AudioCodes' ELIN device eventually sends the call to the emergency service provider over the PSTN or SIP Trunk (PSAP server). The emergency service provider identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network.
  • Page 299 Media Access Control (MAC) address • Depends on network connectivity: ♦ Wireless access point (WAP) Basic Service Set Identifier (BSSID) ♦ Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) chassis ID and port ID Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 300 Mediant 800B Gateway and E- SBC For a Lync client that moves inside the corporate network such as a soft phone on a laptop that connects wirelessly to the corporate network, Lync Server can determine which subnet the phone belongs to or which WAP / SSID is currently serving the soft- client.
  • Page 301 ERL for each floor of the building. The ELIN is used as the phone number for 911 callers within this ERL. The figure below illustrates the use of ERLs and ELINs, with an E9-1-1 call from floor 2 at the branch office: Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 302: Audiocodes Elin Device For Lync Server E9-1-1 Calls To Pstn

    ELIN when dialing 9-1-1. 15.9.3 AudioCodes ELIN Device for Lync Server E9-1-1 Calls to PSTN Microsoft Mediation Server sends the location information of the E9-1-1 caller in the XML- based PIDF-LO body contained in the SIP INVITE message.
  • Page 303 User's Manual 15. Services The figure below illustrates an AudioCodes ELIN device deployed in the Lync Server environment for handling E9-1-1 calls between the Enterprise and the emergency service provider. 15.9.3.1 Detecting and Handling E9-1-1 Calls The ELIN device identifies E9-1-1 calls and translates their incoming E9-1-1 calling numbers into ELIN numbers, sent toward the PSAP.
  • Page 304 Mediant 800B Gateway and E- SBC An example of the ELIN database table is shown below: ELIN Time Count Index Call From 4257275678 22:11:52 4258359333 4257275999 22:11:57 4258359444 4257275615 22:12:03 4258359555 4257275616 22:11:45 4258359777 The ELIN table stores this information for a user-defined period (see ''Configuring the E9-1-1 Callback Timeout'' on page 308), starting from when the E9-1-1 call, established with the PSAP, terminates.
  • Page 305 E9- 1-1 call. This feature is initiated only if the received SIP INVITE message contains a Priority header set to "emergency", as shown below: PRIORITY: emergency Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 306 Mediant 800B Gateway and E- SBC 15.9.3.3 PSAP Callback to Lync Clients for Dropped E9-1-1 Calls As the E9-1-1 service automatically provides all the contact information of the E9-1-1 caller to the PSAP, the PSAP operator can call back the E9-1-1 caller. This is especially useful in cases where the caller disconnects prematurely.

  • Page 307: Configuring Audiocodes Elin Device

    Location-based emergency routing is applicable only to the Gateway application. 15.9.4 Configuring AudioCodes ELIN Device This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server environment. 15.9.4.1 Enabling the E9-1-1 Feature By default, the ELIN device feature for E9-1-1 emergency call handling in a Lync environment is disabled.
  • Page 308 Mediant 800B Gateway and E- SBC 15.9.4.2 Configuring the E9-1-1 Callback Timeout The PSAP can use the ELIN to call back the E9-1-1 caller within a user-defined time interval (in minutes) from when the initial call established with the PSAP has been terminated.
  • Page 309 The above scenario is configured as follows: Enable location-based emergency routing, by loading an ini file to the device with the following parameter setting: E911Gateway = 2 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 310 Mediant 800B Gateway and E- SBC In the Destination Phone Number Manipulation Table for IP-to-Tel Calls (Configuration tab > VoIP menu > Gateway > Manipulations > Dest Number IP- >Tel), add the following two rules for manipulating the destination number of incoming...

  • Page 311: Quality Of Experience

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

  • Page 312: Configuring Clock Synchronization Between Device And Sem

    In other words, you need to configure them with the same NTP server. The NTP server can be one of the following:  AudioCodes EMS server (also acting as an NTP server)  Third-party, external NTP server Once you have determined the NTP server, all the elements--device, SEM, and EMS--must be configured with the same NTP server address.

  • Page 313: Configuring Quality Of Experience Profiles

     Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring the SEM Server'' on page 311.
  • Page 314 Mediant 800B Gateway and E- SBC Note: For your convenience, the device provides pre-configured Quality of Experience Profiles. One of these pre-configured profiles is the default Quality of Experience Profile. Therefore, if you do not configure a Quality of Experience Profile, this default is used.
  • Page 315  [1] Delay [QOEColorRules_monitoredParam]  [2] Packet Loss  [3] Jitter  [4] RERL [Echo] Direction Defines the monitoring direction.  [0] Device Side (default) direction  [1] Remote Side [QOEColorRules_direction] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 316 Mediant 800B Gateway and E- SBC Parameter Description Sensitivity Level Defines the sensitivity level of the thresholds.  sensitivity-level [0] User Defined = Need to define the thresholds in the parameters described below. [QOEColorRules_profile]  [1] Low = Pre-configured low sensitivity threshold values.

  • Page 317: Configuring Bandwidth Profiles

    You can also configure it through ini file (BWProfile) or CLI (configure voip > qoe bw-profile).  To configure Bandwidth Profiles: Open the Bandwidth Profile page (Configuration tab > VoIP menu > Quality of Experience > Bandwidth Profile). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 318 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 16-4: Bandwidth Profile Table - Add Row Dialog Box The figure above shows a configuration example where if the outgoing voice traffic threshold of 64,000 increases by 80% (70% warning threshold plus 10% hysteresis) to 115,200 (64,000 plus 51,200), a Yellow state occurs and an alarm is sent.
  • Page 319 If enabled, an alarm is sent if one of the following scenarios occurs:  Warning threshold is exceeded (Warning severity - Yellow threshold).  Any configured bandwidth threshold is exceeded (Major severity - Red threshold). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 320: Configuring Media Enhancement Profiles

    Mediant 800B Gateway and E- SBC 16.4 Configuring Media Enhancement Profiles Media Enhancement Profiles provides support for access control and media quality enhancements based on call quality measurements (configured in ''Configuring Quality of Experience Profiles'' on page 313) and bandwidth utilization (configured in ''Configuring Bandwidth Profiles'' on page 317).
  • Page 321 Figure 16-6: Media Enhancement Rules Table - Add Row Dialog Box Configure a Media Enhancement Rule according to the parameters described in the table below. Click Add, and then reset the device with a save ("burn") to flash memory. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 322 Mediant 800B Gateway and E- SBC Table 16-5: Media Enhancement Rules Table Parameter Descriptions Parameter Description Index Defines the index of the table row entry. rule-index [MediaEnhancementRules_RuleIndex] Trigger Defines the monitored metrics parameter or bandwidth associated with this rule. trigger ...

  • Page 323: Control Network

    The following procedure describes how to configure Media Realms through the Web interface. You can also configure it through ini file (CpMediaRealm) or CLI (configure voip > voip-network realm). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 324 Mediant 800B Gateway and E- SBC  To configure a Media Realm: Open the Media Realm table (Configuration tab > VoIP menu > VoIP Network > Media Realm Table). Click Add; the following dialog box appears: Figure 17-1: Media Realm Table - Add Row Dialog Box Configure the Media Realm according to the parameters described in the table below.
  • Page 325 6000, the RTCP port and T.38 port for the session is 6001 and 6002, respectively. However, you can configure the device to use the same port for RTP and T.38 packets, by setting the T38UseRTPPort parameter to 1. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 326 Mediant 800B Gateway and 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 327: Configuring Remote Media Subnets

    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.0 Mediant 800B Gateway and E- SBC...
  • Page 328 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 17-3: Remote Media Subnet Table - Add Row Dialog Box Configure the Remote Media Subnet according to the parameters described in the table below. Click Add.

  • Page 329: Configuring Media Realm Extensions

    Select the Media Realm row 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. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 330 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 17-5: Media Realm Extension Table - Add Row Dialog Box Configure the Media Realm Extension according to the parameters described in the table below. Click Add.

  • Page 331: Configuring Srds

    Admission Control rule - see Configuring Admission Control Table on page 637  Classification rule - see Configuring Classification Rules on page 645 As mentioned previously, if you use only a single SRD, the device automatically assigns it to the above-listed configuration entities. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 332 Mediant 800B Gateway and E- SBC As each SIP Interface defines a different Layer-3 network (see ''Configuring SIP Interfaces'' on page 342 for more information) on which to route or receive calls and as you can assign multiple SIP Interfaces to the same SRD, for most deployment scenarios (even for multiple Layer-3 network environments), you only need to employ a single SRD to represent your VoIP network (Layer 5).
  • Page 333 (SRD) or CLI (configure voip > voip-network srd).  To configure an SRD: Open the SRD table (Configuration tab > VoIP menu > VoIP Network > SRD Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 334 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 17-7: SRD Table - Add Row Dialog Box Configure an SRD according to the parameters described in the table below. Click Add. Table 17-4: SRD Table Parameter Descriptions...
  • Page 335 Enables the device to accept REGISTER requests and register them Registrations in its registration database from new users that have not been authenticated by a proxy/registrar server (due to proxy down) and enable-un-auth- Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 336: Filtering Tables In Web Interface By Srd

    Mediant 800B Gateway and E- SBC Parameter Description registrs thus, re-routed to a User-type IP Group. [SRD_EnableUnAuthenticated In normal operation scenarios in which the proxy server is available, Registrations] the device forwards the REGISTER request to the proxy and if authenticated by the proxy (i.e., device receives a success...

  • Page 337: Multiple Srds For Multi-Tenant Deployments

    Shared SRD: Isolated SRDs have their own dedicated SIP resources (SIP Interfaces, Proxy Sets, and IP Groups). This may not be possible in some deployments. For example, in deployments where all tenants use the same SIP Trunking service, or use Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 338 Mediant 800B Gateway and E- SBC the same SIP Interface due to limited SIP interface resources (e.g., multiple IP addresses cannot be allocated and SIP port 5060 must be used). In contrast to Isolated SRDs, a Shared SRD can share its' SIP resources with all other SRDs (Shared and Isolated).
  • Page 339 # srd-view <SRD name> Once accessed, the tenant's name (i.e., SRD name) forms part of the CLI prompt, for example: # srd-view datacenter (srd-datacenter)#  To exit the tenant view: # no srd-view Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 340: Cloning Srds

    Mediant 800B Gateway and E- SBC 17.2.3 Cloning SRDs You can clone (duplicate) existing SRDs. This is especially useful when operating in a multi-tenant environment and you need to add new tenants (SRDs). The new tenants can quickly and easily be added by simply cloning one of the existing SRDs. Once cloned, all you need to do is tweak configuration entities associated with the SRD clone.

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

    If your configuration setup includes only a single SRD, the device automatically selects the SRD when adding related configuration entities. For example, when adding an IP Group, the single SRD is automatically selected in the Add Row dialog box. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 342: Configuring Sip Interfaces

    Mediant 800B Gateway and E- SBC 17.3 Configuring SIP Interfaces The SIP Interface table lets you configure up to 82 SIP Interfaces. A SIP Interface represents a Layer-3 network in your deployment environment, by defining a local, listening port number and type (e.g., UDP), and assigning an IP network interface for SIP signaling traffic.
  • Page 343 For configuring SRDs, see ''Configuring SRDs'' on page 331. Notes:  The parameter is mandatory.  You can assign the same SRD to multiple SIP Interfaces (SBC and Gateway).  For the SAS application, use only SRD 0. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 344 Mediant 800B Gateway and E- SBC Parameter Description Name Defines an arbitrary name to easily identify the row. interface-name The valid value is a string of up to 21 characters. By default, if you do not configure a name, the device automatically assigns the name [SIPInterface_InterfaceName] "SIPInterface_<row index>"...
  • Page 345 SBCDirectMedia. If enabled, even if the SIP Interface is disabled for direct media, direct media is employed for calls belonging to the SIP Interface.  For more information on direct media, see Direct Media on page 610. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 346 Mediant 800B Gateway and E- SBC Parameter Description TLS Context Name Assigns a TLS Context (SSL/TLS certificate) to the SIP Interface. tls-context-name The default TLS Context ("default" at Index 0) is assigned to the SIP Interface by default. [SIPInterface_TLSContext] Notes: ...
  • Page 347 Note: The parameter is applicable only if the device is set to reject unclassified calls. This is configured using the 'Unclassified Calls' parameter on the General Settings page (Configuration tab > VoIP menu > SBC > General Settings). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 348 Mediant 800B Gateway and E- SBC Parameter Description Pre Classification Assigns a Message Manipulation Set ID to the SIP Interface. This Manipulation Set ID lets you apply SIP message manipulation rules on incoming SIP initiating-dialog request messages (not in-dialog), received on this preclassification- SIP Interface, prior to the Classification process.

  • Page 349: Configuring Ip Groups

    IP Group are removed from the device's users database. The following procedure describes how to configure IP Groups through the Web interface. You can also configure it through ini file (IPGroup) or CLI (configure voip > control-network ip-group). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 350 Mediant 800B Gateway and E- SBC  To configure an IP Group: Open the IP Group table (Configuration tab > VoIP menu > VoIP Network > IP Group Table). Click Add; the following dialog box appears: Figure 17-10: IP Group Table - Add Row Dialog Box Configure an IP Group according to to the parameters described in the table below.
  • Page 351 IP Group is deleted and therefore, no routing to the IP Group is done. You can view the registration status of the Gateway-type IP Group in the 'GW Group Registered Status' field, and view the IP Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 352 Mediant 800B Gateway and E- SBC Parameter Description address of the IP Group in the 'GW Group Registered IP Address' field if it is registered with the device. Proxy Set Assigns a Proxy Set to the IP Group. All INVITE messages destined...
  • Page 353 SIP message packet. This feature is especially useful in scenarios [IPGroup_AlwaysUseSourceA where the IP Group endpoints are located behind a NAT firewall (and ddr] the device is unable to identify this using its regular NAT mechanism). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 354 Mediant 800B Gateway and E- SBC Parameter Description  [0] No = (Default) The device sends SIP requests according to the settings of the global parameter, SIPNatDetection.  [1] Yes = The device sends SIP requests and responses to the source IP address received in the previous SIP message packet.
  • Page 355 Note: If configured, the parameter overrides the 'SBC Operation Mode' parameter in the SRD table. Classify By Proxy Set Enables classification of incoming SIP dialogs (INVITEs) to Server- type IP Groups based on Proxy Set (assigned using the classify-by-proxy-set Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 356 Mediant 800B Gateway and E- SBC Parameter Description [IPGroup_ClassifyByProxySet] IPGroup_ProxySetName parameter).  [0] Disable  [1] Enable = (Default) The device searches the Proxy Set table for a Proxy Set that is configured with the same source IP address as that of the incoming INVITE (if host name, then according to the dynamically resolved IP address list).
  • Page 357 [1] SBC Initiates Registration = Used when the device serves as a [IPGroup_RegistrationMode] client (e.g., with an IP PBX). This functions only with the User Info file.  [2] Registrations not Needed = The device adds users to its database in active state. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 358 Mediant 800B Gateway and E- SBC Parameter Description Max. Number of Registered Defines the maximum number of users in this IP Group that can Users register with the device. max-num-of-reg-users The default is -1, meaning that no limitation exists for registered users.
  • Page 359 IP Group in the Classification table. Once classified, the device uses the URI in the To header as the destination.  [-1] Not Configured (default)  [0] From  [1] To Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 360 Mediant 800B Gateway and E- SBC Parameter Description  [2] Request-URI  [3] P-Asserted - First Header  [4] P-Asserted - Second Header  [5] P-Preferred  [6] Route  [7] Diversion  [8] P-Associated-URI  [9] P-Called-Party-ID  [10] Contact ...
  • Page 361 (Read-only field) Displays whether the IP Group entity (gateway) is registered with the device ("Registered" or "Not Registered"). Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 362: Configuring Proxy Sets

    Mediant 800B Gateway and E- SBC 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 registrar server).
  • Page 363 Click Add; the following dialog box appears: Figure 17-12: Proxy Address Table - Add Row Dialog Box Configure the address of the Proxy Set according to the parameters described in the table below. Click Add. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 364 Mediant 800B Gateway and E- SBC Table 17-7: Proxy Sets Table and Proxy Address Table Parameter Description Parameter Description Proxy Sets Table Index Defines an index number for the new table row. Note: Each row must be configured with a unique index.
  • Page 365 (offline). If you enable the Proxy Keep-Alive feature, the device can operate with multiple proxy servers (addresses) for redundancy and load balancing (see the 'Proxy Load Balancing Method' parameter). Notes: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 366 Mediant 800B Gateway and E- SBC Parameter Description  For Survivability mode for User-type IP Groups, the parameter must be enabled (1 or 2).  If the parameter is enabled and the proxy uses the TCP/TLS transport type, you can enable CRLF Keep- Alive feature, using the UsePingPongKeepAlive parameter.
  • Page 367 TLS: "_sipinternaltls_tcp.<domain>" and "_sip_tls.<domain>". For example, if the configured domain name (in the 'Proxy Address' parameter) is "ms-server.com", the device queries for "_sipinternaltls_tcp.ms-server.com" and "_sip_tls.ms-server.com".  TCP: "_sipinternal._tcp.<domain>" and "_sip_tcp.<domain>".  Undefined: "_sipinternaltls_tcp.<domain>", Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 368 Mediant 800B Gateway and E- SBC Parameter Description "_sipinternal_tcp.<domain>", "_sip_tls.<domain>" and "_sip_tcp.<domain>". The SRV query returns the host names (and their weights). The device then performs DNS A-record queries per host name (according to the received weights) to resolve into IP addresses.
  • Page 369 Request-URI of the incoming message, instead of the port configured for the parameter. To enable this, use the IPGroup_SBCRouteUsingRequestURIPort parameter for the IP Group that is associated with the Proxy Set Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 370 Mediant 800B Gateway and E- SBC Parameter Description (Configuring IP Groups on page 349). Transport Type Defines the transport type for communicating with the proxy. transport-type  [0] UDP [ProxyIp_TransportType]  [1] TCP  [2] TLS  [-1] = (Default) The transport type is according to the settings of the global parameter, SIPTransportType.

  • Page 371: Sip Definitions

    You can also configure it through ini file (Account) or CLI (configure voip > sip-definition account).  To configure an Account: Open the Account table (Configuration tab > VoIP menu > SIP Definitions > Account Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 372 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Configure an account according to the parameters described in the table below. Click Add. Once you have configured Accounts, you can register or un-register them, as described below: ...
  • Page 373 "serving" IP Group.  [1] Regular = Regular registration process. For more information, see ''Regular Registration Mode'' on page 374.  [2] GIN = Registration for legacy PBXs, using Global Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 374: Regular Registration Mode

    Mediant 800B Gateway and E- SBC Parameter Description Identification Number (GIN). For more information, see ''Single Registration for Multiple Phone Numbers using GIN'' on page 374. Notes:  Gateway application: To enable registration, you also need to set the 'Registration Mode' parameter to Per Account in the Trunk Group Settings table (see Configuring Trunk Group Settings on page 461).

  • Page 375: Configuring Proxy And Registration Parameters

    The Proxy & Registration page allows you to configure the Proxy server and registration parameters. For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 909. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 376 Mediant 800B Gateway and E- SBC Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see ''Viewing Registration Status'' on page 823.  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions >...

  • Page 377: Sip Message Authentication Example

    According to the sub-header present in the WWW-Authenticate header, the correct REGISTER request is created. Since the algorithm is MD5: • The username is equal to the endpoint phone number "122". • The realm return by the proxy is "audiocodes.com". Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 378 • 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 379: Configuring Sip Message Manipulation

    P-Asserted-Identity header can be copied to the From header), call's parameter values  Deletion of SIP body (e.g., if a message body is not supported at the destination network this body is removed) Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 380 Mediant 800B Gateway and E- SBC  Translating one SIP response code to another  Topology hiding (generally present in SIP headers such as Via, Record Route, Route and Service-Route).  Configurable identity hiding (information related to identity of subscribers, for example, P-Asserted-Identity, Referred-By, Identity and Identity-Info) ...
  • Page 381 Definitions > Msg Policy & Manipulation > Message Manipulations). Click Add; the following dialog box appears: Figure 18-3: Message Manipulations Table - Add Row Dialog Box Configure a Message Manipulation rule according to the parameters described in the table below. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 382 Mediant 800B Gateway and E- SBC Click Add. An example of configured message manipulation rules are shown in the figure below: Figure 18-4: Message Manipulations Page  Index 0: Adds the suffix ".com" to the host part of the To header.
  • Page 383 Note: Only single quotation marks must be used. Row Role Determines which message manipulation condition (configured by the 'Condition' parameter) to use for the rule. row-role  [0] Use Current Condition = (Default) The condition [MessageManipulations_RowRole] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 384: Configuring Sip Message Policy Rules

    Mediant 800B Gateway and E- SBC Parameter Description configured in the table row of the rule is used.  [1] Use Previous Condition = The condition configured in the first table row above the rule that is configured to Use Current Condition is used.
  • Page 385 Max Body Length Defines the maximum SIP message body length. This is the value of the Content-Length header. max-body-length The valid value is up to 1,024 characters. The default is [MessagePolicy_MaxBodyLength] 1,024. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 386 Mediant 800B Gateway and E- SBC Parameter Description Max Num Headers Defines the maximum number of SIP headers. max-num-headers The valid value is any number up to 32. The default is 32. [MessagePolicy_MaxNumHeaders] Note: The device supports up to 20 SIP Record-Route headers that can be received in a SIP INVITE request or a 200 OK response.

  • Page 387: Coders And Profiles

    Notes: • Some coders are license-dependent and are available only if purchased from AudioCodes and included in the Software License Key installed on your device. For more information, contact your AudioCodes sales representative. • Only the packetization time of the first coder in the coder list is declared in INVITE/200 OK SDP, even if multiple coders are defined.
  • Page 388 Mediant 800B Gateway and E- SBC  To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Configure coders according to the parameters described in the table below.
  • Page 389 [1] 24 [1] Enable  [2] 32 (default)  [3] 40  [0] Disable G.729 10, 20 (default), 30, 40, [g729] 50, 60, 80, 100  [1] Enable  [2] Enable Adaptation Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 390: Configuring Coder Groups

    Mediant 800B Gateway and E- SBC Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression   [0] 4.75 [0] Disable 20 (default) Dynamic [Amr]   [1] 5.15 [1] Enable  [2] 5.90  [3] 6.70 ...
  • Page 391 Open the Coder Group Settings page (Configuration tab > VoIP menu > Coders and Profiles > Coders Group Settings). Figure 19-2: Coder Group Settings Page Configure the Coder Group according to the parameters described in the table below. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 392: Configuring Tel Profile

    Mediant 800B Gateway and E- SBC Click Add, and then reset the device with a save ("burn") to flash memory. Table 19-3: Coder Group Settings Table Parameter Descriptions Parameter Description Coder Group ID Defines an ID for the Coder Group.
  • Page 393 Note: Each row must be configured with a unique index. Profile Name Defines an arbitrary name to easily identify the row. The valid value is a string of up to 20 characters. profile-name [TelProfile_ProfileName] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 394 Mediant 800B Gateway and E- SBC Tel Profile Parameter Global Parameter Profile Preference Defines the priority of the Tel Profile, where 1 is the lowest priority and 20 the highest priority. tel-preference Notes: [TelProfile_TelPreference] 1. If both the IP Profile and Tel Profile apply to the same call, the coders and common parameters of the Preferred profile are applied to the call.
  • Page 395 [TelProfile_EnableAGC] EC NLP Mode ECNLPMode echo-canceller-nlp-mode [TelProfile_ECNlpMode] Analog Enable Polarity Reversal EnableReversalPolarity polarity-rvrsl [TelProfile_EnableReversePolarity] Enable Current Disconnect EnableCurrentDisconnect current-disconnect [TelProfile_EnableCurrentDisconnect] MWI Analog Lamp MWIAnalogLamp mwi-analog-lamp [TelProfile_MWIAnalog] MWI Display MWIDisplay mwi-display [TelProfile_MWIDisplay] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 396: Configuring Ip Profiles

    Mediant 800B Gateway and E- SBC Tel Profile Parameter Global Parameter Flash Hook Period FlashHookPeriod flash-hook-period [TelProfile_FlashHookPeriod] DID Wink EnableDIDWink enable-did-wink [TelProfile_EnableDIDWink] Two Stage Dialing IsTwoStageDial is-two-stage-dial [TelProfile_IsTwoStageDial] Enable 911 PSAP Enable911PSAP enable-911-psap [TelProfile_Enable911PSAP] FXO Double Answer EnableFXODoubleAnswer fxo-double-answer [TelProfile_EnableFXODoubleAnswer]...
  • Page 397 Note: Each row must be configured with a unique index. Name Defines an arbitrary name to easily identify the row. profile-name The valid value is a string of up to 40 characters. [IpProfile_ProfileName] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 398 Mediant 800B Gateway and E- SBC Parameter Description Dynamic Jitter Buffer Minimum Defines the minimum delay (in msec) of the device's dynamic Jitter Delay Buffer. jitter-buffer-minimum- The valid range is 0 to 150. The default delay is 10. delay For more information on Jitter Buffer, see Dynamic Jitter Buffer [IpProfile_JitterBufMinDelay] Operation on page 194.
  • Page 399 Note: The corresponding global parameter is InputGain. Voice Volume Defines the voice gain control (in decibels). For the Gateway application: Defines the level of the transmitted signal for IP-to-Tel voice-volume calls. [IpProfile_VoiceVolume] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 400 Mediant 800B Gateway and E- SBC Parameter Description The valid range is -32 to 31 dB. The default is 0 dB. Note: The corresponding global parameter is VoiceVolume. Media IP Version Preference Defines the preferred RTP media IP addressing version for outgoing SIP calls.
  • Page 401 AMD Sensitivity file that needs to be installed on the device. For more information, contact your AudioCodes sales representative. Notes:  To configure the detection sensitivity level, use the 'AMD Sensitivity Level' parameter. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 402 Mediant 800B Gateway and E- SBC Parameter Description  For more information on the AMD feature, see Answering Machine Detection (AMD) on page 204.  The corresponding global parameter is AMDSensitivityParameterSuit. AMD Sensitivity Level Defines the AMD detection sensitivity level of the selected AMD...
  • Page 403 SDP.  expects to receive RFC 2833 packets with the same payload type as configured by the parameter RFC2833PayloadType.  removes DTMF digits in transparent mode (as part of the voice stream). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 404 Mediant 800B Gateway and E- SBC Parameter Description  [5] INFO (Korea) = Sends DTMF digits according to the Korea Telecom format. Notes:  When out-of-band DTMF transfer is used ([1], [2], [3], or [5]), the DTMFTransportType parameter is automatically set to 0 (DTMF digits are removed from the RTP stream).
  • Page 405  [0] Disable (Default) [IpProfile_NSEMode]  [1] Enable In NSE bypass mode, the device starts using G.711 A-Law (default) or G.711 -Law, according to the FaxModemBypassCoderType parameter. The payload type for Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 406 Mediant 800B Gateway and E- SBC Parameter Description these G.711 coders is a standard one (8 for G.711 A-Law and 0 for G.711 -Law). The parameters defining payload type for the 'old' Bypass mode FaxBypassPayloadType and ModemBypassPayloadType are not used with NSE Bypass. The bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval parameter.
  • Page 407 This allows the originating party to listen to network call progress tones such as ringback tone or other network announcements.  Digital: For IP-to-Tel calls, if the parameter Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 408 Mediant 800B Gateway and E- SBC Parameter Description 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 message with SDP in response to only the first received ISDN Proceeding or Progress message after a call is placed to PBX/PSTN over the trunk.
  • Page 409 SIP Diversion header, and then performs IP-to-Tel destination phone number manipulation. Thus, the called (i.e., SIP To header) and redirect (i.e., SIP Diversion header) numbers are different. Note: The corresponding global parameter is Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 410 Mediant 800B Gateway and E- SBC Parameter Description CopyDest2RedirectNumber. Number of Calls Limit Defines the maximum number of concurrent calls (incoming and outgoing) for the SIP entity associated with the IP Profile. If the call-limit number of concurrent calls reaches this limit, the device rejects any [IpProfile_CallLimit] new incoming and outgoing calls belonging to this IP Profile.
  • Page 411 [0] Not Supported = Initial INVITE requests without SDP are not [IpProfile_SBCRemoteDelayed supported. OfferSupport]  [1] Supported = (Default) Initial INVITE requests without SDP are supported. Note: For the parameter to function, you need to assign extension Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 412 Mediant 800B Gateway and E- SBC Parameter Description coders to the IP Profile of the SIP entity that does not support delayed offer (using the IpProfile_SBCExtensionCodersGroupID parameter). User Registration Time Defines the registration time (in seconds) that the device responds...
  • Page 413 Replaces header as is in incoming REFER and outgoing INVITE messages from/to the SIP entity (i.e., Replaces header's value is unchanged). For example, assume that the device establishes a call between A Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 414 Mediant 800B Gateway and E- SBC Parameter Description and B. If B initiates a call transfer to C, the device receives an INVITE with the Replaces header from C. If A supports the Replaces header, the device simply forwards the INVITE as is to A;...
  • Page 415 Defines the SIP provisional response type - 180 or 183 - for Type forwarding early media to the caller, for the SIP entity associated with the IP Profile. sbc-rmt-early-media-  [0] Transparent = (Default) All early media response types are Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 416 Mediant 800B Gateway and E- SBC Parameter Description resp supported; the device forwards all responses as is (unchanged).  [1] 180 = Early media is sent as 180 response only. [IpProfile_SBCRemoteEarlyMed iaResponseType]  [2] 183 = Early media is sent as 183 response only.
  • Page 417 IP entities initiating call hold that do not support the [IpProfile_SBCPlayHeldTone] generation of held tones.  [0] No (default)  [1] Yes Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 418 Mediant 800B Gateway and E- SBC Parameter Description Note: If the parameter is set to Yes, the device plays the tone only if the 'SBC Remote Hold Format' parameter is set to transparent, send-only, send only 0.0.0.0, or not supported.
  • Page 419 SIP entity. Handle X-Detect Enables the detection and notification of events (AMD, CPT, and fax), using the X-Detect SIP header. sbc-handle-xdetect  [0] No (default) [IpProfile_SBCHandleXDetect] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 420 Mediant 800B Gateway and E- SBC Parameter Description  [1] Yes For more information, see Event Detection and Notification using X-Detect Header on page 199. SBC Media Tab Transcoding Mode Defines the transcoding mode (media negotiation) for the SIP entity associated with the IP Profile.
  • Page 421 (i.e., one RTP and the other SRTP), the device performs RTP-SRTP transcoding. To transcode between RTP and SRTP, the following prerequisites must be met:  At least one supported SDP "crypto" attribute and parameters. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 422 Mediant 800B Gateway and E- SBC Parameter Description  EnableMediaSecurity must be set to 1. If one of the above transcoding prerequisites is not met, then:  any value other than “As is” is discarded.  if the incoming offer is SRTP, force transcoding, coder transcoding, and DTMF extensions are not applied.
  • Page 423 Assigns a Coders Group to define the supported fax coders for fax negotiation for the SIP entity associated with the IP Profile. For sbc-fax-coders-group-id configuring Coder Groups, see Configuring Coder Groups on page [IpProfile_SBCFaxCodersGroup 390. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 424 Mediant 800B Gateway and E- SBC Parameter Description Note: The parameter is applicable only if you set the IpProfile_SBCFaxBehavior parameter to a value other than [0]. Fax Mode Enables the device to handle fax offer-answer negotiations for the SIP entity associated with the IP Profile.
  • Page 425 SIP entities in the SDP offer-answer exchange (according sbc-rtp-red-behav to RFC 2198). The parameter defines the device's handling of RTP [IpProfile_SBCRTPRedundancy redundancy for the SIP entity associated with the IP Profile. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 426 Mediant 800B Gateway and E- SBC Parameter Description Behavior] According to the RTP redundancy SDP offer/answer negotiation, the device uses or discards the RTP redundancy packets. The parameter enables asymmetric RTP redundancy, whereby the device can transmit and receive RTP redundancy packets to and...
  • Page 427 SDP offer sent to the SIP entity if the attribute was not present in the original incoming SDP offer.  [2] Remove = The device removes the 'a=rtcp' attribute, if present in the incoming SDP offer received from the other SIP Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 428 Mediant 800B Gateway and E- SBC Parameter Description entity, before sending the outgoing SDP offer to the SIP entity. Note: As the RTCP attribute has been defined by the WebRTC standard as mandatory, the support is important for deployments implementing WebRTC. For more information on WebRTC, see WebRTC on page 685.
  • Page 429 IP 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 610. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 430 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 431: Gateway Application

    Part V Gateway Application...

  • Page 433: Introduction

    CO or the PBX) and connects to analog telephones, dial-up modems, and fax machines. The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 434: Call Processing Summary

    Mediant 800B Gateway and E- SBC 20.1 Call Processing Summary The device's call processing for Gateway calls is shown in the following flowcharts.  IP-to-Tel Call: Figure 20-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-10296...
  • Page 435 User's Manual 20. Introduction  Tel-to-IP Call: Figure 20-2: Tel-to-IP Call Processing Flowchart Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 436 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 437: Digital Pstn

    Creating a Loopback Line: You can create (and remove) remote loopback for DS1 lines. This is done by clicking the Create Loopback button. To remove the loopback, click the Remove Loopback button. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 438 Release Notes). • 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 439 The Stop Trunk button is replaced by the Apply Trunk Settings button. When all trunks are stopped, the Apply to All Trunks button also appears. • All the parameters are available and can be modified. Configure the trunk parameters as required. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 440: Tdm And Timing

    Mediant 800B Gateway and E- SBC Click the Apply Trunk Settings button to apply the changes to the selected trunk (or click Apply to All Trunks to apply the changes to all trunks); the Stop Trunk button replaces Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'.
  • Page 441 To configure internal clock as clock source: Set the clock source to be from the device's internal oscillator. In the TDM Bus Settings page, set the 'TDM Bus Clock Source' parameter (TDMBusClockSource) to Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 442: Configuring Cas State Machines

    Mediant 800B Gateway and E- SBC Internal. For E1/T1 trunks only: Set the line to drive the clock on all trunks: In the Trunk Settings page, set the 'Clock Master' parameter (ClockMaster) to Generated (for all trunks). 21.3 Configuring CAS State Machines...
  • Page 443 [CasStateMachineMaxNumOfIn collected. After reaching this number of digits, the collection of comingANIDigits] ANI digits is stopped. The value must be an integer. The default is -1 (use value from CAS state machine). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 444: Configuring Digital Gateway Parameters

    Mediant 800B Gateway and E- SBC Parameter Description Collet ANI In some cases, when the state machine handles the ANI [CasStateMachineCollectANI] collection (not related to MFCR2), you can control the state machine to collect ANI or discard ANI.  [0] No = Don't collect ANI.
  • Page 445 Gateway > Digital Gateway > Digital Gateway Parameters). Figure 21-4: Digital Gateway Parameters Page Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 732. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 446: Tunneling Applications

    Mediant 800B Gateway and E- SBC 21.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 21.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal...
  • Page 447 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.0 Mediant 800B Gateway and E- SBC...
  • Page 448 Mediant 800B Gateway and E- SBC [ CodersGroup0 ] FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce, CodersGroup0_CoderSpecific; CodersGroup0 0 = g7231; CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ,...

  • Page 449: Qsig Tunneling

    The term tunneling means that messages are transferred ‘as is’ to the remote side without being converted (QSIG > SIP > QSIG). The advantage of tunneling over QSIG-to-SIP interworking is that by using interworking, QSIG functionality can only be partially achieved. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 450 Mediant 800B Gateway and E- SBC When tunneling is used, all QSIG capabilities are supported and the tunneling medium (the SIP network) does not need to process these messages. QSIG messages are transferred in SIP messages in a separate Multipurpose Internet Mail Extensions (MIME) body.

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

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

  • Page 452: Working With Dms-100 Switches

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

  • Page 453: Creating An Nfas-Related Trunk Configuration

    • This feature is applicable only to T1 ISDN protocols supporting NFAS, and only if the NFAS group is configured with two D-channels. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 454: Isdn Overlap Dialing

    Mediant 800B Gateway and E- SBC 21.7 ISDN Overlap Dialing Overlap dialing is a dialing scheme used by several ISDN variants to send and/or receive called number digits one after the other (or several at a time). This is in contrast to en-bloc dialing in which a complete number is sent in one message.

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

    "Address Incomplete" response to the IP side to maintain the current dialog session and to receive additional digits from subsequent re-INVITE or INFO messages. You can use the following parameters to configure overlap dialing for IP-to-Tel calls: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 456 Mediant 800B Gateway and E- SBC • ISDNTxOverlap: Enables IP-to-Tel overlap dialing and defines how the device receives the collected digits from the IP side - in SIP re-INVITE [1] or INFO messages [2]. • TimeBetweenDigits: Defines the maximum time (in seconds) that the device waits between digits received from the IP side.

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

    Euro ISDN QSIG NT-to-TE TE-to-NT Table 21-3: Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE Yes* TE-to-NT * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 458 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 459: Trunk Groups

    To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the telephony interface module for which you want to define the Trunk Group. module [TrunkGroup_Module] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 460 Mediant 800B Gateway and E- SBC Parameter Description From Trunk Defines the starting physical Trunk number in the Trunk Group. The number of listed Trunks depends on the device's hardware first-trunk-id configuration. [TrunkGroup_FirstTrunkId] Note: The parameter is applicable only to PRI and BRI modules.

  • Page 461: Configuring Trunk Group Settings Table

    To configure Trunk Group settings: Open the Trunk Group Settings table (Configuration tab > VoIP menu > Gateway > Trunk Group > Trunk Group Settings). Click Add; the following dialog box appears: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 462 Mediant 800B Gateway and E- SBC Configure a Trunk Group according to the parameters described in the table below. Click Add. Table 22-2: Trunk Group Settings Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row.
  • Page 463 This option is applicable only to FXS interfaces.  [10] Select Trunk by Supplementary Services Table = The BRI port/module is selected according to the settings in the ISDN Supplementary Services table (see Configuring Multi-Line Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 464 Mediant 800B Gateway and E- SBC Parameter Description Extensions and Supplementary Services on page 558), allowing the routing of IP-to-Tel calls to specific BRI endpoints according to extension number. This option is applicable only to FXS and BRI interfaces. ...
  • Page 465 If registration fails, the user part in the INVITE Contact header is set to the source party number.  The 'Contact User' parameter in the Account table overrides this parameter (see ''Configuring Registration Accounts'' on page 371). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 466 Mediant 800B Gateway and E- SBC Parameter Description Serving IP Group Assigns an IP Group to where the device sends INVITE messages for calls received from the Trunk Group. The actual destination to serving-ip-group where the INVITE messages are sent is according to the Proxy Set [TrunkGroupSettings_ServingIP associated with the IP Group.
  • Page 467 "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 468 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 469: Manipulation

    1 and "55" for rule index 2, the device uses rule index 1 for numbers that start with 551 and uses rule index 2 for numbers that start with 550, 552, 553, and so on until 559. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 470 Mediant 800B Gateway and E- SBC However, if you configure the source prefix number as "55" for rule index 1 and "551" for rule index 2, the device applies rule index 1 to all numbers that start with 55, including numbers that start with 551.
  • Page 471 Rule 5: When the destination number has the prefix 6, 7, or 8 (e.g., 85262146), source number prefix 2001, it is changed to 3146. 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.0 Mediant 800B Gateway and E- SBC...
  • Page 472 Mediant 800B Gateway and 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 Table 23-1: Number Manipulation Tables Parameter Descriptions...
  • Page 473 For example, if you enter 9 and the phone number prefix-to-add is 1234, the new number is 91234. [Prefix2Add] Suffix to Add Defines the number or string that you want added to the end of the Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 474 Mediant 800B Gateway and E- SBC Parameter Description suffix-to-add telephone number. For example, if you enter 00 and the phone number is 1234, the new number is 123400. [Suffix2Add] Defines the Type of Number (TON).  If you selected 'Unknown' for the NPI, you can select Unknown [0].

  • Page 475: Manipulating Number Prefix

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

  • Page 476: Sip Calling Name Manipulations

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

  • Page 479: Configuring Redirect Number Ip To Tel

    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 applies the manipulation configured for that rule. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 480 Mediant 800B Gateway and E- SBC Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
  • Page 481 Note: The parameter is applicable only to the Redirect Number IP-to- Tel table. Operation (Action) Stripped Digits From Left Defines the number of digits to remove from the left of the redirect Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 482 Mediant 800B Gateway and E- SBC Parameter Description remove-from-left number prefix. For example, if you enter 3 and the redirect number is 5551234, the new number is 1234. [_RemoveFromLeft] Stripped Digits From Right Defines the number of digits to remove from the right of the redirect number prefix.

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

    After the above manipulation is done, the device sends the following outgoing SIP 302 response: SIP/2.0 302 Moved Temporarily Via: SIP/2.0/TLS 10.33.45.68;branch=z9hG4bKac54132643;alias From: "MP118 1" <sip:8001@10.33.45.68>;tag=1c54119560 To: <sip:6001@10.33.45.69;user=phone>;tag=1c664560944 Call-ID: 541189832710201115142@10.33.45.68 CSeq: 1 INVITE Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.80A.227.005 Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 23.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
  • Page 485 If you selected E.164 Public as the NPI, you can select one of the following:  [0] Unknown  [1] International  [2] National  [3] Network Specific  [4] Subscriber  [6] Abbreviated SIP Phone Context Defines the SIP 'phone-context' URI parameter. context [PhoneContext_Context] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 486: Configuring Release Cause Mapping

    Mediant 800B Gateway and E- SBC 23.8 Configuring Release Cause Mapping When a call is disconnected, the reason for the disconnection (or call failure) is sent by the side (IP or Tel) on which the call disconnection occurred. From the IP side, a SIP response is sent (e.g., 406);...
  • Page 487 Request URI too long Interworking Unsupported media type Service/option not implemented Bad extension Interworking Temporarily unavailable No user responding Call leg/transaction doesn’t 481* Interworking exist 482* Loop detected Interworking Too many hops Interworking Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC ISDN Release SIP Response Description Description Reason Address incomplete Invalid number format Ambiguous Unallocated number Busy here User busy Not acceptable here Normal, unspecified Server internal error Temporary failure Not implemented Network out of order...
  • Page 489 Not found No route to network Not found No route to destination Not found Channel unacceptable Not acceptable Call awarded and being delivered in an Server internal error established channel Normal call clearing Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 490 Mediant 800B Gateway and E- SBC ISDN Release Description Description Reason Response User busy Busy here No user responding Request timeout No answer from the user Temporarily unavailable Call rejected Forbidden Number changed w/o diagnostic Gone Non-selected user clearing Not found...

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

    ISDN cause code also appears in the Release Cause Mapping ISDN to SIP table (see ''Configuring ISDN-to-SIP Release Cause Mapping'' on page 488), the device maps it to the corresponding SIP response code, which it sends to the IP side. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 492 Mediant 800B Gateway and E- SBC Note: If the originally received ISDN cause code is configured in both the Release Cause ISDN to ISDN table and the Release Cause Mapping ISDN to SIP table, the mapping rule with the originally received code in the Release Cause Mapping ISDN to SIP table is ignored;...

  • Page 493: Reason Header

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

  • Page 494: Numbering Plans And Type Of Number

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

  • Page 495: Routing

    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. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 496 Mediant 800B Gateway and E- SBC You can configure the routing rule with one or more of the following incoming Tel characteristics:  Source Trunk Group (from where the call is received)  Source (calling) and destination (called) telephone number prefix and suffix You can configure the IP destination to one of the following: ...
  • Page 497 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. Figure 24-1: Locating SRD Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 498 Mediant 800B Gateway and E- SBC Note: When using a proxy server, it is unnecessary to configure routing rules in the Tel-to-IP Routing table, unless you require one of the following: • Fallback (alternative) routing when communication with the proxy server fails.
  • Page 499 Rule 4 (domain name destination): For called phone number prefixes 5, 7, 8, or 9, and the caller belongs to Trunk Group ID 4, the call is sent to the domain "itsp.com". Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 500 Mediant 800B Gateway and E- SBC  Rule 5 (block): For all callers (*), if the called phone number prefix is 00, the call is rejected (IP address 0.0.0.0).  Rule 6, 7, and 8 (Forking Group): For all callers (*), if the called phone number prefix is 100, the call is sent to Rule 7 and 9 (belonging to Forking Group "1").
  • Page 501 INVITE message is set to the value configured for the 'Destination IP Address' parameter (in this table); otherwise, if no IP address is defined, it is set to the value of Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 502 Mediant 800B Gateway and E- SBC Parameter Description the 'SIP Group Name' parameter (configured in the IP Group table).  The parameter is used as the 'Serving IP Group' in the Account table for acquiring authentication username/password for this call (see ''Configuring Registration Accounts'' on page 371).
  • Page 503 2, 3, and 4 with Forking Group "1": The device sends the call according to index entry 1 only and ignores the other index entries even if the destination is unavailable and alternative routing is enabled. This is because the subsequent Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 504 Mediant 800B Gateway and E- SBC Parameter Description index entries are defined with a Forking Group number that is lower than that of index entry 1.  Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with Forking Group "1": The device first sends the call according to...
  • Page 505 "DNS Error" = No DNS resolution. This status is applicable only when a domain name is used (instead of an IP address).  "Not Available" = Destination is unreachable due to networking issues. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 506: Configuring Ip-To-Trunk Group Routing Rules

    Mediant 800B Gateway and E- SBC 24.3 Configuring IP-to-Trunk Group Routing Rules The IP to Trunk Group Routing table lets you configure up to 120 IP-to-Trunk Group routing rules. IP-to-Trunk Group routing rules are used to route incoming IP calls to Trunk Groups.
  • Page 507 The following procedure describes how to configure Inbound IP Routing rules through the Web interface. You can also configure it through ini file (PSTNPrefix) or CLI (configure voip > gw routing ip2tel-routing). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 508 Mediant 800B Gateway and E- SBC  To configure IP-to-Tel routing rules: Open the IP to Trunk Group Routing table (Configuration tab > VoIP menu > Gateway > Routing > IP to Trunk Group Routing). Click Add; the following dialog box appears: Figure 24-3: IP to Trunk Group Table - Add Row Dialog Box Configure a routing rule according to the parameters described in the table below.
  • Page 509 "*": denotes any number between 0 and 255. For example, 10.8.8.* represents all addresses between 10.8.8.0 and 10.8.8.255. Source Phone Prefix Defines the prefix or suffix of the calling (source) telephone number. src-phone-prefix Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 510 Mediant 800B Gateway and E- SBC Parameter Description [PstnPrefix_SourcePrefix] The prefix can include up to 49 digits. You can use special 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. To denote any prefix, use the asterisk (*) symbol.

  • Page 511: Configuring A Gateway Routing Policy Rule

    (configure voip > gw routing gw-routing-policy).  To edit the Gateway Routing Policy rule: Open the Gateway Routing Policy table (Configuration tab > VoIP menu > Gateway > Routing > Gateway Routing Policy). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 512 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 24-4: Gateway Routing Policy Table - Edit Row Dialog Box Configure the Gateway Routing Policy rule according to the parameters described in the table below. Click Add.

  • Page 513: Ip Destinations Connectivity Feature

    These parameters are configured in the Routing General Parameters page (Configuration tab > VoIP menu > Gateway > Routing > General Parameters), as shown below: Figure 24-5: IP Connectivity Method in Routing General Parameters Page Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC  Quality of Service (QoS): You can enable the device to check the QoS of IP destinations. The device measures the QoS according to RTCP statistics of previously established calls with the IP destination. The RTCP includes packet delay (in milliseconds) and packet loss (in percentage).
  • Page 515 The device plays a tone to the Tel endpoint (for analog interfaces) whenever an alternative route is used. This tone is played for a user-defined time configured by the 'Alternative Routing Tone Duration' parameter. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 516: Alternative Routing Based On Sip Responses

    Mediant 800B Gateway and E- SBC 24.6.2 Alternative Routing Based on SIP Responses The device can perform alternative routing based on the received SIP response code (i.e., 4xx, 5xx, 6xx, or 8xx). If you have configured this response code in the Reasons for Tel-to- IP Alternative Routing table, the device attempts to re-route the call to an alternative destination, if configured.
  • Page 517 Configure SIP response codes (call failure reasons) that invoke alternative Tel-to-IP routing: Open the Reasons for Tel-to-IP Alternative Routing page (Configuration tab > VoIP menu > Gateway > Routing > Alternative Reasons > Reasons for Tel- to-IP). Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 24-7: Reasons for Tel-to-IP Alternative Routing Table - Add Row Dialog Box Configure a SIP response code for alternative routing according to the parameters described in the table below.

  • Page 519: Pstn Fallback

    PSTN. This configuration is necessary as the re-routed call is now considered an IP-to-Tel call. For configuring IP-to-Tel routing rules, see ''Configuring IP to Trunk Group Routing Rules'' on page 506. Note: The PSTN Fallback feature is applicable only to digital interfaces. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC 24.7 Alternative Routing for IP-to-Tel Calls The device supports alternative IP-to-Tel call routing, as described in this section. 24.7.1 Alternative Routing to Trunk upon Q.931 Call Release Cause Code You can configure up to 10 ISDN Q.931 release cause codes, which if received from the Tel side, the device routes the IP-to-Tel call to an alternative Trunk Group, if configured.

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

    The device forwards calls using this table only if no alternative IP-to-Tel routing rule has been configured in the Inbound IP Routing table or alternative routing fails and the following reason(s) in the SIP Diversion header of 3xx messages exists: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 522 Mediant 800B Gateway and E- SBC  For digital interfaces: “out-of-service” - all trunks are unavailable/disconnected  "unavailable": • For digital interfaces: All trunks are busy or unavailable • For analog interfaces: All FXS / FXO lines pertaining to a Trunk Group are busy...

  • Page 523: Alternative Routing Upon Isdn Disconnect

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

  • Page 525: Configuring Dtmf And Dialing

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

  • Page 526: Dialing Plan Features

    Mediant 800B Gateway and E- SBC 25.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 25.1.1 Digit Mapping Digit map pattern rules are used for Tel-to-IP ISDN overlap dialing (by setting the ISDNRxOverlap parameter to 1) to reduce the dialing period (for digital interface). For more information on digit maps for ISDN overlapping, see ISDN Overlap Dialing on page 454.

  • Page 527: External Dial Plan File

    Dial Plan. 25.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see ''Dial Plan File'' on page 747. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 528: Interworking Keypad Dtmfs For Sip-To-Isdn Calls

    Mediant 800B Gateway and E- SBC 25.2 Interworking Keypad DTMFs for SIP-to-ISDN Calls The device can interwork DTMF tones received from the IP to the PSTN, using the ISDN Keypad Facility information element (IE) in Q.931 INFORMATION messages. This feature is applicable only to the Euro ISDN variant (User side).

  • Page 529: Configuring Supplementary Services

    ''Configuration Parameters Reference'' on page 909.  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > Gateway > DTMF & Supplementary > Supplementary Services). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 530 Mediant 800B Gateway and E- SBC Configure the parameters as required. Click Submit, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server. To save the changes to flash memory, see ''Saving Configuration'' on page 732.

  • Page 531: Call Hold And Retrieve

    (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.0 Mediant 800B Gateway and E- SBC...
  • Page 532 Mediant 800B Gateway and 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 533: Call Pickup

    (e.g., #77), the incoming call from the other phone is forwarded to the FXS user's phone. This feature is configured using the parameter KeyCallPickup. Note: The Call Pick-Up feature is supported only for FXS endpoints pertaining to the same Trunk Group ID. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 534: Bri Suspend And Resume

    Mediant 800B Gateway and E- SBC 26.3 BRI Suspend and Resume The device supports call suspend and resume services initiated by ISDN BRI phones connected to the device. During an ongoing call, the BRI phone user can suspend the call by typically pressing the phone’s “P”...

  • Page 535: Call Transfer

    When the device receives a request for a consultation call transfer from the PBX, the device sends a SIP REFER message with a Replaces header to the SIP UA to transfer it to Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 536: Blind Call Transfer

    Mediant 800B Gateway and E- SBC another SIP UA. Once the two SIP UA parties are successfully connected, the device requests the PBX to disconnect the ISDN call, thereby freeing resources on the PBX. For example, assume legacy PBX user "A" has two established calls connected through the device –...

  • Page 537: Call Forward

    (or when a proxy is used, the proxy’s IP address). • For receiving call forward, the device handles SIP 3xx responses for redirecting calls with a new contact. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 538: Call Forward Reminder Ring

    Mediant 800B Gateway and E- SBC 26.6.1 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, only in onhook state, when a third-party Application Server (e.g., softswitch) forwards an incoming call to another destination.

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

    To header, representing the reason for the call forward. The codes for the call forward can be defined using the following parameters:  SuppServCodeCFU - Call Forward Unconditional  SuppServCodeCFUDeact - Call Forward Unconditional Deactivation Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 540: Call Waiting

    Mediant 800B Gateway and E- SBC  SuppServCodeCFB - Call Forward on Busy  SuppServCodeCFBDeact - Call Forward on Busy Deactivation  SuppServCodeCFNR - Call Forward on No Reply  SuppServCodeCFNRDeact - Call Forward on No Reply Deactivation Note: These codes must be defined according to the settings of the softswitch (i.e., the softswitch must recognize them).

  • Page 541: Message Waiting Indication

    Once the voice message is retrieved, the MWI light on the BRI phone turns off. This is configured by setting the VoiceMailInterface parameter to 8 (“ETSI”) and enabled by the EnableMWI parameter. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 542 Mediant 800B Gateway and E- SBC  Euro-ISDN MWI: The device supports Euro-ISDN MWI for IP-to-Tel calls. The device interworks SIP MWI NOTIFY messages to Euro-ISDN Facility information element (IE) MWI messages. This is configured by setting the VoiceMailInterface parameter to 8.

  • Page 543: Caller Id

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

  • Page 544: Caller Id On The Ip Side

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

  • Page 545: Three-Way Conferencing

    The device supports the following 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 546 Mediant 800B Gateway and E- SBC To join a conference, the Request-URI includes the Conference ID string preceded by the number of the participants in the conference and terminated by a unique number. INVITE messages with the same URI join the same conference. For example: INVITE sip:4conf1234@10.1.10.10...

  • Page 547: 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.0 Mediant 800B Gateway and E- SBC...
  • Page 548 Mediant 800B Gateway and 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 549 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.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC 26.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 551 Number (ANI) MF dialed "KPnnnnnnnnST" "nnnnnnnn" None "KPnnnnnnnnnnnnSTP" "nnnnnnnnnnnn" "KPnnnnnnnnnnnnSTKPmmmmmmmmmmST" "nnnnnnnnnnnn" "mmmmmmmmmm" (pANI) None "KPnnSTP" "nn" MF dialed "KPnST" "n" For example: "From: <sip:8>@xyz.com>" generates device MF spill of KP 8 ST Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 552 Mediant 800B Gateway and E- SBC Table notes:  For all other cases, a SIP 484 response is sent.  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 553: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls

    The Priority header of the incoming SIP INVITE message contains the “emergency” value. Emergency pre-emption of calls can be enabled for all calls, using the global parameter CallPriorityMode, or for specific calls using the Tel Profile parameter CallPriorityMode. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 554: Multilevel Precedence And Preemption

    Mediant 800B Gateway and E- SBC Notes: • This feature is applicable to FXO, CAS and ISDN interfaces. • For Trunk Groups configured with call preemption, all must be configured to MLPP [1] or all configured to Emergency [2]. In other words, you cannot set some trunks to [1] and some to [2].
  • Page 555 MLPPDefaultNamespace parameter. You can also configure up to 32 user-defined namespaces, using the table ini file parameter, ResourcePriorityNetworkDomains. Once defined, you need to set the MLPPDefaultNamespace parameter value to the desired table row index. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 556: Mlpp Preemption Events In Sip Reason Header

    Mediant 800B Gateway and E- SBC By default, the device maps the received Resource-Priority field of the SIP Resource- Priority header to the outgoing ISDN PRI Precedence Level (priority level) field as follows:  If the network-domain field in the Resource-Priority header is "uc", then the device sets the Precedence Level field in the ISDN PRI Precedence Level IE according to Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value):...

  • Page 557: Precedence Ring Tone

    Tel and IP sides if a call is preempted, using the PreemptionToneDuration parameter. Emergency Telecommunications Services (ETS) calls (e.g., E911) can be configured with a higher priority than any MLPP call (default), using the E911MLPPBehavior parameter. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 558: Denial Of Collect Calls

    Mediant 800B Gateway and E- SBC 26.13 Denial of Collect Calls You can configure the device to reject (disconnect) incoming Tel-to-IP collect calls and to signal this denial to the PSTN. This capability is required, for example, in the Brazilian telecommunication system to deny collect calls.
  • Page 559 (configure voip > gw digitalgw isdn-supp-serv).  To configure endpoint supplementary services: Open the Supplementary Services table (Configuration tab > VoIP menu > Gateway > DTMF and Supplementary > Supp Services Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 560 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 26-5: Supplementary Services Table - Add Row Dialog Box Configure a supplementary service according to the parameters described in the table below. Click Add. The figure below displays an example of multiple-line extensions configured in the...
  • Page 561 Enables the receipt of Caller ID.  [0] Disabled = The device does not send Caller ID caller-id-enable information to the endpoint. [ISDNSuppServ_IsCallerIDEnabled]  [1] Enabled = The device sends Caller ID information to the endpoint. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 562: Detecting Collect Calls

    The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call) using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
  • Page 563 (PayPhoneMeteringMode) to the required method (SIP Interval Provided, SIP RAW Data Provided, SIP RAW Data Incremental Provided, or SIP 2 TEL INTERWORKING). Note: This feature is applicable to Euro ISDN (PRI and BRI). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 564: Configuring Charge Codes

    Mediant 800B Gateway and E- SBC 26.17 Configuring Charge Codes The Charge Codes table lets you configure metering tones that the device generates to the Tel side on its FXS interfaces, and for Advice of Charge (AOC) services for Euro ISDN trunks (see Advice of Charge Services for Euro ISDN on page 562).

  • Page 565: Configuring Voice Mail

    Guide for Voice Mail User's Manual.  To configure the Voice Mail parameters: Open the Voice Mail Settings page (Configuration tab > VoIP menu > Gateway > Advanced Applications > Voice Mail Settings). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 566 Mediant 800B Gateway and E- SBC Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 732. User's Manual Document #: LTRT-10296...

  • Page 567: Converting Accented Characters From Ip To Tel

    Configure a Character Conversion rule according to the parameters described in the table below. Click Add. Table 26-8: Char Conversion Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 568 Mediant 800B Gateway and E- SBC Parameter Description [CharConversion_Index] Note: Each row must be configured with a unique index. Character Name Defines an arbitrary name to easily identify the row. char-name The valid value is a string of up to 40 characters.

  • Page 569: Analog Gateway

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

  • Page 570: Configuring Metering Tones

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

  • Page 571: Configuring Fxo Settings

    The FXO Settings page allows you to configure the device's specific FXO parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 909. Note: The FXO Settings page is available only for FXO interfaces. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 572 Mediant 800B Gateway and E- SBC  To configure the FXO parameters: Open the FXO Settings page (Configuration tab > VoIP menu > Gateway > Analog Gateway > FXO Settings). Figure 27-3: FXO Settings Page Configure the parameters as required.

  • Page 573: Configuring Authentication

    Gateway > Authentication). Click Add; the following dialog box appears: Figure 27-4: Authentication Table - Edit Row Dialog Box Configure authentication per port according to the parameters described in the table below. Click Add. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 574: Configuring Automatic Dialing

    Mediant 800B Gateway and E- SBC Table 27-1: Authentication Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table row. [Authentication_Index] Module (Read-only) Displays the module number on which the port is located. port-type [Authentication_Module] Port (Read-only) Displays the port number.
  • Page 575 FXO line, plays a dial tone, and then waits for DTMF digits. If no digits are detected within a user-defined time, the configured destination number is automatically dialed by sending a SIP INVITE message with this number. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 576 Mediant 800B Gateway and E- SBC Parameter Description Hotline Dial Tone Duration Defines the duration (in seconds) after which the destination phone number is automatically dialed. This is hotline-dia-ltone-duration applicable only if the port has been configured for Hotline [TargetOfChannel_HotLineToneDuration] (i.e., 'Auto Dial Status' is set to Hotline).

  • Page 577: Configuring Caller Display Information

    Parameter Description Index (Read-only) Displays the index number of the table row. [CallerDisplayInfo_Index] Module (Read-only) Displays the module number on which the port is located. [CallerDisplayInfo_Module] Port (Read-only) Displays the port number. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 578: Configuring Call Forward

    Mediant 800B Gateway and E- SBC Parameter Description [CallerDisplayInfo_Port] Port Type (Read-only) Displays the port type (FXS or FXO). [CallerDisplayInfo_PortType] Display String Defines the Caller ID string. The valid value is a string of up to 18 characters. display-string [CallerDisplayInfo_DisplayString] Note: If you set the parameter to "Private"...
  • Page 579 Note: If the parameter is configured with only a telephone number and a [FwdInfo_Destination] 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 Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 580: Configuring Caller Id Permissions

    Mediant 800B Gateway and E- SBC Parameter Description page 495). No Reply Time If you have set the 'Type' parameter for this port to No Answer or On no-reply-time Busy or No Answer, then configure the number of seconds the device waits before forwarding the call to the specified phone number.

  • Page 581: Configuring Call Waiting

    You can also configure it through ini file (CallWaitingPerPort) or CLI (configure voip > gw analoggw call-waiting).  To enable call waiting per port: Open the Call Waiting table (Configuration tab > VoIP menu > Gateway > Analog Gateway > Call Waiting). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 582: Rejecting Anonymous Calls

    Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 27-7: Call Waiting Table - Edit Row Dialog Box Configure call waiting per port according to the parameters described in the table below. Click Add. Table 27-6: Call Waiting Table Parameter Descriptions...

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

    Index #9 ('Priority Index' 1) in the CPT file for FXS endpoints 1 to 4 when a call is received from a source number with prefix 2. Configure the table as required. For a description of the parameters, see the table below. Click Add. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 584 Mediant 800B Gateway and E- SBC Table 27-7: Tone index Table Parameter Description Parameter Description Index Defines the table index entry. Up to 50 entries can be defined. FXS Port First Defines the first port in the FXS port range.

  • Page 585: Fxs/Fxo Coefficient Types

    FXS Coefficient type. From the 'FXO Coefficient Type' drop-down list (CountryCoefficients), select the required FXO Coefficient type. Click Submit. Save your settings to the flash memory ("burn") with a device reset. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 586: Fxo Operating Modes

    Mediant 800B Gateway and E- SBC 27.13 FXO Operating Modes This section provides a description of the device's FXO operating modes:  For IP-to-Tel calls (see ''FXO Operations for IP-to-Tel Calls'' on page 586)  For Tel-to-IP calls (see ''FXO Operations for Tel-to-IP Calls'' on page 588) ...
  • Page 587 Two-stage dialing implements the Dialing Time feature. Dialing Time allows you to define the time that each digit can be separately dialed. By default, the overall dialing time per digit is 200 msec. The longer the telephone number, the greater the dialing time. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC The relevant parameters for configuring Dialing Time include the following:  DTMFDigitLength (100 msec): time for generating DTMF tones to the PSTN (PBX) side  DTMFInterDigitInterval (100 msec): time between generated DTMF digits to PSTN (PBX) side 27.13.1.3...
  • Page 589 Collecting Digits Mode When automatic dialing is not defined, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 27-11: Call Flow for Collecting Digits Mode Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 590: Call Termination On Fxo Devices

    Mediant 800B Gateway and E- SBC 27.13.2.3 FXO Supplementary Services The FXO supplementary services include the following:  Hold / Transfer toward the Tel side: The ini file parameter LineTransferMode must be set to 0 (default). If the FXO receives a hook-flash from the IP side (using out-of-...
  • Page 591 (allowing detection of caller ID sent between the first and the second rings). If the second ring signal is not received within this timeout, the device doesn't initiate a call to IP. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 592: Remote Pbx Extension Between Fxo And Fxs Devices

    Mediant 800B Gateway and E- SBC 27.13.3.3 Ring Detection Timeout The operation of Ring Detection Timeout depends on the following:  Automatic dialing is disabled and Caller ID is enabled: if the second ring signal is not received for a user-defined time (using the parameter FXOBetweenRingTime), the FXO device doesn’t initiate a call to the IP.

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

    There is one-to-one mapping between PBX lines and FXS device ports. Each PBX line is routed to the same phone (connected to the FXS device). The call disconnects when the phone connected to the FXS device is on-hooked. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 594: Message Waiting Indication For Remote Extensions

    Mediant 800B Gateway and E- SBC 27.14.3 Message Waiting Indication for Remote Extensions The device supports the relaying of Message Waiting Indications (MWI) for remote extensions (and voice mail applications). Instead of subscribing to an MWI server to receive notifications of pending messages, the FXO device receives subscriptions from the remote FXS device and notifies the appropriate extension when messages (and the number of messages) are pending.

  • Page 595: Fxo Gateway Configuration

    In the Trunk Group table page (see Configuring Trunk Groups on page 459), assign the phone numbers 200 to 204 to the device’s FXO endpoints. Figure 27-14: Assigning Phone Numbers to FXO Ports Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 596 Mediant 800B Gateway and E- SBC In the Automatic Dialing page, enter the phone numbers of the FXS device in the ‘Destination Phone Number’ fields. When a ringing signal is detected at Port #1, the FXO device automatically dials the number ‘100’.

  • Page 597: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 599: Sbc Overview

    For example, IP addresses of ITSPs' equipment (e.g. proxies, gateways, and application servers) can be hidden from outside parties. The device's topology hiding is provided by implementing back-to-back user agent (B2BUA) leg routing: Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 600: B2Bua And Stateful Proxy Operating Modes

    Mediant 800B Gateway and E- SBC • 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. • User-defined manipulation of SIP To, From, and Request-URI host names.
  • Page 601 Some SIP functionalities are achieved by conveying the SIP call identifiers either in SIP specific headers (e.g., Replaces) or in the message bodies (e.g. Dialog Info in an XML body). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 602 Mediant 800B Gateway and E- SBC  In some setups, the SIP client authenticates using a hash that is performed on one or more of the headers that B2BUA changes (removes). Therefore, implementing B2BUA would cause authentication to fail. ...

  • Page 603: Call Processing Of Sip Dialog Requests

    The device obtains the source and destination URLs from certain SIP headers. Once the 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. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 604 Mediant 800B Gateway and E- SBC • All SIP requests (e.g., INVITE) except REGISTER: ♦ 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 605: User Registration

    REGISTER messages. For example, you can limit REGISTER requests from a specific IP Group or SRD. Note that this applies only to concurrent REGISTER dialogs and not concurrent registrations in the device's registration database. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 606: Classification And Routing Of Registered Users

    Mediant 800B Gateway and E- SBC 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 more contacts (obtained from the SIP Contact headers).

  • Page 607: General Registration Request Processing

    "late" re-registration to the device. The device removes the user from the database only when this additional time expires. This featured is configured using the 'User Registration Grace Time' parameter (SBCUserRegistrationGraceTime). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 608: Registration Restriction Control

    Mediant 800B Gateway and E- SBC The device keeps registered users in its' registration database even if connectivity with the proxy is lost (i.e., proxy does not respond to users' registration refresh requests). The device removes users from the database only when their registration expiry time is reached (with the additional grace period, if configured).

  • Page 609: Media Anchoring

     Origin: IP address, session and version id  Session connection attribute ('c=' field)  Media connection attribute ('c=' field)  Media port number  RTCP media attribute IP address and port Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 610: Direct Media

    Mediant 800B Gateway and E- SBC The device uses different local ports (e.g., for RTP, RTCP and fax) for each leg (inbound and outbound). The local ports are allocated from the Media Realm associated with each leg. The Media Realm assigned to the leg's IP Group (in the IP Group table) is used. If not assigned to the IP Group, the Media Realm assigned to the leg's SIP Interface (in the SIP Interface table) is used.
  • Page 611 Server (direct media is required in the Lync environment). For more information, see ''Configuring IP Groups'' on page 349. IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 612: Restricting Audio Coders

    Mediant 800B Gateway and 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 613: Coder Transcoding

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

  • Page 616: Transcoding Mode

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

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

    DTMF methods at each leg. This DTMF interworking feature is enabled using IP Profiles (ini file parameter IPProfile):  SBCRFC2833Behavior - affects the RFC 2833 SDP offer-answer negotiation: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 618 Mediant 800B Gateway and E- SBC • [0] (default): the device does not intervene in the RFC 2833 negotiation. • [1]: each outgoing offer-answer includes RFC 2833 in the offered SDP (the device adds RFC 2833 only if the incoming offer does not include RFC 2833).

  • Page 619: Fax Negotiation And Transcoding

    You can define a maximum allowed duration (in minutes) for SBC calls. If an established call reaches this user-defined limit, the device terminates the call. This feature ensures calls are properly terminated, allowing available resources for new calls. This feature is configured using the MaxCallDuration parameter. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 620: Sbc Authentication

    Mediant 800B Gateway and E- SBC 28.8 SBC Authentication The device can authenticate SIP servers and SBC users (clients). The different authentication methods are described in the subsequent subsections. 28.8.1 SIP Authentication Server Functionality The device can function as an Authentication server for authenticating received SIP message requests, based on HTTP authentication Digest with MD5.

  • Page 621: Interworking Sip Signaling

    Changes the host part to the device's IP address – this change causes the remote user agent to send the INVITE to the device.  Adds a special prefix ("T~&R_") to the Contact user part – to identify the new INVITE as a 3xx resultant INVITE. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 622 Mediant 800B Gateway and E- SBC The SBC handling for the 3xx resultant INVITE is as follows: The incoming INVITE is identified as a 3xx resultant INVITE according to the special prefix. The device automatically replaces the SBC host part (in the Request-URI) with the host from the 3xx Contact.

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

    Not present. History-Info History-Info added to Diversion. Disable converted to Diversion. DiversionMode = Add HistoryInfoMode = Add Diversion History-Info Headers are synced and sent. converted to converted to DiversionMode = Add History-Info. Diversion. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 624: Interworking Sip Refer Messages

    Mediant 800B Gateway and E- SBC Parameter Value SIP Header Present in Received SIP Message HistoryInfoMode = Diversion removed. History-Info Both removed. Remove removed. DiversionMode = Remove 28.9.3 Interworking SIP REFER Messages The device supports interworking of SIP REFER messages. SIP UAs may support different versions of the REFER standard while others may not even support REFER.

  • Page 625: Interworking Sip Session Timer

    18x responses (default). This is configured by the IP Profile parameter, 'SBC Remote Multiple 18x Support'.  Early Media RTP: The device supports the interworking with remote clients that send Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 626 Mediant 800B Gateway and E- SBC 18x responses with early media and whose subsequent RTP is delayed, and with remote clients that do not support this and require RTP to immediately follow the 18x response. Some clients do not support 18x with early media, while others require 18x with early media (i.e., they cannot play ringback tone locally).

  • Page 627: Interworking Sip Re-Invite Messages

    SDP and only then forwards it to the destination endpoint. This interworking support is configured by the IP Profile parameter, 'SBC Remote Reinvite Support'. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 628: Interworking Sip Update Messages

    Mediant 800B Gateway and E- SBC 28.9.8 Interworking SIP UPDATE Messages The device supports interworking of the SIP UPDATED message. This enables communication between UAs that generate UPDATE requests and those that do not support the receipt of UPDATE requests. The device does not forward UPDATE requests to IP Groups that do not support it.

  • Page 629: Interworking Sip Via Headers

    Record-Route headers received in the incoming SIP request/response from the other side. Employing IP Profiles, you can configure this interworking feature per SIP entity, using the IpProfile_SBCKeepRoutingHeaders parameter (see ''Configuring IP Profiles'' on page 396). Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 630: Interworking Sip To-Header Tags In Multiple Sdp Answers

    Mediant 800B Gateway and E- SBC 28.9.15 Interworking SIP To-Header Tags in Multiple SDP Answers The device supports the interworking of SIP To-header tags in call forking responses (i.e., multiple SDP answers) between IP entities. The device can either use the same To-header tag value for all SDP answers sent to the SIP entity, or send each SDP answer with its original tag.

  • Page 631: Enabling The Sbc Application

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'SBC Application' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 632 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 633: Configuring General Sbc Settings

    The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP clients behind the device, the call dialog information sent by the application server reflects Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 634 Mediant 800B Gateway and E- SBC only the dialog between the device and itself; not that of the involved SIP clients. This is due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements. The device resolves this by replacing the call identifiers received from the application server with the correct call identifiers (e.g., user A and user B).
  • Page 635 User's Manual 30. Configuring General SBC Settings sip:cjones@example.net </identity> <target uri="sip:line3@host3.example.net"> <param pname="actor" pval="attendant"/> <param pname="automaton" pval="false"/> </target> </remote> </dialog> </dialog-info> Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 636 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 637: 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.0 Mediant 800B Gateway and E- SBC...
  • Page 638 Mediant 800B Gateway and E- SBC routing rule is located, 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 639 Reserved call capacity must be less than the maximum capacity (limit) configured for the CAC rule.  The total reserved call capacity configured for all the CAC rules must be within the device's total call capacity support. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 640 Mediant 800B Gateway and 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 limit special values: [SBCAdmissionControl_Limit]  [0] 0 = Block all these dialogs.

  • Page 641: Configuring Coder Groups

    The Allowed Audio Coders Group for coder restriction takes precedence over the Coder Group for extension coders. In other words, if an extension coder is not listed as an allowed coder, the device does not add the extension coder to the SDP offer. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 642: Configuring Allowed Video Coder Groups

    Mediant 800B Gateway and E- SBC The following procedure describes how to configure Allowed Audio Coder Groups through the Web interface. You can also configure it through ini file (AllowedCodersGroup) or CLI (configure voip > sbc allowed-coders-group group-0).  To configure an Allowed Coders Group: Open the Allowed Audio Coders Group page (Configuration tab >...
  • Page 643 The valid value for user-defined coders is name a string of up to 25 characters (case-insensitive). For [AllowedVideoCodersGroupX_Name] example, "WOW.789" (but without quotes). Note: Each coder type can be configured only once per Allowed Video Coders Group. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 644 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 645: Routing Sbc

    SIP dialog arrived from a registered user. The device searches the database for a user that matches the address-of-record (AOR) and Contact of the incoming SIP message: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 646 Mediant 800B Gateway and E- SBC • Compares the SIP Contact header to the contact value of the user in the database. • Compares the URL in the SIP P-Asserted-Identity/From header to the registered address-of-record (AOR) in the database. If the device finds a matching registered user, it classifies the user to the IP Group associated with the user in the database.
  • Page 647 You can also configure it through ini file (Classification) or CLI (configure voip > sbc routing classification).  To configure a Classification rule: Open the Classification table (Configuration tab > VoIP menu > SBC > Routing SBC > Classification Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 648 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 33-2: Classification Table - Add Row Dialog Box Configure the Classification rule according to the parameters described in the table below. Click Add. Table 33-1: Classification Table Parameter Descriptions...
  • Page 649 Source Host Defines the prefix of the source URI host name as a matching characteristic for the incoming SIP dialog. src-host The URI is typically located in the SIP From header. However, [Classification_SrcHost] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 650 Mediant 800B Gateway and E- SBC Parameter Description you can configure the SIP header from where the device obtains the source URI, in the IP Group table ('Source URI Input' parameter). For more information on how the device obtains this URI, see ''Call Processing of SIP Dialog Requests'' on page 603.

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

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

  • Page 652: Configuring Message Condition Rules

    Mediant 800B Gateway and E- SBC Source Username Destination Index Destination Host Source IP Group Prefix Username Prefix 1111 2000 10.10.10.10 In the IP Group table, add the following IP Groups: Index Source URI Input Destination URI Input P-Called-Party-ID Route In this example, a match exists only for Classification Rule #1.

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

    The IP-to-IP Routing table lets you configure up to 615 SBC IP-to-IP routing rules. Configuration of IP-to-IP routing rules includes two areas:  Rule: Defines the characteristics of the incoming SIP dialog message (e.g., IP Group Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 654 Mediant 800B Gateway and E- SBC from which the message is received).  Action: Defines the action that is done if the incoming call matches the characteristics of the rule (i.e., routes the call to the specified destination). The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call.
  • Page 655 A request sent by the device is responded with one of the following: ♦ SIP response code (i.e., 4xx, 5xx, and 6xx SIP responses) configured in the SBC Alternative Routing Reasons table (see ''Configuring SIP Response Codes for Alternative Routing Reasons'' on page 664). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 656 Mediant 800B Gateway and E- SBC ♦ SIP 408 Timeout or no response (after timeout). • 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).
  • Page 657 Click Add. Table 33-3: IP-to-IP Routing Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [IP2IPRouting_Index] Note: Each row must be configured with a unique index. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 658 Mediant 800B Gateway and E- SBC Parameter Description Routing Policy Assigns an SBC Routing Policy to the rule. The SBC Routing Policy associates the rule with an SRD(s). The SBC Routing sbc-routing-policy-name Policy also defines default LCR settings as well as the LDAP...
  • Page 659 Defines the host part of the incoming SIP dialog’s destination URI (usually the Request-URI). dst-host The default is the asterisk (*) symbol (i.e., any destination host). If [IP2IPRouting_DestHost] this rule is not required, leave this field empty. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 660 Mediant 800B Gateway and E- SBC Parameter Description Message Condition Assigns a SIP Message Condition rule to the IP-to-IP Routing rule. message-condition-name For configuring Message Condition rules, see ''Configuring [IP2IPRouting_MessageConditio Message Condition Rules'' on page 652. nName] Call Trigger Defines the reason (i.e., trigger) for re-routing the SIP request: ...
  • Page 661 INVITE is registered in its' users’ database, and if yes, it sends the INVITE to the address of the corresponding contact specified in the database. If the Request-URI is not registered, the call is rejected. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 662 Mediant 800B Gateway and E- SBC Parameter Description Destination IP Group Defines the IP Group to where you want to route the call. The actual destination of the SIP dialog message depends on the IP dst-ip-group-name Group type (as defined in the 'Type' parameter): [IP2IPRouting_DestIPGroupNam ...
  • Page 663 Group members, if configured (in the rows below it).  Note: Each Forking Group can contain up to 20 members. In other words, up to 20 routing rules can be configured for the same Forking Group. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC Parameter Description Cost Group Assigns a Cost Group to the routing rule for determining the cost of the call. cost-group By default, no value is defined (None). [IP2IPRouting_CostGroup] For configuring Cost Groups, see ''Configuring Cost Groups'' on page 271.
  • Page 665 Defines an index number for the new table row. [SBCAlternativeRoutingReasons_Index] Note: Each row must be configured with a unique index. Release Cause Defines a SIP response code for triggering the device's alternative routing mechanism. rel-cause [SBCAlternativeRoutingReasons_ReleaseCause] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 666: Configuring Sbc Routing Policy Rules

    Mediant 800B Gateway and E- SBC 33.5 Configuring SBC Routing Policy Rules The SBC Routing Policy table lets you configure up to 41 SBC Routing Policy rules. A Routing Policy determines the routing and manipulation (inbound and outbound) rules per SRD in a multiple SRD configuration topology.
  • Page 667 SRD is used. However, if a Routing Policy is configured in 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. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 668 Mediant 800B Gateway and E- SBC Notes: • The Classification table is used only if classification by registered user in the device's users registration database or by Proxy Set fails. • If the device receives incoming calls (e.g., INVITE) from users that have already...
  • Page 669 1. Therefore, a call of 1 minute cost 7 units. Therefore, for calls under one minute, "Weekend A" carries the lower cost. However, if the average call duration is more than one minute, "Weekend B" carries the lower cost. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 670 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 671: Sbc Manipulations

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

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

    The IP Group table can be used to configure a host name that overwrites the received host name. This manipulation can be done for source and destination IP Groups (see ''Configuring IP Groups'' on page 349). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 674 Mediant 800B Gateway and E- SBC The following procedure describes how to configure IP-to-IP Inbound Manipulation rules through interface. also configure through file (IPInboundManipulation) or CLI (configure voip > sbc manipulations ip-inbound- manipulation).  To configure an IP-to-IP Inbound Manipulation rule: Open the IP to IP Inbound Manipulation table (Configuration tab >...
  • Page 675 ''BroadSoft's Shared Phone Line Call Appearance for SBC Survivability'' on page 693. Source IP Group Defines the IP Group from where the incoming INVITE is CLI: src-ip-group-name received. [IPInboundManipulation_SrcIp The default is Any (i.e., any IP Group). GroupName] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 676 Mediant 800B Gateway and E- SBC Parameter Description Source Username Prefix Defines the prefix of the source SIP URI user name (usually in CLI: src-user-name-prefix the From header). [IPInboundManipulation_SrcUs The default is the asterisk (*) symbol (i.e., any source username ernamePrefix] prefix).

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

    IP Groups, respectively. The following procedure describes how to configure IP-to-IP Outbound Manipulation rules through interface. also configure through file (IPOutboundManipulation) or CLI (configure voip > sbc manipulations ip-outbound- manipulation). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 678 Mediant 800B Gateway and E- SBC  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation table (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP-to-IP Outbound). Click Add; the following dialog box appears:...
  • Page 679 Defines the prefix of the calling name (caller ID). The calling name appears in the SIP From header. calling-name-prefix The valid value is a string of up to 37 characters. By default, no [IPOutboundManipulation_Calling Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 680 Mediant 800B Gateway and E- SBC Parameter Description NamePrefix] prefix is defined. Message Condition Assigns a Message Condition rule as a matching characteristic. Message Condition rules define required SIP message formats. message-condition-name For configuring Message Condition rules, see ''Configuring [IPOutboundManipulation_Messa Message Condition Rules'' on page 652.
  • Page 681 SIP dialog or added by the device), a Privacy header is added with the value "id".  [2] Restrict = The user identity is restricted (the restricted presentation is as mentioned above). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 682 Mediant 800B Gateway and E- SBC Parameter Description  [3] Remove Restriction = The device attempts to reveal the user identity by setting user values in the From header and removing the privacy "id" value if the Privacy header exists.

  • Page 683: Advanced Sbc Features

    In the Message Condition table, configure a Message Condition rule to identify incoming emergency calls. See above for examples. For more information on Message Conditions, see ''Configuring Message Condition Rules'' on page 652. Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Mediant 800B Gateway and E- SBC Open the SBC General Settings page (Configuration tab > VoIP > SBC > SBC General Settings), and then scroll down the page to the Call Priority and Preemption group: Figure 35-2: Configuring Emergency SBC Call Preemption From the 'SBC Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable the SBC call preemption feature.

  • Page 685: Webrtc

    The figure below displays an example of a click-to-call application from a customer Web page, where the client needs to enter credentials (username and password) before placing the call. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 686 The WebRTC feature is a license-dependent feature and is available only if it is included in the Software License Key that is installed on the device. For ordering the feature, please contact your AudioCodes sales representative. • The maximum concurrent WebRTC sessions (signaling-over-secure WebSocket and media-over-DTLS) supported by the device is 100.
  • Page 687 When the client clicks the Call button or call link, the browser runs the JavaScript code which sends the HTTP upgrade request for WebSocket in order to establish a WebSocket session with the device. The address of the device is typically included in the JavaScript code. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 688: Sip Over Websocket

    Mediant 800B Gateway and E- SBC A WebSocket session is established between the WebRTC client and the device in order for the WebRTC client to register with the device. This is done using a SIP REGISTER message sent over the WebSocket session (SIP over WebSocket).
  • Page 689 To prevent this, for the IP Profile associated with the WebRTC clients, configure the 'Disconnect on Broken Connection' parameter to Yes. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 690: Configuring Webrtc

    Mediant 800B Gateway and E- SBC 35.3.2 Configuring WebRTC To support WebRTC, you need to perform special configuration settings for the device's SBC leg interfacing with the WebRTC client (i.e., Web browser). The following procedure describes the required configuration. ...

  • Page 691: Call Forking

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

  • Page 692: Call Forking-Based Ip-To-Ip Routing Rules

    Mediant 800B Gateway and E- SBC The device also supports media synchronization for call forking. If the active UA is the first one to send the final response (e.g., 200 OK), the call is established and all other final responses are acknowledged and a BYE is sent if needed. If another UA sends the first final response, it is possible that the SDP answer that was forwarded to the INVITE- initiating UA is irrelevant and thus, media synchronization is needed between the two UAs.

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

    (e.g. 601 and 602) to the primary extension (e.g., 600). Call forking must also be enabled. The following procedure describes the main configuration required. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 694: Call Survivability For Call Centers

    Mediant 800B Gateway and E- SBC Notes: • The device enables outgoing calls from all equipment that share the same line simultaneously (usually only one simultaneous call is allowed per a specific shared line). • You can configure whether REGISTER messages from secondary lines are terminated on the device or forwarded transparently (as is), using the SBCSharedLineRegMode parameter.
  • Page 695 In the Classification table (see ''Configuring Classification Rules'' on page 645), add rules to classify incoming calls that are received from the entities listed in Step 1, to IP Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 696 Mediant 800B Gateway and E- SBC Groups. In the SBC IP-to-IP Routing table (see ''Configuring SBC IP-to-IP Routing Rules'' on page 653), add the following IP-to-IP routing rules: • For normal operation: ♦ Routing from TDM Gateway to Application server.

  • Page 697: Survivability Mode Display On Aastra Ip Phones

    OK to the next alternative destination. This new destination can be the next given IP address resolved from a DNS from the Contact or Record-Route header in the request related to the response. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 698 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 699: Cloud Resilience Package

    Part VII Cloud Resilience Package...

  • Page 701: Crp Overview

    Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
  • Page 702 Mediant 800B Gateway and E- SBC Survivability Quality of Experience/Service Security  Short number dialog (short numbers are learned dynamically in the registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if IP phone initiates REFER) ...

  • Page 703: Crp Configuration

    IP PBX, and routes the calls based on the IP-to-IP routing rules. If communication with the IP PBX fails (i.e., Emergency mode), it still allows calls between the branch users themselves. If this fails, it routes the calls to the PSTN Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 704 Mediant 800B Gateway and E- SBC (if employed). Figure 37-1: CRP in Normal & Auto Answer to Registrations Modes  Auto Answer to Registrations: This mode is the same as the Normal mode, except that the CRP registers the branch users in its registration database instead of forwarding them to the IP PBX.

  • Page 705: Pre-Configured Ip Groups

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

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

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

  • Page 707: Emergency Mode

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

  • Page 708: Configuring Pstn Fallback

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

  • Page 709: High-Availability System

    Part VIII High-Availability System...

  • Page 711: Ha Overview

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

    Mediant 800B Gateway and E- SBC Note: If the active unit runs an earlier version (e.g., 6.8) than the redundant unit (e.g., 7.0), the redundant unit is downgraded to the same version as the active unit (e.g., 6.8). 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 713 After HA switchover, the active device updates other hosts in the network about the new mapping of its Layer-2 hardware address to the global IP address, by sending a broadcast gratuitous Address Resolution Protocol (ARP) message. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 714: Ha Status On The Home Page

    Mediant 800B Gateway and E- SBC 38.3 HA Status on the Home Page The Home page of the device's Web interface displays the status of the HA system. The Home page provides a graphical display of both active and redundant devices.

  • Page 715: Ha Configuration

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

  • Page 716: Configuring The Ha Devices

    Mediant 800B Gateway and E- SBC  If the two devices are connected through two (or more) isolated LAN switches (i.e., packets from one switch cannot traverse the second switch), configure the mode to 2RX/2TX: Figure 39-2: Redundancy Mode for Two Isolated Switches ...
  • Page 717 Make sure that the Maintenance interface uses an Ethernet Device and Ethernet Group that is not used by any other network interface. The Ethernet Group is associated with the Ethernet Device assigned to the interface in the 'Underlying Device' field. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 718 Mediant 800B Gateway and E- SBC The Interface table below shows an example where the Maintenance interface is assigned to Ethernet Device "vlan 2" (which is associated with Ethernet Group "GROUP_2") in the 'Underlying Device' field, while the other interface is assigned to "vlan 1"...
  • Page 719 HA so that the devices become operational in HA. This last stage applies to both devices.  To initialize the devices for HA: Cable the devices to the network. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 720 Mediant 800B Gateway and E- SBC Note: You must connect both ports (two) in the Ethernet Group of the Maintenance interface to the network (i.e., two network cables are used). This provides 1+1 Maintenance port redundancy. Power up the devices; the redundant device synchronizes with the active device and updates its configuration according to the active device.

  • Page 721: Configuration While Ha Is Operational

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

  • Page 722: Configuring Firewall Allowed Rules

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

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

    • In the 'HA Network Reachability Ping Timeout' field, set the timeout for which the ping request waits for a response. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 724 Mediant 800B Gateway and E- SBC • In the 'HA Network Reachability Ping Retries' field, set the number of ping requests that the device sends after no ping response is received from the destination, before the destination is declared unavailable.

  • Page 725: Ha Maintenance

    If you need to replace a non-functional device with a new one, the new device must be configured exactly as the second device, as described in ''Configuring the HA Devices'' on page 716. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 726: Forcing A Switchover

    Mediant 800B Gateway and E- SBC 40.3 Forcing a Switchover If required, you can force a switchover between active and redundant units. For more information, see ''High Availability Maintenance'' on page 733. 40.4 Software Upgrade The following types of software upgrades are available on the HA system: ...

  • Page 727: Maintenance

    Part IX Maintenance...

  • Page 729: Basic Maintenance

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

  • Page 730: Remotely Resetting Device Using Sip Notify

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

  • Page 731: Locking And Unlocking The Device

    Under the Misc Parameters group, set the 'SIP Remote Rest' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. 41.3 Locking and Unlocking the Device The Lock and Unlock option allows you to lock the device so that it doesn't accept any new calls and maintains only the current calls.

  • Page 732: Saving Configuration

    Mediant 800B Gateway and E- SBC Note: The Home page's General Information pane displays whether the device is locked or unlocked (see ''Viewing the Home Page'' on page 64). 41.4 Saving Configuration The Maintenance Actions page allows you to save (burn) the current parameter configuration (including loaded Auxiliary files) to the device's non-volatile memory (i.e.,...

  • Page 733: High Availability Maintenance

    When resetting the Redundant unit, the HA mode becomes temporarily unavailable.  To reset the Redundant unit: Open the High Availability Maintenance page: • Navigation menu tree: Maintenance tab > Maintenance menu > High Availability Maintenance Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 734 Mediant 800B Gateway and E- SBC • Toolbar: Click the Device Actions button, and then choose Reset Redundant Figure 42-2: High Availability Maintenance Page Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK.

  • Page 735: Channel Maintenance

    Click the required FXS or FXO port icon; a shortcut menu appears. From the shortcut menu, choose Reset Channel; the channel is changed to inactive and the port icon is displayed in gray. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 736: Restarting A B-Channel

    Mediant 800B Gateway and E- SBC 43.3 Restarting a B-Channel You can restart a specific B-channel belonging to an ISDN or CAS trunk, using the SNMP MIB variable, acTrunkISDNCommonRestartBChannel. This may be useful, for example, for troubleshooting specific voice channels.
  • Page 737 When HA synchronization finishes and HA status is in "Operational" state, the Trunk Group Settings table is refreshed with the lock/unlock status. The HA state is displayed on the Home page. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 738 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 739: Software Upgrade

    Web interface - see ''Loading Auxiliary Files through Web Interface'' on page 740  CLI - see Loading Auxiliary Files through CLI on page 741  TFTP - see ''Loading Auxiliary Files through ini File using TFTP'' on page 741 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 740 Mediant 800B Gateway and E- SBC Notes: • You can schedule automatic loading of updated Auxiliary files using HTTP/HTTPS. For more information, 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 731.

  • Page 741: Deleting Auxiliary Files

    Auxiliary files as defined in the ini file, through TFTP. 44.1.2 Deleting Auxiliary Files You can delete loaded Auxiliary files through the Web interface, as described below. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 742: Call Progress Tones File

    AudioCodes DConvert utility. For a description on converting a CPT ini file into a binary dat file, refer to the DConvert Utility User's Guide.
  • Page 743 (for cadence tones). For burst tones, the parameter defines the off time required after the burst tone ends and the tone detection is reported. For continuous tones, the parameter is ignored. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 744: Distinctive Ringing

    Mediant 800B Gateway and E- SBC • Second Signal On Time [10 msec]: 'Signal On' period (in 10 msec units) for the second cadence on-off cycle. Can be omitted if there isn't a second cadence. • Second Signal Off Time [10 msec]: 'Signal Off' period (in 10 msec units) for the second cadence on-off cycle.
  • Page 745 An example of a ringing burst definition is shown below: #Three ringing bursts followed by repeated ringing of 1 sec on and 3 sec off. [NUMBER OF DISTINCTIVE RINGING PATTERNS] Number of Ringing Patterns=1 [Ringing Pattern #0] Ring Type=0 Freq [Hz]=25 Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 746: Prerecorded Tones File

    Mediant 800B Gateway and E- SBC First Burst Ring On Time [10msec]=30 First Burst Ring Off Time [10msec]=30 Second Burst Ring On Time [10msec]=30 Second Burst Ring Off Time [10msec]=30 Third Burst Ring On Time [10msec]=30 Third Burst Ring Off Time [10msec]=30...

  • Page 747: Cas Files

    For SBC calls, the PRT file supports only the ringback tone and hold tone. The prerecorded tones can be created using standard third-party, recording utilities such as Adobe Audition, and then combined into a single file (PRT file) using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).
  • Page 748 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 739.
  • Page 749 Create a new file using a text-based editor (such as Notepad) and configure your Dial 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. Version 7.0...
  • Page 750 Mediant 800B Gateway and E- SBC Install the converted file on the device, as described in ''Loading Auxiliary Files'' on page 739. The required Dial Plan is selected using the 'Dial Plan Index' parameter. The parameter can be set to 0 through 7, where 0 denotes PLAN1, 1 denotes PLAN2, and so on.
  • Page 751 • Prefix tags for called number prefixes: 'IP-to-Tel Tagging Destination Dial Plan Index' parameter • Prefix tags for calling number prefixes: 'IP-to-Tel Tagging Source Dial Plan Index' parameter Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 752 Mediant 800B Gateway and E- SBC Open the IP to Trunk Group Routing table (Configuration tab > VoIP menu > Gateway > Routing > IP to Trunk Group Routing). From the 'IP-to-Tel Routing Mode' drop-down list, select Route calls before manipulation so that the device performs the routing processing before manipulation.
  • Page 753 'Prefix to Add' or 'Suffix to Add' fields, using the following syntax: $DialPlan<x>, where x is the Dial Plan index (0 to 7). For example, if the called number is 4252000555, the device manipulates it to LOCL4252000555. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 754: Obtaining Ip Destination From Dial Plan File

    Mediant 800B Gateway and E- SBC Add an SBC IP-to-IP routing rule using the prefix tag to represent the different source or destination URI user parts: Open the IP-to-IP Routing table (Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table), and then click Add.
  • Page 755 Dial Plan file, if the parameter 'Tel To IP Routing Mode' is set to 'Route calls after manipulation'. • Source number Tel-to-IP manipulation is performed on the modified source number as defined in the Dial Plan file. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 756: User Information File

    Mediant 800B Gateway and E- SBC 44.1.6.6 Viewing Information of Installed Dial Plan File You can view information about the Dial Plan file currently installed on the device, through the device's CLI:  Viewing Dial Plan file information: You can view the file name of the installed Dial...
  • Page 757 CLI - see Configuring GW User Info Table through CLI on page 759  Loadable User Info file - see ''Configuring GW User Info Table in Loadable Text File'' on page 760 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 758 Mediant 800B Gateway and E- SBC Notes: • To enable user registration, set the following parameters on the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration) as shown: √ 'Enable Registration': Enable (IsRegisterNeeded is set to 1).
  • Page 759 (sip-def-proxy-and-reg)# user-info gw-user-info display ---- gw-user-info-0 ---- pbx-ext (405) global-phone-num (405) display-name (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered)  To view a specific entry (example): (sip-def-proxy-and-reg)# user-info gw-user-info <index, e.g., 0> Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 760 Mediant 800B Gateway and E- SBC (gw-user-info-0)# display pbx-ext (405) global-phone-num (405) display-name (Ext405) username (user405) password (0aGzoKfh5uI=) status (not-resgistered)  To search a user by pbx-ext: (sip-def-proxy-and-reg)# user-info find <pbx-ext e.g., 405> 405: Found at index 0 in GW user info table, not registered 44.1.7.2.3 Configuring GW User Info Table in Loadable Text File...
  • Page 761 Open the SBC User Info table (Configuration tab > VoIP menu > SIP Definitions > User Information > SBC User Info Table). Click Add; the following dialog box appears: Figure 44-4: SBC User Info Table - Add Row Dialog Box Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 762 Mediant 800B Gateway and E- SBC Configure the SBC User Info table parameters according to the table below. Click Add. To save the changes to flash memory, see ''Saving Configuration'' on page 732. To register a user, select the user's table entry, and then from the Action button's drop- down list, choose Register.
  • Page 763 URI source host part for the AOR in the database Note: To modify the SBC User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 764: Amd Sensitivity File

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

  • Page 765: Software License Key

    Before you can install a new Software License Key, you need to obtain a Software License Key file for your device with the required features from your AudioCodes representative. The Software License Key is an encrypted key in string format that is associated with the device's serial number ("S/N") and supplied in a text-based file.

  • Page 766: Installing The Software License Key

    Install the Software License Key on the device, as described in ''Installing the Software License Key'' on page 766. 44.2.2 Installing the Software License Key Once you have received your Software License Key file from your AudioCodes representative, you can install it on the device using one of the following management tools: ...
  • Page 767 To install the Software License Key through CLI, use the following commands:  To install the Software License Key: (config-system)# feature-key <"string enclosed in double quotation marks">  To view the Software License Key: show system feature-key Version 7.0 Mediant 800B Gateway and E- SBC...

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

    Manager Server The device can receive SBC capacity licenses from a centralized pool of SBC resources managed by the License Pool Manager Server running on AudioCodes EMS. The License Pool Manager Server can dynamically allocate and de-allocate SBC capacity licenses from the pool to devices in the network to meet capacity demands of each device whenever required.
  • Page 769 If the device is allocated an SBC license by the License Pool Manager Server that exceeds the maximum number of sessions that it can support, the device sets the number of sessions to its maximum supported Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 770: Software Upgrade Wizard

    If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
  • Page 771 On the toolbar, click Device Actions, and then choose Software Upgrade Wizard. Figure 44-7: Start Software Upgrade Wizard Screen Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 772 Mediant 800B Gateway and E- SBC Note: At this stage, you can quit the Software Upgrade Wizard without having to reset the device, by clicking Cancel . However, if you continue with the wizard and start loading the cmp file, the upgrade process must be completed with a device reset.
  • Page 773 If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file running on the device) and thereby, overwrite values previously configured for these parameters. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 774 Mediant 800B Gateway and E- SBC When you have completed loading all the desired files, click Next until the last wizard page appears (the FINISH button is highlighted in the left pane): Figure 44-9: Software Upgrade Wizard - Files Loaded Click Reset to burn the files to the device's flash memory;...

  • Page 775: Backing Up And Loading Configuration File

    On the toolbar, click Device Actions, and then from the drop-down menu, choose Load Configuration File or Save Configuration File. Figure 44-11: Configuration File Page To save the ini file to a folder on your computer: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 776 Mediant 800B Gateway and E- SBC Click the Save INI File button; the File Download dialog box appears. Click the Save button, navigate to the folder where you want to save the file, and then click Save. To load the ini file to the device: Click the Browse button, navigate to the folder where the file is located, select the file, and then click Open;...

  • Page 777: Automatic Provisioning

    Open the Application Settings page (Configuration tab > System menu > Application Settings). Figure 45-1: Enabling DHCP - Application Settings Page From the 'Enable DHCP" drop-down list, select Enable. Click Submit. To activate the DHCP process, reset the device. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 778 Mediant 800B Gateway and E- SBC The following shows an example of a configuration file for a Linux DHCP server (dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server"...

  • Page 779: Http-Based Provisioning

    The only configuration required is to preconfigure the device(s) with the URL of the initial (master) ini file. This can be done using one of the following methods:  DHCP as described in ''DHCP-based Provisioning'' on page 777 or via TFTP at a Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 780: Ftp- Based Provisioning

    778 is that the protocol in the URL is "ftp" (instead of "http"). 45.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 781: Http/S-Based Provisioning Using The Automatic Update Feature

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

  • Page 782: Triggers For Automatic Update

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

  • Page 783: Access Authentication With Http Server

    (working in conjunction with the HTTP If- Modified-Since header, described further on in this section). You can configure the information sent in the User-Agent header, using the AupdHttpUserAgent parameter or CLI command, configure system > http-user-agent. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 784 Mediant 800B Gateway and E- SBC The information can include any user-defined string or the following supported string variable tags (case-sensitive): • <NAME>: product name, according to the installed Software License Key • <MAC>: device's MAC address • <VER>: software version currently installed on the device, e.g., "7.00.200.001"...
  • Page 785 If the serial number is the same and the license key is different to the one currently installed on the device, it applies the new License Key. For devices in HA mode, the License Key is applied to both active and redundant units. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 786: File Download Sequence

    Mediant 800B Gateway and E- SBC If the device receives an HTTP 301/302/303 redirect response from the provisioning server, it establishes a connection with the new server at the redirect URL and re- sends the HTTP Get request. 45.2.6 File Download Sequence...

  • Page 787: Mac Address Automatically Inserted In Configuration File Name

    Configure the device with the IP address of the DNS server for resolving the domain name (e.g., http://www.company.com) that is used in the URL of the provisioning server. You configure this in the Interface table: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 788 Mediant 800B Gateway and E- SBC • ini File: [ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] •...
  • Page 789 Configure the device with the IP address of the DNS server for resolving the domain names of the FTPS and HTTP servers: [ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 790: Automatic Update For Mass Deployment

    Mediant 800B Gateway and E- SBC InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] Configure the device to perform the Automatic Update process daily at 03:00 (3 a.m): •...
  • Page 791 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 voip (config-voip)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100 Power down and then power up the device. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 793: Restoring Factory Defaults

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

  • Page 794: Restoring Defaults Using Hardware Reset Button

    Mediant 800B Gateway and E- SBC  To restore factory defaults through Web interface: Open the Configuration File page: • Toolbar: From the Device Actions drop-down list, choose Restore Defaults • Navigation Tree: Maintenance tab > Software Update > Configuration File...

  • Page 795: Restoring Defaults Through Ini File

    ";") so that the device ignores them. Note: The only settings that are not restored to default are the management (OAMP) LAN IP address and the Web interface's login user name and password. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 797: Automatic Archiving Of Configuration File

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

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

  • Page 801: Status, Performance Monitoring And Reporting

    Part X Status, Performance Monitoring and Reporting...

  • Page 803: System Status

    Ethernet Port Info).  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu > Ethernet Port Info Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 804: Reporting Dsp Utilization Through Snmp Mib

    Mediant 800B Gateway and E- SBC • On the Home page, click any Ethernet port on the graphical display of the device (see ''Viewing the Home Page'' on page 64) Table 49-1: Ethernet Port Information Parameters Parameter Description Port Name Displays the name of the port.

  • Page 805: Carrier-Grade Alarms

     To view history alarms:  Open the Alarms History table (Status & Diagnostics tab > System Status menu > Carrier-Grade Alarms > Alarms History). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 806 Mediant 800B Gateway and E- SBC For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised ...

  • Page 807: Performance Monitoring

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

  • Page 808: Viewing Trunk Utilization

    Mediant 800B Gateway and E- SBC 51.2 Viewing Trunk Utilization The Trunk Utilization page provides an X-Y graph that displays the number of active channels per trunk over time. The x-axis indicates the time; the y-axis indicates the number of active trunk channels.
  • Page 809 Instead of using the buttons, you can use the slide ruler. As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 810: Viewing Quality Of Experience

    Mediant 800B Gateway and E- SBC 51.3 Viewing Quality of Experience The Quality Of Experience page provides statistical information on calls per SRD or IP Group. The statistics can be further filtered to display incoming and/or outgoing call direction, and type of SIP dialog (INVITE, SUBSCRIBE, or all).

  • Page 811: Viewing Average Call Duration

    The Quality Of Experience page is applicable only to SBC calls.  To view average call duration: Open the Average Call Duration page (Status & Diagnostics tab > Performance Monitoring menu > Average Call Duration). Figure 51-4: Average Call Duration Graph Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 812 Mediant 800B Gateway and E- SBC From the 'SRD/IpGroup' drop-down list, select whether you want to view information for an SRD or IP Group. From the 'Index' drop-down list, select the SRD or IP Group index. Use the Zoom In button to increase the displayed time resolution or the Zoom Out button to decrease it.

  • Page 813: Voip Status

    Light Orange D-Channel Alarm Dark Orange NFAS Alarm Purple Lower Layer Down (DS3 physical layer is disabled) The status of the channels is depicted by color-coded icons, as described in the table below: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 814 Mediant 800B Gateway and E- SBC Table 52-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls Green Active Call in progress (RTP traffic) and no alarms...

  • Page 815: Viewing Analog Port Information

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

  • Page 816: Viewing Active Ip Interfaces

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

  • Page 817: Viewing Ethernet Device Status

    To view the status of static IP routing:  Open the IP Routing Status table (Status & Diagnostics tab > VoIP Status menu >Static Route Status). Figure 52-5: IP Routing Status Table Page Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 818: Viewing Performance Statistics

    Mediant 800B Gateway and E- SBC 52.7 Viewing Performance Statistics The Basic Statistics page provides read-only, device performance statistics. This page is refreshed every 60 seconds. The duration that the currently displayed statistics has been collected is displayed above the statistics table.
  • Page 819 Displays the reason for the call being released (ended). For example, Termination Reason "NORMAL_CALL_CLEAR" indicates a normal off-hook (hang up) of the call party. Session ID Displays the SIP session ID of the call. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 820: Viewing Call Counters

    Mediant 800B Gateway and E- SBC 52.9 Viewing Call Counters The IP to Tel Calls Count page and Tel to IP Calls Count page provide you with statistical information on incoming (IP-to-Tel) and outgoing (Tel-to-IP) calls. The statistical information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call Call Detail Record or CDR message is sent).
  • Page 821 15 minute period. Attempted Fax Calls Indicates the number of attempted fax calls. Counter Successful Fax Calls Indicates the number of successful fax calls. Counter Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 822: Viewing Registered Users

    Mediant 800B Gateway and E- SBC 52.10 Viewing Registered Users You can view SAS and SBC users listed in the device's Users Registration database. The list shows each Address of Record (AOR) and its corresponding contact. The contact's registration status is also shown: ...

  • Page 823: Viewing Registration Status

    The registration mode (i.e., per device, endpoint, account. or no registration) is configured in the Trunk Group Settings table (see Configuring Trunk Group Settings on page 461) or using the TrunkGroupSettings ini file parameter. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 824: Viewing Call Routing Status

    Mediant 800B Gateway and E- SBC 52.12 Viewing Call Routing Status The Call Routing Status page provides you with information on the current routing method used by the device. This information includes the IP address and FQDN (if used) of the Proxy server with which the device currently operates.

  • Page 825: Viewing Ip Connectivity

    The status of the IP address' connectivity according to the method in the Status 'Connectivity Method' field.  OK = Remote side responds to periodic connectivity queries.  Lost = Remote side didn't respond for a short period. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 826 Mediant 800B Gateway and E- SBC Column Name Description  Fail = Remote side doesn't respond.  Init = Connectivity queries not started (e.g., IP address not resolved).  Disable = The connectivity option is disabled, i.e., parameter 'Alt Routing Tel to IP Mode' (AltRoutingTel2IPMode ini) is set to 'None' or 'QoS'.

  • Page 827: Reporting Information To External Party

    You can configure the device to send RTXP XR at the end of each call and according to a user-defined interval between consecutive reports. Table 53-1: RTCP XR Published VoIP Metrics Group Metric Name General Start Timestamp Stop Timestamp Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 828 Mediant 800B Gateway and E- SBC Group Metric Name Call-ID Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment...
  • Page 829 LocalAddr: IP=172.17.116.201 Port=6000 SSRC=0x54c62a13 RemoteAddr: IP=172.17.116.202 Port=6000 SSRC=0x243220dd LocalGroup: RemoteGroup: LocalMAC: 00:90:8f:57:d9:71 LocalMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z SessionDesc: PT=8 PD=PCMA SR=8000 FD=20 PLC=3 SSUP=Off JitterBuffer: JBA=3 JBR=0 JBN=7 JBM=10 JBX=300 PacketLoss: NLR=0.00 JDR=0.00 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 830 Mediant 800B Gateway and E- SBC BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=6325 GMIN=16 Delay: RTD=0 ESD=11 Signal: SL=-34 NL=-67 RERL=17 QualityEst: RLQ=93 MOSLQ=4.1 MOSCQ=4.10 RemoteMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z JitterBuffer: JBA=3 JBR=0 JBN=0 JBM=0 JBX=300 PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=0 GMIN=16...

  • Page 831: Generating Call Detail Records

    The default CDR fields for SBC signaling are listed in the table below. A typical SBC session consists of two SBC legs. Each leg generates its own signaling CDRs. Each leg generates three CDR types: at call start (SBCReportType=CALL_START), Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 832 Mediant 800B Gateway and E- SBC connect time (SBCReportType=CALL_CONNECT) when call ends (SBCReportType=CALL_END). CDRs belonging to the same SBC session (both legs) have the same Session ID (SessionId CDR field). CDRs belonging to the same SBC leg have the same SIP Call ID (SIPCallId CDR field).
  • Page 833 String of up to 35 characters Redirect reason String of up to 15 characters RedirectReason RedirectURINum Redirection URI String of up to 41 characters RedirectURINumBefo Redirect URI number before manipulation String of up to 41 characters reMap Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 834 Mediant 800B Gateway and E- SBC CDR Field Name Description Format TxSigIPDiffServ Signaling IP DiffServ String of up to 15 characters IPGroup IP Group ID and name String of up to 40 characters SrdId SRD ID and name String of up to 29 characters...
  • Page 835 R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable. LocalMosCQ Local MOS for conversation RemoteMosCQ Remote MOS for conversation Media IP DiffServ TxRTPIPDiffServ Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 836: Cdr Fields For Gateway Application

    Mediant 800B Gateway and E- SBC CDR Field Name Description LatchedRtpIp Remote IP address of the incoming RTP stream that the device "latched" on to as a result of the RTP latching mechanism for NAT traversal. LatchedRtpPort Remote RTP port of the incoming RTP stream that the device "latched"...
  • Page 837 RTP jitter RTPjitter RTPssrc Local RTP SSRC RemoteRTPssrc Remote RTP SSRC RedirectReason Redirect reason Redirection phone number type Redirection phone number plan Redirection phone number RedirectPhonNum MeteringPulses Number of generated metering pulses Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 838 Mediant 800B Gateway and E- SBC Field Name Description SrcHost Source host name SrcHostBeforeMap Source host name before manipulation DstHost Destination host name Destination host name before manipulation DstHostBeforeMap IP Group description LocalRtpIp Remote RTP IP address LocalRtpPort Local RTP port...
  • Page 839 Latching of a new T.38 stream - new port 53.2.1.3.1 Release Reasons in CDR for Gateway Application The possible reasons for call termination for the Gateway application which is represented in the CDR field TrmReason are listed below: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 840 Mediant 800B Gateway and E- SBC  "REASON N/A"  "RELEASE_BECAUSE_NORMAL_CALL_DROP"  "RELEASE_BECAUSE_DESTINATION_UNREACHABLE"  "RELEASE_BECAUSE_DESTINATION_BUSY"  "RELEASE_BECAUSE_NOANSWER"  "RELEASE_BECAUSE_UNKNOWN_REASON"  "RELEASE_BECAUSE_REMOTE_CANCEL_CALL"  "RELEASE_BECAUSE_UNMATCHED_CAPABILITIES"  "RELEASE_BECAUSE_UNMATCHED_CREDENTIALS"  "RELEASE_BECAUSE_UNABLE_TO_HANDLE_REMOTE_REQUEST"  "RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT"  "RELEASE_BECAUSE_CONFERENCE_FULL"  "RELEASE_BECAUSE_VOICE_PROMPT_PLAY_ENDED"  "RELEASE_BECAUSE_VOICE_PROMPT_NOT_FOUND"  "RELEASE_BECAUSE_TRUNK_DISCONNECTED"  "RELEASE_BECAUSE_RSRC_PROBLEM" ...
  • Page 841  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST"  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED"  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING"  "GWAPP_MESSAGE_TYPE_NON_EXISTENT"  "GWAPP_MESSAGE_STATE_INCONSISTENCY" Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 842 Mediant 800B Gateway and E- SBC  "GWAPP_NON_EXISTENT_IE"  "GWAPP_INVALID_IE_CONTENT"  "GWAPP_MESSAGE_NOT_COMPATIBLE"  "GWAPP_RECOVERY_ON_TIMER_EXPIRY"  "GWAPP_PROTOCOL_ERROR_UNSPECIFIED"  "GWAPP_INTERWORKING_UNSPECIFIED"  "GWAPP_UKNOWN_ERROR"  "RELEASE_BECAUSE_HELD_TIMEOUT" 53.2.1.4 CDR Fields for Locally Stored SBC The CDR fields for SBC calls that are stored locally (history) on the device are listed in the table below.

  • Page 843: Customizing Cdrs For Gateway Calls

    The following procedure describes how to customize Gateway CDRs through the Web interface. You can also configure it through ini file (GWCDRFormat) or CLI (configure voip > services cdr > cdr-format gw-cdr-format). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 844 Mediant 800B Gateway and E- SBC  To customize Gateway CDRs: Open the Gateway CDR Format table (Configuration tab > System menu > Call Detail Record > Gateway CDR Format). Click Add; the following dialog box appears: Figure 53-2: Gateway CDR Format Table - Add Row Dialog Box Configure the CDR according to the parameters described in the table below.
  • Page 845 'CDR Type' parameter configured to RADIUS Gateway). RADIUS Attribute ID Defines an ID for the RADIUS Attribute. For vendor-specific Attributes, this represents the VSA ID; for standard attributes, this represents the radius-id Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 846: Customizing Cdrs For Sbc Calls

    Mediant 800B Gateway and E- SBC Parameter Description [GWCDRFormat_Radius Attribute ID (first byte of the Attribute). The valid value is 0 to 255 (one byte). The default is 0. Notes:  The parameter is applicable only for RADIUS accounting (i.e., 'CDR Type' parameter configured to RADIUS Gateway).
  • Page 847 CDR Type Defines the application type for which you want to customize CDRs.  cdr-type [1] Syslog SBC = (Default) Customizes CDR fields for SIP signaling- related CDRs sent in Syslog messages. [SBCCDRFormat_CDRT Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 848 Mediant 800B Gateway and E- SBC Parameter Description  ype] [3] Syslog Media = Customizes CDR fields for media-related CDRs sent in Syslog messages.  [5] History SBC = Customizes CDR fields that are stored locally on the device. ...
  • Page 849 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.0 Mediant 800B Gateway and E- SBC...

  • Page 850: Configuring Cdr Reporting

    Mediant 800B Gateway and E- SBC 53.2.4 Configuring CDR Reporting The following procedure describes how to configure CDR reporting.  To configure CDR reporting: Enable the Syslog feature for sending log messages generated by the device to a collecting log message server. For more information, see ''Enabling Syslog'' on page 875.
  • Page 851 Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings), and then scroll down to the Local Storage group: Figure 53-7: CDR Local Storage on Logging Settings Page Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 852: Configuring Radius Accounting

    Mediant 800B Gateway and E- SBC Configure the following parameters: • 'CDR Local Max File Size' (CDRLocalMaxFileSize): Enter the maximum size (in kilobytes) of the CDR file. Once the file size is reached, the device creates a new file for subsequent CDRs, and so on.
  • Page 853 Wireshark's interpretation of the RADIUS information in a more readable format. The example shows the attribute in string-of-characters format. Figure 53-11: Example of Vendor-Specific RADIUS Attribute Collected by Wireshark Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 854 Mediant 800B Gateway and E- SBC Notes: • You can customize the prefix title of the RADIUS attribute name and the ID. For more information, see Customizing CDRs for Gateway Calls on page 843 and Customizing CDRs for SBC Calls on page 846.
  • Page 855 Name of the String h323-gw-id=<SIP Start gateway ID string> Stop sip-call-id SIP Call ID String sip-call- Start id=abcde@ac.com Stop call- Terminator of the String call-terminator=yes Stop terminator call:  "yes": Call Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 856 Mediant 800B Gateway and E- SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID terminated by the Tel side (Gateway) or outgoing leg (SBC)  "no": Call terminated by the IP side (Gateway) or incoming leg...
  • Page 857 Below is an example of RADIUS Accounting, where non-standard parameters are preceded with brackets: Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213 nas-port-type = 0 acct-status-type = 2 acct-input-octets = 4841 acct-output-octets = 8800 acct-session-time = 1 Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 858: Querying Device Channel Resources Using Sip Options

    Mediant 800B Gateway and E- SBC 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 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16)

  • Page 859: Diagnostics

    Part XI Diagnostics...

  • Page 861: Syslog And Debug Recording

    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.0 Mediant 800B Gateway and E- SBC...
  • Page 862 Mediant 800B Gateway and E- SBC Notes: • If you want to configure a Logging 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 875).
  • Page 863 For more information on configuring IP traces, see ''Filtering IP Network Traces'' on page 865.  [14] SIP Interface = Filters log according to SIP Interface. For configuring SIP Interfaces, see Configuring SIP Interfaces on page 342. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 864 Mediant 800B Gateway and E- SBC Parameter Description Value Defines the value for the selected filtering type in the 'Filter Type' parameter. The value can include the following: value  A single value. [LoggingFilters_Valu  A range, using a hyphen "-" between the two values. For example, to specify IP Groups 1, 2 and 3, configure the parameter to "1-3"...

  • Page 865: 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.0 Mediant 800B Gateway and E- SBC...
  • Page 866 Mediant 800B Gateway and E- SBC Wireshark-like filtering expressions for your IP trace. The following Wireshark-like expressions are supported: Table 54-1: Supported Wireshark-like Expressions for 'Value' Parameter Expression Description ip.src, ip.dst Source and destination IP address ip.addr IP address - up to two IP addresses can be entered ip.proto...

  • Page 867: Configuring Syslog

    For example, in the below Syslog, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 868 Mediant 800B Gateway and E- SBC Message Item Description numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE:...
  • Page 869 User's Manual 54. Syslog and Debug Recording Message Item Description value for calls traversing multiple AudioCodes' devices. For more information, see ''Maintaining Same Syslog SID/BID over Multiple Devices'' on page 871. Board ID (BID) Unique non-SIP session related (e.g., device reset or a Trunk alarm) and device identifier.
  • Page 870 Mediant 800B Gateway and E- SBC Error Abbreviation Error Name Description Simple Aggregation Packets Lost Command Checksum Error Invalid Cell Coder Code Command Sequence Error 8 sec Timeout Before Disconnect Host Received Overrun Invalid AMR Payload Invalid CID Error Invalid G723 Code...
  • Page 871 You can enable the device to maintain the same SIP session ID (SID) and board ID (BID) in debug log messages (Syslog) for calls traversing multiple AudioCodes' devices. The feature is useful in that it allows you to use a single SID/BID to easily identify log messages pertaining to the same call session even though it has traversed multiple devices.
  • Page 872 Mediant 800B Gateway and E- SBC 54.2.1.4 Syslog Fields for Answering Machine Detection (AMD) The Syslog message can include information relating to the Answering Machine Detection (AMD) feature. AMD is used to detect whether a human (including a fax machine), an answering machine, silence, or answering machine beeps have answered the call on the remote side.

  • Page 873: Configuring Web User Activities To Report To Syslog

    You can also view logged user activities in the Web interface (see ''Viewing Web User Activity Logs'' on page 877). • Logging of CLI commands can only be configured through CLI or ini file. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 874: Configuring Syslog Debug Level

    Mediant 800B Gateway and E- SBC The following procedure describes how to configure Web user activity logging through the Web interface. You can also configure it through ini file (ActivityListToLog) or CLI (config- system > logging > activity-log).  To configure Web user activities to report to Syslog server: Open the Syslog Settings page (Configuration tab >...

  • Page 875: Configuring Address Of Syslog Server

    Click Submit. 54.2.6 Viewing Syslog Messages You can receive and view Syslog messages generated by the device using any of the following Syslog server types:  Wireshark - third-party network protocol analyzer (http://www.wireshark.org). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 876 • You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting. User's Manual...

  • Page 877: Viewing Web User Activity Logs

    Username of the user that performed the activity. Interface Protocol used for the connection to the management interface (e.g., Telnet, SSH, Web, or HTTP). Client IP address of the client PC from where the user accessed the Web interface. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 878: Configuring Debug Recording

    Mediant 800B Gateway and E- SBC 54.3 Configuring Debug Recording This section describes how to configure and activate debug recording, and how to collect debug recording packets. For filtering debug recording packets for specific calls, see ''Configuring Log Filter Rules'' on page 865.

  • Page 879: Collecting Debug Recording Messages

    In the Filter field, type "acdr" (see the figure below) to view the debug recording messages. Note that the source IP address of the messages is always the OAMP IP address of the device. The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: Version 7.0...

  • Page 880: Debug Capturing On Physical Voip Interfaces

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

  • Page 881: Self-Testing

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

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

    The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. You can then provide the files to AudioCodes support team for troubleshooting. ...
  • Page 884 Mediant 800B Gateway and E- SBC  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button. User's Manual Document #: LTRT-10296...

  • Page 885: Analog Line Testing

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

  • Page 886: Fxs Line Testing

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

  • Page 887: Testing Sip Signaling Calls

    You can also configure it through ini file (Test_Call) or CLI (configure system > test-call > test-call-table).  To configure a test call: Open the Test Call table (Configuration tab > System menu > Test Call > Test Call Table). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 888 Mediant 800B Gateway and E- SBC Click Add; the following dialog box appears: Figure 58-1: Test Call Table - Add Row Dialog Box Configure a test call according to the parameters described in the table below. Click Add, and then save ("burn") your settings to flash memory.
  • Page 889 QoE Profile Assigns a QoE Profile to the test call. qoe-profile By default, no value is defined (None). [Test_Call_QOEProfile] To configure QoE Profiles, see ''Configuring Quality of Experience Profiles'' on page 313. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 890 Mediant 800B Gateway and E- SBC Parameter Description Bandwidth Profile Assigns a Bandwidth Profile to the test call. bandwidth-profile By default, no value is defined (None). [Test_Call_BWProfile] To configure Bandwidth Profiles, see ''Configuring Bandwidth Profiles'' on page 317. Authentication Tab Note: These parameters are applicable only if the Call Party parameter is set to Caller.

  • Page 891: Starting And Stopping Test Calls

    The status of the test call is displayed in the 'Test Status' field of the Test Call table:  "Idle": test call is not active.  "Scheduled": test call is planned to run (according to 'Schedule Interval' parameter settings) Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 892: Viewing Test Call Statistics

    Mediant 800B Gateway and E- SBC  "Running": test call has been started (i.e., the Dial command was clicked)  "Receiving": test call has been automatically activated by calls received for the test call endpoint from the remote endpoint (when all these calls end, the status returns to "Idle")
  • Page 893 QoE Profile.  Bandwidth Status: Tx/Rx bandwidth and color-threshold status according to the assigned Bandwidth Profile. Note: On the receiving side, when the first call is accepted in "Idle" state, statistics are reset. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 894: Configuring Dtmf Tones For Test Calls

    Mediant 800B Gateway and E- SBC 58.4 Configuring DTMF Tones for Test Calls By default, no DTMF signal is played to an answered test call (incoming or outgoing). However, you can enable this per configured test call in the Test Call table (see ''Configuring Test Call Endpoints'' on page 887).

  • Page 895: Configuring Sbc Test Call With External Proxy

    Only when the device receives the call from the proxy/registrar, does it route the call to the simulated endpoint. The figure below displays an example of an SBC test call: Figure 58-6: SBC Test Call Example Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 896 Mediant 800B Gateway and E- SBC The call is received from the remote endpoint with the called number prefix "8101". As the 'SBC Test ID' parameter is set to "8", the device identifies this call as a test call and removes the digit "8" from the called number prefix, leaving it as "101".

  • Page 897: Test Call Configuration Examples

    Call Party: Caller • Tel-to-IP Routing table configuration: ♦ Destination Phone Prefix: 201 (i.e., the Called URI user-part) ♦ Source Phone Prefix: 101 (i.e., the Endpoint URI user-part) ♦ Destination IP Address: 10.30.40.1 Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 898 The test call is done between two AudioCodes devices - Device A and Device B - with simulated test endpoints. This eliminates the need for phone users, who would otherwise need to answer and end calls many times for batch testing.
  • Page 899 ♦ Destination Address: "10.13.4.12" (this is the IP address of the device itself) ♦ SIP Interface: SIPInterface_0 ♦ Auto Register: Enable ♦ User Name: "testuser" ♦ Password: "12345" ♦ Call Party: Caller Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 900 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 901: Pinging A Remote Host Or Ip Address

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

  • Page 903: Appendix

    Part XII Appendix...

  • Page 905: Dialing Plan Notation For Routing And Manipulation

    To depict prefix and suffix numbers together:  03(100): for any number that starts with 03 and ends with 100.  [100-199](100,101,105): for a number that starts with 100 to 199 and Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 906 Mediant 800B Gateway and E- SBC Notation Description ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc.  03(5xx): for any number that starts with 03 and ends with 5xx.
  • Page 907 For example, if you wish to enter the phone number 555-1212, it must be entered as 5551212 without the hyphen (-). If the hyphen is entered, the entry is invalid. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 908 Mediant 800B Gateway and E- SBC This page is intentionally left blank. User's Manual Document #: LTRT-10296...

  • Page 909: Configuration Parameters Reference

    [1] = Enable - Web access is through any network interface. Password Change Interval Defines the duration (in minutes) of the validity of Web login passwords. When this duration expires, the password of the Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 910 Mediant 800B Gateway and E- SBC Parameter Description [WebUserPassChangeInterval] Web user must be changed. The valid value is 0 to 100000, where 0 means that the password is always valid. The default is 1140. Note: The parameter is applicable only when using the Web...
  • Page 911 WEBPasswordControlViaSNMP = 1, and reset the device with a flash burn (set acSysActionSetResetControl to 1 and acSysActionSetReset to 1). 2) Change the username and password in the acSysWEBAccessEntry table. Use the following format: Username acSysWEBAccessUserName: Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 912: Telnet Parameters

    Mediant 800B Gateway and E- SBC Parameter Description old/pass/new Password acSysWEBAccessUserCode: username/old/new [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface. The format of the ini file table parameter is:...

  • Page 913: Ini File Parameters

    Enables SNMP.  disable [0] No (default)  [1] Yes = SNMP is disabled and no traps are sent. [DisableSNMP] port Defines the device's local (LAN) UDP port used for SNMP Get/Set Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 914 The valid range is a string of up to 64 characters. auto-send-keep-alive Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is [SendKeepAliveTrap] used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
  • Page 915 Defines the SNMPv3 USM user or SNMPv2 user to associate with the trap destination. This determines the trap format, authentication level, trap-user and encryption level. By default, it is associated with the SNMPv2 user [SNMPManagerTrapUser_x] (SNMP trap community string). Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 916 Mediant 800B Gateway and E- SBC Parameter Description The valid value is a string. Trap Manager Host Name Defines an FQDN of the remote host used as an SNMP manager. The resolved IP address replaces the last entry in the Trap Manager table...

  • Page 917: Serial Parameters

    [8] = (Default) 8-bit Note: For the parameter to take effect, a device reset is required. [SerialParity] Defines the serial communication polarity.  [0] = (Default) None  [1] = Odd  [2] = Even Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 918: Auxiliary And Configuration File Name Parameters

    Mediant 800B Gateway and E- SBC Parameter Description Note: For the parameter to take effect, a device reset is required. [SerialStop] Defines the serial communication stop bit.  [1] = (Default) 1-bit (default)  [2] = 2-bit Note: For the parameter to take effect, a device reset is required.

  • Page 919: Automatic Update Parameters

    0 is Trunk 1. Dial Plan File Defines the name of the Dial Plan file. This file should be created using AudioCodes DConvert utility (refer to DConvert Utility User's [DialPlanFileName] Guide). For the ini file, the name must be enclosed by single apostrophes, for example, 'dial_plan.dat'.
  • Page 920 Mediant 800B Gateway and E- SBC Parameter Description predefined-time hour and mm the minutes. The value must be enclosed in single apostrophes. For example, '20:18'. [AutoUpdatePredefinedTime] Notes:  For the parameter to take effect, a device reset is required. ...
  • Page 921 Note: If you use the parameter in an ini file for periodic automatic provisioning with non-HTTP (e.g., TFTP) and without CRC, the device resets upon every file download. Software/Configuration File URL Path for Automatic Update Parameters Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 922 Mediant 800B Gateway and E- SBC Parameter Description automatic-update > Defines the name of the cmp file and the path to the server (IP firmware address or FQDN) from where the device can load the cmp file and update itself. The cmp file can be loaded using HTTP/HTTPS. For [CmpFileURL] example, http://192.168.0.1/filename.

  • Page 923: Networking Parameters

    Note: For the parameter to take effect, a device reset is required. Ethernet Device Table Ethernet Device Table Defines Ethernet Devices (VLANs). [DeviceTable] The format of the ini file table parameter is as follows: Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 924: Multiple Voip Network Interfaces And Vlan Parameters

    Mediant 800B Gateway and E- SBC Parameter Description [ DeviceTable ] FORMAT DeviceTable_Index = DeviceTable_VlanID, DeviceTable_UnderlyingInterface, DeviceTable_DeviceName, DeviceTable_Tagging; [ \DeviceTable ] For a detailed description of the table, see Configuring Underlying Ethernet Devices on page 132. 61.2.2 Multiple VoIP Network Interfaces and VLAN Parameters The IP network interfaces and VLAN parameters are described in the table below.

  • Page 925: Open Solution Network (Osn) Parameters

    DiffServ value in the IP header of the mapping packet. [DiffServToVlanPriority] The format of this ini file is as follows: [ DiffServToVlanPriority ] FORMAT DiffServToVlanPriority_Index = DiffServToVlanPriority_DiffServ, DiffServToVlanPriority_VlanPriority; Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 926: Nat And Stun Parameters

    Mediant 800B Gateway and E- SBC Parameter Description [ \DiffServToVlanPriority ] For example: DiffServToVlanPriority 0 = 46, 6; DiffServToVlanPriority 1 = 40, 6; DiffServToVlanPriority 2 = 26, 4; DiffServToVlanPriority 3 = 10, 2; For a description of the table, see Configuring Quality of Service on page 146.

  • Page 927: Dns Parameters

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

  • Page 928: Dhcp Parameters

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

  • Page 930: Ntp And Daylight Saving Time Parameters

    Mediant 800B Gateway and E- SBC Parameter Description DHCP Option table Defines additional DHCP Options that the device's DHCP server can use to service its DHCP clients. configure voip > dhcp option The format of the ini file table parameter is as follows:...
  • Page 931 Defines the DST offset (in minutes). offset The valid range is 0 to 120. The default is 60. [DayLightSavingTimeOffset] Note: The offset setting is applied only on the hour. For example, if Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 932: Debugging And Diagnostics Parameters

    Mediant 800B Gateway and E- SBC Parameter Description you configure the parameter at 15:42, the device applies the setting only at 16:00. 61.3 Debugging and Diagnostics Parameters This subsection describes the device's debugging and diagnostic parameters. 61.3.1 General Parameters The general debugging and diagnostic parameters are described in the table below.
  • Page 933 Enables the device to ignore LOS alarms received from the BRI user- side trunk and attempts to make a call (relevant for IP-to-Tel calls). ignore-bri-los-alarm  [0] Disable [IgnoreBRILOSAlarm]  [1] Enable (default) Note: The parameter is applicable only to BRI interfaces. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 934: Sip Test Call Parameters

    Mediant 800B Gateway and E- SBC 61.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below. Table 61-19: SIP Test Call Parameters Parameter Description Test Call DTMF String Defines the DTMF tone that is played for answered test calls (incoming and outgoing).

  • Page 935: Syslog, Cdr And Debug Parameters

    [2] Start & End Call = CDR report is sent to Syslog at the start and end of each call.  [3] Connect & End Call = CDR report is sent to Syslog at connection and at the end of each call. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 936 Mediant 800B Gateway and E- SBC Parameter Description  [4] Start & End & Connect Call = CDR report is sent to Syslog at the start, at connection, and at the end of each call. Notes:  For the SBC application, the parameter enables only signaling- related CDRs.
  • Page 937 - No Debug (0). When the CPU usage decreases to 5% less than the threshold (e.g., 65%), the debug level is increased to Basic (1). When the CPU usage decreases to 20% less than the threshold Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 938 Mediant 800B Gateway and E- SBC Parameter Description (e.g., 50%), the debug level changes to Detailed (5). Note: The device does not increase the debug level to a level that is higher than what you configured for the 'Debug Level' parameter.
  • Page 939 Defines the IP address of the server for capturing debug recording. configure system > logging > dbg-rec- dest-ip [DebugRecordingDestIP] Debug Recording Destination Defines the UDP port of the server for capturing debug recording. Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 940 Mediant 800B Gateway and E- SBC Parameter Description Port The default is 925. configure system > logging > dbg-rec- dest-port [DebugRecordingDestPort] Enable Core Dump Enables the automatic generation of a Core Dump file upon a device crash. [EnableCoreDump]  [0] Disable (disable) ...

  • Page 941: Resource Allocation Indication Parameters

    "Device 1" for the active device and "Device 2" for the redundant device. [HAUnitIdName] HA Remote Address Defines the Maintenance interface address of the redundant device in the HA system. configure system > high-availability > By default, no value is defined. remote-address Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 942 Mediant 800B Gateway and E- SBC Parameter Description [HARemoteAddress] HA Revertive Enables HA switchover based on HA priority.  configure system > [0] Disable (default) = A switchover over to the redundant device is high-availability > done only if a failure occurs in the currently active device.

  • Page 943: Security Parameters

    IP address and SSRC for RTCP/RTP and based on IP address only for T.38, the packet is accepted immediately. Note: If a packet from the original (first latched onto) IP address:port is received at any time, the device latches onto Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 944 Mediant 800B Gateway and E- SBC Parameter Description this stream.  [2] Dynamic-Strict = Device latches onto the first stream. If it receives at least a minimum number of consecutive packets (configured by New<media type>StreamPackets) all from the same source which is different to the first stream and the device has not received packets from the current stream for a user- defined period (TimeoutToRelatch<media type>Msec), it...

  • Page 945: Https Parameters

    Enables the requirement of client certificates for HTTPS HTTPS connection connection.  [0] Disable = (Default) Client certificates are not required. req-client-cert  [1] Enable = Client certificates are required. The client [HTTPSRequireClientCertificate] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 946: Srtp Parameters

    Mediant 800B Gateway and E- SBC Parameter Description certificate must be preloaded to the device and its matching private key must be installed on the managing PC. Time and date must be correctly set on the device for the client certificate to be verified.
  • Page 947 Enables authentication on transmitted RTP packets in a secured RTP Transmitted RTP Packets session.  [0] Enable (default) RTP-authentication- disable-tx  [1] Disable [RTPAuthenticationDisableTx] Disable Encryption On Enables encryption on transmitted RTP packets in a secured RTP Transmitted RTP Packets session. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 948: Tls Parameters

    Mediant 800B Gateway and E- SBC Parameter Description  RTP-encryption- [0] Enable (default) disable-tx  [1] Disable [RTPEncryptionDisableTx] Disable Encryption On Enables encryption on transmitted RTCP packets in a secured RTP Transmitted RTCP Packets session.  RTCP-encryption- [0] Enable (default) disable-tx ...
  • Page 949 Server certificate. The certificate is verified with the Root CA information. tls-vrfy-srvr-cert  [0] Disable (default) [VerifyServerCertificate]  [1] Enable Note: If Subject Name verification is necessary, the parameter PeerHostNameVerificationMode must be used as well. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 950: Ssh Parameters

    Mediant 800B Gateway and E- SBC Parameter Description Strict Certificate Extension Enables the validation of the extensions (keyUsage and Validation extentedKeyUsage) of peer certificates. This validation ensures that the signing CA is authorized to sign certificates and that the require-strict-cert...

  • Page 951: Ids Parameters

    Threshold Window is set to 15 sec, the IDSAlarmClearPeriod parameter is ignored and the alarm is cleared only after 30 seconds (2 x 15 sec). The valid value is 0 to 86400. The default is 300. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 952: Ocsp Parameters

    Mediant 800B Gateway and E- SBC Parameter Description IDS Policy Table IDS Policy Table Defines IDS Policies. [IDSPolicy] The format of the ini file parameter is: [ IDSPolicy ] FORMAT IDSPolicy_Index = IDSPolicy_Name, IDSPolicy_Description; [ \IDSPolicy ] For a detailed description of the table, see ''Configuring IDS Policies'' on page 169.

  • Page 953: Quality Of Experience Parameters

    Enables a TLS connection with the SEM server.  configure voip > qoe [0] Disable (default) configuration > tls-  [1] Enable enable Note: For the parameter to take effect, a device reset is required. [QOEEnableTLS] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 954 Mediant 800B Gateway and E- SBC Parameter Description QOE TLS Context Name Selects a TLS Context (configured in the TLS Contexts table) for the TLS connection with the SEM server. configure voip/qoe configuration/tls- The valid value is a string representing the name of the TLS context-name Context as configured in the 'Name' field of the TLS Contexts table.
  • Page 955 The format of the ini file table parameter is as follows: media-enhancement-rules [MediaEnhancementRules] [MediaEnhancementRules] FORMAT MediaEnhancementRules_Index = MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of the table, see ''Configuring Media Enhancement Profiles'' on page 320. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 956: Control Network Parameters

    Mediant 800B Gateway and E- SBC 61.6 Control Network Parameters 61.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 61-31: Proxy, Registration and Authentication SIP Parameters...
  • Page 957 If the parameter is disabled and the device registers to an IP Group (i.e., proxy server), it uses the string configured by the ProxyName parameter as the host name in the REGISTER's Request-URI and uses the string configured by the IP Group Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 958 Mediant 800B Gateway and E- SBC Parameter Description table parameter, SIPGroupName as the host name in the To and From headers. If the IP Group is configured with a Proxy Set that has multiple IP addresses, all the REGISTER messages sent to these proxies are sent with the same host name.
  • Page 959 ProxyDNSQueryType, or use the proxy Set table. Proxy DNS Query Type Global parameter that defines the DNS query record type for resolving the Proxy server's configured domain name (FQDN) proxy-dns-query Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 960 Mediant 800B Gateway and E- SBC Parameter Description [ProxyDNSQueryType] into an IP address.  [0] A-Record (default) = A-record DNS query.  [1] SRV = If the Proxy IP address parameter contains a domain name without port definition (e.g., ProxyIP = domain.com), an SRV query is performed.
  • Page 961 362. Proxy Sets Table Proxy Set Table Defines the Proxy Sets. configure voip > voip- The format of the ini file table parameter is as follows: network proxy-set [ ProxySet ] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 962 Mediant 800B Gateway and E- SBC Parameter Description [ProxySet] FORMAT ProxySet_Index = ProxySet_ProxyName, ProxySet_EnableProxyKeepAlive, ProxySet_ProxyKeepAliveTime, ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap, ProxySet_SRDName, ProxySet_ClassificationInput, ProxySet_TLSContextName, ProxySet_ProxyRedundancyMode, ProxySet_DNSResolveMethod, ProxySet_KeepAliveFailureResp, ProxySet_GWIPv4SIPInterfaceName, ProxySet_SBCIPv4SIPInterfaceName, ProxySet_SASIPv4SIPInterfaceName, ProxySet_GWIPv6SIPInterfaceName, ProxySet_SBCIPv6SIPInterfaceName, ProxySet_SASIPv6SIPInterfaceName; [ \ProxySet ] For a description of the table, see ''Configuring Proxy Sets'' on page 362.
  • Page 963 The valid range is 0 to 2,000,000. The default is 0. Re-register On INVITE Failure Enables immediate re-registration if no response is received for an INVITE request sent by the device. reg-on-invite-fail Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 964 Mediant 800B Gateway and E- SBC Parameter Description  [RegisterOnInviteFailure] [0] Disable (default)  [1] Enable = The device immediately expires its re-registration timer and commences re-registration to the same Proxy upon any of the following scenarios:  The response to an INVITE request is 407 (Proxy Authentication Required) without an authentication header included.
  • Page 965 - set to the value of the private user identity  realm - set to the domain name of the home network  uri - set to the SIP URI of the domain name of the home network Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 966 Mediant 800B Gateway and E- SBC Parameter Description  nonce - set to an empty value  response - set to an empty value For example: Authorization: Digest username=alice_private@home1.net, realm=”home1.net”, nonce=””, response=”e56131d19580cd833064787ecc” Note: This registration header is according to the IMS 3GPP TS24.229 and PKT-SP-24.220 specifications.

  • Page 967: Network Application Parameters

    The format of the ini file table parameter is as follows: voip-network sip- [ SIPInterface ] interface FORMAT SIPInterface_Index = SIPInterface_InterfaceName, [SIPInterface] SIPInterface_NetworkInterface, SIPInterface_ApplicationType, SIPInterface_UDPPort, SIPInterface_TCPPort, SIPInterface_TLSPort, SIPInterface_SRDName, SIPInterface_MessagePolicyName, SIPInterface_TLSContext, SIPInterface_TLSMutualAuthentication, SIPInterface_TCPKeepaliveEnable, SIPInterface_ClassificationFailureResponseType, SIPInterface_PreClassificationManSet, SIPInterface_EncapsulatingProtocol, SIPInterface_MediaRealm, SIPInterface_SBCDirectMedia, SIPInterface_BlockUnRegUsers, Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 968 Mediant 800B Gateway and E- SBC Parameter Description SIPInterface_MaxNumOfRegUsers, SIPInterface_EnableUnAuthenticatedRegistrations, SIPInterface_UsedByRoutingServer; [ \SIPInterface ] For a detailed description of the table, see ''Configuring SIP Interfaces'' on page 342. [TCPKeepAliveTime] Defines the interval (in sec) between the last data packet sent and the first keep-alive probe to send.
  • Page 969 The format of the ini file table parameter is as follows: [ MediaRealmExtension ] FORMAT MediaRealmExtension_Index = MediaRealmExtension_MediaRealmIndex, MediaRealmExtension_ExtensionIndex, MediaRealmExtension_IPv4IF, MediaRealmExtension_IPv6IF, MediaRealmExtension_PortRangeStart, MediaRealmExtension_PortRangeEnd, MediaRealmExtension_MediaSessionLeg; [ \MediaRealmExtension ] For a detailed description of the table, see ''Configuring Media Realm Extensions'' on page 329. Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 970: General Sip Parameters

    (if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset  Note: The Event header value is proprietary to AudioCodes. Max SIP Message Length Defines the maximum size (in Kbytes) for each SIP message that can [KB] be sent over the network.
  • Page 971 PL=<receive packet loss>  JI=<jitter in ms>  LA=<latency in ms> Below is an example of the X-RTP-Stat header in a SIP BYE message: BYE sip:302@10.33.4.125 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.126;branch=z9hG4bKac2127550866 Max-Forwards: 70 From: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 972 Mediant 800B Gateway and E- SBC Parameter Description <sip:401@10.33.4.126;user=phone>;tag=1c2113553324 To: <sip:302@company.com>;tag=1c991751121 Call-ID: 991750671245200001912@10.33.4.125 CSeq: 1 BYE X-RTP-Stat: PS=207;OS=49680;;PR=314;OR=50240;PL=0;JI=600;LA=40 Supported: em,timer,replaces,path,resource- priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRAC K,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.6.80A.227.005 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0 PRACK Mode Determines the PRACK (Provisional Acknowledgment) mechanism mode for SIP 1xx reliable responses.
  • Page 973 [MinSE] The valid range is 10 to 100,000. The default is 90. Session Expires Disconnect Defines a session expiry timeout. The device disconnects the session Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 974 Mediant 800B Gateway and E- SBC Parameter Description Time (sends a SIP BYE) if the refresher did not send a refresh request before one-third (1/3) of the session expires time, or before the time session-exp- configured by the parameter (the minimum of the two).
  • Page 975 Note: The parameter is applicable only if G.711 VBD coder(s) with regular G.711 payload types 0 or 8 are configured for the device (using the CodersGroup parameter). Determines the device's fax transport behavior when G.711 VBD coder fax-vbd-behvr Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 976 Mediant 800B Gateway and E- SBC Parameter Description [FaxVBDBehavior] is negotiated at call start.  [0] = (Default) If the device is configured with a VBD coder (see the CodersGroup parameter) and is negotiated OK at call start, then both fax and modem signals are sent over RTP using the bypass payload type (and no mid-call VBD or T.38 Re-INVITEs occur).
  • Page 977 (non-INVITE transaction timeout timer), as defined in RFC 3261, when tcp-timeout the SIP transport type is TCP. [SIPTCPTimeout] The valid range is 0 to 40 sec. The default is 64 * SipT1Rtx parameter Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 978 Mediant 800B Gateway and E- SBC Parameter Description value. For example, if SipT1Rtx is set to 500 msec, then the default of SIPTCPTimeout is 32 sec. SIP Destination Port Defines the SIP destination port for sending initial SIP requests. The valid range is 1 to 65534. The default port is 5060.
  • Page 979 (received in INVITE) to ISDN Setup with the Off Hook Indicator IE of “Voice”, and “Speech” Bearer Capability IE. Note that the Off Hook Indicator IE is described in UCR 2008 specifications. - The device interworks the SIP tgrp=hotline-ccdata parameter Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 980 Mediant 800B Gateway and E- SBC Parameter Description (received in INVITE) to ISDN Setup with an Off Hook Indicator IE of “Data”, and with “Unrestricted 64k” Bearer Capability IE. The following is an example of the INVITE with tgrp=hotline- ccdata: INVITE sip:1234567;tgrp=hotline-ccdata;trunk-...
  • Page 981 GRUU is desired. This Contact parameter contains a globally unique ID that identifies the UA instance. The global unique ID is created from one of the following: Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 982 When configured, the string <UserAgentDisplayInfo user-agent-info value>/software version' is used, for example: [UserAgentDisplayInfo] User-Agent: myproduct/v.6.80A.227.005 If not configured, the default string, <AudioCodes product- name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 800B Gateway and E-SBC/v.6.80A.227.005 The maximum string length is 50 characters.
  • Page 983 [1] PacketCable = Includes the 'mptime' attribute in the outgoing [MultiPtimeFormat] SDP - PacketCable-defined format. The mptime' attribute enables the device to define a separate packetization period for each negotiated coder in the SDP. The Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 984 Mediant 800B Gateway and E- SBC Parameter Description 'mptime' attribute is only included if the parameter is enabled even if the remote side includes it in the SDP offer. Upon receipt, each coder receives its 'ptime' value in the following precedence: from 'mptime' attribute, from 'ptime' attribute, and then from default value.
  • Page 985 [0] = (Default) Sets the IP address of the outgoing SDP's c= field to 0.0.0.0.  [1] = Sets the IP address of the outgoing SDP c= field to the IP address of the device. If the incoming SDP doesn’t contain the Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 986 Mediant 800B Gateway and E- SBC Parameter Description "a=inactive" line, the returned SDP contains the "a=recvonly" line. Enable Delayed Offer Determines whether the device sends the initial INVITE message with or without an SDP. Sending the first INVITE without SDP is typically...
  • Page 987 Global parameter that defines the progress indicator (PI) sent to the IP. You can also configure this functionality per specific calls, using IP prog-ind-2ip Profiles (IpProfile_ProgressIndicator2IP) or Tel Profiles. For a detailed [ProgressIndicator2IP] Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 988 Mediant 800B Gateway and E- SBC Parameter Description description of the parameter and for configuring this functionality in the IP Profile table, see Configuring IP Profiles on page 396 or in the Tel Profile table, see Configuring Tel Profiles on page 392.
  • Page 989 [1] = (Default) 100 Trying response is sent immediately upon receipt of INVITE request. [TransparentCoderPresentat Determines the format of the Transparent coder representation in the ion] SDP.  [0] = clearmode (default)  [1] = X-CCD Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 990 Mediant 800B Gateway and E- SBC Parameter Description [IgnoreRemoteSDPMKI] Determines whether the device ignores the Master Key Identifier (MKI) if present in the SDP received from the remote side.  [0] Disable (default)  [1] Enable Comfort Noise Generation Enables negotiation and usage of Comfort Noise (CN) for Gateway Negotiation calls.
  • Page 991 The parameter is applicable only to FXS interfaces. PSTN Alert Timeout Digital: Defines the Alert Timeout (in seconds) for calls sent to the PSTN. This timer is used between the time a Setup message is sent to Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 992 Mediant 800B Gateway and E- SBC Parameter Description pstn-alert-timeout the Tel side (IP-to-Tel call establishment) and a Connect message is received. If an Alerting message is received, the timer is restarted. If [PSTNAlertTimeout] the timer expires before the call is answered, the device disconnects the call and sends a SIP 408 request timeout response to the SIP party that initiated the call.
  • Page 993 The Manipulation Set is defined using the MessageManipulations parameter. By default, no manipulation is done (i.e. Manipulation Set ID is set to -1). Notes:  The parameter is used only if the Outbound Message Manipulation Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 994 Mediant 800B Gateway and E- SBC Parameter Description Set parameter of the destination IP Group is not set.  The parameter is applicable only to the Gateway application. WebSocket Keep-Alive Defines how often (in seconds) the device sends ping messages (keep...
  • Page 995 - Fully configured trunk (all channels): The device rejects new incoming calls. If at least one busy channel exists during the graceful period, the device immediately takes all idle channels out-of-service, but sends out-of-service Service messages to Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 996 Mediant 800B Gateway and E- SBC Parameter Description the B-channels only when all channels are idle. - Partially configured trunk (only some channels configured): The device rejects new incoming calls and places all channels out-of-service only after the graceful period expires, by sending out-of-service Service messages to the B-channels.
  • Page 997 The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Digital Out-Of-Service Defines the method for setting all digital trunks to out-of-service state. Behavior To configure the out-of-service method per trunk, see the Version 7.0 Mediant 800B Gateway and E- SBC...
  • Page 998 Mediant 800B Gateway and E- SBC Parameter Description dig-oos-behavior DigitalOOSBehaviorForTrunk_x parameter.  [DigitalOOSBehavior] [0] Default = (Default) For a detailed description, see option [0] of the DigitalOOSBehaviorForTrunk_x parameter (per trunk setting).  [1] Service = Sends an ISDN Service message indicating out-of- service state (or in-service).
  • Page 999 Defines SIP message policy rules for blocking (blacklist) unwanted incoming SIP messages or allowing (whitelist) receipt of desired configure voip > sbc messages. message-policy The format of the ini file table parameter is as follows: [MessagePolicy] Version 7.0 Mediant 800B Gateway and E- SBC...

  • Page 1000: Coders And Profile Parameters

    Mediant 800B Gateway and E- SBC Parameter Description [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Name, MessagePolicy_MaxMessageLength, MessagePolicy_MaxHeaderLength, MessagePolicy_MaxBodyLength, MessagePolicy_MaxNumHeaders, MessagePolicy_MaxNumBodies, MessagePolicy_SendRejection, MessagePolicy_MethodList, MessagePolicy_MethodListType, MessagePolicy_BodyList, MessagePolicy_BodyListType; [/MessagePolicy] For a detailed description of the table, see Configuring SIP Message Policy Rules. 61.8 Coders and Profile Parameters The profile parameters are described in the table below.
  • Page 1001 IpProfile_SBCReliableHeldToneSource, IpProfile_GenerateSRTPKeys, IpProfile_SBCPlayHeldTone, IpProfile_SBCRemoteHoldFormat, IpProfile_SBCRemoteReplacesBehavior, IpProfile_SBCSDPPtimeAnswer, IpProfile_SBCPreferredPTime, IpProfile_SBCUseSilenceSupp, IpProfile_SBCRTPRedundancyBehavior, IpProfile_SBCPlayRBTToTransferee, IpProfile_SBCRTCPMode, IpProfile_SBCJitterCompensation, IpProfile_SBCRemoteRenegotiateOnFaxDetection, IpProfile_JitterBufMaxDelay, IpProfile_SBCUserBehindUdpNATRegistrationTime, IpProfile_SBCUserBehindTcpNATRegistrationTime, IpProfile_SBCSDPHandleRTCPAttribute, IpProfile_SBCRemoveCryptoLifetimeInSDP, IpProfile_SBCIceMode, IpProfile_SBCRTCPMux, IpProfile_SBCMediaSecurityMethod, IpProfile_SBCHandleXDetect, IpProfile_SBCRTCPFeedback, IpProfile_SBCRemoteRepresentationMode, IpProfile_SBCKeepVIAHeaders, IpProfile_SBCKeepRoutingHeaders, IpProfile_SBCKeepUserAgentHeader, IpProfile_SBCRemoteMultipleEarlyDialogs, IpProfile_SBCRemoteMultipleAnswersMode, IpProfile_SBCDirectMediaTag; [\IPProfile] Version 7.0 1001 Mediant 800B Gateway and E- SBC...

  • Page 1002: Channel Parameters

    Mediant 800B Gateway and E- SBC Parameter Description For a description of the table, see ''Configuring IP Profiles'' on page 396. Tel Profile Table Tel Profile Settings Defines the Tel Profile table. Each Tel Profile ID includes a set of parameters (which are typically configured separately using their configure voip >...
  • Page 1003 Enables the network Acoustic Echo Suppressor feature on SBC calls. This feature removes echoes and sends only acoustic-echo-suppressor- the near-end’s desired speech signal to the network (i.e., to enable the far-end party). Version 7.0 1003 Mediant 800B Gateway and E- SBC...
  • Page 1004 Mediant 800B Gateway and E- SBC Parameter Description  [AcousticEchoSuppressorSupport] [0] Disable (default)  [1] Enable Note: For the parameter to take effect, a device reset is required. Echo Canceller Type Defines the echo canceller type.  echo-canceller-type [0] Line echo canceller = (Default) Echo canceller for Tel side.

  • Page 1005: Coder Parameters

    Defines the required number of silence frames at the beginning of vbr-coder-hangover each silence period when using the VBR coder silence [VBRCoderHangover] suppression. The range is 0 to 255. The default is 1. Version 7.0 1005 Mediant 800B Gateway and E- SBC...

  • Page 1006: Dtmf Parameters

    Mediant 800B Gateway and E- SBC Parameter Description AMR Payload Format Defines the AMR payload format type.  [AmrOctetAlignedEnable] [0] Bandwidth Efficient  [1] Octet Aligned (default) Note: The AMR payload type can also be configured per Coder Group (see Configuring Coder Groups on page 390). The Coder Group configuration overrides the parameter.

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

    Analog Signal Transport Type Determines the analog signal transport type.  [AnalogSignalTransportType] [0] Ignore Analog Signals = (Default) Ignore. Version 7.0 1007 Mediant 800B Gateway and E- SBC...
  • Page 1008 Mediant 800B Gateway and E- SBC Parameter Description  [1] RFC 2833 Analog Signal Relay = Transfer hookflash using RFC 2833. Note: The parameter is applicable only to FXS and FXO interfaces. RTP Redundancy Depth Global parameter that enables the device to generate RFC 2198 redundant packets.
  • Page 1009 (no RTP/T.38 traffic) when No- Op packet transmission is enabled. The valid range is 20 to 65,000 msec. The default is 10,000. Note: To enable No-Op packet transmission, use the NoOpEnable parameter. Version 7.0 1009 Mediant 800B Gateway and E- SBC...
  • Page 1010 Mediant 800B Gateway and E- SBC Parameter Description no-operation-interval Defines the payload type of No-Op packets. [RTPNoOpPayloadType] The valid range is 96 to 127 (for the range of Dynamic RTP Payload Type for all types of non hard-coded RTP Payload types, refer to RFC 3551).
  • Page 1011 (i.e., after a SIP BYE). The RTCP sbc-rtcpxr-report-mode XR is sent in the SIP PUBLISH message. [SBCRtcpXrReportMode]  [0] Disable (default)  [1] End of Call Note: The parameter is applicable only to the SBC application. Version 7.0 1011 Mediant 800B Gateway and E- SBC...
  • Page 1012 Mediant 800B Gateway and E- SBC Parameter Description publication-ip-group-id Defines the IP Group to where the RTCP XR is sent. If the value is -1 (default) or 0, the RTCP XR is sent to the ESC [PublicationIPGroupID] server, as configured by the RTCPXREscIP parameter.

  • Page 1013: Gateway Application Parameters

    [3] Events Only = Transparent with Events. Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 396. Version 7.0 1013 Mediant 800B Gateway and E- SBC...
  • Page 1014 Mediant 800B Gateway and E- SBC Parameter Description V.23 Modem Transport Type Determines the V.23 modem transport type.  V23-modem-transport-type [0] Disable = Transparent.  [2] Enable Bypass (default) [V23ModemTransportType]  [3] Events Only = Transparent with Events. Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType).
  • Page 1015 T.38 standard. enhanced-redundancy-depth The valid range is 0 to 4. The default is 2. [FaxRelayEnhancedRedundancyDepth] Fax Relay Redundancy Depth Defines the number of times that each fax relay Version 7.0 1015 Mediant 800B Gateway and E- SBC...

Table of Contents