When running CUCM 6.0(1a) Call Pickup notification worked as advertised. Phone_B and Phone_C are in PickupGroup_1. Phone_A calls Phone_B, after alerting timer expires Phone_C sees alert.
After upgrading to 6.1(1a) the Call Pickup notification no longer works. The Pickup function (softkey) works but there is no notification.
When looking at traces it appears that the CallManager PickupNotify subsystem is sending the notification to the IP address of the calling party (instead of the non-ringing phone). So, if the calling party came to a gateway PickupNotify sends the nalstring to the IP address of the gateway. If the calling party is an IP phone the PickupNotify sends the nalstring to the IP address of the calling phone.
I don't have a trace of "known good" to compare to but this is odd. And, of course, it doesn't work in 6.1(1a).
We noticed the same issue here. We upgraded from 4.2(3) to 6.1(1a) late this week, and I started getting calls about this feature not working... If needed, I will be glad to create traces when I get back to work Monday.
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...