This document describes the AudioCodes Mediant 600 and Mediant 1000 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. Before consulting this document, check the corresponding Release
Notes regarding feature preconditions and/or specific support in this release. In cases where
there are discrepancies between this document and the Release Notes, the information in the
Release Notes supersedes that in this document. Updates to this document and other
documents as well as software files can be downloaded by registered customers at
This document is subject to change without notic e.
Date Published: February-15-2011
Trademarks
AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP
Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open
Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect,
VoIPerfectHD, What’s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or
registered trademarks of AudioCodes Limited. All other products or trademarks are
property of their respective owners. Product specifications are subject to change without
notice.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical support and service are provided by AudioCodes’ Distributors,
Partners, and Resellers from whom the product was purchased. For Customer support for
products purchased directly from AudioCodes, c ontact support@audiocodes.com
Abbreviations and Terminology
.
Each abbreviation, unless widely used, is spell ed out in full when first used.
Version 6.2 19 February 2011
Page 20
Mediant 600 & Mediant 1000
to the PSTN/PBX (i.e., telephone connected directly or indirectly to the
Related Documentation
Manual Name
SIP CPE Release Notes
Product Reference Manual for SIP CPE Devices
Mediant 600 Installation Manual
Mediant 1000 Installation Manual
CPE Configuration Guide for IP Voice Mail
Note: Throughout this manual, unless otherwise specified, the term device refers to
the Mediant 600 and Mediant 1000 gateways.
Note: Before configuring the device, ensure that it is installed correctly as instructed
in the device's Installation Manual.
Note: For assigning an IP address to the device for initial connectivity, refer to the
Installation Manual.
Note: The terms IP-to-Tel and Tel-to-IP refer to the direction of the call relative to
the device. IP-to-Tel refers to calls received from the IP network and destined
Notes:
device); Tel-to-IP refers to calls received from the PSTN/PBX and destined
for the IP network.
•FXO (Foreign Exchange Office) is the interface replacing the analog
telephone and connects to a Public Switched Tel ephone Network (PSTN)
line from the Central Office (CO) or to a P rivate Branch Exchange (PBX).
The FXO is designed to receive line voltage and ringing current, supplied
from the CO or the PBX (just like an analog telephone). An FXO VoIP
device interfaces between the CO/PBX line and the Internet.
•FXS (Foreign Exchange Station) is the interfac e replacing the Exchange
(i.e., the CO or the PBX) and connects to analog telephones, dial-up
modems, and fax machines. The FXS is designed to supply line voltage
and ringing current to these telephone devi ces. An FXS VoIP device
interfaces between the analog telephone devices and the Internet.
SIP User's Manual 20 Document #: LTRT-83308
Page 21
SIP User's Manual 1. Overview
1 Overview
This section provides an overview of the Mediant 1000 and M ediant 600 media gateways.
1.1 Mediant 600
The Mediant 600 (hereafter referred to as device) is a cost-effective, wireline Voice-over-IP
(VoIP) Session Initiation Protocol (SIP)-based media gateway. It is designed to interface
between Time-Division Multiplexing (TDM) and IP networks in enterprises, small and
medium businesses (SMB), and CPE application service providers. Incorporating
AudioCodes’ innovative VoIP technology, the device enables rapid time-to-market and
reliable cost-effective deployment of next-gene ration netwo rks.
The device is based on VoIPerfect, AudioCodes underlying, best-of-breed, media gateway
core technology. The device provides superior voice technology for connecting legacy
telephone and PBX systems to IP networks, as well as seamlessly connecting IP-PBXs to
the PSTN. The device also provides SIP trunking capabilities for Enterprises operating with
multiple Internet Telephony Service Providers (ITSP) for VoIP services. The device is fully
interoperable with multiple vendors of IP-PBXs, IP Centrex application servers,
softswitches, gateways, proxy servers, IP phones, Session Border Controllers and
firewalls.
The device supports the following interface s:
Up to two E1/T1/J1 spans (including fractional E1/T1)
Up to eight ISDN Basic Rate Interface (BRI) interfaces
Up to four FXO interfaces (RJ-11 ports) - for connecting analog lines of an enterprise's
PBX or the PSTN to the IP network
Up to four FXS interfaces (RJ-11 ports) - for connecting legacy telephones, f ax
machines, and modems to the IP network. Opt i onal l y, the FXS interfaces can be
connected to the external trunk lines of a PB X .
When deployed with a combination of FXO and FXS modules, the device can be used as a
PBX for Small Office Home Office (SOHO) users, and businesses not equipped with a
PBX. These interfaces can be provided in one of the fol l owing configurations:
1 x E1/T1 port (can support also Fractional E1/T1)
2 x E1/T1 ports
4 x BRI ports (supporting up to 8 voice calls)
8 x BRI ports (supporting up to 16 voice calls)
4 x BRI ports and 1 x E1/T1 port
4 x BRI ports and 4 x FXS ports
4 x BRI ports and 4 x FXO ports
4 x FXS ports and 1 x E1/T1 port
4 x FXO ports and 1 x E1/T1 port
The device supports various ISDN PRI protocols such as EuroISDN, North American NI2,
Lucent™ 4/5ESS, Nortel™ DMS100 and others, supporting different variants of CAS
protocols, including MFC R2, E&M immediate start, E&M delay dial / start, loop- and
ground-start signaling. The device also supports various ISDN BRI protocols such as ETSI
5ESS and QSIG over BRI. The device also provides dual Ethernet 10/100Base-TX ports
for IP redundancy.
Intelligently packaged in a stackable 1U chassis, the compact device can be mounted on a
desk or in a standard 19-inch rack.
Version 6.2 21 February 2011
Page 22
Mediant 600 & Mediant 1000
The device provides a variety of management and provisioning tools, including an HTTPbased embedded Web server, Telnet, Element Management System (EMS), and Simple
Network Management Protocol (SNMP). The user-friendly, Web interface provides remote
configuration using a Web browser (such as Mi cro soft™ Internet Explorer™).
1.2 Mediant 1000
The Mediant 1000 (hereafter referred to as device) is a best-of-breed Voice-over-IP (VoIP)
Session Initiation Protocol (SIP) Media Gateway, using field-proven, market-leading
technology, implementing analog and digital cutting-edge technology. The device is
designed to seamlessly interface between Time-Division Multiplexing (TDM) and Internet
Protocol (IP) networks, providing superior voice quality and optimized packet voice
streaming (voice, fax, and data traffic) over I P networks.
The device is best suited for small-to-medium sized (SME) enterprises, branch offices, and
residential media gateway solutions. The device is a highly scalable and modular system
that matches the density requirements for smaller environments, while meeting service
providers' demands for growth.
The device is ideal for connecting an enterprise's legacy telephones, fax machines, and
Private Branch Exchange (PBX) systems to IP-based telephony networks, as well as for
seamlessly connecting IP-based PBX architecture to the Public Switched Telephone
Network (PSTN). The device also provides SIP trunking capabilities (including IP-to-IP call
routing) for Enterprises operating with multiple Internet Telephony Service Providers (ITSP)
for VoIP services. In addition to operating as a pure media gateway, the device
incorporates an open platform, known as the Open Solutions Network (OSN) server,
allowing additional deployment options by hosting third-party partner VoIP applications
such as IP-PBX, Calling Card, and IP-P BX redundancy.
The device also provides conferencing services over VoIP networks. This is supported by
an optional Media Processing Module (MPM) that can be housed in the device's chassis.
The MPM module also provides IP Media channels for use on various Media Server
applications.
The device is fully interoperable with multiple vendor gateways, softswitches, SIP servers,
gatekeepers, proxy servers, IP phones, session border controllers (SBC), and firewalls.
The device is designed to meet regulatory approval (including Safety, EMC, and Telecom
for USA, EU and other countries).
Intelligently packaged in a stackable and compact 1U chassis, it can be mounted on a
desk, a wall, or in a standard 19-inch rack. The device is supplied with two integral
mounting brackets for facilitating rack inst al lation.
The device is equipped with two 10/100Base-TX Ethernet ports for connection to the IP
network. The second Ethernet port is used for 1+1 Ethernet redundancy.
The device supports mixed digital and analog int erf ace configurations:
Digital:
•The device supports multiples of 1, 2, or 4 E1/T1/ J1 spans for connecting the
PSTN/PBX to the IP network. The digital modules provide RJ-48 ports. The digital
module can be configured with up to 1 or 2 paired spa ns for switching to the
PSTN in case of power or network failure (PST N Fal lback).
•The device also supports ISDN Basic Rate Interface (BRI) modules for
connecting BRI-based PSTN or PBX lines to the I P network. Each BRI module
supports four BRI ports (RJ-45). Up to five BRI modules can be ho used in the
device, supporting up to 20 BRI digital ports. Th e B RI m odule can be configured
as 'Lifeline' telephone interfaces, switching to the PSTN in case of power failure
or network problems.
•Depending on configuration, the device can provide IP Media channels at the
expense of PSTN channels. These channels may be used for Media Server
applications.
SIP User's Manual 22 Document #: LTRT-83308
Page 23
SIP User's Manual 1. Overview
Analog: The device's analog interface supports up to 24 analog ports (four ports per
analog module) in various Foreign Exchange Off i ce (FXO) or Foreign Exchange
Station (FXS) configurations, supporting up t o 24 sim ultaneous 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. The FXS module can b e used to connect legacy telephones,
fax machines, and modems to the IP network. Opt i onally, the FXS module can be
connected to the external trunk lines of a PB X . When deployed with a combination of
FXO and FXS modules, the device can be used as a P BX for Small Office Home
Office (SOHO) users, and businesses not equi pped with a PBX.
Media Processing Module (MPM): The MPM module provides IP media channels for
conferencing and media server functionality. The device can house up to three MPM
modules.
The device has enhanced hardware and software capabilities to ease its installation and to
maintain voice quality. If the measured voice quality falls beneath a pre-configured value,
or the path to the destination is disconnected, the device assures voice connectivity by
'falling' back to the PSTN. In the event of network problems or power failures, calls can be
routed back to the PSTN without requiring routing modifications in the PBX. Further
reliability is provided by dual Ethernet ports and an optional dual AC power supply.
The device supports various ISDN PRI protocols such as EuroISDN, North American NI2,
Lucent™ 4/5ESS, Nortel™ DMS100 and others. It also supports various ISDN BRI
protocols such as ETSI 5ESS and QSIG over BRI. In addition, it supports different variants
of CAS protocols for E1 and T1 spans, including MFC R2, E&M immediate start, E&M
delay dial / start, loop start and ground start.
The device provides a variety of management and provisioning tools, including an HTTPbased embedded Web server, Telnet, Element Management System (EMS), and Simple
Network Management Protocol (SNMP). The user-friendly, Web interface provides remote
configuration using a Web browser (such as Mi cro soft™ Internet Explorer™).
Version 6.2 23 February 2011
Page 24
Mediant 600 & Mediant 1000
1.3 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. SIP uses elements called Proxy
servers to help route requests to the user's current location, authenticate and authorize
users for services, implement provider call-routing policies and provide features to users.
SIP also provides a registration function that enables users to upload their current locations
for use by Proxy servers. SIP implemented in the gateway, complies with the Internet
Engineering Task Force (IETF) RFC 3261 (refer to http://www.ietf.org).
SIP User's Manual 24 Document #: LTRT-83308
Page 25
SIP User's Manual 2. Configuration Concepts
which accesses the device using the device's MAC address (refer to the
2 Configuration Concepts
This section discusses the device's configuration tools.
2.1 Configuration Tools
You can configure the device, using the following management tools:
The device's HTTP-based Embedded Web Server (Web interface), using any
standard Web browser (described in ''Web-based Management'' on page 27).
A configuration ini file loaded to the device (see ''ini File Configuration'' on p age 219).
AudioCodes’ Element Management System (see ''Element Management S ystem
(EMS)'' on page 225).
Simple Network Management Protocol (SNMP) browser software (refer to the Product
Reference Manual).
Note: To initialize the device by assigning it an IP address, a firmware file (cmp),
and a configuration file (ini file), you can use AudioCodes' BootP/TFTP utility,
Product Reference Manual).
Version 6.2 25 February 2011
Page 26
Mediant 600 & Mediant 1000
Reader's Notes
SIP User's Manual 26 Document #: LTRT-83308
Page 27
SIP User's Manual 3. Web-Based Management
3 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 software (*.cmp), configuration (*.ini), and auxiliary files, and resetting the
device. The Web interface provides real-time, online monitoring of the device, including
display of alarms and their severity. In addition, it displays performance statistics of voice
calls and various traffic parameters.
The Web interface provides a user-friendly, graphical user interface (GUI), which can be
accessed using any standard Web browser (e.g., Microsoft™ Internet Explorer). Access to
the Web interface is controlled by various security mechanisms such as login user name
and password, read-write privileges, and limi ting access to specific IP addresses.
Notes:
•For a detailed description of all the paramet ers in the Web interface, see
''Configuration Parameters Reference'' on page 501.
•The parameters in the Web interface can alternati vely be configured
using their corresponding ini file parameters, w hi ch are enclosed in
square brackets "[...]" in ''Configuration Parameters Reference'' on page
501.
•The Web interface allows you to configure most of the device's settings.
However, additional configuration param eters may exist that are not
provided in the Web interface and which can only be configured using ini
file parameters. These parameters are listed without a corresponding
Web parameter name in ''Configuration Parameter s Referen ce'' on page
501.
•Some Web interface pages are Software Upgrade Key dependant. These
pages appear only if the installed Software Upg rade Key supports the
features related to the pages. For viewing y our S oftware Upgrade Key,
see ''Loading Software Upgrade Key'' on page 201.
3.1 Getting Acquainted with the Web Interface
This section describes the Web interface with regards to its graphical user interface (GUI)
3.1.1 Computer Requirements
Version 6.2 27 February 2011
and basic functionality.
To use the device's Web interface, the followin g i s required:
A connection to the Internet network (World Wide Web).
A network connection to the device's Web interface.
One of the following Web browsers:
•Microsoft™ Internet Explorer™ (version 6.0 or later)
®
•Mozilla Firefox
(version 2.5 or later)
Recommended screen resolutions: 1024 x 768 pixels, or 1280 x 1024 pixels.
Note: Your Web browser must be JavaScript-enabled to access the Web interface.
Page 28
Mediant 600 & Mediant 1000
3.1.2 Accessing the Web Interface
The Web interface can be opened using any standard Web browser (see ''Computer
Requirements'' on page 27). When initially accessing the Web interface, use the default
user name ('Admin') and password ('Admin'). For changing the login user name and
password, see ''Configuring the Web User Accounts'' on page 66).
Note: For assigning an IP address to the device, ref er to the Installation Manual.
To access the Web interface:
1. Open a standard Web browser application.
2. In the Web browser's Uniform Resource Locator (URL) field, specify the device's IP
address (e.g., http://10.1.10.10); the Web interface's Login screen appears, as shown
in the figure below:
Figure 3-1: Login Screen
3. In the 'User Name' and 'Password' fields, enter the case-sensitive, user name and
password.
4. Click the OK button; the Web interface is accessed, displaying the 'Home' page (for a
detailed description of the 'Home' page, see ''U sing the Home Page'' on page 51).
SIP User's Manual 28 Document #: LTRT-83308
Page 29
SIP User's Manual 3. Web-Based Management
, and then scroll down to the Logon
Note: If access to the device's Web interface is denied ("Unauthorized") due to
Microsoft Internet Explorer security sett ings, perform the following:
1. Delete all cookies in the Temporary Internet Files folder. If this does not
resolve the problem, the security settings may need to be altered
(continue with Step 2).
2. In Internet Explorer, navigate to Tools menu > Internet Options >
Security tab > Custom Level
options and select Prompt for username and password. Select the
Advanced tab, and then scroll down until the HTTP 1.1 Settings are displayed and verify that Use HTTP 1.1 is selected.
3. Quit and start the Web browser again.
3.1.3 Areas of the GUI
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.
Toolbar: Provides frequently required command buttons for configuration (see
''Toolbar'' on page 30).
Navigation Pane: Consists of the following areas:
•Navigation bar: Provides tabs for accessing the conf iguration menus (see
''Navigation Tree'' on page 31), creating a Scenario ( see Scenarios on page 40),
and searching ini file parameters that have corre sponding Web interface
parameters (see ''Searching for Configuration Parameters'' on page 39).
•Navigation tree: Displays the elements pertaining to t he tab selected on the
Navigation bar (tree-like structure of the conf iguration menus, Scenario Steps, or
Search engine).
Work pane: Displays configuration pages where configuration is perform ed (see
Version 6.2 29 February 2011
''Working with Configuration Pages'' on page 34).
Page 30
3.1.4 Toolbar
The toolbar provides command buttons for quick-and-easy access to frequently required
commands, as described in the table below:
Mediant 600 & Mediant 1000
Table 3-1: Description of Toolbar Buttons
Icon Button
Description
Name
Submit
Applies parameter settings to the device (se e ''Sav i ng Configuration''
on page 197).
Note: This icon is grayed out when not applicable to the currently
opened page.
Burn
Device
Actions
Saves parameter settings to flash memo ry (see ''Saving
Configuration'' on page 197).
Opens a drop-down menu list with frequently needed commands:
Load Configuration File: opens the 'Configuration File' page for
loading an ini file (see ''Backing Up and Loading Configuration
File'' on page 207).
Save Configuration File: opens the 'Configuration File' page for
saving the ini file to a PC (see ''Backing Up and Loading
Configuration File'' on page 207).
Reset: opens the 'Maintenance Actions' page for resetting the
device (see ''Resetting the Device'' on page 195).
Software Upgrade Wizard: opens the 'Software Upgrade Wizard'
page for upgrading the device's software (see ''S oftware Upgrade
Wizard'' on page 204).
Home
Opens the 'Home' page (see ''Using the Home Page'' on page 51).
Help
Log off
Opens the Online Help topic of the currently opened configuration
page in the Work pane (see ''Getting Help'' on page 49).
Logs off a session with the Web interface (see ''Loggi ng Off the Web
Interface'' on page 50).
Note: If you modify parameters that take effect only after a device reset, after you
click the Submit button, the toolbar displays the word "Reset" (in red color),
as shown in the figure below. This is a reminder to later save ('burn') your
settings to flash memory and reset the devi ce.
Figure 3-3: "Reset" Displayed on Toolbar
SIP User's Manual 30 Document #: LTRT-83308
Page 31
SIP User's Manual 3. Web-Based Management
3.1.5 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 i n the Work pane.
The terminology used throughout this manual for referring to the hierarchical structure of
the tree is as follows:
menu: first level (highest level)
submenu: second level - contained within a menu.
page item: last level (lowest level in a menu) - contained within a menu or submenu
Figure 3-4: Navigation Tree Description
To view menus in the Navigation tree:
On the Navigation bar, select the required tab:
• Configuration (see ''Configuration Tab'' on page 58)
• Maintenance (see ''Maintenance Tab'' on page 194)
• Status & Diagnostics (see ''Status & Diagnostics Tab'' on page 208)
To navigate to a page:
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
Version 6.2 31 February 2011
2. Select the required page item; the page opens in the Work pane.
Page 32
Mediant 600 & Mediant 1000
3.1.5.1 Displaying Navigation Tree in Basic and Full View
You can view an expanded or reduced Navigation tree display regarding the number of
listed menus and submenus. This is relevant when using the configuration tabs
(Configuration, Maintenance, and Status & Diagnostics) on the Navigation bar.
The Navigation tree menu can be displayed in one of two views:
Basic: displays only commonly used menus
Full: displays all the menus pertaining to a configuration tab.
The advantage of the Basic view is that it prevents "cluttering" the Navigation tree with
menus that may not be required. Therefore, a Basic view allows you to easily locate
required menus.
To toggle between Full and Basic view:
Select the Basic option (located below the Navigation bar) to display a reduced menu
tree; select the Full option to display all the menus. By default, the Basic option is
selected.
Figure 3-5: Toggling Between Views
Note: When in Scenario mode (see Scenarios on page 40), the Navigation tree is
displayed in 'Full' view (i.e., all menus are di splayed in the Navigation tree).
SIP User's Manual 32 Document #: LTRT-83308
Page 33
SIP User's Manual 3. Web-Based Management
3.1.5.2 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.
To hide the Navigation pane: click the left-pointing arrow ; the pane is hidden
and the button is replaced by the right-pointing arrow but ton.
To show the Navigation pane: click the right-pointing arrow ; the pane is
displayed and the button is replaced by the left-pointing arrow button.
Figure 3-6: Showing and Hiding Navigation Pane
Version 6.2 33 February 2011
Page 34
Mediant 600 & Mediant 1000
3.1.6 Working with Configuration Pages
The configuration pages contain the parameters for configuring the device. The
configuration pages are displayed in the Work pane, which is located to the right of the
3.1.6.1 Accessing Pages
Navigation pane.
The configuration pages are accessed by clicking the required page item in the Navigation
tree.
To open a configuration page in the Work pane:
1. On the Navigation bar, click the required tab:
• Configuration (see ''Configuration Tab'' on page 58)
• Maintenance (see ''Maintenance Tab'' on page 194)
• Status & Diagnostics (see ''Status & Diagnostics Tab'' on page 208)
The menus of the selected tab appear in the Nav i gation tree.
2. In the Navigation tree, drill-down to the required page item; the page opens in the
Work pane.
You can also access previously opened pages, by clicking your Web browser's Back
button until you have reached the required page. This is useful if you want to view pages in
which you have performed configurations in the current Web session.
Notes:
•You can also access certain pages from the Device Actions button
located on the toolbar (see ''Toolbar'' on page 30).
•To view all the menus in the Navigation tree, ensure t hat the Navigation
tree is in 'Full' view (see ''Displaying Navigation Tree in Basic and Full
View'' on page 32).
•To get Online Help for the currently displayed page, see ''Getting Help''
on page 49.
•Certain pages may not be accessible or may be rea d-only if your Web
user account's access level is low (see ''Configuring the Web User
Accounts'' on page 66). If a page is read-only, 'Read-Only Mode' is
displayed at the bottom of the page.
3.1.6.2 Viewing Parameters
For convenience, some pages allow you to view a reduced or expanded display of
parameters. A reduced display allows you to easily identify required parameters, enabling
you to quickly configure your device.
The Web interface provides you with two methods for handling the display of page
parameters:
Display of "basic" and "advanced" parameters (see ''Displaying Basic and A dvanced
Parameters'' on page 35)
Display of parameter groups (see ''Showing / Hiding Parameter Groups'' on page 36)
SIP User's Manual 34 Document #: LTRT-83308
Page 35
SIP User's Manual 3. Web-Based Management
3.1.6.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 t o
display all parameters.
Basic Parameter List button with up-pointing arrow: click this button to sho w only
common (basic) parameters.
The figure below shows an example of a page displaying basic parameters only, and then
showing advanced parameters as well, using the Advanced Parameter List button.
Figure 3-7: Toggling between Basic and Advanced View
For ease of identification, the basic parameters are displayed with a darker blue color
background than the advanced parameters.
Notes:
•When the Navigation tree is in 'Full' mode (see ''Nav i gation Tree'' on
page 31), configuration pages display all their pa ram eters (i.e., the
'Advanced Parameter List' view is displayed).
•If a page contains only basic parameters, the Basic P arameter List
button is not displayed.
Version 6.2 35 February 2011
Page 36
Mediant 600 & Mediant 1000
3.1.6.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.1.6.3 Modifying and Saving Parameters
When you change parameter values on a page, the Edit symbol appears to the right of
these parameters. This is especially useful for indicating the parameters that you have
currently modified (before applying the changes). After you save your parameter
modifications (refer to the procedure des cribed below), the Edit symbols disappear.
Figure 3-9: Edit Symbol after Modifying Parameter Value
To save configuration changes on a page to the device's volatile memory
(RAM):
Click the Submit button, which is located near the bottom of the page in which
you are working; modifications to parameters with on-the-fly capabilities are
immediately applied to the device and take effect; other parameters (displayed on the
page with the lightning symbol) are not changeable on-the-fly and require a device
reset (see ''Resetting the Device'' on page 195) before taking effect.
SIP User's Manual 36 Document #: LTRT-83308
Page 37
SIP User's Manual 3. Web-Based Management
Notes:
•Parameters saved to the volatile memory (by clicking Submit), revert to
their previous settings after a hardware or software reset (or if the device
is powered down). Therefore, to ensure parameter changes (whether onthe-fly or not) are retained, you need to save ('burn') t hem to the device's
non-volatile memory, i.e., flash (see ''Saving Configuration'' on page
197).
•If you modify a parameter value and then attempt to navigate away from
the page without clicking Submit, a message box appears noti fying you
of this. Click Yes to save your modifications or No to ignore them.
If you enter an invalid parameter value (e.g., not in the range of permitted values) and then
click Submit, a message box appears notifying you of the invalid value. In addition, the
parameter value reverts to its previous value and is highlighted in red, as shown in the
figure below:
Figure 3-10: Value Reverts to Previous Valid Value
3.1.6.4 Entering Phone Numbers
Phone numbers or prefixes that you need to configure throughout the Web interface must
be entered only 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
Version 6.2 37 February 2011
hyphen is entered, the entry is invalid.
Page 38
Mediant 600 & Mediant 1000
3.1.6.5 Working with Tables
The Web interface includes many configuration pages that provide tables for configuring
the device. Some of these tables provide the fol l owing command buttons:
Add Index: adds an index entry to the table.
Duplicate: duplicates a selected, existing index entry.
Compact: organizes the index entries in ascending, consecutive order.
Delete: deletes a selected index entry.
Apply: saves the configuration.
To add an entry to a table:
1. In the 'Add Index' field, enter the desired index entry number, and then click Add
Index; an index entry row appears in the table:
Figure 3-11: Adding an Index Entry to a Table
2. Click Apply to save the index entry.
Notes:
•Before you can add another index entry, you must ensure that you have
applied the previously added index entry (by clic king Apply).
•If you leave the 'Add' field blank and then click Add Index, the existing
index entries are all incremented by one and the newly added index entry
is assigned the index 0.
To add a copy of an existing index table entry:
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 b ecome available.
3. Click Duplicate; a new index entry is added with identical settings as the selected
index in Step 1. In addition, all existing index entries are incremented by one and the
newly added index entry is assigned the index 0.
To edit an existing index table entry:
1. In the 'Index' column, select the index corresponding to the table row that you want to
edit.
2. Click Edit; the fields in the corresponding index row b ecome available.
3. Modify the values as required, and then click Apply; the new settings are applied.
SIP User's Manual 38 Document #: LTRT-83308
Page 39
SIP User's Manual 3. Web-Based Management
To organize the index entries in ascending, consecutive order:
Click Compact; the index entries are organized in ascending, consecutive order,
starting from index 0. For example, if you added three index entries 0, 4, and 6, then
the index entry 4 is re-assigned index number 1 and the index entry 6 is re-assigned
index number 2.
Figure 3-12: Compacting a Web Interface Table
To delete an existing index table entry:
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.
3.1.7 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). You can search for a specific parameter (e.g., "EnableIPSec") or a sub-string
of that parameter (e.g., "sec"). If you search for a sub-string, all parameters that contain the
searched sub-string in their names are listed.
To search for ini file parameters configurable in the Web interface:
1. On the Navigation bar, click the Search tab; the Search engine appears in the
Navigation pane.
2. In the 'Search' field, enter the parameter name or sub-string of the parameter name
that you want to search. If you have performed a previous search for such a
parameter, instead of entering the required string, you can use the 'Search History'
drop-down list to select the string (saved from a previous search).
3. Click Search; a list of located parameters based on your search appears in the
Navigation pane.
Version 6.2 39 February 2011
Page 40
Mediant 600 & Mediant 1000
Each searched result displays the following:
• ini file parameter name
• Link (in green) to its location (page) in the Web interface
• Brief description of the parameter
4. 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.
3.1.8 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, Maintenance, 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.
For each Step, you can select up to 25 parameters in the page that you want available in
the Scenario. Therefore, the Scenario feature is useful in that it allows you quick-and-easy
access to commonly used configuration parameters specific to your network environment.
When you login to the Web interface, your Scenario is displayed in the Navigation tree,
thereby, facilitating your configuration.
Instead of creating a Scenario, you can also load an existing Scenario from a PC to the
device (see ''Loading a Scenario to the Device'' on p age 46).
SIP User's Manual 40 Document #: LTRT-83308
Page 41
SIP User's Manual 3. Web-Based Management
3.1.8.1 Creating a Scenario
The Web interface allows you to create one Scenario with up to 20 configuration pages, as
described in the procedure below:
To create a Scenario:
1. On the Navigation bar, click the Scenarios tab; a message box appears, requesting
Note: If a Scenario already exists, the Scena rio Loading message box appears.
2. Click OK; the Scenario mode appears in the Navigation tree as well as the menus of
the Configuration tab.
Note: If a Scenario already exists and you wish to create a new one, click the Create
Scenario button, and then click OK in the subsequent message bo x.
3. In the 'Scenario Name' field, enter an arbitrary name for the Scenario.
4. On the Navigation bar, click the Configuration or Maintenance tab to display their
respective menus in the Navigation tree.
5. In the Navigation tree, select the required page item for the Step, and then in the page
itself, select the required parameters by selecting the check boxes corresponding to
the parameters.
6. In the 'Step Name' field, enter a name for the Step.
7. 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
Version 6.2 41 February 2011
Page 42
Mediant 600 & Mediant 1000
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 succ essfully created.
10. Click OK; the Scenario mode is quit and the menu tree of the Configuration tab
appears in the Navigation tree.
Notes:
•You can add up to 20 Steps to a Scenario, where each Step can contain
up to 25 parameters.
•When in Scenario mode, the Navigation tree is in 'Ful l' display (i.e., all
menus are displayed in the Navigation tree) and the configuration pages
are in 'Advanced Parameter List' display (i. e., all parameters are shown
in the pages). This ensures accessibility to all parameters when creating
a Scenario. For a description on the Navigation tree views, see
''Navigation Tree'' on page 31.
•If you previously created a Scenario and you click the Create Scenario
button, the previously created Scenario is delet ed and replaced with the
one you are creating.
•Only users with access level of 'Security Administrator' can create a
Scenario.
3.1.8.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:
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
SIP User's Manual 42 Document #: LTRT-83308
Page 43
SIP User's Manual 3. Web-Based Management
2. Click OK; the Scenario and its Steps appear in the Navigation tree, as shown in the
example figure below:
Figure 3-17: Scenario Example
When you select a Scenario Step, the corresponding page is displayed in the Work pane.
In each page, the available parameters are indicated by a dark-blue background; the
unavailable parameters are indicated by a gray or light-blue background.
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.
Note: If you reset the device while in Scenario mode, after the device resets, you
are returned once again to the Scenario mode.
Version 6.2 43 February 2011
Page 44
Mediant 600 & Mediant 1000
3.1.8.3 Editing a Scenario
You can modify a Scenario anytime by adding or removing Steps (i.e., pages) or
parameters, and changing the Scenario name and the Steps' names.
Note: Only users with access level of 'Security Administrator' can edit a Scenario.
To edit a Scenario:
1. On the Navigation bar, click the Scenarios tab; a message box appears, requesting
you to confirm Scenario loading.
2. Click OK; the Scenario appears with its Steps in the Navi gation tree.
3. Click the Edit Scenario button located at the bottom of the Navigation pane; the
'Scenario Name' and 'Step Name' fields appear.
4. You can perform the following edit operations:
• Add Steps:
a. On the Navigation bar, select the desired tab (i.e., Configuration or
Maintenance); the tab's menu appears in the Navigation tree.
b. In the Navigation tree, navigate to the desired page item; the corresponding
page opens in the Work pane.
c. In the page, select the required parameters, by marking the corresponding
check boxes.
d. Click Next.
• 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 cor responding 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. In the page, click Next.
• Edit the Scenario Name:
a. In the 'Scenario Name' field, edit the Scenario name.
b. In the displayed page, click Next.
• Remove a Step:
a. In the Navigation tree, select the required Step; the corresponding page
opens in the Work pane.
b. In the page, clear all the check boxes corresponding to the parameters.
c. Click Next.
5. After clicking Next, a message box appears notifying you of the change. Click OK.
6. Click Save & Finish; a message box appears informing you that the Scenario has
been successfully modified. The Scenario mode is exited and the menus of the
Configuration tab appear in the Navigation tree.
SIP User's Manual 44 Document #: LTRT-83308
Page 45
SIP User's Manual 3. Web-Based Management
3.1.8.4 Saving a Scenario to a PC
You can save a Scenario to a PC (as a dat file). This is especially useful when requiring
more than one Scenario to represent different environment setups (e.g., where one
includes PBX interoperability and another not). Once you create a Scenario and save it to
your PC, you can then keep on saving modifications to it under different Scenario file
names. When you require a specific network environment setup, you can simply load the
suitable Scenario file from your PC (see ''Loading a Scenario to the Device'' on page 46).
To save a Scenario to a PC:
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 sho wn below:
Figure 3-18: Scenario File Page
3. Click the Get Scenario File button; the 'File Download' window appears.
4. Click Save, and then in the 'Save As' window navigate to the folder to where you want
to save the Scenario file. When the file is successfully downloaded to your PC, the
'Download Complete' window appears.
5. Click Close to close the 'Download Complete' window.
Version 6.2 45 February 2011
Page 46
Mediant 600 & Mediant 1000
3.1.8.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:
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 (see ''Saving a Scenario to a PC'' on page 45).
3. Click the Browse button, and then navigate to the Scenario file stored on your P C.
4. Click the Send File button.
Notes:
•You can only load a Scenario file to a device that has an i dentical
hardware configuration setup to the device in w hich it was created. For
example, if the Scenario was created in a devi ce with FXS interfaces, the
Scenario cannot be loaded to a device that does not have FXS
interfaces.
• The loaded Scenario replaces any existing Scen ario.
• You can also load a Scenario file using BootP, by l oading an i ni file that
contains the ini file parameter ScenarioFileName (see Web and Telnet
Parameters on page 513). The Scenario dat file must be located in the
same folder as the ini file. For a detailed descript ion on BootP, refer to
the Product Reference Manual.
3.1.8.6 Deleting a Scenario
You can delete the Scenario by using the Delete Scenario File button, as described in the
procedure below:
To delete the Scenario:
1. On the Navigation bar, click the Scenarios tab; a message box appears, requesting
you to confirm:
Figure 3-19: Scenario Loading Message Box
2. Click OK; the Scenario mode appears in the Navigation tree.
SIP User's Manual 46 Document #: LTRT-83308
Page 47
SIP User's Manual 3. Web-Based Management
3. 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:
•Loading an empty dat file (see ''Loading a Scenario t o the Device'' on
page 46).
•Loading an ini file with the ScenarioFileName parameter set to no value
(i.e., ScenarioFileName = "").
3.1.8.7 Exiting Scenario Mode
When you want to close the Scenario mode after using it for device configuration, follow
the procedure below:
To close the Scenario mode:
1. Simply click any tab (besides the Scenarios tab) on the Navigation bar, or click the
Cancel Scenarios button located at the bottom of the Navigation tree; a message box
appears, requesting you to confirm exiting S cenario mode, as shown below.
Figure 3-21: Confirmation Message Box for Exiting Scenario Mode
2. Click OK to exit.
Version 6.2 47 February 2011
Page 48
Mediant 600 & Mediant 1000
3.1.9 Creating a Login Welcome Message
You can create a Welcome message box (alert message) that appears after each
successful login to the device's Web interface. The ini file table parameter
WelcomeMessage allows you to create the Welcome message. Up to 20 lines of character
strings can be defined for the message. If this parameter is not configured, no Welcome
message box is displayed after login.
An example of a Welcome message is shown in the f i gure below:
Figure 3-22: User-Defined Web Welcome Message after Login
Table 3-2: ini File Parameter for Welcome Login Message
Parameter Description
WelcomeMessage
Defines the Welcome message that appears after a successful login to the
Web interface. The format of this parameter is as follows:
[WelcomeMessage]
FORMAT WelcomeMessage_Index = WelcomeMessage_Text;
[\WelcomeMessage]
For Example:
[WelcomeMessage ]
FORMAT WelcomeMessage_Index = WelcomeMessage_Text;
WelcomeMessage 1 = "*********************************";
WelcomeMessage 2 = "********* This is a Welc om e m essage **";
WelcomeMessage 3 = "*********************************";
[\WelcomeMessage]
Note: Each index represents a line of tex t in the Welcome message box.
Up to 20 indices can be defined.
SIP User's Manual 48 Document #: LTRT-83308
Page 49
SIP User's Manual 3. Web-Based Management
3.1.10 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:
1. Using the Navigation tree, open the required page for which you want Help.
2. On the toolbar, click the Help button; the Help topic pertaining to the opened
page appears, as shown below:
Figure 3-23: Help Topic for Current Page
3. To view a description of a parameter, click the plus sign to expand the parameter.
To collapse the description, click the minus sign.
4. To close the Help topic, click the close button located on the top-right corner of
the Help topic window or simply click the Help button.
Note: Instead of clicking the Help button for each page you open, you can open it
once for a page and then simply leave it open. Each time you open a different
page, the Help topic pertaining to that page is automatically displayed.
Version 6.2 49 February 2011
Page 50
Mediant 600 & Mediant 1000
3.1.11 Logging Off the Web Interface
You can log off the Web interface and re-access it with a different user account. For
detailed information on the Web User Account s, see User Accounts.
To log off the Web interface:
1. On the toolbar, click the Log Off button; the Log Off confirmation message box
appears:
Figure 3-24: Log Off Confirmation Box
2. Click OK; the Web session is logged off and the Log In button appears.
Figure 3-25: 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 (see ''Accessing the Web Interface'' on
page 28).
SIP User's Manual 50 Document #: LTRT-83308
Page 51
SIP User's Manual 3. Web-Based Management
3.2 Using the Home Page
The 'Home' page provides you with a graphical display of the device's front panel,
displaying color-coded status icons for monitoring the functioning of the device. The 'Home'
page also displays general device information (in the 'General Information' pane) such as
the device's IP address and firmware version.
By default, the 'Home' page is displayed when you a ccess the device's Web interface.
To access the Home page:
On the toolbar, click the Home icon; the 'Home' page is displayed.
Figure 3-26: Mediant 600 Home Page
Figure 3-27: Mediant 1000 Home Page
Note: The displayed number and type of telephony interface modules depends on
the device's hardware configuration.
In addition to the color-coded status information depicted on the graphical display of the
device (as described in the subsequent table), the Home page displays various read-only
information in the General Information pa ne:
IP Address: IP address of the device
Subnet Mask: subnet mask address of the device
Default Gateway Address: default gateway used by the device
Digital Port Number: number of digital PRI ports (appears only if the device houses a
DIGITAL module)
BRI Port Number: number of BRI ports (appears only if the device houses a BRI
module)
Analog Port Number: number of analog (FXS and FXO) ports (appears only if the
device houses an FXS or FXO module)
Firmware Version: software version currently running on the device
Version 6.2 51 February 2011
Page 52
Mediant 600 & Mediant 1000
Protocol Type: signaling protocol currently used by the device (i.e. SIP)
Gateway Operational State: operational state of the device:
• LOCKED - device is locked (i.e. no new calls are accepted)
• UNLOCKED - device is not locked
• SHUTTING DOWN - device is currently shutting down
To perform these operations, see ''Maintenance A ct i ons'' on page 194.
Table 3-3: Description of the Areas of the Home Page
Item # Description
1
2
3
4
5
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 A l arm s' page (see Viewing Active Alarms
on page 211), click the Alarms area.
Module slot number (1 to 26).
Module type: FXS, FXO, DIGITAL (i.e., E1/T1), BRI, IPMEDIA.
Module status icon:
(green): Module has been inserted or is correctly configured
(gray): Module was rem oved. 'Reserved' is displayed alongside the module's
name
(red): Module failure. 'Failure' is displayed instead of the module's name
Port (trunk or channel) status icon (see Viewing T runks' Channels on page 55).
Icon Trunk Description
(Digital Module)
Channel Description
(Analog Module)
(grey)
(green)
(yellow)
Disable: Trunk not configured (not
in use)
Active - OK: Trunk synchronized Call Connected: Active RTP
RAI Alarm: Remote Alarm Indication
(RAI), also known as the Yellow
Inactive: Channel is currently
on-hook
stream
-
Alarm
(red)
(blue)
LOS / LOF Alarm: Loss due to LOS
(Loss of Signal) or LOF (Loss of
Frame)
AIS Alarm: Alarm Indication Signal
(AIS), also known as the Blue Alarm
Not Connected: No analog
line is connected to this port
(FXO only)
Handset Offhook: Channel is
off-hook, but there is no
active RTP session
(orange)
D-Channel Alarm: D-channel alarm -
SIP User's Manual 52 Document #: LTRT-83308
Page 53
SIP User's Manual 3. Web-Based Management
Item # Description
6
7
8
9
10
11
Dry Contact (normally open) status icon
(green): Dry Contact is open (normal)
(red): Dry contact is closed
Dry Contact (normally closed) status icon:
(green): Dry Contact is closed (normal)
(red): Dry contact is open
CPU module.
Ethernet LAN port status icons:
(green): Ethernet link is working
(gray): Ethernet link is not configured
You can also view detailed Ethernet port information in the 'Ethernet Port Information'
page (see Viewing Ethernet Port Information on page 210), by clicking the icon.
Fan tray unit status icon:
(green): Fan tray operating
(red): Fan tray failure
Power Supply Unit 1 status icon (applicable only to M edi ant 1000):
(green): Power supply is operating
(red): Power supply failure or no power supply uni t installed
12
Power Supply Unit 2 status indicator (applicable only to Mediant 1000). See Item #10
for an explanation.
Version 6.2 53 February 2011
Page 54
Mediant 600 & Mediant 1000
3.2.1 Assigning a Port Name
The 'Home' page allows you to assign an arbitrary name or a brief description to each port.
This description appears as a tooltip when you mov e your mouse over the port.
To add a port description:
1. Click the required port icon; a shortcut menu appears, as shown below:
Figure 3-28: Shortcut Menu (e.g. Mediant 1000)
2. From the shortcut menu, choose Update Port Info; a text box appears.
Figure 3-29: Typing Port Name (e.g. Mediant 1000)
3. Type a brief description for the port, and then click Apply Port Info.
3.2.2 Resetting an Analog Channel
The 'Home' page allows you to inactivate (reset) an FXO or FXS analog channel. This is
sometimes useful, for example, when the device (FXO) is connected to a PBX and the
communication between the two can't be di sconnected (e.g., when using reverse polarity).
To reset a channel:
Click the required FXS or FXO port icon, and then from the shortcut menu, choose
Reset Channel; the channel is changed to inactiv e (i.e., the port icon is displayed in
grey).
Figure 3-30: Shortcut Menu for Resetting Channel (e.g. Mediant 1000)
SIP User's Manual 54 Document #: LTRT-83308
Page 55
SIP User's Manual 3. Web-Based Management
3.2.3 Viewing Analog Port Informat ion
The 'Home' page allows you to view detailed information on a specific FXS or FXO analog
port such as RTP/RTCP and voice settings.
To view detailed port information:
1. Click the port for which you want to view port settings; the shortcut menu appears.
Figure 3-31: Shortcut Menu for Viewing Analog Port Information (e.g. Mediant 1000)
2. From the shortcut menu, click Port Settings; the 'Basic Channel Information' page
appears.
Figure 3-32: Basic Information Screen
3. To view RTP/RTCP or voice settings, click the relevant button.
3.2.4 Viewing Trunk Channels
The 'Home' page allows you to drill-down to view a detailed status of the channels
pertaining to a trunk In addition, you can also vi ew t he trunk's configuration.
To view a detailed status of a trunk's channels:
1. In the Home page, click the trunk port icon of whose status you want to view; a
shortcut menu appears.
2. From the shortcut menu, choose Port Settings; the 'Trunks & Channels Status' page
pertaining to the specific trunk appears:
Figure 3-33: Trunks and Channels Status Screen
The color-coding for the status of the trunk's channels status is described in the table
below:
Version 6.2 55 February 2011
Page 56
Mediant 600 & Mediant 1000
Table 3-4: Color-Coding Status for Trunk Channels
Icon Color Label Description
Light blue Inactive Config ured, but currently no call
Green Active Call in progress (RTP traffic)
Purple SS7 Configured for SS7 (Currently not supported)
Grey Non Voice Not configured
Blue ISDN Signaling Config ured as a D-channel
Yellow CAS Blocked -
3. To view the configuration settings of the trunk and/or to modify the trunk's settings,
click the Trunk icon, and then from the shortcut menu, choose Port Settings; The
'Trunk Settings' page appears. (For detailed information on configuring the trunk in this
page, see Configuring the Trunk Settings on pa ge 99.)
3.2.5 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.
Warnings:
•A module must be replaced with the same type of m odule and in the
same module slot number. For example, a module with two digital spans
in Slot 1 must be replaced with a module with two digit al spans in Slot 1.
•When only one module is available, removal of the module causes the
device to reset.
•Before inserting a module into a previously empty slot, you must power
down the device.
Note: This section is applicable only to Mediant 1000.
SIP User's Manual 56 Document #: LTRT-83308
Page 57
SIP User's Manual 3. Web-Based Management
To replace a module:
1. Remove the module by performing the following:
a. In the 'Home' page, click the title of the module that you want to replace; the
Remove Module button appears:
Figure 3-34: Remove Module Button
b. Click the Remove Module button; a message box appears requesting you to
c. Click OK to confirm removal; after a few seconds, the module is software-
removed, the module status icon turns to grey, and the name of the module is
suffixed with the word 'Reserved':
Figure 3-36: Removed Module
d. Physically remove the module (refer to the Installatio n M anual).
2. Insert the replaced module, by performing the following:
a. Physically insert the replaced module (refer to the Installation Manual) into the
same slot in which the previous module resided.
b. In the 'Home' page, click the title of the module ('<module type> Reserved') that
you want to replace; the Insert Module button appears:
Figure 3-37: Insert Module Button
c. Click the Insert Module button; a message appears informing you that this may
take a few seconds. When the message disappears, the module is inserted,
which is indicated by the disappearance of the word 'Reserved' from the module's
name.
Version 6.2 57 February 2011
Page 58
Mediant 600 & Mediant 1000
3.3 Configuration Tab
The Configuration tab on the Navigation bar displays menus in the Navigation tree related
to device configuration. This tab provides the following main menus:
System (see ''System Settings'' on page 58)
3.3.1 System Settings
3.3.1.1 Configuring Application Settings
VoIP (see "VoIP Settings" on page 76)
The System menu includes the following:
Application Settings item (see ''Configuring Application Settings'' on page 58)
Syslog Settings item (see ''Configuring Syslog Settings'' on page 60)
Regional Settings item (see ''Configuring Regional Settings'' on page 61)
Certificates item (see ''Configuring Certificates'' on page 62)
Management submenu (see ''Management Settings'' on page 66)
The 'Application Settings' page is used for configuring various application parameters such
as Network Time Protocol (NTP), daylight savi ng time, and Network File System (NFS). For
a description of these parameters, see ''Configuration Parameters Reference'' on page
501.
To configure application settings:
1. Open the 'Application Settings' page (Configuration tab > System menu >
Application Settings).
Figure 3-38: 'Application Settings Page
SIP User's Manual 58 Document #: LTRT-83308
Page 59
SIP User's Manual 3. Web-Based Management
2. Configure the parameters as required.
3. For configuring NFS, under the 'NFS Settings' group, click the NFS Table button;
the 'NFS Settings' page appears. For a description of configuring this page, see
''Configuring NFS Settings'' on page 59.
4. Click the Submit button to save your changes.
5. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
3.3.1.2 Configuring NFS Settings
Network File System (NFS) enables the device to access a remote server's shared files
and directories, and to handle them as if they're located locally. You can configure up to 16
different NFS file systems. As a file system, the NFS is independent of machine types,
operating systems, and network architectures. NFS is used by the device to load the cmp,
ini, and auxiliary files, using the Automatic Update mechanism (refer to the Product
Reference Manual). Note that an NFS file server can share multiple file systems. There
must be a separate row for each remote file system shared by the NFS file server that
needs to be accessed by the device.
To add remote NFS file systems:
1. Open the 'Application Settings' page (see ''Configuring Application Settings'' on page
58).
2. Under the NFS Settings group, click the NFS Table button; the 'NFS Settings'
page appears.
Figure 3-39: NFS Settings Page
3. In the 'Add' field, enter the index number of the remote NFS file system, and then click
Add; an empty entry row appears in the table.
4. Configure the NFS parameters according to the table below.
5. Click the Apply button; the remote NFS file system is immediately applied, which can
be verified by the appearance of the 'NFS mount was successful' message in the
Syslog server.
6. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
Notes:
•To avoid terminating current calls, a row must not be deleted or modified
while the device is currently accessing files on t hat remote NFS file
system.
•The combination of 'Host Or IP' and 'Root Path' must be unique for each
row in the table. For example, the table must include only one row with a
Host/IP of 192.168.1.1 and Root Path of /audio.
•For an explanation on configuring Web interfac e tables, see ''Working
with Tables'' on page 38.
•You can also configure the NFS table using the ini fil e table parameter
NFSServers (see ''NFS Parameters'' on page 509).
Version 6.2 59 February 2011
Page 60
Mediant 600 & Mediant 1000
Table 3-5: NFS Settings Parameters
Parameter Description
Index The row index of the remote file system.
The valid range is 1 to 16.
Host Or IP The domain name or IP address of the NFS server. If a domain name is
provided, a DNS server must be configured.
Root Path Path to the root of the remote file system in the format: /[path]. For
example, '/audio'.
NFS Version NFS version used to access the remote file sy st em .
[2] NFS Version 2
[3] NFS Version 3 (default)
Authentication Type Authentication method used for accessing the remote file system.
[0] Null
[1] Unix (default)
User ID User ID used in authentication when using Unix .
The valid range is 0 to 65537. The default is 0.
Group ID Group ID used in authentication when using Unix.
The valid range is 0 to 65537. The default is 1.
VLAN Type The VLAN type for accessing the remote file sy st em .
[0] OAM
[1] MEDIA (default)
Note: This parameter applies only if VLANs are enabled or if Multiple
IPs is configured (see ''Network Configuration'' on page 404).
3.3.1.3 Configuring Syslog Settings
The 'Syslog Settings' page allows you to configure the device's embedded Syslog client.
For a detailed description on the Syslog parameters, see ''Syslog, CDR and Debug
Parameters'' on page 518. For viewing Syslog messages in the Web interface, see Viewing
Syslog Messages on page 208. For a detailed description on Syslog messages and using
third-party Syslog servers, refer to the Product Reference Manual.
SIP User's Manual 60 Document #: LTRT-83308
Page 61
SIP User's Manual 3. Web-Based Management
To configure the Syslog client:
1. Open the 'Syslog Settings' page (Configuration tab > System menu > Syslog
Settings).
Figure 3-40: Syslog Settings Page
2. Configure the parameters as required, and then click the Submit button to apply your
changes.
3. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
3.3.1.4 Configuring Regional Settings
The 'Regional Settings' page allows you to define and view the device's internal date and
time.
To configure the device's date and time:
1. Open the 'Regional Settings' page (Configuration tab > System menu > Regional
Settings).
Figure 3-41: Regional Settings Page
2. Enter the current date and time in the geographical location in which the device is
installed.
3. Click the Submit button; the date and time are automati call y updated.
Version 6.2 61 February 2011
Page 62
Mediant 600 & Mediant 1000
certificate, therefore, configure
Notes:
•If the device is configured to obtain the date and t i m e from an SNTP
server (see ''Configuring Application Setti ngs'' o n page 58), the fields on
this page are read-only and cannot be modified.
•For an explanation on SNTP, see ''Simple Networ k Time Protocol
Support'' on page 403.
•After performing a hardware reset, the date and time are returned to their
defaults and therefore, should be updated.
3.3.1.5 Configuring Certificates
The 'Certificates' page is used for HTTPS and SIP TLS secure communication. This page
allows you to perform the following:
Replacing the server certificate (see ''Server Certificate Replaceme nt '' on page 62)
Replacing the client certificates (see ''Client Certificates'' on page 64)
Regenerating Self-Signed Certificates (see ''Self-Signed Certificates'' on page 65)
Automatic update of the Private key (installed automatically from a file located on an
HTTPS server, defined using the HTTPSPkey F il eName parameter). For a detailed
description on automatic update methods, ref er to the Product Reference Manual.
Note: The device is shipped with a configured
certificates only if required.
3.3.1.5.1 Server Certificate Replacement
The device is supplied with a working Secure Socket Layer (SSL) configuration consisting
of a unique self-signed server certificate. If an organizational Public Key Infrastructure
(PKI) is used, you may wish to replace this certificate with one provided by your security
administrator.
To replace the device's self-signed certificate:
1. Your network administrator should allocate a unique DNS name for the device (e.g.,
dns_name.corp.customer.com). This DNS name is used to access the device and
therefore, must be listed in the server certificate.
2. If the device is operating in HTTPS mode, then set the HTTPSOnly parameter to
'HTTP and HTTPS' (0) - see ''Configuring Web Security Settings'' on page 69. This
ensures that you have a method for accessing the device in case the new certificate
doesn’t work. Restore the previous setting af ter testing the configuration.
SIP User's Manual 62 Document #: LTRT-83308
Page 63
SIP User's Manual 3. Web-Based Management
-----END CERTIFICATE-----
3. Open the ‘Certificates Signing Request' page (Configuration tab > System menu >
Certificates).
Figure 3-42: Certificates Signing Request Page
4. In the 'Subject Name' field, enter the DNS name, and then click Generate CSR. A
textual certificate signing request that cont ai ns the SSL device identifier is displayed.
5. Copy this text and send it to your security provider. The security provider (also known
as Certification Authority or CA) signs this request and then sends you a server
certificate for the device.
6. Save the certificate to a file (e.g., cert.txt). Ensure that the file is a plain-text file
containing the ‘BEGIN CERTIFICATE’ header, as shown in the example of a Base64Encoded X.509 Certificate below:
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 certificate has successfully loaded, save the configuration (see ''Saving
Configuration'' on page 197) and restart the device; the Web interface uses the
provided certificate.
9. If the device was originally operating in HTTPS mode and you disabled it in Step 2,
then return it to HTTPS by setting the parameter 'Secured Web Connection (HTTPS)'
to 'HTTPS Only' (1) - see ''Configuring Web Secu rity Settings'' on page 69.
Version 6.2 63 February 2011
Page 64
Mediant 600 & Mediant 1000
Notes:
•The certificate replacement process can be repeated when necessary
(e.g., the new certificate expires).
•It is possible to use the IP address of the device (e.g. , 10.3.3.1) instead
of a qualified DNS name in the Subject Name. This is not recommended
since the IP address is subject to changes and may not uniquely identify
the device.
•The server certificate can also be loaded via ini file using the parameter
HTTPSCertFileName.
To apply the loaded certificate for IPSec negotiations:
1. Open the ‘IKE Table’ page (see Configuring the IP Security Proposal Table on page
92); the 'Loaded Certificates Files' group lists the newly uploaded certificates, as
shown below:
Figure 3-43: IKE Table Listing Loaded Certificate Files
2. Click the Apply button to load the certificates; future IKE negotiations are now
performed using the new certificates.
3.3.1.5.2 Client Certificates
By default, Web servers using SSL provide one-way authentication. The client is certain
that the information provided by the Web server is authentic. When an organizational PKI is
used, two-way authentication may be desired: both client and server should be
authenticated using X.509 certificates. This is achieved by installing a client certificate on
the managing PC, and loading the same certificate (in base64-encoded X.509 format) to
the device's Trusted Root Certificate Store. The Trusted Root Certificate file should contain
both the certificate of the authorized user and the certificate of the CA.
Since X.509 certificates have an expiration date and time, the device must be configured to
use NTP (see ''Simple Network Time Protocol Support'' on page 403) to obtain the current
date and time. Without the correct date and tim e, client certificates cannot work.
SIP User's Manual 64 Document #: LTRT-83308
Page 65
SIP User's Manual 3. Web-Based Management
To enable two-way client certificates:
1. Set the parameter 'Secured Web Connection (HTTPS)' to 'HTTPS Only' (0) in
''Configuring Web Security Settings'' on page 69 to ensure you have a method of
accessing the device in case the client certificate doesn’t work. Restore the previous
setting after testing the configuration.
2. Open the ‘Certificates Signing Request' page (see ''Server Certificate Replacement''
on page 62).
3. In the 'Certificates Files' group, click the Browse button corresponding to 'Send
"Trusted Root Certificate Store" file ...', navigate to the file, and then click Send File.
4. When the operation is complete, set the HTTPSRequireClientCertificate ini file
parameter to 1.
5. Save the configuration (see ''Saving Configuration'' on page 197), and then restart the
device.
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 p rompted 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 f or a password (thus, providing a single-signon experience - the authentication is performed using the X.509 digital signature).
If the user doesn’t have a client certificate from a listed CA, or doesn’t have a client
certificate at all, the connection is rejected.
Notes:
•The process of installing a client certifica te on your PC is beyond the
scope of this document. For more information, refer to your Web browser
or operating system documentation, and/ or consult your security
administrator.
•The root certificate can also be loaded via ini file using the parameter
HTTPSRootFileName.
•You can enable Online Certificate Status Protocol (OCSP) on the device
to check whether a peer's certificate has been revoked by an OCSP
server. For further information, refer to the Prod uct Reference Manual.
3.3.1.5.3 Self-Signed Certificates
The device is shipped with an operational, self-signed server certificate. The subject name
for this default certificate is 'ACL_nnnnnnn', where nnnnnnn denotes the serial number of
the device. However, this subject name may not be appropriate for production and can be
changed while still using self-signed certifi cates.
To change the subject name and regenerate the self-signed certificate:
1. Before you begin, ensure the following:
•You have a unique DNS name for the device (e.g.,
dns_name.corp.customer.com). This na m e i s used to access the device and
should therefore, be listed in the server certificate.
•No traffic is running on the device. The certif icate generation process is disruptive
to traffic and should be executed during mai ntenance time.
2. Open the ‘Certificates’ page (see ''Server Certificate Replacement'' on page 62).
Version 6.2 65 February 2011
Page 66
Mediant 600 & Mediant 1000
only access level is typically applied to
3. In the 'Subject Name' field, enter the fully-qualified DNS name (FQDN) as the
certificate subject, and then click Generate Self-signed; after a few seconds, a
message appears displaying the new subject nam e.
4. Save configuration (see ''Saving Configuration'' on page 197), and then restart the
device for the new certificate to take effect.
3.3.1.6 Management Settings
The Management submenu includes the following:
WEB User Accounts item (see ''Configuring Web User Accounts'' on page 66)
Web Security Settings item (see ''Configuring Web Security Settings'' on p age 69)
Telnet/SSH Settings item (see ''Configuring Telnet and SSH Settings'' on page 69)
WEB & Telnet Access List item (see ''Configuring Web and Telnet Access List'' on
page 70)
RADIUS Settings item (see ''Configuring RADIUS Settings'' on page 71)
3.3.1.6.1 Configuring Web User Accounts
SNMP settings submenu (see ''SNMP Settings'' on page 71)
To prevent unauthorized access to the Web interface, two Web user accounts are available
(primary and secondary) with assigned user name, password, and access level. When you
login to the Web interface, you are requested to provide the user name and password of
one of these Web user accounts. If the Web session is idle (i.e., no actions are performed)
for more than five minutes, the Web session expires and you are once again requested to
login with your user name and password. Up to five Web users can simultaneously open
(log in to) a session on the device's Web int erf ace.
Each Web user account is composed of three attributes:
User name and password: enables access (login) to the Web interface.
Access level: determines the extent of the access (i.e., availability of pages and read
/ write privileges). The available access l evels and their corresponding privileges are
listed in the table below:
Table 3-6: Web User Accounts Access Levels and Privileges
Access Level
Security Administrator
Administrator
User Monitor
Numeric
Representation*
Privileges
200 Read / write privileges for all pages.
100
read / write privileges for all pages except
security-related pages, which ar e read-only.
No access to security-related and file-loading
50
pages; read-only access to the other pages.
This readthe secondary Web user account.
No Access
0 No access to any page.
* The numeric representation of the access level i s used only to define accounts in a RADIUS server
(the access level ranges from 1 to 255).
SIP User's Manual 66 Document #: LTRT-83308
Page 67
SIP User's Manual 3. Web-Based Management
The default attributes for the two Web user accounts are shown in the following table:
Table 3-7: Default Attributes for the Web User Accounts
Account / Attribute User Name
(Case-Sensitive)
Primary Account
Secondary Account
Admin Admin Security Administrator
User User User Monitor
Password
(Case-Sensitive)
Access Level
Note: The Access Level cannot
be changed for this account type.
To change the Web user accounts attributes:
1. Open the 'Web User Accounts' page (Configuration tab > System menu > Web User
Accounts).
Figure 3-44: WEB User Accounts Page (for Users with 'Security Administrator' Privileges)
Note: If you are logged into the Web interface as the Security Administrator, both Web
user accounts are displayed on the 'Web User Ac counts' page (as shown above). If
you are logged in with the secondary user account, only the details of the secondary
account are displayed on the page.
2. To change the access level of the secondary account:
a. From the 'Access Level' drop-down list, select the new access level.
b. Click Change Access Level; the new access level is applied im mediately.
Version 6.2 67 February 2011
Page 68
Mediant 600 & Mediant 1000
Notes:
•The access level of the primary Web user account is 'Security
Administrator', which cannot be modified.
•The access level of the secondary account can o nl y be modified by the
primary account user or a secondary account user with 'Security
Administrator' access level.
3. To change the user name of an account, perform the following:
a. In the field 'User Name', enter the new user name (maximum of 19 case-sensitive
characters).
b. Click Change User Name; if you are currently logged into the Web interface with
this account, the 'Enter Network Password' dial og box appears, requesting you to
enter the new user name.
4. To change the password of an account, perform the following:
a. In the field 'Current Password', enter the current password.
b. In the fields 'New Password' and 'Confirm New Password', enter the new
password (maximum of 19 case-sensiti ve characters).
c. Click Change Password; if you are currently logged into the Web interface with
this account, the 'Enter Network Password' dial og box appears, requesting you to
enter the new password.
Notes:
•For security, it's recommended that you change the default user name
and password.
•A Web user with access level 'Security Administrat or' can change all
attributes of all the Web user accounts. Web users with an access level
other than 'Security Administrator' can only change their own password
and user name.
•To reset the two Web user accounts' user names and passwords to
default, set the ini file parameter ResetWebPassword to 1.
•To access the Web interface with a different account, click the Log off
button located on the toolbar, click any button or page item, and then reaccess the Web interface with a different user name and password.
•You can set the entire Web interface to read-only (re gardless of Web
user account's access level), by using the ini fi le parameter
DisableWebConfig (see ''Web and Telnet Parameters'' on page 513).
•Access to the Web interface can be disabled, by setting the ini file
parameter DisableWebTask to 1. By default, acc ess is enabled.
•You can define additional Web user accounts using a RADIUS server
(refer to the Product Reference Manual).
•For secured HTTP connection (HTTPS), refer to t he Product Reference
Manual.
SIP User's Manual 68 Document #: LTRT-83308
Page 69
SIP User's Manual 3. Web-Based Management
3.3.1.6.2 Configuring Web Security Settings
The 'WEB Security Settings' page is used to define a secure Web access communication
method. For a description of these parameters, see ''Web and Telnet Parameters'' on page
513.
To define Web access security:
1. Open the 'WEB Security Settings' page (Configuration tab > System menu >
Management submenu > WEB Security Settings).
Figure 3-45: WEB Security Settings Page
2. Configure the parameters as required.
3. Click the Submit button to save your changes.
4. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
3.3.1.6.3 Configuring Telnet and SSH Settings
The 'Telnet/SSH Settings' page is used to define Telnet and Secure Shell (SSH). For a
description of these parameters, see ''Web and Tel net Parameters'' on page 513.
To define Telnet and SSH:
1. Open the 'Telnet/SSH Settings' page (Configuration tab > System menu >
Management submenu > Telnet/SSH Settings).
Figure 3-46: Telnet/SSH Settings Page
2. Configure the parameters as required.
3. Click the Submit button to save your changes.
4. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
Version 6.2 69 February 2011
Page 70
Mediant 600 & Mediant 1000
3.3.1.6.4 Configuring Web and Telnet Access List
The 'Web & Telnet Access List' page is used to define IP addresses (up to ten) that are
permitted to access the device's Web, Telnet, and SSH interfaces. Access from an
undefined IP address is denied. If no IP addresses are defined, this security feature is
inactive and the device can be accessed from any IP address. The Web and Telnet Access
List can also be defined using the ini file parameter WebAccessList_x (see ''Web and
Telnet Parameters'' on page 513).
To add authorized IP addresses for Web, Telnet, and SSH interfaces access:
1. Open the 'Web & Telnet Access List' page (Configuration tab > System menu >
Management submenu > Web & Telnet Access List).
Figure 3-47: Web & Telnet Access List Page - Add New Entry
2. To add an authorized IP address, in the 'Add an authorized IP address' field, enter the
required IP address, and then click Add New Entry; the IP address you entered is
added as a new entry to the 'Web & Telnet Access List' table.
Figure 3-48: Web & Telnet Access List Table
3. To delete authorized IP addresses, select the Delete Row check boxes corresponding
to the IP addresses that you want to delete, and then click Delete Selected
Addresses; the IP addresses are removed from the table and these IP addresses can
no longer access the Web and Telnet interfaces.
4. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
Notes:
•The first authorized IP address in the list must be your PC's (terminal) IP
address; otherwise, access from your PC is denied.
SIP User's Manual 70 Document #: LTRT-83308
•Delete your PC's IP address last from the 'Web & Tel net Access List'
page. If it is deleted before the last, subsequent access to the device
from your PC is denied.
Page 71
SIP User's Manual 3. Web-Based Management
3.3.1.6.5 Configuring RADIUS Settings
The 'RADIUS Settings' page is used for configuring the Remote Authentication Dial In User
Service (RADIUS) accounting parameters. For a description of these parameters, see
''Configuration Parameters Reference'' on page 501.
To configure RADIUS:
1. Open the ‘RADIUS Settings' page (Configuration tab > System menu >
Management submenu > RADIUS Settings).
Figure 3-49: RADIUS Parameters Page
2. Configure the parameters as required.
3. Click the Submit button to save your changes.
4. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
3.3.1.6.6 SNMP Settings
The SNMP submenu includes the following items:
SNMP Community Settings (see ''Configuring SNMP Community Strings'' on pa ge 71)
SNMP Trap Destinations (see ''Configuring SNMP Trap Destinations'' on page 73)
SNMP Trusted Managers (see ''Configuring SNMP Trusted Managers'' on page 74)
SNMP V3 Users (see ''Configuring SNMP V3 Users'' on page 74)
3.3.1.6.6.1 Configuring 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. For detailed information on SNMP community strings, refer to the
Product Reference Manual. For detailed description on the SNMP parameters, see ''SNMP
Parameters'' on page 534.
Version 6.2 71 February 2011
Page 72
Mediant 600 & Mediant 1000
To configure the SNMP community strings:
1. Open the 'SNMP Community String' page (Maintenance tab > System menu >
Management submenu > SNMP submenu > SNMP Community String).
Figure 3-50: RADIUS Parameters Page
2. Configure the SNMP community strings parameters according to the table below.
3. Click the Submit button to save your changes.
4. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
To delete a community string, select the Delete check box corresponding to the community
string that you want to delete, and then click Submit.
Table 3-8: SNMP Community String Parameters Description
Parameter Description
Community String
Trap Community String
[SNMPTrapCommunityString]
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 charact ers each).
The default string is 'private'.
Community string used in traps (up to 19 charact ers).
The default string is 'trapuser'.
SIP User's Manual 72 Document #: LTRT-83308
Page 73
SIP User's Manual 3. Web-Based Management
IP address of the remote host used as an SNMP M anager.
3.3.1.6.6.2 Configuring SNMP Trap Destinations
The 'SNMP Trap Destinations' page allows you to configure up to five SNMP trap
managers.
To configure SNMP trap destinations:
1. Open the 'SNMP Trap Destinations' page (Maintenance tab > System menu >
The device sends SNMP traps to these IP addresses.
Enter the IP address in dotted-decimal notation, e.g.,
108.10.1.255.
Trap Port
[SNMPManagerTrapPort_x]
Trap Enable
[SNMPManagerTrapSendingEnable_x]
Version 6.2 73 February 2011
Defines the port number of the remote SNMP M anager.
The device sends SNMP traps to these ports.
The valid SNMP trap port range is 100 to 4000. The
default port is 162.
Activates or de-activates the sending of traps to the
corresponding SNMP Manager.
[0] Disable = Sending is disabled.
[1] Enable = Sending is enabled (default).
Page 74
Mediant 600 & Mediant 1000
3.3.1.6.6.3 Configuring SNMP Trusted Managers
The 'SNMP Trusted Managers' page allows you to configure up to five SNMP Trusted
Managers, based on IP addresses. By default, the SNMP agent accepts SNMP Get and
Set requests from any IP address, as long as the correct community string is used in the
request. Security can be enhanced by using Trusted Managers, which is an IP address
from which the SNMP agent accepts and process es SNMP requests.
To configure SNMP Trusted Managers:
1. Open the 'SNMP Trusted Managers' page (Maintenance tab > System menu >
Authentication key. Keys can be entered in the form of a text
password or long hex string. Keys are always per sist ed as long hex
strings and keys are localized.
Privacy key. Keys can be entered in the form of a text password or
long hex string. Keys are always persisted as lon g hex strings and
keys are localized.
Group
[SNMPUsers_Group]
The group with which the SNMP v3 user is associated.
The VoIP menu includes the following main submenus:
Network (see ''Network'' on page 76)
TDM (see TDM on page 87)
Security (see ''Security'' on page 88)
PSTN (see PSTN on page 96)
Media (see ''Media'' on page 102)
Services (see Configuring LDAP Settings on page 109)
Applications Enabling (see Enabling Applications on page 110)
Control Network (see ''Control Network'' on page 111)
SIP Definitions (see ''SIP Definitions'' on page 125)
Coders And Profiles (see ''Coders and Profiles'' on page 132)
GW and IP to IP (see ''GW and IP to IP'' on page 139)
SAS (see SAS on page 188)
IP Media (see IP Media on page 193)
3.3.2.1 Network
The Network Settings submenu includes the followi ng items:
IP Settings (see ''Configuring IP Interface Settings'' on page 76)
IP Routing Table(see ''Configuring the IP Routing Table'' on page 80)
QoS Settings (see ''Configuring QoS Settings'' on page 82)
3.3.2.1.1 Configuring IP Interface Settings
DNS (see ''DNS'' on page 84)
The 'Multiple Interface Table' page allows you to configure up to 16 (up to 15 Control/Media
interfaces and a single OAMP interface) logical network interfaces. Each interface can be
defined with its own IP address, unique VLAN ID, arbitrary interface name, default
gateway, and one of the following applicati on types permitted on the interface:
Control - call control signaling traffic (i.e., SIP)
Media - RTP traffic
Operations, Administration, Maintenance and Provisioning (OAMP) - management
(such as Web- and SNMP-based management)
This page also provides VLAN-related parameters for enabling VLANs and defining the
'Native' VLAN ID (i.e., VLAN ID to which incoming, untagged packets are assigned). For
assigning VLAN priorities and Differentiated Services (DiffServ) for the supported Class of
Service (CoS), see Configuring the QoS Settings on page 82.
SIP User's Manual 76 Document #: LTRT-83308
Page 77
SIP User's Manual 3. Web-Based Management
Notes:
•For a detailed description and examples of network interfaces
configuration, see ''Network Configuration'' on page 404.
•When adding more than one interface, ensure that you enable VLANs
using the 'VLAN Mode' (VlANMode) parameter.
•When booting using BootP/DHCP protocols (see 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. The address specified in
this table takes effect only after you save t he conf i guration to the device's
flash memory. This enables the device to use a t em porary IP address for
initial management and configuration, while retaining the address
(defined in this table) for deployment.
•You can define firewall rules (access list) to deny (block) or permit (allow)
packets received from a specific IP interface configured in this table.
These rules are configured using the AccessList parameter (see
Configuring the Access List).
•You can view currently active configured IP interfaces in the 'IP Active
Interfaces' page (see ''Viewing Active IP Interfaces'' on page 212).
•You can also configure this table using the ini file t abl e parameter
InterfaceTable (see ''Networking Parameters'' on pag e 501).
•For an explanation on configuring Web interfac e tables, see ''Working
with Tables'' on page 38.
To configure IP network interfaces:
1. Open the 'IP Settings ' page (Configuration tab > VoIP menu > Network submenu >
IP Settings).
Figure 3-54: IP Settings Page
Note: The IP Settings page appears only on initial configuration (i.e., IP interfaces
have never been configured) or after the device is restored to default settings.
If you have already configured IP interfaces, then the Multiple Interface Table
page appears instead, as shown in Step 3.
Version 6.2 77 February 2011
Page 78
Mediant 600 & Mediant 1000
[3] OAMP + Media = Only OAMP and Media applicati ons
2. Under the 'Multiple Interface Settings' group, click the Multiple Interface Table
button; a confirmation message box appears:
Figure 3-55: Confirmation Message for Accessing the Multiple Interface Table
3. Click OK to confirm; the 'Multiple Interface Table' page appears:
Figure 3-56: Multiple Interface Table
4. In the 'Add Index' field, enter the desired index number for the new interface, and then
click Add Index; the index row is added to the table.
5. Configure the interface according to the table below.
6. Click the Apply button; the interface is added to the table and the Done button
appears.
7. Click Done to validate the interface. If the interface is not valid (e.g., if it overlaps with
another interface in the table or if it does not adhere to the other rules as summarized
in ''Multiple Interface Table Configuration Summary and Guidelines'' on page 411), a
warning message is displayed.
8. Save the changes to flash memory and reset the device (see ''Saving Configuration''
on page 197).
To view network interfaces that are currently active, click the IP Interface Status Table
button. For a description of this display, see ''Viewing Active IP Interfaces'' on page
The IPv4 IP address in dotted-decimal notation.
Notes:
Each interface must be assigned a unique IP address.
When booting using BootP/DHCP protocols, an IP address
is obtained from the server. This address is used as the
OAMP address for the initial session, overri di ng the
address configured using the InterfaceTable. The address
configured for OAMP applications in this tabl e becomes
available when booting from flash again. This enables the
device to operate with a temporary addres s for initial
management and configuration while retaining t he address
to be used for deployment.
Defines the Classless Inter-Domain Routing (CIDR)-style
representation of a dotted decimal subnet not ation. The CIDRstyle representation uses a suffix indicat ing the number of bits
which are set in the dot
is synonymous with 192.168.0.0 and a subnet of 255.255.0.0.
Defines 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).
The prefix length is a Classless Inter-Domain Routing (CIDR)
style presentation of a dotted-decimal subnet notation. The
CIDR-style presentation is the latest method for interpretation
of IP addresses. Specifically, instead of using ei ght-bit address
blocks, it uses the variableallow allocation on arbitrary-length prefi xes (refer to
http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing
Version 6.2 79 February 2011
Page 80
Mediant 600 & Mediant 1000
For IPv4 Interfaces, the prefix length values range from 0 to
Parameter Description
31.
Note: Subnets of different interfaces must not overlap in any
way (e.g., defining two interfaces with 10. 0.0.1/8 and
10.50.10.1/24 is invalid). Each interface must have its own
address space.
Web/EMS: Gateway
[InterfaceTable_Gateway]
Web/EMS: VLAN ID
[InterfaceTable_VlanID]
Web/EMS: Interface Name
[InterfaceTable_InterfaceName]
Defines the IP address of the default gateway for t hi s
interface.
Notes:
A default gateway can be defined for each interface.
The default gateway's IP address must be in the same
subnet as the interface address.
Defines the VLAN ID for each interface. Incoming traffic with
this VLAN ID is routed to the corresponding interf ace and
outgoing traffic from that interface is tagged wit h this VLAN ID.
Notes:
The VLAN ID must be unique for each interface.
VLANs are available only when booting the device from
flash. When booting using BootP/DHCP proto cols, VLANs
are disabled to allow easier maintenance access. In this
scenario, multiple network interface capabilities are not
available.
Defines a string (up to 16 characters) to name this interface.
This name is displayed in management interf aces (Web, CLI
and SNMP) for clarity (and has no functional u se), as well as
in the 'SIP Media Realm' and 'SIP Interface' tables.
Notes:
This parameter is mandatory.
The name must be unique for each interface.
General Parameters
VLAN Mode
[VlANMode]
Native VLAN ID
[VLANNativeVlanID]
For a description of this parameter, see Networking
Parameters on page 501.
For a description of this parameter, see Networking
Parameters on page 501.
3.3.2.1.2 Configuring the IP Routing Table
The 'IP Routing Table' page allows you to define up to 30 static IP routing rules for the
device. These rules can be associated with a network interface (defined in the Multiple
Interface table) and therefore, the routing decision is based on the source subnet/VLAN. If
not associated with an IP interface, the static IP rule is based on destination IP address.
Before sending an IP packet, the device searches this table for an entry that matches the
requested destination host/network. If such an entry is found, the device sends the packet
to the indicated router. If no explicit entry is found, the packet is sent to the default gateway
(see Configuring IP Interface Settings on page 76).
SIP User's Manual 80 Document #: LTRT-83308
Page 81
SIP User's Manual 3. Web-Based Management
To configure static IP routing:
1. Open the 'IP Routing Table' page (Configuration tab > VoIP menu > Network
submenu > IP Routing Table).
Figure 3-57: IP Routing Table Page
2. In the 'Add a new table entry' table, 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.
To delete a routing rule from the table, select the 'Delete Row' check box corresponding to
the required routing rule, and then click Delete Sel ected Entries.
Notes:
• You can delete only inactive routing rules.
Parameter Description
Destination IP Address
[StaticRouteTable_Destination]
Prefix Length
[StaticRouteTable_PrefixLength]
The address of the host/network you want to reach is determined by an AND operation that is applied
to the fields 'Destination IP Address' and 'Destination Mask'. For example, to reach the network
10.8.x.x, enter 10.8.0.0 in the field 'Destination IP Address' and 255 .255.0.0 in the field 'Destination
Mask'. As a result of the AND operation, the value of the last two octets in the field 'Destination IP
Address' is ignored.
To reach a specific host, enter its IP address in the field 'Destination IP Address' and
255.255.255.255 in the field 'Destination M ask'.
•You can also configure the IP Routing table using the ini file table
parameter StaticRouteTable.
Table 3-12: IP Routing Table Description
Specifies the IP address of the destination ho st /network.
Specifies the subnet mask of the destination host/network.
Version 6.2 81 February 2011
Page 82
Mediant 600 & Mediant 1000
Associates this routing rule with a network interface. This value
Parameter Description
Gateway IP Address
[StaticRouteTable_Gateway]
The IP address of the router (next hop) to which the packets
are sent if their destination matches the rules in the adjacent
columns.
Note: The Gateway address must be in the same subnet as
the IP address of the interface over which you configure this
static routing rule.
Metric The number of hops needed to get to the specified destination.
Note: The recommended value for this parameter is 1. This
parameter must be set to a number greater than 0 for the
routing rule to be valid. Routing entries wit h Hop Count equals
0 are local routes set automatically by the device..
Interface
[StaticRouteTable_InterfaceName]
is the index of the network interface as defined i n the Multiple
Interface table (see ''Configuring IP Interface S ettings'' on
page 76).
Note: The IP address of the 'Gateway IP Address' field must
be in the same subnet as this interface's IP addres s.
Status Read-only field displaying the statu s of the static IP route:
"Active" - routing rule is used ny the device
"Inactive" - routing rule is not applied
3.3.2.1.3 Configuring QoS Settings
The 'QoS Settings' page is used for configuring the Layer-2 and Layer-3 Quality of Service
(QoS) parameters. DiffServ is an architecture providing different types or levels of service
for IP traffic. DiffServ (according to RFC 2474), prioritizes certain traffic types based on
their priority, thereby, accomplishing a higher-level QoS at the expense of other traffic
types. By prioritizing packets, DiffServ routers can minimize transmission delays for timesensitive packets such as VoIP packets.
This page allows you to assign different VLAN priorities (IEEE 802.1p) and Differentiated
Services (DiffServ) to the supported Class of Service (CoS) - Network, Media Premium,
Control Premium, Gold, and Bronze. For a detailed description of the parameters
appearing on this page, see ''Networking Parameters'' on page 501. For a description on
QoS and the mapping of each application to a class of service, see ''Quality of Service
Parameters'' on page 408.
SIP User's Manual 82 Document #: LTRT-83308
Page 83
SIP User's Manual 3. Web-Based Management
To configure QoS:
1. Open the 'QoS Settings' page (Configuration tab > VoIP menu > Network submenu
> QoS Settings).
Figure 3-58: QoS Settings Page
2. Configure the QoS parameters as required.
3. Click the Submit button to save your changes.
4. Save the changes to flash memory (see ''Saving Configuration'' on page 197).
Version 6.2 83 February 2011
Page 84
Mediant 600 & Mediant 1000
3.3.2.1.4 DNS
The DNS submenu includes the following items:
DNS Settings (refer to ''Configuring DNS Settings'' on page 84)
Internal DNS Table (refer to ''Configuring the Internal DNS Table'' on page 85)
Internal SRV Table (refer to ''Configuring the Internal SRV Table'' on page 86)
3.3.2.1.4.1 Configuring DNS Settings
The 'DNS Settings' page defines the VoIP Domain Name System (DNS) server IP
addresses.
Note: For a detailed description of the DNS parameters, refer to ''DNS Parameters''
on page 510.
To define the DNS server:
1. Open the 'DNS Settings' page (Configuration tab > VoIP menu > Network submenu
> DNS submenu > DNS Settings).
Figure 3-59: DNS Settings Page
2. In the 'DNS Primary Server IP' field, enter the IP address of the primary DNS server
(in dotted-decimal notation, for example, 10. 8.2.255).
3. Optionally, in the 'DNS Secondary Server IP', enter the IP address of the second DNS
server (in dotted-decimal notation).
4. Click the Submit button to apply your changes.
5. Save the changes to flash memory (refer to ''Saving Configuration'' on page 197).
SIP User's Manual 84 Document #: LTRT-83308
Page 85
SIP User's Manual 3. Web-Based Management
3.3.2.1.4.2 Configuring the Internal DNS Table
The 'Internal DNS Table' page, similar to a DNS resolution translates up to 20 host
(domain) names into IP addresses (e.g., when using the 'Outbound IP Routing Table' for
Tel-to-IP call routing). Up to four different IP addresses can be assigned to the same host
name (typically used for alternative Tel-to-IP call ro uting).
Notes:
•The device initially attempts to resolve a domai n name using the Internal
DNS table. If the domain name isn't listed in the table, the device
performs a DNS resolution using an external DNS server (defined in
''Configuring DNS Settings'' on page 84).
•You can also configure the DNS table using the ini file table parameter
DNS2IP (see ''DNS Parameters'' on page 510).
To configure the internal DNS table:
1. Open the 'Internal DNS Table' page (Configuration tab > VoIP menu > Network
submenu > DNS submenu > Internal DNS Table).
Figure 3-60: Internal DNS Table Page
2. In the 'Domain Name' field, enter the host name to be translated. You can enter a
string of up to 31 characters.
3. In the 'First IP Address' field, enter the first IP address (in dotted-decimal format
notation) to which the host name is translated.
4. Optionally, in the 'Second IP Address', 'Third IP Address', and 'Second IP Address'
fields, enter the next IP addresses to which the h ost name is translated.
5. Click the Submit button to save your changes.
6. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
Version 6.2 85 February 2011
Page 86
Mediant 600 & Mediant 1000
3.3.2.1.4.3 Configuring the Internal SRV Table
The 'Internal SRV Table' page resolves host names to DNS A-Records. Three different ARecords 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. I f t he dom ain name isn't found,
the device performs an Service Record (SRV) resolution using an
external DNS server (defined in ''Configuring DNS Sett ings'' on page 84).
•You can also configure the Internal SRV table usi ng the ini file table
parameter SRV2IP (see ''DNS Parameters'' on page 510).
To configure the Internal SRV table:
1. Open the 'Internal SRV Table' page (Configuration tab > VoIP menu > Network
submenu > DNS submenu > Internal SRV Table).
Figure 3-61: Internal SRV Table Page
2. In the 'Domain Name' field, enter the host name to be translated. You can enter a
string of up to 31 characters.
3. From the 'Transport Type' drop-down list, select a transport type.
4. In the 'DNS Name 1' field, enter the first DNS A-Record to which the host name is
translated.
5. In the 'Priority', 'Weight' and 'Port' fields, enter the relevant values
6. Repeat steps 4 through 5, for the second and third DNS names, if required.
7. Repeat steps 2 through 6, for each entry.
8. Click the Submit button to save your changes.
9. To save the changes so they are available after a hardware reset or power fail, see
''Saving Configuration'' on page 197.
SIP User's Manual 86 Document #: LTRT-83308
Page 87
SIP User's Manual 3. Web-Based Management
3.3.2.2 TDM
The TDM submenu contains the following item:
TDM (see ''Configuring TDM Bus Settings'' on page 87)
3.3.2.2.1 Configuring TDM Bus Settings
The 'TDM Bus Settings' page allows you to configure the device's Time-Division
Multiplexing (TDM) bus settings. For detailed information on configuring the device's clock
settings, see ''Clock Settings'' on page 421. For a description of these parameters, see
''Configuration Parameters Reference'' on page 501.
To configure the TDM Bus settings:
1. Open the 'TDM Bus Settings' page (Configuration tab > VoIP menu > TDM submenu
> TDM Bus Settings).
Figure 3-62: TDM Bus Settings Page
2. Configure the parameters as required.
3. Click the Submit button to save your changes.
4. Save the changes to flash memory, see ''Saving Configuration'' on page 197.
Version 6.2 87 February 2011
Page 88
Mediant 600 & Mediant 1000
3.3.2.3 Security
The Security Settings submenu allows you to configure various security settings. This
menu contains the following page items:
Firewall Settings (see ''Configuring Firewall Settings'' on page 88)
General Security Settings (see ''Configuring General Security Set tings'' on page 92)
IPSec Proposal Table (see Configuring IP Security Associations Table on page 94)
3.3.2.3.1 Configuring Firewall Settings
IPSec Association Table (see Configuring IP Security Proposal Tab l e on page 92)
The device provides an internal firewall, allowing you (the security administrator) to define
network traffic filtering rules. You can ad d up to 50 ordered firewall rules.
The access list provides the following firewall rul es:
Block traffic from known malicious sources
Only allow traffic from known friendly sources, and block all others
Mix allowed and blocked network sources
Limit traffic to a pre-defined rate (blocking the excess)
Limit traffic to specific protocols, and specific port ranges on the device
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.
Once a rule in the table is located, subsequent rules further down the table are ignored. If
the end of the table is reached without a match, the packet is accepted. For detailed
information on the internal firewall, refer to the Product Reference Manual.
Notes:
•It is recommended to add a rule at the end of your table that blocks all
traffic and add firewall rules above it (in the tabl e) that allow traffic (with
bandwidth limitations). To block all traffic, the following must be set:
- IP address to 0.0.0.0
- Prefix length of 0 (implies the rule can match any I P address)
- Local port range 0-65535
- Protocol "Any"
- Action Upon Match "block"
•You can also configure the firewall settings u sing the ini file table
parameter AccessList (see ''Security Parameters'' on page 524).
SIP User's Manual 88 Document #: LTRT-83308
Page 89
SIP User's Manual 3. Web-Based Management
To add firewall rules:
1. Open the 'Firewall Settings' page (Configuration tab > VoIP menu > Security
submenu > Firewall Settings).
Figure 3-63: Firewall Settings Page
2. In the 'Add' field, enter the index of the access rule that you want to add, and then
click Add; a new firewall rule index appears in the table.
3. Configure the firewall rule's parameters according to the table below.
4. Click one of the following buttons:
• Apply: saves the new rule (without activating it).
• Duplicate Rule: adds a new rule by copying a selected rule.
• Activate: saves the new rule and activates it.
• Delete: deletes the selected rule.
5. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
The previous figure shows the following access list settings:
Rule #1: traffic from the host 'mgmt.customer.com' destined to TCP ports 0 to 80, is
always allowed.
Rule #2: traffic from the 192.xxx.yyy.zzz subnet, is limited to a rate of 40 Kbytes per
second (with an allowed burst of 50 Kbytes). Note that the rate is specified in bytes,
not bits, per second; a rate of 40000 bytes per second, nominally corresponds to 320
kbps.
Rule #3: traffic from the subnet 10.31.4.xxx destined to ports 4000-9000 is always
blocked, regardless of protocol.
Rule #4: traffic from the subnet 10.4.xxx.yyy destined to ports 4 000-900 0 i s always
blocked, regardless of protocol.
All other traffic is allowed
To edit a rule:
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, see ''Saving Configuration'' on page 197.
To activate a de-activated rule:
1. In the 'Edit Rule' column, select the de-activated rule that you want to activate.
2. Click the Activate button; the rule is activated.
To de-activate an activated rule:
1. In the 'Edit Rule' column, select the activated rule that you want to de-activate.
2. Click the DeActivate button; the rule is de-activated.
Version 6.2 89 February 2011
Page 90
Mediant 600 & Mediant 1000
TCP or UDP protocols, and the appropriat e port numbers as
To delete a rule:
1. Select the radio button of the entry you want to activate.
2. Click the Delete Rule button; the rule is deleted.
3. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
Table 3-13: Internal Firewall Parameters
Parameter Description
Rule Status A read-only field indicating whether the rule is active or not.
Note: After device reset, all rules are active.
Source IP
[AccessList_Source_IP]
Prefix Length
[AccessList_PrefixLen]
Local Port Range
[AccessList_Start_Port]
[AccessList_End_Port]
Protocol
[AccessList_Protocol]
IP address (or DNS name) or a specific host name of the
source network (i.e., from where the incoming packet is
received).
IP network mask. 32 for a single host, or t he appropriate
value for the source IP addresses.
A value of 8 corresponds to IPv4 subnet class A
(network mask of 255.0.0.0).
A value of 16 corresponds to IPv4 subnet class B
(network mask of 255.255.0.0).
A value of 24 corresponds to IPv4 subnet class C
(network mask of 255.255.255.0).
The IP address of the sender of the incoming packet is
trimmed in accordance with the prefix length (in bits) and
then compared to the parameter ‘Source IP’ .
The destination UDP/TCP ports (on this devi ce) to which
packets are sent.
The valid range is 0 to 65535.
Note: When the protocol type isn't TCP or UDP, the entire
range must be provided.
The protocol type (e.g., UDP, TCP, ICMP, ESP or 'Any'), or
the IANA protocol number (in the range of 0 (A ny) to 255).
Note: This field also accepts the abbreviated strings 'SIP'
and 'HTTP'. Specifying these strings implies selection of the
defined on the device.
Use Specific Interface
[AccessList_Use_Specific_Interface]
Determines whether you want to apply the rule to a specific
network interface defined in the Multiple Interface table (i.e.,
packets received from that defined in the Source IP field
and received on this network interface):
[0] Disable (default)
[1] Enable
Notes:
If enabled, then in the 'Interface Name' field (described
below), select the interface to which the rule is applied.
If disabled, then the rule applies to all interfaces.
Interface Name
[AccessList_Interface_ID]
The network interface to which you want to apply the rule.
This is applicable if you enabled the 'Use Specific I nterface'
field. The list displays interface names as defi ned in the
Multiple Interface table (see ''Configurin g IP Interface
Settings'' on page 76).
SIP User's Manual 90 Document #: LTRT-83308
Page 91
SIP User's Manual 3. Web-Based Management
bytes/sec, then this allowance would be consume d within 10
Parameter Description
Packet Size
[AccessList_Packet_Size]
Byte Rate
[AccessList_Byte_Rate]
Burst Bytes
[AccessList_Byte_Burst]
Action Upon Match
[AccessList_Allow_Type]
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.
Expected traffic rate (bytes per second). T his field defines
the allowed bandwidth for the specified protocol. In addition
to this field, the 'Burst Bytes' field provides addit i onal
allowance such that momentary bursts of data m ay utilize
more than the defined byte rate, without being interrupted.
For example, if 'Byte Rate' is set to 40000 and 'B urst Bytes'
to 50000, then this implies the following: the al l owed
bandwidth is 40000 bytes/sec with extra all owance of 50000
bytes; if, for example, the actual traffic rate is 45000
seconds, after which all traffic exceeding the allocated
40000 bytes/sec is dropped. If the actual traffic rate then
slowed to 30000 bytes/sec, then the allowance would be
replenished within 5 seconds.
Tolerance of traffic rate limit (number of byt es).
Action upon match (i.e., 'Allow' or 'Block').
Match Count
[AccessList_MatchCount]
A read-only field displaying the number of packets
accepted/rejected by the specific rule.
Version 6.2 91 February 2011
Page 92
Mediant 600 & Mediant 1000
3.3.2.3.2 Configuring General Security Settings
The 'General Security Settings' page is used to configure various security features. For a
description of the parameters appearing on this page, refer ''Configuration Parameters
Reference'' on page 501.
To configure the general security parameters:
1. Open the 'General Security Settings' page (Configuration tab > VoIP menu >
Security submenu > General Security Settings).
Figure 3-64: General Security Settings Page
2. Configure the parameters as required.
3. Click the Submit button to save your changes.
4. To save the changes to flash memory, refer to ''Saving Configuration'' on page 197.
3.3.2.3.3 Configuring IP Security Proposal Table
The 'IP Security Proposals Table' page is used to configure Internet Key Exchange (IKE)
with up to four proposal settings. Each proposal defines an encryption algorithm, an
authentication algorithm, and a Diffie-Hellman group identifier. The same set of proposals
applies to both Main mode and Quick mode.
Note: You can also configure the IP Security Proposals table using the ini file table
parameter IPsecProposalTable (see ''Securit y Parameters'' on page 524).
SIP User's Manual 92 Document #: LTRT-83308
Page 93
SIP User's Manual 3. Web-Based Management
To configure IP Security Proposals:
1. Open the ‘IP Security Proposals Table’ page (Configuration tab > VoIP menu >
Security submenu > IPSec Proposal Table).
Figure 3-65: IP Security Proposals Table
In the figure above, four proposals are defined.
2. Select an Index, click Edit, and then modify the proposal as required.
3. Click Apply.
4. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
To delete a proposal, select the relevant Index num ber, and then click Delete.
Table 3-14: IP Security Proposals Table Configuration Parameters
Determines the length of the key created by the
DH protocol for up to four proposals. For the ini
file parameter, X depicts the proposal number (0
to 3).
[0] Group 1 (768 Bits) = DH-786-Bit
[1] Group 2 (1024 Bits) (default) = DH-1024-
Bit
Proposal Encryption Authentication DH Group
Proposal 0
Proposal 1
Proposal 2
Proposal 3
3DES SHA1 Group 2 (1024 bit)
3DES MD5 Group 2 (1024 bit)
3DES SHA1 Group 1 (786 bit)
3DES MD5 Group 1 (786 bit)
Version 6.2 93 February 2011
Page 94
Mediant 600 & Mediant 1000
3.3.2.3.4 Configuring IP Security Associations Table
The 'IP Security Associations Table' page allows you to configure up to 20 peers (hosts or
networks) for IP security (IPSec)/IKE. Each of the entries in the IPSec Security Association
table controls both Main Mode and Quick Mode configuration for a single peer
Note: You can also configure the IP Security Associations table using the ini file
table parameter IPsecSATable (see ''Security Parameters'' on page 524).
To configure the IPSec Association table:
1. Open the ‘IP Security Associations Table’ page (Configuration tab > VoIP menu >
Security submenu > IPSec Association Table). (Due to the length of the table, the
figure below shows sections of this table.)
Figure 3-66: IP Security Associations Table Page
2. Add an Index or select the Index rule you want to edit.
3. Configure the rule according to the table below.
4. Click Apply; the rule is applied on-the-fly.
5. To save the changes to flash memory, see ''Saving Configuration'' on page 197.
Table 3-16: IP Security Associations Table Configuration Parameters
Parameter Name Description
Operational Mode
[IPsecSATable_IPsecMode]
Remote Endpoint Addr
[IPsecSATable_RemoteEndpointAdd
ressOrName]
SIP User's Manual 94 Document #: LTRT-83308
Defines the IPSec mode of operation.
[0] Transport (default)
[1] Tunnel
Defines the IP address or DNS host name of the peer.
Note: This parameter is applicable only if the Operational
Mode is set to Transport.
Page 95
SIP User's Manual 3. Web-Based Management
Parameter Name Description
Authentication Method
[IPsecSATable_AuthenticationMetho
d]
Shared Key
[IPsecSATable_SharedKey]
Selects the method used for peer authenticat i on during IKE
main mode.
Note: For RSA-based authentication, both peers must be
provisioned with certificates signed by a common CA. For
more information on certificates see ''Server Certific ate
Replacement'' on page 62.
Defines the pre-shared key (in textual format). Both peers
must use the same pre-shared key for the authentication
process to succeed.
Notes:
This parameter is applicable only if the Authentication
Method parameter is set to pre-shared key.
The pre-shared key forms the basis of IPSec security
and therefore, it should be handled with care (t he same
as sensitive passwords). It is not recommende d to use
the same pre-shared key for several connections.
Since the ini file is plain text, loading it to the device
over a secure network connection is recommended.
Use a secure transport such as HTTPS, or a direct
crossed-cable connection from a management PC.
After it is configured, the value of the pre-shared key
cannot be retrieved.
Source Port
[IPsecSATable_SourcePort]
Destination Port
[IPsecSATable_DestPort]
Protocol
[IPsecSATable_Protocol]
IKE SA Lifetime
[IPsecSATable_Phase1SaLifetimeInS
ec]
IPSec SA Lifetime (sec)
[IPsecSATable_Phase2SaLifetimeInS
ec]
Defines the source port to which this configuration applies.
The default value is 0 (i.e., any port).
Defines the destination port to which this configuration
applies.
The default value is 0 (i.e., any port).
Defines the protocol type to which this configuration
applies. Standard IP protocol numbers, as defined by the
Internet Assigned Numbers Authority (IANA) should be
used, for example:
0 = Any protocol (default)
17 = UDP
6 = TCP
Determines the duration (in seconds) for which the
negotiated IKE SA (Main mode) is valid. A fter this time
expires, the SA is re-negotiated.
Note: Main mode negotiation is a processor-intensive
operation; for best performance, do not set t hi s parameter
to less than 28,800 (i.e., eight hours).
The default value is 0 (i.e., unlimited).
Determines the duration (in seconds) for which the
negotiated IPSec SA (Quick mode) is valid. A fter this time
expires, the SA is re-negotiated.
The default value is 0 (i.e., unlimited).
Note: For best performance, a value of 3,600 (i.e., one
hour) or more is recommended.
Version 6.2 95 February 2011
Page 96
Mediant 600 & Mediant 1000
Parameter Name Description
IPSec SA Lifetime (Kbs)
[IPsecSATable_Phase2SaLifetimeInK
B]
Dead Peer Detection Mode
[IPsecSATable_DPDmode]
Remote Tunnel Addr
[IPsecSATable_RemoteTunnelAddre
ss]
Remote Subnet Addr
[IPsecSATable_RemoteSubnetIPAdd
ress]
Determines the maximum volume of traffic (in kilobytes) for
which the negotiated IPSec SA (Quick mode) is val id. After
this specified volume is reached, the SA is re-negotiated.
The default value is 0 (i.e., the value is ignored).
Configures dead peer detection (DPD), according to RFC
3706.
[0] DPD Disabled (default)
[1] DPD Periodic = DPD is enabled with message
exchanges at regular intervals
[2] DPD on demand = DPD is enabled with on-demand
checks - message exchanges as neede d (i.e., before
sending data to the peer). If the liveliness of the peer is
questionable, the device sends a DPD message to
query the status of the peer. If the device has no traffic
to send, it never sends a DPD message.
Note: For detailed information on DPD, refer to the Product
Reference Manual.
Defines the IP address of the peer router.
Note: This parameter is applicable only if the Operational
Mode is set to Tunnel.
Defines the IP address of the remote subnet. T ogether with
the Prefix Length parameter (below), this parameter
defines the network with which the IPSec tunnel al lows
communication.
Note: This parameter is applicable only if the Operational
Mode is set to Tunnel.
Remote Prefix Length
[IPsecSATable_RemoteSubnetPrefix
Length]
Interface Name
[IPsecSATable_InterfaceName]
3.3.2.4 PSTN
The PSTN submenu allows you to configure various PSTN settings and includes the
following page items:
CAS State Machines (see ''Configuring CAS State Machines'' on page 97)
Trunk Settings (see ''Configuring Trunk Settings'' on page 99)
Defines the prefix length of the Remote Subnet IP Address
parameter (in bits). The prefix length de fines the subnet
class of the remote network. A prefix length of 16
corresponds to a Class B subnet (255.255.0.0); a prefix
length of 24 corresponds to a Class C subnet
(255.255.255.0).
Note: This parameter is applicable only if the Operational
Mode is set to Tunnel.
Associates this IPSec rule with a network interf ace that is
defined in the Multiple Interface table (Int erface Name
column) - see ''Configuring IP Interface Settings'' on page
76.
SIP User's Manual 96 Document #: LTRT-83308
Page 97
SIP User's Manual 3. Web-Based Management
3.3.2.4.1 Configuring CAS State Machines
The 'CAS State Machine' page allows you to modify various timers and other basic
parameters to define the initialization of the CAS state machine without changing the state
machine itself (no compilation is required). The change doesn't affect the state machine
itself, but rather the configuration.
The CAS table used can be chosen in two ways (using the parameter CasChannelIndex):
Single CAS table per trunk
Different CAS table per group of B-Channels in a trunk
To modify the CAS state machine parameters:
1. Open the ‘CAS State Machine' page (Configuration tab > VoIP menu > PSTN
submenu > CAS State Machines).
Figure 3-67: CAS State Machine Page
2. Ensure that the trunk is inactive. The trunk number displayed in the 'Related Trunks'
field must be green. If it is red (indicating that the trunk is active), click the trunk
number to open the 'Trunk Settings' page (see ''Configuring Trunk Settings'' on page
99), select the required Trunk number icon, and then click Stop Trunk.
3. In the 'CAS State Machine' page, modify the required parameters according to the
table below.
4. Once you have completed the configuration, activate the trunk if required in the 'Trunk
Settings' page, by clicking the trunk number in the 'Related Trunks' field, and in the
'Trunk Settings' page, select the required Trunk number icon, and then click Apply
Trunk Settings.
5. Click Submit.
6. Reset the device (see ''Resetting the Device'' on page 195).
Notes:
•Don't modify the default values unless you f ul ly understand the
implications of the changes and know the default v al ues. Every change
affects the configuration of the state machine parameters and the call
process related to the trunk you are using with t hi s state machine.
•You can modify CAS state machine parameters onl y if the following
conditions are met:
1) Trunks are inactive (stopped), i.e., the 'Related Trunks' field displays
the trunk number in green.
2) State machine is not in use or is in reset, or when it is not related to
any trunk. If it is related to a trunk, you must delete the trunk or deactivate (Stop) the trunk.
•Field values displaying '-1' indicate CAS default values. In other words,
CAS state machine values are used.
•The modification of the CAS state machine occu rs at the CAS application
initialization only for non-default values (-1).
•For a detailed description of the CAS Protocol t able, refer to the Product
Reference Manual.
Version 6.2 97 February 2011
Page 98
Mediant 600 & Mediant 1000
Table 3-17: CAS State Machine Parameters Description
Parameter Description
Generate Digit On Time
[CasStateMachineGenerateDigitOnTime]
Generate Inter Digit Time
[CasStateMachineGenerateInterDigitTime]
DTMF Max Detection Time
[CasStateMachineDTMFMaxOnDetectionTim
e]
DTMF Min Detection Time
[CasStateMachineDTMFMinOnDetectionTim
e]
MAX Incoming Address Digits
[CasStateMachineMaxNumOfIncomingAddre
ssDigits]
Generates digit on-time (in msec).
The value must be a positive value. The default
value is -1 (use value from CAS state machine).
Generates digit off-time (in msec).
The value must be a positive value. The default
value is -1 (use value from CAS state machine).
Detects digit maximum on time (accordi ng to DSP
detection information event) in msec units.
The value must be a positive value. The default
value is -1 (use value from CAS state machine).
Detects digit minimum on time (accordin g to DSP
detection information event) in msec units. T he
digit time length must be longer than this value t o
receive a detection. Any number may be used, but
the value must be less than
CasStateMachineDTMFMaxOnDetectionTime.
The value must be a positive value. The default
value is -1 (use value from CAS state machine).
Defines the limitation for the maximum address
digits that need to be collected. After reaching this
number of digits, the collection of address digits is
stopped.
The value must be an integer. The default value i s 1 (use value from CAS state machine).
MAX Incoming ANI Digits
[CasStateMachineMaxNumOfIncomingANIDi
gits]
Collet ANI
[CasStateMachineCollectANI]
Digit Signaling System
[CasStateMachineDigitSignalingSystem]
Defines the limitation for the maximum ANI digi ts
that need to be collected. After reaching this
number of digits, the collection of ANI digits is
stopped.
The value must be an integer. The default value i s 1 (use value from CAS state machine).
In some cases, when the state machine handles
the ANI collection (not related to MFCR2), you can
control the state machine to collect ANI or discard
ANI.
[0] No = Don't collect ANI.
[1] Yes = Collect ANI.
[-1] Default = Default value - use value from
CAS state machine.
Defines which Signaling System to use in both
directions (detection\generation).
[0] DTMF = Uses DTMF signaling.
[1] MF = Uses MF signaling (default).
[-1] Default = Default value - use value from
CAS state machine.
SIP User's Manual 98 Document #: LTRT-83308
Page 99
SIP User's Manual 3. Web-Based Management
3.3.2.4.2 Configuring Trunk Settings
The 'Trunk Settings' page allows you to configure the device's trunks. This includes
selecting the PSTN protocol and configuring related parameters.
Some parameters can be configured when the trunk is in service, while others require you
to take the trunk out of service (by clicking the Stop button). Once you have
"stopped" a trunk, all calls are dropped and no new calls can be made on that trunk.
You can also deactivate a trunk (by clicking the Deactivate button) for
maintenance. Deactivation temporarily disconnects (logically) the trunk from the PSTN
network. Upon trunk deactivation, the device generates an AIS alarm on that trunk to the
far-end (as a result, an RAI alarm signal may be received by the device). A subsequent
trunk activation (by clicking the Activate button), reconnects the trunk to the
PSTN network and clears the AIS alarm. Trunk deactivation is typically used for
maintenance such as checking the trunk's physical integrity.
For a description of the trunk parameters, see ''PSTN Parameters'' on page 640.
Notes:
• During trunk deactivation, trunk configur ation cannot be performed.
• A stopped trunk cannot also be activated and a t runk cannot be
deactivated if it has been stopped.
To configure the trunks:
1. Open the ‘Trunk Settings’ page (Configuration tab > VoIP menu > PSTN submenu >
Trunk Settings).
Figure 3-68: Trunk Settings Page
Version 6.2 99 February 2011
Page 100
Mediant 600 & Mediant 1000
On the top of the page, a bar with Trunk number i cons displays the status of each
trunk, according to the following color codes:
• Grey: Disabled
• Green: Active
• Yellow: RAI alarm (also appears when you deactivate a Trun k by clicking the
Deactivate button)
• Red: LOS/LOF alarm
• Blue: AIS alarm
• Orange: D-channel alarm (ISDN only)
2. 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). To
scroll through the trunk number icons (i.e., view the next/last or previous/first group of
eight trunks), refer to the figure below:
Figure 3-69: Trunk Scroll Bar (Used Only as an Example)
Note: If the Trunk scroll bar displays all available trunks, the scroll bar buttons are
unavailable.
After you have selected a trunk, the following is displayed:
•The read-only 'Module ID' field displays the m odule number to which the trunk
belongs.
• The read-only 'Trunk ID' field displays the sel ect ed trunk number.
• The read-only ‘Trunk Configuration State’ di splays the state of the trunk ('Active'
or 'Inactive').
•The displayed parameters pertain to the selected trunk only.
3. Click the Stop Trunk button (located at the bottom of the page) to take the trunk
out of service so that you can configure the currently grayed out (unavailable)
parameters. (Skip this step if you want to configure parameters that are available
when the trunk is active). The stopped trunk is indi cated by the following:
• The ‘Trunk Configuration State’ field displays ‘Inactive’.
• The Stop Trunk button is replaced by the Apply Trunk Settings button.
When all trunks are stopped, the Apply to All Trunks button also appears.
•All the parameters are available and can be modified.
4. Configure the trunk parameters as required.
SIP User's Manual 100 Document #: LTRT-83308
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.