Re: [VoiceOps] Local calling tariff database

The calling party sets the initial calling area but the LRN has a lot to do with it if it's a ported TN at least in the LATA I'm in. Example below All numbers in the same LATA Caller : 808-369-8000 HNLL rate center via NANPA Called Party: 808-749-8000 outer island LRN for called: 808-439-1000

Re: [VoiceOps] Local calling tariff database

The NPANXX of the CallingParty sets the rate center. The rate center sets the list of all local NPANXX for the CalledParty. If the CalledParty NPANXX is in the list then it is a local call. LRN has nothing to do with it On Nov 14, 2017, at 6:54 PM, Alex Balashov

Re: [VoiceOps] Local calling tariff database

Local calling areas were determined by the ILECs/RBOCs. CLECs can offer their customers a different local calling area, but I believe the CABS billing is still determined by the ILECs/RBOCs local calling area, which is listed in their tariffs. Mary Lou Carey BackUP Telecom Consulting

Re: [VoiceOps] Local calling tariff database

Yes you are certainly correct they only pay a fraction of a fraction of a penny based on an old mileage calculation. You can easily avoid this charge with trunks to the tandem in the location in question. On Nov 14, 2017 2:01 PM, "Alex Balashov" wrote: > On Tue, Nov

Re: [VoiceOps] Local calling tariff database

Well, correction; you can port to a CLEC that can pick up the traffic at the tandem without DEOTs. That CLEC can have an entirely different local calling footprint and a different tariff. LCAs are basically an ILEC/RBOC concept, and that is the concept in which I am discussing them here. On Tue,

Re: [VoiceOps] Local calling tariff database

Um, how would it work if rate centers no longer matched, you know, the actual location and rate... On Tue, Nov 14, 2017 at 4:54 PM, Alex Balashov wrote: > On Tue, Nov 14, 2017 at 01:48:20PM -1000, Erik wrote: > > > You can port out of a rate center what u can't do is

Re: [VoiceOps] Local calling tariff database

On Tue, Nov 14, 2017 at 01:48:20PM -1000, Erik wrote: > You can port out of a rate center what u can't do is port out of a > LATA so if you're a clec the LRN does truly matter for cost depending > how you route your tandem traffic vs VoIP traffic. You can't port out of a rate centre. -- Alex

Re: [VoiceOps] Local calling tariff database

On Tue, Nov 14, 2017 at 03:39:22PM -0800, Jared Geiger wrote: > I have a related side question. Is a local calling area determined by > the LRN of the ANI or the DNIS? LRN shouldn't matter, because you can't port out of a rate centre. It is determined by ANI and DNIS. It's really determined by

Re: [VoiceOps] Local calling tariff database

I have a related side question. Is a local calling area determined by the LRN of the ANI or the DNIS? ~Jared On Tue, Nov 14, 2017 at 11:49 AM, Matthew Crocker wrote: > > > Telcordia LCA provides this data > >

Re: [VoiceOps] Local calling tariff database

Telcordia LCA provides this data http://www.trainfo.com/products_services/tra/downloads/lca.pdf Combined with the LERG you can get everything you need for NPANXX & LCA I have a script that eats it up and injects it into my Broadworks NS for local call routing. I use it for proper rating

Re: [VoiceOps] Local calling tariff database

Not for routing every single call out of a service provider it isn't. :-) On November 14, 2017 2:24:27 PM EST, BackUP Telecom Consulting wrote: >Localcallingguide.com and it's free! > >Mary Lou Carey > >BackUP Telecom Consulting > >615-791-9969 > >On 2017-11-14 02:44

Re: [VoiceOps] Local calling tariff database

Localcallingguide.com and it's free! Mary Lou Carey BackUP Telecom Consulting 615-791-9969 On 2017-11-14 02:44 AM, Alex Balashov wrote: Where can one get a digest of local access tariffs that is complementary to machine processing? Ten years ago, when I last cared about this, the canonical

[VoiceOps] Local calling tariff database

Where can one get a digest of local access tariffs that is complementary to machine processing? Ten years ago, when I last cared about this, the canonical answer was CCMI. Is that still the answer? Any idea on pricing? Does anyone offer "can-this-NPA-NXX-call-that-NPA-NXX-locally"-aaS, but