[asterisk-bugs] [JIRA] (ASTERISK-22504) [patch] chan_iax2: wrong expiry time in astdb

[Digium Subversion (JIRA)]

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

Digium Subversion closed ASTERISK-22504.
----------------------------------------

    Resolution: Fixed
    
> [patch] chan_iax2: wrong expiry time in astdb
> ---------------------------------------------
>
>                 Key: ASTERISK-22504
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22504
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.5.1
>            Reporter: Stefan Wächtler
>            Assignee: Richard Mudgett
>            Severity: Minor
>         Attachments: chan_iax2.c.patch
>
>
> When a new IAX2 client registers, the astdb database is updated with the value of _minregexpire_ defined in iax.conf instead of using the expiry time that is provided by the client. (The provided expiry time of the client is updated after inserting the astdb entry.)
> As a consequence, restarting or reloading asterisk creates clients whose registration may expire before they reregister. The clients are therefore unavailable after _minregexpire_ seconds until they reregister.
> The correct reregistration time in astdb is only set up, when asterisk detects a change of ip:port of an already registered client that does reregister (astdb is updated in this case).
> Bugfix:
> Use the expiry time provided by the client to update astdb.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira