Hunt pilot > DN > voicemail is rolling to call handler, not mailbox 6.1

Answered Question
Oct 8th, 2009
User Badges:

I have a hunt pilot that needs 7 numbers then to voicemail. Since I can't roll to VM from hunt pilot I dropped the 7th number and told the hunt pilot to forward unanswered to the 7th, using personal preferences. It forwards fine, but after a no answer it spits to the default call handler, instead of the 7th extensions voicemailbox. Calling the 7th extension directly you get sent to its vmbox as you should. Unsure how to get the hunt pilot to roll to #7 and then hit its vmbox instead of the call handler.

Correct Answer by Rob Huffman about 7 years 5 months ago

....from previous page


So what many people do is to do one of two things (it sounds like #1 would work for you);


1. Make the Hunt Pilot DN an Alternate Extension on the DN for #7's mailbox so the Red MWI Lamp would be lit on their phone.


2. Add a second "shared" line to all Line Group members phones and then set the Hunt Pilot DN as an Alternate Extension on this new line so the Red MWI Lamp would be lit on all member phones.



In this example we are going to go with Method #2 and Light the MWI Lamp on all the phones within the Line Group when a Message is left for the group.


Lets say the Hunt Pilot number is 5000 and the newly created second line DN's on the Line Group member phones is 2355. Set the Hunt Pilot to Forward (CFNA) to the Unity Pilot #.


Create a mailbox for 2355 with 5000 as an Alternate Extension. When the call routes through to Unity via the Hunt Pilot No Answer Unity should see the CLID of 5000 which will then be connected to the Mailbox on 2355.



Then tweak the Message Lamp Setting in CCM for the second Line appearances;


For the second Line Setting on (each phone)-


Line Settings for this Device - Changes affect only this device


Message Waiting Lamp Policy - Light and Prompt


The RED Message Lamp will then work for these Second lines on each phone.



Hope this helps! Cheers!

Rob


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Rob Huffman Thu, 10/08/2009 - 10:11
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Anthony,


CUCM will work this way :)


You have to keep in mind that a call that has routed via the Hunt Pilot will always ignore the CFWD Settings on Hunt Group Member phones. The normal way to control this then is via the Hunt Group Logout of member phones combined with the Hunt Pilot level forward settings.


The following describes how the Call Forward settings on individual Hunt member phones are ignored when presented a call via the Hunt feature. Here is a clip;


Hunting and Call Forwarding


The concept of hunting differs from that of call forwarding. Hunting allows Cisco Unified Communications Manager to extend a call to one or more lists of numbers, where each such list can specify a hunting order that is chosen from a fixed set of algorithms. When a call extends to a hunt party from these lists and the party fails to answer or is busy, hunting resumes with the next hunt party. (The next hunt party varies depending on the current hunt algorithm.) ***Hunting thus ignores the Call Forward No Answer (CFNA), Call Forward Busy (CFB), or Call Forward All (CFA) settings for the attempted party (Line Group member Phones).



Cisco Unified Communications Manager offers the ability to redirect a call when hunting fails (that is, when hunting terminates without any hunt party answering, due either to exhausting the list of hunt numbers or to timing out). If used, this final redirection comprises a Call Forwarding action. Therefore, the Hunt Pilot Configuration window includes Call Forwarding configuration concepts that are similar to those found on the Directory Number Configuration window.


Example of Call Hunting


Although hunting differs from forwarding, hunting often originates as a call that gets forwarded to a hunt-pilot number. The call coverage feature extends hunting to allow final forwarding after hunting either exhausts or times out.


A typical call that invokes hunting can include the following phases:


The call hunts through provisioned hunt groups according to provisioned algorithms for each group. Hunting either succeeds (if a hunt party answers), exhausts (if all hunt parties are attempted, but none answer), or times out (if the time specified in the Maximum Hunt Timer runs out before all parties are attempted, and none of the parties that were attempted answer).


For the purpose of this example, we assume that hunting does not succeed.


If some form of final forwarding is configured, the call forwards to a next destination; otherwise, the call gets released.


Maximum Hunt Timer


The Maximum Hunt Timer field on the Hunt Pilot Configuration window allows the administrator to enter a value (in seconds) to limit the time for hunting through a hunt list. After the specified time lapses, if hunting has not succeeded, the call gets forwarded to a voice-messaging system, a specific dialed number, or some personal treatment (if configured), or the call gets released.



From this good doc;


http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmsys/a03rp.html#wp1078922




If the call goes unanswered or all member phones are logged out, then a Forward should be applied at the "Hunt Pilot" Level;


Hunt Forward Settings


Forward Hunt No Answer - When the call that is distributed through the hunt list is not answered in a specific time, this field specifies how to forward the call.


Destination This setting indicates the directory number to which calls are forwarded.


Forward Hunt Busy - When the call that is distributed through the hunt list is busy in a specific time, this field specifies how to forward the call.


Destination This setting indicates the directory number to which calls are forwarded.


Maximum Hunt Timer - Enter a value (in seconds) that specifies the maximum time for hunting.(Used in conjunction with Forward Hunt Busy)



....continued on next page

Correct Answer
Rob Huffman Thu, 10/08/2009 - 10:12
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

....from previous page


So what many people do is to do one of two things (it sounds like #1 would work for you);


1. Make the Hunt Pilot DN an Alternate Extension on the DN for #7's mailbox so the Red MWI Lamp would be lit on their phone.


2. Add a second "shared" line to all Line Group members phones and then set the Hunt Pilot DN as an Alternate Extension on this new line so the Red MWI Lamp would be lit on all member phones.



In this example we are going to go with Method #2 and Light the MWI Lamp on all the phones within the Line Group when a Message is left for the group.


Lets say the Hunt Pilot number is 5000 and the newly created second line DN's on the Line Group member phones is 2355. Set the Hunt Pilot to Forward (CFNA) to the Unity Pilot #.


Create a mailbox for 2355 with 5000 as an Alternate Extension. When the call routes through to Unity via the Hunt Pilot No Answer Unity should see the CLID of 5000 which will then be connected to the Mailbox on 2355.



Then tweak the Message Lamp Setting in CCM for the second Line appearances;


For the second Line Setting on (each phone)-


Line Settings for this Device - Changes affect only this device


Message Waiting Lamp Policy - Light and Prompt


The RED Message Lamp will then work for these Second lines on each phone.



Hope this helps! Cheers!

Rob


Actions

This Discussion