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.

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?

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.

Error 779 shows up in ip phone when transfer to a hunt group failed.

We have a CME (C2800NM-SPSERVICESK9-M), Version 12.4(24)T3. We have receptionist IP phone and a group of xx team phone setup. There is a hunt group for that group of xx team phones.
The receptionist phone is setup like this:
ephone-dn 102 dual-line
number 279          <<<<DN for receptionist
label xx
description 279
name xxx
corlist incoming SUPER
huntstop channel
hold-alert 30 originator
ephone 71
mac-address xxxx
username "x279" password xxx
provision-tag 279
type 7961 addon 1 7914 2 7914
button 1:102 2m49 3m52 4m40
button 5m7 6m105 7m114 8m11
button 9m43 10m83 11m66 12m74
button 13m48 14m38 15m54 16m104
button 17m88 18m53 19m69 20m37
button 21m41 22m80 23m60 24m56
button 25m70 26m100 27m72 28m92
button 29m71 30m110 31m61
The xx team's hunt pilot is DN 201:
ephone-hunt 20 longest-idle
pilot 201
list *, *, *, *, *, *, *, *, *, *, *, *
final 775                 <<<<this is voicemail number
timeout 15, 15, 15, 15, 15, 15, 15, 15, 15, 15, 15, 15
no-reg pilot
display-logout
1. If calling the reception phone (either from PSTN, or internally in the same site from a phone regiestered to the same CME),   the receptionist can pick the phone and talk, no problem. But if the receptionist transfers the call to ext. 201 (the pilot of hunt group). Intermittently, a few times a week, the call drops after being transferred. The receptionist sees 779 on her display, the callers hears a message saying "There was a technical problem". It is not possible for the receptionist to take the call back. The client has to recall and then on the 2nd try to call is transferred OK.
If the receptionist transfer the call to the DN of individual member of the hunt group, transfer is good.
2. If caller calls the pilot direclty (either from PSTN, or from internal phone in the same CME), the caller experienced the same issue as in the transfer case.
If caller calls the number of individual memeber of the hunt group, there is no problem.

Hi Billy
This is not supported. This support is being added for next release.
Thanks

How to enable HLog for B-ACD Hunt Group

We are using B-ACD for imcoming calls, the hunt group for BACD has 5 members. I want people to be able to login/logoff from this hunt group.
I have this working with the DND button, but then the phone doesn't ring when the extension is dailed directly. So it seems the alternative is using another feature/button called "Hlog".
I've added the HLog softkey but nothing happens when its pressed. I can't seem to find instructions on what else might need to be done to enable HLog.
Here is a bit of the related config info
ephone-template 16
softkeys idle Redial HLog Cfwdall Pickup Dnd Mobility
softkeys seized Cfwdall Endcall Redial Pickup Gpickup Callback
softkeys connected Trnsfer Endcall LiveRcd Hold Mobility
ephone-dn 15 dual-line
number 206
no-reg primary
label 206
description Kathy
name Kathy
call-forward busy 299
call-forward noan 299
timeout 10
ephone 6
device-security-mode none
video
mac-address 0021.1BFC.BF2B
ephone-template 16
max-calls-per-button 2
username "kathy"
password 1112
type 524G
button 1:15
ephone-hunt 50 sequential
pilot A888
list 204, 205, 201, 206
timeout 8, 8, 8, 8
no-reg pilot
statistics collect
auto logout 3
description *** CCA BACD ***
display-logout All agents logged out

We still don't have Logging in and out of the BACD Hunt group working.
The #350 and *350 don't seem to work. On the phone when I dial them it connects for a second then disconnects, no feedback if it worked. But when I try calling our business number the phone still gets rung in the hunt group sequence. So the phone isn't getting logged out.
On some of the phones I can see the "HLog" button but when pressed it says "that key is not active here".

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.

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

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.

Temporal error in IPPhones 6921 with Hunt Group

Hi,
I have registered several IPPhones 6921 in cucm via wan, and trying to make a pickup Group, when I place a call, runs the hunt group, but when i try to pick up the call with Pickup Group softkey in the ipphones shows the message "temporal error" and fails.
I think this could be a bandwith issue, because end customer has a ADSL with only 200 Kb to upload between the two sites, although I have configurated region and Device Pool, still fails.
Any idea?
Regards!

Hi,
I have registered the ipphones in a cucm via WAN, i think that could be a bandwith issue because only happen when they are connected in the cucm, when I registered them locally in my CME all runs properly, so only have this weird behavior when are connected to CUCM via WAN.
Thanks!

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

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

7961GE Hunt Group ringing name

Our shop has been exclusively 7961Gs for 7 years now. We recently purchased some 7961GEs and are noticing that when a phone is part of a Hunt Group, the Hunt Group no longer displays on the inbound call. On the 7961Gs it would say the From: <Caller> For: <Hunt Group> .
Our Help Desk personnel love the 1Gbit speed, but hate not knowing if the incoming call is for them or the Help Desk.
Any help is much appreciated!!
Thank you,
--Whammer

Hi Whammer,
I'm guessing the new 7961GE's are running a pre - 9.0 firmware;
It sounds like this bug
CSCth95017 - Configurable parameter on how callingparty is displayed for hunt groups.
Description
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
Details
1st Found-in:                          (1)
8.6(2)
More
Less
Status:
Fixed
Last Modified:
Mar 11,2012
Known Affected Versions:
More
Less
Fixed-in:                          (3)
9.0(0.98000.74), 9.0(0.98000.21), 8.6(2.21023.1)
More
Less
Product:
Cisco Unified Communications Manager (CallManager)
Platform:
Dependent
Severity:
2 - severe
Customer Reported:                          (26)
Cheers!
Rob

Call Manager Express Hunt Group roll over doesn't work correctly

Hello,I have a wierd issue occuring on the CME portion of a client's UC520. Currently, I have a hunt group set up that has 1 user and then the auto attendant. Basically, I want to give a user a chance to answer the main line, and if she doesn't, it then roll's to the main auto attendant. This is working as long as I keep the time out on the hunt group under 12 seconds. The issue is that is about 2.5 rings. She'd like a little more time to be able to pick it up. When I put the time out above 12 seconds (say 16) and dial from an external number, it rings her phone correctly, then you can hear it attempt to transfer, but it transfers it back to her phone instead of rolling over to the auto attendant. You can even see on her phone that the transfer occurs and it transfers to herself. For an instance, it shows 2 calls with the same caller ID. Change the time out back under to 12 or under, and everything works great. Any help would be greatly appreciated.

Sorry about that. Here is the IOS.
Cisco IOS Software, UC500 Software (UC500-ADVIPSERVICESK9-M), Version 12.4(24)T, RELEASE SOFTWARE (fc1)
And here is some relevant code.
ephone-hunt 1 sequential
pilot 501
list 201
final 401
timeout 11
no-reg pilot
statistics collect
destination-pattern 401
b2bua
voice-class sip outbound-proxy ipv4:10.1.10.1
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad

Hunt-group description on CME 4.0(3)

Similar Messages

Maybe you are looking for