My PRI is being reset at least once a day with the following errors in the
logs.
zaptel, zapata, libpri, and asterisk are from CVS this morning.. This has
been happening for weeks on all versions (including -stable).
the T100P card appears to NOT be sharing an IRQ.
xenon# cat /proc/interupts
CPU0
0: 1203977 XT-PIC timer
1: 3 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 12004595 XT-PIC t1xxp
8: 1 XT-PIC rtc
9: 1046347 XT-PIC eth0
14: 21317 XT-PIC ide0
NMI: 0
ERR: 0
/
Is this something I should be seeking support from Digium on being their
card?
Apr 12 11:04:59 WARNING[1226062640]: PRI: Short write: -1/15 (Unknown
error 500)
Apr 12 11:04:59 WARNING[1226062640]: Detected alarm on channel 1: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 2: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 2
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 3: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 3
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 4: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 4
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 5: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 5
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 6: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 6
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 7: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 7
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 8: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 8
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 9: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 9
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 10: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 10
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 11: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 11
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 12: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 12
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 13: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 13
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 14: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 14
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 15: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 15
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 16: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 16
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 17: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 17
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 18: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 18
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 19: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 19
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 20: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 20
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 21: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 21
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 22: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 22
Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 23: Red
Alarm
Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation
on channel 23
Apr 12 11:04:59 WARNING[1184099120]: PRI: Read on 77 failed: Unknown error
500
Apr 12 11:04:59 NOTICE[1184099120]: PRI got event: 4 on span 1
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 1
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 2
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 3
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 4
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 5
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 6
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 7
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 8
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 9
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 10
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 11
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 12
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 13
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 14
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 15
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 16
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 17
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 18
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 19
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 20
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 21
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 22
Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 23
Apr 12 11:05:04 WARNING[1184099120]: PRI: Read on 77 failed: Unknown error
500
Apr 12 11:05:04 NOTICE[1184099120]: PRI got event: 5 on span 1
Thanks,
-Mike
This doesn't appear to be a load issue, since normally in that case I would
expect you would get a lot of (usually harmless) "frame reject"
messages in
your /var/log/asterisk/messages file, and perhaps an occasional
"missed/double interrupt" message on the console.
I wonder if there have been new bugs introduced in the PRI code. I've seen
a lot of changes in the timing section of the code at least on the dev list.
By all means, report it directly to them (a phone call is best).
Cheers
Scott Stingel
www.evt.media.com
-----Original Message-----
From: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Mike Sturdee
Sent: Monday, April 12, 2004 8:30 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] T100P / ZAP / PRI errors
My PRI is being reset at least once a day with the following errors in the
logs.
zaptel, zapata, libpri, and asterisk are from CVS this morning.. This has
been happening for weeks on all versions (including -stable).
the T100P card appears to NOT be sharing an IRQ.
xenon# cat /proc/interupts
CPU0
0: 1203977 XT-PIC timer
1: 3 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 12004595 XT-PIC t1xxp
8: 1 XT-PIC rtc
9: 1046347 XT-PIC eth0
14: 21317 XT-PIC ide0
NMI: 0
ERR: 0
/
Is this something I should be seeking support from Digium on being their
card?
Apr 12 11:04:59 WARNING[1226062640]: PRI: Short write: -1/15 (Unknown error
500) Apr 12 11:04:59 WARNING[1226062640]: Detected alarm on channel 1: Red
Alarm Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 2: Red
Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo
cancellation on channel 2 Apr 12 11:04:59 WARNING[1192491824]: Detected
alarm on channel 3: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to
disable echo cancellation on channel 3 Apr 12 11:04:59 WARNING[1192491824]:
Detected alarm on channel 4: Red Alarm Apr 12 11:04:59 WARNING[1192491824]:
Unable to disable echo cancellation on channel 4 Apr 12 11:04:59
WARNING[1192491824]: Detected alarm on channel 5: Red Alarm Apr 12 11:04:59
WARNING[1192491824]: Unable to disable echo cancellation on channel 5 Apr 12
11:04:59 WARNING[1192491824]: Detected alarm on channel 6: Red Alarm Apr 12
11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on channel
6 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 7: Red
Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo
cancellation on channel 7 Apr 12 11:04:59 WARNING[1192491824]: Detected
alarm on channel 8: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to
disable echo cancellation on channel 8 Apr 12 11:04:59 WARNING[1192491824]:
Detected alarm on channel 9: Red Alarm Apr 12 11:04:59 WARNING[1192491824]:
Unable to disable echo cancellation on channel 9 Apr 12 11:04:59
WARNING[1192491824]: Detected alarm on channel 10: Red Alarm Apr 12 11:04:59
WARNING[1192491824]: Unable to disable echo cancellation on channel 10 Apr
12 11:04:59 WARNING[1192491824]: Detected alarm on channel 11: Red Alarm Apr
12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on
channel 11 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel
12: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo
cancellation on channel 12 Apr 12 11:04:59 WARNING[1192491824]: Detected
alarm on channel 13: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable
to disable echo cancellation on channel 13 Apr 12 11:04:59
WARNING[1192491824]: Detected alarm on channel 14: Red Alarm Apr 12 11:04:59
WARNING[1192491824]: Unable to disable echo cancellation on channel 14 Apr
12 11:04:59 WARNING[1192491824]: Detected alarm on channel 15: Red Alarm Apr
12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on
channel 15 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel
16: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo
cancellation on channel 16 Apr 12 11:04:59 WARNING[1192491824]: Detected
alarm on channel 17: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable
to disable echo cancellation on channel 17 Apr 12 11:04:59
WARNING[1192491824]: Detected alarm on channel 18: Red Alarm Apr 12 11:04:59
WARNING[1192491824]: Unable to disable echo cancellation on channel 18 Apr
12 11:04:59 WARNING[1192491824]: Detected alarm on channel 19: Red Alarm Apr
12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on
channel 19 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel
20: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo
cancellation on channel 20 Apr 12 11:04:59 WARNING[1192491824]: Detected
alarm on channel 21: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable
to disable echo cancellation on channel 21 Apr 12 11:04:59
WARNING[1192491824]: Detected alarm on channel 22: Red Alarm Apr 12 11:04:59
WARNING[1192491824]: Unable to disable echo cancellation on channel 22 Apr
12 11:04:59 WARNING[1192491824]: Detected alarm on channel 23: Red Alarm Apr
12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on
channel 23 Apr 12 11:04:59 WARNING[1184099120]: PRI: Read on 77 failed:
Unknown error 500 Apr 12 11:04:59 NOTICE[1184099120]: PRI got event: 4 on
span 1 Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 1 Apr 12
11:05:04 NOTICE[1192491824]: Alarm cleared on channel 2 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 3 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 4 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 5 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 6 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 7 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 8 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 9 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 10 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 11 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 12 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 13 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 14 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 15 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 16 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 17 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 18 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 19 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 20 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 21 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 22 Apr 12 11:05:04
NOTICE[1192491824]: Alarm cleared on channel 23 Apr 12 11:05:04
WARNING[1184099120]: PRI: Read on 77 failed: Unknown error 500 Apr 12
11:05:04 NOTICE[1184099120]: PRI got event: 5 on span 1
Thanks,
-Mike
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
I'm running Zaptel CVS from April 8, LibPRI CVS April 8, and v-1.0 CVS April 7. With dual T400P cards with no PRI errors at all. Possibly something driver/config related? Are you timing from your PRI? I remember getting some PRI errors when my timing config was hosed. Could you post your zaptel.conf? -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Scott Stingel Sent: Monday, April 12, 2004 12:09 PM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] T100P / ZAP / PRI errors Mike- Do you have access to any kind of PRI test set, like a T-Bird or something. A red alarm would be easy to capture I imagine - it would be nice to confirm that it's a problem particular to your site. The reason I mention software is that I've noticed a lot of other messages regarding these spurious alarms that immediately clear. I've noticed changes in the code having to do with the timing source. But maybe you're right about the telco doing something odd! Cheers Scott www.evtmedia.com -----Original Message----- From: Mike Sturdee [mailto:sturdee@pathwaynet.com] Sent: Monday, April 12, 2004 9:00 AM To: Scott Stingel Cc: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] T100P / ZAP / PRI errors I have been seeing this for over a month, and blaming it on our generally incompetent telco, so it's definately not a new issue. On Mon, 12 Apr 2004, Scott Stingel wrote:> This doesn't appear to be a load issue, since normally in that case I > would expect you would get a lot of (usually harmless) "frame reject" > messages in your /var/log/asterisk/messages file, and perhaps an > occasional "missed/double interrupt" message on the console. > > I wonder if there have been new bugs introduced in the PRI code. I've > seen a lot of changes in the timing section of the code at least on thedev list.> > By all means, report it directly to them (a phone call is best). > > Cheers > Scott Stingel > > www.evt.media.com > > > -----Original Message----- > From: asterisk-users-admin@lists.digium.com > [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Mike > Sturdee > Sent: Monday, April 12, 2004 8:30 AM > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] T100P / ZAP / PRI errors > > My PRI is being reset at least once a day with the following errors in > the logs. > > zaptel, zapata, libpri, and asterisk are from CVS this morning.. This > has been happening for weeks on all versions (including -stable). > > the T100P card appears to NOT be sharing an IRQ. > > xenon# cat /proc/interupts > CPU0 > 0: 1203977 XT-PIC timer > 1: 3 XT-PIC keyboard > 2: 0 XT-PIC cascade > 5: 12004595 XT-PIC t1xxp > 8: 1 XT-PIC rtc > 9: 1046347 XT-PIC eth0 > 14: 21317 XT-PIC ide0 > NMI: 0 > ERR: 0 > / > > Is this something I should be seeking support from Digium on being > their card? > > > Apr 12 11:04:59 WARNING[1226062640]: PRI: Short write: -1/15 (Unknown > error > 500) Apr 12 11:04:59 WARNING[1226062640]: Detected alarm on channel 1: > Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on > channel 2: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to > disable echo cancellation on channel 2 Apr 12 11:04:59 > WARNING[1192491824]: Detected alarm on channel 3: Red Alarm Apr 12 > 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation onchannel 3 Apr 12 11:04:59 WARNING[1192491824]:> Detected alarm on channel 4: Red Alarm Apr 12 11:04:59WARNING[1192491824]:> Unable to disable echo cancellation on channel 4 Apr 12 11:04:59 > WARNING[1192491824]: Detected alarm on channel 5: Red Alarm Apr 12 > 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 5 > Apr 12 > 11:04:59 WARNING[1192491824]: Detected alarm on channel 6: Red Alarm > Apr 12 > 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on > channel > 6 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 7: > Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo > cancellation on channel 7 Apr 12 11:04:59 WARNING[1192491824]: > Detected alarm on channel 8: Red Alarm Apr 12 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 8 Apr12 11:04:59 WARNING[1192491824]:> Detected alarm on channel 9: Red Alarm Apr 12 11:04:59WARNING[1192491824]:> Unable to disable echo cancellation on channel 9 Apr 12 11:04:59 > WARNING[1192491824]: Detected alarm on channel 10: Red Alarm Apr 12 > 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 10 > Apr > 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 11: Red > Alarm Apr > 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation > on channel 11 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on > channel > 12: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable > echo cancellation on channel 12 Apr 12 11:04:59 WARNING[1192491824]: > Detected alarm on channel 13: Red Alarm Apr 12 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 13 > Apr 12 11:04:59 > WARNING[1192491824]: Detected alarm on channel 14: Red Alarm Apr 12 > 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 14 > Apr > 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 15: Red > Alarm Apr > 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation > on channel 15 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on > channel > 16: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable > echo cancellation on channel 16 Apr 12 11:04:59 WARNING[1192491824]: > Detected alarm on channel 17: Red Alarm Apr 12 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 17 > Apr 12 11:04:59 > WARNING[1192491824]: Detected alarm on channel 18: Red Alarm Apr 12 > 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 18 > Apr > 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 19: Red > Alarm Apr > 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation > on channel 19 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on > channel > 20: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable > echo cancellation on channel 20 Apr 12 11:04:59 WARNING[1192491824]: > Detected alarm on channel 21: Red Alarm Apr 12 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 21 > Apr 12 11:04:59 > WARNING[1192491824]: Detected alarm on channel 22: Red Alarm Apr 12 > 11:04:59 > WARNING[1192491824]: Unable to disable echo cancellation on channel 22 > Apr > 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 23: Red > Alarm Apr > 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation > on channel 23 Apr 12 11:04:59 WARNING[1184099120]: PRI: Read on 77 failed: > Unknown error 500 Apr 12 11:04:59 NOTICE[1184099120]: PRI got event: 4 > on span 1 Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel > 1 Apr 12 > 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 2 Apr 12 > 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 3 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 4 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 5 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 6 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 7 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 8 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 9 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 10 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 11 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 12 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 13 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 14 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 15 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 16 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 17 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 18 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 19 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 20 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 21 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 22 Apr 12 11:05:04 > NOTICE[1192491824]: Alarm cleared on channel 23 Apr 12 11:05:04 > WARNING[1184099120]: PRI: Read on 77 failed: Unknown error 500 Apr 12 > 11:05:04 NOTICE[1184099120]: PRI got event: 5 on span 1 > > > Thanks, > > -Mike > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-Mike =================================Network Engineer Pathway Internet Services 616.774.3131 _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Now you've got me utterly confused ... So, in layman's terms, if I connect a T100P to a circuit provided by the Telco, and the Telco says that they will provide timing, I have to put WHAT? span=1,0,0,esf,b8zs,yellow this means '0' this span is not a sync source, i.e. the Telco will provide my 8kHz. Could one use '2' with impunity (span=1,2,0,...)? I am still not clear under which circumstances one should use '0' versus '2'. WW ----- Original Message Follows -----> Holy crap people, trim your replies! > > > You didn't say what's at the other end of your PRI line, > > but you might try having the other end be the timing > > sync source. Try: span=1,0,0,esf,b8zs instead. Maybe > that will help. > > We need to get this documented *clearly* once and for all. > > Zaptel T1/E1 hardware either free-runs to its own internal > 8kHz time source, or it tries to lock to the recovered > clock from the line. > > Zapata.conf says that timing of 0 means "do not use this > span for timing." Zero does not mean "slave timing", it > means not to use this span as a recovered clock source > for timing at all. Timing values of 1 or 2 mean try to > lock the internal clock to the recovered clock from the > span. > > A value of 0 means that this span's recovered clock never > gets used as a timing source. A value of 1 means that > this span is the primary clock source -- If the span is > up, try to lock the internal clock to the clock recovered > from this span. A value of 2 means to use this span for > timing only if the primary span is down. > > To reiterate: a value of 0 means that the other end must > be locking to the zaptel's clock or else clock slips will > occur. > > Feel free to correct me if I'm wrong, but I am pretty sure > I have this right. :-) > > Regards, > Andrew > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-usersWilly Wouters ypOne Publishing
In laymans terms. To use your telco's T-1 as the timing source .... span=1,1,0,esf,b8zs,yelllow To use the internal clock of the card you would use (I'm pretty sure that this would only be used for channel banks, or connections to other PBX hardware. I don't think a telco is going to use your PBX as a timing source) span=1,0.0,esf,b8zs,yellow If you have multiple telco connections on multiple spans you would have something like this span=1,2,0,esf,b8zs,yellow (secondary time source) span=2,1,0,esf,b8zs,yellow (primary time source) span=3,0,0,esf,b8zs,yellow (provide the time source, i.e. channel bank) -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of willy@yponeinc.com Sent: Monday, April 12, 2004 9:39 PM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] T100P / ZAP / PRI errors Now you've got me utterly confused ... So, in layman's terms, if I connect a T100P to a circuit provided by the Telco, and the Telco says that they will provide timing, I have to put WHAT? span=1,0,0,esf,b8zs,yellow this means '0' this span is not a sync source, i.e. the Telco will provide my 8kHz. Could one use '2' with impunity (span=1,2,0,...)? I am still not clear under which circumstances one should use '0' versus '2'. WW ----- Original Message Follows -----> Holy crap people, trim your replies! > > > You didn't say what's at the other end of your PRI line, > > but you might try having the other end be the timing > > sync source. Try: span=1,0,0,esf,b8zs instead. Maybe > that will help. > > We need to get this documented *clearly* once and for all. > > Zaptel T1/E1 hardware either free-runs to its own internal > 8kHz time source, or it tries to lock to the recovered > clock from the line. > > Zapata.conf says that timing of 0 means "do not use this > span for timing." Zero does not mean "slave timing", it > means not to use this span as a recovered clock source > for timing at all. Timing values of 1 or 2 mean try to > lock the internal clock to the recovered clock from the > span. > > A value of 0 means that this span's recovered clock never > gets used as a timing source. A value of 1 means that > this span is the primary clock source -- If the span is > up, try to lock the internal clock to the clock recovered > from this span. A value of 2 means to use this span for > timing only if the primary span is down. > > To reiterate: a value of 0 means that the other end must > be locking to the zaptel's clock or else clock slips will > occur. > > Feel free to correct me if I'm wrong, but I am pretty sure > I have this right. :-) > > Regards, > Andrew > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-usersWilly Wouters ypOne Publishing _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
That would be a valid configuration, and yes yellow is an option for setting a yellow alarm when no channels are open. -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Scott Stingel Sent: Tuesday, April 13, 2004 10:57 AM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] T100P / ZAP / PRI errors That makes sense. I've always found the following wording (from the sample file) confusing, not clear about whether "this" and "this span" referred to the span connection on the card, or the span itself: # The timing parameter determines the selection of primary, secondary, and # so on sync sources. If this span should be considered a primary sync # source, then give it a value of "1". For a secondary, use "2", and so on. # To not use this as a sync source, just use "0" So just to clarify some more, I assume if you're using a 4-span card like a TE410P, you would have something like this (in a T1 environment with all connected to a telco switch): span=1,1,0,esf,b8zs,yellow (primary time source) span=2,2,0,esf,b8zs,yellow (secondary time source) span=3,0,0,esf,b8zs,yellow span=4,0,0,esf,b8zs,yellow Do you agree with this? (the "yellow" is an optional parameter) Cheers Scott Stingel www.evtmedia.com -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Bisker, Scott (7805) Sent: Tuesday, April 13, 2004 4:59 AM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] T100P / ZAP / PRI errors In laymans terms. To use your telco's T-1 as the timing source .... span=1,1,0,esf,b8zs,yelllow To use the internal clock of the card you would use (I'm pretty sure that this would only be used for channel banks, or connections to other PBX hardware. I don't think a telco is going to use your PBX as a timing source) span=1,0.0,esf,b8zs,yellow If you have multiple telco connections on multiple spans you would have something like this span=1,2,0,esf,b8zs,yellow (secondary time source) span=2,1,0,esf,b8zs,yellow (primary time source) span=3,0,0,esf,b8zs,yellow (provide the time source, i.e. channel bank) -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of willy@yponeinc.com Sent: Monday, April 12, 2004 9:39 PM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] T100P / ZAP / PRI errors Now you've got me utterly confused ... So, in layman's terms, if I connect a T100P to a circuit provided by the Telco, and the Telco says that they will provide timing, I have to put WHAT? span=1,0,0,esf,b8zs,yellow this means '0' this span is not a sync source, i.e. the Telco will provide my 8kHz. Could one use '2' with impunity (span=1,2,0,...)? I am still not clear under which circumstances one should use '0' versus '2'. WW ----- Original Message Follows -----> Holy crap people, trim your replies! > > > You didn't say what's at the other end of your PRI line, but you > > might try having the other end be the timing sync source. Try: > > span=1,0,0,esf,b8zs instead. Maybe > that will help. > > We need to get this documented *clearly* once and for all. > > Zaptel T1/E1 hardware either free-runs to its own internal 8kHz time > source, or it tries to lock to the recovered clock from the line. > > Zapata.conf says that timing of 0 means "do not use this span for > timing." Zero does not mean "slave timing", it means not to use this > span as a recovered clock source for timing at all. Timing values of > 1 or 2 mean try to lock the internal clock to the recovered clock > from the span. > > A value of 0 means that this span's recovered clock never gets used as > a timing source. A value of 1 means that this span is the primary > clock source -- If the span is up, try to lock the internal clock to > the clock recovered from this span. A value of 2 means to use this > span for timing only if the primary span is down. > > To reiterate: a value of 0 means that the other end must be locking to > the zaptel's clock or else clock slips will occur. > > Feel free to correct me if I'm wrong, but I am pretty sure I have this > right. :-) > > Regards, > Andrew > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-usersWilly Wouters ypOne Publishing _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users