QM 8.5.2 Desktop Recording: it "follows" my laptop´s MAC instead of IP Communicator´s device name
Scenario: I configured my IP Communicator 7.x to have a static Device Name (SEPaabbccddeeff) instead of asking the software to derive its device name from one of my laptop´s NICs. I am also running Desktop Recording 8.5.
I would have expected Quality Manager´s Desktop Recording software to interrogate my IP Communicator in order to learn the "logical MAC" behind the "SEP" prefix, but to my surprise Dektop Recording is using the MAC address of one of my laptop´s network adapters. Then, DR tries to verify with CUCM whether this MAC belongs to one of the phones associated to CUCM´s AQM JTAPI user, that is not the case. And so I am not being able to record the voice calls unless I force my softphone´s device name to match the NIC information.
¿ Has anyone faced this scenario and found a way to work this around? My problem is that sometimes I must start my IP Communicator from behind a VPN and therefore the MAC that Desktop Recording gets could be different depending on the network my laptop is hooked to.
QM 8.5.2 Desktop Recording: it "follows" my laptop´s MAC instea
Thank you very much for your kind answer.
I knew about the user guide advice, but it does not help, since a laptop could have many NICs (LAN, WLAN, VPN logical NIC). Every time your "active MAC" changes (ie, if you connect from LAN, from WLAN, from a VPN adapter), Desktop Recording will try to attach the definition to this MAC. There will be times in which your device name will match it, and times in which it will not, and that will force you to update the information on CUCM to make it work.
I would have expected Desktop Recording to interrogate IP Communicator for its Device Name instead
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: email@example.com 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 ...