Conferencing issue & latest stable release?

Hi All,

I have run into conferencing issue yet again (different from
the one below). 
Scenario is -

- I have 2 calls - one active the other on hold.
- I try to add both calls in a conference.
- For this, I first create a conference by calling
sipxConferenceCreate 
(done successfully).
- Next I add the active call into the conference using
sipxConferenceJoin() 
(done successfully).
- Then I try to add the held call into the conference again
using 
sipxConferenceJoin() and this is where problem begins.
Tracing the problem took me to
MpFlowGraphBase::handleAddLink() in which 
check for "pTo->isInputConnected(inPortIdx)"
fails and
throws assertion failures.

Anyone else faced such a problem?

I am actually working on quite an old release of sipxTapi
(some 6-7 months 
old) and not sure if this problem is fixed in newer
releases. Which would be 
the latest stable release? I was looking at the repository 
(http://scm.sipfou
ndry.org/rep/sipX/) but unable to figure out which one 
would be stable (tagged or branched version).

Thanks,
Anshuman



----- Original Message ----- 
From: "Jaroslav Libák" <jarol1seznam.cz>
To: "Anshuman S. Rawat" <arawat3clogic.com>
Cc: <sipxtapi-devlist.sipfoundry.org>
Sent: Monday, August 06, 2007 7:56 PM
Subject: Re: [sipxtapi-dev] Conferencing issue


Try conferencing from wxCommunicator.

m_hLine 0 is not a valid line handle. Handles should always
be greater than 
0.

Jaro

> ------------ Pôvodná správa ------------
> Od: Anshuman S. Rawat <arawat3clogic.com>
> Predmet: [sipxtapi-dev] Conferencing issue
> Dátum: 06.8.2007 15:56:54
> ----------------------------------------
> Hi All,
>
> I am trying to use the conferencing feature of sipXtapi
and have run into
> problems.
>
> Scenario is:
> - Multiple lines exist (4).
> - there is 1 active call (on line 4).
> - other user (not involved in the call) is added to the
conference (line 1
> should be used for this call).
>
> The API  I am using for this purpose is bool 
> sipXmgr::addConfParty(SIPX_CALL
> hCall, const char* const szParty). Conference is
created successfully and
> active call is joined to the conference.
>
> The problem occurs in this function when
sipxConferenceAdd() is called. 
> This
> function expects a parameter of type SIPX_LINE (2nd
param) which is passed
> by calling getCurrentLine(). This function returns a 0
and call to
> sipxConferenceAdd() never returns.
>
> I am not sure how 'm_hLine' (whose value is returned by
getCurrentLine()) 
> is
> set so as to return the correct line or if I am calling
the correct API to
> create a conference in such a case.
>
> Any help in what I am/might be doing wrong will be
appreciated.
>
> Thanks,
> Anshuman
>
> _______________________________________________
> sipxtapi-dev mailing list
> sipxtapi-devlist.sipfoundry.org
> List Archive: http
://list.sipfoundry.org/archive/sipxtapi-dev/
>
>
> 

_______________________________________________
sipxtapi-dev mailing list
sipxtapi-devlist.sipfoundry.org
List Archive: http
://list.sipfoundry.org/archive/sipxtapi-dev/

Hi,

On 8/20/07, Anshuman S. Rawat <arawat3clogic.com> wrote:
> I was looking at the repository (http://scm.sipfou
ndry.org/rep/sipX/)
> but unable to figure out which one would be stable
(tagged or branched
> version).

Only sipXtapi branch, which is actively developped and
supported now
is https://scm.sipfoundry.org/rep/sipX/branches/sipXtapi.
The one you've
mentioned have outdated version of sipXtapi and not
developped anymore.

-- 
Regards,
Alexander Chemeris.

SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000
_______________________________________________
sipxtapi-dev mailing list
sipxtapi-devlist.sipfoundry.org
List Archive: http
://list.sipfoundry.org/archive/sipxtapi-dev/