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).
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. Everything works perfectly and it doesn't appear to me that Oracle might not want to support it as any other routing fashion. Florent Le mar. 13 nov. 2018 à 09:01, Ryan Delgrosso <[email protected]> a écrit : > FWIW you should be able to manage the "Type" with Local Policy. > > Beware of LRT as LRT table uploads may not get replicated to your > standby (depends on version of SD). This could lead you to complete > breakage in the event of a berpd failover, and you will need to ensure > the standby SD has identical LRT tables. > > Local Policy is part of config and will always be replicated and correct. > > > > On 11/12/2018 1:17 PM, Matthew Crocker wrote: > > > > Alex, > > > > 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 > > > > > > On 11/12/18, 4:07 PM, "VoiceOps on behalf of Alex Balashov" < > [email protected] on behalf of [email protected]> > wrote: > > > > However, if you only have like < 10 rules, use something purely > internal > > as Ryan suggests. > > > > On Mon, Nov 12, 2018 at 08:22:28PM +0000, Matthew Crocker wrote: > > > > > > 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 > > > > > > Thanks > > > > > > From: VoiceOps <[email protected]> on behalf of Ryan > Delgrosso <[email protected]> > > > Date: Monday, November 12, 2018 at 3:07 PM > > > To: "[email protected]" <[email protected]> > > > Subject: Re: [VoiceOps] Oracle (Acme Packet) help > > > > > > > > > You can do this with local policy pretty easily. > > > > > > LRT is an option but I detest LRT. I would deploy enum before > using LRT. > > > > > > > > > > > > On 11/12/2018 11:25 AM, Matthew Crocker wrote: > > > > > > Hello, > > > > > > > > > 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. > > > > > > 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. > > > > > > Thanks > > > -Matt > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > VoiceOps mailing list > > > > > > [email protected]<mailto:[email protected]> > > > > > > https://puck.nether.net/mailman/listinfo/voiceops > > > > > > > > > > > _______________________________________________ > > > VoiceOps mailing list > > > [email protected] > > > https://puck.nether.net/mailman/listinfo/voiceops > > > > > > -- > > Alex Balashov | Principal | Evariste Systems LLC > > > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > _______________________________________________ > > VoiceOps mailing list > > [email protected] > > https://puck.nether.net/mailman/listinfo/voiceops > > > > > > _______________________________________________ > > VoiceOps mailing list > > [email protected] > > https://puck.nether.net/mailman/listinfo/voiceops > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
