Voice Mail Profile and Hunt list

[aalejo]

Somebody knows how to configure a voice mail profile to a hunt pilot/hunt list?. Looks like CUCM only uses the default voicemail profile for all hunt pilot  when sending the call to voicemail. from a hunt pilot after RNA or Busy on the pilot.

Thanks

[Jonathan Schulenberg]

Hunt Pilots do not have a oicemail call forward checkbox as Directory Numbers do. The No Coverage checkbox you see instead will use the Call Forward No Coverage condition on whatever DN was rining when the CFNA/CFB condition was hit. If that DN's No Coverage forward is set to voicemail the Voicemail Profile of that DN will be used.

If you want the Hunt Pilot to forward to directly to voicemail you need to specify the appropriate Voicemail Pilot number in the Destination field and apply a CSS that can reach it.

Please remember to rate helpful responses and identify helpful or correct answers.

[aalejo]

Had this issues on a customer deployment and test it later on the Lab. Find out that not the phone Voice mail profile on the line (that is part off the Hunt List - Hunt Group) is used , the default Voice mail profile is used ALWAYS.

CUCM version 8.5.

[Rob Huffman]

Hi there,

You are most correct my friend, the VM profile(s) of

any of the Line group members does not come into play here

What are you trying to accomplish with the use of a VM profile?

Maybe there is another way to configure what you need.

Cheers!

Rob

"May your heart always be joyful
May your song always be sung" - Bob Dylan

[aalejo]

Hi Rob

I was trying to send a call to a VM box/handler after a RNA/Busy on the hunt pilot / hunt list.

I was able to do it using the default VM profile and on the CUCM traces you will see that CUCM uses the default VM profile on the hunt pilot/hunt list.

I am trying to do the same using another mask of my choice not the default one.

Regards

Alex

[Rob Huffman]

Hi Alex,

Usually, if you are trying to route calls that come through via

a Hunt configuration to another Call Handler or mailbox number that is

not the same as the Hunt Pilot you would use an Alternate extension

if it's a standard mailbox and a Forwarded Routing Rule (in Connection)

if it's a Call Handler

So if the Hunt Pilot is 6000 and you want to route the FNA/Busy calls to

a mailbox at 5555 you would add 6000 as an Alternate extension under 5555

in Unity Connection.

If you wanted to route the 6000 FNA/Busy calls to a Call Handler at 4444 you

would set up a Forwarded Call Routing Rule to point to 4444 when forwarded calls

from 6000 hit Unity Connection.

You can't use VM Profiles as you've nicely noted.

Cheers!

Rob

"May your heart always be joyful
May your song always be sung" - Bob Dylan

[aalejo]

Hi Rob

The issue here is that CUCM uses the default Voice Mail Profile for any calls that go to a hunt pilot and forward to VoiceMail (RNA/Busy).

Also, there is no way to change that behavior

Regards

Alex

[Rob Huffman · Accepted solution]

Hi Alex,

We're in agreement here

If you want to apply a different VM profile for a Hunt Pilot you

can front-end the Pilot # with a CTI-RP and apply the VM profile

at that level.

So, if the Hunt Pilot is currently 7777 you can take the number

7777 and move it to a CTI-RP, put a new number like 6504 on

the Hunt Pilot. On the 7777 CTI-RP set the Forward All to the

number you use to replace the Hunt Pilot DN ...ie: 6504.

On the 7777 CTI-RP apply the required VM profile there.

I just tested this out and it works like a charm.

Cheers!

Rob

"May your heart always be joyful
May your song always be sung" - Bob Dylan

[aalejo]

Thats a good idea!

Thats bad that sometimes to fix a Cisco stuff you have to fix the world .

Thanks

Alex

[Rob Huffman]

Hi Alex,

Too true my friend

Cheers!

Rob

"May your heart always be joyful
May your song always be sung" - Bob Dylan