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 dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Drops in clusters, same callers, is a bad VCM to blame?

Status
Not open for further replies.

573dawn

IS-IT--Management
Jun 13, 2007
300
US
Hi All, I have been trying to find some pattern to my dropped calls. What I have seen in the last 2 days is very curious.

4 drops in a cluster yesterday, all were the same caller. Found out about it too late to see what was showing in monitor, BUT

This morning, 4 drops, all same caller, all on IP Line 40 (for those of you who know the story). Times were 9:08, 9:10, 9:18, & 9:45.

Apparently this is the norm, where all the drops are within a smll timeframe, and all involve the same caller. The caller can be wireless or wireline.

All of these drops can be directly correlated with the error:
169542025mS ERR: EXCEPTION ON MEDIA CONNECTION --- Error from protocol entity! MSDSE --- local timer expired ...

A bad VCM unit has been suggested by intrigrant, anyone else agree?

Thanks, Dawn
 
Incidentally to ALL, I have set up my monitors on all related intefaces, so far today I have seen no errors for any interface related to my trouble site. In addition, I see no clock slips on any site.

There has been one drop that I know of so far today, it came with the Media Exception error, as expected.

My BP has agreed to order a new VCM, but he wasn't happy about it and doesn't think it will make a difference. He is very much stuck on my T1 and ATT being at fault. We should have the new VCM next Wednesday. Meanwhile I am going to monitor the T1 and all related elements for errors, packet loss, etc.

I might mention that when I did tests with ATT the last time, we broke this circuit over and over again to see what Monitor would report, and also how long it would take to see our Company software disconnect. It took at least 4-5 seconds for Monitor to lose contact and actually say so. It took that long for our Company software to kick the user off as well. Breaks of less than 4-5 seconds didn't register in Monitor at all. Every test I've had ATT do, and there have been lots, has shown nearly no lost seconds, and the occasional path error, nothing more. My routers also have very low errors.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top