Summary:	ASTERISK-25985: chan_sip:sip_poke_peer does't copy port
Reporter:	József Dudás (j.dudas)	Labels:
Date Opened:	2016-05-03 09:31:20	Date Closed:	2020-01-14 11:13:57.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/Messaging
Versions:	11.22.0 13.8.2	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:
Description:	When a peer is set to different port than 5060, and SIP OPTIONS is sent by asterisk, the SIP packet does not contain the port number. So if trunk port is 5080 (and not 5060), asterisk still sends OPTIONS sip:aaa.bbb.ccc.ddd and not: OPTIONS sip:aaa.bbb.ccc.ddd:5080 Solvable by adding to channels/chan_sip.c's sip_poke_peer function this: p->portinuri = peer->portinuri;
Comments:	By: Asterisk Team (asteriskteam) 2016-05-03 09:31:21.317-0500 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: Rusty Newton (rnewton) 2016-05-04 09:39:07.599-0500 We can't accept inline patches typically. Would you like to submit a patch and get credit for it? https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process By: Asterisk Team (asteriskteam) 2016-05-18 12:00:01.618-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines