[Freeswitch-dev] hangup_after_bridge and intercept application

Francisco de Ezcurra francisco at deezcurra.com.ar
Fri Aug 15 11:28:35 EDT 2008


I was not answering the call originated via mod_event_socket so that was why 
it didn't work as I expected. My fault. :( 

I tried to use the -bleg with transfer but i could not figure out how to use 
it so used uuid_transfer like this and it is working as I need.

     <extension name="intercept">
        <condition field="destination_number" expression="2101">                    
          <action application="set" 
          <action application="answer" />
          <action application="export" data="hangup_after_bridge=false"/>          
          <action application="set" data="api_hangup_hook=uuid_transfer 
${bleg} 2102" />
          <action application="intercept" data="${bleg}"/>
          <action application="transfer" data="2103" />

Is there any way to use the transfer application with -bleg in the dialplan ? 
If yes, how is the syntax ? 

Thanks in advance

On Thursday 14 August 2008, Anthony Minessale wrote:
 The extension that executed the intercept app is the one that will be able
 to move on in the dialplan after the call because it's the effective A leg
 and that is the extension that had a dialplan instruction set.

 you can execute transfer with the -bleg option to perform the transfer on
 the opposite leg of the call.

 On Thu, Aug 14, 2008 at 3:07 PM, Francisco de Ezcurra <

 francisco at deezcurra.com.ar> wrote:
 > The fix works if i hangup the channel that makes the intercept. The other
 > leg
 > goes back to the fifo. But when i hangup the other leg the channel that
 > made
 > the intercept is hung up.
 > What I expect with this (ext. 2101)  dialplan is that the channel that
 > makes
 > the intercept executes the transfer to 2102 when the other leg hangs up.
 > Is this possible? I can not use the variable api_hangup_hook on the
 > channel created in the originate via MES because I don't know at that
 > moment the other leg.
 > Thanks
 > Panchi

More information about the Freeswitch-dev mailing list