Asterisk responds with a 404 to Options requests with no user part, which is what the dispatcher probe builds, 404 shows that UA is up and talking sip, so it should be sufficient to pass the probe. Patch adds 404 status code as a successful result to the probe.
patch accepting 404 as a successful probe result
Hi Kevin,
I do not like this approach with keep adding a build in list to cover all the possibilities for whatsoever device - I'm would rather go for a different approach: default only 200 OK means re-active and you can configure (module params) a list of custom codes to be considered for re-activation.
In this way, everybody will be able to set his own codes without polluting the code itself.
Regards,
Bogdan
Hi Bogdan,
Sounds like a much better approach. I'll consider spending time submitting such a patch in the next week if I can find time. This will be much easier for me in the long run if it's configurable.
Thanks for taking the time to review and respond.
With proper configuration, Asterisk will answer 200 OK.
Just add the "s" extension in the proper context.
Anca will implement configurable set of reply codes to be considered as "successful" probe.
Bogdan
Hi,
I have added a module parameter 'options_reply_codes' that can be set to a list of valid OPTIONS reply codes separated by comma.
200 is considered valid by default.
Example:
modparam("dispatcher", "options_reply_codes", "403, 501, 404")
regards,
Anca
Anca will implement configurable set of reply codes to be considered as "successful" probe.
Bogdan
Sorry - browser refresh error :D..