< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

RE: [reSIProcate] seinding 183 w/sdp


No you must send the same SDP in the 200 that was sent in the 18x.
There are exceptions if you are using PRACK though.

> -----Original Message-----
> From: Justin Matthews [mailto:justin.matthews@xxxxxxx]
> Sent: Monday, October 10, 2005 5:01 PM
> To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] seinding 183 w/sdp
> 
> Hi,
> 
> The same assertion is triggered when sending a 183 w/SDP and then
calling
> provideAnswer before accepting the call.
> 
> Is it possible to send a 183 with SDP and then send a 200 with
different
> SDP
> (not sure if this is following the spec, but I am seeing this with a
> vendor).
> 
> Thanks,
> 
> -Justin
> 
> -----Original Message-----
> From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
> Sent: Wednesday, October 05, 2005 4:10 PM
> To: Justin Matthews; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] seinding 183 w/sdp
> 
> See http://list.sipfoundry.org/archive/resiprocate-devel/msg03455.html
> 
> 
> > -----Original Message-----
> > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-
> > devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin Matthews
> > Sent: Wednesday, October 05, 2005 3:46 PM
> > To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [reSIProcate] seinding 183 w/sdp
> >
> > Hi,
> >
> > I am getting an assertion on ServerInviteSession.cxx:141.  The
current
> > state
> > is UAS_EarlyProvidedAnswer.  After looking at
> > ServerInviteSession::sendProvisional, it appears that
> > UAS_EarlyProvidedAnswer is valid for sending a provisional.
> >
> > What is the correct procedure for sending a 183 w/SDP after
receiving
> an
> > initial INVITE.  My code is below:
> >
> > serverInviteSession->provideAnswer(*sdp);
> > serverInviteSession->provisional(183);
> >
> > Thanks,
> >
> > -Justin
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel