We have recently discovered that our 3rd party call logger is not logging calls for the conference leg of ad-hoc conferences. This is apparently since the CDRs lists the "phone number" of the conference portion of the call log as a port number of the conference bridge, e.g. b00203201013. Within the CDR, there seems to be no reference to the called parties that were conferenced in; and thus no record of outbound calls within this conference leg for our call logger to identify for billing purposes.
I have found within CDR Analysis and Reporting, that if you navigate to Device Reports-->Conference Bridge, you can generate a detailed report which lists all numbers called for each specific ad-hoc conference call.
My question is whether such information exists within a flat file, perhaps referenced by a CDR, which our call logger can utilise to generate billing for the outbound calls we are missing.
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 ...