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

[Dinesh Ramjuttun (JIRA)]

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

Dinesh Ramjuttun commented on ASTERISK-21663:
---------------------------------------------

rtcachefriends is set to yes.

I did not explicitly set transport= in realtime table. Setting is explicitly seems to resolve the issue. Have to monitor.

Also, I thought setting transport=tcp,udp in general section of sip.conf sets the value globally for the peers without having to explicitly set it for each peer. I mean, for the static peers in sip.conf, I did not have to explicitly set transport=tcp,udp, yet it defaults to TCP. In realtime, not setting it defaults to UDP?



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