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

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-29441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-29441:
--------------------------------------

    Assignee: Luke Escude
      Status: Waiting for Feedback  (was: Triage)

> 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
>            Assignee: 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)