Hi Team,

Can AESconnector support "Single Step Conference"?
If yes, please advice how to create "Single Step Conference" using AESconnector.

Best regards, K.Yamahara

Hi Team,

We are using the CMS R18.
On this CMS, ABNCALLS is indicating with "0" value on skill report even if there is no logged in users.
Is this correct behavior on CMS R18?

On our R17 CMS case, it is NOT indicated on skill report.

If it is correct report on R18, please advice me which documents we need to check on this.

Best regards, K.Yamahara

Hi Ross-san,

Thank you for your quick reply.
I understood your answer.

Thank you and regards, K.Yamahara

Hi Team,

We are using OD7.1.

We have od-vxml-applicatoins, which plays some .wav-files.
And we are thinking that the volume/sounds level of these played audio was low.
Therefore we would like to know whether we can volume up to play this .wav files without change .wav-files.
So does OD, EPM and MPP has any configurable parameters to change the volume/sound level of played .wav-audio?

Best regards, K.Yamahara

Hi Wilson-san,

Thank you for your support.

Actually, we can connect using SSL link with OD7.1 application on WAS9.0 after added WAS Client certificate to runtimeconfig's one.
At this time, we also modified the access destination Port setting on OD application side.

Thank you and regards, K.Yamahara

Hi Wilson-san,

Thank you for your quick advise.

We are checking configuration of the keystore in the IBM console.
If we need your help, we will ask it to you again.

Thank you, K.Yamahara

Hi Team,

We are trying to connect using https with OD7.1 application on WAS9.0.
However we can not successed it.

For https communication, First request is OK. However next request will be changed to NG.
Phone Call will be changed to silence from the middle of the time line.

1) GET /tb/Start Request ----- https OK.
2) POST /tb/lnitFlow ----- https OK. However WAS generated Error.

Below is loged message on WAS.
Please check them.
And please adivise hwo to resolve this issue.

----------------
WAS Access Log;

127.0.0.1,"10.174.22.34","[25/Jan/2017:11:47:09 +0900]","https","200","443","tb-lt1.smbctb.local","GET","/tb/Start","?session___sessionid=JNNTBSYMP1-2017025024714-5 &__VPapploggingurl=https%3a%2f%2f10%2e174%2e23%2e14%2faxis%2fservices%2fVPReport4&__VPapplog=%2faxis2%2fservices%2fVPAppLogService&__VPvpms=10%2e174%2e23%2e14&__VPappvars=%2faxis2%2fservices%2fVPAppVarsService&__VPVarAppDate=O&__VPVarAppURL=https%3a%2f%2f10%2e174%2e23%2e14%2faxis%2fservices%2fVPAppRuntimeVars&__VPVarGlobalDate=148 5311770933&__VPbreadcrumb=disabled&__VPmaxbackuplogfiles=10&__VPlogname=%25default%25gJdZJ70Fwh7WmeO1&__VPlogpassword=************************************************************************&_VPloglevel=lnfo&__VPappname=0%3aTB%5fIVR%5fPIN2","AvayaVXI/2.0","-","-","TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384","-","8963","14663"
127.0.0.1,"10.174.22.34","[25/Jan/2017:11:47:09 +0900]","https","200","443","tb-lt1.smbctb.local","POST","/tb/InitFlow","?__DDSESSIONID=kgYRyxYmdkz2gnkgwHZDPvH%3A%2Ftb","AvayaVXI/2.0","https://tb-lt1.smbctb.local/tb/Start","-","TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384","JSESSI0NID:OOOOkgYRyxYmdkz2gnkgwHZDPvH:eaaa9255-ecbb-4014-acOa-6cdd2981c3e5","4537","84878"
127.0.0.1,"10.174.22.34","[25/Jan/2017:11:47:09 +O9O0]","https","200","443","tb-lt1.smbctb.local","GET","/tb/FatalErrorFlow","?__DDSESSIONID=kgYRyxYmdkz2gnkgwHZDPvH%3A%2Ftb","AvayaVXI/2.0","https://tb-lt1.smbctb.local/tb/lnitFlow","-","TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384","JSESSI0NID:OOOOkgYRyxYmdkz2gnkgwHZDPvH:eaaa9255-ecbb-4014-acOa-6cdd2981c3e5","4501","10538"

----------------
WAS messages.log
[1/25/17 11:47:09:249 JST] 0000074a SystemOut 0 ***** Saw exception,tracing before report
[1/25/17 11:47:09:250 JST] 0000074a SystemOut 0 com.avaya.sce.runtimecommon.SCERuntimeException: Err or loading PluggableConnectorlnitialize class [com.avaya.sce.runtime.connectivity.cti.pdc.CTIConectorInit] for initialVariablesPosted com.avaya.sce.runtimecommon.SCERuntimeException: Error Executing CTI Commandjavax.net.ssl.SSLException: Unrecognized SSL message?plaintext connection?^M****RootCause^M
Javax.net.ssl.SSLException: Unrecognized SSL message?plaintext connection?
at com.ibm.jsse2.a.c(a.java:245)
at com.ibm.jsse2.a.a(a.java:106)
at com.ibm.jsse2.as.a(as.java:268)
at com.ibm.jsse2.as.i(as.java:130)
at com.ibm.jsse2.as.a(as.java:483)
at com.ibm.jsse2.as.startHandshake(as.java:160)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:12)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:15)
at com.ibm.net.ssl.www2.protocol.https.b.connect(b.java:64)
at com.avaya.sce.runtime.connectivity.cti.ir.CTICommand.execute(CTICommand.java:141)
at com.avaya.sce.runtime.connectivity.cti.pdc.CTIConnectorlnit.initialVariablesPosted(CTIConnectorlnit.java:92)
at com.avaya.sce.runtime.SCEServlet.processRequest(SCEServlet.java:602)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:76)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:243)
at com.avaya.sce.runtime.SCEServlet.doPost(SCEServlet.Java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServ1et.java:790)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1290)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:778)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:475)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1161)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:4893)
at com.ibm.ws.webcontainer31.0sgi.webapp.WebApp31.handleRequest(WebApp31.java:525)
at com.ibm.ws.webcontainer.osgi.DynamicVirtuaIHost$2.handleRequest(DynamicVirtualHost.java:297)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1003)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:262)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:958)
at com.ibm.ws.http.dispatcher.internal.channeI.HttpDispatcherLink.wrapHandlerAndExecute(HttpDispatcherLink.java:357)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.ready(HttpDispatcherLink.java:317)

- https between MPP and TB-AP is OK.
- In WAS's messages.log, when WAS side tried to connect with https as client, Error was generated.

at com.avaya.sce.runtime.connectivity.cti.ir.CTICommand.execute(CTICommand.java:141)
at com.avaya.sce.runtime.connectivity.cti.pdc.CTIConnectorInit.initialVariablesPosted(CTIConnectorlInit.java:92)
at com.avaya.sce.runtime.SCEServlet.processRequest(SCEServlet.java:602)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:76)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:243)
at com.avaya.sce.runtime.SCEServlet.doPost(SC EServlet.java:148)



Here after are Session detail information on Experience Portal Manager.

Home> Report> Standard Report> Session Detail> Session Detail Report> Session Detail

Sesssion Detail

Session ID : JNNTBSYMP1-2017025024714-5
Dialog ID : JNNTBSYMP1-2017025024714-5-1
Parent ID :
Session Type : VoiceXML
Session Sorce : In-bound Call
Media Server : mpp1
Start Date and Time : 2017/01/25 11:47:14 JST
Operation Time : 9 sec.
Contact Information :
Number of Contact : 1
Caller Number : tel:48102
Callee Number : tel:20101
Server Information :
Application Server : tb-lt1.smbctb.local
ASR Server :
TTS Server : N/A
Slot : 5
ASR MRCP Session ID :
TTS MRCP Session ID : N/A
Application Detail :
Application Name : TB_IVR_PIN2
Start Page Name : https://tb-It1.smbctb.localjtb/Start
Customer ID : N/A
End Information #1 : N/A
End Information #2 : N/A
End Page : FatalErrorFlow
End Reason : Application exited.
Recomended Pass : Yes
Topic : N/A

Performance Detail :
First Prompt delay : 0 msec
Total make call/received call number : 0
Recognition make call number : 0
VoiceXML Page requested number : 637
VoiceXML Page Cash hit number : 630
Average Prompt delay : 0
Average degree of confidence : 0
less than 1 msec Wait number of times : 0
1 - less than 2 msec Wait number of times : 0
2 - less than 3 msec Wait number of times : 0
3 - less than 4 msec Wait number of times : 0
more than 4 msec Wait number of times : 0
Max consecutive recognition Error : 0
Max Page Read-out Delay :

URL : https://tb-lt1.smbctb.local/tb/FataIErrorFlow



Experience Portal Manager

Time : 200 msec
Min. recognition ASR :
URL:
Total Make Call number : 0
Recognition make call number : 0
Session Transcription : Export
Interupt make call number : 0.0%
Default ASR degree of confidence : 50
ASR Engine Type :
TTS Engine Type :
User input number : 0
Speach input number : 0
DTMF entry number : 0



URL Access Detail

Start Time Priod Event Detail
11:47:14 AM 195 VoiceXMLLoad Start CacheHit: False
RootDocument: False
11:47:14 AM 90 VoiceXMLLoad InitFlow CacheHit: False
RootDocument: False
11:47:14 AM 12 VoiceXMLLoad FatalErrorFlow CacheHit: False
RootDocument: False
11:47:14 AM 52 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: False
RootDocument: False
11:47:14 AM 10 VoiceXMLLoad FatalErrorFlow CacheHit: False
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 10 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 9 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 8 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 8 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 8 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 8 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 7 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 9 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 8 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:14 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:14 AM 9 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:23 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:23 AM 6 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:23 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:23 AM 5 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:23 AM 0 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:23 AM 5 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:23 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:23 AM 6 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:23 AM 1 VoiceXMLLoad FatalErrorFlow-Disconnect CacheHit: True
RootDocument: False
11:47:23 AM 5 VoiceXMLLoad FatalErrorFlow CacheHit: True
RootDocument: False
11:47:23 AM 6 VoiceXMLLoad UserDisconnectMarker CacheHit: False
RootDocument: False
11:47:23 AM 3 VoiceXMLLoad AvavaSessionTerminationServlet CacheHit: False
RootDocument: False
11:47:23 AM DialogEnd

Best regards, K.Yamahara

Hi Wilson-san,

Thank you for your information.
We will try to evaluate OD7.1 application with WebSphere9.0.
If I need your help, I will raise new ticket.

Best regards, K.Yamahara

Hi Wilson-san,

Thank you for your quick advice.

I understood your explanation.
I will look IBM Websphere related web site as well.

Thank you and regards, K.Yamahara

Hi Ross-san,

We are going to start development OD7.1 application with Websphere 9.
If you have plan to do test formally or if you already done it, please tell us current paln/status.

Actually, I would like to get support us from your team if we will be faced some issue with Websphere 9 in the future.
However if you alredy have some lisk information on it, please let me know.

Best regards, K.Yamahara

Hi Team,

We are going to deploy OD7.1 applications with Websphier 9 to work under SSL control.
In this case, we would like to confirm below points.
Please advice.

Q1. "security-constraint" in "web.xml"
If my understanding is correct, the security-constraint is NOT required for SSL to work.
Howver I need to add it for limiting the access to HTTPS only.
Are those my understanding correct?

Q2. How to configure the "security-constraint" in "web.xml"?
I can not find any role/documents for "security-constraint" on Avaya support site.
If you have it, please share it with us.

Currently, I'm looking below link.
If you have any better documents or links, please advise.

https://docs.oracle.com/cd/E13222_01/wls/docs81/security/thin_client.html#1046060

Q3. Sample "web.xml" file
If you have the Sample "web.xml" file with "security-constraint" configuration, please share it with us.

Currently, I'm looking below link.
If you have any better documents or links, please advise.

https://docs.oracle.com/cd/E13222_01/wls/docs81/security/thin_client.html#1046060

Best regards, K.Yamahara

Hi zhaod-san,

Thank you for your reply.

I understgood. And We already received same information from SR(BBE).
And we also confirmed that this is Carrier related issue.

We desided to use PRI line/Carrier which support ALERTing message.
Best regards, K.Yamahara

Wilson-san,

Thank you for your reply.
I understood.
We will discuss it with our team.
If I need your help, I will ask it to you again.

Thank you and regards, K.Yamahara

Hi Wilson-san,

Thank you of your quick reply.

Those are good solution for us. We will use them.

On the other hand, if my understanding is correct, those are just report at the time of access report or received scheduled report email.
Originally, we would like to get OD application status information in real time.
For exsample, we can get SNMP-Trap separately from QSESM00070 if OD application stack/hung-up suddenly.
Are there any methodologies for it?

Or are there any way to generate an SNMP trap from within Dialog Designer code as standard feature on OD?
Best regards, K.Yamahara

Hi Team,

We would like to know how can we check OD application operation status?
If OD application will be stack/hung-up suddenly, are there any methodologies to find out those situation?
Some of SNMP-Traps are good solution for us.

Actually, we confirmed that QSESM00070(Application errors occurred for an application) was issued due to catch error status by MPP event handler when OD application force stopped operation(time out, no answer).
By the way, we are going to ignore QSESM00070. Because we also confirmed some error which need to ignore.(e.g. error.recognition).


On the other hand, if we can implement other SNMP-trap report application for check OD application operation status, it is other good way for us.
If you have idea, please advice.
Best regards, K.Yamahara