Hi, Can any one quickly clarify on the below race condition. UAC UAS INVITE ---------> 100 Trying <--------- BYE --- --- \ / \ / \ 480 (to INVITE) <--- ---> ACK (to 480) ---------> 481 (to BYE) <---------Here need clarification on UAC as well as UAS behavior.
1. Do we need to send the ACK for 480 from UAC? 2. If UAC has sent the ACK what should be the UAS behavior? Do we need to process the ACK at UAS side or discard the ACK? Thanks in Advance. Regards, Kavitha.M --- On Sat, 26/7/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Subject: Sip-implementors Digest, Vol 64, Issue 42 To: [email protected] Date: Saturday, 26 July, 2008, 9:30 PM Send Sip-implementors mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Sip-implementors digest..." Today's Topics: 1. Re: Does verion in o line needs incremented byone for each SDP answer? ([EMAIL PROTECTED]) ---------------------------------------------------------------------- Message: 1 Date: Fri, 25 Jul 2008 13:50:20 -0400 From: [EMAIL PROTECTED] Subject: Re: [Sip-implementors] Does verion in o line needs incremented byone for each SDP answer? To: [email protected] Message-ID: <[EMAIL PROTECTED]> From: "Rockson Li (zhengyli)" <[EMAIL PROTECTED]> Thanks Dale, is this bug documented? Section 5.2.5 of draft-ietf-sipping-sip-offeranswer-08 "SIP (Session Initiation Protocol) Usage of the Offer/Answer Model" clarifies it: 5.2.5. Subsequent Offers and Answers The guidelines above (sections 5.1. and 5.2.1. through 5.2.4. ) apply, but constraints in RFC 3264 [4] must also be followed. The following are of particular note because they have proven troublesome: [...] o In the o-line, only the version number may change, and if it changes it must increment by one from the one previously sent as an offer or answer. (RFC 3264 [4] section 8.) If it doesn't change then the entire SDP body must be identical to what was previously sent as an offer or answer. Changing the o-line, except version number value, during the session is an error case. The behavior when receiving such a non-compliant offer/answer SDP body is implementation dependent. If a UA needs to negotiate a 'new' SDP session, it should use the INVITE/Replaces method. Dale ------------------------------ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors End of Sip-implementors Digest, Vol 64, Issue 42 ************************************************ From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
