atcomsystems.ca/forum Forums Wiring - Telecom Carriers - Trunks & Services Telecom Service & Providers Level 3

I have a customer who uses this company as their local/LD service provider. We have discoverd that cell phone calls to their main number usually ring no answer. I have verified this at the NIU. When I call the number from my cell ( Sprint ) I get no ringing current at all. When I answer the call, I seem to get a connection, however, there is no voice path.

Level 3 is telling me they cannot open a "ticket" with these celluar providers & instructed me to call Sprint... :confused:

Anyone else have this issue with Level 3?

I guess not... :sleep:

Did the customer port the telephone numbers to Level 3 from another provider?

I have ran into this before. You have to complain loud enough so that level3 will re-broadcast the port. I have ran into different exchanges that either missed it or weren't broadcast to.

Kumba's got the hot setup. And it's NOT just level 3. What happens is a lec will either miss 1 line or miss the whole change. Calls from users of that lec don't go thru. Sometimes RNA, sometimes OOS, depends on the lec. It helps if the customer can find out what lec the callers that can't get thru are using. Kinda hard when they cannot call you to tell you about the problem, because they don't know who can't call them. It's gotten so bad around here, we had the techs do test calls from wherever they were to help check a new port! John C. (Not Garand)

I have noticed that it's most prevalent on cell phone carriers (missing porting changes). I have had to have the porting broadcast done up to 3 times before all the different carriers and exchanges got it.

As far as the number's themselves I notice that toll-free #'s seem to suffer from it more then local #'s but that could just be my luck. Your mileage may vary.

Thanx, everyone! :thumb:

Yes.

I was thinking along the lines of an incomplete port.

More info...I was just informed that not only are some inbound cell calls RNA, but inbound local & LD as well. Also, I was told that the customer had Level 3 for some time & tried to port to a.t.&t. back in febuary & Level 3 couldn't or wouldn't release the numbers so the cut was canceled.

I agree with dexman, I think the numbers are hosed up the national number database ( what's the proper term? ).

LIDBI (I think that is the correct spelling)

LIDB is for things like accepting collect calls. The porting happens with NPAC in the SMS. That's a hell of a racket, they charge a fortune for any kind of fast access.

Thanx, dexman & djweiss.

Here it is! Thanx, once more!

https://www.npac.com/

Sorry for chiming in so late, but I've been seeing this quite a lot lately with multiple service providers. It seems to be more prevalent with toll-free numbers though. I am starting to think that the number portability database is almost like credit reporting agencies. Some get the information and some don't.

Try this on for size. Customer wants to change LECs AGAIN. He gives numbers to new LEC and old LEC says there are more, and won't process the paperwork, let alone do the cut. AND won't give new LEC the numbers. Customer says for new LEC to handle it, but new LEC doesn't know what a LOA is. Is it any wonder the lines/trunks/whatever are getting SSSOOO screwed up nationally? John C. (Not Garand)

"but new LEC doesn't know what a LOA is"


Run very far away. If they don't know what am LOA is you need to turn around and put the lines with someone who actually knows how to handle an order.

That would be my reaction, too, except somebody has to help the customer. Trouble is, they only remember you if you walk away when they are having a problem like this. Help them out, and in six months it's, "'WHO?' communications". But, I RETIRED! John C. (Not Garand)