|
|
Table Of Contents
Cisco ATA-Supported MGCP Services
Call Agent Redundancy with Configuration Parameters
Cisco ATA Registration Process with MGCP
Complete Reference Table of all Cisco ATA MGCP Services
Supported MGCP Connection Modes
Supported Local Connection Options
NCS 1.0 L-Package Supported by the Cisco ATA with MGCP
MGCP 0.1-1.0 L-Package Supported by the Cisco ATA with MGCP
MGCP 0.1-1.0 G-Package Supported by the Cisco ATA with MGCP
MGCP 0.1-1.0 D-Package Supported by the Cisco ATA with MGCP
Parameters in Commands Sent to the Call Agent
Parameters in Responses Sent to the Call Agent
Parameters in Commands Received from the Call Agent Processed by the Cisco ATA
Parameters in Responses Received from the Call Agent Processed by the Cisco ATA
Cisco ATA-Supported MGCP Services
This section provides information about basic and additional MGCP services that the Cisco ATA supports:
•
Important Basic MGCP Services—This section includes a list of parameters that you must configure in order for the Cisco ATA to function in a MGCP environment.
•
•
•
•
•
•
•
Note
Note
Important Basic MGCP Services
This section provides descriptions and cross references for configuring required MGCP parameters and also for configuring other MGCP services:
•
Required Parameters
You must configure the following parameters for the Cisco ATA to work properly in MGCP mode:
•
The complete endpoint identifier sent to the Call Agent has the format:
<EPIDx>@<ip_addr>
where x is port 0 or port 1 of the Cisco ATA, and ip_addr is the IP address of the MGCP endpoint.
For more information about endpoints and connections, see the "Endpoints and Connections" section.
Note
•
Note
Setting the Codec
The LBRCodec (low-bit-rate codec) parameter determines whether the G.723 or G.729A codec, in addition to G.711A-law and G.711µ-law, can be used for receiving and transmitting. For configuration information, see the "LBRCodec" section on page 5-15.
Configuring Refresh Interval
When the value specified in the CfgInterval parameter is reached, the Cisco ATA attempts to refresh its configuration file from the TFTP server. By opening a web page for the Cisco ATA, you can perform a refresh before the scheduled refresh. Set the CfgInterval parameter to an interval value (in seconds) for refreshing the Cisco ATA configuration file. Cisco recommends that the interval be semi-random to prevent many simultaneous contacts with the TFTP server. For more information, see the "CfgInterval" section on page 5-5.
When the Cisco ATA contacts the TFTP server, it also checks to see if an upgrade signaling image has been placed on the TFTP server. If such an image exists, the Cisco ATA will download this image.
Additional MGCP Services
This section provides information about MGCP features that the Cisco ATA supports as well as descriptions of Cisco ATA behavior in an MGCP environment. This section contains the following topics:
•
•
Endpoints and Connections
The Cisco ATA has two telephone Foreign Exchange Station (FXS) ports. These ports are called port 0 and port 1. Port 0 is labeled Phone 1 on the Cisco ATA and port 1 is labeled Phone 2. Each port is an MGCP endpoint: Port 0 is MGCP endpoint 0, and port 1 is MGCP endpoint 1. The configurable parameters for MCGP endpoints are as follows:
•
•
Each MGCP endpoint supports one device, either an analog phone set or a fax machine, and up to two connections per device are allowed.
Each connection has a fixed ID, either 0, 1, 2, or 3. Connection IDs 0 and are 2 assigned to MGCP endpoint 0, and connection IDs 1 and 3 are assigned to MGCP endpoint 1.
The IP address of each MGCP endpoint identifier can be enclosed by square brackets by setting Bit 20 of the ConnectMode, enabling the use of square brackets. The use of brackets is disabled by default. (For more information, see the "ConnectMode" section on page 5-24.)
Example
This example shows an EPID1orSID1 parameter value with brackets around the IP address of the endpoint:
aaln/1@[128.107.139.111]MGCP Endpoint Device Type
To request the device type from the Cisco ATA, the Call Agent must use the following syntax in the RequestedInfo (F:) parameter line of an AUEP command:
F: X-UAThe Cisco ATA responds with the following device-type:
X-UA: Cisco/ATA186Call Agent Redundancy with Configuration Parameters
Call Agent (CA) redundancy is supported in two ways. You can use the following sets of parameters to configure the primary and secondary CA IP addresses or URLs:
•
•
If the CA is identified with the format CallAgentName@HostName, enter the CA name in the CAxUID parameter and enter the HostName in the CAxorCMx parameter (x is 0 or 1).
If the CA is identified using a URL, enter the URL in the CAxorCMx parameter. An optional port number can also be entered in the format CAxorCMx:Port# (x is 0 or 1).
When the Cisco ATA power ups or performs a configuration update, it tries to contact the primary CA at CA0orCM0. If there is no response or the address is not reachable, the Cisco ATA then tries to contact the secondary CA. The Cisco ATA continues to alternate attempts to contact the primary and secondary CAs until it gets a response.
If the CAxorCMx parameter is configured with a URL, the Cisco ATA contacts the DNS server to resolve the name. The Cisco ATA accepts up to four IP addresses from the DNS server. During operation, if contact is lost between the Cisco ATA and its CA, the Cisco ATA uses an exponential timeout period on each attempt to reach the CA at the IP addresses. The Cisco ATA cycles through the IP addresses until it gets a response.
Cisco ATA Registration Process with MGCP
When the Cisco ATA powers up, each MGCP endpoint is in a disconnected state. The Cisco ATA sends a Restart in Progress (RSIP) command for each MGCP endpoint to the preconfigured Call Agent using one of the following syntax definitions, selected by using Bit 24 in the ConnectMode parameter (see the "ConnectMode" section on page 5-24):
Syntax Type 1
RSIP EPID0@ip_address MGCPVersionRM: restartand
RSIP EPID1@ip_address MGCPVersionRM: restartSyntax Type 2
RSIP *@ip_address MGCPVersionRM: restartUpon a successful response from the Call Agent to the RSIP command, the Cisco ATA places each MGCP endpoint into the connected state and resumes normal operation. Destinations of subsequent Cisco ATA commands to the Call Agent are set according to the NotifyEntity header. Call Agent responses are always sent to the source address of the origin of the command.
If the Cisco ATA does not receive a Call Agent response to a subsequent command when the maximum number of retransmissions of the command times out, the Cisco ATA puts both Call Agent endpoints back into the disconnected state. The Cisco ATA then sends RSIP messages to the destinations indicated in the NotifyEntity header. This is shown in the following example:
RSIP Message for Disconnect State
RSIP *@ip_address MGCPVersionRM: disconnectedComplete Reference Table of all Cisco ATA MGCP Services
Table 4-1 is a reference table that lists all configurable features for the Cisco ATA (using MGCP), and includes links to the detailed descriptions of the parameters used for configuring these features.
Table 4-1 Configurable Features and Related Parameters for MGCP
Caller ID format
Call waiting
Cisco Discovery Protocol—disabling
Codec—Specify default preferred codec
Codec names to use in LocalConnectionOption command
Configuration-update interval
DHCP usage—disabling
Debug messages—configuring host
DNS name resolution
Domain name server
Domain name of endpoint ID
Dual Tone Multi-frequency (DTMF) method
Encryption
Endpoint-identifier specification
EPID0orSID0 and EPID1orSID1, page 5-14
(Also see the "Endpoints and Connections" section.)Fax CED tone detection
Fax CNG tone detectionFax pass-through
G.711 codec
G.711 silence suppression
Hook-flash event time requirements
ID of primary Call Agent
ID of secondary Call Agent
Listening port for MGCP commands
Low bit-rate codec selection
MGCP version string identifier
Mid-call service style—Bellcore, Cisco VG248 or Cisco ATA
Named Signaling Event (NSE) payload number
Registration
ConnectMode, page 5-24
(Also see the "Endpoints and Connections" section and the "Cisco ATA Registration Process with MGCP" section.)Ring-cadence pattern
Real-Time Transfer Protocol (RTP) media port
Real-Time Transfer Protocol (RTP) packet size
Retransmission interval for MGCP commands
Retransmission of commands—Maximum number of times to retransmit
Secondary domain name server
Static network router probe
TFTP file—Set to not use internally generated name
Tones: BusyTone, CallWaitTone
ConfirmTone, DialTone, ReorderTone, and RingBackTone parametersTracing
Type of Service (TOS) bits
VLAN encapsulation
VLAN 802.1Qtags
VLAN UDP and TCP COS fieldsVLAN mode
Web configuration—disallowing
Supported MGCP Connection Modes
The Cisco ATA supports the following MGCP connection modes:
•
•
•
•
•
Supported Local Connection Options
The Cisco ATA supports the following local connection options for the MGCP LocalConnectionOption parameter:
•
•
•
•
•
The LocalConnectionOption parameter is used as "L:" in an MGCP message. The "L:" parameter provides information for the connection, such as packetization period, codec to use, turning echo cancellation on and off, and turning silence suppression on and off.
Related CIsco ATA Parameter
CodecName, page 5-19—Use this parameter to specify the encoders and decoders to use in the LocalConnectionOption parameter.
Supported Signals and Events
The Cisco ATA supports the following persistent events:
•
•
•
The Call Agent must request all other notified events:
•
•
•
•
•
•
Note
The applicable signals and events are included in the following sections, which show the software packages of commands that the Cisco ATA supports:
•
•
•
•
NCS 1.0 L-Package Supported by the Cisco ATA with MGCP
MGCP 0.1-1.0 L-Package Supported by the Cisco ATA with MGCP
MGCP 0.1-1.0 G-Package Supported by the Cisco ATA with MGCP
MGCP 0.1-1.0 D-Package Supported by the Cisco ATA with MGCP
Table 4-5 MGCP 0.1-1.0 D-Package
0-9, *, #, A, B, C, D
DTMF tones
E, BR
l
DTMF long-duration
E
of
Operation failed
E
t
Timer (DTMF input)
E
x
DTMF tones 0-9 wildcard
E
Commands Supported with MGCP
The Cisco ATA supports the following commands for communication with the Call Agent:
•
•
•
•
•
•
•
•
These commands are included in the following sections, which list various categories of parameters and the commands in which they are used:
•
•
•
•
Parameters in Commands Sent to the Call Agent
Table 4-6 Parameters in Commands Sent to the Call Agent
ResponseAck
NTFY (notify). Supported for 1.0 and NCS.
RequestIdentifier
NTFY, RQNT
ObservedEvents
NTFY
RestartMethod
RSIP
Parameters in Responses Sent to the Call Agent
Parameters in Commands Received from the Call Agent Processed by the Cisco ATA
Parameters in Responses Received from the Call Agent Processed by the Cisco ATA
Table 4-9 Parameters in Responses Received from the Call Agent Processed by the Cisco ATA
ResponseAck
DLCX, NTFY (1.0, NCS)
NotifiedEntity
RSIP
MGCP Embedded Events
The embedded event action (E) can be used to reduce response time and increase bandwidth efficiency of MGCP signaling.
Without embedded events, multiple MGCP messages would be required to achieve the same behavior that one message with embedded events can achieve. Also, the time for a dial tone to sound after the user goes off-hook is delayed when embedded events are not used in MGCP messages.
The Cisco ATA supports one level of embedded commands that are compliant with the MGCP 1.0 and MGCP 1.0 NCS profiles. An embedded NotificationRequest that adheres to this limitation must not contain another embedded NotificationRequest.
The service provider has the responsibility of configuring the MGCP Call Agent.
ExampleR: hd(A, E(S(dl), R(oc, [0-9#T](D)), D((1xxxxxxxxxx|9011x.T))))In this example, the Cisco ATA requests to be notified of an off-hook event, at which time the Cisco ATA directs the end-point device to play a dial tone and to collect DTMF digits on such event.
Note
Posted: Thu Feb 9 13:18:46 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
