Thank you for your evaluation.

Hello. You are close but the field you identified is incorrect. If you look further down on the table description, you'll find the field USER_CONTACT_ID (not CONTACT_ID). This is the data element that needs to somehow connect to the phone number collected for the Do Not Call list.

Hi. Thanks, but I'm actually referring to PIM_CONTACT.USER_CONTACT_ID -> "Contact ID provided while importing this contact record in the POM database. This should be used as a link between external customer database and POM database.". We need to tie this data element back to a Do Not Call list record when the targeted phone number has 'opted out' at the conclusion of a received campaign call. This has become necessary due to regulatory auditing by the Telephone Consumer Protection Act. (https://www.ftc.gov/business-guidance/resources/complying-telemarketing-sales-rule)

When creating an outbound campaign list the ID field is mandatory. Typically a phone number is also included in the import list. POM also provides Opt-Out functionality to add the dialed number to the campaign's Do Not Call List. Is it possible to also add the dialed number's associated ID field with the phone number to the Do Not Call List?

I've recently moved from Orchestration Designer Version: 8.0 to 8.1. In my new environment the source files all get updated with the text: "Last generated by Orchestration Designer". I know this is a preference setting but cannot locate it. Can the navigation to this setting be supplied?

After upgrading OD 8.0.0 Upgrade to OD 8.1.2 and importing an application the only error produced indicates: "Cannot find the class file for com.avaya.sce.runtimecommon.SCESession". Is anyone familiar with this upgrade issue and have a resolution?

I have an Avaya document titled: "REUSABLE DIALOG MODULE" by EP&T Advanced Applications - Argentina
In the section: RDM’s Outputs, the following return codes are listed:

The “output_returnCode” variable possible values are:
“SUCCESS”: indicates a successful input was recognized
“NOMATCH”: indicates that maxNoMatchCount has been reached
“NOINPUT”: indicates that maxNoInputCount has been reached
“NEGATIVECONF”: indicates that noAnswerMaxCount has been reached

Is there a definition of the difference between maxNoInputCount and noAnswerMaxCount ?

Thank you John. That does solve my inquiry. It is a little out of date and in case anyone else is looking the solution is: To disable the timestamp generation in Orchestration Designer,
select Window -> Preference -> Avaya -> Orchestration Designer -> Speech
and clear the Generate timestamp during code generation checkbox as shown in the following screen shot.
Click Apply to apply the changes.

We've recently ported our OD 7 source repository over to a new install of OD 8. Everything went fine but when I do a Clean …Eclipse adds a line to every source file: “* Last generated by Orchestration Designer at: 2022-FEB-16 10:03:10 AM”. This creates the undesirable effect of signaling the SVN version control that every source file has been updated.
I know there’s a way to disable this but I cannot remember what it is.

Hello

We have a total of 7 OD applications and are converting them from OD7 to OD8. Six of them converted with no issues and operate as expected but 1 of them does not run and produces the error: Problem simulating platform values (Connection refused (Connection refused))]

The OD7 version of the application functions normally and logs the following: PlatformParams:getPlatformParams: __VPVarGlobalDate is 1641493286405

We are converting from Avaya Aura(r) Orchestration Designer Version: 7.1 (7.1.0.1202) Build id: 201604141446 to Avaya Orchestration Designer Version: 8.0 (8.0.0.2201) Build id: 202009101606

Is there any guess on what is occurring on this one application?

It turns out that this one application was defaulting to Platform: Desktop on Export. Switching it to Platform: Experience Portal on Export resolved the issue.

Thank you Wilson. We installed only axis2 1.7.9 libraries and applications detail records are now successfully captured in the VPAPPLOG table.

Thanks for your patience Wilson. We are currently utilizing: Avaya Orchestration Designer CCXML Version: 7.1 (7.1.0.1202)
Our apache-tomcat-8.5.70/lib contains the following axis2 jar files:
axis2-adb-1.6.2.jar
axis2-adb-codegen-1.6.2.jar
axis2-codegen-1.6.2.jar
axis2-json-1.6.2.jar
axis2-kernel-1.6.2.jar
axis2-saaj-1.6.2.jar
axis2-transport-http-1.6.2.jar
axis2-transport-http-1.7.9.jar
axis2-transport-local-1.6.2.jar
axis2-transport-local-1.7.9.jar

Our EPM is 8.0.0.0.1497. There are many instances of the same error in vpapplogclient.log: "[VPAlarmMonitorThread: https://10.57.8.206/axis2/services/VPAppLogService] ERROR - AlarmMonitorThread:EPMWebServicesClientBaseImpl:logAlarmsAxis2() - Caught Exception FAILED with AxisFault faultCode: null error: HttpTransportProperties.Authenticator class cast exception to log entry size: 1 to URL: https://10.57.8.206/axis2/services/VPAppLogService from AE server: aep8testapp First SID: aep8testepm-2021356163723-3 Last SID: aep8testepm-2021356163723-3 NOTE: It could be caused by this EPM is not online or some other network issues.
org.apache.axis2.AxisFault: HttpTransportProperties.Authenticator class cast exception"

A new Lab build on Tomcat 8 (versus Tomcat 7) results in our application logging call & session detail records but no application detail records (VPAPPLOG) are created. No errors are reported. What might be mis-configured?

We recently updated our environment to AEP V8 but continue to use our OD V7 applications. Calls to the existing application are now producing the error: PAVB_00137 The VoiceXML interpreter failed to parse the cookie string to get the token. Does something need to be updated in our OD V7 development environment?