Finesse and broadcast hunt groups

Hi,
We have Cisco CCE with Finesse agent desktop. One of our ICM routing scripts is configured to send the call to a telephony hunt group label if no agents are available in Ready state.
The hunt group is a bradcast hunt group and all agent phones receive alert when a call to the hunt group label is placed. However when the call is ringing in Finesse, the caller ID actually lists all members of the hunt group. I can easily see that in the "Participants" XML tags on the Finesse server where multiple participants are listed.
Another problem is that when I answer the call from one Finesse agent desktop, all the other Finesse desktops show the same call as active on their screens with the option to End the call.
I know it is not a standard setup but we have a requirement to fall-back to telephony hunt groups if all agents are busy but an emergency call comes through.
Any suggestions how to fix this behavior?
Thanks!

I just checked this behaviour in My lab and it just works fine, you might be hitting some bug.
also what instead of broadcast, you use some other hunting mechanism. like longest idle or circular?
regards
Chintan

Similar Messages

Introducing broadcast hunt-group service for CME

Hello,
Due to popular demand I wrote this script for the purpose of ringing simultaneously more than one ephone without using shared lines. Like the broadcast hunt-group available for SIP phones, or in CCM.
http://pbevila.fastmail.fm/public/bcast.tcl
I haven't tested it completely, currently it works only when all the destinations are SCCP phones, although the objective is to allow mix and match of SCCP phones, SIP phones, pots DPs, etc.
Please try it and send any feedback here.

HI Paolo
I'm attempting to take advantage of your broadcast script you have produced. I'm having a few problems not getting the calls to broadcast. At the moment I'm just playing around with it on a standalone CME with 4 stand 7941 phones. I have used the following config and also shown the output:
application
service bcast flash:bcast.tcl
Jan 4 10:45:47.139: //-1//HIFS:/hifs_ifs_cb: hifs ifs file read succeeded. size=5571, url=flash:bcast.tcl
Jan 4 10:45:47.139: //-1//HIFS:/hifs_free_idata: hifs_free_idata: 0x457E9518
Jan 4 10:45:47.139: //-1//HIFS:/hifs_hold_idata: hifs_hold_idata: 0x457E9518
param destinations 201,202
Warning: parameter destinations has not been registered under bcast namespace
I have then used:
dial-peer voice 100 pots
description broadcast hunt-group
service bcast
incoming called-number 555
failing call flow:
7941(1) - > 555 -> CME-> Broadcast (phone2,Phone3)
When I try to dial 555 from one of the phones it just comes up with number unknown and fails to broadcast. I am also running with cme 3.3 but can upgrade if needed. Also I have no analogue lines just pure VOIP at the moment. I think its some thing to do with the dial-peer?

Broadcast Hunt Groups on UC520

Hello All,
Are Broadcast hunt groups supported on the UC520 in the latest release? Thanks
Jason

Hello Jason,
In Cisco Unified CME 4.3 and later versions you can use SCCP phones with the voice-hunt group
You can configure those hunt groups like this:
voice hunt-group X parallel
pilot XXXX
list XXX, XXX,
final XXX
timeout X
This type of hunt group (parallel) should ring all the phones at the same time.
Gabriel.

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 in CUCDM is ringing first extension in list when set to broadcast?

I'm working with CUCDM 8.1.3+er1.
We have a Hunt Group setup that rings 4 extensions through broadcast. Each of these 4 users have each others line appearances on their phones too.
Hunt Group example:
0 - User1
1 - User2
2 - User3
3 - User4
Problem is, when the hunt group is called the call will show up under User1 (or whoever is first on the list) and not actually everyone's line. I can change the order and the hunt group call will then ring only their line instead of broadcasting it out to the 4 users at the same time.
Is this a bug or a limitation on the platform? Where we cannot have users with line appearances of other users in the same hunt group...

Hi
This configuration sounds odd - why do you need a broadcast hunt group when a call to any extension will ring all the phones anyway due to the shared lines?
Aaron

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

Hunt group and 2911-CME SRST

Imagine this is (1) main hub with a Cisco CUBE 2900, 2 remote sites with Cisco 2911 CME-SRST. All connected via MPLS.
Goal:
If MPLS link or MPLS CE in remote site1 fails, I want to have *inbound* calls forwarded to the POTS line in the branch1.
VoIP Service provider does offer a feature which allow me to select target DIDs and have inbound calls forwarded to whichever number I specify.
Question:
Let's say there 20 people in the branch office1.
Can I setup a hunt group using Cisco 2911 CME and that single number which received the call start ringing the phone of all staff until we find someone to take call? Does CME and support hunt groups and this scenario?

Yes, CME supports various types of hunt groups.
However to have more than one phone ring at once, the best is to use a shared DN.

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

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

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

CCM 4.2 and Hunt Group pickup

Hello,
do someone know if the hunt group pickup feature is now enabled on the CCM 4.2?
Thanks in advance
Daniele

No. Call pickup is still not possible for hunted calls on 4.2. However, there is a new feature that may ease the pain of this. The "hlog" softkey offers the ability for afk users to "log out" of a hunt group while they are away. That way the call does not hunt to them in the first place. You can review this feature and other interesting things in the release notes: http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/prod_release_note09186a00805f1470.html

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

Finesse and broadcast hunt groups

Similar Messages

Maybe you are looking for