Hunt group Callmanager 3.3(5)

Hi all
I have a problem creating a hunt group, more specifically hunt pilot number. When I create the hunt group and dial the hunt pilot number using the DDI I get a busy tone ?? Can anyone point in the right way of troubleshooting this ??
Thanks

Similar Messages

Call Pickup within a Hunt Group CallManager 5.1

I have a customer where we have several hunt groups configured. We also have Pickup Groups configured for each of these areas so that anyone within that group of users can pickup a call ringing on another phone. If someone dials a number directly that is within the pickup group, the call can be picked up from another phone in that group. However, if someone dials the hunt group number, other people within the pickup group cannot pickup the call and have to wait until the hunt works its way around to them. The DNs in the Pickup Group are the same as the DNs in the Hunt Group.
What I want to know is "should this work?". I think I understand why it isn't working, as the dialled number is not a number within the pickup group, as it's a hunt pilot, but is there any way of getting this to work?
Any help would be appreciated.
regards
Mark.

Hi Mark,
You are hitting this bug CSCsb12946 which prevents this feature from working. For various CCM versions there was this workaround but supposedly not for CCM 5.1 (see Fixed-In versions);
Set enterprise parameter (System->Enterprise Parameters->Cisco Support Use 1) Cisco Support Use 1 to CSCsb42763 (case sensitive)
This operation added listbox (Route Plan->Route/Hunt->Hunt Pilot->hunt pilot XXXX -> Call Pickup Group) Call Pickup Group.
From this doc;
http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K11612191
1.- Enter
CSCsb42763 (in mixed case) in the Enterprise Parameter 'Cisco Support
Use 1' under the new group 'Cisco Support use Only' and click update. Only the value
CSCsb42763 in this parameter can enable the configuration. Change the
value to anything else to disable this functionality.
2. Go to Hunt Pilot Configuration page and select a call pickup group from the Call
Pickup Group dropdown list and click update.
CSCsb42763
Call Pickup fails on Hunt List
Issue:
Call pickup fails for hunt list when call is CFA from Route Point in 4.1(2)ES41. This is not the designed functionality for this issue and will break the Call Pickup logic.
Workaround:
Use multiple shared lines & CFNA between each shared line.
Related Bugs
Call Pickup fails when ringing line list member
Symptom: Selecting PickUp or GPickUp does not pickup the call from any of the members of a line group. Condition: CM 4.x Workaround: None. Feature not supported. Further Problem Description: Defect CSCsa66224 may appear to have allowed this feature to work in earlier versions.
Call Pickup from line group member fails after es installed
Symptom: A call is CFNA to a hunt pilot/line group. The call can no longer be picked up. Conditions: Calls CFNA to a hunt pilot. 4.1(2)ES36. Workaround: None
1st Found-In
4.1(3)
4.1(2)
Fixed-In
4.2(0.35)
4.2(0.841)
4.2(1.15)
4.1(3)SR2
4.1(3)ES30
4.1(3)ES29
4.1(3)ES20
4.1(2)ES43.1
5.0(2.1000.3)
5.0(2.50.17)
5.0(1.99.33)
5.0(1.50.224)
5.0(1.20.84)
5.0(0.319)
4.2(1.2)
4.2(0.750)
4.2(0.24)
I did se this one Post from John regarding CCM 5.1.X,
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dddea7c/10#selected_message
Hope this helps!
Rob

CUCM 8.6 - Call Forward All Doesn't Work With DN In Hunt Group

Hello,
I'm trying to make a hunt group that's sole purpose is to dial out to our Help Desk member's cell phone (on-call after hours). The idea is that we want the hunt group to broadcast the call to the on-call engineers. Whoever picks up first takes the call.
At least that's the idea now. They may want to change that to - ring primary on-call cell phone, if no answer ring secondary on-call engineer.
The target cell phones will change every week and I wanted to give the supervisor a means of changing the numbers through the ccmuser page.
I created two DNs and placed them in a hunt group, each with call forward all to a cell phone number.
It seems that the hunt group ignores the call forward all setting and that is by design (https://supportforums.cisco.com/document/9126/cisco-callmanager-call-forward-all-cfa-does-not-work-if-line-hunt-group).
Does anyone else have any suggestions on how to accomplish this?

That's correct, what you're seeing is WAD, this topic has been discussed plenty of times before, the only option you have is SNR

SRST and Hunt Groups

SRST ver 3.4.
Is their a way to provide a sequential hunt group that will also provide forward on busy and foward no answer (based on a timeout value) to the next avialable extension in the group (a group being five or more members)? I have used the alias command in the past, but seems to be limited on what can be configured.
Thanks, J.

SRST does not have the hunt group feature, but Callmanager express has it.
In the new release of Callmanager express, CME 4.0, there is a feature called SRST fallback support using CME. You can use hunt groups in the SRST mode of CME.
Excerpts from CME admin guide.
When Cisco Unified SRST functionality is provided by Cisco Unified CME, provisioning of phones is automatic and most Cisco Unified CME features are available to the phones during periods of fallback, including hunt-groups, call park and access to Cisco Unity voice messaging services using SCCP protocol.
Check this link for more details
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_guide_chapter09186a00806a7fe8.html
Regards,
Anup

Hunt Groups to login

Can you create a hunt group for multiple users to login in CM5.x so as to use it like a helpdesk environment and you can track whether the user has logged in or out of the queue. Any help would be great

Hi Satu,
Just to add a note to the great tips from Pam and James (+5 points each folks :)
Don't feel stupid my friend, there are so many acronyms in this business it will make your head spin :)
ACD = Automatic Call Distribution (calls are distributed between active/logged-in Agents)
This term relates to Call centre applications like UCCX.
As to Hunt Group Login/Logout, sadly this feature is only available CCM 4.2 and CUCM 6.x/7.x with the Login/Logout of Hunt Groups feature (as James nicely noted). This is not available in CCM 4.1.3 or 5.x. Have a look;
Log Out of Hunt Groups
The Log Out of Hunt Groups feature allows phone users to log their phones out from receiving calls that get routed to directory numbers that belong to line groups to which the phone lines are associated. Regardless of the phone status, the phone rings normally for incoming calls that are not calls to the line group(s) that are associated with the phone. The phone provides a visual status of the login state, so the user can determine by looking at the phone whether they are logged in to their line group(s).
The Log Out of Hunt Groups feature also comprises the following components:
The HLog softkey allows a phone user to log a phone out of all line groups to which the phone directory numbers belong. Configure the HLog softkey in the Softkey Layout Configuration window. When the user presses the HLog softkey, the phone screen displays "Logged out of Hunt Group." When the user presses the HLog softkey again to log back in and receive hunt group calls, the "Logged out of Hunt Group" notification on the phone screen clears.
The Hunt Group Logoff Notification service parameter in the Clusterwide Parameters (Device - Phone) section of the Service Parameters Configuration window for the Cisco CallManager service must be configured to enable this feature.
Hunt Group Logoff Notification Service Parameter
The Hunt Group Logoff Notification service parameter in the Clusterwide Parameters (Device - Phone) section of the Service Parameters Configuration window for the Cisco CallManager service provides the option to turn audible ring tones on or off when calls that come in to a line group arrive at the phone and the current status of the phone is logoff. The default value specifies None, which causes the phone not to ring.
The Log Out of Hunt Groups feature, which is device-based, operates differently for non-shared lines and for shared lines.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmsys/a03rp.html#wp1091630
In the CCM 4.1.x and 5.x trains there is really not an equivilant feature. The best you can do is probably using AC Hunt :(
Hope this helps a little!
Rob

Hunt Group Shared Line question

Customer has the following call routing scenario:
CCM 4.2(3)
CTI Route Point is CFwdAll to a Hunt Pilot.
Hunt Pilot contains Hunt List containing a broadcast Hunt Group of 5 phones.
4 of these 5 phones each have the other phones' shared line appearances (ring disabled) so they can see if they are on the phone.
Issue - When incoming call hits the CTI RP, it then goes to the Hunt Pilot, Hunt List, then it "should" ring all the phones in the hunt group. But it only rings the very first DN in the Hunt Group and the DN of the phone that is not setup as a shared line on the other phones. The 4 phones that have each other's DNs setup as shared lines only see the call info popup on the LCD screen showing that the first DN is receiving the call, but their phone doesn't ring.
As a test, I switched the order of the hunt group DNs. After the switch, I realized that only the first number in the broadcast hunt group will ring. Kind of defeats the purpose of a broadcast hunt group. :(
I am starting to see where the issue may come from. If a phone has shared lines setup for DNs that are in a broadcast hunt group, each time a call comes in, then the phones would fill up the LCD with the call info for the 4 shared line DNs.
Any suggestions on allowing phones to be in a broadcast hunt group, and having shared line appearances to monitor the status of the other phones in the hunt group?
Thanks,
Kevin

Hi Kevin,
You are right on the money! Here is an odd tech note that applies to CCM 4.1.X , 4.2.X and 5.0.x. The reason I say odd is that it is hard to read or make sense of, but it is saying exactly what you have discovered.
Note: Do not put DNs that are shared lines in a line group that uses the Broadcast distribution algorithm. Cisco CallManager cannot display all DNs that are shared lines on devices where the DNs are configured as shared lines if the DNs are members of a line group that uses the Broadcast distribution algorithm.
From this doc;
Cisco CallManager Administration Guide, Release 4.1(3) Line Group Configuration
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803ed665.html#wp1036009
In the current environment I can't think of a good way to accomplish your goal of being able to monitor each others activity while using Broadcast hunting.
I know this doesn't help, but at least you know why it works the way it does. (and have some documentation)
Take care!
Rob

Hunt Group Queues

We are evaluating moving from an Avaya 8710 based enterprise PBX to a Cisco PBX. A sticking point we have come accross is how to do basic phone features supported by the Avaya system. A major one is the ability to queue calls in a hunt group. We have sites that have up to 3 or 4 hunt groups and if a call comes in and all members in the hunt group are not available then the call goes to Music on hold until the call can be picked up by the next available in the hunt group.
Is this really a limitation in Call Manager 5.x, 6.x or CME 4.3?

To answer your question about IPCC express, I know it used to be free with CallManager 4.x, not sure with 5.x and came with 5 licenses. But with IPCCx, you can do just about anything you want when it comes to queing, onhold, music, transfers, etc.
But from looking at the doc I sent you:
Understanding Call Queuing
You can configure a pilot point to support call queuing, so when a call comes to pilot point and all hunt groups members are busy, Cisco CallManager Attendant Console sends calls to a queue. While in the queue, the callers receive music on hold if you have chosen an audio source from the Network Hold Audio Source and the User Hold MOH Audio Source drop-down list boxes in the Device Pool window or the Pilot Point Configuration window. The attendants cannot view the queued calls. When a hunt group member becomes available, Cisco CallManager Attendant Console redirects the call to that hunt group member.
You enable queuing for a pilot point by checking the Queuing Enabled check box on the Pilot Point Configuration window. You must also enter a value in the Queue Size field and the Hold Time (in Seconds) field. The queue size specifies the number of calls that are allowed in the queue. If the queue is full, Cisco CallManager Attendant Console routes calls to the "always route" hunt group member that is specified on the Hunt Group Configuration window. If you do not specify an always route member, Cisco CallManager Attendant Console drops the call when the queue size limit is reached. The hold time specifies the maximum time (in seconds) that Cisco CallManager Attendant Console keeps a call in the queue. If the call is in the queue for longer than the "HoldTime," the call gets redirected to "AlwaysRoute" member. If the "AlwaysRoute" member is not configured, no action occurs.
This is saying that the CCM Attendant Console will take care of what you need. It's basically a big queing machine. You dont have to have a live person answer to start the que from what it looks like, just point the calls to the pilot number and let the server take control of the ques.
You can do this one ccm cluster, or hub and spoke in your case. Just remember, that if you are queing calls, you are tying up WAN bandwidth the more you que. But it may work out ok, depending on how much bandwidth you have.
You can get MOH streams off your local router at the remote site, so you are not streaming MOH over the WAN, so that should take care of itself.
Unity can act as a poor man's que. Basically you can have ccm hunt the groups, no one answer, go to Unity voicemail, play a message, transfer back to the hunt group, hunt the group, then possibly back to Unity to play a message, then take a message. (just using a different mailbox and a different pilot number)
Sometimes you have to get creative with these products to make them do what you want them to do. Out of the box, it's not always the exact feature you need, but you have to tweak it.
Most companies that use hunt groups, understand that they are basica in CCM until you port it to IPCC Express. Unity does do menu trees very well, multilevel voicemail, multiply extesnsions to one account, etc.
My best advice for you, get together with your local Cisco SE to go over the features you require and see how it can be done.
cheers!

Allowing CFA for a phone in a Hunt Group

I have CCM v5.13. Several users are members of a hunt group, and claim that they used to be able to call forward their phones and not receive any calls from the Hunt Pilot. I've made some changes to the Hunt Pilot, and ever since they say when they call forward their phones, it only works for calls made directly to their DID number , and that calls from the Hunt Pilot still ring on their phones.
I've researched this, and found Bug CSCec54565, which states that Cisco recognizes the issue, but has no plans to fix it. The recommended work around is to call the DID number directly, not through the Hunt Pilot. This doesn't work for my set up because these DID numbers are customer service lines which are published to the public.
I also found, in my research, solution # K00682545, which states that this Hunt Group is Working As Designed, and suggests the same work around, which is calling the DID directly.
My concern is the changes I made in the Hunt Pilot. I'm giving my users the benefit of the doubt when they say they used to be able to call forward all calls, whether they come from the Hunt Pilot or directly. I've set up a test Hunt Pilot, using our phones here in the shop, and I could duplicate their problem.
Can anyone think of a change I could have made in the Hunt Pilot settings that would bring this result, or are these users imaging that they could ever call forward all their incoming calls while belonging to a Hunt Group? Any ideas would be appreciated.

Hi Bethany,
CUCM Hunt Groups/Line Groups have worked this way since at least CCM 4.1(3) :) I never like to doubt users (not a great idea for job preservation) but...I don't see their claim being a valid one.
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).
From this good doc;
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmsys/a03rp.html#wp1078922
This is where the Hunt Group Logout comes into play. Sadly I don't think any CUCM 5.x versions support this feature, but the users can look forward to this in your next release (6.X or 7.x)
Log Out of Hunt Groups
The Log Out of Hunt Groups feature allows phone users to log their phones out from receiving calls that get routed to directory numbers that belong to line groups to which the phone lines are associated. Regardless of the phone status, the phone rings normally for incoming calls that are not calls to the line group(s) that are associated with the phone. The phone provides a visual status of the login state, so the user can determine by looking at the phone whether they are logged in to their line group(s).
The Log Out of Hunt Groups feature also comprises the following components:
â¢The HLog softkey allows a phone user to log a phone out of all line groups to which the phone directory numbers belong. Configure the HLog softkey in the Softkey Layout Configuration window. When the user presses the HLog softkey, the phone screen displays "Logged out of Hunt Group." When the user presses the HLog softkey again to log back in and receive hunt group calls, the "Logged out of Hunt Group" notification on the phone screen clears.
â¢The Hunt Group Logoff Notification service parameter in the Clusterwide Parameters (Device - Phone) section of the Service Parameters Configuration window for the Cisco CallManager service must be configured to enable this feature.
The Log Out of Hunt Groups feature, which is device-based, operates differently for non-shared lines and for shared lines.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a08ipph.html#wp1032225
Hope this helps!
Rob

Call transfer through Hunt group

Hi,
we have a call manager version 8.6 where we have mutiple huntgroups configured. Following is the call flow
PSTN callers call a DID number from outside which after the translation on the gateway, hits a hunt pilot number on call manager and eventually the call rings on all the line members of the line group. One any of the line group member picks up the call and tries to transfer the call to any internal or external number, we get the following error message on phone screen and transfer does not work
" External transfer Restricted"
Now this happens even if we dial the hunt pilot number internally from an iphone and then if one of the members tries to transfer to an internal extension or external number, we get the error message
More Information:
There are many other hunt groups on the same call manager server and tries to transfer the call same way as the non working one and it works for them
So i checked the difference. All the members of all the hunt groups are device profile logged into physical phone. The only difference was that working hunt group members are logged into 6921 phone where as non working users are logged into 7942 phones (sip firmare) and the profile are created for 9971 although we dont have any physical 9971 phone
So it seems that call transfer through hunt group does not work only if the members are logged into 7942 (sip) phones and works when they are logged into 6921 with 9971 Device profile
I hope its clear. Please let me know if its a known issue or limitation with 7942 phone. Any help will be appreciated

Try changing the Block Offnet to Offnet Transfer CallManager Service Parameter to False and test again. If it then works, we'll probably need CallManager traces to see why both numbers are getting marked as offnet.

7961GE Hunt Group ringing name

Our shop has been exclusively 7961Gs for 7 years now. We recently purchased some 7961GEs and are noticing that when a phone is part of a Hunt Group, the Hunt Group no longer displays on the inbound call. On the 7961Gs it would say the From: <Caller> For: <Hunt Group> .
Our Help Desk personnel love the 1Gbit speed, but hate not knowing if the incoming call is for them or the Help Desk.
Any help is much appreciated!!
Thank you,
--Whammer

Hi Whammer,
I'm guessing the new 7961GE's are running a pre - 9.0 firmware;
It sounds like this bug
CSCth95017 - Configurable parameter on how callingparty is displayed for hunt groups.
Description
Symptom:
As of phone load 9.x and higher, calls to a hunt pilot show the following format for the calling party on the ringing phone.
From 'Calling Party Name' for 'hunt pilot DN'
i.e. From John Doe for XXXX
The previous format was
From 'Calling Party Name' ('Calling Party Number')
i.e. From John Doe (XXX-XXX-XXXX)
Need a configurable parameter to change the format to the previous format if the customer desires.
Conditions:
Occurs on phone loads 9.0(x) and above.
Workaround:
Downgrade to 8.4.x
Details
1st Found-in:                          (1)
8.6(2)
More
Less
Status:
Fixed
Last Modified:
Mar 11,2012
Known Affected Versions:
More
Less
Fixed-in:                          (3)
9.0(0.98000.74), 9.0(0.98000.21), 8.6(2.21023.1)
More
Less
Product:
Cisco Unified Communications Manager (CallManager)
Platform:
Dependent
Severity:
2 - severe
Customer Reported:                          (26)
Cheers!
Rob

Extension not ringing in hunt group

Callmanager 8 environment (2 subs, 1 pub). There are four extensions in a hunt group and one of them stopped ringing today when you dial the hunt pilot. No recent changes to CUCM were made prior to this occurring.
I have tried the following:
1) Removed the extension from line group, reset hunt list, added it back to the hunt list and reset hunt list again.
2) Had the user unplug his phone and plug it back in to force a restart.
3) Remote-reset the phone from CUCM
4) Deleted the hunt pilot, list, and line group and rebuilt them then reset the hunt list
5) Deleted the phone from CUCM and reprogrammed it then reset the hunt list
6) Replaced the phone with a brand new phone and reset the hunt list
I can direct dial the phone extension and if someone forwards their phone to this extension it rings as well. Any ideas would be appreciated.
Thanks
Matt

All,
I just got confirmation that the hunt group is now working. Although I cannot say for sure which changes actually fixed the problem it was some combination of the following:
1) Removed unassociated Line 5 instance of the extension (found in Route Plan Report)
2) Restarted all 3 CUCM servers (per recommendation from a Cisco contractor we worked with last night)
3) Changed RNA settings from 25 to 10 seconds
4) Disabled forwarding of 2 other extensions in the line group
5) Unchecked the "logged into hunt group" box, reset the phone, applied the setting again, reset the phone again
Thank you for everyone's help, much appreciated.
Matt

CCX using Place Call to hunt group. Unable to determine who answered

I'm trying to use the CCX to place a call to a CUCM hunt group and then once the answered, determine which member of the hunt group answered the call.
I have used several of the Get Info steps, including:
Get Call Contact Info
Get Enterprise Call Info
Get Contact Info
However, all of those steps always just report back the CUCM hunt pilot number, instead of the actual line group member who answered the call. Can anyone think of a way to determine the extension of the line group member that answered the call ?
If it matters, I am using CCX 9.0.2su1

I lack a system to test this on at the moment but perhaps try this CUCM Service Parameter. The question is whether CTI Manager will follow this logic or if this is only respected by the CDR flat file export.
Show Line Group Member DN in finalCalledPartyNumber CDR Field
This parameter determines whether the the finalCalledPartyNumber field in call detail records (CDR) shows the directory number (DN) of the line group member who answered the call or the hunt pilot DN. Valid values specify True (the finalCalledPartyNumber in CDRs will show the DN of the phone that answered the call) or False (the finalCalledPartyNumber in CDRs will show the hunt pilot DN). This parameter applies only to basic calls routed through a hunt list without feature interaction such as transfer, conference, call park, and so on. If a feature is involved in the call, then the hunt pilot DN will show in the finalCalledPartyNumber field regardless of the setting in this parameter. This parameter does not apply to Cisco CallManager Attendant Console.
This is a required field.
Default: False

Hunt Group and Voice Mail - How?

Hello,
We are setting up a Hunt Group (Line Group, Hunt List, Hunt Pilot) for call distribution. We don?t want to use the Attendant console for this, we just want the calls distributed. We need to send some calls and broadcast them to different phones. We have it working but we have a need that if no one answers to send the call to voicemail.
The way we have it configured right now?
Line Group:
Broadcast Distribution
2 Lines ? Client Phone Lines
Hunt List:
Line Group Above
Hunt Pilot:
Number & Information Configured
Hunt List Above
What we planned on doing was to take and add a second line group with a single number that is forwarded to voicemail. Then in the hunt list, if no one answers the fist group, go to the second. The problem is, CTI Ports and CTI Route Points don?t seem to be able to be added to the Line Group.
Someone suggested that I add a ?fake? phone and forward the line to voicemail. I tried that and when I call that number it goes to voicemail but when I add it to the Line Group it rings fast busy when it rolls to it.
Any ideas?

I did understand you do not want the attendant console, which is why I said similar but using AC.
The key thing in my earlier reply is that the last member of my hunt group is another CTI routepoint with another DN which is the actual directory number I use in Unity as an alternate extension, but it might be that this does not work for you.
For your case it might be something like:
On the xisting CTI routepoint configure the forward no answer to VM (this works today, correct?)
Then add another CTI route point to your hunt list and configure that CTI route point with forward all to VM.
Then setup Unity with the DN for the first CTI route point and add the DN of the second CTI route point as an alternate extension.
That way I believe it will go to VM directly when no huntgroup members are available, and go to VM if no answer.
Again, this works for me, with the only difference my line group contains AC users and is not broadcast, but the principle would be the same I guess.
But I might be misunderstanding what you are trying to achieve. If so, I am sorry for misunderstanding ;-)
Thanks,
Leo

Voice mail as last stop for hunt group

Hello:
We have no ACD ability, so I have a hunt group set up with 3 extensions (one each as second line on each of 3 phones). If no one is available on any of the hunt extensions, I want it to go to a shared voice mail box.
Can anyone help me know if this is do-able and how (nothing I've tried has worked!). Using CM 6.1/Unity 5.0
Thank you,
Linda

Hi Linda,
This is most possible :) I'm going to add a touch to the great info from Tere (+5 points for this Tere)
In this example we are going to do what you are trying to do as well as Light the MWI Lamp on the phones within the Line Group when a Message is left for the group.
Lets say the Hunt Pilot number is 5000 and one of the second line DN's on the Line Group member phones is 2355. Set the Hunt Pilot to Forward (CFNA) to the Unity Pilot #.
If you don't use a Routing Rule as nicely suggested by Tere you can 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. This will take care of one of the Line Group Member phones but we want to light the Lamp on the second and third phone as well :)
Try setting the the DN's of the other two Line Group members as Alternate MWI's (in Unity) as well;
Setting Up Alternate MWIs for Extensions on the Same Phone System
Cisco Unity can activate alternate MWIs for extensions on the same phone system. Note that depending on the phones and phone systems, some additional phone system programming may be necessary. Refer to the installation guide for the phone system.
To enable alternate MWIs for extensions on the same phone system, do the following procedure for each subscriber who needs alternate MWIs.
To Set Up Alternate MWIs for Extensions on the Same Phone System
Step 1 In the Cisco Unity Administrator, go to the applicable Subscribers > Subscribers > Messages page.
Step 2 Confirm that the Use MWI for Message Notification check box is checked.
Step 3 Click the Add button located beneath the MWI Extensions table to add a row to the table. By default, the first row in the table contains an "X" to indicate the primary extension assigned to a subscriber. If you want one more extension and do not need to activate the MWI on the primary extension, you can also modify the first row.
Step 4 Enter the applicable extension in the Extension field of the table. MWIs are automatically enabled for all rows in the table. When entering characters in the MWI Extensions table, consider the following:
â¢Enter digits 0 through 9. Do not use spaces, dashes, or parentheses.
â¢Enter , (comma) to insert a one-second pause.
â¢Enter # and * to correspond to the # and * keys on the phone.
Step 5 Click the Save icon.
Step 6 Repeat Step 3 through Step 5 as necessary.
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/401/integration/guide/c50acu4x.html#wp1808513
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!
Rob

CCME Call Forward from one Hunt Group to another Hunt Group Failure

Hi I have a couple of hungroups in Cisco Call Manager Express. I am trying to configure a Call Forward no answer from one hunt group to another. Does anybody know if this is possible? If so, is there a config available? Here is my config, but it is not working.
Thanks,
Derek
voice hunt-group 20 parallel
final 2290
list 2201,2251,2252
timeout 30
pilot 2209

Hi Derek,
This is supported with the restriction shown below;
final number
Router(config-voice-hunt-group)# final 8888
Defines the last extension in a voice hunt group.
If a final number in one hunt group is configured as a pilot number of another hunt group, the pilot number of the first hunt group cannot be configured as a final number in any other hunt group.
From;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm/cmecover.html#72373
Cheers!
Rob

Hunt group Callmanager 3.3(5)

Similar Messages

Maybe you are looking for