User's Manual Version 5.
SIP User's Manual Contents Table of Contents 1 Overview ............................................................................................................19 1.1 Mediant 1000 ......................................................................................................... 19 1.2 Mediant 600 ........................................................................................................... 20 1.3 SIP Overview ...................................................................
Mediant 1000 & Mediant 600 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.5 Management Tab ................................................................................................. 253 3.5.1 3.5.2 3.6 Media Settings .........................................................................................................80 3.4.2.1 Configuring the Voice Settings................................................................ 81 3.4.2.2 Configuring the Fax / Modem / CID Settings .......................
SIP User's Manual 4 ini File Configuration ......................................................................................291 4.1 Secured Encoded ini File ..................................................................................... 291 4.2 The ini File Structure ............................................................................................ 292 4.2.1 4.2.2 4.2.3 4.2.4 6 Modifying an ini File .................................................................................
Mediant 1000 & Mediant 600 7.2.3 7.2.4 7.3 Supporting V.34 Faxes ......................................................................................... 404 7.2.3.1 Using Bypass Mechanism for V.34 Fax Transmission.......................... 404 7.2.3.2 Using Relay mode for both T.30 and V.34 faxes .................................. 405 Supporting V.152 Implementation ........................................................................ 405 FXO Operating Modes .........................................
SIP User's Manual 8 Networking Capabilities..................................................................................445 8.1 Ethernet Interface Configuration .......................................................................... 445 8.2 Ethernet Interface Redundancy ........................................................................... 445 8.3 NAT (Network Address Translation) Support....................................................... 446 8.3.1 8.3.2 8.3.3 STUN .................
Mediant 1000 & Mediant 600 10.2 Announcement Server ......................................................................................... 483 10.2.1 NetAnn Interface................................................................................................... 483 10.2.1.1 Playing a Local Voice Prompt ............................................................... 483 10.2.1.2 Playing using HTTP/NFS Streaming..................................................... 483 10.2.1.3 Supported Attributes....
SIP User's Manual Contents 14.3.5 Additional RedHat™ and Fedora™ Installation Notes ......................................... 534 14.3.6 Post-installation Notes for Kernels 2.6+ (Fedora™ Core 4+ and RedHat™ EL 4+)534 14.4 Installing Linux™ Debian ..................................................................................... 535 14.4.1 Stage 1: Obtaining the ISO Image........................................................................ 535 14.4.2 Stage 2: Preparing the Boot Media ...............
Mediant 1000 & Mediant 600 List of Figures Figure 3-1: Enter Network Password Screen .........................................................................................26 Figure 3-2: Main Areas of the Web Interface GUI..................................................................................27 Figure 3-3: "Reset" Displayed on Toolbar ..............................................................................................28 Figure 3-4: Terminology for Navigation Tree Levels .............
SIP User's Manual Contents Figure 3-58: Web & Telnet Access List Page - Add New Entry .......................................................... 114 Figure 3-59: Web & Telnet Access List Table ..................................................................................... 115 Figure 3-60: Firewall Settings Page .................................................................................................... 116 Figure 3-61: Certificates Signing Request Page .......................................
Mediant 1000 & Mediant 600 Figure 3-117: End Process Wizard Page ............................................................................................ 276 Figure 3-118: Message Box Informing of Upgraded CMP File ........................................................... 276 Figure 3-119: Configuration File Page ................................................................................................ 277 Figure 3-120: Message Log Screen .........................................................
SIP User's Manual Contents Figure 12-9: Inserting iPMX Module.................................................................................................... 505 Figure 12-10: Inserting HDMX Module................................................................................................ 506 Figure 12-11: Removing Lithium Battery from iPMX Module .............................................................. 508 Figure 13-1: Selecting Source of Windows XP Installation CD..........................
Mediant 1000 & Mediant 600 List of Tables Table 3-1: Description of Toolbar Buttons..............................................................................................28 Table 3-2: ini File Parameters for Changing Logo Image ......................................................................50 Table 3-3: ini File Parameters for Replacing Logo with Text .................................................................50 Table 3-4: ini File Parameters for Customizing Product Name ...............
SIP User's Manual Contents Table 3-58: FXO Parameters Description ........................................................................................... 249 Table 3-59: TDM Bus Settings Parameters Description ..................................................................... 252 Table 3-60: Management Settings Parameters................................................................................... 255 Table 3-61: SNMP Trap Destinations Parameters Description...................................
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 16 Document #: LTRT-83303
SIP User's Manual Notices Notice This document describes the AudioCodes Mediant 1000 and Mediant 600 Voice-over-IP (VoIP) SIP media gateways. 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.
Mediant 1000 & Mediant 600 Related Documentation Document # Manual Name LTRT-523xx (where xx is the document version) Product Reference Manual LTRT-831xx Mediant 1000 and Mediant 600 SIP Release Notes LTRT-835xx Mediant 1000 MEGACO-SIP Installation Manual LTRT-856xx Mediant 600 SIP Installation Manual LTRT-665xx CPE Configuration Guide for IP Voice Mail Notes: The following naming conventions are used throughout this manual, unless otherwise specified: • The term device refers to the Mediant 1
SIP User's Manual 1 1. Overview Overview This section provides an overview of the Mediant 1000 and Mediant 600 media gateways. 1.1 Mediant 1000 The AudioCodes Mediant 1000 (hereafter referred to as device) is a best-of-breed Voiceover-IP (VoIP) Session Initiation Protocol (SIP) Media Gateway, using field-proven, marketleading technology, implementing analog and digital cutting-edge technology.
Mediant 1000 & Mediant 600 Analog: The device's analog interface supports up to 24 analog ports (four ports per analog module) in various Foreign Exchange Office (FXO) or Foreign Exchange Station (FXS) configurations, supporting up to 24 simultaneous VoIP calls. The device supports up to six analog modules, each module providing four analog RJ-11 ports. The FXO module can be used to connect analog lines of an enterprise's PBX or the PSTN to the IP network.
SIP User's Manual 1.3 1. Overview SIP Overview Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol used on the gateway for creating, modifying, and terminating sessions with one or more participants. These sessions can include Internet telephone calls, media announcements, and conferences. SIP invitations are used to create sessions and carry session descriptions that enable participants to agree on a set of compatible media types.
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 22 Document #: LTRT-83303
SIP User's Manual 2 2. Configuration Concepts Configuration Concepts You can configure the device's parameters (including upgrading the software, and uploading configuration and auxiliary files), using the following tools: An HTTP-based Embedded Web Server (Web interface), using any standard Web browser (described in ''Web-based Management'' on page 25). A configuration file referred to as the ini file (refer to ''ini File Configuration'' on page 291).
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 24 Document #: LTRT-83303
SIP User's Manual 3 3. Web-Based Management Web-Based Management The device's Embedded Web Server (Web interface) provides FCAPS (fault management, configuration, accounting, performance, and security) functionality. The Web interface allows you to remotely configure your device for quick-and-easy deployment, including uploading of configuration (software upgrade) and auxiliary files, and resetting the device.
Mediant 1000 & Mediant 600 3.2 Accessing the Web Interface The Web interface can be opened using any standard Web browser (refer to ''Computer Requirements'' on page 25). When initially accessing the Web interface, use the default user name ('Admin') and password ('Admin'). For changing the login user name and password, refer to ''Configuring the Web User Accounts'' on page 112). ¾ To access the Web interface, take these 4 steps: 1. Open a standard Web browser application. 2.
SIP User's Manual 3.3 3. Web-Based Management Getting Acquainted with the Web Interface The figure below displays the general layout of the Graphical User Interface (GUI) of the Web interface: Figure 3-2: Main Areas of the Web Interface GUI The Web GUI is composed of the following main areas: Title bar: Displays the corporate logo and product name. For replacing the logo with another image or text, refer to ''Replacing the Corporate Logo'' on page 48.
Mediant 1000 & Mediant 600 3.3.1 Toolbar The toolbar provides command buttons for quick-and-easy access to frequently required commands, as described in the table below: Table 3-1: Description of Toolbar Buttons Icon -- Button Name Description Submit Applies parameter settings to the device (refer to ''Saving Configuration'' on page 265). Note: This icon is grayed out when not applicable to the currently opened page.
SIP User's Manual 3.3.2 3. Web-Based Management Navigation Tree The Navigation tree, located in the Navigation pane, displays the menus (pertaining to the menu tab selected on the Navigation bar) used for accessing the configuration pages. The Navigation tree displays a tree-like structure of menus. You can easily drill-down to the required page item level to open its corresponding page in the Work pane.
Mediant 1000 & Mediant 600 ¾ To navigate to a page, take these 2 steps: 1. 2. 3.3.2.1 Navigate to the required page item, by performing the following: • Drilling-down using the plus signs to expand the menus and submenus • Drilling-up using the minus signs to collapse the menus and submenus Select the required page item; the page opens in the Work pane.
SIP User's Manual 3.3.2.2 3. Web-Based Management Showing / Hiding the Navigation Pane The Navigation pane can be hidden to provide more space for elements displayed in the Work pane. This is especially useful when the Work pane displays a page with a table that's wider than the Work pane and to view the all the columns, you need to use scroll bars. The arrow button located just below the Navigation bar is used to hide and show the Navigation pane.
Mediant 1000 & Mediant 600 3.3.3.1 Accessing Pages The configuration pages are accessed by clicking the required page item in the Navigation tree. ¾ To open a configuration page in the Work pane, take these 2 steps: 1.
SIP User's Manual 3. Web-Based Management 3.3.3.2.1 Displaying Basic and Advanced Parameters Some pages provide you with an Advanced Parameter List / Basic Parameter List toggle button that allows you to show or hide advanced parameters (in addition to displaying the basic parameters). This button is located on the top-right corner of the page and has two states: Advanced Parameter List button with down-pointing arrow: click this button to display all parameters.
Mediant 1000 & Mediant 600 3.3.3.2.2 Showing / Hiding Parameter Groups Some pages provide groups of parameters, which can be hidden or shown. To toggle between hiding and showing a group, simply click the group name button that appears above each group. The button appears with a down-pointing or up-pointing arrow, indicating that it can be collapsed or expanded when clicked, respectively. Figure 3-8: Expanding and Collapsing Parameter Groups 3.3.3.
SIP User's Manual 3.
Mediant 1000 & Mediant 600 3.3.3.4 Entering Phone Numbers in Various Tables Phone numbers or prefixes that you enter in various tables throughout the Web interface such as the 'Tel to IP Routing' table, must only be entered as digits without any other characters. For example, if you wish to enter the phone number 555-1212, it must be entered as 5551212 without the hyphen (-). If the hyphen is entered, the entry is invalid. 3.3.3.
SIP User's Manual 3. Web-Based Management ¾ To add a copy of an existing index table entry, take these 3 steps: 1. In the 'Index' column, select the index that you want to duplicate; the Edit button appears. 2. Click Edit; the fields in the corresponding index row become available. 3. Click Duplicate; a new index entry is added with identical settings as the selected index in Step 1.
Mediant 1000 & Mediant 600 ¾ To delete an existing index table entry, take these 3 steps: 3.3.4 1. In the 'Index' column, select the index corresponding to the table row that you want to delete. 2. Click Delete; the table row is removed from the table. Searching for Configuration Parameters The Web interface provides a search engine that allows you to search any ini file parameter that is configurable by the Web interface (i.e., has a corresponding Web parameter).
SIP User's Manual 4. 3. Web-Based Management In the searched list, click the required parameter (link in green) to open the page in which the parameter appears; the relevant page opens in the Work pane and the searched parameter is highlighted for easy identification, as shown in the figure below: Figure 3-13: Searched Result Screen Note: If the searched parameter is not located, a notification message is displayed. Version 5.
Mediant 1000 & Mediant 600 3.3.5 Working with Scenarios The Web interface allows you to create your own "menu" with up to 20 pages selected from the menus in the Navigation tree (i.e., pertaining to the Configuration, Management, and Status & Diagnostics tabs). The "menu" is a set of configuration pages grouped into a logical entity referred to as a Scenario. Each page in the Scenario is referred to as a Step.
SIP User's Manual 7. 3. Web-Based Management Click the Next button located at the bottom of the page; the Step is added to the Scenario and appears in the Scenario Step list: Figure 3-15: Creating a Scenario 8. Repeat steps 5 through 8 to add additional Steps (i.e., pages). 9. When you have added all the required Steps for your Scenario, click the Save & Finish button located at the bottom of the Navigation tree; a message box appears informing you that the Scenario has been successfully created.
Mediant 1000 & Mediant 600 3.3.5.2 Accessing a Scenario Once you have created the Scenario, you can access it at anytime by following the procedure below: ¾ To access the Scenario, take these 2 steps: 1. On the Navigation bar, select the Scenario tab; a message box appears, requesting you to confirm the loading of the Scenario. Figure 3-16: Scenario Loading Message Box 2.
SIP User's Manual 3. Web-Based Management To navigate between Scenario Steps, you can perform one of the following: In the Navigation tree, click the required Scenario Step. In an opened Scenario Step (i.e., page appears in the Work pane), use the following navigation buttons: • Next: opens the next Step listed in the Scenario. • Previous: opens the previous Step listed in the Scenario.
Mediant 1000 & Mediant 600 • • • • 3.3.5.4 Add or Remove Parameters: a. In the Navigation tree, select the required Step; the corresponding page opens in the Work pane. b. To add parameters, select the check boxes corresponding to the desired parameters; to remove parameters, clear the check boxes corresponding to the parameters that you want removed. c. Click Next. Edit the Step Name: a. In the Navigation tree, select the required Step. b. In the 'Step Name' field, modify the Step name. c.
SIP User's Manual 3. Web-Based Management ¾ To save a Scenario to a PC, take these 5 steps: 1. On the Navigation bar, click the Scenarios tab; the Scenario appears in the Navigation tree. 2. Click the Get/Send Scenario File button (located at the bottom of the Navigation tree); the 'Scenario File' page appears, as shown below: Figure 3-18: Scenario File Page 3. Click the Get Scenario File button; the 'File Download' window appears. 4.
Mediant 1000 & Mediant 600 3.3.5.5 Loading a Scenario to the Device Instead of creating a Scenario, you can load a Scenario file (data file) from your PC to the device. ¾ To load a Scenario to the device, take these 4 steps: 1. On the Navigation bar, click the Scenarios tab; the Scenario appears in the Navigation tree. 2. Click the Get/Send Scenario File button (located at the bottom of the Navigation tree); the 'Scenario File' page appears (refer to ''Saving a Scenario to a PC'' on page 44). 3.
SIP User's Manual 3. 3. Web-Based Management Click the Delete Scenario File button; a message box appears requesting confirmation for deletion. Figure 3-20: Message Box for Confirming Scenario Deletion 4. Click OK; the Scenario is deleted and the Scenario mode closes. Note: You can also delete a Scenario using the following alternative methods: 3.3.5.7 • Loading an empty dat file (refer to ''Loading a Scenario to the Device'' on page 46).
Mediant 1000 & Mediant 600 3.3.6 Customizing the Web Interface You can customize the device's Web interface to suit your company preferences. The following Web interface elements can be customized: 3.3.6.
SIP User's Manual 3. 3. Web-Based Management On the left pane, click Image Load to Device; the 'Image Download' page is displayed, as shown in the figure below: Figure 3-23: Image Download Screen 4. Click the Browse button, and then navigate to the folder in which the logo image file that you want to use is located. 5. Click the Send File button; the image file uploads to the device.
Mediant 1000 & Mediant 600 ¾ To replace the default logo with a different image using the ini file, take these 3 steps: 1. Place your corporate logo image file on the TFTP server in the same folder where the device’s ini file is located. 2. Configure the ini file parameters as described in the table below. (For a description on using the ini file, refer to ''Modifying an ini File'' on page 296.) 3. Load the ini file to the device using BootP / TFTP (i.e., not through the Web interface).
SIP User's Manual 3. Web-Based Management Table 3-4: ini File Parameters for Customizing Product Name Parameter UseProductName UserProductName 3.3.6.3 Description Defines whether or not to change the product name: [0] = Don’t change the product name (default). [1] = Enable product name change. The text string that replaces the product name. The default is ‘Mediant 1000’. The string can be up to 29 characters.
Mediant 1000 & Mediant 600 3.3.7 Getting Help The Web interface provides you with context-sensitive Online Help. The Online Help provides you with brief descriptions of most of the parameters you'll need to successfully configure the device. The Online Help provides descriptions of parameters pertaining to the currently opened page. ¾ To view the Help topic for a currently opened page, take these 4 steps: 1. Using the Navigation tree, open the required page for which you want Help. 2.
SIP User's Manual 3. Web-Based Management ¾ To access the Home page, take this step: On the toolbar, click the Home icon; the 'Home' page is displayed: Figure 3-26: Mediant 1000 Home Page Figure 3-27: Mediant 600 Home Page Note: The number and type of modules, trunks and channels displayed in the 'Home' page depends on the device's hardware configuration. Version 5.
Mediant 1000 & Mediant 600 The table below describes the areas of the 'Home' page. Table 3-6: Description of the Areas of the Mediant 1000 Home Page Item# / Label 1 Description Displays the highest severity of an active alarm raised (if any) by the device: Green = No alarms Red = Critical alarm Orange = Major alarm Yellow = Minor alarm To view a list of active alarms in the 'Active Alarms' page (refer to Viewing Active Alarms on page 282), click the Alarms area.
SIP User's Manual 3. Web-Based Management Item# / Label 5 Description Port (trunk or channel) status icon (refer to Monitoring the Mediant 1000 Trunks and Channels on page 59).
Mediant 1000 & Mediant 600 Table 3-7: Description of the Areas of the Mediant 600 Home Page Item# / Label 1 Description Displays the highest severity of an active alarm raised (if any) by the device: Green = No alarms Red = Critical alarm Orange = Major alarm Yellow = Minor alarm To view a list of active alarms in the 'Active Alarms' page (refer to Viewing Active Alarms on page 282), click the Alarms area. 2 Module type (Digital or BRI).
SIP User's Manual 3. Web-Based Management Item# / Label Description Ethernet port status icons: 9 (green): Ethernet link is working. (gray): Ethernet link not configured. You can also view detailed Ethernet port information in the 'Ethernet Port Information' page (refer to Viewing Ethernet Port Information on page 280), by clicking this icon. Fan tray unit status icon: 10 3.3.8.1 (green): Fan tray operating. Red: Fan tray failure.
Mediant 1000 & Mediant 600 3.3.8.2 Viewing Analog Port Information The 'Home' page allows you to view detailed information on a specific FXS or FXO (analog) port such as RTP/RTCP and voice settings. Note: This section is applicable only to Mediant 1000. ¾ To view detailed port information, take these 3 steps: 1. Click the port for which you want to view port settings; the shortcut menu appears. Figure 3-30: Selecting Port Settings from Shortcut Menu 2.
SIP User's Manual 3.3.8.3 3. Web-Based Management Resetting an Analog Channel The 'Home' page allows you to inactivate (reset) an FXO or FXS analog channel. This is sometimes useful in scenarios, for example, when the device (FXO) is connected to a PBX and the communication between the two can't be disconnected (e.g., when using reverse polarity). Note: This section is applicable only to Mediant 1000.
Mediant 1000 & Mediant 600 The color-coding for the status of the trunk's channels status is described in the table below: Table 3-8: Color-Coding Status for Trunk's Channels Icon Color Label Light blue Inactive Green Active Purple SS7 Grey Non Voice Blue Yellow Description Configured, but currently no call Call in progress (RTP traffic) Configured for SS7 (Currently not supported) Not configured ISDN Signaling Configured as a D-channel CAS Blocked -- 3.
SIP User's Manual 3.3.8.5 3. Web-Based Management Replacing Modules To replace the device's modules, you must use the Web interface in combination with physical removal and insertion of the modules. In other words, when you replace a module, you first need to 'software-remove' it, then extract it physically from the chassis and insert a new module, and then 'software-insert' it using the Web interface. The software removal and insertion is performed in the 'Home' page.
Mediant 1000 & Mediant 600 c. Click OK to confirm removal; after a few seconds, the module is softwareremoved, the module status icon turns to grey, and the name of the module is suffixed with the word 'Reserved': Figure 3-37: Removed Module d. 2. Physically remove the module (refer to the device's Fast Track Installation Guide). Insert the replaced module, by performing the following: a.
SIP User's Manual 2. 3. Web-Based Management Click OK; the Web session is logged off and the Log In button appears. Figure 3-40: Web Session Logged Off To log in again, simply click the Log In button, and then in the 'Enter Network Password' dialog box, enter your user name and password (refer to ''Accessing the Web Interface'' on page 26). Version 5.
Mediant 1000 & Mediant 600 3.4 Configuration Tab The Configuration tab on the Navigation bar displays all menus related to device configuration.
SIP User's Manual 3. Web-Based Management ¾ To configure the IP settings parameters, take these 4 steps: 1. Open the 'IP Settings' page (Configuration tab > Network Settings menu > IP Settings page item). Figure 3-41: IP Settings Page 2. Configure the IP parameters according to the table below. 3. Click the Submit button to save your changes. 4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. Version 5.
Mediant 1000 & Mediant 600 Table 3-9: Network Settings -- IP Settings Parameters Parameter Description IP Settings IP Networking Mode [EnableMultipleIPs] Determines the IP network scheme. [0] Single IP Network = Single IP network (default). [1] Multiple IP Networks = Multiple IP networks (OAMP, Media, and Control). [1] Dual IP (Media & Control) = Multiple IP networks. [1] Dual IP (OAM & Control) = Multiple IP networks. [1] Dual IP (OAM & Medial) = Multiple IP networks.
SIP User's Manual 3. Web-Based Management Parameter Description Control Network Settings (Available only in Multiple IP and Dual IP modes.) IP Address [LocalControlIPAddress] The device's source IP address in the Control network. The default value is 0.0.0.0. Subnet Mask The device's subnet mask in the Control network. [LocalControlSubnetMask] The default subnet mask is 0.0.0.0. Default Gateway Address [LocalControlDefaultGW] N/A.
Mediant 1000 & Mediant 600 3.4.1.2 Configuring the Multiple Interface Table The 'Multiple Interface Table' page allows you to configure up to three logical network interfaces, each with its own IP address, unique VLAN ID (if enabled), interface name, and application types (i.e., Control, Media, and/or Operations, Administration, Maintenance and Provisioning - OAMP) permitted on the interface.
SIP User's Manual 3. Web-Based Management Notes: • When adding more than one interface to the table, ensure that you enable VLANs, using the 'VLAN Mode' (VlANMode) parameter. • When booting using BootP/DHCP protocols (refer to the Product Reference Manual), an IP address is obtained from the server. This address is used as the OAMP address for this session, overriding the IP address you configured in the 'Multiple Interface Table' page.
Mediant 1000 & Mediant 600 Parameter PrefixLength Description This column lists the number of ‘1’ bits in the subnet mask (i.e., replaces the standard dotted-decimal representation of the subnet mask for IPv4 interfaces). For example: A subnet mask of 255.0.0.0 is represented by a prefix length of 8 (i.e., 11111111 00000000 00000000 00000000), and a subnet mask of 255.255.255.252 is represented by a prefix length of 30 (i.e., 11111111 11111111 11111111 11111100).
SIP User's Manual 3.4.1.3 3. Web-Based Management Configuring the Application Settings The 'Application Settings' page is used for configuring various application parameters such as Telnet. ¾ To configure the Application settings parameters, take these 4 steps: 1. Open the 'Application Settings' page (Configuration tab > Network Settings menu > Application Settings page item). Figure 3-44: Application Settings Page 2. Configure the Applications parameters according to the table below. 3.
Mediant 1000 & Mediant 600 Table 3-11: Application Settings Parameters Parameter Description NTP Settings (For detailed information on Network Time Protocol (NTP), refer to ''Simple Network Time Protocol Support'' on page 449.) NTP Server IP Address [NTPServerIP] IP address (in dotted-decimal notation) of the NTP server. The default IP address is 0.0.0.0 (i.e., internal NTP client is disabled).
SIP User's Manual 3. Web-Based Management Parameter Description STUN is used to discover whether the device is located behind a NAT and the type of NAT. In addition, it is used to determine the IP addresses and port numbers that the NAT assigns to outgoing signaling messages (using SIP) and media streams (using RTP, RTCP and T.38). STUN works with many existing NAT types and does not require any special behavior from them. For detailed information on STUN, refer to ''STUN'' on page 447.
Mediant 1000 & Mediant 600 3.4.1.4 Configuring the 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. You can configure up to five different NFS file systems. As a file system, the NFS is independent of machine types, OSs, and network architectures. NFS is used by the device to load the cmp, ini, and auxiliary files, using the Automatic Update mechanism (refer to Automatic Update Mechanism).
SIP User's Manual 3. Web-Based Management Table 3-12: Network Settings -- NFS Settings Parameters Parameter Description Index The row index of the remote file system. The valid range is 0 to 4. HostOrIP The domain name or IP address of the NFS server. If a domain name is provided, a DNS server must be configured. RootPath Path to the root of the remote file system in the format: /[path]. For example, '/audio'. NFSVersion NFS version used with the remote file system: 2 or 3 (default).
Mediant 1000 & Mediant 600 ¾ To configure static IP routing, take these 3 steps: 1. Open the 'IP Routing Table' page (Configuration tab > Network Settings menu > IP Routing Table page item). Figure 3-46: IP Routing Table Page 2. In the 'Add a new table entry' group, add a new static routing rule according to the parameters described in the table below. 3. Click Add New Entry; the new routing rule is added to the IP routing table.
SIP User's Manual 3. Web-Based Management Column Name [ini File Parameter Name] Description Gateway IP Address The IP address of the router (next hop) to which the packets are [RoutingTableGatewaysColum sent if their destination matches the rules in the adjacent columns. n] Note: The Gateway address must be in the same subnet on which the address is configured on the 'Multiple Interface Table' page (refer to ''Configuring the Multiple Interface Table'' on page 68).
Mediant 1000 & Mediant 600 3.4.1.6 Configuring the QoS Settings The 'QoS Settings' page is used for configuring the Quality of Service (QoS) parameters. This page allows you to assign VLAN priorities (IEEE 802.1p) and Differentiated Services (DiffServ) for the supported Class of Service (CoS). ¾ To configure QoS, take these 4 steps: 1. Open the 'QoS Settings' page (Configuration tab > Network Settings menu > QoS Settings page item). Figure 3-47: QoS Settings Page 2.
SIP User's Manual 3. Web-Based Management Parameter Description Bronze Priority Defines the priority for the Bronze CoS content. [VLANBronzeServiceClass The valid range is 0 to 7. The default value is 2. Priority] Differential Services (For detailed information on IP QoS using Differentiated Services, refer to ''IP QoS via Differentiated Services (DiffServ)'' on page 450). Network QoS Defines the DiffServ value for Network CoS content. [NetworkServiceClassDiff The valid range is 0 to 63.
Mediant 1000 & Mediant 600 3.4.2 Media Settings The Media Settings menu allows you to configure the device's channel parameters. These parameters are applied to all the device's channels.
SIP User's Manual 3.4.2.1 3. Web-Based Management Configuring the Voice Settings The 'Voice Settings' page is used for configuring various voice parameters such as voice volume. ¾ To configure the Voice parameters, take these 4 steps: 1. Open the 'Voice Settings' page (Configuration tab > Media Settings menu > Voice Settings page item). Figure 3-48: Voice Settings Page 2. Configure the Voice parameters according to the table below. 3. Click the Submit button to save your changes. 4.
Mediant 1000 & Mediant 600 Parameter Description Silence Suppression Silence Suppression is a method for conserving bandwidth on VoIP [EnableSilenceCompression calls by not sending packets when silence is detected. ] [0] Disable = Silence Suppression is disabled (default). [1] Enable = Silence Suppression is enabled. [2] Enable without Adaptation = A single silence packet is sent during a silence period (applicable only to G.729). Note: If the selected coder is G.
SIP User's Manual 3. Web-Based Management Parameter Description Answer Detector Sensitivity Determines the Answer Detector sensitivity. [AnswerDetectorSensitivity] The range is 0 (most sensitive) to 2 (least sensitive). The default is 0. CAS Transport Type [CASTransportType] Controls the ABCD signaling transport type over IP. [0] CAS Events Only = Disable CAS relay (default). [1] CAS RFC2833 Relay = Enable CAS relay mode using RFC 2833.
Mediant 1000 & Mediant 600 3.4.2.2 Configuring the Fax / Modem / CID Settings The 'Fax/Modem/CID Settings' page is used for configuring fax, modem, and Caller ID (CID) parameters. ¾ To configure the fax, modem, and CID parameters, take these 4 steps: 1. Open the 'Fax/Modem/CID Settings' page (Configuration tab > Media Settings menu > Fax/Modem/CID Settings page item). Figure 3-49: Fax/Modem/CID Settings Page 2. Configure the fax, Modem, and CID parameters according to the table below. 3.
SIP User's Manual 3. Web-Based Management Parameter Description Caller ID Transport Type Determines the device's behavior for Caller ID detection. [CallerIDTransportTyp [0] Disable = Caller ID is not detected - DTMF digits remain in the voice e] stream. Caller ID Type [CallerIDType] [1] Relay = Caller ID is detected - DTMF digits are erased from the voice stream. [3] Mute = Caller ID is detected - DTMF digits are erased from the voice stream (default).
Mediant 1000 & Mediant 600 Parameter Description V.23 Modem Transport V.23 Modem Transport Type used by the device. Type [0] Disable = Disable (Transparent) [V23ModemTransportT [1] Enable Relay = N/A ype] [2] Enable Bypass = (default) [3] Events Only = Transparent with Events V.32 Modem Transport V.32 Modem Transport Type used by the device.
SIP User's Manual 3. Web-Based Management Parameter Description Fax/Modem Bypass Coder used by the device when performing fax/modem bypass. Usually, Coder Type high-bit-rate coders such as G.711 should be used. [FaxModemBypassCo [0] G.711Alaw= G.711 A-law 64 (default). derType] [1] G.711Mulaw = G.711 µ-law. Fax/Modem Bypass Packing Factor [FaxModemBypassM] Number of (20 msec) coder payloads that are used to generate a fax/modem bypass packet. The valid range is 1, 2, or 3 coder payloads.
Mediant 1000 & Mediant 600 3.4.2.3 Configuring the RTP / RTCP Settings The 'RTP/RTCP Settings' page allows you to configure the Real-Time Transport Protocol (RTP) and Real-Time Transport (RTP) Control Protocol (RTCP) parameters. ¾ To configure the RTP / RTCP parameters, take these 4 steps: 1. Open the 'RTP/RTCP Settings' page (Configuration tab > Media Settings menu > RTP / RTCP Settings page item). Figure 3-50: RTP/RTCP Settings Page 2.
SIP User's Manual 3. Web-Based Management Table 3-17: Media Settings, RTP / RTCP Parameters Parameter Description Dynamic Jitter Buffer Minimum Delay [DJBufMinDelay] Minimum delay (in msec) for the Dynamic Jitter Buffer. The valid range is 0 to 150. The default delay is 10. Dynamic Jitter Buffer Optimization Factor [DJBufOptFactor] Dynamic Jitter Buffer frame error / delay optimization factor. The valid range is 0 to 13. The default factor is 10.
Mediant 1000 & Mediant 600 Parameter Comfort Noise Generation Negotiation [ComfortNoiseNegotiation] Description Enables negotiation and usage of Comfort Noise (CN). [0] Disable = Disable (default). [1] Enable = Enable. The use of CN is indicated by including a payload type for CN on the media description line of the SDP. The device can use CN with a codec whose RTP timestamp clock rate is 8,000 Hz (G.711/G.726). The static payload type 13 is used. The use of CN is negotiated between sides.
SIP User's Manual 3. Web-Based Management Parameter Description RTP Multiplexing Local UDP Port Determines the local UDP port used for outgoing multiplexed RTP packets (applies to RTP multiplexing). [L1L1ComplexTxUDPPort] The valid range is the range of possible UDP ports: 6,000 to 64,000. The default value is 0 (i.e., RTP multiplexing is disabled). This parameter cannot be changed on-the-fly and requires a device reset.
Mediant 1000 & Mediant 600 3.4.2.4 Configuring the IPmedia Settings The 'IPMedia Settings' page allows you to configure the IP media parameters. ¾ To configure the IP media parameters, take these 4 steps: 1. Open the 'IPMedia Settings' page (Configuration tab > Media Settings menu > IPmedia Settings page item). Figure 3-51: IPMedia Settings Page 2. Configure the IP media parameters according to the table below. 3. Click the Submit button to save your changes. 4.
SIP User's Manual 3. Web-Based Management Parameter Description Answer Detector Redirection [AnswerDetectorRedirection] N/A. Answer Detector Sensitivity [AnswerDetectorSensitivity] Determines the Answer Detector sensitivity. The range is 0 (most sensitive) to 2 (least sensitive). The default is 0.
Mediant 1000 & Mediant 600 Table 3-19: Media Settings Parameters Parameter Description Max Echo Canceller Length [MaxEchoCancellerLength] Maximum Echo Canceler Length (in msec): [0] Default = based on various internal device settings to attain maximum channel capacity (default) [11] = 64 msec [22] = 128 msec Notes: Enable Continuity Tones 3.4.2.6 Mediant 1000 with analog / BRI module can use a max. echo canceller length of 64 msec. Mediant 1000 with PRI can use a max.
SIP User's Manual 3. Web-Based Management Table 3-20: Hook-Flash Settings Parameters Parameter Description Min. Flash-Hook Detection Period Defines the minimum time (in msec) for detection of a hook-flash [msec] event. The valid range is 25 to 300. The default value is 300. [MinFlashHookTime] Detection is guaranteed for hook-flash periods of at least 60 msec (when setting the minimum time to 25). Hook-flash signals that last a shorter period of time are ignored.
Mediant 1000 & Mediant 600 3.4.3 PSTN Settings The PSTN Settings menu allows you to configure various PSTN settings and includes the following page items: 3.4.3.1 Trunk Settings (refer to ''Configuring the Trunk Settings'' on page 96) CAS State Machines (refer to ''Configuring the CAS State Machines'' on page 109) Configuring the Trunk Settings The 'Trunk Settings' page allows you to configure the device's trunks.
SIP User's Manual 3. Web-Based Management On the top of the page, a bar with Trunk number icons displays the status of each trunk, according to the following color codes: 2. • Grey: Disabled • Green: Active • Yellow: RAI alarm • Red: LOS / LOF alarm • Blue: AIS alarm • Orange: D-channel alarm (ISDN only) Select the trunk that you want to configure, by clicking the desired Trunk number icon. The bar initially displays the first eight trunk number icons (i.e., trunks 1 through 8).
Mediant 1000 & Mediant 600 5. Click Apply Trunk Settings to apply the changes to the selected trunk (or click Apply to all Trunks to apply the changes to all trunks); the Stop Trunk button replaces Apply Trunk Settings and the ‘Trunk Configuration State’ displays 'Active'. 6. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. 7. To reset the device, refer to ''Resetting the Device'' on page 262. Notes: • If the ‘Protocol Type’ field displays 'NONE' (i.e.
SIP User's Manual 3.
Mediant 1000 & Mediant 600 ini File Field Name Web Parameter Name Line Build Out Loss [LineBuildOut.Loss] Valid Range and Description Defines the line build out loss for the selected T1 trunk. [0] 0 dB (default) [1] -7.5 dB [2] -15 dB [3] -22.5 dB Note: This parameter is not applicable for PRI E1 and BRI trunks. Trace Level [TraceLevel] Framing Method [FramingMethod] Defines the trace level: [0] No Trace (default) [1] Full ISDN Trace [2] Layer 3 ISDN Trace [3] Only ISDN Q.
SIP User's Manual 3. Web-Based Management ini File Field Name Web Parameter Name BRI Layer 2 Mode [BriLayer2Mode] NFAS Group Number [NFASGroupNumber_x] Valid Range and Description Determines whether Point-to-Point or Point-to-Multipoint mode for BRI ports. [0] Point to Point (default) [1] Point to Multipoint = Must be configured for Network side. Indicates the NFAS group number (NFAS member) for the selected trunk. 'x' identifies the Trunk ID.
Mediant 1000 & Mediant 600 ini File Field Name Web Parameter Name Enable Receiving of Overlap Dialing [ISDNRxOverlap_x] Valid Range and Description Enables Rx ISDN overlap per trunk ID. [0] Disable = Disabled (default). [1] Enable = Enabled. Notes: If enabled, the device receives ISDN called number that is sent in the 'Overlap' mode. The SETUP message to IP is sent only after the number (including the Sending Complete IE) is fully received (via SETUP and/or subsequent INFO Q.931 messages).
SIP User's Manual 3. Web-Based Management ini File Field Name Web Parameter Name Valid Range and Description ISDN Transfer Capabilities Defines the IP-to-ISDN Transfer Capability of the Bearer Capability IE in [ISDNTransferCapability_ ISDN SETUP messages. The ID in the ini file parameter depicts the trunk number. ID] [-1] Not Configured [0] Audio 3.1 = Audio (default). [1] Speech = Speech. [2] Data = Data. Audio 7 = Currently not supported.
Mediant 1000 & Mediant 600 ini File Field Name Web Parameter Name Valid Range and Description the D-channel. Note: Applicable to 4/5ESS, DMS and NI-2 variants. [32768] ACCEPT MU LAW =Mu-Law is also accepted in ETSI. [65536] EXPLICIT PRES SCREENING = The calling party number (octet 3a) is always present even when presentation and screening are at their default. Note: Applicable only to ETSI, NI-2, and 5ESS. [131072] STATUS INCOMPATIBLE STATE = Clears the call on receipt of Q.
SIP User's Manual 3. Web-Based Management ini File Field Name Web Parameter Name Valid Range and Description indicates an unused channel ID, preferred only. [572] USE A LAW = When set, the device sends G.711 A-Law in outgoing voice calls. When disabled, the device sends the default G.711-Law in outgoing voice calls. Applicable to E10 variant. [1024] = Numbering plan / type for T1 IP-to-Tel calling numbers are defined according to the manipulation tables or according to the RPID header (default).
Mediant 1000 & Mediant 600 ini File Field Name Web Parameter Name Valid Range and Description [8] REVERSE CHAN ALLOC ALGO = Channel ID allocation algorithm. [16] = The device clears down the call if it receives a NOTIFY message specifying 'User-Suspended'. A NOTIFY (User-Suspended) message is used by some networks (e.g., in Italy or Denmark) to indicate that the remote user has cleared the call, especially in the case of a long distance voice call.
SIP User's Manual 3. Web-Based Management ini File Field Name Web Parameter Name Valid Range and Description ''E1/T1 Configuration Parameters'' on page 344. This parameter is not applicable to BRI interfaces. Dial Plan The Dial Plan name that is used on a specific trunk. [CasTrunkDialPlanName] The range is up to 11 character strings. Note: This parameter is not applicable to BRI interfaces. Miscellaneous PSTN Alert Timeout Alert Timeout (ISDN T301 timer) in seconds for outgoing calls to PSTN.
Mediant 1000 & Mediant 600 ini File Field Name Web Parameter Name Valid Range and Description 1) If the device receives a 180 Ringing response (with or without SDP) and LocalISDNRBSource = 1, it plays an RBT and sends an Alert with PI = 8 (unless the parameter ProgressIndicator2ISDN_ID is configured differently). 2) If LocalISDNRBSource = 0, the device doesn't play an RBT and an Alert message (without PI) is sent to the ISDN.
SIP User's Manual 3. Web-Based Management ini File Field Name Web Parameter Name Valid Range and Description RTP Only Mode Enables the device to start sending and/or receiving RTP packets to and [RTPOnlyModeForTrunk_ from remote endpoints without the need to establish a Control session. The remote IP address is determined according to the 'Tel to IP Routing' ID] table. The port is the same port as the local RTP port (configured by the parameter BaseUDPPort and the channel on which the call is received).
Mediant 1000 & Mediant 600 ¾ To modify the CAS state machine parameters, take these 6 steps: 1. Open the ‘CAS State Machine' page (Configuration tab > PSTN Settings menu > CAS State Machines page item). Figure 3-56: CAS State Machine Page 2. Ensure that the trunk is inactive. The trunk number displayed in the 'Related Trunks' field must be green.
SIP User's Manual 3. Web-Based Management Table 3-22: CAS State Machine Parameters Description Parameter Description Generate Digit On Time Generates digit on-time (in msec). [CasStateMachineGenerateD The value must be a positive value. The default value is -1. igitOnTime] Generate Inter Digit Time Generates digit off-time (in msec). [CasStateMachineGenerateIn The value must be a positive value. The default value is -1.
Mediant 1000 & Mediant 600 3.4.4.
SIP User's Manual 3. Web-Based Management ¾ To change the Web user accounts attributes, take these 4 steps: 1. Open the 'Web User Accounts' page (Configuration tab > Security Settings menu > Web User Accounts page item). Figure 3-57: Web User Accounts Page (for Users with 'Security Administrator' Privileges) 2.
Mediant 1000 & Mediant 600 Notes: 3.4.4.2 • For security, it's recommended that you change the default user name and password used for initially accessing the Web interface. • The access level of the primary Web user account is 'Security Administrator', which cannot be modified; all its' other account-attributes can be modified. • A Web user with access level 'Security Administrator' can change all attributes of all the Web user accounts.
SIP User's Manual 2. 3. Web-Based Management To add an authorized IP address, in the 'Add a New Authorized IP Address' field, enter the required IP address, and then click Add New Address; the IP address you entered is added as a new entry to the 'Web & Telnet Access List' table. Figure 3-59: Web & Telnet Access List Table 3.
Mediant 1000 & Mediant 600 3.4.4.3 Configuring the Firewall Settings The device provides an internal firewall, allowing you (the security administrator) to define network traffic filtering rules. You can add up to 50 ordered firewall rules. For each packet received on the network interface, the table is scanned from the top down until a matching rule is found. This rule can either deny (block) or permit (allow) the packet.
SIP User's Manual 3. Web-Based Management ¾ To edit a rule, take these 4 steps: 1. In the 'Edit Rule' column, select the rule that you want to edit. 2. Modify the fields as desired. 3. Click the Apply button to save the changes. 4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. ¾ To activate a de-activated rule, take these 2 steps: 1. In the 'Edit Rule' column, select the de-activated rule that you want to activate. 2.
Mediant 1000 & Mediant 600 Parameter Packet Size [AccessList_Packet_Size] Description Maximum allowed packet size. The valid range is 0 to 65535. Note: When filtering fragmented IP packets, this field relates to the overall (re-assembled) packet size, and not to the size of each fragment. Byte Rate [AccessList_Byte_Rate] Expected traffic rate (bytes per second). Burst Bytes [AccessList_Byte_Burst] Tolerance of traffic rate limit (number of bytes).
SIP User's Manual 3. Web-Based Management ¾ To replace the device's self-signed certificate, take these 8 steps: 1. Your network administrator should allocate a unique DNS name for the device (e.g., dns_name.corp.customer.com). This name is used to access the device, and should therefore be listed in the server certificate. 2. Open the ‘Certificates Signing Request' page (Configuration tab > Security Settings menu > Certificates page item). Figure 3-61: Certificates Signing Request Page 3.
Mediant 1000 & Mediant 600 7. In the 'Certificates Files' group, click the Browse button corresponding to 'Send Server Certificate...', navigate to the cert.txt file, and then click Send File. 8. When the loading of the certificate is completed, save the configuration (refer to ''Saving Configuration'' on page 265) and restart the device; the Web interface uses the provided certificate. Notes: • The certificate replacement process can be repeated when necessary (e.g., the new certificate expires).
SIP User's Manual 3. Web-Based Management When a user connects to the secured Web server: If the user has a client certificate from a CA that is listed in the Trusted Root Certificate file, the connection is accepted and the user is prompted for the system password. If both the CA certificate and the client certificate appear in the Trusted Root Certificate file, the user is not prompted for a password (thus, providing a single-signon experience - the authentication is performed using the X.
Mediant 1000 & Mediant 600 ¾ To export the current server certificate to a file using Microsoft Internet Explorer, take these 6 steps: 1. Access the device's Web interface. 2. Double-click the yellow padlock icon displayed at the bottom of the Browser's window. 3. Select the 'Details' tab, and then click Copy to file. 4. Click Next, select 'Base64-encoded X.509', and then click Next. 5. Select a file name, and then click Next. 6. Click Finish; the certificate is saved to the selected file name.
SIP User's Manual 3.4.4.5 3. Web-Based Management Configuring the General Security Settings The 'General Security Settings' page is used to configure various security features. ¾ To configure the general security parameters, take these 4 steps: 1. Open the 'General Security Settings' page (Configuration tab > Security Settings menu > General Security Settings page item). Figure 3-62: General Security Settings Page 2. Configure the General Security parameters according to the table below. 3.
Mediant 1000 & Mediant 600 Table 3-26: General Security Parameters Parameter HTTP Authentication Mode [WebAuthMode] Description Determines the authentication mode for the Web interface. [0] Basic Mode = Basic authentication (clear text) is used (default). [1] Digest When Possible = Digest authentication (MD5) is used. [2] Basic if HTTPS, Digest if HTTP = Digest authentication (MD5) is used for HTTP, and basic authentication is used for HTTPS. Note: When RADIUS login is enabled (i.e.
SIP User's Manual 3. Web-Based Management Parameter Description RADIUS Authentication Server IP address of the RADIUS authentication server. IP Address [RADIUSAuthServerIP] RADIUS Authentication Server Port number of the RADIUS authentication server. Port The default value is 1645. [RADIUSAuthPort] RADIUS Shared Secret [SharedSecret] 'Secret' used to authenticate the device to the RADIUS server. Should be a cryptographically strong password.
Mediant 1000 & Mediant 600 Parameter Description SRTP Setting Media Security [EnableMediaSecurity] Media Security Behavior [MediaSecurityBehaviour] Enables Secure Real-Time Transport Protocol (SRTP). [0] Disable = SRTP is disabled (default). [1] Enable = SRTP is enabled. Determines the device's mode of operation when SRTP is used (EnableMediaSecurity = 1). [0] Preferable = The device initiates encrypted calls. If negotiation of the cipher suite fails, an unencrypted call is established.
SIP User's Manual 3. Web-Based Management ¾ To configure the IPSec SPD table, take these 5 steps: 1. Open the ‘IPSec Table’ page (Configuration tab > Security Settings menu > IPSec Table page item). Figure 3-63: IPSec Table Page 2. From the ‘Policy Index’ drop-down list, select the rule you want to edit (up to 20 policy rules can be configured). 3. Configure the IPSec SPD parameters according to the table below. 4. Click the button Create; the IPSec rule is applied on-the-fly to the device. 5.
Mediant 1000 & Mediant 600 Table 3-28: IPSec SPD Table Configuration Parameters Parameter Name IPSec Mode [IPSecMode] Description Defines the IPSec mode of operation. [0] Transport (Default) [1] Tunneling Remote Tunnel IP Address Defines the IP address of the remote IPSec [IPSecPolicyRemoteTunne tunneling device. lIPAddress] Note: This parameter is only available if the parameter IPSecMode is set to Tunneling (1).
SIP User's Manual 3. Web-Based Management Parameter Name Description IKE Second Phase Parameters (Quick Mode) SA Lifetime (sec) [PsecPolicyLifeInSec] Determines the time (in seconds) that the SA negotiated in the second IKE session (quick mode) is valid. After the time expires, the SA is renegotiated. The default value is 28,800 (i.e., 8 hours). SA Lifetime (KB) [IPSecPolicyLifeInKB] Determines the lifetime (in kilobytes) that the SA negotiated in the second IKE session (quick mode) is valid.
Mediant 1000 & Mediant 600 3.4.4.7 Configuring the IKE Table The 'IKE Table' page is used to configure the Internet Key Exchange (IKE) parameters. Note: You can also configure the IKE table using the ini file table parameter IPSec_IKEDB_Table (refer to ''Security Parameters'' on page 314). ¾ To configure the IKE table, take these 5 steps: 1. Open the ‘IKE Table’ page (Configuration tab > Security Settings menu > IKE Table page item). Figure 3-64: IKE Table Page 2.
SIP User's Manual 3. Web-Based Management If no IKE methods are defined (Encryption / Authentication / DH Group), the default settings (shown in the following table) are applied.
Mediant 1000 & Mediant 600 Parameter Name IKE SA LifeTime (KB) Description Determines the lifetime (in kilobytes) that the SA negotiated in the first IKE session (main mode) is valid. After this size is reached, the SA is re-negotiated. The default value is 0 (i.e., this parameter is ignored). These lifetime parameters [IKE SA LifeTime (sec) and IKE SA LifeTime (KB)] determine the duration the SA created in the main mode phase is valid.
SIP User's Manual 3.4.5 3. Web-Based Management Protocol Configuration The Protocol Configuration menu allows you to configure the device's SIP parameters and contains the following submenus: 3.4.5.
Mediant 1000 & Mediant 600 3.4.5.1.1 SIP General Parameters The 'SIP General Parameters' page is used to configure general SIP parameters. ¾ To configure the general SIP protocol parameters, take these 4 steps: 1. Open the 'SIP General Parameters' page (Configuration tab > Protocol Configuration menu > Protocol Definition submenu > SIP General Parameters page item).
SIP User's Manual 3. Web-Based Management 2. Configure the parameters according to the table below. 3. Click the Submit button to save your changes. 4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. Table 3-31: SIP General Parameters (Protocol Definition) Parameter PRACK Mode [PRACKMode] Description PRACK (Provisional Acknowledgment) mechanism mode for 1xx SIP reliable responses. [0] Disable [1] Supported (default) [2] Required Notes: Version 5.
Mediant 1000 & Mediant 600 Parameter Channel Select Mode [ChannelSelectMode] Description Port (channel) allocation algorithm for IP-to-Tel calls. [0] By Dest Phone Number = Selects the device's channel according to the called number (defined in the 'Endpoint Phone Number' table -Configuring the Endpoint Phone Numbers). (default.) [1] Cyclic Ascending = Selects the next available channel in an ascending cyclic order. Always selects the next higher channel number in the trunk group.
SIP User's Manual 3. Web-Based Management Parameter 183 Message Behavior [SIP183Behaviour] Description Defines the ISDN message that is sent when the 183 Session Progress message is received for IP-to-Tel calls. [0] Progress = The device sends a PROGRESS message (default). [1] Alert = The device sends an ALERT message (upon receipt of a 183 response) instead of an ISDN PROGRESS message.
Mediant 1000 & Mediant 600 Parameter Fax Signaling Method [IsFaxUsed] Description Determines the SIP signaling method for establishing and transmitting a fax session after a fax is detected. [0] No Fax = No fax negotiation using SIP signaling. Fax transport method is according to the parameter FaxTransportMode (default). [1] T.38 Relay = Initiates T.38 fax relay. [2] G.711 Transport = Initiates fax / modem using the coder G.711 Alaw/µ-law with adaptations (refer to Note below).
SIP User's Manual 3. Web-Based Management Parameter Description SIP TCP Local Port [TCPLocalSIPPort] Local TCP port for SIP messages. The valid range is 1 to 65534. The default value is 5060. SIP TLS Local Port [TLSLocalSIPPort] Local TLS port for SIP messages. The valid range is 1 to 65534. The default value is 5061. Note: The value of must be different than the value of 'SIP TCP Local Port' (TCPLocalSIPPort). Enable SIPS [EnableSIPS] Enables secured SIP (SIPS URI) connections over multiple hops.
Mediant 1000 & Mediant 600 Parameter Description Add Number Plan and Determines whether the TON/PLAN parameters are included in the Type to Remote Party ID Remote-Party-ID (RPID) header. Header [0] No [AddTON2RPI] [1] Yes (default) If RPID header is enabled (EnableRPIHeader = 1) and AddTON2RPI = 1, it's possible to configure the calling and called number type and number plan using the Number Manipulation tables for Tel-to-IP calls.
SIP User's Manual 3. Web-Based Management Parameter Description Use Source Number as Determines the use of Tel Source Number and Display Name for Tel-to-IP Display Name calls. [UseSourceNumberAsD [0] No = If a Tel Display Name is received, the Tel Source Number is isplayName] used as the IP Source Number and the Tel Display Name is used as the IP Display Name. If no Display Name is received from the Tel side, the IP Display Name remains empty (default).
Mediant 1000 & Mediant 600 Parameter Description Play Ringback Tone to IP Determines whether or not the device plays a ringback tone (RBT) to the IP side of the call (IP-to-Tel calls). [PlayRBTone2IP] [0] Don't Play = Ringback tone isn't played (default). [1] Play = Ringback tone is played after SIP 183 session progress response is sent.
SIP User's Manual 3. Web-Based Management Parameter Enable GRUU [EnableGRUU] Description Determines whether the Globally Routable User Agent URIs (GRUU) mechanism is used. [0] Disable = Disable (default) [1] Enable = Enable The device obtains a GRUU by generating a normal REGISTER request. This request contains a Supported header with the value 'gruu'. The device includes a '+sip.instance' Contact header parameter for each contact for which the GRUU is desired.
Mediant 1000 & Mediant 600 Parameter Play Busy Tone to Tel [PlayBusyTone2ISDN] Description Enables the device to play a busy or reorder tone to the PSTN after a Telto-IP call is released. [0] Don't Play = Immediately sends an ISDN Disconnect message (default). [1] Play when Disconnecting = Sends an ISDN Disconnect message with PI = 8 and plays a busy or reorder tone to the PSTN (depending on the release cause).
SIP User's Manual 3. Web-Based Management Parameter Enable VoiceMail URI [EnableVMURI] Description Enables or disables the interworking of target and cause for redirection from Tel to IP and vice versa, according to RFC 4468. [0] Disable = Disable (default). [1] Enable = Enable Upon receipt of an ISDN SETUP message with redirect values, the device maps the Redirect phone number to the SIP 'target' parameter and the Redirect number reason to the SIP 'cause' parameter in the Request-URI.
Mediant 1000 & Mediant 600 Parameter SIP Maximum RTX [SIPMaxRtx] Description Maximum number of UDP transmissions (first transmission plus retransmissions) of SIP messages. The range is 1 to 30. The default value is 7. 3.4.5.1.2 Proxy & Registration Parameters The 'Proxy & Registration' page allows you to configure parameters that are associated with Proxy and Registration.
SIP User's Manual 3. Web-Based Management Table 3-32: Proxy & Registration Parameters Parameter Use Default Proxy [IsProxyUsed] Description Enables the use of a SIP Proxy server. [0] Don't Use Proxy = Proxy isn't used - the internal routing table is used instead (default). [1] Use Proxy = Proxy is used. Parameters relevant to Proxy configuration are displayed.
Mediant 1000 & Mediant 600 Parameter Prefer Routing Table [PreferRouteTable] Description Determines if the 'Tel to IP Routing' table takes precedence over a Proxy for routing calls. [0] No = Only Proxy is used to route calls (default). [1] Yes = The device checks the 'Dest Phone Prefix' and/or 'Source Phone Prefix' fields in the 'Tel to IP Routing' table for a match with the Tel-to-IP call. Only if a match is not found, a Proxy is used.
SIP User's Manual 3. Web-Based Management Parameter Description Registrar Transport Determines the transport layer used for outgoing SIP dialogs initiated by the Type device to the Registrar. [RegistrarTransportT [-1] Not Configured (default) ype] [0] UDP [1] TCP [2] TLS Note: When set to ‘Not Configured’, the value of the parameter SIPTransportType is used. Registrar IP Address [RegistrarIP] The IP address (or FQDN) and optionally, port number of the SIP Registrar server.
Mediant 1000 & Mediant 600 Parameter Description Registration Time Threshold [RegistrationTimeThr eshold] Defines a threshold (in seconds) for re-registration timing. If this parameter is greater than 0, but lower than the computed re-registration timing (according to the parameter RegistrationTimeDivider), the re-registration timing is set to the following: timing set by the Registration server in the Expires header minus the value of the parameter RegistrationTimeThreshold.
SIP User's Manual 3. Web-Based Management Parameter Description Proxy DNS Query Type Enables the use of DNS Naming Authority Pointer (NAPTR) and Service [ProxyDNSQueryType Record (SRV) queries to discover Proxy servers. ] [0] A-Record = A-Record (default) [1] SRV = SRV [2] NAPTR = NAPTR If set to A-Record [0], no NAPTR or SRV queries are performed. If set to SRV [1] and the Proxy IP address parameter contains a domain name without port definition (e.g., ProxyIP = domain.
Mediant 1000 & Mediant 600 Parameter User Name [UserName] Description User name used for Registration and Basic/Digest authentication with a Proxy / Registrar server. The parameter doesn't have a default value (empty string). Notes: Password [Password] Applicable only if single device registration is used (i.e., Authentication Mode is set to Authentication Per gateway). For Mediant 1000: The Authentication table can be used instead (refer to Authentication on page 219).
SIP User's Manual 3. Web-Based Management Parameter Description Challenge Caching Mode [SIPChallengeCachin gMode] Determines the mode for Challenge Caching, which reduces the number of SIP messages transmitted through the network. The first request to the Proxy is sent without authorization. The Proxy sends a 401/407 response with a challenge. This response is saved for further uses. A new request is resent with the appropriate credentials.
Mediant 1000 & Mediant 600 ¾ To add Proxy servers and configure Proxy parameters, take these 5 steps: 1. Open the 'Proxy Sets Table' page (Configuration tab > Protocol Configuration menu > Protocol Definition submenu > Proxy Sets Table page item). Figure 3-66: Proxy Sets Table Page 2. From the Proxy Set ID drop-down list, select an ID for the desired group. 3. Configure the Proxy parameters according to the following table. 4. Click the Submit button to save your changes. 5.
SIP User's Manual 3. Web-Based Management Parameter Description To summarize, if the default Proxy Set is used, the INVITE message is sent according to the following preferences: To the Trunk Group's ServingIPGroupID, as defined in the 'Trunk Group Settings' table. According to the 'Tel to IP Routing' table, if the parameter PreferRouteTable is set to 1. To the default Proxy.
Mediant 1000 & Mediant 600 Parameter Description Proxy Load Balancing Enables the Proxy Load Balancing mechanism per Proxy Set ID. Method [0] Disable = Load Balancing is disabled (default). [ProxyLoadBalancing [1] Round Robin = Round Robin. Method] [2] Random Weights = Random Weights. When the Round Robin algorithm is used, a list of all possible Proxy IP addresses is compiled.
SIP User's Manual 3. Web-Based Management Parameter Description Proxy Keep Alive Time Defines the Proxy keep-alive time interval (in seconds) between Keep-Alive [ProxyKeepAliveTime] messages. This parameter is configured per Proxy Set. The valid range is 5 to 2,000,000. The default value is 60. Note: This parameter is applicable only if the parameter EnableProxyKeepAlive is set to 1 (OPTIONS).
Mediant 1000 & Mediant 600 The coders supported by the device are listed in the table below: Table 3-34: Supported Coders Coder Name Packetization Time Rate Payload Type Silence Suppression • Always 8 Disable [0] Enable [1] G.711 A-law [g711Alaw64k] 10, 20 (default), 30, 40, 50, 60, 80, 100, 120 Always 64 G.711 µ-law [g711Ulaw64k] 10, 20 (default), 30, 40, 50, 60, 80, 100, 120 Always 64 EG.711 A-law [eg711Alaw] 10 (default), 20 Always 64 Dynamic (0-120) N/A EG.
SIP User's Manual 3. Web-Based Management ¾ To configure the device's coders, take these 9 steps: 1. Open the 'Coders' page (Configuration tab > Protocol Configuration menu > Protocol Definition submenu > Coders page item). Figure 3-67: Coders Page 2. From the 'Coder Name' drop-down list, select the coder you want to use. For the full list of available coders and their corresponding attributes, refer to the table below. 3.
Mediant 1000 & Mediant 600 3.4.5.1.5 DTMF & Dialing Parameters The 'DTMF & Dialing' page is used to configure parameters associated with dual-tone multi-frequency (DTMF) and dialing. ¾ To configure the DTMF and dialing parameters, take these 4 steps: 1. Open the 'DTMF & Dialing' page (Configuration tab > Protocol Configuration menu > Protocol Definition submenu > DTMF & Dialing page item). Figure 3-68: DTMF & Dialing Page 2. Configure the DTMF and dialing parameters according to the table below. 3.
SIP User's Manual 3. Web-Based Management Table 3-35: DTMF and Dialing Parameters Parameter Description Max Digits in Phone Num Defines the maximum number of collected destination number digits that can be received (i.e., dialed) from the Tel side when Tel-to-IP overlap [MaxDigits] dialing is performed (ISDN uses overlap dialing). When the number of collected digits reaches the maximum, the device uses these digits for the called destination number. The valid range is 1 to 49.
Mediant 1000 & Mediant 600 Parameter Description 1st to 5th Tx DTMF Option Determines a single or several preferred transmit DTMF negotiation methods. [TxDTMFOption] [0] Not Supported = No negotiation - DTMF digits are sent according to the parameters DTMFTransportType and RFC2833PayloadType (default). [1] INFO (Nortel) = Sends DTMF digits according to IETF . [2] NOTIFY = Sends DTMF digits according to .
SIP User's Manual 3. Web-Based Management Parameter Hook-Flash Option [HookFlashOption] Description Determines the supported hook-flash Transport Type (i.e., method by which hook-flash is sent and received). [0] Not Supported = Hook-Flash indication isn't sent (default). [1] INFO = Send proprietary INFO message with Hook-Flash indication. [4] RFC 2833 [5] INFO (Lucent) = Send proprietary INFO message with Hook-Flash indication.
Mediant 1000 & Mediant 600 Parameter Description Dial Tone Duration [sec] [TimeForDialTone] Duration (in seconds) that the dial tone is played (for digital interface: to an ISDN terminal). For digital interfaces: This parameter is applicable for overlap dialing when ISDNInCallsBehavior = 65536. The dial tone is played if the ISDN SETUP message doesn't include the called number. The valid range is 0 to 60. The default is 5.
SIP User's Manual 3.4.5.2 3. Web-Based Management Configuring the SIP Advanced Parameters The SIP Advanced Parameters submenu allows you to configure advanced SIP control protocol parameters.
Mediant 1000 & Mediant 600 3.4.5.2.1 Advanced Parameters The 'Advanced Parameters' page allows you to configure general control protocol parameters. ¾ To configure the advanced general protocol parameters, take these 4 steps: 1. Open the 'Advanced Parameters' page (Configuration tab > Protocol Configuration menu > SIP Advanced Parameters submenu > Advanced Parameters page item).
SIP User's Manual 3. Web-Based Management 2. Configure the parameters according to the table below. 3. Click the Submit button to save your changes. 4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265.
Mediant 1000 & Mediant 600 Parameter Description Enable Digit Delivery to Tel Enables the Digit Delivery feature, which sends DTMF digits (of the called number) to the device's port (phone line) after the call is answered [EnableDigitDelivery] [line offhooked (FXS) or seized (FXO)] for IP-to-Tel calls. [0] Disable = Disabled (default). [1] Enable = Enable Digit Delivery feature for the FXO/FXS device.
SIP User's Manual 3. Web-Based Management Parameter Description PSTN Alert Timeout [PSTNAlertTimeout] For Digital: Alert Timeout (in seconds) (ISDN T301 timer) for calls to PSTN. This timer is used between the time a SETUP message is sent to the Tel side (IP-to-Tel call establishment) and a CONNECT message is received. If an ALERTING message is received, the timer is restarted. For Mediant 1000 Analog: Alert Timeout (in seconds) for calls to the Tel side.
Mediant 1000 & Mediant 600 Parameter Description Enable Polarity Reversal Enables the polarity reversal feature. [EnableReversalPolarity] [0] Disable = Disable the polarity reversal service (default). [1] Enable = Enable the polarity reversal service. If the polarity reversal service is enabled, the FXS interface changes the line polarity on call answer and then changes it back on call release.
SIP User's Manual 3. Web-Based Management Parameter Description Disconnect Call on Silence Determines whether calls are disconnected after detection of silence. Detection [1] Yes = The device disconnects calls in which silence occurs (in [EnableSilenceDisconnec both call directions) for more than a user-defined time. t] [0] No = Call is not disconnected when silence is detected (default). The silence duration can be set by the FarEndDisconnectSilencePeriod parameter (default 120).
Mediant 1000 & Mediant 600 Parameter CDR Report Level [CDRReportLevel] Description Determines whether Call Detail Records (CDR) are sent to the Syslog server and when they are sent. [0] None = CDRs are not used (default). [1] End Call = CDR sent to the Syslog server at the end of each call. [2] Start & End Call = CDR report is sent to Syslog at the start and end of each call. [3] Connect & End Call = CDR report is sent to Syslog at connection and at the end of each call.
SIP User's Manual 3. Web-Based Management Parameter Description Enable X-Channel Header [XChannelHeader] Determines whether the x-channel header is added to SIP messages for trunk / B-channel information. [0] Disable = x-channel header is not used (default). [1] Enable = x-channel header is generated with trunk/B-channel and IP address information. The header provides information on the E1/T1 physical trunk/B-channel on which the call is received or placed.
Mediant 1000 & Mediant 600 Parameter Default Release Cause [DefaultReleaseCause] Description Default Release Cause (to IP) for IP-to-Tel calls when the device initiates a call release and an explicit matching cause for this release isn't found. The default release cause is NO_ROUTE_TO_DESTINATION (3). Other common values include NO_CIRCUIT_AVAILABLE (34), DESTINATION_OUT_OF_ORDER (27), etc. Notes: The default release cause is described in the Q.
SIP User's Manual 3. Web-Based Management Parameter Description The waiting call is automatically answered by the device when the current call is terminated (configured by setting the parameter EnableCallWaiting to 1). Note: This option is applicable only to Mediant 1000 FXS interfaces. Enable User-Information Usage [EnableUserInfoUsage] Out-Of-Service Behavior [FXSOOSBehavior] Enables or disables usage of the User Information loaded to the device in the User Information auxiliary file.
Mediant 1000 & Mediant 600 3.4.5.2.2 Supplementary Services The 'Supplementary Services' page is used to configure parameters that are associated with supplementary services. For detailed information on supplementary services, refer to ''Working with Supplementary Services'' on page 437. ¾ To configure the supplementary services' parameters, take these 4 steps: 1.
SIP User's Manual 3. Web-Based Management Table 3-37: Supplementary Services Parameters Parameter Enable Hold [EnableHold] Description Enables interworking of the Hold/Retrieve supplementary service from PRI to SIP. [0] Disable = Disables. [1] Enable = Enables (default). For Mediant 1000 analog: If the Hold service is enabled, a user can place the call on hold (or remove from hold) using the hook-flash. On receiving a Hold request, the remote party is placed on hold and hears the hold tone.
Mediant 1000 & Mediant 600 Parameter Enable Call Forward [EnableForward] Description Determines whether Call Forward is enabled. [0] Disable = Disable the Call Forward service. [1] Enable = Enable Call Forward service (using REFER) (default). For Mediant 1000 FXS interfaces, the 'Call Forward' table (refer to "Call Forward" on page 222) must be defined to use the Call Forward service. Note: To use this service, the devices at both ends must support this option.
SIP User's Manual 3. Web-Based Management Parameter Enable Caller ID [EnableCallerID] Description Determines whether Caller ID is enabled. [0] Disable = Disable the Caller ID service (default). [1] Enable = Enable the Caller ID service. If the Caller ID service is enabled, then for FXS interfaces, calling number and Display text (from IP) are sent to the device's port. For FXO interfaces, the Caller ID signal is detected and sent to IP in the SIP INVITE message (as 'Display' element).
Mediant 1000 & Mediant 600 Parameter Description Message Waiting Indication (MWI) Parameters Note: MWI is applicable only to Mediant 1000. Enable MWI [EnableMWI] Enables Message Waiting Indication (MWI). [0] Disable = Disabled (default). [1] Enable = MWI service is enabled. Notes: MWI Analog Lamp [MWIAnalogLamp] This parameter is applicable only to FXS interfaces. The device supports only the receipt of SIP MWI NOTIFY messages (the device doesn't generate these messages).
SIP User's Manual 3. Web-Based Management Parameter Stutter Tone Duration [StutterToneDuration] Description Duration (in msec) of the played stutter dial tone, indicating enabled Call Forward or waiting message(s). The Stutter tone is played (instead of a regular dial tone), when Call Forward is enabled on the specific port or when Message Waiting Indication (MWI) is received.
Mediant 1000 & Mediant 600 3.4.5.2.3 Metering Tones The FXS interfaces can generate 12/16 KHz metering pulses towards the Tel side (e.g., for connection to a payphone or private meter). Tariff pulse rate is determined according to an internal table. This capability enables users to define different tariffs according to the source / destination numbers and the time-of-day. The tariff rate includes the time interval between the generated pulses and the number of pulses generated on answer.
SIP User's Manual 3. Web-Based Management Parameter Description Metering Tone Type [MeteringType] Defines the metering tone (12 or 16 kHz) that is generated by FXS interfaces. [0] 12 kHz = 12-kHz metering tone (default). [1] 16 kHz = 16-kHz metering tone. Note: A suitable (12 or 16 KHz) FXS Coefficient file must be used for FXS interfaces. Charge Codes Table If you configured the 'Generate Metering Tones' parameter to 'Internal .
Mediant 1000 & Mediant 600 2. Use the table to define up to 25 different charge codes (each charge code is defined per row). Each code can include from a single and up to four different time periods in a day (24 hours). Each time period is composed of: • The end of the time period (in a 24 rounded-hour's format). • The time interval between pulses (in seconds). • The number of pulses sent on answer. The first time period always starts at midnight (00).
SIP User's Manual 3. Web-Based Management ¾ To configure the keypad features, take these 4 steps: 1. Open the 'Keypad Features' page (Configuration tab > Protocol Configuration menu > SIP Advanced Parameters submenu > Keypad Features page item). Figure 3-73: Keypad Features Page 2. Configure the Keypad Features according to the table below. 3. Click the Submit button to save your changes. 4. To save the changes to the flash memory, refer to ''Saving Configuration'' on page 265.
Mediant 1000 & Mediant 600 Parameter On Busy [KeyCFBusy] Description Keypad sequence that activates the forward on busy option. On Busy or No Answer [KeyCFBusyOrNoAnsw Keypad sequence that activates the forward on 'busy or no answer' option. er] Do Not Disturb [KeyCFDoNotDisturb] Keypad sequence that activates the Do Not Disturb option (immediately reject incoming calls). To activate the required forward method from the telephone: 1.
SIP User's Manual 3. Web-Based Management Parameter Description Transfer Blind [KeyBlindTransfer] Keypad sequence that activates blind transfer for Tel-to-IP calls. There are two possible scenarios: Option 1: After this sequence is dialed, the current call is put on hold (using Re-INVITE), a dial tone is played to the phone, and then phone number collection starts.
Mediant 1000 & Mediant 600 3.4.5.2.6 Stand-Alone Survivability The 'SAS Configuration' page allows you to configure the device's Stand-Alone Survivability (SAS) feature. This feature is useful for providing a local backup via the PSTN in Small or Medium Enterprises (SME) that are serviced by IP Centrex services. In such environments, the enterprise's incoming and outgoing telephone calls (external and internal) are controlled by the Proxy, which communicates with the enterprise through the WAN interface.
SIP User's Manual 3. Web-Based Management ¾ To configure the Stand-Alone Survivability parameters, take these 4 steps: 1. Open the 'SAS Configuration' page (Configuration tab > Protocol Configuration menu > SIP Advanced Parameters submenu > Stand-Alone Survivability page item). Figure 3-74: SAS Configuration Page 2. Configure the parameters according to the table below. 3. Click the Submit button to apply your changes. 4.
Mediant 1000 & Mediant 600 Parameter Description Short Number Length Determines the length of the suffix used for SAS Short Numbering support. [SASShortNumberLeng The dialed number is compared to the registered number. The registered (full) and dialed (full or short) numbers match only if one of the following th] conditions is met: The numbers match entirely (i.e., they are of the same length and all characters match).
SIP User's Manual 3.
Mediant 1000 & Mediant 600 • When the source number is 1234510012001, it is changed to 20018. • When the source number is 3122, it is changed to 2312. 2. From the 'Table Index' drop-down list, select the range of entries that you want to edit (up to 20 entries can be configured for Source Number Manipulation and 50 entries for Destination Number Manipulation). 3. Configure the Number Manipulation table according to the table below. 4. Click the Submit button to save your changes. 5.
SIP User's Manual 3. Web-Based Management Parameter Number of Stripped Digits Description Number of digits removed from the left of the telephone number prefix: Enter the number of digits that you want removed. For example, if you enter 3 and the phone number is 5551234, the new phone number is 1234. Number of digits removed from the right of the telephone number prefix: Enter the number of digits in parenthesis (). Note: A combination of the two options is allowed, e.g., 2(3).
Mediant 1000 & Mediant 600 Parameter Presentation Description Determines whether Caller ID is permitted: Allowed = sends Caller ID information when a call is made using these destination / source prefixes. Restricted = restricts Caller ID information for these prefixes. Not Configured = privacy is determined according to the Caller ID table (refer to ''Caller ID'' on page 221). Notes: Only applicable to Number Manipulation tables for source number manipulation.
SIP User's Manual 3. Web-Based Management 3.4.5.3.2 Numbering Plans and Type of Number Numbers are classified by their Numbering Plan Indication (NPI) and their Type of Number (TON). The device supports all NPI/TON classifications used in the standard. The list of ISDN ETSI NPI/TON values is shown in the following table: Table 3-43: NPI/TON Values for ISDN ETSI NPI TON Description Unknown [0] Unknown [0] A valid classification, but one that has no information about the numbering plan. E.
Mediant 1000 & Mediant 600 ¾ To configure the Phone-Context tables, take these 4 steps: 1. Open the 'Phone Context Table' page (Configuration tab > Protocol Configuration menu > Manipulation Tables submenu > Phone Context Table page item). Figure 3-76: Phone Context Table Page 2. Configure the Phone Context table according to the table below. 3. Click the Submit button to save your changes. 4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265.
SIP User's Manual 3. Web-Based Management Parameter Select the Number Type assigned to this entry. TON Phone Context 3.4.5.4 Description If you selected Unknown as the NPI, you can select Unknown [0]. If you selected Private as the NPI, you can select Unknown [0], Level 2 Regional [1], Level 1 Regional [2], PSTN Specific [3], or Level 0 Regional (Local) [4]. If you selected E.
Mediant 1000 & Mediant 600 3.4.5.4.1 Routing General Parameters The 'Routing General Parameters' page allows you to configure the device's IP-to-Tel and Tel-to-IP routing parameters. ¾ To configure the general routing parameters, take these 4 steps: 1. Open the 'Routing General Parameters' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > Routing General Parameters page item). 2. Configure the general parameters according to the table below. 3.
SIP User's Manual 3. Web-Based Management Parameter Description Replace Empty Destination with Bchannel Phone Number [ReplaceEmptyDstWith PortNumber] Determines whether the internal channel number is used as the destination number if the called number is missing. [0] No (default) [1] Yes Note: Applicable only for Tel-to-IP calls and if the called number is missing.
Mediant 1000 & Mediant 600 Parameter Description Alt Routing Tel to IP Determines the event(s) reason for triggering Alternative Routing. Mode [0] None = Alternative routing is not used. [AltRoutingTel2IPMode] [1] Connectivity = Alternative routing is performed if ping to initial destination fails. [2] QoS = Alternative routing is performed if poor QoS is detected.
SIP User's Manual 3. Web-Based Management Note that for this table to take precedence over a Proxy for routing calls, set the parameter PreferRouteTable to 1. The device checks the 'Destination IP Address' field in this table for a match with the outgoing call. A Proxy is used only if a match is not found. Possible uses for Tel-to-IP routing include the following: Fallback to internal routing table if there is no communication with the Proxy servers.
Mediant 1000 & Mediant 600 ¾ To configure the Tel to IP Routing table, take these 6 steps: 1. Open the 'Tel to IP Routing' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > Tel to IP Routing page item). Figure 3-77: Tel to IP Routing Page 2. From the 'Routing Index' drop-down list, select the range of entries that you want to add. 3.
SIP User's Manual 3. Web-Based Management Parameter Src. Trunk Group ID Description The source Trunk Group for Tel-to-IP calls. The range is 1-99. Notes: If this parameter is not required in the routing rule, leave the field empty. To denote any Trunk Group, you can enter the asterisk (*) symbol. Dest. Phone Prefix Represents a called telephone number prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers.
Mediant 1000 & Mediant 600 Parameter Description Status A read-only field representing the Quality of Service of the destination IP address: Charge Code n/a = Alternative Routing feature is disabled. OK = IP route is available. Ping Error = No ping to IP destination; route is not available. QoS Low = Bad QoS of IP destination; route is not available. DNS Error = No DNS resolution (only when domain name is used instead of an IP address).
SIP User's Manual 3. Web-Based Management ¾ To configure the IP to Trunk Group Routing table, take these 6 steps: 1. Open the 'IP to Trunk Group Routing' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > IP to Trunk Group Routing page item). Figure 3-78: IP to Trunk Group Routing Table Page 2. From the 'Routing Index' drop-down list, select the range of entries that you want to add. 3.
Mediant 1000 & Mediant 600 Parameter Source Host Prefix Description The From URI host name prefix of the incoming INVITE message. If configured, the device uses it for IP-to-Tel routing. If not used, it must be left empty. Notes: Dest. Phone Prefix The asterisk (*) symbol cannot be used to depict any source host prefix.
SIP User's Manual 3. Web-Based Management 3.4.5.4.4 Internal DNS Table The 'Internal DNS Table' page, similar to a DNS resolution is used to translate up to 10 host (domain) names into IP addresses (e.g., when using the 'Tel to IP Routing' table). Two different IP addresses can be assigned to the same host name, typically used for alternative routing (using the 'Tel to IP Routing' table). Notes: • The device initially attempts to resolve a domain name using this Internal DNS table.
Mediant 1000 & Mediant 600 3.4.5.4.5 Internal SRV Table The 'Internal SRV Table' page provides a table for resolving host names to DNS ARecords. Three different A-Records can be assigned to each host name. Each A-Record contains the host name, priority, weight, and port. Notes: • If the Internal SRV table is configured, the device initially attempts to resolve a domain name using this table.
SIP User's Manual 3. Web-Based Management 3.4.5.4.6 Reasons for Alternative Routing The 'Reasons for Alternative Routing' page includes two groups - IP to Tel Reasons and Tel to IP Reasons. Each group allows you to define up to four different release reasons. If a call is released as a result of one of these reasons, the device tries to find an alternative route for that call. The release reason for IP-to-Tel calls is provided in Q.931 notation.
Mediant 1000 & Mediant 600 ¾ To configure the reasons for alternative routing, take these 5 steps: 1. Open the 'Reasons for Alternative Routing' page (Configuration tab > Protocol Configuration menu > Routing Tables submenu > Reasons for Alternative Routing page item). Figure 3-81: Reasons for Alternative Routing Page 2. In the 'IP to Tel Reasons' group, select up to four different call failure reasons that invoke an alternative IP-to-Tel routing. 3.
SIP User's Manual 3. Web-Based Management 3.4.5.4.7 Release Cause Mapping The 'Release Cause Mapping' page consists of two groups that allow the device to map up to 12 different SIP Responses to Q.850 Release Causes and vice versa, thereby overriding the hard-coded mapping mechanism (described in ''Release Reason Mapping'' on page 459). Note: You can also configure SIP Responses-Q.
Mediant 1000 & Mediant 600 3.4.5.
SIP User's Manual 3. Web-Based Management Note: You can also configure the coder groups using the ini file table parameter CoderName (refer to ''SIP Configuration Parameters'' on page 323). ¾ To configure coder groups, take these 11 steps: 1. Open the 'Coder Group Settings' page (Configuration tab > Protocol Configuration menu > Profile Definitions submenu > Coder Group Settings page item). Figure 3-83: Coder Group Settings Page 2. From the 'Coder Group ID' drop-down list, select a coder group ID. 3.
Mediant 1000 & Mediant 600 Notes: • Each coder can appear only once per Coder Group. • The device always uses the packetization time requested by the remote side for sending RTP packets. If not specified, the packetization time (ptime) is assigned the default value. • Only the packetization time of the first coder in the defined coder list is declared in INVITE / 200 OK SDP, even if multiple coders are defined. • For G.729 it is also possible to select silence suppression without adaptations.
SIP User's Manual 3. Web-Based Management ¾ To configure Tel Profiles, take these 9 steps: 1. Open the 'Tel Profile Settings' page (Configuration tab > Protocol Configuration menu > Profile Definitions submenu > Tel Profile Settings page item). Figure 3-84: Tel Profile Settings Page 2. From the 'Profile ID' drop-down list, select the Tel Profile identification number you want to configure. 3. In the 'Profile Name' field, enter an arbitrary name that enables you to easily identify the Tel Profile. 4.
Mediant 1000 & Mediant 600 5. Configure the Profile's parameters according to your requirements. For detailed information on each parameter, refer to its description on the page in which it is configured as an individual parameter. 6. From the 'Coder Group' drop-down list, select the Coder Group (refer to ''Coder Group Settings'' on page 212) or the device's default coder (refer to ''Coders'' on page 157) to which you want to assign the Profile. 7.
SIP User's Manual 3. Web-Based Management ¾ To configure the IP Profile settings, take these 9 steps: 1. Open the 'IP Profile Settings' page (Configuration tab > Protocol Configuration menu > Profile Definitions submenu > IP Profile Settings page item). Figure 3-85: IP Profile Settings Page 2. From the 'Profile ID' drop-down list, select an identification number for the IP Profile. 3. In the 'Profile Name' field, enter an arbitrary name that allows you to easily identify the IP Profile. 4.
Mediant 1000 & Mediant 600 5. Configure the IP Profile's parameters according to your requirements. For detailed information on each parameter, refer to the description on the page in which it is configured as an individual parameter. Parameters that are unique to IP Profile are described in the table below. 6. From the 'Coder Group' drop-down list, select the coder group you want to assign to the Profile.
SIP User's Manual 3. Web-Based Management 3.4.5.6.1 Authentication The 'Authentication' page defines a user name and password for authenticating each device port. Authentication is typically used for FXS interfaces, but can also be used for FXO interfaces. Notes: • The 'Authentication' page is applicable only to Mediant 1000. • The 'Authentication Mode' parameter (refer to ''Proxy & Registration Parameters'' on page 146) determines whether authentication is performed per port or for the entire device.
Mediant 1000 & Mediant 600 3.4.5.6.2 Automatic Dialing The 'Automatic Dialing' page allows you to define a telephone number that is automatically dialed when an FXS or FXO port is used (e.g., off-hooked). ¾ To configure Automatic Dialing, take these 5 steps: 1. Open the 'Automatic Dialing' page (Configuration tab > Protocol Configuration menu > Endpoint Settings submenu > Automatic Dialing page item). Figure 3-87: Automatic Dialing Page 2.
SIP User's Manual 3. Web-Based Management 3.4.5.6.3 Caller Display Information The 'Caller Display Information' page allows you to enable the device to send Caller ID information to IP when a call is made. The called party can use this information for caller identification. The information configured in this page is sent in an INVITE message in the 'From' header.
Mediant 1000 & Mediant 600 4. Click the Submit button to save your changes. 5. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265. Notes: • The 'Caller Display Information' page is relevant only for FXS and FXO interfaces and applicable only to Mediant 1000. • If Caller ID name is detected on an FXO line (EnableCallerID = 1), it is used instead of the Caller ID name defined on this page.
SIP User's Manual 3. Web-Based Management ¾ To configure Call Forward per port, take these 4 steps: 1. Open the 'Call Forward Table' page (Configuration tab > Protocol Configuration menu > Endpoint Settings submenu > Call Forward page item). Figure 3-89: Call Forward Table Page 2. Configure the Call Forward parameters for each port according to the table below. 3. Click the Submit button to save your changes. 4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 265.
Mediant 1000 & Mediant 600 3.4.5.6.5 Caller ID Permissions The 'Caller ID Permissions' page allows you to enable or disable (per port), the Caller ID generation (for FXS interfaces) and detection (for FXO interfaces). If a port isn't configured, its Caller ID generation / detection are determined according to the global parameter EnableCallerID described in ''Supplementary Services'' on page 176.
SIP User's Manual 3. Web-Based Management 3.4.5.6.6 Call Waiting The 'Call Waiting' page allows you to enable or disable call waiting per device FXS port. Notes: • This page is applicable only to FXS interfaces and applicable only to Mediant 1000. • Instead of using this page, you can enable or disable call waiting for all the device's ports, using the global call waiting parameter 'Enable Call Waiting' (refer to ''Supplementary Services'' on page 176).
Mediant 1000 & Mediant 600 3.4.5.7 Configuring the Trunk and IP Groups The Trunk/IP Group menu allows you to configure groups of channels. This submenu includes the following page items: Trunk Group (refer to "Configuring the Trunk Group Table" on page 226) Trunk Group Settings (refer to ''Configuring the Trunk Group Settings'' on page 228) IP Group Table (refer to ''Configuring the IP Groups'' on page 231) Account Table (refer to ''Configuring the Account Table'' on page 232) 3.4.5.7.
SIP User's Manual 3. Web-Based Management Table 3-50: Trunk Group Table Description Parameter Module Description The module type (FXS, FXO, BRI, or PRI) for which you want to define the Trunk Group. Note: FXS and FXO modules are applicable only to Mediant 1000. From Trunk Starting physical Trunk number. The number of listed Trunks depends on the device's hardware configuration. Note: Applicable only to PRI and BRI modules. To Trunk Ending physical Trunk number.
Mediant 1000 & Mediant 600 3.4.5.7.2 Configuring the Trunk Group Settings The 'Trunk Group Settings' page is mainly used to select the method for which IP-to-Tel calls are assigned to channels within each Trunk Group. If no method is selected (for a specific Trunk Group), the setting of the global parameter ChannelSelectMode in the 'SIP General Parameters' page (refer to ''SIP General Parameters'' on page 134) applies.
SIP User's Manual 3. Web-Based Management Mode Channel Select Mode Registration Mode Description The method in which IP-to-Tel calls are assigned to channels pertaining to a Trunk Group: By Dest Phone Number = Selects the device's channel according to the called number defined in the 'Trunk Group Table' (refer to "Configuring the Trunk Group Table" on page 226). Cyclic Ascending (default) = Selects the next available channel in an ascending cyclic order.
Mediant 1000 & Mediant 600 Mode Description To enable Trunk Group registrations, configure the global parameter IsRegisterNeeded to 1. This is unnecessary for 'Per Account' registration mode. If no mode is selected, the registration is performed according to the global registration parameter ChannelSelectMode (refer to ''Proxy & Registration Parameters'' on page 146).
SIP User's Manual 3. Web-Based Management 3.4.5.7.3 Configuring the IP Groups The 'IP Group Table' page allows you to create logical IP entities (IP Groups) that are later used in the call routing tables. The IP Groups are typically implemented in Tel-to-IP call routing.
Mediant 1000 & Mediant 600 Table 3-52: IP Group Parameters Description Parameter Description IP Group ID The identifying number of the IP Group. The range is 1-9. Description Brief string description of the IP Group. The value range is a string of up to 29 characters. The default is an empty field. Proxy Set ID Selects the Proxy Set ID to be associated with the IP Group.
SIP User's Manual 3. Web-Based Management ¾ To configure Accounts, take these 5 steps: 1. Open the 'Account Table' page (Configuration tab > Protocol Configuration menu > Trunk/IP Group submenu > Account Table page item). Figure 3-95: Account Table Page 2. To add an Account, in the 'Add' field, enter the desired table row index, and then click Add. A new row appears. 3. Configure the Account parameters according to the table below. 4. Click the Apply button to save your changes. 5.
Mediant 1000 & Mediant 600 Parameter Description the username and password defined in the 'Authentication' table for FXS interfaces (refer to Authentication on page 219) or the global parameters (UserName and Password) defined on the 'Proxy & Registration' page (refer to ''Proxy & Registration Parameters'' on page 146) are used. Username Digest MD5 Authentication user name (up to 50 characters). Password Digest MD5 Authentication password (up to 50 characters).
SIP User's Manual 3.4.5.8 3. Web-Based Management Configuring the Digital Gateway Parameters The 'Digital Gateway Parameters' page allows you to configure miscellaneous digital parameters. ¾ To configure the digital gateway parameters, take these 4 steps: 1. Open the 'Digital Gateway Parameters' page (Configuration tab > Protocol Configuration menu > Digital Gateway submenu > Digital Gateway Parameters page item). Figure 3-96: Digital Gateway Parameters Page 2.
Mediant 1000 & Mediant 600 Table 3-54: Digital Gateway Parameters Description Parameter B-channel Negotiation [BchannelNegotiation] Description Determines the ISDN B-Channel negotiation mode. [0] Preferred [1] Exclusive (default) [2] Any Notes: Applicable only to ISDN protocols. For some ISDN variants, when 'Any' (2) is selected, the SETUP message does not include the Channel Identification IE.
SIP User's Manual 3. Web-Based Management Parameter Send Screening Indicator to IP [ScreeningInd2IP] Description Overrides the calling party's number (CPN) screening indication in the received ISDN SETUP message for Tel-to-IP calls. [-1] Not Configured = not configured (interworking from ISDN to IP) or set to 0 for CAS (default). [0] User Provided = CPN set by user, but not screened (verified). [1] User Passed = CPN set by user, verified and passed.
Mediant 1000 & Mediant 600 Parameter Enable User-to-User IE for IP to Tel [EnableUUIIP2Tel] Description Enables SIP-to-PRI ISDN interworking. [0] Disable = Disabled (default). [1] Enable = Enable transfer of UUIE from SIP INVITE message to PRI SETUP message. The device supports the following SIP-to-PRI ISDN interworking: SIP INVITE to SETUP, SIP 200 OK to CONNECT, SIP INFO to USER INFORMATION, SIP 18x to ALERT, and SIP BYE to DISCONNECT.
SIP User's Manual 3. Web-Based Management Parameter Description Enable ISDN Tunneling IP to Tel [0] Disable = Disable (default). [EnableISDNTunnelingIP2Tel] [1] Using Header = Enable ISDN Tunneling from SIP to ISDN PRI using a proprietary SIP header. [2] Using Body = Enable ISDN Tunneling from SIP to ISDN PRI using a dedicated message body.
Mediant 1000 & Mediant 600 Parameter Enable Calling Party Category [EnableCallingPartyCategory] Description Determines whether Calling Party Category (CPC) is mapped between SIP and PRI. [0] Disable = Don't relay the CPC between SIP and PRI (default). [1] Enable = The CPC is relayed between SIP and PRI.
SIP User's Manual 3. Web-Based Management Parameter Default Call Priority [SIPDefaultCallPriority] Description Defines the default call priority for MLPP calls.
Mediant 1000 & Mediant 600 3.4.5.9 Configuring the IPmedia Parameters The 'IPmedia Parameters' page allows you to configure the IP media parameters. Note: The 'IPmedia Parameters' page is applicable only to Mediant 1000. The 'IPmedia Parameters' page is Feature Key dependant and therefore is available only if included in the device's Feature Key (refer to 'Updating the Software Upgrade Key' on page 268). ¾ To configure the IP media parameters, take these 4 steps: 1.
SIP User's Manual 3. Web-Based Management ini File Field Name Web Parameter Name Valid Range and Description NetAnn Announcement ID NetAnn identification string (up to 16 characters) for playing an announcement using the NetAnn interface. The application server sends [NetAnnAnncID] a regular SIP INVITE message with a SIP URI that includes this identifier string and a “play=” parameter that identifies the necessary announcement. The default value is ‘annc’. Example 1: INVITE sip: annc@10.2.3.
Mediant 1000 & Mediant 600 3.4.6 Advanced Applications The Advanced Applications menu allows you to configure advanced SIP-based applications. This menu includes the following page items: 3.4.6.
SIP User's Manual 3. Web-Based Management Table 3-56: Voice Mail Parameters Parameter Description General Voice Mail Interface [VoiceMailInterface] Line Transfer Mode [LineTransferMode] Enables the voice mail application on the device and determines the communication method used between the PBX and the device. [0] None (default) [1] DTMF [2] SMDI (N/A)[3] QSIG [4] SETUP Only (ISDN) [5] MATRA/AASTRA QSIG Determines the call transfer method used by the device.
Mediant 1000 & Mediant 600 Parameter Description Forward on No Answer Determines the digit pattern used by the PBX to indicate 'call forward on Digit Pattern (Internal) no answer' when the original call is received from an internal extension. [DigitPatternForwardOnN The valid range is a 120-character string.
SIP User's Manual 3. Web-Based Management Parameter MWI Suffix Pattern [MWISuffixCode] Description Determines the digit code used by the device as a suffix for 'MWI On Digit Pattern' and 'MWI Off Digit Pattern'. This suffix is added to the generated DTMF string after the extension number. The valid range is a 25-character string. SMDI (currently not supported) Enable SMDI [SMDI] N/A SMDI Timeout [SMDITimeOut] N/A 3.4.6.
Mediant 1000 & Mediant 600 Parameter Description RADIUS Accounting Type Determines when the RADIUS accounting messages are sent to the [RADIUSAccountingType] RADIUS accounting server. AAA Indications [AAAIndications] 3.4.6.3 [0] At Call Release = Sent at call release only (default). [1] At Connect & Release = Sent at call connect and release. [2] At Setup & Release = Sent at call setup and release. Determines the Authentication, Authorization and Accounting (AAA) indications.
SIP User's Manual 3. Web-Based Management Table 3-58: FXO Parameters Description Parameter Dialing Mode [IsTwoStageDial] Description Determines the dialing mode for IP-to-Tel (FXO) calls. [0] One Stage = One-stage dialing. [1] Two Stages = Two-stage dialing (default).
Mediant 1000 & Mediant 600 Parameter Description Ring Detection Timeout Defines the timeout (in seconds) for detecting the second ring after the first [sec] detected ring. [FXOBetweenRingTime] If automatic dialing is not used and Caller ID is enabled, the device seizes the line after detection of the second ring signal (allowing detection of caller ID sent between the first and the second rings). If the second ring signal is not received within this timeout, the device doesn't initiate a call to IP.
SIP User's Manual 3. Web-Based Management Parameter Description [0] Enable = Do not disconnect call on detection of busy tone. Disconnect Call on Detection of Busy Tone [1] Disable = Call is released if busy or reorder (fast busy) tones are [DisconnectOnBusyTon detected on the device's FXO port (default). e] Disconnect on Dial Tone The device can disconnect a call after a dial tone is detected from the PBX. [DisconnectOnDialTone [0] Disable = Call isn't released.
Mediant 1000 & Mediant 600 Table 3-59: TDM Bus Settings Parameters Description Parameter PCM Law Select [PCMLawSelect] Description Determines the type of PCM companding law in input/output TDM bus. [1] Alaw = Alaw (default) [3] MuLaw = MuLaw Note: Typically, A-Law is used for E1 spans and µ-Law for T1/J1 spans. Idle PCM Pattern [IdlePCMPattern] Defines the PCM Pattern that is applied to the E1/T1 timeslot (Bchannel) when the channel is idle. The range is 0 to 255.
SIP User's Manual 3. Web-Based Management Parameter Description TDM Bus PSTN Auto Clock Reverting [TDMBusPSTNAutoClockReve rtingEnable] Enables or disables the PSTN trunk auto-fallback reverting feature.
Mediant 1000 & Mediant 600 3.5.1.1 Configuring the Management Settings The 'Management Settings' page allows you to configure the device's management parameters. ¾ To configure the Management parameters, take these 4 steps: 1. Open the 'Management Settings' page (Management tab > Management Configuration menu > Management Settings page item). Figure 3-102: Management Settings Page 2. Configure the Management Settings according to the table below. 3. Click the Submit button to save your changes. 4.
SIP User's Manual 3. Web-Based Management Table 3-60: Management Settings Parameters Parameter Description Syslog Settings Syslog Server IP Address [SyslogServerIP] IP address (in dotted-decimal notation) of the computer you are using to run the Syslog server. The Syslog server is an application designed to collect the logs and error messages generated by the device. Default IP address is 0.0.0.0. For information on Syslog, refer to the Product Reference Manual.
Mediant 1000 & Mediant 600 Parameter Description Trap Manager Host Name [SNMPTrapManagerHostNa me] Defines an FQDN of a remote host that is used as an SNMP manager. The resolved IP address replaces the last entry in the Trap Manager table (defined by the parameter SNMPManagerTableIP_x) and the last trap manager entry of snmpTargetAddrTable in the snmpTargetMIB. For example: 'mngr.corp.mycompany.com'. The valid range is a 99-character string.
SIP User's Manual 3. Web-Based Management 3.5.1.1.1 Configuring the SNMP Trap Destinations Table The 'SNMP Trap Destinations' page allows you to configure up to five SNMP trap managers. ¾ To configure the SNMP Trap Destinations table, take these 5 steps: 1. Access the 'Management Settings' page, as described in ''Configuring the Management Settings'' on page 254. 2. In the 'SNMP Trap Destinations' field, click the right-pointing arrow 'SNMP Trap Destinations' page appears.
Mediant 1000 & Mediant 600 Parameter Description Trap Enable Activates or de-activates the sending of traps to the corresponding [SNMPManagerTrapSendi SNMP Manager. ngEnable_x] [0] Disable = Sending is disabled. [1] Enable = Sending is enabled (default). 3.5.1.1.2 Configuring the SNMP Community Strings The 'SNMP Community String' page allows you to configure up to five read-only and up to five read-write SNMP community strings, and to configure the community string that is used for sending traps.
SIP User's Manual 3. Web-Based Management Table 3-62: SNMP Community Strings Parameters Description Parameter Description Community String Read Only [SNMPReadOnlyCommunityString_x]: Up to five read-only community strings (up to 19 characters each). The default string is 'public'. Read / Write [SNMPReadWriteCommunityString_x]: Up to five read / write community strings (up to 19 characters each). The default string is 'private'.
Mediant 1000 & Mediant 600 Table 3-63: SNMP V3 Users Parameters Parameter Description Index [SNMPUsers_Index] The table index. The valid range is 0 to 9. Username [SNMPUsers_Username] Name of the SNMP v3 user. This name must be unique. AuthProtocol Authentication protocol of the SNMP v3 user. [SNMPUsers_AuthProtocol] 0 = None (default) 1 = MD5 2 = SHA-1 PrivProtocol Privacy protocol of the SNMP v3 user.
SIP User's Manual 2. 3. Web-Based Management In the 'SNMP Trusted Managers' field, click the right-pointing arrow 'SNMP Trusted Managers' page appears. button; the Figure 3-106: SNMP Trusted Managers 3.5.1.2 3. Select the check box corresponding to the SNMP Trusted Manager that you want to enable and for whom you want to define an IP address. 4. Define an IP address in dotted-decimal notation. 5. Click the Submit button to apply your changes. 6.
Mediant 1000 & Mediant 600 3.5.1.
SIP User's Manual 3. Web-Based Management ¾ To reset the device, take these 6 steps: 1. Open the 'Maintenance Actions' page (refer to ''Maintenance Actions'' on page 262). 2. Under the 'Reset Configuration' group, from the 'Burn To FLASH' drop-down list, select one of the following options: 3. • 'Yes': The device's current configuration is saved (burned) to the flash memory prior to reset (default).
Mediant 1000 & Mediant 600 3.5.1.3.2 Locking and Unlocking the Device The Lock and Unlock options allow you to lock the device so that it doesn't accept any new incoming calls. This is useful when, for example, you are uploading new software files to the device and you don't want any traffic to interfere with the process. ¾ To lock the device, take these 5 steps: 1. Open the 'Maintenance Actions' page (refer to ''Maintenance Actions'' on page 262). 2.
SIP User's Manual 3. Web-Based Management 3.5.1.3.3 Saving Configuration The 'Maintenance Actions' page allows you to save (burn) the current parameter configuration (including loaded auxiliary files) to the device's non-volatile memory (i.e., flash). The parameter modifications that you make throughout the Web interface's pages are temporarily saved (to the volatile memory - RAM) when you click the Submit button on these pages.
Mediant 1000 & Mediant 600 3.5.2 Software Update The Software Update menu allows you to upgrade the device's software by loading a new cmp file (compressed firmware) along with the ini file and a suite of auxiliary files, or to update existing auxiliary files. The Software Update menu includes the following page items: 3.5.2.
SIP User's Manual 3. Web-Based Management ¾ To load an auxiliary file to the device using the Web interface, take these 6 steps: 1. Open the 'Load Auxiliary Files' page (Management tab > Software Update menu > Load Auxiliary Files page item). Figure 3-111: Load Auxiliary Files Page 2.
Mediant 1000 & Mediant 600 Notes: • Saving an auxiliary file to flash memory may disrupt traffic on the device. To avoid this, disable all traffic on the device by performing a graceful lock (refer to ''Locking and Unlocking the Device'' on page 264). • The FXO Coefficient file is applicable only to Mediant 1000. • You can schedule automatic loading of updated auxiliary files using HTTP, HTTPS, FTP, or NFS (refer to the Product Reference Manual).
SIP User's Manual 3. Web-Based Management The procedure below describes how to load a Software Upgrade Key to the device using the Web interface. ¾ To load a Software Upgrade Key, take these 6 steps: 1. Open the 'Software Upgrade Key Status' page (Management tab > Software Update menu > Software Update Key page item). 2.
Mediant 1000 & Mediant 600 • Multiple S/N lines (as shown below): Figure 3-112: Software Upgrade Key with Multiple S/N Lines 5. 6. a. in the 'Send Upgrade Key file' field, click the Browse button and navigate to the folder in which the Software Upgrade Key text file is located on your PC. b. Click the Send File button; the new key is loaded to the device and validated. If the key is valid, it is burned to memory and displayed in the 'Current Key' field.
SIP User's Manual 3. Web-Based Management 3.5.2.2.1 Loading via BootP/TFTP The procedure below describes how to load a Software Upgrade Key to the device using AudioCodes' BootP/TFTP Server utility (for a detailed description on the BootP utility, refer to the Product Reference Manual). ¾ To load a Software Upgrade Key file using BootP/TFTP, take these 6 steps: 1. Place the Software Upgrade Key file (typically, a *.txt file) in the same folder in which the device's cmp file is located. 2.
Mediant 1000 & Mediant 600 3.5.2.3 Software Upgrade Wizard The Software Upgrade Wizard guides you through the process of software upgrade: selecting files and loading them to the device. The wizard also enables you to upgrade software while maintaining the existing configuration. Using the wizard obligates you to load and burn a cmp file to the device. You can choose to also use the wizard to load the ini and auxiliary files (e.g.
SIP User's Manual 3. Web-Based Management ¾ To use the Software Upgrade Wizard, take these 11 steps: 1. Stop all traffic on the device (refer to the note above). 2. Open the 'Software Upgrade Wizard' (Management tab > Software Update menu > Software Upgrade Wizard); the 'Software Upgrade Wizard' page appears. Figure 3-113: Start Software Upgrade Wizard Screen 3. Click the Start Software Upgrade button; the 'Load a CMP file' Wizard page appears.
Mediant 1000 & Mediant 600 4. Click the Browse button, navigate to the cmp file, and then click Send File; the cmp file is loaded to the device and you're notified as to a successful loading, as shown below. Figure 3-115: Loaded CMP File 5. Click one of the following buttons: • • Reset; the device resets with the newly loaded cmp, and utilizing the current configuration and auxiliary files. Next; the 'Load an ini File' wizard page opens.
SIP User's Manual 3. Web-Based Management Figure 3-116: Load an ini File Page 7. 8. Version 5.4 You can now choose to either: • Click Reset; the device resets, utilizing the new cmp and ini file you loaded up to now as well as utilizing the other auxiliary files. • Click Back; the 'Load a cmp file' page is opened again. • Click Next; the next page opens for loading the next consecutive auxiliary file listed in the Wizard.
Mediant 1000 & Mediant 600 9. In the 'FINISH' page, complete the upgrade process by clicking Reset; the device 'burns' the newly loaded files to flash memory and then resets t.he device. After the device resets, the 'End Process' screen appears displaying the burned configuration files (refer to the figure below). Figure 3-117: End Process Wizard Page 10.
SIP User's Manual 3. Web-Based Management ¾ To save and restore the ini file, take these 3 steps: 1. Open the 'Configuration File' page (Management tab > Software Update menu > Configuration File). Figure 3-119: Configuration File Page 2. 3. Version 5.4 To save the ini file to a PC, perform the following: a. Click the Save INI File button; the 'File Download' dialog box opens. b.
Mediant 1000 & Mediant 600 3.6 Status & Diagnostics Tab The Status & Diagnostics tab on the Navigation bar displays all menus related to the operating status of the device and device diagnostics. These menus appear in the Navigation tree and include the following: 3.6.
SIP User's Manual 2. 3. Web-Based Management Open the 'Message Log' page (Status & Diagnostics tab > Status & Diagnostics menu > Message Log page item); the 'Message Log' page is displayed and the log is activated. Figure 3-120: Message Log Screen The displayed logged messages are color coded as follows: 3. • Yellow - fatal error message • Blue - recoverable error message (i.e.
Mediant 1000 & Mediant 600 3.6.1.2 Viewing the Ethernet Port Information The 'Ethernet Port Information' page displays read-only information on the Ethernet connection used by the device. This includes indicating the active port, duplex mode, and speed. You can also access this page from the 'Home' page (refer to ''Using the Home Page'' on page 52). For detailed information on the Ethernet redundancy scheme, refer to ''Ethernet Interface Redundancy'' on page 445.
SIP User's Manual 3. Web-Based Management ¾ To access the 'Device Information' page, take this step: Open the 'Device Information' page (Status & Diagnostics tab > Status & Diagnostics menu > Device Information page item). Figure 3-122: Device Information Page ¾ To delete any of the loaded files, take this step: Click the Delete button corresponding to the files that you want to delete. Deleting a file takes effect only after the device is reset (refer to ''Resetting the Device'' on page 262).
Mediant 1000 & Mediant 600 3.6.1.4 Viewing Performance Statistics The 'Performance Statistics' page provides read-only, device performance statistics. This page is refreshed with new statistics every 60 seconds. The duration that the current statistics has been collected, is displayed above the statistics table. ¾ To view performance statistics, take the following step: Open the 'Performance Statistics’ page (Status & Diagnostics tab > Status & Diagnostics menu > Performance Statistics page item).
SIP User's Manual 3. Web-Based Management ¾ To view the list of alarms, take this step: Open the 'Active Alarms’ page (Status & Diagnostics tab > Status & Diagnostics menu > Active Alarms page item). Figure 3-124: Active Alarms Page 3.6.2 Gateway Statistics The 'Gateway Statistics' page allows you to monitor real-time activity such as IP connectivity information, call details and call statistics, including the number of call attempts, failed calls, fax calls, etc.
Mediant 1000 & Mediant 600 ¾ To view the IP-to-Tel and Tel-to-IP Call Counters pages, take this step: Open the Call Counters page that you want to view (Status & Diagnostics tab > Gateway Statistics menu > IP to Tel Calls Count or Tel to IP Calls Count page item); the figure below shows the 'IP to Tel Calls Count' page. Figure 3-125: Calls Count Page Table 3-66: Call Counters Description Counter Description Number of Attempted Calls Indicates the number of attempted calls.
SIP User's Manual 3. Web-Based Management Counter Number of Calls Terminated due to No Answer Description Indicates the number of calls that weren't answered. It's incremented as a result of one of the following release reasons: GWAPP_NO_USER_RESPONDING (18) GWAPP_NO_ANSWER_FROM_USER_ALERTED (19) GWAPP_NORMAL_CALL_CLEAR (16) (when the call duration is zero) Number of Calls Terminated due to Forward Indicates the number of calls that were terminated due to a call forward.
Mediant 1000 & Mediant 600 3.6.2.2 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. ¾ To view the call routing status, take this step: Open the 'Call Routing Status' page (Status & Diagnostics tab > Gateway Statistics menu > Calls Routing Status page item).
SIP User's Manual 3.6.2.3 3. Web-Based Management Registration Status The 'Registration Status' page displays whether the device or endpoints are registered to a SIP Registrar/Proxy server. Note: The 'Registration Status' page is applicable only to Mediant 1000. ¾ To view endpoint Registration status, take this step: Open the 'Registration Status' page (Status & Diagnostics tab > Gateway Statistics menu > Registration Status page item).
Mediant 1000 & Mediant 600 3.6.2.4 SAS/SBC Registered Users The 'SAS Registered Users' page displays a list of up to 100 Stand Alone Survivability (SAS) registered users. The SAS feature is configured in the 'SAS Configuration' page (refer to ''Stand-Alone Survivability'' on page 188). Note: The SAS feature is applicable only to Mediant 1000.
SIP User's Manual 3.6.2.5 3. Web-Based Management IP Connectivity The 'IP Connectivity' page displays online, read-only network diagnostic connectivity information on all destination IP addresses configured in the 'Tel to IP Routing' page (refer to ''Tel to IP Routing Table'' on page 200). Notes: • This information is available only if the parameter 'Enable Alt Routing Tel to IP' (refer to ''Routing General Parameters'' on page 198) is set to 1 (Enable) or 2 (Status Only).
Mediant 1000 & Mediant 600 Column Name Description Connectivity Status The status of the IP address' connectivity according to the method in the 'Connectivity Method' field. Quality Status OK = Remote side responds to periodic connectivity queries. Lost = Remote side didn't respond for a short period. Fail = Remote side doesn't respond. Init = Connectivity queries not started (e.g., IP address not resolved). Disable = The connectivity option is disabled, i.e.
SIP User's Manual 4 4. ini File Configuration ini File Configuration As an alternative to configuring the device using the Web interface (as described in ''WebBased Management'' on page 25), you can configure the device by loading an ini file containing user-defined parameters.
Mediant 1000 & Mediant 600 4.2 The ini File Structure The ini file can contain any number of parameters. The ini file can contain the following types of parameters: 4.2.
SIP User's Manual 4. ini File Configuration An example of an ini file containing individual ini file parameters is shown below: [SYSTEM Params] SyslogServerIP = 10.13.2.69 EnableSyslog = 1 ; These are a few of the system-related parameters. [WEB Params] LogoWidth = '339' WebLogoText = 'My Device' UseWeblogo = 1 ; These are a few of the Web-related parameters. [Files] CallProgressTonesFileName = 'cpusa.dat' 4.2.
Mediant 1000 & Mediant 600 Data line(s): Contain the actual values of the parameters. The values are interpreted according to the Format line. • The first word of the Data line must be the table’s string name followed by the Index field. • Items must be separated by a comma (,). • A Data line must end with a semicolon (;). End-of-Table Mark: Indicates the end of the table. The same string used for the table’s title, preceded by a backslash (\), e.g., [\MY_TABLE_NAME].
SIP User's Manual 4. ini File Configuration The table below displays an example of an ini file table parameter: [ PREFIX ] FORMAT PREFIX_Index = PREFIX_DestinationPrefix, PREFIX_DestAddress, PREFIX_SourcePrefix, PREFIX_ProfileId, PREFIX_MeteringCode, PREFIX_DestPort; PREFIX 0 = 10, 10.13.83.5, *, 0, 255, 0; PREFIX 1 = 20, 10.13.83.7, *, 0, 255, 0; PREFIX 2 = 30, 10.13.83.6, *, 0, 255, 0; PREFIX 3 = 20, 10.13.83.
Mediant 1000 & Mediant 600 4.3 Modifying an ini File You can modify an ini file currently used by a device. Modifying an ini file instead of loading an entirely new ini file preserves the device's current configuration, including factory default values. ¾ To modify an ini file, take these 4 steps: 1. Save the ini file from the device to your PC using the Web interface (refer to ''Backing Up and Restoring Configuration'' on page 276). 2.
SIP User's Manual 4. ini File Configuration ini File Parameter MIIRedundancyEnable Description Enables the Ethernet Interface Redundancy feature. When enabled, the device performs a switchover to the secondary (redundant) Ethernet port upon sensing a link failure in the primary Ethernet port. When disabled, the device operates with a single port (i.e. no redundancy support).
Mediant 1000 & Mediant 600 ini File Parameter DNS2IP Description This ini file table parameter configures the internal DNS table for resolving host names to IP addresses. Two different IP addresses (in dotted-decimal notation) can be assigned to a host name. The format of this parameter is as follows: [Dns2Ip] FORMAT Dns2Ip_Index = Dns2Ip_DomainName, Dns2Ip_FirstIpAddress, Dns2Ip_SecondIpAddress; [\Dns2Ip] Where, DomainName = Host name. FirstIpAddress = First IP address.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Notes: If the Internal SRV table is used, the device first attempts to resolve a domain name using this table. If the domain name isn't located, the device performs an SRV resolution using an external DNS server. This parameter can include up to 10 indices. To configure the Internal SRV table using the Web interface, refer to ''Internal SRV Table'' on page 208.
Mediant 1000 & Mediant 600 ini File Parameter Description EnableUDPPortTranslatio [0] = Disable UDP port translation (default). n [1] = Enable UDP port translation. When enabled, the device compares the source UDP port of the first incoming packet, to the remote UDP port stated in the opening of the channel. If the two UDP ports don't match, the NAT mechanism is activated. Consequently, the remote UDP port of the outgoing stream is replaced by the source UDP port of the first incoming packet.
SIP User's Manual 4. ini File Configuration ini File Parameter SyslogOutputMethod Description Determines the method used for Syslog messages. [0] = Send all Syslog messages to the defined Syslog server (default). [1] = Send all Syslog messages using the Debug Recording mechanism. [2] = Send only Error and Warning level Syslog messages using the Debug Recording mechanism. For a detailed description on Debug Recording, refer to Debug Recording (DR).
Mediant 1000 & Mediant 600 ini File Parameter Description VLANNativeVLANID For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. VLANOamVLANID For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. VLANControlVLANID For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. VLANMediaVLANID For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64.
SIP User's Manual 4. ini File Configuration ini File Parameter Description LocalControlSubnetMask For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. LocalControlDefaultGW For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64. LocalOAMIPAddress For a description of this parameter, refer to ''Configuring the IP Settings'' on page 64.
Mediant 1000 & Mediant 600 ini File Parameter Description GoldServiceClassDiffSer For a description of this parameter, refer to ''Configuring the QoS Settings'' on page 78. v BronzeServiceClassDiffS For a description of this parameter, refer to ''Configuring the QoS Settings'' on page 78.
SIP User's Manual 4.4.2 4. ini File Configuration System Parameters Table 4-2: System Parameters ini File Parameter GroundKeyDetection Description Enables analog ground-key detection (FXS and FXO modules implement ground-start signaling) per device. When disabled, the device uses loopstart signaling. [0] = Disable (default) [1] = Enable (enables ground start) Notes: EnableDiagnostics This parameter is applicable only to Mediant 1000.
Mediant 1000 & Mediant 600 ini File Parameter ActivityListToLog Description The Activity Log mechanism enables the device to send log messages (to a Syslog server) that report certain types of Web actions according to a pre-defined filter. The following filters are available: [PVC] (Parameters Value Change) = Changes made on-the-fly to parameters. [AFL] (Auxiliary Files Loading) = Loading of auxiliary files (e.g., via 'Certificate' screen).
SIP User's Manual 4. ini File Configuration ini File Parameter Description HeartBeatDestIP Destination IP address (in dotted format notation) to which the device sends proprietary UDP 'ping' packets. The default IP address is 0.0.0.0. HeartBeatDestPort Destination UDP port to which the heartbeat packets are sent. The range is 0 to 64000. The default is 0. HeartBeatIntervalmsec Delay (in msec) between consecutive heartbeat packets. EnableRAI [10] = 100000. [-1] = disabled (default).
Mediant 1000 & Mediant 600 ini File Parameter Description FarEndDisconnectSilenc Threshold of the packet count (in percentages) below which is considered silence by the device. eThreshold The valid range is 1 to 100%. The default is 8%. Note: Applicable only if silence is detected according to packet count (FarEndDisconnectSilenceMethod = 1).
SIP User's Manual 4. ini File Configuration ini File Parameter FXOCoeffFileURL Description Specifies the name of the FXO coefficients file and the location of the server (IP address or FQDN) from which it is loaded. For example: http://server_name/file, https://server_name/file. The maximum length of the URL address is 99 characters. Note: This parameter is applicable only to Mediant 1000.
Mediant 1000 & Mediant 600 ini File Parameter Description Set the number of BootP requests the device sends during start-up. The device stops sending BootP requests when either BootP reply is received or number of retries is reached. BootPSelectiveEnable Set the number of DHCP packets the device sends. After all packets were sent, if there's still no reply, the device loads from flash. [1] = 4 DHCP packets [1] = 1 BootP retry, 1 sec. [2] = 5 DHCP packets [2] = 2 BootP retries, 3 sec.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Serial Parameters DisableRS232 [0] = RS-232 serial port is enabled (default). [1] = RS-232 serial port is disabled. The RS-232 serial port can be used to change the networking parameters and view error / notification messages. For information on establishing a serial communications link with the device, refer to the device's Fast Track. SerialBaudRate Determines the value of the RS-232 baud rate.
Mediant 1000 & Mediant 600 ini File Parameter DisableWebTask ResetWebPassword Description [0] = Enable Web management (default). [1] = Disable Web management. Resets the username and password of the primary and secondary accounts to their defaults. [0] = Password and username retain their values (default). [1] = Password and username are reset (for the default username and password, refer to User Accounts). Note: The username and password cannot be reset from the Web interface (i.e.
SIP User's Manual 4. ini File Configuration ini File Parameter ScenarioFileName Description Defines the file name of the Scenario file to be loaded to the device. The file name must have the dat extension and can be up to 47 characters. For loading a Scenario using the Web interface, refer to ''Loading a Scenario to the Device'' on page 46. Telnet Parameters TelnetServerEnable For a description of this parameter, refer to ''Configuring the Application Settings'' on page 71.
Mediant 1000 & Mediant 600 4.4.4 Security Parameters Table 4-4: Security Parameters ini File Parameter EnableMediaSecurity Description For a description of this parameter, refer to ''Configuring the General Security Settings'' on page 123. MediaSecurityBehaviou For a description of this parameter, refer to ''Configuring the General Security Settings'' on page 123. r EnableSIPS For a description of this parameter, refer to ''General Parameters'' on page 166.
SIP User's Manual 4. ini File Configuration ini File Parameter Description OCSPServerIP Defines the IP address of the OCSP server. The default IP address is 0.0.0.0. OCSPServerPort Defines the OCSP server's TCP port number. The default port number is 2560. OCSPDefaultResponse Determines the default OCSP behavior when the server cannot be contacted. [0] = Rejects peer certificate (default). [1] = Allows peer certificate.
Mediant 1000 & Mediant 600 ini File Parameter Description IPSecPolicyLifeInSec, IPSecPolicyLifeInKB, IPSecPolicyProposalEncryption_X, IPSecPolicyProposalAuthentication_X, IPSecPolicyKeyExchangeMethodIndex, IPSecPolicyLocalIPAddressType, IPSecPolicyRemoteTunnelIPAddress, IPsecPolicyRemoteSubnetMask; [\IPSEC_SPD_TABLE] Where, Mode = IPSec mode of operation: [0] Transport, [1] Tunneling. PolicyRemoteIPAddress = Destination IP address (or FQDN) to which the IPSec mechanism is applied.
SIP User's Manual 4. ini File Configuration ini File Parameter Description (DES/SHA1 and 3DES/SHA1). IPsec is performed using the Transport mode. Notes: Each line in the table refers to a different IP destination. To support more than one Encryption / Authentication proposal, for each proposal specify the relevant parameters in the Format line. The proposal list must be contiguous. To configure the IKE table using the Web interface, refer to ''Configuring the IPSec Table'' on page 126.
Mediant 1000 & Mediant 600 ini File Parameter Description Notes: Each line in the table refers to a different IKE peer. To support more than one Encryption / Authentication / DH Group proposal, for each proposal specify the relevant parameters in the Format line. The proposal list must be contiguous. To configure the IKE table using the Web interface, refer to ''Configuring the IKE Table'' on page 130.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Internal Firewall Parameters This ini file table parameter configures the device's access list (firewall), which defines network traffic filtering rules.
Mediant 1000 & Mediant 600 4.4.5 RADIUS Parameters For detailed information on the supported RADIUS attributes, refer to ''Supported RADIUS Attributes'' on page 419. Table 4-5: RADIUS Parameters ini File Parameter Description EnableRADIUS For a description of this parameter, refer to ''Configuring the General Security Settings'' on page 123. AAAIndications For a description of this parameter, refer to ''Configuring RADIUS Accounting Parameters'' on page 247.
SIP User's Manual 4.4.6 4. ini File Configuration SNMP Parameters Table 4-6: SNMP Parameters ini File Parameter Description DisableSNMP For a description of this parameter, refer to ''Configuring the Management Settings'' on page 254. SNMPPort The device's local UDP port used for SNMP Get/Set commands. The range is 100 to 3999. The default port is 161. SNMPTrustedMGR_x Up to five IP addresses of remote trusted SNMP managers from which the SNMP agent accepts and processes get and set requests.
Mediant 1000 & Mediant 600 ini File Parameter Description SNMP Trap Parameters SNMPManagerTableIP_x For a description of this parameter, refer to ''Configuring the SNMP Managers Table'' on page 257. SNMPManagerTrapPort_x For a description of this parameter, refer to ''Configuring the SNMP Managers Table'' on page 257. SNMPManagerTrapUser_ This parameter can be set to the name of any configured SNMPV3 user to associate with this trap destination.
SIP User's Manual 4. ini File Configuration ini File Parameter Description authNoPriv(2), authentication protocol MD5, authentication text password 'myauthkey', and ReadWriteGroup2. Notes: 4.4.7 This parameter can include up to 10 indices. To configure SNMP v3 users through the Web interface, refer to ''Configuring SNMP V3 Users'' on page 259. For an explanation on using ini file table parameters, refer to ''Structure of ini File Table Parameters'' on page 293.
Mediant 1000 & Mediant 600 ini File Parameter Description DNSQueryType For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. ProxyDNSQueryType For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. ProxyIP This ini file table parameter configures the Proxy Set ID table for configuring up to six Proxy Sets, each with up to five Proxy server IP addresses.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Notes: This table parameter can include up to 6 indices (0-5). For configuring the Proxy Sets, refer to the ini file parameter ProxyIP. For configuring the Proxy Set ID table using the Web interface, refer to ''Proxy Sets Table'' on page 153. For an explanation on using ini file table parameters, refer to ''Structure of ini File Table Parameters'' on page 293.
Mediant 1000 & Mediant 600 ini File Parameter OfferUnencryptedSRTCP Description Determines whether the device adds the UNENCRYPTED_SRTCP attribute to outgoing SDP messages when SRTP/SRTCP is enabled. [0] Disable (default). [1] Enable. For example: a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:WxMz3YE0fcbjVJOGgSxweCZxySisl6SWi103t6No UNENCRYPTED_SRTCP Note: When enabled, the device adds the UNENCRYPTED_SRTCP attribute to the ‘crypto’ attribute of the outgoing SDP (SRTCP is still encrypted).
SIP User's Manual 4. ini File Configuration ini File Parameter Description RegistrarIP For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. RegistrarTransportType For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146. RegistrarName For a description of this parameter, refer to ''Proxy & Registration Parameters'' on page 146.
Mediant 1000 & Mediant 600 ini File Parameter Description Account_Register, Account_ContactUser; [\Account] Where, ServedTrunkGroup = Trunk Group ID for which the device performs registration/authentication to a destination IP Group. ServedIPGroup = Currently not applicable (see note below). ServingIPGroup = Destination IP (Group) to where the device sends the REGISTER requests (and/or digest authentication username and password) for registering (and/or authenticating) the Trunk Group.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Where, Description = Brief description of the IP Group. ProxySetId = Proxy Set ID associated with the IP Group. SIPGroupName = Request URI host name used in INVITE and REGISTER messages. SendInviteToProxy = If enabled (1), the INVITE as a result of REFER/3xx messages are sent to the IP Group, overriding the Refer-To/Contact destination.
Mediant 1000 & Mediant 600 ini File Parameter Description UseAORInReferToHeader Defines the source for the SIP URI set in the Refer-To header of outgoing REFER messages. [0] = Use SIP URI from Contact header of the initial call (default). [1] = Use SIP URI from To/From header of the initial call. UseTelURIForAssertedID For a description of this parameter, refer to ''SIP General Parameters'' on page 134.
SIP User's Manual 4. ini File Configuration ini File Parameter Description EnableSilenceSuppInSDP Determines the device's behavior upon receipt of SIP Re-INVITE messages that include the silencesupp:off attribute. EnableRport [0] = Disregard the silecesupp attribute (default). [1] = Handle incoming Re-INVITE messages that include the silencesupp:off attribute in the SDP as a request to switch to the Voice-Band-Data (VBD) mode.
Mediant 1000 & Mediant 600 ini File Parameter Description DefaultReleaseCause For a description of this parameter, refer to ''SIP General Parameters'' on page 134. IPAlertTimeout For a description of this parameter, refer to ''SIP General Parameters'' on page 134. SIPPSessionExpires For a description of this parameter, refer to ''SIP General Parameters'' on page 134. SessionExpiresMethod For a description of this parameter, refer to ''SIP General Parameters'' on page 134.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Where, IsEnabled = Enables [1] or disables [0] call waiting. Port = Port number. Module = Module number. For example: [CallWaitingPerPort] CallWaitingPerPort 0 = 0,1,1$$; CallWaitingPerPort 1 = 1,2,1$$; [\CallWaitingPerPort] If enabled, when an FXS interface receives a call on a busy endpoint, it responds with a 182 response (and not with a 486 busy). The device plays a call waiting indication signal.
Mediant 1000 & Mediant 600 ini File Parameter 3WayConferenceMode Description Defines the mode of operation when the 3-Way Conference feature is used. [0] = Conference-initiating INVITE (sent by the device), uses the ConferenceID concatenated with a unique identifier as the RequestUR (default). [1] = Conference-initiating INVITE (sent by the device), uses only the ConferenceID as the Reques-URI.
SIP User's Manual 4. ini File Configuration ini File Parameter WarningToneDuration FirstCallWaitingToneID Description Defines the duration (in seconds) for which Off-Hook Warning Tone is played to the user. The valid range is -1 to 2,147,483,647. The default is 600. Notes: This parameter is applicable only to Mediant 1000. A negative value indicates that the tone is played infinitely. Determines the index of the first Call Waiting Tone in the CPT file.
Mediant 1000 & Mediant 600 ini File Parameter TxDTMFOption Description This ini file table parameter determines a single or several (up to 5) preferred transmit DTMF negotiation methods. The format of this parameter is as follows: [TxDTMFOption] FORMAT TxDTMFOption_Index = TxDTMFOption_Type; [\TxDTMFOption] For example: [TxDTMFOption] TxDTMFOption 0 = 1; [\TxDTMFOption] Notes: DisableAutoDTMFMute DTMF negotiation methods are prioritized according to the order of their appearance.
SIP User's Manual 4. ini File Configuration ini File Parameter Description 3xxBehavior For a description of this parameter, refer to ''SIP General Parameters'' on page 134. EnablePChargingVector For a description of this parameter, refer to ''SIP General Parameters'' on page 134. EnableVMURI For a description of this parameter, refer to ''SIP General Parameters'' on page 134. EmergencyRegretTimeout For a description of this parameter, refer to Advanced Parameters on page 166.
Mediant 1000 & Mediant 600 ini File Parameter Authentication Description This ini file table parameter defines a username and password combination for authenticating each device port.
SIP User's Manual 4. ini File Configuration ini File Parameter SASDefaultGatewayIP Description For a description of this parameter, refer to "Stand-Alone Survivability" on page 188. Note: SAS is applicable only to Mediant 1000. SASRegistrationTime For a description of this parameter, refer to "Stand-Alone Survivability" on page 188. Note: SAS is applicable only to Mediant 1000. SASShortNumberLength For a description of this parameter, refer to "Stand-Alone Survivability" on page 188.
Mediant 1000 & Mediant 600 ini File Parameter Description standards (e.g., payload type of G.711 U-law is always 0). Other values can be set dynamically. If no value is specified for a dynamic field, a default value is assigned. If a value is specified for a hardcoded field, the value is ignored. IPProfile Only the ptime of the first coder in the defined coder list is declared in INVITE / 200 OK SDP, even if multiple coders are defined. If the coder G.
SIP User's Manual 4. ini File Configuration ini File Parameter TelProfile Description The 'Profile Name' assigned to a Profile index, must enable users to identify it intuitively and easily. To configure the IP Profile table using the Web interface, refer to ''IP Profile Settings'' on page 216. For a description of using ini file table parameters, refer to ''Structure of ini File Table Parameters'' on page 293. This ini file table parameter configures the Tel Profile Settings table.
Mediant 1000 & Mediant 600 4.4.8 Media Server Parameters Table 4-8: Media Server Parameters ini File Parameter Description MSCMLID For a description of this parameter, refer to "Configuring the IPmedia Parameters" on page 242. AmsProfile Must be set to 1 to use advanced audio. AASPackagesProfile Must be set to 3 to use advanced audio. AmsPrimaryLanguage Determines the primary language used in the advanced audio package. The default value is “eng”.
SIP User's Manual 4. ini File Configuration ini File Parameter Description BipOnConference For a description of this parameter, refer to "Configuring the IPmedia Parameters" on page 242. TranscodingID For a description of this parameter, refer to "Configuring the IPmedia Parameters" on page 242. ActiveSpeakersNotifica For a description of this parameter, refer to Configuring the IPmedia Settings on page 92.
Mediant 1000 & Mediant 600 ini File Parameter Description DigitPatternForwardOn For a description of this parameter, refer to ''Configuring the Voice Mail (VM) Parameters'' on page 244. NoAnswer DigitPatternForwardOn For a description of this parameter, refer to ''Configuring the Voice Mail (VM) Parameters'' on page 244. DND DigitPatternForwardNo For a description of this parameter, refer to ''Configuring the Voice Mail (VM) Parameters'' on page 244.
SIP User's Manual 4. ini File Configuration ini File Parameter Description TerminationSide_x Same as the description for parameter TerminationSide, but for a specific trunk ID (x = 0 - 3). ClockMaster For a description of this parameter, refer to "Configuring the Trunk Settings" on page 96. ClockMaster_x Same as the description for parameter ClockMaster, but for a specific trunk ID (x = 0 - 3).
Mediant 1000 & Mediant 600 ini File Parameter Description ISDNRxOverlap_x For a description of this parameter, refer to "Configuring the Trunk Settings" on page 96. ISDNRxOverlap [0] = Disabled (default). [1] = Enabled. Any number bigger than one = Number of digits to receive. Notes: If enabled, the device receives ISDN called number that is sent in the 'Overlap' mode.
SIP User's Manual 4. ini File Configuration ini File Parameter Description ISDN Flexible Behavior Parameters ISDN protocol is implemented in different Switches / PBXs by different vendors. Several implementations vary a little from the specification. Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters are used. ISDNInCallsBehavior For a description of this parameter, refer to "Configuring the Trunk Settings" on page 96.
Mediant 1000 & Mediant 600 ini File Parameter Description DigitMapping For a description of this parameter, refer to ''DTMF & Dialing Parameters'' on page 160. TimeBetweenDigits For a description of this parameter, refer to ''DTMF & Dialing Parameters'' on page 160. MaxDigits For a description of this parameter, refer to ''DTMF & Dialing Parameters'' on page 160. TimeForDialTone For a description of this parameter, refer to ''DTMF & Dialing Parameters'' on page 160.
SIP User's Manual 4. ini File Configuration ini File Parameter CauseMapSIP2ISDN Description This ini file table parameter maps SIP Responses to Q.850 Release Causes. The format of this parameter is as follows: [CauseMapSIP2ISDN] FORMAT CauseMapSIP2ISDN_Index = CauseMapSIP2ISDN_SipResponse, CauseMapSIP2ISDN_IsdnReleaseCause; [\CauseMapSIP2ISDN] Where, SipResponse = SIP Response IsdnReleaseCause = Q.
Mediant 1000 & Mediant 600 ini File Parameter SITQ850Cause Description Determines the Q.850 cause value specified in the Reason header that is included in a 4xx response when Special Information Tone (SIT) is detected on an IP-to-Tel call. The valid range is 0 to 127. The default value is 34. UserToUserHeaderForm Determines the format of the User-to-User header.
SIP User's Manual 4. ini File Configuration ini File Parameter Description ISDNSubAddressFormat Determines the format of the 'subaddress' value for ISDN Calling and Called numbers. [0] = ASCII (default). [1] = BCD (Binary Coded Decimal) For IP-to-Tel calls, if the incoming SIP INVITE message includes subaddress values in the 'isub' parameter for the Called Number (in the Request-URI) and/or the Calling Number (in the From header), these values are interworked to the outgoing ISDN SETUP message.
Mediant 1000 & Mediant 600 ini File Parameter EnableAOC Description [0] = Not used (default). [1] = ISDN Advice of Charge (AOC) messages are interworked to SIP. The device supports receipt of ISDN (Euro ISDN) AOC messages. AOC messages can be received during a call (FACILITY messages) or at the end of a call (DISCONNECT or RELEASE messages). The device converts the AOC messages into SIP INFO (during a call) and BYE (end of a call) messages, using a proprietary AOC SIP header.
SIP User's Manual 4. ini File Configuration ini File Parameter Description CASAddressingDelimite Determines if delimiters are added to the dialed address or dialed ANI parameters. rs [0] = Disable (default) [1] = Enable When this parameter is enabled, delimiters such as '*', '#', and 'ST' are added to the dialed address or dialed ANI parameters. When it is disabled, the address and ANI strings remain without delimiters. Note: This parameter is not applicable to BRI interfaces.
Mediant 1000 & Mediant 600 ini File Parameter Description SendIEonTG For a description of this parameter, refer to ''Configuring the Digital Gateway Parameters'' on page 235. ISDNDMSTimerT310 Overrides the T310 timer for the DMS-100 ISDN variant. T310 defines the timeout between the reception of a PROCEEDING message and the reception of an ALERTING / CONNECT message. The valid range is 10 to 30. The default value is 10 (seconds).
SIP User's Manual 4. ini File Configuration 4.4.12 Analog Telephony Parameters Note: Analog parameters are applicable only to Mediant 1000. Table 4-12: Analog Telephony Parameters ini File Parameter Prefix2ExtLine Description Defines a string prefix (e.g., '9') that when dialed from an FXS port causes the device's FXS port to play a secondary dial tone and then restart digit collection. The valid range is a 1-character string. The default is an empty string.
Mediant 1000 & Mediant 600 ini File Parameter ChargeCode Description This ini file table parameter configures metering tones (and their time intervals) that the device's FXS interface generates to the Tel side.
SIP User's Manual 4. ini File Configuration ini File Parameter Description For example: [TargetOfChannel] TargetOfChannel 1 = 1001,1,0,1; (Automatic dialing on Port 1, Module 1) [\TargetOfChannel] Notes: CallerDisplayInfo The indexing of this ini file table parameter starts at 1. The numbering of channels starts at 0. Define this parameter for each device port that implements Automatic Dialing.
Mediant 1000 & Mediant 600 ini File Parameter FwdInfo Description This ini file table parameter forwards IP-to-Tel calls (using SIP 302 response), based on the device's port to which the call is routed. The format of this parameter is as follows: [FwdInfo] FORMAT FwdInfo_Index = FwdInfo_Type, FwdInfo_Destination, FwdInfo_NoReplyTime, FwdInfo_Port, FwdInfo_Module; [\FwdInfo] Where, Type = Forward Type (for a list of options, refer to ''Call Forward'' on page 222).
SIP User's Manual 4. ini File Configuration ini File Parameter Description The numbering of ports starts at 0. If a port isn't configured, its Caller ID generation / detection are determined according to the global parameter EnableCallerID (described in ''Supplementary Services'' on page 176). To configure Call ID Permissions using the Web interface, refer to ''Caller ID Permissions'' on page 224.
Mediant 1000 & Mediant 600 ini File Parameter SubscribeRetryTime Description For a description of this parameter, refer to ''Supplementary Services'' on page 176. MWIServerTransportTy For a description of this parameter, refer to ''Supplementary Services'' on page 176. pe MWIExpirationTime For a description of this parameter, refer to ''Supplementary Services'' on page 176. StutterToneDuration For a description of this parameter, refer to ''Supplementary Services'' on page 176.
SIP User's Manual 4. ini File Configuration ini File Parameter Description BlindTransferDisconne Defines the duration (in milliseconds) for which the device waits for a disconnection from the Tel side after the Blind Transfer Code ctTimeout (KeyBlindTransfer) has been identified. When this timer expires, a SIP REFER message is sent toward the IP side. If this parameter is set to 0, the REFER message is immediately sent. The valid range is 0 to 1,000,000. The default is 0.
Mediant 1000 & Mediant 600 ini File Parameter Description NTTDIDSignallingForm Determines the type of Direct Inward Dialing (DID) signaling support for NTT (Japan) modem: DTMF- or Frequency Shift Keying (FSK)-based signaling. The devices can be connected to Japan's NTT PBX using 'Modem' DID lines. These DID lines are used to deliver a called number to the PBX. [0] = FSK-based signaling (default) [1] = DTMF-based signaling Note: This parameter is applicable only to FXS interfaces.
SIP User's Manual 4. ini File Configuration ini File Parameter Description CurrentDisconnectDura The duration (in msec) of the current disconnect pulse. The range is 200 to 1500. The default is 900. tion Notes: This parameter is applicable for both FXS and FXO interfaces. The FXO interface detection range is approximately 200 msec of the parameter's value plus 100. For example, if CurrentDisconnectDuration is 200 msec, then the detection range is 100 to 500 msec.
Mediant 1000 & Mediant 600 ini File Parameter Description BellcoreVMWITypeOne Selects the Bellcore VMWI sub-standard. Standard [0] = Between rings (default). [1] = Not ring related. 4.4.13 Number Manipulation and Routing Parameters Table 4-13: Number Manipulation and Routing Parameters ini File Parameter TrunkGroup Description This ini file table parameter defines the device's endpoints/Trunks. Alternatively, you can use the Web interface (refer to Configuring the Trunk Group Table on page 226).
SIP User's Manual 4. ini File Configuration ini File Parameter Description DefaultNumber For a description of this parameter, refer to ''DTMF & Dialing Parameters'' on page 160. ChannelSelectMode For a description of this parameter, refer to ''SIP General Parameters'' on page 134. TrunkGroupSettings This ini file table parameter defines rules for port allocation per Trunk Group. If no rule exists, the global rule defined by the parameter ChannelSelectMode takes effect.
Mediant 1000 & Mediant 600 ini File Parameter Description CopyDestOnEmptySource [0] = Leave Source Number empty (default). [1] = If the Source Number of a Tel-to-IP call is empty, the Destination Number is copied to the Source Number. AddNPIandTON2CallingN For a description of this parameter, refer to Routing General Parameters on page 198. umber AddNPIandTON2CalledNu For a description of this parameter, refer to Routing General Parameters on page 198.
SIP User's Manual 4. ini File Configuration ini File Parameter Description Notes: PSTNPrefix This parameter can include up to 50 indices. The parameters SrcIPGroupID, DestHostPrefix, and SrcHostPrefix are currently not applicable and must be left empty (or -1). (They are used only for IP-to-IP routing, supported in the next applicable release). The phone prefix for destination (DestinationPrefix) and source (SourcePrefix) addresses can be a single number or a range of numbers.
Mediant 1000 & Mediant 600 ini File Parameter Description DestHostPrefix = Request URI host name prefix of the incoming INVITE message. SrcHostPrefix = From URI host name prefix of the incoming INVITE message.
SIP User's Manual 4. ini File Configuration ini File Parameter Description SwapTel2IPCalled&Calling If enabled, the device swaps the calling and called numbers received from the Tel side. The INVITE message contains the swapped numbers. Numbers Applicable for Tel-to-IP calls. [0] = Disabled (default) [1] = Swap calling and called numbers AddTON2RPI For a description of this parameter, refer to ''SIP General Parameters'' on page 134.
Mediant 1000 & Mediant 600 ini File Parameter Description (RPID) header by using the EnableRPIHeader and AddTON2RPI parameters. NumberMapIP2Tel To configure manipulation of destination numbers for Tel-to-IP calls using the Web interface (i.e., in the 'Destination Phone Number Manipulation Table for Tel-to-IP Calls' table), refer to ''Configuring the Number Manipulation Tables'' on page 190).
SIP User's Manual 4. ini File Configuration ini File Parameter Description The Source IP address can include the 'x' wildcard to represent single digits. For example: 10.8.8.xx represents all addresses between 10.8.8.10 and 10.8.8.99. The Source IP address can include the asterisk ('*') wildcard to represent any number between 0 and 255. For example, 10.8.8.* represents all the addresses between 10.8.8.0 and 10.8.8.255.
Mediant 1000 & Mediant 600 ini File Parameter Description Notes: RemoveFromLeft, RemoveFromRight, Prefix2Add, Suffix2Add, LeaveFromRight, NumberType, NumberPlan, and IsPresentationRestricted are applied if the called and calling numbers match the DestinationPrefix and SourcePrefix conditions. The manipulation rules are executed in the following order: RemoveFromLeft, RemoveFromRight, LeaveFromRight, Prefix2Add, and Suffix2Add. Parameters can be skipped by using two dollar signs ('$$').
SIP User's Manual 4. ini File Configuration ini File Parameter Description IsPresentationRestricted = Calling number presentation (0 to allow presentation; 1 to restrict presentation). For example: [SourceNumberMapIp2Tel] SourceNumberMapIp2Tel 0 = 22,03,$$,$$,$$,$$,2,667,$$,$$;SourceNumberMapIp2Tel 1 = 034,01,1.1.1.1,$$,0,2,$$,$$,972,$$,10; [\SourceNumberMapIp2Tel] Notes: Version 5.
Mediant 1000 & Mediant 600 ini File Parameter Description For ETSI ISDN variant, the following Number Plan and Type combinations (Plan/Type) are supported in the Destination and Source Manipulation tables: 0,0 = Unknown, Unknown 9,0 = Private, Unknown 9,1 = Private, Level 2 Regional 9,2 = Private, Level 1 Regional 9,3 = Private, PISN Specific 9,4 = Private, Level 0 Regional (local) 1,0 = Public(ISDN/E.164), Unknown 1,1 = Public(ISDN/E.
SIP User's Manual 4. ini File Configuration ini File Parameter AltRouteCauseIP2Tel Description This ini file table parameter configures call failure reason values received from the PSTN side (in Q.931 presentation). If a call is released as a result of one of these reasons, the device attempts to locate an alternative Trunk Group for the call in the 'IP to Trunk Group Routing' table.
Mediant 1000 & Mediant 600 ini File Parameter Description Alternative Routing Parameters RedundantRoutingMode Determines the type of redundant routing mechanism to implement when a call can’t be completed using the main route. [0] = No redundant routing is used. If the call can’t be completed using the main route (using the active Proxy or the first matching rule in the internal routing table), the call is disconnected. [1] = Internal routing table is used to locate a redundant route (default).
SIP User's Manual 4. ini File Configuration ini File Parameter Description Several entries with the same NPI-TON or Phone-Context are allowed. In this scenario, a Tel-to-IP call uses the first match. Phone-Context '+' is a unique as it doesn't appear in the RequestURI as a Phone-Context parameter. Instead, it's added as a prefix to the phone number. The '+' isn't removed from the phone number in the IP-to-Tel direction.
Mediant 1000 & Mediant 600 ini File Parameter Description FaxModemBypassM For a description of this parameter, refer to ''Configuring the Fax / Modem / CID Settings'' on page 84. FaxBypassPayloadType For a description of this parameter, refer to ''Configuring the RTP / RTCP Settings'' on page 88. CallerIDTransportType For a description of this parameter, refer to ''Configuring the Fax / Modem / CID Settings'' on page 84. ModemBypassPayloadTyp Modem Bypass dynamic payload type. The range is 0-127.
SIP User's Manual 4. ini File Configuration ini File Parameter NSEMode Description Cisco compatible fax and modem bypass mode. [0] = NSE disabled (default) [1] = NSE enabled Notes: This feature can be used only if VxxModemTransportType = 2 (Bypass). If NSE mode is enabled, the SDP contains the following line: 'a=rtpmap:100 X-NSE/8000'. To use this feature: -- The Cisco gateway must include the following definition: 'modem passthrough nse payload-type 100 codec g711alaw'.
Mediant 1000 & Mediant 600 ini File Parameter Description RFC2198PayloadType For a description of this parameter, refer to ''Configuring the RTP / RTCP Settings'' on page 88. EnableSilenceCompressio n For a description of this parameter, refer to ''Configuring the Voice Settings'' on page 81. IsCiscoSCEMode Determines whether a Cisco gateway exists at the remote side. [0] = No Cisco gateway exists at the remote side (default). [1] = A Cisco gateway exists at the remote side.
SIP User's Manual 4. ini File Configuration ini File Parameter Description DTMFGenerationTwist For a description of this parameter, refer to ''Configuring the Voice Settings'' on page 81. DTMFInterDigitInterval Time in msec between generated DTMF digits to PSTN side (if TxDTMFOption = 1, 2 or 3). The default value is 100 msec. The valid range is 0 to 32767. DTMFDigitLength Time (in msec) for generating DTMF tones to the PSTN side (if TxDTMFOption = 1, 2 or 3).
Mediant 1000 & Mediant 600 ini File Parameter KeyBlindTransfer Description Keypad sequence that activates blind transfer for Tel-to-IP calls. There are two possible scenarios: Option 1: After this sequence is dialed, the current call is put on hold (using Re-INVITE), a dial tone is played to the B-channel, and then phone number collection starts. Option 2: A Hook-Flash is pressed, the current call is put on hold, a dial tone is played to the B-channel, and then digit collection starts.
SIP User's Manual 4. ini File Configuration ini File Parameter Description RTCPXREscIP For a description of this parameter, refer to "Configuring the RTP / RTCP Settings" on page 88. RTCPXRReportMode For a description of this parameter, refer to "Configuring the RTP / RTCP Settings" on page 88. 4.4.15 Auxiliary / Configuration Files Parameters The configuration files (i.e.
Mediant 1000 & Mediant 600 ini File Parameter Description UserInfoFileName The name (and path) of the file containing the User Information data. SaveConfiguration Determines if the device's configuration (parameters and files) is saved to flash (non-volatile memory). SIP User's Manual [0] = Configuration isn't saved to flash memory. [1] = Configuration is saved to flash memory (default).
SIP User's Manual 5 5. Default Settings Default Settings You can restore the device's factory default settings or define your own default settings for the device. Note: You can also restore factory default settings using the device's hardware reset button (refer to the device's Fast Track Guide). 5.1 Defining Default Settings The device is shipped with factory default configuration values stored on its non-volatile flash memory.
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 386 Document #: LTRT-83303
SIP User's Manual 6 6. Auxiliary Configuration Files Auxiliary Configuration Files This section describes the auxiliary files (with the dat file extension), which are loaded, in addition to the ini file, to the device. You can load the auxiliary files to the device using one of the following methods: 6.
Mediant 1000 & Mediant 600 You can specify several tones of the same type. These additional tones are used only for tone detection. Generation of a specific tone conforms to the first definition of the specific tone. For example, you can define an additional dial tone by appending the second dial tone's definition lines to the first tone definition in the ini file. The device reports dial tone detection if either of the two tones is detected.
SIP User's Manual 6. Auxiliary Configuration Files • Second Signal On Time [10 msec]: 'Signal On' period (in 10 msec units) for the second cadence on-off cycle. Can be omitted if there isn't a second cadence. • Second Signal Off Time [10 msec]: 'Signal Off' period (in 10 msec units) for the second cadence on-off cycle. Can be omitted if there isn't a second cadence. • Third Signal On Time [10 msec]: 'Signal On' period (in 10 msec units) for the third cadence ON-OFF cycle.
Mediant 1000 & Mediant 600 6.2 Configuring the Distinctive Ringing Section of the ini File Distinctive Ringing is only applicable to FXS interface. Using the distinctive ringing section of this auxiliary file, you can create up to 16 distinctive ringing patterns. Each ringing pattern configures the ringing tone frequency and up to four ringing cadences. The same ringing frequency is used for all the ringing pattern cadences.
SIP User's Manual 6. Auxiliary Configuration Files • Fourth (Burst) Ring On Time [10 msec]: 'Ring Off' period (in 10 msec units) for the fourth cadence on-off cycle. • Fourth (Burst) Ring Off Time [10 msec]: 'Ring Off' period (in 10 msec units) for the fourth cadence on-off cycle. Note: In SIP, the distinctive ringing pattern is selected according to Alert-Info header that is included in the INVITE message. For example, Alert-Info , or Alert-Info.
Mediant 1000 & Mediant 600 6.3 Prerecorded Tones (PRT) File The Call Progress Tones (CPT) mechanism has several limitations such as a limited number of predefined tones and a limited number of frequency integrations in one tone. To work around these limitations and provide tone generation capability that is more flexible, the Prerecorded Tones (PRT) file can be used.
SIP User's Manual 6.5 6. Auxiliary Configuration Files Coefficient File The Coeff_FXS.dat file is used to provide best termination and transmission quality adaptation for different line types for FXS interfaces. This adaptation is performed by modifying the telephony interface characteristics (such as DC and AC impedance, feeding current, and ringing voltage). The coeff.
Mediant 1000 & Mediant 600 The following is an example of an ini file that includes these definitions. This ini file is converted (using the TrunkPack Conversion Utility - refer to the Product Reference Manual) to a binary file and loaded to the device. ; Example of dial-plan configuration. ; This file contains two dial plans: you may specify which ; one to use in CAS configuration. [ PLAN1 ] ; Define the area codes 02, 03, 04. ; In these area codes, phone numbers have 7 digits.
SIP User's Manual 6.7 6. Auxiliary Configuration Files User Information File The User Information file is a text file that maps PBX extensions, connected to the device, to global IP numbers. In this context, a global IP phone number (alphanumerical) serves as a routing identifier for calls in the 'IP World'. The PBX extension uses this mapping to emulate the behavior of an IP phone.
Mediant 1000 & Mediant 600 The maximum permissible size of the file is 10,800 bytes for Mediant 1000 analog modules and 108,000 bytes for digital modules. Each PBX extension registers separately (a REGISTER message is sent for each entry only if AuthenticationMode is set to Per Endpoint) using the IP number in the From / To headers. The REGISTER messages are sent gradually.
SIP User's Manual 7 7. IP Telephony Capabilities IP Telephony Capabilities This section describes the device's IP telephony capabilities. 7.1 Configuring the DTMF Transport Types You can control the way DTMF digits are transported over the IP network to the remote endpoint, by using one of the following modes: Using INFO message according to Nortel IETF draft: DTMF digits are carried to the remote side in INFO messages.
Mediant 1000 & Mediant 600 Note that to set the RFC 2833 payload type with a different value (other than its default, 96) configure the RFC2833PayloadType (RFC 2833 Payload Type) parameter. The device negotiates the RFC 2833 payload type using local and remote SDP and sends packets using the payload type from the received SDP. The device expects to receive RFC 2833 packets with the same payload type as configured by the RFC2833PayloadType parameter.
SIP User's Manual 7. IP Telephony Capabilities remote endpoint at the establishment of the call. During a call, when a fax / modem signal is detected, transition from voice to VBD (or T.38) is automatically performed and no additional SIP signaling is required. If negotiation fails (i.e., no match is achieved for any of the transport capabilities), fallback to existing logic occurs (according to the parameter IsFaxUsed). 7.2.
Mediant 1000 & Mediant 600 7.2.2.1.1 Switching to T.38 Mode using SIP Re-INVITE In the Switching to T.38 Mode using SIP Re-INVITE mode, upon detection of a fax signal, the terminating device negotiates T.38 capabilities using a Re-INVITE message. If the farend device doesn't support T.38, the fax fails. In this mode, the parameter FaxTransportMode is ignored. To configure T.38 mode using SIP Re-INVITE messages, set IsFaxUsed to 1.
SIP User's Manual 7.
Mediant 1000 & Mediant 600 When configured for NSE mode, the device includes in its SDP the following line: a=rtpmap:100 X-NSE/8000 (where 100 is the NSE payload type) The Cisco gateway must include the following definition: "modem passthrough nse payload-type 100 codec g711alaw". To configure NSE mode, perform the following configurations: 7.2.2.
SIP User's Manual 7. IP Telephony Capabilities Echo Canceller = on Silence Compression = off Echo Canceller Non-Linear Processor Mode = off Dynamic Jitter Buffer Minimum Delay = 40 Dynamic Jitter Buffer Optimization Factor = 13 When the device initiates a fax session using G.711, a ‘gpmd’ attribute is added to the SDP according to the following format: For G.711A-law: a=gpmd:0 vbd=yes;ecan=on For G.
Mediant 1000 & Mediant 600 7.2.2.7 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) Echo Canceller Non-Linear Processor Mode = off Jitter buffering optimizations To configure fax / modem transparent with events mode, perform the following configurations: 7.2.
SIP User's Manual 7. IP Telephony Capabilities Configure the following parameters to use bypass mode for V.34 faxes and T.38 for T.30 faxes: 7.2.3.2 FaxTransportMode = 1 (Relay) V34ModemTransportType = 2 (Modem bypass) V32ModemTransportType = 2 V23ModemTransportType = 2 V22ModemTransportType = 2 Using Relay mode for both T.30 and V.34 faxes In this scenario, V.34 fax machines are forced to use their backward compatibility with T.30 faxes and operate in the slower T.30 mode.
Mediant 1000 & Mediant 600 In the example, V.152 implementation is supported (using the dynamic payload type 96 and G.711 u-law as the VBD codec) as well as the voice codecs G.711 µ-law and G.729. Instead of using VBD transport mode, the V.152 implementation can use alternative relay fax transport methods (e.g., fax relay over IP using T.38). The preferred V.152 transport method is indicated by the SDP ‘pmft’ attribute.
SIP User's Manual 7. IP Telephony Capabilities Figure 7-1: Call Flow for One-Stage Dialing One-stage dialing incorporates the following FXO functionality: Waiting for Dial Tone: Enables the device to dial the digits to the Tel side only after detecting a dial tone from the PBX line. The ini file parameter IsWaitForDialTone is used to configure this operation. Time to Wait Before Dialing: Defines the time (in msec) between seizing the FXO line and starting to dial the digits.
Mediant 1000 & Mediant 600 7.3.1.2 Two-Stage Dialing Two-stage dialing is when the IP caller is required to dial twice. The caller initially dials to the FXO device and only after receiving a dial tone from the PBX (via the FXO device), dials the destination telephone number. Figure 7-2: Call Flow for Two-Stage Dialing Two-stage dialing implements the Dialing Time feature. Dialing Time allows you to define the time that each digit can be separately dialed.
SIP User's Manual 7. IP Telephony Capabilities Relevant parameters: EnableReversalPolarity, EnableCurrentDisconnect, CurrentDisconnectDuration, CurrentDisconnectDefaultThreshold, and TimeToSampleAnalogLineVoltage. Detection of Reorder, Busy, Dial, and Special Information Tone (SIT) tones: The call is immediately disconnected after a Reorder, Busy, Dial, or SIT tone is detected on the Tel side (assuming the PBX / CO generates this tone).
Mediant 1000 & Mediant 600 The "start dial" signal is a wink from the PBX to the FXO device. The FXO then sends the last four to five DTMF digits of the called number. The PBX uses these digits to complete the routing directly to an internal station (telephone or equivalent) 7.3.
SIP User's Manual 7.3.2.2 7. IP Telephony Capabilities 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 7-3: Call Flow for Collecting Digits Mode 7.3.2.3 Ring Detection Timeout The ini file parameters IsWaitForDialTone and WaitForDialTone apply to Ring Detection Timeout.
Mediant 1000 & Mediant 600 7.3.2.4 FXO Supplementary Services The FXO supplementary services include the following: Hold / Transfer toward the Tel side: The ini file parameter LineTransferMode must be set to 0 (default). If the FXO receives a hook-flash from the IP side (using out-ofband or RFC 2833), the device sends the hook-flash to the Tel side by performing one of the following: • Performing a hook flash (i.e.
SIP User's Manual 7. IP Telephony Capabilities The X-Detect event notification process is as follows: 1. For IP-to-Tel or Tel-to-IP calls, the device receives a SIP request message (using the X-Detect header) that the remote party wishes to detect events on the media stream. For incoming (IP-to-Tel) calls, the request must be indicated in the initial INVITE and responded to either in the 183 response (for early dialogs) or in the 200 OK response (for confirmed dialogs).
Mediant 1000 & Mediant 600 7.5 RTP Multiplexing (ThroughPacket) The device supports a proprietary method to aggregate RTP streams from several channels to reduce the bandwidth overhead caused by the attached Ethernet, IP, UDP, and RTP headers, and to reduce the packet / data transmission rate. This option reduces the load on network routers and can typically save 50% (e.g., for G.723) on IP bandwidth.
SIP User's Manual 7. IP Telephony Capabilities The default settings of 10 msec Minimum delay and 10 Optimization Factor should provide a good compromise between delay and error rate. The jitter buffer ‘holds’ incoming packets for 10 msec before making them available for decoding into voice. The coder polls frames from the buffer at regular intervals in order to produce continuous speech.
Mediant 1000 & Mediant 600 Destination IP address is disallowed if no ping to the destination is available (ping is continuously initiated every seven seconds), when an inappropriate level of QoS was detected, or when a DNS host name is not resolved. The QoS level is calculated according to delay or packet loss of previously ended calls. If no call statistics are received for two minutes, the QoS information is reset. 7.7.
SIP User's Manual 7. IP Telephony Capabilities DisconnectOnBusyTone is set to 0, the FXO device ignores the detection of Busy/Reorder tones and doesn’t release the call. For all other FXS/FXO release types (caused when there are no free channels in the specific Trunk Group, or when an appropriate rule for routing the call to a Trunk Group doesn’t exist, or if the phone number isn’t found), the device sends a SIP response (to IP) according to the parameter DefaultReleaseCause. This parameter defines Q.
Mediant 1000 & Mediant 600 Field Name Description DstPhoneNum Destination Phone Number DstNumBeforeMap Destination Number Before Manipulation Durat Call Duration Coder Selected Coder Intrv Packet Interval RtpIp RTP IP Address Port Remote RTP Port TrmSd Initiator of Call Release (IP, Tel, Unknown) TrmReason Termination Reason Fax Fax Transaction during the Call InPackets Number of Incoming Packets OutPackets Number of Outgoing Packets PackLoss Local Packet Loss RemotePackLoss Num
SIP User's Manual 7.10 7. IP Telephony Capabilities Supported RADIUS Attributes Use the following table for explanations on the RADIUS attributes contained in the communication packets transmitted between the device and a RADIUS Server. Table 7-3: Supported RADIUS Attributes Attribute Number Attribute Name VSA No.
Mediant 1000 & Mediant 600 Attribute Number Attribute Name VSA No. Purpose Value Format Example AAA1 ID Destination phone number String 2427456425 Stop Acc CallingStation-ID Calling Party Number (ANI) String 5135672127 40 Acct-StatusType Account Request Type (start or stop) 1: start, 2: Note: ‘start’ isn’t supported Numeric stop on the Calling Card application. Start Acc Stop Acc 41 Acct-DelayTime No.
SIP User's Manual 7. IP Telephony Capabilities Below is an example of RADIUS Accounting, where the non-standard parameters are preceded with brackets. Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.
Mediant 1000 & Mediant 600 4. 5. At Device B, route IP-to-PSTN calls to Trunk Group ID according to the first digit of the called number: • PSTNPrefix = 1,1 • PSTNPrefix = 2,2 • PSTNPrefix = 3,4 • PSTNPrefix = 4,4 At Device B, remove the first digit from each IP-to-PSTN number before it is used in an outgoing call: NumberMapIP2Tel = *,1 7.12 Proxy or Registrar Registration Example Below is an example of Proxy and Registrar Registration: REGISTER sip:servername SIP/2.0 VIA: SIP/2.0/UDP 212.179.
SIP User's Manual 7. IP Telephony Capabilities REGISTER messages are sent to the Registrar's IP address (if configured) or to the Proxy's IP address. A single message is sent once per device, or messages are sent per B-channel according to the parameter AuthenticationMode. There is also an option to configure registration mode per Trunk Group using the TrunkGroupSettings table. The registration request is resent according to the parameter RegistrationTimeDivider.
Mediant 1000 & Mediant 600 F1 (10.8.201.108 >> 10.8.201.10 INVITE): INVITE sip:1000@10.8.201.10;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: ;tag=1c5354 To: Call-ID: 534366556655skKw-8000--1000@10.8.201.108 CSeq: 18153 INVITE Contact: User-Agent: Audiocodes-Sip-Gateway/Mediant 1000/v.5.40.010.
SIP User's Manual 7. IP Telephony Capabilities F4 (10.8.201.10 >> 10.8.201.108 200 OK): SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: ;tag=1c5354 To: ;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.108 CSeq: 18153 INVITE Contact: Server: Audiocodes-Sip-Gateway/Mediant 1000/v.5.40.010.
Mediant 1000 & Mediant 600 F7 (10.8.201.10 >> 10.8.201.108 200 OK): SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud From: ;tag=1c5354 To: ;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.108 Server: Audiocodes-Sip-Gateway/Mediant 1000/v.5.40.010.006 CSeq: 18154 BYE Supported: 100rel,em Content-Length: 0 7.13.
SIP User's Manual 4. 5. 6. 7. IP Telephony Capabilities Since the algorithm is MD5, then: • The username is equal to the endpoint phone number 122. • The realm return by the proxy is audiocodes.com. • The password from the ini file is AudioCodes. • The equation to be evaluated is (according to RFC this part is called A1) ‘122:audiocodes.com:AudioCodes’. • The MD5 algorithm is run on this equation and stored for future usage. • The result is ‘a8f17d4b41ab8dab6c95d3c14e34a9e1’.
Mediant 1000 & Mediant 600 7. Upon receiving this request and if accepted by the Proxy, the proxy returns a 200 OK response closing the REGISTER transaction: SIP/2.0 200 OK Via: SIP/2.0/UDP 10.1.1.200 From: ;tag=1c23940 To: Call-ID: 654982194@10.1.1.200 Cseq: 1 REGISTER Date: Thu, 26 Jul 2001 09:34:42 GMT Server: Columbia-SIP-Server/1.17 Content-Length: 0 Contact: ; expires="Thu, 26 Jul 2001 10:34:42 GMT"; action=proxy; q=1.
SIP User's Manual 3. 7. IP Telephony Capabilities Configure the following settings for both devices: In the ‘Tel to IP Routing’ page (refer to ''Tel to IP Routing Table'' on page 200), add the following routing rules: a. In the first row, enter 10 for the destination phone prefix and enter 10.2.37.10 for the destination IP address (i.e., IP address of the first device). b. In the second row, enter 20 for the destination phone prefix and 10.2.37.20 for the destination IP address (i.e.
Mediant 1000 & Mediant 600 Analog phones (POTS) PBX (one or more PBX loop start lines) LAN network Figure 7-8: FXO-FXS Remote PBX Extension (Example) 7.13.4.1 Dialing from Remote Extension (Phone at FXS) The procedure below describes how to dial from the 'remote PBX extension' (i.e., phone connected to the FXS interface). ¾ To make a call from the FXS interface, take these 3 steps: 1. Off-hook the phone and wait for the dial tone from the PBX.
SIP User's Manual 7. IP Telephony Capabilities 7.13.4.2 Dialing from PBX Line or PSTN The procedure below describes how to dial from a PBX line (i.e., from a telephone directly connected to the PBX) or from the PSTN to the 'remote PBX extension' (i.e., telephone connected to the FXS interface). ¾ To dial from a telephone directly connected to the PBX or from the PSTN, take this step: Dial the PBX subscriber number (e.g.
Mediant 1000 & Mediant 600 7.13.4.4 Call Waiting for Remote Extensions When the FXO device detects a Call Waiting indication (FSK data of the Caller Id CallerIDType2) from the PBX, it sends a proprietary INFO message, which includes the caller identification to the FXS device. Once the FXS device receives this INFO message, it plays a call waiting tone and sends the caller ID to the relevant port for display.
SIP User's Manual 3. 7. IP Telephony Capabilities In the ‘Tel to IP Routing’ page (refer to ''Tel to IP Routing Table'' on page 200), enter 20 for the destination phone prefix, and 10.1.10.2 for the IP address of the FXO device. Note: 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). 7.13.4.
Mediant 1000 & Mediant 600 4. In the ‘FXO Settings’ page (refer to ''Configuring the FXO Parameters'' on page 248), set the parameter ‘Dialing Mode’ to ‘Two Stages’ (IsTwoStageDial = 1). 7.13.5 SIP Trunking between Enterprise and ITSPs By implementing the device's enhanced and flexible routing configuration capabilities using Proxy Sets, IP Groups, and Accounts, you can "design" complex routing schemes.
SIP User's Manual 7. IP Telephony Capabilities ¾ To configure call routing between Enterprise and two ITSPs using the device, take these 8 steps: 1. Enable the device to register to a Proxy / Registrar server, using the parameter IsRegisterNeeded in the 'Proxy & Registration' page (refer to ''Proxy & Registration Parameters'' on page 146). 2.
Mediant 1000 & Mediant 600 4. In the 'Trunk Group Table' page (refer to "Configuring the Trunk Group Table" on page 226), enable the Trunks connected between the Enterprise's PBX and the device (Trunk Group ID #1), and between the local PSTN and the device (Trunk Group ID #2). Figure 7-19: Assign the Trunk to Trunk Group ID #1 in the Trunk Group Table Page 5.
SIP User's Manual 7.14 7. IP Telephony Capabilities Working with Supplementary Services The device supports the following supplementary services: Call Hold and Retrieve (refer to ''Call Hold and Retrieve'' on page 437). Consultation / Alternate (refer to "Consultation / Alternate" on page 438). Call Transfer (refer to ''Call Transfer'' on page 438).
Mediant 1000 & Mediant 600 The hold and retrieve functionalities are implemented by Re-INVITE messages. The IP address 0.0.0.0 as the connection IP address or the string ‘a=inactive’ in the received Re-INVITE SDP cause the device to enter Hold state and to play held tone (configured in the device) to the PBX/PSTN. If the string ‘a=sendonly’ is received in the SDP message, the device stops sending RTP packets, but continues to listen to the incoming RTP packets.
SIP User's Manual 7. IP Telephony Capabilities The transfer can be initiated at any of the following stages of the call between A and C: • Just after completing dialing C phone number - transfer from setup. • While hearing Ringback – transfer from alert. • While speaking to C - transfer from active. Blind Transfer (REFER): Blind transfer is performed after we have a call between A and B, and party A decides to immediately transfer the call to C without speaking with C.
Mediant 1000 & Mediant 600 7.14.5 Call Waiting The Call Waiting feature enables FXS devices to accept an additional (second) call on busy endpoints. If an incoming IP call is designated to a busy port, the called party hears call waiting tone (several configurable short beeps) and (for Bellcore and ETSI Caller IDs) can view the Caller ID string of the incoming call. The calling party hears a Call Waiting Ringback Tone.
SIP User's Manual 7.
Mediant 1000 & Mediant 600 The configuration for Caller ID is described below: Use the parameter CallerIDType to define the Caller ID standard. Note that the Caller ID standard that is used on the PBX or phone must match the standard defined in the device.
SIP User's Manual 7. IP Telephony Capabilities • EnableCallerID = 0 • RingsBeforeCallerID = 0 • Set the automatic dialing to hotline (e.g., TargetOfChannel7 = 9005,2) • HotLineToneDuration = 0 The above settings allow the FXO to send RTP without immediately seizing the line after receiving the first ring at your PC. 7. Capture the RTP using Wireshark (you can also use DSP trace) and send the file to AudioCodes. 7.14.7.
Mediant 1000 & Mediant 600 The value of the ‘Presentation’ field that is defined in the ‘Caller Display Information’ table can be overridden by configuring the ‘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. The caller ID can be restricted / allowed (per port) using keypad features KeyCLIR and KeyCLIRDeact (FXS only).
SIP User's Manual 8. Networking Capabilities 8 Networking Capabilities 8.
Mediant 1000 & Mediant 600 When the CPU module loses all Ethernet connectivity, a Critical alarm is generated: 8.3 When MIIRedundancyEnable is disabled: the alarm is generated when the single physical connection is lost. The alarm is cleared when the single physical connection is restored. When MIIRedundancyEnable is enabled: the alarm is generated when both physical connections are lost. The alarm is cleared when one or both of the physical connections are restored.
SIP User's Manual 8.3.1 8. Networking Capabilities STUN Simple Traversal of UDP through NATs (STUN), based on RFC 3489 is a client / server protocol that solves most of the NAT traversal problems. The STUN server operates in the public Internet and the STUN clients are embedded in end-devices (located behind NAT). STUN is used both for the signaling and the media streams. STUN works with many existing NAT types and does not require any special behavior.
Mediant 1000 & Mediant 600 8.3.2 First Incoming Packet Mechanism If the remote device resides behind a NAT device, it’s possible that the device can activate the RTP/RTCP/T.38 streams to an invalid IP address / UDP port. To avoid such cases, the device automatically compares the source address of the incoming RTP/RTCP/T.38 stream with the IP address and UDP port of the remote device.
SIP User's Manual 8.5 8. Networking Capabilities Robust Reception of RTP Streams This mechanism filters out unwanted RTP streams that are sent to the same port number on the device. These multiple RTP streams can result from traces of previous calls, call control errors, and deliberate attacks. When more than one RTP stream reaches the device on the same port number, the device accepts only one of the RTP streams and rejects the rest of the streams.
Mediant 1000 & Mediant 600 The client requests a time update from a specified NTP server at a specified update interval. In most situations, this update interval is every 24 hours based on when the system was restarted.
SIP User's Manual 8. Networking Capabilities Dual IP mode: The device is assigned two IP addresses for the different traffic types. One IP address is assigned to a combination of two traffic types (Media and Control, OAMP and Control, or OAMP and Media), while the other IP address is assigned to whichever traffic type not included in this combination. For example, a typical scenario using this mode includes one IP address assigned to Control and OAMP, and another IP address assigned to Media.
Mediant 1000 & Mediant 600 Media traffic type is assigned ‘Premium media’ CoS, Management traffic type is assigned ‘Bronze’ CoS, and Control traffic type is assigned ‘Premium control’ CoS. For example, RTP/RTCP traffic is assigned the Media VLAN ID and ‘Premium media’ CoS, whereas Web traffic is assigned the Management VLAN ID and ‘Bronze’ CoS. Each of these parameters can be configured with a 802.1p/Q value: traffic type to VLAN ID, and CoS to 802.1p priority.
SIP User's Manual Application 8. Networking Capabilities Traffic / Network Types Class-of-Service (Priority) Web server (HTTP) Management Bronze SNMP GET/SET Management Bronze Web server (HTTPS) Management Bronze IPSec IKE Determined by the service Determined by the service RTP traffic Media Premium media RTCP traffic Media Premium media T.
Mediant 1000 & Mediant 600 Table 8-2: Example of VLAN and Multiple IPs Configuration Network Type IP Address Subnet Mask Default Gateway IP Address VLAN ID External Routing Rule OAMP 10.31.174.50 255.255.0.0 0.0.0.0 4 83.4.87.X Control 10.32.174.50 255.255.0.0 0.0.0.0 5 130.33.4.6 Media 10.33.174.50 255.255.0.0 10.33.0.1 6 -- Notes: 8.9.3.1 • The values provided in this section are only used as an example.
SIP User's Manual 4. 8. Networking Capabilities Configure the multiple IP parameters by completing the following steps: a. In the ‘IP Settings’ page, modify the IP parameters to correspond to the values shown in the figure below. Note that the OAM, Control, and Media Network Settings parameters appear only after you select the options ‘Multiple IP Networks’ or 'Dual IP' in the field ‘IP Networking Mode’.
Mediant 1000 & Mediant 600 5. Configure the 'IP Routing' table to define static routing rules for the OAMP and Control networks, since a default gateway isn’t supported on these networks: a. Open the ‘IP Routing Table’ page (refer to ''Configuring the IP Routing Table'' on page 75). Figure 8-5: Static Routes for OAM/Control in IP Routing Table b.
SIP User's Manual 8. Networking Capabilities Below is an example of an ini file containing VLAN and Multiple IPs parameters: ; Interface Table Configuration: [InterfaceTable] FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_IPv6InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_Gateway, InterfaceTable_VlanID, InterfaceTable_InterfaceName; InterfaceTable 0 = 0, 0, 10.31.174.50, 16, 0.0.0.0, 4, OAMP; InterfaceTable 0 = 1, 0, 10.33.174.
Mediant 1000 & Mediant 600 Instead of using the ini file table parameter InterfaceTable, you can configure multiple IPs and VLANs using the individual ini file parameters, as shown below: ; VLAN Configuration VlanMode=1 VlanOamVlanId=4 VlanNativeVlanId=4 VlanControlVlanId=5 VlanMediaVlanID=6 ; Multiple IPs Configuration EnableMultipleIPs=1 LocalMediaIPAddress=10.33.174.50 LocalMediaSubnetMask=255.255.0.0 LocalMediaDefaultGW=10.33.0.1 LocalControlIPAddress=10.32.174.50 LocalControlSubnetMask=255.255.0.
SIP User's Manual 9. Advanced PSTN Configuration 9 Advanced PSTN Configuration 9.1 Clock Settings The device's clock settings can be configured to either generate its own timing signals, use an internal clock, or recover them from one of the E1/T1 trunks.
Mediant 1000 & Mediant 600 It is also possible to map the less commonly used SIP Responses to a single default ISDN Release Cause. Use the parameter DefaultCauseMapISDN2IP (described in ''ISDN and CAS Interworking-Related Parameters'' on page 348) to define a default ISDN Cause that is always used except when the following Release Causes are received: Normal Call Clearing (16), User Busy (17), No User Responding (18) or No Answer from User (19). This mechanism is only available for Tel-to-IP calls. 9.2.
SIP User's Manual ISDN Release Reason 9.
Mediant 1000 & Mediant 600 ISDN Release Reason SIP Response Description Description 95 Invalid message 503 Service unavailable 96 Mandatory information element is missing 409* Conflict 97 Message type non-existent or not implemented 480* Temporarily not available 98 Message not compatible with call state or message type non-existent or not implemented 409* Conflict 99 Information element non-existent or not implemented 480* Not found 100 Invalid information elements contents 501*
SIP User's Manual SIP Response 9.
Mediant 1000 & Mediant 600 The device stops collecting digits (for ISDN-to-IP calls) when: The sending device transmits a ‘sending complete’ IE in the ISDN Setup or the following INFO messages to signal that no more digits are going to be sent. The inter-digit timeout (configured by the parameter TimeBetweenDigits) expires. The default for this timeout is 4 seconds. The maximum allowed number of digits (configured by the parameter MaxDigits) is reached. The default is 30 digits.
SIP User's Manual 9.
Mediant 1000 & Mediant 600 9.4.
SIP User's Manual 9. Advanced PSTN Configuration ¾ To stop / delete an NFAS Group, take these 3 steps: 1. Stop / delete all NFAS (‘slave’) trunks. 2. Stop / delete the backup trunk if a backup trunk exists. 3. Stop / delete the primary trunk. Notes: Version 5.4 • All trunks in the group must be configured with the same values for trunk parameters TerminationSide, ProtocolType, FramingMethod, and LineCode. • After stopping or deleting the backup trunk, delete the group and then reconfigure it.
Mediant 1000 & Mediant 600 9.
SIP User's Manual 10 10. Media Server Capabilities Media Server Capabilities This section provides information on the device's media server capabilities: Multi-party conferencing (refer to ''Conference Server'' on page 469) Playing and recording Announcements (refer to ''Announcement Server'' on page 483) IP-to-IP Transcoding (refer to ''IP-to-IP Transcoding'' on page 494) Note: This section is applicable only to Mediant 1000.
Mediant 1000 & Mediant 600 10.1.1 Simple Conferencing (NetAnn) 10.1.1.1 SIP Call Flow Figure 10-1: Simple Conferencing SIP Call Flow 10.1.1.2 Creating a Conference The device creates a conference call when the first user joins the conference. To create a conference, the Application Server sends a regular SIP INVITE message to the device.
SIP User's Manual 10. Media Server Capabilities INVITE sip: conf100@audiocodes.com SIP/2.0 By default, a request to create a conference reserves three resources on the device. It is possible to reserve a larger number of resources in advance by adding the number of required participants to the User Part of the Request-URI. For example, '6conf100' reserves six resources for the duration of the conference. If the device can allocate the requested number of resources, it responds with a 200 OK.
Mediant 1000 & Mediant 600 10.1.1.5 PSTN Participants Adding PSTN participants is done by performing a loopback from the IP side (the device's IP address is configured in the 'Tel to IP Routing' table). If the destination phone number in the incoming call from the PSTN is equal to the Conference Service Identifier and Unique Conference Identifier, the participant joins the conference. A PSTN participant uses two DSP channels (caused by the IP loopback). 10.1.2 Advanced Conferencing (MSCML) 10.1.2.
SIP User's Manual 10. Media Server Capabilities Figure 10-2: Advanced Conferencing SIP Call Flow 10.1.2.2 Joining a Conference To join an existing conference, the Application Server sends a SIP INVITE message with the same Request-URI as the one that created the conference. The INVITE message may include a MSCML request body. If not included, defaults are used for that leg attributes.
Mediant 1000 & Mediant 600 10.1.2.3 Modifying a Conference To modify an existing conference, INFO messages are used. Each INFO message carries an MSCML request. The MSCML response is included in an INFO message back from the device to the Application Server. It is possible to modify an entire conference (by issuing requests on the Control Leg) or only a certain participant (by issuing requests on that specific leg).
SIP User's Manual 10. Media Server Capabilities Figure 10-4: Applying Media Services on a Conference -- SIP Call Flow 10.1.2.5 Active Speaker Notification After an advanced conference is established, the Application Server can subscribe to the device to receive notifications of the current set of active speakers in a conference at any given moment. This feature is referred to as Active Speaker Notification (ASN) and is designed according to the MSCML standard.
Mediant 1000 & Mediant 600 10.1.2.6 Terminating a Conference To remove a leg from a conference, the Application Server issues a SIP BYE request on the selected dialog representing the conference leg. The Application Server can terminate all legs in a conference by issuing a SIP BYE request on the Control Leg.
SIP User's Manual 10. Media Server Capabilities 10.1.3 Conference Call Flow Example The call flow, shown in the following figure, describes SIP messages exchanged between the device (10.8.58.4) and three conference participants (10.8.29.1, 10.8.58.6 and 10.8.58.8). Figure 10-6: Conference Call Flow Example Version 5.
Mediant 1000 & Mediant 600 1. SIP MESSAGE 1: 10.8.29.1:5060 -> 10.8.58.4:5060 INVITE sip:conf100@10.8.58.4;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.29.1;branch=z9hG4bKacRHmJhMj Max-Forwards: 70 From: ;tag=1c352329022 To: Call-ID: 1792526528qlax@10.8.29.1 CSeq: 1 INVITE Contact:
SIP User's Manual 10. Media Server Capabilities 4. SIP MESSAGE 4: 10.8.29.1:5060 -> 10.8.58.4:5060 ACK sip:10.8.58.4 SIP/2.0 Via: SIP/2.0/UDP 10.8.29.1;branch=z9hG4bKacbUrWtRo Max-Forwards: 70 From: ;tag=1c352329022 To: ;tag=1c222574568 Call-ID: 1792526528qlax@10.8.29.1 CSeq: 1 ACK Contact:
Mediant 1000 & Mediant 600 7. SIP MESSAGE 7: 10.8.58.4:5060 -> 10.8.58.6:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.58.6;branch=z9hG4bKacfowEuut From: ;tag=1c201038291 To: ;tag=1c1673415884 Call-ID: 1008914574iYgW@10.8.58.6 CSeq: 1 INVITE Contact: Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE Server: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.
SIP User's Manual 10. Media Server Capabilities 10. SIP MESSAGE 10: 10.8.58.4:5060 -> 10.8.58.8:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.8.58.8;branch=z9hG4bKaczJpxnnv From: ;tag=1c2419012378 To: ;tag=1c3203015250 Call-ID: 150852731NDDC@10.8.58.8 CSeq: 1 INVITE Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE Server: Audiocodes-Sip-Gateway-Mediant 1000/v.5.40.010.
Mediant 1000 & Mediant 600 13. SIP MESSAGE 13: 10.8.58.8:5060 -> 10.8.58.4:5060 BYE sip:conf100@10.8.58.4 SIP/2.0 Via: SIP/2.0/UDP 10.8.58.8;branch=z9hG4bKackSIyGww Max-Forwards: 70 From: ;tag=1c2419012378 To: ;tag=1c3203015250 Call-ID: 150852731NDDC@10.8.58.8 CSeq: 2 BYE Contact:
SIP User's Manual 10.2 10. Media Server Capabilities Announcement Server The device supports playing and recording of announcements (local Voice Prompts or HTTP streaming) and playing of Call Progress Tones over the IP network.
Mediant 1000 & Mediant 600 Notes: • A 200 OK message is sent only after the HTTP connection is successfully established and the requested file is found. If the file isn’t found, a 404 Not Found response is sent. • To use NFS, the requested file system should be first mounted by using the NFS Servers table, see ''Configuring the NFS Settings'' on page 74. 10.2.1.
SIP User's Manual 10. Media Server Capabilities The following figure illustrates standard MSCML application architecture: Figure 10-7: MSCML Architecture The architecture comprises the following components: device: Operating independently, the device controls and allocates its processing resources to match each application’s requirements. Its primary role is to handle requests from the Application server for playing announcements and collecting digits.
Mediant 1000 & Mediant 600 An alternative method uses the AutoUpdate mechanism as described in Automatic Update Mechanism. Both the vp.dat and segments.xml file that were previously created using the APS should be located on an external storage server (HTTP, FTP). At startup, the device fetches the files from the remote storage. By using the AutoUpdate mechanism, the device periodically checks if new files are posted to the remote server and fetches these files.
SIP User's Manual 10. Media Server Capabilities The , , and messages are composed of two sections: Attributes and a Prompt block (the request can contain several different Prompt blocks). The Attributes section includes several request-specific parameters. The Prompt block section itself is also composed of two sections: prompt-specific parameters and audio segments (audio / variable).
Mediant 1000 & Mediant 600 10.2.2.2 Playing Announcements A request is used to play an announcement to the caller. Each request contains a single Prompt block and the following request-specific parameters: id: an optional random number used to synchronize request and response. prompturl: a specific audio file URL that is used in addition to the references in the Prompt block. This audio file is the first to be played.
SIP User's Manual 10. Media Server Capabilities extradigittimer: used to enable the following: • Detection of command keys (ReturnKey and EscapeKey). • Not report the shortest match. MGCP Digitmap searches for the shortest possible match. This means that if a digitmap of (123 | 1234) is defined, once the user enters 123, a match is found and a response is sent. If ExtraDigitTimer is defined, the match can also be 1234 because the device waits for the next digits.
Mediant 1000 & Mediant 600 10.2.2.4 Playing Announcements and Recording Voice The request is used to play an announcement to the caller and to then record the voice stream associated with that caller. The play part of the request is identical to the request. The record part includes a URL to which the voice stream is recorded. This URL refers to an HTTP server.
SIP User's Manual 10. Media Server Capabilities An example is shown below of an MSCML Response: 10.2.2.5 Stopping the Playing of an Announcement The Application server issues a request when it requires that the device stops a request in progress and not initiate another operation.
Mediant 1000 & Mediant 600 10.2.3 Announcement Call Flow Example The call flow, shown in the following figure, describes SIP messages exchanged between the device (10.33.24.1) and a SIP client (10.33.2.40) requesting to play local announcement #1 (10.8.25.17) using AudioCodes proprietary method. 1. SIP MESSAGE 1: 10.33.2.40:5060 -> 10.33.24.1:5060 INVITE sip:annc@10.33.24.1;play=http://10.3.0.2/hello.wav;repeat=2 SIP/2.0 Via: SIP/2.0/UDP 10.33.2.
SIP User's Manual 2. 10. Media Server Capabilities SIP MESSAGE 2: 10.33.24.1:5060 -> 10.33.2.40:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.33.2.40;branch=z9hG4bKactXhKPQT From: ;tag=1c2917829348 To: ;tag=1c1528117157 Call-ID: 1414622340oZZq@10.33.2.40 CSeq: 1 INVITE Supported: em,timer,replaces,path Allow:REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,IN FO,SUBSCRIBE,UPDATE Server: Audiocodes-Sip-Gateway-TrunkPack 1610/v.4.60AOH.006.
Mediant 1000 & Mediant 600 5. SIP MESSAGE 5: 10.33.24.1:5060 -> 10.33.2.40:5060 BYE sip:103@10.33.2.40 SIP/2.0 Via: SIP/2.0/UDP 10.33.24.1;branch=z9hG4bKacFhtFbFR Max-Forwards: 70 From: ;tag=1c1528117157 To: ;tag=1c2917829348 Call-ID: 1414622340oZZq@10.33.2.40 CSeq: 1 BYE Contact:
SIP User's Manual 10. Media Server Capabilities The device uses two media (DSP) channels for each call, thereby reducing the number of available Transcoding sessions to half of the defined value for MediaChannels. To limit the number of resources available for Transcoding, use the ini file parameter MediaChannels or Web interface (refer to ''Configuring the IPmedia Parameters'' on page 242). For example, if MediaChannels is 40, only 20 Transcoding sessions are available.
Mediant 1000 & Mediant 600 The figure below illustrates an example of implementing an Application server: Figure 10-9: Using an Application Server SIP User's Manual 496 Document #: LTRT-83303
SIP User's Manual 11 11. Tunneling Applications Tunneling Applications This section discusses TDM and QISG tunneling, supported by the device. 11.1 TDM Tunneling The device's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network.
Mediant 1000 & Mediant 600 For tunneling of E1/T1 CAS trunks, set the protocol type to 'Raw CAS' (ProtocolType = 3 / 9) and enable RFC 2833 CAS relay mode ('CAS Transport Type' parameter is set to 'CAS RFC2833 Relay' -- refer to ''Configuring the Voice Settings'' on page 81). Note: For TDM over IP, the 'Caller ID Transport Type' parameter must be set to 'Disable', i.e., transparent (refer to ''Configuring the Fax / Modem / CID Settings'' on page 84).
SIP User's Manual 11.
Mediant 1000 & Mediant 600 11.2 QSIG Tunneling The device supports QSIG tunneling over SIP according to IETF draft 'Tunnelling of QSIG over SIP' (draft-elwell-sipping-qsig-tunnel-03) and the ECMA-355/ISO/IEC 22535 standard. This method enables all QSIG messages to be sent as raw data in corresponding SIP messages using a dedicated message body. This mechanism is useful for two QSIG subscribers (connected to the same or different QSIG PBX) to communicate with each other over an IP network.
SIP User's Manual 12 12. OSN Server Hardware Installation OSN Server Hardware Installation This section is intended for customers who have purchased the Mediant 1000 media gateway and wish to install the optional Mediant 1000 OSN (Open Solution Network) server functionality. The Mediant 1000 chassis can house a plug-in OSN Server module for hosting third-party, VoIP applications such as IP-PBX, Pre-Paid, and IP-PBX redundancy.
Mediant 1000 & Mediant 600 Hard Drive module (HDMX) Figure 12-3: Hard Drive Module (HDMX) Warning: Before installing the Mediant 1000 OSN Server modules, ensure that the Mediant 1000 is disconnected from the power supply. These modules are not hot-swappable and damage to these modules can occur if replaced under voltage. 12.2 Required Working Tools The following tools are required for installing the OSN Server module: 12.
SIP User's Manual 12. OSN Server Hardware Installation ¾ To install the CM module, take these 4 steps: 1. On the Mediant 1000 front panel, use a Phillips screwdriver to remove the black metal cover plate from the slot located below the module labeled CPU, as shown in the figure below: Figure 12-4: Mediant 1000 Front Panel 2. Insert the CM module into the empty slot (below the CPU), with the plain side of the Printed Circuit Board (PCB) facing up.
Mediant 1000 & Mediant 600 12.4 Installing the iPMX Module The iPMX module is installed on the rear panel of the Mediant 1000, as described in the following procedure: ¾ To install the iPMX module, take these 7 steps: 1. Place the Mediant 1000 so that the rear panel is facing you, as shown in the figure below. Figure 12-6: Mediant 1000 Rear Panel 2. Remove the black metal cover plates in the first and second slots located on the right side of the power connection, as shown in the figure below.
SIP User's Manual 3. 12. OSN Server Hardware Installation Use the cutter tool to remove the small metal strip between the upper and lower slots, as shown in the figure below. Figure 12-8: Mediant 1000 with Cutter Tool 4. Insert the iPMX module into the first slot, closest to the power connection, as shown in the figure below. Figure 12-9: Inserting iPMX Module 5. Push the iPMX module into the slot and press on it firmly to ensure it has been fully inserted. 6.
Mediant 1000 & Mediant 600 12.5 Installing the HDMX Module The Hard Drive module (HDMX) is installed on the rear panel of the Mediant 1000, as described in the following procedure: ¾ To install the HDMX module, take these 6 steps: 1. Place the Mediant 1000 so that the rear panel is facing you. 2. Remove the black metal cover plates in the first and second slots located on the right side of the power connection. 3. Use the cutter tool to remove the small metal strip between the upper and lower slots.
SIP User's Manual 12.6 12. OSN Server Hardware Installation Replacing the iPMX Module's Lithium Battery The iPMX module is equipped with a 3-volt CR-1225 Lithium battery (AudioCodes product number: ACL P/N RBAT00001). Typically, battery life is estimated at two years. However, for various reasons, the battery may last for a shorter duration. Warnings: • When replacing the battery, all BIOS settings revert to factory defaults.
Mediant 1000 & Mediant 600 4. Using a tweezer-like tool (or small flathead screwdriver), carefully leverage the battery out of the battery holder. Be careful not to touch other components on the board with your tool. Figure 12-11: Removing Lithium Battery from iPMX Module 5. For installing the new battery, simply push the battery into the battery holder using your fingers. Ensure that you install the battery in the correct orientation such that the positive side is facing up (i.e.
SIP User's Manual 13 13. Installing Windows XP on the OSN Server Installing Windows XP on the OSN Server The embedded PC on Mediant 1000 (OSN module) can be ordered with Windows XP preinstalled. However, if requested, the OSN server can be supplied without an installed Windows operating system. This section provides step-by-step procedures on installing Microsoft Windows XP on the OSN hard drive. (Although not tested, these procedures should be applicable to Windows 2003.
Mediant 1000 & Mediant 600 These modifications can be performed by a commandfile run at the end of the installation. Use Notepad or a similar text editor to create the following two files and save them in a separate folder named "M1K" on your PC (for later use by the Windows Unattended CD Creator): File name: do.cmd copy d:\m1k\nofw.
SIP User's Manual 3. 13. Installing Windows XP on the OSN Server Define the target directory for the new Windows CD. Figure 13-2: Selecting Target Directory for Windows XP 4. Wait for the copy process to complete. 5. Use Windows Explorer to copy the "M1K" folder to the target directory. This is required to allow the .cmd scripts to operate correctly. (Note: you can also copy your own programs and files into this "M1K" folder.
Mediant 1000 & Mediant 600 7. Create a default user with a password, and assign it to the Administrators group. Figure 13-4: Creating a User 8. Add the drivers for LAN and AUDIO.
SIP User's Manual 9. 13. Installing Windows XP on the OSN Server Add the directory with the cmd files to the CD. Ensure to select the 'Directories' check box (the description is arbitrary). Figure 13-6: Adding cmd Files Directory to CD 10. Click the newly created name, and then click Select to browse to the do.cmd file. Figure 13-7: Selecting do.cmd File Version 5.
Mediant 1000 & Mediant 600 11. Click Add to include this command file to the installation script. The result appears as follows: Figure 13-8: Adding cmd File to Installation Script 12. Select the Done tab, and then click Save. 13. Click create ISO-image. Figure 13-9: Completing ISO Image Creation Your ISO image is now ready. 13.2.3 Stage 3: Burning the CD Use a CD burning program to make a CD from the ISO image. Burn with verification to ensure the CD is correctly burned.
SIP User's Manual 13. Installing Windows XP on the OSN Server 13.2.4 Stage 4: Cabling the Mediant 1000 OSN Server The procedure below describes the cabling for installing Windows. ¾ To cable the OSN server, take these 3 steps: 1. Connect the CM module's (located on the Mediant 1000 front panel) RS-232 port to a PC (DB-9 connector), using the RS-232 serial cable. 2. Connect the CM module's USB port to a USB hub, using the USB cable. 3. Connect an external CD-ROM drive and a keyboard to the USB hub.
Mediant 1000 & Mediant 600 3. 4. Alternative 1: The CD immediately boots. This indicates that the hard disk is unformatted and unpartitioned. a. Allow CD activity and intermediate pauses to run for about 10 minutes. b. Once CD activity has stopped, perform the following, using the USB keyboard: a. Press the key. b. To quicken installation, press the arrow key twice. This changes NTFS full format to NTFS quick format, eliminating time required for hard disk formatting. c.
SIP User's Manual 13. Installing Windows XP on the OSN Server 13.2.6 Stage 6: Enabling the Firewall with Remote Desktop Access The OSN server's firewall was initially disabled to allow Windows XP installation and Remote Desktop access (in Stage 1: Creating the Helper Script). However, once you access the OSN Server after Windows installation has complete, you need to enable the Windows XP firewall and allow future Remote Desktop access.
Mediant 1000 & Mediant 600 2. Click Windows Firewall, and then add 'Remote Desktop' to the selected firewall exceptions. Figure 13-12: Remote Desktop Firewall 3. Select the Advanced tab, click Settings for the 'Local Area Connection', and then also allow Internet access to Remote Desktop. Figure 13-13: Allowing Internet Users Access to Remote Desktop 4. Delete the 'nofw.cmd' item from Windows Startup menu.
SIP User's Manual 13.3 13. Installing Windows XP on the OSN Server Connecting Remotely to OSN Server using Windows XP Typically, for customers requiring Microsoft Windows® XP operating system (OS), the OSN Server is provided with Windows XP already pre-installed. Once the OSN Server modules have been installed in the Mediant 1000 chassis, you can connect to the OSN Server using Microsoft's Remote Desktop Connection program. Notes: • This section is applicable only to Mediant 1000.
Mediant 1000 & Mediant 600 13.3.2 Connecting Using Remote Desktop Connection Once you have cabled the PC to the OSN Server's iPMX module, perform the procedure below for connecting the PC remotely to the OSN Server (running Windows XP) using the Remote Desktop Connection program. ¾ To remotely connect a PC to the OSN Server running Windows XP, take these 6 steps: 1. Change the PC's IP address so that it is in the same subnet as the default OSN Server's IP address (i.e., 10.1.10.12).
SIP User's Manual 2. 13. Installing Windows XP on the OSN Server Start Microsoft's Remote Desktop Connection program - from the Start menu, point to Programs, to Accessories, to Communications, and then click Remote Desktop Connection. Figure 13-16: Entering IP Address in Remote Desktop Connection 3. In the 'Computer' field, enter the OSN Server's default IP address (i.e., 10.1.10.12). 4. Click Connect. Figure 13-17: Entering User Name and Password in Remote Desktop Connection 5.
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 522 Document #: LTRT-83303
SIP User's Manual 14 14. Installing Linux™ Operating System on the OSN Server Installing Linux™ Operating System on the OSN Server Once the OSN Server modules have been installed in the Mediant 1000 Media Gateway, you need to install an operating system (OS) on the OSN server on which the partner application (e.g. IP-PBX) is to run.
Mediant 1000 & Mediant 600 USB cable (not supplied) to connect the external USB CD ROM to the Mediant 1000 RS-232 cable (supplied) LinuxTM Distributions Installation CDs Blank CD or DVD media WindowsTM PC with CD RW or external CD ROM/RW 14.1.2 Software The software requirements include the following: 14.2 RS-232 console / terminal software (e.g., HyperTerminalTM) ISO Image Editor (WinISOTM is recommended -- refer to http://www.winiso.com/download.
SIP User's Manual 14.3 14. Installing Linux™ Operating System on the OSN Server 3. Connect the external CD-ROM to the power supply. 4. Connect the Mediant 1000 to the power supply. Installing Linux™ RedHat (and Fedora) Perform the following four stages for installing LinuxTM Redhat (and Fedora). (Some distributions of LinuxTM may vary slightly): Notes: • Some distributions of Linux may vary slightly. • The Linux version for installation must be according to the application requirements (e.g.
Mediant 1000 & Mediant 600 14.3.1.2 Creating an Updated ISO Image ¾ To create an updated Linux Redhat ISO Image take these 6 steps 1. On the local hard disk of the Window’s™ PC, create a new folder called 'Partner Install'. 2. If you have not already done so, download a utility that allows editing of an ISO image (e.g., WinISO™ from http://www.winiso.com/download.htm 3. Using Internet Explorer, download a UNIX File Format text editor (e.g., PSPad™ at http://www.pspad.comr UltraEdit™ at http://www.
SIP User's Manual 5. 14. Installing Linux™ Operating System on the OSN Server Locate the boot.iso file in the images folder on the CD (refer to the note below). Figure 14-3: Images Folder 6. Copy the boot.iso file to the 'Partner Install' folder created in Step 1, and then open it with an ISO image editor. The isolinux.cfg file should appear as shown in the screen below. Figure 14-4: ISO Screen Note: The 'images' folder may be named differently on different Linux™ distributions. Version 5.
Mediant 1000 & Mediant 600 14.3.2 Stage 2: Editing the isolinux.cfg File ¾ To edit the isolinux.cfg file, take these 14 steps: 1. Extract the isolinux.cfg file by performing the following: a. Right-click the isolinux.cfg file, and then from the shortcut menu, choose Extract. Figure 14-5: Selecting Extract Option b. In the 'Extract to' field, browse to the 'Partner Install' folder (created in Stage 1) to where the isolinux.cfg file must be extracted.
SIP User's Manual c. 14. Installing Linux™ Operating System on the OSN Server Click Extract; the files is extracted and a screen opens containing the extracted isolinux file. Figure 14-7: ISO-Extract Screen 2. Open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad or UltraEdit); the following screen appears. Figure 14-8: Text Edit Screen 3. Version 5.
Mediant 1000 & Mediant 600 4. Locate the line 'default ' (usually 'default linux' appears), and then locate the line 'label ' (usually 'label linux' appears). Under this line, the following appears: kernel ... append ... 5. Add the following parameters to the 'append' line of : text console=ttyS0,115200 Note: In the above string, “ttyS0,115200” consists of a capital “S”, only zeros, and one comma.
SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 11. Right-click the isolinux.cfg file, and then from the shortcut menu, choose Delete to delete this file. Figure 14-9: Deleting CFG 12. From the ISO edit utility menu, select the Actions option, followed by Add Files. Figure 14-10: File Add Version 5.
Mediant 1000 & Mediant 600 13. Navigate to the 'Partner Install' folder, select the isolinux.cfg file, and then click Open. Figure 14-11: ISO Open Function The updated isolinux.cfg file has now been copied from the 'Partner Install' folder to the boot.iso image. 14. Save the boot.iso image in the 'Partner Install' folder. 14.3.3 Stage 3: Burning ISO Image File to CD-ROM ¾ To burn the boot.iso file to a CD-ROM, take these 3 steps: 1. Open a burning utility. 2. Use the Burn Image option to burn the boot.
SIP User's Manual 4. 14. Installing Linux™ Operating System on the OSN Server Open the Terminal application (e.g. HyperTerminal) on your Windows™ PC. Create a new connection with the following settings: • Connect Port: COM1 • Baudrate: 115200 (bits per second) • Data Bits: 8 • Parity: None • Stop Bits: 1 • Flow Control: None 5. Insert the “Boot CD” (created in Stage 3) into the USB CD-ROM drive. 6. Power up the Mediant 1000. 7.
Mediant 1000 & Mediant 600 14.3.5 Additional RedHat™ and Fedora™ Installation Notes Please refer to the following notes for the remaining part of the installation. 1. Select LILO as your bootloader where possible, otherwise select GRUB. 2. It is recommended that you disable the firewall when prompted (select “No Firewall”). 3.
SIP User's Manual 14.4 14. Installing Linux™ Operating System on the OSN Server Installing Linux™ Debian Perform the following five stages for installing Linux™ Debian. Note: Some distributions of Linux may vary slightly. 14.4.1 Stage 1: Obtaining the ISO Image To obtain an updated ISO image, create it using the steps detailed in the section below. ¾ To create an ISO image using an ISO editor utility, take these 4 steps: 1.
Mediant 1000 & Mediant 600 4. Create a 'Partner Install' folder on your hard drive. Select boot.iso as the output filename, and then click Make. Figure 14-14: Create ISO from CD-ROM The .iso file starts being created. Figure 14-15: Creating .iso File 14.4.2 Stage 2: Preparing the Boot Media ¾ To prepare the Boot Media, take these 5 steps: 1. If you have not already done so, download a utility that allows editing of an ISO image (e.g., WinISO™ at http://www.winiso.com/download.htm 2.
SIP User's Manual 3. 14. Installing Linux™ Operating System on the OSN Server Locate the boot.iso file in the 'Partner Install' folder on the hard disk of your PC and with the ISO image utility, navigate to the \isolinux\isolinux.cfg file. Figure 14-16: Partner Install Folder 4. Extract the isolinux.cfg file by right-clicking the file name, and then from the shortcut menu, choosing Extract. Figure 14-17: Extract isolinux.cfg 5. Extract the isolinux.cfg file to the 'Partner Install' folder.
Mediant 1000 & Mediant 600 14.4.3 Stage 3: Editing the isolinux.cfg File To obtain an updated isolinux.cfg file, perform one of the following: Download it from the AudioCodes Web site as described in ''Downloading an updated Debian isolinux.cfg file'' on page 538 Edit it using the steps detailed in ''Editing the isolinux.cfg File'' on page 538 14.4.3.1 Downloading an Updated Debian isolinux.cfg File ¾ To download an updated Debian isolinux.cfg file from AudioCodes Web site, take these 6 steps: 1.
SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 4. Locate the line 'prompt ' (usually appears as 'prompt 1') and change it to 'prompt 0'. 5. Locate the line 'timeout ' (usually appears as 'timeout 600') and change it to 'timeout 0'. Note: If the timeout line does not exist, do not add it. The isolinux.cfg file should now look like the following: serial 0 115200 DEFAULT /install/vmlinuz APPEND vga=normal initrd=/install/initrd.
Mediant 1000 & Mediant 600 9. Right-click the isolinux.cfg file, and then from the shortcut menu, choose Delete to delete this file. Figure 14-19: Deleting CFG 10. From the ISO edit utility menu, select the Actions option, followed by Add Files.
SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 11. Navigate to the 'Partner Install' folder, select the isolinux.cfg file, and then click Open. Figure 14-21: ISO Open Function The updated isolinux.cfg file is copied to the 'Partner Install\isolinux' directory. 12. Save the boot.iso file in the 'Partner Install' folder. 14.4.4 Stage 4: Burning ISO Image to CD ¾ To burn the boot.iso file to CD, take these 3 steps: 1. Open a burning utility. 2.
Mediant 1000 & Mediant 600 • Stop Bits: 1 • Flow Control: None 5. Insert the “Boot CD” (created in Stage 3) into the USB CD-ROM drive. 6. Power up the Mediant 1000. 7. On the Terminal application, the BIOS phase starts and the Linux installation begins. The installation uncompresses the kernel, loads it and its drivers, and then starts the interactive installation. Notes: • After the BIOS phase, some badly formatted text may appear on the screen.
SIP User's Manual 7. 14. Installing Linux™ Operating System on the OSN Server In the 'LILO Installation target', select /dev/hda: Master Boot Record. Note: The bootloader should detect the serial console. If it doesn’t then either: a) pass additional parameters to the kernel (configure that using the main installation menu) or/and b) when configuring LILO you should specify that it tells the kernel to use serial console at speed 115200.
Mediant 1000 & Mediant 600 14.5 Installing Linux™ SUSE Perform the following five stages for the LinuxTM SUSE Installation. Note: Some distributions of Linux may vary slightly. 14.5.1 Additional Requirement for Linux™ SUSE Installation To install Linux™ SUSE, a terminal emulation program is required that supports the following: ANSI colors (or Linux™ emulation) Changing terminal size (to 132x47) The Tera Term™ program may http://hp.vector.co.jp/authors/VA002416/teraterm.
SIP User's Manual 4. 14. Installing Linux™ Operating System on the OSN Server Create a 'Partner Install' folder on your hard drive. Select boot.iso as the output filename, and then click Make. Figure 14-23: Create ISO from CD-ROM The utility begins creating the boot.iso file. Figure 14-24: Creating .iso File 14.5.3 Stage 2: Preparing the Boot Media ¾ To prepare the Boot Media, take these 5 steps: 1. If you have not already done so, download a utility that allows editing of an ISO image (e.g.
Mediant 1000 & Mediant 600 3. Locate the boot.iso file in the 'Partner Install' folder on the hard disk of your PC and navigate to the isolinux.cfg file. Figure 14-25: Partner Install Folder 4. Extract the isolinux.cfg file by right-clicking the filename, and then from the shortcut menu, choosing Extract. Figure 14-26: Extract isolinux.cfg File 5. Extract the isolinux.cfg file to the 'Partner Install' folder.
SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 14.5.4 Stage 3: Editing the isolinux.cfg File To obtain an updated isolinux.cfg file, perform on of the following: Download it from the AudioCodes Web site as described in ''Downloading an updated SUSE isolinux.cfg file'' on page 547 Edit it using the steps detailed in ''Editing the isolinux.cfg File'' on page 548 14.5.4.1 Downloading an Updated SUSE isolinux.cfg File ¾ To download an updated SUSE isolinux.
Mediant 1000 & Mediant 600 14.5.4.2 Editing the isolinux.cfg File ¾ To edit the isolinux.cfg file, take these 19 steps: 1. From the 'Partner Install' folder, open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad or UltraEdit). Figure 14-28: isolinux.cfg File 2. Insert the following line at the beginning of the file, so that it is the first line. serial 0 115200 3. Locate the line 'DEFAULT ' (usually the first line of the file, e.g.
SIP User's Manual 8. 14. Installing Linux™ Operating System on the OSN Server Add the following parameters to the 'append' line: text console=ttyS0,115200. Note: In the above string, “ttyS0,115200” consists of a capital “S”, only zeros, and one comma.
Mediant 1000 & Mediant 600 implicit gfxboot display prompt timeout readinfo framebuffer notice 1 bootlogo message 0 0 2 1 2 11. Save the changes to the isolinux.cfg file, and then close the text editor. 12. Open the 'Partner Install' folder and with the ISO edit utility, open the boot.iso file. 13. Navigate to the isolinux.cfg file, right-click it, and then from the shortcut menu, choose Delete to delete this file. Figure 14-29: Deleting CFG File 14. From the ISO edit Actions menu, select Add Files.
SIP User's Manual 14. Installing Linux™ Operating System on the OSN Server 15. Navigate to the 'Partner Install' folder, select the isolinux.cfg file, and then click Open. Figure 14-31: Partner Install Folder The updated isolinux.cfg file is added to the 'Partner Install' folder. 16. Save the boot.iso in the 'Partner Install' folder. Figure 14-32: Save boot.iso 14.5.5 Stage 4: Burning the CD ¾ To burn the CD image, take these 3 steps: 1. Open a burning utility. 2.
Mediant 1000 & Mediant 600 14.5.6 Stage 5: Installing the Boot Media Now you have the boot media which enables SUSE installation of the Mediant 1000 using serial connection (terminal) with RS232 cable. ¾ To complete the installation, take these 8 steps: 1. Connect your Windows™ PC to the Mediant 1000 using a serial cable. 2. Open the Terminal application on your Windows™ PC. (Refer to the Additional Requirement in ''Additional Requirement for Linux¢ SUSE Installation'' on page 544).
SIP User's Manual 6. 14. Installing Linux™ Operating System on the OSN Server On the Terminal screen, the BIOS phase starts and the Linux™ installation begins. The installation uncompresses the kernel, loads it and its drivers and starts the interactive installation. Notes: • After the BIOS phase, some badly formatted text may appear on the screen. • From this point on, you should proceed with the screen instructions as instructed by your Linux distributor. 7.
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 554 Document #: LTRT-83303
SIP User's Manual 15 15. Supplied SIP Software Package Supplied SIP Software Package The table below lists the standard SIP software package supplied with the SIP device. Table 15-1: Supplied Software Package File Name Description Ram.cmp file M1000_Digital_SIP_xxx.cmp Image file containing the software for the Mediant 1000 device. M1000_SIP_xxx.cmp Image file containing the software for both FXS and FXO modules. M600_Digital_SIP_xxx.cmp Image file containing the software for the Mediant 600 device.
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 556 Document #: LTRT-83303
SIP User's Manual 16. Selected Technical Specifications 16 Selected Technical Specifications 16.1 Mediant 1000 The table below lists the main technical specifications of the Mediant 1000.
Mediant 1000 & Mediant 600 Function Specification FXO Functionality Short or long haul, up to 7,000 m (24,000 ft.), using 24 AWG line cord 4 ports per FXO module Far-end disconnect detection Lightning and high voltage protection for outdoor operation Programmable Line Characteristics: AC impedance matching, hybrid balance, Tx & Rx frequency response, Tx & Rx Gains, ring detection threshold, DC characteristics Note: For a specific coefficient file, please contact AudioCodes.
SIP User's Manual 16. Selected Technical Specifications Function Full-Duplex Parties per Conference Bridge (Max.) Specification 60 Fax/Modem Relay Fax Relay Fax Transparency Modem Transparency Group 3 fax relay up to 14.4 kbps with auto fallback T.30 (PSTN) and T.38 (IP) compliant, real time fax relay Tolerant network delay (up to 9 seconds round trip) CNG tone detection & Relay per T.38 Answer tone (CED or AnsAm) detection & Relay per T.
Mediant 1000 & Mediant 600 Function Specification Physical Dimensions (W x H x D) 482.6 mm (19”) x 1U x 350.5 mm (13.8”) Weight Approx. 5 kg (depending on number of installed modules) Supply Voltage and Power Consumption Universal 100 - 240 VAC; 50 - 60 Hz; 1 A max.
SIP User's Manual 16.2 16. Selected Technical Specifications Mediant 600 The table below lists the main technical specifications of the Mediant 600.
Mediant 1000 & Mediant 600 Function Modem Transparency Specification Automatic switching to PCM or ADPCM on V.34 or V.90 modem detection Automatic switching (pass-through) to PCM, ADPCM or NSE bypass mode for modem signals (V.34 or V.
SIP User's Manual 16.
Mediant 1000 & Mediant 600 Reader's Notes SIP User's Manual 564 Document #: LTRT-83303
SIP User's Manual 17 17. Glossary Glossary Table 17-1: Glossary of Terms Term Meaning ADPCM Adaptive Differential PCM - voice compression AIS Alarm Indication Signal A-law Standard companding algorithm, used in European digital communications systems to optimize the dynamic range of an analog signal for digitizing.
Mediant 1000 & Mediant 600 Term Meaning IPSec IP Security ISDN Integrated Services Digital Network ISO International Standards Organization ITU International Telecommunications Union ITU-T Telecommunications section of the ITU IVR Interactive Voice Response Jitter Variation of interpacket timing interval kbps Kilobit per second. 1,000 bits per second LAPD Line Access Protocol for the D-channel LFA Loss of Frame Alignment LOF Loss of Frame Mbps Megabit per second.
SIP User's Manual 17.
User's Manual Version 5.4 www.audiocodes.
