Hi,

We have tested our application for Avaya 96XX and 16XX and running at few sites but at one site we have some special phones CCT Contact Pro as station configured in Avaya CM. CCT Pro also using AES TSAPI for call monitoring.

As per our log createCall() API return success but when calling call.connect() method to initiate call to given number we are getting CSTA Error: 12.
As per AES TSAPI Error list it's INVALID_CSTA_DEVICE_IDENTIFIER. What does it mean?

Our application has AES version 8.1 JTAPI library but at site AES version is 7.x. Can this be a reason?

Thanks & Regards,
Umesh

One thing, I would like to inform that during our testing, first day everything worked well. But after weekend we stared again to test then it happen. Can this be due to any change in Station configuration at Avaya CM end.

Here are the logs -


com.avaya.jtapi.tsapi.TsapiPlatformException: CSTA Error: 12
at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:100)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:577)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:453)
at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.queryDeviceInfo(Tsapi.java:1102)
at com.avaya.jtapi.tsapi.impl.core.TSProviderImpl.getDeviceExt(TSProviderImpl.java:1578)
at com.avaya.jtapi.tsapi.impl.core.TSCall.connect(TSCall.java:716)
at com.avaya.jtapi.tsapi.impl.TsapiCall.connect(TsapiCall.java:198)
at com.avaya.jtapi.tsapi.impl.TsapiCall.connect(TsapiCall.java:284)
at AvayaAesJTAPICommunicationPkg.JTAPIController.makeCall(JTAPIController.java:1323)
at websocketcommunicationpkg.WebSocketEndPoint.processMakeCallRequest(WebSocketEndPoint.java:866)
at websocketcommunicationpkg.WebSocketEndPoint.processMessage(WebSocketEndPoint.java:301)
at websocketcommunicationpkg.WebSocketEndPoint.onMessage(WebSocketEndPoint.java:73)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.tomcat.websocket.pojo.PojoMessageHandlerWholeBase.onMessage(PojoMessageHandlerWholeBase.java:80)
at org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:401)
at org.apache.tomcat.websocket.server.WsFrameServer.sendMessageText(WsFrameServer.java:119)
at org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:502)
at org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:301)
at org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:133)
at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:82)
at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171)
at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151)
at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148)
at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1626)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

One update We receive that we are able to dial external number/Toll free number from application.
What error we will receive if application is unable to dial a number due to Class of Restrictions? Will it be CSTA Error : 12 ??

Waiting for some reply.

Thanks & Regards,
Umesh

> As per AES TSAPI Error list it's INVALID_CSTA_DEVICE_IDENTIFIER. What does it mean?

According to the TSAPI Programmers Reference document:
INVALID_CSTA_DEVICE_IDENTIFIER (12) – An invalid device identifier or extension is specified in callingDevice.

> Our application has AES version 8.1 JTAPI library but at site AES version is 7.x. Can this be a reason?

I very much doubt that it is the cause.

> Can this be due to any change in Station configuration at Avaya CM end.

Possibly, but I have no way of knowing. I would suggest that you run a "list trace station XXX" at the Communication Manager SAT terminal and make the call. This may give you a clue as to the cause.

> What error we will receive if application is unable to dial a number due to Class of Restrictions?

From a brief test in my lab, I don't see that behavior when the call is blocked by COR.

As this problem is occurring in a production environment, if the list trace station doesn't help, I suggest you ask your customer to open a Service Request with Avaya Services or their Business Partner.

Martin

Thanks Martin. Your response will help me.

Let me check traces. I will update if anything finds unusual.

Regards,
Umesh