atcomsystems.ca/forum Forums TDM Business Telephone Systems Nortel Telephones & Systems BCM 400/can't dial out

Customer has a BCM 400 3.7 installed a few months ago and all was well until the Nor easter on Monday. The PRI is up, we can get incomming calls fine. Go to dial out and you get a fast busy after dialing the entire number. Had Tech Support web ex in, verified all programming was correct, he saw me try to dial out.

The customer has a XO PRI (Pool A dial 9).........now Verizon did have a major outage in the area this week and claim they have to rebuild the cable with a estimated completion of Saturday. However no one else in the building is down, just my client. I don't understand if it a cable, wouldn't that effect incomming calls as well? I am still waiting for XO to confirm a PIC for LD on the circuit level (wouldn't be the first time no carrier PIC caused this for this client). I'm told XO carries the local on the PRI (the customer claims to have SWB/AT&T PIC for local) and the PIC on LD was changed to Sprint with a due date of yesterday.

I'm dumbfounded..... any ideas? I'm thinking the circuit between XO and verizon CO but come back to why is inbound ok???????????

have you tried to enter a number in your destination route,i know that you have to first put one in then take the number out to make the routing table work wich i am sure you have tried
but maybe somehow it got removed good luck

The first I would do its go and Disable PRI card and reEnable it again. I had such a situation one time when after loop restoration I couldn't dial out and didn't have any busy lines in the Maintenance. Incoming same like in your case - no problems. Have you tried reset the system?

Thanks........I did a reboot, nothing....I did not reset the PRI card as the client is able to get incomming calls. XO tech called, feels they have been trouble shooting the wrong issue (checking the circuit, not the ability to dail out). He was able to break off a line and dial local and LD as a trunk not a two way trunk.

FYI......
The issue with this site was caused by caller ID. The Caller ID service was set by the carrier to send out names which were not recognized by the PRI which then dropped the call. It is a slightly longer explaination but I am having trouble explaining it without writing a book.
I do hope this scenario/solution is filed somewhere in the brain in case it happens to others. Its been a week plus of trouble shooting, pointing fingers and a client with no outbound service.
Beth