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?

Similar Messages

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.

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.

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

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

Should apple introduce a pre order service for existing customers?

Hi
After buying a large number of apple products I as wondering if Apple should start letting us loyal customers get first option on new devices, with iPad 3 not a million miles away I don't think it's right that people can buy them and them sell them on eBay for a profit when we miss out.
New customers are always good but it's people who buy 3 or 4 producs that keep it all going

This is a pre-order to be received on or around the 10th. These orders, though, will be filled before Feb 10 orders are filled, and are therefore more likely to have enough stock to satisfy demand.

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

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

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

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

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

Voice mail as last stop for hunt group

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

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

Hello. I began with the DPS. Is it possible to publish a magazine for a limited, specific target group? For example, in one department of a large company? Or to the responsible for various services? If so, how should I do? Thank you for your help.

Hello.
I began with the DPS. Is it possible to publish a magazine for a limited, specific target group? For example, in one department of a large company?
Or to the responsible for various services? If so, how should I do? Thank you for your help.

Short answer is yes.
Click the request for consultation link in Digital Publishing Suite Help | DPS pricing options to receive a price estimate for the DPS license your project.

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

Introducing broadcast hunt-group service for CME

Similar Messages

Maybe you are looking for