<div dir="ltr"><div dir="ltr">On Sat, Jan 9, 2021 at 1:38 AM Michael Maier <<a href="mailto:m1278468@mailbox.org">m1278468@mailbox.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Hello!<br>
<br>
I'm not sure if the following finding is a bug or a feature. Given is a trunk to a registered destination:<br>
<br>
<br>
virtast*CLI> pjsip show registrations<br>
<br>
<Registration/ServerURI..............................> <Auth..........> <Status.......><br>
==========================================================================================<br>
<br>
easybellPJSIP/sip:<a href="http://secure.sip.easybell.de" rel="noreferrer" target="_blank">secure.sip.easybell.de</a> easybellPJSIP Registered<br>
<br>
Objects found: 1<br>
<br>
<br>
The related connection:<br>
# netstat -n | grep 5061<br>
tcp 0 0 <a href="http://192.168.122.174:58709" rel="noreferrer" target="_blank">192.168.122.174:58709</a> <a href="http://212.172.58.207:5061" rel="noreferrer" target="_blank">212.172.58.207:5061</a> ESTABLISHED<br>
<br>
=> That's expected.<br>
<br>
<br>
Now doing an unregister<br>
<br>
pjsip send unregister *all<br>
<br>
gives:<br>
<br>
virtast*CLI> pjsip show registrations<br>
<br>
<Registration/ServerURI..............................> <Auth..........> <Status.......><br>
==========================================================================================<br>
<br>
easybellPJSIP/sip:<a href="http://secure.sip.easybell.de" rel="noreferrer" target="_blank">secure.sip.easybell.de</a> easybellPJSIP Unregistered<br>
<br>
Objects found: 1<br>
<br>
So far so good.<br>
<br>
<br>
But (even after hours - pjsip sends per default tcp/tls keep alives each 90 s):<br>
# netstat -n | grep 5061<br>
tcp 0 0 <a href="http://192.168.122.174:58709" rel="noreferrer" target="_blank">192.168.122.174:58709</a> <a href="http://212.172.58.207:5061" rel="noreferrer" target="_blank">212.172.58.207:5061</a> ESTABLISHED<br>
<br>
=> That's not what I expect.<br>
<br>
Shouldn't the connection been closed after the last trunk to a destination has been closed (there could be more than one numbers / trunks use the same destination / connection - <br>
therefore this would have to be checked before).<br>
<br>
What could be the use case to hold the connection forever even if it is unused?<br>
<br>
<br>
This behavior can be found with Asterisk 18.x (not tested with 16.x).<br></blockquote><div><br></div><div>I believe PJSIP doesn't care or know whether there's anything currently "active" over the connection, and thus it is kept open for when it may be used again. To do otherwise and try to be intelligent is likely a ton of work, which is probably why it was never done. From an Asterisk level we don't really manage the connections and let PJSIP do it.</div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-family:tahoma,sans-serif"><div><font color="#073763">Joshua C. Colp</font></div><div><font color="#073763">Asterisk Technical Lead</font></div><div><font color="#073763">Sangoma Technologies</font></div><div><font color="#073763">Check us out at <a href="http://www.sangoma.com/" target="_blank">www.sangoma.com</a> and <a href="http://www.asterisk.org/" target="_blank">www.asterisk.org</a></font></div></div></div></div></div></div></div></div></div></div></div></div>