Page 1 Mediant™ 500 E-SBC Enterprise Session Border Controller Digital VoIP Media Gateway User's Manual Version 6.8 September 2014 Document # LTRT-10427...
Page 3: Table Of Contents
Getting Familiar with CLI ..................65 7.1.1 Understanding Configuration Modes ............... 65 7.1.2 Using CLI Shortcuts ....................66 7.1.3 Common CLI Commands ..................67 7.1.4 Configuring Tables in CLI ..................68 7.1.5 Understanding CLI Error Messages ................ 69 Version 6.8 Mediant 500 E-SBC...
Page 4 Mediant 500 E-SBC Enabling CLI ......................69 7.2.1 Enabling Telnet for CLI .................... 69 7.2.2 Enabling SSH with RSA Public Key for CLI ............. 70 Establishing a CLI Session ..................72 Configuring Maximum Telnet/SSH Sessions ............73 Viewing and Terminating Current CLI Sessions ............ 73 Configuring Displayed Output Lines in CLI Terminal Window .......
Page 5 14.2.2.6 Fax / Modem Transparent with Events Mode ........165 14.2.2.7 Fax / Modem Transparent Mode ............165 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......166 14.2.3 V.34 Fax Support ....................166 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........167 Version 6.8 Mediant 500 E-SBC...
Page 6 Mediant 500 E-SBC 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ........... 168 14.2.3.3 V.34 Fax Relay for SG3 Fax Machines ..........168 14.2.4 V.150.1 Modem Relay ...................169 14.2.5 Simultaneous Negotiation of Fax (T.38) and Modem (V.150.1) Relay ....170 14.2.6 V.152 Support ......................171 14.2.7 Fax Transmission behind NAT ................171...
Page 7 21.1 Configuring Trunk Settings ................... 329 21.2 TDM and Timing ....................331 21.2.1 Configuring TDM Bus Settings ................331 21.2.2 Clock Settings ......................332 21.2.2.1 Recovering Clock from PSTN Line Interface ........332 21.2.2.2 Configuring Internal Clock as Clock Source ......... 333 Version 6.8 Mediant 500 E-SBC...
Page 8 Mediant 500 E-SBC 21.3 Configuring CAS State Machines ................. 333 21.4 Configuring Digital Gateway Parameters ............. 336 21.5 Tunneling Applications ..................337 21.5.1 TDM Tunneling ......................337 21.5.1.1 DSP Pattern Detector ................340 21.5.2 QSIG Tunneling .....................340 21.6 ISDN Non-Facility Associated Signaling (NFAS) ..........341 21.6.1 NFAS Interface ID ....................342...
Page 9 26.5.2.1 About E9-1-1 Services ................413 26.5.2.2 Microsoft Lync Server 2010 and E9-1-1 ..........414 26.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 26.5.2.4 Configuring AudioCodes ELIN Gateway ..........422 26.6 Multilevel Precedence and Preemption ..............424 26.6.1 MLPP Preemption Events in SIP Reason Header ..........427...
Page 10 Mediant 500 E-SBC 27.7.1.2 Local Handling of SIP 3xx ..............450 27.7.2 Interworking SIP Diversion and History-Info Headers ...........451 27.7.3 Interworking SIP REFER Messages ..............451 27.7.4 Interworking SIP PRACK Messages ..............452 27.7.5 Interworking SIP Session Timer ................452 27.7.6 Interworking SIP Early Media ................453 27.7.7 Interworking SIP re-INVITE Messages ..............455...
Page 11 38.1.4.3 Dial Plan Prefix Tags for Routing ............545 38.1.4.4 Obtaining IP Destination from Dial Plan File ......... 549 38.1.4.5 Modifying ISDN-to-IP Calling Party Number ......... 550 38.1.5 User Information File .....................551 38.1.5.1 Enabling the User Info Table ..............551 Version 6.8 Mediant 500 E-SBC...
Page 12 39.1.3 Provisioning from TFTP Server using DHCP Option 66 ........571 39.1.4 HTTP-based Provisioning ..................571 39.1.5 FTP- or NFS-based Provisioning ................572 39.1.6 Provisioning using AudioCodes EMS ..............572 39.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 573 39.2.1 Files Provisioned by Automatic Update ..............573 39.2.2 File Location for Automatic Update ...............573...
Page 13 48 Syslog and Debug Recordings ..............637 48.1 Syslog Message Format ..................637 48.1.1 Event Representation in Syslog Messages ............638 48.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......640 48.1.3 SNMP Alarms in Syslog Messages ...............641 48.2 Enabling Syslog ....................642 48.3 Configuring Web Operations to Report to Syslog ..........
Page 14 Mediant 500 E-SBC 49 Self-Testing ...................... 653 50 Creating Core Dump and Debug Files upon Device Crash ......655 51 Testing SIP Signaling Calls ................657 51.1 Configuring Test Call Endpoints ................657 51.2 Starting and Stopping Test Calls ................661 51.3 Viewing Test Call Statistics ..................
Page 15 53.14.3 Least Cost Routing Parameters ................887 53.14.4 Call Setup Rules Parameters ................888 54 SBC and DSP Channel Capacity ..............889 54.1 Signaling-Media Sessions & User Registrations ..........889 54.2 Channel Capacity and Capabilities ..............890 55 Technical Specifications ................891 Version 6.8 Mediant 500 E-SBC...
Page 16 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 17: Weee Eu Directive
This document is subject to change without notice. Date Published: September-07-2014 Trademarks AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect, VoIPerfectHD, What’s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or...
Page 18: Related Documentation
Mediant 500 E-SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 500 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 19 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 20 Mediant 500 E-SBC Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads. User's Manual Document #: LTRT-10427...
Page 21: Overview
Overview The Mediant 500 Enterprise Session Border Controller (E-SBC), hereafter referred to as the device, is a member of AudioCodes family of E-SBCs, enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks. The device provides SBC functionality as well as voice-over-IP (VoIP) media gateway functionality.
Page 22 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 23: Getting Started With Initial Connectivity
Part I Getting Started with Initial Connectivity...
Page 25: 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 500 E-SBC...
Page 26 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 27: Default Oamp Ip Address
The table below lists the device's default 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 "Voice" Version 6.8 Mediant 500 E-SBC...
Page 28 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 29: 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 500 E-SBC...
Page 30 Mediant 500 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 107.
Page 31: Cli
At the prompt, type the password (default is "Admin" - case sensitive): Password: Admin At the prompt, type the following: enable At the prompt, type the password again: Password: Admin Access the VoIP configuration mode: # configure voip Access the Interface table: (config-voip)# interface network-if 0 Version 6.8 Mediant 500 E-SBC...
Page 32 Mediant 500 E-SBC 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> Exit the Interface table: (network-if-0)# exit Exit the VoIP configuration mode:...
Page 33: Management Tools
Part II Management Tools...
Page 35: 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 673. Version 6.8 Mediant 500 E-SBC...
Page 36 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 37: Web-Based Management
Microsoft™ Internet Explorer™ (Version 6.0 and later) • ® 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 500 E-SBC...
Page 38: Accessing The Web Interface
Mediant 500 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 37). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...
Page 39: Areas Of The Gui
''Navigation Tree'' on page 41. 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 43. Version 6.8 Mediant 500 E-SBC...
Page 40: Toolbar Description
Mediant 500 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 530).
Page 41: 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 500 E-SBC...
Page 42: Showing / Hiding The Navigation Pane
Mediant 500 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 43: 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 500 E-SBC...
Page 44 Mediant 500 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 45: Modifying And Saving Parameters
Thus, to ensure parameter changes (whether on-the-fly or not) are retained, save ('burn') them to the device's non-volatile memory, i.e., flash (see ''Saving Configuration'' on page 530). Version 6.8 Mediant 500 E-SBC...
Page 46: Working With Tables
Mediant 500 E-SBC If you enter an invalid parameter value (e.g., not in the range of permitted values) and then click Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts to its previous value and is highlighted in red, as shown in the...
Page 47: Searching For Configuration Parameters
The search key can include the full parameter name (e.g., "EnableSyslog") or a substring of it (e.g., "sys"). If you search for a substring, all parameters containing the specified substring in their names are listed in the search result. Version 6.8 Mediant 500 E-SBC...
Page 48 Mediant 500 E-SBC  To search for a parameter: On the Navigation bar, click the Search tab; the Search engine appears in the Navigation pane. In the field alongside the Search button, enter the parameter name or a substring of the name for which you want to search.
Page 49: Creating A Login Welcome Message
WelcomeMessage 2 = "********* This is a Welcome message **"; WelcomeMessage 3 = "*********************************"; [\WelcomeMessage] Each index row represents a line of text in the Welcome message box. Up to 20 lines (or rows) of text can be defined. Version 6.8 Mediant 500 E-SBC...
Page 50: Getting Help
Mediant 500 E-SBC 6.1.9 Getting Help The Web interface provides you with context-sensitive Online Help. The Online Help provides brief descriptions of parameters pertaining to the currently opened page.  To view the Help topic of a currently opened page: On the toolbar, click the Help button;...
Page 51: Logging Off The Web Interface
 To access the Home page:  On the toolbar, click the Home icon. Figure 6-16: Home Page Note: The displayed number and type of telephony interfaces depends on the ordered hardware configuration. Version 6.8 Mediant 500 E-SBC...
Page 52 Mediant 500 E-SBC In addition to the color-coded status information depicted on the graphical display of the device, the Home page displays various read-only information in the General Information pane:  IP Address: IP address of the device  Subnet Mask: Subnet mask address of the device ...
Page 53: Assigning A Port Name
Open the Home page. Click the required port icon; a shortcut menu appears: From the shortcut menu, choose Update Port Info; a text box appears: Type a brief description for the port, and then click Apply Port Info. Version 6.8 Mediant 500 E-SBC...
Page 54: Configuring Web User Accounts
Mediant 500 E-SBC Configuring Web User Accounts Web user accounts define users for the Web interface and CLI. User accounts permit login access to these interfaces as well as different levels of read and write privileges. Thus, user accounts prevent unauthorized access to these interfaces, permitting access only to users with correct credentials (i.e., username and password).
Page 55: 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 500 E-SBC...
Page 56 Mediant 500 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). If you are logged in with the second user account, only the details of this user account are displayed.
Page 57: 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 500 E-SBC...
Page 58 Mediant 500 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 59 The default is according to the settings of the 'Deny Authentication Timer' parameter (see ''Configuring Web Security Settings'' on page 61). Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Version 6.8 Mediant 500 E-SBC...
Page 60: Displaying Login Information Upon Login
Mediant 500 E-SBC Parameter Description Web: User Level Defines the user's access level. CLI: user-level  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 61: 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 500 E-SBC...
Page 62: Configuring Web And Telnet Access List
Mediant 500 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 63 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 500 E-SBC...
Page 64 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 65: Cli-Based Management
This mode allows you to view various information (using the show commands) and activate various debugging capabilities. Welcome to AudioCodes CLI Username: Admin Password: >...
Page 66: Using Cli Shortcuts
Mediant 500 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: # configure system (config-system)# •...
Page 67: Common Cli Commands
Displays the available command list of the current command-set. list | <filter> 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> Version 6.8 Mediant 500 E-SBC...
Page 68: Configuring Tables In Cli
Mediant 500 E-SBC Command Description  exclude <word> – filter lines which does not contain <word>  grep <options> - filter lines according to grep common Unix utility options  egrep <options> - filter lines according to egrep common Unix utility options ...
Page 69: Understanding Cli Error Messages
Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 677. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500 E-SBC...
Page 70: Enabling Ssh With Rsa Public Key For Cli
Mediant 500 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 71 'Admin Key' field. Click Submit. Connect to the device with SSH, using the following command: ssh -i admin.key xx.xx.xx.xx where xx.xx.xx.xx is the device's IP address. RSA-key negotiation occurs automatically and no password is required. Version 6.8 Mediant 500 E-SBC...
Page 72: Establishing A Cli Session
Mediant 500 E-SBC Establishing a CLI Session The device's CLI can be accessed using any of the following methods:  RS-232: The device can be accessed through its RS-232 serial port, by connecting a VT100 terminal to it or using a terminal emulation program (e.g., HyperTerminal) with a PC.
Page 73: Configuring Maximum Telnet/Ssh Sessions
# clear user <session ID> 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 500 E-SBC...
Page 74: Configuring Displayed Output Lines In Cli Terminal Window
Mediant 500 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 75: 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 76: Configuring Snmp Trap Destinations
Mediant 500 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 77 (default) = SNMPv2 user community string  SNMPv3 user configured in ''Configuring SNMP V3 Users'' on page Trap Enable Activates the sending of traps to the SNMP Manager. [SNMPManagerTrapSendingEnable_x]  [0] Disable  [1] Enable (Default) Version 6.8 Mediant 500 E-SBC...
Page 78: Configuring Snmp Trusted Managers
Mediant 500 E-SBC Configuring SNMP Trusted Managers The SNMP Trusted Managers table lets you configure up to five SNMP Trusted Managers based on IP addresses. By default, the SNMP agent accepts SNMP Get and Set requests from any IP address as long as the correct community string is used in the request.
Page 79: Configuring Snmp V3 Users
Name of the SNMP v3 user. This name must be unique. CLI: username [SNMPUsers_Username] Authentication Protocol Authentication protocol of the SNMP v3 user. CLI: auth-protocol  [0] None (default) [SNMPUsers_AuthProtocol]  [1] MD5  [2] SHA-1 Privacy Protocol Privacy protocol of the SNMP v3 user. Version 6.8 Mediant 500 E-SBC...
Page 80 Mediant 500 E-SBC Parameter Description  CLI: priv-protocol [0] None (default) [SNMPUsers_PrivProtocol]  [1] DES  [2] 3DES  [3] AES-128  [4] AES-192  [5] AES-256 Authentication Key Authentication key. Keys can be entered in the form of a text CLI: auth-key password or long hex string.
Page 81: Ini File-Based Management
The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME].  Format line: Specifies the columns of the table (by their string names) that are to be Version 6.8 Mediant 500 E-SBC...
Page 82 Mediant 500 E-SBC configured. • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed. • Columns must be separated by a comma ",".
Page 83: General Ini File Formatting Rules
Save the file with the ini file extension name (e.g., myconfiguration.ini). Load the file to the device. For loading the ini file to the device, see ''Loading an ini File to the Device'' on page 84. Version 6.8 Mediant 500 E-SBC...
Page 84: 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 85: Configuring Password Display In Ini File
$0$<plain text>: Password can be entered in plain text; useful for configuring a new password. When the ini file is loaded to the device and then later saved from the device to a PC, the password is displayed obscured (i.e., $1$<obscured password>). Version 6.8 Mediant 500 E-SBC...
Page 86: Ini Viewer And Editor Utility
Mediant 500 E-SBC INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any Windows-based PC.
Page 87: General System Settings
Part III General System Settings...
Page 89: 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 500 E-SBC...
Page 90 Mediant 500 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 91 TLS version supported by both peers.  [1] 1 = Only TLS 1.0 is used. Clients attempting to contact the device using any other version are rejected. Version 6.8 Mediant 500 E-SBC...
Page 92 Mediant 500 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 93: Assigning Csr-Based Certificates To Tls Contexts
Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-2: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request. Version 6.8 Mediant 500 E-SBC...
Page 94: Assigning Externally Created Private Keys To Tls Contexts
Mediant 500 E-SBC When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below:...
Page 95: Generating Private Keys For Tls Contexts
Figure 10-5: Generate new private key and self-signed certificate Group From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys: • • 1024 (default) • 2048 Version 6.8 Mediant 500 E-SBC...
Page 96: Creating Self-Signed Certificates For Tls Contexts
Mediant 500 E-SBC Click Generate Private Key; a message appears requesting you to confirm key generation. Click OK to confirm key generation; the device generates a new private key, indicated by a message in the Certificate Signing Request group. Figure 10-6: Indication of Newly Generated Private Key Continue with the certificate configuration, by either creating a CSR or generating a new self-signed certificate.
Page 97: Importing Certificates And Certificate Chain Into Trusted Certificate Store
Open the TLS Contexts page (Configuration tab > System menu > TLS Contexts). In the TLS Contexts table, select the required TLS Context index row, and then click the Context Trusted-Roots button, located at the bottom of the TLS Contexts page; the Trusted Certificates page appears. Version 6.8 Mediant 500 E-SBC...
Page 98: Configuring Mutual Tls Authentication
Mediant 500 E-SBC Click the Import button, and then select the certificate file to load. Figure 10-9: Importing Certificate into Trusted Certificates Store Click OK; the certificate is loaded to the device and listed in the Trusted Certificates store. You can also do the following with certificates that are in the Trusted Certificates store: ...
Page 99: Tls For Remote Device Management
The root certificate can also be loaded via the Automatic Update facility, using the HTTPSRootFileName ini file parameter. • You can enable the device to check whether a peer's certificate has been revoked by an OCSP server, per TLS Context (see 'Configuring TLS Certificate Contexts' on page 89). Version 6.8 Mediant 500 E-SBC...
Page 100: Configuring Tls Server Certificate Expiry Check
Mediant 500 E-SBC 10.1.8 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure device send...
Page 101: Date And Time
"1". For USA New York, the UTC/GMT offset is -5 hours and therefore, the offset is a minus value and configured as "-5". To configure Daylight Saving Time (DST), see 'Configuring Daylight Saving Time' on page 103. Version 6.8 Mediant 500 E-SBC...
Page 102 Mediant 500 E-SBC 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 cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication.
Page 103: 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 101). Version 6.8 Mediant 500 E-SBC...
Page 104 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 105: General Voip Configuration
Part IV General VoIP Configuration...
Page 107: Network
100Mbps FULL DOWN The following procedure describes how to configure the Ethernet ports in the Web interface. You can also configure these ports using the table ini file parameter, PhysicalPortsTable or CLI command, configure voip/physical-port. Version 6.8 Mediant 500 E-SBC...
Page 108 Mediant 500 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 109: Configuring Ethernet Port Groups
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. Version 6.8 Mediant 500 E-SBC...
Page 110 Mediant 500 E-SBC  To configure Ethernet Groups: Open the Ethernet Group Settings page (Configuration tab > VoIP menu > Network > Ethernet Groups Table). If the port that you want to assign to a specific Ethernet Group is already associated...
Page 111: Configuring Underlying Ethernet Devices
IP network interface can it be deleted. The following procedure describes how to configure Ethernet devices in the Web interface. You can also configure this using the table ini file parameter, DeviceTable or CLI command, config-voip > interface network-dev. Version 6.8 Mediant 500 E-SBC...
Page 112 Mediant 500 E-SBC  To configure an Ethernet Device: Open the Ethernet Device Table page (Configuration tab > VoIP menu > Network > Ethernet Device Table). Click Add; the following dialog box appears: Configure an Ethernet Device according to the parameters described in the table below.
Page 113: Configuring Ip Network Interfaces
HA and the Maintenance interface, see Configuring High Availability on page 510.  IP address (IPv4 and IPv6) and subnet mask (prefix length)  For configuring Quality of Service (QoS), see ''Configuring the QoS Settings'' on page 124. Version 6.8 Mediant 500 E-SBC...
Page 114 Mediant 500 E-SBC  Default Gateway: Traffic from this interface destined to a subnet that does not meet any of the routing rules (local or static) are forwarded to this gateway  Primary and secondary domain name server (DNS) addresses (optional) ...
Page 115 The CIDR- style presentation is the latest method for interpretation of IP addresses. Specifically, instead of using eight-bit address blocks, it uses the variable-length subnet masking technique to allow allocation on arbitrary-length prefixes. Version 6.8 Mediant 500 E-SBC...
Page 116: Assigning Ntp Services To Application Types
Mediant 500 E-SBC Parameter Description The prefix length for IPv4 must be set to a value from 0 to 30. The 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.
Page 117: 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 500 E-SBC...
Page 118: Voip Interface Per Application Type
Mediant 500 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 119 ♦ 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 500 E-SBC...
Page 120: Voip Interfaces With Multiple Default Gateways
Mediant 500 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 121 For example, the value 16 represents subnet 255.255.0.0. The value must be 0 to 31 for IPv4 interfaces and a value of 0 to 64 for IPv6 interfaces. Version 6.8 Mediant 500 E-SBC...
Page 122: Configuration Example Of Static Ip Routes
Mediant 500 E-SBC Parameter Description The address of the host/network you want to reach is determined by an AND operation that is applied to the fields 'Destination' and 'Prefix Length'. For example, to reach the network 10.8.x.x, enter 10.8.0.0 in the 'Destination' field and 16 in the 'Prefix Length'. As a result of the AND operation, the value of the last two octets in the 'Destination' field is ignored.
Page 123: 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 500 E-SBC...
Page 124: Configuring Quality Of Service
Mediant 500 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 125 Defines the VLAN priority level. CLI: vlan-priority The valid value is 0 to 7. [DiffServToVlanPriority_VlanPriority] Under the Differentiated Services group, configure DiffServ (Layer-3 QoS) values per CoS. Figure 12-8: QoS Settings Page - Differentiated Services Version 6.8 Mediant 500 E-SBC...
Page 126: Configuring Icmp Messages
Mediant 500 E-SBC 12.7 Configuring ICMP Messages Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol suite. It is used by network devices such as routers to send error messages indicating, for example, that a requested service is unavailable.
Page 127 Defines the third IP address (in dotted-decimal format notation) to CLI: third-ip-address which the host name is translated. [Dns2Ip_ThirdIpAddress] Fourth IP Address Defines the fourth IP address (in dotted-decimal format notation) to CLI: fourth-ip-address which the host name is translated. [Dns2Ip_FourthIpAddress] Version 6.8 Mediant 500 E-SBC...
Page 128: Configuring The Internal Srv Table
Mediant 500 E-SBC 12.8.2 Configuring the Internal SRV Table The Internal SRV table resolves host names to DNS A-Records. Three different A-Records can be assigned to each host name, where each A-Record contains the host name, priority, weight, and port.
Page 129 [Srv2Ip_Priority1/2/3] 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 500 E-SBC...
Page 130: Configuring Nfs Settings
Mediant 500 E-SBC 12.9 Configuring NFS Settings Network File System (NFS) enables the device to access a remote server's shared files and directories and to handle them as if they're located locally. The device can use NFS to load cmp, ini, and auxiliary files through the Automatic Update mechanism (see Configuration using FTP or NFS).
Page 131 The VLAN type for accessing the remote file system. CLI: vlan-type  [0] OAMP [NFSServers_VlanType]  [1] Media (default) Note: This parameter applies only if VLANs are enabled or if Multiple IPs is configured (see ''Configuring IP Network Interfaces'' on page 113). Version 6.8 Mediant 500 E-SBC...
Page 132: Network Address Translation Support
Mediant 500 E-SBC 12.10 Network Address Translation Support Network Address Translation (NAT) is a mechanism that maps internal IP addresses (and ports) used within a private network to global IP addresses and vice versa, providing transparent routing to end hosts. The primary advantages of NAT include (1) reduction in...
Page 133: Configuring A Static Nat Ip Address For All Interfaces
Figure 12-14: Configuring Static NAT IP Address in SIP General Parameters Page In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 500 E-SBC...
Page 134: Configuring Nat Translation Per Ip Interface
Mediant 500 E-SBC 12.10.1.2 Configuring NAT Translation per IP Interface The NAT Translation table lets you configure up to 32 network address translation (NAT) rules for translating source IP addresses per VoIP interface (SIP control and RTP media traffic) into NAT IP addresses (global or public), when the device is located behind NAT.
Page 135: Remote Ua Behind Nat
Use Source Address' parameter in the IP Group table (see ''Configuring IP Groups'' on page 260). If this feature is disabled, the device's NAT detection is according to the settings of the global parameter, 'SIP NAT Detection' parameter. Version 6.8 Mediant 500 E-SBC...
Page 136: Media (Rtp/Rtcp/T.38)
Mediant 500 E-SBC 12.10.2.2 Media (RTP/RTCP/T.38) When a remote UA initiates a call and is not located behind a NAT server, the device sends the RTP (or RTCP, T.38) packets to the remote UA using the IP address / UDP port in the SIP message (Contact header).
Page 137 T.38 No-Op: T.38 No-Op packets are sent only while a T.38 session is activated. Sent packets are a duplication of the previously sent frame (including duplication of the sequence number). Note: Receipt of No-Op packets is always supported. Version 6.8 Mediant 500 E-SBC...
Page 138: Robust Receipt Of Media Streams By Media Latching
Mediant 500 E-SBC 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 139 'Timeout To Relatch RTCP' ♦ 'Fax Relay Rx/Tx Timeout' Click Submit, and then save ("burn") your settings to flash memory. For a detailed description of the robust media parameters, see ''General Security Parameters'' on page 703. Version 6.8 Mediant 500 E-SBC...
Page 140: Multiple Routers Support
Mediant 500 E-SBC 12.12 Multiple Routers Support Multiple routers support is designed to assist the device when it operates in a multiple routers network. The device learns the network topology by responding to Internet Control Message Protocol (ICMP) redirections and caches them as routing rules (with expiration time).
Page 141: 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 521. Version 6.8 Mediant 500 E-SBC...
Page 142 Mediant 500 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 143 The list displays interface names as defined in the Interface table in [AccessList_Interface_x] ''Configuring IP Network Interfaces'' on page 113. Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. Version 6.8 Mediant 500 E-SBC...
Page 144 Mediant 500 E-SBC Parameter Description [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. Byte Rate Defines the expected traffic rate (bytes per second), i.e., the allowed CLI: byte-rate bandwidth for the specified protocol.
Page 145: 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 500 E-SBC...
Page 146: Intrusion Detection System
Mediant 500 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 147: 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 500 E-SBC...
Page 148 Mediant 500 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 149 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 470)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response) Version 6.8 Mediant 500 E-SBC...
Page 150 Mediant 500 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 151: 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 500 E-SBC...
Page 152: Viewing Ids Alarms
Mediant 500 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 153 Syslog String Connection TLS authentication failure abuse-tls-auth-fail Abuse   Message exceeds a user-defined maximum malformed-invalid- Malformed message length (50K) msg-len Messages   Any SIP parser error malformed-parse-error   Message policy match malformed-message- Version 6.8 Mediant 500 E-SBC...
Page 154 Mediant 500 E-SBC Type Description Syslog String  Basic headers not present policy   Content length header not present (for TCP) malformed-miss- header  Header overflow  malformed-miss- content-len  malformed-header- overflow   Local authentication ("Bad digest" errors)
Page 155: 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 500 E-SBC...
Page 156: Echo Cancellation
Mediant 500 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 157: 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 171. • For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 673. Version 6.8 Mediant 500 E-SBC...
Page 158 Mediant 500 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-10427...
Page 159: Fax/Modem Operating Modes
You can change the fax rate declared in the SDP, using the 'Fax Relay Max Rate' parameter (FaxRelayMaxRate). This parameter does not affect the actual transmission rate. You can also enable or disable Error Correction Mode (ECM) fax mode using the 'Fax Relay ECM Enable' parameter (FaxRelayECMEnable). Version 6.8 Mediant 500 E-SBC...
Page 160 Mediant 500 E-SBC When using T.38 mode, you can define a redundancy feature to improve fax transmission over congested IP networks. This feature is activated using the 'Fax Relay Redundancy Depth' parameter (FaxRelayRedundancyDepth) 'Fax Relay Enhanced Redundancy Depth' parameter (FaxRelayEnhancedRedundancyDepth). Although this is a proprietary redundancy scheme, it should not create problems when working with other T.38 decoders.
Page 161 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 162: Fax / Modem Transport Mode
Mediant 500 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 163: 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 500 E-SBC...
Page 164: 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 165: Fax / Modem Transparent With Events Mode
Definitions > General Parameters), set the 'Fax Signaling Method' parameter to No Fax (IsFaxUsed = 0). In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Version 6.8 Mediant 500 E-SBC...
Page 166: Rfc 2833 Ans Report Upon Fax/Modem Detection
Mediant 500 E-SBC Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0). Set the 'V.23 Modem Transport Type' parameter to Disable (V23ModemTransportType = 0). Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0).
Page 167: 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 500 E-SBC...
Page 168: Relay Mode For T.30 And V.34 Faxes
Mediant 500 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 169: Modem Relay
SIP INVITE and 200 OK, using the SDP body according to the USA Department of Defense (DoD) UCR-2008, Change 2 specification. This eliminates the need for sending a re-INVITE to negotiate V.150.1. The device sends an INVITE’s SDP offer in a Version 6.8 Mediant 500 E-SBC...
Page 170: Simultaneous Negotiation Of Fax (T.38) And Modem (V.150.1) Relay
• The V.150.1 feature has been tested with certain IP phones. For more details, please contact your AudioCodes sales representative. • The V.150.1 SSE Tx payload type is according to the offered SDP of the remote side.
Page 171: Support
The device supports transmission from fax machines (connected to the device) located inside (behind) a Network Address Translation (NAT). Generally, the firewall blocks T.38 (and other) packets received from the WAN, unless the device behind the NAT sends at Version 6.8 Mediant 500 E-SBC...
Page 172: Configuring Rtp/Rtcp Settings
Mediant 500 E-SBC least one IP packet from the LAN to the WAN through the firewall. If the firewall blocks T.38 packets sent from the termination IP fax, the fax fails. To overcome this, the device sends No-Op (“no-signal”) packets to open a pinhole in the NAT for the answering fax machine.
Page 173: Comfort Noise Generation
Figure 14-4: Comfort Noise Parameter in RTP/RTCP Settings Page Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Click Submit. Note: This feature is applicable only to the Gateway application. Version 6.8 Mediant 500 E-SBC...
Page 174: Dual-Tone Multi-Frequency Signaling
Mediant 500 E-SBC 14.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 14.3.3.1 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint. These methods and their configuration are configured in the DTMF &...
Page 175: Configuring Rfc 2833 Payload
'RFC 2833 RX Payload Type' (RFC2833RxPayloadType) - defines the Rx RFC 2833 DTMF relay dynamic payload type. • 'RFC 2198 Payload Type' (RFC2198PayloadType) - defines the RTP redundancy packet payload type according to RFC 2198. Click Submit. Version 6.8 Mediant 500 E-SBC...
Page 176: Configuring Rtp Base Udp Port
Mediant 500 E-SBC 14.3.4 Configuring RTP Base UDP Port You can configure the range of local UDP ports for RTP, RTCP, and T.38 media streams. The range of possible UDP ports that can be used, depending on configuration, is 6,000 through to 65,535.
Page 177: Configuring Ip Media Settings
'AGC Minimum Gain' (AGCMinGain) - Defines the minimum gain (in dB) by the AGC when activated. • 'AGC Maximum Gain' (AGCMaxGain) - Defines the maximum gain (in dB) by the AGC when activated. • 'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. Version 6.8 Mediant 500 E-SBC...
Page 178: Configuring Various Codec Attributes
Mediant 500 E-SBC When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. This parameter can either be the global parameter or per IP Profile. Click Submit. 14.5 Configuring Various Codec Attributes The following codec attribute settings can be configured in the General Media Settings page: ...
Page 179 Notes: • For a detailed description of the SRTP parameters, see ''SRTP Parameters'' on page 707. • When SRTP is used, the channel capacity may be reduced. Version 6.8 Mediant 500 E-SBC...
Page 180 Mediant 500 E-SBC  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Figure 14-9: Media Security Page Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required.
Page 181: Services
IP Address Lease Time Option 1 Subnet Mask Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Version 6.8 Mediant 500 E-SBC...
Page 182 Mediant 500 E-SBC DHCP Option Code DHCP Option Name Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
Page 183 Web: DNS Server 2 Defines the IP address (IPv4) of the secondary DNS server CLI: dns-server-2 that the DHCP server assigns to the DHCP client. The value [DhcpServer_DNSServer2] is sent in DHCP Option 6 (Domain Name Server). Version 6.8 Mediant 500 E-SBC...
Page 184 Mediant 500 E-SBC Parameter Description Web: NetBIOS Name Server 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).
Page 185: 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 186: Configuring Additional Dhcp Options
Mediant 500 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. Table 15-3: DHCP Vendor Class Table Parameter Descriptions...
Page 187  [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 500 E-SBC...
Page 188: Configuring Static Ip Addresses For Dhcp Clients
Mediant 500 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 189: Viewing And Deleting 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  To view DHCP clients that have been blacklisted from DHCP implementation (due to Version 6.8 Mediant 500 E-SBC...
Page 190 Mediant 500 E-SBC 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  To view or delete DHCP clients: Open the DHCP Servers page (Configuration tab > VoIP menu > Services > DHCP Severs).
Page 191: Sip-Based Media Recording
• For the maximum number of concurrent sessions that the device can record, contact your AudioCodes sales representative. Session recording is a critical requirement in many business communications environments such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons.
Page 192 Mediant 500 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. This recording leg must be one that is interfacing with one of the IP Groups.
Page 193 <group id="00000000-0000-0000-0000-00003a36c4e3"> <associate-time>2010-01-24T01:11:57Z</associate-time> </group> <session id="0000-0000-0000-0000-00000000d0d71a52"> <group-ref>00000000-0000-0000-0000-00003a36c4e3</group-ref> <start-time>2010-01-24T01:11:57Z</start-time> <ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">FA080030C4E34B5B9E59</ac:Avay aUCID> </session> <participant id="1056" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="1056@192.168.241.20"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <send>00000000-0000-0000-0000-1CF23A36C4E3</send> <recv>00000000-0000-0000-0000-BF583A36C4E3</recv> </participant> <participant id="182052092" session="0000-0000-0000-0000- 00000000d0d71a52"> <nameID aor="182052092@voicelab.local"></nameID> <associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- Version 6.8 Mediant 500 E-SBC...
Page 194: Enabling Sip-Based Media Recording
Mediant 500 E-SBC 0000-0000-0000-00000000d0d71a52"> <label>1</label> </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label> </stream> </recording> --boundary_ac1fffff85b— 15.2.1 Enabling SIP-based Media Recording The following procedure describes how to enable the SIP-based media Recording feature. Once you have enabled this feature, your SIP Recording Routing rules (configured in ''Configuring SIP Recording Routing Rules'' on page 194) become active.
Page 195 SIP Interfaces are associated with the SRD - one for "SBC" and one for "GW &IP2IP" – the device uses the "SBC" SIP Interface. If no SBC SIP Interface type is configured, the device uses the “GW & IP2IP” interface. Version 6.8 Mediant 500 E-SBC...
Page 196: 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 197: 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 500 E-SBC...
Page 198: 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 199: 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 500 E-SBC...
Page 200: Securing Radius Communication
Mediant 500 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. ♦ Verify Access Locally: device checks the username and password configured locally for the user (in the Web User Accounts page or Web Users table), and if correct, allows access.
Page 201: Ldap-Based Management And Sip Services
CN=\# Support Dept,OU=R&D Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=a bc,DC=com The device then assigns the user the access level configured for that group (in 'Configuring Access Level per Management Groups Attributes' on page 208). The Version 6.8 Mediant 500 E-SBC...
Page 202: Enabling The Ldap Service
Mediant 500 E-SBC location in the directory where you want to search for the user's member group(s) is configured using the following: • 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 206.
Page 203: Configuring Ldap Servers
Figure 15-11: LDAP Configuration Table - Add Record 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 Version 6.8 Mediant 500 E-SBC...
Page 204 Mediant 500 E-SBC Parameter Description dex] Note: Each table row must be configured with a unique index. LDAP Server IP Defines the IP address of the LDAP server (in dotted-decimal notation, CLI: server-ip e.g., 192.10.1.255). [LdapConfiguration_Ld By default, no IP address is defined.
Page 205 (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 208. Version 6.8 Mediant 500 E-SBC...
Page 206: Configuring Ldap Dns (Base Paths) Per Ldap Server
Mediant 500 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 207: Configuring The Ldap Search Filter Attribute
The search filter is applicable only to LDAP-based login authentication and authorization queries. • The search filter is a global setting that applies to all LDAP-based login authentication and authorization queries, across all configured LDAP servers. Version 6.8 Mediant 500 E-SBC...
Page 208: Configuring Access Level Per Management Groups Attributes
Mediant 500 E-SBC  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 Under LDAP Settings, in the 'LDAP Authentication Filter' parameter, enter the LDAP search filter attribute for searching the login username for user authentication.
Page 209 Defines an index number for the new table record. [MgmntLDAPGroups_ Note: Each table row must be configured with a unique index. GroupIndex] Level Defines the access level of the group(s). [MgmntLDAPGroups_L  [0] Monitor (Default) evel]  [1] Security Administrator  [2] Administrator Version 6.8 Mediant 500 E-SBC...
Page 210: Configuring Ldap Search Methods
Mediant 500 E-SBC Parameter Description Groups 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 (;).
Page 211 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. However, for subsequent queries, the device does not use the partially cached result, but does a new query with the LDAP server again. Version 6.8 Mediant 500 E-SBC...
Page 212: Configuring Local Database For Management User Authentication
Mediant 500 E-SBC The following procedure describes how to configure the device's LDAP cache in the Web interface. For a full description of the cache parameters, see 'LDAP Parameters' on page 887.  To configure the LDAP cache: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP >...
Page 213 Server Timeout' drop-down list, select one of the following: ♦ Deny Access: User is denied access to the management platform. ♦ Verify Access Locally (default): The device verifies the user's credentials in the Web Users table. Click Submit. Version 6.8 Mediant 500 E-SBC...
Page 214: Ldap-Based Login Authentication Example
Mediant 500 E-SBC 15.4.10 LDAP-based Login Authentication Example To facilitate your understanding on LDAP entry data structure and how to configure the device to use and obtain information from this LDAP directory, a brief configuration example is described in this section. The example applies to LDAP-based user login authentication and authorization (access level), and assumes that you are familiar with other aspects of LDAP configuration (e.g., LDAP server's address).
Page 215 (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 user: Figure 15-21: User's memberOf Attribute Version 6.8 Mediant 500 E-SBC...
Page 216 Mediant 500 E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-22: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
Page 217 The management group and its corresponding access level is configured in the Management LDAP Groups table (see 'Configuring Access Level per Management Groups Attributes' on page 208): Figure 15-26: Configuring Management Group Attributes for Determining Access Level Version 6.8 Mediant 500 E-SBC...
Page 218: Active Directory-Based Routing For Microsoft Lync
Mediant 500 E-SBC 15.4.11 Active Directory-based Routing for Microsoft Lync Typically, enterprises wishing to deploy the Microsoft® Lync™ Server are faced with a complex, call routing dial plan when migrating users from their existing PBX or IP PBX to the Lync Server platform. As more and more end-users migrate to the new voice system, dialing plan management and PBX link capacity can be adversely impacted.
Page 219 Alternative route: If the call routing to all the above fails (e.g., due to unavailable destination - call busy), the device can route the call to an alternative destination if an alternative routing rule is configured. Version 6.8 Mediant 500 E-SBC...
Page 220 Mediant 500 E-SBC "Redundant" route: If the query failed (i.e., no attribute found in the AD), the device uses the routing rule matching the "LDAP_ERR" prefix destination number value. Note: For Enterprises implementing a PBX / IP PBX system, but yet to migrate to Lync Server, if the PBX / IP PBX system is unavailable or has failed, the device uses the AD query result for the user’s mobile phone number, routing the call through the...
Page 221: Configuring Ad-Based Routing Rules
Lync clients, and mobile), using the LDAP keywords (case-sensitive) in the Destination Username Prefix field: ♦ PRIVATE: Private number ♦ OCS: Lync client number ♦ PBX: PBX / IP PBX number ♦ MOBILE: Mobile number Version 6.8 Mediant 500 E-SBC...
Page 222 Mediant 500 E-SBC ♦ LDAP_ERR: LDAP query failure Configure a routing rule for routing the initial call (LDAP query) to the LDAP server, by setting the 'Destination Type' field to LDAP for denoting the IP address of the LDAP server.
Page 223: Querying The Ad For Calling Name
Notes: • The Calling Name Manipulation Table for Tel-to-IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value. Version 6.8 Mediant 500 E-SBC...
Page 224: Least Cost Routing
Mediant 500 E-SBC 15.5 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how to configure it. 15.5.1 Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost.
Page 225 Index 3 - no Cost Group is assigned, but as the Default Cost parameter is set to Min, it is selected as the cheapest route • Index 4 - Cost Group "B" is only second-matched rule (Index 1 is the first) Version 6.8 Mediant 500 E-SBC...
Page 226: Configuring Lcr
Mediant 500 E-SBC  Example 3: This example shows how the cost of a call is calculated if the call spans over multiple time bands: Assume a Cost Group, "CG Local" is configured with two time bands, as shown below:...
Page 227 (default.)  [1] Highest Cost = If the device locates other matching LCR routing rules, this routing rule is considered as the Version 6.8 Mediant 500 E-SBC...
Page 228: Configuring Cost Groups
Mediant 500 E-SBC Parameter Description highest cost route and therefore, is not used or used only if the other cheaper routes are unavailable. Note: If more than one valid routing rule without a defined Cost Group exists, the device selects the first-matched rule.
Page 229: Configuring Time Bands For Cost Groups
Click Submit, and then save ("burn") your settings to flash memory. Table 15-10: Time Band Table Description Parameter Description Index Defines an index number for the new table record. CLI: timeband-index Note: Each table row must be configured with a unique index. [CostGroupTimebands_Time Version 6.8 Mediant 500 E-SBC...
Page 230: Assigning Cost Groups To Routing Rules
Mediant 500 E-SBC Parameter Description bandIndex] Start Time Defines the day and time of day from when this time band is CLI: start-time applicable. The format is DDD:hh:mm, where: [CostGroupTimebands_StartT  DDD is the day of the week, represented by the first three letters ime] of the day in upper case (i.e., SUN, MON, TUE, WED, THU,...
Page 231: Configuring Call Setup Rules
If an Exit Action Type is not configured and the device has run all the rules in the Set ID, the default Action Value of the Set ID is "True" (i.e., use the current Version 6.8 Mediant 500 E-SBC...
Page 232 Mediant 500 E-SBC routing rule).  Rule's condition is not met: The device runs the next rule in the Set ID. When the device reaches the end of the Set ID and no Exit was performed, the Set ID ends with a "True"...
Page 233 (attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called number is the same as the number in the attribute "msRTCSIP-PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Version 6.8 Mediant 500 E-SBC...
Page 234 Mediant 500 E-SBC Parameter Description Action Subject Defines the element (header, parameter, or body) upon CLI: action-subject which you want to perform the action. [CallSetupRules_ActionSubject] The valid value is a string of up to 100 characters (case- insensitive). Examples: ...
Page 235: Call Setup Rule Examples
♦ 'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName • Routing table configuration: A single routing rule is assigned the Call Setup Rule Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 2 Version 6.8 Mediant 500 E-SBC...
Page 236 Mediant 500 E-SBC  Example 3: This example configures the device to route the incoming call according to whether or not the source number of the incoming call also exists in the AD server. The device queries the AD server for the attribute record, "telephoneNumber" whose value is the same as the received source number (e.g., telephoneNumber=4064").
Page 237: 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 238: 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 239  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 237.
Page 240 Mediant 500 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 241 MOS of 3.2, the value 32 (i.e., 3.2*10) must be entered.  Delay values are in msec.  Packet Loss values are in percentage (%).  Jitter is in msec.  Echo measures the Residual Echo Return Loss (RERL) in dB. Version 6.8 Mediant 500 E-SBC...
Page 242: Configuring Bandwidth Profiles
Mediant 500 E-SBC Parameter Description Yellow Red Hysteresis Defines the fluctuation (change) from the value configured for the CLI: yellow-red-hysteresis Yellow-Red threshold. When the threshold is exceeded by this [QOEColorRules_YellowRedH hysteresis value, the device sends a report to the SEM indicating ysteresis] this change.
Page 243 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] Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). CLI: ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Version 6.8 Mediant 500 E-SBC...
Page 244: Configuring Media Enhancement Profiles
Mediant 500 E-SBC Parameter Description Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth CLI: total-egress-bandwidth threshold (in Kbps). [BWProfile_TotalEgressBandwidth] Total Ingress Bandwidth Defines the total (video and audio) incoming bandwidth CLI: total-ingress-bandwidth threshold (in Kbps). [BWProfile_TotalIngressBandwidth] Warning Threshold...
Page 245 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. Click Submit. Version 6.8 Mediant 500 E-SBC...
Page 246 Mediant 500 E-SBC Table 16-4: Media Enhancement Profile Table Parameter Descriptions Parameter Description Index Defines the index of the table row entry. [MediaEnhancementProfile_Index] Name Defines an arbitrary name to easily identify the Media CLI: profile-name Enhancement Profile. [MediaEnhancementProfile_ProfileName] The valid value is a string of up to 20 characters.
Page 247 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 500 E-SBC...
Page 248 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 249: 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 500 E-SBC...
Page 250 Mediant 500 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 251: Configuring Remote Media Subnets
''Configuring Bandwidth Profiles'' on page 242, respectively. Thus, you can apply these profiles to remote media subnets instead of Media Realms or IP Groups. You can configure up to five Remote Media Subnets per Media Realm. Version 6.8 Mediant 500 E-SBC...
Page 252 Mediant 500 E-SBC The figure below illustrates an example for implementing Remote Media Subnets. IP Group #2 represents a SIP Trunk which routes international (USA and India) and local calls. As international calls are typically more prone to higher delay than local calls, different Quality of Experience Profiles are assigned to them.
Page 253 The default is 0.0.0.0. [RemoteMediaSubnet_DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the CLI: qoe-profile Remote Media Subnet. [RemoteMediaSubnet_QOEProfileName] BW Profile Name Assigns a Bandwidth Profile to the Remote CLI: bw-profile Media Subnet. [RemoteMediaSubnet_BWProfileName] Version 6.8 Mediant 500 E-SBC...
Page 254: Configuring Srds
Mediant 500 E-SBC 17.3 Configuring SRDs The SRD table lets you configure up to 32 signaling routing domains (SRD). An SRD represents a logical VoIP network. Each logical or physical connection requires an SRD. For example, if the device interfaces with both the LAN and WAN, you need to configure an SRD for each one.
Page 255 SRD, calls cannot be established if the following scenario exists: One of the endpoints is defined as a foreign user (for example, “follow me service”) and one endpoint is located on the WAN and the other on the LAN. Version 6.8 Mediant 500 E-SBC...
Page 256: Configuring Sip Interfaces
Mediant 500 E-SBC Parameter Description The reason for this is that in Media Anchoring, the device does not interfere in the SIP signaling such as manipulation of IP addresses, which is necessary for calls between LAN and WAN.  When the global parameter SBCDirectMedia is disabled, Media Anchoring can only be enabled for calls between endpoints belonging to the same SRD.
Page 257  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 500 E-SBC...
Page 258 Mediant 500 E-SBC Parameter Description TCP Port Defines the listening TCP port. CLI: tcp-port The valid range is 1 to 65534. The default is 5060. [SIPInterface_TCPPort] Notes:  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).
Page 259 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 500 E-SBC...
Page 260: Configuring Ip Groups
Mediant 500 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 261 [1] User = Represents a group of users such as IP phones and softphones where their location is dynamically obtained by the device when REGISTER requests and responses traverse (or are terminated) by the device. These users are considered remote (far- Version 6.8 Mediant 500 E-SBC...
Page 262 Mediant 500 E-SBC Parameter Description end) users. Typically, this IP Group is configured with a Serving IP Group that represents an IP-PBX, Application or Proxy server that serves this User-type IP Group. Each SIP request sent by a user of this IP Group is proxied to the Serving IP Group.
Page 263 Group, and the Contact header in SIP 18x and 200 OK responses for incoming INVITE messages received from a specific IP Group. The Inbound IP Routing table can be used to identify the source IP Group Version 6.8 Mediant 500 E-SBC...
Page 264 Mediant 500 E-SBC Parameter Description from where the INVITE message was received. If this parameter is not configured (default), these headers are populated with the device's dotted-decimal IP address of the network interface on which the message is sent. Note: To ensure proper device handling, this parameter should be a valid FQDN.
Page 265 Survivability mode is enabled for User-type IP Groups. [IPGroup_EnableSurvivabilit  [0] Disable (default).  [1] Enable if Necessary = Survivability mode is enabled only if the Serving IP Group is unavailable. The device saves in its Version 6.8 Mediant 500 E-SBC...
Page 266 Mediant 500 E-SBC Parameter Description Registration database the registration messages sent by the clients (e.g., IP phones) belonging to the User-type IP Group. If communication with the Serving IP Group (e.g., IP-PBX) fails, the User-type IP Group enters into Survivability mode in which the device uses its database for routing calls between the clients of the User-type IP Group.
Page 267 Authenticates SIP severs. This is applicable only to Server- type IP Groups. Authentication Method List Defines SIP methods received from the IP Group that must be CLI: authentication-method- challenged by the device, when the device acts as an Authentication Version 6.8 Mediant 500 E-SBC...
Page 268 Mediant 500 E-SBC Parameter Description list server. If this parameter is not defined (i.e., empty value), no methods [IPGroup_MethodList] are challenged. The default value is null. Multiple entries are separated by a backslash "\", for example, INVITE\REGISTER. Note: This parameter is applicable only if the 'Authentication Mode' parameter is set to SBC as Server [2].
Page 269 To specify the SIP request types (e.g., INVITE) that must be challenged by the device, use the 'Authentication Method List' parameter. Password Defines the shared password for authenticating the IP Group, when CLI: password the device acts as an Authentication server. Version 6.8 Mediant 500 E-SBC...
Page 270: Configuring Proxy Sets
Mediant 500 E-SBC Parameter Description IPGroup_Password] The valid value is a string of up to 51 characters. By default, no password is defined. Notes:  This parameter is applicable only to Server-type IP Groups and when the 'Authentication Mode' parameter is set to SBC as Server (i.e., authentication of servers).
Page 271 Defines the transport type for communicating with the Proxy server. 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 Version 6.8 Mediant 500 E-SBC...
Page 272 Mediant 500 E-SBC Parameter Description parameter SIPTransportType is used. 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 273 Web/EMS: Is Proxy Hot Swap Enables the Proxy Hot-Swap redundancy mechanism, which CLI: voip-network proxy-set > provides real-time switching from the primary Proxy server to is-proxy-hot-swap redundant Proxies when no response is received from the primary. Version 6.8 Mediant 500 E-SBC...
Page 274 Mediant 500 E-SBC Parameter Description  [ProxySet_IsProxyHotSwap] [0] No (default)  [1] Yes = The device sends the SIP INVITE/REGISTER message to the first address (Proxy/Registrar server) listed in the Proxy Set. If a SIP response is received and this response code is...
Page 275 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 89. Version 6.8 Mediant 500 E-SBC...
Page 276 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 277: Sip Definitions
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 500 E-SBC...
Page 278 Mediant 500 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 279 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 500 E-SBC...
Page 280: Regular Registration Mode
Mediant 500 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 281: Configuring Proxy And Registration Parameters
For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 673. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Endpoint Registration Status on page 608. Version 6.8 Mediant 500 E-SBC...
Page 282: Sip Message Authentication Example
Mediant 500 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 283 • 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 284: Configuring Sip Message Manipulation
Mediant 500 E-SBC Final stage: • A1 result: The nonce from the proxy response is "11432d6bce58ddf02e3b5e1c77c010d2". • A2 result: The equation to be evaluated is "A1:11432d6bce58ddf02e3b5e1c77c010d2:A2". • The MD5 algorithm is run on this equation. The outcome of the calculation is the response needed by the device to register with the Proxy.
Page 285 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  Multiple manipulation rules on the same SIP message Version 6.8 Mediant 500 E-SBC...
Page 286 Mediant 500 E-SBC The figure below illustrates a SIP message manipulation example: Figure 18-1: SIP Header Manipulation Example Notes: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide.
Page 287 Defines an index number for the new table record. [MessageManipulations_Ind Note: Each rule must be configured with a unique index. Manipulation Name Defines an arbitrary name to easily identify the Message CLI: manipulation-name Manipulation rule. Version 6.8 Mediant 500 E-SBC...
Page 288 Mediant 500 E-SBC Parameter Description [MessageManipulations_Ma The valid value is a string of up to 16 characters. nipulationName] Manipulation Set ID Defines a Manipulation Set ID for the rule. You can define the same CLI: manipulation-set-id Manipulation Set ID for multiple rules to create a group of rules. The...
Page 289: Configuring Sip Message Policy Rules
Maximum number of headers  Maximum number of bodies  Option to send 400 "Bad Request" response if message request is rejected  Blacklist and whitelist for defined methods (e.g., INVITE)  Blacklist and whitelist for defined bodies Version 6.8 Mediant 500 E-SBC...
Page 290 Mediant 500 E-SBC The following procedure describes how to configure Message Policy rules in the Web interface. You can also configure Message Policy rules using the table ini file parameter, MessagePolicy or the CLI command, configure voip > sbc message-policy.
Page 291 '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 500 E-SBC...
Page 292 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 293: Coders And Profiles
You can also configure this table using the table ini file parameter, CodersGroup0 or CLI command, configure voip > coders-and-profiles coders-group.  To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Version 6.8 Mediant 500 E-SBC...
Page 294 Mediant 500 E-SBC Configure coders according to the parameters described in the table below. 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.
Page 295 127);  [1] Enable Default 65 30 (default), 60, 90, 120 silk-nb 20 (default), 40, 60, 80, Dynamic; [Silk-8Khz] and 100 Default 76 silk-wb 20 (default), 40, 60, 80, Dynamic; [Silk-16Khz] and 100 Default 77 Version 6.8 Mediant 500 E-SBC...
Page 296: Configuring Coder Groups
Mediant 500 E-SBC Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression T.38 [t38fax] T.38 Version 3 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 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).
Page 297: Configuring Tel Profile
Trunk Group table (see Configuring Trunk Group Table on page 347)). 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 500 E-SBC...
Page 298 Mediant 500 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 299 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 500 E-SBC...
Page 300: Configuring Ip Profiles
Mediant 500 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] 19.4 Configuring IP Profiles The IP Profile Settings table lets you configure up to 20 IP Profiles. An IP Profile is a set of parameters with user-defined settings relating to signaling (e.g., SIP message terminations...
Page 301 If the coder lists of both an IP Profile and a Tel Profile apply to the same call, only the coders common to both are used. The order of the coders is determined by the preference.  This parameter is applicable only to the Gateway application. Version 6.8 Mediant 500 E-SBC...
Page 302 Mediant 500 E-SBC Parameter Description Web: Dynamic Jitter Buffer Minimum Defines the minimum delay (in msec) of the device's Delay dynamic Jitter Buffer. CLI: jitter-buffer-minimum-delay The valid range is 0 to 150. The default delay is 10. [IpProfile_JitterBufMinDelay] Notes: ...
Page 303 The valid range is -32 to 31 dB. The default is 0 dB. Note: The corresponding global parameter is InputGain. Web: Voice Volume Defines the voice gain control (in decibels). This defines the CLI: voice-volume level of the transmitted signal for IP-to-Tel calls. Version 6.8 Mediant 500 E-SBC...
Page 304 Mediant 500 E-SBC Parameter Description [IpProfile_VoiceVolume] The valid range is -32 to 31 dB. The default is 0 dB. Note: The corresponding global parameter is VoiceVolume. Web: Media IP Version Preference Defines the preferred RTP media IP addressing version for CLI: media-ip-version-preference outgoing SIP calls.
Page 305 Coders table (see Configuring Coders on page 293). All other optional values (e.g., Coders Group 1), represent the coders defined for the specific Coder Group configured in the Coder Group Settings table (see Version 6.8 Mediant 500 E-SBC...
Page 306 Mediant 500 E-SBC Parameter Description Configuring Coder Groups on page 296). Web: Fax Signaling Method Defines the SIP signaling method for establishing and CLI: fax-sig-method transmitting a fax session when the device detects a fax. [IpProfile_IsFaxUsed]  [0] No Fax = (Default) No fax negotiation using SIP signaling.
Page 307 In NSE bypass mode, the device starts using G.711 A-Law (default) or G.711 -Law, according to the FaxModemBypassCoderType parameter. The payload type for these G.711 coders is a standard one (8 for G.711 A-Law and 0 for G.711 -Law). The parameters defining payload Version 6.8 Mediant 500 E-SBC...
Page 308 Mediant 500 E-SBC Parameter Description type for the 'old' Bypass mode FaxBypassPayloadType and ModemBypassPayloadType are not used with NSE Bypass. The bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval parameter. The SDP contains the following line: 'a=rtpmap:100 X-NSE/8000'. Notes: ...
Page 309 SIP Diversion or History header in the incoming INVITE message, the outgoing Q.931 Setup message will contain a redirect number.  [0] Disable (default).  [1] After Manipulation = Copies the called number after Version 6.8 Mediant 500 E-SBC...
Page 310 Mediant 500 E-SBC Parameter Description manipulation. The device first performs IP-to-Tel destination phone number manipulation, and only then copies the manipulated called number to the redirect number sent in the Q.931 Setup message to the Tel. Thus, the called and redirect numbers are the same.
Page 311 IP network as DTMF signals, according to the settings of this parameter.  The corresponding global parameter is TxDTMFOption. Web: Second Tx DTMF Option Defines the second preferred transmit DTMF negotiation CLI: second-tx-dtmf-option method. For a description, see IpProfile_FirstTxDtmfOption [IpProfile_SecondTxDtmfOption] (above). Version 6.8 Mediant 500 E-SBC...
Page 312 Mediant 500 E-SBC Parameter Description Note: The corresponding global parameter is TxDTMFOption Web: Rx DTMF Option Enables the device to declare the RFC 2833 'telephony- CLI: rx-dtmf-option event' parameter in the SDP. [IpProfile_RxDTMFOption]  [0] Not Supported  [3] Supported (default) The device is always receptive to RFC 2833 DTMF relay packets.
Page 313 The valid range is 0 to 2400. The default is 0 (i.e., disabled). Note: The corresponding global parameter is EarlyAnswerTimeout. Allowed Media Types Defines media types permitted for this SIP entity. The media CLI: sbc-allowed-media-types type appears in the SDP 'm=' line (e.g., 'm=audio'). The Version 6.8 Mediant 500 E-SBC...
Page 314 Mediant 500 E-SBC Parameter Description [IPProfile_SBCAllowedMediaTypes] device permits only media types that appear in both the SDP offer and this configured list. If no common media types exist between the SDP offer and this list, the device drops the call.
Page 315 SIP entity. This header indicates how the [IpProfile_SBCAssertIdentity] outgoing SIP message asserts identity.  [0] As Is = (Default) P-Asserted Identity header is not affected and the device uses the same P-Asserted- Version 6.8 Mediant 500 E-SBC...
Page 316 Mediant 500 E-SBC Parameter Description Identity header (if present) in the incoming message for the outgoing message.  [1] Add = Adds a P-Asserted-Identity header. The header's values are taken from the source URL.  [2] Remove = Removes the P-Asserted-Identity header.
Page 317 INVITE is sent through the SBC: Before forwarding the REFER request, the device changes the host part to the device's IP address and adds a special prefix ("T~&R_") to the Contact user part. Version 6.8 Mediant 500 E-SBC...
Page 318 Mediant 500 E-SBC Parameter Description The incoming INVITE is identified as a REFER- resultant INVITE according to this special prefix. The device replaces the host part in the Request-URI with the host from the REFER contact. The special prefix remains in the user part for regular classification, manipulation, and routing.
Page 319 [1] Delayed = After sending 18x response, the remote client waits before sending RTP (e.g., Microsoft Lync environment). For the device's handling of this remote UA support, see Interworking SIP Early Media on page 453. Version 6.8 Mediant 500 E-SBC...
Page 320 Mediant 500 E-SBC Parameter Description Web: Remote RFC 3960 Gateway Defines whether the destination UA is capable of receiving Model Support 18x messages with delayed RTP. CLI: sbc-rmt-rfc3960-supp  [0] Not Supported = (Default) UA does not support receipt [IpProfile_SBCRemoteSupportsRFC3 of 18x messages with delayed RTP.
Page 321 Web: SDP Ptime Answer Defines the packetization time (ptime) of the coder in RTP CLI: sbc-sdp-ptime-ans packets for this SIP entity. This is useful when implementing [IpProfile_SBCSDPPtimeAnswer] transrating.  [0] Remote Answer (Default) = Use ptime according to Version 6.8 Mediant 500 E-SBC...
Page 322 Mediant 500 E-SBC Parameter Description SDP answer.  [1] Original Offer = Use ptime according to SDP offer.  [2] Preferred Value= Use preferred ptime for negotiation, if configured by the 'Preferred Ptime' parameter. Web: Preferred Ptime Defines the packetization time (in msec) for this SIP entity if...
Page 323 Minimum Delay' (DJBufMinDelay) and 'Dynamic Jitter Buffer Optimization Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed.  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. Version 6.8 Mediant 500 E-SBC...
Page 324 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 325: Gateway Application
Part V Gateway Application...
Page 327: Introduction
IP-to-Tel refers to calls received from the IP network and destined to the PSTN/PBX (i.e., telephone connected directly or indirectly to the device); Tel-to-IP refers to calls received from the PSTN/PBX, and destined for the IP network. Version 6.8 Mediant 500 E-SBC...
Page 328 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 329: Digital Pstn
E1 Euro ISDN and E1 CAS (subject to the constraints in the device's Release Notes). • 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. Version 6.8 Mediant 500 E-SBC...
Page 330 Mediant 500 E-SBC  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: •...
Page 331: Tdm And Timing
For a description of these parameters, see ''PSTN Parameters'' on page 795.  To configure the TDM Bus settings: Open the TDM page (Configuration tab > VoIP menu > TDM > TDM Bus Settings). Figure 21-2: TDM Bus Settings Page Version 6.8 Mediant 500 E-SBC...
Page 332: Clock Settings
Mediant 500 E-SBC Configure the parameters as required. Click Submit. Save the changes to flash memory, see ''Saving Configuration'' on page 530. 21.2.2 Clock Settings In a traditional TDM service network such as PSTN, both ends of the TDM connection must be synchronized.
Page 333: Configuring Internal Clock As Clock Source
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 527). Version 6.8 Mediant 500 E-SBC...
Page 334 Mediant 500 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 335 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 500 E-SBC...
Page 336: Configuring Digital Gateway Parameters
Mediant 500 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 673.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...
Page 337: Tunneling Applications
‘Transparent’ coder to transport data (e.g., for D-channel). You can also use Profiles to assign ToS (for DiffServ) per source - a timeslot carrying data or signaling is assigned a higher priority value than a timeslot carrying voice. Version 6.8 Mediant 500 E-SBC...
Page 338 Mediant 500 E-SBC For tunneling CAS trunks, set the protocol type to 'Raw CAS' (ProtocolType = 3 / 9) and enable RFC 2833 CAS relay mode ('CAS Transport Type' parameter is set to 'CAS RFC2833 Relay'). Note: For TDM over IP, the parameter CallerIDTransportType must be set to '0' (disabled), i.e., transparent.
Page 339 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, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ Version 6.8 Mediant 500 E-SBC...
Page 340: Dsp Pattern Detector
Mediant 500 E-SBC 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 341: Isdn Non-Facility Associated Signaling (Nfas)
Trunk". The T1 trunk whose D-channel is used for backup signaling is called the "Backup NFAS Trunk". The primary and backup trunks each carry 23 B-channels while all other NFAS trunks each carry 24 B-channels. Version 6.8 Mediant 500 E-SBC...
Page 342: Nfas Interface Id
Mediant 500 E-SBC The NFAS group is identified by an NFAS GroupID number (possible values are 1 to 12). To assign a number of T1 trunks to the same NFAS group, use the NFASGroupNumber_x = groupID (where x is the physical trunk ID (0 to the maximum number of trunks) or the Web interface (see ''Configuring Trunk Settings'' on page 329).
Page 343: Creating An Nfas-Related Trunk Configuration
• All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure Version 6.8 Mediant 500 E-SBC...
Page 344: Performing Manual D-Channel Switchover In Nfas Group
Mediant 500 E-SBC 21.6.4 Performing Manual D-Channel Switchover in NFAS Group If an NFAS group is configured with two D-channels (Primary and Backup), you can do a manual switchover between these D-channels.  To manually switchover from active to standby D-channel: Open the NFAS Group &...
Page 345: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578
ISDNRxOverlap = 2  ISDNTxOverlap  ISDNOutCallsBehavior = 2  MinOverlapDigitsForRouting  TimeBetweenDigits  MaxDigits  DigitMapping  MuteDTMFInOverlap For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 329. Version 6.8 Mediant 500 E-SBC...
Page 346: Redirect Number And Calling Name (Display)
Mediant 500 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: Table 21-2: Calling Name (Display)
Page 347: Trunk Group
''Configuring Hunt Group Settings'' on page 349).  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 500 E-SBC...
Page 348 Mediant 500 E-SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the module (i.e., PRI) for which you want to define the CLI: module Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group.
Page 349: Configuring Trunk Group Settings
Click Submit, and then save ("burn") your settings to flash memory. Table 22-2: Trunk Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_TrunkGr Version 6.8 Mediant 500 E-SBC...
Page 350 Mediant 500 E-SBC Parameter Description oupId] Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the CLI: channel-select-mode channels of the Trunk Group. [TrunkGroupSettings_Channel  [0] By Dest Phone Number = The channel is selected SelectMode] according to the called (destination) number.
Page 351 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 260). Notes:  If this parameter is not configured, the registration is Version 6.8 Mediant 500 E-SBC...
Page 352 Mediant 500 E-SBC Parameter Description 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.  If the device is configured globally to register Per Endpoint and...
Page 353 The SIP NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. Note: This parameter appears in the table only if the VoiceMailInterface parameter is set to 3 (QSIG). Configuring Voice Mail on page 432. Version 6.8 Mediant 500 E-SBC...
Page 354 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 355: Manipulation
559. However, if you enter 55 in Index 1 and 551 in Index 2, the device applies rule 1 to all numbers that start with 55, including numbers that start with 551. Version 6.8 Mediant 500 E-SBC...
Page 356 Mediant 500 E-SBC 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. The additional manipulation is performed on the initially manipulated number.
Page 357 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix 1001 123451001# [30-40]x 2001 Source Prefix Stripped Digits from Left Stripped Digits from Right Version 6.8 Mediant 500 E-SBC...
Page 358 Mediant 500 E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Prefix to Add 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 359 Defines the number or string that you want added to the front of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 9 and the phone number CLI: prefix-to-add is 1234, the new number is 91234. [Prefix2Add] Version 6.8 Mediant 500 E-SBC...
Page 360 Mediant 500 E-SBC Parameter Description 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 CLI: suffix-to-add is 1234, the new number is 123400.
Page 361: Manipulating Number Prefix
In this configuration example, the following manipulation process occurs: 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 500 E-SBC...
Page 362: Sip Calling Name Manipulations
Mediant 500 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 363 100, 101 or 105. You can also use the $ sign to denote calls without a calling number. For a description of available notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 671. Version 6.8 Mediant 500 E-SBC...
Page 364 Mediant 500 E-SBC Parameter Description 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. 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.
Page 365: Configuring Redirect Number Ip To Tel
Matching characteristics (Rule) of incoming call, for example, prefix of redirect number.  Manipulation operation (Action), for example, remove user-defined number of digits from the left of the redirect number. If the incoming call matches the characteristics of a rule, its manipulation action is applied. Version 6.8 Mediant 500 E-SBC...
Page 366 Mediant 500 E-SBC Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
Page 367 P- Asserted-Identity URI host name (instead of to the From header). Web: Destination Host Prefix Defines the Request-URI host name prefix, which appears in the Version 6.8 Mediant 500 E-SBC...
Page 368 Mediant 500 E-SBC Parameter Description CLI: dst-host-prefix incoming SIP INVITE message. [_DestHost] The default value is the asterisk (*) symbol (i.e., any prefix). Note: This parameter is applicable only to the Redirect Number IP-to- Tel table. Operation (Action) Web: Stripped Digits From...
Page 369: Manipulating Redirected And Diverted Numbers For Call Diversion
Suffix to Add Number of Digits to Leave After the above manipulation is done, the device sends the following outgoing SIP 302 response: SIP/2.0 302 Moved Temporarily Via: SIP/2.0/TLS 10.33.45.68;branch=z9hG4bKac54132643;alias From: "MP118 1" <sip:8001@10.33.45.68>;tag=1c54119560 To: <sip:6001@10.33.45.69;user=phone>;tag=1c664560944 Version 6.8 Mediant 500 E-SBC...
Page 370: Mapping Npi/Ton To Sip Phone-Context
Mediant 500 E-SBC Call-ID: 541189832710201115142@10.33.45.68 CSeq: 1 INVITE Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.20A.043.001 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 23.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
Page 371: Configuring Release Cause Mapping
If the SIP response is found, the Q.850 Release Cause assigned to it is sent to the PSTN. If no match is found, the default static mapping is used.  Release Cause Mapping from ISDN to SIP table: Maps ISDN cause codes to SIP Version 6.8 Mediant 500 E-SBC...
Page 372 Mediant 500 E-SBC release codes. When a Release Cause is received from the PSTN, the device searches this table for a match. If the Q.850 Release Cause is found, the SIP response assigned to it is sent to the IP side. If no match is found, the default static mapping is used.
Page 373: Fixed Mapping Of Sip Response To Isdn Release Reason
Not acceptable here Normal, unspecified Server internal error Temporary failure Not implemented Network out of order Bad gateway Network out of order Service unavailable Temporary failure Server timeout Recovery on timer expiry 505* Version not supported Interworking Version 6.8 Mediant 500 E-SBC...
Page 374: Fixed Mapping Of Isdn Release Reason To Sip Response
Mediant 500 E-SBC ISDN Release SIP Response Description Description Reason Busy everywhere User busy Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does not specify their cause code mapping.
Page 375 Temporarily not available implemented Message not compatible with call state or message type non-existent or not 409* Conflict implemented Information element non-existent or not 480* Not found implemented Invalid information elements contents 501* Not implemented Version 6.8 Mediant 500 E-SBC...
Page 376 Mediant 500 E-SBC ISDN Release Description Description Reason Response Message not compatible with call state 503* Service unavailable Recovery of timer expiry Request timeout Protocol error Server internal error Interworking unspecified Server internal error * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft doesn’t specify their cause code mapping.
Page 377: Reason Header
If the message isn’t a final response, it is translated to a Q.850 cause. • When the Reason header is received twice (i.e., SIP Reason and Q.850), the Q.850 takes precedence over the SIP reason and is sent to the Tel side. Version 6.8 Mediant 500 E-SBC...
Page 378: Numbering Plans And Type Of Number
Mediant 500 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 379: Routing
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 Version 6.8 Mediant 500 E-SBC...
Page 380 Mediant 500 E-SBC • Source and destination Request-URI host name prefix  Destination: If the call matches the configured characteristics, the device routes the call to an IP destination. If no characteristics match is found in the table, the call is rejected.
Page 381 FQDN to resolve into two IP addresses. For more information on alternative routing, see ''Alternative Routing for Tel-to-IP Calls'' on page 394.  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine Version 6.8 Mediant 500 E-SBC...
Page 382 Mediant 500 E-SBC 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. Note: You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table.
Page 383 [1] Route calls after manipulation = Calls are routed after the number manipulation rules are applied. Notes:  This parameter is not applicable if outbound proxy routing is used.  For number manipulation, see ''Configuring Source/Destination Version 6.8 Mediant 500 E-SBC...
Page 384 Mediant 500 E-SBC Parameter Description Number Manipulation'' on page 355. Route Name Defines an arbitrary name to easily identify the routing rule. CLI: route-name The valid value is a string of up to 20 characters. By default, no [PREFIX_RouteName] value is defined.
Page 385 To reject calls, enter the IP address 0.0.0.0. For example, if you want to prohibit international calls, then in the '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., Version 6.8 Mediant 500 E-SBC...
Page 386 Mediant 500 E-SBC Parameter Description local routing), enter the device's IP address.  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 126).
Page 387 1, 3, and 4 (all belonging to Forking Group "1"), and if the destination is unavailable and alternative routing is enabled, the device sends the call according to index entry 2.  Table index entry 1 is defined with Forking Group "1", index Version 6.8 Mediant 500 E-SBC...
Page 388: Configuring Inbound Ip Routing Table
Mediant 500 E-SBC Parameter Description entry 2 with Forking Group "3", index entry 3 with Forking Group "2", and index entry 4 with Forking Group "1": The device first sends the call according to index entries 1 and 4 (all belonging to Forking Group "1"), and if the destination is...
Page 389 Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing). Figure 24-3: Inbound IP Routing Table The previous figure displays the following configured routing rules: Version 6.8 Mediant 500 E-SBC...
Page 390: Route Name
Mediant 500 E-SBC • Rule 1: If the incoming IP call destination phone prefix is between 10 and 19, the call is assigned settings configured for IP Profile ID 2 and routed to Trunk Group ID 1. • Rule 2: If the incoming IP call destination phone prefix is between 501 and 502 and source phone prefix is 101, the call is assigned settings configured for IP Profile ID 1 and routed to Trunk Group ID 2.
Page 391 Operation (Destination) Web: Trunk Group ID For IP-to-Tel calls: Defines the Trunk Group to where the CLI: trunk-group-id incoming SIP call is sent. [PstnPrefix_TrunkGroupId] For IP-to-IP calls: Identifies the call as an IP-to-IP call if this Version 6.8 Mediant 500 E-SBC...
Page 392: Ip Destinations Connectivity Feature
Mediant 500 E-SBC Parameter Description parameter is set to -1. Web: Trunk ID Defines the Trunk to where the incoming SIP call is sent. CLI: trunk-id Notes: [PstnPrefix_TrunkId]  If both 'Trunk Group ID' and 'Trunk ID' parameters are configured in the table, the routing is done according to the 'Trunk Group ID' parameter.
Page 393 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 610. Version 6.8 Mediant 500 E-SBC...
Page 394: Alternative Routing For Tel-To-Ip Calls
Mediant 500 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 395: Alternative Routing Based On Sip Responses
Tel-to-IP routing rules, see ''Configuring Outbound IP Routing Table'' on page 379. The table below shows an example of alternative routing where the device uses the first available alternative routing rule to re-route the initial, unsuccessful Tel-to-IP call destination: Version 6.8 Mediant 500 E-SBC...
Page 396 Mediant 500 E-SBC Table 24-5: Alternative Routing based on SIP Response Code Example Destination IP Destination SIP Response Rule Used? Phone Prefix 408 Request Main Route 10.33.45.68 Timeout Alternative Route #1 10.33.45.70 486 Busy Here Alternative Route #2 10.33.45.72 200 OK ...
Page 397: Alternative Routing Upon Sip 3Xx With Multiple Contacts
If a contact responds with a SIP 486 or 600, the device does not try to redirect the call to the next contact and drops the call.  The device tries each contact sequentially, listed in the Contact headers. If a SIP 6xx Version 6.8 Mediant 500 E-SBC...
Page 398: Pstn Fallback
Mediant 500 E-SBC Global Failure response is received during this process (e.g., 600 Busy Everywhere), the device does not try to redirect the call to the next contact and drops the call.  The device redirects the call to the first contact listed in the Contact header. If the...
Page 399: Alternative Routing For Ip-To-Tel Calls
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. In the Inbound IP Routing table, configure alternative routing rules with the same call Version 6.8 Mediant 500 E-SBC...
Page 400: Alternative Routing To An Ip Destination Upon A Busy Trunk
Mediant 500 E-SBC matching characteristics, but with different Trunk Group destinations. Configure Q.931 cause codes that invoke alternative IP-to-Tel routing: Open the Reasons for IP-to-Tel Alternative Routing page (Configuration tab > VoIP menu > GW and IP to IP > Routing > Alternative Routing Reasons >...
Page 401 FQDN, or a SIP Request-URI user name and host part (i.e., user@host). The following syntax can also be used: host:port;transport=xxx (i.e., IP address, port and transport type). Note: When configured with a user@host, the original destination number is replaced by the user part. Version 6.8 Mediant 500 E-SBC...
Page 402: Alternative Routing Upon Isdn Disconnect
Mediant 500 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 403: Configuring Dtmf And Dialing
(or a digit map pattern is matched), the device uses these digits for the called destination number.  Inter-digit timeout expires (e.g., for open numbering schemes). This is defined using the TimeBetweenDigits parameter. This is the time that the device waits between each Version 6.8 Mediant 500 E-SBC...
Page 404 Mediant 500 E-SBC received digit. When this inter-digit timeout expires, the device uses the collected digits to dial the called destination number.  Digit string (i.e., dialed number) matches one of the patterns defined in the digit map. Digit map (pattern) rules are defined using the DigitMapping parameter. The digit map pattern can contain up to 52 options (rules), each separated by a vertical bar ("|").
Page 405: External Dial Plan File
User's Manual 25. Configuring DTMF and Dialing 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 542. Version 6.8 Mediant 500 E-SBC...
Page 406 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 407: Configuring Supplementary Services
''Configuration Parameters Reference'' on page 673.  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). Version 6.8 Mediant 500 E-SBC...
Page 408: Call Hold And Retrieve
Mediant 500 E-SBC Configure the parameters as required. Click Submit, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server. To save the changes to flash memory, see ''Saving Configuration'' on page 530.
Page 409: Consultation Transfer For Qsig Path Replacement
IP-to-Tel call: destination number of the original call. • If the UseReferredByForCallingNumber parameter is set to 1, the source number is taken from the SIP Referred-By header if included in the received SIP REFER message. Version 6.8 Mediant 500 E-SBC...
Page 410: Call Forward
Mediant 500 E-SBC This source number can also be used as the value for the 'Source Prefix' field in the IP-to-Tel Destination Phone Number Manipulation table. The local IP address is used as the value for the 'Source IP Address' field.
Page 411: Emergency E911 Phone Number Services
The E911 emergency system automatically associates a physical address with the calling party's telephone number, and routes the call to the most appropriate (closest) Public Safety Answering Point (PSAP), allowing the PSAP to quickly dispatch emergency response (e.g., police) to the caller's location. Version 6.8 Mediant 500 E-SBC...
Page 412: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls
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 413: About E9-1-1 Services
ALI databases. The E9-1-1 Selective Router sends the call to the appropriate PSAP based on the retrieved location information from the ALI. The PSAP operator dispatches the relevant emergency services to the E9-1-1 caller. Version 6.8 Mediant 500 E-SBC...
Page 414: Microsoft Lync Server 2010 And E9-1-1
Mediant 500 E-SBC 26.5.2.2 Microsoft Lync Server 2010 and E9-1-1 Microsoft Lync Server 2010 enables Enterprise voice users to access its unified communications platform from virtually anywhere and through many different devices. This, together with a deployed MLTS, poses a challenge for E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller.
Page 415 As mentioned in the previous section, the Administrator needs to populate the Location Information Server (LIS) database with a network wire map, which maps the Enterprise's network elements to civic addresses. Once done, it can automatically locate clients within Version 6.8 Mediant 500 E-SBC...
Page 416 Mediant 500 E-SBC a network. You can add addresses individually to the LIS or in a batch using a comma- separated value (CSV) file containing the column formats listed in the table below. Table 26-1: Columns in the LIS Database...
Page 417: Audiocodes Elin Gateway For Lync Server 2010 E9-1-1 Calls To Pstn
ELIN when dialing 9-1-1. 26.5.2.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN The Microsoft Mediation Server sends the location information of the E9-1-1 caller in the XML-based PIDF-LO body contained in the SIP INVITE message.
Page 418 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 419 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 420 Mediant 500 E-SBC a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=ptime:20 ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/pidf+xml Content-ID: <voip_911_user1@contoso.com> <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:bp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ms="urn:schema:Rtc.LIS.msftE911PidfExtn.2008" entity="sip:voip_911_user1@contoso.com"><tuple id="0"><status><gp:geopriv><gp:location- info><ca:civicAddress><ca:country>US</ca:country><ca:A1>WA</ca:A1> <ca:A3>Redmond</ca:A3><ca:RD>163rd</ca:RD><ca:STS>Ave</ca:STS><ca: POD>NE</ca:POD><ca:HNO>3910</ca:HNO><ca:LOC>40/4451</ca:LOC> <ca:NAM>1111-222-333; 1234567890 </ca:NAM> <ca:PC>98052</ca:PC></ca:civicAddress></gp:location- info><gp:usage-rules><bp:retransmission- allowed>true</bp:retransmission-allowed></gp:usage- rules></gp:geopriv><ms:msftE911PidfExtn><ms:ConferenceUri>sip:+142...
Page 421: Sip Invite Message
If all the ELINs in the list are in use by active calls, the ELIN Gateway selects the ELIN number as follows: The ELIN with the lowest count (i.e., lowest number of active calls currently using this ELIN). Version 6.8 Mediant 500 E-SBC...
Page 422: Configuring Audiocodes Elin Gateway
26.5.2.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.5.2.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 423 Emergency calls received from Manchester office users are routed by the device to the Manchester police department, which is +44161999. The international code, +44 for England is used for IP routing considerations, but can be omitted depending on your specific network environment. Version 6.8 Mediant 500 E-SBC...
Page 424: Multilevel Precedence And Preemption
Mediant 500 E-SBC The above example scenario is configured as follows: Enable location-based emergency routing, by loading an ini file to the device with the following parameter setting: E911Gateway = 2 In the Destination Phone Number Manipulation Table for IP-to-Tel Calls (Configuration tab >...
Page 425 Department of Defense (DoD) Unified Capabilities (UC) Requirements (UCR 2008, Changes 3) document, as shown below: Table 26-5: NI Digits in ISDN Precedence Level IE Network Domain in SIP Resource-Priority Header 0000 0001 Version 6.8 Mediant 500 E-SBC...
Page 426 Mediant 500 E-SBC Level IE Network Domain in SIP Resource-Priority Header 0002 0003 nato Notes: • If the received ISDN message contains NI digits that are not listed in the translation table, the device sets the network-domain to "uc" in the outgoing SIP message.
Page 427: Mlpp Preemption Events In Sip Reason Header
B-channel is not reserved for reuse. The device sends a SIP 200 OK in response to the received BYE, before the SIP end instrument can proceed with the higher precedence call. Version 6.8 Mediant 500 E-SBC...
Page 428: Precedence Ring Tone
Mediant 500 E-SBC • The softswitch performs a network preemption of an outbound call request for the device that has not received a SIP 2xx response - the following sequence of events occur: The softswitch sends the device a SIP 488 (Not Acceptable Here) response code with this Reason cause code.
Page 429: 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 430: Configuring Charge Codes
Mediant 500 E-SBC recommended to use an NTP server to obtain the date and time. 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 >...
Page 431 (00). This prevents undefined time frames in a day. Pulse Interval Defines the time interval between pulses (in tenths of a CLI: pulse-interval-<1-4> second). [ChargeCode_PulseInterval<1-4>] Pulses On Answer Defines the number of pulses sent on answer. CLI: pulses-on-answer-<1-4> [ChargeCode_PulsesOnAnswer<1- 4>] Version 6.8 Mediant 500 E-SBC...
Page 432: Configuring Voice Mail
Mediant 500 E-SBC 26.10 Configuring Voice Mail The Voice Mail Settings page allows you to configure the voice mail parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 673. Notes: • The Voice Mail Settings page is available only for CAS interfaces.
Page 433: Session Border Controller Application
Part VI Session Border Controller Application...
Page 435: Sbc Overview
Each leg has its own Route/Record Route set. • 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). Version 6.8 Mediant 500 E-SBC...
Page 436: Sip Network Definitions
Mediant 500 E-SBC • Changes the SIP Contact header to the device's own address. • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents. This is achieved by the following: •...
Page 437 ''SBC Manipulations'' on page 487. 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 284. Version 6.8 Mediant 500 E-SBC...
Page 438: User Registration
Mediant 500 E-SBC The flowchart below illustrates the SBC process: Figure 27-1: Routing Process 27.3 User Registration To allow registrations to traverse the SBC, the device must be configured with at least one User-type IP Group. These IP Groups represent a group of user agents that share the following characteristics: ...
Page 439: Initial Registration Request Processing
SIP Contact headers). Database bindings are added upon successful registration responses. Database bindings are removed in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero).  Registration failure responses. Version 6.8 Mediant 500 E-SBC...
Page 440: Routing Using Users Registration Database
Mediant 500 E-SBC  Timeout of the Expires header value (in scenarios where the user agent did not send a refresh registration request). Note: The device's Users Registration database poses the following restrictions: • The same contact cannot belong to more than one AOR.
Page 441: Registration Restriction Control
(e.g. IP address, port, coders, media types, and RTP mode). The media capabilities exchanged in an offer/answer transaction include the following:  Media types (Audio, Secure Audio, Video, Fax, Text...) Version 6.8 Mediant 500 E-SBC...
Page 442: Media Anchoring Without Transcoding (Transparent)
Mediant 500 E-SBC  IP addresses and ports of the media flow  Media flow mode (send receive, receive only, send only, inactive)  Media coders (coders and their characteristics used in each media flow)  Other (standard or proprietary) media and session characteristics...
Page 443: 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 500 E-SBC...
Page 444 Mediant 500 E-SBC  The device does not need to perform NAT traversal (for media) and all the users are in the same domain. Figure 27-4: SBC SIP Signaling without RTP Media Flow The benefits of implementing the No Media Anchoring feature include the following: ...
Page 445: Restricting Coders
For a list of supported coders, see ''Configuring Default Coders'' on page 293. • Allowed Coder Groups are applicable only to audio media. The Allowed Coders process is as follows: The device receives an incoming SIP message with SDP (offer) and checks the offered coders. Version 6.8 Mediant 500 E-SBC...
Page 446: Prioritizing Coder List In Sdp Offer
Mediant 500 E-SBC The source (first) leg may have Allowed Coders (i.e. list of coders that can be used - enforced). The device checks for common coders between the SDP offered coders and the Allowed Coders Group list. For example, assume the following: ...
Page 447: Multiple Rtp Media Streams Per Call Session
SIP message authorization, the device processes the authorization as follows: The device challenges the received SIP message only if it is configured as a SIP method (e.g., INVITE) for authorization. This is configured in the IP Group table, using the 'Authentication Method List' parameter. Version 6.8 Mediant 500 E-SBC...
Page 448: User Authentication Based On Radius
Mediant 500 E-SBC If the message is received without a SIP Authorization header, the device "challenges" the client by sending a SIP 401 or 407 response. The client then resends the request with an Authorization header (containing the user name and password).
Page 449: Interworking Sip 3Xx Redirect Responses
The prefix ("T~&R_") remains in the user part for the classification, manipulation, and routing mechanisms. The classification, manipulation, and routing processes are done exactly like any other INVITE handling. The special prefix can be used for specific routing rules for 3xx resultant INVITEs. Version 6.8 Mediant 500 E-SBC...
Page 450: Local Handling Of Sip 3Xx
Mediant 500 E-SBC The prefix is removed before the resultant INVITE is sent to the destination. Figure 27-5: SIP 3xx Response Handling The process of this feature is described using an example: The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User@IPPBX:5060;transport=tcp;param=a>;q=0.5).
Page 451: Interworking Sip Diversion And History-Info Headers
REFER standard while others may not even support REFER. This feature supports the following:  Attended, unattended, and semi-attended call transfers  Sending INVITE, REFER-notifications, BYE, PRACK and Session Timer on behalf of Version 6.8 Mediant 500 E-SBC...
Page 452: Interworking Sip Prack Messages
Mediant 500 E-SBC peer PBXs  Advanced routing rules for the new, initiated INVITE  Forwarding early media after REFER while attempting to avoid transcoding (by sending session update)  Interoperate with environments were different SIP UAs lack basic SIP functionality such as re-INVITE, UPDATE, PRACK, Delayed Offer, re-INVITE without SDP ...
Page 453: Interworking Sip Early Media
IP Profile parameters, 'SBC Remote Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Version 6.8 Mediant 500 E-SBC...
Page 454 Mediant 500 E-SBC Figure 27-6: SBC Early Media RTP 18x without SDP Figure 27-7: Early Media RTP - SIP 18x with SDP User's Manual Document #: LTRT-10427...
Page 455: Interworking Sip Re-Invite Messages
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 300. Version 6.8 Mediant 500 E-SBC...
Page 456: Call Survivability
Mediant 500 E-SBC 27.8 Call Survivability This section describes various call survivability features supported by the SBC device. 27.8.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 457 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 477), add a rule for routing calls between the above configured IP Groups. Version 6.8 Mediant 500 E-SBC...
Page 458: Call Survivability For Call Centers
Mediant 500 E-SBC In the IP to IP Inbound Manipulation table (see ''Configuring IP-to-IP Inbound Manipulations'' on page 490), 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 primary extension contact (e.g., 600):...
Page 459 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 500 E-SBC...
Page 460: Survivability Mode Display On Aastra Ip Phones
Mediant 500 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 27-12: Routing Rule Example for Call Center Survivability 27.8.4 Survivability Mode Display on Aastra IP Phones...
Page 461: Call Forking
(e.g., 200 OK) the call is established and all other final responses are acknowledged and a BYE is sent if needed. If another UA sends the first final response, then it is possible that the SDP answer that was forwarded to the INVITE- Version 6.8 Mediant 500 E-SBC...
Page 462: Call Forking-Based Ip-To-Ip Routing Rules
Mediant 500 E-SBC initiating UA is not relevant, and media synchronization is needed between the two UAs. Media synchronization is done by sending a re-INVITE request immediately after the call is established. The re-INVITE is sent without an offer to the INVITE-initiating UA. This causes the UA to send an offer which is forwarded to the UA that confirmed the call.
Page 463: Sbc Configuration
(LAN), of the status of another SIP client in the LAN. For example, user B can subscribe to an application server for call pick-up service, whereby if user A's phone rings, the application server notifies user B. User B can then press a pre-configured key sequence to answer the call. Version 6.8 Mediant 500 E-SBC...
Page 464 Mediant 500 E-SBC The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself;...
Page 465: Configuring Admission Control
SRD and its associated IP Groups are as follows:  SRD reserved call capacity: 40  IP Group ID 1 reserved call capacity: 10  IP Group ID 2 reserved call capacity: 20 Version 6.8 Mediant 500 E-SBC...
Page 466 Mediant 500 E-SBC In this setup, the SRD offers a shared pool for unreserved call capacity of 10 [i.e., 40 – (10 + 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.
Page 467 CLI: limit-per-user user belonging to the specified 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 500 E-SBC...
Page 468: Configuring Allowed Audio Coder Groups
Mediant 500 E-SBC Parameter Description Rate Defines the rate at which tokens are added to the token bucket CLI: rate per second (i.e., token rate). One token is added to the bucket [SBCAdmissionControl_Rate] every 1000 divided by the value of this parameter (in milliseconds).
Page 469 The valid value for user-defined coders is a [AllowedCodersGroupX_Name] string of up to 25 characters (case-insensitive). For example, "HD.123" (without quotes). Note: Each coder type (e.g., G.729) can be configured only once per Allowed Coders Group. Version 6.8 Mediant 500 E-SBC...
Page 470: Configuring Allowed Video Coder Groups
Mediant 500 E-SBC 28.4 Configuring Allowed Video Coder Groups The Allowed Video Coders Group table lets you configure up to four Allowed Video Coders Groups. An Allowed Video Coders Group defines a list of video coders that can be used when forwarding video streams to a specific SIP entity.
Page 471 The device checks the SRD that is associated with this SIP Interface (in the SIP Interface table) and then classifies the SIP dialog with the first IP Group that is associated with this SRD. For example, if IP Groups 3 and 4 use the same SRD, the Version 6.8 Mediant 500 E-SBC...
Page 472 Mediant 500 E-SBC device classifies the call to IP Group 3. Note: If classification for a SIP request fails and the device is configured to reject unclassified calls, the device can send a specific 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 256).
Page 473 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 256). Source IP Address Defines the source IP address (in dotted-decimal notation) CLI: src-ip-address of the incoming SIP dialog. Version 6.8 Mediant 500 E-SBC...
Page 474 Mediant 500 E-SBC Parameter Description [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 10.8.8.10 to 10.8.8.99.  asterisk (*) wildcard: represents any number between 0 and 255.
Page 475: Classification Based On Uri Of Selected Header Example
Supported: em,100rel,timer,replaces P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group ID Prefix Username Prefix 1111 2000 10.10.10.10 Version 6.8 Mediant 500 E-SBC...
Page 476: Configuring Message Condition Rules
Mediant 500 E-SBC In the IP Group table, add the following IP Groups: Index Source URI Input Destination URI Input P-Called-Party-ID Route In this example, a match exists only for Classification Rule #1. This is because the source (1111) and destination (2000) username prefixes match those in the INVITE's P-Called-...
Page 477: Configuring Sbc Ip-To-Ip Routing
Matching characteristics (Rule) - characteristics of incoming SIP message such as the IP Group from where the message was received.  Operation (Action) - if the incoming SIP message matches the characteristics of the rule, the device routes the message to the configured destination Version 6.8 Mediant 500 E-SBC...
Page 478 Mediant 500 E-SBC If the characteristics of an incoming call do not match the first rule in the table, the call characteristics are compared to those of the second rule, and so on until a matching rule is located. If no rule is matched, the call is rejected.
Page 479 In this case, instead of setting the alternative route's 'Group Policy' to None, you must set it to Forking. The group members of the alternative route must be configured in the rows immediately below it. Version 6.8 Mediant 500 E-SBC...
Page 480 Mediant 500 E-SBC 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 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.
Page 481 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 500 E-SBC...
Page 482 Mediant 500 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 476. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect [IP2IPRouting_ReRouteIPGroupID] response (e.g., 3xx) or REFER message.
Page 483 'Destination Type' is set to IP Group. However, regardless of the settings of the parameter 'Destination Type', the IP Group is still used - only for determining the IP Profile or outgoing SRD. If neither IP Group nor SRD Version 6.8 Mediant 500 E-SBC...
Page 484 Mediant 500 E-SBC Parameter Description are defined in this table, the destination SRD is determined according to the source SRD associated with the Source IP Group (configured in the IP Group table, see ''Configuring IP Groups'' on page 260). If this table...
Page 485 [0] None (default) = Call uses only this route (even if [IP2IPRouting_GroupPolicy] Forking Group members are configured in the rows below it).  [1] Forking = Call uses this route and the routes of Forking Group members, if configured (in the rows below it). Version 6.8 Mediant 500 E-SBC...
Page 486: Configuring Sip Response Codes For Alternative Routing Reasons
Mediant 500 E-SBC Parameter Description Cost Group Assigns a Cost Group to the routing rule for determining the [IP2IPRouting_CostGroup] cost of the call. To configure Cost Groups, see ''Configuring CLI: cost-group Cost Groups'' on page 228. By default, no Cost Group is defined.
Page 487: Sbc Manipulations
IP Group. Manipulated destination user and host are performed on the following SIP headers: Request-URI, To, and Remote-Party-ID (if exists). Manipulated source user and host are performed on the following SIP headers: From, P-Asserted (if exists), P- Preferred (if exists), and Remote-Party-ID (if exists). Version 6.8 Mediant 500 E-SBC...
Page 488 Mediant 500 E-SBC Figure 28-11: SIP URI Manipulation in IP-to-IP Routing You can also restrict source user identity in outgoing SIP dialogs in the Outbound Manipulation table (using the column PrivacyRestrictionMode). The device identifies an incoming user as restricted if one of the following exists: ...
Page 489 Inbound destination SIP URI user name from "1000" to 9721000": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone> Version 6.8 Mediant 500 E-SBC...
Page 490: Configuring Ip-To-Ip Inbound Manipulations
Mediant 500 E-SBC 28.6.1 Configuring IP-to-IP Inbound Manipulations The IP to IP Inbound Manipulation table lets you configure up to 100 IP-to-IP Inbound Manipulation rules. An IP-to-IP Inbound Manipulation rule defines a manipulation sequence for the source or destination SIP URI user part of inbound SIP dialog requests. You can apply these manipulations to different SIP dialog message types (e.g., INVITE or...
Page 491 Manipulation'' on page 671. Source Host Defines the source SIP URI host name - full name (usually in CLI: src-host the From header). [IPInboundManipulation_SrcHost] The default is the asterisk (*) symbol (i.e., any host name). Version 6.8 Mediant 500 E-SBC...
Page 492 Mediant 500 E-SBC Parameter Description Destination Username Prefix Defines the prefix of the destination SIP URI user name, CLI: dst-user-name-prefix typically located in the Request-URI and To headers. [IPInboundManipulation_DestUser The default is the asterisk (*) symbol (i.e., any destination namePrefix] username prefix).
Page 493: Configuring Ip-To-Ip Outbound Manipulations
The following procedure describes how to configure IP-to-IP Outbound Manipulation rules in the Web interface. You can also configure these rules using the table ini file parameter, IPOutboundManipulation or CLI command, configure voip > sbc manipulations ip- outbound-manipulation. Version 6.8 Mediant 500 E-SBC...
Page 494 Mediant 500 E-SBC  To configure IP-to-IP outbound manipulation rules: Open the IP to IP Outbound Manipulation page (Configuration tab > VoIP menu > SBC > Manipulations SBC > IP to IP Outbound). Click Add; the following dialog box appears:...
Page 495 [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.  [2] REGISTER = Only SIP REGISTER messages.  [3] SUBSCRIBE = Only SIP SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE. Version 6.8 Mediant 500 E-SBC...
Page 496 Mediant 500 E-SBC Parameter Description  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. ReRoute IP Group ID Defines the IP Group that initiated (sent) the SIP redirect CLI: re-route-ip-group-id response (e.g., 3xx) or REFER message. This parameter is typically used for re-routing requests (e.g., INVITEs)
Page 497 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 500 E-SBC...
Page 498 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 499: Cloud Resilience Package
Part VII Cloud Resilience Package...
Page 501: 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 502 Mediant 500 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 503: 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 500 E-SBC...
Page 504: Configuring Call Survivability Mode
Mediant 500 E-SBC 30.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.
Page 505: 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 260. Version 6.8 Mediant 500 E-SBC...
Page 506: Pre-Configured Ip-To-Ip Routing Rules
Mediant 500 E-SBC 30.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 504.
Page 507: 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 508). Version 6.8 Mediant 500 E-SBC...
Page 508: Configuring Pstn Fallback
Mediant 500 E-SBC 30.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 509: High-Availability System
Part VIII High-Availability System...
Page 511: Ha Overview
The device's High Availability (HA) feature provides 1+1 system redundancy using two Mediant 500 E-SBC devices. If failure occurs in the active device, a switchover occurs to the redundant device which takes over the call handling process. Thus the continuity of call services is ensured.
Page 512: Device Switchover Upon Failure
Mediant 500 E-SBC In the active device, all logical interfaces (i.e., Media, Control, OAMP, and Maintenance) are active. In the redundant device, only the Maintenance interface is active, which is used for connectivity to the active device. Therefore, management is done only through the active device.
Page 513: 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 500 E-SBC...
Page 514 Mediant 500 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 515: Ha Configuration
Figure 32-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 32-2: Rx/Tx Mode for Direct Connection Version 6.8 Mediant 500 E-SBC...
Page 516: Configuring The Ha Devices
Mediant 500 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 32-3: Redundancy Mode for Two Isolated Switches Notes: •...
Page 517: 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 32-4: Configured MAINTENANCE Interface in Interface Table Version 6.8 Mediant 500 E-SBC...
Page 518 Mediant 500 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 519: Step 2: Configure The Second Device
(configured in Step 1: Configure the First Device on page 517). 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 500 E-SBC...
Page 520: Step 3: Initialize Ha On The Devices
Mediant 500 E-SBC 32.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. This last stage applies to both devices.
Page 521: Configuring Firewall Allowed Rules
The figure below displays an example of the required firewall rules. In this example, 10.31.4.61 is the Maintenance interface of the redundant device and 10.31.4.62 is the Maintenance interface of the active device. "HA_IF" is the name of the Maintenance interface. Figure 32-7: Allowed Firewall Rules for HA Version 6.8 Mediant 500 E-SBC...
Page 522 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 523: 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 561. Version 6.8 Mediant 500 E-SBC...
Page 524 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 525: Maintenance
Part IX Maintenance...
Page 527: Basic Maintenance
Description'' on page 40) 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 41). Version 6.8 Mediant 500 E-SBC...
Page 528: Remotely Resetting Device Using Sip Notify
Mediant 500 E-SBC  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 527). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: • Yes: The device's current configuration is saved (burned) to the flash memory prior to reset (default).
Page 529: Locking And Unlocking The Device
Under the Misc Parameters group, set the 'SIP Remote Rest' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. 34.3 Locking and Unlocking the Device The Lock and Unlock option allows you to lock the device so that it doesn't accept any new calls and maintains only the current calls.
Page 530: Saving Configuration
Mediant 500 E-SBC Click the LOCK button; a confirmation message box appears requesting you to confirm device lock. Figure 34-4: Device Lock Confirmation Message Box 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.
Page 531: 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 500 E-SBC...
Page 532 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 533: 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 500 E-SBC...
Page 534 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 535: Resetting Channels
If a voice call is currently in progress on the B-channel, it is disconnected when the 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 500 E-SBC...
Page 536 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 537: Software Upgrade
The Auxiliary files listed in the ini file are then automatically loaded through 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 500 E-SBC...
Page 538 Mediant 500 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 539: 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 540 Mediant 500 E-SBC ♦ [17] Call Waiting Ringback Tone - heard by the calling party ♦ [18] Comfort Tone ♦ [23] Hold Tone ♦ [46] Beep Tone • Tone Modulation Type: Amplitude Modulated (1) or regular (0) • Tone Form: The tone's format can be one of the following: ♦...
Page 541: Prerecorded Tones File
For SBC calls, the PRT file supports only the ringback tone and hold tone. The PRT is a .dat file containing a set of prerecorded tones that can be played by the device. Up to 40 tones (totaling approximately 10 minutes) can be stored in a single PRT Version 6.8 Mediant 500 E-SBC...
Page 542: Cas Files
Mediant 500 E-SBC 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 543: External Dial Plan File
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 537.
Page 544 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 537.
Page 545: 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 500 E-SBC...
Page 546 Mediant 500 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 547 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 500 E-SBC...
Page 548 Mediant 500 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 549: Obtaining Ip Destination From Dial Plan File
In the 'Destination Address' field, enter the required Dial Plan index using the following syntax: DialPlan<index> Where "DialPlan0" denotes [PLAN1] in the Dial Plan file, "DialPlan1" denotes [PLAN2], and so on. Note: The "DialPlan" string is case-sensitive. Version 6.8 Mediant 500 E-SBC...
Page 550: Modifying Isdn-To-Ip Calling Party Number
Mediant 500 E-SBC 38.1.4.5 Modifying ISDN-to-IP Calling Party Number The device can use the Dial Plan file to change the Calling Party Number value (source number) of the incoming ISDN call when sending to IP. For this feature, the Dial Plan file supports the following syntax: <ISDN Calling Party Number>,0,<new calling number>...
Page 551: User Information File
PBX user in the User Info table is used in the SIP From header. Note: If you have configured regular Tel-to-IP manipulation rules (see ''Configuring Source/Destination Number Manipulation'' on page 355), the device applies these rules before applying the mapping rules of the User Info table. Version 6.8 Mediant 500 E-SBC...
Page 552 Mediant 500 E-SBC • IP-to-IP Calls: Maps SIP From (calling number) and To (called number) of IP PBX extension numbers with "global" numbers. For example, if the device receives a call from IP PBX extension number 402 (calling / SIP From) that is destined to IP PBX extension number 403 (called / SIP To), the device changes both these numbers into their "global"...
Page 553 Defines the password for registering the user when [GWUserInfoTable_Password] authentication is necessary. The valid value is a string of up to 20 characters. Status (Read-only field) Displays the status of the user - "Registered" or "Not Registered". Version 6.8 Mediant 500 E-SBC...
Page 554 Mediant 500 E-SBC 38.1.5.2.2 Configuring GW User Info Table in CLI The GW User Info table can be configured in the CLI using the following commands:  To add and/or modify a user (example): # configure voip (config-voip)# sip-definition proxy-and-registration (sip-def-proxy-and-reg)# user-info gw-user-info <index, e.g.,...
Page 555: User Information File For Sbc User Database
Loadable User Info file - see ''Configuring SBC User Info Table in Loadable Text File'' on page 38.1.5.3.1 Configuring SBC User Info Table in Web Interface The following procedure describes how to configure the SBC User Info table in the Web interface. Version 6.8 Mediant 500 E-SBC...
Page 556 Mediant 500 E-SBC Note: If any User Info file is loaded to the device, all previously configured entries are removed from the table in the Web interface and replaced with the entries from the loaded User Info file.  To configure the SBC User Info table in the Web interface: Open the SBC User Info Table page (Configuration tab >...
Page 557 Web interface - see ''Loading Auxiliary Files'' on page  ini file, using the UserInfoFileName parameter - see ''Auxiliary and Configuration File Name Parameters'' on page  Automatic Update mechanism, using the UserInfoFileURL parameter - see Automatic Version 6.8 Mediant 500 E-SBC...
Page 558 Mediant 500 E-SBC Update Mechanism To add SBC users to the SBC User Info file, use the following syntax: [ SBC ] FORMAT LocalUser,UserName,Password,IPGroupID john,john_user,john_pass,2 sue,sue_user,sue_pass,1 where:  [ SBC ] indicates that this part of the file is the SBC User Info table ...
Page 559: 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 560: 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 561: 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 562: 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 563 Software Upgrade Wizard. • On the toolbar, click Device Actions, and then choose Software Upgrade Wizard. Figure 38-5: Start Software Upgrade Wizard Screen Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Version 6.8 Mediant 500 E-SBC...
Page 564 Mediant 500 E-SBC Figure 38-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 . However, if you continue with the wizard and start loading the cmp file, the upgrade process must be completed with a device reset.
Page 565 Figure 38-8: Software Upgrade Wizard – Load INI File 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): Version 6.8 Mediant 500 E-SBC...
Page 566 Mediant 500 E-SBC Figure 38-9: Software Upgrade Wizard – Files Loaded Click Reset to burn the files to the device's flash memory; the "Burn and reset in progress" message is displayed and the device 'burns' the newly loaded files to flash memory and then resets.
Page 567: Backing Up And Loading Configuration File
# copy cli-script to tftp://192.168.0.3/config-device1.txt  USB: # copy cli-script to usb://config-device1.txt Note: When loading an ini file using the Configuration File page, parameters not included in the ini file are reset to default settings. Version 6.8 Mediant 500 E-SBC...
Page 568 Mediant 500 E-SBC  To save or load an ini file: Open the Configuration File page by doing one of the following: • From the Navigation tree, click the Maintenance tab, click the Software Update menu, and then click Configuration File.
Page 569: Automatic Update Mechanism
To activate the DHCP process, perform a cold reset by pressing the device's hardware reset button. A soft reset using the Web interface doesn't trigger the DHCP process and if done, this parameter reverts to Disable. Version 6.8 Mediant 500 E-SBC...
Page 570: Provisioning From Http Server Using Dhcp Option 67
Mediant 500 E-SBC The following shows an example of a configuration file for a Linux DHCP server (dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server"...
Page 571: Provisioning From Tftp Server Using Dhcp Option 66
This method is suitable when the network in which the device is deployed contains a provisioning TFTP server for all network equipment, without being able to distinguish between AudioCodes and non-AudioCodes devices. Upon startup, the device searches for Option 66 in the DHCP response from the DHCP server.
Page 572: Ftp- Or Nfs-Based Provisioning
NFS v2/v3 is also supported. 39.1.6 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. As soon as a registered device contacts the EMS server through SNMP, the EMS server handles all required configuration automatically, upgrading software as needed.
Page 573: 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 500 E-SBC...
Page 574: 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 575: Access Authentication With Http Server
• <MAC> - device's MAC address • <VER> - software version currently installed on the device, e.g., "6.80.200.001" • <CONF> - configuration version, as configured in the ini file parameter, INIFileVersion or CLI command, configuration-version Version 6.8 Mediant 500 E-SBC...
Page 576 For example, if you set AupdHttpUserAgent = <NAME>;<VER>, the device sends the following User-Agent header: Mozilla/4.0 (compatible; AudioCodes; Mediant; 6.80.200.001) If the provisioning server has relevant files available for the device, the following occurs, depending on file type and configuration: •...
Page 577: 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 500 E-SBC...
Page 578: Cyclic Redundancy Check On Downloaded Configuration Files
Mediant 500 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 579: Automatic Update Configuration Examples
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' ♦ CLI: Version 6.8 Mediant 500 E-SBC...
Page 580: Automatic Update From Nfs, Ftp And Http Servers
Mediant 500 E-SBC # configure system (config-system)# automatic update automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' Automatic Update of Call Progress Tone file: ♦ ini File: CptFileURL = 'https://www.company.com/call_progress.dat' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# call-progress-tones 'http://www.company.com/call_progress.dat' Automatic Update of ini configuration file: ♦...
Page 581: Automatic Update For Mass Deployment
Device queries the provisioning server daily at 24:00 (midnight) for software, configuration and auxiliary files.  HTTP-based provisioning server at www.company.com for storing the files.  DNS server at 80.179.52.100 for resolving the domain name of the provisioning server. Version 6.8 Mediant 500 E-SBC...
Page 582 Mediant 500 E-SBC  To set up automatic provisioning for mass provisioning (example): Create an ini file named "master_configuration.ini" with the following settings: Common configuration for all devices: # Check for updates daily at 24:00 AutoUpdatePredefinedTime = '24:00' # CPT file update: CptFileURL = 'https://www.company.com/call_progress.dat'...
Page 583: Restoring Factory Defaults
# enable 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 500 E-SBC...
Page 584: Restoring Defaults Using Hardware Reset Button
Mediant 500 E-SBC 40.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:  With a paper clip or any other similar pointed object, press and hold down the reset pinhole button, located on the front panel for at least 12 seconds (but no more than 25 seconds).
Page 585: Automatic Archiving Of Configuration File
To configure configuration-file archiving, use the following CLI command (root level):  Archiving to a remote server: # write-and-backup to <URL path with file name>  Archiving to a USB: # write-and-backup to usb:///<file name> Version 6.8 Mediant 500 E-SBC...
Page 586 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 587: Usb Storage Capabilities
# copy voice-configuration from usb:///<ini configuration file name>  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 500 E-SBC...
Page 588 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 589: Status, Performance Monitoring And Reporting
Part X Status, Performance Monitoring and Reporting...
Page 591: System Status
To delete a loaded file:  Click the Delete button corresponding to the file that you want to delete. Deleting a file takes effect only after device reset (see ''Resetting the Device'' on page 527). Version 6.8 Mediant 500 E-SBC...
Page 592: Viewing Ethernet Port Information
Mediant 500 E-SBC 43.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 593: Carrier-Grade Alarms
Source: unit from which the alarm was raised  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 500 E-SBC...
Page 594: Viewing Alarm History
Mediant 500 E-SBC 44.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 595: 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 500 E-SBC...
Page 596: Viewing Trunk Utilization
Mediant 500 E-SBC 45.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 597: 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 500 E-SBC...
Page 598 Mediant 500 E-SBC  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 45-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 599: Viewing Average Call Duration
Figure 45-4: Average Call Duration Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view information for an SRD or IP Group. From the 'Index' drop-down list, select the SRD or IP Group index. Version 6.8 Mediant 500 E-SBC...
Page 600 Mediant 500 E-SBC Use the Zoom In button to increase the displayed time resolution or the Zoom Out button to decrease it. Instead of using these zoom buttons, you can use the slide ruler. As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds;...
Page 601: Voip Status
Color Label Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Purple Lower Layer Down (DS3 physical layer is disabled) Version 6.8 Mediant 500 E-SBC...
Page 602: Viewing Nfas Groups And D-Channel Status
Mediant 500 E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 46-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 603: Viewing Active Ip Interfaces
Interface table (see ''Configuring IP Network Interfaces'' on page 113).  To view active IP network interfaces:  Open the IP Interface Status page (Status & Diagnostics tab > VoIP Status menu > IP Interface Status). Version 6.8 Mediant 500 E-SBC...
Page 604: Viewing Ethernet Device Status
Mediant 500 E-SBC 46.4 Viewing Ethernet Device Status The Ethernet Device Status page displays the configured Ethernet Devices that have been successfully applied to the device. For configuring Ethernet Devices, see ''Configuring Underlying Ethernet Devices'' on page 111.  To view the configured and applied Ethernet Devices: ...
Page 605: Viewing Performance Statistics
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. Figure 46-6: Calls Count Page Version 6.8 Mediant 500 E-SBC...
Page 606 Mediant 500 E-SBC The fields in this page are described in the following table: Table 46-3: Call Counters Description Counter Description Indicates the number of attempted calls. It is composed of established Number of Attempted Calls and failed calls. The number of established calls is represented by the 'Number of Established Calls' counter.
Page 607: Viewing Registered Sas/Sbc Users
SBC users: # show voip register db sbc list • SBC contacts of a specified AOR: # show voip register db sbc user <Address Of Record> • SAS users: # show voip register db sas list Version 6.8 Mediant 500 E-SBC...
Page 608: Viewing Registration Status
Mediant 500 E-SBC 46.9 Viewing Registration Status The Registration Status page displays the registration status of the device's SIP Accounts, which are configured in the Accounts table (see ''Configuring Registration Accounts'' on page 277).  To view the registration status: ...
Page 609 IP address and FQDN (if exists) of the Proxy server with which the device currently operates.  N/A = Proxy server isn't defined. State  OK = Communication with the Proxy server is in order.  Fail = No response from any of the defined Proxies. Version 6.8 Mediant 500 E-SBC...
Page 610: Viewing Ip Connectivity
Mediant 500 E-SBC 46.11 Viewing IP Connectivity The IP Connectivity page displays on-line, read-only network diagnostic connectivity information on all destination IP addresses configured in the Outbound IP Routing table (see ''Configuring Outbound IP Routing Table'' on page 379). Note: he information in columns 'Quality Status' and 'Quality Info' (per IP address) is reset if two minutes elapse without a call to that destination.
Page 611 Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).  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 500 E-SBC...
Page 612 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 613: Reporting Information To External Party
Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Silence Suppression State Jitter Buffer Jitter Buffer Adaptive Jitter Buffer Rate Jitter Buffer Nominal Version 6.8 Mediant 500 E-SBC...
Page 614 Mediant 500 E-SBC Group Metric Name Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Loss Density Burst Gap Loss Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold Delay...
Page 615 Open the RTP/RTCP Settings page (Configuration tab > VoIP menu > Media > RTP/RTCP Settings). The RTCP XR parameters are listed under the RTCP XR Settings group: Figure 47-1: RTCP XR Parameters in RTP/RTCP Settings Page Version 6.8 Mediant 500 E-SBC...
Page 616: Generating Call Detail Records
Mediant 500 E-SBC Under the RTCP XR Settings group, configure the following: • 'Enable RTCP XR' (VQMonEnable) - enables voice quality monitoring and RTCP • 'Burst Threshold' (VQMonBurstHR) - defines the voice quality monitoring excessive burst alert threshold. • 'Delay Threshold' (VQMonDelayTHR) - defines the voice quality monitoring excessive delay alert threshold.
Page 617: Cdr Field Description
Call time is based on SetupTime, ConnectTime and ReleaseTime CDR fields Table 47-2: CDR Fields for SBC Signaling CDR Field Name Description Format SBCReportType Report Type: String  "CALL_START"  "CALL_CONNECT"  "CALL_END"  "DIALOG_START"  "DIALOG_END" EPTyp Endpoint type: String  "SBC" Version 6.8 Mediant 500 E-SBC...
Page 618 Mediant 500 E-SBC CDR Field Name Description Format SIPMethod SIP message type String of up to 10 characters SIPCallId Unique ID of call String of up to 50 characters SessionId Unique Session ID String of up to 10 characters Orig...
Page 619 If no SIP Reason header exists, the description is taken from the reason text, if exists, of the SIP response code, for example: "417 Unknown Resource-Priority".  If no reason text exists in the SIP response code, the description is Version 6.8 Mediant 500 E-SBC...
Page 620: Cdr Fields For Sbc Media
|SIPInterfaceId |ProxySetId |IpProfileId (name) |MediaRealmId (name) |DirectMedia |SIPTrmReason [S=3] |CALL_END |SBC |170369730753201211288@10.132.10.245 |0 |RMT |10.132.10.245 |5060 |10.132.10.250 |5070 |UDP |103@audiocodes.com |103@audiocodes.com |101@10.132.10.250 |101@10.132.10.250 |0 |RMT |GWAPP_NORMAL_CALL_CLEAR |NO_ANSWER |06:13:54.950 UTC Thu Mar 02 2012 | |06:14:01.175 UTC Thu Mar 02 2012 |-1 | | |40 |2 () |0 (5070SRD) |2 |3 |0 () |0 (lanmedia) |no |CANCEL 47.2.2.2 CDR Fields for SBC Media...
Page 621: 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 500 E-SBC...
Page 622 Mediant 500 E-SBC Field Name Description EPTyp Endpoint type:  ISDN    IPMEDIA  NETANN  STREAMING  TRANSPARENT  MSCML  VXML  IP2IP Orig Call originator:  LCL (Tel side)  RMT (IP side) SourceIp Source IP address...
Page 623 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 500 E-SBC...
Page 624 Mediant 500 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 625: Release Reasons In Cdr
"RELEASE_BECAUSE_DESTINATION_BUSY"  "RELEASE_BECAUSE_NOANSWER"  "RELEASE_BECAUSE_UNKNOWN_REASON"  "RELEASE_BECAUSE_REMOTE_CANCEL_CALL"  "RELEASE_BECAUSE_UNMATCHED_CAPABILITIES"  "RELEASE_BECAUSE_UNMATCHED_CREDENTIALS"  "RELEASE_BECAUSE_UNABLE_TO_HANDLE_REMOTE_REQUEST"  "RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT"  "RELEASE_BECAUSE_CONFERENCE_FULL"  "RELEASE_BECAUSE_VOICE_PROMPT_PLAY_ENDED"  "RELEASE_BECAUSE_VOICE_PROMPT_NOT_FOUND"  "RELEASE_BECAUSE_TRUNK_DISCONNECTED"  "RELEASE_BECAUSE_RSRC_PROBLEM"  "RELEASE_BECAUSE_MANUAL_DISC"  "RELEASE_BECAUSE_SILENCE_DISC"  "RELEASE_BECAUSE_RTP_CONN_BROKEN"  "RELEASE_BECAUSE_DISCONNECT_CODE"  "RELEASE_BECAUSE_GW_LOCKED" Version 6.8 Mediant 500 E-SBC...
Page 626 Mediant 500 E-SBC  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS"  "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 627: Configuring Radius Accounting
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. Version 6.8 Mediant 500 E-SBC...
Page 628 Mediant 500 E-SBC  To configure RADIUS accounting: Open the RADIUS Parameters page (Configuration tab > VoIP menu > SIP Definitions > RADIUS Parameters Settings). Figure 47-3: RADIUS Accounting Parameters Page Set the 'Enable RADIUS Access Control' parameter to Enable.
Page 629 (Gateway call) acct-output- Number of octets sent Numeric - Stop Acc octets for that call duration (Gateway call) acct-session- A unique accounting String 34832 Start Acc identifier - match start Stop Acc & stop Version 6.8 Mediant 500 E-SBC...
Page 630 Mediant 500 E-SBC Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. acct-session- For how many Numeric - Stop Acc time seconds the user received the service acct-input- Number of packets Numeric - Stop Acc packets...
Page 631: Event Notification Using X-Detect Header
The IO* SIT tone is detected as VC The device can map these SIT tones to a Q.850 cause and then map them to SIP 5xx/4xx responses, using parameters SITQ850Cause, SITQ850CauseForNC, SITQ850CauseForIC, SITQ850CauseForVC, and SITQ850CauseForRO. Version 6.8 Mediant 500 E-SBC...
Page 632 Mediant 500 E-SBC Table 47-7: Special Information Tones (SITs) Reported by the device Special Description First Tone Second Tone Third Tone Information Frequency Frequency Frequency Tones (SITs) Duration Duration Duration Name (Hz) (ms) (Hz) (ms) (Hz) (ms) No circuit found 985.2...
Page 633 X- Detect: Response=CPT,FAX INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Response=CPT,FAX Content-Type: Application/X-Detect Content-Length: xxx Type = CPT Subtype = SIT Version 6.8 Mediant 500 E-SBC...
Page 634: Querying Device Channel Resources Using Sip Options
Mediant 500 E-SBC 47.5 Querying Device Channel Resources using SIP OPTIONS The device reports its maximum and available channel resources in SIP 200 OK responses upon receipt of SIP OPTIONS messages. The device sends this information in the SIP X- Resources header with the following parameters: ...
Page 635: Diagnostics
Part XI Diagnostics...
Page 637: 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: Version 6.8 Mediant 500 E-SBC...
Page 638: Event Representation In Syslog Messages
Mediant 500 E-SBC Message Item Description [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237][SID:1034099026] (lgr_flow)(621) #0:DIGIT_EV [File: Line:-1] 18:38:14.958 : 10.33.45.72 : NOTICE:...
Page 639 No Available Release Descriptor 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 500 E-SBC...
Page 640: Identifying Audiocodes Syslog Messages Using Facility Levels
Mediant 500 E-SBC 48.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 641: Snmp Alarms In Syslog Messages
Notice Indeterminate Notice Cleared Notice  Cleared Alarms: CLEAR-ALARM: <Alarm Name>; Textual Description: <Textual Description>; Severity <Alarm Severity>; Source <Alarm Source>; Unique ID: <Alarm Unique ID >; If exists Additional Info1:/ Additional Info2:/ Additional Info3: Version 6.8 Mediant 500 E-SBC...
Page 642: Enabling Syslog
Mediant 500 E-SBC 48.2 Enabling Syslog The following procedure describes how to enable and configure Syslog. Notes: • For configuring CDR reporting, see ''Configuring CDR Reporting'' on page 616. • For viewing Syslog messages in the Web interface, see ''Viewing Syslog Messages'' on page 647.
Page 643: 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 587. Version 6.8 Mediant 500 E-SBC...
Page 644: Filtering Syslog Messages And Debug Recordings
Mediant 500 E-SBC  To configure and activate debug recording: Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings). Figure 48-3: Logging Settings Page Configure the debug capturing server using the 'Debug Recording Destination IP' and 'Debug Recording Destination Port' parameters.
Page 645 [12] User = Filters according to a specified user defined by username or user@host.  [13] IP Trace = Filters according to a specified IP network trace wireshark-like expression. For a detailed description on configuring IP traces, see ''Filtering IP Network Traces'' on page 646. Version 6.8 Mediant 500 E-SBC...
Page 646: Filtering Ip Network Traces
Mediant 500 E-SBC Parameter Description Value Defines the value of the selected filtering type in the 'Filter Type' CLI: value parameter. [LoggingFilters_Value] The value can be the following:  A single value  A range, using a hyphen "-" between the two values, e.g., "1-3"...
Page 647: 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 648 Mediant 500 E-SBC  To activate the Web interface's Message Log: Enable Syslog (see ''Enabling Syslog'' on page 642). 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 649: Collecting Debug Recording Messages
User's Manual 48. Syslog and Debug Recordings 48.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 650 Mediant 500 E-SBC For ISDN trace messages, the additional header, "NetBricks Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below: AUDIOCODES DEBUG RECORDING NetBricks Trace System time: 3559 Direction: Message received from internal server queue (73) From (Entity origination ID): DL_D (DL LAPD Q.921) (100)
Page 651: Debug Capturing On Physical Voip Interfaces
TFTP or FTP server: # debug capture voip physical stop <TFTP/FTP server IP address> If no IP address is defined, the capture is saved on the device for later retrieval. Version 6.8 Mediant 500 E-SBC...
Page 652 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 653: 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 500 E-SBC...
Page 654 Mediant 500 E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-10427...
Page 655: 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 656 Mediant 500 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 657: Testing Sip Signaling Calls
By default, you can configure up to five test calls. However, this number can be increased by installing the relevant Software License Key. For more information, contact your AudioCodes sales representative. 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 >...
Page 658 Mediant 500 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 51-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
Page 659 '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 500 E-SBC...
Page 660 Mediant 500 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 661: 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 662). Version 6.8 Mediant 500 E-SBC...
Page 662: Viewing Test Call Statistics
Mediant 500 E-SBC 51.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 661), you can also view a more detailed status description which includes test call statistics.
Page 663: Configuring Dtmf Tones For Test Calls
Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 51-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 500 E-SBC...
Page 664: Configuring Basic Test Call
Mediant 500 E-SBC 51.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. All incoming calls with this called (destination) prefix number is identified as a test call and sent to the simulated endpoint.
Page 665: 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 500 E-SBC...
Page 666: Test Call Configuration Examples
Mediant 500 E-SBC  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Parameters'' on page 696): Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings).
Page 667 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 668 Mediant 500 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 669: Appendix
Part XII Appendix...
Page 671: Dialing Plan Notation For Routing And Manipulation
03(100): for any number that starts with 03 and ends with 100.  [100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc. Version 6.8 Mediant 500 E-SBC...
Page 672 Mediant 500 E-SBC Notation Description  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.
Page 673: Configuration Parameters Reference
Web: Allow WAN access to Enables WAN access to the management interface through SSH.  [0] Disable (default) CLI: wan-ssh-allow  [1] Enable [AllowWanSSH] Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500 E-SBC...
Page 674: Web Parameters
Mediant 500 E-SBC Parameter Description Web: Web and Telnet This table configures up to ten IP addresses that are permitted to Access List Table access the device's Web interface and Telnet interfaces. Access from EMS: Web Access an undefined IP address is denied. When no IP addresses are defined Addresses in this table, this security feature is inactive (i.e., the device can be...
Page 675 'Web User Accounts', 'Certificates', 'Regional Settings', 'Maintenance Actions' and all file-loading pages ('Load Auxiliary Files', 'Software Upgrade Wizard', and 'Configuration File'). Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500 E-SBC...
Page 676 Mediant 500 E-SBC Parameter Description [ResetWebPassword] Resets the username and password of the primary ("Admin") and secondary ("User") accounts to their default settings ("Admin" and "Admin" respectively), and deletes all other users that may have been configured.  [0] = (Default) Password and username retain their values.
Page 677: Telnet Parameters
Table 53-4: ini File Parameters Parameter Description [INIPasswordsDisplayType] Defines how passwords are displayed in the ini file.  [0] Disable (default) = Passwords are obscured ("encoded"). The passwords are displayed in the following syntax: $1$<obscured Version 6.8 Mediant 500 E-SBC...
Page 678: Snmp Parameters
Mediant 500 E-SBC Parameter Description password> (e.g., $1$S3p+fno=).  [1] Enable = All passwords are hidden and replaced by an asterisk (*). 53.1.5 SNMP Parameters The SNMP parameters are described in the table below. Table 53-5: SNMP Parameters Parameter Description Web: Enable SNMP Enables SNMP.
Page 679 [SNMPManagerTrapPort_x] is 162. Web: Trap Enable Enables the sending of traps to the corresponding SNMP CLI: send-trap manager. [SNMPManagerTrapSendingEna  [0] Disable = Sending is disabled. ble_x]  [1] Enable = (Default) Sending is enabled. Version 6.8 Mediant 500 E-SBC...
Page 680 Mediant 500 E-SBC Parameter Description Web: Trap User Defines the SNMPv3 USM user or SNMPv2 user to associate CLI: trap-user with the trap destination. This determines the trap format, [SNMPManagerTrapUser_x] authentication level, and encryption level. By default, it is associated with the SNMPv2 user (SNMP trap community string).
Page 681: 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 500 E-SBC...
Page 682: 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 683: Automatic Update Parameters
The valid value is a string of up to 511 characters. By default, this parameter is not defined. In other words, the User-Agent header is set to "Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>)”, where the tags are replaced with actual values. Notes: ...
Page 684 Mediant 500 E-SBC Parameter Description access authentication with the HTTP server used for the Automatic Update feature. The valid value is a string of up to 50 characters. By default, no value is defined. EMS: AUPD Verify Certificates Determines whether the Automatic Update mechanism verifies CLI: system/tls/aupd-verify-cert server certificates when using HTTPS.
Page 685 Note: For this parameter to take effect, a device reset is required. CLI: tls-cert Defines the name of the TLS certificate file and the URL from where [TLSCertFileUrl] it can be downloaded. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500 E-SBC...
Page 686: Networking Parameters
Mediant 500 E-SBC Parameter Description CLI: tls-private-key Defines the URL for downloading a TLS private key file using the [TLSPkeyFileUrl] Automatic Update facility. [UserInfoFileURL] Defines the name of the User Information file and the path to the server (IP address or FQDN) on which it is located.
Page 687: Multiple Voip Network Interfaces And Vlan Parameters
Defines up to 30 static IP routes for the device. Table The format of the ini file table parameter is as follows: CLI: configure voip > static [ StaticRouteTable ] [StaticRouteTable] FORMAT StaticRouteTable_Index = StaticRouteTable_DeviceName, StaticRouteTable_Destination, StaticRouteTable_PrefixLength, StaticRouteTable_Gateway, StaticRouteTable_Description; Version 6.8 Mediant 500 E-SBC...
Page 688: Quality Of Service Parameters
Mediant 500 E-SBC Parameter Description [ \StaticRouteTable ] For a description of this parameter, see ''Configuring Static IP Routes'' on page 120. 53.2.4 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below. Table 53-12: QoS Parameters...
Page 689: Nat Parameters
Defines the global (public) IP address of the device to enable static NAT EMS: Static NAT IP between the device and the Internet. Address Note: For this parameter to take effect, a device reset is required. CLI: nat-ip-addr [StaticNatIP] Version 6.8 Mediant 500 E-SBC...
Page 690: Nfs Parameters
Mediant 500 E-SBC Parameter Description Web: SIP NAT Detection Enables the device to detect whether the incoming INVITE message is CLI: configure voip/sip- sent from an endpoint located behind NAT. definition advanced-  [0] Disable = Disables the device's NAT Detection mechanism.
Page 691: Dns Parameters
The Dynamic Host Control Protocol (DHCP) parameters are described in the table below. Table 53-16: DHCP Parameters Parameter Description Web: Enable DHCP Enables DHCP client functionality. EMS: DHCP Enable  [0] Disable (default) [DHCPEnable]  [1] Enable Notes: Version 6.8 Mediant 500 E-SBC...
Page 692 Mediant 500 E-SBC Parameter Description  For this parameter to take effect, a device reset is required.  For a detailed description of DHCP, see ''DHCP-based Configuration Server'' on page 569.  This parameter is a "hidden" parameter. Once defined and saved to flash memory, its value doesn't revert to default even if the parameter doesn't appear in the ini file.
Page 693: Ntp And Daylight Saving Time Parameters
Defines a second NTP server's address as an FQDN or an IP Address address (in dotted-decimal notation). This NTP is used for [NTPSecondaryServerIP] redundancy; if the primary NTP server fails, then this NTP server is used. The default IP address is 0.0.0.0. Version 6.8 Mediant 500 E-SBC...
Page 694 Mediant 500 E-SBC Parameter Description Web: NTP UTC Offset Defines the Universal Time Coordinate (UTC) offset (in seconds) EMS: UTC Offset from the NTP server. CLI: utc-offset The default offset is 0. The offset range is -43200 to 43200. [NTPServerUTCOffset] Note: The offset setting is applied only on the hour.
Page 695: Debugging And Diagnostics Parameters
Ethernet cable disconnected on the remote switch) and the following mechanisms are activated if enabled:  Busy Out mechanism (see the EnableBusyOut parameter)  Test fails: The device resets (if this parameter is set to [2]) to overcome the internal communication error. Version 6.8 Mediant 500 E-SBC...
Page 696: Sip Test Call Parameters
Mediant 500 E-SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  LAN watchdog is applicable only if the Ethernet connection is full duplex. Web: Delay After Reset [sec] Defines the time interval (in seconds) that the device's operation is CLI: delay-after-reset delayed after a reset.
Page 697: Syslog, Cdr And Debug Parameters
If you enable Syslog, you must enter an IP address of the Syslog server (using the SyslogServerIP parameter).  Syslog messages may increase the network traffic.  To configure Syslog SIP message logging levels, use the GwDebugLevel parameter. Version 6.8 Mediant 500 E-SBC...
Page 698 Mediant 500 E-SBC Parameter Description  By default, logs are also sent to the RS-232 serial port. For how to establish serial communication with the device, refer to the Installation Manual. Web/EMS: Syslog Server IP Defines the IP address (in dotted-decimal notation) of the computer Address on which the Syslog server is running.
Page 699 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 700 Mediant 500 E-SBC Parameter Description  CPU usage is at least 5% greater than threshold: Debug level is reduced another level.  CPU usage is 5 to 19% less than threshold: Debug level is increased by one level.  CPU usage is at least 20% less than threshold: Debug level is increased by another level.
Page 701 [1] Enable Web: Core Dump Destination Defines the IP address of the remote server where you want the device to send the Core Dump file. [CoreDumpDestIP] By default, no IP address is defined. Logging Filters Table Version 6.8 Mediant 500 E-SBC...
Page 702: Resource Allocation Indication Parameters
Mediant 500 E-SBC Parameter Description Web: Logging Filters Table This table parameter defines logging filtering rules for Syslog CLI: configure system > messages and debug recordings. logging > logging-filters The format of the ini file table parameter is: [LoggingFilters] [ LoggingFilters ]...
Page 703: Ha Ping Parameters
This table parameter defines the device's access list (firewall), Parameters which defines network traffic filtering rules. CLI: configure voip > access-list The format of this parameter is as follows: [AccessList] [AccessList] FORMAT AccessList_Index = AccessList_Source_IP, AccessList_Source_Port, AccessList_PrefixLen, AccessList_Source_Port, AccessList_Start_Port, Version 6.8 Mediant 500 E-SBC...
Page 704 Mediant 500 E-SBC Parameter Description AccessList_End_Port, AccessList_Protocol, AccessList_Use_Specific_Interface, AccessList_Interface_ID, AccessList_Packet_Size, AccessList_Byte_Rate, AccessList_Byte_Burst, AccessList_Allow_Type; [\AccessList] For example: AccessList 10 = mgmt.customer.com, , , 32, 0, 80, tcp, 1, OAMP, 0, 0, 0, allow; AccessList 22 = 10.4.0.0, , , 16, 4000, 9000, any, 0, , 0, 0, 0, block;...
Page 705: Https Parameters
53.4.2 HTTPS Parameters The Secure Hypertext Transport Protocol (HTTPS) parameters are described in the table below. Table 53-24: HTTPS Parameters Parameter Description Web: Secured Web Connection Determines the protocol used to access the Web interface. Version 6.8 Mediant 500 E-SBC...
Page 706 Mediant 500 E-SBC Parameter Description  (HTTPS) [0] HTTP and HTTPS (default). EMS: HTTPS Only  [1] HTTPs Only = Unencrypted HTTP packets are blocked. CLI: secured-connection Note: For this parameter to take effect, a device reset is [HTTPSOnly] required.
Page 707: Srtp Parameters
[2] AES-CM-128-HMAC-SHA1-32 = device uses AES-CM encryption with a 128-bit key and HMAC-SHA1 message authentication with a 32-bit tag.  [4] ARIA-CM-128-HMAC-SHA1-80 = device uses ARIA encryption algorithm with a 128-bit key and HMAC-SHA1 message authentication with a 32-bit tag. Version 6.8 Mediant 500 E-SBC...
Page 708 Mediant 500 E-SBC Parameter Description  [8] ARIA-CM-192-HMAC-SHA1-80 = device uses ARIA encryption algorithm with a 192-bit key and HMAC-SHA1 message authentication with a 32-bit tag. Notes:  For enabling ARIA encryption, use the AriaProtocolSupport parameter.  This parameter also affects the selection of the crypto in the device's answer.
Page 709: Tls Parameters
Device acts as a client: Verification of the server certificate is required to establish the TLS connection.  Device acts as a server: The device requires the receipt and verification of the client certificate to establish the TLS connection. Version 6.8 Mediant 500 E-SBC...
Page 710 Mediant 500 E-SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  This feature can be configured per SIP Interface (see Configuring SIP Interfaces on page 256).  The SIPS certificate files can be changed using the parameters HTTPSCertFileName and HTTPSRootFileName.
Page 711: Ssh Parameters
SSHAdminKey. CLI: ssh-require-public-key  [1] = RSA public keys are mandatory. [SSHRequirePublicKey] Note: To define the key size, use the TLSPkeySize parameter. Web: Max Payload Size Defines the maximum uncompressed payload size (in bytes) for Version 6.8 Mediant 500 E-SBC...
Page 712: Ids Parameters
Mediant 500 E-SBC Parameter Description EMS: SSH Max Payload Size SSH packets. CLI: ssh-max-payload-size The valid value is 550 to 32768. The default is 32768. [SSHMaxPayloadSize] Web: Max Binary Packet Size Defines the maximum packet size (in bytes) for SSH packets.
Page 713: Quality Of Experience Parameters
The Quality of Experience (QoE) parameters are described in the table below. Table 53-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 714 Mediant 500 E-SBC Parameter Description [QOESecondaryServerIp] Web: Port Defines the port of the SEM server. CLI: configure voip/qoe The valid value range is 0 to 65534. The default is 5000. configuration/port [QOEPort] Web: Interface Name Defines the IP network interface on which the quality experience CLI: configure voip/qoe reports are sent.
Page 715 The format of the ini file table parameter is as follows: CLI: configure voip/qoe [MediaEnhancementRules] media-enhancement-rules FORMAT MediaEnhancementRules_Index = [MediaEnhancementRules] MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of this table, see ''Configuring Media Enhancement Profiles'' on page 244. Version 6.8 Mediant 500 E-SBC...
Page 716: Control Network Parameters
Mediant 500 E-SBC 53.6 Control Network Parameters 53.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 53-30: Proxy, Registration and Authentication SIP Parameters Parameter Description IP Group Table Web: IP Group Table This table configures IP Groups.
Page 717 Proxy option, by setting the parameter EnableProxyKeepAlive to 1 or 2. Web: Proxy IP List Refresh Time Defines the time interval (in seconds) between each Proxy IP EMS: IP List Refresh Time list refresh. Version 6.8 Mediant 500 E-SBC...
Page 718 Mediant 500 E-SBC Parameter Description CLI: proxy-ip-lst-rfrsh-time The range is 5 to 2,000,000. The default interval is 60. [ProxyIPListRefreshTime] Web: Enable Fallback to Routing Determines whether the device falls back to the Outbound IP Table Routing table for call routing when Proxy servers are EMS: Fallback Used unavailable.
Page 719 NAPTR response. If the NAPTR query fails, an SRV query is done according to the configured transport type. If the Proxy IP address parameter contains a domain name with port definition (e.g., ProxyIP = domain.com:5080), the Version 6.8 Mediant 500 E-SBC...
Page 720 Mediant 500 E-SBC Parameter Description device performs a regular DNS A-record query. If a specific Transport Type is defined, a NAPTR query is not performed. Notes:  This functionality can be configured per Proxy Set in the Proxy Set table (see ''Configuring Proxy Sets'' on page 270).
Page 721 ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap, ProxySet_SRD, ProxySet_ClassificationInput, ProxySet_ProxyRedundancyMode, ProxySet_DNSResolveMethod, ProxySet_KeepAliveFailureResp; [ \ProxySet ] For a description of this table, see ''Configuring Proxy Sets'' on page 270. For configuring the IP addresses per Proxy Set in the ini file, Version 6.8 Mediant 500 E-SBC...
Page 722 Mediant 500 E-SBC Parameter Description use the ProxyIP parameter. Registrar Parameters Web: Enable Registration Enables the device to register to a Proxy/Registrar server. EMS: Is Register Needed  [0] Disable = (Default) The device doesn't register to CLI: enable-registration Proxy/Registrar server.
Page 723 (indicative of an outbound proxy server failure).  The remote SIP UA abandons a call and the only provisional response the device has received for the call is 100 Trying (indicative of a home proxy server Version 6.8 Mediant 500 E-SBC...
Page 724 Mediant 500 E-SBC Parameter Description failure, i.e., the failure of a proxy in the route after the outbound proxy).  The device terminates a call due to the expiration of RFC 3261 Timer B or due to the receipt of a 408...
Page 725 - set to the domain name of the home network  uri - set to the SIP URI of the domain name of the home network  nonce - set to an empty value Version 6.8 Mediant 500 E-SBC...
Page 726 Mediant 500 E-SBC Parameter Description  response - set to an empty value For example: Authorization: Digest username=alice_private@home1.net, realm=”home1.net”, nonce=””, response=”e56131d19580cd833064787ecc” Note: This registration header is according to the IMS 3GPP TS24.229 and PKT-SP-24.220 specifications. Web: Add initial Route Header...
Page 727: Network Application Parameters
[SIPInterface] [ SIPInterface ] FORMAT SIPInterface_Index = SIPInterface_InterfaceName, SIPInterface_NetworkInterface, SIPInterface_ApplicationType, SIPInterface_UDPPort, SIPInterface_TCPPort, SIPInterface_TLSPort, SIPInterface_SRD, SIPInterface_MessagePolicy, SIPInterface_TLSMutualAuthentication, SIPInterface_TCPKeepaliveEnable, SIPInterface_ClassificationFailureResponseType, SIPInterface_PreClassificationManSet; [ \SIPInterface ] For a detailed description of this table, see ''Configuring SIP Interfaces'' Version 6.8 Mediant 500 E-SBC...
Page 728 Mediant 500 E-SBC Parameter Description on page 256. Defines the interval (in sec) between the last data packet sent and the [TCPKeepAliveTime] first keep-alive probe to send. The valid value is 10 to 65,000. The default is 60. Notes: ...
Page 729: General Sip Parameters
Web: SIP Remote Reset Enables a specific device action upon the receipt of a SIP NOTIFY CLI: sip-remote-reset request, where the action depends on the value received in the Event [EnableSIPRemoteReset] header.  [0] Disable (default) Version 6.8 Mediant 500 E-SBC...
Page 730 (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 731 (IpProfile_EnableEarlyMedia) or Tel Profiles. For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page or in the Tel Profile table, see Configuring Tel Profiles on page 297. Notes: Version 6.8 Mediant 500 E-SBC...
Page 732 Mediant 500 E-SBC Parameter Description  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.  This parameter is applicable only to the Gateway application.
Page 733 Trunk Group ID 1 if all its member trunks are down.  [0] = Disable (default)  [1] = The device does not respond to SIP OPTIONS received from the proxy associated with Trunk Group 1. Version 6.8 Mediant 500 E-SBC...
Page 734 Mediant 500 E-SBC Parameter Description  [2] = The device does not send keep-alive messages to the proxy associated with Trunk Group 1.  [3] = Both options [1] and [2]. Notes:  When this parameter is set to not respond to SIP OPTIONS received from the proxy, it is applicable only if the OPTIONS message does not include a user part in the Request-URI.
Page 735 CLI: sip-udp-local-port [LocalSIPPort] Web: SIP TCP Local Port Defines the local TCP port for SIP messages. EMS: TCP Local SIP Port The valid range is 1 to 65535. The default is 5060. CLI: sip-tcp-local-port [TCPLocalSIPPort] Version 6.8 Mediant 500 E-SBC...
Page 736 Mediant 500 E-SBC Parameter Description Web: SIP TLS Local Port Defines the local TLS port for SIP messages. EMS: TLS Local SIP Port The valid range is 1 to 65535. The default is 5061. CLI: sip-tls-local-port Note: The value of this parameter must be different from the value of [TLSLocalSIPPort] the parameter TCPLocalSIPPort.
Page 737 EMS: Enable RPI Header  [0] Disable (default). CLI: remote-party-id  [1] Enable = Remote-Party-Identity headers are generated in SIP [EnableRPIheader] INVITE messages for both called and calling numbers. Web: Enable History-Info Enables usage of the History-Info header. Version 6.8 Mediant 500 E-SBC...
Page 738 Mediant 500 E-SBC Parameter Description  Header [0] Disable (default) EMS: Enable History Info  [1] Enable CLI: hist-info-hdr User Agent Client (UAC) Behavior: [EnableHistoryInfo]  Initial request: The History-Info header is equal to the Request-URI. If a PSTN Redirect number is received, it is added as an additional History-Info header with an appropriate reason.
Page 739 “Speech”, the INVITE in this case does not contain tgrp and trunk-context parameters. Note: IP-to-Tel configuration (using the PSTNPrefix parameter) overrides the 'tgrp' parameter in incoming INVITE messages. Web/EMS: TGRP Routing Determines the precedence method for routing IP-to-Tel calls - Version 6.8 Mediant 500 E-SBC...
Page 740: According To The Inbound Ip Routing Table
Mediant 500 E-SBC Parameter Description Precedence according to the Inbound IP Routing table or according to the SIP 'tgrp' CLI: tgrp-routing-prec parameter. [TGRProutingPrecedence]  [0] = (Default) IP-to-Tel routing is determined by the Inbound IP Routing table (PSTNPrefix parameter). If a matching rule is not found in this table, the device uses the Trunk Group parameters for routing the call.
Page 741 When configured, the string <UserAgentDisplayInfo 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: Version 6.8 Mediant 500 E-SBC...
Page 742 Mediant 500 E-SBC Parameter Description User-Agent: Audiocodes-Sip-Gateway-Mediant 500 E- SBC/v.6.80.010.006 The maximum string length is 50 characters. Note: The software version number and preceding forward slash (/) cannot be modified. Therefore, it is recommended not to include a forward slash in the parameter's value (to avoid two forward slashes in the SIP header, which may cause problems).
Page 743 SIP OPTIONS every keep-alive timeout to all proxies. If the device receives a SIP 503 response to an INVITE, it also marks that the proxy is out of service for the defined "Retry-After" period. Version 6.8 Mediant 500 E-SBC...
Page 744 Mediant 500 E-SBC Parameter Description Web/EMS: Enable P- Determines the device usage of the P-Associated-URI header. This Associated-URI Header header can be received in 200 OK responses to REGISTER requests. CLI: p-associated-uri-hdr When enabled, the first URI in the P-Associated-URI header is used in [EnablePAssociatedURIHe subsequent requests as the From/P-Asserted-Identity headers value.
Page 745 IP address, reflected in the From header of the SIP INVITE. Therefore, even customers blocking their Caller ID can be identified by the service provider. Typically, if the device receives a call with blocked Caller ID Version 6.8 Mediant 500 E-SBC...
Page 746 Mediant 500 E-SBC Parameter Description from the PSTN side (e.g., Trunk connected to a PBX), it sends an INVITE to the IP with a From header as follows: From: “anonymous” <anonymous@anonymous.invalid>. This is in accordance with RFC 3325. However, when this parameter is set to 1, the device replaces the "anonymous.invalid"...
Page 747 56. The payload type is negotiated with the remote side, i.e., the selected payload type is according to the remote side selection. The receiving device must include the 'Transparent' coder in its coder list. Web: IP to IP Application Enables the IP-to-IP Call Routing application. Version 6.8 Mediant 500 E-SBC...
Page 748 Mediant 500 E-SBC Parameter Description  CLI: enable-ip2ip [0] Disable (default) [EnableIP2IPApplication]  [1] Enable Note: For this parameter to take effect, a device reset is required. [IP2IPTranscodingMode] Note: This parameter is no longer valid and must not be used.
Page 749 ComfortNoiseNegotiation parameter and the codec’s SCE (silence suppression setting) using the CodersGroup parameter. If the ComfortNoiseNegotiation parameter is enabled, then the following occurs:  If the device is the initiator, it sends a “CN” in the SDP only if the Version 6.8 Mediant 500 E-SBC...
Page 750 Mediant 500 E-SBC Parameter Description SCE of the codec is enabled. If the remote UA responds with a “CN” in the SDP, then CNG occurs; otherwise, CNG does not occur.  If the device is the receiver and the remote SIP UA does not send a “CN”...
Page 751 Defines the Q.850 cause value specified in the SIP Reason header For VC that is included in a 4xx response when SIT-VC (Vacant Circuit - non- registered number Special Information Tone) is detected from the Version 6.8 Mediant 500 E-SBC...
Page 752 Mediant 500 E-SBC Parameter Description [SITQ850CauseForVC] PSTN for IP-to-Tel calls. The valid range is 0 to 127. The default is -1 (not configured). Note: When not configured (i.e., default), the SITQ850Cause parameter is used. Web/EMS: SIT Q850 Cause Defines the Q.850 cause value specified in the SIP Reason header...
Page 753 [DigitalOOSBehavior] DigitalOOSBehaviorForTrunk_x parameter. Notes:  This parameter is applicable only to digital interfaces.  To configure the method for setting Out-of-Service state per trunk, use the DigitalOOSBehaviorForTrunk_x parameter. Version 6.8 Mediant 500 E-SBC...
Page 754 Mediant 500 E-SBC Parameter Description  To configure the timeout interval (in seconds) for Out-of-Service graceful shutdown mode for busy trunks if communication fails with a Proxy server (or Proxy Set), use the GracefulBusyOutTimeout parameter. Retransmission Parameters Web: SIP T1...
Page 755: Coders And Profile Parameters
FORMAT CodersGroup0_Index = CodersGroup0_Name, [CodersGroup7] CodersGroup0_pTime, CodersGroup0_rate, [CodersGroup8] CodersGroup0_PayloadType, CodersGroup0_Sce; [CodersGroup9] CodersGroup0 0 = g711Alaw64k, 20, 0, 255, 0; CodersGroup0 1 = eg711Ulaw, 10, 0, 71, 0; CodersGroup0 2 = eg711Ulaw, 10, 0, 71, 0; [ \CodersGroup0 ] Version 6.8 Mediant 500 E-SBC...
Page 756 Mediant 500 E-SBC Parameter Description [ CodersGroup1 ] FORMAT CodersGroup1_Index = CodersGroup1_Name, CodersGroup1_pTime, CodersGroup1_rate, CodersGroup1_PayloadType, CodersGroup1_Sce; CodersGroup1 0 = Transparent, 20, 0, 56, 0; CodersGroup1 1 = g726, 20, 0, 23, 0; [ \CodersGroup1 ] Notes:  For a list of supported coders and a detailed description of this table, see Configuring Default Coders on page 293.
Page 757 TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP, TelProfile_TimeForReorderTone, TelProfile_EnableDIDWink, TelProfile_IsTwoStageDial, TelProfile_DisconnectOnBusyTone, TelProfile_EnableVoiceMailDelay, TelProfile_DialPlanIndex, TelProfile_Enable911PSAP, TelProfile_SwapTelToIpPhoneNumbers, TelProfile_EnableAGC, TelProfile_ECNlpMode, TelProfile_DigitalCutThrough, TelProfile_EnableFXODoubleAnswer, TelProfile_CallPriorityMode; [\TelProfile] For a description of this parameter, see Configuring Tel Profiles on page 297. Version 6.8 Mediant 500 E-SBC...
Page 758: Channel Parameters
Mediant 500 E-SBC 53.9 Channel Parameters This subsection describes the device's channel parameters. 53.9.1 Voice Parameters The voice parameters are described in the table below. Table 53-34: Voice Parameters Parameter Description Web/EMS: Input Gain Global parameter that defines the pulse-code modulation CLI: input-gain (PCM) input (received) gain control level (in decibels).
Page 759 The valid values are [0] (default), [4], [6], [8] and [10]. Answer Detector (AD) Parameters Web: Enable Answer Detector Currently, not supported. [EnableAnswerDetector] Web: Answer Detector Activity Delay Defines the time (in 100-msec resolution) between Version 6.8 Mediant 500 E-SBC...
Page 760: Coder Parameters
Mediant 500 E-SBC Parameter Description CLI: answer-detector-activativity-delay activating the Answer Detector and the time that the [AnswerDetectorActivityDelay] detector actually starts to operate. The valid range is 0 to 1023. The default is 0. Web: Answer Detector Silence Time Currently, not supported.
Page 761: Dtmf Parameters
Defines the Voice Silence time (in msec) after detecting the end of Over Time (msec) DTMF or MF digits at the Tel/PSTN side when the DTMF Transport CLI: digit-hangover-time-tx Type is either Relay or Mute. Version 6.8 Mediant 500 E-SBC...
Page 762: Rtp, Rtcp And T.38 Parameters
Mediant 500 E-SBC Parameter Description [TxDTMFHangOverTime] Valid range is 0 to 2,000 msec. The default is 1,000 msec. 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 763 RTP packets), then it sends RTP packets to this MAC address and removes this IP entry from the device's ARP cache table.  [2] = (Default) The device uses the received GARP packets to change the MAC address of the transmitted RTP Version 6.8 Mediant 500 E-SBC...
Page 764 Mediant 500 E-SBC Parameter Description packets.  [3] = Options 1 and 2 are used. Notes:  For this parameter to take effect, a device reset is required.  If the device is located in a network subnet which is...
Page 765 The valid value range is 0 to 65,535. The default is 5,000. Web: Disable RTCP XR Interval Determines whether RTCP report intervals are randomized or Randomization whether each report interval accords exactly to the parameter EMS: Disable Interval RTCPInterval. Randomization Version 6.8 Mediant 500 E-SBC...
Page 766 Mediant 500 E-SBC Parameter Description  CLI: disable-RTCP-randomization [0] Disable = (Default) Randomize [DisableRTCPRandomize]  [1] Enable = No Randomize EMS: RTCP XR Collection Server Defines the transport layer used for outgoing SIP dialogs Transport Type initiated by the device to the RTCP XR Collection Server.
Page 767: Gateway And Ip-To-Ip Parameters
Note: You can also configure this functionality per specific calls, using IP Profiles (IpProfile_VxxTransportType). For more information, see ''Configuring IP Profiles'' on page 300. Web: V.32 Modem Transport Type Determines the V.32 modem transport type. Version 6.8 Mediant 500 E-SBC...
Page 768 Mediant 500 E-SBC Parameter Description  EMS: V32 Transport [0] Disable = Transparent. CLI: V32-modem-transport-type  [2] Enable Bypass (default) [V32ModemTransportType]  [3] Events Only = Transparent with Events. Notes:  This parameter applies only to V.32 and V.32bis modems.
Page 769 [11] 28800bps = 28.8 kbps  [12] 31200bps = 31.2 kbps  [13] 33600bps = 33.6 kbps Notes:  The rate is negotiated between both sides (i.e., the device adapts to the capabilities of the remote side). Negotiation of Version 6.8 Mediant 500 E-SBC...
Page 770 Mediant 500 E-SBC Parameter Description the T.38 maximum supported fax data rate is provided in SIP’s SDP T38MaxBitRate parameter. The negotiated 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.
Page 771 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 500 E-SBC...
Page 772 Mediant 500 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. The default is 560.
Page 773 [V1501SPRTTransportChannel2M axWindowSize] 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 500 E-SBC...
Page 774: Dtmf And Hook-Flash Parameters
Mediant 500 E-SBC 53.10.2 DTMF and Hook-Flash Parameters The DTMF and hook-flash parameters are described in the table below. Table 53-39: DTMF and Hook-Flash Parameters Parameter Description Hook-Flash Parameters Web/EMS: Hook-Flash Code For digital interfaces: Defines the digit pattern used by the PBX CLI: hook-flash-code to indicate a Hook Flash event.
Page 775 SDPs. Sends DTMF packets using RFC 2833 payload type according to the payload type in the received SDP. Expects to receive RFC 2833 packets with the same payload type as configured by the parameter RFC2833PayloadType. Version 6.8 Mediant 500 E-SBC...
Page 776 Mediant 500 E-SBC Parameter Description Removes DTMF digits in transparent mode (as part of the voice stream).  When TxDTMFOption is set to 0, the RFC 2833 payload type is set according to the parameter RFC2833PayloadType for both transmit and receive.
Page 777: Digit Collection And Dial Plan Parameters
The valid value range is 0 to 7, defining the Dial Plan index [Plan x] ngDialPlanIndex] in the Dial Plan file. The default is -1 (disabled). For more information on this feature, see ''Modifying ISDN-to-IP Version 6.8 Mediant 500 E-SBC...
Page 778 Mediant 500 E-SBC Parameter Description Calling Party Number'' on page 550. Web: Digit Mapping Rules Defines the digit map pattern (used to reduce the dialing period when EMS: Digit Map Pat terns ISDN overlap dialing for digital interfaces). If the digit string (i.e.,...
Page 779: Voice Mail Parameters
Redirect number reason to the SIP 'cause' parameter in the Request-URI. Redirecting Reason >> SIP Response Code Unknown >> 404 User busy >> 486 No reply >> 408 Deflection >> 487/480 Unconditional >> 302 Version 6.8 Mediant 500 E-SBC...
Page 780 Mediant 500 E-SBC Parameter Description Others >> 302 If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason.
Page 781 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... Version 6.8 Mediant 500 E-SBC...
Page 782 Mediant 500 E-SBC Parameter Description Note: If this parameter is not configured, the MWI SUBSCRIBE 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.
Page 783 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 500 E-SBC...
Page 784: Supplementary Services Parameters
Mediant 500 E-SBC 53.10.5 Supplementary Services Parameters This subsection describes the device's supplementary telephony services parameters. 53.10.5.1 Caller ID Parameters The caller ID parameters are described in the table below. Table 53-42: Caller ID Parameters Parameter Description Web/EMS: Enable Caller ID Global parameter that enables Caller ID.
Page 785: Call Waiting Parameters
The call forwarding parameters are described in the table below. Table 53-44: Call Forwarding Parameters Parameter Description Web: Enable Call Enables the Call Forwarding feature. Forward  [0] Disable CLI: call-forward  [1] Enable (Default) [EnableForward] Notes: Version 6.8 Mediant 500 E-SBC...
Page 786: Call Hold Parameters
Mediant 500 E-SBC Parameter Description  To use this service, the devices at both ends must support this option.  For the device to respond to SIP 3xx responses with a new SIP request (forwarding the original request), set this parameter to Enable.
Page 787: Call Transfer Parameters
After the KeyBlindTransfer DTMF digits sequence is dialed, the current call is put on hold (using a Re-INVITE message), a dial tone is played to the channel, and then the phone number Version 6.8 Mediant 500 E-SBC...
Page 788 Mediant 500 E-SBC Parameter Description collection starts. After the destination phone number is collected, it is sent to the transferee in a SIP REFER request in a Refer-To header. The call is then terminated and a confirmation tone is played to the channel.
Page 789: Mlpp And Emergency Call Parameters
Defines the maximum interval within which the PSAP can use the ELIN to call back the E9-1-1 caller. This interval starts from when the initial call established with the PSAP is terminated. The valid range is 1 to 60 (minutes). The default is 30. Version 6.8 Mediant 500 E-SBC...
Page 790 Mediant 500 E-SBC Parameter Description Web: Emergency Special Release Enables the device to send a SIP 503 "Service Unavailable" Cause response if an emergency call cannot be established (i.e., CLI: emrg-spcl-rel-cse rejected). This can occur, for example, due to the PSTN (for...
Page 791 (if different from ‘FFFFFF’) as a Service domain in CLI: mlpp-norm-ser-dmn the SIP Resource-Priority header in outgoing INVITE messages. [MLPPNormalizedServiceDomain] If the parameter is configured to ‘FFFFFF’, the Resource-Priority header is set to the MLPP Service Domain obtained from the Version 6.8 Mediant 500 E-SBC...
Page 792 Mediant 500 E-SBC Parameter Description Precedence IE. The valid value is 6 hexadecimal digits. The default is ‘000000’. Note: This parameter is applicable only to the MLPP NI-2 ISDN variant with CallPriorityMode set to 1. CLI: mlpp-nwrk-id Defines the MLPP network identifier (i.e., International prefix or...
Page 793 CLI: dscp-4-mlpp-flsh-ov-ov The valid range is -1 to 63. The default is -1. [MLPPFlashOverOverRTPDSCP] Note: If set to -1, the DiffServ value is taken from the global parameter PremiumServiceClassMediaDiffServ or as defined in Version 6.8 Mediant 500 E-SBC...
Page 794: Call Cut-Through Parameters
Mediant 500 E-SBC Parameter Description IP Profiles per call. 53.10.5.7 Call Cut-Through Parameters The call cut-through parameters are described in the table below. Table 53-48: Call Cut-Through Parameters Parameter Description CLI: cut-through-anable Enables PSTN CAS channels/endpoints to receive incoming IP calls even [DigitalCutThrough] if the B-channels are in off-hook state.
Page 795: Pstn Parameters
[15] J1 TRANSPARENT  [16] T1 NTT ISDN = ISDN PRI protocol for the Japan - Nippon Telegraph Telephone (known also as INS 1500).  [17] E1 AUSTEL ISDN = ISDN PRI protocol for the Australian Version 6.8 Mediant 500 E-SBC...
Page 796 Mediant 500 E-SBC Parameter Description Telecom.  [18] E1 HKT ISDN = ISDN PRI (E1) protocol for the Hong Kong - HKT.  [19] E1 KOR ISDN = ISDN PRI protocol for Korean Operator (similar to ETSI).  [20] T1 HKT ISDN = ISDN PRI (T1) protocol for the Hong Kong - HKT.
Page 797 [F] T1 FRAMING ESF CRC6 J2 = J1 Extended SuperFrame with CRC6 (Japan) Same as the description for parameter FramingMethod, but for a [FramingMethod_x] specific trunk ID (where x denotes the Trunk ID and 0 is the first Trunk). Version 6.8 Mediant 500 E-SBC...
Page 798 Mediant 500 E-SBC Parameter Description Web/EMS: Clock Master Determines the Tx clock source of the E1/T1 line. CLI: clock-master  [0] Recovered = (Default) Generate the clock according to the [ClockMaster] Rx of the E1/T1 line.  [1] Generated = Generate the clock according to the internal TDM bus.
Page 799 (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 500 E-SBC...
Page 800: Tdm Bus And Clock Timing Parameters
Mediant 500 E-SBC 53.10.6.2 TDM Bus and Clock Timing Parameters The TDM Bus parameters are described in the table below. Table 53-50: 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 801 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 500 E-SBC...
Page 802: Cas Parameters
Mediant 500 E-SBC 53.10.6.3 CAS Parameters The Common Channel Associated (CAS) parameters are described in the table below. Table 53-51: CAS Parameters Parameter Description Web: CAS Transport Type Determines the ABCD signaling transport type over IP. EMS: CAS Relay Transport Mode ...
Page 803 To configure this parameter, the trunk must first be stopped.  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 500 E-SBC...
Page 804 Mediant 500 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 333.
Page 805: Isdn Parameters
PI = 1 or PI = 3 in the Setup message.  [0] = PI is not added (default).  [1] = PI 1 is added to a sent ISDN Setup message - call is not end-to-end ISDN. Version 6.8 Mediant 500 E-SBC...
Page 806 Mediant 500 E-SBC Parameter Description  [3] = PI 3 is added to a sent ISDN Setup message - calling equipment is not ISDN. NFAS Parameters Note: These parameters are applicable to PRI interfaces. Web: NFAS Group Number Defines the ISDN Non-Facility Associated Signaling (NFAS) EMS: Group Number group number (NFAS member), per trunk.
Page 807 ISDNInCallsBehavior, but per trunk (i.e., where x denotes the Trunk ID). Web/EMS: Q.931 Layer Response Bit-field used to determine several behavior options that Behavior influence the behaviour of the Q.931 protocol. CLI: isdn-bits-ns-behavior  [0] = Disable (default). Version 6.8 Mediant 500 E-SBC...
Page 808 Mediant 500 E-SBC Parameter Description  [ISDNIBehavior] [1] NO STATUS ON UNKNOWN IE = Q.931 Status message isn't sent if Q.931 received message contains an unknown/unrecognized IE. By default, the Status message is sent. Note: This value is applicable only to ISDN variants in which sending of Status message is optional.
Page 809 #16. When this bit is set, the channel ID #16 is considered as a valid B-channel ID, but timeslot values are converted to reflect the range 1 to 15 and 17 to 31. Version 6.8 Mediant 500 E-SBC...
Page 810 Mediant 500 E-SBC Parameter Description This is the new QSIG mode of operation. When this bit is not set (default), the channel_id #16 is not allowed, as for all ETSI-like standards.  [64] USE T1 PRI = PRI interface type is forced to T1.
Page 811 [64] NS BEHAVIOUR2 FAC REJECT = When this bit is set, the device answers with a Facility IE message with the Reject component on receipt of Facility IE with unknown/invalid Invoke component. This bit is implemented in QSIG and ETSI variants. Version 6.8 Mediant 500 E-SBC...
Page 812: Isdn And Cas Interworking Parameters
Mediant 500 E-SBC Parameter Description [PSTNExtendedParams] Determines the bit map for special PSTN behavior parameters:  [0] = (Default) Applicable for NI-2 ISDN and QSIG "Networking Extensions". This bit (i.e., bit #0) is responsible for the Invoke ID size: ...
Page 813 ISDN overlap receiving, the device does not release the call.  The MaxDigits parameter can be used to limit the length of the collected number for ISDN overlap dialing (if Sending Complete Version 6.8 Mediant 500 E-SBC...
Page 814 Mediant 500 E-SBC Parameter Description is not received).  If a digit map pattern is defined (using the DigitMapping or DialPlanIndex parameters), the device collects digits until a match is found (e.g., for closed numbering schemes) or until a timer expires (e.g., for open numbering schemes). If a match is found (or the timer expires), the digit collection process is terminated even if Sending Complete is not received.
Page 815 [EnableHold2ISDN]  [1] Enable Notes:  This parameter is applicable to Euro ISDN variants - from TE (user) to NT (network).  If the parameter is disabled, the device plays a held tone to the Version 6.8 Mediant 500 E-SBC...
Page 816 Mediant 500 E-SBC Parameter Description Tel side when a SIP request with 0.0.0.0 or "inactive" in SDP is received. An appropriate CPT file with the held tone should be used. EMS: Duplicate Q931 Buff Determines the activation/deactivation of delivering raw Q.931 Mode messages.
Page 817 From or P-Asserted-Identity headers. For example, the 'cpc=' parameter in the below INVITE message is set to "payphone": INVITE sip:bob@biloxi.example.com SIP/2.0 To: "Bob" <sip:bob@biloxi.example.com> From: <tel:+17005554141;cpc=payphone>;tag=1928301774 The table below shows the mapping of CPC between SIP and Version 6.8 Mediant 500 E-SBC...
Page 818 Mediant 500 E-SBC Parameter Description PSTN: SIP CPC NI-2 PRI MFC-R2 Argentina Brazil ordinary II-1 II-1 priority II-2 II-2 data II-6 II-6 test II-3 II-3 operator II-5 II-5 payphone II-4 II-7 unknown II-1 II-1 subscriber II-1 cellular II-13 locutorio II-11...
Page 819 [1] PI = 1; [8] PI = 8: The PI value is sent to PSTN in Q.931/Proceeding and Alerting messages. Typically, the PSTN/PBX cuts through the audio channel without playing local ringback tone, enabling the originating party to hear remote Call Progress Tones or network announcements. Version 6.8 Mediant 500 E-SBC...
Page 820 Mediant 500 E-SBC Parameter Description Note: The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Web: Set PI in Rx Disconnect Defines the device's behavior per trunk when a Disconnect Message message is received from the ISDN before a Connect message is EMS: Set PI For Disconnect received.
Page 821  The parameter AddCicAsPrefix can be used to add the CIC as a prefix to the destination phone number for routing IP-to-Tel calls. Web/EMS: AoC Support Enables the interworking of ISDN Advice of Charge (AOC) Version 6.8 Mediant 500 E-SBC...
Page 822 Mediant 500 E-SBC Parameter Description [EnableAOC] messages to SIP.  [0] Disable (default)  [1] Enable For more information on AOC, see ''Advice of Charge Services for Euro ISDN'' on page 429. Web: IPMedia Detectors Enables the device's DSP detectors.
Page 823 T1 QSIG [23] Replacement Transfer [2], or InBand [5] T1 NI2 ISDN [10], TBCT [2] or InBand [5] T1 4ESS ISDN [11], T1 5ESS 9 ISDN [12] T1 DMS-100 ISDN [14] RTL [2] or InBand [5] Version 6.8 Mediant 500 E-SBC...
Page 824 Mediant 500 E-SBC Parameter Description T1 RAW CAS [3], T1 [1] CAS NFA DMS-100 or [3] CAS CAS [2], E1 CAS [8], Normal transfer E1 RAW CAS [9] T1 DMS-100 Meridian RTL [2] or InBand [5] ISDN [35] The valid values of this parameter are described below: ...
Page 825 CLI: isdn-xfer-cab  [1] Speech [ISDNTransferCapability_x]  [2] Data Notes:  If this parameter is not configured or is set to -1, Audio 3.1 capability is used.  The Audio 7 option is currently not supported. Version 6.8 Mediant 500 E-SBC...
Page 826 Mediant 500 E-SBC Parameter Description  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. [TransferCapabilityForDataC Defines the ISDN Transfer Capability for data calls. alls]  [0] = (Default) ISDN Transfer Capability for data calls is 64k unrestricted (data).
Page 827 CLI: configure voip > gw FORMAT CauseMapISDN2SIP_Index = manipulations CauseMapISDN2SIP_IsdnReleaseCause, CauseMapIsdn2Sip CauseMapISDN2SIP_SipResponse; [CauseMapISDN2SIP] [\CauseMapISDN2SIP] Release Cause Mapping from SIP to ISDN Table Web: Release Cause Mapping This table parameter maps SIP responses to Q.850 Release Version 6.8 Mediant 500 E-SBC...
Page 828: Answer And Disconnect Supervision Parameters
Mediant 500 E-SBC Parameter Description Table 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] 53.10.8 Answer and Disconnect Supervision Parameters The answer and disconnect supervision parameters are described in the table below.
Page 829 Determines the silence detection method. [FarEndDisconnectSilenceMeth  [0] None = Silence detection option is disabled.  [1] Packets Count = According to packet count. Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 500 E-SBC...
Page 830 Mediant 500 E-SBC Parameter Description [FarEndDisconnectSilenceThre Defines the threshold of the packet count (in percentages) below shold] which is considered silence by the device. The valid range is 1 to 100%. The default is 8%. Notes:  This parameter is applicable only if silence is detected according to packet count (FarEndDisconnectSilenceMethod is set to 1).
Page 831: Tone Parameters
Web: Play Busy Tone to Tel Enables the device to play a busy or reorder tone to the PSTN after CLI: play-bsy-tone-2tel a Tel-to-IP call is released. [PlayBusyTone2ISDN]  [0] Don't Play = (Default) Immediately sends an ISDN Version 6.8 Mediant 500 E-SBC...
Page 832 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 833 LocalISDNRBSource parameter is set to 1. Note: This parameter is applicable to the Gateway and IP-to-IP applications. Web: Play Ringback Tone to Determines the playing method of the ringback tone to the trunk Version 6.8 Mediant 500 E-SBC...
Page 834 Mediant 500 E-SBC Parameter Description Trunk side, per trunk. CLI: play-rbt-to-trk  [-1] Not configured = (Default) The settings of the [PlayRBTone2Trunk_x] PlayRBTone2Tel parameter is used.  [0] Don't Play = When the device is configured for ISDN / CAS, it doesn't play a ringback tone.
Page 835 CLI: mfcr2-category National or International call, Operator or Subscriber and [R2Category] Subscriber priority. The value range is 1 to 15 (defining one of the MFC R2 tones). The default is 1. Version 6.8 Mediant 500 E-SBC...
Page 836: Tone Detection Parameters
Mediant 500 E-SBC 53.10.9.2 Tone Detection Parameters The signal tone detection parameters are described in the table below. Table 53-56: Tone Detection Parameters Parameter Description EMS: DTMF Enable Enables the detection of DTMF signaling. CLI: DTMF-detector-enable  [0] = Disable [DTMFDetectorEnable] ...
Page 837: Metering Tone Parameters
AOC-E. Parsing every AOC-D received and summing the values is required to obtain the total sum (that is placed in the AOC-E). Note: This parameter is applicable only to ISDN Euro trunks for sending Version 6.8 Mediant 500 E-SBC...
Page 838: Trunk Groups And Routing Parameters
Mediant 500 E-SBC Parameter Description AOC Facility messages (see Advice of Charge Services for Euro ISDN on page 429). Charge Codes Table Web: Charge Codes Table This table parameter configures metering tones and their time intervals EMS: Charge Codes that the E1 trunk (Euro ISDN) sends in AOC Facility messages to the CLI: configure voip >...
Page 839 Trunk Groups. The default is 1000. Web: Source IP Address Input Determines which IP address the device uses to determine CLI: src-ip-addr-input the source of incoming INVITE messages for IP-to-Tel Version 6.8 Mediant 500 E-SBC...
Page 840 Mediant 500 E-SBC Parameter Description [SourceIPAddressInput] routing.  [-1] = (Default) Auto Decision - if the IP-to-IP feature is enabled, this parameter is automatically set to Layer 3 Source IP. If the IP-to-IP feature is disabled, this parameter is automatically set to SIP Contact Header (1).
Page 841: [Prefix_Srcipgroupid]
PstnPrefix_CallSetupRulesSetId; [\PSTNPrefix] For a detailed description of this table, see ''Configuring Inbound IP Routing Table'' on page 388. Web/EMS: IP to Tel Routing Mode Determines whether to route IP calls to the Trunk Group (or Version 6.8 Mediant 500 E-SBC...
Page 842 Mediant 500 E-SBC Parameter Description CLI: ip2tel-rte-mode IP Group) before or after manipulation of the destination [RouteModeIP2Tel] number (configured in ''Configuring Source/Destination Number Manipulation Rules'' on page 355).  [0] Route calls before manipulation = (Default) Calls are routed before the number manipulation rules are applied.
Page 843 Enables re-routing of Tel-to-IP calls that are identified as fax calls. If a CNG tone is detected on the Tel side of a Tel-to-IP call, the prefix string "FAX" is appended to the destination number before routing and manipulation. If you enter the Version 6.8 Mediant 500 E-SBC...
Page 844 Mediant 500 E-SBC Parameter Description string value, "FAX" as the destination number in the Outbound IP Routing table, the routing rule is used to route the call and the destination number manipulation mechanism is used to remove the "FAX" prefix, if required. Note that the "FAX"...
Page 845 INVITE messages to the other members of the forking invite group. The INVITE is immediately sent to the first member. [ForkingDelayTimeForInvite] The valid value range is 0 to 40. The default is 0 (i.e., send immediately). Version 6.8 Mediant 500 E-SBC...
Page 846: Ip Connectivity Parameters
Mediant 500 E-SBC 53.10.11 IP Connectivity Parameters The IP connectivity parameters are described in the table below. Table 53-59: IP Connectivity Parameters Parameter Description Web: Enable Alt Routing Tel to IP Enables the Alternative Routing feature for Tel-to-IP calls. EMS: Enable Alternative Routing ...
Page 847: Alternative Routing Parameters
Defines when the device sends the IP-to-Tel call to an alternative route (if configured) when it receives an ISDN Q.931 Disconnect message from the Tel side.  [0] (Default) = The device forwards early media to the IP side if Version 6.8 Mediant 500 E-SBC...
Page 848 Mediant 500 E-SBC Parameter Description Disconnect includes PI, and disconnects the call when a Release message is received. Only after the call is disconnected does the device send the call to an alternative route.  [1] = The device immediately sends the call to the alternative route.
Page 849: Number Manipulation Parameters
This source number can also be used as the value for the 'Source Prefix' field in the IP-to-Tel Destination Phone Number Manipulation table. The local IP address is used as the value for the 'Source IP Address' field. Version 6.8 Mediant 500 E-SBC...
Page 850 Mediant 500 E-SBC Parameter Description Note: This manipulation does not affect IP-to-Trunk Group routing rules. Web: Use EndPoint Number 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.
Page 851 EMS: Screening Indicator To  [-1] Not Configured = (Default) Not configured (interworking from ISDN IP to ISDN). [ScreeningInd2ISDN]  [0] User Provided = user provided, not screened.  [1] User Passed = user provided, verified and passed. Version 6.8 Mediant 500 E-SBC...
Page 852 Mediant 500 E-SBC Parameter Description  [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)
Page 853 [1] Yes = Add NPI and TON to the Called Number of ISDN Tel-to- CLI: npi-n-ton-to-cld-nb IP call. [AddNPIandTON2CalledNumb For example: After receiving a Called Number of 555, NPI of 1 and TON of 3, the modified number becomes 13555. This number can Version 6.8 Mediant 500 E-SBC...
Page 854 Mediant 500 E-SBC Parameter Description later be used for manipulation and routing. Web: Add NPI and TON to Determines whether the NPI and TON values are added as the prefix Redirect Number to the Redirect number in INVITE messages' Diversion or History- CLI: np-n-ton-2-redirnb Info headers, for ISDN Tel-to-IP calls.
Page 855 This table parameter configures rules for manipulating the calling manipulations calling-name- name (caller ID) for Tel-to-IP calls. This can include modifying or map-tel2ip removing the calling name. [CallingNameMapTel2Ip] [ CallingNameMapTel2Ip ] FORMAT CallingNameMapTel2Ip_Index = CallingNameMapTel2Ip_ManipulationName, CallingNameMapTel2Ip_DestinationPrefix, CallingNameMapTel2Ip_SourcePrefix, CallingNameMapTel2Ip_CallingNamePrefix, CallingNameMapTel2Ip_SrcTrunkGroupID, CallingNameMapTel2Ip_SrcIPGroupID, CallingNameMapTel2Ip_RemoveFromLeft, CallingNameMapTel2Ip_RemoveFromRight, CallingNameMapTel2Ip_LeaveFromRight, Version 6.8 Mediant 500 E-SBC...
Page 856 Mediant 500 E-SBC Parameter Description CallingNameMapTel2Ip_Prefix2Add, CallingNameMapTel2Ip_Suffix2Add; [ \CallingNameMapTel2Ip ] For a detailed description of this table, see ''Configuring SIP Calling Name Manipulation'' on page 362. Destination Phone Number Manipulation for IP-to-Tel Calls Table Web: Destination Phone This table parameter manipulates the destination number of IP-to-Tel Number Manipulation Table calls.
Page 857 [\SourceNumberMapTel2Ip] For a detailed description of this table, see ''Configuring Source/Destination Number Manipulation'' on page 355. Redirect Number IP -to-Tel Table Web: Redirect Number IP -> This table parameter manipulates the redirect number for IP-to-Tel Version 6.8 Mediant 500 E-SBC...
Page 858 Mediant 500 E-SBC Parameter Description calls. EMS: Redirect Number Map The format of the ini file table parameter is as follows: IP to Tel [RedirectNumberMapIp2Tel] CLI: configure voip > gw FORMAT RedirectNumberMapIp2Tel_Index = manipulations redirect- RedirectNumberMapIp2Tel_ManipulationName, number-map-ip2tel RedirectNumberMapIp2Tel_DestinationPrefix, [RedirectNumberMapIp2Tel] RedirectNumberMapIp2Tel_RedirectPrefix,...
Page 859 Determines whether the received Phone-Context parameter is added Context As Prefix as a prefix to the outgoing ISDN Setup message with (for digital CLI: add-ph-cntxt-as-pref interfaces) Called and Calling numbers. [AddPhoneContextAsPrefix]  [0] Disable (default)  [1] Enable Version 6.8 Mediant 500 E-SBC...
Page 860: Sbc Parameters
Mediant 500 E-SBC 53.11 SBC Parameters The SBC and CRP parameters are described in the table below. Table 53-62: SBC and CRP Parameters Parameter Description CRP-specific Parameters Web: CRP Application Enables the CRP application. EMS: Enable CPR Application  [0] Disable (default) CLI: enable-crp ...
Page 861 If the received header’s original value is less than this parameter's value, the header’s value is decremented before being sent on.  If the received header’s original value is greater than the parameter's value, the header’s value is replaced by the user-defined parameter’s value. Version 6.8 Mediant 500 E-SBC...
Page 862 Mediant 500 E-SBC Parameter Description The valid value range is 1-70. The default is 10. Web: SBC Session-Expires Defines the SBC session refresh timer (in seconds) in the CLI: sbc-sess-exp-time Session-Expires header of outgoing INVITE messages. [SBCSessionExpires] The valid value range is 90 (according to RFC 4028) to 86400.
Page 863 IP Profile. [SBCEnforceMediaOrder] Enables the device to include all previously negotiated media lines within the current session ('m=' line) in the SDP offer- Version 6.8 Mediant 500 E-SBC...
Page 864 Mediant 500 E-SBC Parameter Description answer exchange (RFC 3264).  [0] Disable (default)  [1] Enable For example, assume a call (audio) has been established between two endpoints and one endpoint wants to subsequently send an image in the same call session. If this parameter is enabled, the endpoint includes the previously negotiated media type (i.e., audio) with the new negotiated media type (i.e.,...
Page 865 SIP 200 OK response before forwarding it to the user; otherwise, the device does not change the expiry time. This feature is useful in scenarios where multiple users may refresh their registration or subscription simultaneously, thereby Version 6.8 Mediant 500 E-SBC...
Page 866 Mediant 500 E-SBC Parameter Description causing the device to handle many such sessions at a given time. This may result in an overload of the device (reaching maximum session capacity), thereby preventing the establishment of new calls or preventing the handling of some user registration or subscription requests.
Page 867 The device creates a GRUU value for each of its registered clients, which is mapped to the GRUU value received from the Proxy server. In other words, the created GRUU value is only used between the device and its clients (endpoints). Public-GRUU: sip:userA@domain.com;gr=unique- Version 6.8 Mediant 500 E-SBC...
Page 868 Mediant 500 E-SBC Parameter Description Web: Bye Authentication Enables authenticating a SIP BYE request before disconnecting CLI: sbc-bye-auth the call. This feature prevents, for example, a scenario in which [SBCEnableByeAuthentication] the SBC SIP client receives a BYE request from a third-party...
Page 869 SIP forking that is initiated by external proxy servers. It is possible that a call is established with the media not synchronized between the SBC legs. Media synchronization resolves this issue.  [0] Disable  [1] Enable (default) Admission Control Table Version 6.8 Mediant 500 E-SBC...
Page 870 Mediant 500 E-SBC Parameter Description Web: Admission Control This table parameter defines Call Admission Control (CAC) EMS: Call Admission Control rules for limiting the number of allowed concurrent calls (SIP CLI: configure voip > sbc sbc- dialogs). admission-control The format of the ini file table parameter is as follows:...
Page 871 CLI: configure voip > sbc routing [ SBCAlternativeRoutingReasons ] sbc-alternative-routing-reasons FORMAT SBCAlternativeRoutingReasons_Index = [SBCAlternativeRoutingReasons SBCAlternativeRoutingReasons_ReleaseCause; [ \SBCAlternativeRoutingReasons ] For a detailed description of this table, see ''Configuring SIP Response Codes for Alternative Routing Reasons'' on page 486. Version 6.8 Mediant 500 E-SBC...
Page 872 Mediant 500 E-SBC Parameter Description IP to IP Inbound Manipulation Table Web: IP to IP Inbound This table parameter configures the IP to IP Inbound Manipulation Manipulation table. This table allows you to manipulate the SIP EMS: IP to IP Inbound...
Page 873: Standalone Survivability Parameters
The valid range is 1 to 65,534. The default is 5081. Web: SAS Connection Reuse Enables the re-use of the same TCP connection for sessions CLI: sas-connection-reuse with the same user in the SAS application. Version 6.8 Mediant 500 E-SBC...
Page 874 Mediant 500 E-SBC Parameter Description  [SASConnectionReuse] [0] Disable  [1] Enable (default) The device can use the same TCP connection for multiple SIP requests / responses for a specific SIP UA. For example, assume the following:  User A sends a REGISTER message to SAS with transport=TCP.
Page 875 CLI: sasbindingmode requests is using a ‘tel:’ URI or ‘user=phone’ is defined, the [SASBindingMode] binding is performed according to the user part of the URI only. Otherwise, the binding is according to the entire URI, Version 6.8 Mediant 500 E-SBC...
Page 876 Mediant 500 E-SBC Parameter Description i.e., User@Host.  [1] User Part only = The binding is always performed according to the User Part only. Web: SAS Emergency Numbers Defines emergency numbers for the device's SAS application. CLI: sas-emerg-nb When the device's SAS agent receives a SIP INVITE (from an IP...
Page 877: Ip Media Parameters
NetAnn interface. The application server sends a regular SIP INVITE message with a SIP URI that includes this identifier string and a “play=” parameter that identifies the necessary announcement. The default is ‘annc’. Version 6.8 Mediant 500 E-SBC...
Page 878 Mediant 500 E-SBC Parameter Description Example 1: INVITE sip: annc@10.2.3.4;play=http://localhost/1. Example 2: INVITE sip: annc@10.2.3.4;play=http://10.2.3.4/Annc/ello.wav. Web: Transcoding ID Defines the Transcoding identification string (up to 16 [TranscodingID] characters) used for identifying an incoming Transcoding call. The default is ‘trans’. For more information on Transcoding, see NetAnn Interface.
Page 879 Defines the minimum gain (in dB) by the AGC when activated. EMS: Minimal Gain The range is 0 to -31. The default is -20. CLI: AGC-min-gain Note: For this parameter to take effect, a device reset is Version 6.8 Mediant 500 E-SBC...
Page 880 Mediant 500 E-SBC Parameter Description [AGCMinGain] required. Web: AGC Maximum Gain Defines the maximum gain (in dB) by the AGC when activated. EMS: Maximal Gain The range is 0 to 18. The default is 15. CLI: AGC-max-gain Note: For this parameter to take effect, a device reset is [AGCMaxGain] required.
Page 881: Services
[ SIPRecRouting ] recording sip-rec-routing FORMAT SIPRecRouting_Index = [SIPRecRouting] SIPRecRouting_RecordedIPGroupID, SIPRecRouting_RecordedSourcePrefix, SIPRecRouting_RecordedDestinationPrefix, SIPRecRouting_PeerIPGroupID, SIPRecRouting_PeerTrunkGroupID, SIPRecRouting_Caller, SIPRecRouting_SRSIPGroupID; [ \SIPRecRouting ] For a detailed description of this table, see ''Configuring SIP Recording Routing Rules'' on page 194. Version 6.8 Mediant 500 E-SBC...
Page 882: Radius And Ldap Parameters
Mediant 500 E-SBC 53.14.2 RADIUS and LDAP Parameters 53.14.2.1 General Parameters The general RADIUS and LDAP parameters are described in the table below. General RADIUS and LDAP Parameters Parameter Description Web: Use Local Users Defines when the device uses its local user database (Web Users...
Page 883 Server Port CLI: auth-server-port [RADIUSAuthPort] Web: RADIUS Shared Defines the 'secret' used to authenticate the device to the RADIUS Secret server. This should be a cryptically strong password. EMS: RADIUS Auth Server Secret CLI: shared-secret [SharedSecret] Version 6.8 Mediant 500 E-SBC...
Page 884: Ldap Parameters
Mediant 500 E-SBC Parameter Description RADIUS Authentication Parameters Web: Password Local Defines the device's mode of operation regarding the timer (configured Cache Mode by the parameter RadiusLocalCacheTimeout) that determines the CLI: local-cache-mode validity of the username and password (verified by the RADIUS server).
Page 885 Defines the name of the attribute that represents the user Mobile Number attribute name number in the Microsoft AD database. CLI: ldap-mobile-nm-attr The valid value is a string of up to 49 characters. The default is [MSLDAPMobileNumAttri "mobile". buteName] Version 6.8 Mediant 500 E-SBC...
Page 886 Mediant 500 E-SBC Parameter Description CLI: ldap-private-nm-attr Defines the name of the attribute that represents the user's private [MSLDAPPrivateNumAttri number in the AD. If this value equals the value of the buteName] MSLDAPPrimaryKey or MSLDAPSecondaryKey parameter, then the device queries the AD for the destination number in this private attribute name;...
Page 887: Least Cost Routing Parameters
Configuring Default LCR'' on page 226. Web: Cost Group Table This table parameter configures the Cost Groups for LCR, where each EMS: Cost Group Cost Group is configured with a name, fixed call connection charge, Version 6.8 Mediant 500 E-SBC...
Page 888: Call Setup Rules Parameters
Mediant 500 E-SBC Parameter Description Provisioning > Cost Group and a call rate (charge per minute). CLI: configure voip > [ CostGroupTable ] services least-cost-routing FORMAT CostGroupTable_Index = cost-group CostGroupTable_CostGroupName, [CostGroupTable] CostGroupTable_DefaultConnectionCost, CostGroupTable_DefaultMinuteCost; [ \CostGroupTable ] For example: CostGroupTable 2 = "Local Calls", 2, 1;...
Page 889: Sbc And Dsp Channel Capacity
The capacity figures listed in the table below are accurate at the time of publication of this document. However, these figures may change due to a later software update. For the latest figures, please contact your AudioCodes sales representative. •...
Page 890: Channel Capacity And Capabilities
Mediant 500 E-SBC 54.2 Channel Capacity and Capabilities The SBC session capacity and DSP channel capacity are shown in the tables below. Table 54-2: SBC Session Capacity and Capabilities for Mediant 500 E-SBC Wideband Coders Hardware DSP Channels Max. SBC Sessions...
Page 891: Technical Specifications
The device's technical specifications are listed in the table below. Notes: • All specifications in this document are subject to change without prior notice. • The compliance and regulatory information can be downloaded from AudioCodes Web site at http://www.audiocodes.com/library. Table 55-1: Technical Specifications Function Specification...
Page 892 Low latency, unprocessed payload transfer Media De-anchoring Hair-pinning of local calls to avoid unnecessary media delays and bandwidth consumption Voice Quality Monitoring AudioCodes Session Experience Manager (SEM) Quality of Experience Access control and media quality enhancements based on QoE and bandwidth utilization Test agent...
Page 893 User's Manual 55. Technical Specifications This page is intentionally left blank. Version 6.8 Mediant 500 E-SBC...
Page 894 User's Manual Ver. 6.8 www.audiocodes.com...

AudioCodes Mediant 500 E-SBC User Manual

Table of Contents

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

Table of Contents

25 Configuring DTMF and Dialing

26 Configuring Supplementary Services

Session Border Controller Application

27 SBC Overview

28 SBC Configuration

Cloud Resilience Package

29 CRP Overview

30 CRP Configuration

High-Availability System

31 HA Overview

32 HA Configuration

33 HA Maintenance

Maintenance

34 Basic Maintenance

35 High Availability Maintenance

36 Disconnecting Active Calls

37 Resetting Channels

38 Software Upgrade

39 Automatic Update Mechanism

40 Restoring Factory Defaults

41 Automatic Archiving of Configuration File

42 USB Storage Capabilities

Status, Performance Monitoring and Reporting

43 System Status

44 Carrier-Grade Alarms

45 Performance Monitoring

46 Voip Status

47 Reporting Information to External Party

Diagnostics

48 Syslog and Debug Recordings

49 Self-Testing

50 Creating Core Dump and Debug Files Upon Device Crash

51 Testing SIP Signaling Calls

Appendix

52 Dialing Plan Notation for Routing and Manipulation

53 Configuration Parameters Reference

54 SBC and DSP Channel Capacity

55 Technical Specifications

Quick Links

Chapters

Related Manuals for AudioCodes Mediant 500 E-SBC

Summary of Contents for AudioCodes Mediant 500 E-SBC