[asterisk-bugs] [JIRA] (ASTERISK-26247) Change system clock lost ip peers
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Wed Jul 27 19:56:56 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp closed ASTERISK-26247.
----------------------------------
Resolution: Not A Bug
This isn't a bug. Asterisk stores when a contact is no longer valid (when a device registers it tells us how long it is valid for) and by changing the date/time of the system you are taking it past that time, removing it.
> Change system clock lost ip peers
> ---------------------------------
>
> Key: ASTERISK-26247
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26247
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: . I did not set the category correctly.
> Affects Versions: 13.10.0
> Environment: Debian 8 64bits
> Reporter: wushumasters
> Severity: Minor
>
> Hello,
> I dont known if this is a bug, but when i change my clock and put the date/ time to future, asterisk lost the info on astdb of peer
> Before change the date/hour to future:
> /SIP/Registry/1111111111 : 192.168.0.108:57295:3600:1111111111:sip:1111111111 at xxxxxxx:57295;rinstance=a3b1edd86cf0e8f3;transport=UDP
> /SIP/Registry/1140637407 : 192.168.0.108:33945:3600:1140637407:sip:1140637407 at xxxxxx:33945;rinstance=b81ee452cc74df18;transport=UDP
> After change the date/hour to future:
> /SIP/Registry/1111111111 : 192.168.0.108:57295:3600:1111111111:sip:1111111111 at 191.23.122.76:57295;rinstance=a3b1edd86cf0e8f3;transport=UDP
> The information of peer 1140637497 disappeared
> Sorry my english
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list