If the call type is being changed during the script execution (for example, with a Call Type node) then those call types will not be accounted for in Route Call Detail, as no separate route request was made for the newly changed calltype.
If no call type changes are being made via scripting, then these results *should* be the same, provided that a full day's worth of data is included in the query, as a single interval may have calls crossing over a boundary condition where they are counted in 1 interval in the Interval record and another in Route Call Detail.
In a previous article I talked about the Cards & Buttons functionality of Webex Message. It's great to send nicely formatted or interactive messages.
What if you want to learn about Cards? There is a bot that teaches you all about Cards using...
The Python library "webexteamssdk" is great but there's one part of this library that "may need better documentation". This is the ability to create cards & buttons.
Here's a card example:
How is this card setup? What compone...
(using Python and the Flask Library)
An oAuth integration allows you to have an application "do stuff on your behalf".
This is a topic that can be quite complex to understand. For that reason I created this Python code to make it as easy as possible to...
It may be easier than you think.
After some customer requests I started writing code in Python. A few days later the script was ready.
What can it do?
ADD LOGO or image to your virtual background (using a domain/email address/URL/local-file)
Contact Center Knowledge Base
The Contact Center knowledge base contains information about developer topics for Finesse and Task Routing. For one-on-one help with these products, you can open a ticket at https://developer.cisco.com/site/support/. For...