Hunt Call Queuing - Routing call to the messaging does not work properly

[celine.jeannotte]

Hello,

We set up the new feature with CUCM release 9.1 : Hunt Pilot Call Queuing.  There is a problem with the rerouting options available.  The Hunt Pilot number is 3852.

For example, we configure the parameter :

When Queue is full, route the call to this destination : 6200.

When maximum wait time is met, route the call to this destination : 6201.

When no hunt members answer, are logged in, or registered, route the call to this destination : 6202.

6200, 6201 and 6202 are CTI Route Points configured to forward all calls to the Messaging Pilot number and we created 3 System Call Handler with each extension.  The customer want to play different message.

When we dial 3852, the call is reroute to the messaging system but the integration does not work and we here the "opening greeting" instead of the Call handler greeting. 

I have tried to configure a voice mail profile in the CUCM with a MASK,  a direct routing rule in the CUC and a forwarded routing rule in the CUC but the result are always the same.

The only way to hear the Call handler greeting is to assign the 3852 (Hunt Pilot DN) as an extension in one of the System Call handler.  That means we could not play different message depends of the condition (queue is full, maximum wait time or no hunt members).

Does anyone has experienced this and can help me?

[Jaime Valencia]

Thats the same behavior you get for any call to a hunt pilot that you FW to another DN in the end.
You should be able to configure the call routing rules for that, use the port status monitor to see what info you get and configure the rules accordingly

Sent from Cisco Technical Support iPad App