[reSIProcate] Sending SDP in 183 for ServerInviteSession inUAS_EarlyProvidedOffer state

[Scott Godin]

I think calling the api in that order should be legal - but in this case
I don't think that the SDP offer is allowed in the unreliable
provisional response.  We should probably just send the 180 without sdp
and send the sdp when the 200 is sent.  Anyone else?

Scott

> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org
> [mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
> Justin Matthews
> Sent: Thursday, September 07, 2006 3:20 PM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] Sending SDP in 183 for ServerInviteSession
> inUAS_EarlyProvidedOffer state
> 
> Hello,
> 
> Is it valid to call provideOffer and then sendProvisional(183) for a
> ServerInviteSession in the UAS_EarlyProvidedOffer state?
> 
> The ServerInviteSession is in the UAS_EarlyProvidedOffer state after
> receiving an INVITE with no SDP.
> 
> Thanks,
> 
> -Justin
> 
> 
> ServerInviteSession::sendProvisional(int code) {
>    mDialog.makeResponse(*m1xx, mFirstRequest, code);
>    switch (mState)
>    {
>       case UAS_OfferProvidedAnswer:
>       case UAS_EarlyProvidedAnswer:
> 
> 	/**!!! INSERTED HERE ----> */
> 	case UAS_EarlyProvidedOffer:
> 
>          if (mCurrentLocalSdp.get()) // early media
>          {
>             setSdp(*m1xx, mCurrentLocalSdp.get());
>          }
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel