[asterisk-bugs] [JIRA] (ASTERISK-25832) chan_sip: Password error blocks registration retries

[Matthias Urlichs (JIRA)]

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

Matthias Urlichs commented on ASTERISK-25832:
---------------------------------------------

Umm, pardon my ignorance, but why would you need a debug trace and configuration? It's pretty obvious from looking at chan_sip.c:handle_response_register() that receiving a 404 error immediately drops any further attempts ("Got 404 Not found on SIP register to service %s@%s, giving up") and de-registers the retry timeout.

The test configuration for this consists of a single "register" entry in sip.conf, directed at a peer which doesn't know about us (obviously it needs "alwaysauthreject = no"). Observe exactly one attempt at registration and a resulting 404 error. That's trivial. Note that there is no peer configuration I could attach to this request.

> chan_sip: Password error blocks registration 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
>            Assignee: Rusty Newton
>            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)