No subject

Be reasonable. The point of a 403 is to inform the UA that it should not
re-send the REGISTER until it has reason to believe that some aspect of the
situation might have changed that would permit the REGISTER to succeed. In
particular, it should not automatically re-send it every few seconds. Thus,
it would be reasonable to re-send under circumstances like:

- the UA is explicitly ordered to by the user
- the UA reinitializes due to user instruction or power-cycling
- the UA is re-provisioned by some provisioning server
- after an extended period, such as 1 hour, to allow for the possibility
that the registration server has been re-provisioned.

All of these have the property that even if the authorization problem has
not been resolved, they do not present an abnormally high load to the
registration server.

                
> [patch] Asterisk not re-registering after it receives "Forbidden - wrong password on authentication"
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-17138
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17138
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/Registration
>            Reporter: Rudi
>         Attachments: 4.patch, sip_log.txt
>
>
> I found a problem with one of our providers. It looks like SIP Trunk stops re-registering after it receives 
> Forbidden - wrong password on authentication
> I have asterisk version 1.4.38 and i have 
> registertimeout=20
> registerattempts=0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira