The user guide for the 7841 says the following about Call Waiting and multiple calls on the same line;
Respond to Call Waiting Notification Perform one of the following actions to answer a waiting call: Scroll to display the sessions if the call is on the same line but not visible.
However on a current rollout of some 7841s it's been observed that when a second call comes in on the primary line, after the call toast fades out there is no way to view the info about the waiting call. Pressing the up/down navigation buttons has no effect.
Am I misinterpreting the instructions in the User Guide or is this phone not doing what it is supposed to?
Call waiting Notification lets users receive a second incoming call on the same line without disconnecting the first call. When the second call arrives, the user receives a brief call-waiting indicator tone, which is configured with the Ring Setting (Phone Active) in the Directory Number Configuration window.
Configure call waiting in the Directory Number Configuration window in Cisco Unified Communications Manager Administration by setting the busy trigger (greater than 2) and maximum number of calls.
So if busy trigger is set to 2 (which is the default) you could be on an active call, a second call could come in and then once the call toast has faded out there's no way for the end user to retrieve the display of the waiting call? Does that not seem a bit odd?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...