[VoiceOps] Establishing a new LRN
Paul Timmins
paul at timmins.net
Fri Jun 3 14:14:38 EDT 2022
All I've ever had to do was put it in on LTI and that's it. As long as
you're the NXX holder with the NANPA (not a thousands block).
I'm sure there's somewhere to put it in the LERG if you enjoy dealing
with that. I sure don't and never have.
On 6/3/22 14:02, Matthew Crocker wrote:
>
> Hello all,
>
> What is the process for establishing a new LRN in a LATA? We have 3
> codes assigned to us for LATA 126 (413-200, 413-654, 413-370). I
> currently have an LRN 413-654-1234 assign to a switch. I need a new
> LRN (413-200-1234 ???) assigned to a new switch. All of my
> interconnect stuff is handled via Inteliquent, they can route the
> calls to my codes to the appropriate switch. I have all of the SIP
> trunks built for Inteliquent.
>
> I need to migrate customers from one switch to another. My plan is to
> establish a new LRN on an existing code (413-200-1234 for example).
> Have Inteliquent route the code to my new switch. Then I can update
> the porting database for customers to the new LRN as they are migrated.
>
> I believe I need to update the LERG but I don’t know how to do that
>
> Thanks
>
> -Matt
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20220603/ebaf2ea8/attachment-0001.htm>
More information about the VoiceOps
mailing list