[asterisk-bugs] [JIRA] (ASTERISK-25832) sip: password error blocks retries

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229818#comment-229818 ] 

Asterisk Team commented on ASTERISK-25832:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> sip: password error blocks retries
> ----------------------------------
>
>                 Key: ASTERISK-25832
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25832
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 11.21.2, 12.8.2, 13.7.2
>         Environment: any
>            Reporter: Matthias Urlichs
>            Severity: Minor
>
> SIP Registration does not retry if the other side tells us that it doesn't know me.
> This is the wrong thing to do in cases where the remote system uses dynamically-generated SIP peer list and takes some time setting that up after a restart. I have noticed the problem with a Starface peer, which uses a Java/Tomcat front-end to Asterisk -- Asterisk starts up a lot faster than the Tomcat system, thus Asterisk has an empty SIP peer list until Starface is fully operational.
> Asterisk should wait a couple of minutes and then retry.



--
This message was sent by Atlassian JIRA
(v6.2#6252)