DTM Weirdness -- CO Issues? 1

[snd1234]

I'm consistently getting some DTM related issues every day at particular times. Here is an example of a sequence in my alarm logs:

**********

2011-6-10 824am Core Telephony - "Errored Second"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.

2011-6-10 824am Core Telephony - "Degraded Minute"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.

2011-6-10 902am Core Telephony - Digital trunking clock in free run.

2011-6-10 902am Core Telephony - "Degraded Minute"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.

2011-6-10 903am Core Telephony - "Errored Second"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.

2011-6-10 903am Core Telephony - "Loss of Frame" short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.

2011-6-10 903am Core Telephony - "Degraded Minute"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.

**********

So far, I haven't suffered any ill effects from these problems but I just recently migrated and we don't have a huge call volume so perhaps I'm just getting lucky. The weird thing about it is that it CONSISTENLY happens 2-3 times every day. Two times in the morning at about 825am and 1030am. I've had my system in testing for weeks and it always occurred but I started writing down times a few days ago. Here's an example of what I'm taking about

6/6 - 827am
6/6 - 921am
6/6 - 1023am
6/7 - 824am
6/7 - 921am
6/8 - 849am
6/8 - 959pm
6/9 - 855am
6/10 - 824am
6/10 - 902am
6/11 - 841am
6/11 - 937am

I have my DTM set for "Primary External" clocking, my system time is done by NTP, and I am fully patched to latest SU for the 4.0 platform.

I use RJ45 CAT6 cabling between the smartjack and the BCM.

 

[snd1234]

Other info:

Single DTM module
Lives in the main cabinet
Assigned to Bus 7
No error lights or anything on the module
Was a new module I personally broke the seal on

 

[oldestgeek]

Could be a bad DTM but I'd eliminate everything else first. Have your service provider run a test to the smart jack during the times you're getting the errors. Also check the cabling to make sure it doesn't pass too closely to light ballasts, electric motors, or anything that could introduce noise onto the cable. Also, I avoid using Ethernet cables to connect DTM circuits - they're wired incorrectly, although they usually will work. You're better off using a shielded cat 3 cable wired for T1 specs.

 

[snd1234]

Actually, the PRI runs about 150ft through two floors between the smartjack and the demarc so perhaps we need to switch to shielded. I was wondering if that might be the answer.

I will try that before subjecting myself to my provider's idiocy.

 

[telcodog]

Wouldn't it be easier to just move the smart jack? You already have cabling between the two locations.