[asterisk-bugs] [JIRA] (ASTERISK-28026) Session timers not updating after reload for active calls

[Jerry Corrion (JIRA)]

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

Jerry Corrion commented on ASTERISK-28026:
------------------------------------------

Hi Benjamin,
Any call that hits 30 minutes drops if a reload was done within the first 15 minutes of the call. This has been consistently replicated.
This is a call center so there are multiple incoming and outgoing calls always going at once. If a reload occurs while any calls are in session,
and then any of those calls reach the 30 minutes mark, the call gets dropped by carrier because the PBX stops sending session timers for the calls active during reload. Most of the calls on this PBX are probably 2-10 minutes for the operators. We have personally tested numerous times over 30 minutes without reload and doesn't happen.
I'll get you some configurations tomorrow morning. Thanks for your response.


> Session timers not updating after reload for active calls
> ---------------------------------------------------------
>
>                 Key: ASTERISK-28026
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28026
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General, pjproject/pjsip
>    Affects Versions: 13.21.1
>            Reporter: Jerry Corrion
>            Assignee: Jerry Corrion
>              Labels: pjsip
>
> When updating a session timer after performing a core reload any call that was in session during the reload gets the following error when attempting to update the session timer.  
> Error in refreshing session timer: Transport not available for use (PJSIP_ETPNOTAVAIL)
> This results in the call being dropped minutes later.



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