<div dir="ltr">Both enum and redirections could be used, but I would personnally recommend enum as well if you want to achieve simple scenarii (though if you want some deeper routing logic, maybe a redirect server would better fit because you could programmatically apply that logic).<div><br><div>FYI we are also using enum with more than 20 millions records (powerdns with db backend) and our Oracle sbcs (3820/4600/6100) have no troubles handling this dns enum trafic at all, even with +++ call attempts per second. </div><div>Everything works perfectly and it doesn't appear to me that Oracle might not want to support it as any other routing fashion. </div><div><br></div><div>Florent<br><div><br><div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">Le mar. 13 nov. 2018 à 09:01, Ryan Delgrosso <<a href="mailto:ryandelgrosso@gmail.com">ryandelgrosso@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FWIW you should be able to manage the "Type" with Local Policy.<br>
<br>
Beware of LRT as LRT table uploads may not get replicated to your <br>
standby (depends on version of SD). This could lead you to complete <br>
breakage in the event of a berpd failover, and you will need to ensure <br>
the standby SD has identical LRT tables.<br>
<br>
Local Policy is part of config and will always be replicated and correct.<br>
<br>
<br>
<br>
On 11/12/2018 1:17 PM, Matthew Crocker wrote:<br>
><br>
> Alex,<br>
><br>
> Thanks, I actually have 2 projects, LRT will work for my 'call type' routing requirements (LD, EMER, TF, INT) should be easily handled with LRT. I'll also need ENUM to handle my inbound with 20k-ish numbers being routed to a couple different switches. I'm in the process of moving customers from one switch to another and updated DNS with the move makes sense. Now I just need to get all the pieces flying in formation to work<br>
><br>
><br>
> On 11/12/18, 4:07 PM, "VoiceOps on behalf of Alex Balashov" <<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a> on behalf of <a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>> wrote:<br>
><br>
> However, if you only have like < 10 rules, use something purely internal<br>
> as Ryan suggests.<br>
> <br>
> On Mon, Nov 12, 2018 at 08:22:28PM +0000, Matthew Crocker wrote:<br>
> ><br>
> > Thanks everyone, reading up on LRT now. Going to read up on ENUM as well, certainly sounds easier to manage large datasets with. Easier to upload a DNS server then gzip & upload a LRT XML file<br>
> ><br>
> > Thanks<br>
> ><br>
> > From: VoiceOps <<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a>> on behalf of Ryan Delgrosso <<a href="mailto:ryandelgrosso@gmail.com" target="_blank">ryandelgrosso@gmail.com</a>><br>
> > Date: Monday, November 12, 2018 at 3:07 PM<br>
> > To: "<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>" <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br>
> > Subject: Re: [VoiceOps] Oracle (Acme Packet) help<br>
> ><br>
> ><br>
> > You can do this with local policy pretty easily.<br>
> ><br>
> > LRT is an option but I detest LRT. I would deploy enum before using LRT.<br>
> ><br>
> ><br>
> ><br>
> > On 11/12/2018 11:25 AM, Matthew Crocker wrote:<br>
> ><br>
> > Hello,<br>
> ><br>
> ><br>
> > Does anyone know if I can do some basic call routing on an Acme Session Director? Basically I want to build a dialplan to route calls to various session-groups based on the SIP URI. Example: 911@* goes to SAG:EMERGENCY, 011*@* goes to SAG:INTERNATIONAL, +1*@* goes to SAG:LONGDISTANCE, etc.<br>
> ><br>
> > I’m trying to avoid bouncing the calls through something like a Kamailo or freeswitch to process and 302 Moved the call back to the Acme.<br>
> ><br>
> > Thanks<br>
> > -Matt<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> ><br>
> > VoiceOps mailing list<br>
> ><br>
> > <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><mailto:<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a>><br>
> ><br>
> > <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
> ><br>
> ><br>
> <br>
> > _______________________________________________<br>
> > VoiceOps mailing list<br>
> > <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
> > <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
> <br>
> <br>
> --<br>
> Alex Balashov | Principal | Evariste Systems LLC<br>
> <br>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)<br>
> Web: <a href="http://www.evaristesys.com/" rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" rel="noreferrer" target="_blank">http://www.csrpswitch.com/</a><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
> <br>
><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>