- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 06:07 AM - edited 03-19-2019 06:14 AM
All
We have CUCM 6.1(5)
I had configured a broadcast hunt group with BLF, dual line etc - fairly complex call routing. Customer wanted call pickup, which I configured and tested working. SInce then we ended up trashing the phone config (as it is a lab) attached to a production CUCM cluster and then recently rebuilt the lab phones. Now however, I cannot get notification working for call pickup.
I added the above as a bit of history, as now, I have stripped the call pickup configuration down this:
Two phones, single line on each
Call pickup group which is configured on the two phones, call pickup group has the following config:
Name:RPN_Test_BoF_PG
Number:5551011723
Notification policy:Audio and Visual Alert
Notification timer (seconds):6
Selected call pickup groups:5551011723
When I dial phone A, it rings as expected. However no visual or audio alert appears. If I ring phone A, then after a few seconds press the softkey pickup button on phone B - the call is pulled to phone B, and I can press the Answer button.
I have tried various combinations of Audio, Visual, Audio and Visual alert settings and Called party information etc, but nothing gives me an audio or visual alert........
Any ideas anyone?
Thanks in advance
Brian
Solved! Go to Solution.
- Labels:
-
UC Applications
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 06:21 AM
Hi
I once saw a bug where the notification didn't work if the partition of the pickup numbe rwas set to
Try putting it in a PT if it's not in one now, or putting it in
Aaron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 06:19 AM
What are the DNs configured like for notifications?
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 06:21 AM
Hi
I once saw a bug where the notification didn't work if the partition of the pickup numbe rwas set to
Try putting it in a PT if it's not in one now, or putting it in
Aaron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 06:50 AM
Thanks
Aaron, just spotted the same bug myself. I do not have the Cisco bug ID for it yet, but saw this:
http://www.routerdiscussions.com/viewtopic.php?f=4&t=2985
Removed the DN of the pickup group from its partition and it works now. Thanks everyone for looking......
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 07:00 AM
Hi Brian,
I was actually part of that thread from CSC
There are actually a couple of related bugs;
CSCsj38648 Bug Details | Bug #20 of 98 | < Previous | Next > |
---|
CM 6.0: Pickup Notification not working if different partition. | |
Symptom: Pickup notification is not working if pickup group is in different partition than phones. Pickup is working. Conditions: Phones are in one partition, pickup group in another but reachable from phones CSS. Workaround: Configure pickup group in same partition as phones. If dial plan does not allow: none | Status Fixed Severity 3 - moderate Last Modified In Last Year Product Cisco Unified Communications Manager (CallManager) Technology 1st Found-In 6.0(1.1000.37) Fixed-In 6.0(0.9901.308) 6.0(1.1101.5) 6.1(1.1000.11) |
CSCsl97189 Bug Details | Bug #74 of 98 | < Previous | Next > |
---|
Incorrect Call Pickup Notifications based on Partition and Timezone | ||
Symptom: 1. Call Pickup Notifications (audio and/or visual) do not work for any members in the Call Pickup Group. 2. Call Pickup Notification is being sent to devices which are in a timezone different to the monitored party. Conditions: 1. Call Pickup Group is associated with a partition. 2. Placing a Call Pickup Group in a Partition with timeschedule (TS) and timeperiod (TP) and not assigning the dependent devices to that partition. Workaround: 1. Change the Call Pickup partition to "none" 2. N/A Further Information: Fix for this will be available in 6.1.4. However, due to large scope of changes this fix cannot be ported back to any ES. Any install requiring this fix must upgrade to 6.1(4), 7.0(2), or later. | Status Fixed Severity 3 - moderate Last Modified In Last Year Product Cisco Unified Communications Manager (CallManager) Technology 1st Found-In 6.1(1) 6.1(2) 6.1(3) 7.0 Fixed-In 7.0(0.183) 7.0(0.167) 7.0(0.39700.81) 7.0(1.11000.2) 6.1(3.9901.149) 6.1(3.11) 6.1(3.12) 6.1(3.13) 6.1(3.9999.1) 6.1(3.14) 6.1(3.15) 6.1(3.16) 6.1(4.1000.10) | |
Related Bug Information
|
Cheers!
Rob
"Clocks go slow in a place of work
Minutes drag and the hours jerk"
-The Clash
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 07:12 AM
lol Rob
If only you had replied 9 minutes earlier, you would have been flagged with the right answer.....
Thanks for looking anyway, much appreciated!
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 07:27 AM
You can have more than one right answer I think :-)
Aaron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2013 07:31 AM
Hey Brian,
No worries my friend I just wanted to add my 2 cent$
here because I'm not allowed to @ home (just kidding!)
Cheers!
Rob
"Clocks go slow in a place of work
Minutes drag and the hours jerk"
-The Clash
