Summary:	ASTERISK-29834: pjsip: Incorrect IP in contact header when using PJSIP TLS with dynamic IP addresses (intermittently)
Reporter:	AdFun7911 (AdFun7911)	Labels:
Date Opened:	2022-01-05 05:24:48.000-0600	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Channels/chan_pjsip
Versions:	16.21.1	Frequency of Occurrence	Occasional
Related Issues:
Environment:	FreePBX 15.0.17.64 RasPBX 5.10.63	Attachments:	( 0) full_log.txt ( 1) hosts.txt ( 2) resolv.conf ( 3) sip_log.txt ( 4) tls_configuration.txt
Description:	Initial situation: PJSIP is configured over TLS and the external IP address of the server is changing. Remote clients try to connect to that server. Every now and then there is no sound on all endpoints when connecting from outside the internal network. After 30 seconds the connection ends. This pointed to RTP. After a reboot (or fwconsole restart in FreePBX, but not fwconsole reload) everything works fine. Analyzing the SIP response made clear that when this issue occurs, instead of the public IP address it sends the internal IP address to all clients outside of the local network. This happens even though dnsmgr is up and running. The domain resolution from FreePBX itself is working as well. Sometimes it is possible to trigger the issue by refreshing the external IP address, but this doesn't always work for some reason. Also sometimes when the IP address changes again, the issue disappears. Full information from FreePBX Community Forums available here: https://community.freepbx.org/t/incorrect-ip-in-contact-header/78265/63
Comments:	By: Asterisk Team (asteriskteam) 2022-01-05 05:24:48.636-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2022-01-05 05:39:32.216-0600 Please attach all of the logs and configuration to this issue. This ensures the information does not get lost. As well please attach the contents of /etc/hosts and /etc/resolv.conf so DNS resolution details can be seen. By: AdFun7911 (AdFun7911) 2022-01-05 11:28:27.101-0600 Added attachments. By: Joshua C. Colp (jcolp) 2022-01-05 11:31:47.860-0600 Please attach all of the logs and other details from the forum as well, so they are contained in one place and so any individual who may want to look at this does not have to try to piece everything together.