[asterisk-bugs] [JIRA] (ASTERISK-27667) Commit 8082 - 'Prune subs with reliable transports at startup' causes sourcery/contact to fill up

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27667:
------------------------------------------

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].

> Commit 8082 -  'Prune subs with reliable transports at startup' causes sourcery/contact to fill up
> --------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27667
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27667
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_pubsub
>    Affects Versions: GIT
>         Environment: Fedora 21
>            Reporter: Ross Beer
>              Labels: pjsip
>
> Issue ASTERISK-27612 fixed subscriptions persisting after a reliable transport disconnected. However, on a restart, this process causes the 'sorcery/contact' task process to fill and stops PJSIP processing incoming SIP packets.
> Should the task processor for 'sourcery/contact' allow more entries or should subscription removal be handled in a different way?



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