Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

T1 problem

Status
Not open for further replies.

obobob

Technical User
Oct 20, 2002
112
CA
Hi all,
I have a MICS 4.1 with T1; lately I started getting Evt 265 and Alarm 75.
The Telco insists that the circuit is clean and the problem is on my side.
I tried reset, reboot, and reseat the DTI card with not much changed.

During the day I only get Evt 265 every few hours but the alarms only happens over night. So during the day we are still able to use the lines.
Any ideas on how to proceed with this will be appreciated.
 
Alarm 265 - Network did not acknowledge the KSU request to seize the line.

The alarm 75's mean the circuit is going down each night. That in and of itself is suspicious. Why every NIGHT. One might think that the Telco is running some kind of maintenance and it's pulling the circuit down.

For grins and giggles, assign each channel to a 7324 phone, this way you can hit each channel and make a call out.

It sounds as though you might have a dead channel. The MICS is sending a signal out to Telco asking for "dial tone" and not getting the response.That would throw an event 265.

Does the customer occassionally go to dial out, get an error then have to hang up and try again?



MRoberts
 
I got alarm 75 all the time a while back. I have a CSU/DSU inline on the T1 to split out data. This allowed me to tell the telco exactly when the frame slip occured. They setup a monitor on my T1 for a week and didn't find anything. Then the problem came back. They set it up again. This time they must have figured it out, because I haven't seen on in a long time. Of course they didn't tell me what the problem was, just that they think they figured it out.
 
One more thing to check, verify the programming is correct on all of your channels. If for some reason while programming the T channels you missed changing one to E&M and it stayed loop, it could cause the channel to not function properly and could cause a 265.

MRoberts
 
Thanks for the replies,
The programming is good (all E&M), some of the users are experiencing (no service) on lines some times but it moves from one line to another.
The Telco did monitor the T1 for a while and they say it is clean
 
Yes, but have you physically assigned all channels to a phone and physically pressed those buttons and made sure you do not have a dead channel???

The users wouldn't have channels specifically assigned to the phone for outgoing calls so they wouldn't really know if it was one particular channel or couple of channels or not. Not unless they are really observant.

Telco may be able to monitor one side but if we have a bad channel on our side, their side would run clean.

MRoberts
 
I have physically assigned all channels to 2 phones and physically pressed those buttons and I made sure I do not have a dead channel.
The last log I had Evt.265-241 time 10:03
 
If telco is monitoring the circuit remotely, I would set up a vendor meet for them to come out with a Tberd and monitor it directly from the front of our DTI card.

MRoberts
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top