Summary:	ASTERISK-26906: chan_sip: With "callbackextension" set, the "port" option is not respected.
Reporter:	wushumasters (wushumasters)	Labels:
Date Opened:	2017-03-29 11:38:58	Date Closed:	2017-03-31 14:49:11
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:	13.14.0	Frequency of Occurrence
Related Issues:	duplicates ASTERISK-23308 [patch] Unable to specify non-standard destination port if "callbackextension" enabled
Environment:	Debian 8 64 Bits	Attachments:	( 0) callbackextensions.txt
Description:	Hello, When the peer has another port like 5090 and callbackextension was configured the port of peer return to 5060. I think the right is take the port and register in same port I attached a test Sorry my english Thanks
Comments:	By: Asterisk Team (asteriskteam) 2017-03-29 11:38:59.130-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) 2017-03-30 19:14:04.805-0500 Have you tested actual communication to verify the problem is not only in the CLI output? By: wushumasters (wushumasters) 2017-03-30 19:29:42.854-0500 Rusty, Yes, is not only CLI output. After set the callbackextension the peer return to port 5060 Thanks By: Rusty Newton (rnewton) 2017-03-31 14:53:00.223-0500 Thanks for the info. Turns out that I'm closing this issue as it is a duplicate. I found ASTERISK-23308 which has been open a while and appears to be the same issue. There is a patch on that issue, you could see if the contributor could update the patch for your version and submit it to Gerrit for review.