[asterisk-bugs] [JIRA] (ASTERISK-29074) SIP-Reregister timeout based on absolute time

[Benjamin Keith Ford (JIRA)]

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

Benjamin Keith Ford commented on ASTERISK-29074:
------------------------------------------------

The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available.

Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1]

If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way.

[1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[2]: http://www.asterisk.org/community/discuss
[3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties



> SIP-Reregister timeout based on absolute time
> ---------------------------------------------
>
>                 Key: ASTERISK-29074
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29074
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 13.36.0
>            Reporter: Marcel Dischinger
>            Severity: Minor
>
> The timeout for re-registrations at a VoIP-Server seem to be using absolute time instead of relative time. 
> This leads to the following behavior:
> # Device boots, time is t (taken from RTC).
> # Asterisk registers SIP with server
> # NTP updates time to a past time (e.g., (t-2h)) or time is corrected manually by the user
> # Asterisk sends no re-registers until the time is (t+20s). As a result, the registration times out at the server, while asterisk claims it is still registered.
> While I cannot check, it is likely that other Asterisk versions are affected as well.



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