CUCM 10.5.1 - Hunt Pilot Fwd Hunt No Answer - unable to send call to Unity

[Yort Mantup]

Hello, Just found after a recent upgrade to 10.5.1 that in a Hunt Pilot Configuration under the Hunt Cal Treatment Settings I am not able to send a call a Unity Mailbox. Prior to the upgrade the HP was configured to Fwd busy and no answer calls to *52436 which is a customer care mailbox. I have always added the * at the beginning in the past with no issue. What is happening now is it is sending the call to the UnityConnection Messaging System greeting. We are still on CUC 8.5 (SU4). Anyone know a cause / reason this no longer works in 10.5?

[Wilson Samuel]

Do you have a Route Pattern / Translation Pattern starting with * ?

Also, you could use the  Port Status Monitoring  and see what is actually happening once the call has been received by UCXN

http://ciscounitytools.com/Applications/CxN/PortStatusMonitorCUC7x/PortStatusMonitorCUC7x.html

HTH

[Yort Mantup]

I do not have a RP or xlation pattern starting with *?  

[Wilson Samuel]

So, can you from a phone dial *52436 and hit the voicemail box?

If not, I believe you will required a Route Pattern with the same config.

Currently I think the system is hitting the voicemail with the calling number as something else and you are getting the Default  greeting.

[Yort Mantup]

I can dial *52436 and hit the vm box. .  I do have a CTI RP configured (Transfer2VM).  Line 1 is configured as *xxxxx and set to fwd all to vm.  I also have a voicemail profile in CUCM called Transfer2VM configured with a voice mail box mask of xxxxx.   

[Mohammed al Baqari]

Why don't you keep the voicemail box mask empty. Currently, it is stripping the * from the RDN.