Call Pickup Group Notification Failure - CM 6.1(2)

Answered Question
Jun 10th, 2008

Using CM 6.1(2) - Call Pickup Group Notification is not working. Both DN's are in the same partition as the call pickup group and the CCS on the device has the partition in it. Call comes in one DN (1275) and then follows the normal CFNA settings (in this case, rolling to another DN). The other DN that is part of the call pickup group never gets the notification (either visually or audio, on the phone or not). However, if the user preforms the call pickup anyway, it works just fine. It just the notification the is not working.

I've already adjusted the parameters under the System > Service Parameters > Call Manager and under the device settings > DN > "Call Pickup Group Audio Alert Setting(Phone Idle)"

Also, the Call Pickup Group Notification Timer in the Call Pickup Group Notification Settings is set at 1 - so I know it's not being beaten by the CFNA timer.

Also, the call to the DN is NOT set thru a hunt group. This isn't the hunt group call pickup bug everyone has issues with.

Any ideas?

I have this problem too.
0 votes
Correct Answer by Aaron Harrison about 8 years 5 months ago

Hi Brent/Ben

I've seen this problem in a couple of recent installations. It appears to be a bug with this release.

If you set the Route Partition of the Call Pickup Group to it will work.

Regards

Aaron

Please rate helpful posts...

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (8 ratings)
Loading.
Correct Answer
Aaron Harrison Fri, 06/13/2008 - 00:36

Hi Brent/Ben

I've seen this problem in a couple of recent installations. It appears to be a bug with this release.

If you set the Route Partition of the Call Pickup Group to it will work.

Regards

Aaron

Please rate helpful posts...

blcase Fri, 06/13/2008 - 07:56

Yep - worked for me too, nice going. Any chance you have a bug id for this?

Aaron Harrison Wed, 06/25/2008 - 10:59

Sure - I couldn't find a reference in the bug DB so had to launch a TAC case to get it... and it's still not publicly viewable.

CSCsm59305

Cisco did offer to knock up an ES patch for it but I'm sticking to the workaround and standard code unless a definate requirement to do otherwise comes up.

Regards

Aaron

Actions

This Discussion