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

[John Lagonikas (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Lagonikas updated ASTERISK-27161:
--------------------------------------

    Description: 
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:

{noformat}
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: 
{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".

  was:
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.


> 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:
> {noformat}
> 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: 
> {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".



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