I am trying to actively record devices that are registered with the CUCM. I am successful for normal calls, however, for hunt group calls, I am experiencing difficulties, which I believe are attributed to the way that the resulting SIP INVITE messages are composed.
For example, I set up a broadcast hunt group as follows to record four seperate Cisco IP Communicator softphones, each of which have a DN associated with the broadcast hunt group:
CUCM System Version
CUCM IP Address 192.168.10.100
Hunt Pilot 7777
Hunt Group Associated DN's 1001 1002 1003 1004
If we assume that all the devices contained in the hunt group are registered with the CUCM, whenever a call is made to the hunt group number (in this example, 7777), devices 1001-1004 ring. Regardless of which device answers the call, examination of the SIP traffic on the SIP trunk always shows the 'From' field to be 'firstname.lastname@example.org'. This seems to be because 1001 is the first in the list of associated DN's. If the device that 1001 appears on, goes offline eg. powers down, then 1002 will effectively become the first in the list and so any calls answered by the hunt group members, show up in the SIP INVITE message 'From' field, as being: 'email@example.com'.
Why does the 'From' field of the resulting SIP INVITE message always contain the first registered DN in the list of hunt group DN's instead of the DN that actually answered the hunt group call?
Is there some additional configuration on the CUCM that I should be performing, or is that the correct behaviour?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...