For all the call that are looked up whether the uri source or destination matches a user, then TMS checks what type of endpoint was used based on VCS registrations. So "Unknowns" are when TMS cannot get which type of Endpoint/Movi was used from the VCS data.
I would recommend you to raise a TAC case on this to keep the troubleshooting structured. We would need an export of the USER CDR's from the TMS, xconf + xstat from all the VCS'es involved with handling reigstrations for the provisioned users so we can verify the external management and feedback settings.
Additionally you can take a wireshark trace between the TMS and the VCS while running calls, but grab the encryption key from the VCS so we can decrypt the communication. Filter on the TMS and the VCS so we can see what the VCS sends the TMS. Include these logs in the TAC case for troubleshooting. Thanks!
In investigating this same issue, I have found that in many of the instances where the 'unknown' devices are reported, it duplicates a Jabber call (and in at least one case, an endpoint). To find this, I had to narrow my CDR window down to a couple of hours to isolate an individual call.
What might cause this double reporting? Do you think the double reporting is what's causing TMS to show the 'Unknown' Device Type?
Martin - can you verify that the summarized "CDR" data from the User CDR report in TMS is for outbound calls only (Jabber/Movi to anything else) or is there logic built into the report to also summarize inbound usage in the same report (anything to Jabber/Movi)?
We are comparing this report to the VCS CDRs from history.xml and trying to match up on LA_SIP_Alias (source) and LB_SIP_Alias (destination) fields from those VCS records. We are unable to get the same numbers as the TMS User CDR report shows and are wondering aboutthe logic criteria used on the summarization User CDR report.
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 ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...