[asterisk-bugs] [JIRA] (ASTERISK-30006) Update bundled to 2.12 release stops UDP endpoints

[Joshua C. Colp (JIRA)]

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

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

    Description: 
After pulling the latest GIT version for 16/18 after restarting UDP endpoints can no longer register, however TLS/TCP can.

When rolling back the patch https://gerrit.asterisk.org/c/asterisk/+/18075 everything then works again as expected.

There do not appear to be any errors in the logs when loading, only that qualified peers are unreachable.

All UDP endpoints are affected, those that register or those that have a fixed AOR or are identified by IP.

It looks like the UDP transport isn't listening any longer. This transport is defined as below:

{noformat}
[transport-udp]
type = transport
protocol = udp
bind=0.0.0.0
tos=cs3
async_operations=500
symmetric_transport=yes
{noformat}

The transport is showing as configured:

{noformat}
pjsip show transports

Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress....................>
==========================================================================================

Transport:  transport-tcp             tcp      0     96  0.0.0.0:5060
Transport:  transport-tls             tls      0     96  0.0.0.0:5061
Transport:  transport-udp             udp      0     96  0.0.0.0:5060
{noformat}

If the following line is removed, the transport appears to work correctly:

{noformat}
async_operations=500
{noformat}


  was:
After pulling the latest GIT version for 16/18 after reloading UDP endpoints can no longer register, however TLS/TCP can.

When rolling back the patch https://gerrit.asterisk.org/c/asterisk/+/18075 everything then works again as expected.

There do not appear to be any errors in the logs when loading, only that qualified peers are unreachable.

All UDP endpoints are affected, those that register or those that have a fixed AOR or are identified by IP.

It looks like the UDP transport isn't listening any longer. This transport is defined as below:

{noformat}
[transport-udp]
type = transport
protocol = udp
bind=0.0.0.0
tos=cs3
async_operations=500
symmetric_transport=yes
{noformat}

The transport is showing as configured:

{noformat}
pjsip show transports

Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress....................>
==========================================================================================

Transport:  transport-tcp             tcp      0     96  0.0.0.0:5060
Transport:  transport-tls             tls      0     96  0.0.0.0:5061
Transport:  transport-udp             udp      0     96  0.0.0.0:5060
{noformat}

If the following line is removed, the transport appears to work correctly:

{noformat}
async_operations=500
{noformat}



> Update bundled to 2.12 release stops UDP endpoints
> --------------------------------------------------
>
>                 Key: ASTERISK-30006
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30006
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: GIT, 18.11.0
>         Environment: CentOS
>            Reporter: Ross Beer
>            Assignee: Unassigned
>         Attachments: Ast_No_Reply.PNG
>
>
> After pulling the latest GIT version for 16/18 after restarting UDP endpoints can no longer register, however TLS/TCP can.
> When rolling back the patch https://gerrit.asterisk.org/c/asterisk/+/18075 everything then works again as expected.
> There do not appear to be any errors in the logs when loading, only that qualified peers are unreachable.
> All UDP endpoints are affected, those that register or those that have a fixed AOR or are identified by IP.
> It looks like the UDP transport isn't listening any longer. This transport is defined as below:
> {noformat}
> [transport-udp]
> type = transport
> protocol = udp
> bind=0.0.0.0
> tos=cs3
> async_operations=500
> symmetric_transport=yes
> {noformat}
> The transport is showing as configured:
> {noformat}
> pjsip show transports
> Transport:  <TransportId........>  <Type>  <cos>  <tos>  <BindAddress....................>
> ==========================================================================================
> Transport:  transport-tcp             tcp      0     96  0.0.0.0:5060
> Transport:  transport-tls             tls      0     96  0.0.0.0:5061
> Transport:  transport-udp             udp      0     96  0.0.0.0:5060
> {noformat}
> If the following line is removed, the transport appears to work correctly:
> {noformat}
> async_operations=500
> {noformat}



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