Re: [Sip-implementors] Strange with PRACK and Linksys

2009-03-20 Thread Paul Kyzivat
Brett Tate wrote: >> Question is have Linksys any reason to not send second PRACK >> after 401 unauthorized? > > No. However RFC 3262 has some wording issues concerning rejecting PRACK. > Some vendors interpreted RFC 3262 as though a PRACK must be accepted and > failure responses like 401 a

Re: [Sip-implementors] Strange with PRACK and Linksys

2009-03-17 Thread Brett Tate
> Question is have Linksys any reason to not send second PRACK > after 401 unauthorized? No. However RFC 3262 has some wording issues concerning rejecting PRACK. Some vendors interpreted RFC 3262 as though a PRACK must be accepted and failure responses like 401 and 488 can still satisfy compl

Re: [Sip-implementors] Strange with PRACK and Linksys

2009-03-17 Thread Igor Goncharovsky
Hello! Thank you for the answer. In our scenario PRACK is mandatory for using UPDATE, and NSN use UPDATE for puporse of implementation call forward on dialog early stage. And such call forward can not be done via 3xx. I am looking if I can find now trace, but can definitly say: yes, all of the 18

Re: [Sip-implementors] Strange with PRACK and Linksys

2009-03-16 Thread Arunachala
Hi Igor, I am NOT very clear regarding the actual usage of 100rel in your scenario. Note that for PRACK generation, '100 Trying' response is NOT considered as provisional response. Linksys should generate PRACK only if the 18x response from NSN had "Require:100rel. " A sniff file with t

[Sip-implementors] Strange with PRACK and Linksys

2009-03-16 Thread Igor Goncharovsky
Hello! We have found that enabling 100rel in Linksys phones break call proceeding with our equipment. Our Nokia-Siemens hiQ4200 support PRACK and supporting of this messages prerequisite for some services provided. The reason is Linksys don't authenticate PRACK (9th packet in callflow bellow): 19