On Thu, Apr 30, 2009 at 6:16 AM, Sourav Dhar Chaudhuri <[email protected]> wrote: > hi, > UAS MUST not send 200OK for PRACK and must ignore the PRACK. UAS . This is not correct. The UAS should always send some appropriate final response to end the transaction. In this case, sending final failure response for PRACK is debatable. It is recommended to send 200 OK for PRACK and as Paul pointed out, terminate INVITE transaction with appropriate final response.
> As per RFC 3262 section 5 > > All user agents that support this extension MUST support all > offer/answer exchanges that are possible based on the rules in > Section 13.2 of RFC 3261, based on the existence of INVITE and PRACK > as requests, and 2xx and reliable 1xx as non-failure reliable > responses. > As the first offer answer is not completed. here UAC is violating Section > 13.2 of RFC 3261. So UAS should not entertain the PRACK having offer. > > Thanks > > Sourav > > > > > > ________________________________ > From: Krishna Rao Gurram <[email protected]> > To: "[email protected]" > <[email protected]> > Sent: Thursday, 30 April, 2009 1:50:24 PM > Subject: [Sip-implementors] What is the server side behavior if PRACK with > new SDP receives (Urgent!!!!!!) > > Scenario:- > UAS receives Invite with SDP. > Application above UAS sends 100 Trying > Application now sends 180 without SDP and with 100 rel. > UAS receives PRACK with SDP for 180. > Here what is the behavior of UAS? How to handle this PRACK at the UAS end. > > > Please find the messages. > > INVITE sip:[email protected] SIP/2.0 > Via: SIP/2.0/UDP 172.16.107.21:51594;branch=z9hG4bK629348334-18296 > From: Alice<sip:[email protected]:51594>;tag=abc123def > To: Bob<sip:[email protected] > > Call-ID: [email protected] > Cseq: 1 INVITE > Contact: sip:[email protected]:51594 > Max-Forwards: 70 > Accept: application/sdp > Supported: 100rel, replaces > <------------------------------ > Require:100rel > Content-Type: application/sdp > Content-Length: 131 > > v=0 > o=ICF 12345 787 IN IP4 10.203.154.44 > s=Session > c=IN IP4 10.203.154.44 > t=0 0 > m=audio 4568 RTP/AVP 0 > b=AS:128 > a=ptime:20 > > > SIP/2.0 100 Trying > Via: SIP/2.0/UDP 172.16.107.21:51594;branch=z9hG4bK629348334-18296 > From: Alice<sip:[email protected]:51594>;tag=abc123def > To: Bob<sip:[email protected]>;tag=ICF_4168957464-5666 > Call-ID: [email protected] > ---------------------> > CSeq: 1 INVITE > Supported: timer > Contact: Bob<sip:[email protected]:51591> > Content-Length: 0 > > SIP/2.0 180 Ringing > Via: SIP/2.0/UDP 172.16.107.21:51594;branch=z9hG4bK629348334-18296 > From: Alice<sip:[email protected]:51594>;tag=abc123def > To: Bob<sip:[email protected]>;tag=ICF_4168957464-5666 - - > ---------------> > Call-ID: [email protected] > CSeq: 1 INVITE > Supported: 100rel,replaces,precondition,timer > Require: 100rel > RSeq: 2 > Contact: Bob<sip:[email protected]:51591> > Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,UPDATE > Content-Length: 0 > > > PRACK sip:[email protected] SIP/2.0 > Via: SIP/2.0/UDP 172.16.107.21:51594;branch=z9hG4bK629348334-18296 > From: Alice<sip:[email protected]:51594>;tag=abc123def > To: Bob<sip:[email protected] >;tag=ICF_4168957464-5666 > Call-ID: [email protected] > Cseq: 1 PRACK > Contact: sip:[email protected]:51594 > RAck: 2 1 INVITE > <---------------- > Max-Forwards: 70 > Accept: application/sdp > Expires: 3600 > Supported: replaces,100rel > Require:100rel > Content-type: application/sdp > Content-Length: 131 > > v=0 > o=ICF 12345 788 IN IP4 10.203.154.44 > s=Session > c=IN IP4 10.203.154.44 > t=0 0 > m=audio 4568 RTP/AVP 8 > b=AS:128 > a=ptime:20 > > "DISCLAIMER: This message is proprietary to Aricent and is intended solely > for the use of the individual to whom it is addressed. It may contain > privileged or confidential information and should not be circulated or used > for any purpose other than for what it is intended. If you have received this > message in error,please notify the originator immediately. If you are not the > intended recipient, you are notified that you are strictly prohibited from > using, copying, altering, or disclosing the contents of this message. Aricent > accepts no responsibility for loss or damage arising from the use of the > information transmitted by this email including damage from virus." > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > Now surf faster and smarter ! Check out the new Firefox 3 - Yahoo! > Edition http://downloads.yahoo.com/in/firefox/ > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
