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

Similar Messages

Can I configure a 79xx Phone with two busy trigger using UCCE 8.5?

Hi, my name is Eric and I've some doubts to configure my Phones. First of all, I will explain my environment below:
- UCCE 8.5
- CM 8.5
- CVP 8.0
I would like to know if it's supported if I configure a 79xx Phone with 2 busy triggers configuration, because the customer would like to the agent's phone receive two calls per line.
Thank you very much.

Eric,
No, this is not supported and stated as such in cisco docs.
Customer will need to designate separate DN for ACD calls and separate DN for DID/personal calls.
HTH,
Chris

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

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

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

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

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

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

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

CCME hunting and voicemail from external pstn

Hi,
I have setup a small hunt group with 2 extensions 300, 301
ephone-hunt 1 sequential
pilot 700
list 300, 302
final 300
preference 0 secondary 7
timeout 10, 10
I have voicemail setup on extension 300
This works fine internal for voicemail when I dial the pilot number I get the voicemail of extenstion 300
When I apply an external DDI\pstn number using secondary number to the huntgroup it does not connect to the voicemail that I have setup on extenstion 300.
ephone-hunt 1 sequential
pilot 700 secondary xxxxxxxxxx
list 300, 302
final 300
preference 0 secondary 7
timeout 10, 10
Is there any way I can get this huntgroup to connect to voicemail from the pilot number on external number
Thanks in advance

Hi Conor,
I think the problem here is that the VM system sees the Hunt Pilot # rather than 300 once the call hits VM.
Can you try setting up the Pilot# xxxxxxxxxx as an Alternate Extension under 300?
It is possible to have up to two numbers in the same Cisco Unity Express (CUE) User profile. Configure the first number as the Cisco Unity Express User Primary Extension, and the other number as the Primary E.164 number. However, only two Cisco Unified Communications Manager Express extensions are allowed to share the same mailbox in the Cisco Unity Express voicemail.
From this good Q&A doc;
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_qanda_item09186a0080875c6f.shtml#q12
Place one ext in the primary ext field, and the other in the E.164 field
phonenumber - Specifies a number or extension for this user. No spaces or dashes are allowed.
phonenumberE164 - Specifies a telephone number with area code for this user. No spaces or dashes are allowed.
Example:
se-10-0-0-0(config)# username user3 create
se-10-0-0-0(config)# username user3 phonenumber 50180 (in your case 300)
se-10-0-0-0(config)# username user3 phonenumberE164 13335550180 (in your case
xxxxxxxxxx)
From this good doc;
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_administration_guide_chapter09186a00803ef7a7.html
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

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

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

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

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.

Can't configure hunt group voicemail unavailable or busy msg

Similar Messages

Maybe you are looking for