Woops, my double identity of my marketing alias isn't subscribed correctly...-------------
Ooooo, then this is an error because bridge_pre_execute_aleg is not firing on fifo bridge. I'm using FreeSWITCH Version 1.0.trunk (12701M) and setting <action application="set" data="bridge_pre_execute_aleg_app=lua"/> <action application="set" data="bridge_pre_execute_aleg_app=aleg.lua"/> <action application="set" data="bridge_pre_execute_bleg_app=lua"/> <action application="set" data="bridge_pre_execute_bleg_app=bleg.lua"/> on both the fifo in and fifo out channels, but aleg.lua/bleg.lua never get executed on fifo bridge. Do you need a trace or anything? --matt On Thu, Mar 26, 2009 at 10:52 PM, Matt Hunter <m...@hellohunter.com> wrote: > > > 2009/3/26 Anthony Minessale <anthony.miness...@gmail.com> > >> this feature is already implemented system-wide not just in fifo >> >> bridge_pre_execute_aleg_app >> bridge_pre_execute_aleg_data >> >> bridge_pre_execute_bleg_app >> bridge_pre_execute_bleg_data >> >> Set either pair of these vars (aleg is the consumer) >> >> and the application of choice would be executed right when the bridge >> starts. >> >> >> >> 2009/3/26 Matthew Fong <mattdf...@gmail.com> >> >>> Oh, so the reason why the bridge_api_app execution is more useful, is >>> with the custom fifo:info event, for my event_socket to read it, it has to >>> subscribe to ALL fifo:info events, meaning I have to process fifo:info >>> events even if they are not useful to me. With an app in lua, I can fire a >>> custom event based on say my fifo name, this way my event_socket only has to >>> read events for a specific fifo, rather than all fifos. >>> it's not to make more work for u :)...although it's sort of amazing >>> how efficient of a coder you are. >>> >>> --matt >>> >>> >>> On Thu, Mar 26, 2009 at 10:20 PM, Matthew Fong <mattdf...@gmail.com>wrote: >>> >>>> Thanks of course! >>>> But, is there any chance of firing an app? Firing an app on bridge gives >>>> the programmer more control, rather than just listening for fifo::info >>>> custom events. I find that lua running as a FS app can update my database >>>> like 10x faster than reading event_socket thru Rails/Telegraph...plus, I >>>> trust your coding much more than that of your Rail's development >>>> counterparts. :) >>>> >>>> with the custom event you are firing, you should be sure to import the >>>> variables first, then fire the event :) >>>> >>>> You rock Mr. Minessale >>>> >>>> --matt >>>> >>>> 2009/3/26 Anthony Minessale <anthony.miness...@gmail.com> >>>> >>>> I'll fire 2 custom events when the call is bridged one for the consumer >>>>> and one for the caller >>>>> >>>>> events plain custom fifo::info >>>>> >>>>> pull out FIFO-Name header and find the desired fifo >>>>> pull out FIFO-Action header and look for bridge-consumer or >>>>> bridge-caller depending on what you want to see data from. >>>>> >>>>> in latest trunk >>>>> >>>>> 2009/3/26 Matthew Fong <mattdf...@gmail.com> >>>>> >>>>> Hi Anthony, >>>>>> So it's been 2 days since my last request, so I'm due for another one >>>>>> ;) >>>>>> >>>>>> It would be nice if there was a way to execute a script (lua) on fifo >>>>>> bridge. I currently rely on the channel_bridge event, but I'm worried >>>>>> that >>>>>> as my system scales, it would be better to fire a custom event. In >>>>>> non-fifo >>>>>> mode, I can do this with bridge_pre_execute_bleg_app/data, but this >>>>>> doesn't work with a fifo bridge. It doesn't really matter which channel >>>>>> it >>>>>> fires on fifo out or fifo in channel, anything is better than having to >>>>>> listen for a specific channel_bridge on a high-use FS installation. >>>>>> >>>>>> Is there anyway to get an api/script to fire on fifo bridge currently >>>>>> that I'm missing? Thanks! >>>>>> >>>>>> --matt >>>>>> >>>>>> 2009/3/23 Anthony Minessale <anthony.miness...@gmail.com> >>>>>> >>>>>> ok, >>>>>>> maybe after this i can have a day off ;) >>>>>>> >>>>>>> 2 variables added to latest trunk: >>>>>>> >>>>>>> "fifo_caller_consumer_import" >>>>>>> "fifo_consumer_caller_import" >>>>>>> >>>>>>> both work like the regular import but one is a list of vars to copy >>>>>>> from caller to consumer and one is a list to copy from consumer to >>>>>>> caller. >>>>>>> >>>>>>> >>>>>>> 2009/3/23 Matthew Fong <re...@matthewfong.com> >>>>>>> >>>>>>>> Thanks Anthony, for creating the transfer_after_bridge feature for >>>>>>>> me. Your rapid actions, are the reason I'm positive I made the right >>>>>>>> decision switch to to FS. >>>>>>>> I got another challenge to throw your way. In the current fifo >>>>>>>> implementation, there's no way to identify which fifo consumer, >>>>>>>> consumes a >>>>>>>> caller--besides using other_leg_unique_id on bridge (ie, there's no >>>>>>>> way to >>>>>>>> pass data between channels when a fifo bridge is created). I want to >>>>>>>> be able >>>>>>>> to transfer some caller information to the consumer channel on bridge, >>>>>>>> to >>>>>>>> populate an agent's screen. >>>>>>>> >>>>>>>> Under normal (non-fifo) circumstances, when a call is bridged, I've >>>>>>>> used the 'import' channel variable, so that onBridge, the aleg >>>>>>>> automatically >>>>>>>> gets populated with the bleg's 'import' field. However when fifo >>>>>>>> bridges, it >>>>>>>> does not recognize import. In other applications, I've gotten around >>>>>>>> this by >>>>>>>> using bridge_pre_execute_bleg_app/data to throw a custom event but with >>>>>>>> fifo, bridge_pre_execute also does not work. I've been looking at the >>>>>>>> fifo::info event, but again, there's no fifo_action that directly links >>>>>>>> caller variables and consumer variables together. >>>>>>>> >>>>>>>> For now at least, I can get around this by storing uuid information >>>>>>>> in my separate database, and looking up the other channel's information >>>>>>>> based on other_leg_unique_id, but it would be nice if I could directly >>>>>>>> see >>>>>>>> it when the channel is bridged. Anyway, great program, and I hope you >>>>>>>> consider implementing these features to make FS even better. Thanks. >>>>>>>> >>>>>>>> --matt >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Freeswitch-users mailing list >>>>>>>> Freeswitch-users@lists.freeswitch.org >>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >>>>>>>> UNSUBSCRIBE: >>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users >>>>>>>> http://www.freeswitch.org >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Anthony Minessale II >>>>>>> >>>>>>> FreeSWITCH http://www.freeswitch.org/ >>>>>>> ClueCon http://www.cluecon.com/ >>>>>>> >>>>>>> AIM: anthm >>>>>>> MSN:anthony_miness...@hotmail.com<msn%3aanthony_miness...@hotmail.com> >>>>>>> GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com<paypal%3aanthony.miness...@gmail.com> >>>>>>> IRC: irc.freenode.net #freeswitch >>>>>>> >>>>>>> FreeSWITCH Developer Conference >>>>>>> sip:8...@conference.freeswitch.org<sip%3a...@conference.freeswitch.org> >>>>>>> iax:gu...@conference.freeswitch.org/888 >>>>>>> googletalk:conf+...@conference.freeswitch.org<googletalk%3aconf%2b...@conference.freeswitch.org> >>>>>>> pstn:213-799-1400 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Freeswitch-users mailing list >>>>>>> Freeswitch-users@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@lists.freeswitch.org >>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >>>>>> UNSUBSCRIBE: >>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users >>>>>> http://www.freeswitch.org >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Anthony Minessale II >>>>> >>>>> FreeSWITCH http://www.freeswitch.org/ >>>>> ClueCon http://www.cluecon.com/ >>>>> >>>>> AIM: anthm >>>>> MSN:anthony_miness...@hotmail.com<msn%3aanthony_miness...@hotmail.com> >>>>> GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com<paypal%3aanthony.miness...@gmail.com> >>>>> IRC: irc.freenode.net #freeswitch >>>>> >>>>> FreeSWITCH Developer Conference >>>>> sip:8...@conference.freeswitch.org<sip%3a...@conference.freeswitch.org> >>>>> iax:gu...@conference.freeswitch.org/888 >>>>> googletalk:conf+...@conference.freeswitch.org<googletalk%3aconf%2b...@conference.freeswitch.org> >>>>> pstn:213-799-1400 >>>>> >>>>> _______________________________________________ >>>>> Freeswitch-users mailing list >>>>> Freeswitch-users@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@lists.freeswitch.org >>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >>> http://www.freeswitch.org >>> >>> >> >> >> -- >> Anthony Minessale II >> >> FreeSWITCH http://www.freeswitch.org/ >> ClueCon http://www.cluecon.com/ >> >> AIM: anthm >> MSN:anthony_miness...@hotmail.com <msn%3aanthony_miness...@hotmail.com> >> GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com<paypal%3aanthony.miness...@gmail.com> >> IRC: irc.freenode.net #freeswitch >> >> FreeSWITCH Developer Conference >> sip:8...@conference.freeswitch.org <sip%3a...@conference.freeswitch.org> >> iax:gu...@conference.freeswitch.org/888 >> googletalk:conf+...@conference.freeswitch.org<googletalk%3aconf%2b...@conference.freeswitch.org> >> pstn:213-799-1400 >> >> _______________________________________________ >> Freeswitch-users mailing list >> Freeswitch-users@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org