atcomsystems.ca/forum Forums Wiring - Telecom Carriers - Trunks & Services T1's, CSU's and DSU's t1 timing issue

1. i'll check this out when i get to the office but the pri/smart jack were only installed less than a year ago.

2. i bought the cable from monoprice. i'll change it when i get to the office but i haven't had any issues with their cables before. of course i've only used their cables for data, perhaps voice is more sensitive?

3. i don't think this is the issue. i've wiggled the cable before and haven't seen any drops but i'll try it again when i get into the office.

4. this is probably the issue but the card is fairly new. we purchased it this january and it was the latest rev that they had back then. the switchvox was installed in august last year with a single span card but we were having all sorts of echo problems so we switched to a dual span card with hw echo cancellation. i will never use their single span cards again and wish that they support sangoma cards in switchvox but they don't. i've asked them about it before

this is part of the log from last night. the hdlc errors were actually three pages worth but i didn't want to post them all here. do you think that they are related to the drops? i don't always see them when it get an alarm but they are there often enough to make me worry about it.

100 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
101 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
102 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
103 05/26/2009 5:41 AM NOTICE Last Message Repeated 3 times
104 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
105 05/26/2009 5:41 AM NOTICE Last Message Repeated 1 times
106 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
107 05/26/2009 5:41 AM NOTICE Last Message Repeated 1 times
108 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
109 05/26/2009 5:41 AM NOTICE Last Message Repeated 1 times
110 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
111 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
112 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
113 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
114 05/26/2009 5:41 AM NOTICE Last Message Repeated 1 times
115 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
116 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
117 05/26/2009 5:41 AM NOTICE Last Message Repeated 2 times
118 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
119 05/26/2009 5:41 AM NOTICE Last Message Repeated 3 times
120 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
121 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
122 05/26/2009 5:41 AM NOTICE Last Message Repeated 1 times
123 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
124 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
125 05/26/2009 5:41 AM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
126 05/26/2009 1:27 AM NOTICE Last Message Repeated 1 times
127 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): Error releasing mutex: Operation not permitted
128 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): mutex '&q->lock' freed more times than we've locked!
129 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): Error releasing mutex: Operation not permitted
130 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): mutex '&q->lock' freed more times than we've locked!
131 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): Error releasing mutex: Operation not permitted
132 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): mutex '&q->lock' freed more times than we've locked!
133 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): Error releasing mutex: Operation not permitted
134 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): mutex '&q->lock' freed more times than we've locked!
135 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): Error releasing mutex: Operation not permitted
136 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): mutex '&q->lock' freed more times than we've locked!
137 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): Error releasing mutex: Operation not permitted
138 05/26/2009 12:02 AM ERROR ../include/asterisk/lock.h: app_queue.c line 4506 (manager_queue_reload): mutex '&q->lock' freed more times than we've locked!

we're having good weather and the issue seems to have magically disappeared again. i'm not sure if it's a coincidence or not but i'm not really sure that we need a new card and i can almost guarantee that the issues will start up again as soon as the weather worsens.

Well, there is a lot of bad copper in Tampa. It's not uncommon to see a cable get 500-1000 feet longer when it rains.

With the D-Channel flapping like that it would explain all the dropped calls as well.

Looks like you've got a bunch of deadlocks too (All the queue messages). It's not related to your dropping calls but I figured I'd mention it as well.

I've got a guy who is doing some work for us that has a bit of experience with SwitchVox. You can try giving him at call at 863-393-9336. His name is Kevin.

we're having issues again and it's just thundering.

so bad copper could cause hdlc errors on the d-channel which would make the circuit bounce?

Bad copper can make the circuit do anything from noisy background to total service outage.

BTW, I posted the wrong number. That's my office line. You are more then welcome to call it but I'm usually comatose until around 10:30 in the morning. One of the side-effects of being the 3rd shift maintenance crew.

Kevin's number is 863-393-9339.

digium tested all the equipment last night and everything tested fine though we're still having a problem.

this has to be a telco issue then and it's like pulling teeth to get them to come out and actually find the root cause of this. you would think that they would acknowledge that its their problem since it only happens when the weather is bad...

Than you have more than just a slipping problem. Sure would like to see some T1 test results, but saw in your previous log you don't have that ability.

Does the system have an internal or external CSU? If it is external, has that been checked? (I quickly scanned the remarks, and may have missed the reference).

Some smart jacks do have the ability to log errors & alarms. If such a device is being used, Verizon can read the log.

I'm betting all those red alarms that show channel specific are red alarms on the T1. If so that means you are loosing signal. Which should have shown at the smart jack when the tech put his laptop on it. I've never seen any piece of equipment that show red on a channel, but I've never messed with VoIP stuff.