|
|
Joined: Jun 2005
Posts: 23
Member
|
|
Member
Joined: Jun 2005
Posts: 23 |
Recently we began having Slip and Frame errors on the Mitel T1 card that interfaces with our Asterisk PBX. These errors are so numerous that they exceed the threshold and the T1 card is automatically taken offline.
We have noticed the following from our testing:
1) When Asterisk is not running, the errors still occur.
2) When we tried a different Asterisk T1 card the errors still occur.
3) When a loopback plug is plugged into the Mitel in place of the Asterisk server, the errors cease.
4) We hear pops/clicks/beeps on the line during calls. We have found they happen across all channels. User 1 was on one phone in the same room as User 2 on a different call on speaker and the beeps were synchronized over the two separate calls.
5) We found that the 4 channels that are in use for outbound dialing is set to LS/GS (loop start/ground start). We have those 4 channels set to E&M Wink on the Asterisk side.
Here are my questions:
a) There is no setting for Loop/Ground Start as one signaling protocol in Asterisk. It's one or the other (loop or ground). We tested both to no avail. Could this be causing the Slip/Frame errors? As well as the pops/clicks/beeps that the users hear?
b) Where can we view the winkstart/etc parameters for the T1 card. We looked around but didn't find it.
c) How do we view what the current Slip/Threshold settings are and change them? If we increase them to the max hopefully we can mask the issue for the time being.
d) We are only using channels 1-17 for incoming and 21-24 for outgoing calls. Could the fact that we aren't using all 24 channels account for the problems we are having?
Thanks!!
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Mar 2004
Posts: 880 Likes: 1
Member
|
|
Member
Joined: Mar 2004
Posts: 880 Likes: 1 |
There can only be one clock source in a T1 network. Sounds to me like both (or neither) are set to be the 'master' clock source.
|
|
|
|
|
Joined: Aug 2005
Posts: 2,125
Member
|
|
Member
Joined: Aug 2005
Posts: 2,125 |
I think Flood has the right answer. You can see the current sync source by reading the logs. When the T-1s go up or down, there should be an entry to the effect that xxx is the current sync source.
Maintenance, 7,2,4,enter,enter
If not, I'd check to see if your cross-connect wiring is crossing any sort of high-voltage line or even 110 power.
Also, is this an HTG T-1, or is it a channel-bank?
If it's a channel-bank, there may be interference issues on the telco side (where each channel is an analog line of some sort).
If it's not a clock issue, I'm betting on a channel-bank issue. Pops and snaps should be filtered out automatically on a digital line such as a t-1.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
Member
Joined: Jun 2005
Posts: 23 |
Thanks for the replies.
I'll check the Mitel logs for the timing source.
We'll also check on the power lines.
It isn't a channel bank, the Mitel is connected to t T1 card in a Dell server that is running an software PBX. The software PBX (Asterisk) receives VoIP calls and routes them into the Mitel.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
Member
Joined: Jun 2005
Posts: 23 |
Unfortunately the Maint log isn't showing who the sync source is. Here is the last 50 lines: ³2005-OCT-14 12:44:38 Tot alarm went from MAJOR to No Alarm ³
³ Alarm level change due to Bay 02 trunks ³
³ ³
³2005-OCT-14 12:44:38 T1/BRI card at 02 06 00 00 ³
³ alarm condition is now cleared ³
³ ³
³2005-OCT-14 12:44:18 Tot alarm went from No Alarm to MAJOR ³
³ Alarm level change due to Bay 02 trunks ³
³ ³
³2005-OCT-14 12:44:18 T1/BRI card at 02 06 00 00 ³
³ is in red alarm condition due to loss of sync
³ ³
³2005-OCT-14 08:15:27 T1/BRI card at 02 06 00 00 ³
³ has exceeded the maint loss frame threshold ³
³ ³
³2005-OCT-14 08:15:27 T1/BRI card at 02 06 00 00 ³
³ has exceeded the maintenance slip threshold ³
³ ³
³2005-OCT-14 07:03:28 Tot alarm went from MAJOR to No Alarm ³
³ Alarm level change due to Bay 02 trunks ³
³ ³
³2005-OCT-14 07:03:28 T1/BRI card at 02 06 00 00 ³
³ alarm condition is now cleared
³ ³
³2005-OCT-14 07:03:05 T1/BRI card at 02 06 00 00 ³
³ is receiving a yellow alarm ³
³ ³
³2005-OCT-14 07:03:04 T1/BRI card at 02 06 00 00 ³
³ is in red alarm condition due to loss of sync ³
³ ³
³2005-OCT-14 07:02:46 BAY number 02 reported cause: reset by MCC ³
³ at address = 000000 ³
³ ³
³2005-OCT-14 07:00:50 UNIVERSAL CARD failed at 02 07 00 00 ³
³ Card removed Alarm Code = 102
³ ³
³2005-OCT-14 07:00:50 MUSIC PAGER MODULE failed at 02 07 02 00 ³
³ Card removed Alarm Code = 102 ³
³ ³
³2005-OCT-14 07:00:50 T1 TRUNK CARD failed at 02 06 00 00 ³
³ Card removed Alarm Code = 102 ³
³ ³
³2005-OCT-14 07:00:50 BAY number 02 msg link failure! ³
³ ³
³ ³
³2005-OCT-14 06:53:22 T1/BRI card at 02 06 00 00 ³
³ removed from service & transmitting yellow alarm
³ ³
³2005-OCT-14 06:53:22 Tot alarm went from No Alarm to MAJOR ³
³ Alarm level change due to Bay 02 trunks ³
³ ³
³2005-OCT-14 06:53:22 T1/BRI card at 02 06 00 00 ³
³ has exceeded the service slip threshold ³
³ ³
³2005-OCT-13 23:07:51 T1/BRI card at 02 06 00 00 ³
³ has exceeded the maintenance slip threshold ³
³ ³
³2005-OCT-13 22:50:48 T1/BRI card at 02 06 00 00 ³
³ has exceeded the maint loss frame threshold
³ ³
³2005-OCT-13 21:56:48 Tot alarm went from MAJOR to No Alarm ³
³ Alarm level change due to Bay 02 trunks ³
³ ³
³2005-OCT-13 21:56:48 T1/BRI card at 02 06 00 00 ³
³ alarm condition is now cleared ³
³ ³
³2005-OCT-13 21:56:22 T1/BRI card at 02 06 00 00 ³
³ is receiving a yellow alarm ³
³ ³
³2005-OCT-13 21:56:22 T1/BRI card at 02 06 00 00 ³
³ is in red alarm condition due to loss of sync
³ ³
³2005-OCT-13 21:56:03 BAY number 02 reported cause: power up ³
³ at address = 000000 ³
³ ³
³2005-OCT-13 21:55:04 UNIVERSAL CARD failed at 02 07 00 00 ³
³ Card removed Alarm Code = 102 ³
³ ³
³2005-OCT-13 21:55:04 MUSIC PAGER MODULE failed at 02 07 02 00 ³
³ Card removed Alarm Code = 102 ³
³ ³
³2005-OCT-13 21:55:04 T1 TRUNK CARD failed at 02 06 00 00 ³
³ Card removed Alarm Code = 102
³ ³
³2005-OCT-13 21:55:04 Tot alarm went from No Alarm to MAJOR ³
³ Alarm level change due to Bay 02 pcm ³
³ ³
³2005-OCT-13 21:55:04 BAY number 02 msg link failure! ³
³ ³
³ ³
³2005-OCT-13 19:29:34 T1/BRI card at 02 06 00 00 ³
³ has exceeded the maintenance slip threshold ³
³ ³
³2005-OCT-13 19:04:18 T1/BRI card at 02 06 00 00 ³
³ has exceeded the maint loss frame threshold
³ ³
³2005-OCT-13 18:03:28 Tot alarm went from MAJOR to No Alarm ³
³ Alarm level change due to Bay 02 trunks ³
³ ³
³2005-OCT-13 18:03:28 T1/BRI card at 02 06 00 00 ³
³ alarm condition is now cleared ³
³ ³
³2005-OCT-13 18:02:58 T1/BRI card at 02 06 00 00 ³
³ is receiving a yellow alarm ³
³ ³
³2005-OCT-13 18:02:58 T1/BRI card at 02 06 00 00 ³
³ is in red alarm condition due to loss of sync Can you make anything out of these logs?
|
|
|
|
|
Joined: Aug 2005
Posts: 2,125
Member
|
|
Member
Joined: Aug 2005
Posts: 2,125 |
I am not 100% certain, but it looks like you have no sync source, so the T-1 (when it's working) is "free-wheeling" (i.e. each end is trying to independently be its own clock). This would explain the problem.
To simplify: DWFlood is correct. In CDE form 44, set the T-1 card at the PBX to be the Primary Clock Source, and you should be good to go.
FYI: Red Alarm means "I have a problem" and Yellow Alarm means "the other end has a problem."
Also, quick question:
³
2005-OCT-13 21:55:04 UNIVERSAL CARD failed at 02 07 00 00 ³ ³ Card removed Alarm Code = 102 ³ ³ ³ ³
2005-OCT-13 21:55:04 MUSIC PAGER MODULE failed at 02 07 02 00 ³ ³ Card removed Alarm Code = 102 ³ ³
2005-OCT-13 21:55:04 T1 TRUNK CARD failed at 02 06 00 00 ³ ³ Card removed Alarm Code = 102
You're not trying to Hot Swap the T-1 or Universal card, are you? Because those are High Power cards, and are NOT hot swappable. If you need to pull them for whatever reason, you MUST shut down that bay first... and preferably the whole PBX.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
Member
Joined: Jun 2005
Posts: 23 |
There are 2 T1 cards in the Mitel. The first card (set as primary timing cource) is connected to the telco. The 2nd T1 card (set as secondary timing source) is the card that interfaces with the Asterisk server's T1 card (I have had this set to be the timing source as well as to look down the span for the timing).
Could I be running into problems both ways?
1) With the Asterisk servers T1 card set as Primary timing source could cause the 2nd Mitel card (which it interfaces with) to see timing from 2 places (the Asterisk T1 card and the 1st Mitel Card).
2) With the Asterisk card set to look to the 2nd Mitel card for the timing could cause would prevent it from seeing any timing at all. Or does the 2nd Mitel card (that is set to be the secondary timing source for the Mitel) pass along the timing from the 1st T1 card to the Asterisk T1 card.
ALSO:
Those errors seem to generate when the T1 card fails due to the excessive errors and goes offline. The errors you mention above were logged during off peak hours and noone was in the building at the time.
|
|
|
|
|
Joined: Oct 2004
Posts: 1,057
Member
|
|
Member
Joined: Oct 2004
Posts: 1,057 |
How about the AMI vs/ B8ZS settings? If the clocking sources are set, these settings would be the only thing left, other than changing out the clock itself! Otherwise, shift the Asterisk T1 to the primary (in form 44), and see if anything changes.
FYI, not to be rude, but the high power cards are definitely hot swappable. The high power just makes sure they're in the right area of the bay.
You shouldn't have to shut down to change them out.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
Member
Joined: Jun 2005
Posts: 23 |
We've tried changing the signaling and coding to no avail. I'm not so sure the the clocking sources are set at all. I think there is a conflict with the timing source. (See previous post re: Timing)
|
|
|
|
|
Joined: Aug 2005
Posts: 2,125
Member
|
|
Member
Joined: Aug 2005
Posts: 2,125 |
Whichever card is set as primary clock source in form 44 will pass clock to the other t-1 card. I recommend making the Telco t-1 primary clock in form 44. The secondary card should not have clock set at the other end (by Asterisk), but you can list it as secondary clock source, in form 44.
Also, are you seeing other problems in the t-1? All zeroes, bi-polar variations, slips?
In maintenance, reports, status, bay/slot/circuit, 2 enter 6 enter enter enter enter (4x enter), you should see your current t-1 status, with sync and link info on the side.
|
|
|
|
Forums84
Topics94,512
Posts639,931
Members49,844
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (justbill),
248
guests, and
53
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
