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 ?
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
Sometimes you want to use Wireshark to capture packets On Cisco Meeting Server to troubleshoot and investigate video call issues, quality issues, or may be Expressway integration, WebRTC Connections, or why not, understand how the communication and the ca...
When we talk about Stun Protocol used for NAT traversal in voip environment, the common term used when talking about the Type of NAT that is compatible with Stun is “Full Cone NAT”, then when we explain why Turn Protocol is developped to replace Stun Prot...
From X8.11 of Cisco Expressway, a new concept of load balacing based on priority and weight instead of the round robin for better load balancing and probe is added to prevent the Cisco Expressway-C to sollicit a webbridge when it is down.Assume all ...
Local Zone: This is a collection of all devices that are registered with Cisco Expressway. The local zone is divided to subzones. These subzones include the automatically crated default subzone and up to 1000 manually configured subzones. In additio...
Datacenter virtualization is the process of employing virtual hardware for designing, developing, and implementing the datacenters. It is often used as an umbrella term that entails different categories like application virtualization, server virtua...