[asterisk-bugs] [JIRA] (ASTERISK-26696) PJSip Subscription Persistence in AstDB Does not update on refresh

[Zach R (JIRA)]

Zach R created ASTERISK-26696:
---------------------------------

             Summary: PJSip Subscription Persistence in AstDB Does not update on refresh
                 Key: ASTERISK-26696
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26696
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: pjproject/pjsip
    Affects Versions: 13.0.0
         Environment: CentOS 6.6 Final
            Reporter: Zach R
            Severity: Minor


When a phone (say a Cisco SPA 504G) subscribes to a hint about another extension it properly creates the persistence information in the AstDB. But after 30 minutes or whenever the phone sends another subscribe to refresh its subscription the persistence key does not have its expiration timestamp updated to the new time.

This results in the fact subscriptions are not persistent across crashes or restarts, since it sees the subscription as expired when it goes to rebuild subscriptions from the persistence keys. So it would start with no watchers instead of however many it had before the server restarted or crashed.

For example, say extension 500 subscribes to the hint for x501 at 4 AM and has an expiration of 30 minutes. The subscription persistence token in the astdb (database show subscription_persistence) has a timestamp that says it expires at 4:30 AM. Around 4:29 x500 sends a subscribe to refresh the subscription so that it should expire at 5 AM. Yet the astdb database still shows that subscription as expiring at 4:30 AM. 

Say the Asterisk server than restarts at 4:45 AM, when x500's subscription to the hint for x501 is still valid. Once it comes back up the hint for x501 will show as 0 watchers instead of 1 as it was before the restart.



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