I have a customer with an iDCS 500 R2. M software V2.48. TEPRI cards slots 1, 2, and 3. V1.07. The first 2 are pri's. One has 23 channels the other with 16 channels. The 3rd TEPRI is setup as E&M Immediate and used as an interface between the 500 and an auto dialer.

Toll deny and toll allow tables are both empty
Have tested this with station class of service 1, 2, and 3. All with the same results.

All is fine except they are getting busy signals on two local exchanges(7 digit dialing). I can call the numbers in the exchange from a cell phone with no problem. The busy is NOT a fast busy like you get from a toll deny table but a standard busy signal you would receive from the carrier.

Nuvox says they setup a mirrored PRI and had no trouble dialing that local exchange so of course it is up to me to prove my case.

Any Ideas????

Not sure. Turning ISDN Prog to ON helps with DTMF sending on a PRI trunk but usually that just helps with dialing digits after you make a call. Do you have LCR set up? If so make sure your digit entries that start with the numbers of those exchanges are set up correctly with the correct route in them.

No LCR at all.

I'd get the carrier involved. The PRI is obviously working and with no restrictions or LCR set up in the 500 system there is no reason you wouldn't be able to make a call to just two exchanges. See if they can run a trace on the PRI and see what it is receiving on their end when you make calls to those numbers. They may need to come to your site to do this with something like a T-byrd. It sounds like they got something wrong in their own routing tables.

I agree Ben. They claim they setup a mirrored PRI to this and had no problems.

I agree with requesting the provider assist with tracing the test calls. If the provider is supported by a 5ESS, the output message from a 'verify office' command (VFY:OFC,dn=xxxxxxx,dialed digits=xxxxxxx) would identify all steps of treatment for the call, begining at when the sent digits from that specific line are first received by the provider. When attempting the test calls to the impacted NXXs, is the standard busytone heard after all seven digits are entered, or immediately after entering the third digit? Is there a long silent pause heard prior to hearing the busytone?

After all seven digits are entered. Then there is a short pause then a busy signal. If it was the system then you would never get all seven digits entered.

Since you're receiving regular busytone for all calls to these 2 specific prefixes, I'd request Nuvox to conduct 'camp-on' tests to one of these busy calls to identify the cause of the busytone.

Cracker, look at this. This is a tech from the same provider you are having trouble with and on 7 digit dialing. This is with a compact that does not have PRI. I have had more trouble with these voip lines and Cisco IAD's and Adtrans. Most of trouble we found was in the programing of the Adtran or Cisco.

Thanks CMD_GUY I saw that post. I had the customer try dialing the 10 digit number and got the same thing. I just e-mailed him telling him to setup a vendor meet. I don't see how it could be in the 500 since you are able to dial all the digits and then there is a pause before the busy signal. I would get an imediate fast busy if it was the 500.

Thanks Mike I'm going to request that at the vendor meet. Their contract is coming up so we shouldn't have a lot of trouble getting them to troubleshoot this further.

Nuvox ran a trap on the pri's today and found that the numbers that are not working have been ported to Comcast. Comcast is rejecting the calls due to a protocal error. I will be going onsite on Monday and will post final results then. If anyone wants to see the trap info let me know.