UCCX or CUCM Hunt Groups

Does anyone have a checklist for supervisors or administrators to help them decide if a CUCM Hunt Group or UCCX is needed to service departmental call distribution?
-Users can login/logout of line groups with the HLog softkey.
-Calls can be sent off to a larger line group or hunt list (or voicemail) if Ring no answer or busy timers are exceeded.
?What about any reporting? Is there anyway to report Huntpilot or Line group member statistics, I have not found.
-In UCCX you can queue up calls and play MOH in queue, not available with Hunt Pilots.
Is anyone aware of any new advancements or outside the box ways to supplement ACD features (no, not the BACD.TCL script) for CUCM without UCCX?
thanks,
K

Good luck with that. This is a Cisco forum so the recommendation is always going to be for UCCX or UCCE over hunt groups. Money makes the world go around. ;-)
That said, in UCCE/CVP deployments I have configured some very small teams as a hunt group with the hunt pilot accessible from an option in the menu. Mainly for non-agent areas (distribution centers, repair department etc) where they like all the phones in the hunt group to ring.
Regards,
Geoff

Similar Messages

CVP 7.0(2) SIP RNA Timer with CUCM Hunt Group

I have a very simple ICM 7.5(9) script which simply assigns a call type then forwards to a label on CUCM 7.1(5), which is a hunt pilot containing a hunt list with 2 line groups...a circular LG with 10 members (RNA reversion timeout of 20 sec), followed by a broadcast LG with different 10 members. There is no CFNA/CFB forwarding set up on the hunt pilot.
In CVP, the SIP RNA timer is set on for this DN at 120 seconds, and I can see that get set in CVP logs (IP addresses and dialed numbers modified to protect customer data):
41762417: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} Matched 666333315555551111 to proxy.customer.uc
41762418: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} Using Local Static Route for sip:[email protected]
41762419: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} Matched 666333315555551111 to TimeoutMatcher: patterns like 66633331> will use RONA of 120
41762420: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} CALLGUID = 0B19E39A3CE811E28B7DA21700DE4950 LEGID = 0B19E39A3CE811E28B7DA21700DE4950-135458420897716680 - [OUTBOUND]: INVITE TO <sip:[email protected];transport=udp> FROM "--CVP" <sip:[email protected]:5060> EXPIRES[120] 100REL[Unsupported]
The hunt group then begins hunting, and can be answered normally. However, a CANCEL is sent at 60 seconds, and I am not sure why:
From the gateway:
2106715: Dec 3 20:24:29.095: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
CANCEL sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.100.1.5:5060;branch=z9hG4bK2C171513C0
From: "--CVP" <sip:[email protected]>;tag=20687DD0-DAF
To: <sip:[email protected]>
Date: Tue, 04 Dec 2012 01:23:29 GMT
Call-ID:
[email protected]
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1354584269
Reason: Q.850;cause=19
Content-Length: 0
From CUCM SDI traces:
12/03/2012 20:24:29.169 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.100.3.30 on port 43568 index 566129 with 389 bytes:
CANCEL sip:[email protected]:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.100.3.30:5060;branch=z9hG4bK51cac6f4-76fb29a5-78d5dd99-9a021233-1
Call-ID: [email protected]
From: "--CVP" <sip:[email protected]:5060>;tag=ds229f1b0f
To: <sip:[email protected];transport=udp>
CSeq: 1 CANCEL
Content-Length: 0
I am trying to determine which timer is limiting the hunt to 60 seconds.
Can anyone suggest where I might begin looking?
Thanks so much!!!

I've run into a similar problem recently with a CVP 8.5(1) SIP deployment and have found in the CVP documentation that the RNA Timeout is a range configurable between 5 and 60 seconds.
You can enter a larger value through OAMP on the Call Server-->SIP-->Advanced Configuration tab but when you Save and Deploy, it reverts back to the max of 60 seconds. The CVP help file indicates the 5-60 second range.
Regards,
Matt

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

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

Extending the Hunting time on a Hunt Group CUCM 8.5.1

Good afternoon. We are trying to implement a hunt group for our main switchboard. The scenario would be all calls to the home office come into a hunt pilot and then hunt, top down, to the main switchboard extension and then to a choice of 3 other devices that would be logged in. The problem is that we cannot get the hunt group to hunt longer than 1 minute. I have changed the RNA Reversion Timeout and with all the devices logged it, the call will only hunt until the 60 seconds has expired and then the call drops; 15 seconds at the RNA Reversion Timeout will get to all 4 devices - anything longer and the call drops before finishing the hunting process. From the information that I can find, a hunt group should "hunt" for up to 30 minutes (or so we read in the Hunt Pilot information). We're using a "Top Down" algorithm since we want all calls to always start at the switchboard directory number, and all of the Hunt Options are set to "Try Next member; then, try next group in Hunt List". The only place where we have indicated any time is on the Line Group - RNA Reversion Timeout. There are times where only the switchboard device may be logged into the hunt and we need to have that ring time at 60 seconds minimum for the call to be handled appropriately.
Is this a simple overlook on our part or are we limited in what we want to do?
Thanks for any insight that you can give us.
Cinde

Hi Cinde,
I just wanted to add a note to the excellent tips from my friend Aaron here (+5 "A")
The Maximum Hunt Timer is only leveraged when considering it in conjunction with the Call Forward settings on the Hunt Pilot config as noted here;
Maximum Hunt Timer
Enter a value (in seconds) that specifies the maximum time for hunting. Valid values specify 1 to 3600. The default value specifies 1800 seconds (30 minutes).
This timer cancels if either a hunt member answers the call or if the hunt list gets exhausted before the timer expires. If you do not specify a value for this timer, hunting continues until a hunt member answers or hunting exhausts. If neither event takes place, hunting continues for 30 minutes, after which the call gets taken for final treatment.
Note If hunting exceeds the number of hops that the Forward Maximum Hop Count service parameter specifies, hunting expires before the 30-minute maximum hunt timer value, and the caller receives a reorder tone.
In addition, Cisco Unified CM only uses the configuration for the Maximum Hunt Timer setting if you configure the Hunt Forward settings in the Hunt Pilot Configuration window.
From;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_5_1/ccmcfg/bccm-851-cm/b03htpil.html
There is an old bug that describes this in better detail;
Maximum Hunt Timer (MHT) description is unclear
CSCsg93573
Description
Symptom:
In the Hunt Pilot form, under Hunt Forward Settings, there is a field
called Maximum Hunt Timer (MHT). The description in the online help is misleading.
Currently, it conveys that the setting will be used when calling the Hunt Pilot
directly, which is not true. This setting is only used if Hunt Forward Settings
are configured.
So, to accomplish what you want you'll need to set up and link multiple Line Groups that contain the same 4 member DN's via the "Try next member,then try next Group in Hunt List" setting.
Let's say in our example the members of the first Line Group Called Main#1 are 3333,4444,5555 and 6666 then you create a second Line group called Main#2 that contains 3333,4444,5555 and 6666 and Main#3 that contains 3333,4444,5555 and 6666.
Include Main#1,Main#2 and Main#3 in the Hunt List; and Switch the rule on the first Line Group
to, Try next Member;then try next Group in Hunt List and Switch the rule on the Second Line
Group to, Try next Member;then try next Group in Hunt List.
This will then cycle through the Members 3333,4444,5555 and 6666 three complete times.
Cheers!
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

CUCM 9.0 Hunt-Group Phone( all phones in the hunt group) reset

Hi,
we have 7945 , 03 phones with attendanat consoles connected , all three phones get reset at the same time ,
this happens once each 4-5 days time, these three phones are conencted to LAN using two different switches ,
so it cannot be a problem with the switches , or conenctivity , ( other phones do not reset at that time , only these three phones which are in the same hunt group reset )
please advice us

Hi,
There is no option to check on your phone on who picked up the call in the pickup group. Please check the following link for the behavior of 89XX and 99XX IP phones
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/9971_9951_8961/10_0/english/userguide/P567_BK_UB293500_00_userguide-8961-9951-9971-10_0/P567_BK_UB293500_00_userguide-8961-9951-9971-10_0_chapter_0100.html
"Hunt group and multiparty calls show an icon to the right of the caller ID that differentiates the call from a normal call."
HTH
Manish

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 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.

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

AXL SQL Query user-extension- line group-hunt group mapping

Hi all
I want to take an export about user-extension- line group-hunt group mapping
Can somebody help me about it I have CUCM 9.1

There's a lot of table joins in that full mapping! I'll break it down into steps. When you say extension you need to bear in mind that a number and a device are two different things, and a user is associated to these things separately. I'll break it down into chunks.
User to Device:
SELECT enduser.userid, device.description FROM enduser, device, enduserdevicemap WHERE enduser.pkid = enduserdevicemap.fkenduser AND enduserdevicemap.fkdevice = device.pkid AND enduser.userid='FOO'
User to Directory Number:
SELECT enduser.userid, numplan.dnorpattern FROM enduser, numplan, endusernumplanmap WHERE enduser.pkid = endusernumplanmap.fkenduser AND endusernumplanmap.fknumplan = numplan.pkid AND enduser.userid='FOO'
Number to Hunt List:
SELECT numplan.dnorpattern, device.name FROM numplan, device, devicenumplanmap, typeproduct WHERE numplan.pkid = devicenumplanmap.fknumplan AND devicenumplanmap.fkdevice = device.pkid AND device.tkproduct = typeproduct.enum AND typeproduct.name = "Hunt List" AND numplan.dnorpattern='FOO'
Hunt List to Line Group
SELECT device.name, linegroup.name FROM device, routelist, linegroup WHERE device.pkid = routelist.fkdevice AND routelist.fklinegroup = linegroup.pkid AND device.name="FOO"
Line Group to Directory Number
SELECT linegroup.name, numplan.dnorpattern FROM linegroup, linegroupnumplanmap, numplan WHERE linegroup.pkid = linegroupnumplanmap.fklinegroup AND linegroupnumplanmap.fknumplan = numplan.pkid AND linegroup.name="FOO"
All of this (and more!) is fully documented in the CUCM Database Data Dictionary.
GTG
Please rate helpful posts.

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

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 with Pots lines in Call Manager

Hello all. I have a site with 12 Pots lines. It is all configured via Call Manager. We are using mgcp. I asked the telco to setup the numbers to hunt which they said they did but still when I call the main number second time it just rings and eventually get some voicemail that is not from the call manager. I think I need to setup Hunting in the Call Manager? Is that correct?
Line Group --> Add the extensions in here and set them up to hunt?
Hunt List --> Create a Hunt list and associate a Line Group with it?
Hunt Pilot --> I add all the extensions in here?

Let's take one step back. What are you trying to accomplish? I am assuming you want to market one number but have the ability to accept multiple calls on that number. If that is the case, having the telco set up a hunt is the way to go.
Beyond that, where do you want those calls from the PSTN to route? Are you wanting those calls to ring a hunt group on your side? If so, you will need to do the following:
     1. Configure a Line group. (Call Routing -> Route/Hunt -> Line Group) This is where you will be adding the extensions. You will also need to specify a distribution algorithm. The distribution algorith, is where you will be choosing how you want the extensions to ring. For instance, if you set the DA to broadcast, every extension in the line group will ring at the same time. Click Help --> this page, while you are in the line group configuration page to get more information about the settings you can modify and different algorithms you can use.
     2. Configure a Hunt List. (Call Routing -> Route/Hunt -> Hunt List) You will need to create a new Hunt List and add your line group to it. The hunt list is evaluated in a top down fashion. You can get pretty tricky with multiple line groups with different distribution algorithms in your hunt list, but if you just want something basic,just add the line group you made.
     3. Configure the Hunt Pilot. (Call Routing -> Route/Hunt -> Hunt Pilot) The hunt pilot will be the dialed number that triggers the hunt group. Make sure you select all the required settings. You will be selecting the hunt list you just made in this configuration page. Be sure to set a maximum hunt timer and final destination so that the calls do not just ring forever. You can get pretty granular with the settings in here. Reference the help --> this page document for more information.
     4. POINT THE FXO PORTS TO THE HUNT PILOT. This is very important. Calls to your analog lines will not trigger the hunt group unless you point the ports to the Hunt Pilot. If you are using MGCP/SCCP you will need to enter the hunt pilot in the "Attendant DN" field for EVERY FXO port. If you do not enter a value here, CUCM will have no idea what to do when the port rings. It will not answer the call if there is no value specified. This would explain why your calls were ending up with the telco voicemail service; CUCM was never answering the call.
If you completed the above steps correctly, you should be able to call the main number multiple times and have the calls go to a hunt group on your side, no matter which line the call ends up coming in on.
Let me know if you have any questions, this can be kind of tricky at first.
PS, if the calls were going to a voicemail that wasn't from Call Manager (Unity Connection) call the telco and have them remove voicemail service from the lines, assuming you have configured Unity Connection to handle that.
Hope this helps,
Dallan

Hunt Group Fallback

We are running CUCM v9 and are trying to set up the following configuration:
A heldesk hunt group which every phone in the company can log in and out of as they need
When a call comes into the helpdesk hunt group and is not answered for 20 seconds the call gets diverted to ALL phones in the company as a fallback from helpdeskThis call to ALL other phones cannot be a shared DN
Any ideas on how I can implement this? I've been racking my brain for hours. I first though of two separate hunt groups but realised that you can't log in and out of individual hunt groups, its either all or nothing. Then I was thinking group pickup??
Thanks

Create hunt pilot, point to new hunt group, in the hunt group point to 2 new line groups, where line group one points to all phones in longest idle or top down fashion, and the second is defined as broadcast.
On the hunt pilot setup call forwarding to the desired destination and setup the hunt timer as desired.
Chris

UCCX or CUCM Hunt Groups

Similar Messages

Maybe you are looking for