[asterisk-bugs] [JIRA] (ASTERISK-29441) Core reload making TCP endpoints go offline

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29441:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Core reload making TCP endpoints go offline
> -------------------------------------------
>
>                 Key: ASTERISK-29441
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29441
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 16.18.0
>         Environment: CentOS 7 x64
>            Reporter: Luke Escude
>            Severity: Major
>
> So I updated our Asterisk image last night from 16.14 to the newest, 16.18.
> All of our endpoints use transport-tcp, and the image booted fresh just fine - Everything connected. Including outbound registrations (from Asterisk to an upstream SIP proxy)
> But, every time we perform a 'core reload' all TCP endpoints disconnect and won't re-register (Asterisk begins sending the REGISTER packets over UDP instead of TCP).
> The following errors appear in the console when reloading:
> [May 20 15:45:52] WARNING[8794]: res_pjsip/config_transport.c:559 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
> [May 20 15:45:52] WARNING[8794]: res_pjsip/config_transport.c:559 transport_apply: Transport 'transport-tcp' is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
> Restarting asterisk fixes the issue, but we cannot reload.



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