[asterisk-bugs] [JIRA] (ASTERISK-25476) chan_sip loses registrations after a while

[Stephan Eisvogel (JIRA)]

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

Stephan Eisvogel commented on ASTERISK-25476:
---------------------------------------------

I can confirm for 11-head with PAP2 and Snom 8xx devices that this has been fixed since around December 2015.

> chan_sip loses registrations after a while
> ------------------------------------------
>
>                 Key: ASTERISK-25476
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25476
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.20.0, 13.6.0
>         Environment: AstLinux 1.2.4, Linux 3.2.66, x86 32bit
>            Reporter: Michael Keuter
>            Assignee: Richard Mudgett
>            Severity: Blocker
>      Target Release: 11.21.0, 13.7.0
>
>         Attachments: 11.20.0-SIP-options.txt, asterisk-11-issue-ASTERISK-25476.patch, asterisk-13-issue-ASTERISK-25476.patch, ASTERISK-25476-11.20.0-combined.patch, ASTERISK-25476-13.diff
>
>
> In Asterisk 11.20.0 chan_sip looses registrations of some IP-phones (on several different systems) after a while. In Asterisk the phone then shows "unreachable", while the phone's status shows "Registered". Reverting back to Asterisk 11.19.0 solves the problem. The phones are mostly Yealink phones, different models with different firmwares on different systems, none of the phones firmware was recently upgraded. Dis-/enbling the phone's SIP account or rebooting the phone makes it work again for a while, but then  Asterisk shows the phone again as unreachable.
> I attach a SIP trace of a Yealink W52P DECT base with 2 handsets (331/332). "qualify=yes" is enabled, after a while Asterisk stops sending Option packets to ext. 331 while keeps sending packets to 332.



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