> I don't know. I cannot seem to get my carrier to identify a situation where
> I would want to terminate a call and the LRN I would get back would be
> 732040 or similar.
It never will. The code is unrouteable. I'm sure it exists in the LERG
somewhere for some sort of pANI or billing
On Wed, 26 May 2021, Alex Balashov wrote:
Where does this conflict emerge in practice? Do customers call numbers in
this exchange? Do you get billed for calls (less any LRN dip fees) to this
exchange even though none of your wholesale termination vendors can route it?
I don't know. I cannot
)
5. Re: Robocall mitigation SCAM! (Mark Lindsey)
6. Re: Robocall mitigation SCAM! (Matthew Yaklin)
--
Message: 1
Date: Tue, 25 May 2021 22:47:24 -0400
From: Peter Beckman
To: VoiceOps
Subject: [VoiceOps] LRN and va
How are you even getting operator assisted calls onto your network to begin
with? Do you have an operator service you still pay for?
> On May 25, 2021, at 10:47 PM, Peter Beckman wrote:
>
> Carrier A provided us a US NPANXX Rate Deck that had some values in it that
> were not valid, such as
Where does this conflict emerge in practice? Do customers call numbers in this
exchange? Do you get billed for calls (less any LRN dip fees) to this exchange
even though none of your wholesale termination vendors can route it?
—
Sent from mobile, with due apologies for brevity and errors.
> On
Carrier A provided us a US NPANXX Rate Deck that had some values in it that
were not valid, such as 732040.
When asked about it, they claim that Access Tandem Codes are valid LRN
values for operator services calls.
Carrier B provides an API for us to query to get the LRN for a termination
