[Home]

Summary:ASTERISK-27011: ExtraChannel closed on AMI Redirect
Reporter:Boris Barabanov (boristheblade)Labels:
Date Opened:2017-05-20 23:54:38Date Closed:2017-05-22 06:50:04
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:13.8.0 13.11.2 13.15.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Installed Packages Name : asterisk13-core Arch : x86_64 Version : 13.15.0 Release : 1.shmz65.1.158 Size : 16 M Repo : installed From repo : pbx Summary : Asterisk core package without any "extras". URL : http://www.asterisk.org License : GPL Description : This package contains a base install of Asterisk without any "extras".Attachments:( 0) AMI.txt
( 1) full-log.txt
Description:Have 2 bridged channels. Try to redirect  via AMI and one leg is hangups.
Comments:By: Asterisk Team (asteriskteam) 2017-05-20 23:54:40.130-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: Boris Barabanov (boristheblade) 2017-05-20 23:57:43.763-0500

This is log of call and AMI action description
By: Boris Barabanov (boristheblade) 2017-05-21 01:05:52.641-0500

also i try ChannelRedirect via Dynamic feature with same result.
I try few different asterisk versions:13.7.2 - all is ok, 13.8.0 and above - bug exist

features.conf
{code}
app_tst=> 7,self,Macro,preQCB
{code}
extensions.conf
{code}
[ctBTest]
exten => 300,1,Noop()
exten => 300,n,Set(__DYNAMIC_FEATURES=app_tst)
exten => 300,n,Dial(SIP/300)

[macro-preQCB]
exten => s,1,ChannelRedirect(${BRIDGEPEER},ctQCB11,s,1)
exten => s,n,ChannelRedirect(${CHANNEL},ctQCB11,s,1)

[ctQCB11]
exten => s,1,Noop()
exten => s,n,Wait(100)
{code}

log:
{code}
[2017-05-21 08:52:34] DTMF[12659][C-00000001]: channel.c:4096 __ast_read: DTMF end passthrough '7' on SIP/100-00000002
   -- Executing [s@macro-preQCB:1] ChannelRedirect("SIP/100-00000002", "SIP/300-00000003,ctQCB11,s,1") in new stack
   -- Channel SIP/300-00000003 left 'simple_bridge' basic-bridge <73c91a73-8bf0-4cf7-8d7f-cdd7fc96d544>
   -- Executing [s@ctQCB11:1] NoOp("SIP/300-00000003", "") in new stack
   -- Executing [s@ctQCB11:2] Wait("SIP/300-00000003", "100") in new stack
   -- Executing [s@macro-preQCB:2] ChannelRedirect("SIP/100-00000002", "SIP/100-00000002,ctQCB11,s,1") in new stack
 == Channel 'SIP/100-00000002' jumping out of macro 'preQCB'
   -- Channel SIP/100-00000002 left 'simple_bridge' basic-bridge <73c91a73-8bf0-4cf7-8d7f-cdd7fc96d544>
   -- Executing [s@ctQCB11:1] NoOp("SIP/100-00000002", "") in new stack
 == Spawn extension (ctQCB11, s, 2) exited non-zero on 'SIP/300-00000003'

{code}
By: Richard Mudgett (rmudgett) 2017-05-21 08:04:50.089-0500

Since the two channels you are trying to redirect are in the same bridge you have to redirect them at the same time.  Otherwise the other channel hangs up before you can redirect it.  You cannot do this using the ChannelRedirect application since that can only do one channel at a time.  The AMI Redirect action can do this.  However, the [^AMI.txt] file you attached will not do this since you specified the other channel using the wrong header: {{ExtraContext: SIP/300-0000004d}}.  The header should be {{ExtraChannel}}.
By: Boris Barabanov (boristheblade) 2017-05-21 08:15:49.037-0500

Yes Richard, you are right, i mistyped in AMI, I will  check Redirect via AMI.
But I try ChannelRedirect on version 13.7.2., ie first i redirects leg bridged to channel which run DynamicFeature, then i redirecting channel self - this working, on versions upper 13.7.2 - not.

UPD: AMI Redirect works like a charm.
Should i create new ticket about ChannelRedirect or can edit this one ?
By: Joshua C. Colp (jcolp) 2017-05-22 06:50:05.040-0500

We don't currently accept feature requests on the issue tracker. You may try eliciting interest on the mailing list[1].

[1] http://lists.digium.com/mailman/listinfo/asterisk-dev