[asterisk-bugs] [JIRA] (ASTERISK-25861) Subscription timeout earlier than anticipated

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25861:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Subscription timeout earlier than anticipated
> ---------------------------------------------
>
>                 Key: ASTERISK-25861
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25861
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Subscriptions
>    Affects Versions: 11.6.0
>            Reporter: patronic
>
> I'm using a client built with the reSIProcate stack. After a random amount of time, my subscription to presence times out. 
> In the asterisk log file, I can see a SUBSCRIBE comming in at 00:57:48 with a timeout of 60s. Asterisk says it is Scheduling destruction of SIP dialog in 70ms (so at 00:58:58)
> Then for an unknown reason, the client sends another one at 00:58:15. That seems pretty early. But it shouldn't matter. Then Asterisk sends a notify that terminates the subscription with reason=timeout.



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