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

[Dinesh Ramjuttun (JIRA)]

Dinesh Ramjuttun created ASTERISK-21663:
-------------------------------------------

             Summary: 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: 11.3.0, 1.8.21.0
            Reporter: 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.

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 sip, [Prim.Transp. : UDP] but peer setting in sip.conf, [Prim.Transp. : 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