Author Message
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
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
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
The app is acting as a client trying to talk to AES connector servlet through HTTPS. The error seems to indicate that it does not have the credential or SSL certificate as a client. You would need to configure the keystore in the IBM console to allow apps to access the certificate as clients making outbound HTTPS connections.
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
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
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
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
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
Great! I am glad that works out.
Go to:   
Mobile view