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

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-25832:
-----------------------------------------

Thanks for the report and debug. However we also need protocol specific debug captured at the time of the issue. Please include the following:

* Asterisk log files generated using the instructions on the Asterisk wiki [1], with the appropriate protocol debug options enabled, e.g. 'pjsip set logger on' if the issue involves the chan_pjsip channel driver.
* Configuration information for the relevant channel driver, e.g. pjsip.conf.
* A wireshark compatible packet capture, captured at the same time as the Asterisk log output.

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> 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
>            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)