Summary:	ASTERISK-27161: Local channel incorrectly changes its designated CallerIDNum
Reporter:	John Lagonikas (zeleps)	Labels:
Date Opened:	2017-07-27 08:23:23	Date Closed:	2017-07-28 09:08:50
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_local
Versions:	13.17.0 14.6.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	CentOS 6 64bit	Attachments:	( 0) full.0
Description:	We have detected that, when performing an Originate action through AMI to a local channel using a custom callerid, the local channel changes its CallerIDNum to that of the produced SIP channel, instead of retaining the callerid specified in the originate action. This causes the resulting call to present a caller ID number different to the one requested. This behavior was different in asterisk versions 11 and back. The manager action used to produce the call was the following: {noformat} action: Originate channel: Local/mboZYVBvr5VVkyQtfDkoxvAzQ1@mb_all_calls timeout: 20000 callerid:  <5432> account: TestPhone1 application: Dial data: SIP/TestPhone2,20 actionid: mboZYVBvr5VVkyQtfDkoxvAzQ1 async: 1 variable: {noformat} The call is then directed by the dialplan to a FastAGI application which performs this single action: {noformat} EXEC "Dial" "SIP/TestPhone1" {noformat} As you can see in the attached logfile, line 404, the local channel changes its Caller ID to that of the resulting SIP channel. So, the above call arrives at the destination device with a Caller ID number "TestPhone1" instead of "5432".
Comments:	By: Asterisk Team (asteriskteam) 2017-07-27 08:23:24.742-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: John Lagonikas (zeleps) 2017-07-27 08:24:41.873-0500 Asterisk log file with debug verbosity 9. By: Rusty Newton (rnewton) 2017-07-27 11:55:50.192-0500 John, I spoke with a core developer who believes this is normal behavior for recent versions of Asterisk. Check out this page: https://wiki.asterisk.org/wiki/display/AST/Manipulating+Party+ID+Information#ManipulatingPartyIDInformation-PartyIDpropagation Let me know if it makes sense after reading through that. By: Richard Mudgett (rmudgett) 2017-07-27 12:13:36.064-0500 The party ID propagation gives a local channel origination example.  You need to use the Dial 'I' option to block the connected line update to prevent the local channel caller id from being updated. By: John Lagonikas (zeleps) 2017-07-28 02:00:05.650-0500 Rusty, Richard, thank you very much for your answer, the "I" switch does the job. TBH, I did my research on the subject before I posted the issue, but I didn't find anything relevant. Also, the "I" switch exists at least since v. 1.8, but the callerid propagation behavior did not exist until Asterisk 12. Maybe it should be made clear in the documentation that this switch affects callerid propagation specifically, it would greatly help someone researching the issue. By: Rusty Newton (rnewton) 2017-07-28 09:08:50.442-0500 John the documentation looks alright to me. If you have a very specific suggestion where something could be improved (wiki, command line, source, etc) let me know and I'll add it in. You can E-mail me at rnewton at digium dot com.