<HTML>
<HEAD>
<TITLE>Re: [Freeswitch-users] Best way to route Large block of DIDs</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Mod_easyroute might be used for this... it uses a DB backend via ODBC...<BR>
<BR>
This doesn’t really handle ranges as is, but you can do something to create ranges in there...<BR>
<BR>
<BR>
On 8/7/11 8:38 PM, "Luis F Urrea" <<a href="lfurrea@gmail.com">lfurrea@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi all,<BR>
<BR>
I have a relatively large block of DIDs coming from a T1 gateway to a FS box. These DIDs are mapped to user extensions in most cases and in others they go to an IVR.<BR>
<BR>
My question is what would be the best way to write an extension in public.xml dialplan if the block of DIDs that go directly to users is not exactly divided so that I can write a regexp to cover the block.<BR>
<BR>
Does writing a single rule for each user can bring performance implications?<BR>
<BR>
What if I cannot arrange the block of DIDs that belong to users in a consecutive group?<BR>
<BR>
What are the best practices for such case?<BR>
<BR>
TIA!!!<BR>
<BR>
Luis<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
Join us at ClueCon 2011, Aug 9-11, Chicago<BR>
<a href="http://www.cluecon.com">http://www.cluecon.com</a> 877-7-4ACLUE<BR>
<BR>
FreeSWITCH-users mailing list<BR>
<a href="FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><BR>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><BR>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><BR>
<a href="http://www.freeswitch.org">http://www.freeswitch.org</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>