Summary:ASTERISK-18055: Attempting to register to remote server that returns 404 causes no further registration attempts
Reporter:Jacco van Tuijl (jacco)Labels:chan-sip-register-parsing
Date Opened:2011-06-22 04:38:22Date Closed:
Versions:1.8.4 13.18.4 Frequency of
is related toASTERISK-17138 [patch] Asterisk not re-registering after it receives "Forbidden - wrong password on authentication"
Environment:Attachments:( 0) ASTERISK-18055.patch
Description:some sip servers will return a 404 when trying to register to it while they are still booting.
Asterisk stops retying in this case and connections won't be reastablished

how can I upload a patch for this issue?
Comments:By: Richard Mudgett (rmudgett) 2011-06-22 13:53:38.450-0500

The More Actions pull down menu has Attach files.

By: Matt Jordan (mjordan) 2014-02-14 06:25:06.929-0600

So this patch is not the right solution to this problem. If a server returns a 404, in 99% of the cases, Asterisk has been misconfigured, and continuing to send REGISTER requests to that server would be a bad idea.

As it is, I don't think this is actually a bug, but an improvement.

A better way of solving this would be to extend the {{register_retry_403}} to all failure return codes (note: we should have probably picked a less specific name for that option :-)). That would still solve this problem without breaking the behaviour of failed registrations.