[asterisk-bugs] [JIRA] (ASTERISK-25832) chan_sip: "Unknown peer" registration error does not retry
Eugene M. Zheganin (JIRA)
noreply at issues.asterisk.org
Sat Oct 15 03:23:01 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232723#comment-232723 ]
Eugene M. Zheganin commented on ASTERISK-25832:
-----------------------------------------------
I'm sitting on this issue with one of my voice providers (11.22.0 from my side). Once a week it rebuilds something in it's peer database, and whan this rebuild clashes with the SIP reregistration, I'm getting a 404 which * then never retries, and my trunk goes in the state "Rejected", and it's unuseable after this.
Any chance this issue would be resolved ? Right now I'm using a nasty cron hack to check if there's a "Rejected" trunk to issue "sip reload"
> 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
> 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 a 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)
More information about the asterisk-bugs
mailing list