Author Message
MahendraReddy
Joined: Dec 22, 2008
Messages: 0
Offline
Hi,

We have a setup of AVP and ACD in conjunction with AES-5.2.
We created an Conference IVR application (APP1) which will take another simple IVR application (APP2) in conference with the incoming caller of APP1. Post successfull

conference establishment, the conference application (APP1) will initiate a JTAPI listener and start monitoring the IVR channel on which the conference has been taken

(through "provider.getTerminal(IVR_Channel_no).addCallListener(this)", where "this" being the object of a class extended from

"CallControlTerminalConnectionListenerAdapter"). After the disconnect of APP2, the same event is being thrown by AES to the JTAPI listener and then the conference

application (APP1) is able to proceed forward to do the wrapup stuff. This is working in case if there is a single conference call in the system.

However in case of simultaneous conferences, post the IVR application (APP2) which has been taken into conference as 3rd party gets disconnected for the first

conferenced call, the 3rd-conference party call release event is being notified to all the conferenced calls in the system by the AES which is causing to abruptly end

the conference by all other ports along with the actual concerned port. we have tested and observed the same using "JTAPI Example", which comes along with JTAPI SDK.

Please help us in this regard and guide how to uniquely get the conference party release events on terminal basis so that the other conferenced calls will have no effect.

With Regards
Mahendra
+91-8147944002
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
Hi Mahendra,

It sounds like you are using the same instance of your CallListener class for all calls.

The best solution is to instanciate a new CallListener object for each call. An alternative solution may be to check the callID in the event to make sure you are wrapping up the correct call.

Martin
Go to:   
Mobile view