MICS 7.1, cannot receive calls from some carriers...

[Missy8s]

Good morning,

I have a customer with an MICS 7.1 with (1) PRI that cannot receive calls from 'some carriers', namely Comcast land lines and AT&T cell phones.

I had a similar issue with a local college about two years back that turned out to be a 'digit translation' issue with VoIP lines.

If a caller attempts to call a line from one of these carriers (primarily intralata) they hear a call connect failure tone with a carrier intercept message.

"Your call cannot be completed as dialed"

Are there any settings that might affect or cause this condition in the PRI or DID setup?

 

[Missy8s]

FYI / maybe important: There is no failure code accompanying the intercept message...

 

[Crowtalks]

Most likely the issue is going to be in the TELCO's switch translations database for the PRI circuit...especially if another local landline can receive calls from those numbers. If another local landline can't then it still may be a translations issue with the TELCO

Jim

"If I had known it would turn out like this, I would have become a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E Avaya IP Office
Mitel 3300 Basic & Advanced 5000 NuPoint I&M MiCloud

 

[Missy8s]

Are there any settings I should check, just to be on the safe side, before I potentially get into a shouting match with the provider?

 

[Crowtalks]

Not that I can think of...the PRI setup is pretty basic here...you direct incoming through target lines, the telco sends you 4 to ten digits, all you are is a receiving bucket...

The last time I had issues like this was when we "ported" in numbers from a CLEC and our Telco database translations team had certain NXXs built in the wrong incoming route tables.

Are these numbers that can't call you local or long distance?

What recording are they receiving when they attempt to call you?

If they are LD, are they calling you via a toll free number? Can anyone else call you on these specific numbers that these carriers cannot?

Jim

"If I had known it would turn out like this, I would have become a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E Avaya IP Office
Mitel 3300 Basic & Advanced 5000 NuPoint I&M MiCloud

 

[Missy8s]

All of the affected calls are local, the issue appears to vary by carrier.

So far the affected carriers are AT&T (cell phones) and Comcast land lines attempting to call DID's.

The primary number is the only one that was ported but it is NOT part of the DID range but you can call the main number from the affected Comcast / AT&T lines.

The DID range is XXX-371-7054 to 7102.

The primary is XXX-533-0500 and it is assigned to line 257 as a DID.

The area codes and office codes ARE different.

 

[allworxguy]

Are all the DIDs assigned to target lines? Some carriers will reject calls to unassigned numbers.

Marv ccna

http://www.telemarv.ca

Sales, Installation & Service for Norstar, BCM, Samsung & Allworx Serving Ottawa and Eastern Ontario since 1990

 

[Missy8s]

Yes, all active DID's are assigned to target lines but some DID's are reserved for future use and therefor unassigned to targets at this time.

 

[Crowtalks]

These carriers usually interface to an ILEC via wireless style trunks and AT&T and Comcast may very well share the same trunks...I still believe the issue is going to be a translations/routing issue either on your telco's end or the other end...either way it would be the telco's translations department that would work with the other carriers (typically).

If (as Marv said) the DIDs that are affected terminate to a set via target lines, and these DIDs can be dialed locally by other carriers, I still feel you are golden and have a great case to present to your telco.

Jim

"If I had known it would turn out like this, I would have become a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E Avaya IP Office
Mitel 3300 Basic & Advanced 5000 NuPoint I&M MiCloud