LTRT-61405 MP-1xx Fast Track Installation Guide

MP-1xx Fast Track Installation Guide
MGCP, H.323 & SIP
Version 4.4
Document #: LTRT-61405
MP-1xx
Fast Track Installation Guide
MGCP, H.323 & SIP
Version 4.4
Document #: LTRT-61405
Published March 2005
Notice
This Fast Track Installation Guide describes the installation of the AudioCodes MP-1xx MediaPack Series VoIP
gateways applying to MGCP, H.323 and SIP versions.
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 the accuracy of printed
material after the Date Published nor can it accept responsibility for errors or omissions.
Updates to this document and other documents can be viewed by registered Technical Support customers at
www.audiocodes.com under Support / Product Documentation.
© Copyright 2005 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: Mar-01-2005
Date Printed: Mar-02-2005
Fast Track Installation Guide
Contents
Table of Contents
1
Quick Start ................................................................................................................................................. 7
2
Installing the MP-1xx ................................................................................................................................ 8
2.1 Unpacking ...........................................................................................................................................8
2.2 Package Contents ...............................................................................................................................8
2.3 Mounting the MP-1xx ..........................................................................................................................9
2.3.1
Mounting the MP-1xx on a Desktop .................................................................................... 9
2.3.2
Installing the MP-10x in a 19-inch Rack.............................................................................. 9
2.3.3
Installing the MP-124 in a 19-inch Rack ........................................................................... 10
2.3.4
Mounting the MP-10x on a Wall ........................................................................................ 11
2.4 Cabling the MP-1xx ...........................................................................................................................12
2.4.1
MP-1xx Rear Panel Connectors........................................................................................ 12
2.4.2
Cables and Cabling Procedure ......................................................................................... 13
2.4.3
Cabling the Lifeline Phone ................................................................................................ 16
3
Configuring the MP-1xx.......................................................................................................................... 18
3.1 Assigning the MP-1xx IP Address.....................................................................................................18
3.1.1
Assigning an IP Address Using HTTP .............................................................................. 18
3.1.2
Assigning an IP Address Using BootP.............................................................................. 19
3.1.3
Assigning an IP Address via the RS-232 Port .................................................................. 20
3.2 Restoring Networking Parameters to their Initial State .....................................................................21
3.3 Accessing the Embedded Web Server .............................................................................................21
3.4 Configuring the MP-1xx Basic Control Protocol Parameters ............................................................22
3.4.1
Configuring Basic MGCP Parameters............................................................................... 23
3.4.2
Configuring Basic H.323 Parameters................................................................................ 24
3.4.3
Configuring Basic SIP Parameters.................................................................................... 26
3.4.4
Example of Connecting Two MP-108 Devices.................................................................. 28
4
Changing the MP-1xx Username and Password ................................................................................. 29
5
Restoring and Backing Up the MP-1xx Configuration ........................................................................ 30
6
Monitoring the MP-1xx ........................................................................................................................... 31
6.1 Front Panel LEDs ..............................................................................................................................31
6.2 Rear Panel LEDs...............................................................................................................................32
6.3 Monitoring the MP-1xx Channels ......................................................................................................32
7
Software Update...................................................................................................................................... 33
7.1 Software Upgrade Wizard .................................................................................................................33
7.2 Updating the Auxiliary Files...............................................................................................................37
8
MP-1xx IP<->PBX Test Example ............................................................................................................ 39
9
Regulatory Information .......................................................................................................................... 40
9.1 MP-11x FXS ......................................................................................................................................40
9.2 MP-11x FXO......................................................................................................................................41
9.3 MP-124..............................................................................................................................................43
Version 4.4
3
March 2005
MP-1xx
List of Figures
Figure 1-1: Required Steps to Install the MP-1xx.............................................................................................. 7
Figure 2-1: Desktop Mounting ........................................................................................................................... 9
Figure 2-2: MP-108 with Brackets for Rack Installation .................................................................................. 10
Figure 2-3: MP-124 with Brackets for Rack Installation .................................................................................. 11
Figure 2-4: MP-102 Wall Mount....................................................................................................................... 11
Figure 2-5: MP-104/FXS Rear Panel Connectors ........................................................................................... 12
Figure 2-6: MP-124 Rear Panel Connectors ................................................................................................... 12
Figure 2-7: RJ-45 Ethernet Connector Pinout ................................................................................................. 14
Figure 2-8: RJ-11 Phone Connector Pinout .................................................................................................... 14
Figure 2-9: 50-pin Telco Connector (MP-124/FXS only) ................................................................................. 14
Figure 2-10: MP-124 in a 19-inch Rack with MDF Adaptor............................................................................. 14
Figure 2-11: DC Power Supply on the MP-124 ............................................................................................... 15
Figure 2-12: Lifeline Splitter Pinout & RJ-11 Connector for MP-10x/FXS....................................................... 16
Figure 2-13: MP-104/FXS Lifeline Setup......................................................................................................... 17
Figure 3-1: Client Configuration Screen with Blank Parameters..................................................................... 20
Figure 3-2: Embedded Web Server Login Screen .......................................................................................... 21
Figure 3-3: MP-1xx MGCP Quick Setup Screen ............................................................................................. 23
Figure 3-4: MP-1xx H.323 Quick Setup Screen .............................................................................................. 24
Figure 3-5: MP-1xx SIP Quick Setup Screen .................................................................................................. 26
Figure 3-6: Example of Connecting Two MP-108 Devices.............................................................................. 28
Figure 4-1: Change Password Screen ............................................................................................................ 29
Figure 5-1: Configuration File Screen.............................................................................................................. 30
Figure 6-1: MP-1xx/FXS Channel Status Screen............................................................................................ 32
Figure 7-1: Start Software Upgrade Screen .................................................................................................... 33
Figure 7-2: Load a cmp File Screen ................................................................................................................ 34
Figure 7-3: cmp File Successfully Loaded into the MP-1xx Notification ......................................................... 34
Figure 7-4: Load an ini File Screen ................................................................................................................. 35
Figure 7-5: Load a CPT File Screen................................................................................................................ 35
Figure 7-6: FINISH Screen .............................................................................................................................. 36
Figure 7-7: ‘End Process’ Screen.................................................................................................................... 36
Figure 7-8: Auxiliary Files Screen.................................................................................................................... 38
Figure 8-1: MP-104 IP<->PBX Test Example ................................................................................................. 39
List of Tables
Table 2-1: MP-10x Rear Panel Component Descriptions ............................................................................... 12
Table 2-2: MP-124 Rear Panel Component Descriptions ............................................................................... 12
Table 2-3: Cables and Cabling Procedure ...................................................................................................... 13
Table 2-4: Pin Allocation in the 50-pin Telco Connector ................................................................................. 15
Table 2-5: DC Power Supply on the MP-124 Component Descriptions.......................................................... 15
Table 2-6: MP-104/FXS Lifeline Setup Component Descriptions ................................................................... 17
Table 3-1: MP-1xx Default Networking Parameters ........................................................................................ 18
Table 6-1: Definition of MP-1xx Front Panel LED Indicators........................................................................... 31
Table 6-2: Definition of MP-1xx Rear Panel LED Indicators ........................................................................... 32
Table 7-1: ini and Auxiliary Files Descriptions................................................................................................. 37
MP-1xx
4
Document #: LTRT-61405
Fast Track Installation Guide
Tip:
General
When viewing this manual on CD, Web site or on any other electronic copy,
all cross-references are hyperlinked. Click on the page or section numbers
(shown in blue) to reach the individual cross-referenced item directly. To
return back to the point from where you accessed the cross-reference, press
the ALT and ← keys.
Trademarks
AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant, MediaPack, MPMLQ, NetCoder, Stretto, TrunkPack, VoicePacketizer and VoIPerfect, are trademarks or
registered trademarks of AudioCodes Limited. All other products or trademarks are property of
their respective owners.
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, contact support@audiocodes.com.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used. Only industrystandard terms are used throughout this manual. Hexadecimal notation is indicated by 0x
preceding the number.
Note 1: MP-1xx refers to the MP-124 24-port, MP-108 8-port, MP-104 4-port and MP102 2-port VoIP gateways having similar functionality except for the number of
channels (the MP-124 and MP-102 support only FXS).
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
Note:
FXO (Foreign Exchange Office) is the interface replacing the analog
telephone and connects to a Public Switched Telephone Network (PSTN) line
from the Central Office (CO) or to a Private 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 gateway
interfaces between the CO/PBX line and the Internet.
FXS (Foreign Exchange Station) is the interface 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 devices. An FXS VoIP gateway interfaces between the
analog telephone devices and the Internet.
Version 4.4
Warning:
Ensure that you connect FXS ports to analog telephone or to PBX-trunk
lines only, and FXO ports to CO/PBX lines only.
Warning:
The MP-1xx is supplied as a sealed unit and must only be
serviced by qualified service personnel.
5
March 2005
MP-1xx
Warning:
Note:
Disconnect the MP-1xx from the mains and from the Telephone Network
Voltage (TNV) before servicing.
Where “network” appears in this manual, it means LAN, WAN, etc. accessed
via the gateway’s Ethernet interface.
Related Documentation
Document #
Manual Name
LTRT-714xx (e.g., LTRT-71401)
MP-1xx MGCP User’s Manual
LTRT-616xx
MP Series Release Notes
LTRT-651xx
MP-1xx H.323 User’s Manual
LTRT-652xx
MP-1xx H.323 Release Notes
LTRT-654xx
MP-1xx SIP User’s Manual
LTRT-656xx
MP-1xx SIP Release Notes
MP-1xx
6
Document #: LTRT-61405
Fast Track Installation Guide
1
1. Quick Start
Quick Start
This Fast Track Installation Guide helps you to set up the MP-1xx gateway for the first time. Prior
knowledge of IP networks is required. Refer to Figure 1-1 for the quick setup flow. For detailed
information on how to fully configure the gateway, refer to the MP-1xx User’s Manuals.
Figure 1-1: Required Steps to Install the MP-1xx
Refer to Section 2.1
Refer to Section 2.3
Refer to Section 2.4
Refer to Section 3.1
Refer to Section 3.4
Version 4.4
7
March 2005
MP-1xx
2
Installing the MP-1xx
Caution Electrical Shock
The equipment must only be installed or serviced by qualified service personnel.
¾ To install the MP-1xx, take these 4 steps:
1.
Unpack the MP-1xx (refer to Section 2.1 below).
2.
Check the package contents (refer to Section 2.2 below).
3.
Mount the MP-1xx (refer to Section 2.3 below).
4.
Cable the MP-1xx (refer to Section 2.4 on page 12).
After connecting the MP-1xx to the power source, the Ready and LAN LEDs on the front panel
turn to green (after a self-testing period of about 1 minute). Any malfunction changes the Ready
LED to red (refer to Section 6.1 on page 31 for details on the MP-1xx LEDs).
When you have completed the above relevant sections you are then ready to start configuring the
gateway (Section 3 on page 18).
2.1
Unpacking
¾ To unpack the MP-1xx, take these 6 steps:
2.2
1.
Open the carton and remove the packing materials.
2.
Remove the MP-1xx gateway from the carton.
3.
Check that there is no equipment damage.
4.
Check, retain and process any documents.
5.
Notify AudioCodes or your local supplier of any damage or discrepancies.
6.
Retain any diskettes or CDs.
Package Contents
Ensure that in addition to the MP-1xx, the package contains:
MP-1xx
•
AC power cable for the AC power supply option.
•
DC terminal block (MP-124 only, for the DC power supply option).
•
CD (software and documentation).
•
Lifeline cable (RJ-11 adaptor cable for 1 to 2). Supplied with MP-10x/FXS, only.
•
3 brackets (2 short, 1 long) and bracket-to-device screws for 19-inch rack installation option
(MP-10x only).
•
2 short equal-length brackets and bracket-to-device screws for MP-124 19-inch rack
installation.
•
This Fast Track Installation Guide.
8
Document #: LTRT-61405
Fast Track Installation Guide
2.3
2. Installing the MP-1xx
Mounting the MP-1xx
The MP-1xx can be mounted on a desktop or on a wall (only MP-10x), or installed in a standard
19-inch rack.
2.3.1
Mounting the MP-1xx on a Desktop
No brackets are required. Simply place the MP-1xx on the desktop in the position you require.
Figure 2-1 on the next page shows the MP-108. The front panels of the MP-102/FXS, MP-104
(FXS/FXO) and MP-108 (FXS/FXO) are similar except for the number of channels and their
corresponding LEDs.
Figure 2-1: Desktop Mounting
Rack Mount Safety Instructions (UL)
When installing the chassis in a rack, be sure to implement the following safety
instructions recommended by Underwriters Laboratories:
•
•
•
•
•
2.3.2
Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly,
the operating ambient temperature of the rack environment may be greater than
room ambient. Therefore, consideration should be given to installing the equipment
in an environment compatible with the maximum ambient temperature (Tma)
specified by the manufacturer.
Reduced Air Flow - Installation of the equipment in a rack should be such that the
amount of air flow required for safe operation on the equipment is not
compromised.
Mechanical Loading - Mounting of the equipment in the rack should be such that
a hazardous condition is not achieved due to uneven mechanical loading.
Circuit Overloading - Consideration should be given to the connection of the
equipment to the supply circuit and the effect that overloading of the circuits might
have on overcurrent protection and supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when addressing this concern.
Reliable Earthing - Reliable earthing of rack-mounted equipment should be
maintained. Particular attention should be given to supply connections other than
direct connections to the branch circuit (e.g., use of power strips.)
Installing the MP-10x in a 19-inch Rack
The MP-10x is installed into a standard 19-inch rack by the addition of two supplied brackets (1
short, 1 long). The MP-108 with brackets for rack installation is shown in Figure 2-2.
¾ To install the MP-10x in a 19-inch rack, take these 9 steps:
1.
Version 4.4
Remove the two screws on one side of the device nearest the front panel.
9
March 2005
MP-1xx
2.
Insert the peg on the short bracket into the third air vent down on the column of air vents
nearest the front panel.
3.
Swivel the bracket until the holes in the bracket line up with the two empty screw holes on
the device.
4.
Use the screws found in the devices’ package to attach the short bracket to the side of the
device.
5.
Remove the two screws on the other side of the device nearest the front panel.
6.
Position the long bracket so that the holes in the bracket line up with the two empty screw
holes on the device.
7.
Use the screws found in the device’s package to attach the long bracket to the side of the
device.
8.
Position the device in the rack and line up the bracket holes with the rack frame holes.
9.
Use four standard rack screws to attach the device to the rack. These screws are not
provided with the device.
Figure 2-2: MP-108 with Brackets for Rack Installation
2.3.3
Installing the MP-124 in a 19-inch Rack
The MP-124 is installed into a standard 19-inch rack by the addition of two short (equal-length)
supplied brackets. The MP-124 with brackets for rack installation is shown in Figure 2-3.
¾ To install the MP-124 in a 19-inch rack, take these 7 steps:
MP-1xx
1.
Remove the two screws on one side of the device nearest the front panel.
2.
Insert the peg on one of the brackets into the third air vent down on the column of air vents
nearest the front panel.
3.
Swivel the bracket until the holes in the bracket line up with the two empty screw holes on
the device.
4.
Use the screws found in the devices’ package to attach the bracket to the side of the device.
5.
Repeat steps 1 to 4 to attach the second bracket to the other side of the device.
6.
Position the device in the rack and line up the bracket holes with the rack frame holes.
7.
Use four standard rack screws to attach the device to the rack. These screws are not
provided with the device.
10
Document #: LTRT-61405
Fast Track Installation Guide
2. Installing the MP-1xx
Figure 2-3: MP-124 with Brackets for Rack Installation
2.3.4
Mounting the MP-10x on a Wall
The MP-10x is mounted on a wall by the addition of two short (equal-length) supplied brackets.
The MP-102 with brackets for wall mount is shown in Figure 2-4.
¾ To mount the MP-10x on a wall, take these 7 steps:
1.
Remove the screw on the side of the device that is nearest the bottom and the front panel.
2.
Insert the peg on the bracket into the third air vent down on the column of air vents nearest
the front panel.
3.
Swivel the bracket so that the side of the bracket is aligned with the base of the device and
the hole in the bracket line up with the empty screw hole.
4.
Attach the bracket using one of the screws provided in the device package.
5.
Repeat steps 1 to 4 to attach the second bracket to the other side of the device.
6.
Position the device on the wall with the base of the device next to the wall.
7.
Use four screws to attach the device to the wall. These screws are not provided with the
device.
Figure 2-4: MP-102 Wall Mount
Version 4.4
11
March 2005
MP-1xx
2.4
Cabling the MP-1xx
Refer to Table 2-3 on page 13 for the cabling procedure for the MP-1xx.
2.4.1
MP-1xx Rear Panel Connectors
Note 1: MP-10x (FXS/FXO) gateways feature almost identical rear panel connectors
and LEDs, located slightly differently from one device to the next.
Note 2: The RJ-45 port (Eth 1) on the MP-10x/FXO rear panel is inverted on the MP1xx/FXS. The label on the rear panel also distinguishes FXS from FXO
devices.
Figure 2-5: MP-104/FXS Rear Panel Connectors
1
2
4
3
6
5
Table 2-1: MP-10x Rear Panel Component Descriptions
Item #
Label
1
100-250V~
Component Description
AC power supply socket.
2
3
Protective earthing screw.
Eth 1
10/100 Base-TX Ethernet connection.
RJ-11 FXS/FXO ports.
4
5
FXS
6
RS – 232
FXS / FXO label.
9 pin RS-232 status port.
Figure 2-6: MP-124 Rear Panel Connectors
3
2
1
4
6
5
Table 2-2: MP-124 Rear Panel Component Descriptions
Item #
Label
1
Protective earthing screw.
2
100-250V~
3
ANALOG LINES 1 –24
4
Data Cntrl Ready
5
RS – 232
6
Eth 1 Eth 2
MP-1xx
Component Description
AC power supply socket.
50-pin Telco for 1 to 24 analog lines.
LED indicators
9 pin RS-232 status port.
Dual 10/100 Base-TX Ethernet connections.
12
Document #: LTRT-61405
Fast Track Installation Guide
2.4.2
2. Installing the MP-1xx
Cables and Cabling Procedure
Verify that you have the cables listed under column ‘Cable’ in Table 2-3 before beginning to cable
the MP-1xx according to the column ‘Cabling Procedure’.
Table 2-3: Cables and Cabling Procedure
Cable
RJ-45 Ethernet
cable
RJ-11 two-wire
telephone cords
Cabling Procedure
When initializing (connecting the MP-1xx to the network for the first time) use a
standard Ethernet cable to connect the network interface on your computer to a port
on a network hub / switch. Use a second standard Ethernet cable to connect the
MP-1xx to another port on the same network hub / switch.
For normal use, connect the MP-1xx Ethernet connection directly to the network,
using a standard RJ-45 Ethernet cable. For connector’s pinout refer to Figure 2-7 on
page 13.
Connect the RJ-11 connectors on the rear panel of the
MP-10x/FXS to fax machine, modem, or phones (refer Ensure that FXS & FXO are
to Figure 2-8).
connected to the correct
devices, otherwise, damage
Connect the RJ-11 connectors on the MP-10x/FXO
rear panel to telephone exchange analog lines or PBX can occur.
extensions (Figure 2-8).
MP-124/FXS ports are usually distributed using an MDF Adaptor Block (special order
option). Refer to Figure 2-10 for details.
Lifeline cable
For detailed information on setting up the Lifeline, refer to the procedure under
Section 2.4.2 on page 13.
1.
50-pin Telco cable 2.
(MP-124 devices
3.
only).
An Octopus cable 4.
is not included
with the MP-124
5.
package.
RS-232 serial
cable
Wire the 50-pin Telco connectors according to the pinout in Figure 2-9 on page
14, and Table 2-4 on page 15.
Attach each pair of wires from a 25-pair Octopus cable to its corresponding
socket on the MDF Adaptor Block’s rear.
Connect the wire-pairs at the other end of the cable to a male 50-pin Telco
connector.
Insert and fasten this connector to the female 50-pin Telco connector on the MP124 rear panel (labeled Analog Lines 1-24).
Connect the telephone lines from the Adaptor Block to a fax machine, modem, or
telephones by inserting each RJ-11 connector on the 2-wire line cords of the
POTS phones into the RJ-11 sockets on the front of an MDF Adaptor Block as
shown in Figure 2-10 on page 14.
Connect the RS-232 port to your PC’s RS-232 port with a straight serial cable. Using
the RS-232 port is optional.
Protective earthing Connect an earthed strap to the chassis protective earthing screw and fasten it
securely according to the safety standards.
strap
AC Power cable
Connect the MP-1xx 100-250V~ 50-60 Hz power socket to the mains.
DC Power cable
(MP-124 devices
only)
Refer to Figure 2-11. Insert two 18 AWG wires into the supplied DC terminal block
and fasten the two screws located directly above each wire. Insert the DC terminal
block into the DC inlet on the MP-124 rear panel and fasten it with the two adaptor-topanel screws. Connect the other end of the cable to a 48 VDC power supply.
Safety Notice
When installing the DC power supply on the MP-124, be sure to implement the following safety
instructions:
•
Connect the unit to a SELV source sufficiently isolated from the mains.
•
Connect the unit permanently to earth via its earthing stud.
Version 4.4
13
March 2005
MP-1xx
Figure 2-7: RJ-45 Ethernet Connector Pinout
RJ-45 Connector and Pinout
12345678
1 - Tx+
2 - Tx3 - Rx+
6 - Rx-
4, 5, 7, 8
not
connected
Figure 2-8: RJ-11 Phone Connector Pinout
RJ-11 Connector and Pinout
1234
1234-
Not connected
Tip
Ring
Not connected
Figure 2-9: 50-pin Telco Connector (MP-124/FXS only)
Pin Numbers
25
1
26
50
Figure 2-10: MP-124 in a 19-inch Rack with MDF Adaptor
19-inch Rack
Rear View
FRONT INPUT
24 line cords
2-wire with RJ-11
connectors
M D F Adaptor Block - rear
REAR OUTPUT
24 wire pairs in
Octopus cable
with 50-pin male
Telco connector
Primary
LAN Cable
to Eth 1
AC Power Cord
Back-up
LAN Cable
to Eth 2
Connect to
here
ANALOG LINES 1-20
Cntrl
Grounding Strap
MP-1xx
50-pin female
Telco connector
14
Ready
ON
RS-232
Data
100 - 250V~
50 - 60Hz 2A
12345
CONFIG
Eth 1
Eth 2
MP-124
Rear View
RS-232 Cable
Document #: LTRT-61405
Fast Track Installation Guide
2. Installing the MP-1xx
Table 2-4: Pin Allocation in the 50-pin Telco Connector
Phone Channel
Connector Pins
Phone Channel
Connector Pins
1
2
3
4
5
6
7
8
9
10
11
12
1/26
2/27
3/28
4/29
5/30
6/31
7/32
8/33
9/34
10/35
11/36
12/37
13
14
15
16
17
18
19
20
21
22
23
24
13/38
14/39
15/40
16/41
17/42
18/43
19/44
20/45
21/46
22/47
23/48
24/49
Figure 2-11: DC Power Supply on the MP-124
1
2
3
Table 2-5: DC Power Supply on the MP-124 Component Descriptions
Component Description
Item #
Version 4.4
1
2 screws for wire connection to the DC terminal block.
2
2 screws for connecting the DC terminal block to the MP-124 panel.
3
Two 18 AWG wires.
15
March 2005
MP-1xx
2.4.3
Cabling the Lifeline Phone
The Lifeline provides a wired analog POTS phone connection to any PSTN or PBX FXS port
when there is no power, or when the network fails. Users can therefore use the Lifeline phone
even when the MP-1xx is not powered on or not connected to the network. With the MP-108/FXS
and MP-104/FXS the Lifeline connection is provided on port #4 (refer to Figure 2-13). With the
MP-102/FXS the Lifeline connection is provided on port #2.
Note:
The MP-124 and MP-10x/FXO do NOT support the Lifeline.
The Lifeline’s Splitter connects pins #1 and #4 to another source of an FXS port, and pins #2 and
#3 to the POTS phone. Refer to the Lifeline Splitter pinout in Figure 2-12.
Figure 2-12: Lifeline Splitter Pinout & RJ-11 Connector for MP-10x/FXS
1234
1234-
Life Line Tip
Tip
Ring
Life Line Ring
¾ To cable the MP-10x/FXS Lifeline phone, take these 3 steps:
1.
Connect the Lifeline Splitter to port #4 (on the MP-104/FXS or MP-108/FXS) or to port #2 (on
the MP-102/FXS).
2.
Connect the Lifeline phone to Port A on the Lifeline Splitter.
3.
Connect an analog PSTN line to Port B on the Lifeline Splitter.
Note:
MP-1xx
The use of the Lifeline on network failure can be disabled using the
‘LifeLineType’ ini file parameter. For detailed information on the ini file refer to
Table 7-1.
16
Document #: LTRT-61405
Fast Track Installation Guide
2. Installing the MP-1xx
Figure 2-13: MP-104/FXS Lifeline Setup
1
2
3
4
6
7
5
Table 2-6: MP-104/FXS Lifeline Setup Component Descriptions
Item #
Version 4.4
Component Description
1
B: To PSTN wall port.
2
Phone to Port 1.
3
Lifeline to Port 4.
4
PSTN to Splitter (B).
5
Phone to Port 1.
6
Lifeline phone to Splitter (A).
7
Lifeline phone.
17
March 2005
MP-1xx
3
Configuring the MP-1xx
The MP-1xx is supplied with application software already resident in its flash memory (with
factory default parameters).
Section 3.1 below describes how to assign an IP address to the MP-1xx, while Section 3.4 on
page 22 describes how to set up the MP-1xx with basic parameters using a standard Web
browser (such as Microsoft TM Internet Explorer).
Note:
3.1
Section 3.1 applies equally to MGCP, H.323 and SIP.
Assigning the MP-1xx IP Address
To assign an IP address to the MP-1xx use one of the following methods:
•
HTTP using a Web browser (refer to Section 3.1.1 below).
•
BootP (refer to Section 3.1.2 on page 19).
•
DHCP (refer to the Mediant 2000 User’s Manual).
•
Serial communication software (e.g., HyperTerminalTM) connected to the MP-1xx via the RS232 port (refer to Section 3.1.3 on page 20).
The default networking parameters are show in Table 3-1.
You can use the ‘Reset’ button to restore the MP-1xx networking parameters to their factory
default values (refer to Section 3.2 on page 21).
Table 3-1: MP-1xx Default Networking Parameters
FXS or FXO
Default Value
10.1.10.10
FXS
10.1.10.11
FXO
MP-1xx default subnet mask is 255.255.0.0, default gateway IP address is 0.0.0.0
3.1.1
Assigning an IP Address Using HTTP
¾ To assign an IP address using HTTP, take these 8 steps:
MP-1xx
1.
Connect your computer to the MP-1xx. Either connect the network interface on your
computer to a port on a network hub/switch (refer to Table 2-3 on page 13 - RJ-45 Ethernet
cable), or use an Ethernet cross-over cable to directly connect the network interface on your
computer to the RJ-45 jack on the MP-1xx.
2.
Change your PC’s IP address and subnet mask to correspond with the MP-1xx factory
default IP address and subnet mask, shown in Table 3-1. For details on changing the IP
address and subnet mask of your PC, refer to Windows™ Online Help (Start>Help).
3.
Access the MP-1xx Embedded Web Server (refer to Section 3.3 on page 21).
4.
In the ‘Quick Setup’ screen, set the MP-1xx ‘IP Address’, ‘Subnet Mask’ and ‘Default
Gateway IP Address’ fields under ‘IP Configuration’ to correspond with your network IP
settings. If your network doesn’t feature a default gateway, enter a dummy value in the
‘Default Gateway IP Address’ field.
5.
Click the Reset button and click OK in the prompt; the MP-1xx applies the changes and
restarts. This takes approximately 1 minute to complete. When the MP-1xx has finished
restarting, the Ready and LAN LEDs on the front panel are lit green.
18
Document #: LTRT-61405
Fast Track Installation Guide
Tip:
3.1.2
3. Configuring the MP-1xx
Record and retain the IP address and subnet mask you assign the MP-1xx.
Do the same when defining new username or password. If the Embedded
Web Server is unavailable (for example, if you’ve lost your username and
password), use the BootP/TFTP configuration utility to access the device,
“reflash” the load and reset the password (refer to the MP-1xx User’s Manuals
for detailed information on using a BootP/TFTP configuration utility to access
the device).
6.
Disconnect your computer from the MP-1xx or from the hub / switch (depending on the
connection method you used in step 1).
7.
Reconnect the MP-1xx and your PC (if necessary) to the network.
8.
Restore your PC’s IP address & subnet mask to what they originally were. If necessary,
restart your PC and re-access the MP-1xx via the Embedded Web Server with its new
assigned IP address.
Assigning an IP Address Using BootP
Tip 1:
BootP procedure can also be performed using any standard compatible
BootP server.
Tip 2:
You can also use BootP to load the auxiliary files to the MP-1xx (refer to the
Mediant 2000 User’s Manual).
¾ To assign an IP address using BootP, take these 12 steps:
1.
Open the BootP application (supplied with the MP-1xx software package).
2.
Click on the Edit Clients icon;
the ‘Client Configuration’ screen is displayed.
3.
Click on the Add New Client icon;
a client with blank parameters is displayed (Figure 3-1).
4.
In the ‘Client MAC’ field, enter the MAC address of the gateway. The MAC address is printed
on a label located on the base of the MP-1xx.
5.
Verify that the box to the right of the ‘Client MAC’ field is checked. This enables the particular
client in the BootP tool (if the client is disabled, no replies are sent to BootP requests).
6.
In the ‘Client Name’ field, enter a descriptive name for this client so that it is easier to
remember which gateway the record refers to. For example, this name could refer to the
location of the gateway.
7.
In the ‘IP’ field, enter the IP address you want to assign the gateway. Use the normal dotted
decimal format.
8.
In the ‘Subnet’ field, enter the subnet mask you want to assign the gateway. Use the normal
dotted decimal format. Ensure that the subnet mask is correct. If the address is incorrect, the
gateway may not function until the entry is corrected and a BootP reset is applied.
9.
In the ‘Gateway’ field, enter the IP address for the default gateway. If you do not know the IP
address for the default gateway, contact your network administrator.
10. Click Apply to save this entry to the list of clients.
11. Click OK; the ‘Client Configuration’ screen is closed.
12. Reset the MP-1xx physically causing it to use BootP; the MP-1xx changes its network
parameters to the values provided by the BootP.
Version 4.4
19
March 2005
MP-1xx
Figure 3-1: Client Configuration Screen with Blank Parameters
3.1.3
Assigning an IP Address via the RS-232 Port
¾ To assign an IP address via the RS-232, take these 6 steps:
MP-1xx
1.
Connect the MP-1xx RS-232 port to either COM1 or COM2 RS-232 communication port on
your PC with a standard RS-232 straight cable (not a cross-over cable).
2.
Use a serial communication software (e.g., HyperTerminalTM) to connect to the MP-1xx.
Set your serial communication software to the following communications port settings:
¾
Baud Rate:
115,200 bps
¾
Data bits:
8
¾
Parity:
None
¾
Stop bits:
1
¾
Flow control:
Hardware
3.
At the prompt type “conf” and press enter; the configuration command shell is activated.
4.
To check the current network parameters, at the prompt, type “GCP IP” and press enter; the
current network settings are displayed.
5.
Change the network settings by typing: “SCP IP [ip_address] [subnet_mask]
[default_gateway]” (e.g., “SCP IP 10.13.77.7 255.255.0.0 10.13.0.1”); the new settings take
effect on-the-fly. Connectivity is active at the new IP address.
Note: This command requires you to enter all three network parameters (separated by
spaces).
6.
To save the configuration, at the prompt, type “SAR” and press enter; the MP-1xx restarts
with the new network settings.
20
Document #: LTRT-61405
Fast Track Installation Guide
3.2
3. Configuring the MP-1xx
Restoring Networking Parameters to their Initial State
You can use the ‘Reset’ button to restore the MP-1xx networking parameters to their factory
default values (described in Table 3-1) and to reset the username and password.
Note that the MP-1xx returns to the software version burned in flash. This process also restores
the MP-1xx parameters to their factory settings, therefore you must load your previously backedup ini file, or the default ini file (received with the software kit) to set them to their correct values.
¾ To restore networking parameters to their initial state, take these 6
steps:
3.3
1.
Disconnect the MP-1xx from the power and network cables.
2.
Reconnect the power cable; the gateway is powered up. After approximately 45 seconds the
Ready LED turns to green and the Control LED blinks for about 3 seconds.
3.
While the Control LED is blinking, press shortly on the reset button (located on the left side
of the front panel); the gateway resets a second time and is restored with factory default
parameters (username: “Admin”, password: “Admin”).
4.
Reconnect the network cable.
5.
Assigning the MP-1xx IP address (refer to Section 3.1 on page 18).
6.
Load your previously backed-up ini file, or the default ini file (received with the software kit).
To load the ini file via the Embedded Web Server, refer to Section 5 on page 30.
Accessing the Embedded Web Server
¾ To access the Embedded Web Server, take these 4 steps:
1.
Open a standard Web-browsing application such as Microsoft™ Internet Explorer™ (Version
6.0 and higher) or Netscape™ Navigator™ (Version 7.0 and higher).
2.
In the URL field, specify the IP address of the MP-1xx (e.g., http://10.1.10.10 for MP1xx/FXS); the Embedded Web Server’s ‘Enter Network Password’ screen appears, shown in
Figure 3-2.
Figure 3-2: Embedded Web Server Login Screen
3.
In the ‘User Name’ and ‘Password’ fields, enter the username (default: “Admin”) and
password (default: “Admin”). Note that the username and password are case-sensitive.
4.
Click OK; the ‘Quick Setup’ screen is accessed, shown in Figure 3-3 (MGCP), Figure 3-4
(H.323), and Figure 3-5 (SIP).
Version 4.4
21
March 2005
MP-1xx
3.4
Configuring the MP-1xx Basic Control Protocol
Parameters
To configure the MP-1xx basic control protocol parameters use the Embedded Web Server’s
‘Quick Setup’ screen.
•
For MGCP refer to Section 3.4.1 on page 22.
•
For H.323, refer to Section 3.4.2 on page 24.
•
For SIP, refer to Section 3.4.3 on page 26.
When you have completed the above relevant section you are then ready to start using the MP1xx. For information on how to fully configure the VoIP gateway, refer to the MP-1xx User’s
Manuals.
MP-1xx
Tip:
Once the gateway is configured correctly, back up your settings by making a
copy of the VoIP gateway configuration (ini file) and store it in a directory on
your computer. This saved file can be used to restore configuration settings at
a future time. For information on backing up and restoring the gateway’s
configuration refer to Section 5 on page 30.
Note:
The following configuring Sections from here up to and including Section
3.4.3 on page 26 apply individually to MGCP, H.323, or SIP.
MGCP Configuring continues with Section 3.4.1 on page 22.
H.323 Configuring continues with Section 3.4.2 on page 24.
SIP Configuring continues with Section 3.4.3 on page 26.
22
Document #: LTRT-61405
Fast Track Installation Guide
3.4.1
3. Configuring the MP-1xx
Configuring Basic MGCP Parameters
After accessing the Embedded Web Server (refer to Section 3.3 on page 21) the MGCP ‘Quick
Setup’ screen is displayed, shown in Figure 3-3.
Figure 3-3: MP-1xx MGCP Quick Setup Screen
¾ To configure basic MGCP parameters, take these 9 steps:
1.
If your network features a DNS server, in the fields ‘DNS Primary Server IP’ and ‘DNS
Secondary Server IP’, enter the IP address of the primary and secondary DNS servers
(clarify with your network administrator). Note that the DNS server option is not supported by
MGCP.
2.
If your network features a DHCP server, in the ‘Enable DHCP’ field, select ‘Enable’; the ‘IP
Address’, ‘Subnet Musk’ and ‘Default Gateway IP Address’ fields are disabled. When the
gateway is configured to use DHCP, it attempts to contact the DHCP server to obtain the
networking parameters (i.e., IP address, subnet mask, default gateway and
primary/secondary DNS server).
3.
Select ‘MGCP’ in the ‘Control Protocol Type’ field.
4.
In the ‘Call Agent IP’ field, enter the Call Agent IP address if your enterprise’s network
doesn’t feature a DNS server that automatically defines the Call Agent’s IP address. If you
have a DNS server, the field is optional.
5.
In the ‘Call Agent Port’ field, enter the Call Agent port. The default is 2427.
6.
In the ‘Call Agent Domain Name’ field, enter the Call Agent domain name. When using the
DNS server option, enter the domain name of the Call Agent operating with the MP-1xx. The
DNS server automatically deduces the Call Agent’s IP address from the domain name.
7.
In the ‘Gateway Name’ field, enter a name to the device. (For example: ‘gateway1.com’).
Ensure that the name you choose is the one that the Call Manager/Agent is configured with
to identify your MP-1xx.
Version 4.4
23
March 2005
MP-1xx
8.
In the ‘Endpoint Name’ field, enter an intuitive endpoint name. Ensure that the endpoint
name you choose is the one that the Call Agent works with.
9.
Click the Reset button and click OK in the prompt; The MP-1xx applies the changes and
restarts. This takes approximately 1 minute to complete. When the MP-1xx has finished
restarting, the Ready and LAN LEDs on the front panel are lit green.
Note:
3.4.2
MGCP Users should continue with Section 4 Changing the MP-1xx Username
on page 29.
Configuring Basic H.323 Parameters
After accessing the Embedded Web Server (refer to Section 3.3 on page 21) the H.323 ‘Quick
Setup’ screen is displayed, shown in Figure 3-4.
Figure 3-4: MP-1xx H.323 Quick Setup Screen
¾ To configure basic H.323 parameters, take these 7 steps:
1.
MP-1xx
If the MP-1xx is behind a router with NAT enabled, perform the following procedure. If it isn’t,
leave the ‘NAT IP Address’ field undefined.
¾
Determine the “public” IP address assigned to the router (by using, for instance, router
Web management). Enter this public IP address in the ‘NAT IP Address’ field.
¾
Enable the DMZ configuration on the residential router for the LAN port where the MP1xx gateway is connected. This enables unknown packets to be routed to the DMZ port.
2.
When working with a Gatekeeper, set ‘Working with Gatekeeper’ field, under ‘H.323
Parameters’, to ‘Yes’ and enter the IP address of the primary Gatekeeper in the field
‘Gatekeeper IP Address’. When no Gatekeeper is used, the internal routing table is used to
route the calls.
3.
Leave parameter ‘Enable Annex D/T.38 FAX Relay’ at its default unless your technical
requirements differ.
24
Document #: LTRT-61405
Fast Track Installation Guide
4.
Select the coder (i.e., vocoder) that best suits your VoIP system requirements. The default
coder is: G.7231 30 msec. To program the entire list of coders you want the MP-1xx to use,
click the button on the left side of the ‘1st Coder’ field; the drop-down list for the 2nd to 5th
coders appear. Select coders according to your system requirements. Note that coders
higher on the list are preferred and take precedence over coders lower on the list.
Note:
5.
3. Configuring the MP-1xx
The preferred coder is the coder that the MP-1xx uses as a first choice for all
connections. If the far end gateway does not use this coder, the MP-1xx
negotiates with the far end gateway to select a coder that both sides can use.
Map outgoing calls to IP addresses (when Gatekeeper isn’t used) by completing these steps:
¾
Click the arrow button next to the ‘Tel to IP Routing Table’ label; the ‘Tel to IP Routing’
screen opens.
Any telephone number whose destination number matches the prefix defined in the
‘Destination Phone Prefix’ field and whose source number matches the prefix defined in
the adjacent ‘Source Phone Prefix‘ field, is sent to the IP address entered in the ‘IP
Address’ field.
¾
Click the Submit button; the ‘Tel to IP Routing’ table is automatically updated.
¾
Click the Close Window button.
For more information on the ‘Tel to IP Routing’ table refer to the MP-1xx H.323 User’s
Manual.
6.
7.
Allocate MP-1xx endpoints (analog lines) and their corresponding phone numbers to
incoming IP calls by completing these steps:
¾
Click the arrow button next to the ‘Endpoint Phone Number’ label; the ‘Endpoint Phone
Numbers’ screen opens.
¾
Enter the number of a channel, starting with 1, (or a group of channels), under the
column ‘Channel(s)’ (for example 1-4 for the first 4 endpoints).
¾
Assign each channel a phone number (for a group of channels, define the first number
in an ordered sequence). For an example of connecting two MP-108 devices, refer to
Section 3.4.4 on page 28.
¾
Click the Submit button; the ‘Endpoint Phone Number’ table is automatically updated.
¾
Click the Close Window button.
Click the Reset button and click OK in the prompt; The MP-1xx applies the changes and
restarts. This takes approximately 1 minute to complete. When the MP-1xx has finished
restarting, the Ready and LAN LEDs on the front panel are lit green.
Note:
Version 4.4
H.323 Users should continue with Section 3.4.4 Example of Connecting Two
MP-108 Devices on page 28.
25
March 2005
MP-1xx
3.4.3
Configuring Basic SIP Parameters
After accessing the Embedded Web Server (refer to Section 3.3 on page 21) the SIP ‘Quick
Setup’ screen is displayed, shown in Figure 3-5.
Figure 3-5: MP-1xx SIP Quick Setup Screen
¾ To configure basic SIP parameters, take these 9 steps:
1.
MP-1xx
If the MP-1xx is behind a router with NAT enabled, take the following procedures:
¾
Determine the “public” IP address assigned to the router (by using, for instance, router
Web management). Enter this public IP address in the ‘NAT IP Address’ field.
¾
Enable the DMZ configuration on the residential router for the LAN port where the MP1xx gateway is connected. This enables unknown packets to be routed to the DMZ port.
2.
Under ‘SIP Parameters’, enter the MP-1xx Domain Name in the field ‘Gateway Name’. If the
field is not specified, the MP-1xx IP address is used instead (default).
3.
When working with a Proxy server, set ‘Working with Proxy’ field to ‘Yes’ and enter the IP
address of the primary Proxy server in the field ‘Proxy IP Address’. When no Proxy is used,
the internal routing table is used to route the calls.
4.
Enter the Proxy Name in the field ‘Proxy Name’. If Proxy name is used, it replaces the Proxy
IP address in all SIP messages. This means that messages are still sent to the physical
Proxy IP address but the SIP URI contains the Proxy name instead.
5.
Configure ‘Enable Registration’ to ‘Yes’ or ‘No’:
‘No’ = the MP-1xx does not register to a Proxy server/Registrar (default).
‘Yes’ = the MP-1xx registers to a Proxy server/Registrar at power up and every ‘Registration
Time’ seconds. The MP-1xx sends a register request according to the ‘Authentication Mode’
parameter. For detailed information on the parameters ‘Registration Time’ and
‘Authentication Mode’, refer to the MP-1xx SIP User’s Manual.
26
Document #: LTRT-61405
Fast Track Installation Guide
6.
Select the coder (i.e., vocoder) that best suits your VoIP system requirements. The default
coder is: G.7231 30 msec. To program the entire list of coders you want the MP-1xx to use,
click the button on the left side of the ‘1st Coder’ field; the drop-down list for the 2nd to 5th
coders appears. Select coders according to your system requirements. Note that coders
higher on the list are preferred and take precedence over coders lower on the list.
Note:
7.
3. Configuring the MP-1xx
The preferred coder is the coder that the MP-1xx uses as a first choice for all
connections. If the far end gateway does not use this coder, the MP-1xx
negotiates with the far end gateway to select a coder that both sides can use.
Map outgoing calls to IP addresses (when Proxy isn’t used) by completing these steps:
¾
Click the arrow button next to the ‘Tel to IP Routing Table’ label; the ‘Tel to IP Routing’
screen opens.
Any telephone number whose destination number matches the prefix defined in the
‘Destination Phone Prefix’ field and whose source number matches the prefix defined in
the adjacent ‘Source Phone Prefix‘ field, is sent to the IP address entered in the ‘IP
Address’ field.
¾
Click the Submit button; the ‘Tel to IP Routing’ table is automatically updated.
¾
Click the Close Window button.
For more information on the ‘Tel to IP Routing’ table refer to the MP-1xx SIP User’s Manual.
8.
9.
Allocate MP-1xx endpoints (analog lines) and their corresponding phone numbers to
incoming IP calls by completing these steps:
¾
Click the arrow button next to the ‘Endpoint Phone Number’ label; the ‘Endpoint Phone
Numbers’ screen opens.
¾
Enter the number of a channel, starting with 1, (or a group of channels), under the
column ‘Channel(s)’ (for example 1-4 for the first 4 endpoints).
¾
Assign each channel a phone number (for a group of channels, define the first number
in an ordered sequence) For an example of connecting two MP-108 devices, refer to
Section 3.4.4 on page 28.
¾
Click the Submit button; the ‘Endpoint Phone Number’ table is automatically updated.
¾
Click the Close Window button.
Click the Reset button and click OK in the prompt; The MP-1xx applies the changes and
restarts. This takes approximately 1 minute to complete. When the MP-1xx has finished
restarting, the Ready and LAN LEDs on the front panel are lit green.
Note:
Version 4.4
SIP Users should continue with Section 3.4.4 Example of Connecting Two
MP-108 Devices on page 28.
27
March 2005
MP-1xx
3.4.4
Example of Connecting Two MP-108 Devices
This example applies to H.323 and SIP. Figure 3-6 below shows an example of two MP-108/FXS
devices’ internal routing tables. The phone ‘2001’ is connected to the first channel of gateway
10.2.222.108, and phone ‘2101’ is connected to the first channel of gateway 10.2.222.107.
To make a call between two gateways, lift the receiver of phone ‘2001’; you hear a dial tone and
the first channel’s LED lights up. Dial 2101; after dialing the last digit, the data LED begins
blinking (indicating traffic) and phone ‘2101’ rings.
Note 1: The prefixes you choose in the ‘Tel to IP Routing’ table must differentiate the
gateways from each other to ensure correct routing. In the example, using the
first digit (2) doesn’t differentiate the devices, thus 2 digits of the phone
number are used.
Note 2: To enable phones connected to the same MP-1xx to communicate with each
other, define in the internal routing table the IP address and corresponding
phone numbers of the device itself (applicable only to H.323 devices).
Figure 3-6: Example of Connecting Two MP-108 Devices
Phone # 2001
Phone # 2101
IP Network
10.2.222.108
10.2.222.107
Web Browser in PC
MP-1xx
28
Document #: LTRT-61405
Fast Track Installation Guide
Note:
4
4. Changing the MP-1xx Username and Password
The following Sections from here, up to the end of this Fast Track Guide,
apply equally to MGCP, H.323 and SIP.
Changing the MP-1xx Username and
Password
To prevent unauthorized access to the MP-1xx, it is recommended that you change the username
and password (both are case-sensitive) that are used to access the Embedded Web Server.
¾ To change the username and password, take these 6 steps:
1.
Access the Embedded Web Server (refer to Section 3.3 on page 21).
2.
Open the ‘Change Password’ screen (Advanced Configuration menu > Change
Password); the ‘Change Password’ screen is displayed.
Figure 4-1: Change Password Screen
3.
In the ‘User Name’ and ‘New Password’ fields, enter the new username and the new
password respectively. Note that the username and password can be a maximum of 7 casesensitive characters.
4.
In the ‘Confirm Password’ field, reenter the new password.
5.
Click the Change Password button; the new username and password are applied and the
‘Enter Network Password’ screen appears, shown in Figure 3-2 on page 21.
6.
Enter the updated username and password in the ‘Enter Network Password’ screen.
Version 4.4
29
March 2005
MP-1xx
5
Restoring and Backing Up the MP-1xx
Configuration
The ‘Configuration File’ screen enables you to restore (load a new ini file to the gateway) or to
back up (make a copy of the VoIP gateway ini file and store it in a directory on your computer) the
current configuration the gateway is using. For information on the ini file refer to Table 7-1 on
page 37.
Back up your configuration if you want to protect your VoIP gateway programming. The backup
ini file includes only those parameters that were modified and contain other than default values.
Restore your configuration if the VoIP gateway has been replaced or has lost its programming
information, you can restore the VoIP gateway configuration from a previous backup or from a
newly created ini file. To restore the VoIP gateway configuration from a previous backup you
must have a backup of the VoIP gateway information stored on your computer.
¾ To restore or back up the ini file:
•
Open the ‘Configuration File’ screen (Advanced Configuration menu > Configuration
File); the ‘Configuration File’ screen is displayed.
Figure 5-1: Configuration File Screen
¾ To back up the ini file, take these 4 steps:
1.
Click the Get INI FILE button; the ‘File Download’ window opens.
2.
Click the Save button; the ‘Save As’ window opens.
3.
Navigate to the folder where you want to save the ini file.
4.
Click the Save button; the VoIP gateway copies the ini file into the folder you selected.
¾ To restore the ini file, take these 4 steps:
MP-1xx
1.
Click the Browse button.
2.
Navigate to the folder that contains the ini file you want to load.
3.
Click the file and click the Open button; the name and path of the file appear in the field
beside the Browse button.
4.
Click the Send ini File button, and click OK in the prompt; the gateway is automatically reset
(from the cmp version stored on the flash memory).
30
Document #: LTRT-61405
Fast Track Installation Guide
6
6. Monitoring the MP-1xx
Monitoring the MP-1xx
The MP-1xx provides several ways of monitoring the status of the gateway:
6.1
•
Monitoring the MP-1xx front panel LEDs (refer to Section 6.1 below).
•
Monitoring the MP-1xx rear panel LEDs (refer to Section 6.2 on page 32).
•
Monitoring the MP-1xx channels via the Embedded Web Server (refer to Section 6.3 on
page 32).
Front Panel LEDs
The MP-1xx front panel LEDs indicate the Ethernet LAN status, Data (RTP) activity and state of
the gateway ports. Table 6-1 describes the meaning of each state of the LEDs on the front panel.
Table 6-1: Definition of MP-1xx Front Panel LED Indicators
LED
Ready
LAN
Control
Type
Device
Status
Ethernet
Link Status
Control
Link
Color
State
Green
ON
Device powered, self-test OK
Orange
Blinking
Software loading/Initialization
Red
ON
Malfunction
Green
ON
Valid 10/100 Base-TX Ethernet connection
Red
ON
Malfunction
Green
Toggles
/ Blinking
Blank
Data
Packet
Status
Telephone
Interface
Green
Blinking
Transmitting packets
Red
Blinking
MP-1xx is receiving data packets
No traffic
Green
ON
Green
Blinking
Red
ON
Blank
Version 4.4
MGCP:
Changes between green and off. Indicates activity,
control messages are received in real time.
H.323 / SIP:
Sending and receiving H.323 / SIP messages.
No traffic.
Blank
Channels
Definition
The phone is offhooked (FXS); the FXO offhooks the
line towards the PBX.
There’s an incoming call, before answering
Line malfunction
Normal onhook position
31
March 2005
MP-1xx
6.2
Rear Panel LEDs
The LEDs on the rear panel are located within the RJ-45 socket. Table 6-2 describes the
meaning of each state of the LEDs on the rear panel.
Table 6-2: Definition of MP-1xx Rear Panel LED Indicators
Label
Type
Color
State
Ethernet
Status
Yellow
ON
Ethernet port receiving data
ETH-1
Red
ON
Collision
6.3
Definition
Monitoring the MP-1xx Channels
¾ To monitor the status of the channels:
•
Open the Channel Status screen (Status & Diagnostics menu > Channel Status); the
Channel Status screen is displayed.
Figure 6-1: MP-1xx/FXS Channel Status Screen
The color of each channel shows the call status of that channel.
•
Not Connected (FXO only) - indicates that no analog line is connected to this port.
•
Inactive - indicates this channel is currently onhook.
•
Handset Offhook - indicates this channel is offhook but there is no active RTP session.
•
RTP Active - indicates an active RTP stream.
¾ To monitor the details of a channel, take these 2 steps:
MP-1xx
1.
In the Channel Status screen, click the numbered icon of the specific channel whose detailed
status you need to check/monitor; the channel-specific Channel Status screen appears.
2.
Click the submenu links to check/view a specific channel’s parameter settings.
32
Document #: LTRT-61405
Fast Track Installation Guide
7
7. Software Update
Software Update
The ‘Software Update’ menu enables users to upgrade the MP-1xx software by loading a new
cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files.
The ‘Software Update’ menu comprises two submenus:
•
Software Update Wizard (refer to Section 7.1 below).
•
Auxiliary Files (refer to Section 7.2 on page 37).
Note:
7.1
When upgrading the MP-1xx software you must load the new cmp file with all
other related configuration files.
Software Upgrade Wizard
The Software Upgrade Wizard guides users through the process of software upgrade: selecting
files and loading them to the gateway. The wizard also enables users to upgrade software while
maintaining the existing configuration. Using the wizard obligates users to load a cmp file. Users
can choose to also use the Wizard to load the ini and auxiliary files (e.g., Call Progress Tones)
but this option cannot be pursued without loading the cmp file. For the ini and each auxiliary file
type, users can choose to reload an existing file, load a new file or not load a file at all.
Note:
The Software Upgrade Wizard requires the MP-1xx to be reset at the end of
the process, disrupting any of its traffic. To avoid disruption, disable all traffic
on the MP-1xx before initiating the Wizard.
¾ To use the Software Upgrade Wizard, take these 9 steps:
1.
Stop all traffic on the MP-1xx (refer to the note above).
2.
Open the ‘Software Upgrade Wizard’ (Software Update menu > Software Upgrade
Wizard); the ‘Start Software Upgrade’ screen appears.
Figure 7-1: Start Software Upgrade Screen
Note:
Version 4.4
At this point, the process can be canceled with no consequence to the MP-1xx
(click the Cancel button). If you continue the process (by clicking the Start
Software Upgrade button, the process must be followed through and
completed with a MP-1xx reset at the end. If you click the Cancel button in any
of the subsequent screens, the MP-1xx is automatically reset with the
configuration that was previously burned in flash memory.
33
March 2005
MP-1xx
3.
Click the Start Software Upgrade button; the ‘Load a cmp file’ screen appears (Figure 7-2).
Note:
When in the Wizard process, the rest of the Web application is unavailable and
the background Web screen is disabled. After the process is completed,
access to the full Web application is restored.
Figure 7-2: Load a cmp File Screen
4.
Click the Browse button, navigate to the cmp file and click the button Send File; the cmp file
is loaded to the MP-1xx and you’re notified as to a successful loading (refer to Figure 7-3).
Figure 7-3: cmp File Successfully Loaded into the MP-1xx Notification
5.
Note that the four action buttons (Cancel, Reset, Back, and Next) are now activated
(following cmp file loading).
You can now choose to either:
¾
Click Reset; the MP-1xx resets, utilizing the new cmp you loaded and utilizing the
current configuration files.
¾
Click Cancel; the MP-1xx resets utilizing the cmp, ini and all other configuration files
that were previously stored in flash memory. Note that these are NOT the files you
loaded in the previous Wizard steps.
¾
Click Back; the ‘Load a cmp File’ screen is reverted to; refer to Figure 7-2.
¾
Click Next; the ‘Load an ini File’ screen opens; refer to Figure 7-4. Loading a new ini file
or any other auxiliary file listed in the Wizard is optional.
Note that as you progress, the file type list on the left indicates which file type loading is in
process by illuminating green (until ‘FINISH’).
MP-1xx
34
Document #: LTRT-61405
Fast Track Installation Guide
7. Software Update
Figure 7-4: Load an ini File Screen
6.
In the ‘Load an ini File’ screen, you can now choose to either:
¾
Click Browse and navigate to the ini file; the check box ‘Use existing configuration’, by
default checked, becomes unchecked. Click Send File; the ini file is loaded to the MP1xx and you’re notified as to a successful loading.
¾
Ignore the Browse button (its field remains undefined and the check box ‘Use existing
configuration’ remains checked by default).
¾
Ignore the Browse button and uncheck the ‘Use existing configuration’ check box; no ini
file is loaded, the MP-1xx uses its factory-preconfigured values.
You can now choose to either:
¾
Click Cancel; the MP-1xx resets utilizing the cmp, ini and all other configuration files
that were previously stored in flash memory. Note that these are NOT the files you
loaded in the previous Wizard steps.
¾
Click Reset; the MP-1xx resets, utilizing the new cmp and ini file you loaded up to now
as well as utilizing the other configuration files.
¾
Click Back; the ‘Load a cmp file’ screen is reverted to; refer to Figure 7-2.
¾
Click Next; the ‘Load a CPT File’ screen opens, refer to Figure 7-5; Loading a new CPT
file or any other auxiliary file listed in the Wizard is optional.
Figure 7-5: Load a CPT File Screen
7.
Version 4.4
Follow the same procedure you followed when loading the ini file (refer to Step 6). The same
procedure applies to the ‘Load a VP file’ (not applicable to the MP-1xx gateway) screen and
‘Load a coefficient file’ screen.
35
March 2005
MP-1xx
8.
Button
In the ‘FINISH’ screen (refer to Figure 7-6), the Next button is disabled. Complete the
upgrade process by clicking Reset or Cancel.
Result
Reset
The MP-1xx ‘burns’ the newly loaded files to flash memory. The ‘Burning files to flash
memory’ screen appears. Wait for the ‘burn’ to finish. When it finishes, the ‘End Process’
screen appears displaying the burned configuration files (refer to Figure 7-7).
Cancel
The MP-1xx resets, utilizing the files previously stored in flash memory. (Note that these
are NOT the files you loaded in the previous Wizard steps).
Figure 7-6: FINISH Screen
Figure 7-7: ‘End Process’ Screen
9.
MP-1xx
Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application
is reactivated.
36
Document #: LTRT-61405
Fast Track Installation Guide
7.2
7. Software Update
Updating the Auxiliary Files
The auxiliary files are configuration dat files that are loaded to the gateway (in addition to the ini
file) to enable enhanced gateway provisioning. The following auxiliary files are available:
coefficient, Voice Prompts, Call Progress Tones (CPT) and Prerecorded Tones (PRT). The Voice
Prompts file is currently applicable only to MGCP. Table 7-1 presents a brief description of the ini
file and of each auxiliary file.
Table 7-1: ini and Auxiliary Files Descriptions
File Type
Description
Ini
Load the file to provision the MP-1xx parameters. The Embedded Web Server
enables practically full device provisioning but customers may occasionally require
new feature configuration parameters in which case this file is loaded.
Note that loading the ini file only provisions parameters that are contained in the ini
file. If a parameter is not specified in the ini file, values associated with that parameter
are reset to a default value. These values may not be the same as the values that
were configured for the VoIP gateway at the time of manufacture.
Note: After the file has completed loading, the VoIP gateway automatically restarts
(software is loaded from the flash).
Coefficient
This file (different file for FXS and FXO gateways) contains the telephony interface
configuration information for the VoIP gateway. This information includes telephony
interface characteristics, such as DC and AC impedance, feeding current and ringing
voltage. This file is specific to the type of telephony interface that the VoIP gateway
supports. In most cases you have to load this type of file.
Voice Prompts
The voice announcement file contains a set of Voice Prompts to be played by the
MP-1xx during operation on Call Agent request. Only MGCP is supported.
Call Progress
Tones
This is a region-specific, telephone exchange-dependent file that contains the Call
Progress Tones levels and frequencies that the VoIP gateway uses. The default CPT
file is: U.S.A.
Prerecorded
Tones
The dat PRT file enhances the gateway’s capabilities of playing a wide range of
telephone exchange tones that cannot be defined in the Call Progress Tones file.
¾ To load an auxiliary file via the Embedded Web Server, take these 6
steps:
1.
Open the ‘Auxiliary Files’ screen (Software Update menu > Load Auxiliary Files); the
‘Auxiliary Files’ screen is displayed (shown in Figure 7-8).
2.
Click the Browse button that is in the field for the type of file you want to load.
3.
Navigate to the folder that contains the file you want to load.
4.
Click the file and click the Open button; the name and path of the file appear in the field next
to the Browse button.
5.
Click the Send File button adjacent to the field that contains the name of the file you want to
load. An asterisk in the screen section indicates that the file’s loading takes effect on-the-fly
(e.g., Voice Prompts file).
6.
Repeat steps 2 to 5 for each file you want to load.
Version 4.4
37
March 2005
MP-1xx
Figure 7-8: Auxiliary Files Screen
¾ To save the loaded auxiliary files to flash memory, take these 2 steps:
1.
Click the Save Configuration button on the main menu bar; the ‘Save Configuration to the
Flash Memory’ screen is displayed.
Note:
2.
Saving an auxiliary file to flash memory may disrupt traffic on the MP-1xx. To
avoid this, disable all traffic on the device before saving to flash memory.
Click the Save Configuration button in the middle of the screen; a confirmation message
appears when the save is complete.
Note:
A device reset is required to activate a loaded CPT file, and may be required
for the activation of certain ini file parameters.
¾ To reset the MP-1xx, take these 2 steps:
MP-1xx
1.
Click the Reset button on the main menu bar; the ‘Reset’ screen is displayed.
2.
Click the Reset button in the middle of the screen; the auxiliary files are saved into flash and
the MP-1xx restarts. This takes approximately 1 minute to complete. When the MP-1xx has
finished restarting, the Ready and LAN LEDs on the front panel are lit green.
38
Document #: LTRT-61405
Fast Track Installation Guide
8
8. MP-1xx IP <-> PBX Test Example
MP-1xx IP<->PBX Test Example
Analog Line Interconnect via the IP Network
Figure 8-1 shows AudioCodes’ MP-104/FXO mediating between the PBX/PSTN world and the IP
network. A is an enterprise User in Europe with its own PBX and AudioCodes’ MP-104/FXO
connected to analog lines. B is a SOHO (Small Office, Home Office) User in the USA, without a
PBX, but with AudioCodes’ MP-104/FXS connected to the phones.
A calling B scenario (Automatic dialing set in the ini file)
1. User A offhooks the phone, hears the enterprise PBX’s dial tone, and dials User B’s phone
number 4133; the call is routed to the analog line connected to the MP-104/FXO which routes
it to the MP-104/FXS that maps it to the phone of User B.
B calling A scenario (One-stage dialing set in the ini file)
1. User B offhooks the phone, hears the MP-104/FXS device’s dial tone, and dials 4247.
2. The MP-104/FXS device routes the call to the MP-104/FXO which dials it to the enterprise’s
PBX, which routes it to User A’s extension.
Figure 8-1: MP-104 IP<->PBX Test Example
Version 4.4
39
March 2005
MP-1xx
9
Regulatory Information
9.1
MP-11x FXS
Declaration of Conformity
Application of Council Directives:
73/23/EEC (including amendments),
89/336/EEC (including amendments),
Standards to which Conformity is Declared:
EN55022: 1998, Class B
EN55024:1998
EN61000-3-2: 1995
EN60950: 2000
(including amendments A1: 1998, A2: 1998, A14: 2000)
EN61000-3-3: 1995
Manufacturer’s Name:
AudioCodes Ltd.
Manufacturer’s Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Analog VoIP System.
Model Numbers:
MP-1xx/FXS
(xx- may represent 02,04,08)
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards.
th
Signature
I. Zusmanovich, Compliance Engineering Manager
11 February, 2005
Airport City, Lod, Israel
Date (Day/Month/Year)
Location
Czech
[AudioCodes Ltd] tímto prohlašuje, že tento [MP-1xx/FXS series] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice
89/336/EEC, 73/23/EEC.
Danish
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [MP-1xx/FXS Series] overholder de væsentlige krav og øvrige relevante krav i direktiv
89/336/EEC, 73/23/EEC.
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [MP-1xx/FXS Series] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van
richtlijn 89/336/EEC, 73/23/EEC
English
Hereby, [AudioCodes Ltd], declares that this [MP-1xx/FXS Series] is in compliance with the essential requirements and other relevant provisions of Directive
89/336/EEC, 73/23/EEC.
Estonian
Käesolevaga kinnitab [AudioCodes Ltd] seadme [MP-1xx/FXS Series] vastavust direktiivi 89/336/EEC, 73/23/EEC põhinõuetele ja nimetatud direktiivist
tulenevatele teistele asjakohastele sätetele.
Finnish
[AudioCodes Ltd] vakuuttaa täten että [MP-1xx/FXS Series] tyyppinen laite on direktiivin 89/336/EEC, 73/23/EEC oleellisten vaatimusten ja sitä koskevien
direktiivin muiden ehtojen mukainen.
French
Par la présente [AudioCodes Ltd] déclare que l'appareil [MP-1xx/FXS Series] est conforme aux exigences essentielles et aux autres dispositions pertinentes de
la directive 89/336/EEC, 73/23/EEC
German
Hiermit erklärt [AudioCodes Ltd], dass sich dieser/diese/dieses [MP-1xx/FXS Series] in Übereinstimmung mit den grundlegenden Anforderungen und den
anderen relevanten Vorschriften der Richtlinie 89/336/EEC, 73/23/EEC befindet". (BMWi)
Greek
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [AudioCodes Ltd] ∆ΗΛΩΝΕΙ ΟΤΙ [MP-1xx/FXS Series] ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ
ΣΧΕΤΙΚΕΣ ∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 89/336/EEC, 73/23/EEC
Hungarian
Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-1xx/FXS Series] megfelel a vonatkozó alapvetõ követelményeknek és az 89/336/EEC, 73/23/EEC irányelv
egyéb elõírásainak
Icelandic
æki þetta er í samræmi við tilskipun Evrópusambandsins 89/336/EEC, 73/23/EEC
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (MP-1xx/FXS Series) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla
direttiva 89/336/EEC, 73/23/EEC.
Latvian
Ar šo [AudioCodes Ltd] deklarē, ka [MP-1xx/FXS Series] atbilst Direktīvas 89/336/EEC, 73/23/EEC būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [MP-1xx/FXS Series] tenkina 89/336/EEC, 73/23/EEC Direktyvos esminius reikalavimus ir kitas sios direktyvos
nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [MP-1xx/FXS Series] jikkonforma mal-ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva
89/336/EEC, 73/23/EEC
Norwegian
Dette produktet er i samhørighet med det Europeiske Direktiv 89/336/EEC, 73/23/EEC
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrób [MP-1xx/FXS Series] spelnia podstawowe wymagania i odpowiada warunkom zawartym w
dyrektywie 89/336/EEC, 73/23/EEC
Portuguese
[AudioCodes Ltd] declara que este [MP-1xx/FXS Series] está conforme com os requisitos essenciais e outras disposições da Directiva 89/336/EEC, 73/23/EEC.
Slovak
[AudioCodes Ltd] týmto vyhlasuje, že [MP-1xx/FXS Series] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 89/336/EEC, 73/23/EEC.
Slovene
Šiuo [AudioCodes Ltd] deklaruoja, kad šis [MP-1xx/FXS Series] atitinka esminius reikalavimus ir kitas 89/336/EEC, 73/23/EEC Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (MP-1xx/FXS Series) cumple con los requisitos esenciales y cualesquiera otras disposiciones
aplicables o exigibles de la Directiva 89/336/EEC, 73/23/EEC
Swedish
Härmed intygar [AudioCodes Ltd] att denna [MP-1xx/FXS Series] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser
som framgår av direktiv 89/336/EEC, 73/23/EEC.
MP-1xx
40
Document #: LTRT-61405
Fast Track Installation Guide
9. Regulatory Information
Safety Notice
Installation and service of this card must only be performed by authorized, qualified service personnel.
The protective earth terminal on the back of the MP-1xx must be permanently connected to protective earth.
Telecommunication Safety
The safety status of each port on the gateway is declared and detailed in the table below:
TNV-3:
Ports
Safety Status
Ethernet (100 Base-TX)
SELV
FXS (ODP P/N’s)
FXS
TNV-3
TNV-2
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating
conditions and on which over voltages from Telecommunication Networks are possible
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating
conditions and is not subjected to over voltages from Telecommunication Networks
Safety extra low voltage circuit.
TNV-2:
SELV:
FCC Statement
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This
equipment generates uses and can and can radiate radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However there is no guarantee that interference will not
occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
9.2
MP-11x FXO
Declaration of Conformity
Application of Council Directives:
73/23/EEC (including amendments),
89/336/EEC (including amendments),
1999/5/EC Annex-II of the Directive
Standards to which Conformity is Declared:
EN55022: 1998, Class B
EN55024:1998
EN61000-3-2: 1995
(including amendments A1: 1998, A2: 1998, A14: 2000)
EN61000-3-3: 1995
EN60950: 2000
TBR-21: 1998
Manufacturer’s Name:
AudioCodes Ltd.
Manufacturer’s Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Analog VoIP System.
Model Numbers:
MP-1xx/FXO
(xx- may represent 02, 04, 08)
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards.
th
Signature
11 February 2005
Date (Day/Month/Year)
Airport City, Lod, Israel
Location
I. Zusmanovich, Compliance Engineering Manager
Version 4.4
41
March 2005
MP-1xx
Czech
[AudioCodes Ltd] tímto prohlašuje, že tento [MP-1xx/FXO] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES."
Danish
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [MP-1xx/FXO] overholder de væsentlige krav og øvrige relevante krav i direktiv
1999/5/EF
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [MP-1xx/FXO] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van
richtlijn 1999/5/EG
English
Hereby, [AudioCodes Ltd], declares that this [MP-1xx/FXO] is in compliance with the essential requirements and other relevant provisions of Directive
1999/5/EC.
Estonian
Käesolevaga kinnitab [AudioCodes Ltd] seadme [MP-1xx/FXO] vastavust direktiivi 1999/5/EÜ põhinõuetele ja nimetatud direktiivist tulenevatele teistele
asjakohastele sätetele.
Finnish
[AudioCodes Ltd] vakuuttaa täten että [MP-1xx/FXO] tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden
ehtojen mukainen.
French
Par la présente [AudioCodes Ltd] déclare que l'appareil [MP-1xx/FXO] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la
directive 1999/5/CE
German
Hiermit erklärt [AudioCodes Ltd], dass sich dieser/diese/dieses [MP-1xx/FXO] in Übereinstimmung mit den grundlegenden Anforderungen und den anderen
relevanten Vorschriften der Richtlinie 1999/5/EG befindet". (BMWi)
Greek
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [AudioCodes Ltd] ∆ΗΛΩΝΕΙ ΟΤΙ [MP-1xx/FXO] ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ
∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 1999/5/ΕΚ
Hungarian
Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-1xx/FXO] megfelel a vonatkozó alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb
elõírásainak
Icelandic
æki þetta er í samræmi við tilskipun Evrópusambandsins 1999/5
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (MP-1xx/FXO) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla
direttiva 1999/5/CE.
Latvian
Ar šo [AudioCodes Ltd] deklarē, ka [MP-1xx/FXO] atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [MP-1xx/FXO] tenkina 1999/5/EB Direktyvos esminius reikalavimus ir kitas sios direktyvos nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [MP-1xx/FXO] jikkonforma mal-ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva
1999/5/EC
Norwegian
Dette produktet er i samhørighet med det Europeiske Direktiv 1999/5
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrób [MP-1xx/FXO] spelnia podstawowe wymagania i odpowiada warunkom zawartym w
dyrektywie 1999/5/EC
Portuguese
[AudioCodes Ltd] declara que este [MP-1xx/FXO] está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE.
Slovak
[AudioCodes Ltd] týmto vyhlasuje, že [MP-1xx/FXO] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 1999/5/ES.
Slovene
Šiuo [AudioCodes Ltd] deklaruoja, kad šis [MP-1xx/FXO] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (MP-1xx/FXO) cumple con los requisitos esenciales y cualesquiera otras disposiciones
aplicables o exigibles de la Directiva 1999/5/CE
Swedish
Härmed intygar [AudioCodes Ltd] att denna [MP-1xx/FXO] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser
som framgår av direktiv 1999/5/EG.
Safety Notice
Installation and service of this unit must only be performed by authorized, qualified service personnel.
The protective earth terminal on the back of the MP-1xx must be permanently connected to protective earth.
Industry Canada Notice
This equipment meets the applicable Industry Canada Terminal Equipment technical specifications. This is confirmed by the
registration numbers. The abbreviation, IC, before the registration number signifies that registration was performed based on a
declaration of conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry
Canada approved the equipment.
Network Compatibility
The products support the Telecom networks in EU that comply with TBR21.
Telecommunication Safety
The safety status of each port is declared and detailed in the table below:
Ports
Safety Status
Ethernet (100 Base-TX)
SELV
FXO
TNV-3
TNV-3:
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating conditions
and on which over voltages from Telecommunication Networks are possible.
SELV:
Safety extra low voltage circuit.
MP-1xx
42
Document #: LTRT-61405
Fast Track Installation Guide
9. Regulatory Information
MP-1xx/FXO Notice
The MP-1xx FXO Output Tones and DTMF level should not exceed -9 dBm (AudioCodes setting #23) in order to comply with
FCC 68, TIA/EIA/IS-968 and TBR-21.
The maximum allowed gain between any 2 ports connected to the PSTN should be set to 0 dB in order to comply with FCC 68,
TIA/EIA/IS-968 Signal power limitation
FCC Statement
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However there is no guarantee that interference will not
occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
9.3
MP-124
Declaration of Conformity
Application of Council Directives:
73/23/EEC (including amendments),
89/336/EEC (including amendments),
Standards to which Conformity is Declared:
EN55022: 1998, Class A
EN55024:1998
EN61000-3-2: 1995
(including amendments A1: 1998, A2: 1998, A14: 2000)
EN61000-3-3: 1995
EN60950: 1992 Including amendments 1,2,3,4 and 11
Manufacturer’s Name: :
AudioCodes Ltd.
Manufacturer’s Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Analog VoIP System.
Model Numbers:
MP-124/FXS
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards.
th
Signature
I. Zusmanovich, Compliance Engineering Manager
11 February, 2005
Airport City, Lod, Israel
Date (Day/Month/Year)
Location
Czech
[AudioCodes Ltd] tímto prohlašuje, že tento [MP-124] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 89/336/EEC,
73/23/EEC.
Danish
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [MP-124] overholder de væsentlige krav og øvrige relevante krav i direktiv 89/336/EEC,
73/23/EEC.
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [MP-124] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn
89/336/EEC, 73/23/EEC
English
Hereby, [AudioCodes Ltd], declares that this [MP-124] is in compliance with the essential requirements and other relevant provisions of Directive 89/336/EEC,
73/23/EEC.
Estonian
Käesolevaga kinnitab [AudioCodes Ltd] seadme [MP-124] vastavust direktiivi 89/336/EEC, 73/23/EEC põhinõuetele ja nimetatud direktiivist tulenevatele teistele
asjakohastele sätetele.
Finnish
[AudioCodes Ltd] vakuuttaa täten että [MP-124] tyyppinen laite on direktiivin 89/336/EEC, 73/23/EEC oleellisten vaatimusten ja sitä koskevien direktiivin muiden
ehtojen mukainen.
French
Par la présente [AudioCodes Ltd] déclare que l'appareil [MP-124] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive
89/336/EEC, 73/23/EEC
German
Hiermit erklärt [AudioCodes Ltd], dass sich dieser/diese/dieses [MP-124] in Übereinstimmung mit den grundlegenden Anforderungen und den anderen relevanten
Vorschriften der Richtlinie 89/336/EEC, 73/23/EEC befindet". (BMWi)
Greek
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [AudioCodes Ltd] ∆ΗΛΩΝΕΙ ΟΤΙ [MP-124] ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ
∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 89/336/EEC, 73/23/EEC
Hungarian
Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-124] megfelel a vonatkozó alapvetõ követelményeknek és az 89/336/EEC, 73/23/EEC irányelv egyéb
elõírásainak
Icelandic
æki þetta er í samræmi við tilskipun Evrópusambandsins 89/336/EEC, 73/23/EEC
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (MP-124) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla directiva
89/336/EEC, 73/23/EEC.
Version 4.4
43
March 2005
MP-1xx
Latvian
Ar šo [AudioCodes Ltd] deklarē, ka [MP-124] atbilst Direktīvas 89/336/EEC, 73/23/EEC būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [MP-124] tenkina 89/336/EEC, 73/23/EEC Direktyvos esminius reikalavimus ir kitas sios direktyvos nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [MP-124] jikkonforma mal-ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva 89/336/EEC,
73/23/EEC
Norwegian
Dette produktet er i samhørighet med det Europeiske Direktiv 89/336/EEC, 73/23/EEC
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrób [MP-124] spelnia podstawowe wymagania i odpowiada warunkom zawartym w dyrektywie
89/336/EEC, 73/23/EEC
Portuguese
[AudioCodes Ltd] declara que este [MP-124] está conforme com os requisitos essenciais e outras disposições da Directiva 89/336/EEC, 73/23/EEC.
Slovak
[AudioCodes Ltd] týmto vyhlasuje, že [MP-124 Series] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 89/336/EEC, 73/23/EEC.
Slovene
Šiuo [AudioCodes Ltd] deklaruoja, kad šis [MP-124 Series] atitinka esminius reikalavimus ir kitas 89/336/EEC, 73/23/EEC Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (MP-124 Series) cumple con los requisitos esenciales y cualesquiera otras disposiciones aplicables o
exigibles de la Directiva 89/336/EEC, 73/23/EEC
Swedish
Härmed intygar [AudioCodes Ltd] att denna [MP-124 Series] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser som
framgår av direktiv 89/336/EEC, 73/23/EEC.
Safety Notice
Installation and service of this unit must only be performed by authorized, qualified service personnel.
The protective earth terminal on the back of the MP-124 must be permanently connected to protective earth.
Telecommunication Safety
The safety status of each port on the gateway is declared and detailed in the table below:
TNV-3:
TNV-2:
Ports
Safety Status
Ethernet (100 Base-TX)
FXS (ODP P/N’s)
FXS
SELV
TNV-3
TNV-2
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating
conditions and on which over voltages from Telecommunication Networks are possible
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating
conditions and is not subjected to over voltages from Telecommunication Networks
SELV:
Safety extra low voltage circuit.
FCC Statement
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated
in a commercial environment. This equipment generates uses and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.
This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
Original
printed on
recycled paper
and available on
CD or Web site
MP-1xx
44
Document #: LTRT-61405
AudioCodes Offices
International Headquarters
AudioCodes Ltd, 1 Hayarden Street, Airport City
Lod 70151, Israel.
Tel: +972-3-976 4000
Fax: +972-3-976 4040
USA Headquarters
AudioCodes Inc, 2890 Zanker Road, Suite # 200
San Jose, CA 95134
Tel: +1-408-577-0488
Fax: +1-408-577-0492
AudioCodes Offices Worldwide
Beijing, Boston (MA), Chicago (IL), London
Mexico City, Paris, Raleigh (NC), Somerset (NJ), Tokyo
info@audiocodes.com
www.audiocodes.com
MP-1xx SIP User’s Manual
Version 4.4
Document #: LTRT-65404
Notice
This document describes the AudioCodes MediaPack Series MP-1xx Voice over IP (VoIP) 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. Updates to this document and other documents can be viewed by registered Technical
Support customers at www.audiocodes.com under Support / Product Documentation.
© Copyright 2005 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: Mar-01-2005
Date Printed: Mar-16-2005
MP-1xx SIP User’s Manual
Contents
Table of Contents
1
Overview ....................................................................................................................15
1.1
1.2
1.3
1.4
2
Introduction .....................................................................................................................................15
Gateway Description.......................................................................................................................15
SIP Overview ..................................................................................................................................17
MP-1xx Features ............................................................................................................................18
1.4.1 General Features ....................................................................................................................18
1.4.2 Hardware Features .................................................................................................................18
1.4.3 SIP Features ...........................................................................................................................18
MP-1xx Physical Description....................................................................................21
2.1
MP-1xx Front Panel ........................................................................................................................21
2.1.1 MP-1xx Front Panel Buttons ...................................................................................................21
2.1.2 MP-1xx Front Panel LEDs ......................................................................................................22
2.2 MP-1xx Rear Panel.........................................................................................................................22
2.2.1 MP-10x Rear Panel.................................................................................................................22
2.2.2 MP-124 Rear Panel ................................................................................................................23
3
Installing the MP-1xx.................................................................................................25
3.1
3.2
3.3
Unpacking.......................................................................................................................................25
Package Contents ..........................................................................................................................25
Mounting the MP-1xx......................................................................................................................26
3.3.1 Mounting the MP-1xx on a Desktop........................................................................................26
3.3.2 Installing the MP-10x in a 19-inch Rack .................................................................................26
3.3.3 Installing the MP-124 in a 19-inch Rack .................................................................................27
3.3.4 Mounting the MP-10x on a Wall..............................................................................................28
3.4 Cabling the MP-1xx ........................................................................................................................29
3.4.1 Connecting the MP-1xx RS-232 Port to Your PC ...................................................................32
3.4.1.1 Configuring the Serial Connection................................................................................32
3.4.2 Cabling the Lifeline Phone ......................................................................................................32
4
Getting Started...........................................................................................................35
4.1
Assigning the MP-1xx IP Address ..................................................................................................35
4.1.1 Assigning an IP Address Using HTTP ....................................................................................35
4.1.2 Assigning an IP Address Using BootP....................................................................................36
4.2 Restoring Networking Parameters to their Initial State...................................................................36
4.3 Configure the MP-1xx Basic Parameters .......................................................................................37
5
Configuring the MP-1xx ............................................................................................39
5.1
5.2
5.3
5.4
Configuration Concepts ..................................................................................................................39
Overview of the Embedded Web Server ........................................................................................39
Computer Requirements.................................................................................................................39
Password Control ...........................................................................................................................40
5.4.1 Embedded Web Server Username & Password.....................................................................40
5.5 Configuring the Web Interface via the ini File.................................................................................40
5.5.1 Limiting the Embedded Web Server to Read-Only Mode.......................................................40
5.5.2 Disabling the Embedded Web Server.....................................................................................40
5.6 Accessing the Embedded Web Server...........................................................................................41
5.6.1 Using Internet Explorer to Access the Embedded Web Server..............................................41
5.7 Getting Acquainted with the Web Interface ....................................................................................42
5.7.1 Main Menu Bar........................................................................................................................42
5.7.2 Saving Changes......................................................................................................................43
5.7.3 Entering Phone Numbers in Various Tables...........................................................................43
5.8 Protocol Management.....................................................................................................................44
5.8.1 Protocol Definition Parameters ...............................................................................................44
5.8.1.1 General Parameters .....................................................................................................44
5.8.1.2 Proxy & Registration Parameters .................................................................................48
5.8.1.3 Coders ..........................................................................................................................53
5.8.1.4 DTMF & Dialing Parameters.........................................................................................55
Version 4.4
3
March 2005
MP-1xx SIP
5.8.2 Configuring the Advanced Parameters...................................................................................58
5.8.2.1 General Parameters .....................................................................................................58
5.8.2.2 Supplementary Services...............................................................................................63
5.8.2.3 Keypad Features ..........................................................................................................66
5.8.3 Configuring the Number Manipulation Tables ........................................................................68
5.8.3.1 Dialing Plan Notation ....................................................................................................71
5.8.4 Configuring the Routing Tables ..............................................................................................73
5.8.4.1 General Parameters .....................................................................................................73
5.8.4.2 Tel to IP Routing Table .................................................................................................75
5.8.4.3 IP to Hunt Group Routing .............................................................................................78
5.8.4.4 Internal DNS Table .......................................................................................................80
5.8.4.5 Reasons for Alternative Routing...................................................................................81
5.8.5 Configuring the Profile Definitions ..........................................................................................83
5.8.5.1 Coder Group Settings ...................................................................................................83
5.8.5.2 Tel Profile Settings........................................................................................................85
5.8.5.3 IP Profile Settings .........................................................................................................87
5.8.6 Configuring the Endpoint Phone Numbers .............................................................................89
5.8.7 Configuring the Hunt Group Settings......................................................................................91
5.8.8 Configuring the Endpoint Settings ..........................................................................................93
5.8.8.1 Authentication ...............................................................................................................93
5.8.8.2 Automatic Dialing..........................................................................................................94
5.8.8.3 Caller ID ........................................................................................................................95
5.8.8.4 Call Forward .................................................................................................................96
5.8.8.5 Caller ID Permissions ...................................................................................................98
5.8.9 Configuring the FXO Parameters............................................................................................99
5.8.10 Protocol Management ini File Parameters............................................................................101
5.9 Advanced Configuration ...............................................................................................................103
5.9.1 Configuring the Network Settings .........................................................................................103
5.9.1.1 Configuring the SNMP Managers Table.....................................................................107
5.9.1.2 Multiple Routers Support ............................................................................................112
5.9.1.3 Simple Network Time Protocol Support......................................................................112
5.9.2 Configuring the Channel Settings .........................................................................................113
5.9.2.1 Dynamic Jitter Buffer Operation .................................................................................120
5.9.3 Restoring and Backing up the Gateway Configuration.........................................................121
5.9.4 Regional Settings..................................................................................................................122
5.9.5 Changing the MP-1xx Username and Password..................................................................123
5.10 Status & Diagnostics.....................................................................................................................124
5.10.1 Gateway Statistics ................................................................................................................124
5.10.1.1 IP Connectivity............................................................................................................124
5.10.1.2 Call Counters ..............................................................................................................125
5.10.2 Monitoring the MP-1xx Channels..........................................................................................127
5.10.3 Activating the Internal Syslog Viewer ...................................................................................129
5.10.4 System Information ...............................................................................................................130
5.11 Software Update ...........................................................................................................................131
5.11.1 Software Upgrade Wizard.....................................................................................................131
5.11.2 Auxiliary Files ........................................................................................................................137
5.11.2.1 Loading the Auxiliary Files via the ini File...................................................................138
5.12 Save Configuration .......................................................................................................................139
5.13 Resetting the MP-1xx ...................................................................................................................140
6
ini File Configuration of the MP-1xx ...................................................................... 141
6.1
6.2
6.3
7
Secured ini File .............................................................................................................................141
Modifying an ini File ......................................................................................................................141
The ini File Structure.....................................................................................................................142
6.3.1 The ini File Structure Rules...................................................................................................142
6.3.2 The ini File Example .............................................................................................................142
Configuration Files.................................................................................................. 143
7.1
Configuring the Call Progress Tones and Distinctive Ringing File...............................................143
7.1.1 Format of the Call Progress Tones Section in the ini File ....................................................143
7.1.2 Format of the Distinctive Ringing Section in the ini File .......................................................145
7.1.2.1 Examples of Various Ringing Signals.........................................................................146
MP-1xx SIP User’s Manual
4
Document #: LTRT-65404
MP-1xx SIP User’s Manual
Contents
7.2
Prerecorded Tones (PRT) File .....................................................................................................147
7.2.1 PRT File Format....................................................................................................................147
7.3 The Coefficient Configuration File ................................................................................................148
8
Gateway Capabilities Description .......................................................................... 149
8.1
8.2
8.3
Proxy or Registrar Registration Example .....................................................................................149
Configuring the DTMF Transport Types .......................................................................................150
Configuring the Gateway’s Alternative Routing (based on Connectivity and QoS)......................152
8.3.1 Alternative Routing Mechanism ............................................................................................152
8.3.2 Determining the Availability of Destination IP Addresses.....................................................152
8.3.3 Relevant Parameters ............................................................................................................153
8.4 Working with Supplementary Services .........................................................................................153
8.4.1 Call Hold and Retrieve ..........................................................................................................153
8.4.1.1 Initiating Hold/Retrieve................................................................................................153
8.4.1.2 Receiving Hold / Retrieve ...........................................................................................154
8.4.2 Consultation / Alternate.........................................................................................................154
8.4.3 Call Transfer..........................................................................................................................154
8.4.4 Call Forward..........................................................................................................................155
8.4.5 Call Waiting ...........................................................................................................................155
8.4.6 Message Waiting Indication ..................................................................................................156
8.5 Call Termination on MP-1xx/FXO.................................................................................................156
8.6 Mapping PSTN Release Cause to SIP Response .......................................................................157
8.7 Call Detail Report..........................................................................................................................158
8.8 Metering Tones Relay...................................................................................................................159
8.9 Configuration Examples................................................................................................................160
8.9.1 Establishing a Call between Two Gateways.........................................................................160
8.9.2 SIP Call Flow.........................................................................................................................161
8.9.3 SIP Authentication Example .................................................................................................163
8.9.4 Remote IP Extension between FXO and FXS ......................................................................165
8.9.4.1 Dialing from Remote Extension ..................................................................................166
8.9.4.2 Dialing from other PBX line, or from PSTN ................................................................166
8.9.4.3 MP-108/FXS Configuration (using the Embedded Web Server) ................................167
8.9.4.4 MP-108/FXO Configuration (using the Embedded Web Server)................................168
9
Diagnostics .............................................................................................................. 169
9.1
MP-1xx Self-Testing .....................................................................................................................169
9.1.1 Rapid Self-Test Mode ...........................................................................................................169
9.1.2 Detailed Self-Test Mode .......................................................................................................169
9.2 Troubleshooting the MP-1xx via the RS-232 Port ........................................................................170
9.2.1 Viewing the Gateway’s Information ......................................................................................170
9.2.2 Changing the Networking Parameters..................................................................................170
9.3 Syslog Support .............................................................................................................................171
9.3.1 Syslog Servers ......................................................................................................................171
9.3.2 Operation ..............................................................................................................................171
9.3.2.1 Sending the Syslog Messages ...................................................................................171
9.3.2.2 Setting the Syslog Server ...........................................................................................171
9.3.2.3 The ini File Example for Syslog ..................................................................................172
9.4 Solutions to Possible Problems ....................................................................................................172
9.4.1 General .................................................................................................................................172
10 BootP/DHCP Support .............................................................................................. 173
10.1 Startup Process ............................................................................................................................173
10.2 DHCP Support ..............................................................................................................................175
10.3 BootP Support ..............................................................................................................................176
10.3.1 Upgrading the MP-1xx ..........................................................................................................176
10.3.2 Vendor Specific Information Field .........................................................................................176
11 SNMP-Based Management ..................................................................................... 179
11.1 About SNMP .................................................................................................................................179
11.1.1 SNMP Message Standard ....................................................................................................179
11.1.2 SNMP MIB Objects ...............................................................................................................180
Version 4.4
5
March 2005
MP-1xx SIP
11.1.3 SNMP Extensibility Feature ..................................................................................................180
11.2 Carrier Grade Alarm System ........................................................................................................181
11.2.1 Active Alarm Table................................................................................................................181
11.2.2 Alarm History.........................................................................................................................181
11.3 Cold Start Trap .............................................................................................................................181
11.4 Third-Party Performance Monitoring Measurements ...................................................................182
11.5 Supported MIBs ............................................................................................................................182
11.6 SNMP Interface Details ................................................................................................................185
11.6.1 SNMP Community Names ....................................................................................................185
11.6.1.1 Configuration of Community Strings via the ini File....................................................185
11.6.1.2 Configuration of Community Strings via SNMP..........................................................185
11.6.2 Trusted Managers.................................................................................................................186
11.6.2.1 Configuration of Trusted Managers via ini File ...........................................................186
11.6.2.2 Configuration of Trusted Managers via SNMP ...........................................................186
11.6.3 SNMP Ports ..........................................................................................................................187
11.6.4 Multiple SNMP Trap Destinations .........................................................................................188
11.6.4.1 Configuration via the ini File .......................................................................................188
11.6.4.2 Configuration via SNMP .............................................................................................189
11.7 SNMP Manager Backward Compatibility......................................................................................190
11.8 AudioCodes’ Element Management System ................................................................................190
12 Selected Technical Specifications ......................................................................... 191
Appendix A
MP-1xx SIP Software Kit....................................................................... 195
Appendix B
The BootP/TFTP Configuration Utility................................................. 197
B.1 When to Use the BootP/TFTP ......................................................................................................197
B.2 An Overview of BootP...................................................................................................................197
B.3 Key Features ................................................................................................................................197
B.4 Specifications................................................................................................................................198
B.5 Installation.....................................................................................................................................198
B.6 Loading the cmp File, Booting the Device ....................................................................................198
B.7 BootP/TFTP Application User Interface........................................................................................199
B.8 Function Buttons on the Main Screen ..........................................................................................199
B.9 Log Window ..................................................................................................................................200
B.10 Setting the Preferences ................................................................................................................201
B.10.1 BootP Preferences................................................................................................................201
B.10.2 TFTP Preferences.................................................................................................................202
B.11 Configuring the BootP Clients ......................................................................................................203
B.11.1 Adding Clients .......................................................................................................................203
B.11.2 Deleting Clients .....................................................................................................................204
B.11.3 Editing Client Parameters .....................................................................................................204
B.11.4 Testing the Client ..................................................................................................................204
B.11.5 Setting Client Parameters .....................................................................................................205
B.11.6 Using Command Line Switches ............................................................................................206
B.12 Managing Client Templates..........................................................................................................207
Appendix C
C.1
C.2
C.3
RTP/RTCP Payload Types and Port Allocation .................................. 209
Packet Types Defined in RFC 1890 .............................................................................................209
Defined Payload Types.................................................................................................................209
Default RTP/RTCP/T.38 Port Allocation.......................................................................................210
Appendix D
Fax & Modem Transport Modes .......................................................... 211
D.1 Fax/Modem Settings.....................................................................................................................211
D.2 Configuring Fax Relay Mode ........................................................................................................211
D.3 Configuring Fax/Modem Bypass Mode ........................................................................................211
D.4 Supporting V.34 Faxes .................................................................................................................212
D.4.1 Using Bypass Mechanism for V.34 Fax Transmission .........................................................212
D.4.2 Using Relay mode for both T.30 and V.34 faxes ..................................................................212
Appendix E
E.1
Customizing the MP-1xx Web Interface .............................................. 213
Replacing the Main Corporate Logo.............................................................................................213
MP-1xx SIP User’s Manual
6
Document #: LTRT-65404
MP-1xx SIP User’s Manual
Contents
E.1.1 Replacing the Main Corporate Logo with an Image File.......................................................213
E.1.2 Replacing the Main Corporate Logo with a Text String ........................................................215
E.2 Replacing the Background Image File..........................................................................................215
E.3 Customizing the Product Name....................................................................................................216
E.4 Modifying ini File Parameters via the Web AdminPage ...............................................................217
Appendix F
Accessory Programs and Tools .......................................................... 219
F.1 TrunkPack Downloadable Conversion Utility................................................................................219
F.1.1 Converting a CPT ini File to a Binary dat File.......................................................................220
F.1.2 Encoding / Decoding an ini File ............................................................................................221
F.1.3 Creating a Loadable Prerecorded Tones File.......................................................................222
F.2 Call Progress Tones Wizard .........................................................................................................224
F.2.1 About the Call Progress Tones Wizard.................................................................................224
F.2.2 Installation .............................................................................................................................224
F.2.3 Initial Settings........................................................................................................................224
F.2.4 Recording Screen – Automatic Mode ...................................................................................225
F.2.5 Recording Screen – Manual Mode .......................................................................................226
F.2.6 The Call Progress Tones ini File...........................................................................................227
Appendix G
SNMP Traps........................................................................................... 229
G.1 Alarm Traps ..................................................................................................................................229
G.1.1 Component: System#0 .........................................................................................................229
G.1.2 Component: AlarmManager#0..............................................................................................231
G.1.3 Component: EthernetLink#0 .................................................................................................231
G.1.4 Other Traps ...........................................................................................................................232
G.1.5 Trap Varbinds........................................................................................................................232
Appendix H
H.1
H.2
H.3
Regulatory Information ........................................................................ 233
MP-11x FXS .................................................................................................................................233
MP-11x FXO .................................................................................................................................234
MP-124 .........................................................................................................................................236
Version 4.4
7
March 2005
MP-1xx SIP
List of Figures
Figure 1-1: MP-124 Gateway Front View .........................................................................................................15
Figure 1-2: MP-108 Gateway Front View .........................................................................................................16
Figure 1-3: MP-104 Gateway Front View .........................................................................................................16
Figure 1-4: MP-102 Gateway Front View .........................................................................................................16
Figure 1-5: Typical MP-1xx VoIP Application ...................................................................................................17
Figure 2-1: MP-108 Front Panel .......................................................................................................................21
Figure 2-2: MP-124 Front Panel .......................................................................................................................21
Figure 2-3: MP-104/FXS Rear Panel Connectors ............................................................................................23
Figure 2-4: MP-124 (FXS) Rear Panel Connectors..........................................................................................23
Figure 3-1: Desktop or Shelf Mounting.............................................................................................................26
Figure 3-2: MP-108 with Brackets for Rack Installation ...................................................................................27
Figure 3-3: MP-124 with Brackets for Rack Installation ...................................................................................28
Figure 3-4: MP-102 Wall Mount........................................................................................................................28
Figure 3-5: RJ-45 Ethernet Connector Pinout ..................................................................................................30
Figure 3-6: RJ-11 Phone Connector Pinout .....................................................................................................30
Figure 3-7: 50-pin Telco Connector (MP-124/FXS only) ..................................................................................30
Figure 3-8: MP-124 in a 19-inch Rack with MDF Adaptor................................................................................30
Figure 3-9: DC Power Supply on the MP-124 ..................................................................................................31
Figure 3-10: RS-232 Cable Wiring ...................................................................................................................32
Figure 3-11: Lifeline Splitter Pinout & RJ-11 Connector for MP-10x/FXS........................................................32
Figure 3-12: MP-104/FXS Lifeline Setup..........................................................................................................33
Figure 4-1: Quick Setup Screen .......................................................................................................................37
Figure 5-1: Embedded Web Server Login Screen ...........................................................................................41
Figure 5-2: MP-1xx Web Interface....................................................................................................................42
Figure 5-3: Protocol Definition, General Parameters Screen ...........................................................................44
Figure 5-4: Proxy & Registration Parameters Screen ......................................................................................48
Figure 5-5: Coders Screen ...............................................................................................................................53
Figure 5-6: DTMF & Dialing Parameters Screen..............................................................................................55
Figure 5-7: Advanced Parameters, General Parameters Screen ....................................................................58
Figure 5-8: Supplementary Services Parameters Screen ................................................................................63
Figure 5-9: Keypad Features Screen ...............................................................................................................66
Figure 5-10: Source Phone Number Manipulation Table for Tel IP calls ......................................................68
Figure 5-11: Routing Tables, General Parameters Screen ..............................................................................73
Figure 5-12: Tel to IP Routing Table Screen....................................................................................................76
Figure 5-13: IP to Hunt Group Routing Table Screen ......................................................................................78
Figure 5-14: Internal DNS Table Screen ..........................................................................................................80
Figure 5-15: Reasons for Alternative Routing Screen......................................................................................81
Figure 5-16: Coder Group Settings Screen ......................................................................................................83
Figure 5-17: Tel Profile Settings Screen...........................................................................................................85
Figure 5-18: IP Profile Settings Screen ............................................................................................................87
Figure 5-19: Endpoint Phone Number Table Screen .......................................................................................89
Figure 5-20: Hunt Group Settings screen.........................................................................................................91
Figure 5-21: Authentication Screen ..................................................................................................................93
Figure 5-22: Automatic Dialing Table Screen...................................................................................................94
Figure 5-23: Caller Display Information Screen ...............................................................................................95
Figure 5-24: Call Forwarding Table Screen .....................................................................................................96
Figure 5-25: MP-1xx FXS Caller ID Permission Screen...................................................................................98
Figure 5-26: FXO Settings Screen ...................................................................................................................99
Figure 5-27: Network Settings Screen............................................................................................................103
Figure 5-28: SNMP Managers Table Screen .................................................................................................107
Figure 5-29: Channel Settings, Voice Settings Parameters ...........................................................................113
Figure 5-30: Channel Settings, Fax/Modem/CID Parameters........................................................................115
Figure 5-31: Channel Settings, RTP Parameters...........................................................................................117
Figure 5-32: Channel Settings, Miscellaneous Parameters ...........................................................................118
Figure 5-33: Configuration File Screen...........................................................................................................121
Figure 5-34: Regional Settings Screen...........................................................................................................122
Figure 5-35: Change Password Screen .........................................................................................................123
Figure 5-36: IP Connectivity Screen...............................................................................................................124
Figure 5-37: Tel IP Call Counters Screen ....................................................................................................126
MP-1xx SIP User’s Manual
8
Document #: LTRT-65404
MP-1xx SIP User’s Manual
Contents
Figure 5-38: MP-1xx/FXS Channel Status Screen.........................................................................................127
Figure 5-39: Channel Status Details Screen ..................................................................................................128
Figure 5-40: Message Log Screen .................................................................................................................129
Figure 5-41: System Information Screen........................................................................................................130
Figure 5-42: Start Software Upgrade Screen .................................................................................................131
Figure 5-43: Load a cmp File Screen .............................................................................................................132
Figure 5-44: cmp File Successfully Loaded into the MP-1xx Notification ......................................................133
Figure 5-45: Load an ini File Screen ..............................................................................................................134
Figure 5-46: Load a CPT File Screen.............................................................................................................135
Figure 5-47: FINISH Screen ...........................................................................................................................136
Figure 5-48: ‘End Process’ Screen.................................................................................................................136
Figure 5-49: Auxiliary Files Screen.................................................................................................................138
Figure 5-50: Save Configuration Screen ........................................................................................................139
Figure 5-51: Reset Screen .............................................................................................................................140
Figure 6-1: ini File Structure ...........................................................................................................................142
Figure 6-2: SIP ini File Example .....................................................................................................................142
Figure 7-1: Call Progress Tone Types............................................................................................................144
Figure 7-2: Defining a Dial Tone Example .....................................................................................................145
Figure 7-3: Examples of Various Ringing Signals ..........................................................................................146
Figure 8-1: Metering Tone Relay Architecture ...............................................................................................159
Figure 8-2: Proprietary Info Message for Relaying Metering Tones ..............................................................159
Figure 8-3: SIP Call Flow................................................................................................................................161
Figure 8-4: MP-108 FXS & FXO Remote IP Extension..................................................................................166
Figure 9-1: Status and Error Messages..........................................................................................................170
Figure 9-2: Setting the Syslog Server IP Address..........................................................................................172
Figure 9-3: The ini File Example for Syslog....................................................................................................172
Figure 10-1: MP-1xx Startup Process ............................................................................................................174
Figure 11-1: Example of Entries in a Device ini file Regarding SNMP...........................................................189
Figure B-1: Main Screen.................................................................................................................................199
Figure B-2: Reset Screen ...............................................................................................................................199
Figure B-3: Preferences Screen .....................................................................................................................201
Figure B-4: Client Configuration Screen.........................................................................................................203
Figure B-5: Templates Screen........................................................................................................................207
Figure E-1: User-Customizable Web Interface Title Bar ................................................................................213
Figure E-2: Customized Web Interface Title Bar............................................................................................213
Figure E-3: Image Download Screen .............................................................................................................214
Figure E-4: INI Parameters Screen ................................................................................................................217
Figure F-1: TrunkPack Downloadable Conversion Utility Opening Screen....................................................219
Figure F-2: Call Progress Tones Conversion Screen.....................................................................................220
Figure F-3: Encode/Decode ini File(s) Screen ...............................................................................................221
Figure F-4: Prerecorded Tones Screen..........................................................................................................222
Figure F-5: File Data Window.........................................................................................................................223
Figure F-6: Initial Settings Screen ..................................................................................................................224
Figure F-7: Recording Screen –Automatic Mode ...........................................................................................225
Figure F-8: Recording Screen after Automatic Detection...............................................................................226
Figure F-9: Recording Screen - Manual Mode ...............................................................................................227
Figure F-10: Call Progress Tone Properties...................................................................................................228
Figure F-11: Call Progress Tone Database Matches .....................................................................................228
Figure F-12: Full PBX/Country Database Match ............................................................................................228
Version 4.4
9
March 2005
MP-1xx SIP
List of Tables
Table 2-1: Front Panel Buttons on the MP-1xx ................................................................................................21
Table 2-2: Indicator LEDs on the MP-1xx Front Panel.....................................................................................22
Table 2-3: MP-10x Rear Panel Component Descriptions ................................................................................23
Table 2-4: Indicator LEDs on the MP-10x Rear Panel .....................................................................................23
Table 2-5: MP-124 Rear Panel Component Descriptions ................................................................................24
Table 2-6: Indicator LEDs on the MP-124 Rear Panel .....................................................................................24
Table 3-1: Cables and Cabling Procedure .......................................................................................................29
Table 3-2: DC Power Supply on the MP-124 Component Descriptions...........................................................31
Table 3-3: Pin Allocation in the 50-pin Telco Connector ..................................................................................31
Table 3-4: MP-104/FXS Lifeline Setup Component Descriptions ....................................................................33
Table 4-1: MP-1xx Default Networking Parameters .........................................................................................35
Table 5-1: Protocol Definition, General Parameters (continues on pages 45 to 47)........................................45
Table 5-2: Proxy & Registration Parameters (continues on pages 49 to 52) ...................................................49
Table 5-3: ini File Coder Parameter .................................................................................................................54
Table 5-4: DTMF & Dialing Parameters (continues on pages 55 to 57) ..........................................................55
Table 5-5: Advanced Parameters, General Parameters (continues on pages 59 to 62) .................................59
Table 5-6: Supplementary Services Parameters (continues on pages 64 to 65).............................................64
Table 5-7: Keypad Features Parameters .........................................................................................................67
Table 5-8: Number Manipulation Parameters ..................................................................................................69
Table 5-9: Number Manipulation ini File Parameters (continues on pages 70 to 71) ......................................70
Table 5-10: Routing Tables, General Parameters (continues on pages 73 to 74)...........................................73
Table 5-11: Tel to IP Routing Table..................................................................................................................76
Table 5-12: IP to Hunt Group Routing Table....................................................................................................79
Table 5-13: Internal DNS ini File Parameter ....................................................................................................80
Table 5-14: Reasons for Alternative Routing ini File Parameter ......................................................................82
Table 5-15: ini File Coder Group Parameters ..................................................................................................84
Table 5-16: ini File Tel Profile Settings.............................................................................................................86
Table 5-17: ini File IP Profile Settings ..............................................................................................................88
Table 5-18: Endpoint Phone Numbers Table ...................................................................................................89
Table 5-19: Channel Select Modes ..................................................................................................................92
Table 5-20: Authentication ini File Parameter ..................................................................................................93
Table 5-21: Automatic Dialing ini File Parameter .............................................................................................95
Table 5-22: Caller ID ini File Parameter ...........................................................................................................96
Table 5-23: Call Forward Table ........................................................................................................................97
Table 5-24: Authentication ini File Parameter ..................................................................................................98
Table 5-25: FXO Parameters (continues on pages 99 to 100) ........................................................................99
Table 5-26: Protocol Management, ini File Parameters (continues on pages 101 to 102) ............................101
Table 5-27: Network Setting Parameters (continues on pages 104 to 106) ..................................................104
Table 5-28: SNMP Managers Table Parameters ...........................................................................................107
Table 5-29: Board, ini File Parameters (continues on pages 108 to 110)......................................................108
Table 5-30: SNMP ini File Parameters ...........................................................................................................111
Table 5-31: Channel Settings, Voice Settings Parameters ............................................................................114
Table 5-32: Channel Settings, Fax/Modem/CID Parameters (continues on pages 115 to 116) ....................115
Table 5-33: Channel Settings, RTP Parameters ............................................................................................117
Table 5-34: Channel Settings, Miscellaneous Parameters ............................................................................118
Table 5-35: Channel Settings, ini File Parameters.........................................................................................119
Table 5-36: IP Connectivity Parameters.........................................................................................................125
Table 5-37: Call Counters Description (continues on pages 126 to 127).......................................................126
Table 5-38: Auxiliary Files Descriptions .........................................................................................................137
Table 5-39: Configuration Files ini File Parameters .......................................................................................138
Table 8-1: Summary of DTMF configuration Parameters (continues on pages 151 to 152)..........................151
Table 8-2: Supported CDR Fields ..................................................................................................................158
Table 10-1: Vendor Specific Information Field ...............................................................................................176
Table 10-2: Structure of the Vendor Specific Information Field .....................................................................177
Table 12-1: MP-1xx Selected Technical Specifications (continues on pages 191 to 193) ............................191
Table A-1: MP-1xx SIP Supplied Software Kit ...............................................................................................195
Table B-1: Command Line Switch Descriptions .............................................................................................206
Table C-1: Packet Types Defined in RFC 1890 .............................................................................................209
Table C-2: Defined Payload Types.................................................................................................................209
MP-1xx SIP User’s Manual
10
Document #: LTRT-65404
MP-1xx SIP User’s Manual
Contents
Table C-3: Default RTP/RTCP/T.38 Port Allocation.......................................................................................210
Table E-1: Customizable Logo ini File Parameters ........................................................................................215
Table E-2: Web Appearance Customizable ini File Parameters ....................................................................215
Table E-3: Customizable Logo ini File Parameters ........................................................................................216
Table E-4: Web Appearance Customizable ini File Parameters ....................................................................216
Table G-1: acBoardFatalError Alarm Trap .....................................................................................................229
Table G-2: acBoardEvResettingBoard Alarm Trap ........................................................................................229
Table G-3: acBoardCallResourcesAlarm Alarm Trap ....................................................................................230
Table G-4: acBoardControllerFailureAlarm Alarm Trap .................................................................................230
Table G-5: acBoardOverloadAlarm Alarm Trap .............................................................................................230
Table G-6: acActiveAlarmTableOverflow Alarm Trap ....................................................................................231
Table G-7: acBoardEthernetLinkAlarm Alarm Trap........................................................................................231
Table G-8: coldStart Trap ...............................................................................................................................232
Table G-9: authenticationFailure Trap............................................................................................................232
Table G-10: acBoardEvBoardStarted Trap ....................................................................................................232
Version 4.4
11
March 2005
MP-1xx SIP
Tip:
When viewing this manual on CD, Web site or on any other electronic copy,
all cross-references are hyperlinked. Click on the page or section numbers
(shown in blue) to reach the individual cross-referenced item directly. To
return back to the point from where you accessed the cross-reference, press
the ALT and ← keys.
Trademarks
AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant, MediaPack, MPMLQ, NetCoder, Stretto, TrunkPack, VoicePacketizer and VoIPerfect, are trademarks or
registered trademarks of AudioCodes Limited. All other products or trademarks are property of
their respective owners.
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, contact support@audiocodes.com.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used. Only industrystandard terms are used throughout this manual. Hexadecimal notation is indicated by 0x
preceding the number.
Related Documentation
Document #
Manual Name
LTRT-656xx (e.g., LTRT-65601)
MP-1xx SIP Release Notes
LTRT-614xx
MP-1xx Fast Track Installation Guide
Note 1:
Note 2:
Note 3:
Note 4:
MP-1xx refers to the MP-124 24-port, MP-108 8-port, MP-104 4-port and
MP-102 2-port media gateways having similar functionality except for the
number of channels (the MP-124 and MP-102 support only FXS).
MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
Note:
Where “network” appears in this manual, it means Local Area Network
(LAN), Wide Area Network (WAN), etc. accessed via the gateway’s Ethernet
interface.
Note:
FXO (Foreign Exchange Office) is the interface replacing the analog
telephone and connects to a Public Switched Telephone Network (PSTN)
line from the Central Office (CO) or to a Private 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
gateway interfaces between the CO/PBX line and the Internet.
FXS (Foreign Exchange Station) is the interface 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 devices. An FXS VoIP gateway interfaces
between the analog telephone devices and the Internet.
MP-1xx SIP User’s Manual
12
Document #: LTRT-65404
MP-1xx SIP User’s Manual
General
Warning: Ensure that you connect FXS ports to analog telephone or to PBX-trunk
lines only and FXO ports to CO/PBX lines only.
Warning: The MP-1xx is supplied as a sealed unit and must only be serviced by
qualified service personnel.
Warning: Disconnect the MP-1xx from the mains and from the Telephone Network
Voltage (TNV) before servicing.
Version 4.4
13
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
14
Document #: LTRT-65404
MP-1xx SIP User’s Manual
1. Overview
1
Overview
1.1
Introduction
This document provides you with the information on installation, configuration and operation of
the MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port VoIP media gateways. As
these units have similar functionality, except for the number of channels and some minor
features, they are referred to collectively as the MP-1xx. It is expected that the readers are
familiar with regular telephony and data networking concepts.
1.2
Gateway Description
The MediaPack MP-1xx Series Analog VoIP gateways are cost-effective, cutting edge technology
solutions, providing superior voice quality and optimized packet voice streaming (voice, fax and
data traffic) over the same IP network. These gateways use the award-winning, field-proven
Digital Signal Processing (DSP) voice compression technology used in other MediaPack and
TrunkPackTM series products.
The MP-1xx gateways incorporate up to 24 analog ports for connection, either directly to an
enterprise PBX (MP-10x/FXO), to phones, or to fax (MP-1xx/FXS), supporting up to 24
simultaneous VoIP calls.
Additionally, the MP-1xx units are equipped with a 10/100 Base-TX Ethernet port for connection
to the network.
The MP-1xx gateways are best suited for small to medium size enterprises, branch offices or for
residential media gateway solutions.
The MP-1xx gateways enable Users to make free local or international telephone/fax calls
between the distributed company offices, using their existing telephones/fax. These calls are
routed over the existing network ensuring that voice traffic uses minimum bandwidth.
The MP-1xx gateways are very compact devices that can be installed as a desk-top unit (refer to
Section 3.3.1) or on the wall (refer to Section 3.3.4) or in a 19-inch rack (refer to Section 3.3.3
and Section 3.3.3).
The MP-1xx gateways support SIP (Session Initiation Protocol) or H.323 protocols, enabling the
deployment of "voice over IP" solutions in environments where each enterprise or residential
location is provided with a simple media gateway.
This provides the enterprise with a telephone connection (e.g., RJ-11), and the capability to
transmit the voice and telephony signals over a packet network.
The MP-124 supports up to 24 analog telephone loop start FXS ports, shown in Figure 1-1.
Figure 1-1: MP-124 Gateway Front View
Version 4.4
15
March 2005
MP-1xx SIP
The MP-108 supports up to 8 analog telephone loop start FXS or FXO ports, shown in Figure 1-2.
Figure 1-2: MP-108 Gateway Front View
The MP-104 supports up to 4 analog telephone loop start FXS or FXO ports, shown in Figure 1-3.
Figure 1-3: MP-104 Gateway Front View
The MP-102 supports up to 2 analog telephone loop start FXS ports, shown in Figure 1-4.
Figure 1-4: MP-102 Gateway Front View
MP-1xx SIP User’s Manual
16
Document #: LTRT-65404
MP-1xx SIP User’s Manual
1. Overview
The layout diagram (Figure 1-5), illustrates a typical MP-108 and MP-104 or MP-102 VoIP
application.
Figure 1-5: Typical MP-1xx VoIP Application
1.3
SIP Overview
SIP (Session Initialization Protocol) is an application-layer control (signaling) protocol used on the
MP-1xx 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, on the MP-1xx, complies with the IETF (Internet Engineering Task
Force) RFC 3261 (refer to http://www.ietf.org).
Version 4.4
17
March 2005
MP-1xx SIP
1.4
MP-1xx Features
This section provides a high-level overview of some of the many MP-1xx supported features.
1.4.1
1.4.2
1.4.3
General Features
•
Superior, high quality Voice, Data and fax over IP networks.
•
Spans a range of 2 to 24 analog ports.
•
Supports analog telephone sets or analog PSTN/PBX trunk lines (FXS/FXO).
•
Connects to the network via a 10/100 Base-TX Ethernet interface.
•
Selectable G.711 or Low Bit Rate (LBR) coders per channel.
•
T.38 fax with superior performance (handling a round-trip delay of up to nine seconds).
•
Echo Canceler, Jitter Buffer, Voice Activity Detection (VAD) and Comfort Noise Generation (CNG)
support.
•
Web management for easy configuration and installation.
•
Simple Network Management Protocol (SNMP) and Syslog support.
•
Simple Network Time Protocol (SNTP) support, the time-of-day can be obtained from a
standard SNTP server.
Hardware Features
•
MP-124 19-inch, 1 U rugged enclosure provides up to 24 analog FXS ports, using a single
50 pin Telco connector.
•
MP-10x compact, rugged enclosure only one-half of a 19-inch rack unit, 1 U high (1.75" or
44.5 mm).
•
MP-124 devices: optional AC or DC power supply.
•
Lifeline - provides a wired phone connection to PSTN line when there is no power, or the
network fails (applies to MP-10x FXS gateways).
•
LEDs on the front and rear panels that provide information on the operating status of the
media gateway and the network interface.
•
Restart button on the Front panel that restarts the MP-1xx gateway, and is also used to
restore the MP-1xx parameters to their factory default values.
SIP Features
The MP-1xx SIP gateway complies with the IETF RFC 3261 standard.
•
Reliable User Datagram Protocol (UDP) transport, with retransmissions.
•
T.38 real time fax (using SIP).
Note: If the remote side includes the fax maximum rate parameter in the Session Description
Protocol (SDP) body of the Invite message, the gateway returns the same rate in the
response SDP.
•
Works with Proxy or without Proxy, using an internal routing table.
•
Fallback to internal routing table if Proxy is not responding.
•
Supports up to four Proxy servers. If the primary Proxy fails, the MP-1xx automatically
switches to a redundant Proxy.
•
Supports Proxy server discovery using Domain Name Server (DNS) SRV records.
MP-1xx SIP User’s Manual
18
Document #: LTRT-65404
MP-1xx SIP User’s Manual
1. Overview
•
Proxy and Registrar Authentication (handling 401 and 407 responses) using Basic or Digest
methods.
•
Single gateway Registration or multiple Registration of all gateway endpoints.
•
Configuration of authentication username and password per each gateway endpoint, or
single username and password per gateway.
•
Supported methods: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, INFO, REFER,
NOTIFY, PRACK, UPDATE and SUBSCRIBE.
•
Modifying connection parameters in a call (re-INVITE).
•
Working with Redirect server and handling 3xx responses.
•
Early media (supporting 183 Session Progress).
•
PRACK reliable provisional responses <RFC 3262>.
•
Call Hold and Transfer Supplementary services using REFER, Refer-To, Referred-By,
Replaces and NOTIFY.
•
Call Forward (using 302 response): Immediate, Busy, No reply, Busy or No reply, Do Not
Disturb.
•
Supports RFC 3327 – Adding “Path” to Supported header.
•
Supports RFC 3581 – Symmetric Response Routing.
•
Session Timer <draft-ietf-sip-session-timer-13.txt>.
•
Supports network asserted identity and privacy (RFC 3325 and RFC 3323).
•
Supports Tel URI (Uniform Resource Identifier) according to RFC 2806 bis.
•
Remote party ID <draft-ietf-sip-privacy-04.txt>.
•
Obtaining Proxy Domain Name(s) from DHCP (Dynamic Host Control Protocol) according to
RFC 3361.
•
RFC 2833 relay for Dual Tone Multi Frequency (DTMF) digits, including payload type
negotiation.
•
DTMF out-of-band transfer using:
INFO method <draft-choudhuri-sip-info-digit-00.txt>.
INFO method, compatible with Cisco gateways.
NOTIFY method <draft-mahy-sipping-signaled-digits-01.txt>.
•
Supported coders:
G.711 A-law 64 kbps
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.711 µ-law 64 kbps
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.723.1 5.3, 6.3 kbps
(30, 60, 90, 120, 150 msec)
G.726 32 kbps
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.729A 8 kbps
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.729B is supported if Silence Suppression is enabled.
•
Can negotiate coder from a list of given coders.
•
Implementation of Message Waiting Indication (MWI) IETF draft-ietf-sipping-mwi-04.txt,
including SUBSCRIBE (to the MWI server). The MP-1xx/FXS gateways can accept an MWI
Notify message that indicates waiting messages or indicates that the MWI is cleared.
For more updated information on the gateway’s supported features, refer to the latest MP-1xx SIP
Release Notes.
Version 4.4
19
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
20
Document #: LTRT-65404
MP-1xx SIP User’s Manual
2
2. MP-1xx Physical Description
MP-1xx Physical Description
This section provides detailed information on the MP-1xx hardware, the location and functionality
of the LEDs, buttons and connectors on the front and rear panels.
For detailed information on installing the MP-1xx refer to Section 3 on page 25.
2.1
MP-1xx Front Panel
Figure 2-1 and Figure 2-2 illustrate the front layout of the MP-108 (almost identical on MP-104
and MP-102) and MP-124 respectively. Refer to Section 2.1.1 for meaning of the front panel
buttons; refer to Section 2.1.2 for functionality of the front panel LEDs.
Figure 2-1: MP-108 Front Panel
Reset Button
Figure 2-2: MP-124 Front Panel
Reset Button
2.1.1
MP-1xx Front Panel Buttons
Table 2-1 lists and describes the front panel buttons on the MP-1xx.
Table 2-1: Front Panel Buttons on the MP-1xx
Type
Function
Reset the MP-1xx
Reset button
Version 4.4
Comment
Press the reset button with a paper clip or any other similar
pointed object, until the gateway is reset.
Restore the MP-1xx parameters to
Refer to Section 4.2 on page 36.
their factory default values
21
March 2005
MP-1xx SIP
2.1.2
MP-1xx Front Panel LEDs
Table 2-2 lists and describes the front panel LEDs on the MP-1xx.
MP-1xx (FXS/FXO) media gateways feature almost identical front panel
LEDs; they only differ in the number of channel LEDs that correspond to the
number of channels.
Note:
Table 2-2: Indicator LEDs on the MP-1xx Front Panel
Label
Type
Color
State
Green
ON
Device Powered, self-test OK
Device Status
Orange
Blinking
Software Loading/Initialization
Red
ON
Malfunction
LAN
Ethernet Link
Status
Green
ON
Valid 10/100 Base-TX Ethernet connection
Red
ON
Malfunction
Control
Control Link
Green
Blinking
Ready
Packet Status
Data
Channels
Telephone
Interface
Function
Sending and receiving SIP messages
No traffic
Blank
Green
Blinking
Red
Blinking
Blank
-
Green
ON
Green
Blinking
Red
ON
Blank
-
Transmitting RTP (Real-Time Transport Protocol)
Packets
Receiving RTP Packets
No traffic
Offhook / Ringing for FXS Phone Port
FXO Line-Seize/Ringing State for Line Port
2.2
MP-1xx Rear Panel
2.2.1
MP-10x Rear Panel
There’s an incoming call, before answering
Line Malfunction
Normal
Figure 2-3 illustrates the rear panel layout of the MP-104. For descriptions of the MP-10x rear
panel components, refer to Table 2-3. For the functionality of the MP-10x rear panel LEDs, refer
to Table 2-4.
Tip 1:
MP-10x (FXS/FXO) media gateways feature almost identical rear panel
connectors and LEDs, located slightly differently from one device to the next.
Tip 2:
The RJ-45 port (Eth 1) on the MP-10x/FXO rear panel is inverted on the MP1xx/FXS. The label on the rear panel also distinguishes FXS from FXO
devices.
MP-1xx SIP User’s Manual
22
Document #: LTRT-65404
MP-1xx SIP User’s Manual
2. MP-1xx Physical Description
Figure 2-3: MP-104/FXS Rear Panel Connectors
1
2
4
3
6
5
Table 2-3: MP-10x Rear Panel Component Descriptions
Item #
Label
Component Description
1
100-250V ~ 1A
50-60 Hz
AC power supply socket.
2
Protective earthing screw (mandatory for all installations).
3
Eth 1
10/100 Base-TX Ethernet connection.
4
2, 4 or 8 FXS/FXO ports.
5
FXS
6
RS-232
FXS / FXO label.
9 pin RS-232 status port (for Cable Wiring of the RS-232 refer to Figure
3-10 on page 32).
Table 2-4: Indicator LEDs on the MP-10x Rear Panel
Label
Type
ETH-1
Ethernet Status
Color
State
Meaning
Yellow
ON
Ethernet port receiving data
Red
ON
Collision
Note that the Ethernet LEDs are located within the RJ-45 socket.
2.2.2
MP-124 Rear Panel
Figure 2-4 illustrates the rear panel layout of the MP-124. For descriptions of the MP-124 rear
panel components, refer to Table 2-5. For the functionality of the MP-124 rear panel LEDs, refer
to Table 2-6.
Figure 2-4: MP-124 (FXS) Rear Panel Connectors
1
Version 4.4
2
3
4
23
5
6
March 2005
MP-1xx SIP
Table 2-5: MP-124 Rear Panel Component Descriptions
Item #
Label
Component Description
1
Protective earthing screw (mandatory for all installations).
2
100-250 V~
50 - 60 Hz 2A
3
ANALOG LINES 1 –24
4
Data Cntrl Ready
5
RS-232
6
Eth 1 Eth 2
AC power supply socket.
50-pin Telco for 1 to 24 analog lines.
LED indicators (described in Table 2-6).
9 pin RS-232 status port (for Cable Wiring of the RS-232 refer to Figure
3-10 on page 32).
Dual 10/100 Base-TX Ethernet connections.
48 V
2A max
Connection to external DC 40-60 V power supply (refer to Figure 3-9).
The Dual In-line Package (DIP) switch, located on the MP-124 rear panel
(supplied with some of the units), is not functional and should not be used.
Note:
The Ethernet LEDs are located within each of the RJ-45 sockets.
Note that on the MP-124 the rear panel also duplicates the Data, Control and Ready LEDs from
the front panel.
Table 2-6: Indicator LEDs on the MP-124 Rear Panel
Label
Type
Color
State
Data
Packet Status
Green
ON
Transmitting RTP Packets
Red
ON
Receiving RTP Packets
No traffic
Blank
Cntrl
Control Link
Green
Blinking
Eth 1
Eth 2
Device Status
Ethernet Status
Ethernet Status
MP-1xx SIP User’s Manual
Sending and receiving H.323 messages
No traffic
Blank
Ready
Function
Green
ON
Device Powered and Self-test OK
Orange
ON
Software Loading/Initialization
Red
ON
Malfunction
Green
ON
Valid 10/100 Base-TX Ethernet connection
Red
ON
Malfunction
Green
ON
Valid 10/100 Base-TX Ethernet connection
Red
ON
Malfunction
24
Document #: LTRT-65404
MP-1xx SIP User’s Manual
3
3. Installing the MP-1xx
Installing the MP-1xx
This section provides information on the hardware installation procedure for the MP-1xx. For
information on how to start using the gateway, refer to Section 4 on page 35. For detailed
information on the MP-1xx connectors, LEDs and buttons, refer to Section 2 on page 21.
Caution Electrical Shock
The equipment must only be installed or serviced by qualified service personnel.
To install the MP-1xx, take these 4 steps:
1.
Unpack the MP-1xx (refer to Section 3.1 below).
2.
Check the package contents (refer to Section 3.2 below).
3.
Mount the MP-1xx (refer to Section 3.3 on page 26).
4.
Cable the MP-1xx (refer to Section 3.4 on page 29).
After connecting the MP-1xx to the power source, the Ready and LAN LEDs on the front panel
turn to green (after a self-testing period of about 1 minute). Any malfunction changes the Ready
LED to red.
When you have completed the above relevant sections you are then ready to start configuring the
gateway (Section 4 on page 35).
3.1
Unpacking
To unpack the MP-1xx, take these 6 steps:
3.2
1.
Open the carton and remove packing materials.
2.
Remove the MP-1xx gateway from the carton.
3.
Check that there is no equipment damage.
4.
Check, retain and process any documents.
5.
Notify AudioCodes or your local supplier of any damage or discrepancies.
6.
Retain any diskettes or CDs.
Package Contents
Ensure that in addition to the MP-1xx, the package contains:
•
AC power cable for the AC power supply option.
•
DC terminal block (MP-124 only, for the DC power supply option).
•
CD (software and documentation).
•
Lifeline cable (RJ-11 adaptor cable for 1 to 2). (Supplied with MP-10x/FXS only).
•
3 brackets (2 short, 1 long) and bracket-to-device screws for 19-inch rack installation option
(MP-10x only).
•
2 short equal-length brackets and bracket-to-device screws for MP-124 19-inch rack
installation.
•
The MP-1xx Fast Track Installation Guide.
Version 4.4
25
March 2005
MP-1xx SIP
3.3
Mounting the MP-1xx
The MP-1xx can be mounted on a desktop or on a wall (only MP-10x), or installed in a standard
19-inch rack. Refer to Section 3.4 on page 29 for cabling the MP-1xx.
3.3.1
Mounting the MP-1xx on a Desktop
No brackets are required. Simply place the MP-1xx on the desktop in the position you require.
Figure 3-1: Desktop or Shelf Mounting
Rack Mount Safety Instructions (UL)
When installing the chassis in a rack, be sure to implement the following Safety
instructions recommended by Underwriters Laboratories:
•
•
•
•
•
3.3.2
Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly,
the operating ambient temperature of the rack environment may be greater than
room ambient. Therefore, consideration should be given to installing the equipment
in an environment compatible with the maximum ambient temperature (Tma)
specified by the manufacturer.
Reduced Air Flow - Installation of the equipment in a rack should be such that the
amount of air flow required for safe operation on the equipment is not
compromised.
Mechanical Loading - Mounting of the equipment in the rack should be such that
a hazardous condition is not achieved due to uneven mechanical loading.
Circuit Overloading - Consideration should be given to the connection of the
equipment to the supply circuit and the effect that overloading of the circuits might
have on overcurrent protection and supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when addressing this concern.
Reliable Earthing - Reliable earthing of rack-mounted equipment should be
maintained. Particular attention should be given to supply connections other than
direct connections to the branch circuit (e.g., use of power strips.)
Installing the MP-10x in a 19-inch Rack
The MP-10x is installed into a standard 19-inch rack by the addition of two supplied brackets (1
short, 1 long). The MP-108 with brackets for rack installation is shown in Figure 3-2.
To install the MP-10x in a 19-inch rack, take these 9 steps:
1.
Remove the two screws on one side of the device nearest the front panel.
2.
Insert the peg on the short bracket into the third air vent down on the column of air vents
nearest the front panel.
MP-1xx SIP User’s Manual
26
Document #: LTRT-65404
MP-1xx SIP User’s Manual
3. Installing the MP-1xx
3.
Swivel the bracket until the holes in the bracket line up with the two empty screw holes on
the device.
4.
Use the screws found in the devices’ package to attach the short bracket to the side of the
device.
5.
Remove the two screws on the other side of the device nearest the front panel.
6.
Position the long bracket so that the holes in the bracket line up with the two empty screw
holes on the device.
7.
Use the screws found in the device’s package to attach the long bracket to the side of the
device.
8.
Position the device in the rack and line up the bracket holes with the rack frame holes.
9.
Use four standard rack screws to attach the device to the rack. These screws are not
provided with the device.
Figure 3-2: MP-108 with Brackets for Rack Installation
3.3.3
Installing the MP-124 in a 19-inch Rack
The MP-124 is installed into a standard 19-inch rack by the addition of two short (equal-length)
supplied brackets. The MP-124 with brackets for rack installation is shown in Figure 3-3.
To install the MP-124 in a 19-inch rack, take these 7 steps:
1.
Remove the two screws on one side of the device nearest the front panel.
2.
Insert the peg on one of the brackets into the third air vent down on the column of air vents
nearest the front panel.
3.
Swivel the bracket until the holes in the bracket line up with the two empty screw holes on
the device.
4.
Use the screws found in the devices’ package to attach the bracket to the side of the device.
5.
Repeat steps 1 to 4 to attach the second bracket to the other side of the device.
6.
Position the device in the rack and line up the bracket holes with the rack frame holes.
7.
Use four standard rack screws to attach the device to the rack. These screws are not
provided with the device.
Version 4.4
27
March 2005
MP-1xx SIP
Figure 3-3: MP-124 with Brackets for Rack Installation
3.3.4
Mounting the MP-10x on a Wall
The MP-10x is mounted on a wall by the addition of two short (equal-length) supplied brackets.
The MP-102 with brackets for wall mount is shown in Figure 3-4.
To mount the MP-10x on a wall, take these 7 steps:
1.
Remove the screw on the side of the device that is nearest the bottom and the front panel.
2.
Insert the peg on the bracket into the third air vent down on the column of air vents nearest
the front panel.
3.
Swivel the bracket so that the side of the bracket is aligned with the base of the device and
the hole in the bracket line up with the empty screw hole.
4.
Attach the bracket using one of the screws provided in the device package.
5.
Repeat steps 1 to 4 to attach the second bracket to the other side of the device.
6.
Position the device on the wall with the base of the device next to the wall.
7.
Use four screws to attach the device to the wall. These screws are not provided with the
device.
Figure 3-4: MP-102 Wall Mount
MP-1xx SIP User’s Manual
28
Document #: LTRT-65404
MP-1xx SIP User’s Manual
3.4
3. Installing the MP-1xx
Cabling the MP-1xx
Verify that you have the cables listed under column ‘Cable’ in Table 3-1 before beginning to cable
the MP-1xx according to the column ‘Cabling Procedure’. For detailed information on the MP-1xx
rear panel connectors, refer to Section 2.2 on page 22.
Table 3-1: Cables and Cabling Procedure
Cable
Cabling Procedure
RJ-45
Ethernet
cable
When initializing (connecting the MP-1xx to the network for the first time) use a standard
Ethernet cable to connect the network interface on your computer to a port on a network
hub / switch. Use a second standard Ethernet cable to connect the MP-1xx to another
port on the same network hub / switch.
For normal use, connect the MP-1xx Ethernet connection directly to the network, using a
standard RJ-45 Ethernet cable. For connector’s pinout refer to Figure 3-5 on page 30.
RJ-11 twowire
telephone
cords
Connect the RJ-11 connectors on the rear panel of the MP10x/FXS to fax machine, modem, or phones (refer to Figure 3-6).
Ensure that FXS &
FXO are connected
to the correct
Connect RJ-11 connectors on the MP-10x/FXO rear panel to
devices, otherwise
telephone exchange analog lines or PBX extensions (Figure 3-6). damage can occur.
MP-124/FXS ports are usually distributed using an MDF Adaptor Block (special order
option). Refer to Figure 3-8 for details.
Lifeline cable
For detailed information on setting up the Lifeline, refer to the procedure under Section
3.4.2 on page 32.
Wire the 50-pin Telco connectors according to the pinout in Figure 3-7 on page 30,
and Figure 3-8 on page 30.
Attach each pair of wires from a 25-pair Octopus cable to its corresponding socket
on the MDF Adaptor Block’s rear.
Connect the wire-pairs at the other end of the cable to a male 50-pin Telco
connector.
Insert and fasten this connector to the female 50-pin Telco connector on the MP124 rear panel (labeled Analog Lines 1-24).
Connect the telephone lines from the Adaptor Block to a fax machine, modem, or
telephones by inserting each RJ-11 connector on the 2-wire line cords of the POTS
phones into the RJ-11 sockets on the front of an MDF Adaptor Block as shown in
Figure 3-8 on page 30.
50-pin Telco
cable (MP-124
devices only).
1.
An Octopus
cable is not
included with
the MP-124
package.
3.
RS-232 serial
cable
For detailed information on connecting the MP-1xx RS-232 port to your PC, refer to
Section 3.4.1 on page 32.
Protective
earthing strap
Connect an earthed strap to the chassis protective earthing screw and fasten it securely
according to the safety standards.
AC Power
cable
Connect the MP-1xx 100-250V~ 50-60 Hz power socket to the mains.
2.
4.
5.
DC Power cable Refer to Figure 3-9. Insert two 18 AWG wires into the supplied DC terminal block and
(MP-124
fasten the two screws located directly above each wire. Insert the DC terminal block into
devices only)
the DC inlet on the MP-124 rear panel and fasten it with the two adaptor-to-panel
screws. Connect the other end of the cable to a 48 VDC power supply.
Safety Notice
When installing the DC power supply on the MP-124, be sure to implement the following safety
instructions:
• Connect the unit to an SELV source sufficiently isolated from the mains.
• Connect the unit permanently to earth via its protective earthing stud.
Version 4.4
29
March 2005
MP-1xx SIP
Figure 3-5: RJ-45 Ethernet Connector Pinout
RJ-45 Connector and Pinout
12345678
1 - Tx+
2 - Tx3 - Rx+
6 - Rx-
4, 5, 7, 8
not
connected
Figure 3-6: RJ-11 Phone Connector Pinout
RJ-11 Connector and Pinout
1234
1234-
Not connected
Tip
Ring
Not connected
Figure 3-7: 50-pin Telco Connector (MP-124/FXS only)
Pin Numbers
25
1
26
50
Figure 3-8: MP-124 in a 19-inch Rack with MDF Adaptor
19-inch Rack
Rear View
FRONT INPUT
24 line cords
2-wire with RJ-11
connectors
M D F Adaptor Block - rear
REAR OUTPUT
24 wire pairs in
Octopus cable
with 50-pin male
Telco connector
Primary
LAN Cable
to Eth 1
AC Power Cord
Back-up
LAN Cable
to Eth 2
Connect to
here
ANALOG LINES 1-20
Cntrl
Grounding Strap
MP-1xx SIP User’s Manual
50-pin female
Telco connector
30
Ready
ON
RS-232
Data
100 - 250V~
50 - 60Hz 2A
12345
CONFIG
Eth 1
Eth 2
MP-124
Rear View
RS-232 Cable
Document #: LTRT-65404
MP-1xx SIP User’s Manual
3. Installing the MP-1xx
Figure 3-9: DC Power Supply on the MP-124
1
2
3
Table 3-2: DC Power Supply on the MP-124 Component Descriptions
Component Description
Item #
1
2 screws for wire connection to the DC terminal block.
2
2 screws for connecting the DC terminal block to the MP-124 panel.
3
Two 18 AWG wires.
Table 3-3: Pin Allocation in the 50-pin Telco Connector
Phone Channel
Connector Pins
Phone Channel
Connector Pins
1
2
3
4
5
6
7
8
9
10
11
12
1/26
2/27
3/28
4/29
5/30
6/31
7/32
8/33
9/34
10/35
11/36
12/37
13
14
15
16
17
18
19
20
21
22
23
24
13/38
14/39
15/40
16/41
17/42
18/43
19/44
20/45
21/46
22/47
23/48
24/49
Version 4.4
31
March 2005
MP-1xx SIP
3.4.1
Connecting the MP-1xx RS-232 Port to Your PC
Using a standard RS-232 straight cable (not a cross-over cable) with DB-9 connectors, connect
the MP-1xx RS-232 port to either COM1 or COM2 RS-232 communication port on your PC. The
required connector pinout and gender are shown below in Figure 3-10.
The RS-232 port is mainly used internally by service personnel for monitoring purposes.
Advanced users can also use this feature to obtain log information (for example).
Figure 3-10: RS-232 Cable Wiring
2
3
5
RD
TD
GND
DB-9
forfor
MP-1xx
DB-9male
male
MP-100
DB-9female
femalefor
for PC
PC
DB-9
3.4.1.1
2
3
5
Configuring the Serial Connection
To communicate with the MP-1xx, set your serial communication software to the following
communications port settings:
3.4.2
•
Baud Rate: 115,200 bps
•
Data bits:
8
•
Parity:
None
•
Stop bits:
1
•
Flow control:Hardware
Cabling the Lifeline Phone
The Lifeline provides a wired analog POTS phone connection to any PSTN or PBX FXS port
when there is no power, or when the network connection fails. Users can therefore use the
Lifeline phone even when the MP-1xx is not powered on or not connected to the network. With
the MP-108/FXS and MP-104/FXS the Lifeline connection is provided on port #4 (refer to Figure
3-12). With the MP-102/FXS the Lifeline connection is provided on port #2.
Note:
The MP-124 and MP-10x/FXO do NOT support the Lifeline.
The Lifeline’s Splitter connects pins #1 and #4 to another source of an FXS port, and pins #2 and
#3 to the POTS phone. Refer to the Lifeline Splitter pinout in Figure 3-11.
Figure 3-11: Lifeline Splitter Pinout & RJ-11 Connector for MP-10x/FXS
1234
MP-1xx SIP User’s Manual
123432
Life Line Tip
Tip
Ring
Life Line Ring
Document #: LTRT-65404
MP-1xx SIP User’s Manual
3. Installing the MP-1xx
To cable the MP-10x/FXS Lifeline phone, take these 3 steps:
1.
Connect the Lifeline Splitter to port #4 (on the MP-104/FXS or MP-108/FXS) or to port #2 (on
the MP-102/FXS).
2.
Connect the Lifeline phone to Port A on the Lifeline Splitter.
3.
Connect an analog PSTN line to Port B on the Lifeline Splitter.
Note:
The use of the Lifeline on network failure can be disabled using the
‘LifeLineType’ ini file parameter (described in Table 5-29 on page 108).
Figure 3-12: MP-104/FXS Lifeline Setup
1
2
3
4
6
7
5
Table 3-4: MP-104/FXS Lifeline Setup Component Descriptions
Item #
Version 4.4
Component Description
1
B: To PSTN wall port.
2
Phone to Port 1.
3
Lifeline to Port 4.
4
PSTN to Splitter (B).
5
Phone to Port 1.
6
Lifeline phone to Splitter (A).
7
Lifeline phone.
33
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
34
Document #: LTRT-65404
MP-1xx SIP User’s Manual
4
4. Getting Started
Getting Started
The MP-1xx is supplied with application software already resident in its flash memory (with
factory default parameters).
Section 4.1 below describes how to assign an IP address to the MP-1xx, while Section 4.2 on
page 36 describes how to set up the MP-1xx with basic parameters using a standard Web
browser (such as Microsoft TM Internet Explorer).
For detailed information on how to fully configure the gateway refer to the Web Interface,
described in Section 5 on page 39.
4.1
Assigning the MP-1xx IP Address
To assign an IP address to the MP-1xx use one of the following methods:
•
HTTP using a Web browser (refer to Section 4.1.1 below).
•
BootP (refer to Section 4.1.2 on page 36).
•
DHCP (refer to Section 10.2 on page 175).
•
Serial communication software (e.g., HyperTerminalTM) connected to the MP-1xx via the RS232 port (refer to Section 9.2.2 on page 170).
The default networking parameters are show in Table 4-1.
You can use the ‘Reset’ button to restore the MP-1xx networking parameters to their factory
default values (refer to Section 4.2 on page 36).
Table 4-1: MP-1xx Default Networking Parameters
FXS or FXO
Default Value
FXS
10.1.10.10
FXO
10.1.10.11
MP-1xx default subnet mask is 255.255.0.0, default gateway IP address is 0.0.0.0
4.1.1
Assigning an IP Address Using HTTP
To assign an IP address using HTTP, take these 8 steps:
1.
Connect your computer to the MP-1xx. Either connect the network interface on your
computer to a port on a network hub / switch (refer to Table 3-1 on page 29 - RJ-45 Ethernet
cable), or use an Ethernet cross-over cable to directly connect the network interface on your
computer to the RJ-45 jack on the MP-1xx.
2.
Change your PC’s IP address and subnet mask to correspond with the MP-1xx factory
default IP address and subnet mask, shown in Table 4-1. For details on changing the IP
address and subnet mask of your PC, refer to Windows™ Online Help (Start>Help).
3.
Access the MP-1xx Embedded Web Server (refer to Section 5.5 on page 40).
4.
In the ‘Quick Setup’ screen (shown in Figure 4-1), set the MP-1xx ‘IP Address’, ‘Subnet
Mask’ and ‘Default Gateway IP Address’ fields under ‘IP Configuration’ to correspond with
your network IP settings. If your network doesn’t feature a default gateway, enter a dummy
value in the ‘Default Gateway IP Address’ field.
Version 4.4
35
March 2005
MP-1xx SIP
5.
Click the Reset button and click OK in the prompt; the MP-1xx applies the changes and
restarts. This takes approximately 1 minute to complete. When the MP-1xx has finished
restarting, the Ready and LAN LEDs on the front panel are lit green.
Tip:
4.1.2
Record and retain the IP address and subnet mask you assign the MP-1xx.
Do the same when defining new username or password. If the Embedded
Web Server is unavailable (for example, if you’ve lost your username and
password), use the BootP/TFTP (Trivial File Transfer Protocol) configuration
utility to access the device, “reflash” the load and reset the password (refer
to Appendix B on page 197 for detailed information on using a BootP/TFTP
configuration utility to access the device).
6.
Disconnect your computer from the MP-1xx or from the hub / switch (depending on the
connection method you used in step 1).
7.
Reconnect the MP-1xx and your PC (if necessary) to the LAN.
8.
Restore your PC’s IP address & subnet mask to what they originally were. If necessary,
restart your PC and re-access the MP-1xx via the Embedded Web Server with its new
assigned IP address.
Assigning an IP Address Using BootP
Note:
BootP procedure can also be performed using any standard compatible
BootP server.
Tip:
You can also use BootP to load the auxiliary files to the MP-1xx (refer to
Section 5.11.2.1 on page 138).
To assign an IP address using BootP, take these 3 steps:
4.2
1.
Open the BootP application (supplied with the MP-1xx software package).
2.
Add client configuration for the MP-1xx, refer to Section B.11.1 on page 203.
3.
Reset the gateway physically causing it to use BootP; the MP-1xx changes its network
parameters to the values provided by the BootP.
Restoring Networking Parameters to their Initial
State
You can use the ‘Reset’ button to restore the MP-1xx networking parameters to their factory
default values (described in Table 4-1) and to reset the username and password.
Note that the MP-1xx returns to the software version burned in flash. This process also restores
the MP-1xx parameters to their factory settings, therefore you must load your previously backedup ini file, or the default ini file (received with the software kit) to set them to their correct values.
To restore networking parameters to their initial state, take these 6
steps:
1.
Disconnect the MP-1xx from the power and network cables.
MP-1xx SIP User’s Manual
36
Document #: LTRT-65404
MP-1xx SIP User’s Manual
4.3
4. Getting Started
2.
Reconnect the power cable; the gateway is powered up. After approximately 45 seconds the
Ready LED turns to green and the Control LED blinks for about 3 seconds.
3.
While the Control LED is blinking, press shortly on the reset button (located on the left side
of the front panel); the gateway resets a second time and is restored with factory default
parameters (username: “Admin”, password: “Admin”).
4.
Reconnect the network cable.
5.
Assigning the MP-1xx IP address (refer to Section 4.1 on page 35).
6.
Load your previously backed-up ini file, or the default ini file (received with the software kit).
To load the ini file via the Embedded Web Server, refer to Section 5.9.2.1 on page 120.
Configure the MP-1xx Basic Parameters
To configure the MP-1xx basic parameters use the Embedded Web Server’s ‘Quick Setup’
screen (shown in Figure 4-1 below). Refer to Section 5.5 on page 40 for information on accessing
the ‘Quick Setup’ screen.
Figure 4-1: Quick Setup Screen
To configure basic SIP parameters, take these 9 steps:
1.
If the MP-1xx is behind a router with Network Address Translation (NAT) enabled, perform
the following procedure. If it isn’t, leave the ‘NAT IP Address’ field undefined.
Determine the “public” IP address assigned to the router (by using, for instance, router
Web management). Enter this public IP address in the ‘NAT IP Address’ field.
Enable the DMZ (Demilitarized Zone) configuration on the residential router for the LAN
port where the MP-1xx gateway is connected. This enables unknown packets to be
routed to the DMZ port.
Version 4.4
37
March 2005
MP-1xx SIP
2.
Under ‘SIP Parameters’, enter the MP-1xx Domain Name in the field ‘Gateway Name’. If the
field is not specified, the MP-1xx IP address is used instead (default).
3.
When working with a Proxy server, set ‘Working with Proxy’ field to ‘Yes’ and enter the IP
address of the primary Proxy server in the field ‘Proxy IP Address’. When no Proxy is used,
the internal routing table is used to route the calls.
4.
Enter the Proxy Name in the field ‘Proxy Name’. If Proxy name is used, it replaces the Proxy
IP address in all SIP messages. This means that messages are still sent to the physical
Proxy IP address but the SIP URI contains the Proxy name instead.
5.
Configure ‘Enable Registration’ to ‘Yes’ or ‘No’:
‘No’ = the MP-1xx does not register to a Proxy server/Registrar (default).
‘Yes’ = the MP-1xx registers to a Proxy server/Registrar at power up and every ‘Registration
Time’ seconds; The MP-1xx sends a register request according to the ‘Authentication Mode’
parameter. For detailed information on the parameters ‘Registration Time’ and
‘Authentication Mode’, refer to Table 5-2 on page 49.
6.
Select the coder (i.e., vocoder) that best suits your VoIP system requirements. The default
coder is: G.7231 30 msec. To program the entire list of coders you want the MP-1xx to use,
click the button on the left side of the ‘1st Coder’ field; the drop-down list for the 2nd to 5th
coders appears. Select coders according to your system requirements. Note that coders
higher on the list are preferred and take precedence over coders lower on the list.
Note:
The preferred coder is the coder that the MP-1xx uses as a first choice for all
connections. If the far end gateway does not use this coder, the MP-1xx
negotiates with the far end gateway to select a coder that both sides can
use.
7.
To program the Tel to IP Routing Table, press the arrow button next to ‘Tel to IP Routing
Table’. For information on how to configure the Tel to IP Routing Table, refer to Section
5.8.4.2 on page 75.
8.
To program the Endpoint Phone Number Table, press the arrow button next to ‘Endpoint
Phone Number’. For information on how to configure the Endpoint Phone Number Table,
refer to Section 5.8.6 on page 89.
9.
Click the Reset button and click OK in the prompt; The MP-1xx applies the changes and
restarts. This takes approximately 1 minute to complete. When the MP-1xx has finished
restarting, the Ready and LAN LEDs on the front panel are lit green.
You are now ready to start using the VoIP gateway. To prevent unauthorized access to the MP1xx, it is recommended that you change the username and password that are used to access the
Web Interface. Refer to Section 5.9.5 on page 123 for details on how to change the username
and password.
Tip:
MP-1xx SIP User’s Manual
Once the gateway is configured correctly back up your settings by making a
copy of the VoIP gateway configuration (ini file) and store it in a directory on
your computer. This saved file can be used to restore configuration settings
at a future time. For information on backing up and restoring the gateway’s
configuration refer to Section 5.9.2.1 on page 120.
38
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
5
Configuring the MP-1xx
5.1
Configuration Concepts
Users can utilize the the MP-1xx in a wide variety of applications, enabled by its parameters and
configuration files (e.g., Call Progress Tones (CPT), etc.). The parameters can be configured and
configuration files can be loaded using:
•
A standard Web Browser (described and explained in this section).
•
A configuration file referred to as the ini file. For information on how to use the ini file refer to
Section 6 on page 141.
•
An SNMP browser software (refer to Section 11 on page 179).
•
AudioCodes’ Element Management System (EMS) (refer to Section 11.8 on page 190 and to
AudioCodes’ EMS User’s Manual or EMS Product Description).
To upgrade the MP-1xx (load new software or configuration files onto the gateway) use the
Software Upgrade wizard, available through the Web Interface (refer to Section 5.11.1 on page
131), or alternatively use the BootP/TFTP configuration utility (refer to Section 10.3.1 on page
176).
For information on the configuration files refer to Section 6 on page 141.
5.2
Overview of the Embedded Web Server
The Embedded Web Server is used both for gateway configuration, including loading of
configuration files, and for run-time monitoring. The Embedded Web Server can be accessed
from a standard Web browser, such as Microsoft™ Internet Explorer, Netscape™ Navigator, etc.
Specifically, Users can employ this facility to set up the gateway configuration parameters. Users
also have the option to remotely reset the gateway and to permanently apply the new set of
parameters.
5.3
Computer Requirements
To use the Web Interface, the following is needed:
•
A computer capable of running your Web browser.
•
A network connection to the VoIP gateway.
•
One of the following compatible Web browsers:
Microsoft™ Internet Explorer™ (version 6.0 and higher).
Netscape™ Navigator™ (version 7.0 and higher).
Note:
Version 4.4
Some Java-script applications are not supported in Netscape.
39
March 2005
MP-1xx SIP
5.4
Password Control
The Embedded Web Server is protected by a unique username and password combination. The
first time a browser request is made, the User is requested to provide his username and
password to obtain access. Subsequent requests are negotiated by the browser on behalf of the
User, so that the User doesn’t have to re-enter the username and password for each request, but
the request is still authenticated (the Embedded Web Server uses the MD5 authentication
method supported by the HTTP 1.1 protocol).
An additional level of protection is obtained by a restriction that no more than three IP addresses
can access the Embedded Web Server concurrently. With this approach, a fourth User is told that
the server is busy, even if the correct username and password were provided.
5.4.1
Embedded Web Server Username & Password
The default username and password for all gateways are:
•
Username = “Admin” (case-sensitive)
•
Password = “Admin” (case-sensitive)
For details on changing the username and password, refer to Section 5.9.5 on page 123. Note
that the password and username can be a maximum of 7 case-sensitive characters.
The User can reset the Web username and password (to the default values) by enabling an ini
file parameter called ‘ResetWebPassword’. The Web password is automatically the default
password.
5.5
Configuring the Web Interface via the ini File
Two additional security preferences can be configured using ini file parameters. These security
levels provide protection against unauthorized access (such as Internet hacker attacks),
particularly to Users without a firewall. For information on the ini file refer to Section 6 on page
141.
5.5.1
Limiting the Embedded Web Server to Read-Only Mode
Users can limit the Web Interface to read-only mode by changing the ini file parameter
‘DisableWebConfig’ to 1. In this mode all Web screens are read-only and cannot be modified. In
addition, the following screens cannot be accessed: ‘Quick Setup’, ‘Change Password’, ’Reset‘,
‘Save Configuration‘, ‘Software Upgrade Wizard’, ‘Load Auxiliary Files’, ‘Configuration File’ and
‘Regional Settings’.
5.5.2
Disabling the Embedded Web Server
To deny access to the gateway through HTTP protocol, the User can disable the Embedded Web
Server task. To disable the Web task, use the ini file parameter ‘DisableWebTask = 1’. The
default is to Web task enabled.
MP-1xx SIP User’s Manual
40
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.6
5. Configuring the MP-1xx
Accessing the Embedded Web Server
To access the Embedded Web Server, take these 4 steps:
1.
Open a standard Web-browsing application such as Microsoft™ Internet Explorer™ (Version
6.0 and higher) or Netscape™ Navigator™ (Version 7.0 and higher).
2.
In the Uniform Resource Locator (URL) field, specify the IP address of the MP-1xx (e.g.,
http://10.1.10.10); the Embedded Web Server’s ‘Enter Network Password’ screen appears,
shown in Figure 5-1.
Figure 5-1: Embedded Web Server Login Screen
5.6.1
3.
In the ‘User Name’ and ‘Password’ fields, enter the username (default: “Admin”) and
password (default: “Admin”). Note that the username and password are case-sensitive.
4.
Click the OK button; the ‘Quick Setup’ screen is accessed (shown in Figure 4-1).
Using Internet Explorer to Access the Embedded Web Server
Internet explorer’s security settings may block access to the gateway’s Web browser if they’re
configured incorrectly. In this case, the following message is displayed:
Unauthorized
Correct authorization is required for this area. Either your browser does not perform
authorization or your authorization has failed. RomPager server.
To troubleshoot blocked access to Internet Explorer™, take these 2
steps
1.
Delete all cookies from the Temporary Internet files. If this does not clear up the problem, the
security settings may need to be altered (refer to Step 2).
2.
In Internet Explorer, Tools, Internet Options select the Security tab, and then select Custom
Level. Scroll down until the Logon options are displayed and change the setting to Prompt
for username and password and then restart the browser. This fixes any issues related to
domain use logon policy.
Version 4.4
41
March 2005
MP-1xx SIP
5.7
Getting Acquainted with the Web Interface
Figure 5-2 shows the general layout of the Web Interface screen.
Figure 5-2: MP-1xx Web Interface
Main Menu
Bar
Submenu
Bar
Title Bar
Main Action
Frame
Corporate
Logo
Control
Protocol
The Web Interface screen features the following components:
5.7.1
•
Title bar - contains three configurable elements: corporate logo, a background image and
the product’s name. For information on how to modify these elements refer to Appendix E on
page 213.
•
Main menu bar - always appears on the left of every screen to quickly access parameters,
submenus, submenu options, functions and operations.
•
Submenu bar - appears on the top of screens and contains submenu options.
•
Main action frame - the main area of the screen in which information is viewed and
configured.
•
Corporate logo – AudioCodes’ corporate logo. For information on how to remove this logo
Appendix E on page 213.
•
Control Protocol – the MP-1xx control protocol.
Main Menu Bar
The main menu bar of the Web Interface is divided into the following 7 menus:
•
Quick Setup – Use this menu to configure the gateway’s basic settings; for the full list of
configurable parameters go directly to ‘Protocol Management’ and ‘Advanced Configuration’
menus. An example of the Quick Setup configuration is described in Section 4.2 on page 36.
•
Protocol Management – Use this subdivided menu to configure the gateway’s control
protocol parameters and tables (refer to Section 5.8 on page 44).
MP-1xx SIP User’s Manual
42
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
•
Advanced Configuration – Use this subdivided menu to set the gateway’s advanced
configuration parameters (for advanced users only) (refer to Section 5.9 on page 103).
•
Status & Diagnostics – Use this subdivided menu to view and monitor the gateway’s
channels, Syslog messages, hardware / software product information, and to assess the
gateway’s statistics and IP connectivity information (refer to Section 5.10 on page 124).
•
Software Update – Use this subdivided menu when you want to load new software or
configuration files onto the gateway (refer to Section 5.11 on page 131).
•
Save Configuration – Use this menu to save configuration changes to the non-volatile flash
memory (refer to Section 5.12 on page 139).
•
Reset – Use this menu to remotely reset the gateway. Note that you can choose to save the
gateway configuration to flash memory before reset (refer to Section 5.12 on page 139).
When positioning your curser over a parameter name (or a table) for more than 1 second, a short
description of this parameter is displayed. Note that those parameters that are preceded with an
exclamation mark (!) are Not changeable on-the-fly and require reset.
5.7.2
Saving Changes
To save changes to the volatile memory (RAM) press the Submit button (changes to parameters
with on-the-fly capabilities are immediately available, other parameter are updated only after a
gateway reset). Parameters that are only saved to the volatile memory revert to their previous
settings after hardware reset. When performing a software reset (i.e., via Web or SNMP) you can
choose to save the changes to the non-volatile memory. To save changes so they are available
after a power fail, you must save the changes to the non-volatile memory (flash). When Save
Configuration is performed, all parameters are saved to the flash memory.
To save the changes to flash, take these 2 steps:
1.
Click the Save Configuration button; the ‘Save Configuration to Flash Memory’ screen
appears.
2.
Click the Save Configuration button in the middle of the screen; a confirmation message
appears when the save is complete.
Note: When you reset the MP-1xx from the Web Interface, you can choose to save the
configuration to flash memory.
5.7.3
Entering Phone Numbers in Various Tables
Phone numbers entered into various tables on the gateway, such as the Tel to IP routing table,
must be entered without any formatting characters. For example, if you wish to enter the phone
number 555-1212, it must be entered as 5551212 without the hyphen (-). If the hyphen is entered,
the entry does not work. The hyphen character is used in number entry only, as part of a range
definition. For example, the entry [20-29] means “all numbers in the range 20 to 29”.
Version 4.4
43
March 2005
MP-1xx SIP
5.8
Protocol Management
Use this subdivided menu to configure the gateway’s SIP parameters and tables.
Note:
5.8.1
Those parameters contained within square brackets are the names used to
configure the parameters via the ini file.
Protocol Definition Parameters
Use this submenu to configure the gateway’s specific SIP protocol parameters.
5.8.1.1
General Parameters
Use this screen to configure general SIP parameters.
To configure the general parameters under Protocol Definition, take
these 4 steps:
1.
Open the ‘General Parameters’ screen (Protocol Management menu > Protocol Definition
submenu > General Parameters option); the ‘General Parameters’ screen is displayed.
Figure 5-3: Protocol Definition, General Parameters Screen
MP-1xx SIP User’s Manual
44
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
2.
Configure the general parameters under Protocol Definition according to Table 5-1.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-1: Protocol Definition, General Parameters (continues on pages 45 to 47)
Parameter
Description
PRACK Mode
[PRACKMode]
PRACK mechanism mode for 1XX reliable responses:
Disable
[0].
Supported [1] (default).
Required
[2].
Note 1: The Supported and Required headers contain the “100rel” parameter.
Note 2: MP-1xx sends PRACK message if 180/183 response is received with “100rel” in
the Supported or the Required headers.
Channel Select Mode
[ChannelSelectMode]
Port allocation algorithm for IP to Tel calls.
You can select one of the following methods:
•
By phone number [0] = Select the gateway port according to the called number
(called number is defined in the ‘Endpoint Phone Number’ table).
• Cyclic Ascending [1] = Select the next available channel in an ascending cycle
order. Always select the next higher channel number in the hunt group. When the
gateway reaches the highest channel number in the hunt group, it selects the lowest
channel number in the hunt group and then starts ascending again.
• Ascending [2] = Select the lowest available channel. Always start at the lowest
channel number in the hunt group and if that channel is not available, select the next
higher channel.
• Cyclic Descending [3] = Select the next available channel in descending cycle
order. Always select the next lower channel number in the hunt group. When the
gateway reaches the lowest channel number in the hunt group, it selects the highest
channel number in the hunt group and then starts descending again.
• Descending [4] = Select the highest available channel. Always start at the highest
channel number in the hunt group and if that channel is not available, select the next
lower channel.
• Number + Cyclic Ascending [5] = First select the gateway port according to the
called number (called number is defined in the ‘Endpoint Phone Number’ table). If the
called number isn’t found, then select the next available channel in ascending cyclic
order. Note that if the called number is found, but the port associated with this
number is busy, the call is released.
The default method is ‘By Phone Number’.
Enable Early Media
[EnableEarlyMedia]
No
[0] = Early Media is disabled (default).
Yes [1] = Enable Early Media.
If enabled, the gateway sends 183 Session Progress response with SDP (instead of 180
Ringing), allowing the media stream to be set up prior to the answering of the call.
Note that to send 183 response you must also set the parameter ‘ProgressIndicator2IP’
to 1. If it is equal to 0, 180 Ringing response is sent.
Note: Generally, this parameter is set to 1.
Session-Expires Time
[SIPSessionExpires]
Determines the timeout (in seconds) for keeping a "re-INVITE" message alive within a
SIP session. The SIP session is refreshed (using INVITE) each time this timer expires.
The default is 0 (not activated).
Minimum Session-Expires
[MINSE]
Defines the time (in seconds) that is used in the Min-SE header field. This field defines
the minimum time that the user agent supports for session refresh.
The valid range is 10 to 100000. The default value is 90.
Version 4.4
45
March 2005
MP-1xx SIP
Table 5-1: Protocol Definition, General Parameters (continues on pages 45 to 47)
Parameter
Description
Asserted Identity Mode
[AssertedIdMode]
Disable [0] = None (default).
Adding PAsserted Identity [1].
Adding PPrefered Identity [2].
The Asserted ID mode defines the header that is used in the generated INVITE request.
The header also depends on the calling Privacy: allowed or restricted.
The P-asserted (or P-preferred) headers are used to present the originating party’s
Caller ID. The Caller ID is composed of a Calling Number and (optionally) a Calling
Name.
P-asserted (or P-preferred) headers are used together with the Privacy header. If Caller
ID is restricted the “Privacy: id” is included. Otherwise for allowed Caller ID the “Privacy:
none” is used. If Caller ID is restricted (received from Tel or configured in the gateway),
the From header is set to <anonymous@anonymous.invalid>.
Enable T.38 Fax Relay
[IsFaxUsed]
Determines the SIP signaling method used to establish and convey a fax session after a
fax is detected.
No Fax [0]
= No fax negotiation using SIP signaling (default).
T.38 Relay [1]
= Initiates T.38 fax relay.
G.711 Transport [2] = Initiates fax using the coder G.711 A-law/µ-law (if not previously
selected) with adaptations (refer to note 1).
Note 1: Fax adaptations:
Echo Canceller = On
Silence Compression = Off
Echo Canceller Non-Linear Processor Mode = Off
Dynamic Jitter Buffer Minimum Delay = 40
Dynamic Jitter Buffer Optimization Factor = 13
Note 2: If the gateway initiates a fax session using G.711 (option 2), a ‘gpmd’ attribute is
added to the SDP in the following format:
For A-law: ‘a=gpmd:0 vbd=yes;ecan=on’. For µ-law: ‘a=gpmd:8 vbd=yes;ecan=on’.
Note 3: When ‘IsFaxUsed’ is set to 1 or 2, the parameter ‘FaxTransportMode’ is
ignored.
Detect Fax on Answer Tone
[DetFaxOnAnswerTone]
Initiate T.38 on Preamble [0] = Terminating fax gateway initiates T.38 session on
receiving of HDLC preamble signal from fax (default)
Initiate T.38 on CED
[1] = Terminating fax gateway initiates T.38 session on
receiving of CED answer tone from fax.
Note: This parameters is applicable only if ‘IsFaxUsed = 1’.
SIP Local Port
[LocalSIPPort]
Local UDP port used to receive SIP messages.
The default value is 5060.
SIP Destination Port
[SIPDestinationPort]
SIP UDP destination port for sending SIP messages.
The default value is 5060.
Use “user=phone” in SIP URL No
[IsUserPhone]
Yes
[0] = "user=phone" string isn’t used in SIP URL.
[1] = "user=phone" string is part of the SIP URL (default).
Use “user=phone” in From
header
[IsUserPhoneInFrom]
[0] = Doesn’t use ";user=phone" string in From header (default).
[1] = ";user=phone" string is part of the From header.
Tel to IP No Answer Timeout
[IPAlertTimeout]
No
Yes
Defines the time (in seconds) the gateway waits for a 200 OK response from the called
party (IP side) after sending an Invite message. If the timer expires, the call is released.
The valid range is 0 to 3600. The default value is 180.
[0] = TON/PLAN parameters aren’t included in the RPID header.
Add Number Plan and Type to No
Yes [1] = TON/PLAN parameters are included in the RPID header (default).
Remote Party ID Header
[AddTON2RPI]
If RPID header is enabled (EnableRPIHeader = 1) and ‘AddTON2RPI=1’, it is possible
to configure the calling and called number type and number plan using the Number
Manipulation tables for Tel IP calls.
No
[0] = Interworks the Tel calling name to SIP Display Name (default).
Use Source Number as
Yes [1] = Set Display Name to Calling Number if not configured.
Display Name
[UseSourceNumberAsDispl
ayName]
Applicable to Tel IP calls. If enabled and calling party name is not defined
(CallerDisplayInfoX = <name> is not specified per gateway’s x port), the calling number
is used instead.
MP-1xx SIP User’s Manual
46
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-1: Protocol Definition, General Parameters (continues on pages 45 to 47)
Parameter
Description
Play Ringback Tone to IP
[PlayRBTone2IP]
Don’t Play [0] = Ringback tone isn’t played to the IP side of the call (default).
Play
[1] = Ringback tone is played to the IP side of the call after SIP 183
session progress response is sent.
Note 1: To enable the gateway to send a 183 response, set ‘EnableEarlyMedia’ to 1.
Note 2: If ‘EnableDigitDelivery = 1’, the gateway doesn’t play a Ringback tone to IP and
doesn’t send a 183 response.
Play Ringback Tone to Tel
[PlayRBTone2Tel]
Don’t Play [0] = Ringback Tone isn’t played.
Always Play [1] = Ringback Tone is played to the Tel side of the call when 180/183
response is received.
Play According to PI [3] = N/A.
Play According to 180/183 [2] = Ringback Tone is played to the Tel side of the call if no
SDP is received in 180/183 responses. If 180/183 with SDP message is received, the
gateway cuts through the voice channel and doesn’t play Ringback tone (default).
Retransmission Parameters
SIP T1 Retransmission Timer The time interval (in msec) between the first transmission of a SIP message and the first
[msec]
retransmission of the same message.
[SipT1Rtx]
The default is 500.
Note: The time interval between subsequent retransmissions of the same SIP message
starts with SipT1Rtx and is multiplied by two until SipT2Rtx.
For example (assuming that SipT1Rtx = 500 and SipT2Rtx = 4000):
The first retransmission is sent after 500 msec.
The second retransmission is sent after 1000 (2*500) msec.
The third retransmission is sent after 2000 (2*1000) msec.
The fourth retransmission and subsequent retransmissions until SIPMaxRtx are sent
after 4000 (2*2000) msec.
SIP T2 Retransmission Timer The maximum interval (in msec) between retransmissions of SIP messages.
[msec]
The default is 4000.
[SipT2Rtx]
Note: The time interval between subsequent retransmissions of the same SIP message
starts with SipT1Rtx and is multiplied by two until SipT2Rtx.
SIP Maximum Rtx
[SIPMaxRtx]
Version 4.4
Number of UDP retransmissions of SIP messages.
The range is 1 to 7.
The default value is 7.
47
March 2005
MP-1xx SIP
5.8.1.2
Proxy & Registration Parameters
Use this screen to configure parameters that are associated with Proxy and Registration.
To configure the Proxy & Registration parameters, take these 4 steps:
1.
Open the ‘Proxy & Registration’ parameters screen (Protocol Management menu >
Protocol Definition submenu > Proxy & Registration option); the ‘Proxy & Registration’
parameters screen is displayed.
Figure 5-4: Proxy & Registration Parameters Screen
MP-1xx SIP User’s Manual
48
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
2.
Configure the Proxy & Registration parameters according to Table 5-2.
3.
Click the Submit button to save your changes, or click the Register or Un-Register buttons
to save your changes and to register / unregister to a Proxy / Registrar.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-2: Proxy & Registration Parameters (continues on pages 49 to 52)
Parameter
Description
Enable Proxy
[IsProxyUsed]
Don’t Use Proxy [0] = Proxy isn’t used, the internal routing table is used instead (default).
Use Proxy
[1] = Proxy is used.
If you are using a Proxy server, enter the IP address of the primary Proxy server in the
Proxy IP address field.
If you are not using a Proxy server, you must configure the Tel to IP Routing table on the
gateway (described in Section 5.8.4.2 on page 75).
Proxy Name
[ProxyName]
Defines the Home Proxy Domain Name.
If specified, the Proxy Name is used as Request-URI in REGISTER, INVITE and other SIP
messages. If not specified, the Proxy IP address is used instead.
Proxy IP Address
[ProxyIP]
IP address (and optionally port number) of the primary Proxy server you are using.
Enter the IP address as FQDN or in dotted format notation (for example 201.10.8.1).
You can also specify the selected port in the format: <IP Address>:<port>.
This parameter is applicable only if you select ‘Yes’ in the ‘Is Proxy Used’ field.
If you enable Proxy Redundancy (by setting EnableProxyKeepAlive=1), the gateway can
work with up to three Proxy servers. If there is no response from the primary Proxy, the
gateway tries to communicate with the redundant Proxies. When a redundant Proxy is
found, the gateway either continues working with it until the next failure occurs or reverts
to the primary Proxy (refer to the ‘Redundancy Mode’ parameter). If none of the Proxy
servers respond, the gateway goes over the list again.
The gateway also provides real time switching (hotswap mode), between the primary and
redundant proxies (‘IsProxyHotSwap=1’). If the first Proxy doesn’t respond to Invite
message, the same Invite message is immediately sent to the second Proxy.
Note 1: If ‘EnableProxyKeepAlive=1’, the gateway monitors the connection with the
Proxies by using keep-alive messages ("OPTIONS").
Note 2: To use Proxy Redundancy, you must specify one or more redundant Proxies
using multiple ’ProxyIP= <IP address>’ definitions.
Note 3: When port number is specified (e.g., domain.com:5080), DNS SRV queries aren’t
performed, even if ‘EnableProxySRVQuery’ is set to 1.
Gateway Name
[SIPGatewayName]
Use this parameter to assign a name to the device (For example: ‘gateway1.com’). Ensure
that the name you choose is the one that the Proxy is configured with to identify your
media gateway.
Note: If specified, the gateway Name is used as the host part of the SIP URL, in both ‘To’
and ‘From’ headers. If not specified, the gateway IP address is used instead (default).
Gateway Registration Name Defines the user name that is used in From and To headers of Register messages.
[GWRegistrationName]
Applicable only to single registration per gateway (’AuthenticationMode = 1).
If ‘GWRegistrationName’ isn’t specified (default), the ’Username’ parameter is used
instead.
Note: If ‘“AuthenticationMode=0’, all the gateway’s endpoints are registered with a user
name that equals to the endpoint’s phone number.
First Redundant Proxy IP
Address
[ProxyIP]
IP addresses of the first redundant Proxy you are using.
Enter the IP address as FQDN or in dotted format notation (for example 192.10.1.255).
You can also specify the selected port in the format: <IP Address>:<port>.
Note 1: This parameter is available only if you select “Yes” in the ‘Enable Proxy’ field.
Note 2: When port number is specified, DNS SRV queries aren’t performed, even if
‘EnableProxySRVQuery’ is set to 1.
ini file note: The IP address of the first redundant Proxy is defined by the second
repetition of the ini file parameter ‘ProxyIP’.
Version 4.4
49
March 2005
MP-1xx SIP
Table 5-2: Proxy & Registration Parameters (continues on pages 49 to 52)
Parameter
Description
Second Redundant Proxy
IP Address
[ProxyIP]
IP addresses of the second redundant Proxy you are using.
Enter the IP address as FQDN or in dotted format notation (for example 192.10.1.255).
You can also specify the selected port in the format: <IP Address>:<port>.
Note 1: This parameter is available only if you select “Yes” in the ‘Enable Proxy’ field.
Note 2: When port number is specified, DNS SRV queries aren’t performed, even if
‘EnableProxySRVQuery’ is set to 1.
ini file note: The IP address of the second redundant Proxy is defined by the third
repetition of the ini file parameter ‘ProxyIP’.
Third Redundant Proxy IP
Address
[ProxyIP]
IP addresses of the third redundant Proxy you are using.
Enter the IP address as FQDN or in dotted format notation (for example 192.10.1.255).
You can also specify the selected port in the format: <IP Address>:<port>.
Note 1: This parameter is available only if you select “Yes” in the ‘Enable Proxy’ field.
Note 2: When port number is specified, DNS SRV queries aren’t performed, even if
‘EnableProxySRVQuery’ is set to 1.
ini file note: The IP addresses of the third redundant Proxy is defined by the forth
repetition of the ini file parameter ‘ProxyIP’.
Enable Proxy SRV Queries Enables the use of DNS Service Record (SRV) queries to discover Proxy servers.
[EnableProxySRVQuery] Disable [0] = Disabled (default).
Enable [1] = Enabled.
If enabled and the Proxy IP address parameter contains a domain name without port
definition (e.g., ProxyIP = domain.com), an SRV query is performed. The SRV query
returns up to four Proxy host names and their weights. The gateway then performs DNS
A-record queries for each Proxy host name (according to the received weights) to locate
up to four Proxy IP addresses. Therefore, if the first SRV query returns two domain
names, and the A-record queries return 2 IP addresses each, no more searches are
performed.
If the Proxy IP address parameter contains a domain name with port definition (e.g.,
ProxyIP = domain.com:5080), the gateway performs a regular DNS A-record query.
Note: This mechanism is applicable only if ‘EnableProxyKeepAlive = 1’.
Parking [0] = Gateway continues working with the last active Proxy until the next failure
Redundancy Mode
[ProxyRedundancyMode] (default).
Homing [1] = Gateway always tries to work with the primary Proxy server (switches back
to the main Proxy whenever it is available).
Note: To use Redundancy Mode, enable Keep-alive with Proxy option (Enable Proxy
Keep Alive = Yes).
Is Proxy Trusted
[IsTrustedProxy]
This parameter isn’t applicable and must always be set to ‘Yes’ [1].
The parameter ‘AssertedIdMode’ should be used instead.
Enable Registration
[IsRegisterNeeded]
No
[0] = Gateway doesn’t register to Proxy / Registrar (default).
Yes [1] = Gateway registers to Proxy / Registrar when the device is powered up and
every Registration Time seconds.
Note: The gateway sends a register request for each channel or for the entire gateway
(according to the Authentication Mode parameter).
Registrar Name
[RegistrarName]
Registrar Domain Name.
If specified, the name is used as Request-URI in Register messages.
If isn’t specified (default), the Registrar IP address or Proxy name or Proxy IP address is
used instead.
Registrar IP Address
[RegistrarIP]
IP address of Registrar server (optional).
Enter the IP address in dotted format notation, for example 201.10.8.1.
Note: If not specified, the Register request is sent to the primary Proxy server (refer to
‘Proxy IP address’ parameter).
Registration Time
[RegistrationTime]
Time (in seconds) for which registration to a Proxy server is valid. The value is used in the
"Expires = " header. Typically a value of 3600 is assigned, for one hour registration.
The gateway resumes registration when half the defined timeout period expires.
The default is 3600 seconds.
MP-1xx SIP User’s Manual
50
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-2: Proxy & Registration Parameters (continues on pages 49 to 52)
Parameter
Description
Re-registration Timing (%) Defines the re-registration timing (in percentage). The timing is a percentage of the re[RegistrationTimeDivider] register timing set by the Registration server.
The valid range is 50 to 100. The default value is 50.
For example: If ‘RegistrationTimeDivider = 70’ (%) and Registration Expires time = 3600,
the gateway resends its registration request after 3600 x 70% = 2520 sec.
Registration Retry Time
[RegistrationRetryTime]
Defines the time period (in seconds) after which a Registration request is resent if
registration fails with 4xx, or there is no response from the Proxy/Registrar.
The default is 30 seconds. The range is 10 to 3600.
Enable Proxy Keep Alive
[EnableProxyKeepAlive]
No
[0] = Disable (default).
Yes [1] = Keep alive with Proxy is enabled.
If enabled, ‘OPTIONS’ SIP message is sent every ‘Proxy Keep-Alive Time’.
Note: This parameter must be enabled when Proxy redundancy is used.
Proxy Keep Alive Time
[ProxyKeepAliveTime]
Defines the Proxy keep-alive time interval (in seconds) between OPTIONS messages.
The default value is 60 seconds.
Use Gateway Name for
OPTIONS
[UseGatewayNameForOpt
ions]
No
[0] = Use the gateway’s IP address in keep-alive OPTIONS messages (default).
Yes [1] = Use ‘GatewayName’ in keep-alive OPTIONS messages.
The OPTIONS Request-URI host part contains either the gateway’s IP address or a string
defined by the parameter ‘Gatewayname’.
The gateway uses the OPTIONS request as a keep-alive message to its primary and
redundant Proxies.
Enable Fallback to Routing
Table
[IsFallbackUsed]
No
[0] = Gateway fallback is not used (default).
Yes [1] = Internal Tel to IP Routing table is used when Proxy servers are not available.
When the gateway falls back to the internal Tel to IP Routing table, the gateway continues
scanning for a Proxy. When the gateway finds an active Proxy, it switches from internal
routing back to Proxy routing.
Note: To enable the redundant Proxies mechanism set ‘EnableProxyKeepAlive’ to 1.
PreferRouteTable
[Prefer Routing Table]
Determines if the local Tel to IP routing table takes precedence over a Proxy for routing
calls.
No
[0] = Only Proxy is used to route calls (default).
Yes [1] = The Proxy checks the 'Destination IP Address' field in the 'Tel to IP Routing'
table for a match with the outgoing call. Only if a match is not found, a Proxy is used.
Note: Applicable only if Proxy is not always used (‘AlwaysSendToProxy’ = 0,
‘SendInviteToProxy’ = 0).
Use Routing Table for Host Use the internal Tel to IP routing table to obtain the URL Host name and (optionally) an IP
Names and Profiles
profile (per call), even if Proxy server is used.
[AlwaysUseRouteTable]
No
[0] = Don’t use (default).
Yes [1] = Use.
Note: This Domain name is used, instead of Proxy name or Proxy IP address, in the
INVITE SIP URL.
Always Use Proxy
[AlwaysSendToProxy]
No
[0] = Use standard SIP routing rules (default).
Yes [1] = All SIP messages and Responses are sent to Proxy server.
Note: Applicable only if Proxy server is used.
Send All Invite to Proxy
[SendInviteToProxy]
No
[0] = Invite messages, generated as a result of Transfer or Redirect, are sent
directly to the URL (according to the refer-to header in the REFER message or contact
header in 30x response) (default).
Yes [1] = All Invite messages, including those generated as a result of Transfer or
Redirect are sent to Proxy.
Note: Applicable only if Proxy server is used and “AlwaysSendtoProxy=0”.
Enable Proxy Hot-Swap
[IsProxyHotSwap]
Enable Proxy Hot-Swap redundancy mode.
No
[0] = Disabled (default).
Yes [1] = Enabled.
If Hot Swap is enabled, SIP Invite message is first sent to the primary Proxy server. If
there is no response from the primary Proxy server for ‘Number of RTX before Hot-Swap’
retransmissions, the Invite message is resent to the redundant Proxy server.
Version 4.4
51
March 2005
MP-1xx SIP
Table 5-2: Proxy & Registration Parameters (continues on pages 49 to 52)
Parameter
Description
Number of RTX Before Hot- Number of retransmitted Invite messages before call is routed (hot swapped) to another
Swap
Proxy.
[ProxyHotSwapRtx]
The range is 1-30. The default is 3.
Note: This parameter is also used for alternative routing using the Tel to IP Routing table.
If a domain name in the routing table is resolved into 2 IP addresses, and if there is no
response for ‘ProxyHotSwapRtx’ retransmissions to the Invite message that is sent to the
first IP address, the gateway immediately initiates a call to the second IP address.
User Name
[UserName]
Note: The Authentication
table can be used instead.
Username used for Registration and for BASIC/DIGEST authentication process with
Proxy.
Parameter doesn’t have a default value (empty string).
Note: Applicable only if single gateway registration is used (‘Authentication Mode =
Authentication Per gateway’).
Password
[Password]
Password used for BASIC/DIGEST authentication process with Proxy. Single password is
used for all gateway ports.
The default is “Default_Passwd”.
Note: The Authentication table can be used instead.
Cnonce
[Cnonce]
String used by the server and client to provide mutual authentication. (Free format i.e.,
“Cnonce = 0a4f113b”).
The default is “Default_Cnonce”.
Authentication Mode
[AuthenticationMode]
Per Endpoint [0] = Registration & Authentication separately for each endpoint (default).
Per gateway [1] = Single Registration & Authentication for the gateway.
Per Ch. Select Mode [2] = N/A.
Usually Authentication on a per endpoint basis is used for FXS gateways, in which each
endpoint registers (and authenticates) separately with its own username and password.
Single Registration and Authentication (Authentication Mode=1) is usually defined for FXO
gateways.
MP-1xx SIP User’s Manual
52
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.1.3
5. Configuring the MP-1xx
Coders
From the Coders screen you can configure the first to fifth preferred coders (and their
corresponding ptimes) for the gateway. The first coder is the highest priority coder and is used by
the gateway whenever possible. If the far end gateway cannot use the coder assigned as the first
coder, the gateway attempts to use the next coder and so forth.
To configure the Gateway’s coders, take these 6 steps:
1.
Open the ‘Coders’ screen (Protocol Management menu > Protocol Definition submenu >
Coders option); the ‘Coders’ screen is displayed.
Figure 5-5: Coders Screen
2.
From the coder drop-down list, select the coder you want to use. For the full list of available
coders and their corresponding ptimes refer to Table 5-3.
Note: Each coder can appear only once.
3.
From the drop-down list to the right of the coder list, select the size of the Voice Packet
(ptime) used with this coder in milliseconds. Selecting the size of the packet determines how
many coder payloads are combined into one RTP (voice) packet.
Note 1: The ptime packetization period depends on the selected coder name.
Note 2: If not specified, the ptime gets a default value.
Note 3: The ptime specifies the maximum packetization time the gateway can receive.
4.
Repeat steps 2 and 3 for the second to fifth coders (optional).
5.
Click the Submit button to save your changes.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Note:
Version 4.4
Only the ptime of the first coder in the defined coder list is declared in
Invite/200 OK SDP, even if multiple coders are defined.
53
March 2005
MP-1xx SIP
Table 5-3: ini File Coder Parameter
Parameter
Description
CoderName
Enter the coders in the format: CoderName=<Coder>,<ptime>.
For example:
CoderName = g711Alaw64k,20
CoderName = g711Ulaw64k,40
CoderName = g7231,90
Note 1: This parameter (CoderName) can appear up to 10 times.
Note 2: The coder name is case-sensitive.
You can select the following coders:
g711Alaw64k
– G.711 A-law.
g711Ulaw64k
– G.711 µ-law.
g7231
– G.723.1 6.3 kbps (default).
g7231r53
– G.723.1 5.3 kbps.
g726
– G.726 ADPCM 32 kbps (Payload Type = 35).
g729
– G.729A.
Note: G.729B is supported if the coder G.729 is selected and
‘EnableSilenceCompression’ equals 1 or 2.
The RTP packetization period (ptime, in msec) depends on the selected coder name, and
can have the following values:
g711
g729
g723
G.726
MP-1xx SIP User’s Manual
– 10, 20, 30, 40, 50, 60, 80, 100, 120 (default=20).
– 10, 20, 30, 40, 50, 60, 80, 100, 120 (default=20).
– 30, 60, 90, 120, 150 (default = 30).
– 10, 20, 40, 60, 80, 100, 120 (default=20).
54
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.1.4
5. Configuring the MP-1xx
DTMF & Dialing Parameters
Use this screen to configure parameters that are associated with DTMF and dialing.
To configure the dialing parameters, take these 4 steps:
1.
Open the ‘DTMF & Dialing’ screen (Protocol Management menu > Protocol Definition
submenu > DTMF & Dialing option); the ‘DTMF & Dialing’ parameters screen is displayed.
Figure 5-6: DTMF & Dialing Parameters Screen
2.
Configure the DTMF & Dialing parameters according to Table 5-4.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-4: DTMF & Dialing Parameters (continues on pages 55 to 57)
Parameter
Description
Max Digits in Phone Num
[MaxDigits]
Maximum number of digits that can be dialed.
You can enter a value from 1 to 49.
The default value is 5.
Note: Dialing ends when the maximum number of digits is dialed, the Interdigit Timeout
expires, the '#' key is dialed, or a digit map pattern is matched.
Note: Digit Mapping Rules
can be used instead.
Inter Digits Timeout [sec]
[TimeBetweenDigits]
Version 4.4
Time in seconds that the gateway waits between digits dialed by the user. When the
Interdigit Timeout expires, the gateway attempts to dial the digits already received.
You can enter a value of 1 to 10 seconds. The default value is 4 seconds.
55
March 2005
MP-1xx SIP
Table 5-4: DTMF & Dialing Parameters (continues on pages 55 to 57)
Parameter
Description
Use Out-of-Band DTMF
Use out-of-band signaling to relay DTMF digits.
No
[0] = DTMF digits are sent in-band (default).
Yes [1] = DTMF digits are sent out-of-band according to the parameter ‘Out-of-band
DTMF format’.
[IsDTMFUsed]
Note: When out-of-band DTMF transfer is used (Enable DTMF = Yes), the parameter
‘DTMF Transport Type’ is automatically set to 0 (erase the DTMF digits from the RTP
stream).
Out-of-Band DTMF Format
[OutOfBandDTMFFormat]
The exact method to send out-of-band DTMF digits.
Info (Nortel)
[1] = Sends DTMF digits according with "IETF draft-choudhuri-sip-infodigit-00".
Info (Cisco)
[2] = Sends DTMF digits according with Cisco format (default).
Notify (3Com) [3] = NOTIFY format <draft-mahy-sipping-signaled-digits-01.txt>.
Note 1: To use out-of-band DTMF, set ‘Enable DTMF = yes’ (‘IsDTMFUsed=1’).
Note 2: When using out-of-band DTMF, the “DTMFTransportType” parameter is
automatically set to 0, to erase the DTMF digits from the RTP stream.
Declare RFC 2833 in SDP
[RxDTMFOption]
Defines the supported Receive DTMF negotiation method.
No
[0] = Don’t declare RFC 2833 Telephony-event parameter in SDP
Yes [3] = Declare RFC 2833 Telephony-event parameter in SDP (default)
The MP-1xx is designed to always be receptive to RFC 2833 DTMF relay packets.
Therefore, it is always correct to include the “Telephony-event” parameter as a default in
the SDP. However some gateways use the absence of the “telephony-event” from the
SDP to decide to send DTMF digits in-band using G.711 coder, if this is the case you
can set “RxDTMFOption=0”.
DTMF RFC 2833 Negotiation
[TxDTMFOption]
No
[0] = No negotiation, DTMF digit is sent according to the parameters ‘DTMF
Transport Type’ and ‘RFC2833PayloadType’.
Yes [4] = Enable RFC 2833 payload type (PT) negotiation (default).
Note 1: This parameter is applicable only if “IsDTMFUsed=0” (out-of-band DTMF is not
used).
Note 2: If enabled, the gateway:
•
•
•
Negotiates RFC 2833 payload type using local and remote SDPs.
Sends DTMF packets using RFC 2833 PT according to the PT in the received SDP.
Expects to receive RFC 2833 packets with the same PT as configured by the
“RFC2833PayloadType” parameter.
Note 3: If the remote party doesn’t include the RFC 2833 DTMF relay payload type in
the SDP, the gateway uses the same PT for send and for receive.
Note 4: If TxDTMFOption is set to 0, the RFC 2833 payload type is set according to the
parameter ‘RFC2833PayloadType’ for both transmit and receive.
RFC 2833 Payload Type
[RFC2833PayloadType]
The RFC 2833 DTMF relay dynamic payload type.
Range: 96 to 99, 106 to 127; Default = 96
The 100, 102 to 105 range is allocated for proprietary usage.
Note 1: Cisco is using payload type 101 for RFC 2833.
Note 2: When RFC 2833 payload type (PT) negotiation is used (TxDTMFOption=4), this
payload type is used for the received DTMF packets. If negotiation isn’t used, this
payload type is used for receive and for transmit.
Use Info for Hook-Flash
[IsHookFlashUsed]
No
[0] = INFO message isn’t sent (default).
Yes [1] = Proprietary INFO message with hook-flash is sent when hook-flash is
detected (FXS). FXO gateways generate a hook-flash signal when INFO message with
hook-flash is received.
Note: When either of the supplementary services (Hold, Transfer or Call Waiting) is
enabled, hook-flash is used internally, and thus the hook-flash signal isn’t sent via an
INFO message.
MP-1xx SIP User’s Manual
56
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-4: DTMF & Dialing Parameters (continues on pages 55 to 57)
Parameter
Description
Digit Mapping Rules
[DigitMapping]
Digit map pattern. If the digit string (dialed number) has matched one of the patterns in
the digit map, the gateway stops collecting digits and starts to establish a call with the
collected number
The digit map pattern contains up to 8 options, each up to 22 characters that are
separated by a vertical bar (|).
Available notations:
• [n-m] represents a range of numbers
• ‘.’ (single dot) represents repetition
• ‘x’ represents any single digit
• ‘T’ represents a dial timer (configured by TimeBetweenDigits parameter)
• ‘S’ should be used when a specific rule, that is part of a general rule, is to be
applied immediately. For example, if you enter the general rule x.T and the specific
rule 11x, you should append ‘S’ to the specific rule 11xS.
For example: 11xS|00T|[1-7]xxx|8xxxxxxx|#xxxxxxx|*xx|91xxxxxxxxxx|9011x.T
Dial Tone Duration [sec]
[TimeForDialTone]
Time in seconds that the dial tone is played.
The default time is 16 seconds.
FXS Gateway ports play the dial tone after phone is picked up; while FXO Gateway
ports play the dial tone after port is seized in response to ringing.
Note 1: During play of dial tone, the Gateway waits for DTMF digits.
Note 2: ‘TimeForDialTone’ is not applicable when Automatic Dialing is enabled.
Hot Line Dial Tone Duration
[HotLineDialToneDuration]
Duration (in seconds) of the Hotline dial tone.
If no digits are received during the Hotline dial tone duration, the gateway initiates a call
to a preconfigured number (set in the automatic dialing table).
The valid range is 0 to 60. The default time is 5 seconds.
Applicable to FXS and FXO gateways.
Enable Special Digits
[IsSpecialDigits]
Disable [0] = "*" or "#" terminate number collection (default).
Enable [1] = if you want to allow "*" and "#" to be used for telephone numbers dialed
by a user or entered for the endpoint telephone number.
Note: The # and * can always be used as first digit of a dialed number, even if you
select ‘Disable’ for this parameter.
Default Destination Number
[DefaultNumber]
Defines the telephone number that the gateway uses if the parameters ‘TrunkGroup_x’
or ’ChannelList‘ don’t include a phone number. The parameter is used as a starting
number for the list of channels comprising all hunt groups in the gateway.
Version 4.4
57
March 2005
MP-1xx SIP
5.8.2
Configuring the Advanced Parameters
Use this submenu to configure the gateway’s advanced control protocol parameters.
5.8.2.1
General Parameters
Use this screen to configure general control protocol parameters.
To configure the general parameters under Advanced Parameters, take
these 4 steps:
1.
Open the ‘General Parameters’ screen (Protocol Management menu > Advanced
Parameters submenu > General Parameters option); the ‘General Parameters’ screen is
displayed.
Figure 5-7: Advanced Parameters, General Parameters Screen
MP-1xx SIP User’s Manual
58
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
2.
Configure the general parameters under ‘Advanced Parameters’ according to Table 5-5.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-5: Advanced Parameters, General Parameters (continues on pages 59 to 62)
Parameter
Description
Signaling DiffServ
[ControlIPDiffServ]
Defines the value of the 'DiffServ' field in the IP header for SIP messages.
The valid range is 0 to 63. The default value is 0.
IP Security
[SecureCallsFromIP]
No
[0] = Gateway accepts all SIP calls (default).
Yes [1] = Gateway accepts SIP calls only from IP addresses defined in the Tel to IP
routing table. The gateway rejects all calls from unknown IP addresses.
For detailed information on the Tel to IP Routing table refer to Section 5.8.4.2 on page
75.
Note: Specifying the IP address of a Proxy server in the Tel to IP Routing table enables
the gateway to only accept calls originating in the Proxy server and rejects all other
calls.
Filter Calls to IP
[FilterCalls2IP]
Don’t Filter [0]
Filter [1]
= Disabled (default)
= Enabled
If the filter calls to IP feature is enabled, then when a Proxy is used, the gateway first
checks the Tel IP routing table before making a call through the Proxy. If the number is
not allowed (number isn’t listed or a Call Restriction routing rule, IP=0.0.0.0, is applied),
the call is released.
Enable Digit Delivery to IP
[EnableDigitDelivery2IP]
Disable [0] = Disabled (default).
Enable [1] = Enable digit delivery to IP.
The digit delivery feature enables sending of DTMF digits to the destination IP address
after the Tel IP call was answered.
To enable this feature, modify the called number to include at least one ’p’ character.
The gateway uses the digits before the ‘p’ character in the initial Invite message. After
the call was answered the gateway waits for the required time (# of ‘p’ * 1.5 seconds)
and then sends the rest of the DTMF digits using the method chosen (in-band, out-ofband).
Note: The called number can include several ‘p’ characters (1.5 seconds pause).
For example, the called number can be as follows: pp699, p9p300.
Enable Digit Delivery to Tel
[EnableDigitDelivery]
Disable [0]
Enable [1]
= Disabled (default).
= Enable Digit Delivery feature for MP-1xx/FXO & FXS.
The digit delivery feature enables sending of DTMF digits to the gateway’s port after the
line is offhooked (FXS) or seized (FXO). For IP Tel calls, after the line is offhooked /
seized, the MP-1xx plays the DTMF digits (of the called number) towards the phone line.
Note 1: The called number can also include the characters ‘p’ (1.5 seconds pause) and
‘d’ (detection of dial tone). If the character ‘d’ is used, it must be the first “digit” in the
called number. The character ‘p’ can be used several times.
For example, the called number can be as follows: d1005, dpp699, p9p300.
To add the ‘d’ and ‘p’ digits, use the usual number manipulation rules.
Note 2: To use this feature with FXO gateways, configure the gateway to work in one
stage dialing mode.
Note 3: If the parameter ‘EnableDigitDelivery’ is enabled, it is possible to configure the
gateway to wait for dial tone per destination phone number (before or during dialing of
destination phone number), therefore the parameter ‘IsWaitForDialTone’ (that is
configurable for the entire gateway) is ignored.
Note 4: The FXS gateway sends 200 OK messages only after it finishes playing the
DTMF digits to the phone line.
Version 4.4
59
March 2005
MP-1xx SIP
Table 5-5: Advanced Parameters, General Parameters (continues on pages 59 to 62)
Parameter
Description
Enable DID Wink
[EnableDIDWink]
Disable [0] = DID is disabled (default).
Enable [1] = Enable DID.
If enabled, the MP-1xx can be used for connection to EIA/TIA-464B DID Loop Start
lines. Both FXO (detection) and FXS (generation) are supported.
An FXO gateway dials DTMF digits after a Wink signal is detected (instead of a Dial
tone).
An FXS gateway generates the Wink signal after the detection of offhook (instead of
playing a Dial tone).
Reanswer Time
[RegretTime]
The time period (in seconds) after user hangs up the phone and before call is
disconnected (FXS). Also called regret time.
The default time is 0 seconds.
Disconnect and Answer Supervision
Enable Polarity Reversal
[EnableReversalPolarity]
Disable [0] = Disable the polarity reversal service (default).
Enable [1] = Enable the polarity reversal service.
If the polarity reversal service is enabled, then the FXS gateway changes the line
polarity on call answer and changes it back on call release.
The FXO gateway sends a 200 OK response when polarity reversal signal is detected,
and releases a call when a second polarity reversal signal is detected.
Enable Current Disconnect
[EnableCurrentDisconnect]
Disable [0] = Disable the current disconnect service (default).
Enable [1] = Enable the current disconnect service.
If the current disconnect service is enabled, the FXO gateway releases a call when
current disconnect signal is detected on its port, while the FXS gateway generates a
"Current Disconnect Pulse" after a call is released from IP.
The current disconnect duration is determined by the parameter
‘CurrentDisconnectDuration’. The current disconnect threshold (FXO only) is determined
by the parameter ‘CurrentDisconnectDefaultThreshold’. The frequency at which the
analog line voltage is sampled is determined by the parametr
‘TimeToSampleAnalogLineVoltage’.
No [0]
= Don’t release the call.
Disconnect on Broken
Yes [1] = Call is released if RTP packets are not received for a predefined timeout
Connection
[DisconnectOnBrokenConn (default).
ection]
Note 1: If enabled, the timeout is set by the parameter
‘BrokenConnectionEventTimeout’, in 100 msec resolution. The default timeout is 10
seconds: (BrokenConnectionEventTimeout =100).
Note 2: This feature is applicable only if RTP session is used without Silence
Compression. If Silence Compression is enabled, the Gateway doesn’t detect that the
RTP connection is broken.
Note 3: During a call, if the source IP address (from where the RTP packets were sent)
is changed without notifying the Gateway, the Gateway filters these RTP packets. To
overcome this issue, set ‘DisconnectOnBrokenConnection=0’; the Gateway doesn’t
detect RTP packets arriving from the original source IP address, and switches (after 300
msec) to the RTP packets arriving from the new source IP address.
Broken Connection Timeout
[BrokenConnectionEventTi
meout]
The amount of time (in 100 msec units) an RTP packet isn’t received, after which a call
is disconnected.
The valid range is 1 to 1000. The default value is 100 (10 seconds).
Note 1: Applicable only if ‘DisconnectOnBrokenConnection = 1’.
Note 2: Currently this feature works only if Silence Suppression is disabled.
Disconnect Call on Silence
Detection
[EnableSilenceDisconnect]
Yes [1] = The FXO gateway disconnect calls in which silence occurs in both (call)
directions for more than 120 seconds.
No
[0] = Call is not disconnected when silence is detected (default).
The silence duration can be set by the ‘FarEndDisconnectSilencePeriod’ parameter
(default 120).
Note: To activate this feature set DSP Template to 2 or 3.
Silence Detection Period [sec] Duration of silence period (in seconds) prior to call disconnection.
[FarEndDisconnectSilenceP The range is 10 to 28800 (8 hours). The default is 120 seconds.
eriod]
Applicable to gateways, that use DSP templates 2 or 3.
MP-1xx SIP User’s Manual
60
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-5: Advanced Parameters, General Parameters (continues on pages 59 to 62)
Parameter
Description
Silence Detection Method
Silence detection method.
[FarEndDisconnectSilenceM None [0] = Silence detection option is disabled.
ethod]
Packets Count [1] = According to packet count.
Voice/Energy Detectors [2] = According to energy and voice detectors (default).
All [3] = According to packet count and energy / voice detectors.
CDR and Debug
CDR Server IP Address
[CDRSyslogServerIP]
Defines the destination IP address for CDR logs.
The default value is a null string that causes the CDR messages to be sent with all
Syslog messages.
Note: The CDR messages are sent to UDP port 514 (default Syslog port).
CDR Report Level
[CDRReportLevel]
None [0] = Call Detail Recording (CDR) information isn’t sent to the Syslog server
(default).
End Call [1] = CDR information is sent to the Syslog server at end of each Call.
Start & End Call [2] = CDR information is sent to the Syslog server at the start and at
the end of each Call.
The CDR Syslog message complies with RFC 3161 and is identified by:
Facility = 17 (local1) and Severity = 6 (Informational).
Debug Level
[GwDebugLevel]
Syslog logging level. One of the following debug levels can be selected:
0 [0] = Debug is disabled (default)
1 [1] = Flow debugging is enabled
2 [2] = Flow and device interface debugging are enabled
3 [3] = Flow, device interface and stack interface debugging are enabled
4 [4] = Flow, device interface, stack interface and session manager debugging are
enabled
5 [5] = Flow, device interface, stack interface, session manager and device interface
expanded debugging are enabled.
Note: Usually set to 5 if debug traces are needed.
Misc. Parameters
Progress Indicator to IP
[ProgressIndicator2IP]
No PI [0] = For IP Tel calls, the gateway sends “180 Ringing” SIP response to IP after
placing a call to phone (FXS) or to PBX (FXO).
PI = 1, PI = 8 [1], [8] = For IP Tel calls, if ‘EnableEarlyMedia=1’, the gateway sends
“183 session in progress” message + SDP, immediately after a call is placed to
Phone/PBX. This is used to cut through the voice path, before remote party answers the
call, enabling the originating party to listen to network Call Progress Tones (such as
Ringback tone or other network announcements).
Not Configured [-1] = Default values are used.
The default for FXO gateways is 1; The default for FXS gateways is 0.
Enable Busy Out
[EnableBusyOut]
No
[0] = ‘Busy out’ feature is not used (default).
Yes [1] = The MP-1xx/FXS gateway plays a reorder tone when the phone is offhooked
and one of the following occurs:
There is a network problem.
Proxy servers do not respond and the internal routing table is not configured.
Default Release Cause
[DefaultReleaseCause]
Default Release Cause (to IP) for IP Tel calls, used when the gateway initiates a call
release, and if an explicit matching cause for this release isn’t found, a default release
cause can be configured:
The default release cause is: NO_ROUTE_TO_DESTINATION (3).
Other common values are: NO_CIRCUIT_AVAILABLE (34),
DESTINATION_OUT_OF_ORDER (27), etc.
Note: The default release cause is described in the Q.931 notation, and is translated to
corresponding SIP 40x or 50x value. For example: 404 for 3, 503 for 34 and 502 for 27.
Delay After Reset [sec]
[GWAppDelayTime]
Version 4.4
Defines the amount of time (in seconds) the gateway’s operation is delayed after a reset
cycle.
The valid range is 0 to 600. The default value is 5 seconds.
Note: This feature helps to overcome connection problems caused by some LAN
routers or IP configuration parameters change by a DHCP Server.
61
March 2005
MP-1xx SIP
Table 5-5: Advanced Parameters, General Parameters (continues on pages 59 to 62)
Parameter
Description
Max Number of Active Calls
[MaxActiveCalls]
Defines the maximum number of calls that the gateway can have active at the same
time. If the maximum number of calls is reached, new calls are not established.
The default value is max available channels (no restriction on the maximum number of
calls). The valid range is 1 to max number of channels.
Max Call Duration (sec)
[MaxCallDuration]
Defines the maximum call duration in seconds. If this time expires, both sides of the call
are released (IP and Tel).
The default time is 0 seconds (no limitation).
Enable LAN Watchdog
[EnableLanWatchDog]
Disable [0] = Disable LAN Watch-Dog (default).
Enable [1] = Enable LAN Watch-Dog.
If LAN Watch-Dog is enabled, the gateway restarts when a network failure is detected.
Enable Calls Cut Through
[CutThrough]
Enables users to receive incoming IP calls while the port is in an offhooked state.
Disable [0] = Disabled (default).
Enable [1] = Enabled.
If enabled, FXS gateways answer the call and “cut through” the voice channel, if there is
no other active call on that port, even if the port is in offhooked state.
When the call is terminated (by the remote party), the gateway plays a reorder tone for
‘TimeForReorderTone’ seconds and is then ready to answer the next incoming call,
without onhooking the phone.
The waiting call is automatically answered by the gateway when the current call is
terminated (EnableCallWaiting=1).
Note: This option is applicable only to FXS gateways.
MP-1xx SIP User’s Manual
62
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.2.2
5. Configuring the MP-1xx
Supplementary Services
Use this screen to configure parameters that are associated with supplementary services. For
detailed information on the supplementary services, refer to Section 8.4 on page 153.
To configure the supplementary services’ parameters, take these 4
steps:
1.
Open the ‘Supplementary Services’ screen (Protocol Management menu > Advanced
Parameters submenu > Supplementary Services option); the ‘Supplementary Services’
screen is displayed.
Figure 5-8: Supplementary Services Parameters Screen
2.
Configure the supplementary services parameters according to Table 5-6.
3.
Click the Submit button to save your changes, or click the Subscribe for MWI or UnSubscribe for MWI buttons to save your changes and to subscribe / unsubscribe to the MWI
server.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Version 4.4
63
March 2005
MP-1xx SIP
Table 5-6: Supplementary Services Parameters (continues on pages 64 to 65)
Parameter
Description
Enable Hold
[EnableHold]
No
[0] = Disable the Hold service (default).
Yes [1] = Enable the Hold service.
If the Hold service is enabled, a user can activate Hold (or Unhold) using the hook-flash.
On receiving a Hold request, the remote party is put on-hold and hears the hold tone.
Note: To use this service, the gateways at both ends must support this option.
Hold Format
[HoldFormat]
Determines the format of the hold request.
0.0.0.0
[0] = The connection IP address in SDP is 0.0.0.0 (default).
Send Only [1] = The last attribute of the SDP contains the following “a=sendonly”.
Enable Transfer
[EnableTransfer]
No
[0] = Disable the Call Transfer service (default).
Yes [1] = Enable the Call Transfer service (using REFER).
If the Transfer service is enabled, the user can activate Transfer using hook-flash
signaling. If this service is enabled, the remote party performs the call transfer.
Note 1: To use this service, the gateways at both ends must support this option.
Note 2: To use this service, set the parameter ‘Enable Hold’ to ‘Yes’.
Transfer Prefix
[xferPrefix]
Defined string that is added, as a prefix, to the transferred / forwarded called number,
when Refer / Redirect message is received.
Note 1: The number manipulation rules apply to the user part of the “REFER-TO /
Contact” URL before it is sent in the INVITE message.
Note 2: The ‘xferprefix’ parameter can be used to apply different manipulation rules to
differentiate the transferred / forwarded number from the original dialed number.
Enable Call Forward
[EnableForward]
No
[0] = Disable the Call Forward service (default).
Yes [1] = Enable Call Forward service (using REFER).
For FXS gateways a Call Forward table must be defined to use the Call Forward
service.
To define the Call Forward table, refer to Section 5.8.8.4 on page 96.
Note: To use this service, the gateways at both ends must support this option.
Enable Call Waiting
[EnableCallWaiting]
No
Yes
[0] = Disable the Call Waiting service (default).
[1] = Enable the Call Waiting service.
If enabled, when an FXS gateway receives a call on a busy endpoint, it responds with a
182 response (and not with a 486 busy). The gateway plays a call waiting indication
signal. When hook-flash is detected, the gateway switches to the waiting call.
The gateway that initiated the waiting call plays a Call Waiting Ringback tone to the
calling party after a 182 response is received.
Note 1: The gateway’s Call Progress Tones file must include a "call waiting Ringback”
tone (caller side) and a "call waiting” tone (called side, FXS only).
Note 2: The ‘Enable Hold’ parameter must be enabled on both the calling and the called
sides.
For information on the Call Waiting feature refer to Section 8.4.5 on page 155.
For information on the Call Progress Tones file refer to Section 7.1 on page 143.
Number of Call Waiting
Number of waiting indications that are played to the receiving side of the call (FXS only)
Indications
for Call Waiting.
[NumberOfWaitingIndication
The default value is 2.
s]
Time Between Call Waiting
Indications
[TimeBetweenWaitingIndica
tions]
Time before Waiting Indication
[TimeBeforeWaitingIndicatio
n]
[Waiting Beep Duration]
WaitingBeepDuration
MP-1xx SIP User’s Manual
Difference (in seconds) between call waiting indications (FXS only) for Call Waiting.
The default value is 10 seconds.
Defines the interval (in seconds) before a call waiting indication is played to the port that
is currently in a call (FXS only).
The valid range is 0 to 100. The default time is 0 seconds.
Duration (in msec) of waiting indications that are played to the receiving side of the call
(FXS only) for Call Waiting.
The default value is 300.
64
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-6: Supplementary Services Parameters (continues on pages 64 to 65)
Parameter
Description
Enable Caller ID
[EnableCallerID]
No
[0] = Disable the Caller ID service (default).
Yes [1] = Enable the Caller ID service.
If the Caller ID service is enabled, then, for FXS gateways, calling number and Display
text are sent to gateway port.
For FXO gateways, the Caller ID signal is detected and is sent to IP in SIP INVITE
message (as "Display" element).
For information on the Caller ID table refer to Section 5.8.8.3 on page 95.
To disable/enable caller I generation per port, refer to Section 5.8.8.5 on page 98.
Caller ID Type
[CallerIDType]
Defines one of the following standards for detection (FXO) and generation (FXS) of
Caller ID signals.
Bellcore
[0] (default).
ETSI
[1].
NTT
[2].
British
[4]
DTMF ETSI [16]
Denmark
[17]
India
[18]
Brazil
[19]
Note: The Caller ID signals are generated/detected between the first and the second
rings.
MWI Parameters
Enable MWI
[EnableMWI]
Enable MWI (message waiting indication).
Disable [0] = Disabled (default).
Enable [1] = MWI service is enabled.
This parameter is applicable only to FXS gateways.
Note: The MP-1xx only supports reception of MWI.
For detailed information on MWI, refer to Section 8.4.6 on page 156.
MWI Analog Lamp
[MWIAnalogLamp]
Disable [0] = Disable (default).
Enable [1] = Enable visual Message Waiting Indication, supplies line voltage of
approximately 100 VDC to activate the phone’s lamp.
This parameter is applicable only to FXS gateways.
MWI Display
[MWIDisplay]
Disable
Enable
[0] = MWI information isn’t sent to display (default).
[1] = MWI information is sent to display.
If enabled, the gateway generates an MWI FSK message that is displayed on the MWI
display.
This parameter is applicable only to FXS gateways.
Subscribe to MWI
[EnableMWISubscription]
Disable [0] = Disable MWI subscription (default).
Enable [1] = Enable subscription to MWI (to MWIServerIP address).
Note: Use the parameter ‘SubscriptionMode’ (described in Table 5-26 on page 101) to
determine whether the gateway subscribes separately per endpoint of for the entire
gateway.
MWI Server IP Address
[MWIServerIP]
MWI server IP address. If provided, the gateway subscribes to this IP address.
Can be configured as a numerical IP address or as a domain name. If not configured,
the Proxy IP address is used instead.
MWI Subscribe Expiration
Time
[MWIExpirationTime]
MWI subscription expiration time in seconds.
The default is 7200 seconds. The range is 10 to 72000.
MWI Subscribe Retry Time
[SubscribeRetryTime]
Subscription retry time in seconds.
The default is 120 seconds. The range is 10 to 7200.
Stutter Tone Duration
[StutterToneDuration]
Duration (in msec) of the played stutter dial tone that indicates waiting message(s).
The default is 2000 (2 seconds). The range is 1000 to 60000.
The Stutter tone is played (instead of a regular Dial tone) when a MWI is received. The
tone is composed of a ‘Confirmation tone’ that is played for ‘StutterToneDuration’
followed by a ‘Stutter tone’. Both tones are defined in the CPT file.
Note: This parameter is applicable only to FXS gateways.
For detailed information on Message Waiting Indication (MWI), refer to Section 8.4.6 on
page 156.
Version 4.4
65
March 2005
MP-1xx SIP
5.8.2.3
Keypad Features
The Keypad Features screen (applicable only to FXS gateways) enables you to activate /
deactivate the following features directly from the connected telephone’s keypad:
•
Call Forward (refer to Section 5.8.8.4 on page 96).
•
Caller ID Restriction (refer to Section 5.8.8.3 on page 95).
•
Hotline (refer to Section 5.8.8.2 on page 94).
To configure the keypad features, take these 4 steps:
1.
Open the ‘Keypad Features’ screen (Protocol Management menu > Advanced
Parameters submenu > Keypad Features option); the ‘Keypad Features’ screen is
displayed.
Figure 5-9: Keypad Features Screen
2.
Configure the Keypad Features according to Table 5-7.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Note:
MP-1xx SIP User’s Manual
The method used by the gateway to collect dialed numbers is identical to the
method used during a regular call (i.e., max digits, interdigit timeout, digit
map, etc.).
66
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-7: Keypad Features Parameters
Parameter
Description
Forward
Unconditional
[KeyCFUnCond]
Keypad sequence that activates the immediate forward option.
No Answer
[KeyCFNoAnswer]
Keypad sequence that activates the forward on no answer option.
On Busy
[KeyCFBusy]
Keypad sequence that activates the forward on busy option.
On Busy or No Answer
[KeyCFBusyOrNoAnswer]
Keypad sequence that activates the forward on ‘busy or no answer’ option.
Do Not Disturb
[KeyCFDoNotDisturb]
Keypad sequence that activates the Do Not Disturb option.
To activate the required forward method from the telephone:
• Dial the preconfigured sequence number on the keypad; a dial tone is heard.
• Dial the telephone number to which the call is forwarded (terminate the number with #); a confirmation tone is
heard.
Deactivate
[KeyCFDeact]
Keypad sequence that deactivates any of the forward options.
After the sequence is pressed a confirmation tone is heard.
Caller ID Restriction
Activate
[KeyCLIR]
Keypad sequence that activates the restricted Caller ID option.
After the sequence is pressed a confirmation tone is heard.
Deactivate
[KeyCLIRDeact]
Keypad sequence that deactivates the restricted Caller ID option.
After the sequence is pressed a confirmation tone is heard.
Hotline
Activate
[KeyHotLine]
Keypad sequence that activates the delayed hotline option.
To activate the delayed hotline option from the telephone:
• Dial the preconfigured sequence number on the keypad; a dial tone is heard.
• Dial the telephone number to which the phone automatically dials after a
configurable delay (terminate the number with #); a confirmation tone is heard.
Deactivate
[KeyHotLineDeact]
Keypad sequence that deactivates the delayed hotline option.
After the sequence is pressed a confirmation tone is heard.
Version 4.4
67
March 2005
MP-1xx SIP
5.8.3
Configuring the Number Manipulation Tables
The VoIP gateway provides four Number Manipulation tables for incoming and outgoing calls.
These tables are used to modify the destination and source telephone numbers so that the calls
can be routed correctly.
The Manipulation Tables are:
•
Destination Phone Number Manipulation Table for IP Tel calls
•
Destination Phone Number Manipulation Table for Tel IP call
•
Source Phone Number Manipulation Table for IP Tel calls
•
Source Phone Number Manipulation Table for Tel IP calls
Note:
Number manipulation can occur either before or after a routing decision is
made. For example, you can route a call to a specific hunt group according
to its original number, and then you can remove / add a prefix to that number
before it is routed. To control when number manipulation is done, set the IP
to Tel Routing Mode (described in Table 5-12) and the Tel to IP Routing
Mode (described in Table 5-11) parameters.
Possible uses for number manipulation can be as follows:
•
To strip/add dialing plan digits from/to the number. For example, a user could dial 9 in front
of each number in order to indicate an external line. This number (9) can be removed here
before the call is setup.
•
Allow / disallow Caller ID information to be sent according to destination / source prefixes.
For detailed information on Caller ID refer to Section 5.8.8.3 on page 95.
To configure the Number Manipulation tables, take these 5 steps:
1.
Open the Number Manipulation screen you want to configure (Protocol Management menu
> Manipulation Tables submenu); the relevant Manipulation table screen is displayed.
Figure 5-10 shows the ‘Source Phone Number Manipulation Table for Tel IP calls’.
Figure 5-10: Source Phone Number Manipulation Table for Tel IP calls
2.
In the ‘Table Index’ drop-down list, select the range of entries that you want to edit (up to 20
entries can be configured for Source Number Manipulation and 50 entries for Destination
Number Manipulation).
3.
Configure the Number Manipulation table according to Table 5-8.
MP-1xx SIP User’s Manual
68
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
4.
Click the Submit button to save your changes.
5.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-8: Number Manipulation Parameters
Parameter
Description
Destination Prefix
Each entry in the Destination Prefix fields represents a destination telephone number
prefix. An asterisk (*) represents any number.
Source Prefix
Each entry in the Source Prefix fields represents a source telephone number prefix.
An asterisk (*) represents any number.
Source IP
Each entry in the Source IP fields represents the source IP address of the call
(obtained from the Contact header in the Invite message).
This column only applies to the ‘Destination Phone Number Manipulation Table for
IP to Tel’.
Note: The source IP address can include the “x” wildcard to represent single digits.
For example: 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.
The manipulation rules are applied to any incoming call whose:
• Destination number prefix matches the prefix defined in the ‘Destination Number’ field.
• Source number prefix matches the prefix defined in the ‘Source Prefix’ field.
• Source IP address matches the IP address defined in the ‘Source IP’ field (if applicable).
Note that number manipulation can be performed using a combination of each of the above criteria, or using each
criterion independently.
Note: For available notations that represent multiple numbers refer to Section 5.8.3.1 on page 71.
Num of stripped digits
•
Prefix / Suffix to add
•
Number of digits to leave
Enter the number of digits that you want to leave from the right.
Enter the number of digits that you want to remove from the left of the telephone
number prefix. For example, if you enter 3 and the phone number is 5551234, the
new phone number is 1234.
• Enter the number of digits (in brackets) that you want to remove from the right of
the telephone number prefix.
Note: A combination of the two options is allowed (e.g., 2(3)).
Prefix - Enter the number / string you want to add to the front of the phone
number. For example, if you enter 9 and the phone number is 1234, the new
number is 91234.
• Suffix - Enter the number / string (in brackets) you want to add to the end of the
phone number. For example, if you enter (00) and the phone number is 1234, the
new number is 123400.
Note: You can enter a prefix and a suffix in the same field (e.g., 9(00)).
Note: The manipulation rules are executed in the following order:
1.
Num of stripped digits
2.
Number of digits to leave
3.
Prefix / suffix to add
Figure 5-10 on the previous page exemplifies the use of these manipulation rules in the ‘Source Phone Number
Manipulation Table for Tel IP Calls’:
• When destination number equals 035000 and source number equals 20155, the source number is changed to
97220155.
• When source number equals 1001876, it is changed to 587623.
• Source number 1234510012001 is changed to 20018.
• Source number 3122 is changed to 2312.
Presentation
Version 4.4
Select ‘Allowed’ to send Caller ID information when a call is made using these
destination / source prefixes.
Select ‘Restricted’ if you want to restrict Caller ID information for these prefixes.
When set to ‘Not Configured’, the privacy is determined according to the Caller ID
table (refer to Section 5.8.8.3 on page 95).
Note: If ‘Presentation’ is set to ‘Restricted’ and ‘Asserted Identity Mode’ is set to ‘PAsserted’, the From header in Invite message is: From: “anonymous” <sip:
anonymous@anonymous.invalid> and “privacy: id” header is included in the Invite
message.
69
March 2005
MP-1xx SIP
Table 5-9: Number Manipulation ini File Parameters (continues on pages 70 to 71)
Parameter
Description
NumberMapTel2IP
Manipulates the destination number for Tel to IP calls.
NumberMapTel2IP = a,b,c,d,e,f,g
a = Destination number prefix
b = Number of stripped digits from the left, or (if brackets are used) from the right. A
combination of both options is allowed.
c = String to add as prefix, or (if brackets are used) as suffix. A combination of both
options is allowed.
d = Number of remaining digits from the right
e = Number Plan used in RPID header
f = Number Type used in RPID header
g = Source number prefix
The ‘b’ to ‘f’ manipulation rules are applied if the called and calling numbers match
the
‘a’ and ‘g’ conditions.
The manipulation rules are executed in the following order: ‘b’, ‘d’ and ‘c’.
Parameters can be skipped by using the sign "$$", for example:
NumberMapTel2IP=01,2,972,$$,0,0,$$
NumberMaPTel2IP=03,(2),667,$$,0,0,22
Note: Number Plan & Type can optionally be used in Remote Party ID (RPID)
header by using the ‘EnableRPIHeader’ and ‘AddTON2RPI’ parameters.
NumberMapIP2Tel
Manipulate the destination number for IP to Tel calls.
NumberMapIP2Tel = a,b,c,d,e,f,g,h,i
a = Destination number prefix.
b = Number of stripped digits from the left, or (if brackets are used) from the right. A
combination of both options is allowed.
c = String to add as prefix, or (if brackets are used) as suffix. A combination of both
options is allowed.
d = Number of remaining digits from the right.
e = Not applicable, set to $$.
f = Not applicable, set to $$.
g = Source number prefix.
h = Not applicable, set to $$.
i = Source IP address (obtained from the Contact header in the Invite message).
The ‘b’ to ‘d’ manipulation rules are applied if the called and calling numbers match
the ‘a’, ‘g’ and ‘i’ conditions.
The manipulation rules are executed in the following order: ‘b’, ‘d’ and ‘c’.
Parameters can be skipped by using the sign "$$", for example:
NumberMapIP2Tel =01,2,972,$$,$$,$$,034,$$,10.13.77.8
NumberMapIP2Tel =03,(2),667,$$,$$,$$,22
Note: The Source IP address can include the “x” wildcard to represent single digits.
For example: 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.
MP-1xx SIP User’s Manual
70
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Parameter
Description
SourceNumberMapTel2IP
SourceNumberMapTel2IP = a,b,c,d,e,f,g,h
a = Source number prefix
b = Number of stripped digits from the left, or (if in brackets are used) from right. A
combination of both options is allowed.
c = String to add as prefix, or (if in brackets are used) as suffix. A combination of
both options is allowed.
d = Number of remaining digits from the right
e = Number Plan used in RPID header
f = Number Type used in RPID header
g = Destination number prefix
h = Calling number presentation (0 to allow presentation, 1 to restrict presentation)
The ‘b’ to ‘f’ and ‘h’ manipulation rules are applied if the called and calling numbers
match the ‘a’ and ‘g’ conditions.
The manipulation rules are executed in the following order: ‘b’, ‘d’ and ‘c’.
Parameters can be skipped by using the sign "$$", for example:
SourceNumberMapTel2IP=01,2,972,$$,0,0,$$,1
SourceNumberMapTel2IP=03,(2),667,$$,0,0,22
Note 1: ‘Presentation’ is set to ‘Restricted’ only if ‘Asserted Identity Mode’ is set to
‘P-Asserted’.
Note 2: Number Plan & Type can optionally be used in Remote Party ID (RPID)
header by using the ‘EnableRPIHeader’ and ‘AddTON2RPI’ parameters.
SourceNumberMapIP2Tel
Manipulate the destination number for IP to Tel calls.
NumberMapIP2Tel = a,b,c,d,e,f,g
a = Source number prefix
b = Number of stripped digits from the left, or (if brackets are used) from the right. A
combination of both options is allowed.
c = String to add as prefix, or (if brackets are used) as suffix. A combination of both
options is allowed.
d = Number of remaining digits from the right
e = Not in use, should be set to $$
f = Not in use, should be set to $$
g = Destination number prefix
The ‘b’ to ‘d’ manipulation rules are applied if the called and calling numbers match
the ‘a’ and ‘g’ conditions.
The manipulation rules are executed in the following order: ‘b’, ‘d’ and ‘c’.
Parameters can be skipped by using the sign "$$", for example:
NumberMapIP2Tel =01,2,972,$$,$$,$$,034
NumberMapIP2Tel =03,(2),667,$$,$$,$$,22
5.8.3.1
Dialing Plan Notation
The dialing plan notation applies, in addition to the four Manipulation tables, also to Tel IP
Routing table and to IP Hunt Group Routing table.
When entering a number in the destination and source ‘Prefix’ columns, you can create an entry
that represents multiple numbers using the following notation:
•
[n-m] represents a range of numbers
•
[n,m] represents multiple numbers. Note that this notation only supports single digit numbers.
•
x represents any single digit
•
# (that terminates the number) represents the end of a number
•
A single asterisk (*) represents any number
For example:
Version 4.4
71
March 2005
MP-1xx SIP
•
[5551200-5551300]# represents all numbers from 5551200 to 5551300
•
[2,3,4] represents all numbers that start with the numbers 2, 3 and 4
•
54324 represents any number that starts with 54324
•
54324xx# represents a 7 digit number that starts with 54324
•
123[100-200]# represents all numbers from 123100 to 123200.
The VoIP gateway matches the rules starting at the top of the table. For this reason, enter more
specific rules above more generic rules. For example, if you enter 551 in entry 1 and 55 in entry
2, the VoIP gateway applies rule 1 to numbers that starts with 551 and applies rule 2 to numbers
that start with 550, 552, 553, 554, 555, 556, 557, 558 and 559. However if you enter 55 in entry 1
and 551 in entry 2, the VoIP gateway applies rule 1 to all numbers that start with 55 including
numbers that start with 551.
MP-1xx SIP User’s Manual
72
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.4
5. Configuring the MP-1xx
Configuring the Routing Tables
Use this submenu to configure the gateway’s IP Tel and Tel IP routing tables and their
associated parameters.
5.8.4.1
General Parameters
Use this screen to configure the gateway’s IP Tel and Tel IP routing parameters.
To configure the general parameters under Routing Tables, take these 4
steps:
1.
Open the ‘General Parameters’ screen (Protocol Management menu > Routing Tables
submenu > General option); the ‘General Parameters’ screen is displayed.
Figure 5-11: Routing Tables, General Parameters Screen
2.
Configure the general parameters under ‘Routing Tables’ according to Table 5-10.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-10: Routing Tables, General Parameters (continues on pages 73 to 74)
Parameter
Description
Add Hunt Group ID as Prefix
[AddTrunkGroupAsPrefix]
No
[0] = Don’t add hunt group ID as prefix (default).
Yes [1] = Add hunt group ID as prefix to called number.
If enabled, then the hunt group ID is added as a prefix to the destination phone number
for Tel IP calls.
Note 1: This option can be used to define various routing rules.
Note 2: To use this feature you must configure the hunt group IDs.
Add Port Number as Prefix
[AddPortAsPrefix]
Version 4.4
No
[0] = Disable the add port as prefix service (default).
Yes [1] = Enable the add port as prefix service.
If enabled, then the gateway’s port number (single digit in the range 1 to 8 in MP-10x,
two digits in the range 01 to 24 in MP-124) is added as a prefix to the destination phone
number for Tel IP calls.
Note: This option can be used to define various routing rules.
73
March 2005
MP-1xx SIP
Table 5-10: Routing Tables, General Parameters (continues on pages 73 to 74)
Parameter
Description
IP to Tel Remove Routing
Table Prefix
[RemovePrefix]
No
[0] = Don't remove prefix (default)
Yes [1] = Remove the prefix (defined in the IP to Hunt Group Routing table) from a
telephone number for an IP Tel call, before forwarding it to Tel.
For example:
To route an incoming IP Tel Call with destination number 21100, the IP to Hunt Group
Routing table is scanned for a matching prefix. If such prefix is found, 21 for instance,
then before the call is routed to the corresponding hunt group the prefix (21) is removed
from the original number, so that only 100 is left.
Note 1: Applicable only if number manipulation is performed after call routing for IP Tel
calls (refer to ‘IP to Tel Routing Mode’ parameter).
Note 2: Similar operation (of removing the prefix) is also achieved by using the usual
number manipulation rules.
Enable Alt Routing Tel to IP
[AltRoutingTel2IPEnable]
No
[0] = Disable the Alternative Routing feature (default).
Yes
[1] = Enable the Alternative Routing feature.
Status Only [2] = The Alternative Routing feature is disabled. A read only information
on the quality of service of the destination IP addresses is provided.
For information on the Alternative Routing feature refer to Section 8.3 on page 152.
Alt Routing Tel to IP Mode
[AltRoutingTel2IPMode]
None [0] = Alternative routing is not used.
Conn [1] = Alternative routing is performed if ping to initial destination failed.
QoS [2] = Alternative routing is performed if poor quality of service was detected.
Both [3] = Alternative routing is performed if, either ping to initial destination failed, or
poor quality of service was detected, or DNS host name is not resolved (default).
Note: QoS (Quality of Service) is quantified according to delay and packet loss,
calculated according to previous calls. Qos statistics are reset if no new data is received
for two minutes.
For information on the Alternative Routing feature refer to 8.3 on page 152.
Max Allowed Packet Loss for
Packet loss percentage at which the IP connection is considered a failure.
Alt Routing [%]
The range is 1% to 20%. The default value is 20%.
[IPConnQoSMaxAllowedPL]
Max Allowed Delay for Alt
Routing [msec]
Transmission delay (in msec) at which the IP connection is considered a failure.
[IPConnQoSMaxAllowedDel The range is 100 to 1000. The default value is 250 msec.
ay]
MP-1xx SIP User’s Manual
74
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.4.2
5. Configuring the MP-1xx
Tel to IP Routing Table
The Tel to IP Routing Table is used to route incoming Tel calls to IP addresses. This routing table
associates a called / calling telephone number’s prefixes with a destination IP address or with an
FQDN (Fully Qualified Domain Name). When a call is routed through the VoIP gateway (Proxy
isn’t used), the called and calling numbers are compared to the list of prefixes on the IP Routing
Table (up to 50 prefixes can be configured); Calls that match these prefixes are sent to the
corresponding IP address. If the number dialed does not match these prefixes, the call is not
made.
When using a Proxy server, you do not need to configure the Tel to IP Routing Table. However, if
you want to use fallback routing when communication with Proxy servers is lost, or to use the
‘Filter Calls to IP’ and ‘IP Security’ features, or to obtain different SIP URI host names (per called
number) or to assign IP profiles, you need to configure the IP Routing Table.
Note that for the Tel to IP Routing table to take precedence over a Proxy for routing calls, set the
parameter ‘PreferRouteTable’ to 1. The gateway checks the 'Destination IP Address' field in the
'Tel to IP Routing' table for a match with the outgoing call. Only if a match is not found, a Proxy is
used.
Possible uses for Tel to IP Routing can be as follows:
•
Can fallback to internal routing table if there is no communication with the Proxy servers.
•
Call Restriction – (when Proxy isn’t used), reject all outgoing Tel IP calls that are
associated with the destination IP address: 0.0.0.0.
•
IP Security – When the IP Security feature is enabled (SecureCallFromIP = 1), the VoIP
gateway accepts only those IP Tel calls with a source IP address identical to one of the IP
addresses entered in the Tel to IP Routing Table.
•
Filter Calls to IP – When a Proxy is used, the gateway checks the Tel IP routing table
before a telephone number is routed to the Proxy. If the number is not allowed (number isn’t
listed or a Call Restriction routing rule was applied), the call is released.
•
Always Use Routing Table – When this feature is enabled (AlwaysUseRouteTable = 1), even
if a Proxy server is used, the SIP URI host name in the sent INVITE message is obtained
from this table. Using this feature users are able to assign a different SIP URI host name for
different called and/or calling numbers.
•
Assign Profiles to destination address (also when a Proxy is used).
•
Alternative Routing – (When Proxy isn’t used) an alternative IP destination for telephone
number prefixes is available. To associate an alternative IP address to called telephone
number prefix, assign it with an additional entry (with a different IP address), or use an
FQDN that resolves to two IP addresses. Call is sent to the alternative destination when one
of the following occurs:
No ping to the initial destination is available, or when poor QoS (delay or packet loss,
calculated according to previous calls) is detected, or when a DNS host name is not
resolved. For detailed information on Alternative Routing, refer to Section 8.3 on page
152.
When a release reason that is defined in the ‘Reasons for Alternative Tel to IP Routing’
table is received. For detailed information on the ‘Reasons for Alternative Routing
Tables’ refer to Section 5.8.4.5 on page 81.
Alternative routing (using this table) is commonly implemented when there is no response to
an Invite message (after Invite retransmissions). The gateway then issues an internal 408
‘No Response’ implicit release reason. If this reason is included in the ‘Reasons for
Alternative Routing’ table, the gateway immediately initiates a call to the redundant
destination using the next matched entry in the ‘Tel to IP Routing’ table. Note that if a domain
name in this table is resolved to two IP addresses, the timeout for Invite retransmissions can
be reduced by using the parameter ‘Number of RTX Before Hotswap’.
Version 4.4
75
March 2005
MP-1xx SIP
Tip:
Tel to IP routing can be performed either before or after applying the number
manipulation rules. To control when number manipulation is done, set the
Tel to IP Routing Mode parameter (described in Table 5-11).
To configure the Tel to IP Routing table, take these 6 steps:
1.
Open the ‘Tel to IP Routing’ screen (Protocol Management menu > Routing Tables
submenu > Tel to IP Routing option); the ‘Tel to IP Routing’ screen is displayed (shown in
Figure 5-12).
2.
In the ‘Tel to IP Routing Mode’ field, select the Tel to IP routing mode (refer to Table 5-11).
3.
In the ‘Routing Index’ drop-down list, select the range of entries that you want to edit.
4.
Configure the Tel to IP Routing table according to Table 5-11.
5.
Click the Submit button to save your changes.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Figure 5-12: Tel to IP Routing Table Screen
Table 5-11: Tel to IP Routing Table
Parameter
Description
Tel to IP Routing Mode
[RouteModeTel2IP]
Route calls before manipulation [0] = Tel IP calls are routed before the number
manipulation rules are applied (default).
Route calls after manipulation [1] = Tel IP calls are routed after the number
manipulation rules are applied.
Note: Not applicable if Proxy routing is used.
Destination Phone Prefix
Each entry in the Destination Phone Prefix fields represents a called telephone number
prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers.
Source Phone Prefix
Each entry in the Source Phone Prefix fields represents a calling telephone number
prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers.
Any telephone number whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field and
its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field, is sent to the IP address
entered in the ‘IP Address’ field.
Note that Tel to IP routing can be performed according to a combination of source and destination phone prefixes, or
using each independently.
Note 1: An additional entry of the same prefixes can be assigned to enable alternative routing.
Note 2: For available notations that represent multiple numbers refer to Section 5.8.3.1 on page 71.
MP-1xx SIP User’s Manual
76
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-11: Tel to IP Routing Table
Parameter
Description
Destination IP Address
In each of the IP Address fields, enter the IP address that is assigned to these prefixes.
Domain names, such as domain.com, can be used instead of IP addresses.
To discard outgoing IP calls, enter 0.0.0.0 in this field.
Note: When using domain names, you must enter a DNS server IP address, or
alternatively define these names in the ‘Internal DNS Table’.
Profile ID
Enter the number of the IP profile that is assigned to the destination IP address defined in
the ‘Destination IP Address’ field.
Status
A read only field representing the quality of service of the destination IP address.
N/A = Alternative Routing feature is disabled.
OK = IP route is available
Ping Error = No ping to IP destination, route is not available
QoS Low = Bad QoS of IP destination, route is not available
DNS Error = No DNS resolution (only when domain name is used instead of an IP
address).
Parameter Name in ini File Parameter Format
Prefix
Prefix = <Destination Phone Prefix>,<IP Address>,<Source Phone Prefix>,<Profile ID>
For example:
Prefix = 20,10.2.10.2,202,1
Prefix = 10[340-451]xxx#,10.2.10.6,*,1
Prefix = *,gateway.domain.com,*
Note 1: <destination / source phone prefix> can be single number or a range of numbers.
For available notations refer to Section 5.8.3.1 on page 71.
Note 2: This parameter can appear up to 50 times.
Note 3: Parameters can be skipped by using the sign "$$", for example:
Prefix = $$,10.2.10.2,202,1
Version 4.4
77
March 2005
MP-1xx SIP
5.8.4.3
IP to Hunt Group Routing
The IP to Hunt Group Routing Table is used to route incoming IP calls to groups of channels
called hunt groups. Calls are assigned to hunt groups according to any combination of the
following three options (or using each independently):
•
Destination phone prefix
•
Source phone prefix
•
Source IP address
The call is then sent to the VoIP gateway channels assigned to that hunt group. The specific
channel, within a hunt group, that is assigned to accept the call is determined according to the
hunt group’s channel selection mode which is defined in the Hunt Group Settings table (Section
5.8.7 on page 91) or according to the global parameter ‘ChannelSelectMode’ (refer to Table 5-5
on page 59). Hunt groups can be used on both FXO and FXS gateways; however, usually they
are used with FXO gateways.
Note: When a release reason that is defined in the ‘Reasons for Alternative IP to Tel Routing’
table is received for a specific IP Tel call, an alternative hunt group for that call is available. To
associate an alternative hunt group to an incoming IP call, assign it with an additional entry in the
‘IP to Hunt Group Routing’ table (repeat the same routing rules with a different hunt group ID).
For detailed information on the ‘Reasons for Alternative Routing Tables’ refer to Section 5.8.4.5
on page 81.
To use hunt groups you must also do the following.
•
You must assign a hunt group ID to the VoIP gateway channels on the Endpoint Phone
Number screen. For information on how to assign a hunt group ID to a channel, refer to
Section 5.8.6 on page 89.
•
You can configure the Hunt Group Settings table to determine the method in which new calls
are assigned to channels within the hunt groups (a different method for each hunt group can
be configured). For information on how to enable this option, refer to Section 5.8.7 on page
91. If a Channel Select Mode for a specific hunt group isn’t specified, then the global
"Channel Select Mode" parameter (defined in ‘General Parameters’ screen under ‘Advanced
Parameters’) applies.
To configure the IP to Hunt Group Routing table, take these 6 steps:
1.
Open the ‘IP to Hunt Group Routing’ screen (Protocol Management menu > Routing
Tables submenu > IP to Hunt Group Routing option); the ‘IP to Hunt Group Routing’ table
screen is displayed (shown in Figure 5-13).
Figure 5-13: IP to Hunt Group Routing Table Screen
MP-1xx SIP User’s Manual
78
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
2.
In the ‘IP to Tel Routing Mode’ field, select the IP to Tel routing mode (refer to Table 5-12).
3.
In the ‘Routing Index’ drop-down list, select the range of entries that you want to edit (up to
24 entries can be configured).
4.
Configure the IP to Hunt Group Routing table according to Table 5-12.
5.
Click the Submit button to save your changes.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-12: IP to Hunt Group Routing Table
Parameter
Description
IP to Tel Routing Mode
[RouteModeIP2Tel]
Route calls before manipulation [0] = IP Tel calls are routed before the number
manipulation rules are applied (default).
Route calls after manipulation [1] = IP Tel calls are routed after the number
manipulation rules are applied.
Destination Phone Prefix
Each entry in the Destination Phone Prefix fields represents a called telephone number
prefix. The prefix can be 1 to 49 digits long. An asterisk (*) represents all numbers.
Source Phone Prefix
Each entry in the Source Phone Prefix fields represents a calling telephone number
prefix. The prefix can be 1 to 49 digits long. An asterisk (*) represents all numbers.
Source IP Address
Each entry in the Source IP Address fields represents the source IP address of an
IP Tel call (obtained from the Contact header in the Invite message).
Note: The source IP address can include the “x” wildcard to represent single digits. For
example: 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.
Any SIP incoming call whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field and
its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field and its source IP address
matches the address defined in the ‘Source IP Address’ field, is assigned to the hunt group entered in the field to the
right of these fields.
Note that IP to hunt group routing can be performed according to any combination of source / destination phone
prefixes and source IP address, or using each independently.
Note: For available notations that represent multiple numbers (used in the prefix columns), refer to Section 5.8.3.1 on
page 71.
Hunt Group ID
In each of the Hunt Group ID fields, enter the hunt group ID to which calls that match
these prefixes are assigned.
Profile ID
Enter the number of the IP profile that is assigned to the routing rule.
Parameter Name in ini
File
Parameter Format
PSTNPrefix
PSTNPrefix = a,b,c,d,e
a = Destination Number Prefix
b = Hunt Group ID
c = Source Number Prefix
d = Source IP address (obtained from the Contact header in the Invite message)
e = IP Profile ID
Selection of hunt groups (for IP to Tel calls) is according to destination number, source
number and source IP address.
Note 1: To support the ‘in call alternative routing’ feature, Users can use two entries that
support the same call, but assigned it with a different hunt groups. The second entree
functions as an alternative selection if the first rule fails as a result of one of the release
reasons listed in the AltRouteCauseIP2Tel table.
Note 2: An optional IP ProfileID (1 to 5) can be applied to each routing rule.
Note 3: The Source IP Address can include the “x” wildcard to represent single digits.
For example: 10.8.8.xx represents all IP addresses between 10.8.8.10 to 10.8.8.99.
Note 4: For available notations that represent multiple numbers refer to Section 5.8.3.1
on page 71.
Note 5: This parameter can appear up to 24 times.
Version 4.4
79
March 2005
MP-1xx SIP
5.8.4.4
Internal DNS Table
The internal DNS table, similar to a DNS resolution, translates hostnames into IP addresses. This
table is used when hostname translation is required (e.g., ‘Tel to IP Routing’ table, etc.). Two
different IP addresses can be assigned to the same hostname. If the hostname isn’t found in this
table, the gateway communicates with an external DNS server.
Assigning two IP addresses to hostname can be used for alternative routing (using the ‘Tel to IP
Routing’ table).
To configure the internal DNS table, take these 7 steps:
1.
Open the ‘Internal DNS Table’ screen (Protocol Management menu > Routing Tables
submenu > Internal DNS Table option); the ‘Internal DNS Table’ screen is displayed.
Figure 5-14: Internal DNS Table Screen
2.
In the ‘DNS Name’ field, enter the hostname to be translated. You can enter a string up to 31
characters long.
3.
In the ‘First IP Address’ field, enter the first IP address that the hostname is translated to.
4.
In the ‘Second IP Address’ field, enter the second IP address that the hostname is translated
to.
5.
Repeat steps 2 to 4, for each Internal DNS Table entry.
6.
Click the Submit button to save your changes.
7.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-13: Internal DNS ini File Parameter
Parameter Name in ini File
Parameter Format
DNS2IP
DNS2IP = <Hostname>, <first IP address>, <second IP address>
For example:
DNS2IP = Domainname.com, 10.8.21.4, 10.13.2.95
Note: This parameter can appear up to 10 times.
MP-1xx SIP User’s Manual
80
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.4.5
5. Configuring the MP-1xx
Reasons for Alternative Routing
The Reasons for Alternative Routing screen includes two tables (Tel IP and IP Tel). Each table
enables you to define up to 4 different release reasons. If a call is released as a result of one of
these reasons, the gateway tries to find an alternative route to that call. The release reason for
IP Tel calls is provided in Q.931 notation. The release reason for Tel IP calls is provided in SIP
4xx, 5xx and 6xx response codes. For Tel IP calls an alternative IP address, for IP Tel calls an
alternative hunt group.
Refer to ‘Tel to IP Routing’ on page 75 for information on defining an alternative IP address. Refer
to the ‘IP to Hunt Group Routing’ on page 78 for information on defining an alternative hunt group.
You can use this table for example:
For Tel IP calls, when there is no response to an Invite message (after Invite retransmissions),
and the gateway then issues an internal 408 ‘No Response’ implicit release reason.
For IP Tel calls, when the destination is busy, and release reason #17 is issued or for other call
releases that issue the default release reason (#3). Refer to ‘DefaultReleaseCause’ in Table 5-5.
Note: The reasons for alternative routing option for Tel IP calls only applies when Proxy isn’t
used.
To configure the reasons for alternative routing, take these 5 steps:
1.
Open the ‘Reasons for Alternative Routing’ screen (Protocol Management menu > Routing
Tables submenu > Reasons for Alternative Routing option); the ‘Reasons for Alternative
Routing’ screen is displayed.
Figure 5-15: Reasons for Alternative Routing Screen
2.
In the ‘IP to Tel Reasons’ table, from the drop-down list select up to 4 different call failure
reasons that invoke an alternative IP to Tel routing.
3.
In the ‘Tel to IP Reasons’ table, from the drop-down list select up to 4 different call failure
reasons that invoke an alternative Tel to IP routing.
4.
Click the Submit button to save your changes.
5.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Version 4.4
81
March 2005
MP-1xx SIP
Table 5-14: Reasons for Alternative Routing ini File Parameter
Parameter Name in ini File
Parameter Format
AltRouteCauseTel2IP
AltRouteCauseTel2IP = <SIP Call failure reason from IP>
For example:
AltRouteCauseTel2IP = 408
AltRouteCauseTel2IP = 486
(Response timeout).
(User is busy).
Note: This parameter can appear up to 4 times.
AltRouteCauseIP2Tel
AltRouteCauseIP2Tel = <Call failure reason from Tel>
For example:
AltRouteCauseIP2Tel = 3 (No route to destination).
AltRouteCauseIP2Tel = 17 (Busy here).
Note: This parameter can appear up to 4 times.
MP-1xx SIP User’s Manual
82
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.5
5. Configuring the MP-1xx
Configuring the Profile Definitions
Utilizing the Profiles feature, the MP-1xx provides high-level adaptation when connected to a
variety of equipment (from both Tel and IP sides) and protocols, each of which require a different
system behavior. Using Profiles, users can assign different Profiles (behavior) on a per-call basis,
using the Tel to IP and IP to Hunt Group Routing tables, or associate different Profiles to the
gateway’s endpoint(s). The Profiles contain parameters such as Coders, T.38 Relay, Voice and
DTMF Gains, Silence Suppression, Echo Canceler, RTP DiffServ, Current Disconnect and more.
The Profiles feature allows users to tune these parameters or turn them on or off, per source or
destination routing and/or the specific gateway or its ports. For example, specific ports can be
designated to have a profile which always uses G.711.
Each call can be associated with one or two Profiles, Tel Profile and (or) IP Profile. If both IP and
Tel profiles apply to the same call, the coders and other common parameters of the preferred
Profile (determined by the Preference option) are applied to that call. If the Preference of the Tel
and IP Profiles is identical, the Tel Profile parameters are applied.
Note:
5.8.5.1
The default values of the parameters in the Tel and IP Profiles are identical
to the Web/ini file parameter values. If a value of a parameter is changed in
the Web/ini file, it is automatically updated in the Profiles correspondingly.
After any parameter in the Profile is modified by the user, modifications to
parameters in the Web/ini file no longer impact that Profile.
Coder Group Settings
Use the Coders Group Settings screen to define up to four different coder groups. These coder
groups are used in the Tel and IP Profile Settings screens to assign different coders to Profiles.
To configure the coder group settings, take these 8 steps:
1.
Open the ‘Coder Group Settings’ screen (Protocol Management menu > Profile
Definitions submenu > Coder Group Settings option); the ‘Coder Group Settings’ screen is
displayed.
Figure 5-16: Coder Group Settings Screen
2.
In the ‘Coder Group ID’ drop-down list, select the coder group you want to edit (up to four
coder groups can be configured).
3.
From the coder drop-down list, select the coder you want to use. For the full list of available
coders and their corresponding ptimes refer to Table 5-15.
Note: Each coder can appear only once.
4.
From the drop-down list to the right of the coder list, select the size of the Voice Packet
(ptime) used with this coder in milliseconds. Selecting the size of the packet determines how
Version 4.4
83
March 2005
MP-1xx SIP
many coder payloads are combined into one RTP (voice) packet.
Note 1: The ptime packetization period depends on the selected coder name.
Note 2: If not specified, the ptime gets a default value.
Note 3: The ptime specifies the maximum packetization time the gateway can receive.
5.
Repeat steps 3 and 4 for the second to fifth coders (optional).
6.
Repeat steps 2 to 5 for the second to forth coder groups (optional).
7.
Click the Submit button to save your changes.
8.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Note:
In the current version, only the ptime of the first coder is sent in the SDP
section of the Invite message.
Table 5-15: ini File Coder Group Parameters
Parameter
Description
CoderName_ID
Coder list for Profiles (up to five coders in each group).
The CoderName_ID parameter (ID from 1 to 4) provides groups of coders that can be
associated with IP or Tel profiles.
You can select the following coders:
g711Alaw64k
– G.711 A-law.
g711Ulaw64k
– G.711 µ-law.
g7231
– G.723.1 6.3 kbps (default).
g7231r53
– G.723.1 5.3 kbps.
g726
– G.726 ADPCM 32 kbps (Payload Type = 35).
g729
– G.729A.
The RTP packetization period (ptime, in msec) depends on the selected Coder name,
and can have the following values:
g711 family
g729
g723 family
G.726 family
– 10, 20, 30, 40, 50, 60, 80, 100, 120 (default=20).
– 10, 20, 30, 40, 50, 60, 80, 100, 120 (default=20).
– 30, 60, 90, 120, 150 (default = 30).
– 10, 20, 30, 40, 50, 60, 80, 100, 120 (default=20)
Note: G.729B is supported if the coder G.729 is selected and
‘EnableSilenceCompression’ equals 1 or 2.
ini file note 1: This parameter (CoderName_ID) can appear up to 20 times (five coders
in four coder groups).
ini file note 2: The coder name is case-sensitive.
ini file note 3: Enter in the format: Coder,ptime.
For example, the following three coders belong to coder group with ID=1:
CoderName_1 = g711Alaw64k,20
CoderName_1 = g711Ulaw64k,40
CoderName_1 = g7231,90
MP-1xx SIP User’s Manual
84
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.5.2
5. Configuring the MP-1xx
Tel Profile Settings
Use the Tel Profile Settings screen to define up to four different Tel Profiles. These Profiles are
used in the ‘Endpoint Phone Number’ table to associate different Profiles to gateway’s endpoints,
thereby applying different behavior to different MP-1xx ports.
To configure the Tel Profile settings, take these 9 steps:
1.
Open the ‘Tel Profile Settings’ screen (Protocol Management menu > Profile Definitions
submenu > Tel Profile Settings option); the ‘Tel Profile Settings’ screen is displayed.
Figure 5-17: Tel Profile Settings Screen
2.
In the ‘Profile ID’ drop-down list, select the Tel Profile you want to edit (up to four Tel Profiles
can be configured).
3.
In the ‘Profile Name’ field, enter a name that enables you to identify the Profile intuitively and
easily.
4.
In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile.
The preference option is used to determine the priority of the Profile. If both IP and Tel
profiles apply to the same call, the coders and other common parameters of the preferred
Profile are applied to that call. If the Preference of the Tel and IP Profiles is identical, the Tel
Profile parameters are applied.
Note: If the coder lists of both IP and Tel Profiles apply to the same call, an intersection of
the coders is performed (i.e., only common coders remain). The order of the coders is
determined by the preference.
Version 4.4
85
March 2005
MP-1xx SIP
5.
Configure the Profile’s parameters according to your requirements. For detailed information
on each parameter refer to the description of the screen in which it is configured as an
individual parameter.
6.
In the ‘Coder Group’ drop-down list, select the coder group you want to assign to that Profile.
You can select the gateway’s default coders (refer to Section 5.8.1.3 on page 53) or one of
the coder groups you defined in the Coder Group Settings screen (refer to Section 5.8.5.1 on
page 83).
7.
Repeat steps 2 to 6 for the second to fifth Tel Profiles (optional).
8.
Click the Submit button to save your changes.
9.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-16: ini File Tel Profile Settings
Parameter
Description
TelProfile_ID
TelProfile_<Profile ID> =
<Profile Name>,<Preference>,<Coder Group ID>,<IsFaxUsed *>,<DJBufMinDelay *>,
<DJBufOptFactor *>,<IPDiffServ *>,<ControlIPDiffServ*>,<DTMFVolume>,<InputGain>,
<VoiceVolume>,<EnableReversePolarity>,<EnableCurrentDisconnect>,
<EnableDigitDelivery>, <ECE>
For example:
TelProfile_1 = FaxProfile,1,2,0,10,5,22,33,2,22,34,1,0,1,1
TelProfile_2 = ModemProfile,0,10,13,$$,$$,$$,$$,$$,0,$$,0,0,1,1
$$ = Not configured, the default value of the parameter is used.
(*) = Common parameter used in both IP and Tel profiles.
Note: This parameter can appear up to 4 times.
MP-1xx SIP User’s Manual
86
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.5.3
5. Configuring the MP-1xx
IP Profile Settings
Use the IP Profile Settings screen to define up to four different IP Profiles. These Profiles are
used in the Tel to IP and IP to Hunt Group Routing tables to associate different Profiles to routing
rules. IP Profiles can also be used when working with Proxy server (set ‘AlwaysUseRouteTable’
to 1).
To configure the IP Profile settings, take these 9 steps:
1.
Open the ‘IP Profile Settings’ screen (Protocol Management menu > Profile Definitions
submenu > IP Profile Settings option); the ‘IP Profile Settings’ screen is displayed.
Figure 5-18: IP Profile Settings Screen
2.
In the ‘Profile ID’ drop-down list, select the IP Profile you want to edit (up to four IP Profiles
can be configured).
3.
In the ‘Profile Name’ field, enter a name that enables you to identify the Profile intuitively and
easily.
4.
In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile.
The preference option is used to determine the priority of the Profile. If both IP and Tel
profiles apply to the same call, the coders and other common parameters of the preferred
Profile are applied to that call. If the Preference of the Tel and IP Profiles is identical, the Tel
Profile parameters are applied.
Note: If the coder lists of both IP and Tel Profiles apply to the same call, an intersection of
the coders is performed (i.e., only common coders remain). The order of the coders is
determined by the preference.
5.
Configure the Profile’s parameters according to your requirements. For detailed information
on each parameter refer to the description of the screen in which it is configured as an
individual parameter.
6.
In the ‘Coder Group’ drop-down list, select the coder group you want to assign to that Profile.
You can select the gateway’s default coders (refer to Section 5.8.1.3 on page 53) or one of
the coder groups you defined in the Coder Group Settings screen (refer to Section 5.8.5.1 on
page 83).
Version 4.4
87
March 2005
MP-1xx SIP
7.
Repeat steps 2 to 6 for the second to fifth IP Profiles (optional).
8.
Click the Submit button to save your changes.
9.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-17: ini File IP Profile Settings
Parameter
Description
IPProfile_ID
IPProfile_<Profile ID> =
<Profile Name>,<Preference>,<Coder Group ID>,<IsFaxUsed *>,<DJBufMinDelay *>,
<DJBufOptFactor *>,<IPDiffServ *>,<ControlIPDiffServ *>,<EnableSilenceCompression>,
<RTPRedundancyDepth>
For example:
IPProfile_1 = name1,2,1,0,10,13,15,44,1,1
IPProfile_2 = name2,$$,$$,$$,$,$$,$$,$$,$$,1
$$ = Not configured, the default value of the parameter is used.
(*) = Common parameter used in both IP and Tel profiles.
Note: This parameter can appear up to 4 times.
MP-1xx SIP User’s Manual
88
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.6
5. Configuring the MP-1xx
Configuring the Endpoint Phone Numbers
From the Endpoint Phone Numbers screen you can enable and assign telephone numbers, hunt
groups (optional) and profiles to the VoIP gateway ports.
To configure the Endpoint Phone Numbers table, take these 4 steps:
1.
Open the ‘Endpoint Phone Numbers Table’ screen (Protocol Management menu >
Endpoint Phone Numbers); the ‘Endpoint Phone Numbers Table’ screen is displayed.
Figure 5-19: Endpoint Phone Number Table Screen
2.
Configure the Endpoint Phone Numbers according to Table 5-18. You must enter a number
in the Phone Number fields for each port that you want to use.
3.
Click the Submit button to save your changes, or click the Register or Un-Register buttons
to save your changes and to register / unregister to a Proxy / Registrar.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-18: Endpoint Phone Numbers Table
Parameter
Description
Channel(s)
The numbers (1-8) in the Channel(s) fields represent the ports on the back of the VoIP
gateway.
To enable a VoIP gateway channel, you must enter the port number on this screen.
[n-m] represents a range of ports. For example, enter [1-4] to specify the ports from 1 to
4.
Note: For FXO gateways, the number of defined endpoints must not exceed the number
of connected physical lines.
Phone Number
In each of the Phone Number fields, enter the telephone number that is assigned to that
channel.
For a range of channels enter the first number in an ordered sequence.
These numbers are also used for port allocation for IP to Tel calls, if the hunt group’s
‘Channel Select Mode’ is set to ‘By Phone Number’.
Version 4.4
89
March 2005
MP-1xx SIP
Table 5-18: Endpoint Phone Numbers Table
Parameter
Description
Hunt Group ID
In each of the Hunt Group ID fields, enter the hunt group ID (1-99) assigned to the
channel(s). The same hunt group ID can be used for more than one channel and in
more than one field.
The hunt group ID is an optional field that is used to define a group of common behavior
channels that are used for routing IP to Tel calls. If an IP to Tel call is assigned to a hunt
group, the call is routed to the channel or channels that correspond to the hunt group ID.
You can configure the Hunt Group Settings table to determine the method in which new
calls are assigned to channels within the hunt groups (refer to Section 5.8.7 on page
91).
Note: If you enter a hunt group ID, you must configure the IP to Hunt Group Routing
Table (assigns incoming IP calls to the appropriate hunt group). If you do not configure
the IP to Hunt Group Routing Table, calls don’t complete.
For information on how to configure this table refer to Section 5.8.4.3.
Profile ID
Enter the number of the Tel profile that is assigned to the endpoints defined in the
‘Channel(s)’ field.
Parameter Name in ini File
Parameter Format
TrunkGroup_x
TrunkGroup_<Hunt Group ID> = <Starting channel> - <Ending channel>, <Phone
Number>, <Tel Profile ID>
For example:
TrunkGroup_1 = 1-4,100
TrunkGroup_2 = 5-8,200,1
Note 1: The numbering of channels starts with 1.
Note 2: ‘Hunt Group ID’ can be set to any number in the range 1 to 99.
Note 3: When ‘x’ (Hunt Group ID) is omitted, the functionality of the TrunkGroup
parameter is similar to the functionality of ChannelList and Channel2Phone parameters.
Note 4: This parameter can appear up to 8 times for MP-108 Gateways and up to 24
times for MP-124 Gateways.
Note 5: An optional Tel ProfileID (1 to 5) can be applied to each group of channels.
ChannelList
Note: TrunkGroup_x
parameter can be used
instead.
Channel2Phone
MP-1xx SIP User’s Manual
List of phone numbers for MP-1xx channels
a, b, c, d
a = first channel.
b = number of channels starting from “a”.
c = the phone number of the first channel.
d = Tel Profile ID assigned to the group of channels.
For example: ChannelList = 0,8,101, defines phone numbers 101 to 108 for up to 8 MP108 channels.
Note 1: The ini file can include up to 24 “ChannelList = “ entries.
Note 2: The “ChannelList“ can be used instead of, or in addition to, Channel2Phone
parameter.
Phone number of channel.
Its format: Channel2Phone = “<channel>, <number>”
<channel> is 0...23.
Example: “Channel2Phone = 0, 1002”
Appears once for each channel: 8 times for MP-108, or 4 times for MP-104 and twice for
MP-102.
For 8-port and 24-port gateways it is suggested to use “TrunkGroup“ parameter, where
in a single line, all gateway’s phone numbers can be defined.
Note: When ‘Channel2Phone’ is used to define an endpoint, hunt group and profile can’t
be assigned to that endpoint.
90
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.7
5. Configuring the MP-1xx
Configuring the Hunt Group Settings
The Hunt Group Settings Table is used to determine the method in which new calls are assigned
to channels within each hunt group. If such a rule doesn’t exist (for a specific hunt group), the
global rule, defined by the Channel Select Mode parameter (Protocol Definition > General
Parameters), applies.
To configure the Hunt Group Settings table, take these 7 steps:
1.
Open the ‘Hunt Group Settings’ screen (Protocol Management menu > Hunt Group
Settings); the ‘Hunt Group Settings’ screen is displayed.
Figure 5-20: Hunt Group Settings screen
2.
In the Routing Index drop-down list, select the range of entries that you want to edit (up to
24 entries can be configured).
3.
In the Hunt Group ID field, enter the hunt group ID number.
4.
In the Channel Select Mode drop-down list, select the Channel Select Mode that
determines the method in which new calls are assigned to channels within the hunt groups
entered in the field to the right of this field. For information on available Channel Select
Modes refer to Table 5-19.
5.
Repeat steps 4 and 5, for each defined hunt group.
6.
Click the Submit button to save your changes.
7.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Version 4.4
91
March 2005
MP-1xx SIP
Table 5-19: Channel Select Modes
Mode
Description
By phone number
Select the gateway port according to the called number (refer to the note
below).
Cyclic Ascending
Select the next available channel in ascending cycle order. Always select the
next higher channel number in the hunt group. When the gateway reaches the
highest channel number in the hunt group, it selects the lowest channel
number in the hunt group and then starts ascending again.
Ascending
Select the lowest available channel. Always start at the lowest channel number
in the hunt group and if that channel is not available, select the next higher
channel.
Cyclic Descending
Select the next available channel in descending cycle order. Always select the
next lower channel number in the hunt group. When the gateway reaches the
lowest channel number in the hunt group, it selects the highest channel
number in the hunt group and then start descending again.
Descending
Select the highest available channel. Always start at the highest channel
number in the hunt group and if that channel is not available, select the next
lower channel.
Number + Cyclic Ascending
First select the gateway port according to the called number (refer to the note
below). If the called number isn’t found, then select the next available channel
in ascending cyclic order. Note that if the called number is found, but the port
associated with this number is busy, the call is released.
Parameter Name in ini File
Parameter Format
TrunkGroupSettings
TrunkGroupSettings = <Hunt group ID>, <Channel select Mode>
For example:
TrunkGroupSettings = 1,5
<Channel Select Mode> can accept the following values:
• 0 = By Phone Number
• 1 = Cyclic Ascending
• 2 = Ascending
• 3 = Cyclic Descending
• 4 = Descending
• 5 = Number + Cyclic Ascending
Note: This parameter can appear up to 24 times.
Note:
MP-1xx SIP User’s Manual
The gateway’s port numbers are defined in the ‘Endpoint Phone Numbers’
table under the ‘Phone Number’ column. For detailed information on the
‘Endpoint Phone Numbers’ table refer to Section 5.8.6 on page 89).
92
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.8
5. Configuring the MP-1xx
Configuring the Endpoint Settings
The Endpoint Settings screens enable you to configure port-specific parameters.
5.8.8.1
Authentication
The Authentication Table (normally used with FXS gateways) defines a username and password
combination for authentication for each MP-1xx port.
The ‘Authentication Mode’ parameter (described in Table 5-2) determines if authentication is
performed per port or for the entire gateway. If authentication is performed for the entire gateway,
this table is ignored.
Note that if either the username or password field is omitted, the port’s phone number (defined in
Table 5-18) and global password (refer to the parameter ‘Password’ described in Table 5-2) are
used instead.
To configure the Authentication Table, take these 6 steps:
1.
Set the ‘Authentication Mode’ parameter to ‘Authentication per Endpoint’.
2.
Open the ‘Authentication’ screen (Protocol Management menu > Endpoint Settings >
Authentication option); the ‘Authentication’ screen is displayed.
Figure 5-21: Authentication Screen
3.
In the ‘User Name’ and ‘Password’ fields for a port, enter the username and password
combination respectively.
4.
Repeat step 4 for each port.
5.
Click the Submit button to save your changes.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-20: Authentication ini File Parameter
Parameter Name in ini File
Parameter Format
Authentication_x
Authentication_<Port Number> = <Username>,<Password>
For example:
Authentication_0 = david,14325
Authentication_1 = Alex,18552
Note: Using the sign “$$” enables the User to omit either the username or
the password. For instance, Authentication_5 = $$, 152. In this case,
endpoint 5’s phone number is used instead of username.
Version 4.4
93
March 2005
MP-1xx SIP
5.8.8.2
Automatic Dialing
Use the Automatic Dialing Table to define telephone numbers that are automatically dialed when
a specific port is used.
To configure the Automatic Dialing table, take these 6 steps:
1.
Open the ‘Automatic Dialing’ screen (Protocol Management menu > Endpoint Settings
submenu > Automatic Dialing option); the ‘Automatic Dialing’ screen is displayed.
Figure 5-22: Automatic Dialing Table Screen
2.
In the ‘Destination Phone Number’ field for a port, enter the telephone number to dial.
3.
In the ‘Auto Dial Status’ field, select one of the following:
Enable [1] – When a port is selected, when making a call, the number in the Destination
Phone Number field is automatically dialed if phone is offhooked (for FXS gateways) or
ring signal is applied to port (FXO gateways).
Disable [0] – The automatic dialing option on the specific port is disabled (the number in
the Destination Phone Number field is ignored).
Hotline [2] – When a phone is offhooked and no digit is pressed for
‘HotLineDialToneDuration’, the number in the Destination Phone Number field is
automatically dialed (applies to FXS and FXO gateways).
4.
Repeat step 3 for each port you want to use for Automatic Dialing.
5.
Click the Submit button to save your changes.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Note 1:
After a ring signal is detected, on an ‘Enabled’ FXO port, the gateway
initiates a call to the destination number without seizing the line. The line is
seized only after the call is answered.
Note 2:
After a ring signal is detected on a ‘Disabled’ or ‘Hotline’ FXO port, the
gateway seizes the line.
MP-1xx SIP User’s Manual
94
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-21: Automatic Dialing ini File Parameter
Parameter Name in ini File
Parameter Format
TargetOfChannelX
TargetOfChannel<Port> = <Phone>,<Mode>
For example:
TargetOfChannel0 = 1001,1
TargetOfChannel3 = 911,2
Note 1: The numbering of channels starts with 0.
Note 2: Define this parameter for each gateway port you want to use for
Automatic Dialing.
Note 3: This parameter can appear up to 8 times for MP-108 gateways and up
to 24 times for MP-124 gateways.
5.8.8.3
Caller ID
Use the Caller Display Information screen to send (to IP) Caller ID information when a call is
made using the VoIP gateway (relevant to both FXS and FXO). The person receiving the call can
use this information for caller identification. The information on this table is sent in an INVITE
message in the ‘From’ header. For information on Caller ID restriction according to destination /
source prefixes refer to Section 5.8.3 on page 68.
Note:
If Caller ID name is detected on an FXO line (EnableCallerID = 1), it is used
instead of the Caller ID name defined in this table (FXO gateways only).
To configure the Caller ID table, take these 6 steps:
1.
Open the ‘Caller Display Information’ screen (Protocol Management menu > Endpoint
Settings submenu > Caller ID option); the ‘Caller Display Information’ screen is displayed.
Figure 5-23: Caller Display Information Screen
2.
Version 4.4
In the Caller ID/Name field, enter the Caller ID string. The Caller ID string can contain up to
18 characters.
Note that when the FXS gateway receives “Private” or “Anonymous” strings in the ‘From’
header, it doesn’t send the calling name or number to the Caller ID display.
95
March 2005
MP-1xx SIP
3.
In the ‘Presentation’ field, select ‘Allowed’ [0] to send the string in the Caller ID/Name field
when a (Tel IP) call is made using this VoIP gateway port. Select ‘Restricted’ [1] if you
don’t want to send this string. Note that when ‘Presentation’ is set to ‘Restricted’, the
parameter ‘Asserted Identity Mode’ must be set to ‘P-Asserted’.
Note: The value of the ‘Presentation’ field can (optionally) be overridden by configuring the
‘Presentation’ parameter in the ‘Source Number Manipulation’ table.
To maintain backward compatibility, when the strings “Private” or “Anonymous” are set in the
Caller ID/Name field, the Caller ID is restricted and the value in the Presentation field is
ignored.
4.
Repeat steps 2 and 3 for each VoIP gateway port.
5.
Click the Submit button to save your changes.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-22: Caller ID ini File Parameter
Parameter Name in ini File
Parameter Format
CallerDisplayInfoX
CallerDisplayInfo<channel> = <Caller ID string>,<Restriction>
0 = Not restricted (default).
1 = Restricted.
For example:
CallerDisplayInfo0 = Susan C.,0
CallerDisplayInfo2 = Mark M.,1
Note 1: The numbering of channels starts with 0.
Note 2: This parameter can appear up to eight times for MP-108, and up
to 24 times for MP-124.
5.8.8.4
Call Forward
The VoIP gateway allows you to forward incoming IP Tel calls (using 302 response) based on
the VoIP gateway port to which the call is routed (applicable only to FXS gateways).
The Call Forwarding Table is applicable only if the Call Forward feature is enabled. To enable
Call Forward set ‘Enable Call Forward’ to ‘Enable’ in the ‘Supplementary Services’ screen, or
‘EnableForward=1’ in the ini file (refer to Table 5-6).
To configure the Call Forward table, take these 4 steps:
1.
Open the ‘Call Forward Table’ screen (Protocol Management menu > Endpoint Settings
submenu > Call Forward option); the ‘Call Forward Table’ screen is displayed.
Figure 5-24: Call Forwarding Table Screen
MP-1xx SIP User’s Manual
96
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
2.
Configure the Call Forward parameters for each port according to the table below.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-23: Call Forward Table
Parameter
Description
Forward Type
Not in use
[0] = Don’t forward incoming calls (default).
On Busy
[1] = Forward incoming calls when the gateway port is busy.
Immediate
[2] = Forward any incoming call to the Phone number specified.
No reply
[3] = Forward incoming calls that are not answered with the time
specified in the ‘Time for No Reply Forward’ field.
On busy or No reply [4] = Forward incoming calls when the port is busy or when calls
are not answered after a configurable period of time.
Do Not Disturb
[5] = Immediately reject incoming calls.
Forward to Phone Number
Enter the telephone number or URL (number@IP address) to which the call is
forwarded.
Note: If this field only contains telephone number and Proxy isn’t used, the ‘forward to’
phone number must be specified in the ‘Tel to IP Routing’ table of the forwarding
gateway.
Time for No Reply Forward
If you have set the Forward Type for this port to no reply, enter the number of seconds
the VoIP gateway waits before forwarding the call to the phone number specified.
Parameter Name in ini File
Parameter Format
FwdInfo_x
FwdInfo_<Gateway Port Number (0 to 23)> = <Forward Type>, <Forwarded SIP User
Identification>, <Timeout (in seconds) for No Reply>
For example:
FwdInfo_0 = 1,1001
FwdInfo_1 = 1,2003@10.5.1.1
FwdInfo_2 = 3,2005,30
Note 1: The numbering of gateway ports starts with 0.
Note 2: This parameter can appear up to 24 times for MP-124.
Version 4.4
97
March 2005
MP-1xx SIP
5.8.8.5
Caller ID Permissions
The Caller ID Permission table is used to enable or disable (per port) the Caller ID generation (for
FXS gateways) and detection (for FXO gateways). If a port isn’t configured, its Caller ID
generation / detection are determined according to the global parameter ‘EnableCallerID’
(described in Table 5-6).
To configure the Caller ID Permission Table, take these 5 steps:
1.
Open the ‘Caller ID Permission’ screen (Protocol Management menu > Endpoint Settings
> Caller ID Permission option); the ‘Caller ID Permission ’ screen is displayed.
Figure 5-25: MP-1xx FXS Caller ID Permission Screen
2.
In the ‘Caller ID’ field, select one of the following:
Enable – Enables Caller ID generation (FXS) or detection (FXO) for the specific port.
Disable – Caller ID generation (FXS) or detection (FXO) for the specific port is disabled.
Empty – Caller ID generation (FXS) or detection (FXO) for the specific port is determined
according to the parameter ‘EnableCallerID’ (described in Table 5-6).
3.
Repeat step 2 for each port.
4.
Click the Submit button to save your changes.
5.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-24: Authentication ini File Parameter
Parameter Name in ini File
Parameter Format
EnableCallerID_X
EnableCallerID_<Port> = <Caller ID>
Caller ID:
0
= Disabled (default).
1
= Enabled.
If not configured, use the global parameter ‘EnableCallerID’.
Note 1: The numbering of ports starts with 0.
Note 2: This parameter can appear up to eight times for MP-108, and up
to 24 times for MP-124.
MP-1xx SIP User’s Manual
98
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.8.9
5. Configuring the MP-1xx
Configuring the FXO Parameters
Use this screen to configure the gateway’s specific FXO parameters.
To configure the FXO parameters, take these 4 steps:
1.
Open the ‘FXO Settings’ screen (Protocol Management menu > FXO); the ‘FXO Settings’
screen is displayed.
Figure 5-26: FXO Settings Screen
2.
Configure the FXO parameters according to Table 5-25.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Table 5-25: FXO Parameters (continues on pages 99 to 100)
Parameter
Description
Dialing Mode
[IsTwoStageDial]
One Stage [0] = One-stage dialing.
Two Stage [1] = Two-stage dialing (default).
Used for IP MP-10x/FXO gateways calls.
If two-stage dialing is enabled, then the FXO gateway seizes one of the PSTN/PBX lines
without performing any dial, the remote User is connected over IP to PSTN/PBX, and all
further signaling (dialing and Call Progress Tones) is performed directly with the PBX
without the gateway’s intervention.
If one-stage dialing is enabled, then the FXO gateway seizes one of the available lines
(according to Channel Select Mode parameter), and dials the destination phone number
received in INVITE message. Use the ‘Waiting For Dial Tone’ parameter to specify
whether the dialing should come after detection of dial tone, or immediately after seizing
of the line.
Version 4.4
99
March 2005
MP-1xx SIP
Table 5-25: FXO Parameters (continues on pages 99 to 100)
Parameter
Description
Waiting For Dial Tone
[IsWaitForDialTone]
No
Yes
[0] = Don’t wait for dial tone.
[1] = Wait for dial tone (default).
Used for IP MP-1xx/FXO gateways, when ‘One Stage Dialing’ is enabled.
If “wait for dial tone” is enabled, the FXO gateway dials the phone number (to the
PSTN/PBX line) only after it detects a dial tone.
Note 1: The correct dial tone parameters should be configured in the Call Progress
Tones file.
Note 2: It can take the gateway 1 to 3 seconds to detect a dial tone (according to the
dial tone configuration in the Call Progress Tones file).
If ‘Waiting For Dial Tone‘ is disabled, the FXO gateway immediately dials the phone
number after seizing the PSTN/PBX line, without ‘listening’ to dial tone.
Time to Wait before Dialing
[msec]
[FXOWaitForDialTime]
Delay (in milliseconds) between the time the line is seized and dialing is begun.
The default is 1000 msec.
Note: Applicable only to MP-10x/FXO for single stage dialing, when waiting for dial tone
is disabled.
Ring Detection Timeout [sec]
[FXOBetweenRingTime]
Note: Applicable only to MP-10x/FXO gateways for Tel IP calls.
The Ring Detection timeout is used differently for normal and for automatic dialing.
If automatic dialing is not used, and if Caller ID is enabled, then the FXO gateway seizes
the line after detection of the second ring signal (allowing detection of caller ID, sent
between the first and the second rings). If the second ring signal doesn’t arrive for “Ring
Detection Timeout” the gateway doesn’t initiate a call to IP.
When automatic dialing is used, the FXO gateway initiates a call to IP when ringing
signal is detected. The FXO line is seized only if the remote IP party answers the call. If
the remote party doesn’t answer the call and the ringing signal stops for “Ring Detection
Timeout”, the FXO gateway Releases the IP call.
Usually set to a value between 5 to 8.
The default is 8 seconds.
Reorder Tone Duration [sec]
[TimeForReorderTone]
Busy or Reorder tone duration (seconds) the FXO gateway plays before releasing the
line.
The valid range is 0 to 100. The default is 10 seconds.
Usually, after playing a Reorder / Busy tone for the specified duration, the FXS gateway,
starts playing an Offhook Warning tone.
Note 1: Selection of Busy or Reorder tone is performed according to the release cause
received from IP.
Note 2: Refer also to the parameter ‘CutThrough’ (described in Table 5-5).
Answer Supervision
[EnableVoiceDetection]
Yes [1] = FXO gateway sends 200 OK (to INVITE) message when speech/fax/modem
is detected.
No
[0] = 200 OK is sent immediately after the FXO gateway finishes dialing (default).
Note 1: To activate this feature set “DSPVersionTemplateNumber” parameter to 2 or 3.
Usually this feature is used only with early media establish voice path before the call is
answered.
Note 2: This feature is applicable only to ‘One Stage’ dialing.
Rings before Detecting Caller Sets the number of rings before the gateway starts detection of Caller ID (FXO only).
ID
0 [0]= Before first ring.
[RingsBeforeCallerID]
1 [1]= After first ring (default).
2 [2]= After second ring.
SendMetering2IP
No
[0] = Disabled (default).
[Send Metering Message to
Yes [1] = FXO gateways send a metering tone Info message to IP on detection of
IP]
12/16 kHz metering pulse. FXS gateways generate the 12/16 kHz metering tone on
reception of a metering message.
Note 1: Suitable (12 kHz or 16 kHz) coeff file must be used for both FXS and FXO
gateways. The ‘MeteringType’ parameter must be defined in both FXS/FXO gateways.
Note 2: The proprietary metering tone Info message is shown in Section 8.8 on page
159.
MP-1xx SIP User’s Manual
100
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
5.8.10 Protocol Management ini File Parameters
Table 5-26 describes the SIP Protocol Management parameters that can only be configured via
the ini file.
Table 5-26: Protocol Management, ini File Parameters (continues on pages 101 to 102)
ini File Parameter
Name
Valid Range and Description
SubscriptionMode
Determines the method the gateway uses to subscribe to an MWI server.
0 (Per endpoint) = Each endpoint subscribes separately. This method is usually used for
FXS gateways (default).
1 (Per gateway) = Single subscription for the entire gateway. This method is usually used
for FXO gateways.
EnablePtime
0 = Remove the ptime header from SDP.
1 = Include the ptime header in SDP (default).
EnableRPIheader
Enable Remote-Party-ID Headers for calling and called numbers for Tel IP calls.
0 = Disable (default).
1 = RPI (Remote-Party-ID) headers are generated in SIP INVITE message for both
called and calling numbers.
IsUserPhoneInFrom
0 = Doesn’t use ";user=phone" string in From header (default).
1 = ";user=phone" string is part of the From header.
EnableDID
Enables Japan NTT ‘Modem’ Direct Inward Dialing (DID) support. FXS gateways can be
connected to Japan’s NTT PBX using ‘Modem’ DID lines. These DID lines are used to
deliver a called number to the PBX (applicable to FXS gateways). The DID signal can be
sent alone or combined with an NTT Caller ID signal.
EnableDID_X
Enables generation of Japan NTT Modem DID signal per port.
EnableDID_<Port> = <Modem DID>
Modem DID:
0
= Disabled (default).
1
= Enabled.
If not configured, use the global parameter ‘EnableDID’.
Note: Applicable only to MP-1xx/FXS gateways.
FarEndDisconnectSilence
Threshold
Threshold of the packet count (in percents), below which is considered silence by the
media gateway.
The valid range is 1 to 100. The default is 8%.
Note: Applicable only if silence is detected according to packet count
(FarEndDisconnectSilenceMethod = 1).
T38UseRTPPort
Defines that the T.38 packets are sent / received using the same port as RTP packets.
0 = Use the RTP port +2 to send / receive T.38 packets (default).
1 = Use the same port as the RTP port to send / receive T.38 packets.
DisableAutoDTMFMute
Enables / disables the automatic mute of DTMF digits when out-of-band DTMF
transmission is used.
0 = Auto mute is used (default).
1 = No automatic mute of in-band DTMF.
When ‘DisableAutoDTMFMute=1’, the DTMF transport type is set according to the
parameter ‘DTMFTransportType’ and the DTMF digits aren’t muted if out-of-band DTMF
mode is selected (’IsDTMFUsed =1’). This enables the sending of DTMF digits in-band
(transparent of RFC 2833) in addition to out-of-band DTMF messages.
Note: Usually this mode is not recommended.
DisconnectOnBusyTone
Version 4.4
0 = Call isn’t released (FXO gateway).
1 = Call is released (on FXO gateways) if busy or reorder (fast busy) tones are detected
on the gateway’s FXO port (default).
101
March 2005
MP-1xx SIP
Table 5-26: Protocol Management, ini File Parameters (continues on pages 101 to 102)
ini File Parameter
Name
Valid Range and Description
MeteringType
Defines the metering tone (12 kHz or 16 kHz) that is detected by FXO gateways and
generated by FXS gateways.
0 = 12 kHz metering tone (default).
1 = 16 kHz metering tone.
Note: Suitable (12 kHz or 16 KHz) coeff file must be used for both FXS and FXO
gateways.
PolarityReversalType
Defines the voltage change slope during polarity reversal or wink.
0 = Soft (default).
1 = Hard.
Note 1: Some Caller ID signals use reversal polarity and/or wink signals. In these cases
it is recommended to set PolarityReversalType to 1 (Hard).
Note 2: Applicable only to FXS gateways.
CurrentDisconnectDuratio Duration of the current disconnect pulse (in msec).
n
The default is 900 msec, The range is 200 to 1500 msec.
Applicable for both FXS and FXO gateways.
Note: The FXO gateways’ detection range is +/-200 msec of the parameter’s value +
100.
For example if CurrentDisconnectDuration = 200, the detection range is 100 to 500
msec.
CurrentDisconnectDefault
Threshold
TimeToSampleAnalogLine
Voltage
Determines the line voltage threshold which, when reached, is considered a current
disconnect detection.
Note: Applicable only to MP-10x/FXO gateways.
The valid range is 0 to 20 Volts. The default value is 4 Volts.
Determines the frequency at which the analog line voltage is sampled (after offhook), for
detection of the current disconnect threshold.
Note: Applicable only to MP-10x/FXO gateways.
The valid range is 100 to 2500 msec. The default value is 1000 msec.
AnalogCallerIDTimimgMod 0 = Caller ID is generated between the first two rings (default).
e
1 = The gateway attempts to find an optimized timing to generate the Caller ID according
to the selected Caller ID type. Note that when used with distinctive ringing, the Caller ID
signal doesn’t change the distinctive ringing timing.
Note: Applicable only to FXS gateways.
EnableRAI
0 = Disable RAI (Resource Available Indication) service (default).
1 = Enable RAI service.
If RAI is enabled, an SNMP ‘acBoardCallResourcesAlarm’ Alarm Trap is sent if gateway
resources fall below a predefined (configurable) threshold.
RAIHighThreshold
High Threshold (in percentage) that defines the gateway‘s busy endpoints.
The range is 0 to 100.
The default value is 90%.
When the percentage of the gateway‘s busy endpoints exceeds the value configured in
High Threshold, the gateway sends an SNMP ‘acBoardCallResourcesAlarm’ Alarm Trap
with a ‘major’ Alarm Status.
Note: The gateway’s available Resources are calculated by dividing the number of busy
endpoints by the total number of available gateway endpoints.
RAILowThreshold
Low Threshold (in percentage) that defines the gateway‘s busy endpoints.
The range is 0 to 100.
The default value is 90%.
When the percentage of the gateway’s busy endpoints falls below the value defined in
Low Threshold, the gateway sends an SNMP ‘acBoardCallResourcesAlarm’ Alarm Trap
with a ‘cleared’ Alarm Status.
RAILoopTime
MP-1xx SIP User’s Manual
Time interval (in seconds) that the gateway checks for resource availability.
The default is 10 seconds.
102
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.9
5. Configuring the MP-1xx
Advanced Configuration
Use this subdivided menu to set the gateway’s advanced configuration parameters (for advanced
users only).
5.9.1
Configuring the Network Settings
From the Network Settings page you can define:
•
IP settings.
•
NTP settings.
•
SNMP settings.
•
Syslog settings.
•
RTP settings.
•
Ethernet Ports Information (read-only).
To configure the Network Settings parameters, take these 4 steps:
1.
Open the ‘Network Settings’ screen (Advanced Configuration menu > Network Settings);
the ‘Network Settings’ screen is displayed.
Figure 5-27: Network Settings Screen
Version 4.4
103
March 2005
MP-1xx SIP
2.
Configure the Network Settings according to
3.
.
4.
Click the Submit button to save your changes.
5.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Note:
Those parameters contained within square brackets are the names used to
configure the parameters via the ini file.
Table 5-27: Network Setting Parameters (continues on pages 104 to 106)
Parameter
Description
IP Settings
IP Address
IP address of the gateway.
Enter the IP address in dotted format notation, for example 10.8.201.1.
Note 1: A warning message is displayed (after pressing the button ‘Submit’) if the
entered value is incorrect.
Note 2: After changing the IP address and pressing the button ‘Submit’, a prompt
appears indicating that for the change to take effect, the gateway is to be reset.
Subnet Mask
Subnet mask of the gateway.
Enter the subnet mask in dotted format notation, for example 255.255.0.0
Note 1: A warning message is displayed (after pressing the button ‘Submit’) if the
entered value is incorrect.
Note 2: After changing the subnet mask and pressing the button ‘Submit’, a prompt
appears indicating that for the change to take effect, the gateway is to be reset.
Default Gateway Address
IP address of the default gateway used by the gateway.
Enter the IP address in dotted format notation, for example 10.8.0.1.
Note 1: A warning message is displayed (after pressing the button ‘Submit’) if the
entered value is incorrect.
Note 2: After changing the default gateway IP address and pressing the button
‘Submit’, a prompt appears indicating that for the change to take effect, the gateway
is to be reset.
For detailed information on multiple routers support, refer to Section 5.9.1.2 on page
112.
DNS Primary Server IP
[DNSPriServerIP]
IP address of the primary DNS server.
Enter the IP address in dotted format notation, for example 10.8.2.255.
Note: To use Fully Qualified Domain Names (FQDN) in the Tel to IP Routing table,
you must define this parameter.
DNS Secondary Server IP
[DNSSecServerIP]
IP address of the second DNS server.
Enter the IP address in dotted format notation, for example 10.8.2.255.
MP-1xx SIP User’s Manual
104
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-27: Network Setting Parameters (continues on pages 104 to 106)
Parameter
Description
Enable DHCP
[DHCPEnable]
Disable [0] = Disable DHCP support on the gateway (default).
Enable [1] = Enable DHCP support on the gateway.
After the gateway is powered up, it attempts to communicate with a BootP server. If
a BootP server is not responding and if DHCP is enabled, then the gateway attempts
to get its IP address and other network parameters from the DHCP server.
Note: After you enable the DHCP Server (from the Web browser) follow this
procedure:
• Click the Submit button.
• Save the configuration using the ‘Save Configuration’ button (before you reset
the gateway). For information on how to save the configuration refer to Section
5.12 on page 139.
• Reset the gateway directly (Web reset doesn’t trigger the BootP/DHCP
procedure and the parameter DHCPEnable reverts to ‘0’).
Note that throughout the DHCP procedure the BootP/TFTP application must be
deactivated. Otherwise, the MP-1xx receives a response from the BootP server
instead of the DHCP server.
Note: For additional information on DHCP refer to Section 10.2 on page 175.
ini file note: The DHCPEnable is a special "Hidden" parameter. Once defined and
saved in flash memory, its assigned value doesn’t revert to its default even if the
parameter doesn't appear in the ini file.
NAT IP Address
[StaticNatIP]
Global gateway IP address.
Define if static Network Address Translation (NAT) device is used between the
gateway and the Internet.
NTP Settings
For detailed information on NTP, refer to Section 5.9.1.3 on page 112.
NTP Server IP Address
[NTPServerIP]
IP address (in dotted format notation) of the NTP server.
The default IP address is 0.0.0.0 (the internal NTP client is disabled).
NTP UTC Offset
[NTPServerUTCOffset]
Defines the UTC (Universal Time Coordinate) offset (in seconds) from the NTP
server.
The default offset is 0. The offset range is –43200 to 43200 seconds.
NTP Update Interval
[NTPUpdateInterval]
Defines the time interval (in seconds) the NTP client requests for a time update.
The default interval is 86400 seconds (24 hours). The range is 0 to 214783647
seconds.
Note: It isn’t recommended to be set beyond one month (2592000 seconds).
SNMP Settings
Enable SNMP
[DisableSNMP]
Enable [0] = SNMP is enabled (default).
Disable [1] = SNMP is disabled and no traps are sent.
For detailed information on configuring the SNMP Managers table, refer to Section 5.9.1.1 on page 107.
For detailed information on the SNMP parameters that can only be configured via the ini file, refer to Table 5-30 on
page 111.
For detailed information on developing an SNMP-based program to manage your devices, refer to Section 179 on page
11.
Syslog Settings
Syslog Server IP address
[SyslogServerIP]
Version 4.4
IP address (in dotted format notation) of the computer you are using to run the
Syslog Server.
The Syslog Server is an application designed to collect the logs and error messages
generated by the VoIP gateway.
Note: The default UDP Syslog port is 514.
For information on the Syslog refer to Section 9.2.2 on page 170.
105
March 2005
MP-1xx SIP
Table 5-27: Network Setting Parameters (continues on pages 104 to 106)
Parameter
Description
Enable Syslog
[EnableSyslog]
Enable [1] = Send the logs and error message generated by the gateway to the
Syslog Server. If you select Enable, you must enter an IP address in the Syslog
Server IP address field.
Disable [0] = Logs and errors are not sent to the Syslog Server (default).
Note 1: Syslog messages may increase the network traffic.
Note 2: Logs can also be sent to the RS-232 serial port (refer to Section 9.2 on page
170).
Note 3: To configure the Syslog logging levels use the parameter ‘Debug Level’.
RTP Settings
RTP Base UDP Port
[BaseUDPPort]
Lower boundary of UDP port used for RTP, RTCP (Real-Time Control Protocol)
(RTP port + 1) and T.38 (RTP port + 2). The upper boundary is the Base UDP Port +
10 * (number of gateway’s channels).
The range of possible UDP ports is 4000 to 64000.
The default base UDP port is 6000.
For example:
If the Base UDP Port is set to 6000 (the default) then:
The first channel uses the following ports: RTP 6000, RTCP 6001 and T.38 6002,
the second channel uses: RTP 6010, RTCP 6011 and T.38 6012, etc.
Note: If RTP Base UDP Port is not a factor of 10, the following message is
generated: "invalid local RTP port".
For detailed information on the default RTP/RTCP/T.38 port allocation refer to the
Section C.3 on page 210.
RTP IP Diff Serv
[IPDiffServ]
DSCP values can be from 0 to 63 (default = 0)
Diff Serv Code Point (DSCP) value that is assigned to the RTP packets. The DSCP
value is used by DiffServ compatible routers to prioritize how packets are sent. By
prioritizing packets, the DiffServ routers can minimize the transmission delays for
time sensitive packets such as VoIP packets.
If enter a Diff Serv value, this value is used instead of the RTP IP TOS and RTP IP
Precedence values.
RTP IP TOS
[IPTOS]
Value that is assigned to IP Type Of Service (TOS) field in the IP header for all RTP
packets sent by the VoIP gateway.
You can enter a value from 0 to 15.
The default value is 0.
RTP IP Precedence
[IPPrecedence]
Value that is assigned to the IP Precedence field in the IP header for all RTP packets
sent by the VoIP gateway.
You can enter a value from 0 to 7.
The default value is 0.
Ethernet Ports Information
Port 1 Duplex Mode
Shows the Duplex mode the Ethernet port is using (Half Duplex or Full Duplex).
This is a read-only parameter.
Port 1 Speed
Shows the speed, in Mbps, that the Ethernet port is using (10 Mbps or 100 Mbps).
This is a read-only parameter.
MP-1xx SIP User’s Manual
106
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.9.1.1
5. Configuring the MP-1xx
Configuring the SNMP Managers Table
The SNMP Managers table allows you to configure the attributes of up to five SNMP managers.
To configure the SNMP Managers Table, take these 6 steps:
1.
Access the ‘Network Settings’ screen (Advanced Configuration menu > Network
Settings); the ‘Network Settings’ screen is displayed (Figure 5-27).
2.
Open the SNMP Managers Table screen by clicking the arrow sign (-->) to the right of the
SNMP Managers Table label; the SNMP Managers Table screen is displayed (Figure 5-28).
3.
Configure the SNMP managers parameters according to Table 5-28 below.
4.
Click the Submit button to save your changes.
5.
Click the Close Window button.
6.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Figure 5-28: SNMP Managers Table Screen
Note:
If you clear a checkbox and click Submit, all settings in the same row revert
to their defaults.
Table 5-28: SNMP Managers Table Parameters
Web Parameter Name
ini File Parameter Name
Checkbox
[SNMPManagerIsUsed_x]
Up to five parameters, each determines the validity of the parameters (IP
address and port number) of the corresponding SNMP Manager used to
receive SNMP traps.
Checkbox cleared [0] = Disabled (default)
Checkbox selected [1] = Enabled
IP Address
[SNMPManagerTableIP_x]
Up to five IP addresses of remote hosts that are used as SNMP Managers.
The device sends SNMP traps to these IP addresses.
Enter the IP address in dotted format notation, for example 108.10.1.255.
Note: The first entry (out of the five) replaces the obsolete parameter
SNMPManagerIP.
Version 4.4
107
March 2005
MP-1xx SIP
Trap Port
[SNMPManagerTrapPort_x]
Up to five parameters used to define the Port numbers of the remote SNMP
Managers. The device sends SNMP traps to these ports.
Note: The first entry (out of the five) replaces the obsolete parameter
SNMPTrapPort.
The default SNMP trap port is 162
The SNMP trap port must be between 100 to 4000.
Trap Enable
Up to five parameters, each determines the activation/deactivation of sending
[SNMPManagerTrapSendingEnable_x] traps to the corresponding SNMP Manager.
Disable [0] = Sending is disabled
Enable [1] = Sending is enabled (default)
Table 5-29 describes the board parameters that can only be configured via the ini file.
Table 5-29: Board, ini File Parameters (continues on pages 108 to 110)
ini File Parameter Name
Valid Range and Description
LifeLineType
The Lifeline is activated on:
0 = Power down (default)
1 = Power down or when link is down (physical disconnect)
2 = Power down or when link is down or on network failure (logical link
disconnect)
Note: To enable Lifeline switching on network failure, LAN watch dog must be
activated (EnableLANWatchDog=1).
DSPVersionTemplateNumber
0 = Firmware DSP version supports PCM/ADPCM, G723 and G729A Coders
(default).
1 = Firmware DSP version supports PCM/ADPCM.
2 = Same as "0" but with voice and energy detectors.
3 = Same as "1" but with voice and energy detectors.
Usually DSP templates 2 or 3 should be used. These templates are required
for the FXO gateway Answer and Disconnect supervision features.
EnableDiagnostics
0 = No diagnostics (default).
1 = Perform diagnostics.
WatchDogStatus
0 = Disable gateway’s watch dog.
1 = Enable gateway’s watch dog (default).
DisableRS232
0 = RS-232 serial port is enabled (default)
1 = RS-232 serial port is disabled
To enable sending of all log and error messages to the RS-232 serial port,
define:
“EnableSyslog = 0” and “DisableRS232 = 0”
DisableWebTask
0 = Enable Web management (default)
1 = Disable Web management
ResetWebPassword
Enables resetting to default of Web password to:
Username: “Admin”
Password: “Admin”
DisableWebConfig
0 = Enable changing parameters from Web (default)
1 = Operate Web server in “read only” mode
HTTPport
HTTP port used for Web management (default = 80)
EthernetPhyConfiguration
0 = 10 Base-T half-duplex.
1 = 10 Base-T full-duplex.
2 = 100 Base-TX half-duplex.
3 = 100 Base-TX full-duplex.
4 = Auto-Negotiate (Default).
Note: Auto-Negotiate falls back to half-duplex mode (HD) when the opposite
port is not in auto-negotiate, but the speed (10 Base-T, 100 Base -TX) in this
mode is always configured correctly.
MP-1xx SIP User’s Manual
108
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-29: Board, ini File Parameters (continues on pages 108 to 110)
ini File Parameter Name
Valid Range and Description
DisableNAT
Enables / disables the Network Address Translation (NAT) mechanism.
0 = Enabled.
1 = Disabled (default).
Note: The compare operation that is performed on the IP address is enabled
by default and is controlled by the parameter ‘EnableIPAddrTranslation’. The
compare operation that is performed on the UDP port is disabled by default and
is controlled by the parameter ‘EnableUDPPortTranslation’.
EnableIPAddrTranslation
0 = Disable IP address translation.
1 = Enable IP address translation (default).
When enabled, the gateway compares the source IP address of the first
incoming packet, to the remote IP address stated in the opening of the channel.
If the two IP addresses don’t match, the NAT mechanism is activated.
Consequently, the remote IP address of the outgoing stream is replaced by the
source IP address of the first incoming packet.
Note: The NAT mechanism must be enabled for this parameter to take effect
(DisableNAT = 0).
EnableUDPPortTranslation
0 = Disable UDP port translation (default).
1 = Enable UDP port translation.
When enabled, the gateway compares the source UDP port of the first
incoming packet, to the remote UDP port stated in the opening of the channel.
If the two UDP ports don’t match, the NAT mechanism is activated.
Consequently, the remote UDP port of the outgoing stream is replaced by the
source UDP port of the first incoming packet.
Note: The NAT mechanism and the IP address translation must be enabled for
this parameter to take effect (DisableNAT = 0, EnableIpAddrTranslation = 1).
HeartBeatDestIP
Destination IP address (in dotted format notation) to which the gateway sends
proprietary UDP ‘ping’ packets.
The default IP address is 0.0.0.0.
HeartBeatDestPort
Destination UDP port to which the heartbeat packets are sent.
The range is 0 to 64000.
The default is 0.
HeartBeatIntervalmsec
Delay (in msec) between consecutive heartbeat packets.
10 = 100000.
-1 = disabled (default).
BootP and TFTP Parameters
IniFileURL
Specifies the name of the ini file and the location of the TFTP server from
which the gateway loads the ini and configuration files.
For example:
tftp://192.168.0.1/filename
tftp://192.10.77.13/config<MAC>
Note: The optional string “<MAC>” is replaced with the gateway’s MAC (Media
Access Control) address.
Therefore, the gateway requests an ini file name that contains its MAC
address. This option enables loading different configurations for specific
gateways.
CmpFileURL
Specifies the name of the cmp file and the location of the TFTP server from
which the gateway loads a new cmp file and updates itself.
For example: tftp://192.168.0.1/filename
Note 1: When this parameter is set in the ini file, the gateway always loads the
cmp file after it is reset.
Note 2: The version of the loaded cmp file isn’t checked.
Version 4.4
109
March 2005
MP-1xx SIP
Table 5-29: Board, ini File Parameters (continues on pages 108 to 110)
ini File Parameter Name
Valid Range and Description
The BootP parameters are special "Hidden" parameters. Once defined and saved in the flash memory, they are used
even if they don't appear in the ini file.
BootPRetries
BootP retries. Sets the number of BootP requests the device sends during
start-up. The device stops sending BootP requests when either BootP reply is
received or Number of Retries is reached.
1 = 1 BootP retry, 1 second.
2 = 2 BootP retries, 3 second.
3 = 3 BootP retries, 6 second (default).
4 = 10 BootP retries, 30 second.
5 = 20 BootP retries, 60 second.
6 = 40 BootP retries, 120 second.
7 = 100 BootP retries, 300 second.
15 = BootP retries indefinitely.
Note: This parameter only takes effect from the next reset of the device.
BootPSelectiveEnable
Enables the Selective BootP mechanism.
1 = Enabled.
0 = Disabled (default).
The Selective BootP mechanism enables the gateway’s integral BootP client to
filter unsolicited BootP/DHCP replies (accepts only BootP replies that contain
the text “AUDC" in the vendor specific information field). This option is useful in
environments where enterprise BootP/DHCP servers provide undesired
responses to the gateway’s BootP requests.
Note: When working with DHCP (EnableDHCP=1) the selective BootP feature
must be disabled.
BootPDelay
The interval between the device’s startup and the first BootP/DHCP request
that is issued by the device.
1 = 1 second (default).
2 = 3 second.
3 = 6 second.
4 = 30 second.
5 = 60 second.
Note: This parameter only takes effect from the next reset of the device.
ExtBootPReqEnable
0 = Disable (default).
1 = Enable extended information to be sent in BootP request.
If enabled, the device uses the vendor specific information field in the BootP
request to provide device-related initial startup information such as board type,
current IP address, software version, etc. For a full list of the vendor specific
Information fields refer to Section 10.3.2 on page 176.
The BootP/TFTP configuration utility displays this information in the ‘Client Info’
column (refer to Figure B-1).
Note: This option is not available on DHCP servers.
MP-1xx SIP User’s Manual
110
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-30 describes the SNMP parameters that can only be configured via the ini file.
Table 5-30: SNMP ini File Parameters
ini File Parameter Name
Description
SNMPPort
The device’s local UDP port used for SNMP Get/Set commands.
The range is 100 to 3999.
The default port is 161.
SNMPTrustedMGR_x
Up to five IP addresses of remote trusted SNMP managers from which the
SNMP agent accepts and processes get and set requests.
Note 1: If no values are assigned to these parameters any manager can
access the device.
Note 2: Trusted managers can work with all community strings.
SNMP Community String Parameters
SNMPReadOnlyCommunityString_x Read-only community string (up to 19 chars).
The default string is “public”.
SNMPReadWriteCommunityString_x Read-write community string (up to 19 chars).
The default string is “private”.
SNMPTrapCommunityString_x
Community string used in traps (up to 19 chars).
The default string is “trapuser”.
SetCommunityString
Note: Obsolete parameter, use
SNMPReadWriteCommunityString_x
instead.
SNMPManagerIP
Note: Obsolete parameter, use
SNMPManagerTableIP_x instead.
SNMP community string (up to 19 chars).
Default community string for read “public”, for set & get “private”.
IP address (in dotted format notation) for the computer that is used as the first
SNMP Manager. The SNMP Manager is a device that is used for receiving
SNMP Traps.
Note 1: To enable the device to send SNMP Traps, set the ini file parameter
SNMPManagerIsUsed to 1.
Note 2: If you want to use more than one SNMP manger, ignore this parameter
and use the parameters ‘SNMPManagerTableIP_x’ instead.
Version 4.4
111
March 2005
MP-1xx SIP
5.9.1.2
Multiple Routers Support
Multiple routers support is designed to assist the media gateway when it operates in a multiple
routers network. The gateway learns the network topology by responding to ICMP redirections
and caches them as routing rules (with expiration time).
When a set of routers operating within the same subnet serve as gateways to that network and
intercommunicate using a dynamic routing protocol (such as OSPF, etc.), the routers can
determine the shortest path to a certain destination and signal the remote host the existence of
the better route. Using multiple router support the media gateway can utilize these router
messages to change its next hop and establish the best path.
Note: Multiple Routers support is an integral feature that doesn’t require configuration.
5.9.1.3
Simple Network Time Protocol Support
Simple Network Time Protocol (SNTP) client functionality generates requests and reacts to the
resulting responses using the NTP version 3 protocol definitions (according to RFC 1305).
Through these requests and responses, the NTP client is able to synchronize the system time to
a time source within the network, thereby eliminating any potential issues should the local system
clock 'drift' during operation. By synchronizing time to a network time source, traffic handling,
maintenance, and debugging actions become simplified for the network administrator.
The NTP client follows a simple process in managing system time; the NTP client requests an
NTP update, receives an NTP response, and updates the local system clock based on a
configured NTP server within the network.
The client requests a time update from a specified NTP server at a specified update interval. In
most situations this update interval should be every 24 hours based on when the system was
restarted. The NTP server identity (as an IP address) and the update interval are configurable
parameters that can be specified either in the ini file (NTPServerIP, NTPUpdateInterval
respectively) or via an SNMP MIB object.
When the client receives a response to its request from the identified NTP server it must be
interpreted based on time zone, or location, offset that the system is to a standard point of
reference called the Universal Time Coordinate (UTC). The time offset that the NTP client should
use is a configurable parameter that can be specified either in the ini file (NTPServerUTCOffset)
or via an SNMP MIB object.
If required, the clock update is performed by the client as the final step of the update process.
The update is done in such a way as to be transparent to the end users. For instance, the
response of the server may indicate that the clock is running too fast on the client. The client
slowly robs bits from the clock counter in order to update the clock to the correct time. If the clock
is running too slow, then in an effort to catch the clock up, bits are added to the counter, causing
the clock to update quicker and catch up to the correct time. The advantage of this method is that
it does not introduce any disparity in the system time, that is noticeable to an end user, or that
could corrupt call timeouts and timestamps.
MP-1xx SIP User’s Manual
112
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.9.2
5. Configuring the MP-1xx
Configuring the Channel Settings
The Channels Settings screen enables you to set the VoIP gateway channel parameters, such as
Input and Output voice gain, Jitter buffer characteristics, Modem, Fax and DTMF transport
modes. These parameters are applied to all MP-1xx channels.
Note that several Channels Settings parameters can be configured per call using profiles (refer to
Section 5.8.5 on page 83).
To configure the Channel Settings parameters, take these 4 steps:
1.
Open the ‘Channel Settings’ screen (Advanced Configuration menu > Channel Settings);
the ‘Channel Settings’ screen is displayed.
2.
Configure the Channel Settings parameters according to Table 5-31, Table 5-32, Table 5-33
and Table 5-34.
3.
Click the Submit button to save your changes.
4.
To save the changes so they are available after a power fail refer to Section 5.12 on page
139.
Note 1:
Those parameters contained within square brackets are the names used to
configure the parameters via the ini file.
Note 2:
Channel parameters are changeable on-the-fly. Changes take effect from
next call.
Figure 5-29: Channel Settings, Voice Settings Parameters
Version 4.4
113
March 2005
MP-1xx SIP
Table 5-31: Channel Settings, Voice Settings Parameters
Parameter
Description
Voice Volume
[VoiceVolume]
Voice gain control in dB. This parameter sets the level for the transmitted
(IP Tel) signal.
You can enter a value from -32 to 31 dB.
The default value is 0 dB.
Input Gain
[InputGain]
PCM input gain control in dB. This parameter sets the level for the received
(Tel IP) signal.
You can enter a value from -32 to 31 dB.
The default value is 0 dB.
Note: This parameter is intended for advanced users. Changing it affects other
gateway functionalities.
Disable [0] = Silence Suppression disabled (default).
Enable [1] = Silence Suppression enabled.
Enable without adaptation [2] = A single silence packet is sent during silence
The parameter SCE is used to maintain period (applicable only to G.729).
backward compatibility.
Silence Suppression is a method conserving bandwidth on VoIP calls by not
sending packets when silence is detected.
Note: If the selected coder is G.729, the following rules determine the value of
the “annexb” parameter of the fmtp attribute in the SDP.
EnableSilenceCompression = 0
“annexb=no”.
EnableSilenceCompression = 1
“annexb=yes”.
EnableSilenceCompression = 2 and IsCiscoSCEMode = 0
“annexb=yes”.
EnableSilenceCompression = 2 and IsCiscoSCEMode = 1
“annexb=no”.
Silence Suppression
[EnableSilenceCompression]
Echo Canceler
[EnableEchoCanceller]
The parameter ECE is used to maintain
backward compatibility.
DTMF Transport Type
[DTMFTransportType]
Off [0] = Echo Canceler disabled.
On [1] = Echo Canceler enabled (default).
0 = Erase digits from voice stream, do not relay to remote.
2 = Digits remain in voice stream.
3 = Erase digits from voice stream, relay to remote according to RFC 2833.
Note: This parameter is automatically updated if one of the following
parameters is configured: IsDTMFUsed, TxDTMFOption or RxDTMFOption.
MF Transport Type
[MFTransportType]
N/A.
DTMF Volume (-31 to 0 dB)
[DTMFVolume]
DTMF level for regenerated digits to PSTN side (-31 to 0, corresponding to -31
dBm to 0 dBm in 1 dB steps, default = -11 dBm).
Enable Answer Detector
[EnableAnswerDetector]
N/A.
Answer Detector Activity Delay
[AnswerDetectorActivityDelay]
N/A.
Answer Detector Silence Time
[AnswerDetectorSilenceTime]
N/A.
Answer Detector Redirection
[AnswerDetectorRedirection]
N/A.
Answer Detector Sensitivity
[AnswerDetectorSensitivity]
MP-1xx SIP User’s Manual
Determines the Answer Detector sensitivity.
The range is 0 (most sensitive) to 2 (least sensitive).
The default is 0.
114
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Figure 5-30: Channel Settings, Fax/Modem/CID Parameters
Table 5-32: Channel Settings, Fax/Modem/CID Parameters (continues on pages 115 to 116)
Parameter
Description
Fax Transport Mode
[FaxTransportMode]
Fax Transport Mode that the gateway uses.
You can select:
Disable [0].
T.38 Relay [1] (default).
Bypass [2].
Events Only [3] = N/A.
Note: If parameter IsFaxUsed = 1, then FaxTransportMode is always set to 1
(T.38 relay).
Caller ID Transport Type
[CallerIDTransportType]
Caller ID Type
[CallerIDType]
V.21 Modem Transport Type
[V21ModemTransportType]
V.22 Modem Transport Type
[V22ModemTransportType]
Version 4.4
N/A.
Defines one of the following standards for detection (FXO) and generation (FXS)
of Caller ID signals.
Bellcore
[0] (default).
ETSI
[1].
NTT
[2].
British
[4]
DTMF ETSI [16]
Denmark
[17]
India
[18]
Brazil
[19]
Note: The Caller ID signals are generated/detected between the first and the
second rings.
N/A.
V.22 Modem Transport Type that the gateway uses.
You can select:
Transparent [0].
Relay [1] = N/A.
Bypass [2] (default).
115
March 2005
MP-1xx SIP
Table 5-32: Channel Settings, Fax/Modem/CID Parameters (continues on pages 115 to 116)
Parameter
Description
V.23 Modem Transport Type
[V23ModemTransportType]
V.23 Modem Transport Type that the gateway uses.
You can select:
Transparent [0].
Relay [1] = N/A.
Bypass [2] (default).
V.32 Modem Transport Type
[V32ModemTransportType]
V.32 Modem Transport Type that the gateway uses.
You can select:
Transparent [0].
Relay [1] = N/A.
Bypass [2] (default).
Note: This option applies to V.32 and V.32bis modems.
V.34 Modem Transport Type
[V34ModemTransportType]
V.34 Modem Transport Type that the gateway uses.
You can select:
Transparent [0].
Relay [1] = N/A.
Bypass [2] (default).
Note: This option applies to V.34 and V.90 modems.
Fax Relay Redundancy Depth
[FaxRelayRedundancyDepth]
Number of times that each fax relay payload is retransmitted to the network.
You can enter a value from 0 to 2.
The default value is 0.
Fax Relay Enhanced Redundancy
Depth
[FaxRelayEnhancedRedundancyD
epth]
Number of times that control packets are retransmitted when using the T.38
standard.
You can enter a value from 0 to 4.
The default value is 2.
Fax Relay ECM Enable
[FaxRelayECMEnable]
Disable [0] = Error Correction Mode (ECM) mode is not used during fax relay.
Enable [1] = ECM mode is used during fax relay (default).
Fax Relay Max Rate (bps)
[FaxRelayMaxRate]
Maximum rate, in bps, at which fax relay messages are transmitted.
You can select:
2400 [0] = 2.4 kbps.
4800 [1] = 4.8 kbps.
7200 [2] = 7.2 kbps.
9600 [3] = 9.6 kbps.
12000 [4] = 12.0 kbps.
14400 [5] = 14.4 kbps (default).
Fax/Modem Bypass Coder Type
[FaxModemBypassCoderType]
Coder the gateway uses when performing fax/modem bypass. Usually, high-bitrate coders such as G.711 should be used.
You can select:
G711 A-law 64 [0] (default).
G711 µ-law [1].
G726 32 [4].
G726 40 [11].
Fax/Modem Bypass Packing Factor
[FaxModemBypassM]
Number of (20 msec) coder payloads that are used to generate a fax/modem
bypass packet.
You can enter a value of 1, 2 or 3 coder payloads.
The default value is 1 coder payload.
CNG Detector Mode
[CNGDetectorMode]
Disable
[0] = Don’t detect CNG (default)
Relay
[1] = N/A.
Event Only [2] = Detect CNG on caller side and start fax session (if
IsFaxUsed=1)
Usually T.38 fax session starts when the “preamble” signal is detected by the
answering side. Some SIP gateways doesn’t’ support the detection of this fax
signal on the answering side, for these cases it is possible to configure the MP1xx gateways to start the T.38 fax session when the CNG tone is detected by the
originating side. However this mode is not recommended.
MP-1xx SIP User’s Manual
116
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Figure 5-31: Channel Settings, RTP Parameters
Table 5-33: Channel Settings, RTP Parameters
Parameter
Description
Dynamic Jitter Buffer Minimum Delay
[DJBufMinDelay]
Minimum delay for the Dynamic Jitter Buffer.
You can enter a value from 0 to 150 milliseconds.
The default delay is 70 milliseconds.
Note: For more information on the Jitter Buffer, refer to Section 5.9.2.1 on
page 120.
Dynamic Jitter Buffer Optimization
Factor
[DJBufOptFactor]
Dynamic Jitter Buffer frame error / delay optimization factor.
You can enter a value from 0 to 13.
The default factor is 7.
Note 1: Set to 13 for data (fax & modem) calls.
Note 2: For more information on the Jitter Buffer, refer to Section 5.9.2.1 on
page 120.
RTP Redundancy Depth
[RTPRedundancyDepth]
Enter [0] to disable the generation of redundant packets (default).
Enter [1] to enable the generation of RFC 2198 redundancy packets.
Packing Factor
[M]
N/A.
Controlled internally by the gateway according to the selected coder.
Basic RTP Packet Interval
[BasicRTPPacketInterval]
Note: This parameter should not be
used. Use the ‘Coders’ screen under
‘Protocol Definition’ instead.
N/A.
Controlled internally by the gateway according to the selected coder.
RTP Directional Control
[RTPDirectionControl]
N/A.
Controlled internally by the gateway according to the selected coder.
RFC 2833 TX Payload Type
[RFC2833TxPayloadType]
N/A.
Use the ini file parameter RFC2833PayloadType instead.
RFC 2833 RX Payload Type
[RFC2833RxPayloadType]
N/A.
Use the ini file parameter RFC2833PayloadType instead.
RFC 2198 Payload Type
[RFC2198PayloadType]
RTP redundancy packet payload type, according to RFC 2198.
The range is 96-127. The default is 104.
Applicable if “RTP Redundancy Depth=1”
Fax Bypass Payload Type
[FaxBypassPayloadType]
Determines the fax bypass RTP dynamic payload type.
The valid range is 96 to 120. The default value is 102.
Version 4.4
117
March 2005
MP-1xx SIP
Table 5-33: Channel Settings, RTP Parameters
Parameter
Description
Enable RFC 3389 CN Payload Type
[EnableStandardSIDPayloadType]
Disable [0] = G.711 SID packets are sent in a proprietary method (default).
Enable [1] = SID (comfort noise) packets are sent with the RTP SID payload
type according to RFC 3389. Applicable to G.711 and G.726 coders.
Analog Signal Transport Type
[AnalogSignalTransportType]
Ignore analog signals [0] = Hook-flash isn’t transferred to the remote side
(default).
RFC 2833 analog signal relay [1] = Hook-flash is transferred via RFC 2833.
Figure 5-32: Channel Settings, Miscellaneous Parameters
Table 5-34: Channel Settings, Miscellaneous Parameters
Parameter
Description
Min. Flash-Hook Detection Period
[msec]
[MinFlashHookTime]
Minimum threshold in msec + 50 msec for detection of hook-flash.
Relevant only for MP-1xx/FXS gateways.
25 to 300, (default = 300).
Max. Flash-Hook Detection Period
[msec]
[FlashHookPeriod]
300 to 1500 (default 400) hook-flash time in msec. The parameter is used for
hook-flash detection in MP-1xx/FXS and for hook-flash generation in MP1xx/FXO gateways.
Note: For FXO gateways, a constant of 90 msec must be added to the
required hook-flash period. For example, to generate a 450 msec hook-flash,
set ‘FlashHookPeriod’ to 540.
MP-1xx SIP User’s Manual
118
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-35 describes the Channel parameters that can only be configured via the ini file.
Table 5-35: Channel Settings, ini File Parameters
ini File Parameter
Name
ECHybridLoss
Valid Range and Description
0 = 6 dB (default)
1 = 9 dB
2 = 0 dB
3 = 3 dB
Sets the four wire to two wire worst case Hybrid loss, the ratio between the signal level sent
to the hybrid and the echo level returning from the hybrid.
FaxModemRelayVolume -18 to -3, corresponding to -18 dBm to -3 dBm in 1 dB steps. (Default = -12 dBm) fax gain
control.
T38ProtectionMode
0 = Use redundancy packets for protecting T.38 fax relay stream, (default)
1 = Use Forward Error Correction (FEC) algorithm to protect T.38 fax relay stream (isn’t
implemented)
MGCPDTMFDetectionP
oint
0 = DTMF event is reported on the start of a detected DTMF digit.
1 = DTMF event is reported on the end of a detected DTMF digit (default).
The parameter is used for out-of-band dialing (using SIP INFO messages).
DTMFDigitLength
Time in msec for generating DTMF tones to the PSTN side (if received in INFO).
The default value is 100 msec.
DTMFInterDigitInterval
Time in msec between generated DTMFs to PSTN side (if received in INFO).
The default value is = 100 msec.
TestMode
0 = CoderLoopback, encoder-decoder loopback inside DSP.
1 = PCMLoopback, loopback the incoming PCM to the outgoing PCM.
2 = ToneInjection, generates a 1000 Hz tone to outgoing PCM.
3 = NoLoopback, (default).
ModemBypassPayloadT Modem Bypass dynamic payload type (range 0-127).
ype
The default value is 103.
DetFaxOnAnswerTone
0 = Starts T.38 procedure on detection of V.21 preamble (default).
1 = Starts T.38 Procedure on detection of CED fax answering tone.
FaxModemBypassBasic 0 = set internally (default)
RtpPacketInterval
1 = 5 msec
2 = 10 msec
3 = 20 msec
NSEMode
Cisco compatible fax and modem bypass mode
0 = NSE disabled (default)
1 = NSE enabled
Note 1: This feature can be used only if VxxModemTransportType=2 (Bypass)
Note 2: If NSE mode is enabled the SDP contains the following line:
“a=rtpmap:100 X-NSE/8000”
Note 3: To use this feature:
• The Cisco gateway must include the following definition: "modem passthrough nse
payload-type 100 codec g711alaw".
• Set the Modem transport type to Bypass mode (‘VxxModemTransportType = 2’) for all
modems.
• Configure the gateway parameter NSEPayloadType= 100
In NSE bypass mode the gateway starts using G.711 A-Law (default) or G.711µ-Law,
according to the parameter ‘FaxModemBypassCoderType’. The payload type used with
these G.711 coders is a standard one (8 for G.711 A-Law and 0 for G.711 µ-Law). The
parameters defining payload type for the “old” AudioCodes’ Bypass mode.
‘FaxBypassPayloadType’ and ‘ModemBypassPayloadType’ are not used with NSE Bypass.
The bypass packet interval is selected according to the parameter
‘FaxModemBypassBasicRtpPacketInterval’.
NSEPayloadType
NSE payload type for Cisco Bypass compatible mode.
The valid range is 96-127. The default value is 105.
Note: Cisco gateways usually use NSE payload type of 100.
Version 4.4
119
March 2005
MP-1xx SIP
Table 5-35: Channel Settings, ini File Parameters
ini File Parameter
Name
IsCiscoSCEMode
5.9.2.1
Valid Range and Description
0 = There isn’t a Cisco gateway at the remote side (default).
1 = There is a Cisco gateway at the remote side.
When there is a Cisco gateway at the remote side, the local gateway must set the value of
the “annexb” parameter of the fmtp attribute in the SDP to “no”. This logic should be used if
‘EnableSilenceCompression = 2’ (enable without adaptation). In this case, Silence
Suppression should be used on the channel but not declared in the SDP.
Dynamic Jitter Buffer Operation
Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate,
voice quality is perceived as good. In many cases, however, some frames can arrive slightly
faster or slower than the other frames. This is called jitter (delay variation), and degrades the
perceived voice quality. To minimize this problem, the gateway uses a jitter buffer. The jitter
buffer collects voice packets, stores them and sends them to the voice processor in evenly
spaced intervals.
The MP-1xx uses a dynamic jitter buffer that can be configured using two parameters:
•
Minimum delay, ‘DJBufMinDelay’ (0 msec to 150 msec). Defines the starting jitter capacity of
the buffer. For example, at 0 msec, there is no buffering at the start. At the default level of 70
msec, the gateway always buffers incoming packets by at least 70 msec worth of voice
frames.
•
Optimization Factor, ‘DJBufOptFactor’ (0 to 12, 13). Defines how the jitter buffer tracks to
changing network conditions. When set at its maximum value of 12, the dynamic buffer
aggressively tracks changes in delay (based on packet loss statistics) to increase the size of
the buffer and doesn’t decays back down. This results in the best packet error performance,
but at the cost of extra delay. At the minimum value of 0, the buffer tracks delays only to
compensate for clock drift and quickly decays back to the minimum level. This optimizes the
delay performance but at the expense of a higher error rate.
The default settings of 70 msec Minimum delay and 7 Optimization Factor should provide a good
compromise between delay and error rate. The jitter buffer "holds" incoming packets for 70 msec
before making them available for decoding into voice. The coder polls frames from the buffer at
regular intervals in order to produce continuous speech. As long as delays in the network do not
change (jitter) by more than 70 msec from one packet to the next, there is always a sample in the
buffer for the coder to use. If there is more than 70 msec of delay at any time during the call, the
packet arrives too late. The coder tries to access a frame and is not able to find one. The coder
must produce a voice sample even if a frame is not available. It therefore compensates for the
missing packet by adding a Bad-Frame-Interpolation (BFI) packet. This loss is then flagged as the
buffer being too small. The dynamic algorithm then causes the size of the buffer to increase for
the next voice session. The size of the buffer may decrease again if the gateway notices that the
buffer is not filling up as much as expected. At no time does the buffer decrease to less than the
minimum size configured by the Minimum delay parameter.
Special Optimization Factor Value: 13
One of the purposes of the Jitter Buffer mechanism is to compensate for clock drift. If the two
sides of the VoIP call are not synchronized to the same clock source, one RTP source generates
packets at a lower rate, causing under-runs at the remote Jitter Buffer. In normal operation
(optimization factor 0 to 12), the Jitter Buffer mechanism detects and compensates for the clock
drift by occasionally dropping a voice packet or by adding a BFI packet.
Fax and modem devices are sensitive to small packet losses or to added BFI packets. Therefore
to achieve better performance during modem and fax calls, the Optimization Factor should be set
to 13. In this special mode the clock drift correction is performed less frequently - only when the
Jitter Buffer is completely empty or completely full. When such condition occurs, the correction is
performed by dropping several voice packets simultaneously or by adding several BFI packets
simultaneously, so that the Jitter Buffer returns to its normal condition.
MP-1xx SIP User’s Manual
120
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.9.3
5. Configuring the MP-1xx
Restoring and Backing up the Gateway Configuration
The Configuration File screen enables you to restore (load a new ini file to the gateway) or to
back up (make a copy of the VoIP gateway ini file and store it in a directory on your computer) the
current configuration the gateway is using.
Back up your configuration if you want to protect your VoIP gateway programming. The backup
ini file includes only those parameters that were modified and contain other than default values.
Restore your configuration if the VoIP gateway has been replaced or has lost its programming
information, you can restore the VoIP gateway configuration from a previous backup or from a
newly created ini file. To restore the VoIP gateway configuration from a previous backup you
must have a backup of the VoIP gateway information stored on your computer.
To restore or back up the ini file:
•
Open the ‘Configuration File’ screen (Advanced Configuration menu > Configuration
File); the ‘Configuration File’ screen is displayed.
Figure 5-33: Configuration File Screen
To back up the ini file, take these 4 steps:
1.
Click the Get ini File button; the ‘File Download’ window opens.
2.
Click the Save button; the ‘Save As’ window opens.
3.
Navigate to the folder where you want to save the ini file.
4.
Click the Save button; the VoIP gateway copies the ini file into the folder you selected.
To restore the ini file, take these 4 steps:
1.
Click the Browse button.
2.
Navigate to the folder that contains the ini file you want to load.
3.
Click the file and click the Open button; the name and path of the file appear in the field
beside the Browse button.
4.
Click the Send ini File button, and click OK in the prompt; the gateway is automatically reset
(from the cmp version stored on the flash memory).
Version 4.4
121
March 2005
MP-1xx SIP
5.9.4
Regional Settings
The ‘Regional Settings’ screen enables you to set and view the gateway’s internal date and time
and to load to the gateway the following configuration files: Call Progress Tones, coefficient
(different files for MP-1xx/FXS and MP-10x/FXO gateways) and Voice Prompts (currently not
applicable to MP-1xx gateways). For detailed information on the configuration files refer to
Section 6 on page 141.
To configure the date and time of the MP-1xx, take these 3 steps:
1.
Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional
Settings); the ‘Regional Settings' screen is displayed.
Figure 5-34: Regional Settings Screen
2.
Enter the time and date where the gateway is installed.
3.
Click the Set Date & Time button; the date and time are automatically updated.
Note that after performing a hardware reset, the date and time are returned to their defaults and
should be updated.
To load a configuration file to the VoIP gateway, take these 8 steps:
1.
Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional
Settings); the ‘Regional Settings’ screen is displayed (shown in Figure 5-34).
2.
Click the Browse button adjacent to the file you want to load.
3.
Navigate to the folder that contains the file you want to load.
4.
Click the file and click the Open button; the name and path of the file appear in the field
beside the Browse button.
5.
Click the Send File button that is next to the field that contains the name of the file you want
to load. An exclamation mark in the screen section indicates that the file’s loading doesn’t
take effect on-the-fly (e.g., CPT file).
6.
Repeat steps 2 to 5 for each file you want to load.
MP-1xx SIP User’s Manual
122
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5.9.5
5. Configuring the MP-1xx
Note 1:
Saving a configuration file to flash memory may disrupt traffic on the MP-1xx.
To avoid this, disable all traffic on the device before saving to flash memory.
Note 2:
A device reset is required to activate a loaded CPT file.
7.
To save the loaded auxiliary files so they are available after a power fail refer to Section 5.12
on page 139.
8.
To reset the MP-1xx refer to Section 5.12 on page 139.
Changing the MP-1xx Username and Password
To prevent unauthorized access to the MP-1xx, it is recommended that you change the username
and password (both are case-sensitive) that are used to access the Web Interface.
To change the username and password, take these 5 steps:
1.
Open the ‘Change Password’ screen (Advanced Configuration menu > Change
Password); the ‘Change Password’ screen is displayed.
Figure 5-35: Change Password Screen
2.
In the ‘User Name’ and ‘Password’ fields, enter the new username and the new password
respectively. Note that the username and password can be a maximum of 7 case-sensitive
characters.
3.
In the ‘Confirm Password’ field, reenter the new password.
4.
Click the Change Password button; the new username and password are applied and the
‘Enter Network Password’ screen appears, shown in Figure 5-1 on page 41.
5.
Enter the updated username and password in the ‘Enter Network Password’ screen.
Version 4.4
123
March 2005
MP-1xx SIP
5.10 Status & Diagnostics
Use this subdivided menu to view and monitor the gateway’s channels, Syslog messages,
hardware / software product information, and to assess the gateway’s statistics and IP
connectivity information.
5.10.1 Gateway Statistics
Use the screens under Gateway Statistics to monitor real-time activity such as IP Connectivity
information, call details and call statistics, including the number of call attempts, failed calls, fax
calls, etc.
Note: The Gateway Statistics screens doesn’t refresh automatically. To view updated information
re-access the screen you require.
5.10.1.1 IP Connectivity
The IP Connectivity screen provides you with an online read-only network diagnostic connectivity
information on all destination IP addresses configured in the Tel to IP Routing table.
Note: This information is available only if the parameter ‘AltRoutingTel2IPEnable’ (described in
Table 5-10) is set to 1 (Enable) or 2 (Status Only).
Note:
The information in columns ‘Quality Status’ and ‘Quality Info.’ (per IP
address) is reset if two minutes elapse without a call to that destination.
To view the IP connectivity information, take these 2 steps:
1.
Set ‘AltRoutingTel2IPEnable’ to 1 or 2.
2.
Open the ‘IP Connectivity’ screen (Status & Diagnostics menu > Gateway Statistics
submenu > IP Connectivity); the ‘IP Connectivity’ screen is displayed (Figure 5-36).
Figure 5-36: IP Connectivity Screen
MP-1xx SIP User’s Manual
124
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-36: IP Connectivity Parameters
Column Name
Description
IP Address
IP address defined in the destination IP address field in the Tel to IP Routing table.
or
IP address that is resolved from the host name defined in the destination IP address field in
the Tel to IP Routing table.
Host Name
Host name (or IP address) defined in the destination IP address field in the Tel to IP Routing
table.
Connectivity Method
The method according to which the destination IP address is queried periodically (currently
only by ping).
Connectivity Status
Displays the status of the IP address’ connectivity according to the method in the ‘Connectivity
Method’ field.
Can be one of the following:
• OK
= Remote side responds to periodic connectivity queries.
• Lost
= Remote side didn’t respond for a short period.
• Fail
= Remote side doesn’t respond.
• Init
= Connectivity queries not started (e.g., IP address not resolved).
• Disable = The connectivity option is disabled (‘AltRoutingTel2IPMode’ equals 0 or 2).
Quality Status
Determines the QoS (according to packet loss and delay) of the IP address.
Can be one of the following:
• Unknown = Recent quality information isn’t available.
• OK
• Poor
Note 1: This field is applicable only if the parameter ‘AltRoutingTel2IPMode’ is set to 2 or 3.
Note 2: This field is reset if no QoS information is received for 2 minutes.
Quality Info.
Displays QoS information: delay and packet loss, calculated according to previous calls.
Note 1: This field is applicable only if the parameter ‘AltRoutingTel2IPMode’ is set to 2 or 3.
Note 2: This field is reset if no QoS information is received for 2 minutes.
DNS Status
Can be one of the following:
• DNS Disable
• DNS Resolved
• DNS Unresolved
5.10.1.2 Call Counters
The Call Counters screens provide you with statistic information on incoming (IP Tel) and
outgoing (Tel IP) calls. The statistic information is updated according to the release reason that
is received after a call is terminated (during the same time as the end-of-call CDR message is
sent). The release reason can be viewed in the Termination Reason field in the CDR message.
For detailed information on each counter, refer to Table 5-37 on page 126.
You can reset this information by clicking the Reset Counters button.
To view the IP Tel and Tel IP Call Counters information:
•
Version 4.4
Open the Call Counters screen you want to view (Status & Diagnostics menu > Gateway
Statistics submenu); the relevant Call Counters screen is displayed. Figure 5-37 shows the
‘Tel IP Call Counters’ screen.
125
March 2005
MP-1xx SIP
Figure 5-37: Tel IP Call Counters Screen
Table 5-37: Call Counters Description (continues on pages 126 to 127)
Counter
Number of Attempted
Calls
Description
This counter indicates the number of attempted calls.
It is composed of established and failed calls. The number of established calls is
represented by the ‘Number of Established Calls’ counter. The number of failed
calls is represented by the five failed-call counters. Only one of the established /
failed call counters is incremented every time.
This counter indicates the number of established calls. It is incremented as a result
of one of the following release reasons, if the duration of the call is bigger then
zero:
GWAPP_REASON_NOT_RELEVANT (0)
GWAPP_NORMAL_CALL_CLEAR (16)
GWAPP_NORMAL_UNSPECIFIED (31)
And the internal reasons:
Number of Established RELEASE_BECAUSE_UNKNOWN_REASON
Calls
RELEASE_BECAUSE_REMOTE_CANCEL_CALL
RELEASE_BECAUSE_MANUAL_DISC
RELEASE_BECAUSE_SILENCE_DISC
RELEASE_BECAUSE_DISCONNECT_CODE
Note: When the duration of the call is zero, the release reason
GWAPP_NORMAL_CALL_CLEAR increments the ‘Number of Failed Calls due to
No Answer’ counter. The rest of the release reasons increment the ‘Number of
Failed Calls due to Other Failures’ counter.
This counter indicates the number of calls that failed as a result of a busy line. It is
Number of Failed Calls
incremented as a result of the following release reason:
due to a Busy Line
GWAPP_USER_BUSY (17)
This counter indicates the number of calls that weren’t answered. It is incremented
as a result of one of the following release reasons:
GWAPP_NO_USER_RESPONDING (18)
Number of Failed Calls GWAPP_NO_ANSWER_FROM_USER_ALERTED (19)
due to No Answer
And (when the call duration is zero) as a result of the following:
GWAPP_NORMAL_CALL_CLEAR (16)
RELEASE_BECAUSE_NORMAL_CALL_DROP (internal)
This counter indicates the number of calls whose destinations weren’t found. It is
Number of Failed Calls incremented as a result of one of the following release reasons:
due to No Route
GWAPP_UNASSIGNED_NUMBER (1)
GWAPP_NO_ROUTE_TO_DESTINATION (3)
MP-1xx SIP User’s Manual
126
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Table 5-37: Call Counters Description (continues on pages 126 to 127)
Counter
Description
This counter indicates the number of calls that failed due to mismatched gateway
Number of Failed Calls capabilities. It is incremented as a result of an internal identification of capability
due to No Matched
mismatch. This mismatch is reflected to CDR via the value of the parameter
Capabilities
‘DefaultReleaseReason’ (default is GWAPP_NO_ROUTE_TO_DESTINATION (3)),
or by the GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED(79) reason.
Number of Failed Calls This counter is incremented as a result of calls that fail due to reasons not covered
due to Other Failures by the other counters.
Percentage of
Successful Calls
The percentage of established calls from attempted calls.
Average Call Duration
The average call duration of established calls.
[sec]
Attempted Fax Calls
Counter
This counter indicates the number of attempted fax calls.
Successful Fax Calls
Counter
This counter indicates the number of successful fax calls.
5.10.2 Monitoring the MP-1xx Channels
The Channel Status screen provides real time monitoring on the current channels status.
To monitor the status of the MP-1xx channels take this step:
•
Open the ‘Channel Status’ screen (Status & Diagnostics menu > Channel Status); the
‘Channel Status’ screen is displayed (different screen for FXS and FXO).
Figure 5-38: MP-1xx/FXS Channel Status Screen
The color of each channel shows the call status of that channel.
•
Not Connected (FXO only) - indicates that no analog line is connected to this port.
•
Inactive - indicates this channel is currently onhook.
Version 4.4
127
March 2005
MP-1xx SIP
•
Handset Offhook - indicates this channel is offhook but there is no active RTP session.
•
RTP Active - indicates an active RTP stream.
To monitor the details of a specific channel, take these 2 steps:
1.
Click the numbered icon of the specific channel whose detailed status you need to
check/monitor; the channel-specific Channel Status screen appears, shown in Figure 5-39.
2.
Click the submenu links to check/view a specific channel’s parameter settings.
Figure 5-39: Channel Status Details Screen
MP-1xx SIP User’s Manual
128
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
5.10.3 Activating the Internal Syslog Viewer
The Message Log screen displays Syslog debug messages sent by the gateway.
Note that it is not recommended to keep a ‘Message Log’ session open for a prolonged period
(refer to the Note below). For prolong debugging use an external Syslog server, refer to Section
9.2.2 on page 170.
Refer to the Debug Level parameter ‘GwDebugLevel’ (described in Table 5-5) to determine the
Syslog logging level.
To activate the Message Log, take these 4 steps:
1.
In the General Parameters screen under Advanced Parameters submenu (accessed from
the Protocol Management menu), set the parameter ‘Debug Level’ to 5. This parameter
determines the Syslog logging level, in the range 0 to 5, where 5 is the highest level.
2.
Open the ‘Message Log’ screen (Status & Diagnostics menu > Message Log); the
‘Message Log’ screen is displayed.
Figure 5-40: Message Log Screen
3.
Select the messages, copy them and paste them into a text editor such as Notepad. Send
this txt file to our Technical Support for diagnosis and troubleshooting.
4.
To clear the screen of messages, click on the submenu Message Log; the screen is cleared
and new messages begin appearing.
Tip:
Version 4.4
Do not keep the ‘Message Log’ screen minimized for a prolonged period as
a prolonged session may cause the MP-1xx to overload. As long as the
screen is open (even if minimized), a session is in progress and messages
are sent. Closing the screen (and accessing another) stops the messages
and terminates the session.
129
March 2005
MP-1xx SIP
5.10.4 System Information
The System Information screen displays specific hardware and software product information. This
information can help you to expedite any troubleshooting process. Capture the screen and email
it to ‘our’ Technical Support personnel to ensure quick diagnosis and effective corrective action.
From this screen you can also view and remove any loaded auxiliary files used by the MP-1xx
(stored in the RAM).
To access the System Information screen:
•
Open the ‘System Information’ screen (Status & Diagnostics menu > System
Information); the ‘System Information’ screen is displayed.
Figure 5-41: System Information Screen
To delete any of the loaded auxiliary files, take these 3 steps:
1.
Press the Delete button to the right of the files you want to delete. Deleting a file takes effect
only after the MP-1xx is reset.
2.
Click the Reset button on the main menu bar; the Reset screen is displayed.
3.
Select the Burn option and click the Reset button. The MP-1xx is reset and the auxiliary files
you chose to delete are discarded.
MP-1xx SIP User’s Manual
130
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
5.11 Software Update
The ‘Software Update’ menu enables users to upgrade the MP-1xx software by loading a new
cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files.
The ‘Software Update’ menu comprises two submenus:
•
Software Update Wizard (refer to Section 5.11.1 below).
•
Auxiliary Files (refer to Section 5.11.2 on page 137).
Note:
When upgrading the MP-1xx software you must load the new cmp file with
all other related configuration files.
5.11.1 Software Upgrade Wizard
The Software Upgrade Wizard guides users through the process of software upgrade: selecting
files and loading them to the gateway. The wizard also enables users to upgrade software while
maintaining the existing configuration. Using the wizard obligates users to load a cmp file. Users
can choose to also use the Wizard to load the ini and auxiliary files (e.g., Call Progress Tones)
but this option cannot be pursued without loading the cmp file. For the ini and each auxiliary file
type, users can choose to reload an existing file, load a new file or not load a file at all.
Note:
The Software Upgrade Wizard requires the MP-1xx to be reset at the end of
the process, disrupting any of its traffic. To avoid disruption, disable all traffic
on the MP-1xx before initiating the Wizard.
To use the Software Upgrade Wizard, take these 9 steps:
1.
Stop all traffic on the MP-1xx (refer to the note above).
2.
Open the ‘Software Upgrade Wizard’ (Software Update menu > Software Upgrade
Wizard); the ‘Start Software Upgrade’ screen appears.
Figure 5-42: Start Software Upgrade Screen
Version 4.4
131
March 2005
MP-1xx SIP
Note:
3.
At this point, the process can be canceled with no consequence to the MP1xx (click the Cancel button). If you continue the process (by clicking the
Start Software Upgrade button, the process must be followed through and
completed with a MP-1xx reset at the end. If you click the Cancel button in
any of the subsequent screens, the MP-1xx is automatically reset with the
configuration that was previously burned in flash memory.
Click the Start Software Upgrade button; the ‘Load a cmp file’ screen appears (Figure
5-43).
Note:
When in the Wizard process, the rest of the Web application is unavailable
and the background Web screen is disabled. After the process is completed,
access to the full Web application is restored.
Figure 5-43: Load a cmp File Screen
4.
Click the Browse button, navigate to the cmp file and click the button Send File; the cmp file
is loaded to the MP-1xx and you’re notified as to a successful loading (refer to Figure 5-44).
MP-1xx SIP User’s Manual
132
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Figure 5-44: cmp File Successfully Loaded into the MP-1xx Notification
5.
Note that the four action buttons (Cancel, Reset, Back, and Next) are now activated
(following cmp file loading).
You can now choose to either:
Click Reset; the MP-1xx resets, utilizing the new cmp you loaded and utilizing the
current configuration files.
Click Cancel; the MP-1xx resets utilizing the cmp, ini and all other configuration files that
were previously stored in flash memory. Note that these are NOT the files you loaded in
the previous Wizard steps.
Click Back; the ‘Load a cmp File’ screen is reverted to; refer to Figure 5-43.
Click Next; the ‘Load an ini File’ screen opens; refer to Figure 5-45. Loading a new ini
file or any other auxiliary file listed in the Wizard is optional.
Note that as you progress, the file type list on the left indicates which file type loading is in
process by illuminating green (until ‘FINISH’).
Version 4.4
133
March 2005
MP-1xx SIP
Figure 5-45: Load an ini File Screen
6.
In the ‘Load an ini File’ screen, you can now choose to either:
Click Browse and navigate to the ini file; the check box ‘Use existing configuration’, by
default checked, becomes unchecked. Click Send File; the ini file is loaded to the MP1xx and you’re notified as to a successful loading.
Ignore the Browse button (its field remains undefined and the check box ‘Use existing
configuration’ remains checked by default).
Ignore the Browse button and uncheck the ‘Use existing configuration’ check box; no ini
file is loaded, the MP-1xx uses its factory-preconfigured values.
You can now choose to either:
Click Cancel; the MP-1xx resets utilizing the cmp, ini and all other configuration files
that were previously stored in flash memory. Note that these are NOT the files you
loaded in the previous Wizard steps.
Click Reset; the MP-1xx resets, utilizing the new cmp and ini file you loaded up to now
as well as utilizing the other configuration files.
Click Back; the ‘Load a cmp file’ screen is reverted to; refer to Figure 5-43.
Click Next; the ‘Load a CPT File’ screen opens, refer to Figure 5-46; Loading a new
CPT file or any other auxiliary file listed in the Wizard is optional.
MP-1xx SIP User’s Manual
134
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
Figure 5-46: Load a CPT File Screen
7.
Follow the same procedure you followed when loading the ini file (refer to Step 6). The same
procedure applies to the ‘Load a VP file’ (not applicable to the MP-1xx gateway) screen and
‘Load a coefficient file’ screen.
8.
In the ‘FINISH’ screen (refer to Figure 5-47), the Next button is disabled. Complete the
upgrade process by clicking Reset or Cancel.
Button
Result
Reset
The MP-1xx ‘burns’ the newly loaded files to flash memory. The ‘Burning files to flash
memory’ screen appears. Wait for the ‘burn’ to finish. When it finishes, the ‘End Process’
screen appears displaying the burned configuration files (refer to Figure 5-48).
Cancel
The MP-1xx resets, utilizing the files previously stored in flash memory. (Note that these
are NOT the files you loaded in the previous Wizard steps).
Version 4.4
135
March 2005
MP-1xx SIP
Figure 5-47: FINISH Screen
Figure 5-48: ‘End Process’ Screen
9.
Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application
is reactivated.
MP-1xx SIP User’s Manual
136
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
5.11.2 Auxiliary Files
The ‘Auxiliary Files’ screen enables you to load to the gateway the following files: Call Progress
Tones, coefficient and Prerecorded Tones (PRT). The Voice Prompts file is currently not
applicable to the MP-1xx. For detailed information on these files refer to Section 6 on page 141.
For information on deleting these files from the MP-1xx refer to Section 5.10.4 on page 130.
Table 5-38 presents a brief description of each auxiliary file.
Table 5-38: Auxiliary Files Descriptions
File Type
Description
Coefficient
This file (different file for FXS and FXO gateways) contains the telephony interface configuration
information for the VoIP gateway. This information includes telephony interface characteristics,
such as DC and AC impedance, feeding current and ringing voltage. This file is specific to the
type of telephony interface that the VoIP gateway supports. In most cases you have to load this
type of file.
Call Progress Tones This is a region-specific, telephone exchange-dependent file that contains the Call Progress
Tones levels and frequencies that the VoIP gateway uses. The default CPT file is: U.S.A.
Prerecorded Tones
The dat PRT file enhances the gateway’s capabilities of playing a wide range of telephone
exchange tones that cannot be defined in the Call Progress Tones file.
To load an auxiliary file to the gateway, take these 8 steps:
1.
Open the ‘Auxiliary Files’ screen (Software Upgrade menu > Load Auxiliary Files); the
‘Auxiliary Files’ screen is displayed.
2.
Click the Browse button that is in the field for the type of file you want to load.
3.
Navigate to the folder that contains the file you want to load.
4.
Click the file and click the Open button; the name and path of the file appear in the field
beside the Browse button.
5.
Click the Send File button that is next to the field that contains the name of the file you want
to load. An exclamation mark in the screen section indicates that the file’s loading doesn’t
take effect on-the-fly (e.g., CPT file).
6.
Repeat steps 2 to 5 for each file you want to load.
Note 1:
Saving an auxiliary file to flash memory may disrupt traffic on the MP-1xx. To
avoid this, disable all traffic on the device before saving to flash memory.
Note 2:
A MP-1xx reset is required to activate a loaded CPT file, and may be
required for the activation of certain ini file parameters.
7.
To save the loaded auxiliary files so they are available after a power fail refer to Section 5.12
on page 139.
8.
To reset the MP-1xx refer to Section 5.12 on page 139.
Version 4.4
137
March 2005
MP-1xx SIP
Figure 5-49: Auxiliary Files Screen
5.11.2.1 Loading the Auxiliary Files via the ini File
To load the auxiliary files via the ini file, take these 3 steps:
1.
In the ini file, define the auxiliary files to be loaded to the MP-1xx. You can also define in the
ini file whether the loaded files should be stored in the non-volatile memory so that the TFTP
process is not required every time the MP-1xx boots up.
2.
Locate the auxiliary files you want to load and the ini file in the same directory.
3.
Invoke a BootP/TFTP session; the ini and auxiliary files are loaded onto the MP-1xx.
Table 5-39 below describes the ini file parameters that are associated with the configuration files.
Table 5-39: Configuration Files ini File Parameters
ini File Parameter Name
Description
CallProgressTonesFileName
The name (and path) of the file containing the Call Progress Tones
definition.
FXSLoopCharacteristicsFileName
The name (and path) of the file providing the FXS line characteristic
parameters.
FXOLoopCharacteristicsFileName
The name (and path) of the file providing the FXO line characteristic
parameters.
PrerecordedTonesFileName
The name (and path) of the file containing the Prerecorded Tones.
SaveConfiguration
Set to 1 to store the Call Progress Tones, PRT and coefficient files in the
non-volatile memory.
MP-1xx SIP User’s Manual
138
Document #: LTRT-65404
MP-1xx SIP User’s Manual
5. Configuring the MP-1xx
5.12 Save Configuration
The Save Configuration screen enables users to save the current parameter configuration and
the loaded auxiliary files to the non-volatile memory so they are available after a power fail.
Parameters that are only saved to the volatile memory revert to their previous settings after
hardware reset.
Note that when performing a software reset (i.e., via Web or SNMP) you can choose to save the
changes to the non-volatile memory. Therefore, there is no need to use the Save Configuration
screen.
Note:
Saving changes to the non-volatile memory may disrupt traffic on the gateway.
To avoid this, disable all traffic before saving.
To save the changes to the non-volatile, take these 2 steps:
1.
Click the Save Configuration button on the main menu bar; the ‘Save Configuration’ screen
is displayed.
Figure 5-50: Save Configuration Screen
2.
Version 4.4
Click the Save Configuration button in the middle of the screen; a confirmation message
appears when the save is complete.
139
March 2005
MP-1xx SIP
5.13 Resetting the MP-1xx
The Reset screen enables you to remotely reset the gateway. Before reset you can choose to
save the gateway configuration to flash memory.
To reset the MP-1xx, take these 3 steps:
1.
Click the Reset button on the main menu bar; the Reset screen is displayed.
Figure 5-51: Reset Screen
2.
Select one of the following options:
Burn - (default) the current configuration is burned to flash prior to reset.
Don’t Burn - resets the MP-1xx without burning the current configuration to flash
(discards all modifications to the configuration).
3.
Click the Reset button. If the Burn option is selected, all configuration changes are saved to
flash memory. If the Don’t Burn option is selected, all configuration changes are discarded.
The MP-1xx is shut down and re-activated. A message about the waiting period is displayed.
The screen is refreshed.
MP-1xx SIP User’s Manual
140
Document #: LTRT-65404
MP-1xx SIP User’s Manual
6
6. ini File Configuration of the MP-1xx
ini File Configuration of the MP-1xx
As an alternative to configuring the VoIP gateway using the Web Interface (refer to Section 5 on
page 39), it can be configured by loading the ini file containing Customer-configured parameters.
The ini file is loaded via the BootP/TFTP utility (refer to Appendix B on page 197) or via any
standard TFTP server. It can also be loaded through the Web Interface (refer to Section 5.9.2.1
on page 120).
The ini file configuration parameters are stored in the MP-1xx non-volatile memory after the file is
loaded. When a parameter is missing from the ini file, a default value is assigned to that
parameter (according to the cmp file loaded on the MP-1xx) and stored in the non-volatile
memory (thereby overriding the value previously defined for that parameter). Therefore, to restore
the default configuration parameters, use the ini file without any valid parameters or with a
semicolon (;) preceding all lines in the file.
Some of the MP-1xx parameters are configurable through the ini file only (and not via the Web).
These parameters usually determine a low-level functionality and are seldom changed for a
specific application.
Note:
6.1
For detailed explanation of each parameter, refer to Section 5 on page 39.
Secured ini File
The ini file contains sensitive information that is required for the functioning of the MP-1xx. It is
loaded to, or retrieved from, the device via TFTP or HTTP. These protocols are unsecured and
vulnerable to potential hackers. Therefore an encoded ini file significantly reduces these threats.
You can choose to load an encoded ini file to the MP-1xx. When you load an encoded ini file, the
retrieved ini file is also encoded. Use the ‘TrunkPack Downloadable Conversion Utility’ to encode
or decode the ini file before you load it to, or retrieve it from the device. Note that the encoded ini
file’s loading procedure is identical to the regular ini file’s loading procedure. For information on
encoding / decoding an ini file refer to Section F.1.2 on page 221.
6.2
Modifying an ini File
To modify the ini file, take these 3 steps:
1.
Get the ini file from the gateway using the Embedded Web Server (refer to Section 5.9.2.1
on page 120).
2.
Open the file (the file is open in Notepad or a Customer-defined text file editor) and modify
the ini file parameters according to your requirements; save and close the file.
3.
Load the modified ini file to the gateway (using either BootP/TFTP utility or the Embedded
Web Server).
This method preserves the programming that already exists in the device, including special
default values that were preconfigured when the unit was manufactured.
Tip:
Version 4.4
Before loading the ini file to the gateway, verify that the extension of the ini
file saved on your PC is correct: Verify that the check box ‘Hide file
extension for known file types’ (My computer>Tools>Folder Options>View)
is unchecked. Then, confirm that the ini file name extension is xxx.ini and
NOT erroneously xxx.ini.ini or xxx~.ini.
141
March 2005
MP-1xx SIP
6.3
The ini File Structure
The ini file can contain any number of parameters. The parameters are divided into groups by
their functionality. The general form of the ini file is shown in Figure 6-1 below.
Figure 6-1: ini File Structure
[Sub Section Name]
Parameter_Name = Parameter_Value
Parameter_Name = Parameter_Value
; REMARK
[Sub Section Name]
6.3.1
6.3.2
The ini File Structure Rules
•
Lines beginning with a semi-colon ‘;’ (as the first character) are ignored.
•
A Carriage Return must be the final character of each line.
•
The number of spaces before and after "=" is not relevant.
•
If there is a syntax error in the parameter name, the value is ignored.
•
Syntax errors in the parameter value field can cause unexpected errors (because
parameters may be set to the wrong values).
•
Sub-section names are optional.
•
String parameters, representing file names, for example CallProgressTonesFileName, must
be placed between two inverted commas (‘…’).
•
The parameter name is NOT case-sensitive; the parameter value is not case-sensitive
except for coder names.
•
The ini file should be ended with one or more carriage returns.
The ini File Example
Figure 6-2 shows an example of an ini file for the VoIP gateway.
Figure 6-2: SIP ini File Example
[Channel Params]
DJBufferMinDelay = 75
RTPRedundancyDepth = 1
DefaultNumber = 101
MaxDigits = 3
CoderName = g7231,90
; Phone of each endpoint
Channel2Phone = 0, 101
Channel2Phone = 1, 102
Channel2Phone = 2, 103
Channel2Phone = 3, 104
EnableSyslog = 0
[Files]
CallProgressTonesFilename = 'CPUSA.dat'
FXSLoopCharacteristicsFileName = 'coeff.dat'
SaveConfiguration = 1
MP-1xx SIP User’s Manual
142
Document #: LTRT-65404
MP-1xx SIP User’s Manual
7
7. Configuration Files
Configuration Files
This section describes the configuration dat files that are loaded (in addition to the ini file) to the
gateway. The configuration files are:
•
Call Progress Tones file (refer to Section 7.1 on page 143).
•
Prerecorded Tones file (refer to Section 7.2 on page 147).
•
FXS/FXO Coefficient files (refer to Section 7.3 on page 148).
To load either of the configuration files to the MP-1xx use the Embedded Web Server (refer to
Section 5.11.2 on page 137) or alternatively specify the name of the relevant configuration file in
the gateway’s ini file and load it (the ini file) to the gateway (refer to Section 5.11.2.1 on page
138).
7.1
Configuring the Call Progress Tones and
Distinctive Ringing File
The Call Progress Tones and Distinctive Ringing, configuration file used by the MP-1xx is a
binary file (with the extension dat) that is comprised of two sections. The first section contains the
definitions of the Call Progress Tones (levels and frequencies) that are detected / generated by
the MP-1xx. The second section contains the characteristics of the distinctive ringing signals that
are generated by the MP-1xx.
Users can either use, one of the supplied MP-1xx configuration (dat) files, or construct their own
file. To construct their own configuration file, users are recommended, to modify the supplied
usa_tone.ini file (in any standard text editor) to suit their specific requirements, and to convert it
(the modified ini file) into binary format using the “TrunkPack Downloadable Conversion Utility”
supplied with the software package. For the description of the procedure on how to convert CPT
ini file to a binary dat file, refer to Section F.1.1 on page 220.
Note that only the dat file can be loaded to the MP-1xx gateway.
To load the Call Progress Tones (dat) file to the MP-1xx, use the Embedded Web Server (refer to
Section 5.9.4 on page 122) or the ini file (refer to Section 5.11.2.1 on page 138).
7.1.1
Format of the Call Progress Tones Section in the ini File
Using the CPT section of this configuration file, the User can create up to 16 different Call
Progress Tones using up to 15 different frequencies (in the range of 300 Hz to 1980 Hz). Each of
these Call Progress Tones is specified by its tone frequency (either single or dual frequencies are
supported) and its tone cadence. The tone cadence is specified by 2 sets of on/off periods (you
can discard the use of the first on/off cycle by setting the relevant parameters to zero). When a
tone is composed of a single frequency, the second frequency field must be set to zero.
For a continuous tone (such as dial tone), only the “First Signal On time” should be specified. In
this case, the parameter specifies the detection period. For example, if it equals 300, the tone is
detected after 3 seconds (300 x 10 msec). The minimum detection time is 100 msec.
Users can specify several tones of the same type. These additional tones are used only for tone
detection. Generation of a specific tone conforms to the first definition of the specific tone. For
example, Users can define an additional dial tone by appending the second dial tone’s definition
lines to the first tone definition in the ini file. The MP-1xx reports dial tone detection if either of the
two tones is detected.
The Call Progress Tones section of the ini file comprises the following segments:
•
Version 4.4
[NUMBER OF CALL PROGRESS TONES] – Contains the following key:
143
March 2005
MP-1xx SIP
“Number of Call Progress Tones” defining the number of Call Progress Tones that are
defined in the file.
•
[CALL PROGRESS TONE #X] – containing the Xth tone definition (starting from 1 and not
exceeding the number of Call Progress Tones defined in the first section) using the following
keys:
Tone Type – Call Progress Tone type
Figure 7-1: Call Progress Tone Types
- Dial Tone
2 - Ringback Tone
3 - Busy Tone
7 - Reorder Tone
8 - Confirmation Tone
9 - Call Waiting Tone
15 - Stutter Dial Tone
16 - Off Hook Warning Tone
17 - Call Waiting Ringback Tone
23 - Hold Tone
1
Low Freq [Hz] – Frequency in hertz of the lower tone component in case of dual
frequency tone, or the frequency of the tone in case of single tone.
High Freq [Hz] – Frequency in hertz of the higher tone component in case of dual
frequency tone, or zero (0) in case of single tone.
Low Freq Level [-dBm] – Generation level 0 dBm to –31 dBm in [dBm].
High Freq Level – Generation level. 0 to –31 dBm. The value should be set to ‘32’ in the
case of a single tone.
First Signal On Time [10 msec] – “Signal On” period (in 10 msec units) for the first
cadence on-off cycle.
First Signal Off Time [10 msec] – “Signal Off” period (in 10 msec units) for the first
cadence on-off cycle.
Second Signal On Time [10 msec] – “Signal On” period (in 10 msec units) for the
second cadence on-off cycle.
Second Signal Off Time [10 msec] – “Signal Off” period (in 10 msec units) for the
second cadence on-off cycle.
Default Duration [msec] - The default duration (in 1 msec units) of the generated tone.
Note 1:
When the same frequency is used for a continuous tone and a cadence
tone, the ‘Signal On Time’ parameter of the continues tone must have a
value that is greater than the ‘Signal On Time’ parameter of the cadence
tone. Otherwise the continues tone is detected instead of the cadence tone.
Note 2:
The tones frequency should differ by at least 40 Hz from one tone to other
defined tones.
For example: to configure the dial tone to 440 Hz only, define the following text:
MP-1xx SIP User’s Manual
144
Document #: LTRT-65404
MP-1xx SIP User’s Manual
7. Configuration Files
Figure 7-2: Defining a Dial Tone Example
#Dial tone
[CALL PROGRESS TONE #1]
Tone Type=1
Low Freq [Hz]=440
High Freq [Hz]=0
Low Freq Level [-dBm]=10 (-10 dBm)
High Freq Level [-dBm]=32 (use 32 only if a single tone is required)
First Signal On Time [10msec]=300; the dial tone is detected after 3 sec
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=0
Second Signal Off Time [10msec]=0
7.1.2
Format of the Distinctive Ringing Section in the ini File
Distinctive Ringing is only applicable to MP-1xx/FXS gateways. Using the distinctive ringing
section of this configuration file, the User can create up to 16 distinctive ringing patterns.
To instruct the gateway to play a different Ringing tone, append the string ‘-dr#’ (# can be 0 to 15)
to the Alert-Info header in the Invite message.
In the following examples, the MP-1xx plays the Ringing tone with ‘Ringing Pattern’ equals 2. If
the number of the ‘Ringing Pattern’ isn’t found, the default Ringing tone (0) is played.
Alert-Info: <Bellcore-dr2>
Alert-Info: http://127.0.0.1/Bellcore-dr2
Each ringing pattern configures the ringing tone frequency and up to 4 ringing cadences. The
same ringing frequency is used for all the ringing pattern cadences. The ringing frequency can be
configured in the range of 10 Hz to 200 Hz with a 5 Hz resolution. Each of the ringing pattern
cadences is specified by the following parameters:
•
Burst Ring On Time – Configures the cadence to be a burst cadence in the entire ringing
pattern. The burst relates to On time and the Off time of the same cadence. It must appear
between “First/Second/Third/Fourth” string and the “Ring On/Off Time” This cadence rings
once during the ringing pattern. Otherwise, the cadence is interpreted as cyclic: it repeats for
every ringing cycle.
•
Ring On Time - specifies the duration of the ringing signal.
•
Ring Off Time - specifies the silence period of the cadence.
The distinctive ringing section of the ini file format contains the following strings:
•
[NUMBER OF DISTINCTIVE RINGING PATTERNS] – Contains the following key:
“Number of Distinctive Ringing Patterns” defining the number of Distinctive Ringing
signals that are defined in the file.
•
[Ringing Pattern #X] – Contains the Xth ringing pattern definition (starting from 0 and not
exceeding the number of Distinctive Ringing patterns defined in the first section minus 1)
using the following keys:
Ring Type – Must be equal to the Ringing Pattern number.
Freq [Hz] – Frequency in hertz of the ringing tone.
First (Burst) Ring On Time [10 msec] – “Ring On” period (in 10 msec units) for the first
cadence on-off cycle.
First (Burst) Ring Off Time [10 msec] – “Ring Off” period (in 10 msec units) for the first
cadence on-off cycle.
Second (Burst) Ring On Time [10 msec] – “Ring On” period (in 10 msec units) for the
second cadence on-off cycle.
Second (Burst) Ring Off Time [10 msec] – “Ring Off” period (in 10 msec units) for the
second cadence on-off cycle.
Version 4.4
145
March 2005
MP-1xx SIP
Third (Burst) Ring On Time [10 msec] – “Ring On” period (in 10 msec units) for the
third cadence on-off cycle.
Third (Burst) Ring Off Time [10 msec] – “Ring Off” period (in 10 msec units) for the
third cadence on-off cycle.
Fourth (Burst) Ring On Time [10 msec] – “Ring Off” period (in 10 msec units) for the
forth cadence on-off cycle.
Fourth (Burst) Ring Off Time [10 msec] – “Ring Off” period (in 10 msec units) for the
forth cadence on-off cycle.
Note:
7.1.2.1
In SIP the distinctive ringing pattern is selected according to Alert-Info
header that is included in Invite message. For example: Alert-Info <Bellcoredr2>, or Alert-Info<http://…/Bellcore-dr2>. ‘dr2’ defines ringing pattern # 2. If
the Alert-Info header is missing, ringing pattern #1 is played.
Examples of Various Ringing Signals
Figure 7-3: Examples of Various Ringing Signals
[NUMBER OF DISTINCTIVE RINGING PATTERNS]
Number of Ringing Patterns=3
#Regular North American Ringing Pattern
[Ringing Pattern #0]
Ring Type=0
Freq [Hz]=20
First Ring On Time [10msec]=200
First Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 1
[Ringing Pattern #1]
Ring Type=1
Freq [Hz]=20
First Ring On Time [10msec]=200
First Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 2
[Ringing Pattern #2]
Ring Type=2
Freq [Hz]=20
First Ring On Time [10msec]=80
First Ring Off Time [10msec]=40
Second Ring On Time [10msec]=80
Second Ring Off Time [10msec]=400
MP-1xx SIP User’s Manual
146
Document #: LTRT-65404
MP-1xx SIP User’s Manual
7.2
7. Configuration Files
Prerecorded Tones (PRT) File
The Call Progress Tones mechanism has several limitations, such as a limited number of
predefined tones and a limited number of frequency integrations in one tone. To work around
these limitations and provide tone generation capability that is more flexible, the PRT file can be
used. If a specific prerecorded tone exists in the PRT file, it takes precedence over the same tone
that exists in the CPT file and is played instead of it.
Note that the prerecorded tones are used only for generation of tones. Detection of tones is
performed according to the CPT file.
7.2.1
PRT File Format
The PRT dat file contains a set of prerecorded tones to be played by the MP-1xx during
operation. Up to 40 tones (totaling approximately one minute) can be stored in a single file in
flash memory. The prerecorded tones (raw data PCM or L8 files) are prepared offline using
standard recording utilities (such as CoolEditTM) and combined into a single file using the
TrunkPack Downloadable Conversion utility (refer to Section F.1.3 on page 222).
The raw data files must be recorded with the following characteristics:
•
Coders:
G.711 A-law, G.711 µ-law or Linear PCM
•
Rate:
8 kHz
•
Resolution: 8-bit
•
Channels:
mono
The generated PRT file can then be loaded to the MP-1xx using the BootP/TFTP utility (refer to
Section 5.11.2.1 on page 138) or via the Embedded Web Server (Section 5.11.2 on page 137).
The prerecorded tones are played repeatedly. This enables you to record only part of the tone
and play it for the full duration. For example, if a tone has a cadence of 2 seconds on and 4
seconds off, the recorded file should contain only these 6 seconds. The PRT module repeatedly
plays this cadence for the configured duration. Similarly, a continuous tone can be played by
repeating only part of it.
Version 4.4
147
March 2005
MP-1xx SIP
7.3
The Coefficient Configuration File
The Coeff_FXS.dat and Coeff_FXO.dat files are used to provide best termination and
transmission quality adaptation for different line types for MP-1xx/FXS and MP-10x/FXO
gateways respectively. This adaptation is performed by modifying the telephony interface
characteristics (such as DC and AC impedance, feeding current and ringing voltage).
The coeff.dat configuration file is produced specifically for each market after comprehensive
performance analysis and testing, and can be modified on request. The current file supports US
line type of 600 ohm AC impedance and (for FXS) 40 V RMS ringing voltage for REN = 2.
To load the coeff.dat file to the MP-1xx use the Embedded Web Server (refer to Section 5.9.4 on
page 122) or alternatively specify the FXS/FXO coeff.dat file name in the gateway’s ini file (refer
to Section 5.11.2.1 on page 138).
The Coeff.dat file consists of a set of parameters for the signal processor of the loop interface
devices. This parameter set provides control of the following AC and DC interface parameters:
•
DC (battery) feed characteristics
•
AC impedance matching
•
Transmit gain
•
Receive gain
•
Hybrid balance
•
Frequency response in transmit and receive direction
•
Hook thresholds
•
Ringing generation and detection parameters
This means, for example, that changing impedance matching or hybrid balance doesn’t require
hardware modifications, so that a single device is able to meet requirements for different markets.
The digital design of the filters and gain stages also ensures high reliability, no drifts (over
temperature or time) and simple variations between different line types.
In future software releases, it is to be expanded to consist of different sets of line parameters,
which can be selected in the ini file, for each port.
MP-1xx SIP User’s Manual
148
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8. Gateway Capabilities Description
8
Gateway Capabilities Description
8.1
Proxy or Registrar Registration Example
The REGISTER message is sent to the Registrar’s IP address (if configured) or to the Proxy’s IP
address. The message is sent per Gateway or per Gateway endpoint according to the
“AuthenticationMode” parameter. Usually the FXS Gateways are registered per Gateway port,
while FXO Gateways send a single registration message, where Username is used instead of
phone number in From/To headers. The registration request is resent according to the parameter
‘RegistrartionTimeDivider’. For example, if ‘RegistrationTimeDivider = 70’ (%) and Registration
Expires time = 3600, the gateway resends its registration request after 3600 x 70% = 2520 sec.
The default value of ‘RegistrartionTimeDivider’ is 50%.
REGISTER sip:servername SIP/2.0
VIA: SIP/2.0/UDP 212.179.22.229;branch=z9hG4bRaC7AU234
From: <sip:101@sipgatewayname>;tag=1c29347
To: <sip:101@sipgatewayname>
Call-ID: 10453@212.179.22.229
Seq: 1 REGISTER
Expires: 3600
Contact: sip:101@212.179.22.229
Content-Length: 0
The "servername" string is defined according to the following rules:
•
The "servername" is equal to "RegistrarName" if configured. The "RegistrarName" can be
any string.
•
Otherwise, the "servername" is equal to "RegistrarIP" (either FQDN or numerical IP
address), if configured.
•
Otherwise the "servername" is equal to "ProxyName" if configured. The "ProxyName" can be
any string.
•
Otherwise the "servername" is equal to "ProxyIP" (either FQDN or numerical IP address).
The "sipgatewayname" parameter (defined in the ini file or set from the Web browser), can be
any string. Some Proxy servers require that the "sipgatewayname" (in REGISTER messages) is
set equal to the Registrar/Proxy IP address or to the Registrar/Proxy domain name.
Version 4.4
149
March 2005
MP-1xx SIP
8.2
Configuring the DTMF Transport Types
You can control the way DTMF digits are transported over the IP network to the remote endpoint.
The following five modes are supported:
1.
Using INFO message according to the Nortel IETF draft:
In this mode DTMF digits are carried to the remote side within INFO messages.
To enable this mode set:
‘Enable DTMF = Yes’ (IsDTMFUsed = 1)
‘OutofBandDTMFFormat = 1’
‘RxDTMFOption = 0’
Note that in this mode DTMF digits are erased from the audio stream (DTMFTransportType
is automatically set to 0).
2.
Using INFO message according to Cisco’s style:
In this mode DTMF digits are carried to the remote side within INFO messages.
To enable this mode set:
‘Enable DTMF = Yes’ (IsDTMFUsed = 1)
‘OutofBandDTMFFormat = 2’
‘RxDTMFOption = 0’
Note that in this mode DTMF digits are erased from the audio stream (DTMFTransportType
is automatically set to 0).
3.
Using NOTIFY messages according to <draft-mahy-sipping-signaled-digits-01.txt>:
In this mode DTMF digits are carried to the remote side using NOTIFY messages.
To enable this mode set:
‘Enable DTMF = Yes’ (IsDTMFUsed = 1)
‘OutofBandDTMFFormat = 3’
‘RxDTMFOption = 0’
Note that in this mode DTMF digits are erased from the audio stream (DTMFTransportType
is automatically set to 0).
4.
Using RFC 2833 relay with Payload type negotiation:
In this mode, DTMF digits are carried to the remote side as part of the RTP stream in
accordance with RFC 2833 standard.
To enable this mode set:
‘Enable DTMF = No’ (IsDTMFUsed = 0)
‘DTMF RFC 2833 Negotiation = Yes’ (TxDTMFOption=4)
‘RxDTMFOption = 3’
‘DTMFTransportType = 3’
Note that to set the RFC 2833 payload type with a different value (other than its default, 96)
configure the ‘RFC2833PayloadType’ parameter. The gateway negotiates the RFC 2833
payload type using local and remote SDP and sends packets using the PT from the received
SDP. The gateway expects to receive RFC 2833 packets with the same PT as configured by
the ‘RFC2833PayloadType’ parameter. The RFC 2833 packets are sent even if the remote
side didn't include the send "telephone-event" parameter in its SDP, in which case the
gateway uses the same PT for send and for receive.
5.
Sending DTMF digits (in RTP packets) as part of the audio stream (DTMF Relay is disabled):
Note that this method is normally used with G.711 coders; with other LBR coders the quality
of the DTMF digits is reduced.
To ser this mode:
‘Enable DTMF = No’ (IsDTMFUsed = 0)
MP-1xx SIP User’s Manual
150
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8. Gateway Capabilities Description
‘DTMF RFC 2833 Negotiation = No’ (TxDTMFOption=0)
‘RxDTMFOption = 0’
‘DTMFTransportType = 2’
Note 1:
The gateway is always ready to receive DTMF packets over IP, in all
possible transport modes: INFO messages, Notify and RFC 2833 (in proper
payload type) or as part of the audio stream.
Note 2:
To exclude RFC 2833 Telephony event parameter from the gateway’s SDP,
set ‘RxDTMFOption = 0’ in the ini file.
The following parameters affect the way the MP-1xx SIP handles the DTMF digits:
Table 8-1: Summary of DTMF configuration Parameters (continues on pages 151 to 152)
ini File Field Name
[Web Name]
IsDTMFUsed
[Use Out-of-Band DTMF]
Valid Range and Description
Use out-of-band signaling to relay DTMF digits.
No
[0] = DTMF digits are sent inband (default).
Yes [1] = DTMF digits are sent out-of-band according to the parameter ‘Out-of-band
DTMF format’.
Note: When out-of-band DTMF transfer is used (Enable DTMF = Yes), the parameter
‘DTMF Transport Type’ is automatically set to 0 (erase the DTMF digits from the RTP
stream).
OutOfBandDTMFFormat
The exact method to send out-of-band DTMF digits.
[1] = Sends DTMF digits according with "IETF draft-choudhuri-sip-info[Out-of-Band DTMF Format] Info (Nortel)
digit-00".
Info (Cisco)
[2] = Sends DTMF digits according with Cisco format (default).
Notify (3Com)
[3] = NOTIFY format <draft-mahy-sipping-signaled-digits-01.txt>.
Note 1: To use out-of-band DTMF, set ‘Enable DTMF = yes’ (‘IsDTMFUsed=1’).
Note 2: When using out-of-band DTMF, the “DTMFTransportType” parameter is
automatically set to 0, to erase the DTMF digits from the RTP stream.
TxDTMFOption
[DTMF RFC 2833
Negotiation]
No
[0] = No negotiation, DTMF digit is sent according to the parameters ‘DTMF
Transport Type’ and ‘RFC2833PayloadType’.
Yes [4] = Enable RFC 2833 payload type (PT) negotiation
Note 1: This parameter is applicable only if “IsDTMFUsed=0” (out-of-band DTMF is not
used).
Note 2: If enabled, the gateway:
•
•
•
Negotiates RFC 2833 payload type using local and remote SDPs.
Sends DTMF packets using RFC 2833 PT according to the PT in the received SDP.
Expects to receive RFC 2833 packets with the same PT as configured by the
“RFC2833PayloadType” parameter.
Note 3: If the remote party doesn’t include the RFC 2833 DTMF relay payload type in the
SDP, the gateway uses the same PT for send and for receive.
Note 4: If TxDTMFOption is set to 0, the RFC 2833 payload type is set according to the
parameter ‘RFC2833PayloadType’ for both transmit and receive.
RxDTMFOption
Defines the supported Receive DTMF negotiation method.
No
[0] = Don’t declare RFC 2833 Telephony-event parameter in SDP
Yes [3] = Declare RFC 2833 Telephony-event parameter in SDP (default)
The MP-1xx is designed to always be receptive to RFC 2833 DTMF relay packets.
Therefore, it is always correct to include the “Telephony-event” parameter as a default in
the SDP. However some gateways use the absence of the “telephony-event” from the
SDP to decide to send DTMF digits inband using G.711 coder, if this is the case you can
set “RxDTMFOption=0”.
Version 4.4
151
March 2005
MP-1xx SIP
Table 8-1: Summary of DTMF configuration Parameters (continues on pages 151 to 152)
ini File Field Name
[Web Name]
RFC 2833 Payload Type
[RFC2833PayloadType]
Valid Range and Description
The RFC 2833 DTMF relay dynamic payload type.
Range: 96 to 99, 106 to 127; Default = 96
The 100, 102 to 105 range is allocated for proprietary usage.
Note 1: Cisco is using payload type 101 for RFC 2833.
Note 2: When RFC 2833 payload type (PT) negotiation is used (TxDTMFOption=4), this
payload type is used for the received DTMF packets. If negotiation isn’t used, this
payload type is used for receive and for transmit.
MGCPDTMFDetectionPoin 0 = Send out-of-band DTMF message on starting point of DTMF digit
t
1 = Send DTMF message on ending point of DTMF digit (default)
DTMFDigitLength
Time in msec for generating DTMF tones to the PSTN side (if received in INFO).
The default value is 100 msec.
DTMFInterDigitInterval
Time in msec between generated DTMFs to PSTN side (if received in INFO).
The default value is = 100 msec.
DTMFVolume
[DTMF Volume]
DTMF level for regenerated digits to PSTN side (-31 to 0, corresponding to -31 dBm to 0
dBm in 1 dB steps, default = -11 dBm).
DTMFTransportType
[DTMF Transport Type]
0 = Erase digits from voice stream, do not relay to remote.
2 = Digits remain in voice stream.
3 = Erase digits from voice stream, relay to remote according to RFC 2833.
Note: This parameter is automatically updated if one of the following parameters is
configured: IsDTMFUsed, TxDTMFOption or RxDTMFOption.
8.3
Configuring the Gateway’s Alternative Routing
(based on Connectivity and QoS)
The Alternative Routing feature enables reliable routing of Tel to IP calls when a Proxy isn’t used.
The MP-1xx gateway periodically checks the availability of connectivity and suitable Quality of
Service (QoS) before routing. If the expected quality cannot be achieved, an alternative IP route
for the prefix (phone number) is selected.
8.3.1
Alternative Routing Mechanism
When a Tel IP call is routed through the MP-1xx gateway, the call’s destination number is
compared to the list of prefixes defined in the Tel to IP Routing table (described in Section 5.8.4.2
on page 75). The Tel to IP Routing table is scanned for the destination number’s prefix starting at
the top of the table. When an appropriate entry (destination number matches one of the prefixes)
is found; the prefix’s corresponding destination IP address is checked. If the destination IP
address is disallowed, an alternative route is searched for in the following table entries.
Destination IP address is disallowed if no ping to the destination is available (ping is continuously
initiated every 7 seconds), when an inappropriate level of QoS was detected, or when DNS host
name is not resolved. The QoS level is calculated according to delay or packet loss of previously
ended calls. If no call statistics are received for two minutes, the QoS information is reset.
The MP-1xx gateway matches the rules starting at the top of the table. For this reason, enter the
main IP route above any alternative route.
8.3.2
Determining the Availability of Destination IP Addresses
To determine the availability of each destination IP address (or host name) in the routing table,
one (or all) of the following (configurable) methods are applied:
•
Connectivity - The destination IP address is queried periodically (currently only by ping).
MP-1xx SIP User’s Manual
152
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8.3.3
8. Gateway Capabilities Description
•
QoS - The QoS of an IP connection is determined according to RTCP statistics of previous
calls. Network delay (in msec) and network packet loss (in percentage) are separately
quantified and compared to a certain (configurable) threshold. If the calculated amounts (of
delay or packet loss) exceed these thresholds the IP connection is disallowed.
•
DNS resolution – When host name is used (instead of IP address) for the destination route, it
is resolved to an IP address by a DNS server. Connectivity and QoS are then applied to the
resolved IP address.
Relevant Parameters
The following parameters (described in Table 5-10) are used to configure the Alternative Routing
mechanism:
8.4
•
AltRoutingTel2IPEnable
•
AltRoutingTel2IPMode
•
IPConnQoSMaxAllowedPL
•
IPConnQoSMaxAllowedDelay
Working with Supplementary Services
The MP-1xx SIP FXS and FXO gateways support the following supplementary services:
•
Hold / Retrieve; refer to Section 8.4.1.
•
Consultation / Alternate; refer to Section 8.4.2.
•
Transfer (Refer + Replaces); refer to Section 8.4.3.
•
Call Forward (3xx Redirect Responses); refer to Section 8.4.4.
•
Call Waiting (182 Queued Response); refer to Section 8.4.5.
•
Message Waiting Indication (MWI); refer to Section 8.4.6.
To activate these supplementary services (Hold, Transfer, Forward, Waiting and MWI) on the
MP-1xx gateway, enable each service’s corresponding parameter either from the Web Interface
or via the ini file. Note that all call participants must support the specific used method.
Note:
When working with application servers (such as BroadSoft’s BroadWorks) in
client server mode (the application server controls all supplementary
services and keypad features by itself), the gateway’s supplementary
services must be disabled.
8.4.1
Call Hold and Retrieve
8.4.1.1
Initiating Hold/Retrieve
•
Active calls can be put on-hold by pressing the phone's hook-flash button.
•
The party that initiates the hold is called the holding party; the other party is called the held
party.
•
After a successful Hold, the holding party hears a Dial Tone.
•
Call retrieve can be performed only by the holding party while the call is held and active.
•
The holding party performs the retrieve by pressing the hook-flash.
•
After a successful retrieve, voice is connected again.
•
Hold is performed by sending a REINVITE with the IP address 0.0.0.0 or “a=sendonly” in the
SDP according to the parameter ‘HoldFormat’.
Version 4.4
153
March 2005
MP-1xx SIP
8.4.1.2
8.4.2
8.4.3
Receiving Hold / Retrieve
•
When an active call receives REINVITE message with either the IP address 0.0.0.0 or the
“inactive” string in SDP, the gateway stops sending RTP and plays a local Held Tone.
•
When an active call receives REINVITE message with “sendonly” string in SDP, the gateway
stops sending RTP and listens to the remote party. In this mode, it is expected that on-hold
music (or any other hold tone) is to be played (over IP) by the remote party.
Consultation / Alternate
•
The consolation feature is relevant only for the holding party (applicable only to the MP1xx/FXS gateway).
•
After holding a call (by pressing hook-flash), the holding party hears dial tone and can now
initiate a new call that is called a consultation call.
•
While hearing dial tone, or when dialing to the new destination (before dialing is complete)
the user can retrieve the held call by pressing hook-flash.
•
The held call can’t be retrieved while Ringback tone is heard.
•
After the consultation call is connected, the user can switch between the held and active call
by pressing hook-flash.
Call Transfer
There are two types of call transfers:
•
Consultation Transfer (Refer + Replaces)
•
Blind Transfer (Refer)
The common way to perform a consultation transfer is as follows:
In the transfer scenario there are three parties:
Party A = transferring, Party B = transferred, Party C = transferred to.
•
A Calls B.
•
B answers.
•
A presses the hook-flash and puts B on-hold (party B hears a hold tone)
•
A dials C.
•
After A completed dialing C, he can perform the transfer by onhook the A phone.
•
After the transfer is completed B and C parties are engaged in a call.
The transfer can be initiated at any of the following stages of the call between A to C:
a. Just after completing dialing C phone number - Transfer from setup.
b. While hearing Ringback
– Transfer from alert.
c.
– Transfer from active.
While speaking to C
Blind transfer is performed after we have a call between A and B, and party A decides to transfer
the call to C immediately without speaking with C.
The result of the transfer is a call between B and C (just like consultation transfer only skipping
the consultation stage).
Note the following SIP issues:
•
Transfer is initiated by sending Refer with Replaces.
MP-1xx SIP User’s Manual
154
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8.4.4
8. Gateway Capabilities Description
•
The gateway can receive and act upon receiving Refer with or without Replaces.
•
The gateway can receive and act upon receiving INVITE with Replaces, in which case the
old call is replaced by the new one.
•
The INVITE with Replaces can be used to implement Directed Call Pickup.
Call Forward
Five forms of call forward are supported:
1.
Immediate
- Any incoming call is forwarded immediately and unconditionally.
2.
Busy
- Incoming call is forwarded if the endpoint is busy.
3.
No reply
-The incoming call is forwarded if it isn't answered for a specified time.
4.
On busy or No reply - Forward incoming calls when the port is busy or when calls are not
answered after a configurable period of time.
5.
Do Not Disturb
- Immediately reject incoming calls.
Three forms of forwarding parties are available:
1.
Served party – the party that is configured to forward the call – MP-1xx/FXS.
2.
Originating party – the party that initiated the first call – MP-1xx/FXS or FXO.
3.
Diverted party – the new destination of the forwarded call – MP-1xx/FXS or FXO.
The served party (MP-1xx/FXS) can be configured through the Web browser (refer to Section
5.8.8.4 on page 96) or via ini file to activate one of the call forward modes. These modes are
configurable per gateway's endpoint.
Note the following SIP issues:
8.4.5
•
Initiating forward – When forward is initiated, the gateway sends a 302 response with a
contact that contains the phone number from the forward table and its corresponding IP
address from the routing table (or, when Proxy is used, the proxy’s IP address).
•
Receiving forward – The gateway handles 3xx responses for redirecting calls with a new
contact.
Call Waiting
The Call Waiting feature enables FXS gateways to accept an additional (second) call on busy
endpoints. If an incoming IP call is designated to a busy port, the called party hears call waiting
tone (several configurable short beeps) and (for Bellcore and ETSI Caller IDs) can view the Caller
ID string of the incoming call. The calling party hears a Call Waiting Ringback Tone. Called party
can accept the new call, using hook-flash, and can toggle between the two calls.
To enable Call Waiting:
•
Set “EnableCallWaiting = 1”.
•
Set “EnableHold = 1”.
•
Define the Call Waiting indication and Call Waiting Ringback tones in the Call Progress
Tones file.
•
To configure the Call Waiting indication tone cadence, modify the following parameters:
‘NumberOfWaitingIndications’, ‘WaitingBeepDuration’ and ‘TimeBetweenWaitingIndications’.
•
To configure a delay interval before a Call Waiting Indication is played to the currently busy
port use the parameter ‘TimeBeforeWaitingIndication’. This enables the caller to hang up
before disturbing the called party with Call Waiting Indications. Applicable only to FXS
gateways.
Both the calling and the called sides are supported by FXS gateways; the FXO gateways support
Version 4.4
155
March 2005
MP-1xx SIP
only the calling side.
To indicate Call Waiting, the gateway sends a 182 - call queued response.
The gateway identifies a Waiting Call when a 182 (call queued response) is received.
8.4.6
Message Waiting Indication
Support for Message Waiting Indication (MWI) according to IETF draft-ietf-sipping-mwi-04.txt,
including SUBSCRIBE (to MWI server). MP-1xx/FXS gateways can accept an MWI Notify
message that indicates waiting messages or that the MWI is cleared. Users are informed of these
messages by a stutter dial tone. The stutter and confirmation tones are defined in the CPT file
(refer to Section 7.1 on page 143). If the MWI display is configured, the number of waiting
messages is also displayed. If the MWI lamp is configured, the phone’s lamp (on a phone that is
equipped with an MWI lamp) is lit. The gateway can subscribe to the MWI server per port (usually
used on FXS) or per gateway (used on FXO).
To configure MWI set the following parameters:
8.5
•
EnableMWI
•
MWIServerIP
•
MWIAnalogLamp
•
MWIDisplay
•
StutterToneDuration
•
EnableMWISubscription
•
MWIExpirationTime
•
SubscribeRetryTime
•
SubscriptionMode
Call Termination on MP-1xx/FXO
The following five methods for call termination are supported by the MP-1xx/FXO. Note that the
disconnection methods used by the MP-1xx must be supported by the CO or PBX.
•
Detection of polarity reversal / current disconnect This is the recommended method. The call is immediately disconnected after polarity
reversal or current disconnect is detected on the Tel side (assuming the PBX / CO produces
this signal).
Relevant ini file parameters: EnableReversalPolarity, EnableCurrentDisconnect,
CurrentDisconnectDuration, CurrentDisconnectDefaultThreshold and
TimeToSampleAnalogLineVoltage.
•
Detection of Reorder / Busy tones The call is immediately disconnected after Reorder / Busy tone is detected on the Tel side
(assuming the PBX / CO produces this tone). This method requires the correct tone
frequencies and cadence to be defined in the Call Progress Tones file. If these frequencies
are not known, define them in the CPT file (the tone produced by the PBX / CO must be
recorded and its frequencies analyzed). This method is slightly less reliable than the
previous one. You can use the CPTWizaed (described in Section F.1.3 on page 222) to
analyze Call Progress Tones generated by any PBX or telephone network.
Relevant ini file parameters: TimeForReorderTone.
MP-1xx SIP User’s Manual
156
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8.6
8. Gateway Capabilities Description
•
Detection of silence The call is disconnected after silence is detected on both call directions for a specific
(configurable) amount of time. The call isn’t disconnected immediately; therefore, this
method should only be used as a backup.
Relevant ini file parameters: EnableSilenceDisconnect and FarEndDisconnectSilencePeriod
(with DSP templates number 2 or 3).
•
Interruption of RTP stream Relevant ini file parameters: BrokenConnectionEventTimeout and
DisconnectOnBrokenConnection. Note that this method operates correctly only if silence
suppression is not used.
•
Protocol-based termination of the call from the IP side.
Mapping PSTN Release Cause to SIP Response
The MP-1xx FXO gateway is used to interoperate between the SIP network and the PSTN/PBX.
This interoperability includes the mapping of PSTN/PBX Call Progress Tones to SIP 4xx or 5xx
responses for IP Tel calls. The converse is also true: For Tel IP calls, the SIP 4xx or 5xx
responses are mapped to tones played to the PSTN/PBX.
When establishing an IP Tel call the following rules are applied:
If the remote party (PSTN/PBX) is busy and the FXO gateway detects a Busy tone, it sends 486
busy to IP. If it detects a Reorder tone, it sends 404 not found (no route to destination) to IP. In
both cases the call is released. Note that if ‘DisconnectOnBusyTone = 0’ the FXO gateway
ignores the detection of Busy/Reorder tones and doesn’t release the call.
For all other MP-1xx FXS/FXO releases (caused when there are no free channels in the specific
hunt group, or when an appropriate rule for routing the call to a hunt group doesn’t exist, or if the
phone number isn’t found), the MP-1xx sends SIP response (to IP) according to the parameter
‘DefaultReleaseCause’. This parameter defines Q.931 release causes. Its default value is ‘3’, that
is mapped to SIP 404 response. By changing its value to ‘34’ SIP 503 response is sent. Other
causes can be used as well.
Version 4.4
157
March 2005
MP-1xx SIP
8.7
Call Detail Report
The Call Detail Report (CDR) contains vital statistic information on calls made by the gateway.
CDRs are generated at the end and (optionally) at the beginning of each call (determined by the
parameter ‘CDRReportLevel’). The destination IP address for CDR logs is determined by the
parameter ‘CDRSyslogServerIP’.
The following CDR fields are supported:
Table 8-2: Supported CDR Fields
Field Name
Description
Cid
CallId
Trunk
BChan
ConId
TG
EPTyp
Orig
SourceIp
DestIp
TON
NPI
SrcPhoneNum
TON
NPI
DstPhoneNum
DstNumBeforeMap
Durat
Coder
Intrv
RtpIp
Port
TrmSd
TrmReason
Fax
InPackets
OutPackets
PackLoss
UniqueId
SetupTime
ConnectTime
ReleaseTime
RTPdelay
RTPjitter
RTPssrc
RemoteRTPssrc
RedirectReason
TON
NPI
RedirectPhonNum
Port Number
H.323/SIP Call Identifier
N/A
N/A
H.323/SIP Conference ID
Trunk Group Number
Endpoint Type
Call Originator (IP, Tel)
Source IP Address
Destination IP Address
Source Phone Number Type
Source Phone Number Plan
Source Phone Number
Destination Phone Number Type
Destination Phone Number Plan
Destination Phone Number
Destination Number Before Manipulation
Call Duration
Selected Coder
Packet Interval
RTP IP Address
Remote RTP Port
Initiator of Call Release (IP, Tel, Unknown)
Termination Reason
Fax Transaction during the Call
Number of Incoming Packets
Number of Outgoing Packets
Number of Outgoing Lost Packets
unique RTP ID
Call Setup Time
Call Connect Time
Call Release Time
RTP Delay
RTP Jitter
Local RTP SSRC
Remote RTP SSRC
Redirect Reason
Redirection Phone Number Type
Redirection Phone Number Plan
Redirection Phone Number
MP-1xx SIP User’s Manual
158
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8.8
8. Gateway Capabilities Description
Metering Tones Relay
The MP-1xx FXS and FXO gateways can be used to relay standard 12 or 16 kHz metering tones
over the IP network as illustrated in Figure 8-1 below.
Figure 8-1: Metering Tone Relay Architecture
After a call is established between the FXS and FXO gateways, the PSTN generates 12 or 16
kHz metering tones towards the FXO gateway. The FXO gateway detects these pulses and
relays them, over IP, to the FXS gateway using a proprietary Info messages (shown in Figure
8-2). The FXS gateway generates the same pulses to the connected phone.
The parameter ‘MeteringType’ (described in Table 5-26) is used to determine the frequency of the
metering tone (12 kHz (default) or 16 kHz). In addition, the correct (12 or 16 kHz) coefficient file
must be used for both FXS and FXO gateways.
To enable this feature configure ‘SendMetering2IP = 1’.
The proprietary Info message used to relay the metering tone pulse contains a "Content-Type:
message/Metering":
Figure 8-2: Proprietary Info Message for Relaying Metering Tones
INFO sip:108@10.13.83.1 SIP/2.0
Via: SIP/2.0/UDP 10.13.83.2;branch=z9hG4bKacEizRjAa
Max-Forwards: 70
From: "aviad" <sip:201@10.13.83.2>;tag=1c1638621413
To: <sip:108@10.13.83.1;user=phone>;tag=1c1412617336
Call-ID: 2031013892fcCd@10.13.83.2
CSeq: 3 INFO
Contact: <sip:201@10.13.83.2>
Supported: em,timer,replaces,path
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
User-Agent: Audiocodes-Sip-Gateway-MP-104 FXS/v.4.40.0.18700
Content-Type: message/Metering
Content-Length: 0
Version 4.4
159
March 2005
MP-1xx SIP
8.9
Configuration Examples
8.9.1
Establishing a Call between Two Gateways
After you’ve installed and set up the MP-1xx, you can ensure that it functions as expected by
establishing a call between it and another gateway. This section exemplifies how to configure two
MP-108/FXS SIP gateways in order to establish a call. After configuration, you can make calls
between telephones connected to a single MP-108 gateway or between the two MP-108
gateways.
In the following example, the IP address of the first gateway is 10.2.37.10 and its endpoint
numbers are 101 to 108. The IP address of the second gateway is 10.2.37.20 and its endpoint
numbers are 201 to 208.
In this example, a SIP Proxy is not used. Call routing is performed using the internal ‘Tel to IP
Routing’ table.
To configure the two gateways, take these 4 steps:
1.
Configure the following settings on the first MP-108 gateway (10.2.37.10):
In the ‘Endpoint Phone Numbers’ screen, assign the phone numbers 101 to 108 for the
gateway’s endpoints.
2.
Configure the following settings on the second MP-108 gateway (10.2.37.20):
In the ‘Endpoint Phone Numbers’ screen, assign the phone numbers 201 to 208 for the
gateway’s endpoints.
3.
Configure the following settings for both gateways:
In the ‘Tel To IP Routing’ screen, in the first row, enter 10 in the ‘Destination Phone
Prefix’ field and enter the IP address of the first gateway (10.2.37.10) in the field ‘IP
Address’. In the second row, enter 20 and the IP address of the second gateway
(10.2.37.20) respectively.
These settings enable the routing (from both gateways) of outgoing Tel IP calls that
start with 10 to the first gateway and calls that start with 20 to the second gateway.
4.
Make a call! Pick up the phone connected to port #1 of the first MP-108 and dial 102 (to the
phone connected to port #2 of the same gateway). Listen out for progress tones at the
calling endpoint and for ringing tone at the called endpoint. Answer the called endpoint, talk
into the calling endpoint, and check the voice quality. Dial 201 from the phone connected to
port #1 of the first MP-108 gateway; the phone connected to port #1 of the second MP-108
rings. Answer the call and check the voice quality.
MP-1xx SIP User’s Manual
160
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8.9.2
8. Gateway Capabilities Description
SIP Call Flow
The following Call Flow describes SIP messages exchanged between two MP-108 gateways
during simple call.
Phone "6000" dials "2000", sending INVITE message to Gateway 10.8.201.161
Figure 8-3: SIP Call Flow
MP-108
10.8.201.158
MP-108
10.8.201.161
INVITE
F1
Ringing
F2
200 OK
F3
ACK
F4
BYE
F5
200 OK
F6
F1 10.8.201.158 ==> 10.8.201.161 INVITE
INVITE sip:6000@10.8.201.161;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKacolwbzYF
From: <sip:2000@10.8.201.158>;tag=1c3535
To: <sip:6000@10.8.201.161>
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
CSeq: 20214 INVITE
Contact: <sip:2000@10.8.201.158;user=phone>
User-Agent: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
Supported: 100rel,em
Accept-Language: en
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO
Content-Type: application/sdp
Content-Length: 208
v=0
s=Phone-Call
t=0 0
o=AudiocodesGW 87943 43401 IN IP4 10.8.201.158
c=IN IP4 10.8.201.158
m=audio 6000 RTP/AVP 8 96
a=rtpmap:8 pcma/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=ptime:20
Version 4.4
161
March 2005
MP-1xx SIP
F2 10.8.201.161 ==> 10.8.201.158 180 RINGING
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKacolwbzYF
From: <sip:2000@10.8.201.158>;tag=1c3535
To: <sip:6000@10.8.201.161>;tag=1c29715
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
Server: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
CSeq: 20214 INVITE
Supported: 100rel,em
Content-Length: 0
Note:
Phone "2000" answers the call, and sends "200 OK" message to gateway
10.8.201.158.
F3 10.8.201.161 ==> 10.8.201.158 200 OK
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKacolwbzYF
From: <sip:2000@10.8.201.158>;tag=1c3535
To: <sip:6000@10.8.201.161>;tag=1c29715
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
CSeq: 20214 INVITE
Contact: <sip:6000@10.8.201.161;user=phone>
Server: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
Supported: 100rel,em
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO
Content-Type: application/sdp
Content-Length: 208
v=0
s=Phone-Call
t=0 0
o=AudiocodesGW 30762 37542 IN IP4 10.8.201.161
c=IN IP4 10.8.201.161
m=audio 4040 RTP/AVP 8 96
a=rtpmap:8 pcma/8000
a=ptime:20
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
F4 10.8.201.158 ==> 10.8.201.161 ACK
ACK sip:6000@10.8.201.161;user=phone;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKachoWSQxD
From: <sip:2000@10.8.201.158>;tag=1c3535
To: <sip:6000@10.8.201.161>;tag=1c29715
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
User-Agent: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
CSeq: 20214 ACK
Supported: 100rel,em
Content-Length: 0
Note:
MP-1xx SIP User’s Manual
Phone "6000" goes onhook, gateway 10.8.201.161 sends "BYE" to gateway
10.8.201.158. Voice path is established.
162
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8. Gateway Capabilities Description
F5 10.8.201.161 ==> 10.8.201.158 BYE
BYE sip:2000@10.8.201.158;user=phone;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.161;branch=z9hG4bKacLBzZgmA
From: <sip:6000@10.8.201.161>;tag=1c29715
To: <sip:2000@10.8.201.158>;tag=1c3535
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
User-Agent: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
CSeq: 34541 BYE
Supported: 100rel,em
Content-Length: 0
F6 10.8.201.158 ==> 10.8.201.161 200 OK
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.8.201.161;branch=z9hG4bKacLBzZgmA
From: <sip:6000@10.8.201.161>;tag=1c29715
To: <sip:2000@10.8.201.158>;tag=1c3535
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
Server: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
CSeq: 34541 BYE
Supported: 100rel,em
Content-Length: 0
8.9.3
SIP Authentication Example
MP-108 gateway supports basic and digest (MD5) authentication types, according to SIP RFC
3261 standard. A proxy server might require authentication before forwarding an INVITE
message. A Registrar/Proxy server may also require authentication for client registration. A proxy
replies to an unauthenticated INVITE with a 407 Proxy Authorization Required response,
containing a Proxy-Authenticate header with the form of the challenge. After sending an ACK for
the 407, the User Agent can then resend the INVITE with a Proxy-Authorization header
containing the credentials.
User Agent, redirect or registrar servers typically use 401 Unauthorized response to challenge
authentication containing a WWW-Authenticate header, and expect the re-INVITE to contain an
Authorization header.
The following example describes the Digest Authentication procedure including computation of
User Agent credentials.
The REGISTER request is sent to Registrar/Proxy server for registration, as follows:
REGISTER sip:10.2.2.222 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.200
From: <sip: 122@10.1.1.200>;tag=1c17940
To: <sip: 122@10.1.1.200>
Call-ID: 634293194@10.1.1.200
User-Agent: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
CSeq: 1 REGISTER
Contact: sip:122@10.1.1.200:
Expires:3600
On receiving this request the Registrar/Proxy returns 401 Unauthorized response.
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.2.1.200
From: <sip:122@10.2.2.222 >;tag=1c17940
To: <sip:122@10.2.2.222 >
Call-ID: 634293194@10.1.1.200
Cseq: 1 REGISTER
Date: Mon, 30 Jul 2001 15:33:54 GMT
Server: Columbia-SIP-Server/1.17
Content-Length: 0
Version 4.4
163
March 2005
MP-1xx SIP
WWW-Authenticate: Digest realm="audiocodes.com",
nonce="11432d6bce58ddf02e3b5e1c77c010d2",
stale=FALSE,
algorithm=MD5
According to the sub-header present in the WWW-Authenticate header the correct REGISTER
request is formed.
Since the algorithm used is MD5, take:
The username is equal to the endpoint phone number: 122
The realm return by the proxy: audiocodes.com
The password from the ini file: AudioCodes.
The equation to be evaluated: (according to RFC this part is called A1).
“122:audiocodes.com:AudioCodes”.
The MD5 algorithm is run on this equation and stored for future usage.
The result is: “a8f17d4b41ab8dab6c95d3c14e34a9e1”
Next we need to evaluate the par called A2. We take:
The method type “REGISTER”
Using SIP protocol “sip”
Proxy IP from ini file “10.2.2.222”
The equation to be evaluated:
“REGISTER:sip:10.2.2.222”.
The MD5 algorithm is run on this equation and stored for future usage.
The result is:”a9a031cfddcb10d91c8e7b4926086f7e”
The final stage:
The A1 result
The nonce from the proxy response: “11432d6bce58ddf02e3b5e1c77c010d2”
The A2 result
The equation to be evaluated:
“A1:11432d6bce58ddf02e3b5e1c77c010d2:A2”.
The MD5 algorithm is run on this equation. The outcome of the calculation is the response
needed by the GW to be able top register with the Proxy.
The response is: “b9c45d0234a5abf5ddf5c704029b38cf”
At this time a new REGISTER request is issued with the response:
REGISTER sip:10.2.2.222 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.200
From: <sip: 122@10.1.1.200>;tag=1c23940
To: <sip: 122@10.1.1.200>
Call-ID: 654982194@10.1.1.200
MP-1xx SIP User’s Manual
164
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8. Gateway Capabilities Description
Server: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410
CSeq: 1 REGISTER
Contact: sip:122@10.1.1.200:
Expires:3600
Authorization: Digest, username: 122,
realm="audiocodes.com”,
nonce="11432d6bce58ddf02e3b5e1c77c010d2",
uri=”10.2.2.222”,
response=“b9c45d0234a5abf5ddf5c704029b38cf”
On receiving this request, if accepted by the Proxy, the proxy returns a 200 OK response closing
the REGISTER transaction.
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.1.200
From: <sip: 122@10.1.1.200>;tag=1c23940
To: <sip: 122@10.1.1.200>
Call-ID: 654982194@10.1.1.200
Cseq: 1 REGISTER
Date: Thu, 26 Jul 2001 09:34:42 GMT
Server: Columbia-SIP-Server/1.17
Content-Length: 0
Contact: <sip:122@10.1.1.200>; expires="Thu, 26 Jul 2001 10:34:42 GMT"; action=proxy;
q=1.00
Contact: <122@10.1.1.200:>; expires="Tue, 19 Jan 2038 03:14:07 GMT"; action=proxy;
q=0.00
Expires: Thu, 26 Jul 2001 10:34:42 GMT
8.9.4
Remote IP Extension between FXO and FXS
This application explains how to implement remote extension via IP, using MP-108/FXO and MP108/FXS gateways. In this configuration, PBX incoming calls are routed to the “Remote
Extension” via the MP-108/FXO and MP-108/FXS gateways.
Requirements:
•
One MP-108/FXO gateway
•
One MP-108/FXS gateway
•
Analog phones (POTS)
•
PBX – one or more PBX loop start lines
•
LAN.
Connect the MP-108/FXO ports directly to the PBX lines as shown in the diagram below:
Version 4.4
165
March 2005
MP-1xx SIP
Figure 8-4: MP-108 FXS & FXO Remote IP Extension
8.9.4.1
Dialing from Remote Extension
(Phone connected to MP-108/FXS)
To configure the call, take these 6 steps:
8.9.4.2
1.
Lift the handset to hear the dial tone coming from PBX, as if the phone was connected
directly to PBX.
2.
MP-108/FXS and MP-108/FXO establish a voice path connection from the phone to the PBX
immediately the phone handset is raised.
3.
Dial the destination number (the DTMF digits are sent, over IP, directly to the PBX).
4.
All tones heard are generated from the PBX (such as Ringback, busy or fast busy tones).
5.
There is one-to-one mapping between MP-108/FXS ports and PBX lines.
6.
The call is disconnected when the phone connected to the MP-108/FXS goes onhook.
Dialing from other PBX line, or from PSTN
To configure the call, take these 5 steps:
1.
Dial the PBX subscriber number the same way as if the user’s phone was connected directly
to PBX.
2.
Immediately as PBX rings into MP-108/FXO, the ring signal is “send” to phone connected to
MP-108/FXS.
3.
Once the phone’s handset, connected to MP-108/FXS, is raised, the MP-108/FXO seizes the
PBX line and the voice path is established between the phone and the PBX line.
4.
There is a one to one mapping between PBX lines and MP-108/FXS ports. Each PBX line is
routed to the same phone (connected to MP-108/FXS).
5.
The call is disconnected when phone connected to MP-108/FXS goes onhook.
MP-1xx SIP User’s Manual
166
Document #: LTRT-65404
MP-1xx SIP User’s Manual
8.9.4.3
8. Gateway Capabilities Description
MP-108/FXS Configuration (using the Embedded Web Server)
To configure the MP-108/FXS, take these 3 steps:
1.
In the ‘Endpoint Phone Numbers’ screen, assign the phone numbers 100 to 107 for the
gateway’s endpoints.
2.
In the ‘Automatic Dialing’ screen, enter the phone numbers of the MP-108/FXO gateway in
the ‘Destination Phone Number’ fields. When a phone connected to port #1 goes offhook,
the FXS gateway automatically dials the number ‘200’.
3.
In the ‘Tel To IP Routing’ screen, enter 20 in the ‘Destination Phone Prefix’ field, and the IP
address of the MP-108/FXO gateway (10.1.10.2) in the field ‘IP Address’.
Version 4.4
167
March 2005
MP-1xx SIP
8.9.4.4
MP-108/FXO Configuration (using the Embedded Web Server)
To configure the MP-108/FXO, take these 4 steps:
1.
In the ‘Endpoint Phone Numbers’ screen, assign the phone numbers 200 to 207 for the
gateway’s endpoints.
2.
In the ‘Automatic Dialing’ screen, enter the phone numbers of the MP-108/FXS gateway in
the ‘Destination Phone Number’ fields. When a ringing signal is detected at port #1, the FXO
gateway automatically dials the number ‘100’.
3.
In the ‘Tel To IP Routing’ screen, enter 10 in the ‘Destination Phone Prefix’ field, and the IP
address of the MP-108/FXS gateway (10.1.10.3) in the field ‘IP Address’.
4.
In the ‘Protocol Management’ screen, set the parameter ‘Dialing Mode’ to ‘Two Stage’
(IsTwoStageDial=1).
MP-1xx SIP User’s Manual
168
Document #: LTRT-65404
MP-1xx SIP User’s Manual
9
9. Diagnostics
Diagnostics
Several diagnostic tools are provided, enabling you to identify correct functioning of the MP-1xx,
or an error condition with a probable cause and a solution or workaround.
9.1
•
Front and rear panel indicator LEDs on the MP-1xx. The location and functionality of the
front panel LEDs is shown in Section 2.1.2 on page 22. The location and functionality of the
rear panel LEDs is shown in Sections 2.2 and 22.
•
Self-Testing on hardware initialization, refer to Section 9.1 below.
•
RS-232 terminal Notification Messages, refer to Section 9.2 on page 170.
•
Syslog Event Notification Messages. The Log Message can be viewed using an external
Syslog server, refer to Section 9.2.2 on page 170, or on the ‘Message Log’ screen in the
Embedded Web Server, refer to Section 5.10.3 on page 129. Note that the ‘Message Log’
screen is not recommended for prolong debugging.
MP-1xx Self-Testing
The MP-1xx features two self-testing modes: rapid and detailed.
9.1.1
Rapid Self-Test Mode
Rapid self-test mode is run each time the media gateway completes the initialization process.
This is a short test phase in which the only errors detected and reported are failure in initializing
hardware components. All Status and Error reports in this self-test phase are reported through
Network Interface ports, as well as indicated by the LED Status Indicators.
9.1.2
Detailed Self-Test Mode
Detailed self-test mode is run when initialization of the media gateway is completed and if the
configuration parameter EnableDiagnostics is set to 1. In this mode, the media gateway tests all
hardware components (memory, DSP, etc.), outputs the status of the test results, and ends the
test.
To enable the detailed self-test mode, take these 4 steps:
1.
Retrieve the ini file from the VoIP gateway.
2.
Change the EnableDiagnostics parameter to 1.
3.
Load the ini file onto the VoIP gateway.
4.
Restart the VoIP gateway.
The VoIP gateway does not process calls while in Detailed self-test mode. When you are finished
running the detailed test, you must disable the Detailed self-test mode.
To disable the detailed self-test mode, take these 4 steps:
1.
Retrieve the ini file from the VoIP gateway.
2.
Change the EnableDiagnostics parameter to 0.
3.
Load the ini file onto the VoIP gateway.
4.
Restart the VoIP gateway.
Version 4.4
169
March 2005
MP-1xx SIP
9.2
Troubleshooting the MP-1xx via the RS-232 Port
To troubleshoot initialization problems and view the status and error messages of the MP-1xx,
use serial communication software (e.g., HyperTerminalTM) connected to the MP-1xx via the RS232 port. You can also use this connection to change the network settings (IP address, subnet
mask and default gateway IP address) of the MP-1xx.
For detailed information on connecting the RS-232 port to your PC, refer to Section 3.4.1 on page
32.
9.2.1
Viewing the Gateway’s Information
After applying power to or resetting the gateway, the information, shown in Figure 9-1 below,
appears on the terminal screen. This information is used to determine possible MP-1xx
initialization problems, such as incorrectly defined (or undefined) Local IP address, subnet mask,
default router IP address, TFTP server IP address, BootFile name, ini file name and full-duplex or
half-duplex network state.
Figure 9-1: Status and Error Messages
MAC address = 00-90-8F-01-00-9E
Local IP address = 10.1.37.6
Subnet mask = 255.255.0.0
Default gateway IP address = 10.1.1.5
TFTP server IP address = 10.1.1.167
Boot file name = ram35136.cmp
INI file name = mp108.ini
Call agent IP address = 10.1.1.18
Log server IP address = 0.0.0.0
Full/Half Duplex state = HALF DUPLEX
Flash Software Burning state = OFF
Serial Debug Mode = OFF
Lan Debug Mode = OFF
BootLoad Version 1.75
Starting TFTP download... Done.
MP108 Version 3.80.00
9.2.2
Changing the Networking Parameters
You can use the serial connection to change the network settings (IP address, subnet mask and
default gateway IP address) of the MP-1xx.
To change the network settings via RS-232, take these 4 steps:
1.
At the prompt type “conf” and press enter; the configuration command shell is activated.
2.
To check the current network parameters, at the prompt, type “GCP IP” and press enter; the
current network settings are displayed.
3.
Change the network settings by typing: “SCP IP [ip_address] [subnet_mask]
[default_gateway]” (e.g., “SCP IP 10.13.77.7 255.255.0.0 10.13.0.1”); the new settings take
effect on-the-fly. Connectivity is active at the new IP address.
Note: This command requires you to enter all three network parameters (separated by
spaces).
4.
To save the configuration, at the prompt, type “SAR” and press enter; the MP-1xx restarts
with the new network settings.
MP-1xx SIP User’s Manual
170
Document #: LTRT-65404
MP-1xx SIP User’s Manual
9.3
9. Diagnostics
Syslog Support
Syslog protocol is an event notification protocol that enables a machine to send event notification
messages across IP networks to event message collectors -also known as Syslog servers.
Syslog protocol is defined in the IETF RFC 3164 standard.
Since each process, application and operating system was written independently, there is little
uniformity to Syslog messages. For this reason, no assumption is made on the contents of the
messages other than the minimum requirements of its priority.
Syslog uses UDP as its underlying transport layer mechanism. The UDP port that was assigned
to Syslog is 514.
The Syslog message is transmitted as an ASCII (American Standard Code for Information
Interchange) message. The message starts with a leading "<" ('less-than' character), followed by
a number, which is followed by a ">" ('greater-than' character). This is optionally followed by a
single ASCII space.
The number described above is known as the Priority and represents both the Facility and
Severity as described below. The Priority number consists of one, two, or three decimal integers.
For example:
<37> Oct 11 16:00:15 mymachine su: 'su root' failed for lonvick on /dev/pts/8
9.3.1
Syslog Servers
Users can use the provided Syslog server (ACSyslog08.exe) or other third-party Syslog servers.
Examples of Syslog servers available as shareware on the Internet:
•
Kiwi Enterprises: http://www.kiwisyslog.com/
•
The US CMS Server: http://uscms.fnal.gov/hanlon/uscms_server/
•
TriAction Software: http://www.triaction.nl/Products/SyslogDaemon.asp
•
Netal SL4NT 2.1 Syslog Daemon: http://www.netal.com
A typical Syslog server application enables filtering of the messages according to priority, IP
sender address, time, date, etc.
9.3.2
Operation
9.3.2.1
Sending the Syslog Messages
The Syslog client, embedded in the firmware of the MP-1xx, sends error reports/events generated
by the MP-1xx unit application to a Syslog server, using IP/UDP protocol.
9.3.2.2
Setting the Syslog Server
To set the Syslog server:
•
Version 4.4
Use the MP-1xx Embedded Web Server (Advanced Configuration>Network Settings>screen
section Syslog Settings) to enable the Syslog Server (Enable Syslog) and to enter its IP
address (Syslog Server IP address); refer to Section 5.9 on page 103 and to Figure 9-2
below.
171
March 2005
MP-1xx SIP
Figure 9-2: Setting the Syslog Server IP Address
•
9.3.2.3
Alternately, use the Embedded Web Server or the BootP/TFTP utility to load the ini
configuration file containing both the IP address and the enabling parameters:
SyslogServerIP and EnableSyslog respectively. For detailed information on the BootP/TFTP
utility, refer to Appendix B on page 197. For an ini file example showing these parameters,
refer to Section 9.3.2.3 and to Figure 9-2 under it.
The ini File Example for Syslog
Figure 9-2 shows an ini file section with an example configuration for the address parameter
SyslogServerIP and an example configuration for the client activation parameter EnableSyslog.
Figure 9-3: The ini File Example for Syslog
[Syslog]
SyslogServerIP = 10.2.0.136
EnableSyslog = 1
GWDebugLevel = 5
9.4
Solutions to Possible Problems
9.4.1
General
If there is a problem, check the following resources:
•
The ‘Channel Status’ pages on the Web Interface. Refer to Section 5.10 on page 124.
•
The Log Message on the Web Interface, refer to Section 5.10.3 on page 129.
•
Log messages sent to the RS-232 Port. Refer to Section 9.2 on page 170.
•
BootP & TFTP log messages (for startup problems). Refer to Section B.9 on page 200.
•
Log messages in Syslog server. Refer to Section 9.2.2 on page 170.
MP-1xx SIP User’s Manual
172
Document #: LTRT-65404
MP-1xx SIP User’s Manual
10
10. BootP/DHCP Support
BootP/DHCP Support
10.1 Startup Process
The startup process (illustrated in Figure 10-1 on page 174) begins when the gateway is reset
(physically or from the Web / SNMP) and ends when the operational software is running. In the
startup process, the network parameters, software and configuration files are obtained.
After the gateway powers up or after it is physically reset, it broadcasts a BootRequest message
to the network. If it receives a reply (from a BootP server), it changes its network parameters (IP
address, subnet mask and default gateway address) to the values provided. If there is no reply
from a BootP server and if DHCP is enabled (DHCPEnable = 1), the gateway initiates a standard
DHCP procedure to configure its network parameters.
After changing the network parameters, the gateway attempts to load the cmp and various
configuration files from the TFTP server’s IP address, received from the BootP/DHCP servers. If
a TFTP server’s IP address isn’t received, the gateway attempts to load the software (cmp) file
and / or configuration files from a preconfigured TFTP server (refer to the parameters ‘IniFileURL’
and ‘CmpFileURL’ described in Table 5-29 on page 108). Thus, the gateway can obtain its
network parameters from BootP or DHCP servers and its software and configuration files from a
different TFTP server (preconfigured in ini file).
If BootP/DHCP servers are not found or when the gateway is reset from the Web / SNMP, it
retains its network parameters and attempts to load the software (cmp) file and / or configuration
files from a preconfigured TFTP server.
If a preconfigured TFTP server doesn’t exist, the gateway operates using the existing software
and configuration files loaded on its non-volatile memory.
Note that after the operational software runs, if DHCP is configured, the gateway attempts to
renew its lease with the DHCP server.
Version 4.4
Note 1:
Though DHCP and BootP servers are very similar in operation, the DHCP
server includes some differences that could prevent its operation with BootP
clients. However, many DHCP servers, such as Windows™ NT DHCP
server, are backward-compatible with BootP protocol and can be used for
gateway configuration.
Note 2:
The time duration between BootP/DHCP requests is set to 1 second by
default. This can be changed by the BootPDelay ini file parameter. Also, the
number of requests is 3 by default and can be changed by BootPRetries ini
file parameter (both parameters can also be set using the BootP command
line switches).
173
March 2005
MP-1xx SIP
Figure 10-1: MP-1xx Startup Process
Reset from the Web
Interface or SNMP
Physical Reset
BootP
x times
No
Response
BootP Response
DHCP
x times
No
Response
DHCP Response
Update network
parameters from
BootP/DHCP reply
BootP/DHCP
reply contains firmware
file name?
No
Yes
Download
firmware via
TFTP
BootP/DHCP
reply contains ini file
name?
BootP/DHCP
reply contains ini file
name?
No
Preconfigured firmware
URL?
Yes
Yes
Yes
Download
firmware via
TFTP
No
Device
reset
No
Preconfigured ini file
URL?
Yes
Download
configuration
files via TFTP
No
Run operational software
MP-1xx SIP User’s Manual
174
Document #: LTRT-65404
MP-1xx SIP User’s Manual
10. BootP/DHCP Support
10.2 DHCP Support
When the gateway is configured to use DHCP (DHCPEnable = 1), it attempts to contact the
enterprise’s DHCP server to obtain the networking parameters (IP address, subnet mask, default
gateway, primary/secondary DNS server and SIP server address). These network parameters
have a "time limit". After the time limit expires, the gateway must "renew" its lease from the DHCP
server.
Note that if the DHCP server denies the use of the gateway's current IP address and specifies a
different IP address (according to RFC 1541), the gateway must change its networking
parameters. If this happens while calls are in progress, they are not automatically rerouted to the
new network address (since this function is beyond the scope of a VoIP gateway). Therefore,
administrators are advised to configure DHCP servers to allow renewal of IP addresses.
Note: If the gateway's network cable is disconnected and reconnected, a DHCP renewal is
performed (to verify that the gateway is still connected to the same network).
When DHCP is enabled, the gateway also includes its product name (e.g., ‘MP-108 FXS’ or ‘MP104 FXO’) in the DHCP ‘option 60’ Vendor Class Identifier. The DHCP server can use this
product name to assign an IP address accordingly.
Note: After power-up, the gateway issues two DHCP requests. Only in the second request, the
DHCP ‘option 60’ is contained. If the gateway is reset from the Web/SNMP, only a single DHCP
request containing ‘option 60’ is sent.
If DHCP procedure is used, the new gateway IP address, allocated by the DHCP server, must be
detected.
Note:
If, during operation, the IP address of the gateway is changed as a result of
a DHCP renewal, the gateway is automatically reset.
To detect the gateway’s IP address, follow one of the procedures below:
•
Starting with Bootload software version 1.92, the gateway can use host name in the DHCP
request. The host name is set to acl_nnnnn, where nnnnn stands for the gateway’s serial
number (the serial number is equal to the last 6 digits of the MAC address converted from
Hex to decimal). If the DHCP Server registers this host name to a DNS server, the user can
access the gateway (through a Web browser) using a URL of http://acl_<serial number>
(instead of using the gateway’s IP address). For example, if the gateway’s MAC address is
00908f010280, the DNS name is acl_66176.
•
After physically resetting the gateway its IP address is displayed in the ‘Client Info’ column in
the BootP/TFTP configuration utility (refer to Figure B-1 on page 199).
•
Use the RS-232 connector (for detailed information on using the RS-232, refer to Section 9.2
on page 170).
•
Contact your System Administrator.
Version 4.4
175
March 2005
MP-1xx SIP
10.3 BootP Support
10.3.1 Upgrading the MP-1xx
When upgrading the MP-1xx (loading new software onto the gateway) using the BootP/TFTP
configuration utility:
•
From version 4.2 to version 4.4, the device loses its configuration. Therefore, to retain the
previous gateway configuration you must save the ini file before you replace the cmp file,
and reload it to the device. For information on backing up and restoring the gateway’s
configuration refer to Section 5.9.2.1 on page 120.
•
From version 4.4 to version 4.4 or to any higher version, the device retains its configuration
(ini file), however, the auxiliary files (CPT, logo, etc.) may be erased.
When using the Software Upgrade wizard, available through the Web Interface (refer to Section
5.11.1 on page 131), the auxiliary files are saved as well.
Note: To save the cmp file to non-volatile memory, use the -fb command line switches. If the file
is not saved, the gateway reverts to the old version of software after the next reset. For
information on using command line switches, refer to Section B.11.6 on page 206.
10.3.2 Vendor Specific Information Field
The MP-1xx uses the vendor specific information field in the BootP request to provide devicerelated initial startup information. The BootP/TFTP configuration utility displays this information in
the ‘Client Info’ column (refer to Figure B-1).
Note: This option is not available on DHCP servers.
The Vendor Specific Information field is disabled by default. To enable / disable this feature: set
the ini file parameter ‘ExtBootPReqEnable’ (Table 5-29 on page 108) or use the ‘-be’ command
line switch (refer to Table B-1 on page 206).
Table 10-1 details the vendor specific information field according to device types:
Table 10-1: Vendor Specific Information Field
Description
Value
Length
220
Board Type
#10 = MP-102
#11 = MP-104
#12 = MP-108
#13 = MP-124
1
221
Current IP Address
XXX.XXX.XXX.XXX
4
222
Burned Boot Software Version
X.XX
4
223
Burned cmp Software Version
XXXXXXXXXXXX
12
224
Geographical Address
0 – 31
1
225
Chassis Geographical Address
0 – 31
1
228
Indoor / Outdoor
(Indoor is valid only for FXS. FXO is
always Outdoor.)
#0 = Indoor
#1 = Outdoor
1
Tag #
229
E&M
N/A
1
230
Analog Channels
2 / 4 / 8 / 24
1
MP-1xx SIP User’s Manual
176
Document #: LTRT-65404
MP-1xx SIP User’s Manual
10. BootP/DHCP Support
Table 10-2 exemplifies the structure of the vendor specific information field for a TP-1610 slave
module with IP Address 10.2.70.1.
Table 10-2: Structure of the Vendor Specific Information Field
Value (4)
Tag End
177
Value (3)
221
Value (2)
1
Value (1)
1
Length
225
Tag Num
2
Value
Tab Num
1
Length
Value
220
Length
Version 4.4
12
Tag Num
42
Length
Total
VendorSpecific
Information
Code
4
10
2
70
1
255
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
178
Document #: LTRT-65404
MP-1xx SIP User’s Manual
11
11. SNMP-Based Management
SNMP-Based Management
Simple Network Management Protocol (SNMP) is a standard-based network control protocol
used to manage elements in a network. The SNMP Manager (usually implemented by a Network
Manager (NM) or an Element Manager (EM)) connects to an SNMP Agent (embedded on a
remote Network Element (NE)) to perform network element Operation, Administration and
Maintenance (OAM).
Both the SNMP Manager and the NE refer to the same database to retrieve information or
configure parameters. This database is referred to as the Management Information Base (MIB),
and is a set of statistical and control values. Apart from the standard MIBs documented in IETF
RFCs, SNMP additionally enables the use of private MIBs, containing a non-standard information
set (specific functionality provided by the NE).
Directives, issued by the SNMP Manager to an SNMP Agent, consist of the identifiers of SNMP
variables (referred to as MIB object identifiers or MIB variables) along with instructions to either
get the value for that identifier, or set the identifier to a new value (configuration). The SNMP
Agent can also send unsolicited events towards the EM, called SNMP traps.
The definitions of MIB variables supported by a particular agent are incorporated in descriptor
files, written in Abstract Syntax Notation (ASN.1) format, made available to EM client programs so
that they can become aware of MIB variables and their use.
The device contains an embedded SNMP Agent supporting both general network MIBs (such as
the IP MIB), VoP-specific MIBs (such as RTP) and our proprietary MIBs (acBoard, acGateway,
acAlarm and other MIBs), enabling a deeper probe into the inter-working of the device. All
supported MIB files are supplied to customers as part of the release.
11.1 About SNMP
11.1.1 SNMP Message Standard
Four types of SNMP messages are defined:
•
Get - A request that returns the value of a named object.
•
Get-Next - A request that returns the next name (and value) of the ‘next’ object supported by
a network device given a valid SNMP name.
•
Set - A request that sets a named object to a specific value.
•
Trap - A message generated asynchronously by network devices. It is an unsolicited
message from an agent to the manager.
Each of these message types fulfills a particular requirement of Network Managers:
•
Get Request - Specific values can be fetched via the ‘get’ request to determine the
performance and state of the device. Typically, many different values and parameters can be
determined via SNMP without the overhead associated with logging into the device, or
establishing a TCP (Transmission Control Protocol) connection with the device.
•
Get Next Request - Enables the SNMP standard network managers to ‘walk’ through all
SNMP values of a device (via the ‘get-next’ request) to determine all names and values that
an operant device supports. This is accomplished by beginning with the first SNMP object to
be fetched, fetching the next name with a ‘get-next’, and repeating this operation.
•
Set Request - The SNMP standard provides a method of effecting an action associated with
a device (via the ‘set’ request) to accomplish activities such as disabling interfaces,
disconnecting users, clearing registers, etc. This provides a way of configuring and
controlling network devices via SNMP.
Version 4.4
179
March 2005
MP-1xx SIP
•
Trap Message - The SNMP standard furnishes a mechanism by which devices can ‘reach
out’ to a Network Manager on their own (via a ‘trap’ message) to notify or alert the manager
of a problem with the device. This typically requires each device on the network to be
configured to issue SNMP traps to one or more network devices that are awaiting these
traps.
The above message types are all encoded into messages referred to as Protocol Data Units
(PDUs) that are interchanged between SNMP devices.
11.1.2 SNMP MIB Objects
The SNMP MIB is arranged in a tree-structured fashion, similar in many ways to a disk directory
structure of files. The top level SNMP branch begins with the ISO ‘internet’ directory, which
contains four main branches:
•
The ‘mgmt’ SNMP branch - Contains the standard SNMP objects usually supported (at least
in part) by all network devices.
•
The ‘private’ SNMP branch - Contains those ‘extended’ SNMP objects defined by network
equipment vendors.
•
The ‘experimental’ and ‘directory’ SNMP branches - Also defined within the ‘internet’ root
directory, these branches are usually devoid of any meaningful data or objects.
The ‘tree’ structure described above is an integral part of the SNMP standard, though the most
pertinent parts of the tree are the ‘leaf’ objects of the tree that provide actual management data
regarding the device. Generally, SNMP leaf objects can be partitioned into two similar but slightly
different types that reflect the organization of the tree structure:
•
Discrete MIB Objects - Contain one precise piece of management data. These objects are
often distinguished from ‘Table’ items (below) by adding a ‘.0’ (dot-zero) extension to their
names. The operator must merely know the name of the object and no other information.
•
Table MIB Objects - Contain multiple sections of management data. These objects are
distinguished from ‘Discrete’ items (above) by requiring a ‘.’ (dot) extension to their names
that uniquely distinguishes the particular value being referenced. The ‘.’ (dot) extension is the
‘instance’ number of an SNMP object. For ‘Discrete’ objects, this instance number is zero.
For ‘Table’ objects, this instance number is the index into the SNMP table. SNMP tables are
special types of SNMP objects which allow parallel arrays of information to be supported.
Tables are distinguished from scalar objects, so that tables can grow without bounds. For
example, SNMP defines the ‘ifDescr’ object (as a standard SNMP object) that indicates the
text description of each interface supported by a particular device. Since network devices
can be configured with more than one interface, this object can only be represented as an
array.
By convention, SNMP objects are always grouped in an ‘Entry’ directory, within an object with a
‘Table’ suffix. (The ‘ifDescr’ object described above resides in the ‘ifEntry’ directory contained in
the ‘ifTable’ directory).
11.1.3 SNMP Extensibility Feature
One of the principal components of an SNMP manager is a MIB Compiler which allows new MIB
objects to be added to the management system. When a MIB is compiled into an SNMP
manager, the manager is made ‘aware’ of new objects that are supported by agents on the
network. The concept is similar to adding a new schema to a database.
Typically, when a MIB is compiled into the system, the manager creates new folders or directories
that correspond to the objects. These folders or directories can typically be viewed with a MIB
Browser, which is a traditional SNMP management tool incorporated into virtually all Network
Management Systems.
The act of compiling the MIB allows the manager to know about the special objects supported by
the agent and access these objects as part of the standard object set.
MP-1xx SIP User’s Manual
180
Document #: LTRT-65404
MP-1xx SIP User’s Manual
11. SNMP-Based Management
11.2 Carrier Grade Alarm System
The basic alarm system has been extended to a carrier-grade alarm system. A carrier-grade
alarm system provides a reliable alarm reporting mechanism that takes into account EMS
outages, network outages, and transport mechanism such as SNMP over UDP.
A carrier-grade alarm system is characterized by the following:
•
The device has a mechanism that allows a manager to determine which alarms are currently
active in the device. That is, the device maintains an active alarm table.
•
The device has a mechanism to allow a manager to detect lost alarm raise and clear
notifications [sequence number in trap, current sequence number MIB object].
•
The device has a mechanism to allow a manager to recover lost alarm raise and clear
notifications [maintains a log history].
•
The device sends a cold start trap to indicate that it is starting. This allows the EMS to
synchronize its view of the device's active alarms.
The SNMP alarm traps are sent as in previous releases. This system provides the mechanism for
viewing of history and current active alarm information.
11.2.1 Active Alarm Table
The device maintains an active alarm table to allow a manager to determine which alarms are
currently active in the device. Two views of the active alarm table are supported by the agent:
•
acActiveAlarmTable in the enterprise acAlarm
•
alarmActiveTable and alarmActiveVariableTable in the IETF standard ALARM-MIB (rooted in
the AC tree)
The acActiveAlarmTable is a simple, one-row per alarm table that is easy to view with a MIB
browser.
The ALARM-MIB is currently a draft standard and therefore has no OID assigned to it. In the
current software release, the MIB is rooted in the experimental MIB subtree. In a future release,
after the MIB has been ratified and an OID assigned, it is to move to the official OID.
11.2.2 Alarm History
The device maintains a history of alarms that have been raised and traps that have been cleared
to allow a manager to recover any lost, raised or cleared traps. Two views of the alarm history
table are supported by the agent:
•
acAlarmHistoryTable in the enterprise acAlarm
•
nlmLogTable and nlmLogVariableTable in the standard NOTIFICATION-LOG-MIB
As with the acActiveAlarmTable, the acAlarmHistoryTable is a simple, one-row-per-alarm table
that is easy to view with a MIB browser.
11.3 Cold Start Trap
MP-1xx technology supports a cold start trap to indicate that the device is starting. This allows the
manager to synchronize its view of the device's active alarms. Two different traps are sent at
start-up:
•
Version 4.4
The standard coldStart trap - iso(1).org(3).dod(6).internet(1). snmpV2(6). snmpModules(3).
snmpMIB(1). snmpMIBObjects(1). snmpTraps(5). coldStart(1) - sent at system initialization.
181
March 2005
MP-1xx SIP
•
The enterprise acBoardEvBoardStarted which is generated at the end of system
initialization. This is more of an ‘application-level’ cold start sent after the entire initializing
process is complete and all the modules are ready.
11.4 Third-Party Performance Monitoring
Measurements
Performance measurements are available for a third-party performance monitoring system
through an SNMP interface. These measurements can be polled at scheduled intervals by an
external poller or utility in a media server or other off-device system.
The device provides two types of performance measurements:
1.
Gauges: Gauges represent the current state of activities on the device. Gauges, unlike
counters, can decrease in value, and like counters, can increase. The value of a gauge is the
current value or a snapshot of the current activity on the device.
2.
Counters: Counters always increase in value and are cumulative. Counters, unlike gauges,
never decrease in value unless the off-device system is reset, the counters are then zeroed.
Performance measurements are provided by three proprietary MIBs (acPerfMediaGateway,
acPerfMediaServices and acPerfH323SIPGateway). The first MIB is a generic-type of
performance measurements MIB available on all MP-1xx and related devices. The second is
specific to the media server, and the third is for H.323/SIP media gateways.
The generic performance measurements MIB covers:
•
Control protocol
•
RTP stream
•
System packets statistics
Performance measurement enterprise
Proxy/Gatekeeper routing tables.
MIB
supports
statistics
which
apply
to
the
11.5 Supported MIBs
The MP-1xx contains an embedded SNMP Agent supporting the following MIBs:
•
Standard MIB (MIB-II) - The various SNMP values in the standard MIB are defined in RFC
1213. The standard MIB includes various objects to measure and monitor IP activity, TCP
activity, UDP activity, IP routes, TCP connections, interfaces and general system indicators.
•
RTP MIB - The RTP MIB is supported in conformance with the IETF RFC 2959. It contains
objects relevant to the RTP streams generated and terminated by the device and to RTCP
information related to these streams.
•
NOTIFICATION-LOG-MIB - This standard MIB (RFC 3014 - iso.org.dod.internet.mgmt.mib2) is supported as part of our implementation of carrier grade alarms.
•
ALARM-MIB - This is an IETF proposed MIB also supported as part of our implementation of
carrier grade alarms. This MIB is still not standard and is therefore under the
audioCodes.acExperimental branch.
•
SNMP-TARGET-MIB - This MIB is partially supported (RFC 2273). It allows for the
configuration of trap destinations and trusted managers only.
•
SNMP Research International Enterprise MIBs – MP-1xx supports two SNMP Research
International MIBs: SR-COMMUNITY-MIB and TGT-ADDRESS-MASK-MIB. These MIBs are
used in the configuration of SNMPv2c community strings and trusted managers.
In addition to the standard MIBs, the complete series contains several proprietary MIBs:
MP-1xx SIP User’s Manual
182
Document #: LTRT-65404
MP-1xx SIP User’s Manual
•
11. SNMP-Based Management
acBoard MIB - This proprietary MIB contains objects related to configuration of the device
and channels, as well as to run-time information. Through this MIB, users can set up the
device configuration parameters, reset the device, monitor the device’s operational
robustness and Quality of Service during run-time, and receive traps.
Note:
The acBoard MIB is still supported but is being replaced by five newer
proprietary MIBs.
The acBoard MIB has the following groups:
boardConfiguration
boardInformation
channelConfiguration
channelStatus
reset
acTrap
As noted above, five new MIBs cover the device’s general parameters. Each contains a
Configuration subtree for configuring related parameters. In some, there also are Status and
Action subtrees.
The 5 MIBs are:
1.
AC-ANALOG-MIB
2.
AC-CONTROL-MIB
3.
AC-MEDIA-MIB
4.
AC-PSTN-MIB
5.
AC-SYSTEM-MIB
Other proprietary MIBs are:
•
acGateway MIB - This proprietary MIB contains objects related to configuration of the device
when applied as a SIP or H.323 media gateway only. This MIB complements the other
proprietary MIBs.
The acGateway MIB has the following groups:
•
Common
- for parameters common to both SIP and H.323
SIP
- for SIP parameters only
H.323
- for H.323 parameters only
acAlarm - This is a proprietary carrier-grade alarm MIB. It is a simpler implementation of the
notificationLogMIB and the IETF suggested alarmMIB (both also supported in all MP-1xx and
related devices).
The acAlarm MIB has the following groups:
ActiveAlarm - straightforward (single-indexed) table, listing all currently active alarms,
together with their bindings (the alarm bindings are defined in acAlarm. acAlarmVarbinds
and also in acBoard.acTrap. acBoardTrapDefinitions.
oid_1_3_6_1_4_1_5003_9_10_1_21_2_0).
acAlarmHistory - straightforward (single-indexed) table, listing all recently raised alarms
together with their bindings (the alarm bindings are defined in acAlarm. acAlarmVarbinds
and also in acBoard.acTrap. acBoardTrapDefinitions.
oid_1_3_6_1_4_1_5003_9_10_1_21_2_0).
Version 4.4
183
March 2005
MP-1xx SIP
The table size can be altered via
notificationLogMIB.notificationLogMIBObjects.nlmConfig.nlmConfigGlobalEntryLimit or
notificationLogMIB.notificationLogMIBObjects.nlmConfig.nlmConfigLogTable.nlm
ConfigLogEntry.nlmConfigLogEntryLimit.
The table size can be any value between 10 to 100 and is 100 by default.
•
Traps
Full proprietary trap definitions and trap Varbinds are found in the acBoard MIB and acAlarm
MIB.
The following proprietary traps are supported in the device:
acBoardEvResettingBoard - Sent after the device is reset.
acBoardEvBoardStarted - Sent after the device is successfully restored and initialized
following reset.
acBoardConfigurationError - Sent when a device’s settings are illegal - the trap contains
a message stating/detailing/explaining the illegality of the setting.
acBoardFatalError - Sent whenever a fatal device error occurs.
acBoardCallResourcesAlarm - Indicates that no free channels are available.
acBoardControllerFailureAlarm - The Gatekeeper/Proxy is not found or registration
failed. Internal routing table can be used for routing.
acBoardEthernetLinkAlarm - Ethernet link or links are down.
acBoardOverloadAlarm - Overload in one or some of the system's components.
acActiveAlarmTableOverflow - An active alarm could not be placed in the active alarm
table because the table is full.
In addition to the listed traps, the device also supports the following standard traps:
coldStart
authenticationFailure
The following are special notes pertaining to MIBs:
Note 1:
Note 2:
•
A detailed explanation of each parameter can be viewed in an SNMP
browser in the ‘MIB Description’ field.
•
Not all groups in the MIB are functional. Refer to version release notes.
•
Certain parameters are non-functional. Their MIB status is marked
'obsolete'.
•
When a parameter is set to a new value via SNMP, the change may affect
device functionality immediately or may require that the device be soft
reset for the change to take effect. This depends on the parameter type.
The current (updated) device configuration parameters are programmed into
the device provided that the user does not load an ini file to the device after
reset. Loading an ini file after reset overrides the updated parameters.
Additional MIBs are to be supported in future releases.
MP-1xx SIP User’s Manual
184
Document #: LTRT-65404
MP-1xx SIP User’s Manual
11. SNMP-Based Management
11.6 SNMP Interface Details
This section describes details of the SNMP interface that is required when developing an Element
Manager (EM) for any of the media gateways, or to manage a device with a MIB browser.
Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file
encoding, refer to Section F.1.2 on page 221.
11.6.1 SNMP Community Names
By default, the device uses a single, read-only community string of ‘public’ and a single read-write
community string of ‘private’.
Users can configure up to 5 read-only community strings and up to 5 read-write community
strings, and a single trap community string is supported:
11.6.1.1 Configuration of Community Strings via the ini File
SNMPREADONLYCOMMUNITYSTRING_<x> = '#######'
SNMPREADWRITECOMMUNITYSTRING_<x> = '#######'
where <x> is a number between 0 and 4, inclusive. Note that the '#' character represents any
alphanumeric character. The maximum length of the string is 20 characters.
11.6.1.2 Configuration of Community Strings via SNMP
To configure read-only and read-write community strings, the EM must use the srCommunityMIB.
To configure the trap community string, the EM must also use the snmpVacmMIB and the
snmpTargetMIB.
To add a read-only community string (v2user):
•
Add a new row to the srCommunityTable with CommunityName v2user and GroupName
ReadGroup.
To delete the read-only community string (v2user), take these 2 steps:
1.
If v2user is being used as the trap community string, follow the procedure for changing the
trap community string (see below).
2.
Delete the srCommunityTable row with CommunityName v2user.
To add a read-write community string (v2admin):
•
Add a new row to the srCommunityTable with CommunityName of v2admin and GroupName
ReadWriteGroup.
To delete the read-write community string (v2admin), take these 2 steps:
1.
If v2admin is being used as the trap community string, follow the procedure for changing the
trap community string. (See below.)
2.
Delete the srCommunityTable row with a CommunityName of v2admin and GroupName of
ReadWriteGroup.
Version 4.4
185
March 2005
MP-1xx SIP
To change the only read-write community string from v2admin to v2mgr,
take these 4 steps:
1.
Follow the procedure above to add a read-write community string to a row for v2mgr.
2.
Set up the EM so that subsequent ‘set’ requests use the new community string, v2mgr.
3.
If v2admin is being used as the trap community string, follow the procedure to change the
trap community string (see below).
4.
Follow the procedure above to delete a read-write community name in the row for v2admin.
To change the trap community string, take these 2 steps:
(The following procedure assumes that a row already exists in the srCommunityTable for the new
trap community string. The trap community string can be part of the TrapGroup, ReadGroup or
ReadWriteGroup. If the trap community string is used solely for sending traps (recommended), it
should be made part of the TrapGroup).
1.
Add a row to the vacmSecurityToGroupTable with these values: SecurityModel=2,
SecurityName=the new trap community string, GroupName=TrapGroup, ReadGroup or
ReadWriteGroup. The SecurityModel and SecurityName objects are row indices.
Note:
2.
You must add GroupName and RowStatus on the same set.
Modify the SecurityName field in the sole row of the snmpTargetParamsTable.
11.6.2 Trusted Managers
By default, the agent accepts ‘get’ and ‘set’ requests from any IP address, as long as the correct
community string is used in the request. Security can be enhanced via the use of Trusted
Managers. A Trusted Manager is an IP address from which the SNMP Agent accepts and
processes ‘get’ and ‘set’ requests. An EM can be used to configure up to 5 Trusted Managers.
Note:
If Trusted Managers are defined, all community strings work from all Trusted
Managers. That is, there is no way to associate a community string with
particular trusted managers.
11.6.2.1 Configuration of Trusted Managers via ini File
To set the Trusted Mangers table from start-up, write the following in the ini file:
SNMPTRUSTEDMGR_X = D.D.D.D
where X is any integer between 0 and 4 (0 sets the first table entry, 1 sets the second, and so
on), and D is an integer between 0 and 255.
11.6.2.2 Configuration of Trusted Managers via SNMP
To configure Trusted Managers, the EM must use the srCommunityMIB, the snmpTargetMIB and
the TGT-ADDRESS-MASK-MIB.
To add the first Trusted Manager, take these 3 steps:
(The following procedure assumes that there is at least one configured read-write community.
There are currently no Trusted Managers. The taglist for columns for all srCommunityTable rows
MP-1xx SIP User’s Manual
186
Document #: LTRT-65404
MP-1xx SIP User’s Manual
11. SNMP-Based Management
are currently empty).
1.
Add a row to the snmpTargetAddrTable with these values: Name=mgr0, TagList=MGR,
Params=v2cparams.
2.
Add a row to the tgtAddressMaskTable table with these values: Name=mgr0,
tgtAddressMask=255.255.255.255:0. The agent doesn’t allow creation of a row in this table
unless a corresponding row exists in the snmpTargetAddrTable.
3.
Set the value of the TransportLabel field on each non-TrapGroup row in the
srCommunityTable to MGR.
To add a subsequent Trusted Manager, take these 2 steps:
(The following procedure assumes that there is at least one configured read-write community.
There are currently one or more Trusted Managers. The taglist for columns for all rows in the
srCommunityTable are currently set to MGR. This procedure must be performed from one of the
existing Trusted Managers).
1.
Add a row to the snmpTargetAddrTable with these values: Name=mgrN, TagList=MGR,
Params=v2cparams, where N is an unused number between 0 and 4.
2.
Add a row to the tgtAddressMaskTable table with these values: Name=mgrN,
tgtAddressMask=255.255.255.255:0.
An alternative to the above procedure is to set the tgtAddressMask column while you are
creating other rows in the table.
To delete a Trusted Manager (not the final one), take this step:
(The following procedure assumes that there is at least one configured read-write community.
There are currently two or more Trusted Managers. The taglist for columns for all rows in the
srCommunityTable are currently set to MGR. This procedure must be performed from one of the
existing trusted managers, but not the one that is being deleted.
•
Remove the appropriate row from the snmpTargetAddrTable.
The change takes effect immediately. The deleted trusted manager cannot access the device.
The agent automatically removes the row in the tgtAddressMaskTable.
To delete the final Trusted Manager, take these 2 steps:
(The following procedure assumes that there is at least one configured read-write community.
There is currently only one Trusted Manager. The taglist for columns for all rows in the
srCommunityTable are currently set to MGR. This procedure must be performed from the final
Trusted Manager.
1.
Set the value of the TransportLabel field on each row in the srCommunityTable to the empty
string.
2.
Remove the appropriate row from the snmpTargetAddrTable
The change takes effect immediately. All managers can now access the device.
11.6.3 SNMP Ports
The SNMP Request Port is 161 and the Trap Port is 162. These ports can be changed by setting
parameters in the device ini file. The parameter name is:
SNMPPort = <port_number>
Valid UDP port number; default = 161
This parameter specifies the port number for SNMP requests and responses. Usually, it should
not be specified. Use the default.
Version 4.4
187
March 2005
MP-1xx SIP
11.6.4 Multiple SNMP Trap Destinations
An agent can now send traps to up to five managers. For each manager, set the following
parameters defined in the snmpManagersTable in the acBoardMIB:
•
snmpTrapManagerSending
•
snmpManagerIsUsed
•
snmpManagerTrapPort
•
snmpManagerIP
When snmpManagerIsUsed is set to zero (not used), the other three parameters are set to zero.
•
snmpManagerIsUsed (Default = Disable(0))
The allowed values are 0 (disable or no) and 1 (enable or yes).
•
snmpManagerIp (Default = 0.0.0.0)
This is known as SNMPMANAGERTABLEIP in the ini file and is the IP address of the
manager.
•
SnmpManagerTrapPort (Default = 162)
The valid port range for this is 100-4000.
•
snmpManagerTrapSendingEnable (Default = Enable(1))
The allowed values are 0 (disable) and 1 (enable).
Note 1:
Each of these MIB objects is independent and can be set regardless of the
state of snmpManagerIsUsed.
Note 2:
If the parameter IsUsed is set to 1, the IP address for that row should be
supplied in the same SNMP PDU.
11.6.4.1 Configuration via the ini File
In the MP-1xx ini file, the parameters below can be set to enable or disable the sending of SNMP
traps. Multiple trap destinations can be supported on the device by setting multiple trap
destinations in the ini file.
SNMPMANAGERTRAPSENDINGENABLE_<x> = 0 or 1 indicates if traps are to be sent to the
specified SNMP trap manager. A value of ‘1’ means that it is enabled, while a value of ‘0’ means
disabled.
<x> = a number 0, 1, 2 which is the array element index. Currently, up to 5 SNMP trap managers
can be supported.
Figure 11-1 presents an example of entries in a device ini file regarding SNMP. The device can
be configured to send to multiple trap destinations. The lines in the file below are commented out
with the ‘;’ at the beginning of the line. All of the lines below are commented out since the first line
character is a semi-colon.
MP-1xx SIP User’s Manual
188
Document #: LTRT-65404
MP-1xx SIP User’s Manual
11. SNMP-Based Management
Figure 11-1: Example of Entries in a Device ini file Regarding SNMP
; SNMP trap destinations
; The board maintains a table of trap destinations containing 5 ;rows. The rows are
numbered 0..4. Each block of 4 items below ;apply to a row in the table.
; To configure one of the rows, uncomment all 4 lines in that ;block. Supply an IP
address and if necessary, change the port ;number.
; To delete a trap destination, set ISUSED to 0.
; -change these entries as needed
;SNMPManagerTableIP_0=
;SNMPManagerTrapPort_0=162
;SNMPManagerIsUsed_0=1
;SNMPManagerTrapSendingEnable_0=1
;
;SNMPManagerTableIP_1=
;SNMPManagerTrapPort_1=162
;SNMPManagerIsUsed_1=1
;SNMPManagerTrapSendingEnable_1=1
;
;SNMPManagerTableIP_2=
;SNMPManagerTrapPort_2=162
;SNMPManagerIsUsed_2=1
;SNMPManagerTrapSendingEnable_2=1
;
;SNMPManagerTableIP_3=
;SNMPManagerTrapPort_3=162
;SNMPManagerIsUsed_3=1
;SNMPManagerTrapSendingEnable_3=1
;
;SNMPManagerTableIP_4=
;SNMPManagerTrapPort_4=162
;SNMPManagerIsUsed_4=1
;SNMPManagerTrapSendingEnable_4=1
Note:
The same information configurable in the ini file can also be configured via
the acBoardMIB.
11.6.4.2 Configuration via SNMP
To configure trap destinations, the EM must use the snmpTargetMIB. Up to 5 trap destinations
can be configured.
To add a trap destination:
•
Add a row to the snmpTargetAddrTable with these values:
Name=trapN, TagList=AC_TRAP, Params=v2cparams, where N is an unused number
between 0 and 4.
All changes to the trap destination configuration take effect immediately.
To delete a trap destination:
•
Remove the appropriate row from the snmpTargetAddrTable.
To modify a trap destination:
(You can change the IP address and/or port number for an existing trap destination. The same
effect can be achieved by removing a row and adding a new row).
Version 4.4
189
March 2005
MP-1xx SIP
•
Modify the IP address
snmpTargetAddrTable.
and/or
port
number
for
the
appropriate
row
in
the
To disable a trap destination:
•
Change TagList on the appropriate row in the snmpTargetAddrTable to the empty string.
To enable a trap destination:
•
Change TagList on the appropriate row in the snmpTargetAddrTable to ‘AC_TRAP’.
11.7 SNMP Manager Backward Compatibility
With support for the Multi Manager Trapping feature, the older acSNMPManagerIP MIB object,
synchronized with the first index in the snmpManagers MIB table, is also supported. This is
translated in two features:
•
SET/GET to either of the two MIB objects is identical.
i.e., as far as the SET/GET are concerned OID 1.3.6.1.4.1.5003.9.10.1.1.2.7 is identical to
OID 1.3.6.1.4.1.5003.9.10.1.1.2.21.1.1.3.
•
When setting ANY IP to the acSNMPManagerIP (this is the older parameter, not the table
parameter), two more parameters are SET to ENABLE. snmpManagerIsUsed.0 and
snmpManagerTrapSendingEnable.0 are both set to 1.
11.8 AudioCodes’ Element Management System
Using AudioCodes’ Element Management System (EMS) is recommended to Customers
requiring large deployments (multiple media gateways in globally distributed enterprise offices, for
example), that need to be managed by central personnel.
The EMS is not included in the device’s supplied package. Contact AudioCodes for detailed
information on AudioCodes’ EMS and on AudioCodes’ EVN - Enterprise VoIP Network – solution
for large VoIP deployments.
MP-1xx SIP User’s Manual
190
Document #: LTRT-65404
MP-1xx SIP User’s Manual
12
12. Selected Technical Specifications
Selected Technical Specifications
Table 12-1: MP-1xx Selected Technical Specifications (continues on pages 191 to 193)
MP-1xx/FXS Functionality
FXS Capabilities
Short or Long Haul:
MP-10x/FXS:
up to 15k feet (4,600 m) using 24 AWG line cord.
up to 24k feet (7,300 m) using 26 AWG line cord.
MP-124/FXS:
up to 10k feet (3,000 m) using 24 AWG line cord.
Note: The lines were tested under the following conditions: ring voltage greater than
30 Vrms, offhook loop current greater than 20 mA.
MP-104 and MP-108 (special order option, using different assembly), includes
lightning and high voltage protection for outdoor operation.
Caller ID generation: Bellcore GR-30-CORE Type 1 using Bell 202 FSK modulation,
ETSI Type 1, NTT, Denmark, India, Sweden, Brazil, British and DTMF ETSI CID
(ETS 300-659-1).
Programmable Line Characteristics: Battery feed, line current, hook thresholds, AC
impedance matching, hybrid balance, Tx & Rx frequency response, Tx & Rx Gains.
Programmable ringing signal. Up to three cadences and frequency 10 to 200 Hz.
Drive up to 4 phones per port (total 32 phones) simultaneously in offhook and Ring
states.
MP-124 REN = 2
MP-10x REN = 5
Over-temperature protection for abnormal situations as shorted lines.
Loop-backs for testing and maintenance.
MP-10x/FXO Functionality
FXO Capabilities
Short or Long Haul up to 24k feet (7,300 m) using 24 AWG line cord.
(does not apply to MP-102 and Includes lightning and high voltage protection for outdoor operation.
MP-124)
Programmable Line Characteristics: AC impedance matching, hybrid balance, Tx &
Rx frequency response, Tx & Rx Gains, ring detection threshold, DC characteristics.
Caller ID detection: Bellcore GR-30-CORE Type 1 using Bell 202 FSK modulation,
ETSI Type 1, NTT, Denmark, India, Sweden, Brazil, British and DTMF ETSI CID
(ETS 300-659-1).
Voice & Tone Characteristics
Voice Compression
G.711 PCM at 64 kbps µ-law/A-law
G.723.1 MP-MLQ at 5.3 or 6.3 kbps
G.726 at 32 kbps ADPCM
G.729 CS-ACELP 8 Kbps Annex A / B
Silence Suppression
G.723.1 Annex A
G.729 Annex B
PCM and ADPCM - Standard Silence Descriptor (SID) with Proprietary Voice Activity
Detection (VAD) and Comfort Noise Generation (CNG).
Packet Loss Concealment
G.711 appendix 1
G.723.1
G.729 a/b
Echo Canceler
G.165 and G.168 2000, 25 msec with extension to 40 msec
DTMF Transport (in-band)
Mute, transfer in RTP payload or relay in compliance with RFC 2833
DTMF Detection and
Generation
Dynamic range 0 to -25 dBm, compliant with TIA 464B and Bellcore TR-NWT000506.
Call Progress Tone
Detection and Generation
16 tones: single tone or dual tones, programmable frequency & amplitude; 15
frequencies in the range 300 to 1980 Hz, 1 or 2 cadences per tone, up to 2 sets of
ON/OFF periods.
Output Gain Control
-32 dB to +31 dB in steps of 1 dB
Input Gain Control
-32 dB to +31 dB in steps of 1 dB
Version 4.4
191
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
(30, 60, 90, 120, 150 msec)
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
(10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
March 2005
MP-1xx SIP
Table 12-1: MP-1xx Selected Technical Specifications (continues on pages 191 to 193)
Fax and Modem Transport Modes
Real time Fax Relay
Group 3 real-time fax relay up to 14400 bps with auto fallback
Tolerant network delay (up to 9 seconds round trip delay)
T.30 (PSTN) and T.38 (IP) compliant (real-time fax)
CNG tone detection & Relay per T.38
Answer tone (CED or AnsAm) detection & Relay per T.38
Fax Transparency
Automatic fax bypass (pass-through) to G.711, ADPCM or NSE bypass mode
Modem Transparency
Automatic switching (pass-through) to PCM, ADPCM or NSE bypass mode for modem
signals (V.34 or V.90 modem detection)
Protocols
VoIP Signaling Protocol
SIP RFC 3261
Communication Protocols
RTP/RTCP packetization.
IP stack (UDP, TCP, RTP).
Remote Software load (TFTP & BootP, DHCP support).
Line Signaling Protocols
Loop start, FXS and FXO
Interfaces
FXS Telephony Interface
2, 4, 8 or 24 Analog FXS phone or fax ports, loop start
FXO Telephony Interface
4 or 8 Analog FXO PSTN/PBX loop start ports
Network Interface
RJ-45 shielded connector, 10/100 Base-TX.
RS-232 Interface
RS-232 Terminal Interface for maintenance, diagnostic reports and code tracing. DB9 connector on rear panel
Lifeline (MP-10x/FXS)
Lifeline provides a wired analog POTS phone connection to any PSTN or PBX FXS
port when there is no power, or the network fails (refer to Section 3.4.1 on page 32
for details). Does NOT function with MP-124 and MP-10x/FXO gateways.
Connectors & Switches
Rear Panel
24 Analog Lines (MP-124)
50-pin Telco shielded connector
8 Analog Lines (MP-108)
8 RJ-11 connectors
4 Analog Lines (MP-104)
4 RJ-11 connectors
2 Analog Lines (MP-102)
2 RJ-11 connectors
Ethernet
10/100 Base-TX, RJ-45 shielded connector
RS-232
Console port - DB-9
Front Panel
Reset
Resets the MP-1xx
Physical
MP-10x Enclosure
Dimensions
Width:
Height:
Depth:
Weight:
MP-124 Enclosure
Dimensions
1U, 19-inch Rack
Width:
Height:
Depth:
Weight:
Environmental
Operational:
Storage:
Humidity:
Installation
Desk-top, shelf, or 19-inch rack mount with side brackets.
Electrical
Universal 90-264 VAC, 1A, 47-63 Hz
2A for MP-124
MP-1xx SIP User’s Manual
221 mm
44.5 mm
240 mm
1.24 kg
8.7 in
1.75 in
9.5 in
2.5 lb
445 mm 17.5 in
44.5 mm 1.75 in
269 mm 10.6 in
2.24 kg 4.9 lb
-5° to 55° C23° to 131° F
-40° to 70° C -40° to 158° F
10 to 90% non-condensing
192
Document #: LTRT-65404
MP-1xx SIP User’s Manual
12. Selected Technical Specifications
Table 12-1: MP-1xx Selected Technical Specifications (continues on pages 191 to 193)
MP-124 only, DC power supply 40-60 VDC, 2A
Type Approvals
Telecommunication
FCC part 68 & CE CTR21, ASIF S003 (FXS)
Safety and EMC
UL 60950-1, FCC part 15 Class B
CE Mark (EN 60950-1, EN 55022, EN 55024)
Management
Configuration
Gateway configuration using Web browser, ini files or local RS-232 console
Management and
Maintenance
SNMP v2c
Syslog, per RFC 3164
Local RS-232 terminal
Web Management (via HTTP)
All specifications in this document are subject to change without prior notice.
Version 4.4
193
March 2005
MP-1xx SIP
Reader's Notes
MP-1xx SIP User’s Manual
194
Document #: LTRT-65404
MP-1xx SIP User’s Manual
A. MP-1xx SIP Software Kit
Appendix A MP-1xx SIP Software Kit
Table A-1 describes the standard supplied software kit for MP-1xx FXS/FXO SIP gateways. The
supplied documentation includes this User’s Manual, the MP-1xx Fast Track and the MP-1xx SIP
Release Notes.
Table A-1: MP-1xx SIP Supplied Software Kit
File Name
Description
Ram.cmp files
MP124_SIP_xxx.cmp
Image file containing the software for the MP-124/FXS gateway.
MP108_SIP_xxx.cmp
Common Image file Image file containing the software for both MP-10x/FXS and MP10x/FXO gateways.
ini files and utilities
SIPgw_MP124.ini
Sample Ini file for MP-124/FXS gateway.
SIPgw_fxs_MP108.ini
Sample ini file for MP-108/FXS gateways.
SIPgw_fxo_MP108.ini
Sample ini file for MP-108/FXO gateways.
SIPgw_fxs_MP104.ini
Sample ini file for MP-104/FXS gateways.
SIPgw_fxo_MP104.ini
Sample ini file for MP-104/FXO gateways.
SIPgw_fxs_MP102.ini
Sample ini file for MP-102/FXS gateways.
Usa_tones_xx.dat
Default loadable Call Progress Tones dat file.
Usa_tones_xx.ini
Call progress Tones ini file (used to create dat file).
MP1xx_Coeff_FXS.dat
Telephony interface configuration file for MP-1xx/FXS gateways.
MP10x_Coeff_FXO.dat
Telephony interface configuration file for MP-10x/FXO gateways.
DConvert240.exe
TrunkPack Downloadable Conversion Utility
ACSyslog08.exe
Syslog server.
bootp.exe
BootP/TFTP configuration utility
CPTWizard.exe
Call Progress Tones Wizard
MIBs Files
MIB library for SNMP browser
Version 4.4
195
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
196
Document #: LTRT-65404
MP-1xx SIP User’s Manual
B. The BootP/TFTP Configuration Utility
Appendix B The BootP/TFTP Configuration Utility
The BootP/TFTP utility enables you to easily configure and provision our boards and media
gateways. Similar to third-party BootP/TFTP utilities (which are also supported) but with added
functionality; our BootP/TFTP utility can be installed on Windows™ 98 or Windows™
NT/2000/XP. The BootP/TFTP utility enables remote reset of the device to trigger the initialization
procedure (BootP and TFTP). It contains BootP and TFTP utilities with specific adaptations to our
requirements.
B.1
When to Use the BootP/TFTP
The BootP/TFTP utility can be used with the device as an alternative means of initializing the
gateways. Initialization provides a gateway with an IP address, subnet mask, and the default
gateway IP address. The tool also loads default software, ini and other configuration files. BootP
Tool can also be used to restore a gateway to its initial configuration, such as in the following
instances:
•
The IP address of the gateway is not known.
•
The Web browser has been inadvertently turned off.
•
The Web browser password has been forgotten.
•
The gateway has encountered a fault that cannot be recovered using the Web browser.
Tip:
B.2
The BootP is normally used to configure the device’s initial parameters.
Once this information has been provided, the BootP is no longer needed. All
parameters are stored in non-volatile memory and used when the BootP is
not accessible.
An Overview of BootP
BootP is a protocol defined in RFC 951 and RFC 1542 that enables an internet device to discover
its own IP address and the IP address of a BootP on the network, and to obtain the files from that
utility that need to be loaded into the device to function.
A device that uses BootP when it powers up broadcasts a BootRequest message on the network.
A BootP on the network receives this message and generates a BootReply. The BootReply
indicates the IP address that should be used by the device and specifies an IP address from
which the unit may load configuration files using Trivial File Transfer Protocol (TFTP) described in
RFC 906 and RFC 1350.
B.3
Key Features
•
Internal BootP supporting hundreds of entities.
•
Internal TFTP.
•
Contains all required data for our products in predefined format.
•
Provides a TFTP address, enabling network separation of TFTP and BootP utilities.
•
Tools to backup and restore the local database.
•
Templates.
•
User-defined names for each entity.
•
Option for changing MAC address.
Version 4.4
197
March 2005
MP-1xx SIP
B.4
B.5
•
Protection against entering faulty information.
•
Remote reset.
•
Unicast BootP response.
•
User-initiated BootP respond, for remote provisioning over WAN.
•
Filtered display of BootP requests.
•
Location of other BootP utilities that contain the same MAC entity.
•
Common log window for both BootP and TFTP sessions.
•
Works with Windows™ 98, Windows™ NT, Windows™ 2000 and Windows™ XP.
Specifications
•
BootP standards: RFC 951 and RFC 1542
•
TFTP standards: RFC 1350 and RFC 906
•
Operating System: Windows™ 98, Windows™ NT, Windows™ 2000 and Windows™ XP
•
Max number of MAC entries: 200
Installation
To install the BootP/TFTP on your computer, take these 2 steps:
1.
Locate the BootP folder on the VoIP gateway supplied CD ROM and open the file Setup.exe.
2.
Follow the prompts from the installation wizard to complete the installation.
To open the BootP/TFTP, take these 2 steps:
B.6
1.
From the Start menu on your computer, navigate to Programs and then click on BootP.
2.
The first time that you run the BootP/TFTP, the program prompts you to set the user
preferences. Refer to the Section B.10 on page 201 for information on setting the
preferences.
Loading the cmp File, Booting the Device
Once the application is running, and the preferences were set (refer to Section B.10), for each
unit that is to be supported, enter parameters into the tool to set up the network configuration
information and initialization file names. Each unit is identified by a MAC address. For information
on how to configure (add, delete and edit) units refer to Section B.11 on page 203.
To load the software and configuration files, take these 4 steps:
1.
Create a folder on your computer that contains all software and configuration files that are
needed as part of the TFTP process.
2.
Set the BootP and TFTP preferences (refer to Section B.10).
3.
Add client configuration for the VoIP gateway that you want to initialize by the BootP, refer to
Section B.11.1.
4.
Reset the VoIP gateway, either physically or remotely, causing the device to use BootP to
access the network and configuration information.
MP-1xx SIP User’s Manual
198
Document #: LTRT-65404
MP-1xx SIP User’s Manual
B.7
B. The BootP/TFTP Configuration Utility
BootP/TFTP Application User Interface
Figure B-1 shows the main application screen for the BootP/TFTP utility.
Figure B-1: Main Screen
Log Window
B.8
Function Buttons on the Main Screen
Pause: Click this button to pause the BootP Tool so that no replies are sent to BootP
requests. Click the button again to restart the BootP Tool so that it responds to all
BootP requests. The Pause button provides a depressed graphic when the feature is
active.
Edit Clients: Click this button to open a new window that enables you to enter
configuration information for each supported VoIP gateway. Details on the Clients
window are provided in Section B.11 on page 203.
Edit Templates: Click this button to open a new window that enables you to create or
edit standard templates. These templates can be used when configuring new clients
that share most of the same settings. Details on the Templates window are provided
in Section B.12 on page 207.
Clear Log: Click this button to clear all entries from the Log Window portion of the
main application screen. Details on the log window are provided in Section B.9 on
page 200.
Filter Clients: Click this button to prevent the BootP Tool from logging BootP requests
received from disabled clients or from clients which do not have entries in the Clients
table.
Reset: Click this button to open a new window where you enter an IP address
requests for a gateway that you want to reset. Refer to Figure B-2 below.
Figure B-2: Reset Screen
Version 4.4
199
March 2005
MP-1xx SIP
When a gateway resets, it first sends a BootRequest. Therefore, Reset can be used to force a
BootP session with a gateway without needing to power cycle the gateway. As with any BootP
session, the computer running the BootP Tool must be located on the same subnet as the
controlled VoIP gateway.
B.9
Log Window
The log window (refer to Figure B-1 on the previous page) records all BootP request and BootP
reply transactions, as well as TFTP transactions. For each transaction, the log window displays
the following information:
•
Client: shows the Client address of the VoIP gateway, which is the MAC address of the
client for BootP transactions or the IP address of the client for TFTP transactions.
•
Date: shows the date of the transaction, based on the internal calendar of the computer.
•
Time: shows the time of day of the transaction, based on the internal clock of the computer.
•
Status: indicates the status of the transaction.
Client Not Found: A BootRequest was received but there is no matching client entry in
the BootP Tool.
Client Found: A BootRequest was received and there is a matching client entry in the
BootP Tool. A BootReply is sent.
Client’s MAC Changed: There is a client entered for this IP address but with a different
MAC address.
Client Disabled: A BootRequest was received and there is a matching client entry in the
BootP tool but this entry is disabled.
Listed At: Another BootP utility is listed as supporting a particular client when the Test
Selected Client button is clicked (for details on Testing a client refer to Section B.11.4 on
page 204).
Download Status: Progress of a TFTP load to a client, shown in %.
•
New IP / File: shows the IP address applied to the client as a result of the BootP transaction,
as well as the file name and path of a file transfer for a TFTP transaction.
•
Client Name: shows the client name, as configured for that client in the Client Configuration
screen.
Use right-click on a line in the Log Window to open a pop-up window with the following options:
•
Reset: Selecting this option results in a reset command being sent to the client VoIP
gateway. The program searches its database for the MAC address indicated in the line. If the
client is found in that database, the program adds the client MAC address to the Address
Resolution Protocol (ARP) table for the computer. The program then sends a reset
command to the client. This enables a reset to be sent without knowing the current IP
address of the client, as long as the computer sending the reset is on the same subnet.
Note: In order to use reset as described above, the user must have administrator privileges
on the computer. Attempting to perform this type of reset without administrator privileges on
the computer results in an error message. ARP Manipulation Enable must also be turned
on in the Preferences window.
•
View Client: Selecting this option, or double clicking on the line in the log window, opens the
Client Configuration window. If the MAC address indicated on the line exists in the client
database, it is highlighted. If the address is not in the client database, a new client is added
with the MAC address filled out. You can enter data in the remaining fields to create a new
client entry for that client.
MP-1xx SIP User’s Manual
200
Document #: LTRT-65404
MP-1xx SIP User’s Manual
B. The BootP/TFTP Configuration Utility
B.10 Setting the Preferences
The Preferences window, Figure B-3, is used to configure the BootP Tool parameters.
Figure B-3: Preferences Screen
B.10.1 BootP Preferences
ARP is a common acronym for Address Resolution Protocol, and is the method used by all
Internet devices to determine the link layer address, such as the Ethernet MAC address, in order
to route Datagrams to devices that are on the same subnet.
When ARP Manipulation is enabled on this screen, the BootP Tool creates an ARP cache entry
on your computer when it receives a BootP BootRequest from the VoIP gateway. Your computer
uses this information to send messages to the VoIP gateway without using ARP again. This is
particularly useful when the gateway does not yet have an IP address and, therefore, cannot
respond to an ARP.
Because this feature creates an entry in the computer ARP cache, Administrator Privileges are
required. If the computer is not set to allow administrator privileges, ARP Manipulation cannot be
enabled.
•
ARP Manipulation Enabled: Enable ARP Manipulation to remotely reset a gateway that
does not yet have a valid IP address.
If ARP Manipulation is enabled, the following two commands are available.
•
Version 4.4
Reply Type: Reply to a BootRequest can be either Broadcast or Unicast. The default for
the BootP Tool is Broadcast. In order for the reply to be set to Unicast, ARP Manipulation
must first be enabled. This then enables the BootP Tool to find the MAC address for the
client in the ARP cache so that it can send a message directly to the requesting device.
Normally, this setting can be left at Broadcast.
201
March 2005
MP-1xx SIP
•
ARP Type: The type of entry made into the ARP cache on the computer, once ARP
Manipulation is enabled, can be either Dynamic or Static. Dynamic entries expire after a
period of time, keeping the cache clean so that stale entries do not consume computer
resources. The Dynamic setting is the default setting and the setting most often used. Static
entries do not expire.
•
Number of Timed Replies: This feature is useful for communicating to VoIP gateways that
are located behind a firewall that would block their BootRequest messages from getting
through to the computer that is running the BootP Tool. You can set this value to any whole
digit. Once set, the BootP Tool can send that number of BootReply messages to the
destination immediately after you send a remote reset to a VoIP gateway at a valid IP
address. This enables the replies to get through to the VoIP gateway even if the
BootRequest is blocked by the firewall. To turn off this feature, set the Number of Timed
Replies = 0.
B.10.2 TFTP Preferences
•
Enabled: To enable the TFTP functionality of the BootP Tool, check the box beside this
heading. If you want to use another TFTP application, other than the one included with the
BootP Tool, unselect the box.
•
On Interface: This pull down menu displays all network interfaces currently available on the
computer. Select the interface that you want to use for the TFTP. Normally, there is only one
choice.
•
Directory: This option is enabled only when the TFTP is enabled. Use this parameter to
specify the folder that contains the files for the TFTP utility to manage (cmp, ini, Call
Progress Tones, etc.).
•
Boot File Mask: Boot File Mask specifies the file extension used by the TFTP utility for the
boot file that is included in the BootReply message. This is the file that contains VoIP
gateway software and normally appears as cmp.
•
ini File Mask: ini File mask specifies the file extension used by the TFTP utility for the
configuration file that is included in the BootReply message. This is the file that contains
VoIP gateway configuration parameters and normally appears as ini.
•
Timeout: This specifies the number of seconds that the TFTP utility waits before
retransmitting TFTP messages. This can be left at the default value of 5 (the more
congested your network, the higher the value you should define in these fields).
•
Maximum Retransmissions: This specifies the number of times that the TFTP utility tries to
resend messages after timing out. This can be left at the default value of 10 (the more
congested your network, the higher the value you should define in these fields).
MP-1xx SIP User’s Manual
202
Document #: LTRT-65404
MP-1xx SIP User’s Manual
B. The BootP/TFTP Configuration Utility
B.11 Configuring the BootP Clients
The Clients window, shown in Figure B-4 below, is used to set up the parameters for each
specific VoIP gateway.
Figure B-4: Client Configuration Screen
B.11.1 Adding Clients
Adding a client creates an entry in the BootP Tool for a specific gateway.
To add a client to the list without using a template, take these 3 steps:
1.
Click on the Add New Client Icon;
a client with blank parameters is displayed.
2.
Enter values in the fields on the right side of the window, using the guidelines for the fields in
Section B.11.5 on page 205.
3.
Click Apply to save this entry to the list of clients, or click Apply & Reset to save this entry
to the list of clients and send a reset message to that gateway to immediately implement the
settings.
Note: To use Apply & Reset you must enable ARP Manipulation in the Preferences
window. Also, you must have administrator privileges for the computer you are using.
An easy way to create several clients that use similar settings is to create a template. For
information on how to create a template refer to Section B.12 on page 207.
Version 4.4
203
March 2005
MP-1xx SIP
To add a client to the list using a template, take these 5 steps:
1.
Click on the Add New Client Icon;
a client with blank parameters is displayed.
2.
In the field Template, located on the right side of the Client Configuration Window, click
on the down arrow to the right of the entry field and select the template that you want to use.
3.
The values provided by the template are automatically entered into the parameter fields on
the right side of the Client Configuration Window. To use the template parameters, leave
the check box next to that parameter selected. The parameter values appear in gray text.
4.
To change a parameter to a different value, unselect the check box to the right of that
parameter. This clears the parameter provided by the template and enables you to edit the
entry. Clicking the check box again restores the template settings.
5.
Click Apply to save this entry to the list of clients or click Apply & Reset to save this entry to
the list of clients and send a reset message to that gateway to immediately implement the
settings.
Note: To use Apply & Reset you must enable ARP Manipulation in the Preferences
window. Also, you must have administrator privileges for the computer you are using.
B.11.2 Deleting Clients
To delete a client from the BootP Tool, take these 3 steps:
1.
Select the client that you wish to delete by clicking on the line in the window for that client.
2.
Click the Delete Current Client button
3.
A warning pops up. To delete the client, click Yes.
B.11.3 Editing Client Parameters
To edit the parameters for an existing client, take these 4 steps:
1.
Select the client that you wish to edit by clicking on the line in the window for that client.
2.
Parameters for that client display in the parameter fields on the right side of the window.
3.
Make the changes required for each parameter.
4.
Click Apply to save the changes, or click Apply & Reset to save the changes and send a
reset message to that gateway to immediately implement the settings.
Note: To use Apply & Reset you must enable ARP Manipulation in the Preferences
window. Also, you must have administrator privileges for the computer you are using.
B.11.4 Testing the Client
There should only be one BootP utility supporting any particular client MAC active on the network
at any time.
To check if other BootP utilities support this client, take these 4 steps:
1.
Select the client that you wish to test by clicking on the client name in the main area of the
Client Configuration Window.
2.
Click the Test Selected Client button
3.
Examine the Log Window on the Main Application Screen. If there is another BootP utility
that supports this client MAC, there is a response indicated from that utility showing the
status Listed At along with the IP address of that utility.
4.
If there is another utility responding to this client, you must remove that client from either this
utility or the other one.
MP-1xx SIP User’s Manual
204
Document #: LTRT-65404
MP-1xx SIP User’s Manual
B. The BootP/TFTP Configuration Utility
B.11.5 Setting Client Parameters
Client parameters are listed on the right side of the Client Configuration Window.
•
Client MAC: The Client MAC is used by BootP to identify the VoIP gateway. The MAC
address for the VoIP gateway is printed on a label located on the VoIP gateway hardware.
Enter the Ethernet MAC address for the VoIP gateway in this field. Click the box to the right
of this field to enable this particular client in the BootP tool (if the client is disabled, no replies
are sent to BootP requests).
Note: When the MAC address of an existing client is edited, a new client is added, with the
same parameters as the previous client.
•
Client Name: Enter a descriptive name for this client so that it is easier to remember which
VoIP gateway the record refers to. For example, this name could refer to the location of the
gateway.
•
Template: Click the pull down arrow if you wish to use one of the templates that you
configured. This applies the parameters from that template to the remaining fields.
Parameter values that are applied by the template are indicated by a check mark in the box
to the right of that parameter. Uncheck this box if you want to enter a different value. If
templates are not used, the box to the right of the parameters is colored gray and is not
selectable.
•
IP: Enter the IP address you want to apply to the VoIP gateway. Use the normal dotted
decimal format.
•
Subnet: Enter the subnet mask you want to apply to the VoIP gateway. Use the normal
dotted decimal format. Ensure that the subnet mask is correct. If the address is incorrect, the
VoIP gateway may not function until the entry is corrected and a BootP reset is applied.
•
Gateway: Enter the IP address for the data network gateway used on this subnet that you
want to apply to the VoIP gateway. The data network gateway is a device, such as a router,
that is used in the data network to interface this subnet to the rest of the enterprise network.
•
TFTP Server IP: This field contains the IP address of the TFTP utility that is used for file
transfer of software and initialization files to the gateway. When creating a new client, this
field is populated with the IP address used by the BootP Tool. If a different TFTP utility is to
be used, change the IP address in this field to the IP address used by the other utility.
•
Boot File: This field specifies the file name for the software (cmp) file that is loaded by the
TFTP utility to the VoIP gateway after the VoIP gateway receives the BootReply message.
The actual software file is located in the TFTP utility directory that is specified in the BootP
Preferences window. The software file can be followed by command line switches. For
information on available command line switches refer to Section B.11.6 on page 206.
Note 1:
Once the software file loads into the gateway, the gateway begins
functioning from that software. In order to save this software to non-volatile
memory, (only the cmp file, i.e., the compressed firmware file, can be burned
to your device's flash memory), the -fb flag must be added to the end of the
file name. If the file is not saved, the gateway reverts to the old version of
software after the next reset.
Note 2:
The Boot file field can contain up to two file names: cmp file name to be
used for load of application image and ini file name to be used for gateway
provisioning. Either one, two or no file names can appear in the Boot file
field. To use both file names use the ";" separator (without blank spaces)
between the xxx.cmp and the yyy.ini files (e.g., ram.cmp;SIPgw.ini).
•
ini File: This field specifies the configuration ini file that the gateway uses to program its
various settings. Enter the name of the file that is loaded by the TFTP utility to the VoIP
gateway after it receives the BootReply message. The actual ini file is located in the TFTP
utility directory that is specified in the BootP Preferences window.
•
Call Agent: This field specifies the IP address of the MGCP Call Agent that is controlling the
gateway. This field can be ignored for all other control/signaling protocols.
Version 4.4
205
March 2005
MP-1xx SIP
B.11.6 Using Command Line Switches
You can add command line switches in the field Boot File.
To use a Command Line Switch, take these 4 steps:
1.
In the field Boot File, leave the file name defined in the field as it is (e.g., ramxxx.cmp).
2.
Place your cursor after cmp.
3.
Press the space bar.
4.
Type in the switch you require.
Example: “ramxxx.cmp -fb” to burn flash memory.
“ramxxx.cmp -fb -em 4” to burn flash memory and for Ethernet Mode 4 (auto-negotiate).
Table B-1 lists and describes the switches that are available:
Table B-1: Command Line Switch Descriptions
Switch
-fb
-em #
Description
Burn ram.cmp in flash (only for cmp files)
Use this switch to set Ethernet mode.
0 = 10 Base-T half-duplex
1 = 10 Base-T full-duplex
2 = 100 Base-TX half-duplex
3 = 100 Base-TX full-duplex
4 = auto-negotiate (default)
Auto-negotiate falls back to half-duplex mode when the opposite port is not in auto-negotiate but the speed
(10 Base-T or 100 Base-TX) in this mode is always configured correctly.
-br
BootP retries. Sets the number of BootP requests the device sends during start-up. The device stops
sending BootP requests when either BootP reply is received or Number of Retries is reached. This switch
takes effect only from the next device reset.
1 = 1 BootP retry, 1 second
2 = 2 BootP retries, 3 seconds
3 = 3 BootP retries, 6 seconds
4 = 10 BootP retries, 30 seconds
5 = 20 BootP retries, 60 seconds
6 = 40 BootP retries, 120 seconds
7 = 100 BootP retries, 300 seconds
15 = BootP retries indefinitely
-bd
BootP delays. Sets the interval between the device’s start-up and the first BootP/DHCP request that is
issued by the device. The switch only takes effect from the next reset of the device.
1 = 1 second delay (default).
2 = 10 second delay.
3 = 30 second delay.
4 = 60 second delay.
5 = 120 second delay.
-bs
Use –bs 1 to enable the Selective BootP mechanism.
Use –bs 0 to disable the Selective BootP mechanism.
The Selective BootP mechanism enables the gateway’s integral BootP client to filter unsolicited
BootP/DHCP replies (accepts only BootP replies that contain the text “AUDC" in the vendor specific
information field). This option is useful in environments where enterprise BootP/DHCP servers provide
undesired responses to the gateway’s BootP requests.
-be
Use -be 1 for the device to send device-related initial startup information (such as board type, current IP
address, software version, etc.) in the vendor specific information field (in the BootP request). This
information can be viewed in the main screen of the BootP/TFTP, under column 'Client Info‘ (refer to
Figure B-1 showing BootP/TFTP main screen with the column 'Client Info' on the extreme right). For a full
list of the vendor specific Information fields refer to Section 10.3.2 on page 176.
Note: This option is not available on DHCP servers.
MP-1xx SIP User’s Manual
206
Document #: LTRT-65404
MP-1xx SIP User’s Manual
B. The BootP/TFTP Configuration Utility
B.12 Managing Client Templates
Templates can be used to simplify configuration of clients when most of the parameters are the
same.
Figure B-5: Templates Screen
To create a new template, take these 4 steps:
1.
Click on the Add New Template button
2.
Fill in the default parameter values in the parameter fields.
3.
Click Apply to save this new template.
4.
Click OK when you are finished adding templates.
To edit an existing template, take these 4 steps:
1.
Select the template by clicking on its name from the list of templates in the window.
2.
Make changes to the parameters, as required.
3.
Click Apply to save this new template.
4.
Click OK when you are finished editing templates.
To delete an existing template, take these 3 steps:
1.
Select the template by clicking its name from the list of templates in the window.
2.
Click on the Delete Current Template button.
3.
A warning pop up message appears. To delete the template, click Yes.
Note that if this template is currently in use, the template cannot be deleted.
Version 4.4
207
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
208
Document #: LTRT-65404
MP-1xx SIP User’s Manual
C. RTP/RTCP Payload Types and Port Allocation
Appendix C RTP/RTCP Payload Types and Port
Allocation
RTP Payload Types are defined in RFC 1889 and RFC 1890. We have added new payload types
to enable advanced use of other coder types. These types are reportedly not used by other
applications.
C.1
Packet Types Defined in RFC 1890
Table C-1: Packet Types Defined in RFC 1890
C.2
Payload Type
Description
Basic Packet Rate [msec]
0
2
4
8
18
200
G.711 µ-Law
G.726-32
G.723 (6.3/5.3 kbps)
G.711 A-Law
G.729A
RTCP Sender Report
201
RTCP Receiver Report
10,20
10,20
30
10,20
20
Randomly, approximately every 5 seconds (when
packets are sent by channel)
Randomly, approximately every 5 seconds (when
channel is only receiving)
202
203
204
RTCP SDES packet
RTCP BYE packet
RTCP APP packet
Defined Payload Types
Table C-2: Defined Payload Types
Payload Type
Description
Basic Packet Rate [msec]
35
36
38
39
40
41
42
43
44
45
46
47
51
52
53
54
56
96
102
103
104
105
G.726 32 kbps
G.726 24 kbps
G.726 40 kbps
G.727 16 kbps
G.727 24-16 kbps
G.727 24 kbps
G.727 32-16 kbps
G.727 32-24 kbps
G.727-32 kbps
G.727 40-16 kbps
G.727 40-24 kbps
G.727 40-32 kbps
NetCoder 6.4 kbps
NetCoder 7.2 kbps
NetCoder 8.0 kbps
NetCoder 8.8 kbps
Transparent PCM
RFC 2833 DTMF relay
Fax Bypass
Modem Bypass
RFC 2198 (Redundancy)
NSE Bypass
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
Same as channel’s voice coder.
Version 4.4
209
March 2005
MP-1xx SIP
C.3
Default RTP/RTCP/T.38 Port Allocation
The following table shows the Default RTP/RTCP/T.38 Port Allocation.
Table C-3: Default RTP/RTCP/T.38 Port Allocation
Channel Number
RTP Port
RTCP Port
T.38 Port
1
4000
4001
4002
2
4010
4011
4012
3
4020
4021
4022
4
4030
4031
4032
5
4040
4041
4042
6
4050
4051
4052
7
4060
4061
4062
8
4070
4071
4072
9
4080
4081
4082
10
4090
4091
4092
11
4100
4101
4102
12
4110
4111
4112
13
4120
4121
4122
14
4130
4131
4132
15
4140
4141
4142
16
4150
4151
4152
17
4160
4161
4162
18
4170
4171
4172
19
4180
4181
4182
20
4190
4191
4192
21
4200
4201
4202
22
4210
4211
4212
23
4220
4221
4222
24
4230
4231
4232
Note:
MP-1xx SIP User’s Manual
To configure the gateway to use the same port for both RTP and T.38
packets, set the parameter ‘T38UseRTPPort’ to 1.
210
Document #: LTRT-65404
MP-1xx SIP User’s Manual
D. Fax & Modem Transport Modes
Appendix D Fax & Modem Transport Modes
D.1
Fax/Modem Settings
Users may choose to use one of the following transport methods for fax and for each modem type
(V.22/V.23/Bell/V.32/V.34):
•
Fax relay
demodulation / modulation
•
Bypass
using a high bit rate coder to pass the signal
•
Transparent
passing the signal in the current voice coder
When the fax relay mode is enabled, distinction between fax and modem is not immediately
possible at the beginning of a session. The channel is therefore in “Answer Tone” mode until a
distinction is determined. The packets being sent to the network at this stage are T.38-complaint
fax relay packets.
D.2
Configuring Fax Relay Mode
When faxTransportType= 1 (relay mode), then on detection of fax the channel automatically
switches from the current voice coder to answer tone mode, and then to T.38-compliant fax relay
mode.
When fax transmission has ended, the reverse switching from fax relay to voice is performed.
This mode switching automatically occurs at both the local and remote endpoints.
Users can limit the fax rate using the FaxRelayMaxRate parameter and can enable/disable ECM
fax mode using the FaxRelayECMEnable parameter.
When using T.38 mode, the User can select between two protection strategies – redundancy
packets or forward error correction (FEC). This selection is made using the
T38FaxRelayProtectionMode configuration parameter. The User can also control a special
(proprietary) redundancy mode that was specially designed to improve protection against packet
loss using the EnhancedFaxRelayRedundancyDepth parameter. Although this is a proprietary
redundancy scheme, it is compatible with other T.38 decoders. The depth of the redundancy (that
is, the number of repetitions) is defined by the FaxRelayRedundancyDepth configuration
parameter.
Note:
D.3
T.38 mode currently supports only the T.38 UDP syntax.
Configuring Fax/Modem Bypass Mode
When VxxTransportType= 2 (FaxModemBypass, Vxx can be one of the following:
V32/V22/Bell/V34/Fax), then on detection of fax/modem, the channel automatically switches from
the current voice coder to a high bit-rate coder, as defined by the User, with the
FaxModemBypassCoderType configuration parameter.
During the bypass period, the coder uses the packing factor (by which a number of basic coder
frames are combined together in the outgoing WAN packet) set by the User in the
FaxModemBypassM configuration parameter. The network packets generated and received
during the bypass period are regular voice RTP packets (per the selected bypass coder) but with
a different RTP Payload type.
When fax/modem transmission ends, the reverse switching, from bypass coder to regular voice
coder, is carried out.
Version 4.4
211
March 2005
MP-1xx SIP
D.4
Supporting V.34 Faxes
V.34 faxes don’t comply with the T.38 relay standard. We therefore provide the optional modes
described under Sections D.4.1 and D.4.2:
Note that the CNG detector is disabled (CNGDetectorMode=0) in all the following examples.
D.4.1
Using Bypass Mechanism for V.34 Fax Transmission
In this proprietary scenario, the media gateway uses a high bit-rate coder to transmit V.34 faxes,
enabling the full utilization of its speed.
Refer to the following configurations:
FaxTransportMode = 2 (Bypass)
V34ModemTransportType = 2 (Modem bypass)
V32ModemTransportType = 2
V23ModemTransportType = 2
V22ModemTransportType = 2
In this configuration, both T.30 and V.34 faxes work in Bypass mode.
Or
FaxTransportMode = 1 (Relay)
V34ModemTransportType = 2 (Modem bypass)
V32ModemTransportType = 2
V23ModemTransportType = 2
V22ModemTransportType = 2
In this configuration, T.30 fax uses T.38 Relay mode while V.34 fax uses Bypass mode.
D.4.2
Using Relay mode for both T.30 and V.34 faxes
In this scenario, V.34 fax machines are compelled to use their backward compatibility with T.30
faxes; as a T.30 machine, the V.34 fax can use T.38 Relay mode.
Refer to the following configuration:
FaxTransportMode = 1 (Relay)
V34ModemTransportType = 0 (Transparent)
V32ModemTransportType = 0
V23ModemTransportType = 0
V22ModemTransportType = 0
Both T.30 and V.34 faxes use T.38 Relay mode. This configuration forces the V.34 fax machine
to operate in the slower T.30 mode.
MP-1xx SIP User’s Manual
212
Document #: LTRT-65404
MP-1xx SIP User’s Manual
E. Customizing the MP-1xx Web Interface
Appendix E Customizing the MP-1xx Web
Interface
Customers incorporating the MP-1xx into their portfolios can customize the Web Interface to suit
their specific corporate logo and product naming conventions.
Customers can customize the Web Interface’s title bar (AudioCodes’ title bar is shown in Figure
E-1; a customized title bar is shown in Figure E-3).
Figure E-1: User-Customizable Web Interface Title Bar
Corporate logo can be OEMcustomized
Background image can be
OEM-customized
Product name can be
OEM-customized
Figure E-2: Customized Web Interface Title Bar
To customize the title bar via the Web Interface, take these 3 steps:
E.1
1.
Replace the main corporate logo (refer to Section E.1 below).
2.
Replace the title bar’s background image file (refer to Section E.2 on page 215).
3.
Customize the product’s name (refer to Section E.3 on page 216).
Replacing the Main Corporate Logo
The main corporate logo can be replaced either with a different logo image file (refer to Section
E.1.1 below) or with a text string (refer to Section E.1.2 on page 215). Note that when the main
corporation logo is replaced, AudioCodes’ logo on the left bar (refer to Figure 5-2) and in the
Software Upgrade Wizard (Section 5.11.1 on page 131) disappear.
Also note that the browser’s title bar is automatically updated with the string assigned to the
WebLogoText parameter when AudioCodes’ default logo is not used.
E.1.1
Replacing the Main Corporate Logo with an Image File
Note:
Use a gif, jpg or jpeg file for the logo image. It is important that the image file
has a fixed height of 59 pixels (the width can be configured). The combined
size of the image files (logo and background) is limited to 64 kbytes.
To replace the default logo with your own corporate image via the Web
Interface, take these 7 steps:
1.
Access the MP-1xx Embedded Web Server (refer to Section 5.5 on page 40).
2.
In the URL field, append the suffix ‘AdminPage’ (note that it’s case-sensitive) to the IP
address, e.g., http://10.1.229.17/AdminPage.
Version 4.4
213
March 2005
MP-1xx SIP
3.
Click Image Load to Device; the Image Download screen is displayed (shown in Figure
E-3).
Figure E-3: Image Download Screen
4.
Click the Browse button in the Send Logo Image File from your computer to the device
box. Navigate to the folder that contains the logo image file you want to load.
5.
Click the Send File button; the file is sent to the device. When loading is complete, the
screen is automatically refreshed and the new logo image is displayed.
6.
Note the appearance of the logo. If you want to modify the width of the logo (the default
width is 339 pixels), in the Logo Width field, enter the new width (in pixels) and press the
Set Logo Width button.
7.
To save the image to flash memory so it is available after a power fail refer to Section 5.12
on page 139.
The new logo appears on all Web Interface screens.
Tip:
If you encounter any problem during the loading of the files, or you want to
restore the default images, click the Restore Default Images button.
To replace the default logo with your own corporate image via the ini
file, take these 2 steps:
1.
Place your corporate logo image file in the same folder as where the device’s ini file is
located (i.e., the same location defined in the BootP/TFTP configuration utility). For detailed
information on the BootP/TFTP, refer to Appendix B on page 197.
2.
Add/modify the two ini file parameters in Table E-1 according to the procedure described in
Section 6.2 on page 141.
Note that loading the device’s ini file via the ‘Configuration File’ screen in the Web Interface
doesn’t load the corporate logo image files as well.
MP-1xx SIP User’s Manual
214
Document #: LTRT-65404
MP-1xx SIP User’s Manual
E. Customizing the MP-1xx Web Interface
Table E-1: Customizable Logo ini File Parameters
Parameter
Description
LogoFileName
The name of the image file containing your corporate logo.
Use a gif, jpg or jpeg image file.
The default is AudioCodes’ logo file.
Note: The length of the name of the image file is limited to 47 characters.
LogoWidth
Width (in pixels) of the logo image.
Note: The optimal setting depends on the resolution settings.
The default value is 339, which is the width of AudioCodes’ displayed logo.
E.1.2
Replacing the Main Corporate Logo with a Text String
The main corporate logo can be replaced with a text string.
•
To replace AudioCodes’ default logo with a text string via the Web Interface, modify the two
ini file parameters in Table E-2 according to the procedure described in Section E.4 on page
217.
•
To replace AudioCodes’ default logo with a text string via the ini file, add/modify the two ini
file parameters in Table E-2 according to the procedure described in Section 6.2 on page
141.
Table E-2: Web Appearance Customizable ini File Parameters
Parameter
Description
UseWebLogo
0 = Logo image is used (default).
1 = Text string is used instead of a logo image.
WebLogoText
Text string that replaces the logo image.
The string can be up to 15 characters.
E.2
Replacing the Background Image File
The background image file is duplicated across the width of the screen. The number of times the
image is duplicated depends on the width of the background image and screen resolution. When
choosing your background image, keep this in mind.
Note:
Use a gif, jpg or jpeg file for the background image. It is important that the
image file has a fixed height of 59 pixels. The combined size of the image
files (logo and background) is limited to 64 kbytes.
To replace the background image via the Web, take these 6 steps:
1.
Access the MP-1xx Embedded Web Server (refer to Section 5.5 on page 40).
2.
In the URL field, append the suffix ‘AdminPage’ (note that it’s case-sensitive) to the IP
address, e.g., http://10.1.229.17/AdminPage.
3.
Click the Image Load to Device, the Image load screen is displayed (shown in Figure E-3).
4.
Click the Browse button in the Send Background Image File from your computer to
gateway box. Navigate to the folder that contains the background image file you want to
load.
5.
Click the Send File button; the file is sent to the device. When loading is complete, the
screen is automatically refreshed and the new background image is displayed.
6.
To save the image to flash memory so it is available after a power fail refer to Section 5.12
on page 139.
Version 4.4
215
March 2005
MP-1xx SIP
The new background appears on all Web Interface screens.
Tip 1:
If you encounter any problem during the loading of the files, or you want to
restore the default images, click the Restore Default Images button.
Tip 2:
When replacing both the background image and the logo image, first load
the logo image followed by the background image.
To replace the background image via the ini file, take these 2 steps:
1.
Place your background image file in the same folder as where the device’s ini file is located
(i.e., the same location defined in the BootP/TFTP configuration utility). For detailed
information on the BootP/TFTP, refer to Appendix B on page 197.
2.
Add/modify the ini file parameters in Table E-3 according to the procedure described in
Section 6.2 on page 141.
Note that loading the device’s ini file via the ‘Configuration File’ screen in the Web Interface
doesn’t load the logo image file as well.
Table E-3: Customizable Logo ini File Parameters
Parameter
Description
BkgImageFileName
The name (and path) of the file containing the new background.
Use a gif, jpg or jpeg image file.
The default is AudioCodes background file.
Note: The length of the name of the image file is limited to 47 characters.
E.3
Customizing the Product Name
The Product Name text string can be modified according to OEMs specific requirements.
•
To replace AudioCodes’ default product name with a text string via the Web Interface, modify
the two ini file parameters in Table E-4 according to the procedure described in Section E.4
on page 217.
•
To replace AudioCodes’ default product name with a text string via the ini file, add/modify the
two ini file parameters in Table E-4 according to the procedure described in Section 6.2 on
page 141.
Table E-4: Web Appearance Customizable ini File Parameters
Parameter
Description
UseProductName
0 = Don’t change the product name (default).
1 = Enable product name change.
UserProductName
Text string that replaces the product name.
The default is “MP-1xx”.
The string can be up to 29 characters.
MP-1xx SIP User’s Manual
216
Document #: LTRT-65404
MP-1xx SIP User’s Manual
E.4
E. Customizing the MP-1xx Web Interface
Modifying ini File Parameters via the Web AdminPage
To modify ini file parameters via the AdminPage, take these 6 steps:
1.
Access the MP-1xx Embedded Web Server (refer to Section 5.5 on page 40).
2.
In the URL field, append the suffix ‘AdminPage’ (note that it’s case-sensitive) to the IP
address, e.g., http://10.1.229.17/AdminPage.
3.
Click the INI Parameters option, the INI Parameters screen is displayed (shown in Figure
E-4).
Figure E-4: INI Parameters Screen
4.
In the Parameter Name dropdown list, select the required ini file parameter.
5.
In the Enter Value field to the right, enter the parameter’s new value.
6.
Click the Apply new value button to the right; the INI Parameters screen is refreshed, the
parameter name with the new value appears in the fields at the top of the screen and the
Output Window displays a log displaying information on the operation.
Note:
Version 4.4
You cannot load the image files (e.g., logo/background image files) to the
device by choosing a file name parameter in this screen.
217
March 2005
MP-1xx SIP
Reader’s Notes
MP-1xx SIP User’s Manual
218
Document #: LTRT-65404
MP-1xx SIP User’s Manual
F. Accessory Programs and Tools
Appendix F Accessory Programs and Tools
The accessory applications and tools shipped with the device provide you with friendly interfaces
that enhance device usability and smooth your transition to the new VoIP infrastructure. The
following applications are available:
F.1
•
TrunkPack Downloadable Conversion Utility (refer to Section F.1 below).
•
Call Progress Tones Wizard (refer to Section F.1.3 on page 222).
TrunkPack Downloadable Conversion Utility
Use the TrunkPack Downloadable Conversion Utility to:
•
Create a loadable Call Progress Tones file (refer to Section F.1.1 on page 220).
•
Encode / decode an ini file (refer to Section F.1.2 on page 221).
•
Create a loadable Prerecorded Tones file (refer to Section F.1.3 on page 222).
Figure F-1: TrunkPack Downloadable Conversion Utility Opening Screen
Version 4.4
219
March 2005
MP-1xx SIP
F.1.1
Converting a CPT ini File to a Binary dat File
For detailed information on creating a CPT ini file refer to Section 7.1 on page 143.
To convert a CPT ini file to a binary dat file, take these 10 steps:
1.
Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with
the software package); the utility’s main screen opens (shown in Figure F-1).
2.
Click the Process Call Progress Tones File(s) button; the ‘Call Progress Tones’ screen,
shown in Figure F-2, opens.
Figure F-2: Call Progress Tones Conversion Screen
3.
Click the Select File… button that is in the ‘Call Progress Tone File’ box.
4.
Navigate to the folder that contains the CPT ini file you want to convert.
5.
Click the ini file and click the Open button; the name and path of both the ini file and the
(output) dat file appears in the fields below the Select File button.
6.
Enter the Vendor Name, Version Number and Version Description in the corresponding
required fields under the ‘User Data’ section.
7.
Set ‘CPT Version’ to ‘Version 1’ only if you use this utility with a version released before
version 4.4 of the device software (this field is used to maintain backward compatibility).
8.
Check the ‘Use dBm units for Tone Levels’ check box. Note that the levels of the Call
Progress Tones (in the CPT file) must be in -dBm units.
9.
Click the Make File button; you’re prompted that the operation (conversion) was successful.
10. Close the application.
MP-1xx SIP User’s Manual
220
Document #: LTRT-65404
MP-1xx SIP User’s Manual
F.1.2
F. Accessory Programs and Tools
Encoding / Decoding an ini File
For detailed information on secured ini file refer to Section 6.1 on page 141.
To encode an ini file, take these 6 steps:
1.
Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with
the software package); the utility’s main screen opens (shown in Figure F-1).
2.
Click the Process Encoded/Decoded ini file(s) button; the ‘Encode/Decode ini File(s)’
screen, shown in Figure F-3, opens.
Figure F-3: Encode/Decode ini File(s) Screen
3.
Click the Select File… button under the ‘Encode ini File(s)’ section.
4.
Navigate to the folder that contains the ini file you want to encode.
5.
Click the ini file and click the Open button; the name and path of both the ini file and the
output encoded file appear in the fields under the Select File button. Note that the name and
extension of the output file can be modified.
6.
Click the Encode File(s) button; an encoded ini file with the name and extension you
specified is created.
To decode an encoded ini file, take these 4 steps:
1.
Click the Select File… button under the ‘Decode ini File(s)’ section.
2.
Navigate to the folder that contains the file you want to decode.
3.
Click the file and click the Open button. the name and path of both the encode ini file and the
output decoded file appear in the fields under the Select File button. Note that the name of
the output file can be modified.
4.
Click the Decode File(s) button; a decoded ini file with the name you specified is created.
Note that the decoding process verifies the input file for validity. Any change made to the
encoded file causes an error and the decoding process is aborted.
Version 4.4
221
March 2005
MP-1xx SIP
F.1.3
Creating a Loadable Prerecorded Tones File
For detailed information on the PRT file refer to Section 7.2 on page 147.
To create a loadable PRT dat file from your raw data files, take these 7
steps:
1.
Prepare the prerecorded tones (raw data PCM or L8) files you want to combine into a single
dat file using standard recording utilities.
2.
Execute the TrunkPack Downloadable Conversion utility, DConvert240.exe (supplied with
the software package); the utility’s main screen opens (shown in Figure F-1).
3.
Click the Process Prerecorded Tones File(s) button; the Prerecorded Tones File(s) screen,
shown in Figure F-4, opens.
Figure F-4: Prerecorded Tones Screen
4.
To add the prerecorded tone files (you created in Step 1) to the ‘Prerecorded Tones’ screen
follow one of these procedures:
Select the files and drag them to the ‘Prerecorded Tones’ screen.
MP-1xx SIP User’s Manual
222
Document #: LTRT-65404
MP-1xx SIP User’s Manual
F. Accessory Programs and Tools
Click the Add File(s) button; the ‘Select Files’ screen opens. Select the required
Prerecorded Tone files and press the Add>> button. Close the ‘Select Files’ screen.
5.
For each raw data file, define a Tone Type, a Coder and a Default Duration by completing
the following steps:
Double-click or right-click the required file; the ‘File Data’ window (shown in Figure F-5)
appears.
From the ‘Type’ drop-down list, select the tone type this raw data file is associated with.
From the ‘Coder’ drop-down list, select the coder that corresponds to the coder this raw
data file was originally recorded with.
In the ‘Description’ field, enter additional identifying information (optional).
In the ’Default’ field, enter the default duration this raw data file is repeatedly played.
Close the ‘File Data’ window (press the Esc key to cancel your changes); you are
returned to the Prerecorded Tones File(s) screen.
Figure F-5: File Data Window
6.
In the ‘Output’ field, specify the output directory in which the PRT file is generated followed
by the name of the PRT file (the default name is prerecordedtones.dat). Alternatively, use
the Browse button to select a different output file. Navigate to the desired file and select it;
the selected file name and its path appear in the ‘Output’ field.
7.
Click the Make File(s) button; the Progress bar at the bottom of the window is activated. The
dat file is generated and placed in the directory specified in the ‘Output’ field. A message box
informing you that the operation was successful indicates that the process is completed.
Version 4.4
223
March 2005
MP-1xx SIP
F.2
Call Progress Tones Wizard
This section describes the Call Progress Tones Wizard (CPTWizard), an application designed to
facilitate the provisioning of an MP-1xx/FXO gateway by recording and analyzing Call Progress
Tones generated by any PBX or telephone network.
F.2.1
About the Call Progress Tones Wizard
The Call Progress Tones wizard helps detect the Call Progress Tones generated by your PBX (or
telephone exchange) and creates a basic Call Progress Tones ini file (containing definitions for all
relevant Call Progress Tones), providing a good starting point when configuring an MP-1xx/FXO
gateway. This ini file can then be converted to a dat file that can be loaded to the gateway using
the TrunkPack Downloadable Conversion utility.
To use this wizard, an MP-1xx/FXO gateway connected to your PBX with 2 physical phone lines
is required. This gateway must be configured with factory-default settings and shouldn’t be used
for phone calls during the operation of the wizard.
Note that firmware version 4.2 and above is required on the gateway.
F.2.2
Installation
The CPTWizard can be installed on any Windows 2000 or Windows XP based PC. Windowscompliant networking and audio peripherals are required for full functionality.
To install the CPTWizard, copy the files from the supplied installation kit to any folder on your PC.
No further setup is required (approximately 5 MB of hard disk space are required).
F.2.3
Initial Settings
To start the CPTWizard, take these 5 steps:
1.
Execute the CPTWizard.exe file; the wizard’s initial settings screen is displayed.
Figure F-6: Initial Settings Screen
2.
Enter the IP address of the MP-1xx/FXO gateway you are using.
MP-1xx SIP User’s Manual
224
Document #: LTRT-65404
MP-1xx SIP User’s Manual
3.
Select the gateway’s ports that are connected to your PBX, and specify the phone number of
each extension.
4.
In the Invalid phone number field, enter a number that generates a “fast busy” tone when
dialed. Usually, any incorrect phone number should cause a “fast busy” tone.
5.
Press Next.
Note:
F.2.4
F. Accessory Programs and Tools
The CPTWizard communicates with the MP-10x/FXO gateway via TPNCP
(TrunkPack Network Control Protocol). If this protocol has been disabled in
the gateway configuration, the CPTWizard doesn’t display the next screen
and an error is reported.
Recording Screen – Automatic Mode
After the connection to the MP-1xx/FXO gateway is established, the recording screen is
displayed.
Figure F-7: Recording Screen –Automatic Mode
To start recording in automatic mode:
Press the Start Automatic Configuration button; the wizard starts the following Call Progress
Tones detection sequence (the operation takes approximately 60 seconds to complete):
1.
Sets port 1 offhook, listens to the dial tone
2.
Sets port 1 and port 2 offhook, dials the number of port 2, listens to the busy tone
3.
Sets port 1 offhook, dials the number of port 2, listens to the Ringback tone
4.
Sets port 1 offhook, dials an invalid number, listens to the reorder tone
Version 4.4
225
March 2005
MP-1xx SIP
5.
The wizard then analyzes the recorded Call Progress Tones and displays a message
specifying the tones that were detected (by the gateway) and analyzed (by the wizard)
correctly. At the end of a successful detection operation, the detected Call Progress Tones
are displayed in the Tones Analyzed pane (refer to Figure F-8).
Figure F-8: Recording Screen after Automatic Detection
6.
All four Call Progress Tones are saved (as standard A-law PCM at 8000 bits per sample) in
the same directory as the CPTWizard.exe file is located, with the following names:
cpt_recorded_dialtone.pcm
cpt_recorded_busytone.pcm
cpt_recorded_ringtone.pcm
cpt_recorded_invalidtone.pcm
Note 1:
If the gateway is configured correctly (with a Call Progress Tones dat file
loaded to the gateway), all four Call Progress Tones are detected by the
gateway. By noting whether the gateway detects the tones or not, you can
determine how well the Call Progress Tones dat file matches your PBX.
During the first run of the CPTWizard, it is likely that the gateway does not
detect any tones.
Note 2:
Some tones cannot be detected by the MP-10x gateway hardware (such as
3-frequency tones and complex cadences). CPTWizard is therefore limited to
detecting only those tones that can be detected on the MP-10x gateway.
At this stage, you can either press Next to generate a Call Progress Tones ini file and terminate
the wizard, or continue to manual recording mode.
F.2.5
Recording Screen – Manual Mode
In manual mode you can record and analyze tones, included in the Call Progress Tones ini file, in
MP-1xx SIP User’s Manual
226
Document #: LTRT-65404
MP-1xx SIP User’s Manual
F. Accessory Programs and Tools
addition to those tones analyzed when in automatic mode.
To start recording in manual mode, take these 6 steps:
1.
Press the Manual tab at the top of the recording screen, the manual recording screen is
displayed.
Figure F-9: Recording Screen - Manual Mode
2.
Check the play-through check box to hear the tones through your PC speakers.
3.
Press the Go offhook button, enter a number to dial in the Dial field, and press the Dial
button. When you’re ready to record, press the Start Recording button; when the desired
tone is complete, press Stop Recording. (The recorded tone is saved as
“cpt_manual_tone.pcm”.)
Note:
F.2.6
Due to some PC audio hardware limitations, you may hear “clicks” in playthrough mode. It is safe to ignore these clicks.
4.
Select the tone type from the drop-down list and press Analyze recorded tone; the
analyzed tone is added to the Tones analyzed list at the bottom of the screen. It is possible
to record and analyze several different tones for the same tone type (e.g., different types of
“busy” signal).
5.
Repeat the process for more tones, as necessary.
6.
When you’re finished adding tones to the list, press Next to generate a Call Progress Tones
ini file and terminate the wizard.
The Call Progress Tones ini File
After the Call Progress Tones detection is complete, a text file named call_progress_tones.ini is
created in the same directory as the directory in which the CPTWizard.exe is located. This file
contains:
•
Version 4.4
Information about each tone that was recorded and analyzed by the wizard. This information
includes frequencies and cadence (on/off) times, and is required for using this file with the
TrunkPack Downloadable Conversion utility.
227
March 2005
MP-1xx SIP
Figure F-10: Call Progress Tone Properties
[CALL PROGRESS TONE #1]
Tone Type=1
Low Freq [Hz]=350
High Freq [Hz]=440
Low Freq Level [-dBm]=0
High Freq Level [-dBm]=0
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=0
Second Signal Off Time [10msec]=0
•
Information related to possible matches of each tone with the CPTWizard’s internal database
of well-known tones. This information is specified as comments in the file, and is ignored by
the TrunkPack Downloadable Conversion utility.
Figure F-11: Call Progress Tone Database Matches
# Recorded tone: Busy Tone (automatic configuration)
## Matches: PBX name=ITU Anguilla, Tone name=Busy tone
## Matches: PBX name=ITU Antigua and Barbuda, Tone name=Busy tone
## Matches: PBX name=ITU Barbados, Tone name=Busy tone
## Matches: PBX name=ITU Bermuda, Tone name=Busy tone
## Matches: PBX name=ITU British Virgin Islan, Tone name=Busy tone
## Matches: PBX name=ITU Canada, Tone name=Busy tone
## Matches: PBX name=ITU Dominica (Commonweal, Tone name=Busy tone
## Matches: PBX name=ITU Hongkong, China, Tone name=Busy tone
## Matches: PBX name=ITU Jamaica, Tone name=Busy tone
## Matches: PBX name=ITU Korea (Republic of), Tone name=Busy tone
## Matches: PBX name=ITU Montserrat, Tone name=Busy tone
•
Information related to matches of all tones recorded with the CPTWizard’s internal database.
The database is scanned to find one or more PBX definitions that match all recorded tones
(i.e., dial tone, busy tone, ringing tone, reorder tone and any other manually-recorded tone –
all match the definitions of the PBX). If a match is found, the entire PBX definition is reported
(as comments) in the ini file using the same format.
Figure F-12: Full PBX/Country Database Match
## Some tones matched PBX/country Audc US
## Additional database tones guessed below (remove #'s to use).
#
# # Audc US, US Ringback tone
# [CALL PROGRESS TONE #5]
# Tone Type=2
# Low Freq [Hz]=450
# High Freq [Hz]=500
# Low Freq Level [-dBm]=0
# High Freq Level [-dBm]=0
# First Signal On Time [10msec]=180
# First Signal Off Time [10msec]=450
# Second Signal On Time [10msec]=0
# Second Signal Off Time [10msec]=0
Note 1:
If a match is found in the database, consider using the database’s definitions
instead of the recorded definitions, as they might be more accurate.
Note 2
For full operability of the MP-1xx/FXO gateway, it may be necessary to edit
this file and add more Call Progress Tone definitions. Sample Call Progress
Tones ini files are available in the release package.
Note 3:
When the CPT ini file is complete, use the TrunkPack Downloadable
Conversion utility to create a loadable CPT dat file. After loading this file to
the gateway, repeat the automatic detection procedure discussed above,
and verify that the gateway detects all four Call Progress Tones correctly.
MP-1xx SIP User’s Manual
228
Document #: LTRT-65404
MP-1xx SIP User’s Manual
G. SNMP Traps
Appendix G SNMP Traps
This section provides information on proprietary SNMP traps currently supported by the gateway.
There is a separation between traps that are alarms and traps that are not (logs). Currently all
have the same structure made up of the same 10 varbinds (1.3.6.1.4.1.5003.9.10.1.21.1).
G.1
Alarm Traps
The following tables provide information on alarms that are raised as a result of a generated
SNMP trap. The component name (described in each of the following headings) refers to the
string that is provided in the ‘acBoardTrapGlobalsSource’ trap varbind. To clear a generated
alarm the same notification type is sent but with the severity set to ‘cleared’.
G.1.1
Component: System#0
Table G-1: acBoardFatalError Alarm Trap
Alarm:
acBoardFatalError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.1
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable (56)
Alarm Text:
Board Fatal Error: <text>
Status Changes:
Condition:
Any fatal error
Alarm status:
Critical
<text> value:
A run-time specific string describing the fatal error
Condition:
After fatal error
Alarm status:
Status stays critical until reboot. A clear trap is not sent.
Corrective Action:
Capture the alarm information and the Syslog clause, if active. Contact your first-level
support group. The support group will likely want to collect additional data from the
device and perform a reset.
Table G-2: acBoardEvResettingBoard Alarm Trap
Alarm:
acBoardEvResettingBoard
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.5
Default Severity
critical
Event Type:
equipmentAlarm
Probable Cause:
outOfService (71)
Alarm Text:
User resetting board
Status Changes:
Condition:
When a soft reset is triggered via the Web interface or SNMP.
Alarm status:
Critical
Condition:
After raise
Alarm status:
Status stays critical until reboot. A clear trap is not sent.
Corrective Action:
A network administrator has taken action to reset the device. No corrective action is
required.
Version 4.4
229
March 2005
MP-1xx SIP
Table G-3: acBoardCallResourcesAlarm Alarm Trap
Alarm:
acBoardCallResourcesAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.8
Default Severity
Major
Event Type:
processingErrorAlarm
Probable Cause:
softwareError (46)
Alarm Text:
Call resources alarm
Status Changes:
Condition:
Number of free channels exceeds the predefined RAI high threshold.
Alarm Status:
Major
Note:
To enable this alarm the RAI mechanism must be activated (EnableRAI = 1).
Condition:
Number of free channels falls below the predefined RAI low threshold.
Alarm Status:
Cleared
Table G-4: acBoardControllerFailureAlarm Alarm Trap
Alarm:
acBoardControllerFailureAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.9
Default Severity
Minor
Event Type:
processingErrorAlarm
Probable Cause:
softwareError (46)
Alarm Text:
Controller failure alarm
Status Changes:
Condition:
Proxy has not been found
Alarm Status:
Major
Additional Info:
Proxy not found. Use internal routing
or
Proxy lost. looking for another Proxy
Condition:
Proxy is found.
The clear message includes the IP address of the located Proxy.
Alarm Status:
Cleared
Table G-5: acBoardOverloadAlarm Alarm Trap
Alarm:
acBoardOverloadAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.11
Default Severity
Major
Event Type:
processingErrorAlarm
Probable Cause:
softwareError (46)
Alarm Text:
Board overload alarm
Status Changes:
Condition:
An overload condition exists in one or more of the system components.
Alarm Status:
Major
Condition:
The overload condition passed
Alarm Status:
Cleared
MP-1xx SIP User’s Manual
230
Document #: LTRT-65404
MP-1xx SIP User’s Manual
G.1.2
G. SNMP Traps
Component: AlarmManager#0
Table G-6: acActiveAlarmTableOverflow Alarm Trap
Alarm:
acActiveAlarmTableOverflow
OID:
1.3.6.1.4.15003.9.10.1.21.2.0.12
Default Severity
Major
Event Type:
processingErrorAlarm
Probable Cause:
resourceAtOrNearingCapacity (43)
Alarm Text:
Active alarm table overflow
Status Changes:
Condition:
Too many alarms to fit in the active alarm table
Alarm status:
major
Condition:
After raise
Alarm status:
Status stays major until reboot. A clear trap is not sent.
Note:
The status stays major until reboot as it denotes a possible loss of information until the
next reboot. If an alarm is raised when the table is full, it is possible that the alarm is
active, but does not appear in the active alarm table.
Corrective Action:
Some alarm information may have been lost, but the ability of the device to perform its
basic operations has not been impacted. A reboot is the only way to completely clear a
problem with the active alarm table. Contact your first-level group.
G.1.3
Component: EthernetLink#0
Table G-7: acBoardEthernetLinkAlarm Alarm Trap
Alarm:
acBoardEthernetLinkAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.10
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable (56)
Alarm Text:
Ethernet link alarm: <text>
Status Changes:
Condition:
Fault on single interface
Alarm status:
major
<text> value:
Redundant link is down
Condition:
Fault on both interfaces
Alarm status:
critical
<text> value:
No Ethernet link
Condition:
Both interfaces are operational
Alarm status:
cleared
Corrective Action:
Ensure that both Ethernet cables are plugged into the back of the system. Inspect the
system’s Ethernet link lights to determine which interface is failing. Reconnect the cable
or fix the network problem
Version 4.4
231
March 2005
MP-1xx SIP
G.1.4
Other Traps
The following are provided as SNMP traps and are not alarms.
Table G-8: coldStart Trap
Trap Name:
coldStart
OID:
1.3.6.1.6.3.1.1.5.1
MIB
SNMPv2-MIB
Note:
This is a trap from the standard SNMP MIB.
Table G-9: authenticationFailure Trap
Trap Name:
authenticationFailure
OID:
1.3.6.1.6.3.1.1.5.5
MIB
SNMPv2-MIB
Table G-10: acBoardEvBoardStarted Trap
Trap Name:
acBoardEvBoardStarted
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.4
MIB
AcBoard
Severity
cleared
Event Type:
equipmentAlarm
Probable Cause:
Other(0)
Alarm Text:
Initialization Ended
Note:
This is the AudioCodes Enterprise application cold start trap.
G.1.5
Trap Varbinds
Each trap described above provides the following fields (known as ‘varbinds’). Refer to the
AcBoard MIB for additional details on these varbinds.
•
acBoardTrapGlobalsName
•
acBoardTrapGlobalsTextualDescription
•
acBoardTrapGlobalsSource
•
acBoardTrapGlobalsSeverity
•
acBoardTrapGlobalsUniqID
•
acBoardTrapGlobalsType
•
acBoardTrapGlobalsProbableCause
•
acBoardTrapGlobalsAdditionalInfo1
•
acBoardTrapGlobalsAdditionalInfo2
•
acBoardTrapGlobalsAdditionalInfo3
Note that ‘acBoardTrapGlobalsName’ is actually a number. The value of this varbind is ‘X’ minus
1, where ‘X’ is the last number in the trap’s OID. For example, the ‘name’ of
‘acBoardEthernetLinkAlarm’ is ‘9’. The OID for ‘acBoardEthernetLinkAlarm’ is 1.3.6.1.4.1.5003.
9.10.1.21.2.0.10.
MP-1xx SIP User’s Manual
232
Document #: LTRT-65404
MP-1xx SIP User’s Manual
H. Regulatory Information
Appendix H Regulatory Information
H.1
MP-11x FXS
Declaration of Conformity
Application of Council Directives:
73/23/EEC (including amendments),
89/336/EEC (including amendments),
Standards to which Conformity is Declared:
EN55022: 1998, Class B
EN55024:1998
EN61000-3-2: 1995
EN60950: 2000
(including amendments A1: 1998, A2: 1998, A14: 2000)
EN61000-3-3: 1995
Manufacturer’s Name:
AudioCodes Ltd.
Manufacturer’s Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Analog VoIP System.
Model Numbers:
MP-1xx/FXS
(xx- may represent 02,04,08)
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards.
th
11 February, 2005 Airport City, Lod, Israel
Signature
I. Zusmanovich, Compliance Engineering Manager
Czech
Date (Day/Month/Year) Location
[AudioCodes Ltd] tímto prohlašuje, že tento [MP-1xx/FXS series] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice
89/336/EEC, 73/23/EEC.
Danish
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [MP-1xx/FXS Series] overholder de væsentlige krav og øvrige relevante krav i direktiv
89/336/EEC, 73/23/EEC.
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [MP-1xx/FXS Series] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van
richtlijn 89/336/EEC, 73/23/EEC
English
Hereby, [AudioCodes Ltd], declares that this [MP-1xx/FXS Series] is in compliance with the essential requirements and other relevant provisions of Directive
89/336/EEC, 73/23/EEC.
Estonian
Käesolevaga kinnitab [AudioCodes Ltd] seadme [MP-1xx/FXS Series] vastavust direktiivi 89/336/EEC, 73/23/EEC põhinõuetele ja nimetatud direktiivist
tulenevatele teistele asjakohastele sätetele.
Finnish
[AudioCodes Ltd] vakuuttaa täten että [MP-1xx/FXS Series] tyyppinen laite on direktiivin 89/336/EEC, 73/23/EEC oleellisten vaatimusten ja sitä koskevien
direktiivin muiden ehtojen mukainen.
French
Par la présente [AudioCodes Ltd] déclare que l'appareil [MP-1xx/FXS Series] est conforme aux exigences essentielles et aux autres dispositions pertinentes
de la directive 89/336/EEC, 73/23/EEC
German
Hiermit erklärt [AudioCodes Ltd], dass sich dieser/diese/dieses [MP-1xx/FXS Series] in Übereinstimmung mit den grundlegenden Anforderungen und den
anderen relevanten Vorschriften der Richtlinie 89/336/EEC, 73/23/EEC befindet". (BMWi)
Greek
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [AudioCodes Ltd] ∆ΗΛΩΝΕΙ ΟΤΙ [MP-1xx/FXS Series] ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ
ΣΧΕΤΙΚΕΣ ∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 89/336/EEC, 73/23/EEC
Hungarian
Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-1xx/FXS Series] megfelel a vonatkozó alapvetõ követelményeknek és az 89/336/EEC, 73/23/EEC
irányelv egyéb elõírásainak
Icelandic
æki þetta er í samræmi við tilskipun Evrópusambandsins 89/336/EEC, 73/23/EEC
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (MP-1xx/FXS Series) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla
direttiva 89/336/EEC, 73/23/EEC.
Latvian
Ar šo [AudioCodes Ltd] deklarē, ka [MP-1xx/FXS Series] atbilst Direktīvas 89/336/EEC, 73/23/EEC būtiskajām prasībām un citiem ar to saistītajiem
noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [MP-1xx/FXS Series] tenkina 89/336/EEC, 73/23/EEC Direktyvos esminius reikalavimus ir kitas sios direktyvos
nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [MP-1xx/FXS Series] jikkonforma mal-ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fidDirrettiva 89/336/EEC, 73/23/EEC
Norwegian
Dette produktet er i samhørighet med det Europeiske Direktiv 89/336/EEC, 73/23/EEC
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrób [MP-1xx/FXS Series] spelnia podstawowe wymagania i odpowiada warunkom
zawartym w dyrektywie 89/336/EEC, 73/23/EEC
Portuguese
[AudioCodes Ltd] declara que este [MP-1xx/FXS Series] está conforme com os requisitos essenciais e outras disposições da Directiva 89/336/EEC,
73/23/EEC.
Slovak
[AudioCodes Ltd] týmto vyhlasuje, že [MP-1xx/FXS Series] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 89/336/EEC, 73/23/EEC.
Slovene
Šiuo [AudioCodes Ltd] deklaruoja, kad šis [MP-1xx/FXS Series] atitinka esminius reikalavimus ir kitas 89/336/EEC, 73/23/EEC Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (MP-1xx/FXS Series) cumple con los requisitos esenciales y cualesquiera otras disposiciones
aplicables o exigibles de la Directiva 89/336/EEC, 73/23/EEC
Swedish
Härmed intygar [AudioCodes Ltd] att denna [MP-1xx/FXS Series] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta
bestämmelser som framgår av direktiv 89/336/EEC, 73/23/EEC.
Version 4.4
233
March 2005
MP-1xx SIP
Safety Notice
Installation and service of this card must only be performed by authorized, qualified service personnel.
The protective earth terminal on the back of the MP-1xx must be permanently connected to protective earth.
Telecommunication Safety
The safety status of each port on the gateway is declared and detailed in the table below:
Ports
Safety Status
Ethernet (100 Base-TX)
SELV
FXS (ODP P/N’s)
TNV-3
FXS
TNV-2
TNV-3:
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating conditions
and on which over voltages from Telecommunication Networks are possible
TNV-2:
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating conditions
and is not subjected to over voltages from Telecommunication Networks
SELV:
Safety extra low voltage circuit.
FCC Statement
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This
equipment generates uses and can and can radiate radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However there is no guarantee that interference will not
occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
H.2
MP-11x FXO
Declaration of Conformity
Application of Council Directives:
73/23/EEC (including amendments),
89/336/EEC (including amendments),
1999/5/EC Annex-II of the Directive
Standards to which Conformity is Declared:
EN55022: 1998, Class B
EN55024:1998
EN61000-3-2: 1995
(including amendments A1: 1998, A2: 1998, A14: 2000)
EN61000-3-3: 1995
EN60950: 2000
TBR-21: 1998
Manufacturer’s Name:
AudioCodes Ltd.
Manufacturer’s Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Analog VoIP System.
Model Numbers:
MP-1xx/FXO
(xx- may represent 02, 04, 08)
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards.
th
Signature
11 February 2005
Date (Day/Month/Year)
Airport City, Lod, Israel
Location
I. Zusmanovich, Compliance Engineering Manager
MP-1xx SIP User’s Manual
234
Document #: LTRT-65404
MP-1xx SIP User’s Manual
H. Regulatory Information
Czech
[AudioCodes Ltd] tímto prohlašuje, že tento [MP-1xx/FXO] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES."
Danish
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [MP-1xx/FXO] overholder de væsentlige krav og øvrige relevante krav i direktiv
1999/5/EF
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [MP-1xx/FXO] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van
richtlijn 1999/5/EG
English
Hereby, [AudioCodes Ltd], declares that this [MP-1xx/FXO] is in compliance with the essential requirements and other relevant provisions of Directive
1999/5/EC.
Estonian
Käesolevaga kinnitab [AudioCodes Ltd] seadme [MP-1xx/FXO] vastavust direktiivi 1999/5/EÜ põhinõuetele ja nimetatud direktiivist tulenevatele teistele
asjakohastele sätetele.
Finnish
[AudioCodes Ltd] vakuuttaa täten että [MP-1xx/FXO] tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden
ehtojen mukainen.
French
Par la présente [AudioCodes Ltd] déclare que l'appareil [MP-1xx/FXO] est conforme aux exigences essentielles et aux autres dispositions pertinentes de
la directive 1999/5/CE
German
Hiermit erklärt [AudioCodes Ltd], dass sich dieser/diese/dieses [MP-1xx/FXO] in Übereinstimmung mit den grundlegenden Anforderungen und den
anderen relevanten Vorschriften der Richtlinie 1999/5/EG befindet". (BMWi)
Greek
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [AudioCodes Ltd] ∆ΗΛΩΝΕΙ ΟΤΙ [MP-1xx/FXO] ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ
ΣΧΕΤΙΚΕΣ ∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 1999/5/ΕΚ
Hungarian
Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-1xx/FXO] megfelel a vonatkozó alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb
elõírásainak
Icelandic
æki þetta er í samræmi við tilskipun Evrópusambandsins 1999/5
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (MP-1xx/FXO) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla
direttiva 1999/5/CE.
Latvian
Ar šo [AudioCodes Ltd] deklarē, ka [MP-1xx/FXO] atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [MP-1xx/FXO] tenkina 1999/5/EB Direktyvos esminius reikalavimus ir kitas sios direktyvos nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [MP-1xx/FXO] jikkonforma mal-ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva
1999/5/EC
Norwegian
Dette produktet er i samhørighet med det Europeiske Direktiv 1999/5
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrób [MP-1xx/FXO] spelnia podstawowe wymagania i odpowiada warunkom zawartym w
dyrektywie 1999/5/EC
Portuguese
[AudioCodes Ltd] declara que este [MP-1xx/FXO] está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE.
Slovak
[AudioCodes Ltd] týmto vyhlasuje, že [MP-1xx/FXO] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 1999/5/ES.
Slovene
Šiuo [AudioCodes Ltd] deklaruoja, kad šis [MP-1xx/FXO] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (MP-1xx/FXO) cumple con los requisitos esenciales y cualesquiera otras disposiciones
aplicables o exigibles de la Directiva 1999/5/CE
Swedish
Härmed intygar [AudioCodes Ltd] att denna [MP-1xx/FXO] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser
som framgår av direktiv 1999/5/EG.
Safety Notice
Installation and service of this unit must only be performed by authorized, qualified service personnel.
The protective earth terminal on the back of the MP-1xx must be permanently connected to protective earth.
Industry Canada Notice
This equipment meets the applicable Industry Canada Terminal Equipment technical specifications. This is confirmed by the
registration numbers. The abbreviation, IC, before the registration number signifies that registration was performed based on a
declaration of conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry
Canada approved the equipment.
Network Compatibility
The products support the Telecom networks in EU that comply with TBR21.
Telecommunication Safety
The safety status of each port is declared and detailed in the table below:
Ports
Safety Status
Ethernet (100 Base-TX)
SELV
FXO
TNV-3
TNV-3:
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating conditions
and on which over voltages from Telecommunication Networks are possible.
SELV:
Safety extra low voltage circuit.
Version 4.4
235
March 2005
MP-1xx SIP
MP-1xx/FXO Notice
The MP-1xx FXO Output Tones and DTMF level should not exceed -9 dBm (AudioCodes setting #23) in order to comply with
FCC 68, TIA/EIA/IS-968 and TBR-21.
The maximum allowed gain between any 2 ports connected to the PSTN should be set to 0 dB in order to comply with FCC 68,
TIA/EIA/IS-968 Signal power limitation
FCC Statement
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However there is no guarantee that interference will not
occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the
following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
H.3
MP-124
Declaration of Conformity
Application of Council Directives:
73/23/EEC (including amendments),
89/336/EEC (including amendments),
Standards to which Conformity is Declared:
EN55022: 1998, Class A
EN55024:1998
EN61000-3-2: 1995
(including amendments A1: 1998, A2: 1998, A14: 2000)
EN61000-3-3: 1995
EN60950: 1992 Including amendments 1,2,3,4 and 11
Manufacturer’s Name: :
AudioCodes Ltd.
Manufacturer’s Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Analog VoIP System.
Model Numbers:
MP-124/FXS
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards.
th
11 February, 2005 Airport City, Lod, Israel
Signature
I. Zusmanovich, Compliance Engineering Manager
Czech
Date (Day/Month/Year) Location
[AudioCodes Ltd] tímto prohlašuje, že tento [MP-124] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 89/336/EEC,
73/23/EEC.
Danish
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [MP-124] overholder de væsentlige krav og øvrige relevante krav i direktiv 89/336/EEC,
73/23/EEC.
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [MP-124] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn
89/336/EEC, 73/23/EEC
English
Hereby, [AudioCodes Ltd], declares that this [MP-124] is in compliance with the essential requirements and other relevant provisions of Directive 89/336/EEC,
73/23/EEC.
Estonian
Käesolevaga kinnitab [AudioCodes Ltd] seadme [MP-124] vastavust direktiivi 89/336/EEC, 73/23/EEC põhinõuetele ja nimetatud direktiivist tulenevatele teistele
asjakohastele sätetele.
Finnish
[AudioCodes Ltd] vakuuttaa täten että [MP-124] tyyppinen laite on direktiivin 89/336/EEC, 73/23/EEC oleellisten vaatimusten ja sitä koskevien direktiivin muiden
ehtojen mukainen.
French
Par la présente [AudioCodes Ltd] déclare que l'appareil [MP-124] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive
89/336/EEC, 73/23/EEC
German
Hiermit erklärt [AudioCodes Ltd], dass sich dieser/diese/dieses [MP-124] in Übereinstimmung mit den grundlegenden Anforderungen und den anderen
relevanten Vorschriften der Richtlinie 89/336/EEC, 73/23/EEC befindet". (BMWi)
Greek
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [AudioCodes Ltd] ∆ΗΛΩΝΕΙ ΟΤΙ [MP-124] ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ
∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 89/336/EEC, 73/23/EEC
MP-1xx SIP User’s Manual
236
Document #: LTRT-65404
MP-1xx SIP User’s Manual
Hungarian
H. Regulatory Information
Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-124] megfelel a vonatkozó alapvetõ követelményeknek és az 89/336/EEC, 73/23/EEC irányelv egyéb
elõírásainak
Icelandic
æki þetta er í samræmi við tilskipun Evrópusambandsins 89/336/EEC, 73/23/EEC
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (MP-124) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla directiva
89/336/EEC, 73/23/EEC.
Latvian
Ar šo [AudioCodes Ltd] deklarē, ka [MP-124] atbilst Direktīvas 89/336/EEC, 73/23/EEC būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [MP-124] tenkina 89/336/EEC, 73/23/EEC Direktyvos esminius reikalavimus ir kitas sios direktyvos nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [MP-124] jikkonforma mal-ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva
89/336/EEC, 73/23/EEC
Norwegian
Dette produktet er i samhørighet med det Europeiske Direktiv 89/336/EEC, 73/23/EEC
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrób [MP-124] spelnia podstawowe wymagania i odpowiada warunkom zawartym w dyrektywie
89/336/EEC, 73/23/EEC
Portuguese
[AudioCodes Ltd] declara que este [MP-124] está conforme com os requisitos essenciais e outras disposições da Directiva 89/336/EEC, 73/23/EEC.
Slovak
[AudioCodes Ltd] týmto vyhlasuje, že [MP-124 Series] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 89/336/EEC, 73/23/EEC.
Slovene
Šiuo [AudioCodes Ltd] deklaruoja, kad šis [MP-124 Series] atitinka esminius reikalavimus ir kitas 89/336/EEC, 73/23/EEC Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (MP-124 Series) cumple con los requisitos esenciales y cualesquiera otras disposiciones aplicables o
exigibles de la Directiva 89/336/EEC, 73/23/EEC
Swedish
Härmed intygar [AudioCodes Ltd] att denna [MP-124 Series] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser
som framgår av direktiv 89/336/EEC, 73/23/EEC.
Safety Notice
Installation and service of this unit must only be performed by authorized, qualified service personnel.
The protective earth terminal on the back of the MP-124 must be permanently connected to protective earth.
Telecommunication Safety
The safety status of each port on the gateway is declared and detailed in the table below:
Ports
Safety Status
Ethernet (100 Base-TX)
SELV
FXS (ODP P/N’s)
TNV-3
FXS
TNV-2
TNV-3:
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating conditions
and on which over voltages from Telecommunication Networks are possible
TNV-2:
Circuit whose normal operating voltages exceeds the limits for an SELV circuit under normal operating conditions
and is not subjected to over voltages from Telecommunication Networks
SELV:
Safety extra low voltage circuit.
FCC Statement
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated
in a commercial environment. This equipment generates uses and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.
This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
Original
printed on
recycled paper
and available on
CD or Web site
Version 4.4
237
March 2005
AudioCodes Offices
International Headquarters
AudioCodes Ltd, 1 Hayarden Street, Airport City
Lod 70151, Israel.
Tel: +972-3-976 4000
Fax: +972-3-976 4040
USA Headquarters
AudioCodes Inc, 2890 Zanker Road, Suite # 200
San Jose, CA 95134
Tel: +1-408-577-0488
Fax: +1-408-577-0492
AudioCodes Offices Worldwide
Beijing, Boston (MA), Chicago (IL), London
Mexico City, Paris, Raleigh (NC), Somerset (NJ), Tokyo
info@audiocodes.com
www.audiocodes.com