Hi Using an emptt Allow: header is the preferred approach. But I think many UA(s) ignore it. So the best way would be to reject the incoming methods with a suitable 4xx - E.g. 405 Method Not Allowed.
Regards Ranjit -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Klaus Darilion Sent: Wednesday, May 26, 2010 11:39 AM To: WORLEY, Dale R (Dale) Cc: Implementors"<[email protected]>"@il27exr02.cig.mot .com Subject: Re: [Sip-implementors] is an empty Allow header allowed? WORLEY, Dale R (Dale) wrote: > ________________________________________ From: > [email protected] > [[email protected]] On Behalf Of Klaus > Darilion [[email protected]] > > Thus, this SIP client only sends REGISTER and PUBLISH, and is not > willing to accept any SIP requests. > > Thus, I wonder if it is correct to signal an empty Allow header > Allow: in the REGISTER request to avoid incoming methods. > > According to ABNF it should be allowed. So is this the preferred way > or is there a better choice? > _______________________________________________ > > It does seem that "Allow:" is a correct way to specify that the UA > will not process any requests. Do you know of any other way to > specify this fact? No. But anyway, I think most clients ignore the Allow header anyway and thus my presence user agent has to be prepared to receive any event and reject it with 405. regards klaus _______________________________________________ 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
