Hi! Can someone clarify the status of RFC 4028 (Session Timers) in perspective of a call statefull proxy. I wanted to know .. (1) DO ALL SIP Products comply to this document ? (2) Wat is the Backward compatiablity Procedure (IF ANY Standard) for this to happen.?
Second Question is About determinin Next Hope Adderss, Port, Transport in Section 16 of RFC 3261. IF the Request-URI (which is the TARGET as well( rfc 2361 section 16.4) is sip:[EMAIL PROTECTED]:5060 wat will be the Next HOP address, port, transport according to rfc 3263 and also when this request was received from a SIPP client on TCP Connection. I am asking this question because according to my understanding of rfc 3263 (secion 4.1: Otherwise if no transpoprt protocol is specified, but the TARGET is a numeric IP adderss, the client SHOULD use UDP for a SIP URI and TCP for a SIPS uri) is it my understanding which is wrong or is it some bug in SIPP's default scenarios? anyone any ideas? :( --------------------------------- Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
