Strange bbehaviorof JTAPI

ashish.nijai — Fri, 23 May 2014 10:03:33 GMT

Dear,

I am using Cisco JTAPI to monitor extensions in Cisco UCM.

I found strange bbehaviorof JTAPI while dialing from JTAPI monitored device.

The call pattern must be like Offered->Dialling->Answered->Disconnected.

Instead I am getting call events like Answered->Dialing->Offered->Disconnected. same thing happens in Transfer mode.

While monitoring incoming call, the JTAPI shows correct pattern of events Ringing->Answered->Disconnected.

Problem in Dialing or transfer events are I am getting multiple events for a single event. I am not sure how to solve it.

I am using events like

CallCtlConnOfferedEv
CallCtlConnDialingEv
CallCtlTermConnRingingEv
CallCtlTermConnTalkingEv
CallCtlTermConnDroppedEv
CallCtlTermConnHeldEv
CiscoTransferStartEv
CiscoTransferEndEv

Kindly waiting for your reply.

Reagrds,

Ashish Nijai

Re: Strange bbehaviorof JTAPI

mpotluri — Tue, 27 May 2014 16:58:59 GMT

Ashish,

The events are for different addresses. You will see CallCtlConnDialingEv for the calling address and CallCtlTermConnRingingEv will be for called terminal. You will see connection events for both calling and called addresses. Terminal connection events are seen for observed addresses/Terminals only. Application needs to use getAddress()/getTerminal() interfaces on these events to find out the corresponding address.

Let me know if this answers your question.

topic Strange bbehaviorof JTAPI in Call Control

Strange bbehaviorof JTAPI

Re: Strange bbehaviorof JTAPI