Re: [VoiceOps] Growing difficulties porting DIDs out of major VoIP carriers
Technically, it is possible to port without an LSR as long as winning carrier submits their port request in NPAC and the losing carrier concurs. The LSR is technically just a courtesy notice sent to the losing carrier so they know to look for the port request in NPAC, but a lot of games get played when it comes to LSRs on both sides of the fence. The losing carriers often play games by refusing to concur in NPAC until they receive a "valid" LSR (which can require an act of God to be considered valid). Winning carriers also play games sometimes by refusing to put any effort into making the port happen. Tracking an LSR through the entire process involves a lot of work that they would prefer not to do so they purposely weed out the customers that don't really care enough to make a big deal about keeping their old number. Some winning carriers have no clue what to do if they run into a problem with the port request and others just refuse to deal with a request if doesn't go through easily. Last year I was without my business number for about 11 months after I moved because Comcast disconnected my service before the port completed. I complained that I'd had my number for 10 years before porting it to them but that didn't seem to bother them. They had no intention of putting the effort into getting my number back! Initially they claimed they couldn't get it back after it had been disconnected. Then they told me it had already been released back to the previous carrier. When I told them I was a telecom consultant and knew their SPID was still associated with my TN, they finally admitted it was still available, but claimed they couldn't give it back to me unless I installed new service with them. I told them I had it call forwarded to another number for months after I disconnected the equipment but they claimed they couldn't turn it back on unless there was equipment at my previous location. After numerous calls and a threat to file an FCC complaint, I finally got them to turn it up for a month so I could port it away. I ended up having to pay them $110.00 so they could dispatch a tech to my previous location and activate my number. (The tech hooked up the equipment, activated the phone service and then removed the equipment and told me not to return it until after my number ported.) SO frustrating, especially since I could have walked them through the entire process! Unfortunately there's not a lot of oversight and it's very difficult for an end user to get help when it happens so until these offending carriers get their hand slapped enough, they have no incentive to clean up their act! Mary Lou Carey BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2019-03-05 10:41 AM, Oren Yehezkely wrote: Hello, I am hoping that someone may be able to shed some light as to the difficulties mobile carriers have to port DIDs away from major VoIP carriers such as Bandwidth and Onvoy. The problem does not seem to be on the VoIP providers. In most of the cases, they do not even receive an LSR. The mobile carriers seem to be asking for a CSR multiple times but never submit an LSR, then they tell the EU that the port request has failed. In another case, when the DID is with Bandwidth, the ATT system tells the customer that the number is with LOCKED with Google Voice and cannot be ported. I wonder who builds these faulty systems for these corporations? Any advice is appreciated. Oren ___ 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] LNP, tandems, etc.
Industry standard for tandem changes is 45 days so everyone can be notified and make the change in their own routing tables. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-10-04 11:21 AM, Mike Hammett wrote: I reached out to Comcast and pending an increase in installed trunk capacity, they should have the problem fixed by next month. I'd imagine if Frontier installed the new trunks faster than allowed by the tariff, Comcast would have it resolved more quickly. By fixed, I mean Comcast is moving their LRN back to the correct tandem. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Mike Hammett" TO: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 4:46:52 PM SUBJECT: [VoiceOps] LNP, tandems, etc. I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case. Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to that tandem. The operator of that tandem is telling us that the LRN is actually homed off of a different tandem in our LATA (operated by CenturyLink) in town C. Unfortunately, I can't corroborate this information with TelcoData the only rate center I see off of that tandem in TelcoData is an AT town next door. Where can I read up authoritatively on the porting requirements that would apply to this and related bits of info I should know? I'm checking on our LERG access as I know that has the authoritative information, but I don't have that access at the moment. Maybe we're not subscribed to it. Number NPA-NXX in town A: https://www.telcodata.us/search-area-code-exchange-detail?npa=815=991 LRN NPA-NXX in town B: https://www.telcodata.us/search-area-code-exchange-detail?npa=815=901 Tandem in town B: https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T Tandem in town C: https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T Thanks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.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 mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] Question about billing on SIP trunks
I would think it would only matter if the called party is served by the PSTN network because that's the only time that MOU billing should take place. However, it may be that your service provider doesn't differentiate and just bills you MOU charges based on what you send them so that they're covered just in case it hits the PSTN network. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-09-20 06:20 PM, Ryan Delgrosso wrote: So if it were me operating whoever your provider is, I would take the diversion as the originating number of the leg in question and bill appropriately, as the PAI/FROM in this case is display only. That being said, does the provider youre with make a distinction between local/LD? thats relatively archaic these days as the aggregate cost of national termination is so low most stopped caring, it might be worth considering moving to another provider. On 9/20/2018 1:34 PM, Peter Crawford wrote: Hello voice-ops: Enterprise admin here. We just converted from ISDN to SIP (and changed providers) and we're seeing some undesirable billing behavior. I'm hoping I can get some objective feedback from different providers. If a call comes into our system, and we forward it off-net using the SIP trunks (using either "standard" call forwarding or a call forking/paralleling feature like Avaya's EC500 or Cisco's Single Number Reach), we send the call with the SIP FROM header of the original caller (which is desirable to preserve callerID). We also include a Diversion Header with one of our phone numbers (the original destination of the call). We're being billed based on the *original* calling number, which sometimes results in long distance charges, even if this leg of the call is local to us. This is particularly onerous if the inbound call is international! So, the question is- what *should* we be billed on: FROM or DIVERSION. At one point, the provider indicated that P-Charge-Info was supported, but now backing away from that. Do we have any recourse (technical or otherwise)? Thanks. ___ 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 mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] LNP, tandems, etc.
Just because Comcast has the tandem switch association wrong in the LERG doesn't mean everyone else does. The 10K block establishes the routing for the LRN block only. 1K blocks are routed via the LRN of each carrier via NPAC, but the owner of the 1K block still has to publish their own routing record in the LERG. (To figure out how each carrier routes traffic from a particular rate center, you match up their NPA-NXX / rate center / Switch in LERG 6 with their switch homing arrangement record in LERG 7 SHA). Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-29 08:49 PM, Mike Hammett wrote: So then in my situation: https://www.telcodata.us/search-area-code-exchange-detail?npa=815=901 Comcast has 815-901 as well as 815-901-0. Verizon Wireless has 1k-8k. 9k I guess would be either not provisioned or default back to Comcast because they have the 10k block. Because they have the parent 10k block, are they then required to have a connection to the tandem I'm on anyway? The 1k block I now understand could be elsewhere, but the 10k? Interesting that AT U-Verse voice isn't on legacy AT infrastructure. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: p...@timmins.net TO: voice...@ics-il.net, voiceops@voiceops.org, mary...@backuptelecom.com CC: voiceops@voiceops.org, mary...@backuptelecom.com SENT: Wednesday, August 29, 2018 7:08:15 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. Thousands blocks are basically just a fancy LNP operation. Your tandem homing has to follow 10k blocks, and the 1k blocks are basically mass ported to your LRN. Even if the numbers are usually homed a certain way because they are in a ratecenter, they won't be in this case because they are ported numbers and supposed to be routed to your LRN. Example would be the Detroit LATA where there are about 6 or so AT and other tandems. I'm homed off WBFDMIMN20T. The local carrier has local/local toll trunks to me all over the place, but all intercarrier calls and out of area calls other than local traffic from AT LEC comes through my LRN 248-574-7678 off WBFDMIMN20T. This saves me from having to create FGD trunking ports to all the other tandems in the region, only the barely used local/intra trunking from AT ILEC, who has moved most customers to their uverse VoIP affiliate here, and those don't use the local/intra trunks either. It lowers my capex and opex having potentially over provisioned/underutilized trunking all over the place, saves numbers and decreases the need for splits and overlays, and even saves at money. Only people who lose out are ribbon and metaswitch (and whoever supports at 5ESS and EWSD deployments) on licensing and support costs for unneeded channels. On Aug 29, 2018 19:51, Mike Hammett wrote: "they give you market entry without the technical need to establish extra homing arrangements that aren't beneficial to you." Could you elaborate on that? - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: p...@timmins.net TO: mary...@backuptelecom.com, ptimm...@clearrate.com, voiceops@voiceops.org CC: voiceops@voiceops.org, ptimm...@clearrate.com SENT: Wednesday, August 29, 2018 6:05:39 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. I've had some interesting arguments with other carriers regarding their obligation to connect to us. Oh, you aren't connected where I'm homed? Go order connectivity then. They have a little more power to make demands when you have more than 24 standing calls to them, but by and large with these stubborn providers we never do, and when they have complained i've given them a location they can install 1 way trunks to me at (as I have no desire to terminate traffic to them directly), and they always balk and find some other way of dealing with it because it was all well and good until it was their money they were spending instead of mine. The trick ends up being to never do 10k blocks when you don't have to. Thousands blocks aren't just great for number consolidation, they give you market entry without the technical need to establish extra homing arrangements that aren't beneficial to you. Sure sometimes you're the guy who has to own the 10k block, bu That's true if the ILEC has an agreement with the tandem provider. There are some little ILECs that have their own tandem and refuse to use the big ILEC tandem provider! You have to look at the routing of the ILEC switch in the LERG to figure that out. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-29 11:38 AM, Paul Timmins wrote: > You don't actually have to establish connectivity to all ILECs in an > area, even if you are porting out numbers from their ratecenters. The > ILECs already have to
Re: [VoiceOps] LNP, tandems, etc.
Thanks for the vote of confidence Adam! LOL!
Mike..while I do have clients that I do everything for, I never
insist on operating that way because it makes both of us too dependent
on each other. I have a lot of clients that only seek my help from time
to time because they only need help from time to time, so I charge on a
per hour basis for service provided rather than a monthly basis. I've
found what works best for everyone involved is to train my clients on
the tasks that are simple or repetitive and advise / do the work for the
non-repetitive tasks that require more skill / experience. I've been
doing it this way for 18 years and I've never run out of work, so it
works well for everyone involved! If you''re interested feel free to
give me a call! If not, that's okay too.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-
On 2018-08-30 09:04 AM, Mike Hammett wrote:
I'm looking for one part (perhaps even two parts) educational and one
part get it fixed.
Fixing it could be as simple as not sending sending that traffic to
that tandem anymore. Easiest and cheapest (unless volume dictates
otherwise) way, though perhaps not the best. I've also made inquiries
to Frontier as to what services they have that could help solve this,
be it some value-add to take it to that tandem for me anyway, a DS1 to
that other tandem, etc. I've also reached out to others (including
Centurylink) for quoting out that transport. Probably need some other
paperwork as well (not sure if we have an ICA with them or not, I'm
guessing not), but I'm sure they'll tell me what I need to connect
when I ask to connect.
I'm one of those guys that likes to understand a situation vs.
outsourcing from the beginning. Sure, outsourcing may end up being the
best way of implementing it, but I can't just always take everyone at
their word and then not understand what's going on when things go
sideways.
The summary seems to be that Comcast did something wrong (or at least
unconventionally) and now I have to do extra work\expense to work
around it.
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
-
FROM: "Adam Vocks"
TO: "Mike Hammett" , p...@timmins.net
CC: voiceops@voiceops.org
SENT: Thursday, August 30, 2018 8:04:06 AM
SUBJECT: RE: [VoiceOps] LNP, tandems, etc.
Hi Mike, if you have money to throw at the problem, I think I'd just
hire Mary to track down and fix the problem for you. She's obviously
knowledgeable, probably has enough contacts and is now familiar with
your problem.
Adam
-Original Message-
From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of
Mike
Hammett
Sent: Thursday, August 30, 2018 7:17 AM
To: p...@timmins.net
Cc: voiceops@voiceops.org
Subject: Re: [VoiceOps] LNP, tandems, etc.
1) How do I find an appropriate contact to ask?
2) From what Mary has said, Comcast is doing it wrong in my area. I
suppose it's useful to know how something is SUPPOSED to be done and
acknowledge that it very well could be very different in production.
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
- Original Message -
From: p...@timmins.net
To: voice...@ics-il.net, voiceops@voiceops.org,
mary...@backuptelecom.com
Cc: voiceops@voiceops.org, mary...@backuptelecom.com
Sent: Wed, 29 Aug 2018 21:04:33 -0500 (CDT)
Subject: Re: [VoiceOps] LNP, tandems, etc.
The block owner often has a connection to the ILEC
tandem for their block in that range, but thats not always
necessary (I dont have any ilec FGD groups in the Chicago LATA,
so
its not universally necessary).The only way to know for certain is to check the LERG or
just
ask the carrier, which is what I usually do because I dont like
giving money to iconnectiv, since they tend to like to send me legally
cartoonish Cease and Descists every few years for the last
decade.On Aug 29, 2018 21:49, Mike Hammett
voice...@ics-il.net wrote:p
{
margin: 0; }So then
in
my situation:
https://www.telcodata.us/search-area-code-exchange-detail?npa=815;
amp;exchange=901Comcast has 815-901 as
well as
815-901-0. Verizon Wireless has 1k-8k. 9k I guess would be either
not
provisioned or default back to Comcast because they have the 10k
block.
Because they have the parent 10k block, are they then required to have
a
connection to the tandem Im on anyway? The 1k block I now
understand could be elsewhere, but the 10k?Interesting that
ATT U-Verse voice isnt on legacy ATT
infrastructure.-Mike
HammettIntelligent Computing
Solutionshttp://www.ics-il.comMidwest Internet
Exchangehttp://www.midwest-ix.com
From:
p...@timmins.netTo: voice...@ics-il.net,
voiceops@voiceops.org, mary...@backuptelecom.comCc:
voiceops@voiceops.org, mary...@backuptelecom.comSent:
Wednesday,
August
29, 2018 7:08:15 PMSubject: Re: [VoiceOps] LNP, tandems,
Re: [VoiceOps] LNP, tandems, etc.
I am an AOCN and have real time access to the LERG so just out of curiosity and because I like mysteries, I looked up your example to see what you were talking about. Comcast's records in LATA 364 are a mess! Most of Comcast's NXXs were assigned back in 11/07/13. When it was originally added, Comcast had it homed on the DKLBILXA50T tandem, which is correct. Then in February 2016 someone made a SHA change to their switch record and changed the tandem to DIXNILXA50T for the Local and IntraLATA tandems and CHCGILWU24T for the FGD Tandem. My guess is that Comcast initially set it up correctly, but when they added the CenturyLink territory of the LATA, they didn't add a second switch homing arrangement and LRN for the CenturyLink territory like they should have. I can't explain why it works unless there just haven't been any new companies since 2016. I would call Frontier back and tell them that they must have trunks established with Comcast because they have a bunch of NXXs in their territory that were set up in November 2013. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-28 06:00 PM, Mike Hammett wrote: Meaning if I thought were true? I had just assumed that Inteliquent did have the connections to every tandem in the LATAs they serve, given that (my thought) that you could only port numbers on the same tandem, so universal coverage would require connections to every tandem. We're actually looking at someone like Inteliquent to expand our footprint. So I'm supposed to be connected to every tandem in my LATA? In my LATA, there are only two (I believe), but some LATAs (like Chicago) have several. I'm supposed to drag a DS1 (or use Inteliquent, etc. if available) to connect to each one, even if I don't provide service in the rate centers traditionally served by that tandem? It seems like Comcast threw a dart at a dart board in choosing which tandem to connect to vs. going with the one that everyone else in that town uses. So then I could port a number from any rate center in my LATA (say Savanna) and point it to my LRN, living off of a tandem switch that the Savanna ILEC isn't connected to (from my outside world perspective)? Is there even the LATA constraint? Given the porting limitations I had experienced in the VoIP world, I assumed it was a tandem-by-tandem basis. So the LERG shows which tandem I need to send traffic to if I want to talk to them, but they could send their outbound calls to a different tandem? My current customer complaint is for calls that we're sending to Comcast, apparently homed off of the other tandem. If everyone is supposed to be on every tandem, then why can't the tandem I'm on just accept the calls I'm sending to Comcast, since Comcast should be there? Obviously me not being on the other tandem would affect inbound traffic to me. Is there another service I should be paying Frontier for to get me to the other tandem with some value-add service? I know CenturyLink hops through almost every town going that way (former LightCore and others before route). Frontier or CenturyLink may be able to get me a DS1 to the other tandem if I need that. I'm aware that I could still be completely missing the mark. BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't for many ages. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Paul Timmins" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 5:19:11 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. If that were true, you wouldn't be able to use inteliquent (et al) as your access tandem. Everyone is supposed to be directly or indirectly connected to every tandem in the LATA (which you can't independently verify, as telcodata and the LERG both show terminating tandem information to reach that end office, not what tandems the end office is hooked to to terminate calls. On Aug 28, 2018 17:47, Mike Hammett wrote: I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case. Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to that tandem. The operator of that tandem is telling us that the LRN is actually homed off of a different tandem in our LATA (operated by CenturyLink) in town C. Unfortunately, I can't corroborate this information with TelcoData the only rate center I see off of that tandem in TelcoData is an AT town next door. Where can I read up authoritatively on the porting requirements that would apply to this and related bits of info I should know? I'm checking on our LERG access as I know that has the authoritative information, but I don't have that
Re: [VoiceOps] LNP, tandems, etc.
If you have an LRN in the ILEC tandem provider's area, you can port to/from any rate center in that ILEC area. If there are small ILECs that use the big ILEC's tandem, you can also port to/from those rate centers. However, if you have more than 24 DS0s worth of traffic to that small ILEC area, the small ILEC can force you to install a direct connection to them. That doesn't happen very often but I've seen it happen a few times. If you're using a third party provider like Inteliquent, you need to have an LRN in every LATA that you want to port numbers in/out of. Your traffic can traverse their network between LATAs through your one connection with them, but in the background Inteliquent has to have connections with each tandem provider in both areas in order for it to work. That's why they give you a list of all the rate centers that they cover when you sign up with them! Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-28 06:00 PM, Mike Hammett wrote: Meaning if I thought were true? I had just assumed that Inteliquent did have the connections to every tandem in the LATAs they serve, given that (my thought) that you could only port numbers on the same tandem, so universal coverage would require connections to every tandem. We're actually looking at someone like Inteliquent to expand our footprint. So I'm supposed to be connected to every tandem in my LATA? In my LATA, there are only two (I believe), but some LATAs (like Chicago) have several. I'm supposed to drag a DS1 (or use Inteliquent, etc. if available) to connect to each one, even if I don't provide service in the rate centers traditionally served by that tandem? It seems like Comcast threw a dart at a dart board in choosing which tandem to connect to vs. going with the one that everyone else in that town uses. So then I could port a number from any rate center in my LATA (say Savanna) and point it to my LRN, living off of a tandem switch that the Savanna ILEC isn't connected to (from my outside world perspective)? Is there even the LATA constraint? Given the porting limitations I had experienced in the VoIP world, I assumed it was a tandem-by-tandem basis. So the LERG shows which tandem I need to send traffic to if I want to talk to them, but they could send their outbound calls to a different tandem? My current customer complaint is for calls that we're sending to Comcast, apparently homed off of the other tandem. If everyone is supposed to be on every tandem, then why can't the tandem I'm on just accept the calls I'm sending to Comcast, since Comcast should be there? Obviously me not being on the other tandem would affect inbound traffic to me. Is there another service I should be paying Frontier for to get me to the other tandem with some value-add service? I know CenturyLink hops through almost every town going that way (former LightCore and others before route). Frontier or CenturyLink may be able to get me a DS1 to the other tandem if I need that. I'm aware that I could still be completely missing the mark. BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't for many ages. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Paul Timmins" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 5:19:11 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. If that were true, you wouldn't be able to use inteliquent (et al) as your access tandem. Everyone is supposed to be directly or indirectly connected to every tandem in the LATA (which you can't independently verify, as telcodata and the LERG both show terminating tandem information to reach that end office, not what tandems the end office is hooked to to terminate calls. On Aug 28, 2018 17:47, Mike Hammett wrote: I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case. Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to that tandem. The operator of that tandem is telling us that the LRN is actually homed off of a different tandem in our LATA (operated by CenturyLink) in town C. Unfortunately, I can't corroborate this information with TelcoData the only rate center I see off of that tandem in TelcoData is an AT town next door. Where can I read up authoritatively on the porting requirements that would apply to this and related bits of info I should know? I'm checking on our LERG access as I know that has the authoritative information, but I don't have that access at the moment. Maybe we're not subscribed to it. Number NPA-NXX in town A: https://www.telcodata.us/search-area-code-exchange-detail?npa=815=991 L
Re: [VoiceOps] LNP, tandems, etc.
That's true if the ILEC has an agreement with the tandem provider. There are some little ILECs that have their own tandem and refuse to use the big ILEC tandem provider! You have to look at the routing of the ILEC switch in the LERG to figure that out. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-29 11:38 AM, Paul Timmins wrote: You don't actually have to establish connectivity to all ILECs in an area, even if you are porting out numbers from their ratecenters. The ILECs already have to have a way to reach any other tandem in the LATA so as long as you have an LRN homed on A tandem in the area, and port your numbers to that, you're good to go. The ILECs don't LIKE it, but if we cared what they truly liked we'd all just leave the market. On Aug 29, 2018 12:33, BackUP Telecom Consulting wrote: When there are multiple ILECs in a LATA like in LA - LATA 730, you would set up an interconnection point with each ILEC. So you'd have one for the AT areas and one for the old Verizon areas. When you have trunks to both carriers in the LATA, you can use your own network to switch traffic from the one LATA to the other LATA, but you can't deliver it to the ILEC and expect them to hand it off to the other ILEC. It would work the same with the third party providers...as long as they have a connection in both ILEC areas, then they can use their own network to deliver the traffic from the one ILEC area to the other ILEC area. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-28 08:18 PM, Mike Hammett wrote: I thought everyone connected to the ILEC-hosted tandem responsible for the rate centers where the number blocks were assigned, but that seems to not always be the case when there are multiple ILEC-hosted tandems in a LATA. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Erik" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 7:25:40 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. Most providers simply connect to the tandem at the ILEC. The end office transit termination and origination cost is SO LOW that it doesn't make since to have a switch or access point at the end office. Since most things are ILEC if not all are VOIP everything is coming from a centralize switch point. Hopefully all the 1970's billing methods will disappear. On Tue, Aug 28, 2018 at 1:00 PM, Mike Hammett wrote: Meaning if I thought were true? I had just assumed that Inteliquent did have the connections to every tandem in the LATAs they serve, given that (my thought) that you could only port numbers on the same tandem, so universal coverage would require connections to every tandem. We're actually looking at someone like Inteliquent to expand our footprint. So I'm supposed to be connected to every tandem in my LATA? In my LATA, there are only two (I believe), but some LATAs (like Chicago) have several. I'm supposed to drag a DS1 (or use Inteliquent, etc. if available) to connect to each one, even if I don't provide service in the rate centers traditionally served by that tandem? It seems like Comcast threw a dart at a dart board in choosing which tandem to connect to vs. going with the one that everyone else in that town uses. So then I could port a number from any rate center in my LATA (say Savanna) and point it to my LRN, living off of a tandem switch that the Savanna ILEC isn't connected to (from my outside world perspective)? Is there even the LATA constraint? Given the porting limitations I had experienced in the VoIP world, I assumed it was a tandem-by-tandem basis. So the LERG shows which tandem I need to send traffic to if I want to talk to them, but they could send their outbound calls to a different tandem? My current customer complaint is for calls that we're sending to Comcast, apparently homed off of the other tandem. If everyone is supposed to be on every tandem, then why can't the tandem I'm on just accept the calls I'm sending to Comcast, since Comcast should be there? Obviously me not being on the other tandem would affect inbound traffic to me. Is there another service I should be paying Frontier for to get me to the other tandem with some value-add service? I know CenturyLink hops through almost every town going that way (former LightCore and others before route). Frontier or CenturyLink may be able to get me a DS1 to the other tandem if I need that. I'm aware that I could still be completely missing the mark. BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't for many ages. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Paul Timmins" TO: "Mike Hammett"
Re: [VoiceOps] LNP, tandems, etc.
It's true that in the metropolitan areas the ILECs will allow you to trunk everything to the tandem, but the routing for rural areas is handled totally different in some ILEC areas. The old CenturyLink used to force carriers in some rural areas to deliver to the end office if the office associated with the rate center because it was so far out that the office had no local tandem. Others like the old Qwest territories let you route all traffic from the switches that had no local tandem over the Access Tandem if you had SPOP (Single Point of Presence) language in your agreement. The old BellSouth areas let you establish one Multi-tandem supergroup for the entire ILEC area and just charged you minutes of use anytime they had to inter-tandem a call. Every ILEC territory is just a little different, but they all share commonalities that they require you to route the LRN NXX to the tandem (or EO if there is no local tandem) that it is served by. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-28 07:25 PM, Erik wrote: Most providers simply connect to the tandem at the ILEC. The end office transit termination and origination cost is SO LOW that it doesn't make since to have a switch or access point at the end office. Since most things are ILEC if not all are VOIP everything is coming from a centralize switch point. Hopefully all the 1970's billing methods will disappear. On Tue, Aug 28, 2018 at 1:00 PM, Mike Hammett wrote: Meaning if I thought were true? I had just assumed that Inteliquent did have the connections to every tandem in the LATAs they serve, given that (my thought) that you could only port numbers on the same tandem, so universal coverage would require connections to every tandem. We're actually looking at someone like Inteliquent to expand our footprint. So I'm supposed to be connected to every tandem in my LATA? In my LATA, there are only two (I believe), but some LATAs (like Chicago) have several. I'm supposed to drag a DS1 (or use Inteliquent, etc. if available) to connect to each one, even if I don't provide service in the rate centers traditionally served by that tandem? It seems like Comcast threw a dart at a dart board in choosing which tandem to connect to vs. going with the one that everyone else in that town uses. So then I could port a number from any rate center in my LATA (say Savanna) and point it to my LRN, living off of a tandem switch that the Savanna ILEC isn't connected to (from my outside world perspective)? Is there even the LATA constraint? Given the porting limitations I had experienced in the VoIP world, I assumed it was a tandem-by-tandem basis. So the LERG shows which tandem I need to send traffic to if I want to talk to them, but they could send their outbound calls to a different tandem? My current customer complaint is for calls that we're sending to Comcast, apparently homed off of the other tandem. If everyone is supposed to be on every tandem, then why can't the tandem I'm on just accept the calls I'm sending to Comcast, since Comcast should be there? Obviously me not being on the other tandem would affect inbound traffic to me. Is there another service I should be paying Frontier for to get me to the other tandem with some value-add service? I know CenturyLink hops through almost every town going that way (former LightCore and others before route). Frontier or CenturyLink may be able to get me a DS1 to the other tandem if I need that. I'm aware that I could still be completely missing the mark. BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't for many ages. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Paul Timmins" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 5:19:11 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. If that were true, you wouldn't be able to use inteliquent (et al) as your access tandem. Everyone is supposed to be directly or indirectly connected to every tandem in the LATA (which you can't independently verify, as telcodata and the LERG both show terminating tandem information to reach that end office, not what tandems the end office is hooked to to terminate calls. On Aug 28, 2018 17:47, Mike Hammett wrote: I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case. Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to that tandem. The operator of that tandem is telling us that the LRN is actually homed off of a different tandem in our LATA (operated by CenturyLink) in town C. Unfortunately, I can't corroborate this information with TelcoData th
Re: [VoiceOps] LNP, tandems, etc.
When there are multiple ILECs in a LATA like in LA - LATA 730, you would set up an interconnection point with each ILEC. So you'd have one for the AT areas and one for the old Verizon areas. When you have trunks to both carriers in the LATA, you can use your own network to switch traffic from the one LATA to the other LATA, but you can't deliver it to the ILEC and expect them to hand it off to the other ILEC. It would work the same with the third party providers...as long as they have a connection in both ILEC areas, then they can use their own network to deliver the traffic from the one ILEC area to the other ILEC area. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-28 08:18 PM, Mike Hammett wrote: I thought everyone connected to the ILEC-hosted tandem responsible for the rate centers where the number blocks were assigned, but that seems to not always be the case when there are multiple ILEC-hosted tandems in a LATA. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Erik" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 7:25:40 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. Most providers simply connect to the tandem at the ILEC. The end office transit termination and origination cost is SO LOW that it doesn't make since to have a switch or access point at the end office. Since most things are ILEC if not all are VOIP everything is coming from a centralize switch point. Hopefully all the 1970's billing methods will disappear. On Tue, Aug 28, 2018 at 1:00 PM, Mike Hammett wrote: Meaning if I thought were true? I had just assumed that Inteliquent did have the connections to every tandem in the LATAs they serve, given that (my thought) that you could only port numbers on the same tandem, so universal coverage would require connections to every tandem. We're actually looking at someone like Inteliquent to expand our footprint. So I'm supposed to be connected to every tandem in my LATA? In my LATA, there are only two (I believe), but some LATAs (like Chicago) have several. I'm supposed to drag a DS1 (or use Inteliquent, etc. if available) to connect to each one, even if I don't provide service in the rate centers traditionally served by that tandem? It seems like Comcast threw a dart at a dart board in choosing which tandem to connect to vs. going with the one that everyone else in that town uses. So then I could port a number from any rate center in my LATA (say Savanna) and point it to my LRN, living off of a tandem switch that the Savanna ILEC isn't connected to (from my outside world perspective)? Is there even the LATA constraint? Given the porting limitations I had experienced in the VoIP world, I assumed it was a tandem-by-tandem basis. So the LERG shows which tandem I need to send traffic to if I want to talk to them, but they could send their outbound calls to a different tandem? My current customer complaint is for calls that we're sending to Comcast, apparently homed off of the other tandem. If everyone is supposed to be on every tandem, then why can't the tandem I'm on just accept the calls I'm sending to Comcast, since Comcast should be there? Obviously me not being on the other tandem would affect inbound traffic to me. Is there another service I should be paying Frontier for to get me to the other tandem with some value-add service? I know CenturyLink hops through almost every town going that way (former LightCore and others before route). Frontier or CenturyLink may be able to get me a DS1 to the other tandem if I need that. I'm aware that I could still be completely missing the mark. BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't for many ages. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Paul Timmins" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 5:19:11 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. If that were true, you wouldn't be able to use inteliquent (et al) as your access tandem. Everyone is supposed to be directly or indirectly connected to every tandem in the LATA (which you can't independently verify, as telcodata and the LERG both show terminating tandem information to reach that end office, not what tandems the end office is hooked to to terminate calls. On Aug 28, 2018 17:47, Mike Hammett wrote: I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case. Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to t
Re: [VoiceOps] LNP, tandems, etc.
You can pick which rate center your LRN will be assigned from, but you still have to follow the tandem homing established by the ILEC for that rate center. Not all ILECs require the same type of trunking to each of the tandems, but all require you to home your LRN on the tandem that your LRN-NXX would normally be served by in the PSTN network. Now you can appear to get around this by using the CLLI code of a third party providers, but the third party providers network is required to route traffic like the ILEC so really you're just using one pipe to send all your traffic to the ILEC and the third party provider breaks it out according to what tandem the ILEC requires trunking to. Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-08-28 09:56 PM, Mike Hammett wrote: Okay. I'll take that as my action item. On to the understanding... I don't understand how someone can aribrarily choose which tandem an LRN hangs off of. Why aren't they forced to keep an LRN attached to whatever tandem handles a given incumbent rate center? In my situation, 815-901 is in DeKalb. DeKalb's tandem is... DeKalb. How can Comcast decide to throw it onto Dixon's tandem? I wouldn't have this confusion if Comcast's LRN in Dixon was from an NPA-NXX assigned to Dixon. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Matthew Crocker" TO: "Mike Hammett" CC: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 8:53:27 PM SUBJECT: Re: [VoiceOps] LNP, tandems, etc. Mike You either need to connect to the other tandem or pay another carrier to get you there. It is the responsibility of the originating carrier to get the call to the terminating carriers switch. Depending on the call volume you should probably just route through your LD carrier On Aug 28, 2018, at 9:15 PM, Mike Hammett wrote: I drew a picture, hoping it would clear things up a bit. Through my switch, we're trying to call a number in a block assigned to Sycamore, with an LRN in a DeKalb number block, but the common tandem operator is telling me that the LRN actually lives on a different tandem. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Mike Hammett" TO: voiceops@voiceops.org SENT: Tuesday, August 28, 2018 4:46:52 PM SUBJECT: [VoiceOps] LNP, tandems, etc. I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case. Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to that tandem. The operator of that tandem is telling us that the LRN is actually homed off of a different tandem in our LATA (operated by CenturyLink) in town C. Unfortunately, I can't corroborate this information with TelcoData the only rate center I see off of that tandem in TelcoData is an AT town next door. Where can I read up authoritatively on the porting requirements that would apply to this and related bits of info I should know? I'm checking on our LERG access as I know that has the authoritative information, but I don't have that access at the moment. Maybe we're not subscribed to it. Number NPA-NXX in town A: https://www.telcodata.us/search-area-code-exchange-detail?npa=815=991 LRN NPA-NXX in town B: https://www.telcodata.us/search-area-code-exchange-detail?npa=815=901 Tandem in town B: https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T [1] Tandem in town C: https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T Thanks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.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 Links: -- [1] https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T ___ 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] CABS\Intercarrier Compensation Billing
Intercarrier CABS billing has to do with the charges that carriers bill each other for use of their network. It used to be that all facilities based carriers could charge for any PSTN traffic terminating on their switch or any toll free traffic originating from their switch. The rules were changed in 2017 so now facilities-based carriers cannot charge for end office switching - only tandem switching and dip charges. Whether to bill for it or not has always been based on the amount of traffic the facilities-based carrier has. Most carriers who have a significant amount of traffic to bill for use a CABS billing service and it doesn't really pay to do that unless you have 10,000 MOU (minutes of use) per month. There are also a few things to consider when determining whether you want to bill. Most wireless carriers try to establish bill and keep agreements so if a lot of your traffic is traversing their networks, you can bet they are going to want to negotiated that away. You also have to remember that if you're billing a company that isn't billing you, it gives them reason to start billing you so you have to evaluate all those components when deciding whether or not to go that route. The top 3 companies that do CABS billing are: Kadence http://www.gokadence.com/ MAC https://maccnet.com/services/billing-solutions/ UDP http://www.udp.com/ Mary Lou Carey BackUP Telecom Consulting Office: 615-771-7868 (temporary) Cell: 615-796- On 2018-07-05 02:19 PM, Mike Hammett wrote: My client is asking me to setup CABS billing for them. I only really see this being relevant to inter-carrier compensation. Where can I find more resources about how that works? Is inter-carrier compensation is something we'd be billing the tandem operator or each company sending us calls? Note: I'm primarily a data\SIP guy, but I've been thrown into telco hell. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.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] ATT Transport Group Contact Number
If you look on one of your ASR orders, there is a phone number listed on the FOC for the rep that issued the order. Usually that is an 8XX number for the provisioning and installation center. You can call them and ask them for the design contact for your order. Mary Lou Carey BackUP Telecom Consulting 615-791-9969 On 2018-04-10 11:58 AM, Andy Smith wrote: Hello, I need to speak with an ATT tech that has knowledge of their transport network(s) in LATA 368 (Peoria, IL). Does anyone have contact information? Thanks, Andy ___ 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] Troubles with Comcast
You may be able to get the correct contact from the person who is the admin for their CIC code. It is John Blimmel 303-658-7197. You'll want to put a trouble ticket in with their wholesale NOC. Mary Lou Carey BackUP Telecom Consulting 615-791-9969 On 2018-01-24 08:54 AM, Mike Hammett wrote: If anyone has contact information for who to open a ticket with at Frontier, I'd appreciate it. "Contacts and Escalation Lists" isn't helping me and nor is our account manager. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - FROM: "Matthew Yaklin" <myak...@firstlight.net> TO: "Matthew Crocker" <matt...@corp.crocker.com>, "Mike Hammett" <voice...@ics-il.net> CC: voiceops@voiceops.org SENT: Tuesday, January 23, 2018 4:58:18 PM SUBJECT: Re: [VoiceOps] Troubles with Comcast I agree. Open a ticket with the tandem provider and provide such info as calling party number, called number, day/time of calls, and what happened when failed (dead air, busy signal, etc...). It is up to them to get the call delivered to comcast. You do not have any visibility if the calls are even reaching a comcast switch. Matt - FROM: VoiceOps <voiceops-boun...@voiceops.org> on behalf of Matthew Crocker <matt...@corp.crocker.com> SENT: Tuesday, January 23, 2018 5:55:03 PM TO: Mike Hammett CC: voiceops@voiceops.org SUBJECT: Re: [VoiceOps] Troubles with Comcast You probably need to work with your tandem provider to find out they are presenting the all circuits busy error On Jan 23, 2018, at 5:37 PM, Mike Hammett <voice...@ics-il.net> wrote: I apologize in advance for I am new to this level of voice. I'm sending calls to the local tandem and I'm getting all circuits are busy when I call a Comcast number (or one ported to Comcast). Calls to those numbers work from other places (like my cell phone). Calls to other carriers on that tandem work. How can I reach someone at Comcast to troubleshoot this? We're using the Metaswitch platform. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.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 mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] Local calling tariff database
Correct.and the tariffs of the called party's carrier identify determine whether the calling party is making a local or toll call. Local calling areas are very weird with the ILECs because two rate centers can make a local call to the same rate center but if you make a call between those two rate centers it's considered toll. For example, in my area Franklin and Murfreesboro are considered local to Nashville, but a call between Franklin and Murfreesboro is toll. Mary Lou Carey BackUP Telecom Consulting 615-791-9969 On 2017-11-14 06:40 PM, Matthew Crocker wrote: 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 <abalas...@evaristesys.com> 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 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 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/ ___ 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 mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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 615-791-9969 On 2017-11-14 05:39 PM, Jared Geiger wrote: 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 <matt...@corp.crocker.com> wrote: Telcordia LCA provides this data http://www.trainfo.com/products_services/tra/downloads/lca.pdf [1] 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 (billing trusts the Broadworks rating) and 7 digit dials when available. -Matt -- Matthew Crocker Crocker Communications, Inc. President On 11/14/17, 2:45 PM, "VoiceOps on behalf of Alex Balashov" <voiceops-boun...@voiceops.org on behalf of abalas...@evaristesys.com> wrote: 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 <mary...@backuptelecom.com> wrote: Localcallingguide.com and it's free! Mary Lou Carey BackUP Telecom Consulting 615-791-9969 [2] 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 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 reliably? -- Alex -- Sent via mobile, please forgive typos and brevity. ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops [3] ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops [3] Links: -- [1] http://www.trainfo.com/products_services/tra/downloads/lca.pdf [2] tel:615-791-9969 [3] https://puck.nether.net/mailman/listinfo/voiceops ___ 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] 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 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 reliably? ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] SS7 Feeds?
Have you tried Syniverse for NEUSTAR (formerly TNSI)? Mary Lou Carey BackUP Telecom Consulting 615-791-9969 On 2017-08-03 09:35 AM, Shawn L via VoiceOps wrote: Looking for an additional (backup) SS7 connection. Wondering if anyone can suggest a good provider that we can work with / order through. We've been trying to order another one through AT for about a year now, and are still no closer to actually getting it. Thanks ___ 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
