[asterisk-bugs] [JIRA] (ASTERISK-25832) chan_sip: "Unknown peer" registration error does not retry

[Matthias Urlichs (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Urlichs updated ASTERISK-25832:
----------------------------------------

    Description: 
SIP Registration does not retry after a 404 error.

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.

  was:
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.


> chan_sip: "Unknown peer" registration error does not retry
> ----------------------------------------------------------
>
>                 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 after a 404 error.
> 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)