Release Notes for the Cisco ATA 186 and Cisco ATA 188 Release 3.1(0)

Table Of Contents

Release Notes for the Cisco ATA 186 and Cisco ATA 188 Release 3.1

Contents

Introduction to the Cisco ATA Analog Telephone Adaptor

Downloading and Upgrading the Software

New Features for Release 3.1

Resolved Issues for Release 3.1

Resolved Non-Protocol-Specific Issues

Resolved SIP Issues

Resolved SCCP Issues

Resolved H.323 Issues

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Release Notes for the Cisco ATA 186 and Cisco ATA 188 Release 3.1

Feb 10, 2004

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 3.1 (SIP, H.323, SCCP, and MGCP protocols).

Note The term Cisco ATA refers to both the Cisco ATA 186 and the Cisco ATA 188.

Contents

These release notes provide the following information:

• Introduction to the Cisco ATA Analog Telephone Adaptor

• Downloading and Upgrading the Software

• New Features for Release 3.1

• Resolved Issues for Release 3.1

• Related Documentation

• Obtaining Documentation

• Obtaining Technical Assistance

Introduction to the Cisco ATA Analog Telephone Adaptor

The Cisco ATA is an analog telephone adaptor that allows traditional 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 Cisco ATA 186 has one RJ45 port that provides access to an Ethernet network. The Cisco ATA 188 has an Ethernet switch and two RJ45 ports—one for accessing an Ethernet network and one for connecting a downstream Ethernet device such as a PC.

Downloading and Upgrading the Software

Before you can use the Cisco ATA Release 3.1, 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 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

New Features for Release 3.1

Table 1 lists new features for Cisco ATA Release 3.1, and includes the protocol(s) for which the feature applies.

Table 1 New Cisco ATA Features in Release 3.1

Topic

Behavior Description

Protocols

Auto-Retrieval of Held Call

Use ConnectMode bit 26 to enable this feature. If the Cisco ATA user places a call on hold to either initiate a second call or to answer a call-waiting call, this feature allows the Cisco ATA to automatically reconnect to the held party whenever the active call is disconnected from the far end.

SIP

Redirect Call to 302 Contact Address

Use ConnectMode bit 0 to enable this feature. This features allows the Cisco ATA to send a redirected INVITE request to the IP address specified in a 302 Temporarily Moved response instead of relaying the message through the SIP proxy.

SIP

Symmetric Codec Support

This Cisco ATA feature employs the use of the H.245 Master/Slave Determination scheme at the beginning of each call to determine which endpoint plays the role of Master in the selection of audio codecs. The Cisco ATA then uses the Master side's codec for transmitting and receiving data. Once media is established, both endpoints communicate with symmetric codecs.

Prior to this release, the Cisco ATA performed codec selection based on its preferred codec, which usually resulted in the Cisco ATA using different codecs for transmitting and receiving data.

H.323

Resolved Issues for Release 3.1

This section lists the issues in previous releases of the Cisco ATA that are resolved for Release 3.1:

• Resolved Non-Protocol-Specific Issues

• Resolved SIP Issues

• Resolved SCCP Issues

• Resolved H.323 Issues

Resolved Non-Protocol-Specific Issues

Table 2 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1 for all four supported protocols (SIP, H.323, SCCP and MGCP).

Table 2 Resolved Issues for All Protocols

DDTS Number

Summary

CSCed45534

Spurious DTMF tones sound on the far end of the Cisco ATA.

CSCed69371

When two Cisco ATAs that are running 3.0 software obtain duplicate IP addresses via DHCP, the Cisco ATA enters an ARP infinite-loop state.

Resolved SIP Issues

Table 3 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1 for SIP only.

Table 3 Resolved Issues for SIP Protocol

DDTS Number

Summary

CSCec57445

When the Cisco ATA disconnects an active call-waiting call, the second call also is dropped.

CSCed21399

Enabling the called-party anonymity feature causes Sweden call-transfer feature to fail.

CSCed29478

Requests originated by a callee to an Anonymous caller with CLIR privacy feature enabled results in the Cisco ATA sending a 404 Not Found response.

CSCed38815

The Cisco ATA may send an incorrect media IP address in the Session Description Protocol of a 200 OK message in response to a Re-INVITE request.

CSCed39412

The Cisco ATA sends an invalid port number when responding to an INVITE request.

CSCed41268

The Cisco ATA must change its behavior for responding to a BYE request for a unknown Call-ID.

CSCed44149

The Cisco ATA is sending a 486 Busy Here Response that does not correlate to the call.

CSCed48422

The Cisco ATA includes an equal (=) sign instead of a colon (:) in the Proxy-Authorization header.

CSCed49460

The Cisco ATA may create a malformed Request-URI when the SIP proxy and outbound proxy are specified as IP addresses and the backup proxy is not specified.

CSCed49981

The Cisco ATA should handle a 180 response with Session Description Protocol (SDP) the same way it handles a 183 response with SDP.

CSCed51785

The Cisco ATA does not put a right-angle bracket around the URL in the Refer-To header.

CSCed51992

The Cisco ATA does not support the overloading of more than one Refer-To header in a REFER request.

CSCed54123

The call-waiting feature fails after a second hook flash on the Cisco ATA is performed, and the on-hold party is dropped.

CSCed60604

The Cisco ATA does not handle RTP header extensions.

CSCed63768

SessionTimer: When the Cisco ATA receives a re-INVITE to Refresh for a call on hold, the Cisco ATA 200 OK Response should contain a 0.0.0.0 address in the 'c=' line of the Session Description Header.

Resolved SCCP Issues

Table 4 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1 for SCCP only.

Table 4 Resolved Issues for SCCP Protocol

DDTS Number

Summary

CSCed52004

The Cisco ATA cannot handle zero-length TCP messages.

Resolved H.323 Issues

Table 5 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1 for H.323 only.

Table 5 Resolved Issues for H.323 Protocol

DDTS Number

Summary

CSCed65226

The Cisco ATA does not use symmetric Tx/Rx codecs.

Related Documentation

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

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

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.

Ordering Documentation

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

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

We appreciate your comments.

Obtaining Technical Assistance

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

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:

•Streamline business processes and improve productivity

•Resolve technical issues with online support

•Download and test software packages

•Order Cisco learning materials and merchandise

•Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

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:

•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

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:

http://www.cisco.com/tac

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.

Cisco TAC Escalation Center

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.

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0401R)

Topic	Behavior Description	Protocols
Auto-Retrieval of Held Call	Use ConnectMode bit 26 to enable this feature. If the Cisco ATA user places a call on hold to either initiate a second call or to answer a call-waiting call, this feature allows the Cisco ATA to automatically reconnect to the held party whenever the active call is disconnected from the far end.	SIP
Redirect Call to 302 Contact Address	Use ConnectMode bit 0 to enable this feature. This features allows the Cisco ATA to send a redirected INVITE request to the IP address specified in a 302 Temporarily Moved response instead of relaying the message through the SIP proxy.	SIP
Symmetric Codec Support	This Cisco ATA feature employs the use of the H.245 Master/Slave Determination scheme at the beginning of each call to determine which endpoint plays the role of Master in the selection of audio codecs. The Cisco ATA then uses the Master side's codec for transmitting and receiving data. Once media is established, both endpoints communicate with symmetric codecs. Prior to this release, the Cisco ATA performed codec selection based on its preferred codec, which usually resulted in the Cisco ATA using different codecs for transmitting and receiving data.	H.323

DDTS Number	Summary
CSCed45534	Spurious DTMF tones sound on the far end of the Cisco ATA.
CSCed69371	When two Cisco ATAs that are running 3.0 software obtain duplicate IP addresses via DHCP, the Cisco ATA enters an ARP infinite-loop state.

DDTS Number	Summary
CSCec57445	When the Cisco ATA disconnects an active call-waiting call, the second call also is dropped.
CSCed21399	Enabling the called-party anonymity feature causes Sweden call-transfer feature to fail.
CSCed29478	Requests originated by a callee to an Anonymous caller with CLIR privacy feature enabled results in the Cisco ATA sending a 404 Not Found response.
CSCed38815	The Cisco ATA may send an incorrect media IP address in the Session Description Protocol of a 200 OK message in response to a Re-INVITE request.
CSCed39412	The Cisco ATA sends an invalid port number when responding to an INVITE request.
CSCed41268	The Cisco ATA must change its behavior for responding to a BYE request for a unknown Call-ID.
CSCed44149	The Cisco ATA is sending a 486 Busy Here Response that does not correlate to the call.
CSCed48422	The Cisco ATA includes an equal (=) sign instead of a colon (:) in the Proxy-Authorization header.
CSCed49460	The Cisco ATA may create a malformed Request-URI when the SIP proxy and outbound proxy are specified as IP addresses and the backup proxy is not specified.
CSCed49981	The Cisco ATA should handle a 180 response with Session Description Protocol (SDP) the same way it handles a 183 response with SDP.
CSCed51785	The Cisco ATA does not put a right-angle bracket around the URL in the Refer-To header.
CSCed51992	The Cisco ATA does not support the overloading of more than one Refer-To header in a REFER request.
CSCed54123	The call-waiting feature fails after a second hook flash on the Cisco ATA is performed, and the on-hold party is dropped.
CSCed60604	The Cisco ATA does not handle RTP header extensions.
CSCed63768	SessionTimer: When the Cisco ATA receives a re-INVITE to Refresh for a call on hold, the Cisco ATA 200 OK Response should contain a 0.0.0.0 address in the 'c=' line of the Session Description Header.