Table Of Contents
Release Notes for the Cisco ATA 186 and Cisco ATA 188 Release 3.1(2)
Contents
Introduction to the Cisco ATA Analog Telephone Adaptor
Downloading and Upgrading the Software
New Features
New Features for Release 3.1(0)
New Features for Release 3.1(1)
Changed Feature for Release 3.1(1)
Resolved Issues
Resolved Issues for Release 3.1(0)
Resolved Issues for Release 3.1(1)
Resolved Issues for Release 3.1(2)—H.323 Only
Related Documentation
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Cisco ATA 186 and Cisco ATA 188 Release 3.1(2)
October 5, 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(2), as well as for the 3.1(0) and 3.1(1) Cisco ATA releases for the SCCP, SIP, H.323 and MGCP protocols.
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
• Changed Feature for Release 3.1(1)
• Resolved Issues
• 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(2), you must first download and upgrade the Cisco ATA software. You can download the software (ATA030102H323040927A.zup), 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
This section contains the following topics:
• New Features for Release 3.1(0)
• New Features for Release 3.1(1)
New Features for Release 3.1(0)
Table 1 lists new features for Cisco ATA Release 3.1(0), and includes the protocol(s) for which the feature applies.
Table 1 New Cisco ATA Features in Release 3.1(0)
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
|
New Features for Release 3.1(1)
Table 2 lists the new features for Cisco ATA Release 3.1(1), and includes the protocol(s) for which the feature applies.
Table 2 New Cisco ATA Features in Release 3.1(1)
Topic
|
Behavior Description
|
Protocols
|
Multicast Music on Hold
|
The Cisco ATA supports playing multicast Music on Hold. No additional configuration is needed.
|
SCCP
|
NATIP configuration parameter added for H.323
|
This parameter specifies the WAN address of the attached router/NAT, previously used only with the SIP protocol.
Default: 0.0.0.0
Voice Configuration Menu Access Code: 200
|
H.323
|
Loose routing
|
If the Cisco ATA detects that its nearest proxy during a SIP request is a loose router, than the Cisco ATA must follow the procedures defined in RFC-3261 for all requests to that proxy for the remainder of the call. RFC-3621 defines the loose-routing format for SIP requests.
|
SIP
|
Tones for R+digit commands (for Sweden)
|
Prompt tones and error tones are now available for users with R1, R2, R3, and other functions configured in the various contexts of the Call Command field.
|
SIP
|
Changed Feature for Release 3.1(1)
Table 3 lists a changed feature for Cisco ATA Release 3.1(1).
Table 3 Changed Cisco ATA Feature in Release 3.1(1)
Topic
|
Feature Description
|
Protocols
|
Attended Call Transfer using REFER
|
Default call commands for the United States and Sweden have changed. All users using the Attended Call Transfer feature must base their call command string on the new default provided in the latest sip_example.txt file.
|
SIP
|
Resolved Issues
This section contains the following topics:
• Resolved Issues for Release 3.1(0)
• Resolved Issues for Release 3.1(1)
• Resolved Issues for Release 3.1(2)—H.323 Only
Resolved Issues for Release 3.1(0)
This section lists the issues in previous releases of the Cisco ATA that are resolved for Release 3.1(0):
• Resolved Non-Protocol-Specific Issues
• Resolved SIP Issues
• Resolved SCCP Issues
• Resolved H.323 Issues
Resolved Non-Protocol-Specific Issues
Table 4 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(0) for all four supported protocols (SIP, H.323, SCCP and MGCP).
Table 4 Resolved Issues for All Protocols for Release 3.1(0)
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 5 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(0)for SIP only.
Table 5 Resolved Issues for SIP Protocol for Release 3.1(0)
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 6 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(0) for SCCP only.
Table 6 Resolved Issues for SCCP Protocol for Release 3.1(0)
DDTS Number
|
Summary
|
CSCed52004
|
The Cisco ATA cannot handle zero-length TCP messages.
|
Resolved H.323 Issues
Table 7 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(0) for H.323 only.
Table 7 Resolved Issues for H.323 Protocol for Release 3.1(0)
DDTS Number
|
Summary
|
CSCed65226
|
The Cisco ATA does not use symmetric Tx/Rx codecs.
|
Resolved Issues for Release 3.1(1)
This section lists the issues in previous releases of the Cisco ATA that are resolved for Release 3.1(1):
• Resolved Non-Protocol-Specific Issues
• Resolved SIP Issues
• Resolved SCCP Issues
• Resolved H.323 Issues
• Resolved MGCP Issues
Resolved Non-Protocol-Specific Issues
Table 8 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(1) for all four supported protocols (SIP, H.323, SCCP and MGCP).
Table 8 Resolved Issues for All Protocols for Release 3.1(1)
DDTS Number
|
Summary
|
CSCee75045
|
The Cisco ATA186 cannot correctly perform a reassembly of IP fragment packets.
|
CSCee84790
|
ATA may experience one-way audio after the RTP stream source is changed.
|
Resolved SIP Issues
Table 9 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(1) for SIP only.
Table 9 Resolved Issues for SIP Protocol for Release 3.1(1)
DDTS Number
|
Summary
|
CSCeb29729
|
Repeat dialing following a busy signal fails when the caller is in a three-way call.
|
CSCeb29807
|
Repeat dialing after a busy signal did not take place after a conference call completed.
|
CSCed52352
|
The attended CT feature did not work with the BTS10200 4.1.1I6 load.
|
CSCed78184
|
Request to add examples to the Cisco ATA administration guide for configuring the Sweden Call Waiting Hang-Up Alert feature.
|
CSCed81921
|
Message waiting indicator (MWI) messages are not recognized by the Cisco ATA 186.
|
CSCee08227
|
The Cisco ATA is not sending a BYE request when a call is disconnected.
|
CSCee11722
|
Blind transfer from the Cisco ATA to the Cisco IP Phone 7960 fails.
|
CSCee11971
|
If the conference warning tone is enabled, the conference feature does not work properly.
|
CSCee14271
|
The user can use the call return function to dial a blocked number.
|
CSCee15008
|
Malformed Request-URI, To-URI, and From-URI occurring in INVITE requests.
|
CSCee16830
|
Caller ID is presented upon call return even when Caller Line Identification Restriction (CLIR) is the default CallFeature setting.
|
CSCee21833
|
The Cisco ATA sends a malformed register.
|
CSCee22057
|
The Cisco ATA plays the conference warning tone even after one party in the conference has dropped out.
|
CSCee38045
|
The Cisco ATA does not register after receiving a STUN binding response.
|
CSCee39037
|
The Cisco ATA inserts multiple Authentication headers in registers.
|
CSCee39477
|
Authentication fails when used with privacy/anonymity features.
|
CSCee43810
|
The Cisco ATA occasionally crashes during a lengthy call.
|
CSCee54974
|
NatServer default port is 0 instead of 5060.
|
CSCee55257
|
The Cisco ATA routes calls to the voice prompt server instead of the call-forwarded number.
|
CSCee55974
|
The DialPlan stored in the Cisco ATA configuration file was being truncated to 244 characters.
|
CSCee57176
|
The Cisco ATA sends a malformed ACK and no subsequent BYE after a CANCEL request.
|
CSCee58660
|
There are occasional problems with ACK Req-URIs that the Cisco ATA sends after receiving a 487 Request Cancelled message.
|
CSCee59004
|
The Cisco ATA 186 processes the Range command and the DialPlan R rule incorrectly.
|
CSCee60515
|
The Cisco ATA can be attacked by RST, SYN and data-injection packets.
|
CSCee63601
|
A From header that contains an escape character is not copied correctly.
|
CSCee66726
|
Type Of Service (TOS) values are not being used to tag signaling and RTP packets.
|
CSCee68397
|
Sweden hook flash receives unexpected audio after conferencing is established.
|
CSCee89902
|
Sweden G.726 hook flash receives unexpected audio leak after conferencing is established.
|
CSCee91360
|
Loose router-enabled proxy causes subsequent calls to fail.
|
Resolved SCCP Issues
Table 10 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(1) for SCCP only.
Table 10 Resolved Issues for SCCP Protocol for Release 3.1(1)
DDTS Number
|
Summary
|
CSCed51467
|
The Conference Bridge keeps the phone session after the connection is lost.
|
CSCed90702
|
The behavior of the Cisco ATA for Conference Call differs between Cisco CallManager release 3.3 and Cisco CallManager release 4.0.
|
CSCed93371
|
The behavior of the Cisco ATA for the Call Hold/Resume feature differs between Cisco CallManager release 3.3 and Cisco CallManager release 4.0.
|
CSCee18828
|
The Cisco ATA186 is not playing Music on Hold on load ATA030100SCCP040211A.
|
CSCee22280
|
Support for Multicast Music on Hold for SCCP requested.
|
CSCee38651
|
The Cisco ATA186 stops sending RTP packets for preservation calls after five minutes.
|
CSCee66104
|
For an active Cisco ATA call on port 2 only, this call is not preserved during a Cisco CallManager failover.
|
Resolved H.323 Issues
Table 11 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(1) for H.323 only.
Table 11 Resolved Issues for H.323 Protocol for Release 3.1(1)
DDTS Number
|
Summary
|
CSCeb50977
|
The cch323_h225_receiver encounters a parse error.
|
CSCed84087
|
The Cisco ATA may not send the DRQ, depending on the call sequence.
|
CSCee14184
|
The Cisco ATA may send the wrong TCP sequence to the Cisco IOS Gateway.
|
CSCee41983
|
Supportability of G.723 codecs not depicted properly in H.245 CESE.
|
Resolved MGCP Issues
Table 12 lists the issues in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(1) for MGCP only.
Table 12 Resolved Issues for MGCP Protocol for Release 3.1(1)
DDTS Number
|
Summary
|
CSCee03928
|
RTP statistics are missing in syslog.
|
CSCee54690
|
In NCS 1.0, the Cisco ATA uses an incorrect package name for PING.
|
CSCee76328
|
MGCP protocol error number 510 occurs.
|
Resolved Issues for Release 3.1(2)—H.323 Only
Table 13 lists the issue in previous releases of the Cisco ATA that are resolved for Cisco ATA Release 3.1(2). This release is only for the H.323 protocol.
Table 13 Resolved Issues for H.323 Protocol for Release 3.1(2)
DDTS Number
|
Summary
|
CSCef42352
|
The Cisco ATA resets after receiving packets from a test suite.
|
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
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://cisco.com/univercd/cc/td/doc/pcat/
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/packet
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
•World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.html
CCSP, the Cisco Square Bridge logo, 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, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, 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. (0406R)
