Best practice ideas for using self services across many IVR application
We have one MAIN IVR CVP application which include all IVR self services like (Payment , Check bills , check account info ,ect.. )
We are requested to create a specific LIMITED IVR application which will make use of the Payment service only (This service is already existing in the MAIN Application).
My question is
Should I route the call to the MAIN application and make use of the Payment logic which already exist ? ( This will unify my code and avoid make duplication in the code which will enhance the maintenance and any feature change in the payment service)
Or Should I create a new application and copy and paste the same payment logic ? So we have (MAIN IVR) include all self services (including Payment Service ) and (Limited IVR) include small menu and Payment service logic repeated. This way of separation is very useful in terms of reporting (However reporting is also achievable when being used from the first one)
Audio and Video Endpoints Knowledge Base
For one-on-one help with these products, you can open a ticket at https://developer.cisco.com/site/support/. For other products, please contact Cisco TAC at https://www.cisco.com/c/en/us/support/index.ht...
I want to find out how many agents are configured for an attribute. I have followed all the steps which are provided by the Cisco UCCE 11.6 API guide but I could not get the count. Is it possible to get a count of agents or not?
Collaboration Management Knowledge Base
For one-on-one help with these products, you can open a ticket at https://developer.cisco.com/site/support/. For other products, please contact Cisco TAC at https://www.cisco.com/c/en/us/support/index.html
Lately I have received a few requests from people asking if it was possible to Archive a Webex MessageSpace as in "download all messages".Interesting.
You can download all messages using the messages API but that leaves yo...