[asterisk-bugs] [JIRA] (ASTERISK-24844) bridge made with wrong channels using their names

Tue Mar 10 07:23:34 CDT 2015

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

Matt Jordan updated ASTERISK-24844:
-----------------------------------

    Description: 
Sometimes happened to me that trying to make bridges, through AMI, some of them are made linking channels wrong that I said.

For example, in a specific moment, I have next 4 channels to bridge, originate in such order, ch1 before ch2, ch2 before ch3, and so on:
{noformat}
ch1: dahdi/i1/123456789-c145
ch2: iax2/pbx8-19952
ch3: iax2/pbx8-19
ch4: iax2/pbx8-28577
{noformat}

First, I tried to link ch1 and ch2:
{noformat}
action: bridge
actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
channel1: dahdi/i1/123456789-c145
channel2: iax2/pbx8-19952
{noformat}

And is done ok:
{noformat}
event: bridgeaction
privilege: call,all
timestamp: 1414076642.188133
response: success
channel1: dahdi/i1/123456789-c145
channel2: iax2/pbx8-19952
{noformat}

Second, I tried to link ch3 and ch4
{noformat}
action: bridge
actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
channel1: iax2/pbx8-19
channel2: iax2/pbx8-28577
{noformat}

But in this case, instead of receive an ok with above channels, I've received:
{noformat}
action: bridge
actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
channel1: iax2/pbx8-19952
channel2: iax2/pbx8-28577
{noformat}

Notice that the bridge were done between ch4 and ch2, instead of ch4 and ch3.

We made a workaround of this issue launching the action bridges with their uniqueid's instead of channel name's. But I wanted to open an issue for your knowledge. I don't know if is known or not, I don't find it in the issue tracker.

PD: We realized of this issue checking in the code, the function {{ast_channel_by_name_cb}} in main/channel.c, which matches channel names taking only the first part of the name.

PD2: I'm really sorry because I don't have any AMI traces of this issue, happened time ago. 

PD3: Sorry for my English. I hope to be enough clear.

  was:
Sometimes happened to me that trying to make bridges, through AMI, some of them are made linking channels wrong that I said.

For example, in a specific moment, I have next 4 channels to bridge, originate in such order, ch1 before ch2, ch2 before ch3, and so on:
ch1: dahdi/i1/123456789-c145
ch2: iax2/pbx8-19952
ch3: iax2/pbx8-19
ch4: iax2/pbx8-28577

First, I tried to link ch1 and ch2:
action: bridge
actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
channel1: dahdi/i1/123456789-c145
channel2: iax2/pbx8-19952

And is done ok:
event: bridgeaction
privilege: call,all
timestamp: 1414076642.188133
response: success
channel1: dahdi/i1/123456789-c145
channel2: iax2/pbx8-19952

Second, I tried to link ch3 and ch4
action: bridge
actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
channel1: iax2/pbx8-19
channel2: iax2/pbx8-28577

But in this case, instead of receive an ok with above channels, I've received:
action: bridge
actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
channel1: iax2/pbx8-19952
channel2: iax2/pbx8-28577
Notice that the bridge were done between ch4 and ch2, instead of ch4 and ch3.

We made a workaround of this issue launching the action bridges with their uniqueid's instead of channel name's. But I wanted to open an issue for your knowledge. I don't know if is known or not, I don't find it in the issue tracker.

PD: We realized of this issue checking in the code, the function ast_channel_by_name_cb in main/channel.c, which matches channel names taking only the first part of the name.

PD2: I'm really sorry because I don't have any AMI traces of this issue, happened time ago. 

PD3: Sorry for my English. I hope to be enough clear.

> bridge made with wrong channels using their names
> -------------------------------------------------
>
>                 Key: ASTERISK-24844
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24844
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Channels
>    Affects Versions: 11.6.1
>         Environment: ubuntu 12.04 running certified-asterisk-11.6-cert2
>            Reporter: Alberto Sanchez Gonzalez
>            Assignee: Alberto Sanchez Gonzalez
>            Severity: Minor
>         Attachments: asterisk_bridge_channels_wronly_with comments.txt
>
>
> Sometimes happened to me that trying to make bridges, through AMI, some of them are made linking channels wrong that I said.
> For example, in a specific moment, I have next 4 channels to bridge, originate in such order, ch1 before ch2, ch2 before ch3, and so on:
> {noformat}
> ch1: dahdi/i1/123456789-c145
> ch2: iax2/pbx8-19952
> ch3: iax2/pbx8-19
> ch4: iax2/pbx8-28577
> {noformat}
> First, I tried to link ch1 and ch2:
> {noformat}
> action: bridge
> actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
> channel1: dahdi/i1/123456789-c145
> channel2: iax2/pbx8-19952
> {noformat}
> And is done ok:
> {noformat}
> event: bridgeaction
> privilege: call,all
> timestamp: 1414076642.188133
> response: success
> channel1: dahdi/i1/123456789-c145
> channel2: iax2/pbx8-19952
> {noformat}
> Second, I tried to link ch3 and ch4
> {noformat}
> action: bridge
> actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
> channel1: iax2/pbx8-19
> channel2: iax2/pbx8-28577
> {noformat}
> But in this case, instead of receive an ok with above channels, I've received:
> {noformat}
> action: bridge
> actionid: eee7463b-8897-4b1d-b12d-e82957a4c888
> channel1: iax2/pbx8-19952
> channel2: iax2/pbx8-28577
> {noformat}
> Notice that the bridge were done between ch4 and ch2, instead of ch4 and ch3.
> We made a workaround of this issue launching the action bridges with their uniqueid's instead of channel name's. But I wanted to open an issue for your knowledge. I don't know if is known or not, I don't find it in the issue tracker.
> PD: We realized of this issue checking in the code, the function {{ast_channel_by_name_cb}} in main/channel.c, which matches channel names taking only the first part of the name.
> PD2: I'm really sorry because I don't have any AMI traces of this issue, happened time ago. 
> PD3: Sorry for my English. I hope to be enough clear.

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