Summary:	ASTERISK-27662: res_pjsip: Restarting of transport does not wait long enough in all cases
Reporter:	Nikolay (tensor)	Labels:	pjsip
Date Opened:	2018-02-08 05:56:25.000-0600	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Resources/res_pjsip
Versions:	13.17.1	Frequency of Occurrence
Related Issues:
Environment:	hardware: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, 4GB RAM, CentOS Linux release 7.4.1708 (Core), kernel 3.10.0-693.5.2.el7.x86_64, asterisk version is 13.17.1	Attachments:	( 0) diff.txt ( 1) Скриншот_от_12.01.18,_14-40-12.png ( 2) Скриншот_от_12.01.18,_15-56-14.png ( 3) Скриншот_от_12.01.18,_15-59-00.png
Description:	The chan_pjsip module when you reload the settings of transportation releases port 5060. In this case, there was an attempt to occupy the port until his release.
Comments:	By: Asterisk Team (asteriskteam) 2018-02-08 05:56:26.193-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Nikolay (tensor) 2018-02-08 05:58:43.907-0600 log By: Chris Savinovich (csavinovich) 2018-02-11 09:13:38.704-0600 Nikolay, We are going to need you to submit contents of your pjsip_*.conf files. Thanks Chris By: Nikolay (tensor) 2018-02-12 03:16:46.216-0600 I put the changes that were made in the config file. By: Nikolay (tensor) 2018-02-12 03:23:07.118-0600 When faced with a problem. We restored the configuration from the backup and did a reload. Transport rebooted correctly. Then we returned the config with which there were problems, it also loaded correctly. Changes that were made in the config attached to diff.txt By: Chris Savinovich (csavinovich) 2018-02-12 12:49:27.248-0600 I am not sure if I understand you correctly: Are you saying you cannot replicate the issue any more? If so, can you make it happen in a consistent way and then provide us with the details, cause otherwise we won't be able to replicate it here either. Thanks By: Nikolay (tensor) 2018-02-14 01:31:59.685-0600 We can not provide consistent steps to reproduce the problem. We do not know what exactly leads to this situation. You can try to do a lot of reloads and in some cases there will be a crash when trying to occupy the port before it is released. By: Joshua C. Colp (jcolp) 2018-03-08 08:33:27.735-0600 The transport reload functionality is disabled by default for many reasons, and this being one of them. PJSIP does not provide a mechanism to 'restart' transports. To do so in a completely safe fashion requires COMPLETELY tearing down the PJSIP environment and creating it from scratch, which is not currently done. The code attempts to do a restart by getting rid of the old one, waiting some time, and starting a new one. The period of time it waits for may not be enough in all cases.