How about parking the call with an announcement such as "locating subscriber, please wait a monent" and using app_swift, calling with then CID info read and then using a menu options in your dialplan on how to handle the call? Press 1 call app_bridge to connect the legs.
Intricate, yes. but more functional than the "c" flag as you can add more options than simply pressing 1 or # such as forwarding the call, sending them to telemarketing hell, playing a message that you are not available and to try back later, or simply hanging up. Just a thought. Thanks, Steve Totaro On Sun, May 11, 2008 at 2:38 PM, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote: > For zap channels, you do have the "c" option on the dialgroup which > requires that you press # before the call is connected. > > Works great for my mobile ;) > > Julian > > Atis Lezdins wrote: >> On Sun, May 11, 2008 at 8:49 PM, Matt Watson <[EMAIL PROTECTED]> wrote: >>> I just took a quick look at the dialplan that freepbx uses for doing call >>> confirmation... the dialplan part of it is actually quite simple... its >>> just a matter of setting the USE_CONFIRMATION varialbe =TRUE. >>> >>> However, the actual magic looks like it happenes through its >>> dialparties.agi... which is a little more complicated than i'd like to try >>> and dissect on a sunday afternoon! >>> >>> but that might be a good place to look at how its done to learn by example. >> >> It should be like >> >> Dial(SIP/123&SIP/456,30,M(confirm)); >> >> and macro named "confirm" that playback the prompt, reads DTMF, and >> sets value of MACRO_RESULT >> >>> I know in the freepbx implementation what it does is whenever a handset >>> thats part of the ringgroup answers, they get a recorded message "You have >>> an incoming call, press 1 to accept" maybe it says something else too... >>> can;t recall at the moment. The first member of the Ring group to hit 1 >>> gets the call... if more than 1 person picks up the handset right away, the >>> first to hit 1 gets it, and the rest hear a "sorry, too late, somebody else >>> got it"-type message (no idea what it actually says). >> >> I suppose just a disconnect, because call was already bridged. >> >> Regards, >> Atis >> >> > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
