Keep in mind I am not trying to just arrogantly shoot down your idea, I enjoy the brainstorming.
Unfortunately it's still a problem because the core bridge/originate mechanism does not parse XML it's only parses the dial string markup. The XML dialplan is completely abstract from the originate mechanism because there can be many dialplans not just XML. In the end you must end up with one string of application and one string of data. I am very strict about maintaining scope boundaries between abstract concepts. I think it's the number 1 breakdown that led to asterisk getting so messed up over the years and I want to avoid that same plague. I hope you understand and if you want to continue to ponder some more functionality I welcome it. On Tue, Aug 25, 2009 at 9:50 PM, Carlos S. Antunes <[email protected]> wrote: > Anthony, > > Yes, you are right, I was thinking strictly in terms of SIP gateways. I > guess that instead on the tag "gateway", one could use "channel"? For > example: > > <action application="bridge"> > <!-- set some kind of *bridge-specific* variable --> > <channel order=1 data="sofia/gateway/gw-1/1$1"/> > <channel order=1 data="sofia/gateway/gw-2/1$1"/> > <channel order=2 data="sofia/gateway/gw-3/1$1"> > <!-- set some kind of *channel-specific* variable --> > </channel > > <channel order=3 data="sofia/gateway/gw-4/1$1"/> > </action> > > Would this be acceptable to you? > > Regarding the combinations of continue_on_fail and hangup_after bridge, > I'll give that a try although I suspect it will result in less structured > and harder to understand markup... > > Thanks! > > Carlos > > Anthony Minessale wrote: > > This suggestion violates the scope boundaries. > > gateways are specific concept to mod_sofia so a <gateway> tag in <action> > (part of agnostic xml dialplan) > does not flow properly. > > you can also use combinations of continue_on_fail and hangup_after bridge > so you can > just put each bridge statement in it's own action. > > > On Tue, Aug 25, 2009 at 9:06 AM, Carlos S. Antunes <[email protected]>wrote: > >> Max, >> >> I would like to see something similar too. For example, it would be >> wonderful if one could specify multiple gateways to try like this or >> something similar: >> >> <action application="bridge"> >> <!-- set some kind of *bridge-specific* parameter/variable --> >> <gateway order=1 data="sofia/gateway/gw-1/1$1"/> >> <gateway order=1 data="sofia/gateway/gw-2/1$1"/> >> <gateway order=2 data="sofia/gateway/gw-3/1$1"> >> <!-- set some kind of *gw-specific* parameter/variable --> >> </gateway> >> <gateway order=3 data="sofia/gateway/gw-4/1$1"/> >> </action> >> >> One would be able to avoid the "[]" and "{}" hacks and combine >> sequential and simultaneous trying of gateways. >> >> What do the developers think of this? >> >> Carlos >> >> Max Ivanov wrote: >> > Nowdays I 'm forced to put multiple "|" to find first free gateway, ie >> > >> sofia/gateway/panas111/1000|sofia/gateway/panas112/1000|sofia/gateway/panas113/1000 >> > , >> > the whole sting is tooo long, is there any shorter way to write same >> thing? Like >> > "sofia/gateway/panas*/1000" will try all gateways matching the pattern. >> > >> > _______________________________________________ >> > FreeSWITCH-users mailing list >> > [email protected] >> > 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 >> [email protected] >> 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/ > Twitter: http://twitter.com/FreeSWITCH_wire > > AIM: anthm > MSN:[email protected] <msn%[email protected]> > GTALK/JABBER/PAYPAL:[email protected]<paypal%[email protected]> > IRC: irc.freenode.net #freeswitch > > FreeSWITCH Developer Conference > sip:[email protected] <sip%[email protected]> > iax:[email protected]/888 > googletalk:[email protected]<googletalk%3aconf%[email protected]> > pstn:213-799-1400 > > ------------------------------ > > _______________________________________________ > FreeSWITCH-users mailing > [email protected]http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.freeswitch.org > > > _______________________________________________ > FreeSWITCH-users mailing list > [email protected] > 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/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:[email protected] <msn%[email protected]> GTALK/JABBER/PAYPAL:[email protected]<paypal%[email protected]> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:[email protected] <sip%[email protected]> iax:[email protected]/888 googletalk:[email protected]<googletalk%3aconf%[email protected]> pstn:213-799-1400
_______________________________________________ FreeSWITCH-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
