Author Message
KishorePinnamaneni
Joined: Jan 10, 2014
Messages: 1
Offline
It returned unspecified error. Looking at AES logs, found error
App attempting to send to an invalid session

Here are the logs.

ch.ecma.csta.binding.MakeCall@8e4a32
2013-04-29 13.44.15,783 com.avaya.api.sessionsvc.SessionSecurityContextFactory getSessionSecurityContext
INFO: created SSC: com.avaya.sessionsvc.securityContext.SSCSDBAuthz@166dbe6 for Farend: null, AAMethod: AAMethod [Authn: true, Authz: SdbAuthz]
2013-04-29 13.44.15,783 com.avaya.sessionsvc.SessionMulticaster addSessionListener
FINE: com.avaya.mvcs.proxy.TPacketReaderNode$MySessionListener@1ef0affadded to com.avaya.sessionsvc.SessionMulticaster@baffd4
2013-04-29 13.44.15,783 com.avaya.mvcs.proxy.TPacketReaderNode getSessionId
FINE: Mapping channel DefaultTCPChannel Bound to SocketAddress: /10.7.16.19:4721 Connected to SocketAddress: /10.6.44.22:6342session object session C4E7928EA7BD6CE68BF9990A9F196D1B-396
2013-04-29 13.44.15,785 com.avaya.sessionsvc.SessionMulticaster addSessionListener
FINE: com.avaya.mvcs.proxy.CstaRouterNode$MySessionListener@f1d778added to com.avaya.sessionsvc.SessionMulticaster@baffd4
2013-04-29 13.44.15,785 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: Creating a new SubscriptionManager for session=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396,DefaultTCPChannel Bound to SocketAddress: /10.7.16.19:4721 Connected to SocketAddress: /10.6.44.22:6342]
2013-04-29 13.44.15,785 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 1 Routing request=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] ch.ecma.csta.binding.start.StartApplicationSession@1793c15
2013-04-29 13.44.15,785 com.avaya.sessionsvc.SessionServicesImpl asyncStartApplicationSession
FINE: appInfo is not null
2013-04-29 13.44.15,785 com.avaya.api.sessionsvc.ProtocolVersion findMatchingProtocol
INFO: Protocol version negotiated: http://www.ecma-international.org/standards/ecma-323/csta/ed3/priv4
2013-04-29 13.44.15,786 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 1 Received com.avaya.platform.broker.impl.AsyncResponse@1c68b6f in response to session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] ch.ecma.csta.binding.start.StartApplicationSession@1793c15
2013-04-29 13.44.15,786 com.avaya.common.logger.PrintStreamLogger log
INFO: STANDARD OUT: 2013-04-29 13:44:15,786 [pool-2-thread-1] DEBUG net.sf.jpam.Pam - Debug mode active.

2013-04-29 13.44.15,789 com.avaya.sessionsvc.securityContext.SSCBaseClass authenticate
INFO: Login successful on CUS Store: user=ctiagent, after 3msecs
2013-04-29 13.44.15,789 com.avaya.sessionsvc.SessionObjectImpl validate
INFO: Login successful: user=ctiagent, clientID=XML Unencrypted:10.6.44.22:6342
2013-04-29 13.44.15,789 com.avaya.sessionsvc.SessionObjectImpl validate
FINE: session C4E7928EA7BD6CE68BF9990A9F196D1B-396 _sessionTimeout=180, _cleanupTimeout=60
2013-04-29 13.44.15,789 com.avaya.sessionsvc.SessionServicesImpl asyncStartApplicationSession
INFO: Validated session=session C4E7928EA7BD6CE68BF9990A9F196D1B-396, requested sessionTimeout=180, actual sessionTimeout=180, requested cleanupTimeout=60, actual cleanupTimeout=60
2013-04-29 13.44.15,789 com.avaya.sessionsvc.SessionMulticaster addSessionListener
FINE: com.avaya.sessionsvc.SessionServicesImpl$MySessionListener@578ea2added to com.avaya.sessionsvc.SessionMulticaster@baffd4
2013-04-29 13.44.15,789 com.avaya.sessionsvc.SessionObjectImpl start
FINE: session C4E7928EA7BD6CE68BF9990A9F196D1B-396 is starting.
2013-04-29 13.44.16,330 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 2 Routing request=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] com.avaya.csta.binding.GetDeviceId@5b40ce
2013-04-29 13.44.16,330 com.avaya.cs.dataservice.CMInfoDataService <init>
FINE: GOING TO THE DBCONNECTION POOL...
2013-04-29 13.44.16,335 com.avaya.sessionsvc.SessionMulticaster addSessionListener
FINE: com.avaya.cmapi.extsvc.DeviceServicesImpl$MySessionListener@fb9ed2added to com.avaya.sessionsvc.SessionMulticaster@baffd4
2013-04-29 13.44.16,335 com.avaya.cmapi.extsvc.DeviceServicesImpl getDeviceID
INFO: "session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] " mapped to [4380:SWLINK1:10.7.16.18:0] via Client API call
2013-04-29 13.44.16,337 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 2 Received session[null] com.avaya.csta.binding.GetDeviceIdResponse@73b9ae in response to session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] com.avaya.csta.binding.GetDeviceId@5b40ce
2013-04-29 13.44.16,431 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 2797 Routing request=session[session 7C5494018E724B2B316D43BFD6843D7E-391] ch.ecma.csta.binding.SingleStepTransferCall@10c568a
2013-04-29 13.44.16,431 com.avaya.cs.callcontrol.CallControlSnapshotImpl checkForListener
FINE: [7914:SWLINK1:10.7.16.18:0] has ccs listener in session state Active
2013-04-29 13.44.16,431 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 2797 Received com.avaya.platform.broker.impl.AsyncResponse@1c68b6f in response to session[session 7C5494018E724B2B316D43BFD6843D7E-391] ch.ecma.csta.binding.SingleStepTransferCall@10c568a
2013-04-29 13.44.16,440 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 3 Routing request=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] com.avaya.csta.binding.GetThirdPartyDeviceId@10589d8
2013-04-29 13.44.16,440 com.avaya.cs.dataservice.CMInfoDataService <init>
FINE: GOING TO THE DBCONNECTION POOL...
2013-04-29 13.44.16,441 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 3 Received session[null] com.avaya.csta.binding.GetThirdPartyDeviceIdResponse@9cd9f8 in response to session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] com.avaya.csta.binding.GetThirdPartyDeviceId@10589d8
2013-04-29 13.44.16,773 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 2798 Routing request=session[session 7C5494018E724B2B316D43BFD6843D7E-391] ch.ecma.csta.binding.MakeCall@d219d1
2013-04-29 13.44.16,773 com.avaya.cs.callcontrol.CallControlSnapshotImpl checkForListener
FINE: [7912:SWLINK1::0] has ccs listener in session state Active
2013-04-29 13.44.16,773 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 2798 Received com.avaya.platform.broker.impl.AsyncResponse@1c68b6f in response to session[session 7C5494018E724B2B316D43BFD6843D7E-391] ch.ecma.csta.binding.MakeCall@d219d1
2013-04-29 13.44.17,149 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 4 Routing request=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] ch.ecma.csta.binding.MonitorStart@31cf42
2013-04-29 13.44.17,149 com.avaya.cmapi.monitor.MonitoringServicesImpl acquireCrossRefId
FINE: acquired crossRefID=19771: 51 are now in use, 79949 still available.
2013-04-29 13.44.17,149 com.avaya.cmapi.monitor.MonitoringServicesImpl startMonitor
FINE: started monitor=19771
2013-04-29 13.44.17,150 com.avaya.sessionsvc.SessionMulticaster addSessionListener
FINE: com.avaya.cmapi.monitor.MonitoringServicesImpl$MySessionListener@1e0170added to com.avaya.sessionsvc.SessionMulticaster@baffd4
2013-04-29 13.44.17,150 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangeRegistrationFilter
FINE: added RegistrationListener: 19771, id=[4380:SWLINK1:10.7.16.18:0] , listener=com.avaya.cmapi.monitor.RegistrationListenerImpl@1f07089
2013-04-29 13.44.17,150 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangeListeners
FINE: adding/changing other listeners, isCallMonitor=false
2013-04-29 13.44.17,150 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangePhysicalDeviceFilter
FINE: added PhysicalDeviceListener: crossRef=19771, id=[4380:SWLINK1:10.7.16.18:0] , listener=com.avaya.cmapi.monitor.PhysicalDeviceListenerImpl@6c3b92
2013-04-29 13.44.17,150 com.avaya.mvcs.proxy.CstaRouterNode$AsyncHandlerHook processHook
FINE: invokeID= 4 MonitorStartResponse subscribed to the channel 19771 for session=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396,DefaultTCPChannel Bound to SocketAddress: /10.7.16.19:4721 Connected to SocketAddress: /10.6.44.22:6342]
2013-04-29 13.44.17,156 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 4 Received com.avaya.platform.broker.impl.AsyncResponse@1c68b6f in response to session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] ch.ecma.csta.binding.MonitorStart@31cf42
2013-04-29 13.44.17,567 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 5 Routing request=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] ch.ecma.csta.binding.MonitorStart@d59dc6
2013-04-29 13.44.17,567 com.avaya.cmapi.monitor.MonitoringServicesImpl acquireCrossRefId
FINE: acquired crossRefID=19772: 52 are now in use, 79948 still available.
2013-04-29 13.44.17,567 com.avaya.cmapi.monitor.MonitoringServicesImpl startMonitor
FINE: started monitor=19772
2013-04-29 13.44.17,567 com.avaya.cmapi.monitor.MonitoringServicesImpl addChangeListeners
FINE: adding/changing other listeners, isCallMonitor=false
2013-04-29 13.44.17,567 com.avaya.cmapi.monitor.MonitoringServicesImpl createCallControlListener
FINE: invertFilter is not required because protocolVersion=5.2
2013-04-29 13.44.17,568 com.avaya.cmapi.monitor.MonitoringServicesImpl createCallControlServicesListener
FINE: added CallControlListener: 19772, id=[4380:SWLINK1::0] , listener=com.avaya.cmapi.monitor.CallControlServicesListenerImpl@695eb3
2013-04-29 13.44.17,568 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 5 Received com.avaya.platform.broker.impl.AsyncResponse@1c68b6f in response to session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] ch.ecma.csta.binding.MonitorStart@d59dc6
2013-04-29 13.44.17,577 com.avaya.mvcs.proxy.CstaRouterNode$AsyncHandlerHook processHook
FINE: invokeID= 5 MonitorStartResponse subscribed to the channel 19772 for session=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396,DefaultTCPChannel Bound to SocketAddress: /10.7.16.19:4721 Connected to SocketAddress: /10.6.44.22:6342]
2013-04-29 13.44.18,124 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 6 Routing request=session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] com.avaya.csta.binding.RegisterTerminalRequest@1ac5cbe
2013-04-29 13.44.18,124 com.avaya.cmapi.dapilinkmgr.SessionManager sendMessage
WARNING: App attempting to send to an invalid session. Dropping Message.
2013-04-29 13.44.18,124 com.avaya.platform.broker.impl.AsyncServiceMethodImpl invoke
WARNING: Exception when calling method.invoke
java.lang.reflect.InvocationTargetException
   at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at com.avaya.platform.broker.impl.AsyncServiceMethodImpl.invoke(AsyncServiceMethodImpl.java:164)
   at com.avaya.workflow.impl.RouterImpl.routeRequest(RouterImpl.java:97)
   at com.avaya.mvcs.proxy.CstaRouter.routeRequest(CstaRouter.java:173)
   at com.avaya.mvcs.proxy.CstaRouterService.routeRequest(CstaRouterService.java:141)
   at com.avaya.mvcs.proxy.CstaRouterNode.processPacket(CstaRouterNode.java:332)
   at com.avaya.mvcs.proxy.AbstractPipelineNode.process(AbstractPipelineNode.java:130)
   at com.avaya.mvcs.proxy.Pipeline$PipelineSubscriber.inform(Pipeline.java:427)
   at com.avaya.common.eventservice.UnfilteredSubscription.notify(UnfilteredSubscription.java:70)
   at com.avaya.common.multicaster.Multicaster.notify(Multicaster.java:386)
   at com.avaya.common.channel.Channel.publish(Channel.java:115)
   at com.avaya.common.eventservice.EventService.publish(EventService.java:123)
   at com.avaya.common.eventservice.EventServiceManager.publish(EventServiceManager.java:156)
   at com.avaya.common.eventservice.Publisher.publish(Publisher.java:110)
   at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:253)
   at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:53)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
   at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: MCI InvalidCM error: serverID = SWLINK1
   at com.avaya.cmapi.dapilinkmgr.DapiLinkManagerImpl.sendDapiData(DapiLinkManagerImpl.java:262)
   at com.avaya.cmapi.dapilinkmgr.DLMDirectWrapper.sendDapiData(DLMDirectWrapper.java:60)
   at com.avaya.callinfo.CallInfoMCITransport.sendMessage(CallInfoMCITransport.java:323)
   at com.avaya.callinfo.CallInfoMCITransport.syncQueryMessage(CallInfoMCITransport.java:334)
   at com.avaya.callinfo.CallInfoMCITransport.syncQueryProcess(CallInfoMCITransport.java:305)
   at com.avaya.cs.callinfo.DapiHandshake.getSwitchRelease(DapiHandshake.java:235)
   at com.avaya.cs.callinfo.DapiHandshake.isTTSCapableCM(DapiHandshake.java:273)
   at com.avaya.cs.callinfo.CallInfoImplA.isTTSCapableCM(CallInfoImplA.java:1557)
   at com.avaya.cmapi.intsvc.CallInfoHelperServicesImpl.isTTSCapableCM(CallInfoHelperServicesImpl.java:291)
   at com.avaya.cmapi.intsvc.CstaTerminalImpl.isTtsCapable(CstaTerminalImpl.java:352)
   at com.avaya.cmapi.intsvc.CstaTerminalImpl.registerTerminal(CstaTerminalImpl.java:558)
   at com.avaya.cmapi.extsvc.H323RegistrationServices.registerTerminal(H323RegistrationServices.java:99)
   ... 21 more
2013-04-29 13.44.18,125 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 6 Received com.avaya.platform.broker.impl.AsyncResponse@1c68b6f in response to session[session C4E7928EA7BD6CE68BF9990A9F196D1B-396] com.avaya.csta.binding.RegisterTerminalRequest@1ac5cbe
2013-04-29 13.44.18,125 com.avaya.mvcs.proxy.CstaMarshallerNode$CstaMarshallerThread convertThrowable
FINE: Exception is instance of InvocationTargetException
2013-04-29 13.44.18,125 com.avaya.mvcs.proxy.CstaMarshallerNode$CstaMarshallerThread convertThrowable
FINE: InvocationTargetException cause is: java.lang.IllegalArgumentException: MCI InvalidCM error: serverID =
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
I think your problem is with the Switch Name that you used when generating the Device ID and are now using to register the station.

Make sure that your Switch Name is correct and uses the correct case - RegisterTerminal is case sensitive.

Martin
KishorePinnamaneni
Joined: Jan 10, 2014
Messages: 1
Offline
It is working now. Thanks
Go to:   
Mobile view