Download Print this page

AudioCodes Mediant 1000 User Manual

AudioCodes Mediant 1000 User Manual

Enterprise session border controller (e-sbc) and media gateway

Hide thumbs Also See for Mediant 1000:

User manual (844 pages)

,

Hardware installation manual (84 pages)

,

Installation manual (76 pages)

Table Of Contents

Table of Contents

Advertisement

Quick Links

See also: Troubleshooting Manual , Configuration Manual

User's Manual

AudioCodes Family of Media Gateways & Session Border Controllers (SBC)

Mediant™ 1000B

Gateway & Enterprise SBC

Version 7.2

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the Mediant 1000 and is the answer not in the manual?

Questions and answers

Summary of Contents for AudioCodes Mediant 1000

Page 1 User's Manual AudioCodes Family of Media Gateways & Session Border Controllers (SBC) Mediant™ 1000B Gateway & Enterprise SBC Version 7.2...
Page 3: Table Of Contents
User's Manual Contents Table of Contents Introduction ....................... 25 Product Overview ....................25 Typographical Conventions ..................26 Getting Familiar with Configuration Concepts and Terminology ......26 1.3.1 SBC Application ....................... 26 1.3.2 Gateway Application ....................30 Getting Started with Initial Connectivity ..............33 Introduction .......................
Page 4 Mediant 1000B Gateway & E-SBC CLI-Based Management ..................75 Getting Familiar with CLI ..................75 7.1.1 Understanding Configuration Modes ............... 75 7.1.2 Using CLI Shortcuts ....................76 7.1.3 Common CLI Commands ..................77 7.1.4 Configuring Tables through CLI ................78 7.1.5 Understanding CLI Error Messages ................
Page 5 User's Manual Contents 10.8.2 TLS for Remote Device Management ..............116 10.9 Configuring TLS Server Certificate Expiry Check ..........117 11 Date and Time ....................119 11.1 Configuring Automatic Date and Time using SNTP ..........119 11.2 Configuring Date and Time Manually ..............120 11.3 Configuring the Time Zone ...................
Page 6 Mediant 1000B Gateway & E-SBC 13.3 Intrusion Detection System .................. 167 13.3.1 Enabling IDS ......................168 13.3.2 Configuring IDS Policies ..................169 13.3.3 Assigning IDS Policies ...................173 13.3.4 Viewing IDS Alarms ....................175 14 Media ........................ 177 14.1 Configuring Voice Settings ................... 177 14.1.1 Configuring Voice Gain (Volume) Control .............177 14.1.2 Silence Suppression (Compression) ..............177 14.1.3 Configuring Echo Cancellation ................178...
Page 7 15.7.2.2 Adding ELINs to the Location Information Server ......... 283 15.7.2.3 Passing Location Information to the PSTN Emergency Provider ..284 15.7.3 AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN .....285 15.7.3.1 Detecting and Handling E9-1-1 Calls ............ 286 15.7.3.2 Pre-empting Existing Calls for E9-1-1 Calls ..........
Page 8 15.7.3.3 PSAP Callback to Skype for Business Clients for Dropped E9-1-1 Calls 15.7.3.4 Selecting ELIN for Multiple Calls within Same ERL ......289 15.7.3.5 Location Based Emergency Routing ............. 290 15.7.4 Configuring AudioCodes ELIN Device ..............290 15.7.4.1 Enabling the E9-1-1 Feature ..............290 15.7.4.2 Configuring the E9-1-1 Callback Timeout ..........291 15.7.4.3 Configuring the SIP Release Cause Code for Failed E9-1-1 Calls ..
Page 9 User's Manual Contents 19.4 Configuring IP Profiles ..................393 19.5 Configuring Tel Profile ..................428 Gateway Application .....................441 20 Introduction ..................... 443 20.1 Call Processing Summary ..................443 21 Digital PSTN ..................... 447 21.1 Configuring Trunk Settings ................... 447 21.2 TDM and Timing ....................449 21.2.1 TDM Bus Clock Settings ..................449 21.2.1.1 Recovering Clock from PSTN Line Interface ........
Page 10 Mediant 1000B Gateway & E-SBC 24 Manipulation ....................503 24.1 Configuring Redirect Reasons ................503 24.2 Configuring Source/Destination Number Manipulation Rules ......503 24.3 Manipulating Number Prefix ................. 509 24.4 SIP Calling Name Manipulations ................510 24.5 Configuring Redirect Number IP to Tel ..............513 24.6 Manipulating Redirected and Diverted Numbers for Call Diversion .....
Page 11 User's Manual Contents 26.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines .........................557 26.11.3 Pre-empting Existing Calls for E911 IP-to-Tel Calls ..........560 26.12 Multilevel Precedence and Preemption ..............561 26.12.1 MLPP Preemption Events in SIP Reason Header ..........563 26.12.2 Precedence Ring Tone ..................564 26.13 Denial of Collect Calls ..................
Page 12 Mediant 1000B Gateway & E-SBC 28 SBC Overview ....................605 28.1 Feature List ......................605 28.2 B2BUA and Stateful Proxy Operating Modes ............606 28.3 Call Processing of SIP Dialog Requests .............. 609 28.4 User Registration ....................611 28.4.1 Initial Registration Request Processing ..............611 28.4.2 Classification and Routing of Registered Users ............612 28.4.3 General Registration Request Processing ............613 28.4.4 Registration Refreshes ..................613...
Page 13 User's Manual Contents 29 Enabling the SBC Application ................ 637 30 Utilizing Gateway Channel Resources for SBC ..........639 31 Configuring General SBC Settings ..............641 31.1 Interworking Dialog Information in SIP NOTIFY Messages ......... 641 32 Configuring Admission Control ..............643 33 Routing SBC ....................
Page 14 Mediant 1000B Gateway & E-SBC 38 CRP Overview ....................717 39 CRP Configuration ..................719 39.1 Enabling the CRP Application ................719 39.2 Configuring Call Survivability Mode ..............719 39.3 Pre-Configured IP Groups ..................721 39.4 Pre-Configured IP-to-IP Routing Rules ..............722 39.4.1 Normal Mode ......................722 39.4.2 Emergency Mode ....................722 39.4.3 Auto Answer to Registrations ................723...
Page 15 45.1.1.2 Provisioning from TFTP Server using DHCP Option 66 ....... 777 45.1.2 HTTP-based Provisioning ..................778 45.1.3 FTP-based Provisioning ..................779 45.1.4 Provisioning using AudioCodes EMS ..............779 45.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 779 45.2.1 Files Provisioned by Automatic Update ..............780 45.2.2 File Location for Automatic Update ...............780...
Page 16 Mediant 1000B Gateway & E-SBC 49 Viewing Management User Activity Logs ............. 809 50 Viewing Performance Monitoring ..............811 50.1 Viewing Trunk Utilization ..................811 50.2 Viewing Call Success and Failure Ratio .............. 812 50.3 Viewing Average Call Duration ................814 50.4 Configuring Performance Profiles ................
Page 17 User's Manual Contents 55.2.1.1 Event Representation in Syslog Messages .......... 889 55.2.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ..890 55.2.1.3 Syslog Fields for Answering Machine Detection (AMD) ....... 891 55.2.1.4 SNMP Alarms in Syslog Messages ............891 55.2.2 Enabling Syslog .....................892 55.2.3 Configuring the Syslog Server Address ..............892...
Page 18 Mediant 1000B Gateway & E-SBC 62.2.8 DHCP Parameters ....................948 62.2.9 NTP and Daylight Saving Time Parameters ............950 62.3 Debugging and Diagnostics Parameters .............. 952 62.3.1 General Parameters ....................952 62.3.2 SIP Test Call Parameters ..................954 62.3.3 Syslog, CDR and Debug Parameters ..............955 62.3.4 Resource Allocation Indication Parameters............961 62.4 Security Parameters .....................
Page 19 User's Manual Contents 62.10.9.3 Metering Tone Parameters ..............1123 62.10.10 Telephone Keypad Sequence Parameters ........... 1124 62.10.11 FXO and FXS Parameters ................1128 62.10.12 Trunk Groups and Routing Parameters ............1132 62.10.13 IP Connectivity Parameters ................1140 62.10.14 Alternative Routing Parameters ..............1141 62.10.15 Number Manipulation Parameters ..............
Page 20 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
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: Related Documentation
Security measures should be done in accordance with your organization’s security policies. For basic security guidelines, refer to AudioCodes Recommended Security Guidelines document. Note: Throughout this manual, unless otherwise specified, the term device refers to your AudioCodes product.
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 New parameters: IP2IPRouting_IPGroupSetName; EnableNonCallCdr; PGroupSet; IPGroupSetMember; NoRTPDetectionTimeout. Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads.
Page 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 1000B Gateway & E-SBC  Optional Open Solution Network (OSN) server module for hosting value-added applications Note: For maximum call capacity figures, see ''Channel Capacity'' on page 1187. Typographical Conventions This document uses the following typographical conventions to convey information: Table 1-1: Typographical Conventions Convention Description...
Page 27 User's Manual 1. Introduction phones. In the SIP world, the endpoints are referred to as SIP user agents (UA). The UA that initiates the call is referred to as the user agent client (UAC); the UA that accepts the call is referred to as the user-agent server (UAS). The following table describes the main configuration concepts and terminology.
Page 28 Mediant 1000B Gateway & E-SBC Configuration Terms Description means whether the SRD's resources (SIP Interfaces, IP Groups, and Proxy Sets) can be used by other SRDs. For example, if all tenants route calls with the same SIP Trunking service provider, the SRD of the SIP Trunk would be configured as a Shared Sharing Policy.
Page 29 User's Manual 1. Introduction Configuration Terms Description routing rules. As most deployments require only one Routing Policy, the default Routing Policy is automatically assigned to the manipulation rules and to the routing rules. Routing Policy Routing Policy logically groups routing and manipulation (inbound and outbound) rules to a specific SRD.
Page 30: Gateway Application
Mediant 1000B Gateway & E-SBC 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 User's Manual 1. Introduction Configuration Terms Description assigned to the IP Group. SIP Interfaces The SIP Interface represents a Layer-3 network for the IP-based SIP entity. It defines a local listening port for SIP signaling traffic on a local, logical IP network interface. The term local implies that it's a logical port and network interface on the device.
Page 32 Mediant 1000B Gateway & E-SBC Configuration Terms Description IP-to-Tel (Trunk Group) IP-to-Tel routing rules are used to route incoming IP calls to Trunk Routing Rules Groups. 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
User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 7.2 Mediant 1000B Gateway & E-SBC...
Page 36 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27045...
Page 37: Default Oamp Ip Address
User's Manual 3. Default OAMP IP Address Default OAMP IP Address The device is shipped with a factory default IP address for operations, administration, maintenance, and provisioning (OAMP), through its VoIP LAN interface. You can use this address to initially access the device from any of its management tools (embedded Web server, EMS, or Telnet/SSH).
Page 38 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27045...
Page 39: Configuring Voip Lan Interface For Oamp
User's Manual 4. Configuring VoIP LAN Interface for OAMP Configuring VoIP LAN Interface for OAMP You can change the IP address of the VoIP-LAN interface for OAMP, using any of the following methods:  Embedded HTTP/S-based Web server - see ''Web Interface'' on page 39 ...
Page 40 Mediant 1000B Gateway & E-SBC In the 'Username' and 'Password' fields, enter the case-sensitive, default login username ("Admin") and password ("Admin"). Click Login. Configure the Ethernet port(s) that you want to use for the OAMP interface: In the Ethernet Groups table, configure an Ethernet Group by assigning it up to two ports (two ports provide optional, port-pair redundancy).
Page 41: Cli
User's Manual 4. Configuring VoIP LAN Interface for OAMP This procedure describes how to configure the VoIP-LAN IP address for OAMP through the device's CLI. The procedure uses the regular CLI commands. Alternatively, you can use the CLI Wizard utility to set up your device with the initial OAMP settings. The utility provides a fast-and-easy method for initial configuration of the device through CLI.
Page 42 Mediant 1000B Gateway & E-SBC Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Configure the Default Gateway address: (network-if-0)# gateway <IP address> Exit the IP Interfaces table: (network-if-0)# exit Exit the Network configuration mode: (config-network)# exit Reset the device with a flash burn: # reload now Cable the device to your network.
Page 43: Management Tools
Part II Management Tools...
Page 45: Introduction
User's Manual 5. Introduction Introduction This part describes the various management tools that you can use to configure the device:  Embedded HTTP/S-based Web server - see ''Web-based Management'' on page 47  Command Line Interface (CLI) - see ''CLI-Based Management'' on page 75 ...
Page 46 Mediant 1000B Gateway & E-SBC This page is intentionaly left blank. User's Manual Document #: LTRT-27045...
Page 47: Web-Based Management
User's Manual 6. Web-Based Management Web-Based Management The device provides an embedded Web server (hereafter referred to as Web interface), supporting fault management, configuration, accounting, performance, and security (FCAPS), including the following:  Full configuration  Software and configuration upgrades ...
Page 48: Accessing The Web Interface
Mediant 1000B Gateway & E-SBC 6.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser. In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...
Page 49: Areas Of The Gui
User's Manual 6. Web-Based Management Note: • The default login username and password is "Admin" (case-sensitive). To change the login credentials, see ''Configuring Management User Accounts'' on page 65. • By default, Web access is only through the IP address of the OAMP interface. However, you can allow access from all of the device's IP network interfaces, by setting the EnableWebAccessFromAllInterfaces parameter to 1.
Page 50 Mediant 1000B Gateway & E-SBC Item # Description Company logo. Menu bar containing the menus. Toolbar providing frequently required command buttons.  Save: Saves configuration changes to the device's flash memory (without resetting the device). If you make a configuration change, the button is surrounded by a red-colored border as a reminder to save your settings to flash memory, by clicking the button.
Page 51: Accessing Configuration Pages From Navigation Tree
User's Manual 6. Web-Based Management Item # Description SRD filter. When your configuration includes multiple SRDs, you can filter tables in the Web interface by a specific SRD. For more information, see ''Filtering Tables in Web Interface by SRD'' on page 322. Search box for searching parameter names and values (see ''Searching for Configuration Parameters'' on page 61).
Page 52 Mediant 1000B Gateway & E-SBC  Troubleshoot menu: Troubleshoot tab When you open the Navigation tree, folders containing commonly required items are opened by default, allowing quick access to their pages. Items that open pages containing tables provide the following indications in the Navigation tree: ...
Page 53: Configuring Stand-Alone Parameters
User's Manual 6. Web-Based Management Note: Depending on the access level (e.g., Monitor level) of your Web user account, certain pages may not be accessible or may be read-only (see ''Configuring Management User Accounts'' on page 65). For read-only privileges: •...
Page 54: Configuring Table Parameters
Mediant 1000B Gateway & E-SBC On the toolbar, click Save; a confirmation message box appears: Figure 6-4: Save Configuration Confirmation Box Click Yes to confirm; the changes are save to flash memory. • If a device reset is required: On the toolbar, click Reset; the Maintenance Actions page opens. Click Reset;...
Page 55: Adding Table Rows
User's Manual 6. Web-Based Management 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. For more information on invalid rows, see ''Invalid Value Indications'' on page Adds a new row to the table (see ''Adding Table Rows'' on page 55).
Page 56: Modifying Table Rows
Mediant 1000B Gateway & E-SBC Click Apply to add the row to the table or click Cancel to ignore your configuration. If the Save button is surrounded by a red border, you must save your settings to flash memory, otherwise they are discarded if the device resets (without a save to flash) or powers off.
Page 57: Deleting Table Rows
User's Manual 6. Web-Based Management save to flash) or powers off. 6.1.6.3 Deleting Table Rows The following procedure describes how to delete a row from a table.  To delete a table row: Select the row that you want to delete. Click the delete icon, located on the table's toolbar;...
Page 58 Mediant 1000B Gateway & E-SBC If you click Cancel, the dialog box closes and the row is not added to the table. To add the row, you must configure the parameter. • Editing a row: If you modify the parameter so that it's no longer referencing a row of another table (i.e., blank value), when you close the dialog box, the Invalid Line icon appears in the following locations:...
Page 59: Viewing Table Rows
User's Manual 6. Web-Based Management Note: If you assign a non-mandatory parameter with a referenced row and then later delete the referenced row (in the table in which the row is configured), the parameter's value automatically changes to an empty field (i.e., no row assigned). Therefore, make sure that you are aware of this and if necessary, assign a different referenced row to the parameter.
Page 60: Changing Index Position Of Table Rows
Mediant 1000B Gateway & E-SBC  To sort table rows by column: Click the name of the column by which you want to sort the table rows; the up-down arrows appear alongside the column name and the up button is displayed in a darker shade of color, indicating that the column is sorted in ascending order: Figure 6-11: Table Sorted by Index in Ascending Order To sort the column in descending order, click the column name again;...
Page 61: Searching Table Entries
User's Manual 6. Web-Based Management • To move one index down (e.g., from Index 3 to Index 4): Click the down arrow; the row moves one index down in the table (e.g., to 4) and the row that originally occupied the index is moved one index up (e.g., to 3). In other words, the rows have swapped positions.
Page 62 Mediant 1000B Gateway & E-SBC  "Port" When the device completes the search, it displays a list of found results based on the search key. Each possible result, when clicked, opens the page on which the parameter or value is located. You need to click the most appropriate result. ...
Page 63: Creating A Login Welcome Message
User's Manual 6. Web-Based Management 6.1.8 Creating a Login Welcome Message You can create a personalized welcome message that is displayed on the Web Login page, as shown in the example below: Figure 6-15: User-Defined Web Welcome Message after Login ...
Page 64: Getting Help
Mediant 1000B Gateway & E-SBC 6.1.9 Getting Help The Web interface provides you with context-sensitive pop-up help of standalone parameters. When you hover your mouse over a parameter's field, a pop-up appears with a short description of the parameter, as shown in the following example: Figure 6-16: Viewing Context-Sensitive Help for a Parameter 6.1.10 Logging Off the Web Interface The following procedure describes how to log off the Web interface.
Page 65: Configuring Management User Accounts
User's Manual 6. Web-Based Management 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 (username and password) and with a management user level which defines the level of read and write privileges.
Page 66 Mediant 1000B Gateway & E-SBC Note: • For security, it's recommended that you change the default username and password of the default users. • To restore the device to the default users (and with their default usernames and passwords), configure the ini file ResetWebPassword parameter to 1. If you have configured any other accounts, they are deleted.
Page 67 User's Manual 6. Web-Based Management Parameter Description 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 "-" signs. Password Defines the Web user's password.
Page 68 Mediant 1000B Gateway & E-SBC Parameter Description a user-defined timeout configured by the 'Block Duration' parameter (see below) or if their status is changed (to New or Valid) by a Security Administrator or Master.  Inactivity = The state is automatically set for users that have not accessed the Web interface for a user-defined number of days, set by the 'User Inactivity Timer' (see ''Configuring Web Session and Access Settings'' on page 70).
Page 69: Displaying Login Information Upon Login
User's Manual 6. Web-Based Management Parameter Description  The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Displaying Login Information upon Login You can enable the device to display login information immediately upon Web login. ...
Page 70: Configuring Web Session And Access Settings
Mediant 1000B Gateway & E-SBC The following information is displayed:  'Access Level': User level of the currently logged in user (e.g., Security Administrator).  'Session Time': Duration of the current Web session (starting from login). The Log Out button is also provided for logging out of the Web session (see ''Logging Off the Web Interface'' on page 64).
Page 71: Changing Login Password For Administrator And Monitor Users
User's Manual 6. Web-Based Management Under the Security group, configure the following parameters: Figure 6-23: Configuring Web User Security • 'Deny Authentication Timer': Interval (in seconds) that the user needs to wait before logging in from the same IP address after reaching the maximum number of failed login attempts (see next step).
Page 72: Configuring Secured (Https) Web
- what the user has (i.e., the physical card) and what the user knows (i.e., the login password). This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative. User's Manual Document #: LTRT-27045...
Page 73: Configuring Web And Telnet Access List
User's Manual 6. Web-Based Management  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader. Access the device using the following URL: https://<host name or IP address>; the device prompts for a username and password. Enter the password only.
Page 74 Mediant 1000B Gateway & E-SBC Note: When deleting all the IP addresses, make sure that you delete the IP address of the computer from which you are currently logged into the device, last; otherwise, access from your computer will be immediately denied. ...
Page 75: Cli-Based Management
User's Manual 7. CLI-Based Management CLI-Based Management This chapter provides an overview of the CLI-based management and provides configuration relating to CLI management. Note: • By default, CLI is disabled (for security purposes). • The CLI can only be accessed by management users with the following user levels: √...
Page 76: Using Cli Shortcuts
Mediant 1000B Gateway & E-SBC The Enable mode groups the configuration commands under the following command sets: • configure network: Contains IP network-related commands (e.g., interface and dhcp-server): # configure network (config-network)# • configure voip: Contains voice-over-IP related commands (e.g., ip-group, sbc, gateway, and media): # configure voip (config-voip)#...
Page 77: Common Cli Commands
User's Manual 7. CLI-Based Management Shortcut Key Description  Displays a list of all subcommands in the current mode, for example: ? (question mark) (config-network)# ? access-list Network access list dhcp-server DHCP server configuration configuration  Displays a list of available commands beginning with certain letter(s), for example: (config-network)# d? dhcp-server...
Page 78: Configuring Tables Through Cli
Mediant 1000B Gateway & E-SBC Command Description virtual-LAN interface command set: (config)# interface vlan 1 (conf-if-VLAN 1)# do show interfaces GigabitEthernet 0/0 Undoes an issued command or disables a feature. Enter no before the command: # no debug log activate Activates a command.
Page 79: Understanding Cli Error Messages
User's Manual 7. CLI-Based Management When you add a new table row, the device accesses the row's configuration mode. For example, if three rows are configured in the Accounts table (account-0, account-1, and account-2) and you then add a new row, account-3 is automatically created and its' configuration mode is accessed: (config-voip)# sip-definition account new (account-3)#...
Page 80: Enabling Cli
Mediant 1000B Gateway & E-SBC Enabling CLI By default, access to the device's CLI through Telnet and SSH is disabled. This section describes how to enable these protocols. 7.2.1 Enabling Telnet for CLI The following procedure describes how to enable Telnet. You can enable a secured Telnet that uses Secure Socket Layer (SSL) where information is not transmitted in clear text.
Page 81 User's Manual 7. CLI-Based Management  To enable SSH and configure RSA public keys for Windows (using PuTTY SSH software): Start the PuTTY Key Generator program, and then do the following: Under the 'Parameters' group, do the following: ♦ Select the SSH-2 RSA option. ♦...
Page 82 Mediant 1000B Gateway & E-SBC For additional security, you can configure the 'Public Key' field to Enable. This ensures that SSH access is only possible by using the RSA key and not by username and password. Configure the other SSH parameters as required. For a description of these parameters, see ''SSH Parameters'' on page 967.
Page 83: Configuring Maximum Telnet/Ssh Sessions
User's Manual 7. CLI-Based Management Configuring Maximum Telnet/SSH Sessions You can configure the maximum number of concurrent Telnet and SSH sessions (up to five) permitted on the device. Note: Before changing the setting, make sure that not more than the number of sessions that you want to configure are currently active;...
Page 84: Viewing Current Cli Sessions
Mediant 1000B Gateway & E-SBC At the Password prompt, type the password, and then press Enter: Password: Admin At the prompt, type the following, and then press Enter: > enable At the prompt, type the password again, and then press Enter: Password: Admin Viewing Current CLI Sessions You can view users that are currently logged in to the device's CLI.
Page 85: Configuring Displayed Output Lines In Cli Terminal Window
User's Manual 7. CLI-Based Management Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be from 0 to 65,535, or determined by re-sizing the terminal window by mouse-dragging the window's border.
Page 86 Mediant 1000B Gateway & E-SBC  To configure the number of displayed output lines by dragging terminal window: Establish a CLI session with the device. Access the System menu: # configure system At the prompt, type the following command: (config-system)# cli-terminal At the prompt, type the following command: <cli-terminal># window-height automatic When this mode is configured, each time you change the height of the terminal window...
Page 87: Snmp-Based Management
8. 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 88 Mediant 1000B Gateway & E-SBC 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 92). • You can enhance security by configuring Trusted Managers (see ''Configuring SNMP Trusted Managers'' on page 91).
Page 89: Configuring Snmp Trap Destinations With Ip Addresses
User's Manual 8. SNMP-Based Management Table 8-1: SNMP Community String Parameter Descriptions Parameter Description Read Only Community Strings Defines read-only SNMP community strings. Up to five read- only community strings can be configured. configure system > snmp settings > ro-community-string The valid value is a string of up to 19 characters that can include only the following: [SNMPReadOnlyCommunityString_x]...
Page 90 Mediant 1000B Gateway & E-SBC  To configure SNMP trap destinations: Open the SNMP Trap Destinations table (Setup menu > Administration tab > SNMP folder > SNMP Trap Destinations). Figure 8-3: SNMP Trap Destinations Table Configure the SNMP trap manager according to the table below. Select the check boxes corresponding to the configured SNMP managers that you want to enable.
Page 91: Configuring An Snmp Trap Destination With Fqdn
User's Manual 8. SNMP-Based Management Parameter Description Trap Enable Activates the sending of traps to the SNMP Manager.  [SNMPManagerTrapSendingEnable_x] [0] Disable  [1] Enable (Default) Configuring an SNMP Trap Destination with FQDN Instead of configuring SNMP trap destinations (managers) with IP addresses in dotted- decimal notation in the SNMP Trap Destinations table (see ''Configuring SNMP Trap Destination with IP Addresses'' on page 89), you can configure a single SNMP trap manager with an FQDN (e.g., mngr.corp.mycompany.com).
Page 92: Enabling Snmp Traps For Web Activity
Mediant 1000B Gateway & E-SBC  To configure SNMP Trusted Managers: Open the SNMP Trusted Managers table (Setup menu > Administration tab > SNMP folder > SNMP Trusted Managers). Figure 8-4: SNMP Trusted Managers Table Configure an IP address (in dotted-decimal notation) for one or more SNMP Trusted Managers.
Page 93 User's Manual 8. SNMP-Based Management  To configure an SNMP v3 user: Open the SNMPv3 Users table (Setup menu > Administration tab > SNMP folder > SNMP V3 Users). Click New; the following dialog box appears: Figure 8-6: SNMPv3 Users Table - Dialog Box Configure the SNMP V3 parameters according to the table below.
Page 94 Mediant 1000B Gateway & E-SBC Parameter Description auth-key or long hex string. Keys are always persisted as long hex 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 95: Ini File-Based Management
User's Manual 9. INI File-Based Management INI File-Based Management You can configure the device through an ini file, which is a text-based file with an *.ini file extension name, created using any standard text-based editor such as Notepad. Once you have created an ini file with all your configuration settings, you need to install (load) it to the device to apply the configuration.
Page 96 Mediant 1000B Gateway & E-SBC • 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 97: General Ini File Formatting Rules
User's Manual 9. INI File-Based Management 9.1.3 General ini File Formatting Rules The ini file must adhere to the following formatting rules:  The ini file name must not include hyphens "-" or spaces; if necessary, use an underscore "_" instead. ...
Page 98: 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 99 User's Manual 9. INI File-Based Management When obscured password mode is enabled, you can enter a password in the ini file using any of the following formats:  $1$<obscured password>: Password in obscured format as generated by the device; useful for restoring device configuration and copying configuration from one device to another.
Page 100: Ini Viewer And Editor Utility
Mediant 1000B Gateway & E-SBC INI Viewer and Editor Utility AudioCodes INI Viewer & Editor utility provides a user-friendly graphical user interface (GUI) that lets you easily view and modify the device's ini file. This utility is available from AudioCodes Web site at www.AudioCodes.com/downloads, and can be installed on any Windows-based PC.
Page 101: General System Settings
Part III General System Settings...
Page 103: Configuring Ssl/Tls Certificates
User's Manual 10. Configuring SSL/TLS Certificates Configuring SSL/TLS Certificates The TLS Contexts table lets you configure X.509 certificates which are used for secure management of the device, secure SIP transactions, and other security applications. Note: • The device is shipped with an active, default TLS setup. Configure certificates only if required.
Page 104 Mediant 1000B Gateway & E-SBC 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 105 User's Manual 10. Configuring SSL/TLS Certificates Configure the TLS Context according to the parameters described in the table below. Click Apply, and then reset the device with a save-to-flash for your settings to take effect. Table 10-1: TLS Contexts Parameter Descriptions Parameter Description General...
Page 106 Mediant 1000B Gateway & E-SBC Parameter Description  [7] TLSv1.0 TLSv1.1 and TLSv1.2 = Only TLS 1.0, TLS 1.1 and TLS 1.2 (excludes SSL 3.0). Cipher Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher list format). ciphers-server For valid values, refer to URL [TLSContexts_ServerCipherString]...
Page 107: Assigning Csr-Based Certificates To Tls Contexts
User's Manual 10. Configuring SSL/TLS Certificates 10.2 Assigning CSR-based Certificates to TLS Contexts The following procedure describes how to request a digitally signed certificate from a Certification Authority (CA) for a TLS Context. This process is referred to as a certificate signing request (CSR) and is required if your organization employs a Public Key Infrastructure (PKI) system.
Page 108 Mediant 1000B Gateway & E-SBC Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-1: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request. When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt).
Page 109: Viewing Certificate Information
User's Manual 10. Configuring SSL/TLS Certificates Make sure that the 'Private key' field displays "OK"; otherwise, consult with your security administrator. Figure 10-2: Verifying Private Key Note: • The certificate replacement process can be repeated whenever necessary (e.g., the new certificate expires). •...
Page 110: Assigning Externally Created Private Keys To Tls Contexts
Mediant 1000B Gateway & E-SBC Select a TLS Context row, and then click the Certificate Information link located below the table; the Certificate Information page appears: Figure 10-3: Viewing Certificate Information 10.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.
Page 111: Generating Private Keys For Tls Contexts
User's Manual 10. Configuring SSL/TLS Certificates In the table, select the required TLS Context index row, and then click the Change Certificate link located below the table; the Context Certificates page appears. Scroll down to the Upload Certificate Files From Your Computer group: Figure 10-4: Upload Certificate Files from your Computer Group Fill in the 'Private key pass-phrase' field, if required.
Page 112 Mediant 1000B Gateway & E-SBC 103). In the table, select the required TLS Context index row, and then click the Change Certificates link located below the table; the Context Certificates page appears. Scroll down to the Generate New Private Key and Self-signed Certificate group: Figure 10-6: Generate new private key and self-signed certificate Group From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys:...
Page 113: Creating Self-Signed Certificates For Tls Contexts
User's Manual 10. Configuring SSL/TLS Certificates 10.6 Creating Self-Signed Certificates for TLS Contexts The following procedure describes how to assign a certificate that is digitally signed by the device itself to a TLS Context. In other words, the device acts as a CA. ...
Page 114: Importing Certificates And Certificate Chain Into Trusted Certificate Store
Mediant 1000B Gateway & E-SBC Click OK to confirm generation; the device generates a new self-signed certificate displaying the new subject name, indicated by a message in the Certificate Signing Request group: Figure 10-9: Generated Self-Signed Certificate Save the configuration with a device reset for the new certificate to take effect. 10.7 Importing Certificates and Certificate Chain into Trusted Certificate Store...
Page 115 User's Manual 10. Configuring SSL/TLS Certificates For the device to trust a whole chain of certificates per TLS Context, you need to add them to the device's Trusted Certificates Store, as described below. Note: Only Base64 (PEM) encoded X.509 certificates can be loaded to the device. ...
Page 116: Configuring Mutual Tls Authentication
Mediant 1000B Gateway & E-SBC 10.8 Configuring Mutual TLS Authentication This section describes how to configure mutual (two-way) TLS authentication. 10.8.1 TLS for SIP Clients When Secure SIP (SIPS) is implemented using TLS, it is sometimes required to use two- way (mutual) authentication between the device and a SIP user agent (client).
Page 117: Configuring Tls Server Certificate Expiry Check
User's Manual 10. Configuring SSL/TLS Certificates certificate doesn't work. Restore the previous setting after testing the configuration. In the TLS Contexts table (see ''Configuring TLS Certificate Contexts'' on page 103), select the required TLS Context row, and then click the Trusted Root Certificates link located below the table;...
Page 118 Mediant 1000B Gateway & E-SBC Scroll down the page to the TLS Expiry Settings group: Figure 10-12: TLS Expiry Settings Group In the 'TLS Expiry Check Start' field, enter the number of days before the installed TLS server certificate is to expire when the device sends an SNMP trap event to notify of this.
Page 119: Date And Time
User's Manual 11. Date and Time Date and Time The date and time of the device can be configured manually or it can be obtained automatically from a Simple Network Time Protocol (SNTP) server. 11.1 Configuring Automatic Date and Time using SNTP The device's Simple Network Time Protocol (SNTP) client functionality generates requests and reacts to the resulting responses using the NTP Version 3 protocol definitions (according to RFC 1305).
Page 120: Configuring Date And Time Manually
Mediant 1000B Gateway & E-SBC 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 121: Configuring The Time Zone
User's Manual 11. Date and Time 11.3 Configuring the Time Zone You can configure the time zone in which the device is deployed. This is referred to as the Coordinated Universal Time (UTC) time offset and defines how many hours the device is from Greenwich Mean Time (GMT).
Page 122 Mediant 1000B Gateway & E-SBC Enable. From the 'DST Mode' drop-down list, select the range type for configuring the start and end dates for DST: • Day of year: The range is configured by exact date (day number of month), for example, from March 30 to October 30.
Page 123: General Voip Configuration
Part IV General VoIP Configuration...
Page 125: Network
User's Manual 12. Network Network This section describes network-related configuration. 12.1 Building and Viewing your Network Topology The Network view lets you easily build and view your voice network topology entities, including IP network interfaces, Ethernet Devices (VLANs), Ethernet Groups, and physical Ethernet ports.
Page 126 Mediant 1000B Gateway & E-SBC Table 12-1: Description of Network View Item # Description Configures and displays IP Interfaces. The IP Interface appears as an icon, displaying the application type ("OCM" for OAMP, "C" for Control, and "M" for Media), row index number, name, and IP address, as shown in the example below: If you click the icon, a drop-down menu appears listing the following commands: ...
Page 127 User's Manual 12. Network Item # Description table closes and you are returned to the Network View, displaying the newly added Ethernet Device. For more information on configuring Ethernet Devices, see ''Configuring Underlying Ethernet Devices'' on page 132. Configures and displays Ethernet Groups. The Ethernet Groups appear as icons, displaying the row index number and name, as shown in the example below: Ethernet ports associated with Ethernet Groups are indicated by lines connecting between...
Page 128: Configuring Physical Ethernet Ports
Mediant 1000B Gateway & E-SBC Item # Description  Red: No network connectivity through port (e.g., cable disconnected). To refresh the status indication, click the Refresh Network View button (described below in Item #5). To open the Physical Ports table, click any port icon, and then from the drop-down menu, choose View Physical Port List.
Page 129 User's Manual 12. Network  To configure the physical Ethernet ports: Open the Physical Ports table (Setup menu > IP Network tab > Core Entities folder > Physical Ports). Select a port that you want to configure, and then clicking Edit; the following dialog box appears: Configure the port according to the parameters described in the table below.
Page 130: Configuring Ethernet Port Groups
Note: The SWX LAN Expansion module is a customer-ordered item. For more information, contact your AudioCodes sales representative. The port names (strings) displayed in the Ethernet Groups table represent the physical ports on the device. For the mapping of these strings to the physical ports, see Configuring Physical Ethernet Ports on page 128.
Page 131 User's Manual 12. Network Note: • If you want to assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group. To remove the port, configure the 'Member' field so that no port is selected or select a different port. •...
Page 132: Configuring Underlying Ethernet Devices
Mediant 1000B Gateway & E-SBC Parameter Description later stage, a switchover to the redundant port is done, which begins to transmit and receive.  [4] 2RX/2TX = Both ports in the Ethernet Group can receive and transmit packets. This option is currently not relevant and should not be used.
Page 133 User's Manual 12. Network Note: You cannot delete an Ethernet Device that is associated with an IP network interface (in the IP Interfaces table). You can only delete it once you have disassociated it from the IP network interface. The following procedure describes how to configure Ethernet Devices through the Web interface.
Page 134 Mediant 1000B Gateway & E-SBC Parameter Description Note: The parameter is mandatory. Tagging Defines VLAN tagging for the Ethernet Device.  tagging [0] Untagged = (Default for pre-configured Ethernet Device) The Ethernet Device accepts untagged packets and packets [DeviceTable_Tagging] with the same VLAN ID as the Ethernet Device. Incoming untagged packets are assigned the VLAN ID of the Ethernet Device.
Page 135: Configuring Ip Network Interfaces
User's Manual 12. Network 12.5 Configuring IP Network Interfaces You can configure a single VoIP network interface for all applications, including OAMP (management traffic), call control (SIP signaling messages), and media (RTP traffic), or you can configure multiple logical, IP network interfaces for these applications. You may need to logically separated network segments for these applications for administration and security.
Page 136 Mediant 1000B Gateway & E-SBC  (Optional) Primary and secondary domain name server (DNS) addresses for resolving FQDNs into IP addresses.  Ethernet Device: Layer-2 bridging device and assigned a VLAN ID. As the Ethernet Device is associated with an Ethernet Group, this is useful for setting trusted and un- trusted networks on different physical Ethernet ports.
Page 137 User's Manual 12. Network Note: • If you edit or delete an IP interface, current calls using the interface are immediately terminated. • If you delete an IP interface, row indices of other tables (e.g., Media Realms table) that are associated with the deleted IP interface, lose their association with the interface ('Interface Name' field displays "None") and the row indices become invalid.
Page 138 Mediant 1000B Gateway & E-SBC Parameter Description Interface Mode Defines the method that the interface uses to acquire its IP address.  mode [3] IPv6 Manual Prefix = IPv6 manual prefix IP address assignment. The IPv6 prefix (higher 64 bits) is set manually while [InterfaceTable_InterfaceMod the interface ID (the lower 64 bits) is derived from the device's MAC address.
Page 139: Assigning Ntp Services To Application Types
User's Manual 12. Network 12.5.1 Assigning NTP Services to Application Types You can associate the Network Time Protocol (NTP) application with the OAMP or Control application type. This is done using the EnableNTPasOAM ini file parameter. For more information on NTP, see ''Configuring Automatic Date and Time using SNTP'' on page 119. 12.5.2 IP Interfaces Table Configuration Guidelines Adhere to the following guidelines when configuring network interfaces in the IP Interfaces table:...
Page 140: Networking Configuration Examples
Mediant 1000B Gateway & E-SBC 12.5.3 Networking Configuration Examples This section provides configuration examples of networking interfaces. 12.5.3.1 One VoIP Interface for All Applications This example describes the configuration of a single VoIP interface for all applications: IP Interfaces table: Configured with a single interface for OAMP, Media and Control: Table 12-6: Example of Single VoIP Interface in IP Interfaces table Application Interface...
Page 141: Voip Interfaces For Combined Application Types
User's Manual 12. Network Table 12-9: Example Static Routes Table Destination Prefix Length Gateway 176.85.49.0 192.168.11.1 All other parameters are set to their respective default values. The NTP application remains with its default application types. 12.5.3.3 VoIP Interfaces for Combined Application Types This example describes the configuration of multiple interfaces for the following applications: ...
Page 142: Voip Interfaces With Multiple Default Gateways
Mediant 1000B Gateway & E-SBC ♦ For Media Service class, the default DiffServ value is set to 46 ♦ For Control Service class, the default DiffServ value is set to 40 ♦ For Gold Service class, the default DiffServ value is set to 26 ♦...
Page 143 User's Manual 12. Network  To configure static IP routes: Open the Static Routes table (Setup menu > IP Network tab > Core Entities folder > Static Routes). Click New; the following dialog box appears: Configure a static route according to the parameters described in the table below. The address of the host/network you want to reach is determined by an AND operation that is applied to the fields 'Destination' and 'Prefix Length'.
Page 144: Configuration Example Of Static Ip Routes
Mediant 1000B Gateway & E-SBC Parameter Description Prefix Length Defines the Classless Inter-Domain Routing (CIDR)-style representation of a dotted-decimal subnet notation of the prefix-length destination host/network. The CIDR-style representation uses a [StaticRouteTable_PrefixLength] suffix indicating the number of bits that are set in the dotted- decimal format.
Page 145: Troubleshooting The Static Routes Table
User's Manual 12. Network  The static route's Gateway address in the Static Routes table is in the same subnet as the IP address of the IP network interface in the IP Interfaces table. Figure 12-4: Example of using a Static Route 12.6.2 Troubleshooting the Static Routes Table When adding a new static route to the Static Routes table, the added rule passes a validation test.
Page 146: Network Address Translation Support
Mediant 1000B Gateway & E-SBC 12.7 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 the number of global IP addresses required in a private network (global IP addresses are only used to connect to the Internet) and (2) better network security by hiding the internal architecture.
Page 147: Configuring A Static Nat Ip Address For All Interfaces
User's Manual 12. Network The figure below illustrates the NAT problem faced by SIP networks when the device is located behind a NAT: Figure 12-5: Device behind NAT and NAT Issues 12.7.1.1 Configuring a Static NAT IP Address for All Interfaces You can configure a global (public) IP address of the router to enable static NAT between the device and the Internet for all network interfaces.
Page 148: Configuring Nat Translation Per Ip Interface
Mediant 1000B Gateway & E-SBC 12.7.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.
Page 149: Remote Ua Behind Nat
User's Manual 12. Network Parameter Description [NATTranslation_SourceStartPort] configured, the match is done on the entire port range. Only IP addresses and ports of matched source ports will be replaced. Source End Port Defines the optional ending port range (1-65536) of the IP interface, used as matching criteria for the NAT rule.
Page 150: Media (Rtp/Rtcp/T.38)
Mediant 1000B Gateway & E-SBC this feature is disabled, the device's NAT detection is according to the settings of the global parameter, 'SIP NAT Detection' parameter (see below procedure).  To enable the NAT Detection feature (global): Open the Transport Settingspage (Setup menu > Signaling & Media tab > SIP Definitions folder >...
Page 151 User's Manual 12. Network The device identifies whether the UA is located behind NAT by comparing the source IP address of the first received media packet with the IP address and UDP port of the first received SIP message (INVITE) when the SIP session was started. This is done for each media type--RTP, RTCP and T.38--and therefore, they can have different destination IP addresses and UDP ports than one another.
Page 152: Configuring Quality Of Service
Mediant 1000B Gateway & E-SBC avt-rtp-noop-03 ("A No-Op Payload Format for RTP"). The IETF document defines a No-Op payload format for RTP. The draft defines the RTP payload type as dynamic. You can configure the payload type as described in the following procedure (default is 120).
Page 153 User's Manual 12. Network The mapping of an application to its CoS and traffic type is shown in the table below: Table 12-16: Traffic/Network Types and Priority Application Traffic / Network Types Class-of-Service (Priority) Debugging interface Management Bronze Telnet Management Bronze Web server (HTTP) Management...
Page 154: Configuring Diffserv-To-Vlan Priority Mapping
Mediant 1000B Gateway & E-SBC Table 12-17: QoS Settings Parameter Descriptions Parameter Description Media Premium QoS Defines the DiffServ value for Premium Media CoS content. media-qos The valid range is 0 to 63. The default is 46. [PremiumServiceClassMediaDiffServ] Note: You can also configure the the parameter per IP Profile (IpProfile_IPDiffServ) or Tel Profile (TelProfile_IPDiffServ).
Page 155: Configuring Icmp Messages
User's Manual 12. Network Click New; the following dialog box appears: Figure 12-12: QoS Mapping Table - Add Dialog Box Configure a DiffServ-to-VLAN priority mapping rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 12-18: QoS Mapping Table Parameter Descriptions Parameter Description...
Page 156: Dns
Mediant 1000B Gateway & E-SBC  To configure handling of ICMP messages: Open the Network Settings page (Setup menu > IP Network tab > Advanced folder > Network Settings). Figure 12-13: Configuring ICMP Messaging Under the ICMP group, do the following: •...
Page 157: Configuring The Internal Srv Table
User's Manual 12. Network Click New; the following dialog box appears: Figure 12-14: Internal DNS Table - Add Dialog Box Configure a DNS rule according to the parameters described in the table below. Click Apply. Table 12-19: Internal DNS Table Parameter Description Parameter Description Index...
Page 158 Mediant 1000B Gateway & E-SBC Note: The device first attempts to resolve a domain name using the table. If the domain is not configured in the table, the device performs a Service Record (SRV) resolution using an external DNS server, configured in the IP Interfaces table (see ''Configuring IP Network Interfaces'' on page 135).
Page 159 User's Manual 12. Network Parameter Description 1st/2nd/3rd Entry DNS Name (1-3) Defines the first, second or third DNS A-Record to which the host name is translated. dns-name-1|2|3 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.
Page 160: Open Solution Network (Osn) Server
Mediant 1000B Gateway & E-SBC 12.11 Open Solution Network (OSN) Server This section describes various networking settings for the OSN server. Note: • The OSN is a customer-ordered item. • For information on cabling the OSN, refer to the device's Hardware Installation Manual.
Page 161: Disabling Internal Switch Port For Osn
User's Manual 12. Network 12.11.2 Disabling Internal Switch Port for OSN You can enable or disable the Ethernet port of the device's internal switch, which interfaces with the OSN server. If the port is not blocked, you can optionally access the OSN server through any Ethernet port on the device's front panel (instead of through the OSN module's Ethernet ports located on the rear panel).
Page 162: Robust Receipt Of Media Streams By Media Latching
Mediant 1000B Gateway & E-SBC 12.12 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 163: Security
User's Manual 13. Security Security This section describes the VoIP security-related configuration. 13.1 Configuring Firewall Settings The Firewall table lets you configure up to 50 firewall rules, which define network traffic filtering rules (access list). The access list offers the following firewall possibilities: ...
Page 164 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 13-1: Firewall Table - Add Dialog Box Configure a firewall rule according to the parameters described in the table below. Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
Page 165 User's Manual 13. Security Parameter Description Start Port Defines the destination UDP/TCP start port (on this device) to where packets are sent. start-port The valid range is 0 to 65535. [AccessList_Start_Port] Note: When the protocol type isn't TCP or UDP, the entire range must be provided.
Page 166 Mediant 1000B Gateway & E-SBC Parameter Description 50000, then this implies the following: the allowed bandwidth is 40000 bytes/sec with extra allowance of 50000 bytes; if, for example, the actual traffic rate is 45000 bytes/sec, then this allowance would be consumed within 10 seconds, after which all traffic exceeding the allocated 40000 bytes/sec is dropped.
Page 167: Configuring General Security Settings
User's Manual 13. Security 13.2 Configuring General Security Settings The device uses TLS over TCP to encrypt and optionally, authenticate SIP messages. This is referred to as Secure SIP (SIPS). SIPS uses the X.509 certificate exchange process, as described in ''Configuring SSL/TLS Certificates'' on page 103, where you need to configure certificates (TLS Context).
Page 168: Enabling Ids
Mediant 1000B Gateway & E-SBC  Block (blacklist) remote hosts (IP addresses / ports) considered by the device as malicious. The device automatically blacklists the malicious source for a user-defined period after which it is removed from the blacklist.  Send SNMP traps to notify of malicious activity and/or whether an attacker has been added to or removed from the blacklist.
Page 169: Configuring Ids Policies
User's Manual 13. Security effect. 13.3.2 Configuring IDS Policies Configuring IDS Policies is a two-stage process that includes the following tables: IDS Policies (parent table): Defines a name and provides a description for the IDS Policy. You can configure up to 20 IDS Policies. IDS Rules table (child table): Defines the actual rules for the IDS Policy.
Page 170 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 13-5: IDS Policies Table - Add Dialog Box Configure an IDS Policy name according to the parameters described in the table below. Click Apply. Table 13-3: IDS Policies Table Parameter Descriptions Parameter Description Index...
Page 171 User's Manual 13. Security Click New; the following dialog box appears: Figure 13-6: IDS Rule Table - Add Dialog Box The figure above shows a configuration example: If 15 malformed SIP messages ('Reason') are received within a period of 30 seconds ('Threshold Window'), a minor alarm is sent ('Minor-Alarm Threshold').
Page 172 Mediant 1000B Gateway & E-SBC Parameter Description message includes authentication)  [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 647). This also applies to calls rejected by the device based on a registered users policy (configured by the SRD_BlockUnRegUsers or SIPInterface_BlockUnRegUsersblocks parameters).
Page 173: Assigning Ids Policies
User's Manual 13. Security Parameter Description [IDSRule_DenyThreshold] The default is -1 (i.e., not configured). Note: The parameter is applicable only if the 'Threshold Scope' parameter is set to IP or IP+Port. Deny Period Defines the duration (in sec) to keep the attacker on the blacklist, if configured using the 'Deny Threshold' parameter.
Page 174 Mediant 1000B Gateway & E-SBC The figure above shows a configuration example where the IDS Policy "SIP Trunk" is applied to SIP Interfaces 1 and 2, and to all source IP addresses outside of subnet 10.1.0.0/16 and IP address 10.2.2.2. Configure a rule according to the parameters described in the table below.
Page 175: Viewing Ids Alarms
User's Manual 13. Security Parameter Description policy page 169). [IDSMatch_Policy] 13.3.4 Viewing IDS Alarms For the IDS feature, the device sends the following SNMP traps:  Traps that notify the detection of malicious attacks: • acIDSPolicyAlarm: The device sends this alarm whenever a threshold of a specific IDS Policy rule is crossed.
Page 176 Mediant 1000B Gateway & E-SBC Where SI is the SIP Interface and NI is the network interface. The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This occurs only if you have configured Syslog (see ''Enabling Syslog'' on page 892).
Page 177: Media
User's Manual 14. Media Media This section describes the media-related configuration. 14.1 Configuring Voice Settings The section describes various voice-related configuration such as voice volume, silence suppression, and DTMF transport type. For a detailed description of these parameters, see ''Configuration Parameters Reference'' on page 927. 14.1.1 Configuring Voice Gain (Volume) Control The device allows you to configure the level of the received (input gain) Tel-to-IP or IP-to- IP signal and the level of the transmitted (output gain) IP-to-Tel or IP-to-IP signal.
Page 178: Configuring Echo Cancellation
Mediant 1000B Gateway & E-SBC Click Apply. 14.1.3 Configuring Echo Cancellation The device supports adaptive linear (line) echo cancellation according to G.168-2002. Echo cancellation is a mechanism that removes echo from the voice channel. Echoes are reflections of the transmitted signal. In this line echo, echoes are generated when two-wire telephone circuits (carrying both transmitted and received signals on the same wire pair) are converted to a four-wire circuit.
Page 179: Fax/Modem Operating Modes
User's Manual 14. Media Note: • Unless otherwise specified, the configuration parameters mentioned in this section are available on this page. • Some SIP parameters override these fax and modem parameters. For example, the IsFaxUsed parameter and V.152 parameters in Section ''V.152 Support'' on page 189.
Page 180: Fax Relay Mode
Mediant 1000B Gateway & E-SBC  T.38 fax relay (see ''T.38 Fax Relay Mode'' on page 180)  G.711 Transport: switching to G.711 when fax/modem is detected (see ''G.711 Fax / Modem Transport Mode'' on page 182)  Fax fallback to G.711 if T.38 is not supported (see ''Fax Fallback'' on page 183) ...
Page 181 User's Manual 14. Media  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 14-5: Configuring Fax Signaling to T.38 On the Fax/Modem/CID Settings page, configure the following optional parameters: •...
Page 182: Fax / Modem Transport Mode
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 183: Fax Fallback
User's Manual 14. Media  Echo Canceller = off  Silence Compression = off  Echo Canceller Non-Linear Processor Mode = off  Dynamic Jitter Buffer Minimum Delay = 40  Dynamic Jitter Buffer Optimization Factor = 13 After a few seconds upon detection of fax V.21 preamble or super G3 fax signals, the device sends a second Re-INVITE enabling the echo canceller (the echo canceller is disabled only on modem transmission).
Page 184: Fax/Modem Bypass Mode
Mediant 1000B Gateway & E-SBC  To configure fax fallback mode: 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 Fax Fallback: Figure 14-8: Configuring Fax Signaling to Fallback Click Apply.
Page 185: 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 186: Fax / Modem Transparent With Events Mode
Mediant 1000B Gateway & E-SBC 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).
Page 187: Rfc 2833 Ans Report Upon Fax/Modem Detection
User's Manual 14. Media On the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Disable (FaxTransportMode = 0). Set the 'V.21 Modem Transport Type' parameter to Disable (V21ModemTransportType = 0). Set the 'V.22 Modem Transport Type' parameter to Disable (V22ModemTransportType = 0).
Page 188: Bypass Mechanism For V.34 Fax Transmission
Mediant 1000B Gateway & E-SBC  Bypass mechanism for V.34 fax transmission (see ''Bypass Mechanism for V.34 Fax Transmission'' on page 188)  T.38 Version 0 relay mode, i.e., fallback to T.38 (see ''Relay Mode for T.30 and V.34 Faxes'' on page 188) Note: •...
Page 189: Support
User's Manual 14. Media Set the 'V.32 Modem Transport Type' parameter to Disable (V32ModemTransportType = 0). Set the 'V.34 Modem Transport Type' parameter to Disable (V34ModemTransportType = 0). 14.2.4 V.152 Support The device supports the ITU-T recommendation V.152 (Procedures for Supporting Voice- Band Data over IP Networks).
Page 190 Mediant 1000B Gateway & E-SBC The device uses a dynamic jitter buffer that can be configured with the following:  Minimum delay: Defines the starting jitter capacity of the buffer. For example, at 0 msec, there is no buffering at the start. At the default level of 10 msec, the device always buffers incoming packets by at least 10 msec worth of voice frames.
Page 191: Comfort Noise Generation
User's Manual 14. Media Set the 'Dynamic Jitter Buffer Optimization Factor' parameter (DJBufOptFactor) to the Dynamic Jitter Buffer frame error/delay optimization factor. Click Apply. 14.3.2 Comfort Noise Generation The device can generate artificial background noise, called comfort noise, in the voice channel during periods of silence (i.e.
Page 192 Mediant 1000B Gateway & E-SBC Set the 'Declare RFC 2833 in SDP' parameter to No (RxDTMFOption = 0). Set the 'First Tx DTMF Option' parameter to INFO Nortel (FirstTxDTMFOption = Note: DTMF digits are removed from the audio stream (and the 'DTMF Transport Type' parameter is automatically set to Mute DTMF).
Page 193: Configuring Rfc 2833 Payload
User's Manual 14. Media Note: • The device is always ready to receive DTMF packets over IP in all possible transport modes: INFO messages, NOTIFY, and RFC 2833 (in proper payload type) or as part of the audio stream. • To exclude RFC 2833 Telephony event parameter from the device's SDP, set the 'Declare RFC 2833 in SDP' parameter to No.
Page 194: Event Detection And Notification Using X-Detect Header
Mediant 1000B Gateway & E-SBC You can configure the starting port (lower boundary) of the port range (default is 6000), using the BaseUDPPort parameter. Once configured, the port range is according to the following equation: <BaseUDPPort parameter value> to [BaseUDPPort parameter value + (number of channels * 10)] Where, number of channels is the maximum number of purchased channels for the device (included in the installed License Key).
Page 195 User's Manual 14. Media be left. For more information on AMD, see ''Answering Machine Detection (AMD)'' on page 200.  Call Progress Tone (CPT): Detects whether a specific tone, defined in the installed CPT file is received from the call. It can be used to detect the beep sound played by an answering machine (as mentioned above), Special Information Tones (SIT) which indicate call failure with a recorded announcement describing the call failure, and the busy, reorder and ring tones.
Page 196: Sit Event Detection
Mediant 1000B Gateway & E-SBC Event Subtype Description and Required Configuration Type  SIT-RO Install the CPT file on the device.  Busy For SIT detection:  Reorder Set the SITDetectorEnable parameter to 1.  Ringtone Set the UserDefinedToneDetectorEnable parameter to 1. ...
Page 197: Detecting Answering Machine Beeps
User's Manual 14. Media Special Description First Tone Second Tone Third Tone Information Frequency Frequency Frequency Tones (SITs) Duration Duration Duration Name (Hz) (ms) (Hz) (ms) (Hz) (ms) Vacant circuit (non 985.2 1370.6 1776.7 registered number) Reorder (system 913.8 1428.5 1776.7 busy) 913.8...
Page 198: Sip Call Flow Examples Of Event Detection And Notification
CSeq: 1 INFO Contact: <sip:56700@172.22.168.249> Supported: em,timer,replaces,path,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,I NFO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.7.20A.000.038 Content-Type: application/x-detect Content-Length: 30 Type= AMD SubType= AUTOMATA Upon detection of the start of voice (i.e., the greeting message of the answering machine), the device sends the following INFO message to the application server: INFO sip:sipp@172.22.2.9:5060 SIP/2.0...
Page 199 Call-ID: 1-29753@172.22.2.9 CSeq: 1 INFO Contact: <sip:56700@172.22.168.249> Supported: em,timer,replaces,path,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,I NFO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.7.20A.000.038 Content-Type: application/x-detect Content-Length: 34 Type= PTT SubType= SPEECH-END The application server sends its message to leave on the answering message.  The following example shows a SIP call flow for event detection and notification of the...
Page 200: 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 201 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 763.
Page 202: Configuring Amd
Mediant 1000B Gateway & E-SBC Performance AMD Detection Sensitivity Success Rate for Live Calls Success Rate for Answering Machine 7 (Best for Live 94.72% 76.14% Calls) Table 14-4: Approximate AMD High Detection Sensitivity - Parameter Suite 1 (Based on North American English) Performance AMD Detection...
Page 203 User's Manual 14. Media  To configure AMD for all calls: Open the DSP Settings page (Setup menu > Signaling & Media tab > Media folder > DSP Settings): From the 'IPMedia Detectors' drop-down list (EnableDSPIPMDetectors), select Enable to enable AMD. Scroll down to the Answer Machine Detector group: Figure 14-13: Configuring AMD Select the AMD algorithm suite:...
Page 204: Enabling Ip-To-Tel Call Disconnection Upon Detection Of Answering Machine
Mediant 1000B Gateway & E-SBC 14.5.2 Enabling IP-to-Tel Call Disconnection upon Detection of Answering Machine The device can disconnect an IP-to-Tel call upon detection of an answering machine on the Tel side. Once detected, the device disconnects the call after the receipt of an ISDN Connect from the Tel side and then sends a SIP BYE message to the IP side to disconnect the call.
Page 205: Configuring Ground- Or Loop-Start Signaling Per Analog Port
User's Manual 14. Media The following procedure describes how to configure AGC using the Web interface:  To configure AGC using the Web interface: Open the DSP Settings page (Setup menu > Signaling & Media tab > Media folder > DSP Settings): Figure 14-15: AGC Parameters Configure the following parameters:...
Page 206: Configuring Dsp Templates
Mediant 1000B Gateway & E-SBC Note: • For ground-start signaling, make sure that the device's chassis houses the FXO G module (and not the regular FXO module). • To support FXO ground-start signaling, set the following additional parameters: √ EnableCurrentDisconnect to 1 √...
Page 207: Dsp Channel Resources For Transcoding
User's Manual 14. Media  To select a DSP Template: Open the General Settings page (Configuration tab > VoIP menu > Media > General Media Settings). Figure 14-17: Defining Single DSP Template in General Settings Page In the 'DSP Version Template Number' field, enter the required DSP Template number.
Page 208: Configuring Media (Srtp) Security
Mediant 1000B Gateway & E-SBC • Set the MediaChannels parameter to the maximum number of required IP media channels, regardless of the module from where the channels are obtained. Note: Setting the MediaChannels parameter to a value that is greater than the available DSP resources that is provided by the MPM module(s) can result in the "stealing"...
Page 209 User's Manual 14. Media The key lifetime field is not supported. However, if it is included in the key it is ignored and the call does not fail. For SBC calls belonging to a specific SIP entity, you can configure the device to remove the lifetime field in the 'a=crypto' attribute (using the IP Profile parameter, IpProfile_SBCRemoveCryptoLifetimeInSDP).
Page 210 Mediant 1000B Gateway & E-SBC  To enable and configure SRTP: Open the Media Security page (Setup menu > Signaling & Media tab > Media folder > Media Security). Figure 14-18: Configuring Media Security From the 'Media Security' drop-down list (EnableMediaSecurity), select Enable to enable SRTP.
Page 211: Services
User's Manual 15. Services Services This section describes configuration for various supported services. 15.1 DHCP Server Functionality The device can serve as a Dynamic Host Configuration Protocol (DHCP) server that assigns and manages IP addresses from a user-defined address pool for DHCP clients. The DHCP server can also be configured to supply additional information to the requesting client such as the IP address of the TFTP server, DNS server, NTP server, and default router (gateway).
Page 212 Mediant 1000B Gateway & E-SBC DHCP Option Code DHCP Option Name Option 2 Time Offset Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following: ...
Page 213 User's Manual 15. Services Click New; the following dialog box appears: Figure 15-1: DHCP Servers Table - Add Dialog Box Configure a DHCP server according to the parameters described in the table below. Click Apply. Table 15-2: DHCP Servers Table Parameter Descriptions Parameter Description General...
Page 214 Mediant 1000B Gateway & E-SBC Parameter Description [DhcpServer_EndIPAddress] to allocate addresses. The default value is 192.168.0.149. Note: The IP address must belong to the same subnet as the associated interface’s IP address and must be "greater or equal" to the starting IP address defined in 'Start IP Address'. Subnet Mask Defines the subnet mask (for IPv4 addresses) for the DHCP client.
Page 215 User's Manual 15. Services Parameter Description The default value is 0.0.0.0. Time Offset Defines the Greenwich Mean Time (GMT) offset (in seconds) that the DHCP server assigns to the DHCP client. The value is time-offset sent in DHCP Option 2 (Time Offset). [DhcpServer_TimeOffset] The valid range is -43200 to 43200.
Page 216: Configuring The Vendor Class Identifier
The VCI is a string that identifies the vendor and functionality of a DHCP client to the DHCP server. For example, Option 60 can show the unique type of hardware (e.g., "AudioCodes 440HD IP Phone") or firmware of the DHCP client. The DHCP server can then differentiate between DHCP clients and process their requests accordingly.
Page 217: Configuring Additional Dhcp Options
User's Manual 15. Services Table 15-3: DHCP Vendor Class Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. dhcp vendor-class <index> Note: Each row must be configured with a unique index. [DhcpVendorClass_Index] DHCP Server Index Associates the VCI table entry with a DHCP server that you configured in ''Configuring the DHCP Server'' on page 211.
Page 218 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-3: DHCP Option Table - Add Dialog Box Configure additional DHCP Options for the DHCP server according to the parameters described in the table below. Click Apply. Table 15-4: DHCP Option Table Parameter Descriptions Parameter Description...
Page 219: Configuring Static Ip Addresses For Dhcp Clients
User's Manual 15. Services Parameter Description IPv4 addresses, each separated by a comma (e.g., 192.168.10.5,192.168.10.20). For hexadecimal values, the value is a hexadecimal string (e.g., c0a80a05). You can also configure the parameter with case-sensitive placeholder strings that are replaced with actual values if the 'Expand Value' parameter (see below) is set to Yes: ...
Page 220: Viewing And Deleting Dhcp Clients
Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-4: DHCP Static IP Table - Add Dialog Box Configure a static IP address for a specific DHCP client according to the parameters described in the table below. Click Apply.
Page 221: Radius-Based Services
User's Manual 15. Services # show network dhcp clients  To view DHCP clients according to IP address: # show network dhcp ip  To view DHCP clients according to MAC address: # show network dhcp mac  To view DHCP clients that have been blacklisted from DHCP implementation (due to duplicated IP addresses in the network, where another device is using the same IP address as the one assigned to the client): # show network dhcp black-list...
Page 222: Configuring Radius Servers
Mediant 1000B Gateway & E-SBC  To enable RADIUS: Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder > Authentication Server). Figure 15-6: Enabling RADIUS Under the RADIUS group, from the 'Enable RADIUS Access Control' drop-down list, select Enable.
Page 223 User's Manual 15. Services servers 0 ip-address 10.4.4.203 auth-port 1812 auth-ha-state "ACTIVE" acc-port 1813 acc-ha-state "ACTIVE" servers 1 ip-address 10.4.4.202 auth-port 1812 auth-ha-state "STANDBY" acc-port 1813 acc-ha-state "STANDBY" Where auth-ha-state and acc-ha-state display the authentication and accounting redundancy status respectively. "ACTIVE" means that the server was used for the last sent authentication or accounting request;...
Page 224: Configuring Interface For Radius Communication
Mediant 1000B Gateway & E-SBC Table 15-6: 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. IP Address Defines the IP address of the RADIUS server (in dotted-decimal notation).
Page 225: Configuring The Radius Vendor Id
User's Manual 15. Services  To configure RADIUS packet retransmission: Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder > Authentication Server). Figure 15-8: Configuring RADIUS Packet Retransmission Under the RADIUS group, do the following: In the 'RADIUS Packets Retransmission' field (RADIUSRetransmission), enter the maximum number of RADIUS retransmissions that the device performs if no response is received from the RADIUS server.
Page 226: Setting Up A Third-Party Radius Server
Mediant 1000B Gateway & E-SBC Management User Accounts'' on page 65). However, you can configure the device to use the Local Users table as a fallback mechanism if the RADIUS server does not respond. When RADIUS authentication is used, the RADIUS server stores the user accounts - usernames, passwords, and access levels (authorization).
Page 227: Configuring Radius-Based User Authentication
RADIUS servers, see ''Configuring Management User Accounts'' on page 65. # 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 228 Mediant 1000B Gateway & E-SBC When implementing Web user access levels, do one of the following: • If the RADIUS server response includes the access level attribute: In the 'RADIUS VSA Access Level Attribute' field, enter the code that indicates the access level attribute in the VSA section of the received RADIUS packet.
Page 229: Securing Radius Communication
User's Manual 15. Services 15.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 230 Mediant 1000B Gateway & E-SBC key (filter), which defines the exact DN to search and one or more attributes whose values must be returned to the device must also be configured. For more information on configuring these attributes and search filters, see ''AD-based Routing for Microsoft Skype for Business'' on page 250.
Page 231: Enabling The Ldap Service
User's Manual 15. Services 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 232: Configuring Ldap Server Groups
Mediant 1000B Gateway & E-SBC 15.3.3 Configuring LDAP Server Groups The LDAP Server Groups table lets you configure up to 41 LDAP Server Groups. An LDAP Server Group is a logical configuration entity that contains up to two LDAP servers. LDAP servers are assigned to LDAP Server Groups in the LDAP Servers table (see ''Configuring LDAP Servers'' on page 234).
Page 233 User's Manual 15. Services Parameter Description Index Defines an index number for the new table row. [LdapServerGroups_Index] Note: Each row must be configured with a unique index. Name Defines an arbitrary name to easily identify the row. name The valid value is a string of up to 20 characters. [LdapServerGroups_Name] Note: Each row must be configured with a unique name.
Page 234: Configuring Ldap Servers
Mediant 1000B Gateway & E-SBC 15.3.4 Configuring LDAP Servers The LDAP Servers table lets you configure up to four LDAP servers. The table defines the address and connectivity settings of the LDAP server. The LDAP server can be configured for SIP-related queries (e.g., routing and manipulation) or LDAP-based management user login authentication and authorization (username-password).
Page 235 User's Manual 15. Services Parameter Description server-group Groups'' on page 232). [LdapConfiguration_Group] Note:  The parameter is mandatory and must be set before configuring the other parameters in the table.  Up to two LDAP servers can be assigned to the same LDAP Server Group.
Page 236 Mediant 1000B Gateway & E-SBC Parameter Description LDAP Server Domain Name Defines the domain name (FQDN) of the LDAP server. The device tries to connect to the LDAP server according to the IP domain-name address listed in the received DNS query. If there is no [LdapConfiguration_LdapConfSer connection to the LDAP server or the connection to the LDAP verDomainName]...
Page 237: Configuring Ldap Dns (Base Paths) Per Ldap Server
User's Manual 15. Services Parameter Description 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 [LdapConfiguration_LdapConfBin during connection and binding to the LDAP server. The DN is dDn] used to uniquely name an AD object.
Page 238: Configuring The Ldap Search Filter Attribute
Mediant 1000B Gateway & E-SBC  To configure an LDAP base path per LDAP server: Open the LDAP Servers table (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Servers). In the table, select the row of the LDAP server for which you want to configure DN base paths, and then click the LDAP Servers Search Based DNs link located below the table;...
Page 239: Configuring Access Level Per Management Groups Attributes
User's Manual 15. Services sAMAccountName that equals "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 234). Therefore, the LDAP response includes only the groups of which the specific user is a member.
Page 240 Mediant 1000B Gateway & E-SBC Group objects represent groups in the LDAP server of which the user is a member. The access level represents the user account's permissions and rights in the device's management interface (e.g., Web and CLI). The access level can either be Monitor, Administrator, or Security Administrator.
Page 241: Configuring The Device's Ldap Cache
User's Manual 15. Services Click New; the following dialog box appears: Figure 15-22: Management LDAP Groups Table - Add Dialog Box Configure a group name(s) with a corresponding access level according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 15-10: Management LDAP Groups Table Parameter Descriptions Parameter Description...
Page 242 Mediant 1000B Gateway & E-SBC The handling of LDAP queries using the device's LDAP cache is shown in the flowchart below: Figure 15-23: LDAP Query Process with Local LDAP Cache If an LDAP query is required for an Attribute of a key that is already cached with that same Attribute, instead of sending a query to the LDAP server, the device uses the cache.
Page 243: Refreshing The Ldap Cache
User's Manual 15. Services Note: • The LDAP Cache feature is applicable only to LDAP-based SIP queries (Control). • The maximum LDAP cache size is 10,000 bytes. • The device can save up to six LDAP Attributes in the cache per user (search LDAP key).
Page 244: Clearing The Ldap Cache
Mediant 1000B Gateway & E-SBC Figure 15-25: LDAP Cache Refresh Flowchart  To refresh the LDAP cache per LDAP Server Group: Open the LDAP Settings page (Setup menu > IP Network tab > RADIUS & LDAP folder > LDAP Settings). Figure 15-26: Refreshing LDAP Cache Under the Cache Actions group, do the following: From the 'LDAP Group Index' drop-down list, select the required LDAP Server...
Page 245: Configuring Local Database For Management User Authentication
User's Manual 15. Services folder > LDAP Settings). Under the Cache Actions group, do the following: From the 'LDAP Group Index' drop-down list, select the required LDAP Server Group (see ''Configuring LDAP Server Groups'' on page 232). Click Clear Group. 15.3.9 Configuring Local Database for Management User Authentication You can configure the device to use the Local Users table (local database) to authenticate...
Page 246: Ldap-Based Login Authentication Example
Mediant 1000B Gateway & E-SBC Click Apply, and then reset the device with a save-to-flash for your settings to take effect. 15.3.10 LDAP-based Login Authentication Example To facilitate your understanding on LDAP entry data structure and how to configure the device to use and obtain information from this LDAP directory, a brief configuration example is described in this section.
Page 247 User's Manual 15. Services  Search Attribute Filter: (sAMAccountName=$). The login username is found based on this attribute (where the attribute's value equals the username): Figure 15-29: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-30: User's memberOf Attribute Version 7.2...
Page 248 Mediant 1000B Gateway & E-SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-31: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
Page 249 User's Manual 15. Services  The search attribute filter based on username is configured by the 'LDAP Authentication Filter' parameter (see ''Configuring the LDAP Search Filter Attribute'' on page 238): Figure 15-34: Configuring Search Attribute Filter  The group management attribute is configured by the 'Management Attribute' parameter in the LDAP Servers table: Figure 15-35: Configuring Management Attribute ...
Page 250: Enabling Ldap Searches For Numbers With Characters
Mediant 1000B Gateway & E-SBC 15.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., 503-823 4567), the LDAP query returns a failed result.
Page 251 User's Manual 15. Services Queried User Domain Query or Query Result Parameter (Attribute) in AD Example MSLDAPPBXNumAttributeName PBX or IP PBX number telephoneNumber= (e.g., "telephoneNumber" - +3233554447 default) MSLDAPOCSNumAttributeName Mediation Server / Skype msRTCSIP- for Business client number Line=john.smith@company.com (e.g., "msRTCSIP-Line") MSLDAPMobileNumAttributeName Mobile number (e.g., mobile=+3247647156...
Page 252 Mediant 1000B Gateway & E-SBC • "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) •...
Page 253: Configuring Ad-Based Routing Rules
User's Manual 15. Services The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 15-37: Querying AD in Skype for Business Environment Note: If you are using the device's local LDAP cache, see ''Configuring the Device's LDAP Cache'' on page 241 for the LDAP query process.
Page 254 Mediant 1000B Gateway & E-SBC  To configure LDAP-based IP routing for Skype for Business: Configure the LDAP server parameters, as described in ''Configuring LDAP Servers'' on page 234. Configure the AD attribute names used in the LDAP query: Open the SIP Definitions General Settings page (Setup menu > Signaling & Media tab >...
Page 255 User's Manual 15. Services Configure a routing rule for routing the initial call (LDAP query) to the LDAP server, by setting the 'Destination Type' field to LDAP for denoting the IP address of the LDAP server. For alternative routing, enable the alternative routing mechanism and configure corresponding SIP reasons for alternative routing.
Page 256: Querying The Ad For Calling Name
Mediant 1000B Gateway & E-SBC  Rule 6: Sends query for original destination number of received call to the LDAP server.  Rule 7: Alternative routing rule that sends the call of original dialed number to IP destination 10.33.45.72. This rule is applied in any of the following cases •...
Page 257: Least Cost Routing
User's Manual 15. Services Note: • The Calling Name Manipulation for Tel-to-IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value. • The feature is applicable only to the Gateway application. 15.4 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how...
Page 258 Mediant 1000B Gateway & E-SBC Table 15-15: Call Cost Comparison between Cost Groups for different Call Durations Total Call Cost per Duration Connection Cost Group Minute Cost Cost 1 Minute 10 Minutes 80.3 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 259: Configuring Lcr
User's Manual 15. Services Routing Index Dest Phone Prefix Destination IP Cost Group x.x.x.x x.x.x.x "B" The device calculates the optimal route in the following index order: 3, 1, 2, and then 4, due to the following logic: • Index 1 - Cost Group "A" has the lowest connection cost and minute cost •...
Page 260: Configuring Cost Groups
Mediant 1000B Gateway & E-SBC Assign Cost Groups to outbound IP routing rules - see ''Assigning Cost Groups to Routing Rules'' on page 262. 15.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).
Page 261 User's Manual 15. Services Parameter Description time of the call is not within a time band configured for the Cost Group, then this default charge per minute is used. 15.4.2.1.1 Configuring Time Bands for Cost Groups The Time Band table lets you configure Time Bands per Cost Group. A Time Band defines a day and time range (e.g., from Saturday 05:00 to Sunday 24:00) and a fixed call connection charge and call rate per minute for this interval.
Page 262: Assigning Cost Groups To Routing Rules
Mediant 1000B Gateway & E-SBC Table 15-17: 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] Start Time Defines the day and time of day from when this time band is applicable.
Page 263  Capture: Recording of signaling and RTP packets, and Syslog. The remote host can be, for example, a Syslog server or AudioCodes SEM. Note: • You can configure only one Remote Web Service for Routing, for Call Status, and for Topology.
Page 264  [3] Capture = Recording of signaling and RTP packets, which can be sent to a remote host, for example, to a Syslog server or AudioCodes SEM. Note:  You can configure only one remote Web service for each of the...
Page 265 User's Manual 15. Services Parameter Description following service types: Routing, Call Status, and Topology Status.  For the Topology Status option to be functional, you must enable the functionality (see ''Enabling Topology Status Services'' on page 269).  The Routing option also includes the Call Status and Topology Status services.
Page 266 Mediant 1000B Gateway & E-SBC Parameter Description [HTTPRemoteServices_LoginN connectivity with the device. eeded]  [0] Disable = Commands are not used.  [1] Enable (default) Username Defines the username for HTTP authentication. rest-user-name The valid value is a string of up to 80 characters. The default is "user".
Page 267: Configuring Remote Http Hosts
User's Manual 15. Services 15.5.1.1 Configuring Remote HTTP Hosts The HTTP Remote Hosts table lets you configure up to 10 remote HTTP hosts per Remote Web Service. The HTTP Remote Hosts table is a "child" of the Remote Web Services table (configured in ''Configuring Remote Web Services'' on page 262).
Page 268 Mediant 1000B Gateway & E-SBC Parameter Description Note:  Each row must be configured with a unique name.  The parameter is mandatory. Address Defines the address (IP address or FQDN) of the remote host. rest-address The valid value is a string of up to 80 characters. [HTTPRemoteHosts_Address] Note: ...
Page 269: Enabling Topology Status Services
15.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 270 Mediant 1000B Gateway & E-SBC This HTTP request-response transaction for the routing path occurs between Routing server and each device in the route path (hops) as the call traverses the devices to its final destination. Each device in the call path connects to the Routing server, which responds with the next hop in the route path.
Page 271 User's Manual 15. Services "additionalRoute" attribute in HTTP Get Route request) to the Routing server, sends a new routing request to the Routing server. The Routing server may respond with a new route destination, thereby implementing alternative routing. Alternatively, it may enable the device to return a failure response to the previous device in the route path chain and respond with an alternative route to this device.
Page 272: Http-Based Proxy Services
 HTTP-based EMS Services for AudioCodes Equipment behind NAT: You can configure the device to act as an HTTP Proxy that enables AudioCodes EMS to manage AudioCodes equipment (such as IP Phones) over HTTP when the equipment is located behind NAT (e.g., in the LAN) and EMS is located in a public domain (e.g., in the WAN).
Page 273: Enabling The Http Proxy Application
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 274 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 15-48: HTTP Interfaces Table - Add Dialog Box Configure an HTTP Interface according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 15-20: HTTP Interfaces Table Parameter Descriptions Parameter Description...
Page 275: Configuring Http Proxy Services
User's Manual 15. Services Parameter Description [HTTPInterface_TLSContext] By default, the default TLS Context (Index 0) is assigned. To configure TLS Contexts, see ''Configuring TLS Certificate Contexts'' on page 103. Note: The parameter is applicable only if the connection protocol is HTTPS (defined using the 'Protocol' parameter, above). Verify Certificate Enables TLS certificate verification when the connection with the proxy service is based on HTTPS.
Page 276: Configuring Http Proxy Hosts
Mediant 1000B Gateway & E-SBC Configure an HTTP Proxy service according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 15-21: HTTP Proxy Services Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row.
Page 277 User's Manual 15. Services Proxy Services'' on page 275). You can configure up to 50 HTTP Proxy hosts; up to 5 HTTP Proxy hosts per HTTP Proxy Service. The following procedure describes how to configure HTTP Remote hosts through the Web interface.
Page 278: Configuring An Http-Based Ems Service
Mediant 1000B Gateway & E-SBC Parameter Description resolution results in multiple IP addresses, the device uses the first available address (i.e., that responds to the keep-alive). Protocol Defines the protocol type.  [0] HTTP (default) protocol  [1] HTTPS [HTTPProxyHost_Protocol] HTTP Port Defines the port of the managed equipment.
Page 279 User's Manual 15. Services Click New; the following dialog box appears: Figure 15-51: EMS Services Table - Add Dialog Box Configure an EMS Service according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 15-23: EMS Services Table Parameter Descriptions Parameter Description...
Page 280: 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 describes the configuration of the device for interoperating between the Skype for Business environment and the E9-1-1 emergency provider.
Page 281: Microsoft Skype For Business And E9-1-1
15. Services The VoIP user dials 9-1-1. AudioCodes' ELIN device eventually sends the call to the emergency service provider over the PSTN or SIP Trunk (PSAP server). The emergency service provider identifies the call is an emergency call and sends it to an E9-1-1 Selective Router in the Emergency Services provider's network.
Page 282 Mediant 1000B Gateway & E-SBC the location of each network element in the enterprise. Immediately after the Skype for Business client registration process or when the operating system detects a network connection change, each Skype for Business client submits a request to the LIS for a location.
Page 283: Adding Elins To The Location Information Server
User's Manual 15. Services ♦ Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) chassis ID and port ID For a Skype for Business client that moves inside the corporate network such as a soft phone on a laptop that connects wirelessly to the corporate network, Skype for Business can determine which subnet the phone belongs to or which WAP / SSID is currently serving the soft-client.
Page 284: Passing Location Information To The Pstn Emergency Provider
Mediant 1000B Gateway & E-SBC Network Columns Element x>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country> <ChassisID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNu Switch mberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectional>,<City> ,<State>,<PostalCode>,<Country> 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>...
Page 285: Audiocodes Elin Device For Skype For Business E9-1-1 Calls To Pstn
Therefore, IP phones, for example, on a specific floor are in the same subnet and therefore, use the same ELIN when dialing 9-1-1. 15.7.3 AudioCodes ELIN Device for Skype for Business E9-1-1 Calls to PSTN Microsoft Mediation Server sends the location information of the E9-1-1 caller in the XML- based PIDF-LO body contained in the SIP INVITE message.
Page 286: Detecting And Handling E9-1-1 Calls
Mediant 1000B Gateway & E-SBC 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. 15.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.
Page 287 User's Manual 15. Services An example of the ELIN database table is shown below: ELIN Time Count Index Call From 4257275678 22:11:52 4258359333 4257275999 22:11:57 4258359444 4257275615 22:12:03 4258359555 4257275616 22:11:45 4258359777 The ELIN table stores this information for a user-defined period (see ''Configuring the E9-1-1 Callback Timeout'' on page 291), starting from when the E9-1-1 call, established with the PSAP, terminates.
Page 288: Pre-Empting Existing Calls For E9-1-1 Calls
Mediant 1000B Gateway & E-SBC a=rtpmap:8 PCMA/8000 a=ptime:20 ------=_NextPart_000_4A6D_01CAB3D6.7519F890 Content-Type: application/pidf+xml Content-ID: <voip_911_user1@contoso.com> <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:bp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ms="urn:schema:Rtc.LIS.msftE911PidfExtn.2008" entity="sip:voip_911_user1@contoso.com"><tuple id="0"><status><gp:geopriv><gp:location- info><ca:civicAddress><ca:country>US</ca:country><ca:A1>WA</ca:A1> <ca:A3>Redmond</ca:A3><ca:RD>163rd</ca:RD><ca:STS>Ave</ca:STS><ca: POD>NE</ca:POD><ca:HNO>3910</ca:HNO><ca:LOC>40/4451</ca:LOC> <ca:NAM>1111-222-333; 1234567890 </ca:NAM> <ca:PC>98052</ca:PC></ca:civicAddress></gp:location- info><gp:usage-rules><bp:retransmission- allowed>true</bp:retransmission-allowed></gp:usage- rules></gp:geopriv><ms:msftE911PidfExtn><ms:ConferenceUri>sip:+142 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-- 15.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 289: Selecting Elin For Multiple Calls Within Same Erl
User's Manual 15. Services number (i.e., ELIN) received from the PSAP to the corresponding E9-1-1 caller's extension number as matched in the ELIN table. The handling of PSAP callbacks by the device is as follows: When the device receives a call from the emergency service provider, it searches the ELIN table for an ELIN that corresponds to the received called party number in the incoming message.
Page 290: Location Based Emergency Routing
Location-based emergency routing is applicable only to the Gateway application. 15.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. 15.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 291: Configuring The E9-1-1 Callback Timeout
User's Manual 15. Services 15.7.4.2 Configuring the E9-1-1 Callback Timeout The PSAP can use the ELIN to call back the E9-1-1 caller within a user-defined time interval (in minutes) from when the initial call established with the PSAP has been terminated.
Page 292: Configuring Sbc Ip-To-Ip Routing Rule For E9-1-1
Mediant 1000B Gateway & E-SBC 15.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.
Page 293 User's Manual 15. Services • Emergency calls received from Manchester office users are routed by the device to the Manchester police department (+44161999). The international code, +44 for England is used for IP routing considerations, but can be omitted depending on your specific deployment. The above scenario is configured as follows: Enable location-based emergency routing, by loading an ini file to the device with the following parameter setting:...
Page 294: Viewing The Elin Table
Mediant 1000B Gateway & E-SBC 15.7.4.6 Viewing the ELIN Table To view the ELIN table:  # show voip e911 ELIN Time Count Index Call From ------------------------------------------------------------ 4257275678 22:11:52 0 4258359333 4257275999 22:11:57 0 4258359444 4257275615 22:12:03 0 4258359555 4257275616 22:11:45 0 4258359777 ------------ Current Time: 22:12:40...
Page 295: 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 296: 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 297: Configuring Quality Of Experience Profiles
User's Manual 16. Quality of Experience 16.2 Configuring Quality of Experience Profiles Quality of Experience Profiles enable you to effectively monitor the quality of voice calls traversing the device in your network. Quality of Experience Profiles define severity thresholds for voice metrics monitored by the device, which if crossed can result in various actions (discussed later in the section).
Page 298  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 295.
Page 299 User's Manual 16. Quality of Experience  Alternative routing based on measured metrics. If a call is rejected because of a crossed threshold, the device generates a SIP 806 response. You can configure this SIP response code as a reason for alternative routing (see ''Configuring SIP Response Codes for Alternative Routing Reasons'' on page 668).
Page 300 Mediant 1000B Gateway & E-SBC Parameter Description  [QOEProfile_SensitivityLevel] [1] Low = Pre-configured low sensitivity thresholds.  [2] Medium = (Default) Pre-configured medium sensitivity thresholds.  [3] High = Pre-configured high sensitivity thresholds. Reporting is done for small fluctuations in parameter values. In the Quality of Experience Profile table, select the row for which you want to configure QoE thresholds, and then click the Quality of Experience Color Rules link located below the table;...
Page 301 User's Manual 16. Quality of Experience Parameter Description are significant.  [2] Medium = (Default) Pre-configured medium sensitivity threshold values.  [3] High = Pre-configured high sensitivity threshold values. Thus, reporting is done for small fluctuations in parameter values. Thresholds Minor Threshold (Yellow) Defines the Minor threshold value, which is the lower threshold located between the Yellow and Green states.
Page 302: Configuring Bandwidth Profiles
Mediant 1000B Gateway & E-SBC Parameter Description  Echo measures the Residual Echo Return Loss (RERL) in Major Hysteresis (Red) Defines the amount of fluctuation (hysteresis) from the Major threshold, configured by the 'Major Threshold (Red)' parameter major-hysteresis-red in order for the threshold to be considered as crossed. The [QOEColorRules_MajorHysteresis] hysteresis is used only to determine threshold crossings from Red to Yellow.
Page 303 User's Manual 16. Quality of Experience bandwidth threshold. When bandwidth goes over the threshold, the device considers it a Red state (Major alarm severity); when it goes below the threshold, it considers it a Yellow state (Minor alarm severity). The device also uses hysteresis to determine whether the threshold has indeed being crossed.
Page 304 Mediant 1000B Gateway & E-SBC The following procedure describes how to configure Bandwidth Profiles through the Web interface. You can also configure it through ini file (BWProfile) or CLI (configure voip > qoe bw-profile).  To configure a Bandwidth Profile: Open the Bandwidth Profile table (Setup menu >...
Page 305 User's Manual 16. Quality of Experience Parameter Description Ingress Video Bandwidth Defines the major (total) threshold for incoming video traffic (in Kbps). ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the major (total) threshold for video and audio outgoing bandwidth (in Kbps). total-egress-bandwidth [BWProfile_TotalEgressBandwidth] Total Ingress Bandwidth...
Page 306: Configuring Quality Of Service Rules
Mediant 1000B Gateway & E-SBC 16.4 Configuring Quality of Service Rules The Quality of Service Rules table lets you configure up to 510 Quality of Service rules. A Quality of Service rule defines an action to perform when the threshold (major or minor) of a specific performance monitoring call metric is crossed for a specific IP Group.
Page 307 User's Manual 16. Quality of Experience Click New; the following dialog box appears: Figure 16-7: Quality of Service Rules Table - Dialog Box Configure a rule according to the parameters described in the table below. Click Apply, and then reset the device with a save-to-flash for your settings to take effect.
Page 308 Mediant 1000B Gateway & E-SBC Parameter Description to any value. Action Rule Action Defines the action to be done if the rule is matched.  rule-action [0] Reject Calls = (Default) New calls destined to the specified IP Group are rejected for a user-defined duration. To configure [QualityOfServiceRules_RuleActi the duration, use the 'Calls Reject Duration' parameter (see below).
Page 309: Control Network
User's Manual 17. Control Network Control Network This section describes configuration of the network at the SIP control level. 17.1 Configuring Media Realms The Media Realms table lets you configure a pool of up to 64 SIP media interfaces, termed Media Realms.
Page 310 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-1: Media Realms Table - Add Dialog Box Configure the Media Realm according to the parameters described in the table below. Click Apply. Table 17-1: Media Realms table Parameter Descriptions Parameter Description General...
Page 311 User's Manual 17. Control Network Parameter Description ipv6if By default, no value is defined. [CpMediaRealm_IPv6IF] To configure IP network interfaces, see Configuring IP Network Interfaces on page 135. Port Range Start Defines the starting port for the range of media interface UDP ports.
Page 312: Configuring Remote Media Subnets
Mediant 1000B Gateway & E-SBC Parameter Description For more information on local UDP port range, see ''Configuring RTP Base UDP Port'' on page 193. Default Media Realm Defines the Media Realm as the default Media Realm. The default Media Realm is used for SIP Interfaces and IP Groups is-default for which you have not assigned a Media Realm.
Page 313 User's Manual 17. Control Network The figure below illustrates an example for implementing Remote Media Subnets. IP Group #2 represents a SIP Trunk which routes international (USA and India) and local calls. As international calls are typically more prone to higher delay than local calls, different Quality of Experience Profiles are assigned to them.
Page 314 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-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 17-2: Remote Media Subnet Table Parameter Descriptions Parameter Description Index...
Page 315: Configuring Media Realm Extensions
User's Manual 17. Control Network Parameter Description Quality of Experience Profiles'' on page 297. BW Profile Assigns a Bandwidth Profile to the Remote Media Subnet. bw-profile By default, no value is defined. [RemoteMediaSubnet_BWProfileName] To configure Bandwidth Profiles, see ''Configuring Bandwidth Profiles'' on page 302. 17.1.2 Configuring Media Realm Extensions The Media Realm Extension table lets you configure 2 Media Realm Extensions.
Page 316 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-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 17-3: Media Realm Extension Table Parameter Descriptions Parameter Description Index...
Page 317: Configuring Srds
User's Manual 17. Control Network Parameter Description [MediaRealmExtension_PortRangeEnd] ports for the Media Realm Extension. Note: It is unnecessary to configure the parameter. The device automatically populates the parameter with a value, calculated by the summation of the 'Number of Media Session Legs' parameter (multiplied by the port chunk size) and the 'Port Range Start' parameter.
Page 318 Mediant 1000B Gateway & E-SBC Interface would represent a specific Layer-3 network (IP PBX, SIP Trunk, or far-end users) in your environment. The following figure provides an example of such a deployment: Figure 17-6: Deployment using a Single SRD Note: •...
Page 319 User's Manual 17. Control Network The following procedure describes how to configure SRDs through the Web interface. You can also configure it through ini file (SRD) or CLI (configure voip > srd).  To configure an SRD: Open the SRDs table (Setup menu > Signaling & Media tab > Core Entities folder > SRDs).
Page 320 Mediant 1000B Gateway & E-SBC Parameter Description SBC Operation Mode Defines the device's operational mode for the SRD.  sbc-operation-mode [0] B2BUA = (Default) Device operates as a back-to-back user agent (B2BUA), changing the call identifiers and headers between the [SRD_SBCOperationMod inbound and outbound legs.
Page 321 User's Manual 17. Control Network Parameter Description User Security Mode Defines the blocking (reject) policy for incoming SIP dialog-initiating requests (e.g., INVITE messages) from registered and unregistered users block-un-reg-users belonging to the SRD. [SRD_BlockUnRegUsers]  [0] Accept All = (Default) Accepts requests from registered and unregistered users.
Page 322: Filtering Tables In Web Interface By Srd
Mediant 1000B Gateway & E-SBC Parameter Description registers the user in its registration database. Note:  Regardless of the parameter, the device always accepts registration refreshes from users that are already registered in its database.  For a SIP Interface that is associated with the SRD, if the corresponding parameter in the SIP Interfaces table (SIPInterface_EnableUnAuthenticatedRegistrations) is configured to Disable or Enable, the parameter in the SRD is ignored for calls...
Page 323: Multiple Srds For Multi-Tenant Deployments
User's Manual 17. Control Network 17.2.2 Multiple SRDs for Multi-tenant Deployments The device can be deployed in a multi-tenant architecture, serving multiple customers (tenants) from a single, shared physical entity. The device's multi-tenant feature is fully scalable, offering almost “non-bleeding” partition per tenant, whereby users of one tenant can’t infringe on the space of users of another tenant.
Page 324: Cloning Srds
Mediant 1000B Gateway & E-SBC and typically, their configuration is not required. Isolated SRDs are more relevant only when each tenant requires its own dedicated Routing Policy to create separate, dedicated routing "tables"; for all other scenarios, SRDs can be Shared. For more information on Routing Policies, see ''Configuring SBC Routing Policy Rules'' on page 670.
Page 325 User's Manual 17. Control Network 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. When an SRD is cloned, the device adds the new SRD clone to the next available index row in the SRDs table.
Page 326: Color-Coding Of Srds In Web Interface
Mediant 1000B Gateway & E-SBC 17.2.4 Color-Coding of SRDs in Web Interface To easily identify your configured SRDs, the Web interface displays each SRD in a unique color. The color is automatically and randomly assigned to new SRDs and is displayed in a box alongside the name of the SRD in tables where the SRD is configured or assigned.
Page 327 User's Manual 17. Control Network deployments (except multi-tenant deployments), your SRD represents your entire network and thus, only one SRD is required. The device provides a default SRD and in such scenarios where only a single SRD is required, your SIP Interfaces are automatically assigned to the default SRD.
Page 328 Mediant 1000B Gateway & E-SBC Configure a SIP Interface according to the parameters described in the table below. Click Apply. Table 17-5: SIP Interfaces table Parameter Descriptions Parameter Description Assigns an SRD to the SIP Interface. If only one SRD is configured in the SRDs table, the SRD is assigned to the SIP Interface by default.
Page 329 User's Manual 17. Control Network Parameter Description Network Interface Assigns a Control-type IP network interface to the SIP Interface. network-interface By default, no value is defined. [SIPInterface_NetworkInterfac To configure network interfaces, see ''Configuring IP Network Interfaces'' on page 135. Note: The parameter is mandatory. Application Type Defines the application for which the SIP Interface is used.
Page 330 Mediant 1000B Gateway & E-SBC Parameter Description [SIPInterface_TCPKeepaliveE check that the connection to the IP entity is available. nable]  [0] Disable (default)  [1] Enable Note: To configure TCP keepalive, use the following ini file parameters: TCPKeepAliveTime, TCPKeepAliveInterval, and TCPKeepAliveRetry.
Page 331 User's Manual 17. Control Network Parameter Description assigned to the SIP Interface is applied first.  The parameter is applicable only to the SBC application. Media Media Realm Assigns a Media Realm to the SIP Interface. media-realm-name By default, no value is defined. [SIPInterface_MediaRealm] To configure Media Realms, see ''Configuring Media Realms'' on page 309.
Page 332 Mediant 1000B Gateway & E-SBC Parameter Description Context is configured for the Proxy Set associated with the call.  To configure TLS Contexts, see ''Configuring SSL/TLS Certificates'' on page 103. TLS Mutual Authentication Enables TLS mutual authentication for the SIP Interface (when the device acts as a server).
Page 333: Configuring Ip Groups
User's Manual 17. Control Network Parameter Description the SIP Interface. Enable Un-Authenticated Enables the device to accept REGISTER requests and register them Registrations in its registration database from new users that have not been authenticated by a proxy/registrar server (due to proxy down) and enable-un-auth-registrs thus, re-routed to a User-type IP Group.
Page 334 Mediant 1000B Gateway & E-SBC the 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.
Page 335 User's Manual 17. Control Network Configure an IP Group according to to the parameters described in the table below. Click Apply. Table 17-6: IP Groups Table Parameter Descriptions Parameter Description Assigns an SRD to the IP Group. srd-name If only one SRD is configured in the SRDs table, the SRD is assigned by default.
Page 336 Mediant 1000B Gateway & E-SBC Parameter Description The address is configured by the Proxy Set that is associated with the IP Group.  [1] User = Represents a group of users such as IP phones and softphones where their location is dynamically obtained by the device when REGISTER requests and responses traverse (or are terminated) by the device.
Page 337 User's Manual 17. Control Network Parameter Description [IPGroup_ProxySetName] To configure Proxy Sets, see ''Configuring Proxy Sets'' on page 346. Note:  For the Gateway application: IP Group ID 0 cannot be associated with Proxy Set ID 0.  The Proxy Set must be associated with the same SRD as that assigned to the IP Group.
Page 338 Mediant 1000B Gateway & E-SBC Parameter Description Note:  If the parameter is not configured, the value of the global parameter, ProxyName is used instead (see ''Configuring Proxy and Registration Parameters'' on page 365).  The parameter overrides inbound message manipulation rules that manipulate the host name in Request-URI, To, and/or From SIP headers.
Page 339 User's Manual 17. Control Network Parameter Description of the Proxy Set that is associated with the IP Group (see ''Configuring Proxy Sets'' on page 346).  If the Proxy Set is configured with multiple proxies (addresses) and at least one of them is "alive", the displayed status is "Connected". To view the connected proxy server, see ''Viewing Call Routing Status'' on page 824.
Page 340 Mediant 1000B Gateway & E-SBC Parameter Description (B2BUA), changing the call identifiers and headers between the inbound and outbound legs.  [1] Call Stateful Proxy = Device operates as a Stateful Proxy, passing the SIP message transparently between inbound and outbound legs.
Page 341 User's Manual 17. Control Network Parameter Description always-use-source-addr a SIP dialog, to the source IP address received in the previous SIP message packet. This feature is especially useful in scenarios where [IPGroup_AlwaysUseSource the IP Group endpoints are located behind a NAT firewall (and the Addr] device is unable to identify this using its regular NAT mechanism).
Page 342 Mediant 1000B Gateway & E-SBC Parameter Description  [0] From  [1] To  [2] Request-URI  [3] P-Asserted - First Header  [4] P-Asserted - Second Header  [5] P-Preferred  [6] Route  [7] Diversion  [8] P-Associated-URI ...
Page 343 User's Manual 17. Control Network Parameter Description Keep Original Call-ID Enables the device to use the same call identification (SIP Call-ID header value) received in incoming messages for the call identification sbc-keep-call-id in outgoing messages. The call identification value is contained in the [IPGroup_SBCKeepOriginal SIP Call-ID header.
Page 344 Mediant 1000B Gateway & E-SBC Parameter Description Manipulation Set (see the IPGroup_OutboundManSet parameter), when the IP Group is the destination of the call. Outbound Message Assigns a Message Manipulation Set (rule) to the IP Group for SIP Manipulation Set message manipulation on the outbound leg. outbound-mesg- By default, no value is defined.
Page 345 User's Manual 17. Control Network Parameter Description username and password) according to one of the following: 1)Account configured in the Accounts table (only if authenticating Server-type IP Group), 2) global username and password parameters (only if authenticating Server-type IP Group), 3) User Information file, or 4) sends request to users requesting credentials (only if authenticating User-type IP Group).
Page 346: Configuring Proxy Sets
Mediant 1000B Gateway & E-SBC Parameter Description  [-1] = Not Configured (Default)  [0] Standard = INVITE messages that are generated as a result of Transfer or Redirect are sent directly to the URI, according to the Refer-To header in the REFER message or Contact header in the 3xx response.
Page 347 User's Manual 17. Control Network balancing and redundancy (Proxy Hot-Swap feature) between multiple servers. If you configure the address as an FQDN, you can configure the method (A-record DNS, SRV, or NAPTR) for resolving the domain name to an IP address. The device supports up to 30 DNS-resolved IP addresses.
Page 348 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 17-10: Proxy Sets Table - Add Dialog Box Configure a Proxy Set according to the parameters described in the table below. Click Apply. Select the index row of the Proxy Set that you added, and then click the Proxy Address link located below the table;...
Page 349 User's Manual 17. Control Network Parameter Description  To configure SRDs, see Configuring SRDs on page 317. General Index Defines an index number for the new table row. configure voip > voip-network Note: Each row must be configured with a unique index. proxy-set [ProxySet_Index] Name...
Page 350 Mediant 1000B Gateway & E-SBC Parameter Description to this Proxy Set fails, the TLS Context is not used. Instead, the device uses the TLS Context configured for the SIP Interface (see ''Configuring SIP Interfaces'' on page 326) used for the call; otherwise, the default TLS Context (ID 0) is used.
Page 351 User's Manual 17. Control Network Parameter Description Keep-Alive Failure Responses Defines SIP response codes that if any is received in response to a keep-alive message using SIP OPTIONS, the device considers the keepalive-fail-resp proxy as down. [ProxySet_KeepAliveFailureRes Up to three response codes can be configured, where each code is separated by a comma (e.g., 407,404).
Page 352 Mediant 1000B Gateway & E-SBC Parameter Description  proxy-load-balancing-method [0] Disable = (Default) Disables proxy load balancing.  [1] Round Robin = A list of all possible proxy IP addresses is [ProxySet_ProxyLoadBalancing compiled. This list includes all IP addresses of the Proxy Set Method] after DNS resolutions (including NAPTR and SRV, if configured).
Page 353 User's Manual 17. Control Network Parameter Description address, the device selects the matching Proxy Set in the following order:  Selects the Proxy Set whose IP address, port, and transport type match the source of the incoming dialog (regardless of the settings of this parameter).
Page 354 Mediant 1000B Gateway & E-SBC Parameter Description Note: An SRV query can return up to four host names. For each host name, the subsequent DNS A-record query can resolve into up to 15 IP addresses. However, the device supports up to 30 DNS-resolved IP addresses.
Page 355: Building And Viewing Sip Entities In Topology View
User's Manual 17. Control Network 17.6 Building and Viewing SIP Entities in Topology View The Topology view lets you easily build and view your main SIP entities, including trunks and ports (analog and digital), Trunk Groups, IP Groups, SIP Interfaces, and Media Realms.
Page 356 Mediant 1000B Gateway & E-SBC Item # Description name. You can use demarcation to visually separate your voice network to provide a clearer understanding of your topology. This is especially useful for IP Groups, SIP Interfaces, and Media Realms, where you can display them on the top or bottom border of the Topology view (as shown in the figure below for callouts #1 and #2, respectively).
Page 357 User's Manual 17. Control Network Item # Description  Show List: Opens the SIP Interfaces table.  Delete: Opens the SIP Interfaces table where you are prompted to confirm deletion of the SIP Interface. To add a SIP Interface, do the following: Click the Add SIP Interface plus icon.
Page 358 Mediant 1000B Gateway & E-SBC Item # Description For more information on configuring Media Realms, see ''Configuring Media Realms'' on page 309. 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): If you hover your mouse over the icon, a pop-up appears displaying the following basic information (example):...
Page 359 User's Manual 17. Control Network Item # Description  To support the connectivity status feature, you must enable the keep-alive mechanism for the Proxy Set that is associated with the IP Group (see ''Configuring Proxy Sets'' on page 346).  The green-color state also applies to scenarios where the device rejects calls with the IP Group due to low QoE (e.g., low MOS), despite connectivity.
Page 360 Mediant 1000B Gateway & E-SBC Item # Description For more information on configuring trunk settings, see Configuring Trunk Settings on page 447. Links to Web pages relating to commonly required Gateway configuration:  Number Manipulation: Opens the Destination Phone Number Manipulation for IP-to-Tel Calls table where you can configure destination phone number manipulation rules for IP-to-Tel calls (see Configuring Number Manipulation Tables on page 503).
Page 361: Sip Definitions
User's Manual 18. SIP Definitions SIP Definitions This section describes configuration of various SIP-related functionalities. 18.1 Configuring Registration Accounts The Accounts table lets you configure up to 102 Accounts. An Account defines registration information for registering and authenticating (digest) Trunk Groups (e.g., PBX) or IP Groups (e.g., IP PBX) with a "serving"...
Page 362 Mediant 1000B Gateway & E-SBC 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 363 User's Manual 18. SIP Definitions Parameter Description Application Type Defines the application type:  application-type [0] GW = (Default) Gateway application.  [2] SBC = SBC application. [Account_ApplicationType] Served IP Group Defines the IP Group (e.g., IP-PBX) that you want to register and/or authenticate upon its behalf.
Page 364: Regular Registration Mode
Mediant 1000B Gateway & E-SBC Parameter Description Registration for Multiple Phone Numbers using GIN'' on page 364. Note:  Gateway application: To enable registration, you also need to set the 'Registration Mode' parameter to Per Account in the Trunk Group Settings table (see Configuring Trunk Group Settings on page 467).
Page 365: Configuring Proxy And Registration Parameters
User's Manual 18. SIP Definitions contact address on behalf of each of these. Rather than performing a separate registration procedure for each user agents, GIN registration mode does multiple registrations using a single REGISTER transaction. According to this mechanism, the PBX delivers to the service provider in the Contact header field of a REGISTER request a template from which the service provider can construct contact URIs for each of the AORs assigned to the PBX and thus, can register these contact URIs within its location service.
Page 366: Sip Message Authentication Example
Mediant 1000B Gateway & E-SBC ''Configuration Parameters Reference'' on page 927. To configure Proxy servers (Proxy Sets), see ''Configuring Proxy Sets'' on page 346. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see ''Viewing Registration Status'' on page 825. ...
Page 367 • 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 368: Configuring Sip Message Manipulation
Mediant 1000B Gateway & E-SBC Authorization: Digest, username: 122, realm="audiocodes.com”, nonce="11432d6bce58ddf02e3b5e1c77c010d2", uri=”10.2.2.222”, response=“b9c45d0234a5abf5ddf5c704029b38cf” Upon receiving this request and if accepted by the Proxy, the Proxy returns a 200 OK response, completing the registration transaction: SIP/2.0 200 OK Via: SIP/2.0/UDP 10.1.1.200 From: <sip: 122@10.1.1.200>;tag=1c23940...
Page 369 User's Manual 18. SIP Definitions • Manipulating Inbound SIP INVITE Messages: Message manipulation can be applied only to all inbound calls (not specific calls). This is done by assigning a Manipulation Set ID to the "global" ini file parameter, GWInboundManipulationSet. •...
Page 370 Mediant 1000B Gateway & E-SBC The figure below illustrates a SIP message manipulation example: Figure 18-2: SIP Header Manipulation Example User's Manual Document #: LTRT-27045...
Page 371 User's Manual 18. SIP Definitions 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 372 Mediant 1000B Gateway & E-SBC Configure a Message Manipulation rule according to the parameters described in the table below. Click Apply. An example of configured message manipulation rules are shown in the figure below: Figure 18-4: Example of Configured Message Manipulation Rules ...
Page 373 User's Manual 18. SIP Definitions Parameter Description 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. Match Message Type Defines the SIP message type that you want to manipulate.
Page 374: Configuring Sip Message Policy Rules
Mediant 1000B Gateway & E-SBC Parameter Description action-value The default value is a string (case-insensitive) in the following syntax:  [MessageManipulations_Acti string/<message-element>/<call-param> + onValue]  string/<message-element>/<call-param> For example:  'itsp.com'  header.from.url.user  param.call.dst.user  param.call.dst.host + '.com'  param.call.src.user + '<' + header.from.url.user + '@' + header.p- asserted-id.url.host + '>' Note: Only single quotation marks must be used.
Page 375 User's Manual 18. SIP Definitions Manipulation folder > Message Policies). Click New; the following dialog box appears: Figure 18-5: Message Policies Table - Add Dialog Box Configure a Message Policy rule according to the parameters described in the table below. Click Apply.
Page 376 Mediant 1000B Gateway & E-SBC Parameter Description max-body-length is the value of the Content-Length header. [MessagePolicy_MaxBodyLength] The valid value is up to 1,024 characters. The default is 1,024. Max Num Headers Defines the maximum number of SIP headers. max-num-headers The valid value is any number up to 32. The default is [MessagePolicy_MaxNumHeaders] Note: The device supports up to 20 SIP Record-Route headers that can be received in a SIP INVITE request...
Page 377: Configuring Call Setup Rules
User's Manual 18. SIP Definitions Parameter Description SIP body is allowed; the others are rejected. Malicious Signature Malicious Signature Database Enables the use of the Malicious Signature database (signature-based detection). signature-db-enable  [0] Disable (default) [MessagePolicy_UseMaliciousSignatureDB]  [1] Enable To configure Malicious Signatures, see ''Configuring Malicious Signatures'' on page 701.
Page 378 Mediant 1000B Gateway & E-SBC matching IP-to-IP Routing rule. You can also use Call Setup rules for complex routing schemes by using multiple Dial Plan tags. This is typically required when the source and/or destination of the call needs to be categorized with more than one characteristics.
Page 379 User's Manual 18. SIP Definitions Click New; the following dialog box appears: Figure 18-6: Call Setup Rules Table - Add Dialog Box Configure a Call Setup rule according to the parameters described in the table below. Click Apply, and then save your settings to flash memory. Table 18-4: Call Setup Rules Parameter Descriptions Parameter Description...
Page 380 Mediant 1000B Gateway & E-SBC Parameter Description To configure the search key, use the 'Search Key' parameter (see below). Note: The parameter is applicable only if the 'Query Type' parameter is configured to any value other than None. Search Key Defines the key to query.
Page 381 User's Manual 18. SIP Definitions Parameter Description  LDAP:  ldap.attr.mobile exists (if Attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (if called number is the same as the number in the Attribute "msRTCSIP-PrivateLine")  ldap.found !exists (if LDAP record not found) ...
Page 382: Call Setup Rule Examples
Mediant 1000B Gateway & E-SBC Parameter Description Action Value Defines a value that you want to use in the action. action-value The valid value is a string of up to 300 characters (case- insensitive). [CallSetupRules_ActionValue] Examples:  '+9723976'+ldap.attr.alternateNumber  '9764000' ...
Page 383 User's Manual 18. SIP Definitions ♦ 'Search Key': ‘telephoneNumber=’ + param.call.src.user ♦ 'Attributes to Get': displayName ♦ 'Row Role': Use Current Condition ♦ 'Condition': ldap.attr. displayName exists ♦ 'Action Subject': param.call.src.name ♦ 'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName •...
Page 384 Mediant 1000B Gateway & E-SBC ♦ 'Query Type': LDAP ♦ 'Query Target': LDAP-DC-CORP ♦ 'Search Key': 'telephoneNumber='+param.call.dst.user ♦ 'Attributes to Get': ofiSBCRouting ♦ 'Row Role': Use Current Condition ♦ 'Condition': ldap.found exists ♦ 'Action Subject': dsttags ♦ 'Action Type': Modify ♦...
Page 385: Coders And Profiles
For supported audio coders, see ''Supported Audio Coders'' on page 387. • Some coders are license-dependent 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 386 Mediant 1000B Gateway & E-SBC The following procedure describes how to configure the Coder Groups table through the Web interface. You can also configure it through ini file (AudioCodersGroups and AudioCoders) or CLI (configure voip > coders-and-profiles audio-coders-groups).  To configure a Coder Group: Open the Coder Groups table (Setup menu >...
Page 387: Supported Audio Coders
User's Manual 19. Coders and Profiles Parameter Description Payload Type Defines the payload type if the payload type (i.e., format of the RTP payload) for the coder is dynamic. For payload types, see payload-type ''Supported Audio Coders'' on page 387. [AudioCoders_PayloadType] Note: GSM-FR and MS-GSM coders use Payload Type 3.
Page 388 Mediant 1000B Gateway & E-SBC 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 g711u-law-vbd (default 110) [24] G.722 20 (default), 40, 60, 80, [90] 64 (default)
Page 389: Configuring Allowed Audio Coder Groups
User's Manual 19. Coders and Profiles 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   [91] Variable [0] Disable EVRC 20 (default), 40, 60, 80,...
Page 390 Mediant 1000B Gateway & E-SBC To apply an Allowed Audio Coders Group for restricting coders to a SIP entity: Configure an Allowed Audio Coders Group in the Allowed Audio Coders Groups table (see description below). In the IP Profile associated with the SIP entity (see ''Configuring IP Profiles'' on page 393): •...
Page 391 User's Manual 19. Coders and Profiles Click New; the following dialog box appears: Figure 19-3: Allowed Audio Coders Table - Add Dialog Box Configure coders for the Allowed Audio Coders Group according to the parameters described in the table below. Click Apply.
Page 392: Configuring Allowed Video Coder Groups
Mediant 1000B Gateway & E-SBC 19.3 Configuring Allowed Video Coder Groups The Allowed Video Coders Groups table lets you configure up to four Allowed Video Coders Groups for SBC calls. Each Allowed Video Coders Group can be configured with up to 10 coders. An Allowed Video Coders Group defines a list of video coders that can be used when forwarding video streams to a specific SIP entity.
Page 393: Configuring Ip Profiles
User's Manual 19. Coders and Profiles located below the table; the Allowed Video Coders table opens. Click New; the following dialog box appears: Figure 19-5: Allowed Video Coders Table - Add Dialog Box Configure coders for the Allowed Video Coders Group according to the parameters described in the table below.
Page 394 Mediant 1000B Gateway & E-SBC when the device interworks between different IP entities, each of which may require different handling by the device. This can include, for example, transcoding or even transrating (of packetization time). For example, if a specific IP entity uses the G.711 coder only, you can configure an IP Profile with G.711 for this IP entity.
Page 395 User's Manual 19. Coders and Profiles Click New; the following dialog box appears: Figure 19-6: IP Profiles Table - Add Dialog Box Configure an IP Profile according to the parameters described in the table below. Click Apply. Table 19-5: IP Profiles Table Parameter Descriptions Parameter Description General...
Page 396 Mediant 1000B Gateway & E-SBC Parameter Description  At least one supported SDP "crypto" attribute and parameters.  EnableMediaSecurity must be set to 1. If one of the above transcoding prerequisites is not met, then:  any value other than “As is” is discarded. ...
Page 397 User's Manual 19. Coders and Profiles Parameter Description ^31|1:1 a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:bnuYZnMxSfUiGitviWJZmzr7OF3AiRO0l5Vnh0kH|2 The first crypto line includes the MKI parameter "1:1". In the 200 OK response, the device selects one of the crypto lines (i.e., '2' or '3'). Typically, it selects the first line that supports the crypto suite. However, for SRTP-to-SRTP in SBC sessions, it can be determined by the remote side on the outgoing leg.
Page 398 Mediant 1000B Gateway & E-SBC Parameter Description re-key generation, one-way voice may occur.  The corresponding global parameter is ResetSRTPStateUponRekey. Generate SRTP Keys Mode Enables the device to generate a new SRTP key upon receipt of a re-INVITE with the SIP entity associated with the IP Profile. generate-srtp-keys ...
Page 399 User's Manual 19. Coders and Profiles Parameter Description 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. When the SIP entity initiates an [IpProfile_SBCRemoteMultiple INVITE that is subsequently forked (for example, by a proxy server) EarlyDialogs]...
Page 400 Mediant 1000B Gateway & E-SBC Parameter Description  [0] Disable = (Default) Device always sends the same SDP answer, which is based on the first received answer that it sent to the SIP entity, for all forked responses (even if 'Forking Handling Mode' is Sequential), and thus, may result in transcoding.
Page 401 User's Manual 19. Coders and Profiles Parameter Description packets transparently (RTP-to-RTP), without processing them.  [1] Force = Transcoding is always done on the outgoing leg. The device interworks the media for the SIP entity (as both legs have different media capabilities), by implementing DSP transcoding. This enables the device to receive capabilities that are not negotiated between the SIP entities.
Page 402 Mediant 1000B Gateway & E-SBC Parameter Description Preference. Note:  The parameter is applicable only if Allowed coders are assigned to the IP Profile (see the 'Allowed Audio Coders' or 'Allowed Video Coders' parameters).  For more information on the Allowed Coders feature, see Restricting Coders on page 618.
Page 403 User's Manual 19. Coders and Profiles Parameter Description Note:  If the device interworks between different DTMF methods and one of the methods is in-band DTMF packets (RFC 2833), detection and generation of DTMF methods requires DSP resources. RFC 2833 DTMF Payload Defines the payload type of DTMF digits for the SIP entity associated Type with the IP Profile.
Page 404 Mediant 1000B Gateway & E-SBC Parameter Description  [2] Remove = Disable silence suppression for each relevant coder listed in the SDP. RTP Redundancy Mode Enables interworking RTP redundancy negotiation support between SIP entities in the SDP offer-answer exchange (according to RFC sbc-rtp-red-behav 2198).
Page 405  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. SDP Handle RTCP Enables the interworking of the RTCP attribute, 'a=rtcp' (RTCP) in the SDP, for the SIP entity associated with the IP Profile. The RTCP...
Page 406 Mediant 1000B Gateway & E-SBC Parameter Description according to RFC 5124, during RTP profile negotiation between two communicating SIP entities. RFC 5124 defines an RTP profile (S)AVPF for (secure) real-time communications to provide timely feedback from the receivers to a sender. For more information on RFC 5124, see http://tools.ietf.org/html/rfc5124.
Page 407 User's Manual 19. Coders and Profiles Parameter Description jitter-buffer-optimization-factor The valid range is 0 to 12. The default factor is 10. [IpProfile_JitterBufOptFactor] For more information on Jitter Buffer, see Configuring the Dynamic Jitter Buffer on page 189. Note:  For data (fax and modem) calls, set the parameter to 12. ...
Page 408 Mediant 1000B Gateway & E-SBC Parameter Description PRACK Mode Defines the device's handling of SIP PRACK messages for the SIP entity associated with the IP Profile. sbc-prack-mode  [1] Optional = PRACK is optional. If required, the device performs [IpProfile_SbcPrackMode] the PRACK process on behalf of the SIP entity.
Page 409 User's Manual 19. Coders and Profiles Parameter Description device does not interfere, but maintains an independent timer for each leg to monitor the session. If the session is not refreshed on time, the device disconnects the call.  [2] Not Supported = The device does not allow a session timer with this SIP entity.
Page 410 Mediant 1000B Gateway & E-SBC Parameter Description  Call State-full Proxy: Device operates as if the parameter is set to 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 to the SIP entity.
Page 411 User's Manual 19. Coders and Profiles Parameter Description SUBSCRIBE and REFER messages. Keep User-Agent Header Enables interworking SIP User-Agent headers between SIP entities. The parameter defines the device's handling of User-Agent headers sbc-keep-user-agent for response/request messages sent to the SIP entity associated [IpProfile_SBCKeepUserAgen with the IP Profile.
Page 412 Mediant 1000B Gateway & E-SBC Parameter Description 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. The valid range is 0 to 2,000,000. The default is 0. If configured to 0, the Expires header's value received in the user’s REGISTER request remains unchanged.
Page 413 User's Manual 19. Coders and Profiles Parameter Description  sbc-rmt-refer-behavior [0] Regular = (Default) Refer-To header is unchanged and the device forwards the REFER as is. [IpProfile_SBCRemoteReferB  [1] Database URL = Changes the Refer-To header so that the re- ehavior] routed INVITE is sent through the SBC: Before forwarding the REFER request, the device changes...
Page 414 Mediant 1000B Gateway & E-SBC Parameter Description connecting A to C, and disconnecting the call between A and B, by sending a SIP BYE request to B. Note that if media transcoding is required, the device sends an INVITE to C on behalf of A with a new SDP offer.
Page 415 User's Manual 19. Coders and Profiles Parameter Description (i.e.,transparent handling).  [1] Database URL = The device changes the Contact header so that the re-route request is sent through the device. The device changes the URI in the Contact header of the received SIP 3xx response to its own URI and adds a special user prefix ("T~&R_”), which is then sent to the FEU.
Page 416 Mediant 1000B Gateway & E-SBC Parameter Description does not play a held tone to the held party (and assumes that the initiator of the call hold plays the held tone). Note: The device plays a held tone only if the 'SBC Play Held Tone' parameter is set to Yes.
Page 417 User's Manual 19. Coders and Profiles Parameter Description parameter).  [1] Single coder = (Default) Use only one coder. If the incoming answer (from the called "fax") includes a coder that matches a coder match between the incoming offer coders (from the calling "fax") and the coders of the selected Coder Group (SBCFaxCodersGroupID, then the device uses this coder.
Page 418 Mediant 1000B Gateway & E-SBC Parameter Description  [0] Ignore = The call is maintained despite no media and is released when signaling ends the call (i.e., SIP BYE).  [1] Disconnect = (Default) The device ends the call.  [2] Reroute = (SBC application only) The device ends the call and searches the IP-to-IP Routing table for a matching rule and if found, generates a new INVITE to the corresponding destination...
Page 419 User's Manual 19. Coders and Profiles Parameter Description a=group:ANAT 2 4 If you configure the parameter to a "prefer" option, the outgoing SDP offer contains two medias which are the same except for the "c=" field. The first media is the preferred address type (and this type is also on the session level "c="...
Page 420 Mediant 1000B Gateway & E-SBC Parameter Description Note:  Digital: The inclusion of the SDP in the 18x response depends on the ISDN Progress Indicator (PI). The SDP is sent only if PI is set to 1 or 8 in the received Proceeding, Alerting, or Progress messages.
Page 421 User's Manual 19. Coders and Profiles Parameter Description Profile Preference Defines the priority of the IP Profile, where 20 is the highest priority and 1 the lowest priority. ip-preference Note: [IpProfile_IpPreference]  If an IP Profile and a Tel Profile apply to the same call, the coders and other common parameters of the profile with the highest preference are applied to the call.
Page 422 Mediant 1000B Gateway & E-SBC Parameter Description  Analog: For IP-to-Tel calls, the device sends a 180 Ringing response to IP after placing a call to a phone (FXS) or PBX (FXO).  Digital: For IP-to-Tel calls, the device sends 180 Ringing response to the IP after receiving an ISDN Alerting or (for CAS) after placing a call to the PBX/PSTN.
Page 423 User's Manual 19. Coders and Profiles Parameter Description QSIG Tunneling Enables QSIG tunneling-over-SIP for this SIP entity. This is according to IETF Internet-Draft draft-elwell-sipping-qsig-tunnel-03 enable-qsig-tunneling and ECMA-355 and ETSI TS 102 345. [IpProfile_EnableQSIGTunneli  [0] Disable (default).  [1] Enable = Enables QSIG tunneling from QSIG to SIP, and vice versa.
Page 424 Mediant 1000B Gateway & E-SBC Parameter Description  [IpProfile_IsDTMFUsed] [0] Disable = (Default)  [1] Enable First Tx DTMF Option Defines the first preferred transmit DTMF negotiation method.  first-tx-dtmf-option [0] Not Supported = No negotiation - DTMF digits are sent according to the parameters DTMFTransportType and [IpProfile_FirstTxDtmfOption] RFC2833PayloadType (for transmit and receive).
Page 425 User's Manual 19. Coders and Profiles Parameter Description fax-sig-method fax session when the device detects a fax.  [IpProfile_IsFaxUsed] [0] No Fax = (Default) No fax negotiation using SIP signaling. The fax transport method is according to the FaxTransportMode parameter. ...
Page 426 Mediant 1000B Gateway & E-SBC Parameter Description 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 are used: [IpProfile_VxxTransportType] ...
Page 427 (16 sensitivity levels, from 0 to 15). This requires a customized AMD Sensitivity file that needs to be installed on the device. For more information, contact your AudioCodes sales representative. Note:  To configure the detection sensitivity level, use the 'AMD Sensitivity Level' parameter.
Page 428: Configuring Tel Profile
Mediant 1000B Gateway & E-SBC 19.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 429 User's Manual 19. Coders and Profiles Tel Profile Parameter Global Parameter [TelProfile_ProfileName] Signaling Profile Preference Defines the priority of the Tel Profile, where 1 is the lowest priority and 20 the highest priority. tel-preference Note: [TelProfile_TelPreference]  If both the IP Profile and Tel Profile apply to the same call, the coders and common parameters of the Preferred profile are applied to the call.
Page 430 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter  [1] Enable Digital interfaces: If the called number in IP-to-Tel call includes the characters 'w' or 'p', the device places a call with the first part of the called number (before 'w' or 'p') and plays DTMF digits after the call is answered.
Page 431 User's Manual 19. Coders and Profiles Tel Profile Parameter Global Parameter reorder tone is played, the device rejects the call. Note:  If the parameter is disabled and the PSTN side remains in off- hook state after the IP call ends the call, the device releases the call after 60 seconds.
Page 432 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter Note:  The parameter is applicable only to FXO and CAS.  The corresponding global parameter is DisconnectOnBusyTone. Time For Reorder Tone Defines the duration (in seconds) that the device plays a busy or reorder tone before releasing the line.
Page 433 User's Manual 19. Coders and Profiles Tel Profile Parameter Global Parameter paging calls, which provides a one-way voice path from the paging phone to the paged phones (FXS phones). Note:  The parameter is applicable only to FXS interfaces.  The corresponding global parameter is CutThrough.
Page 434 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter  FXO Interfaces: The device releases a call when a current disconnect signal is detected on its port.  FXS Interfaces: The device generates a 'Current Disconnect Pulse' after the call is released from the IP side.
Page 435 User's Manual 19. Coders and Profiles Tel Profile Parameter Global Parameter not generate a polarity change to normal if the Tel-to-IP call is answered by an IP party. Polarity reverts to normal when the call is released. For example: (Wink) KP 911 ST (Polarity) KP I(I) xxx-xxxx ST (Off Hook) ...
Page 436 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter Signaling DiffServ Defines the DiffServ value for Premium Control CoS content (Call Control applications). signaling-diffserv The valid range is 0 to 63. The default is 40. [TelProfile_SigIPDiffServ] Note:  For more information on DiffServ, see ''Configuring Class-of- Service QoS'' on page 152.
Page 437 User's Manual 19. Coders and Profiles Tel Profile Parameter Global Parameter  [0] No PI =  Analog: For IP-to-Tel calls, the device sends a 180 Ringing response to IP after placing a call to a phone (FXS) or PBX (FXO). ...
Page 438 Mediant 1000B Gateway & E-SBC Tel Profile Parameter Global Parameter Dynamic Jitter Buffer Maximum Delay Defines the maximum delay (in msec) for the device's Dynamic Jitter Buffer. jitter-buffer-maximum- delay The default is 300. [TelProfile_JitterBufMaxDelay] Dynamic Jitter Buffer Optimization Factor Defines the Dynamic Jitter Buffer frame error/delay optimization factor.
Page 439 User's Manual 19. Coders and Profiles Tel Profile Parameter Global Parameter FXO Double Answer Enables the FXO Double Answer feature, which rejects (disconnects) incoming (FXO) Tel-to-IP collect calls and signals fxo-double-answer (informs) this call denial to the PSTN. [TelProfile_EnableFXODoubleAnswer]  [0] Disable (default) ...
Page 440 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27045...
Page 441: Gateway Application
Part V Gateway Application...
Page 443: Introduction
User's Manual 20. Introduction Introduction This section describes configuration of the Gateway application. The Gateway application refers to IP-to-Tel (PSTN for digital interfaces) and Tel-to-IP call routing. For analog interfaces, Tel refers to FXO or FXS. For digital interfaces, Tel refers to the PSTN. Note: •...
Page 444 Mediant 1000B Gateway & E-SBC  IP-to-Tel Call: Figure 20-1: IP-to-Tel Call Processing Flowchart User's Manual Document #: LTRT-27045...
Page 445 User's Manual 20. Introduction  Tel-to-IP Call: Figure 20-2: Tel-to-IP Call Processing Flowchart Version 7.2 Mediant 1000B Gateway & E-SBC...
Page 446 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27045...
Page 447: 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 448 Mediant 1000B Gateway & E-SBC  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 449: Tdm And Timing
User's Manual 21. Digital PSTN • The read-only 'Module ID' field displays the module number to which the trunk belongs. • The read-only 'Trunk ID' field displays the selected trunk number. • The read-only 'Trunk Configuration State' displays the status of the trunk: ♦...
Page 450: Configuring Internal Clock As Clock Source
Mediant 1000B Gateway & E-SBC folder > TDM Bus Settings), and then do the following: Figure 21-2: Configuring TDM Bus From the 'TDM Bus Clock Source' drop-down list (TDMBusClockSource), select Network to recover the clock from the line interface. In the 'TDM Bus Local Reference' field (TDMBusLocalReference), enter the trunk from which the clock is derived.
Page 451: Configuring Cas State Machines
User's Manual 21. Digital PSTN Internal. (E1/T1 Trunks Only) Set the line to drive the clock on all trunks: In the Trunk Settings page, set the 'Clock Master' parameter (ClockMaster) to Generated (for all trunks). 21.3 Configuring CAS State Machines The CAS State Machine table lets you modify various timers and other basic parameters to define the initialization of the CAS state machine without changing the state machine itself (no compilation is required).
Page 452 Mediant 1000B Gateway & E-SBC 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 453: Configuring Digital Gateway Parameters
User's Manual 21. Digital PSTN Parameter Description CAS state machine). Collet ANI In some cases, when the state machine handles the ANI [CasStateMachineCollectANI] collection (not related to MFCR2), you can control the state machine to collect ANI or discard ANI. ...
Page 454: Tunneling Applications
Mediant 1000B Gateway & E-SBC 21.5 Tunneling Applications This section discusses the device's support for VoIP tunneling applications. 21.5.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network. TDM Tunneling utilizes the device's internal routing (without Proxy control) capabilities to receive voice and data streams from TDM spans or individual timeslots, convert them into packets, and then transmit them over the IP network (using point-to-point or point-to-multipoint device distributions).
Page 455 User's Manual 21. Digital PSTN For example, you can use low-bit-rate vocoders to transport voice and ‘Transparent’ coder to transport data (e.g., for D-channel). You can also use Profiles to assign ToS (for DiffServ) per source - a timeslot carrying data or signaling is assigned a higher priority value than a timeslot carrying voice.
Page 456 Mediant 1000B Gateway & E-SBC [ 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, ""; [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupName,...
Page 457: Dsp Pattern Detector
User's Manual 21. Digital PSTN TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ TelProfile_2 = data,$$,2,$$,$$,$$,$$,$$,$$,$$ [\TelProfile] 21.5.1.1 DSP Pattern Detector For TDM tunneling applications, you can use the DSP pattern detector feature to initiate the echo canceller at call start.
Page 458 Mediant 1000B Gateway & E-SBC The term tunneling means that messages are transferred ‘as is’ to the remote side without being converted (QSIG > SIP > QSIG). The advantage of tunneling over QSIG-to-SIP interworking is that by using interworking, QSIG functionality can only be partially achieved. When tunneling is used, all QSIG capabilities are supported and the tunneling medium (the SIP network) does not need to process these messages.
Page 459: Isdn Non-Facility Associated Signaling (Nfas)
User's Manual 21. Digital PSTN 21.6 ISDN Non-Facility Associated Signaling (NFAS) In regular T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B- channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.
Page 460: Working With Dms-100 Switches
Mediant 1000B Gateway & E-SBC To define an explicit Interface ID for a T1 trunk (that is different from the default), use the following parameters:  ISDNIBehavior_x = 512 (x = 0 to the maximum number of trunks identifying the device's physical trunk) ...
Page 461: Creating An Nfas-Related Trunk Configuration
User's Manual 21. Digital PSTN 21.6.3 Creating an NFAS-Related Trunk Configuration The procedures for creating and deleting an NFAS group must be performed in the correct order, as described below.  To create an NFAS Group: If there’s a backup (‘secondary’) trunk for this group, it must be configured first. Configure the primary trunk before configuring any NFAS (‘slave’) trunk.
Page 462: Collecting Isdn Digits And Sending Complete Number In Sip
Mediant 1000B Gateway & E-SBC with the complete destination number (see ''Collecting ISDN Digits and Sending Complete Number in SIP'' on page 462)  Interworks ISDN overlap dialing with SIP, according to RFC 3578 (see ''Interworking ISDN Overlap Dialing with SIP According to RFC 3578'' on page 463) Note: ISDN overlap dialing is applicable to PRI and BRI.
Page 463: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578
User's Manual 21. Digital PSTN 21.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 With overlap dialing disabled, the device expects to receive the digits all at once (enbloc) or with very little delay between digits and then sends the complete number in a single message.
Page 464: Redirect Number And Calling Name (Display)
Mediant 1000B Gateway & E-SBC • TimeBetweenDigits: Defines the maximum time (in seconds) that the device waits between digits received from the IP side. When the time expires, the device uses the collected digits to dial the called destination number. Note: For IP-to-Tel overlap dialing, to send ISDN Setup messages without including the Sending Complete IE, you must configure the ISDNOutCallsBehavior parameter...
Page 465: Trunk Groups
User's Manual 22. Trunk Groups Trunk Groups This section describes the configuration of the device's channels, which includes assigning them to Trunk Groups. 22.1 Configuring Trunk Groups The Trunk Group table lets you configure up to 120 Trunk Groups. A Trunk Group is a logical group of physical trunks and channels.
Page 466 Mediant 1000B Gateway & E-SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the telephony interface module for which you want to define the Trunk Group. module [TrunkGroup_Module] 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 467: Configuring Trunk Group Settings Table
User's Manual 22. Trunk Groups Parameter Description Trunk Group ID Defines the Trunk Group ID for the specified channels. The same Trunk Group ID can be assigned to more than one group of trunk-group-id channels. If an IP-to-Tel call is assigned to a Trunk Group, the IP [TrunkGroup_TrunkGroupNum] call is routed to the channel(s) pertaining to that Trunk Group ID.
Page 468 Mediant 1000B Gateway & E-SBC Configure a Trunk Group according to the parameters described in the table below. Click Apply. Table 22-2: Trunk Group Settings Table Parameter Descriptions Parameter Description General Index Defines an index number for the new table row. [TrunkGroupSettings_Index] Note: Each row must be configured with a unique index.
Page 469 User's Manual 22. Trunk Groups Parameter Description Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the channels of the Trunk Group. channel-select-mode  [0] By Dest Phone Number = The channel is selected according [TrunkGroupSettings_ChannelS to the called (destination) number.
Page 470 Mediant 1000B Gateway & E-SBC Parameter Description telephones connected to the FXS ports belonging to the Hunt Group start ringing. The call is eventually received by whichever telephone first answers the call (after which the other phones stop ringing). This option is applicable only to FXS interfaces. ...
Page 471 User's Manual 22. Trunk Groups Parameter Description Call-ID: 9907977062512000232825@10.33.37.78 CSeq: 3 REGISTER Contact: <sip:101@10.33.37.78>;expires=3600 Expires: 3600 User-Agent: Sip-Gateway/v.7.20A.000.038 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Groups table (see ''Configuring IP Groups'' on page 333). Note: ...
Page 472 Mediant 1000B Gateway & E-SBC Parameter Description Serving IP Group Assigns an IP Group to where the device sends INVITE messages for calls received from the Trunk Group. The actual destination to serving-ip-group where the INVITE messages are sent is according to the Proxy Set [TrunkGroupSettings_ServingIP associated with the IP Group.
Page 473 User's Manual 22. Trunk Groups Parameter Description device is locking the Trunk Group and indicates the number of buys channels and the time remaining until the graceful period ends, after which the device locks the channels regardless of whether the call has ended or not. ...
Page 474 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27045...
Page 475: Routing
User's Manual 23. Routing Routing This section describes the configuration of call routing rules. 23.1 Configuring Tel-to-IP Routing Rules The Tel-to-IP Routing table lets you configure up to 180 Tel-to-IP routing rules. Tel-to-IP routing rules are used to route calls from the Tel side to an IP destination. Configuration of Tel-to-IP routing rules includes two areas: ...
Page 476 Mediant 1000B Gateway & E-SBC The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it sends the call to the IP destination configured for that rule. If it doesn't find a matching rule, it rejects the call. Figure 23-1: Locating SRD In addition to normal Tel-to-IP routing, you can configure the following features: ...
Page 477 User's Manual 23. Routing  Always Use Routing Table: Even if a proxy server is used, the SIP Request-URI host name in the outgoing INVITE message is obtained from this table. Using this feature, you can assign a different SIP URI host name for different called and/or calling numbers.
Page 478 Mediant 1000B Gateway & E-SBC  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 23-2: Tel-to-IP Routing Table - Add Dialog Box Configure a routing rule according to the parameters described in the table below.
Page 479 User's Manual 23. Routing Parameter Rule 1 Rule 2 Rule Rule 4 Rule Rule 6 Rule 7 Rule 8 Group Destinatio 10.33.45.6 10.33.45.50 itsp.co 0.0.0. 10.33.45.6 10.33.45.6 domain.co n IP Address IP Profile Forking Group Cost Weekend- Weekend_Hig Group ID Below are descriptions of each rule: ...
Page 480 Mediant 1000B Gateway & E-SBC 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. src-phone-prefix For example, [100-199](100,101,105) denotes a number that [PREFIX_SourcePrefix] starts with 100 to 199 and ends with 100, 101 or 105. To denote any prefix, use the asterisk (*) symbol (default) or to denote calls without a calling number, use the $ sign.
Page 481 User's Manual 23. Routing Parameter Description table).  The parameter is used as the 'Serving IP Group' in the Accounts table for acquiring authentication username/password for this call (see ''Configuring Registration Accounts'' on page 361).  To configure Proxy Sets, see ''Configuring Proxy Sets'' on page 346.
Page 482 Mediant 1000B Gateway & E-SBC Parameter Description IP Profile Assigns an IP Profile to the routing rule in the outgoing direction. The IP Profile allows you to assign various configuration attributes ip-profile-id (e.g., voice coder) per routing rule. To configure IP Profiles, see [PREFIX_ProfileName] ''Configuring IP Profiles'' on page 393.
Page 483 User's Manual 23. Routing Parameter Description other index entries even if the destination is unavailable and alternative routing is enabled. This is because the subsequent index entries are defined with a Forking Group number that is lower than that of index entry 1. ...
Page 484: Configuring Ip-To-Tel Routing Rules
Mediant 1000B Gateway & E-SBC Parameter Description rules that are not assigned Cost Groups are considered as a higher or lower cost route compared to matching routing rules that are assigned Cost Groups. For example, if the 'Default Call Cost' parameter in the Routing Policy is configured to Lowest Cost, even if the device locates matching routing rules that are assigned Cost Groups, the first-matched routing rule without an assigned Cost Group is considered as the...
Page 485 User's Manual 23. Routing (see ''Configuring Trunk Group Settings'' on page 467) or for all Trunk Groups, using the global parameter ChannelSelectMode. Configuration of IP-to-Tel routing rules includes two areas:  Match: Defines the characteristics of the incoming IP call (e.g., IP Group from which the call is received).
Page 486 Mediant 1000B Gateway & E-SBC Note: • Instead of using the table for IP-to-Tel routing, you can employ a third-party Routing server to handle the routing decisions. For more information, see ''Centralized Third-Party Routing Server'' on page 269. • You can configure up to three alternative routing rules per "main" routing rule in the table.
Page 487 User's Manual 23. Routing Table 23-3: Example of IP-to-Tel Routing Rules Parameter Rule 1 Rule 2 Rule 3 Source Host Prefix abcd.domain Destination Phone Prefix [501-502] Source Phone Prefix Source IP Address Trunk Group ID IP Profile ITSP-A ITSP-B Below provides descriptions of each rule: ...
Page 488 Mediant 1000B Gateway & E-SBC Parameter Description Group in the 'Source IP Group' parameter (in this table) is different, the incoming SIP call is rejected. If the 'Source IP Group' parameter is not defined, the SIP Interface associated with the default SRD (Index 0) is used. If there is no valid source IP Group, the call is rejected.
Page 489: Configuring A Gateway Routing Policy Rule
User's Manual 23. Routing Parameter Description notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 923. By default, no value is defined. The prefix can include up to 49 digits. Destination Host Prefix Defines the Request-URI host name prefix of the incoming INVITE message.
Page 490 Mediant 1000B Gateway & E-SBC Groups. The default call cost determines whether matched routing rules that are not assigned a Cost Group are considered as a higher or lower cost route compared to other matching routing rules that are assigned Cost Groups. If you disable LCR, the device ignores the Cost Groups assigned to Tel-to-IP routing rules in the Tel-to-IP Routing table.
Page 491: Alternative Routing For Tel-To-Ip Calls
User's Manual 23. Routing Parameter Description lcr-enable Policy.  [GWRoutingPolicy_LCREnable] [0] Disable (default)  [1] Enable For more information on LCR, see ''Least Cost Routing'' on page 257. Note: LCR is applicable only to Tel-to-IP routing. Default Call Cost Defines whether routing rules in the Tel-to-IP Routing table that are not assigned a Cost Group are considered a higher cost or lcr-default-cost lower cost route compared to other matched routing rules that...
Page 492: Alternative Routing Based On Ip Connectivity
Mediant 1000B Gateway & E-SBC • SIP OPTIONS: The device sends "keep-alive" SIP OPTIONS messages to the IP destination. If the device receives a SIP 200 OK in response, it considers the destination as available. If the destination does not respond to the OPTIONS message, then it is considered unavailable.
Page 493 User's Manual 23. Routing configured in the Tel-to-IP Routing table. These rules must be configured anywhere below the "main" routing rule and with identical matching characteristics (e.g., destination prefix number) to the "main" routing rule. The device uses the first alternative route that is available.
Page 494: Alternative Routing Based On Sip Responses
Mediant 1000B Gateway & E-SBC Open the Routing Settings page (Setup menu > Signaling & Media tab > Gateway folder > Routing > Routing Settings): Figure 23-7: Configuring Alternative Tel-to-IP Routing based on Connectivity Under the Alternative Route group, do the following: From the 'Enable Alt Routing Tel to IP' (Tel2IPEnable) drop-down list, select Enable to enable alternative Tel-to-IP routing based on IP connectivity.
Page 495 User's Manual 23. Routing configured by 1) assigning an IP Group a QoE and/or Bandwidth profile that rejects calls if the threshold is crossed, 2) configuring 806 in the Reasons for Tel-to-IP Alternative Routing table and 3) configuring an alternative routing rule. Note: The device also plays a tone to the endpoint whenever an alternative route is used.
Page 496 Mediant 1000B Gateway & E-SBC • Parking mode: The device continues operating with the redundant proxy (now active) until the next failure occurs, after which it switches to the next redundant proxy. • Homing mode: The device always attempts to operate with the primary proxy. In other words, it switches back to the primary proxy whenever it's available again.
Page 497: Alternative Routing Upon Sip 3Xx With Multiple Contacts
User's Manual 23. Routing Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP Definitions folder > Proxy & Registration). From the 'Redundant Routing Mode' drop-down list, select one of the following: • Routing Table: Tel-to-IP Routing table is used for alternative routing. •...
Page 498: Pstn Fallback
Mediant 1000B Gateway & E-SBC 23.4.5 PSTN Fallback The PSTN Fallback feature enables the device to re-route a Tel-to-IP call to the legacy PSTN using one of its trunks if the IP destination is unavailable. For example, if poor voice quality is detected over the IP network, the device attempts to re-route the call to the PSTN.
Page 499 User's Manual 23. Routing The default release code is Cause Code No. 3 (No Route to Destination). You can change the default code as follows:  To change the default Q.931 release code: Open the Gateway Advanced Settings page (Setup menu > Signaling & Media tab > Gateway folder >...
Page 500: Alternative Routing To An Ip Destination Upon A Busy Trunk
Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 23-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.
Page 501 User's Manual 23. Routing • Analog interfaces: All FXS / FXO lines pertaining to a Trunk Group are busy or unavailable The following procedure describes how to configure Forward on Busy Trunks through the Web interface. You can also configure it through ini file (ForwardOnBusyTrunkDest) or CLI (configure voip >...
Page 502: Alternative Routing Upon Isdn Disconnect
SIP Trunk. This is configured using the ini file parameter, TR104FXOSwitchover. Note: For more information on this application, please contact your AudioCodes sales representative. User's Manual...
Page 503: Manipulation
User's Manual 24. Manipulation Manipulation This section describes the configuration of various manipulation processes. 24.1 Configuring Redirect Reasons You can manipulate call redirect (diversion) reasons between IP (SIP) and Tel (ISDN). The SIP Diversion header contains the information on the redirection of the call, including the reason (e.g., 'reason=user-busy').
Page 504 Mediant 1000B Gateway & E-SBC • 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). ...
Page 505 User's Manual 24. Manipulation The following procedure describes how to configure number manipulation rules through the Web interface. You can also configure this using the following management tools:  Destination Phone Number Manipulation for IP-to-Tel Calls table: ini file (NumberMapIP2Tel) or CLI (configure voip > gateway manipulation dst-number-map- ip2tel) ...
Page 506 Mediant 1000B Gateway & E-SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source Prefix 1001 123451001# [30-40]x 2001 Stripped Digits From Left Stripped Digits From Right Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted...
Page 507 User's Manual 24. Manipulation Parameter Description represent any number between 0 and 255. For example, 10.8.8.* represents all IP addresses between 10.8.8.0 and 10.8.8.255. Destination IP Group Defines the IP Group to where the call is sent. dst-ip-group-id The default is Any (i.e., any IP Group). [_DestIPGroupID] Note: The parameter is applicable only to the Destination Phone Number Manipulation for Tel-to-IP Calls table.
Page 508 Mediant 1000B Gateway & E-SBC Parameter Description Action 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. [_RemoveFromLeft] Stripped Digits From Right Defines the number of digits to remove from the right of the telephone...
Page 509: Manipulating Number Prefix
User's Manual 24. Manipulation Parameter Description Plans and Type of Number on page 529. Defines the Numbering Plan Indicator (NPI).  [-1] = Not configured and the value received from PSTN/IP is used.  [0] Unknown (default) [NumberPlan]  [1] E.164 Public ...
Page 510: Sip Calling Name Manipulations
Mediant 1000B Gateway & E-SBC 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: The following notation is used in the 'Prefix to Add' field: 0[5,3]15...
Page 511 User's Manual 24. Manipulation  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 calling name). The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call.
Page 512 Mediant 1000B Gateway & E-SBC Table 24-4: Calling Name Manipulation Tables Parameter Descriptions 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 an arbitrary name to easily identify the row. manipulation-name The valid value is a string of up to 20 characters.
Page 513: Configuring Redirect Number Ip To Tel
User's Manual 24. Manipulation Parameter Description Manipulation for IP-to-Tel Calls table. Source Host Prefix Defines the URI host name prefix of the incoming SIP INVITE message in the From header. src-host-prefix The default value is the asterisk (*) symbol (i.e., any source host prefix). [_SrcHost] Note: ...
Page 514 Mediant 1000B Gateway & E-SBC Number Information Element (IE) in the ISDN Setup message sent to the Tel side. This also includes the reason for the call redirection.  Redirect Number Tel to IP table: Defines Tel-to-IP redirect number manipulation. You can manipulate the prefix of the redirect number received from the Tel side, in the outgoing SIP Diversion, Resource-Priority, or History-Info headers sent to the IP side.
Page 515 User's Manual 24. Manipulation Click New; the following dialog box appears (e.g., Redirect Number Tel-to-IP table): Figure 24-4: Redirect Number Manipulation for Tel-to-IP Table (Example) - Add Dialog Box Configure a manipulation rule according to the parameters described in the table below.
Page 516 Mediant 1000B Gateway & E-SBC Parameter Description src-trunk-group-id To denote any Trunk Group, leave this field empty. The value -1 indicates that this field is ignored in the rule. [_SrcTrunkGroupID] Note: The parameter is applicable only to the Redirect Number Tel-to- IP table.
Page 517 User's Manual 24. Manipulation Parameter Description [_Suffix2Add] number is 123400. Defines the Type of Number (TON).  [-1] = (Default) Not configured  [0] Unknown (default) [_NumberType]  [1] International-Level2 Regional  [2] National-Level1 Regional  [3] Network-PSTN Specific  [4] Subscriber-Level0 Regional ...
Page 518: Manipulating Redirected And Diverted Numbers For Call Diversion
Mediant 1000B Gateway & E-SBC 24.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. Note: The feature is applicable only to Euro ISDN and QSIG variants in the IP-to-Tel call direction.
Page 519: Mapping Npi/Ton To Sip Phone-Context
User's Manual 24. Manipulation Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.7.20A.000.038 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 24.7 Mapping NPI/TON to SIP Phone-Context The Phone Contexts table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
Page 520 Mediant 1000B Gateway & E-SBC 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 ISDN Setup message (for digital interfaces) with called and calling numbers, from the 'Add Phone Context As Prefix' drop-down list (AddPhoneContextAsPrefix), select Enable.
Page 521: Configuring Release Cause Mapping
User's Manual 24. Manipulation 24.8 Configuring Release Cause Mapping When a call is disconnected, the reason for the disconnection (or call failure) is sent by the side (IP or Tel) on which the call disconnection occurred. From the IP side, a SIP response is sent (e.g., 406);...
Page 522: Fixed Mapping Of Sip Response To Isdn Release Reason
Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 24-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 24-8: Release Cause Mapping from SIP to ISDN Table Parameter Descriptions Parameter Description...
Page 523: Isdn-To-Sip Release Cause Mapping
User's Manual 24. Manipulation ISDN Release SIP Response Description Description Reason Conflict Temporary failure Gone Number changed w/o diagnostic Length required Interworking Request entity too long Interworking Request URI too long Interworking Unsupported media type Service/option not implemented Bad extension Interworking Temporarily unavailable No user responding...
Page 524 Mediant 1000B Gateway & E-SBC ISDN cause code from the PSTN side, it searches the table for a matching ISDN cause code. If found, the device sends the corresponding SIP response to the IP. If the ISDN cause code is not configured in the table, the default, fixed ISDN-to-SIP release reason mapping is used.
Page 525: Fixed Mapping Of Isdn Release Reason To Sip Response
User's Manual 24. Manipulation 24.8.2.2 Fixed Mapping of ISDN Release Reason to SIP Response The following table shows the mapping of ISDN release reason to SIP response. Table 24-11: Mapping of ISDN Release Reason to SIP Response ISDN Release Description Description Reason Response...
Page 526: Configuring Isdn-To-Isdn Release Cause Mapping
Mediant 1000B Gateway & E-SBC ISDN Release Description Description Reason Response Bearer capability not implemented Not implemented Channel type not implemented 480* Temporarily unavailable Requested facility not implemented 503* Service unavailable Only restricted digital information bearer 503* Service unavailable capability is available Service or option not implemented Not implemented Invalid call reference value...
Page 527 User's Manual 24. Manipulation In other words, it lets you change the originally received ISDN cause code to a different ISDN cause code. For example, the PSTN may indicate disconnected calls (hang up) by sending cause code 127. However, you can change the cause code to 16, which is a more typical cause code for such call scenarios.
Page 528: Reason Header
Mediant 1000B Gateway & E-SBC Parameter Description Orig. Q.850 Causes Defines the originally received ISDN Q.850 cause code. For example, you can enter "127" (without q850-causes apostrophes) to represent cause code 127 [CauseMapIsdn2Isdn_OrigIsdnReleaseCause] Interworking, Unspecified. The valid value (cause code) is 1 to 127. Map Q.850 Causes Defines the ISDN Q.850 cause code to which you want to change the originally received cause code.
Page 529: Numbering Plans And Type Of Number
User's Manual 24. Manipulation the device sends a SIP response to the IP according to the 'Default Release Cause' parameter. 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.
Page 530 Mediant 1000B Gateway & E-SBC  1/4 - Subscriber (local) number in ISDN/Telephony numbering plan  9/4 - Subscriber (local) number in Private numbering plan User's Manual Document #: LTRT-27045...
Page 531: Configuring Dtmf And Dialing
User's Manual 25. Configuring DTMF and Dialing Configuring DTMF and Dialing This section describes dual-tone multi-frequency (DTMF) and dialing configuration. 25.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 25.1.1 Digit Mapping Digit map pattern rules are used for Tel-to-IP ISDN overlap dialing (by setting the ISDNRxOverlap parameter to 1) to reduce the dialing period (for digital interface).
Page 532: External Dial Plan File
Mediant 1000B Gateway & E-SBC 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 533: Configuring Hook Flash
User's Manual 25. Configuring DTMF and Dialing 4452eff4acb SIP/2.0 To: sip:123#456@192.168.100.214;user=phone;x-type=unknown;x- plan=unknown;x-pres=allowed The destination number can be manipulated when this feature is enabled. Note that if manipulation before routing is required, the * and # characters should not be used, as the device will handle them according to the above keypad protocol.
Page 534 Mediant 1000B Gateway & E-SBC ♦ '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 428. Figure 25-3: Configuring Hook-Flash Detection Period Click Apply.
Page 535: Configuring Supplementary Services
User's Manual 26. Configuring Supplementary Services Configuring Supplementary Services This section describes SIP supplementary services that can enhance your telephone service. Note: • All call participants must support the specific supplementary service that is used. • When working with certain application servers (such as BroadSoft’s BroadWorks) in client server mode (the application server controls all supplementary services and keypad features by itself), the device's supplementary services must be disabled.
Page 536 Mediant 1000B Gateway & E-SBC The device also supports "double call hold" for FXS interfaces where the called party, which has been placed on-hold by the calling party, can then place the calling party on hold as well and make a call to another destination. The flowchart below provides an example of this type of call hold: Figure 26-1: Double Hold SIP Call Flow The flowchart above describes the following "double"...
Page 537: Call Pickup
User's Manual 26. Configuring Supplementary Services Note: • If a party that is placed on hold (e.g., B in the above example) is called by another party (e.g., D), then the on-hold party receives a call waiting tone instead of the held tone.
Page 538: Consultation Feature
Mediant 1000B Gateway & E-SBC Note: Only one call can be suspended per trunk. If another suspend request is received from a BRI phone while there is already a suspended call (even if done by another BRI phone connected to the same trunk), the device rejects this suspend request.
Page 539: Consultation Transfer For Qsig Path Replacement
User's Manual 26. Configuring Supplementary Services Note: For FXS interfaces, the device can also handle call transfers using SIP INVITE and re-INVITE messages, instead of REFER messages. This is useful when communicating with SIP UAs that do not support the receipt of REFER messages. This feature is applicable to FXS interfaces.
Page 540: Blind Call Transfer
Mediant 1000B Gateway & E-SBC 26.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 541: Enabling Call Forwarding
User's Manual 26. Configuring Supplementary Services Call forward performed by the PSTN side: When the device sends the INVITE message to the remote SIP entity and receives a SIP 302 response, the device sends a Facility message with the same IE mentioned above to the PSTN, and waits for the PSTN side to disconnect the call.
Page 542 Mediant 1000B Gateway & E-SBC (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 543: Call Forward Reminder (Off-Hook) Special Dial Tone
User's Manual 26. Configuring Supplementary Services Note: The feature is applicable only to FXS interfaces. 26.6.3 Call Forward Reminder (Off-Hook) Special Dial Tone The device plays a special dial tone (stutter dial tone - Tone Type #15) to a specific FXS endpoint when the phone is off-hooked and when a third-party Application server (e.g., a softswitch) is used to forward calls intended for the endpoint to another destination.
Page 544: Bri Call Forwarding
Mediant 1000B Gateway & E-SBC 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 739). 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 INVITE message to the softswitch.
Page 545 User's Manual 26. Configuring Supplementary Services  To configure the digit codes for call forwarding services by BRI phones: Open the Supplementary Services Settings page (Setup menu > Signaling & Media tab > Gateway folder > DTMF & Supplementary > Supplementary Services Settings).
Page 546: Enabling Call Waiting
Mediant 1000B Gateway & E-SBC 26.7 Enabling Call Waiting The Call Waiting feature enables busy FXS endpoints connected to the device to accept an additional (second) call. If an incoming IP call is designated to a busy port, the called FXS endpoint hears a call waiting tone (several configurable short beeps) and can view the Caller ID of the incoming call (for Bellcore and ETSI Caller IDs).
Page 547: Message Waiting Indication
User's Manual 26. Configuring Supplementary Services 26.8 Message Waiting Indication The device supports Message Waiting Indication (MWI) according to IETF RFC 3842. The device also supports subscribing to an MWI server (using SIP SUBSCRIBE messages). For FXS interfaces, the device can accept a SIP MWI NOTIFY message that indicates waiting messages or cleared messages.
Page 548: Caller Id
Mediant 1000B Gateway & E-SBC  QSIG MWI: The device supports the interworking of QSIG MWI to IP (in addition to interworking of SIP MWI NOTIFY to QSIG Facility MWI messages). This provides interworking between an ISDN PBX with voice mail capabilities and a softswitch, which requires information on the number of messages waiting for a specific user.
Page 549: Debugging A Caller Id Detection On Fxo
User's Manual 26. Configuring Supplementary Services Note: You can enable Caller ID generation (FXS interfaces) and detection (FXO interfaces) per port in the Caller ID Permissions table (see ''Configuring Caller ID Permissions'' on page 586). For ports that are not configured in the table, Caller ID is according to the global parameter, as described in the procedure below.
Page 550: Caller Id On The Ip Side
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 551: Three-Way Conferencing
The device supports the following three-way conference modes:  Conference Managed by External, AudioCodes Conferencing (Media) Server: The conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.
Page 552 Mediant 1000B Gateway & E-SBC ♦ Configure the device with an Inbound Manipulation rule that is applied to calls received from the third-party network entity so that the device considers conference calls as regular calls and forwards them to the Conference server without getting involved in the conferencing setup.
Page 553: Emergency E911 Phone Number Services
User's Manual 26. Configuring Supplementary Services Settings). Figure 26-9: Configuring Three-way Conferencing From the 'Enable 3-Way Conference' drop-down list (Enable3WayConference), select Enable. From the '3-Way Conference Mode' drop-down list (3WayConferenceMode), select the three-way conference mode (e.g, On Board). For On Board mode: •...
Page 554: Fxs Device Emulating Psap Using Did Loop-Start Lines
Mediant 1000B Gateway & E-SBC 26.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 26-10: 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 555 User's Manual 26. Configuring Supplementary Services After the call is disconnected by the PSAP, the PSAP sends a SIP BYE to the FXS device, and the FXS device reverses the polarity of the line toward the tandem switch. The following parameters need to be configured: ...
Page 556 Mediant 1000B Gateway & E-SBC  # 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 557: Fxo Device Interworking Sip E911 Calls From Service Provider's Ip Network To Psap Did Lines
User's Manual 26. Configuring Supplementary Services 26.11.2 FXO Device Interworking SIP E911 Calls from Service Provider's IP Network to PSAP DID Lines The device's FXO interface can interwork SIP emergency E911 calls from the Service Provider's IP network to the analog PSAP DID lines. The standards that define this interface include TR-TSY-000350 or Bellcore’s GR-350-Jun2003.
Page 558 Mediant 1000B Gateway & E-SBC 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 559 From: "0123456789" <sip:333333444444@audiocodes.com>;tag=1c771623824 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...
Page 560: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls
Mediant 1000B Gateway & E-SBC 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 From: port1vega1 <sip:06@192.168.13.2:5060>...
Page 561: Multilevel Precedence And Preemption
User's Manual 26. Configuring Supplementary Services 26.12 Multilevel Precedence and Preemption The device supports Multilevel Precedence and Preemption (MLPP) service. MLPP is a call priority scheme, which does the following:  Assigns a precedence level (priority level) to specific phone calls or messages. ...
Page 562 Mediant 1000B Gateway & E-SBC MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header 9 (highest) flash-override-override MLPPFlashOverOverRTPDSCP The device automatically interworks the network identity digits (NI) in the ISDN Q.931 Precedence Information Element (IE) to the network domain subfield of the INVITE's Resource-Priority header, and vice versa.
Page 563: Mlpp Preemption Events In Sip Reason Header
User's Manual 26. Configuring Supplementary Services MLPP Precedence Level ISDN Precedence Level SIP Resource-Priority Header Field Priority Immediate Flash Flash Override  If the network-domain field in the Resource-Priority header is any value other than "uc", then the device sets the Precedence Level field to "0 1 0 0" (i.e., "routine"). This can be modified using the EnableIp2TelInterworkingtable field of the ini file parameter, ResourcePriorityNetworkDomains.
Page 564: Precedence Ring Tone
Mediant 1000B Gateway & E-SBC • CANCEL - If an outgoing call is being preempted by another call • 480 (Temporarily Unavailable), 486 (User Busy), 488 (Not Acceptable Here) - Due to incoming calls being preempted by another call. The device receives SIP requests with preemption reason cause=5 in the following cases: •...
Page 565: Configuring Multi-Line Extensions And Supplementary Services
User's Manual 26. Configuring Supplementary Services 26.14 Configuring Multi-Line Extensions and Supplementary Services The Supplementary Services table lets you configure up to 100 supplementary services for endpoints connected to the device. These endpoints include FXS phones and Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) phones. You can use the table for the following functionalities: ...
Page 566 Mediant 1000B Gateway & E-SBC Note: • If you have configured regular Tel-to-IP or IP-to-Tel manipulation rules (see ''Configuring Source/Destination Number Manipulation'' on page 503), the device applies them before applying the local-global mapping rules configured in the table. • To allow the end user to hear a dial tone when picking up the BRI phone, it is recommended to set the Progress Indicator in the Setup Ack bit (0x10000=65536).
Page 567 User's Manual 26. Configuring Supplementary Services  To register or un-register an endpoint: In the Trunk Group Settings table (see ''Configuring Trunk Group Settings'' on page 467), configure the registration method using the 'Registration Mode' parameter. In the Supplementary Services table, select the required endpoint. From the 'Action' drop-down list, select Register.
Page 568: Detecting Collect Calls
The device interworks these ISDN messages with SIP by converting the AOC messages into SIP INFO (during call) and BYE messages (end of call) using AudioCodes proprietary SIP AOC header, and vice versa. The device supports both currency (monetary units) and pulse (non-monetary units) AOC messages.
Page 569 The device supports various AOC methods:  Tel-to-IP Direction: The device converts the AOC messages received in the EURO ISDN Facility IE messages into SIP INFO and BYE messages using AudioCodes proprietary SIP AOC header.  Device Generation of AOC to Tel: The device generates the metering tones according to user-defined pulses and intervals, configured in the Charge Code table (see ''Configuring Charge Codes'' on page 570).
Page 570: Configuring Charge Codes
Mediant 1000B Gateway & E-SBC In the Tel-to-IP Routing table, assign the Charge Code index to the relevant Tel-to-IP routing rule (see ''Configuring Tel-to-IP Routing Rules'' on page 475). • AOC in Tel-to-IP Direction: Open the Supplementary Services Settings page, and then configure the 'AoC Support' parameter to Enable to send AOC to IP.
Page 571 User's Manual 26. Configuring Supplementary Services Click New; the following dialog box appears: Figure 26-16: Charge Codes Table - Add Dialog Box Configure a Charge Code according to the parameters described in the table below. Click Apply. Table 26-7: Charge Codes Table Parameter Descriptions Parameter Description Index...
Page 572: Configuring Voice Mail
Mediant 1000B Gateway & E-SBC 26.18 Configuring Voice Mail The Voice Mail Settings page lets you configure voice mail. For more information on voice mail, refer to the CPE Configuration Guide for Voice Mail User's Manual. For a detailed description of the voice mail parameters, see ''Voice Mail Parameters'' on page 1041. Note: Voice Mail is applicable only to FXO and CAS interfaces.
Page 573: Converting Accented Characters From Ip To Tel
User's Manual 26. Configuring Supplementary Services • 'MWI Source Number' (MWISourceNumber): Defines the calling party's phone number in the Q.931 MWI Setup message to PSTN. Under the SMDI group, configure Simplified Message Desk Interface (SMDI): • 'Enable SMDI' (SMDI): Enables SMDI interface on the device. •...
Page 574 Mediant 1000B Gateway & E-SBC languages such as German. An example of such a character is the umlaut (or diaeresis), which consists of two dots placed over a letter, as in ä. The importance of this conversion feature is that it allows PSTN entities that do not support accented characters, to receive ASCII characters.
Page 575 User's Manual 26. Configuring Supplementary Services Parameter Description [CharConversion_FirstByte] Second Byte Defines the second byte of the Unicode character (e.g., 164). second-byte The default is 128. [CharConversion_SecondByte] Converted Output Defines the ASCII character (e.g., "ae") to which the Unicode character must be converted. converted-output The valid value is a string of up to four characters.
Page 576 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27045...
Page 577: Analog Gateway
User's Manual 27. Analog Gateway Analog Gateway This section describes configuration of analog settings. 27.1 Configuring Keypad Features The Keypad Features page lets you configure key sequences that can be pressed on telephone keypads of FXS endpoints to activate and deactivate the following features: ...
Page 578: Configuring Metering Tones
Mediant 1000B Gateway & E-SBC Configure the keypad features as required. Click Apply. 27.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 579: Configuring Authentication
User's Manual 27. Analog Gateway  To configure the FXO parameters: Open the FXO Settings page (Setup menu > Signaling & Media tab > Gateway folder > Analog Gateway > FXO Settings). Figure 27-3: Configuring FXO Settings Configure the parameters as required. Click Apply.
Page 580 Mediant 1000B Gateway & E-SBC • Endpoints per Trunk Group: Open the Trunk Group Settings table (see ''Configuring Trunk Group Settings'' on page 467), and then for the required Trunk Group ID, configure the 'Registration Mode' parameter to Per Endpoint (TrunkGroupSettings_RegistrationMode).
Page 581: Configuring Automatic Dialing
User's Manual 27. Analog Gateway 27.5 Configuring Automatic Dialing The Automatic Dialing table lets you configure telephone numbers that are automatically dialed when FXS or FXO ports go off-hook. The dialing can be done immediately upon off- hook or after a user-defined interval after off-hook, referred to as Hotline dialing. For example, you can configure Hotline automatic dialing where if Port #1 remains off-hooked for over 15 seconds, the device automatically dials 911.
Page 582: Configuring Caller Display Information
Mediant 1000B Gateway & E-SBC Parameter Description dst-number [TargetOfChannel_Destination] Auto Dial Status Enables automatic dialing.  auto-dial-status [0] Disable = Automatic dialing for the specific port is disabled. [TargetOfChannel_Type]  [1] Enable = (Default) Automatic dialing is enabled and the phone number configured in the 'Destination Phone Number' field is automatically dialed if the following occurs: ...
Page 583 User's Manual 27. Analog Gateway The following procedure describes how to configure caller ID through the Web interface. You can also configure it through ini file (CallerDisplayInfo) or CLI (configure voip > gateway analog caller-display-info).  To configure caller ID: Open the Caller Display Information table (Setup menu >...
Page 584: Configuring Call Forward
Mediant 1000B Gateway & E-SBC Parameter Description  [1] Restricted = The caller ID string is not sent. The Caller ID is sent to the remote side using only the SIP P-Asserted- Identity or P-Preferred-Identity headers, according to the AssertedIdMode parameter. Note: The parameter is overridden by the 'Presentation' parameter in the Source Number Manipulation table (see ''Configuring Source/Destination Number Manipulation'' on page...
Page 585 User's Manual 27. Analog Gateway Select the row corresponding to the port that you want to configure, and then click Edit; the following dialog box appears: Figure 27-6: Call Forward Table - Edit Dialog Box Configure call forwarding per port according to the parameters described in the table below.
Page 586: Configuring Caller Id Permissions
Mediant 1000B Gateway & E-SBC 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 475).
Page 587: Configuring Call Waiting
User's Manual 27. Analog Gateway Parameter Description General Index Defines an index number for the new table row. [EnableCallerId_Index] Note: Each row must be configured with a unique index. Module (Read-only) Displays the module number on which the port is located. [EnableCallerId_Module] Port (Read-only) Displays the port number.
Page 588: Rejecting Anonymous Calls
Mediant 1000B Gateway & E-SBC  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 589: Configuring Fxs Distinctive Ringing And Call Waiting Tones Per Source/Destination Number
User's Manual 27. Analog Gateway 27.11 Configuring FXS Distinctive Ringing and Call Waiting Tones per Source/Destination Number The Tone Index table lets you configure distinctive ringing tones and call waiting tones per calling (source) and called (destination) number (or prefix) for IP-to-Tel calls. You can configure the feature per FXS port or for a range of FXS ports.
Page 590: Fxs/Fxo Coefficient Types
Mediant 1000B Gateway & E-SBC Table 27-7: Tone index Table Parameter Description Parameter Description Index Defines the table index entry. Up to 50 entries can be defined. FXS Port First Defines the first port in the FXS port range. fxs-port-first [ToneIndex_FXSPort_First] FXS Port Last Defines the last port in the FXS port range.
Page 591: Fxo Operating Modes
User's Manual 27. Analog Gateway  Hybrid balance  Frequency response in transmit and receive direction  Hook thresholds  Ringing generation and detection parameters  To select the FXO and FXS Coefficient types: Open the Analog Settings page (Setup menu > Signaling & Media tab > Gateway folder >...
Page 592 Mediant 1000B Gateway & E-SBC One-stage dialing incorporates the following FXO functionality:  Waiting for Dial Tone: Enables the device to dial the digits to the Tel side only after detecting a dial tone from the PBX line. The ini file parameter IsWaitForDialTone is used to configure this operation.
Page 593: Two-Stage Dialing
User's Manual 27. Analog Gateway 27.13.1.2 Two-Stage Dialing Two-stage dialing is when the IP caller is required to dial twice. The caller initially dials to the FXO device and only after receiving a dial tone from the PBX (via the FXO device), dials the destination telephone number.
Page 594: Fxo Operations For Tel-To-Ip Calls
Mediant 1000B Gateway & E-SBC The "start dial" signal is a wink from the PBX to the FXO device. The FXO then sends the last four to five DTMF digits of the called number. The PBX uses these digits to complete the routing directly to an internal station (telephone or equivalent).
Page 595: Collecting Digits Mode
User's Manual 27. Analog Gateway 27.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 27-12: Call Flow for Collecting Digits Mode 27.13.2.3 FXO Supplementary Services The FXO supplementary services include the following: ...
Page 596: Call Termination On Fxo Devices
Mediant 1000B Gateway & E-SBC a response to input from the Tel side. If the FXO receives a REFER request (with or without replaces), it generates a new INVITE according to the Refer-To header. 27.13.3 Call Termination on FXO Devices This section describes the device's call termination capabilities for its FXO interfaces: ...
Page 597: Call Termination Before Call Establishment
User's Manual 27. Analog Gateway Note: The implemented disconnect method must be supported by the CO or PBX. 27.13.3.2 Call Termination before Call Establishment The device supports the following call termination methods before a call is established:  Call termination upon receipt of SIP error response (in Automatic Dialing mode): By default, when the FXO device operates in Automatic Dialing mode, there is no method to inform the PBX if a Tel-to-IP call has failed (SIP error response - 4xx, 5xx or 6xx - is received).
Page 598: Dialing From Remote Extension (Phone At Fxs)
Mediant 1000B Gateway & E-SBC This section provides an example on how to implement a remote telephone extension through the IP network, using FXO andFXS interfaces. In this configuration, the FXO device routes calls received from the PBX to the ‘Remote PBX Extension’ connected to the FXS device.
Page 599: Dialing From Pbx Line Or Pstn
User's Manual 27. Analog Gateway 27.14.2 Dialing from PBX Line or PSTN 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).
Page 600: Fxs Gateway Configuration
Mediant 1000B Gateway & E-SBC 27.14.5 FXS Gateway Configuration The following procedure describes how to configure the FXS interface (at the 'remote PBX extension').  To configure the FXS interface: In the Trunk Group table (see Configuring Trunk Groups), assign the phone numbers 100 to 104 to the device's FXS ports.
Page 601: Fxo Gateway Configuration
User's Manual 27. Analog Gateway 27.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 465), assign the phone numbers 200 to 204 to the device’s FXO endpoints.
Page 602 Mediant 1000B Gateway & E-SBC This page is intentinally left blank. User's Manual Document #: LTRT-27045...
Page 603: Session Border Controller Application
Part VI Session Border Controller Application...
Page 605: Sbc Overview
User's Manual 28. SBC Overview SBC Overview This section provides an overview of the device's SBC application. Note: • For guidelines on how to deploy your SBC device, refer to the SBC Design Guide document. • The SBC feature is available only if the device is installed with a License Key that includes this feature.
Page 606: B2Bua And Stateful Proxy Operating Modes
Mediant 1000B Gateway & E-SBC • 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. •...
Page 607 User's Manual 28. SBC Overview the original value with itself in the incoming message. In contrast, when the device operates in Stateful Proxy mode, the device by default forwards SIP messages transparently (unchanged) between SIP endpoints (from inbound to outbound legs). The device retains the SIP dialog identifiers and topology headers received in the incoming message and sends them as is in the outgoing message.
Page 608 Mediant 1000B Gateway & E-SBC 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:  SRDs in the SRDs table (see ''Configuring SRDs'' on page 317) ...
Page 609: Call Processing Of Sip Dialog Requests
User's Manual 28. SBC Overview 28.3 Call Processing of SIP Dialog Requests The device processes incoming SIP dialog requests (SIP methods) such as INVITE, SUBSCRIBE, OPTIONS, REFER, INFO, UNSOLICITED NOTIFY, MESSAGE, and REGISTER. The process is summarized in the following figure and subsequently described: Figure 28-2: SBC Call Processing The SIP dialog-initiating process consists of the following stages:...
Page 610 Mediant 1000B Gateway & E-SBC • All SIP requests (e.g., INVITE) except REGISTER: ♦ Source URL: Obtained from the From header. If the From header contains the value 'Anonymous', the source URL is obtained from the P-Preferred- Identity header. If the P-Preferred-Identity header does not exist, the source URL is obtained from the P-Asserted-Identity header.
Page 611: User Registration
User's Manual 28. SBC Overview manipulation rule is associated with the dialog, by configuring the rule with incoming matching characteristics such as source IP Group and destination host name. The manipulation rules are also assigned a Routing Policy, which in turn, is assigned to IP- to-IP routing rules.
Page 612: Classification And Routing Of Registered Users
Mediant 1000B Gateway & E-SBC The device provides a dynamic registration database that it updates according to registration requests traversing it. Each database entry for a user represents a binding between an AOR (obtained from the SIP To header), optional additional AORs, and one or more contacts (obtained from the SIP Contact headers).
Page 613: General Registration Request Processing
User's Manual 28. SBC Overview When an incoming INVITE is received for routing to a user and the user is located in the registration database, the device sends the call to the user's corresponding contact address specified in the database. Note: If the Request-URI contains the "tel:"...
Page 614: Registration Restriction Control
Mediant 1000B Gateway & E-SBC user from the database only when this additional time expires. 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 the registrar/proxy server.
Page 615: Media Anchoring
User's Manual 28. SBC Overview  Other (standard or proprietary) media and session characteristics Typically, the device does not change the negotiated media capabilities (mainly performed by the remote user agents). However, it does examine and may take an active role in the SDP offer-answer mechanism.
Page 616: Direct Media
Mediant 1000B Gateway & E-SBC Interfaces table) is used. The following figure provides an example of SDP handling for a call between a LAN IP Phone 10.2.2.6 and a remote IP Phone 212.179.1.13 on the WAN. Figure 28-3: SDP Offer/Answer Example 28.5.2 Direct Media You can configure the device to allow the media (RTP/SRTP) session to flow directly between the SIP endpoints, without traversing the device.
Page 617 User's Manual 28. SBC Overview Direct media is typically implemented for calls between users located in the same LAN or domain, and where NAT traversal is not required and other media handling features such as media transcoding is not required. The following figure provides an example of direct media between LAN IP phones, while SIP signaling continues to traverse the device between LAN IP phones and the hosted WAN IP-PBX.
Page 618: Restricting Audio Coders
Mediant 1000B Gateway & E-SBC Direct Media' parameter is set to Enable (SIPInterface_SBCDirectMedia = 1). IP Groups of the endpoints use the same SIP Interface and the SIP Interface's 'SBC Direct Media' parameter Enable When Single (SIPInterface_SBCDirectMedia = 2), and the endpoints are located behind the same NAT.
Page 619: Coder Transcoding
User's Manual 28. SBC Overview  The allowed coders configured for the SIP entity include G.711 and G.729. The device removes the G.723 coder from the SDP offer, re-orders the coder list so that G.711 is listed first, and sends the SIP message containing only the G.711 and G.729 coders in the SDP.
Page 620 Mediant 1000B Gateway & E-SBC The figure below illustrates transcoding between two SIP entities (IP Groups) where one uses G.711 (LAN IP phone) and the other G.729 (WAN IP phone). The initial SDP offer received on the inbound leg from the LAN IP phone includes coder G.711 as the supported coder.
Page 621 User's Manual 28. SBC Overview Note: • If you assign a SIP entity an Allowed Audio Coders Group for coder restriction (allowed coders) and a Coders Group for extension coders, the allowed coders take precedence over the extension coders. In other words, if an extension coder is not listed as an allowed coder, the device does not add the extension coder to the SDP offer.
Page 622 Mediant 1000B Gateway & E-SBC that do not appear in the Allowed Audio Coders Group for coder restriction. m=audio 6050 RTP/AVP 0 8 18 96 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:4 annexa=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:20 a=sendrecv On the outbound leg for the outgoing SDP offer: The SDP offer now includes only the G.711 and G.729 coders due to the coder restriction process on the incoming SDP offer (see Step 1).
Page 623: Transcoding Mode
User's Manual 28. SBC Overview Note: • To implement transcoding, you must configure the number of required DSP channels for transcoding (for example, MediaChannels = 120). Each transcoding session uses two DSP resources. • The transcoding mode can be configured globally, using the TranscodingMode parameter or for specific calls, using the IP Profiles table.
Page 624: Srtp-Rtp And Srtp-Srtp Transcoding
Mediant 1000B Gateway & E-SBC However, if Extension coders are also used, the coder list is arranged according to the SBCPreferencesMode parameter. Depending on the parameter's settings, the Extension coders are added after the Allowed coders according to their order in the Allowed Audio Coders Group, or the Allowed and Extension coders are arranged according to their position in the Allowed Audio Coders Group.
Page 625: Interworking Dtmf Methods
User's Manual 28. SBC Overview 28.5.9.1 Interworking DTMF Methods The device supports interworking between various DTMF methods such as RFC 2833, In- Band DTMF’s, and SIP INFO (Cisco\Nortel\Korea). By default, the device allows the remote user agents to negotiate (in case of RFC 2833) and passes DTMF without intervention.
Page 626: Fax Negotiation And Transcoding
Mediant 1000B Gateway & E-SBC 28.6 Fax Negotiation and Transcoding The device can allow fax transmissions to traverse transparently without transcoding or it can handle the fax as follows:  Allow interoperability between different fax machines, supporting fax transcoding if required.
Page 627: Sbc Authentication
User's Manual 28. SBC Overview In the 'Max Call Duration' field (SBCMaxCallDuration), enter the maximum call duration per SBC call: Figure 28-6: Configuring Maximum Call Duration Click Apply. 28.8 SBC Authentication The device can authenticate SIP servers and SBC users (clients). The different authentication methods are described in the subsequent subsections.
Page 628: User Authentication Based On Radius
Mediant 1000B Gateway & E-SBC The device's Authentication server functionality is configured per IP Group, using the 'Authentication Mode' parameter in the IP Groups table (see ''Configuring IP Groups'' on page 333). 28.8.2 User Authentication based on RADIUS The device can authenticate SIP clients (users) using a remote RADIUS server. The device supports the RADIUS extension for digest authentication of SIP clients, according to draft- sterman-aaa-sip-01.
Page 629 User's Manual 28. SBC Overview the LAN and the new contact is on the WAN). In such a scenario, the device enables the user to reach the WAN contact and overcome NAT problems.  Enforce certain SBC policies (e.g., call admission control, header manipulation, and transcoding) on the resultant INVITE.
Page 630: Local Handling Of Sip 3Xx
Mediant 1000B Gateway & E-SBC sip:Prefix_Key_User@SBC:5070;transport=udp). Upon receipt of the new request from the FEU, the device replaces the Request-URI with destination address (e.g., RequestURI: sip:Prefix_User@IPPBX:5070;transport=tcp;param=a). The device removes the user prefix from the Request-URI, and then sends this Request-URI destination (e.g., RequestURI:...
Page 631: Interworking Sip Refer Messages
User's Manual 28. SBC Overview Parameter Value SIP Header Present in Received SIP Message HistoryInfoMode = Not present. History-Info History-Info added to Diversion. Disable converted to Diversion. DiversionMode = Add Diversion History-Info Headers are synced and sent. HistoryInfoMode = Add converted to converted to DiversionMode = Add...
Page 632: Interworking Sip Session Timer
Mediant 1000B Gateway & E-SBC sessions between such endpoints. SIP PRACK handling is configured using the IP Profile parameter, 'SBC Prack Mode':  Optional: PRACK is optional for these UAs. If required, the device performs the PRACK process on behalf of the destination UA. ...
Page 633 User's Manual 28. SBC Overview only, and is configured by the IP Profile parameter, 'SBC Remote Early Media Response Type'.  Multiple 18x: The device supports the interworking of different support for multiple 18x responses (including 180 Ringing, 181 Call is Being Forwarded, 182 Call Queued, and 183 Session Progress) that are forwarded to the caller.
Page 634: Interworking Sip Re-Invite Messages
Mediant 1000B Gateway & E-SBC Figure 28-9: Early Media RTP - SIP 18x with SDP 28.9.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 635: Interworking Sip Re-Invite To Update
User's Manual 28. SBC Overview bridge the media between the endpoints. The handling of UPDATE messages is configured by the IP Profile parameter 'SBC Remote Update Support'. 28.9.9 Interworking SIP re-INVITE to UPDATE The device enables communication between endpoints (IP Groups) that do not support re- INVITE requests but support the UPDATE method, and vice versa.
Page 636: Interworking Sip Via Headers
Mediant 1000B Gateway & E-SBC 28.9.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.
Page 637: Enabling The Sbc Application
User's Manual 29. Enabling the SBC Application Enabling the SBC Application Before you can start configuring the SBC, you must first enable the SBC application. Once enabled, the Web interface displays the menus and parameter fields relevant to the SBC application.
Page 638 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 639: 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 1187).
Page 640 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 641: Configuring General Sbc Settings
User's Manual 31. Configuring General SBC Settings Configuring General SBC Settings This section describes configuration of various SBC features. 31.1 Interworking Dialog Information in SIP NOTIFY Messages You can enable the device to interwork dialog information (XML body) received in SIP NOTIFY messages from a remote (WAN) application server.
Page 642 Mediant 1000B Gateway & E-SBC 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"> sip:cjones@example.net </identity>...
Page 643: Configuring Admission Control
User's Manual 32. Configuring Admission Control Configuring Admission Control The Admission Control table lets you configure up to 102 Call Admission Control rules (CAC). CAC rules define the maximum number of concurrent calls (SIP dialogs) permitted per IP Group, SIP Interface or SRD, and per user (identified by its registered contact). CAC rules also define a guaranteed (reserved) number of concurrent calls.
Page 644 Mediant 1000B Gateway & E-SBC routing rule exists, the device rejects the SIP request with a SIP 480 "Temporarily Unavailable" response. Note: The device applies the CAC rule for the incoming leg immediately after the Classification process. If the call/request is rejected at this stage, no routing is performed.
Page 645 User's Manual 32. Configuring Admission Control Parameter Description Name Defines an arbitrary name to easily identify the row. admission-name The valid value is a string of up to 20 characters. By default, no value is defined. [SBCAdmissionControl_Adm issionControlName] Limit Type Defines the entity to which the rule applies.
Page 646 Mediant 1000B Gateway & E-SBC Parameter Description Limit Defines the maximum number of concurrent SIP dialogs per IP Group, SIP Interface or SRD. You can also use the following special values: limit  [0] 0 = Block all these dialogs. [SBCAdmissionControl_Limit ...
Page 647: Routing Sbc
User's Manual 33. Routing SBC Routing SBC This section describes the configuration of the call routing entities for the SBC application. 33.1 Configuring Classification Rules The Classification table lets you configure up to 102 Classification rules. A Classification rule classifies incoming SIP dialog-initiating requests (e.g., INVITE messages) to a "source" IP Group.
Page 648 Mediant 1000B Gateway & E-SBC From the 'Unclassified Calls' drop-down list, select Reject to reject unclassified calls or Allow to accept unclassified calls: Figure 33-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 dialog request was received and the SIP Interface configured with this port (in the SIP...
Page 649 User's Manual 33. Routing SBC Selects the Proxy Set whose IP address, port, and transport type match the source of the incoming dialog. If no match is found for a), it selects the Proxy Set whose IP address and transport type match the source of the incoming dialog (if the 'Classification Input' parameter is configured to IP Address Only).
Page 650 Mediant 1000B Gateway & E-SBC The flowchart below illustrates the classification process: Figure 33-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 > sbc classification).
Page 651 User's Manual 33. Routing SBC Click New; the following dialog box appears: Figure 33-3: Classification Table - Add Dialog Box Configure the Classification rule according to the parameters described in the table below. Click Apply. Table 33-1: Classification Table Parameter Descriptions Parameter Description Assigns an SRD to the rule as a matching characteristic for the...
Page 652 Mediant 1000B Gateway & E-SBC Parameter Description Note: The SIP Interface must belong to the SRD assigned to the rule (see the 'SRD' parameter in the table). Source IP Address Defines a source IP address as a matching characteristic for the incoming SIP dialog.
Page 653 User's Manual 33. Routing SBC Parameter Description of SIP Dialog Requests'' on page 609. The default is the asterisk (*) symbol, which represents any source host prefix. Note: For REGISTER requests, the source URI is obtained from the To header. Destination Username Prefix Defines the prefix of the destination Request-URI user part as a matching characteristic for the incoming SIP dialog.
Page 654: Classification Based On Uri Of Selected Header Example
Mediant 1000B Gateway & E-SBC Parameter Description ip-profile-id Group (in the IP Groups table) to which the SIP dialog is classified. Therefore, assigning an IP Profile during classification allows you to [Classification_IpProfileNam assign different IP Profiles to specific users (calls) that belong to the same IP Group (User or Server type).
Page 655: Configuring Message Condition Rules
User's Manual 33. Routing SBC Index Source URI Input Destination URI Input P-Called-Party-ID Route In the example, a match exists only for Classification Rule #1. This is because the source (1111) and destination (2000) username prefixes match those in the INVITE's P-Called- Party-ID header (i..e.,...
Page 656: Configuring Sbc Ip-To-Ip Routing
Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 33-4: Message Conditions Table - Add Dialog Box Configure a Message Condition rule according to the parameters described in the table below. Click Apply. An example of configured Message Condition rules is shown in the figure below: Figure 33-5: Example of Configured SIP Message Conditions ...
Page 657 User's Manual 33. Routing SBC The device searches the table from top to bottom for the first rule that matches the characteristics of the incoming call. If it finds a matching rule, it sends the call to the destination configured for that rule. If it doesn't find a matching rule, it rejects the call. Note: Configure stricter rules higher up in the table than less strict rules to ensure the desired rule is used to route the call.
Page 658 Mediant 1000B Gateway & E-SBC To configure and apply an IP-to-IP Routing rule, the rule must be associated with a Routing Policy. The Routing Policy associates the routing rule with an SRD(s). Therefore, the Routing Policy lets you configure routing rules for calls belonging to specific SRD(s). However, as multiple Routing Policies are relevant only for multi-tenant deployments (if needed), for most deployments, only a single Routing Policy is required.
Page 659 User's Manual 33. Routing SBC requests (e.g., INVITEs) that the device sends upon receipt of SIP 3xx responses or REFER messages. These rules are configured for destinations that do not support receipt of 3xx or REFER and where the device handles the requests locally (instead of forwarding the 3xx or REFER to the destination).
Page 660 Mediant 1000B Gateway & E-SBC destination, you can employ user-defined tags to represent these numbers. Thus, instead of configuring many routing rules, you can configure only one routing rule using the tag as the source and destination number matching characteristics, and a destination for the calls.
Page 661 User's Manual 33. Routing SBC Parameter Description If only one Routing Policy is configured in the Routing Policies table, the Routing Policy is automatically assigned. If multiple Routing Policies are configured, no value is assigned. To configure Routing Policies, see ''Configuring SBC Routing Policy Rules'' on page 670.
Page 662 Mediant 1000B Gateway & E-SBC Parameter Description configured in the Alternative Routing Reasons table.  Multiple alternative route entries can be configured (e.g., Index 1 is the main route - Route Row - and indices 2 through 4 are configured as alternative routes). Match Source IP Group Defines the IP Group from where the IP call is received (i.e., the...
Page 663 User's Manual 33. Routing SBC Parameter Description specific URI source user or all source users. Destination Username Prefix Defines the prefix of the incoming SIP dialog's destination URI (usually the Request URI) user part. You can use special dst-user-name-prefix notations for denoting the prefix. To denote calls without a user [IP2IPRouting_DestUsernamePrefi part in the URI, use the $ sign.
Page 664 Mediant 1000B Gateway & E-SBC Parameter Description configured to [2]), you can use this option as an explicit matching characteristics to route the call to an alternative destination. Therefore, for alternative routing upon broken RTP detection, position the routing rule configured with this option above the regular routing rule associated with the call.
Page 665 User's Manual 33. Routing SBC Parameter Description below: [ PLAN6 ] 200,0,10.33.8.52 ; called prefix 200 is routed to destination 10.33.8.52 201,0,10.33.8.52 300,0,itsp.com ; called prefix 300 is routed to destination itsp.com Once the Dial Plan is defined, you need to assign it (0 to 7) to the routing rule as the destination in the 'Destination Address' parameter, where "0"...
Page 666 Mediant 1000B Gateway & E-SBC Parameter Description Note:  The parameter is applicable only if the 'Destination Type' parameter is configured to IP Group.  The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in this table).
Page 667 User's Manual 33. Routing SBC Parameter Description handle them locally), set the parameter to "internal". Destination Port Defines the destination port to where the call is sent. dst-port [IP2IPRouting_DestPort] Destination Transport Type Defines the transport layer type for sending the call: ...
Page 668: Configuring Sip Response Codes For Alternative Routing Reasons
Mediant 1000B Gateway & E-SBC Parameter Description matching routing rules that are assigned Cost Groups, the first-matched routing rule without an assigned Cost Group is considered as the lowest cost route and thus, chosen as the preferred route. 33.4 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.
Page 669 User's Manual 33. Routing SBC Note: • If the device receives a SIP 408 response, an ICMP message, or no response, alternative routing is still performed even if the code is not configured in the Alternative Routing Reasons table. • SIP requests belonging to an SRD or IP Group that have reached the call limit (maximum concurrent calls and/or call rate) as configured in the Call Admission table are sent to an alternative route if configured in the IP-to-IP Routing table for...
Page 670: Configuring Sbc Routing Policy Rules
Mediant 1000B Gateway & E-SBC Parameter Description Unavailable; [481] Transaction Not Exist; [482] Loop Detected; [483] Too Many Hops; [484] Address Incomplete; [485] Ambiguous; [486] Busy; [487] Request Terminated; [488] Not Acceptable Here; [491] Request Pending; [493] Undecipherable; [500] Internal Error; [501] Not Implemented;...
Page 671 User's Manual 33. Routing SBC Routing Policy to routing and manipulation rules. The figure below shows the configuration entities to which Routing Policies can be assigned: Typically, assigning a Routing Policy to a Classification rule is not required, as when an incoming call is classified it uses the Routing Policy associated with the SRD to which it belongs.
Page 672 Mediant 1000B Gateway & E-SBC Note: • The Classification table is used only if classification by registered user in the device's users registration database or by Proxy Set fails. • If the device receives incoming calls (e.g., INVITE) from users that have already been classified and registered in the device's registration database, the device ignores the Classification table and uses the Routing Policy that was determined for the user during the initial classification process.
Page 673 User's Manual 33. Routing SBC Parameter Description [SBCRoutingPolicy_Name] automatically assigns a name in the following format: "SBCRoutingPolicy_<Index>", for example, "SBCRoutingPolicy_2". Note: Each row must be configured with a unique name. LDAP Servers Group Name Assigns an LDAP Server Group to the Routing Policy. Routing rules in the IP-to-IP Routing table that are ldap-srv-group-name associated with the Routing Policy and that are configured...
Page 674: Configuring Ip Group Sets
Mediant 1000B Gateway & E-SBC Parameter Description the lower cost. However, if the average call duration is more than one minute, "Weekend B" carries the lower cost. 33.6 Configuring IP Group Sets The IP Group Set table lets you configure up to 51 IP Group Sets. An IP Group Set is a group of IP Groups used for load balancing of calls, belonging to the same source, to a call destination (i.e., IP Group).
Page 675 User's Manual 33. Routing SBC Click New; the following dialog box appears: Figure 33-9: IP Group Set Table - Dialog Box Configure the IP Group Set according to the parameters described in the table below. Click Apply. Table 33-6: IP Group Set Table Parameter Descriptions Parameter Description General...
Page 676 Mediant 1000B Gateway & E-SBC Parameter Description value per IP Group. 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.
Page 677: Sbc Manipulations
User's Manual 34. SBC Manipulations SBC Manipulations This section describes the configuration of the manipulation rules for the SBC application. Note: For additional manipulation features, see the following: • ''Configuring SIP Message Policy Rules''. • ''Configuring SIP Message Manipulation'' on page 368. The device supports SIP URI user part (source and destination) manipulations for inbound and outbound routing.
Page 678 Mediant 1000B Gateway & E-SBC CSeq: 1 INVITE Contact: <sip:7000@10.2.2.3> Supported: em,100rel,timer,replaces Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK User-Agent: Sip Message Generator V1.0.0.5 Content-Type: application/sdp Content-Length: 155 o=SMG 791285 795617 IN IP4 10.2.2.6 s=Phone-Call c=IN IP4 10.2.2.6 t=0 0 m=audio 6000 RTP/AVP 8 a=rtpmap:8 pcma/8000 a=sendrecv a=ptime:20 ...
Page 679: Configuring Ip-To-Ip Inbound Manipulations
User's Manual 34. SBC Manipulations INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>  Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone> 34.1 Configuring IP-to-IP Inbound Manipulations The Inbound Manipulations table lets you configure up to 205 IP-to-IP Inbound Manipulation rules.
Page 680 Mediant 1000B Gateway & E-SBC 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 670. Note: The IP Groups table can be used to configure a host name that overwrites the received host name.
Page 681 User's Manual 34. SBC Manipulations Parameter Description table, the Routing Policy is automatically assigned. If multiple Routing Policies are configured, no value is assigned. To configure Routing Policies, see ''Configuring SBC Routing Policy Rules'' on page 670. Note: The parameter is mandatory. General Index Defines an index number for the new table record.
Page 682 Mediant 1000B Gateway & E-SBC Parameter Description Source IP Group Defines the IP Group from where the incoming INVITE is CLI: src-ip-group-name received. [IPInboundManipulation_SrcIp The default is Any (i.e., any IP Group). GroupName] Source Username Prefix Defines the prefix of the source SIP URI user name (usually in CLI: src-user-name-prefix the From header).
Page 683: Configuring Ip-To-Ip Outbound Manipulations
User's Manual 34. SBC Manipulations Parameter Description Prefix to Add Defines the number or string that you want added to the front of CLI: prefix-to-add the user name. For example, if you enter 'user' and the user [IPInboundManipulation_Prefix name is "john", the new user name is "userjohn". 2Add] Suffix to Add Defines the number or string that you want added to the end of...
Page 684 Mediant 1000B Gateway & E-SBC  To configure Outbound Manipulation rules: Open the Outbound Manipulations table (Setup menu > Signaling & Media tab > SBC folder > Manipulation > Outbound Manipulations). Click New; the following dialog box appears: Figure 34-3: Outbound Manipulations Table- Add Dialog Box Configure an Outbound Manipulation rule according to the parameters described in the table below.
Page 685 User's Manual 34. SBC Manipulations Parameter Description Additional Manipulation Determines whether additional manipulation is done for the table entry rule listed directly above it. is-additional-manipulation  [0] No = (Default) Regular manipulation rule - not done in addition [IPOutboundManipulation_IsA to the rule above it. dditionalManipulation] ...
Page 686 Mediant 1000B Gateway & E-SBC Parameter Description Note: If you need to manipulate calls of many different source URI user names, you can use tags (see 'Source Tags' parameter below) instead of this parameter. Source Host Defines the source SIP URI host name - full name, typically in the From header.
Page 687 User's Manual 34. SBC Manipulations Parameter Description message-condition-name To configure Message Condition rules, see ''Configuring Message Condition Rules'' on page 655. [IPOutboundManipulation_Me ssageConditionName] ReRoute IP Group Defines the IP Group that initiated (sent) the SIP redirect response (e.g., 3xx) or REFER message. The parameter is typically used for re-route-ip-group-name re-routing requests (e.g., INVITEs) when interworking is required for [IPOutboundManipulation_Re...
Page 688 Mediant 1000B Gateway & E-SBC Parameter Description fix2Add] 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.
Page 689: Configuring Dial Plans
User's Manual 35. Configuring Dial Plans Configuring Dial Plans Dial Plans let you categorize users (source and/or destination) according to source and/or destination numbers of the incoming SIP dialog-initiating requests. The device categorizes users by searching in the Dial Plan for rules that match these numbers according to prefix, suffix, and/or whole number.
Page 690 Mediant 1000B Gateway & E-SBC  Tag: The tag corresponds to the matched prefix of the source and/or destination number and is the categorization result. You can use various syntax notations to configure the prefix numbers in dial plan rules. You can configure the prefix as a complete number (all digits) or as a partial number using some digits and various syntax notations (patterns) to allow the device to match a dial pan rule for similar source and/or destination numbers.
Page 691 User's Manual 35. Configuring Dial Plans 53([2-4]),A 531(4),B  For incoming calls with prefix number "321444", the rule with tag A is chosen and for incoming calls with prefix number "32144", the rule with tag B is chosen: 321xxx,A 321,B ...
Page 692 Mediant 1000B Gateway & E-SBC Table 35-2: Dial Plan Table Parameter Descriptions Parameter Description Index Defines an index number for the new table row. [DialPlans_Index] Note: Each row must be configured with a unique index. Name Defines an arbitrary name to easily identify the row. name The valid value is a string of up to 15 characters.
Page 693: Importing And Exporting Dial Plans
User's Manual 35. Configuring Dial Plans Parameter Description  *: (Asterisk symbol) If it is the only character in the rule, it denotes any number. To denote the asterisk "*" symbol itself, precede it with the escape "\\" character (see below). ...
Page 694 Mediant 1000B Gateway & E-SBC From the 'Action' drop-down menu, choose Export; the following dialog box appears: Figure 35-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 695 User's Manual 35. Configuring Dial Plans From the 'Action' drop-down menu, choose Import; the following dialog box appears: Figure 35-5: 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 696: Creating Dial Plan Files
Mediant 1000B Gateway & E-SBC From the 'Action' drop-down menu, choose Import; the following dialog box appears: Figure 35-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. Note: The rules in the imported file replace all existing rules of the specific Dial Plan.
Page 697: Using Dial Plan Tags For Ip-To-Ip Routing
User's Manual 35. Configuring Dial Plans 35.3 Using Dial Plan Tags for IP-to-IP Routing For deployments requiring hundreds of routing rules (which may exceed the maximum number of rules that can be configured in the IP-to-IP Routing table), you can employ tags to represent the many different calling (source URI user name) and called (destination URI user name) prefix numbers in your routing rules.
Page 698: Dial Plan Backward Compatibility
Mediant 1000B Gateway & E-SBC 35.3.1 Dial Plan Backward Compatibility Note: This section is for backward compatibility only. It is recommended to migrate your Dial Plan configuration to the latest Dial Plan feature (see ''Using Dial Plan Tags for IP-to-IP Routing'' on page 697). Configure prefix tags in the Dial Plan file using the following syntax: [ PLAN<index>...
Page 699: Using Dial Plan Tags For Outbound Manipulation
User's Manual 35. Configuring Dial Plans Add an SBC IP-to-IP routing rule using the prefix tag to represent the different source or destination URI user parts: Open the IP-to-IP Routing table (see ''Configuring SBC IP-to-IP Routing Rules'' on page 656), and then click New. Configure the prefix tag in the 'Source Username Prefix' or 'Destination Username Prefix' fields (e.g., "LOCL", without the quotes).
Page 700: Using Dial Plan Tags For Call Setup Rules
Mediant 1000B Gateway & E-SBC 35.5 Using Dial Plan Tags for Call Setup Rules You can use Dial Plan tags in Call Setup rules, configured in the Call Setup Rules table (see Configuring Call Setup Rules on page 377). The Call Setup rule can be assigned to an IP Group and is processed by the device for the classified source IP Group immediately before the routing process (i.e., Classification >...
Page 701: Configuring Malicious Signatures
User's Manual 36. Configuring Malicious Signatures Configuring Malicious Signatures The Malicious Signature table lets you configure up to 30 Malicious Signature patterns. Malicious Signatures are signature patterns that identify SIP user agents (UA) who perform malicious attacks on SIP servers by SIP scanning. Malicious Signatures allow you to protect SBC calls handled by the device from such malicious activities, thereby increasing your SIP security.
Page 702 Mediant 1000B Gateway & E-SBC  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 36-1: Malicious Signature Table - Add Dialog Box Configure a Malicious Signature according to the parameters described in the table below.
Page 703: Advanced Sbc Features
User's Manual 37. Advanced SBC Features Advanced SBC Features 37.1 Configuring Call Preemption for SBC Emergency Calls The device supports emergency call preemption for SBC calls by prioritizing emergency calls over regular calls. If the device receives an incoming emergency call when there are unavailable resources to process the call, the device preempts one of the regular calls to free up resources for sending the emergency call to its' destination (i.e., emergency service provider), instead of rejecting it.
Page 704: Emergency Call Routing Using Ldap To Obtain Elin
Mediant 1000B Gateway & E-SBC 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 37-2: Configuring Emergency SBC Call Preemption From the 'Preemption Mode' drop-down list (SBCPreemptionMode), select Enable to enable call preemption.
Page 705: Enabling Interworking Of Sip And Sip-I Endpoints
User's Manual 37. Advanced SBC Features  To enable emergency call routing using LDAP to obtain ELIN: Configure a Call Setup rule in the Call Setup Rules table (see ''Configuring Call Setup Rules'' on page 377). The following example shows a Call Setup rule that queries an Active Directory (AD) server for the attribute "telephoneNumber"...
Page 706 Mediant 1000B Gateway & E-SBC 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 707: Call Forking
''Configuring SIP Message Manipulation'' on page 368). 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 708: Configuring Sip Forking Initiated By Sip Proxy
Mediant 1000B Gateway & E-SBC 37.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 709: Enabling Auto-Provisioning Of Subscriber-Specific Information Of Broadworks Server For Survivability
User's Manual 37. Advanced SBC Features 37.5.1 Enabling Auto-Provisioning of Subscriber-Specific Information of BroadWorks Server for Survivability This feature enables SBC user registration for interoperability with BroadSoft BroadWorks server to provide call survivability in case of connectivity failure with the BroadWorks server, for example, due to a WAN failure.
Page 710: Configuring Broadsoft's Shared Phone Line Call Appearance For Survivability
Mediant 1000B Gateway & E-SBC 37.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 711: Configuring Call Survivability For Call Centers
User's Manual 37. Advanced SBC Features In the Inbound Manipulations table (see ''Configuring IP-to-IP Inbound Manipulations'' on page 679), add a manipulation rule for the secondary extensions (e.g., 601 and 602) so that they also register to the device's database under the primary extension contact (e.g., 600): •...
Page 712 Mediant 1000B Gateway & E-SBC Figure 37-8: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Groups table (see ''Configuring IP Groups'' on page 333), add IP Groups for the following entities: •...
Page 713: Enabling Survivability Display On Aastra Ip Phones
User's Manual 37. Advanced SBC Features The figure below displays a routing rule example, assuming IP Group "1" represents the TDM Gateway and IP Group "3" represents the call center agents: Figure 37-9: Routing Rule Example for Call Center Survivability 37.5.4 Enabling Survivability Display on Aastra IP Phones If the SBC device is deployed in an Enterprise network with Aastra IP phones and connectivity with the WAN fails, the device provides call survivability by enabling...
Page 714: Alternative Routing On Detection Of Failed Sip Response
Mediant 1000B Gateway & E-SBC 37.6 Alternative Routing on Detection of Failed SIP Response The device can detect failure of a sent SIP response (e.g., TCP timeout, and UDP ICMP). In such a scenario, the device re-sends the response to an alternative destination. This support is in addition to alternative routing if the device detects failed SIP requests.
Page 715: Cloud Resilience Package
Part VII Cloud Resilience Package...
Page 717: Crp Overview
User's Manual 38. CRP Overview CRP Overview The device's Cloud Resilience Package (CRP) application enhances cloud-based or hosted communications environments by ensuring survivability, high voice quality and security at enterprise branch offices and cloud service customer premises. CRP is designed to be deployed at customer sites and branches of: ...
Page 718 Mediant 1000B Gateway & E-SBC Survivability Quality of Experience/Service Security  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 719: Crp Configuration
User's Manual 39. CRP Configuration CRP Configuration This section describes configuration specific to the CRP application. As CRP has similar functionality to the SBC application, for configuration that is common to the SBC, which is not covered in this section, see the following SBC sections: ...
Page 720 Mediant 1000B Gateway & E-SBC  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 721: Pre-Configured Ip Groups
User's Manual 39. CRP Configuration  Always Emergency: The CRP routes the calls between the branch users themselves as if connectivity failure has occurred with the IP PBX. The CRP also registers the branch users in its registration database. Figure 39-2: CRP in Always Emergency Mode ...
Page 722: Pre-Configured Ip-To-Ip Routing Rules
Mediant 1000B Gateway & E-SBC 39.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 719. Note: •...
Page 723: Auto Answer To Registrations
User's Manual 39. CRP Configuration Mode Index Source IP Request Destination Destination Destination Alternative Group ID / Type Type IP Group Address Route Emergency Options OPTIONS Dest Internal Route Row Always Emergency Address IP Group Route Row IP Group Alternative IP Group Route Row 39.4.3 Auto Answer to Registrations...
Page 724 Mediant 1000B Gateway & E-SBC To enable this feature, set the ini file parameter CRPGatewayFallback to 1. When enabled, the alternative routing rule appears immediately below the IP Group 2 to IP Group 1 rule in the IP-to-IP Routing table. Note: •...
Page 725: Maintenance
Part VIII Maintenance...
Page 727: Basic Maintenance
User's Manual 40. Basic Maintenance Basic Maintenance This section describes basic maintenance procedures. 40.1 Resetting the Device You can reset the device through the device's management tools. Device reset may be required for maintenance purposes. Certain parameters require a device reset for their settings to take effect.
Page 728: 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 729: Locking And Unlocking The Device
User's Manual 40. Basic Maintenance 40.3 Locking and Unlocking the Device You can lock the device so that it doesn't accept any new calls, maintaining only current calls. This may be useful, for example, when uploading new software files to the device and you don't want any traffic to interfere with the process.
Page 730: Saving Configuration
Mediant 1000B Gateway & E-SBC 40.4 Saving Configuration When you configure parameters and tables in the Web interface and then click the Apply button on the pages in which the configurations are done, changes are saved to the device's volatile memory (RAM). These changes revert to their previous settings if the device subsequently resets (hardware or software) or powers down.
Page 731: Replacing Modules
User's Manual 41. Replacing Modules Replacing Modules To replace the device's modules, you must use the Web interface in combination with physical removal and insertion of the modules. Therefore, when you replace a module, you first need to 'software-remove' it, extract it physically from the chassis, insert a new module, and then 'software-insert' it using the Web interface.
Page 732 Mediant 1000B Gateway & E-SBC Insert the new module: Physically insert the new module into the same chassis slot in which the previous module was housed (refer to the Hardware Installation Manual). On the Monitor home page, click the title of the module ("<module type> Reserved") that you are replacing;...
Page 733: Channel Maintenance
User's Manual 42. Channel Maintenance Channel Maintenance This chapter describes various channel-related maintenance procedures. 42.1 Resetting an Analog Channel You can reset an analog (FXO or FXS) channel by disconnecting the current call (if exists). This is sometimes useful, for example, when the device (FXO) is connected to a PBX and communication between the two cannot be disconnected (e.g., when using reverse polarity).
Page 734: Locking And Unlocking Trunk Groups
Mediant 1000B Gateway & E-SBC 42.3 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 735: Disconnecting Active Calls
User's Manual 42. Channel Maintenance • "Going Out Of Service (<duration remaining of graceful period> sec / <number of calls still active> calls)": Appears when the device is locking the Trunk Group and indicates the number of buys channels and the time remaining until the graceful period ends, after which the device locks the channels regardless of whether the call has ended or not.
Page 736 Mediant 1000B Gateway & E-SBC From the shortcut menu, choose Port Description; the following dialog box appears: Figure 42-4: Configuring Analog Port Description Type a brief description for the port, and then click Submit. User's Manual Document #: LTRT-27045...
Page 737: Software Upgrade
User's Manual 43. Software Upgrade Software Upgrade This chapter describes various software update procedures. 43.1 Auxiliary Files You can load various Auxiliary files to the device. Auxiliary files provide the device with additional configuration. The table below lists the different types of Auxiliary files. Table 43-1: Auxiliary Files File Description...
Page 738: Loading Auxiliary Files Through Web Interface
Mediant 1000B Gateway & E-SBC Note: • You can automatically load Auxiliary files from a remote server using the device's Automatic Update mechanism (see Automatic Update Mechanism). • Saving Auxiliary files to flash memory may disrupt traffic on the device. To avoid this, disable all traffic on the device by performing a graceful lock as described in ''Locking and Unlocking the Device'' on page 729.
Page 739: Loading Auxiliary Files Through Cli
User's Manual 43. Software Upgrade Click the Browse button corresponding to the Auxiliary file type that you want to load, navigate to the folder in which the file is located, and then click Open; the name of the file appears next to the Browse button. Click the corresponding Load File button.
Page 740 (in any 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.
Page 741 User's Manual 43. Software Upgrade ♦ [8] Confirmation Tone ♦ [9] Call Waiting Tone (heard by the called party) ♦ [15] Stutter Dial Tone ♦ [16] Off Hook Warning Tone ♦ [17] Call Waiting Ringback Tone (heard by the calling party) ♦...
Page 742: Distinctive Ringing
Mediant 1000B Gateway & E-SBC Note: • When the same frequency is used for a continuous tone and a cadence tone, the 'Signal On Time' parameter of the continuous tone must have a value that is greater than the 'Signal On Time' parameter of the cadence tone. Otherwise, the continuous tone is detected instead of the cadence tone.
Page 743 User's Manual 43. Software Upgrade • First (Burst) Ring On Time [10 msec]: 'Ring On' period (in 10 msec units) for the first cadence on-off cycle. • First (Burst) Ring Off Time [10 msec]: 'Ring Off' period (in 10 msec units) for the first cadence on-off cycle.
Page 744: Prerecorded Tones File
For SBC calls, the PRT file supports only the ringback tone and hold tone. The prerecorded tones can be created using standard third-party, recording utilities such as Adobe Audition, and then combined into a single file (PRT file) using AudioCodes DConvert utility. For more information, refer to DConvert Utility User's Guide.
Page 745: Voice Prompts File
User's Manual 43. Software Upgrade Once created, you need to install the PRT file on the device. This can be done using the Web interface (see ''Loading Auxiliary Files'' on page 737). 43.1.5 Voice Prompts File The Voice Prompts (VP) file contains a set of voice prompts (or announcements) and/or .wav files that can be played by the device during operation.
Page 746: 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 737.
Page 747: 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 748 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 737.
Page 749: Dial Plan Prefix Tags For Ip-To-Tel Routing
User's Manual 43. Software Upgrade In the 'Digit Mapping Rules' field, enter the digit map. Figure 43-2: Configuring Digit Map and Dial Plan Click Apply. Note: • The Dial Plan file must not contain overlapping prefixes. Attempting to process an overlapping configuration by the DConvert utility results in an error message specifying the problematic line.
Page 750 Mediant 1000B Gateway & E-SBC Note: • When using prefix tags, you need to configure manipulation rules to remove the tags before the device sends the calls to their destinations. • Called and calling prefix tags can be used in the same routing rule. •...
Page 751: Obtaining Ip Destination From Dial Plan File
User's Manual 43. Software Upgrade 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 characteristics for destination or source number prefixes: Open the IP-to-Tel Routing table (see ''Configuring IP-to-Tel Routing Rules'' on page 484).
Page 752: Modifying Isdn-To-Ip Calling Party Number
Mediant 1000B Gateway & E-SBC An example of a configured Dial Plan (# 6) in the Dial Plan file is shown below: [ PLAN6 ] 200,0,10.33.8.52 ; called prefix 200 is routed to 10.33.8.52 201,0,10.33.8.52 300,0,itsp.com ; called prefix 300 is routed to itsp.com Convert the file to a loadable file and then load it to the device (see ''Creating a Dial Plan File'' on page 746).
Page 753: Viewing Information Of Installed Dial Plan File
User's Manual 43. Software Upgrade ; 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 received Calling Number Party of 0567811181 is changed to 04343434181 and sent to the IP with a SIP INVITE as follows: Via: SIP/2.0/UDP 211.192.160.214:5060;branch=z9hG4bK3157667347 From: <sip:04343434181@kt.co.kr:5060>;tag=de0004b1...
Page 754: User Information File
Mediant 1000B Gateway & E-SBC # debug auxilary-files dial-plan match-number <Dial Plan number> <prefix number> For example, the following checks whether the called prefix number 2000 is defined in Dial Plan 1, which is used for obtaining the destination IP address (tag): # debug auxilary-files dial-plan match-number PLAN1 2000 Match found for 4 digits Matched prefix: 2000...
Page 755 User's Manual 43. Software Upgrade Note: If you have configured regular IP-to-Tel manipulation rules (see ''Configuring Source/Destination Number Manipulation'' on page 503), the device applies these rules before applying the mapping rules of the User Info table. • Tel-to-IP Calls: Maps the calling (source) PBX extension to the "global" number. For example, if the device receives a Tel call from PBX extension 402, it changes this calling number to 638002, and then sends call to the IP side with this calling number.
Page 756 Mediant 1000B Gateway & E-SBC Note: • To configure the User Info table, make sure that you have enabled the feature, as described in Enabling the User Info Table on page754. • If a User Info file is loaded to the device (as described in ''Configuring GW User Info Table in Loadable Text File'' on page 758), all previously configured entries are removed from the table in the Web interface and replaced with the entries from the loaded User Info file.
Page 757 User's Manual 43. Software Upgrade Parameter Description Display Name Defines the Caller ID of the PBX extension. [GWUserInfoTable_DisplayName] The valid value is a string of up to 30 characters. Username Defines the username for registering the user when authentication is necessary. [GWUserInfoTable_Username] The valid value is a string of up to 40 characters.
Page 758 Mediant 1000B Gateway & E-SBC Note: To configure the User Info table, make sure that you have enabled the feature, as described in Enabling the User Info Table on page 754. 43.1.8.2.3 Configuring GW User Info Table in Loadable Text File The GW User Info table can be configured as a User Info file using a text-based file (*.txt).
Page 759: User Information File For Sbc User Database
User's Manual 43. Software Upgrade 43.1.8.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 760 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 43-7: SBC User Info Table - Add Dialog Box Configure a user according to the table below. Click Apply. To register a user, select the user's table entry, and then from the Action drop-down list, choose Register.
Page 761 User's Manual 43. Software Upgrade 43.1.8.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., 1>...
Page 762: Viewing The Installed User Info File Name
Mediant 1000B Gateway & E-SBC is the same file used for the GW User Info table. Thus, this file can include both Gateway and SBC user information. You can load the User Info file using any of the following methods: ...
Page 763: Amd Sensitivity File
The XML-to-binary format conversion can be done using AudioCodes DConvert utility. For more information on using this utility, refer to DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.
Page 764: Obtaining License Key For Feature Upgrade
Before you can install a new License Key, you need to obtain a License Key file for your device with the required features from your AudioCodes representative. The License Key is an encrypted key in string format that is associated with the device's serial number ("S/N") and supplied in a text-based file.
Page 765: Installing License Key Through Web Interface
User's Manual 43. Software Upgrade Note: When you install a new License Key, it is loaded to the device's non-volatile flash memory and overwrites the previously installed License Key. 43.2.3.1 Installing License Key through Web Interface The following procedure describes how to install the License Key through the Web interface.
Page 766: Installing License Key Through Cli
Manager Server The device can receive SBC capacity licenses from a centralized pool of SBC resources managed by the License Pool Manager Server running on AudioCodes EMS. The License Pool Manager Server can dynamically allocate and de-allocate SBC capacity licenses from the pool to devices in the network to meet capacity demands of each device whenever required.
Page 767 User's Manual 43. Software Upgrade You can view the SBC license allocated by the License Pool Manager Server in the License Key page (see ''Installing License Key through Web Interface'' on page 765):  "SBC Sessions Capability": • "Local License": Number of SBC sessions according to the installed License Key. The actual license is indicated on the page in the "SBC="...
Page 768 Mediant 1000B Gateway & E-SBC The following SNMP alarms relate to the allocation/de-allocation of SBC licenses by the License Pool Manager Server:  acLicensePoolInfraAlarm (1.3.6.1.4.1.5003.9.10.1.21.2.0.106): • Sent when the device receives a new SBC license from the License Pool Manager Server and a device reset is required. •...
Page 769: Software Upgrade Wizard
Once loaded, you can select other file types to load. Note: • You can obtain the latest software files from AudioCodes Web site at http://www.audiocodes.com/downloads. • When you start the wizard, the rest of the Web interface is unavailable. After the files are successfully installed with a device reset, access to the full Web interface is restored.
Page 770 Mediant 1000B Gateway & E-SBC • Navigation tree: Setup menu > Administration tab > Maintenance folder > Software Upgrade. Figure 43-13: Starting Software Upgrade Wizard Click Start Software Upgrade; the wizard starts, prompting you to load a .cmp file: Figure 43-14: Loading CMP File in Software Upgrade Wizard Note: At this stage, you can quit the Software Upgrade wizard without having to reset the device, by clicking Cancel.
Page 771 User's Manual 43. Software Upgrade Click Load File; the device begins to install the .cmp file and a progress bar displays the status of the loading process: Figure 43-15: CMP File Loading Progress Bar When the file is loaded, a message is displayed to inform you. To load additional files, use the Next and Back buttons to navigate through the wizard to the desired file-load wizard page;...
Page 772 Mediant 1000B Gateway & E-SBC 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;...
Page 773: Backing Up And Loading Configuration File
User's Manual 44. Backing Up and Loading Configuration File Backing Up and Loading Configuration File You can save a copy of the device's current configuration settings as a file on a local PC (ini file), remote server. This can be used as a backup file for your configuration. If needed, you can then load the file to the device to restore your configuration settings.
Page 774 Mediant 1000B Gateway & E-SBC Click the Load INI File button, and then at the prompt, click OK; the device uploads the file and then resets. Once complete, the Web Login screen appears, requesting you to enter your username and password. Figure 44-2: Loading ini File using Configuration File Page User's Manual Document #: LTRT-27045...
Page 775: Automatic Provisioning
User's Manual 45. Automatic Provisioning Automatic Provisioning This chapter describes the device's automatic provisioning mechanisms. 45.1 Automatic Configuration Methods The table below summarizes the automatic provisioning methods supported by the device: Table 45-1: Automatic Provisioning Methods BootP / TFTP DHCP Automatic Update Methods SNMP (EMS)
Page 776: Provisioning From Http Server Using Dhcp Option 67
(alternatively, the "next-server" directive may be used). ddns-update-style ad-hoc; default-lease-time 60; max-lease-time 60; class "gateways" { match if(substring(hardware, 1, 3) = 00:90:8f); subnet 10.31.0.0 netmask 255.255.0.0 { pool { allow members of "audiocodes"; range 10.31.4.53 10.31.4.75; filename "SIP_F6.60A.217.003.cmp –fb;device.ini"; option routers 10.31.0.1; option subnet-mask 255.255.0.0; Note: •...
Page 777: Provisioning From Tftp Server Using Dhcp Option 66
Provisioning the device from a third-party TFTP server is suitable when the network in which the device is deployed includes a provisioning TFTP server for all network equipment, without the capability of distinguishing between AudioCodes and non- AudioCodes devices. Upon startup, the device checks for DHCP Option 66 in the DHCP response received from the DHCP server.
Page 778: Http-Based Provisioning
Mediant 1000B Gateway & E-SBC Enable the device to include DHCP Option 66 in DHCP Option 55 (Parameter Request List) when requesting TFTP provisioning parameters from a DHCP server, using the following ini file parameter: DHCPRequestTFTPParams = 1 Reset the device with a save-to-flash for your settings to take effect. Note: •...
Page 779: Ftp-Based Provisioning
776 is that the protocol in the URL is "ftp" (instead of "http"). 45.1.4 Provisioning using AudioCodes EMS AudioCodes EMS server functions as a core-network provisioning server. The device's SNMP Manager should be configured with the IP address of the EMS server, using one of the methods detailed in the previous sections.
Page 780: Files Provisioned By Automatic Update
Mediant 1000B Gateway & E-SBC 45.2.1 Files Provisioned by Automatic Update You can use the Automatic Update feature to update the device with any of the following files:  Software file (cmp)  Auxiliary files (e.g., Call Progress Tones, SSL Certificates, SSL Private Key) ...
Page 781: Mac Address Placeholder In Configuration File Name
User's Manual 45. Automatic Provisioning 45.2.3 MAC Address Placeholder in Configuration File Name You can configure the file name of the configuration file (ini) in the URL to automatically include the MAC address of the device. As described in ''File Location for Automatic Update'' on page 780, the file name is included in the configured URL of the provisioning server where the file is located.
Page 782 Mediant 1000B Gateway & E-SBC  To use a file template for automatic provisioning: Define the file types to download by the file template, using the AupdFilesList parameter. Use the keywords listed in the table below to specify each file type. For example, to specify ini, Feature Key, and CPT files: •...
Page 783: Triggers For Automatic Update
Upon receipt of an SNMP request from the provisioning server. • Upon receipt of a special SIP NOTIFY message from the provisioning server. The NOTIFY message includes an Event header with the AudioCodes proprietary value, "check-sync;reboot=false", as shown in the example below: NOTIFY sip:<user>@<dsthost> SIP/2.0 To: sip:<user>@<dsthost>...
Page 784: Access Authentication With Http Server
Mediant 1000B Gateway & E-SBC Click Apply. To enable through CLI: configure voip > sip-definition advanced-settings > sip- remote-reset. 45.2.6 Access Authentication with HTTP Server You can configure the device to authenticate itself with the HTTP/S server. The device authenticates itself by providing the HTTP/S server with its authentication username and password.
Page 785 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 786 Mediant 1000B Gateway & E-SBC Note: • When this method is used, there is typically no need for the provisioning server to check the device’s current firmware version using the HTTP-User-Agent header. • The Automatic Update feature assumes that the Web server conforms to the HTTP standard.
Page 787: File Download Sequence
User's Manual 45. Automatic Provisioning sends the HTTP Get request. 45.2.8 File Download Sequence Whenever the Automatic Update feature is triggered (see ''Triggers for Automatic Update'' on page 783), the device attempts to download each file from the configured URLs, in the following order: ini file CLI Script file...
Page 788: Cyclic Redundancy Check On Downloaded Configuration Files
Mediant 1000B Gateway & E-SBC 45.2.9 Cyclic Redundancy Check on Downloaded Configuration Files You can enable the device to perform cyclic redundancy checks (CRC) on downloaded configuration files (ini) during the Automatic Update process. The CRC checks whether the content (raw data) of the downloaded file is different to the content of the previously downloaded file from the previous Automatic Update process.
Page 789: Automatic Update From Remote Servers
User's Manual 45. Automatic Provisioning Configure the device with the following Automatic Update settings: Automatic Update is done every 24 hours (1440 minutes): ♦ ini File: AutoUpdateFrequency = 1440 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 1440 Automatic Update of software file (.cmp): ♦...
Page 790 Mediant 1000B Gateway & E-SBC  HTTP server at www.company.com for storing the configuration file (ini).  DNS server at 80.179.52.100 for resolving the domain names of the provisioning servers (FTPS and HTTP).  To set up Automatic Provisioning for files stored on different server types (example): CPT file: Set up an NFS server and copy the CPT file to the directory /usr/shared/public on...
Page 791: Automatic Update For Mass Deployment
User's Manual 45. Automatic Provisioning InterfaceTable_UnderlyingDevice; InterfaceTable 0 = 6, 10, 10.15.7.95, 16, 10.15.0.1, 1, "Voice", 80.179.52.100, 0.0.0.0, "vlan 1"; [ \InterfaceTable ] Configure the device to perform the Automatic Update process daily at 03:00 (3 a.m): • ini File: AutoUpdateFrequency = '03:00' •...
Page 792 Mediant 1000B Gateway & E-SBC IniFileURL = 'http://www.company.com/config_<MAC>.ini' ♦ CLI: # configure system (config-system)# automatic update (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: URL of the master configuration file: ♦...
Page 793: Restoring Factory Defaults
User's Manual 46. Restoring Factory Defaults Restoring Factory Defaults This section describes how to restore the device's configuration to factory defaults. 46.1 Restoring Factory Defaults through CLI You can restore the device to factory defaults through CLI, as described in the following procedure.
Page 794: Restoring Defaults Using Hardware Reset Button
Mediant 1000B Gateway & E-SBC  To restore factory defaults through Web interface: Open the Configuration File page: • Toolbar: From the Actions drop-down menu, choose Configuration File. • Navigation tree: Setup menu > Administration tab > Maintenance folder > Configuration File.
Page 795: Status, Performance Monitoring And Reporting
Part IX Status, Performance Monitoring and Reporting...
Page 797: System Status
User's Manual 47. System Status System Status This section describes how to view various system statuses. 47.1 Viewing Device Information You can view hardware and software information about the device on the Device Information page. The page also lists Auxiliary files that have been installed on the device and allows you to remove them (see ''Deleting Auxiliary Files'' on page 739).
Page 798 Mediant 1000B Gateway & E-SBC • 'Firmware': Software version currently running on the device • 'Type': Name of the device  SBC Call Statistics: • Active Calls: Total number of SBC calls. The corresponding SNMP performance monitoring MIB is PM_gwInINVITEDialogs. •...
Page 799 User's Manual 47. System Status Table 47-1: 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 800: Viewing Port Information
Mediant 1000B Gateway & E-SBC Item # Description Analog Channel on page 733)  Port Settings: Displays trunk status (see ''Viewing Trunk and Channel Status'' on page 831) and analog port status (see ''Viewing Port Information'' on page 800)  Update Port Info: Assigns a name to the port (see ''Configuring Name for Telephony Ports'' on page 735) Ethernet port status icons:...
Page 801 User's Manual 47. System Status • For digital ports: The Trunks & Channel Status page appears (see Viewing Trunk and Channel Status on page 831). Click a channel; the following page appears with the Basic tab selected: • For analog ports: The following page appears with the Basic tab selected: Figure 47-3: Viewing Analog Port Status To view additional channel information, click the required tab - SIP, RTP/RTCP, and Voice Settings.
Page 802 Mediant 1000B Gateway & E-SBC Field Description  "IP": Call made from IP side Source Tel Number Telephone number of the caller. Destination Tel Number Telephone number of the called party. Redirect Calling Number Telephone number of the redirected number. Remote Signaling IP IP address used for SIP on the IP side.
Page 803 User's Manual 47. System Status Field Description established. Call Type Type of call:  "Voice": Voice call  "Fax": Fax call Call Destination IP address of called party. Coder Coder type used for the call. Last Current Disconnect Duration Duration of the disconnect signal. Note: The parameter is applicable only to analog interfaces.
Page 804 Mediant 1000B Gateway & E-SBC Field Description  "1": On Note: The parameter is applicable only to analog interfaces. RTP/RTCP Channel Identifier Channel identifier number. RTP Direction Direction of RTP:  "Tx & Rx": both directions (transmit and receive) Local UDP Port Local UDP port on the device.
Page 805: Viewing Carrier-Grade Alarms
User's Manual 48. Viewing Carrier-Grade Alarms Viewing Carrier-Grade Alarms This section describes how to view SNMP alarms raised by the device. 48.1 Viewing Active Alarms You can view current (active) alarms in the Web interface that have been raised by the device.
Page 806: Viewing History Alarms
Mediant 1000B Gateway & E-SBC 48.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 807 User's Manual 48. Viewing Carrier-Grade Alarms Field Description 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 1000B Gateway &...
Page 808 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 809: Viewing Management User Activity Logs
User's Manual 49. Viewing Management User Activity Logs Viewing Management User Activity Logs If you have enabled the reporting of management user activities performed in the device's management interfaces (see ''Configuring Reporting of Management User Activities'' on page 893), you can view the logged activities in the Web interface, as described in the procedure below.
Page 810 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 811: Viewing Performance Monitoring
User's Manual 50. Viewing Performance Monitoring Viewing Performance Monitoring This section describes how to view performance monitoring in the device's Web interface. 50.1 Viewing Trunk Utilization You can view the number of active channels per trunk over time in the Web interface's Trunk Utilization page.
Page 812: Viewing Call Success And Failure Ratio
Mediant 1000B Gateway & E-SBC For more graph functionality, see the following table: Table 50-1: Additional Graph Functionality for Trunk Utilization Button Description 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.
Page 813 User's Manual 50. Viewing Performance Monitoring  To view success and failed call ratio: Open the Success/Failure Ratio page (Monitor menu > Monitor tab > Performance Monitoring folder > Success / Failure Ratio). Figure 50-2: Viewing Success/Failure Ratio From the 'SRD/IP Group' drop-down list, select whether you want to view statistic for an SRD or IP Group.
Page 814: Viewing Average Call Duration
Mediant 1000B Gateway & E-SBC 50.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 815: Configuring Performance Profiles
User's Manual 50. Viewing Performance Monitoring 50.4 Configuring Performance Profiles The Performance Profile table lets you configure up to 432 Performance Profile rules. A Performance Profile rule defines thresholds of performance monitoring call metrics for Major and Minor severity alarms. If the threshold is crossed, the device raises the corresponding severity alarm.
Page 816 Mediant 1000B Gateway & E-SBC  Minor Threshold (Yellow): Lower threshold that indicates changes from Green or Red to Yellow.  Major Threshold (Red): Higher threshold that indicates changes from Green or Yellow to Red. The device also uses hysteresis to determine whether the threshold has indeed being crossed.
Page 817 User's Manual 50. Viewing Performance Monitoring Note: • Forwarded calls are not considered in the calculation for ASR and NER. • If you don't configure thresholds for a specific metric, the device still provides current performance monitoring values of the metric, but does not raise any threshold alarms for it.
Page 818 Mediant 1000B Gateway & E-SBC Parameter Description 'SRD' parameter (see below).  [2] IP Group = Assigns an IP Group. To specify the IP Group, use the 'IP Group' parameter (see below). IP Group Assigns an IP Group to the rule. ip-group-name Note: The parameter is applicable only if you configure the 'Entity' parameter to IP Group.
Page 819 User's Manual 50. Viewing Performance Monitoring Parameter Description Minimum Samples Defines the minimum number of call sessions (sample) that is required for the device to calculate the performance minimum-samples monitoring metrics (per window size). If the number of call [PerformanceProfile_MinimumSample] sessions is less than the configured value, no calculation is done.
Page 820 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 821: Viewing Voip Status
User's Manual 51. Viewing VoIP Status Viewing VoIP Status This section describes how to view VoIP-related status. 51.1 Viewing Tel-IP Call Counters You can view statistical information on IP-to-Tel and Tel-to-IP calls in the Web interface's IP to Tel Calls Count page and Tel to IP Calls Count page. The information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call CDR message is sent).
Page 822 Mediant 1000B Gateway & E-SBC Counter Description  RELEASE_BECAUSE_DISCONNECT_CODE Note: When the duration of the call is zero, the release reason GWAPP_NORMAL_CALL_CLEAR increments the 'Number of Failed Calls due to No Answer' counter. The rest of the release reasons increment the 'Number of Failed Calls due to Other Failures' counter. Percentage of The percentage of established calls from attempted calls, known as Successful Calls (ASR)
Page 823: Viewing Sbc Registered Users
User's Manual 51. Viewing VoIP Status 51.2 Viewing SBC Registered Users You can view SBC users that are registered with the device. For each user, the Address of Record (AOR) and the corresponding contacts are shown. An AOR is a SIP or SIPS URI that points to a domain with a location service that can map the URI to another URI (contact) where the user might be available.
Page 824: Viewing Call Routing Status
Mediant 1000B Gateway & E-SBC 51.3 Viewing Call Routing Status You can view information on the current call routing method used by the device. The information includes the IP address (or FQDN) of the Proxy server with which the device routes the call.
Page 825: Viewing Registration Status
User's Manual 51. Viewing VoIP Status 51.4 Viewing Registration Status You can view the registration status of the device's endpoints (FXS, FXO and BRI) and SIP Accounts. The registration mode (i.e., per device, endpoint, account. or no registration) is configured in the Trunk Group Settings table (see Configuring Trunk Group Settings on page 467) or using the TrunkGroupSettings ini file parameter.
Page 826: Viewing Ip Connectivity
Mediant 1000B Gateway & E-SBC 51.5 Viewing IP Connectivity You can view on-line, read-only network diagnostic connectivity information on destination IP addresses configured in the Tel-to-IP Routing table (see ''Configuring Tel-to-IP Routing Rules'' on page 475). Note: The table is applicable only to the Gateway application. ...
Page 827 User's Manual 51. Viewing VoIP Status Column Name Description 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).  The parameter is reset if two minutes elapse without a call to the destination.
Page 828: Viewing Gateway Cdr History
Mediant 1000B Gateway & E-SBC 51.6 Viewing Gateway CDR History You can view historical (last 4,096 CDRs) Call Detail Records (CDR) of Gateway calls in a table. CDR history information is stored on the device’s memory. When a new CDR is generated, the device adds it to the top of the table and all existing entries are shifted one down in the table.
Page 829: Viewing Sbc Cdr History
User's Manual 51. Viewing VoIP Status Field Description address. Duration Displays the duration of the call, displayed in the format hh:mm:ss, where hh is hours, mm minutes and ss seconds. For example, 00:01:20 denotes 1 minute and 20 seconds. Termination Reason Displays the reason for the call being released (ended).
Page 830 Mediant 1000B Gateway & E-SBC Field Description Callee Displays the phone number (destination URI user@host) of the party to whom the call was made. Direction Displays the direction of the call:  "Incoming"  "Outgoing" Remote IP Displays the IP address of the call party. For an "Incoming" call, this is the source IP address;...
Page 831: Viewing Pstn Status
User's Manual 52. Viewing PSTN Status Viewing PSTN Status This section describes how to view PSTN-related status. 52.1 Viewing Trunks & Channels Status You can view the status of the device's PSTN (digital and BRI) trunks and corresponding channels in the Web interface. It also enables you to view trunk configuration and channel information.
Page 832: Viewing Nfas Groups And D-Channel Status
Mediant 1000B Gateway & E-SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 52-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls Green Active Call in progress (RTP traffic) and no alarms...
Page 833 User's Manual 52. Viewing PSTN Status  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 52-1: NFAS Group &...
Page 834 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 835: Viewing Network Status
User's Manual 53. Viewing Network Status Viewing Network Status This section describes how to view network-related status. 53.1 Viewing Active IP Interfaces You can view the device's active IP interfaces that are configured in the IP Interfaces table (see ''Configuring IP Network Interfaces'' on page 135). ...
Page 836: Viewing Static Routes Status
Mediant 1000B Gateway & E-SBC Table 53-1: Ethernet Port Information Table Description Parameter Description Port Name Displays the name of the port. Active Displays whether the port is active ("Yes") or not ("No"). Speed Displays the speed of the Ethernet port. Duplex Mode Displays whether the port is half- or full-duplex.
Page 837: Reporting Information To External Party
User's Manual 54. Reporting Information to External Party Reporting Information to External Party This section describes features for reporting various information to an external party. 54.1 Configuring RTCP XR RTP Control Protocol Extended Reports (RTCP XR) is a VoIP management control that defines a set of metrics containing information for assessing VoIP call quality and for diagnosing problems.
Page 838 Mediant 1000B Gateway & E-SBC the remote endpoint. The following table lists the supported voice metrics (parameters) published in the RTCP XR. Table 54-1: RTCP XR Published VoIP Metrics Metric Parameter Description CallID Call ID - call ID from the SIP dialog LocalID Local ID - identifies the reporting endpoint for the media session RemoteID...
Page 839 User's Manual 54. Reporting Information to External Party Metric Parameter Description Jitter Buffer Discard Rate BurstGapLoss BLD Burst Loss Density Burst Duration Gap Loss Density Gap Duration GMIN Minimum Gap Threshold Delay Round Trip Delay (msec) End System Delay (msec) One Way Delay (msec) Inter-Arrival Jitter (msec) Mean Absolute Jitter (msec)
Page 840 Mediant 1000B Gateway & E-SBC Metric Parameter Description 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 MOSCQEstAlg MOS-CQ Est. Algorithm - name (string) of the algorithm used to estimate MOSCQ QoEEstAlg QoE Est.
Page 841 User's Manual 54. Reporting Information to External Party Delay: RTD=65535 ESD=0 QualityEst: DialogID: 20328634741612201520943@172.17.116.201;to- tag=1c1690611502;from-tag=1c2032864069  To configure RTCP XR: Open the RTP/RTCP Settings page (Setup menu > Signaling & Media tab > Media folder > RTP/RTCP Settings). Under the RTCP-XR group, configure the following: •...
Page 842: Generating Call Detail Records
Mediant 1000B Gateway & E-SBC • (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 54-2: Configuring RTCP XR Collection Server Using the PublicationIPGroupID ini file parameter, define the IP Group to where you want to send the RTCP XR.
Page 843 User's Manual 54. Reporting Information to External Party  "CALL_START": CDR is sent upon an INVITE message.  "CALL_CONNECT": CDR is sent upon a 200 OK response (i.e., call is established).  "CALL_END": CDR is sent upon a BYE message (i.e., call ends) The CDR types for SBC signaling and the SIP dialog stages are shown in the following figure: Figure 54-3: CDR Types for SBC Signaling...
Page 844 Mediant 1000B Gateway & E-SBC CDR Field Description CDR Report Type Format (SBCReportType) SessionId Unique Session ID String (up to characters) LegId Unique ID number of the call leg within a "CALL_START", String specific call session. "CALL_CONNECT" (decimal) and "CALL_END" A basic call consists of two legs (incoming leg and outgoing leg) and thus, two leg IDs are generated for the session, one for...
Page 845 User's Manual 54. Reporting Information to External Party CDR Field Description CDR Report Type Format (SBCReportType) SrcURIBeforeMap Source URI before manipulation String (up to characters) DstURI Destination URI String (up to characters) DstURIBeforeMap Destination URI before manipulation String (up to characters) Durat Call duration (in seconds)
Page 846 Mediant 1000B Gateway & E-SBC CDR Field Description CDR Report Type Format (SBCReportType) Calls with duration:  NORMAL_CALL_CLEAR:  "GWAPP_NORMAL_CALL_CLEA R"  "ABNORMALLY_TERMINATED": Anything else N/A - Reasons not belonging to above categories. Call setup time String (up to SetupTime characters) ConnectTime Call connect time...
Page 847 User's Manual 54. Reporting Information to External Party CDR Field Description CDR Report Type Format (SBCReportType) DirectMedia Direct media or traversing SBC: String  "yes"  "no" SIPTrmReason SIP call termination reason (BYE, "CALL_END" String (up to CANCEL, or SIP error codes, e.g., 404) characters) SipTermDesc Description of SIP termination reason:...
Page 848: Cdr Fields For Sbc Media
Mediant 1000B Gateway & E-SBC 54.2.1.2 CDR Fields for SBC Media The default CDR fields for SBC media are listed in the following table. The media CDRs are published for each active media stream, thereby allowing multiple media CDRs, where each media CDR has a unique call ID corresponding to the signaling CDR.
Page 849 User's Manual 54. Reporting Information to External Party CDR Field Range Description the call session. For example, the device generates leg ID "1" for the incoming leg and leg ID "2" for the outgoing leg. If the call is transferred, the device generates leg ID "3"...
Page 850: Cdr Fields For Sbc Local Storage
Mediant 1000B Gateway & E-SBC CDR Field Range Description unavailable (not licensed or disabled), this R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable. LocalMosCQ 10 to 46 (127 if information is Local MOS for conversation unavailable) RemoteMosCQ...
Page 851: Cdr Fields For Gateway Application
User's Manual 54. Reporting Information to External Party CDR Field Title Source URI Before Manipulation SrcURIBeforeMap Destination URI DstURI Destination URI Before Manipulation DstURIBeforeMap Call Duration Durat Termination Side TrmSd Termination Reason TrmReason Termination Reason Category TrmReasonCategory Setup Time SetupTime Connect Time ConnectTime Release Time...
Page 852 Mediant 1000B Gateway & E-SBC The CDR types and the SIP dialog stages are shown in the following figure: Figure 54-5: Gateway CDR Report Types Table 54-5: Default CDR Fields for Gateway Calls CDR Field Description GWReportType (CDR Report Type) GWReportType Report type: ...
Page 853 User's Manual 54. Reporting Information to External Party CDR Field Description GWReportType (CDR Report Type) may be as follows: initial call is "1", outgoing leg to user's office phone is "2" and outgoing leg to the user's mobile phone is "3". If the call is then transferred, the leg ID for the transfer leg is "4".
Page 854 Mediant 1000B Gateway & E-SBC CDR Field Description GWReportType (CDR Report Type) RtpIp RTP IP address "CALL_END" Port Remote RTP port "CALL_END" TrmSd Initiator of call release (IP, Tel, or Unknown) "CALL_END" TrmReason SIP call termination reason (see ''Release Reasons in CDR "CALL_END"...
Page 855 User's Manual 54. Reporting Information to External Party CDR Field Description GWReportType (CDR Report Type) (euro or usd)  recorded-units: for unit charge (1-999999) Mult 0,001-1000 (in steps of 10) "CALL_END" (See explanation above.) TrmReasonCategor Termination reason category: "CALL_END"  Calls with duration 0 (i.e., not connected): ...
Page 856 Mediant 1000B Gateway & E-SBC CDR Field Description GWReportType (CDR Report Type) RemoteRFactor Remote R-factor "CALL_END" Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided. Instead, the device sends the CDR field with the value 127, meaning that information is unavailable.
Page 857 User's Manual 54. Reporting Information to External Party 54.2.1.4.1 Release Reasons in CDR for Gateway Application The possible reasons for call termination for the Gateway application which is represented in the CDR field TrmReason are listed below:  "REASON N/A" ...
Page 858 Mediant 1000B Gateway & E-SBC  "GWAPP_CALL_REJECTED"  "GWAPP_NUMBER_CHANGED"  "GWAPP_NON_SELECTED_USER_CLEARING"  "GWAPP_INVALID_NUMBER_FORMAT"  "GWAPP_FACILITY_REJECT"  "GWAPP_RESPONSE_TO_STATUS_ENQUIRY"  "GWAPP_NORMAL_UNSPECIFIED"  "GWAPP_CIRCUIT_CONGESTION"  "GWAPP_USER_CONGESTION"  "GWAPP_NO_CIRCUIT_AVAILABLE"  "GWAPP_NETWORK_OUT_OF_ORDER"  "GWAPP_NETWORK_TEMPORARY_FAILURE"  "GWAPP_NETWORK_CONGESTION"  "GWAPP_ACCESS_INFORMATION_DISCARDED"  "GWAPP_REQUESTED_CIRCUIT_NOT_AVAILABLE"  "GWAPP_RESOURCE_UNAVAILABLE_UNSPECIFIED"  "GWAPP_PERM_FR_MODE_CONN_OUT_OF_S"  "GWAPP_PERM_FR_MODE_CONN_OPERATIONAL"...
Page 859: Cdr Fields For Gateway Local Storage
User's Manual 54. Reporting Information to External Party  "GWAPP_NOT_CUG_MEMBER"  "GWAPP_CUG_NON_EXISTENT"  "GWAPP_MANDATORY_IE_MISSING"  "GWAPP_MESSAGE_TYPE_NON_EXISTENT"  "GWAPP_MESSAGE_STATE_INCONSISTENCY"  "GWAPP_NON_EXISTENT_IE"  "GWAPP_INVALID_IE_CONTENT"  "GWAPP_MESSAGE_NOT_COMPATIBLE"  "GWAPP_RECOVERY_ON_TIMER_EXPIRY"  "GWAPP_PROTOCOL_ERROR_UNSPECIFIED"  "GWAPP_INTERWORKING_UNSPECIFIED"  "GWAPP_UKNOWN_ERROR"  "RELEASE_BECAUSE_HELD_TIMEOUT" 54.2.1.5 CDR Fields for Gateway Local Storage The CDR fields for Gateway calls that are stored locally on the device are listed in the table below.
Page 860 Mediant 1000B Gateway & E-SBC CDR Field Title Call duration Durat Selected coder Coder RTP IP address RtpIp Remote RTP port Port Initiator of call release TrmSd SIP call termination reason TrmReason Fax transaction during call Number of incoming packets InPackets Number of outgoing packets OutPackets...
Page 861: Customizing Cdrs For Gateway Calls
User's Manual 54. Reporting Information to External Party CDR Field Title Proxy Set name ProxySetId IP Profile name IpProfileId Media Realm name MediaRealmId SIP signaling transport type SigTransportType Local R-factor LocalRFactor Note: If the RTCP XR feature is unavailable (not licensed or disabled), this R-factor VoIP metric is not provided.
Page 862 Mediant 1000B Gateway & E-SBC  CDRs related to RADIUS accounting and sent in RADIUS accounting request messages. For RADIUS accounting CDRs, you can customize the RADIUS Attribute's prefix name and ID, for standard RADIUS Attributes and vendor-specific RADIUS Attributes (VSA). For example, instead of the default VSA name, "h323-connect-time" with RADIUS Attribute ID 28, you can change the name to "Call-Connect-Time"...
Page 863 User's Manual 54. Reporting Information to External Party An example of CDR customization rules configured in the table is shown below: Figure 54-7: Examples of Configured Gateway CDR Customization Rules  Index 0: The default CDR field "Call Orig" for Syslog is changed to "Caller". ...
Page 864 Mediant 1000B Gateway & E-SBC Parameter Description Plan; [514] Redirect Number Before Manipulation; [515] Redirect Number; [526] Redirect Number Type; [527] Redirect Number Plan; [516] Source Host Name Before Manipulation; [517] Source Host Name; [518] Destination Host Name Before Manipulation; [519] Destination Host Name;...
Page 865: Customizing Cdrs For Sbc Calls
User's Manual 54. Reporting Information to External Party Parameter Description  For standard RADIUS Attributes (i.e., 'RADIUS Attribute Type' parameter configured to Standard), the value must be a "known" RADIUS ID (per RFC for RADIUS). However, if you configure the ID to 0 (default) for any of the RADIUS Attributes (configured in the 'Column Type' parameter) listed below and then apply your rule (Click Apply), the device automatically replaces the value...
Page 866 Mediant 1000B Gateway & E-SBC The following procedure describes how to customize SBC-related CDRs through the Web interface. 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 >...
Page 867 User's Manual 54. Reporting Information to External Party Parameter Description messages. Field Type Defines the CDR field (column) that you want to customize. The applicable CDR field depends on the settings of the 'CDR Type' col-type parameter: [SBCCDRFormat_FieldType]  For all types: [300] CDR Type (default); [301] Call ID; [302] Session ID;...
Page 868 Mediant 1000B Gateway & E-SBC Parameter Description or double). For example, if you want the CDR field name to appear as 'Phone Duration', you must configure the parameter to 'Phone Duration'. You can also configure the CDR field name with an equals (=) sign, for example "call-connect-time=".
Page 869: Configuring Cdr Reporting
User's Manual 54. Reporting Information to External Party 54.2.4 Configuring CDR Reporting To enable and configure CDR reporting, follow the procedure below. For detailed descriptions of the parameters, see ''Syslog, CDR and Debug Parameters'' on page 955.  To configure CDR reporting: Enable the Syslog feature for sending log messages generated by the device to a collecting log message server.
Page 870 Mediant 1000B Gateway & E-SBC 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 871: Configuring Radius Accounting
User's Manual 54. Reporting Information to External Party • filename: name you want to assign the file. Any file extension name can be used, but as the file content is in CSV format, it is recommended to use the .csv file extension.
Page 872 Mediant 1000B Gateway & E-SBC connection and release, or call setup and release. This section lists the CDR attributes for RADIUS accounting. 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.
Page 873 User's Manual 54. Reporting Information to External Party  Vendor-specific RADIUS attributes: RADIUS attributes that are specific to the device (company) are referred to as Vendor-specific attributes (VSA). The CDR of VSAs are sent with a general RADIUS ID of 26 to indicate that they are vendor- specific (non-standard).
Page 874 Mediant 1000B Gateway & E-SBC For a detailed description of the parameters, see ''RADIUS Parameters'' on page 1178. Figure 54-16: Configuring RADIUS Accounting Click Apply, and then reset the device with a save-to-flash for your settings to take effect. The table below lists the RADIUS Accounting CDR attributes included in the communication packets transmitted between the device and a RADIUS server.
Page 875 User's Manual 54. Reporting Information to External Party Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID the IP side (Gateway) or incoming leg (SBC)  "originate": Call originated from the Tel side (Gateway) or outgoing leg (SBC) h323-call-type Protocol type or...
Page 876 Mediant 1000B Gateway & E-SBC Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID incoming leg (SBC) terminator Terminator of the String terminator=originate Stop call:  "answer": Call originated from the IP side (Gateway) or incoming leg (SBC) ...
Page 877 User's Manual 54. Reporting Information to External Party Vendor- Attribute Attribute Specific Value Description Example Name Attribute Format (VSA) ID acct-session-id (Standard) A unique String 34832 Start accounting identifier - match Stop start & stop acct-session- (Standard) For how many Numeric - Stop time...
Page 878: Querying Device Channel Resources Using Sip Options
Mediant 1000B Gateway & E-SBC 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 54.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.
Page 879: Diagnostics
Part X Diagnostics...
Page 881: Syslog And Debug Recording
User's Manual 55. Syslog and Debug Recording Syslog and Debug Recording For debugging and troubleshooting, you can use the device's Syslog and/or Debug Recording capabilities:  Syslog: Syslog is an event notification protocol that enables a device to send event notification messages across IP networks to event message collectors, also known as Syslog servers.
Page 882 Mediant 1000B Gateway & E-SBC 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 892).
Page 883 User's Manual 55. Syslog and Debug Recording Parameter Description Filter Type Defines the filter type criteria.  filter-type [1] Any (default)  [2] Trunk ID = Filters log by Trunk ID. Note: Applicable only to [LoggingFilters_FilterType] the Gateway application.  [3] Trunk Group ID = Filters log by Trunk Group ID.
Page 884 Mediant 1000B Gateway & E-SBC Parameter Description  "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 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"...
Page 885: Filtering Ip Network Traces
User's Manual 55. Syslog and Debug Recording Parameter Description Log Type Defines the type of messages to include in the log file.  log-type [0] = (Default) Not configured. The option is applicable only for sending Syslog messages to a Syslog server (i.e., 'Log [LoggingFilters_CaptureType] Destination' parameter is configured to Syslog Server).
Page 886: Configuring Syslog
Mediant 1000B Gateway & E-SBC Wireshark-like filtering expressions for your IP trace. The following Wireshark-like expressions are supported: Table 55-2: Supported Wireshark-like Expressions for 'Value' Parameter Expression Description ip.src, ip.dst Source and destination IP address ip.addr IP address - up to two IP addresses can be entered ip.proto IP protocol type (PDU) entered as an enumeration value (e.g., 1 is ICMP, 6 is TCP, 17 is UDP)
Page 887 User's Manual 55. Syslog and Debug Recording are identified by a session ID ("SID"), described in detail in the table below. The following is an example of a SIP-session related Syslog message: 13:10:57.811 : 10.13.4.12 : NOTICE : [S=235][SID:2ed1c8:96:5] (lgr_flow)(63) UdpTransportObject#0- Adding socket event for address 10.33.2.42:5060 [Time: 04-19-2012@18:29:39] ...
Page 888 Mediant 1000B Gateway & E-SBC Message Item Description number in Syslog messages, by setting the 'CDR Syslog Sequence Number' parameter to Disable (see ''Configuring Syslog'' on page 892). Log Number Ignore this number; it has been replaced by the Message (lgr)(number) Sequence Number (described previously).
Page 889: Event Representation In Syslog Messages
User's Manual 55. Syslog and Debug Recording Message Item Description Message Body Describes the message. Timestamp When the Network Time Protocol (NTP) is enabled, a timestamp string [hour:minutes:seconds] is added to all Syslog messages. 55.2.1.1 Event Representation in Syslog Messages The Syslog message events that the device sends are denoted by unique abbreviations.
Page 890: Identifying Audiocodes Syslog Messages Using Facility Levels
Unknown Aggregation Payload Type Invalid Routing Flag Received 55.2.1.2 Identifying AudioCodes Syslog Messages using Facility Levels The device’s Syslog messages can easily be identified and distinguished from Syslog messages from other equipment, by setting its Facility level. The Facility levels of the device's Syslog messages are numerically coded with decimal values.
Page 891: 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 55-6: Syslog Message Severity ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) Critical RecoverableMsg Major...
Page 892: Enabling Syslog
Mediant 1000B Gateway & E-SBC ITU Perceived Severity AudioCodes' Syslog Severity (SNMP Alarm’s Severity) 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: 55.2.2 Enabling Syslog...
Page 893: Configuring Reporting Of Management User Activities
User's Manual 55. Syslog and Debug Recording  To configure the Syslog debug level: Open the Syslog Settings page (Troubleshoot menu > Troubleshoot tab > Logging folder > Syslog Settings). Figure 55-4: Configuring Syslog Debug Level From the 'Debug Level' (GwDebugLevel) drop-down list, select the debug level of Syslog messages: •...
Page 894 Mediant 1000B Gateway & E-SBC The device can report the following user activities:  Modifications of individual parameters, for example: 14:33:00.162 : 10.15.7.95 : Local 0 :NOTICE : [S=3403] [BID=3aad56:32] Activity Log: Max Login Attempts was changed from '3' to '2'. User: Admin. Session: HTTP (10.13.22.54) ...
Page 895: 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 896: Configuring Debug Recording
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. 55.3 Configuring Debug Recording This section describes how to configure debug recording and how to collect debug recording packets.
Page 897: Collecting Debug Recording Messages
Click Apply. 55.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 898: Debug Capturing On Physical Voip Interfaces
Mediant 1000B Gateway & E-SBC The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: 55.3.3 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets).
Page 899: Self-Testing
User's Manual 56. Self-Testing Self-Testing The device features the following self-testing modes to identify faulty hardware components:  Detailed Test (Configurable): This test verifies the correct functioning of the different hardware components on the device. This test is done when the device is taken out of service (i.e., not in regular service for processing calls).
Page 900 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 901: 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 902 Mediant 1000B Gateway & E-SBC 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 command: # clear debug-file The following procedure describes how to retrieve the debug file from the device through...
Page 903: Fxo Line Testing
User's Manual 58. FXO Line Testing FXO Line Testing The device can test the telephone lines connected to its FXO ports through SNMP using the SNMP acAnalogFxoLineTestTable table. The tests provide various line measurements. In addition to the tests, a keep-alive test is also done every 100 msec on each of the analog ports to detect communication problems with the analog equipment: ...
Page 904 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 905: 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 calls through the Web interface.
Page 906 Mediant 1000B Gateway & E-SBC Click New; the following dialog box appears: Figure 59-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. Table 59-1: Test Call Rules Table Parameter Descriptions Parameter Description...
Page 907 User's Manual 59. Testing SIP Signaling Calls Parameter Description  [1] IP Group = (Default) Calls are matched by (or routed to) an IP Group. To specify the IP Group, see the 'IP Group' parameter in the table.  [2] Dest Address = Calls are matched by (or routed to) a destination IP address.
Page 908 Mediant 1000B Gateway & E-SBC Parameter Description is set to Dest Address. QoE Profile Assigns a QoE Profile to the test call. qoe-profile By default, no value is defined. [Test_Call_QOEProfile] To configure QoE Profiles, see ''Configuring Quality of Experience Profiles'' on page 297. Bandwidth Profile Assigns a Bandwidth Profile to the test call.
Page 909 User's Manual 59. Testing SIP Signaling Calls Parameter Description  test-mode [0] Once = (Default) The test runs until the lowest value between the following is reached: [Test_Call_TestMode]  Maximum channels is reached for the test session, configured by 'Maximum Channels for Session'. ...
Page 910: Starting And Stopping Test Calls
Mediant 1000B Gateway & E-SBC 59.2 Starting and Stopping Test Calls The following procedure describes how to start, stop, and restart test calls.  To start, stop, and restart a test call: In the Test Call Rules table, select the required test call entry. From the Action drop-down list, choose the required command: •...
Page 911: Viewing Test Call Statistics
User's Manual 59. Testing SIP Signaling Calls 59.4 Viewing Test Call Statistics You can view statistical information on the test call.  To view statistics of a test call: In the Test Call Rules table, select the required test call row. Scroll down the page to the area below the table.
Page 912 Mediant 1000B Gateway & E-SBC Statistics Field Description (see ''Viewing Test Call Status'' on page 910). 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' parameter settings) and also shows the following summary of completed test calls:...
Page 913: Configuring Dtmf Tones For Test Calls
User's Manual 59. Testing SIP Signaling Calls 59.5 Configuring DTMF Tones for Test Calls By default, no DTMF signal is played to an answered test call (incoming or outgoing). However, you can enable this per test call in the Test Call Rules table by configuring the 'Play' parameter to DTMF (see ''Configuring Test Call Endpoints'' on page 905).
Page 914: Configuring Sbc Test Call With External Proxy
Mediant 1000B Gateway & E-SBC  To configure basic call testing: Open the Test Call Settings page (Troubleshooting tab > Troubleshooting menu > Test Call folder > Test Call Settings). In the 'Test Call ID' field, enter a prefix for the simulated endpoint: Figure 59-5: Configuring Basic Test Calls Click Apply.
Page 915 User's Manual 59. Testing SIP Signaling Calls The figure below displays an example of an SBC test call: Figure 59-6: SBC Test Call Example The call is received from the remote endpoint with the called number prefix "8101". As the 'SBC Test ID' parameter is set to "8", the device identifies this call as a test call and removes the digit "8"...
Page 916: Test Call Configuration Examples
Mediant 1000B Gateway & E-SBC 59.8 Test Call Configuration Examples Below are a few examples of test call configurations.  Single Test Call Scenario: This example describes the configuration of a simple test call scenario that includes a single test call between a simulated test endpoint on the device and a remote endpoint.
Page 917 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 918 Mediant 1000B Gateway & E-SBC  Registration Test Call Scenario: This example describes the configuration for testing the registration and authentication (i.e., username and pas,sword) process of a simulated test endpoint on the device with an external proxy/registrar server. This is useful, for example, for verifying that endpoints located in the LAN can register with an external proxy and subsequently, communicate with one another.
Page 919: Pinging A Remote Host Or Ip Address
User's Manual 60. Pinging a Remote Host or IP Address Pinging a Remote Host or IP Address You can verify the network connectivity with a remote host or IP address by pinging the network entity.  IPv4: The ping to an IPv4 address can be done from any of the device's VoIP interfaces that is configured with an IPv4 address.
Page 920 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 921: Appendix
Part XI Appendix...
Page 923: Dialing Plan Notation For Routing And Manipulation
User's Manual 61. Dialing Plan Notation for Routing and Manipulation Dialing Plan Notation for Routing and Manipulation The device supports flexible dialing plan notations for denoting the prefix and/or suffix source and/or destination numbers and SIP URI user names in the routing and manipulation tables.
Page 924 Mediant 1000B Gateway & E-SBC Notation Description  [5551200-5551300]#  To depict prefix numbers from 123100 to 123200:  123[100-200]#  To depict prefix and suffix numbers together:  03(100): for any number that starts with 03 and ends with 100. ...
Page 925 User's Manual 61. Dialing Plan Notation for Routing and Manipulation Notation Description Version 7.2 Mediant 1000B Gateway & E-SBC...
Page 926 Mediant 1000B Gateway & E-SBC This page is intentionally left blank. User's Manual Document #: LTRT-27045...
Page 927: Configuration Parameters Reference
User's Manual 62. Configuration Parameters Reference Configuration Parameters Reference The device's configuration parameters, default values, and their descriptions are documented in this section. Note: Parameters and values enclosed in square brackets [...] represent the ini file parameters and their enumeration values. 62.1 Management Parameters This section describes the device's management-related parameters.
Page 928: Web Parameters
Mediant 1000B Gateway & E-SBC 62.1.2 Web Parameters The Web parameters are described in the table below. Table 62-2: Web Parameters Parameter Description Enable web access from all interfaces Enables Web access from any of the device's IP network interfaces. The feature applies to HTTP and HTTPS web-access-from-all-interfaces protocols.
Page 929 User's Manual 62. Configuration Parameters Reference Parameter Description expires can users attempt to login from this same IP address. The valid value is 0 to 100000, where 0 means that login is not denied regardless of number of failed login attempts. The default is 60.
Page 930: Telnet Parameters
Mediant 1000B Gateway & E-SBC Parameter Description required.  You cannot reset the username and password through the Web interface (by loading an ini file or on the AdminPage). To reset the username and password:   SNMP: 1) Set acSysGenericINILine to WEBPasswordControlViaSNMP = 1, and reset the device with a flash burn (set acSysActionSetResetControl to 1 and...
Page 931: Ini File Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description  [TelnetServerEnable] [1] Enable Unsecured (default)  [2] Enable Secured Note: Only the primary Web User Account (which has Security Administration access level) can access the device using Telnet (see ''Configuring Management User Accounts'' on page 65). Telnet Server TCP Port Defines the port number for the embedded Telnet server.
Page 932 > snmp trap > auto- Enables the device to send NAT keep-alive traps to the port send-keep-alive of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP [SendKeepAliveTrap] communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
Page 933 User's Manual 62. Configuration Parameters Reference Parameter Description  [1] = Enable configure system > snmp settings > Defines the base product system OID. sys-oid The default is eSNMP_AC_PRODUCT_BASE_OID_D. [SNMPSysOid] Note: For the parameter to take effect, a device reset is required.
Page 934 Mediant 1000B Gateway & E-SBC Parameter Description [SNMPManagerTableIP_x] Enter the IP address in dotted-decimal notation, e.g., 108.10.1.255. Trap Port Defines the port number of the remote SNMP Manager. The device sends SNMP traps to this port. port The valid SNMP trap port range is 100 to 4000. The default [SNMPManagerTrapPort_x] port is 162.
Page 935: Serial Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description For example, "Private-comm_string1". The default is "private". Trap Community String Defines the community string for SNMP traps. configure system > snmp trap > The valid value is a string of up to 19 characters that can community-string include only the following: ...
Page 936: Auxiliary And Configuration File Name Parameters
Mediant 1000B Gateway & E-SBC Parameter Description parameters and view error/notification messages. To establish serial communication with the device, see ''Establishing a CLI Session'' on page 83. Note: For the parameter to take effect, a device reset is required. [SerialBaudRate] Defines the serial communication baud rate.
Page 937 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 938: 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 939 User's Manual 62. Configuration Parameters Reference Parameter Description  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 940 Mediant 1000B Gateway & E-SBC Parameter Description  [2] = Enable CRC for individual lines only. Same as option [1], except that the CRC ignores the order of lines (i.e., same text can be on different lines). tftp-block-size Defines the size of the TFTP data blocks (packets) when downloading a file from a TFTP server for the Automatic Update mechanism.
Page 941 User's Manual 62. Configuration Parameters Reference Parameter Description  The case-sensitive string, "<MAC>" can be used in the file name for instructing the device to replace it with the device's MAC address. For more information, see ''MAC Address Placeholder in Configuration File Name'' on page 781.
Page 942: Networking Parameters
Mediant 1000B Gateway & E-SBC Parameter Description [TemplateUrl] of the provisioning server on which the files to download are located. For more information, see ''File Template for Automatic Provisioning'' on page 781. Defines the list of file types in the File Template for automatic updates, template-files-list to download from the provisioning server.
Page 943: Multiple Voip Network Interfaces And Vlan Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description [ \DeviceTable ] For a detailed description of the table, see Configuring Underlying Ethernet Devices on page 132. 62.2.2 Multiple VoIP Network Interfaces and VLAN Parameters The IP network interfaces and VLAN parameters are described in the table below. Table 62-10: IP Network Interfaces and VLAN Parameters Parameter Description...
Page 944: Open Solution Network (Osn) Parameters
[1] Enable For more information, refer to the SBA Installation and Maintenance Manual. Note: The feature will only be supported when AudioCodes SBA supports Skype for Business. Please contact your sales representative if you need more information. 62.2.5 Quality of Service Parameters The Quality of Service (QoS) parameters are described in the table below.
Page 945 User's Manual 62. Configuration Parameters Reference Table 62-13: 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 configure network >...
Page 946: Nat Parameters
Mediant 1000B Gateway & E-SBC Parameter Description Bronze QoS Defines the DiffServ value for the Bronze CoS content (OAMP applications). bronze-qos The valid range is 0 to 63. The default is 10. [BronzeServiceClassDiffServ] 62.2.6 NAT Parameters The Network Address Translation (NAT) parameters are described in the table below. Table 62-14: NAT Parameters Parameter Description...
Page 947: Dns Parameters
1. The parameter is used to allow SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT. It is needed to keep the NAT pinhole open for the SNMP messages sent from EMS to the device.
Page 948: Dhcp Parameters
Mediant 1000B Gateway & E-SBC Table 62-15: DNS Parameters Parameter Description Internal DNS Table Internal DNS Table The table defines the internal DNS table for resolving host names into IP addresses. configure network > dns dns-to-ip The format of the ini file table parameter is: [DNS2IP] [Dns2Ip] FORMAT Dns2Ip_Index = Dns2Ip_DomainName,...
Page 949 User's Manual 62. Configuration Parameters Reference Parameter Description [DHCP120OptionMode] Enables the acceptance of DHCP Option 120 in DHCP responses sent by a DHCP server.  [0] = DHCP Option 120 is not supported and ignored if received in the DHCP response. ...
Page 950: Ntp And Daylight Saving Time Parameters
Mediant 1000B Gateway & E-SBC Parameter Description server option The format of the ini file table parameter is as follows: [DhcpOption] [ DhcpOption ] FORMAT DhcpOption_Index = DhcpOption_DhcpServerIndex, DhcpOption_Option, DhcpOption_Type, DhcpOption_Value, DhcpOption_ExpandValue; [ \DhcpOption ] For a detailed description of the table, see Configuring Additional DHCP Options on page 217.
Page 951 User's Manual 62. Configuration Parameters Reference Parameter Description Identifier server. The NTP server may have several keys configured for different clients; this number identifies which key is used. auth-key-id The valid value is 1 to 65535. The default is 0 (i.e., no authentication is [NtpAuthKeyId] done).
Page 952: Debugging And Diagnostics Parameters
Mediant 1000B Gateway & E-SBC Parameter Description [DayLightSavingTimeOffset] you configure the parameter at 15:42, the device applies the setting only at 16:00. 62.3 Debugging and Diagnostics Parameters This subsection describes the device's debugging and diagnostic parameters. 62.3.1 General Parameters The general debugging and diagnostic parameters are described in the table below. Table 62-18: General Debugging and Diagnostic Parameters Parameter Description...
Page 953 User's Manual 62. Configuration Parameters Reference Parameter Description conditions, the Lifeline feature provides PSTN connectivity and thus call continuity for the FXS phone users. If the device is in Lifeline mode and the scenario that caused it to enter Lifeline (e.g., power outage) no longer exists (e.g., power returns), the device exists Lifeline and operates as normal.
Page 954: Sip Test Call Parameters
Mediant 1000B Gateway & E-SBC Parameter Description description of this feature, see Configuring Ground- or Loop-Start Signaling per Analog Port on page 205. Port Ground Start The table defines loop- or ground-start signaling per analog (FXS or [GroundKeyDetection_x] FXO) port. For the ini file parameter, the x denotes the port number, where 0 represents Port I.
Page 955: Syslog, Cdr And Debug Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description  This feature is applicable to all applications (Gateway and SBC). SBC Test ID Defines the SBC test call prefix (ID) for identifying SBC test calls that traverse the device to register with an external routing entity such as an sbc-test-id IP PBX or proxy server.
Page 956 Mediant 1000B Gateway & E-SBC Parameter Description  Syslog messages may increase the network traffic.  To configure Syslog SIP message logging levels, use the GwDebugLevel parameter.  By default, logs are also sent to the RS-232 serial port. For how to establish serial communication with the device, refer to the Installation Manual.
Page 957 User's Manual 62. Configuration Parameters Reference Parameter Description calls the media may start at ringback tone. A CDR is also sent upon termination (end) of the media in the call.  [3] Update & End Media = Sends a CDR when an update occurs in the media of the call.
Page 958 Mediant 1000B Gateway & E-SBC Parameter Description  [SyslogOptimization] [0] Disable  [1] Enable (default) Note: The size of the bundled message is configured by the MaxBundleSyslogLength parameter. mx-syslog-lgth Defines the maximum size (in bytes) threshold of logged Syslog messages bundled into a single UDP packet, after which they are [MaxBundleSyslogLength] sent to a Syslog server.
Page 959 User's Manual 62. Configuration Parameters Reference Parameter Description  [16] = (Default) local use 0 (local0)  [17] = local use 1 (local1)  [18] = local use 2 (local2)  [19] = local use 3 (local3)  [20] = local use 4 (local4) ...
Page 960 Mediant 1000B Gateway & E-SBC Parameter Description cache, register-unregister, and start-stop trunk. In the Web, these actions are typically done by clicking a button (e.g., the LOCK button). Note: For the ini file parameter, enclose values in single quotation marks, for example: ActivityListToLog = 'pvc', 'afl', 'dr', 'fb', 'swu', 'ard', 'naa', 'spc'.
Page 961: Resource Allocation Indication Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description Gateway CDR Format Table Gateway CDR Format The table defines CDR customization rules for Gateway calls. configure troubleshoot > cdr > The format of the ini file table parameter is: cdr-format gw-cdr-format [ GWCDRFormat ] [GWCDRFormat] FORMAT GWCDRFormat_Index = GWCDRFormat_CDRType,...
Page 962: Security Parameters
Mediant 1000B Gateway & E-SBC Parameter Description threshold, the device sends an SNMP acBoardCallResourcesAlarm alarm trap with a 'cleared' alarm status. The range is 0 to 100%. The default is 90%. [RAILoopTime] Defines the time interval (in seconds) that the device periodically checks call resource availability.
Page 963: Srtp Parameters
User's Manual 62. Configuration Parameters Reference Table 62-23: HTTPS Parameters Parameter Description Secured Web Connection Determines the protocol used to access the Web interface. (HTTPS)  [0] HTTP and HTTPS (default). configure system > web >  [1] HTTPs Only = Unencrypted HTTP packets are blocked. secured-connection Note: For the parameter to take effect, a device reset is required.
Page 964 Mediant 1000B Gateway & E-SBC Parameter Description Media Security Enables Secure Real-Time Transport Protocol (SRTP).  configure voip > media [0] Disable (default) security > media-security-  [1] Enable enable Note: For the parameter to take effect, a device reset is required. [EnableMediaSecurity] Media Security Behavior Global parameter that defines the handling of SRTP (when the...
Page 965: Tls Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description authentication-disable-tx [RTPAuthenticationDisableTx] Disable Encryption On Enables encryption on transmitted RTP packets in a secured RTP Transmitted RTP Packets session.  configure voip > media [0] Enable (default) security > RTP-encryption-  [1] Disable disable-tx [RTPEncryptionDisableTx] Disable Encryption On...
Page 966 Mediant 1000B Gateway & E-SBC Parameter Description configure network/security- The interval range is 0 to 1,500 minutes. The default is 0 (i.e., no settings/tls-re-hndshk-int TLS Re-Handshake). [TLSReHandshakeInterval] TLS Mutual Authentication Defines the device's mode of operation regarding mutual authentication and certificate verification for TLS connections. [SIPSRequireClientCertificate] ...
Page 967: Ssh Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description  If you configure the parameter to Server & Client, you also need to configure the SIPSRequireClientCertificate parameter to Enable.  For FQDN, the certificate may use wildcards (*) to replace parts of the domain name. TLS Client Verify Server Determines whether the device, when acting as a client for TLS Certificate...
Page 968: Ids Parameters
Mediant 1000B Gateway & E-SBC Parameter Description SSH Admin Key Defines the RSA public key for strong authentication for logging in to the SSH interface (if enabled). configure system > cli-settings > ssh-admin-key The value should be a base64-encoded string. The value can be a maximum length of 511 characters.
Page 969: Ocsp Parameters
User's Manual 62. Configuration Parameters Reference Parameter Description However, this "quiet" period must be at least twice the Threshold Window value. For example, if IDSAlarmClearPeriod is set to 20 sec and the Threshold Window is set to 15 sec, the IDSAlarmClearPeriod parameter is ignored and the alarm is cleared only after 30 seconds (2 x 15 sec).
Page 970: Quality Of Experience Parameters
Mediant 1000B Gateway & E-SBC Parameter Description [OCSPEnable] For a description of OCSP, see Configuring Certificate Revocation Checking (OCSP). Primary Server IP Defines the IP address of the OCSP server. configure network > ocsp > The default IP address is 0.0.0.0. server-ip [OCSPServerIP] Secondary Server IP...
Page 971 User's Manual 62. Configuration Parameters Reference Parameter Description [QOEEnableTLS] Note: For the parameter to take effect, a device reset is required. QoE TLS Context Name Selects a TLS Context (configured in the TLS Contexts table) for the TLS connection with the SEM server. configure voip >...
Page 972: Control Network Parameters
Mediant 1000B Gateway & E-SBC Parameter Description Profiles'' on page 302. Note: For the parameter to take effect, a device reset is required. Quality of Service Rules Table Quality of Service Rules Defines Quality of Service rules. configure voip > qoe The format of the ini file table parameter is as follows: quality-of-service-rules [ QualityOfServiceRules ]...
Page 973 User's Manual 62. Configuration Parameters Reference Parameter Description IP Groups This table configures IP Groups. configure voip > ip-group The format of the ini file table parameter is: [IPGroup] [ IPGroup ] FORMAT IPGroup_Index = IPGroup_Type, IPGroup_Name, IPGroup_ProxySetName, IPGroup_SIPGroupName, IPGroup_ContactUser, IPGroup_SipReRoutingMode, IPGroup_AlwaysUseRouteTable, IPGroup_SRDName, IPGroup_MediaRealm, IPGroup_ClassifyByProxySet, IPGroup_ProfileName, IPGroup_MaxNumOfRegUsers,...
Page 974 Mediant 1000B Gateway & E-SBC Parameter Description Accounts Defines user accounts for registering and/or authenticating (digest) Trunk Groups or IP Groups (e.g., an IP-PBX) with a configure voip > sip-definition Serving IP Group (e.g., a registrar server). account The format of the ini file table parameter is as follows: [Account] [Account] FORMAT Account_Index = Account_ServedTrunkGroup,...
Page 975 User's Manual 62. Configuration Parameters Reference Parameter Description configure voip > sip-definition Proxy after using a redundant Proxy. settings > redundancy-mode  [0] Parking = (Default) The device continues working with a [ProxyRedundancyMode] redundant (now active) Proxy until the next failure, after which it works with the next redundant Proxy.
Page 976 Mediant 1000B Gateway & E-SBC Parameter Description destination and then sends a new INVITE to this destination. Note:  The parameter is applicable only to the Gateway application.  When the parameter is set to [1] and the INVITE sent to the Proxy fails, the device re-routes the call according to the Standard mode [0].
Page 977 User's Manual 62. Configuration Parameters Reference Parameter Description four Proxy IP addresses. Thus, if the first SRV query returns two domain names and the A-record queries return two IP addresses each, no additional searches are performed.  [2] NAPTR = NAPTR query is done. If successful, an SRV query is sent according to the information received in the NAPTR response.
Page 978 Mediant 1000B Gateway & E-SBC Parameter Description proxy-and-registration > cnonce- The value is free format, i.e., 'Cnonce = 0a4f113b'. The default is 4-auth 'Default_Cnonce'. [Cnonce] Challenge Caching Mode Enables local caching of SIP message authorization challenges from Proxy servers. configure voip > sip- definition settings >...
Page 979 User's Manual 62. Configuration Parameters Reference Parameter Description ProxySet_ProxyRedundancyMode, ProxySet_DNSResolveMethod, ProxySet_KeepAliveFailureResp, ProxySet_GWIPv4SIPInterfaceName, ProxySet_SBCIPv4SIPInterfaceName, ProxySet_GWIPv6SIPInterfaceName, ProxySet_SBCIPv6SIPInterfaceName; [ \ProxySet ] For a description of the table, see ''Configuring Proxy Sets'' on page 346. Registrar Parameters Enable Registration Enables the device to register to a Proxy/Registrar server. ...
Page 980 Mediant 1000B Gateway & E-SBC Parameter Description Registrar Transport Type Determines the transport layer used for outgoing SIP dialogs initiated by the device to the Registrar. configure voip > sip-definition  settings > registrar-transport [-1] Not Configured (default)  [0] UDP [RegistrarTransportType] ...
Page 981 User's Manual 62. Configuration Parameters Reference Parameter Description  The remote SIP UA abandons a call before the device has received any provisional response (indicative of an outbound proxy server failure).  The remote SIP UA abandons a call and the only provisional response the device has received for the call is 100 Trying (indicative of a home proxy server failure, i.e., the failure of a proxy in the route after the outbound...
Page 982 Mediant 1000B Gateway & E-SBC Parameter Description Set Out-Of-Service On Enables setting the endpoint, trunk, or entire device (i.e., all Registration Failure endpoints) to out-of-service if registration fails.  configure voip > sip-definition [0] Disable (default) proxy-and-registration > set-oos-  [1] Enable on-reg-failure If the registration is per endpoint (i.e., AuthenticationMode is set...
Page 983 User's Manual 62. Configuration Parameters Reference Parameter Description For example: Authorization: Digest username=alice_private@home1.net, realm=”home1.net”, nonce=””, response=”e56131d19580cd833064787ecc” Note: This registration header is according to the IMS 3GPP TS24.229 and PKT-SP-24.220 specifications. Add initial Route Header Enables the inclusion of the SIP Route header in initial registration or re-registration (REGISTER) requests sent by the configure voip >...
Page 984: Network Application Parameters
Mediant 1000B Gateway & E-SBC Parameter Description [PingPongKeepAliveTime] The default range is 5 to 2,000,000. The default is 120. The device uses the range of 80-100% of this user-defined value as the actual interval. For example, if the parameter value is set to 200 sec, the interval used is any random time between 160 to 200 seconds.
Page 985 User's Manual 62. Configuration Parameters Reference Parameter Description SIP Interfaces Table SIP Interfaces Defines SIP Interfaces. configure voip > sip- The format of the ini file table parameter is as follows: interface [ SIPInterface ] [SIPInterface] FORMAT SIPInterface_Index = SIPInterface_InterfaceName, SIPInterface_NetworkInterface, SIPInterface_ApplicationType, SIPInterface_UDPPort, SIPInterface_TCPPort, SIPInterface_TLSPort, SIPInterface_SRDName, SIPInterface_MessagePolicyName,...
Page 986: General Sip Parameters
Mediant 1000B Gateway & E-SBC Parameter Description For a detailed description of the table, see ''Configuring NAT Translation per IP Interface'' on page 148. Media Realms table Media Realms Defines Media Realms. configure voip > realm The format of the ini file table parameter is as follows: [CpMediaRealm] [ CpMediaRealm ] FORMAT CpMediaRealm_Index = CpMediaRealm_MediaRealmName,...
Page 987 (if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Max SIP Message Length Defines the maximum size (in Kbytes) for each SIP message that can [KB] be sent over the network.
Page 988 Mediant 1000B Gateway & E-SBC Parameter Description cancel-after-connect CANCEL can be sent only during the INVITE transaction (before 200 OK), and once a 200 OK response is received the call can be rejected [RejectCancelAfterConnect] only by a BYE request.  [0] Disable = (Default) Accepts a CANCEL request received during the INVITE transaction by sending a 200 OK response and terminates the call session.
Page 989 User's Manual 62. Configuration Parameters Reference Parameter Description CSeq: 1 BYE X-RTP-Stat: PS=207;OS=49680;;PR=314;OR=50240;PL=0;JI=600;LA=40 Supported: em,timer,replaces,path,resource- priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRAC K,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Sip-Gateway-/v.7.20A.000.038 Reason: Q.850 ;cause=16 ;text="local" Content-Length: 0 PRACK Mode Determines the PRACK (Provisional Acknowledgment) mechanism mode for SIP 1xx reliable responses. prack-mode ...
Page 990 Mediant 1000B Gateway & E-SBC Parameter Description response, and the voice channel remains open. However, if the device did not send a 183 with an SDP and it receives an Alert without PI, the device sends a 180 (without SDP). If it receives an Alert with PI it sends a 183with an SDP.
Page 991 User's Manual 62. Configuration Parameters Reference Parameter Description Minimum Session-Expires Defines the time (in seconds) in the SIP Min-SE header. The header defines the minimum time that the user agent refreshes the session. configure voip > sbc settings > min-session-expires The valid range is 10 to 100,000.
Page 992 Mediant 1000B Gateway & E-SBC Parameter Description  [3] Don’t Reply and Send = Both options [1] and [2] are applied. Note:  The parameter is only applicable to digital interfaces.  When the parameter is set to not respond to SIP OPTIONS received from the proxy, it is applicable only if the OPTIONS message does not include a user part in the Request-URI.
Page 993 User's Manual 62. Configuration Parameters Reference Parameter Description Note:  If VBD coder negotiation fails at call start and if the IsFaxUsed parameter is set to 1 (or 3), then the channel opens with the FaxTransportMode parameter set to 1 (relay) to allow future detection of fax tones and sending of T.38 Re-INVITES.
Page 994 Mediant 1000B Gateway & E-SBC Parameter Description TCP/TLS Connection Reuse Enables the reuse of an established TCP or TLS connection between the device and a SIP user agent (UA) for subsequent SIP requests tcp-conn-reuse sent to the UA. Any new requests (e.g., INVITE or REGISTER) uses [EnableTCPConnectionReu the same secured connection.
Page 995 User's Manual 62. Configuration Parameters Reference Parameter Description port [SIPDestinationPort] Use user=phone in SIP URL Determines whether the 'user=phone' string is added to the SIP URI and SIP To header. configure voip > sip-  definition settings > [0] No = 'user=phone' string is not added. user=phone-in-url ...
Page 996 Mediant 1000B Gateway & E-SBC Parameter Description table: SIP Reason Code ISDN Redirecting Reason 302 - Moved Temporarily Call Forward Universal (CFU) 408 - Request Timeout Call Forward No Answer (CFNA) 480 - Temporarily Unavailable 487 - Request Terminated 486 - Busy Here Call Forward Busy (CFB) 600 - Busy Everywhere ...
Page 997 User's Manual 62. Configuration Parameters Reference Parameter Description IE of “Voice”, and “Speech” Bearer Capability IE. Note that the Off Hook Indicator IE is described in UCR 2008 specifications. - The device interworks the SIP tgrp=hotline-ccdata parameter (received in INVITE) to ISDN Setup with an Off Hook Indicator IE of “Data”, and with “Unrestricted 64k”...
Page 998 Mediant 1000B Gateway & E-SBC Parameter Description INVITE sip:200;tgrp=7;trunk- context=example.com@10.33.2.68;user=phone SIP/2.0 Note:  For enabling routing based on the 'tgrp' parameter, the UseSIPTgrp parameter must be set to 2.  For IP-to-Tel routing based on the 'dtg' parameter (instead of the 'tgrp' parameter), use the parameter UseBroadsoftDTG.
Page 999 > user- agent-info User-Agent: myproduct/v.7.20A.000.038 [UserAgentDisplayInfo] If not configured, the default string, <AudioCodes product- name>/software version' is used, for example: User-Agent: Audiocodes-Sip-Gateway-Medaint 1000B Gateway and SBC/v.7.20A.000.038 The maximum string length is 50 characters.
Page 1000 Mediant 1000B Gateway & E-SBC Parameter Description session-owner "AudiocodesGW". [SIPSDPSessionOwner] For example: o=AudiocodesGW 1145023829 1145023705 IN IP4 10.33.4.126 configure voip > sip- Enables the device to ignore new SDP re-offers (from the media definition settings > sdp-ver- negotiation perspective) in certain scenarios (such as session expires). nego According to RFC 3264, once an SDP session is established, a new SDP offer is considered a new offer only when the SDP origin value is...
Page 1001 User's Manual 62. Configuration Parameters Reference Parameter Description Multiple Packetization Time Determines whether the 'mptime' attribute is included in the outgoing Format SDP.  configure voip > sip- [0] None = (Default) Disabled. definition settings > mult-  [1] PacketCable = Includes the 'mptime' attribute in the outgoing ptime-format SDP - PacketCable-defined format.
Page 1002 Mediant 1000B Gateway & E-SBC Parameter Description that the proxy is out of service for the defined "Retry-After" period. Enable P-Associated-URI Determines the device usage of the P-Associated-URI header. This Header header can be received in 200 OK responses to REGISTER requests. When enabled, the first URI in the P-Associated-URI header is used in p-associated-uri-hdr subsequent requests as the From/P-Asserted-Identity headers value.
Page 1003 User's Manual 62. Configuration Parameters Reference Parameter Description Gateway Name Defines a name for the device (e.g., device123.com). This name is used as the host part of the SIP URI in the From header. If not configure voip > sip- specified, the device's IP address is used instead (default).
Page 1004 Mediant 1000B Gateway & E-SBC Parameter Description provider. Typically, if the device receives a call with blocked Caller ID from the PSTN side (e.g., Trunk connected to a PBX), it sends an INVITE to the IP with a From header as follows: From: “anonymous” <anonymous@anonymous.invalid>.
Page 1005 User's Manual 62. Configuration Parameters Reference Parameter Description parmeter. Enable X-Channel Header Enables the device to add the SIP X-Channel header to outgoing SIP messages. The header provides information on the physical Trunk/B- configure voip > sip- channel on which the call is received or sent. definition settings >...
Page 1006 Mediant 1000B Gateway & E-SBC Parameter Description 56. The payload type is negotiated with the remote side, i.e., the selected payload type is according to the remote side selection. The receiving device must include the 'Transparent' coder in its coder list. Note: The parameter is applicable only to digital interfaces.
Page 1007 User's Manual 62. Configuration Parameters Reference Parameter Description [TimeoutBetween100And18 The valid range is 0 to 180,000 (i.e., 3 minutes). The default is 32000 (i.e., 32 sec). configure voip > sip- Determines if and when the device sends a 100 Trying in response to definition settings >...
Page 1008 Mediant 1000B Gateway & E-SBC Parameter Description  [2] = The 'ecan' attribute is not included in the SDP.  [3] = The 'ecan' attribute and the 'vbd' parameter are not included in the SDP. Note: The parameter is applicable only when the IsFaxUsed parameter is set to 2, and for re-INVITE messages generated by the device as result of modem or fax tone detection.
Page 1009 User's Manual 62. Configuration Parameters Reference Parameter Description 8277765 To: <sip:notavailable@unknown.invalid>;tag=svw-0-1229428367 Call-ID: ConorCCR-0-LU-1229417827103300@dtas- stdn.fs5000group0-000.l CSeq: 1 INFO Contact: sip:10.20.7.70:5060 Content-Type: application/On-Hook (application/Off-Hook) Content-Length: 0 Note:  The parameter is applicable only if the parameter RegretTime is configured.  The parameter is applicable only to FXS interfaces. PSTN Alert Timeout Digital: Defines the Alert Timeout (in seconds) for calls sent to the PSTN.
Page 1010 Mediant 1000B Gateway & E-SBC Parameter Description RTPOnlyMode parameter value is ignored. [RTPOnlyModeForTrunk_x] Enables the RTP Only feature per trunk. The x in the parameter name denotes the trunk number, where 0 is Trunk 1. For a description of the parameter, see the RTPOnlyMode parameter.
Page 1011 User's Manual 62. Configuration Parameters Reference Parameter Description inbound-map-set MessageManipulations parameter. By default, no manipulation is done (i.e. Manipulation Set ID is set to -1). [GWInboundManipulationSe Note: The parameter is applicable only to the Gateway application. configure voip > gateway Selects the Manipulation Set ID for manipulating all outbound INVITE manipulation settings >...
Page 1012 Mediant 1000B Gateway & E-SBC Parameter Description table). In such a scenario, all the physical trunks of the Trunk Group are set to the Busy Out condition. Each trunk uses the out-of-service method according to the ISDN/CAS variant.  To configure the method for taking trunks/channels out-of- service, see the DigitalOOSBehaviorForTrunk_x parameter for per trunk or the DigitalOOSBehavior parameter for all trunks.