[asterisk-bugs] [JIRA] (ASTERISK-27161) Local channel incorrectly changes CallerIDNum

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237852#comment-237852 ] 

Asterisk Team commented on ASTERISK-27161:
------------------------------------------

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].

> Local channel incorrectly changes CallerIDNum
> ---------------------------------------------
>
>                 Key: ASTERISK-27161
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27161
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: 13.17.0, 14.6.0
>         Environment: CentOS 6 64bit
>            Reporter: John Lagonikas
>         Attachments: full.0
>
>
> We have detected that, when performing an Originate action through AMI to a local channel using a custom callerid, the local channel changes it's 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:
> action: Originate
> channel: Local/mboZYVBvr5VVkyQtfDkoxvAzQ1 at mb_all_calls
> timeout: 20000
> callerid:  <5432>
> account: TestPhone1
> application: Dial
> data: SIP/TestPhone2,20
> actionid: mboZYVBvr5VVkyQtfDkoxvAzQ1
> async: 1
> variable: 
> The call is then directed by the dialplan to a FastAGI application which performs this single action:
> EXEC "Dial" "SIP/TestPhone1" 
> As you can see in the attached logfile, line 404, the local channel changes its Caller ID to that of the resulting SIP channel.



--
This message was sent by Atlassian JIRA
(v6.2#6252)