Using Route Call Detail to Connect Routing Attempts
One of our two VVB servers failed which caused a portion of our calls to be sent to a Release Call node in ICM scripts. I have been tasked with finding the number of released calls, but each call made multiple routing attempts before the call was released, causing each call to have multiple distinct router call key combos. How would I go about finding the actual number of call attempts? I tried using distinct ANI, but since callers likely called in multiple times, this isn't perfectly accurate.
You could create a call type for released calls and place it right before the release call step in the ICM script. Then you could run a report on the call type. Otherwise CVP reporting may give extra detail on the calls.
IntroductionThe IssueServices Shown their status as UnknownWhat actions require to be taken?Logs required for troubleshootingWhat to expect in the logs:
The purpose of this document is to provide troubleshooting insight into a well-known iss...
New Cisco Champion Radio release on Zero Trust for WebexListen: https://smarturl.it/CCRS8E14 Follow us: https://twitter.com/CiscoChampion Cisco introduced End to End (E2E) Encryption in 2008 as a Webex Meeting option where only the me...
Community Live- Tour of the Real-Time Monitoring Tool
(Live event - Tuesday, 20 April, 2021 at 10:00 am Pacific/ 1:00 pm Eastern / 7:00 pm Paris)
This event will have place on Tuesday 20th, April 2021 at 10:00 hrs PDT
Learn: How to configure Cloud Connected PSTN with Webex Calling
CCP Provider Name
Product Home Page Link
Webex Calling Region
Countries Supported by Provider
Free Trial Link
Contact Provider Link
FR & LU
Meet the Authors Video - Leveraging SBCs to Empower a Changing World of Collaboration
(Live event – Tuesday, 16th, 2020 at 10:00 a.m. Pacific / 1:00 p.m. Eastern / 7:00 p.m. Paris)
This event had place on Tuesday 16th, February 2020 at 10am PST ...