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

AudioCodes Mediant 800B User Manual

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

Advertisement

Quick Links

See also: User Manual , Quick Manual
Mediant™ 800B Gateway & E-SBC
Enterprise Session Border Controller
Analog & Digital VoIP Media Gateway
User's Manual
Version 6.6
April 2013
Document # LTRT-10274

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant 800B

Summary of Contents for AudioCodes Mediant 800B

  • Page 1 Mediant™ 800B Gateway & E-SBC Enterprise Session Border Controller Analog & Digital VoIP Media Gateway User's Manual Version 6.6 April 2013 Document # LTRT-10274...
  • Page 3 Displaying Login Information upon Login .............. 62 Configuring Web Security Settings ............... 63 Web Login Authentication using Smart Cards............63 Configuring Web and Telnet Access List .............. 64 Configuring RADIUS Settings ................66 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 4 Mediant 800B GW & E-SBC CLI-Based Management ..................67 Enabling CLI using Telnet ..................67 Enabling CLI using SSH and RSA Public Key ............67 Establishing a CLI Session ................... 69 CLI Commands ....................70 5.4.1 Status Commands ....................70 5.4.2 Ping Command ......................73...
  • Page 5 13.2.2.4 Fax/Modem Bypass Mode..............152 13.2.2.5 Fax / Modem NSE Mode ................153 13.2.2.6 Fax / Modem Transparent with Events Mode ........154 13.2.2.7 Fax / Modem Transparent Mode ............154 13.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......155 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 6 Mediant 800B GW & E-SBC 13.2.3 V.34 Fax Support ....................155 13.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........156 13.2.3.2 Relay Mode for T.30 and V.34 Faxes ............157 13.2.3.3 V.34 Fax Relay for SG3 Fax Machines ..........157 13.2.4 V.150.1 Modem Relay ...................159 13.2.5 Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay ....160...
  • Page 7 20.6.4 Performing Manual D-Channel Switchover in NFAS Group ........290 20.7 ISDN Overlap Dialing ..................290 20.7.1 Collecting ISDN Digits and Sending Complete Number in SIP ......290 20.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 ....291 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 8 Mediant 800B GW & E-SBC 20.8 Redirect Number and Calling Name (Display) ............ 292 21 Trunk Group ....................293 21.1 Configuring Trunk Group Table ................293 21.2 Configuring Hunt Group Settings ................ 295 22 Manipulation ....................301 22.1 Configuring General Settings ................301 22.2 Configuring Source/Destination Number Manipulation Rules ......
  • Page 9 25.11.4 Enhanced 9-1-1 Support for Lync Server 2010 .............371 25.11.4.1 About E9-1-1 Services ................371 25.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........372 25.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 25.11.4.4 Configuring AudioCodes ELIN Gateway ..........380 25.12 Multilevel Precedence and Preemption ............... 382 25.12.1 MLPP Preemption Events in SIP Reason Header ..........384...
  • Page 10 Mediant 800B GW & E-SBC 26.14.3 Call Termination on FXO Devices .................409 26.14.3.1 Calls Termination by PBX ..............409 26.14.3.2 Call Termination before Call Establishment ...........410 26.14.3.3 Ring Detection Timeout ................411 26.15 Remote PBX Extension between FXO and FXS Devices ........411 26.15.1 Dialing from Remote Extension (Phone at FXS) ...........412...
  • Page 11 31.2.1 SAS Routing in Normal State ................495 31.2.2 SAS Routing in Emergency State ................497 32 SAS Configuration ..................499 32.1 General SAS Configuration ................499 32.1.1 Enabling the SAS Application ................499 32.1.2 Configuring Common SAS Parameters ..............499 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 12 Mediant 800B GW & E-SBC 32.2 Configuring SAS Outbound Mode ............... 502 32.3 Configuring SAS Redundant Mode ..............502 32.4 Configuring Gateway Application with SAS ............503 32.4.1 Gateway with SAS Outbound Mode ..............503 32.4.2 Gateway with SAS Redundant Mode ..............505 32.5 Advanced SAS Configuration ................
  • Page 13 38.3.3 TFTP Configuration using DHCP Option 66 ............561 38.3.4 HTTP-based Automatic Updates ................562 38.3.5 Configuration using FTP or NFS ................562 38.3.6 Configuration using AudioCodes EMS ..............563 38.4 Loading Files Securely (Disabling TFTP) ............563 38.5 Remotely Triggering Auto Update using SIP NOTIFY ......... 564 39 Restoring Factory Defaults ................
  • Page 14 46 Syslog and Debug Recordings ..............611 46.1 Syslog Message Format ..................611 46.1.1 Event Representation in Syslog Messages ............612 46.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......614 46.1.3 SNMP Alarms in Syslog Messages ...............614 46.2 Configuring Syslog Settings ................615 46.3 Configuring Debug Recording ................
  • Page 15 51.11.5.9 Call Cut-Through Parameters ..............776 51.11.5.10 Automatic Dialing Parameters ............777 51.11.5.11 Direct Inward Dialing Parameters .............777 51.11.5.12 ISDN BRI Parameters ..............779 51.11.6 PSTN Parameters ....................780 51.11.6.1 General Parameters ................780 51.11.6.2 TDM Bus and Clock Timing Parameters ..........785 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 16 Mediant 800B GW & E-SBC 51.11.6.3 CAS Parameters ..................787 51.11.6.4 ISDN Parameters ...................790 51.11.7 ISDN and CAS Interworking Parameters ..............797 51.11.8 Answer and Disconnect Supervision Parameters ..........813 51.11.9 Tone Parameters ....................818 51.11.9.1 Telephony Tone Parameters ..............818 51.11.9.2 Tone Detection Parameters ..............825 51.11.9.3 Metering Tone Parameters..............826...

  • Page 17: Weee Eu Directive

    This document is subject to change without notice. Date Published: April-29-2013 Trademarks AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect, VoIPerfectHD, What’s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or...

  • Page 18: Related Documentation

    This device includes cryptographic software written by Eric Young (eay@cryptsoft.com). 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 19: Overview

    ‎ 1 . Overview User's Manual 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 20 Mediant 800B GW & E-SBC The device allows full management through its HTTP/S-based embedded Web server. This user-friendly Web interface allows remote configuration using any standard Web browser (such as Microsoft™ Internet Explorer™). User's Manual Document #: LTRT-10274...

  • Page 21: Getting Started With Initial Connectivity

    Part I Getting Started with Initial Connectivity...

  • Page 23: Assigning The Oamp Ip Address

    Ethernet cable. Figure ‎ 2 -1: Cabling Device to PC Change the IP address and subnet mask of your computer to correspond with the default IP address and subnet mask of the device. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 24 Mediant 800B GW & E-SBC Access the Web interface: On your computer, start a Web browser and in the URL address field, enter the default IP address of the device; the Web interface's Login screen appears: Figure ‎ 2 -2: Web Login Screen In the 'Username' and 'Password' fields, enter the default login user name ("Admin"...
  • Page 25 At the prompt, type the following command to set the IP address, and then press Enter: (network-if-0)# set ip <IP address> At the prompt, type the following command to set the prefix length, and then press Enter: (network-if-0)# set prefix-length <prefix length, e.g., 16> Version 6.6 Mediant 800B GW & E-SBC...
  • Page 26 Mediant 800B GW & E-SBC At the prompt, type the following command to set the Default Gateway, and then press Enter: (network-if-0)# set gateway <IP address> At the prompt, type the following command to exit the Multiple Interface table, and...

  • Page 27: Management Tools

    Part II Management Tools...

  • Page 29: Introduction

    Embedded HTTP/S-based Web server - see 'Web-based Management' on page  Command Line Interface (CLI) - see 'CLI-Based Management' on page  AudioCodes Element Management System - see EMS-Based Management on page  Simple Network Management Protocol (SNMP) browser software - see 'SNMP-Based Management' on page ...
  • Page 30 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 31: Web-Based Management

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

  • Page 32: Accessing The Web Interface

    Mediant 800B GW & E-SBC 4.1.2 Accessing the Web Interface The procedure below describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see 'Computer Requirements' on page 31). In the Web browser, specify the IP address of the device (e.g., http://10.1.10.10); the Web interface's Login window appears, as shown below: Figure ‎...

  • Page 33: Areas Of The Gui

    For more information, see 'Navigation Tree' on page 35. Work pane, displaying the configuration page of the selected menu in the Navigation tree. This is where configuration is done. For more information, see 'Working with Configuration Pages' on page 37. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 34: Toolbar Description

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

  • Page 35: Navigation Tree

    Figure ‎ 4 -4: Navigating in Hierarchical Menu Tree (Example) Note: The figure above is used only as an example. The displayed menus depend on supported features based on the Software License Key installed on your device. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 36: Displaying Navigation Tree In Basic And Full View

    Mediant 800B GW & E-SBC 4.1.5.1 Displaying Navigation Tree in Basic and Full View You can view an expanded or reduced display of the Navigation tree. This affects the number of displayed menus and submenus in the tree. The expanded (Full) view displays all the menus pertaining to the selected configuration tab;...

  • Page 37: Working With Configuration

    Certain pages may not be accessible or may be read-only, depending on the access level of your Web user account (see 'Configuring Web User Accounts' on page 56). If a page is read-only, "Read-Only Mode" is displayed at the bottom of the page. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 38: Viewing Parameters

    Mediant 800B GW & E-SBC 4.1.6.2 Viewing Parameters Some pages allow you to view a reduced or expanded display of parameters. The Web interface provides two methods for displaying page parameters:  Displaying "basic" and "advanced" parameters - see 'Displaying Basic and Advanced Parameters' on page ...

  • Page 39: Modifying And Saving Parameters

    Parameters displayed on the page with the lightning symbol take effect only after a device reset. For resetting the device, see 'Resetting the Device' on page 527. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 40: Working With Tables

    Mediant 800B GW & E-SBC Note: Parameters saved to the volatile memory (by clicking Submit), revert to their previous settings after a hardware or software reset, or if the device is powered down. Therefore, 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 530).
  • Page 41 Edit Edits the selected row. Delete Removes the selected row from the table. When you click this button, a confirmation box appears requesting you to confirm deletion. Click Delete to accept deletion. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 42 Mediant 800B GW & E-SBC Item # Button Show/Hide Toggles between displaying and hiding the full configuration of a selected row. This configuration is displayed below the table (see Item #6) and is useful for large tables that cannot display all its columns in the work pane.

  • Page 43: Searching For Configuration Parameters

    Work pane and the searched parameter is highlighted in the page for easy identification, as shown in the figure below: Figure ‎ 4 -15: Searched Result Screen Version 6.6 Mediant 800B GW & E-SBC...

  • Page 44: Working With Scenarios

    Mediant 800B GW & E-SBC Table ‎ 4 -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 4.1.8...
  • Page 45 Save & Finish button to save your Scenario. Selected parameter(s) that you want added to a Scenario Step. Next button to add the current Step to the Scenario and enables you to add additional Steps. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 46: Accessing A Scenario

    Mediant 800B GW & E-SBC Notes:  You can add up to 20 Steps per Scenario, where each Step can contain up to 25 parameters.  When in Scenario mode, the Navigation tree is in 'Full' display (i.e., all menus are displayed in the Navigation tree) and the configuration pages are in 'Advanced Parameter List' display (i.e., all parameters are shown...

  • Page 47: Editing A Scenario

    To remove parameters, clear the check boxes corresponding to the desired parameters. Click Next.  Edit Step Name: In the Navigation tree, select the required Step. In the 'Step Name' field, modify the Step name. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 48: Saving A Scenario To A Pc

    Mediant 800B GW & E-SBC On the page, click Next.  Edit Scenario Name: In the 'Scenario Name' field, edit the Scenario name. On the displayed page, click Next.  Remove a Step: In the Navigation tree, select the required Step; the corresponding page opens in the Work pane.

  • Page 49: Loading A Scenario To The Device

     Loading an empty dat file (see 'Loading a Scenario to the Device' on page 49).  Loading an ini file with the ScenarioFileName parameter set to no value (i.e., ScenarioFileName = ""). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 50: Quitting Scenario Mode

    Mediant 800B GW & E-SBC 4.1.8.7 Quitting Scenario Mode Follow the procedure below to quit the Scenario mode.  To quit the Scenario mode: On the Navigation bar, click any tab except the Scenarios tab, or click the Cancel Scenarios button located at the bottom of the Navigation tree; a message box appears, requesting you to confirm exiting Scenario mode, as shown below.

  • Page 51: Getting Help

    To collapse the description, click the minus sign. To close the Help topic, click the close button located on the top-right corner of the Help topic window or simply click the Help button. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 52: Logging Off The Web Interface

    Mediant 800B GW & E-SBC Note: 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.

  • Page 53: Viewing The Home

    "LOCKED": device is locked (i.e. no new calls are accepted)  "UNLOCKED": device is not locked  "SHUTTING DOWN": device is currently shutting down To perform these operations, see 'Basic Maintenance' on page 527. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 54 Mediant 800B GW & E-SBC Table ‎ 4 -10: Home Page Description Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green = No alarms  Red = Critical alarm ...

  • Page 55: Assigning A Port Name

    Click the required port icon; a shortcut menu appears, as shown below: Figure ‎ 4 -25: Choosing Port Settings From the shortcut menu, choose Update Port Info; a text box appears. Type a brief description for the port, and then click Apply Port Info. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 56: Configuring Web User Accounts

    Mediant 800B GW & E-SBC Configuring Web User Accounts You can create up to 10 Web user accounts for the device. Up to five Web users can simultaneously be logged in to the device's Web interface. Web user accounts prevent unauthorized access to the Web interface, enabling login access only to users with correct credentials (i.e., username and password).

  • Page 57: Basic User Accounts Configuration

    When you log in to the Web interface, the username and password string values are case-sensitive, according to your configuration.  Up to two users can be logged in to the Web interface at the same time, and they can be of the same user. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 58 Mediant 800B GW & E-SBC  To configure the two pre-configured Web user accounts: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). If you are logged in as Security Administrator, both Web user accounts are displayed (as shown below).

  • Page 59: Advanced User Accounts Configuration

    Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). Under the Web Users Table group, click the Create Table button.  Subsequent access: Configuration tab > System menu > Web User Accounts. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 60 Mediant 800B GW & E-SBC The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"): Figure ‎ 4 -27: Web Users Table Page Click the Add button; the following dialog box is displayed: Figure ‎...
  • Page 61 Monitor = (Default) Read-only user. This user can only view Web pages and access to security-related pages is denied.  Admin = Read/write privileges for all pages, except security-related pages including the Web Users table where this user has only read- Version 6.6 Mediant 800B GW & E-SBC...

  • Page 62: Displaying Login Information Upon Login

    Mediant 800B GW & E-SBC Parameter Description only privileges.  SecAdmin = Read/write privileges for all pages. This user is the Security Administrator.  Master-User = Read/write privileges for all pages. This user also functions as a security administrator. Notes: ...

  • Page 63: Configuring Web Security Settings

    - what the user has (i.e., the physical card) and what the user knows (i.e., the login password). This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 64: Configuring Web And Telnet Access List

    Mediant 800B GW & E-SBC  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader. Access the device using the following URL: https://<host name or IP address>; the device prompts for a username and password.
  • Page 65 PC is denied.  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 6.6 Mediant 800B GW & E-SBC...

  • Page 66: Configuring Radius Settings

    Mediant 800B GW & E-SBC Configuring RADIUS Settings The RADIUS Settings page is used for configuring the Remote Authentication Dial In User Service (RADIUS) accounting parameters. For a description of these parameters, see 'Configuration Parameters Reference' on page 643. ...

  • Page 67: Cli-Based Management

    TCP, providing methods for key exchange, authentication, encryption, and authorization. SSH requires appropriate client software for the management PC. Most Linux distributions have OpenSSH pre-installed; Windows-based PCs require an SSH client software such as Version 6.6 Mediant 800B GW & E-SBC...
  • Page 68 Mediant 800B GW & E-SBC PuTTY, which downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty/. By default, SSH uses the same username and password as the Telnet and Web server. SSH supports 1024/2048-bit RSA public keys, providing carrier-grade security. Follow the instructions below to configure the device with an administrator RSA key as a means of strong authentication.

  • Page 69: Establishing A Cli Session

    Establish a Telnet or SSH session with the device using its OAMP IP address. Log in to the session using the username and password assigned to the Admin user of the Web interface. At the Username prompt, type the username, and then press Enter: Username: Admin Version 6.6 Mediant 800B GW & E-SBC...

  • Page 70: Cli Commands

    Mediant 800B GW & E-SBC At the Password prompt, type the password, and then press Enter: Password: Admin At the prompt, type the following, and then press Enter: enable At the prompt, type the password again, and then press Enter:...
  • Page 71 Used=16 Free= 0 Total=16 DSP device 13: Active Used=16 Free= 0 Total=16 DSP device 14: Active Used=16 Free= 0 Total=16 DSP device 15: Active Used=16 Free= 0 Total=16 DSP device 16: Active Used=16 Free= 0 Total=16 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 72 Mediant 800B GW & E-SBC DSP device 17: Active Used=16 Free= 0 Total=16 DSP device 18: Inactive PSEC - DSP firmware: AC491IPSEC Version: 0660.03 CONFERENCE - DSP firmware: AC491256C Version: 0660.03 />sh dsp perf DSP Statistics (statistics for 968 seconds):...

  • Page 73: Ping Command

    <number> Sets the Destination Number for the test call. set src <number> Sets the Source Number for the test call. set cid <display string> Sets the Display Name for the test call. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 74: Management Commands

    Mediant 800B GW & E-SBC Sub-Command Arguments Description set DTMFs <DTMF pattern> Sets the pattern of DTMFs that is played to the PSTN side after the test call is connected. display Displays all the set parameters for the test call. These values can be manually set using the set commands or defaults.

  • Page 75: Configuration Commands

     3 = LOCAL_ALL_CHANNELS_LOOP (whole trunk only) PstnSendAlarm PS/PH/PSA <TrunkId> Sends an alarm signal at the Tx interface <AlarmSendCode> or on a specific Trunk ID. The valid value options for AlarmSendCode include the Version 6.6 Mediant 800B GW & E-SBC...

  • Page 76: Ldap Commands

    Mediant 800B GW & E-SBC Command Short Arguments Description Format following:  0 = NO_ALARMS (means stop sending AIS)  1 = AIS_ALARM  2 = STOP_RAI_ALARM  3 = SEND_RAI_ALARM DeleteCasFile PS/CAS/DC <TableIndex> Deletes all the device's CAS files when <TableIndex>...

  • Page 77: Snmp-Based Management

    To save the changes to flash memory, see 'Saving Configuration' on page 530. To delete a community string, select the Delete check box corresponding to the community string that you want to delete, and then click Submit. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 78: Configuring Snmp Trap Destinations

    Mediant 800B GW & E-SBC Table ‎ 6 -1: SNMP Community String Parameters Description Parameter Description  Read Only [SNMPReadOnlyCommunityString_x]: Up to five Community String read-only community strings (up to 19 characters each). The default string is 'public'.  Read / Write [SNMPReadWriteCommunityString_x]: Up to five read / write community strings (up to 19 characters each).

  • Page 79: Configuring Snmp Trusted Managers

    SNMP agent accepts and processes SNMP requests. Notes: The SNMP Trusted Managers table can also be configured using the table ini file parameter, SNMPTrustedMgr_x (see 'SNMP Parameters' on page 654). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 80: Configuring Snmp V3 Users

    Mediant 800B GW & E-SBC  To configure SNMP Trusted Managers: Open the SNMP Trusted Managers page (Configuration tab > System menu > Management submenu > SNMP submenu > SNMP Trusted Managers). Figure ‎ 6 -2: 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.
  • Page 81 Group The group with which the SNMP v3 user is associated. [SNMPUsers_Group]  [0] Read-Only (default)  [1] Read-Write  [2] Trap Note: All groups can be used to send traps. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 82 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 83: Ems-Based Management

    ‎ 7 . EMS-Based Management User's Manual EMS-Based Management AudioCodes Element Management System (EMS) is an advanced solution for standards- based management of E-SBCs within VoP networks, covering all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of AudioCodes' families of E-SBCs.
  • Page 84 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 85: Ini File-Based Management

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

  • Page 87: General Ini File Formatting Rules

     All other methods: The default is assigned to the parameters that were not included in the loaded ini file and thereby, overriding values previously configured for these parameters. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 88: Modifying An Ini File

    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 89: General System Settings

    Part III General System Settings...

  • Page 91: Configuring Certificates

    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 ‎ 9 -1: Certificate Signing Request Group Version 6.6 Mediant 800B GW & E-SBC...

  • Page 92: Loading A Private Key

    Mediant 800B GW & E-SBC Copy the text and send it to your security provider. The security provider, also known as Certification Authority or CA, signs this request and then sends you a server certificate for the device. Save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE"...
  • Page 93 If the device was originally operating in HTTPS mode and you disabled it in Step 2, then enable it by setting the 'Secured Web Connection (HTTPS)' field to HTTPS Only. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 94: Mutual Tls Authentication

    Mediant 800B GW & E-SBC Mutual TLS Authentication By default, servers using TLS provide one-way authentication. The client is certain that the identity of the server is authentic. When an organizational PKI is used, two-way authentication may be desired - both client and server should be authenticated using X.509 certificates.

  • Page 95: Configuring Certificate Revocation Checking (Ocsp)

    The device does not query OCSP for its own certificate.  Some PKIs do not support OCSP but generate Certificate Revocation Lists (CRLs). For such cases, set up an OCSP server such as OCSPD. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 96: Tls Server Certificate Expiry Check

    Mediant 800B GW & E-SBC TLS Server Certificate Expiry Check The device can periodically check the validation date of the installed TLS server certificate. This periodic check interval is user-defined. In addition, within a user-defined number of days before the installed TLS server certificate expires, the device can be configured to send the SNMP trap, acCertificateExpiryNotifiaction to notify of the impending certificate expiration.

  • Page 97: Date And Time

    The client slowly robs bits from the clock counter to update the clock to the correct Version 6.6 Mediant 800B GW & E-SBC...
  • Page 98 Mediant 800B GW & E-SBC time. If the clock is running too slow, then in an effort to catch the clock up, bits are added to the counter, causing the clock to update quicker and catch up to the correct time. The advantage of this method is that it does not introduce any disparity in the system time that is noticeable to an end user or that could corrupt call timeouts and timestamps.

  • Page 99: General Voip Configuration

    Part IV General VoIP Configuration...

  • Page 101: Network

    Select the 'Index' radio button corresponding to the port that you want to configure. Click the Edit button. Configure the ports (see the table below for a description of the parameters). Click Apply. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 102 Mediant 800B GW & E-SBC Table ‎ 1 1-1: Physical Port Settings Parameters Description Parameter Description Port (Read-only) Displays the port number. The string values [PhysicalPortsTable_Port] displayed on the Web page represent the physical ports, as shown below: Mode (Read-only field) Displays the mode of the port: [PhysicalPortsTable_Mode] ...

  • Page 103: Configuring Tx/Rx For Ethernet Port-Pair Groups

    If a link exists on both ports, then the active one is either the first to have a link up or the lower-numbered port if both have the same link up from Version 6.6 Mediant 800B GW & E-SBC...

  • Page 104: Configuring Ip Network Interfaces

    Mediant 800B GW & E-SBC Parameter Description start.  [3] 2RX/1TX = Both ports in the group can receive packets, but only one port can transmit. The transmitting port is determined arbitrarily by the device. If the selected port fails at a later stage, a switchover to the redundant port is done, which begins to transmit as well as receive.
  • Page 105 Click the Apply button; the interface is added to the table and the Done button appears. Click Done to validate the interface. If the interface is not valid (e.g., if it overlaps with Version 6.6 Mediant 800B GW & E-SBC...
  • Page 106 Mediant 800B GW & E-SBC another interface in the table or if it does not adhere to the other rules as summarized in 'Multiple Interface Table Configuration Summary and Guidelines' on page 108), a warning message is displayed. Save the changes to flash memory and reset the device (see 'Saving Configuration' on page 530).
  • Page 107 This is useful for separating trusted networks from un- ace] trusted networks, by assigning each to different physical ports. To view the port groups and configure port settings, see Configuring Physical Ethernet Ports on page 101. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 108: Assigning Ntp Services To Application Types

    Mediant 800B GW & E-SBC 11.3.1 Assigning NTP Services to Application Types You can associate the Network Time Protocol (NTP) application with the OAMP or Control application type. This is done using the EnableNTPasOAM ini file parameter. 11.3.2 Multiple Interface Table Configuration Rules The Multiple Interface table configuration must adhere to the following rules: ...

  • Page 109: Troubleshooting The Multiple Interface Table

    Apart from these validation errors, connectivity problems may be caused by one of the following:  Trying to access the device with untagged traffic when VLANs are on and Native VLAN is not configured properly.  The IP Routing table is not configured properly. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 110: Networking Configuration Examples

    Mediant 800B GW & E-SBC 11.3.4 Networking Configuration Examples This section provides configuration examples of networking interfaces. 11.3.4.1 One VoIP Interface for All Applications This example describes the configuration of a single VoIP interface for all applications: Multiple Interface table: Configured with a single interface for OAMP, Media and Control: Table ‎...

  • Page 111: Voip Interfaces For Combined Application Types

    Layer-2 QoS values are assigned:  For packets sent with DiffServ value of 46, set VLAN priority to 6  For packets sent with DiffServ value of 40, set VLAN priority to 6 Version 6.6 Mediant 800B GW & E-SBC...

  • Page 112: Voip Interfaces With Multiple Default Gateways

    Mediant 800B GW & E-SBC  For packets sent with DiffServ value of 26, set VLAN priority to 4  For packets sent with DiffServ value of 10, set VLAN priority to 2  Layer-3 QoS values are assigned: ...

  • Page 113: Configuring The Ip Routing Table

    Delete Selected Entries. Notes:  You can delete only inactive routing rules.  The IP Routing table can also be configured using the table ini file parameter, StaticRouteTable. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 114 Mediant 800B GW & E-SBC Table ‎ 1 1-12: IP Routing Table Description Parameter Description Destination IP Address Defines the IP address of the destination host/network. The [StaticRouteTable_Destination] destination can be a single host or a whole subnet, depending on the Prefix Length configured for this routing rule.

  • Page 115: Interface Column

    The 'Gateway IP Address' field must be on the same subnet as the IP address of the associated interface specified in the 'Interface Name' field.  The 'Interface Name' selected for the routing rule must be of the same address family as the rule defined. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 116: Troubleshooting The Routing Table

    Mediant 800B GW & E-SBC  The 'Metric; field must be set to 1.  For the configuration settings to take effect, you must reset the device with a "burn" to flash memory. 11.4.3 Troubleshooting the Routing Table When adding a new static routing rule, the added rule passes a validation test. If errors are found, the routing rule is rejected and is not added to the IP Routing table.
  • Page 117  OAMP  Control Notes:  For the QoS settings to take effect, a device reset is required.  You can also configure the DiffServ table using the table ini file parameter DiffServToVlanPriority. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 118 Mediant 800B GW & E-SBC  To configure QoS: Open the Diff Serv Table page (Configuration tab > VoIP menu > Network submenu > QoS Settings). Figure ‎ 1 1-5: DiffServ Table Page Configure DiffServ to VLAN priority mapping (Layer-2 QoS): Enter an index entry, and then click Add.

  • Page 119: Disabling Icmp Redirect Messages

    IP network interface, configured in the Multiple Interface table (see 'Configuring IP Network Interfaces' on page 104).  You can also configure the DNS table using the table ini file parameter, DNS2IP (see 'DNS Parameters' on page 647). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 120 Mediant 800B GW & E-SBC  To configure the internal DNS table: Open the Internal DNS Table page (Configuration tab > VoIP menu > Network submenu > DNS submenu > Internal DNS Table). Click Add; the following dialog box appears: Figure ‎...

  • Page 121: Configuring The Internal Srv Table

    Figure ‎ 1 1-8: Internal SRV Table Page Configure the SRV rule, as required. For a description of the parameters, see the table below. Click Submit; the SRV rule is added to the table. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 122: Configuring Nfs Settings

    Mediant 800B GW & E-SBC Table ‎ 1 1-17: Internal SRV Table Parameter Description Parameter Description Domain Name Defines the host name to be translated. [Srv2Ip_InternalDomain] The valid value is a string of up to 31 characters. Transport Type Defines the transport type.
  • Page 123 Path to the root of the remote file system in the format: /[path]. For [NFSServers_RootPath] example, '/audio'. NFS Version NFS version used to access the remote file system. [NFSServers_NfsVersion]  [2] NFS Version 2  [3] NFS Version 3 (default) Version 6.6 Mediant 800B GW & E-SBC...

  • Page 124: Network Address Translation Support

    Mediant 800B GW & E-SBC Parameter Description Authentication Type Authentication method used for accessing the remote file system. [NFSServers_AuthType]  [0] Null  [1] Unix (default) User ID User ID used in authentication when using Unix. [NFSServers_UID] The valid range is 0 to 65537. The default is 0.

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

    In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation. Click Submit. Save the setting to the device's flash memory with a device reset (see 'Saving Configuration' on page 530). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 126: Configuring Nat Translation Per Ip Interface

    Mediant 800B GW & E-SBC 11.9.1.2 Configuring NAT Translation per IP Interface The NAT Translation table defines network address translation (NAT) rules for translating source IP addresses per VoIP interface (SIP control and RTP media traffic) into NAT IP addresses (global or public), when the device is located behind NAT. This allows, for example, the separation of VoIP traffic between different ITSP’s, and topology hiding of...

  • Page 127: Remote Ua Behind Nat

    RTP No-Op packets according to the avt-rtp-noop draft - see 'No-Op Packets' on page The figure below illustrates a typical network architecture where the remote UA is located behind NAT: Figure ‎ 1 1-13: Remote UA behind NAT Version 6.6 Mediant 800B GW & E-SBC...

  • Page 128: First Incoming Packet Mechanism

    Receipt of No-Op packets is always supported. 11.10 Robust Receipt of Media Streams The “robust-media” mechanism is an Audiocodes proprietary mechanism to filter out unwanted media (i.e., RTP, RTCP, and T.38) streams that are sent to the same port number on the device. In practice, the media RTP/RTCP ports may receive additional multiple unwanted media streams as result of traces of previous calls, call control errors, or deliberate attacks.

  • Page 129: Multiple Routers Support

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

  • Page 131: Security

    - Start Port - End Port: 0-65535 - Protocol: Any - Action Upon Match: Block  You can also configure the firewall settings using the table ini file parameter, AccessList (see 'Security Parameters' on page 665). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 132 Mediant 800B GW & E-SBC  To add firewall rules: Open the Firewall Settings page (Configuration tab > VoIP menu > Security submenu > Firewall Settings). Click the Add button; the following dialog box appears: Figure ‎ 1 2-1: Firewall Settings Page - Add Record Configure the firewall parameters, as required.
  • Page 133 Defines the destination UDP/TCP start port (on this device) to [AccessList_Start_Port] where packets are sent. The valid range is 0 to 65535. Note: When the protocol type isn't TCP or UDP, the entire range must be provided. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 134 Mediant 800B GW & E-SBC Parameter Description End Port Defines the destination UDP/TCP end port (on this device) to [AccessList_End_Port] where packets are sent. The valid range is 0 to 65535. Note: When the protocol type isn't TCP or UDP, the entire range must be provided.

  • Page 135: Configuring General Security Settings

    Open the General Security Settings page (Configuration tab > VoIP menu > Security submenu > General Security Settings). Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, refer to 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 136: Intrusion Detection System

    Mediant 800B GW & E-SBC 12.3 Intrusion Detection System The device can be configured to detect malicious attacks on its system and send SNMP traps if malicious activity is identified. The Intrusion Detection System (IDS) is an important feature for Enterprises to ensure legitimate calls are not being adversely affected by attacks and to prevent Theft of Service and unauthorized access.

  • Page 137: Configuring Ids Policies

    Figure ‎ 1 2-3: IDS Policy Table with Default Rules Add a Policy name: Click Add. Figure ‎ 1 2-4: IDS Policy Table - Add Record Configure the parameters as described in the following table, and then click Submit. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 138 Mediant 800B GW & E-SBC Table ‎ 1 2-3: IDS Policy Table Parameters Parameter Description Index Defines the table row number for the policy. CLI: policy [IDSPolicy_Index] Name Defines a name for the policy. CLI: rule The valid value is a string of up to 20 characters.
  • Page 139 The counter is [IDSRule_ThresholdWindo automatically reset at the end of the interval. The valid range is 1 to 1,000,000. The default is 1. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 140: Assigning Ids Policies

    Mediant 800B GW & E-SBC Parameter Description Minor-Alarm Threshold Defines the threshold that if crossed a minor severity alarm is sent. CLI: minor-alrm-thr The valid range is 1 to 1,000,000. A value of 0 or -1 means not [IDSRule_MinorAlarmThre defined.
  • Page 141 "!" appears before each subnet.  10.1.0.0/16 & !10.1.1.1: includes subnet 10.1.0.0/16, except IP address 10.1.1.1. Policy Selects the IDS policy, configured in 'Configuring IDS Policies' on CLI: policy page 137. [IDSMatch_Policy] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 142: Viewing Ids Alarms

    Mediant 800B GW & E-SBC 12.3.4 Viewing IDS Alarms The device uses SNMP (and Syslog) to notify the detection of malicious attacks. The trap displays the IDS Policy and Rule, and the Policy-Match index. The device sends the SNMP alarm, acIDSPolicyAlarm whenever a threshold of a specific IDS Policy rule is crossed.
  • Page 143 Remote rejects (prior to SIP 180 response) establish-remote-reject   Requests and responses without a matching flow-no-match-tu Abnormal Flow transaction user (except ACK requests)  flow-no-match-  Requests and responses without a matching transaction transaction (except ACK requests) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 144 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 145: Media

    When silence is detected, it stops sending packets in the channel. The procedure below describes how to enable silence suppression using the Web interface. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 146: Echo Cancellation

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

  • Page 147: Fax And Modem Capabilities

    IsFaxUsed parameter and V.152 parameters in Section 'V.152 Support' on page 160).  For a detailed description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 643. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 148: Fax/Modem Operating Modes

    Mediant 800B GW & E-SBC  To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Configuration tab > VoIP menu > Media submenu > Fax/Modem/CID Settings). Configure the parameters, as required. Click Submit to apply your changes.

  • Page 149: Fax/Modem Transport Modes

    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. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 150 Mediant 800B GW & E-SBC 13.2.2.1.1 Switching to T.38 Mode using SIP Re-INVITE In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal the terminating device negotiates T.38 capabilities using a Re-INVITE message. If the far- end device doesn't support T.38, the fax fails.

  • Page 151: G.711 Fax / Modem Transport Mode

     For G.711A-law: a=gpmd:0 vbd=yes;ecan=on  For G.711 µ-law: a=gpmd:8 vbd=yes;ecan=on In this mode, the 'Fax Transport Mode' (FaxTransportMode) parameter is ignored and automatically set to Disable (transparent mode). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 152: Fax/Modem Bypass Mode

    Mediant 800B GW & E-SBC  To configure fax fallback mode:  In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to Fax Fallback (IsFaxUsed = 3).

  • Page 153: Fax / Modem Nse Mode

    INVITE messages are sent. The voice channel is optimized for fax/modem transmission (same as for usual bypass mode). The parameters defining payload type for AudioCodes proprietary Bypass mode -- 'Fax Bypass Payload Type' (RTP/RTCP Settings page) and ModemBypassPayloadType (ini file) -- are not used with NSE Bypass.

  • Page 154: Fax / Modem Transparent With Events Mode

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

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

    Faxes' on page 157) To configure whether to pass V.34 over T38 fax relay, or use Bypass over the High Bit Rate coder (e.g. PCM A-Law), use the 'V.34 Fax Transport Type' parameter (V34FaxTransportType). Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC You can use the 'SIP T38 Version' parameter (SIPT38Version) in the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters) to configure one of the following:  Pass V.34 over T.38 fax relay using bit rates of up to 33,600 bps ('SIP T38 Version' is set to Version 3).

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

    Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 158 Mediant 800B GW & E-SBC Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0). Set the ini file parameter, V34FaxTransportType to 1 (i.e., relay). Set the ini file parameter, T38MaxDatagramSize to 560 (default).

  • Page 159: V.150.1 Modem Relay

    V.150.1 Software License Key.  The V.150.1 feature has been tested with certain IP phones. For more details, please contact your AudioCodes sales representative.  The V.150.1 SSE Tx payload type is according to the offered SDP of the remote side.

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

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

  • Page 161: Fax Transmission Behind Nat

    (jitter) by more than 10 msec from one packet to the next, there is always a sample in the buffer for the coder to use. If there is more than 10 Version 6.6 Mediant 800B GW & E-SBC...

  • Page 162: Comfort Noise Generation

    Mediant 800B GW & E-SBC msec of delay at any time during the call, the packet arrives too late. The coder tries to access a frame and is not able to find one. The coder must produce a voice sample even if a frame is not available.

  • Page 163: Dual-Tone Multi-Frequency Signaling

    Note: To set the RFC 2833 payload type with a value other than its default, use the RFC2833PayloadType parameter. The device negotiates the RFC 2833 payload type using local and remote SDP and sends packets using the payload type from the Version 6.6 Mediant 800B GW & E-SBC...

  • Page 164: Configuring Rfc 2833 Payload

    Mediant 800B GW & E-SBC received SDP. The device expects to receive RFC 2833 packets with the same payload type as configured by this parameter. If the remote side doesn’t include ‘telephony-event’ in its SDP, the device sends DTMF digits in transparent mode (as part of the voice stream).

  • Page 165: Configuring Rtp Base Udp Port

    T38UseRTPPort parameter to 1.  If you are using Media Realms (see 'Configuring Media Realms' on page 170), the port range configured for the Media Realm must be within this range defined by the BaseUDPPort parameter. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 166: Configuring Ip Media Settings

    Mediant 800B GW & E-SBC The procedure below describes how to configure the RTP base UDP port using the Web interface.  To configure the RTP base UDP port: Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media submenu >...

  • Page 167: Configuring Various Codec Attributes

    Figure ‎ 1 3-8: Coder Attribute Configuration in General Media Settings Page Configure the parameters as required, and then click Submit. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 168: Configuring Analog Settings

    Mediant 800B GW & E-SBC 13.6 Configuring Analog Settings The Analog Settings page allows you to configure various analog parameters. For a detailed description of the parameters appearing on this page, see 'Configuration Parameters Reference' on page 643. This page also selects the type (USA or Europe) of FXS and/or FXO coefficient information.
  • Page 169 When the M-lead goes idle, the device sends re-INVITE with 'a=inactive' in SDP (radio is in idle mode) The E&M interface wiring is shown in the figure below: Figure ‎ 1 3-10: E&M Type V 4-Wire Interface Version 6.6 Mediant 800B GW & E-SBC...

  • Page 170: Configuring Media Realms

    Once you have configured a Media Realm, you can configure it with the following:  Quality of Experience parameters for reporting to AudioCodes SEM server used for monitoring the quality of calls (see Configuring Quality of Experience Parameters per Media Realm on page 172) ...
  • Page 171 Interface Name field in the Multiple Interface table. Port Range Start Defines the starting port for the range of Media interface UDP [CpMediaRealm_PortRangeStart] ports. Notes:  You must either configure all media realms with port Version 6.6 Mediant 800B GW & E-SBC...

  • Page 172: Configuring Quality Of Experience Per Media Realm

    Mediant 800B GW & E-SBC Parameter Description ranges or all without; not some with and some without.  The available UDP port range is calculated using the BaseUDPport parameter:  BaseUDPport to BaseUDPport + 255*10  Port ranges over 60,000 must not be used.
  • Page 173 The QoE feature is available only if the device is installed with the relevant Software License Key.  To configure the address of the AudioCodes Session Experience Manager (SEM) server to where the device reports the QoE, see 'Configuring SEM Server for Media Quality of Experience' on page 177.
  • Page 174 Mediant 800B GW & E-SBC The figure above shows value thresholds for the MOS parameter, which are assigned using pre-configured values of the Low Sensitivity profile. In this example setting, if the MOS value changes by 0.1 (hysteresis) to 3.3 or 3.5, the device sends a report to the SEM indicating this change.

  • Page 175: Configuring Bandwidth Management Per Media Realm

    The transition possibilities include Normal-High threshold state changes and High-Critical threshold state changes. Thus, up to two thresholds can be configured per Media Realm; one for each state transition. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 176 Mediant 800B GW & E-SBC Notes:  This feature is available only if the device is installed with the relevant Software License Key.  For your bandwidth management settings to take effect, you must reset the device.  You can also use the BWManagement ini file parameter to configure bandwidth management per Media Realm.

  • Page 177: Configuring Server For Media Quality Of Experience

    13.9 Configuring Server for Media Quality of Experience The device can be configured to report voice (media) quality of experience 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 and processed by the SEM.

  • Page 178: Configuring Media Security

    Mediant 800B GW & E-SBC 13.10 Configuring Media Security The device supports Secured RTP (SRTP) according to RFC 3711. SRTP is used to encrypt RTP and RTCP transport for protecting VoIP traffic. SRTP requires a key exchange mechanism that is performed according to RFC 4568 – “Session Description Protocol (SDP) Security Descriptions for Media Streams”.
  • Page 179 Media Security). Figure ‎ 1 3-16: Media Security Page Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 180 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 181: Services

    The LDAP Settings page is used for configuring the LDAP server parameters. For a full description of these parameters, see 'Configuration Parameters Reference' on page 643. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 182: Configuring The Device's Ldap Cache

    Mediant 800B GW & E-SBC  To configure the LDAP server parameters: Open the LDAP Settings page (Configuration tab > VoIP menu > Services submenu > LDAP Settings). Figure ‎ 1 4-1: LDAP Settings Page The read-only 'LDAP Server Status' field displays one of the following possibilities: ...
  • Page 183 LDAP server again.  For a full description of the cache parameters, see 'Configuration Parameters Reference' on page 643. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 184: Active Directory Based Tel-To-Ip Routing For Microsoft Lync

    Mediant 800B GW & E-SBC  To configure the LDAP cache parameters: Open the LDAP Settings page (Configuration tab > VoIP menu > Services submenu > LDAP Settings). Figure ‎ 1 4-3: LDAP Settings Page - Cache Parameters Configure the parameters as required.
  • Page 185 If the query is found: The AD returns up to four attributes - Lync / OCS, PBX / IP PBX, private (only if it equals Primary or Secondary key), and mobile. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 186 Mediant 800B GW & E-SBC The device adds unique prefix keywords to the query results in order to identify the query type (i.e., IP domain). These prefixes are used as the prefix destination number value in the Outbound IP Routing table to denote the IP domains: ...
  • Page 187 Figure ‎ 1 4-4: LDAP Query Flowchart Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page for the LDAP query process. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 188: Configuring Ad-Based Routing Rules

    Mediant 800B GW & E-SBC 14.1.3.2 Configuring AD-Based Routing Rules The procedure below describes how to configure Tel-to-IP routing based on LDAP queries.  To configure LDAP-based Tel-to-IP routing for Lync Server 2010: Configure the LDAP server parameters, as described in 'Configuring the LDAP Server' on page 181.
  • Page 189 10.33.45.100) upon successful AD query result for the Mobile attribute.  Rule 5: Sends call to IP address of device (10.33.45.80) if AD query failure (e.g., no response from LDAP server or attribute not found). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 190: Querying The Ad For Calling Name

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

  • Page 191: Least Cost Routing

    Note that for one minute, Cost Groups "A" and "D" are identical, but due to the average call duration, Cost Group "D" is cheaper. Therefore, average call duration is an important factor in determining the cheapest routing role. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 192 Mediant 800B GW & E-SBC Below are a few examples of how you can implement LCR:  Example 1: This example uses two different Cost Groups for routing local calls and international calls: Two Cost Groups are configured as shown below:...

  • Page 193: Configuring Lcr

    Cost Groups in the Outbound IP Routing table. Note: The Routing Rule Groups table can also be configured using the table ini file parameter, RoutingRuleGroups. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 194 Mediant 800B GW & E-SBC  To enable LCR: Open the Routing Rule Groups Table page (Configuration tab > VoIP menu > Services submenu > Least Cost Routing > Routing Rule Groups Table). Click the Add button; the Add Record dialog box appears: Figure ‎...

  • Page 195: Configuring Cost Groups

    Figure ‎ 1 4-8: Cost Group Table - Add Record Configure the parameters as required. For a description of the parameters, see the table below. Click Submit; the entry is added to the Cost Group table. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 196: Configuring Time Bands For Cost Groups

    Mediant 800B GW & E-SBC Table ‎ 1 4-6: Cost Group Table Description Parameter Description Index Defines the table index entry. [CostGroupTable_Index] Cost Group Name Defines an arbitrary name for the Cost Group. [CostGroupTable_CostGroupName] The valid value is a string of up to 30 characters.
  • Page 197 Defines the call cost per minute charge during this [CostGroupTimebands_MinuteCost] timeband. The valid value range is 0-65533. The default is 0. Note: The entered value must be a whole number (i.e., not a decimal). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 198: Assigning Cost Groups To Routing Rules

    Mediant 800B GW & E-SBC 14.2.2.4 Assigning Cost Groups to Routing Rules Once you have configured your Cost Groups, you need to assign them to routing rules:  Gateway/IP-to-IP application: Outbound IP Routing table - see Configuring Outbound IP Routing Table on page ...

  • Page 199: Enabling Applications

    Figure ‎ 1 5-1: Applications Enabling Page From the relevant application drop-down list, select Enable. Save (burn) the changes to the device's flash memory with a device reset (see 'Saving Configuration' on page 530). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 200 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 201: Control Network

    SIP Interface table, instead of navigating to the SIP Interface Table page as described in 'Configuring SIP Interface Table' on page 203.  The SRD table can also be configured using the table ini file parameter, SRD. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 202 Mediant 800B GW & E-SBC  To configure SRDs: Open the SRD Settings page (Configuration tab > VoIP menu > Control Network submenu > SRD Table). Figure ‎ 1 6-1: SRD Settings Page From the 'SRD Index' drop-down list, select an index for the SRD, and then configure it according to the table below.

  • Page 203: Configuring Sip Interface Table

    Using SIP signaling interfaces per call leg (i.e., each SIP entity communicates with a specific SRD).  Using different SIP listening ports for a single or for multiple IP network interfaces.  Differentiating between applications by creating SIP Interfaces per application. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 204 Mediant 800B GW & E-SBC Separating signaling traffic between networks (e.g., different customers) to use different routing tables, manipulations, SIP definitions, and so on. Note: The SIP Interface table can also be configured using the table ini file parameter, SIPInterface.
  • Page 205  [0] Disable = Device does not request the client certificate for TLS connection.  [1] Enable = Device requires receipt and verification of the client certificate to establish the TLS connection. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 206: Configuring Ip Groups

    Mediant 800B GW & E-SBC Parameter Description TCP Keepalive Enable Enables the TCP Keep-Alive mechanism with the IP entity on this SIP interface. TCP keepalive can be used, for example, to keep a [SIPInterface_TCPKeepaliveE NAT entry open for clients located behind a NAT server or simply nable] to check that the connection to the IP entity is available.
  • Page 207 Figure ‎ 1 6-2: IP Group Table - Add Dialog Box Configure the IP Group parameters according to the table below. Click Submit. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 208 Mediant 800B GW & E-SBC Table ‎ 1 6-3: IP Group Parameters Parameter Description Common Parameters Type Defines the type of IP Group: [IPGroup_Type]  [0] Server = Used when the destination address, configured by the Proxy Set, of the IP Group (e.g., ITSP, Proxy, IP-PBX, or Application server) is known.
  • Page 209 If this parameter is not configured (default), these headers are populated with the device's dotted-decimal IP address of the network interface on which the message is sent. Note: To ensure proper device handling, this parameter should be a valid FQDN. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 210 Mediant 800B GW & E-SBC Parameter Description Assigns an SRD to the IP Group. [IPGroup_SRD] The default is 0. Notes:  For this parameter to take effect, a device reset is required.  To configure SRDs, see Configuring SRD Table on page 201.
  • Page 211 Upon receipt of the registration message, the device returns a SIP 200 OK to the client. Notes:  This parameter is applicable only to the IP-to-IP application. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 212 Mediant 800B GW & E-SBC Parameter Description  This parameter is applicable only to User-type IP Groups. Serving IP Group ID If configured, INVITE messages initiated from the IP Group are sent to [IPGroup_ServingIPGroup] this Serving IP Group (range 1 to 9). In other words, the INVITEs are sent to the address defined for the Proxy Set associated with this Serving IP Group.
  • Page 213 Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the inbound message. The Message [IPGroup_InboundManSet] Manipulation rules are configured using the MessageManipulations parameter (see Configuring SIP Message Manipulation on page 228). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 214 Mediant 800B GW & E-SBC Parameter Description Outbound Message Message Manipulation Set (rule) that you want to assign to this IP Manipulation Set Group for SIP message manipulation on the outbound message. The [IPGroup_OutboundManSet Message Manipulation rules are configured using the MessageManipulations parameter (see Configuring SIP Message Manipulation on page 228).

  • Page 215: Configuring Proxy Sets Table

    Open the Proxy Sets Table page (Configuration tab > VoIP menu > Control Network submenu > Proxy Sets Table). Figure ‎ 1 6-3: Proxy Sets Table Page From the 'Proxy Set ID' drop-down list, select an ID for the desired group. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 216 Mediant 800B GW & E-SBC Configure the Proxy parameters, as required. For a description of the parameters, see the table below. Click Submit. To save the changes to flash memory, see 'Saving Configuration' on page 530. Table ‎ 1 6-4: Proxy Sets Table Parameters...
  • Page 217 Note: This parameter is applicable only if the parameter EnableProxyKeepAlive is set to 1 (OPTIONS). When the parameter EnableProxyKeepAlive is set to 2 (REGISTER), the time interval between Keep-Alive messages is determined by the RegistrationTime Version 6.6 Mediant 800B GW & E-SBC...
  • Page 218 Mediant 800B GW & E-SBC Parameter Description parameter for the Gateway/IP-to-IP application or SBCProxyRegistrationTime parameter for the SBC application. Web: Proxy Load Balancing Enables the Proxy Load Balancing mechanism per Proxy Set ID. Method  [0] Disable = Load Balancing is disabled (default) EMS: Load Balancing ...
  • Page 219 [1] Compare IP, port and transport type = The call is classified to the Proxy Set according to its IP address, port, and transport type. Note: This parameter is applicable only if the IP Group table's parameter, 'Classify by Proxy Set' is set to Enable. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 220 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 221: Sip Definitions

    Parameters' on page 224). Notes:  For viewing Account registration status, see Viewing Endpoint Registration Status on page 587.  The Account table can also be configured using the table ini file parameter, Account. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 222 Mediant 800B GW & E-SBC  To configure Accounts: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions submenu > Account Table). Figure ‎ 1 7-1: Account Table Page In the 'Add' field, enter the desired table row index, and then click Add. A new row appears.
  • Page 223 Host Name and Contact User parameters.  If registration to an IP Group fails for all the accounts configured in this table for a specific Trunk Group and if this Trunk Group Version 6.6 Mediant 800B GW & E-SBC...

  • Page 224: Configuring Proxy And Registration Parameters

    Mediant 800B GW & E-SBC Parameter Description includes all the channels in the Trunk Group, the Trunk Group is set to Out-Of-Service if the parameter OOSOnRegistrationFail is set to 1 (see Proxy & Registration Parameters on page 224). Contact User Defines the AOR user name.
  • Page 225 Open the Proxy Sets Table page to configure groups of proxy addresses. Alternatively, you can open this page from the Proxy Sets Table page item (see 'Configuring Proxy Sets Table' on page for a description of this page). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 226: Sip Message Authentication Example

     The password from the ini file is "AudioCodes".  The equation to be evaluated is "122:audiocodes.com:AudioCodes". According to the RFC, this part is called A1.  The MD5 algorithm is run on this equation and stored for future usage.
  • Page 227 At this time, a new REGISTER request is issued with the following response: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c23940 To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 Server: Audiocodes-Sip-Gateway/Mediant 800B Gateway and SBC/v.6.60.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”,...

  • Page 228: Configuring Sip Message Manipulation

    Mediant 800B GW & E-SBC 17.4 Configuring SIP Message Manipulation The Message Manipulations page allows you to define up to 100 SIP message manipulation rules. Each manipulation rule can be assigned any Manipulation Set ID (0 to 19), enabling you to create groups (sets) of manipulation rules whereby rules of a group are configured with the same Manipulation Set ID number.
  • Page 229 ‎ 1 7. SIP Definitions User's Manual The figure below illustrates a SIP message manipulation example: Figure ‎ 1 7-3: SIP Header Manipulation Example Version 6.6 Mediant 800B GW & E-SBC...
  • Page 230 Mediant 800B GW & E-SBC Notes:  For a detailed description of the syntax for configuring SIP message manipulation rules, refer to SIP Message Manipulations Quick Reference Guide.  For the IP-to-IP application, the outgoing message is re-created and thus, SIP headers that are not relevant to the outgoing SIP session (e.g., Referred-By) are not included in the outgoing message.
  • Page 231 The valid value is a string. ion] For example:  header.from.url.user== '100' (indicates that the user part of the From header must have the value "100")  header.contact.param.expires > '3600'  header.to.url.host contains 'domain'  param.call.dst.user != '100' Version 6.6 Mediant 800B GW & E-SBC...
  • Page 232 Mediant 800B GW & E-SBC Parameter Description Operation Action Subject Defines the SIP header upon which the manipulation is [MessageManipulations_Action performed. Subject] Action Type Defines the type of manipulation. [MessageManipulations_Action  [0] Add (default) = adds new header/param/body (header or Type] parameter elements).

  • Page 233: Configuring Sip Message Policy Rules

    Figure ‎ 1 7-6: Message Policy Table - Add Record Dialog Box The policy defined above limits SIP messages to 32,768 characters, headers to 256 characters, bodies to 512 characters, number of headers to 16, and only permits two Version 6.6 Mediant 800B GW & E-SBC...
  • Page 234 Mediant 800B GW & E-SBC bodies. Invalid requests are rejected. Only INVITE and BYE requests are permitted and there are no restrictions on bodies. Configure the SIP message policy rule as required. See the table below for a description of each parameter.
  • Page 235 [0] Policy Blacklist =The specified SIP body (in the 'Body List' field) is rejected by the policy.  [1] Policy Whitelist = (Default) The specified SIP body (in the 'Body List' field) is allowed by the policy. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 236: Configuring Radius Accounting

    Mediant 800B GW & E-SBC 17.6 Configuring RADIUS Accounting The the RADIUS Parameters page allows you to enable RADIUS accounting of SIP calls by a RADIUS accounting server. The device can send the accounting messages to the RADIUS server upon call release, call connection and release, or call setup and release.

  • Page 237: Coders And Profiles

    For information on V.152 and implementation of T.38 and VBD coders, see 'Supporting V.152 Implementation' on page 160.  The Coders table can also be configured using the table ini file parameter, CodersGroup. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 238 Mediant 800B GW & E-SBC  To configure the device's coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles submenu > Coders). Figure ‎ 1 8-1: Coders Table Page From the 'Coder Name' drop-down list, select the required coder.
  • Page 239 [8] 23.85 (default) silk-nb 20 (default), 40, 60, 80, Dynamic [Silk-8Khz] and 100 (default is silk-wb 20 (default), 40, 60, 80, Dynamic [Silk-16Khz] and 100 (default is T.38 [t38fax] T.38 Version 3 [t38fax] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 240: Configuring Coder Groups

    Mediant 800B GW & E-SBC 18.2 Configuring Coder Groups The Coder Group Settings page allows you to define up to 10 groups of coders (termed Coder Groups). For each Coder Group, you can define up to 10 coders configured with packetization time (ptime), rate, payload type, and silence suppression.

  • Page 241: Configuring Tel Profile

    The procedure below describes how to configure Tel Profiles using the Web interface. Note: Tel Profiles can also be configured using the table ini file parameter, TelProfile (see 'Configuration Parameters Reference' on page 643) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 242 Mediant 800B GW & E-SBC  To configure Tel Profiles: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > Tel Profile Settings). Figure ‎ 1 8-3: Tel Profile Settings Page From the 'Profile ID' drop-down list, select the Tel Profile index.

  • Page 243: Configuring Ip Profiles

    To configure IP Profiles: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles submenu > IP Profile Settings). From the 'Profile ID' drop-down list, select the IP Profile index. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 244 Mediant 800B GW & E-SBC In the 'Profile Name' field, enter an arbitrary name that allows you to easily identify the IP Profile. From the 'Profile Preference' drop-down list, select the priority of the IP Profile, where '1' is the lowest priority and '20' is the highest. If both IP and Tel profiles apply to the same call, the coders and other common parameters (noted by an asterisk) of the preferred Profile are applied to that call.
  • Page 245 Reason for Alternative Routing table to initiate an alternative rule for Tel-to-IP calls using cause 805. Web: Progress Indicator to IP For a description, see the global parameter [IpProfile_ProgressIndicator2IP] ProgressIndicator2IP. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 246 Mediant 800B GW & E-SBC Parameter Description Web: Profile Preference Defines the priority of the IP Profile, where "1" is the lowest and [IpProfile_IpPreference] "20" the highest. If both IP and Tel Profiles apply to the same call, the coders and other common parameters of the preferred profile are applied to the call.
  • Page 247 Allowed Coders Group table. Note: If the SBCExtensionCodersGroupID parameter of the IP Profile table is set to None, this parameter is not applicable. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 248 Mediant 800B GW & E-SBC Parameter Description Determines the device’s handling of the SIP Diversion header. Web: Diversion Mode [IpProfile_SBCDiversionMode] For more information on interworking of the History-Info and Diversion headers, see Interworking SIP Diversion and History- Info Headers. ...
  • Page 249 (SBCFaxCodersGroupID, then the device uses this coder. If no match exists, the device uses the first listed coder of the matched coders between the incoming offer coders (from the calling "fax") and the coders of the selected Coders Group ID. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 250 Mediant 800B GW & E-SBC Parameter Description Web: SBC Session Expires Mode Determines the required session expires mode of the IP entity. [IpProfile_SBCSessionExpiresM  [0] Transparent = (Default) The device does not interfere ode] with the session expires negotiation. ...
  • Page 251 [1] Supported = (Default) Initial INVITE requests without SDP are supported. Note: For this parameter to function properly, a valid Extension Coders Group ID needs to be configured for IP Profiles that do not support delayed offer. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 252 Mediant 800B GW & E-SBC Parameter Description Web: SBC PRACK Mode Determines the PRACK mode required at the remote side: [IpProfile_SbcPrackMode]  [1] Optional = PRACK is optional for these UAs. If required, the device performs the PRACK process on behalf of the destination UA.
  • Page 253 (and assumes that the initiator of the call hold plays the held tone). Note: The device plays a held tone only if the 'SBC Play Held Tone' parameter is set to Yes. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 254 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 255: Gateway And Ip-To-Ip Application

    Part V Gateway and IP-to-IP Application...

  • Page 257: Ip-To-Ip Routing Overview

     VoIP between an enterprise's headquarters and remote branch offices  VoIP between an enterprise and the PSTN through an ITSP The IP-to-IP call routing capability is feature-rich, allowing interoperability with different ITSPs: Version 6.6 Mediant 800B GW & E-SBC...

  • Page 258: Theory Of Operation

    Mediant 800B GW & E-SBC  Easy and smooth integration with multiple ITSP SIP trunks.  Supports SIP registration and authentication with ITSP servers (on behalf of the enterprise's IP telephony system) even if the enterprise's IP telephony system does no support registration and authentication.

  • Page 259: Proxy Sets

    Generally, these are remote IP-PBX users (e.g., IP phones and soft phones). For registrations of User-type IP Groups, the device updates its internal database with the AOR and Contacts of the users (see the figure below) Digest authentication using SIP Version 6.6 Mediant 800B GW & E-SBC...
  • Page 260 Mediant 800B GW & E-SBC 401/407 responses, if needed, is done by the Serving IP Group (e.g., IP-PBX). The device forwards these responses directly to the remote SIP users. For a call to a registered remote user, the device searches its dynamic database using the Request URI for an entry that matches a registered AOR or Contact.

  • Page 261: Inbound And Outbound Ip Routing Rules

     The device has the public IP address 212.25.125.136 and is connected to the enterprise's firewall/NAT demilitarized zone (DMZ) network, providing the interface between the IP-PBX, and two ITSP's and the local PSTN. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 262 Mediant 800B GW & E-SBC  The enterprise has an IP-PBX located behind a Firewall/NAT:  IP-PBX IP address: 10.15.4.211  Transport protocol: UDP  Voice coder: G.711  IP-PBX users: 4-digit length extension number and served by two ITSPs.
  • Page 263  Configure outbound IP routing rules (see 'Step 9: Configure Outbound IP Routing' on page 272).  Configure destination phone number manipulation (see 'Step 10: Configure Destination Phone Number Manipulation' on page 273). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 264: Step 1: Enable The Ip-To-Ip Capabilities

    Mediant 800B GW & E-SBC 19.2.1 Step 1: Enable the IP-to-IP Capabilities This step describes how to enable the device's IP-to-IP application.  To enable IP-to-IP capabilities: Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling submenu > Applications Enabling).

  • Page 265: Step 4: Configure The Proxy Sets

    In the 'Enable Proxy Keep Alive' drop-down list, select Using Options, and then in the 'Proxy Load Balancing Method' drop-down list, select Round Robin. Figure ‎ 1 9-7: Proxy Set ID #1 for ITSP-A Version 6.6 Mediant 800B GW & E-SBC...
  • Page 266 Mediant 800B GW & E-SBC Configure Proxy Set ID #2 for ITSP-B: From the 'Proxy Set ID' drop-down list, select 2. In the 'Proxy Address' column, enter the IP addresses of the ITSP-B SIP trunk (e.g., "216.182.224.202" and "216.182.225.202"). From the 'Transport Type' drop-down list corresponding to the IP address entered above, select UDP.

  • Page 267: Step 5: Configure The Ip Groups

    In the 'SIP Group Name' field, enter the host name that is used internal in the device's database for this IP Group (e.g., RemoteIPPBXusers). From the 'Serving IP Group ID' drop-down list, select 3 (i.e. the IP Group for the IP-PBX). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 268: Step 6: Configure The Account Table

    Mediant 800B GW & E-SBC Note: No Serving IP Groups are defined for ITSP-A and ITSP-B. Instead, the Outbound IP Routing table (see 'Step 9: Configure Outbound IP Routing' on page 272) is used to configure outbound IP call routing for calls originating from these ITSP IP Groups.

  • Page 269: Step 7: Configure Ip Profiles For Voice Coders

    Profiles > IP Profile Settings). Configure Profile ID #1 for the IP-PBX (as shown below): From the 'Profile ID' drop-down list, select 1. From the 'Coder Group' drop-down list, select Coder Group 1. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 270: Step 8: Configure Inbound Ip Routing

    Mediant 800B GW & E-SBC Click Submit. Figure ‎ 1 9-13: Defining IP Profile ID 1 Configure Profile ID #2 for the ITSP's: From the 'Profile ID' drop-down list, select 2. From the 'Coder Group' drop-down list, select Coder Group 2.
  • Page 271 Trunk connected to the device and interfacing with the local PSTN.  'Source IP Group ID': enter "-1" to indicate that these calls are not assigned to any source IP Group. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 272: Step 9: Configure Outbound Ip Routing

    Mediant 800B GW & E-SBC 19.2.9 Step 9: Configure Outbound IP Routing This step defines how to configure the device for routing outbound (i.e., sent) IP-to-IP calls. In our example scenario, calls from both ITSP's must be routed to the IP-PBX, while outgoing calls from IP-PBX users must be routed according to destination.

  • Page 273: Step 10: Configure Destination Phone Number Manipulation

    'Destination Prefix': enter the prefix "0200".  'Source Prefix': enter the asterisk (*) symbol to indicate all sources.  'Number of Digits to Leave': enter "4" to leave only the last four digits. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 274 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 275: Digital Pstn

    For a description of the trunk parameters, see 'PSTN Parameters' on page 780. Notes:  During trunk deactivation, trunk configuration cannot be performed.  A stopped trunk cannot also be activated and a trunk cannot be deactivated if it has been stopped. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 276 Mediant 800B GW & E-SBC  To configure the trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN submenu > Trunk Settings). Figure ‎ 2 0-1: Trunk Settings Page On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: ...
  • Page 277 E1/T1 trunk to provide the device’s clock or enable ‘TDM Bus PSTN Auto Clock’ in the TDM Bus Settings page (see 'TDM and Timing' on page 278).  To delete a previously configured trunk, set the parameter 'Protocol Type' to 'None'. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 278: Tdm And Timing

    Mediant 800B GW & E-SBC 20.2 TDM and Timing This section describes the configuration of the TDM and clock timing parameters. 20.2.1 Configuring TDM Bus Settings The TDM page allows you to configure the device's Time-Division Multiplexing (TDM) bus settings. For a description of these parameters, see 'PSTN Parameters' on page 780.

  • Page 279: Configuring Internal Clock As Clock Source

    (no compilation is required). The change doesn't affect the state machine itself, but rather the configuration. The CAS table used can be chosen in two ways (using the parameter CasChannelIndex):  Single CAS table per trunk Version 6.6 Mediant 800B GW & E-SBC...
  • Page 280 Mediant 800B GW & E-SBC  Different CAS table per group of B-channels in a trunk  To modify the CAS state machine parameters: Open the CAS State Machine page (Configuration tab > VoIP menu > PSTN submenu > CAS State Machines).
  • Page 281 Defines which Signaling System to use in [CasStateMachineDigitSignalingSystem] both directions (detection\generation).  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 282: Configuring Digital Gateway Parameters

    Mediant 800B GW & E-SBC 20.4 Configuring Digital Gateway Parameters The Digital Gateway Parameters page allows you to configure miscellaneous digital parameters. For a description of these parameters, see 'Configuration Parameters Reference' on page 643.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...

  • Page 283: Tunneling Applications

    ‘Transparent’ coder to transport data (e.g., for D-channel). You can also use Profiles to assign ToS (for DiffServ) per source - a timeslot carrying data or signaling is assigned a higher priority value than a timeslot carrying voice. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 284 Mediant 800B GW & E-SBC For tunneling of E1/T1 CAS trunks, set the protocol type to 'Raw CAS' (ProtocolType = 3 / 9) and enable RFC 2833 CAS relay mode ('CAS Transport Type' parameter is set to 'CAS RFC2833 Relay').
  • Page 285 CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ Version 6.6 Mediant 800B GW & E-SBC...

  • Page 286: Dsp Pattern Detector

    Mediant 800B GW & E-SBC TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 20.5.1.1 DSP Pattern Detector For TDM tunneling applications, you can use the DSP pattern detector feature to initiate the echo canceller at call start. The device can be configured to support detection of a specific one-byte idle data pattern transmitted over digital E1/T1 timeslots.

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

    The parameter ‘DchConfig_x = Trunk_type’ defines the type of NFAS trunk. Trunk_type is set to 0 for the primary trunk, to 1 for the backup trunk, and to 2 for an ordinary NFAS Version 6.6 Mediant 800B GW & E-SBC...

  • Page 288: Nfas Interface Id

    Mediant 800B GW & E-SBC trunk. ‘x’ denotes the physical trunk ID (0 to the maximum number of trunks). You can also use the Web interface (see 'Configuring Trunk Settings' on page 275). For example, to assign the first four T1 trunks to NFAS group #1, in which trunk #0 is the...

  • Page 289: Creating An Nfas-Related Trunk Configuration

    All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode.  After stopping or deleting the backup trunk, delete the group and then reconfigure it. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC 20.6.4 Performing Manual D-Channel Switchover in NFAS Group If an NFAS group is configured with two D-channels (Primary and Backup), you can do a manual switchover between these D-channels.  To manually switchover from active to standby D-channel: Open the NFAS Group &...

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

    ISDNRxOverlap = 2  ISDNTxOverlap  ISDNOutCallsBehavior = 2  MinOverlapDigitsForRouting  TimeBetweenDigits  MaxDigits  DigitMapping  MuteDTMFInOverlap For configuring ISDN overlap dialing using the Web interface, see 'Configuring Trunk Settings' on page 275. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC 20.8 Redirect Number and Calling Name (Display) The following tables define the device's redirect number and calling name (Display) support for various ISDN variants according to NT (Network Termination) / TE (Termination Equipment) interface direction: Table ‎...

  • Page 293: Trunk Group

    To register the Trunk Groups, click the Register button. To unregister the Trunk Groups, click Unregister. The registration method for each Trunk Group is according to the 'Registration Mode' parameter in the Trunk Group Settings page (see 'Configuring Hunt Group Settings' on page 295). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 294 Mediant 800B GW & E-SBC Table ‎ 2 1-1: Trunk Group Table Parameters Parameter Description Module Defines the module (i.e., FXS, FXO, PRI, or BRI) for which you [TrunkGroup_Module] want to define the Trunk Group. From Trunk Defines the starting physical Trunk number in the Trunk Group.

  • Page 295: Configuring Hunt Group Settings

    Configure the Trunk Group as required. For a description of the parameters, see the table below. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 296 Mediant 800B GW & E-SBC Table ‎ 2 1-2: Hunt Group Settings Parameters Description Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. [TrunkGroupSettings_Trunk GroupId] Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the [TrunkGroupSettings_Chan channels of the Trunk Group.
  • Page 297 Account table (see 'Configuring Account Table' on page 221). An example is shown below of a REGISTER message for registering endpoint "101" using the registration Per Endpoint mode: REGISTER sip:SipGroupName SIP/2.0 Via: SIP/2.0/UDP 10.33.37.78;branch=z9hG4bKac862428454 From: <sip:101@GatewayName>;tag=1c862422082 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 298 Mediant 800B GW & E-SBC Parameter Description To: <sip:101@GatewayName> Call-ID: 9907977062512000232825@10.33.37.78 CSeq: 3 REGISTER Contact: <sip:101@10.33.37.78>;expires=3600 Expires: 3600 User-Agent: Sip-Gateway/v.6.60A.011.002 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Group table (see 'Configuring IP Groups' on page 206).
  • Page 299 SIP NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. Note: This parameter appears in the table only if the VoiceMailInterface parameter is set to 3 (QSIG). Configuring Voice Mail on page 389. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 300 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 301: Manipulation

    For example, if you enter 551 in Index 1 and 55 in Index 2, the device applies rule 1 to numbers that start with 551 and applies rule 2 to numbers that start with 550, 552, 553, Version 6.6 Mediant 800B GW & E-SBC...
  • Page 302 Mediant 800B GW & E-SBC and so on until 559. However, if you enter 55 in Index 1 and 551 in Index 2, the device applies rule 1 to all numbers that start with 55, including numbers that start with 551.
  • Page 303 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 Source IP Group Destination [6,7,8] Prefix Version 6.6 Mediant 800B GW & E-SBC...
  • Page 304 Mediant 800B GW & E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Suffix to Add Number of Digits to Leave...
  • Page 305 For example, if you enter 9 and the phone number [Prefix2Add] is 1234, the new number is 91234. Web: Suffix to Add Defines the number or string that you want added to the end of the Version 6.6 Mediant 800B GW & E-SBC...
  • Page 306 Mediant 800B GW & E-SBC Parameter Description EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone number [Suffix2Add] is 1234, the new number is 123400. Web/EMS: Number of Defines the number of digits that you want to keep from the right of the Digits to Leave phone number.

  • Page 307: Manipulating Number Prefix

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

  • Page 308: Sip Calling Name Manipulations

    Mediant 800B GW & E-SBC 22.4 SIP Calling Name Manipulations The Calling Name Manipulations Tel2IP and Calling Name Manipulations IP2Tel tables allow you to configure up to 120 manipulation rules for manipulating the calling name (i.e., caller ID) in SIP messages. This can include modifying or removing the calling name. SIP calling name manipulation is applicable to Tel-to-IP and IP-to-Tel calls.
  • Page 309 For example: 10.8.8.xx represents all IP addresses between 10.8.8.10 to 10.8.8.99.  The source IP address can include the asterisk (*) wildcard to represent any number between 0 and 255. For example, 10.8.8.* Version 6.6 Mediant 800B GW & E-SBC...

  • Page 310: Configuring Redirect Number Ip To Tel

    Mediant 800B GW & E-SBC Parameter Description represents all IP addresses between 10.8.8.0 and 10.8.8.255. Web: Source Host Prefix Defines the URI host name prefix of the incoming SIP INVITE message in the From header. Notes:  This parameter is applicable only to the Calling Name Manipulations IP2Tel table.
  • Page 311 Click the Action tab, and then configure the manipulation operation. For a description of the parameters, see the table below. Click Submit to apply your settings. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 312 Mediant 800B GW & E-SBC Table ‎ 2 2-4: Redirect Number Manipulation Parameters Description Parameter Description Matching Characteristics (Rule) Web/EMS: Redirect Prefix Defines the redirect telephone number prefix. To denote any number, [RedirectPrefix] use the wildcard asterisk (*) symbol. Web/EMS: Destination Defines the destination (called) telephone number prefix.
  • Page 313 Notes:  This parameter is applicable only to the Redirect Number IP > Tel table.  For more information on available NPI/TON values, see Numbering Plans and Type of Number on page 322. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC Parameter Description Web: NPI Defines the Numbering Plan Indicator (NPI). EMS: Number Plan  [0] Unknown (default) [NumberPlan]  [9] Private  [1] E.164 Public  [-1] Not Configured = value received from PSTN/IP is used Notes: ...

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

    Open the Phone Context Table page (Configuration tab > VoIP menu > GW and IP to IP submenu > Manipulations > Phone Context). Figure ‎ 2 2-5: Phone Context Table Page Configure the parameters as required. For a description of the parameters, see the Version 6.6 Mediant 800B GW & E-SBC...
  • Page 316 Mediant 800B GW & E-SBC table below. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Notes:  You can configure multiple rows with the same NPI/TON or same SIP 'phone-context'.

  • Page 317: Configuring Release Cause Mapping

    In the 'Release Cause Mapping from ISDN to SIP' group, map different Q.850 Release Causes to SIP Responses. In the 'Release Cause Mapping from SIP to ISDN' group, map different SIP Responses to Q.850 Release Causes. Click Submit to apply your changes. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC 22.8.1 Fixed Mapping of SIP Response to ISDN Release Reason The following table describes the mapping of SIP response to ISDN release reason. Table ‎ 2 2-7: Mapping of SIP Response to ISDN Release Reason...

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

    No circuit available Service unavailable Network out of order Service unavailable Temporary failure Service unavailable Switching equipment congestion Service unavailable Access information discarded 502* Bad gateway Requested channel not available 503* Service unavailable Version 6.6 Mediant 800B GW & E-SBC...
  • Page 320 Mediant 800B GW & E-SBC ISDN Release Description Description Reason Response Resource unavailable Service unavailable QoS unavailable 503* Service unavailable Facility not subscribed 503* Service unavailable Incoming calls barred within CUG Forbidden Bearer capability not authorized Forbidden Bearer capability not presently available...

  • Page 321: Reason Header

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

  • Page 322: Numbering Plans And Type Of Number

    Mediant 800B GW & E-SBC 22.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 below: Table ‎...

  • Page 323: Routing

    One or more characteristics can be defined for the rule:  Source IP Group (to which the call belongs)  Source and destination Request-URI host name prefix  Source Trunk Group (from where the call is received) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 324 Mediant 800B GW & E-SBC  Source (calling) and destination (called) telephone number prefix and suffix  Source and destination Request-URI host name prefix  Destination: If the call matches the configured characteristics, the device routes the call to an IP destination. If no characteristics match is found in the table, the call is rejected.
  • Page 325 IP address, or use an FQDN that resolves into two IP addresses. For more information on alternative routing, see 'Alternative Routing for Tel-to-IP Calls' on page 336. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 326 Mediant 800B GW & E-SBC Notes:  Outbound IP routing can be performed before or after number manipulation. This is configured using the RouteModeTel2IP parameter, as described below.  The Outbound IP Routing Table can also be configured using the table ini file parameter, Prefix.
  • Page 327 Number Manipulation' on page 301. Web: Src. IP Group ID Defines the IP Group from where the incoming IP call is received. EMS: Source IP Group ID Typically, the IP Group of an incoming INVITE is determined Version 6.6 Mediant 800B GW & E-SBC...
  • Page 328 Mediant 800B GW & E-SBC Parameter Description [PREFIX_SrcIPGroupID] according to the Inbound IP Routing Table. Notes:  This parameter is applicable only to the IP-to-IP routing application.  To denote all IP Groups, leave this field empty.  If this IP Group has a Serving IP Group, then all calls from this IP Group are sent to the Serving IP Group.
  • Page 329 Defines the transport layer type for sending the IP call: [PREFIX_TransportType]  [-1] Not Configured  [0] UDP  [1] TCP  [2] TLS Note: When set to Not Configured (-1), the transport type defined by Version 6.6 Mediant 800B GW & E-SBC...
  • Page 330 Mediant 800B GW & E-SBC Parameter Description the SIPTransportType parameter is used. Web: Dest IP Group ID Defines the IP Group to where you want to route the call. The SIP EMS: Destination IP Group INVITE message is sent to the IP address defined for the Proxy Set ID associated with the IP Group.
  • Page 331 You can also use LDAP routing rules with standard routing rules for Forking Groups.  When the UseDifferentRTPportAfterHold parameter is enabled, every forked call is sent with a different RTP port. Thus, ensure Version 6.6 Mediant 800B GW & E-SBC...

  • Page 332: Configuring Inbound Ip Routing Table

    Mediant 800B GW & E-SBC Parameter Description that the device has available RTP ports for these forked calls. 23.3 Configuring Inbound IP Routing Table The Inbound IP Routing Table page allows you to configure up to 24 inbound call routing rules: ...
  • Page 333 Defines the Request-URI host name prefix of the incoming SIP INVITE [DestPrefix] message. If this routing rule is not required, leave the field empty. Note: The asterisk (*) wildcard can be used to depict any prefix. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 334 Mediant 800B GW & E-SBC Parameter Description Web: Source Host Prefix Defines the From URI host name prefix of the incoming SIP INVITE [SrcHostPrefix] message. If this routing rule is not required, leave the field empty. Notes:  The asterisk (*) wildcard can be used to depict any prefix.

  • Page 335: Ip Destinations Connectivity Feature

    If the destination does not respond to the OPTIONS message, then it is considered unavailable. You can configure the time interval for sending these OPTIONS messages, using the 'Alt Routing Tel to IP Keep Alive Time' parameter. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC These parameters are configured in the Routing General Parameters page (Configuration tab > VoIP menu > GW and IP to IP > Routing > General Parameters), as shown below: Figure ‎ 2 3-5: IP Connectivity Method in Routing General Parameters Page ...
  • Page 337 In the Routing General Parameters page (Configuration tab > VoIP menu > GW and IP to IP > Routing > General Parameters), do the following: Enable alternative routing based on IP connectivity, by setting the 'Enable Alt Routing Tel to IP AltRouting' (Tel2IPEnable) parameter to Enable. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 338: Alternative Routing Based On Sip Responses

    Mediant 800B GW & E-SBC Configure the IP connectivity reason for triggering alternative routing, by setting the 'Alt Routing Tel to IP Mode' parameter (AltRoutingTel2IPMode) to one of the following:  SIP OPTIONS failure  Poor QoS  SIP OPTIONS failure, poor QoS, or unresolved DNS The device plays a tone to the Tel endpoint (for analog interfaces) whenever an alternative route is used.
  • Page 339 Figure ‎ 2 3-7: Tel to IP Reasons - Reasons for Alternative Routing Page Under the 'Tel to IP Reasons' group, select up to five different SIP response codes (call failure reasons) that invoke alternative Tel-to-IP routing. Click Submit. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 340: Pstn Fallback

    Mediant 800B GW & E-SBC 23.5.3 PSTN Fallback The PSTN Fallback feature enables the device to re-route a Tel-to-IP call to the legacy PSTN using one of its trunks if the IP destination is unavailable. For example, if poor voice quality is detected over the IP network, the device attempts to re-route the call to the PSTN.
  • Page 341 For configuring IP-to-Tel routing rules in the Inbound IP Routing table, see 'Configuring Inbound IP Routing Table' on page 332.  The Reasons for Alternative Routing IP to Tel table can also be configured using the table ini file parameter, AltRouteCauseIP2Tel. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC 23.6.2 Alternative Routing to an IP Destination upon a Busy Trunk You can configure the device to forward (i.e., call redirection) IP-to-Tel calls to an alternative IP destination using SIP 3xx responses. This can be done upon the following scenarios: ...
  • Page 343 Request-URI user name and host part (i.e., user@host). The following syntax can also be used: host:port;transport=xxx (i.e., IP address, port and transport type). Note: When configured with a user@host, the original destination number is replaced by the user part. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 344 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 345: Configuring Dtmf And Dialing

    > DTMF & Supplementary submenu > DTMF & Dialing). Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 346: Dialing Plan Features

    Mediant 800B GW & E-SBC 24.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 24.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 290.
  • Page 347 (TimeBetweenDigits parameter), it sends the collected digits. Therefore, this ensures that calls are not rejected as a result of their digit pattern not been completed in the Dial Plan. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 348: External Dial Plan File

    Mediant 800B GW & E-SBC 24.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 539. User's Manual Document #: LTRT-10274...

  • Page 349: Configuring Supplementary Services

    To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP submenu > DTMF & Supplementary submenu > Supplementary Services). Figure ‎ 2 5-1: Supplementary Services Page Version 6.6 Mediant 800B GW & E-SBC...

  • Page 350: Call Hold And Retrieve

    Mediant 800B GW & E-SBC Configure the parameters as required. Click Submit to apply your changes, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server.
  • Page 351 B places A on hold; B hears a dial tone. B calls D and establishes a voice path. A ends call with C; A hears a held tone. B ends call with D. B retrieves call with A. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 352: Call Pickup

    Mediant 800B GW & E-SBC Notes:  If a party that is placed on hold (e.g., B in the above example) is called by another party (e.g., D), then the on-hold party receives a call waiting tone instead of the held tone.

  • Page 353: Call Transfer

    The two calls can be incoming or outgoing calls. This service is similar to NI2 Two B-Channel Transfer (TBCT) Supplementary Service. The main difference is that in Version 6.6 Mediant 800B GW & E-SBC...

  • Page 354: Consultation Transfer For Qsig Path Replacement

    Mediant 800B GW & E-SBC ECT one of the calls must be in HELD state. The ECT standard defines two methods - Implicit and Explicit. In implicit method, the two calls must be on the same trunk. BRI uses the implicit mechanism, and PRI the explicit mechanism.

  • Page 355: Call Forward

    IP address from the routing table (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 6.6 Mediant 800B GW & E-SBC...

  • Page 356: Call Forward Reminder Ring

    Mediant 800B GW & E-SBC 25.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. This is important in that it notifies (audibly) the FXS endpoint user that a call forwarding service is currently being performed.

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

    The codes for the call forward can be defined using the following parameters:  SuppServCodeCFU - Call Forward Unconditional  SuppServCodeCFUDeact - Call Forward Unconditional Deactivation  SuppServCodeCFB - Call Forward on Busy  SuppServCodeCFBDeact - Call Forward on Busy Deactivation Version 6.6 Mediant 800B GW & E-SBC...

  • Page 358: Call Waiting

    Mediant 800B GW & E-SBC  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 359: Message Waiting Indication

    For more information on IP voice mail configuration, refer to the IP Voice Mail CPE Configuration Guide.  For creating a CPT file using AudioCodes CPTWizard utility, refer to CPTWizard Utility User's Guide. To configure MWI, use the following parameters: ...

  • Page 360: Caller Id

    Mediant 800B GW & E-SBC MWI messages. This is supported by setting the VoiceMailInterface parameter to 8.  QSIG MWI: The device also supports the interworking of QSIG MWI to IP (in addition to interworking of SIP MWI NOTIFY to QSIG Facility MWI messages). This provides interworking between an ISDN PBX with voicemail capabilities and a softswitch, which requires information on the number of messages waiting for a specific user.

  • Page 361: Debugging A Caller Id Detection On Fxo

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

  • Page 362: Caller Id On The Ip Side

    Mediant 800B GW & E-SBC Enter the following commands: ait <IP address of PC to collect the debug traces sent from the device> AddChannelIdTrace ALL-WITH-PCM <port number, which starts from 0> Start Make a call to the FXO. To stop the DR recording, at the CLI prompt, type STOP.

  • Page 363: Three-Way Conferencing

    The device supports the following conference modes (configured by the parameter 3WayConferenceMode):  Conferencing managed by an external, AudioCodes Conference (media) server: The Conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.

  • Page 364: Emergency E911 Phone Number Services

    Mediant 800B GW & E-SBC To configure this local, on-board three-way conferencing: Open the Supplementary Services page. Set 'Enable 3-Way Conference' to Enable (Enable3WayConference = 1). Set 'Three Way Conference Mode' to On Board (3WayConferenceMode = 2). 'Flash Keys Sequence...
  • Page 365 MFR1DetectorEnable = 1  DelayBeforeDIDWink = 200 (for 200 msec) - can be configured in the range from 0 (default) to 1000. Note: Modification of the WinkTime and FlashHookPeriod parameters require a device reset. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 366 Mediant 800B GW & E-SBC The outgoing SIP INVITE message contains the following headers: INVITE sip:Line@DomainName From: <sip:*81977820#@sipgw>;tag=1c143 To: <sip:Line@DomainName> Where:  Line = as configured in the Endpoint Phone Number Table  SipGtw = configured by the SIPGatewayName parameter ...

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

    RFC 2833 hookflash Telephony event (according to the HookFlashOption parameter). Following the "hookflash" Wink signal, the PSAP sends DTMF digits. These digits are detected by the device and forwarded to the IP, using RFC 2833 telephony events (or Version 6.6 Mediant 800B GW & E-SBC...
  • Page 368 Mediant 800B GW & E-SBC inband, depending on the device's configuration). Typically, this Wink signal followed by the DTMF digits initiates a call transfer. For supporting the E911 service, used the following configuration parameter settings:  Enable911PSAP = 1 (also forces the EnableDIDWink and EnableReversalPolarity) ...
  • Page 369 REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO ,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-FXO/v.6.00A.020.077 Privacy: none P-Asserted-Identity: "0123456789" <sip:3333344444@audiocodes.com> Content-Type: application/sdp Content-Length: 253 o=AudiocodesGW 771609035 771608915 IN IP4 10.33.37.78 s=Phone-Call c=IN IP4 10.33.37.78 t=0 0 m=audio 4000 RTP/AVP 8 0 101 a=rtpmap:8 pcma/8000 Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv  Example B: The detection of a Wink signal generates the following SIP INFO message: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 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...

  • Page 371: Enhanced 9-1-1 Support For Lync Server 2010

    E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller. This section describes the E9-1-1 solution provided by Microsoft Lync Server 2010 (hereafter referred to as Lync Server 2010), and the deployed AudioCodes ELIN Gateway which provides the ISDN (or CAMA) connectivity to the PSTN-based E9-1-1 emergency providers.

  • Page 372: Microsoft Lync Server 2010 And E9-1-1

    Mediant 800B GW & E-SBC The PSTN identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network. The E9-1-1 Selective Router determines the geographical location of the caller by requesting this information from an Automatic Location Identification (ALI) database based on the phone number or Automatic Number Identifier (ANI) of the 911 caller.
  • Page 373 When a user manually provides a location, the location is mapped based on the MAC address of the default gateway of the client’s network and stored on the client. When the client returns to Version 6.6 Mediant 800B GW & E-SBC...
  • Page 374 Mediant 800B GW & E-SBC any previously stored location, the client is automatically set to that location. A user can also manually select any location stored in the local users table and manage existing entries. 25.11.4.2.2 Adding ELINs to the Location Information Server...
  • Page 375 ERL with a unique ELIN. Table ‎ 2 5-4: Designating ERLs and Assigning to ELINs ERL Number Physical Area IP Address ELIN Floor 1 10.13.124.xxx 503 972-4410 Floor 2 10.15.xxx.xxx 503 972-4411 Floor 3 10.18.xxx.xxx 503 972-4412 Version 6.6 Mediant 800B GW & E-SBC...

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

    The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN. Figure ‎ 2 5-9: AudioCodes ELIN Gateway for E9-1-1 in Lync Server 2010 Environment 25.11.4.3.1...
  • Page 377 ELIN is disregarded and no longer used (for PSAP callback). Therefore, table entries of only the most recently terminated E9-1-1 callers are considered in the ELIN table. The maximum entries in the ELIN table depend on the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment: ...
  • Page 378 Mediant 800B GW & E-SBC o=- 0 0 IN IP4 Client s=session c=IN IP4 Client t=0 0 m=audio 30684 RTP/AVP 114 111 112 115 116 4 3 8 0 106 97 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000...
  • Page 379 The ELIN Gateway supports the receipt of up to five ELIN numbers in the XML message of each incoming SIP INVITE message. As discussed in the preceding sections, the ELIN Gateway sends the ELIN number as the E9-1-1 calling number to the PSTN-based Version 6.6 Mediant 800B GW & E-SBC...

  • Page 380: Configuring Audiocodes Elin Gateway

    25.11.4.4 Configuring AudioCodes ELIN Gateway This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment. 25.11.4.4.1 Enabling the E9-1-1 Feature By default, the E9-1-1 feature in the ELIN Gateway for Lync Server 2010 is disabled.
  • Page 381 You can view the ELIN table of the ELIN Gateway. The method depends on the type of device:  Using the following CLI command: # show voip gw e911 ELIN Time Count Index Call From ------------------------------------------------------------ 4257275678 22:11:52 0 4258359333 Version 6.6 Mediant 800B GW & E-SBC...

  • Page 382: Multilevel Precedence And Preemption

    Mediant 800B GW & E-SBC 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616 22:11:45 0 4258359777 ------------ Current Time: 22:12:40  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump 25.12 Multilevel Precedence and Preemption The device supports Multilevel Precedence and Preemption (MLPP) service.
  • Page 383 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): Version 6.6 Mediant 800B GW & E-SBC...

  • Page 384: Mlpp Preemption Events In Sip Reason Header

    Mediant 800B GW & E-SBC Table ‎ 2 5-8: Mapping of SIP Resource-Priority Header to PRI Precedence Level for MLPP MLPP Precedence Level PRI Precedence Level SIP Resource-Priority Header Field Routine Priority Immediate Flash Flash Override  If the network-domain field in the Resource-Priority header is any value other than "uc", then the device sets the Precedence Level field to "0 1 0 0"...

  • Page 385: 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 6.6 Mediant 800B GW & E-SBC...

  • Page 386: Denial Of Collect Calls

    Mediant 800B GW & E-SBC 25.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. When this feature is enabled upon rejecting the incoming call, the device sends a sequence of signals to the PSTN.
  • Page 387 [0] Allowed = The device sends the string defined in the 'Caller ID' field when this BRI extension makes a Tel-to-IP call.  [1] Restricted = The string defined in the 'Caller ID' field is not sent. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 388: Advice Of Charge Services For Euro Isdn

    Mediant 800B GW & E-SBC Parameter Description Caller ID Enabled Enables the receipt of Caller ID. [ISDNSuppServ_IsCallerIDEnabl  [0] Disabled = The device does not send Caller ID information to the BRI extension.  [1] Enabled = The device sends Caller ID information to the BRI extension 25.15 Advice of Charge Services for Euro ISDN...

  • Page 389: Configuring Voice Mail

    Open the Voice Mail Settings page (Configuration tab > VoIP menu > GW and IP to IP > Advanced Applications > Voice Mail Settings). Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 390 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 391: 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 827. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 392: Configuring Metering Tones

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

  • Page 393: Configuring Charge Codes

    (AoC) services for Euro ISDN trunks (see Advice of Charge Services for Euro ISDN on page 388).  The Charge Codes table can also be configured using the table ini file parameter, ChargeCode. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 394: Configuring Fxo Settings

    Mediant 800B GW & E-SBC  To configure the Charge Codes: Open the Charge Codes Table page (Configuration tab > VoIP menu > GW and IP to IP submenu > Analog Gateway submenu > Charge Codes). Alternatively, you can access this page from the Metering Tones page (see 'Configuring Metering Tones' on page 392).

  • Page 395: Configuring Authentication

    After you click Submit, the password is displayed as an asterisk (*).  The Authentication table can also be configured using the table ini file parameter, Authentication (see 'Configuration Parameters Reference' on page 643). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 396: Configuring Automatic Dialing

    Mediant 800B GW & E-SBC  To configure authentication credentials per port: Set the parameter 'Registration Mode' (AuthenticationMode) to Per Endpoint. This can be configured in any of the following pages:  Proxy & Registration page (see 'Configuring Proxy and Registration Parameters' on page 224).
  • Page 397 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 6.6 Mediant 800B GW & E-SBC...

  • Page 398: Configuring Caller Display Information

    Mediant 800B GW & E-SBC Parameter Description Hotline Dial Tone Duration Defines the duration (in seconds) after which the destination [TargetOfChannel_HotLineToneD phone number is automatically dialed. This is applicable only if uration] the port has been configured for Hotline (i.e., 'Auto Dial Status' is set to Hotline).

  • Page 399: Configuring Call Forward

    The Call Forward table can also be configured using the table ini file parameter, FwdInfo.  To configure Call Forward per port: Open the Call Forward Table page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Call Forward). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 400: Configuring Caller Id Permissions

    Mediant 800B GW & E-SBC Configure the table as required. For descriptions of the parameters, see the table below. Click Submit to apply your changes. Table ‎ 2 6-5: Call Forward Table Parameter Description Parameter Description Forward Type Defines the condition upon which the call is forwarded.

  • Page 401: Configuring Call Waiting

    For additional call waiting configuration, see the following parameters: FirstCallWaitingToneID (in the CPT file), TimeBeforeWaitingIndication, WaitingBeepDuration, TimeBetweenWaitingIndications, and NumberOfWaitingIndications.  The Call Waiting table can also be configured using the table ini file parameter, CallWaitingPerPort. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 402: Rejecting Anonymous Calls

    Mediant 800B GW & E-SBC  To enable call waiting per port: Open the Call Waiting page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Call Waiting). Configure the table as required. For a description of the parameter, see the table below.
  • Page 403 FXS Port Last Defines the last port in the FXS port range. [ToneIndex_FXSPort_Last] Source Prefix Defines the prefix of the calling number. [ToneIndex_SourcePrefix] Destination Prefix Defines the prefix of the called number. [ToneIndex_DestinationPrefix] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 404: Fxs/Fxo Coefficient Types

    Mediant 800B GW & E-SBC Parameter Description Priority Index Defines the index of the distinctive ringing and call waiting tones. [ToneIndex_PriorityIndex] The call waiting tone index equals to the Priority Index plus the value of the FirstCallWaitingToneID parameter. For example, if you want to use the call waiting tone in the CPT file at Index #9, you need to enter "1"...

  • Page 405: Fxo Operating Modes

    Waiting for Dial Tone: Enables the device to dial the digits to the Tel side only after detecting a dial tone from the PBX line. The ini file parameter IsWaitForDialTone is used to configure this operation. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 406: Two-Stage Dialing

    Mediant 800B GW & E-SBC  Time to Wait Before Dialing: Defines the time (in msec) between seizing the FXO line and starting to dial the digits. The ini file parameter WaitForDialTime is used to configure this operation. Note: The ini file parameter IsWaitForDialTone must be disabled for this mode.

  • Page 407: Did Wink

    Automatic dialing is defined using the Web interface's Automatic Dialing (TargetOfChannel ini file parameter) page, described in see 'Configuring Automatic Dialing' on page 396. The SIP call flow diagram below illustrates Automatic Dialing. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 408: Collecting Digits Mode

    Mediant 800B GW & E-SBC 26.14.2.2 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 ‎ 2 6-9: Call Flow for Collecting Digits Mode...

  • Page 409: Fxo Supplementary Services

    Call Progress Tones file. If these frequencies are unknown, define them in the CPT file. The tone produced by the PBX / CO must be recorded and its frequencies analyzed. Adding a reorder Version 6.6 Mediant 800B GW & E-SBC...

  • Page 410: Call Termination Before Call Establishment

    Mediant 800B GW & E-SBC tone to the CPT file can be done using AudioCodes CPTWizard utility (refer to the CPTWizard Utility User's Guide). This method is slightly less reliable than the previous one. You can use the CPTWizard to analyze Call Progress Tones generated by any PBX or telephone network.

  • Page 411: Ring Detection Timeout

    FXO interfaces with ports connected directly to the PBX lines (shown in the figure below)  FXS interfaces for the 'remote PBX extension'  Analog phones (POTS)  PBX (one or more PBX loop start lines)  LAN network Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC 26.15.1 Dialing from Remote Extension (Phone at FXS) The procedure below describes how to dial from the 'remote PBX extension' (i.e., phone connected to the FXS interface).  To make a call from the FXS interface: Off-hook the phone and wait for the dial tone from the PBX.

  • Page 413: Call Waiting For Remote Extensions

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

  • Page 414: Fxs Gateway Configuration

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

  • Page 415: Fxo Gateway Configuration

    IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. Figure ‎ 2 6-14: FXO Tel-to-IP Routing Configuration In the FXO Settings page (see 'Configuring FXO Parameters' on page 394), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 416 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 417: Session Border Controller Application

    Part VI Session Border Controller Application...

  • Page 419: Sbc Overview

    Changes the SIP Contact header to the device's own address.  Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC Version 6.6 Mediant 800B GW & E-SBC...

  • Page 420: Sip Network Definitions

    Mediant 800B GW & E-SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following:  Manipulation of SIP URI user and host parts.  Connection to ITSP SIP trunks on behalf of an IP-PBX - the device can register and utilize user and password to authenticate for the IP-PBX.
  • Page 421 'SBC Manipulations' on page 470. SIP message manipulations: You can configure SIP message manipulation rules that can add, remove, and/or modify SIP headers and parameters. For more information, see 'Configuring SIP Message Manipulation' on page 228. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 422: User Registration And Internal Database

    Mediant 800B GW & E-SBC The flowchart below illustrates the SBC process: Figure ‎ 2 7-1: Routing Process 27.3 User Registration and Internal Database To allow registrations to traverse the SBC, the device must be configured with at least one User-type IP Group.

  • Page 423: Initial Registration Request Processing

    The device manages a dynamic database that is updated according to registration requests that traverse the SBC. Each database entry represents a binding between an AOR and one or more contact. Database bindings are added upon successful registration Version 6.6 Mediant 800B GW & E-SBC...

  • Page 424: Routing Using Internal Database

    Mediant 800B GW & E-SBC responses. For specific registrations, the AOR is obtained from the SIP To header and the contact is taken from the SIP Contact header. Database bindings are removed in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero) ...

  • Page 425: Registration Restriction Control

    (e.g. audio, fax, modem, DTMF). Each offer/answer may create more than one media session of different types (e.g. audio and fax). In a SIP dialog, multiple offer/answer transactions may occur, each may change the media sessions characteristics (e.g. IP Version 6.6 Mediant 800B GW & E-SBC...
  • Page 426 Mediant 800B GW & E-SBC address, port, coders, media types, and RTP mode). The media capabilities exchanged in an offer/answer transaction include the following:  Media types (Audio, Secure Audio, Video, Fax, Text...)  IP addresses and ports of the media flow ...

  • Page 427: Media Anchoring Without Transcoding (Transparent)

    IP Group). Therefore, to allow user agents of different IP Groups to communicate with each other (regardless of their capabilities), an extended coders table with at least one coder that is supported by each IP Groups' user agents needs to be Version 6.6 Mediant 800B GW & E-SBC...
  • Page 428 Mediant 800B GW & E-SBC assigned to each IP Group. Therefore, each offer destined to specific IP Groups include this coder. In the scenario depicted in the figure below, the IP phone on the LAN side initiates a call to the IP phone on the WAN.

  • Page 429: No Media Anchoring

     Opening voice channels and allocation of IP media ports are not required The No Media Anchoring feature is typically implemented in the following scenarios:  SBC device is located within the LAN. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 430 Mediant 800B GW & E-SBC  Calls between two SIP UA's in the same LAN and signals are sent to a SIP proxy server (or hosted IP PBX) located in the WAN. Figure ‎ 2 7-5: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring include the following: ...

  • Page 431: Transcoding Modes

    The transcoding mode can be configured using the parameters TranscodingMode and IPProfile. Note: To implement transcoding, you must configure the number of required DSP channels for transcoding (for example, MediaChannels = 120). Each transcoding session uses two DSP resources. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 432: Restricting Coders

    Mediant 800B GW & E-SBC 27.4.5 Restricting Coders The SBC Allowed Coders (coders restriction) feature determines the coders that can be used for a specific SBC leg. This provides greater control over bandwidth by enforcing the use of specific coders (allowed coders groups) while preventing the use of other coders.

  • Page 433: Prioritizing Coder List In Sdp Offer

    In addition to restricting the use of coders with Allowed coders, the device can prioritize the coders listed in the SDP offer. This feature is referred to as Coder Preference. This is done on both SBC legs: Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC  Incoming SDP offer: The device arranges the coder list according to the order in the Allowed Coders Group table. The coders listed higher up in the table take preference over ones listed lower down in the table. This feature is enabled by setting the 'Allowed Coders Mode' parameter in the IP Profile table to Preference or Restriction and Preference.

  • Page 435: Interworking Dtmf Methods

    SBCFaxCodersGroupID: defines the supported fax coders (from the Coders Group Settings table).  SBCFaxOfferMode: determines the fax coders sent in the outgoing SDP offer.  SBCFaxAnswerMode: determines the fax coders sent in the outgoing SDP answer. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 436: Limiting Sbc Call Duration

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

  • Page 437: Interworking Sip 3Xx Redirect Responses

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

  • Page 438: Local Handling Of Sip 3Xx

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

  • Page 439: Interworking Sip Refer Messages

    Forwarding early media after REFER while attempting to avoid transcoding (by sending session update)  Interoperate with environments were different SIP UAs lack basic SIP functionality such as re-INVITE, UPDATE, PRACK, Delayed Offer, re-INVITE without SDP Version 6.6 Mediant 800B GW & E-SBC...

  • Page 440: Interworking Sip Prack Messages

    Mediant 800B GW & E-SBC  Session updates after connect to avoid transcoding The handling of REFER can be configured for all calls, using the global parameter SBCReferBehavior. For configuring different REFER handling options for different UAs (i.e., IP Groups), use the IP Profile table parameter, 'SBC Remote Refer Behavior'.
  • Page 441 Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Figure ‎ 2 7-7: SBC Early Media RTP 18x without SDP Version 6.6 Mediant 800B GW & E-SBC...

  • Page 442: Interworking Sip Re-Invite Messages

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

  • Page 443: Interworking Sip Re-Invite To Update

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

  • Page 444: Call Survivability

    Mediant 800B GW & E-SBC 27.9 Call Survivability This section describes various call survivability features supported by the SBC device. 27.9.1 Auto-Provisioning of Subscriber-Specific Information for BroadWorks Server for Survivability This feature enables SBC user registration for interoperability with BroadSoft BroadWorks server to provide call survivability in case of connectivity failure with the BroadWorks server, for example, due to a WAN failure.
  • Page 445 Manipulations' on page 472), add a manipulation rule for the secondary extensions (e.g., 601 and 602) so that they also register in the device's database under the primary extension contact (e.g., 600):  Set the 'Manipulation Purpose' field to Shared Line. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 446: Call Survivability For Call Centers

    Mediant 800B GW & E-SBC  Set the 'Source IP Group' field to the IP Group ID that you created for the users (e.g., 2).  Set the 'Source Username Prefix' field to represent the secondary extensions (e.g., 601 and 602).
  • Page 447 The 'Destination Type' field is set to Hunt Group, which is specifically used for call center survivability.  The 'Destination IP Group ID' field is set to the IP Group of the call center agents. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 448: Survivability Mode Display On Aastra Ip Phones

    Mediant 800B GW & E-SBC The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure ‎ 2 7-13: Routing Rule Example for Call Center Survivability 27.9.4 Survivability Mode Display on Aastra IP Phones...

  • Page 449: Call Forking

    (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, then it is possible that the SDP answer that was forwarded to the INVITE- Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC initiating UA is not relevant, and media synchronization is needed between the two UAs. Media synchronization is done by sending a re-INVITE request immediately after the call is established. The re-INVITE is sent without an offer to the INVITE-initiating UA. This causes the UA to send an offer which is forwarded to the UA that confirmed the call.

  • Page 451: Sbc Configuration

    Open the General Settings page (Configuration tab > VoIP menu > SBC > General Settings). Figure ‎ 2 8-1: General Settings Page Configure the parameters as required. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 452: Configuring Admission Control

    Mediant 800B GW & E-SBC 28.2 Configuring Admission Control The Admission Control page allows you to define up to 100 rules for limiting the number of concurrent calls (SIP dialogs). These call limits can be applied per SRD, IP Group, SIP request type (e.g., INVITEs), SIP dialog direction (e.g., inbound), and/or per user (identified...
  • Page 453 (not the subsequent requests that can be of stType] different type and direction).  [0] All = (Default) Includes the total number of all dialogs.  [1] INVITE  [2] SUBSCRIBE  [3] Other Version 6.6 Mediant 800B GW & E-SBC...

  • Page 454: Configuring Allowed Coder Groups

    Mediant 800B GW & E-SBC Parameter Description Request Direction Defines the direction of the SIP request to which the rule applies. [SBCAdmissionControl_Reque  [0] Both = (Default) Rule applies to inbound and outbound SIP stDirection] dialogs.  [1] Inbound = Rule applies only to inbound SIP dialogs.
  • Page 455 From the 'Allowed Coders Group ID' drop-down list, select an ID for the Allowed Coder Group. In the Coder Name table, select coders for the Allowed Coder Group. Click Submit to apply your changes. To save the changes to flash memory, see 'Saving Configuration' on page 530. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 456: Routing Sbc

    Mediant 800B GW & E-SBC 28.4 Routing SBC This section describes the configuration of the routing entities for the SBC application. These include the following:  Classification rules - see 'Configuring the Classification Rules' on page  Condition rules - see 'Configuring Condition Rules' on page ...
  • Page 457 'Classification Failure Response Type' parameter in the SIP Interface table (see 'Configuring SIP Interface Table' on page 203). The flowchart below illustrates the classification process: Figure ‎ 2 8-4: Classification Process (Identifying IP Group or Rejecting Call) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 458 Mediant 800B GW & E-SBC Notes:  Incoming REGISTER messages are saved in the device’s registration database and sent to a destination only if they are associated with a source User-type IP Group.  The Classification table can also be configured using the table ini file parameter, Classification.
  • Page 459 Prefix incoming SIP dialog. Note: The prefix can be a single digit or a range of digits. For available [Classification_DestUser notations, see 'Dialing Plan Notation for Routing and Manipulation' on namePrefix] page 641. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC Parameter Description Destination Host Defines the prefix of the destination Request-URI host name of the [Classification_DestHost] incoming SIP dialog request. If this routing rule is not required, leave the field empty. The asterisk (*) symbol can be used to depict any destination host prefix.

  • Page 461: Configuring Condition Rules

    For a detailed description of the syntax for configuring SIP message manipulation rules, refer to SIP Message Manipulations Quick Reference Guide.  The Condition table can also be configured using the table ini file parameter, ConditionTable. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC  To configure Condition rules: Open the Condition Table page (Configuration tab > VoIP menu > SBC > Routing SBC > Condition Table). Click the Add button; the following dialog box appears: Figure ‎ 2 8-6: Condition Table Page - Add Record Dialog Box Configure the rule as required.
  • Page 463  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). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 464 Mediant 800B GW & E-SBC  Re-routing of SIP requests: This table enables you to configure "re-routing" rules of requests (e.g., INVITEs) that the device sends upon receipt of SIP 3xx responses or REFER messages. These rules are configured for destinations that do not support receipt of 3xx or REFER and where the device handles the requests locally (instead of forwarding the 3xx or REFER to the destination).
  • Page 465 Message Condition Selects a Message Condition rule. To configure Message [IP2IPRouting_MessageCondition] Condition rules, see 'Configuring Condition Rules' on page 461. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect Version 6.6 Mediant 800B GW & E-SBC...
  • Page 466 Mediant 800B GW & E-SBC Parameter Description [IP2IPRouting_ReRouteIPGroupID] response (e.g., 3xx) or REFER message. This field is typically used for re-routing requests (e.g., INVITEs) when interworking is required for SIP 3xx redirect responses or REFER messages (for more information, see 'Interworking...
  • Page 467 SRD if both are configured in this table. Destination Address Defines the destination to where the call is sent. This can be [IP2IPRouting_DestAddress] an IP address or a domain name (e.g., domain.com). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 468 Mediant 800B GW & E-SBC Parameter Description If ENUM-based routing is used (i.e., the 'Destination Type' parameter is set to ENUM) this parameter defines the IP address or domain name (FQDN) of the ENUM service, for example, e164.arpa, e164.customer.net, or NRENum.net.

  • Page 469: Configuring Alternative Routing Reasons

    SIP request with a SIP 486 "Busy Here" response.  The SBC Alternative Routing Reasons table can also be configured using the table ini file parameter, SBCAlternativeRoutingReasons. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 470: Sbc Manipulations

    Mediant 800B GW & E-SBC  To configure SIP reason codes for alternative IP routing: Open the SBC Alternative Routing Reasons page (Configuration tab > VoIP menu > SBC > Routing SBC > Alternative Routing Reasons). Figure ‎ 2 8-10: Alternative Routing Reasons Page Configure different call failure reasons that invoke alternative routing.
  • Page 471 CSeq: 38 INVITE Contact: <sip:7000@212.179.1.12> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 5 IN IP4 212.179.1.11 s=Phone-Call c=IN IP4 212.179.1.11 t=0 0 m=audio 8000 RTP/AVP 8 Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 The SIP message manipulations in the example above (contributing to typical topology hiding) are as follows:  Inbound source SIP URI user name from "7000" to "97000": From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe ...
  • Page 473 [1] Yes = If the above row entry rule matched the call, consider this row entry as a match as well and perform the manipulation specified by this rule. Note: Additional manipulation can only be done on a Version 6.6 Mediant 800B GW & E-SBC...
  • Page 474 Mediant 800B GW & E-SBC Parameter Description different SIP URI, source or destination, to the rule configured in the row above as configured by the 'Manipulated URI' parameter (see below). Manipulation Purpose Defines the purpose of the manipulation: [IPInboundManipulation_Manipulati ...

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

    Manipulation operation (Action), for example, remove user-defined number of characters from the left of the SIP URI user part. If the incoming call matches the characteristics of a rule, then its manipulation action is applied. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 476 Mediant 800B GW & E-SBC Notes:  Manipulated destination SIP URI user names are done on the following SIP headers: Request URI, To, and Remote-Party-ID (if exists).  Manipulated source SIP URI user names are done on the following SIP...
  • Page 477 [2] REGISTER = Only SIP REGISTER messages.  [3] SUBSCRIBE = Only SIP SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except Version 6.6 Mediant 800B GW & E-SBC...
  • Page 478 Mediant 800B GW & E-SBC Parameter Description REGISTER. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect [IPOutboundManipulation_ReRo response (e.g., 3xx) or REFER message. This parameter is uteIPGroupID] typically used for re-routing requests (e.g., INVITEs) when interworking is required for SIP 3xx redirect responses or REFER messages.
  • Page 479 The device identifies an incoming user as restricted if one of the following exists:  From header user is anonymous.  P-Asserted-Identity and Privacy headers contain the value "id". Note: All restriction logic is performed after the user number has been manipulated. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 480 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 481: Cloud Resilience Package Application

    Part VII Cloud Resilience Package Application...

  • Page 483: Crp Overview

    One of the main advantages of CRP is that it enables quick-and-easy configuration. This is accomplished by its pre-configured routing entities, whereby only minimal configuration is required such as for IP addresses to get the device up and running and deployed in the network. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 484 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 485: Crp Configuration

    Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'Enable CRP Application' drop-down list, select Enable. Save (burn) the changes to the device's flash memory with a device reset (see Saving Configuration on 530). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 486: Configuring Call Survivability Mode

    Mediant 800B GW & E-SBC 30.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.

  • Page 487: 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 206. Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC 30.4 Pre-Configured IP-to-IP Routing Rules 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 486. Notes: ...

  • Page 489: Stand-Alone Survivability Application

    Part VIII Stand-Alone Survivability Application...

  • Page 491: Sas Overview

    31.1.1 SAS Outbound Mode This section describes the SAS outbound mode, which includes the following states:  Normal state (see 'Normal State' on page 492)  Emergency state (see 'Emergency State' on page 492) Version 6.6 Mediant 800B GW & E-SBC...

  • Page 492: Normal State

    Mediant 800B GW & E-SBC 31.1.1.1 Normal State In normal state, SAS receives REGISTER requests from the enterprise's UAs and forwards them to the external proxy (i.e., outbound proxy). Once the proxy replies with a SIP 200 OK, the device records the Contact and address of record (AOR) of the UAs in its internal SAS registration database.

  • Page 493: Sas Redundant Mode

    UAs, you can configure SAS to ignore messages received from UAs in normal state (the 'SAS Survivability Mode' parameter must be set to 'Always Emergency' / 2) and thereby, “force” the UAs to switch back to their primary proxy. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 494: Normal State

    Mediant 800B GW & E-SBC 31.1.2.1 Normal State In normal state, the UAs register and operate directly with the external proxy. Figure ‎ 3 1-3: SAS Redundant Mode in Normal State (Example) 31.1.2.2 Emergency State If the UAs detect that their primary (external) proxy does not respond, they immediately register to SAS and start routing calls to it.

  • Page 495: Sas Routing

    31.2.1 SAS Routing in Normal State The flowchart below displays the routing logic for SAS in normal state for INVITE messages received from UAs: Figure ‎ 3 1-5: Flowchart of INVITE from UA's in SAS Normal State Version 6.6 Mediant 800B GW & E-SBC...
  • Page 496 Mediant 800B GW & E-SBC The flowchart below displays the routing logic for SAS in normal state for INVITE messages received from the external proxy: Figure ‎ 3 1-6: Flowchart of INVITE from Primary Proxy in SAS Normal State User's Manual...

  • Page 497: Sas Routing In Emergency State

    ‎ 3 1. SAS Overview User's Manual 31.2.2 SAS Routing in Emergency State The flowchart below shows the routing logic for SAS in emergency state: Figure ‎ 3 1-7: Flowchart for SAS Emergency State Version 6.6 Mediant 800B GW & E-SBC...
  • Page 498 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 499: Sas Configuration

    The procedure below describes how to configure SAS settings that are common to all SAS modes. This includes various SAS parameters as well as configuring the Proxy Set for the SAS proxy (if required). The SAS Proxy Set ID defines the address of the UAs' external proxy. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 500 Mediant 800B GW & E-SBC  To configure common SAS settings: Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand Alone Survivability). Define the port used for sending and receiving SAS messages. This can be any of the following port types: ...
  • Page 501 From the 'Enable Proxy Keep Alive' drop-down list, select Using Options. This instructs the device to send SIP OPTIONS messages to the proxy for the keep- alive mechanism. Figure ‎ 3 2-2: Defining SAS Proxy Server Click Submit to apply your settings. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 502: Configuring Sas Outbound Mode

    Mediant 800B GW & E-SBC 32.2 Configuring SAS Outbound Mode This section describes how to configure the SAS outbound mode. These settings are in addition to the ones described in 'Configuring Common SAS Parameters' on page 499. Note: The VoIP CPEs (such as IP phones or residential gateways) need to be...

  • Page 503: Configuring Gateway Application With Sas

    Figure ‎ 3 2-3: Enabling Proxy Server for Gateway Application Click Submit. Open the Proxy Sets Table page (Configuration tab > VoIP menu > Control Network submenu > Proxy Sets Table). From the 'Proxy Set ID' drop-down list, select 0. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 504 Mediant 800B GW & E-SBC In the first 'Proxy Address' field, enter the IP address and port of the device (in the format x.x.x.x:port). This is the port as defined in the 'SAS Local UDP/TCP/TLS Port' field (see 'Configuring Common SAS Parameters' on page 499).

  • Page 505: Gateway With Sas Redundant Mode

    Figure ‎ 3 2-7: Defining Proxy Servers for Gateway Application Click Submit. Disable the use of user=phone in the SIP URL: Open the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions submenu > General Parameters). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 506: Advanced Sas Configuration

    Mediant 800B GW & E-SBC From the 'Use user=phone in SIP URL' drop-down list, select No. This instructs the Gateway application not to use user=phone in SIP URL and therefore, REGISTER and INVITE messages use SIP URI. (By default, REGISTER messages are sent with sip uri and INVITE messages with tel uri.)

  • Page 507: Manipulating Destination Number Of Incoming Invite

    Request-URI user part. In normal state, the numbers are not manipulated. In this state, SAS searches the number 552155551234 in its database and if found, it sends the INVITE containing this number to the UA. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 508 Mediant 800B GW & E-SBC  To manipulate the destination number in SAS emergency state: Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand Alone Survivability). From the 'SAS Inbound Manipulation Mode' (SASInboundManipulationMode) drop- down list, select Emergency Only.
  • Page 509 For example, if you enter 3 and the user name is veFromRight] "john", the new user name is "j". Note: If both 'Remove From Right' and 'Leave From Right' parameters are configured, the 'Remove From Right' setting is applied first. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 510: Sas Routing Based On Ip-To-Ip Routing Table

    Mediant 800B GW & E-SBC Parameter Description Leave From Right Defines the number of characters that you want retained from the [IPInboundManipulation_Leave right of the user name. FromRight] Note: If both 'Remove From Right' and 'Leave From Right' parameters are configured, the 'Remove From Right' setting is applied first.
  • Page 511 Typically, the IP Group of an incoming SIP dialog is determined (or classified) using the ‘Classification’ table (see Configuring Classification Rules on page 456). If not used (i.e., any IP Group), simply leave the field empty. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 512 Mediant 800B GW & E-SBC Parameter Description The default is -1. Source Username Prefix Defines the prefix of the user part of the incoming SIP dialog's [IP2IPRouting_SrcUsernameP source URI (usually the From URI). You can use special notations refix] for denoting the prefix. For example, to denote any prefix, use the asterisk (*) symbol;...
  • Page 513 'Destination Address' field). However, if both parameters are configured, then the IP Group takes precedence. If the destination IP Group is of USER type, the device searches for a match between the Request-URI (of the received SIP dialog) to Version 6.6 Mediant 800B GW & E-SBC...
  • Page 514 Mediant 800B GW & E-SBC Parameter Description an AOR registration record in the device's database. The SIP dialog is then sent to the IP address of the registered contact. The default is -1. Notes:  This parameter is only relevant if the parameter 'Destination Type' is set to 'IP Group'.

  • Page 515: Blocking Calls From Unregistered Sas Users

    To block calls from unregistered SAS users: Open the SAS Configuration page (Configuration tab > VoIP menu > SAS Stand Alone Survivability). From the 'SAS Block Unregistered Users' drop-down list, select Block. Click Submit to apply your changes. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 516: Configuring Sas Emergency Calls

    Mediant 800B GW & E-SBC 32.5.5 Configuring SAS Emergency Calls You can configure SAS to route emergency calls (such as 911 in North America) directly to the PSTN through its FXO interface or E1/T1 trunk. Thus, even during a communication failure with the external proxy, enterprise UAs can still make emergency calls.

  • Page 517: Re-Using Tcp Connections

     [1]: Enable - SAS changes the Contact header so that it points to the SAS host and therefore, the top-most Via header and the Contact header point to the same host. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 518: Viewing Registered Sas Users

    Mediant 800B GW & E-SBC 32.6 Viewing Registered SAS Users You can view all the users that are registered in the SAS registration database. This is displayed in the 'SAS/SBC Registered Users page, as described in 'Viewing Registered Users' on page 587.

  • Page 519: Sas Cascading

    SAS Routing table. In this example, a call is routed from SAS Gateway (A) user to a user on SAS Gateway (B). Figure ‎ 3 3-1: SAS Cascading Using SAS Routing Table - Example Version 6.6 Mediant 800B GW & E-SBC...
  • Page 520 Mediant 800B GW & E-SBC  SAS Redundancy mode: If users cannot be distinguished (i.e., associated to a specific SAS gateway), then the SAS Redundancy feature is used to configure SAS Cascading. This mode routes the call in a loop fashion, from one SAS gateway to the next, until the user is located.

  • Page 521: Ip Media Capabilities

    Part IX IP Media Capabilities...

  • Page 523: Transcoding Using Third-Party Call Control

    In the example below, an Application Server sends a special INVITE that consists of two media lines to perform transcoding between G.711 and G.729: m=audio 20000 RTP/AVP 0 c=IN IP4 A.example.com m=audio 40000 RTP/AVP 18 c=IN IP4 B.example.com Version 6.6 Mediant 800B GW & E-SBC...
  • Page 524 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 525: Maintenance

    Part X Maintenance...

  • Page 527: Basic Maintenance

    'Toolbar Description' on page 34) 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 36). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 528: Remotely Resetting Device Using Sip Notify

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

  • Page 529: Locking And Unlocking The Device

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

  • Page 530: Saving Configuration

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

  • Page 531: Resetting Channels

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

  • Page 533: Software Upgrade

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

  • Page 535: 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 536 Mediant 800B GW & E-SBC  [3] Busy Tone  [4] Congestion Tone  [6] Warning Tone  [7] Reorder Tone  [8] Confirmation Tone  [9] Call Waiting Tone - heard by the called party  [15] Stutter Dial Tone ...

  • Page 537: Distinctive Ringing

     [Ringing Pattern #X]: Contains the Xth ringing pattern definition (starting from 0 and not exceeding the number of Distinctive Ringing patterns defined in the first section minus 1) using the following keys: Version 6.6 Mediant 800B GW & E-SBC...
  • Page 538 Mediant 800B GW & E-SBC  Ring Type: Must be equal to the Ringing Pattern number.  Freq [Hz]: Frequency in hertz of the ringing tone.  First (Burst) Ring On Time [10 msec]: 'Ring On' period (in 10 msec units) for the first cadence on-off cycle.

  • Page 539: Cas Files

    Plans, as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Install the converted file on the device, as described in 'Loading Auxiliary Files' on Version 6.6...

  • Page 540: Dialing Plans For Digit Collection

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

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

    Mediant 800B GW & E-SBC Notes:  The Dial Plan file must not contain overlapping prefixes. Attempting to process an overlapping configuration by the DConvert utility results in an error message specifying the problematic line.  The Dial Plan index can be selected globally for all calls (as described in the previous procedure), or per specific calls using Tel Profiles.
  • Page 543 From Left' field is set to '4'.  The Destination Prefix' field is set to the value "LONG" and the 'Stripped Digits From Left' field is set to '4'. Figure ‎ 3 7-2: Configuring Manipulation for Removing Label Version 6.6 Mediant 800B GW & E-SBC...

  • Page 544: Obtaining Ip Destination From Dial Plan File

    Mediant 800B GW & E-SBC 37.1.3.4 Obtaining IP Destination from Dial Plan File You can use a Dial Plan index listed in a loaded Dial Plan file for determining the IP destination of Tel-to-IP /IP-to-IP calls and SBC calls. This enables the mapping of called numbers to IP addresses (in dotted-decimal notation) or FQDNs (up to 15 characters).

  • Page 545: User Information File

    Mapping (Manipulating) PBX Extension Numbers with Global Phone Numbers: maps PBX extension number, connected to the device, with any "global" phone number (alphanumerical) for the IP side. In this context, the "global" phone number Version 6.6 Mediant 800B GW & E-SBC...
  • Page 546 Mediant 800B GW & E-SBC serves as a routing identifier for calls in the "IP world" and the PBX extension uses this mapping to emulate the behavior of an IP phone. This feature is especially useful in scenarios where unique or non-consecutive number translation per PBX is needed.

  • Page 547: User Information File For Sbc User Database

    The User Info file is a text-based file that you can create using any text-based program such as Notepad. To add SBC users to this file, use the following syntax: [ SBC ] FORMAT LocalUser,UserName,Password,IPGroupID Version 6.6 Mediant 800B GW & E-SBC...

  • Page 548: Enabling The User Info Table

    Mediant 800B GW & E-SBC john,john_user,john_pass,2 sue,sue_user,sue_pass,1 where:  LocalUser is the user and is used as the Request-URI user part for the AOR in the database  UserName is the user's authentication username  Password is the user's authentication password ...

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

    Web interface - see 'Installing Software License Key using Web Interface' on page  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non-volatile flash memory and overwrites the previously installed Software License Key.
  • Page 551 Open the Software License Key file and check that the "S/N" line appears. If it does not appear, contact AudioCodes. Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]".

  • Page 552: Software Upgrade Wizard

    (see 'Basic Maintenance' on page 527). Notes:  You can get the latest software files from AudioCodes Web site at http://www.audiocodes.com/downloads.  Before upgrading the device, it is recommended that you save a copy of the device's configuration settings (i.e., ini file) to your computer.
  • Page 553 Device reset may take a few minutes depending on cmp file version (this may even take up to 10 minutes). Click the Next button; the wizard page for loading an ini file appears. You can now perform one of the following: Version 6.6 Mediant 800B GW & E-SBC...
  • Page 554 Mediant 800B GW & E-SBC  Load a new ini file: Click Browse, navigate to the ini file, and then click Send File; the ini file is loaded to the device and you're notified as to a successful loading. ...

  • Page 555: Backing Up And Loading Configuration File

    Click the Load INI File button, and then at the prompt, click OK; the device uploads the ini file and then resets (from the cmp version stored on the flash memory). Once complete, the Web Login screen appears, requesting you to enter your user name and password. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 556 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 557: Automatic Update

    "master" configuration file with common settings from an HTTP server. This "master" file applies common configuration and instructs each device to download a specific configuration file based on the device's MAC address from an HTTP server. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 558 Mediant 800B GW & E-SBC Warning: Do not use the Web interface to configure the device when the Automatic Update feature is implemented. If you do and save (burn) the new settings to the device's flash memory, the IniFileURL parameter is automatically set to 0 and Automatic Updates is consequently disabled.
  • Page 559  By default, parameters that are not included in the downloaded configuration file are set to default. To retain the current settings of these parameters, set the SetDefaultOnINIFileProcess parameter to 0. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 560: Obtaining Networking Parameters Using Dhcp

    Mediant 800B GW & E-SBC 38.2 Obtaining Networking Parameters using DHCP You can configure the device to obtain an IP address from a DHCP server during bootup.  To enable DHCP for obtaining an IP address: Open the Application Settings page (Configuration tab > System menu >...

  • Page 561: Configuration Using Dhcp Option 67

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

  • Page 562: Http-Based Automatic Updates

    Mediant 800B GW & E-SBC 38.3.4 HTTP-based Automatic Updates An HTTP/S server can be placed in the customer's network where configuration and software updates are available for download. This does not require additional servers at the customer premises and is NAT-safe.

  • Page 563: Configuration Using Audiocodes Ems

    User's Manual 38.3.6 Configuration using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections. As soon as a registered device contacts the EMS server through SNMP, the EMS server handles all required configuration automatically, upgrading software as needed.

  • Page 564: Remotely Triggering Auto Update Using Sip Notify

    Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP Definitions > Advanced Parameters). Under the Misc Parameters group, set the 'SIP Remote Reset' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. User's Manual Document #: LTRT-10274...

  • Page 565: Restoring Factory Defaults

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

  • Page 566: Restoring Defaults Using Hardware Reset Button

    Mediant 800B GW & E-SBC 39.2 Restoring Defaults using Hardware Reset Button The device's hardware reset pinhole button can be used to reset the device to default settings.  To restore default settings using the hardware reset pinhole button: ...

  • Page 567: Usb Storage Capabilities

    Saving current configuration to the USB, using the following CLI command: # copy voice-configuration to usb://<the .ini configuration file name> Note: Only a single USB storage (formatted to FAT/FAT32) operation is supported at any given time. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 568 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 569: Status, Performance Monitoring And Reporting

    Part XI Status, Performance Monitoring and Reporting...

  • Page 571: System Status

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

  • Page 572: Viewing Ethernet Port Information

    Mediant 800B GW & E-SBC 41.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information on the Ethernet port group connections. This includes information such as activity status, duplex mode, and speed. Note: The Ethernet Port Information page also be accessed from the Home page (see 'Viewing the Home Page' on page 53).

  • Page 573: Carrier-Grade Alarms

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

  • Page 574: Viewing Alarm History

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

  • Page 575: Performance Monitoring

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

  • Page 576: Viewing Trunk Utilization

    Mediant 800B GW & E-SBC 43.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 577: Viewing Quality Of Experience

    Dialog Failed Attempts: displays the failed call attempts. This includes the number of calls and subscribes which were successfully and abnormally terminated.  Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 578 Mediant 800B GW & E-SBC  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure ‎ 4 3-3: Quality Of Experience Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view QoE for an SRD or IP Group.

  • Page 579: Viewing Average Call Duration

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

  • Page 581: Voip Status

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

  • Page 582: Viewing Analog Port Information

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

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

     Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure ‎ 4 4-4: NFAS Group & D-Channel Status Page Version 6.6 Mediant 800B GW & E-SBC...

  • Page 584: Viewing Active Ip Interfaces

    Mediant 800B GW & E-SBC 44.4 Viewing Active IP Interfaces The IP Interface Status page displays the device's active IP interfaces that are listed in the Multiple Interface Table page (see 'Configuring IP Network Interfaces' on page 104).  To view the active IP network interfaces: ...
  • Page 585 Indicates the number of calls that failed as a result of a busy line. It is Terminated due to a incremented as a result of the following release reason: Busy Line GWAPP_USER_BUSY (17) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 586 Mediant 800B GW & E-SBC Counter Description Number of Calls Indicates the number of calls that weren't answered. It's incremented as Terminated due to No a result of one of the following release reasons: Answer  GWAPP_NO_USER_RESPONDING (18)  GWAPP_NO_ANSWER_FROM_USER_ALERTED (19) ...

  • Page 587: Viewing Registered Users

    FXO / BRI), and SIP Accounts are registered to a SIP Registrar/Proxy server.  To view the registration status:  Open the Registration Status page (Status & Diagnostics tab > VoIP Status menu > Registration Status). Version 6.6 Mediant 800B GW & E-SBC...

  • Page 588: Viewing Call Routing Status

    Mediant 800B GW & E-SBC  Registered Per Gateway:  "YES" = Registration is per device  "NO"= Registration is not per device  Ports Registration Status:  "REGISTERED" = channel is registered  "NOT REGISTERED" = channel not registered ...

  • Page 589: Viewing Ip Connectivity

    (AltRoutingTel2IPMode) to Enable or Status Only (see 'Configuring General Routing Parameters' on page 323). Open the IP Connectivity page (Status & Diagnostics tab > VoIP Status menu > IP Connectivity). Figure ‎ 4 4-10: IP Connectivity Page Version 6.6 Mediant 800B GW & E-SBC...
  • Page 590 Mediant 800B GW & E-SBC Table ‎ 4 4-6: IP Connectivity Parameters Column Name Description IP Address The IP address can be one of the following:  IP address defined as the destination IP address in the Outbound IP Routing Table.

  • Page 591: Reporting Information To External Party

    Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Silence Suppression State Jitter Buffer Jitter Buffer Adaptive Jitter Buffer Rate Version 6.6 Mediant 800B GW & E-SBC...
  • Page 592 Mediant 800B GW & E-SBC Group Metric Name Jitter Buffer Nominal Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Gap Loss Burst Loss Density Burst Duration Gap Loss Density Gap Duration...
  • Page 593 'RTCP XR Collection Server Transport Type' (RTCPXRESCTransportType) - determines the transport layer for outgoing SIP dialogs initiated by the device to the RTCP XR Collection Server. Click Submit. Reset the device for the settings to take effect. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 594: Generating Call Detail Records

    Mediant 800B GW & E-SBC 45.2 Generating Call Detail Records The Call Detail Record (CDR) contains vital statistic information on calls made from the device. The device can be configured to generate and report CDRs for various stages of the call, including SIP messages and/or media. You can configure when CDRs for a call are generated, for example, only at the end of the call or only at the start and end of the call.

  • Page 595: Cdr Field Description

    Transport type:    SrcURI Source URI SrcURIBeforeMap Source URI before manipulation DstURI Destination URI DstURIBeforeMap Destination URI before manipulation Durat Call duration TrmSd Termination side (local or remote) TrmReason Termination reason Version 6.6 Mediant 800B GW & E-SBC...
  • Page 596 Mediant 800B GW & E-SBC CDR Field Name Description TrmReasonCategory Termination reason category:  Calls with duration 0 (i.e., not connected):  NO_ANSWER - GWAPP_NORMAL_CALL_CLEAR, GWAPP_NO_USER_RESPONDING, GWAPP_NO_ANSWER_FROM_USER_ALERTED  BUSY - GWAPP_USER_BUSY  NO_RESOURCES - GWAPP_RESOUUCE_UNAVAILABLE_UNSPECIFIED, RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LE RESOURCE_BECAUSE_NO_TRANSCODING_RESOURCES _LEFT, RELEASE_BECAUSE_GW_LOCKED ...

  • Page 597: Cdr Fields For Sbc Media

    |SIPInterfaceId |ProxySetId |IpProfileId (name) |MediaRealmId (name) |DirectMedia |SIPTrmReason [S=3] |CALL_END |SBC |170369730753201211288@10.132.10.245 |0 |RMT |10.132.10.245 |5060 |10.132.10.250 |5070 |UDP |103@audiocodes.com |103@audiocodes.com |101@10.132.10.250 |101@10.132.10.250 |0 |RMT |GWAPP_NORMAL_CALL_CLEAR |NO_ANSWER |06:13:54.950 UTC Thu Mar 02 2012 | |06:14:01.175 UTC Thu Mar 02 2012 |-1 | | |40 |2 () |0 (5070SRD) |2 |3 |0 () |0 (lanmedia) |no |CANCEL 45.2.2.2 CDR Fields for SBC Media...

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

    Mediant 800B GW & E-SBC CDR Field Name Description OutPackets Number of sent packets LocalPackLoss Local packet loss RemotePackLoss Remote packet loss RTPdelay RTP delay RTPjitter RTP jitter TxRTPssrc Tx RTP SSRC RxRTPssrc Local RTP SSRC LocalRFactor Local conversation quality...
  • Page 599 Remote RTP port TrmSd Initiator of call release (IP, Tel, or Unknown) TrmReason SIP call termination reason (see 'Release Reasons in CDR' on page 602) Fax transaction during call InPackets Number of incoming packets Version 6.6 Mediant 800B GW & E-SBC...
  • Page 600 Mediant 800B GW & E-SBC Field Name Description OutPackets Number of outgoing packets PackLoss Local packet loss RemotePackLoss Number of outgoing lost packets SIPCalld Unique SIP call ID SetupTime Call setup time ConnectTime Call connect time ReleaseTime Call release time...
  • Page 601 Remote MOS for conversation quality SigSourcePort SIP source port SigDestPort SIP destination port MediaType Media type - audio, video, or text SIPTrmReason SIP call termination reason (BYE, CANCEL, or SIP error codes, e.g., 404) Version 6.6 Mediant 800B GW & E-SBC...

  • Page 602: Release Reasons In Cdr

    Mediant 800B GW & E-SBC Field Name Description SipTermDesc Description of SIP termination reason:  SIP Reason header, if exists, for example: SIP ;cause=200 ;text="Call completed elsewhere".  If no SIP Reason header exists, the description is taken from the reason text, if exists, of the SIP response code, for example: "417...
  • Page 603  "GWAPP_ACCESS_INFORMATION_DISCARDED"  "GWAPP_REQUESTED_CIRCUIT_NOT_AVAILABLE"  "GWAPP_RESOURCE_UNAVAILABLE_UNSPECIFIED"  "GWAPP_PERM_FR_MODE_CONN_OUT_OF_S"  "GWAPP_PERM_FR_MODE_CONN_OPERATIONAL"  "GWAPP_PRECEDENCE_CALL_BLOCKED"  "RELEASE_BECAUSE_PREEMPTION_ANALOG_CIRCUIT_RESERVED_FOR_ REUSE"  "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED"  "GWAPP_BC_NOT_AUTHORIZED"  "GWAPP_BC_NOT_PRESENTLY_AVAILABLE"  "GWAPP_SERVICE_NOT_AVAILABLE"  "GWAPP_CUG_OUT_CALLS_BARRED"  "GWAPP_CUG_INC_CALLS_BARRED"  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS" Version 6.6 Mediant 800B GW & E-SBC...

  • Page 604: Supported Radius Attributes

    Mediant 800B GW & E-SBC  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST"  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED"  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING" ...
  • Page 605 (Gateway / IP-to-IP application) or Destination URI (SBC application) calling- Calling Party Number String 5135672127 Start Acc station-id (ANI) (Gateway / IP- Stop Acc to-IP application) or Source URI (SBC application) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 606 Mediant 800B GW & E-SBC Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. acct-status- Account Request Numeric 1: start, 2: stop Start Acc type Type (start or stop) Stop Acc Note: ‘start’ isn’t supported on the Calling Card application.
  • Page 607 (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 Version 6.6 Mediant 800B GW & E-SBC...

  • Page 608: Querying Device Channel Resources Using Sip Options

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

  • Page 609: Diagnostics

    Part XII Diagnostics...

  • Page 611: Syslog And Debug Recordings

    For example, in the below Syslog message generation, messages 238 through 300 were not received. In other words, three Syslog messages were lost (the sequential numbers are indicated below in bold font): Version 6.6 Mediant 800B GW & E-SBC...

  • Page 612: Event Representation In Syslog Messages

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

  • Page 614: Identifying Audiocodes Syslog Messages Using Facility Levels

    Mediant 800B GW & E-SBC 46.1.2 Identifying AudioCodes Syslog Messages using Facility Levels The device’s Syslog messages can easily be identified and distinguished from Syslog messages from other equipment, by setting its Facility level. The Facility levels of the device's Syslog messages are numerically coded with decimal values. Facility level may use any of the "local use"...

  • Page 615: Configuring Syslog Settings

    Figure ‎ 4 6-1: Syslog Settings Page Enable the Syslog feature by setting the 'Enable Syslog' to Enable. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port' parameters. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 616: Configuring Debug Recording

    Mediant 800B GW & E-SBC Configure the debug level using the 'Debug Level' parameter. Under the 'Activity Types to Report ...' group, select the activities to report. Click Submit to apply your changes. 46.3 Configuring Debug Recording The device enables you to activate debug recording and send debug recording packets to a defined capturing server.
  • Page 617  [8] IP Group = Filters according to a specified IP Group ID listed in the IP Group table.  [9] SRD = Filters according to a specified SRD ID listed in the Version 6.6 Mediant 800B GW & E-SBC...

  • Page 618: Filtering Ip Network Traces

    Mediant 800B GW & E-SBC Parameter Description SRD table.  [10] Classification = Filters according to a specified Classification rule listed in the Classification table (applicable only to the SBC and application).  [11] IP-to-IP Routing = Filters according to a specified SBC IP- to-IP routing rule listed in the IP-to-IP Routing table (applicable only to the SBC application).

  • Page 619: Viewing Syslog Messages

    You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 620: Collecting Debug Recording Messages

    Close the Message Log page by accessing any another page in the Web interface. 46.6 Collecting Debug Recording Messages To collect debug recording packets, the open source program Wireshark is used. AudioCodes proprietary plug-in files for Wireshark, which are shipped in your software kit, are also required. Notes: ...
  • Page 621 To install Wireshark and the plug-ins for debug recording: Install Wireshark on your computer. The Wireshark program can be downloaded from http://www.wireshark.org. Copy the supplied AudioCodes plug-in files to the directory in which you installed Wireshark, as follows: Copy this file To this folder ...\dtds\cdr.dtd...
  • Page 622 Calling party number: '201' Called party number: '102' Sending complete For CAS trace messages, the additional header "CAS Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below: AUDIOCODES DEBUG RECORDING CAS Trace Timer: 1145504439...

  • Page 623: Self-Testing

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

  • Page 625: Analog Line Testing

    Line polarity (0 = Positive; 1 = Negative)  Message Waiting Indication (0 = Off; 1 = On) Note: Use the Analog Line testing mechanism only for monitoring and never when there are calls in progress. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 626 Mediant 800B GW & E-SBC Reader's Notes User's Manual Document #: LTRT-10274...

  • Page 627: Testing Sip Signaling Calls

    By default, you can configure up to five test calls. This maximum can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative.  The Test Call Endpoint table can also be configured using the table ini file parameter Test_Call (see 'SIP Test Call Parameters' on page 659) or CLI command, configure system >...
  • Page 628 Mediant 800B GW & E-SBC Configure the test endpoint parameters as desired. See the table below for a description of these parameters. Click Submit to apply your settings. Test Call Table Parameters Parameter Description General Tab Endpoint URI Defines the endpoint's URI. This can be defined as a user or user@host.
  • Page 629 Note: This parameter is applicable only if 'Call Party' is set to Caller. Calls per Second Defines the number of calls per second. [Test_Call_CallsPer Note: This parameter is applicable only if 'Call Party' is set to Caller. Second] CLI: calls-per- second Version 6.6 Mediant 800B GW & E-SBC...

  • Page 630: Starting, Stopping And Restarting Test Calls

    Mediant 800B GW & E-SBC Parameter Description Test Mode Defines the test session mode. [Test_Call_TestMo  [0] Once = (Default) The test runs until the lowest value between the following is reached: CLI: test-mode  Maximum channels is reached for the test session, configured by 'Maximum Channels for Session'.

  • Page 631: Viewing Test Call Statistics

    Call Attempts: The number of calls that were attempted.  Total Established Calls: The total number of calls that were successfully established.  Total Failed Attempts: The total number of calls that failed to be established. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 632: Configuring Dtmf Tones For Test Calls

    Mediant 800B GW & E-SBC  Remote Disconnections Count: Number of calls that were disconnected by the remote side.  Average CPS: The average calls per second.  Test Status: Displays the status (brief description) as displayed in the 'Test Status' field (see 'Starting, Stopping and Restarting Test Calls' on page 630).

  • Page 633: Configuring Basic Test Call

    For a full description of this parameter, see 'SIP Test Call Parameters' on page 659.  This call test is done on all SIP interfaces.  This call test is applicable only to the Gateway/IP-to-IP application. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 634: Configuring Sbc Test Call With External Proxy

    Mediant 800B GW & E-SBC 49.4 Configuring SBC Test Call with External Proxy The SBC Test Call feature tests incoming SBC SIP call flow between a simulated test endpoint on the device and a remote SIP endpoint, when registration and routing is done through an external proxy/registrar server such as a hosted IP PBX in the WAN.
  • Page 635 This test call is initiated only upon receipt of incoming calls and with the configured prefix.  This call test is done on all SIP interfaces.  This test call is applicable only to the SBC application. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 636: Test Call Configuration Examples

    Mediant 800B GW & E-SBC 49.5 Test Call Configuration Examples Below are a few examples of test call configurations.  Single Test Call Scenario: This example describes the configuration of a simple test call scenario that includes a single test call between a simulated test endpoint on the device and a remote endpoint.
  • Page 637 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 638 Mediant 800B GW & E-SBC  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and password) process of a simulated test endpoint on the device with an external proxy/registrar server. This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another.

  • Page 639: Appendix

    Part XIII Appendix...

  • Page 641: Dialing Plan Notation For Routing And Manipulation

    03(abc): for any number that starts with 03 and ends with abc.  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 642 Mediant 800B GW & E-SBC Notation Description Notes:  The value n must be less than the value m.  Only numerical ranges are supported (not alphabetical letters).  For suffix ranges, the starting (n) and ending (m) numbers in the range must have the same number of digits.

  • Page 643: Configuration Parameters Reference

    EtherGroupTable_Mode, EtherGroupTable_Member1, EtherGroupTable_Member2; [\EtherGroupTable] Notes:  For this parameter to take effect, a device reset is required.  For a description of this parameter, see Configuring Tx/Rx for Ethernet Port-Pair Groups on page 103. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 644: Multiple Voip Network Interfaces And Vlan Parameters

    Mediant 800B GW & E-SBC 51.1.2 Multiple VoIP Network Interfaces and VLAN Parameters The IP network interfaces and VLAN parameters are described in the table below. Table ‎ 5 1-2: IP Network Interfaces and VLAN Parameters Parameter Description Multiple Interface Table Web: Multiple Interface This table parameter configures the Multiple Interface table.

  • Page 645: Quality Of Service Parameters

    For a description of this table, see Configuring Quality of Service on page Layer-3 Class of Service (TOS/DiffServ) Parameters Web: Media Premium QoS Defines the DiffServ value for Premium Media CoS EMS: Premium Service Class Media Diff content. Serv Version 6.6 Mediant 800B GW & E-SBC...

  • Page 646: Nat And Stun Parameters

    Mediant 800B GW & E-SBC Parameter Description [PremiumServiceClassMediaDiffServ] The valid range is 0 to 63. The default is 46. Note: The value for the Premium Control DiffServ is determined by the following (according to priority):  IPDiffServ value in the selected IP Profile (IPProfile parameter).

  • Page 647: Nfs Parameters

    Dns2Ip_FirstIpAddress, Dns2Ip_SecondIpAddress, Dns2Ip_ThirdIpAddress, Dns2Ip_FourthIpAddress; [\Dns2Ip] For example: Dns2Ip 0 = DnsName, 1.1.1.1, 2.2.2.2, 3.3.3.3, 4.4.4.4; Note: For a detailed description of this table parameter, see 'Configuring the Internal DNS Table' on page 119. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 648: Dhcp Parameters

    Mediant 800B GW & E-SBC Parameter Description Internal SRV Table Web: Internal SRV Table This table parameter defines the internal SRV table for resolving host EMS: DNS Information names into DNS A-Records. Three different A-Records can be assigned [SRV2IP] to a host name. Each A-Record contains the host name, priority, weight, and port.

  • Page 649: Ntp And Daylight Saving Time Parameters

    Day of month - mm:day/wk:hh:mm, where:  mm denotes month (e.g., 04)  day denotes day of week (e.g., FRI)  wk denotes week of the month (e.g., 03)  hh denotes hour (e.g., 23) Version 6.6 Mediant 800B GW & E-SBC...

  • Page 650: Management Parameters

    Mediant 800B GW & E-SBC Parameter Description  mm denotes minutes (e.g., 10) For example, "04:FRI/03:23:00" denotes Friday, the third week of April, at 11 P.M. The week field can be 1-5, where 5 denotes the last occurrence of the specified day in the specified month. For example, "04:FRI/05:23:00"...
  • Page 651 Enables Web login authentication using a third-party, smart card. ntication]  [0] = Disable (default)  [1] = Enable When enabled, the device retrieves the Web user’s login username from the smart card, which is automatically displayed (read-only) in Version 6.6 Mediant 800B GW & E-SBC...
  • Page 652 Mediant 800B GW & E-SBC Parameter Description the Web Login screen; the user is then required to provide only the login password. Typically, a TLS connection is established between the smart card and the device’s Web interface, and a RADIUS server is implemented to authenticate the password with the username.

  • Page 653: Telnet Parameters

    When set to zero, idle sessions are not disconnected. EMS: Server Idle Disconnect The valid range is any value. The default is 0. [TelnetServerIdleDisconnect] Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 654: Snmp Parameters

    Mediant 800B GW & E-SBC 51.2.4 SNMP Parameters The SNMP parameters are described in the table below. Table ‎ 5 1-13: SNMP Parameters Parameter Description Web: Enable SNMP Enables SNMP. [DisableSNMP]  [0] Enable = (Default) SNMP is enabled. ...
  • Page 655 Manager table (defined by the SNMPManagerTableIP parameter) and the last trap manager entry of snmpTargetAddrTable in the snmpTargetMIB. For example: 'mngr.corp.mycompany.com'. The valid range is a string of up to 99 characters. SNMP Community String Parameters Version 6.6 Mediant 800B GW & E-SBC...

  • Page 656: Serial Parameters

    Mediant 800B GW & E-SBC Parameter Description Community String Defines up to five read-only SNMP community strings (up to 19 [SNMPReadOnlyCommunityStr characters each). The default string is 'public'. ing_x] Community String Defines up to five read/write SNMP community strings (up to 19 [SNMPReadWriteCommunitySt characters each).

  • Page 657: Debugging And Diagnostics Parameters

    Syslog server.  [0] = (Default) Rapid and Enhanced self-test mode.  [1] = Detailed self-test mode (full test of DSPs, PCM, Switch, LAN, PHY and Flash). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 658 Mediant 800B GW & E-SBC Parameter Description  [2] = A quicker version of the Detailed self-test mode (full test of DSPs, PCM, Switch, LAN, PHY, but partial test of Flash). Note: For this parameter to take effect, a device reset is required.

  • Page 659: Sip Test Call Parameters

    The valid value can be any string of up to 15 characters. By default, no number is defined. Note: This feature is applicable only to the SBC application. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 660: Syslog, Cdr And Debug Parameters

    Mediant 800B GW & E-SBC Parameter Description Test Call Table Web: Test Call Table Defines the local and remote endpoints to be tested. [Test_Call] [Test_Call] FORMAT Test_Call_Index = Test_Call_EndpointURI, Test_Call_CalledURI, Test_Call_RouteBy, Test_Call_IPGroupID, Test_Call_DestAddress, Test_Call_DestTransportType, Test_Call_SRD, Test_Call_ApplicationType, Test_Call_AutoRegister, Test_Call_UserName, Test_Call_Password, Test_Call_CallParty,...
  • Page 661 (if occurs), and at the end of the media. Note: To enable CDR generation as well as enable signaling-related CDRs, use the CDRReportLevel parameter. Web/EMS: Debug Level Defines the Syslog debug logging level. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 662 Mediant 800B GW & E-SBC Parameter Description  [GwDebugLevel] [0] 0 = (Default) Debug is disabled.  [1] 1 = Flow debugging is enabled.  [5] 5 = Flow, device interface, stack interface, session manager, and device interface expanded debugging are enabled.
  • Page 663 This table parameter defines logging filtering rules for Syslog [LoggingFilters] messages and debug recordings. The format of this parameter is as follows: [ LoggingFilters ] FORMAT LoggingFilters_Index = LoggingFilters_Type, LoggingFilters_Value, LoggingFilters_Syslog, LoggingFilters_CaptureType; [ \LoggingFilters ] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 664: Resource Allocation Indication Parameters

    Mediant 800B GW & E-SBC Parameter Description Note: For a detailed description of this table, see 'Filtering Syslog Messages and Debug Recordings' on page 616. 51.3.4 Resource Allocation Indication Parameters The Resource Allocation Indication (RAI) parameters are described in the table below.

  • Page 665: Security Parameters

    EMS: HTTPS Port Defines the local Secured HTTPS port of the device. This [HTTPSPort] parameter allows secure remote device Web management from the LAN. To enable secure Web management from the LAN, Version 6.6 Mediant 800B GW & E-SBC...
  • Page 666 Mediant 800B GW & E-SBC Parameter Description configure the desired port. The valid range is 1 to 65535 (other restrictions may apply within this range). The default port is 443. Note: For this parameter to take effect, a device reset is required.

  • Page 667: Srtp Parameters

    The range is 0 to 4. The default is 0 (i.e., new keys are generated [SRTPTxPacketMKISize] without MKI). Notes:  For the GW/IP-to-IP application, the device only initiates the MKI size.  You can also configure MKI size in an IP Profile. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 668 Mediant 800B GW & E-SBC Parameter Description  For the SBC application, the device can forward MKI size as is for SRTP-to-SRTP flows or override the MKI size during negotiation, using IP Profiles. This can be done on the inbound or outbound leg.
  • Page 669 SRTP. Notes:  This feature can also be configured for an IP Profile.  If this feature is disabled and the server resets the ROC upon a re-key generation, one-way voice may occur. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 670: Tls Parameters

    Mediant 800B GW & E-SBC 51.4.4 TLS Parameters The Transport Layer Security (TLS) parameters are described in the table below. Table ‎ 5 1-22: TLS Parameters Parameter Description Web/EMS: TLS Version Determines the supported versions of SSL/TLS (Secure Socket [TLSVersion] Layer/Transport Layer Security.
  • Page 671 SSH.  [512]  [768]  [1024] (default)  [2048] Web: TLS FIPS 140 Mode Enables FIPS 140-2 conformance mode for TLS.  [TLS_Fips140_Mode] [0] Disable (default)  [1] Enable Version 6.6 Mediant 800B GW & E-SBC...

  • Page 672: Ssh Parameters

    Mediant 800B GW & E-SBC 51.4.5 SSH Parameters Secure Shell (SSH) parameters are described in the table below. Table ‎ 5 1-23: SSH Parameters Parameter Description Web/EMS: Enable SSH Server Enables the device's embedded SSH server. [SSHServerEnable]  [0] Disable (default) ...

  • Page 673: Ocsp 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. IDS Policy Table Version 6.6 Mediant 800B GW & E-SBC...

  • Page 674: Radius Parameters

    Mediant 800B GW & E-SBC Parameter Description Web: 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 this table, see 'Configuring IDS Policies' on page 137.
  • Page 675 RADIUS server. This should be a cryptically strong password. Secret [SharedSecret] RADIUS Authentication Parameters Web: Default Access Level Defines the default access level for the device when the RADIUS [DefaultAccessLevel] (authentication) response doesn't include an access level Version 6.6 Mediant 800B GW & E-SBC...
  • Page 676 Mediant 800B GW & E-SBC Parameter Description attribute. The valid range is 0 to 255. The default is 200 (i.e., Security Administrator). Web: Device Behavior Upon Defines the device's response upon a RADIUS timeout. RADIUS Timeout  [0] Deny Access = Denies access.

  • Page 677: Sip Media Realm Parameters

    For a detailed description of this table, see 'Configuring Bandwidth Management per Media Realm' on page 175. Quality of Experience Parameters Web: Server IP Defines the IP address of AudioCodes Session Experience Manager CLI: server-ip (SEM) server to where the quality experience reports are sent. Version 6.6...
  • Page 678 Mediant 800B GW & E-SBC Parameter Description [QOEServerIP] Note: For this parameter to take effect, a device reset is required. Web: Port Defines the port of the SEM server. [QOEPort] The valid value range is 0 to 65534. The default is 5000.

  • Page 679: Control Network Parameters

    Port = Port number, where 1 denotes the Port 1 of the module For example: Authentication 1 = lee,1552,1,2; (user name "lee" with password 1552 for authenticating Port 2 of Module 1) Notes:  The indexing of this parameter starts at 0. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 680 Mediant 800B GW & E-SBC Parameter Description  For a description o this table, see Configuring Authentication on page 395. Account Table Web: Account Table This table parameter configures the Account table for EMS: SIP Endpoints > Account registering and/or authenticating (digest) Trunk Groups or IP [Account] Groups (e.g., an IP-PBX) to another Serving IP Group (e.g., an...
  • Page 681 Web: SIP ReRouting Mode Determines the routing mode after a call redirection (i.e., a 3xx EMS: SIP Re-Routing Mode SIP response is received) or transfer (i.e., a SIP REFER [SIPReroutingMode] request is received). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 682 Mediant 800B GW & E-SBC Parameter Description  [0] Standard = (Default) INVITE messages that are generated as a result of Transfer or Redirect are sent directly to the URI, according to the Refer-To header in the REFER message, or Contact header in the 3xx response.
  • Page 683 Proxy/Registrar server. The default is an empty string. Notes:  This parameter is applicable only to the Gateway / IP-to-IP application.  This parameter is applicable only if single device Version 6.6 Mediant 800B GW & E-SBC...
  • Page 684 Mediant 800B GW & E-SBC Parameter Description registration is used (i.e., the parameter AuthenticationMode is set to authentication per gateway).  Instead of configuring this parameter, the Authentication table can be used (see Authentication on page 395). Web/EMS: Password Defines the password for Basic/Digest authentication with a [Password] Proxy/Registrar server.
  • Page 685 Notes:  This parameter is applicable only to the Gateway / IP-to-IP application.  The device sends a REGISTER request for each channel or for the entire device (according to the AuthenticationMode parameter). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 686 Mediant 800B GW & E-SBC Parameter Description Web/EMS: Registrar Name Defines the Registrar domain name. If specified, the name is [RegistrarName] used as the Request-URI in REGISTER messages. If it isn't specified (default), the Registrar IP address, or Proxy name or IP address is used instead.
  • Page 687 The device terminates a call due to the receipt of a 408 (Request Timeout) response and the only provisional response the device has received for the call is the 100 Trying provisional response (indicative of a home proxy server failure). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 688 Mediant 800B GW & E-SBC Parameter Description Web: ReRegister On Connection Enables the device to perform SIP re-registration upon Failure TCP/TLS connection failure. EMS: Re Register On Connection  [0] Disable (default) Failure  [1] Enable [ReRegisterOnConnectionFailure] Web: Gateway Registration Name...
  • Page 689  [1] Enable When the device sends a REGISTER message, the Route header includes either the Proxy's FQDN, or IP address and port according to the configured Proxy Set, for example: Route: <sip:10.10.10.10;lr;transport=udp> Version 6.6 Mediant 800B GW & E-SBC...

  • Page 690: Network Application Parameters

    Mediant 800B GW & E-SBC Parameter Description Route: <sip: pcscf- gm.ims.rr.com;lr;transport=udp> EMS: Ping Pong Keep Alive Enables the use of the carriage-return and line-feed sequences [UsePingPongKeepAlive] (CRLF) Keep-Alive mechanism, according to RFC 5626 “Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)”...
  • Page 691 NAT IP addresses. This allows, for example, the separation of VoIP traffic between different ISTP’s, and topology hiding (of internal IP addresses to the “public” network). Each IP interface (configured in the Multiple Interface table - InterfaceTable parameter) can be associated Version 6.6 Mediant 800B GW & E-SBC...

  • Page 692: General Sip Parameters

    (if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Message Defines the maximum size (in Kbytes) for each SIP message that Length [KB] can be sent over the network.
  • Page 693 Below is an example of the X-RTP-Stat header in a SIP BYE message: BYE sip:302@10.33.4.125 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.126;branch=z9hG4bKac2127550866 Max-Forwards: 70 From: <sip:401@10.33.4.126;user=phone>;tag=1c21135533 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; Version 6.6 Mediant 800B GW & E-SBC...
  • Page 694 Mediant 800B GW & E-SBC Parameter Description Supported: em,timer,replaces,path,resource- priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,P RACK,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.6.2A.008.006 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0 Web/EMS: PRACK Mode Determines the PRACK (Provisional Acknowledgment) mechanism [PrackMode] mode for SIP 1xx reliable responses.  [0] Disable ...
  • Page 695 Defines the response of the device upon receipt of a SIP 183 response.  [0] Progress = (Default) Digital: The device sends a Progress message. Analog: A 183 response (without SDP) does not Version 6.6 Mediant 800B GW & E-SBC...
  • Page 696 Mediant 800B GW & E-SBC Parameter Description cause the device to play a ringback tone.  [1] Alert = Digital: The device sends an Alerting message (upon receipt of a 183 response) instead of an ISDN Progress message. Analog: 183 response is handled by the device as if a 180 Ringing response is received, and the device plays a ringback tone.
  • Page 697 Echo Canceller = On  Silence Compression = Off  Echo Canceller Non-Linear Processor Mode = Off  Dynamic Jitter Buffer Minimum Delay = 40  Dynamic Jitter Buffer Optimization Factor = 13 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 698 Mediant 800B GW & E-SBC Parameter Description  If the device initiates a fax session using G.711 (option 2 and possibly 3), a 'gpmd' attribute is added to the SDP in the following format:  For A-law: 'a=gpmd:8 vbd=yes;ecan=on' For -law: 'a=gpmd:0 vbd=yes;ecan=on' ...
  • Page 699 Note: For the SAS application, this feature is configured using the SASConnectionReuse parameter. Web: Fake TCP alias Enables the re-use of the same TCP/TLS connection for sessions [FakeTCPalias] with the same user, even if the "alias" parameter is not present in Version 6.6 Mediant 800B GW & E-SBC...
  • Page 700 Mediant 800B GW & E-SBC Parameter Description the SIP Via header of the first INVITE.  [0] Disable = (Default) TCP/TLS connection reuse is done only if the "alias" parameter is present in the Via header of the first INVITE.
  • Page 701 Determines whether the SIP 'tgrp' parameter is used. This SIP EMS: Use SIP Tgrp parameter specifies the Trunk Group to which the call belongs [UseSIPTgrp] (according to RFC 4904). For example, the SIP message below Version 6.6 Mediant 800B GW & E-SBC...
  • Page 702 Mediant 800B GW & E-SBC Parameter Description indicates that the call belongs to Trunk Group ID 1: INVITE sip::+16305550100;tgrp=1;trunk- context=example.com@10.1.0.3;user=phone SIP/2.0  [0] Disable = (Default) The 'tgrp' parameter isn't used.  [1] Send Only = The Trunk Group number or name (configured in the Hunt Group Settings) is added to the 'tgrp' parameter value in the Contact header of outgoing SIP messages.
  • Page 703 Trunk Group ID 56: INVITE sip:123456@192.168.1.2;dtg=56;user=phone SIP/2.0 Note: If the Trunk Group is not found based on the 'dtg' parameter, the Inbound IP Routing Table is used instead for routing the call to Version 6.6 Mediant 800B GW & E-SBC...
  • Page 704 Mediant 800B GW & E-SBC Parameter Description the appropriate Trunk Group. Web/EMS: Enable GRUU Determines whether the Globally Routable User Agent URIs [EnableGRUU] (GRUU) mechanism is used, according to RFC 5627. This is used for obtaining a GRUU from a registrar and for communicating a GRUU to a peer within a dialog.
  • Page 705 When configured, the string [UserAgentDisplayInfo] <UserAgentDisplayInfo value>/software version' is used, for example: User-Agent: myproduct/v.6.40.010.006 If not configured, the default string, <AudioCodes product- name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 800B Gateway and SBC/v.6.40.010.006 The maximum string length is 50 characters.
  • Page 706 Mediant 800B GW & E-SBC Parameter Description [SIPSubject] not specified, the Subject header isn't included (default). The maximum length is up to 50 characters. [CoderPriorityNegotiation] Defines the priority for coder negotiation in the incoming SDP offer, between the device's or remote UA's coder list.
  • Page 707  "Pai2" = The calling number is obtained using the following logic: If a P-Preferred-Identity header is present, the number is obtained from it. If no P-Preferred-Identity header is present and two P- Version 6.6 Mediant 800B GW & E-SBC...
  • Page 708 Mediant 800B GW & E-SBC Parameter Description Asserted-Identity headers are present, the number is obtained from the second P-Asserted-Identity header. If only one P-Asserted-Identity header is present, the calling number is obtained from it. Notes:  The "From" and "Pai2" values are not case-sensitive.
  • Page 709 Determines whether the device sets the Contact header of outgoing INVITE requests to ‘anonymous’ for restricted calls. Restriction [EnableContactRestriction]  [0] Disable (default)  [1] Enable Determines whether the device's IP address is used as the URI Version 6.6 Mediant 800B GW & E-SBC...
  • Page 710 Mediant 800B GW & E-SBC Parameter Description [AnonymousMode] host part instead of "anonymous.invalid" in the INVITE's From header for Tel-to-IP calls.  [0] = (Default) If the device receives a call from the Tel with blocked caller ID, it sends an INVITE with From: “anonymous”<anonymous@anonymous.invalid>...
  • Page 711 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. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 712 Mediant 800B GW & E-SBC Parameter Description Note: This parameter can also be configured per IP Profile (using the IPProfile parameter) and Tel Profile (using the TelProfile parameter). [EnableRekeyAfter181] Enables the device to send a re-INVITE with a new (different) SRTP key (in the SDP) if a SIP 181 response is received ("call is...
  • Page 713 Number Manipulation tables to leave only the last 3 digits (for example) for sending to a PBX. EMS: Use SIP URI For Defines the URI format in the SIP Diversion header. Diversion Header  [0] = 'tel:' (default) [UseSIPURIForDiversionHead  [1] = 'sip:' Version 6.6 Mediant 800B GW & E-SBC...
  • Page 714 Mediant 800B GW & E-SBC Parameter Description [TimeoutBetween100And18x] Defines the timeout (in msec) between receiving a 100 Trying response and a subsequent 18x response. If a 18x response is not received within this timeout period, the call is disconnected. The valid range is 0 to 180,000 (i.e., 3 minutes). The default is 32000 (i.e., 32 sec).
  • Page 715 The device notifies the softswitch (or Application server) of the unanswered collect call (on-hook) by sending a SIP INFO message. As a result, the softswitch disconnects the call (sends a Version 6.6 Mediant 800B GW & E-SBC...
  • Page 716 Mediant 800B GW & E-SBC Parameter Description BYE message to the device). If the call is a regular incoming call and the FXS user on-hooks the phone without intending to disconnect the call, the softswitch does not disconnect the call (during the regret time).
  • Page 717 This parameter is applicable only to FXO interfaces. Web/EMS: SIT Q850 Cause For Defines the Q.850 cause value specified in the SIP Reason header that is included in a 4xx response when SIT-IC (Operator Intercept Version 6.6 Mediant 800B GW & E-SBC...
  • Page 718 Mediant 800B GW & E-SBC Parameter Description [SITQ850CauseForIC] Special Information Tone) is detected from the PSTN for IP-to-Tel calls. The valid range is 0 to 127. The default is -1 (not configured). Note: When not configured (i.e., default), the SITQ850Cause parameter is used.
  • Page 719  [2] D-Channel = Takes D-Channel down or up (ISDN only).  [3] Alarm = Sends or clears PSTN AIS Alarm (ISDN and CAS).  [4] Block = Blocks trunk (CAS only). Notes: Version 6.6 Mediant 800B GW & E-SBC...
  • Page 720 Mediant 800B GW & E-SBC Parameter Description  This parameter is applicable only if the parameter EnableBusyOut is set to 1.  The default behavior (value 0) is as follows:  ISDN: Use Service messages on supporting variants and use Alarm on non-supporting variants.
  • Page 721 This table parameter configures SIP message policy rules for blocking [MessagePolicy] (blacklist) unwanted incoming SIP messages or allowing (whitelist) receipt of desired messages.The format of this parameter is as follows: [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Policy, MessagePolicy_MaxMessageLength, MessagePolicy_MaxHeaderLength, MessagePoliy_MaxBodyLength, Version 6.6 Mediant 800B GW & E-SBC...

  • Page 722: Coders And Profile Parameters

    Mediant 800B GW & E-SBC Parameter Description MessagePolicy_MaxNumHeaders, MessagePolicy_MaxNumBodies, MessagePolicy_SendRejection, MessagePolicy_MethodListType, MessagePolicy_MethodList, MessagePolicy_BodyListType, MessagePolicy_BodyList; [/MessagePolicy] Note: For a detailed description of this table, see 'Configuring SIP Message Policy Rules'. 51.9 Coders and Profile Parameters The profile parameters are described in the table below.
  • Page 723 Number table (TrunkGroup parameter). Therefore, Tel Profiles allow you to [TelProfile] apply the same settings of a group of parameters to multiple channels, or apply specific settings to different channels. The format of this parameter is as follows: Version 6.6 Mediant 800B GW & E-SBC...
  • Page 724 Mediant 800B GW & E-SBC Parameter Description [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP, TelProfile_TimeForReorderTone, TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode;...
  • Page 725 TelProfile_DialPlanIndex Dial Plan DialPlanIndex Index TelProfile_Enable911PSAP Enable 911 Enable911PSAP PSAP TelProfile_SwapTelToIpPhoneNumbers Swap Tel SwapTEl2IPCalled&CallingNumbers To IP Phone Numbers TelProfile_EnableAGC Enable AGC EnableAGC TelProfile_ECNlpMode EC NLP ECNLPMode Mode TelProfile_DigitalCutThrough DigitalCutThrough TelProfile_EnableFXODoubleAnswer EnableFXODoubleAnswer TelProfile_CallPriorityMode CallPriorityMode Version 6.6 Mediant 800B GW & E-SBC...

  • Page 726: Channel Parameters

    Mediant 800B GW & E-SBC 51.10 Channel Parameters This subsection describes the device's channel parameters. 51.10.1 Voice Parameters The voice parameters are described in the table below. Table ‎ 5 1-32: Voice Parameters Parameter Description Web/EMS: Input Gain Defines the pulse-code modulation (PCM) input gain control (in [InputGain] decibels).
  • Page 727 The valid range is 0 to 60. The default is 10. Threshold] Web: Min Reference Delay Defines the acoustic echo suppressor minimum reference delay (in x10 msec 10-ms units). [AcousticEchoSuppMinRefD The valid range is 0 to 40. The default is 0. elayx10ms] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 728: Coder Parameters

    Mediant 800B GW & E-SBC Parameter Description Web: Max Reference Delay Defines the acoustic echo suppressor maximum reference delay (in x10 msec 10-ms units). [AcousticEchoSuppMaxRef The valid range is 0 to 40. The default is 40 (i.e., 40 x 10 = 400 ms).

  • Page 729: Dtmf Parameters

    The valid range is -31 to 0 dB. The default is -11 dB. [DTMFVolume] Note: This parameter can also be configured in a Tel Profile. Web: DTMF Generation Twist Defines the range (in decibels) between the high and low frequency Version 6.6 Mediant 800B GW & E-SBC...

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

    Mediant 800B GW & E-SBC Parameter Description EMS: DTMF Twist Control components in the DTMF signal. Positive decibel values cause the [DTMFGenerationTwist] higher frequency component to be stronger than the lower one. Negative values cause the opposite effect. For any parameter value, both components change so that their average is constant.
  • Page 731 Defines the RTP redundancy packet payload type according EMS: Redundancy Payload Type to RFC 2198. [RFC2198PayloadType] The range is 96 to 127. The default is 104. Note: This parameter is applicable only if the parameter RTPRedundancyDepth is set to 1. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 732 Mediant 800B GW & E-SBC Parameter Description Web: Packing Factor N/A. Controlled internally by the device according to the EMS: Packetization Factor selected coder. [RTPPackingFactor] Web/EMS: Basic RTP Packet Interval N/A. Controlled internally by the device according to the [BasicRTPPacketInterval] selected coder.
  • Page 733 [0] Active Always = (Default) RTCP is active even during inactive RTP periods, i.e., when the media is in 'recvonly' or 'inactive' mode.  [1] Inactive Only If RTP Inactive = No RTCP is sent when RTP is inactive. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 734 Mediant 800B GW & E-SBC Parameter Description RTP Control Protocol Extended Reports (RTCP XR) Parameters Web: Enable RTCP XR Enables voice quality monitoring and RTCP XR, according EMS: RTCP XR Enable to Internet-Draft draft-ietf-sipping-rtcp-summary-13. [VQMonEnable]  [0] Disable (default) ...

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

    [2] Enable Bypass (default) [V23ModemTransportType]  [3] Events Only = Transparent with Events Note: This parameter can also be configured in an IP Profile. Web: V.32 Modem Transport Determines the V.32 modem transport type. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 736 Mediant 800B GW & E-SBC Parameter Description  [0] Disable = Disable (Transparent) Type EMS: V32 Transport  [2] Enable Bypass (default) [V32ModemTransportType]  [3] Events Only = Transparent with Events Notes:  This parameter applies only to V.32 and V.32bis modems.
  • Page 737 The rate is negotiated between both sides (i.e., the device adapts to the capabilities of the remote side). Negotiation of the T.38 maximum supported fax data rate is provided in SIP’s SDP T38MaxBitRate parameter. The negotiated Version 6.6 Mediant 800B GW & E-SBC...
  • Page 738 Mediant 800B GW & E-SBC Parameter Description T38MaxBitRate is the minimum rate supported between the local and remote endpoints.  Fax relay rates greater than 14.4 kbps are applicable only to V.34 / T.38 fax relay. For non-T.38 V.34 supporting devices, configuration greater than 14.4 kbps is truncated to 14.4 kbps.
  • Page 739 Defines the port (with relation to RTP port) for sending and [T38UseRTPPort] receiving T.38 packets.  [0] = (Default) Use the RTP port +2 to send/receive T.38 packets.  [1] = Use the same port as the RTP port to send/receive T.38 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 740 Mediant 800B GW & E-SBC Parameter Description packets. Notes:  For this parameter to take effect, you must reset the device.  When the device is configured to use V.152 to negotiate audio and T.38 coders, the UDP port published in SDP for RTP and for T38 must be different.
  • Page 741 The value range is 8 to 32. The default is 8. [V1501SPRTTransportChannel 2MaxWindowSize] Web: SPRT Transport Ch.3 Max Defines the maximum payload size for V.150.1 SPRT Transport Payload Size Channel 3. [V1501SPRTTransportChannel The range is 140 to 256. The default is 140. 3MaxPayloadSize] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 742: Dtmf And Hook-Flash Parameters

    Mediant 800B GW & E-SBC 51.11.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below. Table ‎ 5 1-37: DTMF and Hook-Flash Parameters Parameter Description Hook-Flash Parameters Web/EMS: Hook-Flash Code For analog interfaces: Defines the digit pattern that when [HookFlashCode] received from the Tel side, indicates a Hook Flash event.
  • Page 743 Defines the supported receive DTMF negotiation method. EMS: Rx DTMF Option  [0] No = Don't declare RFC 2833 telephony-event [RxDTMFOption] parameter in SDP.  [3] Yes = (Default) Declare RFC 2833 telephony-event parameter in SDP. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 744 Mediant 800B GW & E-SBC Parameter Description The device is always receptive to RFC 2833 DTMF relay packets. Therefore, it is always correct to include the 'telephony-event' parameter as default in the SDP. However, some devices use the absence of the 'telephony-event' in the SDP to decide to send DTMF digits in-band using G.711...
  • Page 745 '1007766p100', the device places a call with 1007766 as the destination number, then after the call is answered it waits 1.5 seconds ('p') and plays the rest of the number (100) as DTMF digits. Additional examples: 1664wpp102, 66644ppp503, and 7774w100pp200. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 746 Mediant 800B GW & E-SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  For analog interfaces: The called number can include characters 'p' (1.5 seconds pause) and 'd' (detection of dial tone). If character 'd' is used, it must be the first 'digit' in the called number.

  • Page 747: Digit Collection And Dial Plan Parameters

    . (single dot): Repeat digits until next notation (e.g., T).  x: Any single digit.  T: Dial timeout (configured by the TimeBetweenDigits parameter).  S: Short timer (configured by the TimeBetweenDigits parameter; Version 6.6 Mediant 800B GW & E-SBC...
  • Page 748 Mediant 800B GW & E-SBC Parameter Description default is two seconds) that can be used when a specific rule is defined after a more general rule. For example, if the digit map is 99|998, then the digit collection is terminated after the first two 9 digits are received.

  • Page 749: Voice Mail Parameters

    Redirect number reason to the SIP 'cause' parameter in the Request-URI. Redirecting Reason >> SIP Response Code Unknown >> 404 User busy >> 486 No reply >> 408 Deflection >> 487/480 Unconditional >> 302 Others >> 302 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 750 Mediant 800B GW & E-SBC Parameter Description If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason. [WaitForBusyTime] Defines the time (in msec) that the device waits to detect busy and/or reorder tones.
  • Page 751 Defines the digit code used by the device to notify the PBX of EMS: MWI On Code messages waiting for a specific extension. This code is added as [MWIOnCode] prefix to the dialed number. The valid range is a 25-character string. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 752 Mediant 800B GW & E-SBC Parameter Description Web: MWI Suffix Pattern Defines the digit code used by the device as a suffix for 'MWI On EMS: MWI Suffix Code Digit Pattern' and 'MWI Off Digit Pattern'. This suffix is added to the [MWISuffixCode] generated DTMF string after the extension number.
  • Page 753 Defines a digit pattern that if received as Src (S) or Redirect (R) Pattern numbers is ignored and not added to that number. EMS: Digit To Ignore The valid range is a 25-character string. [DigitPatternDigitToIgnore] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 754: Supplementary Services Parameters

    Mediant 800B GW & E-SBC 51.11.5 Supplementary Services Parameters This subsection describes the device's supplementary telephony services parameters. 51.11.5.1 Caller ID Parameters The caller ID parameters are described in the table below. Table ‎ 5 1-40: Caller ID Parameters Parameter...
  • Page 755 ETSI MWI sub standard, use the ETSIVMWITypeOneStandard parameter.  If you define Caller ID Type as NTT [2], you need to define the NTT DID signaling form (FSK or DTMF) using the NTTDIDSignallingForm parameter. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 756 Mediant 800B GW & E-SBC Parameter Description Web: Enable FXS Caller ID Enables the interworking of Calling Party Category (cpc) code Category Digit For Brazil Telecom from SIP INVITE messages to FXS Caller ID first digit. [AddCPCPrefix2BrazilCallerID]  [0] Disable (default) ...
  • Page 757 200 OK with the P-Asserted-Identity header. In the opposite direction, if the ISDN device receives a 200 OK with P- Asserted-Identity header, it interworks it to the Connected party number and name in the Q.931 Connect message, including its Version 6.6 Mediant 800B GW & E-SBC...
  • Page 758 Mediant 800B GW & E-SBC Parameter Description privacy. Web/EMS: Use Destination As Enables the device to include the Called Party Number, from Connected Number outgoing Tel calls (after number manipulation), in the SIP P- [UseDestinationAsConnectedNu Asserted-Identity header. The device includes the SIP P-...

  • Page 759: Call Waiting Parameters

    CallWaitingPerPort 1 = 1,1,2; (call waiting enabled for Port 2 of Module 1) Notes:  This parameter is applicable only to FXS ports.  For a detailed description of this table, see Configuring Call Version 6.6 Mediant 800B GW & E-SBC...
  • Page 760 Mediant 800B GW & E-SBC Parameter Description Waiting on page 401. Web: Number of Call Waiting Defines the number of call waiting indications that are played to Indications the called telephone that is connected to the device for Call EMS: Call Waiting Number of Waiting.

  • Page 761: Call Forwarding Parameters

    Module 1 to an IP address upon On Busy: FwdInfo 1 = 1,2003@10.5.1.1,30,1,2; Notes:  The indexing of this parameter starts at 0.  For a detailed description of this table, see Configuring Call Forward on page 399. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 762: Message Waiting Indication Parameters

    Mediant 800B GW & E-SBC Parameter Description Call Forward Reminder Ring Parameters Notes:  These parameters are applicable only to FXS interfaces.  For a description of this feature, see Call Forward Reminder Ring on page 356. Web/EMS: Enable NRT...
  • Page 763 [ETSIVMWITypeOneStandard]  [0] = (Default) ETSI VMWI between rings  [1] = ETSI VMWI before ring DT_AS  [2] = ETSI VMWI before ring RP_AS  [3] = ETSI VMWI before ring LR_DT_AS Version 6.6 Mediant 800B GW & E-SBC...

  • Page 764: Call Hold Parameters

    Mediant 800B GW & E-SBC Parameter Description  [4] = ETSI VMWI not ring related DT_AS  [5] = ETSI VMWI not ring related RP_AS  [6] = ETSI VMWI not ring related LR_DT_AS Note: For this parameter to take effect, a device reset is required.

  • Page 765: Call Transfer Parameters

    [1] Enable = (Default) The device responds to a REFER message with the Referred-To header to initiate a call transfer. For analog interfaces: If the transfer service is enabled, the user can activate Transfer using hook-flash signaling. If this service is enabled, the Version 6.6 Mediant 800B GW & E-SBC...
  • Page 766 Mediant 800B GW & E-SBC Parameter Description remote party performs the call transfer. Notes:  To use call transfer, the devices at both ends must support this option.  To use call transfer, set the parameter EnableHold to 1. Web: Transfer Prefix...
  • Page 767 The device uses two DSP channels per transferred call. Thus, to use this feature, you also need to configure the maximum number of available DSP channels, using the MediaChannels parameter.  This parameter is applicable only to FXS interfaces. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 768: Three-Way Conferencing Parameters

    EMS: 3 Way Mode Conference feature is used. [3WayConferenceMode]  [0] AudioCodes Media Server = (Default) 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 769 When this feature is enabled and only one RTP port is available, only one call can be made by the FXS endpoint, as there is no free RTP port for a second call. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 770: Mlpp And Emergency Call Parameters

    Mediant 800B GW & E-SBC Parameter Description  When this feature is enabled and you are using the Call Forking feature, every forked call is sent with a different RTP port. As the device can fork a call to up to 10 destinations, the device requires at least 10 free RTP ports.
  • Page 771 (defined by the parameter EMS: Emergency Regret Timeout EmergencyNumbers). Until this time expires, an emergency call [EmergencyRegretTimeout] can only be disconnected by the remote party, typically, by a Public Safety Answering Point (PSAP). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 772 Mediant 800B GW & E-SBC Parameter Description The valid range is 1 to 30. The default is 10. Note: This parameter is applicable only to FXS interfaces. Multilevel Precedence and Preemption (MLPP) Parameters Web: MLPP Default Namespace Determines the namespace used for MLPP calls received from...
  • Page 773 Fac(1c): 91 a1 15 02 01 05 02 01 19 30 0d 0a 01 05 0a 01 01 04 05 01 00 12 3a bc  MLPPNetworkIdentifier set to 490: PlaceCall- MLPPNetworkID:9004 MlppServiceDomain:123abc, Version 6.6 Mediant 800B GW & E-SBC...
  • Page 774 Mediant 800B GW & E-SBC Parameter Description MlppPrecLevel:5 Fac(1c): 91 a1 15 02 01 0a 02 01 19 30 0d 0a 01 05 0a 01 01 04 05 90 04 12 3a bc Web: MLPP Default Service Defines the MLPP default service domain string. If the device...
  • Page 775 [MLPPFlashOverOverRTPDSC The valid range is -1 to 63. The default is -1. Note: If set to -1, the DiffServ value is taken from the global parameter PremiumServiceClassMediaDiffServ or as defined in Version 6.6 Mediant 800B GW & E-SBC...

  • Page 776: Call Cut-Through Parameters

    Mediant 800B GW & E-SBC Parameter Description IP Profiles per call. 51.11.5.9 Call Cut-Through Parameters The call cut-through parameters are described in the table below. Table ‎ 5 1-48: Call Cut-Through Parameters Parameter Description Web: Enable Calls Cut Enables FXS endpoints to receive incoming IP calls while the port is in off- Through hook state.

  • Page 777: Automatic Dialing Parameters

    The FXS interface generates a Wink signal upon detection of an off-hook state, instead of playing a dial tone. Example: (Wink) KP I(I) xxx-xxxx ST (Off Hook) Where:  I = one or two information digits  x = ANI Version 6.6 Mediant 800B GW & E-SBC...
  • Page 778 Mediant 800B GW & E-SBC Parameter Description Note: The FXO interface generates such MF digits when the Enable911PSAP parameter is set to 1.  [2] Double Wink = Double-wink signaling. The FXS interface generates the first wink upon detection of an off-hook state in the line.

  • Page 779: Isdn Bri Parameters

    Note: Upon receipt of an ISDN Facility message for call forward from the BRI phone, the device sends a SIP INVITE to the softswitch with a user-defined code in the SIP To header, representing the Version 6.6 Mediant 800B GW & E-SBC...

  • Page 780: Pstn Parameters

    Mediant 800B GW & E-SBC Parameter Description reason for the call forward. For more information on BRI call forwarding, see 'BRI Call Forwarding' on page 357. Web/EMS: Call Forward Defines the prefix code for activating Call Forward Unconditional sent Unconditional to the softswitch.
  • Page 781 [50] BRI EURO ISDN = Euro ISDN over BRI  [51] BRI N12 ISDN  [52] BRI DMS 100 ISDN  [53] BRI 5ESS 10 ISDN  [54] BRI QSIG = QSIG over BRI Version 6.6 Mediant 800B GW & E-SBC...
  • Page 782 Mediant 800B GW & E-SBC Parameter Description  [55] BRI VN6 = VN6 over BRI  [56] BRI NTT = BRI ISDN Japan (Nippon Telegraph)  [57] BRI IUA Notes:  All PRI trunks must be configured as the same line type (either E1 or T1).
  • Page 783 [1] Generated = Generate the clock according to the internal TDM bus. Notes:  The source of the internal TDM bus clock is determined by the parameter TDMBusClockSource.  This parameter is not applicable to BRI interfaces. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 784 Mediant 800B GW & E-SBC Parameter Description [ClockMaster_x] Same as the description for parameter ClockMaster, but for a specific Trunk ID (where x denotes the Trunk ID and 0 is the first Trunk). Note: This parameter is not applicable to BRI interfaces.

  • Page 785: Tdm Bus And Clock Timing Parameters

    [1] Internal = (Default) Generate clock from local source. [TDMBusClockSource]  [4] Network = Recover clock from PSTN line. Web/EMS: TDM Bus Local Defines the physical Trunk ID from which the device recovers Reference Version 6.6 Mediant 800B GW & E-SBC...
  • Page 786 Mediant 800B GW & E-SBC Parameter Description [TDMBusLocalReference] (receives) its clock synchronization. The range is 0 to the maximum number of Trunks. The default is Note: This parameter is applicable only if the parameter TDMBusClockSource is set to 4 and the parameter TDMBusPSTNAutoClockEnable is set to 0.

  • Page 787: Cas Parameters

    E&M Winkstart CAS (E_M_WinkTable.dat) protocol, and Trunks 2 and 3 to use the E&M Immediate Start CAS (E_M_ImmediateTable.dat) protocol: CASFileName_0 = 'E_M_WinkTable.dat' CASFileName_1 = 'E_M_ImmediateTable.dat' CASTableIndex_0 = 0 CASTableIndex_1 = 0 CASTableIndex_2 = 1 CASTableIndex_3 = 1 Version 6.6 Mediant 800B GW & E-SBC...
  • Page 788 Mediant 800B GW & E-SBC Parameter Description Notes:  You can define CAS tables per B-channel using the parameter CASChannelIndex.  The x in the ini file parameter denotes the trunk number, where 0 is Trunk 1. Web: Dial Plan Defines the CAS Dial Plan name per trunk.
  • Page 789 Web: Digit Signaling System Defines which Signaling System to use in both directions [CASStateMachineDigitSignalin (detection\generation). gSystem]  [0] DTMF = DTMF signaling.  [1] MF = (Default) MF signaling.  [-1] Default = Default value. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 790: Isdn Parameters

    Mediant 800B GW & E-SBC 51.11.6.4 ISDN Parameters The ISDN parameters are described in the table below. Table ‎ 5 1-55: ISDN Parameters Parameter Description Web: ISDN Termination Side Determines the ISDN termination side. EMS: Termination Side  [0] User side = (Default) ISDN User Termination [TerminationSide] Equipment (TE) side.
  • Page 791 [1] = PI 1 is added to a sent ISDN Setup message - call is not end-to-end ISDN.  [3] = PI 3 is added to a sent ISDN Setup message - calling equipment is not ISDN. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 792 Mediant 800B GW & E-SBC Parameter Description ISDN Flexible Behavior Parameters ISDN protocol is implemented in different switches/PBXs by different vendors. Several implementations may vary slightly from the specification. Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters can be used.
  • Page 793 [131072] STATUS INCOMPATIBLE STATE = Clears the call on receipt of Q.931 Status with incompatible state. Otherwise, no action is taken (default).  [262144] STATUS ERROR CAUSE = Clear call on receipt of Status according to cause value. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 794 Mediant 800B GW & E-SBC Parameter Description  [524288] ACCEPT A LAW =A-Law is also accepted in 5ESS.  [2097152] RESTART INDICATION = Upon receipt of a Restart message, acEV_PSTN_RESTART_CONFIRM is generated.  [4194304] FORCED RESTART = On data link (re)initialization, send RESTART if there is no call.
  • Page 795 Sending-Complete IE in the Setup message. This behavior is used when overlap dialing is not needed. When overlap dialing is needed, set this bit and the behavior is changed to suit the scenario, i.e., Version 6.6 Mediant 800B GW & E-SBC...
  • Page 796 Mediant 800B GW & E-SBC Parameter Description Sending-Complete IE is added when required in the Setup message for Enblock mode or in the last Digit with Overlap mode.  [16] USE MU LAW = The device sends G.711-m-Law in outgoing voice calls. When disabled, the device sends G.711-A-Law in outgoing voice calls.

  • Page 797: Isdn And Cas Interworking Parameters

    [2] Always Send Local Date and Time = The device always sends its local date and time (obtained from its internal clock) to PBXs in ISDN Q.931 Connect messages (Date / Time IE). It Version 6.6 Mediant 800B GW & E-SBC...
  • Page 798 Mediant 800B GW & E-SBC Parameter Description does this regardless of whether or not the incoming SIP 200 OK includes the Date header. If the SIP 200 OK includes the Date header, the device ignores its value. Notes:  This feature is applicable only to Tel-to-IP calls.
  • Page 799 [2] Using Body = Enable ISDN Tunneling from ISDN PRI to SIP using a dedicated message body. When ISDN Tunneling is enabled, the device sends all ISDN PRI messages using the correlated SIP messages. The ISDN Setup Version 6.6 Mediant 800B GW & E-SBC...
  • Page 800 Mediant 800B GW & E-SBC Parameter Description message is tunneled using SIP INVITE, all mid-call messages are tunneled using SIP INFO, and ISDN Disconnect/Release message is tunneled using SIP BYE messages. The raw data from the ISDN is inserted into a proprietary SIP header (X-ISDNTunnelingInfo) or a dedicated message body (application/isdn) in the SIP messages.
  • Page 801 If the incoming ISDN Setup message includes 'subaddress' values for the Called Number and/or the Calling Number, these values are mapped to the outgoing SIP INVITE message's ‘isub’ parameter in accordance with RFC 4715. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 802 Mediant 800B GW & E-SBC Parameter Description [IgnoreISDNSubaddress] Determines whether the device ignores the Subaddress from the incoming ISDN Called and Calling numbers when sending to IP.  [0] = (Default) If an incoming ISDN Q.931 Setup message contains a Called/Calling Number Subaddress, the Subaddress is interworked to the SIP 'isub' parameter according to RFC.
  • Page 803 (OLI) IE of an incoming ISDN Setup message is relayed to the From/P-Asserted-Identity headers using the 'cpc' parameter in the outgoing INVITE message, and vice versa. For example (calling party is a payphone): Version 6.6 Mediant 800B GW & E-SBC...
  • Page 804 Mediant 800B GW & E-SBC Parameter Description From:<sip:2000;cpc=payphone@10.8.23.70>;tag=1c18 06157451 Note: This feature is applicable only to the NI-2 PRI variant. [UserToUserHeaderFormat] Defines the interworking between the SIP INVITE's User-to-User header and the ISDN User-to-User (UU) IE data.  [0] = (Default) SIP header format: X-UserToUser.
  • Page 805 Defines the Alert Timeout (ISDN T301 timer) in seconds for [TrunkPSTNAlertTimeout_x] outgoing calls to PSTN, per trunk. This timer is used between the time that an ISDN Setup message is sent to the Tel side (IP-to-Tel Version 6.6 Mediant 800B GW & E-SBC...
  • Page 806 Mediant 800B GW & E-SBC Parameter Description call establishment) and a Connect message is received. If Alerting is received, the timer is restarted. The range is 1 to 600. The default is 180. Note: The x in the ini file parameter denotes the trunk number, where 0 is Trunk 1.
  • Page 807 IP Profiles (using the IPProfile parameter) and then assigning the required IP Profile ID in the Inbound IP Routing Table (PSTNPrefix).  This feature is similar to that of the EnableISDNTunnelingIP2Tel Version 6.6 Mediant 800B GW & E-SBC...
  • Page 808 Mediant 800B GW & E-SBC Parameter Description parameter. If both parameters are configured, the EnableISDNTunnelingIP2Tel parameter takes precedence. Web: Trunk Groups to Send IE Defines Trunk Group IDs (up to 50 characters) from where the EMS: List Of Trunk Groups To optional ISDN IE (defined by the parameter AddIEinSetup) is sent.
  • Page 809 The parameter SendISDNTransferOnConnect can be used to define if the TBCT/ECT transfer is performed after receipt of Alerting or Connect messages. For RLT, the transfer is always done after receipt of Connect (SendISDNTransferOnConnect is set to 1). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 810 Mediant 800B GW & E-SBC Parameter Description  This transfer can be performed between B-channels from different trunks or Trunk Groups, by using the parameter EnableTransferAcrossTrunkGroups.  The device initiates the ECT process after receiving a SIP REFER message only for trunks that are configured to User side.
  • Page 811 SIP NOTIFY message with a SIP 603 Decline response.  [0] = (Default) The device performs a hairpin TDM transfer upon ISDN call transfer.  [1] = Hairpin TDM transfer is disabled. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 812 Mediant 800B GW & E-SBC Parameter Description Web: Enable QSIG Transfer Determines whether the device interworks QSIG Facility messages Update with CallTranferComplete or CallTransferUpdate invoke application [EnableQSIGTransferUpdate] protocol data units (APDU) to SIP UPDATE messages with P- Asserted-Identity and optional Privacy headers. This feature is supported for IP-to-Tel and Tel-to-IP calls.

  • Page 813: Answer And Disconnect Supervision Parameters

    Tel side only when the call duration is greater than or equal to the minimum call duration. Notes:  This parameter is applicable to IP-to-Tel and Tel-to-IP calls.  This parameter is applicable only to ISDN and CAS protocols. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 814 Mediant 800B GW & E-SBC Parameter Description Web/EMS: Disconnect on Dial Tone Determines whether the device disconnects a call when a [DisconnectOnDialTone] dial tone is detected from the PBX.  [0] Disable = (Default) Call is not released.  [1] Enable = Call is released if a dial tone is detected on the device's FXO port.
  • Page 815 The range is 1 to 3600. The default is 0 (20 for E1 and 40 for T1). Web: Disconnect Call on Busy Tone Determines whether a call is disconnected upon detection Detection (ISDN) of a busy tone (for ISDN). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 816 Mediant 800B GW & E-SBC Parameter Description  [0] Disable = (Default) Do not disconnect call upon EMS: Isdn Disconnect On Busy Tone [ISDNDisconnectOnBusyTone] detection of busy tone.  [1] Enable = Disconnect call upon detection of busy tone. Notes: ...
  • Page 817 This parameter is applicable for FXS and FXO interfaces.  The FXO interface detection window is 100 msec below the parameter's value and 350 msec above the parameter's value. For example, if this parameter is set Version 6.6 Mediant 800B GW & E-SBC...

  • Page 818: Tone Parameters

    Mediant 800B GW & E-SBC Parameter Description to 400 msec, then the detection window is 300 to 750 msec.  For this parameter to take effect, a device reset is required. [CurrentDisconnectDefaultThreshold] Defines the line voltage threshold at which a current disconnect detection is considered.
  • Page 819 For analog interfaces: Defines the duration (in seconds) that the Duration [sec] device plays a busy or reorder tone before releasing the line. Typically, [TimeForReorderTone] after playing the busy or reorder tone for this duration, the device Version 6.6 Mediant 800B GW & E-SBC...
  • Page 820 Mediant 800B GW & E-SBC Parameter Description starts playing an offhook warning tone. For digital interfaces: Defines the duration (in seconds) that the CAS device plays a busy or reorder tone before releasing the line. The valid range is 0 to 254. The default is 0 seconds for analog interfaces and 10 seconds for digital interfaces.
  • Page 821 If a 180 response is received, but the 'early media' voice channel is not opened, the device configured for CAS plays a ringback tone to the PSTN. The device configured for ISDN operates according to the Version 6.6 Mediant 800B GW & E-SBC...
  • Page 822 Mediant 800B GW & E-SBC Parameter Description LocalISDNRBSource parameter: 1) If LocalISDNRBSource is set to 1, the device plays a ringback tone and sends an ISDN Alert with PI = 8 to the ISDN (unless the ProgressIndicator2ISDN_x parameter is configured differently).
  • Page 823 For digital modules: If configured to 1 ('Play') and EnableEarlyMedia is set to 1, the device plays a ringback tone according to the following:  For CAS interfaces: the device opens a voice channel, sends a Version 6.6 Mediant 800B GW & E-SBC...
  • Page 824 Mediant 800B GW & E-SBC Parameter Description 183+SDP response, and then plays a ringback tone to IP.  For ISDN interfaces: if a Progress or an Alerting message with PI (1 or 8) is received from the ISDN, the device opens a voice channel, sends a 183+SDP or 180+SDP response, but doesn't play a ringback tone to IP.

  • Page 825: Tone Detection Parameters

    FXO interfaces):  SITDetectorEnable = 1  UserDefinedToneDetectorEnable = 1  DisconnectOnBusyTone = 1 (applicable for busy, reorder, and SIT tones) Notes:  For this parameter to take effect, a device reset is required. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 826: Metering Tone Parameters

    Mediant 800B GW & E-SBC Parameter Description  The IP-to-ISDN call is disconnected on detection of a SIT tone only in call alert state. If the call is in connected state, the SIT does not disconnect the call. Detection of busy or reorder tones disconnect these calls also in call connected state.

  • Page 827: Telephone Keypad Sequence Parameters

    When the user dials these digits (e.g., #77), the incoming call from another phone is forwarded to the user's phone. The valid value is a string of up to 15 characters (0-9, #, and *). Version 6.6 Mediant 800B GW & E-SBC...
  • Page 828 Mediant 800B GW & E-SBC Parameter Description The default is undefined. Notes:  Call pick-up is configured only for FXS endpoints pertaining to the same Trunk Group.  This parameter is applicable only to FXS interfaces. Prefix for External Line [Prefix2ExtLine] Defines a string prefix (e.g., '9' dialed for an external line) that...
  • Page 829 Web: Forward Deactivate Defines the keypad sequence to deactivate any of the call EMS: Call Forward Deactivation forward options. After the sequence is pressed, a confirmation [KeyCFDeact] tone is heard. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 830 Mediant 800B GW & E-SBC Parameter Description Keypad Feature - Caller ID Restriction Parameters Web: Restricted Caller ID Activate Defines the keypad sequence to activate the restricted Caller ID EMS: CLIR option. After the sequence is pressed, a confirmation tone is [KeyCLIR] heard.

  • Page 831: General Fxo Parameters

     If caller ID is enabled and if the number of rings defined by the parameter RingsBeforeCallerID is greater than the number of rings defined by this parameter, the greater value is used. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 832 Mediant 800B GW & E-SBC Parameter Description Web/EMS: Dialing Mode Determines the dialing mode for IP-to-Tel (FXO) calls. [IsTwoStageDial]  [0] One Stage = One-stage dialing. In this mode, the device seizes one of the available lines (according to the...

  • Page 833: E&M Parameters

    The E&M parameters are described in the table below. Table ‎ 5 1-63: E&M Parameters Parameter Description Voice Type Defines the E&M voice interface type. [EnMVoiceType]  [0] Two Wire  [1] Four Wire (default) Version 6.6 Mediant 800B GW & E-SBC...

  • Page 834: Trunk Groups And Routing Parameters

    Mediant 800B GW & E-SBC Parameter Description Note: For this parameter to take effect, a device reset is required. System Type Defines the E&M signaling type. E&M signaling defines a trunk circuit [EnMSystemType] side and a signaling unit side for each connection similar to the data circuit-terminating equipment (DCE) and data terminal equipment (DTE) reference type.
  • Page 835  [7] Trunk Cyclic Ascending  [8] Trunk & Channel Cyclic Ascending  [9] Ring to Hunt Group  [10] Select Trunk by ISDN SuppServ Table  [11] Dest Number + Ascending Notes: Version 6.6 Mediant 800B GW & E-SBC...
  • Page 836 Mediant 800B GW & E-SBC Parameter Description  For a detailed description of the parameter's options, see 'Configuring Hunt Group Settings' on page 295.  Channel select mode per Trunk Group can be configured in the Hunt Group Settings (see 'Configuring Hunt Group Settings' on page 295).
  • Page 837 PstnPrefix 0 = 100, 1, 200, *, 0, 2, , , ,; PstnPrefix 1 = *, 2, *, , 1, 3, acl, joe, , ,; Note: For a detailed description of this table, see 'Configuring Inbound IP Routing Table' on page 332. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 838 Mediant 800B GW & E-SBC Parameter Description Web/EMS: IP to Tel Routing Determines whether to route IP calls to the Trunk Group (or IP Mode Group) before or after manipulation of the destination number [RouteModeIP2Tel] (configured in 'Configuring Source/Destination Number Manipulation Rules' on page 301).
  • Page 839 Trunk Group. The Destination Number IP to Tel Manipulation table must be used to remove this prefix before placing the call to the ISDN. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 840 Mediant 800B GW & E-SBC Parameter Description [FaxReroutingMode] Enables re-routing of Tel-to-IP calls that are identified as fax calls. If a CNG tone is detected on the Tel side of a Tel-to-IP call, the prefix string "FAX" is appended to the destination number before routing and manipulation.

  • Page 841: Ip Connectivity Parameters

    Defines the time interval (in seconds) between SIP OPTIONS Alive Time Keep-Alive messages used for the IP Connectivity application. EMS: Alternative Routing Keep The valid range is 5 to 2,000,000. The default is 60. Alive Time [AltRoutingTel2IPKeepAliveTime] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 842: Alternative Routing Parameters

    Mediant 800B GW & E-SBC Parameter Description Web: Max Allowed Packet Loss for Defines the packet loss (in percentage) at which the IP Alt Routing [%] connection is considered a failure and Alternative Routing [IPConnQoSMaxAllowedPL] mechanism is activated. The default is 20%.
  • Page 843 TCP, if Trunk Group ID 2 is unavailable: ForwardOnBusyTrunkDest 1 = 2, 112@10.13.4.12:5060;transport=tcp; Note: For a detailed description of this table, see 'Alternative Routing to IP Destination upon Busy Trunk' on page 342. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 844: Number Manipulation Parameters

    Mediant 800B GW & E-SBC 51.11.16 Number Manipulation Parameters The number manipulation parameters are described in the table below. Table ‎ 5 1-67: Number Manipulation Parameters Parameter Description [ManipulateIP2PSTNReferTo] Enables the manipulation of the called party (destination) number according to the SIP Refer-To header received by the device for TDM (PSTN) blind transfer.
  • Page 845 Tel.  [-1] Not Configured (default)  [0] Unkown  [1] Busy  [2] No Reply  [3] Network Busy  [4] Deflection  [9] DTE out of Order  [10] Forwarding DTE Version 6.6 Mediant 800B GW & E-SBC...
  • Page 846 Mediant 800B GW & E-SBC Parameter Description  [13] Transfer  [14] PickUp  [15] Systematic/Unconditional Note: This parameter is applicable only to digital PSTN interfaces (ISDN). Web: Set TEL-to-IP Redirect Defines the redirect reason for Tel-to-IP calls. If redirect (diversion)
  • Page 847 [1] Yes = Add Trunk Group ID as prefix to called number. Notes:  This option can be used to define various routing rules.  To use this feature, you must configure the Trunk Group IDs Version 6.6 Mediant 800B GW & E-SBC...
  • Page 848 Mediant 800B GW & E-SBC Parameter Description (see Configuring Trunk Group Table on page 293). Web: Add Trunk ID as Prefix Determines whether or not the port number / Trunk ID is added as EMS: Add Port ID As Prefix a prefix to the called (destination) number for Tel-to-IP calls.
  • Page 849 The valid range is an 8-character string. The default is an empty string. Web: Add Number Plan and Determines whether the TON/PLAN parameters are included in the Type to RPI Header Remote-Party-ID (RPID) header. EMS: Add Ton 2 RPI  [0] No Version 6.6 Mediant 800B GW & E-SBC...
  • Page 850 Mediant 800B GW & E-SBC Parameter Description  [AddTON2RPI] [1] Yes (default) If the Remote-Party-ID header is enabled (EnableRPIHeader = 1) and AddTON2RPI = 1, it's possible to configure the calling and called number type and number plan using the Number Manipulation tables for Tel-to-IP calls.
  • Page 851 Note: For a detailed description of this table, see 'Configuring Source/Destination Number Manipulation' on page 301. Source Phone Number Manipulation for IP-to-Tel Calls Table Web: Source Phone Number This parameter table manipulates the source number for IP-to-Tel Version 6.6 Mediant 800B GW & E-SBC...
  • Page 852 Mediant 800B GW & E-SBC Parameter Description Manipulation Table for IP > Tel calls. The format of this parameter is as follows: Calls [SourceNumberMapIp2Tel] EMS: SIP Manipulations > FORMAT SourceNumberMapIp2Tel_Index = Source IP to Telcom SourceNumberMapIp2Tel_DestinationPrefix, [SourceNumberMapIP2Tel] SourceNumberMapIp2Tel_SourcePrefix, SourceNumberMapIp2Tel_SourceAddress, SourceNumberMapIp2Tel_NumberType,...
  • Page 853 This table parameter configures the Phone Context table. This EMS: SIP Manipulations > parameter maps NPI and TON to the SIP 'phone-context' Phone Context parameter, and vice versa. [PhoneContext] The format for this parameter is as follows: [PhoneContext] Version 6.6 Mediant 800B GW & E-SBC...

  • Page 854: Least Cost Routing Parameters

    Mediant 800B GW & E-SBC Parameter Description FORMAT PhoneContext_Index = PhoneContext_Npi, PhoneContext_Ton, PhoneContext_Context; [\PhoneContext] For example: PhoneContext 0 = 0,0,unknown.com PhoneContext 1 = 1,1,host.com PhoneContext 2 = 9,1,na.e164.host.com Note: For a detailed description of this table, see 'Mapping NPI/TON to SIP Phone-Context' on page 315.

  • Page 855: Ldap Parameters

    Web: LDAP Bind DN Defines the LDAP server's bind Distinguished Name (DN). EMS: Bind DN This is used as the username during connection and [LDAPBindDN] binding to the server. For example: LDAPBindDN = "CN=Search user,OU=Labs,DC=OCSR2,DC=local" Version 6.6 Mediant 800B GW & E-SBC...
  • Page 856 Mediant 800B GW & E-SBC Parameter Description Note: The DN is used to uniquely name an Active Directory object. Web: LDAP Search Dn Defines up to three search DNs for LDAP search queries. EMS: Search DN These are the DN subtrees where the search is done. This [LDAPSearchDN] parameter is mandatory for the search.

  • Page 857: Sbc And Crp Parameters

    Table ‎ 5 1-70: SBC and CRP Parameters Parameter Description CRP-Specific Parameters Web: CRP Application Enables the CRP application. [EnableCRPApplication]  [0] Disable (default)  [1] Enable Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 858 Mediant 800B GW & E-SBC Parameter Description Web: CRP Survivability Defines the CRP mode. Mode  [0] Standard Mode (default) [CRPSurvivabilityMode]  [1] Always Emergency Mode  [2] Auto-answer REGISTER SBC-Specific Parameters Web/EMS: Enable SBC Enables the Session Border Control (SBC) application.
  • Page 859 Determines the device's handling of REFER requests. Behavior  [0] Transparent = (Default) Refer-To header is unchanged and [SBCReferBehavior] the device forwards the REFER as is.  [1] DB URL = Changes the Refer-To header so that the re- Version 6.6 Mediant 800B GW & E-SBC...
  • Page 860 Mediant 800B GW & E-SBC Parameter Description routed INVITE is sent through the SBC: Before forwarding the REFER request, the device changes the host part to the device's IP address and adds a special prefix ("T~&R_") to the Contact user part.
  • Page 861 [0] 0 = (Default) Send SIP 401 "Unauthorized" with a WWW- [AuthChallengeMethod] Authenticate header as the authentication challenge response.  [1] 1 = Send SIP 407 "Proxy Authentication Required" with a Proxy-Authenticate header as the authentication challenge response. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 862 Mediant 800B GW & E-SBC Parameter Description Web: Authentication Quality Defines the authentication and integrity level of quality of protection of Protection (QoP) for digest authentication offered to the client. When the [AuthQOP] device challenges a SIP request (e.g., INVITE), it sends a SIP 401 response with the Proxy-Authenticate header or WWW-Authenticate header containing the 'qop' parameter.
  • Page 863 The call is disconnected only if the authenticating server responds with a 200 OK. [SBCExtensionsProvisionin Enables SBC user registration for interoperability with BroadSoft's gMode] BroadWorks server, to provide call survivability in case of connectivity failure with the BroadWorks server. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 864 Mediant 800B GW & E-SBC Parameter Description  [0] = (Default) Normal processing of REGISTER messages.  [1] = Registration method for BroadWorks server. In a failure scenario with BroadWorks, the device acts as a backup SIP proxy server, maintaining call continuity between the enterprise LAN users (subscribers) and between the subscribers and the PSTN (if provided).
  • Page 865 (i.e., not terminated on the device). [SBCSharedLineRegMode]  [1] Enable = REGISTER messages of secondary lines are terminated on the device. Note: The device always forwards REGISTER messages of the primary line. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 866 Mediant 800B GW & E-SBC Parameter Description Web: SBC Forking Handling Defines the handling of SIP 18x responses received due to call Mode forking of an INVITE. [SBCForkingHandlingMode  [0] Latch On First = (Default) Only the first 18x is forwarded to the INVITE-initiating UA.
  • Page 867 EMS: IP to IP Routing routing incoming SIP messages such as INVITE messages to an IP [IP2IPRouting] destination. The format of this parameter is as follows: [IP2IPRouting] FORMAT IP2IPRouting_Index = IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, Version 6.6 Mediant 800B GW & E-SBC...
  • Page 868 Mediant 800B GW & E-SBC Parameter Description IP2IPRouting_RequestType, IP2IPRouting_MessageCondition, IP2IPRouting_ReRouteIPGroupID, IP2IPRouting_Trigger, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions, IP2IPRouting_CostGroup; [ \IP2IPRouting ] For example: IP2IPRouting 1 = -1, *, *, *, *, 0, , -1, 0, 0, 1, , , 0, -1, 0,;...

  • Page 869: Standalone Survivability Parameters

    If the connection to the proxy fails ('Emergency Mode'), the device serves as a proxy by allowing calls internal to the local network or outgoing to PSTN. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 870 Mediant 800B GW & E-SBC Parameter Description Web: SAS Local SIP UDP Port Defines the local UDP port for sending and receiving SIP EMS: Local SIP UDP messages for SAS. The SIP entities in the local network need to [SASLocalSIPUDPPort] send the registration requests to this port.
  • Page 871 Contact header point to the same host. Note: Operating in this mode causes all incoming dialog requests to traverse the SAS, which may cause load problems. Web: SAS Survivability Mode Determines the Survivability mode used by the SAS application. Version 6.6 Mediant 800B GW & E-SBC...
  • Page 872 Mediant 800B GW & E-SBC Parameter Description  [0] Standard = (Default) Incoming INVITE and REGISTER EMS: Survivability Mode [SASSurvivabilityMode] requests are forwarded to the defined Proxy list of SASProxySet in Normal mode and handled by the SAS application in Emergency mode.
  • Page 873 "4002@10.33.4.226" (i.e., keep only four digits from right of user part): SASRegistrationManipulation 0 = 0, 4; Note: For a detailed description of this table, see 'Manipulating URI user part of Incoming REGISTER' on page 506. Web: SAS IP-to-IP Routing Table Version 6.6 Mediant 800B GW & E-SBC...

  • Page 874: Ip Media Parameters

    Mediant 800B GW & E-SBC Parameter Description [IP2IPRouting] This table parameter configures the IP-to-IP Routing table for SAS routing rules. The format of this parameter is as follows: [IP2IPRouting] FORMAT IP2IPRouting_Index = IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions;...
  • Page 875 (configurable) volume level.  [0] Disable (default)  [1] Enable Notes:  This parameter can also be configured in a Tel Profile.  For a description of AGC, see Automatic Gain Control Version 6.6 Mediant 800B GW & E-SBC...
  • Page 876 Mediant 800B GW & E-SBC Parameter Description (AGC) on page 166. Web: AGC Slope Determines the AGC convergence rate: EMS: Gain Slope  [0] 0 = 0.25 dB/sec [AGCGainSlope]  [1] 1 = 0.50 dB/sec  [2] 2 = 0.75 dB/sec ...
  • Page 877 Defines the number of consecutive patterns to trigger the pattern detection event. The valid range is 0 to 31. The default is 5. Note: For this parameter to take effect, a device reset is required. Version 6.6 Mediant 800B GW & E-SBC...

  • Page 878: Auxiliary And Configuration File Name Parameters

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

  • Page 879: Automatic Update Parameters

    Defines the name of the cmp file and the path to the server (IP 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 example: http://192.168.0.1/filename Version 6.6 Mediant 800B GW & E-SBC...
  • Page 880 Mediant 800B GW & E-SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  When this parameter is configured, the device always loads the cmp file after it is reset.  The cmp file is validated before it's burned to flash. The checksum of the cmp file is also compared to the previously burnt checksum to avoid unnecessary resets.

  • Page 881: Dsp Templates

    8 x FXO 4 x BRI & 4 x FXS 4 x FXS & 4 x FXO 4 x BRI 6 x E&M 4 x FXS or 4 x FXO (Telephony Interfaces may be Version 6.6 Mediant 800B GW & E-SBC...
  • Page 882 The Conference Participants column lists the number of participants in one or more conference (bridge), where each conference may include three or more participants. Conferences are supported on all above configurations. Please contact AudioCodes for the maximum number of participants per configuration. User's Manual...

  • Page 883: Technical Specifications

    Rouge RTP detection and prevention*, SIP message policy Encryption and TLS, SRTP, HTTPS, SSH, IPSec, IKE, SNMPv3, Client/Server Authentication authentication Privacy Topology Hiding, User Privacy Traffic Separation Physical or VLAN Interface Separation (Media / OAMP / Control) Version 6.6 Mediant 800B GW & E-SBC...
  • Page 884 Mediant 800B GW & E-SBC Function Specification Interoperability Standalone SIP B2BUA, Netann (RFC4240), MSCML (RFC5022) or RFC 4117 transcoding device control. Full SIP transparency, mature & broadly deployed SIP stack ITSP and PBX support Interoperable with many SIP trunk Service Providers and PBX...
  • Page 885 Physical / Environmental Enclosure 1U chassis Dimensions 1U x 320mm x 345mm (HxWxD) Weight Approx. 5.95lb (2.7kg) installed with OSN Mounting Desktop or 19" mount Power 100-240V 1.5A 50-60 Hz Operating Temperature 5° to 40°C Version 6.6 Mediant 800B GW & E-SBC...
  • Page 886 User's Manual Ver. 6.6 www.audiocodes.com...

This manual is also suitable for:

E-sbc

Table of Contents