Page 1 User's Manual Enterprise Session Border Controller Analog & Digital VoIP Media Gateway Mediant™ 1000B Gateway & E-SBC Version 6.8 November 2014 Document # LTRT-27034...
Page 3: Table Of Contents
Getting Familiar with CLI ..................67 7.1.1 Understanding Configuration Modes ............... 67 7.1.2 Using CLI Shortcuts ....................68 7.1.3 Common CLI Commands ..................69 7.1.4 Configuring Tables in CLI ..................70 7.1.5 Understanding CLI Error Messages ................ 70 Version 6.8 Mediant 1000B Gateway & SBC...
Page 4 Mediant 1000B Gateway & SBC Enabling CLI ......................71 7.2.1 Enabling Telnet for CLI .................... 71 7.2.2 Enabling SSH with RSA Public Key for CLI ............. 72 Establishing a CLI Session ..................73 Configuring Maximum Telnet/SSH Sessions ............74 Viewing and Terminating Current CLI Sessions ............ 75 Configuring Displayed Output Lines in CLI Terminal Window .......
Page 5 14.2.2.2 G.711 Fax / Modem Transport Mode ............ 162 14.2.2.3 Fax Fallback ..................163 14.2.2.4 Fax/Modem Bypass Mode ..............164 14.2.2.5 Fax / Modem NSE Mode ............... 165 14.2.2.6 Fax / Modem Transparent with Events Mode ........166 Version 6.8 Mediant 1000B Gateway & SBC...
Page 6 Mediant 1000B Gateway & SBC 14.2.2.7 Fax / Modem Transparent Mode ............166 14.2.2.8 RFC 2833 ANS Report upon Fax/Modem Detection ......167 14.2.3 V.34 Fax Support ....................167 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission ........168 14.2.3.2 Relay Mode for T.30 and V.34 Faxes ........... 168 14.2.4 V.152 Support ......................168...
Page 7 Gateway Application .....................329 20 Introduction ..................... 331 21 Digital PSTN ..................... 333 21.1 Configuring Trunk Settings ................... 333 21.2 TDM and Timing ....................336 21.2.1 Configuring TDM Bus Settings ................336 21.2.2 Clock Settings ......................336 Version 6.8 Mediant 1000B Gateway & SBC...
Page 8 Mediant 1000B Gateway & SBC 21.2.2.1 Recovering Clock from PSTN Line Interface ........337 21.2.2.2 Configuring Internal Clock as Clock Source ......... 337 21.3 Configuring CAS State Machines ................. 338 21.4 Configuring Digital Gateway Parameters ............. 340 21.5 Tunneling Applications ..................341 21.5.1 TDM Tunneling ......................341...
Page 9 26.11.4.1 About E9-1-1 Services ................435 26.11.4.2 Microsoft Lync Server 2010 and E9-1-1 ..........436 26.11.4.3 AudioCodes ELIN Gateway for Lync Server 2010 E9-1-1 Calls to PSTN 26.11.4.4 Configuring AudioCodes ELIN Gateway ..........444 26.12 Multilevel Precedence and Preemption ..............447 26.12.1 MLPP Preemption Events in SIP Reason Header ..........449...
Page 10 Mediant 1000B Gateway & SBC 27.3 Configuring FXO Settings ..................459 27.4 Configuring Authentication ................... 460 27.5 Configuring Automatic Dialing ................462 27.6 Configuring Caller Display Information ..............463 27.7 Configuring Call Forward ..................464 27.8 Configuring Caller ID Permissions ............... 466 27.9 Configuring Call Waiting ..................
Page 11 29.5.3 Configuring SBC IP-to-IP Routing .................530 29.5.4 Configuring SIP Response Codes for Alternative Routing Reasons .....538 29.6 SBC Manipulations ....................540 29.6.1 Configuring IP-to-IP Inbound Manipulations ............542 29.6.2 Configuring IP-to-IP Outbound Manipulations ............545 Cloud Resilience Package ..................551 Version 6.8 Mediant 1000B Gateway & SBC...
Page 12 Mediant 1000B Gateway & SBC 30 CRP Overview ....................553 31 CRP Configuration ..................555 31.1 Enabling the CRP Application ................555 31.2 Configuring Call Survivability Mode ..............556 31.3 Pre-Configured IP Groups ..................557 31.4 Pre-Configured IP-to-IP Routing Rules ..............558 31.4.1 Normal Mode ......................558...
Page 13 37.1.1.2 Provisioning from TFTP Server using DHCP Option 66 ....... 611 37.1.2 HTTP-based Provisioning ..................611 37.1.3 FTP- or NFS-based Provisioning ................612 37.1.4 Provisioning using AudioCodes EMS ..............612 37.2 HTTP/S-Based Provisioning using the Automatic Update Feature ...... 613 37.2.1 Files Provisioned by Automatic Update ..............613 37.2.2 File Location for Automatic Update ...............613...
Page 14 45 Syslog and Debug Recordings ..............677 45.1 Syslog Message Format ..................677 45.1.1 Event Representation in Syslog Messages ............678 45.1.2 Identifying AudioCodes Syslog Messages using Facility Levels ......680 45.1.3 Syslog Fields for Answering Machine Detection (AMD) ........680 45.1.4 SNMP Alarms in Syslog Messages ...............681 45.2 Enabling Syslog ....................
Page 15 51.7 General SIP Parameters ..................772 51.8 Coders and Profile Parameters ................800 51.9 Channel Parameters .................... 803 51.9.1 Voice Parameters ....................803 51.9.2 Coder Parameters ....................805 51.9.3 DTMF Parameters ....................806 51.9.4 RTP, RTCP and T.38 Parameters .................807 Version 6.8 Mediant 1000B Gateway & SBC...
Page 16 Mediant 1000B Gateway & SBC 51.10 Gateway and IP-to-IP Parameters ............... 812 51.10.1 Fax and Modem Parameters .................812 51.10.2 DTMF and Hook-Flash Parameters ...............817 51.10.3 Digit Collection and Dial Plan Parameters .............822 51.10.4 Voice Mail Parameters ...................825 51.10.5 Supplementary Services Parameters ..............830 51.10.5.1 Caller ID Parameters ................
Page 17 52.2 DSP Templates and Channel Capacity .............. 1013 52.2.1 Analog (FXS/FXO) Interfaces ................1013 52.2.2 BRI Interfaces ..................... 1014 52.2.3 E1/T1 Interfaces ....................1015 52.2.4 Media Processing Interfaces ................1016 53 Technical Specifications ................1019 Version 6.8 Mediant 1000B Gateway & SBC...
Page 18 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 19: Weee Eu Directive
User's Manual Notices Notice This document describes AudioCodes Mediant 1000B Gateway & Enterprise Session Border Controller (E-SBC). Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.
Page 20: Related Documentation
Mediant 1000B Gateway & SBC Related Documentation Manual Name SIP CPE Release Notes Mediant 1000B Gateway and E-SBC Hardware Installation Manual Complementary Guides CLI Reference Guide CPE Configuration Guide for IP Voice Mail SNMP Reference Guide SBC Design Guide Recommended Security Guidelines Configuration Note...
Page 21 Some of the features listed in this document are available only if the relevant Software License Key has been purchased from AudioCodes and installed on the device. For a list of Software License Keys that can be purchased, please consult your AudioCodes sales representative.
Page 22 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 23: Overview
User's Manual 1. Overview Overview AudioCodes' Mediant 1000B Gateway and E-SBC (hereafter referred to as device) is a member of AudioCodes family of Enterprise Session Border Controllers (E-SBC), enabling connectivity and security between small medium businesses (SMB) and service providers' VoIP networks.
Page 24 Mediant 1000B Gateway & SBC The device also provides up to 6 Ethernet ports (2 ports on the CRMX module and 4 ports on the LAN Expansion module). These ports operate in port-pair redundancy, providing up to 3 port-pair groups. The port groups can be assigned to IP network interfaces enabling physical separation between interfaces.
Page 25: Getting Started With Initial Connectivity
Part I Getting Started with Initial Connectivity...
Page 27: Introduction
User's Manual 2. Introduction Introduction This part describes how to initially access the device's management interface and change its default IP address to correspond with your networking scheme. Version 6.8 Mediant 1000B Gateway & SBC...
Page 28 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 29: Default Oamp Ip Address
Table 3-1: Default VoIP LAN IP Address for OAMP IP Address Value OAMP + Media + Control Application Type IP Address 192.168.0.2 Prefix Length 255.255.255.0 (24) 192.168.0.1 Default Gateway Underlying Device Interface Name "O+M+C" Version 6.8 Mediant 1000B Gateway & SBC...
Page 30 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 31: Configuring Voip Lan Interface For Oamp
Physical Ports Table) and then configure the device's physical Ethernet port-pair (group) that you want to later assign to the OAMP interface. For more information, see Configuring Physical Ethernet Ports on page 109. Version 6.8 Mediant 1000B Gateway & SBC...
Page 32 Mediant 1000B Gateway & SBC Open the Interface Table page (Configuration tab > VoIP menu > Network > IP Interfaces Table). Select the 'Index' radio button corresponding to the OAMP + Media + Control application type, and then click Edit.
Page 33: Cli
Access the VoIP configuration mode: # configure voip Access the Interface table: (config-voip)# interface network-if 0 Configure the IP address: (network-if-0)# ip-address <IP address> Configure the prefix length: (network-if-0)# prefix-length <prefix length / subnet mask, e.g., 16> Version 6.8 Mediant 1000B Gateway & SBC...
Page 34 Mediant 1000B Gateway & SBC Configure the Default Gateway address: (network-if-0)# gateway <IP address> Exit the Interface table: (network-if-0)# exit Exit the VoIP configuration mode: (config-voip)# exit Reset the device with a flash burn: # reload now Cable the device to your network. You can now access the device's management interface using this new OAMP IP address.
Page 35: Management Tools
Part II Management Tools...
Page 37: Introduction
Web, CLI, and ini file parameter is mentioned. The ini file parameters are enclosed in square brackets [...]. • For a list and description of all the configuration parameters, see ''Configuration Parameters Reference'' on page 715. Version 6.8 Mediant 1000B Gateway & SBC...
Page 38 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 39: Web-Based Management
• ® Mozilla Firefox (Versions 5 through 9.0)  Recommended screen resolutions: 1024 x 768 pixels, or 1280 x 1024 pixels Note: Your Web browser must be JavaScript-enabled to access the Web interface. Version 6.8 Mediant 1000B Gateway & SBC...
Page 40: Accessing The Web Interface
Mediant 1000B Gateway & SBC 6.1.2 Accessing the Web Interface The following procedure describes how to access the Web interface.  To access the Web interface: Open a standard Web browser (see ''Computer Requirements'' on page 39). In the Web browser, specify the OAMP IP address of the device (e.g., http://10.1.10.10);...
Page 41: Areas Of The Gui
''Navigation Tree'' on page 42. Work pane, displaying the configuration page of the selected menu in the Navigation tree. This is where configuration is done. For more information, see ''Working with Configuration Pages'' on page 45. Version 6.8 Mediant 1000B Gateway & SBC...
Page 42: Toolbar Description
Mediant 1000B Gateway & SBC 6.1.4 Toolbar Description The toolbar provides frequently required command buttons, described in the table below: Table 6-2: Description of Toolbar Buttons Icon Button Description Name Submit Applies parameter settings to the device (see ''Saving Configuration'' on page 568).
Page 43: Displaying Navigation Tree In Basic And Full View
The expanded view displays all the menus pertaining to the selected configuration tab; the reduced view displays only commonly used menus.  To display a reduced menu tree, select the Basic option (default). Version 6.8 Mediant 1000B Gateway & SBC...
Page 44: Showing / Hiding The Navigation Pane
Mediant 1000B Gateway & SBC  To display all menus and submenus, select the Advanced option. Figure 6-4: Basic and Full View Options Note: After you reset the device, the Web GUI is displayed in Basic view. 6.1.5.2 Showing / Hiding the Navigation Pane You can hide the Navigation pane to provide more space for elements displayed in the Work pane.
Page 45: Working With Configuration
 Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.  Basic Parameter List button with up-pointing arrow: click this button to show only common (basic) parameters. Version 6.8 Mediant 1000B Gateway & SBC...
Page 46 Mediant 1000B Gateway & SBC The figure below shows an example of a page displaying basic parameters only. If you click the Advanced Parameter List button (shown below), the page will also display the advanced parameters. Figure 6-6: Toggling between Basic and Advanced View Notes: •...
Page 47: Modifying And Saving Parameters
Thus, to ensure parameter changes (whether on-the-fly or not) are retained, save ('burn') them to the device's non-volatile memory, i.e., flash (see ''Saving Configuration'' on page 568). Version 6.8 Mediant 1000B Gateway & SBC...
Page 48: Working With Tables
Mediant 1000B Gateway & SBC If you enter an invalid parameter value (e.g., not in the range of permitted values) and then click Submit, a message box appears notifying you of the invalid value. In addition, the parameter value reverts to its previous value and is highlighted in red, as shown in the...
Page 49: Searching For Configuration Parameters
The search key can include the full parameter name (e.g., "EnableSyslog") or a substring of it (e.g., "sys"). If you search for a substring, all parameters containing the specified substring in their names are listed in the search result. Version 6.8 Mediant 1000B Gateway & SBC...
Page 50 Mediant 1000B Gateway & SBC  To search for a parameter: On the Navigation bar, click the Search tab; the Search engine appears in the Navigation pane. In the field alongside the Search button, enter the parameter name or a substring of the name for which you want to search.
Page 51: Creating A Login Welcome Message
20 lines (or rows) of text can be defined. 6.1.9 Getting Help The Web interface provides you with context-sensitive Online Help. The Online Help provides brief descriptions of parameters pertaining to the currently opened page. Version 6.8 Mediant 1000B Gateway & SBC...
Page 52: Logging Off The Web Interface
Mediant 1000B Gateway & SBC  To view the Help topic of a currently opened page: On the toolbar, click the Help button; the Help topic pertaining to the opened page appears, as shown below: Figure 6-14: Help Topic for Current Page To view a description of a parameter, click the plus sign to expand the parameter.
Page 53: Viewing The Home Page
"LOCKED": device is locked (i.e. no new calls are accepted) • "UNLOCKED": device is not locked • "SHUTTING DOWN": device is currently shutting down To perform these operations, see ''Basic Maintenance'' on page 565. Version 6.8 Mediant 1000B Gateway & SBC...
Page 54 Mediant 1000B Gateway & SBC The table below describes the areas of the Home page. Table 6-7: Home Page Description Item # Description Displays the highest severity of an active alarm raised (if any) by the device:  Green: No alarms ...
Page 55: Assigning A Port Name
Click the required port icon; a shortcut menu appears: From the shortcut menu, choose Update Port Info; a text box appears: Type a brief description for the port, and then click Apply Port Info. Version 6.8 Mediant 1000B Gateway & SBC...
Page 56: Configuring Web User Accounts
Mediant 1000B Gateway & SBC Configuring Web User Accounts Web user accounts define users for the Web interface and CLI. User accounts permit login access to these interfaces as well as different levels of read and write privileges. Thus, user accounts prevent unauthorized access to these interfaces, permitting access only to users with correct credentials (i.e., username and password).
Page 57: Basic User Accounts Configuration
The username and password can be a string of up to 19 characters and are case- sensitive. • When only the basic user accounts are being used, up to two users can be concurrently logged in to the Web interface, and they can be the same user. Version 6.8 Mediant 1000B Gateway & SBC...
Page 58 Mediant 1000B Gateway & SBC  To configure the two pre-configured Web user accounts: Open the Web User Accounts page (Configuration tab > System menu > Web User Accounts). If you are logged in as Security Administrator, both Web user accounts are displayed (as shown below).
Page 59: Advanced User Accounts Configuration
Subsequent access: Configuration tab > System menu > Web User Accounts. The Web Users table appears, listing the two default, pre-configured Web use accounts - Security Administrator ("Admin") and Monitor ("User"): Figure 6-17: Web Users Table Page Version 6.8 Mediant 1000B Gateway & SBC...
Page 60 Mediant 1000B Gateway & SBC Click Add; the following dialog box is displayed: Figure 6-18: Web Users Table - Add Record Dialog Box Configure a Web user according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory.
Page 61 The default is according to the settings of the 'Deny Authentication Timer' parameter (see ''Configuring Web Security Settings'' on page 63). Note: The 'Deny Authentication Timer' parameter relates to failed Web logins from specific IP addresses. Version 6.8 Mediant 1000B Gateway & SBC...
Page 62: Displaying Login Information Upon Login
Mediant 1000B Gateway & SBC Parameter Description Web: User Level Defines the user's access level. CLI: user-level  Monitor = (Default) Read-only user. This user can only view Web pages and access to security-related pages is denied.  Administrator = Read/write privileges for all pages, except security- related pages including the Web Users table where this user has only read-only privileges.
Page 63: Configuring Web Security Settings
Management > WEB Security Settings). Set the 'Secured Web Connection (HTTPS)' parameter to HTTPS Only. Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 568. Version 6.8 Mediant 1000B Gateway & SBC...
Page 64: Web Login Authentication Using Smart Cards
This feature is enabled using the EnableMgmtTwoFactorAuthentication parameter. Note: For specific integration requirements for implementing a third-party smart card for Web login authentication, contact your AudioCodes representative.  To log in to the Web interface using CAC: Insert the Common Access Card into the card reader.
Page 65 PC is denied. • Delete your PC's IP address last from the 'Web & Telnet Access List page. If it is deleted before the last, subsequent access to the device from your PC is denied. Version 6.8 Mediant 1000B Gateway & SBC...
Page 66 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 67: Cli-Based Management
Enable mode upon initial login. For configuring user access levels, see Configuring Web User Accounts on page 56. • The default password for accessing the Enable mode is "Admin" (case-sensitive). To change this password, use the CLIPrivPass ini file parameter. Version 6.8 Mediant 1000B Gateway & SBC...
Page 68: Using Cli Shortcuts
Mediant 1000B Gateway & SBC The Enable mode groups the configuration commands under the following command sets: • config-system: Provides the general and system related configuration commands, for example, Syslog configuration. This set is accessed by typing the following command:...
Page 69: Common Cli Commands
| <filter> Applied to a command output. The filter should be typed after the command with a pipe mark (|). Supported filters:  include <word> – filter (print) lines which contain <word> Version 6.8 Mediant 1000B Gateway & SBC...
Page 70: Configuring Tables In Cli
Mediant 1000B Gateway & SBC Command Description  exclude <word> – filter lines which does not contain <word>  grep <options> - filter lines according to grep common Unix utility options  egrep <options> - filter lines according to egrep common Unix utility options ...
Page 71: Enabling Cli
Configure the other Tenet parameters as required. For a description of these parameters, see ''Telnet Parameters'' on page 719. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 1000B Gateway & SBC...
Page 72: Enabling Ssh With Rsa Public Key For Cli
Mediant 1000B Gateway & SBC 7.2.2 Enabling SSH with RSA Public Key for CLI Unless configured for TLS, Telnet is not secure as it requires passwords to be transmitted in clear text. To overcome this, Secure SHell (SSH) is used, which is the de-facto standard for secure CLI.
Page 73: Establishing A Cli Session
Secure SHell (SSH): The device can be accessed through its Ethernet interface by the SSH protocol using SSH client software. A popular and freeware SSH client software is Putty, which can be downloaded from www.chiark.greenend.org.uk/~sgtatham/putty/download.html. Version 6.8 Mediant 1000B Gateway & SBC...
Page 74: Configuring Maximum Telnet/Ssh Sessions
Mediant 1000B Gateway & SBC  Telnet: The device can be accessed through its Ethernet interface by the Telnet protocol using Telnet client software.The following procedure describes how to establish a CLI session with the device. The following procedure describes how to access the CLI through Telnet/SSH.
Page 75: Viewing And Terminating Current Cli Sessions
When this command is run, it ends the Telnet/SSH session (logs out the RS-232 session) and displays the CLI login prompt. Note: The session from which the command is run cannot be terminated. Version 6.8 Mediant 1000B Gateway & SBC...
Page 76: Configuring Displayed Output Lines In Cli Terminal Window
Mediant 1000B Gateway & SBC Configuring Displayed Output Lines in CLI Terminal Window You can configure the maximum number of lines (height) displayed in the terminal window for the output of CLI commands (Telnet and SSH). The number of displayed lines can be specified from 0 to 65,535, or determined by re-sizing the terminal window by mouse- dragging the window's border.
Page 77: Snmp-Based Management
SNMP Manager. All supported MIB files are supplied to customers as part of the release. AudioCodes EMS is an advanced solution for standards-based management that covers all areas vital for the efficient operation, administration, management and provisioning (OAM&P) of the device.
Page 78: Configuring Snmp Trap Destinations
Mediant 1000B Gateway & SBC  To configure SNMP community strings: Open the SNMP Community String page (Configuration tab > System menu > Management > SNMP > SNMP Community String). Configure SNMP community strings according to the table below. Click Submit, and then save ("burn") your settings to flash memory.
Page 79 (default) = SNMPv2 user community string  SNMPv3 user configured in ''Configuring SNMP V3 Users'' on page Trap Enable Activates the sending of traps to the SNMP Manager. [SNMPManagerTrapSendingEnable_x]  [0] Disable  [1] Enable (Default) Version 6.8 Mediant 1000B Gateway & SBC...
Page 80: Configuring Snmp Trusted Managers
Mediant 1000B Gateway & SBC Configuring SNMP Trusted Managers The SNMP Trusted Managers table lets you configure up to five SNMP Trusted Managers based on IP addresses. By default, the SNMP agent accepts SNMP Get and Set requests from any IP address as long as the correct community string is used in the request.
Page 81 [0] None (default) [SNMPUsers_PrivProtocol]  [1] DES  [2] 3DES  [3] AES-128  [4] AES-192  [5] AES-256 Authentication Key Authentication key. Keys can be entered in the form of a text Version 6.8 Mediant 1000B Gateway & SBC...
Page 82 Mediant 1000B Gateway & SBC Parameter Description CLI: auth-key password or long hex string. Keys are always persisted as long hex [SNMPUsers_AuthKey] strings and keys are localized. Privacy Key Privacy key. Keys can be entered in the form of a text password or CLI: priv-key long hex string.
Page 83: Ini File-Based Management
The table ini file parameter is composed of the following elements:  Title of the table: The name of the table in square brackets, e.g., [MY_TABLE_NAME].  Format line: Specifies the columns of the table (by their string names) that are to be Version 6.8 Mediant 1000B Gateway & SBC...
Page 84 Mediant 1000B Gateway & SBC configured. • The first word of the Format line must be "FORMAT", followed by the Index field name and then an equal "=" sign. After the equal sign, the names of the columns are listed.
Page 85: General Ini File Formatting Rules
Save the file with the ini file extension name (e.g., myconfiguration.ini). Load the file to the device. For loading the ini file to the device, see ''Loading an ini File to the Device'' on page 86. Version 6.8 Mediant 1000B Gateway & SBC...
Page 86: 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 87: Configuring Password Display In Ini File
$0$<plain text>: Password can be entered in plain text; useful for configuring a new password. When the ini file is loaded to the device and then later saved from the device to a PC, the password is displayed obscured (i.e., $1$<obscured password>). Version 6.8 Mediant 1000B Gateway & SBC...
Page 88: Ini Viewer And Editor Utility
Mediant 1000B Gateway & 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 89: General System Settings
Part III General System Settings...
Page 91: Configuring Ssl/ Tls Certificates
Private key - externally created and then uploaded to device  X.509 certificates - self-signed certificates or signed as a result of a certificate signing request (CSR)  Trusted root certificate authority (CA) store (for validating certificates) Version 6.8 Mediant 1000B Gateway & SBC...
Page 92 Mediant 1000B Gateway & SBC When the device establishes a TLS connection (handshake) with a SIP user agent (UA), the TLS Context is determined as follows:  Incoming calls: Proxy Set: If the incoming call is successfully classified to an IP Group based on Proxy Set (i.e., IP address of calling party) and the Proxy Set is configured for...
Page 93 TLS version supported by both peers.  [1] 1 = Only TLS 1.0 is used. Clients attempting to contact the device using any other version are rejected. Version 6.8 Mediant 1000B Gateway & SBC...
Page 94 Mediant 1000B Gateway & SBC Parameter Description Web: Ciphers Server Defines the supported cipher suite for the TLS server (in OpenSSL cipher CLI: ciphers-server list format). [TLSContexts_Serve For valid values, refer to URL rCipherString] http://www.openssl.org/docs/apps/ciphers.html. The default is "AES:RC4". For example, use "ALL" for all ciphers suites (e.g., for ARIA encryption for TLS).
Page 95: Assigning Csr-Based Certificates To Tls Contexts
Click the Create CSR button; a textual certificate signing request is displayed in the area below the button: Figure 10-2: Certificate Signing Request Group Copy the text and send it to your security provider (CA) to sign this request. Version 6.8 Mediant 1000B Gateway & SBC...
Page 96: Assigning Externally Created Private Keys To Tls Contexts
Mediant 1000B Gateway & SBC When the CA sends you a server certificate, save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file containing the"‘BEGIN CERTIFICATE" header, as shown in the example of a Base64-Encoded X.509 Certificate below:...
Page 97: Generating Private Keys For Tls Contexts
TLS Contexts page; the Context Certificates page appears. Scroll down to the Generate new private key and self-signed certificate group: Figure 10-5: Generate new private key and self-signed certificate Group Version 6.8 Mediant 1000B Gateway & SBC...
Page 98: Creating Self-Signed Certificates For Tls Contexts
Mediant 1000B Gateway & SBC From the 'Private Key Size' drop-down list, select the desired private key size (in bits) for RSA public-key encryption for newly self-signed generated keys: • • 1024 (default) • 2048 Click Generate Private Key; a message appears requesting you to confirm key generation.
Page 99: Importing Certificates And Certificate Chain Into Trusted Certificate Store
In the TLS Contexts table, select the required TLS Context index row, and then click the Context Trusted-Roots button, located at the bottom of the TLS Contexts page; the Trusted Certificates page appears. Version 6.8 Mediant 1000B Gateway & SBC...
Page 100: Configuring Mutual Tls Authentication
Mediant 1000B Gateway & SBC Click the Import button, and then select the certificate file to load. Figure 10-9: Importing Certificate into Trusted Certificates Store Click OK; the certificate is loaded to the device and listed in the Trusted Certificates store.
Page 101: Tls For Remote Device Management
HTTPSRootFileName ini file parameter. • You can enable the device to check whether a peer's certificate has been revoked by an OCSP server, per TLS Context (see 'Configuring TLS Certificate Contexts' on page 91). Version 6.8 Mediant 1000B Gateway & SBC...
Page 102: Configuring Tls Server Certificate Expiry Check
Mediant 1000B Gateway & SBC 10.1.8 Configuring TLS Server Certificate Expiry Check You can also configure the TLS Server Certificate Expiry Check feature, whereby the device periodically checks the validation date of the installed TLS server certificates. You also configure...
Page 103: Date And Time
"1". For USA New York, the UTC/GMT offset is -5 hours and therefore, the offset is a minus value and configured as "-5". To configure Daylight Saving Time (DST), see 'Configuring Daylight Saving Time' on page 105. Version 6.8 Mediant 1000B Gateway & SBC...
Page 104 Mediant 1000B Gateway & SBC You can also configure the device to authenticate and validate the NTP messages received from the NTP server. Authentication is done using an authentication key with the MD5 cryptographic hash algorithm. When this feature is enabled, the device ignores NTP messages received without authentication.
Page 105: Configuring Daylight Saving Time
If the current date falls within the DST period, verify that it has been successful applied to the device's current date and time. You can view the device's date and time in the Regional Settings page (see 'Configuring Date and Time Manually' on page 103). Version 6.8 Mediant 1000B Gateway & SBC...
Page 106 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 107: General Voip Configuration
Part IV General VoIP Configuration...
Page 109: Network
FULL GE1_2 00:1e:67:11:7c:28 100Mbps FULL DOWN Note: All the LAN ports (including those of the optional SWX Expansion module) have the same MAC address. This is the MAC address of the device itself. Version 6.8 Mediant 1000B Gateway & SBC...
Page 110 Mediant 1000B Gateway & SBC The following procedure describes how to configure the Ethernet ports in the Web interface. You can also configure these ports using the table ini file parameter, PhysicalPortsTable or CLI command, configure voip/physical-port.  To configure the physical Ethernet ports: Open the Physical Ports Settings page (Configuration tab >...
Page 111: Configuring Ethernet Port Groups
Note: The SWX LAN Expansion module is a customer-ordered item. For more information, contact your AudioCodes sales representative. You can assign Ethernet ports to IP network interfaces. This is done by first configuring an Ethernet Device with the required Ethernet Group containing the port or ports (see 'Configuring Underlying Ethernet Devices' on page 113).
Page 112 Mediant 1000B Gateway & SBC The following procedure describes how to configure Tx/Rx mode in the Web interface. You can also configure this using the table ini file parameter, EtherGroupTable or CLI command, configure voip/ether-group. Note: Before you can re-assign a port to a different Ethernet Group, you must first remove the port from its current Ethernet Group.
Page 113: Configuring Underlying Ethernet Devices
The Ethernet Device table lets you configure Ethernet Devices by defining a VLAN ID assigning it an arbitrary name for future reference to other configuration items, and associating it with an Ethernet Port Group. Version 6.8 Mediant 1000B Gateway & SBC...
Page 114 Mediant 1000B Gateway & SBC You can view configured Ethernet Devices that have been successfully applied to the device (saved to flash), in the Ethernet Device Status Table page. This page is accessed by clicking the Ethernet Device Status Table button, located at the bottom of the Ethernet Device Table page.
Page 115 Route table ('Device Name' field - see ''Configuring Static IP Routing'' on page 123). By default, the device automatically assigns a name using the following syntax: "dev <next available table row index>" (e.g., "dev 3"). Version 6.8 Mediant 1000B Gateway & SBC...
Page 116: Configuring Ip Network Interfaces
Mediant 1000B Gateway & SBC 12.4 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 117 Configure the IP network interface according to the parameters described in the table below. Click Submit. To view configured network interfaces that are currently active, click the IP Interface Status Table button. For more information, see ''Viewing Active IP Interfaces'' on page 642. Version 6.8 Mediant 1000B Gateway & SBC...
Page 118 Mediant 1000B Gateway & SBC Table 12-7: Interface Table Parameters Description Parameter Description Table parameters Index Table index row of the interface. CLI: network-if The range is 0 to 11. [InterfaceTable_Index] Web: Application Type Defines the applications allowed on the interface.
Page 119: Assigning Ntp Services To Application Types
The network interface types can be combined: • Example 1: ♦ One combined OAMP-Media-Control interface with an IPv4 address • Example 2: ♦ One OAMP interface with an IPv4 address ♦ One or more Control interfaces with IPv4 addresses Version 6.8 Mediant 1000B Gateway & SBC...
Page 120: Networking Configuration Examples
Mediant 1000B Gateway & SBC ♦ One or more Media interfaces with IPv4 interfaces • Example 3: ♦ One OAMP with an IPv4 address ♦ One combined Media-Control interface with IPv4 address ♦ One combined Media-Control interface with IPv6 address ...
Page 121: Voip Interface Per Application Type
IP Address Lengt n Type e Mode Gateway g Device Name OAMP IPv4 192.168.0.2 192.168.0.1 Mgmt Manual Media & IPv4 200.200.85.14 200.200.85. MediaCntrl1 Control Manual Media & IPv4 200.200.86.14 200.200.86. MediaCntrl2 Control Manual Version 6.8 Mediant 1000B Gateway & SBC...
Page 122 Mediant 1000B Gateway & SBC Prefix Inde Applicatio Interfac Default Underlyin Interface IP Address Lengt n Type e Mode Gateway g Device Name Media & IPv6 2000::1:200:200:86:1 V6CntrlMedia Control Manual Static Route table: A routing rule is required to allow remote management from a host in 176.85.49.0/24:...
Page 123: Voip Interfaces With Multiple Default Gateways
 To configure a static IP route: Open the Static Route Table page (Configuration tab > VoIP menu > Network > Static Route Table). Click Add; the following dialog box appears: Version 6.8 Mediant 1000B Gateway & SBC...
Page 124 Mediant 1000B Gateway & SBC Configure a static route according to the parameters described in the table below. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Note: You can delete only static routing rules that are inactive.
Page 125: Configuration Example Of Static Ip Routes
 The static route in the Static Route table is associated with the IP network interface in the Interface table, using the 'Device Name' and 'Underlying Device' parameters, respectively. Version 6.8 Mediant 1000B Gateway & SBC...
Page 126: Troubleshooting The Routing Table
Mediant 1000B Gateway & SBC  The static route's Gateway address in the Static Route table is in the same subnet as the IP address of the IP network interface in the Interface table. Figure 6: Example of using Static Route 12.5.2 Troubleshooting the Routing Table...
Page 127: Configuring Quality Of Service
  OAMP Control: Premium Control   Control Management: Bronze Varies according to the interface Depends on traffic type: type associated with NTP (see  Control: Premium control ''Assigning NTP Services to Version 6.8 Mediant 1000B Gateway & SBC...
Page 128 Mediant 1000B Gateway & SBC Application Traffic / Network Types Class-of-Service (Priority)  Application Types'' on page 119): Management: Bronze  OAMP  Control The following procedure describes how to configure DiffServ-to-VLAN priority mapping in the Web interface. You can also configure this using the table ini file parameter, DiffServToVlanPriority or CLI command configure voip >...
Page 129: Configuring Icmp Messages
To enable or disable sending and receipt of ICMP Redirect messages, use the 'Send and Receive ICMP Redirect Messages' parameter. To enable or disable the sending of ICMP Destination Unreachable messages, use the 'Send ICMP Unreachable Messages' parameter. Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 130: Dns
Mediant 1000B Gateway & SBC 12.8 You can use the device's embedded domain name server (DNS) or an external, third-party DNS to translate domain names into IP addresses. This is useful if domain names are used as the destination in call routing. The device supports the configuration of the following DNS types: ...
Page 131: Configuring The Internal Srv Table
The following procedure describes how to configure the Internal SRV table in the Web interface. You can also configure this using the table ini file parameter, SRV2IP or CLI command, configure voip > voip-network dns srv2ip. Version 6.8 Mediant 1000B Gateway & SBC...
Page 132 Mediant 1000B Gateway & SBC  To configure an SRV rule: Open the Internal SRV Table page (Configuration tab > VoIP menu > Network > DNS > Internal SRV Table). Click Add; the following dialog box appears: Figure 12-11: Internal SRV Table Page Configure an SRV rule according to the parameters described in the table below.
Page 133: Open Solution Network (Osn) Server
To enable / disable the internal switch's Ethernet port interfacing with OSN: Open the Application Settings page (Configuration tab > System menu > Application Settings). From the 'Block OSN Port' drop-down list, select Enable or Disable. Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 134: Configuring Nfs Settings
Mediant 1000B Gateway & SBC 12.10 Configuring NFS Settings Network File System (NFS) enables the device to access a remote server's shared files and directories and to handle them as if they're located locally. The device can use NFS to load cmp, ini, and auxiliary files through the Automatic Update mechanism (see Configuration using FTP or NFS).
Page 135: Network Address Translation Support
If configured, uses the single Static NAT IP address for all interfaces - see ''Configuring a Static NAT IP Address for All Interfaces'' on page 136. Version 6.8 Mediant 1000B Gateway & SBC...
Page 136: Configuring A Static Nat Ip Address For All Interfaces
Mediant 1000B Gateway & SBC If configured, uses the NAT Translation table which configures NAT per interface - see Configuring NAT Translation per IP Interface on page 137. If NAT is not configured by any of the above-mentioned methods, the device sends the packet according to its IP address configured in the Interface table.
Page 137: Configuring Nat Translation Per Ip Interface
[NATTranslation_SourceIPInterfaceName] Target IP Address Defines the global IP address. This address is set in CLI: TargetIPAddress the SIP Via and Contact headers as well as in the o= and c= SDP fields. [NATTranslation_TargetIPAddress] Version 6.8 Mediant 1000B Gateway & SBC...
Page 138: Remote Ua Behind Nat
Mediant 1000B Gateway & SBC Parameter Description Source Start Port Defines the optional starting port range (1-65536) of CLI: SourceStartPort the IP interface, used as matching criteria for this NAT [NATTranslation_SourceStartPort] rule. If not configured, the match is done on the entire port range.
Page 139: Media (Rtp/Rtcp/T.38)
NAT, the device sends the media packets to the public IP address:port obtained from the source address of the first media packet received from the UA. Otherwise, the packets are sent using the IP address:port obtained from the first Version 6.8 Mediant 1000B Gateway & SBC...
Page 140 Mediant 1000B Gateway & SBC received SIP message. Note also that if the SIP session is established (ACK) and the device (not the UA) sends the first packet, it sends it to the address obtained from the SIP message and only after the device receives the first packet from the UA, does it determine whether the UA is behind NAT.
Page 141: Robust Receipt Of Media Streams By Media Latching
12. Network 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 142: Multiple Routers Support
Mediant 1000B Gateway & SBC 12.13 Multiple Routers Support Multiple routers support is designed to assist the device when it operates in a multiple routers network. The device learns the network topology by responding to Internet Control Message Protocol (ICMP) redirections and caches them as routing rules (with expiration time).
Page 143: Security
Action Upon Match: Block The following procedure describes how to configure Firewall rules in the Web interface. You can also configure this using the table ini file parameter, AccessList or the CLI command, configure voip/access-list. Version 6.8 Mediant 1000B Gateway & SBC...
Page 144 Mediant 1000B Gateway & SBC  To configure a Firewall rule: Open the Firewall Settings page (Configuration tab > VoIP menu > Security > Firewall Settings). Click Add; the following dialog box appears: Figure 13-1: Firewall Settings Page - Add Record Configure a Firewall rule according to the parameters described in the table below.
Page 145 CLI: network-interface-name rule. This is applicable if you enabled the 'Use Specific [AccessList_Interface_x] Interface' field. The list displays interface names as defined in the Interface table in ''Configuring IP Network Interfaces'' on page 116. Version 6.8 Mediant 1000B Gateway & SBC...
Page 146 Mediant 1000B Gateway & SBC Parameter Description Packet Size Defines the maximum allowed packet size. CLI: packet-size The valid range is 0 to 65535. [AccessList_Packet_Size] Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment.
Page 147: Configuring General Security Settings
TLS all the way to the destination (over multiple hops), set the 'Enable SIPS' (EnableSIPS) parameter to Enable in the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters). Version 6.8 Mediant 1000B Gateway & SBC...
Page 148: Intrusion Detection System
Mediant 1000B Gateway & SBC 13.3 Intrusion Detection System The device's Intrusion Detection System (IDS) feature detects malicious attacks on the device and reacts accordingly. A remote host is considered malicious if it has reached or exceeded a user-defined threshold (counter) of specified malicious attacks.
Page 149: Enabling Ids
Open the IDS Policy Table page (Configuration tab > VoIP menu > Security > Intrusion Detection and Prevention > Policy Table); the table shows the pre- configured IDS policies: Figure 13-3: IDS Policy Table with Default Rules Version 6.8 Mediant 1000B Gateway & SBC...
Page 150 Mediant 1000B Gateway & SBC Click Add; the following dialog box appears: Figure 13-4: IDS Policy Table - Add Record Configure an IDS Policy name according to the parameters described in the table below. Click Submit. Table 13-3: IDS Policy Table Parameter Descriptions...
Page 151 [4] Dialog establish failure =  Classification failure (see ''Configuring Classification Rules'' on page 522)  Routing failure  Other local rejects (prior to SIP 180 response)  Remote rejects (prior to SIP 180 response) Version 6.8 Mediant 1000B Gateway & SBC...
Page 152 Mediant 1000B Gateway & SBC Parameter Description  [5] Abnormal flow =  Requests and responses without a matching transaction user (except ACK requests)  Requests and responses without a matching transaction (except ACK requests) Threshold Scope Defines the source of the attacker to consider in the device's CLI: threshold-scope detection count.
Page 153: Assigning Ids Policies
!3,4-7 means all indexes excluding 3, and excluding 4 through 7) Proxy Set ID Defines the Proxy Set(s) to which the IDS Policy is assigned. This CLI: proxy-set indicates the Proxy Sets from where the attacks are coming from. The Version 6.8 Mediant 1000B Gateway & SBC...
Page 154 Mediant 1000B Gateway & SBC Parameter Description [IDSMatch_ProxySet] following syntax is supported:  A comma-separated list of Proxy Set IDs (e.g., 1,3,4)  A hyphen "-" indicates a range of Proxy Sets (e.g., 3,4-7 means IDs 3, and 4 through 7) ...
Page 155: Viewing Ids Alarms
The device also sends IDS notifications and alarms in Syslog messages to a Syslog server. This only occurs if you have configured Syslog (see ''Enabling Syslog'' on page 681). An example of a Syslog message with IDS alarms and notifications is shown below: Version 6.8 Mediant 1000B Gateway & SBC...
Page 156 Mediant 1000B Gateway & SBC Figure 13-9: Syslog Message Example with IDS Alarms and Notifications The table below lists the Syslog text messages per malicious event: Table 13-6: Types of Malicious Events and Syslog Text String Type Description Syslog String...
Page 157: Media
When silence is detected, it stops sending packets in the channel. The following procedure describes how to enable silence suppression using the Web interface. Version 6.8 Mediant 1000B Gateway & SBC...
Page 158: Echo Cancellation
Mediant 1000B Gateway & SBC  To enable silence suppression using the Web interface: Open the Voice Settings page (Configuration tab > VoIP menu > Media > Voice Settings). Figure 14-2: Enabling Silence Suppression in Voice Settings Page Set the 'Silence Suppression' (EnableSilenceCompression) field to Enable.
Page 159: Fax And Modem Capabilities
To access the fax and modem parameters: Open the Fax/Modem/CID Settings page (Configuration tab > VoIP menu > Media > Fax/Modem/CID Settings). Figure 14-4: Fax/Modem/CID Settings Page Configure the parameters, as required. Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 160: Fax/Modem Operating Modes
Mediant 1000B Gateway & SBC 14.2.1 Fax/Modem Operating Modes The device supports two modes of operation:  Fax/modem negotiation that is not performed during the establishment of the call.  Voice-band data (VBD) mode for V.152 implementation (see ''V.152 Support'' on page 168): fax/modem capabilities are negotiated between the device and the remote endpoint at the establishment of the call.
Page 161 Relay (FaxTransportMode = 1). Configure the following optional parameters: • 'Fax Relay Redundancy Depth' (FaxRelayRedundancyDepth) • 'Fax Relay Enhanced Redundancy Depth' (FaxRelayEnhancedRedundancyDepth) • 'Fax Relay ECM Enable' (FaxRelayECMEnable) • 'Fax Relay Max Rate' (FaxRelayMaxRate) Version 6.8 Mediant 1000B Gateway & SBC...
Page 162: 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 163: Fax Fallback
To configure fax fallback mode:  In the SIP General Parameters page (Configuration tab > VoIP menu > SIP Definitions > General Parameters), set the 'Fax Signaling Method' parameter to Fax Fallback (IsFaxUsed = 3). Version 6.8 Mediant 1000B Gateway & SBC...
Page 164: Fax/Modem Bypass Mode
Mediant 1000B Gateway & SBC 14.2.2.4 Fax/Modem Bypass Mode In this proprietary mode, when fax or modem signals are detected, the channel automatically switches from the current voice coder to a high bit-rate coder, according to the 'Fax/Modem Bypass Coder Type' parameter (FaxModemBypassCoderType). The channel is also automatically reconfigured with the following fax / modem adaptations: ...
Page 165: 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 166: Fax / Modem Transparent With Events Mode
Mediant 1000B Gateway & SBC 14.2.2.6 Fax / Modem Transparent with Events Mode In this mode, fax and modem signals are transferred using the current voice coder with the following automatic adaptations:  Echo Canceller = on (or off for modems) ...
Page 167: Rfc 2833 Ans Report Upon Fax/Modem Detection
T38 Version 0 relay mode, i.e., fallback to T.38 (see ''Relay Mode for T.30 and V.34 Faxes'' on page 168) Note: The CNG detector is disabled in all the subsequent examples. To disable the CNG detector, set the 'CNG Detector Mode' parameter (CNGDetectorMode) to Disable. Version 6.8 Mediant 1000B Gateway & SBC...
Page 168: Bypass Mechanism For V.34 Fax Transmission
Mediant 1000B Gateway & SBC 14.2.3.1 Bypass Mechanism for V.34 Fax Transmission In this proprietary scenario, the device uses bypass (or NSE) mode to transmit V.34 faxes, enabling the full utilization of its speed.  To use bypass mode for T.30 and V.34 faxes: In the Fax/Modem/CID Settings page, do the following: Set the 'Fax Transport Mode' parameter to Bypass (FaxTransportMode = 2).
Page 169: Fax Transmission Behind Nat
T.38 only in the SDP, or T.38 and audio media in the SDP. This feature is configured using the T38FaxSessionImmediateStart parameter. The No-Op packets are enabled using the NoOpEnable and NoOpInterval parameters. Version 6.8 Mediant 1000B Gateway & SBC...
Page 170: Configuring Rtp/Rtcp Settings
Mediant 1000B Gateway & SBC 14.3 Configuring RTP/RTCP Settings This section describes configuration relating to Real-Time Transport Protocol (RTP) and RTP Control Protocol (RTCP). 14.3.1 Configuring the Dynamic Jitter Buffer Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate, voice quality is perceived as good.
Page 171: Comfort Noise Generation
Figure 14-6: Comfort Noise Parameter in RTP/RTCP Settings Page Set the 'Comfort Noise Generation Negotiation' parameter (ComfortNoiseNegotiation) to Enable. Click Submit. Note: This feature is applicable only to the Gateway application. Version 6.8 Mediant 1000B Gateway & SBC...
Page 172: Dual-Tone Multi-Frequency Signaling
Mediant 1000B Gateway & SBC 14.3.3 Dual-Tone Multi-Frequency Signaling This section describes the configuration of Dual-Tone Multi-Frequency (DTMF) signaling. 14.3.3.1 Configuring DTMF Transport Types The device supports various methods for transporting DTMF digits over the IP network to the remote endpoint. These methods and their configuration are configured in the DTMF &...
Page 173: Configuring Rfc 2833 Payload
'RFC 2833 RX Payload Type' (RFC2833RxPayloadType) - defines the Rx RFC 2833 DTMF relay dynamic payload type. • 'RFC 2198 Payload Type' (RFC2198PayloadType) - defines the RTP redundancy packet payload type according to RFC 2198. Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 174: Configuring Rtp Base Udp Port
Mediant 1000B Gateway & SBC 14.3.4 Configuring RTP Base UDP Port You can configure the range of local UDP ports for RTP, RTCP, and T.38 media streams. The range of possible UDP ports that can be used, depending on configuration, is 6,000 through to 64,000.
Page 175: Answering Machine Detector (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. The data needed for an accurate calibration should be recorded under the following guidelines: ...
Page 176 Mediant 1000B Gateway & SBC of a call answered by an answering machine is low, it would be advisable to configure the device to use a sensitivity level that is more sensitive to human than machine. Each suite can support up to 16 sensitivity levels (0 to 15), except for Parameter Suite 0, which supports up to 8 levels (0 to 7).
Page 177 Syslog messages. For information on Syslog fields for AMD, see Syslog Fields for Answering Machine Detection (AMD)' on page 680. For an example of a SIP call flow for AMD showing the SIP INFO messages, see 'SIP Call Flow Example of AMD' on page 178. Version 6.8 Mediant 1000B Gateway & SBC...
Page 178: Detecting Answering Machine Beeps
Mediant 1000B Gateway & SBC 14.4.1 Detecting Answering Machine Beeps The device supports the detection of the beep sound played by an answering machine to indicate the end of the answering machine's greeting message. This is useful in that the device can then notify, for example, a third-party, application server that it can now leave a voice message on the answering machine.
Page 179 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,INFO ,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway/v.6.80A.227.005 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. Version 6.8 Mediant 1000B Gateway & SBC...
Page 180: Configuring Amd
Mediant 1000B Gateway & SBC 14.4.3 Configuring AMD You can configure AMD for all calls using the global AMD parameters, or for specific calls using IP Profiles. The procedure below describes how to configure AMD for all calls. For configuring AMD for specific calls, use the AMD parameters in the IP Profile table (see 'Configuring IP Profiles' on page 302).
Page 181: Automatic Gain Control (Agc)
'AGC Disable Fast Adaptation' (AGCDisableFastAdaptation) - Enables the AGC Fast Adaptation mode. When using with application, 'Transcoding Mode' (TranscodingMode) parameter must be set to Force. This parameter can either be the global parameter or per IP Profile. Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 182: Configuring Analog Settings
Mediant 1000B Gateway & SBC 14.6 Configuring Analog Settings The Analog Settings page allows you to configure various analog parameters. For a detailed description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 715. This page also selects the type (USA or Europe) of FXS and/or FXO coefficient information.
Page 183: Configuring Ground- Or Loop-Start Signaling Per Analog Port
For each port, select one of the following from the Ground Start drop-down list: • [0] Disable = (Default) Port uses loop-start signaling. • [1] Enable = Port uses ground-start signaling. Click Submit, and then save ("burn") your settings to flash memory with a device reset. Version 6.8 Mediant 1000B Gateway & SBC...
Page 184: Configuring Dsp Templates
Mediant 1000B Gateway & SBC 14.8 Configuring DSP Templates The DSP Template determines the coders that can be used by the device and various other functionalities. For a list of DSP templates and the maximum number of channels supported by each coder, see DSP Templates. You can select a single DSP Template.
Page 185 MPM and PRI modules. For example, to achieve 120 channels (with conferencing), you need to use two MPM modules (installed in slots #5 and #6) and one PRI module providing two PRI spans (installed in Slot #1). Version 6.8 Mediant 1000B Gateway & SBC...
Page 186: Configuring Media (Srtp) Security
Mediant 1000B Gateway & SBC  Software Configuration: The device must be configured as follows: • Set the MediaChannels parameter to the maximum number of required IP media channels, regardless of the module from where the channels are obtained. Note:...
Page 187 Notes: • For a detailed description of the SRTP parameters, see ''SRTP Parameters'' on page 749. • When SRTP is used, the channel capacity may be reduced. Version 6.8 Mediant 1000B Gateway & SBC...
Page 188 Mediant 1000B Gateway & SBC  To enable and configure SRTP: Open the Media Security page (Configuration tab > VoIP menu > Media > Media Security). Set the 'Media Security' parameter to Enable to enable SRTP. Configure the other SRTP parameters as required.
Page 189: Services
IP Address Lease Time Option 1 Subnet Mask Option 3 Router Option 6 Domain Name Server Option 44 NetBIOS Name Server Option 46 NetBIOS Node Type Option 42 Network Time Protocol Server Option 2 Time Offset Version 6.8 Mediant 1000B Gateway & SBC...
Page 190 Mediant 1000B Gateway & SBC DHCP Option Code DHCP Option Name Option 66 TFTP Server Name Option 67 Boot file Name Option 120 SIP Server Once you have configured the DHCP server, you can configure the following:  DHCP Vendor Class Identifier names (DHCP Option 60) - see ''Configuring the Vendor Class Identifier'' on page ...
Page 191 Defines the IP address (IPv4) of the secondary DNS server CLI: dns-server-2 that the DHCP server assigns to the DHCP client. The value [DhcpServer_DNSServer2] is sent in DHCP Option 6 (Domain Name Server). Version 6.8 Mediant 1000B Gateway & SBC...
Page 192 Mediant 1000B Gateway & SBC Parameter Description Web: NetBIOS Name Server Defines the IP address (IPv4) of the NetBIOS WINS server CLI: netbios-server that is available to a Microsoft DHCP client. The value is sent [DhcpServer_NetbiosNameServer] in DHCP Option 44 (NetBIOS Name Server).
Page 193: 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 194: Configuring Additional Dhcp Options
Mediant 1000B Gateway & SBC Click Add; the following dialog box appears: Figure 15-2: DHCP Vendor Class Table - Add Record Dialog Box Configure a VCI for the DHCP server according to the parameters described in the table below. Click Submit.
Page 195  [1] IP address = IPv4 address.  [2] Hexadecimal = Hexadecimal-encoded string. For example, if you set the 'Value' parameter to "company.com", you need to set the 'Type' parameter to ASCII. Version 6.8 Mediant 1000B Gateway & SBC...
Page 196: Configuring Static Ip Addresses For Dhcp Clients
Mediant 1000B Gateway & SBC Parameter Description Web: Value Defines the value of the DHCP Option. For example, if you are CLI: value using Option 66, this parameter is used for specifying the TFTP [DhcpOption_Value] provisioning server (e.g., http://192.168.3.155:5000/provisioning/). The valid value is a string of up to 256 characters. By default, no value is defined.
Page 197: Viewing And Deleting Dhcp Clients
# show voip dhcp ip  To view DHCP clients according to MAC address: # show voip dhcp mac  To view DHCP clients that have been blacklisted from DHCP implementation (due to Version 6.8 Mediant 1000B Gateway & SBC...
Page 198 Mediant 1000B Gateway & SBC duplicated IP addresses in the network, where another device is using the same IP address as the one assigned to the client): # show voip dhcp black-list  To view or delete DHCP clients: Open the DHCP Servers page (Configuration tab > VoIP menu > Services > DHCP Severs).
Page 199: Radius Authentication
Set up a RADIUS server (third-party) to communicate with the device - see 'Setting Up a Third-Party RADIUS Server' on page  Configure the device as a RADIUS client for communication with the RADIUS server - see 'Configuring RADIUS Authentication' on page Version 6.8 Mediant 1000B Gateway & SBC...
Page 200: Setting Up A Third-Party Radius Server
 To set up a third-party RADIUS server (e.g., FreeRADIUS): Define the AudioCodes device as an authorized client of the RADIUS server, with the following: • Predefined shared secret (password used to secure communication between the device and the RADIUS server) •...
Page 201: Configuring Radius Authentication
If the RADIUS server response does not include the access level attribute: In the 'Default Access Level' field, enter the default access level that is applied to all users authenticated by the RADIUS server. Version 6.8 Mediant 1000B Gateway & SBC...
Page 202: Securing Radius Communication
Mediant 1000B Gateway & SBC Configure RADIUS timeout handling: From the 'Behavior upon Authentication Server Timeout' drop-down list, select the option if the RADIUS server does not respond within five seconds: ♦ Deny Access: device denies user login access. ♦...
Page 203: Ldap-Based Management And Sip Services
CN=\# Support Dept,OU=R&D Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=a bc,DC=com The device then assigns the user the access level configured for that group (in 'Configuring Access Level per Management Groups Attributes' on page 210). The Version 6.8 Mediant 1000B Gateway & SBC...
Page 204: Enabling The Ldap Service
Mediant 1000B Gateway & SBC location in the directory where you want to search for the user's member group(s) is configured using the following: • Search base object (distinguished name or DN, e.g., "ou=ABC,dc=corp,dc=abc,dc=com"), which defines the location in the directory from where the LDAP search begins, and is configured in 'Configuring LDAP DNs (Base Paths) per LDAP Server' on page 208.
Page 205: Configuring Ldap Servers
Configure an LDAP server according to the parameters described in the table below. Click Submit. LDAP Configuration Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [LdapConfiguration_In Version 6.8 Mediant 1000B Gateway & SBC...
Page 206 Mediant 1000B Gateway & SBC Parameter Description dex] Note: Each table row must be configured with a unique index. LDAP Server IP Defines the IP address of the LDAP server (in dotted-decimal notation, CLI: server-ip e.g., 192.10.1.255). [LdapConfiguration_Ld By default, no IP address is defined.
Page 207 (i.e., the 'Type' parameter is set to Management).  If this functionality is not used, the device assigns the user the configured default access level. For more information, see 'Configuring Access Level per Management Groups Attributes' on page 210. Version 6.8 Mediant 1000B Gateway & SBC...
Page 208: Configuring Ldap Dns (Base Paths) Per Ldap Server
Mediant 1000B Gateway & SBC Parameter Description Use SSL Enables the device to encrypt the username and password (for Control CLI: and Management related queries) using TLS when sending them to the [LdapConfiguration_us LDAP server. eTLS]  [0] No = (Default) Username and password are sent in clear-text format.
Page 209: Configuring The Ldap Search Filter Attribute
The search filter is applicable only to LDAP-based login authentication and authorization queries. • The search filter is a global setting that applies to all LDAP-based login authentication and authorization queries, across all configured LDAP servers. Version 6.8 Mediant 1000B Gateway & SBC...
Page 210: Configuring Access Level Per Management Groups Attributes
Mediant 1000B Gateway & SBC  To configure the LDAP search filter for management users: Open the LDAP Settings page (Configuration tab > VoIP menu > Services > LDAP > LDAP Settings). Figure 15-12: LDAP Settings Page - LDAP Search Filter Under LDAP Settings, in the 'LDAP Authentication Filter' parameter, enter the LDAP search filter attribute for searching the login username for user authentication.
Page 211 Note: Each table row must be configured with a unique index. GroupIndex] Level Defines the access level of the group(s). [MgmntLDAPGroups_L  [0] Monitor (Default) evel]  [1] Security Administrator  [2] Administrator Version 6.8 Mediant 1000B Gateway & SBC...
Page 212: Configuring Ldap Search Methods
Mediant 1000B Gateway & SBC Parameter Description Groups Defines the attribute names of the groups in the LDAP server. [MgmntLDAPGroups_ The valid value is a string of up to 256 characters. To define multiple Group] groups, separate each group name with a semicolon (;).
Page 213 However, for subsequent queries, the device does not use the partially cached result, but does a new query with the LDAP server again. Version 6.8 Mediant 1000B Gateway & SBC...
Page 214: Configuring Local Database For Management User Authentication
Mediant 1000B Gateway & SBC The following procedure describes how to configure the device's LDAP cache in the Web interface. For a full description of the cache parameters, see 'LDAP Parameters' on page 1003.  To configure the LDAP cache: Open the LDAP Settings page (Configuration tab >...
Page 215 Server Timeout' drop-down list, select one of the following: ♦ Deny Access: User is denied access to the management platform. ♦ Verify Access Locally (default): The device verifies the user's credentials in the Web Users table. Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 216: Ldap-Based Login Authentication Example
Mediant 1000B Gateway & SBC 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. The example applies to LDAP-based user login authentication and authorization (access level), and assumes that you are familiar with other aspects of LDAP configuration (e.g., LDAP server's address).
Page 217 (where the attribute's value equals the username): Figure 15-19: Username Found using sAMAccount Attribute Search Filter  Management Attribute: memberOf. The attribute contains the member groups of the user: Figure 15-20: User's memberOf Attribute Version 6.8 Mediant 1000B Gateway & SBC...
Page 218 Mediant 1000B Gateway & SBC  Management Group: mySecAdmin. The group to which the user belongs, as listed under the memberOf attribute: Figure 15-21: User's mySecAdmin Group in memberOf Management Attribute The configuration to match the above LDAP data structure schema is as follows: ...
Page 219: Active Directory-Based Routing For Microsoft Lync
PBX or IP PBX - users not yet migrated to Lync Server  Mobile - mobile number  Private - private telephone line for Lync users (in addition to the primary telephone line) Version 6.8 Mediant 1000B Gateway & SBC...
Page 220: Querying The Ad And Routing Priority
Mediant 1000B Gateway & SBC 15.3.11.1 Querying the AD and Routing Priority The device queries the AD using the initial destination number (i.e., called number). The query can return up to four user phone numbers, each pertaining to one of the IP domains (i.e., private number, Lync number, PBX / IP PBX number, and mobile number).
Page 221 Lync Server, if the PBX / IP PBX system is unavailable or has failed, the device uses the AD query result for the user’s mobile phone number, routing the call through the PSTN to the mobile destination. Version 6.8 Mediant 1000B Gateway & SBC...
Page 222 Mediant 1000B Gateway & SBC The flowchart below summarizes the device's process for querying the AD and routing the call based on the query results: Figure 15-26: LDAP Query Flowchart Note: If you are using the device's local LDAP cache, see 'Configuring the Device's LDAP Cache' on page for the LDAP query process.
Page 223: Configuring Ad-Based Routing Rules
Lync clients, and mobile), using the LDAP keywords (case-sensitive) in the Destination Username Prefix field: ♦ PRIVATE: Private number ♦ OCS: Lync client number ♦ PBX: PBX / IP PBX number ♦ MOBILE: Mobile number Version 6.8 Mediant 1000B Gateway & SBC...
Page 224 Mediant 1000B Gateway & SBC ♦ LDAP_ERR: LDAP query failure Configure a routing rule for routing the initial call (LDAP query) to the LDAP server, by setting the 'Destination Type' field to LDAP for denoting the IP address of the LDAP server.
Page 225: Querying The Ad For Calling Name
The Calling Name Manipulation Table for Tel-to-IP Calls table uses the numbers before manipulation, as inputs. • The LDAP query uses the calling number after source number manipulation, as the search key value. Version 6.8 Mediant 1000B Gateway & SBC...
Page 226: Least Cost Routing
Mediant 1000B Gateway & SBC 15.4 Least Cost Routing This section provides a description of the device's least cost routing (LCR) feature and how to configure it. 15.4.1 Overview The LCR feature enables the device to choose the outbound IP destination routing rule based on lowest call cost.
Page 227 Index 3 - no Cost Group is assigned, but as the Default Cost parameter is set to Min, it is selected as the cheapest route • Index 4 - Cost Group "B" is only second-matched rule (Index 1 is the first) Version 6.8 Mediant 1000B Gateway & SBC...
Page 228: Configuring Lcr
Mediant 1000B Gateway & SBC  Example 3: This example shows how the cost of a call is calculated if the call spans over multiple time bands: Assume a Cost Group, "CG Local" is configured with two time bands, as shown below:...
Page 229 (default.)  [1] Highest Cost = If the device locates other matching LCR routing rules, this routing rule is considered as the Version 6.8 Mediant 1000B Gateway & SBC...
Page 230: Configuring Cost Groups
Mediant 1000B Gateway & SBC Parameter Description highest cost route and therefore, is not used or used only if the other cheaper routes are unavailable. Note: If more than one valid routing rule without a defined Cost Group exists, the device selects the first-matched rule.
Page 231: Configuring Time Bands For Cost Groups
Click Submit, and then save ("burn") your settings to flash memory. Table 15-9: Time Band Table Description Parameter Description Index Defines an index number for the new table record. CLI: timeband-index Note: Each table row must be configured with a unique Version 6.8 Mediant 1000B Gateway & SBC...
Page 232: Assigning Cost Groups To Routing Rules
Mediant 1000B Gateway & SBC Parameter Description [CostGroupTimebands_TimebandIndex] index. Start Time Defines the day and time of day from when this time CLI: start-time band is applicable. The format is DDD:hh:mm, where: [CostGroupTimebands_StartTime]  DDD is the day of the week, represented by the first three letters of the day in upper case (i.e., SUN,...
Page 233: Configuring Call Setup Rules
If an Exit Action Type is not configured and the device has run all the rules in the Set ID, the default Action Value of the Set ID is "True" (i.e., use the current Version 6.8 Mediant 1000B Gateway & SBC...
Page 234 Mediant 1000B Gateway & SBC routing rule).  Rule's condition is not met: The device runs the next rule in the Set ID. When the device reaches the end of the Set ID and no Exit was performed, the Set ID ends with a "True"...
Page 235 (attribute "mobile" exists in AD)  param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called number is the same as the number in the attribute "msRTCSIP-PrivateLine")  ldap.found !exists (LDAP record not found)  ldap.err exists (LDAP error exists) Version 6.8 Mediant 1000B Gateway & SBC...
Page 236 Mediant 1000B Gateway & SBC Parameter Description Action Subject Defines the element (header, parameter, or body) upon CLI: action-subject which you want to perform the action. [CallSetupRules_ActionSubject] The valid value is a string of up to 100 characters (case- insensitive).
Page 237: Call Setup Rule Examples
'Action Type': Modify ♦ 'Action Value': ldap.attr. displayName • Routing table configuration: A single routing rule is assigned the Call Setup Rule Set ID. ♦ Index 1:  'Call Setup Rules Set Id': 2 Version 6.8 Mediant 1000B Gateway & SBC...
Page 238 Mediant 1000B Gateway & SBC  Example 3: This example configures the device to route the incoming call according to whether or not the source number of the incoming call also exists in the AD server. The device queries the AD server for the attribute record, "telephoneNumber" whose value is the same as the received source number (e.g., telephoneNumber=4064").
Page 239: 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 240: 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 241  Report the change in the measured metrics to AudioCodes' Session Experience Manager (SEM) server. The SEM displays this call quality status for the associated SEM link (IP Group, Media Realm, or Remote Media Subnet). For configuring the SEM server's address, see ''Configuring SEM Server'' on page 239.
Page 242 Mediant 1000B Gateway & SBC Configure a QoE Profile according to the parameters described in the table below. Click Submit. Table 16-1: Quality of Experience Profile Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
Page 243 SEM indicating this change. Note: If the monitored parameter crosses two thresholds at once (e.g., from Green to Red), the device ignores the hysteresis value and reports the call state change to the SEM. Version 6.8 Mediant 1000B Gateway & SBC...
Page 244: Configuring Bandwidth Profiles
Mediant 1000B Gateway & SBC Parameter Description Yellow Red Threshold Defines the parameter threshold values between CLI: yellow-red-threshold Yellow (medium quality) and Red (poor quality) states. [QOEColorRules_YellowRedThreshold] The valid threshold values are as follows:  MOS values are in multiples of 10. For example, to denote a MOS of 3.2, the value 32 (i.e., 3.2*10)
Page 245 The valid value is a string of up to 20 characters. Egress Audio Bandwidth Defines the outgoing audio traffic threshold (in Kbps). CLI: egress-audio-bandwidth [BWProfile_EgressAudioBandwidth] Ingress Audio Bandwidth Defines the incoming audio traffic threshold (in Kbps). CLI: ingress-audio-bandwidth [BWProfile_IngressAudioBandwidth] Version 6.8 Mediant 1000B Gateway & SBC...
Page 246 Mediant 1000B Gateway & SBC Parameter Description Egress Video Bandwidth Defines the outgoing video traffic threshold (in Kbps). CLI: egress-video-bandwidth [BWProfile_EgressVideoBandwidth] Ingress Video Bandwidth Defines the incoming video traffic threshold (in Kbps). CLI: ingress-video-bandwidth [BWProfile_IngressVideoBandwidth] Total Egress Bandwidth Defines the total (video and audio) outgoing bandwidth CLI: total-egress-bandwidth threshold (in Kbps).
Page 247: Configuring Media Enhancement Profiles
 Media Enhancement Profile table: Table ini file parameter, MediaEnhancementProfile or CLI command, configure voip/qoe media-enhancement  Media Enhancement Rules table: Table ini file parameter, MediaEnhancementRules or CLI command, configure voip/qoe media-enhancement-rules Version 6.8 Mediant 1000B Gateway & SBC...
Page 248 Mediant 1000B Gateway & SBC  To configure a Media Enhancement Profile: Open the Media Enhancement Profile page (Configuration tab > VoIP menu > Quality of Experience > Media Enhancement Profile). Click Add; the following dialog box appears: Figure 16-5: Media Enhancement Profile Table - Add Record Configure a Media Enhancement Profile according to the parameters described in the table below.
Page 249 Defines an alternative IP Profile ID for the IP Group that CLI: value is associated with this rule, if this rule is applied. This [MediaEnhancementRules_ActionValue] parameter is applicable only if the 'Rule Action' parameter is set to Alternative IP Profile. Version 6.8 Mediant 1000B Gateway & SBC...
Page 250 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 251: Control Network
If you modify a Media Realm currently being used by a call, the device does not perform Quality of Experience for the call. If you delete the Media Realm during the call, the device maintains the call until the call parties end the call. Version 6.8 Mediant 1000B Gateway & SBC...
Page 252 Mediant 1000B Gateway & SBC The following procedure describes how to configure Media Realms in the Web interface. You can also configure Media Realms using the table ini file parameter, CpMediaRealm or CLI command, configure voip/voip-network realm.  To configure a Media Realm: Open the Media Realm Table page (Configuration tab >...
Page 253 QoE Profiles, see ''Configuring Quality of Experience [CpMediaRealm_QoeProfile] Profiles'' on page 240. BW Profile Assigns a Bandwidth Profile to the Media Realm. For CLI: bw-profile configuring Bandwidth Profiles, see ''Configuring Bandwidth [CpMediaRealm_BWProfile] Profiles'' on page 244. Version 6.8 Mediant 1000B Gateway & SBC...
Page 254: Configuring Remote Media Subnets
Mediant 1000B Gateway & SBC 17.2 Configuring Remote Media Subnets Remote Media Subnets define destination subnets for media (RTP/SRTP) traffic on a specific Media Realm. Each Remote Media Subnet can be assigned different call quality (Quality of Experience Profile) and bandwidth utilization (Bandwidth Profile) profiles. These profiles are configured in ''Configuring Quality of Experience Profiles'' on page ''Configuring Bandwidth Profiles'' on page 244, respectively.
Page 255 [RemoteMediaSubnet_DstIPAddress] QOE Profile Name Assigns a Quality of Experience Profile to the CLI: qoe-profile Remote Media Subnet. [RemoteMediaSubnet_QOEProfileName] BW Profile Name Assigns a Bandwidth Profile to the Remote CLI: bw-profile Media Subnet. [RemoteMediaSubnet_BWProfileName] Version 6.8 Mediant 1000B Gateway & SBC...
Page 256: Configuring Srds
Mediant 1000B Gateway & SBC 17.3 Configuring SRDs The SRD table lets you configure up to 32 signaling routing domains (SRD). An SRD represents a logical VoIP network. Each logical or physical connection requires an SRD. For example, if the device interfaces with both the LAN and WAN, you would need to configure an SRD for each one.
Page 257 SRD, calls cannot be established if the following scenario exists: One of the endpoints is defined as a foreign user (for example, “follow me service”) and one endpoint is located on the WAN and the other on the LAN. Version 6.8 Mediant 1000B Gateway & SBC...
Page 258: Configuring Sip Interfaces
Mediant 1000B Gateway & SBC Parameter Description The reason for this is that in Media Anchoring, the device does not interfere in the SIP signaling such as manipulation of IP addresses, which is necessary for calls between LAN and WAN.
Page 259 This port must be outside of the RTP port range.  Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). Version 6.8 Mediant 1000B Gateway & SBC...
Page 260 Mediant 1000B Gateway & SBC Parameter Description TCP Port Defines the listening TCP port. CLI: tcp-port The valid range is 1 to 65534. The default is 5060. [SIPInterface_TCPPort] Notes:  This port must be outside of the RTP port range.
Page 261 If both the SIP Interface and IP Group associated with the incoming call are assigned a Message Manipulation Set, the one assigned to the SIP Interface is applied first.  This parameter is applicable only to SBC calls. Version 6.8 Mediant 1000B Gateway & SBC...
Page 262: Configuring Ip Groups
Mediant 1000B Gateway & SBC 17.5 Configuring IP Groups The IP Group table lets you configure up to 100 IP Groups. An IP Group represents a SIP entity in the network with which the device communicates. This can be a server (e.g., IP PBX or ITSP) or it can be a group of users (e.g., LAN IP phones).
Page 263 [1] User = Represents a group of users such as IP phones and softphones where their location is dynamically obtained by the device when REGISTER requests and responses traverse (or are terminated) by the device. These users are considered remote Version 6.8 Mediant 1000B Gateway & SBC...
Page 264 Mediant 1000B Gateway & SBC Parameter Description (far-end) users. Typically, this IP Group is configured with a Serving IP Group that represents an IP-PBX, Application or Proxy server that serves this User-type IP Group. Each SIP request sent by a user of this IP Group is proxied to the Serving IP Group.
Page 265 Defines the host name (string) that the device uses in the SIP CLI: local-host-name message's Via and Contact headers. This is typically used to define [IPGroup_ContactName] an FQDN as the host name. The device uses this string for Via and Version 6.8 Mediant 1000B Gateway & SBC...
Page 266 Mediant 1000B Gateway & SBC Parameter Description Contact headers in outgoing INVITE messages sent to a specific IP Group, and the Contact header in SIP 18x and 200 OK responses for incoming INVITE messages received from a specific IP Group. The Inbound IP Routing table can be used to identify the source IP Group from where the INVITE message was received.
Page 267 When this parameter is set to [2], the XferPrefix parameter can be used to define different routing rules for redirected calls.  This parameter is ignored if the parameter AlwaysSendToProxy is set to 1. Version 6.8 Mediant 1000B Gateway & SBC...
Page 268 Mediant 1000B Gateway & SBC Parameter Description Enable Survivability Defines how the device handles registration messages and whether CLI: enable-survivability Survivability mode is enabled for User-type IP Groups. [IPGroup_EnableSurvivability]  [0] Disable (default).  [1] Enable if Necessary = Survivability mode is enabled only if the Serving IP Group is unavailable.
Page 269 [1] SBC Initiates Registration = Used when the device serves as a client (e.g., with an IP PBX). This functions only with the User Info file.  [2] Registrations not Needed = The device adds users to its database in active state. Version 6.8 Mediant 1000B Gateway & SBC...
Page 270 Mediant 1000B Gateway & SBC Parameter Description Authentication Mode Defines the authentication mode. CLI: authentication-mode  [0] User Authenticates = (Default) The device does not handle the [IPGroup_AuthenticationMode authentication, but simply passes the authentication messages between the SIP user agents.
Page 271 [4] P-Asserted - Second Header  [5] P-Preferred  [6] Route  [7] Diversion  [8] P-Associated-URI  [9] P-Called-Party-ID  [10] Contact  [11] Referred-by Notes:  The parameter is applicable only when classification is done Version 6.8 Mediant 1000B Gateway & SBC...
Page 272: Configuring Proxy Sets
Mediant 1000B Gateway & SBC Parameter Description according to the Classification table.  If the configured SIP header does not exist in the incoming INVITE message, the classification of the message to a source IP Group fails.  If the device receives an INVITE as a result of a REFER request or a 3xx response, the incoming INVITE is routed according to the Request-URI.
Page 273 Proxy Sets Table). Figure 17-6: Proxy Sets Table Page Configure a Proxy Set according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 1000B Gateway & SBC...
Page 274 Mediant 1000B Gateway & SBC Table 17-6: Proxy Sets Table Parameter Description Parameter Description Web: Proxy Set ID Defines an index number for the new table record. EMS: Index CLI: configure voip > voip- network proxy-set [ProxySet_Index] Proxy Address Defines the address of the Proxy server. Up to 10 addresses can CLI: voip-network proxy-ip >...
Page 275 Note: The SIP 200 response code is not supported by this feature. Web: Proxy Load Balancing Enables the Proxy Load Balancing mechanism per Proxy Set. Method  [0] Disable = Load Balancing is disabled (default) EMS: Load Balancing Method Version 6.8 Mediant 1000B Gateway & SBC...
Page 276 Mediant 1000B Gateway & SBC Parameter Description  CLI: voip-network proxy-set > [1] Round Robin = A list of all possible Proxy IP addresses is proxy-load-balancing-method compiled. This list includes all IP addresses per Proxy Set [ProxySet_ProxyLoadBalancin after necessary DNS resolutions (including NAPTR and SRV, gMethod] if configured).
Page 277 UDP to communicate with the proxy and no TLS Context is used. For more information about how certificates are associated with calls and for configuring TLS Contexts, see Configuring SSL/TLS Certificates on page 91. Version 6.8 Mediant 1000B Gateway & SBC...
Page 278 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 279: Sip Definitions
> sip-definition account.  To configure an Account: Open the Account Table page (Configuration tab > VoIP menu > SIP Definitions > Account Table). Click Add; the following dialog box appears: Version 6.8 Mediant 1000B Gateway & SBC...
Page 280 Mediant 1000B Gateway & SBC Configure an account according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Once you have configured Accounts, you can register or un-register them, as described below: ...
Page 281 If registration fails, the user part in the INVITE Contact header contains the source party number. Application Type Defines the application type: CLI: application-type  [0] GW/IP2IP = (Default) Gateway and IP-to-IP application. [Account_ApplicationType]  [2] SBC = SBC application. Version 6.8 Mediant 1000B Gateway & SBC...
Page 282: Regular Registration Mode
Mediant 1000B Gateway & SBC 18.2.1 Regular Registration Mode When you configure the registration mode in the Account table to Regular, the device sends REGISTER requests to the Serving IP Group. The host name (in the SIP From/To headers) and contact user (user in From/To and Contact headers) are taken from the configured Account table upon successful registration.
Page 283: Configuring Proxy And Registration Parameters
For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 715. Note: To view the registration status of endpoints with a SIP Registrar/Proxy server, see Viewing Endpoint Registration Status on page 649. Version 6.8 Mediant 1000B Gateway & SBC...
Page 284 Mediant 1000B Gateway & SBC  To configure the Proxy and registration parameters: Open the Proxy & Registration page (Configuration tab > VoIP menu > SIP Definitions > Proxy & Registration). Configure the parameters as required. Click Submit.  To register or un-register the device to a Proxy/Registrar: ...
Page 285: Sip Message Authentication Example
• The password from the ini file is "AudioCodes". • The equation to be evaluated is "122:audiocodes.com:AudioCodes". According to the RFC, this part is called A1. • The MD5 algorithm is run on this equation and stored for future usage.
Page 286: Configuring Sip Message Manipulation
Mediant 1000B Gateway & SBC • Using SIP protocol "sip". • Proxy IP from ini file is "10.2.2.222". • The equation to be evaluated is "REGISTER:sip:10.2.2.222". • The MD5 algorithm is run on this equation and stored for future usage.
Page 287 Configurable identity hiding (information related to identity of subscribers, for example, P-Asserted-Identity, Referred-By, Identity and Identity-Info)  Apply conditions per rule - the condition can be on parts of the message or call’s parameters  Multiple manipulation rules on the same SIP message Version 6.8 Mediant 1000B Gateway & SBC...
Page 288 Mediant 1000B Gateway & SBC The figure below illustrates a SIP message manipulation example: Figure 18-1: SIP Header Manipulation Example Notes: • For a detailed description of the syntax used for configuring Message Manipulation rules, refer to the SIP Message Manipulations Quick Reference Guide.
Page 289 Index 3: If the user part of the From header equals "unknown", then it is changed according to the srcIPGroup call’s parameter.  Index 4: Removes the Priority header from an incoming INVITE message. Version 6.8 Mediant 1000B Gateway & SBC...
Page 290 Mediant 1000B Gateway & SBC Table 18-2: Message Manipulations Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [MessageManipulations_Index] Note: Each rule must be configured with a unique index. Manipulation Name Defines an arbitrary name to easily identify the Message CLI: manipulation-name Manipulation rule.
Page 291: Configuring Sip Message Policy Rules
To apply SIP Message Policy rules, you need to assign them to SIP Interfaces associated with the relevant IP Groups (see ''Configuring SIP Interfaces'' on page 258). Each Message Policy rule can be configured with the following:  Maximum message length  Maximum header length Version 6.8 Mediant 1000B Gateway & SBC...
Page 292 Mediant 1000B Gateway & SBC  Maximum message body length  Maximum number of headers  Maximum number of bodies  Option to send 400 "Bad Request" response if message request is rejected  Blacklist and whitelist for defined methods (e.g., INVITE) ...
Page 293 'Body List' parameter (above). [MessagePolicy_BodyListType]  [0] Policy Blacklist =The specified SIP body is rejected.  [1] Policy Whitelist = (Default) Only the specified SIP body is allowed; the others are rejected. Version 6.8 Mediant 1000B Gateway & SBC...
Page 294 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 295: Coders And Profiles
You can also configure this table using the table ini file parameter, CodersGroup0 or CLI command, configure voip > coders-and-profiles coders-group.  To configure coders: Open the Coders page (Configuration tab > VoIP menu > Coders and Profiles > Coders). Figure 19-1: Coders Table Page Version 6.8 Mediant 1000B Gateway & SBC...
Page 296 Mediant 1000B Gateway & SBC Configure coders according to the parameters described in the table below. Click Submit, and then reset the device with a save ("burn") to flash memory. Table 19-1: Coders Table Parameter Descriptions Parameter Description Coder Name Defines the coder.
Page 297 [iLBC] 100, 120 127);  [1] Enable Default 65 30 (default), 60, 90, 120  [0] Disable Transparent 10, 20 (default), 40, 60, Dynamic (0- [Transparent] 80, 100, 120 127)  [1] Enable Version 6.8 Mediant 1000B Gateway & SBC...
Page 298: Configuring Coder Groups
Mediant 1000B Gateway & SBC Coder Name Packetization Time Rate (kbps) Payload Silence (msec) Type Suppression T.38 [t38fax] T.38 Over RTP Dynamic (90 - 127); Default 106 19.2 Configuring Coder Groups The Coder Group Settings table lets you configure up to 10 Coder Groups. A Coder Group is a set of configured coders (coder type, packetization time, rate, payload type, and silence suppression).
Page 299: Configuring Tel Profile
 To configure a Tel Profile: Open the Tel Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > Tel Profile Settings). Click Add; the following dialog box appears: Version 6.8 Mediant 1000B Gateway & SBC...
Page 300 Mediant 1000B Gateway & SBC Configure a Tel Profile according to the parameters described in the table below. For a description of each parameter, refer to the corresponding "global" parameter. Click Submit, and then save ("burn") your settings to flash memory.
Page 301 Web: DTMF Volume DTMFVolume CLI: dtmf-volume [TelProfile_DtmfVolume] Web: Input Gain InputGain CLI: input-gain [TelProfile_InputGain] Web: Voice Volume VoiceVolume CLI: voice-volume [TelProfile_VoiceVolume] Web: Echo Canceler EnableEchoCanceller CLI: echo-canceller [TelProfile_EnableEC] Web: Enable AGC EnableAGC CLI: enable-agc [TelProfile_EnableAGC] Version 6.8 Mediant 1000B Gateway & SBC...
Page 302: Configuring Ip Profiles
Mediant 1000B Gateway & SBC Tel Profile Parameter Global Parameter Web: EC NLP Mode ECNLPMode CLI: echo-canceller-nlp-mode [TelProfile_ECNlpMode] Analog Web: Enable Polarity Reversal EnableReversalPolarity CLI: polarity-rvrsl [TelProfile_EnableReversePolarity] Web: Enable Current Disconnect EnableCurrentDisconnect CLI: current-disconnect [TelProfile_EnableCurrentDisconnect] Web: MWI Analog Lamp MWIAnalogLamp...
Page 303 Open the IP Profile Settings page (Configuration tab > VoIP menu > Coders and Profiles > IP Profile Settings). Click Add; the following dialog box appears: Configure an IP Profile according to the parameters described in the table below. Version 6.8 Mediant 1000B Gateway & SBC...
Page 304 Mediant 1000B Gateway & SBC Click Submit, and then save ("burn") your settings to flash memory. Table 19-5: IP Profile Settings Table Parameter Descriptions Parameter Description Common Web: Index Defines an index number for the new table record. [IpProfile_Index] Web: Profile Name Defines an arbitrary name to easily identify the IP Profile.
Page 305  During a call, if the source IP address (from where the RTP packets are received) is changed without notifying the device, the device filters these RTP packets. To overcome this, set the Version 6.8 Mediant 1000B Gateway & SBC...
Page 306 Mediant 1000B Gateway & SBC Parameter Description DisconnectOnBrokenConnection parameter to 0; the device doesn't detect RTP packets arriving from the original source IP address and switches (after 300 msec) to the RTP packets arriving from the new source IP address.
Page 307 Defines the maximum delay and length (in msec) of the Jitter CLI: jitter-buffer-max-delay Buffer. [IpProfile_JitterBufMaxDelay] The valid range is 150 to 2,000. The default is 250. Web: Coders Group ID Defines coders supported by this SIP entity, by assigning a Coders Version 6.8 Mediant 1000B Gateway & SBC...
Page 308 Mediant 1000B Gateway & SBC Parameter Description CLI: coders-group-id Group. [IpProfile_CodersGroupID] The value, Default Coders Group represents the coders configured in the Coders table (see Configuring Coders on page 295). All other optional values (e.g., Coders Group 1), represent the coders defined for the specific Coder Group configured in the Coder Group Settings table (see Configuring Coder Groups on page 298).
Page 309 G.711 -Law). The parameters defining payload type for the 'old' Bypass mode FaxBypassPayloadType and ModemBypassPayloadType are not used with NSE Bypass. The bypass packet interval is configured according to the FaxModemBypassBasicRtpPacketInterval parameter. The SDP contains the following line: Version 6.8 Mediant 1000B Gateway & SBC...
Page 310 Mediant 1000B Gateway & SBC Parameter Description 'a=rtpmap:100 X-NSE/8000'. Notes:  When enabled, the following conditions must also be met:  The Cisco gateway must include the following definition: 'modem passthrough nse payload-type 100 codec g711alaw'.  Set the Modem transport type to Bypass mode (VxxModemTransportType is set to 2) for all modems.
Page 311 INVITE message, to the redirect number in the outgoing Q.931 CLI: copy-dst-to-redirect- Setup message, for IP-to-Tel calls. Thus, even if there is no SIP number Diversion or History header in the incoming INVITE message, the Version 6.8 Mediant 1000B Gateway & SBC...
Page 312 Mediant 1000B Gateway & SBC Parameter Description [IpProfile_CopyDest2RedirectN outgoing Q.931 Setup message will contain a redirect number. umber]  [0] Disable (default).  [1] After Manipulation = Copies the called number after manipulation. The device first performs IP-to-Tel destination phone number manipulation, and only then copies the manipulated called number to the redirect number sent in the Q.931 Setup message to the Tel.
Page 313 Enables the device to declare the RFC 2833 'telephony-event' CLI: rx-dtmf-option parameter in the SDP. [IpProfile_RxDTMFOption]  [0] Not Supported  [3] Supported (default) The device is always receptive to RFC 2833 DTMF relay packets. Version 6.8 Mediant 1000B Gateway & SBC...
Page 314 Mediant 1000B Gateway & SBC Parameter Description Thus, it is always correct to include the 'telephony-event' parameter by default in the SDP. However, some devices use the absence of the 'telephony-event' in the SDP to decide to send DTMF digits in- band using G.711 coder.
Page 315 All QSIG messages are sent as raw data in corresponding SIP messages using a dedicated message body. Notes:  QSIG tunneling must be enabled on originating and terminating devices.  To enable this function, set the ISDNDuplicateQ931BuffMode Version 6.8 Mediant 1000B Gateway & SBC...
Page 316 Mediant 1000B Gateway & SBC Parameter Description parameter to 128 (i.e., duplicate all messages).  To define the format of encapsulated QSIG messages, use the QSIGTunnelingMode parameter.  Tunneling according to ECMA-355 is applicable to all ISDN variants (in addition to the QSIG protocol).
Page 317 To configure Allowed Video Coders Groups, see Configuring Allowed Video Coder Groups on page 522. Web: Allowed Coders Mode Defines the mode of the Allowed Coders feature for this SIP entity. Version 6.8 Mediant 1000B Gateway & SBC...
Page 318 Mediant 1000B Gateway & SBC Parameter Description  CLI: sbc-allowed-coders-mode [0] Restriction = In the incoming SDP offer, the device uses only [IpProfile_SBCAllowedCodersM Allowed coders; the rest are removed from the SDP offer (i.e., ode] only coders common between those in the received SDP offer and the Allowed coders are used).
Page 319 Diversion header depends on the settings of the SBCDiversionMode parameter. Web: Fax Coders Group ID Assigns a Coders Group ID to define the supported fax coders for Version 6.8 Mediant 1000B Gateway & SBC...
Page 320 Mediant 1000B Gateway & SBC Parameter Description CLI: sbc-fax-coders-group-id fax negotiation for this SIP entity. For configuring Coder Groups, [IpProfile_SBCFaxCodersGroup see Configuring Coder Groups on page 298. Note: The parameter is applicable only if you set the IpProfile_SBCFaxBehavior parameter to a value other than [0].
Page 321 CLI: sbc-rmt-refer-behavior entity. [IpProfile_SBCRemoteReferBeh  [0] Regular = (Default) Refer-To header is unchanged and the avior] device forwards the REFER as is.  [1] Database URL = Changes the Refer-To header so that the Version 6.8 Mediant 1000B Gateway & SBC...
Page 322 Mediant 1000B Gateway & SBC Parameter Description re-routed INVITE is sent through the SBC: Before forwarding the REFER request, the device changes the host part to the device's IP address and adds a special prefix ("T~&R_") to the Contact user part.
Page 323 [0] Not Supported = (Default) UA does not support receipt of [IpProfile_SBCRemoteSupports 18x messages with delayed RTP. For the device's handling of RFC3960] this remote UA support, see Interworking SIP Early Media on page 504. Version 6.8 Mediant 1000B Gateway & SBC...
Page 324 Mediant 1000B Gateway & SBC Parameter Description  [1] Supported = UA is capable of receiving 18x messages with delayed RTP. Web: Remote Can Play Defines whether the destination UA can play a local ringback tone. Ringback  [0] No = UA does not support local ringback tone. The device CLI: sbc-rmt-can-play-ringback sends 18x with delayed SDP to the UA.
Page 325 [0] Transparent (default) = Forward as is. [IpProfile_SBCUseSilenceSupp]  [1] Add = Enable silence suppression for each relevant coder listed in the SDP.  [2] Remove = Disable silence suppression for each relevant Version 6.8 Mediant 1000B Gateway & SBC...
Page 326 Mediant 1000B Gateway & SBC Parameter Description coder listed in the SDP. Web: Play RBT To Transferee Enables the device to play a ringback tone to the transferred party CLI: sbc-play-rbt-to-xferee (transferee) during a blind call transfer, for this SIP entity (which [IpProfile_SBCPlayRBTToTrans does not support such a tone generation during call transfer).
Page 327 Factor' (DJBufOptFactor) can be used to configure minimum packet delay only when transcoding is employed.  This functionality may require DSP resources. For more information, contact your AudioCodes sales representative. Web: Remote Renegotiate on Enables local handling of fax detection and negotiation by the Fax Detection device on behalf of the SIP entity (to which the IP Profile is assigned).
Page 328 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 329: Gateway Application
Part V Gateway Application...
Page 331: Introduction
CO or the PBX) and connects to analog telephones, dial-up modems, and fax machines. The FXS is designed to supply line voltage and ringing current to these telephone devices. An FXS VoIP device interfaces between the analog telephone devices and the Internet. Version 6.8 Mediant 1000B Gateway & SBC...
Page 332 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 333: Digital Pstn
BRI trunks can operate with E1 or T1 trunks. • If the protocol type is CAS, you can assign or modify a dial plan (in the 'Dial Plan' field) and perform this without stopping the trunk. Version 6.8 Mediant 1000B Gateway & SBC...
Page 334 Mediant 1000B Gateway & SBC  To configure trunks: Open the Trunk Settings page (Configuration tab > VoIP menu > PSTN > Trunk Settings). On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: •...
Page 335 Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'. To save the changes to flash memory, see ''Saving Configuration'' on page 568. To reset the device, see ''Resetting the Device'' on page 565. Version 6.8 Mediant 1000B Gateway & SBC...
Page 336: Tdm And Timing
Mediant 1000B Gateway & SBC 21.2 TDM and Timing This section describes the configuration of the TDM and clock timing parameters. 21.2.1 Configuring TDM Bus Settings The TDM page allows you to configure the device's Time-Division Multiplexing (TDM) bus settings. For a description of these parameters, see ''PSTN Parameters'' on page 857.
Page 337: Recovering Clock From Pstn Line Interface
Settings page, set the 'TDM Bus Clock Source' parameter (TDMBusClockSource) to Internal. For 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). Version 6.8 Mediant 1000B Gateway & SBC...
Page 338: Configuring Cas State Machines
Mediant 1000B Gateway & SBC 21.3 Configuring CAS State Machines The CAS State Machine page allows you to 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). The change doesn't affect the state machine itself, but rather the configuration.
Page 339 Defines which Signaling System to use in both directions [CasStateMachineDigitSignalingSyste (detection\generation).  [0] DTMF = Uses DTMF signaling.  [1] MF = Uses MF signaling (default).  [-1] Default = Default value - use value from CAS state machine. Version 6.8 Mediant 1000B Gateway & SBC...
Page 340: Configuring Digital Gateway Parameters
Mediant 1000B Gateway & SBC 21.4 Configuring Digital Gateway Parameters The Digital Gateway Parameters page allows you to configure miscellaneous digital parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 715.  To configure the digital gateway parameters: Open the Digital Gateway Parameters page (Configuration tab >...
Page 341: Tunneling Applications
When a failure in a physical trunk or in the IP network occurs, the device re- establishes the tunneling connections when the network is restored. Note: It's recommended to use the keep-alive mechanism for each connection, by activating the ‘session expires’ timeout and using Re-INVITE messages. Version 6.8 Mediant 1000B Gateway & SBC...
Page 342 Mediant 1000B Gateway & SBC device supports configuration (TDMoIPInitiateInviteTime TDMoIPInviteRetryTime parameters) of the following timers for the TDM-over-IP tunneling application:  Time between successive INVITEs sent from the same trunk.  Time between call release and the new INVITE that is sent on the same channel. The call can be released if the device receives a 4xx or 5xx response.
Page 343 TrunkGroup 0 = 0,1,1,16,16,7001,2; TrunkGroup 0 = 0,2,2,16,16,7002,2; TrunkGroup 0 = 0,3,3,16,16,7003,2; [\TrunkGroup] [ CodersGroup0 ] FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce; CodersGroup0 0 = g7231; CodersGroup0 1 = Transparent; [ \CodersGroup0 ] Version 6.8 Mediant 1000B Gateway & SBC...
Page 344: Dsp Pattern Detector
Mediant 1000B Gateway & SBC [TelProfile] FORMAT TelProfile_Index = TelProfile_ProfileName, TelProfile_TelPreference, TelProfile_CodersGroupID, TelProfile_IsFaxUsed, TelProfile_JitterBufMinDelay, TelProfile_JitterBufOptFactor, TelProfile_IPDiffServ, TelProfile_SigIPDiffServ, TelProfile_DtmfVolume, TelProfile_InputGain, TelProfile_VoiceVolume, TelProfile_EnableReversePolarity, TelProfile_EnableCurrentDisconnect, TelProfile_EnableDigitDelivery, TelProfile_EnableEC, TelProfile_MWIAnalog, TelProfile_MWIDisplay, TelProfile_FlashHookPeriod, TelProfile_EnableEarlyMedia, TelProfile_ProgressIndicator2IP; TelProfile_1 = voice,$$,1,$$,$$,$$,$$,$$,$$,$$ 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 345 INFO message with Setup Ack encapsulated in its MIME body. The PBX sends QSIG Information messages (to complete the Called Party Number) only after it receives the Setup Ack. The device relays these Information messages encapsulated in SIP INFO messages to the remote party. Version 6.8 Mediant 1000B Gateway & SBC...
Page 346: Isdn Non-Facility Associated Signaling (Nfas)
Mediant 1000B Gateway & SBC 21.6 ISDN Non-Facility Associated Signaling (NFAS) In regular T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B- channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.
Page 347: Working With Dms-100 Switches
NFASGroupNumber_1 = 1 NFASGroupNumber_2 = 1 NFASGroupNumber_3 = 1 DchConfig_0 = 0 ;Primary T1 trunk DchConfig_1 = 2 ;B-Channel NFAS trunk DchConfig_2 = 2 ;B-Channel NFAS trunk DchConfig_3 = 2 ;B-channel NFAS trunk Version 6.8 Mediant 1000B Gateway & SBC...
Page 348: Creating An Nfas-Related Trunk Configuration
Mediant 1000B Gateway & SBC 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.
Page 349: Collecting Isdn Digits And Sending Complete Number In Sip
 ISDNRxOverlap_x = 1 (can be configured per trunk)  TimeBetweenDigits  MaxDigits  MuteDTMFInOverlap  DigitMapping For configuring ISDN overlap dialing using the Web interface, see ''Configuring Trunk Settings'' on page 333. Version 6.8 Mediant 1000B Gateway & SBC...
Page 350: Interworking Isdn Overlap Dialing With Sip According To Rfc 3578
Mediant 1000B Gateway & SBC 21.7.2 Interworking ISDN Overlap Dialing with SIP According to RFC 3578 The device supports the interworking of ISDN overlap dialing to SIP and vice versa, according to RFC 3578.  Interworking ISDN overlap dialing to SIP (Tel to IP): The device sends collected digits each time it receives them (initially from the ISDN Setup message and then from subsequent Q.931 Information messages) to the IP side, using subsequent SIP...
Page 351: Trunk Group
''Configuring Trunk Group Settings'' on page 353).  To register the Trunk Groups, click the Register button, located below the Trunk Group table.  To unregister the Trunk Groups, click the Unregister button, located below the Trunk Group table. Version 6.8 Mediant 1000B Gateway & SBC...
Page 352 Mediant 1000B Gateway & SBC Table 22-1: Trunk Group Table Parameter Descriptions Parameter Description Module Defines the module (i.e., FXS, FXO, PRI, or BRI) for which you CLI: module want to define the Trunk Group. [TrunkGroup_Module] From Trunk Defines the starting physical Trunk number in the Trunk Group.
Page 353: Configuring Trunk Group Settings
Click Submit, and then save ("burn") your settings to flash memory. Table 22-2: Trunk Group Settings Parameter Descriptions Parameter Description Trunk Group ID Defines the Trunk Group ID that you want to configure. CLI: trunk-group-id [TrunkGroupSettings_TrunkGr Version 6.8 Mediant 1000B Gateway & SBC...
Page 354 Mediant 1000B Gateway & SBC Parameter Description oupId] Channel Select Mode Defines the method by which IP-to-Tel calls are assigned to the CLI: channel-select-mode channels of the Trunk Group. [TrunkGroupSettings_Channel  [0] By Dest Phone Number = The channel is selected SelectMode] according to the called (destination) number.
Page 355 Group, according to the settings in the Account table (see ''Configuring Registration Accounts'' on page 279). An example is shown below of a REGISTER message for registering endpoint "101" using the registration Per Endpoint mode: REGISTER sip:SipGroupName SIP/2.0 Via: SIP/2.0/UDP Version 6.8 Mediant 1000B Gateway & SBC...
Page 356 Mediant 1000B Gateway & SBC Parameter Description 10.33.37.78;branch=z9hG4bKac862428454 From: <sip:101@GatewayName>;tag=1c862422082 To: <sip:101@GatewayName> Call-ID: 9907977062512000232825@10.33.37.78 CSeq: 3 REGISTER Contact: <sip:101@10.33.37.78>;expires=3600 Expires: 3600 User-Agent: Sip-Gateway/v.6.60A.011.002 Content-Length: 0 The "SipGroupName" in the Request-URI is configured in the IP Group table (see ''Configuring IP Groups'' on page 261).
Page 357 The SIP NOTIFY messages are sent to the IP Group defined by the NotificationIPGroupID parameter. Note: This parameter appears in the table only if the VoiceMailInterface parameter is set to 3 (QSIG). Configuring Voice Mail on page 456. Version 6.8 Mediant 1000B Gateway & SBC...
Page 358 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 359: Manipulation
559. However, if you enter 55 in Index 1 and 551 in Index 2, the device applies rule 1 to all numbers that start with 55, including numbers that start with 551. Version 6.8 Mediant 1000B Gateway & SBC...
Page 360 Mediant 1000B Gateway & SBC You can perform a second "round" (additional) of source and destination number manipulations for IP-to-Tel calls, on an already manipulated number. The initial and additional number manipulation rules are both configured in the number manipulation tables for Ip-to-Tel calls.
Page 361 2001, it is changed to 3146. Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Source IP Group Destination [6,7,8] Prefix 1001 123451001# [30-40]x 2001 Source Prefix Stripped Digits from Left Stripped Digits from Right Version 6.8 Mediant 1000B Gateway & SBC...
Page 362 Mediant 1000B Gateway & SBC Parameter Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Prefix to Add Suffix to Add Number of Digits to Leave Presentation Allowed Restricted Table 23-1: Number Manipulation Tables Parameter Descriptions Parameter Description Index Defines an index number for the new table record.
Page 363 Defines the number or string that you want added to the front of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 9 and the phone number CLI: prefix-to-add is 1234, the new number is 91234. [Prefix2Add] Version 6.8 Mediant 1000B Gateway & SBC...
Page 364 Mediant 1000B Gateway & SBC Parameter Description Web: Suffix to Add Defines the number or string that you want added to the end of the EMS: Prefix/Suffix To Add telephone number. For example, if you enter 00 and the phone number CLI: suffix-to-add is 1234, the new number is 123400.
Page 365: Manipulating Number Prefix
The prefix is calculated as 020215. The first seven digits from the left are removed from the original number, thereby changing the number to 8888888. The prefix that was previously calculated is then added. Version 6.8 Mediant 1000B Gateway & SBC...
Page 366: Sip Calling Name Manipulations
Mediant 1000B Gateway & SBC 23.4 SIP Calling Name Manipulations The calling name manipulation tables lets you configure up to 120 manipulation rules for manipulating the calling name (i.e., caller ID) in SIP messages, for IP-to-Tel and Tel-to-IP calls. Manipulation includes modifying or removing the calling name. The calling name manipulation tables include the following: ...
Page 367 100, 101 or 105. You can also use the $ sign to denote calls without a calling number. For a description of available notations, see ''Dialing Plan Notation for Routing and Manipulation Tables'' on page 713. Version 6.8 Mediant 1000B Gateway & SBC...
Page 368 Mediant 1000B Gateway & SBC Parameter Description The default value is the asterisk (*) symbol (i.e., any source prefix). Web: Calling Name Prefix Defines the caller name (i.e., caller ID) prefix. CLI: calling-name-prefix You can use special notations for denoting the prefix. For example, to [_CallingNamePrefix] denote calls without a calling name, use the $ sign.
Page 369: Configuring Redirect Number Ip To Tel
 Manipulation operation (Action), for example, remove user-defined number of digits from the left of the redirect number. If the incoming call matches the characteristics of a rule, its manipulation action is applied. Version 6.8 Mediant 1000B Gateway & SBC...
Page 370 Mediant 1000B Gateway & SBC Notes: • If the device copies the received destination number to the outgoing SIP redirect number (enabled by the CopyDest2RedirectNumber parameter), no redirect number Tel-to-IP manipulation is done. • The manipulation rules are done in the following order: Stripped Digits From Left, Stripped Digits From Right, Number of Digits to Leave, Prefix to Add, and then Suffix to Add.
Page 371 P- Asserted-Identity URI host name (instead of to the From header). Web: Destination Host Prefix Defines the Request-URI host name prefix, which appears in the Version 6.8 Mediant 1000B Gateway & SBC...
Page 372 Mediant 1000B Gateway & SBC Parameter Description CLI: dst-host-prefix incoming SIP INVITE message. [_DestHost] The default value is the asterisk (*) symbol (i.e., any prefix). Note: This parameter is applicable only to the Redirect Number IP-to- Tel table. Operation (Action)
Page 373: Manipulating Redirected And Diverted Numbers For Call Diversion
Number of Digits to Leave After the above manipulation is done, the device sends the following outgoing SIP 302 response: SIP/2.0 302 Moved Temporarily Via: SIP/2.0/TLS 10.33.45.68;branch=z9hG4bKac54132643;alias From: "MP118 1" <sip:8001@10.33.45.68>;tag=1c54119560 To: <sip:6001@10.33.45.69;user=phone>;tag=1c664560944 Version 6.8 Mediant 1000B Gateway & SBC...
Page 374: Mapping Npi/Ton To Sip Phone-Context
Mediant 1000B Gateway & SBC Call-ID: 541189832710201115142@10.33.45.68 CSeq: 1 INVITE Contact: <sip:8005@10.33.45.68;user=phone> Supported: em,timer,replaces,path,early-session,resource-priority Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUB SCRIBE,UPDATE Diversion: <tel:6005>;reason=unknown;counter=1 Server: Audiocodes-Sip-Gateway-IPmedia 260_UN/v.6.20A.043.001 Reason: SIP ;cause=302 ;text="302 Moved Temporarily" Content-Length: 0 23.7 Mapping NPI/TON to SIP Phone-Context The Phone Context table lets you configure rules for mapping the Numbering Plan Indication (NPI) and Type of Number (TON) to the SIP 'phone-context' parameter, and vice versa.
Page 375: Configuring Release Cause Mapping
PSTN. If no match is found, the default static mapping is used.  Release Cause Mapping from ISDN to SIP table: Maps ISDN cause codes to SIP Version 6.8 Mediant 1000B Gateway & SBC...
Page 376 Mediant 1000B Gateway & SBC release codes. When a Release Cause is received from the PSTN, the device searches this table for a match. If the Q.850 Release Cause is found, the SIP response assigned to it is sent to the IP side. If no match is found, the default static mapping is used.
Page 377: Fixed Mapping Of Sip Response To Isdn Release Reason
Normal, unspecified Server internal error Temporary failure Not implemented Network out of order Bad gateway Network out of order Service unavailable Temporary failure Server timeout Recovery on timer expiry 505* Version not supported Interworking Version 6.8 Mediant 1000B Gateway & SBC...
Page 378: Fixed Mapping Of Isdn Release Reason To Sip Response
Mediant 1000B Gateway & SBC ISDN Release SIP Response Description Description Reason Busy everywhere User busy Decline Call rejected Does not exist anywhere Unallocated number 606* Not acceptable Network out of order * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft does not specify their cause code mapping.
Page 379 Temporarily not available implemented Message not compatible with call state or message type non-existent or not 409* Conflict implemented Information element non-existent or not 480* Not found implemented Invalid information elements contents 501* Not implemented Version 6.8 Mediant 1000B Gateway & SBC...
Page 380 Mediant 1000B Gateway & SBC ISDN Release Description Description Reason Response Message not compatible with call state 503* Service unavailable Recovery of timer expiry Request timeout Protocol error Server internal error Interworking unspecified Server internal error * Messages and responses were created because the ‘ISUP to SIP Mapping’ draft doesn’t specify their cause code mapping.
Page 381: Reason Header
Cause' parameter. This parameter defines Q.931 release causes. Its default value is 3, which is mapped to the SIP 404 response. By changing its value to 34, the SIP 503 response is sent. Other causes can be used as well. Version 6.8 Mediant 1000B Gateway & SBC...
Page 382: Numbering Plans And Type Of Number
Mediant 1000B Gateway & SBC 23.9 Numbering Plans and Type of Number The IP-to-Tel destination or source number manipulation tables allow you to classify numbers by their Numbering Plan Indication (NPI) and Type of Number (TON). The device supports all NPI/TON classifications used in the ETSI ISDN variant, as shown in the table...
Page 383: Routing
Source IP Group (to which the call belongs) • Source and destination Request-URI host name prefix • Source Trunk Group (from where the call is received) • Source (calling) and destination (called) telephone number prefix and suffix Version 6.8 Mediant 1000B Gateway & SBC...
Page 384 Mediant 1000B Gateway & SBC • Source and destination Request-URI host name prefix  Destination: If the call matches the configured characteristics, the device routes the call to an IP destination. If no characteristics match is found in the table, the call is rejected.
Page 385 FQDN to resolve into two IP addresses. For more information on alternative routing, see ''Alternative Routing for Tel-to-IP Calls'' on page 398.  Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine Version 6.8 Mediant 1000B Gateway & SBC...
Page 386 Mediant 1000B Gateway & SBC with calculating the cost of using a service (Tel-to-IP call) and relaying that information to the customer. AOC, which is configured in the Charge Codes table, can be applied per Tel-to-IP routing rule. Note: You can configure up to three alternative routing rules per "main" routing rule in the Inbound IP Routing table.
Page 387 Number Manipulation'' on page 359. Route Name Defines an arbitrary name to easily identify the routing rule. CLI: route-name The valid value is a string of up to 20 characters. By default, no [PREFIX_RouteName] Version 6.8 Mediant 1000B Gateway & SBC...
Page 388 Mediant 1000B Gateway & SBC Parameter Description value is defined. Matching Call Characteristics Web: Src. IP Group ID Defines the IP Group from where the incoming IP call is received. EMS: Source IP Group ID Typically, the IP Group of an incoming INVITE is determined CLI: src-ip-group-id according to the Inbound IP Routing table.
Page 389 Prefix' field, enter 00 and in the 'Dest IP Address' field, enter 0.0.0.0.  For routing calls between phones connected to the device (i.e., local routing), enter the device's IP address.  When the device's IP address is unknown (e.g., when DHCP is Version 6.8 Mediant 1000B Gateway & SBC...
Page 390 Mediant 1000B Gateway & SBC Parameter Description used), enter IP address 127.0.0.1.  When using domain names, enter the DNS server's IP address or alternatively, configure these names in the Internal DNS table (see ''Configuring the Internal DNS Table'' on page 130).
Page 391 Forking Group number that is lower than that of index entry 1.  Table index entry 1 is defined with Forking Group "1", index entry 2 with Forking Group "2", and index entries 3 and 4 with Version 6.8 Mediant 1000B Gateway & SBC...
Page 392: Configuring Inbound Ip Routing Table
Mediant 1000B Gateway & SBC Parameter Description Forking Group "1": The device first sends the call according to index entries 1, 3, and 4 (all belonging to Forking Group "1"), and if the destination is unavailable and alternative routing is enabled, the device sends the call according to index entry 2.
Page 393 The following procedure describes how to configure Inbound IP Routing rules in the Web interface. You can also configure Inbound IP Routing rules using the table ini file parameter, PSTNPrefix or CLI command, configure voip > gw routing ip2tel-routing. Version 6.8 Mediant 1000B Gateway & SBC...
Page 394 Mediant 1000B Gateway & SBC  To configure IP-to-Tel or inbound IP routing rules: Open the Inbound IP Routing Table page (Configuration tab > VoIP menu > GW and IP to IP > Routing > IP to Trunk Group Routing).
Page 395 Defines the SRD from where the incoming packet is received. CLI: src-srd-id Note: When the incoming INVITE matches the SRD in the [PstnPrefix_SrcSRDID] routing rule, if the 'Source IP Group ID' parameter (see below) Version 6.8 Mediant 1000B Gateway & SBC...
Page 396: Ip Destinations Connectivity Feature
Mediant 1000B Gateway & SBC Parameter Description is defined and it is associated with a different SRD, the incoming SIP call is rejected. If the 'Source IP Group ID' parameter is not defined, the SRD's default IP Group is used. If there is no valid source IP Group, the call is rejected.
Page 397 IP Connectivity: This page displays a more informative connectivity status of the IP destinations used in Tel-to-IP routing rules in the Outbound IP Routing table. For viewing this page, see ''Viewing IP Connectivity'' on page 651. Version 6.8 Mediant 1000B Gateway & SBC...
Page 398: Alternative Routing For Tel-To-Ip Calls
Mediant 1000B Gateway & SBC 24.5 Alternative Routing for Tel-to-IP Calls The device supports various alternative Tel-to-IP call routing methods, as described in this section. 24.5.1 Alternative Routing Based on IP Connectivity You can configure the device to route Tel-to-IP calls to an alternative IP destination when the connectivity state of an IP destination is unavailable.
Page 399: Alternative Routing Based On Sip Responses
Alternative Routing table and 3) configuring an alternative routing rule. Note: The device also plays a tone to the endpoint whenever an alternative route is used. This tone is played for a user-defined time, configured by the AltRoutingToneDuration parameter. Version 6.8 Mediant 1000B Gateway & SBC...
Page 400 Mediant 1000B Gateway & SBC Depending on configuration, the alternative routing is done using one of the following configuration entities:  Outbound IP Routing Rules: You configure alternative routing rules for a specific routing rule in the Outbound IP Routing table. If the destination of the "main" routing rule is unavailable, the device searches the table for the next matching rule (e.g.,...
Page 401 If you are using the Outbound IP Routing table, configure alternative routing rules with identical call matching characteristics, but with different IP destinations. If you are using the Proxy Set, configure redundant proxies. Version 6.8 Mediant 1000B Gateway & SBC...
Page 402: Alternative Routing Upon Sip 3Xx With Multiple Contacts
Mediant 1000B Gateway & SBC 24.5.3 Alternative Routing upon SIP 3xx with Multiple Contacts You can configure how the device handles received SIP 3xx responses that contain multiple alternative contacts. The 3xx response indicates that the original destination is unavailable (e.g., 301 Moved Permanently – user cannot be found) and that the call can be redirected to alternative destinations specified in the SIP Contact headers.
Page 403: Alternative Routing For Ip-To-Tel Calls
The following procedure describes how to configure alternative routing reasons for IP-to- Tel calls in the Web interface. You can also configure alternative routing reasons for IP-to- Tel calls using the table ini file parameter, AltRouteCauseIP2Tel or CLI command, configure voip/gw routing alt-route-cause-ip2tel. Version 6.8 Mediant 1000B Gateway & SBC...
Page 404: Alternative Routing To An Ip Destination Upon A Busy Trunk
Mediant 1000B Gateway & SBC  To configure alternative Trunk Group routing based on Q.931 cause codes: In the Proxy & Registration page, set the 'Redundant Routing Mode' parameter to Routing Table so that the device uses the Inbound IP Routing table for alternative routing.
Page 405 FQDN, or a SIP Request-URI user name and host part (i.e., user@host). The following syntax can also be used: host:port;transport=xxx (i.e., IP address, port and transport type). Note: When configured with a user@host, the original destination number is replaced by the user part. Version 6.8 Mediant 1000B Gateway & SBC...
Page 406: Alternative Routing Upon Isdn Disconnect
Mediant 1000B Gateway & SBC 24.6.3 Alternative Routing upon ISDN Disconnect You can configure when the device sends a call to an alternative route if it receives an ISDN Q.931 Disconnect message with a Progress Indicator (PI) IE from the Tel side for IP- to-Tel calls.
Page 407: Configuring Dtmf And Dialing
Open the DTMF & Dialing page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > DTMF & Dialing). Configure the parameters as required. Click Submit. To save the changes to flash memory, see ''Saving Configuration'' on page 568. Version 6.8 Mediant 1000B Gateway & SBC...
Page 408: Dialing Plan Features
Mediant 1000B Gateway & SBC 25.1 Dialing Plan Features This section describes various dialing plan features supported by the device. 25.1.1 Digit Mapping Digit map pattern rules are used for Tel-to-IP ISDN overlap dialing (by setting the ISDNRxOverlap parameter to 1) to reduce the dialing period (for digital interface). For more information on digit maps for ISDN overlapping, see ISDN Overlap Dialing on page 348.
Page 409 (TimeBetweenDigits parameter), it sends the collected digits. Therefore, this ensures that calls are not rejected as a result of their digit pattern not been completed in the Dial Plan. Version 6.8 Mediant 1000B Gateway & SBC...
Page 410: External Dial Plan File
Mediant 1000B Gateway & SBC 25.1.2 External Dial Plan File The device can be loaded with a Dial Plan file with user-defined dialing plans. For more information, see ''Dial Plan File'' on page 583. User's Manual Document #: LTRT-27034...
Page 411: Configuring Supplementary Services
The Supplementary Services page is used to configure many of the discussed supplementary services parameters. For a description of the parameters appearing on this page, see ''Configuration Parameters Reference'' on page 715. Version 6.8 Mediant 1000B Gateway & SBC...
Page 412 Mediant 1000B Gateway & SBC  To configure supplementary services parameters: Open the Supplementary Services page (Configuration tab > VoIP menu > GW and IP to IP > DTMF & Supplementary > Supplementary Services). Configure the parameters as required. Click Submit, or click the Subscribe to MWI or Unsubscribe to MWI buttons to save your changes and to subscribe / unsubscribe to the MWI server.
Page 413: Call Hold And Retrieve
(or any other hold tone) is played (over IP) by the remote party. You can also configure the device to keep a call on-hold for a user-defined time after which the call is disconnected, using the HeldTimeout parameter. Version 6.8 Mediant 1000B Gateway & SBC...
Page 414 Mediant 1000B Gateway & 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...
Page 415: Call Pickup
 After holding a call (by pressing hook-flash), the holding party hears a dial tone and can then initiate a new call, which is called a Consultation call. Version 6.8 Mediant 1000B Gateway & SBC...
Page 416: Call Transfer
Mediant 1000B Gateway & SBC  While hearing a dial tone, or when dialing to the new destination (before dialing is complete), the user can retrieve the held call by pressing hook-flash.  The held call can’t be retrieved while ringback tone is heard.
Page 417: Consultation Transfer For Qsig Path Replacement
IP-to-Tel call: destination number of the original call. • If the UseReferredByForCallingNumber parameter is set to 1, the source number is taken from the SIP Referred-By header if included in the received SIP REFER message. Version 6.8 Mediant 1000B Gateway & SBC...
Page 418: Call Forward
Mediant 1000B Gateway & SBC This source number can also be used as the value for the 'Source Prefix' field in the IP-to-Tel Destination Phone Number Manipulation table. The local IP address is used as the value for the 'Source IP Address' field.
Page 419: Call Forward Reminder Ring
For playing the special dial tone, the received SIP NOTIFY message must contain the following headers:  From and To: contain the same information, indicating the specific endpoint  Event: ua-profile  Content-Type: "application/simservs+xml" Version 6.8 Mediant 1000B Gateway & SBC...
Page 420: Call Forward Reminder Dial Tone (Off-Hook) Upon Spanish Sip Alert-Info
Mediant 1000B Gateway & SBC  Message body is the XML body and contains the “dial-tone-pattern” set to "special- condition-tone" (<ss:dial-tone-pattern>special-condition-tone</ss:dial-tone-pattern>), which is the special tone indication. To cancel the special dial tone and playing the regular dial tone, the received SIP NOTIFY message must contain the following headers: ...
Page 421: Call Waiting
Call Waiting Indications. Applicable only to FXS modules. Both the calling and called sides are supported by FXS interfaces; FXO interfaces support only the calling side. Version 6.8 Mediant 1000B Gateway & SBC...
Page 422: Message Waiting Indication
Mediant 1000B Gateway & SBC To indicate Call Waiting, the device sends a 182 Call Queued response. The device identifies Call Waiting when a 182 Call Queued response is received. Note: The Call Waiting feature is applicable only to FXS/FXO interfaces.
Page 423: Caller Id
Send MWI Interrogation message, use its result, and use the MWI Activate requests. 26.9 Caller ID This section describes the device's Caller ID support. Note: The Caller ID feature is applicable only to FXS/FXO interfaces. Version 6.8 Mediant 1000B Gateway & SBC...
Page 424: Caller Id Detection / Generation On The Tel Side
Mediant 1000B Gateway & SBC 26.9.1 Caller ID Detection / Generation on the Tel Side By default, generation and detection of Caller ID to the Tel side is disabled. To enable Caller ID, set the parameter EnableCallerID to 1. When the Caller ID service is enabled: ...
Page 425: Caller Id On The Ip Side
‘Presentation’ parameter in the ‘Tel to IP Source Number Manipulation’ table. Therefore, this table can be used to set the presentation for specific calls according to Source / Destination prefixes. Version 6.8 Mediant 1000B Gateway & SBC...
Page 426: Three-Way Conferencing
The device supports the following conference modes:  Conferencing managed by an external, AudioCodes Conference (media) server: The Conference-initiating INVITE sent by the device uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties.
Page 427 Open the Supplementary Services page. Set 'Enable 3-Way Conference' to Enable (Enable3WayConference = 1). Set '3-Way Conference Mode' to On Board (3WayConferenceMode = 2). 'Flash Keys Sequence Style' Sequence Sequence (FlashKeysSequenceStyle = 1 or 2). Version 6.8 Mediant 1000B Gateway & SBC...
Page 428: Emergency E911 Phone Number Services
Mediant 1000B Gateway & SBC 26.11 Emergency E911 Phone Number Services This section describes the device's support for emergency phone number services. The device supports the North American emergency telephone number system known as Enhanced 911 (E911), according to the TR-TSY-000350 and Bellcore's GR-350-Jun2003 standards.
Page 429 From header/user part = calling party number as received from the MF spill The ANI and the pseudo-ANI numbers are sent to the PSAP either in the From and/or P- AssertedID SIP header. Version 6.8 Mediant 1000B Gateway & SBC...
Page 430 Mediant 1000B Gateway & SBC Typically, the MF spills are sent from the E911 tandem switch to the PSAP, as shown in the table below: Table 26-2: Dialed MF Digits Sent to PSAP Digits of Calling Number Dialed MF Digits 8 digits "nnnnnnnn"...
Page 431: Fxo Device Interworking Sip E911 Calls From Service Provider's Ip Network To Psap Did Lines
RFC 2833 hookflash Telephony event (according to the HookFlashOption parameter). Following the "hookflash" Wink signal, the PSAP sends DTMF digits. These digits are detected by the device and forwarded to the IP, using RFC 2833 telephony events (or Version 6.8 Mediant 1000B Gateway & SBC...
Page 432 Mediant 1000B Gateway & SBC inband, depending on the device's configuration). Typically, this Wink signal followed by the DTMF digits initiates a call transfer. For supporting the E911 service, used the following configuration parameter settings:  Enable911PSAP = 1 (also forces the EnableDIDWink and EnableReversalPolarity) ...
Page 433 User-Agent: Audiocodes-Sip-Gateway-FXO/v.6.00A.020.077 Privacy: none P-Asserted-Identity: "0123456789" <sip:3333344444@audiocodes.com> Content-Type: application/sdp Content-Length: 253 o=AudiocodesGW 771609035 771608915 IN IP4 10.33.37.78 s=Phone-Call c=IN IP4 10.33.37.78 t=0 0 m=audio 4000 RTP/AVP 8 0 101 a=rtpmap:8 pcma/8000 a=rtpmap:0 pcmu/8000 Version 6.8 Mediant 1000B Gateway & SBC...
Page 434: Pre-Empting Existing Calls For E911 Ip-To-Tel Calls
Mediant 1000B Gateway & SBC a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv  Example B: The detection of a Wink signal generates the following SIP INFO message: INFO sip:4505656002@192.168.13.40:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.2:5060 From: port1vega1 <sip:06@192.168.13.2:5060> To: <sip:4505656002@192.168.13.40:5060>;tag=132878796- 1040067870294 Call-ID: 0010-0016-D69A7DA8-1@192.168.13.2...
Page 435: Enhanced 9-1-1 Support For Lync Server 2010
E9-1-1 due to the difficulty in accurately locating the E9-1-1 caller. This section describes the E9-1-1 solution provided by Microsoft Lync Server 2010 (hereafter referred to as Lync Server 2010), and the deployed AudioCodes ELIN Gateway which provides the ISDN (or CAMA) connectivity to the PSTN-based E9-1-1 emergency providers.
Page 436: Microsoft Lync Server 2010 And E9-1-1
Mediant 1000B Gateway & SBC The E9-1-1 Selective Router determines the geographical location of the caller by requesting this information from an Automatic Location Identification (ALI) database based on the phone number or Automatic Number Identifier (ANI) of the 911 caller.
Page 437 When a user manually provides a location, the location is mapped based on the MAC address of the default gateway of the client’s network and stored on the client. When the client returns to Version 6.8 Mediant 1000B Gateway & SBC...
Page 438 Mediant 1000B Gateway & SBC any previously stored location, the client is automatically set to that location. A user can also manually select any location stored in the local users table and manage existing entries. 26.11.4.2.2 Adding ELINs to the Location Information Server...
Page 439 ERL with a unique ELIN. Table 26-5: Designating ERLs and Assigning to ELINs ERL Number Physical Area IP Address ELIN Floor 1 10.13.124.xxx 503 972-4410 Floor 2 10.15.xxx.xxx 503 972-4411 Floor 3 10.18.xxx.xxx 503 972-4412 Version 6.8 Mediant 1000B Gateway & SBC...
Page 440: Audiocodes Elin Gateway For Lync Server 2010 E9-1-1 Calls To Pstn
PSAP, based on ELIN-address match lookup in the Emergency Services provider's ALI database. The figure below illustrates an AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment for handling E9-1-1 calls between the Enterprise and the PSTN.
Page 441 ELIN is disregarded and no longer used (for PSAP callback). Therefore, table entries of only the most recently terminated E9-1-1 callers are considered in the ELIN table. The maximum entries in the ELIN table depend on the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment: •...
Page 442 Mediant 1000B Gateway & SBC o=- 0 0 IN IP4 Client s=session c=IN IP4 Client t=0 0 m=audio 30684 RTP/AVP 114 111 112 115 116 4 3 8 0 106 97 c=IN IP4 172.29.105.23 a=rtcp:60423 a=label:Audio a=rtpmap:3 GSM/8000/1 a=rtpmap:101 telephone-event/8000...
Page 443 Gateway sends the ELIN number as the E9-1-1 calling number to the PSTN-based emergency provider. If the XML message contains more than one ELIN number, the ELIN Gateway chooses the ELIN according to the following logic: Version 6.8 Mediant 1000B Gateway & SBC...
Page 444: Configuring Audiocodes Elin Gateway
26.11.4.4 Configuring AudioCodes ELIN Gateway This section describes E9-1-1 configuration of the AudioCodes ELIN Gateway deployed in the Lync Server 2010 environment. 26.11.4.4.1 Enabling the E9-1-1 Feature By default, the E9-1-1 feature in the ELIN Gateway for Lync Server 2010 is disabled.
Page 445 Emergency calls received from London office users are routed by the device to the London police department, which is +4420999. • Emergency calls received from Manchester office users are routed by the device to the Manchester police department, which is +44161999. Version 6.8 Mediant 1000B Gateway & SBC...
Page 446 Mediant 1000B Gateway & SBC The international code, +44 for England is used for IP routing considerations, but can be omitted depending on your specific network environment. The above example scenario is configured as follows: Enable location-based emergency routing, by loading an ini file to the device with the...
Page 447: Multilevel Precedence And Preemption
Table 26-7: MLPP Call Priority Levels (Precedence) and DSCP Configuration Parameters MLPP Precedence Level Precedence Level in Resource- DSCP Configuration Parameter Priority SIP Header 0 (lowest) routine MLPPRoutineRTPDSCP priority MLPPPriorityRTPDSCP immediate MLPPImmediateRTPDSCP flash MLPPFlashRTPDSCP flash-override MLPPFlashOverRTPDSCP 9 (highest) flash-override-override MLPPFlashOverOverRTPDSCP Version 6.8 Mediant 1000B Gateway & SBC...
Page 448 Mediant 1000B Gateway & SBC 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. The SIP Resource-Priority header contains two fields, namespace and priority.
Page 449: Mlpp Preemption Events In Sip Reason Header
• The softswitch performs a network preemption of an active call - the following sequence of events occurs: The softswitch sends the device a SIP BYE request with this Reason cause code. Version 6.8 Mediant 1000B Gateway & SBC...
Page 450: Precedence Ring Tone
Mediant 1000B Gateway & SBC The device initiates the release procedures for the B-channel associated with the call request and maps the preemption cause to PRI Cause = #8 ‘Preemption’. This value indicates that the call is being preempted. For PRI, it also indicates that the B-channel is not reserved for reuse.
Page 451: Configuring Multi-Line Extensions And Supplementary Services
Open the Supplementary Services Table page (Configuration tab > VoIP menu > GW and IP to IP > DTMF and Supplementary > Supp Services Table). Click Add; the following dialog box appears: Figure 26-10: Supplementary Services Table - Add Record Version 6.8 Mediant 1000B Gateway & SBC...
Page 452 Mediant 1000B Gateway & SBC Configure a supplementary service according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. The figure below displays an example of multiple-line extensions configured in the...
Page 453: 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 454: Configuring Charge Codes
The device supports various methods for AOC:  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.  IP-to-Tel direction provides optional methods: •...
Page 455 It is mandatory that the last time period of each rule end at midnight (00). This prevents undefined time frames in a day. Pulse Interval Defines the time interval between pulses (in tenths of a CLI: pulse-interval-<1-4> second). [ChargeCode_PulseInterval<1-4>] Version 6.8 Mediant 1000B Gateway & SBC...
Page 456: Configuring Voice Mail
Mediant 1000B Gateway & SBC Parameter Description Pulses On Answer Defines the number of pulses sent on answer. CLI: pulses-on-answer-<1-4> [ChargeCode_PulsesOnAnswer<1- 4>] 26.18 Configuring Voice Mail The Voice Mail Settings page allows you to configure the voice mail parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 715.
Page 457: Analog Gateway
The activation of each feature remains in effect until it is deactivated (i.e., not deactivated after a call). • For a description of the keypad parameters, see ''Telephone Keypad Sequence Parameters'' on page 946. Version 6.8 Mediant 1000B Gateway & SBC...
Page 458 Mediant 1000B Gateway & SBC  To configure the keypad features Open the Keypad Features page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Keypad Features). Figure 27-1: Keypad Features Page Configure the keypad features as required.
Page 459: Configuring Metering Tones
The FXO Settings page allows you to configure the device's specific FXO parameters. For a description of these parameters, see ''Configuration Parameters Reference'' on page 715. Note: The FXO Settings page is available only for FXO interfaces. Version 6.8 Mediant 1000B Gateway & SBC...
Page 460: Configuring Authentication
Mediant 1000B Gateway & SBC  To configure the FXO parameters: Open the FXO Settings page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > FXO Settings). Figure 27-3: FXO Settings Page Configure the parameters as required.
Page 461 (Read-only) Displays the port type (FXS or FXO). [Authentication_PortType] User Name Defines the user name used for authenticating the port. CLI: user-name [Authentication_UserId] Password Defines the password used for authenticating the port. CLI: password [Authentication_UserPassword] Version 6.8 Mediant 1000B Gateway & SBC...
Page 462: Configuring Automatic Dialing
Mediant 1000B Gateway & SBC 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.
Page 463: Configuring Caller Display Information
To configure Caller display: Open the Caller Display Information page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Caller Display Information). Click Add; the following dialog box appears: Version 6.8 Mediant 1000B Gateway & SBC...
Page 464: Configuring Call Forward
Mediant 1000B Gateway & SBC Configure caller display per port according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Table 27-3: Caller Display Information Table Parameter Descriptions Parameter Description Index (Read-only) Displays the index number of the table record.
Page 465 [4] On Busy or No Answer = Forward incoming calls when the port is busy or when calls are not answered within the time specified in the 'No Reply Time' field.  [5] Don't Disturb = Immediately reject incoming calls. Version 6.8 Mediant 1000B Gateway & SBC...
Page 466: Configuring Caller Id Permissions
Mediant 1000B Gateway & SBC Parameter Description Forward Destination Defines the telephone number or URI (<number>@<IP address>) to CLI: destination where the call is forwarded. [FwdInfo_Destination] Note: If this parameter is configured with only a telephone number and a Proxy isn't used, this forwarded-to phone number must be specified in the Outbound IP Routing table (see ''Configuring Outbound IP Routing Table'' on page 383).
Page 467: Configuring Call Waiting
Open the Call Waiting page (Configuration tab > VoIP menu > GW and IP to IP > Analog Gateway > Call Waiting). Click Add; the following dialog box appears: Configure call waiting per port according to the parameters described in the table below. Version 6.8 Mediant 1000B Gateway & SBC...
Page 468: Rejecting Anonymous Calls
Mediant 1000B Gateway & SBC Click Submit, and then save ("burn") your settings to flash memory. Table 27-6: Call Waiting Table Parameter Descriptions Parameter Description Index Defines an index number for the new table record. [CallWaitingPerPort_Index] Note: Each table row must be configured with a unique index.
Page 469 CPT file at Index #9, you need to enter "1" as the Priority Index value and set the FirstCallWaitingToneID parameter to "8". The summation of these values is 9, i.e., index #9. The default is 0. Version 6.8 Mediant 1000B Gateway & SBC...
Page 470: Fxs/Fxo Coefficient Types
Mediant 1000B Gateway & SBC 27.12 FXS/FXO Coefficient Types The FXS Coefficient and FXO Coefficient types used by the device can be one of the following:  US line type of 600 ohm AC impedance and 40 V RMS ringing voltage for REN = 2 ...
Page 471: Fxo Operations For Ip-To-Tel Calls
 Time to Wait Before Dialing: Defines the time (in msec) between seizing the FXO line and starting to dial the digits. The ini file parameter WaitForDialTime is used to configure this operation. Version 6.8 Mediant 1000B Gateway & SBC...
Page 472: Two-Stage Dialing
Mediant 1000B Gateway & SBC Note: The ini file parameter IsWaitForDialTone must be disabled for this mode.  Answer Supervision: The Answer Supervision feature enables the FXO device to determine when a call is connected, by using one of the following methods: •...
Page 473: Fxo Operations For Tel-To-Ip Calls
Automatic dialing is defined using the Web interface's Automatic Dialing (TargetOfChannel ini file parameter) page, described in see ''Configuring Automatic Dialing'' on page 462. The SIP call flow diagram below illustrates Automatic Dialing. Version 6.8 Mediant 1000B Gateway & SBC...
Page 474: Collecting Digits Mode
Mediant 1000B Gateway & SBC 27.13.2.2 Collecting Digits Mode When automatic dialing is not defined, the device collects the digits. The SIP call flow diagram below illustrates the Collecting Digits Mode. Figure 27-10: Call Flow for Collecting Digits Mode 27.13.2.3...
Page 475: Call Termination On Fxo Devices
This method operates correctly only if silence suppression is not used.  Protocol-based termination of the call from the IP side Note: The implemented disconnect method must be supported by the CO or PBX. Version 6.8 Mediant 1000B Gateway & SBC...
Page 476: Call Termination Before Call Establishment
Mediant 1000B Gateway & SBC 27.13.3.2 Call Termination before Call Establishment The device supports the following call termination methods before a call is established:  Call termination upon receipt of SIP error response (in Automatic Dialing mode): By default, when the FXO device operates in Automatic Dialing mode, there is no method to inform the PBX if a Tel-to-IP call has failed (SIP error response - 4xx, 5xx or 6xx - is received).
Page 477: Dialing From Remote Extension (Phone At Fxs)
‘sent’ to the phone connected to the FXS device. Once the phone connected to the FXS device is off-hooked, the FXO device seizes the PBX line and the voice path is established between the phone and PBX. Version 6.8 Mediant 1000B Gateway & SBC...
Page 478: Message Waiting Indication For Remote Extensions
Mediant 1000B Gateway & SBC There is one-to-one mapping between PBX lines and FXS device ports. Each PBX line is routed to the same phone (connected to the FXS device). The call disconnects when the phone connected to the FXS device is on-hooked.
Page 479: Fxs Gateway Configuration
For the transfer to function in remote PBX extensions, Hold must be disabled at the FXS device (i.e., Enable Hold = 0) and hook-flash must be transferred from the FXS to the FXO (HookFlashOption = 4). Version 6.8 Mediant 1000B Gateway & SBC...
Page 480: Fxo Gateway Configuration
Mediant 1000B Gateway & SBC 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, assign the phone numbers 200 to 204 to the device’s FXO endpoints.
Page 481: Session Border Controller Application
Part VI Session Border Controller Application...
Page 483: Sbc Overview
Each leg has its own Route/Record Route set. • Modifies SIP To, From, and Request-URI host names (must be configured using the Message Manipulations table). • Generates a new SIP Call-ID header value (different between legs). Version 6.8 Mediant 1000B Gateway & SBC...
Page 484: Sip Network Definitions
Mediant 1000B Gateway & SBC • Changes the SIP Contact header to the device's own address. • Layer-3 topology hiding by modifying source IP address in the SIP IP header.  SIP normalization: The device supports SIP normalization, whereby the SBC application can overcome interoperability problems between SIP user agents.
Page 485 ''SBC Manipulations'' on page 540. SIP message manipulations: You can configure SIP message manipulation rules that can add, remove, and/or modify SIP headers and parameters. For more information, see ''Configuring SIP Message Manipulation'' on page 286. Version 6.8 Mediant 1000B Gateway & SBC...
Page 486: User Registration
Mediant 1000B Gateway & SBC The flowchart below illustrates the SBC process: Figure 28-1: Routing Process 28.3 User Registration To allow registrations to traverse the SBC, the device must be configured with at least one User-type IP Group. These IP Groups represent a group of user agents that share the following characteristics: ...
Page 487: Initial Registration Request Processing
SIP Contact headers). Database bindings are added upon successful registration responses. Database bindings are removed in the following cases:  Successful de-registration responses (REGISTER with Expires header that equals zero).  Registration failure responses. Version 6.8 Mediant 1000B Gateway & SBC...
Page 488: Routing Using Users Registration Database
Mediant 1000B Gateway & SBC  Timeout of the Expires header value (in scenarios where the user agent did not send a refresh registration request). Note: The device's Users Registration database poses the following restrictions: • The same contact cannot belong to more than one AOR.
Page 489: Registration Restriction Control
(e.g. IP address, port, coders, media types, and RTP mode). The media capabilities exchanged in an offer/answer transaction include the following:  Media types (Audio, Secure Audio, Video, Fax, Text...) Version 6.8 Mediant 1000B Gateway & SBC...
Page 490: Media Anchoring Without Transcoding (Transparent)
Mediant 1000B Gateway & SBC  IP addresses and ports of the media flow  Media flow mode (send receive, receive only, send only, inactive)  Media coders (coders and their characteristics used in each media flow)  Other (standard or proprietary) media and session characteristics...
Page 491: Media Anchoring With Transcoding
WAN leg the device adds another supported codec G.729 to the SDP, which is now offered to the WAN IP phone. The WAN IP phone chooses the Version 6.8 Mediant 1000B Gateway & SBC...
Page 492 Mediant 1000B Gateway & SBC extended codec (G.729) in its SDP answer to the device's WAN leg. Since this codec was not included in the original incoming offer, the device performs transcoding (between G.729 and G.711) between its two legs, allowing the streaming of media to occur.
Page 493: No Media Anchoring
The No Media Anchoring feature is enabled for all calls (regardless of SRD), using the global parameter, SBCDirectMedia. You can also enable No Media Anchoring per SRD (in the SRD table), whereby calls belonging to this same SRD (source and destination) are Version 6.8 Mediant 1000B Gateway & SBC...
Page 494: Transcoding Modes
Mediant 1000B Gateway & SBC handled as No Media Anchoring (direct media) calls. This occurs even if the global parameter is disabled. Notes: • No Media Anchoring can be used when the SBC does not do NAT traversal (for media) where all the users are in the same domain.
Page 495: Restricting Coders
Allowed coders list and the order of priority is first according to the Allowed coders list. Assuming that the outgoing leg also includes Allowed coders and/or Extension coders: The device performs the Allowed coders procedure (common coders) between the Version 6.8 Mediant 1000B Gateway & SBC...
Page 496 Mediant 1000B Gateway & SBC updated coder list and the outgoing leg's Allowed coders. The Extension coders procedure is performed before Allowed coders. Adding to the example, assume the following: • For the outgoing leg, the device selects the common coders G.711 and G.729 (explained in the example above).
Page 497: Prioritizing Coder List In Sdp Offer
28.4.9 Multiple RTP Media Streams per Call Session The device's SBC application supports multiple RTP media streams per SBC call session. Up to five different media types can be included in a session:  Audio (m=audio)  Video (m=video) Version 6.8 Mediant 1000B Gateway & SBC...
Page 498: Interworking Dtmf Methods
Mediant 1000B Gateway & SBC  Text (m=text)  Fax (m=image) Therefore, the device can provide transcoding of various attributes in the SDP offer/answer (e.g., codec, port, and packetization time) per media type. If the device is unable to perform transcoding (for example, does not support the codec), it relays the SBC dialog transparently.
Page 499: Limiting Sbc Call Duration
If the message is received without a SIP Authorization header, the device "challenges" the client by sending a SIP 401 or 407 response. The client then resends the request with an Authorization header (containing the user name and password). Version 6.8 Mediant 1000B Gateway & SBC...
Page 500: User Authentication Based On Radius
Mediant 1000B Gateway & SBC The device validates the SIP message according to the AuthNonceDuration, AuthChallengeMethod and AuthQOP parameters. ♦ If validation fails, the device rejects the message and sends a 403 (Forbidden) response to the client. ♦ If validation succeeds, the device verifies client identification. It checks that...
Page 501: Resultant Invite Traversing Device
INVITE handling. The special prefix can be used for specific routing rules for 3xx resultant INVITEs. The prefix is removed before the resultant INVITE is sent to the destination. Figure 28-6: SIP 3xx Response Handling The process of this feature is described using an example: Version 6.8 Mediant 1000B Gateway & SBC...
Page 502: Local Handling Of Sip 3Xx
Mediant 1000B Gateway & SBC The device receives the Redirect server's SIP 3xx response (e.g., Contact: <sip:User@IPPBX:5060;transport=tcp;param=a>;q=0.5). The device replaces the Contact header value with the special prefix and database key value as user part, and with the device's URL as host part (e.g., Contact: <sip:Prefix_Key_User@SBC:5070;transport=udp>;q=0.5).
Page 503: Interworking Sip Refer Messages
INVITE is sent through the SBC application.  IP Group Name: The device sets the host part in the REFER message to the name configured for the IP Group in the IP Group table. Version 6.8 Mediant 1000B Gateway & SBC...
Page 504: Interworking Sip Prack Messages
Mediant 1000B Gateway & SBC 28.8.4 Interworking SIP PRACK Messages The device supports interworking of SIP Provisional Response ACKnowledgement (PRACK) messages (18x). While some UAs may not support PRACK (RFC 3262) others may require it. The device can be configured to resolve this interoperable issue and enable sessions between such endpoints.
Page 505 Early Media RTP', 'SBC Remote Supports RFC 3960', and 'SBC Remote Can Play Ringback'. See the flowcharts below for the device's handling of such scenarios: Figure 28-7: SBC Early Media RTP 18x without SDP Figure 28-8: Early Media RTP - SIP 18x with SDP Version 6.8 Mediant 1000B Gateway & SBC...
Page 506: Interworking Sip Re-Invite Messages
Mediant 1000B Gateway & SBC 28.8.7 Interworking SIP re-INVITE Messages The device supports interworking of SIP re-INVITE messages. This enables communication between endpoints that generate re-INVITE requests and those that do not support the receipt of re-INVITEs. The device does not forward re-INVITE requests to IP Groups that do not support it.
Page 507: Interworking Call Hold
Below is an example of an XML body received from the BroadWorks server: <?xml version="1.0" encoding="utf-8"?> <BroadsoftDocument version="1.0" content="subscriberData"> <phoneNumbers> <phoneNumber>2403645317</phoneNumber> <phoneNumber>4482541321</phoneNumber> </phoneNumbers> <aliases> Version 6.8 Mediant 1000B Gateway & SBC...
Page 508: Broadsoft's Shared Phone Line Call Appearance For Sbc Survivability
Mediant 1000B Gateway & SBC <alias>sip:bob@broadsoft.com</alias> <alias>sip:rhughes@broadsoft.com</alias> </aliases> <extensions> <extension>5317</extension> <extension>1321</extension> </extensions> </BroadSoftDocument> 28.9.2 BroadSoft's Shared Phone Line Call Appearance for SBC 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 509: Call Survivability For Call Centers
The SBC can handle a sequence of up to five users, after which the session is timed out and the call is dropped. Figure 28-11: Normal Operation in Call Center Application Version 6.8 Mediant 1000B Gateway & SBC...
Page 510 Mediant 1000B Gateway & SBC Figure 28-12: Call Survivability for Call Center  To configure call survivability for a call center application: In the IP Group table (see ''Configuring IP Groups'' on page 261), add IP Groups for the following entities: •...
Page 511: Survivability Mode Display On Aastra Ip Phones
When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following XML body: Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> <LMIDocument version="1.0"> <LocalModeStatus> <LocalModeActive>true</LocalModeActive> Version 6.8 Mediant 1000B Gateway & SBC...
Page 512: Call Forking
Mediant 1000B Gateway & SBC <LocalModeDisplay>StandAlone Mode</LocalModeDisplay> </LocalModeStatus> </LMIDocument> 28.10 Call Forking This section describes various Call Forking features supported by the device. 28.10.1 Initiating SIP Call Forking The SBC device supports call forking of an incoming call to multiple SBC users (destinations).
Page 513: Call Forking-Based Ip-To-Ip Routing Rules
INVITE messages to all the specified destinations. It handles the multiple SIP dialogs until one of the calls is answered and then terminates the other SIP dialogs. For more information, see ''Configuring SBC IP-to-IP Routing Rules'' on page 530. Version 6.8 Mediant 1000B Gateway & SBC...
Page 514: Alternative Routing On Detection Of Failed Sip Response
Mediant 1000B Gateway & SBC 28.11 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 515: Sbc Configuration
A's phone rings, the application server notifies user B. User B can then press a pre-configured key sequence to answer the call. Version 6.8 Mediant 1000B Gateway & SBC...
Page 516 Mediant 1000B Gateway & SBC The NOTIFY message contains the XML body with call identifiers (call-id and tags). However, as the application server is located in the external network WAN and the SIP clients behind the device, the call dialog information sent by the application server reflects only the dialog between the device and itself;...
Page 517: Configuring Admission Control
SRD and its associated IP Groups are as follows:  SRD reserved call capacity: 40  IP Group ID 1 reserved call capacity: 10  IP Group ID 2 reserved call capacity: 20 Version 6.8 Mediant 1000B Gateway & SBC...
Page 518 Mediant 1000B Gateway & SBC In this setup, the SRD offers a shared pool for unreserved call capacity of 10 [i.e., 40 – (10 + 20)]. If IP Group ID 1 needs to handle 15 calls, it is guaranteed 10 calls and the remaining 5 is provided from the SRD's shared pool.
Page 519 (in milliseconds). ate] The default is 0 (i.e., unlimited rate). Note: The token bucket feature is per IP Group, SRD, SIP request type, and SIP request direction. Version 6.8 Mediant 1000B Gateway & SBC...
Page 520: Configuring Allowed Audio Coder Groups
Mediant 1000B Gateway & SBC Parameter Description Maximum Burst Defines the maximum number of tokens (SIP dialogs) that the bucket CLI: max-burst can hold. The device only accepts a SIP dialog if a token exists in the [SBCAdmissionControl_M bucket. Once the SIP dialog is accepted, a token is removed from the axBurst] bucket.
Page 521 The valid value for user-defined coders is a [AllowedCodersGroupX_Name] string of up to 25 characters (case-insensitive). For example, "HD.123" (without quotes). Note: Each coder type (e.g., G.729) can be configured only once per Allowed Coders Group. Version 6.8 Mediant 1000B Gateway & SBC...
Page 522: Configuring Allowed Video Coder Groups
Mediant 1000B Gateway & SBC 29.4 Configuring Allowed Video Coder Groups The Allowed Video Coders Group table lets you configure up to four Allowed Video Coders Groups. An Allowed Video Coders Group defines a list of video coders that can be used when forwarding video streams to a specific SIP entity.
Page 523 SIP Interface which is configured with this port (in the SIP Interface table). The device checks the SRD that is associated with this SIP Interface (in the SIP Interface table) and then classifies the SIP dialog with the first IP Group that is Version 6.8 Mediant 1000B Gateway & SBC...
Page 524 Mediant 1000B Gateway & SBC associated with this SRD. For example, if IP Groups 3 and 4 use the same SRD, the device classifies the call to IP Group 3. Note: If classification for a SIP request fails and the device is configured to reject unclassified calls, the device can send a specific SIP response code per SIP interface.
Page 525 Note: The SRDs are also associated with a port number as defined by the SIP Interface used by the SRD (see ''Configuring SIP Interfaces'' on page 258). Source IP Address Defines the source IP address (in dotted-decimal notation) CLI: src-ip-address Version 6.8 Mediant 1000B Gateway & SBC...
Page 526 Mediant 1000B Gateway & SBC Parameter Description [Classification_SrcAddress] of the incoming SIP dialog. The IP address can be configured using the following wildcards:  "x" wildcard: represents single digits. For example, 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.
Page 527: Classification Based On Uri Of Selected Header Example
P-Called-Party-ID: <sip:1111@10.33.38.1> User-Agent: Sip Message Generator V1.0.0.5 Content-Length: 0 In the Classification table, add the following classification rules: Source Username Destination Index Destination Host Source IP Group ID Prefix Username Prefix 1111 2000 10.10.10.10 Version 6.8 Mediant 1000B Gateway & SBC...
Page 528: Configuring Message Condition Rules
Mediant 1000B Gateway & SBC In the IP Group table, add the following IP Groups: Index Source URI Input Destination URI Input P-Called-Party-ID Route In this example, a match exists only for Classification Rule #1. This is because the source...
Page 529 Defines the Condition rule of the SIP message. CLI: condition The valid value is a string. [ConditionTable_Condition] Note: User and host parts must be enclosed in single quotes. Description Defines a brief description of the Condition rule. CLI: description [ConditionTable_Description] Version 6.8 Mediant 1000B Gateway & SBC...
Page 530: Configuring Sbc Ip-To-Ip Routing
Mediant 1000B Gateway & SBC 29.5.3 Configuring SBC IP-to-IP Routing The IP-to-IP Routing table lets you configure up to 500 SBC IP-to-IP routing rules. An IP- to-IP routing rule routes received SIP dialog messages (e.g., INVITE) to an IP destination.
Page 531 The call cost of the routing rule is done by assigning it a Cost Group. For configuring Cost Groups, see ''Least Cost Routing'' on page 226. If two routing rules Version 6.8 Mediant 1000B Gateway & SBC...
Page 532 Mediant 1000B Gateway & SBC have identical costs, then the rule appearing higher up in the table (i.e., first-matched rule) is used. If a selected route is unavailable, the device uses the next least-cost routing rule. However, even if a matched rule is not assigned a Cost Group, the device...
Page 533 URI (usually the From URI). You can use CLI: src-user-name-prefix special notations for denoting the prefix. To denote calls without a user part in the URI, use the $ sign. For available notations, see ''Dialing Plan Notation for Routing and Version 6.8 Mediant 1000B Gateway & SBC...
Page 534 Mediant 1000B Gateway & SBC Parameter Description Manipulation'' on page 713. The default is the asterisk (*) symbol (i.e., any prefix). If this rule is not required, leave this field empty. Source Host Defines the host part of the incoming SIP dialog's source [IP2IPRouting_SrcHost] URI (usually the From URI).
Page 535 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" denotes [PLAN1], "1" Version 6.8 Mediant 1000B Gateway & SBC...
Page 536 Mediant 1000B Gateway & SBC Parameter Description denotes [PLAN2], and so on.  [7] LDAP = LDAP-based routing.  [8] Gateway = The device routes the SBC call to the Tel side (Gateway call) using an IP-to-Tel routing rule in the Inbound IP Routing table (see Configuring Inbound IP Routing Table on page 392).
Page 537 [4] Group Member Consider Inputs = This routing rule is a member of the Forking routing rule. The incoming call is also forked to the destination of this routing rule only if the incoming call matches this rule's input characteristics. Version 6.8 Mediant 1000B Gateway & SBC...
Page 538: Configuring Sip Response Codes For Alternative Routing Reasons
Mediant 1000B Gateway & SBC Parameter Description Notes:  The alternative routing entry ([1] or [2]) must be defined in the next consecutive table entry index to the Route Row entry (i.e., directly below it). For example, if Index 4 is configured as a Route Row, Index 5 must be configured as the alternative route.
Page 539 Figure 29-10: Alternative Routing Reasons Table - Add Record Configure a SIP response code for alternative routing according to the parameters described in the table below. Click Submit, and then save ("burn") your settings to flash memory. Version 6.8 Mediant 1000B Gateway & SBC...
Page 540: Sbc Manipulations
Mediant 1000B Gateway & SBC Table 29-7: SBC Alternative Routing Reasons Table Parameter Descriptions Parameter Description Index Defines an index number for the new table [SBCAlternativeRoutingReasons_Index] record. Release Cause Defines a SIP response code for triggering the CLI: rel-cause device's alternative routing mechanism.
Page 541 The SIP message manipulations in the example above (contributing to typical topology hiding) are as follows:  Inbound source SIP URI user name from "7000" to "97000": From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe Version 6.8 Mediant 1000B Gateway & SBC...
Page 542: Configuring Ip-To-Ip Inbound Manipulations
Mediant 1000B Gateway & SBC  Source IP Group name (i.e., SIP URI host name) from "10.2.2.6" to "IP_PBX": From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1 =abe From: <sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe  Inbound destination SIP URI user name from "1000" to 9721000": INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0 To: <sip:1000@10.2.2.3;user=phone> INVITE sip:9721000@ITSP;user=phone;x=y;z=a SIP/2.0 To: <sip:9721000@ITSP;user=phone>...
Page 543 Note: Additional manipulation can only be done on a different SIP URI, source or destination, to the rule configured in the row above as configured by the 'Manipulated URI' parameter (see below). Version 6.8 Mediant 1000B Gateway & SBC...
Page 544 Mediant 1000B Gateway & SBC Parameter Description Manipulation Purpose Defines the purpose of the manipulation: CLI: purpose  [0] Normal = (Default) Inbound manipulations affect the [IPInboundManipulation_Manipulati routing input and source and/or destination number. onPurpose]  [1] Routing input only = Inbound manipulations affect the routing input only, retaining the original source and destination number.
Page 545: Configuring Ip-To-Ip Outbound Manipulations
Operation (Action) - if the incoming call matches the characteristics of the rule, the device manipulates the source or destination SIP URI user part or calling name of the SIP dialog (e.g., removes user-defined number of characters from the left of the SIP URI user part). Version 6.8 Mediant 1000B Gateway & SBC...
Page 546 Mediant 1000B Gateway & SBC Note: SIP URI host name (source and destination) manipulations can also be configured in the IP Group table. These manipulations are simply host name substitutions with the names configured for the source and destination IP Groups, respectively.
Page 547 Assigns a Message Condition rule as a matching CLI: message-condition characteristic. Message Condition rules define required SIP [IPOutboundManipulation_Messa message formats. For configuring Message Condition rules, geCondition] see ''Configuring Message Condition Rules'' on page 528. Version 6.8 Mediant 1000B Gateway & SBC...
Page 548 Mediant 1000B Gateway & SBC Parameter Description Request Type Defines the SIP request type to which the manipulation rule is CLI: request-type applied. [IPOutboundManipulation_Reques  [0] All = (Default) all SIP messages. tType]  [1] INVITE = All SIP messages except REGISTER and SUBSCRIBE.
Page 549 The device identifies an incoming user as restricted if one of the following exists:  From header user is anonymous.  P-Asserted-Identity and Privacy headers contain the value "id". Note: All restriction logic is performed after the user number has been manipulated. Version 6.8 Mediant 1000B Gateway & SBC...
Page 550 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 551: Cloud Resilience Package
Part VII Cloud Resilience Package...
Page 553: Crp Overview
Distributed PBX or unified communications deployments The CRP application is based on the functionality of the SBC application, providing branch offices with call routing and survivability support similar to AudioCodes' Stand-Alone Survivability (SAS) application. CRP is implemented in a network topology where the...
Page 554 Mediant 1000B Gateway & SBC Survivability Quality of Experience/Service Security registration process)  Survivability indication to IP phone  Call hold and retrieve  Call transfer (if the IP phone initiates REFER)  Basic Shared Line Appearance (excluding correct busy line indications) ...
Page 555: Crp Configuration
Open the Applications Enabling page (Configuration tab > VoIP menu > Applications Enabling > Applications Enabling). From the 'CRP Application' drop-down list, select Enable. Click Submit, and then reset the device with a burn-to-flash for your settings to take effect. Version 6.8 Mediant 1000B Gateway & SBC...
Page 556: Configuring Call Survivability Mode
Mediant 1000B Gateway & SBC 31.2 Configuring Call Survivability Mode The CRP can be configured to operate in one of the following call survivability modes:  Normal (Default): The CRP interworks between the branch users and the IP PBX located at headquarters. The CRP forwards all requests (such as for registration) from the branch users to the IP PBX, and routes the calls based on the IP-to-IP routing rules.
Page 557: Pre-Configured Ip Groups
The IP Groups can be edited, except for the fields listed above, which are read-only. • For accessing the IP Group table and for a description of its parameters, see ''Configuring IP Groups'' on page 261. Version 6.8 Mediant 1000B Gateway & SBC...
Page 558: Pre-Configured Ip-To-Ip Routing Rules
Mediant 1000B Gateway & SBC 31.4 Pre-Configured IP-to-IP Routing Rules For the CRP application, the IP-to-IP Routing table is pre-configured with IP-to-IP routing rules. These rules depend on the configured Call Survivability mode, as described in ''Configuring Call Survivability Mode'' on page 556.
Page 559: Emergency Mode
For the routing rule of Index 2, the destination is the source IP Group (i.e., from where the REGISTER message was received). Index 7 appears only if the CRPGatewayFallback parameter is enabled (see ''Configuring PSTN Fallback'' on page 560). Version 6.8 Mediant 1000B Gateway & SBC...
Page 560: Configuring Pstn Fallback
Mediant 1000B Gateway & SBC 31.5 Configuring PSTN Fallback You can enable the CRP to route emergency calls (or PSTN-intended calls) such as "911" from the Proxy server (IP Group 2) to the PSTN (IP Group 3). In addition, for calls from the...
Page 561: Maintenance
Part VIII Maintenance...
Page 565: Basic Maintenance
Description'' on page 42) to indicate that a device reset is required. • After you reset the device, the Web GUI is displayed in Basic view (see ''Displaying Navigation Tree in Basic and Full View'' on page 43). Version 6.8 Mediant 1000B Gateway & SBC...
Page 566: Remotely Resetting Device Using Sip Notify
Mediant 1000B Gateway & SBC  To reset the device: Open the Maintenance Actions page (see ''Basic Maintenance'' on page 565). Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: •...
Page 567: Locking And Unlocking The Device
Under the Misc Parameters group, set the 'SIP Remote Rest' parameter to Enable. Click Submit. Note: This SIP Event header value is proprietary to AudioCodes. 32.3 Locking and Unlocking the Device The Lock and Unlock option allows you to lock the device so that it doesn't accept any new calls and maintains only the current calls.
Page 568: Saving Configuration
Mediant 1000B Gateway & SBC Click the LOCK button; a confirmation message box appears requesting you to confirm device lock. Figure 32-4: Device Lock Confirmation Message Box Click OK to confirm device lock; if you set 'Graceful Option' to Yes, a lock icon is delayed and a window appears displaying the number of remaining calls and time.
Page 569: Disconnecting Active Calls
Session ID. This is done in the CLI using the following commands (from basic command mode):  Disconnects all active calls: # clear voip calls  Disconnects active calls belonging to a specified Session ID: # clear voip calls <Session ID> Version 6.8 Mediant 1000B Gateway & SBC...
Page 570 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 571: Replacing Modules
Click the Insert Module button; a message appears informing you that this may take a few seconds. When the message disappears, the module is inserted, which is indicated by the disappearance of the word 'Reserved' from the module's name. Version 6.8 Mediant 1000B Gateway & SBC...
Page 572 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 573: Resetting Channels
B-channel is restarted. • B-channel restart can only be done if the D-channel of the trunk to which it belongs is synchronized (Layer 2). • B-channel restart does not affect the B-channel's configuration. Version 6.8 Mediant 1000B Gateway & SBC...
Page 574 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 575: Software Upgrade
The Auxiliary files can be loaded to the device using one of the following methods:  Web interface.  TFTP: This is done by specifying the name of the Auxiliary file in an ini file (see Version 6.8 Mediant 1000B Gateway & SBC...
Page 576 Mediant 1000B Gateway & SBC Auxiliary and Configuration Files Parameters) and then loading the ini file to the device. The Auxiliary files listed in the ini file are then automatically loaded through TFTP during device startup. If the ini file does not contain a specific auxiliary file type, the device uses the last auxiliary file of that type that was stored on its non-volatile memory.
Page 577: Call Progress Tones File
AudioCodes DConvert utility. For a description on converting a CPT ini file into a binary dat file, refer to the DConvert Utility User's Guide.
Page 578 Mediant 1000B Gateway & SBC  [NUMBER OF CALL PROGRESS TONES]: Contains the following key: 'Number of Call Progress Tones' defining the number of Call Progress Tones that are defined in the file.  [CALL PROGRESS TONE #X]: containing the Xth tone definition, starting from 0 and not exceeding the number of Call Progress Tones less 1 defined in the first section (e.g., if 10 tones, then it is 0 to 9), using the following keys:...
Page 579: Distinctive Ringing
This cadence rings once during the ringing pattern. Otherwise, the cadence is interpreted as cyclic: it repeats for every ringing cycle.  Ring On Time: Specifies the duration of the ringing signal.  Ring Off Time: Specifies the silence period of the cadence. Version 6.8 Mediant 1000B Gateway & SBC...
Page 580 Mediant 1000B Gateway & SBC The Distinctive Ringing section of the ini file format contains the following strings:  [NUMBER OF DISTINCTIVE RINGING PATTERNS]: Contains the following key: • 'Number of Distinctive Ringing Patterns' defining the number of Distinctive Ringing signals that are defined in the file.
Page 581: Prerecorded Tones File
Up to 40 tones (totaling approximately 10 minutes) can be stored in a single PRT file on the device's flash memory. The prerecorded tones are prepared offline using third- party recording utilities and combined into a single file, using AudioCodes DConvert utility (refer to the document, DConvert Utility User's Guide for more information).
Page 582: Voice Prompts File
Mediant 1000B Gateway & SBC 36.1.3 Voice Prompts File The Voice Prompts (VP) file contains a set of voice prompts (or announcements) that can be played by the device during operation. The voice announcements are prepared offline using standard recording utilities and then combined into a single file using the DConvert utility.
Page 583: 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 575.
Page 584 • 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 585: Dial Plan Prefix Tags For Routing
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 575.
Page 586 Mediant 1000B Gateway & SBC For example, this feature is useful in deployments that need to handle hundreds of call routing scenarios such as for a large geographical area (a state in the US). Such an area could consist of hundreds of local area codes as well as codes for international calls. The local calls and international calls would need to be routed to different SIP trunks.
Page 587 (a state in the US). Such an area could consist of hundreds of local area codes as well as codes for international calls. The local calls and international calls would need to be routed to different SIP trunks. Thus, Version 6.8 Mediant 1000B Gateway & SBC...
Page 588 Mediant 1000B Gateway & SBC instead of configuring many routing rules for each call destination type, you can simply configure two routing rules, one with a unique prefix tag representing the different local area codes and the other with a prefix tag representing international calls.
Page 589: Obtaining Ip Destination From Dial Plan File
In the 'Destination Address' field, enter the required Dial Plan index using the following syntax: DialPlan<index> Where "DialPlan0" denotes [PLAN1] in the Dial Plan file, "DialPlan1" denotes [PLAN2], and so on. Version 6.8 Mediant 1000B Gateway & SBC...
Page 590: Modifying Isdn-To-Ip Calling Party Number
Mediant 1000B Gateway & SBC Note: The "DialPlan" string is case-sensitive. 36.1.5.5 Modifying ISDN-to-IP Calling Party Number The device can use the Dial Plan file to change the Calling Party Number value (source number) of the incoming ISDN call when sending to IP. For this feature, the Dial Plan file supports the following syntax: <ISDN Calling Party Number>,0,<new calling number>...
Page 591: User Information File
PBX user in the User Info table is used in the SIP From header. Note: If you have configured regular Tel-to-IP manipulation rules (see ''Configuring Source/Destination Number Manipulation'' on page 359), the device applies these rules before applying the mapping rules of the User Info table. Version 6.8 Mediant 1000B Gateway & SBC...
Page 592 Mediant 1000B Gateway & SBC • IP-to-IP Calls: Maps SIP From (calling number) and To (called number) of IP PBX extension numbers with "global" numbers. For example, if the device receives a call from IP PBX extension number 402 (calling / SIP From) that is destined to IP PBX extension number 403 (called / SIP To), the device changes both these numbers into their "global"...
Page 593 Defines the password for registering the user when [GWUserInfoTable_Password] authentication is necessary. The valid value is a string of up to 20 characters. Status (Read-only field) Displays the status of the user - "Registered" or "Not Registered". Version 6.8 Mediant 1000B Gateway & SBC...
Page 594 Mediant 1000B Gateway & SBC 36.1.6.2.2 Configuring GW User Info Table in CLI The GW User Info table can be configured in the CLI using the following commands:  To add and/or modify a user (example): # configure voip (config-voip)# sip-definition proxy-and-registration (sip-def-proxy-and-reg)# user-info gw-user-info <index, e.g.,...
Page 595: User Information File For Sbc User Database
Web interface - see ''Configuring SBC User Info Table in Web Interface'' on page  CLI - see Configuring SBC User Info Table in CLI on page  Loadable User Info file - see ''Configuring SBC User Info Table in Loadable Text File'' on page Version 6.8 Mediant 1000B Gateway & SBC...
Page 596 Mediant 1000B Gateway & SBC 36.1.6.3.1 Configuring SBC User Info Table in Web Interface The following procedure describes how to configure the SBC User Info table in the Web interface. Note: If any User Info file is loaded to the device, all previously configured entries are removed from the table in the Web interface and replaced with the entries from the loaded User Info file.
Page 597 This file can be created using any text-based program such as Notepad. This User Info file is the same file used for the GW User Info table. Thus, this file can include both Gateway and SBC user information. Version 6.8 Mediant 1000B Gateway & SBC...
Page 598: 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 the DConvert Utility User's Guide. Only one AMD Sensitivity file can be installed on the device.
Page 599: Software License Key
Before you can install a new Software License Key, you need to obtain a Software License Key file for your device with the required features from your AudioCodes representative. The Software License Key is an encrypted key in string format that is associated with the device's serial number ("S/N") and supplied in a text-based file.
Page 600: Installing The Software License Key
 CLI - see Installing Software License Key using CLI  AudioCodes EMS - refer to the EMS User’s Manual or EMS Product Description Note: When you install a new Software License Key, it is loaded to the device's non- volatile flash memory and overwrites the previously installed Software License Key.
Page 601: Installing Software License Key Using Cli
Open the Software License Key file and check that the "S/N" line appears. If it does not appear, contact AudioCodes. Verify that you have loaded the correct file. Open the file and ensure that the first line displays "[LicenseKeys]".
Page 602: Software Upgrade Wizard
If you upgraded your firmware (.cmp file) and the "SW version mismatch" message appears in the Syslog or Web interface, your Software License Key does not support the new .cmp file version. If this occurs, contact AudioCodes support for assistance.
Page 603 Select the file, and then click Open. Click Load File; the device begins to install the .cmp file. A progress bar displays the status of the loading process and a message informs you when file load successfully completes. Version 6.8 Mediant 1000B Gateway & SBC...
Page 604 Mediant 1000B Gateway & SBC Figure 36-7: Software Upgrade Wizard – CMP File Loading Progress Bar If you want to load additional files, skip this step and continue with the next step. If you only want to load a .cmp file, click Reset ;...
Page 605 'burns' the newly loaded files to flash memory and then resets. Note: Device reset may take a few minutes (even up to 30 minutes), depending on .cmp file version. Version 6.8 Mediant 1000B Gateway & SBC...
Page 606 Mediant 1000B Gateway & SBC When the device finishes the installation process and resets, the following wizard page is displayed, showing the installed software version and other files (ini file and auxiliary files) that you may also have installed: Figure 36-10: Software Upgrade Process Completed Successfully Click End Process to close the wizard;...
Page 607: Backing Up And Loading Configuration File
To save the ini file to a folder on your computer: Click the Save INI File button; the File Download dialog box appears. Click the Save button, navigate to the folder where you want to save the file, and then click Save. Version 6.8 Mediant 1000B Gateway & SBC...
Page 608 Mediant 1000B Gateway & SBC To load the ini file to the device: Click the Browse button, navigate to the folder where the file is located, select the file, and then click Open; the name and path of the file appear in the field beside the Browse button.
Page 609: Automatic Update Mechanism
To activate the DHCP process, perform a cold reset by pressing the device's hardware reset button. A soft reset using the Web interface doesn't trigger the DHCP process and if done, this parameter reverts to Disable. Version 6.8 Mediant 1000B Gateway & SBC...
Page 610: Provisioning From Http Server Using Dhcp Option 67
Mediant 1000B Gateway & SBC The following shows an example of a configuration file for a Linux DHCP server (dhcpd.conf). The devices are allocated temporary IP addresses in the range 10.31.4.53 to 10.31.4.75. TFTP is assumed to be on the same computer as the DHCP server (alternatively, the "next-server"...
Page 611: Provisioning From Tftp Server Using Dhcp Option 66
(master) ini file. This can be done using one of the following methods:  DHCP as described in 'DHCP-based Provisioning' on page or via TFTP at a staging warehouse. The URL is configured using the IniFileURL parameter. Version 6.8 Mediant 1000B Gateway & SBC...
Page 612: Ftp- Or Nfs-Based Provisioning
NFS v2/v3 is also supported. 37.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. As soon as a registered device contacts the EMS server through SNMP, the EMS server handles all required configuration automatically, upgrading software as needed.
Page 613: Http/S-Based Provisioning Using The Automatic Update Feature
The Automatic Update feature is done per file and configured by specifying the file name and URL address of the provisioning server where the file is located. For a description of the parameters used to configure URLs per file, see Automatic Update Parameters. Version 6.8 Mediant 1000B Gateway & SBC...
Page 614: 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 615: Access Authentication With Http Server
<MAC> - device's MAC address • <VER> - software version currently installed on the device, e.g., "6.80.200.001" • <CONF> - configuration version, as configured in the ini file parameter, INIFileVersion or CLI command, configuration-version Version 6.8 Mediant 1000B Gateway & SBC...
Page 616 Mediant 1000B Gateway & SBC The device automatically populates these tag variables with actual values in the sent header: User-Agent: Mozilla/4.0 (compatible; AudioCodes; <NAME>;<MAC>;<VER>;<CONF>). For example, if you set AupdHttpUserAgent = <NAME>;<VER>, the device sends the following User-Agent header: Mozilla/4.0 (compatible; AudioCodes; Mediant; 6.80.200.001)
Page 617: File Download Sequence
If you use the ResetNow parameter in an ini file for periodic automatic provisioning with non-HTTP (e.g., TFTP) and without CRC, the device resets after every file download. Therefore, use this parameter with caution and only if necessary for your deployment requirements. Version 6.8 Mediant 1000B Gateway & SBC...
Page 618: Cyclic Redundancy Check On Downloaded Configuration Files
Mediant 1000B Gateway & SBC Notes: • For ini file downloads, by default, parameters not included in the file are set to defaults. To retain the current settings of these parameters, set the SetDefaultOnINIFileProcess parameter to 0. • If you have configured one-time software file (.cmp) download (configured by the ini file parameter CmpFileURL or CLI command configure system >...
Page 619: Automatic Update Configuration Examples
Automatic Update is done every 24 hours (1440 minutes): ♦ ini File: AutoUpdateFrequency = 1440 ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# update-frequency 1440 Automatic Update of software file (.cmp): ♦ ini File: AutoCmpFileUrl = 'https://www.company.com/sw.cmp' Version 6.8 Mediant 1000B Gateway & SBC...
Page 620: Automatic Update From Nfs, Ftp And Http Servers
Mediant 1000B Gateway & SBC ♦ CLI: # configure system (config-system)# automatic update automatic-update)# auto-firmware 'http://www.company.com/sw.cmp' Automatic Update of Call Progress Tone file: ♦ ini File: CptFileURL = 'https://www.company.com/call_progress.dat' ♦ CLI: # configure system (config-system)# automatic update (automatic-update)# call-progress-tones 'http://www.company.com/call_progress.dat' Automatic Update of ini configuration file: ♦...
Page 621: Automatic Update For Mass Deployment
Device queries the provisioning server daily at 24:00 (midnight) for software, configuration and auxiliary files.  HTTP-based provisioning server at www.company.com for storing the files.  DNS server at 80.179.52.100 for resolving the domain name of the provisioning server. Version 6.8 Mediant 1000B Gateway & SBC...
Page 622 Mediant 1000B Gateway & SBC  To set up automatic provisioning for mass provisioning (example): Create an ini file named "master_configuration.ini" with the following settings: Common configuration for all devices: # Check for updates daily at 24:00 AutoUpdatePredefinedTime = '24:00' # CPT file update: CptFileURL = 'https://www.company.com/call_progress.dat'...
Page 623: Restoring Factory Defaults
At the prompt, type the password again, and then press Enter: # Password: Admin At the prompt, type the following to reset the device to default settings, and then press Enter: # write factory Version 6.8 Mediant 1000B Gateway & SBC...
Page 624: Restoring Defaults Using Hardware Reset Button
Mediant 1000B Gateway & SBC 38.2 Restoring Defaults using Hardware Reset Button The device's hardware reset pinhole button can be used to reset the device to default settings.  To restore default settings using the hardware reset pinhole button: ...
Page 625: Automatic Archiving Of Configuration File
(for whatever reason). To configure configuration-file archiving, use the following CLI command (root level):  Archiving to a remote server: # write-and-backup to <URL path with file name> Version 6.8 Mediant 1000B Gateway & SBC...
Page 626 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 627: Status, Performance Monitoring And Reporting
Part IX Status, Performance Monitoring and Reporting...
Page 629: System Status
To delete a loaded file:  Click the Delete button corresponding to the file that you want to delete. Deleting a file takes effect only after device reset (see ''Resetting the Device'' on page 565). Version 6.8 Mediant 1000B Gateway & SBC...
Page 630: Viewing Ethernet Port Information
Mediant 1000B Gateway & SBC 40.2 Viewing Ethernet Port Information The Ethernet Port Information page displays read-only information about the Ethernet Port Group connections.  To view Ethernet port information:  Open the Ethernet Port Information page: • Navigation menu tree: Status & Diagnostics tab > System Status menu >...
Page 631: Carrier-Grade Alarms
Open the Alarms History page (Status & Diagnostics tab > System Status menu > Carrier-Grade Alarms > Alarms History). For each alarm, the following information is provided:  Severity: severity level of the alarm: • Critical (red) • Major (range) Version 6.8 Mediant 1000B Gateway & SBC...
Page 632 Mediant 1000B Gateway & SBC • Minor (yellow) • Cleared (green)  Source: unit from which the alarm was raised  Description: brief explanation of the alarm  Date: date and time that the alarm was generated To view the next 20 alarms (if exist), click the Go to page button.
Page 633: Performance Monitoring
As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 1000B Gateway & SBC...
Page 634: Viewing Trunk Utilization
Mediant 1000B Gateway & SBC 42.2 Viewing Trunk Utilization The Trunk Utilization page provides an X-Y graph that displays the number of active channels per trunk over time. The x-axis indicates the time; the y-axis indicates the number of active trunk channels.
Page 635: Viewing Quality Of Experience
Dialog Failed Attempts: displays the failed call attempts. This includes the number of calls and subscribes which were successfully and abnormally terminated.  Dialog Termination Ratio: displays call termination by reason (e.g., due to no answer). Version 6.8 Mediant 1000B Gateway & SBC...
Page 636 Mediant 1000B Gateway & SBC  To view Quality of Experience: Open the Quality Of Experience page (Status & Diagnostics tab > Performance Monitoring menu > Quality Of Experience). Figure 42-3: Quality Of Experience Graph From the 'SRD/IpGroup' drop-down list, select whether you want to view QoE for an SRD or IP Group.
Page 637: Viewing Average Call Duration
As you increase the resolution, more data is displayed on the graph. The minimum resolution is about 30 seconds; the maximum resolution is about an hour. To pause the graph, click the Pause button; click Play to resume. Version 6.8 Mediant 1000B Gateway & SBC...
Page 638 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 639: Voip Status
Gray Disabled Green Active - OK Yellow RAI Alarm LOS / LOF Alarm Blue AIS Alarm Light Orange D-Channel Alarm Dark Orange NFAS Alarm Purple Lower Layer Down (DS3 physical layer is disabled) Version 6.8 Mediant 1000B Gateway & SBC...
Page 640: Viewing Analog Port Information
Mediant 1000B Gateway & SBC The status of the channels is depicted by color-coded icons, as described in the table below: Table 43-2: Description of Color-Coded Icons for Channel Status Icon Color Label Description Light blue Inactive Channel is configured, but currently has no calls...
Page 641: Viewing Nfas Groups And D-Channel Status
To view the status of the D-channels and NFAS groups:  Open the NFAS Group & D-Channel Status page (Status & Diagnostics tab > VoIP Status menu > NFAS Group & D-Channel Status). Figure 43-4: NFAS Group & D-Channel Status Page Version 6.8 Mediant 1000B Gateway & SBC...
Page 642: Viewing Active Ip Interfaces
Mediant 1000B Gateway & SBC 43.4 Viewing Active IP Interfaces The IP Interface Status page displays the device's active IP interfaces that are listed in the Interface table (see ''Configuring IP Network Interfaces'' on page 116).  To view active IP network interfaces: ...
Page 643: Viewing Static Routes Status
Performance Statistics). Figure 43-6: Basic Statistics Page The duration that the displayed statistics were collected is displayed in seconds above the table. To reset the performance statistics to zero, click the Reset Statistics button. Version 6.8 Mediant 1000B Gateway & SBC...
Page 644: Viewing Cdr History
Mediant 1000B Gateway & SBC 43.8 Viewing CDR History The CDR History table displays historical Call Detail Record (CDR) information of Gateway calls. CDR history information is stored on the device’s memory. The CDR History table can contain up to 4,096 CDRs. When a new CDR is generated, the device adds it to the top of the table and all previous entries are shifted one down in the table.
Page 645: Viewing Call Counters
Status menu > IP to Tel Calls Count or Tel to IP Calls Count); the figure below shows the IP to Tel Calls Count page. Figure 43-8: Calls Count Page The fields in this page are described in the following table: Table 43-4: Call Counters Description Counter Description Version 6.8 Mediant 1000B Gateway & SBC...
Page 646 Mediant 1000B Gateway & SBC Counter Description Number of Attempted Indicates the number of attempted calls. It is composed of established Calls and failed calls. The number of established calls is represented by the 'Number of Established Calls' counter. The number of failed calls is represented by the failed-call counters.
Page 647 15 minute period. Attempted Fax Calls Indicates the number of attempted fax calls. Counter Successful Fax Calls Indicates the number of successful fax calls. Counter Version 6.8 Mediant 1000B Gateway & SBC...
Page 648: Viewing Registered Users
Mediant 1000B Gateway & SBC 43.10 Viewing Registered Users You can view SAS and SBC users listed in the device's Users Registration database. The list shows each Address of Record (AOR) and its corresponding contact. The contact's registration status is also shown: ...
Page 649: Viewing Registration Status
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 353) or using the TrunkGroupSettings ini file parameter. Version 6.8 Mediant 1000B Gateway & SBC...
Page 650: Viewing Call Routing Status
Mediant 1000B Gateway & SBC 43.12 Viewing Call Routing Status The Call Routing Status page provides you with information on the current routing method used by the device. This information includes the IP address and FQDN (if used) of the Proxy server with which the device currently operates.
Page 651: Viewing Ip Connectivity
The status of the IP address' connectivity according to the method in the Status 'Connectivity Method' field.  OK = Remote side responds to periodic connectivity queries.  Lost = Remote side didn't respond for a short period.  Fail = Remote side doesn't respond. Version 6.8 Mediant 1000B Gateway & SBC...
Page 652 Mediant 1000B Gateway & SBC Column Name Description  Init = Connectivity queries not started (e.g., IP address not resolved).  Disable = The connectivity option is disabled, i.e., parameter 'Alt Routing Tel to IP Mode' (AltRoutingTel2IPMode ini) is set to 'None' or 'QoS'.
Page 653: Reporting Information To External Party
Remote Address (IP, Port & SSRC) Session Description Payload Type Payload Description Sample Rate Frame Duration Frame Octets Frames per Packets Packet Loss Concealment Silence Suppression State Jitter Buffer Jitter Buffer Adaptive Jitter Buffer Rate Jitter Buffer Nominal Version 6.8 Mediant 1000B Gateway & SBC...
Page 654 Mediant 1000B Gateway & SBC Group Metric Name Jitter Buffer Max Jitter Buffer Abs Max Packet Loss Network Packet Loss Rate Jitter Buffer Discard Rate Burst Loss Density Burst Gap Loss Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold...
Page 655 RTP/RTCP Settings). The RTCP XR parameters are listed under the RTCP XR Settings group: Figure 44-1: RTCP XR Parameters in RTP/RTCP Settings Page Under the RTCP XR Settings group, configure the following: • 'Enable RTCP XR' (VQMonEnable) - enables voice quality monitoring and RTCP Version 6.8 Mediant 1000B Gateway & SBC...
Page 656: Generating Call Detail Records
Mediant 1000B Gateway & SBC • 'Burst Threshold' (VQMonBurstHR) - defines the voice quality monitoring excessive burst alert threshold. • 'Delay Threshold' (VQMonDelayTHR) - defines the voice quality monitoring excessive delay alert threshold. • 'R-Value Delay Threshold' (VQMonEOCRValTHR) - defines the voice quality monitoring end of call low quality alert threshold.
Page 657: Configuring Cdr Reporting
Call originator (Orig CDR field) - indicates the call direction (caller)  Call duration (Durat CDR field) - call duration (elapsed time) from call connect  Call time is based on SetupTime, ConnectTime and ReleaseTime CDR fields Version 6.8 Mediant 1000B Gateway & SBC...
Page 658: Gwapp_Normal_Call_Clear
Mediant 1000B Gateway & SBC Table 44-2: CDR Fields for SBC Signaling CDR Field Name Description Format SBCReportType Report Type: String  "CALL_START"  "CALL_CONNECT"  "CALL_END"  "DIALOG_START"  "DIALOG_END" EPTyp Endpoint type: String  "SBC" SIPMethod SIP message type...
Page 659 String of up to 55 characters DirectMedia Direct media or traversing SBC: String  "yes"  "no" SIPTrmReason SIP call termination reason (BYE, String of up to 12 characters. CANCEL, or SIP error codes, e.g., 404) Version 6.8 Mediant 1000B Gateway & SBC...
Page 660: Cdr Fields For Sbc Media
Mediant 1000B Gateway & SBC CDR Field Name Description Format SipTermDesc Description of SIP termination reason: String of up to 26 characters  SIP Reason header, if exists, for example: SIP ;cause=200 ;text="Call completed elsewhere".  If no SIP Reason header exists, the...
Page 661: Cdr Fields For Gateway/Ip-To-Ip Application
The CDR fields for the Gateway / IP-to-IP application are listed in the table below. Table 44-4: CDR Fields for Gateway/IP-to-IP Application Field Name Description Report type: GWReportType  CALL_START  CALL_CONNECT  CALL_END Version 6.8 Mediant 1000B Gateway & SBC...
Page 662 Mediant 1000B Gateway & SBC Field Name Description Port number SessionId SIP session identifier Trunk Physical trunk number Note: This field is applicable only to the Gateway application. BChan Selected B-channel Note: This field is applicable only to the Gateway application.
Page 663 Note: This field is applicable only to the Gateway application. SrcHost Source host name SrcHostBeforeMap Source host name before manipulation Destination host name DstHost DstHostBeforeMap Destination host name before manipulation IP Group description LocalRtpIp Remote RTP IP address LocalRtpPort Local RTP port Version 6.8 Mediant 1000B Gateway & SBC...
Page 664 Mediant 1000B Gateway & SBC Field Name Description Amount 0-999999 Data is stored per call and sent in the syslog as follows:  currency-type: amount multiplier for currency charge (euro or usd)  recorded-units: for unit charge (1-999999) Mult 0,001-1000 (in steps of 10) (See explanation above.)
Page 665: Release Reasons In Cdr
CDR field TrmReason are listed below:  "REASON N/A"  "RELEASE_BECAUSE_NORMAL_CALL_DROP"  "RELEASE_BECAUSE_DESTINATION_UNREACHABLE"  "RELEASE_BECAUSE_DESTINATION_BUSY"  "RELEASE_BECAUSE_NOANSWER"  "RELEASE_BECAUSE_UNKNOWN_REASON"  "RELEASE_BECAUSE_REMOTE_CANCEL_CALL"  "RELEASE_BECAUSE_UNMATCHED_CAPABILITIES"  "RELEASE_BECAUSE_UNMATCHED_CREDENTIALS"  "RELEASE_BECAUSE_UNABLE_TO_HANDLE_REMOTE_REQUEST"  "RELEASE_BECAUSE_NO_CONFERENCE_RESOURCES_LEFT"  "RELEASE_BECAUSE_CONFERENCE_FULL"  "RELEASE_BECAUSE_VOICE_PROMPT_PLAY_ENDED"  "RELEASE_BECAUSE_VOICE_PROMPT_NOT_FOUND" Version 6.8 Mediant 1000B Gateway & SBC...
Page 666: Release_Because_Manual_Disc
Mediant 1000B Gateway & SBC  "RELEASE_BECAUSE_TRUNK_DISCONNECTED"  "RELEASE_BECAUSE_RSRC_PROBLEM"  "RELEASE_BECAUSE_MANUAL_DISC"  "RELEASE_BECAUSE_SILENCE_DISC"  "RELEASE_BECAUSE_RTP_CONN_BROKEN"  "RELEASE_BECAUSE_DISCONNECT_CODE"  "RELEASE_BECAUSE_GW_LOCKED"  "RELEASE_BECAUSE_NORTEL_XFER_SUCCESS"  "RELEASE_BECAUSE_FAIL"  "RELEASE_BECAUSE_FORWARD"  "RELEASE_BECAUSE_ANONYMOUS_SOURCE"  "RELEASE_BECAUSE_IP_PROFILE_CALL_LIMIT"  "GWAPP_UNASSIGNED_NUMBER"  "GWAPP_NO_ROUTE_TO_TRANSIT_NET"  "GWAPP_NO_ROUTE_TO_DESTINATION"  "GWAPP_CHANNEL_UNACCEPTABLE"  "GWAPP_CALL_AWARDED_AND "...
Page 667: Configuring Radius Accounting
Accounting server. The device can send the accounting messages to the RADIUS server upon call release, call connection and release, or call setup and release. For a list of the CDR attributes, see the table following the procedure below. Version 6.8 Mediant 1000B Gateway & SBC...
Page 668 Mediant 1000B Gateway & SBC  To configure RADIUS accounting: Open the RADIUS Parameters page (Configuration tab > VoIP menu > SIP Definitions > RADIUS Parameters Settings). Figure 44-3: RADIUS Accounting Parameters Page Set the 'Enable RADIUS Access Control' parameter to Enable.
Page 669 Number of octets sent Numeric - Stop Acc octets for that call duration (Gateway call) acct-session- A unique accounting String 34832 Start Acc identifier - match start Stop Acc & stop Version 6.8 Mediant 1000B Gateway & SBC...
Page 670 Mediant 1000B Gateway & SBC Vendor Attribute Attribute Specific Value Purpose Example Number Name Attribute Format (VSA) No. acct-session- For how many Numeric - Stop Acc time seconds the user received the service acct-input- Number of packets Numeric - Stop Acc...
Page 671: Event Notification Using X-Detect Header
There are additional three SIT tones that are detected as one of the above SIT tones:  The NC* SIT tone is detected as NC  The RO* SIT tone is detected as RO  The IO* SIT tone is detected as VC Version 6.8 Mediant 1000B Gateway & SBC...
Page 672 Mediant 1000B Gateway & SBC The device can map these SIT tones to a Q.850 cause and then map them to SIP 5xx/4xx responses, using parameters SITQ850Cause, SITQ850CauseForNC, SITQ850CauseForIC, SITQ850CauseForVC, and SITQ850CauseForRO. Table 44-7: Special Information Tones (SITs) Reported by the device...
Page 673 INFO sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=1c25298 To: <sip:101@10.33.2.53;user=phone> Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: <sip:100@10.33.2.53> X- Detect: Response=CPT,FAX Content-Type: Application/X-Detect Content-Length: xxx Type = CPT Subtype = SIT Version 6.8 Mediant 1000B Gateway & SBC...
Page 674: Querying Device Channel Resources Using Sip Options
Mediant 1000B Gateway & SBC 44.5 Querying Device Channel Resources using SIP OPTIONS The device reports its maximum and available channel resources in SIP 200 OK responses upon receipt of SIP OPTIONS messages. The device sends this information in the SIP X- Resources header with the following parameters: ...
Page 675: Diagnostics
Part X Diagnostics...
Page 677: Syslog And Debug Recordings
For example, in the below Syslog message, messages 238 through 300 were not received. In other words, 63 Syslog messages were lost (the sequential Version 6.8 Mediant 1000B Gateway & SBC...
Page 678: Event Representation In Syslog Messages
Mediant 1000B Gateway & SBC Message Item Description numbers are indicated below in bold font): 18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235][SID:1034099026] (lgr_psbrdex)(619) recv <-- DIGIT(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1 [File: Line:-1] 18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236][SID:1034099026] (lgr_flow)(620) #0:DIGIT_EV [File: Line:-1] 18:38:14.
Page 679 Counts the number of BFI Frames Received From The Host No Available Release Descriptor RTP Reorder Unknown RTP Payload Type RTP SSRC Error Unrecognized Fax Relay Command Invalid Accumulated Packets Counter Invalid Channel ID Version 6.8 Mediant 1000B Gateway & SBC...
Page 680: Identifying Audiocodes Syslog Messages Using Facility Levels
Unknown Aggregation Payload Type Invalid Routing Flag Received 45.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 681: Snmp Alarms In Syslog Messages
For viewing Syslog messages in the Web interface, see ''Viewing Syslog Messages'' on page 688. • For a detailed description on the Syslog parameters, see ''Syslog, CDR and Debug Parameters'' on page 741. Version 6.8 Mediant 1000B Gateway & SBC...
Page 682 Mediant 1000B Gateway & SBC  To enable Syslog: Open the Syslog Settings page (Configuration tab > System menu > Syslog Settings). Figure 45-1: Syslog Settings Page Enable the Syslog feature by setting 'Enable Syslog' to Enable. Define the Syslog server using the 'Syslog Server IP Address' and 'Syslog Server Port' parameters.
Page 683: Configuring Web Operations To Report To Syslog
Debug recording is also useful for recording network traffic in environments where hub or port mirroring is unavailable and for recording internal traffic between two endpoints on the same device. Note: Debug recording is collected only on the device's OAMP interface. Version 6.8 Mediant 1000B Gateway & SBC...
Page 684: Filtering Syslog Messages And Debug Recordings
Mediant 1000B Gateway & SBC  To configure and activate debug recording: Open the Logging Settings page (Configuration tab > System menu > Logging > Logging Settings). Figure 45-3: Logging Settings Page Configure the debug capturing server using the 'Debug Recording Destination IP' and 'Debug Recording Destination Port' parameters.
Page 685  [13] IP Trace = Filters according to a specified IP network trace wireshark-like expression. For a detailed description on configuring IP traces, see ''Filtering IP Network Traces'' on page 687. Version 6.8 Mediant 1000B Gateway & SBC...
Page 686 Mediant 1000B Gateway & SBC Parameter Description Value Defines the value of the selected filtering type in the 'Filter Type' CLI: value parameter. [LoggingFilters_Value] The value can be the following:  A single value  A range, using a hyphen "-" between the two values, e.g., "1-3"...
Page 687: Filtering Ip Network Traces
== 1.1.1.1 and ip.dst == 3.3.3.3 ip.src == 2.2.2.2 and ip.dst == 3.3.3.3 Note: If the 'Value' field is not defined, the device records all IP traffic types. Version 6.8 Mediant 1000B Gateway & SBC...
Page 688: Viewing Syslog Messages
Syslog server. • You can select the Syslog messages in this page, and copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to AudioCodes Technical Support for diagnosis and troubleshooting. ...
Page 689: Collecting Debug Recording Messages
User's Manual 45. Syslog and Debug Recordings 45.7 Collecting Debug Recording Messages To collect debug recording packets, use the open source program Wireshark. AudioCodes proprietary plug-in files for Wireshark are required. Notes: • The default debug recording port is 925. You can change the port in Wireshark (Edit menu >...
Page 690 Mediant 1000B Gateway & SBC The device adds the header "AUDIOCODES DEBUG RECORDING" to each debug recording message, as shown below: For ISDN trace messages, the additional header, "NetBricks Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below:...
Page 691 Calling party number: '201' Called party number: '102' Sending complete For CAS trace messages, the additional header "CAS Trace" is added below the "AUDIOCODES DEBUG RECORDING" header, as shown in the example below: AUDIOCODES DEBUG RECORDING CAS Trace Timer: 1145504439...
Page 692: Debug Capturing On Physical Voip Interfaces
Mediant 1000B Gateway & SBC 45.8 Debug Capturing on Physical VoIP Interfaces You can capture traffic on the device's physical (Ethernet LAN) VoIP interfaces (Layer-2 VLAN tagged packets). The captured traffic can be saved in a PCAP-format file (suitable for Wireshark) to a TFTP (default) or an FTP server. The generated PCAP file is in the Extensible Record Format (ERF).
Page 693: Self-Testing
Startup Test (automatic): This hardware test has minor impact in real-time. While this test is executed, the regular operation of the device is disabled. If an error is detected, an error message is sent to the Syslog. Version 6.8 Mediant 1000B Gateway & SBC...
Page 694 Mediant 1000B Gateway & SBC This page is intentionally left blank. User's Manual Document #: LTRT-27034...
Page 695: Creating Core Dump And Debug Files Upon Device Crash
The core dump can either be included in or excluded from the debug file, or alternatively, sent separately to a TFTP server. The files can then be sent to AudioCodes support team for troubleshooting. ...
Page 696 Mediant 1000B Gateway & SBC The following procedure describes how to retrieve the debug file from the device in the Web interface.  To save the debug file from the device:  In the Debug Utilities page, click the Save Debug File button.
Page 697: Analog Line Testing
Line polarity (0 = Positive; 1 = Negative)  Message Waiting Indication (0 = Off; 1 = On) Note: Use the Analog Line testing mechanism only for monitoring and never when there are calls in progress. Version 6.8 Mediant 1000B Gateway & SBC...
Page 698: Fxs Line Testing
Mediant 1000B Gateway & SBC 48.2 FXS Line Testing The device can test the telephone lines connected to its FXS ports, using the SNMP acAnalogFxsLineTestTable table. These tests provide various line measurements. In addition to these 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 and overheating of the FXS ports.
Page 699: Testing Sip Signaling Calls
The following procedure describes how to configure test calls in the Web interface. You can also configure this using the table ini file parameter, Test_Call or CLI command, configure system > test-call > test-call-table. Version 6.8 Mediant 1000B Gateway & SBC...
Page 700 Mediant 1000B Gateway & SBC  To configure a test call: Open the Test Call Table page (Configuration tab > System menu > Test Call > Test Call Table). Click Add; the following dialog box appears: Figure 49-1: General Tab of Test Call Table Configure a test call according to the parameters described in the table below.
Page 701 'Destination Address' or 'IP [Test_Call_AutoRegister] Group ID' parameter settings (see above).  [0] Disable (default)  [1] Enable Username Defines the authentication username. CLI: user-name By default, no username is defined. [Test_Call_UserName] Version 6.8 Mediant 1000B Gateway & SBC...
Page 702 Mediant 1000B Gateway & SBC Parameter Description Password Defines the authentication password. CLI: password By default, no password is defined. [Test_Call_Password] Test Settings Tab Call Party Defines whether the test endpoint is the initiator or receiving side CLI: call-party of the test call.
Page 703: Starting And Stopping Test Calls
"Done": test call has been successfully completed (or was prematurely stopped by clicking the Drop Call command) A more detailed description of this field is displayed below the table when you click the Show/Hide button (see ''Viewing Test Call Statistics'' on page 704). Version 6.8 Mediant 1000B Gateway & SBC...
Page 704: Viewing Test Call Statistics
Mediant 1000B Gateway & SBC 49.3 Viewing Test Call Statistics In addition to viewing a brief status description of the test call in the 'Test Status' field (as described in ''Starting, Stopping and Restarting Test Calls'' on page 703), you can also view a more detailed status description which includes test call statistics.
Page 705: Configuring Dtmf Tones For Test Calls
Open the Test Call Settings page (Configuration tab > System menu > Test Call > Test Call Settings). Figure 49-3: DTMF in Test Call Settings Page In the 'Test Call DTMF String' field, enter the DTMF string (up to 15 digits). Click Submit. Version 6.8 Mediant 1000B Gateway & SBC...
Page 706: Configuring Basic Test Call
Mediant 1000B Gateway & SBC 49.5 Configuring Basic Test Call The Basic Test Call feature tests incoming Gateway calls from a remote SIP endpoint to a simulated test endpoint on the device. The only required configuration is to assign a prefix number (test call ID) to the simulated endpoint.
Page 707: Configuring Sbc Test Call With External Proxy
The device receives the call from the proxy server. As the 'Test Call ID' parameter is set to "101", the device identifies the incoming call as a test call and sends it directly to the simulated test endpoint "101". Version 6.8 Mediant 1000B Gateway & SBC...
Page 708: Test Call Configuration Examples
Mediant 1000B Gateway & SBC  To configure SBC call testing: Configure the test call parameters (for a full description, see ''SIP Test Call Parameters'' on page 740): Open the Test Call Settings page (Configuration tab > System menu > Test Call >...
Page 709 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 710 Mediant 1000B Gateway & 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 711: Appendix
Part XI Appendix...
Page 713: Dialing Plan Notation For Routing And Manipulation
03(100): for any number that starts with 03 and ends with 100.  [100-199](100,101,105): for a number that starts with 100 to 199 and ends with 100, 101 or 105.  03(abc): for any number that starts with 03 and ends with abc. Version 6.8 Mediant 1000B Gateway & SBC...
Page 714 Mediant 1000B Gateway & SBC Notation Description  03(5xx): for any number that starts with 03 and ends with 5xx.  03(400,401,405): for any number that starts with 03 and ends with 400 or 401 or 405. Notes:  The value n must be less than the value m.
Page 715: Configuration Parameters Reference
Web: Allow WAN access to Enables WAN access to the management interface through SSH.  [0] Disable (default) CLI: wan-ssh-allow  [1] Enable [AllowWanSSH] Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 1000B Gateway & SBC...
Page 716: Web Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Web and Telnet This table configures up to ten IP addresses that are permitted to Access List Table access the device's Web interface and Telnet interfaces. Access from EMS: Web Access an undefined IP address is denied. When no IP addresses are defined Addresses in this table, this security feature is inactive (i.e., the device can be...
Page 717 'Web User Accounts', 'Certificates', 'Regional Settings', 'Maintenance Actions' and all file-loading pages ('Load Auxiliary Files', 'Software Upgrade Wizard', and 'Configuration File'). Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 1000B Gateway & SBC...
Page 718 Mediant 1000B Gateway & SBC Parameter Description [ResetWebPassword] Resets the username and password of the primary ("Admin") and secondary ("User") accounts to their default settings ("Admin" and "Admin" respectively), and deletes all other users that may have been configured. ...
Page 719: Telnet Parameters
Table 51-4: ini File Parameters Parameter Description [INIPasswordsDisplayType] Defines how passwords are displayed in the ini file.  [0] Disable (default) = Passwords are obscured ("encoded"). The passwords are displayed in the following syntax: $1$<obscured Version 6.8 Mediant 1000B Gateway & SBC...
Page 720: Snmp Parameters
[SendKeepAliveTrap] Enables the device to send NAT keep-alive traps to the port of the SNMP network management station (e.g., AudioCodes EMS). This is used for NAT traversal, and allows SNMP communication with AudioCodes EMS management platform, located in the WAN, when the device is located behind NAT.
Page 721 Defines the port number of the remote SNMP Manager. The device EMS: Port sends SNMP traps to this port. CLI: port The valid SNMP trap port range is 100 to 4000. The default port is Version 6.8 Mediant 1000B Gateway & SBC...
Page 722 Mediant 1000B Gateway & SBC Parameter Description [SNMPManagerTrapPort_x] 162. Web: Trap Enable Enables the sending of traps to the corresponding SNMP manager. CLI: send-trap  [0] Disable = Sending is disabled. [SNMPManagerTrapSendingE  [1] Enable = (Default) Sending is enabled.
Page 723: Serial Parameters
Note: For this parameter to take effect, a device reset is required. EMS: Flow Control Defines the RS-232 flow control. [SerialFlowControl]  [0] = (Default) None  [1] = Hardware Note: For this parameter to take effect, a device reset is required. Version 6.8 Mediant 1000B Gateway & SBC...
Page 724: Auxiliary And Configuration File Name Parameters
Mediant 1000B Gateway & SBC 51.1.7 Auxiliary and Configuration File Name Parameters The configuration files (i.e., auxiliary files) can be loaded to the device using the Web interface. For loading these files using the ini file, you need to configure these files in the ini file and configured whether they must be stored in the non-volatile memory.
Page 725: Automatic Update Parameters
Description Web: Dial Plan File Defines the name (and path) of the Dial Plan file. This file should be EMS: Dial Plan File Name created using AudioCodes DConvert utility (refer to DConvert Utility [DialPlanFileName] User's Guide). [UserInfoFileName] Defines the name (and path) of the file containing the User Information data.
Page 726 Mediant 1000B Gateway & SBC Parameter Description The valid value is an IP address in dotted-decimal notation or an FQDN. [AUPDDigestUsername] Defines the username for digest (MD5 cryptographic hashing) access authentication with the HTTP server used for the Automatic Update feature.
Page 727 Note: The maximum length of the URL address is 99 characters. CLI: voice-prompts Defines the name of the Voice Prompts file and the path to the [VpFileURL] server (IP address or FQDN) on which it is located. For example: http://server_name/file, https://server_name/file Version 6.8 Mediant 1000B Gateway & SBC...
Page 728: Networking Parameters
Mediant 1000B Gateway & SBC Parameter Description Note: The maximum length of the URL address is 99 characters. CLI: cas-table Defines the name of the CAS file and the path to the server (IP [CasFileURL] address or FQDN) on which it is located. For example: http://server_name/file, https://server_name/file.
Page 729: Multiple Voip Network Interfaces And Vlan Parameters
Parameter Description Web: Send ICMP Enables sending of ICMP Unreachable messages. Unreachable Messages  [0] Enable = (Default) Device sends these messages. [DisableICMPUnreachable]  [1] Disable = Device does not send these messages. Version 6.8 Mediant 1000B Gateway & SBC...
Page 730: Open Solution Network (Osn) Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Send and Receive Enables sending and receiving of ICMP Redirect messages. ICMP Redirect Messages  [0] Enable = (Default) Device sends and accepts these messages. [DisableICMPRedirects]  [1] Disable = Device rejects these messages and also does not send them.
Page 731: Nat And Stun Parameters
The Network Address Translation (NAT) parameters are described in the table below. Table 51-14: NAT Parameters Parameter Description NAT Parameters Web/EMS: NAT Mode Enables the NAT feature for media when the device communicates Version 6.8 Mediant 1000B Gateway & SBC...
Page 732 Mediant 1000B Gateway & SBC Parameter Description CLI: disable-NAT-traversal with UAs located behind NAT. [NATMode]  [0] Auto-Detect = NAT is performed only if necessary. If the UA is identified as being located behind NAT, the device sends the media packets to the public IP address:port obtained from the source address of the first media packet received from the UA.
Page 733: Nfs 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 734: Dns Parameters
Mediant 1000B Gateway & SBC 51.2.8 DNS Parameters The Domain name System (DNS) parameters are described in the table below. Table 51-16: DNS Parameters Parameter Description Internal DNS Table Web: Internal DNS Table This table parameter defines the internal DNS table for resolving host EMS: DNS Information names into IP addresses.
Page 735 Web: DHCP Vendor Defines Vendor Class Identifier (VCI) names (DHCP Class table Option 60) for the device's DHCP server. Only if the CLI: configure voip > DHCPDiscover request message, received from the DHCP Version 6.8 Mediant 1000B Gateway & SBC...
Page 736: Ntp And Daylight Saving Time Parameters
Mediant 1000B Gateway & SBC Parameter Description dhcp vendor-class client, contains this value does the device provide DHCP [DhcpVendorClass] services. The format of the ini file table parameter is as follows: [ DhcpVendorClass ] FORMAT DhcpVendorClass_Index = DhcpVendorClass_DhcpServerIndex, DhcpVendorClass_VendorClassId; [ \DhcpVendorClass ] For a detailed description of this table, see Configuring the Vendor Class Identifier on page 193.
Page 737 May 1 at 8 A.M.  Day of month - mm:day/wk:hh:mm, where:  mm denotes month (e.g., 04)  day denotes day of week (e.g., FRI)  wk denotes week of the month (e.g., 03) Version 6.8 Mediant 1000B Gateway & SBC...
Page 738: Debugging And Diagnostics Parameters
Mediant 1000B Gateway & SBC Parameter Description  hh denotes hour (e.g., 23)  mm denotes minutes (e.g., 10) For example, "04:FRI/03:23:00" denotes Friday, the third week of April, at 11 P.M. The week field can be 1-5, where 5 denotes the last occurrence of the specified day in the specified month.
Page 739 Power Supply modules is removed from the chassis or not operating correctly (failure).  [1] = (Default) Disable - no alarm is sent.  [2] = Enable - an alarm is sent. Version 6.8 Mediant 1000B Gateway & SBC...
Page 740: Sip Test Call Parameters
Mediant 1000B Gateway & SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  If this parameter is set to [2], for this feature to be functional, both Main and Redundant Power Supply modules must be housed in the chassis.
Page 741: Syslog, Cdr And Debug Parameters
[ \Test_Call ] For a description of this table, see ''Configuring Test Call Endpoints'' on page 699. 51.3.3 Syslog, CDR and Debug Parameters The Syslog, CDR and debug parameters are described in the table below. Version 6.8 Mediant 1000B Gateway & SBC...
Page 742 Mediant 1000B Gateway & SBC Table 51-21: Syslog, CDR and Debug Parameters Parameter Description Web: Enable Syslog Determines whether the device sends logs and error messages (e.g., EMS: Syslog enable CDRs) generated by the device to a Syslog server. CLI: syslog ...
Page 743 Note: When debug reporting is enabled, in order to view Syslog messages with Wireshark, you need to install AudioCodes Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are decoded as "AC SYSLOG" and are displayed using the 'acsyslog' filter instead of the regular 'syslog' filter.
Page 744 Mediant 1000B Gateway & SBC Parameter Description [SyslogCpuProtection] were required for the previous debug-level functionality. When sufficient CPU resources become available again, the device increases the debug level. The threshold is configured by the 'Debug Level High Threshold' parameter (see below).
Page 745 CLI: configure system > logging > dbg-rec-dest-ip [DebugRecordingDestIP] Web: Debug Recording Defines the UDP port of the server for capturing debug recording. Destination Port The default is 925. CLI: configure system > logging > dbg-rec-dest-port [DebugRecordingDestPort] Version 6.8 Mediant 1000B Gateway & SBC...
Page 746: Resource Allocation Indication Parameters
Mediant 1000B Gateway & SBC Parameter Description Debug Recording Status Activates or de-activates debug recording. CLI: configure system >  [0] Stop (default) logging > dbg-rec-status  [1] Start [DebugRecordingStatus] Web: Enable Core Dump Enables the automatic generation of a Core Dump file upon a device [EnableCoreDump] crash.
Page 747 The range is 0 to 100%. The default is 90%. Defines the time interval (in seconds) that the device periodically checks [RAILoopTime] call resource availability. The valid range is 1 to 200. The default is 10. Version 6.8 Mediant 1000B Gateway & SBC...
Page 748: Security Parameters
Mediant 1000B Gateway & SBC 51.4 Security Parameters This subsection describes the device's security parameters. 51.4.1 General Security Parameters The general security parameters are described in the table below. Table 51-23: General Security Parameters Parameter Description Firewall Table Web/EMS: Internal...
Page 749: Srtp Parameters
The Secure Real-Time Transport Protocol (SRTP) parameters are described in the table below. Table 51-25: SRTP Parameters Parameter Description Web: Media Security Enables Secure Real-Time Transport Protocol (SRTP). EMS: Enable Media Security  [0] Disable (default) CLI: media-security-enable  [1] Enable Version 6.8 Mediant 1000B Gateway & SBC...
Page 750 Mediant 1000B Gateway & SBC Parameter Description [EnableMediaSecurity] Note:  For this parameter to take effect, a device reset is required. Web/EMS: Media Security Global parameter that defines the handling of SRTP (when the Behavior EnableMediaSecurity parameter is set to 1). You can also...
Page 751: Tls Parameters
The interval range is 0 to 1,500 minutes. The default is 0 (i.e., CLI: tls-re-hndshk-int no TLS Re-Handshake). [TLSReHandshakeInterval] Web: TLS Mutual Authentication Defines the device's mode of operation regarding mutual EMS: SIPS Require Client authentication and certificate verification for TLS connections. Version 6.8 Mediant 1000B Gateway & SBC...
Page 752 Mediant 1000B Gateway & SBC Parameter Description  Certificate [0] Disable = (Default) [SIPSRequireClientCertificate]  Device acts as a client: Verification of the server’s certificate depends on the VerifyServerCertificate parameter.  Device acts as a server: The device does not request the client certificate.
Page 753: Ssh Parameters
Defines the RSA public key for strong authentication for logging in CLI: ssh-admin-key to the SSH interface (if enabled). [SSHAdminKey] The value should be a base64-encoded string. The value can be a maximum length of 511 characters. Version 6.8 Mediant 1000B Gateway & SBC...
Page 754: Ids Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Require Public Key Enables RSA public keys for SSH. EMS: EMS: SSH Require Public  [0] = (Default) RSA public keys are optional if a value is configured for the parameter SSHAdminKey.
Page 755 The format of the ini file parameter is: [ IDSMatch ] FORMAT IDSMatch_Index = IDSMatch_SIPInterface, IDSMatch_ProxySet, IDSMatch_Subnet, IDSMatch_Policy; [ \IDSMatch ] For a detailed description of this table, see ''Assigning IDS Policies'' on page 153. Version 6.8 Mediant 1000B Gateway & SBC...
Page 756: Quality Of Experience Parameters
The Quality of Experience (QoE) parameters are described in the table below. Table 51-29: Quality of Experience Parameters Parameter Description SEM Parameters Web: Server IP Defines the IP address of AudioCodes primary Session Experience CLI: configure voip/qoe Manager (SEM) server to where the quality experience reports are configuration/server-ip sent. [QOEServerIP] Note: For this parameter to take effect, a device reset is required.
Page 757 The format of the ini file table parameter is as follows: CLI: configure voip/qoe [MediaEnhancementRules] media-enhancement-rules FORMAT MediaEnhancementRules_Index = [MediaEnhancementRules] MediaEnhancementRules_MediaEnhancementProfile, MediaEnhancementRules_RuleIndex, MediaEnhancementRules_Trigger, MediaEnhancementRules_Color, MediaEnhancementRules_ActionRule, MediaEnhancementRules_ActionValue; [\MediaEnhancementRules] For a detailed description of this table, see ''Configuring Media Enhancement Profiles'' on page 247. Version 6.8 Mediant 1000B Gateway & SBC...
Page 758: Control Network Parameters
Mediant 1000B Gateway & SBC 51.6 Control Network Parameters 51.6.1 IP Group, Proxy, Registration and Authentication Parameters The proxy server, registration and authentication SIP parameters are described in the table below. Table 51-30: Proxy, Registration and Authentication SIP Parameters Parameter...
Page 759 Group (i.e., proxy server), it uses the string configured by the ProxyName parameter as the host name in the REGISTER's Request-URI and uses the string configured by the IP Group table parameter, SIPGroupName as the host name in the To Version 6.8 Mediant 1000B Gateway & SBC...
Page 760 Mediant 1000B Gateway & SBC Parameter Description and From headers. If the IP Group is configured with a Proxy Set that has multiple IP addresses, all the REGISTER messages sent to these proxies are sent with the same host name.
Page 761 If a specific Transport Type is configured, a NAPTR query is not performed.  To enable NAPTR/SRV queries for Proxy servers only, use the global parameter ProxyDNSQueryType, or use the proxy Set table. Version 6.8 Mediant 1000B Gateway & SBC...
Page 762 Mediant 1000B Gateway & SBC Parameter Description Web: Proxy DNS Query Type Global parameter that defines the DNS query record type for CLI: proxy-dns-query resolving the Proxy server's configured domain name (FQDN) [ProxyDNSQueryType] into an IP address.  [0] A-Record (default) = A-record DNS query.
Page 763 Set IDs, each with up to 10 Proxy server IP addresses (or CLI: configure voip > voip-network FQDN). proxy-ip The format of the ini file table parameter is as follows: [ProxyIP] [ProxyIP] FORMAT ProxyIp_Index = ProxyIp_IpAddress, ProxyIp_TransportType, ProxyIp_ProxySetId; [\ProxyIP] Version 6.8 Mediant 1000B Gateway & SBC...
Page 764 Mediant 1000B Gateway & SBC Parameter Description For a description of this table, see ''Configuring Proxy Sets'' on page 272. To configure the Proxy Set attributes (such as Proxy Load Balancing) in the ini file, use the ProxySet parameter. Proxy Set Table Web: Proxy Set Table This table parameter defines the Proxy Set ID table.
Page 765 Defines the time interval (in seconds) after which a registration CLI: registration-retry-time request is re-sent if registration fails with a 4xx response or if [RegistrationRetryTime] there is no response from the Proxy/Registrar server. Version 6.8 Mediant 1000B Gateway & SBC...
Page 766 Mediant 1000B Gateway & SBC Parameter Description The default is 30 seconds. The range is 10 to 3600. Web: Registration Time Threshold Defines a threshold (in seconds) for re-registration timing. If EMS: Time Threshold this parameter is greater than 0, but lower than the computed...
Page 767 This is typically used for FXO interfaces and digital modules.  [3] Per FXS = Registration and authentication for FXS endpoints. Note: This parameter is applicable only to the Gateway application. Version 6.8 Mediant 1000B Gateway & SBC...
Page 768 Mediant 1000B Gateway & SBC Parameter Description Web: 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. EMS: Set OOS On Registration Fail  [0] Disable (default) CLI: set-oos-on-reg-failure ...
Page 769 TCP or TLS. The device first sends a SIP OPTION message to establish the TCP/TLS connection and if it receives any SIP response, it continues sending the CRLF keep-alive Version 6.8 Mediant 1000B Gateway & SBC...
Page 770: Network Application Parameters
Mediant 1000B Gateway & SBC Parameter Description sequences. EMS: Ping Pong Keep Alive Time Defines the periodic interval (in seconds) after which a “ping” [PingPongKeepAliveTime] (double-CRLF) keep-alive is sent to a proxy/registrar, using the CRLF Keep-Alive mechanism. The default range is 5 to 2,000,000. The default is 120.
Page 771 UDP port network realm range. [CpMediaRealm] The format of the ini file table parameter is as follows: [ CpMediaRealm ] FORMAT CpMediaRealm_Index = CpMediaRealm_MediaRealmName, CpMediaRealm_IPv4IF, CpMediaRealm_IPv6IF, CpMediaRealm_PortRangeStart, CpMediaRealm_MediaSessionLeg, Version 6.8 Mediant 1000B Gateway & SBC...
Page 772: General Sip Parameters
Mediant 1000B Gateway & SBC Parameter Description CpMediaRealm_PortRangeEnd, CpMediaRealm_IsDefault, CpMediaRealm_QoeProfile, CpMediaRealm_BWProfile; [ \CpMediaRealm ] For a detailed description of this table, see ''Configuring Media Realms'' on page 251. Remote Media Subnet Table Web: Remote Media This table parameter defines Remote Media Subnets.
Page 773 (if Automatic Update has been enabled on the device)  'check-sync;reboot=true': triggers a device reset Note: The Event header value is proprietary to AudioCodes. Web/EMS: Max SIP Defines the maximum size (in Kbytes) for each SIP message that can Message Length [KB] be sent over the network.
Page 774 Mediant 1000B Gateway & SBC Parameter Description  [1] = Enable The X-RTP-Stat header provides the following statistics:  Number of received and sent voice packets  Number of received and sent voice octets  Received packet loss, jitter (in ms), and latency (in ms) The X-RTP-Stat header contains the following fields: ...
Page 775 SIP 4xx response to the originating party. However, if the ReleaseIP2ISDNCallOnProgressWithCause parameter is set to 1, then the device sends a SIP 4xx response even if the EnableEarlyMedia parameter is set to 1. Version 6.8 Mediant 1000B Gateway & SBC...
Page 776 Mediant 1000B Gateway & SBC Parameter Description  [0] = (Default) If a Progress with Cause message is received from the PSTN for an outgoing IP-to-ISDN call, the device does not disconnect the call by sending a SIP 4xx response to the originating party.
Page 777 G.729 and “regular” G.711 coders, it sends an SDP answer containing only the G.729 coder.  [1] = Enable. The device assumes that the G.711 coder received in the INVITE SDP offer is a VBD coder. For example, if the device is Version 6.8 Mediant 1000B Gateway & SBC...
Page 778 Mediant 1000B Gateway & SBC Parameter Description configured with G.729 and G.711 VBD coders and it receives an INVITE with an SDP offer containing G.729 and “regular” G.711 coders, it sends an SDP answer containing G.729 and G.711 VBD coders, allowing a subsequent bypass (passthrough) session if fax/modem signals are detected during the call.
Page 779 EnableTCPConnectionReuse parameter to 1. Web/EMS: Reliable Enables setting of all TCP/TLS connections as persistent and Connection Persistent Mode therefore, not released. CLI: reliable-conn-persistent  [0] = (Default) Disable. All TCP connections (except those that are Version 6.8 Mediant 1000B Gateway & SBC...
Page 780 Mediant 1000B Gateway & SBC Parameter Description [ReliableConnectionPersis set to a proxy IP) are released if not used by any SIP tentMode] dialog\transaction.  [1] = Enable - TCP connections to all destinations are persistent and not released unless the device reaches 70% of its maximum TCP resources.
Page 781 If a 'tgrp' value is specified in incoming messages, it is ignored.  [2] Send and Receive = The functionality of outgoing SIP messages is identical to the functionality described for option [1]. In Version 6.8 Mediant 1000B Gateway & SBC...
Page 782 Mediant 1000B Gateway & SBC Parameter Description addition, for incoming SIP INVITEs, if the Request-URI includes a 'tgrp' parameter, the device routes the call according to that value (if possible). The Contact header in the outgoing SIP INVITE (Tel-to- IP call) contains "tgrp=<source trunk group ID>;trunk- context=<gateway IP address>”.
Page 783 Record (AOR). For example, in call transfer where user A is talking to user B, and user A wants to transfer the call to user C. User A sends a REFER to user C: REFER sip:C@domain.com SIP/2.0 Version 6.8 Mediant 1000B Gateway & SBC...
Page 784 Defines the string that is used in the SIP User-Agent and Server Information response headers. When configured, the string <UserAgentDisplayInfo EMS: User Agent Display value>/software version' is used, for example: Info User-Agent: myproduct/v.6.40.010.006 CLI: user-agent-info If not configured, the default string, <AudioCodes product- User's Manual Document #: LTRT-27034...
Page 785 INVITE sent to the call made un-hold (retrieved). The used coder is therefore, re-negotiated. This parameter is useful in the following call scenario example: Party A calls party B and coder G.711 is chosen. Version 6.8 Mediant 1000B Gateway & SBC...
Page 786 Mediant 1000B Gateway & SBC Parameter Description Party B is put on-hold while Party A blind transfers Party B to Party Party C answers and Party B is made un-hold. However, as Party C supports only G.729 coder, re-negotiation of the supported coder is required.
Page 787 [2] P-Called-Party-ID header = Obtains the destination number from the P-Called-Party-ID header. Web/EMS: Enable Reason Enables the usage of the SIP Reason header. Header  [0] Disable CLI: reason-header  [1] Enable (default) [EnableReasonHeader] Version 6.8 Mediant 1000B Gateway & SBC...
Page 788 Mediant 1000B Gateway & SBC Parameter Description Web/EMS: Gateway Name Defines a name for the device (e.g., device123.com). This name is CLI: gw-name used as the host part of the SIP URI in the From header. If not [SIPGatewayName] specified, the device's IP address is used instead (default).
Page 789 'rport' parmeter. Web: Enable X-Channel Determines whether the SIP X-Channel header is added to SIP Header messages for providing information on the physical Trunk/B-channel Version 6.8 Mediant 1000B Gateway & SBC...
Page 790 Mediant 1000B Gateway & SBC Parameter Description EMS: X Channel Header on which the call is received or placed. CLI: x-channel-header  [0] Disable = (Default) X-Channel header is not used. [XChannelHeader]  [1] Enable = X-Channel header is generated by the device and sent in INVITE messages and 180, 183, and 200 OK SIP responses.
Page 791 For example, if a calling party makes a call to telephone number 622125519100 Ext. 104, the device receives the SIP INVITE (from Microsoft's application) with the URI user part as INVITE sip:622125519100;ext=104@10.1.1.10 (or INVITE Version 6.8 Mediant 1000B Gateway & SBC...
Page 792 Mediant 1000B Gateway & SBC Parameter Description tel:622125519100;ext=104). If the parameter EnableMicrosofExt is enabled, the device modifies the called number by adding an "e" as the prefix, removing the "ext=" parameter, and adding the extension number as the suffix (e.g., e622125519100104). Once modified, the...
Page 793 Enables the device to send a SIP INFO message with the On- Info Hook/Off-Hook parameter when the FXS phone goes on-hook during CLI: reans-info-enbl an ongoing call and then off-hook again, within the user-defined regret [EnableReansweringINFO] timeout (configured by the parameter RegretTime). Therefore, the Version 6.8 Mediant 1000B Gateway & SBC...
Page 794 Mediant 1000B Gateway & SBC Parameter Description device notifies the far-end that the call has been re-answered.  [0] Disable (default)  [1] Enable This parameter is typically implemented for incoming IP-to-Tel collect calls to the FXS port. If the FXS user does not wish to accept the collect call, the user disconnects the call by on-hooking the phone.
Page 795 4xx response when SIT-IC (Operator Intercept [SITQ850CauseForIC] Special Information Tone) is detected from the PSTN for IP-to-Tel calls. The valid range is 0 to 127. The default is -1 (not configured). Version 6.8 Mediant 1000B Gateway & SBC...
Page 796 Mediant 1000B Gateway & SBC Parameter Description Note: When not configured (i.e., default), the SITQ850Cause parameter is used. Web/EMS: SIT Q850 Cause Defines the Q.850 cause value specified in the SIP Reason header For VC that is included in a 4xx response when SIT-VC (Vacant Circuit - non-...
Page 797 [4] Block = Blocks trunk (CAS only). Notes:  The parameter is applicable only to digital interfaces.  To configure the timeout interval (in seconds) for Out-of-Service graceful shutdown mode for busy trunks if communication fails with Version 6.8 Mediant 1000B Gateway & SBC...
Page 798 Mediant 1000B Gateway & SBC Parameter Description a Proxy server (or Proxy Set), use the GracefulBusyOutTimeout parameter.  The parameter is applicable only if the EnableBusyOut parameter is set to 1 (Enable).  When configuring the parameter value at run-time, you must stop the trunk and then restart it for the settings to take effect.
Page 799 For example, the below configuration changes the user part of the SIP From header to 200: MessageManipulations 1 = 0, Invite.Request, , Header.From.Url.User, 2, 200, 0; For a detailed description of this table, see Configuring SIP Message Manipulation on page 286. Version 6.8 Mediant 1000B Gateway & SBC...
Page 800: Coders And Profile Parameters
Mediant 1000B Gateway & SBC Parameter Description Message Policy Table Web: Message Policy Table This table parameter configures SIP message policy rules for blocking CLI: configure voip > sbc (blacklist) unwanted incoming SIP messages or allowing (whitelist) message-policy receipt of desired messages.
Page 801 IpProfile_SBCRFC2833Behavior, IpProfile_SBCAlternativeDTMFMethod, IpProfile_SBCAssertIdentity, IpProfile_AMDSensitivityParameterSuit, IpProfile_AMDSensitivityLevel, IpProfile_AMDMaxGreetingTime, IpProfile_AMDMaxPostSilenceGreetingTime, IpProfile_SBCDiversionMode, IpProfile_SBCHistoryInfoMode, IpProfile_EnableQSIGTunneling, IpProfile_SBCFaxCodersGroupID, IpProfile_SBCFaxBehavior, IpProfile_SBCFaxOfferMode, IpProfile_SBCFaxAnswerMode, IpProfile_SbcPrackMode, IpProfile_SBCSessionExpiresMode, IpProfile_SBCRemoteUpdateSupport, IpProfile_SBCRemoteReinviteSupport, IpProfile_SBCRemoteDelayedOfferSupport, IpProfile_SBCRemoteReferBehavior, IpProfile_SBCRemote3xxBehavior, IpProfile_SBCRemoteMultiple18xSupport, IpProfile_SBCRemoteEarlyMediaResponseType, IpProfile_SBCRemoteEarlyMediaSupport, IpProfile_EnableSymmetricMKI, IpProfile_MKISize, IpProfile_SBCEnforceMKISize, IpProfile_SBCRemoteEarlyMediaRTP, IpProfile_SBCRemoteSupportsRFC3960, IpProfile_SBCRemoteCanPlayRingback, IpProfile_EnableEarly183, IpProfile_EarlyAnswerTimeout, IpProfile_SBC2833DTMFPayloadType, IpProfile_SBCUserRegistrationTime, Version 6.8 Mediant 1000B Gateway & SBC...
Page 802 Mediant 1000B Gateway & SBC Parameter Description IpProfile_ResetSRTPStateUponRekey, IpProfile_AmdMode, IpProfile_SBCReliableHeldToneSource, IpProfile_GenerateSRTPKeys, IpProfile_SBCPlayHeldTone, IpProfile_SBCRemoteHoldFormat, IpProfile_SBCRemoteReplacesBehavior, IpProfile_SBCSDPPtimeAnswer, IpProfile_SBCPreferredPTime, IpProfile_SBCUseSilenceSupp, IpProfile_SBCRTPRedundancyBehavior, IpProfile_SBCPlayRBTToTransferee, IpProfile_SBCRTCPMode, IpProfile_SBCJitterCompensation, IpProfile_SBCRemoteRenegotiateOnFaxDetection, IpProfile_JitterBufMaxDelay; [\IPProfile] For a description of this table, see ''Configuring IP Profiles'' on page 302. Tel Profile Table Web: Tel Profile Settings This table parameter configures the Tel Profile table.
Page 803: Channel Parameters
IP Profile table, see ''Configuring IP Profiles'' on page 302. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated Version 6.8 Mediant 1000B Gateway & SBC...
Page 804 Mediant 1000B Gateway & SBC Parameter Description with the IP Profile. Web: Echo Canceler Global parameter that enables echo cancellation (i.e., echo from EMS: Echo Canceller Enable voice calls is removed). You can also configure this functionality CLI: echo-canceller-enable per specific calls, using IP Profiles [EnableEchoCanceller] (IpProfile_EnableEchoCanceller) or Tel Profiles.
Page 805: Coder Parameters
EVRC voice activity detector. Units are in EVRC frame size (20 [EVRCDTXMax] msec). The range is 0 to 20000. The default is 32. Note: This parameter is applicable only to the EVRC coder. Version 6.8 Mediant 1000B Gateway & SBC...
Page 806: Dtmf Parameters
Mediant 1000B Gateway & SBC Parameter Description EMS: VBR Coder Header Determines the format of the RTP header for VBR coders. Format  [0] = (Default) Payload only (no header, TOC, or m-factor) - CLI: VBR-coder-header-format similar to RFC 3558 Header Free format.
Page 807: Rtp, Rtcp And T.38 Parameters
Global parameter that defines the minimum delay (in msec) of Delay the device's dynamic Jitter Buffer. You can also configure this EMS: Minimal Delay (dB) functionality per specific calls, using IP Profiles CLI: jitter-buffer-minimum-delay (IpProfile_JitterBufMinDelay) or Tel Profiles. For a detailed Version 6.8 Mediant 1000B Gateway & SBC...
Page 808 Mediant 1000B Gateway & SBC Parameter Description [DJBufMinDelay] description of this parameter and for configuring this functionality in the IP Profile table, see Configuring IP Profiles on page 302, or in the Tel Profile table, see Configuring Tel Profiles on page 299.
Page 809 RTP, RTCP (RTP port + 1) and T.38 (RTP port + [BaseUDPport] For a detailed description of configuring the UDP port range, see Configuring RTP Base UDP Port on page 174. You can Version 6.8 Mediant 1000B Gateway & SBC...
Page 810 Mediant 1000B Gateway & SBC Parameter Description also configure this functionality per specific calls, using IP Profiles (see Configuring IP Profiles on page 302). Notes:  For this parameter to take effect, a device reset is required.  If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile.
Page 811 PUBLISH messages, according to Internet-Draft draft-ietf- [RTCPXREscIP] sipping-rtcp-summary-13. The address can be configured as a numerical IP address or as a domain name. Note: This parameter is applicable only to the Gateway application. Version 6.8 Mediant 1000B Gateway & SBC...
Page 812: Gateway And Ip-To-Ip Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Gateway RTCP XR Report Determines whether RTCP XR reports are sent to the Event Mode State Compositor (ESC) and defines the interval at which they EMS: Report Mode are sent. CLI: rtcp-xr-rep-mode ...
Page 813 IP Profiles (IpProfile_CNGmode). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page 302. Version 6.8 Mediant 1000B Gateway & SBC...
Page 814 Mediant 1000B Gateway & SBC Parameter Description Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. Web: Fax Detect Timeout Since Defines a timeout (in msec) for detecting fax from the Tel side Connect (msec) during an established voice call.
Page 815 EMS: Dynamic Jitter Buffer Defines the Jitter Buffer delay (in milliseconds) during fax and Minimal Delay (dB) modem bypass session. CLI: jitter-buffer-minimum-delay The range is 0 to 150 msec. The default is 40. [FaxModemBypasDJBufMinD elay] Version 6.8 Mediant 1000B Gateway & SBC...
Page 816 Mediant 1000B Gateway & SBC Parameter Description EMS: Enable Inband Network Enables in-band network detection related to fax/modem. Detection  [0] = (Default) Disable. CLI: enable-fax-modem-inband-  [1] = Enable. When this parameter is enabled on Bypass and network-detection transparent with events mode (VxxTransportType is set to 2 or...
Page 817: Dtmf And Hook-Flash Parameters
The valid range is a 25-character string. The default is a null string. Note: This parameter can also be configured in a Tel Profile. Web/EMS: Hook-Flash Option Determines the hook-flash transport type (i.e., method by Version 6.8 Mediant 1000B Gateway & SBC...
Page 818 Mediant 1000B Gateway & SBC Parameter Description CLI: hook-flash-option which hook-flash is sent and received). For digital interfaces [HookFlashOption] (E1/T1): This feature is applicable only if the HookFlashCode parameter is configured.  [0] Not Supported = (Default) Hook-Flash indication is not sent.
Page 819 [4] RFC 2833.  [5] INFO (Korea) = Sends DTMF digits according to Korea Telecom format. The format of the ini file table parameter is as follows: [TxDTMFOption] FORMAT TxDTMFOption_Index = TxDTMFOption_Type; [\TxDTMFOption] Version 6.8 Mediant 1000B Gateway & SBC...
Page 820 Mediant 1000B Gateway & SBC Parameter Description For example: TxDTMFOption 0 = 1; TxDTMFOption 1 = 3; Notes:  DTMF negotiation methods are prioritized according to the order of their appearance.  When out-of-band DTMF transfer is used ([1], [2], [3], or [5]), the parameter DTMFTransportType is automatically set to 0 (DTMF digits are erased from the RTP stream).
Page 821 IsWaitForDialTone (configurable for the entire device) is ignored.  For analog interfaces: The FXS interface send SIP 200 OK responses only after the DTMF dialing is complete.  This parameter can also be configured in a Tel Profile. Version 6.8 Mediant 1000B Gateway & SBC...
Page 822: Digit Collection And Dial Plan Parameters
Mediant 1000B Gateway & SBC Parameter Description CLI: replace-nb-sign-w-esc Determines whether to replace the number sign (#) with the [ReplaceNumberSignWithEscapeChar] escape character (%23) in outgoing SIP messages for Tel- to-IP calls.  [0] Disable (default).  [1] Enable = All number signs #, received in the dialed DTMF digits are replaced in the outgoing SIP Request- URI and To headers with the escape sign %23.
Page 823 (digital). When the number of collected digits reaches this maximum, the device uses these digits for the called destination number. The valid range is 1 to 49. The default is 5 for analog and 30for Version 6.8 Mediant 1000B Gateway & SBC...
Page 824 Mediant 1000B Gateway & SBC Parameter Description digital. Notes:  Instead of using this parameter, Digit Mapping rules can be configured.  Dialing ends when any of the following scenarios occur:  Maximum number of digits is dialed  Interdigit Timeout (TimeBetweenDigits) expires ...
Page 825: Voice Mail Parameters
Redirect phone number to the SIP 'target' parameter and the Redirect number reason to the SIP 'cause' parameter in the Request-URI. Redirecting Reason >> SIP Response Code Unknown >> 404 User busy >> 486 No reply >> 408 Version 6.8 Mediant 1000B Gateway & SBC...
Page 826 Mediant 1000B Gateway & SBC Parameter Description Deflection >> 487/480 Unconditional >> 302 Others >> 302 If the device receives a Request-URI that includes a 'target' and 'cause' parameter, the 'target' is mapped to the Redirect phone number and the 'cause' is mapped to the Redirect number reason.
Page 827 SMDI message is dropped. If the timeout expires and only a Setup message is received, the call is established. The valid range is 0 to 10000 (i.e., 10 seconds). The default is 2000. Message Waiting Indication (MWI) Parameters Version 6.8 Mediant 1000B Gateway & SBC...
Page 828 Mediant 1000B Gateway & SBC Parameter Description Web: MWI Off Digit Pattern Defines the digit code used by the device to notify the PBX that EMS: MWI Off Code there are no messages waiting for a specific extension. This CLI: mwi-off-dig-ptrn code is added as prefix to the dialed number.
Page 829 EMS: VM Digit Pattern No Reason an external line (not an internal extension). External The valid range is a 120-character string. CLI: fwd-no-rsn-dig-ptrn-ext [DigitPatternForwardNoReasonE Version 6.8 Mediant 1000B Gateway & SBC...
Page 830: Supplementary Services Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Internal Call Digit Pattern Defines the digit pattern used by the PBX to indicate an internal EMS: Digit Pattern Internal Call call. CLI: int-call-dig-ptrn The valid range is a 120-character string. [DigitPatternInternalCall]...
Page 831  [2] Standard NTT  [4] Standard BT = Britain  [16] Standard DTMF Based ETSI  [17] Standard Denmark = Caller ID and MWI  [18] Standard India  [19] Standard Brazil Version 6.8 Mediant 1000B Gateway & SBC...
Page 832 Mediant 1000B Gateway & SBC Parameter Description Notes:  Typically, the Caller ID signals are generated / detected between the first and second rings. However, sometimes the Caller ID is detected before the first ring signal. In such a scenario, set the RingsBeforeCallerID parameter to 0.
Page 833 Caller ID, which is composed of a Calling Number and a Calling Name (optional).  [0] Disabled = (Default) P-Asserted-Identity and P-Preferred- Identity headers are not added.  [1] Add P-Asserted-Identity  [2] Add P-Preferred-Identity Version 6.8 Mediant 1000B Gateway & SBC...
Page 834 Mediant 1000B Gateway & SBC Parameter Description The used header also depends on the calling Privacy (allowed or restricted). These headers are used together with the Privacy header. If Caller ID is restricted (i.e., P-Asserted-Identity is not sent), the Privacy header includes the value 'id' ('Privacy: id').
Page 835: Call Waiting Parameters
[0] = (Default) Use 182 Queued response to indicate call waiting.  [1] = Use 180 Ringing response to indicate call waiting. Call Waiting Table Web: Call Waiting Table This table parameter configures call waiting per FXS port. The Version 6.8 Mediant 1000B Gateway & SBC...
Page 836 Mediant 1000B Gateway & SBC Parameter Description EMS: SIP Endpoints > Call format of this The format of the ini file table parameter format of Waiting the ini file table parameter is as follows: CLI: configure voip > gw [CallWaitingPerPort]...
Page 837: Call Forwarding Parameters
Provisioning > Tab: Call The format of the ini file table parameter is as follows: Forward [FwdInfo] CLI: configure voip > gw FORMAT FwdInfo_Index = FwdInfo_Type, FwdInfo_Destination, analoggw call-forward FwdInfo_NoReplyTime, FwdInfo_Module, FwdInfo_Port; Version 6.8 Mediant 1000B Gateway & SBC...
Page 838: Message Waiting Indication Parameters
Mediant 1000B Gateway & SBC Parameter Description [FwdInfo] [\FwdInfo] Where,  Module = Module number, where 1 denotes the module in Slot 1.  Port = Port number, where 1 denotes Port 1 of a module. For example:  Below configuration forwards calls originally destined to Port 1 of Module 1 to "1001"...
Page 839 The default is 7200 seconds. The range is 10 to 2,000,000. EMS: MWI Expiration Time CLI: mwi-subs-expr-time [MWIExpirationTime] Web: MWI Subscribe Retry Time Defines the subscription retry time (in seconds) after last EMS: Subscribe Retry Time subscription failure. Version 6.8 Mediant 1000B Gateway & SBC...
Page 840: Call Hold Parameters
Mediant 1000B Gateway & SBC Parameter Description CLI: mwi-subs-rtry-time The default is 120 seconds. The range is 10 to 2,000,000. [SubscribeRetryTime] Web: Subscription Mode Determines the method the device uses to subscribe to an MWI CLI: subscription-mode server. [SubscriptionMode] ...
Page 841 To Tel side: plays DTMF digits according to the received SIP INFO message(s). (The stopped held tone is not played again.)  To IP side: sends DTMF SIP INFO messages to an IP destination if it detects DTMF digits from the Tel side. Version 6.8 Mediant 1000B Gateway & SBC...
Page 842: Call Transfer Parameters
Mediant 1000B Gateway & SBC 51.10.5.6 Call Transfer Parameters The call transfer parameters are described in the table below. Table 51-47: Call Transfer Parameters Parameter Description Web/EMS: Enable Transfer Enables the Call Transfer feature. CLI: enable-transfer  [0] Disable [EnableTransfer] ...
Page 843 If the timeout expires, the device sends the INVITE without changing the calling number. Notes:  The suspension of the INVITE message occurs for all calls.  This parameter is applicable to QSIG. Version 6.8 Mediant 1000B Gateway & SBC...
Page 844: Multi-Line Extensions And Supplementary Services Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Call Transfer using re-INVITEs Enables call transfer using re-INVITEs. CLI: enable-call-transfer-using-  [0] Disable = (Default) Call transfer is done using REFER reinvites messages. [EnableCallTransferUsingReinvites]  [1] Enable = Call transfer is done by sending re-INVITE messages (instead of REFER).
Page 845: Three-Way Conferencing Parameters
EMS: 3 Way Mode feature is used. CLI: 3w-conf-mode  [0] AudioCodes Media Server = (Default) The Conference- [3WayConferenceMode] 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 846 Mediant 1000B Gateway & SBC Parameter Description  When using an external conference server (options [0] or [1]), a conference call with up to six participants can be established. Web: Max. 3-Way Conference Defines the maximum number of simultaneous, on-board three- EMS: Max In Board Calls way conference calls.
Page 847: Mlpp And Emergency Call Parameters
For FXO interfaces, the preemption is done only on existing IP-to-Tel calls. In other words, if all the current FXO channels are busy with calls that were initiated by the FXO (i.e., Tel-to- IP calls), new incoming emergency IP-to-Tel calls are dropped. Version 6.8 Mediant 1000B Gateway & SBC...
Page 848 Mediant 1000B Gateway & SBC Parameter Description  MLPP and Emergency services can also be configured in a Tel Profile.  For more information, see ''Pre-empting Existing Call for E911 IP-to-Tel Call'' on page 434. Emergency E911 Parameters [E911Gateway] Enables Enhanced 9-1-1(E9-1-1) support for ELIN handling in Microsoft Lync Server 2010 environment.
Page 849 The format of this table ini file parameter is as follows: FORMAT ResourcePriorityNetworkDomains_Index = ResourcePriorityNetworkDomains_Name, ResourcePriorityNetworkDomains_EnableIp2TelInterworking; ResourcePriorityNetworkDomains 1 = dsn, 0; ResourcePriorityNetworkDomains 2 = dod, 0; ResourcePriorityNetworkDomains 3 = drsn, 0; ResourcePriorityNetworkDomains 5 = uc, 1; ResourcePriorityNetworkDomains 7 = cuc, 0; Version 6.8 Mediant 1000B Gateway & SBC...
Page 850 Mediant 1000B Gateway & SBC Parameter Description [ \ResourcePriorityNetworkDomains ] Notes:  Indices 1, 2, 3, 5, and 7 cannot be modified and are defined for DSN, DOD, DRSN, UC, and CUC, respectively.  If the MLPPDefaultNamespace parameter is set to -1, interworking from PSTN NI digits is done automatically.
Page 851 [1] Enable = (Default) Adds the SIP resource-priority tag in the SIP Require header. Note: This parameter is applicable only to MLPP priority call handling (i.e., only when the CallPriorityMode parameter is set to 1). Version 6.8 Mediant 1000B Gateway & SBC...
Page 852 Mediant 1000B Gateway & SBC Parameter Description Multiple Differentiated Services Code Points (DSCP) per MLPP Call Priority Level (Precedence) Parameters The MLPP service allows placement of priority calls, where properly validated users can preempt (terminate) lower-priority phone calls with higher-priority calls. For each MLPP call priority level, the DSCP can be set to a value from 0 to 63.
Page 853: Call Cut-Through Parameters
A special CAS table can be used to report call status events (Active/Idle) to the PSTN side during Cut Through mode.  This feature can also be configured in a Tel Profile and therefore, assigned to specific B-channels that use specific CAS tables. Version 6.8 Mediant 1000B Gateway & SBC...
Page 854: Automatic Dialing Parameters
Mediant 1000B Gateway & SBC 51.10.5.11 Automatic Dialing Parameters The automatic dialing upon off-hook parameters are described in the table below. Table 51-52: Automatic Dialing Parameters Parameter Description Automatic Dialing Table Web: Automatic Dialing This table parameter defines telephone numbers that are automatically Table dialed when a specific FXS or FXO port is off-hooked.
Page 855 The valid range is 0 to 1,000. The default is 0. [DelayBeforeDIDWink] Note: This parameter is applicable only to FXS interfaces. EMS: NTT DID Signalling Determines the type of DID signaling support for NTT (Japan) modem: Version 6.8 Mediant 1000B Gateway & SBC...
Page 856: Isdn Bri Parameters
Mediant 1000B Gateway & SBC Parameter Description Form DTMF- or Frequency Shift Keying (FSK)-based signaling. The devices CLI: NTT-DID-signaling- can be connected to Japan's NTT PBX using 'Modem' DID lines. These form DID lines are used to deliver a called number to the PBX.
Page 857: Pstn Parameters
"=" (equal sign)  "-" (hyphen)  "_" (underscore)  "#" (pound sign) By default, the value is undefined. Web/EMS: Protocol Type Defines the PSTN protocol for all the Trunks. To configure the Version 6.8 Mediant 1000B Gateway & SBC...
Page 858 Mediant 1000B Gateway & SBC Parameter Description CLI: protocol protocol type for a specific Trunk, use the ini file parameter [ProtocolType] ProtocolType_x:  [0] NONE  [1] E1 EURO ISDN = ISDN PRI Pan-European (CTR4) protocol  [2] T1 CAS = Common T1 robbed bits protocols including E&M wink start, E&M immediate start, E&M delay dial/start and loop-...
Page 859 The valid range is 0 to 2400. The default is 0 (i.e., the default T301 timer value - 180 seconds - is used). If set to any other value than 0, it overrides the timer with this value. Version 6.8 Mediant 1000B Gateway & SBC...
Page 860 Mediant 1000B Gateway & SBC Parameter Description Notes:  For this parameter to take effect, a device reset is required.  This parameter is applicable only to the QSIG variant. [ISDNJapanNTTTimerT3JA] Defines the T3_JA timer (in seconds). This parameter overrides the internal PSTN T301 timeout on the Users Side (TE side).
Page 861 The PSTN Fallback feature has no relation to the PSTN Fallback Software License Key. [AdminState] Defines the administrative state for all trunks.  [0] = Lock the trunk; stops trunk traffic to configure the trunk Version 6.8 Mediant 1000B Gateway & SBC...
Page 862 Mediant 1000B Gateway & SBC Parameter Description protocol type.  [1] = Shutting down (read only).  [2] = (Default) Unlock the trunk; enables trunk traffic. Notes:  For this parameter to take effect, a device reset is required. ...
Page 863: Tdm Bus And Clock Timing Parameters
[4] Network = Recover clock from PSTN line. Note: For this parameter to take effect, a device reset is required. Web/EMS: TDM Bus Local Defines the physical Trunk ID from which the device recovers Version 6.8 Mediant 1000B Gateway & SBC...
Page 864 Mediant 1000B Gateway & SBC Parameter Description Reference (receives) its clock synchronization. [TDMBusLocalReference] The range is 0 to the maximum number of Trunks. The default is 0. Note: This parameter is applicable only if the parameter TDMBusClockSource is set to 4 and the parameter TDMBusPSTNAutoClockEnable is set to 0.
Page 865: Cas Parameters
Trunks 2 and 3 to use the E&M Immediate Start CAS (E_M_ImmediateTable.dat) protocol: CASFileName_0 = 'E_M_WinkTable.dat' CASFileName_1 = 'E_M_ImmediateTable.dat' CASTableIndex_0 = 0 CASTableIndex_1 = 0 CASTableIndex_2 = 1 CASTableIndex_3 = 1 Notes:  You can define CAS tables per B-channel using the parameter Version 6.8 Mediant 1000B Gateway & SBC...
Page 866 Mediant 1000B Gateway & SBC Parameter Description CASChannelIndex.  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1. Web: Dial Plan Defines the CAS Dial Plan name per trunk. EMS: Dial Plan Name The range is up to 11 characters.
Page 867 Web: Digit Signaling System Defines which Signaling System to use in both directions [CASStateMachineDigitSignalin (detection\generation). gSystem]  [0] DTMF = DTMF signaling.  [1] MF = (Default) MF signaling.  [-1] Default = Default value. Version 6.8 Mediant 1000B Gateway & SBC...
Page 868: Isdn Parameters
Mediant 1000B Gateway & SBC 51.10.6.4 ISDN Parameters The ISDN parameters are described in the table below. Table 51-58: ISDN Parameters Parameter Description Web: ISDN Termination Side Determines EMS: Termination Side the ISDN CLI: isdn-termination-side termination [TerminationSide] side.  [0] User...
Page 869 INFO1 signal on the line, stop the trunk using the Stop Trunk button. [TerminationSide_x] Same as description parameter Termination Side, but for a specific trunk ID (where x denotes the Version 6.8 Mediant 1000B Gateway & SBC...
Page 870 Mediant 1000B Gateway & SBC Parameter Description Trunk ID and 0 is the first Trunk). Web/EMS: B-channel Negotiation Determines CLI: b-ch-negotiation the ISDN [BchannelNegotiation] B-Channel negotiation mode.  Preferre  Exclusiv (default)  [2] Any Notes:  This paramet er is...
Page 871 PI 1 or  [1] = The call connect ed state) is not released if a Q.931 Disconn ect with PI (PI = 1 or 8) messag e is received during the call. Version 6.8 Mediant 1000B Gateway & SBC...
Page 872 Mediant 1000B Gateway & SBC Parameter Description  [0] = (Default) The call disconn ected. Web: PI For Setup Message Determines CLI: pi-4-setup-msg whether [PIForSetupMsg] and which Progress Indicator (PI) information element (IE) is added to the sent ISDN Setup message.
Page 873 With NFAS, you can use a single D- channel to control multiple interfaces. Notes:  For this paramet er to take effect, a device reset is required  This Version 6.8 Mediant 1000B Gateway & SBC...
Page 874 Mediant 1000B Gateway & SBC Parameter Description paramet er is applicab le only to T1 ISDN protocol  The x in the ini file paramet er name denotes the trunk number, where 0 is Trunk  more informati on on...
Page 875 The x in the ini file paramet er name denotes the trunk number, where 0 is Trunk Web: NFAS Interface ID Defines a EMS: ISDN NFAS Interface ID different CLI: isdn-nfas-interface-id Interface ID Version 6.8 Mediant 1000B Gateway & SBC...
Page 876 Mediant 1000B Gateway & SBC Parameter Description [ISDNNFASInterfaceID_x] per T1 trunk. The valid range is 0 to 100. The default interface ID equals the trunk's ID. Notes:  To set NFAS interface configur ISDNIBe havior_x include '512' feature per T1 trunk.
Page 877 Tel calls (Q.931 Setup).  [64] VOICE CONN RS = device sends a Connect (answer) messag e on incomin g Tel calls.  [2048] CHAN ID IN FIRST RS = (Default) Version 6.8 Mediant 1000B Gateway & SBC...
Page 878 Mediant 1000B Gateway & SBC Parameter Description device sends Channel ID in the first respons e to an incomin g Q.931 Call Setup messag Otherwi se, the Channel ID is sent only if device requires changin g the propose Channel ...
Page 879 Setup messag e. This option is applicab le to the overlap dialing mode. device also plays a dial tone (for TimeFor DialTon e) until the next called Version 6.8 Mediant 1000B Gateway & SBC...
Page 880 Mediant 1000B Gateway & SBC Parameter Description number digits received . By default, this is bit is set.  [214748 3648] USER SCREE INDICA TOR = When device receives Calling Number IE's in Setup messag e, the device, default, uses...
Page 881 : the first  prov ided prov ided : the  prov ided user prov ided : the first When this bit is configur ed, the device behaves follows: Version 6.8 Mediant 1000B Gateway & SBC...
Page 882 Mediant 1000B Gateway & SBC Parameter Description  prov ided prov ided : the first calli  prov ided prov ided : the  prov ided prov ided : the first  prov ided User's Manual Document #: LTRT-27034...
Page 883 Same as description for the parameter ISDNInCall sBehavior, but per trunk (i.e., where x denotes the Trunk ID). Web/EMS: Q.931 Layer Response Bit-field Behavior used to CLI: isdn-bits-ns-behavior determine several [ISDNIBehavior] behavior options that Version 6.8 Mediant 1000B Gateway & SBC...
Page 884 Mediant 1000B Gateway & SBC Parameter Description influence behaviour of the Q.931 protocol.  [0] = Disable (default)  [1] NO STATU S ON UNKNO WN IE = Q.931 Status messag e isn't sent if Q.931 received messag contains unknow...
Page 885 Status messag e is optional.  ACCEP UNKNO FAC IE Accepts unknow n/unreco gnized Facility Otherwi se, the Q.931 messag e that contains unknow Facility IE is rejected (default) Version 6.8 Mediant 1000B Gateway & SBC...
Page 886 Mediant 1000B Gateway & SBC Parameter Description Note: This option is applicab le only to ISDN variants where a complet e ASN1 decodin g is perform ed on Facility  [128] SEND USER CONNE CT ACK = The Connect messag...
Page 887 Identific ation IE explicit Interface ID, even if the B- channel is on the same trunk as the D- channel. Note: This value is applicab le only 4/5ESS, and NI-2 variants.  [32768] Version 6.8 Mediant 1000B Gateway & SBC...
Page 888 Mediant 1000B Gateway & SBC Parameter Description ACCEP T MU =Mu- Law is also accepte d in ETSI.  [65536] EXPLICI T PRES SCREE NING = calling party number (octet 3a) is always present even when presenta tion and screenin...
Page 889 =A-Law is also accepte d in 5ESS.  [209715 RESTA INDICA TION = Upon receipt of a Restart messag acEV_P STN_R ESTAR T_CON FIRM is generat  [419430 FORCE RESTA RT = On Version 6.8 Mediant 1000B Gateway & SBC...
Page 890 Mediant 1000B Gateway & SBC Parameter Description data link (re)initial ization, send RESTA RT if there is no call.  [671088 64] NS ACCEP T ANY CAUSE Accept Q.850 Cause IE from ISDN. Note: This option is applicab le only to Euro ISDN.
Page 891 OXE).  [107374 1824] ENCOD INTEGE R = If this bit is set, INTEGE R ASN.1 type is used in operator coding (complia nt to ECMA standard otherwis OBJEC IDENTIF ASN.1 type is Version 6.8 Mediant 1000B Gateway & SBC...
Page 892 Mediant 1000B Gateway & SBC Parameter Description used. Note: This option is applicab le only to QSIG.  [214748 3648] 5ESS National Mode For Bch Mainten ance = Use the National mode of AT&T 5ESS for B- channel mainten ance.
Page 893 For BRI terminal endpoint identifier (TEI) configur ation, instead of using ISDNIBe havior paramet er, use following paramet ers: BriTEIC onfigP2 P_x, BriTEIC onfigP2 MP_x, BriTEIA ssignTri gger_x, BriTEIR emoveT rigger_x. [ISDNIBehavior_x] Same as Version 6.8 Mediant 1000B Gateway & SBC...
Page 894 Mediant 1000B Gateway & SBC Parameter Description description parameter ISDNIBeha vior, but for a specific trunk ID. Web: General Call Control Behavior Bit-field for EMS: General CC Behavior determining CLI: isdn-bits-cc-behavior several general CC [ISDNGeneralCCBehavior] behavior options. To select the...
Page 895  [32] CHAN ID 16 ALLOW ED = Applies only to ETSI E1 lines (30B+D) Enables handling differenc between Version 6.8 Mediant 1000B Gateway & SBC...
Page 896 Mediant 1000B Gateway & SBC Parameter Description newer QSIG standard (ETS 300- 172) other ETSI- based standard s (ETS 300-102 and ETS 300- 403) in conversi on of B- channel values into timeslot values:  'reg ular stan dard time...
Page 897 51. Configuration Parameters Reference Parameter Description nnel iden tifie d as nnel carri into time slot #16.  stan dard nnel rang e is 1 to time slot rang e is still 1 to nnel Version 6.8 Mediant 1000B Gateway & SBC...
Page 898 Mediant 1000B Gateway & SBC Parameter Description iden tifie d as nnel #16, still carri into time slot #16. this set, nnel side as a vali d B- nnel time slot valu vert refle rang User's Manual Document #: LTRT-27034...
Page 899 (def ault) , the nnel allo , as like stan dard  [64] USE T1 PRI = interface type is forced to  [128] USE E1 PRI = interface type is Version 6.8 Mediant 1000B Gateway & SBC...
Page 900 Mediant 1000B Gateway & SBC Parameter Description forced to  [256] START WITH B CHAN OOS = channel s start in the Out- Service state (OOS).  [512] CHAN ALLOC LOWES T = CC allocate s B- channel starting from the...
Page 901 UUI. When this bit is not set (default behavior ), CC impleme nts the UUI- protocol specifie d in the 300-403 standard s for Implicit Service  [65536] GTD5 TBCT = impleme Version 6.8 Mediant 1000B Gateway & SBC...
Page 902 Mediant 1000B Gateway & SBC Parameter Description nts the VERIZO N-GTD- 5 Switch variant of the TBCT Supple mentary Service, specifie d in FSD 01-02- 40AG Feature Specific ation Docume nt from Verizon. Otherwi TBCT is impleme nted as specifie...
Page 903 0 (i.e., disable).  USER SENDIN COMPL =The default behavior of the device (when this bit is not set) is to automati cally generat e the Sending Complet e IE in Setup messag Version 6.8 Mediant 1000B Gateway & SBC...
Page 904 Mediant 1000B Gateway & SBC Parameter Description e. This behavior is used when overlap dialing is needed. When overlap dialing is needed, set this bit and behavior changed to suit scenario , i.e., Sending Complet e IE is added when...
Page 905 _NB IE. Note: This option is applicab le only to the Korean variant (Korean network) . This is useful Korean switches that don't accept CALLED _NB IE.  [256] STORE CHAN ID IN SETUP Version 6.8 Mediant 1000B Gateway & SBC...
Page 906 Mediant 1000B Gateway & SBC Parameter Description = The device forces sending of a Channel -Id IE in outgoing Setup messag e even if it's not required by the standard (i.e., optional) and no Channel -Id has been specifie d in the...
Page 907 Numberi plan/typ e for T1 IP-to-Tel calling numbers defined accordin g to the manipul ation tables or accordin g to the RPID header (default) Otherwi se, the plan/typ e for T1 calls are Version 6.8 Mediant 1000B Gateway & SBC...
Page 908 Mediant 1000B Gateway & SBC Parameter Description accordin g to the length of calling number.  [2048] = device accepts any IA5 characte r in the called_n b and calling_ strings sends any IA5 characte r in the called_n b, and is...
Page 909 Web: ISDN NS Behaviour 2 Bit-field to CLI: isdn-bits-ns-extension- determine behavior several [ISDNNSBehaviour2] behavior options that influence behavior of the Q.931 protocol.  [8] NS BEHAVI OUR2 UUI = User to User Informati Element (UUIE) Version 6.8 Mediant 1000B Gateway & SBC...
Page 910 Mediant 1000B Gateway & SBC Parameter Description accepte d for any protocol discrimi nator. This is useful interope rability with non- standard switches  [16] NS BEHAVI OUR2 DISPLA Y = The Display IE is accepte d even if it is not...
Page 911  [0] = (Default) Applicab le for NI- 2 ISDN QSIG "Networ king Extensio ns". This bit (i.e., bit #0) is responsi ble for Invoke ID size:  this (def ault) then Invo Version 6.8 Mediant 1000B Gateway & SBC...
Page 912 Mediant 1000B Gateway & SBC Parameter Description size byte with valu e of  this set, then Invo size byte ordi Invo valu  [2] = Applicab le to the ROSE format (accordi ng to the QSIG specifica tions). This bit (i.e., bit...
Page 913 QSIG supplem entary services Facility messag should be 0x9F Networki Extensio Howeve accordin g to the version, value should be 0x91 ROSE:  this (def ault) king Exte nsio  this Version 6.8 Mediant 1000B Gateway & SBC...
Page 914 Mediant 1000B Gateway & SBC Parameter Description set:  [3] = options [0] and above. Note: For this parameter to take effect, a device reset is required. BRI Parameters BRI Layer 2 Mode Defines Point-to-Point (P2P) or Point-to-Multipoint (P2MP) CLI: isdn-layer2-mode mode for BRI ports.
Page 915: Isdn And Cas Interworking Parameters
For IP-to-Tel calls, this parameter is not applicable. Only if the incoming ISDN Connect message contains the Date / Time IE does the device add the Date header to the sent SIP 200 OK Version 6.8 Mediant 1000B Gateway & SBC...
Page 916 Mediant 1000B Gateway & SBC Parameter Description message. Web/EMS: Min Routing Defines the minimum number of overlap digits to collect (for ISDN Overlap Digits overlap dialing) before sending the first SIP message for routing CLI: min-dg-b4-routing Tel-to-IP calls. [MinOverlapDigitsForRouting The valid value range is 0 to 49. The default is 1.
Page 917 SIP header (X-ISDNTunnelingInfo) or a dedicated message body (application/isdn) in the SIP messages. Notes:  For this feature to function, you must set the parameter ISDNDuplicateQ931BuffMode to 128 (i.e., duplicate all messages). Version 6.8 Mediant 1000B Gateway & SBC...
Page 918 Mediant 1000B Gateway & SBC Parameter Description  ISDN tunneling is applicable for all ISDN variants as well as QSIG. Web/EMS: Enable ISDN Enables ISDN Tunneling for IP-to-Tel calls. Tunneling IP to Tel  [0] Disable (default) CLI: isdn-tnl-ip2tel ...
Page 919 If the isub parameter is not received in the user part of the Request-URI, the device searches for it in the URI parameters of the To header, for example, To: "Alex" <sip: 9565645@host.domain;isub=1234> Version 6.8 Mediant 1000B Gateway & SBC...
Page 920 Mediant 1000B Gateway & SBC Parameter Description If present, the isub value is sent in the ISDN Setup message as the destination subaddress. If the isub parameter is not present in the Request-URI header nor To header, the device does the following: ...
Page 921 Discriminator (pd) attribute (according to IETF Internet-Draft draft-johnston-sipping-cc-uui-04). For example: User-to- User=3030373435313734313635353b313233343b3834;pd  [2] = SIP header format: User-to-User with encoding=hex at the end and pd embedded as the first byte (according to IETF Version 6.8 Mediant 1000B Gateway & SBC...
Page 922 Mediant 1000B Gateway & SBC Parameter Description Internet-Draft draft-johnston-sipping-cc-uui-03). For example: User-to- User=043030373435313734313635353b313233343b3834; encoding=hex where "04" at the beginning of this message is the pd.  [3] = Interworks the SIP User-to-User header containing text format to ISDN UUIE in hexadecimal format, and vice versa. For...
Page 923 [-1] Not Configured = (Default) Use per device configuration of For Trunk Mode the BChannelNegotiation parameter. [BChannelNegotiationForTru  [0] Preferred. nk_x]  [1] Exclusive.  [2] Any. Notes:  This parameter is applicable to ISDN protocols. Version 6.8 Mediant 1000B Gateway & SBC...
Page 924 Mediant 1000B Gateway & SBC Parameter Description  The option Any is only applicable if TerminationSide is set to 0 (i.e., User side).  The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1.
Page 925 Trunk Groups, this parameter is ignored. Web: Enable User-to-User IE Enables transfer of User-to-User (UU) IE from ISDN PRI to SIP. for Tel to IP  [0] Disable (default) EMS: Enable UUI Tel 2 Ip Version 6.8 Mediant 1000B Gateway & SBC...
Page 926 Mediant 1000B Gateway & SBC Parameter Description  CLI: uui-ie-for-tel2ip [1] Enable [EnableUUITel2IP] The device supports the following ISDN PRI-to-SIP interworking: Setup to SIP INVITE, Connect to SIP 200 OK, User Information to SIP INFO, Alerting to SIP 18x response, and Disconnect to SIP BYE response messages.
Page 927 Blind Transfer by executing a CAS Wink, dialing the Refer-to number to the switch, and then releasing the call.  [4] = Supports QSIG Single Step transfer (PRI/BRI): Version 6.8 Mediant 1000B Gateway & SBC...
Page 928 Mediant 1000B Gateway & SBC Parameter Description IP-to-Tel: When a SIP REFER message is received, the device performs a transfer by sending a Facility message to the PBX, initiating Single Step transfer. Once a success return result is received, the transfer is completed.
Page 929 [DisableFallbackTransferToT Enables "hairpin" TDM transfer upon ISDN (ECT, RLT, or TBCT) call transfer failure. When this feature is enabled and an ISDN call transfer failure occurs, the device sends a SIP NOTIFY message Version 6.8 Mediant 1000B Gateway & SBC...
Page 930 Mediant 1000B Gateway & SBC Parameter Description with a SIP 603 Decline response.  [0] = (Default) The device performs a hairpin TDM transfer upon ISDN call transfer.  [1] = Hairpin TDM transfer is disabled. Web: Enable QSIG Transfer...
Page 931: Answer And Disconnect Supervision Parameters
Notes:  FXO interfaces: This feature is applicable only to one-stage dialing (FXO).  Digital interfaces: To activate this feature, set the EnableDSPIPMDetectors parameter to 1. Version 6.8 Mediant 1000B Gateway & SBC...
Page 932 Mediant 1000B Gateway & SBC Parameter Description  Digital interfaces: This feature is applicable only when the protocol type is CAS. Web/EMS: Max Call Duration (min) Defines the maximum duration (in minutes) of a call. If this CLI: mx-call-duration duration is reached, the device terminates the call. This feature...
Page 933 Enables the generation of the BrokenConnection event during a silence period if the channel’s NoOp feature is enabled (using the parameter NoOpEnable) and if the channel stops receiving NoOp RTP packets.  [0] Disable (default) Version 6.8 Mediant 1000B Gateway & SBC...
Page 934 Mediant 1000B Gateway & SBC Parameter Description  [1] Enable Web: Trunk Alarm Call Disconnect Defines the duration (in seconds) to wait after an E1/T1 trunk Timeout "Red" alarm (LOS / LOF) is raised, before the device CLI: trk-alrm-call-disc-to disconnects the SIP call. If this timeout expires and the alarm is...
Page 935 Some Caller ID signals use reversal polarity and/or Wink signals. In these cases, it is recommended to set the parameter PolarityReversalType to 1 (Hard).  For this parameter to take effect, a device reset is required. Version 6.8 Mediant 1000B Gateway & SBC...
Page 936: Tone Parameters
Mediant 1000B Gateway & SBC Parameter Description EMS: Current Disconnect Duration Defines the duration (in msec) of the current disconnect pulse. CLI: current-disconnect-duration The range is 200 to 1500. The default is 900. [CurrentDisconnectDuration] Notes:  This parameter is applicable for FXS and FXO interfaces.
Page 937 For analog interfaces: Defines the duration (in seconds) that the Duration [sec] device plays a busy or reorder tone before releasing the line. Typically, CLI: reorder-tone-duration after playing the busy or reorder tone for this duration, the device Version 6.8 Mediant 1000B Gateway & SBC...
Page 938 Mediant 1000B Gateway & SBC Parameter Description [TimeForReorderTone] starts playing an offhook warning tone. For digital interfaces: Defines the duration (in seconds) that the CAS device plays a busy or reorder tone before releasing the line. The valid range is 0 to 254. The default is 0 seconds for analog interfaces and 10 seconds for digital interfaces.
Page 939 Tel side. The user-defined tone is configured when creating the PRT file, using AudioCodes DConvert utility. The tone must be assigned to the "acSpecialConditionTone" (Tone Type 21) option in DConvert. The parameter can be configured with up to 10 release codes. When configuring multiple codes, separate the codes by commas (without spaces).
Page 940 Mediant 1000B Gateway & SBC Parameter Description 1, it plays a ringback tone and sends an ISDN Alert with PI = 8 (unless the ProgressIndicator2ISDN_x parameter is configured differently). 2) If the LocalISDNRBSource parameter is set to 0, the device doesn't play a ringback tone and an Alert message without PI is sent to the ISDN.
Page 941 (183 is handled the same way as a 180 with SDP), the device sends an Alert message with PI = 8 without playing a ringback tone.  [3] Play Local Until Remote Media Arrive = Plays tone according to Version 6.8 Mediant 1000B Gateway & SBC...
Page 942 Mediant 1000B Gateway & SBC Parameter Description received media. The behaviour is similar to option [2]. If a SIP 180 response is received and the voice channel is already open (due to a previous 183 early media response or due to an SDP in the current 180 response), the device plays a local ringback tone if there are no prior received RTP packets.
Page 943: Tone Detection Parameters
SIP Reason header that is included in a 4xx response when a SIT tone is detected on an IP-to-Tel call. To disconnect IP-to-CAS calls when a SIT tone is detected, the following parameters must be configured (applicable to Version 6.8 Mediant 1000B Gateway & SBC...
Page 944: Metering Tone Parameters
Mediant 1000B Gateway & SBC Parameter Description FXO interfaces):  SITDetectorEnable = 1  UserDefinedToneDetectorEnable = 1  DisconnectOnBusyTone = 1 (applicable for busy, reorder, and SIT tones) Notes:  For this parameter to take effect, a device reset is required.
Page 945 EndTime = Period (1 - 4) end time.  PulseInterval = Period (1 - 4) pulse interval.  PulsesOnAnswer = Period (1 - 4) pulses on answer. For example: ChargeCode 1 = 7,30,1,14,20,2,20,15,1,0,60,1; Version 6.8 Mediant 1000B Gateway & SBC...
Page 946: Telephone Keypad Sequence Parameters
Mediant 1000B Gateway & SBC Parameter Description ChargeCode 2 = 5,60,1,14,20,1,0,60,1; ChargeCode 3 = 0,60,1; ChargeCode 0 = 6, 3, 1, 12, 2, 1, 18, 5, 2, 0, 2, 1; Notes:  To associate a configured Charge Code to an outgoing Tel-to-IP call, use the Outbound IP Routing table.
Page 947 (Flash Hook + Digit mode - when the parameter [FlashKeysSequenceTimeout] FlashKeysSequenceStyle is set to 1 or 2). The valid range is 100 to 5,000. The default is 2,000. Keypad Feature - Call Forward Parameters Version 6.8 Mediant 1000B Gateway & SBC...
Page 948 Mediant 1000B Gateway & SBC Parameter Description Web: Forward Unconditional Defines the keypad sequence to activate the immediate call EMS: Call Forward Unconditional forward option. CLI: fwd-unconditional [KeyCFUnCond] Web: Forward No Answer Defines the keypad sequence to activate the forward on no EMS: Call Forward No Answer answer option.
Page 949: Fxo And Fxs Parameters
USA or Europe (TBR21) standards. CLI: fxs-country-coefficients  [66] Europe = TBR21 [FXSCountryCoefficients]  [70] USA = (Default) United States Note: For this parameter to take effect, a device reset is Version 6.8 Mediant 1000B Gateway & SBC...
Page 950 Mediant 1000B Gateway & SBC Parameter Description required. FXO Parameters Web: FXO Coefficient Type Determines the FXO line characteristics (AC and DC) EMS: Country Coefficients according to USA or TBR21 standard. CLI: fxo-country-coefficients  [66] Europe = TBR21 [CountryCoefficients] ...
Page 951 IP call. This parameter is typically set to between 5 and 8. The default is 8. Notes: Version 6.8 Mediant 1000B Gateway & SBC...
Page 952 Mediant 1000B Gateway & SBC Parameter Description  This parameter is applicable only for Tel-to-IP calls.  This timeout is calculated from the end of the ring until the start of the next ring. For example, if the ring cycle is two seconds on and four seconds off, the timeout value should be configured to five seconds (i.e., greater than...
Page 953: Trunk Groups And Routing Parameters
CLI: configure voip > gw hunt-or-trunk- telephone numbers and assigning them to Trunk Groups. group TrunkGroup The format of the ini file table parameter is as follows: [TrunkGroup] [TrunkGroup] FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_FirstTrunkId, Version 6.8 Mediant 1000B Gateway & SBC...
Page 954 Mediant 1000B Gateway & SBC Parameter Description TrunkGroup_FirstBChannel, TrunkGroup_LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileId, TrunkGroup_LastTrunkId, TrunkGroup_Module; [\TrunkGroup] Notes:  Trunk Group ID 1 is denoted as 0 in the table.  For a description of this table, seeConfiguring Trunk Group Table on page 351.
Page 955 Tel Source Number and Presentation is set to Restricted (1). For example: When 'From: 100 <sip:200@201.202.203.204>' is received, the outgoing Source Number and Display Name are set to '100' and the Presentation is set to Allowed (0). Version 6.8 Mediant 1000B Gateway & SBC...
Page 956 Mediant 1000B Gateway & SBC Parameter Description When 'From: <sip:100@101.102.103.104>' is received, the outgoing Source Number is set to '100' and the Presentation is set to Restricted (1). Web: ENUM Resolution Defines the ENUM service for translating telephone numbers CLI: enum-service-domain...
Page 957 (i.e., number isn't listed in the table or a call restriction routing rule of IP address 0.0.0.0 is applied), the call is released. Note: When no Proxy is used, this parameter must be Version 6.8 Mediant 1000B Gateway & SBC...
Page 958 Mediant 1000B Gateway & SBC Parameter Description disabled and filtering is according to the Outbound IP Routing table. Web: IP-to-Tel Tagging Destination Defines the Dial Plan index in the Dial Plan file for called Dial Plan Index prefix tags for representing called number prefixes in CLI: ip2tel-tagging-dst Inbound Routing rules.
Page 959 Defines the maximum time interval (in seconds) that the device waits for CNG detection before re-routing calls identified as fax calls to fax destinations (terminating fax machine). The valid value range is 1-10. The default is 5. Version 6.8 Mediant 1000B Gateway & SBC...
Page 960 Mediant 1000B Gateway & SBC Parameter Description Call Forking Parameters Web/EMS: Forking Handling Mode Determines how the device handles the receipt of multiple CLI: forking-handling SIP 18x forking responses for Tel-to-IP calls. The forking 18x response is the response with a different SIP to-tag than [ForkingHandlingMode] the previous 18x response.
Page 961: Ip Connectivity Parameters
Defines the time interval (in seconds) between SIP OPTIONS Alive Time Keep-Alive messages used for the IP Connectivity application. EMS: Alternative Routing Keep The valid range is 5 to 2,000,000. The default is 60. Alive Time CLI: alt-rte-tel2ip-keep-alive [AltRoutingTel2IPKeepAliveTime] Version 6.8 Mediant 1000B Gateway & SBC...
Page 962: Alternative Routing Parameters
Mediant 1000B Gateway & SBC Parameter Description Web: Max Allowed Packet Loss for Defines the packet loss (in percentage) at which the IP Alt Routing [%] connection is considered a failure and Alternative Routing CLI: mx-pkt-loss-4-alt-rte mechanism is activated. [IPConnQoSMaxAllowedPL] The default is 20%.
Page 963 FORMAT AltRouteCauseTel2IP_Index = AltRouteCauseTel2IP_ReleaseCause; [\AltRouteCauseTel2IP] For example: AltRouteCauseTel2IP 0 = 486; (Busy Here) AltRouteCauseTel2IP 1 = 480; (Temporarily Unavailable) AltRouteCauseTel2IP 2 = 408; (No Response) For a detailed description of this table, see ''Alternative Version 6.8 Mediant 1000B Gateway & SBC...
Page 964 Mediant 1000B Gateway & SBC Parameter Description Routing Based on SIP Responses'' on page 399. Reasons for Alternative IP-to-Tel Routing Table Web: Reasons for Alternative IP-to- This table parameter configures call failure reason values Tel Routing received from the PSTN side (in Q.931 presentation). If a call...
Page 965: Number Manipulation Parameters
For example, if the incoming INVITE From header contains "12345" Tel] and the destined B-channel number is 17, then the outgoing calling party number in the Q.931 Setup message is set to "17" instead of "12345". Version 6.8 Mediant 1000B Gateway & SBC...
Page 966 Mediant 1000B Gateway & SBC Parameter Description Note: When enabled, this feature is applied after routing and manipulation on the source number (i.e., just before sending to the Tel side). Web: Tel2IP Default Redirect Determines the default redirect reason for Tel-to-IP calls when no Reason redirect reason (or “unknown”) exists in the received Q931 ISDN...
Page 967 The device first performs Tel-to-IP destination phone number manipulation (i.e., on the SIP To header), and only then copies the manipulated called number to the SIP Diversion header for the Tel-to-IP call. Therefore, with Version 6.8 Mediant 1000B Gateway & SBC...
Page 968 Mediant 1000B Gateway & SBC Parameter Description this option, the called and redirect numbers are identical.  [2] Copy before phone number manipulation = Copies the called number before manipulation. The device first copies the original called number to the SIP Diversion header, and then performs Tel-to-IP destination phone number manipulation.
Page 969 If such a prefix is found (e.g., "21"), then before the call is routed to the corresponding Trunk Group, the prefix "21" is removed from the original number, and therefore, only "100" Version 6.8 Mediant 1000B Gateway & SBC...
Page 970 Mediant 1000B Gateway & SBC Parameter Description remains. Notes:  This parameter is applicable only if number manipulation is performed after call routing for IP-to-Tel calls (i.e., RouteModeIP2Tel parameter is set to 0).  Similar operation (of removing the prefix) is also achieved by using the usual number manipulation rules.
Page 971 IP > Tel Calls [NumberMapIp2Tel] EMS: SIP Manipulations > FORMAT NumberMapIp2Tel_Index = Destination IP to Telcom NumberMapIp2Tel_ManipulationName, CLI: configure voip > gw NumberMapIp2Tel_DestinationPrefix, manipulations NumberMapIp2Tel_SourcePrefix, NumberMapIp2Tel2 NumberMapIp2Tel_SourceAddress, [NumberMapIP2Tel] NumberMapIp2Tel_NumberType, NumberMapIp2Tel_NumberPlan, NumberMapIp2Tel_RemoveFromLeft, NumberMapIp2Tel_RemoveFromRight, Version 6.8 Mediant 1000B Gateway & SBC...
Page 972 Mediant 1000B Gateway & SBC Parameter Description NumberMapIp2Tel_LeaveFromRight, NumberMapIp2Tel_Prefix2Add, NumberMapIp2Tel_Suffix2Add, NumberMapIp2Tel_IsPresentationRestricted; [\NumberMapIp2Tel] For a detailed description of this table, see ''Configuring Source/Destination Number Manipulation'' on page 359. EMS: Perform Additional Enables additional destination number manipulation for IP-to-Tel IP2TEL Destination calls. The additional manipulation is done on the initially manipulated...
Page 973 The format of the ini file table parameter is as follows: IP to Tel [RedirectNumberMapIp2Tel] CLI: configure voip > gw FORMAT RedirectNumberMapIp2Tel_Index = manipulations redirect- RedirectNumberMapIp2Tel_ManipulationName, number-map-ip2tel RedirectNumberMapIp2Tel_DestinationPrefix, [RedirectNumberMapIp2Tel] RedirectNumberMapIp2Tel_RedirectPrefix, RedirectNumberMapIp2Tel_SourceAddress, RedirectNumberMapIp2Tel_SrcHost, RedirectNumberMapIp2Tel_DestHost, RedirectNumberMapIp2Tel_NumberType, RedirectNumberMapIp2Tel_NumberPlan, RedirectNumberMapIp2Tel_RemoveFromLeft, RedirectNumberMapIp2Tel_RemoveFromRight, RedirectNumberMapIp2Tel_LeaveFromRight, RedirectNumberMapIp2Tel_Prefix2Add, RedirectNumberMapIp2Tel_Suffix2Add, Version 6.8 Mediant 1000B Gateway & SBC...
Page 974 Mediant 1000B Gateway & SBC Parameter Description RedirectNumberMapIp2Tel_IsPresentationRestricted; [\RedirectNumberMapIp2Tel] For a description of this table, see Configuring Redirect Number Manipulation on page 369. Redirect Number Tel-to-IP Table Web: Redirect Number Tel -> This table parameter manipulates the Redirect Number for Tel-to-IP calls.
Page 975: Sbc Parameters
SRD, the call is rejected. Web: SBC No Answer Timeout Defines the timeout (in seconds) for SBC outgoing (outbound IP CLI: sbc-no-arelt-timeout routing) SIP INVITE messages. If the called IP party does not Version 6.8 Mediant 1000B Gateway & SBC...
Page 976 Mediant 1000B Gateway & SBC Parameter Description [SBCAlertTimeout] answer the call within this user-defined interval, the device disconnects the session. The device starts the timeout count upon receipt of a SIP 180 Ringing response from the called party. If no other SIP response (for example, 200 OK) is received thereafter within this timeout, the call is released.
Page 977 CLI: configure voip/sbc general- Registration database. setting/sbc-usr-reg-grace-time The valid value is 0 to 300 (i.e., 5 minutes). The default is 0. [SBCUserRegistrationGraceTime Web/EMS: Handle P-Asserted- Global parameter that defines the handling of the SIP P- Version 6.8 Mediant 1000B Gateway & SBC...
Page 978 Mediant 1000B Gateway & SBC Parameter Description Identity Asserted-Identity header. You can also configure this CLI: p-assert-id functionality per specific calls, using IP Profiles [SBCAssertIdentity] (IpProfile_SBCAssertIdentity). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see ''Configuring IP Profiles'' on page 302.
Page 979 This parameter is used to provide replay protection (i.e., [AuthNonceDuration] ensures that old communication streams are not used in replay attacks). The valid value range is 30 to 600. The default is 300. Version 6.8 Mediant 1000B Gateway & SBC...
Page 980 Mediant 1000B Gateway & SBC Parameter Description Web: Authentication Challenge Defines the type of server-based authentication challenge. Method  [0] 0 = (Default) Send SIP 401 "Unauthorized" with a WWW- CLI: auth-chlng-mthd Authenticate header as the authentication challenge [AuthChallengeMethod] response.
Page 981 Aastra IP phones display the message, "Stand Alone Mode" on their LCD screens. Survivability mode occurs when connectivity with the WAN fails and as a result, the device enables communication between IP phone users within the LAN Version 6.8 Mediant 1000B Gateway & SBC...
Page 982 Mediant 1000B Gateway & SBC Parameter Description enterprise.  [0] = Disable  [1] = Enable When this feature is enabled and the SBC device is in Survivability mode, it responds to SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following...
Page 983  [1] Enable = All SBC calls use the No Media Anchoring feature (i.e., direct media). Note: For more information on No Media Anchoring, see ''No Media Anchoring (Anti Tromboning)'' on page 493. Version 6.8 Mediant 1000B Gateway & SBC...
Page 984 Mediant 1000B Gateway & SBC Parameter Description Web: Transcoding Mode Global parameter that defines the voice transcoding mode CLI: transcoding-mode (media negotiation). You can also configure this functionality per [TranscodingMode] specific calls, using IP Profiles (IpProfile_TranscodingMode). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see Configuring IP Profiles on page 302.
Page 985 (SIP CLI: configure voip > sbc sbc- dialogs). admission-control The format of the ini file table parameter is as follows: [SBCAdmissionControl] [SBCAdmissionControl] FORMAT SBCAdmissionControl_Index = SBCAdmissionControl_AdmissionControlName, SBCAdmissionControl_LimitType, SBCAdmissionControl_IPGroupID, Version 6.8 Mediant 1000B Gateway & SBC...
Page 986 Mediant 1000B Gateway & SBC Parameter Description SBCAdmissionControl_SRDID, SBCAdmissionControl_RequestType, SBCAdmissionControl_RequestDirection, SBCAdmissionControl_Limit, SBCAdmissionControl_LimitPerUser, SBCAdmissionControl_Rate, SBCAdmissionControl_MaxBurst, SBCAdmissionControl_Reservation; [\SBCAdmissionControl] For a detailed description of this table, see ''Configuring Admission Control'' on page 517. Allowed Audio Coders Table Web: Allowed Audio Coders This table parameter defines Allowed Coders Groups, which CLI: configure voip >...
Page 987 URI user part (source and/or destination) of the inbound SIP Manipulation dialog message. The format of the ini file table parameter is as CLI: configure voip > sbc follows: manipulations ip-inbound- [IPInboundManipulation] manipulation FORMAT IPInboundManipulation_Index = Version 6.8 Mediant 1000B Gateway & SBC...
Page 988 Mediant 1000B Gateway & SBC Parameter Description [IPInboundManipulation] IPInboundManipulation_ManipulationName IPInboundManipulation_IsAdditionalManipulation, IPInboundManipulation_ManipulatedURI, IPInboundManipulation_ManipulationPurpose, IPInboundManipulation_SrcIPGroupID, IPInboundManipulation_SrcUsernamePrefix, IPInboundManipulation_SrcHost, IPInboundManipulation_DestUsernamePrefix, IPInboundManipulation_DestHost, IPInboundManipulation_RequestType, IPInboundManipulation_RemoveFromLeft, IPInboundManipulation_RemoveFromRight, IPInboundManipulation_LeaveFromRight, IPInboundManipulation_Prefix2Add, IPInboundManipulation_Suffix2Add; [\IPInboundManipulation] For a detailed description of this table, see ''Configuring IP-to-IP Inbound Manipulations'' on page 542. IP to IP Outbound Manipulation Table...
Page 989: Standalone Survivability Parameters
('Normal Mode'), this port serves as the source port. The valid range is 1 to 65,534. The default is 5081. Web: SAS Connection Reuse Enables the re-use of the same TCP connection for sessions Version 6.8 Mediant 1000B Gateway & SBC...
Page 990 Mediant 1000B Gateway & SBC Parameter Description CLI: sas-connection-reuse with the same user in the SAS application. [SASConnectionReuse]  [0] Disable  [1] Enable (default) The device can use the same TCP connection for multiple SIP requests / responses for a specific SIP UA. For example, assume the following: ...
Page 991 Determines the SAS application database binding mode. EMS: Binding Mode  [0] URI = (Default) If the incoming AoR in the INVITE CLI: sasbindingmode requests is using a ‘tel:’ URI or ‘user=phone’ is defined, the Version 6.8 Mediant 1000B Gateway & SBC...
Page 992 Mediant 1000B Gateway & SBC Parameter Description [SASBindingMode] binding is performed according to the user part of the URI only. Otherwise, the binding is according to the entire URI, i.e., User@Host.  [1] User Part only = The binding is always performed according to the User Part only.
Page 993: Ip Media Parameters
IP-to-IP calls is 120, corresponding to 60 IP-to- IP calls. The maximum number of media channels depends on the number of installed Media Processing modules (MPM). For more information, see DSP Channel Resources on page 184. Version 6.8 Mediant 1000B Gateway & SBC...
Page 994 Mediant 1000B Gateway & SBC Parameter Description The default is 0. Notes:  For this parameter to take effect, a device reset is required.  The SBC application does not require DSP channels. The SBC application uses DSP channels only if media transcoding is needed, where two DSP channels are used per transcoding session.
Page 995 For example: INVITE sip:ivr@10.2.3.4 Subsequent INFO messages carry the requests and responses. Web: Transcoding ID Defines the Transcoding identification string (up to 16 [TranscodingID] characters) used for identifying an incoming Transcoding call. The default is ‘trans’. Version 6.8 Mediant 1000B Gateway & SBC...
Page 996 Mediant 1000B Gateway & SBC Parameter Description For more information on Transcoding, see NetAnn Interface. AMS Parameters Enables advanced audio. This parameter must be set to 1. [AmsProfile]  [0] = Disable (default)  [1] = Enable Note: For this parameter to take effect, a device reset is required.
Page 997 For a description of AGC, see Automatic Gain Control (AGC) on page 181. Web: AGC Slope Determines the AGC convergence rate: EMS: Gain Slope  [0] 0 = 0.25 dB/sec CLI: AGC-gain-slope  [1] 1 = 0.50 dB/sec Version 6.8 Mediant 1000B Gateway & SBC...
Page 998 Mediant 1000B Gateway & SBC Parameter Description  [AGCGainSlope] [2] 2 = 0.75 dB/sec  [3] 3 = 1.00 dB/sec (default)  [4] 4 = 1.25 dB/sec  [5] 5 = 1.50 dB/sec  [6] 6 = 1.75 dB/sec ...
Page 999 You can also configure this functionality per specific calls, using IP Profiles (IpProfile_AMDMaxGreetingTime). For a detailed description of this parameter and for configuring this functionality in the IP Profile table, see Configuring IP Version 6.8 Mediant 1000B Gateway & SBC...
Page 1000 Mediant 1000B Gateway & SBC Parameter Description Profiles on page 302. Note: If this functionality is configured for a specific IP Profile, the settings of this global parameter is ignored for calls associated with the IP Profile. EMS: AMD Max Post Silence Greeting...
Page 1001 [MRCPDefaultMIMEType] Determines the default format for speech recognition for inline grammars.  [0] = (Default) Indicates GRXML  [1] = Indicates GL (Nuance format) [MRCPEnabled] Activates the Media Resource Control Protocol (MRCP) Version 6.8 1001 Mediant 1000B Gateway & SBC...
Page 1002 Mediant 1000B Gateway & SBC Parameter Description functionality.  [0] = Disable (default)  [1] = Activate [MRCPMaxPorts] Defines the number of ports that are allocated to running MRCP-related activities such as speech recognition and text-to-speech. A port is considered duplex, so that speech recognition and text-to-speech can run on the same port.
Page 1003: Services
RADIUS Accounting Parameters Web: Enable RADIUS Enables the RADIUS application. Access Control  [0] Disable (Default) CLI: enable  [1] Enable [EnableRADIUS] Note: For this parameter to take effect, a device reset is required. Version 6.8 1003 Mediant 1000B Gateway & SBC...
Page 1004 Mediant 1000B Gateway & SBC Parameter Description Web: Accounting Server Defines the IP address of the RADIUS accounting server. IP Address CLI: accounting-server-ip [RADIUSAccServerIP] Web: Accounting Port Defines the port of the RADIUS accounting server. CLI: accounting-port The default is 1646.
Page 1005 [RadiusTO] Defines the time interval (measured in seconds) that the device waits for a response before a RADIUS retransmission is issued. The valid range is 1 to 30. The default is 10. Version 6.8 1005 Mediant 1000B Gateway & SBC...
Page 1006: Ldap Parameters
Mediant 1000B Gateway & SBC 51.14.1.3 LDAP Parameters The Lightweight Directory Access Protocol (LDAP) parameters are described in the table below. LDAP Parameters Parameter Description Web: LDAP Service Enables the LDAP feature. CLI: configure  [0] Disable (default) voip/ldap/enable ...
Page 1007 The default is 0. timemout [LDAPCacheEntryRemova lTimeout] LDAP Configuration Table Web: LDAP Configuration Defines the LDAP servers. Table [ LdapConfiguration ] CLI: configure voip > ldap > FORMAT LdapConfiguration_Index = ldap-configuration LdapConfiguration_LdapConfServerIp, Version 6.8 1007 Mediant 1000B Gateway & SBC...
Page 1008: Least Cost Routing Parameters
Mediant 1000B Gateway & SBC Parameter Description [LdapConfiguration] LdapConfiguration_LdapConfServerPort, LdapConfiguration_LdapConfServerMaxRespondTime, LdapConfiguration_LdapConfServerDomainName, LdapConfiguration_LdapConfPassword, LdapConfiguration_LdapConfBindDn, LdapConfiguration_LdapConfInterfaceType, LdapConfiguration_Type, LdapConfiguration_MngmAuthAtt, LdapConfiguration_ConnectionStatus; [ \LdapConfiguration ] For a detailed description of this table, see 'Configuring LDAP Servers' on page 205. LDAP Server Search DN Table Web: LDAP Search DN Defines the full base path (i.e., distinguished name / DN) to the...
Page 1009 FORMAT CostGroupTimebands_TimebandIndex = CLI: configure voip > CostGroupTimebands_StartTime, CostGroupTimebands_EndTime, services least-cost-routing CostGroupTimebands_ConnectionCost, cost-group-time-bands CostGroupTimebands_MinuteCost; [CostGroupTimebands] [\CostGroupTimebands] Note: For a detailed description of this table, see ''Configuring Time Bands for Cost Groups'' on page 231. Version 6.8 1009 Mediant 1000B Gateway & SBC...
Page 1010: Call Setup Rules Parameters
Mediant 1000B Gateway & SBC 51.14.3 Call Setup Rules Parameters The Call Setup Rules parameters are described in the table below. Table 51-74: Call Setup Rules Parameters Parameter Description Web: Call Setup Rules This table parameter defines Call Setup Rules that the device runs at...
Page 1011: Sbc And Channel Capacity
The table below lists the maximum capacity. This includes SIP signaling sessions, SBC sessions, and registered users. Table 52-1: Maximum Signaling-Media Sessions and Registered Users Media Signaling Codec Registered Users Sessions Transcoding SRTP-RTP and RTP-to-RTP SRTP-TDM Version 6.8 1011 Mediant 1000B Gateway & SBC...
Page 1012 The capacity figures listed in the table below are accurate at the time of publication of this document. However, these figures may change due to a later software update. For the latest figures, please contact your AudioCodes sales representative. •...
Page 1013: Dsp Templates And Channel Capacity
10, 11, 12, 14, 15, 16 Number of Channels Default Settings With SRTP Voice Coder √ √ G.711 A/Mu-law PCM √ √ G.727 √ √ G.726 ADPCM √ √ G.723.1 √ √ G.729 A, B √ G.722 Version 6.8 1013 Mediant 1000B Gateway & SBC...
Page 1014: Bri Interfaces
Mediant 1000B Gateway & SBC 52.2.2 BRI Interfaces The table below lists the supported channel capacity per DSP firmware template for BRI interfaces: Table 52-3: DSP Firmware Templates for BRI Interfaces DSP Template 0, 1, 2, 4, 5, 6 10, 11, 12, 14, 15, 16...

AudioCodes Mediant 1000B User Manual

Table of Contents

1 Overview

Getting Started with Initial Connectivity

2 Introduction

3 Default OAMP IP Address

4 Configuring Voip LAN Interface for OAMP

Management Tools

5 Introduction

6 Web-Based Management

7 CLI-Based Management

8 SNMP-Based Management

9 INI File-Based Management

General System Settings

10 Configuring SSL/ TLS Certificates

11 Date and Time

General Voip Configuration

12 Network

13 Security

14 Media

15 Services

16 Quality of Experience

17 Control Network

18 SIP Definitions

19 Coders and Profiles

Gateway Application

20 Introduction

21 Digital PSTN

22 Trunk Group

23 Manipulation

24 Routing

25 Configuring DTMF and Dialing

26 Configuring Supplementary Services

27 Analog Gateway

Session Border Controller Application

28 SBC Overview

29 SBC Configuration

Cloud Resilience Package

30 CRP Overview

31 CRP Configuration

Maintenance

32 Basic Maintenance

33 Disconnecting Active Calls

34 Replacing Modules

35 Resetting Channels

36 Software Upgrade

37 Automatic Update Mechanism

38 Restoring Factory Defaults

39 Automatic Archiving of Configuration File

Status, Performance Monitoring and Reporting

40 System Status

41 Carrier-Grade Alarms

42 Performance Monitoring

43 Voip Status

Quick Links

Chapters

Related Manuals for AudioCodes Mediant 1000B

Summary of Contents for AudioCodes Mediant 1000B