sundance-communications.com/forum Forums TDM Business Telephone Systems Vodavi Telephones & Systems STS and T-1 Outbound calling problems

I have a customer with an STS and a non-PRI T-1. They have a constant problem with outbound calling where after dialing they are getting a long pause and then a "number can not be completed as dialed from the carrier, Allegiance Telecom. Has anyone had/seen this problem before? Any ideas?

Thanks,
Chris

Is it a problem on every call? Are they dialing a 7 digit (local) or 10 digit (LD) call when the problem occurs? On T1 circuits, AT&T used to require end-users to send area code + number, not 1+ area code and number, I don't know about Allegiance. Are they using LCR for outbound calling?

In MA we have had to dial the area code for all numbers for a few years now. The problem it seems is that there is a connection time of about 3 seconds that needs to be maintainted, when dialing 9 to get an outside line and you get dial tone you need to wait for about 3 seconds from the time you push 9 till the time you dial. I turned on LCR for one day and it seemed to cause more problems and the customer requested it be turned off.

We work a lot with XO Communications, who took over Allegiance accounts. Very frequently, we are told that even local calls must be prefaced with 1+ area code.

It seems like that always works, while any variations are spotty at best. I really think it's a matter of the switch programmer that sets up the account. We see this more with PRI's or T1's than simple POTS customers. I don't have much experience with other CLECs, so I can't speak for all of them.

I think that a big part of the problem is that most CLEC's have their switches located in major metropolitan areas and any service your customer receives must follow the local dialing "rules" set up at the host switch's city.

I honestly believe that getting a good technician on the phone from the carrier will resolve your problem, but that's a shot in the dark.

------------------
Ed
---------
How come there's always enough time to go back and fix it a second time?

Spoke to XO again on this today. The customer has called and opened yet another ticket on the issue. Seems that now 1 out of 3 calls is getting the "call cannot be completed" message. XO (again this is an Allegiance Telecom customer under the umbrella of XO since XO bought Allegiance)claims that they are going to set up a meeting with a switch tech and myself for testing.

Any suggestions and ideas as to where to go when that happens?

Thanks,
~Chris

If you're getting the switch recording you are getting to them, so now they should be able to put up a trap to see what digits you are giving them. If the digits are correct then they have a problem. I can't see your system putting out intermitten incorrect digits, but I suppose it's possible. At any rate any carrier worth their salt can trap the digits to see if that is the problem, shouldn't need a meet to determine that.

Want to add it could be a problem with signaling, if it's wink maybe you're outpulsing before receiving the wink, for example.

[This message has been edited by justbill (edited May 24, 2005).]

A joint vendor meet having the XO tech plugging his test set directly into the network interface and placing calls should find the issue. Place 10 calls directly on the circuit sucessfully would probably point to a customer premise equipment issue. Be there for the tests to witness. You have no idea how many troubles are cleared by "FM".

[This message has been edited by RATHER BE FISHING (edited May 24, 2005).]

OK tests happened today. They (XO/Allegiance) tested behind the PBX and didn't come up with something that points towards a problem. So I am going to go onsite on Saturday morning and replace the KSU and change some things. If anyone has any ideas for me to look at while I am there that would be helpful. Dave G., head at Vodavi Tech Support said that maybe there is a bad DTMF receiver on the KSU but it is new, we put in a replacement when they moved in March to make our jobs easier (we downloaded and installed a "new" system in the new location and had it up and running and put the system that they had in the "lab"). I am going to replace the inhouse unit and try to switch card slots and cabinets.

Anyone know anything else to try?

Thanks,
~Chris

Seems to me you're going to a lot of trouble when putting a trap up would tell you Exactly why it's failing, but maybe I'm to old school, wanting to make the carrier do what I pay them for.

Replaced the KSU today, that Saturday just didn't work out. After working with XO (Allegiance) on this they showed errors coming into the Adtran DSX port (MANY errors) so I just decided to go ahead and put my Lab Box (software version P1.02.01) with an uploaded version of the latest WinDBA (from that morning) into it. All seems fine now but what I got from Vodavi it that the DTRU onboard units (there are 2 and they create the T-1 path for a phone call) one could be bad which is why I finally decided to replace the base box. Well after the fact I talked to Dave G at Vodavi and the errors could be caused by a bad PLLU unit connected to the system main board. Tomorrow will tell as I am sure that if there improvement (I tested it and didn't get the same problems after the fact but we all know that doesn't mean anything) I'll know tomorrow. Vodavi said they will ship a new PLLU if what I have all ready done didn't solve the problem. We'll just have to wait and see.

Worst part is, I have no lab/test unit now (sob sob) JK

~Chris.

Tell me your stories, I am so young and clueless.