[asterisk-bugs] [JIRA] (ASTERISK-19948) Asterisk 1.8 manager redirect command fails when redirecting multiple channels currently bridged together via dial command.

Tue Nov 6 23:33:21 CST 2012

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

Deepak Lohani commented on ASTERISK-19948:
------------------------------------------

Greeting,
We have also been experiencing  this issue since we upgraded to Asterisk 1.8 from 1.6.Wheever we try to redirect to channels, extra channels gets hang.We uses this feature to put two channels in conference.

> Asterisk 1.8 manager redirect command fails when redirecting multiple channels currently bridged together via dial command.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19948
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19948
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 1.8.12.2, 1.8.13.0
>         Environment: Centos 5.7 x86_64
>            Reporter: Brent Dalgleish
>         Attachments: dialplan.inc, issue_19948.log
>
>
> Have observed a problem with asterisk 1.8 (versions 1.8.3.2, 1.8.12.2,1.8.13.0-rc2 all behave the same) and using the manager redirect command to redirect two channels which are bridged together via dial command to alternate locations.
> When the redirect is attempted, the following error is received on the second channel:
> [Jun  4 13:06:29] WARNING[24411]: channel.c:5874 __ast_channel_masquerade: Can't setup masquerade. One or both channels is dead. (AsyncGoto/SIP/30-00000001 <-- SIP/30-00000001)
> Have previously used this on multiple 1.6 version with no problem (manager.c was patched to include Extra channel options from 1.8).
> Any help would be great, thank you.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira