setCollection would place a collection onto a variable so that you could store multiple values on it.

Use addCollection() which will create the collection for you.

Please login or create a login if you haven't already so you don't post anonymous.

Yes, you can do that.

Look at com.avaya.sce.runtime.SimpleVariable.createSimpleVariable(...)
and
com.avaya.runtime.sce.ComplexVariable.createComplexVariable(...)

Are you transferring callers back and forth between agent and IVR or is this more of a give IVR prior to the caller reaching an agent? We are releasing OD 7 in the next couple of months which will have much more formal integration with AACC.

Do you have the VXML that is sent over to the VB to see if the disconnect handler is indeed configured? You would need to enable VXML output in your ddrt.properties file.

You also should look through the sessionslot log on the MPP for the VB to see what further happens when the hangup event is caught. It should either send it to your handler or the default handler.

You can look into using POM (Proactive Outreach Manager) or you would need to write your own application/script that runs on a scheduled basis and invokes the app using the platform webservice to run it.

Look in the variable editor. Each variable has a flag for privacy. If set, the variable will not be traced or reported.

You would have to build the prompt using a combination of audio variables and recorded phrasesets for those characters that are not part of the localization bundles.

Yes, you can do it that way.

Are you having trouble speaking the prompt or getting back the response? Can you use a phraseset to record the prompt? An audio variable uses the localization bundle to speak the message.

The WI DB is behind the Avaya firewall and not accessible otherwise. Here is a description of it:

customer has reported the Log4j debug logging and savereport.log for VPAppLogClient OSGI bundle are broken under the WebSphere version 7.0.0.21.

The vpAppLogClient.log is created but the content remain empty and savereport.log is not created when the EPM is down.

SV has tested the EP 6.0 VPAppLogClientOSGI on WebSphere version 7.0.0.11 and has not found any problem.

VPAppLogClientOSGI bundle needs to work on a solution to be able to work on WebSphere version 7.0.0.21 and above.


How to reproduce:

#1, Installed WebSphere version 7.0.0.21 or above (I am using WAS 8.5.5.0):
- Installed the VPAppLogClientOSGI from the latest OD 6.0.0.1103 (6.0SP2). (If VPAppLogClientOSGI is installed prior, proceed to uninstall then install):
#2, Installed an OD app (e.g. MyTreasureMap)
#3, In EPM Application page, click on "verify" button to verify the MyTreasureMap URL
#4, Go to WebSphere installed machine, verify vpAppLogClient.log is created but the content is emtpy. The file is created under /opt/IBM/WebSphere/AppServer/lib/ext/appClientLogs/vpAppLogClient.log.

[root@VM-RH6-WAS85 bin]# ls -lt /opt/IBM/WebSphere/AppServer/lib/ext/appClientLogs/vpAppLogClient.log
-rw-r--r-- 1 root root 0 Aug 2 14:58 /opt/IBM/WebSphere/AppServer/lib/ext/appClientLogs/vpAppLogClient.log

#5, Make a few calls, verify the log entries are sent to the EPM by generating the Application Details report. Verify the debug log vpAppLogClient.log remains empty.

#6, Shutdown the EPM and make a few calls. Verify the vpAppLogClient.log still remains empty and no savereport.log is created.

NOTE: savereport.log.1 is actually created in the lab machine under /<epm ip>.
However, customer has very strict directory permission and that is probably why the savereport.log is not created under SunTrust machine.

You can set some data to private that you don't want to report. Is that what you are after?

If you set logging to finest for the voice browser on the VPMS and then look through your session slot logs on the MPP, it should indicate where and why in the VXML the error was thrown. It may not show the exact line, but will show what it was doing at the time it threw the error.

The problem is here:
06/11/2013 19:15:04:962 DEBUG - CTICallObserver.callChangedEvent:70206: found 3 connections
06/11/2013 19:15:04:962 DEBUG - CTICallObserver.callChangedEvent:70206: state of connection 0 is 54
06/11/2013 19:15:04:962 DEBUG - CTICallObserver.callChangedEvent:70206: state of connection 1 is 51
06/11/2013 19:15:04:962 DEBUG - CTICallObserver.callChangedEvent:70206: state of connection 2 is 54

You have 3 connections on this call (not sure what 3rd is, maybe Witness?). In any case, only 1 connection is connected (51) while the other 2 are in an unknown state (54). CTIC will only validate a call when 2 or more connections are connected, otherwise it will wait until a 2nd connection goes to a valid connected state.

First, my advice is to avoid the simulation scripts. They are very old and hard to work with. It is usually easier to test against a staging system and you get better feedback as the scripts just spit out a canned response.

If you do want to use them, you need something for callinfo:

You should have a command for callinfoInitialCall.
<command name="callinfoInitialCall">
<configuration>
<action type="OK"/>
</configuration>
</command>

You should also give the connector name = "CTI"
<connector name="CTI">

You should bring this issue to AACC support. They could better diagnose why it isn't getting passed.