I have personally deployed enum + acme in large capacity (300k+
individual numbers) for this explicit purpose.
It scales extraordinarily well and is very robust. Sip redirect is A way
to go but now involves building another application layer. Enum allows
for distributed caching, all while using mostly off-the-shelf software
stacks (i suppose theres an argument to be made that kamailio/opensips
are OTS software as well). FWIW my DNS stack of choice is usually
PowerDNS for this purpose.
FWIW ENUM:SAG routing is quite good and the ability to actually
reference internal session groups in the enum response, so you can push
business logic outside of the SD without giving up the SD's
intelligence. It can be very powerful.
On 11/12/2018 1:19 PM, Alex Balashov wrote:
I would really question the suggestion of ENUM. While it is supported,
it has fallen out of fashion, in favour of SIP redirects. I have heard
some anecdotes about Oracle's indifference to performance issues at high
volumes, and a general perception that ENUM is not held in high regard
as a priority.
On Mon, Nov 12, 2018 at 09:17:37PM +0000, 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
