Page 1
AccessLinX
VoIP GATEWAY
H.323, MGCP, SIP
USER GUIDE
52-80420-00 A0
Page 2
Contents
1 OVERVIEW .................................................................................................................................. 1-1
1.1 PRODUCT OVERVIEW .............................................................................................................1-1
1.2 F
1.3 LASER SAFETY .......................................................................................................................1-3
1.4 HOW TO GET HELP.................................................................................................................1-3
2 PRE-INSTALLATION REQUIREMENTS ..............................................................................2-1
2.1 S
2.2 TELEPHONES AND ACCESSORIES ...........................................................................................2-1
3 GATEWAY INSTALLATION....................................................................................................3-1
3.1 I
4 GATEWAY INITIAL CONFIGURATION AND BACKGROUND INFORMATION ......4-1
4.1 KEYPAD CONFIGURATION......................................................................................................4-1
4.2 UNDERSTANDING DHCP .......................................................................................................4-2
4.3
4.4 UNDERSTANDING NTP........................................................................................................... 4-4
4.5
4.6 DIAL PLAN FOR SIP AND H.323.............................................................................................4-7
4.7
5 USING THE VOIP GATEWAY .................................................................................................5-1
5.1 FIRST CALL ............................................................................................................................5-1
5.2 P
5.3 ADDING ADDITIONAL UNITS .................................................................................................5-2
5.4 ADVANCED CALLING FEATURES FOR SIP..............................................................................5-2
5.5
5.6
EATURES
UPPORTING EQUIPMENT REQUIREMENTS
NSTALLING THE VO
4.1.1 Keypad Configuration for MGCP....................................................................................4-2
4.2.1 When Should Clients Use DHCP .....................................................................................4-4
UNDERSTANDING NAT AND NAPT ......................................................................................4-4
4.4.1 Daylight Saving Time (Summer Time) .............................................................................4-5
UNDERSTANDING SYSLOG .....................................................................................................4-5
4.5.1 Remote Logging................................................................................................................ 4-6
4.6.1 Default Dial Plan .............................................................................................................4-7
4.6.2 Dial Plan Syntax...............................................................................................................4-7
4.6.3 Dial Plan Examples..........................................................................................................4-8
DNS RESOLVER ...................................................................................................................4-10
LACING CALLS
5.4.1 Call Waiting......................................................................................................................5-2
5.4.2 Conference Call................................................................................................................5-2
5.4.3 Forwarding a Call............................................................................................................5-2
5.4.4 Attended Transfer Call .....................................................................................................5-2
5.4.5 Blind Transfer Call...........................................................................................................5-3
5.4.6 Hold ..................................................................................................................................5-3
5.4.7 Conditional Call Forwarding ..........................................................................................5-3
5.4.8 Do Not Disturb (DND).....................................................................................................5-3
5.4.9 Redialing to Last Received Caller ...................................................................................5-3
5.4.10 Block Last Received Caller .........................................................................................5-3
5.4.11 Auto Redial .................................................................................................................. 5-3
ADVANCED CALLING FEATURES FOR H.323..........................................................................5-4
5.5.1 Call Waiting......................................................................................................................5-4
5.5.2 Conference Call................................................................................................................5-4
5.5.3 Forwarding a Call............................................................................................................5-4
5.5.4 Transferring a Call...........................................................................................................5-5
5.5.5 Hold ..................................................................................................................................5-5
ADVANCED CALLING FEATURES FOR MGCP ........................................................................5-5
...............................................................................................................................1-1
............................................................................2-1
IP G
ATEWAY
.....................................................................................................................5-1
.........................................................................................3-1
ii
52-80420-00 A0
Page 3
6 UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES...................................................................................................................6-1
6.1 DOWNLOADING THE FILE MANUALLY USING TELNET ..........................................................6-2
6.2 DOWNLOADING THE FILE MANUALLY USING THE WEB ........................................................6-3
6.3 DHCP A
6.3.1 Setting DHCP Automatic Configuration via the Web .....................................................6-3
6.3.2 Setting DHCP Automatic Configuration via Telnet ........................................................6-6
6.4 F
6.4.1 Setting the TFTP/HTTP Server “Root” Configuration File via the Web .......................6-7
6.4.2 Setting the TFTP Server “Root” Configuration File via Telnet.....................................6-8
6.5 C
7 CONFIGURING THE GATEWAY VIA TELNET .................................................................7-1
7.1 STARTING A TELNET SESSION................................................................................................7-1
7.2
7.3 GENERAL COMMANDS ...........................................................................................................7-7
7.4 USING THE CLI COMMANDS..................................................................................................7-8
8 CONFIGURING THE GATEWAY VIA A TERMINAL........................................................8-1
COMMAND MODES................................................................................................................. 7-3
7.2.1 Enable Mode.....................................................................................................................7-3
7.2.2 Commands Mode ..............................................................................................................7-3
7.2.3 Report Mode .....................................................................................................................7-3
7.2.4 Statistics Mode..................................................................................................................7-4
7.2.5 Download Mode ...............................................................................................................7-4
7.2.6 Configuration Modes........................................................................................................7-5
UTOMATIC CONFIGURATION
IXED (PROVISIONED
REATING AND ENCRYPTING CONFIGURATION FILES
) HTTP
OR
...................................................................................6-3
TFTP A
UTOMATIC CONFIGURATION
...........................................................6-9
................................6-7
9 CONFIGURING THE GATEWAY VIA THE WEB...............................................................9-1
9.1 CONFIGURING THE GATEWAY’S IP ADDRESS AND DNS SETTINGS ...................................... 9-1
9.1.1 Setting the Gateway to be a DHCP Client.......................................................................9-4
9.1.2 Using the Gateway with a Fixed Address ........................................................................9-4
9.2 VOIP PROTOCOL CONFIGURATION........................................................................................9-4
9.3 AUTOCONFIGURATION ...........................................................................................................9-4
9.4
9.5 CONFIGURING VOICE AND MANAGEMENT SERVICES ............................................................9-9
9.6 SNMP CONFIGURATION ......................................................................................................9-11
10 CONFIGURING SECURITY VIA THE WEB.......................................................................10-1
10.1 D
10.2 SETTING THE PASSWORD .....................................................................................................10-2
10.3 CONFIGURING ADVANCED SECURITY ..................................................................................10-3
10.4 S
10.5 ENABLING/DISABLING CONFIGURATION VIA TELNET .........................................................10-5
10.6 INSTALLING AN ENCRYPTION KEY ......................................................................................10-6
10.7 I
11 MISCELLANEOUS CONFIGURATION VIA WEB ............................................................11-1
DEFAULT MISCELLANEOUS CONFIGURATION ....................................................................................11-1
C
CALLER ID..........................................................................................................................................11-6
SYSLOG SERVER CONFIGURATION .....................................................................................................11-6
P
SIP ADVANCED CALLING FEATURES AND KEY SEQUENCE CONFIGURATION...................................11-9
RING TONES CONFIGURATION ..........................................................................................................11-12
12 PROTOCOL H.323 CONFIGURATION VIA THE WEB....................................................12-1
12.1 DEFAULT H.323 CONFIGURATION .......................................................................................12-1
CONFIGURING VLANS...........................................................................................................9-6
9.4.1 Using VLANs on the Gateway..........................................................................................9-7
9.4.2 VLAN Tagging on the Gateway........................................................................................9-7
9.4.3 VLAN Configuration Procedure on the Gateway............................................................9-7
EFAULT SECURITY CONFIGURATION
ETTING A PASSWORD FOR THE
NSTALLING A GENERAL CONFIGURATION FILE ENCRYPTION KEY
LOCK LOCALIZATION
ORT PROTOCOL CONFIGURATION
.......................................................................................................................11-5
.....................................................................................................11-7
.................................................................................10-2
CLI (
ONLY FOR UNITS WITH
AUX/C
ONSOLE PORT
....................................10-7
)........ 10-4
iii
52-80420-00 A0
Page 4
12.2 SETTING THE H.323 CONFIGURATION .................................................................................12-2
12.3 DTMF S
12.4 AUDIO/CODEC CONFIGURATION .......................................................................................12-5
13 PROTOCOL MGCP CONFIGURATION VIA WEB ...........................................................13-1
13.1 DEFAULT MGCP CONFIGURATION .....................................................................................13-1
13.2 S
13.3 RTP TELEPHONE EVENT (RFC2833) CONFIGURATION ......................................................13-4
13.4 AUDIO/CODEC CONFIGURATION .......................................................................................13-5
14 PROTOCOL SIP CONFIGURATION VIA WEB .................................................................14-1
14.1 DEFAULT SIP CONFIGURATION ...........................................................................................14-1
14.2 SIP SERVER CONFIGURATION ..............................................................................................14-2
14.3 SIP E
14.4 LINE-1 AND LINE-2 STATUS AND CONFIGURATION ............................................................14-8
14.5 AUDIO/CODEC CONFIGURATION .....................................................................................14-11
14.6 S
15 COMPLETING THE GATEWAY CONFIGURATION VIA WEB ...................................15-1
16 SNMP MANAGEMENT OVERVIEW....................................................................................16-2
16.1 NETWORK MANAGEMENT STATION SETUP .........................................................................16-2
17 NETWORK CONFIGURATION VIA TELNET ...................................................................17-1
17.1 DEFAULT LAN CONFIGURATION.........................................................................................17-1
17.2 NETWORK CONFIGURATION COMMANDS ............................................................................17-2
17.2.1 Enabling DHCP.........................................................................................................17-3
17.2.2 Setting the IP Address of the LAN Interfaces............................................................17-3
17.2.3 Setting the Subnet Mask of the LAN Interface..........................................................17-4
17.2.4 Setting the IP Address of the Default Gateway.........................................................17-4
17.2.5 Setting the IP Address of the DNS Server.................................................................17-4
17.2.6 Setting the Automatic Configuration ID ...................................................................17-5
17.2.7 Enabling the Use of DHCP Options 66, 67..............................................................17-5
17.2.8 Enabling the Auto Config Mode................................................................................17-6
17.2.9 Setting the TFTP/HTTP Server IP Address ..............................................................17-6
17.2.10 Setting the File Name ................................................................................................17-7
17.3 LAN DISPLAYING COMMANDS ...........................................................................................17-7
17.3.1 Displaying all the LAN Configuration......................................................................17-8
17.3.2 Displaying the IP Address of the LAN Interface.......................................................17-8
17.3.3 Displaying the Subnet Mask of the LAN Interface....................................................17-9
18 SECURITY CONFIGURATION VIA TELNET....................................................................18-1
18.1 DEFAULT SECURITY CONFIGURATION.................................................................................18-1
18.2 SECURITY CONFIGURATION COMMANDS.............................................................................18-1
18.2.1 Entering into LAN Configuration Mode ...................................................................18-2
18.2.2
18.2.3 Enabling DHCP Security ..........................................................................................18-2
18.2.4 Setting Management IP Addresses............................................................................18-3
18.3 SECURITY DISPLAYING COMMANDS....................................................................................18-3
18.3.1 Displaying all the Security Parameters ....................................................................18-4
18.3.2 Displaying the Advanced Security Status..................................................................18-4
18.3.3
18.3.4 Displaying Management IP Addresses .....................................................................18-5
19 HTTP CONFIGURATION VIA TELNET..............................................................................19-1
19.1 DEFAULT HTTP CONFIGURATION .......................................................................................19-1
19.2 HTTP C
19.2.1 Entering into HTTP Configuration Mode.................................................................19-1
19.2.2
19.3 HTTP D
IGNALING
ETTING THE
XTENSIONS
ELECTING A PREFERRED
Enabling Advanced Security .....................................................................................18-2
Displaying the DHCP Security Status.......................................................................18-5
ONFIGURATION COMMANDS
Enabling/Disabling Configuration via HTTP...........................................................19-2
ISPLAYING COMMANDS
...............................................................................................................12-3
MGCP C
ONFIGURATION
..................................................................................................................14-6
CODEC
................................................................................13-2
SIP......................................................................14-12
FOR
..................................................................................19-1
..........................................................................................19-2
iv
52-80420-00 A0
Page 5
v
19.3.1 Entering into HTTP Configuration Mode.................................................................19-2
20 CONFIGURING VLANS VIA TELNET.................................................................................20-1
20.1 D
20.2 VLAN CONFIGURATION COMMANDS .................................................................................20-1
20.3 VLAN DISPLAYING COMMANDS.........................................................................................20-5
21 INTERFACE CONFIGURATION VIA TELNET.................................................................21-1
21.1 D
21.2 INTERFACE CONFIGURATION COMMANDS...........................................................................21-1
21.3 I
22 EXECUTING REPORTS VIA TELNET ................................................................................22-1
22.1 REPORTS COMMANDS ..........................................................................................................22-1
23 PROTOCOL H.323 CONFIGURATION VIA TELNET ......................................................23-1
23.1 DEFAULT H.323 CONFIGURATION .......................................................................................23-1
23.2 H.323 CONFIGURATION COMMANDS...................................................................................23-1
23.3 H.323 DISPLAYING COMMANDS ..........................................................................................23-4
24 PROTOCOL MGCP CONFIGURATION VIA TELNET ....................................................24-1
24.1 DEFAULT MGCP CONFIGURATION .....................................................................................24-1
24.2 MGCP C
EFAULT
20.2.1
20.2.2 Enabling Using VLANs..............................................................................................20-2
20.2.3 Creating a New VLAN...............................................................................................20-3
20.2.4
20.2.5 Adding Ports to a VLAN and Setting the Port’s Default VLAN ...............................20-3
20.2.6 Removing Ports from a VLAN...................................................................................20-4
20.2.7
20.2.8 Assigning VLAN and Priority Tag VoIP Call Session Start Frames .......................20-4
20.2.9 Assigning VLAN, Priority Tag and ToS to the Outgoing RTP Frames....................20-5
20.3.1 Displaying the VLAN Configuration.........................................................................20-6
20.3.2 Displaying the Service VLAN Configuration............................................................20-6
EFAULT INTERFACE CONFIGURATION
21.2.1
21.2.2 Setting the Interface’s State.......................................................................................21-2
21.2.3 Setting the Interface’s Duplex Speed ........................................................................21-2
21.2.4
NTERFACE DISPLAYING COMMANDS
21.3.1 Displaying the Specified Interface Configuration ....................................................21-4
21.3.2
22.1.1 Entering into Report Mode........................................................................................22-1
22.1.2 Entering into Statistics Mode....................................................................................22-1
22.1.3 Displaying the Interfaces’ Statistics..........................................................................22-2
22.1.4 Clearing the Interfaces’ Statistics.............................................................................22-6
22.1.5 Entering into Download Mode..................................................................................22-6
22.1.6 Displaying the Configuration Download Status.......................................................22-7
23.2.1 Entering into H.323 Configuration Mode.................................................................23-2
23.2.2
23.2.3 Setting the Dial Plan Matching String......................................................................23-2
23.2.4 Setting the Phone Number of Line 1 .........................................................................23-3
23.2.5
23.2.6 Setting the Caller ID for Line 1.................................................................................23-3
23.2.7 Setting the Caller ID for Line 2.................................................................................23-4
23.3.1 Displaying all the H.323 Configuration ...................................................................23-5
23.3.2 Displaying the Gatekeeper IP Address .....................................................................23-5
23.3.3 Displaying the Dial Plan Matching String ...............................................................23-5
23.3.4 Displaying the Phone Number of Line 1...................................................................23-5
23.3.5 Displaying the Phone Number of Line 2...................................................................23-5
23.3.6 Displaying the Caller ID for Line 1 ..........................................................................23-6
23.3.7 Displaying the Caller ID for Line 2 ..........................................................................23-6
VLAN C
Entering into VLAN Configuration Mode .................................................................20-2
Deleting an Existing VLAN .......................................................................................20-3
Assigning VLAN and Priority Tag to the Management Packets ..............................20-4
Entering into Interface Configuration Mode............................................................21-2
Enabling Flow Control on the Interface...................................................................21-3
Displaying the Configuration of all the Interfaces ...................................................21-4
Setting the Gatekeeper IP Address............................................................................23-2
Setting the Phone Number of Line 2 .........................................................................23-3
ONFIGURATION COMMANDS
ONFIGURATION
......................................................................................20-1
...............................................................................21-1
..................................................................................21-3
.................................................................................24-1
52-80420-00 A0
Page 6
24.2.1 Entering into MGCP Configuration Mode ...............................................................24-2
24.2.2 Setting the Call Agent’s IP Address..........................................................................24-2
24.2.3 Setting the Call Agent’s Port.....................................................................................24-3
24.2.4 Setting the Endpoint Domain Name..........................................................................24-3
24.3 MGCP D
24.3.1 Displaying All the MGCP Parameters......................................................................24-4
24.3.2 Displaying the Call Agent’s IP Address ...................................................................24-4
24.3.3 Displaying the Call Agent’s Port ..............................................................................24-4
24.3.4 Displaying the Endpoint Domain Name ...................................................................24-5
24.3.5 Displaying the Phone line Status ..............................................................................24-5
25 PROTOCOL SIP CONFIGURATION VIA TELNET ..........................................................25-1
25.1 DEFAULT SIP CONFIGURATION ...........................................................................................25-2
25.2 SIP CONFIGURATION COMMANDS .......................................................................................25-2
25.2.1
25.2.2 Setting the SIP Server's IP Address...........................................................................25-3
25.2.3 Setting the SIP Server's Port Number .......................................................................25-4
25.2.4
25.2.5 Enabling/Disabling Sending REGISTER Request....................................................25-4
25.2.6 Setting the Dial Plan Matching String......................................................................25-5
25.2.7
25.2.8 Setting the Phone Number of Line 1 .........................................................................25-5
25.2.9 Setting the Phone Number of Line 2 .........................................................................25-6
25.2.10 Setting the Caller ID for Line 1.................................................................................25-6
25.2.11 Setting the Caller ID for Line 2.................................................................................25-6
25.2.12 Setting the SIP Port for Line 1 ..................................................................................25-7
25.2.13 Setting the SIP Port for Line 2 ..................................................................................25-7
25.2.14 Setting the AEC for Line 1.........................................................................................25-8
25.2.15 Setting the AEC for Line 2.........................................................................................25-8
25.2.16 Setting the User Name for Line 1..............................................................................25-8
25.2.17 Setting the User Name for Line 2..............................................................................25-9
25.2.18 Setting the Password for Line 1 ................................................................................25-9
25.2.19 Setting the Password for Line 2 ................................................................................25-9
25.2.20 Setting the NAT IP Address.....................................................................................25-10
25.2.21 Setting the RTP/RTCP Port Base............................................................................25-10
25.2.22 Setting the STUN Server IP Address.......................................................................25-10
25.2.23 Setting the STUN Server’s Port Number.................................................................25-11
25.3 SIP DISPLAYING COMMANDS ............................................................................................25-11
25.3.1 Displaying all the SIP Configuration......................................................................25-12
25.3.2 Displaying the SIP Server's IP Address..................................................................25-13
25.3.3 Displaying the SIP Server's Port Number...............................................................25-13
25.3.4 Displaying the SIP Server's Domain Name ............................................................25-13
25.3.5 Displaying the Sending REGISTER Request Status ...............................................25-14
25.3.6 Displaying the Dial Plan.........................................................................................25-14
25.3.7 Displaying the SIP Call Control Transport Protocol.............................................25-14
25.3.8 Displaying the Phone Number of Line 1.................................................................25-15
25.3.9
25.3.10 Displaying the Caller ID for Line 1 ........................................................................25-15
25.3.11 Displaying the Caller ID for Line 2 ........................................................................25-16
25.3.12 Displaying the SIP Port for Line 1..........................................................................25-16
25.3.13 Displaying the SIP Port for Line 2..........................................................................25-16
25.3.14 Displaying the AEC for Line 1................................................................................25-17
25.3.15 Displaying the AEC for Line 2 ................................................................................25-17
25.3.16 Displaying the User Name for Line 1 .....................................................................25-17
25.3.17 Displaying the User Name for Line 2 .....................................................................25-18
25.3.18 Displaying the Password for Line 1........................................................................25-18
25.3.19 Displaying the Password for Line 2........................................................................25-18
25.3.20 Displaying the NAT IP Address ..............................................................................25-19
25.3.21 Displaying the RTP/RTCP Port Base .....................................................................25-19
25.3.22 Displaying the STUN Server IP Address ................................................................25-19
ISPLAYING COMMANDS
Entering into SIP Configuration Mode.....................................................................25-3
Setting the SIP Server's Domain Name.....................................................................25-4
Setting the SIP Call Control Transport Protocol .....................................................25-5
Displaying the Phone Number of Line 2.................................................................25-15
........................................................................................24-3
vi
52-80420-00 A0
Page 7
25.3.23 Displaying the STUN Server’s Port Number ..........................................................25-20
25.3.24 Displaying the Phone-line Status............................................................................25-20
26 COMPLETING THE GATEWAY CONFIGURATION VIA TELNET ............................26-1
26.1 GENERAL COMMANDS .........................................................................................................26-1
26.1.1
26.1.2 Rebooting the Gateway..............................................................................................26-1
26.1.3 Setting the Configuration to the Factory Defaults....................................................26-2
26.1.4
27 LED DEFINITIONS ...................................................................................................................27-4
28 SPECIFICATIONS.....................................................................................................................28-1
Entering into Commands Mode.................................................................................26-1
Downloading Image or Configuration File Using TFTP\HTTP..............................26-2
vii
52-80420-00 A0
Page 8
1 Overview
This user guide provides instructions for installing and configuring the AccessLinX VoIP
Gateways. This chapter includes an overview of these products and information for obtaining
technical assistance. The following chapters include brief installation instructions and full
configuration and software-upgrade instructions for using and managing the VoIP Gateway.
AccessLinX, VoIP Gateway and Gateway unit are interchangeable terms throughout this
manual.
1.1 Product Overview
The AccessLinX units are analog gateways with two Voice-over-IP (VoIP) ports. The unit
enables the use of two independent analog telephone lines or FAX machines to make VoIP
phone calls over the Internet or Intranet. In addition, it enables connecting up to four
computers or segments to the network. Local computers are connected via Ethernet
10/100BaseTX ports. Uplink connection is via either a 100BaseFX SFP or SFF fiber optic or
a 10/100BaseTX copper port.
All Ethernet ports are connected by an advanced switching engine that supports VLANs and
QoS.
Figure 1-1 AccessLinX VoIP Gateway Front View
1.2 Features
The VoIP Gateway implements up to two simultaneous, independent audio channels and has
the following features:
• Support in all major protocols SIP (RFC 2543, RFC 3261), MCGP (RFC 2705, NCS),
ITU H.323 V2.0
1-1
52-80420-00 A0
Page 9
OVERVIEW
• Voice coding G.711 (A-law or µ-law) or G.723.1 or G729A/B or G726
Full-duplex acoustic echo cancellation with an effective 64ms tail length, -18dB network
•
echo cancellation
• Comfort noise generation and voice activity detection
• Fax/Modem Tone Detection
• DTMF tone generation and detection
• Call tone generation
Caller ID generation
•
o On-hook and off-hook (CID with call waiting)
o FSK (Bellcore), optional DTMF (Swedish)
Call Hold, Transfer and Waiting
•
• Call Forwarding
• 3-way call (conference)
Extremely flexible dial plan options
•
• Four 10/100Base-TX managed switched Ethernet ports
• Optional optical ports available:
o Single-mode LC 100BaseFX
Multi-mode MT-RJ 100BaseFX
o
• Support of sixteen 802.1Q compatible tagged VLANs
• VLAN support for voice channel
Supports assigning priority to voice frames with the 802.1 Priority tag or TOS field
•
• Advanced error and packet loss concealment technology
• DHCP-compliant IP address selection or fixed IP selection
Embedded HTTP server for remote Web browser-based configuration
•
• SNMP for remote configuration control and monitoring
• Telnet
Auto Configuration for mass deployment. Automatic software and configuration upgrades
•
using TFTP or HTTP
• Display LEDs for status monitoring
1-2
52-80420-00 A0
Page 10
OVERVIEW
1.3 Laser Safety
The emission produced by the end products described in this guide are under Class 1 emission
levels according to IEC 60825-1 and the FDA 21 CFR 1040.10 and 1040.1. These products
shall not be installed in an optical network handling above Class 1 levels.
1.4 How to Get Help
For technical support, please contact IMC Networks Technical Support at:
Tel: (949) 465-3000; (800) 624-1070 (in U.S. and Canada);
+32-16-550880 (Europe)
Fax: (949) 465-3020
E-Mail: techsupport@imcnetworks.com
www.imcnetworks.com
Web:
1-3
52-80420-00 A0
Page 11
2 Pre-Installation Requirements
Before you begin installing your AccessLinX, prepare the site. Make sure that the operating
environment meets the physical conditions suitable for such equipment (see operating
temperature and humidity specifications
2.1 Supporting Equipment Requirements
To set up and use an AccessLinX VoIP Gateway unit you need:
LAN cables (copper or fiber, depending on the Gateway’s LAN ports) to connect
•
the VoIP Gateway, PCs, and your local network.
• Use a cross cable for the Ethernet 10/100Base-TX connections from the Gateway to
another Gateway or to a switch or hub.
in at the end of this document).
• Use a straight cable to connect the unit to computer devices.
The call management devices and applications appropriate for the call protocol
•
installed on the VoIP Gateway (H.323, MGCP, or SIP).
• One or Two analog phones or fax machines.
2.2 Telephones and Accessories
The VoIP Gateway supports all standard analog DTMF telephones and accessories, including:
• Single-line touch-tone telephones.
• Multiple-line touch-tone telephones.
• Touch-tone telephones with redial or speed-dial features.
Phones or accessories that support Caller ID.
•
• Answering machines with touch-tone support.
• Phones or accessories that support Distinctive Ring.
• Fax machines
NOTE Pulse-dial telephones and accessories are not supported.
2-1
52-80420-00 A0
Page 12
3 Gateway Installation
The AccessLinX must be powered by an external UL listed limited power
source or Class II power source (AC/DC adapter), rated input: 100-240
VAC@0.5A, 47-63Hz, 5V@2.4A output.
The phone ports (Phone1 and Phone2) are intended for indoor connections
only and may not be connected to the Telecommunication Network.
3.1 Installing the VoIP Gateway
To install your VoIP Gateway:
1. Unpack the VoIP Gateway unit.
Figures 3-1, 3-2 and 3-3 show the connectors on the rear of the unit for each of three
available gateway models:
• The RJ-11 telephone ports Phone 1 and Phone 2 connect to the telephony devices.
• The PSTN (lifeline) port can be connected as a standby to the public telephone
network. In case of power failure, the phone connected to the Phone1 port will be
automatically switched from VoIP to this line, for regular telephone
communication.
• The LAN ports connect to the LAN, to other VoIP Gateway units and to computers.
• The AUX/Console port, available only in some AccessLinX products, connects to
the serial port on a PC for configuring the unit.
PSTN port Telephone ports LAN ports SFP 100BaseFX
Figure 3-1 AccessLinX with SFP VoIP Gateway Rear View
3-1
Uplink port
DC power
connector
52-80420-00 A0
Page 13
GATEWAY INSTALLATION
PSTN port Telephone ports LAN ports DC power
connector
Figure 3-2 AccessLinX VoIP Gateway Rear View
PSTN port Telephone ports LAN ports AUX/Console
port (optional)
Figure 3-3 AccessLinX VoIP Gateway Rear View with AUX/Console Port
DC power
connector
IMPORTANT ONLY the PSTN (Life Line) port can be connected to the Public
Telecommunication Network. The phone ports (Phone1 and Phone2)
are intended for indoor connections only and may not be connected to
the Telecommunication Network.
2. Choose a location that is near the devices to be connected and close to an electrical outlet.
Place the Gateway unit on a desktop or other level surface. You may also mount the unit
on the wall, using two wood screws 6.1” (15.5 cm) apart for horizontal positioning or
2.68” (6.8 cm) apart for vertical positioning. Use screws as specified in Table 3-1 below.
Holes for mounting on the wall are situated at the bottom of the unit (see Figure 3-4).
3-2
52-80420-00 A0
Page 14
S
H
Distance for vertical hanging
Distance for vertical hanging
Distance for vertical
= 2.68” ( 6.8 cm)
= 2.68” ( 6.8 cm)
mounting = 2.68” ( 6.8 cm)
Clasp for fastening DC
power-feed cable
Figure 3-4 Bottom of Gateway VoIP Unit
Table 3-1 Mounting screws maximum dimensions
GATEWAY INSTALLATION
Distance for horizontal
Distance for horizontal
Distance for horizontal
Distance for horizontal
Distance for horizontal
hanging = 6.1” ( 15.5 cm)
hanging = 6.1” ( 15.5 cm)
hanging = 6.1” ( 15.5 cm)
hanging = 6.1” ( 15.5 cm)
mounting = 6.1” ( 15.5 cm)
Head diameter (H): Max 9 mm (0.35")
Shank diameter (S): Max 3.5 mm (0.138")
Length (L): 25-30 mm (1"-1.2")
L
3. Connect to the network via an RJ-45 LAN 100Base-TX connector or the fiber optic
connector of the Gateway unit.
4. If you use an RJ-45 connector, use a cross cable to connect the Gateway unit to another
unit, or to a switch or hub. The cable length must not exceed the maximum length
specified for the media type.
5. Connect any required PC to the unit using a straight cable.
6. Connect the phones to the Gateway unit via the RJ-11 connectors. Up to five phones in
parallel may be connected to each port.
7. Connect the power adapter to the power connector of the unit and to the power source.
Fasten the DC power-feed cable to the clasp at the bottom of the unit to avoid accidental
disconnection.
8. Verify that all system components are properly installed. Make sure that all cable
connectors are securely positioned in the appropriate ports.
9. Do not place any object on top of the unit. Make sure that the ventilation holes on top of
the unit are not blocked.
The Gateway unit is now ready to be configured.
3-3
52-80420-00 A0
Page 15
4 Gateway Initial Configuration
and Background Information
To configure the Gateway, proceed as follows:
1. Assign an IP Address to the Gateway.
2. Configure the VoIP protocol parameters appropriate to the protocol installed (H.323 Gatekeeper and Dial plan; MGCP - Call agent; SIP - SIP Server).
3. Optionally configure other general parameters.
4. Save the new settings and reset the Gateway unit.
You can use a terminal to configure local basic settings, such as the unit’s IP and most of the
unit’s parameters. For detailed instructions, see Chapter 57: Configuring the Gateway via a
Terminal.
For extended configuration settings, you must use the WEB configuration. You can use SNMP
to configure SNMP parameters, and to control and monitor the Gateway unit. Specific
instructions for configuring various Gateway functions via the WEB are presented in:
• Chapter 9: Configuring the Gateway via the Web
• Chapter 12: Protocol H.323 Configuration via the Web
• Chapter 13: Protocol MGCP Configuration via Telnet
• Chapter 14: Protocol SIP Configuration via Web
• Chapter 16: SNMP Management Overview
Once the Gateway is powered up, addressed, and configured; and the call management device
(Gatekeeper, Call agent or SIP Server) is operating properly, you can place a call.
4.1 Keypad Configuration
Basic configuration commands such as setting factory defaults and changing the IP mode from
DHCP to fixed, or hearing the current IP address announced, can be done by entering
configuration commands using the telephone keypad. Use this option if you have lost normal
access to the Gateway via a PC. The following commands are active ten minutes from boot on
the telephone connected to line 1.
To set the factory defaults:
4-1
52-80420-00 A0
Page 16
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
Dial ##3332858 (D,E,F,A,U,L,T). Once the command is accepted, the Management LED on
the front panel will glow a steady green and after about 30 seconds the unit will power up with
factory defaults.
To set the IP mode:
To change the IP mode from DHCP to fixed or vice-versa, dial ##3427937 (D,H,C,P,Y,E,S) for
DHCP or ##342766 (D,H,C,P,N,O) for fixed IP 10.1.0.54 Mask 255.255.0.0. The Management
LED on the front panel will glow a steady green for about 3 seconds and the unit will boot with
the required IP setting.
To hear the current IP address announced over the headset:
Dial ## 472337 (I,P,A,D,D,R).
4.1.1 Keypad Configuration for MGCP
If the Keypad Configuration option is used before the Gateway is registered with the Call
Agent, dial tone and other tones like “busy” will not be generated. To use the Keypad
Configuration option, dial a valid Keypad Configuration sequence. If the “dot” confirmation is
not heard after a short period, put the handset on the hook and repeat the dialed sequence.
4.2 Understanding DHCP
DHCP (Dynamic Host Configuration Protocol) provides a framework for passing configuration
information to hosts on a TCP/IP network. DHCP, based on the Bootstrap Protocol (BOOTP),
adds the capability of automatic allocation of reusable network addresses and additional
configuration options. DHCP captures the behavior of BOOTP relay agents and DHCP
participants can interoperate with BOOTP participants.
DHCP provides configuration parameters to Internet hosts. DHCP consists of two components:
a protocol for delivering host-specific configuration parameters from a DHCP Server to a host
and a mechanism for allocating network addresses to hosts.
DHCP is built on a client-server model, where designated DHCP Server hosts allocate network
addresses and deliver configuration parameters to dynamically configured hosts. Throughout
the remainder of this document, the term
parameters through DHCP, and the term client refers to a host requesting initialization
parameters from a DHCP Server.
DHCP supports three mechanisms for IP address allocation:
• Automatic allocation - DHCP assigns a permanent IP address to a client.
• Dynamic allocation - DHCP assigns an IP address to a client for a limited period of time
(or until the client explicitly relinquishes the address). Dynamic allocation allows automatic
reuse of an address that is no longer needed by the client to which it was assigned. Thus,
dynamic allocation is particularly useful for assigning an address to a client that will be
connected to the network only temporarily or for sharing a limited pool of IP addresses
among a group of clients that do not need permanent IP addresses. Dynamic allocation may
also be a good choice for assigning an IP address to a new client being permanently
refers to a host providing initialization
server
4-2
52-80420-00 A0
Page 17
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
connected to a network where IP addresses are scarce and it is important to reclaim them
when old clients are retired.
• Manual allocation - a client's IP address is assigned by the network administrator, and
DHCP is used simply to convey the assigned address to the client. A particular network will
use one or more of these mechanisms, depending on the policies of the network
administrator. Manual allocation allows DHCP to be used to eliminate the error-prone
process of manually configuring hosts with IP addresses in environments where (for
whatever reasons) it is desirable to manage IP address assignment outside of the DHCP
mechanisms.
As shown in Figure 4-1, the parameter negotiation starts with a DHCPDISCOVER broadcast
message from the client seeking a DHCP Server. The DHCP Server responds with a
DHCPOFFER unicast message offering configuration parameters (such as an IP address, a
MAC address, a domain name, and a lease for the IP address) to the client. The client returns a
DHCPREQUEST broadcast message requesting the offered IP address from the DHCP Server.
The DHCP Server responds with a DHCPACK unicast message confirming that the IP address
has been allocated to the client.
Figure 4-1: Obtaining an IP Address from a DHCP Server
The client may suggest values for the IP address and lease time in the DHCPDISCOVER
message. The client may include the requested IP address option to suggest that a particular IP
address be assigned, and may include the IP address lease time option to suggest the lease time
it would like to have. The requested IP address option is to be filled in only in a
DHCPREQUEST message when the client is verifying network parameters obtained
previously.
If a server receives a DHCPREQUEST message with an invalid requested IP address, the
server should respond to the client with a DHCPNAK message and may choose to report the
problem to the system administrator. The server may include an error message in the message
option.
For setting the Gateway as DHCP client via Telnet see Configuring the Gateway via Telnet
and via Web see Configuring the Gateway via the Web
4-3
,
.
52-80420-00 A0
Page 18
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
4.2.1 When Should Clients Use DHCP
A client should use DHCP to reacquire or verify its IP address and network parameters
whenever the local network parameters may have changed (e.g. at the Gateway boot time or
after a disconnection from the local network), as the local network configuration may change
without the client's or user’s knowledge.
If a client has knowledge of a previous network address and is unable to contact a local DHCP
Server, the client may continue to use the previous network address until the lease for that
address expires. If the lease expires before the client can contact a DHCP Server, the client
must immediately discontinue use of the previous network address and may inform local users
of the problem.
4.3 Understanding NAT and NAPT
The goal of the Network Address Translator (NAT) is to provide functionality as if the private
network had globally unique addresses and the NAT device was not present. Basic NAT allows
a one-to-one mapping between one private address and one public address. In its simplest
configuration, the NAT operates on a router connecting two networks together. One of these
networks (designated as inside) is addressed with either private or obsolete addresses that need
to be converted into legal addresses before packets are forwarded onto the other network
(designated as outside). The translation operates in conjunction with routing, so that NAT can
simply be enabled on a customer-side Internet access router when translation is desired.
NAPT (Network Port Address Translator) maps a single public address to one or many internal
addresses and all network IP addresses on the connected computers are local and cannot be seen
by the outside world.
NAT with Port Address Translation (NAPT) is an extension to NAT in that NAPT uses
TCP/UDP ports in addition to network addresses (IP addresses) to map many private network
addresses to a single outside address.
A VoIP Gateway behind NAT might require special settings. For solutions in SIP, see NAT
Settings in Chapter 14: Protocol SIP Configuration via Web.
4.4 Understanding NTP
The NTP is designed to synchronize clocks among devices in a network. NTP runs over User
Datagram Protocol (UDP), which runs over IP. An NTP network usually gets its time from an
authoritative time source, such as a radio clock or an atomic clock attached to a time server.
NTP then distributes this time across the network. NTP is extremely efficient; no more than one
packet per minute is necessary to synchronize two devices to within a millisecond of one
another.
NTP is a tiered time distribution system with redundancy capability. NTP measures delays
within the network and within the algorithms on the machine on which it is running. Using
these tools and techniques, it is able to synchronize clocks to within milliseconds of each other
4-4
52-80420-00 A0
Page 19
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
when connected on a Local Area Network and within hundreds of milliseconds of each other
when connected to a Wide Area Network. The tiered nature of the NTP time distribution tree
enables a user to choose the accuracy needed by selecting a level (stratum) within the tree for
machine placement. A time server placed higher in the tree (lower stratum number), provides a
higher likelihood of agreement with the UTC time standard.
You should use the security features of NTP to avoid the accidental or malicious setting of an
incorrect time by using an encrypted authentication mechanism.
NTP has become a standard for internet time synchronization. Most importantly, there are more
than 100000 free NTP time servers in the world.
For setting the IP address of the NTP server via Web see Section Clock Localization
.
4.4.1 Daylight Saving Time (Summer Time)
You can configure your Gateway to observe the Daylight Saving Time (DST) in your area. This
way, whenever the system time is updated using a time server located in a different time area, it
will be automatically corrected with the local DST time offset.
The DST is followed by the U.S. standards. You can have the Gateway advance the clock one
hour at 2:00 a.m. on the first Sunday in April and move back the clock one hour at 2:00 a.m. on
the last Sunday in October. You can also explicitly specify the start and end dates and times and
whether or not the time adjustment recurs every year.
For enabling automatically adjust the internal clock to daylight saving time according to the
local time zone via Web see Section Clock Localization
.
4.5 Understanding Syslog
The system message logging can save messages in a Syslog server. The system message
logging facility has the following features:
• It provides you with logging information for monitoring and troubleshooting.
• It allows you to select the types of logging information to be captured.
It allows you to select the destination of captured logging information.
•
You can specify which system messages should be executed, based on their severity level (see
Table 4-1). You can monitor system messages by viewing the logs on a Syslog server.
4-5
52-80420-00 A0
Page 20
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
Table 4-1: Log Message Severity Levels
Severity Level Keyword Description
0 emergency Internal error occurred. The Gateway reached a crash
state and cannot continue to operate.
1 alert Internal error occurred. The Gateway might operate
incorrectly.
2 critical Internal error or non supported event occurred.
3 error Error on a setting done by user.
4 warning Warning on a setting done by user.
5 notification Notifies on configuration setting.
6 information Informs on state changes.
7 debug Debug message to be used by Technical Support.
For setting the Syslog server IP address and the log message severity level via Web see Section
Syslog Server Configuration
.
4.5.1 Remote Logging
To enable remote logging on a UNIX Syslog host facility, follow these steps:
1. Configure the Syslog host to accept and log messages.
2. Enable remote logging by using the enable syslog command.
3. Configure remote logging by using the following command:
config syslog {add} <ipaddress> <facility> {<severity>}
4. Specify the following:
— ipaddress — The IP address of the Syslog host.
— facility — The Syslog facility level for local use. Options include
local0
through
local7
.
— severity — Filters the log to display message with the selected severity or higher (more
critical).
Severities include (in order)
debug. If not specified, all messages are sent to the Syslog host.
emergency, critical, alert, error, warning, notice, info
4-6
52-80420-00 A0
, and
Page 21
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
4.6 Dial Plan for SIP and H.323
4.6.1 Default Dial Plan
A dial plan provides the unit with a map that is used to determine when a complete number has
been dialed. The number is then passed on to the SIP Server\Gatekeeper, which resolves it into
an IP address.
The default dial plan (>#|[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|x.T) includes strings separated by
the vertical bar character “|”. Once a match between one of the strings and the keys that have
been dialed is reached, the Gateway contacts the SIP Server\Gatekeeper and attempts to make a
call. The default dial plan includes the string [2-9]xxxxxxxxx meaning that dialed numbers can
be 10 digits long starting with any digit in the range 2-9. The string x.T (or x.t) in the default
dial plan means that after any dialed number and a pause of 4 seconds an attempt to make a call
is made. The user can use the default dial plan or set up an alternative plan. For detailed
explanation of possible dial plan schemes see following sections.
To set the dial plan when using the H.323 protocol via Web, see Setting the H.323
Configuration
Dial Plan Matching String
To set the dial plan when using the SIP protocol via Web, see SIP Server configuration
. To set the dial plan when using the H.323 protocol via Telnet, see Setting the
.
. To
set the dial plan when using the SIP protocol via Telnet, see Setting the Dial Plan Matching
.
String
4.6.2 Dial Plan Syntax
A dial plan is a case insensitive character string or a list of strings. Any telephone keypad
character is allowed:
| “0” | “1” | “2” | “3” | “4” | “5” | “6” | “7” | “9” | “#” | “
Table 4-2 lists the Dial Plan characters.
” |
*
4-7
52-80420-00 A0
Page 22
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
Table 4-2: The Dial Plan Characters
Character(s) Description
x One of the allowed telephone keypad characters.
T or t Short for Timer. Implies a four-second delay, and can only be used at
the end of a string.
x. Implies any number of characters (none or more).
>#
[character1character2]
P or p
R or r
| Used to separate between multiple possible Dial Plans.
Defines the character # as a terminating character. When dialing # the
dialed number preceding the character # is immediately sent. The
terminating character can only be entered after at least one user-dialed
digit. Optionally the Dial Plan >* can be used to define the character * as
the terminating character.
Defines any character in the range between character1 and character2.
Short for Prefix. Defines a prefix rule.
Short for Replace. Defines a replace rule.
4.6.3 Dial Plan Examples
This section describes the following dial plan examples:
Simple Dial Plan
•
• Basic Dial Plan
• Complex Dial Plan
Prefix Rule Dial Plan and
•
• Replace Rule Dial Plan.
4.6.3.1 Simple Dial Plan Example
The simple dial plan example allows dialing of seven-digit numbers (e.g. 2233445) or an
operator on 0. The dial plan is:
0T|xxxxxxx
meaning that a match is produced if you dial zero followed by a four-second delay, or if you
dial any seven-digit number.
4-8
52-80420-00 A0
Page 23
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
4.6.3.2 Basic Dial Plan Example
The basic dial plan allows dialing of any number of digits. The dial plan is:
x.T
This ensures a match against one or more digits. A match is produced when a delay of about 4
seconds follows any number of dialed digits.
4.6.3.3 Complex Dial Plan Example
Table 4-3 lists the complex dial plan characters.
Table 4-3: The Complex Dial Plan Characters
Character(s) Description
># The # character defined as a terminating character.
0T Local operator on 0.
00T Long distance operator on 00.
[3-5]xxx Four-digit local extension numbers starting with 3, 4, or 5.
8xxxxxxx Seven-digit local numbers prefixed with 8.
91xxxxxxxxxx Ten-digit long distance numbers prefixed with 91.
9011x.T International numbers starting with 9011 with zero or more digits.
The complete syntax scheme of this dial plan is
(>#|[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|x.T).
(>#|0T|00T|[3-5]xxx|8xxxxxxx|91xxxxxxxxxx|9011x.T)
4.6.3.4 Prefix Rule Dial Plan
Dial Plan Prefix is used to add a user defined prefix to the head of the dialed number.
Syntax:
p(STRING1)STRING2
If a dialed number matches STRING1, STRING2 is added to the head of the dialed number.
Example:
p(2x.t)00
This example adds digits 00 to any dialed number beginning with the digit 2.
4-9
52-80420-00 A0
Page 24
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
4.6.3.5 Replace Rule Dial Plan
Dial Plan Replace can be used to prevent a dialed sequence from being sent or a dialed
sequence can be replaced by another sequence.
Syntax:
r(STRING,STRING2)STRING3.
If a dialed number matches string1+string2, string1 is replaced by string3.
Example 1
: r(0,x.t)33
This example replaces leading 0 with 33 in a dialed number of any string beginning with zero.
Example 2:
r([1-3]0,xxx)
This example removes the digits 10, 20 or 30 from dialed numbers of format 10xxx, 20xxx or
30xxx.
Example 3:
r(1)345678
This example sets 1 as a shortcut for “345678”. Dialing 1 will be replaced with the number
345678.
4.7 DNS Resolver
The Domain Name System (DNS) is the means by which Internet domain names are located and
translated into Internet Protocol addresses. A domain name is a mnemonic “handle” to an Internet
address.
Because it would be impractical to maintain a central list of domain name/IP address
correspondences, the lists of domain names and IP addresses are distributed throughout the Internet
in a hierarchy of authority. There is probably a DNS server within close geographic proximity to your
access provider that maps the domain names in your Internet requests or forwards them to other
servers in the Internet.
Figure 4-2 demonstrates how the DNS operates. The client enters a domain name
(www.domainname.com) into his browser. The browser contacts the Client’s ISP to obtain the IP
address corresponding to the domain name. The ISP first tries to find the answer in its own “cached”
data. If it finds the answer, it returns it to the client's browser. Since the ISP isn’t in charge of the
DNS, and is just acting as a “DNS relay”, the answer is marked “non-authoritative”. If the answer is
not found or if it is too old (past the TTL), the ISP DNS contacts the nameservers for the domain
directly for the answer. If the nameservers are not known, the ISP looks for the information at the
‘root servers’, or ‘registry servers’. For com/net/org, these start with a.gtld-servers.net.
4-10
52-80420-00 A0
Page 25
GATEWAY INITIAL CONFIGURATION AND BACKGROUND
INFORMATION
Figure 4-2: Simplified Example of how DNS Works
You can define up to two DNS servers. If a query to the primary address fails to be resolved
after three attempts, the next gateway address is queried.
To use DNS, you must have a DNS server present on your network.
To set the SIP server DNS via Web, see SIP Server configuration
via Telnet, see
Setting the SIP Server's Domain Name
.
. To set the SIP server DNS
4-11
52-80420-00 A0
Page 26
5 Using the VoIP Gateway
To make a call, a Call Server (Gatekeeper/SIP Server/Call Agent) must be located on the
network and visible to all VoIP Gateway units. Placing a telephone call with your VoIP
Gateway for VoIP is the same as using a telephone with a standard telephone provider. Check
with the Call Server’s User Guide for available call features.
5.1 First Call
Place the first call from one phone line to a second phone line on the same Gateway unit. This
step ensures that the Gateway unit and the Call Server are operating properly and that all
configuration information is correct.
5.2 Placing Calls
To place a call:
1. Make sure that all equipment is powered up.
2. Check that the Call Server is running and that all endpoints are registered.
3. Check for a dial tone on each of the VoIP GateWay endpoints (phone lines), registered by
the Call Server.
A dial tone is not present until the Gateway unit is addressed and powered up, the Call
Server is running, and the endpoint (phone line) is registered. Keypad Configuration will
be active for 10 minutes starting from boot.
4. Place a call using the assigned telephone numbers.
5. Hang up the handset to terminate the call.
5-1
52-80420-00 A0
Page 27
USING THE VOIP GATEWAY
5.3 Adding Additional Units
You can add more Gateway units to the network, following the same procedure that is used to
establish the first unit. Additional units can exist anywhere visible to the Call Server and all
other Gateway units.
5.4 Advanced Calling features for SIP
In the following subsections:
• An expression such as ”dial flash + 7” implies “press on flash, then press on 7” (the
dialing sequence progresses as read from left to right).
The Star (or Asterisk) key is represented by the symbol “*”.
•
• The term destination number within an expression implies “dial the destination
number”.
5.4.1 Call Waiting
If you are engaged in a call and another party calls your line, you hear a short tone on your
line. The caller hears a ringing tone.
Press flash to toggle between calls.
5.4.2 Conference Call
To establish a conference, call the first number and then dial flash to hold the call, dial the
second number and before or after being answered, dial flash once more to establish the 3way call.
5.4.3 Forwarding a Call
To set the Forward option, dial * + 2 + destination number.
All calls to the phone with Forward set will be received at the destination number.
To unset the
Forward
option, dial * + 3.
5.4.4 Attended Transfer Call
To perform an Attended Transfer Call (the first callee is part of the transfer until new callee
answers) dial flash to hold the call, then dial the new number and wait to hear the ring. When
the phone rings or after the new callee answers, put the handset down.
5-2
52-80420-00 A0
Page 28
USING THE VOIP GATEWAY
Before the new callee picks up the handset, the phone will ring both at the destination number
and at your line.
By picking up the handset, the callee at the destination number will be engaged in the call with
the original caller.
If the callee at the destination number does not pick up the handset, you can receive the call by
picking up the handset as long as the phone rings.
5.4.5 Blind Transfer Call
To perform a Blind Transfer (a new call is automatically set between the caller and the second
callee and the first callee is immediately removed from the call) when a call is received, dial
*98 and then the destination number. The phone will ring at the destination number and the
first callee will have a dial tone.
5.4.6 Hold
To hold a call that you are receiving, press flash once. The caller will be at hold. To
retrieve the call, press
once more.
flash
When the caller is at hold, you can then run another call by dialing another number. When you
put the handset down the phone will ring. Pick up the call and you will be engaged in a call
with the original caller. If you wish you can then transfer the call as described in Attended
Transfer Call
or in Blind Transfer Call, or just proceed with the original call.
5.4.7 Conditional Call Forwarding
To activate “Conditional Call Forwarding”, dial *1 and then dial the destination number. If the call
has been made and the phone has not been picked up within 20 seconds, the call is forwarded to the
destination number. To cancel Call Forwarding, dial *3.
5.4.8 Do Not Disturb (DND)
To activate DND, dial *4. The caller will hear the "busy" tone. To cancel DND, dial *5
5.4.9 Redialing to Last Received Caller
To dial to the last received caller, dial *69.
5.4.10 Block Last Received Caller
To block the last received caller, dial *60. To start accepting calls from the blocked number again,
dial *80, or dial *60 to accept the previously blocked number and block the latest received caller.
5.4.11 Auto Redial
When a number is dialed and the dialed number is busy, the Caller can activate Auto Redial by
hanging up, dialing *66 and laying the handset down again. The Gateway will periodically dial
5-3
52-80420-00 A0
Page 29
USING THE VOIP GATEWAY
the busy number for a default period of 30 minutes. When the dialed number is reached the
Caller will be notified with a special distinctive ring. When the Caller picks up the phone he
will be immediately in the call.
If the called party hangs up and the caller does not pick up the phone when the special ring
tone is heard, then on the next attempt to use the phone the Caller will get a busy signal
indicating that the Auto Redial service succeeded. To place the next call, the caller needs to
hang up and pick up the phone again.
To cancel the periodic Auto Redialing before the timeout has been reached, dial *86.
5.5 Advanced Calling features for H.323
In the following subsections:
• An expression such as “dial flash + 7” implies “press on flash, then press on 7” (the
dialing sequence progresses as read from left to right).
• The Star (or Asterisk) key is represented by the symbol “
• The term destination number within an expression implies “dial the destination
number”.
”.
*
5.5.1 Call Waiting
If you are engaged in a call and another party calls your line, you hear a short tone on your
line. The caller hears a ringing tone.
To accept the new call, dial
flash +
. To return to the origin call, dial
*
flash +
again.
*
5.5.2 Conference Call
If you are engaged in a call and wish to add a third party, dial
party’s number. Once the third party answers the call, a 3-way call is established.
To drop the conference, dial flash + 8.
flash + 7
, then dial the third
5.5.3 Forwarding a Call
To set the Forward option, dial * + 2 + destination number.
All calls to the phone with Forward set will be received at the destination number.
To unset the Forward option, dial * + 3.
5-4
52-80420-00 A0
Page 30
USING THE VOIP GATEWAY
5.5.4 Transferring a Call
To transfer a call that you are receiving to another number, dial flash + 4 + destination
number
The phone will ring both at the destination number and at your line.
By picking up the handset, the callee at the destination number will be engaged in the call
with the original caller. Your phone will stop ringing.
If the callee at the destination number does not pick up the handset, you can receive the call
by picking up the handset as long as the phone rings.
and put the handset down.
5.5.5 Hold
To hold a call that you are receiving, press flash + 1. The caller will be at hold.
You can then run another call by dialing another number. When you put the handset down
the phone will ring. Pick up the phone and you will be engaged in a call with the original
caller. If you wish you can then transfer the call as described in Transferring a Call
proceed with the original call.
or just
5.6 Advanced Calling Features for MGCP
Advanced calling features are supported. Refer to your Call Agent for the advanced calling
features supported.
5-5
52-80420-00 A0
Page 31
6 Upgrading the Gateway
Firmware and Downloading
Configuration Files
The Gateway, when shipped, has code already installed in its Flash ROM memory and is
ready to run. This section describes the process for upgrading the Gateway’s firmware with a
new version of the ROM image. New ROM images can be obtained from the vendor of your
Gateway. This section also describes how to download configuration files to the Gateway.
A convenient way to set up the Gateway configuration is to download the configuration file to the
Gateway.
You can set downloading of the configuration file to the gateway to be in any of the following three
ways:
• Manual download
The configuration file and upgrade versions are downloaded directly via Telnet (see
Downloading the File Manually using Telnet
using the Web
• DHCP server auto configuration (see DHCP Automatic Configuration)
The configuration file and upgrade versions are downloaded automatically using a DHCP
server that is based at the provider’s network. The TFTP/HTTP server IP address and the file
name are provided by the DHCP server during the Bootp process and at half lease time. You
can set DHCP server Automatic Configuration either via the Web (see Setting DHCP
Automatic Configuration via the Web
Configuration via Telnet
• Fixed (provisioned) TFTP/HTTP Auto Configuration (see Fixed (Provisioned) HTTP or
TFTP Automatic Configuration
The configuration file and upgrade versions are downloaded automatically as needed during
boot and at fixed polling intervals using a TFTP/HTTP server based at the provider’s network.
The TFTP/HTTP server IP address and the file name are provisioned into the gateway. You can
set Fixed Automatic Configuration either via the Web (see Setting the TFTP/HTTP Server
“Root” Configuration File via the Web
Configuration File via Telnet
Two kinds of configuration files can be downloaded:
).
).
)
).
or Web (see Downloading the File Manually
) or via Telnet (see Setting DHCP Automatic
) or via Telnet (see Setting the TFTP Server “Root”
1. “Root” configuration file - the first file to be downloaded. This file can include any of the
Gateway configuration parameters and three execution flags. Each execution flag, when set, can
initiate one of the following possible actions:
• Downloading a secondary General configuration file.
6-1
52-80420-00 A0
Page 32
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
Upgrading the Gateway Application firmware.
•
• Upgrading the Gateway Loader firmware.
CONFIGURATION FILES
The “root” configuration file normally includes specific configuration parameters for the
Gateway being loaded.
Using the Gateway’s MAC address we can identify each Gateway uniquely and therefore
download to each Gateway its own “root” configuration file with the specific required
parameters.
2. “General” configuration file - The second configuration file will include general parameters,
common to a few or all the Gateway units in the network and also the following execution
flags.
Upgrading the Gateway Application firmware.
•
Upgrading the Gateway Loader firmware.
•
The configuration files can also include:
• The IP address of the TFTP/HTTP.
Firmware file names.
•
• Firmware file.
NOTE
1. If the Firmware file versions (APP_VERSION, LDR_VERSION) parameters
are used, a firmware upgrade will take place only if the Firmware file
version is different from the current firmware version.
2. The name of the “root” configuration file must be of the format
ipg_xxxx.cfg.
3. Configuration files must include header “; Configuration Parameters.
Don't edit this line !!! “. You will find an example for this file in this
document or see file ipg_example.cfg.
4. To control when the new configuration parameters will be included use
the ‘Automatic Configuration ID’.
NOTE
The Gateway’s configuration parameters are kept and are valid for all
firmware upgrades. Setting to defaults is recommended only
protocol was replaced, for example from SIP to MGCP etc.
6.1 Downloading the File Manually using Telnet
if the VoIP
IPG >
IPG >
IPG >
IPG >
IPG >
commands
IPG.Commands >copy 192.168.1.16 sip_232_4_42_23.rom
6-2
52-80420-00 A0
Page 33
Or:
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
IPG.Commands >
copy 192.168.1.16 ipg_232_00a012112233.cfg
NOTE
Copy will work only if Auto Configuration flag is disabled.
6.2 Downloading the File Manually using the Web
Figure 6-1: Download Page
6.3 DHCP Automatic Configuration
In DHCP download (Bootp), the Gateway must be in DHCP mode. The name of the “root”
configuration file and the IP of the TFTP/HTTP server are supplied to the Gateway when the
Gateway queries the DHCP server for an IP address and a boot file, during boot and at half leasetime.
6.3.1 Setting DHCP Automatic Configuration via the Web
1. Open the Network page (Figure 6-2).
6-3
52-80420-00 A0
Page 34
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
Figure 6-2: Network Status Page
2. In the horizontal menu bar of the Network page, select Network Update (Figure 6-3). Verify
that the Use DHCP to obtain LAN configuration option is selected.
Figure 6-3: Network Update Page
6-4
52-80420-00 A0
Page 35
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
3. In the horizontal menu bar of the Network page, select AutoConfiguration (Figure 6-4).
Verify that the
Enable Automatic Configuration
Figure 6-4: Automatic Configuration Page
option is selected.
4. For Microsoft DHCP server:
• Select Use DHCP code options 66, 67 in the Gateway.
In DHCP download (Bootp), the Gateway must be in DHCP mode. The name of the
“root” configuration file and the IP address of the TFTP server are supplied to the
Gateway when the Gateway queries the DHCP server for an IP address and a boot file,
during boot and at half lease-time.
• Reserve a station and define its MAC and IP.
• Add options 66,67.
Option 66 (
o
TFTP Server Name Option
when the sname (the “root” file) field in the DHCP header is being used for
DHCP options.
o Option 67 (Bootfile Name Option) - used to identify a boot-file (the “root”
file) when the file field is the DHCP header that is being used for DHCP
options.
• Set the Automatic configuration ID.
Set the Automatic configuration ID to be deferent from the value on the DHCP Server.
The Automatic configuration ID on the DHCP Server can be set to the value “always”,
which causes the configuration file to be executed on every boot without comparing to
the ID stored in the Gateway.
) - used to identify a TFTP server
5. Click on Save Settings to save the updated network settings.
6-5
52-80420-00 A0
Page 36
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
6.3.2 Setting DHCP Automatic Configuration via Telnet
1. Use the set show dhcp (sh dh) command in Network Configuration mode to verify that the
network configuration is obtained dynamically.
IPG.Config.Network >show dhcp
IPG.Config.Network >
IPG.Config.Network > dhcp|dh = y
If the Network configuration is not obtained dynamically, use the
set dhcp (se dh
Network Configuration mode.
IPG.Config.Network >set dhcp y
2. Use the show autoconfig (sh a) command in Network Configuration mode to verify that the
automatic configuration is enabled.
IPG.Config.Network >show autoconfig
IPG.Config.Network >
IPG.Config.Network > autoconfig|a = y
) command in
If the automatic configuration is not enabled, use the set autoconfig (se a) command in
Network Configuration mode.
IPG.Config.Network >set autoconfig y
3. For Microsoft DHCP server:
• Set the using of DHCP options 66, 67 by using the set options6667 (se o) command
in Network Configuration mode. You can display the status of the DHCP options 66,
67 by using the show options6667 (sh o) command in Network Configuration mode.
IPG.Config.Network >set options6667 y
IPG.Config.Network >show options6667
IPG.Config.Network >
IPG.Config.Network > options6667|o = y
• Set the Automatic configuration ID to a value different from the value on the DHCP
server, by using the
set id (se id
) command in Network Configuration mode. You can
display the Automatic configuration ID by using the show id (sh id) command in
Network Configuration mode. To cause the configuration file to be executed on every
boot and half lease time without comparing to the ID stored in the Gateway, set the
DHCP server the ID to
IPG.Config.Network >
IPG.Config.Network >
IPG.Config.Network >
IPG.Config.Network > id|id = 5
always
set id 5
show id
.
6-6
52-80420-00 A0
Page 37
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
Reboot the Gateway for applying the changes by using the
•
reboot power (r p
) command
in Commands mode.
IPG.Commands >reboot power
IPG.Commands > Warning! Reset system (y/n) ? y
6.4 Fixed (Provisioned) HTTP or TFTP Automatic
Configuration
You can supply the IP address of the HTTP/TFTP server and the name of the “root” configuration
file directly to the Gateway, instead of through the DHCP options. During boot, and at defined
polling periods, the Gateway will poll the TFTP/HTTP Server for a configuration file and will
determine if an upgrade is needed.
NOTE
If Automatic Configuration is enabled, the IP address of the HTTP/TFTP
Server and the name of the “root” configuration file that are supplied by the
user override the values obtained by the DHCP server.
6.4.1 Setting the TFTP/HTTP Server “Root” Configuration
File via the Web
1. Open the Network page (Figure 6-2).
2. In the horizontal menu bar of the
Network
page, select
Network Update
, You may select
either of the following options: Use DHCP to obtain LAN configuration or Fixed LAN
configuration
3. In the horizontal menu bar of the Network page, select AutoConfiguration
(Figure 6-3).
(Figure 6-4).
Verify that the Enable Automatic Configuration option is set.
4. Set the server protocol (HTTP or TFTP) in the Server protocol field.
5. Set the server IP address for the location of the configuration files in the Server Address field.
6. Set the name of the “root” configuration file in the File name field:
The file name has the following syntax: ipg_xxxx.cfg where xxxx is free text, up to 97 characters
in length.
7. Set the polling time (in hours) in the Polling time (hours) field. The polling time sets the time
period for the file download.
8. Click on Save Settings to save the updated network settings.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
6-7
52-80420-00 A0
Page 38
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
6.4.2 Setting the TFTP Server “Root” Configuration File via
Telnet
1. The network configuration can be obtained dynamically or can be fixed. Use the show dhcp
(
) command in Network Configuration mode to verify the DHCP configuration.
sh dh
IPG.Config.Network >
IPG.Config.Network >
IPG.Config.Network > dhcp|dh = y
show dhcp
If DHCP is disabled (n), enable it with the set dhcp (se dh) command in Network
Configuration mode:
IPG.Config.Network >set dhcp y
2. Use the set show autoconfig (sh a) command in Network Configuration mode to verify that
automatic configuration is enabled.
IPG.Config.Network >show autoconfig
IPG.Config.Network >
IPG.Config.Network > autoconfig|a = y
If automatic configuration disabled (n), enable it with the
set autoconfig (se a
) command in
Network Configuration mode.
IPG.Config.Network >set autoconfig y
3. Set the HTTP/TFTP server IP address for the location for the configuration files by using the
set tftpip (se t) command in Network Configuration mode. Use the show tftpip (sh t)
command in Network Configuration mode to verify the HTTP/TFTP server IP address.
IPG.Config.Network >
IPG.Config.Network >show tftpip
IPG.Config.Network >
IPG.Config.Network > tftpip|t = 10.2.197.9
set tftpip 10.2.197.9
4. Set the “root” configuration file name by using the set file (se f) command in Network
Configuration mode. Use the
verify the name of the “root” configuration file.
The file name has the following syntax: ipg_xxxx.cfg where xxxx is free text.
IPG.Config.Network >set file ipg_test.cfg
IPG.Config.Network >
IPG.Config.Network >
IPG.Config.Network > file|f = ipg_test.cfg
5. Reboot the Gateway to effect the changes by using the reboot power (r p) command in
Commands mode.
IPG.Commands >reboot power
IPG.Commands > Warning! Reset system (y/n) ? y
show file (sh f
show file
) command in Network Configuration mode to
6-8
52-80420-00 A0
Page 39
UPGRADING THE GATEWAY FIRMWARE AND DOWNLOADING
CONFIGURATION FILES
6.5 Creating and Encrypting Configuration Files
Use file ipg_example.cfg, as an example to create your own configuration file. Valid
commands can be found in the file
232_Autoconfig.pdf
format ipg_xxxx.cfg. For added security you can encrypt the “root” and General configuration
files.
To encrypt a configuration file:
1.
Install the encryption key(s) into the Gateway (see sections Installing an Encryption Key
and Installing a General Configuration File Encryption Key
characters.
2.
Encrypt the configuration file with the
utility using the same encryption key that
gwBin
you entered into the Gateway. Make sure that the name given to the encrypted file is of
format
ipg_xxxx.cfg
.
. The “root” file name must be of
). The maximum size is 64
6-9
52-80420-00 A0
Page 40
7 Configuring the Gateway via
Telnet
You can use CLI (Command Line Interface) commands via Telnet to configure and control the
Gateway.
Any workstation with a Telnet facility should be able to communicate with the Gateway over
the network. Two Telnet sessions can be opened concurrently with the Console. The Telnet
session will be disconnected after a specified time of inactivity.
7.1 Starting a Telnet Session
Before you can start a Telnet session, you must know the IP address of the Gateway. To open
the Telnet session, you must specify the IP address of the Gateway that you want to manage.
Check the user manual supplied with your Telnet facility if you are unsure of how to do this.
Once the connection is established, you will be prompted to log in. VT100 emulation and
V100 keys must be used.
When you log in, Telnet screen opens with a prompt for a password:
Password:>
Proceed as follows:
1. If a password has been entered in the Set Security Password Page
password.
Otherwise:
Press <Enter> to invoke the opening screen.
The opening screen includes specifications of:
• The hardware module type (232)
The software versions
•
• The current IP settings of the unit
• The unit’s MAC address
(Figure 10-1), enter this
The current CLI screen of the Application or the Loader.
•
For example:
7-1
52-80420-00 A0
Page 41
CONFIGURING THE GATEWAY VIA TELNET
///////////////////////////////////////////////////////////////////
/
//
//
//
//
// VoIP Gateway
//
// Application SIP Version 4.52.35
// Loader Version 4.52.35
// IP address 10.2.171.221
// MAC address 00:a0:12:0c:0f:a9
// Module type 232
// 2 ports FXS phone
// 4 ports 10/100Base-T/TX
// CPU Hw Ver 7
// CLI APPLICATION
// UpTime 0 days, 05:02:20
// Real Time
//
//////////////////////////////////////////////////////////////////
IPG >
The IPG > prompt line indicates that the VoIP Gateway is in its main CLI mode. In this
mode, global and main-mode CLI commands are available.
To view the available commands in the current mode:
Press <?>.
A list of the available commands appears, describing each command briefly and showing
the minimal abbreviation allowed for each command name.
To apply a CLI command:
1. Type the command in lowercase characters. You may abbreviate any or all of the
keywords.
Examples of abbreviations: l or ? for list, en for end (as a rule, you may abbreviate
keywords down to the shortest unique abbreviation – any length between the full and
the shortest unique presentation is valid).
2. Press <Enter>.
To repeat a previously entered CLI command:
Repeatedly press on the UP ARROW key until the desired command appears. Up to 7
CLI commands are kept in memory.
7-2
52-80420-00 A0
Page 42
CONFIGURING THE GATEWAY VIA TELNET
7.2 Command Modes
The CLI user interface is divided into several modes. The mode you are currently in
determines the available commands. Enter a question mark (?) at the mode prompt to obtain a
list of commands available for each command mode.
7.2.1 Enable Mode
When you start a session, you begin in Enable mode. The Enable mode prompt is an angle
bracket (>):
IGP>
Enable mode can be password protected. By default, no password is set. You can set a
password using the Web management (for more information see Setting the Password
).
7.2.2 Commands Mode
The Commands mode allows you to perform general operations on the Gateway such as
rebooting, restoring the Gateway to the factory defaults and downloading a configuration file
or software image. The Commands mode is indicated by the following prompt:
IGP.Commands >
To access the Commands mode:
Type the commands command (or the c shortcut) in Enable mode:
IGP >commands
IGP >c
The system responds with the Commands prompt:
IGP.Commands >
7.2.3 Report Mode
The Report mode allows you to display the interfaces statistics and download configuration
information. The Report mode is indicated by the following prompt:
IGP.Report >
To access the Report mode:
Type the report command (or the r shortcut) in Enable mode:
IGP >report
IGP >r
7-3
52-80420-00 A0
Page 43
CONFIGURING THE GATEWAY VIA TELNET
The system responds with the Report prompt:
IGP.Report >
7.2.4 Statistics Mode
The Statistics mode allows you to display and clear the interfaces statistics. The Statistics
mode is indicated by the following prompt:
IGP.Report.Statistics >
To access the Statistics mode:
Step 1: Type the report command (o the r shortcut) in Enable mode:
IGP >report
IGP >r
The system responds with the Report prompt:
IGP.Report >
Step 2: Type the statistics command (or the s shortcut) in Report mode:
IGP.Report >statistics
IGP.Report >s
The system responds with the Statistics prompt:
IGP.Report.Statistics >
7.2.5 Download Mode
The Download mode allows you to display the configuration download status. The Download
mode is indicated by the following prompt:
IGP.Report.Download >
To access the Download mode:
Step 1: Type the report command (or the r shortcut) in Enable mode:
IGP >report
IGP >r
The system responds with the Report prompt:
IGP.Report >
Step 2: Type the download command (or the d shortcut) in Report mode:
7-4
52-80420-00 A0
Page 44
CONFIGURING THE GATEWAY VIA TELNET
IGP.Report >download
IGP.Report >d
The system responds with the Download prompt:
IGP.Report.Download >
7.2.6 Configuration Modes
Using the configuration modes (Global, Interface, etc.), you can make changes to the
Gateway’s configuration. If you save the configuration, these commands are stored and used
after rebooting. To access the various configuration modes, you must start at Global
Configuration mode.
The Global Configuration mode allows configuration capabilities. It is indicated by the
following prompt:
IGP.Config >
The following example indicates that the CLI is in Interface Configuration mode:
IGP.Config.Interface >
To access the Global Configuration mode:
Type the
IGP >
config
IGP >con
command (or the
config
shortcut) in Enable mode:
con
The system responds with the Global Configuration prompt:
IGP.Config.Interface >
Table 7-1 shows the configuration modes available in the Gateway.
7-5
52-80420-00 A0
Page 45
CONFIGURING THE GATEWAY VIA TELNET
Table 7-1: Configuration Modes Summary
Configuration
For configuring Command Syntax
Mode
Interface The Gateway physical interfaces
settings.
Security The security settings.
Network The network settings
IPG.Config >interface
IPG.Config.Interface >
IPG.Config >
in
IPG.Config.Interface >
IPG.Config >
security
IPG.Config.Security >
IPG.Config >se
IPG.Config.Security >
IPG.Config >netconfig
IPG.Config.Network >
IPG.Config >n
IPG.Config. Network >
SNMP SNMP settings
VLAN Virtual LANs (VLANs) settings.
HTTP The HTTP (Hypertext Transfer
Protocol) settings.
IPG.Config >snmp
IPG.Config.Snmp >
IPG.Config >sn
IPG.Config.Snmp >
IPG.Config >
vlan
IPG.Config.VLAN >
IPG.Config >v
IPG.Config.VLAN >
IPG.Config >http
IPG.Config.HTTP >
IPG.Config >ht
IPG.Config.HTTP >
7-6
52-80420-00 A0
Page 46
CONFIGURING THE GATEWAY VIA TELNET
Configuration
For configuring Command Syntax
Mode
SIP The SIP (Session Initiation
Protocol) settings.
H.323 The H.323 protocol settings.
MGCP The MGCP (Media Gateway
Control Protocols) settings.
IPG.Config >sip
IPG.Config.SIP >
IPG.Config >si
IPG.Config.SIP >
IPG.Config >h323
IPG.Config.H323 >
IPG.Config >h3
IPG.Config.H323 >
IPG.Config >
IPG.Config.Mgcp >
IPG.Config >m
IPG.Config.Mgcp >
mgcp
7.3 General Commands
Table 7-2 lists the commands you can use at all times, regardless of the type of the prompt that
is displayed.
Table 7-2: General Commands
Command Description
exit
help
quit
end
list (or ?)
Escape current mode and go to previous mode.
Display the format of available commands in the current mode. You
can also use the question mark (?) for displaying the list of
commands.
Disconnect and log out.
Escape current mode and go to Privileged (Enable) mode.
Display list of the command available in the current mode.
7-7
52-80420-00 A0
Page 47
CONFIGURING THE GATEWAY VIA TELNET
7.4 Using the CLI Commands
The CLI commands can be used in two forms:
1. Typing the full form of the command that is specified in the command help:
IPG.Config >?
IPG.Config > interface,in - Interface Configuration
IPG.Config > security,se - Advanced Security Configuration
IPG.Config > netconfig,n - Network Configuration
IPG.Config > vlan,v - VLAN Configuration
IPG.Config > http,ht - HTTP Configuration
IPG.Config > sip,si - SIP Configuration
IPG.Config > help,h - Display commands format
IPG.Config > list,l,? - Display command list
IPG.Config > end,en - current mode and go to main mode
IPG.Config > exit,ex - current mode and go to previous mode
IPG.Config > quit,q - Quit console
IPG.Config >interface
2. Using the abbreviated form (shortest unique form) of the command which is specified in the
command help.
IPG.Config >?
IPG.Config > interface,in - Interface Configuration
IPG.Config > security,se - Advanced Security Configuration
IPG.Config > netconfig,n - Network Configuration
IPG.Config > vlan,v - VLAN Configuration
IPG.Config > http,ht - HTTP Configuration
IPG.Config > sip,si - SIP Configuration
IPG.Config > help,h - Display commands format
IPG.Config > list,l,? - Display command list
IPG.Config > end,en - current mode and go to main mode
IPG.Config > exit,ex - current mode and go to previous mode
IPG.Config > quit,q - Quit console
IPG.Config >in
3. Using any combination longer than the abbreviated form and shorter than the full form of the
command which is specified in the command help:
IPG.Config >
inter
NOTE
Command abbreviations that are shorter than the specified abbreviated
forms are not accepted.
7-8
52-80420-00 A0
Page 48
8 Configuring the Gateway via a
Terminal
If your gateway unit has a Console port, you can use this port to enter the CLI described in
Configuring the Gateway via Telnet
To access the CLI via the Console port, proceed as follows:
1. Connect the special RJ-45 serial cable to the AUX/Console connector on the back panel.
Connect the other side of the cable to a standard VT-100 or compatible terminal, or to a
terminal emulator. The cable length must not exceed 10 meters.
The cable pin-out is as follows:
.
NOTE The cable is compatible with Cisco’s Router Console Cable with DB-9
adapter.
2. Power up the unit and the terminal.
3. Verify that the terminal is set to 9600 baud, 8 data bits, 1 stop bit, no parity, and no flow
control.
Once the initialization process ends, proceed described in Configuring the Gateway via
Telnet.
8-1
52-80420-00 A0
Page 49
9 Configuring the Gateway via the
Web
You can configure the VoIP Gateway remotely via a PC Web browser. To do so, enter the IP
address of the Gateway into the Web browser and access the Gateway. The VoIP Gateway can
be configured to use a fixed IP address or to acquire an IP address from a DHCP server. The
Gateway is factory set to acquire an IP from a DHCP server (use the show command at top
Console mode to see the current IP).
To update a setting, enter the required settings on a web page and then save the changes by
clicking on the Save button at the bottom of the page. Once all settings have been saved, select
the Reset option on the left-hand side of the Web page to reset the VoIP Gateway and activate
the new settings.
9.1 Configuring the Gateway’s IP Address and DNS Settings
To change the mode from using DHCP to fixed IP, or to assign a different fixed IP address,
configure the unit as follows:
1. If the Gateway unit is using DHCP:
Connect the Gateway to a network with a DHCP server.
•
• Configure a PC with an IP address on the same subnet.
2. Connect your PC to the Gateway (or via a hub or a switch).
3. Enter the IP address of the Gateway unit into the PC Web browser.
The gateway’s Home page appears (Figure 9-1).
9-1
52-80420-00 A0
Page 50
CONFIGURING THE GATEWAY VIA THE WEB
Figure 9-1 The Gateway’s Home Page
4. In the vertical menu bar on the left, select Network. The Network Status Page appears:
5. To change network settings, select Network Update on the horizontal menu bar. The
Network Update page appears (Figure 9-3). You may need to scroll down to display the
fields at the bottom of the page.
Figure 9-2 Network Status Page
9-2
52-80420-00 A0
Page 51
CONFIGURING THE GATEWAY VIA THE WEB
Figure 9-3 Network Update Page
6. Select either of the following options.
To use a fixed IP address:
Select
•
• Fill in or change the fields associated with fixed IP addressing:
fixed LAN Configuration
IP Address, IP Netmask, IP Gateway, IP DNS Server 1 and 2, etc.
Or
To use a DHCP server:
• Select Use DHCP to obtain LAN configuration
7. Scroll down to the bottom of the Web page, and click the Save Settings button.
8. Select Reset in the vertical menu bar, to reset the unit (see Completing the Gateway
Configuration via Web).
You can now use the new IP address.
9-3
52-80420-00 A0
Page 52
CONFIGURING THE GATEWAY VIA THE WEB
9.1.1 Setting the Gateway to be a DHCP Client
To use a DHCP server to supply an IP address to the Gateway, you must first configure the
Gateway appropriately by selecting the
described in step 6 above.
It is recommended that you configure your DHCP server to assign the same address to the
Gateway unit each time it is powered up. This will help to track the available Gateway units
during the Gateway and Gatekeeper configuration.
When the Gateway VoIP Gateway is powered up, it queries the DHCP server for an IP
address. You must know this “new” IP address, assigned by the server, in order to access the
Gateway Web Setup Facility. To determine which IP address refers to your VoIP Gateway,
look at the IP address in the CLI opening screen, that appears when the unit boots via Telnet
(See Configuring the Gateway via Telnet
browser, you can access the Gateway Web Configuration page.
Use DHCP to obtain LAN configuration
). by entering the Gateway IP address into your Web
option, as
9.1.2 Using the Gateway with a Fixed Address
If you do not have access to a DHCP server, and your Gateway is configured to use a DHCP
server, or if you do not know the IP used by the Gateway, configure your Gateway via the
keypad options (See Keypad Configuration
view the IP address or disable DHCP.
). If you have an AUX/Console port, you can also
9.2 VoIP Protocol Configuration
Once the VoIP Gateway unit has obtained its IP address, you can use the Web Configuration
to configure the VoIP Gateway. To be able to place calls, you must configure the VoIP
protocol parameters, appropriate to the VoIP protocol installed in the VoIP Gateway (H.323,
MGCP or SIP). Refer to sections 7-9 for details on H.323 configuration, MGCP configuration,
or SIP configuration.
9.3 Autoconfiguration
To enable and set automatic configuration (see Upgrading Gateway Firmware
and Downloading Configuration Files):
1. In the horizontal menu bar of the Network page, select AutoConfguration. The
Automatic Configuration page appears (Figure 9-4).
9-4
52-80420-00 A0
Page 53
CONFIGURING THE GATEWAY VIA THE WEB
Figure 9-4: Automatic Configuration Page
2. Select the Enable Automatic Configuration check box for enabling automatic
configuration.
3. Select the
Automatic configuration ID
. The Gateway will run the configuration file
only if the file name or ID is different from the ones currently stored in the Gateway.
For DHCP Download you can set the ID also at the DHCP server along with the file
name (e.g., ipg_12345.cfg, 8). For Fixed Auto Configuration the ID can be set also in
the “root” Configuration file.
The ID at the DHCP server or in the Configuration file can be set to the literal value
“always”, causing the configuration file to be executed on every boot without
comparing to the ID stored in the Gateway.
4. In DHCP download (Bootp), the Gateway must be in DHCP mode. The name of the
“root” configuration file and the IP of the TFTP server are supplied to the Gateway
when the Gateway queries the DHCP server for an IP address and a boot file, during
boot and at half lease-time.
To enable using DHCP options 66, 67, select the
Use DHCP code options 66,67
check box. When this check box is selected:
Option 66 (Boot Server Host Name) is set as the IP of the TFTP server for the “root”
configuration file.
Option 67 (Bootfile Name) is set as the name of the “root” configuration file.
5. For Fixed Auto Configuration set the polling interval in hours.
6. To select Fixed (Provisioned) Auto Configuration, supply the IP address of the
HTTP/TFTP server and the name of the “root” configuration file directly to the
Gateway, instead of through the DHCP options. During boot, and at defined polling
periods, the Gateway will poll the HTTP/TFTP Server for a configuration file and will
9-5
52-80420-00 A0
Page 54
CONFIGURING THE GATEWAY VIA THE WEB
determine if an upgrade is needed.
7. Set the Server IP address.
8. Set the file name (“root” configuration file) to download.
9. Set the Server protocol (HTTP or TFTP).
9.4 Configuring VLANs
To set VLAN configuration on your Gateway module:
1. In the vertical menu bar of the current Gateway Web page, select
The VLAN Configuration page appears (Figure 9-5).
2. Proceed as described in the following subsections.
VLAN
.
9-6
52-80420-00 A0
Page 55
CONFIGURING THE GATEWAY VIA THE WEB
Figure 9-5 VLAN Configuration Page
9.4.1 Using VLANs on the Gateway
VLANs (Virtual LANs) logically group a set of stations to communicate as if they were on the
same LAN segment. Traffic between VLANs is restricted. Unicast and broadcast traffic is
forwarded only to LAN segments of the same VLAN. Your gateway enables you to configure
up to sixteen 802.1Q-compatible VLANs. A VLAN is identified by a unique number from 1 to
4095 (VLAN ID). By default, the VLAN configuration is disabled and traffic is free to travel
between all Gateway ports.
9.4.2 VLAN Tagging on the Gateway
VLAN tagging is required to identify traffic from more than one VLAN on the same port. A
“tag” is simply the VLAN identification number (VLAN ID), as specified in the 802.1Q
standard. The tag is included in the packets forwarded across the LAN. You can allow the
Gateway to connect to non 802.1Q-compliant devices by adding/removing the tag from
packets according to tag definitions in the VLAN configuration table.
9.4.3 VLAN Configuration Procedure on the Gateway
Use the TAB key or click to move around the table in the VLAN configuration page. Your
Gateway is factory set with VLAN ID – 1 assigned by default to all the ports of the unit. Each
port must have a default ID. All packets received on the Gateway ports without a VLAN tag
will inherit the default VLAN ID of the receiving port as their VLAN ID.
9-7
52-80420-00 A0
Page 56
CONFIGURING THE GATEWAY VIA THE WEB
You can use the VLAN configuration page to define new VLANs.
To define a new VLAN, proceed as follows:
1. In the VLAN column, enter the new VLAN ID.
2. In the Ports table, in the row corresponding to the new VLAN ID:
In the column under the number of each port that is permitted to be a member of the new
VLAN:
• Enter T if packets of the VLAN are to be transmitted from the port with a VLAN
tag in the packet (Tagged).
• Enter U if packets of the VLAN are to be transmitted from the port without a VLAN
tag in the packet (Untagged).
3. You can use the Del key to remove a port, if it is not a member of the new VLAN.
4. Once the port members of a VLAN have been entered, you can assign the VLAN as the
default VLAN for one or more ports that belong to that VLAN. Select the proper VLAN
ID on the default VLAN row in all the required ports.
9-8
52-80420-00 A0
Page 57
CONFIGURING THE GATEWAY VIA THE WEB
5. If you wish to remove a VLAN from the VLAN column, first make sure it is not a
default VLAN for any port. If it is, assign another VLAN as default for the port(s) and
then delete the original VLAN.
Once the VLAN configuration table is set and VLAN Enable is selected, packets received at a
Gateway port will be forwarded only to ports of the same VLAN (ports that have their port
member field set to “T” or “U” for that VLAN).
Traffic addressed to the Gateway unit (Web management or VoIP protocol frames) will be
received and transmitted on any of the defined VLANs.
9.5 Configuring Voice and Management Services
To further refine the VLAN configuration and assign a VLAN per protocol, for frames where
the Gateway is the source or the destination, use the Voice and Management Services
Configuration screen (Figure 6-5). The user can assign VLAN and priority tags to outgoing
frames. This will help devices such as switches and routers in the LAN to serve the frames
with higher priority queues and with lower delays Service VLANs can be defined also for
security reasons.
To configure the Voice and Service management:
In the vertical menu bar of the current Gateway Web page, select Services.
The Voice and Management Services Configuration Page appears (Figure 9-6).
9-9
52-80420-00 A0
Page 58
CONFIGURING THE GATEWAY VIA THE WEB
Figure 9-6 Voice and Management Services Configuration Page
The following fields are available in this window.
NOTE VLAN tags are simply VLAN IDs. Priority tags are simply priority values.
Management/All
VLAN Tag
Priority Tag
VLAN Tag for RTP
packets
Priority Tag for RTP
packets
TOS for RTP
packets
VLAN Tag for Call
Signalling packets
Priority Tag for Call
Signalling packets
To assign a unique VLAN tag to all management including ping and
voice, enter a VLAN value in the range 1 – 4095.
To assign a priority tag to all management including ping and voice,
enter a value in the range 0 (lowest priority) to 7 (highest priority).
To assign a unique VLAN tag to the outgoing RTP frames, enter a
VLAN value in the range 1 – 4095. Overrides the VLAN Tag field.
To assign a priority tag to the outgoing RTP frames, enter a value in
the range 0 (lowest priority) to 7 (highest priority). Overrides the
Priority Tag field.
To assign a priority using the TOS field in the IP header of the RTP
frames, Insert a TOS value in the range 0-255. For example, enter a
TOS value of 16 for minimum delay. The default value is 160.
To assign a unique VLAN tag to the start frames of the VoIP call
session, enter a VLAN value in the range 1 – 4095. Overrides the
VLAN Tag
To assign a priority tag to the start frames of the VoIP call session,
enter a value in the range 0 (lowest priority) to 7 (highest priority).
Overrides the
field.
Priority Tag
field.
NOTE If a service VLAN is defined, the VLAN must be a valid VLAN for the incoming
port.
To define a VLAN on the incoming port, see section 9.4 : Configuring VLANs
9-10
.
52-80420-00 A0
Page 59
CONFIGURING THE GATEWAY VIA THE WEB
9.6 SNMP Configuration
To enable access of the VoIP Gateway from a Network Management Station, you must
configure SNMP parameters.
To view and update the SNMP configuration:
In the left-hand menu of the current Gateway Web page, select SNMP.
The SNMP Configuration page (Figure 9-7) appears.
The following fields are available in this window:
Figure 9-7 SNMP Configuration Page
9-11
52-80420-00 A0
Page 60
CONFIGURING THE GATEWAY VIA THE WEB
SNMP Trap Configuration:
IP address
Trap Community
SNMP Community Configuration:
Read Community
Write Community
SNMP System Info:
Contact Person
Administratively Assigned Name
Physical Location
For further details on SNMP features refer to Chapter 16: SNMP Management Overview.
9-12
52-80420-00 A0
Page 61
10 Configuring Security via the
Web
In today’s networks security is very important for protecting the Gateway and your local
network from hackers.
The following security features are available in the Getaway using the Web management
interface:
• Password - to prevent access to the Gateway’s configuration.
• Advanced security - specifying a list of IP addresses that can manage the Gateway (up to
eight IP addresses can be set in the IP address list).
• DHCP security – to receive an IP address and other configuration parameters only from a
DHCP server that is listed in the IP address list (up to eight IP addresses can be set in the
IP address list).
• Blocking the Gateway management via HTTP and/or Telnet on the LAN interfaces.
Installing an Encryption Key in order to use encryption with a configuration file.
•
10-1
52-80420-00 A0
Page 62
CONFIGURING SECURITY VIA THE WEB
10.1 Default Security Configuration
Table 10-1: Default Security Configuration
Parameter Default Value
Password None
Advanced security Disabled
DHCP security Disabled
HTTP access on the LAN interfaces Enabled
Telnet access on the LAN interfaces Enabled
10.2 Setting the Password
You can use a security password to prevent access of configuration of the Gateway unit by
unauthorized users via the Telnet/Console or the Web Configuration pages.
To set a password:
1. In the vertical menu bar of the current Gateway Web page, select
The Set Security Password page appears (Figure 10-1).
Security
.
Figure 10-1 Set Security Password Page
10-2
52-80420-00 A0
Page 63
CONFIGURING SECURITY VIA THE WEB
2. Enter the new password and confirm it.
3. Click on Save Password to effect the change.
You can use Advanced Security to select secured IP and/or port.
10.3 Configuring Advanced Security
You can use Advanced Security to select secured IP and/or port.
To configure Advanced Security:
1. In the horizontal menu bar of the Set Security Password page, select Advanced Security.
The Advanced Security Configuration page appears (Figure 10-2).
The following options and entries are available in this window:
Advanced Security Enable
DHCP Security enable Select this option to enable the Gateway, when in DHCP
IP Address
Select this option to enable Advanced Security.
mode, to receive an IP address and other configuration
parameters from a DHCP server only if it is listed in the IP
address list.
Optionally, list the IP addresses of stations that are permitted
to manage the Gateway.
10-3
52-80420-00 A0
Page 64
CONFIGURING SECURITY VIA THE WEB
Figure 10-2 Advanced Security Configuration Page
NOTE To permit management of the Gateway only to specified stations, you must
enter the IP address for each station allowed.
If no stations are specified by IP address, all stations are permitted to manage
the Gateway.
2. After selecting the desired options and entering the desired values, click on
Save Settings
to effect the configuration.
10.4 Setting a Password for the CLI
(only for units with AUX/Console port)
To set a password for the CLI:
1. In the horizontal menu bar of the Set Security Password page, select CLI.
The
Set CLI Password
page appears (Figure 10-3).
10-4
52-80420-00 A0
Page 65
CONFIGURING SECURITY VIA THE WEB
Figure 10-3 Set CLI Password Configuration Page
2. After entering and confirming the desired CLI password, click on Save Password to
effect the configuration. Using a password will disable and hide all CLI activity until
password is entered.
10.5 Enabling/disabling Configuration via Telnet
To enable/disable Telnet configuration:
1. In the horizontal menu bar of the Set Security Password page, select
The Telnet Configuration page appears (Figure 10-4).
2. If required, select or clear the Telnet Enable checkbox, and click on Save Telnet
Settings
to effect the change.
Telnet
.
10-5
52-80420-00 A0
Page 66
CONFIGURING SECURITY VIA THE WEB
Figure 10-4 Telnet Configuration Page
10.6 Installing an Encryption Key
In order to use encryption with a configuration file (see section 6.5 : Creating and Encrypting
Configuration Files) the user needs to define an encryption key.
To install a new encryption key:
1. In the horizontal menu bar of the Set Security Password page, select Encryption.
The Set Encryption Key page appears (Figure 10-5).
Figure 10-5 Set Encryption Key Page
2. Enter and confirm the new key in the appropriate fields, and click on Save Key to effect
the change.
10-6
52-80420-00 A0
Page 67
CONFIGURING SECURITY VIA THE WEB
10.7 Installing a General Configuration File Encryption Key
In order to use encryption with the general configuration file, the user needs to define an
encryption key (see Creating and Encrypting a Configuration File
to 64 characters will be used to decrypt the General configuration file. By default the field is
empty and configuration files are assumed to be not encrypted.
To install a new general configuration file encryption key:
1. In the horizontal menu bar of the Security page, select EncGeneral. The Set General
Configuration File Encryption Key page appears (Figure 10-6).
). An encryption key with up
Figure 10-6: Set General Configuration File Encryption Key Page
2. Enter and confirm the new key in the appropriate fields.
3. Click on Save Key to effect the change.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
10-7
52-80420-00 A0
Page 68
11 Miscellaneous Configuration
via Web
In the Miscellaneous Web configuration page you can set the following:
The NTP (Network Time Protocol) IP address for obtaining the correct time.
•
• The local time zone, relative to GMT.
• Automatic adjustment of the internal clock to daylight saving time according to the local
time zone.
• Local country caller ID.
• Syslog server IP address and log-messages severity level.
HTTP and Telnet server ports, and Syslog, TFTP and HTTP client ports.
•
• Advanced calling features (available only in SIP).
• Ring tone names and cadences.
Default Miscellaneous Configuration
Table 11-1: Default Miscellaneous Configuration
Parameter Default Value
Time Zone GMT-8:00 Pacific Time
Adjust clock for daylight savings Disabled
Country CID United States
HTTP Server Port 80
Telnet Server Port 23
Syslog Client Port 514
TFTP client port 69
11-1
52-80420-00 A0
Page 69
MISCELLANEOUS CONFIGURATION VIA WEB
Parameter Default Value
HTTP client port 80
Call Waiting Enabled (configurable only in SIP)
Caller ID display Enabled (configurable only in SIP)
3-way calling Enabled (configurable only in SIP)
Last call redial Enabled (available only in SIP)
Distinctive ring tones Enabled (available only in SIP)
Call transfer Enabled (configurable only in SIP)
Do Not Disturb (DND) Enabled (available only in SIP)
Call forwarding Enabled (configurable only in SIP)
Block/accept last call Enabled (available only in SIP)
Show Caller Identity on Call Waiting Enabled (configurable only in SIP)
Auto redial Expire Timer value 1800 seconds
Conditional forward key pattern *1 (available only in SIP)
Unconditional forward key pattern *2 (configurable only SIP)
Disable forward key pattern *3 (configurable only SIP)
Enable DND key pattern *4 (available only in SIP)
Disable DND key pattern *5 (available only in SIP)
Blind Transfer key pattern *98 (available only in SIP)
Redial last call key pattern *69 (available only in SIP)
Block last call key pattern *60 (available only in SIP)
Accept last call key pattern *80 (available only in SIP)
Auto redial *66 (available only in SIP)
11-2
52-80420-00 A0
Page 70
MISCELLANEOUS CONFIGURATION VIA WEB
Parameter Default Value
Disable auto redial *86 (available only in SIP)
Ring Cadences Table 11-2 (available only in SIP)
11-3
52-80420-00 A0
Page 71
MISCELLANEOUS CONFIGURATION VIA WEB
Table 11-2: The Default Ring Cadences with Their Associated Names
Ring Number Ring Cadence Alert-Info Ring Name
1 ON 2000 ms
OFF 4000 ms
2 ON 800 ms
OFF 400 ms
ON 800 ms
OFF 4000 ms
3 ON 400 ms
OFF 200 ms
ON 400 ms
OFF 200 ms
ON 800 ms
OFF 4000 ms
4 ON 300 ms
OFF 200 ms
ON 1000 ms
OFF 200 ms
ON 300 ms
OFF 4000 ms
Bellcore-dr1
Bellcore-dr2
Bellcore-dr3
Bellcore-dr4
5 ON 500 ms
OFF 20 ms
6 ON 2000 ms
OFF 4000 ms
7 ON 2000 ms
OFF 4000 ms
8 ON 2000 ms
OFF 4000 ms
11-4
Bellcore-dr5
Bellcore-dr6
Bellcore-dr7
Bellcore-dr8
52-80420-00 A0
Page 72
MISCELLANEOUS CONFIGURATION VIA WEB
Clock Localization
To configure the clock to local time:
In the vertical menu bar of the current Gateway Web page, select Miscellaneous. The Clock
page appears.
Figure 11-1 Clock Localization Page
Table 11-3 lists the options and entries in the clock localization page.
Table 11-3: The Available Clock Localization Configuration Fields
Field Name Description
NTP Server
Time Zone
Adjust clock for daylight
savings
The IP address of the NTP server. For more information
regarding the NTP protocol, see Understanding NTP
Local time zone, relative to GMT. The default is 480 minutes.
Automatically adjusts the internal clock to daylight saving
time according to the local time zone. For more information
regarding the NTP protocol, see Daylight Saving Time
(Summer Time)
.
Click
Save Settings
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
to save the configuration changes.
.
11-5
52-80420-00 A0
Page 73
MISCELLANEOUS CONFIGURATION VIA WEB
Caller ID
To select the local country for local CID support:
In the vertical menu bar of the current Gateway Web page, select Miscellaneous.
1.
In the horizontal menu bar, select CID. The Caller ID page appears (Figure 11-2).
2.
3. Select the local country in the drop-down list-box.
By default, the Country Caller ID is
4. Click Save Settings.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
United States
.
Syslog Server Configuration
For more information on the logging facility, see Section Clock Localization.
Understanding Syslog.
To set the Syslog server IP address and the log message severity level:
In the vertical menu bar of the current Gateway Web page, select Miscellaneous.
1.
Figure 11-2: Caller ID Configuration Page
11-6
52-80420-00 A0
Page 74
MISCELLANEOUS CONFIGURATION VIA WEB
In the horizontal menu bar, select Syslog. The Syslog Daemon Address
2.
Configuration page appears (Figure 11-3).
Figure 11-3: Syslog Daemon Address Configuration Page
3. Set the IP address of the Syslog server in the Syslog Server IP Address field (in
the A.B.C.D format).
Set the log messages severity level in the Message severity level drop-down list-
4.
box.
The severity is inversely related to the specified level (0 represents highest
severity, 7 represents lowest severity). When you specify a severity level, logging
output of the specified level and all lower levels (higher severities) are enabled.
The severity levels of the log message types are listed in Table 4-1.
5. Click Save Settings.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
Port Protocol Configuration
The user can configure the TCP\UDP ports used by the management protocols for the Web
HTTP server, Telnet server, Syslog client, TFTP client and HTTP client. Following is an
example where the TCP port used by the Web management will need to be configured.
Default TCP port 80 is used by HTTP for Web management. If an HTTP server using
TCP port 80 is placed in the LAN, users will need to change the management TCP
port.
To change the protocols’ ports:
11-7
52-80420-00 A0
Page 75
MISCELLANEOUS CONFIGURATION VIA WEB
In the vertical menu bar of the current Gateway Web page, select Miscellaneous.
1.
In the horizontal menu bar, select
2.
appears (Figure 11-4).
ProtocolPorts
. The Ports configuration page
Figure 11-4: The Ports Protocol Configuration Page
3. Set the HTTP server port in the range <1-65535> in the HTTP Server Port field.
4. Set the Telnet server port in the range <1-65535> in the Telnet Server Port field.
5. Set the Syslog client port in the range <1-65535> in the Syslog Client Port field.
6. Set the TFTP client port in the range <1-65535> in the HTTP/TFTP Client Port
field.
7. Set the HTTP client port in the range <1-65535> in the HTTP/TFTP Client Port
field.
8. Click Save Settings.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
11-8
52-80420-00 A0
Page 76
MISCELLANEOUS CONFIGURATION VIA WEB
SIP Advanced Calling Features and Key Sequence
Configuration
In SIP, all Advanced Calling features can be either enabled or disabled. By default, all Advanced
Calling features are enabled. The assigned key sequences for using the Asterisk (*) calling features
can be configured also from the Miscellaneous-Calling web screen.
To set the Advanced Calling Features and Key Sequence Configuration:
In the vertical menu bar of the current Gateway Web page, select Miscellaneous.
1.
In the horizontal menu bar, select Calling. The top part of the Advanced Calling
2.
Features page appears (Figure 11-5).
3. Table 11-4 lists the available fields for enabling/disabling advanced calling
features.
Figure 11-5: The Advanced Calling Features Page
11-9
52-80420-00 A0
Page 77
MISCELLANEOUS CONFIGURATION VIA WEB
Table 11-4: The Available Advanced Calling Features Configuration Fields
Field Name Description
Enable Call Waiting
Enable Caller ID display Enables/disables the feature to view the CID of received
Enable 3-way calling
Enable last call redial Enables/disables Redialing Last Call feature. See Redialing of
Enable distinctive
ringtones
Enable call transfer Enables/disables Blind Transfer Call (see Blind Transfer Call
Enable Do Not Disturb
(DND)
Enable call forwarding
Enable block/accept last
call
Enable auto redial Enables/disables redialing a busy number. See Auto Redial
Show Caller identity on
Call Waiting
Auto redial Expire Timer
value
Enables/disables Call Waiting feature. See Call Waiting
description.
Calls.
Enables/disables Conference feature. See Conference Call
for description.
Last Received Call for description.
Enables/disables Distinctive Ring tones feature. See Ring
Tones Configuration.
When a call is received a Blind Transfer Call can done by
dialing *98 (default key sequence) and then the destination
number. Once the transfer sequence is dialed the call is
immediately disconnected and the caller will automatically try
to create a new call with the destination number.
Enables/disables DND feature. See Do Not Disturb (DND)
description.
Enables/disables Call Forwarding feature. See Forward a call
and Conditional Call Forwarding
Enables/disables Block/Accept Last Call feature. See Block
Last Received Call for description.
Enables seeing the name of the Caller on the call waiting.
The time period in seconds for dialing a busy number. The
default is 1800 seconds.
for description.
for
).
for
4. After making your selections, scroll down to the bottom of the page for the key-
sequences used to activate/deactivate advanced calling features. The
Advanced Configuration part at the bottom of the page (Figure 11-6) contains the
Key Sequences settings.
11-10
Handset
52-80420-00 A0
Page 78
MISCELLANEOUS CONFIGURATION VIA WEB
Figure 11-6: The Assigned Key Sequences Fields
5. Table 11-5 lists the available fields in this part of the page.
Complete your desired settings and click Save Settings.
6.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
11-11
52-80420-00 A0
Page 79
MISCELLANEOUS CONFIGURATION VIA WEB
Table 11-5: The Available Key Sequences Fields
Field Name Description
Conditional forward
Unconditional forward Activate Unconditional call forward key sequence. See
Disable forward
Enable DND Activate DND key sequence. See Do Not Disturb (DND)
Disable DND
Transfer Activate Blind Transfer Call key sequence. See Blind Transfer
Redial last call
Block last call Block last received call key sequence. See Block Last
Accept last call
Auto redial
Disable auto redial
Activate Conditional call forward key sequence. See
Conditional Call Forwarding
Forward a call
Deactivate Call forward key sequence. See Conditional Call
Forwarding
description.
Deactivate DND key sequence. See Do Not Disturb (DND)
Call.
Redial last received call key sequence. See Redialing of Last
Received Call for description.
Received Call for description.
Reaccept last blocked number key sequence. See Block Last
Received Call
Activate Auto Redial by hanging up. See Auto Redial
To cancel the periodic Auto Redialing before the timeout has
been reached. See Auto Redial
for description.
.
.
for description.
for
.
.
.
Ring Tones Configuration
Setting the distinctive rings and distinctive call waiting tones enables the called party to identify the
caller based on Distinctive Rings and Call Waiting Tones. The feature is dependent on the remote
caller or the SIP server for including the Alert-Info header with the appropriate Ring Name in the
INVITE message for the Distinctive Ring or Call Waiting Tone.
Eight Ring Cadences (patterns) with 8 Ring Names used by both telephone lines can be configured
for the Distinctive Rings and 6 Ring Cadences (with the same Ring Names as for the Distinctive
rings) are used for the Call Waiting Tones. The default values for the Ring Cadences and their Ring
Names are based on the 5 Bellcore GR-506-CORE ring patterns. If the Ring Name in Alert-Info
header is not recognized or is not supplied, the standard Bellcore Ring pattern 1 is always used and
cannot be changed to another pattern. The default Alert-Info Ring names can be configured to
different names but the default names will also be recognized.
Table 11-2
the Distinctive Rings and 6 defaults - by the Call Waiting Tones. The default values are used when
the tables are left blank.
To set the Ring Tones:
1.
lists the default Ring Cadences with their associated names. Eight defaults are used by
In the vertical menu bar of the current Gateway Web page, select Miscellaneous.
11-12
52-80420-00 A0
Page 80
MISCELLANEOUS CONFIGURATION VIA WEB
In the horizontal menu bar, select Ring tones. The Ringing Configuration page,
2.
comprising three sets of fields, appears (Figure 11-7, Figure 11-8 and Figure
11-9).
Figure 11-7: The Ring Name Fields in the Ringing Configuration Page
Figure 11-8: The Ring Cadence Fields in the Ringing Configuration Page
11-13
52-80420-00 A0
Page 81
MISCELLANEOUS CONFIGURATION VIA WEB
Figure 11-9: The Call Wait Tone Cadence Fields in the Ringing Configuration Page
3. Set the Alert-Info ring name in the Ring Name 1 to Ring Name 8 fields.
Option to identify the caller based on a distinct ring. Ring Names are used for
Distinctive Rings and Call Waiting tones. The names are sent in the Alert-Info
header of the INVITE message to indicate the ring that should be played.
4. Set the Distinctive Ring cadences in the Ring Cadence 1 to Ring Cadence 8 fields.
Distinctive Rings Cadences (patterns) associated with the Ring Names. The
parameter can be: ON, OFF, IDLE, R-repeat, time in milliseconds.
Example:
RING_2=ON(200),OFF(300),ON(100),OFF(400),ON(200),IDLE(4000),R
5. Set the Call Waiting Ring Tones in the CWT Cadence 1 to CWT Cadence 6 fields.
Call Waiting tone Cadences (patterns) associated with the Ring Names.
6. Click Save Settings.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
11-14
52-80420-00 A0
Page 82
12 Protocol H.323 Configuration
via the Web
H.323 is a standard approved by the International Telecommunication Union (ITU) to
promote compatibility in videoconference transmissions over IP networks. H.323 was
originally promoted as a way to provide consistency in audio, video and data packet
transmissions in the event that a Local Area Network (LAN) did not provide Guaranteed
Service Quality (QoS).
If the Gateway has H.323 installed you need to configure the Gatekeeper IP address and other
H.323 parameters with the Web Configuration. To run the Web Configuration see
Configuring the Gateway via the Web
12.1 Default H.323 Configuration
.
Table 12-1: Default H.323 Configuration
Parameter Default Value
Dial plan >#|[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|x.T
Caller ID FSK
RRQ for KeepAlive RRQ Disabled
T38 fax support Disabled
Send In-band DTMF Enabled
Send Out-of-band DTMF Enabled
Audio/CODEC standard G711 u-law and a-law
Packetization period 30 ms
Silence Suppression Enabled
Fixed Jitter Buffer 100ms
12-1
52-80420-00 A0
Page 83
PROTOCOL H.323 CONFIGURATION VIA THE WEB
12.2 Setting the H.323 Configuration
To configure the Gatekeeper IP address and other H.323 parameters:
• In the vertical menu bar of the current Gateway Web page, select H323. The H323
Configuration
page (Figure 12-1) appears.
Figure 12-1: H.323 Configuration Page
H323 Gatekeeper Settings
•
Choose whether or not to use GRQ (Gatekeeper Request) for gatekeeper (GK)
o
address.
The GRQ is a Registration, Admission, and Status (RAS) message sent as a
gatekeeper request.
o Enter the IP address of your gatekeeper in the first field and the phone numbers for
Line1
and
at the bottom of the page. All other fields on this page have default
Line2
values and need not to be filled in.
At this point, you can click on Save H323 Settings at the bottom of the page and use
the default Dial Plan. Alternatively, you may enter a user-defined dial plan in the Dial
Plan field.
Set the alternate IP address of H.323 gatekeeper. If you want the alternate IP address
o
of H.323 gatekeeper to be used, select the Enable Alternate Gatekeeper support
check box.
12-2
52-80420-00 A0
Page 84
PROTOCOL H.323 CONFIGURATION VIA THE WEB
• Gateway Settings
o Setting the Dial Plan
o Use the default dial plan (>#|[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|x.T) or set your own
dial plan. For more information regarding the dial plan format see Dial Plan for SIP
and H.323.
o For each phone line set the following:
Set the phone number (with E164 alias).
∇
The E164 is the format of global switched telephone numbers are defined by the
ITU-T (International Telecommunications Union - Telecommunications
Standardization Sector). The 16-digit number is split into international, national
and user number portions.
Set the caller ID.
∇
Enter the “Name” you want to show on the called party’s Caller ID display. When
you make a call from a line of the Gateway with the Caller ID inserted, the remote
called party will receive this string. Gateway US version is factory set to FSK
(Bellcore) CID.
Set the H.323 alias.
∇
The H.323 Alias is usually descriptive of the particular client terminal and usually
contains alphanumeric characters.
∇ Select the Enable Full RRQ for KeepAlive RRQ check box to enable the RRQ.
The RRQ is a RAS (Registration, Admission, and Status protocol) message sent
as a registration request.
∇ Select the Enable T38 Fax Support check box to enable T38 fax support.
The T38 is a Real time IP Fax Relay protocol.
• Click on the Save H323 Settings button to save the changes.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
12.3 DTMF Signaling
Dual Tone Multi-Frequency (DTMF) identifies telephone buttons by a combination of two
tones. When you press a button, two standard tones are sent. One tone uniquely indicates
the row number and the other tone uniquely indicates the column number of the button that
you press.
12-3
52-80420-00 A0
Page 85
PROTOCOL H.323 CONFIGURATION VIA THE WEB
To configure DTMF Signaling:
In the horizontal menu bar of the H323 Configuration Web page, select
The DTMF Configuration page appears (Figure 12-2).
Figure 12-2: DTMF Configuration Page
Table 12-2 lists the available fields in the DTMF configuration page:
DTMF Signaling
.
12-4
52-80420-00 A0
Page 86
PROTOCOL H.323 CONFIGURATION VIA THE WEB
Table 12-2: The Available Voice and Management Services Configuration
Fields
Field Name Description
Send In-band
DTMF
Send Out-of-band
DTMF
Supports signaling tones within the audio channel.
Supports signaling tones outside the audio channel. This requires
choosing one of the following options:
•
Q931 Info Message
The Q.931 protocol contains control information that is
exchanged with telephone networks. The information includes
digital code for the following messages:
ALERTING, CALL PROCEEDING, CONNECT, CONNECT
ACKNOWLEDGE, SETUP, SETUP ACKNOWLEDGE,
SUSPEND, SUSPEND ACKNOWLEDGE, SUSPEND REJECT,
RESUME, RESUME ACKNOWLEDGE, RESUME REJECT,
DISCONNECT, RELEASE, RELEASE COMPLETE, STATUS
ENQUIRY and STATUS.
•
H245 User Input
Enables forwarding H.245 user input indication messages.
• RFC-2833 Signaling
Enables the RFC2833 protocol for transmission of Telephony
event packets.
Click Save DTMF Settings at the bottom of the Web page to effect the changes.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
12.4 Audio/CODEC Configuration
The Gateway supports G711 u-law and a-law standards by default. The user can set the
Gateway to also support one of the three voice coding standards: G723, G726 or G729.
Both ports will be allowed to use the selected option. For every supported voice coding
standard the user can enable/disable Silence Suppression and, except for G723, select the
default Packetization period (as a multiple of 10ms in the range 10ms-100ms).
To set Audio/CODEC parameters:
1. In the vertical menu bar of the current Gateway Web page, select CODECS. The
Audio/CODEC Configuration page appears (Figure 12-3).
12-5
52-80420-00 A0
Page 87
PROTOCOL H.323 CONFIGURATION VIA THE WEB
Figure 12-3: Audio/CODEC Configuration Page
2. Select the Audio/CODEC standard.
NOTE
Only one complex code (G723, G726, G729) can be selected.
3. Set the Packetization period.
4. Set the Silence Suppression.
5. Set the Fixed Jitter Buffer which is the fixed playout delay in milliseconds.
6. Click Save CODEC Configuration at the bottom of the Web page to effect the
changes.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
12-6
52-80420-00 A0
Page 88
13 Protocol MGCP Configuration
via Web
The MGCP (Media Gateway Control Protocols) is designed to control Telephony Gateways
from external call control elements called media gateway controllers or call agents. A
telephony gateway is a network element that provides conversion between the audio signals
carried on telephone circuits and data packets carried over the Internet or over other packet
networks
If the Gateway has MGCP installed you need to configure the Call Agent IP address and
other MGCP parameters with the Web Configuration. To run the Web Configuration, see
Configuring the Gateway via the Web
13.1 Default MGCP Configuration
.
Table 13-1: Default MGCP Configuration
Parameter Default Value
Call Agent Address Obtained from a DNS server
Call Agent port 2427
Endpoint domain name Gateway’s IP address
Max. delay before RSIP 600 seconds
Max. disconnect delay before RSIP 0, the feature is disabled
Allocated Endpoints Number of telephone connectors (2)
Support PacketCable NCS 1.0 Enabled
Support IETF MGCP 1.0 (RFC 2705) Disabled
Support Message Piggybacking Enabled
Send Telephone Events via RFC2833
signaling
Disabled
Payload value 96
13-1
52-80420-00 A0
Page 89
PROTOCOL MGCP CONFIGURATION VIA WEB
Parameter Default Value
Suppress voice packets during RFC2833
Telephone Event packet transmission
Squelch inband DTMF audio Disabled
ABCD event signaling mode Transition
Audio/CODEC standard G711 u-law and a-law
Disabled
13.2 Setting the MGCP Configuration
To configure MGCP parameters:
In the vertical menu bar of the current Gateway Web page, select
Configuration page (Figure 13-1) appears.
MGCP
. The
MGCP
Table 13-2 lists the available fields in the MGCP configuration page.
Figure 13-1: MGCP Configuration Page
13-2
52-80420-00 A0
Page 90
PROTOCOL MGCP CONFIGURATION VIA WEB
Table 13-2: The Available MGCP Configuration Fields
Field Name Description
Call Agent Address
Call Agent port
AccessLinX VoIP Gateway
Domain Name
Max. delay before RSIP Maximum time in seconds allowed for the Restart In
Max. disconnect delay before
RSIP
Allocated Endpoints
Support PacketCable NCS 1.0 Enable/disable Packet Cable NCS 1.0 support.
Support IETF MGCP 1.0
(RFC 2705)
Support Message Piggybacking When this option is enabled, the Gateway is
Fill in the address of the Call Agent in this field
Or
Leave this field blank if you wish to obtain the Call
Agent address from a DNS server.
The address of the call agent can be IP address or
FQDN address.
FQDN (Fully-Qualified Domain Name) is a portion of
an Internet Uniform Resource Locator (URL) that fully
identifies the server program that an Internet request
is addressed to. The FQDN includes the second-level
domain name and any other levels.
Enter the Call Agent port number in this field
Or
Leave this field blank if you wish to use the default
MGCP Call Agent port 2427.
Enter the Endpoint Domain name in this field
Or
Leave this field blank if Gateway’s IP address is to be
used for the Domain Name.
Progress message to be sent to the Call agent.
The default value is 600 seconds.
If this parameter is not zero, MGCP RSIP will be sent
when the link on the Uplink port goes up after being
down for a period longer than Max. disconnect
delay before RSIP
By default the parameter is zero and the feature is
disabled.
Number of allocated Endpoints. Number of phone
lines permitted to register with Call Agent.
Minimum=1. Maximum=Number of telephone
connectors.
Enable/disable MGCP 1.0 support.
permitted to send Piggyback messages (several
MGCP messages sent in one UDP frame) to the Call
agent.
.
Enter your settings and click Save MGCP Settings to effect the changes.
13-3
52-80420-00 A0
Page 91
PROTOCOL MGCP CONFIGURATION VIA WEB
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
13.3 RTP Telephone Event (RFC2833) Configuration
RFC2833 describes a protocol for sending Telephony events (Receiver ON/OFF Hook, Ring
ON/OFF) and DTMF digits in RTP packets. This method is used as an alternative method for
the MGCP protocol signaling frames to solve a variety of signaling delays. The Payload value
is Payload Type field of the RTP frame. Payloads 0-95 are well defined and reserved values by
IANA. Payloads values of 96-127 are free (dynamic) and are not reserved by the standards.
If the RFC2833 protocol for Telephony events is enabled, voice packets can be suppressed
during the transmission of the RFC2833 Telephone Event packets.
To configure RTP Telephone Event (RFC2833) parameters:
In the horizontal menu bar of the MGCP Configuration page, select
OOB Signaling
RTP Telephone Event (RFC2833) Configuration page (Figure 13-2) appears.
. The
Figure 13-2: RTP Telephone Event (RFC2833) Configuration Page
Table 13-3 lists the available fields in the RTP Telephone Event (RFC2833) Configuration
page.
13-4
52-80420-00 A0
Page 92
PROTOCOL MGCP CONFIGURATION VIA WEB
Table 13-3: The Available RTP Telephone Event (RFC2833) Configuration
Fields
Field Name Description
Send Telephone Events via
RFC2833 signaling using
payload value
Suppress voice packets during
RFC2833 Telephone Event
packet transmission
Squelch inband DTMF audio When selected inband DTMF audio is not transmitted
ABCD event signaling mode
When enabled, the Gateway will send RFC2833
frames only for the Telephony events. RFC2833
frames for the DTMF digits are not supported.
Consult your Call server documentation to know if
this RFC2833 option is supported and what Payload
value is required.
The default payload value is 96.
Enabling this option preserves the original voice
bandwidth and prevents the need for more bandwidth
for the RFC2833 packets. Consult your Call server
documentation for the preferred mode of operation.
in the audio stream.
Two possible modes for RFC2833 Telephony events
signaling (ABCD signaling packets) are available:
•
Transition mode: In this mode, the event packet
is sent only at the moment of the event.
• Continuous mode: In this mode, the event
packet is sent continuously at the rate of the
voice, as long as the event exists.
The Continuous mode behaves better in situations of
packet loss, preventing cases such as stuck ringers.
Consult your Call server documentation for the
preferred mode of operation.
Enter your settings and click Save RFC2833 Settings to effect the changes.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
13.4 Audio/CODEC Configuration
The Gateway supports G711 u-law and a-law standards by default. The user can set the
Gateway to also support one of the three voice coding standards: G723, G726 or G729. Up to
two ports will be allowed to use the selected option. The remaining ports (if any) will support
G711 u-law and a-law.
To set Audio/CODEC parameters:
1. In the vertical menu bar of the current Gateway Web page, select CODECS. The
Audio/CODEC Configuration page appears (Figure 13-3).
13-5
52-80420-00 A0
Page 93
PROTOCOL MGCP CONFIGURATION VIA WEB
Figure 13-3: Audio/CODEC Configuration Page
2. Select the Audio/CODEC standard.
3. Set the Fixed Jitter Buffer which is the fixed playout delay in milliseconds.
4. Click Save CODEC Configuration at the bottom of the Web page to effect the changes.
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
13-6
52-80420-00 A0
Page 94
14 Protocol SIP Configuration via
Web
The SIP (Session Initiation Protocol) is an Internet Engineering Task Force (IETF) standard
protocol for initiating an interactive user session that involves multimedia elements such as
video, voice, chat, gaming, and virtual reality.
If the Gateway has SIP (Session Initiation Protocol) installed you must configure the SIP
Server IP address and other SIP parameters with the Web Configuration. To run the Web
Configuration, see Configuring the Gateway via the Web
14.1 Default SIP Configuration
.
Table 14-1: Default SIP Configuration
Parameter Default Value
SIP server IP address Empty
SIP server port number 5060
Dial plan >#|[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|x.T
RTP/RTPC NAT port base 16384
INVITE Expires Timer value Disabled
SIP Session Timer value Disabled
Support PRACK method with
provisional response reliability
SIP Registration Timer Value 1800 seconds
Disabled
Send RTP on 183 Session Progress Disabled
Send Telephone Events via RFC2833
signaling using payload value
96
14-1
52-80420-00 A0
Page 95
PROTOCOL SIP CONFIGURATION VIA WEB
Parameter Default Value
Suppress voice packets during
RFC2833 Telephone Event packet
transmission
Call Forward Disabled
Audio/CODEC standard G711 u-law and a-law
SIP call control transport protocol UDP
Jitter Buffer 100 ms
Disabled
14.2 SIP Server configuration
To configure the SIP Protocol parameters:
• In the vertical menu bar of the current Gateway Web page, select SIP.
The SIP Configuration page (Figure 14-1) appears. You may need to scroll down in
order to display the fields at the bottom of this page.
14-2
52-80420-00 A0
Page 96
PROTOCOL SIP CONFIGURATION VIA WEB
Figure 14-1: SIP Configuration Page
•
SIP Server Settings
o SIP server IP address or Domain Name.
If this field is set to a Domain name and the SIP Server port is empty, the SIP server
information will be obtained by a DNS SRV query. If the DNS SRV query fails the DNS A
queries and the default SIP port 5060 will be used.
If this field is set to a Domain name and the SIP Server port is not empty DNS A queries with
Server port will be used.
If the field is set to the Server’s IP and Server port is configured, Server’s IP and configured
port will be used. If port is not configured the default port 5060 will be used.
o Set SIP server Port number (5060 by default).
o SIP Server’s Domain name which is used in registration. For more information
regarding the DNS (Domain Name Server) of the SIP server, see DNS Resolver
.
For example: LINExNUMBER@DOMAINNAME
o Select the Send Registration Request check box if you want the Gateway to send
REGISTER request.
14-3
52-80420-00 A0
Page 97
PROTOCOL SIP CONFIGURATION VIA WEB
• SRV DNS Support for SIP
SRV (abbreviated from SERVICE) is a request to DNS server for receiving IP addresses of
servers that distribute some kind of service. The type of DNS queries used depends on the
way the SIP Server IP and port are configured. The following describes the possible
options:
A Domain name is set for the SIP Server’s IP address.
o
∇ If the Port is set the gateway will use DNS A type queries.
∇ If the Port is not set the gateway will use DNS SRV queries. If the query is
unsuccessful DNS A type queries will be performed and the default SIP port 5060
is used.
An IP address is set for the SIP Server’s IP.
o
∇ If the port is set the configured IP address and the configured port are used.
∇ If the port is not set the Configured IP address and the default SIP port 5060 are
used.
• Gateway Settings
Setting the Dial Plan
o
Use the default dial plan (>#|[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|x.T) or set your own dial plan
in the Dial Plan field. For more information regarding the dial plan format see Dial Plan for
SIP and H.323.
o Set the SIP call control transport protocol.
For each phone line set the following:
o
∇ Set the phone number (E164 number).
The E164 is the format of global switched telephone numbers are defined by the ITU-T
(International Telecommunications Union - Telecommunications Standardization Sector). The
16-digit number is split into international, national and user number portions.
Set the caller ID.
∇
Enter the “Name” you want to show on the called party’s Caller ID display. When you make a
call from a line of the Gateway with the Caller ID inserted, the remote called party will receive
this string. Gateway US version is factory set to FSK (Bellcore) CID.
∇ Set the SIP call-signaling port.
Choose whether or not AEC is on.
∇
The AEC (Automatic Echo Cancellation) reduces the amount of feedback the called party
hears when the calling party is using a speakerphone.
Set the Authentication user name and password
∇
• NAT Settings
o Set the NAT IP Address to be used for SIP.
14-4
52-80420-00 A0
Page 98
PROTOCOL SIP CONFIGURATION VIA WEB
If the IP address is not set, the NAT option is disabled. For more information regarding the
NAT protocol see Understanding NAT and NAPT
o Set the RTP (Real-time Transport Protocol)/RTPC port base.
• STUN Server Settings
.
The STUN (Simple Traversal of UDP through NATs) server is an implementation of the
STUN protocol that enables STUN functionality in SIP-based systems. STUN is an
application-layer protocol that can determine the public IP and nature of a NAT device that
sits between the STUN client and STUN server.
Set the STUN server IP address.
o
o Set the STUN server port.
Set the values for SIP Server Settings, Nat Settings and STUN Server Settings according to
the way the Gateway is connected to the network:
If the Gateway does not reside behind a NAT server and has an outbound (global) IP
•
address, you only need to set the SIP Server’s IP address, Port and Domain Name fields.
If the Gateway resides behind a NAT server and wishes to communicate with the SIP
•
server via a Proxy server:
•
Set the
SIP server IP address
and
fields to the values of the Proxy server’s IP
Port
address and port.
Set the Domain Name to the SIP Server’s Domain name.
•
If the Gateway resides behind a NAT server and wishes to communicate with the SIP
•
server using STUN support:
Set the SIP server’s IP address, Port and Domain Name fields to the values of the
•
SIP server’s IP address, port and Domain Name.
Set the STUN Server’s IP address and Port fields to the IP and port of the STUN
•
server.
If the Gateway resides behind a NAT server and the outbound (global) IP is Static, the
•
Gateway could be configured to use the outbound (global) IP also for the SIP protocol.
Set the SIP server’s
•
SIP server’s IP address, port and Domain Name.
Set the NAT IP address field to the value of the Gateway’s outbound IP address.
•
Click the Save SIP Settings to save the SIP configuration.
•
NOTE
After entering and saving all configurations, you MUST reset the Gateway.
IP address, Port
and
Domain Name
14-5
fields to the values of the
52-80420-00 A0
Page 99
PROTOCOL SIP CONFIGURATION VIA WEB
14.3 SIP Extensions
To configure SIP Extensions:
• In the horizontal menu bar of the SIP page, select SIP Extensions. The SIP Extensions
configuration page (Figure 14-2) appears.
Figure 14-2: SIP Extensions Page
Table 14-2 lists the available fields in the SIP Configuration page.
Table 14-2: The Available SIP Extensions Fields
Field Name Description
Support PRACK method with
provisional response
reliability
Provides a standard reliability mechanism for provisional
responses, which means that the Gateway is sending
ACKs for provisional responses (180, 183, etc).
Reference: RFC3262 Reliability of Provisional Responses
in the Session Initiation Protocol (SIP).
14-6
52-80420-00 A0
Page 100
PROTOCOL SIP CONFIGURATION VIA WEB
Field Name Description
Encode SIP URI with user
parameter
INVITE Expires Timer value
The set of valid telephone-subscriber strings is a subset of
valid user strings. The user URI parameter exists to
distinguish telephone numbers from user names that
happen to look like telephone numbers. If the user string
contains a telephone number formatted as a telephonesubscriber, the user parameter value “phone” SHOULD be
present. Even without this parameter, recipients of SIP
and SIPS URIs MAY interpret the pre-@ part as a
telephone number if local restrictions on the name space
for user name allow it.
Reference: RFC3261, Section 19.1.1: SIP and SIPS URI
Components.
Example: from: <77540@192.168.0.40;user=phone>
Defines the length of time we allow for an OK response to
an INVITE. If the time elapses – we transmit a CANCEL to
invalidate the INVITE.
There is no default value - this option is not used if no
value is specified.
Reference: RFC3261, Section 13.2.1 Creating the Initial
INVITE.
“The User Agent Client (UAC) MAY add an Expires
header field (Section 20.19) to limit the validity of the
invitation. If the time indicated in the Expires header field
is reached and no final answer for the INVITE has been
received, the UAC core SHOULD generate a CANCEL
request for the INVITE, as per Section 9”.
SIP Session Timer value
Specifies the Session-Expires header in an INVITE
request. Used as the SIP session’s keep-alive
mechanism.
There is no default value - this option is not used if no
value is specified.
Draft-ietf-sip-session-timer-10.txt of the Internet
Engineering Task Force is currently supported:
“This document defines an extension to the Session
Initiation Protocol (SIP). This extension allows for a
periodic refresh of SIP sessions through a re-INVITE or
UPDATE request. The refresh allows both user agents
and proxies to determine if the SIP session is still active”.
The extension defines two new header fields, SessionExpires, which conveys the lifetime of the session, and
Min-SE, which conveys the minimum allowed value for the
session timer.
14-7
52-80420-00 A0
Loading...