[asterisk-bugs] [JIRA] (ASTERISK-28373) persistant registrations not working for TCP transport

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Fri Apr 5 15:09:47 CDT 2019


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

Joshua C. Colp closed ASTERISK-28373.
-------------------------------------

    Resolution: Not A Bug

This is not a bug.

Generally endpoints require connection reuse, that is they connect to Asterisk and expect that same TCP connection to be reused. This is accomplished using the "rewrite_contact" option. If this is enabled and Asterisk is restarted it prunes the relevant contacts, as the underlying TCP connection has been lost and a new one can not be established back to the endpoint.

> persistant registrations not working for TCP transport
> ------------------------------------------------------
>
>                 Key: ASTERISK-28373
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28373
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.3.0
>         Environment: debian 9 amd64
> asterisk v16.3.0
> using pjsip
> mysql ODBC 
>            Reporter: Michael
>            Severity: Minor
>              Labels: pjsip
>
> not sure what component/s to select.
> With regards to persisant sip registrations, only UDP transport works.  TCP doesn't seem to.  What I observe happening is when I shut down asterisk, and start it back up, all TCP sip registrations are removed from the ps_contacts table but UDP registrations remain.  I've confirmed this in the sql logs.  There are indeed delete commands for the TCP registrations.
> So, when asterisk is restarted, UDP endpoints work right away.  TCP endpoints need to wait until they re-register.



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



More information about the asterisk-bugs mailing list