[asterisk-bugs] [JIRA] (ASTERISK-21844) [patch] Realtime TCP endpoints lose registration after

[Matt Jordan (JIRA)]

Matt Jordan created ASTERISK-21844:
--------------------------------------

             Summary: [patch] Realtime TCP endpoints lose registration after 
                 Key: ASTERISK-21844
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21844
             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