On Tuesday, May 22, 2018, 3:07:59 PM EDT, Alex Balashov <abalashov@evaristesys.com> wrote:

Again: DNS-based resolution mechanisms make use of a global DNS
hierarchy, so you need to figure out how to expose your LRN provider's
e164.arpa. zone into your local DNS resolver.

Shouldn't be too hard. You can configure most DNS caches like PowerDNS
to source a particular zone from a static upstream.

On Tue, May 22, 2018 at 07:00:47PM +0000, KamDev Essa wrote:

>  In the LRN request via ENUM using dig I provide an IP of my LRN dip provide and a E.164 formatted TN of the requested user. I get a text dump from which I extract the rn value if present. I dont not know how to automate those steps or other steps to get the same solution.
> KD   
>    On Tuesday, May 22, 2018, 2:53:53 PM EDT, Alex Balashov <abalashov@evaristesys.com> wrote: 
> 
>  On Tue, May 22, 2018 at 06:47:33PM +0000, KamDev Essa wrote:
>
> > I cannot handle the ENUM in kamailio or mysql.
>
> How did you draw that conclusion?
>
> --
> 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/
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 

> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users