RE: [reSIProcate] How can one deal with 200 OK with incorrect SDP ?
You should send ACK, then BYE.
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Asheesh Joshi
> Sent: Thursday, November 10, 2005 1:18 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] How can one deal with 200 OK with incorrect SDP
?
>
> Hi Gurus,
> A question. What should one do if one receives a 200 OK with incorrect
SDP
> ?
>
> Ie. What is best current practice, if a SIP client sent INVITE, got a
> provisional response that stopped any INVITE retransmission, then got
a
> wrongly formatted 200 OK final response? Should the client just wait
> idle for whatever long until some answer timer in it expired, or
should it
> send
> a BYE immediately after stack sending an ACK for the incorrect 200 OK
?
> We cant send CANCEL right ?
>
> -Regards
> Asheesh.
>
>
>
>
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of
Scott
> Godin
> Sent: Wednesday, November 09, 2005 9:44 PM
> To: Micky Kaufmann; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] ServerInviteSession Bug on provisional
>
> Thanks for the heads up...
>
> Most of the PRACK stuff is not really implemented (ie. the xxxReliable
> states). This will need to be fixed when PRACK is early UPDATES are
> properly completed.
>
> Scott
>
> > -----Original Message-----
> > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-
> > devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Micky Kaufmann
> > Sent: Wednesday, November 09, 2005 11:05 AM
> > To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [reSIProcate] ServerInviteSession Bug on provisional
> >
> > Hi,
> >
> > There's an assertion if provisional is called when a UAS is in the
> > following states:
> > UAS_NoOfferReliable, UAS_EarlyReliable, UAS_FirstSentOfferReliable,
> > UAS_OfferReliable.
> >
> > I don't see any reason for asserting these states.
> >
> > This also means that there might be a bug in the state machine vsd
> > drawing (especially when new events are added without updating the
> > drawing)
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel