On Fri, 2006-06-09 at 14:58 -0400, Paul Kyzivat wrote: > I can sympathize with the query - there is some ambiguity. OPTIONS is > required to return the same status it would if the request were INVITE. > But that isn't helpful if you are interested in sending a SUBSCRIBE. > > If the UAS doesn't support INVITE, and returns 405 when receiving one, > should it return a 405 to OPTIONS even though it supports that? > Apparently it must. The UAC can tell the difference based on whether the > Allow header in the response contains OPTIONS or not. > > That is pretty clunky.
My belief is that support of OPTIONS is mandatory, so a UA can never "really" respond 405. Thus, a 405 response always means "If this was an INVITE, I'd respond with 405." That's further proof that it is pretty clunky. Dale --- interop.pingtel.com -- the public SIP phone interoperability test server _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
