[asterisk-bugs] [JIRA] (ASTERISK-21663) Realtime TCP endpoints lose registration after "sip reload" & "core reload"

[Michael L. Young (JIRA)]

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

Michael L. Young edited comment on ASTERISK-21663 at 4/24/13 8:54 AM:
----------------------------------------------------------------------

Dinesh, please try the attached patch.  One is for 1.8 and the other is for 11.  Please try your settings exactly how you had them when you reported this issue in order to confirm that it fixes the problem of not using the default primary outbound transport when transport is not specified on a per peer basis.

Also, please remember that the order of the transports is important.  If you have "transports=udp,tcp", then UDP will be used as the default.  If you have "transports=tcp,udp" then TCP will be used as the default.

Thanks
                
      was (Author: elguero):
    Dinesh, please try the attached patch.  One is for 1.8 and the other is for 11.  Please try your settings exactly how you had them when you reported this issue in order to confirm that it fixes the problem of not using the default primary outbound transport when transport is not specified on a per peer basis.

Thanks
                  
> Realtime TCP endpoints lose registration after "sip reload" &  "core reload"
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-21663
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21663
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.21.0, 11.3.0
>            Reporter: Dinesh Ramjuttun
>            Assignee: Dinesh Ramjuttun
>            Severity: Minor
>         Attachments: asterisk-21663-outbound-default-transport-fix_11.diff, asterisk-21663-outbound-default-transport-fix_1.8.diff
>
>
> The scenario is as follows:
> - TCP endpoints are being used.
> - transport is set to "udp,tcp" in sip.conf (transport=udp,tcp)
> I have tested with both realtime configuration and flat peer configuration in sip.conf
> After a "sip reload", a realtime TCP peer loses its registration. With qualify=yes set, the TCP peer becomes "unreachable" to asterisk. When that TCP peer is called, sip invites are retransmitted unsuccessfully before giving up. Extension to extension calls cannot go through. Only way to fix this is either by restarting Asterisk or waiting for the peers to re-register again.
> If peer setting is static in sip.conf, the TCP endpoint does not lose its registration.
> I have compared the "sip show peer [peer]" in both cases after a "sip reload" or "core reload". With realtime peers, "sip show peer [peer]" shows primary transport as UDP while "sip show peer [peer]" with static peer in sip.conf ,primary transport is showed as TCP.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira