Hunt Group Issue

Hello,
I am trying to set up a Hunt Group which hunts, top down, to four different extensions (A,B,C,D).
This is working as expected apart from one particular extenstion...C. When start or middle of the Line Group this extension gets skipped over completely even though the user is logged into their phone and direct calls to that extension get through fine. When C gets put to the end of the Hunt Group the call gets terminated rather than the extension ringing with a "Line Busy" message.
I have checked the Directory Number and Extension Mobility Profile settings of extension C against those that do work (A,B,D) and I believe everything is set the same...I can see no obvious reasons why C will not ring. I have also checked with the user that no DND/call forwards are set up. I have also created an entirely new Directory Number and associated it with user C's EM-Profile...the same thing happens.
Am I potentially missing something here? For the life of me cannot see why this is happening.
Thanks,
-David

Hi David.
If you create a Line Group with that user's extension only and create an Hunt List than an Hunt pilot, are you able to make that phone ring?
In you associate the same extension to a phisical phone, does it ring when in the Line group in subject?
Thanks
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"

Similar Messages

Broadcast hunt group issue

I have a broadcast huntgroup built that has 4 phones assigned to it. It has been working for a while now, but today all of the sudden only the first phone in the hunt group rings. I have verified that the line group is still set as a broadcast group and that all 4 phones are in the group too.

You minght want to reset the Hunt List and see if that help.
Dat Pham

Hunt Group Issue - DN being skipped over

Hello,
I am trying to set up a Hunt Group which hunts, top down, to four different extensions (A,B,C,D).
This is working as expected apart from one particular extenstion...C. When start or middle of the Line Group this extension gets skipped over completely even though the user is logged into their phone and direct calls to that extension get through fine. When C gets put to the end of the Hunt Group the call gets terminated rather than the extension ringing with a "Line Busy" message.
I have checked the Directory Number and Extension Mobility Profile settings of extension C against those that do work (A,B,D) and I believe everything is set the same...I can see no obvious reasons why C will not ring. I have also checked with the user that no DND/call forwards are set up. I have also created an entirely new Directory Number and associated it with user C's EM-Profile...the same thing happens.
Am I potentially missing something here? For the life of me cannot see why this is happening.
Thanks,
-David

David,
Two things come to mind..
1. Does the user have HLOG softkey? If so perhaps the user has accidentally logged out of the hunt group
2. Have you tried logout/login back to EM?
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"

# of Hunt groups associated with B-ACD and # Automated Attendants (AA) for UC560

This reference (from public site) states (3) AA and (10) Hunt groups
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps7293/reference_guide_c07-566560.html
This (harder to find document in supportforums) references (5) AA , but it does not reference (20) Hunt Groups. We understand from speaking with Cisco Partner Presales that the current firmware supports this, but we cannot find the published reference.
https://supportforums.cisco.com/docs/DOC-9656/

We are currently running 5 AA's on a 560 and have been doing so for a few months.
I cannot help with the hunt groups as we do not use them.
The 560 seems to support a bunch of features that can only be programmed using the CLI, I wish they would match the CCA up with these as it causes all sorts of issues if you do not remember what was configured using CLI vs CCA.
For instance our outgoing CLID was configured using the CLI as CCA only supports 15 entries where the CLI supports 100, which is great until someone opens the Outgoing CLID tab in the CCA and it over writes the CLI config.

Setting up Hunt Group using an extension number instead of a pilot number

Hi Guys,
I would like to set up a hunt group. My question is can I use a real extension number assigned to a phone to be a pilot number instead of creating a new pilot number.
The requirements are if no one is answering a call to an extension 1000 (extension 1000 is assigned to a user) it should be forwarded to 1001, 1002, 1003 and back to 1000. I was thinking of using 1000 as pilot number. Is that possible ?
Thanks Guys

Hi Guys,
Thank you very much for your suggestions. Here is what I have done:
With Manish's solution the call forwarding works upto the third phone then it got disengaged. Looks like there is a timer I need to increase so that the call will not time out. Could you please let me know which timer I have to adjust. I have checked the max forwards hops and they are set to 15-20 so don't think this is an issue.
With regard to Jamie's solution, I have created a separate partition and assigned same DN 1000 to it. It works great when I call from inside. However when I call it from outside using the full E164 number the call goes to 1000 then it just go to the voicemail of 1000 if not answered. I have removed the settings under DN page so that it will not go to voicemail. After doing this the phone with extension 1000 keeps ringing until it times out. Not sure where the issue is here.
I have given a suggestion to my customer to use a new pilot number with hunt groups. I have tested this as well. When I call it from outside the call goes to all the five phones and it just keep going into circle until someone answered and that's what I want. But when I call DN 1000 from inside it goes to all the five phones and when I reaches to the last phone configured under the line group member the call then just dropped out. Is there a way to fix this so that when someone just dial the extension number from inside all the phones keep ringing in circle manner and did not drop until someone has answered it.
Thanks a lot guys.
Regards

CSCth95017 - Configurable parameter on how callingparty is displayed for hunt groups.

Hello all,
The "fixed-in" versions for this bug are listed below;
Fixed in: (5)
9.0(0.98000.74),9.0(0.98000.21),8.6(4.98000.21)
8.6(2.21023.1),1.9(9.98000.16)
But the bug is related to firmware and the "fixed-in" versions look like CUCM versions;
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
Can anyone clarify the "fixed-in" versions for this bug and where the versions are available for download.
Cheers!
Rob
"Always movin' ahead and never lookin' back" - Springsteen

Hi Rob, The original documentation highlighted this as a phone issue. You have a good eye to catch this. The ultimate resolution was committed on the server side. I updated the bug Release-note to include more information about the fix. You will see that in Bug Toolking and Bug Search Tool in 24-48 hours. Looks like it was necessary to change the information CUCM was sending out in order for the phones to leverage that information. Here is what I added to the bug: New Service Parameter : "Display Hunt Pilot Name or DN for Hunt Group Calls When Alerting" Default Value : True ? Default behavior will be new behavior from 8.x . For customers who want the previous behavior of 7.x will have to set this parameter to false after upgrade. Call Processing Fix from SCCP and SIP Side : - For Hunt Pilot calls, CUCM will not send Hunt Pilot URI to in outgoing INVITE when this service parameter is false but internally CUCM still treats this call as Hunt pilot call so that we do not break other features. - For Hunt Pilot calls, CUCM will send the HP URI to phone when this SP is true. For the versions above: 9.0(0.98000.74) - this is an internal nightly build (.98xxx.). this *may* get it included in 9.0(1) 9.0(0.98000.21) - this is an internal nightly build (.98xxx.). this *may* get it included in 9.0(1) 8.6(4.98000.21) - this is an internal nightly build (.98xxx.). this *may* get it included in 8.6(5) 8.6(2.21023.1) - this gets it fixed in 8.6(2) engineering special branch commonly referred to as es23. TAC can provide this to you. This *may* get it included in the next 8.6.2su that gets posted to Cisco.com. 1.9(9.98000.16) - this appears to be a typo. Regards, Wes

Are Looping Hunt Groups a liability?

Over the years I've come across several requests for Hunt Groups that basically keep calls looping around until someone picks up. To the users these calls are so important that they don’t want them ending on a mailbox. However, I’ve heard a few times that this is not best practice because it could create all sort of issues. Is there any truth to this? And if so, what would be the recommended approach given the fact the call must keep ringing until someone picks up?
Thanks in advance for your help! It’s alway greatly appreciated.

Brian,
1. There is not a distintive ring option in CM. You could create a 2nd line on your user's phones and add those lines to the hunt. From there the user can select a different ring for the line (this is a local phone option for ring).
2. Setup alternate MWI on the group vmail box. Alternate I believe has a limit of 9. If you have more users than that then create a DN on each of their phones with the same # of the voicemail box. If that number is the original vmail pilot that is a CTI or other device then you wont be able to do that but you could create another DN and use a translation and the Multiple Tenant MWI option in CM service. Reply back if you need more detail.
3. MWI is turned off. The message stays in the group mailbox, there is no forwarding unless the user manually forwards it.
4. Not by default and I don't believe you have that option but not totally sure.
Please rate any helpful posts
Thanks
Fred

Temporal error in IPPhones 6921 with Hunt Group

Hi,
I have registered several IPPhones 6921 in cucm via wan, and trying to make a pickup Group, when I place a call, runs the hunt group, but when i try to pick up the call with Pickup Group softkey in the ipphones shows the message "temporal error" and fails.
I think this could be a bandwith issue, because end customer has a ADSL with only 200 Kb to upload between the two sites, although I have configurated region and Device Pool, still fails.
Any idea?
Regards!

Hi,
I have registered the ipphones in a cucm via WAN, i think that could be a bandwith issue because only happen when they are connected in the cucm, when I registered them locally in my CME all runs properly, so only have this weird behavior when are connected to CUCM via WAN.
Thanks!

Hunt Group Rings Fast Busy After First Member

I created a Hunt Group per Cisco documentation that included Line Group, Hunt List and Hunt Pilot. The Line Group is setup with RNA Reversion Timeout at 5, Distribution Algorithm - Top Down, Hunt Options all set to - Try next member, but do not go to next group. I have 4 extensions in the Line Group Members list.
The issue I am having is that if I call the pilot number, the first extension in the Line Group Members list rings three times then goes to fast busy and never gets to the second line in the Line Group Members list.
Currently running UCS 8.6.2.20000-2
Any input or thoughts is welcomed.

Hi Wes.
This is the normal behaviour of a line group.
A workaround you can use is create another Line Group with the same extensions and the same selection order, another Hunt List and a new pilot.
Than you can use CFW no answer from one pilot to the other so that you can reiterate the hunting between line groups
HTH
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"

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 not working in telephony-service srst

Cisco IOS Software, 3800 Software (C3825-IPVOICEK9-M), Version 12.4(24)T5, RELEASE SOFTWARE (fc3)
ROM: System Bootstrap, Version 12.4(13r)T10, RELEASE SOFTWARE (fc1)
show telephony-service
CONFIG (Version=7.1)
=====================
Version 7.1
Cisco Unified Communications Manager Express
For on-line documentation please see:
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/tsd_products_support_series_home.html
CUCM System version: 8.5.1.13900-5
Hi,
when the Call Manager fails and phones goes to telephony-service srst, phones get registered, can call out and receive calls. However when i try to ring the hunt group it fails with a beep sound. So i tried to create the hunt-group manually using the following commands, still no help. Could anyone please help on this issue.
dial-peer hunt 2
ephone-hunt 1 peer
pilot 8066700
list 8066721, 8066722
timeout 25, 25
hops 2
ephone-hunt 3 peer
pilot 8058600
list 8058609, 8058829
timeout 25, 25
hops 2
Thanks

Hi adcompto,
As you said based on the debugs, I can see that the number get translated(8058600) as below
Interface=0x67A07950, Interface Type=1, Destination=, Mode=0x0,
Call Params(Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
Called Number=8058600
then it is matching cucm dialpeer as below,
Apr 28 21:04:59.138: //705991/93F21854B47A/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=202
and finally getting disconnected with the cause code of 38(network out of order)
*Apr 28 21:05:02.142: //705994/93F21854B47A/CCAPI/cc_api_call_disconnected:
Cause Value=38, Interface=0x67A07950, Call Id=705994
do you know why it is hitting the cucm dialpeer instead ephonehunt? Also the all the numbers( 8066721, 8066722, 8058609, 8058829) in the hunt group are all registered and works fine, when I dial them directly. I will try your suggestion tomorrow by shutting down the cucm dialpeer and see how it works, in the meanwhile do you have any other suggestions.
Thanks for your help.
Barry

Hunt group type Set up with outside ext numbers ie Cell phones

Using CUCM 9.1
Is there a quick and easy way to create a hunt group type set up using outside (cell phone numbers)?
The scenario will be one (person who will be ON Call) using an internal DID that is forwarded to to a cell phone of the oncall person that particular week. If no answer it would forward to the next line group of 4 members and also try their cell phones. After this it would simply repeat the entire process. So far it looks like a solution may be possible with single line reach perhaps?
Any insight would be grealy appreciated.
Dave

Hello,
I set up something like this on CUCM 8.0 a couple of years ago.
I used the Mobile Connect feature as you suggest and it worked ok after some playing about with the timers.
The main problem was that there was no way for the remote users to log out of the hunt group. They could disable Mobile Connect using the IVR but the calls would still ring on their deskphones - if you log out of the phones (i.e. Extension Mobility) before leaving the office this problem should not occur.
The other issue was how long calls took to connect especially if a couple of people in the group did not answer. We actually recorded a message asking callers to be patient that was played when the call was first received (we were using UCCX to do the IVR and call transfer).
Hope this is of use.

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

Error 779 shows up in ip phone when transfer to a hunt group failed.

We have a CME (C2800NM-SPSERVICESK9-M), Version 12.4(24)T3. We have receptionist IP phone and a group of xx team phone setup. There is a hunt group for that group of xx team phones.
The receptionist phone is setup like this:
ephone-dn 102 dual-line
number 279          <<<<DN for receptionist
label xx
description 279
name xxx
corlist incoming SUPER
huntstop channel
hold-alert 30 originator
ephone 71
mac-address xxxx
username "x279" password xxx
provision-tag 279
type 7961 addon 1 7914 2 7914
button 1:102 2m49 3m52 4m40
button 5m7 6m105 7m114 8m11
button 9m43 10m83 11m66 12m74
button 13m48 14m38 15m54 16m104
button 17m88 18m53 19m69 20m37
button 21m41 22m80 23m60 24m56
button 25m70 26m100 27m72 28m92
button 29m71 30m110 31m61
The xx team's hunt pilot is DN 201:
ephone-hunt 20 longest-idle
pilot 201
list *, *, *, *, *, *, *, *, *, *, *, *
final 775                 <<<<this is voicemail number
timeout 15, 15, 15, 15, 15, 15, 15, 15, 15, 15, 15, 15
no-reg pilot
display-logout
1. If calling the reception phone (either from PSTN, or internally in the same site from a phone regiestered to the same CME),   the receptionist can pick the phone and talk, no problem. But if the receptionist transfers the call to ext. 201 (the pilot of hunt group). Intermittently, a few times a week, the call drops after being transferred. The receptionist sees 779 on her display, the callers hears a message saying "There was a technical problem". It is not possible for the receptionist to take the call back. The client has to recall and then on the 2nd try to call is transferred OK.
If the receptionist transfer the call to the DN of individual member of the hunt group, transfer is good.
2. If caller calls the pilot direclty (either from PSTN, or from internal phone in the same CME), the caller experienced the same issue as in the transfer case.
If caller calls the number of individual memeber of the hunt group, there is no problem.

Hi Billy
This is not supported. This support is being added for next release.
Thanks

Group Pickup feature doesnt work when add the phones to a hunt group in BE3k

Hi All,
I have a blast group with pilot number 300 , there are two members ext. 600 and ext.601 in that blast group. I added these two extensions to Call pickup group and enable "Audio and Visual Alert". I also have a spare phone ext. 602.
when I dialed between extensions ext.600,601 and 602 , group pick up feature is woking and I can see "call available pickup " on the phone screen and hear the audio alert. But when I dial the hunt group pilot number 300 from spare phone ext.602 , both ext.600 and ext. 601 are ringing but I can't see call pickup indicators on the screen. I also tried "Opickup' on the phone but got "no call available for pickup" message on the screen.
Any ideas why and how to fix this issue?

Hi Billy
This is not supported. This support is being added for next release.
Thanks

Hunt Group Issue

Similar Messages

Maybe you are looking for