Author Message
JimAdmire
Joined: May 17, 2007
Messages: 0
Offline
I'm seeing this error in the CTIConnector Trace.Log file after I see the following in the application log:

30/07/2008 15:29:16 DEBUG - 3AC18A79BD81F54C7681A66BC2463924:/MDES_MITS : CTICommand.execute: encrypted value is 3H/qh4Dn28P6ZSheQK389HkVG8/1UYZ9zix6oMt3evU=
30/07/2008 15:29:16 DEBUG - 3AC18A79BD81F54C7681A66BC2463924:/MDES_MITS : CTICommand.execute: request to manager is http://10.80.2.239:8080/cticonnector/CallInfoInitialCall?channel%3D178&k=3H%2Fqh4Dn28P6ZSheQK389HkVG8%2F1UYZ9zix6oMt3evU%3D
30/07/2008 15:29:16 ERROR - 3AC18A79BD81F54C7681A66BC2463924:/MDES_MITS : channel:178 |
EXCEPTION>
java.io.IOException: Server returned HTTP response code: 500 for URL: http://10.80.2.239:8080/cticonnector/CallInfoInitialCall?channel%3D178&k=3H%2Fqh4Dn28P6ZSheQK389HkVG8%2F1UYZ9zix6oMt3evU%3D
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
   at java.net.URLConnection.getContent(Unknown Source)
   at java.net.URL.getContent(Unknown Source)
   at com.avaya.sce.runtime.connectivity.cti.ir.CTICommand.execute(CTICommand.java:95)
   at com.avaya.sce.runtime.SCEServlet.ProcessCTIGetCallInfo(SCEServlet.java:486)
   at com.avaya.sce.runtime.SCEServlet.processRequest(SCEServlet.java:309)
   at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:53)
   at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:214)
   at com.avaya.sce.runtime.SCEServlet.doPost(SCEServlet.java:163)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
   at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
   at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
   at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
   at java.lang.Thread.run(Unknown Source)

This exception occurs when trying to populate the CTICallInfo structure.

In the TSAPI trace, I turned logging up to level 7 and see

07/30/08 17:30:28.205 {Thread-1717} MonitorDevice request failed - retrying
07/30/08 17:30:28.205 {Thread-1717} Sent InvokeID 1570 for TSProvider@3c342b
07/30/08 17:30:28.205 {Thread-1717} CSTAMonitorDevice ::=
07/30/08 17:30:28.205 {Thread-1717} {
07/30/08 17:30:28.205 {Thread-1717} deviceID "29178"
07/30/08 17:30:28.205 {Thread-1717} monitorFilter
07/30/08 17:30:28.205 {Thread-1717} {
07/30/08 17:30:28.205 {Thread-1717} call 0x0 < >
07/30/08 17:30:28.205 {Thread-1717} feature 0x0 < >
07/30/08 17:30:28.205 {Thread-1717} agent 0x0 < >
07/30/08 17:30:28.205 {Thread-1717} maintenance 0x0 < >
07/30/08 17:30:28.205 {Thread-1717} privateFilter 0
07/30/08 17:30:28.205 {Thread-1717} }
07/30/08 17:30:28.205 {Thread-1717} }
07/30/08 17:30:28.205 <GetEventThread> Received invokeID 1570 for TSProvider@3c342b
07/30/08 17:30:28.205 <GetEventThread> CSTAUniversalFailureConfEvent ::=
07/30/08 17:30:28.205 <GetEventThread> {
07/30/08 17:30:28.205 <GetEventThread> error 41 < GENERIC_SUBSCRIBED_RESOURCE_AVAILABILITY >
07/30/08 17:30:28.205 <GetEventThread> }
07/30/08 17:30:28.205 <GetEventThread> Handling INVOKE ID 1570 for TSProvider@3c342b
07/30/08 17:30:28.205 <GetEventThread> DONE handling INVOKE ID 1570 for TSProvider@3c342b
07/30/08 17:30:28.205 <GetEventThread> Received invokeID 1554 for TSProvider@3c342b
07/30/08 17:30:28.205 <GetEventThread> CSTAMonitorConfEvent ::=
07/30/08 17:30:28.205 <GetEventThread> {
07/30/08 17:30:28.205 <GetEventThread> monitorCrossRefID 178
07/30/08 17:30:28.205 <GetEventThread> monitorFilter
07/30/08 17:30:28.205 <GetEventThread> {
07/30/08 17:30:28.205 <GetEventThread> call 0x80000000 < CF_CALL_CLEARED >
07/30/08 17:30:28.205 <GetEventThread> feature 0xf0000000 < FF_CALL_INFORMATION FF_DO_NOT_DISTURB FF_FORWARDING FF_MESSAGE_WAITING >
07/30/08 17:30:28.220 <GetEventThread> agent 0xfc000000 < AF_LOGGED_ON AF_LOGGED_OFF AF_NOT_READY AF_READY AF_WORK_NOT_READY AF_WORK_READY >
07/30/08 17:30:28.220 <GetEventThread> maintenance 0xc0000000 < MF_BACK_IN_SERVICE MF_OUT_OF_SERVICE >
07/30/08 17:30:28.220 <GetEventThread> privateFilter 0
07/30/08 17:30:28.220 <GetEventThread> }
07/30/08 17:30:28.220 <GetEventThread> }
07/30/08 17:30:28.220 <GetEventThread> TsapiPrivate ::=
07/30/08 17:30:28.220 <GetEventThread> {
07/30/08 17:30:28.220 <GetEventThread> vendor "ECS"
07/30/08 17:30:28.220 <GetEventThread> data 2 0 5d 0 30 4 3 2 6 80
07/30/08 17:30:28.220 <GetEventThread> tsType 114
07/30/08 17:30:28.220 <GetEventThread> }
07/30/08 17:30:28.220 <GetEventThread> Handling INVOKE ID 1554 for TSProvider@3c342b
07/30/08 17:30:28.220 <GetEventThread> DONE handling INVOKE ID 1554 for TSProvider@3c342b

What is an error 41? And what is different about the extensions starting at 29178 from extensions 29000-29177 where the observer can be added?

thanks,

Jim
NeilGoldsmith
Joined: Nov 6, 2013
Messages: 902
Offline
You should bring this JTAPI log to the AES/JTAPI support group to further look at the error. Looks like something in the AES, maybe misconfigured, but this group isn't the best to diagnose those errors.
JimAdmire
Joined: May 17, 2007
Messages: 0
Offline
Thanks. I was thinking you might be able to help for the message that came out of the cticonnector. I'll post in the AES forum.

NeilGoldsmith
Joined: Nov 6, 2013
Messages: 902
Offline
Well ,the error that comes out of the connector is related to the JTAPI error. It probably shouldn't give a 500 error, but the net result is the same back to the app whether it was a 500 error or a returned error.

Do you have the snippet of the CTIC log showing the call it makes? I can look to see why it is a 500 error, but that still doesn't resolve your error 41.
NaikAshok
Joined: Jan 29, 2008
Messages: 0
Offline
Go to:   
Mobile view