Page 1 User's Manual AudioCodes Family of Multi-Service Business Routers (MSBR) Mediant™ 500 MSBR Version 7.2...
Page 3: Table Of Contents
Changing Index Position of Table Rows ..........63 7.1.6.9 Searching Table Entries ................64 7.1.7 Searching for Configuration Parameters ..............64 7.1.8 Getting Help ......................66 7.1.9 Logging Off the Web Interface ................. 66 Customizing the Web Interface ................66 Version 7.2 Mediant 500 MSBR...
Page 4 Mediant 500 MSBR 7.2.1 Replacing the Corporate Logo ................. 67 7.2.1.1 Replacing the Corporate Logo with an Image ..........67 7.2.1.2 Replacing the Corporate Logo with Text ..........68 7.2.2 Customizing the Product Name ................69 7.2.3 Customizing the Favicon ..................70 7.2.4...
Page 5 15.5 DNS ........................151 15.5.1 Configuring the Internal DNS Table ...............151 15.5.2 Configuring the Internal SRV Table ...............152 15.6 Multiple Routers Support ..................154 16 Security ......................155 16.1 Configuring TLS for SIP ..................155 Version 7.2 Mediant 500 MSBR...
Page 6 Mediant 500 MSBR 16.2 Intrusion Detection System .................. 155 16.2.1 Enabling IDS ......................156 16.2.2 Configuring IDS Policies ..................156 16.2.3 Assigning IDS Policies ...................160 16.2.4 Viewing IDS Alarms ....................162 17 Media ........................ 165 17.1 Configuring Voice Settings ................... 165 17.1.1 Configuring Voice Gain (Volume) Control .............165 17.1.2 Configuring Echo Cancellation ................165...
Page 7 18.7.2.2 Adding ELINs to the Location Information Server ......... 273 18.7.2.3 Passing Location Information to the PSTN Emergency Provider ..274 18.7.3 AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN .....275 18.7.3.1 Detecting and Handling E9-1-1 Calls ............ 276 Version 7.2...
Page 8 18.7.3.3 PSAP Callback to Skype for Business Clients for Dropped E9-1-1 Calls 18.7.3.4 Selecting ELIN for Multiple Calls within Same ERL ......279 18.7.3.5 Location Based Emergency Routing ............. 280 18.7.4 Configuring AudioCodes ELIN Device ..............280 18.7.4.1 Enabling the E9-1-1 Feature ..............280 18.7.4.2 Configuring the E9-1-1 Callback Timeout ..........280 18.7.4.3 Configuring the SIP Release Cause Code for Failed E9-1-1 Calls ..
Page 9 27 Routing ......................495 27.1 Configuring Tel-to-IP Routing Rules ..............495 27.2 Configuring IP-to-Tel Routing Rules ..............504 27.3 Configuring a Gateway Routing Policy Rule ............509 27.4 Alternative Routing for Tel-to-IP Calls ..............511 Version 7.2 Mediant 500 MSBR...
Page 10 Mediant 500 MSBR 27.4.1 IP Destinations Connectivity Feature ..............511 27.4.2 Alternative Routing Based on IP Connectivity ............512 27.4.3 Alternative Routing Based on SIP Responses ............514 27.4.4 Alternative Routing upon SIP 3xx with Multiple Contacts ........517 27.4.5 PSTN Fallback .......................517 27.5 Alternative Routing for IP-to-Tel Calls ..............518 27.5.1 Alternative Routing to Trunk upon Q.931 Call Release Cause Code ....518...
Page 11 31.13.2 FXO Operations for Tel-to-IP Calls ................617 31.13.2.1 Automatic Dialing .................. 617 31.13.2.2 Collecting Digits Mode................618 31.13.2.3 FXO Supplementary Services ............... 618 31.13.3 Call Termination on FXO Devices .................619 31.13.3.1 Calls Termination by PBX ..............619 Version 7.2 Mediant 500 MSBR...
Page 12 Mediant 500 MSBR 31.13.3.2 Call Termination before Call Establishment .......... 620 31.13.3.3 Ring Detection Timeout ................. 620 31.14 Remote PBX Extension between FXO and FXS Devices ........620 31.14.1 Dialing from Remote Extension (Phone at FXS) ...........621 31.14.2 Dialing from PBX Line or PSTN ................621 31.14.3 Message Waiting Indication for Remote Extensions ..........622...
Page 13 41.3 Enabling Interworking of SIP and SIP-I Endpoints ..........731 41.4 Call Forking ......................733 41.4.1 Initiating SIP Call Forking ..................733 41.4.2 Configuring SIP Forking Initiated by SIP Proxy .............734 41.4.3 Configuring Call Forking-based IP-to-IP Routing Rules ........734 41.5 Call Survivability ....................734 Version 7.2 Mediant 500 MSBR...
Page 14 Mediant 500 MSBR 41.5.1 Enabling Auto-Provisioning of Subscriber-Specific Information of BroadWorks Server for Survivability ......................735 41.5.2 Configuring BroadSoft's Shared Phone Line Call Appearance for Survivability ...736 41.5.3 Configuring Call Survivability for Call Centers ............737 41.5.4 Enabling Survivability Display on Aastra IP Phones ..........739 41.6 Alternative Routing on Detection of Failed SIP Response ........
Page 15 51.1.1 DHCP-based Provisioning ..................807 51.1.2 HTTP-based Provisioning ..................808 51.1.3 FTP-based Provisioning ..................809 51.1.4 Provisioning using AudioCodes EMS ..............809 51.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 809 51.2.1 Files Provisioned by Automatic Update ..............810 51.2.2 File Location for Automatic Update ...............810 51.2.3 MAC Address Placeholder in Configuration File Name .........811...
Page 16 Mediant 500 MSBR 51.2.9 Cyclic Redundancy Check on Downloaded Configuration Files ......818 51.2.10 Automatic Update Configuration Examples ............818 51.2.10.1 Automatic Update for Single Device ............. 819 51.2.10.2 Automatic Update from Remote Servers ..........820 51.2.10.3 Automatic Update for Mass Deployment ..........821 51.3 Zero Configuration ....................
Page 17 63.2.1.1 Event Representation in Syslog Messages .......... 937 63.2.1.2 Unique Device Identification in Syslog Messages ........ 938 63.2.1.3 Identifying AudioCodes Syslog Messages using Facility Levels ..938 63.2.1.4 Syslog Fields for Answering Machine Detection (AMD) ....... 939 63.2.1.5 SNMP Alarms in Syslog Messages ............939 63.2.2 Enabling Syslog .....................940...
Page 18 Mediant 500 MSBR 64 Self-Testing ...................... 949 65 Creating Core Dump and Debug Files upon Device Crash ......951 66 Debugging Web Services ................953 67 Re-initializing Device with "Purified" Configuration ........955 68 Analog Line Testing ..................957 68.1 FXO Line Testing ....................957 69 Testing SIP Signaling Calls ................
Page 19 74.10.8 Tone Parameters ....................1167 74.10.8.1 Telephony Tone Parameters ............... 1168 74.10.8.2 Tone Detection Parameters ..............1174 74.10.8.3 Metering Tone Parameters ..............1175 74.10.9 Telephone Keypad Sequence Parameters............1177 74.10.10 FXO and FXS Parameters ................1181 Version 7.2 Mediant 500 MSBR...
Page 20 Mediant 500 MSBR 74.10.11 Trunk Groups and Routing Parameters ............1185 74.10.12 IP Connectivity Parameters ................1192 74.10.13 Alternative Routing Parameters ..............1194 74.10.14 Number Manipulation Parameters ..............1196 74.11 Answer and Disconnect Supervision Parameters ..........1206 74.12 SBC Parameters ....................1211 74.12.1 Supplementary Services ..................
Page 21: Weee Eu Directive
Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our Web site at www.audiocodes.com/support.
Page 22 The device's installed License Key does not include the MSFT feature key, which enables the device to operate in a Microsoft Skype for Business environment. If necessary, you can order this feature key separately from your AudioCodes sales representative. Note: •...
Page 23 Some of the features listed in this document are available only if the relevant License Key has been purchased from AudioCodes and installed on the device. For a list of License Keys that can be purchased, please consult your AudioCodes sales representative.
Page 24: Document Revision Record
Tr069DataModel; Tr069VerifyCertificate; Tr069VerifyCommonName; Tr069TLSContext Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads. User's Manual...
Page 25: Introduction
User's Manual 1. Introduction Introduction This User's Manual describes how to configure and manage your AudioCodes product (hereafter, referred to as device). This document is intended for the professional person responsible for installing, configuring and managing the device. Product Overview...
Page 26: Typographical Conventions
Mediant 500 MSBR • (Optional, customer-ordered) Four FXS ports • (Optional, customer-ordered) Single FXO port The device allows full management through its command line interface (CLI) as well as its HTTP/S-based embedded Web server. The user-friendly Web interface allows remote configuration using any standard Web browser (such as Microsoft™...
Page 27: Sbc Application
As the device provides a default SRD, in a single SRD topology, the device automatically assigns the SRD to newly created configuration entities. Thus, in such scenarios, there is no need to get Version 7.2 Mediant 500 MSBR...
Page 28 Mediant 500 MSBR Configuration Terms Description involved with SRD configuration. Multiple SRDs are required only for multi-tenant deployments, where it "splits" the device into multiple logical devices. For multiple SRDs, the SRD can be configured with a Sharing Policy. The Sharing Policy simply means whether the SRD's resources (SIP Interfaces, IP Groups, and Proxy Sets) can be used by other SRDs.
Page 29 "serving" IP Group. Registration is for REGISTER messages, which are initiated by the device on behalf of the "serving" SIP entity. The associations between the configuration entities are summarized in the following figure: Figure 1-1: Association of Configuration Entities Version 7.2 Mediant 500 MSBR...
Page 30: Gateway Application
Mediant 500 MSBR The main configuration entities and their involvement in the call processing is summarized in following figure. The figure is used only as an example to provide basic understanding of the configuration terminology. Depending on configuration and network topology, the call process may include additional stages or a different order of stages.
Page 31 Trunk Group, or calling or called telephone number prefix and suffix. The SIP entity can be denoted by an IP Group or other IP destinations such as IP address, FQDN, E.164 Telephone Number Mapping (ENUM service), and Lightweight Directory Access Protocol (LDAP). Version 7.2 Mediant 500 MSBR...
Page 32 Mediant 500 MSBR IP-to-Tel (Trunk Group) IP-to-Tel routing rules are used to route incoming IP calls to Trunk Groups. Routing Rules The specific channel pertaining to the Trunk Group to which the call is routed can also be configured. Accounts Accounts are used to register or authenticate PSTN-based endpoints with a SIP entity (e.g., a registrar or proxy server).
Page 33: Getting Started With Initial Connectivity
Part I Getting Started with Initial Connectivity...
Page 35: 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. Device management can be done though the LAN and/or WAN interface. Version 7.2 Mediant 500 MSBR...
Page 36 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 37: Accessing The Device's Management Interfaces
Figure 3-1: Example of Terminal Emulator Program At the CLI prompt, type the username (default is "Admin"), and then press Enter: Username: Admin At the prompt, type the password (default is "Admin"), and then press Enter: Password: Admin Version 7.2 Mediant 500 MSBR...
Page 38: Connecting To The Web Interface
Mediant 500 MSBR At the prompt, type the following, and then press Enter: enable At the prompt, type the password again, and then press Enter: Password: Admin Connecting to the Web Interface You can access the Web-based management interface using the device's default LAN IP...
Page 39 IP address (see table above); the Web interface's Web Login screen appears: Figure 3-3: Web Login Screen In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Version 7.2 Mediant 500 MSBR...
Page 40 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 41: Configuring Router's Lan And Wan
At the prompt, type the following command to access the router configuration mode: # configure data Access the data LAN switch interface: (config-data)# interface vlan 1 To disable the DHCP server: (conf-if-VLAN 1)# no service dhcp To enable DHCP server: Version 7.2 Mediant 500 MSBR...
Page 42: Configuring The Wan Interface
Mediant 500 MSBR Configure the pool of IP addresses: (conf-if-VLAN 1)# ip dhcp-server network 10.8.6.84 10.8.6.89 255.255.255.0 Enable DHCP server functionality: (conf-if-VLAN 1)# service dhcp Save your settings with a flash burn: (conf-if-VLAN 1)# do write Configuring the WAN Interface This procedure describes how to configure the WAN interface and uses Gigabit Ethernet as an example.
Page 43: Enabling Remote Management From Wan
To enable remote management from WAN through Telnet or SSH:  Enable Telnet through CLI: Access the System configuration mode: # configure system (config-system)# Access the CLI Settings command set: (config-system)# cli-settings (cli-settings)# Enable Telnet from WAN: Version 7.2 Mediant 500 MSBR...
Page 44 Mediant 500 MSBR (cli-settings)# wan-telnet-allow on Save configuration to flash: (cli-settings)# do write  Enable SSH through CLI: Access the System configuration mode: # configure system (config-system)# Access the CLI Settings command set: (config-system)# cli-settings (cli-settings)# Enable SSH: (cli-settings)# ssh on...
Page 45: Management Tools
Part II Management Tools...
Page 47: Introduction
Configuration ini file - see INI File-Based Management on page 107 Note: • Some configuration settings can only be done using a specific management tool. • For a list and description of all the configuration parameters, see Configuration Parameters Reference on page 983. Version 7.2 Mediant 500 MSBR...
Page 48 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 49: Web-Based Management
(Version 5.02 or later) • Google Chrome (Version 50 or later)  Recommended screen resolutions: 1024 x 768 pixels, or 1280 x 1024 pixels Note: Your Web browser must be JavaScript-enabled to access the Web interface. Version 7.2 Mediant 500 MSBR...
Page 50: Accessing The Web Interface
Mediant 500 MSBR 7.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser. In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...
Page 51: Areas Of The Gui
PC, or for loading an ini file to the device (see Configuration File on page 805).  Auxiliary Files: Opens the Auxiliary Files page, which is used for loading Auxiliary files to the device (see Loading Auxiliary Files through Web Interface on page 772). Version 7.2 Mediant 500 MSBR...
Page 52: Accessing Configuration Pages From Navigation Tree
Mediant 500 MSBR  License Key: Opens the License Key page, which is used for installing a new License Key file (see Installing License Key through Web Interface on page 798).  Software Upgrade: Starts the Software Upgrade Wizard for upgrading the device's software (see Software Upgrade on page 767).
Page 53 If you hover your cursor over the icon, it displays the number of rows in the table that are associated with invalid rows. Version 7.2 Mediant 500 MSBR...
Page 54: Configuring Stand-Alone Parameters
Mediant 500 MSBR  Folder containing an item with an invalid row: If a folder contains an item with an invalid row (or associated with an invalid row), the closed folder displays a red-colored icon, as shown in the following example: If you hover your cursor over the icon, it displays the names of the items that are configured with invalid values.
Page 55 (without saving to flash) or powers down. Therefore, make sure that you save your configuration to the device's flash memory. Version 7.2 Mediant 500 MSBR...
Page 56: Configuring Table Parameters
Mediant 500 MSBR 7.1.6 Configuring Table Parameters A typical configuration table is shown below and subsequently described: Figure 7-5: Description of Tables Table 7-2: General Description of Configuration Tables Item # Button Page title (i.e., name of table). The page title also displays the number of configured rows as well as the number of invalid rows.
Page 57: Adding Table Rows
Figure 7-6: Parameter with View Button (Example) You can assign a referenced-row using one of the following methods:  Selecting a referenced-row from the drop-down list: • Scroll down to the desired item and click it. Version 7.2 Mediant 500 MSBR...
Page 58 Mediant 500 MSBR • Search for the item by entering in the field the first few characters of the desired row, and then clicking it. The figure below shows an example of searched results for items (Proxy Sets) that begin with the letter "i": Figure 7-7: Searching a Row to Reference ...
Page 59: Modifying Table Rows
For example, if you delete a SIP Interface that you have assigned to a Proxy Set, the invalid icon appears alongside the Proxy Sets item in the Navigation tree as well as on the Proxy Sets page. Version 7.2 Mediant 500 MSBR...
Page 60: Invalid Value Indications
Mediant 500 MSBR 7.1.6.5 Invalid Value Indications The Web interface provides the following indications of invalid values when configuring table rows:  Parameters configured with invalid values: An invalid value is a value that is not permissible for the parameter. This can include incorrect syntax (string, numeral, or character) or an out-of-range value.
Page 61 Therefore, make sure that you are aware of this and if necessary, assign a different referenced row to the parameter. Only if the parameter is mandatory is the Invalid Line icon displayed for the table in which the parameter is configured. Version 7.2 Mediant 500 MSBR...
Page 62: Viewing Table Rows
Mediant 500 MSBR 7.1.6.6 Viewing Table Rows Tables display a certain number of rows per page. If you have configured more than this number, you can use the table's navigation bar to scroll through the table pages, as shown below and described in the subsequent table:...
Page 63: Changing Index Position Of Table Rows
(e.g., to 3). In other words, the rows have swapped positions. Continue clicking the required arrow until the row has moved to the desired location in the table. Version 7.2 Mediant 500 MSBR...
Page 64: Searching Table Entries
Mediant 500 MSBR 7.1.6.9 Searching Table Entries You can search for any parameter value (alphanumeric) in configuration tables, using the Search tool. The Search tool, located above each table, is shown below and described in the subsequent table: Figure 7-16: Table Search Tool...
Page 65 • Parameter's value • Brief description of parameter Figure 7-17: Search Result Window Click the link of the navigation path corresponding to the required found parameter to open the page on which the parameter appears. Version 7.2 Mediant 500 MSBR...
Page 66: Getting Help
The product name also affects other management interfaces. • In addition to Web-interface customization, you can customize the following to reference your company instead of AudioCodes: √ SNMP Interface: Product system OID (see the SNMPSysOid parameter) and trap Enterprise OID (see the SNMPTrapEnterpriseOid parameter).
Page 67: Replacing The Corporate Logo
User's Manual 7. Web-Based Management 7.2.1 Replacing the Corporate Logo You can replace the default corporate logo image (i.e., AudioCodes logo) that is displayed in the Web interface. The logo appears in the following Web areas:  Web Login screen: Figure 7-20: Corporate Logo on Web Login Screen ...
Page 68: Replacing The Corporate Logo With Text
Mediant 500 MSBR the device's IP address (e.g., http://10.1.229.17/AdminPage). Log in with your credentials; the Admin page appears. On the left pane, click Image Load to Device; the right pane displays the following: Figure 7-23: Customizing Web Logo Use the Browse button to select your logo file, and then click Send File; the device loads the file.
Page 69: Customizing The Product Name
UseProductName = 1 UserProductName = < name > Load the ini file using the Auxiliary Files page (see Loading Auxiliary Files on page 771). Reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 500 MSBR...
Page 70: Customizing The Favicon
7.2.3 Customizing the Favicon You can replace the default favicon (i.e., AudioCodes) with your own personalized favicon. Depending on the browser, the favicon is displayed in various areas of your browser, for example, in the URL address bar, on the page tab, and when bookmarked: Figure 7-26: Favicon Display in Browser ...
Page 71: Creating A Login Welcome Message
Reset the device with a save-to-flash for your settings to take effect. Configuring Management User Accounts The Local Users table lets you configure up to 10 management user accounts for the device's Web interface and CLI. You configure each user account with login credentials Version 7.2 Mediant 500 MSBR...
Page 72 Mediant 500 MSBR (username and password) and with a management user level which defines the level of read and write privileges. The table below describes the different types of user levels: Table 7-5: Description of Management User Levels Numeric User Level...
Page 73 Figure 7-29: Local Users Table - Dialog Box Configure a user account according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 7-7: Local Users Table Parameter Descriptions Parameter Description General Version 7.2 Mediant 500 MSBR...
Page 74 Mediant 500 MSBR Index Defines an index number for the new table row. [WebUsers_Index] Note: Each row must be configured with a unique index. Username Defines the Web user's username. user The valid value is a string of up to 40 alphanumeric characters, including the period ".", underscore "_", and hyphen "-"...
Page 75 Web interface is blocked. [WebUsers_PwAgeInterval The valid value is 0 to 10000, where 0 means that the password is always valid. The default is 90. Version 7.2 Mediant 500 MSBR...
Page 76: Displaying Login Information Upon Login
Mediant 500 MSBR Session Limit Defines the maximum number of concurrent Web interface sessions allowed for the specific user. For example, if configured to 2, the same session-limit user account can be logged into the device’s Web interface (i.e., [WebUsers_SessionLimit] same username-password combination) from two different management stations (i.e., IP addresses) at any one time.
Page 77: Viewing Logged-In User Information
Note: You can only perform the configuration described in this section if you are a management user with Security Administrator level or Master level. For more information, see Configuring Management User Accounts on page 71. Version 7.2 Mediant 500 MSBR...
Page 78 Mediant 500 MSBR  To configure Web user sessions and access security: Open the Web Settings page (Setup menu > Administration tab > Web & CLI folder > Web Settings). Under the Session group, configure the following parameters: Figure 7-32: Configuring Web User Sessions •...
Page 79: Changing Login Password For Administrator And Monitor Users
To enable two-way authentication whereby both management client and server are authenticated using X.509 certificates, from the 'Require Client Certificates for HTTPS connection' drop-down list, select Enable. In the 'HTTPS Cipher String' field, enter the cipher string for HTTPS (in OpenSSL Version 7.2 Mediant 500 MSBR...
Page 80: Limiting Oamp Access To A Specific Wan Interface
Mediant 500 MSBR cipher list format). WAN access: • To enable WAN access to the management interface through HTTP, from the 'Allow WAN access to HTTP' drop-down list, select Enable. • To enable WAN access to the management interface through HTTPS, from the 'Allow WAN access to HTTPS' drop-down list, select Enable.
Page 81: Web Login Authentication Using Smart Cards
This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative.  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader.
Page 82 Mediant 500 MSBR  To add IP addresses to the Access List: Open the Access List table (Setup menu > Administration tab > Web & CLI folder > Access List). Figure 7-35: Access List - Adding IP Address In the 'Add an authorized IP address' field, configure an IP address, and then click Add New Entry;...
Page 83: Cli-Based Management
Figure 8-1: Enabling Telnet Configure the following parameters: • 'Embedded Telnet Server': Select Enable Unsecured or Enable Secured (i.e, SSL) to enable Telnet. • 'Telnet Server TCP Port': Enter the port number of the embedded Telnet server. Version 7.2 Mediant 500 MSBR...
Page 84: Enabling Ssh With Rsa Public Key For Cli
Mediant 500 MSBR • 'Telnet Server Idle Timeout': Enter the duration of inactivity in the Telnet session after which the session automatically ends. • 'Allow WAN access to Telnet': Select Enable to enable Telnet from the WAN. Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
Page 85 Accounts on page 71), and then for the required user, paste the public key that you copied in Step 1.d into the 'SSH Public Key' field, as shown below: Figure 8-3: Pasting Public RSA Key per User in Local Users Table Version 7.2 Mediant 500 MSBR...
Page 86 Mediant 500 MSBR • For all users: Open the CLI Settings page (Setup menu > Administration tab > Web & CLI folder > CLI Settings), and then paste the public key that you copied in Step 1.d into the 'Admin Key' field, as shown below:...
Page 87: Configuring Maximum Telnet/Ssh Sessions
Configuring Management User Accounts on page  To establish a CLI session with the device: Connect the device to the network. Establish a Telnet or SSH session using the device's OAMP IP address. Version 7.2 Mediant 500 MSBR...
Page 88: Viewing Current Cli Sessions
Mediant 500 MSBR Log in to the session using the username and password assigned to the Admin user of the Web interface: At the Username prompt, type the username, and then press Enter: Username: Admin At the Password prompt, type the password, and then press Enter:...
Page 89: Configuring Displayed Output Lines In Cli Terminal Window
CLI. TACACS+ services are maintained on a database on a TACACS+ daemon. You must have access to and must configure a TACACS+ server before configuring TACACS+ on your device. TACACS+ can provide the following services: Version 7.2 Mediant 500 MSBR...
Page 90 Mediant 500 MSBR  Authentication: provides authentication through login and password dialog  Authorization: manages user capabilities for the duration of the user's session by placing restrictions on what commands a user may execute  Accounting: collects and sends information for auditing and reporting to the TACACS+...
Page 91: Snmp-Based Management
9. SNMP-Based Management SNMP-Based Management The device provides an embedded SNMP agent that lets you manage it using AudioCodes Element Management System (EMS) or a third-party SNMP manager. The SNMP agent supports standard and proprietary Management Information Base (MIBs). All supported MIB files are supplied to customers as part of the release.
Page 92 Mediant 500 MSBR Note: • SNMP community strings are applicable only to SNMPv1 and SNMPv2c; SNMPv3 uses username-password authentication along with an encryption key (see Configuring SNMP V3 Users on page 96). • You can enhance security by configuring Trusted Managers (see Configuring SNMP Trusted Managers on page 95).
Page 93 > community-string only the following:  [SNMPTrapCommunityString Upper- and lower-case letters (a to z, and A to Z)  Numbers (0 to 9)  Hyphen (-)  Underline (_) For example, "Trap-comm_string1". The default is "trapuser". Version 7.2 Mediant 500 MSBR...
Page 94: Configuring Snmp Trap Destinations With Ip Addresses
Mediant 500 MSBR Configuring SNMP Trap Destinations with IP Addresses The SNMP Trap Destinations table lets you to configure up to five SNMP trap managers to receive traps sent by the device. The SNMP manager is defined by IP address and port.
Page 95: Configuring An Snmp Trap Destination With Fqdn
(as long as the community string is correct). The following procedure describes how to configure SNMP Trusted Managers through the Web interface. You can also configure it through ini file (SNMPTrustedMgr_x) or CLI (configure system > snmp settings > trusted-managers). Version 7.2 Mediant 500 MSBR...
Page 96: Enabling Snmp Traps For Web Activity
Mediant 500 MSBR  To configure SNMP Trusted Managers: Open the SNMP Trusted Managers table (Setup menu > Administration tab > SNMP folder > SNMP Trusted Managers). Figure 9-4: SNMP Trusted Managers Table Configure an IP address (in dotted-decimal notation) for one or more SNMP Trusted Managers.
Page 97 [1] MD5 [SNMPUsers_AuthProtocol]  [2] SHA-1 Privacy Protocol Privacy protocol of the SNMP v3 user.  priv-protocol [0] None (default)  [1] DES [SNMPUsers_PrivProtocol]  [2] 3DES  [3] AES-128  [4] AES-192  [5] AES-256 Version 7.2 Mediant 500 MSBR...
Page 98 Mediant 500 MSBR Authentication Key Authentication key. Keys can be entered in the form of a text password or long hex string. Keys are always persisted as long hex auth-key strings and keys are localized. [SNMPUsers_AuthKey] Privacy Key Privacy key. Keys can be entered in the form of a text password or long hex string.
Page 99: Based Management
(CPE) and the Auto Configuration Servers (ACS). The TR- 069 connection to the ACS can be done on the LAN or WAN interface. The protocol stack looks as follows: Table 10-1: TR-069 Protocol Stack CPE/ACS Management Application RPC Methods SOAP HTTP SSL/TLS TCP/IP Version 7.2 Mediant 500 MSBR...
Page 100 Mediant 500 MSBR Communication is typically established by the CPE; hence, messages from CPE to ACS are typically carried in HTTP requests, and messages from ACS to CPE in HTTP responses. Figure 10-1: TR-069 Session Example Communication between ACS and CPE is defined via Remote Procedure Call (RPC) methods.
Page 101 Download: Used by the ACS to cause the CPE to download the following file(s) from a designated location: ♦ Firmware Upgrade Image (File Type = 1) - cmp file. ♦ Vendor Configuration File (File Type = 3) - output of show running- Version 7.2 Mediant 500 MSBR...
Page 102 Mediant 500 MSBR config CLI command, which includes Data and Voice configuration. The CPE responds to the Download method, indicating successful or unsuccessful completion via one of the following: ♦ A DownloadResponse with the Status argument set to zero (indicating success), or a fault response to the Download request (indicating failure).
Page 103 Inform: A CPE must call this method to initiate a transaction sequence whenever a connection to an ACS is established. • TransferComplete: Informs the ACS of the completion (either successful or unsuccessful) of a file transfer initiated by an earlier Download or Upload method call. Version 7.2 Mediant 500 MSBR...
Page 104: 104
FXS interfaces (lines) only. TR-104 defines a "data model" template for TR-069 enabled devices. The "data model" that is applicable to the AudioCodes device is defined in the DSL Forum TR-104 – "DSLHome™ Provisioning Parameters for VoIP CPE"...
Page 105 InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.Line.{i}.Callin gFeatures: Configures voice parameters per FXS line such as caller ID. ♦ InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.Line.{i}.SIP: Configures username/password per FXS line. AudioCodes maps this object to the corresponding entry in the Authentication table • InternetGatewayDevice.Services.VoiceService.1.VoiceProfile.1.SIP: Configures SIP parameters specific to the UA such as Proxy server.
Page 106: Configuring Tr-069
Mediant 500 MSBR 10.3 Configuring TR-069 The CWMP/TR-069 Settings page is used to enable and configure TR-069.  To configure TR-069: Open the CWMP/TR-069 Settings page (Setup menu > IP Network tab > TR-069 (CWMP)): Figure 10-5: CWMP/TR-069 Settings Page Configure the parameters as required.
Page 107: Ini File-Based Management
An exception is Index fields, which are mandatory. • The Format line must end with a semicolon ";".  Data line(s): Contain the actual values of the columns (parameters). The values are interpreted according to the Format line. Version 7.2 Mediant 500 MSBR...
Page 108 Mediant 500 MSBR • The first word of the Data line must be the table’s string name followed by the Index field. • Columns must be separated by a comma ",". • A Data line must end with a semicolon ";".
Page 109: General Ini File Formatting Rules
(!), for example: !CpMediaRealm 1 = "ITSP", "Voice", "", 60210, 2, 6030, 0, "", ""; • To restore the device to default settings through the ini file, see Restoring Factory Defaults on page 835. Version 7.2 Mediant 500 MSBR...
Page 110: 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 111 $0$<plain text>: Password can be entered in plain text; useful for configuring a new password. When the ini file is loaded to the device and then later saved from the device to a PC, the password is displayed obscured (i.e., $1$<obscured password>). Version 7.2 Mediant 500 MSBR...
Page 112: Ini Viewer And Editor Utility
11.6 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 113: Rest-Based Management
URL path (i.e., /api/v1/alarms/active). Figure 12-1: Accessing Device's REST Interface via Web Figure 12-2: REST Resource - Alarms Version 7.2 Mediant 500 MSBR...
Page 114 Mediant 500 MSBR Figure 12-3: REST Resource - Active Alarms Note: • For more information on the REST API, refer to the document, REST API for Mediant Devices. • When accessing the device's REST interface, you are prompted for your management user credentials (username and password).
Page 115: General System Settings
Part III General System Settings...
Page 117: Configuring Ssl/Tls Certificates
You can configure the device to check whether a peer's certificate has been revoked, using the OCSP. When OCSP is enabled, the device queries the OCSP server for revocation information whenever a Version 7.2 Mediant 500 MSBR...
Page 118 Mediant 500 MSBR peer certificate is received (TLS client mode, or TLS server mode with mutual authentication). Note: • The device does not query OCSP for its own certificate. • Some PKIs do not support OCSP, but generate Certificate Revocation Lists (CRLs).
Page 119 WebRTC calls. [TLSContexts_DTLSV  ersion] [0] Any (default)  [1] DTLSv1.0  [2] DTLSv1.2 For more information on WebRTC, see WebRTC. Note: The parameter is applicable only to the SBC application. Version 7.2 Mediant 500 MSBR...
Page 120: Assigning Csr-Based Certificates To Tls Contexts
Mediant 500 MSBR Cipher Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format). ciphers-server The default is AES:RC4. For valid values, visit the OpenSSL website at [TLSContexts_ServerC https://www.openssl.org/docs/man1.0.2/apps/ciphers.html. ipherString] Cipher Client Defines the supported cipher suite for TLS clients.
Page 121 Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 13-1: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request. Version 7.2 Mediant 500 MSBR...
Page 122 Mediant 500 MSBR When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Make sure 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 123: Viewing Certificate Information
Open the TLS Contexts table (see Configuring TLS Certificate Contexts on page 117). Select a TLS Context row, and then click the Certificate Information link located below the table; the Certificate Information page appears: Figure 13-4: Viewing Certificate Information Version 7.2 Mediant 500 MSBR...
Page 124: Assigning Externally Created Private Keys To Tls Contexts
Mediant 500 MSBR 13.4 Assigning Externally Created Private Keys to TLS Contexts The following procedure describes how to assign an externally created private key to a TLS Context.  To assign an externally created private key to a TLS Context: Obtain a private key in either textual PEM (PKCS #7) or PFX (PKCS #12) format (typically provided by your security administrator).
Page 125: Generating Private Keys For Tls Contexts
If you don't want to encrypt the file, make the field blank. The default passphrase is "audc". The passphrase can be up to 32 characters. Click Generate Private-Key; a message appears requesting you to confirm key generation. Version 7.2 Mediant 500 MSBR...
Page 126: Creating Self-Signed Certificates For Tls Contexts
Mediant 500 MSBR Click OK to confirm key generation; the device generates a new private key, indicated by a message in the Certificate Signing Request group: Figure 13-8: Indication of Newly Generated Private Key Continue with the certificate configuration by either creating a CSR or generating a new self-signed certificate.
Page 127: Importing Certificates Into Trusted Root Certificate Store
Root CA certificate, which is self-signed. The purpose of a certificate chain is to establish a chain of trust from a child certificate to the trusted root CA certificate. The CA vouches for the identity of the child certificate by signing Version 7.2 Mediant 500 MSBR...
Page 128 Mediant 500 MSBR it. A client certificate is considered trusted if one of the CA certificates up the certificate chain is found in the server certificate directory. For the device to trust a whole chain of certificates per TLS Context, you need to import them into the device's Trusted Certificates Store, as described below.
Page 129: Configuring Mutual Tls Authentication
When an organizational PKI is used, two-way authentication may be desired - both client and server should be authenticated using X.509 certificates. This is achieved by installing a client certificate on the management PC and Version 7.2 Mediant 500 MSBR...
Page 130: Configuring Tls Server Certificate Expiry Check
Mediant 500 MSBR loading the root CA's certificate to the device's Trusted Certificates table (certificate root store). The Trusted Root Certificate file may contain more than one CA certificate combined, using a text editor.  To enable mutual TLS authentication for HTTPS: On the Web Settings page (see Configuring Secured (HTTPS) Web on page 79), configure the 'Secured Web Connection (HTTPS)' parameter to HTTPS Only.
Page 131 In the 'TLS Expiry Check Period' field, enter the periodical interval (in days) for checking the TLS server certificate expiry date. By default, the device checks the certificate every 7 days. Click the Submit TLS Expiry Settings button. Version 7.2 Mediant 500 MSBR...
Page 132 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 133: Date And Time
• In the 'NTP Authentication Key Identifier' field, configure the NTP authentication key identifier. • In the 'NTP Authentication Secret Key' field, configure the secret authentication key shared between the device and the NTP server. Version 7.2 Mediant 500 MSBR...
Page 134: Configuring Date And Time Manually
Mediant 500 MSBR Verify that the device has received the correct date and time from the NTP server. The date and time is displayed in the 'UTC Time' read-only field under the Time Zone group. Note: If the device does not receive a response from the NTP server, it polls the NTP server for 10 minutes.
Page 135: Configuring Daylight Saving Time
Figure 14-4: Configuring Daylight Savings From the 'Day Light Saving Time' (DayLightSavingTimeEnable) drop-down list, select Enable. From the 'DST Mode' drop-down list, select the range type for configuring the start and end dates for DST: Version 7.2 Mediant 500 MSBR...
Page 136 Mediant 500 MSBR • Day of year: The range is configured by exact date (day number of month), for example, from March 30 to October 30. If 'DST Mode' is set to Day of year, in the 'Start Time' (DayLightSavingTimeStart) and 'End Time' (DayLightSavingTimeEnd) drop-down lists, configure the period for which DST is relevant.
Page 137: General Voip Configuration
Part IV General VoIP Configuration...
Page 139: Network
 Click the MSBR Network View home icon (Setup menu > IP Network tab > MSBR Network View). The following figure displays an example of the Network View: Figure 15-1: Example of the Network View Version 7.2 Mediant 500 MSBR...
Page 140: Network Address Translation Support
Mediant 500 MSBR 15.2 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 141: Configuring A Static Nat Ip Address For All Interfaces
In the 'NAT IP Address' field, enter the NAT IP address in dotted-decimal notation. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Note: The feature is applicable only to the Gateway application. Version 7.2 Mediant 500 MSBR...
Page 142: Configuring Nat Translation Per Ip Interface
Mediant 500 MSBR 15.2.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 - public) when the device is located behind NAT. The device's NAT traversal mechanism replaces the source IP address of SIP messages sent from a specified VoIP interface to a public IP address.
Page 143: Remote Ua Behind Nat
IP address in the Via header. If necessary, you can also configure the device to always consider incoming SIP INVITE messages as sent from endpoints that are located behind NAT. When this is enabled, the Version 7.2 Mediant 500 MSBR...
Page 144: Media (Rtp/Rtcp/T.38)
Mediant 500 MSBR device sends responses to the INVITE (to the endpoint) using the the source IP address of the packet (INVITE) initially received from the endpoint. This is useful in scenarios where the endpoint is located behind a NAT firewall and the device (for whatever reason) is unable to identify NAT using its regular NAT Detection mechanism.
Page 145 Open the Media Settings page (Setup menu > Signaling & Media tab > Media folder > Media Settings), and then from the 'NAT Traversal' drop-down list (NATMode), select the required NAT option: Figure 15-7: Configuring NAT Traversal for Media Click Apply. Version 7.2 Mediant 500 MSBR...
Page 146: Robust Receipt Of Media Streams By Media Latching
15.3 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 147 Configure a period (msec) after which if no packets are received from the current media session, the channel can re-latch onto another stream: ♦ 'Timeout To Relatch RTP' ♦ 'Timeout To Relatch SRTP' ♦ 'Timeout To Relatch Silence' ♦ 'Timeout To Relatch RTCP' Version 7.2 Mediant 500 MSBR...
Page 148: Configuring Quality Of Service
Mediant 500 MSBR ♦ 'Fax Relay Rx/Tx Timeout' Figure 15-9: Configuring Media Robust Click Apply, and then save your settings to flash memory. 15.4 Configuring Quality of Service This section describes how to configure Layer-2 and Layer-3 Quality of Service (QoS).
Page 149 Defines the DiffServ value for Premium Media CoS content. media-qos The valid range is 0 to 63. The default is 46. [PremiumServiceClassMediaDiff Note: You can also configure the the parameter per IP Profile Serv] (IpProfile_IPDiffServ) or Tel Profile (TelProfile_IPDiffServ). Version 7.2 Mediant 500 MSBR...
Page 150: Configuring Diffserv-To-Vlan Priority Mapping
Mediant 500 MSBR Control Premium QoS Defines the DiffServ value for Premium Control CoS content (Call Control applications). control-qos The valid range is 0 to 63. The default is 40. [PremiumServiceClassControlDiff Serv] Note: You can also configure the the parameter per IP Profile (IpProfile_SigIPDiffServ) or Tel Profile (TelProfile_SigIPDiffServ).
Page 151: Dns
You can also configure it through ini file (DNS2IP) or CLI (configure network > dns dns-to-ip).  To configure the device's DNS table: Open the Internal DNS table (Setup menu > IP Network tab > DNS folder > Internal DNS). Version 7.2 Mediant 500 MSBR...
Page 152: Configuring The Internal Srv Table
Mediant 500 MSBR Click New; the following dialog box appears: Figure 15-12: Internal DNS Table - Add Dialog Box Configure a DNS rule according to the parameters described in the table below. Click Apply. Table 15-5: Internal DNS Table Parameter Description...
Page 153 By default, no value is defined. [Srv2Ip_Dns1/2/3] Priority (1-3) Defines the priority of the target host. A lower value means that it is more preferred. priority-1|2|3 By default, no value is defined. [Srv2Ip_Priority1/2/3] Version 7.2 Mediant 500 MSBR...
Page 154: Multiple Routers Support
Mediant 500 MSBR Weight (1-3) Defines a relative weight for records with the same priority. weight-1|2|3 By default, no value is defined. [Srv2Ip_Weight1/2/3] Port (1-3) Defines the TCP or UDP port on which the service is to be found. port-1|2|3 By default, no value is defined.
Page 155: Security
The Intrusion Detection System (IDS) is an important feature for Enterprises to ensure legitimate calls are not being adversely affected by attacks and to prevent Theft of Service and unauthorized access. There are many types of malicious attacks, the most common being: Version 7.2 Mediant 500 MSBR...
Page 156: Enabling Ids
Mediant 500 MSBR  Denial of service: This can be Denial of Service (DoS) where an attacker wishing to prevent a server from functioning correctly directs a large amount of requests – sometimes meaningless and sometimes legitimate, or it can be Distributed Denial of...
Page 157 Figure 16-3: IDS Policies Table with Default Rules Click New; the following dialog box appears: Figure 16-4: IDS Policies Table - Add Dialog Box Configure an IDS Policy name according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 158 Mediant 500 MSBR Table 16-1: IDS Policies Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. policy Note: Each row must be configured with a unique index. [IDSPolicy_Index] Name Defines a descriptive name, which is used when associating the row in other tables.
Page 159 Defines the threshold interval (in seconds) during which the device counts the attacks to check if a threshold is crossed. The counter is threshold-window automatically reset at the end of the interval. [IDSRule_ThresholdWindow The valid range is 1 to 1,000,000. The default is 1. Version 7.2 Mediant 500 MSBR...
Page 160: Assigning Ids Policies
Mediant 500 MSBR Alarms Minor-Alarm Threshold Defines the threshold that if crossed a minor severity alarm is sent. minor-alrm-thr The valid range is 1 to 1,000,000. A value of 0 or -1 means not defined. [IDSRule_MinorAlarmThres hold] Major-Alarm Threshold Defines the threshold that if crossed a major severity alarm is sent.
Page 161 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 7.2 Mediant 500 MSBR...
Page 162: Viewing Ids Alarms
Mediant 500 MSBR Proxy Set ID Assigns a Proxy Set(s) to the IDS Policy. This indicates the Proxy Sets from where the attacks are coming from. The following syntax proxy-set is supported: [IDSMatch_ProxySet]  A comma-separated list of Proxy Set IDs (e.g., 1,3,4) ...
Page 163 Figure 16-8: Syslog Message Example with IDS Alarms and Notifications The table below lists the Syslog text messages per malicious event: Table 16-4: Types of Malicious Events and Syslog Text String Reason Description Syslog String TLS authentication failure abuse-tls-auth-fail Connection Abuse Version 7.2 Mediant 500 MSBR...
Page 164 Mediant 500 MSBR   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- policy  Basic headers not present  malformed-miss-  Content length header not present (for TCP) header ...
Page 165: Media
To suppress the remaining residual echo, a Non Linear Processor (NLP) is used, as well as a double-talk (two people speak at the same time) detector that prevents false adaptation during near-end speech. Version 7.2 Mediant 500 MSBR...
Page 166: Fax And Modem Capabilities
Mediant 500 MSBR The following procedure describes how to configure echo cancellation through the Web interface:  To configure echo cancellation: Configure line echo cancellation: Open the Voice Settings page (Setup menu > Signaling & Media tab > Media folder > Voice Settings).
Page 167: Fax Relay Mode
In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal the terminating device negotiates T.38 capabilities using a Re-INVITE message. If the far- end device doesn't support T.38, the fax fails. In this mode, the 'Fax Transport Mode' parameter (FaxTransportMode) is ignored. Version 7.2 Mediant 500 MSBR...
Page 168 Mediant 500 MSBR  To configure T.38 mode using SIP Re-INVITE messages: Open the Gateway General Settings page (Setup menu > Signaling & Media tab > Gateway folder > Gateway General Settings), and then from the 'Fax Signaling Method' drop-down list (IsFaxUsed), select T.38 Relay: Figure 17-3: Configuring Fax Signaling to T.38...
Page 169 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 170: Fax / Modem Transport Mode
Mediant 500 MSBR 17.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 171: Fax/Modem Bypass Mode
Set the 'V.23 Modem Transport Type' parameter to Enable Bypass (V23ModemTransportType = 2). Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Version 7.2 Mediant 500 MSBR...
Page 172: 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 173: Fax / Modem Transparent With Events Mode
13, and to enable echo cancellation for fax and disable it for modem.  To configure fax / modem transparent mode: Open the Gateway General Settings page (Setup menu > Signaling & Media tab > Version 7.2 Mediant 500 MSBR...
Page 174: Rfc 2833 Ans Report Upon Fax/Modem Detection
Mediant 500 MSBR Gateway folder > Gateway General Settings), and then from the 'Fax Signaling Method' drop-down list (IsFaxUsed), select No Fax. On the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0).
Page 175: Bypass Mechanism For V.34 Fax Transmission
Set the 'V.22 Modem Transport Type' parameter to Enable Bypass (V22ModemTransportType = 2). Set the 'V.23 Modem Transport Type' parameter to Enable Bypass (V23ModemTransportType = 2). Set the 'V.32 Modem Transport Type' parameter to Enable Bypass (V32ModemTransportType = 2). Version 7.2 Mediant 500 MSBR...
Page 176: Relay Mode For T.30 And V.34 Faxes
Mediant 500 MSBR Set the 'V.34 Modem Transport Type' parameter to Enable Bypass (V34ModemTransportType = 2). Set the ini file parameter, V34FaxTransportType to 2 (Bypass). 17.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.
Page 177 Content-Length: 433 o=AudiocodesGW 1938931006 1938930708 IN IP4 10.8.6.55 s=Phone-Call c=IN IP4 10.8.6.55 t=0 0 m=audio 6010 RTP/AVP 18 97 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 telephone-event/8000 a=fmtp:97 0-15 a=ptime:20 a=sendrecv m=image 6012 udptl t38 a=T38FaxVersion:3 a=T38MaxBitRate:33600 a=T38FaxMaxBuffer:1024 Version 7.2 Mediant 500 MSBR...
Page 178: Modem Relay
V.150.1 modem relay is applicable only to the Gateway application. • The V.150.1 feature has been tested with certain IP phones. For more details, please contact your AudioCodes sales representative. • The V.150.1 SSE Tx payload type is according to the offered SDP of the remote side.
Page 179: Simultaneous Negotiation Of Fax (T.38) And Modem (V.150.1) Relay
(e.g., fax relay over IP using T.38). The preferred V.152 transport method is indicated by the SDP ‘pmft’ attribute. Omission of this attribute in the SDP content means that VBD mode is the preferred transport mechanism for voice-band data. Version 7.2 Mediant 500 MSBR...
Page 180: Configuring Rtp/Rtcp Settings
Mediant 500 MSBR 17.3 Configuring RTP/RTCP Settings This section describes configuration relating to Real-Time Transport Protocol (RTP) and RTP Control Protocol (RTCP). 17.3.1 Configuring the Dynamic Jitter Buffer Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate, voice quality is perceived as good.
Page 181: Comfort Noise Generation
This feature is applicable only to the Gateway application. 17.3.3 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint. The methods and their configuration can be configured on the DTMF Version 7.2 Mediant 500 MSBR...
Page 182 Mediant 500 MSBR & Dialing page (Setup menu > Signaling & Media tab > Gateway > DTMF & Supplementary > DTMF & Dialing): Figure 17-9: Configuring DTMF Transport  Using INFO message according to Nortel IETF draft: DTMF digits are sent to the remote side in INFO messages.
Page 183: Configuring Rfc 2833 Payload
The consecutive port offset from the RTP port for RTCP and T.38 traffic is one and two, respectively. For example, if the voice session uses RTP port 6000, the device allocates ports 6001 and 6002 for RTCP and T.38, respectively. However, you can configure the Version 7.2 Mediant 500 MSBR...
Page 184: Event Detection And Notification Using X-Detect Header
Mediant 500 MSBR device to use the same port for RTP and T.38 packets, by configuring the T38UseRTPPort parameter to 1. Within the port range, the device allocates the UDP ports per media channel (leg) in "jumps" (spacing) of 10. For example, if the port range starts at 6000 and the UDP port spacing is 10, the available ports are 6000, 6010, 6020, 6030, and so on.
Page 185 For SBC calls, event detection is enabled using the IPProfile_SBCHandleXDetect parameter in the IP Profiles table (see Configuring IP Profiles on page 404). Table 17-1: Supported X-Detect Event Types Event Subtype Description and Required Configuration Type Version 7.2 Mediant 500 MSBR...
Page 186: Sit Event Detection
Mediant 500 MSBR  Voice (live voice) Event detection using the AMD feature. For more information, see Answering Machine Detection  Automata (answering machine) (AMD) on page 190.  Silence (no voice)  Unknown  Beep (greeting message of answering machine) ...
Page 187: Detecting Answering Machine Beeps
(Tone Type #46) that is also defined in the installed CPT file and the received INVITE message contains an X-Detect header with the value "Request=CPT": X-Detect: Request=CPT For more information on the CPT file, see Call Progress Tones File on page 773. Version 7.2 Mediant 500 MSBR...
Page 188: Sip Call Flow Examples Of Event Detection And Notification
Mediant 500 MSBR The device reports beep detections to application servers, by sending a SIP INFO message that contains a body with one of the following values, depending on the method used for detecting the beep:  AMD-detected Beep: Type= AMD SubType= Beep ...
Page 189 The device detects the beep of an answering machine and sends an INFO message to the remote party: 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 Version 7.2 Mediant 500 MSBR...
Page 190: Answering Machine Detection (Amd)
AudioCodes sales representative for more information on this service. You will be typically required to provide AudioCodes with a database of recorded voices (calls) in the language on which the device's AMD feature can base its voice detector algorithms.
Page 191 Interferences, for example, could include background noises of other people talking, spikes, and car noises. Once you have provided AudioCodes with your database of recordings, AudioCodes compiles it into a loadable file. For a brief description of the file format and for installing the file on the device, see AMD Sensitivity File on page 795.
Page 192: Configuring Amd
Mediant 500 MSBR Table 17-4: Approximate AMD High Detection Sensitivity - Parameter Suite 1 (Based on North American English) Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 0 (Best for Answering Machine) 15 (Best for Live Calls) 17.5.1 Configuring AMD...
Page 193: Enabling Ip-To-Tel Call Disconnection Upon Detection Of Answering Machine
Open the Gateway Advanced Settings page (Setup menu > Signaling & Media tab > Gateway folder > Gateway Advanced Settings). Figure 17-12: Enabling Disconnection upon Answering Machine Detection From the 'AMD Mode' drop-down list, select Disconnect on AMD, and then click Apply. Version 7.2 Mediant 500 MSBR...
Page 194: Automatic Gain Control (Agc)
Mediant 500 MSBR Note: The feature is applicable only to digital interfaces. 17.6 Automatic Gain Control (AGC) Automatic Gain Control (AGC) adjusts the energy of the output signal to a required level (volume). This feature compensates for near-far gain differences. AGC estimates the energy of the incoming signal from the IP or Tel, determined by the 'AGC Redirection' parameter, calculates the essential gain, and then performs amplification.
Page 195 'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. The parameter can either be the global parameter or per IP Profile. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 196: Configuring Media (Srtp) Security
Mediant 500 MSBR 17.7 Configuring Media (SRTP) Security The device supports Secured RTP (SRTP) according to RFC 3711. SRTP is used to encrypt RTP and RTCP transport for protecting VoIP traffic. SRTP requires a cryptographic key exchange mechanism to negotiate the keys. To negotiate the keys, the device...
Page 197 Open the Media Security page (Setup menu > Signaling & Media tab > Media folder > Media Security). Figure 17-14: Configuring Media Security From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP. Version 7.2 Mediant 500 MSBR...
Page 198 Mediant 500 MSBR Configure the other SRTP parameters as required. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. User's Manual Document #: LTRT-10375...
Page 199: Services
Session (RS) from the Session Recording Client (SRC), which is on the path of the Communication Session (CS), to a Session Recording Server (SRS) at the recording equipment. The device functions as the SRC, sending recording sessions to a third-party SRS, as shown in the figure below. Version 7.2 Mediant 500 MSBR...
Page 200 Mediant 500 MSBR The device can record calls between two IP Groups, or between an IP Group and a Trunk Group for Gateway calls. The type of calls to record can be specified by source and/or destination prefix number or SIP Request-URI, as well as by call initiator. The side ("leg") on which the recording is done must be specified.
Page 201 SRS in the SRS redundancy group). For the SRS redundancy license, you would need to order 100 SIPRec Redundancy sessions to enable the SRS redundancy feature and support the number of recorded sessions. For more information and for ordering the feature, please contact your AudioCodes sales representative. Version 7.2 Mediant 500 MSBR...
Page 202 Mediant 500 MSBR The device initiates a recording session by sending an INVITE message to the SRS when the recorded call is connected. The SIP From header contains the identity of the SRC and the To header contains the identity of the SRS. The SDP in the INVITE contains: ...
Page 203: Enabling Sip-Based Media Recording
<associate-time>2010-01-24T01:11:57Z</associate-time> <recv>00000000-0000-0000-0000-1CF23A36C4E3</recv> <send>00000000-0000-0000-0000-BF583A36C4E3</send> </participant> <stream id="00000000-0000-0000-0000-1CF23A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>1</label> </stream> <stream id="00000000-0000-0000-0000-BF583A36C4E3" session="0000- 0000-0000-0000-00000000d0d71a52"> <label>2</label> </stream> </recording> --boundary_ac1fffff85b— 18.1.1 Enabling SIP-based Media Recording The following procedure describes how to enable the SIP-based media Recording feature. Version 7.2 Mediant 500 MSBR...
Page 204: Configuring Sip Recording Rules
Mediant 500 MSBR  To enable SIP-based media recording: Open the SIP Recording Settings page (Setup menu > Signaling & Media tab > SIP Recording folder > SIP Recording Settings). Figure 18-2: Enabling SIPRec From the 'SIP Recording Application' drop-down list, select Enable.
Page 205 By default, all source numbers or URIs are defined (*). [SIPRecRouting_Recorded SourcePrefix] Recorded Destination Defines calls to record based on destination number or URI. Prefix By default, all destination numbers or URIs are defined (*). recorded-dst-prefix [SIPRecRouting_Recorded DestinationPrefix] Version 7.2 Mediant 500 MSBR...
Page 206: Configuring Sip User Part For Srs
Mediant 500 MSBR Peer IP Group Defines the peer IP Group that is participating in the call. peer-ip-group-name By default, all IP Groups are defined (Any). [SIPRecRouting_PeerIPGr oupName] Peer Trunk Group ID Defines the peer Trunk Group that is participating in the call. To configure Trunk Groups, see Configuring Trunk Groups on page 485.
Page 207: Interworking Sip-Based Media Recording With Third-Party Vendors
SIP message, typically in the INVITE and the first 18x response. If the device receives a SIP message with Genesys SIP header, it adds the header's information to AudioCodes' proprietary tag in the XML metadata of the SIP INVITE that it sends to the recording server, as shown below: <ac:GenesysUUID...
Page 208: Enabling Radius Services
Mediant 500 MSBR 18.2.1 Enabling RADIUS Services Before you can implement any RADIUS services, you must enable the RADIUS feature, as described in the procedure below.  To enable RADIUS: Open the Authentication Server page (Setup menu > Administration tab > Web &...
Page 209 Open the RADIUS Servers table (Setup menu > IP Network tab > RADIUS & LDAP folder > RADIUS Servers). Click New; the following dialog box appears: Figure 18-5: RADIUS Servers Table - Add Dialog Box Version 7.2 Mediant 500 MSBR...
Page 210: Configuring Interface For Radius Communication
Mediant 500 MSBR Configure a RADIUS server according to the parameters described in the table below. Click Apply. Table 18-2: RADIUS Servers Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [RadiusServers_Index] Note: Each row must be configured with a unique index.
Page 211: Configuring Radius Packet Retransmission
Vendor ID (as registered with the Internet Assigned Numbers Authority or IANA). The device's default vendor ID is 5003 which can be changed, as described in the following procedure. For an example of using the Vendor ID, see Setting Up a Third-Party RADIUS Version 7.2 Mediant 500 MSBR...
Page 212: Radius-Based Management User Authentication
Mediant 500 MSBR Server on page 213. The procedure is applicable to both RADIUS-based user authentication and RADIUS-based accounting. Note: The Vendor ID must be the same as the Vendor ID set on the third-party RADIUS server. See the example for setting up a third-party RADIUS server in Setting Up a Third-Party RADIUS Server on page 213.
Page 213: Setting Up A Third-Party Radius Server
RADIUS server) • Vendor ID (configured on the device in Configuring the RADIUS Vendor ID on page 211) Below is an example of the clients.conf file (FreeRADIUS client configuration): # clients.conf - client configuration directives Version 7.2 Mediant 500 MSBR...
Page 214: Configuring Radius-Based User Authentication
RADIUS servers, see Configuring Management User Accounts on page 71. # AudioCodes VSA dictionary VENDOR AudioCodes 5003 ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes VALUE ACL-Auth-Level ACL-Auth-UserLevel 50 VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100 VALUE ACL-Auth-Level ACL-Auth-SecurityAdminLevel 200 Define the list of users authorized to use the device, using one of the password authentication methods supported by the server implementation.
Page 215 Always: First attempts to authenticate the user using the Local Users table, but if not found, it authenticates the user with the RADIUS server. Figure 18-13: Local Users Table for Login Authentication Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 500 MSBR...
Page 216: Securing Radius Communication
Mediant 500 MSBR 18.2.6.3 Securing RADIUS Communication RADIUS authentication requires HTTP basic authentication (according to RFC 2617). However, this is insecure as the usernames and passwords are transmitted in clear text over plain HTTP. Thus, as digest authentication is not supported with RADIUS, it is recommended that you use HTTPS with RADIUS so that the usernames and passwords are encrypted.
Page 217 If the device finds a group, it assigns the user the corresponding access level and permits login; otherwise, login is denied. Once the LDAP response has been received (success or failure), the device ends the LDAP session. Version 7.2 Mediant 500 MSBR...
Page 218: Enabling The Ldap Service
Mediant 500 MSBR For both of the previously discussed LDAP services, the following additional LDAP functionality is supported:  Search method for searching DN object records between LDAP servers and within each LDAP server (see Configuring LDAP Search Methods). ...
Page 219 Click Apply. Table 18-3: LDAP Server Groups Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [LdapServerGroups_Ind Note: Each row must be configured with a unique index. Version 7.2 Mediant 500 MSBR...
Page 220: Configuring Ldap Servers
Mediant 500 MSBR Name Defines a descriptive name, which is used when associating the row in other tables. name The valid value is a string of up to 20 characters. [LdapServerGroups_Na Note: Each row must be configured with a unique name.
Page 221 Configure an LDAP server according to the parameters described in the table below. Click Apply. Table 18-4: LDAP Servers Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [LdapConfiguration_Inde Note: Each row must be configured with a unique index. Version 7.2 Mediant 500 MSBR...
Page 222 Mediant 500 MSBR LDAP Servers Group Assigns the LDAP server to an LDAP Server Group, configured in the LDAP Server Groups table (see Configuring LDAP Server Groups on server-group page 218). [LdapConfiguration_Gro Note:  The parameter is mandatory and must be set before configuring the other parameters in the table.
Page 223 For example, $. Note:  The parameter is mandatory.  By default, the device sends the password in clear-text format. You can enable the device to encrypt the password using TLS (see the 'Use SSL' parameter below). Version 7.2 Mediant 500 MSBR...
Page 224: Configuring Ldap Dns (Base Paths) Per Ldap Server
Mediant 500 MSBR LDAP Bind DN Defines the LDAP server's bind Distinguished Name (DN) or username.  bind-dn LDAP-based SIP queries: The DN is used as the username during connection and binding to the LDAP server. The DN is used to [LdapConfiguration_Lda uniquely name an AD object.
Page 225: Configuring The Ldap Search Filter Attribute
"SueM".  Attribute (e.g., "memberOf") to return from objects that match the filter criteria: The attribute is configured by the 'Management Attribute' parameter in the LDAP Servers table (see Configuring LDAP Servers on page 220). Version 7.2 Mediant 500 MSBR...
Page 226: Configuring Access Level Per Management Groups Attributes
Mediant 500 MSBR Therefore, the LDAP response includes only the groups of which the specific user is a member. Note: • 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.
Page 227 Management LDAP Groups link located below the table; the Management LDAP Groups table opens. Click New; the following dialog box appears: Figure 18-20: Management LDAP Groups Table - Add Dialog Box Configure a group name(s) with a corresponding access level according to the Version 7.2 Mediant 500 MSBR...
Page 228: Configuring The Device's Ldap Cache
Mediant 500 MSBR parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 18-6: Management LDAP Groups Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [MgmntLDAPGroups_Gr Note: Each row must be configured with a unique index.
Page 229 Version 7.2 Mediant 500 MSBR...
Page 230: Refreshing The Ldap Cache
Mediant 500 MSBR Note: • The LDAP Cache feature is applicable only to LDAP-based SIP queries (Control). • The maximum LDAP cache size is 10,000 entries. • The device can save up to six LDAP Attributes in the cache per searched LDAP key.
Page 231 (e.g., telephoneNumber=1004). Click Refresh; if a request with the specified key exists in the cache, a request is sent to the LDAP server for the Attributes associated in the cache with the search key. Version 7.2 Mediant 500 MSBR...
Page 232: Clearing The Ldap Cache
Mediant 500 MSBR 18.3.8.2 Clearing the LDAP Cache You can remove (clear) all LDAP entries in the device's LDAP cache for a specific LDAP Server Group, as described in the following procedure.  To clear the LDAP cache: Open the LDAP Settings page (Setup menu > IP Network tab > RADIUS & LDAP folder >...
Page 233: Ldap-Based Login Authentication Example
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). The LDAP server's entry data structure schema in the example is as follows: Version 7.2 Mediant 500 MSBR...
Page 234 Mediant 500 MSBR  DN (base path): OU=testMgmt,OU=QA,DC=testqa,DC=local. The DN path to search for the username in the directory is shown below: Figure 18-26: Base Path (DN) in LDAP Server User's Manual Document #: LTRT-10375...
Page 235 (where the attribute's value equals the username): Figure 18-27: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 18-28: User's memberOf Attribute Version 7.2 Mediant 500 MSBR...
Page 236 Mediant 500 MSBR  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 18-29: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
Page 237 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 226): Figure 18-34: Configuring Management Group Attributes for Determining Access Level Version 7.2 Mediant 500 MSBR...
Page 238: Enabling Ldap Searches For Numbers With Characters
Mediant 500 MSBR 18.3.11 Enabling LDAP Searches for Numbers with Characters Typically, the device performs LDAP searches in the AD for complete numbers where the digits are adjacent to one another (e.g., 5038234567). However, if the number is defined in the AD with characters (such as spaces, hyphens and periods) separating the digits (e.g.,...
Page 239 "OCS" (OCS:<Skype for Business_number>): used to match a routing rule based on query results of the Skype for Business client number (MSLDAPOCSNumAttributeName) • "PBX" (PBX:<PBX_number>): used to match a routing rule based on query results of the PBX / IP PBX number (MSLDAPPBXNumAttributeName) Version 7.2 Mediant 500 MSBR...
Page 240 Mediant 500 MSBR • "MOBILE" (MOBILE:<mobile_number>): used to match a routing rule based on query results of the mobile number (MSLDAPMobileNumAttributeName) • "LDAP_ERR": used to match a routing rule based on a failed query result when no attribute is found in the AD Note: These prefixes are involved only in the routing and manipulation processes;...
Page 241: Configuring Ad-Based Routing Rules
If you are using the device's local LDAP cache, see Configuring the Device's LDAP Cache on page 228 for the LDAP query process. 18.3.12.2 Configuring AD-Based Routing Rules The following procedure describes how to configure outbound IP routing based on LDAP queries. Version 7.2 Mediant 500 MSBR...
Page 242 Mediant 500 MSBR  To configure LDAP-based IP routing for Skype for Business: Configure the LDAP server parameters, as described in Configuring LDAP Servers on page 220. Configure the AD attribute names used in the LDAP query: Open the SIP Definitions General Settings page (Setup menu > Signaling &...
Page 243 10.33.45.100) upon successful AD query result for the Mobile attribute.  Rule 5: Sends call to IP address of device (10.33.45.80) if AD query failure (e.g., no response from LDAP server or attribute not found). Version 7.2 Mediant 500 MSBR...
Page 244: Querying The Ad For Calling Name
Mediant 500 MSBR  Rule 6: Sends query for original destination number of received call to the LDAP server.  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases •...
Page 245: Least Cost Routing
The below table shows an example of call cost when taking into consideration call duration. This example shows four defined Cost Groups and the total call cost if the average call duration is 10 minutes: Version 7.2 Mediant 500 MSBR...
Page 246 Mediant 500 MSBR Table 18-11: Call Cost Comparison between Cost Groups for different Call Durations Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes 80.3 If four matching routing rules are located in the routing table and each one is assigned a different Cost Group as listed in the table above, then the rule assigned Cost Group "D"...
Page 247: Configuring Lcr
Configure Time Bands for a Cost Group - see Configuring Time Bands for Cost Groups on page 249. Assign Cost Groups to outbound IP routing rules - see Assigning Cost Groups to Routing Rules on page 250. Version 7.2 Mediant 500 MSBR...
Page 248: Configuring Cost Groups
Mediant 500 MSBR 18.4.2.1 Configuring Cost Groups The Cost Groups table lets you configure up to 10 Cost Groups. A Cost Group defines a fixed call connection cost and a call rate (charge per minute). Once configured, you can configure Time Bands per Cost Group.
Page 249 Click Apply, and then save your settings to flash memory. Table 18-13: Time Band Table Description Parameter Description Index Defines an index number for the new table row. timeband-index Note: Each row must be configured with a unique index. [CostGroupTimebands_ TimebandIndex] Version 7.2 Mediant 500 MSBR...
Page 250: Assigning Cost Groups To Routing Rules
Mediant 500 MSBR Start Time Defines the day and time of day from when this time band is applicable. The format is DDD:hh:mm, where: start-time  DDD is the day of the week, represented by the first three letters of [CostGroupTimebands_ the day in upper case (i.e., SUN, MON, TUE, WED, THU, FRI, or...
Page 251  Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM.  QoS: Call routing based on QoS. For more information, see Configuring QoS-Based Routing by Routing Server on page 260.
Page 252 Mediant 500 MSBR Click New; the following dialog box appears: Figure 18-38: Remote Web Services Table - Add Dialog Box Configure a remote Web service according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.
Page 253 [2] Sticky Next = Similar to Sticky Primary, but if the primary host does not respond, the device sends the traffic to the next available host and continues sending traffic to this host even if the primary host becomes available again. Version 7.2 Mediant 500 MSBR...
Page 254 Mediant 500 MSBR Persistent Connection Defines whether the HTTP connection with the host remains open or is only opened per request. http-persistent-  connection [0] Disable = Connection is not persistent and closes when the device detects inactivity. The device uses HTTP keep-alive [HTTPRemoteServices_Pe messages to detect inactivity.
Page 255: Configuring Remote Http Hosts
In the table, select the required remote Web service index row, and then click the HTTP Remote Hosts link located below the table; the HTTP Remote Hosts table appears. Click New; the following dialog box appears: Figure 18-39: HTTP Remote Hosts Table - Add Dialog Box Version 7.2 Mediant 500 MSBR...
Page 256 Mediant 500 MSBR Configure an HTTP remote host according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 18-15: HTTP Remote Hosts Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row.
Page 257: Enabling Topology Status Services
18.5.3 Centralized Third-Party Routing Server You can employ a remote, third-party Routing server to handle call routing decisions in deployments consisting of multiple AudioCodes devices. The Routing server can be used to handle SBC, Tel-to-IP, and IP-to-Tel calls. Employing a Routing server replaces the...
Page 258 Mediant 500 MSBR route or reject the call. However, if for the initial request (first sent Get Route request for the call) the Routing server cannot find an appropriate route for the call or it does not respond, for example, due to connectivity loss (i.e., the Routing server sends an HTTP 404 "Not Found"...
Page 259 Configure the address and connection settings of the Routing server, referred to as a Remote Web Service and HTTP remote host (see Configuring Remote Web Services on page 250). You must configure the 'Type' parameter of the Remote Web Service to Version 7.2 Mediant 500 MSBR...
Page 260: Configuring Qos-Based Routing By Routing Server
Mediant 500 MSBR Routing, as shown in the following example: Figure 18-43: Configuring Remote Web Service for Routing Server SBC Calls: In the IP-to-IP Routing table, configure the 'Destination Type' parameter of the routing rule to Routing Server (see Configuring SBC IP-to-IP Routing Rules on...
Page 261: Http-Based Proxy Services
URL in a Web browser: http://<device's WAN IP address:port>/url prefix/ Define the IP address of the managed equipment (see Configuring HTTP Proxy Hosts on page 266). Version 7.2 Mediant 500 MSBR...
Page 262: Enabling The Http Proxy Application
 HTTP-based EMS Services for AudioCodes Equipment behind NAT: You can configure the device to act as an HTTP Proxy that enables AudioCodes EMS to manage AudioCodes equipment (such as IP Phones) over HTTP when the equipment is located behind NAT (e.g., in the LAN) and EMS is located in a public domain (e.g., in the WAN).
Page 263: Configuring Http Interfaces
The HTTP Interfaces table lets you configure up to 10 HTTP Interfaces. An HTTP Interface represents a local, listening interface for receiving HTTP/S requests from HTTP-based (Web) clients such as managed equipment (e.g., IP Phones) and/or AudioCodes EMS management tool for HTTP/S-based services.
Page 264 Mediant 500 MSBR Table 18-16: HTTP Interfaces Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [HTTPInterface_Index] Note:  Each row must be configured with a unique index.  The parameter is mandatory.
Page 265: Configuring Http Proxy Services
The valid value is a string of up to 40 characters. By default, no value [HTTPProxyService_Servic is defined. eName] Note:  Each row must be configured with a unique name.  The parameter is mandatory. Version 7.2 Mediant 500 MSBR...
Page 266: Configuring Http Proxy Hosts
Mediant 500 MSBR Listening Interface Assigns an HTTP Interface to the HTTP Proxy service. To configure HTTP Interfaces, see Configuring HTTP Interfaces on page 263. listening-int Note: The parameter is mandatory. [HTTPProxyService_Listen ingInterface] URL Prefix Defines the URL prefix that is used to access the managed equipment's embedded Web server.
Page 267 Protocol Defines the protocol type.  protocol [0] HTTP (default)  [1] HTTPS [HTTPProxyHost_Protocol] HTTP Port Defines the port of the managed equipment. http-port The default is 0. [HTTPProxyHost_Port] Note: The parameter is mandatory. Security Version 7.2 Mediant 500 MSBR...
Page 268: Configuring An Http-Based Ems Service
Mediant 500 MSBR TLS Context Assigns a TLS Context for the TLS connection with the HTTP Proxy host. tls-context By default, the default TLS Context (Index 0) is assigned. [HTTPProxyHost_TLSCont ext] To configure TLS Contexts, see Configuring TLS Certificate Contexts on page 117.
Page 269: E9-1-1 Support For Microsoft Skype For Business
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 Skype for Business and AudioCodes' device's ELIN interworking capabilities, which provides the SIP Trunk or ISDN (or CAMA) connectivity to the E9-1-1 emergency service provider. This section also Version 7.2...
Page 270: About E9-1-1 Services
The figure below illustrates the routing of an E9-1-1 call to the PSAP: The VoIP user dials 9-1-1. AudioCodes' ELIN device sends the call to the emergency service provider over the PSTN or SIP Trunk (PSAP server). The emergency service provider identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network.
Page 271: Microsoft Skype For Business And E9-1-1
Each client then caches this information. When the Skype for Business client dials 9-1-1, this location information is then included as part of the emergency call and used by the emergency service provider to route the call to the correct PSAP. Version 7.2 Mediant 500 MSBR...
Page 272 Mediant 500 MSBR The gathering of location information in the Skype for Business network is illustrated in the figure below: Figure 18-52: Microsoft Skype for Business Client Acquiring Location Information The Administrator provisions the LIS database with the location of each network element in the Enterprise.
Page 273: Adding Elins To The Location Information Server
(CSV) file containing the column formats listed in the table below. Table 18-20: Columns in the LIS Database Network Element Columns <BSSID>,<Description>,<Location>,<CompanyName>,<HouseNu mber>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,< Wireless access point StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Co untry> <Subnet>,<Description>,<Location>,<CompanyName>,<HouseNu mber>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName>,< Subnet StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Co untry> <ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location >,<CompanyName>,<HouseNumber>,<HouseNumberSuffix>,…< Port PreDirectional>,<StreetName>,<StreetSuffix>,<PostDirectional>,< City>,<State>,<PostalCode>,<Country> <ChassisID>,<Description>,<Location>,<CompanyName>,<House Number>,<HouseNumberSuffix>,<PreDirectional>,…<StreetName Switch >,<StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>, <Country> Version 7.2 Mediant 500 MSBR...
Page 274: Passing Location Information To The Pstn Emergency Provider
Mediant 500 MSBR For the ELIN number to be included in the SIP INVITE (XML-based PIDF-LO message) sent by the Mediation Server to the ELIN device, the administrator must add the ELIN number to the <CompanyName> column (shown in the table above in bold typeface). As the ELIN device supports up to five ELINs per PIDF-LO, the <CompanyName>...
Page 275: Audiocodes Elin Device For Skype For Business E9-1-1 Calls To Pstn
PSAP, based on ELIN-address match lookup in the emergency service provider's ALI database. The figure below illustrates an AudioCodes ELIN device deployed in the Skype for Business environment for handling E9-1-1 calls between the Enterprise and the emergency service provider.
Page 276: Detecting And Handling E9-1-1 Calls
Mediant 500 MSBR 18.7.3.1 Detecting and Handling E9-1-1 Calls The ELIN device identifies E9-1-1 calls and translates their incoming E9-1-1 calling numbers into ELIN numbers, sent toward the PSAP. The device handles the received E9- 1-1 calls as follows: The device identifies E9-1-1 calls if the incoming SIP INVITE message contains a PIDF-LO XML message body.
Page 277 30684 RTP/AVP 114 111 112 115 116 4 3 8 0 106 97 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000 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"?> Version 7.2 Mediant 500 MSBR...
Page 278: Pre-Empting Existing Calls For E9-1-1 Calls
Mediant 500 MSBR <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 55550199@contoso.com;user=phone</ms:ConferenceUri><ms:ConferenceMo de>twoway</ms:ConferenceMode><LocationPolicyTagID xmlns="urn:schema:Rtc.Lis.LocationPolicyTagID.2008">user- tagid</LocationPolicyTagID ></ms:msftE911PidfExtn></status><timestamp>1991-09- 22T13:37:31.03</timestamp></tuple></presence> ------=_NextPart_000_4A6D_01CAB3D6.7519F890-- 18.7.3.2 Pre-empting Existing Calls for E9-1-1 Calls If the ELIN device receives an E9-1-1 call from the IP network and there are unavailable...
Page 279: Selecting Elin For Multiple Calls Within Same Erl
PSAP. For example, if E9-1-1 caller using ELIN 4257275678 was terminated at 11:01 and E9-1-1 caller using ELIN 4257275670 was terminated at 11:03, then the device selects ELIN 4257275678. In this scenario, multiple E9-1-1 calls are sent with the same ELIN. Version 7.2 Mediant 500 MSBR...
Page 280: Location Based Emergency Routing
Location-based emergency routing is applicable only to the Gateway application. 18.7.4 Configuring AudioCodes ELIN Device This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Skype for Business environment. 18.7.4.1 Enabling the E9-1-1 Feature By default, the ELIN device feature for E9-1-1 emergency call handling in a Skype for Business environment is disabled.
Page 281: Configuring The Sip Release Cause Code For Failed E9-1-1 Calls
Gateway folder > Gateway Advanced Parameters). From 'Emergency Special Release Cause' drop-down list (EmergencySpecialReleaseCause), select Enable. Figure 18-55: Configuring SIP Release Code for Failed E9-1-1 Calls Click Apply. Note: The feature is applicable only to the Gateway application (digital interfaces). Version 7.2 Mediant 500 MSBR...
Page 282: Configuring Sbc Ip-To-Ip Routing Rule For E9-1-1
Mediant 500 MSBR 18.7.4.4 Configuring SBC IP-to-IP Routing Rule for E9-1-1 To route incoming E9-1-1 calls to the emergency service provider's PSAP server, you need to configure routing rules in the IP-to-IP Routing table for routing between the emergency callers' IP Group and the PSAP server's IP Group. The only special configuration is to define the emergency number (e.g., 911) in the 'Destination Username Prefix' parameter of...
Page 283: Viewing The Elin Table
Microsoft Skype for Business Presence of Third- Party Endpoints Microsoft presence capability allows Skype for Business users to know the status (e.g., "Available" or "Do Not Disturb") of their contacts. Presence status of contacts is displayed Version 7.2 Mediant 500 MSBR...
Page 284 Mediant 500 MSBR on the user's Skype for Business endpoint. Presence information of Skype for Business endpoints (such as Skype for Business desktop client) is handled solely by the Skype for Business Server, without any intervention of the device. However, when third-party (non- Skype for Business) endpoint devices (e.g., mobile phone or PBX phone) are used by the...
Page 285 SIP-ETag value of last 200 OK) and Expires header value set to "0", as shown in the following example: PUBLISH sip:john.doe@sfb.example SIP/2.0 From: <sip:john.doe@sfb.example>;tag=1c1654434948 To: <sip:john.doe@sfb.example> CSeq: 1 PUBLISH Contact: <sip:john.doe@10.33.221.57:5061;transport=tls> Event: presence Expires: 0 User-Agent: sur1-vg1.ecarecenters.net/v.7.20A.001.080 SIP-If-Match: 2545777538-1-1 Content-Length: 0 Version 7.2 Mediant 500 MSBR...
Page 286: Configuring Skype For Business Server For Presence
Mediant 500 MSBR The following figure shows a basic illustration of the device's integration into Microsoft Skype for Business Presence feature for third-party endpoints. Figure 18-59: Basic Example of Microsoft Presence for Third-Party Endpoints 18.8.1 Configuring Skype for Business Server for Presence On the Skype for Business Server side, you need to define the device in the Skype for Business Topology as a Trusted Application.
Page 287 Make sure the port number matches the port number configured on the device. Enable and Publish the Skype for Business Server 2015 Topology Run the following cmdlet to publish and enable your new topology: Enable-CsTopology Version 7.2 Mediant 500 MSBR...
Page 288: Configuring The Device For Skype For Business Presence
Mediant 500 MSBR 18.8.2 Configuring the Device for Skype for Business Presence The following procedure describes how to configure the device for notifying Skype for Business Server of presence status of Skype for Business users when making and receiving calls using third-party, endpoint devices. To help you understand the configuration, the following lists in chronological order the main processing steps: The device receives an incoming call.
Page 289 IP Groups, see Configuring IP Groups on page 333. For Gateway calls: Assign the group of Call Setup Rules (Set ID) that you configured in Step 7 (above) to your Tel-to-IP Routing rules (see Configuring Tel-to-IP Routing Rules on page 495). Version 7.2 Mediant 500 MSBR...
Page 290 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 291: 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 292: 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 293: Configuring Quality Of Experience Profiles
The device also uses hysteresis to determine whether the threshold has indeed being crossed. Hysteresis defines the amount of fluctuation from the threshold in order for the threshold to be considered as crossed (i.e., change in color state). Hysteresis is used to Version 7.2 Mediant 500 MSBR...
Page 294  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). To configure the SEM server's address, see Configuring the SEM Server on page 291.
Page 295 Note: Each row must be configured with a unique index. Profile Name Defines a descriptive name, which is used when associating the row in other tables. name The valid value is a string of up to 20 characters. [QOEProfile_Name] Version 7.2 Mediant 500 MSBR...
Page 296 Mediant 500 MSBR Sensitivity Level Defines the pre-configured threshold profile to use.  sensitivity-level [0] User Defined = Need to define thresholds per monitored parameter in the Quality of Experience Color Rules table. [QOEProfile_SensitivityLevel]  [1] Low = Pre-configured low sensitivity thresholds.
Page 297 For example, if you configure the 'Minor Threshold (Yellow)' parameter to 4 and the 'Minor Hysteresis (Yellow)' parameter to 0.1 (for MOS), the device considers a threshold crossing to Green only if the MOS crosses 4.1 (i.e., 4 + 0.1). Version 7.2 Mediant 500 MSBR...
Page 298: Configuring Bandwidth Profiles
Mediant 500 MSBR Major Threshold (Red) Defines the Major threshold value, which is the upper threshold located between the Yellow and Red states. To consider a major-threshold-red threshold crossing: [QOEColorRules_MajorThreshol  Increase in severity (i.e., Yellow to Red): Only this value is used.
Page 299 Minor threshold only (i.e., hysteresis is not used). Green to Red (Major alarm) The change occurs if the current bandwidth 64,000 Kbps crosses the configured Major threshold only (i.e., hysteresis is not used). Version 7.2 Mediant 500 MSBR...
Page 300 Mediant 500 MSBR Yellow to Red (Major alarm) The change occurs if the current bandwidth 64,000 Kbps crosses the configured Major threshold only (i.e., hysteresis is not used). Red to Yellow (Minor alarm) The change occurs if the current bandwidth...
Page 301  Decrease in severity (Red to Green, or Yellow to Green): This value is used with the hysteresis, configured by the 'Hysteresis' parameter (see below). Note: The parameter applies to all your configured bandwidths. Version 7.2 Mediant 500 MSBR...
Page 302: Configuring Quality Of Service Rules
Mediant 500 MSBR Hysteresis Defines the amount of fluctuation (hysteresis) from the configured bandwidth threshold in order for the threshold to be hysteresis considered as crossed (i.e., avoids false reports of threshold [BWProfile_Hysteresis] crossings). The hysteresis is used only to determine threshold crossings when severity is reduced (i.e., from Red to Yellow,...
Page 303 Defines an index number for the new table row. [QualityOfServiceRules_Index] Note: Each row must be configured with a unique index. IP Group Assigns an IP Group. The rule applies to all calls belonging to the IP Group. ip-group-name [QualityOfServiceRules_IPGroup Name] Version 7.2 Mediant 500 MSBR...
Page 304 Mediant 500 MSBR Rule Metric Defines the performance monitoring call metric to which the rule applies if the metric's threshold is crossed. rule-metric  [0] Voice Quality = (Default) The device calculates MOS of [QualityOfServiceRules_RuleMet calls and if the threshold is crossed (i.e., poor quality), the...
Page 305 'Rule Metric' parameter) if the rule is matched. alt-ip-profile-name By default, no value is defined. [QualityOfServiceRules_AltIPProf ileName] Note: The parameter is applicable only if the 'Rule Action' parameter is configured to Alternative IP Profile. Version 7.2 Mediant 500 MSBR...
Page 306 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 307: Control Network
You can also configure it through ini file (CpMediaRealm) or CLI (configure voip > realm).  To configure a Media Realm: Open the Media Realms table (Setup menu > Signaling & Media tab > Core Entities folder > Media Realms). Version 7.2 Mediant 500 MSBR...
Page 308 Mediant 500 MSBR Click New; the following dialog box appears: Figure 20-1: Media Realms Table - Add Dialog Box Configure the Media Realm according to the parameters described in the table below. Click Apply. Table 20-1: Media Realms table Parameter Descriptions...
Page 309 6001 and 6002, respectively. However, you can configure the device to use the same port for RTP and T.38 packets, by configuring the T38UseRTPPort parameter to 1. For more information on local UDP port range, see Configuring RTP Base UDP Port on page 183. Version 7.2 Mediant 500 MSBR...
Page 310: Configuring Remote Media Subnets
Mediant 500 MSBR Default Media Realm Defines the Media Realm as the default Media Realm. The default Media Realm is used for SIP Interfaces and IP Groups for which you have not is-default assigned a Media Realm. [CpMediaRealm_IsDef  [0] No (default) ault] ...
Page 311 Open the Media Realms table (see Configuring Media Realms on page 307). Select the Media Realm row for which you want to add Remote Media Subnets, and then click the Remote Media Subnet link located below the table; the Remote Media Subnet table appears. Version 7.2 Mediant 500 MSBR...
Page 312 Mediant 500 MSBR Click New; the following dialog box appears: Figure 20-3: Remote Media Subnet Table - Add Dialog Box Configure the Remote Media Subnet according to the parameters described in the table below. Click Apply. Table 20-2: Remote Media Subnet Table Parameter Descriptions...
Page 313: Configuring Media Realm Extensions
Open the Media Realms table (see Configuring Media Realms on page 307). Select the Media Realm for which you want to add Remote Media Extensions, and then click the Media Realm Extension link located below the table; the Media Realm Extension table appears. Version 7.2 Mediant 500 MSBR...
Page 314 Mediant 500 MSBR Click New; the following dialog box appears: Figure 20-5: Media Realm Extension Table - Add Dialog Box Configure the Media Realm Extension according to the parameters described in the table below. Click Apply. Table 20-3: Media Realm Extension Table Parameter Descriptions...
Page 315: Configuring Srds
SRD, you can use the default SRD instead of creating a new one. When only one SRD is employed and you create other related configuration entities (e.g., SIP Interfaces), the default SRD is automatically assigned to the new configuration entity. Version 7.2 Mediant 500 MSBR...
Page 316 Mediant 500 MSBR Therefore, when employing a single-SRD configuration topology, there is no need to handle SRD configuration (i.e., transparent). SRDs are associated with the following configuration entities:  SIP Interface (mandatory) - see Configuring SIP Interfaces on page 325 ...
Page 317 Open the SRDs table (Setup menu > Signaling & Media tab > Core Entities folder > SRDs). Click New; the following dialog box appears: Figure 20-7: SRDs Table - Add Dialog Box Configure an SRD according to the parameters described in the table below. Version 7.2 Mediant 500 MSBR...
Page 318 Mediant 500 MSBR Click Apply. Table 20-4: SRDs table Parameter Descriptions Parameter Description General Index Defines an index for the new table row. [SRD_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.
Page 319 (i.e., Classification, Manipulation and Routing). Note:  The parameter is applicable only to calls belonging to User-type IP Groups.  The feature is not applicable to REGISTER requests. Version 7.2 Mediant 500 MSBR...
Page 320 Mediant 500 MSBR  The option, Accept Registered Users from Same Source [2] does not apply to registration refreshes. These requests are accepted even if the source address is different to that registered with the device.  When the device rejects a call, it sends a SIP 500 "Server Internal Error"...
Page 321: Filtering Tables In Web Interface By Srd
CPU, memory and interface allocations should be optimized so as not to waste resources for small-sized tenants on the one hand, and not to allocate too many instances for a single Version 7.2 Mediant 500 MSBR...
Page 322 Mediant 500 MSBR tenant/customer on the other. For example, it would be a waste to allocate a capacity of 100 concurrent sessions to a small tenant for which 10 concurrent sessions suffice. In a multi-tenant deployment, each tenant is represented by a dedicated SRD. The different Layer-3 networks (e.g., LAN IP-PBX users, WAN SIP Trunk, and WAN far-end users) of...
Page 323 To access a specific tenant view: # srd-view <SRD name> Once accessed, the tenant's name (i.e., SRD name) forms part of the CLI prompt, for example: # srd-view datacenter (srd-datacenter)#  To exit the tenant view: # no srd-view Version 7.2 Mediant 500 MSBR...
Page 324: Cloning Srds
Mediant 500 MSBR 20.2.3 Cloning SRDs You can clone (duplicate) existing SRDs. This is especially useful when operating in a multi-tenant environment and you need to add new tenants (SRDs). The new tenants can quickly and easily be added by simply cloning one of the existing SRDs. Once cloned, all you need to do is tweak configuration entities associated with the SRD clone.
Page 325: Color-Coding Of Srds In Web Interface
Tel-to-IP and IP-to-Tel calls. You can also configure various optional features for the SIP Interface such as assigning it a Media Realm, blocking calls received on the SIP Interface from users not registered with the device, and enabling direct media. Version 7.2 Mediant 500 MSBR...
Page 326 Mediant 500 MSBR Each SIP Interface can be associated with only one SRD. As the SRD configuration entity represents your VoIP deployment SIP network (Layer 5), you need to associate your SIP Interfaces with a specific SRD in order to represent your Layer-3 networks. For most deployments (except multi-tenant deployments), your SRD represents your entire network and thus, only one SRD is required.
Page 327 [1] Up = The SIP Interface element is displayed on the upper border of the view. For more information on the Topology view, see Building and Viewing SIP Entities in Topology View on page 356. Version 7.2 Mediant 500 MSBR...
Page 328 Mediant 500 MSBR Network Interface Assigns an IP network interface to the SIP Interface. network-interface By default, no value is defined. [SIPInterface_NetworkInt Note: The parameter is mandatory. erface] Application Type Defines the application for which the SIP Interface is used.
Page 329 Enables the SIP Interface to be used by a third-party routing server for call routing decisions. used-by-routing-server  [0] Not Used (default) [SIPInterface_UsedByRo  [1] Used utingServer] For more information on the third-party routing server feature, see Centralized Third-Party Routing Server on page 257. Version 7.2 Mediant 500 MSBR...
Page 330 Mediant 500 MSBR Pre-Parsing Manipulation Assigns a Pre-Parsing Manipulation Set to the SIP Interface. This lets you apply pre-parsing SIP message manipulation rules on any incoming SIP message received on this SIP Interface. pre-parsing-man- By default, no Pre-Parsing Manipulation Set is assigned.
Page 331 For outgoing calls: The assigned TLS Context is used if no TLS Context is configured for the Proxy Set associated with the call.  To configure TLS Contexts, see Configuring SSL/TLS Certificates on page 117. Version 7.2 Mediant 500 MSBR...
Page 332 Mediant 500 MSBR TLS Mutual Enables TLS mutual authentication for the SIP Interface (when the Authentication device acts as a server).  tls-mutual-auth [0] Disable = Device does not request the client certificate for TLS connection on the SIP Interface.
Page 333: Configuring Ip Groups
IP Group associated with the Proxy Set. The feature is configured using the IP Groups table's 'Classify by Proxy Set' parameter. For more information and recommended security guidelines, see the parameter's description, later in this section. Version 7.2 Mediant 500 MSBR...
Page 334 Mediant 500 MSBR  SBC application: Representing the source and destination of the call in IP-to-IP Routing rules (see Configuring SBC IP-to-IP Routing Rules on page 671).  SIP dialog registration and authentication (digest user/password) of specific IP Groups (Served IP Group, e.g., corporate IP-PBX) with other IP Groups (Serving IP Group, e.g., ITSP).
Page 335 [1] Up = The IP Group element is displayed on the upper border of the view. For more information on the Topology view, see Building and Viewing SIP Entities in Topology View on page 356. Version 7.2 Mediant 500 MSBR...
Page 336 Mediant 500 MSBR Type Defines the type of IP Group.  type [0] Server = Applicable when the destination address of the IP Group (e.g., ITSP, Proxy, IP-PBX, or Application server) is known. The [IPGroup_Type] address is configured by the Proxy Set that is associated with the IP Group.
Page 337 The valid value is a string of up to 100 characters. By default, no value is defined. Note:  If the parameter is not configured, the value of the global parameter, ProxyName is used instead (see Configuring Proxy and Registration Version 7.2 Mediant 500 MSBR...
Page 338 Mediant 500 MSBR Parameters on page 369).  The parameter overrides inbound message manipulation rules that manipulate the host name in Request-URI, To, and/or From SIP headers. If you configure the parameter and you want to manipulate the host name in any of these SIP headers, you must apply your...
Page 339 In other words, the same SIP dialog identifiers (tags, Call-Id and CSeq) occur on both legs (as long as no other configuration disrupts the CSeq compatibleness).  [2] Microsoft Server = Operating mode for the One-Voice Resiliency Version 7.2 Mediant 500 MSBR...
Page 340 Mediant 500 MSBR feature, whereby the device is deployed together with Skype for Business-compatible IP Phones at small remote branch offices in a Microsoft® Skype for Business™ environment. For more information on B2BUA and Stateful Proxy modes, see B2BUA and Stateful Proxy Operating Modes on page 628.
Page 341 Once classified, the device uses the parameter for routing the call. For example, if set to To, the URI in the To header of the incoming INVITE is used as a matching characteristic for classifying the call to an IP Group Version 7.2 Mediant 500 MSBR...
Page 342 Mediant 500 MSBR in the Classification table. Once classified, the device uses the URI in the To header as the destination.  [-1] Not Configured (default)  [0] From  [1] To  [2] Request-URI  [3] P-Asserted - First Header ...
Page 343 Quality of Experience QoE Profile Assigns a Quality of Experience Profile rule. qoe-profile By default, no value is defined. [IPGroup_QOEProfile] To configure Quality of Experience Profiles, see Configuring Quality of Experience Profiles on page 293. Version 7.2 Mediant 500 MSBR...
Page 344 Mediant 500 MSBR Bandwidth Profile Assigns a Bandwidth Profile rule. bandwidth-profile By default, no value is defined. [IPGroup_BWProfile] To configure Bandwidth Profiles, see Configuring Bandwidth Profiles on page 298. Message Manipulation Inbound Message Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the inbound leg.
Page 345 The Proxy Set's Hot-Swap feature (for proxy redundancy) is not supported for users that are already bound to a registrar. However, you can achieve proxy "hot-swap" for failed initial (non-bounded) REGISTER requests. If a failure response is received for the initial Version 7.2 Mediant 500 MSBR...
Page 346 Mediant 500 MSBR REGISTER request and the response’s code appears in the Alternative Routing Reasons table (see Configuring SIP Response Codes for Alternative Routing Reasons onn page 690), "hot-swap" to the other IP addresses of the Proxy Set is done until a success response is received from one of the addresses.
Page 347 (Read-only field) Displays the IP address of the IP Group entity Address (gateway) if registered with the device; otherwise, the field is blank. Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway). Version 7.2 Mediant 500 MSBR...
Page 348: Configuring Proxy Sets
Mediant 500 MSBR GW Group Registered (Read-only field) Displays whether the IP Group entity (gateway) is Status registered with the device ("Registered" or "Not Registered"). Note: The field is applicable only to Gateway-type IP Groups (i.e., the 'Type' parameter is configured to Gateway).
Page 349 Address link located below the table; the Proxy Address table opens. Click New; the following dialog box appears: Figure 20-11: Proxy Address Table - Add Dialog Box Configure the address of the Proxy Set according to the parameters described in the table below. Version 7.2 Mediant 500 MSBR...
Page 350 Mediant 500 MSBR Click Apply. Table 20-7: Proxy Sets Table and Proxy Address Table Parameter Description Parameter Description Assigns an SRD to the Proxy Set. voip-network proxy- Note: set > srd-id  The parameter is mandatory and must be configured first before you [ProxySet_SRDName can configure the other parameters in the table.
Page 351 TCP/TLS transport type, you can enable CRLF Keep-Alive feature, using the UsePingPongKeepAlive parameter.  If you enable this Proxy Keep-Alive feature, the device can operate with multiple proxy servers (addresses) for redundancy and load balancing (see the 'Proxy Load Balancing Method' parameter). Version 7.2 Mediant 500 MSBR...
Page 352 Mediant 500 MSBR Defines the interval (in seconds) between keep-alive messages sent by the Proxy Keep-Alive Time device when the Proxy Keep-Alive feature is enabled (see the 'Proxy Keep- Alive' parameter in this table). proxy-keep-alive-time The valid range is 5 to 2,000,000. The default is 60.
Page 353 More than one IP address has been configured for the Proxy Set.  The proxy address is not configured as an FQDN (only IP address).  SRV is disabled (see the DNSQueryType parameter).  The SRV response includes several records with a different Priority value. Version 7.2 Mediant 500 MSBR...
Page 354 Mediant 500 MSBR Min. Active Servers Defines the minimum number of proxies in the Proxy Set that must be for Load Balancing online for the device to consider the Proxy Set as online, when proxy load balancing is used. min-active-serv- The valid value is 1 to 15.
Page 355 30 IP addresses in the received list and ignores the rest. Proxy Address Table Index Defines an index number for the new table row. proxy-ip-index Note: Each row must be configured with a unique index. [ProxyIp_ProxyIpInde Version 7.2 Mediant 500 MSBR...
Page 356: Building And Viewing Sip Entities In Topology View
Mediant 500 MSBR Proxy Address Defines the address of the proxy. proxy-address Up to 10 addresses can be configured per Proxy Set. The address can be defined as an IP address in dotted-decimal notation (e.g., 201.10.8.1) or [ProxyIp_IpAddress] FQDN. You can also specify the port using the following format: ...
Page 357 (as shown in the figure below for callouts #1 and #2, respectively). For example, on the top border you can position all entities relating to WAN, and on the bottom border all entities relating to LAN. Version 7.2 Mediant 500 MSBR...
Page 358 Mediant 500 MSBR Item # Description By default, configuration entities are displayed on the bottom border. To define the position, use the 'Topology Location' parameter when configuring the entity, where Down is the bottom border and Up the top border: Figure 20-12: Configuration Postion in Topology View Configured SIP Interfaces.
Page 359 Configured IP Groups. Each IP Group is displayed using the following "IP Group [Server]" or "IP Group [User]" titled icon (depending on whether it's a Server- or User-type IP Group respectively), which includes the name and row index number (example of a Server-type): Version 7.2 Mediant 500 MSBR...
Page 360 Mediant 500 MSBR Item # Description If you hover your mouse over the icon, a pop-up appears displaying the following basic information (example): If you click the icon, a drop-down menu appears listing the following commands:  Edit: Opens a dialog box in the IP Groups table to modify the IP Group.
Page 361 Calls table where you can configure destination phone number manipulation rules for IP-to-Tel calls (see Configuring Number Manipulation Tables on page 523).  Routing: Opens the IP-to-Tel Routing table where you can configure IP-to-Tel routing rules (see Configuring IP-to-Tel Routing Rules on page 504). Version 7.2 Mediant 500 MSBR...
Page 362 Mediant 500 MSBR Item # Description  DTMF & Dialing: Opens the DTMF & Dialing page where you can configure DTMF and dialing related settings.  GW Settings: Opens the Gateway General Settings page where you can configure general gateway related settings.
Page 363: Sip Definitions
You can also configure it through ini file (Account) or CLI (configure voip > sip-definition account).  To configure an Account: Open the Accounts table (Setup menu > Signaling & Media tab > SIP Definitions folder > Accounts). Click New; the following dialog box appears: Version 7.2 Mediant 500 MSBR...
Page 364 Mediant 500 MSBR Configure an account according to the parameters described in the table below. Click Apply. Once you have configured Accounts, you can register or un-register them, as described below:  To register or un-register an Account: In the table, select the required Account entry row.
Page 365  register [0] No= (Default) The device only performs authentication (not registration). Authentication is typically done for INVITE messages sent to [Account_Register] the "serving" IP Group. If the device receives a SIP 401 (Unauthorized) in Version 7.2 Mediant 500 MSBR...
Page 366 Mediant 500 MSBR Parameter Description response to a sent INVITE, the device checks for a matching "serving" and "served" entry in the table. If a matching row exists, the device authenticates the INVITE by providing the corresponding MD5 authentication username and password to the "serving" IP Group.
Page 367 Defines the digest MD5 Authentication username. user-name The valid value is a string of up to 50 characters. [Account_Usernam Password Defines the digest MD5 Authentication password. password The valid value is a string of up to 50 characters. [Account_Password Version 7.2 Mediant 500 MSBR...
Page 368: Regular Registration Mode
Mediant 500 MSBR 21.1.1 Regular Registration Mode When you configure the registration mode in the Accounts table to Regular, the device sends REGISTER requests to the Serving IP Group. The host name (in the SIP From/To headers) and contact user (user in From/To and Contact headers) are taken from the configured Accounts table upon successful registration.
Page 369: Registrar Stickiness
Parameters Reference on page 983. To configure Proxy servers (Proxy Sets), see Configuring Proxy Sets on page 348. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Registration Status on page 869. Version 7.2 Mediant 500 MSBR...
Page 370: Sip Message Authentication Example
The REGISTER request is sent to a Registrar/Proxy server for registration: REGISTER sip:10.2.2.222 SIP/2.0 Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c17940 To: <sip: 122@10.1.1.200> Call-ID: 634293194@10.1.1.200 User-Agent: Sip-Gateway/Mediant 500 MSBR/v.7.20A.000.038 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Upon receipt of this request, the Registrar/Proxy returns a 401 Unauthorized response: SIP/2.0 401 Unauthorized...
Page 371 • 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 372: Configuring Call Setup Rules
Mediant 500 MSBR To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 Cseq: 1 REGISTER Date: Thu, 26 Jul 2012 09:34:42 GMT Server: Columbia-SIP-Server/1.17 Content-Length: 0 Contact: <sip:122@10.1.1.200>; expires="Thu, 26 Jul 2012 10:34:42 GMT"; action=proxy; q=1.00 Contact: <122@10.1.1.200:>; expires="Tue, 19 Jan 2038 03:14:07 GMT"; action=proxy; q=0.00 Expires: Thu, 26 Jul 2012 10:34:42 GMT 21.3...
Page 373 Condition: ldap.found exists Action Type: Exit Action Value: True  Correct: • Single rule: Condition: ldap.found !exists Action Type: Exit Action Value: False • Set of rules: Condition: ldap.found exists Action Type: Exit Action Value: True Version 7.2 Mediant 500 MSBR...
Page 374 Mediant 500 MSBR Condition: <leave it blank> Action Type: Exit Action Value: False Note: If the source and/or destination numbers are manipulated by the Call Setup rules, they revert to their original values if the device moves to the next routing rule.
Page 375 LDAP query or until the call is connected. Thus, the device does not need to re-query the same attributes. Row Role Determines which condition must be met in order for this rule to be performed. Version 7.2 Mediant 500 MSBR...
Page 376 Mediant 500 MSBR Parameter Description  row-role [0] Use Current Condition = The Condition configured for this rule must be matched in order to perform the configured action (default). [CallSetupRules_RowRole]  [1] Use Previous Condition = The Condition configured for the rule located directly above this rule in the Call Setup table must be matched in order to perform the configured action.
Page 377: Call Setup Rule Examples
(e.g., "telephoneNumber =5098"). If such an attribute is found, the device retrieves the name from the attribute record, "displayName" and uses this as the calling name in the incoming call. Version 7.2 Mediant 500 MSBR...
Page 378 Mediant 500 MSBR • Call Setup Rules table configuration: ♦ 'Rules Set ID': 2 ♦ 'Query Type': LDAP ♦ 'Query Target': LDAP-DC-CORP ♦ 'Search Key': ‘telephoneNumber=’ + param.call.src.user ♦ 'Attributes to Get': displayName ♦ 'Row Role': Use Current Condition ♦...
Page 379 Index 1:  'Destination Tag': dep-sales  'Destination IP Group': SALES ♦ Index 2:  'Destination Tag': dep-mkt  'Destination IP Group': MKT ♦ Index 3:  'Destination Tag': dep-rd  'Destination IP Group': RD Version 7.2 Mediant 500 MSBR...
Page 380 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 381: Sip Message Manipulation
Message Manipulation rule. The normalization feature removes unknown SIP message elements before forwarding the message. These elements can include SIP headers, SIP header parameters, and SDP body fields. The SIP message manipulation feature supports the following: Version 7.2 Mediant 500 MSBR...
Page 382 Mediant 500 MSBR  Manipulation on SIP message type (Method, Request/Response, and Response type)  Addition of new SIP headers  Removal of SIP headers ("black list")  Modification of SIP header components such as values, header values (e.g., URI...
Page 383 User's Manual 22. SIP Message Manipulation The figure below illustrates a SIP message manipulation example: Figure 22-2: SIP Header Manipulation Example Version 7.2 Mediant 500 MSBR...
Page 384 Mediant 500 MSBR Note: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide. • For the SBC application, Inbound message manipulation is done only after the Classification, inbound/outbound number manipulations, and routing processes.
Page 385 Condition, Index 4 and 5 use the condition configured for Index 3. A configuration example is shown in the beginning of this section. The option allows you to use the same condition for multiple manipulation rules. Version 7.2 Mediant 500 MSBR...
Page 386 Mediant 500 MSBR Parameter Description Note:  When configured to Use Previous Condition, the 'Message Type' and 'Condition' parameters are not applicable and if configured are ignored.  When multiple manipulation rules apply to the same header, the next rule applies to the resultant string of the previous rule.
Page 387: Configuring Message Condition Rules
Web interface. You can also configure it through ini file (ConditionTable) or CLI (configure voip > sbc routing condition-table).  To configure a Message Condition rule: Open the Message Conditions table (Setup menu > Signaling & Media tab > Version 7.2 Mediant 500 MSBR...
Page 388: Configuring Sip Message Policy Rules
Mediant 500 MSBR Message Manipulation folder > Message Conditions). Click New; the following dialog box appears: Figure 22-5: Message Conditions Table - Add Dialog Box Configure a Message Condition rule according to the parameters described in the table below. Click Apply.
Page 389 You can also configure it through ini file (MessagePolicy) or CLI (configure voip > message message-policy).  To configure SIP Message Policy rules: Open the Message Policies table (Setup menu > Signaling & Media tab > Message Manipulation folder > Message Policies). Version 7.2 Mediant 500 MSBR...
Page 390 Mediant 500 MSBR Click New; the following dialog box appears: Figure 22-7: Message Policies Table - Add Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Apply. Table 22-3: Message Policies Table Parameter Descriptions...
Page 391 [0] Policy Blacklist =The specified SIP body is rejected. [MessagePolicy_BodyLis  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; tType] the others are rejected. Malicious Signature Malicious Signature Enables the use of the Malicious Signature database (signature-based Database detection). Version 7.2 Mediant 500 MSBR...
Page 392: Configuring Pre-Parsing Manipulation Rules
Mediant 500 MSBR Parameter Description  signature-db-enable [0] Disable (default)  [1] Enable [MessagePolicy_UseMali ciousSignatureDB] To configure Malicious Signatures, see Configuring Malicious Signatures on page 727. Note: The parameter is applicable only to the SBC application. 22.4 Configuring Pre-Parsing Manipulation Rules The Pre-Parsing Manipulation Set table lets you configure up to 10 Pre-Parsing Manipulation Sets.
Page 393 Click New; the following dialog box appears: Figure 22-9: Pre-Parsing Manipulation Rules Table - Add Dialog Box Configure a rule according to the parameters described in the table below. Click New, and then save your settings to flash memory. Version 7.2 Mediant 500 MSBR...
Page 394 Mediant 500 MSBR Table 22-5: Pre-Parsing Manipulation Rules Table Parameter Descriptions Parameter Description Match Index Defines an index number for the new table row. [PreParsingManipulationRules_R Note: Each row must be configured with a unique index. uleIndex] Message Type Defines the SIP message type to which you want to apply the rule.
Page 395: Coders And Profiles
For supported audio coders, see Supported Audio Coders on page 397. • Some coders are license-based and are available only if purchased from AudioCodes and included in the License Key installed on your device. For more information, contact your AudioCodes sales representative. •...
Page 396 Mediant 500 MSBR  To configure a Coder Group: Open the Coder Groups table (Setup menu > Signaling & Media tab > Coders & Profiles folder > Coder Groups). Figure 23-1: Coder Group Table From the 'Coder Group Name' drop-down list, select the desired Coder Group index number and name.
Page 397: Supported Audio Coders
10, 20 (default), 30, 40, 50, [90] 64 (default) 60, 80, 100, 120 g711-ulaw  [1] Enable G.711A-law_VBD 10, 20 (default), 30, 40, 50, [90] 64 8 or 60, 80, 100, 120 Dynamic g711a-law-vbd (default 118) Version 7.2 Mediant 500 MSBR...
Page 398 Mediant 500 MSBR Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression [1] 10, [2] 20, [3] 30, [4] 40, [5] 50, [6] 60, [8] 80, [9] 90, [10] 100, [12] 120 [23] G.711U-law_VBD 10, 20 (default), 30, 40, 50,...
Page 399: Configuring Various Codec Attributes
• AMR coder: ♦ 'AMR Payload Format' (AmrOctetAlignedEnable): Defines the AMR payload format type: • SILK coder (Skype's default audio codec): ♦ 'Silk Tx Inband FEC': Enables forward error correction (FEC) for the SILK coder. Version 7.2 Mediant 500 MSBR...
Page 400: Configuring Allowed Audio Coder Groups
Mediant 500 MSBR ♦ 'Silk Max Average Bit Rate': Defines the maximum average bit rate for the SILK coder. Figure 23-2: Configuring SILK Coder Attributes Click Apply. 23.2 Configuring Allowed Audio Coder Groups The Allowed Audio Coders Groups table lets you configure up to 10 Allowed Audio Coders Groups for SBC calls.
Page 401 Allowed Audio Coders table opens. Click New; the following dialog box appears: Figure 23-4: Allowed Audio Coders Table - Add Dialog Box Configure coders for the Allowed Audio Coders Group according to the parameters described in the table below. Version 7.2 Mediant 500 MSBR...
Page 402: Configuring Allowed Video Coder Groups
Mediant 500 MSBR Click Apply. Table 23-3: Allowed Audio Coders Groups and Allowed Audio Coders Tables Parameter Descriptions Parameter Description Allowed Audio Coders Groups Table Index Defines an index number for the new table row. allowed-audio-coders-groups Note: Each row must be configured with a unique index.
Page 403 Allowed Video Coders table opens. Click New; the following dialog box appears: Figure 23-6: Allowed Video Coders Table - Add Dialog Box Configure coders for the Allowed Video Coders Group according to the parameters described in the table below. Version 7.2 Mediant 500 MSBR...
Page 404: Configuring Ip Profiles
Mediant 500 MSBR Click Apply. Table 23-4: Allowed Video Coders Groups and Allowed Video Coders Tables Parameter Descriptions Parameter Description Allowed Video Coders Groups Table Index Defines an index number for the new table row. allowed-video-coders-groups Note: Each row must be configured with a unique index.
Page 405 Parameter Description General Index Defines an index number for the new table row. [IpProfile_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the Version 7.2 Mediant 500 MSBR...
Page 406 Mediant 500 MSBR Parameter Description profile-name row in other tables. [IpProfile_ProfileName] The valid value is a string of up to 40 characters. Media Security SBC Media Security Mode Defines the handling of RTP and SRTP for the SIP entity associated with the IP Profile.
Page 407 Gateway application: The device only initiates the MKI size.  SBC application: The device can forward MKI size as is for SRTP-to-SRTP flows or override the MKI size during negotiation. This can be done on the inbound or outbound leg. Version 7.2 Mediant 500 MSBR...
Page 408 Mediant 500 MSBR Parameter Description  The corresponding global parameter is SRTPTxPacketMKISize. SBC Enforce MKI Size Enables negotiation of the Master Key Identifier (MKI) length for SRTP-to-SRTP flows between SIP networks (i.e., IP Groups). sbc-enforce-mki-size This includes the capability of modifying the MKI length on the...
Page 409  [0] Transparent = (Default) All early media response types are [IpProfile_SBCRemoteEarlyMedi supported; the device forwards all responses as is aResponseType] (unchanged).  [1] 180 = Early media is sent as 180 response only. Version 7.2 Mediant 500 MSBR...
Page 410 Mediant 500 MSBR Parameter Description  [2] 183 = Early media is sent as 183 response only. Remote Multiple Early Dialogs Defines the device's handling of To-header tags in call forking responses (i.e., multiple SDP answers) sent to the SIP entity sbc-multi-early-diag associated with the IP Profile.
Page 411 RTP packets from the peer side (which it then forwards to the SIP entity). Note: To generate silence packets, DSP resources are required (except for calls using the G.711 coder). Version 7.2 Mediant 500 MSBR...
Page 412 Mediant 500 MSBR Parameter Description SBC Media Allowed Audio Coders Assigns an Allowed Audio Coders Group, which defines audio (voice) coders that can be used for the SIP entity associated with allowed-audio-coders-group- the IP Profile. name To configure Allowed Audio Coders Groups, see Configuring [IpProfile_SBCAllowedAudioCod Allowed Audio Coder Groups on page 400.
Page 413 SIP entity to where the SIP INFO is being sent (and keep sending the DTMF digits using the RFC 2833 method). This is done using AudioCodes proprietary SIP header X-AC- Action and a Message Manipulation rule (inbound) to instruct the <device>...
Page 414 Mediant 500 MSBR Parameter Description Manipulation rule to re-start the sending of the SIP INFO. For example, you can configure two Message Manipulation rules where the sending of both SIP INFO and RFC 2833 depends on the negotiated media port -- the device stops sending SIP INFO if the SDP of the re-INVITE or UPDATE message contains port 7550 and re-starts sending if the port is 8660.
Page 415 Select the option if the SIP entity requires RTP redundancy.  [2] Disable = The device removes the RTP redundancy payload (if present) from the SDP offer/answer for calls received from or sent to the SIP entity. Select the option if the Version 7.2 Mediant 500 MSBR...
Page 416 Mediant 500 MSBR Parameter Description SIP entity does not support RTP redundancy. Note:  To enable the device to generate RFC 2198 redundant packets, use the IPProfile_RTPRedundancyDepth parameter.  To configure the payload type in the SDP offer for RTP redundancy, use the RFC2198PayloadType.
Page 417 RTP and RTCP multiplexing.  [0] Not Supported = (Default) RTP and RTCP packets use different ports.  [1] Supported = Device multiplexes RTP and RTCP packets onto a single port. Version 7.2 Mediant 500 MSBR...
Page 418 Mediant 500 MSBR Parameter Description Note: As RTP multiplexing has been defined by the WebRTC standard as mandatory, the support is important for deployments implementing WebRTC. For more information on WebRTC, see WebRTC. RTCP Feedback Enables RTCP-based feedback indication in outgoing SDPs sent to the SIP entity associated with the IP Profile.
Page 419 PRACK process on behalf of the SIP entity.  [2] Mandatory = PRACK is required for this SIP entity. Calls from endpoints that do not support PRACK are rejected. Calls destined to these endpoints are also required to support Version 7.2 Mediant 500 MSBR...
Page 420 Mediant 500 MSBR Parameter Description PRACK.  [3] Transparent (default) = The device does not intervene with the PRACK process and forwards the request as is. P-Asserted-Identity Header Mode Defines the device's handling of the SIP P-Asserted-Identity header for the SIP entity associated with the IP Profile. This sbc-assert-identity header indicates how the outgoing SIP message asserts identity.
Page 421 Add Routing Headers [1].  [0] Replace Contact = Device replaces the address in the Contact header, received in incoming messages from the other side, with its own address in the outgoing message sent Version 7.2 Mediant 500 MSBR...
Page 422 Mediant 500 MSBR Parameter Description to the SIP entity.  [1] Add Routing Headers = Device adds a Record-Route header for itself to outgoing messages (requests\responses) sent to the SIP entity in dialog-setup transactions. The Contact header remains unchanged. ...
Page 423 Defines the registration time (in seconds) that the device responds to SIP REGISTER requests from users belonging to sbc-usr-reg-time the SIP entity associated with the IP Profile. The registration time [IpProfile_SBCUserRegistrationTi is inserted in the Expires header in the outgoing response sent Version 7.2 Mediant 500 MSBR...
Page 424 Mediant 500 MSBR Parameter Description to the user. The Expires header determines the lifespan of the registration. For example, a value of 3600 means that the registration will timeout in one hour and at that point, the user will not be able to make or receive calls.
Page 425 SIP dialog with a new dialog such as Behavior] in call transfer or call pickup.  [0] Standard = (Default) The SIP entity supports INVITE messages containing Replaces headers. The device forwards the INVITE message containing the Replaces header to the Version 7.2 Mediant 500 MSBR...
Page 426 Mediant 500 MSBR Parameter Description SIP entity. The device may change the value of the Replaces header to reflect the call identifiers of the leg.  [1] Handle Locally = The SIP entity does not support INVITE messages containing Replaces headers. The device...
Page 427  Only one database entry is supported for the same host, port, and transport combination. For example, the following URLs cannot be distinguished by the device:  sip:10.10.10.10:5060;transport=tcp;param=a  sip:10.10.10.10:5060;transport=tcp;param=b Version 7.2 Mediant 500 MSBR...
Page 428 Mediant 500 MSBR Parameter Description  The database entry expires two hours after the last use.  The maximum number of destinations (i.e., database entries) is 50.  The corresponding global parameter is SBC3xxBehavior. SBC Hold Remote Hold Format Defines the format of the SDP in the SIP re-INVITE (or UPDATE) for call hold that the device sends to the held party.
Page 429 The IP address is indicated in the "c=" field (Connection) of the SDP.  [0] Only IPv4 = (Default) SDP offer includes only IPv4 media IP addresses.  [1] Only IPv6 = SDP offer includes only IPv6 media IP Version 7.2 Mediant 500 MSBR...
Page 430 Mediant 500 MSBR Parameter Description addresses.  [2] Prefer IPv4 = SDP offer includes IPv4 and IPv6 media IP addresses, but the first (preferred) media is IPv4.  [3] Prefer IPv6 = SDP offer includes IPv4 and IPv6 media IP addresses, but the first (preferred) media is IPv6.
Page 431 Ringing response is sent.  The corresponding global parameter is EnableEarlyMedia. Early 183 Enables the device to send SIP 183 responses with SDP to the IP upon receipt of INVITE messages. enable-early-183  [0] Disable (default) [IpProfile_EnableEarly183] Version 7.2 Mediant 500 MSBR...
Page 432 Mediant 500 MSBR Parameter Description  [1] Enable = By sending the 183 response, the device opens an RTP channel before receiving the "progress" tone from the ISDN side. The device sends RTP packets immediately upon receipt of an ISDN Progress, Alerting with Progress indicator,...
Page 433 EnableEarlyMedia is set to 1, the device sends 180 Ringing with SDP in response to an ISDN Alerting or it sends a 183 Session Progress message with SDP in response to only the first received ISDN Proceeding or Version 7.2 Mediant 500 MSBR...
Page 434 Mediant 500 MSBR Parameter Description Progress message after a call is placed to PBX/PSTN over the trunk.  [8] PI = 8: same as PI = 1. Note: The corresponding global parameter is ProgressIndicator2IP. Hold Enables the Call Hold feature (analog interfaces) and...
Page 435 [1] INFO (Nortel) = Sends DTMF digits according to IETF Internet-Draft draft-choudhuri-sip-info-digit-00.  [2] NOTIFY = Sends DTMF digits according to IETF Internet- Draft draft-mahy-sipping-signaled-digits-01.  [3] INFO (Cisco) = Sends DTMF digits according to the Cisco Version 7.2 Mediant 500 MSBR...
Page 436 Mediant 500 MSBR Parameter Description format.  [4] RFC 2833 = (Default) The device:  negotiates RFC 2833 payload type using local and remote SDPs.  sends DTMF packets using RFC 2833 payload type according to the payload type in the received SDP.
Page 437 CNG tone is detected by the originating fax. However, this mode is not recommended. Note: The corresponding global parameter is CNGDetectorMode. Vxx Modem Transport Type Defines the modem transport type.  vxx-transport-type [-1] = (Not Configured) The settings of the global parameters Version 7.2 Mediant 500 MSBR...
Page 438 Mediant 500 MSBR Parameter Description [IpProfile_VxxTransportType] are used:  V21ModemTransportType  V22ModemTransportType  V23ModemTransportType  V32ModemTransportType  V34ModemTransportType  [0] Disable = Transparent.  [2] Enable Bypass (Default)  [3] Events Only = Transparent with Events. For a detailed description of the parameter per modem type, see the relevant global parameter (listed above).
Page 439 (value of -1), the device plays a default held tone. To play user-defined tones, you need to record your tones and then install them on the device using a loadable Prerecorded Tones (PRT) file. For more information, see Prerecorded Tones File on page 778. Version 7.2 Mediant 500 MSBR...
Page 440: Configuring Tel Profile
Mediant 500 MSBR 23.5 Configuring Tel Profile The Tel Profiles table lets you configure up to nine Tel Profiles. A Tel Profile is a set of parameters with specific settings which can be assigned to specific calls. The Tel Profiles table includes a wide range of parameters for configuring the Tel Profile.
Page 441 When the parameter is set to 1, 2, or 3, the parameter FaxTransportMode is ignored.  When the parameter is set to 0, T.38 might still be used without the control protocol's involvement. To completely disable T.38, set FaxTransportMode to a value other than Version 7.2 Mediant 500 MSBR...
Page 442 Mediant 500 MSBR Tel Profile Parameter Global Parameter  For more information on fax transport methods, see Fax/Modem Transport Modes on page 166.  The corresponding global parameter is IsFaxUsed. Enable Digit Delivery Enables the Digit Delivery feature, which sends DTMF digits...
Page 443 The device identifies emergency calls by one of the following:  The destination number of the IP call matches one of the numbers configured by the EmergencyNumbers parameter. (For E911, you must configure the Version 7.2 Mediant 500 MSBR...
Page 444 Mediant 500 MSBR Tel Profile Parameter Global Parameter parameter to "911".)  The incoming SIP INVITE message contains the “emergency” value in the Priority header. Note:  The parameter is applicable to FXS/FXO, ISDN and CAS.  For FXO interfaces, the preemption is done only on existing IP-to-Tel calls.
Page 445 Note: The corresponding global parameter is VoiceVolume Enable AGC Enables the Automatic Gain Control (AGC) feature. The AGC feature automatically adjusts the level of the received enable-agc signal to maintain a steady (configurable) volume level. [TelProfile_EnableAGC]  [0] Disable (default) Version 7.2 Mediant 500 MSBR...
Page 446 Mediant 500 MSBR Tel Profile Parameter Global Parameter  [1] Enable Note:  For a description of AGC, see Automatic Gain Control (AGC) on page 194.  The corresponding global parameter is EnableAGC. Analog Enable Polarity Reversal Enables the Polarity Reversal feature for call release.
Page 447 (number that dialed 911) in the format "KP<ANI>ST" (*ANI#), where ANI is the calling number from the INVITE. If no polarity reversal, the FXO goes idle. For example: (Wink) KP911ST (Polarity Change) KP02963700ST Note: The Enable911PSAP parameter must be set to Version 7.2 Mediant 500 MSBR...
Page 448 Mediant 500 MSBR Tel Profile Parameter Global Parameter Note:  For FXS interfaces, the EnableReversalPolarity and PolarityReversalType parameters must be configured to  The parameter is applicable to FXS and FXO interfaces.  The corresponding global parameter is EnableDIDWink. Enable 911 PSAP Enables the support for the E911 DID protocol, according to the Bellcore GR-350-CORE standard.
Page 449 Session Progress message with SDP immediately after a call is placed to a phone/PBX. This is used to cut-through the voice path before the remote party answers the call. This allows the originating party to Version 7.2 Mediant 500 MSBR...
Page 450 Mediant 500 MSBR Tel Profile Parameter Global Parameter listen to network call progress tones such as ringback tone or other network announcements.  Digital: For IP-to-Tel calls, if the parameter EnableEarlyMedia is set to 1, the device sends 180 Ringing with SDP in response to an ISDN Alerting or...
Page 451 To specify whether the dialing must start after detection of the dial tone or immediately after seizing the line, use the IsWaitForDialTone parameter.  [1] Yes = (Default) Two-stage dialing. In this mode, the device seizes one of the PSTN/PBX lines without Version 7.2 Mediant 500 MSBR...
Page 452 Mediant 500 MSBR Tel Profile Parameter Global Parameter performing any dialing, connects the remote IP user to the PSTN/PBX and all further signaling (dialing and Call Progress Tones) is performed directly with the PBX without the device's intervention. Note: ...
Page 453 For FXO interfaces, a constant of 100 msec must be added to the required hook-flash period. For example, to generate a 450 msec hook-flash, configure the parameter to 550.  The corresponding global parameter is FlashHookPeriod. Version 7.2 Mediant 500 MSBR...
Page 454 Mediant 500 MSBR This page is intentionallty left blank. User's Manual Document #: LTRT-10375...
Page 455: Gateway Application
Part V Gateway Application...
Page 457: Introduction
The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. 24.1 Call Processing Summary The device's call processing for Gateway calls is shown in the following flowcharts. Version 7.2 Mediant 500 MSBR...
Page 458 Mediant 500 MSBR  IP-to-Tel Call: Figure 24-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-10375...
Page 459 User's Manual 24. Introduction  Tel-to-IP Call: Figure 24-2: Tel-to-IP Call Processing Flowchart Version 7.2 Mediant 500 MSBR...
Page 460 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 461: Digital Pstn
Release Note). • The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact your AudioCodes sales representative before implementing this protocol. • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk.
Page 462 Mediant 500 MSBR  To configure trunks: Open the Trunk Settings page (Setup menu > Signaling & Media tab > Gateway folder > Trunks & Groups > Trunks). On the top of the page, a bar with Trunk number icons displays the status of each trunk according to the following color codes: •...
Page 463: Tdm And Timing
PSTN line clock (see Recovering Clock from PSTN Line on page 464)  Internal clock (see Configuring Internal Clock as Clock Source on page 465) Note: When the device is used in a ‘non-span’ configuration, the internal device clock must be used (as explained above). Version 7.2 Mediant 500 MSBR...
Page 464: Recovering Clock From Pstn Line Interface
Mediant 500 MSBR 25.2.1.1 Recovering Clock from PSTN Line Interface This section provides a brief description for configuring synchronization based on recovering clock from the PSTN line interface. For a full description of the clock parameters, see PSTN Parameters on page 1134.
Page 465: 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 Apply, and then reset the device. Version 7.2 Mediant 500 MSBR...
Page 466 Mediant 500 MSBR Note: • The CAS state machine can only be configured using the Web-based management tool. • Don't modify the default values unless you fully understand the implications of the changes and know the default values. Every change affects the configuration of the state machine parameters and the call process related to the trunk you are using with this state machine.
Page 467: Configuring Digital Gateway Parameters
Open the Digital Gateway Settings page (Setup menu > Signaling & Media tab > Gateway folder > Digital Gateway > Digital Gateway Settings). Figure 25-4: Digital Gateway Parameters Page Configure the parameters as required. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 468: Tunneling Applications
Mediant 500 MSBR 25.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 25.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal...
Page 469 TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileName, TrunkGroup_Module; TrunkGroup 1 = 0,0,0,1,31,1000,1; TrunkGroup 1 = 0,1,1,1,31,2000,1; TrunkGroup 1 = 0,2,2,1,31,3000,1; TrunkGroup 1 = 0,3,3,1,31,4000,1; TrunkGroup 1 = 0,0,0,16,16,7000,2; TrunkGroup 1 = 0,1,1,16,16,7001,2; TrunkGroup 1 = 0,2,2,16,16,7002,2; TrunkGroup 1 = 0,3,3,16,16,7003,2; [/TrunkGroup] Version 7.2 Mediant 500 MSBR...
Page 470 Mediant 500 MSBR [ AudioCodersGroups ] FORMAT AudioCodersGroups_Index = AudioCodersGroups_Name; AudioCodersGroups 0 = "AudioCodersGroups_0"; AudioCodersGroups 1 = "AudioCodersGroups_1"; [ \AudioCodersGroups ] [ AudioCoders ] AudioCoders 0 = "AudioCodersGroups_0", 0, 0, 3, 7, -1, 0, ""; AudioCoders 1 = "AudioCodersGroups_1", 0, 7, 2, 90, 56, 0, "";...
Page 471: Dsp Pattern Detector
(commonly called Ringdown circuits). No dialing is necessary; the user simply picks up the handset or pushes a button and a dedicated line is seized. Thus, many turrets have multiple handsets Version 7.2 Mediant 500 MSBR...
Page 472 Mediant 500 MSBR and multi-channel speaker units, allowing immediate connection with multiple parties (e.g., 30 channels). These channels remain constantly open throughout the trading day. Today, private wire services are evolving from digital TDM architectures to IP-based architectures. The device can be used for interworking between these two architectures, where you have the PSTN switch (PBX) using the E1/T1 CAS protocol on one side, and a SIP-based private wire (turret system) trunk on the other side.
Page 473 <xsd:complexType name="pwSignallingType"> <xsd:sequence> <xsd:choice> <xsd:element ref="ringDown" /> <xsd:element ref="hookSwitch" /> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xsd:choice> </xsd:sequence> <xsd:anyAttribute namespace="##other" processContents="lax" /> </xsd:complexType> <xsd:element name="pwSignal" type="pwSignallingType"/>  <xsd:complexType name="ringDownType"> <xsd:sequence> <xsd:any namespace="##other" minOccurs="0" Version 7.2 Mediant 500 MSBR...
Page 474 Mediant 500 MSBR maxOccurs="unbounded" processContents="lax" /> </xsd:sequence> <xsd:attribute name="signal" type="ringDownSignalType" use="required"/> <xsd:anyAttribute namespace="##other" processContents="lax" /> </xsd:complexType> <xsd:element name="ringDown" type="ringDownType"/>  <xsd:complexType name="hookSwitchType"> <xsd:sequence> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xsd:sequence> <xsd:attribute name="signal" type="hookSwitchSignalType" use="required"/> <xsd:anyAttribute namespace="##other" processContents="lax" />...
Page 475 E1 or T1 CAS Trunk. Make sure that you select the CAS table file that you loaded in the previous step, in the 'CAS Table per Trunk' field: Figure 25-9: Selecting CAS File for Trunk - Private Wire Version 7.2 Mediant 500 MSBR...
Page 476: Qsig Tunneling
Mediant 500 MSBR In the Trunk Group table (see Configuring Trunk Groups on page 485), configure the Trunk Group ID for the E1/T1 CAS Trunk, as shown in the following example: Figure 25-10: Configuring Trunk Group for Private Wire In the Trunk Group Settings table (see Configuring <trnkgrpsettableM5MSBR> on...
Page 477: Isdn Non-Facility Associated Signaling (Nfas)
The device supports up to 12 NFAS groups. Each group can comprise up to 10 T1 trunks and each group must contain different T1 trunks. Each T1 trunk is called an "NFAS member". The T1 trunk whose D-channel is used for signaling is called the "Primary NFAS Version 7.2 Mediant 500 MSBR...
Page 478: Nfas Interface Id
Mediant 500 MSBR 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. The NFAS group is identified by an NFAS GroupID number (possible values are 1 to 12).
Page 479: Working With Dms-100 Switches
Stop or delete (by setting ProtocolType to 0, i.e., 'None') all NFAS (‘slave’) trunks. Stop or delete (by setting ProtocolType to 0, i.e., 'None') the backup trunk if a backup trunk exists. Stop or delete (by setting ProtocolType to 0, i.e., 'None') the primary trunk. Version 7.2 Mediant 500 MSBR...
Page 480: Performing Manual D-Channel Switchover In Nfas Group
Mediant 500 MSBR Note: • All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure 25.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.
Page 481: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578
SIP re-INVITE or SIP INFO messages. You can use the following parameters to configure overlap dialing for Tel-to-IP calls: • ISDNRxOverlap: Enables Tel-to-IP overlap dialing and defines how the device sends the collected digits to the IP side - in SIP re-INVITE [2] or INFO messages [3]. Version 7.2 Mediant 500 MSBR...
Page 482: Redirect Number And Calling Name (Display)
Mediant 500 MSBR • MinOverlapDigitsForRouting: Defines the minimum number of overlap digits to collect from the Tel side before the device can send the first SIP message (INVITE) for routing the call to the IP side. • MaxDigits: Defines the maximum number of collected digits that can be received from the Tel side (if ISDN Sending Complete IE is not received).
Page 483 User's Manual 25. Digital PSTN TE-to-NT Table 25-3: Redirect Number NT/TE Interface DMS-100 NI-2 4/5ESS Euro ISDN QSIG NT-to-TE TE-to-NT Yes* * When using ETSI DivertingLegInformation2 in a Facility IE (not Redirecting Number IE). Version 7.2 Mediant 500 MSBR...
Page 484 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 485: Trunk Groups
'Registration Mode' parameter in the Trunk Group Settings page (see Configuring Trunk Group Settings on page 487).  To register Trunk Groups, click the Register button.  To unregister Trunk Groups, click the Unregister button. Table 26-1: Trunk Group Table Parameter Descriptions Parameter Description Version 7.2 Mediant 500 MSBR...
Page 486 Mediant 500 MSBR Parameter Description Module Defines the telephony interface module for which you want to define the Trunk Group. module [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group. The number of listed Trunks depends on the device's hardware first-trunk-id configuration.
Page 487: Configuring Trunk Group Settings Table
To configure Trunk Group settings: Open the Trunk Group Settings table (Setup menu > Signaling & Media tab > Gateway folder > Trunks & Groups > Trunk Group Settings). Click New; the following dialog box appears: Version 7.2 Mediant 500 MSBR...
Page 488 Mediant 500 MSBR Configure a Trunk Group according to the parameters described in the table below. Click Apply. Table 26-2: Trunk Group Settings Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [TrunkGroupSettings_Inde Note: Each row must be configured with a unique index.
Page 489 For the third incoming call, the second channel of Trunk 0 is selected.  [9] Ring to Hunt Group = The device allocates IP-to-Tel calls to all the FXS ports (channels) in the Trunk Group (i.e., a ringing Version 7.2 Mediant 500 MSBR...
Page 490 Mediant 500 MSBR Parameter Description group). When a call is received for the Trunk Group, all telephones connected to the FXS ports belonging to the Trunk Group start ringing. The call is eventually received by whichever telephone first answers the call (after which the other phones stop ringing).
Page 491 If registration fails, the user part in the INVITE Contact header is set to the source party number.  The 'Contact User' parameter in the Accounts table overrides this parameter (see Configuring Registration Accounts on page 363). Version 7.2 Mediant 500 MSBR...
Page 492 Mediant 500 MSBR Parameter Description Serving IP Group Assigns an IP Group to where the device sends INVITE messages for calls received from the Trunk Group. The actual destination to serving-ip-group where the INVITE messages are sent is according to the Proxy Set [TrunkGroupSettings_Serv associated with the IP Group.
Page 493  "Out Of Service": All fully configured trunks in the Trunk Group are out of service, for example, when the Trunk Group is locked or in Busy Out state (see the EnableBusyOut parameter). Version 7.2 Mediant 500 MSBR...
Page 494 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 495: Routing
SRD. As one of the attributes of a SIP Interface is an SRD and as you can configure multiple SIP Interfaces per SRD, the specific SIP Interface not only determines the above-mentioned attributes, but also the SRD for routing the call. Version 7.2 Mediant 500 MSBR...
Page 496 Mediant 500 MSBR The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call.
Page 497 The following procedure describes how to configure Tel-to-IP routing rules through the Web interface. You can also configure it through ini file (Prefix) or CLI (configure voip > gateway routing tel2ip-routing). Version 7.2 Mediant 500 MSBR...
Page 498 Mediant 500 MSBR  To configure Tel-to-IP routing rules: Open the Tel-to-IP Routing table (Setup menu > Signaling & Media tab > Gateway folder > Routing > Tel > IP Routing). Click New; the following dialog box appears: Figure 27-2: Tel-to-IP Routing Table - Add Dialog Box Configure a routing rule according to the parameters described in the table below.
Page 499 Match Source Trunk Group Defines the Trunk Group from where the call is received. To denote any Trunk Group, use the asterisk (*) symbol. By default, no Trunk src-trunk-group-id Group is defined (-1). [PREFIX_SrcTrunkG roupID] Version 7.2 Mediant 500 MSBR...
Page 500 Mediant 500 MSBR Parameter Description Source Phone Prefix Defines the prefix and/or suffix of the calling (source) telephone number. You can use special notations for denoting the prefix. For example, [100- src-phone-prefix 199](100,101,105) denotes a number that starts with 100 to 199 and ends [PREFIX_SourcePre with 100, 101 or 105.
Page 501 IP Profile associated with the IP Group.  If no IP Group is configured, the device uses IP Profile 0 Destination Port Defines the destination port to where you want to route the call. dst-port [PREFIX_DestPort] Version 7.2 Mediant 500 MSBR...
Page 502 Mediant 500 MSBR Parameter Description Transport Type Defines the transport layer type used for routing the call.  transport-type [-1] = (Default) Not configured and the transport type is according to the settings of the global parameter, SIPTransportType. [PREFIX_TransportT ...
Page 503 (Read-only field) Displays the connectivity status of the routing rule's destination. The destination can be an IP address or an IP Group, as configured in the 'Destination IP Address' and 'Destination IP Group' fields respectively. Version 7.2 Mediant 500 MSBR...
Page 504: Configuring Ip-To-Tel Routing Rules
Mediant 500 MSBR Parameter Description For IP Groups, the status indicates the connectivity with the SIP proxy server's address configured for the Proxy Set that is associated with the IP Group. For the status to be displayed, the Proxy Keep-Alive feature, which monitors the connectivity with proxy servers per Proxy Set, must be enabled for the Proxy Set (see Configuring Proxy Sets on page 348).
Page 505 Web interface. You can also configure it through ini file (PSTNPrefix) or CLI (configure voip > gateway routing ip2tel-routing).  To configure IP-to-Tel routing rules: Open the IP-to-Tel Routing table (Setup menu > Signaling & Media tab > Gateway folder > Routing > IP > Tel Routing). Version 7.2 Mediant 500 MSBR...
Page 506 Mediant 500 MSBR Click New; the following dialog box appears: Figure 27-3: IP-to-Tel Routng Table - Add Dialog Box Configure a routing rule according to the parameters described in the table below. Click Apply. The following table shows configuration examples of Tel-to-IP routing rules:...
Page 507 (*) symbol. To denote calls without a calling number, use the $ sign. For a description of available notations, see Dialing Plan Notation for Routing and Manipulation Tables on page 979. By default, no value is defined. Version 7.2 Mediant 500 MSBR...
Page 508 Mediant 500 MSBR Parameter Description Note: If the P-Asserted-Identity header is present in the incoming INVITE message, the value of the parameter is compared to the P- Asserted-Identity URI host name (and not the From header). Source Host Prefix Defines the prefix of the URI host name in the From header of the incoming INVITE message.
Page 509: Configuring A Gateway Routing Policy Rule
> Routing > Routing Policies). Click New; the following dialog box appears: Figure 27-4: Routing Policies Table - Edit Dialog Box Configure the Routing Policy rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 510 Mediant 500 MSBR Table 27-5: Routing Policies Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table row. [GwRoutingPolicy_Index] Name Defines a descriptive name, which is used when associating the row in other tables. name The valid value is a string of up to 40 characters.
Page 511: Alternative Routing For Tel-To-Ip Calls
Signaling & Media tab > Gateway folder > Routing > Routing Settings), as shown below: Figure 27-6: Configuring IP QoS Thresholds for Alternative Tel-to-IP Routing  DNS Resolution: When a host name (FQDN) is used (instead of an IP address) for Version 7.2 Mediant 500 MSBR...
Page 512: Alternative Routing Based On Ip Connectivity
Mediant 500 MSBR the IP destination, it is resolved into an IP address by a DNS server. The device checks network connectivity and QoS of the resolved IP address. If the DNS host name is unresolved, the device considers the connectivity of the IP destination as unavailable.
Page 513 Connectivity: Alternative routing is performed if a or SIP OPTIONS message to the initial destination fails ♦ QoS: Alternative routing is performed if poor QoS is detected. QoS is quantified according to delay and packet loss calculated according to previous calls. ♦ Both (above) Version 7.2 Mediant 500 MSBR...
Page 514: Alternative Routing Based On Sip Responses
Mediant 500 MSBR (For Analog Interfaces Only) In the 'Alternative Routing Tone Duration' field, configure the duration for which the device plays a tone to the Tel endpoint (for analog interfaces) whenever an alternative route is used. Enable the connectivity feature (see IP Destinations Connectivity Feature on page 511).
Page 515 The device assumes that all the proxy servers belonging to the Proxy Set are synchronized with regards to registered users. Thus, when the device locates an available proxy using the Hot Swap feature, it does not re-register the users; new registration (refresh) is done as normal. Version 7.2 Mediant 500 MSBR...
Page 516 Mediant 500 MSBR The following procedure describes how to configure alternative Tel-to-IP routing based on SIP response codes through the Web. You can also configure it through ini file (AltRouteCauseTel2Ip) or CLI (configure voip > gateway routing alt-route-cause-tel2ip).  To configure alternative Tel-to-IP routing based on SIP response codes:...
Page 517: Alternative Routing Upon Sip 3Xx With Multiple Contacts
In the Tel-to-IP Routing table (see Configuring Tel-to-IP Routing Rules on page 495), configure an alternative routing rule with the same call matching characteristics (e.g., phone number destination) as the "main" routing rule, but where the destination is the IP address of the device itself. Version 7.2 Mediant 500 MSBR...
Page 518: Alternative Routing For Ip-To-Tel Calls
Mediant 500 MSBR In the IP-to-Tel Routing table (see Configuring IP-to-Tel Routing Rules on page 504), configure an IP-to-Tel routing rule to route calls received from the device (i.e., its IP address) to a specific Trunk Group connected to the PSTN. This configuration is necessary as the re-routed call is now considered an IP-to-Tel call.
Page 519 Click New; the following dialog box appears: Figure 27-13: Reasons for IP-to-Tel Alternative Routing Table - Add Dialog Box Configure a Q.931 release cause code for alternative routing according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 520: Alternative Routing To An Ip Destination Upon A Busy Trunk
Mediant 500 MSBR Table 27-9: Reasons for IP-to-Tel Alternative Routing Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [AltRouteCauseIP2Tel_Ind Note: Each row must be configured with a unique index. Release Cause Defines a Q.931 release code that if received, the device attempts to route the call to an alternative destination (if configured).
Page 521: Alternative Routing Upon Isdn Disconnect
ISDN Q.931 Disconnect message with a Progress Indicator (PI) IE from the Tel side for IP- to-Tel calls. The Disconnect message indicates that the call cannot be established due to, for example, a busy state on the Tel side. Version 7.2 Mediant 500 MSBR...
Page 522: Alternative Routing From Fxo To Ip
SIP Trunk. This is configured using the ini file parameter, TR104FXOSwitchover. Note: For more information on this application, please contact your AudioCodes sales representative. User's Manual...
Page 523: Manipulation
Source Phone Number Manipulation for Tel-to-IP Calls (up to 120 entries) • Destination Phone Number Manipulation for Tel-to-IP Calls (up to 120 entries)  IP-to-Tel calls: • Source Phone Number Manipulation for IP-to-Tel Calls (up to 120 entries) Version 7.2 Mediant 500 MSBR...
Page 524 Mediant 500 MSBR • Destination Phone Number Manipulation for IP-to-Tel Calls (up to 120 entries) Configuration of number manipulation rules includes two areas:  Match: Defines the matching characteristics of the incoming call (e.g., prefix of destination number).  Action: Defines the action that is done if the incoming call matches the characteristics of the rule (e.g., removes a user-defined number of digits from the left of the number).
Page 525 Table 28-1: Configuration Examples of Source Phone Number Manipulation for Tel-to-IP Calls Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 [6,7,8] Destination Prefix Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits Version 7.2 Mediant 500 MSBR...
Page 526 Mediant 500 MSBR Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 From Left Stripped Digits From Right Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Below is a description of each rule: ...
Page 527 The default is Any (i.e., any IP Group). [_SrcIPGroupID] Note: The parameter is applicable only to the Destination Phone Number Manipulation for IP-to-Tel Calls table and Source Phone Number Manipulation for IP-to-Tel Calls table. Action Version 7.2 Mediant 500 MSBR...
Page 528 Mediant 500 MSBR Parameter Description Stripped Digits From Left Defines the number of digits to remove from the left of the telephone number prefix. For example, if you enter 3 and the phone number is remove-from-left 5551234, the new phone number is 1234.
Page 529: Manipulating Number Prefix
= location (number of digits counted from the left of the number) of a specific string in the original destination or source number. • l = number of digits that this string includes.  y = prefix to add at the specified location. Version 7.2 Mediant 500 MSBR...
Page 530: Sip Calling Name Manipulations
Mediant 500 MSBR For example, assume that you want to manipulate an incoming IP call with destination number "+5492028888888" (i.e., area code "202" and phone number "8888888") to the number "0202158888888". To perform such manipulation, the following configuration is required in the Number Manipulation table:...
Page 531 Figure 28-3: Calling Name Manipulation for IP-to-Tel Calls Table (Example) - Add Dialog Box Configure a manipulation rule according to the parameters described in the table below. Click Apply. Table 28-4: Calling Name Manipulation Tables Parameter Descriptions Parameter Description Version 7.2 Mediant 500 MSBR...
Page 532 Mediant 500 MSBR Parameter Description General Index Defines an index number for the new table row. [_Index] Note: Each row must be configured with a unique index. Name Defines a descriptive name, which is used when associating the row in other tables.
Page 533: Configuring Redirect Number Ip To Tel
The redirect number manipulation tables let you configure rules for manipulating the redirect number received in SIP messages. The redirect number manipulation tables include:  Redirect Number IP-to-Tel table: (Applicable only ISDN) Defines IP-to-Tel redirect Version 7.2 Mediant 500 MSBR...
Page 534 Mediant 500 MSBR number manipulation. You can manipulate the value of the received SIP Diversion, Resource-Priority, or History-Info headers, which is then added to the Redirecting Number Information Element (IE) in the ISDN Setup message sent to the Tel side.
Page 535 The default value is the asterisk (*) symbol (i.e., any number prefix). [_RedirectPrefix] Source Trunk Group ID Defines the Trunk Group from where the Tel call is received. src-trunk-group-id To denote any Trunk Group, leave this field empty. The value -1 Version 7.2 Mediant 500 MSBR...
Page 536 Mediant 500 MSBR Parameter Description [_SrcTrunkGroupID] indicates that this field is ignored in the rule. Note: The parameter is applicable only to the Redirect Number Tel- to-IP table. Source IP Address Defines the IP address of the caller. The IP address appears in the SIP Contact header of the incoming INVITE message.
Page 537 [1] Restricted = Restricts Caller ID information for these prefixes. Note: If you configure the parameter to Restricted and the 'AssertedIdMode' parameter to Add P-Asserted-Identity, the From header in the INVITE message includes the following: From: 'anonymous' <sip: anonymous@anonymous.invalid> and 'privacy: id' header. Version 7.2 Mediant 500 MSBR...
Page 538: Manipulating Redirected And Diverted Numbers For Call Diversion
Mediant 500 MSBR 28.6 Manipulating Redirected and Diverted Numbers for Call Diversion You can configure manipulation rules to manipulate the Diverted-to and Diverting numbers received in the incoming Call Redirection Facility message for call diversion, which is interworked to outgoing SIP 302 responses.
Page 539: Mapping Npi/Ton To Sip Phone-Context
> Manipulation > Phone Contexts). Click New; the following dialog box appears: Figure 28-5: Phone Contexts Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 540 Mediant 500 MSBR Note: • You can configure multiple rows with the same NPI/TON or same SIP 'phone- context'. In such a configuration, a Tel-to-IP call uses the first matching rule in the table. • To add the incoming SIP 'phone-context' parameter as a prefix to the outgoing...
Page 541: Configuring Release Cause Mapping
To configure a SIP-to-ISDN release cause mapping rule: Open the Release Cause Mapping from SIP to ISDN table (Setup menu > Signaling & Media tab > Gateway folder > Manipulation > Release Cause SIP > ISDN). Version 7.2 Mediant 500 MSBR...
Page 542: Fixed Mapping Of Sip Response To Isdn Release Reason
Mediant 500 MSBR Click New; the following dialog box appears: Figure 28-6: Release Cause Mapping from SIP to ISDN Table - Add Dialog Box Configure a mapping rule according to the parameters described in the table below. Click Apply. Table 28-8: Release Cause Mapping from SIP to ISDN Table Parameter Descriptions...
Page 543 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. Version 7.2 Mediant 500 MSBR...
Page 544: Isdn-To-Sip Release Cause Mapping
Mediant 500 MSBR 28.8.2 ISDN-to-SIP Release Cause Mapping 28.8.2.1 Configuring ISDN-to-SIP Release Cause Mapping The Release Cause Mapping from ISDN to SIP table lets you configure up to 12 ISDN ITU- T Q.850 release cause code (call failure) to SIP response code mapping rules. The table lets you override the default ISDN-to-SIP release cause mappings, listed in Fixed Mapping of ISDN Release Reason to SIP Response on page 545.
Page 545: Fixed Mapping Of Isdn Release Reason To Sip Response
Call rejected Forbidden Number changed w/o diagnostic Gone Redirection Bad Request Exchange Routing Error Bad Request Non-selected user clearing Not found Destination out of order Bad gateway Address incomplete Address incomplete Facility rejected Not implemented Version 7.2 Mediant 500 MSBR...
Page 546 Mediant 500 MSBR ISDN Release Description Description Reason Response Response to status enquiry 501* Not implemented Normal unspecified Temporarily unavailable Circuit Congestion Server internal error User Congestion Server internal error No circuit available Service unavailable Network out of order Service unavailable...
Page 547: Configuring Isdn-To-Isdn Release Cause Mapping
PSTN side, it searches the table for a matching ISDN cause code. If found, the device changes the cause code to the corresponding ISDN cause code. If the ISDN cause code is not configured in the table, the originally received ISDN cause code is used. If the Version 7.2 Mediant 500 MSBR...
Page 548 Mediant 500 MSBR new ISDN cause code also appears in the Release Cause Mapping ISDN to SIP table (see Configuring ISDN-to-SIP Release Cause Mapping on page 544), the device maps it to the corresponding SIP response code, which it sends to the IP side.
Page 549: Reason Header
The parameter defines Q.931 release causes. Its default value is 3, which is mapped to the SIP 404 response. By changing its value to 34, the SIP 503 response is sent. Other causes can be used as well. Version 7.2 Mediant 500 MSBR...
Page 550: Numbering Plans And Type Of Number
Mediant 500 MSBR 28.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 551: Configuring Dtmf And Dialing
998 can never be matched. But when the digit map is 99s|998, then after dialing the first two 9 digits, the device waits another two seconds within which the caller can enter the digit 8. Version 7.2 Mediant 500 MSBR...
Page 552: External Dial Plan File
Mediant 500 MSBR Below is an example of a digit map pattern containing eight rules: DigitMapping = 11xS|00[1- 7]xxx|8xxxxxxx|#xxxxxxx|*xx|91xxxxxxxxxx|9011x|xx.T In the example, the rule "00[1-7]xxx" denotes dialed numbers that begin with 00, and then any digit from 1 through 7, followed by three digits (of any number). Once the device receives these digits, it does not wait for additional digits, but starts sending the collected digits (dialed number) immediately.
Page 553: Configuring Hook Flash
(in msec) for detection of a hook-flash event from an FXS interface. Detection is guaranteed for hook-flash periods of at least 60 msec (when configuring the period to 25). The device ignores hook-flash signals lasting a shorter period of time. Version 7.2 Mediant 500 MSBR...
Page 554 Mediant 500 MSBR ♦ 'Max. Flash-Hook Detection Period' (FlashHookPeriod): Defines the maximum hook-flash period (in msec) for Tel and IP sides for FXS and FXO interfaces. For more information, see the Telprofile_FlashHookPeriod parameter in Configuring Tel Profiles on page 440.
Page 555: Configuring Supplementary Services
(or any other hold tone) is played (over IP) by the remote party. You can also configure the device to keep a call on-hold for a user-defined time after which the call is disconnected, using the HeldTimeout parameter. Version 7.2 Mediant 500 MSBR...
Page 556 Mediant 500 MSBR The device also supports "double call hold" for FXS interfaces where the called party, which has been placed on-hold by the calling party, can then place the calling party on hold as well and make a call to another destination. The flowchart below provides an example of...
Page 557: Call Pickup
To resume the call, the phone user typically presses the same keys or button and then off-hooks the phone. During the suspended state, the device plays a howler tone to the remote party. This service is also supported Version 7.2 Mediant 500 MSBR...
Page 558: Consultation Feature
Mediant 500 MSBR when instead of pressing the call park button(s), the phone cable is disconnected (suspending the call) and then reconnected again (resuming the call). If the phone user does not resume the call within a user-defined interval (configured by the HeldTimeout parameter), the device releases the call.
Page 559: Consultation Transfer For Qsig Path Replacement
Q.931 Disconnect messages to the PBX, notifying the PBX that it can disconnect the ISDN calls (of user "A"). This feature is enabled by the QSIGPathReplacementMode parameter. Note: The feature is applicable only to digital interfaces. Version 7.2 Mediant 500 MSBR...
Page 560: Blind Call Transfer
Mediant 500 MSBR 30.5.3 Blind Call Transfer Blind call transfer is done (using SIP REFER messages) after a call is established between call parties A and B, and party A decides to immediately transfer the call to C without first speaking to C.
Page 561: Enabling Call Forwarding
To configure call forwarding per FXS or FXO port, see Configuring Call Forward on page 606. 30.6.2 Call Forward Reminder Ring The device supports the Call Forward Reminder Ring feature for FXS interfaces whereby the device's FXS endpoint emits a short ring burst when a third-party Application server Version 7.2 Mediant 500 MSBR...
Page 562 Mediant 500 MSBR (e.g., softswitch) forwards an incoming call to another destination. The ring is emitted only when the endpoint is in on-hook state. The feature is useful in that it notifies the endpoint user that a call forwarding service is currently being performed.
Page 563: Call Forward Reminder (Off-Hook) Special Dial Tone
The special dial tone is used as a result of the device receiving a SIP NOTIFY message from a third-party softswitch providing the call forwarding service with the following SIP Alert-Info header: Version 7.2 Mediant 500 MSBR...
Page 564: Remote Handling Of Bri Call Forwarding
Mediant 500 MSBR Alert-Info: <http://127.0.0.1/Tono-Espec-Invitacion>;lpi- aviso=Desvio-Inmediato This special tone is a stutter dial tone (Tone Type = 15), as defined in the CPT file (see Call Progress Tones File on page 773). The FXS phone user, connected to the device, activates the call forwarding service by dialing a special number (e.g., *21*xxxxx) and as a result, the device sends a regular SIP...
Page 565 SuppServCodeCFU parameter. INVITE sip:*72100@10.33.8.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.5:5060;branch=z9hG4bKWDSUKUHWFEXQSVOUVJGM From: <sip:400@10.33.2.5;user=phone>;tag=DUOROSXSOYJJLNBFRQTG To: <sip:*72100@10.33.8.53;user=phone> Call-ID: GMNOVQRRXUUCYCQSFAHS@10.33.2.5 CSeq: 1 INVITE Contact: <sip:400@10.33.2.5:5060> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE User-Agent: Sip Message Generator V1.0.0.5 User-to-User: 31323334;pd=4 Content-Type: application/sdp Content-Length: 155 Version 7.2 Mediant 500 MSBR...
Page 566: Local Handling Of Bri Call Forwarding
Mediant 500 MSBR 30.6.6 Local Handling of BRI Call Forwarding You can configure the device to handle BRI call forwarding per BRI extension line, using the Supplementary Services table. Upon receipt of an ISDN Facility message from the BRI phone user, the device retrieves and stores the user's call forwarding information.
Page 567: Enabling Call Waiting
You can enable call waiting per port in the Call Waiting table (see Configuring Call Waiting on page 609). For ports that are not configured in the table, call waiting is according to the global parameter, as described in the procedure below. Version 7.2 Mediant 500 MSBR...
Page 568: Message Waiting Indication
Mediant 500 MSBR  To enable and configure call waiting: Open the Supplementary Services Settings page (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services Settings). Figure 30-10: Configuring Call Waiting From the 'Enable Call Waiting' drop-down list (EnableCallWaiting), select Enable.
Page 569 When a change in the status occurs (e.g., a new voice message is waiting or the user has retrieved a message from the voice mail), the PBX initiates an ISDN Setup message with Facility IE containing an MWI Activate request, which includes the new Version 7.2 Mediant 500 MSBR...
Page 570: Caller Id
Mediant 500 MSBR number of voice messages waiting for the user. The device forwards this information to the softswitch by sending a SIP NOTIFY. Depending on PBX support, the MWIInterrogationType parameter can be configured to handle these MWI Interrogation messages in different ways. For example, some PBXs support only the MWI Activate request (and not MWI Interrogation request).
Page 571: Debugging A Caller Id Detection On Fxo
ID. If the above does not solve the problem, you need to record the caller ID signal (and send it to AudioCodes), as described below.  To record the caller ID signal using the debug recording mechanism: Access the FAE page (by appending "FAE"...
Page 572: Caller Id On The Ip Side
FXS or BRI port initiates a call and invites two remote IP-based participants. The device also supports multiple, concurrent three-way conference calls. The device supports the following three-way conference modes:  Conference Managed by External, AudioCodes Conferencing (Media) Server: User's Manual Document #: LTRT-10375...
Page 573 You can configure the maximum number of simultaneous, on- board conferences, using the MaxInBoardConferenceCalls parameter.The mode is configured by setting the 3WayConferenceMode parameter to 2. Version 7.2 Mediant 500 MSBR...
Page 574 Mediant 500 MSBR Note: • Instead of using the flash-hook button to establish a three-way conference call, you can dial a user-defined hook-flash code (e.g., "*1"), configured by the HookFlashCode parameter. • Three-way conferencing is applicable only to FXS and BRI interfaces.
Page 575: Emergency E911 Phone Number Services
(known as Automatic Number Identification - ANI). Once the PSAP receives the call, it searches for the physical address that is associated with the calling party's telephone number (in the Automatic Location Identification database - ALI). Version 7.2 Mediant 500 MSBR...
Page 576: Fxs Device Emulating Psap Using Did Loop-Start Lines
Mediant 500 MSBR 30.11.1 FXS Device Emulating PSAP using DID Loop-Start Lines The device's FXS interface can be configured to emulate PSAP (using DID loop start lines), according to the Telcordia GR-350-CORE specification. Figure 30-13: FXS Device Emulating PSAP using DID Loop-Start Lines The call flow of an E911 call to the PSAP is as follows: The E911 tandem switch seizes the line.
Page 577 8 digits "nnnnnnnn" (ANI) "KPnnnnnnnnST" 12 digits "nnnnnnnnnnnn" (ANI) "KPnnnnnnnnnnnnSTP" 12 digits ANI and 10 digits PANI "KPnnnnnnnnnnnnSTKPmmmmmmmmmmST" two digits "nn" "KPnnSTP" The MF KP, ST, and STP digits are mapped as follows:  * for KP Version 7.2 Mediant 500 MSBR...
Page 578 Mediant 500 MSBR  # for ST  B for STP For example, if ANI and PANI are received, the SIP INVITE contains the following From header: From: <sip:*nnnnnnnnnnnn#*mmmmmmmmmm#@10.2.3.4>;tag=1c14 Note: It is possible to remove the * and # characters, using the device's number manipulation rules.
Page 579: Fxo Device Interworking Sip E911 Calls From Service Provider's Ip Network To Psap Did Lines
PSAP, the device generates a SIP INFO message that includes a "hookflash" body, or sends RFC 2833 hookflash Telephony event (according to the HookFlashOption parameter). Following the "hookflash" Wink signal, the PSAP sends DTMF digits. These digits are Version 7.2 Mediant 500 MSBR...
Page 580 Mediant 500 MSBR detected by the device and forwarded to the IP, using RFC 2833 telephony events (or inband, depending on the device's configuration). Typically, this Wink signal followed by the DTMF digits initiates a call transfer. For supporting the E911 service, used the following configuration parameter settings: ...
Page 581 To: <sip:301@10.33.37.79;user=phone> Call-ID: 77162335841200014153@10.33.37.78 CSeq: 1 INVITE Contact: <sip:101@10.33.37.78> Supported: em,100rel,timer,replaces,path Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO ,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-FXO/v.7.20A.000.038 Privacy: none P-Asserted-Identity: "0123456789" <sip:3333344444@audiocodes.com> Content-Type: application/sdp Content-Length: 253 o=AudiocodesGW 771609035 771608915 IN IP4 10.33.37.78 s=Phone-Call c=IN IP4 10.33.37.78 Version 7.2 Mediant 500 MSBR...
Page 582: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls
Mediant 500 MSBR t=0 0 m=audio 4000 RTP/AVP 8 0 101 a=rtpmap:8 pcma/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv  Example B: The detection of a Wink signal generates the following SIP INFO message: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060...
Page 583: Multilevel Precedence And Preemption
MLPP can be enabled for all calls, using the global parameter, CallPriorityMode, or for specific calls using the Tel Profile parameter, CallPriorityMode. Version 7.2 Mediant 500 MSBR...
Page 584 Mediant 500 MSBR Note: • MLPP is applicable only to ISDN PRI and BRI interfaces. • The device provides MLPP interworking between SIP and ISDN (both directions). • For Trunk Groups configured with call preemption, all must be configured to MLPP [1] or all configured to Emergency [2].
Page 585 INVITE messages for Tel-to-IP calls when MLPP priority call handling is used. This is configured using the RPRequired parameter. • For a complete list of the MLPP parameters, see MLPP and Emergency Call Parameters on page 1124. Version 7.2 Mediant 500 MSBR...
Page 586: Mlpp Preemption Events In Sip Reason Header
Mediant 500 MSBR 30.12.1 MLPP Preemption Events in SIP Reason Header The device sends the SIP Reason header (as defined in RFC 4411) to indicate the reason and type of a preemption event. The device sends a SIP BYE or CANCEL request, or SIP...
Page 587: Precedence Ring Tone
BRI call forwarding services for point-to-multipoint configurations (according to ETSI 300 207-1) - Call Forward Busy (CFB), Call Forward No Reply (CFNR), and Call Forward Unconditional (CFU).  Routing IP-to-Tel calls (including voice and fax) to specific endpoints based on called Version 7.2 Mediant 500 MSBR...
Page 588 Mediant 500 MSBR line extension number (local number). To enable this functionality, in the Trunk Group Settings table, set the 'Channel Select Mode' field to Select Trunk by Supplementary Services Table for the Trunk Group to which the port belongs (see Configuring Trunk Group Settings on page 487).
Page 589 General Index Defines an index number for the new table row. [ISDNSuppServ_Index] Note: Each row must be configured with a unique index. Global Phone Number Defines a global telephone extension number for the endpoint. The Version 7.2 Mediant 500 MSBR...
Page 590 Mediant 500 MSBR Parameter Description phone-number global number is used for the following functionalities:  [ISDNSuppServ_PhoneNu Endpoint registration mber]  IP-to-Tel routing  Mapping between local and global (E.164) numbers between Tel and IP sides respectively Local Phone Number Defines a local telephone extension number for the endpoint (e.g., the PBX extension number).
Page 591: Detecting Collect Calls
Reverse Charging Indication IE  Facility IE When the device detects a collect call, it adds a proprietary header (X-Siemens-Call-Type: collect call) to the outgoing SIP INVITE message. No special configuration is required for the feature. Version 7.2 Mediant 500 MSBR...
Page 592: Advice Of Charge Services For Euro Isdn
The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call) using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
Page 593: Configuring Charge Codes
You can configure up to 25 different Charge Codes, where each table row represents a Charge Code. Each Charge Code can include up to four different time periods in a day (24 hours). The device selects the time period by comparing the device's current time to the Version 7.2 Mediant 500 MSBR...
Page 594 Mediant 500 MSBR end time of each time period of the selected Charge Code. The device generates the number of pulses on answer once the call is connected, and from that point on, it generates a pulse for each pulse interval. If a call starts at a certain time period and crosses to the next, the information of the next time period is used.
Page 595: Configuring Voice Mail
Voice Mail is applicable only to FXO and CAS interfaces.  To configure voice mail: Open the Voice Mail Settings page (Setup menu > Signaling & Media tab > Gateway folder > Voice Mail Settings). Version 7.2 Mediant 500 MSBR...
Page 596 Mediant 500 MSBR Under the General group, configure the following: • 'Line Transfer Mode' (LineTransferMode): Defines the call transfer method used by the device. • 'Voice Mail Interface' (VoiceMailInterface): Enables the device's Voice Mail feature and defines the communication method between the device and PBX.
Page 597: Converting Accented Characters From Ip To Tel
(e.g., ä to "ae" instead of the default "a"). The following procedure describes how to configure Character Conversion rules through the Web interface. You can also configure it through ini file (CharConversion) or CLI (configure voip > gateway dtmf-supp-service dtmf-and-dialing > char-conversion). Version 7.2 Mediant 500 MSBR...
Page 598 Mediant 500 MSBR  To configure a Character Conversion rule: Open the Char Conversion table (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Char Conversion). Click New; the following dialog box appears: Figure 30-22: Char Conversion Table - Add Dialog Box The figure above shows a configuration example where ä...
Page 599: Analog Gateway
To configure keypad sequences: Open the Keypad Features page (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Keypad Features). Figure 31-1: Configuring Phone Key Sequences to Activate Various Services Version 7.2 Mediant 500 MSBR...
Page 600: Configuring Metering Tones
Mediant 500 MSBR Configure the keypad features as required. Click Apply. 31.2 Configuring Metering Tones The FXS interfaces can generate 12/16 KHz metering pulses toward the Tel side (e.g., for connection to a pay phone or private meter). Tariff pulse rate is according to the device's Charge Codes table.
Page 601: Configuring Authentication
For all endpoints: Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP Definitions folder > Proxy & Registration), and then configure the 'Authentication Mode' (AuthenticationMode) parameter to Per Endpoint: Figure 31-4: Enabling Authentication per Endpoint Version 7.2 Mediant 500 MSBR...
Page 602 Mediant 500 MSBR • Endpoints per Trunk Group: Open the Trunk Group Settings table (see Configuring Trunk Group Settings on page 487), and then for the required Trunk Group ID, configure the 'Registration Mode' parameter to Per Endpoint (TrunkGroupSettings_RegistrationMode). Open the Authentication table (Setup menu > Signaling & Media tab > Gateway folder >...
Page 603: Configuring Automatic Dialing
(Read-only) Displays the module number on which the port is located. [TargetOfChannel_Modul Port (Read-only) Displays the port number. port [TargetOfChannel_Port] Port Type (Read-only) Displays the port type (FXS or FXO). [TargetOfChannel_PortT ype] Destination Phone Defines the destination telephone number to automatically dial. Version 7.2 Mediant 500 MSBR...
Page 604: Configuring Caller Display Information
Mediant 500 MSBR Parameter Description Number dst-number [TargetOfChannel_Desti nation] Auto Dial Status Enables automatic dialing.  auto-dial-status [0] Disable = Automatic dialing for the specific port is disabled.  [1] Enable = (Default) Automatic dialing is enabled and the phone...
Page 605 [0] Allowed = The caller ID string is sent when a Tel-to-IP call is made. [CallerDisplayInfo_IsCid  [1] Restricted = The caller ID string is not sent. The Caller ID is sent Restricted] to the remote side using only the SIP P-Asserted-Identity or P- Version 7.2 Mediant 500 MSBR...
Page 606: Configuring Call Forward
Mediant 500 MSBR Parameter Description Preferred-Identity headers, according to the AssertedIdMode parameter. Note: The parameter is overridden by the 'Presentation' parameter in the Source Number Manipulation table (see Configuring Source/Destination Number Manipulation on page 523). 31.7 Configuring Call Forward The Call Forward table lets you configure call forwarding per FXS or FXO port for IP-to-Tel calls.
Page 607 'No Reply Time' field.  [5] Don't Disturb = Immediately reject incoming calls. Call Forward Forward Destination Defines the telephone number or URI (<number>@<IP address>) to where the call is forwarded. destination Version 7.2 Mediant 500 MSBR...
Page 608: Configuring Caller Id Permissions
Mediant 500 MSBR Parameter Description [FwdInfo_Destination] Note: If the parameter is configured with only a telephone number and a Proxy isn't used, this forwarded-to phone number must be specified in the Tel-to-IP Routing table (see Configuring Tel-to-IP Routing Rules on page 495).
Page 609: Configuring Call Waiting
The section is applicable only to FXS interfaces. The following procedure describes how to configure call waiting per port through the Web interface. You can also configure it through ini file (CallWaitingPerPort) or CLI (configure voip > gateway analog call-waiting). Version 7.2 Mediant 500 MSBR...
Page 610 Mediant 500 MSBR  To enable call waiting per port: Open the Call Waiting table (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Call Waiting). Select the row corresponding to the port that you want to configure, and then click Edit;...
Page 611: Rejecting Anonymous Calls
 To configure distinctive ringing and call waiting tones per FXS port: Open the Tone Index table (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Tone Index). Version 7.2 Mediant 500 MSBR...
Page 612 Mediant 500 MSBR Click New; the following dialog box appears: Figure 31-9: Tone Index Table - Add Dialog Box The figure above shows a configuration example for using distinctive ringing and call waiting tones of Index #9 ('Priority Index' 1) in the CPT file for FXS endpoints 1 through 4 when a call is received from a calling (source) number with prefix 2.
Page 613: Fxs/Fxo Coefficient Types
To select the FXO and FXS Coefficient types: Open the Analog Settings page (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > Analog Settings). Figure 31-10: Configuring FXS/FXO Coefficient Types Version 7.2 Mediant 500 MSBR...
Page 614: Fxo Operating Modes
Mediant 500 MSBR From the 'FXS Coefficient Type' drop-down list (FXSCountryCoefficients), select the required FXS Coefficient type. From the 'FXO Coefficient Type' drop-down list (CountryCoefficients), select the required FXO Coefficient type. Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
Page 615 Voice Detection: the device sends a 200 OK in response to an INVITE only when it detects the start of speech (fax or modem answer tone) from the Tel side. Note that the IPM detectors must be enabled. Version 7.2 Mediant 500 MSBR...
Page 616: Two-Stage Dialing
Mediant 500 MSBR 31.13.1.2 Two-Stage Dialing Two-stage dialing is when the IP caller is required to dial twice. The caller initially dials to the FXO device and only after receiving a dial tone from the PBX (via the FXO device), dials the destination telephone number.
Page 617: Fxo Operations For Tel-To-Ip Calls
Hold/Transfer Toward the IP side • Blind Transfer to the Tel side 31.13.2.1 Automatic Dialing The SIP call flow diagram below illustrates Automatic Dialing: To configure Automatic dialing, see Configuring Automatic Dialing on page 603). Version 7.2 Mediant 500 MSBR...
Page 618: Collecting Digits Mode
Mediant 500 MSBR 31.13.2.2 Collecting Digits Mode When automatic dialing is not configured, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 31-12: Call Flow for Collecting Digits Mode 31.13.2.3 FXO Supplementary Services The FXO supplementary services include the following: ...
Page 619: Call Termination On Fxo Devices
Note: This method operates correctly only if silence suppression is not used.  Protocol-based termination of the call from the IP side Note: The implemented disconnect method must be supported by the CO or PBX. Version 7.2 Mediant 500 MSBR...
Page 620: Call Termination Before Call Establishment
Mediant 500 MSBR 31.13.3.2 Call Termination before Call Establishment The device supports the following call termination methods before a call is established:  Call termination upon receipt of SIP error response (in Automatic Dialing mode): By default, when the FXO device operates in Automatic Dialing mode, there is no method to inform the PBX if a Tel-to-IP call has failed (SIP error response - 4xx, 5xx or 6xx - is received).
Page 621: Dialing From Remote Extension (Phone At Fxs)
The following procedure describes how to dial from a PBX line (i.e., from a telephone directly connected to the PBX) or from the PSTN to the 'remote PBX extension' (i.e., telephone connected to the FXS interface). Version 7.2 Mediant 500 MSBR...
Page 622: Message Waiting Indication For Remote Extensions
Mediant 500 MSBR  To dial from a telephone directly connected to the PBX or from the PSTN:  Dial the PBX subscriber number (e.g., phone number 101) in the same way as if the user’s phone was connected directly to the PBX. As soon as the PBX rings the FXO device, the ring signal is ‘sent’...
Page 623: Fxs Gateway Configuration
For the transfer to function in remote PBX extensions, Hold must be disabled at the FXS device (i.e., Enable Hold = 0) and hook-flash must be transferred from the FXS to the FXO (HookFlashOption = 4). Version 7.2 Mediant 500 MSBR...
Page 624: Fxo Gateway Configuration
Mediant 500 MSBR 31.14.6 FXO Gateway Configuration The following procedure describes how to configure the FXO interface (to which the PBX is directly connected).  To configure the FXO interface: In the Trunk Group table page (see Configuring Trunk Groups on page 485 ), assign the phone numbers 200 to 204 to the device’s FXO endpoints.
Page 625: Session Border Controller Application
Part VI Session Border Controller Application...
Page 627: Sbc Overview
The device's topology hiding is provided by implementing back-to-back user agent (B2BUA) leg routing: • Strips all incoming SIP Via header fields and creates a new Via value for the outgoing message. • Each leg has its own Route/Record Route set. Version 7.2 Mediant 500 MSBR...
Page 628: B2Bua And Stateful Proxy Operating Modes
Mediant 500 MSBR • User-defined manipulation of SIP To, From, and Request-URI host names. • Generates a new SIP Call-ID header value (different between legs). • Changes the SIP Contact header and sets it to the device's address. • Layer-3 topology hiding by modifying source IP address in the SIP IP header.
Page 629 XML body).  In some setups, the SIP client authenticates using a hash that is performed on one or more of the headers that B2BUA changes (removes). Therefore, implementing B2BUA would cause authentication to fail. Version 7.2 Mediant 500 MSBR...
Page 630 Mediant 500 MSBR  For facilitating debugging procedures, some administrators require that the value in the Call-ID header remains unchanged between the inbound and outbound SBC legs. As B2BUA changes the Call-ID header, such debugging requirements would fail. The operating mode can be configured per the following configuration entities: ...
Page 631: Call Processing Of Sip Dialog Requests
The device obtains the source and destination URLs from certain SIP headers. Once the URLs are determined, the user and host parts of the URLs can be used as matching rule characteristics for classification, message manipulation, and call routing. • All SIP requests (e.g., INVITE) except REGISTER: Version 7.2 Mediant 500 MSBR...
Page 632 Mediant 500 MSBR ♦ Source URL: Obtained from the From header. If the From header contains the value 'Anonymous', the source URL is obtained from the P-Preferred- Identity header. If the P-Preferred-Identity header does not exist, the source URL is obtained from the P-Asserted-Identity header.
Page 633: User Registration
The device provides a dynamic registration database that it updates according to registration requests traversing it. Each database entry for a user represents a binding between an AOR (obtained from the SIP To header), optional additional AORs, and one or Version 7.2 Mediant 500 MSBR...
Page 634: Classification And Routing Of Registered Users
Mediant 500 MSBR more contacts (obtained from the SIP Contact headers). Database bindings are added upon successful registration responses from the proxy server (SIP 200 OK). The device removes database bindings in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero).
Page 635: General Registration Request Processing
 The graceful period is also used before removing a user from the registration database when the device receives a successful unregister response (200 OK) from Version 7.2 Mediant 500 MSBR...
Page 636: Registration Restriction Control
Mediant 500 MSBR the registrar/proxy server. This is useful in scenarios, for example, in which users (SIP user agents) such as IP Phones erroneously send unregister requests. Instead of immediately removing the user from the registration database upon receipt of a...
Page 637: Media Anchoring
SDP:  Origin: IP address, session and version id  Session connection attribute ('c=' field)  Media connection attribute ('c=' field)  Media port number  RTCP media attribute IP address and port Version 7.2 Mediant 500 MSBR...
Page 638: Direct Media
Mediant 500 MSBR The device uses different local ports (e.g., for RTP, RTCP and fax) for each leg (inbound and outbound). The local ports are allocated from the Media Realm associated with each leg. The Media Realm assigned to the leg's IP Group (in the IP Groups table) is used. If not assigned to the IP Group, the Media Realm assigned to the leg's SIP Interface (in the SIP Interfaces table) is used.
Page 639 Microsoft Server (direct media is required in the Skype for Business environment). For more information, see Configuring IP Groups on page 333. IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Version 7.2 Mediant 500 MSBR...
Page 640: Restricting Audio Coders
Mediant 500 MSBR Direct Media' parameter is set to Enable (SIPInterface_SBCDirectMedia = 1). IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Direct Media' parameter Enable When Single (SIPInterface_SBCDirectMedia = 2), and the endpoints are located behind the same NAT.
Page 641: Prioritizing Coder List In Sdp Offer
The BFCP stream is identified in the SDP as 'm=application <port> UDP/BFCP' and a dedicated UDP port is used for the BFCP streams. 32.5.6 Interworking Miscellaneous Media Handling This section describes various interworking features relating to media handling. Version 7.2 Mediant 500 MSBR...
Page 642: Interworking Rtp Redundancy
Mediant 500 MSBR 32.5.6.1 Interworking RTP Redundancy The device supports interworking of RTP redundancy (according to RFC 2198) between SIP entities. Employing IP Profiles, you can configure RTP redundancy handling per SIP entity:  Generate RFC 2198 redundant packets (IpProfile_RTPRedundancyDepth parameter).
Page 643: Sbc Authentication
If validation succeeds, the device verifies client identification. It checks that the username and password received from the client is the same username and password in the device's User Information table / database (see SBC Version 7.2 Mediant 500 MSBR...
Page 644: User Authentication Based On Radius
Mediant 500 MSBR User Information for SBC User Database on page 792). If the client is not successfully authenticated after three attempts, the device sends a SIP 403 (Forbidden) response to the client. If the user is successfully identified, the device accepts the SIP message request.
Page 645: Resultant Invite Traversing Device
The prefix is removed before the resultant INVITE is sent to the destination. Figure 32-6: SIP 3xx Response Handling The process of this feature is described using an example: The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User@IPPBX:5060;transport=tcp;param=a>;q=0.5). Version 7.2 Mediant 500 MSBR...
Page 646: Local Handling Of Sip 3Xx
Mediant 500 MSBR The device replaces the Contact header value with the special prefix and database key value as user part, and with the device's URL as host part (e.g., Contact: <sip:Prefix_Key_User@SBC:5070;transport=udp>;q=0.5). The device sends this manipulated SIP 3xx response to the Far-End User (FEU).
Page 647: Interworking Sip Refer Messages
 Transparent handling: The device forwards the REFER with the Refer-To header unchanged.  Re-routing through SBC: The device changes the Refer-To header so that the re- routed INVITE is sent through the SBC application. Version 7.2 Mediant 500 MSBR...
Page 648: Interworking Sip Prack Messages
Mediant 500 MSBR  IP Group Name: The device sets the host part in the REFER message to the name configured for the IP Group in the IP Groups table. 32.8.4 Interworking SIP PRACK Messages The device supports interworking of SIP Provisional Response ACKnowledgement (PRACK) messages (18x).
Page 649 Media RTP Detection Mode', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Figure 32-7: SBC Early Media RTP 18x without SDP Version 7.2 Mediant 500 MSBR...
Page 650: Interworking Sip Re-Invite Messages
Mediant 500 MSBR Figure 32-8: Early Media RTP - SIP 18x with SDP 32.8.7 Interworking SIP re-INVITE Messages The device supports interworking of SIP re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs.
Page 651: Interworking Sip Update 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'. To configure IP Profiles, see Configuring IP Profiles on page 404. Version 7.2 Mediant 500 MSBR...
Page 652: Interworking Sip Via Headers
Mediant 500 MSBR 32.8.12 Interworking SIP Via Headers The device supports the interworking of SIP Via headers between SIP entities. For the outgoing message sent to a SIP entity, the device can remove or retain all the Via headers received in the incoming SIP request from the other side. Employing IP Profiles, you can configure this interworking feature per SIP entity, using the IpProfile_SBCKeepVIAHeaders parameter (see Configuring IP Profiles on page 404).
Page 653: Utilizing Gateway Channel Resources For Sbc
To support the feature, the License Key installed on your device must include the "TDMtoSBC" feature key; otherwise, to purchase the feature, contact your AudioCodes sales representative to upgrade your License Key. • The maximum number of SBC sessions that can be supported is according to the device's maximum SBC capacity (see Channel Capacity on page 1243).
Page 654 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 655: Enabling The Sbc Application
Open the Applications Enabling page (Setup menu > Signaling & Media tab > Core Entities folder > Applications Enabling). From the 'SBC Application' drop-down list, select Enable: Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Version 7.2 Mediant 500 MSBR...
Page 656 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 657: Configuring General Sbc Settings
XML body. Below is an example of an XML body where the call-id, tags, and URIs have been replaced by the device: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="10" state="partial" entity="sip:alice@example.com"> <dialog id="zxcvbnm3" call-id="67402270@10.132.10.150" local-tag="1c137249965" Version 7.2 Mediant 500 MSBR...
Page 658 Mediant 500 MSBR remote-tag="CCDORRTDRKIKWFVBRWYM" direction="initiator"> <state event="replaced">terminated</state> </dialog> <dialog id="sfhjsjk12" call-id="67402270@10.132.10.150" local-tag="1c137249965" remote-tag="CCDORRTDRKIKWFVBRWYM" direction="receiver"> <state reason="replaced">confirmed</state> <replaces call-id="67402270@10.132.10.150" local-tag="1c137249965" remote-tag="CCDORRTDRKIKWFVBRWYM"/> <referred-by> sip:bob-is-not-here@vm.example.net </referred-by> <local> <identity display="Jason Forster"> sip:jforsters@home.net </identity> <target uri="sip:alice@pc33.example.com"> <param pname="+sip.rendering" pval="yes"/> </target> </local> <remote> <identity display="Cathy Jones">...
Page 659: Configuring Admission Control
5 is provided from the SRD's shared pool. If the SDR's shared pool is currently empty and resources for new calls are required, the quota is taken from the device's total capacity, if available. For example, if IP Group ID 1 needs to handle 21 calls, it's Version 7.2 Mediant 500 MSBR...
Page 660 Mediant 500 MSBR guaranteed 10, the SRD's shared pool provides another 10, and the last call is provided from the device's total call capacity support (e.g., of 200). Requests that reach the user-defined call limit (maximum concurrent calls and/or call rate) are sent to an alternative route if configured in the IP-to-IP Routing table.
Page 661 [0] Both = (Default) Rule applies to inbound and outbound SIP dialogs. [SBCAdmissionControl_  [1] Inbound = Rule applies only to inbound SIP dialogs. RequestDirection]  [2] Outbound = Rule applies only to outbound SIP dialogs. Limit Version 7.2 Mediant 500 MSBR...
Page 662 Mediant 500 MSBR Reserved Capacity Defines the guaranteed (minimum) call capacity. reservation The default is 0 (i.e., no reserved capacity). [SBCAdmissionControl_ Note: Reservation]  Reserved call capacity is applicable only to IP Groups and SRDs (i.e., 'Limit Type' parameter configured to IP Group or SRD). If you configure the 'Limit Type' parameter to SIP Interface, leave the 'Reserved Capacity' parameter at its' default (i.e., 0).
Page 663: Routing Sbc
 To configure the action for unclassified calls: Open the SBC General Settings (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings). Version 7.2 Mediant 500 MSBR...
Page 664 Mediant 500 MSBR From the 'Unclassified Calls' drop-down list, select Reject to reject unclassified calls or Allow to accept unclassified calls: Figure 37-1: Configuring Action for Classification Failure Click Apply. If you configure the parameter to Allow, the incoming SIP dialog is assigned to an IP Group as follows: The device determines on which SIP listening port (e.g., 5061) the incoming SIP...
Page 665 Proxy Set feature). • The device saves incoming SIP REGISTER messages in its registration database. If the REGISTER message is received from a User-type IP Group, the device sends the message to the configured destination. Version 7.2 Mediant 500 MSBR...
Page 666 Mediant 500 MSBR The flowchart below illustrates the classification process: Figure 37-2: Classification Process (Identifying IP Group or Rejecting Call) The following procedure describes how to configure Classification rules through the Web interface. You can also configure it through ini file (Classification) or CLI (configure voip >...
Page 667 Defines a descriptive name, which is used when associating the row in other tables. classification-name The valid value is a string of up to 40 characters. By default, no name is [Classification_Classifica defined. tionName] Note: Each row must be configured with a unique name. Version 7.2 Mediant 500 MSBR...
Page 668 Mediant 500 MSBR Source SIP Interface Assigns a SIP Interface to the rule as a matching characteristic for the incoming SIP dialog. src-sip-interface-name The default is Any (i.e., all SIP Interfaces belonging to the SRD assigned [Classification_SrcSIPInt to the rule).
Page 669 SRD's assigned Routing Policy is used) while for others a different Routing Policy is specified to override the SRD's assigned Routing Policy. By default, no value is defined. To configure Routing Policies, see Configuring SBC Routing Policy Rules on page 692. Version 7.2 Mediant 500 MSBR...
Page 670: Classification Based On Uri Of Selected Header Example
Mediant 500 MSBR Source IP Group Assigns an IP Group to the matched incoming SIP dialog. src-ip-group-name By default, no value is defined. [Classification_SrcIPGro To configure IP Groups, see Configuring IP Groups on page 333. upName] Note: The IP Group must be associated with the assigned SRD (see the 'SRD' parameter in the table).
Page 671: Configuring Sbc Ip-To-Ip Routing
IP address in dotted-decimal notation or FQDN. Routing to a host name can be resolved using NAPTR/SRV/A-Record.  Request-URI of incoming SIP dialog-initiating requests.  Any registered user in the registration database. If the Request-URI of the incoming Version 7.2 Mediant 500 MSBR...
Page 672 Mediant 500 MSBR INVITE exists in the database, the call is sent to the corresponding contact address specified in the database.  According to result of an ENUM query.  Hunt Group - used for call survivability of call centers (see Configuring Call Survivability for Call Centers on page 737).
Page 673 A request sent by the device is responded with one of the following: ♦ SIP response code (i.e., 4xx, 5xx, and 6xx SIP responses) configured in the Alternative Routing Reasons table (see Configuring SIP Response Codes for Alternative Routing Reasons on page 690). Version 7.2 Mediant 500 MSBR...
Page 674 Mediant 500 MSBR ♦ SIP 408 Timeout or no response (after timeout). • The DNS resolution includes IP addresses that the device has yet to try (for the current call). Messages are re-routed with the same SIP Call-ID and CSeq header fields (increased by 1).
Page 675 You can also configure it through ini file (IP2IPRouting) or CLI (configure voip > sbc routing ip2ip-routing).  To configure an IP-to-IP routing rule: Open the IP-to-IP Routing table (Setup menu > Signaling & Media tab > SBC folder > Routing > IP-to-IP Routing). Version 7.2 Mediant 500 MSBR...
Page 676 Mediant 500 MSBR Click New; the following dialog box appears: Figure 37-4: IP-to-IP Routing Table - Dialog Box Configure an IP-to-IP routing rule according to the parameters described in the table below. Click Apply. Table 37-2: IP-to-IP Routing Table Parameter Descriptions...
Page 677 For more information, see Configuring SBC Routing Policy Rules on page 692. Request Type Defines the SIP dialog request type (SIP Method) of the incoming SIP dialog. request-type  [0] All (default) [IP2IPRouting_RequestTy  [1] INVITE  [2] REGISTER Version 7.2 Mediant 500 MSBR...
Page 678 Mediant 500 MSBR  [3] SUBSCRIBE  [4] INVITE and REGISTER  [5] INVITE and SUBSCRIBE  [6] OPTIONS Source Username Prefix Defines the prefix of the user part of the incoming SIP dialog's source URI (usually the From URI). You can use special notations for denoting src-user-name-prefix the prefix.
Page 679 Note: The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in this table). For more information, see Configuring SBC Routing Policy Rules on page 692. Action Version 7.2 Mediant 500 MSBR...
Page 680 Mediant 500 MSBR Destination Type Determines the destination type to which the outgoing SIP dialog is sent. dst-type  [0] IP Group = (Default) The SIP dialog is sent to the IP Group as [IP2IPRouting_DestType] defined in the 'Destination IP Group' (IP2IPRouting_DestIPGroupName) parameter.
Page 681 Interface must be one that is associated with the Routing Policy or with a shared Routing Policy (i.e., the Routing Policy is associated with one or more Shared SRDs). If the Routing Policy is shared, the Version 7.2 Mediant 500 MSBR...
Page 682 Mediant 500 MSBR SIP Interface can be one that is associated with any SRD or Routing Policy (but it's recommended that it belong to the same SRD/Routing Policy or to shared SRD/Routing Policy to avoid "bleeding"). Destination Address Defines the destination address to where the call is sent. The address can be an IP address or a domain name (e.g., domain.com).
Page 683 Internal (see above). The valid value syntax (case-insensitive) is:  For SIP response codes: reply(response='<code>') The following example sends a SIP 200: reply(response='200')  For redirection responses: redirect(response='<code>',contact='sip:'+….) redirect(contact='…',response='<code>') redirect(contact='sip:user@host') Version 7.2 Mediant 500 MSBR...
Page 684: Configuring Rerouting Of Calls To Fax Destinations
Mediant 500 MSBR Examples:  The device responds to the dialog with a SIP 300 redirect response that includes a contact value: redirect(response=’300’,contact=’sip:102@host’)  The device redirects the call from the sender to a SIP Recording Server (SRS): redirect(response='302',contact='sip:'+header.to.ur l.user+'@siprecording.com') Note: ...
Page 685 IP-to-IP Routing Rule #1 - routes fax calls from IP Group #0 to IP Group #2: Match Source IP Group HQ (IP Group #0) Call Trigger Fax Rerouting Action Destination Type IP Group Destination IP Group Fax (IP Group #2) Version 7.2 Mediant 500 MSBR...
Page 686: Configuring Specific Udp Ports Using Tag-Based Routing
Mediant 500 MSBR 37.2.2 Configuring Specific UDP Ports using Tag-based Routing You can configure the device to use a specific local UDP port for each SIP entity (e.g., PBX) communicating with a common proxy server (e.g., ITSP). The figure below illustrates an example scenario of such an implementation, whereby the device uses a specific local UDP port (e.g., 6001, 6002, and 6003) for each IP PBX, on the leg interfacing with the...
Page 687 IP Group for the third IP PBX ("Type" and "Port" tags are later used to identify the IP PBX and assign it a local UDP port 6003 on the leg interfacing with the proxy server): General Index Name PBX-3 Type Server SBC Advanced Version 7.2 Mediant 500 MSBR...
Page 688 Mediant 500 MSBR Tags Type=PBX;Port=6003 • IP Group for the proxy server ("Type" tag is later used to identify proxy server): General Index Name ITSP Type Server SBC Advanced Tags Type=ITSP Open the Call Setup Rules table (see Configuring Call Setup Rules on page 372), and then configure the following Call Setup rules: •...
Page 689 "Type=ITSP") to the IP PBXs (identified by the specific port assigned to the IP PBX by the value of the destination tag name "Port"): General Index Name ITSP-to-PBX Match Source Tag Type=ITSP Action Destination Type Destination Tag Routing Tag Name Port Version 7.2 Mediant 500 MSBR...
Page 690: Configuring Sip Response Codes For Alternative Routing Reasons
Mediant 500 MSBR 37.3 Configuring SIP Response Codes for Alternative Routing Reasons The Alternative Routing Reasons table lets you configure up to 20 SIP response codes for call release (termination) reasons, which then trigger alternative routing. If a call (outgoing SIP dialog-initiating methods, e.g., INVITE, OPTIONS, and SUBSCRIBE messages) is...
Page 691 Gateway; [503] Service Unavailable; [504] Server Timeout; [505] Version Not Supported; [513] Message Too Large; [600] Busy Everywhere; [603] Decline; [604] Does Not Exist Anywhere; [606] Not Acceptable; [805] Admission Failure; [806] Media Limits Exceeded; [818] Signalling Limits Exceeded. Version 7.2 Mediant 500 MSBR...
Page 692: Configuring Sbc Routing Policy Rules
Mediant 500 MSBR 37.4 Configuring SBC Routing Policy Rules The Routing Policies table lets you configure up to 41 Routing Policy rules. A Routing Policy determines the routing and manipulation (inbound and outbound) rules per SRD in a multiple SRD configuration topology. The Routing Policy also configures the following: ...
Page 693 Web interface. You can also configure it through ini file (SBCRoutingPolicy) or CLI (configure voip > sbc routing sbc-routing-policy).  To configure a Routing Policy rule: Open the Routing Policies table (Setup menu > Signaling & Media tab > SBC folder > Routing > Routing Policies). Version 7.2 Mediant 500 MSBR...
Page 694 Mediant 500 MSBR Click New; the following dialog box appears: Figure 37-9: Routing Policies Table - Add Dialog Box Configure the Routing Policy rule according to the parameters described in the table below. Click Apply. Table 37-4: Routing Policies table Parameter Descriptions...
Page 695: Configuring Ip Group Sets
Group #1 in the IP Group Set, the second call to IP Group #2, and the third call to IP Group #3. If the call sent to IP Group #1 is rejected, the device employs alternative routing and sends it to IP Group #4. Version 7.2 Mediant 500 MSBR...
Page 696 Mediant 500 MSBR Once you have configured your IP Group Set, to implement call load-balancing by IP Groups, do one of the following:  In the IP-to-IP Routing table, configure the routing rule's 'Destination Type' parameter to IP Group Set, and then assign it the IP Group Set in the 'IP Group Set' parameter.
Page 697 Group Set. Select the IP Group Set row for which you want to assign IP Groups, and then click the IP Group Set Member link located below the table; the IP Group Set Member table appears. Version 7.2 Mediant 500 MSBR...
Page 698 Mediant 500 MSBR Click New; the following dialog box appears: Figure 37-11: IP Group Set Member Table - Dialog Box Configure IP Group Set members according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.
Page 699: Sbc Manipulations
IP Groups respectively (if any, in the IP Groups table). Below is an example of a call flow and consequent SIP URI manipulations:  Incoming INVITE from LAN: INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 Via: SIP/2.0/UDP 10.2.2.6;branch=z9hGLLLLLan From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe To: <sip:1000@10.2.2.3;user=phone> Call-ID: USELLLAN@10.2.2.3 Version 7.2 Mediant 500 MSBR...
Page 700 Mediant 500 MSBR CSeq: 1 INVITE Contact: <sip:7000@10.2.2.3> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 ...
Page 701: Configuring Ip-To-Ip Inbound Manipulations
Routing Policy ("Default_SBCRoutingPolicy"), when only one Routing Policy is required, the device automatically assigns the default Routing Policy to the routing rule. If you are implementing LDAP-based routing (with or without Call Setup Rules) and/or Version 7.2 Mediant 500 MSBR...
Page 702 Mediant 500 MSBR Least Cost Routing (LCR), you need to configure these settings for the Routing Policy (regardless of the number of Routing Policies employed). For more information on Routing Policies, see Configuring SBC Routing Policy Rules on page 692.
Page 703 [2] REGISTER = Only REGISTER messages.  [3] SUBSCRIBE = Only SUBSCRIBE messages.  [4] INVITE and REGISTER = All SIP messages except SUBSCRIBE.  [5] INVITE and SUBSCRIBE = All SIP messages except REGISTER. Version 7.2 Mediant 500 MSBR...
Page 704 Mediant 500 MSBR Source IP Group Defines the IP Group from where the incoming INVITE is received. src-ip-group-name The default is Any (i.e., any IP Group). [IPInboundManipulatio n_SrcIpGroupName] Source Username Prefix Defines the prefix of the source SIP URI user name (usually in the From header).
Page 705: Configuring Ip-To-Ip Outbound Manipulations
Web interface. You can also configure it through ini file (IPOutboundManipulation) or CLI (configure voip > sbc manipulation ip-outbound-manipulation).  To configure Outbound Manipulation rules: Open the Outbound Manipulations table (Setup menu > Signaling & Media tab > Version 7.2 Mediant 500 MSBR...
Page 706 Mediant 500 MSBR SBC folder > Manipulation > Outbound Manipulations). Click New; the following dialog box appears: Figure 38-3: Outbound Manipulations Table- Add Dialog Box Configure an Outbound Manipulation rule according to the parameters described in the table below. Click Apply.
Page 707 Source Host Defines the source SIP URI host name - full name, typically in the From header. src-host The default value is the asterisk (*) symbol (i.e., any source host name). [IPOutboundManipulatio n_SrcHost] Version 7.2 Mediant 500 MSBR...
Page 708 Mediant 500 MSBR Source Tags Assigns a prefix tag to denote source URI user names corresponding to the tag configured in the associated Dial Plan. src-tags The valid value is a string of up to 20 characters. The tag is case [IPOutboundManipulatio insensitive.
Page 709 Destination URI, you can configure the parameter to a string of up 49 characters. If you set the 'Manipulated Item' parameter to Calling Name, you can configure the parameter to a string of up 36 characters. Version 7.2 Mediant 500 MSBR...
Page 710 Mediant 500 MSBR Privacy Restriction Mode Defines user privacy handling (i.e., restricting source user identity in outgoing SIP dialogs). privacy-restriction-mode  [0] Transparent = (Default) No intervention in SIP privacy. [IPOutboundManipulatio  [1] Don't change privacy = The user identity remains the same as in n_PrivacyRestrictionMod the incoming SIP dialog.
Page 711: Configuring Dial Plans
Dial Plan for a rule that matches the destination number. If matching dial plan rules are found, the tags configured for these rules are used in the routing and/or manipulation processes as source and/or destination tags. Version 7.2 Mediant 500 MSBR...
Page 712 Mediant 500 MSBR Note: When tags are used in the IP-to-IP Routing table to determine destination IP Groups (i.e., 'Destination Type' parameter configured to Destination Tag), the device searches the Dial Plan for a matching destination (called) prefix number only.
Page 713 "4"): Prefix 532[1-9] 532[2-4]  For incoming calls with prefix number "53124", the rule with tag C is chosen (longest suffix - C has three digits, B two digits and A one digit): Prefix Version 7.2 Mediant 500 MSBR...
Page 714 Mediant 500 MSBR 53([2-4]) 53([01-99]) 53([001-999])  For incoming calls with prefix number "53124", the rule with tag B is chosen (suffix is more specific for digit "4"): Prefix 53([2-4]) 53(4),B Dial Plans are configured using two tables with parent-child type relationship: ...
Page 715: Importing And Exporting Dial Plans
Web client. The CLI lets you import and export Dial Plans from and to a remote server. The following procedures describe how to export configured Dial Plans.  To export all configured dial plan rules:  Web interface (to a local folder): Open the Dial Plan table. Version 7.2 Mediant 500 MSBR...
Page 716 Mediant 500 MSBR From the 'Action' drop-down menu, choose Export; the following dialog box appears: Figure 39-4: Exporting Dial Plan Select the Save File option, and then click OK; the file is saved to the default folder on your PC for downloading files.
Page 717 Web interface (from a local folder): Open the Dial Plan table. Select the required Dial Plan, and then click the Dial Plan Rule link; the Dial Plan Rule table opens, displaying all the rules of the selected Dial Plan. Version 7.2 Mediant 500 MSBR...
Page 718: Creating Dial Plan Files
Mediant 500 MSBR From the 'Action' drop-down menu, choose Import; the following dialog box appears: Figure 39-6: Importing Dial Plan Rules for Specific Dial Plan Use the Browse button to select the Dial Plan file on your PC, and then click OK.
Page 719: Using Dial Plan Tags For Ip-To-Ip Routing
Figure 39-7: Dial Plan Example for Local and International Call Routing For the IP Group or SRD associated with the calls for which you want to use tag- based routing, assign the Dial Plan that you configured in Step 1. Version 7.2 Mediant 500 MSBR...
Page 720: Using Dial Plan Tags For Routing Destinations
Mediant 500 MSBR • IP Groups table: 'Dial Plan' parameter (IPGroup_SBCDialPlanName) - see Configuring IP Groups on page 333 • SRDs table: 'Dial Plan' parameter (SRD_SBCDialPlanName) - see Configuring SRDs on page 315 In the IP-to-IP Routing table (see Configuring SBC IP-to-IP Routing Rules on page 671), configure a routing rule with the required destination and whose matching characteristics include the tag(s) that you configured in your Dial Plan in Step 1.
Page 721 In the Dial Plan table, configure a Dial Plan with Dial Plan rules, where the 'Prefix' parameter is the destination (called) prefix number. In our example, we will configure a Dial Plan called "Dial Plan 1" with two Dial Plan rules: Parameter Index 0 Index 1 Version 7.2 Mediant 500 MSBR...
Page 722 Mediant 500 MSBR Name Bel-Neth Prefix Country=England;City=London Holland;City=Amsterdam;Country=Belgium The following displays the configuration in the Web interface of the Dial Plan rule for Index Figure 39-9: Dial Plan configuration Example In the IP Groups table, configure your IP Groups. Make sure that you assign the source IP Group with the Dial Plan that you configured in Step 1 and that you configure each destination IP Group with one of the required Dial Plan tags.
Page 723: Dial Plan Backward Compatibility
The example Dial Plan file below defines the prefix tags "LOCL"and "INTL" to represent different called number prefixes for local and long distance calls: [ PLAN1 ] 42520[3-5],0,LOCL 425207,0,LOCL 42529,0,LOCL 425200,0,INTL 425100,0,INTL ..Version 7.2 Mediant 500 MSBR...
Page 724: Using Dial Plan Tags For Outbound Manipulation
Mediant 500 MSBR Note: • Called and calling prefix tags can be used in the same routing rule. • When using prefix tags, you need to configure manipulation rules to remove the tags before the device sends the calls to their destinations.
Page 725: Using Dial Plan Tags For Call Setup Rules
(prefix) in a specified Dial Plan to obtain the corresponding tag. The Call Setup rule can then perform many different manipulations (based on Message Manipulation syntax), including modifying the name of the tag. The tags can be used only in the 'Condition', 'Action Subject' and 'Action Value' fields. Version 7.2 Mediant 500 MSBR...
Page 726: Using Dial Plan Tags For Message Manipulation
Mediant 500 MSBR 39.6 Using Dial Plan Tags for Message Manipulation You can use Dial Plan tags (srctags and dsttags) in Message Manipulation rules, configured in the Message Manipulations table (see Configuring SIP Message Manipulation on page 381). The tags can be used only in the 'Condition' and 'Action Value' fields.
Page 727: Configuring Malicious Signatures
(i.e., IP Group). To configure Message Policies, see Configuring SIP Message Policy Rules. The following procedure describes how to configure Malicious Signatures through the Web interface. You can also configure it through ini file (MaliciousSignatureDB) or CLI (configure voip > sbc malicious-signature-database). Version 7.2 Mediant 500 MSBR...
Page 728 Mediant 500 MSBR  To configure a Malicious Signature: Open the Malicious Signature table (Setup menu > Signaling & Media tab > SBC folder > Malicious Signature). Click New; the following dialog box appears: Figure 40-1: Malicious Signature Table - Add Dialog Box Configure a Malicious Signature according to the parameters described in the table below.
Page 729: Advanced Sbc Features
The device does not monitor emergency calls with regards to Quality of Experience (QoE).  To configure SBC emergency call preemption: In the Message Conditions table (see Configuring Message Condition Rules on page 387), configure a Message Condition rule to identify incoming emergency calls. See Version 7.2 Mediant 500 MSBR...
Page 730: Emergency Call Routing Using Ldap To Obtain Elin
Mediant 500 MSBR above for examples. Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings), and then scroll down to the Call Priority and Preemption group: Figure 41-2: Configuring Emergency SBC Call Preemption From the 'Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable call preemption.
Page 731: Enabling Interworking Of Sip And Sip-I Endpoints
SIP-I is SIP encapsulated with ISUP and the interworking is between SIP signaling and ISUP signaling. This allows you to deploy the device in a SIP environment where part of the call path involves the PSTN. Version 7.2 Mediant 500 MSBR...
Page 732 Mediant 500 MSBR The SIP-I sends calls, originating from the SS7 network, to the SIP network by adding ISUP messaging in the SIP INVITE message body. The device can receive such a message from the SIP-I and remove the ISUP information before forwarding the call to the SIP endpoint.
Page 733: Call Forking
Configuring SIP Message Manipulation on page 381). For a complete description of the ISUP manipulation syntax, refer to the SIP Message Manipulation Reference Guide. In addition, you can use AudioCodes proprietary SIP header X-AC-Action in Message Manipulation rules to support the following call actions (e.g., SIP-I SUS and RES messages) for the ISUP SPIROU variant: ...
Page 734: Configuring Sip Forking Initiated By Sip Proxy
Mediant 500 MSBR 41.4.2 Configuring SIP Forking Initiated by SIP Proxy The device can handle the receipt of multiple SIP 18x responses as a result of SIP forking initiated by a proxy server. This occurs when the device forwards an INVITE, received from a user agent (UA), to a proxy server and the proxy server then forks the INVITE request to multiple UAs.
Page 735: Enabling Auto-Provisioning Of Subscriber-Specific Information Of Broadworks Server For Survivability
To enable the BroadWorks survivability feature: Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder > SBC General Settings). From 'BroadWorks Survivability Feature' drop-down list (SBCExtensionsProvisioningMode), select Enable: Click Apply. Version 7.2 Mediant 500 MSBR...
Page 736: Configuring Broadsoft's Shared Phone Line Call Appearance For Survivability
Mediant 500 MSBR 41.5.2 Configuring BroadSoft's Shared Phone Line Call Appearance for Survivability The device can provide redundancy for BroadSoft's Shared Call Appearance feature. When the BroadSoft application server switch (AS) fails or does not respond, or when the network connection between the device and the BroadSoft AS is down, the device manages the Shared Call Appearance feature for the SIP clients.
Page 737: Configuring Call Survivability For Call Centers
(such as IVR), the device routes the incoming calls received from the customer (i.e., from the TDM gateway) to the call center agents. Version 7.2 Mediant 500 MSBR...
Page 738 Mediant 500 MSBR In normal operation, the device registers the agents in its users registration database. Calls received from the TDM gateway are forwarded by the device to the application server, which processes the calls and sends them to specific call center agents, through the device.
Page 739: Enabling Survivability Display On Aastra Ip Phones
LCD screens. If you enable the feature and the device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following XML body: Version 7.2 Mediant 500 MSBR...
Page 740: Alternative Routing On Detection Of Failed Sip Response
Mediant 500 MSBR Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument>  To enable survivability display on Aastra phones: Load an ini file to the device that includes the following parameter setting: SBCEnableSurvivabilityNotice = 1 41.6...
Page 741: Cloud Resilience Package
Part VII Cloud Resilience Package...
Page 743: Crp Overview
Topology hiding   Basic call routing between Test call agent registering users and device, or any other route to responding server  Short number dialog (short numbers are learned dynamically in the registration process) Version 7.2 Mediant 500 MSBR...
Page 744 Mediant 500 MSBR  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications)  Call waiting (if supported by IP phone) One of the main advantages of CRP is that it enables quick-and-easy configuration.
Page 745: Crp Configuration
Click Apply, and then reset the device with a save-to-flash for your settings to take effect. 43.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes: Version 7.2 Mediant 500 MSBR...
Page 746 Mediant 500 MSBR  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 747: Pre-Configured Ip Groups
The IP Groups can be edited, except for the fields listed above, which are read-only. • For accessing the IP Groups table and for a description of its parameters, see Configuring IP Groups on page 333. Version 7.2 Mediant 500 MSBR...
Page 748: Pre-Configured Ip-To-Ip Routing Rules
Mediant 500 MSBR 43.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 745.
Page 749: Emergency Mode
Route Row #1 [CRP IP Group #2 [CRP Route Row Users] Proxy] #1 [CRP IP Group #1 [CRP Alternative Users] Users] Route Ignore Inputs #1 [CRP IP Group #3 [CRP Alternative Users] Gateway] Route Ignore Inputs Version 7.2 Mediant 500 MSBR...
Page 750: Configuring Pstn Fallback
Mediant 500 MSBR #2 [CRP IP Group #1 [CRP Route Row Proxy] Users] #2 [CRP IP Group #3 [CRP Route Row Proxy] Gateway] #3 [CRP IP Group #2 [CRP Route Row Gateway] Proxy] #3 [CRP IP Group #1 [CRP Alternative...
Page 751: Data-Router Configuration
Part VIII Data-Router Configuration...
Page 755: Introduction
Web-based management for data-router functionality of the MSBR series products is not supported. Instead, CLI is used to configure this functionality. However, AudioCodes recommends using CLI scripting to configure all other functionality as well (i.e., VoIP and System) through the CLI.
Page 756 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 757: Maintenance
Part IX Maintenance...
Page 759: Basic Maintenance
No: The device resets without saving the current configuration to flash. All configuration done after the last configuration save will be discarded (lost) after reset. From the 'Graceful Option' drop-down list, select one of the following: Version 7.2 Mediant 500 MSBR...
Page 760: Remotely Resetting Device Using Sip Notify
Remotely Resetting Device using SIP NOTIFY The device can be remotely reset upon the receipt of a SIP NOTIFY that contains an Event header that is set to 'check-sync;reboot=true' (proprietary to AudioCodes), as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...
Page 761: Saving Configuration
Save button is displayed with a red border, as shown below: Figure 45-4: Saving Configuration to Flash To save configuration to flash through CLI, use the following command: # write Version 7.2 Mediant 500 MSBR...
Page 762 Mediant 500 MSBR Note: Saving configuration to flash may disrupt current traffic on the device. To avoid this, disable all new traffic before saving, by performing a graceful lock (see Locking and Unlocking the Device on page 760). User's Manual...
Page 763: Channel Maintenance
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 7.2 Mediant 500 MSBR...
Page 764: Locking And Unlocking Trunk Groups
Mediant 500 MSBR 46.4 Locking and Unlocking Trunk Groups You can lock a Trunk Group to take its trunks (and their channels) out of service. When you initiate a lock, the device rejects all new incoming calls for the Trunk Group and immediately terminates active calls (busy channels), eventually taking the entire Trunk Group out of service.
Page 765: Disconnecting Active Calls
You can configure an arbitrary name or a brief description for each telephony port displayed on the Home page. This description is displayed as a tooltip when you hover your mouse over the port. Note: Only alphanumerical characters can be used in the port description. Version 7.2 Mediant 500 MSBR...
Page 766 Mediant 500 MSBR  To add a port description: Open the Monitor home page (see Viewing Device Status on Monitor Page on page 840). Click the required port icon; a shortcut menu appears: Figure 46-2: Choosing Port Description From the shortcut menu, choose Port Description; the following dialog box appears: Figure 46-3: Configuring Analog Port Description Type a brief description for the port, and then click Submit.
Page 767: Software Upgrade
If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance. •...
Page 768 Mediant 500 MSBR Open the Software Upgrade wizard: • Toolbar: From the Actions drop-down menu, choose Software Upgrade. • Navigation tree: Setup menu > Administration tab > Maintenance folder > Software Upgrade. Figure 47-1: Starting Software Upgrade Wizard Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file:...
Page 769 Restore configuration to factory defaults: Clear the 'Use existing configuration' check box. • Retain the existing configuration (default): Select the 'Use existing configuration' check box. Figure 47-4: Load an INI File in the Software Upgrade Wizard Version 7.2 Mediant 500 MSBR...
Page 770 Mediant 500 MSBR Note: If you use the wizard to load an ini file, parameters excluded from the ini file are assigned default values (according to the .cmp file) and thereby, overwrite values previously configured for these parameters. Click Reset; a progress bar is displayed, indicating the progress of saving the files to flash and device reset.
Page 771: Auxiliary Files
Saving Auxiliary files to flash memory may disrupt traffic on the device. To avoid this, disable all traffic on the device by performing a graceful lock as described in Locking and Unlocking the Device on page 760. Version 7.2 Mediant 500 MSBR...
Page 772: Loading Auxiliary Files Through Web Interface
Mediant 500 MSBR 48.1.1 Loading Auxiliary Files through Web Interface The following procedure describes how to load Auxiliary files through the Web interface. Note: • When loading an ini file through the Auxiliary Files page (as described in this section), only parameter settings specified in the ini file are applied to the device;...
Page 773: Loading Auxiliary Files Through Cli
(see Distinctive Ringing on page 776). You can use one of the supplied Auxiliary files (.dat file format) or create your own file. To create your own file, it's recommended to modify the supplied usa_tone.ini file (in any Version 7.2 Mediant 500 MSBR...
Page 774 Mediant 500 MSBR standard text editor) to suit your specific requirements and then convert the modified ini file into binary dat file format, using AudioCodes DConvert utility. For more information, refer to the DConvert Utility User's Guide. Note: The CPT file can only be loaded in .dat file format.
Page 775 'Signal On Time' parameter of the cadence tone. Otherwise, the continuous tone is detected instead of the cadence tone. • The tones frequency must differ by at least 40 Hz between defined tones. Version 7.2 Mediant 500 MSBR...
Page 776: Distinctive Ringing
Mediant 500 MSBR Below shows an example of a configured dial tone to 440 Hz only: [NUMBER OF CALL PROGRESS TONES] Number of Call Progress Tones=1 #Dial Tone [CALL PROGRESS TONE #0] Tone Type=1 Tone Form =1 (continuous) Low Freq [Hz]=440...
Page 777 First Ring Off Time [10msec]=400 #GR-506-CORE Ringing Pattern 2 [Ringing Pattern #2] Ring Type=2 Freq [Hz]=20 First Ring On Time [10msec]=80 First Ring Off Time [10msec]=40 Second Ring On Time [10msec]=80 Second Ring Off Time [10msec]=400 Version 7.2 Mediant 500 MSBR...
Page 778: Prerecorded Tones File
Audition), and then combined into a single and loadable PRT file (.dat) using the latest version of AudioCodes DConvert utility. Once created, you need to install the PRT file on the device (flash memory), using the Web interface (see Loading Auxiliary Files on page 771) or CLI.
Page 779: 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 771.
Page 780: Dialing Plans For Digit Collection
• To use the Dial Plan file, you must also use a special CAS .dat file that supports this feature. For more information, contact your AudioCodes sales representative. • For E1 CAS MFC-R2 variants, which don't support terminating digit for the called party number, usually I-15, the Dial Plan file and the DigitMapping parameter are ignored.
Page 781 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 771.
Page 782: Dial Plan Prefix Tags For Ip-To-Tel Routing
Mediant 500 MSBR Open the DTMF & Dialing page (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > DTMF & Dialing). In the 'Dial Plan Index' field, enter the Dial Plans by index number that you want to use.
Page 783 In the 'IP-to-Tel Tagging Source Dial Plan Index' field, enter the Dial Plan index that you want to use for prefix tags for calling number prefixes. Figure 48-3: Specifying Dial Plan for Prefix Tags Version 7.2 Mediant 500 MSBR...
Page 784: Obtaining Ip Destination From Dial Plan File
Mediant 500 MSBR Click Apply. Configure the device to perform the routing process before manipulation: Open the Routing Settings page (see previous step). From the 'IP-to-Tel Routing Mode' drop-down list, select Route calls before manipulation, and then click Apply. Configure IP-to-Tel routing rules where the prefix tags are used as matching...
Page 785: Modifying Isdn-To-Ip Calling Party Number
The second number must always be set to "0".  <new calling number>: String of up to 12 characters containing the mapped number that is used as the URI user part in the From and Contact headers of the outgoing INVITE. Version 7.2 Mediant 500 MSBR...
Page 786: Viewing Information Of Installed Dial Plan File
Mediant 500 MSBR Below shows an example of such a configuration in the Dial Plan file: [ PLAN1 ] ; specific received number changed to 04343434181. 0567811181,0,04343434181 ; number range that changes to 04343434181. 056788118[2-4],0,04343434181 If we take the first Dial Plan rule in the example (i.e., "0567811181,0,04343434181"), the...
Page 787: User Information File
"IP world" and the PBX extension uses this mapping to emulate the behavior of an IP phone. This feature is especially useful in scenarios where unique or non-consecutive number translation per PBX is needed. Version 7.2 Mediant 500 MSBR...
Page 788: Configuring Gw User Info Table Through Web Interface
Mediant 500 MSBR This number manipulation feature supports the following call directions: • IP-to-Tel Calls: Maps the called "global" number (in the Request-URI user part) to the PBX extension number. For example, if the device receives an IP call destined for "global" number 638002, it changes this called number to the PBX extension number 402, and then sends the call to the PBX extension on the Tel side.
Page 789 Note: Each row must be configured with a unique index. PBX Extension Defines the PBX extension number. [GWUserInfoTable_PBXE The valid value is a string of up to 10 characters. xtension] Note: The parameter is mandatory. Version 7.2 Mediant 500 MSBR...
Page 790: Configuring Gw User Info Table Through Cli
Mediant 500 MSBR Global Phone Number Defines the "global" phone number for the IP side. [GWUserInfoTable_Globa The valid value is a string of up to 20 characters. lPhoneNumber] Note: The parameter is mandatory. Display Name Defines the Caller ID of the PBX extension.
Page 791: Configuring Gw User Info Table In Loadable Text File
To modify the GW User Info table using a User Info file, you need to load to the device a new User Info file containing your modifications. Below is an example of a configured User Info file: [ GW ] FORMAT PBXExtensionNum,GlobalPhoneNum,DisplayName,UserName,Password 401,638001,Mike,miked,1234 402,638002,Lee,leem,4321 403,638003,Sue,suer,8790 404,638004,John,johnd,7694 405,638005,Pam,pame,3928 406,638006,Steve,steveg,1119 Version 7.2 Mediant 500 MSBR...
Page 792: User Information File For Sbc User Database
Mediant 500 MSBR 407,638007,Fred,frede,8142 408,638008,Maggie,maggiea,9807 48.7.3 User Information File for SBC User Database You can use the SBC User Info table for the following:  Registering each user to an external registrar server.  Authenticating (for any SIP request and as a client) each user if challenged by an external server.
Page 793 AOR in the database. [SBCUserInfoTable_IPGr oupName] To configure IP Groups, see Configuring IP Groups on page 333. Status (Read-only field) Displays the status of the user - "Registered" or "Not Registered". [SBCUserInfoTable_Statu Version 7.2 Mediant 500 MSBR...
Page 794: Configuring Sbc User Info Table Through Cli
Mediant 500 MSBR 48.7.3.2 Configuring SBC User Info Table through CLI The SBC 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 sbc-user-info <index, e.g.,...
Page 795: Viewing The Installed User Info File Name
English is spoken. However, if you wish to replace the default file with a different AMD Sensitivity file containing customized detection algorithms, please contact your AudioCodes sales representative for more information.
Page 796 The XML-to-binary format conversion can be done using AudioCodes DConvert utility. For more information on using this utility, refer to DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.
Page 797: License Key
License Key The License Key determines the device's supported features and call session capacities, as ordered from your AudioCodes sales representative. You can upgrade or change your device's supported features and capacity, by purchasing and installing a new License Key that match your requirements.
Page 798: Installing A New License Key
 Serial Number: Device's serial number.  Board Type: AudioCodes internal identification number of the type of your device.  Remote License Server / Remote License Server IP: For more information, see Upgrading SBC Capacity Licenses by License Pool Manager Server on page 802.
Page 799 The License Key page uses color-coded icons to indicate the changes between the previous License Key and the newly loaded License Key (for more information, see Installing License Key through Web Interface on page 798). Version 7.2 Mediant 500 MSBR...
Page 800: Installing A License Key File
Mediant 500 MSBR Click Apply New License Key; the following message box appears: Figure 49-4: Apply New License Key Message Click Reset; the device begins to save the file to flash memory with a reset and the following progress message box appears:...
Page 801 Figure 49-7: Apply New License Key Message Click Reset; the device begins to save the file to flash memory with a reset and the following progress message box appears: Figure 49-8: Reset in Progress for License Key Version 7.2 Mediant 500 MSBR...
Page 802: Installing License Key Through Cli
Manager Server The device can receive SBC capacity (session) licenses from a centralized pool of SBC resources managed by the License Pool Manager Server running on AudioCodes EMS. The License Pool Manager Server can dynamically allocate and de-allocate SBC licenses from the pool to devices in the network to meet capacity demands of each device, whenever required.
Page 803 SBC licenses allocated by the License Pool Manager Server. The device sends the following SNMP alarms relating to the allocation/de-allocation of SBC licenses by the License Pool Manager Server:  acLicensePoolInfraAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.106)  acLicensePoolApplicationAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.107)  acLicensePoolOverAllocationAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.125) Version 7.2 Mediant 500 MSBR...
Page 804: Backing Up The License Key
Viewing the Device's Product Key The Product Key identifies a specific purchase of your device installation for the purpose of subsequent communication with AudioCodes (e.g., for support and software upgrades). The Product Key is your chassis' serial number--"S/N(Product Key)"--which also appears on the product label affixed to the chassis.
Page 805: Configuration File
The following procedure describes how to load a configuration file from a folder on your PC to the device. You can load any of the following configuration file types:  ini file  CLI Script file Version 7.2 Mediant 500 MSBR...
Page 806 Mediant 500 MSBR  CLI Startup Script file Warning: • When loading an ini file as described in this section, parameters not included in the ini file are restored to default settings. If you want to keep the device's current...
Page 807: Automatic Provisioning
To enable the device as a DHCP client: Open the Network Settings page (Setup menu > IP Network tab > Advanced folder > Network Settings). From the 'Enable DHCP" drop-down list, select Enable. Figure 51-1: Enabling DHCP Client Functionality Click Apply. Version 7.2 Mediant 500 MSBR...
Page 808: Http-Based Provisioning
Mediant 500 MSBR To activate the DHCP process, reset the device. 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 809: Ftp-Based Provisioning
Provisioning on page 808 is that the protocol in the URL is "ftp" (instead of "http"). 51.1.4 Provisioning using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections.
Page 810: Files Provisioned By Automatic Update
Mediant 500 MSBR Note: • For a description of all the Automatic Update parameters, see Automatic Update Parameters on page or refer to the CLI Reference Guide. • For additional security, use HTTPS or FTPS. The device supports HTTPS (RFC 2818) and FTPS using the AUTH TLS method <draft-murray-auth-ftp-ssl-16>.
Page 811: Mac Address Placeholder In Configuration File Name
The device automatically replaces the string with its hardware MAC address, resulting in a file name request that contains device's address, example, startup_00908F033512.txt. Therefore, you can configure all the devices with the same URL and file name. Version 7.2 Mediant 500 MSBR...
Page 812: File Template For Automatic Provisioning
Mediant 500 MSBR Note: If you write the MAC address placeholder string in lower case (i.e., "<mac>"), the device adds the MAC address in lower case to the file name (e.g., config_<mac>.ini results in config_00908f053736e); if in upper case (i.e., "<MAC>"), the device adds the MAC address in upper case to the file name (e.g.,...
Page 813: Triggers For Automatic Update
Zero Configuration (see Zero Configuration on page 822).  Upon device startup (reset or power up). To disable this trigger, run the following CLI command: (config-system)# automatic-update (automatic-update)# run-on-reboot off Version 7.2 Mediant 500 MSBR...
Page 814: Access Authentication With Http Server
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 815: Querying Provisioning Server For Updated Files
INIFileVersion or CLI command, configuration-version The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld-<NAME>;<VER>(<MAC>), the device sends the following User-Agent header: User-Agent: MyWorld-Mediant;7.00.200.001(00908F1DD0D3)
Page 816 Mediant 500 MSBR • File Download upon each Automatic Update process: This is applicable to software (.cmp) and configuration files. In the sent HTTP Get request, the device uses the HTTP If-Modified-Since header to determine whether to download these files. The header contains the date and time (timestamp) of when the device last downloaded the file from the specific URL.
Page 817: File Download Sequence
When multiple files requiring a reset are downloaded, the device resets only after it has downloaded and installed all the files. However, you can explicitly instruct the device to immediately reset for the following files:  CLI Script file: Use the reload if-needed CLI command Version 7.2 Mediant 500 MSBR...
Page 818: Cyclic Redundancy Check On Downloaded Configuration Files
Mediant 500 MSBR Note: • If you have configured one-time software file (.cmp) download (configured by the ini file parameter CmpFileURL or CLI command configure system > automatic- update > firmware), the device will only apply the file if one-time software updates are enabled.
Page 819: Automatic Update For Single Device
'http://www.company.com/call_progress.dat' Enable Cyclical Redundancy Check (CRC) on downloaded ini file: ♦ ini File: AUPDCheckIfIniChanged = 1 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# crc-check regular Power down and then power up the device. Version 7.2 Mediant 500 MSBR...
Page 820: Automatic Update From Remote Servers
Mediant 500 MSBR 51.2.10.2 Automatic Update from Remote Servers This example describes how to configure the Automatic Update feature where files are stored and downloaded from different file server types. The example scenario includes the following:  FTPS server at ftpserver.corp.com for storing the License Key file. The login credentials to the server are username "root"...
Page 821: Automatic Update For Mass Deployment
(automatic-update)# cli-script https://company.com/files/cli_script_<MAC>.txt (automatic-update)# voice-configuration http://www.company.com/config_<MAC>.ini Copy the master configuration file that you created in Step 1 as well as the CPT and .cmp files to the HTTP-based provisioning server. Configure each device with the following: Version 7.2 Mediant 500 MSBR...
Page 822: Zero Configuration
If your device was originally purchased and shipped without the Zero Configuration feature and you now wish to order this feature, contact your AudioCodes sales representative. The procedure typically requires you to return your device as a return merchandise authorization (RMA).
Page 823: Zero Configuration Process
When the device is powered up, it acquires an IP address from a DHCP server for its WAN Ethernet interface. The device establishes a secure HTTPS connection with AudioCodes Redirect server, and then requests the configuration file. A special factory-set certificate is used by the device to authenticate itself and verify authenticity of the Redirect server.
Page 824: Activating Zero Configuration
To set up and activate Zero Configuration: Create the CLI configuration file and publish it on an HTTP/HTTPS provisioning server. Connect to AudioCodes Redirect server and then configure the following: • MAC address of the device(s) that you want to service.
Page 825: Working With The Redirect Server
51.3.4.1 Redirect Server GUI This section describes how to use the Redirect server GUI. 51.3.4.1.1 Logging in to Redirect Server The procedure below describes how to log in to the GUI of the Redirect server. Version 7.2 Mediant 500 MSBR...
Page 826 Mediant 500 MSBR  To log in to the Redirect server GUI: Go to http://redirect.audiocodes.com; the Redirect server login window appears: Figure 51-4: Logging into the Redirect Server In the 'Username' and 'Password' fields, enter your login credentials provided by AudioCodes support team.
Page 827 Figure 51-6: Group Tab - Redirect Server GUI The table below describes the action icons: Table 51-4: Group Action Icons Icon Name Magnifying Displays detailed information of the group glass Modifies the group's details Edit Group Details Trash Deletes the group Version 7.2 Mediant 500 MSBR...
Page 828 Mediant 500 MSBR 51.3.4.1.4 Managing Locations The Locations tab displays all redirect locations of where the configuration file is stored, relevant to the currently logged-in user: Figure 51-7: Locations Tab - Redirect Server GUI You must configure the location as an HTTP or HTTPS URL. You can also group devices with different locations.
Page 829 The new MAC addresses are also displayed for the specific location under the Devices tab (see Managing Devices on page 828). Colons as well as upper and lower case have no meaning. MAC addresses must be clearly separated from one another. Version 7.2 Mediant 500 MSBR...
Page 830: Xml-Rpc Programmatic Api
Mediant 500 MSBR 51.3.4.2 XML-RPC Programmatic API Please contact AudioCodes support for detailed XML-RPC API documentation. 51.4 Automatic Provisioning using USB Flash Drive The device can be automatically provisioned using an external USB hard drive or flash drive (disk on key) connected to its USB port. In order to do this, you need to create a CLI script file named "ac_autorun.txt"...
Page 831 MSBR(cli-terminal)# set ssh on MSBR(cli-terminal)# activate defaults exit help history list pwd quit MSBR(cli-terminal)# set wan-ssh-allow on Note: Setting the parameter requires a reset. MSBR(cli-terminal)*# exit MSBR(config-system)*# exit MSBR*# write Writing configuration...done MSBR*# Version 7.2 Mediant 500 MSBR...
Page 832 Mediant 500 MSBR  To automatically provision the device using a USB flash drive: Using a basic text-editing program such as Notepad, create a new text file. Type the desired CLI commands in the file. Save the file as "ac_autorun.txt".
Page 833: 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 7.2 Mediant 500 MSBR...
Page 834 Mediant 500 MSBR This page is intetnionaly left blank. User's Manual Document #: LTRT-10375...
Page 835: Restoring Factory Defaults
This may be important, for example, to maintain connectivity with the device (through the OAMP interface) after factory defaults have been applied.  To restore factory defaults through Web interface: Open the Configuration File page: Version 7.2 Mediant 500 MSBR...
Page 836: Restoring Defaults Using Hardware Reset Button
Mediant 500 MSBR • Toolbar: From the Actions drop-down menu, choose Configuration File. • Navigation tree: Setup menu > Administration tab > Maintenance folder > Configuration File. Figure 53-1: Restoring Factory Defaults through Web To keep your current IP network settings, select the Preserve Network Configuration check box.
Page 837: Status, Performance Monitoring And Reporting
Part X Status, Performance Monitoring and Reporting...
Page 839: System Status
Figure 54-1: Viewing Device Information (Example) Table 54-1: Device Information Description Parameter Description General Settings VoIP MAC Address MAC address of the VoIP application. LAN MAC Address MAC address of the LAN. WAN MAC Address MAC address of the WAN. Version 7.2 Mediant 500 MSBR...
Page 840: Viewing Device Status On Monitor Page
Mediant 500 MSBR Serial Number Serial number of the CPU. This serial number also appears on the product label that is affixed to the chassis, as "CPU S/N". Product Key Product Key, which identifies the specific device purchase. The Product Key also appears on the product label that is affixed to the chassis, as "S/N(Product Key)".
Page 841 Graphical display of the device with color-coded status icons, as shown in the figure below and described in the subsequent table: Note: The displayed number and type of telephony interfaces, LAN interfaces and WAN interfaces depends on the ordered hardware configuration. Version 7.2 Mediant 500 MSBR...
Page 842 Mediant 500 MSBR Table 54-2: Description of Graphical Display of Device Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green = No alarms  Red = Critical alarm  Orange = Major alarm ...
Page 843: Viewing Voice Port Information
Basic: Displays information such as call duration, line voltage, hook status (off or on), and polarity reversal.  RTP/RTCP: Displays RTP/RTCP-related information such as packet loss and network jitter.  Voice Settings: Displays voice-related configuration such as silence suppression. Version 7.2 Mediant 500 MSBR...
Page 844 Mediant 500 MSBR  To view information on an analog port: Open the Monitor home page (see Viewing Device Status on Monitor Page on page 840). On the graphical display of the device, click a port; a shortcut menu appears.
Page 845 DTMF Selected Method for Tx/Rx DTMF Transport method used for the call. For configuring the transport method, see Configuring DTMF Transport Types on page 181. Channel Identifier: Channel identifier number. Basic Version 7.2 Mediant 500 MSBR...
Page 846 Mediant 500 MSBR Status Status of port:  "Inactive": No call  "Active": Active call Call ID See above. Endpoint ID ID of endpoint:  "Not Available" Call Duration Call duration (in seconds) from when call was established. Call Type Type of call: ...
Page 847 Displays the volume gain (in dB). Voice Volume Displays the voice volume gain (in dB). DTMF Transport Type Displays the DTMF transport type. Enabled Detectors Displays enabled detectors (e.g., AMD). Fax Transport Type Displays the fax transport type. Version 7.2 Mediant 500 MSBR...
Page 848 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 849: Viewing Carrier-Grade Alarms
Critical (red)  Major (orange)  Minor (yellow) Source Component of the device from which the alarm was raised. Brief description of the alarm. Description Date Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised. Version 7.2 Mediant 500 MSBR...
Page 850: Viewing History Alarms
Mediant 500 MSBR 55.2 Viewing History Alarms You can view all SNMP alarms, in the Web interface's Alarms History table, that have been raised (active alarms) as well as cleared (resolved). One of the benefits of this is that you can view alarms that may have been raised and then cleared on a continuous basis.
Page 851 55. Viewing Carrier-Grade Alarms Date Date (DD/MM/YYYY) and time (HH:MM:SS) the alarm was raised.  To delete all the alarms in the table: Click the Delete History Table button; a confirmation message box appears. Click OK to confirm. Version 7.2 Mediant 500 MSBR...
Page 852 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 853: Viewing Management User Activity Logs
Username of the user account that performed the activity. Interface Protocol used for connecting to the management interface (e.g., Telnet, SSH, Web, or HTTP). Client IP address of the client PC from where the user accessed the management interface. Version 7.2 Mediant 500 MSBR...
Page 854 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 855: Viewing Performance Monitoring
Figure 57-1: Viewing Trunk Utilization From the 'Trunk' drop-down list, select the trunk for which you want to view active channels. For more graph functionality, see the following table: Table 57-1: Additional Graph Functionality for Trunk Utilization Button Description Version 7.2 Mediant 500 MSBR...
Page 856: Viewing Call Success And Failure Ratio
Mediant 500 MSBR Add button Displays additional trunks in the graph. Up to five trunks can be displayed simultaneously. To view another trunk, click the button and then from the new 'Trunk' drop-down list, select the required trunk. The graph displays each trunk in a different color, according to the legend shown in the top-left corner of the graph.
Page 857 Other: all SIP messages If there is no data for the charts, the chart appears gray and "No Data" is displayed to the right of the chart.  To refresh the charts:  Click Refresh. Version 7.2 Mediant 500 MSBR...
Page 858: Viewing Average Call Duration
Mediant 500 MSBR  To reset the counters:  Click Reset Counters. 57.3 Viewing Average Call Duration You can view the number of currently active calls and the average call duration (ACD) in the Web interface's Average Call Duration page. You can filter display by a specific SRD or IP Group.
Page 859: Configuring Performance Profiles
PM_gwSBCSRDACD: ACD per SRD If the configured ACD minor or major thresholds are crossed, the device raises the SNMP alarm, acACDThresholdAlarm (OID 1.3.6.1.4.1.5003.9.10.1.21.2.0.112). To view ACD in the Web interface, see Viewing Average Call Duration on page 858. Version 7.2 Mediant 500 MSBR...
Page 860 Mediant 500 MSBR At any given time during a call, a voice metric can be in one of the following color-coded quality states (as displayed by SEM):  Green: Indicates good call quality  Yellow: Indicates fair call quality ...
Page 861 Click New; the following dialog box appears: Figure 57-5: Performance Profile Table - Dialog Box Configure the rule according to the parameters described in the table below. Click Apply. Table 57-3: Performance Profile Table Parameter Descriptions Parameter Description Version 7.2 Mediant 500 MSBR...
Page 862 Mediant 500 MSBR Index Defines an index number for the new table row. [PerformanceProfile_Ind Note: Each row must be configured with a unique index. Match Entity Defines a configuration entity type to which you want to apply the rule. ...
Page 863: Configuring Packetsmart Agent For Network Monitoring
VoIP networks. By providing real-time monitoring of live traffic, PacketSmart can identify any network issues as they arise that may impact VoIP quality, enabling service providers to address issues prior to customer complaints. Version 7.2 Mediant 500 MSBR...
Page 864 The PacketSmart feature is a license-based feature and is available only if it is included in the License Key installed on the device. For ordering the feature, please contact your AudioCodes sales representative. • Before configuring the PacketSmart agent, configure the following: √...
Page 865: Viewing Voip Status
The number of established calls is represented by the 'Number of Established Calls' counter. The number of failed calls is represented by the failed-call counters. Only one of the established / failed call counters is incremented every time. Version 7.2 Mediant 500 MSBR...
Page 866 Mediant 500 MSBR Number of Established Indicates the number of established calls. It is incremented as a result of one of the following release reasons if the duration of the call is Calls greater than zero:  GWAPP_REASON_NOT_RELEVANT (0) ...
Page 867: Viewing Sbc Registered Users
10 seconds from the proxy/registrar server.  CLI: • SBC users: # show voip register db sbc list • SBC contacts of a specified AOR: # show voip register db sbc user <Address Of Record> Version 7.2 Mediant 500 MSBR...
Page 868: Viewing Proxy Set Status
Mediant 500 MSBR 58.3 Viewing Proxy Set Status You can view the status of Proxy Sets that are used in your call routing topology. Proxy Sets that are not associated with any routing rule are not displayed. To configure proxy Sets, see Configuring Proxy Sets on page 348.
Page 869: Viewing Registration Status
Trunk Group Settings table (see Configuring Trunk Group Settings on page 487) or using the TrunkGroupSettings ini file parameter.  To view registration status:  Open the Registration Status table (Monitor menu > Monitor tab > VoIP Status folder > Registration Status). Version 7.2 Mediant 500 MSBR...
Page 870: Viewing Ip Connectivity
Mediant 500 MSBR Table 58-4: Registration Status Table Description Parameter Description Registered Per Gateway Registration status of the device as one entity:  "YES"  "NO" Note: The parameter is applicable only to the Gateway application. Ports Registration Status Displays the registration status per analog (FXS or FXO) port: ...
Page 871 The parameter is applicable only if the parameter 'Alt Routing Tel to IP Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).  The parameter is reset if two minutes elapse without a call to the destination. Version 7.2 Mediant 500 MSBR...
Page 872: Viewing Gateway Cdr History
Mediant 500 MSBR Quality Info Displays QoS information: delay and packet loss, calculated according to previous calls. Note:  The parameter is applicable only if the parameter 'Alt Routing Tel to IP Mode' is set to 'QoS' or 'Both' (AltRoutingTel2IPMode = 2 or 3).
Page 873: Viewing Sbc Cdr History
 To view SBC CDR history:  Web: Open the SBC CDR History table (Monitor menu > Monitor tab > VoIP Status folder > SBC CDR History). Figure 58-6: SBC CDR History Table  CLI: Version 7.2 Mediant 500 MSBR...
Page 874 Mediant 500 MSBR • All CDR history: # show voip calls history sbc • CDR history for a specific SIP session ID: # show voip calls history sbc <session ID> Table 58-7: SBC CDR History Table Field Description Call End Time Displays the time at which the call ended.
Page 875: Viewing Pstn Status
Table 59-1: Description of Color-Coded Icons for Trunk Status Trunk Icon Color Label Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Version 7.2 Mediant 500 MSBR...
Page 876: Viewing Nfas Groups And D-Channel Status
Mediant 500 MSBR The status of the channels is depicted by color-coded icons, as described in the table below: Table 59-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 877 To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Monitor menu > Monitor tab > PSTN Status folder > NFAS Group & D-Channel Status). Figure 59-1: NFAS Group & D-Channel Status Page Version 7.2 Mediant 500 MSBR...
Page 878 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 879: Viewing Data Ip Network Status
From the 'WAN Interface Name' drop-down list, select the interface that you want to view. The figure below displays an example of network status for the WAN copper interface: Figure 60-1: Viewing Network Interface Status Version 7.2 Mediant 500 MSBR...
Page 880 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 881: Reporting Information To External Party
The type of RTCP XR report event (VQReportEvent) supported by the device is VQSessionReport (SessionReport). The device can include local and remote metrics in the RTCP XR. Local metrics are generated by the device while remote metrics are provided by Version 7.2 Mediant 500 MSBR...
Page 882 Mediant 500 MSBR the remote endpoint. The following table lists the supported voice metrics (parameters) published in the RTCP XR. Table 61-1: RTCP XR Published VoIP Metrics Metric Parameter Description CallID Call ID - call ID from the SIP dialog...
Page 883 MOS-LQ - estimated mean opinion score for listening voice quality on a scale from 1 to 5, in which 5 represents excellent and 1 represents unacceptable MOSLQEstAl MOS-LQ Est. Algorithm - name (string) of the algorithm used to estimate MOSLQ Version 7.2 Mediant 500 MSBR...
Page 884 Mediant 500 MSBR MOSCQ MOS-CQ - estimated mean opinion score for conversation voice quality on a scale from 1 to 5, in which 5 represents excellent and 1 represents unacceptable MOSCQEstAl MOS-CQ Est. Algorithm - name (string) of the algorithm used to...
Page 885 RTCP XR reports. • (Gateway Application Only) 'Gateway RTCP XR Report Mode' (RTCPXRReportMode): Enables the sending of RTCP XR reports and configures at what stage of the call they are sent. Version 7.2 Mediant 500 MSBR...
Page 886: Generating Call Detail Records
Mediant 500 MSBR • (SBC Application Only) 'SBC RTCP XR Report Mode' (SBCRtcpXrReportMode): Enables the sending of RTCP XR reports of QoE metrics at the end of each call session (i.e., after a SIP BYE). Figure 61-2: Configuring RTCP XR Collection Server Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
Page 887: Cdr Fields For Sbc Signaling
CDR Report Type Format (SBCReportType) SBCReportT Report type: String  "CALL_START": CDR sent upon an INVITE message.  "CALL_CONNEC T": CDR sent upon a 200 OK response.  "CALL_END": CDR sent upon a BYE message. Version 7.2 Mediant 500 MSBR...
Page 888 Mediant 500 MSBR  "DIALOG_START"  "DIALOG_END" EPTyp Endpoint type: "SBC" String SIPMethod SIP message type String (up to 10 characters) SIPCallId Unique ID of call String (up to 50 characters) SessionId Unique Session ID String (up to 10 characters)
Page 889 0 (i.e., not connected):  NO_ANSWER:  "GWAPP_NO RMAL_CALL_ CLEAR"  "GWAPP_NO _USER_RES PONDING"  "GWAPP_NO _ANSWER_F ROM_USER_ ALERTED"  BUSY:  "GWAPP_US ER_BUSY"  NO_RESOURCE  "GWAPP_RE SOUUCE_UN AVAILABLE_ UNSPECIFIE D"  "RELEASE_B ECAUSE_NO Version 7.2 Mediant 500 MSBR...
Page 890 Mediant 500 MSBR _CONFEREN CE_RESOUR CES_LEFT"  "RESOURCE _BECAUSE_ NO_TRANSC ODING_RES OURCES_LE FT"  "RELEASE_B ECAUSE_GW _LOCKED"  NO_MATCH:  "RELEASE_B ECAUSE_UN MATCHED_C APABILITIES"  FORWARDED:  "RELEASE_B ECAUSE_FO RWARD"  GENERAL_FAILE D: Any other reason Calls with duration: ...
Page 891 SIP response code, the description is taken from an internal SIP response mapping mechanism. For example, if the device receives a SIP response "422", it sends in the CDR "422 Session Interval Too Small Version 7.2 Mediant 500 MSBR...
Page 892: Cdr Fields For Sbc Media
Mediant 500 MSBR method" as the description. Caller Name of caller String (up to 36 characters) Callee Name of called party String (up to 36 characters) Below shows an example of an SBC signaling CDR sent at the end of a call (call was...
Page 893 Remote RTP IP address RemoteRtpPort 0 to 0xFFFF Remote RTP port InPackets 0 to 0xFFFFFFFF Number of packets received by the device (local) OutPackets 0 to 0xFFFFFFFF Number of packets sent by the device (local) Version 7.2 Mediant 500 MSBR...
Page 894: Cdr Fields For Sbc Local Storage
Mediant 500 MSBR LocalPackLoss 0 to 0xFFFFFFFF Number of packet loss of the entire stream (local) RemotePackLoss 0 to 0xFFFFFF (-1 if Remote packet loss information is unavailable) RTPdelay 0 to 10000 ms (-1 if information Average RTP delay of the entire stream...
Page 895 RedirectURINumBeforeMap Signaling IP DiffServ TxSigIPDiffServ IP Group Name IPGroup SRD Name SrdId SIP Interface Name SIPInterfaceId Proxy Set Name ProxySetId IP Profile Name IpProfileId Media Realm Name MediaRealmId Direct Media DirectMedia SIP Termination Reason SIPTrmReason Version 7.2 Mediant 500 MSBR...
Page 896: Cdr Fields For Gateway Application
Mediant 500 MSBR SIP Termination Description SIPTermDesc Caller Display ID Caller Callee Display ID Callee 61.2.1.4 CDR Fields for Gateway Application The CDRs generated by the device for Gateway calls include media and signaling CDR fields. The default CDR fields are listed in the table below.
Page 897 Physical trunk number BChan Selected B-channel ConId SIP conference ID Trunk Group ID EPTyp Endpoint type:    EANDM  ISDN    IPMEDIA  NETANN  STREAMING  TRANSPARENT  MSCML  VXML Version 7.2 Mediant 500 MSBR...
Page 898 Mediant 500 MSBR Orig Call originator:  LCL (Tel side)  RMT (IP side) SourceIp Source IP address DestIp Destination IP address Source phone number type Source phone number plan SrcPhoneNum Source phone number SrcNumBeforeM Source number before manipulation Destination phone number type...
Page 899 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) "CALL_END" (See explanation above.) Version 7.2 Mediant 500 MSBR...
Page 900 Mediant 500 MSBR TrmReasonCate Termination reason category: "CALL_END" gory  Calls with duration 0 (i.e., not connected):  NO_ANSWER - GWAPP_NORMAL_CALL_CLEAR, GWAPP_NO_USER_RESPONDING GWAPP_NO_ANSWER_FROM_US ER_ALERTED  BUSY - GWAPP_USER_BUSY  NO_RESOURCES - GWAPP_RESOUUCE_UNAVAILAB LE_UNSPECIFIED, RELEASE_BECAUSE_NO_CONFE RENCE_RESOURCES_LEFT, RESOURCE_BECAUSE_NO_TRAN SCODING_RESOURCES_LEFT, RELEASE_BECAUSE_GW_LOCKE  NO_MATCH -...
Page 901 RTP latching mechanism for NAT traversal. LatchedRtpPort Remote RTP port of the incoming RTP "CALL_END" stream that the device "latched" on to as a result of the RTP latching mechanism for NAT traversal. Version 7.2 Mediant 500 MSBR...
Page 902 Mediant 500 MSBR LatchedT38Ip Latching of a new T.38 stream - new IP "CALL_END" address LatchedT38Port Latching of a new T.38 stream - new port "CALL_END" Local MOS "CALL_END" MosR Remote MOS "CALL_END" 61.2.1.4.1 Release Reasons in CDR for Gateway Application...
Page 903 REUSE" • "RELEASE_BECAUSE_PRECEDENCE_CALL_BLOCKED"  "GWAPP_QUALITY_OF_SERVICE_UNAVAILABLE"  "GWAPP_REQUESTED_FAC_NOT_SUBSCRIBED"  "GWAPP_BC_NOT_AUTHORIZED"  "GWAPP_BC_NOT_PRESENTLY_AVAILABLE"  "GWAPP_SERVICE_NOT_AVAILABLE"  "GWAPP_CUG_OUT_CALLS_BARRED"  "GWAPP_CUG_INC_CALLS_BARRED"  "GWAPP_ACCES_INFO_SUBS_CLASS_INCONS"  "GWAPP_BC_NOT_IMPLEMENTED"  "GWAPP_CHANNEL_TYPE_NOT_IMPLEMENTED"  "GWAPP_REQUESTED_FAC_NOT_IMPLEMENTED"  "GWAPP_ONLY_RESTRICTED_INFO_BEARER"  "GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED"  "GWAPP_INVALID_CALL_REF"  "GWAPP_IDENTIFIED_CHANNEL_NOT_EXIST"  "GWAPP_SUSPENDED_CALL_BUT_CALL_ID_NOT_EXIST" Version 7.2 Mediant 500 MSBR...
Page 904: Cdr Fields For Gateway Local Storage
Mediant 500 MSBR  "GWAPP_CALL_ID_IN_USE"  "GWAPP_NO_CALL_SUSPENDED"  "GWAPP_CALL_HAVING_CALL_ID_CLEARED"  "GWAPP_INCOMPATIBLE_DESTINATION"  "GWAPP_INVALID_TRANSIT_NETWORK_SELECTION"  "GWAPP_INVALID_MESSAGE_UNSPECIFIED"  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING"  "GWAPP_MESSAGE_TYPE_NON_EXISTENT"  "GWAPP_MESSAGE_STATE_INCONSISTENCY"  "GWAPP_NON_EXISTENT_IE"  "GWAPP_INVALID_IE_CONTENT"  "GWAPP_MESSAGE_NOT_COMPATIBLE"  "GWAPP_RECOVERY_ON_TIMER_EXPIRY"  "GWAPP_PROTOCOL_ERROR_UNSPECIFIED"  "GWAPP_INTERWORKING_UNSPECIFIED"  "GWAPP_UKNOWN_ERROR" ...
Page 905 Local RTP port LocalRtpPort 0-999999 Amount 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) Version 7.2 Mediant 500 MSBR...
Page 906 Mediant 500 MSBR 0,001-1000 (in steps of 10) Mult (See explanation above.) Termination reason category TrmReasonCategory SRD name SrdId SIP Interface name SIPInterfaceId Proxy Set name ProxySetId IP Profile name IpProfileId Media Realm name MediaRealmId SIP signaling transport type SigTransportType...
Page 907: Customizing Cdrs For Gateway Calls
You can also configure it through ini file (GWCDRFormat) or CLI (configure troubleshoot > cdr > cdr-format gw-cdr-format).  To customize Gateway CDRs: Open the Gateway CDR Format table (Troubleshoot menu > Troubleshoot tab > Call Detail Record folder > Gateway CDR Format). Version 7.2 Mediant 500 MSBR...
Page 908 Mediant 500 MSBR Click New; the following dialog box appears: Figure 61-6: Gateway CDR Format Table - Add Dialog Box Configure CDR format rules according to the parameters described in the table below. Click Apply. An example of CDR customization rules configured in the table is shown below: Figure 61-7: Examples of Configured Gateway CDR Customization Rules ...
Page 909 Factor; [626] Remote R Factor; [627] Local MOS CQ; [628] Remote MOS CQ; [629] AMD Decision; [630] AMD Decision Probability; [631] Latched RTP IP; [632] Latched RTP Port; [633] Latched T38 IP; [634] Latched T38 Port. Version 7.2 Mediant 500 MSBR...
Page 910 Mediant 500 MSBR Title Defines a new name for the CDR field (for Syslog) or for the RADIUS Attribute prefix name (for RADIUS accounting) that you selected in the title 'Column Type' parameter. [GWCDRFormat_Title] The valid value is a string of up to 31 characters.
Page 911: Customizing Cdrs For Sbc Calls
You can also configure it through ini file (SBCCDRFormat) or CLI (configure troubleshoot > cdr > cdr-format sbc-cdr-format).  To customize SBC-related CDRs: Open the SBC CDR Format table (Troubleshoot menu > Troubleshoot tab > Call Detail Record folder > SBC CDR Format). Version 7.2 Mediant 500 MSBR...
Page 912 Mediant 500 MSBR Click New; the following dialog box appears: Figure 61-8: SBC CDR Format Table - Add Dialog Box Configure the CDR according to the parameters described in the table below. Click Apply. Examples of configured CDR customization rules are shown below:...
Page 913 Source Username Before Manipulation; [811] Destination Username Before Manipulation; [812] Source Host; [813] Destination Host; [814] Source Host Before Manipulation; [815] Destination Host Before Manipulation; [816] Source Dial Plan Tags; [817] Destination Dial Plan Tags; [818] Remote SIP User Agent. Version 7.2 Mediant 500 MSBR...
Page 914 Mediant 500 MSBR Title Defines a new name for the CDR field (for Syslog or local storage) or for the RADIUS Attribute prefix name (for RADIUS accounting) that you title selected in the 'Column Type' parameter. [SBCCDRFormat_Title] The valid value is a string of up to 31 characters. You can also configure the name to be enclosed by apostrophes (single or double).
Page 915: Configuring Cdr Reporting
SUBSCRIBE, OPTIONS, and REGISTER), use the EnableNonCallCdr parameter. 61.2.5 Storing CDRs on the Device The CDRs of Gateway and SBC calls generated by the device can also be stored locally on the device (RAM). Version 7.2 Mediant 500 MSBR...
Page 916 Mediant 500 MSBR Note: When the device is reset or powered off, locally stored CDRs are deleted. You can specify the calls (configuration entities) for which you wish to create CDRs and store locally. This is done using Logging Filter rules in the Logging Filters table. For example, you can configure a rule to create CDRs for traffic belonging only to IP Group 2 and store the CDRs locally.
Page 917: Configuring Radius Accounting
The device can send accounting data of SIP calls as call detail records (CDR) to a RADIUS Accounting server. CDR-based accounting messages can be sent upon call release, call connection and release, or call setup and release. This section lists the CDR attributes for RADIUS accounting. Version 7.2 Mediant 500 MSBR...
Page 918 Mediant 500 MSBR The following figure shows the interface between the device and the RADIUS server, based on the RADIUS Accounting protocol. For each CDR that the device sends to the RADIUS server, it sends an Accounting-Request Stop with all the CDR attributes. When the RADIUS server successfully receives all the CDR attributes, it responds with an Accounting-Response Stop ACK message to the device.
Page 919 From the 'Enable RADIUS Access Control' drop-down list (EnableRADIUS), select Enable. • From the 'RADIUS Accounting Type' drop-down list (RADIUSAccountingType), select the stage of the call that RADIUS accounting messages are sent to the RADIUS accounting server. Version 7.2 Mediant 500 MSBR...
Page 920 Mediant 500 MSBR • From the 'AAA Indications' drop-down list (AAAIndications), select whether you want Authentication, Authorization and Accounting (AAA) indications. For a detailed description of the parameters, see RADIUS Parameters on page 1233. Figure 61-16: Configuring RADIUS Accounting Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
Page 921 Terminator of the call: String call- Stop Acc terminator=y  "yes": Call terminated by the Tel side (Gateway) or outgoing leg (SBC)  "no": Call terminated by the IP side (Gateway) or incoming leg (SBC) Version 7.2 Mediant 500 MSBR...
Page 922 Mediant 500 MSBR terminator Terminator of the call: String terminator= Stop Acc originate  "answer": Call originated from the IP side (Gateway) or incoming leg (SBC)  "originate": Call originated from the Tel side (Gateway) or outgoing leg (SBC) called-station-id (Standard) Called (destination)
Page 923 (4923 23) h323-remote-address = 212.179.22.214 (4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899 3fd61009 0e2f3cc5 (4923 30) h323-disconnect-cause = 22 (0x16) (4923 27) h323-call-type = VOIP (4923 26) h323-call-origin = Originate (4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5 Version 7.2 Mediant 500 MSBR...
Page 924: Querying Device Channel Resources Using Sip Options
Mediant 500 MSBR 61.4 Querying Device Channel Resources using SIP OPTIONS The device reports its maximum and available channel resources in SIP 200 OK responses upon receipt of SIP OPTIONS messages. The device sends this information in the SIP X- Resources header with the following parameters: ...
Page 925: Obtaining Status And Performance Using A Usb Flash Drive
Obtaining Status and Performance using a USB Flash Drive You can use a USB flash drive to obtain status and performance information of the device. For more information, see Automatic Provisioning using USB Flash Drive on page 830. Version 7.2 Mediant 500 MSBR...
Page 926 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 927: Diagnostics
Part XI Diagnostics...
Page 929: Syslog And Debug Recording
Syslog messages, or CDRs. Disabling a rule is useful, for example, if you no longer require the rule, but may need it in the future. Thus, instead of deleting the rule entirely, you can simply disable it. Version 7.2 Mediant 500 MSBR...
Page 930 Mediant 500 MSBR Note: • If you want to configure a Log Filter rule that logs Syslog messages to a Syslog server (i.e., not to a Debug Recording server), you must enable Syslog functionality, using the 'Enable Syslog' (EnableSyslog) parameter (see Enabling Syslog on page 940).
Page 931  "1/2" (without apostrophes), means module 1, port 2  "1/[2-4]" (without apostrophes), means module 1, ports 2 through 4  The exclamation (!) wildcard character can be used for excluding a Version 7.2 Mediant 500 MSBR...
Page 932 Mediant 500 MSBR specific configuration entity from the filter. For example, to include all IP Groups in the filter except IP Group ID 2, configure the 'Filter Type' parameter to IP Group and the 'Value' parameter to "!2" (without apostrophes). Note that for SBC calls, a Logging Filter rule applies to the entire session, which is both legs (i.e., not per leg).
Page 933: Filtering Ip Network Traces
Source and destination IP address ip.addr IP address - up to two IP addresses can be entered ip.proto IP protocol type (PDU) entered as an enumeration value (e.g., 1 is ICMP, 6 is TCP, 17 is UDP) Version 7.2 Mediant 500 MSBR...
Page 934: Configuring Syslog
Mediant 500 MSBR udp, tcp, icmp, sip, ldap, http, https Single expressions for protocol type udp.port, tcp.port Transport layer udp.srcport, tcp.srcport Transport layer for source port udp.dstport, tcp.dstport Transport layer for destination port and, &&, ==, <, > Between expressions Below are examples of configured expressions for the 'Value' parameter: ...
Page 935 Syslog messages, by setting the 'CDR Syslog Sequence Number' parameter to Disable (see Configuring Syslog on page 940). Log Number Ignore this number; it has been replaced by the Message (lgr)(number) Sequence Number (described previously). Version 7.2 Mediant 500 MSBR...
Page 936 Mediant 500 MSBR Session ID (SID) Unique SIP call session and device identifier. The device identifier facilitates debugging by clearly identifying the specific device that sent the log message, especially useful in deployments consisting of multiple devices. In addition, the...
Page 937: Event Representation In Syslog Messages
Lost Fax Frames In High Speed Mode Lost Modem Frames In High Speed Mode Misalignment Error Modem Relay Is Not Supported DSP JB Overrun Packet Header Error RTP Packet Loss Counts the number of BFI Frames Received From The Host Version 7.2 Mediant 500 MSBR...
Page 938: Unique Device Identification In Syslog Messages
Cannot assign requested address  63.2.1.3 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.
Page 939: Syslog Fields For Answering Machine Detection (Amd)
If additional information exists in the alarm, then these are also added: Additional Info1:/ Additional Info2:/ Additional Info3 The Messages’ Severity is as follows: Table 63-6: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Critical RecoverableMsg Major RecoverableMsg Minor RecoverableMsg Warning Notice Version 7.2 Mediant 500 MSBR...
Page 940: Enabling Syslog
Mediant 500 MSBR 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: 63.2.2 Enabling Syslog The following procedure describes how to enable Syslog.
Page 941: Configuring Syslog Debug Level
(e.g., Web and CLI) by management users, in Syslog messages. The Syslog message indicates these logs with the string "Activity Log". Each logged user activity includes the following information:  Username (e.g., "Admin") of the user that performed the action Version 7.2 Mediant 500 MSBR...
Page 942 Mediant 500 MSBR  IP address of the client PC from where the Web user accessed the management interface  Protocol used for the session (e.g., SSH or HTTP) The following example shows a Web-user activity log (indicating a login action) with the above-mentioned information: 14:07:46.300 : 10.15.7.95 : Local 0...
Page 943: Viewing Syslog Messages
When debug recording is enabled and Syslog messages are also included in the debug recording, to view Syslog messages using Wireshark, you must install AudioCodes' Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and displayed using the "acsyslog" filter (instead of the regular "syslog"...
Page 944: Viewing Historical Syslog Messages
You can select the Syslog messages displayed on the 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. 63.2.7 Viewing Historical Syslog Messages You can view a historical list of the most recent (up to 200 Kbytes) Syslog messages that were generated by the device.
Page 945: Configuring Debug Recording
Logging Filters table (see Configuring Log Filter Rules on page 929). Note: 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 833. Version 7.2 Mediant 500 MSBR...
Page 946: Collecting Debug Recording Messages
Click Apply. 63.3.2 Collecting Debug Recording Messages To collect debug recording packets, use the open source packet capturing program, Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Note: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...
Page 947: Debug Capturing Voip And Data-Router Traffic
User's Manual 63. Syslog and Debug Recording The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: 63.3.3 Debug Capturing VoIP and Data-Router Traffic You can capture VoIP and data-router network traffic by sending traces to the CLI or to a file that is later sent to a FTP or TFTP server.
Page 948: Configuring Termination Of Debug Capture Upon Event
Mediant 500 MSBR  Captures packets continuously in a cyclical buffer (packets always captured until stop command): # debug capture VoIP physical cyclic buffer  Retrieves latest capture (PCAP file) saved on a specified server: # debug capture VoIP physical get_last_capture <TFTP/FTP server IP address>...
Page 949: Self-Testing
Startup Test (automatic): This hardware test has minor impact in real-time. While this test is executed, the regular operation of the device is disabled. If an error is detected, an error message is sent to the Syslog. Version 7.2 Mediant 500 MSBR...
Page 950 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 951: Creating Core Dump And Debug Files Upon Device Crash
The files may assist you in identifying the cause of the crash. The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. You can then provide the files to AudioCodes support team for troubleshooting. ...
Page 952 Mediant 500 MSBR You can also delete the core dump file through CLI, as described in the following procedure:  To delete the core dump file:  Navigate to the root CLI directory (enable mode), and then enter the following...
Page 953: Debugging Web Services
Open the Web Service Settings page (Setup menu > IP Network tab > Web Services folder > Web Service Settings). In the 'Debug Level' field (RestDebugMode), enter the debug level (or disable debugging by configuring it to 0): Figure 66-1: Configuring Debug for Web Services Click Apply. Version 7.2 Mediant 500 MSBR...
Page 954 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 955: Re-Initializing Device With "Purified" Configuration
When this command is run, the device 1) creates a CLI script file of the current configuration, 2) restores to factory defaults, 3) undergoes a reset, 4) applies (loads) the script file, and then 5) resets again (if required) for configuration settings to take effect. Version 7.2 Mediant 500 MSBR...
Page 956 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 957: Analog Line Testing
You can also view the above information through the Web interface (see Viewing Port Information on page 843). Note: Analog line testing is traffic affecting and therefore, do the test only for monitoring and when there are no active calls in progress. Version 7.2 Mediant 500 MSBR...
Page 958 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 959: Testing Sip Signaling Calls
By default, you can configure up to five test calls. However, this number can be increased by installing the relevant License Key. For more information, contact your AudioCodes sales representative. The following procedure describes how to configure test call rules through the Web interface.
Page 960 Mediant 500 MSBR Click New; the following dialog box appears: Figure 69-1: Test Call Rules Table - Add Dialog Box Configure a test call according to the parameters described in the table below. Click Apply, and then save your settings to flash memory.
Page 961 Transport Type  [-1] = Not configured (default) dst-transport  [0] UDP [Test_Call_DestTran  [1] TCP sportType]  [2] TLS Note: The parameter is applicable only if the 'Route By' parameter is set to Dest Address. Version 7.2 Mediant 500 MSBR...
Page 962 Mediant 500 MSBR QoE Profile Assigns a QoE Profile to the test call. qoe-profile By default, no value is defined. [Test_Call_QOEProfi To configure QoE Profiles, see Configuring Quality of Experience Profiles on page 293. Bandwidth Profile Assigns a Bandwidth Profile to the test call.
Page 963: Starting And Stopping Test Calls
In the Test Call Rules table, select the required test call entry. From the Action drop-down list, choose the required command: • Dial: Starts the test call (applicable only if the test call party is the caller). Version 7.2 Mediant 500 MSBR...
Page 964: Viewing Test Call Status
Mediant 500 MSBR • Drop Call: Stops the test call. • Restart: Ends all established calls and then starts the test call session again. 69.3 Viewing Test Call Status You can view the status of test call rules in the 'Test Status' field of the Test Call Rules table.
Page 965 Average CPS Elapsed Time Duration of the test call since it was started (or restarted). Test Status Status (brief description) as displayed in the 'Test Status' field (see Viewing Test Call Status on page 964). Version 7.2 Mediant 500 MSBR...
Page 966: Configuring Dtmf Tones For Test Calls
Mediant 500 MSBR Detailed Status Displays a detailed description of the test call status:  "Idle": Test call is currently not active.  "Scheduled - Established Calls: <number of established calls>, ASR: <ASR>%": Test call is planned to run (according to 'Schedule Interval'...
Page 967: Configuring Basic Test Calls
In the 'Test Call ID' field, enter a prefix for the simulated endpoint: Figure 69-5: Configuring Basic Test Calls For a full description of the parameter, see SIP Test Call Parameters on page 1011. Click Apply. Version 7.2 Mediant 500 MSBR...
Page 968: Test Call Configuration Examples
Mediant 500 MSBR Note: • The device can play DTMF tones to the remote endpoint. For more information, see Configuring DTMF Tones for Test Calls on page 966. • Test calls are done on all SIP Interfaces. 69.7 Test Call Configuration Examples Below are a few examples of test call configurations.
Page 969 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 970 Mediant 500 MSBR  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 971: Data-Router Debugging
# debug ethernet loopback interface <interface name / type> For example: # debug ethernet loopback interface GigabitEthernet 0/0 The no debug command disables the loopback test. Note: All communication through the loopback WAN interface stops when this test is enabled. Version 7.2 Mediant 500 MSBR...
Page 972: Performing A Traceroute
Mediant 500 MSBR 70.2 Performing a Traceroute You can use traceroute as a diagnostic tool for displaying the route (path) and measuring transit delays of packets across an IP network. The traceroute sends three requests to each hop on the way to the destination. Traceroute is done using the following CLI command: # traceroute ipv6 <X:X::X:X>...
Page 973: Pinging A Remote Host Or Ip Address
# ping ipv6 <IPv6 address or host name> source data [vrf | source-address interface| interface] [size <max. IP packet size>] [repeat <1-300>] For a complete description of the ping command, refer to the CLI Reference Guide. Note: IPv6 ping is currently only supported on Ethernet and Fiber interfaces. Version 7.2 Mediant 500 MSBR...
Page 974 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 975: Troubleshooting Using A Usb Flash Drive
72. Troubleshooting using a USB Flash Drive Troubleshooting using a USB Flash Drive You can use a USB flash drive for quick-and-easy troubleshooting of the device. For more information, see Automatic Provisioning using USB Flash Drive on page 830. Version 7.2 Mediant 500 MSBR...
Page 976 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 977: Appendix
Part XII Appendix...
Page 979: Dialing Plan Notation For Routing And Manipulation
An example for entering a combined prefix and suffix dial plan - assume you want to match a rule whose destination phone prefix is 4 to 8, and suffix is 234, 235, or 236. The entered value would be the following: [4-8](23[4,5,6]). Version 7.2 Mediant 500 MSBR...
Page 980 Mediant 500 MSBR [n-m] or (n-m) Represents a range of numbers. Examples:  To depict prefix numbers from 5551200 to 5551300:  [5551200-5551300]#  To depict prefix numbers from 123100 to 123200:  123[100-200]#  To depict prefix and suffix numbers together: ...
Page 981 "x" wildcards (e.g., xx165xxxxx#); the prefix to add to the number would include the HEX values (e.g., +49 \287303\29 165-). Below is a list of common ASCII characters and their corresponding HEX values: ASCII Character HEX Value Version 7.2 Mediant 500 MSBR...
Page 982 Mediant 500 MSBR This page is intentionally left blank. User's Manual Document #: LTRT-10375...
Page 983: Configuration Parameters Reference
By default, the device's data-router firewall blocks all ("any") incoming traffic on the WAN. Thus, to enable WAN access, you must also enable the data-router firewall: # configure data (config-data)# interface gigabitethernet 0/0 (conf-if-GE 0/0)# firewall enable Version 7.2 Mediant 500 MSBR...
Page 984 Mediant 500 MSBR Allow WAN access to Enables WAN access to the management interface through SNMP. SNMP  [0] Disable (default) wan-snmp-allow  [1] Enable [AllowWanSNMP] Note:  For the parameter to take effect, a device reset is required. ...
Page 985: Web Parameters
Web interface. These users can only log in to the Web interface if their status is changed (to New or Valid) by a Security Administrator or Master user. The valid value is 0 to 10000, where 0 means inactive. The default is Version 7.2 Mediant 500 MSBR...
Page 986 Mediant 500 MSBR Note: The parameter is applicable only when using the Local Users table. Session Timeout Defines the duration (in minutes) of inactivity of a logged-in user in the Web interface, after which the user is automatically logged off the Web [WebSessionTimeout] session.
Page 987 The configured text message must be enclosed in double quotation marks (i.e., "...").  If the parameter is not configured, no Welcome message is displayed. [UseProductName] Enables the option to customize the name of the device (product) that appears in the management interfaces. Version 7.2 Mediant 500 MSBR...
Page 988 Mediant 500 MSBR  [0] = Disabled (default).  [1] = Enables the display of a user-defined name, which is configured by the UserProductName parameter. For more information, see Customizing the Product Name on page 69. [UserProductName] Defines a name for the device instead of the default name.
Page 989: Telnet Parameters
[CLIPrivPass] Defines the password to access the Enable configuration mode in the CLI. The valid value is a string of up to 50 characters. The default is "Admin". Note: The password is case-sensitive. Version 7.2 Mediant 500 MSBR...
Page 990: Ini File Parameters
Mediant 500 MSBR Default Terminal Window Defines the number (height) of output lines displayed in the CLI Height terminal window. This applies to all new CLI sessions and is preserved after device resets. configure system > cli-settings > The valid value range is -1 (default) and 0-65535: default-window- ...
Page 991 > snmp trap > Enables the device to send NAT keep-alive traps to the port of auto-send-keep-alive the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication [SendKeepAliveTrap] with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
Page 992 Mediant 500 MSBR [SNMPTrapEnterpriseOid] Defines the SNMP MIB OID for the Trap Enterprise. The default is 1.3.6.1.4.1.5003.9.10.1.21. Note:  For the parameter to take effect, a device reset is required.  The device automatically adds the device’s unique product identifier number at the end of your OID.
Page 993 [SNMPReadOnlyCommunityStri  ng_x] Upper- and lower-case letters (a to z, and A to Z)  Numbers (0 to 9)  Hyphen (-)  Underline (_) For example, "Public-comm_string1". The default is "public". Version 7.2 Mediant 500 MSBR...
Page 994: Parameters
Mediant 500 MSBR Read/Write Community Strings Defines a read-write SNMP community string. Up to five read- write community strings can be configured. configure system > snmp settings > rw-community-string The valid value is a string of up to 30 characters that can include...
Page 995 Defines the connection request password used by the ACS to connect to the device. connection-request- password The valid value is a string of up to 256 characters. By default, no password is defined. [TR069ConnectionReque stPassword] Version 7.2 Mediant 500 MSBR...
Page 996: Serial Parameters
Mediant 500 MSBR Default Inform Interval Defines the inform interval (in seconds) at which the device periodically communicates with the ACS. Each time the device communicates with inform-interval the ACS, the ACS sends a response indicating whether or not the ACS [TR069PeriodicInformInte has an action to execute on the device.
Page 997: Auxiliary And Configuration File Name Parameters
The table below lists the ini file parameters associated with the Auxiliary files. For more information on Auxiliary files, see Loading Auxiliary Files on page 771. Table 74-8: Auxiliary and Configuration File Parameters Parameter Description General Parameters Version 7.2 Mediant 500 MSBR...
Page 998 0 is Trunk 1. Dial Plan File Defines the name of the Dial Plan file. This file should be created using AudioCodes DConvert utility (refer to DConvert Utility User's [DialPlanFileName] Guide). For the ini file, the name must be enclosed by single apostrophes, for example, 'dial_plan.dat'.
Page 999: Automatic Update Parameters
The device automatically populates these tag variables with actual values in the sent header. By default, the device sends the following in the User-Agent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<VER>;<MAC>;<CONF>) For example, if you set AupdHttpUserAgent = MyWorld- <NAME>;<VER>(<MAC>), the device sends the following User-Agent...
Page 1000 Mediant 500 MSBR Mediant;7.00.200.001(00908F1DD0D3) Note:  The variable tags are case-sensitive.  If you configure the parameter with the <CONF> variable tag, you must reset the device with a save-to-flash for your settings to take effect.  The tags can be defined in any order.
Page 1001 The maximum length of the URL address is 255 characters. voice-configuration Defines the name of the ini file and the URL address (IP address or FQDN) of the server on which the file is located. [IniFileURL] For example: http://192.168.0.1/filename http://192.8.77.13/config_<MAC>.ini https://<username>:<password>@<IP address>/<file name> Version 7.2 1001 Mediant 500 MSBR...
Page 1002 Mediant 500 MSBR Note:  For the parameter to take effect, a device reset is required.  When using HTTP or HTTPS, the date and time of the ini file are validated. Only more recently dated ini files are loaded.
Page 1003: Networking Parameters
[SingleNetworkMode]  [0] = Disable  [1] = (Default) Enable Note: For the parameter to take effect, a device reset is required. Version 7.2 1003 Mediant 500 MSBR...
Page 1004: Quality Of Service Parameters
Mediant 500 MSBR 74.2.3 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below. Table 74-12: QoS Parameters Parameter Description Layer-2 Class Of Service (CoS) Parameters (VLAN Tag Priority Field) DiffServ Table The table configures DiffServ-to-VLAN Priority mapping. For each packet sent to the LAN, the VLAN Priority of the packet is set according configure network >...
Page 1005: Nat Parameters
Internet. configure voip > sip- definition general-settings Note: > nat-ip-addr  For the parameter to take effect, a device reset is required. [StaticNatIP]  The parameter is applicable only to the Gateway application. Version 7.2 1005 Mediant 500 MSBR...
Page 1006: Dns Parameters
SendKeepAliveTrap parameter is set to 1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.
Page 1007: Dhcp Parameters
When set to 0, the DHCP lease renewal is disabled. Otherwise, the renewal time is divided by this factor. Some DHCP-enabled routers perform better when set to 4. Note: For the parameter to take effect, a device reset is required. Version 7.2 1007 Mediant 500 MSBR...
Page 1008: Ntp And Daylight Saving Time Parameters
Mediant 500 MSBR 74.2.7 NTP and Daylight Saving Time Parameters The Network Time Protocol (NTP) and daylight saving time parameters are described in the table below. Table 74-16: NTP and Daylight Saving Time Parameters Parameter Description NTP Parameters CLI path: configure system > ntp >...
Page 1009: Debugging And Diagnostics Parameters
When enabled, the data-router access list rules, configured [EnableSecSyslog] using the access-list CLI command, which are set to "log", send Syslog messages whenever traffic matching the access list is encountered.  [0] = (Default) Disabled  [1] = Enabled Version 7.2 1009 Mediant 500 MSBR...
Page 1010 Mediant 500 MSBR [EnableDiagnostics] Determines the method for verifying correct functioning of the different hardware components on the device. On completion of the check and if the test fails, the device sends information on the test results of each hardware component to the Syslog server.
Page 1011: Sip Test Call Parameters
Note: The parameter is applicable only to BRI interfaces. 74.3.2 SIP Test Call Parameters The SIP Signaling Test Call parameters are described in the table below. Table 74-18: SIP Test Call Parameters Parameter Description Version 7.2 1011 Mediant 500 MSBR...
Page 1012: Syslog, Cdr And Debug Parameters
Mediant 500 MSBR Test Call DTMF String Defines the DTMF tone that is played for answered test calls (incoming and outgoing). configure troubleshoot > test-call settings > The DTMF string can be up to 15 strings. The default is "3212333". If testcall-dtmf-string no string is defined (empty), DTMF is not played.
Page 1013  [4] Start & End & Update Media = Sends a CDR at the start of the media, upon an update in the media (if occurs), and at the end of the media. Note: Version 7.2 1013 Mediant 500 MSBR...
Page 1014 Mediant 500 MSBR  The parameter is applicable only to the SBC application.  To enable CDR generation as well as enable signaling-related CDRs, use the CDRReportLevel parameter. Local Storage Max File Defines the size (in kilobytes) of each stored CDR file. Once the file...
Page 1015 [22] = local use 6 (local6)  [23] = local use 7 (local7) CDR Syslog Sequence Enables or disables the inclusion of the sequence number (S=) in CDR Number Syslog messages.  configure system > cdr > [0] Disable Version 7.2 1015 Mediant 500 MSBR...

AudioCodes Mediant 500 MSBR User Manual

1 Introduction

Getting Started with Initial Connectivity

2 Introduction

3 Accessing the Device's Management Interfaces

4 Configuring Router's LAN and WAN

5 Enabling Remote Management from WAN

Management Tools

6 Introduction

7 Web-Based Management

8 CLI-Based Management

9 SNMP-Based Management

10 Based Management

11 INI File-Based Management

12 REST-Based Management

General System Settings

13 Configuring SSL/TLS Certificates

14 Date and Time

General Voip Configuration

15 Network

16 Security

17 Media

18 Services

19 Quality of Experience

20 Control Network

21 SIP Definitions

22 SIP Message Manipulation

23 Coders and Profiles

Gateway Application

Quick Links

Related Manuals for AudioCodes Mediant 500 MSBR

Summary of Contents for AudioCodes Mediant 500 MSBR