I am getting the following error while attempting to validate my script from Tomcat Manager. The code worked earlier and I am not sure what I did to cause this.

ERROR http-8080-Processor25 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SRS_Main].[jsp] - Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
   at org.apache.jsp.jsp.validate_jsp._jspService(validate_jsp.java:554)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
   at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
   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:172)
   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:875)
   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)

thanks. that is what I was looking for. I was using the std message for silence in the play back for phone numbers. I am going to copy the std_en_us message for silence and put them into my application phraseset. But, are there any documented issues with using the std_en_us messages within application prompts? I am fighting a application server timeout issue from various places in the script and I am wondering if this could be causing my issue?


Thanks
Scott

I don't think so. I reinstalled from the same archive.

Do you know how it worked before? Why did it let me do use them under my other box?

I found the issue with the messages with the red X. I simply needed to resave those. I am still having hte issue of being able to add a std_en_us phrase to a prompt. Can;t figure this one out.

Thanks.
Scott

I had to rebuild my development box and in the process I have lost the ability to add any of the std_en_us phrases to a phrase. and all my existing phrases that use the std_en_us messages have red X's. Any ideas?

I am attempting to run DD on a thin client(blade) that doesn't have any audio drivers. I am getting the error "Error(0x8004503a) unable to set audio input" during generation. Is there a work around ? or is the work around get another machine?

the faq is located under the Dialog Designer/CTI Connector section. We are using UUI to send pop information to CCE.

I am wondering if the way my switch is passing the call, via vectors, could be causing the issue with my CTI connector not passing the call back to the switch properly. Could this be why the CTI transfer is not sending the voice along with the CTI pop?

And can you explain the purpose of that faq? the faq reads like vectors are not the proper method of sending CTI based calls to VP. Is that correct, and if so, what is the proper method?

Sorry. should have linked to my other thread.

https://devconnect.avaya.com/secure/forum/d_forum_3.jsp?t=3895&f=6

What is the purpose of this FAQ if there are no issues between vectors and CTI? Maybe I am missing its point.

Thanks

I ran across this in the FAQ and I think it relates to the problem I am having. " Will CTI work with vector programming (i.e. converse steps, etc.)?

No. If the vector has control over the call, then it will ignore messages from the TServer. "

In production, we are sending calls to VP using vectors based on DNIS. For this script I am transfering to agents using Converse Data Return. In developing a CTI based application, using the same vectors in the switch, I am having issues transferring the calls via CTI. Could the use of vectors be my issue? and what is the proper method to send calls to VP if so?

Thanks.

thanks for the reply. I did some testing with our switch tech and the call is getting into the queue and the CTI pop is happening ok, I simply don't have voice in either direction. I am thinking this is switch related not VP/DD. Do you have any thoughts on the voice path issue?

During a CTI transfer, the initial inbound call is being disconnceted. I do get the CTI pop at the agent desktop, just not the call. Here is the CTI trace log .

04/02/2009 15:34:18 DEBUG - ProviderMonitor: Checking:AES1 for availability
04/02/2009 15:34:19 DEBUG - Hold.doHold:3725 putting on hold ext:3725
04/02/2009 15:34:19 DEBUG - CTICallObserver.addApplicationObserver: adding an app observer to extension:3725
04/02/2009 15:34:19 DEBUG - Hold.doHold 3725: Placing terminal connection 0 on hold...
04/02/2009 15:34:19 DEBUG - Hold.doHold 3725: Waiting....
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3725 is 1
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 0 is 216 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Terminal Connection Held Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.updateCallState 3725: setting call:8932 to state:held
04/02/2009 15:34:19 DEBUG - CTICallObserver.updateCallState 3725: setting cached call:8932 to state:held
04/02/2009 15:34:19 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 3725 about call event
04/02/2009 15:34:19 DEBUG - Hold.doHold 3725: Terminal connection 0 placed on hold
04/02/2009 15:34:19 DEBUG - Hold.doHold 3725: Done placing connections on hold
04/02/2009 15:34:19 DEBUG - CTICallObserver.removeApplicationObserver: removing an app observer from extension:3725
04/02/2009 15:34:19 DEBUG - CTICallObserver.addApplicationObserver: adding an app observer to extension:3725
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall: Attempting to Connect from 3725 to 6200...
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: Connecting with UUI Gen Acct info Queue...
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall: Using FastConnect
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: Returned from connect call...
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: new call id is 9011
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: Call id is active
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: Call state is 48
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: blind call -- Waiting on mutex
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3725 is 7
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 0 is 101 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Connection Active Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 1 is 106 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Connection Created Event for id:9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCall 3725: call id is 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCall 3725: ucid is 00000000000000000000
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCall 3725: setting 9011 to state: initiated
04/02/2009 15:34:19 DEBUG - CallInfoData.CallInfoData:3725: callid 9011
04/02/2009 15:34:19 DEBUG - CallInfoData.CallInfoData:3725: ani 3725
04/02/2009 15:34:19 DEBUG - CallInfoData.CallInfoData:3725: dnis 6200
04/02/2009 15:34:19 DEBUG - CallInfoData.CallInfoData:3725: ucid 00000000000000000000
04/02/2009 15:34:19 DEBUG - CallInfoData.CallInfoData:3725: uui
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCall 3725: added call to list
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCall 3725:cache is:true
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCallToCache:caching call:9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 3725 about call event
04/02/2009 15:34:19 DEBUG - CTICallOperation.applicationCallEvent 3725: call is active, may transfer now
04/02/2009 15:34:19 DEBUG - Mutex.setWait: wait is false
04/02/2009 15:34:19 DEBUG - CTICallOperation.makeCall 3725: Thread on mutex + resumed
04/02/2009 15:34:19 DEBUG - CTICallObserver.removeApplicationObserver: removing an app observer from extension:3725
04/02/2009 15:34:19 DEBUG - Transfer.doMerge: Performing transfer...
04/02/2009 15:34:19 DEBUG - Transfer.doMerge:3725 active callid is 9011 held call id is 8932
04/02/2009 15:34:19 DEBUG - Transfer.doMerge:3725 number of connections is 2
04/02/2009 15:34:19 DEBUG - Transfer.doMerge:3725 found held call com.avaya.jtapi.tsapi.cc@153c375
04/02/2009 15:34:19 DEBUG - Transfer.doMerge:3725 found active call com.avaya.jtapi.tsapi.cc@153c375
04/02/2009 15:34:19 DEBUG - Transfer.doMerge:3725 about to transfer the call
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 2 is 105 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Connection Connected Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 3 is 208 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got an unknown event 208
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 4 is 116 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Terminal Connection Created Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 5 is 115 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Terminal Connection Active Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 6 is 219 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Terminal Connection Talking Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: found 1 connections
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: Found connections object, but not 2 active connections. May be using FastConnect
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3725 is 1
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 0 is 206 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Call Control Connection Established Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: found 2 connections
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: state of connection 0 is 51
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: state of connection 1 is 50
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: Call is not fully established
04/02/2009 15:34:19 ERROR - BlindCall.doBlindCall 3725: error performing blind call. This error can be valid if callee is busy or unreachable com.avaya.jtapi.tsapi.TsapiInvalidStateException: CSTA Error: 21
04/02/2009 15:34:19 DEBUG - CTIConnectorManager.dropCall: Call state of call com.avaya.jtapi.tsapi.cc@153c375 is ACTIVE
04/02/2009 15:34:19 DEBUG - CTIConnectorManager.dropCall: Address is 4057593011...
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3725 is 6
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 0 is 106 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Connection Created Event for id:9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.addCall 3725: call id is 9011 is already added, returning call data
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 1 is 116 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Terminal Connection Created Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 2 is 104 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Connection Alerting Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 3 is 203 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Call Control alerting Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.updateCallState 3725: setting call:9011 to state:ringing
04/02/2009 15:34:19 DEBUG - CTICallObserver.updateCallState 3725: setting cached call:9011 to state:ringing
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 4 is 119 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Terminal Connection Ringing Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 5 is 218 for call 9011
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent3725: got Call Control Terminal Ringing Event
04/02/2009 15:34:19 DEBUG - CTIConnectorManager.dropCall: Connection 0 state is CONNECTED
04/02/2009 15:34:19 DEBUG - CTIConnectorManager.dropCall: Disconnecting connection 0 for address 4057593011...
04/02/2009 15:34:19 DEBUG - CTIConnectorManager.dropCall: Call com.avaya.jtapi.tsapi.cc@153c375 dropped
04/02/2009 15:34:19 DEBUG - CTICallObserver.updateCallState 3725: setting call:8932 to state:disconnected
04/02/2009 15:34:19 DEBUG - CTICallObserver.updateCallState 3725: setting cached call:8932 to state:disconnected
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3725 is 7
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 0 is 107 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Connection Disconnected Event 107
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 1 is 205 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Connection Disconnected Event 205
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 2 is 117 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got an unknown event 117
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 3 is 215 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got an unknown event 215
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 4 is 107 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Connection Disconnected Event 107
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 5 is 205 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Connection Disconnected Event 205
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 6 is 103 for call 8932
04/02/2009 15:34:19 DEBUG - CTICallObserver.callChangedEvent:3725: got Call Observation Ended Event
04/02/2009 15:34:19 DEBUG - CTICallObserver.removeCall:removing call:8932 from ext:3725
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3725 is 4
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 0 is 105 for call 9011
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent3725: got Connection Connected Event
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 1 is 206 for call 9011
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: got Call Control Connection Established Event
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: found 2 connections
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: state of connection 0 is 51
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: state of connection 1 is 51
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: established both connections of call
04/02/2009 15:34:22 DEBUG - CTICallObserver.updateCallState 3725: setting call:9011 to state:established
04/02/2009 15:34:22 DEBUG - CTICallObserver.updateCallState 3725: setting cached call:9011 to state:established
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 2 is 115 for call 9011
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent3725: got Terminal Connection Active Event
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent 3725: Event: 3 is 219 for call 9011
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: got Terminal Connection Talking Event
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: found 2 connections
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: state of connection 0 is 51
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: state of connection 1 is 51
04/02/2009 15:34:22 DEBUG - CTICallObserver.callChangedEvent:3725: established both connections of call
04/02/2009 15:34:22 DEBUG - CTICallObserver.updateCallState 3725: setting call:9011 to state:established
04/02/2009 15:34:22 DEBUG - CTICallObserver.updateCallState 3725: setting cached call:9011 to state:established
04/02/2009 15:34:23 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 3727 is 11
04/02/2009 15:34:23 DEBUG - CTICallObserver.callChangedEvent 3727: Event: 0 is 105 for call 8921
04


The following are the Tomcat logs from the same period.

- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Using SCESession 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main servlet : AppRoot
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Using SCESession 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main servlet : XferTypeSwitch
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : [condition1] Condition [DNIS_Table:strAgent_Xfer_Type] String Equal [Converse] next [null]
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Using SCESession 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main servlet : dialcall
- BlindCall.doBlindCall 3725: error performing blind call. This error can be valid if callee is busy or unreachable com.avaya.jtapi.tsapi.TsapiInvalidStateException: CSTA Error: 21
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Using SCESession 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main servlet : UpdateATSDB
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : [condition1] Condition [Subscriber_Data:intSubID] Not Empty [null] next [null]
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : [condition2] Condition [sp_InsertRecordtblResult:_Code] Is Empty
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Using SCESession 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main servlet : sp_InsertRecordtblResult00700
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Assigning [301] to [sp_InsertRecordtblResult:_Agent]
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Assigning [00700] to [sp_InsertRecordtblResult:_Code]
- 0FCBE219522E83EBE2CE1B913E5045E6:/SRS_Main : Assigning [Subscriber_Data:intFileID] to [sp_InsertRecordtblResult:_FileID]


We are running VP 4.1 and AES

next question, I have a non cti enable application on my application server that is currently taking production calls. when i configure the channels for CTI will that affect the other calls that are routing on the non cti applications?

that did it. I put my tsapi.pro file in common/lib not commonclasses. that did it. thanks.