Or, of course, there is always mod_xml_curl. Basically, XML dialplan on the fly. Call comes in, FreeSWITCH sends XML request via HTTP to a web application server, web application server responds with XML routing response, FreeSWITCH routes the call. On Thu, Nov 12, 2009 at 5:53 PM, Rupa Schomaker <rupa@rupa.com> wrote:
On Thu, Nov 12, 2009 at 4:32 PM, Robin Vleij <viper@fx-services.com> wrote:
On 11/12/09 9:59 PM, Rupa Schomaker wrote: If I read it right, this is suited for "complete" nrs. So would I have a system connected with lots of DIDs, I would put them in easyroute. Then for systems with lots of number ranges, I would use mod_lcr.
lcr is based on prefix, so the boundaries for which the range is assigned may not match a prefix. You may be better off either:
1) denormalize your ranges and just insert all distinct #s
2) Modify mod_easyroute to support ranges
3) talk to SWK (he is on irc here and there) about his (non free) fancier routing options
-- -Rupa
_______________________________________________ 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
-- Eliot Gable "We do not inherit the Earth from our ancestors: we borrow it from our children." ~David Brower "I decided the words were too conservative for me. We're not borrowing from our children, we're stealing from them--and it's not even considered to be a crime." ~David Brower "Esse oportet ut vivas, non vivere ut edas." (Thou shouldst eat to live; not live to eat.) ~Marcus Tullius Cicero