This document was generated from CDN thread
Created by: Alejandra Moreno on 03-11-2009 07:20:24 AM
Hi,
I have a cti tool running on a server which upon startup registers statically a pool of cti ports. Upon some events the cti port gets a call, answers, receives the CiscoMediaOpenLogicalChannelEv and starts streaming. Lately only some times we encounter situations where the cti port fails to stream. I debugged and figured out that the cti port does answer the call but something prevents from firing the CiscoMediaOpenLogicalChannelEv event. What could be interfering? thanks.
greetings,
alej
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: David Staudt on 03-11-2009 01:57:44 PM
Can you provide JTAPI logs for an intance of this problem (detailed level, all types)
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 10-11-2009 07:40:36 AM
Hi,
It took some time to post a reply because I have been digging into the JTAPI logs. After making more tests I realized that in the cases where the tool fails I can see in the JTAPI logs the CiscoMediaOpenLogicalChannelEv event
is fired, although with some delay, but the tool doesn't receive it (I have a print out for every event received). Maybe the logs can give a hint:
Case NOK:
Nov 05 14:53:39.157 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent {
eventSequence = 176
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44510126
milliSecondPacketSize = 20
compressionType = 4
mediaConnectionMode = 3
}
5284: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNKP1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent
5285: Nov 05 14:53:39.192 CET %JTAPI-PROTOCOL-7-UNKP1-10.16.17.162) received Event: com.cisco.cti.protocol.StartTransmissionEvent {
eventSequence = 177
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44510126
ipAddr = -2028859382
rtpPortNumber = 17942
milliSecondPacketSize = 20
compressionType = 4
precedenceValue = 184
useSilenceSuppression = false
maxFramesPerPacket = 80
bitRate = 1
mediaDeviceName =
mediaResourceId = 0
mediaConnectionMode = 3
}
5286: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNKP1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.StartTransmissionEvent
5287: Nov 05 14:53:39.192 CET %JTAPI-CTIIMPL-7-UNKP1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent[176]
5288: Nov 05 14:53:39.192 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670811/2),CID=44510126] On DeviceP1-CCMSNP) CTIP_SNP02_08(2,98748) CallOpenLogicalChannel : MediaConnectionMode =3
5289: Nov 05 14:53:39.192 CET %JTAPI-JTAPI-7-UNKP1-CCMSNP) [CTIP_SNP02_08] CiscoMediaOpenLogicalChannelEv [#535] Cause:100 CallCtlCause:0 CiscoFeatureReason:12
5290: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
5291: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
5292: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
5293: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
5294: Nov 05 14:53:39.192 CET %JTAPI-CTIIMPL-7-UNKP1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.StartTransmissionEvent[177]
5295: Nov 05 14:53:39.192 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670811/2),CID=44510126] On DeviceP1-CCMSNP) CTIP_SNP02_08(2,98748) StartTransmission MediaConnectionMode:3
5296: Nov 05 14:53:39.192 CET %JTAPI-JTAPI-7-UNKP1-CCMSNP) [CTIP_SNP02_08] CiscoRTPOutputStartedEv [#536] Cause:100 CallCtlCause:0 CiscoFeatureReason:12
5297: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
5298: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
5299: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
5300: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
5301: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5302: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JCES[2]
5303: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5304: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to callChangedEvent
5305: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5306: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JCES[4]
5307: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5308: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to callChangedEvent
5309: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5310: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JTES[1]
5311: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5312: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to terminalChangedEvent
5313: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5314: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JTES[1]
5315: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5316: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to terminalChangedEvent
5317: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5318: Nov 05 14:53:43.152 CET %JTAPI-PROTOCOL-7-UNKP1-10.16.17.162) received Event: com.cisco.cti.protocol.StopTransmissionEvent {
eventSequence = 178
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44510126
mediaDeviceName =
mediaResourceId = 0
mediaConnectionMode = 3
}
5319: Nov 05 14:53:43.152 CET %JTAPI-MISC-7-UNKP1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.StopTransmissionEvent
5320: Nov 05 14:53:43.152 CET %JTAPI-CTIIMPL-7-UNKP1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.StopTransmissionEvent[178]
5321: Nov 05 14:53:43.152 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670811/2),CID=44510126] On DeviceP1-CCMSNP) CTIP_SNP02_08(2,98748) StopTransmission MediaConnectionMode:3
5322: Nov 05 14:53:43.152 CET %JTAPI-JTAPI-7-UNKP1-CCMSNP) [CTIP_SNP02_08] CiscoRTPOutputStoppedEv [#537] Cause:100 CallCtlCause:0 CiscoFeatureReason:12
5323: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
5324: Nov 05 14:53:43.152 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
5325: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
5326: Nov 05 14:53:43.152 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
5327: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JTES[1]
5328: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5329: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to terminalChangedEvent
5330: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
Case OK:
Nov 05 14:51:39.242 CET %JTAPI-PROTOCOL-7-UNKP1-10.16.17.162) received Event: com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent {
eventSequence = 45
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44509602
milliSecondPacketSize = 20
compressionType = 4
mediaConnectionMode = 3
}
1363: Nov 05 14:51:39.242 CET %JTAPI-MISC-7-UNKP1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent
1364: Nov 05 14:51:39.242 CET %JTAPI-CTIIMPL-7-UNKP1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent[45]
1365: Nov 05 14:51:39.242 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670671/2),CID=44509602] On DeviceP1-CCMSNP) CTIP_SNP02_08(2,98748) CallOpenLogicalChannel : MediaConnectionMode =3
1366: Nov 05 14:51:39.243 CET %JTAPI-JTAPI-7-UNKP1-CCMSNP) [CTIP_SNP02_08] CiscoMediaOpenLogicalChannelEv [#91] Cause:100 CallCtlCause:0 CiscoFeatureReason:12
1367: Nov 05 14:51:39.243 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
1368: Nov 05 14:51:39.243 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
1369: Nov 05 14:51:39.243 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
1370: Nov 05 14:51:39.243 CET %JTAPI-MISC-7-UNKbserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet
1371: Nov 05 14:51:39.245 CET %JTAPI-JTAPIIMPL-7-UNKbserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): delivering JTES[1]
1372: Nov 05 14:51:39.245 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.deliverEvents()
1373: Nov 05 14:51:39.245 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]delivering to terminalChangedEvent
1374: Nov 05 14:51:39.263 CET %JTAPI-PROTOCOL-7-UNKP1-10.16.17.162) received Event: com.cisco.cti.protocol.StartTransmissionEvent {
eventSequence = 46
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44509602
ipAddr = 1024397322
rtpPortNumber = 28710
milliSecondPacketSize = 20
compressionType = 4
precedenceValue = 184
useSilenceSuppression = false
maxFramesPerPacket = 80
bitRate = 1
mediaDeviceName =
mediaResourceId = 0
mediaConnectionMode = 3
}
1375: Nov 05 14:51:39.263 CET %JTAPI-MISC-7-UNKP1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.StartTransmissionEvent
1376: Nov 05 14:51:39.264 CET %JTAPI-PROTOCOL-7-UNKP1-10.16.17.162) received Event: com.cisco.cti.protocol.CallStateChangedEvent {
In the case where it fails the teminalChangedEvent is NOT delivered to the class framework.jtapi.CTImediaTerminal which should trace this event and start the streaming to the CTI port. Why is this hapenning only sometimes?
thanks! alej
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 23-11-2009 09:49:46 AM
Hi again,
I have been further investigating and I arrived to the conclusion that in SOME cases the mediaTerm events are not delivered to my observer. After getting
EventThread: queuing com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent
the following events are missing:
22948: Nov 20 15:43:22.436 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(mailto:framework.jtapi.CTImediaTerminal@164dbd5): delivering JTES[1]
22949: Nov 20 15:43:22.436 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@164dbd5]ObserverProxy.deliverEvents()
22950: Nov 20 15:43:22.436 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@164dbd5]delivering to terminalChangedEvent
I have one call observer and a mediaTerm observer, both as separate instances to avoid interferences in the queueing of events. Any ideas why this could be hapenning?
thanks,
alej
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Roland Russwurm on 18-01-2010 09:37:25 AM
I have seen the same problem already although it occurs quite rarely and a restart of the application always helped to get it working again. Still I would also be very interested what is the cause of this issue and how it can be fixed.
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 18-01-2010 03:51:56 PM
I never got any answer...and the problem persists.
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Mohan Potluri on 27-01-2010 09:51:07 AM
based on the trace snippet, the event seems to be delivered to the terminal observer.
Can you attach the full JTAPI log?
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 28-01-2010 08:12:52 AM
Would you be as kind as to point out where you see the event is delivered? The relevant lines are posted, you would be lost if I attach all log files; it's a huge api.
thanks,
alej
Created by: Alejandra Moreno on 03-11-2009 07:20:24 AM
Hi,
I have a cti tool running on a server which upon startup registers statically a pool of cti ports. Upon some events the cti port gets a call, answers, receives the CiscoMediaOpenLogicalChannelEv and starts streaming. Lately only some times we encounter situations where the cti port fails to stream. I debugged and figured out that the cti port does answer the call but something prevents from firing the CiscoMediaOpenLogicalChannelEv event. What could be interfering? thanks.
greetings,
alej
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: David Staudt on 03-11-2009 01:57:44 PM
Can you provide JTAPI logs for an intance of this problem (detailed level, all types)
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 10-11-2009 07:40:36 AM
Hi,
It took some time to post a reply because I have been digging into the JTAPI logs. After making more tests I realized that in the cases where the tool fails I can see in the JTAPI logs the CiscoMediaOpenLogicalChannelEv event
is fired, although with some delay, but the tool doesn't receive it (I have a print out for every event received). Maybe the logs can give a hint:
Case NOK:
Nov 05 14:53:39.157 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent {eventSequence = 176
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44510126
milliSecondPacketSize = 20
compressionType = 4
mediaConnectionMode = 3
}
5284: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
P1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent5285: Nov 05 14:53:39.192 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.StartTransmissionEvent {eventSequence = 177
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44510126
ipAddr = -2028859382
rtpPortNumber = 17942
milliSecondPacketSize = 20
compressionType = 4
precedenceValue = 184
useSilenceSuppression = false
maxFramesPerPacket = 80
bitRate = 1
mediaDeviceName =
mediaResourceId = 0
mediaConnectionMode = 3
}
5286: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
P1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.StartTransmissionEvent5287: Nov 05 14:53:39.192 CET %JTAPI-CTIIMPL-7-UNK
P1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent[176]5288: Nov 05 14:53:39.192 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670811/2),CID=44510126] On Device
P1-CCMSNP) CTIP_SNP02_08(2,98748) CallOpenLogicalChannel : MediaConnectionMode =35289: Nov 05 14:53:39.192 CET %JTAPI-JTAPI-7-UNK
P1-CCMSNP) [CTIP_SNP02_08] CiscoMediaOpenLogicalChannelEv [#535] Cause:100 CallCtlCause:0 CiscoFeatureReason:125290: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
5291: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet5292: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
5293: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet5294: Nov 05 14:53:39.192 CET %JTAPI-CTIIMPL-7-UNK
P1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.StartTransmissionEvent[177]5295: Nov 05 14:53:39.192 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670811/2),CID=44510126] On Device
P1-CCMSNP) CTIP_SNP02_08(2,98748) StartTransmission MediaConnectionMode:35296: Nov 05 14:53:39.192 CET %JTAPI-JTAPI-7-UNK
P1-CCMSNP) [CTIP_SNP02_08] CiscoRTPOutputStartedEv [#536] Cause:100 CallCtlCause:0 CiscoFeatureReason:125297: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
5298: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet5299: Nov 05 14:53:39.192 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
5300: Nov 05 14:53:39.192 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet5301: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5302: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JCES[2]5303: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5304: Nov 05 14:53:39.237 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to callChangedEvent
5305: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5306: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JCES[4]5307: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5308: Nov 05 14:53:39.240 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to callChangedEvent
5309: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5310: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JTES[1]5311: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5312: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to terminalChangedEvent
5313: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5314: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JTES[1]5315: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5316: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to terminalChangedEvent
5317: Nov 05 14:53:39.244 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
5318: Nov 05 14:53:43.152 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.StopTransmissionEvent {eventSequence = 178
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44510126
mediaDeviceName =
mediaResourceId = 0
mediaConnectionMode = 3
}
5319: Nov 05 14:53:43.152 CET %JTAPI-MISC-7-UNK
P1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.StopTransmissionEvent5320: Nov 05 14:53:43.152 CET %JTAPI-CTIIMPL-7-UNK
P1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.StopTransmissionEvent[178]5321: Nov 05 14:53:43.152 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670811/2),CID=44510126] On Device
P1-CCMSNP) CTIP_SNP02_08(2,98748) StopTransmission MediaConnectionMode:35322: Nov 05 14:53:43.152 CET %JTAPI-JTAPI-7-UNK
P1-CCMSNP) [CTIP_SNP02_08] CiscoRTPOutputStoppedEv [#537] Cause:100 CallCtlCause:0 CiscoFeatureReason:125323: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
5324: Nov 05 14:53:43.152 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet5325: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
5326: Nov 05 14:53:43.152 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet5327: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): delivering JTES[1]5328: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents()
5329: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]delivering to terminalChangedEvent
5330: Nov 05 14:53:43.152 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.deliverEvents() completed
Case OK:
Nov 05 14:51:39.242 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent {eventSequence = 45
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44509602
milliSecondPacketSize = 20
compressionType = 4
mediaConnectionMode = 3
}
1363: Nov 05 14:51:39.242 CET %JTAPI-MISC-7-UNK
P1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent1364: Nov 05 14:51:39.242 CET %JTAPI-CTIIMPL-7-UNK
P1-10.16.17.162) EventThread handling event com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent[45]1365: Nov 05 14:51:39.242 CET %JTAPI-CTI-7-UNK:Call:[GCID=(4670671/2),CID=44509602] On Device
P1-CCMSNP) CTIP_SNP02_08(2,98748) CallOpenLogicalChannel : MediaConnectionMode =31366: Nov 05 14:51:39.243 CET %JTAPI-JTAPI-7-UNK
P1-CCMSNP) [CTIP_SNP02_08] CiscoMediaOpenLogicalChannelEv [#91] Cause:100 CallCtlCause:0 CiscoFeatureReason:121367: Nov 05 14:51:39.243 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.queueEvents: queuing asynchronously
1368: Nov 05 14:51:39.243 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet1369: Nov 05 14:51:39.243 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTIaddress@c39a20]ObserverProxy.queueEvents: queuing asynchronously
1370: Nov 05 14:51:39.243 CET %JTAPI-MISC-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTIaddress@c39a20</a>]): queuing com.cisco.jtapi.JtapiTerminalEventSet1371: Nov 05 14:51:39.245 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(<a>mailto:framework.jtapi.CTImediaTerminal@e1899b</a>]): delivering JTES[1]1372: Nov 05 14:51:39.245 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]ObserverProxy.deliverEvents()
1373: Nov 05 14:51:39.245 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@e1899b]delivering to terminalChangedEvent
1374: Nov 05 14:51:39.263 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.StartTransmissionEvent {eventSequence = 46
deviceCallManagerID = 2
deviceID = 98748
callCallManagerID = 2
callLegID = 44509602
ipAddr = 1024397322
rtpPortNumber = 28710
milliSecondPacketSize = 20
compressionType = 4
precedenceValue = 184
useSilenceSuppression = false
maxFramesPerPacket = 80
bitRate = 1
mediaDeviceName =
mediaResourceId = 0
mediaConnectionMode = 3
}
1375: Nov 05 14:51:39.263 CET %JTAPI-MISC-7-UNK
P1-10.16.17.162) EventThread: queuing com.cisco.cti.protocol.StartTransmissionEvent1376: Nov 05 14:51:39.264 CET %JTAPI-PROTOCOL-7-UNK
P1-10.16.17.162) received Event: com.cisco.cti.protocol.CallStateChangedEvent {In the case where it fails the teminalChangedEvent is NOT delivered to the class framework.jtapi.CTImediaTerminal which should trace this event and start the streaming to the CTI port. Why is this hapenning only sometimes?
thanks! alej
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 23-11-2009 09:49:46 AM
Hi again,
I have been further investigating and I arrived to the conclusion that in SOME cases the mediaTerm events are not delivered to my observer. After getting
EventThread: queuing com.cisco.cti.protocol.DeviceCallOpenLogicalChannelEvent
the following events are missing:
22948: Nov 20 15:43:22.436 CET %JTAPI-JTAPIIMPL-7-UNK
bserverThread(mailto:framework.jtapi.CTImediaTerminal@164dbd5): delivering JTES[1]22949: Nov 20 15:43:22.436 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@164dbd5]ObserverProxy.deliverEvents()
22950: Nov 20 15:43:22.436 CET %JTAPI-JTAPIIMPL-7-UNK:[framework.jtapi.CTImediaTerminal@164dbd5]delivering to terminalChangedEvent
I have one call observer and a mediaTerm observer, both as separate instances to avoid interferences in the queueing of events. Any ideas why this could be hapenning?
thanks,
alej
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Roland Russwurm on 18-01-2010 09:37:25 AM
I have seen the same problem already although it occurs quite rarely and a restart of the application always helped to get it working again. Still I would also be very interested what is the cause of this issue and how it can be fixed.
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 18-01-2010 03:51:56 PM
I never got any answer...and the problem persists.
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Mohan Potluri on 27-01-2010 09:51:07 AM
based on the trace snippet, the event seems to be delivered to the terminal observer.
Can you attach the full JTAPI log?
Subject: RE: CiscoMediaOpenLogicalChannelEv not received
Replied by: Alejandra Moreno on 28-01-2010 08:12:52 AM
Would you be as kind as to point out where you see the event is delivered? The relevant lines are posted, you would be lost if I attach all log files; it's a huge api.
thanks,
alej