I’m getting "Got SIP response 405 “Method Not Allowed”’ on asterisk CLI. I have read through the other posts regarding this subject but none seem to apply here.
Because 190.165.XXX.XXX doesn’t support the NOTIFY method, which I think is used for things like message waiting and busy lamp fields (presence). It seems to be lacking and Allow header, which would say what it did support and an a User-Agent one, to say what it is.
190.165.XXX.XXX is broken, because it violates a MUST clause in RFC 3261:
[quote] The UAS MUST also add an Allow
header field to the 405 (Method Not Allowed) response. The Allow
header field MUST list the set of methods supported by the UAS
generating the message. The Allow header field is presented in
Section 20.5.[/quote]
Thanks david55 for pointing me in the right direction. I changed one of my trunks from type=friend to type=peer, after that the “Method Not Allowed” stopped.
This means you are using allowguest=yes as this the default.
Not sure why digium thinks this is a good choice.
You should put allowguest=no in sip.conf
Just to clarify. Although allowguest is a security problem for the vast majority of people who don’t use SIP in a true peer to peer fashion, the relevance here was that, if you have an option in a specific sip.conf entry that is using the disallowed method, you might actually find out that, as a result of changing the sip.conf entry’s type, you are not using that sip.conf entry at all. and the calls are being treated as guest calls.