some incoming long distance calls not going through on nortel 81c

[chansel77]

We are experiencing some problems with certain states being able to call our switch. When certain area codes call they get our all trunks are busy ran 2 ch 3 message. Wondering what this could be, most area codes call with no problems. Any help is appreciated.

 

[trvlr1]

Is that a message you have set up in your PBX or is it a telco message?

 

[chansel77]

it is our message. Verizon traces the call to us. Thats what i cannot understand. If other area codes make it through so should this one.

 

[trvlr1]

is this a PRI or T-1? If PRI have you tried to turn on d chan monitoring and compared what you get in for a "good" call versus a "bad" call?
Also, have you tried tracing in LD 80 and comparing what you are seeing?

 

[chansel77]

It is a PRI. I will turn on the d chan monitoring

 

[chansel77]

I told you wrong. Its a DTI Trunk

 

[trvlr1]

Can Verizon tell you exactly what they are sending you? They may be sending something incompatable with your requirements some how.

 

[KCFLHRC]

So is your RAN set up on Vacant Number Intercept or how is it exactly getting to the RAN?

 

[chansel77]

verizon is sending us 7. the ran message is call to vacant number intercept.

 

[KCFLHRC]

Are your extensions 7 digits in length?

 

[chansel77]

well our DID trunks are 4 digit and we had to add an IDC table to make them 7 digit on our location. What i dont know is what the other long distance carriers are sending us. I know verizon is sending 7 and it is not working. I am just wondering if the other carriers that are working, are sending something different.

 

[trvlr1]

get someone on the hook from Verizon, have someone from a good state call in, then from a bad state call in and have Verizon show you exactly what they are sending you.
Another thing to think about, what phone company is the call originating from? They may have incorrect information in their local C.O. that is sending the wrong info out.

 

[KCFLHRC]

The number of digits outpulsed is controlled by your serving C.O., not each individual carrier. Unless of course you have individual trunking from each of those carriers. What your saying is very confusing. If your DID trunks are 4 digits then why did you have to build and IDC table for 7 digits? Doesn't make sense to me. If you have a group of DID's that start at 2100 it shouldn't matter what part of the country I'm calling from you should always see 2100.

 

[chansel77]

we are military. It is in a regulation that we have to go to 7 digit dialing. The local carrier is AT&T and they were only sending 4. In order to be compliant, a vendor had to come in and put the table in for 7 digits. I think it is dumb, but unfortunately my thoughts dont count. I will try the trace from the areas that are working and compare to one that is not. Thank you both for your time.

 

[trvlr1]

I was not necessarily meaning the number of digits, but perhaps the type of information that was being sent is causing issues, or is perhaps wrong. (though checking the number of digits is a good plan too!)