[reSIProcate] on a UAS based on the DUM: Not able to send SDP data Answer in a provisional response

[Scott Godin]

Your right - sendProvisonal was all wrong.  I've committed a fix for it.
Calling provisional() after provideAnswer() will now send the SDP that it
will send with the 200 response.

 

Thanks!

 

Scott

 

  _____  

From: Bellanger Julien [mailto:julien.bellanger at capgemini.com] 
Sent: Tuesday, May 24, 2005 8:01 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] on a UAS based on the DUM: Not able to send SDP data
Answer in a provisional response

 

Hi, 

 

 

I have made an UAS based on the DUM API. When I received an INVITE request
with SDP data, I try to provide an answer to these SDP data in the
provisional response
message SIP/180.
So just before to call the ServerInviteSession::provisional() method, I'm
calling the
ServerInviteSession::provideAnswer() with my SDP data. The problem is that
my SDP data are not sent in the SIP/180 message, they are are sent after in
the
SIP/200 response when I call the accept() method.

After having a look to the code, I think to understand why:

- the ServerInviteSession::provideAnswer() store the SDP content in the
InviteSession::mCurrentLocalSdp member and set the InviteSession::mState
of the call to UAS_OfferProvidedAnswer.

- ServerInviteSession::provisional() call the sendprovisional() method which
always test
and use the InviteSession::mProposedLocalSdp member to eventually send SDP
content
in the provsional response message. But the mProposedLocalSdp is set when we
call
the provideOffer() method but not when the call the provideAnswer() method.

I think the sendprovisional() should test the mState of the Call to know if
it has
to use the mProposedLocalSdp Content or the mCurrentLocalSdp.

Are you agree with that, or am I in a wrong way ?

Thanks in advance,

Julien

This message contains information that may be privileged or confidential and
is the property of the Capgemini Group. It is intended only for the person
to whom it is addressed. If you are not the intended recipient, you are not
authorized to read, print, retain, copy, disseminate, distribute, or use
this message or any part thereof. If you receive this message in error,
please notify the sender immediately and delete all copies of this message.

	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050617/214de946/attachment.htm>