I had a 3.1(3a) callmanager cluster that was upgraded to 3.2(2C) service pack C. After the Upgrade we ran into all sorts of issues. The one outstanding issue is as follows.
Phones A & B have shared lines for DN's 1, 2, & 3. A call comes in from the PSTN to 1 and phone A picks it up. The call is then put on hold. From another DN a call is made and then released. When the person goes to pick up the holding call the line shows that it is in use. Phone A then calls phone B using DN 2 to see if they had picked up the line on hold. Phone B never picked up the holding call. The call to phone B from phone A shows that the call is sourcing from DN 3.
So the problem here is when you make a call the phone give the callmanager the wrong DN info. In this case the call DN 3 was choosen, but if DN 3 was on a call by another phone and they put their call on hold they would not be able to pick it back up because the CM thinks it is in use by Phone A.
I know this sounds confusing but any help or insite is appreciated.
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...