Old AC hunt groups vs. post CCM4.X line groups

This is old gripe I have with CCM 4.X and I want to know what others think about it.
From very early versions CCM has had the AC hunt groups that had the neat feature of being able to specify AC usernames and line #s as hunt group members as well as DNs as hunt group members. You could mix and match for robust scenarios.
Starting with version 4.0 line group/hunt list/hunt pilot was introduced. Also the "busy trigger" for DNs was introduced.
The new LG/HL/HP model introduced a much better feature set for hunting. It also observes the "busy trigger" such that if a person is on a single phone call and his/her DN is configured with a busy trigger of 2, the call will still hunt to that user.
Problem 1: The old AC hunt group does not observe the busy trigger. So if I have a DN with a busy trigger of 6 for a switchboard person, the AC based hunt group will consider that line busy and hunt past it with only 1 call on the line.
Problem 2:The new model of LG/HL/HP DOES observes the busy trigger but does not offer the flexability of adding AC user and line # as a line group member.
Conclusion: Each model has features the other needs. This should be reconciled.
Thoughts?

Same thing happened to me with a cataylst driver on my laptop. Hangs forever. I had just updated my system about a day before I applied this update, and the kernel upgrade definitely wasn't the culprit. I get a console login on my laptop, but whenever I startx it'll just hang forever and not respond to any input other than holding down the power button. Everything was working fine with the kernel, but then the last update, which included
*libxcb
*xcb-proto
*xcb-util
*mlocate
*libx11
*xorg-server
*xf86-input-evdev
*flac
*hal-info
Shared between my two systems (one of which is my desktop, with a nvidia graphics chip and the nvidia proprietary drivers).
I tried downgrading x-server and all the libs that were related to X, but that only broke dbus.
I'm afraid to reboot my desktop now...
Last edited by Subject-17 (2009-08-02 09:01:18)

Similar Messages

Hunt-group description on CME 4.0(3)

Hi all,
I set up a CME with release 12.4(4)XC4 with 3 hunt-group. See config:
ephone-hunt 1 sequential
pilot <omitted>
list 105, 104, 103, 102, 101
max-timeout 120
timeout 10, 10, 10, 10, 10
statistics collect
description PostOperatore
ephone-hunt 2 longest-idle
pilot <omitted>
list 102, 103
timeout 10, 10
statistics collect
description Numero_Verde
display-logout All LogOUT
ephone-hunt 10 longest-idle
pilot <omitted>
list 151, 152, 153, 154, 155, 156, 157
timeout 11, 11, 11, 11, 11, 11, 11
statistics collect
description Gruppo_SDH
You can see that in group 1 and 2 there are 2 ephone-dn (102 and 103).
I need that a description can be added to "phone displays" to provide hunt group information associated with ringing and answered calls.
for example: I call the pilot number of hunt-group 2, and the display of telephone with number 102 or 103 show, for example, the pilot telephone number.
In the command reference, this is documented with description command but it seems doesn't work. The telephone are 7912 and 7940.
Any idea?
thanks
Diego

Diego,
The description under ephone-hunt should only for documentation purpose. I think what you can possibly do here is to add two directory entries for each hunt pilot with the appropriate nmaes PostOperatore and Numero_Verde. Under telephony-service give the command "Service dnis dir-lookup". Based on the number the Original called party dialed, you should get a display name at the bottom of the LCD screen of a 7940 or 7960 showing the name of the original called number. I havent tested this with hunt groups. Just an idea. Let me know if that works by rating the posts.
PS: Make note of what changes you make, in case you need to revert back. Also take a back up of your old configs.

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.

Lync RSG Hunt Group not working as expected, not getting calls on lync clients

I have created an Hunt Group in Lync. When i dial the number i do get the welcome message but after that it does not get forwarded to the test user which is configured in the Group. (Created a Queue and selected the group here and assigned this to the workflow)
Error on Lync report:
Request: BYE Response: 200
Diagnostic ID: 26029 Category: Unexpected
Component: Response Group application
Reason:
Call is disconnected because of invalid configuration.
Description:
Call is disconnected because of invalid configuration.
Error in Event Viewer:
The workflow runtime encountered a critical error.
Failure occurrences: 8, since 4/17/2012 7:47:14 AM.
The last encountered error was from a workflow with the display name: TestRG, the URI: sip:[email protected], and the GUID: 810c628c-d0c5-4b31-b8d5-f61595def5b0
Suhas

HI,
Do you deploy standard lync server or enterprise lync server?
If enterprise lync server, please log in SQL server and search the rgsdyn--dbo.ActiveFEInstance. Please check you can find the FE server FQDN and the port 8404 in this table.
Please running the Lync server logging tool on the FE server to find why the Response Group can not transfer the calls to the agent.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

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

Hunt Groups and Voicemail

Was not sure if this was the right group to post these questions. I believe that these will be super easy for this group, and I want to double check my thinking against you guys. So, here they are.
If we elect to use a BROADCAST type of hunt group in some of our departments (all phones in the hunt group ring simultaneously when a call is directed to the group) and then direct that call to a DEPARTMENTAL VOICE MAIL BOX in a BNA condition:
1. Can the call ring with a unique ring that those in the hunt group can identify as different from a call that is directed specifically to their personal extension?
2. If the call to the hunt group ends up in the departmental HUNT GROUP VOICE MAIL BOX, will all phones in the hunt group receive notification that a message exists in the GROUP voice mail box?
3. If yes to 2 above, when any one individual in the group dials in to the group box and listens to the message, are all message waiting indicators subsequently turned off and does the person who responded to the message then become the owner of the message in his personal mail box?
Additional questions not related to hunt groups:
4. Do internal station to station calls ring with a special tone that differentiates them from external inbound calls?

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

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

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"

Hunt group question

We have a customer who is currently set-up in the following manner: All external calls ring a receptionist. If she is busy or not available, the call hunts to another user and so on. There are currently five (5) users set-up like this. These users all have a button on their existing phones labeled Available. When this button is inactive (not pushed), they are in the incoming calls hunt group. When this button is active (pushed), the user is no longer available to receive calls from this hunt group. They can still make and receive calls to their internal extensions.
Short of installing IPCC, how can I mimic this functionality?
Its easy enough to set-up a hunt group, but I dont know of a way to take the extensions out of availability for the hunt group when the users dont want to take these calls but still want to receive internal calls made to their extensions.
Thanks in advance for your assistance!
Chris

Chris,
You can accomplish this with Attendant Console. The users would have a piece of software on their PC that controls their availability. Please see the following link for details.
http://www.cisco.com/en/US/products/sw/voicesw/ps555/index.html
http://www.cisco.com/en/US/products/sw/voicesw/ps555/products_installation_and_configuration_guide09186a0080176f6e.html
Hope this helps. If so, please rate the post.
Brandon

Hunt Group stops forwarding after setting up forwarding.

Hi!
I am having a problem with a hunt pilot after setting up forwarding.
The original setup is this:
Hunt pilot pointing to a Hunt list with two line groups. The first Line Group
are the Operator lines, that are set up in a Device Profile with extension
mobility, to allow log on/log off fo the user. The second Line group are the
guard lines in normal phones, which take calls after operators log off.
So, the setup is like this:
HUNT PILOT
HUNT GROUP
LINE GROUP 1
Operator Line 1
Operator Line 2
Operator Line n
LINE GROUP 2
Guard Line 1
Guard Line 2
Guard Line n
I was asked to make the calls that reach the Guard lines able to be picked up
from any phone. Broadcast as hunt algorithm is not an option.
So, I removed the Line Group 2 from the Hunt Group, set up the Hunt FNA and FB
to the first Guard Line, and the Max Hunt timer to 240 secs.
The, I set the CFNA/FB for each guard line to the next line, and put all the
Guard Lines in the same call pickp group.
After I did that, all calls are forwarded directly to the guard lines, skipping
the hunt group entirely! So I had to do a rollback.
Is this expected behaviour? What should I do different?
Regards,
Ariel

I forgot to add that this is in a CCM4.1(3)

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

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

Can't configure hunt group voicemail unavailable or busy msg

I have set up hunt group voicemail button on one of the phones. I can login and set up the new password, but when I get to the stage of recording the unavailable voicemail. It hangs up straight away with call end on display with out giving time for the recording.
I have tried to dial the voicemail hunt extension it does the same thing.

Hi Lap,
Is it the first time to record unavailable greeting for this huntgroup voice mail box? If not, can you hear the old unavailable greeting? Did you try with a different hunt group? You got the same issue? Do you have such issue with the individual voice mail box? Were you able to record the voice mail box name before unavailable greeting for this hunt group?
Best regards,
Wendy Yang

Old AC hunt groups vs. post CCM4.X line groups

Similar Messages

Maybe you are looking for