Re: [VoiceOps] LRN and valid values
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 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 > number, so we can rate it properly and implement our own LCR. Carrier B > says LRNs will always be valid NPANXX values, and 732040 and similar would > never be returned. > > I don't have access to the LERG, and frankly, even if I did, I'm not sure > where I'd look to see who wins the conflict. > > Any suggestions? > > Beckman > --- > Peter Beckman Internet Guy > beck...@angryox.com http://www.angryox.com/ > --- > ___ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] LRN and valid values
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 May 25, 2021, at 10:48 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 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 > number, so we can rate it properly and implement our own LCR. Carrier B > says LRNs will always be valid NPANXX values, and 732040 and similar would > never be returned. > > I don't have access to the LERG, and frankly, even if I did, I'm not sure > where I'd look to see who wins the conflict. > > Any suggestions? > > Beckman > --- > Peter Beckman Internet Guy > beck...@angryox.com http://www.angryox.com/ > --- > ___ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
[VoiceOps] LRN and valid values
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 number, so we can rate it properly and implement our own LCR. Carrier B says LRNs will always be valid NPANXX values, and 732040 and similar would never be returned. I don't have access to the LERG, and frankly, even if I did, I'm not sure where I'd look to see who wins the conflict. Any suggestions? Beckman --- Peter Beckman Internet Guy beck...@angryox.com http://www.angryox.com/ --- ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
