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

Similar Messages

  • CCME Call Forward from one Hunt Group to another Hunt Group Failure

    Hi I have a couple of hungroups in Cisco Call Manager Express. I am trying to configure a Call Forward no answer from one hunt group to another. Does anybody know if this is possible? If so, is there a config available? Here is my config, but it is not working.
    Thanks,
    Derek
    voice hunt-group 20 parallel
    final 2290
    list 2201,2251,2252
    timeout 30
    pilot 2209

    Hi Derek,
    This is supported with the restriction shown below;
    final number
    Router(config-voice-hunt-group)# final 8888
    Defines the last extension in a voice hunt group.
    If a final number in one hunt group is configured as a pilot number of another hunt group, the pilot number of the first hunt group cannot be configured as a final number in any other hunt group.
    From;
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm/cmecover.html#72373
    Cheers!
    Rob 

  • Hunt group Callmanager 3.3(5)

    Hi all
    I have a problem creating a hunt group, more specifically hunt pilot number. When I create the hunt group and dial the hunt pilot number using the DDI I get a busy tone ?? Can anyone point in the right way of troubleshooting this ??
    Thanks

    Hi all
    I have a problem creating a hunt group, more specifically hunt pilot number. When I create the hunt group and dial the hunt pilot number using the DDI I get a busy tone ?? Can anyone point in the right way of troubleshooting this ??
    Thanks

  • CCX using Place Call to hunt group. Unable to determine who answered

    I'm trying to use the CCX to place a call to a CUCM hunt group and then once the answered, determine which member of the hunt group answered the call.
    I have used several of the Get Info steps, including:
    Get Call Contact Info
    Get Enterprise Call Info
    Get Contact Info
    However, all of those steps always just report back the CUCM hunt pilot number, instead of the actual line group member who answered the call.  Can anyone think of a way to determine the extension of the line group member that answered the call ?
    If it matters, I am using CCX 9.0.2su1

    I lack a system to test this on at the moment but perhaps try this CUCM Service Parameter. The question is whether CTI Manager will follow this logic or if this is only respected by the CDR flat file export.
    Show Line Group Member DN in finalCalledPartyNumber CDR Field
    This parameter determines whether the the finalCalledPartyNumber field in call detail records (CDR) shows the directory number (DN) of the line group member who answered the call or the hunt pilot DN. Valid values specify True (the finalCalledPartyNumber in CDRs will show the DN of the phone that answered the call) or False (the finalCalledPartyNumber in CDRs will show the hunt pilot DN). This parameter applies only to basic calls routed through a hunt list without feature interaction such as transfer, conference, call park, and so on. If a feature is involved in the call, then the hunt pilot DN will show in the finalCalledPartyNumber field regardless of the setting in this parameter. This parameter does not apply to Cisco CallManager Attendant Console.  
       This is a required field.  
       Default:  False

  • CallerID not correct when calling a Hunt Group #

    Not sure what happened, but when users called the 4357(Hunt Group) the caller id would show "Helpdesk and also the callers name and ext" on the caller ID of the users in the 4357 (Hunt Group List).
    Now when users call the 4357 the caller id on the (Hunt Group) end just shows the "callers name and ext".
    We like when it would show Helpdesk along with the user info because we know the person is actually calling the Helpdesk and not calling directly. For example, my boss knows to only pick up calls that come into the helpdesk when he is the only one here, but now he is picking them all up because it looks as though they are calling him directly.
    Any suggestions?

    Hi Aaron,
    I have made the changes you told o make and its working now.
    Thanks.
    Syed Kazi.

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

  • 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

  • CUCM 8.6 - Call Forward All Doesn't Work With DN In Hunt Group

    Hello,
    I'm trying to make a hunt group that's sole purpose is to dial out to our Help Desk member's cell phone (on-call after hours). The idea is that we want the hunt group to broadcast the call to the on-call engineers. Whoever picks up first takes the call. 
    At least that's the idea now. They may want to change that to - ring primary on-call cell phone, if no answer ring secondary on-call engineer. 
    The target cell phones will change every week and I wanted to give the supervisor a means of changing the numbers through the ccmuser page.
    I created two DNs and placed them in a hunt group, each with call forward all to a cell phone number. 
    It seems that the hunt group ignores the call forward all setting and that is by design (https://supportforums.cisco.com/document/9126/cisco-callmanager-call-forward-all-cfa-does-not-work-if-line-hunt-group). 
    Does anyone else have any suggestions on how to accomplish this?

    That's correct, what you're seeing is WAD, this topic has been discussed plenty of times before, the only option you have is SNR

  • Adding an extension to a Call Pickup Group

    I am new to call manager 7.0 and just wanted to know if adding an extension to a Call Pickup group was as easy as just going to the directory number configuration page of the extension and selecting a call pickup group within the "Call Forward and Call Pickup Settings?" Would there be anything else I would need to do?

    nope, that's it
    Assigning a Call Pickup Group to Directory Numbers
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmfeat/fscpickg.html#wp1056555
    HTH
    java
    if this helps, please rate

  • 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

  • Group Pickup feature doesnt work when add the phones to a hunt group in BE3k

    Hi All,
    I have a blast group with pilot number 300 , there are two members ext. 600 and ext.601 in that blast group.   I added these two extensions to Call pickup group and enable "Audio and Visual Alert".  I also have a spare phone ext. 602.
    when I dialed between extensions ext.600,601 and 602 , group pick up feature is woking and I can see "call available pickup " on the phone screen and hear the audio alert. But when I dial the hunt group pilot number 300 from spare phone ext.602 , both ext.600 and ext. 601 are ringing  but I can't see call pickup indicators on the screen. I also tried  "Opickup'  on the phone but  got "no call available for pickup" message on the screen. 
    Any ideas why and how to fix this issue?

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

  • Call transfer through Hunt group

    Hi,
    we have a call manager version 8.6 where we have mutiple huntgroups configured. Following is the call flow
    PSTN callers call a DID number from outside which after the translation on the gateway, hits a hunt pilot number on call manager and eventually the call rings on all the line members of the line group. One any of the line group member picks up the call and tries to transfer the call to any internal or external number, we get the following error message on phone screen and transfer does not work
    " External transfer Restricted"
    Now this happens even if we dial the hunt pilot number internally from an iphone and then if one of the members tries to transfer to an internal extension or external number, we get the error message
    More Information:
    There are many other hunt groups on the same call manager server and tries to transfer the call same way as the non working one and it works for them
    So i checked the difference. All the members of all the hunt groups are device profile logged into physical phone. The only difference was that working hunt group members are logged into 6921 phone where as non working users are logged into 7942 phones (sip firmare) and the profile are created for 9971 although we dont have any physical 9971 phone
    So it seems that call transfer through hunt group does not work only if the members are logged into 7942 (sip) phones and works when they are logged into 6921 with 9971 Device profile
    I hope its clear. Please let me know if its a known issue or limitation with 7942 phone. Any help will be appreciated

    Try changing the Block Offnet to Offnet Transfer CallManager Service Parameter to False and test again.  If it then works, we'll probably need CallManager traces to see why both numbers are getting marked as offnet.

  • CUPC Incoming Call from Hunt Group

    Hi all!
    Is is possible that I can see whenever someone calls me on my extension, or whenever a call comes in from a hunt group? Can I differ the incoming calls?
    Regards
    Rene           

    Are you talking about the attendant console hunt group? If yes, then you can do this by using the broadcast hunting feature. What it does is, all calls to the hunt pilot will be placed in queue and will be displayed in the Broadcast calls window within the Attendant Console. All uses can see the calling number of calls in queue and pick and chose the calls they want to answer.
    Check this link for more details
    http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/sys_ad/4_1_3/ccmfeat/fsccmac.htm#wp1144539
    Regards,
    Anup

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

Maybe you are looking for