|
|
These release notes describe newly incorporated features, changed features or changed behavior, resolved issues, and open issues for the Cisco ATA 186 and the Cisco ATA 188 for Release 2.16.ms (MGCP and SCCP protocols).
 |
Note The term Cisco ATA refers to both the Cisco ATA 186 and the Cisco ATA 188. |
These release notes provide the following information:
The Cisco ATA is an analog telephone adaptor that allows regular analog telephones to operate on IP-based telephony networks. The Cisco ATA supports two voice ports, each with its own independent telephone number.
Two Cisco ATA products are available to Cisco customers—the Cisco ATA 186 and the Cisco ATA 188. Both products run the same software and have two voice ports. The difference between these products is that the Cisco ATA 186 has one RJ45 port that provides access to an Ethernet network, while the Cisco ATA 188 has an Ethernet switch and two RJ45 ports. The Cisco ATA 188 has one RJ45 port for access to an Ethernet network and a second RJ45 port for connecting a downstream Ethernet device such as a PC.
Before you can use the Cisco ATA Release 2.16.ms, you must first download and upgrade the Cisco ATA software. You can download the software, after logging in, at:
http://www.cisco.com/cgi-bin/tablebuild.pl/ata186
|
Note If you are using the Cisco ATA executable-file-upgrade method, check with the administrator of the Cisco CallManager (if you are using SCCP) and TFTP server to make sure that the TFTP upgrade method is disabled. Otherwise, the Cisco ATA might downgrade to an old image via TFTP. |
For more information about downloading and upgrading software, see the Cisco ATA administrator's guides for the signaling protocol you are using. The administrator's guides can be found at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ata/ataadmn/index.htm
In releases prior to 2.16.ms, the Cisco ATA first attempts to register with Cisco CallManager as device type Cisco ATA 186 (for either the Cisco ATA 186 or the Cisco ATA 188). If the Cisco ATA cannot register as a Cisco ATA 186 device type, it then attempts to register with Cisco CallManager as device type Cisco 7960. This behavior was created specifically for the Cisco ATA in conjunction with Cisco CallManager 3.0 and 3.1 because those releases of Cisco CallManager do not support the device type Cisco ATA 186.
This behavior has been modified in Release 2.16.ms to prevent the possibility that the Cisco ATA might register incorrectly as a Cisco 7960 device type with Cisco CallManager 3.2 if the first registration attempt is delayed for any reason.
You can now configure the Cisco ATA ConnectMode parameter (bit 27) to specify which device type the Cisco ATA should use when registering with Cisco CallManager 3.2 or later:
This section contains information on new features for Cisco ATA Release 2.16.ms:
This section contains information on new features for Cisco ATA Release 2.16.ms for both MGCP and SCCP:
The Cisco ATA inserts tone type IDs into its debug log.
To help analyze call flows, the tone locally played by the Cisco ATA to the FXS port is reported by means of the prserv debug log. Local tones are different from other tones because local tones are not carried within the inband audio. Instead, the Cisco ATA is prompted by a network event to play the tone, and the Cisco ATA generates the tone for the exclusive purpose of playing it to the attached telephone handset. For example, during a call between the Cisco ATA and a far-end phone, the far-end user might press a digit on the dial pad, thus sending an AVT Named Signaling Event to the Cisco ATA. This event prompts the Cisco ATA to generate a DTMF tone and to play the tone locally to the Cisco ATA phone.
Table 1 lists the tone type identifier and its description for local tone reporting.
| Tone Type ID | Description |
|---|---|
|
Note For information on the prserv debug tool, see the "Configuring and Debugging Fax Services" section in the Cisco ATA administrator's guides. |
To monitor the quality of service for the media stream, you can access RTP packet statistics of the two voice ports and their channels by opening the following page on the Cisco ATA Web server:
The following RTP packet statistics are reported:
Using the refresh feature on the RTP Statistics page, you can obtain updated, real-time RTP statistics during a call.
To reset the Cisco ATA counters, do the following:
Using voice configuration menu code 3123#, you can obtain basic network status to use for diagnostic purposes. After you enter this code, the Cisco ATA announces a message in the following format:
If the hexadecimal value provided by the voice configuration menu is 0x1d, the network status of the Cisco ATA is shown in Table 3.
Table 3 Voice Configuration Menu Example Network Status
| Bit Number | Description | Boolean Value |
|---|---|---|
| 0 | Cisco ATA sent CDP request | |
| 1 | VLAN ID acquired via CDP | |
| 2 | Cisco ATA sent DHCP request | |
| 3 | DHCP server offered IP address | |
| 4 | Cisco ATA obtained IP address from DHCP server | |
| 5 | Cisco ATA web server is ready |
The Cisco ATA Stats Web page (http://<Cisco ATA IP address>/stats)displays the following information:
D1, D2, D3 values are shown in number of seconds since 00:00:00 UTC, 1970-01-01. If no NTP response has been received from the NTP server, the values of D1, D2, and D3 are 0.
Table 4 Web Configuration Menu Network Status Bitmap
| Bit Number | Description |
|---|---|
Cisco ATA sent request for configuration file, ata<macaddress>, to TFTP server |
|
Cisco ATA sent request for configuration file, atadefault.cfg, to TFTP server |
|
If the hexadecimal value provided by the web configuration menu is 0x1011, the network status of the Cisco ATA is shown in Table 5.
Table 5 Web Configuration Menu Example Network Status
| Bit Number | Description | Boolean Value |
|---|---|---|
Cisco ATA sent request for configuration file, ata<macaddress>, to TFTP server |
||
Cisco ATA sent request for configuration file, atadefault.cfg, to TFTP server |
||
In this release, the Cisco ATA performs a DNS query by first sending its request to DNS server number 1. Then, if DNS server number 1 does not respond to this request within one second, the Cisco ATA sends the same request to DNS server number 2. The Cisco ATA accepts the first response from either of the DNS servers, thereby reducing the time the Cisco ATA requires for name resolution if DNS server number 1 is down or not responding.
The OpFlags parameter now uses a control bit (Bit 13, mask 0x2000) to allow DNS name resolution using both statically configured DNS IP addresses (by means of configuration parameters DNS1IP and DNS2IP) and DHCP server-supplied DNS IP addresses. Therefore, the Cisco ATA can query as many as four DNS IP addresses in one DNS query.
CDP Discovery behavior is implemented as follows:
There is one new MGCP-specific feature in Cisco ATA Release 2.16.ms:
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.
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 The Cisco ATA does not need to be configured to handle MGCP embedded events. |
This section contains information on new SCCP-specific features for Cisco ATA Release 2.16.ms:
During normal Cisco ATA operation, keepalive packets are exchanged between Cisco CallManagers and Cisco ATAs. When the WAN link fails, the Cisco ATA detects that it can no longer exchange keepalive packets with the Cisco CallManager, so the Cisco ATA registers with the SRST router.
The Cisco ATA is configured to query the SRST router as a backup call-processing source when the central Cisco CallManager does not acknowledge keepalive packets. The SRST router performs call setup and processing.
When the WAN link is restored, the Cisco ATA switches back to the central Cisco CallManager, and the SRST router purges its call processing database and reverts to SRST-standby mode. Cisco ATAs that are in use are not interrupted by the WAN link recovery and switch back to the central Cisco CallManager after the call is terminated.
|
Note SRST is configured on an SRST-enabled router and on the Cisco CallManager. The Cisco ATA does not need to be configured to utilize SRST. |
You can control line polarity of the Cisco ATA FXS ports when a call is connected or disconnected by configuring the Polarity bitmap parameter as follows:
The voice configuration menu access code is 304.
In Release 2.16.ms, you can configure an alternate TFTP server to use if the primary TFTP server fails.
You configure an alternate TFTP server by using either the Cisco ATA configuration parameter AltTftpURL or DHCP option 150.
If you use the AltTftpURL parameter to configure the alternate TFTP server, you must enter a non-zero value containing either the IP address or URL of the alternate TFTP server.
However, if you wish to use DHCP option 150 to configure the alternate TFTP server, you must set the value of the AltTftpURL parameter to 0. DHCP option 150 allows you to enter IP addresses for both the primary TFTP server and an alternate TFTP server (if an alternate TFTP server exists). The Cisco ATA would then use the alternate TFTP server IP address specified in DHCP option 150 as its alternate TFTP server.
Other pertinent information about the AltTftpURL parameter follows:
Use the default value of 0 in two scenarios:
The Cisco ATA provides a distinction in the ringer sound for internal and external calls. Internal calls generate one ring, while external calls generate two rings with a very short pause between the rings. No configuration is required and the ring patterns are not configurable.
This section contains information on changed features for Release 2.16.ms and contains the following topics:
The name of the example configuration file that comes with the Cisco ATA MGCP software has changed to mgcp_example.txt (from sk_example.txt).
The following changes are specific to the SCCP protocol:
If the phone that is connected to the Cisco ATA stays off-hook after the far-end party disconnects the call, the Cisco ATA does not play any tone to its FXS port. This means that there will be silence on the phone that is connected to the Cisco ATA. When new calls arrive for this Cisco ATA, the caller will receive a ringback tone and the Cisco ATA will play the call-waiting tone to its FXS port. This is defined as the off-hook-ringing feature.
The Cisco ATA now can be configured to allow for PSTN-like behavior in the scenario just described. If the phone that is connected to the Cisco ATA stays off-hook after the far-end party disconnects the call, the Cisco ATA will play a fast-busy tone to its FXS port. When any new calls arrive for this Cisco ATA, the caller will receive a busy tone.
The amount of waiting time before the Cisco ATA plays a fast-busy tone to its FXS port can be configured using bits 22-25 of the SigTimer parameter, as follows:
Other values: 1-14 in seconds; 15 (never play a fast-busy tone but enable the off-hook ringing feature).
The following changes in Release 2.16.ms apply to both the MGCP and SCCP protocols:
If Bits 7-0 are 0, the TOS bit value for audio packets defaults to 0xB8.
If Bits 15-8 are 0, the TOS bit value for signaling packets defaults to 0x68.
|
Note The previous value of the UDPTOS parameter is carried forward to the TOS parameter during a Cisco ATA upgrade. |
This section lists the issues in previous releases of the Cisco ATA that are resolved in Release 2.16.ms:
This section lists the issues in previous releases of the Cisco ATA that are resolved in Cisco ATA Release 2.16.ms for MGCP only.
When the notified-entity parameter value is a domain name with a specific port number, the Cisco ATA should contact the MGCP Call Agent at the port number instead of using the default value.
The Cisco ATA 186 may send a Notify (NTFY) message with an empty Observed Events (O:) parameter.
The Cisco ATA should automatically append the Call Agent domain name to the machine name before sending a query to the DNS server.
The Cisco ATA must return its preferred-codecs list based on the ordered preference of the Call Agent.
The Reset and Refresh commands cannot be individually executed if web access is disabled.
Bit 16 of the Cisco ATA ConnectMode parameter needs to allow the selection of full or simple Session Description Protocol (SDP) in MGCP 0.1 and 1.0.
The Cisco ATA does not ignore unknown/unsupported SDP "a=" attributes.
This section lists the issues in previous releases of the Cisco ATA that are resolved in Cisco ATA Release 2.16.ms for SCCP only.
Change Cisco ATA reset behavior when both phone lines go to the idle state.
It is not possible to make a fourth-party conference call with the Cisco ATA 186 using the TAPI application.
The Cisco ATA 186 image for Cisco CallManager 3.3(0.243) is out of date.
Initially setting a password through the Web configuration page does not require confirmation.
Cisco ATA 186 may require a special device type for each version of Cisco CallManager.
The Cisco ATA multicast music-on-hold feature causes the Cisco CallManager to drop the call.
Could not open Cisco ATA Web configuration page after multiple failover/fallbacks.
The Cisco ATA is not sending KeepAlive messages to the Cisco CallManager when the KeepAlive Interval was configured through the Cisco CallManager.
DTMF digits A, B, C, and D cannot be relayed through Cisco CallManager.
The Cisco ATA 188 does not mark Type of Service (TOS) bits for SCCP packets that are destined for the Cisco CallManager.
The Cisco ATA 188 does not properly mark Type of Service (TOS) bits for media packets.
DHCP/CDP discovery is not working properly on voice VLANs if the Native VLAN ID is not equal to 1.
In a Cisco ATA-to-IP-Phone call, the Cisco ATA hangs when the IP phone disconnects first.
The Cisco ATA sends out RTP packets even when the G.729 codec with silence suppression has been set.
This section lists the protocol-generic issues in previous releases of the Cisco ATA that are resolved in Release 2.16.ms for both MGCP and SCCP.
Duplexity mismatch occurs in Cisco Discovery Protocol (CDP) information.
Standard G3 fax transmissions are failing because the echo canceller is disabled when it should remain enabled.
The Cisco ATA plays a garbled voice configuration menu prompt.
The Cisco ATA does not allow caller ID to display on a phone that has two lines.
The Cisco ATA 186, when running v2.15 ata186 (Build 020911b), permits the http://< ATA IPaddress>/reset command to take effect without requiring a username or password.
Out-of-band DTMF RTP packets are not sent repeatedly for redundancy purposes, as with the Cisco AS5350.
This section contains the following topics:
There are no MGCP-specific open issues in Cisco ATA Release 2.16.ms.
There are no SCCP-specific open issues in Cisco ATA Release 2.16.ms.
There are no open issues for both MGCP and SCCP in Cisco ATA Release 2.16.ms.
Use these release notes in conjunction with the documents located at this index:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ata/index.htm
The following sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
You can order Cisco documentation in these ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Posted: Thu Jun 19 15:43:36 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.