[Freeswitch-users] exec_after*

Sergey Okhapkin sos at sokhapkin.dyndns.org
Mon Oct 18 12:40:30 PDT 2010


The "h" extension in asterisk is a feature I used extensively. Lack of a 
hangup dialplan handler makes DP programming in FS harder and less clear. 
Fortunately, CDR handlers allow to do some post call cleanup work, but in-
dialplan implementation would be much better and clearer.

On Monday 18 October 2010, Jeroen C. van Gelderen wrote:
> Bingo.
> 
> The exec_after_bridge_app call is guarded by:
> 
>   if (!inner_bridge && switch_channel_up(chan_a)) {
>   }
> 
> whereas the exec_after_bridge_api is guarded by:
> 
>   if (!inner_bridge) {
>   }
> 
> Anyone know the reason for this difference? It would seem common for the
> channel to be hung up by the time one wants to execute the registered
> application.
> 
> Cheers,
> -Slim
> --
> Jeroen C. "Slim" van Gelderen
> 
> -----Original Message-----
> From: freeswitch-users-bounces at lists.freeswitch.org
> [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Sergey
> Okhapkin
> Sent: Monday, October 18, 2010 12:11
> To: FreeSWITCH Users Help
> Subject: Re: [Freeswitch-users] exec_after*
> 
> Will the DP application specified with exec_after_bridge executed if the
> channel was hung up?
> 
> On Monday 18 October 2010, Michael Collins wrote:
> > Well, the only difference is that one is executing an API and the other
> > executes a dialplan application. AFAIK they should operate in a similar
> > fashion. The only difference I see is that you have supplied an argument
> 
> in
> 
> > your API call ("${recfile}") but not in your exec_after_bridge call.
> >
> > -MC
> >
> > On Sun, Oct 17, 2010 at 3:33 PM, Jeroen C. van Gelderen
> >
> > <slim at thegreek.com>wrote:
> > > Hi,
> > >
> > > My helpdesk extensions are recorded. When the recording is complete
> > > (after bridge) I want to run a script to create a ticket and attach
> > > said recording to it.
> > >
> > > Initially I tried to use
> > >
> > > [...]
> > > Dialplan: FreeTDM/3:1/ Action set(exec_after_bridge_app=system)
> > > Dialplan: FreeTDM/3:1/ Action
> > > set(exec_after_bridge_arg=/root/wav2ticket.php)
> >
> > [...]
> >
> > > but this doesn't result in an invocation of my script and seemingly no
> > > helpful diagnostic messages.
> > >
> > > I changed to using
> > >
> > > <action application="set"
> > >  data="api_after_bridge=system /root/wav2ticket.php ${recfile}"/>
> > >
> > > which DOES work.
> > >
> > > Can anyone clarify the difference between the two approaches?
> > >
> > > Cheers,
> > > -Slim
> > > --
> > > Jeroen C. "Slim" van Gelderen
> > > Olympic Sports Data Services
> > > Email: slim at thegreek.com
> > > Phone: +1 876 953 6182 x128
> > >
> > >
> > >
> > > _______________________________________________
> > > FreeSWITCH-users mailing list
> > > FreeSWITCH-users at lists.freeswitch.org
> > > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> > > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-user
> > >s http://www.freeswitch.org
> 
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
> 
> 
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
> 




More information about the FreeSWITCH-users mailing list