No, it is not valid behavior. The Allow header should contain only methods that are "allowed" and supported by the UA. It is particularly problematic when you consider that RFC 5057 indicates that a 405 response destroys the INVITE usage.
cheers, (-:bob -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kashif Husain Sent: Wednesday, March 21, 2012 8:33 AM To: [email protected] Subject: [Sip-implementors] 405 response for UPDATE Hello SIP implementors, I have a far-end entity which sends UPDATE in Allow header but when I send UPDATE for session refresh I get 405 Method Not Allowed. Is this a valid behavior? Is it allowed to send 405 in this scenario? If yes then I would like know the reason behind it. Thank you very much in advance. Regards, -kashif _______________________________________________ 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
