Avaya Support Forums  

Go Back   Avaya Support Forums > Small and Medium Business Communications

Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old 11-16-2012, 01:47 AM
stimac stimac is offline
Aspiring Member
Join Date: Jun 2012
Posts: 2
stimac has 10 reputation points
Default TAPI removing a conference master from a manual build up conference call

I'm using TAPI 2.x to connect to IP Office.
I build up an conference call with 2 participants.

(dest 223) ---call---> (dest 221) ---consultation call to ---> (dest 222)
(dest 221) is initiated the conference

The conference master (dest 221) is monitored using TAPI. To build up the conference I use the TAPI functions ::lineSetupTransfere(dest) and ::lineCompleteTransfer(LINETRANSFERMODE_CONFERENCE ).
In this case I receive several events from the TAPI which signals the conference state on the knowing call handles. I receive also events on a new unknown call handle with a new callId which represent the instance of the conference call.

To remove the conference master from the conference call I use the TAPI ::lineDrop() function with the call handle of the conference call. Upon successful completion the conference master (dest 221) is removed from the conference and the other participants (dest 222) and (dest 223) are still in the conference call.

(dest 221) removed from the conference and (dest 222) <--conference--> (dest 223)

This handling works very well but I have an issue when I initiate the conference manualy on the phone device <CONF>dest<CONF> instead of calling the TAPI functions ::lineSetupTransfer() and ::lineComplteTransfer from my application.

My purpose is to remove the conference master (dest 221) out of the conference and the other participants shall still continue the conference.

In this case I receive a completely different event flow as I describe before. I receive two LINE_APPNEWCALL events with the callIds of the old known connections. The new call handle with the callId of the conference call is not signaled in this scenario.
The consequence is, I could not call the ::lineDrop() function from my application to remove the conference master from the conference. I can only disconnect each participants from the conference, but not the conference master.

In the TAPI Reference is mention a function ::lineGetConfRelatedCalls() which return all call handles of the conference in a structure. The first entry of the structure should be the handle of the conference call and the other entries are the participants of the conference. I try this function to determine the conference call in this scenario, but the function return unfortunately LINEERR_NOCONFERENCE. Is this function implemented for the IP Office TAPI?

How can I remove an conference master from the conference while the other participants are still continue the conference call?
Or is there an other way how to get the handle of the conference call to drop the conference?
Are the events in case of manual conference initialization on the phone right?
Have anyone an idea how I can solve the issue?

Thanks in advance.
Reply With Quote

::dropcall, conference, tapi

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 01:04 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.