Cisco SIP IP Phone 7960 Version 2.1 Release Note
Available Languages
Table Of Contents
Cisco SIP IP Phone 7960 Version 2.1 Release Note
Ordering the Cisco SIP IP Phone 7960 Administrator Guide
Known Problems in this Release
Admendments to the Documentation
Obtaining Technical Assistance
Cisco SIP IP Phone 7960 Version 2.1 Release Note
June, 2001
This document lists the known problems in the Cisco SIP IP Phone 7960 Version 2.1 and contains information about the Cisco SIP IP Phone 7960 (hereafter referred to as the Cisco SIP IP phone) that was not included in the Cisco SIP IP phone documentation.
Sections in this document include the following:
•
Ordering the Cisco SIP IP Phone 7960 Administrator Guide
•
•
•
Ordering the Cisco SIP IP Phone 7960 Administrator Guide
The Cisco SIP IP phone firmware is available via CCO only. Therefore, to obtain a printed copy of the Cisco SIP IP Phone 7960 Administrator Guide, you must either download the PDF file of the manual from CCO or order a printed and bound copy of the manual through Cisco MarketPlace.
To obtain a PDF file of the Cisco SIP IP Phone 7960 Administrator Guide, Version 2.1, which you can download and print, go to: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/admin2.pdf
Related Documentation
In addition to this release note, use the following publications to learn how to install and use the Cisco SIP IP phone:
•
•
•
Known Problems in this Release
This section lists the currently known problems in the Cisco SIP IP phone Version 2.1.
Problem: Cisco SIP IP phone crashes with an async break or PC reboot (CSCds20969)
Problem Description: The Cisco SIP IP phone might lock up if a break is sent to the phone via the RS-232 port. The phone might also lock up if the PC to which the RS-232 port is attached is rebooted.
Recommended Action: Unplug and replug the power cord on the phone.
Problem: When the network media is manually configured, the inline power does not work when connected to a Catalyst 3500 switch (CSCds27516)
Problem Description: When the network media is manually configured, the inline power support does not work when the Cisco SIP IP phone is connected to a Catalyst 3500 switch.
Recommended Action: When connecting to a Catalyst 3500 switch, configure the phone to automatically negotiate the network media type by selecting Auto for the Network Media Type parameter located in the Network Configuration menu.
Problem: When in overview mode, the Cisco SIP IP phone soft keys do not work (CSCds35841)
Problem Description: Pressing a line button during a call displays the overview screen on which there is located a Redial and NewCall soft key. However, these soft keys are ignored by the phone if pressed.
Recommended Action: Return to the call screen (wait 8 seconds for the call screen to reappear or press the line button again).
Problem: Caller cannot terminate a call transferred back by the Callee (CSCds64602)
Problem Description: The Cisco SIP phone does not properly handle the following call scenario:
–
–
–
Recommended Action: Press the speaker button or go off hook and back on hook several times to terminate the call.
Problem: Message Waiting Indication (MWI) for Cisco uOne Messaging System with the Cisco SIP IP phone does not work after a phone reboot (CSCdt11124))
Problem Description: The MWI on the Cisco SIP IP phone is not retained following a phone power cycle or reboot because the Unsolicited Notify is a single event that occurs at the time a message is deposited or retrieved.
Recommended Action: None. If a system upgrade or other action that requires a phone reboot is to be performed, notify the end users of this condition.
Problem: 7960 SDP Codec negotiation issue causes one-way voice (CSCdt89255)
Problem Description: The 7960 SIP IP Phone SDP codec negotiation can cause one-way voice when other endpoint is using asynchronous codec support.
Recommended Action: Ensure other clients support single codec. The 7960 SIP IP Phone does not support asynchronous codec.
Problem: proxyN_port of UNPROVISIONED does not default to 5060 (CSCdu35450)
Problem Description: The proxyN_port parameter in the SIP 7960 IP Phone
does not default to 5060. It defaults to 0 instead.
Recommended Action: Set the proxyN_port parameter to 5060, rather than "" or "UNPROVISIONED".
Problem: DSP Timeouts with multiple instances of DTMF and speakerphone (CSCdu43127)
Problem Description: On rare occasion when using speakerphone, G729a codec, VAD enabled, and DTMF, the phone can encounter a DSP timeout which only affects the active call. Any subsequent calls work unless the above four factors are used again. The DSP timeout only occurs when ALL four of the above factors happen simultaneously, and only affects the active call.
This issue is also a side effect of excessive debug use.
Recommended Actions:
–
–
–
Problem: Invalid SRV in maddr of Contact causes hung midcall INVITE (CSCdu43128)
Problem Description: After a basic call is established and a mid-call INVITE is sent to the phone, with an invalid SRV entry in the Contact: header, the phone leaves call hung. The SIP messaging is correct in that the mid-call INVITE gets rejected with a 500 Internal Server error, but the display still shows a connected call.
Recommended Action: Press the EndCall softkey or hang up the phone.
Problem: Line name with a leading "+" causes all calls to fail with a 404 (CSCdu40212)
Problem Description: When the phone has a lineN_name with a leading +, such as +1234567, all calls with or without the + are rejected with a "404 Not Found".
Recommended Action: Set the lineN_name so that it does not include the leading +, i.e. 1234567
Problem: An Initial INVITE with c=0.0.0.0 gets rejected with 500 (CSCdu49096)
Problem Description: The phone rejects initial INVITEs that contain a 'hold' SDP with a 500 Internal Server Error. This scenario would be used for 3rd party Call Control.
Recommended Action: None.
New Features in This Release
For detailed information about each new feature and a list of all the Cisco SIP IP phone features, refer to the Version 2.1 of the Cisco SIP IP Phone 7960 Administrator Guide.
The following new features have been added to the Cisco SIP IP phone Version 2.1:
•
The "Route" attribute of the Template tag in the dial plan template file can be used to indicate which proxy (default, emergency, FQDN) that the call should be initially routed to. For example, to configure an emergency proxy, specify value of the "Route" attribute as "emergency".
•
When the primary proxy does not respond to the INVITE message sent by the Cisco SIP IP Phone after the configured number of retries, the Cisco SIP IP Phone sends the INVITE to the backup proxy. This is independent from which proxy is defined in the "Route" attribute in the dial plan template used.
The Cisco SIP IP Phone does not have to register with the backup proxy. All interactions, such as authentication challenges, with the backup proxy is treated the same as the interactions with the primary proxy.
The backup proxy is only used with new INVITE messages. Once the backup proxy is used, it is active for the duration of the call.
The location of the backup SIP proxy can be defined as an IP address in the default configuration file. See proxy_backup and proxy_backup_port parameters in Modifying the Default SIP Configuration File in Chapter 3, "Managing Cisco SIP IP Phones".
•
An optional emergency SIP proxy can be configured with the "Route" attribute of the Template tag in the Dial Plan template file. See "Support of user-defined proxy routing".
When an emergency SIP proxy is configured and a call is initiated, the phone generates an INVITE message to the address specified in the proxy_emergency parameter. The emergency proxy is used for the call duration.
The location of the emergency proxy can be defined as an IP address in the default configuration file. See proxy_emergency and proxy_emergency_port parameters in Modifying the Default SIP Configuration File in Chapter 3, "Managing Cisco SIP IP Phones".
•
DNS SRV is the Domain Name Server RR used to locate servers for a given service.
SIP on Cisco's SIP IP Phones use DNS SRV query to determine the IP address of the SIP Proxy or the Redirect Server. The query string generated is in compliance with RFC2782, and prepends the protocol label with an underscore "_"; as in "_protocol._transport.". The addition of the underscore reduces the risk of the same name being used for unrelated purposes.
Also in compliance with RFC 2782 and the draft-ietf-sip-srv-01 spec. is that the system can remember multiple IP addresses and use them properly. In the draft-ietf-sip-srv-01 spec, it is assumed that all proxies returned for the SRV record are equivalent such that the phone can register with any of the proxies and initiate a call using any other proxy.
•
VAD can be enabled or disabled with enable_vad parameter. Value 0 for disable, and value 1 for enable. See enable_vad parameter in Modifying the Default SIP Configuration File in Chapter 3, "Managing Cisco SIP IP Phones".
•
Three-way conferencing supports one phone conferencing with two other phones by providing mixing on the initiating phone. To set up a 3-way conference call, see documentation on Making Conference Calls in "Getting Started with the Cisco IP Phone 7960".
Limitations:
–
Workaround: Have one leaf node hang up to leave other leg of the call connected.
–
Workaround: Hang up the call-waiting call and then conference in the person who just called.
–
Workaround: None. Transfer ability is disabled on the bridge node.
–
Workaround: None. DTMF capability is disabled on the bridge node.
–
Workaround: None. An attempt to force a different codec will result in the conference not being established.
–
Workaround: Use the Mute button instead of hold for leaf nodes to still be able to communicate.
–
Workaround: Wait for the third party to answer the second call leg prior to conferencing in the first call leg.
•
If the INVITE message contains an Alert-Info header, distinctive ringing is invoked, Format of the header is "Alert-info: x". "x" can be any number. This header is only received by the phone which does not generate this header.
Distinctive ringing is supported when the phone is idle or during a call. In the idle mode, the phone rings with a different cadence. The selected ringing type plays twice with a short pause in between. In call-waiting mode, two short beeps are generated instead of one long beep.
Admendments to the Documentation
This section contains information that has been amended or was not included in the Cisco SIP IP Phone 7960 Administrator Guide or Getting Started with the Cisco IP Phone 7960/7940. When applicable, the headings in this section correspond with the section titles in the documentation.
Customizing Phone Settings
After adjusting the phone ringer type and volume settings, the phone must be left untouched for 20 seconds before the settings are saved to Flash. Once the settings are saved to Flash, they will be saved across a reboot. If the phone is not allowed to remain idle for 20 seconds after the ringer type and volume settings have been saved, the settings will not be saved across a phone reboot.
Obtaining Documentation
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco Connection Online
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•
•
•
–
–
You can e-mail questions about using CCO to cco-team@cisco.com.
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate and value your comments.
This document is to be used in conjunction with the Cisco SIP IP Phone 7960 Administrator Guide publication.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site 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. (0104R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)