Page 1 User's Manual Enterprise Session Border Controller Analog & Digital VoIP Media Gateway Mediant 800B Gateway & E-SBC Version 6.8...
Page 3: Table Of Contents
Getting Familiar with CLI ..................71 7.1.1 Understanding Configuration Modes ...............71 7.1.2 Using CLI Shortcuts ....................72 7.1.3 Common CLI Commands ..................73 7.1.4 Configuring Tables in CLI ..................74 7.1.5 Understanding CLI Error Messages ................75 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 4 Mediant 800B Gateway and E-SBC Enabling CLI ......................75 7.2.1 Enabling Telnet for CLI ....................75 7.2.2 Enabling SSH with RSA Public Key for CLI.............76 Establishing a CLI Session ................... 77 Configuring Maximum Telnet/SSH Sessions ............78 Viewing and Terminating Current CLI Sessions ............ 79 Configuring Displayed Output Lines in CLI Terminal Window .......
Page 5 14.2.2.1 T.38 Fax Relay Mode ................169 14.2.2.2 G.711 Fax / Modem Transport Mode .............172 14.2.2.3 Fax Fallback ...................172 14.2.2.4 Fax/Modem Bypass Mode..............173 14.2.2.5 Fax / Modem NSE Mode ................174 14.2.2.6 Fax / Modem Transparent with Events Mode ........175 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 6 Mediant 800B Gateway and E-SBC 14.2.2.7 Fax / Modem Transparent Mode ............175 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......176 14.2.3 V.34 Fax Support ....................176 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........177 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ............178 14.2.3.3 V.34 Fax Relay for SG3 Fax Machines ..........178...
Page 7 19.2 Configuring Coder Groups .................. 318 19.3 Configuring Tel Profile ..................319 19.4 Configuring IP Profiles ..................323 Gateway Application .....................353 20 Introduction ..................... 355 21 Digital PSTN ..................... 357 21.1 Configuring Trunk Settings ................. 357 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 8 Mediant 800B Gateway and E-SBC 21.2 TDM and Timing ....................361 21.2.1 Configuring TDM Bus Settings ................361 21.2.2 Clock Settings ......................361 21.2.2.1 Recovering Clock from PSTN Line Interface .........362 21.2.2.2 Configuring Internal Clock as Clock Source...........362 21.3 Configuring CAS State Machines ............... 363 21.4 Configuring Digital Gateway Parameters ............
Page 9 26.11.4 Enhanced 9-1-1 Support for Lync Server 2010 .............466 26.11.4.1 About E9-1-1 Services ................466 26.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........467 26.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 26.11.4.4 Configuring AudioCodes ELIN Gateway ..........475 26.12 Multilevel Precedence and Preemption ............... 478 26.12.1 MLPP Preemption Events in SIP Reason Header ..........480...
Page 10 Mediant 800B Gateway and E-SBC 27.2 Configuring Metering Tones ................493 27.3 Configuring FXO Settings ................... 494 27.4 Configuring Authentication .................. 495 27.5 Configuring Automatic Dialing ................497 27.6 Configuring Caller Display Information..............498 27.7 Configuring Call Forward ..................500 27.8 Configuring Caller ID Permissions ..............
Page 11 29.5.3 Configuring SBC IP-to-IP Routing .................571 29.5.4 Configuring SIP Response Codes for Alternative Routing Reasons .....580 29.6 SBC Manipulations ..................... 583 29.6.1 Configuring IP-to-IP Inbound Manipulations ............585 29.6.2 Configuring IP-to-IP Outbound Manipulations ............588 Cloud Resilience Package ..................595 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 12 Mediant 800B Gateway and E-SBC 30 CRP Overview ....................597 31 CRP Configuration ..................599 31.1 Enabling the CRP Application ................599 31.2 Configuring Call Survivability Mode ..............600 31.3 Pre-Configured IP Groups .................. 601 31.4 Pre-Configured IP-to-IP Routing Rules ............... 602 31.4.1 Normal Mode ......................602...
Page 13 42.1.1.2 Provisioning from TFTP Server using DHCP Option 66 ......673 42.1.2 HTTP-based Provisioning ..................673 42.1.3 FTP-based Provisioning ..................674 42.1.4 Provisioning using AudioCodes EMS ..............674 42.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 675 42.2.1 Files Provisioned by Automatic Update ..............675 42.2.2 File Location for Automatic Update ...............675...
Page 14 Mediant 800B Gateway and E-SBC 44 Saving Current Configuration to a File and Sending it to Remote Destination ......................689 45 USB Storage Capabilities ................691 Status, Performance Monitoring and Reporting ..........693 46 System Status ....................695 46.1 Viewing Device Information ................695 46.2 Viewing Ethernet Port Information ..............
Page 15 51 Syslog and Debug Recordings ..............747 51.1 Syslog Message Format ..................747 51.1.1 Event Representation in Syslog Messages ............748 51.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......750 51.1.3 SNMP Alarms in Syslog Messages ...............751 51.2 Enabling Syslog ....................751 51.3 Configuring Web Operations to Report to Syslog ..........
Page 16 Mediant 800B Gateway and E-SBC 57.2.7 DNS Parameters ....................804 57.2.8 DHCP Parameters ....................805 57.2.9 NTP and Daylight Saving Time Parameters ............807 57.3 Debugging and Diagnostics Parameters ............. 809 57.3.1 General Parameters ....................809 57.3.2 SIP Test Call Parameters ..................811 57.3.3 Syslog, CDR and Debug Parameters ..............812 57.3.4 Resource Allocation Indication Parameters............817...
Page 17 57.14.4 Call Setup Rules Parameters ................1052 58 SBC and DSP Channel Capacity ..............1053 58.1 Signaling-Media Sessions & User Registrations ..........1053 58.2 Channel Capacity and Capabilities ..............1055 59 Technical Specifications ................1059 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 18 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 19: Weee Eu Directive
User's Manual Notices Notice This document describes AudioCodes Mediant 800B Gateway & Enterprise Session Border Controller (E-SBC). Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.
Page 20: Related Documentation
Mediant 800B Gateway and E-SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 800 Gateway and E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP Reference Guide SBC Design Guide Recommended Security Guidelines Configuration Note...
Page 21 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
Page 22 Mediant 800B Gateway and E-SBC Document Revision Record LTRT Description 10275 Initial document release for Version 6.8. 10287 Screenshot updated for example of SIP message manipulation rules; available video coders not based on license key; AupdHttpUserAgent parameter updated; RFC updated for CDR Syslog message (RFC 3164); core dump procedure updated; HA Settings page screenshot updated for configuring HA;...
Page 23 Automatic Update; Automatic Update from Remote Servers; Configuring RTCP XR. 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 24 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 25: Overview
User's Manual 1. Overview Overview AudioCodes' Mediant 800B Gateway and E-SBC (hereafter referred to as device) is a member of AudioCodes family of Enterprise Session Border Controllers (E-SBC), enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks.
Page 26 Mediant 800B Gateway and E-SBC The device provides up to 12 Ethernet ports (up to 4 Gigabit Ethernet ports and up to 8 Fast Ethernet ports). These ports operate in port-pair redundancy, providing up to 6 port- pair groups. The device allows full management through its HTTP/S-based embedded Web server. This user-friendly Web interface allows remote configuration using any standard Web browser (such as Microsoft™...
Page 27: Getting Started With Initial Connectivity
Part I Getting Started with Initial Connectivity...
Page 29: Introduction
User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 30 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 31: Default Oamp Ip Address
Table 3-1: Default VoIP LAN IP Address for OAMP IP Address Value Application Type OAMP + Media + Control IP Address 192.168.0.2 Prefix Length 255.255.255.0 (24) Default Gateway 192.168.0.1 Underlying Device Interface Name "O+M+C" Version 6.8 Mediant 800B Gateway and E-SBC...
Page 32 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 33: Configuring Voip Lan Interface For Oamp
IP address of the device; the Web interface's Web Login screen appears: Figure 4-1: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 34 Mediant 800B Gateway and E-SBC Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table) and then configure the device's physical Ethernet port-pair (group) that you want to later assign to the OAMP interface. For more information, see Configuring Physical Ethernet Ports on page 117.
Page 35: Cli
(config-voip)# interface network-if 0 Configure the IP address: (network-if-0)# ip-address <IP address> Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Configure the Default Gateway address: (network-if-0)# gateway <IP address> Version 6.8 Mediant 800B Gateway and E-SBC...
Page 36 Mediant 800B Gateway and E-SBC Exit the Interface table: (network-if-0)# exit Exit the VoIP configuration mode: (config-voip)# exit Reset the device with a flash burn: # reload now Cable the device to your network. You can now access the device's management interface using this new OAMP IP address.
Page 37: Management Tools
Part II Management Tools...
Page 39: Introduction
Web, CLI, and ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 783. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 40 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 41: Web-Based Management
• ® Mozilla Firefox (Versions 5 through 9.0)  Recommended screen resolutions: 1024 x 768 pixels, or 1280 x 1024 pixels Note: Your Web browser must be JavaScript-enabled to access the Web interface. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 42: Accessing The Web Interface
Mediant 800B Gateway and E-SBC 6.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see ''Computer Requirements'' on page 41). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...
Page 43: Areas Of The Gui
''Navigation Tree'' on page 45. 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 47. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 44: Toolbar Description
Mediant 800B Gateway and E-SBC 6.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Table 6-2: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see ''Saving Configuration'' on page 626).
Page 45: Navigation Tree
The expanded view displays all the menus pertaining to the selected configuration tab; the reduced view displays only commonly used menus.  To display a reduced menu tree, select the Basic option (default). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 46: Showing / Hiding The Navigation Pane
Mediant 800B Gateway and E-SBC  To display all menus and submenus, select the Advanced option. Figure 6-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 6.1.5.2 Showing / Hiding the Navigation Pane You can hide the Navigation pane to provide more space for elements displayed in the Work pane.
Page 47: Working With Configuration
 Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 48 Mediant 800B Gateway and E-SBC The figure below shows an example of a page displaying basic parameters only. If you click the Advanced Parameter List button (shown below), the page will also display the advanced parameters. Figure 6-6: Toggling between Basic and Advanced View Notes: •...
Page 49: Modifying And Saving Parameters
Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts to its previous value and is highlighted in red, as shown in the figure below: Figure 6-9: Value Reverts to Previous Valid Value Version 6.8 Mediant 800B Gateway and E-SBC...
Page 50: Working With Tables
Mediant 800B Gateway and E-SBC 6.1.6.4 Working with Tables Many of the Web configuration pages provide tables for configuring various functionalities of the device. The figure below and subsequent table describe the areas of a typical configuration table: Figure 6-10: Displayed Details Pane...
Page 51 - Displays the previous page  - Displays the first page Defines the number of rows to display per page. You can select 5 or 10, where the default is 10. Displays the currently displayed page number. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 52: Searching For Configuration Parameters
Mediant 800B Gateway and E-SBC 6.1.7 Searching for Configuration Parameters You can locate the exact Web page on which a specific parameter appears, by using the Search feature. To search for a Web parameter, you must use the ini file parameter name as the search key.
Page 53: Creating A Login Welcome Message
Figure 6-13: User-Defined Web Welcome Message after Login To enable and create a Welcome message, use the WelcomeMessage table ini file parameter, as described in the table below. If this parameter is not configured, no Welcome message is displayed. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 54 Mediant 800B Gateway and E-SBC Table 6-6: ini File Parameter for Welcome Login Message Parameter Description [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface. The format of this parameter is as follows: [WelcomeMessage] FORMAT WelcomeMessage_Index = WelcomeMessage_Text;...
Page 55: Getting Help
Instead of clicking the Help button for each page you open, you can open it once for a page and then simply leave it open. Each time you open a different page, the Help topic pertaining to that page is automatically displayed. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 56: Logging Off The Web Interface
Mediant 800B Gateway and E-SBC 6.1.10 Logging Off the Web Interface The following procedure describes how to log off the Web interface.  To log off the Web interface: On the toolbar, click the Log Off icon; the following confirmation message box...
Page 57 (red): Module failure and "Failure" is displayed Port (trunk or channel) status icon. Icon Trunk Description Channel Description (Digital Module) (Analog Modules) Disable: Trunk not Idle: Channel is currently on-hook configured (not in use) (gray) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 58 Mediant 800B Gateway and E-SBC Item # Description Active - OK: Trunk Call Connected: Active RTP stream synchronized (green) RAI Alarm: Remote Alarm Indication (RAI), also known (yellow) as the Yellow Alarm LOS/LOF Alarm: Loss due to Not Connected: No FXO line is...
Page 59: Assigning A Port Name
Note: At least one Security Administrator user must exits. Master Read / write privileges for all pages. Can create all user types, including additional Master users and Security Administrators. It can delete all users except the last Version 6.8 Mediant 800B Gateway and E-SBC...
Page 60 Mediant 800B Gateway and E-SBC Numeric User Level Representation in Privileges RADIUS Security Administrator. Administrator Read / write privileges for all pages, except security- related pages (read-only). Monitor No access to security-related and file-loading pages; read-only access to all other pages.
Page 61: Basic User Accounts Configuration
The username and password can be a string of up to 19 characters and are case- sensitive. • When only the basic user accounts are being used, up to two users can be concurrently logged in to the Web interface, and they can be the same user. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 62 Mediant 800B Gateway and 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 63: Advanced User Accounts Configuration
Subsequent access: Configuration tab > System menu > Web User Accounts. The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"): Figure 6-18: Web Users Table Page Version 6.8 Mediant 800B Gateway and E-SBC...
Page 64 Mediant 800B Gateway and E-SBC Click Add; the following dialog box is displayed: Figure 6-19: Web Users Table - Add Record Dialog Box Configure a Web user according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
Page 65 The default is according to the settings of the 'Deny Authentication Timer' parameter (see ''Configuring Web Security Settings'' on page 67). Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 66: Displaying Login Information Upon Login
Mediant 800B Gateway and E-SBC Parameter Description Web: User Level Defines the user's access level. CLI: privilege  Monitor = (Default) Read-only user. This user can only view Web pages and access to security-related pages is denied.  Administrator = Read/write privileges for all pages, except security- related pages including the Web Users table where this user has only read-only privileges.
Page 67: 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.8 Mediant 800B Gateway and E-SBC...
Page 68: Configuring Web And Telnet Access List
Mediant 800B Gateway and 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 69 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.8 Mediant 800B Gateway and E-SBC...
Page 70 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 71: Cli-Based Management
Enable mode upon initial login. For configuring user access levels, see Configuring Web User Accounts on page 59. • The default password for accessing the Enable mode is "Admin" (case-sensitive). To change this password, use the CLIPrivPass ini file parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 72: Using Cli Shortcuts
Mediant 800B Gateway and E-SBC The Enable mode groups the configuration commands under the following command sets: • config-system: Provides the general and system related configuration commands, for example, Syslog configuration. This set is accessed by typing the following command:...
Page 73: Common Cli Commands
Applied to a command output. The filter should be typed after the command with a pipe mark (|). Supported filters:  include <word> – filter (print) lines which contain <word>  exclude <word> – filter lines which does not contain <word> Version 6.8 Mediant 800B Gateway and E-SBC...
Page 74: Configuring Tables In Cli
Mediant 800B Gateway and E-SBC Command Description  grep <options> - filter lines according to grep common Unix utility options  egrep <options> - filter lines according to egrep common Unix utility options  begin <word> – filter (print) lines which begins with <word>...
Page 75: Understanding Cli Error Messages
Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 787. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 76: Enabling Ssh With Rsa Public Key For Cli
Mediant 800B Gateway and E-SBC 7.2.2 Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text. To overcome this, Secure SHell (SSH) is used, which is the de-facto standard for secure CLI.
Page 77: Establishing A Cli Session
Putty, which can be downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.  Telnet: The device can be accessed through its Ethernet interface by the Telnet protocol using Telnet client software.The following procedure describes how to establish a CLI session with the device. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 78: Configuring Maximum Telnet/Ssh Sessions
Mediant 800B Gateway and E-SBC The following procedure describes how to access the CLI through Telnet/SSH. Note: The CLI login credentials are the same as all the device's other management interfaces (such as Web interface). The default username and password is "Admin"...
Page 79: Viewing And Terminating Current Cli Sessions
When this command is run, it ends the Telnet/SSH session (logs out the RS-232 session) and displays the CLI login prompt. Note: The session from which the command is run cannot be terminated. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 80: Configuring Displayed Output Lines In Cli Terminal Window
Mediant 800B Gateway and E-SBC Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be specified from 0 to 65,535, or determined by re-sizing the terminal window by mouse- dragging the window's border.
Page 81: Snmp-Based Management
SNMP Manager. All supported MIB files are supplied to customers as part of the release. AudioCodes EMS is an advanced solution for standards-based management that covers all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of the device.
Page 82 Mediant 800B Gateway and E-SBC  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String). Configure SNMP community strings according to the table below. Click Submit, and then save ("burn") your settings to flash memory.
Page 83: Configuring Snmp Trap Destinations
Figure 8-1: SNMP Trap Destinations Page Configure the SNMP trap manager parameters according to the table below. Select the check box corresponding to the SNMP Manager that you wish to enable. Click Submit. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 84: Configuring Snmp Trusted Managers
Mediant 800B Gateway and E-SBC Note: Only row entries whose corresponding check boxes are selected are applied when clicking Submit; otherwise, settings revert to their defaults. Table 8-2: SNMP Trap Destinations Parameters Description Parameter Description Web: SNMP Manager Enables the SNMP Manager to receive traps and checks...
Page 85 Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address. Define an IP address in dotted-decimal notation. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 86: Configuring Snmp V3 Users
Mediant 800B Gateway and E-SBC Configuring SNMP V3 Users The SNMP v3 Users table lets you configure up to 10 SNMP v3 users for authentication and privacy. The following procedure describes how to configure SNMP v3 users in the Web interface.
Page 87 Group The group with which the SNMP v3 user is associated. CLI: group  [0] Read-Only (default) [SNMPUsers_Group]  [1] Read-Write  [2] Trap Note: All groups can be used to send traps. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 88 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 89: Ini File-Based Management
(dynamic tables of other applications are empty, but static tables are not). The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME]. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 90 Mediant 800B Gateway and E-SBC  Format line: Specifies the columns of the table (by their string names) that are to be configured. • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed.
Page 91: General Ini File Formatting Rules
Open a text file editor such as Notepad. Add only the required parameters and their settings. Save the file with the ini file extension name (e.g., myconfiguration.ini). Load the file to the device. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 92: Loading An Ini File To The Device
The file may be loaded to the device using HTTP. These protocols are not secure and are vulnerable to potential hackers. To overcome this security threat, the AudioCodes DConvert utility allows you to binary-encode (encrypt) the ini file before loading it to the device.
Page 93: Configuring Password Display In Ini File
PC, the password is displayed obscured (i.e., $1$<obscured password>). INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any...
Page 94 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 95: General System Settings
Part III General System Settings...
Page 97: Configuring Certificates
Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 98 Mediant 800B Gateway and E-SBC When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows:  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for...
Page 99 [5] 5 = TLS 1.2 and TLS 1.0 only.  [6] 6 = TLS 1.2 and TLS 1.1 only  [7] 7 = TLS 1.2, TLS 1.1 and TLS 1.0 only (excludes SSL 3.0). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 100: Assigning Csr-Based Certificates To Tls Contexts
Mediant 800B Gateway and E-SBC Parameter Description Web: Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher CLI: ciphers-server list format). [TLSContexts_Serve For valid values, refer to URL rCipherString] http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).
Page 101 When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below: -----BEGIN CERTIFICATE----- MIIDkzCCAnugAwIBAgIEAgAAADANBgkqhkiG9w0BAQQFADA/MQswCQYDVQQGEw JGUjETMBEGA1UEChMKQ2VydGlwb3N0ZTEbMBkGA1UEAxMSQ2VydGlwb3N0ZSBT ZXJ2ZXVyMB4XDTk4MDYyNDA4MDAwMFoXDTE4MDYyNDA4MDAwMFowPzELMAkGA1 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 102: Assigning Externally Created Private Keys To Tls Contexts
Mediant 800B Gateway and E-SBC UEBhMCRlIxEzARBgNVBAoTCkNlcnRpcG9zdGUxGzAZBgNVBAMTEkNlcnRpcG9z dGUgU2VydmV1cjCCASEwDQYJKoZIhvcNAQEBBQADggEOADCCAQkCggEAPqd4Mz iR4spWldGRx8bQrhZkonWnNm`+Yhb7+4Q67ecf1janH7GcN/SXsfx7jJpreWUL f7v7Cvpr4R7qIJcmdHIntmf7JPM5n6cDBv17uSW63er7NkVnMFHwK1QaGFLMyb FkzaeGrvFm4k3lRefiXDmuOe+FhJgHYezYHf44LvPRPwhSrzi9+Aq3o8pWDguJ uZDIUP1F1jMa+LPwvREXfFcUW+w== -----END CERTIFICATE----- Scroll down to the Upload certificates files from your computer group, click the Browse button corresponding to the 'Send Device Certificate...' field, navigate to the cert.txt file, and then click Send File.
Page 103 Open the TLS Contexts page again, select the TLS Context index row, and then verify that under the Certificate Information group, the 'Private key' field displays "OK"; otherwise, consult your security administrator. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 104: Generating Private Keys For Tls Contexts
Mediant 800B Gateway and E-SBC 10.4 Generating Private Keys for TLS Contexts The device can generate the private key for a TLS Context, as described in the procedure below.  To generate a new private key for a TLS Context: Open the TLS Contexts page (Configuration tab >...
Page 105: Creating Self-Signed Certificates For Tls Contexts
The device provides its own Trusted Root Certificate Store. This lets you manage certificate trust. You can add up to 20 certificates to the store per TLS Context (but this may be less depending on certificate file size). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 106 Mediant 800B Gateway and E-SBC The trusted store can also be used for certificate chains. A certificate chain is a sequence of certificates where each certificate in the chain is signed by the subsequent certificate. The last certificate in the list of certificates is the Root CA certificate, which is self-signed.
Page 107: Configuring Mutual Tls Authentication
- both client and server should be authenticated using X.509 certificates. This is achieved by installing a client certificate on the management PC and loading the root CA's certificate to the device's Trusted Root Certificate Store. The Trusted Version 6.8 Mediant 800B Gateway and E-SBC...
Page 108 Mediant 800B Gateway and E-SBC Root Certificate file may contain more than one CA certificate combined, using a text editor.  To enable mutual TLS authentication for HTTPS: Set the 'Secured Web Connection (HTTPS)' field to HTTPS Only in the Web Security Settings page (see Configuring Web Security Settings on page 67) to ensure you have a method for accessing the device in case the client certificate does not work.
Page 109: Configuring Tls Server Certificate Expiry Check
In the 'TLS Expiry Check Period' field, enter the periodical interval (in days) for checking the TLS server certificate expiry date. By default, the device checks the certificate every 7 days. Click the Submit TLS Expiry Settings button. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 110 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 111: Date And Time
Saving Time (DST), see 'Configuring Daylight Saving Time' on page 113. You can also configure the device to authenticate and validate the NTP messages received from the NTP server. Authentication is done using an authentication key with the MD5 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 112 Mediant 800B Gateway and E-SBC cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication. The following procedure describes how to configure SNTP. For detailed descriptions of the configuration parameters, see NTP and Daylight Saving Time Parameters on page 807.
Page 113: Configuring Daylight Saving Time
If the current date falls within the DST period, verify that it has been successful applied to the device's current date and time. You can view the device's date and time in the Regional Settings page (see 'Configuring Date and Time Manually' on page 111). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 114 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 115: General Voip Configuration
Part IV General VoIP Configuration...
Page 117: Network
You can also configure these ports using the table ini file parameter, PhysicalPortsTable or CLI command, configure voip/physical-port. Note: All the LAN ports have the same MAC address. This is the MAC address of the device itself. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 118 Mediant 800B Gateway and E-SBC  To configure the physical Ethernet ports: Open the Physical Ports Settings page (Configuration tab > VoIP menu > Network > Physical Ports Table). Select a port that you want to configure by clicking its table row, and then click Edit;...
Page 119: Configuring Ethernet Port Groups
'Configuring Physical Ethernet Ports' on page 117. The following procedure describes how to configure Tx/Rx mode in the Web interface. You can also configure this using the table ini file parameter, EtherGroupTable or CLI command, configure voip/ether-group. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 120 Mediant 800B Gateway and E-SBC Notes: • Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group. To remove the port, either set the 'Member' field to None or to a different port.
Page 121: Configuring Underlying Ethernet Devices
Device Table page. The Ethernet Device Status Table page can also be accessed from the Status & Diagnostics tab > VoIP Status menu > Ethernet Device Status Table (see ''Viewing Ethernet Device Status'' on page 709). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 122 Mediant 800B Gateway and E-SBC Note: You cannot delete an Ethernet Device that is associated with an IP network interface (in the Interface table). Only after the Ethernet Device has been disassociated from the IP network interface can it be deleted.
Page 123: Configuring Ip Network Interfaces
For configuring Quality of Service (QoS), see ''Configuring the QoS Settings'' on page 134.  Default Gateway: Traffic from this interface destined to a subnet that does not meet any of the routing rules (local or static) are forwarded to this gateway Version 6.8 Mediant 800B Gateway and E-SBC...
Page 124 Mediant 800B Gateway and E-SBC  Primary and secondary domain name server (DNS) addresses (optional)  Underlying Ethernet Device: Layer-2 bridging device and assigned a VLAN ID. As the Ethernet Device is associated with an Ethernet Port Group, this is useful for setting trusted and un-trusted networks on different physical Ethernet ports.
Page 125 Specifically, instead of using eight-bit address blocks, it uses the variable-length subnet masking technique to allow allocation on arbitrary-length prefixes. The prefix length for IPv4 must be set to a value from 0 to 30. The Version 6.8 Mediant 800B Gateway and E-SBC...
Page 126: Assigning Ntp Services To Application Types
Mediant 800B Gateway and E-SBC Parameter Description prefix length for IPv6 must be set to a value from 0 to 64. Web/EMS: Default Gateway Defines the IP address of the default gateway for the interface. CLI: gateway When traffic is sent from this interface to an unknown destination [InterfaceTable_Gateway] (i.e., not in the same subnet and not defined for any static routing...
Page 127: Networking Configuration Examples
201.201.0.0/16 to 192.168.11.10, and all traffic for subnet 202.202.0.0/16 to 192.168.11.1: Table 12-6: Example of Static Route Table Destination Prefix Length Gateway 201.201.0.0 192.168.11.10 202.202.0.0 192.168.11.1 The NTP applications remain with their default application types. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 128: Voip Interface Per Application Type
Mediant 800B Gateway and E-SBC 12.4.3.2 VoIP Interface per Application Type This example describes the configuration of three VoIP interfaces; one for each application type: Interface table: Configured with three interfaces, each for a different application type, i.e., one for OAMP, one for Call Control, and one for RTP Media, and each with a...
Page 129 For Gold Service class, the default DiffServ value is set to 26 ♦ For Bronze Service class, the default DiffServ value is set to 10 Figure 12-5: Example of Layer-2 QoS in DiffServ Table Version 6.8 Mediant 800B Gateway and E-SBC...
Page 130: Voip Interfaces With Multiple Default Gateways
Mediant 800B Gateway and E-SBC 12.4.3.4 VoIP Interfaces with Multiple Default Gateways Below is a configuration example using default gateways per IP network interface. In this example, the default gateway for OAMP is 192.168.0.1 and for Media and Control it is 200.200.85.1.
Page 131 'Destination' field is ignored. To reach a specific host, enter its IP address in the 'Destination' field and 32 in the 'Prefix Length' field. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 132: Configuration Example Of Static Ip Routes
Mediant 800B Gateway and E-SBC Parameter Description Gateway Defines the IP address of the Gateway (next hop) used for traffic CLI: gateway destined to the subnet/host defined in the 'Destination' / 'Prefix [StaticRouteTable_Gateway] Length' field. Notes:  The Gateway's address must be in the same subnet as the IP address of the network interface that is associated with the static route (using the 'Device Name' parameter - see above).
Page 133: Troubleshooting The Routing Table
To restore connectivity, the device must be accessed locally from the OAMP subnet and the required routes be configured. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 134: Configuring Quality Of Service
Mediant 800B Gateway and E-SBC 12.6 Configuring Quality of Service The QoS Settings page lets you configure Layer-2 and Layer-3 Quality of Service (QoS). Differentiated Services (DiffServ) is an architecture providing different types or levels of service for IP traffic. DiffServ (according to RFC 2474), prioritizes certain traffic types based on priority, accomplishing a higher-level QoS at the expense of other traffic types.
Page 135 Differentiated Services Defines a DiffServ value. CLI: diff-serv The valid value is 0 to 63. [DiffServToVlanPriority_DiffServ] VLAN Priority Defines the VLAN priority level. CLI: vlan-priority The valid value is 0 to 7. [DiffServToVlanPriority_VlanPriority] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 136: Configuring Icmp Messages
Mediant 800B Gateway and E-SBC Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS. Figure 12-8: QoS Settings Page - Differentiated Services 12.7 Configuring ICMP Messages Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol suite.
Page 137: Dns
Figure 12-10: Internal DNS Table - Add Record Dialog Box Configure the DNS rule, as required. For a description of the parameters, see the table below. Click Submit; the DNS rule is added to the table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 138: Configuring The Internal Srv Table
Mediant 800B Gateway and E-SBC Table 12-15: Internal DNS Table Parameter Description Parameter Description Domain Name Defines the host name to be translated. CLI: domain-name The valid value is a string of up to 31 characters. [Dns2Ip_DomainName] First IP Address...
Page 139 Weight (1-3) Defines a relative weight for records with the same priority. CLI: weight-1|2|3 [Srv2Ip_Weight1/2/3] Port (1-3) Defines the TCP or UDP port on which the service is to be found. CLI: port-1|2|3 [Srv2Ip_Port1/2/3] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 140: Open Solution Network (Osn) Server
Mediant 800B Gateway and E-SBC 12.9 Open Solution Network (OSN) Server This section describes various networking settings for the OSN server. Notes: • The OSN is a customer-ordered item. • For information on cabling the OSN, refer to the device's Hardware Installation Manual.
Page 141: Network Address Translation Support
If NAT is not configured by any of the above-mentioned methods, the device sends the packet according to its IP address configured in the Interface table. Note: The priority list above is applicable only to the Gateway calls. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 142: Configuring A Static Nat Ip Address For All Interfaces
Mediant 800B Gateway and E-SBC The figure below illustrates the NAT problem faced by the SIP networks where the device is located behind a NAT: Figure 12-12: Device behind NAT and NAT Issues 12.10.1.1 Configuring a Static NAT IP Address for All Interfaces You can configure a global (public) IP address of the router to enable static NAT between the device and the Internet for all network interfaces.
Page 143: Configuring Nat Translation Per Ip Interface
[NATTranslation_SourceIPInterfaceName] Target IP Address Defines the global IP address. This address is set in CLI: TargetIPAddress the SIP Via and Contact headers as well as in the o= [NATTranslation_TargetIPAddress] and c= SDP fields. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 144: Remote Ua Behind Nat
Mediant 800B Gateway and E-SBC Parameter Description Source Start Port Defines the optional starting port range (1-65536) of CLI: SourceStartPort the IP interface, used as matching criteria for this NAT [NATTranslation_SourceStartPort] rule. If not configured, the match is done on the entire port range.
Page 145: Media (Rtp/Rtcp/T.38)
NAT Is Not Used: (Default) NAT feature is disabled. The device considers the UA as not located behind NAT and always sends the media packets to the UA using the IP address:port obtained from the first received SIP message. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 146 Mediant 800B Gateway and E-SBC  NAT Is Used: NAT is always performed. The device considers the UA as located behind NAT and always sends the media packets to the UA using the source address obtained from the first media packet received from the UA. In this mode, the device does not send any packets until it receives the first packet from the UA (in order to obtain the IP address).
Page 147: Robust Receipt Of Media Streams By Media Latching
12. Network 12.11 Robust Receipt of Media Streams by Media Latching The Robust Media mechanism (or media latching) is an AudioCodes proprietary mechanism to filter out unwanted media (RTP, RTCP, SRTP, SRTCP, and T.38) streams that are sent to the same port number of the device. Media ports may receive additional multiple unwanted media streams (from multiple sources of traffic) as result of traces of previous calls, call control errors, or deliberate malicious attacks (e.g., Denial of Service).
Page 148 Mediant 800B Gateway and E-SBC If you have set the InboundMediaLatchMode parameter to 1 or 2, scroll down to the Robust Settings group and do the following: • Define the minimum number of continuous media (RTP, RTCP, SRTP, and SRTCP) packets that need to be received by the channel before it can latch onto this new incoming stream: ♦...
Page 149: Multiple Routers Support
Using multiple router support, the device can utilize these router messages to change its next hop and establish the best path. Note: Multiple Routers support is an integral feature that doesn’t require configuration. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 150 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 151: Security
If you are using the High Availability feature and you have configured "block" rules, ensure that you also add "allow" rules for HA traffic. For more information, see Configuring Firewall Allowed Rules on page 618. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 152 Mediant 800B Gateway and E-SBC The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList or the CLI command, configure voip/access-list.  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab >...
Page 153 CLI: network-interface-name This is applicable if you enabled the 'Use Specific Interface' field. [AccessList_Interface_x] The list displays interface names as defined in the Interface table in ''Configuring IP Network Interfaces'' on page 123. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 154 Mediant 800B Gateway and E-SBC Parameter Description Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment.
Page 155: Configuring General Security Settings
TLS all the way to the destination (over multiple hops), set the 'Enable SIPS' (EnableSIPS) parameter to Enable in the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 156: Intrusion Detection System
Mediant 800B Gateway and E-SBC 13.3 Intrusion Detection System The device's Intrusion Detection System (IDS) feature detects malicious attacks on the device and reacts accordingly. A remote host is considered malicious if it has reached or exceeded a user-defined threshold (counter) of specified malicious attacks.
Page 157: Enabling Ids
Open the IDS Policy Table page (Configuration tab > VoIP menu > Security > Intrusion Detection and Prevention > Policy Table); the table shows the pre- configured IDS policies: Figure 13-3: IDS Policy Table with Default Rules Version 6.8 Mediant 800B Gateway and E-SBC...
Page 158 Mediant 800B Gateway and E-SBC Click Add; the following dialog box appears: Figure 13-4: IDS Policy Table - Add Record Configure an IDS Policy name according to the parameters described in the table below. Click Submit. Table 13-3: IDS Policy Table Parameter Descriptions...
Page 159 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 563)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 160 Mediant 800B Gateway and E-SBC Parameter Description  [5] Abnormal flow =  Requests and responses without a matching transaction user (except ACK requests)  Requests and responses without a matching transaction (except ACK requests) Threshold Scope Defines the source of the attacker to consider in the device's CLI: threshold-scope detection count.
Page 161: Assigning Ids Policies
A hyphen "-" indicates a range of SIP Interfaces (e.g., 3,4-7 means IDs 3, and 4 through 7)  A prefix of an exclamation mark "!" means negation of the set (e.g., !3,4-7 means all indexes excluding 3, and excluding 4 through 7) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 162 Mediant 800B Gateway and E-SBC Parameter Description Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This CLI: proxy-set indicates the Proxy Sets from where the attacks are coming from. The [IDSMatch_ProxySet] following syntax is supported: ...
Page 163: Viewing Ids Alarms
To view the blacklist: # show voip security ids blacklist active For example: Active blacklist entries: 10.33.5.110(NI:0) remaining 00h:00m:10s in blacklist Where SI is the SIP Interface and NI is the network interface. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 164 Mediant 800B Gateway and E-SBC The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This only occurs if you have configured Syslog (see ''Enabling Syslog'' on page 751). An example of a Syslog message with IDS alarms and notifications is shown below:...
Page 165: Media
When silence is detected, it stops sending packets in the channel. The following procedure describes how to enable silence suppression using the Web interface. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 166: Echo Cancellation
Mediant 800B Gateway and E-SBC  To enable silence suppression using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 14-2: Enabling Silence Suppression in Voice Settings Page Set the 'Silence Suppression' (EnableSilenceCompression) field to Enable.
Page 167: Fax And Modem Capabilities
Some SIP parameters override these fax and modem parameters. For example, the IsFaxUsed parameter and V.152 parameters in Section ''V.152 Support'' on page 181. • For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 783. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 168 Mediant 800B Gateway and E-SBC  To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Configuration tab > VoIP menu > Media > Fax/Modem/CID Settings). Configure the parameters, as required. Click Submit. User's Manual Document #: LTRT-10620...
Page 169: Fax/Modem Operating Modes
You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Version 6.8 Mediant 800B Gateway and E-SBC...
Page 170 Mediant 800B Gateway and E-SBC Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders. 14.2.2.1.1 Switching to T.38 Mode using SIP Re-INVITE In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal...
Page 171 RTP method is used, whereby the device encapsulates the entire T.38 packet (payload with all its headers) in the sent RTP. For T.38 over RTP, AudioCodes devices use the proprietary identifier "AcUdptl" in the 'a=ftmp' line of the SDP. For example: o=AudiocodesGW 1357424688 1357424660 IN IP4 10.8.6.68...
Page 172: Fax / Modem Transport Mode
Mediant 800B Gateway and E-SBC 14.2.2.2 G.711 Fax / Modem Transport Mode In this mode, when the terminating device detects fax or modem signals (CED or AnsAM), it sends a Re-INVITE message to the originating device, requesting it to re-open the channel in G.711 VBD with the following adaptations:...
Page 173: Fax/Modem Bypass Mode
Configure the following optional parameters: • 'Fax/Modem Bypass Coder Type' (FaxModemBypassCoderType). • 'Fax Bypass Payload Type' (FaxBypassPayloadType) - in the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). • ModemBypassPayloadType (ini file). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 174: 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 175: Fax / Modem Transparent With Events Mode
Fax (IsFaxUsed = 0). In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 176: Rfc 2833 Ans Report Upon Fax/Modem Detection
Mediant 800B Gateway and E-SBC Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0).
Page 177: Bypass Mechanism For V.34 Fax Transmission
Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, V34FaxTransportType to 2 (Bypass). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 178: Relay Mode For T.30 And V.34 Faxes
Mediant 800B Gateway and E-SBC 14.2.3.2 Relay Mode for T.30 and V.34 Faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode.  To use T.38 mode for V.34 and T.30 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Relay (FaxTransportMode = 1).
Page 179 1938931006 1938930708 IN IP4 10.8.6.55 s=Phone-Call c=IN IP4 10.8.6.55 t=0 0 m=audio 6010 RTP/AVP 18 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 telephone-event/8000 a=fmtp:97 0-15 a=ptime:20 a=sendrecv m=image 6012 udptl t38 a=T38FaxVersion:3 a=T38MaxBitRate:33600 a=T38FaxMaxBuffer:1024 a=T38FaxMaxDatagram:122 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy Version 6.8 Mediant 800B Gateway and E-SBC...
Page 180: Modem Relay
Mediant 800B Gateway and E-SBC 14.2.4 V.150.1 Modem Relay The device can be configured to transfer modem calls using a subset of the ITU-T V.150.1 Modem Relay protocol. The device also supports V.150.1 modem relay coder negotiation in the initial SIP INVITE and 200 OK, using the SDP body according to the USA Department of Defense (DoD) UCR-2008, Change 2 specification.
Page 181: Simultaneous Negotiation Of Fax (T.38) And Modem (V.150.1) Relay
SDP ‘pmft’ attribute. Omission of this attribute in the SDP content means that VBD mode is the preferred transport mechanism for voice-band data. To configure T.38 mode, use the CodersGroup parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 182: Fax Transmission Behind Nat
Mediant 800B Gateway and E-SBC Note: You can also configure the device to handle G.711 coders received in INVITE SDP offers as VBD coders, using the HandleG711asVBD parameter. For example, if the device is configured with G.729 and G.711 VBD coders and it receives an INVITE with an SDP offer containing G.729 and “regular”...
Page 183: Configuring Rtp/Rtcp Settings
BFI packets simultaneously, so that the Jitter Buffer returns to its normal condition. The following procedure describes how to configure the jitter buffer using the Web interface. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 184: Comfort Noise Generation
Mediant 800B Gateway and E-SBC  To configure jitter buffer using the Web interface: Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). The relevant parameters are listed under the 'General Settings' group, as shown below:...
Page 185: Dual-Tone Multi-Frequency Signaling
INFO messages. To enable this mode, define the following: Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the '1st Tx DTMF Option' parameter to INFO (Cisco) (TxDTMFOption = 3). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 186: Configuring Rfc 2833 Payload
Mediant 800B Gateway and E-SBC Note: In this mode, DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF). Notes: • The device is always ready to receive DTMF packets over IP in all possible transport modes: INFO messages, NOTIFY, and RFC 2833 (in proper payload type) or as part of the audio stream.
Page 187: Configuring Rtp Base Udp Port
UDP port configured for a SIP Interface (see Configuring SIP Interfaces on page 274). For example, if your highest configured UDP port for a SIP Interface is 6060, you must configure the BaseUDPPort parameter to any value greater than 6060. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 188: Configuring Ip Media Settings
Mediant 800B Gateway and E-SBC 14.4 Configuring IP Media Settings This section describes the configuration of various IP media features. 14.4.1 Automatic Gain Control (AGC) Automatic Gain Control (AGC) adjusts the energy of the output signal to a required level (volume).
Page 189: Configuring Various Codec Attributes
General Media Settings). Figure 14-8: Codec Settings in General Media Settings Page Configure the parameters as required, and then click click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 626. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 190: Configuring Analog Settings
Mediant 800B Gateway and E-SBC 14.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 783. This page also selects the type (USA or Europe) of FXS and/or FXO coefficient information.
Page 191 Figure 14-10: Media Security Page Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 626. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 192 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 193: Services
Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Option 66 TFTP Server Name Version 6.8 Mediant 800B Gateway and E-SBC...
Page 194 Mediant 800B Gateway and E-SBC DHCP Option Code DHCP Option Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
Page 195 Defines the IP address (IPv4) of the NetBIOS WINS server CLI: netbios-server that is available to a Microsoft DHCP client. The value is sent [DhcpServer_NetbiosNameServer] in DHCP Option 44 (NetBIOS Name Server). The default value is 0.0.0.0. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 196 Mediant 800B Gateway and E-SBC Parameter Description Web: NetBIOS Node Type Defines the node type of the NetBIOS WINS server for a CLI: netbios-node-type Microsoft DHCP client. The value is sent in DHCP Option 46 [DhcpServer_NetbiosNodeType] (NetBIOS Node Type). ...
Page 197: Configuring The Vendor Class Identifier
The VCI is a string that identifies the vendor and functionality of a DHCP client to the DHCP server. For example, Option 60 can show the unique type of hardware (e.g., "AudioCodes 440HD IP Phone") or firmware of the DHCP client. The DHCP server can then differentiate between DHCP clients and process their requests accordingly.
Page 198: Configuring Additional Dhcp Options
Mediant 800B Gateway and E-SBC Click Add; the following dialog box appears: Figure 15-2: DHCP Vendor Class Table - Add Record Dialog Box Configure a VCI for the DHCP server according to the parameters described in the table below. Click Submit.
Page 199  [1] IP address = IPv4 address.  [2] Hexadecimal = Hexadecimal-encoded string. For example, if you set the 'Value' parameter to "company.com", you need to set the 'Type' parameter to ASCII. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 200: Configuring Static Ip Addresses For Dhcp Clients
Mediant 800B Gateway and E-SBC Parameter Description Web: Value Defines the value of the DHCP Option. For example, if you are CLI: value using Option 66, this parameter is used for specifying the TFTP [DhcpOption_Value] provisioning server (e.g., http://192.168.3.155:5000/provisioning/). The valid value is a string of up to 256 characters. By default, no value is defined.
Page 201: Viewing And Deleting Dhcp Clients
# show voip dhcp clients  To view DHCP clients according to IP address: # show voip dhcp ip  To view DHCP clients according to MAC address: # show voip dhcp mac Version 6.8 Mediant 800B Gateway and E-SBC...
Page 202 Mediant 800B Gateway and E-SBC  To view DHCP clients that have been blacklisted from DHCP implementation (due to duplicated IP addresses in the network, where another device is using the same IP address as the one assigned to the client): # show voip dhcp black-list ...
Page 203: Sip-Based Media Recording
Session (RS) from the Session Recording Client (SRC), which is on the path of the Communication Session (CS), to a Session Recording Server (SRS) at the recording equipment. The device functions as the SRC, sending recording sessions to a third-party SRS, as shown in the figure below. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 204 Mediant 800B Gateway and E-SBC The device can record calls between two IP Groups. The type of calls to record can be specified by source and/or destination prefix number or SIP Request-URI, as well as by call initiator. The side ("leg") on which the recording is done must be specified. Specifying the leg is important as it determines the various call media attributes of the recorded RTP (or SRTP) such as coder type.
Page 205 0-15 m=audio 6030 RTP/AVP 8 96 c=IN IP4 10.33.8.70 a=ptime:20 a=sendonly a=label:2 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 --boundary_ac1fffff85b Content-Type: application/rs-metadata Content-Disposition: recording-session <?xml version="1.0" encoding="UTF-8"?> <recording xmlns='urn:ietf:params:xml:ns:recording'> <datamode>complete</datamode> <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> Version 6.8 Mediant 800B Gateway and E-SBC...
Page 206: Enabling Sip-Based Media Recording
Mediant 800B Gateway and E-SBC </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>1</label> </stream>...
Page 207 Defines which calls to record according to which CLI: caller party is the caller. [SIPRecRouting_Caller]  [0] Both (default) = Caller can be peer or recorded side  [1] Recorded Party  [2] Peer Party Version 6.8 Mediant 800B Gateway and E-SBC...
Page 208 Mediant 800B Gateway and E-SBC Parameter Description Recording Server (SRS) IP Group ID Defines the IP Group of the recording server CLI: srs-ip-group-id (SRS). [SIPRecRouting_SRSIPGroupID] Note: The SIP Interface used for communicating with the SRS is according to the SRD assigned to the SRS IP Group (in the IP Group table).
Page 209: Configuring Sip User Part For Srs
SIP message, typically in the INVITE and the first 18x response. If the device receives a SIP message with Genesys SIP header, it adds the header's information to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server, as shown below: <ac:GenesysUUID...
Page 210: Avaya Ucid
If the device receives a SIP INVITE from Avaya, it adds the UCID value, received in the User-to-User SIP header to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server. For example, if the received SIP header is: User-to-User: 00FA080019001038F725B3;encoding=hex...
Page 211: Radius Authentication
Set up a RADIUS server (third-party) to communicate with the device - see 'Setting Up a Third-Party RADIUS Server' on page  Configure the device as a RADIUS client for communication with the RADIUS server - see 'Configuring RADIUS Authentication' on page Version 6.8 Mediant 800B Gateway and E-SBC...
Page 212: Setting Up A Third-Party Radius Server
 To set up a third-party RADIUS server (e.g., FreeRADIUS): Define the AudioCodes device as an authorized client of the RADIUS server, with the following: • Predefined shared secret (password used to secure communication between the device and the RADIUS server) •...
Page 213: Configuring Radius Authentication
If the RADIUS server response does not include the access level attribute: In the 'Default Access Level' field, enter the default access level that is applied to all users authenticated by the RADIUS server. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 214: Securing Radius Communication
Mediant 800B Gateway and E-SBC Configure RADIUS timeout handling: From the 'Behavior upon Authentication Server Timeout' drop-down list, select the option if the RADIUS server does not respond within five seconds: ♦ Deny Access: device denies user login access. ♦...
Page 215: Ldap-Based Management And Sip Services
The device then assigns the user the access level configured for that group (in 'Configuring Access Level per Management Groups Attributes' on page 222). The location in the directory where you want to search for the user's member group(s) is configured using the following: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 216: Enabling The Ldap Service
Mediant 800B Gateway and E-SBC • Search base object (distinguished name or DN, e.g., "ou=ABC,dc=corp,dc=abc,dc=com"), which defines the location in the directory from where the LDAP search begins, and is configured in 'Configuring LDAP DNs (Base Paths) per LDAP Server' on page 220.
Page 217: Enabling Ldap-Based Web/Cli User Login Authentication And Authorization
Open the LDAP Configuration Table page (Configuration tab > VoIP menu > Services > LDAP > LDAP Configuration Table). Click Add; the following dialog box appears: Figure 15-11: LDAP Configuration Table - Add Record Version 6.8 Mediant 800B Gateway and E-SBC...
Page 218 Mediant 800B Gateway and E-SBC Configure an LDAP server according to the parameters described in the table below. Click Submit. LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [LdapConfiguration_In Note: Each table row must be configured with a unique index.
Page 219 (i.e., the 'Type' parameter is set to Management).  If this functionality is not used, the device assigns the user the configured default access level. For more information, see 'Configuring Access Level per Management Groups Attributes' on page 222. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 220: Configuring Ldap Dns (Base Paths) Per Ldap Server
Mediant 800B Gateway and E-SBC Parameter Description Use SSL Enables the device to encrypt the username and password (for Control CLI: and Management related queries) using TLS when sending them to the [LdapConfiguration_us LDAP server. eTLS]  [0] No = (Default) Username and password are sent in clear-text format.
Page 221: Configuring The Ldap Search Filter Attribute
To configure the LDAP search filter for management users: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 15-13: LDAP Settings Page - LDAP Search Filter Version 6.8 Mediant 800B Gateway and E-SBC...
Page 222: Configuring Access Level Per Management Groups Attributes
Mediant 800B Gateway and E-SBC Under LDAP Settings, in the 'LDAP Authentication Filter' parameter, enter the LDAP search filter attribute for searching the login username for user authentication. Click Submit. 15.4.6 Configuring Access Level per Management Groups Attributes The Management LDAP Groups table lets you configure LDAP group objects and their corresponding management user access level.
Page 223 Defines the attribute names of the groups in the LDAP server. [MgmntLDAPGroups_ The valid value is a string of up to 256 characters. To define multiple Group] groups, separate each group name with a semicolon (;). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 224: Configuring Ldap Search Methods
Mediant 800B Gateway and E-SBC 15.4.7 Configuring LDAP Search Methods You can configure the device's method for searching the LDAP server(s) for the configured DN objects:  DN Search Method between Two LDAP Servers: When two LDAP servers are implemented, the device runs an LDAP query to search for DN object records on both LDAP servers.
Page 225: Configuring The Device's Ldap Cache
Improves routing decision performance by using local cache for subsequent LDAP queries  Reduces number of queries performed on an LDAP server and corresponding bandwidth consumption  Provides partial survivability in case of intermittent LDAP server failure (or network isolation) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 226 Mediant 800B Gateway and E-SBC The handling of LDAP queries with the LDAP cache is shown in the flowchart below: Figure 15-16: LDAP Query Process with Local LDAP Cache Note: If for the first LDAP query, the result fails for at least one attribute and is successful for at least one, the partial result is cached.
Page 227: Configuring Local Database For Management User Authentication
Web Users table. To configure local Web/CLI users in the Web Users table, see Configuring Web User Accounts. Notes: • This feature is applicable to LDAP and RADIUS servers. • This feature is applicable only to user management authentication. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 228 Mediant 800B Gateway and E-SBC  To use the Web Users table for authenticating management users: Open the Authentication Settings page (Configuration tab > System menu > Management > Authentication Settings). Figure 15-18: Authentication Settings Page - Local Database for Login Authentication Under General Login Authentication Settings: •...
Page 229: Ldap-Based Login Authentication Example
The LDAP server's entry data structure schema in the example is as follows:  DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: Figure 15-19: Base Path (DN) in LDAP Server Version 6.8 Mediant 800B Gateway and E-SBC...
Page 230 Mediant 800B Gateway and E-SBC  Search Attribute Filter: (sAMAccountName=$). The login username is found based on this attribute (where the attribute's value equals the username): Figure 15-20: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the...
Page 231 The search attribute filter based on username is configured by the 'LDAP Authentication Filter' parameter in the LDAP Settings page (see 'Configuring the LDAP Search Filter Attribute' on page 221): Figure 15-24: Configuring Search Attribute Filter Version 6.8 Mediant 800B Gateway and E-SBC...
Page 232 Mediant 800B Gateway and E-SBC  The group management attribute is configured by the 'Management Attribute' parameter in the LDAP Configuration table: Figure 15-25: Configuring Management Attribute  The management group and its corresponding access level is configured in the...
Page 233: Active Directory-Based Routing For Microsoft Lync
Primary or Secondary key. MSLDAPPrimaryKey Primary Key query search instead of PBX msRTCSIP-PrivateLine= key - can be any AD attribute +3233554480 MSLDAPSecondaryKey Secondary Key query key search if Primary Key fails - can be any attribute Version 6.8 Mediant 800B Gateway and E-SBC...
Page 234 Mediant 800B Gateway and E-SBC The process for querying the AD and subsequent routing based on the query results is as follows: If the Primary Key is configured, it uses the defined string as a primary key instead of the one defined in MSLDAPPBXNumAttributeName. It requests the attributes which are described below.
Page 235 Figure 15-27: 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.8 Mediant 800B Gateway and E-SBC...
Page 236: Configuring Ad-Based Routing Rules
Mediant 800B Gateway and E-SBC 15.4.11.2 Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries.  To configure LDAP-based IP routing for Lync Server: Configure the LDAP server parameters, as described in 'Configuring LDAP Servers' on page 217.
Page 237 AD query result for the Lync attribute.  Rule 4: Sends call to user's mobile phone number (to PSTN through the device's IP address at 10.33.45.100) upon successful AD query result for the Mobile attribute. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 238: Querying The Ad For Calling Name
Mediant 800B Gateway and E-SBC  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).  Rule 6: Sends query for original destination number of received call to the LDAP server.
Page 239: Least Cost Routing
This example shows four defined Cost Groups and the total call cost if the average call duration is 10 minutes: Table 15-7: Call Cost Comparison between Cost Groups for different Call Durations Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes 80.3 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 240 Mediant 800B Gateway and E-SBC Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes If four matching routing rules are located in the routing table and each one is assigned a different Cost Group as listed in the table above, then the rule assigned Cost Group "D" is selected.
Page 241: Configuring Lcr
The Routing Rule Groups table lets you enable the LCR feature. This also includes configuring the average call duration and default call cost for routing rules that are not assigned Cost Groups in the Outbound IP Routing table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 242 Mediant 800B Gateway and E-SBC The following procedure describes how to enable LCR in the Web interface. You can also do this using the table ini file parameter, RoutingRuleGroups or CLI command, configure voip > services least-cost-routing routing-rule-groups.  To enable LCR: Open the Routing Rule Groups Table page (Configuration tab >...
Page 243: Configuring Cost Groups
Cost Group Name Defines an arbitrary name for the Cost Group. CLI: cost-group-name The valid value is a string of up to 30 characters. [CostGroupTable_CostGroupNam Note: Each Cost Group must have a unique name. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 244: Configuring Time Bands For Cost Groups
Mediant 800B Gateway and E-SBC Parameter Description Default Connection Cost Defines the call connection cost (added as a fixed charge to CLI:default-connection-cost the call) for a call outside the time bands. [CostGroupTable_DefaultConnecti The valid value range is 0-65533. The default is 0.
Page 245: Assigning Cost Groups To Routing Rules
To use your configured Cost Groups, you need to assign them to routing rules:  Gateway application: Outbound IP Routing table - see Configuring Outbound IP Routing Table on page  SBC application: IP-to-IP Routing table - see Configuring SBC IP-to-IP Routing Rules on page Version 6.8 Mediant 800B Gateway and E-SBC...
Page 246: Configuring Call Setup Rules
Mediant 800B Gateway and E-SBC 15.6 Configuring Call Setup Rules The Call Setup Rules table lets you configure up to 40 Call Setup rules. Call Setup rules define various sequences that are run upon the receipt of an incoming call (dialog) at call setup, before the device routes the call to its destination.
Page 247 10 rules. The Set ID is used to assign the Call Setup rules to a routing rule in the routing table. The valid value is 0 to 9. The default is 0. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 248 Mediant 800B Gateway and E-SBC Parameter Description Attributes To Query Defines the query string that the device sends to the LDAP CLI: attr-to-query server. [CallSetupRules_AttributesToQuery] The valid value is a string of up to 100 characters. Combined strings and values can be configured like in the Message Manipulations table, using the '+' operator.
Page 249 The valid value is a string of up to 300 characters (case- [CallSetupRules_ActionValue] insensitive). Examples:  '+9723976'+ldap.attr.alternateNumber  '9764000'  ldap.attr.displayName  true (if the 'Action Type' is set to Exit)  false (if the 'Action Type' is set to Exit) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 250: Call Setup Rule Examples
Mediant 800B Gateway and E-SBC 15.6.1 Call Setup Rule Examples Below are configuration examples for using Call Setup Rules.  Example 1: This example configures the device to replace (manipulate) the incoming call's source number with a number retrieved from the AD by an LDAP query. The device queries the AD server for the attribute record, "telephoneNumber"...
Page 251 ♦ Index 1:  'Call Setup Rules Set Id': 3  'Destination IP Group ID': 3 (IP Group for Lync) ♦ Index 2:  'Destination IP Group ID': 4 (IP Group of PBX) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 252 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 253: Quality Of Experience
The device can be configured to report voice (media) Quality of Experience (QoE) to AudioCodes' Session Experience Manager (SEM) server, a plug-in for AudioCodes EMS. The reports include real-time metrics of the quality of the actual call experience, which are then processed by the SEM.
Page 254: Configuring Clock Synchronization Between Device And Sem
In other words, you need to configure them with the same NTP server. The NTP server can be one of the following:  AudioCodes EMS server (also acting as an NTP server)  Third-party, external NTP server Once you have determined the NTP server, all the elements--device, SEM, and EMS--must be configured with the same NTP server address.
Page 255  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 254.
Page 256 Mediant 800B Gateway and E-SBC Table 16-1: Quality of Experience Profile Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [QOEProfile_Index] Profile Name Defines an arbitrary name to easily identify the QoE Profile. CLI: name The valid value is a string of up to 20 characters.
Page 257 SEM indicating this wHysteresis] change. Note: If the monitored parameter crosses two thresholds at once (e.g., from Green to Red), the device ignores the hysteresis value and reports the call state change to the SEM. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 258: Configuring Bandwidth Profiles
Mediant 800B Gateway and E-SBC Parameter Description Yellow Red Threshold Defines the parameter threshold values between Yellow (medium CLI: yellow-red-threshold quality) and Red (poor quality) states. [QOEColorRules_YellowRedT The valid threshold values are as follows: hreshold]  MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.
Page 259 Defines the outgoing audio traffic threshold (in Kbps). CLI: egress-audio-bandwidth [BWProfile_EgressAudioBandwidth] Ingress Audio Bandwidth Defines the incoming audio traffic threshold (in Kbps). CLI: ingress-audio-bandwidth [BWProfile_IngressAudioBandwidth] Egress Video Bandwidth Defines the outgoing video traffic threshold (in Kbps). CLI: egress-video-bandwidth [BWProfile_EgressVideoBandwidth] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 260 Mediant 800B Gateway and E-SBC Parameter Description Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). CLI: ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth CLI: total-egress-bandwidth threshold (in Kbps). [BWProfile_TotalEgressBandwidth] Total Ingress Bandwidth...
Page 261: Configuring Media Enhancement Profiles
 Media Enhancement Profile table: Table ini file parameter, MediaEnhancementProfile or CLI command, configure voip/qoe media-enhancement  Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules or CLI command, configure voip/qoe media-enhancement-rules Version 6.8 Mediant 800B Gateway and E-SBC...
Page 262 Mediant 800B Gateway and E-SBC  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Click Add; the following dialog box appears: Figure 16-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below.
Page 263 Defines an alternative IP Profile ID for the IP Group that CLI: value is associated with this rule, if this rule is applied. This [MediaEnhancementRules_ActionValue] parameter is applicable only if the 'Rule Action' parameter is set to Alternative IP Profile. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 264 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 265: Control Network
The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm or CLI command, configure voip/voip-network realm. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 266 Mediant 800B Gateway and E-SBC  To configure a Media Realm: Open the Media Realm Table page (Configuration tab > VoIP menu > VoIP Network > Media Realm Configuration). Click Add; the following dialog box appears: Figure 17-1: Media Realm Page - Add Record Dialog Box Configure the Media Realm according to the parameters described in the table below.
Page 267 If the table is not configured, the default Media Realm includes all the configured media interfaces. QoE Profile Assigns a QoE Profile to the Media Realm. For configuring CLI: qoe-profile QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 254. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 268 Mediant 800B Gateway and E-SBC Parameter Description BW Profile Assigns a Bandwidth Profile to the Media Realm. For CLI: bw-profile configuring Bandwidth Profiles, see ''Configuring Bandwidth [CpMediaRealm_BWProfile] Profiles'' on page 258. User's Manual Document #: LTRT-10620...
Page 269: Configuring Remote Media Subnets
Select the Media Realm index row for which you want to add Remote Media Subnets, and then click the Remote Media Subnet link located below the table; the Remote Media Subnet table appears. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 270 Mediant 800B Gateway and E-SBC Click Add; the following dialog box appears: Figure 17-3: Remote Media Subnet - Add Record Configure the Remote Media Subnet according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
Page 271: Configuring Srds
SBC application) The following procedure describes how to configure SRDs in the Web interface. You can also configure this using the table ini file parameter, SRD or CLI command, configure voip > voip-network srd. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 272 Mediant 800B Gateway and E-SBC  To configure an SRD: Open the SRD Table page (Configuration tab > VoIP menu > VoIP Network > SRD Table). Click Add; the following dialog box appears: Figure 17-4: SRD Settings Page Configure an SRD according to the parameters described in the table below.
Page 273 Note: Regardless of the parameter, the device always accepts registration refreshes from users that are already registered in its database. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 274: Configuring Sip Interfaces
Mediant 800B Gateway and E-SBC 17.4 Configuring SIP Interfaces The SIP Interface table lets you configure up to 32 SIP Interfaces. A SIP Interface defines a listening port and type (UDP, TCP, or TLS) for SIP signaling traffic on a specific logical IP network interface (configured in the Interface table).
Page 275 This port must be outside of the RTP port range.  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 276 Mediant 800B Gateway and E-SBC Parameter Description Assigns an SRD ID to the SIP Interface (configured in ''Configuring CLI: srd SRDs'' on page 271). [SIPInterface_SRD] The default is 0. Notes:  You can assign the same SRD ID to up to two SIP Interfaces of the same application type.
Page 277 If both the SIP Interface and IP Group associated with the incoming call are assigned a Message Manipulation Set, the one assigned to the SIP Interface is applied first.  This parameter is applicable only to SBC calls. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 278: Configuring Ip Groups
Mediant 800B Gateway and E-SBC 17.5 Configuring IP Groups The IP Group table lets you configure up to 50 IP Groups. An IP Group represents a SIP entity in the network with which the device communicates. This can be a server (e.g., IP PBX or ITSP) or it can be a group of users (e.g., LAN IP phones).
Page 279 Figure 17-5: IP Group Table - Add Dialog Box Configure an IP Group according to to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 280 Mediant 800B Gateway and E-SBC Table 17-5: IP Group Table Parameter Descriptions Parameter Description Common Parameters Index Defines an index for the new table record. [IPGroup_Index] Type Defines the type of IP Group: CLI:type  [0] Server = Used when the destination address, configured by the [IPGroup_Type] Proxy Set, of the IP Group (e.g., ITSP, Proxy, IP-PBX, or...
Page 281 IP Group. Notes:  This parameter is applicable only to Server-type IP Groups.  This parameter is overridden by the ‘Contact User’ parameter in the ‘Account’ table (see ''Configuring Registration Accounts'' on page 297). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 282 Mediant 800B Gateway and E-SBC Parameter Description Assigns an SRD to the IP Group. CLI: srd The default is 0. [IPGroup_SRD] Notes:  For this parameter to take effect, a device reset is required.  To configure SRDs, see Configuring SRDs on page 271.
Page 283 [-1] Not Configured = (Default) The routing is according to the [IPGroup_RoutingMode] selected Serving IP Group. If no Serving IP Group is selected, the device routes the call according to the Outbound IP Routing table Version 6.8 Mediant 800B Gateway and E-SBC...
Page 284 Mediant 800B Gateway and E-SBC Parameter Description (see Configuring Outbound IP Routing Table on page 411).  [0] Routing Table = The device routes the call according to the Outbound IP Routing table.  [1] Serving IP Group = The device sends the SIP INVITE to the selected Serving IP Group.
Page 285 IP address, but also with SIP message characteristics to increase the strictness of the classification process (see Configuring Classification Rules on page 563). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 286 Mediant 800B Gateway and E-SBC Parameter Description The reason for preferring classification based on Proxy Set when the IP address is unknown is that IP address forgery (commonly known as IP spoofing) is more difficult than malicious SIP message tampering and therefore, using a Classification rule without an IP address offers a weaker form of security.
Page 287 URIs. [IPGroup_SourceUriInput]  [-1] Not Configured (default)  [0] From  [1] To  [2] Request-URI  [3] P-Asserted - First Header  [4] P-Asserted - Second Header Version 6.8 Mediant 800B Gateway and E-SBC...
Page 288 Mediant 800B Gateway and E-SBC Parameter Description  [5] P-Preferred  [6] Route  [7] Diversion  [8] P-Associated-URI  [9] P-Called-Party-ID  [10] Contact  [11] Referred-by Notes:  This parameter is applicable only when classification is done according to the Classification table.
Page 289 'Authentication Mode' parameter is set to SBC as Server (i.e., authentication of servers).  To specify the SIP request types (e.g., INVITE) that must be challenged by the device, use the 'Authentication Method List' parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 290: Configuring Proxy Sets
Mediant 800B Gateway and E-SBC 17.6 Configuring Proxy Sets The Proxy Sets table lets you configure up to 50 Proxy Sets. A Proxy Set defines the destination address (IP address or FQDN) and transport type (e.g., UDP) of a SIP server (e.g., Proxy).
Page 291 CLI: voip-network proxy-ip >  [0] UDP transport-type  [1] TCP [ProxyIp_TransportType]  [2] TLS  [-1] = Undefined Note: If this parameter is not defined, the settings of the global parameter SIPTransportType is used. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 292 Mediant 800B Gateway and E-SBC Parameter Description Proxy Name Defines an arbitrary name to easily identify the Proxy Set. CLI: proxy-name The valid value is a string of up to 20 characters. [ProxySet_ProxyName] DNS Resolve Method Defines the DNS query record type for resolving the Proxy server's CLI: dns-resolve-method host name into an IP address.
Page 293 Proxy server to is-proxy-hot-swap redundant Proxies when no response is received from the primary. [ProxySet_IsProxyHotSwap]  [0] No (default)  [1] Yes = The device sends the SIP INVITE/REGISTER message Version 6.8 Mediant 800B Gateway and E-SBC...
Page 294 Mediant 800B Gateway and E-SBC Parameter Description to the first address (Proxy/Registrar server) listed in the Proxy Set. If a SIP response is received and this response code is defined in the 'Keep Alive Failure Response' parameter (above), the device assumes the Proxy as down and sends the message again;...
Page 295 UDP, the device uses UDP to communicate with the proxy and no TLS Context is used. For more information about how certificates are associated with calls and for configuring TLS Contexts, see Configuring SSL/TLS Certificates on page 97. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 296 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 297: Sip Definitions
'UserName' and 'Password' parameters on the Proxy & Registration page The following procedure describes how to configure Accounts in the Web interface. You can also configure Accounts using the table ini file parameter, Account or CLI command, configure voip > sip-definition account. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 298 Mediant 800B Gateway and E-SBC  To configure an Account: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Configure an account according to the parameters described in the table below.
Page 299 If this parameter is not configured, the 'Contact User' parameter in the IP Group table is used instead.  If registration fails, the user part in the INVITE Contact header contains the source party number. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 300: Regular Registration Mode
Mediant 800B Gateway and E-SBC Parameter Description Application Type Defines the application type: CLI: application-type  [0] GW/IP2IP = (Default) Gateway and IP-to-IP application. [Account_ApplicationType]  [2] SBC = SBC application. 18.2.1 Regular Registration Mode When you configure the registration mode in the Account table to Regular, the device sends REGISTER requests to the Serving IP Group.
Page 301: Configuring Proxy And Registration Parameters
For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 783. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Endpoint Registration Status on page 714. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 302 Mediant 800B Gateway and E-SBC  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Configure the parameters as required. Click Submit.  To register or un-register the device to a Proxy/Registrar: ...
Page 303: 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 304 At this time, a new REGISTER request is issued with the following response: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c23940 To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 Server: Audiocodes-Sip-Gateway/Mediant 800B Gateway and E- SBC/v.6.60.010.006 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, username: 122, realm="audiocodes.com”,...
Page 305: Configuring Sip Message Manipulation
P-Asserted-Identity header can be copied to the From header), call's parameter values  Deletion of SIP body (e.g., if a message body is not supported at the destination network this body is removed)  Translating one SIP response code to another Version 6.8 Mediant 800B Gateway and E-SBC...
Page 306 Mediant 800B Gateway and E-SBC  Topology hiding (generally present in SIP headers such as Via, Record Route, Route and Service-Route).  Configurable identity hiding (information related to identity of subscribers, for example, P-Asserted-Identity, Referred-By, Identity and Identity-Info)  Apply conditions per rule - the condition can be on parts of the message or call’s parameters ...
Page 307 Figure 18-3: Message Manipulations Table - Add Record Dialog Box Configure a Message Manipulation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 308 Mediant 800B Gateway and E-SBC An example of configured message manipulation rules are shown in the figure below: Figure 18-4: Message Manipulations Page  Index 0: Adds the suffix ".com" to the host part of the To header.  Index 1: Changes the user part of the From header to the user part of the P-Asserted- ...
Page 309 > '3600'  header.to.url.host contains 'domain'  param.call.dst.user != '100' Operation Action Subject Defines the SIP header upon which the manipulation is performed. CLI: action-subject The valid value is a string (case-insensitive). [MessageManipulations_Act ionSubject] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 310 Mediant 800B Gateway and E-SBC Parameter Description Action Type Defines the type of manipulation. CLI: action-type  [0] Add (default) = Adds new header/param/body (header or [MessageManipulations_Act parameter elements). ionType]  [1] Remove = Removes header/param/body (header or parameter elements).
Page 311: Configuring Sip Message Policy Rules
Figure 18-5: Message Policy Table - Add Record Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 312 Mediant 800B Gateway and E-SBC Table 18-3: Message Policy Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [MessagePolicy_Index] Max Message Length Defines the maximum SIP message length. CLI: max-message-length The valid value is up to 32,768 characters. The default is [MessagePolicy_MaxMessageLength] 32,768.
Page 313 'Body List' parameter (above). [MessagePolicy_BodyListType]  [0] Policy Blacklist =The specified SIP body is rejected.  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; the others are rejected. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 314 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 315: Coders And Profiles
To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Configure coders according to the parameters described in the table below. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 316 Mediant 800B Gateway and E-SBC Click Submit, and then reset the device with a save ("burn") to flash memory. Table 19-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder. CLI: name Note: Each coder type (e.g., G.729) can be configured only once [CodersGroup0_Name] in the table.
Page 317 Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 T.38 [t38fax] T.38 Version 3 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 318: Configuring Coder Groups
Mediant 800B Gateway and E-SBC 19.2 Configuring Coder Groups The Coder Group Settings table lets you configure up to 10 Coder Groups. A Coder Group is a set of configured coders (coder type, packetization time, rate, payload type, and silence suppression). Each Coder Group can include up to 10 coders.
Page 319: Configuring Tel Profile
Trunk Group Table (see Configuring Trunk Group Table on page 379)). The following procedure describes how to configure Tel Profiles in the Web interface. You can also configure Tel Profiles using the table ini file parameter, TelProfile or CLI command, configure voip/coders-and-profiles tel-profile. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 320 Mediant 800B Gateway and E-SBC  To configure a Tel Profile: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > Tel Profile Settings). Click Add; the following dialog box appears: Configure a Tel Profile according to the parameters described in the table below. For a description of each parameter, refer to the corresponding "global"...
Page 321 Web: Dynamic Jitter Buffer Optimization Factor DJBufOptFactor CLI: jitter-buffer-optimization-factor [TelProfile_JitterBufOptFactor] Web: DTMF Volume DTMFVolume CLI: dtmf-volume [TelProfile_DtmfVolume] Web: Input Gain InputGain CLI: input-gain [TelProfile_InputGain] Web: Voice Volume VoiceVolume CLI: voice-volume [TelProfile_VoiceVolume] Web: Echo Canceler EnableEchoCanceller CLI: echo-canceller [TelProfile_EnableEC] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 322 Mediant 800B Gateway and E-SBC Tel Profile Parameter Global Parameter Web: Enable AGC EnableAGC CLI: enable-agc [TelProfile_EnableAGC] Web: EC NLP Mode ECNLPMode CLI: echo-canceller-nlp-mode [TelProfile_ECNlpMode] Analog Web: Enable Polarity Reversal EnableReversalPolarity CLI: polarity-rvrsl [TelProfile_EnableReversePolarity] Web: Enable Current Disconnect EnableCurrentDisconnect CLI: current-disconnect...
Page 323: Configuring Ip Profiles
> coders-and-profiles ip-profile.  To configure an IP Profile: Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 324 Mediant 800B Gateway and E-SBC Configure an IP Profile according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 19-5: IP Profile Settings Table Parameter Descriptions Parameter Description Common Web: Index Defines an index number for the new table record.
Page 325 This parameter is set to Enable Without Adaptation [2] and IsCiscoSCEMode to [0]: 'annexb=yes'  Enable Without Adaptation is set to Enable Without Adaptation [2] and IsCiscoSCEMode to [1]: 'annexb=no'  The corresponding global parameter is EnableSilenceCompression. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 326 Mediant 800B Gateway and E-SBC Parameter Description Web: RTP Redundancy Depth Enables the device to generate RFC 2198 redundant CLI: rtp-redundancy-depth packets. This can be used for packet loss where the [IpProfile_RTPRedundancyDepth] missing information (audio) can be reconstructed at the receiver's end from the redundant data that arrives in subsequent packets.
Page 327 MKI value according to the selected crypto line in the offer. For example, assume that the device receives an INVITE containing the following two crypto lines in SDP: a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:TAaxNnQt8/qLQMnDuG4vxYfWl6K7eBK/uf k04pR4|2^31|1:1 a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:bnuYZnMxSfUiGitviWJZmzr7OF3AiRO0l5 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 328 Mediant 800B Gateway and E-SBC Parameter Description Vnh0kH|2^31 The first crypto line includes the MKI parameter "1:1". In the 200 OK response, the device selects one of the crypto lines (i.e., '2' or '3'). Typically, it selects the first line that supports the crypto suite. However, for SRTP- to-SRTP in SBC sessions, it can be determined by the remote side on the outgoing leg.
Page 329 To completely disable T.38, set FaxTransportMode to a value other than 1.  For more information on fax transport methods, see Fax/Modem Transport Modes on page 169. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 330 Mediant 800B Gateway and E-SBC Parameter Description  The corresponding global parameter is IsFaxUsed. Web: CNG Detector Mode Enables the detection of the fax calling tone (CNG) and CLI: cng-mode defines the detection method. [IpProfile_CNGmode]  [0] Disable = (Default) The originating fax does not detect CNG;...
Page 331 Enables the Early Media feature for sending media (e.g., CLI: early-media ringing) before the call is established. [IpProfile_EnableEarlyMedia]  [0] Disable (default)  [1] Enable  Digital: The device sends a SIP 18x response with Version 6.8 Mediant 800B Gateway and E-SBC...
Page 332 Mediant 800B Gateway and E-SBC Parameter Description SDP, allowing the media stream to be established before the call is answered.  Analog: The device sends a SIP 183 Session Progress response with SDP instead of a 180 Ringing, allowing the media stream to be established before the call is answered.
Page 333 SIP entity that don't include encryption information.  [2] Disable = This SIP entity does not support encrypted calls (i.e., SRTP).  [3] Preferable - Single Media = The device sends SDP Version 6.8 Mediant 800B Gateway and E-SBC...
Page 334 Mediant 800B Gateway and E-SBC Parameter Description with a single media ('m=') line only (e.g., m=audio 6000 RTP/AVP 4 0 70 96) with RTP/AVP and crypto keys. The SIP entity can respond with SRTP or RTP parameters:  If the SIP entity does not support SRTP, it uses RTP and ignores the crypto lines.
Page 335 Euro ISDN), set the EnableHold2ISDN parameter to 1.  Analog interfaces: To use the call hold service, the devices at both ends must support this option.  The corresponding global parameter is EnableHold. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 336 Mediant 800B Gateway and E-SBC Parameter Description Web: Add IE In Setup Defines an optional Information Element (IE) data (in hex CLI: add-ie-in-setup format) which is added to ISDN Setup messages. For [IpProfile_AddIEInSetup] example, to add IE '0x20,0x02,0x00,0xe1', enter the value "200200e1".
Page 337 SIP entity (as both legs have different media capabilities), by implementing DSP transcoding. This enables the device to receive capabilities that are not negotiated between the SIP entities. For example, it can enforce Gain Control to use voice transcoding Version 6.8 Mediant 800B Gateway and E-SBC...
Page 338 Mediant 800B Gateway and E-SBC Parameter Description even though both legs have negotiated without the device's intervention (such as Extension coders). Notes:  To implement transcoding, you must configure the number of required DSP channels for transcoding (using the MediaChannels parameter). Each transcoding session uses two DSP resources.
Page 339 If one of the above transcoding prerequisites is not met, then:  any value other than “As is” is discarded.  if the incoming offer is SRTP, force transcoding, coder transcoding, and DTMF extensions are not applied. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 340 Mediant 800B Gateway and E-SBC Parameter Description Web: RFC 2833 Behavior Defines the handling of RFC 2833 SDP offer\answer CLI: sbc-rfc2833-behavior negotiation for this SIP entity. [IpProfile_SBCRFC2833Behavior]  [0] As is = (Default) The device does not intervene in the RFC 2833 negotiation.
Page 341 [2] Handle on re-INVITE = Handle fax according to fax settings in the IP Profile for all re-INVITE offer-answer transactions (except for initial INVITE). Note: The fax settings in the IP Profile include IpProfile_SBCFaxCodersGroupID, IpProfile_SBCFaxOfferMode, and IpProfile_SBCFaxAnswerMode. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 342 Mediant 800B Gateway and E-SBC Parameter Description Web: Fax Offer Mode Defines the coders included in the outgoing SDP offer CLI: sbc-fax-offer-mode (sent to the called "fax") for this SIP entity. [IpProfile_SBCFaxOfferMode]  [0] All coders = (Default) Use only (and all) the coders of the selected Coders Group ID configured using the SBCFaxCodersGroupID parameter.
Page 343 [1] Supported = (Default) Initial INVITE requests without SDP are supported. Note: For this parameter to function, you need to configure a valid Extension Coders Group ID for IP Profiles that do not support delayed offer. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 344 Mediant 800B Gateway and E-SBC Parameter Description Web: Remote REFER Behavior Defines the device's handling of REFER requests for this CLI: sbc-rmt-refer-behavior SIP entity. [IpProfile_SBCRemoteReferBehavior]  [0] Regular = (Default) Refer-To header is unchanged and the device forwards the REFER as is.
Page 345 SIP networks (i.e., IP Groups). This includes the [IpProfile_SBCEnforceMKISize] capability of modifying the MKI length on the inbound or outbound SBC call leg for this SIP entity.  [0] Don't enforce = (Default) Device forwards the MKI size as is. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 346 Mediant 800B Gateway and E-SBC Parameter Description  [1] Enforce = Device changes the MKI length according to the settings of the IP Profile parameter, MKISize. Web: Remote Early Media RTP Behavior Defines whether the destination UA sends RTP CLI: sbc-rmt-early-media-rtp immediately after it sends 18x response.
Page 347 INVITE containing the Replaces header and establishes a new call between the SIP entity and the new call party. It then disconnects the call with the initial call party, by Version 6.8 Mediant 800B Gateway and E-SBC...
Page 348 Mediant 800B Gateway and E-SBC Parameter Description sending it a SIP BYE request.  [2] Keep as is = The SIP entity supports INVITE messages containing Replaces headers. The deviceforwards the Replaces header as is in incoming REFER and outgoing INVITE messages from/to the SIP entity (i.e., Replaces header's value is...
Page 349 RTP periods. In other words, the device does not generate RTCP when there is no RTP traffic (such as when a call is on hold). Note: The corresponding global parameter is SBCRTCPMode. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 350 Mediant 800B Gateway and E-SBC Parameter Description Web: Jitter Compensation Enables the on-demand jitter buffer for SBC calls. This CLI: sbc-jitter-compensation jitter buffer can be used when other functionality such as [IpProfile_SBCJitterCompensation] voice transcoding are not done on the call. This jitter buffer is useful when incoming packets are received at inconsistent intervals (i.e., packet delay variation).
Page 351 User's Manual 19. Coders and Profiles Parameter Description  This feature utilizes DSP resources. If there are insufficient resources, the fax transaction fails. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 352 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 353: Gateway Application
Part V Gateway Application...
Page 355: Introduction
CO or the PBX) and connects to analog telephones, dial-up modems, and fax machines. The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 356 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 357: Digital Pstn
 Creating a Loopback Line: You can create (and remove) remote loopback for DS1 lines. This is done by clicking the Create Loopback button. To remove the loopback, click the Remove Loopback button. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 358 BRI trunks can operate with E1 or T1 trunks. • The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk.
Page 359 Click the Apply Trunk Settings button to apply the changes to the selected trunk (or click Apply to All Trunks to apply the changes to all trunks); the Stop Trunk button replaces Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 360 Mediant 800B Gateway and E-SBC To save the changes to flash memory, see ''Saving Configuration'' on page 626. To reset the device, see ''Resetting the Device'' on page 623. User's Manual Document #: LTRT-10620...
Page 361: Tdm And Timing
 Internal clock (see ''Configuring Internal Clock as Clock Source'' on page 362) Note: When the device is used in a ‘non-span’ configuration, the internal device clock must be used (as explained above). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 362: Recovering Clock From Pstn Line Interface
Mediant 800B Gateway and E-SBC 21.2.2.1 Recovering Clock from PSTN Line Interface This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line interface. For a full description of the clock parameters, see ''PSTN Parameters'' on page 940.
Page 363: Configuring Cas State Machines
Settings page, by clicking the trunk number in the 'Related Trunks' field, and in the Trunk Settings page, select the required Trunk number icon, and then click Apply Trunk Settings. Click Submit, and then reset the device (see ''Resetting the Device'' on page 623). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 364 Mediant 800B Gateway and E-SBC Notes: • The CAS state machine can only be configured using the Web-based management tool. • Don't modify the default values unless you fully understand the implications of the changes and know the default values. Every change affects the configuration of the state machine parameters and the call process related to the trunk you are using with this state machine.
Page 365 Defines which Signaling System to use in both directions [CasStateMachineDigitSignalingSyst (detection\generation).  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 366: Configuring Digital Gateway Parameters
Mediant 800B Gateway and E-SBC 21.4 Configuring Digital Gateway Parameters The Digital Gateway Parameters page allows you to configure miscellaneous digital parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 783.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...
Page 367: Tunneling Applications
By utilizing the ‘Profiles’ mechanism (see ''Coders and Profiles'' on page 315), you can configure the TDM Tunneling feature to choose different settings based on a timeslot or groups of timeslots. For example, you can use low-bit-rate vocoders to transport voice and Version 6.8 Mediant 800B Gateway and E-SBC...
Page 368 Mediant 800B Gateway and E-SBC ‘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.
Page 369 CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce; CodersGroup0 0 = g7231; CodersGroup0 1 = Transparent; [ \CodersGroup0 ] [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, Version 6.8 Mediant 800B Gateway and E-SBC...
Page 370: Dsp Pattern Detector
Mediant 800B Gateway and E-SBC TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 21.5.1.1 DSP Pattern Detector For TDM tunneling applications, you can use the DSP pattern detector feature to initiate the echo canceller at call start. The device can be configured to support detection of a specific one-byte idle data pattern transmitted over digital E1/T1 timeslots.
Page 371 INFO message with Setup Ack encapsulated in its MIME body. The PBX sends QSIG Information messages (to complete the Called Party Number) only after it receives the Setup Ack. The device relays these Information messages encapsulated in SIP INFO messages to the remote party. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 372: Isdn Non-Facility Associated Signaling (Nfas)
Mediant 800B Gateway and E-SBC 21.6 ISDN Non-Facility Associated Signaling (NFAS) In regular T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B- channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.
Page 373: Nfas Interface Id
If there is no NFAS Backup trunk, the following configuration should be used: ISDNNFASInterfaceID_0 = 0 ISDNNFASInterfaceID_1 = 2 ISDNNFASInterfaceID_2 = 3 ISDNNFASInterfaceID_3 = 4 ISDNIBehavior = 512 ;This parameter should be added because of Version 6.8 Mediant 800B Gateway and E-SBC...
Page 374: Creating An Nfas-Related Trunk Configuration
Mediant 800B Gateway and E-SBC ;ISDNNFASInterfaceID coniguration above NFASGroupNumber_0 = 1 NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1 NFASGroupNumber_3 = 1 DchConfig_0 = 0 ;Primary T1 trunk DchConfig_1 = 2 ;B-Channel NFAS trunk DchConfig_2 = 2 ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk...
Page 375: Isdn Overlap Dialing
 ISDNRxOverlap_x = 1 (can be configured per trunk)  TimeBetweenDigits  MaxDigits  MuteDTMFInOverlap  DigitMapping For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 357. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 376: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578
Mediant 800B Gateway and E-SBC 21.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 With overlap dialing disabled, the device expects to receive the digits all at once (enbloc) or with very little delay between digits and then sends the complete number in a single message.
Page 377 USER SENDING COMPLETE [2]. For more information on the above mentioned parameters, see PSTN Parameters on page 940. For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 357. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 378: Redirect Number And Calling Name (Display)
Mediant 800B Gateway and E-SBC 21.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:...
Page 379: Trunk Group
''Configuring Hunt Group Settings'' on page 381).  To register the Trunk Groups, click the Register button, located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 380 Mediant 800B Gateway and E-SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the module (i.e., FXS, FXO, PRI, or BRI) for which you CLI: module want to define the Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk CLI: first-trunk-id Group.
Page 381: Configuring Hunt Group Settings
IP > Trunk Group > Hunt Group Settings). Configure a Trunk Group according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 382 Mediant 800B Gateway and E-SBC Table 22-2: Hunt Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_ TrunkGroupId] Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the channels of CLI: channel-select- the Trunk Group.
Page 383 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 278). Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 384 Mediant 800B Gateway and E-SBC Parameter Description  If this parameter is not configured, the registration is performed according to the global registration parameter, ChannelSelectMode.  To enable Trunk Group registration, set the global parameter, IsRegisterNeeded to 1. This is unnecessary for 'Per Account' registration mode.
Page 385  "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 386 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 387: Manipulation
However, if you configure the source prefix number as "55" for rule index 1 and "551" for rule index 2, the device applies rule index 1 to all numbers that start with 55, including Version 6.8 Mediant 800B Gateway and E-SBC...
Page 388 Mediant 800B Gateway and E-SBC numbers that start with 551. If the device doesn't find a matching rule, no manipulation is done on the call. You can perform a second "round" (additional) of source and destination number manipulations for IP-to-Tel calls, on an already manipulated number. The initial and additional number manipulation rules are both configured in the number manipulation tables for Ip-to-Tel calls.
Page 389 Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits from Left Stripped Digits from Right Prefix to Add Version 6.8 Mediant 800B Gateway and E-SBC...
Page 390 Mediant 800B Gateway and E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 23-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
Page 391 Web: Suffix to Add Defines the number or string that you want added to the end of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone number Version 6.8 Mediant 800B Gateway and E-SBC...
Page 392 Mediant 800B Gateway and E-SBC Parameter Description CLI: suffix-to-add is 1234, the new number is 123400. [Suffix2Add] Web/EMS: Number of Defines the number of digits that you want to keep from the right of the Digits to Leave phone number. For example, if you enter 4 and the phone number is CLI: num-of-digits-to-leave 00165751234, then the new number is 1234.
Page 393: Manipulating Number Prefix
The prefix is calculated as 020215. The first seven digits from the left are removed from the original number, thereby changing the number to 8888888. The prefix that was previously calculated is then added. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 394: Sip Calling Name Manipulations
Mediant 800B Gateway and E-SBC 23.4 SIP Calling Name Manipulations The calling name manipulation tables lets you configure up to 120 manipulation rules for manipulating the calling name (i.e., caller ID) in SIP messages, for IP-to-Tel and Tel-to-IP calls. Manipulation includes modifying or removing the calling name. The calling name manipulation tables include the following: ...
Page 395 ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 781. The default value is the asterisk (*) symbol (i.e., any source prefix). Web: Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 396 Mediant 800B Gateway and E-SBC Parameter Description CLI: calling-name-prefix You can use special notations for denoting the prefix. For example, to [_CallingNamePrefix] denote calls without a calling name, use the $ sign. For a description of available notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 781.
Page 397 Defines the number or string to add at the end of the calling name. For EMS: Prefix/Suffix To Add example, if you enter 00 and calling name is "company:name", the new CLI: suffix-to-add name is "company:name00". [_Suffix2Add] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 398: Configuring Redirect Number Ip To Tel
Mediant 800B Gateway and E-SBC 23.5 Configuring Redirect Number IP to Tel The redirect number manipulation tables let you configure rules for manipulating the redirect number received in SIP messages. The redirect number manipulation tables include:  Redirect Number IP-to-Tel table: This table defines IP-to-Tel redirect number manipulation.
Page 399 Notes:  This parameter is applicable only to the Redirect Number Tel > IP table.  This parameter is not applicable to IP-to-IP call routing. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 400 Mediant 800B Gateway and E-SBC Parameter Description Source IP Group ID Defines the IP Group from where the IP call originated. Typically, the CLI: src-ip-group-id IP Group of an incoming INVITE is determined or classified by the [_SrcIPGroupID] Inbound IP Routing table.
Page 401 [-1] Not Configured = (Default) Value received from PSTN/IP is CLI: npi used [_NumberPlan]  [0] Unknown  [1] E.164 Public  [9] Private For more information on available NPI/TON values, see Numbering Plans and Type of Number on page 410. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 402: Manipulating Redirected And Diverted Numbers For Call Diversion
Mediant 800B Gateway and E-SBC 23.6 Manipulating Redirected and Diverted Numbers for Call Diversion You can configure manipulation rules to manipulate the Diverted-to and Diverting numbers received in the incoming Call Redirection Facility message for call diversion, which is interworked to outgoing SIP 302 responses. This feature is applicable to the Euro ISDN and QSIG variants, and to IP-to-Tel calls.
Page 403: Mapping Npi/Ton To Sip Phone-Context
ISDN Setup message (for digital manipulations general-setting interfaces) with called and calling numbers. > add-ph-cntxt-as-pref  [0] Disable (default) [AddPhoneContextAsPrefix]  [1] Enable Defines the Number Plan Indicator (NPI). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 404: Configuring Release Cause Mapping
Mediant 800B Gateway and E-SBC Parameter Description  [0] Unknown (default) CLI: npi [PhoneContext_Npi]  [1] E.164 Public  [9] Private For a detailed list of the available NPI/TON values, see Numbering Plans and Type of Number on page 410.
Page 405: Fixed Mapping Of Sip Response To Isdn Release Reason
The following table describes the mapping of SIP response to ISDN release reason. Table 23-8: Mapping of SIP Response to ISDN Release Reason ISDN Release SIP Response Description Description Reason 400* Bad request Normal, unspecified Unauthorized Call rejected Version 6.8 Mediant 800B Gateway and E-SBC...
Page 406 Mediant 800B Gateway and E-SBC ISDN Release SIP Response Description Description Reason Payment required Call rejected Forbidden Call rejected Not found Unallocated number Method not allowed Service/option unavailable Not acceptable Service/option not implemented Proxy authentication required Call rejected Request timeout...
Page 407: Fixed Mapping Of Isdn Release Reason To Sip Response
503* Service unavailable Incoming calls barred within CUG Forbidden Bearer capability not authorized Forbidden Bearer capability not presently available Service unavailable Service/option not available 503* Service unavailable Bearer capability not implemented Not implemented Version 6.8 Mediant 800B Gateway and E-SBC...
Page 408 Mediant 800B Gateway and E-SBC ISDN Release Description Description Reason Response Channel type not implemented 480* Temporarily unavailable Requested facility not implemented 503* Service unavailable Only restricted digital information bearer 503* Service unavailable capability is available Service or option not implemented...
Page 409: Reason Header
Cause' parameter. This parameter defines Q.931 release causes. Its default value is 3, which is mapped to the SIP 404 response. By changing its value to 34, the SIP 503 response is sent. Other causes can be used as well. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 410: Numbering Plans And Type Of Number
Mediant 800B Gateway and E-SBC 23.9 Numbering Plans and Type of Number The IP-to-Tel destination or source number manipulation tables allow you to classify numbers by their Numbering Plan Indication (NPI) and Type of Number (TON). The device supports all NPI/TON classifications used in the ETSI ISDN variant, as shown in the table...
Page 411: Routing
If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call.  Matching Characteristics: One or more characteristics can be defined for the rule: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 412 Mediant 800B Gateway and E-SBC • Source IP Group (to which the call belongs) • Source and destination Request-URI host name prefix • Source Trunk Group (from where the call is received) • Source (calling) and destination (called) telephone number prefix and suffix •...
Page 413 IP addresses. Instead of an IP address, you can use an FQDN to resolve into two IP addresses. For more information on alternative routing, see ''Alternative Routing for Tel-to-IP Calls'' on page 428. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 414 Mediant 800B Gateway and E-SBC  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine with calculating the cost of using a service (Tel-to-IP call) and relaying that information to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule.
Page 415 This parameter is not applicable if outbound proxy routing is used.  For number manipulation, see ''Configuring Source/Destination Number Manipulation'' on page 387. Route Name Defines an arbitrary name to easily identify the routing rule. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 416 Mediant 800B Gateway and E-SBC Parameter Description CLI: route-name The valid value is a string of up to 20 characters. By default, no [PREFIX_RouteName] value is defined. Matching Call Characteristics Web: Src. IP Group ID Defines the IP Group from where the incoming IP call is received.
Page 417 'Dest Phone Prefix' field, enter 00 and in the 'Dest IP Address' field, enter 0.0.0.0.  For routing calls between phones connected to the device (i.e., local routing), enter the device's IP address. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 418 Mediant 800B Gateway and E-SBC Parameter Description  When the device's IP address is unknown (e.g., when DHCP is used), enter IP address 127.0.0.1.  When using domain names, enter the DNS server's IP address or alternatively, configure these names in the Internal DNS table (see ''Configuring the Internal DNS Table'' on page 137).
Page 419 2, 3, and 4 with Forking Group "1": The device sends the call according to index entry 1 only and ignores the other index entries even if the destination is unavailable and Version 6.8 Mediant 800B Gateway and E-SBC...
Page 420 Mediant 800B Gateway and E-SBC Parameter Description alternative routing is enabled. This is because the subsequent index entries are defined with a Forking Group number that is lower than that of index entry 1.  Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with...
Page 421: Configuring Inbound Ip Routing Table
SNMP trap, GWAPP_TRAP_BUSYOUT_LINK notifying of the out-of-service state for the specific trunk number. When the physical FXO port or trunk is physically reconnected, this trap is sent notifying of the back-to-service state. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 422 Mediant 800B Gateway and E-SBC Notes: • You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table. • If your deployment includes calls of many different called (source) and/or calling (destination) numbers that need to be routed to the same destination, you can employ user-defined prefix tags to represent these numbers.
Page 423 INVITE message, the value of this parameter is compared to the P-Asserted-Identity URI host name (and not the From header). Web: Source IP Address Defines the source IP address of the incoming IP call that can CLI: src-ip-address Version 6.8 Mediant 800B Gateway and E-SBC...
Page 424 Mediant 800B Gateway and E-SBC Parameter Description [PstnPrefix_SourceAddress] be used for routing decisions. The IP address can be configured in dotted-decimal notation (e.g., 10.8.8.5) or as an FQDN. If the address is an FQDN, DNS resolution is done according to the DNSQueryType parameter.
Page 425 This IP Group can later be used for outbound IP routing and as the 'Serving IP Group' in the Account table for obtaining authentication user name/password for this call. For configuring registration accounts in the Account table, see ''Configuring Account Table'' on page 297. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 426: Ip Destinations Connectivity Feature
Mediant 800B Gateway and E-SBC 24.4 IP Destinations Connectivity Feature The device can be configured to check the integrity of the connectivity to IP destinations of Tel-to-IP routing rules in the Outbound IP Routing table. The IP Connectivity feature can be...
Page 427 IP Connectivity: This page displays a more informative connectivity status of the IP destinations used in Tel-to-IP routing rules in the Outbound IP Routing table. For viewing this page, see ''Viewing IP Connectivity'' on page 716. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 428: Alternative Routing For Tel-To-Ip Calls
Mediant 800B Gateway and E-SBC 24.5 Alternative Routing for Tel-to-IP Calls The device supports various alternative Tel-to-IP call routing methods, as described in this section. 24.5.1 Alternative Routing Based on IP Connectivity You can configure the device to route Tel-to-IP calls to an alternative IP destination when the connectivity state of an IP destination is unavailable.
Page 429: Alternative Routing Based On Sip Responses
Alternative Routing table and 3) configuring an alternative routing rule. Note: The device also plays a tone to the endpoint whenever an alternative route is used. This tone played for a user-defined time, configured by the AltRoutingToneDuration parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 430 Mediant 800B Gateway and E-SBC Depending on configuration, the alternative routing is done using one of the following configuration entities:  Outbound IP Routing Rules: You configure alternative routing rules for a specific routing rule in the Outbound IP Routing table. If the destination of the "main" routing rule is unavailable, the device searches the table for the next matching rule (e.g.,...
Page 431 If you are using the Outbound IP Routing table, configure alternative routing rules with identical call matching characteristics, but with different IP destinations. If you are using the Proxy Set, configure redundant proxies. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 432: Alternative Routing Upon Sip 3Xx With Multiple Contacts
Mediant 800B Gateway and E-SBC 24.5.3 Alternative Routing upon SIP 3xx with Multiple Contacts You can configure how the device handles received SIP 3xx responses that contain multiple alternative contacts. The 3xx response indicates that the original destination is unavailable (e.g., 301 Moved Permanently – user cannot be found) and that the call can be redirected to alternative destinations specified in the SIP Contact headers.
Page 433: Alternative Routing For Ip-To-Tel Calls
The following procedure describes how to configure alternative routing reasons for IP-to- Tel calls in the Web interface. You can also configure alternative routing reasons for IP-to- Tel calls using the table ini file parameter, AltRouteCauseIP2Tel or CLI command, configure voip/gw routing alt-route-cause-ip2tel. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 434: Alternative Routing To An Ip Destination Upon A Busy Trunk
Mediant 800B Gateway and E-SBC  To configure alternative Trunk Group routing based on Q.931 cause codes: In the Proxy & Registration page, set the 'Redundant Routing Mode' parameter to Routing Table so that the device uses the Inbound IP Routing table for alternative routing.
Page 435 (i.e., IP address, port and transport type). Note: • If you do not specify a port, the device uses UDP port 5060. • When configured with a user@host, the original destination number is replaced by the user part. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 436: Alternative Routing Upon Isdn Disconnect
Mediant 800B Gateway and E-SBC 24.6.3 Alternative Routing upon ISDN Disconnect You can configure when the device sends a call to an alternative route if it receives an ISDN Q.931 Disconnect message with a Progress Indicator (PI) IE from the Tel side for IP- to-Tel calls.
Page 437: Configuring Dtmf And Dialing
Open the DTMF & Dialing page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > DTMF & Dialing). Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 626. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 438: Dialing Plan Features
Mediant 800B Gateway and E-SBC 25.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 25.1.1 Digit Mapping Digit map pattern rules are used for Tel-to-IP ISDN overlap dialing (by setting the ISDNRxOverlap parameter to 1) to reduce the dialing period (for digital interface). For more information on digit maps for ISDN overlapping, see ISDN Overlap Dialing on page 375.
Page 439 (TimeBetweenDigits parameter), it sends the collected digits. Therefore, this ensures that calls are not rejected as a result of their digit pattern not been completed in the Dial Plan. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 440: External Dial Plan File
Mediant 800B Gateway and E-SBC 25.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see ''Dial Plan File'' on page 644. User's Manual Document #: LTRT-10620...
Page 441: Configuring Supplementary Services
To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). Configure the parameters as required. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 442: Call Hold And Retrieve
Mediant 800B Gateway and E-SBC Click Submit, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server. To save the changes to flash memory, see ''Saving Configuration'' on page 626.
Page 443 A places B on hold; A hears a dial tone and B hears a held tone. A calls C and establishes a voice path. B places A on hold; B hears a dial tone. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 444: Call Pickup
Mediant 800B Gateway and E-SBC 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. 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...
Page 445: Consultation Feature
This feature is applicable to FXS interfaces. To enable this support, use the EnableCallTransferUsingReinvites parameter. The device also supports attended (consultation) call transfer for BRI phones (user side) connected to the device and using the Euro ISDN protocol. BRI call transfer is according to Version 6.8 Mediant 800B Gateway and E-SBC...
Page 446: Consultation Transfer For Qsig Path Replacement
Mediant 800B Gateway and E-SBC ETSI TS 183 036, Section G.2 (Explicit Communication Transfer – ECT). Call transfer is enabled using the EnableTransfer and EnableHoldtoISDN parameters. The Explicit Call Transfer (ECT, according to ETS-300-367, 368, 369) supplementary service is supported for BRI and PRI trunks. This service provides the served user who has two calls to ask the network to connect these two calls together and release its connection to both parties.
Page 447: Call Forward
The served party (FXS interface) can be configured through the Web interface (see Configuring Call Forward on page 500) or ini file to activate one of the call forward modes. These modes are configurable per endpoint. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 448: Call Forward Reminder Ring
Mediant 800B Gateway and E-SBC Notes: • When call forward is initiated, the device sends a SIP 302 response with a contact that contains the phone number from the forward table and its corresponding IP address from the routing table (or when a proxy is used, the proxy’s IP address).
Page 449: Call Forward Reminder (Off-Hook) Special Dial Tone
(e.g., *21*xxxxx) and as a result, the device sends a regular SIP INVITE message to the softswitch. The softswitch later notifies of the activation of the forwarding service by sending an unsolicited NOTIFY message with the Alert-Info header, as mentioned above. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 450: Bri Call Forwarding
Mediant 800B Gateway and E-SBC When the call forwarding service is de-activated, for example, by dialing #21# and sending an INVITE with this number, the softswitch sends another SIP NOTIFY message with the following Alert-Info header: Alert-Info: <http://127.0.0.1/ Tono-Normal-Invitacion>; Aviso = Desvió-Inmediato...
Page 451  “cfnr-activate”: Call Forward on No Reply activated  “cfnr-deactivate”: Call Forward on No Reply deactivated For example: INVITE sip:400@10.33.2.48;user=phone;facility=cfu-activate SIP/2.0 To enable the feature, configure the UseFacilityInRequest ini file parameter to 1. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 452: Call Waiting
Mediant 800B Gateway and E-SBC 26.7 Call Waiting The Call Waiting feature enables FXS devices to accept an additional (second) call on busy endpoints. If an incoming IP call is designated to a busy port, the called party hears a call waiting tone (several configurable short beeps) and (for Bellcore and ETSI Caller IDs) can view the Caller ID string of the incoming call.
Page 453: Message Waiting Indication
ISDN PRI NI-2 Message Waiting Notification (MWN), sent in the ISDN Facility IE message. This is applicable when the device is connected to a PBX through an ISDN PRI trunk configured to NI-2. This is configured by setting the VoiceMailInterface parameter to [9]. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 454 Mediant 800B Gateway and E-SBC  QSIG MWI: The device supports the interworking of QSIG MWI to IP (in addition to interworking of SIP MWI NOTIFY to QSIG Facility MWI messages). This provides interworking between an ISDN PBX with voice mail capabilities and a softswitch, which requires information on the number of messages waiting for a specific user.
Page 455: Caller Id
PolarityReversalType: some Caller ID signals use reversal polarity and/or wink signals. In these scenarios, it is recommended to set PolarityReversalType to 1 (Hard) (FXS only).  The Caller ID interworking can be changed using the parameters UseSourceNumberAsDisplayName and UseDisplayNameAsSourceNumber. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 456: Debugging A Caller Id Detection On Fxo
Mediant 800B Gateway and E-SBC 26.9.2 Debugging a Caller ID Detection on FXO The following procedure describes debugging caller ID detection in FXO interfaces.  To debug a Caller ID detection on an FXO interface: Verify that the parameter EnableCallerID is set to 1.
Page 457: Three-Way Conferencing
The device supports the following conference modes:  Conferencing managed by an external, AudioCodes Conference (media) server: The Conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.
Page 458 Mediant 800B Gateway and E-SBC • The conference-initiating INVITE sent by the device uses only the ConferenceID as the Request-URI. The Conferencing server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants.
Page 459: Emergency E911 Phone Number Services
The wink can be delayed by configuring the parameter DelayBeforeDIDWink to 200 (for 200 msec or a higher value). The switch detects the wink and then sends the MF Spill digits with ANI and (optional) Pseudo-ANI (P ANI). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 460 Mediant 800B Gateway and E-SBC The FXS device collects the MF digits, and then sends a SIP INVITE message to the PSAP with all collected MF digits in the SIP From header as one string. The FXS device generates a mid-call wink signal (two subsequent polarity reversals) toward the E911 tandem switch upon either detection of an RFC 2833 "hookflash"...
Page 461 If the device receives the SIP INFO message below, it then generates a "hookflash" mid- call Wink signal: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: port1vega1 <sip:06@192.168.13.2:5060> To: <sip:4505656002@192.168.13.40:5060>;tag=132878796- 1040067870294 Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2 CSeq:2 INFO Content-Type: application/broadsoft Content-Length: 17 event flashhook Version 6.8 Mediant 800B Gateway and E-SBC...
Page 462: Fxo Device Interworking Sip E911 Calls From Service Provider's Ip Network To Psap Did Lines
Mediant 800B Gateway and E-SBC 26.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines The device's FXO interface can interwork SIP emergency E911 calls from the Service Provider's IP network to the analog PSAP DID lines. The standards that define this interface include TR-TSY-000350 or Bellcore’s GR-350-Jun2003.
Page 463 The MF duration of all digits, except for the KP digit is 60 msec. The MF duration of the KP digit is 120 msec. The gap duration is 60 msec between any two MF digits. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 464 Mediant 800B Gateway and E-SBC Notes: • Manipulation rules can be configured for the calling (ANI) and called number (but not on the "display" string), for example, to strip 00 from the ANI "00INXXYYYY". • The called number, received as userpart of the Request URI ("301" in the example below), can be used to route incoming SIP calls to FXO specific ports, using the TrunkGroup and PSTNPrefix parameters.
Page 465: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls
For FXO interfaces, the preemption is done only on existing IP-to-Tel calls. In other words, if all the current FXO channels are busy with calls that were answered by the FXO device (i.e., Tel-to-IP calls), new incoming emergency IP-to- Tel calls are rejected. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 466: 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 467: Microsoft Lync Server 2010 And E9-1-1
PSAP. The gathering of location information in the Lync Server 2010 network is illustrated in the figure below: Figure 26-6: Microsoft Lync Server 2010 Client Acquiring Location Information Version 6.8 Mediant 800B Gateway and E-SBC...
Page 468 Mediant 800B Gateway and E-SBC The Administrator provisions the LIS database with the location of each network element in the Enterprise. The location is a civic address, which can include contextual in-building and company information. In other words, it associates a specific network entity (for example, a WAP) with a physical location in the Enterprise (for example, Floor 2, Wing A, and the Enterprise's street address).
Page 469 Emergency Response Locations (ERLs) and assign a dedicated Emergency Location Identification Number (ELIN) to each ERL (or zone). When Lync Server 2010 sends a SIP INVITE message with the PIDF-LO to the PSTN Gateway, it Version 6.8 Mediant 800B Gateway and E-SBC...
Page 470 Mediant 800B Gateway and E-SBC can parse the content and translate the calling number to an appropriate ELIN. The PSTN Gateway then sends the call to the PSTN with the ELIN number as the calling number. This ELIN number is sent to the Emergency Services provider, which sends it on to the appropriate PSAP according to the ELIN address match in the ALI database lookup.
Page 471: Audiocodes Elin Gateway For Lync Server 2010 E9-1-1 Calls To Pstn
PSAP, based on ELIN-address match lookup in the Emergency Services provider's ALI database. The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN.
Page 472 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 473 E9-1-1 call. This feature is initiated only if the received SIP INVITE message contains a Priority header set to "emergency", as shown below: PRIORITY: emergency Version 6.8 Mediant 800B Gateway and E-SBC...
Page 474 Mediant 800B Gateway and E-SBC 26.11.4.3.3 PSAP Callback to Lync 2010 Clients for Dropped E9-1-1 Calls As the E9-1-1 service automatically provides all the contact information of the E9-1-1 caller to the PSAP, the PSAP operator can call back the E9-1-1 caller. This is especially useful in cases where the caller disconnects prematurely.
Page 475: Configuring Audiocodes Elin Gateway
26.11.4.4 Configuring AudioCodes ELIN Gateway This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment. 26.11.4.4.1 Enabling the E9-1-1 Feature By default, the E9-1-1 feature in the ELIN Gateway for Lync Server 2010 is disabled.
Page 476 Mediant 800B Gateway and E-SBC 26.11.4.4.3 Configuring the SIP Release Cause Code for Failed E9-1-1 Calls When a Lync 2010 client makes an emergency call, the call is routed through the Microsoft Mediation Server to the ELIN Gateway, which sends it on to the PSTN. In some scenarios, the call may not be established due to either the PSTN (for example, the destination is busy or not found) or ELIN Gateway (for example, lack of resources or an internal error).
Page 477 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616 22:11:45 0 4258359777 ------------ Current Time: 22:12:40  Using Syslog, by invoking the following Web command shell: SIP / GateWay / E911Dump Version 6.8 Mediant 800B Gateway and E-SBC...
Page 478: Multilevel Precedence And Preemption
Mediant 800B Gateway and E-SBC 26.12 Multilevel Precedence and Preemption The device supports Multilevel Precedence and Preemption (MLPP) service. MLPP is a call priority scheme, which does the following:  Assigns a precedence level (priority level) to specific phone calls or messages.
Page 479 Table 5.3.2.12-4 (Mapping of RPH r-priority Field to PRI Precedence Level Value): Table 26-8: Mapping of SIP Resource-Priority Header to PRI Precedence Level for MLPP MLPP Precedence Level PRI Precedence Level SIP Resource-Priority Header Field Routine Priority Immediate Flash Flash Override Version 6.8 Mediant 800B Gateway and E-SBC...
Page 480: Mlpp Preemption Events In Sip Reason Header
Mediant 800B Gateway and E-SBC  If the network-domain field in the Resource-Priority header is any value other than "uc", then the device sets the Precedence Level field to "0 1 0 0" (i.e., "routine"). This can be modified using the EnableIp2TelInterworkingtable field of the ini file parameter, ResourcePriorityNetworkDomains.
Page 481: Precedence Ring Tone
200 OK is received from the remote destination. When a 200 OK is received, a double answer is sent from the FXO line. • Ensure that the PSTN side is configured to identify this double-answer signal. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 482: Configuring Multi-Line Extensions And Supplementary Services
Mediant 800B Gateway and E-SBC 26.14 Configuring Multi-Line Extensions and Supplementary Services The Supplementary Services table lets you configure up to 100 supplementary services for endpoints connected to the device. These endpoints include analog FXS phones and Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) phones.
Page 483 From the 'Action' drop-down list, select Register. To unregister the endpoint, select Un-Register. Table 26-9: Supplementary Services Table Parameter Description Parameter Description Index Defines an index number for the new table record. [ISDNSuppServ_Index] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 484 Mediant 800B Gateway and E-SBC Parameter Description Global Phone Number Defines a global telephone extension number for the endpoint. The global number is used for the following functionalities: phone-number  Endpoint registration [ISDNSuppServ_PhoneNumb  IP-to-Tel routing  Mapping between local and global (E.164) numbers between...
Page 485: Detecting Collect Calls
The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call), using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
Page 486 Mediant 800B Gateway and E-SBC For AOC in the Tel-to-IP direction: Enable the AOC service for sending AOC to IP: on the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF and Supplementary > Supplementary Services), set 'AoC Support' to Enable.
Page 487: Configuring Charge Codes
IP > DTMF and Supplementary > Charge Codes). Figure 26-12: Charge Codes Table Page Configure a Charge Code according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 488 Mediant 800B Gateway and E-SBC Table 26-10: Charge Codes Table Parameter Descriptions Parameter Description End Time Defines the end of the time period in a 24 hour format, hh. For CLI: end-time-<1-4> example, "04" denotes 4 A.M. [ChargeCode_EndTime<1-4>] Notes: ...
Page 489: 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 save the changes to flash memory, see ''Saving Configuration'' on page 626. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 490 Mediant 800B Gateway and E-SBC This page is Intentionally left blank. User's Manual Document #: LTRT-10620...
Page 491: 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 993. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 492 Mediant 800B Gateway and E-SBC  To configure the keypad features Open the Keypad Features page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Keypad Features). Figure 27-1: Keypad Features Page Configure the keypad features as required.
Page 493: Configuring Metering Tones
If you set the 'Generate Metering Tones' parameter to Internal Table, access the Charge Codes Table page by clicking the Charge Codes Table button. For more information on configuring the Charge Codes table, see ''Configuring Charge Codes'' on page 487. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 494: Configuring Fxo Settings
Mediant 800B Gateway and E-SBC 27.3 Configuring FXO Settings The FXO Settings page allows you to configure the device's specific FXO parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 783. Note: The FXO Settings page is available only for FXO interfaces.
Page 495: Configuring Authentication
Click Add; the following dialog box appears: Figure 27-4: Authentication Page Edit Record Configure authentication per port according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 496 Mediant 800B Gateway and E-SBC Table 27-1: Authentication Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table record. [Authentication_Index] Port (Read-only) Displays the port number. CLI: port [Authentication_Port] Module (Read-only) Displays the module number on which the port is CLI: port-type located.
Page 497: Configuring Automatic Dialing
(Read-only) Displays the port number. CLI: port [TargetOfChannel_Port] Port Type (Read-only) Displays the port type (FXS or FXO). [TargetOfChannel_PortType] Destination Phone Number Defines the destination telephone number to automatically dial. CLI: /dst-number [TargetOfChannel_Destination] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 498: Configuring Caller Display Information
Mediant 800B Gateway and E-SBC Parameter Description Auto Dial Status Enables automatic dialing. CLI: auto-dial-status  [0] Disable = Automatic dialing for the specific port is disabled. [TargetOfChannel_Type]  [1] Enable = (Default) Automatic dialing is enabled and the phone number configured in the 'Destination Phone Number' field is automatically dialed if the following occurs: ...
Page 499 ID is sent to the remote side using only the SIP P- Asserted-Identity or P-Preferred-Identity headers, according to the AssertedIdMode parameter. Note: This parameter is overridden by the 'Presentation' parameter in the Source Number Manipulation table (see ''Configuring Source/Destination Number Manipulation'' on page 387). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 500: Configuring Call Forward
Mediant 800B Gateway and E-SBC 27.7 Configuring Call Forward The Call Forward table lets you configure call forwarding per FXS or FXO port, for IP-to-Tel calls. This redirects the call, using a SIP 302 response, initially destined to a specific port, to a different port on the device or to an IP destination.
Page 501: Configuring Caller Id Permissions
Open the Caller ID Permissions page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Caller ID Permissions). Click Add; the following dialog box appears: Figure 27-6: Caller ID Permissions Page - Edit Record Version 6.8 Mediant 800B Gateway and E-SBC...
Page 502: Configuring Call Waiting
Mediant 800B Gateway and E-SBC Configure a caller ID permission per port according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 27-5: Caller ID Permissions Table Parameter Descriptions...
Page 503: Rejecting Anonymous Calls
RejectAnonymousCallPerPort. If configured, when an FXS interface receives an anonymous call, the device rejects the call and responds with a SIP 433 (Anonymity Disallowed) response. For a description of the parameter see ''Caller ID Parameters'' on page 912. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 504: Configuring Fxs Distinctive Ringing And Call Waiting Tones Per Source/Destination Number
Mediant 800B Gateway and E-SBC 27.11 Configuring FXS Distinctive Ringing and Call Waiting Tones per Source/Destination Number You can configure a distinctive ringing tone and call waiting tone per calling (source) and/or called (destination) number (or prefix) for IP-to-Tel calls. This feature can be configured per FXS endpoint or for a range of FXS endpoints.
Page 505: Fxs/Fxo Coefficient Types
DC (battery) feed characteristics  AC impedance matching  Transmit gain  Receive gain  Hybrid balance  Frequency response in transmit and receive direction  Hook thresholds  Ringing generation and detection parameters Version 6.8 Mediant 800B Gateway and E-SBC...
Page 506: Fxo Operating Modes
Mediant 800B Gateway and E-SBC  To select the FXO and FXS Coefficient types: Open the Analog Settings page (Configuration tab > VoIP menu > Media > Analog Settings). This page includes the Coefficient type parameters, as shown below: Figure 27-9: FXS/FXO Coefficient Parameters in Analog Settings Page From the 'FXS Coefficient Type' drop-down list (FXSCountryCoefficients), select the required FXS Coefficient type.
Page 507: One-Stage Dialing
Voice Detection: the device sends a 200 OK in response to an INVITE only when it detects the start of speech (fax or modem answer tone) from the Tel side. Note that the IPM detectors must be enabled. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 508: Two-Stage Dialing
Mediant 800B Gateway and E-SBC 27.13.1.2 Two-Stage Dialing Two-stage dialing is when the IP caller is required to dial twice. The caller initially dials to the FXO device and only after receiving a dial tone from the PBX (via the FXO device), dials the destination telephone number.
Page 509: Fxo Operations For Tel-To-Ip Calls
Automatic dialing is defined using the Web interface's Automatic Dialing (TargetOfChannel ini file parameter) page, described in see ''Configuring Automatic Dialing'' on page 497. The SIP call flow diagram below illustrates Automatic Dialing. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 510: Collecting Digits Mode
Mediant 800B Gateway and E-SBC 27.13.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 27-11: Call Flow for Collecting Digits Mode 27.13.2.3...
Page 511: Call Termination On Fxo Devices
This method operates correctly only if silence suppression is not used.  Protocol-based termination of the call from the IP side Note: The implemented disconnect method must be supported by the CO or PBX. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 512: Call Termination Before Call Establishment
Mediant 800B Gateway and E-SBC 27.13.3.2 Call Termination before Call Establishment The device supports the following call termination methods before a call is established:  Call termination upon receipt of SIP error response (in Automatic Dialing mode): By default, when the FXO device operates in Automatic Dialing mode, there is no method to inform the PBX if a Tel-to-IP call has failed (SIP error response - 4xx, 5xx or 6xx - is received).
Page 513: Remote Pbx Extension Between Fxo And Fxs Devices
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.8 Mediant 800B Gateway and E-SBC...
Page 514: Dialing From Remote Extension (Phone At Fxs)
Mediant 800B Gateway and E-SBC 27.14.1 Dialing from Remote Extension (Phone at FXS) The following procedure 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 515: Message Waiting Indication For Remote Extensions
Upon detection of an MWI message, the FXO device sends a SIP NOTIFY message to the IP side. When receiving this NOTIFY message, the remote FXS device generates an MWI signal toward its Tel side. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 516: Call Waiting For Remote Extensions
Mediant 800B Gateway and E-SBC 27.14.4 Call Waiting for Remote Extensions When the FXO device detects a Call Waiting indication (FSK data of the Caller Id - CallerIDType2) from the PBX, it sends a proprietary INFO message, which includes the caller identification to the FXS device.
Page 517: Fxo Gateway Configuration
IP address of the FXS device (10.1.10.3) in the field ‘IP Address’. Figure 27-16: FXO Tel-to-IP Routing Configuration In the FXO Settings page (see ''Configuring FXO Parameters'' on page 494), set the parameter ‘Dialing Mode’ to Two Stages (IsTwoStageDial = 1). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 518 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 519: Session Border Controller Application
Part VI Session Border Controller Application...
Page 521: Sbc Overview
Modifies SIP To, From, and Request-URI host names (must be configured using the Message Manipulations table). • Generates a new SIP Call-ID header value (different between legs). • Changes the SIP Contact header to the device's own address. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 522: Sip Network Definitions
Mediant 800B Gateway and E-SBC • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following: •...
Page 523 ''SBC Manipulations'' on page 583. 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 305. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 524 Mediant 800B Gateway and E-SBC The flowchart below illustrates the SBC process: Figure 28-1: Routing Process User's Manual Document #: LTRT-10620...
Page 525: User Registration
Alternatively, the original user can be retained in the Contact header and used in the outgoing REGISTER request (using the SBCKeepContactUserinRegister parameter). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 526: Sbc Users Registration Database
Mediant 800B Gateway and E-SBC 28.3.2 SBC Users Registration Database The device manages a dynamic Users Registration database that is updated according to registration requests that traverse it. Each database entry for a user represents a binding between an AOR (obtained from the SIP To header) and one or more contact (obtained from the SIP Contact headers).
Page 527: Registration Restriction Control
The flowchart below depicts the process for blocking unregistered users. When the call is rejected, the device sends a SIP 500 (Server Internal Error) response to the remote end. Figure 28-2: Blocking Incoming Calls from Unregistered Users Version 6.8 Mediant 800B Gateway and E-SBC...
Page 528: Sbc Media Handling
Mediant 800B Gateway and E-SBC 28.4 SBC Media Handling Media behavior includes anything related to the establishment, management and termination of media sessions within the SIP protocol. Media sessions are created using the SIP "offer"/"answer" mechanism. If successful, the result is a bi-directional media (RTP) flow (e.g.
Page 529: Media Anchoring Without Transcoding (Transparent)
The figure below illustrates an example of SDP handling for a call between a LAN IP Phone 10.2.2.6 and a remote IP Phone 212.179.1.13 on the WAN. Figure 28-3: SDP Offer/Answer Example Version 6.8 Mediant 800B Gateway and E-SBC...
Page 530: Media Anchoring With Transcoding
Mediant 800B Gateway and E-SBC 28.4.2 Media Anchoring with Transcoding The device performs transcoding when there are no common coders between the two user agents (i.e., the SDP answer from one user agent doesn't include any coder included in the offer previously sent by the other user agent).
Page 531: No Media Anchoring
The device is located within the LAN.  Calls between two SIP UAs in the same LAN and signaling is sent to a SIP proxy server (or hosted IP PBX) located in the WAN. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 532 Mediant 800B Gateway and E-SBC  The device does not need to perform NAT traversal (for media) and all the users are in the same domain. Figure 28-5: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring feature include the following: ...
Page 533: Transcoding Modes
IP Profile table. 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.8 Mediant 800B Gateway and E-SBC...
Page 534: Restricting Coders
Mediant 800B Gateway and E-SBC 28.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 535 In the IP Profile table, select this Coders Group in the 'Extension Coders Group ID' parameter. In the IP Profile table, enable this feature by setting the 'Allowed Coders Mode' parameter to Restriction or Restriction and Preference. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 536: Prioritizing Coder List In Sdp Offer
Mediant 800B Gateway and E-SBC 28.4.7 Prioritizing Coder List in SDP Offer In addition to restricting the use of coders with Allowed coders, you can prioritize the coders listed in the SDP offer. This feature is referred to as Coder Preference. This is done on both SBC legs: ...
Page 537: Multiple Rtp Media Streams Per Call Session
 IPProfile_SBCFaxBehavior: defines the offer negotiation method - pass fax transparently, negotiate fax according to fax settings in IP Profile, or enforce remote UA to first establish a voice channel before fax negotiation. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 538: Limiting Sbc Call Duration
Mediant 800B Gateway and E-SBC  IPProfile_SBCFaxCodersGroupID: defines the supported fax coders (from the Coders Group Settings table).  IPProfile_SBCFaxOfferMode: determines the fax coders sent in the outgoing SDP offer.  IPProfile_SBCFaxAnswerMode: determines the fax coders sent in the outgoing SDP answer.
Page 539: User Authentication Based On Radius
The device accepts the SIP client's request (sends a SIP 200 OK or forwards the authenticated request) or rejects it (sends another SIP 407 to the SIP client). To configure this feature, set the SBCServerAuthMode ini file parameter to 2. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 540: Interworking Sip Signaling
Mediant 800B Gateway and E-SBC 28.8 Interworking SIP Signaling The device supports interworking of SIP signaling messages to ensure interoperability between communicating SIP UAs or entities. This is critical in network environments where the UAs on opposing SBC legs have different SIP signaling support. For example, some UAs may support different versions of a SIP method while others may not event support a specific SIP method.
Page 541: Local Handling Of Sip 3Xx
Routing table rules. (where the 'Call Trigger' field is set to 3xx). It is also possible to specify the IP Group that sent the 3xx request as matching criteria for the re-routing rule in this table ('ReRoute IP Group ID' field). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 542: Interworking Sip Diversion And History-Info Headers
Mediant 800B Gateway and E-SBC 28.8.2 Interworking SIP Diversion and History-Info Headers This device can be configured to interwork between the SIP Diversion and History-Info headers. This is important, for example, to networks that support the Diversion header but not the History-Info header, or vice versa. Therefore, mapping between these headers is crucial for preserving the information in the SIP dialog regarding how and why (e.g., call...
Page 543: Interworking Sip Refer Messages
Mandatory: PRACK is required for these UAs. Calls from UAs that do not support PRACK are rejected. Calls destined to these UAs are also required to support PRACK.  Transparent (default): The device does not intervene with the PRACK process and forwards the request as is. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 544: Interworking Sip Session Timer
Mediant 800B Gateway and E-SBC 28.8.5 Interworking SIP Session Timer The device supports interworking of the SIP signaling keep-alive mechanism. The SIP standard provides a signaling keep-alive mechanism using re-INVITE and UPDATE messages. In certain setups, keep-alive may be required by some SIP UAs while for others it may not be supported.
Page 545 User's Manual 28. SBC Overview Figure 28-7: SBC Early Media RTP 18x without SDP Figure 28-8: Early Media RTP - SIP 18x with SDP Version 6.8 Mediant 800B Gateway and E-SBC...
Page 546: Interworking Sip Re-Invite Messages
Mediant 800B Gateway and E-SBC 28.8.7 Interworking SIP re-INVITE Messages The device supports interworking re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs. The device does not forward re-INVITE requests to IP Groups that do not support it.
Page 547: Interworking Call Hold
Interworking generation of held tone where the device generates the tone to the held party instead of the call hold initiator. This is configured by the IP Profile parameter, 'SBC Reliable Held Tone Source'. For configuring IP Profiles, see ''Configuring IP Profiles'' on page 323. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 548: Call Survivability
Mediant 800B Gateway and E-SBC 28.9 Call Survivability This section describes various call survivability features supported by the SBC device. 28.9.1 Auto-Provisioning of Subscriber-Specific Information for BroadWorks Server for Survivability This feature enables SBC user registration for interoperability with BroadSoft BroadWorks server to provide call survivability in case of connectivity failure with the BroadWorks server, for example, due to a WAN failure.
Page 549: Broadsoft's Shared Phone Line Call Appearance For Sbc Survivability
'SBC Client Forking Mode' parameter to Parallel so that the device forks incoming calls to all contacts under the same AOR registered in the device's registration database. In the IP-to-IP Routing table (see ''Configuring SBC IP-to-IP Routing Rules'' on page Version 6.8 Mediant 800B Gateway and E-SBC...
Page 550: Call Survivability For Call Centers
Mediant 800B Gateway and E-SBC 571), add a rule for routing calls between the above configured IP Groups. In the IP to IP Inbound Manipulation table (see ''Configuring IP-to-IP Inbound Manipulations'' on page 585), add a manipulation rule for the secondary extensions (e.g., 601 and 602) so that they also register to the device's database under the...
Page 551 The 'Destination Type' field is set to Hunt Group, which is specifically used for call center survivability. ♦ The 'Destination IP Group ID' field is set to the IP Group of the call center agents. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 552 Mediant 800B Gateway and E-SBC The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure 28-13: Routing Rule Example for Call Center Survivability User's Manual...
Page 553: Survivability Mode Display On Aastra Ip Phones
(user), belonging to the destination IP Group User-type, registered in the database to all other users located under the same AOR as the specific contact. This is configured using the SBCSendInviteToAllContacts parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 554: Sip Forking Initiated By Sip Proxy Server
Mediant 800B Gateway and E-SBC 28.10.2 SIP Forking Initiated by SIP Proxy Server The device can handle SIP forking responses received from a proxy server in response to an INVITE forwarded by the device from a UA. In other words, received responses with a different SIP To header 'tag' parameter for the request forwarded by the device.
Page 555: Sbc Configuration
The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP Version 6.8 Mediant 800B Gateway and E-SBC...
Page 556 Mediant 800B Gateway and E-SBC clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself; not that of the involved SIP clients. This is due to, for example, the device's topology hiding (e.g., IP address) of its LAN elements.
Page 557: Configuring Admission Control
+ 20)]. If IP Group ID 1 needs to handle 15 calls, it is guaranteed 10 calls and the remaining 5 is provided from the SRD's shared pool. If the SDR's shared pool is currently Version 6.8 Mediant 800B Gateway and E-SBC...
Page 558 Mediant 800B Gateway and E-SBC empty and resources for new calls are required, the quota is taken from the device's total capacity, if available. For example, if IP Group ID 1 needs to handle 21 calls, it's guaranteed 10, the SRD's shared pool provides another 10, and the last call is provided from the device's total call capacity support (e.g., of 200).
Page 559 IP Group or SRD. You can also [SBCAdmissionControl_LimitPerU use the following special values: ser]  [0] 0 = Block all these dialogs.  [-1] -1 = (Default) Unlimited. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 560 Mediant 800B Gateway and E-SBC Parameter Description Rate Defines the rate (in seconds) at which tokens are added to the CLI: rate token bucket per second (i.e., token rate). [SBCAdmissionControl_Rate] The default is 0 (i.e., unlimited rate). Notes:  You must first configure the Maximum Burst parameter (see below) before configuring the Rate parameter.
Page 561: Configuring Allowed Audio Coder Groups
 To configure an Allowed Coders Group: Open the Allowed Audio Coders Group page (Configuration tab > VoIP menu > SBC > Allowed Audio Coders Group). Figure 29-4: Allowed Audio Coders Group Page Version 6.8 Mediant 800B Gateway and E-SBC...
Page 562: Configuring Allowed Video Coder Groups
Mediant 800B Gateway and E-SBC Configure an Allowed Audio Coders Group according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 29-2: Allowed Audio Coders Group Table Parameter Descriptions...
Page 563: Routing Sbc
Proxy Set. The Proxy Set is assigned to the IP Group in the IP Group table. If classification based on Proxy Set fails (or classification based on Proxy Set is disabled), the device proceeds to classification based on the Classification table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 564 Mediant 800B Gateway and E-SBC Note: • For security, it is recommended to classify SIP dialogs based on Proxy Set only if the IP address of the Server-type IP Group is unknown. In other words, if the Proxy Set associated with the IP Group is configured with an FQDN. In such cases, the device classifies incoming SIP dialogs to the IP Group based on the DNS-resolved IP address.
Page 565 SIP response code per SIP interface. This is configured by the 'Classification Failure Response Type' parameter in the SIP Interface table (see ''Configuring SIP Interfaces'' on page 274). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 566 Mediant 800B Gateway and E-SBC The flowchart below illustrates the classification process: Figure 29-5: Classification Process (Identifying IP Group or Rejecting Call) Note: The device saves incoming SIP REGISTER messages in its registration database. If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination.
Page 567 By default, no SRD is defined. Note: The SRDs are also associated with a port number as defined by the SIP Interface used by the SRD (see ''Configuring SIP Interfaces'' on page 274). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 568 Mediant 800B Gateway and E-SBC Parameter Description Source IP Address Defines the source IP address (in dotted-decimal notation) CLI: src-ip-address of the incoming SIP dialog. [Classification_SrcAddress] The IP address can be configured using the following wildcards:  "x" wildcard: represents single digits. For example, 10.8.8.xx represents all the addresses between...
Page 569: Classification Based On Uri Of Selected Header Example
This example assumes the following incoming INVITE message: INVITE sip:8000@10.33.4.226 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.226;branch=z9hG4bKVEBTDAHSUYRTEXEDEGJY From: <sip:100@10.33.4.226>;tag=YSQQKXXREVDPYPTNFMWG To: <sip:8000@10.33.4.226> Call-ID: FKPNOYRNKROIMEGBSSKS@10.33.4.226 CSeq: 1 INVITE Contact: <sip:100@10.33.4.226> Route: <sip:2000@10.10.10.10.10>,<sip:300@10.10.10.30> Supported: em,100rel,timer,replaces P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 570: Configuring Message Condition Rules
Mediant 800B Gateway and E-SBC In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group ID Prefix Username Prefix 1111 2000 10.10.10.10 In the IP Group table, add the following IP Groups:...
Page 571: Configuring Sbc Ip-To-Ip Routing
Rule: Defines the characteristics of the incoming SIP dialog message (e.g., IP Group from which the message is received).  Action: Defines the action that is done if the incoming call matches the characteristics of the rule (i.e., routes the call to the specified destination). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 572 Mediant 800B Gateway and E-SBC The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it sends the call to the destination configured for that rule. If it doesn't find a matching rule, it rejects the call.
Page 573 The LCR feature can also be employed with call forking. The device calculates a maximum call cost for each Forking group and routes the call to the Forking group Version 6.8 Mediant 800B Gateway and E-SBC...
Page 574 Mediant 800B Gateway and E-SBC with the lowest cost. Thus, even if the call can successfully be routed to the main routing rule, a different routing rule can be chosen (even an alternative route, if configured) based on LCR. If routing to one Forking group fails, the device tries to route the call to the Forking group with the next lowest cost (main or alternative route), and so on.
Page 575 Defines the SIP dialog request type of the incoming SIP [IP2IPRouting_RequestType] dialog. CLI: request-type  [0] All (default)  [1] INVITE  [2] REGISTER  [3] SUBSCRIBE  [4] INVITE and REGISTER  [5] INVITE and SUBSCRIBE  [6] OPTIONS Version 6.8 Mediant 800B Gateway and E-SBC...
Page 576 Mediant 800B Gateway and E-SBC Parameter Description Message Condition Assigns a SIP message Condition rule. To configure [IP2IPRouting_MessageCondition] Condition rules, see ''Configuring Message Condition Rules'' CLI: message-condition on page 570. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect [IP2IPRouting_ReRouteIPGroupID] response (e.g., 3xx) or REFER message.
Page 577 Defines the IP Group ID to where you want to route the call. [IP2IPRouting_DestIPGroupID] The SIP dialog messages are sent to the IP address defined CLI: dst-ip-group-id for the Proxy Set associated with this IP Group. If you select Version 6.8 Mediant 800B Gateway and E-SBC...
Page 578 Mediant 800B Gateway and E-SBC Parameter Description an IP Group, it is unnecessary to configure a destination IP address (in the '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...
Page 579 Alternative Routing Reasons on page 580). However, if no response, ICMP, or a SIP 408 response is received, the device attempts to use the alternative route even if no entries are configured in the ‘SBC Alternative Routing Version 6.8 Mediant 800B Gateway and E-SBC...
Page 580: Configuring Sip Response Codes For Alternative Routing Reasons
Mediant 800B Gateway and E-SBC Parameter Description Reasons’ table.  Multiple alternative route entries can be configured (e.g., Index 1 is the main route - Route Row - and indices 2 through 4 are configured as alternative routes). Group Policy Defines whether the routing rule includes call forking.
Page 581 IP-to-IP Routing table for the SRD or IP Group. If no alternative routing rule is located, the device automatically rejects the SIP request with a SIP 480 "Temporarily Unavailable" response. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 582 Mediant 800B Gateway and E-SBC The following procedure describes how to configure the SBC Alternative Routing Reasons table in the Web interface. You can also configure this table using the table ini file parameter, SBCAlternativeRoutingReasons or CLI command, configure voip > sbc routing sbc-alt-routing-reasons.
Page 583: Sbc Manipulations
Below is an example of a call flow and consequent SIP URI manipulations:  Incoming INVITE from LAN: INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 Via: SIP/2.0/UDP 10.2.2.6;branch=z9hGLLLLLan From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe To: <sip:1000@10.2.2.3;user=phone> Call-ID: USELLLAN@10.2.2.3 CSeq: 1 INVITE Version 6.8 Mediant 800B Gateway and E-SBC...
Page 584 Mediant 800B Gateway and E-SBC Contact: <sip:7000@10.2.2.3> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 ...
Page 585: Configuring Ip-To-Ip Inbound Manipulations
The following procedure describes how to configure IP-to-IP Inbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPInboundManipulation or CLI command, configure voip > sbc manipulations ip-inbound- manipulation. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 586 Mediant 800B Gateway and E-SBC  To configure an IP-to-IP Inbound Manipulation rule: Open the IP to IP Inbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Inbound). Click Add; the following dialog box appears:...
Page 587 [2] REGISTER = Only REGISTER messages.  [3] SUBSCRIBE = Only SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 588: Configuring Ip-To-Ip Outbound Manipulations
Mediant 800B Gateway and E-SBC Parameter Description Manipulated URI Determines whether the source or destination SIP URI user CLI: manipulated-uri part is manipulated. [IPInboundManipulation_Manipula  [0] Source = (Default) Manipulation is done on the source tedURI] SIP URI user part.
Page 589 Figure 29-13: IP to IP Outbound Manipulation Page Add Dialog Box Configure an IP-to-IP outbound manipulation rule according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 590 Mediant 800B Gateway and E-SBC Table 29-9: IP to IP Outbound Manipulation Table Parameter Description Parameter Description Index Defines an index number for the new table record. [IPOutboundManipulation_Index] Manipulation Name Defines an arbitrary name to easily identify the CLI: manipulation-name manipulation name.
Page 591 [3] 3xx or REFER = Applies to options [1] and [2].  [4] Initial only = Regular requests that the device forwards to a destination. In other words, re-routing of requests triggered by the receipt of REFER or 3xx does not apply. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 592 Mediant 800B Gateway and E-SBC Parameter Description Operation Manipulation Rule - Action Manipulated Item Defines the element in the SIP message that you want CLI: manipulated-uri manipulated. [IPOutboundManipulation_IsAdditional  [0] Source URI = (Default) Manipulates the source SIP Manipulation] Request-URI user part.
Page 593 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.8 Mediant 800B Gateway and E-SBC...
Page 594 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 595: Cloud Resilience Package
Part VII Cloud Resilience Package...
Page 597: Crp Overview
Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
Page 598 Mediant 800B Gateway and E-SBC Survivability Quality of Experience/Service Security registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...
Page 599: Crp Configuration
Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'CRP Application' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 600: Configuring Call Survivability Mode
Mediant 800B Gateway and E-SBC 31.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.
Page 601: 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 278. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 602: Pre-Configured Ip-To-Ip Routing Rules
Mediant 800B Gateway and E-SBC 31.4 Pre-Configured IP-to-IP Routing Rules For the CRP application, the IP-to-IP Routing table is pre-configured with IP-to-IP routing rules. These rules depend on the configured Call Survivability mode, as described in ''Configuring Call Survivability Mode'' on page 600.
Page 603: Emergency Mode
For the routing rule of Index 2, the destination is the source IP Group (i.e., from where the REGISTER message was received). Index 7 appears only if the CRPGatewayFallback parameter is enabled (see ''Configuring PSTN Fallback'' on page 604). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 604: Configuring Pstn Fallback
Mediant 800B Gateway and E-SBC 31.5 Configuring PSTN Fallback You can enable the CRP to route emergency calls (or PSTN-intended calls) such as "911" from the Proxy server (IP Group 2) to the PSTN (IP Group 3). In addition, for calls from the...
Page 605: High-Availability System
Part VIII High-Availability System...
Page 607: Ha Overview
Device Switchover upon Failure on page 608. • HA is supported only on the Mediant 800B hardware platform (not Mediant 800). The figure below illustrates the Active-Redundant HA devices under normal operation. Communication between the two devices is through a Maintenance interface, having a unique IP address for each device.
Page 608: Device Switchover Upon Failure
Mediant 800B Gateway and E-SBC Thus, under normal operation, one of the devices is in active state while the other is in redundant state, where both devices share the same configuration and software. Any subsequent configuration update or software upgrade on the active device is also done on the redundant device.
Page 609: Ha Status On The Home Page
In the 'HA Device Name' field, enter a name for the active device. Click Submit. Note: Once the devices are running in HA mode, you can change the name of the redundant device, through the active device only, in the 'Redundant HA Device Name' field. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 610 Mediant 800B Gateway and E-SBC The Home page also displays the HA operational status of the device to which you are currently logged in. This is displayed in the 'High Availability' field under the General Information pane:  "Not Operational": HA is not configured or the installed Software License Key does not include the HA feature ...
Page 611: Ha Configuration
Figure 33-1: Rx/Tx Mode for Geographical HA  If the Maintenance ports of both devices are connected directly to each other without intermediation of switches, configure the mode to 2RX/1TX: Figure 33-2: Rx/Tx Mode for Direct Connection Version 6.8 Mediant 800B Gateway and E-SBC...
Page 612: Configuring The Ha Devices
Mediant 800B Gateway and E-SBC  If the two devices are connected through two (or more) isolated LAN switches (i.e., packets from one switch cannot traverse the second switch), configure the mode to 2RX/2TX: Figure 33-3: Redundancy Mode for Two Isolated Switches Notes: •...
Page 613: Step 1: Configure The First Device
Ethernet Device "vlan 2" (which is associated with Ethernet Port Group "GROUP_2") in the 'Underlying Device' field, while the other interface is assigned to "vlan 1" (associated with "GROUP_1"): Figure 33-4: Configured MAINTENANCE Interface in Interface Table Version 6.8 Mediant 800B Gateway and E-SBC...
Page 614 Mediant 800B Gateway and E-SBC If the connection is through a switch, the packets of both interfaces should generally be untagged. In such a scenario, set the Native VLAN ID of each Ethernet Port Group so that it is the same as the VLAN ID set for each interface assigned to that Ethernet Port Group.
Page 615: Step 2: Configure The Second Device
(configured in Step 1: Configure the First Device on page 613). Burn the configuration to flash without a reset. Power down the device. Continue to ''Step 3: Initialize HA on the Devices'' on page for completing the HA configuration. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 616: Step 3: Initialize Ha On The Devices
Mediant 800B Gateway and E-SBC 33.1.2.3 Step 3: Initialize HA on the Devices Once you have configured both devices for HA as described in the previous sections, follow the procedure below to complete and initialize HA so that the devices become operational in HA.
Page 617: Configuration While Ha Is Operational
After it synchronizes with the active device, it initiates a switchover and becomes the new active device (the former active device resets and becomes the new redundant device). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 618: Configuring Firewall Allowed Rules
Mediant 800B Gateway and E-SBC 33.3 Configuring Firewall Allowed Rules If you add firewall rules in the Firewall Settings page (see ''Configuring Firewall Settings'' on page 151) that block specified traffic, you also need to add rules that ensure traffic related to the HA feature is allowed.
Page 619: Ha Maintenance
The previously active device burns and resets with the new software version. The previously active device switches over to become the active device. For more information on upgrading the software, see ''Software Upgrade Wizard'' on page 663. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 620 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 621: Maintenance
Part IX Maintenance...
Page 623: Basic Maintenance
Description'' on page 44) 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 45). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 624: Remotely Resetting Device Using Sip Notify
Mediant 800B Gateway and E-SBC  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 623). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...
Page 625: 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 626: Saving Configuration
Mediant 800B Gateway and E-SBC Click OK to confirm device lock; if you set 'Graceful Option' to Yes, a lock icon is delayed and a window appears displaying the number of remaining calls and time. If you set 'Graceful Option' to No, the lock process begins immediately. The 'Gateway Operational State' field displays "LOCKED".
Page 627: High Availability Maintenance
Under the 'Switch Over' group, click Switch Over; a confirmation box appears requesting you to confirm. Click OK.  To reset the Redundant device: Under the 'Redundant Options' group, click Reset; a confirmation box appears requesting you to confirm. Click OK. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 628 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 629: Disconnecting Active Calls
Session ID. This is done in the CLI using the following commands (from basic command mode):  Disconnects all active calls: # clear voip calls  Disconnects active calls belonging to a specified Session ID: # clear voip calls <Session ID> Version 6.8 Mediant 800B Gateway and E-SBC...
Page 630 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 631: Resetting Channels
B-channel is restarted. • B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2). • B-channel restart does not affect the B-channel's configuration. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 632 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 633: Disabling Analog Ports
By default, all the analog ports are enabled. To disable an analog port, use the following CLI command: (config-voip)# interface fxs-fxo (fxs-fxo)# analog-port-enable <module>/<port> [on|off] For example, to disable port 2 on module 1: (fxs-fxo)# analog-port-enable 1/2 off Version 6.8 Mediant 800B Gateway and E-SBC...
Page 634 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 635: Locking And Unlocking Trunk Groups
• "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 636 Mediant 800B Gateway and E-SBC Note: • If the device is reset, a locked Trunk Group remains locked. If the device is reset while graceful lock is in progress, the Trunk Group is forced to lock immediately after the device finishes its reset.
Page 637: Software Upgrade
TFTP during device startup. If the ini file does not contain a specific auxiliary file type, the device uses the last auxiliary file of that type that was stored on its non-volatile memory. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 638 Mediant 800B Gateway and E-SBC Notes: • You can schedule automatic loading of updated auxiliary files using HTTP/HTTPS. For more information on automatic updates, see Automatic Update Mechanism. • When loading an ini file using this Web page, parameters that are excluded from the loaded ini file retain their current settings (incremental).
Page 639: 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 640 Mediant 800B Gateway and E-SBC ♦ [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 ♦ [16] Off Hook Warning Tone ♦...
Page 641: Distinctive Ringing
This cadence rings once during the ringing pattern. Otherwise, the cadence is interpreted as cyclic: it repeats for every ringing cycle.  Ring On Time: Specifies the duration of the ringing signal.  Ring Off Time: Specifies the silence period of the cadence. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 642 Mediant 800B Gateway and E-SBC The Distinctive Ringing section of the ini file format contains the following strings:  [NUMBER OF DISTINCTIVE RINGING PATTERNS]: Contains the following key: • 'Number of Distinctive Ringing Patterns' defining the number of Distinctive Ringing signals that are defined in the file.
Page 643: Prerecorded Tones File
Up to 40 tones (totaling approximately 10 minutes) can be stored in a single PRT file on the device's flash memory. The prerecorded tones are prepared offline using third- party recording utilities and combined into a single file, using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).
Page 644: Cas Files
Plans, as required. Save the file with the ini file extension name (e.g., mydialplanfile.ini). Convert the ini file to a dat binary file, using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide. Load the converted file to the device, as described in ''Loading Auxiliary Files'' on page 637.
Page 645: Dialing Plans For Digit Collection
• 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 646 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 637.
Page 647: Dial Plan Prefix Tags For Routing
Note: When using prefix tags, you need to configure manipulation rules to remove the tags before the device sends the calls to their destinations. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 648 Mediant 800B Gateway and E-SBC You configure prefix tags in the Dial Plan file, using the following syntax: [ PLAN<index> ] <prefix number>,0,<prefix tag> where:  Index is the Dial Plan index  prefix number is the called or calling number prefix (ranges can be defined in brackets) ...
Page 649 (Configuration tab > VoIP menu > GW and IP to IP > Manipulations > Source Number IP->Tel). In the 'Source Prefix' field, enter the prefix calling tag. In the 'Stripped Digits From Left' field, enter the number of characters in the prefix calling tag. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 650 Mediant 800B Gateway and E-SBC 41.1.4.3.2 Dial Plan Prefix Tags for SBC IP-to-IP Routing For deployments requiring many SBC IP-to-IP routing rules that exceed the maximum number of rules that can be configured in the IP-to-IP Routing table, you can employ user- defined string labels (tags) to represent the many different prefix calling (source) and called (destination) numbers.
Page 651: Obtaining Ip Destination From Dial Plan File
An example of a configured Dial Plan (# 6) in the Dial Plan file is shown below: [ PLAN6 ] 200,0,10.33.8.52 ; called prefix 200 is routed to 10.33.8.52 201,0,10.33.8.52 300,0,itsp.com ; called prefix 300 is routed to itsp.com Version 6.8 Mediant 800B Gateway and E-SBC...
Page 652: Modifying Isdn-To-Ip Calling Party Number
Mediant 800B Gateway and E-SBC Convert the file to a loadable file and then load it to the device (see ''Creating a Dial Plan File'' on page 644). Assign the Dial Plan index to the required routing rule: • SBC Calls: In the SBC IP-to-IP Routing table, do the following: Set the 'Destination Type' field to Dial Plan.
Page 653: User Information File
Note: If you have configured regular IP-to-Tel manipulation rules (see ''Configuring Source/Destination Number Manipulation'' on page 387), the device applies these rules before applying the mapping rules of the User Info table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 654 Mediant 800B Gateway and E-SBC • Tel-to-IP Calls: Maps the calling (source) PBX extension to the "global" number. For example, if the device receives a Tel call from PBX extension 402, it changes this calling number to 638002, and then sends call to the IP side with this calling number.
Page 655 The valid value is a string of up to 20 characters. mber] Display Name Defines the Caller ID of the PBX extension. [GWUserInfoTable_DisplayName] The valid value is a string of up to 30 characters. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 656 Mediant 800B Gateway and E-SBC Parameter Description Username Defines the username for registering the user when [GWUserInfoTable_Username] authentication is necessary. The valid value is a string of up to 40 characters. Password Defines the password for registering the user when [GWUserInfoTable_Password] authentication is necessary.
Page 657: User Information File For Sbc User Database
You can use the SBC User Info table for the following:  Registering each user to an external registrar server.  Authenticating (for any SIP request and as a client) each user if challenged by an external server. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 658 Mediant 800B Gateway and E-SBC  Authenticating as a server incoming user requests (for SBC security). If the device registers on behalf of users and the users do not perform registration, any SIP request destined to the user is routed to the Proxy Set associated with the user’s IP Group.
Page 659 To view all table entries: (sip-def-proxy-and-reg)# user-info sbc-user-info display ---- sbc-user-info-0 ---- local-user (JohnDee) username (userJohn) password (s3fn+fn=) ip-group-id (1) status (not-resgistered) ---- sbc-user-info-1 ---- local-user (SuePark) username (userSue) password (t6sn+un=) ip-group-id (1) status (not-resgistered) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 660 Mediant 800B Gateway and E-SBC  To view a specific entry (example): (sip-def-proxy-and-reg)# user-info sbc-user-info <index, e.g., 0> (sbc-user-info-0)# display local-user (JohnDee) username (userJohn) password (s3fn+fn=) ip-group-id (1) status (not-resgistered)  To search a user by local-user: (sip-def-proxy-and-reg)# user-info find <local-user, e.g., JohnDoe>...
Page 661: 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 662: Installing The Software License Key
 CLI - see Installing Software License Key using CLI  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non- volatile flash memory and overwrites the previously installed Software License Key.
Page 663: Installing Software License Key Using Cli
Open the Software License Key file and check that the "S/N" line appears. If it does not appear, contact AudioCodes. Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]".
Page 664: Software Upgrade Wizard
If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
Page 665 Select the Maintenance tab, click the Software Update menu, and then click Software Upgrade Wizard. • On the toolbar, click Device Actions, and then choose Software Upgrade Wizard. Figure 41-5: Start Software Upgrade Wizard Screen Version 6.8 Mediant 800B Gateway and E-SBC...
Page 666 Mediant 800B Gateway and E-SBC Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Figure 41-6: Software Upgrade Wizard - Load CMP File Note: At this stage, you can quit the Software Upgrade Wizard without having to reset the device, by clicking Cancel .
Page 667 (and do not select an ini file). • Restore configuration to factory defaults: Clear the 'Use existing configuration' check box (and do not select an ini file). Figure 41-8: Software Upgrade Wizard – Load INI File Version 6.8 Mediant 800B Gateway and E-SBC...
Page 668 Mediant 800B Gateway and E-SBC When you have completed loading all the desired files, click Next until the last wizard page appears (the FINISH button is highlighted in the left pane): Figure 41-9: Software Upgrade Wizard – Files Loaded Click Reset to burn the files to the device's flash memory;...
Page 669: Backing Up And Loading Configuration File
To save the ini file to a folder on your computer: Click the Save INI File button; the File Download dialog box appears. Click the Save button, navigate to the folder where you want to save the file, and then click Save. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 670 Mediant 800B Gateway and E-SBC To load the ini file to the device: Click the Browse button, navigate to the folder where the file is located, select the file, and then click Open; the name and path of the file appear in the field beside the Browse button.
Page 671: Automatic Update Mechanism
(dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server" directive may be used). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 672: Provisioning From Http Server Using Dhcp Option 67
Mediant 800B Gateway and E-SBC ddns-update-style ad-hoc; default-lease-time 60; max-lease-time 60; class "gateways" { match if(substring(hardware, 1, 3) = 00:90:8f); subnet 10.31.0.0 netmask 255.255.0.0 { pool { allow members of "audiocodes"; range 10.31.4.53 10.31.4.75; filename "SIP_F6.60A.217.003.cmp –fb;device.ini"; option routers 10.31.0.1;...
Page 673: Provisioning From Tftp Server Using Dhcp Option 66
HTTP server for file updates. HTTP(S) is not sensitive to NAT devices, enabling configuration whenever needed without on-site intervention. For additional security, the URL may contain a different port, and username and password. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 674: Ftp-Based Provisioning
URL is "ftp" (instead of "http"). 42.1.4 Provisioning using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections.
Page 675: Http/S-Based Provisioning Using The Automatic Update Feature
The Automatic Update feature is done per file and configured by specifying the file name and URL address of the provisioning server where the file is located. For a description of the parameters used to configure URLs per file, see Automatic Update Parameters. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 676: Triggers For Automatic Update
Upon receipt of an SNMP request from the provisioning server. • Upon receipt of a special SIP NOTIFY message from the provisioning server. The NOTIFY message includes an Event header with the AudioCodes proprietary value, "check-sync;reboot=false", as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...
Page 677: Access Authentication With Http Server
<CONF> - configuration version, as configured in the ini file parameter, INIFileVersion or CLI command, configuration-version The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 678 Mediant 800B Gateway and E-SBC User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld-<NAME>;<VER>(<MAC>), the device sends the following User-Agent header: User-Agent: MyWorld-Mediant;6.8.200.001(00908F1DD0D3) Note: If you configure the AupdHttpUserAgent parameter with the <CONF> variable tag, you must reset the device with a burn-to-flash for your settings to take effect.
Page 679: File Download Sequence
If you use the ResetNow parameter in an ini file for periodic automatic provisioning with non-HTTP (e.g., TFTP) and without CRC, the device resets after every file download. Therefore, use this parameter with caution and only if necessary for your deployment requirements. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 680: Cyclic Redundancy Check On Downloaded Configuration Files
Mediant 800B Gateway and E-SBC Notes: • For ini file downloads, by default, parameters not included in the file are set to defaults. To retain the current settings of these parameters, set the SetDefaultOnINIFileProcess parameter to 0. • If you have configured one-time software file (.cmp) download (configured by the ini file parameter CmpFileURL or CLI command configure system >...
Page 681: Mac Address Automatically Inserted In Configuration File Name
InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] • CLI: # configure voip (config-voip)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100 Configure the device with the following Automatic Update settings: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 682 Mediant 800B Gateway and E-SBC Automatic Update is done every 24 hours (1440 minutes): ♦ ini File: AutoUpdateFrequency = 1440 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 1440 Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp'...
Page 683: Automatic Update From Remote Servers
[ InterfaceTable ] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress, InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 684: Automatic Update For Mass Deployment
Mediant 800B Gateway and E-SBC Configure the device to perform the Automatic Update process daily at 03:00 (3 a.m): AutoUpdatePredefinedTime = '03:00' 42.2.9.3 Automatic Update for Mass Deployment This example describes how to configure the Automatic Update feature for updating multiple devices (i.e., mass deployment) using an HTTP provisioning server.
Page 685 InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] ♦ CLI: # configure voip (config-voip)# interface network-if 0 (network-if-0)# primary-dns 80.179.52.100 Power down and then power up the device. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 686 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 687: Restoring Factory Defaults
At the prompt, type the password again, and then press Enter: # Password: Admin At the prompt, type the following to reset the device to default settings, and then press Enter: # write factory Version 6.8 Mediant 800B Gateway and E-SBC...
Page 688: Restoring Defaults Using Hardware Reset Button
Mediant 800B Gateway and E-SBC 43.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 689: Saving Current Configuration To A File And Sending It To Remote Destination
For example: # write-and-backup to tftp://192.168.0.3/config-device1.txt  Creating a Configuration file and saving it on a USB stick plugged into the device: # write-and-backup to usb:///<file name> For example: # write-and-backup to usb:///config-device1.txt Version 6.8 Mediant 800B Gateway and E-SBC...
Page 690 Mediant 800B Gateway and E-SBC This page is left intentionally blank. User's Manual Document #: LTRT-10620...
Page 691: Usb Storage Capabilities
 To save the current configuration to the USB: # copy voice-configuration to usb:///<ini configuration file name> Note: Only a single USB storage (formatted to FAT/FAT32) operation is supported at any given time. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 692 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 693: Status, Performance Monitoring And Reporting
Part X Status, Performance Monitoring and Reporting...
Page 695: 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 623). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 696: Viewing Ethernet Port Information
Mediant 800B Gateway and E-SBC 46.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information about the Ethernet Port Group connections.  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu >...
Page 697: Carrier-Grade Alarms
 Description: brief explanation of the alarm  Date: date and time that the alarm was generated You can view the next 20 alarms (if exist), by clicking the Go to page button. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 698: Viewing Alarm History
Mediant 800B Gateway and E-SBC 47.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 699: Performance Monitoring
As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 700: Viewing Trunk Utilization
Mediant 800B Gateway and E-SBC 48.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 701: Viewing Quality Of Experience
Dialog Failed Attempts: displays the failed call attempts. This includes the number of calls and subscribes which were successfully and abnormally terminated.  Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 702 Mediant 800B Gateway and E-SBC  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 48-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 703: Viewing Average Call Duration
As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 704 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 705: Voip Status
Gray Disabled Active - OK Green Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm NFAS Alarm Dark Orange Purple Lower Layer Down (DS3 physical layer is disabled) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 706 Mediant 800B Gateway and E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 49-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls...
Page 707: Viewing Analog Port Information
For more information, see ''Performing Manual D-Channel Switchover in NFAS Group'' on page 374. Note: This page is applicable only to T1 ISDN protocols supporting NFAS, and only if the NFAS group is configured with two D-channels. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 708: Viewing Active Ip Interfaces
Mediant 800B Gateway and E-SBC  To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure 49-4: NFAS Group & D-Channel Status Page 49.4...
Page 709: Viewing Ethernet Device Status
Viewing Performance Statistics The Basic Statistics page provides read-only, device performance statistics. This page is refreshed every 60 seconds. The duration that the currently displayed statistics has been collected is displayed above the statistics table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 710: Viewing Cdr History
Mediant 800B Gateway and E-SBC  To view performance statistics:  Open the Basic Statistics page (Status & Diagnostics tab > VoIP Status menu > Performance Statistics). Figure 49-6: Basic Statistics Page The duration that the displayed statistics were collected is displayed in seconds above the table.
Page 711: Viewing Call Counters
The release reason can be viewed in the 'Termination Reason' field in the CDR message. You can reset the statistical data displayed on the page (i.e., refresh the display), by clicking the Reset Counters button located below the table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 712 Mediant 800B Gateway and E-SBC  To view IP-to-Tel and Tel-to-IP call counters:  Open the Call Counters page that you want to view (Status & Diagnostics tab > VoIP Status menu > IP to Tel Calls Count or Tel to IP Calls Count); the figure below shows the IP to Tel Calls Count page.
Page 713: Viewing Registered Sas/Sbc Users
An AOR is a SIP or SIPS URI that points to a domain with a location service that can map the URI to another URI (contact) where the user might be available. A contact is a SIP URI Version 6.8 Mediant 800B Gateway and E-SBC...
Page 714: Viewing Registration Status
Mediant 800B Gateway and E-SBC that can be used to contact that specific instance of the user agent for subsequent requests.  To view registered SAS/SBC users in the Users Registration database:  Web: SAS/SBC Registered Users page (Status & Diagnostics tab > VoIP Status menu >...
Page 715: Viewing Call Routing Status
Routing Table = Calls are routed using the routing table:  Gateway calls: Outbound IP Routing table (Configuring Outbound IP Routing Table on page 411)  SBC calls: SBC IP-to-IP Routing table (Configuring SBC IP-to-IP Routing Rules on page 571) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 716: Viewing Ip Connectivity
Mediant 800B Gateway and E-SBC Parameter Description  Not Used = Proxy server isn't defined. IP Address  IP address and FQDN (if exists) of the Proxy server with which the device currently operates.  N/A = Proxy server isn't defined.
Page 717  This parameter is reset if no QoS information is received for 2 minutes. DNS Status DNS status can be one of the following:  DNS Disable  DNS Resolved  DNS Unresolved Version 6.8 Mediant 800B Gateway and E-SBC...
Page 718 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 719: Reporting Information To External Party
Start timestamp in the RTCP XR indicates the start of the media segment; the End timestamp indicates the time of the last sent periodic RTCP XR (typically, up to 5 seconds before reported segment ends). device Version 6.8 Mediant 800B Gateway and E-SBC...
Page 720 Mediant 800B Gateway and E-SBC Table 50-1: RTCP XR Published VoIP Metrics Group Metric Name General Start Timestamp Stop Timestamp Call-ID Local Address (IP, Port & SSRC) Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate...
Page 721 RemoteID: <sip:2000@172.17.116.202;user=phone> OrigID: <sip:1000@172.17.116.201> LocalAddr: IP=172.17.116.201 Port=6000 SSRC=0x54c62a13 RemoteAddr: IP=172.17.116.202 Port=6000 SSRC=0x243220dd LocalGroup: RemoteGroup: LocalMAC: 00:90:8f:57:d9:71 LocalMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z SessionDesc: PT=8 PD=PCMA SR=8000 FD=20 PLC=3 SSUP=Off JitterBuffer: JBA=3 JBR=0 JBN=7 JBM=10 JBX=300 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 722 Mediant 800B Gateway and E-SBC PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=6325 GMIN=16 Delay: RTD=0 ESD=11 Signal: SL=-34 NL=-67 RERL=17 QualityEst: RLQ=93 MOSLQ=4.1 MOSCQ=4.10 RemoteMetrics: Timestamps: START=2015-12-16T20:09:45Z STOP=2015-12-16T20:09:52Z JitterBuffer: JBA=3 JBR=0 JBN=0 JBM=0 JBX=300 PacketLoss: NLR=0.00 JDR=0.00 BurstGapLoss: BLD=0.00 BD=0 GLD=0.00 GD=0 GMIN=16...
Page 723 - enables the sending of RTCP XR reports of QoE metrics at the end of each call session (i.e., after a SIP BYE). Click Submit, and then reset the device with a save ("burn") for your settings to take effect. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 724: Generating Call Detail Records
Mediant 800B Gateway and E-SBC 50.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 725: Cdr Field Description
String of up to 10 characters DestIp Destination IP address String of up to 20 characters DestPort Destination UDP port String of up to 10 characters TransportType Transport type: String  "UDP"  "TCP" Version 6.8 Mediant 800B Gateway and E-SBC...
Page 726 Mediant 800B Gateway and E-SBC CDR Field Name Description Format  "TLS" SrcURI Source URI String of up to 41 characters SrcURIBeforeMap Source URI before manipulation String of up to 41 characters DstURI Destination URI String of up to 41 characters...
Page 727 [S=40] |SBCReportType |EPTyp |SIPCallId |SessionId |Orig |SourceIp |SourcePort |DestIp |DestPort |TransportType |SrcURI |SrcURIBeforeMap |DstURI |DstURIBeforeMap |Durat |TrmSd |TrmReason |TrmReasonCategory |SetupTime |ConnectTime |ReleaseTime |RedirectReason |RedirectURINum |RedirectURINumBeforeMap |TxSigIPDiffServ|IPGroup (description) |SrdId (name) |SIPInterfaceId |ProxySetId |IpProfileId (name) |MediaRealmId Version 6.8 Mediant 800B Gateway and E-SBC...
Page 728: Cdr Fields For Sbc Media
Mediant 800B Gateway and E-SBC (name) |DirectMedia |SIPTrmReason |SIPTermDesc |Caller |Callee [S=41] |CALL_END |SBC |20767593291410201017029@10.33.45.80 |1871197419|LCL |10.33.45.80 |5060 |10.33.45.72 |5060 |UDP |9001@10.8.8.10 |9001@10.8.8.10 |6001@10.33.45.80 |6001@10.33.45.80 |15 |LCL |GWAPP_NORMAL_CALL_CLEAR |NORMAL_CALL_CLEAR |17:00:29.954 UTC Thu Oct 14 2014 |17:00:49.052 UTC Thu Oct 14 2014 |17:01:04.953...
Page 729: Cdr Fields For Gateway/Ip-To-Ip Application
Note: This field is applicable only to the Gateway application. ConId SIP conference ID Note: This field is applicable only to the Gateway application. Trunk Group ID Note: This field is applicable only to the Gateway application. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 730 Mediant 800B Gateway and E-SBC Field Name Description EPTyp Endpoint type:    EANDM  ISDN    IPMEDIA  NETANN  STREAMING  TRANSPARENT  MSCML  VXML  IP2IP Orig Call originator:  LCL (Tel side) ...
Page 731 Data is stored per call and sent in the syslog as follows:  currency-type: amount multiplier for currency charge (euro or usd)  recorded-units: for unit charge (1-999999) Mult 0,001-1000 (in steps of 10) (See explanation above.) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 732 Mediant 800B Gateway and E-SBC 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_LEFT RESOURCE_BECAUSE_NO_TRANSCODING_RESOURCES_L EFT, RELEASE_BECAUSE_GW_LOCKED  NO_MATCH - RELEASE_BECAUSE_UNMATCHED_CAPABILITIES ...
Page 733: Release Reasons In Cdr
"RELEASE_BECAUSE_UNKNOWN_REASON"  "RELEASE_BECAUSE_REMOTE_CANCEL_CALL"  "RELEASE_BECAUSE_UNMATCHED_CAPABILITIES"  "RELEASE_BECAUSE_UNMATCHED_CREDENTIALS"  "RELEASE_BECAUSE_UNABLE_TO_HANDLE_REMOTE_REQUEST"  "RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT"  "RELEASE_BECAUSE_CONFERENCE_FULL"  "RELEASE_BECAUSE_VOICE_PROMPT_PLAY_ENDED"  "RELEASE_BECAUSE_VOICE_PROMPT_NOT_FOUND"  "RELEASE_BECAUSE_TRUNK_DISCONNECTED"  "RELEASE_BECAUSE_RSRC_PROBLEM"  "RELEASE_BECAUSE_MANUAL_DISC"  "RELEASE_BECAUSE_SILENCE_DISC"  "RELEASE_BECAUSE_RTP_CONN_BROKEN"  "RELEASE_BECAUSE_DISCONNECT_CODE"  "RELEASE_BECAUSE_GW_LOCKED"  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS" Version 6.8 Mediant 800B Gateway and E-SBC...
Page 734 Mediant 800B Gateway and E-SBC  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "  "GWAPP_PREEMPTION"  "PREEMPTION_CIRCUIT_RESERVED_FOR_REUSE"  "GWAPP_NORMAL_CALL_CLEAR"  "GWAPP_USER_BUSY"  "GWAPP_NO_USER_RESPONDING"  "GWAPP_NO_ANSWER_FROM_USER_ALERTED"  "MFCR2_ACCEPT_CALL"  "GWAPP_CALL_REJECTED"...
Page 735 "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED"  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING"  "GWAPP_MESSAGE_TYPE_NON_EXISTENT"  "GWAPP_MESSAGE_STATE_INCONSISTENCY"  "GWAPP_NON_EXISTENT_IE"  "GWAPP_INVALID_IE_CONTENT"  "GWAPP_MESSAGE_NOT_COMPATIBLE"  "GWAPP_RECOVERY_ON_TIMER_EXPIRY"  "GWAPP_PROTOCOL_ERROR_UNSPECIFIED"  "GWAPP_INTERWORKING_UNSPECIFIED"  "GWAPP_UKNOWN_ERROR"  "RELEASE_BECAUSE_HELD_TIMEOUT" Version 6.8 Mediant 800B Gateway and E-SBC...
Page 736: Configuring Radius Accounting
Mediant 800B Gateway and E-SBC 50.3 Configuring RADIUS Accounting The device can send accounting data of SIP calls as call detail records (CDR) to 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. For a list of the CDR attributes, see the table following the procedure below.
Page 737 H323- Q.931 disconnect Numeric Stop Disconnect- cause code Cause h323-gw-id Name of the String SIPIDString Start gateway Stop sip-call-id SIP Call ID String abcde@ac.com Start Stop call- Terminator of the String call-terminator=yes Stop Version 6.8 Mediant 800B Gateway and E-SBC...
Page 738 Mediant 800B Gateway and E-SBC Vendor Specific Attribute Attribute Value Attribute Purpose Example Number Name Format (VSA) terminator call:  "yes": Call terminated by the Tel side (Gateway) or outgoing leg (SBC)  "no": Call terminated by the IP side...
Page 739 Below is an example of RADIUS Accounting, where the non-standard parameters are preceded with brackets: Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213 nas-port-type = 0 acct-status-type = 2 acct-input-octets = 4841 acct-output-octets = 8800 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 740: Event Notification Using X-Detect Header
Mediant 800B Gateway and E-SBC acct-session-time = 1 acct-input-packets = 122 acct-output-packets = 220 called-station-id = 201 calling-station-id = 202 // Accounting non-standard parameters: (4923 33) h323-gw-id = (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 3fd61009 0e2f3cc5...
Page 741 Once the device receives such a request, it sends a SIP response message (using the X-Detect header) to the remote party, listing all supported events that can be detected. The absence of the X-Detect header indicates that no detections are available. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 742 Mediant 800B Gateway and E-SBC Each time the device detects a supported event, the event is notified to the remote party by sending an INFO message with the following message body: • Content-Type: application/X-DETECT • Type = [ CPT | FAX | PTT…] •...
Page 743: Querying Device Channel Resources Using Sip Options
In the example above, "telchs" specifies the number of available channels and the number of occupied channels (4 channels are occupied and 12 channels are available). Note: This feature is applicable only to the Gateway / IP-to-IP application. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 744 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 745: Diagnostics
Part XI Diagnostics...
Page 747: Syslog And Debug Recordings
Syslog message, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv Version 6.8 Mediant 800B Gateway and E-SBC...
Page 748: Event Representation In Syslog Messages
Mediant 800B Gateway and E-SBC Message Item Description <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237][SID:1034099026] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE:...
Page 749 RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Invalid Header Length Invalid Codec Type Unknown Aggregation Payload Type Invalid Routing Flag Received Version 6.8 Mediant 800B Gateway and E-SBC...
Page 750: Identifying Audiocodes Syslog Messages Using Facility Levels
Mediant 800B Gateway and E-SBC 51.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 751: Snmp Alarms In Syslog Messages
For viewing Syslog messages in the Web interface, see ''Viewing Syslog Messages'' on page 757. • For a detailed description on the Syslog parameters, see ''Syslog, CDR and Debug Parameters'' on page 812. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 752 Mediant 800B Gateway and E-SBC  To enable Syslog: Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Figure 51-1: Syslog Settings Page Enable the Syslog feature by setting 'Enable Syslog' to Enable. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port' parameters.
Page 753: Configuring Web Operations To Report To Syslog
Debug recording is collected only on the device's OAMP interface. • You can also save debug recordings to an external USB hard drive that is connected to the device's USB port. For more information, see USB Storage Capabilities on page 691. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 754: Filtering Syslog Messages And Debug Recordings
Mediant 800B Gateway and E-SBC  To configure and activate debug recording: Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings). Figure 51-3: Logging Settings Page Configure the debug capturing server using the 'Debug Recording Destination IP' and 'Debug Recording Destination Port' parameters.
Page 755 The value can be the following:  A single value  A range, using a hyphen "-" between the two values, e.g., "1-3"  Multiple, non-contiguous values, using commas "," between each value, e.g., "1,3,9" Version 6.8 Mediant 800B Gateway and E-SBC...
Page 756: Filtering Ip Network Traces
Mediant 800B Gateway and E-SBC Parameter Description  Trunks/FXO/FXS pertaining to a module, using the syntax module number/port or port, for example:  "1/2", means module 1, port 2  "1/[2-4]", means module 1, ports 2 through 4  Any to indicate all ...
Page 757: 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.8...
Page 758 Mediant 800B Gateway and E-SBC  To activate the Web interface's Message Log: Enable Syslog (see ''Enabling Syslog'' on page 751). Open the Message Log page (Status & Diagnostics tab > System Status menu > Message Log); the Message Log page is displayed and the log is activated.
Page 759: Collecting Debug Recording Messages
User's Manual 51. Syslog and Debug Recordings 51.7 Collecting Debug Recording Messages To collect debug recording packets, use the open source program Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...
Page 760: Debug Capturing On Physical Voip Interfaces
Mediant 800B Gateway and E-SBC 51.8 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets). The captured traffic can be saved in a PCAP-format file (suitable for Wireshark) to a TFTP (default) or an FTP server. The generated PCAP file is in the Extensible Record Format (ERF).
Page 761: Self-Testing
Startup Test (automatic): This hardware test has minor impact in real-time. While this test is executed, the regular operation of the device is disabled. If an error is detected, an error message is sent to the Syslog. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 762 Mediant 800B Gateway and E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10620...
Page 763: Creating Core Dump And Debug Files Upon Device Crash
The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. The files can then be sent to AudioCodes support team for troubleshooting. ...
Page 764 Mediant 800B Gateway and E-SBC The following procedure describes how to retrieve the debug file from the device in the Web interface.  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button.
Page 765: Analog Line Testing
 Coefficients checksum  Message waiting indication status  Ring state  Reversal polarity state Note: Use the Analog Line testing mechanism only for monitoring and never when there are calls in progress. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 766 Mediant 800B Gateway and E-SBC This page is left intentionally blank. User's Manual Document #: LTRT-10620...
Page 767: Testing Sip Signaling Calls
The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call or CLI command, configure system > test-call > test-call-table. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 768 Mediant 800B Gateway and E-SBC  To configure a test call: Open the Test Call Table page (Configuration tab > System menu > Test Call > Test Call Table). Click Add; the following dialog box appears: Figure 55-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
Page 769 'Destination Address' or 'IP [Test_Call_AutoRegister] Group ID' parameter settings (see above).  [0] Disable (default)  [1] Enable Username Defines the authentication username. CLI: user-name By default, no username is defined. [Test_Call_UserName] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 770 Mediant 800B Gateway and E-SBC Parameter Description Password Defines the authentication password. CLI: password By default, no password is defined. [Test_Call_Password] Test Settings Tab Call Party Defines whether the test endpoint is the initiator or receiving side CLI: call-party of the test call.
Page 771: Starting And Stopping Test Calls
"Done": test call has been successfully completed (or was prematurely stopped by clicking the Drop Call command) A more detailed description of this field is displayed below the table when you click the Show/Hide button (see ''Viewing Test Call Statistics'' on page 772). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 772: Viewing Test Call Statistics
Mediant 800B Gateway and E-SBC 55.3 Viewing Test Call Statistics In addition to viewing a brief status description of the test call in the 'Test Status' field (as described in ''Starting, Stopping and Restarting Test Calls'' on page 771), you can also view a more detailed status description which includes test call statistics.
Page 773: Configuring Dtmf Tones For Test Calls
Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 55-3: DTMF in Test Call Settings Page In the 'Test Call DTMF String' field, enter the DTMF string (up to 15 digits). Click Submit. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 774: Configuring Basic Test Call
Mediant 800B Gateway and E-SBC 55.5 Configuring Basic Test Call The Basic Test Call feature tests incoming Gateway calls from a remote SIP endpoint to a simulated test endpoint on the device. The only required configuration is to assign a prefix number (test call ID) to the simulated endpoint.
Page 775: Configuring Sbc Test Call With External Proxy
The device receives the call from the proxy server. As the 'Test Call ID' parameter is set to "101", the device identifies the incoming call as a test call and sends it directly to the simulated test endpoint "101". Version 6.8 Mediant 800B Gateway and E-SBC...
Page 776: Test Call Configuration Examples
Mediant 800B Gateway and E-SBC  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Parameters'' on page 810): Open the Test Call Settings page (Configuration tab > System menu > Test Call >...
Page 777 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 778 Mediant 800B Gateway and E-SBC  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and pas,sword) process of a simulated test endpoint on the device with an external proxy/registrar server. This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another.
Page 779: Appendix
Part XII Appendix...
Page 781: Dialing Plan Notation For Routing And Manipulation
[100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc.  03(5xx): for any number that starts with 03 and ends with 5xx. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 782 Mediant 800B Gateway and E-SBC Notation Description  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.  Only numerical ranges are supported (not alphabetical letters).
Page 783: Configuration Parameters Reference
When this duration expires, the password of the Web user must be changed. The valid value is 0 to 100000, where 0 means that the password is always valid. The default is 1140. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 784 Mediant 800B Gateway and E-SBC Parameter Description Note: This parameter is applicable only when using the Web Users table, where the default value of the 'Password Age' parameter in the Web Users table inherits this parameter's value. Web: User Inactivity Timer...
Page 785 (set acSysActionSetResetControl to 1 and acSysActionSetReset to 1). 2) Change the username and password in the acSysWEBAccessEntry table. Use the following format: Username acSysWEBAccessUserName: old/pass/new Password acSysWEBAccessUserCode: username/old/new Version 6.8 Mediant 800B Gateway and E-SBC...
Page 786 Mediant 800B Gateway and E-SBC Parameter Description [WelcomeMessage] Enables and defines a Welcome message that appears on the Web Login page for logging in to the Web interface. The format of this parameter is as follows: [WelcomeMessage ] FORMAT WelcomeMessage_Index = WelcomeMessage_Text...
Page 787: Telnet Parameters
 The password is case-sensitive.  The password is required only by Admin and Monitor user access levels; Security Administrator and Master user access levels automatically enter the Enable mode upon initial login. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 788: Ini File Parameters
The valid range is a string of up to 64 characters. [SendKeepAliveTrap] Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
Page 789 This parameter can be controlled by the Config Global Entry Limit MIB (located in the Notification Log MIB). The valid range is 50 to 1000. The default is 500. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 790 Mediant 800B Gateway and E-SBC Parameter Description CLI: engine-id Defines the SNMP engine ID for SNMPv2/SNMPv3 agents. This [SNMPEngineIDString] is used for authenticating a user attempting to access the SNMP agent on the device. The ID can be a string of up to 36 characters. The default is 00:00:00:00:00:00:00:00:00:00:00:00 (12 Hex octets characters).
Page 791 Trusted managers can work with all community strings. SNMP V3 Users Table This parameter table defines SNMP v3 users. The format of this Web/EMS: SNMP V3 Users CLI: configure system > snmp v3- parameter is as follows: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 792 Mediant 800B Gateway and E-SBC Parameter Description users [SNMPUsers] [SNMPUsers] FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol, SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, SNMPUsers_Group; [\SNMPUsers] For example: SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1; The example above configures user 'v3admin1' with security level authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2.
Page 793: Serial Parameters
Note: For this parameter to take effect, a device reset is required. EMS: Flow Control Defines the RS-232 flow control. [SerialFlowControl]  [0] = (Default) None  [1] = Hardware Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 794: Auxiliary And Configuration File Name Parameters
0 is Trunk 1. Web: Dial Plan File Defines the name (and path) of the Dial Plan file. This file should be EMS: Dial Plan File Name created using AudioCodes DConvert utility (refer to DConvert Utility [DialPlanFileName] User's Guide). [UserInfoFileName] Defines the name (and path) of the file containing the User Information data.
Page 795: Automatic Update Parameters
User-Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld- <NAME>;<VER>(<MAC>), the device sends the following User- Agent header: User-Agent: MyWorld- Mediant;6.80.200.001(00908F1DD0D3) Notes:  The variable tags are case-sensitive. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 796 Mediant 800B Gateway and E-SBC Parameter Description  If you configure the parameter with the <CONF> variable tag, you must reset the device with a burn-to-flash for your settings to take effect.  The tags can be defined in any order.
Page 797 The case-sensitive string, "<MAC>" can be used in the file name for instructing the device to replace it with the device's MAC address. For more information, see MAC Address Automatically Inserted in Configuration File Name on page 681. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 798 Mediant 800B Gateway and E-SBC Parameter Description  The maximum length of the URL address is 99 characters. CLI: prerecorded-tones Defines the name of the Prerecorded Tones (PRT) file and the path [PrtFileURL] to the server (IP address or FQDN) on which it is located.
Page 799: Networking Parameters
FORMAT EtherGroupTable_Index = EtherGroupTable_Group, [EtherGroupTable] EtherGroupTable_Mode, EtherGroupTable_Member1, EtherGroupTable_Member2; [\EtherGroupTable] For a description of this parameter, see Configuring Ethernet Port Groups on page 119. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 800: Multiple Voip Network Interfaces And Vlan Parameters
Mediant 800B Gateway and E-SBC 57.2.2 Multiple VoIP Network Interfaces and VLAN Parameters The IP network interfaces and VLAN parameters are described in the table below. Table 57-10: IP Network Interfaces and VLAN Parameters Parameter Description Interface Table Web: Interface Table This table parameter configures the Interface table.
Page 801: Open Solution Network (Osn) Parameters
The format of this ini file is as follows: vlan-mapping [ DiffServToVlanPriority ] [DiffServToVlanPriority] FORMAT DiffServToVlanPriority_Index = DiffServToVlanPriority_DiffServ, DiffServToVlanPriority_VlanPriority; [ \DiffServToVlanPriority ] For example: DiffServToVlanPriority 0 = 46, 6; DiffServToVlanPriority 1 = 40, 6; DiffServToVlanPriority 2 = 26, 4; Version 6.8 Mediant 800B Gateway and E-SBC...
Page 802: Nat Parameters
Mediant 800B Gateway and E-SBC Parameter Description DiffServToVlanPriority 3 = 10, 2; For a description of this table, see Configuring Quality of Service on page 134. Note: For this parameter to take effect, a device reset is required. Layer-3 Class of Service (TOS/DiffServ) Parameters...
Page 803 1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.
Page 804: Dns Parameters
Mediant 800B Gateway and E-SBC 57.2.7 DNS Parameters The Domain name System (DNS) parameters are described in the table below. Table 57-15: DNS Parameters Parameter Description Internal DNS Table Web: Internal DNS Table This table parameter defines the internal DNS table for resolving host EMS: DNS Information names into IP addresses.
Page 805: Dhcp Parameters
DhcpServer_SubnetMask, DhcpServer_LeaseTime, DhcpServer_DNSServer1, DhcpServer_DNSServer2, DhcpServer_NetbiosNameServer, DhcpServer_NetbiosNodeType, DhcpServer_NTPServer1, DhcpServer_NTPServer2, DhcpServer_TimeOffset, DhcpServer_TftpServer, DhcpServer_BootFileName, DhcpServer_ExpandBootfileName, DhcpServer_OverrideRouter, DhcpServer_SipServer, DhcpServer_SipServerType; [ \DhcpServer ] For a detailed description of this table, see Configuring the Device's DHCP Server on page 193. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 806 Mediant 800B Gateway and E-SBC Parameter Description DHCP Vendor Class Table Web: DHCP Vendor Defines Vendor Class Identifier (VCI) names (DHCP Option 60) for the Class table device's DHCP server. Only if the DHCPDiscover request message, CLI: configure voip >...
Page 807: Ntp And Daylight Saving Time Parameters
The valid value is a string of up to 32 characters. By default, no key auth-key-md5 is defined. [ntpAuthMd5Key] Daylight Saving Time Parameters Web: Day Light Saving Time Enables daylight saving time. EMS: Mode  [0] Disable (default) CLI: summer-time  [1] Enable [DayLightSavingTimeEnable] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 808 Mediant 800B Gateway and E-SBC Parameter Description Web: Start Time / Day of Defines the date and time when daylight saving begins. This value Month Start can be configured using any of the following formats: EMS: Start  Day of year - mm:dd:hh:mm, where: CLI: start ...
Page 809: Debugging And Diagnostics Parameters
If the device is in Lifeline mode and the scenario that caused it to enter Lifeline (e.g., power outage) no longer exists (e.g., power returns), the device exists Lifeline and operates as normal.  [0] = (Default) Lifeline is activated upon power outage. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 810 Mediant 800B Gateway and E-SBC Parameter Description  [1] = Lifeline is activated upon power outage.  [2] = Lifeline is activated upon a power outage network failure (logical link disconnection), or when the Trunk Group is in Busy Out state (see the EnableBusyOut parameter).
Page 811: Sip Test Call Parameters
Test_Call_DestAddress, Test_Call_DestTransportType, Test_Call_SRD, Test_Call_ApplicationType, Test_Call_AutoRegister, Test_Call_UserName, Test_Call_Password, Test_Call_CallParty, Test_Call_MaxChannels, Test_Call_CallDuration, Test_Call_CallsPerSecond, Test_Call_TestMode, Test_Call_TestDuration, Test_Call_Play, Test_Call_ScheduleInterval, Test_Call_QOEProfile, Test_Call_BWProfile; [ \Test_Call ] For a description of this table, see ''Configuring Test Call Endpoints'' on page 767. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 812: Syslog, Cdr And Debug Parameters
Mediant 800B Gateway and E-SBC 57.3.3 Syslog, CDR and Debug Parameters The Syslog, CDR and debug parameters are described in the table below. Table 57-20: Syslog, CDR and Debug Parameters Parameter Description Web: Enable Syslog Determines whether the device sends logs and error messages (e.g., EMS: Syslog enable CDRs) generated by the device to a Syslog server.
Page 813 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the 'acsyslog' filter instead of the regular 'syslog' filter.
Page 814 Mediant 800B Gateway and E-SBC Parameter Description Web: Syslog Optimization Enables the device to accumulate and bundle multiple debug messages into a single UDP packet and then send it to a Syslog CLI: configure server. The benefit of this feature is that it reduces the number of system/logging/syslog- UDP Syslog packets, thereby improving (optimizing) CPU utilization.
Page 815 (2) Subnet Mask  (3) Default Gateway IP Address  (4) ActivityListToLog  [ll] Login and Logout = Web login and logout attempts. Note: For the ini file parameter, enclose values in single quotation Version 6.8 Mediant 800B Gateway and E-SBC...
Page 816 Mediant 800B Gateway and E-SBC Parameter Description marks, for example: ActivityListToLog = 'pvc', 'afl', 'dr', 'fb', 'swu', 'ard', 'naa', 'spc'. CLI: isdn-facility-trace Enables ISDN traces of Facility Information Elements (IE) for ISDN [FacilityTrace] call diagnostics. This allows you to trace all the parameters contained in the Facility IE and view them in the Syslog.
Page 817: Resource Allocation Indication Parameters
"Device 1" for the active device and "Device 2" for the redundant device. [HAUnitIdName] HA Remote Address Defines the Maintenance interface address of the redundant device in the HA system. configure system > high-availability > By default, no value is defined. remote-address [HARemoteAddress] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 818 Mediant 800B Gateway and E-SBC Parameter Description HA Revertive Enables HA switchover based on HA priority.  configure system > [0] Disable (default) = A switchover over to the redundant device is high-availability > done only if a failure occurs in the currently active device.
Page 819: Security Parameters
 [2] Dynamic-Strict = Device latches onto the first stream. If it receives at least a minimum number of consecutive packets (configured by New<media type>StreamPackets) all from the Version 6.8 Mediant 800B Gateway and E-SBC...
Page 820 Mediant 800B Gateway and E-SBC Parameter Description same source which is different to the first stream and the device has not received packets from the current stream for a user- defined period (TimeoutToRelatch<media type>Msec), it latches onto the next packet received from any other stream. If...
Page 821: Https Parameters
[0] Basic Mode =Basic authentication (clear text) is used. CLI: http-auth-mode  [1] Web Based Authentication = (Default) Digest [WebAuthMode] authentication (MD5) is used. Note: If you enable RADIUS login (i.e., the WebRADIUSLogin Version 6.8 Mediant 800B Gateway and E-SBC...
Page 822: Srtp Parameters
Mediant 800B Gateway and E-SBC Parameter Description parameter is set to 1), you must set the WebAuthMode parameter to Basic Mode [0]. Web: Requires Client Certificates Determines whether client certificates are required for HTTPS for HTTPS connection connection. CLI: req-client-cert ...
Page 823 [0] Enable (default) AuthenticationDisable Tx  [1] Disable CLI: RTP-authentication- disable-tx [RTPAuthenticationDisableTx] Web: Disable Encryption On Enables encryption on transmitted RTP packets in a secured RTP Transmitted RTP Packets session. EMS: RTP EncryptionDisable Version 6.8 Mediant 800B Gateway and E-SBC...
Page 824: Tls Parameters
Mediant 800B Gateway and E-SBC Parameter Description  [0] Enable (default) CLI: RTP-encryption-disable-tx  [1] Disable [RTPEncryptionDisableTx] Web: Disable Encryption On Enables encryption on transmitted RTCP packets in a secured Transmitted RTCP Packets RTP session. EMS: RTCP EncryptionDisable  [0] Enable (default) ...
Page 825 Otherwise, the connection is terminated. Note: If you set this parameter to [2] (Server & Client), for this functionality to operate, you also need to set the SIPSRequireClientCertificate parameter to [1] (Enable). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 826 Mediant 800B Gateway and E-SBC Parameter Description Web: TLS Client Verify Server Determines whether the device, when acting as a client for TLS Certificate connections, verifies the Server certificate. The certificate is EMS: Verify Server Certificate verified with the Root CA information.
Page 827: Ssh Parameters
Defines the maximum SSH login attempts allowed for entering an CLI: ssh-max-login-attempts incorrect password by an administrator before the SSH session is [SSHMaxLoginAttempts] rejected. The valid range is 1 to 3. the default is 3. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 828: Ids Parameters
Mediant 800B Gateway and E-SBC 57.4.6 IDS Parameters The Intrusion Detection System (IDS) parameters are described in the table below. Table 57-28: IDS Parameters Parameter Description Web: Intrusion Detection Enables the IDS feature. System (IDS)  [0] Disable (default) CLI: enable-ids ...
Page 829: Quality Of Experience Parameters
The Quality of Experience (QoE) parameters are described in the table below. Table 57-29: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of AudioCodes primary Session Experience CLI: configure voip/qoe Manager (SEM) server to where the quality experience reports are configuration/server-ip sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
Page 830 Mediant 800B Gateway and E-SBC Parameter Description [BWProfile] FORMAT BWProfile_Index = BWProfile_Name, BWProfile_EgressAudioBandwidth, BWProfile_IngressAudioBandwidth, BWProfile_EgressVideoBandwidth, BWProfile_IngressVideoBandwidth, BWProfile_TotalEgressBandwidth, BWProfile_TotalIngressBandwidth, BWProfile_WarningThreshold, BWProfile_hysteresis, BWProfile_GenerateAlarms; [\BWProfile] For a detailed description of this table, see ''Configuring Bandwidth Profiles'' on page 258. Note: For this parameter to take effect, a device reset is required.
Page 831: 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) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 832 Mediant 800B Gateway and E-SBC Parameter Description For a description o this table, see Configuring Authentication on page 495. Note: The indexing of this parameter starts at 0. Account Table Web: Account Table This table parameter configures the Account table for EMS: SIP Endpoints >...
Page 833 Determines the routing mode after a call redirection (i.e., a 3xx EMS: SIP Re-Routing Mode SIP response is received) or transfer (i.e., a SIP REFER CLI: sip-rerouting-mode request is received). [SIPReroutingMode]  [0] Standard = (Default) INVITE messages that are Version 6.8 Mediant 800B Gateway and E-SBC...
Page 834 Mediant 800B Gateway and E-SBC Parameter Description 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.  [1] Proxy = Sends a new INVITE to the Proxy.
Page 835 This parameter is applicable only to the Gateway application.  This parameter is applicable only if single device registration is used (i.e., the parameter AuthenticationMode is set to authentication per gateway).  Instead of configuring this parameter, the Authentication Version 6.8 Mediant 800B Gateway and E-SBC...
Page 836 Mediant 800B Gateway and E-SBC Parameter Description table can be used (see Authentication on page 495). Web/EMS: Password Defines the password for Basic/Digest authentication with a CLI: password-4-auth Proxy/Registrar server. A single password is used for all device [Password] ports.
Page 837 Registrar server. The IP address is in dotted-decimal CLI: ip-addrr-rgstrr notation, e.g., 201.10.8.1:<5080>. [RegistrarIP] Notes:  This parameter is applicable only to the Gateway application.  If not specified, the REGISTER request is sent to the Version 6.8 Mediant 800B Gateway and E-SBC...
Page 838 Mediant 800B Gateway and E-SBC Parameter Description primary Proxy server.  When a port number is specified, DNS NAPTR/SRV queries aren't performed, even if the parameter DNSQueryType is set to 1 or 2.  If the parameter RegistrarIP is set to an FQDN and is...
Page 839 Web: ReRegister On Connection Enables the device to perform SIP re-registration upon Failure TCP/TLS connection failure. EMS: Re Register On Connection  [0] Disable (default) Failure  [1] Enable CLI: reg-on-conn-failure [ReRegisterOnConnectionFailure] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 840 Mediant 800B Gateway and E-SBC Parameter Description Web: Gateway Registration Name Defines the user name that is used in the From and To EMS: Name headers in SIP REGISTER messages. If no value is specified CLI: gw-registration-name (default) for this parameter, the UserName parameter is used [GWRegistrationName] instead.
Page 841 Route: <sip: pcscf- gm.ims.rr.com;lr;transport=udp> EMS: Ping Pong Keep Alive Enables the use of the carriage-return and line-feed sequences [UsePingPongKeepAlive] (CRLF) Keep-Alive mechanism, according to RFC 5626 “Managing Client-Initiated Connections in the Session Initiation Version 6.8 Mediant 800B Gateway and E-SBC...
Page 842 Mediant 800B Gateway and E-SBC Parameter Description Protocol (SIP)” for reliable, connection-orientated transport types such as TCP.  [0] Disable (default)  [1] Enable The SIP user agent/client (i.e., device) uses a simple periodic message as a keep-alive mechanism to keep their flow to the proxy or registrar alive (used for example, to keep NAT bindings open).
Page 843 (i.e., 100 messages divided by 5 sec; 100 per 5 seconds).  If you configure the MaxGeneratedRegistersRate parameter to 100 and the GeneratedRegistersInterval to 1, the device sends a maximum of a 100 REGISTER messages per second. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 844: Network Application Parameters
Mediant 800B Gateway and E-SBC 57.6.2 Network Application Parameters The SIP network application parameters are described in the table below. Table 57-31: SIP Network Application Parameters Parameter Description Signaling Routing Domain Table Web: SRD Settings This table parameter configures the Signaling Routing Domains (SRD).
Page 845 FORMAT RemoteMediaSubnet_Index = RemoteMediaSubnet_Realm, CLI: configure voip > voip- RemoteMediaSubnet_RemoteMediaSubnetIndex, network realm RemoteMediaSubnet_RemoteMediaSubnetName, remotemediasubnet RemoteMediaSubnet_PrefixLength, [SubRealm] RemoteMediaSubnet_AddressFamily, RemoteMediaSubnet_DstIPAddress, RemoteMediaSubnet_QOEProfileName, RemoteMediaSubnet_BWProfileName; [\RemoteMediaSubnet] For a detailed description of this table, see ''Configuring Remote Media Subnets'' on page 269. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 846: General Sip Parameters
(if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Defines the maximum size (in Kbytes) for each SIP message that can Message Length [KB] be sent over the network.
Page 847 LA=<latency in ms> Below is an example of the X-RTP-Stat header in a SIP BYE message: BYE sip:302@10.33.4.125 SIP/2.0 Via: SIP/2.0/UDP 10.33.4.126;branch=z9hG4bKac2127550866 Max-Forwards: 70 From: <sip:401@10.33.4.126;user=phone>;tag=1c2113553324 To: <sip:302@company.com>;tag=1c991751121 Call-ID: 991750671245200001912@10.33.4.125 CSeq: 1 BYE X-RTP-Stat: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 848 Mediant 800B Gateway and E-SBC Parameter Description PS=207;OS=49680;;PR=314;OR=50240;PL=0;JI=600;LA=40 Supported: em,timer,replaces,path,resource- priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRAC K,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.6.2A.008.006 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0 Web/EMS: PRACK Mode Determines the PRACK (Provisional Acknowledgment) mechanism CLI: prack-mode mode for SIP 1xx reliable responses. [PrackMode] ...
Page 849 The valid range is 0 to 32 (in seconds). The default is 32. ctTime] Web/EMS: Session Expires Determines the SIP method used for session-timer updates. Method  [0] Re-INVITE = (Default) Uses re-INVITE messages for session- Version 6.8 Mediant 800B Gateway and E-SBC...
Page 850 Mediant 800B Gateway and E-SBC Parameter Description CLI: session-exp-method timer updates. [SessionExpiresMethod]  [1] UPDATE = Uses UPDATE messages. Notes:  The device can receive session-timer refreshes using both methods.  The UPDATE message used for session-timer is excluded from the SDP body.
Page 851 T.38 Re-INVITES. In such a scenario, the FaxVBDBehavior parameter has no effect.  This feature can be used only if the remote party supports T.38 fax relay; otherwise, the fax fails. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 852 Mediant 800B Gateway and E-SBC Parameter Description [NoAudioPayloadType] Defines the payload type of the outgoing SDP offer. The valid value range is 96 to 127 (dynamic payload type). The default is 0 (i.e. NoAudio is not supported). For example, if set to 120, the...
Page 853 The valid range is 0 to 40 sec. The default is 64 * SipT1Rtx parameter value. For example, if SipT1Rtx is set to 500 msec, then the default of SIPTCPTimeout is 32 sec. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 854 Mediant 800B Gateway and E-SBC Parameter Description Web: SIP Destination Port Defines the SIP destination port for sending initial SIP requests. EMS: Destination Port The valid range is 1 to 65534. The default port is 5060. CLI: sip-dst-port Note: SIP responses are sent to the port specified in the Via header.
Page 855 (received in INVITE) to ISDN Setup with an Off Hook Indicator IE of “Data”, and with “Unrestricted 64k” Bearer Capability IE. The following is an example of the INVITE with tgrp=hotline- ccdata: INVITE sip:1234567;tgrp=hotline-ccdata;trunk- Version 6.8 Mediant 800B Gateway and E-SBC...
Page 856 Mediant 800B Gateway and E-SBC Parameter Description context=dsn.mil@example.com  For ISDN-to-IP calls: - The device interworks ISDN Setup with an Off Hook Indicator of “Voice” to SIP INVITE with “tgrp=hotline;trunk- context=dsn.mil” in the Contact header. - The device interworks ISDN Setup with an Off Hook indicator of “Data”...
Page 857 Thus, each endpoint can get a unique id – its phone number. The globally unique ID in TP is the MAC address concatenated with the phone number of the endpoint. If the remote server doesn’t support GRUU, it ignores the parameters Version 6.8 Mediant 800B Gateway and E-SBC...
Page 858 EMS: User Agent Display value>/software version' is used, for example: Info User-Agent: myproduct/v.6.40.010.006 CLI: user-agent-info If not configured, the default string, <AudioCodes product- [UserAgentDisplayInfo] name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Mediant 800B Gateway and E-SBC/v.6.40.010.006 The maximum string length is 50 characters.
Page 859 CLI: 3xx-behavior response is received for an outgoing INVITE request. The device can [3xxBehavior] either use the same call identifiers (Call-ID, To, and From tags) or change them in the new initiated INVITE. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 860 Mediant 800B Gateway and E-SBC Parameter Description  [0] Forward = (Default) Use different call identifiers for a redirected INVITE message.  [1] Redirect = Use the same call identifiers. Web/EMS: Enable P- Enables the inclusion of the P-Charging-Vector header to all outgoing Charging Vector INVITE messages.
Page 861 SIP agent.)  [0] Disable = (Default) The device sends the initial INVITE message with an SDP.  [1] Enable = The device sends the initial INVITE message without an SDP. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 862 Mediant 800B Gateway and E-SBC Parameter Description [DisableCryptoLifeTimeIn Enables the device to send "a=crypto" lines without the lifetime SDP] parameter in the SDP. For example, if the SDP contains "a=crypto:12 AES_CM_128_HMAC_SHA1_80 inline:hhQe10yZRcRcpIFPkH5xYY9R1de37ogh9G1MpvNp|2^31", it removes the lifetime parameter "2^31".  [0] Disable (default) ...
Page 863 Profile table, see Configuring Tel Profiles on page 319. Note: If this functionality is configured for a specific profile, the settings of this global parameter is ignored for calls associated with the profile. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 864 Mediant 800B Gateway and E-SBC Parameter Description [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 being forwarded"). The re-INVITE is sent immediately upon receipt of the 200 OK (when the call is answered).
Page 865 "e" as the prefix, removing the "ext=" parameter, and adding the extension number as the suffix (e.g., e622125519100104). Once modified, the device can then manipulate the number further, using the Number Version 6.8 Mediant 800B Gateway and E-SBC...
Page 866 Mediant 800B Gateway and E-SBC Parameter Description 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 ...
Page 867 [3] = The 'ecan' attribute and the 'vbd' parameter are not included in the SDP. Note: This parameter is applicable only when the IsFaxUsed parameter is set to 2, and for re-INVITE messages generated by the device as result of modem or fax tone detection. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 868 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: First Call Defines the index of the first ringback tone in the CPT file. This option Ringback Tone ID enables an Application server to request the device to play a distinctive CLI: 1st-call-rbt-id...
Page 869 0 is Trunk 1. For a description of this parameter, see the RTPOnlyMode parameter. Note: For using the global parameter (i.e., setting the RTP Only feature for all trunks), set this parameter to -1 (default). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 870 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Media IP Version Global parameter that defines the preferred RTP media IP addressing Preference version (IPv4 or IPv6) for outgoing SIP calls. You can also configure CLI: media-ip-ver-pref this functionality per specific calls, using IP Profiles [MediaIPVersionPreference] (IpProfile_MediaIPVersionPreference).
Page 871 Out condition. Each trunk uses the proper Out-Of-Service method according to the selected ISDN/CAS variant.  Digital: For configuring the method for taking trunks/channels out- of-service, see the DigitalOOSBehaviorForTrunk_x parameter for per trunk or the DigitalOOSBehavior parameter for all trunks. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 872 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Graceful Busy Defines the timeout interval (in seconds) for Out-of-Service graceful Out Timeout [sec] shutdown mode for busy trunks (per trunk) if communication fails with CLI: graceful-bsy-out-t-out a Proxy server (or Proxy Set). In such a scenario, the device rejects...
Page 873 - Fully configured trunk (all channels): > If all channels are idle when the graceful period begins, the device immediately takes the channels out-of-service without sending out-of-service Service messages and instead, only takes the D-channel down. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 874 Mediant 800B Gateway and E-SBC Parameter Description > If at least one channel is busy during the graceful period, the device immediately takes all idle channels out-of-service and sends out-of-service Service messages to these B-channels. Thus, the PSTN/PBX side can detect that these calls are in out-...
Page 875 The second retransmission is sent after 1000 (2*500) msec.  The third retransmission is sent after 2000 (2*1000) msec.  The fourth retransmission and subsequent retransmissions until SIPMaxRtx are sent after 4000 (2*2000) msec. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 876 Mediant 800B Gateway and E-SBC Parameter Description Web: SIP T2 Defines the maximum interval (in msec) between retransmissions of Retransmission Timer SIP messages (except for INVITE requests). [msec] The default is 4000. EMS: T2 RTX Note: The time interval between subsequent retransmissions of the...
Page 877 The format of the ini file table parameter is as follows: [MessagePolicy] FORMAT MessagePolicy_Index = MessagePolicy_Policy, MessagePolicy_MaxMessageLength, MessagePolicy_MaxHeaderLength, MessagePoliy_MaxBodyLength, MessagePolicy_MaxNumHeaders, MessagePolicy_MaxNumBodies, MessagePolicy_SendRejection, MessagePolicy_MethodListType, MessagePolicy_MethodList, MessagePolicy_BodyListType, MessagePolicy_BodyList; [/MessagePolicy] For a detailed description of this table, see Configuring SIP Message Policy Rules. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 878: Coders And Profile Parameters
Mediant 800B Gateway and E-SBC 57.8 Coders and Profile Parameters The profile parameters are described in the table below. Table 57-33: Profile Parameters Parameter Description Coders Table / Coder Groups Table Web: Coders Table/Coder This table parameter defines the device's coders. Each group can consist Group Settings of up to 10 coders.
Page 879 TableEndpoint Phone Number table (TrunkGroup parameter). Therefore, profile Tel Profiles allow you to apply the same settings of a group of [TelProfile] parameters to multiple channels, or apply specific settings to different channels. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 880 Mediant 800B Gateway and E-SBC Parameter Description The format of the ini file table parameter is as follows: [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,...
Page 881: Channel Parameters
G.726 voice coder and voice quality is poor, change the settings of this parameter (between Big Endian and Little Endian). Web: MF Transport Type Currently, not supported. CLI: MF-transport-type [MFTransportType] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 882 Mediant 800B Gateway and E-SBC Parameter Description Web: Silence Suppression Global parameter that enables the Silence Suppression EMS: Silence Compression Mode feature. You can also configure this functionality per CLI: silence-compression-mode specific calls, using IP Profiles (IpProfile_SCE). For a [EnableSilenceCompression]...
Page 883 Web: Answer Detector Redirection Currently, not supported. [AnswerDetectorRedirection] Web: Answer Detector Sensitivity Defines the Answer Detector sensitivity. EMS: Sensitivity The range is 0 (most sensitive) to 2 (least sensitive). The CLI: answer-detector-sensitivity default is 0. [AnswerDetectorSensitivity] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 884: Coder Parameters
Mediant 800B Gateway and E-SBC 57.9.2 Coder Parameters The coder parameters are described in the table below. Table 57-35: Coder Parameters Parameter Description Silk Tx Inband FEC Enables forward error correction (FEC) for the SILK coder. CLI: silk-tx-inband-fec  [0] Disable (default) [SilkTxInbandFEC] ...
Page 885: Dtmf Parameters
DTMF or MF digits at the Tel/PSTN side when the DTMF Transport CLI: digit-hangover-time-tx Type is either Relay or Mute. [TxDTMFHangOverTime] Valid range is 0 to 2,000 msec. The default is 1,000 msec. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 886 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: NTE Max Duration Defines the maximum time for sending Named Telephony Events / CLI: telephony-events-max- NTEs (RFC 4733/2833 DTMF relay) to the IP side, regardless of duration the DTMF signal duration on the TDM side.
Page 887: Rtp, Rtcp And T.38 Parameters
IP Profile table, see Configuring IP Profiles on page 323. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 888 Mediant 800B Gateway and E-SBC Parameter Description Web: Enable RTP Redundancy Enables the device to include the RTP redundancy dynamic Negotiation payload type in the SDP, according to RFC 2198. CLI: rtp-rdcy-nego-enbl  [0] Disable (default) [EnableRTPRedundancyNegoti  [1] Enable...
Page 889 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. Note: This parameter is applicable only to Gateway calls (not SBC). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 890 Mediant 800B Gateway and E-SBC Parameter Description RTP Control Protocol Extended Reports (RTCP XR) Parameters Web: Enable RTCP XR Enables voice quality monitoring and RTCP XR, according to EMS: RTCP XR Enable RFC 3611. CLI: voice-quality-monitoring-enable  [0] Disable (default) [VQMonEnable] ...
Page 891 (i.e., after a SIP BYE). The RTCP [SBCRtcpXrReportMode] XR is sent in the SIP PUBLISH message.  [0] Disable (default)  [1] End of Call Note: This parameter is applicable only to the SBC application. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 892 Mediant 800B Gateway and E-SBC Parameter Description publication-ip-group-id Defines the IP Group to where the RTCP XR is sent. If the value is -1 (default) or 0, the RTCP XR is sent to the ESC [PublicationIPGroupID] server, as configured by the RTCPXREscIP parameter.
Page 893: Gateway And Ip-To-Ip Parameters
IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 323. Web: V.32 Modem Transport Type Determines the V.32 modem transport type. EMS: V32 Transport  [0] Disable = Transparent. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 894 Mediant 800B Gateway and E-SBC Parameter Description  [2] Enable Bypass (default) CLI: V32-modem-transport-type [V32ModemTransportType]  [3] Events Only = Transparent with Events. Notes:  This parameter applies only to V.32 and V.32bis modems.  You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType).
Page 895 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.8 Mediant 800B Gateway and E-SBC...
Page 896 Mediant 800B Gateway and 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...
Page 897 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. Therefore, set the T38UseRTPPort parameter to 0. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 898 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: T.38 Max Datagram Defines the maximum size of a T.38 datagram that the device Size can receive. This value is included in the outgoing SDP when CLI: t38-mx-datagram-sz T.38 is used. [T38MaxDatagramSize] The valid range is 120 to 600.
Page 899 Web: SPRT Transport Ch.3 Max Defines the maximum payload size for V.150.1 SPRT Transport Payload Size Channel 3. CLI: SPRT-transport-channel3- The range is 140 to 256. The default is 140. max-payload-size [V1501SPRTTransportChannel3M axPayloadSize] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 900: Dtmf And Hook-Flash Parameters
Mediant 800B Gateway and E-SBC 57.10.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below. Table 57-39: DTMF and Hook-Flash Parameters Parameter Description Hook-Flash Parameters Web/EMS: Hook-Flash Code For analog interfaces: Defines the digit pattern that when CLI: hook-flash-code received from the Tel side, indicates a Hook Flash event.
Page 901 Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Web/EMS: 1st Tx DTMF Option / Defines up to two preferred transmit DTMF negotiation Version 6.8 Mediant 800B Gateway and E-SBC...
Page 902 Mediant 800B Gateway and E-SBC Parameter Description 2nd Tx DTMF Option methods. CLI: configure voip > gw dtmf-and-  [0] Not Supported = (Default) No negotiation - DTMF digits suppl dtmf-and-dialing > dtmf- are sent according to the parameters DTMFTransportType options and RFC2833PayloadType.
Page 903 If character 'd' is used, it must be the first 'digit' in the called number. The character 'p' can be used several times. For example (for FXS/FXO interfaces), the called number can be as follows: d1005, dpp699, p9p300. To add the 'd' Version 6.8 Mediant 800B Gateway and E-SBC...
Page 904: Digit Collection And Dial Plan Parameters
Mediant 800B Gateway and E-SBC Parameter Description and 'p' digits, use the usual number manipulation rules.  For analog interfaces: To use this feature with FXO interfaces, configure the device to operate in one-stage dialing mode.  If this parameter is enabled, it is possible to configure the...
Page 905 Defines the maximum number of collected destination number digits that can be received (i.e., dialed) from the Tel side (analog) when EMS: Max Digits in Phone Tel-to-IP ISDN overlap dialing is performed (digital). When the Version 6.8 Mediant 800B Gateway and E-SBC...
Page 906: Voice Mail Parameters
Mediant 800B Gateway and E-SBC Parameter Description Number number of collected digits reaches this maximum, the device uses CLI: mxdig-b4-dialing these digits for the called destination number. [MaxDigits] The valid range is 1 to 49. The default is 5 for analog and 30for digital.
Page 907 IP side, the device (FXO) sends a hook-flash to the PBX, dials the digits (that are received in the Refer-To header), and then immediately releases the line (i.e., on- hook). The PBX performs the transfer internally. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 908 Mediant 800B Gateway and E-SBC Parameter Description  E1/T1 CAS: When a SIP REFER message is received, the device performs a blind transfer, by performing a CAS wink, waiting a user-defined time (configured by the WaitForDialTime parameter), dialing the Refer-To number, and then releasing the call.
Page 909 For example, if the 'SIP Group Name' field of the IP Group is set to "company.com", the device sends the following SUBSCRIBE message: SUBSCRIBE sip:company.com... Instead of: SUBSCRIBE sip:10.33.10.10... Note: If this parameter is not configured, the MWI SUBSCRIBE Version 6.8 Mediant 800B Gateway and E-SBC...
Page 910 Mediant 800B Gateway and E-SBC Parameter Description message is sent to the MWI server as defined by the MWIServerIP parameter. [NotificationIPGroupID] Defines the IP Group ID to which the device sends SIP NOTIFY MWI messages. Notes:  This is used for MWI Interrogation. For more information on the interworking of QSIG MWI to IP, see Message Waiting Indication on page 453.
Page 911 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. CLI: dig-to-ignore-dig-pattern [DigitPatternDigitToIgnore] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 912: Supplementary Services Parameters
Mediant 800B Gateway and E-SBC 57.10.5 Supplementary Services Parameters This subsection describes the device's supplementary telephony services parameters. 57.10.5.1 Caller ID Parameters The caller ID parameters are described in the table below. Table 57-42: Caller ID Parameters Parameter Description Caller ID Permissions Table...
Page 913 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. CLI: fxs-callid-cat-brazil  [0] Disable (default) Version 6.8 Mediant 800B Gateway and E-SBC...
Page 914 Mediant 800B Gateway and E-SBC Parameter Description  [1] Enable [AddCPCPrefix2BrazilCallerID] When this parameter is enabled, the device sends the Caller ID number (calling number) with the cpc code (received in the SIP INVITE message) to the device's FXS port. The cpc code is added as a prefix to the caller ID (after IP-to-Tel calling number manipulation).
Page 915 - Connected Number and Connected Name. For example, if the call is answered by the device, the 200 OK response includes the P-Asserted-Identity with Caller ID. The device interworks (in some ISDN variants), the Connected Party number and name Version 6.8 Mediant 800B Gateway and E-SBC...
Page 916 Mediant 800B Gateway and E-SBC Parameter Description from Q.931 Connect message to SIP 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 privacy.
Page 917: 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 Waiting on page 502. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 918 Mediant 800B Gateway and E-SBC Parameter Description 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 919: Call Forwarding Parameters
FwdInfo 1 = 1,2003@10.5.1.1,30,1,2; For a detailed description of this table, see Configuring Call Forward on page 500. Note: The indexing of this parameter starts at 0. Call Forward Reminder Ring Parameters Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 920: Message Waiting Indication Parameters
Mediant 800B Gateway and E-SBC Parameter Description  These parameters are applicable only to FXS interfaces.  For a description of this feature, see Call Forward Reminder Ring on page 448. Web/EMS: Enable NRT Enables endpoint subscription for Ring reminder event notification Subscription feature.
Page 921 [3] = ETSI VMWI before ring LR_DT_AS  [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 Version 6.8 Mediant 800B Gateway and E-SBC...
Page 922: Call Hold Parameters
Mediant 800B Gateway and E-SBC Parameter Description Note: For this parameter to take effect, a device reset is required. EMS: Bellcore VMWI Type One Determines the Bellcore VMWI sub-standard. Standard  [0] = (Default) Between rings. CLI: bellcore-vmwi-type-one-  [1] = Not ring related.
Page 923: Call Transfer Parameters
If this service is enabled, the 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. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 924 Mediant 800B Gateway and E-SBC Parameter Description Web: Transfer Prefix Defines the string that is added as a prefix to the EMS: Logical Prefix For Transferred transferred/forwarded called number when the REFER/3xx Call message is received. CLI: transfer-prefix Notes: [xferPrefix] ...
Page 925 Determines the interworking of incoming mid-call SIP REFER CLI: ip2ip-transfer-mode messages to outgoing REFER messages, for calls pertaining [IP2IPTransfermode] to the IP-to-IP application.  [0] Disable = (Default) Upon receipt of a REFER message, Version 6.8 Mediant 800B Gateway and E-SBC...
Page 926: Multi-Line Extensions And Supplementary Services Parameters
Note: For this parameter to take effect, a device reset is required. Web: 3-Way Conference Mode Determines the mode of operation when the 3-Way Conference EMS: 3 Way Mode feature is used. CLI: 3w-conf-mode  [0] AudioCodes Media Server = (Default) The Conference- User's Manual Document #: LTRT-10620...
Page 927 This conference mode is used when operating with AudioCodes IPMedia conferencing server.  [1] Non-AudioCodes Media Server = The Conference- initiating INVITE (sent by the device) uses only the ConferenceID as the Request-URI. The conference server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants.
Page 928: Mlpp And Emergency Call Parameters
Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Conference ID Defines the Conference Identification string. CLI: conf-id The valid value is a string of up to 16 characters. The default is [ConferenceID] "conf". The device uses this identifier in the Conference-initiating INVITE that is sent to the media server when the Enable3WayConference parameter is set to 1.
Page 929 [1] = Enable EMS: Enable 911 PSAP Enables the support for the E911 DID protocol, according to the [Enable911PSAP] Bellcore GR-350-CORE standard. This protocol defines signaling between E911 Tandem Switches and the PSAP, using Version 6.8 Mediant 800B Gateway and E-SBC...
Page 930 Mediant 800B Gateway and E-SBC Parameter Description analog loop-start lines. The FXO device can be installed instead of an E911 switch, connected directly to PSAP DID loop-start lines.  [0] = Disable (default)  [1] = Enable Notes:  This parameter is applicable only to FXO interfaces.
Page 931 If the incoming PRI Setup message doesn't contain a valid Precedence Level value, the default value is used in the Resource-Priority header of the outgoing SIP INVITE request. In this scenario, the character string is sent without translation to a numerical value. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 932 Mediant 800B Gateway and E-SBC Parameter Description Web: MLPP DiffServ Defines the DiffServ value (differentiated services code EMS: Diff Serv point/DSCP) used in IP packets containing SIP messages that CLI: mlpp-diffserv are related to MLPP calls. This parameter defines DiffServ for...
Page 933 The valid range is -1 to 63. The default is -1. CLI: dscp-4-mlpp-prio Note: If set to -1, the DiffServ value is taken from the global [MLPPPriorityRTPDSCP] parameter PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 934: Call Cut-Through Parameters
Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: RTP DSCP for MLPP Defines the RTP DSCP for MLPP Immediate precedence call Immediate level. CLI: dscp-4-mlpp-immed The valid range is -1 to 63. The default is -1. [MLPPImmediateRTPDSCP] Note: If set to -1, the DiffServ value is taken from the global parameter PremiumServiceClassMediaDiffServ or as defined in IP Profiles per call.
Page 935: Automatic Dialing Parameters
TargetOfChannel_Port is the port number, where 1 denotes Port 1 on the module.  This is parameter is applicable only to FXS and FXO interfaces.  For a detailed description of this table, see ''Configuring Automatic Version 6.8 Mediant 800B Gateway and E-SBC...
Page 936: Direct Inward Dialing Parameters
Mediant 800B Gateway and E-SBC Parameter Description Dialing'' on page 497. 57.10.5.12 Direct Inward Dialing Parameters The Direct Inward Dialing (DID) parameters are described in the table below. Table 57-53: DID Parameters Parameter Description Web/EMS: DID Wink Enables Direct Inward Dialing (DID) using Wink-Start signaling, typically CLI: did-wink-enbl used for signaling between an E-911 switch and the PSAP.
Page 937 Note: This parameter is applicable only to FXS interfaces. CLI: wink-time Defines the time (in msec) elapsed between two consecutive polarity [WinkTime] reversals. This parameter can be used for DID signaling, for example, Version 6.8 Mediant 800B Gateway and E-SBC...
Page 938: Isdn Bri Parameters
Mediant 800B Gateway and E-SBC Parameter Description E911 lines to the Public Safety Answering Point (PSAP), according to the Bellcore GR-350-CORE standard (refer to the ini file parameter Enable911PSAP). The valid range is 0 to 4,294,967,295. The default is 200.
Page 939 Enables the device to indicate the type of call forwarding service in the Request-URI of the outgoing SIP INVITE message, using a [UseFacilityInRequest] proprietary header parameter "facility=<call forward service>".  [0] = (Default) Disable  [1] = Enable Version 6.8 Mediant 800B Gateway and E-SBC...
Page 940: Pstn Parameters
Mediant 800B Gateway and E-SBC 57.10.6 PSTN Parameters This subsection describes the device's PSTN parameters. 57.10.6.1 General Parameters The general PSTN parameters are described in the table below. Table 57-55: General PSTN Parameters Parameter Description Web: Trunk Name Defines an arbitrary name for a trunk (where x denotes the trunk CLI: name (config-voip >...
Page 941  The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. [ProtocolType_x] Defines the protocol type for a specific trunk ID (where x denotes the Trunk ID and 0 is the first trunk).
Page 942 Mediant 800B Gateway and E-SBC Parameter Description the duration of T310 timer, the call clears. The valid value range is 0 to 600 seconds. The default is 0 (i.e., use the default timer value according to the protocol's specifications). Notes: ...
Page 943 Defines the administrative state for all trunks.  [0] = Lock the trunk; stops trunk traffic to configure the trunk protocol type.  [1] = Shutting down (read only).  [2] = (Default) Unlock the trunk; enables trunk traffic. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 944 Mediant 800B Gateway and E-SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  When the device is locked from the Web interface, this parameter changes to 0.  To define the administrative state per trunk, use the TrunkAdministrativeState parameter.
Page 945 (a, e, i, o, and u, respectively).  [1] Western European (Default)  [2] Central European  [3] South European  [4] North European  [5] Cyrillic  [6] Arabic  [7] Hebrew  [8] Turkish Version 6.8 Mediant 800B Gateway and E-SBC...
Page 946: Tdm Bus And Clock Timing Parameters
Mediant 800B Gateway and E-SBC 57.10.6.2 TDM Bus and Clock Timing Parameters The TDM Bus parameters are described in the table below. Table 57-56: TDM Bus and Clock Timing Parameters Parameter Description TDM Bus Parameters Web/EMS: PCM Law Select Determines the type of pulse-code modulation (PCM) companding [PCMLawSelect] algorithm law in input and output TDM bus.
Page 947 100 indicates that the device does not perform a fallback to the [AutoClockTrunkPriority] trunk (typically, used to mark untrusted source of clock). Note: Fallback is enabled when the TDMBusPSTNAutoClockEnable parameter is set to 1. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 948: Cas Parameters
Mediant 800B Gateway and E-SBC 57.10.6.3 CAS Parameters The Common Channel Associated (CAS) parameters are described in the table below. Note that CAS is not applicable to BRI interfaces. Table 57-57: CAS Parameters Parameter Description Web: CAS Transport Type Determines the ABCD signaling transport type over IP.
Page 949  Only one of these formats can be implemented; not both.  When this parameter is not configured, a single CAS table for the entire trunk is used, configured by the parameter CASTableIndex. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 950 Mediant 800B Gateway and E-SBC Parameter Description [CASTablesNum] Defines how many CAS protocol configurations files are loaded. The valid range is 1 to 8. Note: For this parameter to take effect, a device reset is required. CAS State Machines Parameters Note: For configuring the CAS State Machine table using the Web interface, see ''Configuring CAS State Machines'' on page 363.
Page 951: Isdn Parameters
- calling equipment is not ISDN. Web/EMS: B-channel Negotiation Determines the ISDN B-Channel negotiation mode. CLI: b-ch-negotiation  [0] Preferred [BchannelNegotiation]  [1] Exclusive (default)  [2] Any Notes:  This parameter is applicable only to ISDN protocols. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 952 Mediant 800B Gateway and E-SBC Parameter Description  For some ISDN variants, when 'Any' (2) is selected, the Setup message excludes the Channel Identification IE.  The Any' (2) option is applicable only if the following conditions are met: ...
Page 953 User provided, Network provided: the second one is used  User provided, user provided: the first one is used When this bit is configured, the device behaves as follows:  Network provided, Network provided: the first Version 6.8 Mediant 800B Gateway and E-SBC...
Page 954 Mediant 800B Gateway and E-SBC Parameter Description calling number is used.  Network provided, User provided: the second one is used  User provided, Network provided: the first one is used  User provided, user provided: the first one is...
Page 955 To configure the device to support several ISDNIBehavior features, enter a summation of the individual feature values. For example, to support both [512] and [2048] features, set the parameter ISDNIBehavior is set to 2560 (i.e., 512 + 2048). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 956 Mediant 800B Gateway and E-SBC Parameter Description  When configuring in the Web interface, to select the options click the arrow button and then for each required option select 1 to enable.  For BRI terminal endpoint identifier (TEI) configuration, instead of using the ISDNIBehavior...
Page 957  [128] DIAL WITH KEYPAD = The device uses the Keypad IE to store the called number digits instead of the CALLED_NB IE. Note: This option is applicable only to the Korean Version 6.8 Mediant 800B Gateway and E-SBC...
Page 958 Mediant 800B Gateway and E-SBC Parameter Description variant (Korean network). This is useful for Korean switches that don't accept the CALLED_NB IE.  [256] STORE CHAN ID IN SETUP = The device forces the sending of a Channel-Id IE in an outgoing Setup message even if it's not required by the standard (i.e., optional) and no Channel-Id...
Page 959 0-63: Static TEI is used.  127: Dynamic TEI allocation is supported (TEI request procedure initiated). Note: The value 127 replaces the previous configuration requirement to set the ISDNIBehavior parameter to NS EXPLICIT INTERFACE ID (1). Version 6.8 Mediant 800B Gateway and E-SBC...
Page 960 Mediant 800B Gateway and E-SBC Parameter Description CLI: tei-config-p2mp Defines the BRI TEI when in point-to-multipoint (P2MP) mode. (config-voice > interface bri The valid value is 0 to 63, 127. The default is 127. <module/port>)  Network Side: Not applicable - In network side in P2MP [BriTEIConfigP2MP_x] configuration, any TEI must be accepted.
Page 961: Isdn And Cas Interworking Parameters
IP side with a SIP 183. For each subsequently received SIP INFO message with additional digits of the same dialog session, the device sends the collected digits to the Tel side in ISDN Info Q.931 messages. For each Version 6.8 Mediant 800B Gateway and E-SBC...
Page 962 Mediant 800B Gateway and E-SBC Parameter Description received SIP INFO, the device sends a SIP 200 OK response to maintain the current dialog session and to receive additional digits from subsequent INFOs. Note: When IP-to-Tel overlap dialing is enabled, to send ISDN...
Page 963 When ISDN Tunneling is enabled, the device extracts raw data received in the proprietary SIP header, x-isdntunnelinginfo, or a dedicated message body (application/isdn) in the SIP message and then sends the data in an ISDN message to the PSTN. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 964 Mediant 800B Gateway and E-SBC Parameter Description If the raw data in this SIP header is suffixed with the string "ADDE", then the raw data is extracted and added as Informational Elements (IE) in the outgoing Q.931 message. The tunneling of the x- isdntunnelinginfo SIP header with IEs is converted from INVITE, 180, and 200 OK SIP messages to Q.931 SETUP, ALERT, and...
Page 965 SIP 'isub' parameter according to RFC.  [1] = The device removes the ISDN Subaddress and does not include the 'isub' parameter in the Request-URI and does not process INVITEs with this parameter. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 966 Mediant 800B Gateway and E-SBC Parameter Description [ISUBNumberOfDigits] Defines the number of digits (from the end) that the device takes from the called number (received from the IP) for the isub number (in the sent ISDN Setup message). This feature is only applicable for IP-to-ISDN calls.
Page 967 Web: Calling Party Category Defines the regional Calling Party Category (CPC) mapping variant Mode between SIP and PSTN for MFC-R2. CLI: cpc-mode  [0] None (default) [CallingPartyCategoryMode]  [1] Brazil R2  [2] Argentina R2 Notes: Version 6.8 Mediant 800B Gateway and E-SBC...
Page 968 Mediant 800B Gateway and E-SBC Parameter Description  To enable CPC mapping, set the EnableCallingPartyCategory parameter to 1.  This parameter is applicable only to the E1 MFC-R2 variant. CLI: usr2usr-hdr-frmt Defines the interworking between the SIP INVITE's User-to-User [UserToUserHeaderFormat] header and the ISDN User-to-User (UU) IE data.
Page 969 Defines the Alert Timeout (ISDN T301 timer) in seconds for CLI: pstn-alrt-timeout outgoing calls to PSTN, per trunk. This timer is used between the [TrunkPSTNAlertTimeout_x] time that an ISDN Setup message is sent to the Tel side (IP-to-Tel Version 6.8 Mediant 800B Gateway and E-SBC...
Page 970 Mediant 800B Gateway and 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 name denotes the trunk number, where 0 is Trunk 1.
Page 971 When IP Profiles are used for configuring different IE data for Trunk Groups, this parameter is ignored. Web: Enable User-to-User IE Enables transfer of User-to-User (UU) IE from ISDN PRI to SIP. for Tel to IP Version 6.8 Mediant 800B Gateway and E-SBC...
Page 972 Mediant 800B Gateway and E-SBC Parameter Description  [0] Disable (default) EMS: Enable UUI Tel 2 Ip CLI: uui-ie-for-tel2ip  [1] Enable [EnableUUITel2IP] The device supports the following ISDN PRI-to-SIP interworking: Setup to SIP INVITE, Connect to SIP 200 OK, User Information to SIP INFO, Alerting to SIP 18x response, and Disconnect to SIP BYE response messages.
Page 973 Blind Transfer by executing a CAS Wink, dialing the Refer-to number to the switch, and then releasing the call.  [4] = Supports QSIG Single Step transfer (PRI/BRI): Version 6.8 Mediant 800B Gateway and E-SBC...
Page 974 Mediant 800B Gateway and E-SBC Parameter Description IP-to-Tel: When a SIP REFER message is received, the device performs a transfer by sending a Facility message to the PBX, initiating Single Step transfer. Once a success return result is received, the transfer is completed.
Page 975 Enables "hairpin" TDM transfer upon ISDN (ECT, RLT, or TBCT) call transfer failure. When this feature is enabled and an ISDN call transfer failure occurs, the device sends a SIP NOTIFY message with a SIP 603 Decline response. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 976 Mediant 800B Gateway and E-SBC Parameter Description  [0] = (Default) The device performs a hairpin TDM transfer upon ISDN call transfer.  [1] = Hairpin TDM transfer is disabled. Web: Enable QSIG Transfer Determines whether the device interworks QSIG Facility messages...
Page 977 Causes. The format of the ini file table parameter is as follows: EMS: SIP to ISDN Cause [CauseMapSIP2ISDN] Mapping FORMAT CauseMapSIP2ISDN_Index = CLI: configure voip > gw CauseMapSIP2ISDN_SipResponse, manipulations CauseMapSIP2ISDN_IsdnReleaseCause; CauseMapSip2Isdn [\CauseMapSIP2ISDN] [CauseMapSIP2ISDN] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 978: Answer And Disconnect Supervision Parameters
Mediant 800B Gateway and E-SBC 57.10.8 Answer and Disconnect Supervision Parameters The answer and disconnect supervision parameters are described in the table below. Table 57-60: Answer and Disconnect Parameters Parameter Description Web: Wait before PSTN Release- Defines a timeout (in milliseconds) that the device waits for the receipt of an ISDN Q.931 Release message from the PSTN side...
Page 979 The silence duration can be configured by the FarEndDisconnectSilencePeriod parameter (default 120). Note: To activate this feature, set the parameters EnableSilenceCompression and FarEndDisconnectSilenceMethod to 1. Web: Silence Detection Period Defines the duration of the silence period (in seconds) after which Version 6.8 Mediant 800B Gateway and E-SBC...
Page 980 Mediant 800B Gateway and E-SBC Parameter Description [sec] the call is disconnected. EMS: Silence Detection Time Out The range is 10 to 28,800 (i.e., 8 hours). The default is 120 [FarEndDisconnectSilencePeri seconds. Note: For this parameter to take effect, a device reset is required.
Page 981 The FXO releases a call when a current disconnect signal is detected on its port.  The FXS interface generates a 'Current Disconnect Pulse' after a call is released from IP. The current disconnect duration is configured by the Version 6.8 Mediant 800B Gateway and E-SBC...
Page 982 Mediant 800B Gateway and E-SBC Parameter Description CurrentDisconnectDuration parameter. The current disconnect threshold (FXO only) is configured by the CurrentDisconnectDefaultThreshold parameter. The frequency at which the analog line voltage is sampled is configured by the TimeToSampleAnalogLineVoltage parameter. Note: This parameter can also be configured in a Tel Profile.
Page 983: Tone Parameters
The range is 1,000 to 60,000. The default is 2,000 (i.e., 2 seconds). Notes:  This parameter is applicable only to FXS interfaces.  If you want to configure the duration of the confirmation tone to Version 6.8 Mediant 800B Gateway and E-SBC...
Page 984 Mediant 800B Gateway and E-SBC Parameter Description longer than 16 seconds, you must increase the value of the parameter TimeForDialTone accordingly.  The MWI tone takes precedence over the call forwarding reminder tone. For more information on MWI, see Message Waiting Indication on page 453.
Page 985 Tel side. The user-defined tone is configured when creating the PRT file, using AudioCodes DConvert utility. The tone must be assigned to the "acSpecialConditionTone" (Tone Type 21) option in DConvert. The parameter can be configured with up to 10 release codes.
Page 986 Mediant 800B Gateway and E-SBC Parameter Description If the SIP release reason received from the IP side is mapped to the Q.931 release code specified by the parameter, the device plays the user-defined tone. Otherwise, if not specified and the release code is 17 (User Busy), the device plays the busy tone and for all other release codes, the device plays the reorder tone.
Page 987  If the device receives a SIP 180 Ringing response (with or without SDP) and the LocalISDNRBSource parameter is set to 1, it plays a ringback tone and sends an ISDN Alert with Version 6.8 Mediant 800B Gateway and E-SBC...
Page 988 Mediant 800B Gateway and E-SBC Parameter Description PI = 8 (unless the ProgressIndicator2ISDN_x parameter is configured differently).  If the LocalISDNRBSource parameter is set to 0, the device doesn't play a ringback tone and an Alert message without PI is sent to the ISDN. In this case, the PBX / PSTN plays the ringback tone to the originating terminal.
Page 989 FXS ports 1 and 2 if the source number prefix of the received call is ToneIndex 1 = 1, 2, 20*, , 3; For a detailed description of this table, see Configuring FXS Distinctive Ringing and Call Waiting Tones per Source/Destination Number. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 990: Tone Detection Parameters
Mediant 800B Gateway and E-SBC 57.10.9.2 Tone Detection Parameters The signal tone detection parameters are described in the table below. Table 57-62: Tone Detection Parameters Parameter Description EMS: DTMF Enable Enables the detection of DTMF signaling. CLI: DTMF-detector-enable  [0] = Disable [DTMFDetectorEnable] ...
Page 991: Metering Tone Parameters
(that is placed in the AOC-E). Note: This parameter is applicable only to FXS interfaces and ISDN Euro trunks for sending AOC Facility messages (see Advice of Charge Version 6.8 Mediant 800B Gateway and E-SBC...
Page 992 Mediant 800B Gateway and E-SBC Parameter Description Services for Euro ISDN on page 485). Web: Analog Metering Determines the metering method for generating pulses (sinusoidal Type metering burst frequency) by the FXS port. EMS: Metering Type  [0] 12 KHz = (Default) 12 kHz sinusoidal bursts.
Page 993: Telephone Keypad Sequence Parameters
Once the second call is established, on-hooking transfers the first (held) call to the second call. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 994 Mediant 800B Gateway and E-SBC Parameter Description  During an existing call, if a call comes in (call waiting), pressing the flash button places the active call on hold and answers the waiting call; pressing flash again toggles between these two calls.
Page 995 Keypad Feature - Call Waiting Parameters Web: Call Waiting Activate Defines the keypad sequence to activate the Call Waiting EMS: Keypad Features CW option. After the sequence is pressed, a confirmation tone is CLI: cw-act heard. [KeyCallWaiting] Version 6.8 Mediant 800B Gateway and E-SBC...
Page 996: Fxo And Fxs Parameters
Mediant 800B Gateway and E-SBC Parameter Description Web: Call Waiting Deactivate Defines the keypad sequence to deactivate the Call Waiting EMS: Keypad Features CW Deact option. After the sequence is pressed, a confirmation tone is CLI: cw-deact heard. [KeyCallWaitingDeact] Keypad Feature - Reject Anonymous Call Parameters...
Page 997 (to the PSTN/PBX line) only after it detects a dial tone. If this parameter is disabled, the device immediately dials the phone number after seizing the PSTN/PBX line without 'listening' for a dial tone. Version 6.8 Mediant 800B Gateway and E-SBC...
Page 998 Mediant 800B Gateway and E-SBC Parameter Description Notes:  The correct dial tone parameters must be configured in the CPT file.  The device may take 1 to 3 seconds to detect a dial tone (according to the dial tone configuration in the CPT file). If the dial tone is not detected within 6 seconds, the device releases the call and sends a SIP 500 "Server Internal...
Page 999 Defines the duration of the Break connection (off-hook) for FXO pulse dial generation. The valid value range is 20 to 120 (in msec). The default is Note: For this parameter to take effect, a device reset is required Version 6.8 Mediant 800B Gateway and E-SBC...
Page 1000: Trunk Groups And Routing Parameters
Mediant 800B Gateway and E-SBC Parameter Description [PulseDialGenerationMakeTime] Defines the duration of the Make connection (on-hook) for FXO pulse dial generation. The valid value range is 20 to 120 (in msec). The default is Note: For this parameter to take effect, a device reset is required.
Page 1001 Tel Source Number is used as the IP Source Number [UseSourceNumberAsDisplayName] and the Tel Display Name is used as the IP Display Name. If no Display Name is received from the Tel side, Version 6.8 1001 Mediant 800B Gateway and E-SBC...
Page 1002 Mediant 800B Gateway and E-SBC Parameter Description the IP Display Name remains empty.  [1] Yes = If a Tel Display Name is received, the Tel Source Number is used as the IP Source Number and the Tel Display Name is used as the IP Display Name. If...
Page 1003 [1] Secure Incoming calls = The device accepts SIP calls (i.e., calls from the IP side) only from IP addresses that are defined in the Outbound IP Routing table or Proxy Set table, or IP addresses resolved from DNS servers Version 6.8 1003 Mediant 800B Gateway and E-SBC...
Page 1004 Mediant 800B Gateway and E-SBC Parameter Description from FQDN values defined in the Proxy Set table. All other incoming calls are rejected.  [2] Secure All calls = The device accepts SIP calls only from IP addresses (in dotted-decimal notation format) that are defined in the Outbound IP Routing table or Proxy Set table, and rejects all other incoming calls.
Page 1005 INVITE and then sends a new INVITE to a specific IP Group or fax server according to the Outbound IP Routing table rules. To enable this feature, set the Version 6.8 1005 Mediant 800B Gateway and E-SBC...
Page 1006 Mediant 800B Gateway and E-SBC Parameter Description CNGDetectorMode parameter to 2 and the IsFaxUsed parameter to 1, 2, or 3.  [2] Progress and Delay = (Applicable only to ISDN). Incoming ISDN calls are delayed until a CNG tone detection or timeout, set by the FaxReroutingDelay parameter.
Page 1007: Ip Connectivity Parameters
[0] None = Alternative routing is not used. [AltRoutingTel2IPMode]  [1] Connectivity = Alternative routing is performed if SIP OPTIONS message to the initial destination fails (determined according to the AltRoutingTel2IPConnMethod parameter). Version 6.8 1007 Mediant 800B Gateway and E-SBC...
Page 1008: Alternative Routing Parameters
Mediant 800B Gateway and E-SBC Parameter Description  [2] QoS = Alternative routing is performed if poor QoS is detected.  [3] Both = (Default) Alternative routing is performed if either SIP OPTIONS to initial destination fails, poor QoS is detected, or the DNS host name is not resolved.
Page 1009 SIP 404 Not Found response, the call can be re-sent to a different destination number (as defined using the parameter NumberMapTel2IP).  [0] = Disable (default)  [1] = Enable Version 6.8 1009 Mediant 800B Gateway and E-SBC...
Page 1010 Mediant 800B Gateway and E-SBC Parameter Description Web/EMS: Alternative Routing Defines the duration (in milliseconds) for which the device plays a Tone Duration [ms] tone to the endpoint on each attempt for Tel-to-IP alternative CLI: alt-rte-tone-duration routing. When the device finishes playing the tone, a new SIP [AltRoutingToneDuration] INVITE message is sent to the new IP destination.
Page 1011: Number Manipulation Parameters
Enables the use of the B-channel number as the calling number As Calling Number Tel2IP (sent in the From field of the INVITE) instead of the number received EMS: Use EP Number As in the Q.931 Setup message, for Tel-to-IP calls. Version 6.8 1011 Mediant 800B Gateway and E-SBC...
Page 1012 Mediant 800B Gateway and E-SBC Parameter Description  [0] Disable (default) Calling Number Tel to IP CLI: epn-as-cpn-tel2ip  [1] Enable [UseEPNumAsCallingNumTel For example, if the incoming calling party number in the Q.931 Setup 2IP] message is "12345" and the B-channel number is 17, then the outgoing INVITE From header is set to "17"...
Page 1013 [2] User Failed = user provided, verified and failed.  [3] Network Provided = network provided Note: This parameter is applicable only to digital PSTN interfaces (ISDN). Web: Copy Destination Enables the device to copy the received ISDN (digital interfaces) Version 6.8 1013 Mediant 800B Gateway and E-SBC...

AudioCodes Mediant 800B User Manual

1 Overview

Getting Started with Initial Connectivity

2 Introduction

3 Default OAMP IP Address

4 Configuring Voip LAN Interface for OAMP

Management Tools

5 Introduction

6 Web-Based Management

7 CLI-Based Management

8 SNMP-Based Management

9 INI File-Based Management

General System Settings

10 Configuring Certificates

11 Date and Time

General Voip Configuration

12 Network

13 Security

14 Media

15 Services

16 Quality of Experience

17 Control Network

18 SIP Definitions

19 Coders and Profiles

Gateway Application

20 Introduction

21 Digital PSTN

22 Trunk Group

23 Manipulation

24 Routing

25 Configuring DTMF and Dialing

26 Configuring Supplementary Services

Quick Links

Related Manuals for AudioCodes Mediant 800B

Summary of Contents for AudioCodes Mediant 800B