Thanks Ross, you suggestion of considering use of transitional audio helped. We added transitional audio on AppRoot and now all prompts are getting played.

But last prompt we heard was After playing "<audio src="http://10.8.21.29:8080/PTC_Prod_V1/data/english/phrases/waitWhileProcess.wav">Please wait while we process your information.</audio>" everything is silence..

Anything prompts after that are never heard by caller.

I was on call for 40+ seconds after silence and then I dropped call.

What about issue related to prompts not getting heard?

One more thing we notices is errors in vpAppLogClient file. Please find attached log..

Please find attached all logs for a test call...

AOD 7.0.1 AEP 7.2..

After playing "<audio src="http://10.8.21.29:8080/PTC_Prod_V1/data/english/phrases/waitWhileProcess.wav">Please wait while we process your information.</audio>" everything is silence..

PFA trace file..

We have application ported from DD 5 to DD7. We have WS call in application. We notice that all prompts play which are used before WS call. Any prompt played after WS call is not being heard. As per logs we see prompts being played but we are unable to hear the same.

Any idea what could be causing the issue?

Is it possible to play music while IVR is processing backend request(SP or web service)?

If so how can that be accomplished?

Does AOD support X509 certificate authentication process?

Is Single Step Conference supported on TSAPI Basic license or will it require Advanced licenses?

We have AEP7 with AOD 7 application deployed.

When we dial into system, Inbound application works fine. But same fails with error "NoResource : Insufficient MPP Resources [ERRORS]”." for outbound application.

We have 2 application servers. Both inbound & outbound works fine from one application server. But outbound fails from second application server.

What could be causing system to throw this error. Both application servers are setup the same. They both have same version of Java & Tomcat and same applications have been deployed on both servers.

We have AEP 7 with SIP setup.

We set UUI with UCID and transfer call to a VDN. AEP receives 20 digit UCID. But on One-X Agent screen we see just 16 digits, last 4 digits are removed.

Is there any limitation on how many digits can be passed to One-X agent. OR is ti something on AEP or AOD which is removing last 4 digits?

Thanks,
Shantala

I am having same issue. As per attached document AEP need to be setup as SIP. But our setup is H323, does this logic works even for H323.

In our case we have setup "operation mode" to "service provider". We do blind transfer with AAI set with alphanumeric value. Will setting operation mode to shared uui and converting AAI to HEX work on H323 setup too OR is it only on SIP?

If it has to be SIP then on H323 how can we pass AAI/UUI to CM or OneX Agent screen?

We have an application where we received conversed data. Then we do converse return with AAI set with some alphanumeric value. We are doing a blind transfer to FAC+TransferVDN and setting AAI.

But we are not seeing that value being passed back to CM or One-X Agent.

This is on AEP deployment with AOD7 application. This has H323 stations configured with operation mode set to "Service Provider". There is no CTI configured on this deployment.

Is there any issue with the way we are handling coding in AOD application. How can we make AAI passed back to CM/One-X Agent.

Call gets to IVR with converse-on from CM. IVR then does bling transfer to a VDN with AAI/UUI set with URL.

My question was can AAI/UUI which doesn't use CTI have alphabets and special characters like URL?

URL need to get populated onto client One-X Agent screen.