Need to see AESC log and possibly a jtapi log (set JTAPI to log in tsapi.pro file. Set log level = 7).

Take a look at com.avaya.cc.ccxml.ui/plugin.xml

under the org.eclipse.wst.common.snippets.SnippetContributions ext pt.

Snippets are part of the Web Tools (WTP/WST) that is added to Eclipse.

I'm not positive if those chars are messing it up. The AESC log you sent doesn't capture the blind call processing. Can you delete both app and AESC logs and rerun just one test call to cause the error again and post both those logs for download?

Do you have the AESC log for this same application?

I suspect the UUI might be problematic with some of the characters in it. Can you change UUI as a test? I also recommend using a consultation call with transfer on ring instead of a blind transfer. Usually is a safer option, however the UUI issue won't resolve it in this case.

1) What does the runtime do at start of a call? And how often does it do it (frequency)?
Always gather a connection to the VPMS for every call.

2) What are 'VPAppLogService' and 'VPAppRuntimeVars:getAppVarsAxis2()' used for?
VPAppLog is responsible for the connection back to the VPMS for logging/reporting and for gathering CAV and global data.

3) Why are we experiencing this latency?
Are you saying it happens once after restart of Tomcat and then is fine without user intervention, or do you need to do something to correct it? Is it fine after the 2nd call?

Sorry, redundant to Ross' answer.

I've included it. You can also find the sample apps on your CD or as separate downloads to OD here on Devconnect.

Your best choice is likely a CCXML based application. Have a look at the ConferencePredefined CCXML (CallControl) sample app. It may answer alot of your questions.

Should not always give disconnect. You will have to consult with VP support though as OD is just a client to the response the platform generates upon a SIP transfer.

You will lose the old collection with a new call to either setCollection or addCollection.

I don't see the error in your log, can you post the part of the log showing the error as well as the command sent to the AESC and any AESC logs you have.
Also, please login or create a devconnect accnt.

It's not done on a node by node basis. Can you give me more details on what you want to avoid reporting/logging?

That should do it.

FYI... I was logged out at the time I posted the anonymous response.

You need a targettype. Something like this:

<send targettype="'ccxml'"
name="'start.dialog'"
target="session.id"
delay="'0s'"/>