sundance-communications.com/forum Forums Other TDM Phone Systems Executone-Isoetec Telephones & Systems 228 T-1 problems

Update:Well my customer is still dropping calls 80 or more a day Disco. super. shows them all. T-1 provider see's nothing wrong. I am to the point of putting a channel bank on this thing! Anyone have any ideas all my setttings are solid: lines are tie type 84 drop pulse is up to 20 from 14 what could it be? I really don'thave the time to mess with a channel bank it's like 2 steps back.

Thanks
Guys!

>>provider see's nothing wrong

They never do, then when you change something they blame it on you.
98 percent of the time it's the carrier.
Was the circuit up and working correctly b-4 the dropped call came into play, if so I'll lay odds that the carrier did some kind of upgrade or change in their system that caused it. But these types of problems are frustrating.
Good Luck

Did the customer change carriers? and that is when problem started?

It sound like there is a framing, or switch type error.

Hookup your laptop to the CSU and see what kind of errors you see on it. You can pinpoint what direction the problems are happening by looking at the CSU reports. Resetr reports and look again in 24 hours.

Good Luck!!

What Line type are you using? 84??

Also Disconnect supervision in the reports only means that the outside party was the first to disconnect. Either on purpose or due to a problem.

That is true if you are using an ESF CSU like a T-smart. but not on the T-serv which is most common. Perhaps a t-smart would be a good idea.

I am using a T serv 2, I did switch it out with no change. This problem just started out of nowhere one day it worked the next it started dropping. Which of coures points to the carrier. I am working with MCI here if that tells you anything. Verizon has checked and laid the blame square on MCI, What gets me..no errors on the T-1 screens no slips no alarms, the 228 see's nothing wrong and the busy signal I get when these calls drop. On the Executone you get dead air if the system drops it in most cases. Sometimes on an outbound long dist. call I get the busy signal and the "C" screen shows the call connected.

Thanks

You know this brings back some memories of a similiar problem on one account that had 3
T1 ckts on an IDS 432 same software.
After several vendor meets with telco, and replacing the T1 card, CSU, Power supplies
SBC finaly sent someone who took the time and found 1 pair on the T1 getting wet at a splice 2 blocks away, the pair was green and corroded, after he changed the pairs, the disconnect problem disappeared and has not come back since, over 2 years ago.
Rick

Well...I put in a channel bank. Had MCI make a change on the signal to it. Just did this and they still get dropped calls, dosent look good for MCI. -Rick I thought of that so I had Verizon check out the local equipment and they did find a problem and said they fixed it, but no change. Maybe they have a little mole chewing on the wires...ya never know. Ya know I think the problem is with these T1 providers now a days you have to talk to 3 different companies it is a real pain.

I have been following your posted message on your problem. When you mention mci, it brought back bad experience with them.
Customer with 6 pri, 3 t-1 and mci as the carrier. the Customer would start dropping calls, rna, numbers dialed local or ld wouldn't go through. Whenever they would start to get busy.
Mci said it had to be the equipment and not them. Converted the pri to t-1 with an adtran unit. Mci still said they had issues with the equipment. Conference call with many people, showed that Mci had an issue on the last mile of the circuit, to the site.
Since they corrected the last mile issue everything was working ok.

OK this may be a dumb question, but since you put a channel bank in I have to ask. Is this D4/AMI or ESF/B8ZS. The reason I have to ask is if it's D4 not seeing errors doesn't mean anything, the only time it will regester an error is if the error is at the same time as the check bit. The circuit must be taken out of service and tested ESF to seeing if there are errors or not, monitoring won't do the job.
Bill