Hi Wilson,

We downloaded this version of the runtimeconfig, but we are still seeing bunch of vulnerabilities. Can you provide a more recent version that has the additional fixes? Below is the list of various issues.

Cross-Site Scripting: Reflected
Password Management: Insecure Submission
Cross-Site Scripting: DOM
Password Management: Password in HTML Form
Server-Side Request Forgery
Privacy Violation: Autocomplete
System Information Leak: External
Portability Flaw: Locale Dependent Comparison

Thanks,
Miki

Hi Wilson,

I tried adding the disconnect in the flow, but the behavior was the same. Is there a way to manually generate VXML to do a call drop?

Thanks,
Miki

Hi,

We are currently running on Orchestration Designer version7.1.0.12.02. We are noticing the IVR calls seem to be doing a release rather than drop/disconnecting the call. Is there a way to have the IVR do a drop/disconnect rather than release when the application wants to hang up?

Thanks,
Miki

Unfortunately the receiving extension that is transferring the call to the IVR is just an extension and not an IVR application. The OD logs don't show the original ANI coming across on the UUI or anywhere else. Are you expecting the originating ANI in the UUI from CM or EP, or were you expecting an IVR to set the ANI in the UUI before being sent to the destination IVR in question?

I have shared the information with our telephony team, and he requested that this Avaya case notes- 1-14894417306 and 1-14833858112 be checked.

Thanks,
Miki

Hi,

We are currently running on Orchestration Designer version7.1.0.12.02. Our applications are currently running in windows, but would like to know if we can run the applications on Linux server. The documentation seems to indicate that's not supported. Can you confirm if Linux is supported or not?

Thanks,
MY

Hi,

We are currently running on Orchestration Designer version7.1.0.12.02. We are seeing an issue when a call comes in on our phone switch, and when that call is transferred to our IVR the ANI we receive is the internal phone number that transferred the call and not the original ANI. Any idea how that can be resolved so that we are getting the original ANI and not the internal ANI that transferred the call? We are running in SIP environment.

Here is excerpt of our log.
/CallHandler : Storing :_sipcallid to simple: _sipcallid as [8028bcc894c8e918fc45cf1a4bc00]
/CallHandler : Storing :redirectinfo___presentationinfo to complex: redirectinfo:presentationinfo as []
/CallHandler : Storing :redirectinfo___reason to complex: redirectinfo:reason as []
/CallHandler : Storing :redirectinfo___screeninginfo to complex: redirectinfo:screeninginfo as []
/CallHandler : Storing :redirectinfo___uri to complex: redirectinfo:uri as []
/CallHandler : Storing :session___aai to complex: session:aai as [PD,00;FA,000104C65D53F1DF;FB,000104B65D53F1D7]
/CallHandler : Storing :session___ani to complex: session:ani as [+3191231234]
/CallHandler : Storing :session___calltag to complex: session:calltag as [abc-abc_SM-1-2019226113858]
/CallHandler : Storing :session___channel to complex: session:channel as []
/CallHandler : Storing :session___dnis to complex: session:dnis as [1231234]
/CallHandler : Storing :session___mediatype to complex: session:mediatype as [unknown]
/CallHandler : Storing :session___protocolname to complex: session:protocolname as [sip]
/CallHandler : Storing :session___protocolversion to complex: session:protocolversion as [2.0]
/CallHandler : Storing :session___sessionlabel to complex: session:sessionlabel as [00001012221565782495]
/CallHandler : Storing :session___sharedmode to complex: session:sharedmode as [shared]
/CallHandler : Storing :session___ucid to complex: session:ucid as [00001012221565782495]
/CallHandler : Storing :session___uui to complex: session:uui as [PD,00;FA,000104C65D53F1DF;FB,000104B65D53F1D7]
/CallHandler : Storing :session___videobitrate to complex: session:videobitrate as [unknown]
/CallHandler : Storing :session___videocodec to complex: session:videocodec as [unknown]
/CallHandler : Storing :session___videoenabled to complex: session:videoenabled as [unknown]
/CallHandler : Storing :session___videofarfmtp to complex: session:videofarfmtp as [unknown]
/CallHandler : Storing :session___videoformat to complex: session:videoformat as [unknown]
/CallHandler : Storing :session___videofps to complex: session:videofps as [unknown]
/CallHandler : Storing :session___videoheight to complex: session:videoheight as [unknown]
/CallHandler : Storing :session___videonearfmtp to complex: session:videonearfmtp as [unknown]
/CallHandler : Storing :session___videowidth to complex: session:videowidth as [unknown]
/CallHandler : Storing :session___vpcalledextension to complex: session:vpcalledextension as []
/CallHandler : Storing :session___vpcoveragereason to complex: session:vpcoveragereason as []
/CallHandler : Storing :session___vpcoveragetype to complex: session:vpcoveragetype as []
/CallHandler : Storing :session___vprdnis to complex: session:vprdnis as []
/CallHandler : Storing :shareduui___id to complex: shareduui:id as [PD |FA |FB]
/CallHandler : Collection Mismatch, going bigger, New size is:3
/CallHandler : Storing :complex: shareduui:id[1] as [PD]
/CallHandler : Storing :complex: shareduui:id[2] as [FA]
/CallHandler : Storing :complex: shareduui:id[3] as [FB]
/CallHandler : Storing :shareduui___value to complex: shareduui:value as [00 |000104C65D53F1DF |000104B65D53F1D7]

Thanks,
Miki

Hi,

We currently have an OD7.1 application with CSR desktops running EMC Desktop 6.4.1. We would like to tie the IVR activity with the activity on EMC Desktop with the UCID, but the UCID in IVR is not matching up to the UCID in EMC Desktop. We have the trunk set to share uui and send ucid to Y as well as AEP application setup to share uui and send ucid to Yes. We have actually tried all combinations, and nothing seems to work. Secondly we have noticed when share uui is set on the trunk the UUI data does not get sent to EMC Desktop. Please advise on this as well. Any help would really be appreciated.


EMC: Logs
****************************
Time: 12/15/2017 12:13 PM
AFPSCREENPOPPLUGINNEW.TelephonyEventHandler.XMLStation_StationCallChanged - EventType: CSTAConnectionCleared; ThisStationDN: 1231683; CallAppearance: 1; CallerDN: 1231231234; CalledDN: 1231683; UCID: 00001119381513357997; UUI: ; Key: 31; CallID: 11938; CallDirection: Incoming; EventCause: AgileSoftware.Developer.CSTA.CSTAConnectionClearedEventArgs
****************************

IVR Logs:
:session___ani to complex: session:ani as [+1231231234]
:session___calltag to complex: session:calltag as [mppserver1-_SM-1-20173
:session___channel to complex: session:channel as []
:session___dnis to complex: session:dnis as [4823521]
:session___mediatype to complex: session:mediatype as [unknown]
:session___protocolname to complex: session:protocolname as [sip]
:session___protocolversion to complex: session:protocolversion as [2.0]
:session___sessionlabel to complex: session:sessionlabel as [00001117531513357965]
:session___sharedmode to complex: session:sharedmode as [shared]
:session___ucid to complex: session:ucid as [00001117531513357965]
:session___uui to complex: session:uui as [PD,00;F7,000B;F8,0784322501;F5,3837372D3434352D3
:session___videobitrate to complex: session:videobitrate as [unknown]
:session___videocodec to complex: session:videocodec as [unknown]
:session___videoenabled to complex: session:videoenabled as [unknown]

Thanks,
Miki

Will do. Thank you.

These are the settings:
<context-param>
<param-name>runtime-ASR</param-name>
<param-value>Nuance 10.0</param-value>
<description>Runtime ASR {SRGS-Literals|SRGS-SISR|Nuance OSR|IBM|...}</description>
</context-param>
<context-param>
<param-name>runtime-SSML</param-name>
<param-value>true</param-value>
<description>Runtime SSML Generation {true|false} - "true" enables SSML generation, "false" disables.</description>
</context-param>
<context-param>
<param-name>runtime-nature</param-name>
<param-value>speech</param-value>
<description>Application nature, speech or message</description>
</context-param>
<context-param>
<param-name>runtime-Platform</param-name>
<param-value>Experience Portal</param-value>
<description>Runtime Platform {Desktop|Voice Portal|Experience Portal|Other|IR|MPS}</description>
</context-param>
<context-param>
<param-name>runtime-VXML-Compatibility</param-name>
<param-value>2.1</param-value>
<description>2.1 + IVVR, 2.1 Allows VXML 2.1 extensions, 2.0 Uses VXML 2.0 Only</description>
</context-param>
<context-param>
<param-name>runtime-DTMF-Native</param-name>
<param-value>LOCAL_SRGS_SISR</param-value>
<description>(NATIVE|LOCAL_SRGS_SISR|LOCAL_SRGS_LITERALS, NATIVE means DTMF Grammars are in native asr format.</description>
</context-param>

Hi,

We are running on following:
App Server: Tomcat 8 and 7
OD7: 7.10.12.02.p2
Experience Portal 7.0.1
JDK: Oracle 8

We are experience an issue with recognizing # when remote DTMF processing is turned on. The application works fine with remote DTMF process set to No. The * seems to work fine either way, but I have not been successful in get # to be recognized in a link or using a grammar file. Please let me know when needs to be done to get this working again.

This is the pound.gram file:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<grammar>
<properties>
<mode value="dtmf"/>
<type value="static"/>
</properties>
<data>
<column id="coldata" repeat="-1" width="150">
<item repeat="-1" repeat-prob="-1" tag="#" value="#" weight="-1"/>
</column>
</data>
</grammar>

Thanks,
Miki

x

Hi,

We are running on following:
App Server: Tomcat 8 and 7
OD7: 7.10.12.02.p2
Experience Portal 7.0.1
JDK: Oracle 8

We are periodically seeing some performance issues in our test environment. During these period we are seeing EPBatchLogWriterThread using large amount of CPU and memory through Oracle java Mission Control. We have logging disabled in VPAppLogClient.log4j.properties, so not sure why this is happening. The problem seems to appear, and then clear up on it own. Sometimes the system requires a recycle. Attached are some screen prints. Any input on what is causing the issue and possible resolution would really be appreciated.

Best Regards,
Miki

Thanks for the information. I'm pretty sure we support TLS, but we will double check.

The system where the grace period ended is the new system we built. What does the system use to track whether to allow or deny grace period? Is it based on IP, host, etc.?

Thanks,
MY

Hello,

We are running on Experience Portal 7.0.1, but we have new application being developed on Orchestration Designer 7.1. In one server environment the licensing fails and calls don't work. On another environment the system licensing goes into grace period. Logs are below. We have OD 7.0.1 applications work fine with the same weblm that is not working with OD 7.1.
Questions:
1) Can we run OD7.1 application on EP 7.0.1? Any known issues with this?
2) Are there any licensing issues between OD7.1 and EP 7.0.1?
3) Any issues with weblem with our setup?

>>Log from server that is not working at all due to license issue.
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : runtime_platform : Experience Portal
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : runtime_asr : Nuance 9.0 (Quantum)
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | DEBUG - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Refreshing License
22/03/2017 10:08:38:780 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Acquiring Avaya Platform runtime license
22/03/2017 10:08:38:795 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Using license check timeout :0
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : Runtime :false
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : IC :false
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | INFO - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : CTI :false
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | DEBUG - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : License is bad, grace period expired
22/03/2017 10:08:59:824 | DD685F5C59C20B000E31E6CA50301DC0 | DEBUG - B5F6D6D8675ECBB64DADEE684EC2EEF5:/CallHandler : License refresh timer started

>>Logs where the licensing goes into grace period.:
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Acquiring Avaya Platform runtime license
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : PlatformParams:getPlatformParams: __VPVarGlobalDate is 1488397641970
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : PlatformParams:getPlatformParams:Timestamp is 03/01/17 13:47:21
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : License: Use the license server url in VPMS instead - https://weblm:52233/WebLM/LicenseServer
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Using license check timeout :0
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Runtime :false
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : IC :false
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | INFO - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : CTI :false
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : Remaining grace period 538209790
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : License is bad, allowing grace period
23/03/2017 11:19:17:154 | 23872F17543570E9CCF7BB6F14D45E68 | DEBUG - 7032BA28B5FF3A808BC89F9D9D80FEBD:/CallHandler : License refresh timer started

Best Regards,
Miki