CUCM 14SU1 hunt group unity connection issue

[tomneary78]

Hi Group,

I'm running into an issue with a customer of mine specific to unity connection transferring to hunt pilots.  The issue did not exist in version 14.0, only popped up after we upgraded to SU1 this past summer.  We have some pseudo IVRs setup with unity connection providing a menu to the user, and some options being sent to hunt pilots with native queueing.  The issue we are seeing if an internal caller calls one of these departments, and the call gets redirected to unity connection, and the call is queued, the call is dropped.  Strange this is that it does not happen from callers from outside via CUBE/SIP Trunk.  I opened a TAC a few months ago and really got nowhere.  I was able to implement a workaround for the problem hunt group at the time, but now a new group is complaining.  Has anyone else seen a similar issue?

Thanks,

Tom

[Nithin Eluvathingal]

Can you explain a little more about the call flow, so that I can test this on my lab where I have 14.SU1.

[tomneary78]

Thanks for the assist here.  The simplest call flow was the one I came up with a workaround is this. 

Call initially is answered by a Unity Connection Call Handler.  If it is normal hours, it plays a blank greeting, and sends the call to the Hunt Pilot number with native queueing.  If all agents are busy, it should queue the call and play the queue announcement.  At this point the call is dropped.  This problem only happens on internal calls.  External calls via CUBE, don't experience the same issue.  I suspected a media resource issue, but the problem only surfaces after SU1.  It operated without issue for a full year. 

The workaround I did for this particular group, was bypass the initial Unity Connection call handler.  Since it was only being used for scheduling, it wasn't really necessary.  So if an internal caller calls a native queue hunt pilot, and no users are available, it queues the call and plays the appropriate announcements.