RE: [Asterisk-Users] T100P No D-channels

2004-09-02 Thread Pliva, Josef
Thanks gentlemen for all your help and suggestions; 

For some reason, this setup of ours started to work perfectly again this
morning and is still up without any of the symptoms and failures I
described. We'll have to figure this out with our telco rep - I am certain
this problem has not gone away...just like tech stocks, it just gave us a
reprieve for a short while :(

Regards
Josef


-Original Message-
From: Eric Wieling [mailto:[EMAIL PROTECTED]
Sent: August 31, 2004 5:27 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] T100P No D-channels


On Tue, 2004-08-31 at 15:58, Pliva, Josef wrote:
> Unfortunately, I am seeing great many missed IRQs continually...if in fact
> it is that which causes the loss of D-channel.

Then you need to find out why interrupts are being locked for long
enough to make the T100P miss interrupts.  Common causes: frame buffer,
graphics, RAID drivers, IDE DMA, and many, many other things.  Doing an
hdparm -u1 /dev/hda might help



-- 
  Eric Wieling * BTEL Consulting * 504-899-1387 x2111
"In a related story, the IRS has recently ruled that the cost of Windows
upgrades can NOT be deducted as a gambling loss."

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
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
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


RE: [Asterisk-Users] T100P No D-channels

2004-08-31 Thread Eric Wieling
On Tue, 2004-08-31 at 15:58, Pliva, Josef wrote:
> Unfortunately, I am seeing great many missed IRQs continually...if in fact
> it is that which causes the loss of D-channel.

Then you need to find out why interrupts are being locked for long
enough to make the T100P miss interrupts.  Common causes: frame buffer,
graphics, RAID drivers, IDE DMA, and many, many other things.  Doing an
hdparm -u1 /dev/hda might help



-- 
  Eric Wieling * BTEL Consulting * 504-899-1387 x2111
"In a related story, the IRS has recently ruled that the cost of Windows
upgrades can NOT be deducted as a gambling loss."

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] T100P No D-channels

2004-08-31 Thread Chris Shaw
H I guess from a troubleshooting standpoint to try and pinpoint the
problem what I would do is remove all cards from the system and then only
replace the cards that are absolutely necessary like your SCSI card and your
Video card and of course the T100P and then check /proc/interrupts to see if
you're having any more MISses... Also are you getting interrupt ERRs as
well?

Is APIC enabled for your board? If it is, you'll see things like
IO-APIC-edge or IO-APIC-level in your /proc/interrupts. If not, you'll see
XT-PIC for all interrupts... If you can't get APIC turned on you might try
upgrading your kernel, your motherboard/bios may be blacklisted in that
particular kernel...

You definitely DO NOT want to share interrupts on the T100P unless it's a
low-interrupt device like a USB controller or your video card. You
definitely don't want to share with say a NIC or a SCSI controller... If it
is sharing with one of those, try shuffling the cards around in different
slots and make sure that your T100P isn't in slot 5. Slot 5 is usually
shared with Slot 1 if they're on the same bus...

Of course you've probably already tried all of this but just in case you
haven't...

-Chris

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


RE: [Asterisk-Users] T100P No D-channels

2004-08-31 Thread Pliva, Josef
Hi Chris, 
thanks for taking time to look this over.

T100P/* is connected to the Mitel IP-PBX/CU and it to telco - so I think our
setting is correct. 
BTW, I did try 0 (as well as 2) without success, just for "fun", before I
came on a good explanation 
of the sync source in this forum.

Unfortunately, I am seeing great many missed IRQs continually...if in fact
it is that which causes the loss of D-channel.

Regards
Josef


-Original Message-
From: Chris Shaw [mailto:[EMAIL PROTECTED]
Sent: August 31, 2004 4:46 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] T100P No D-channels


> Zaptel.conf sets t100p to be the primary sync source for the only span, as
> suggested by many Asterisk users.

I'm trying to understand so please bear with me... The T100P is connected
directly to the Mitel? Or to the Telco through a T1?

What I mean is are calls coming into the Mitel from the telco and then from
there going into * or are calls going into * first and then being fed into
the Mitel?

If your T100P is connected to the telco then the clocking source should be
the telco as their clocks are going to be a LOT more accurate than your PC's
interrupt timers...

If your T100P is connected to the Mitel, then you've got it right... Just
checking, I wasn't sure from your description...

Occasional interrupt misses are pretty normal although in a perfect world
with a good mobo they should not happen at all... If you're seeing multiple
misses per second (e.g. everytime you do cat /proc/interrupts you see more)
then there's a problem...

-Chris

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
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
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] T100P No D-channels

2004-08-31 Thread Chris Shaw
> Zaptel.conf sets t100p to be the primary sync source for the only span, as
> suggested by many Asterisk users.

I'm trying to understand so please bear with me... The T100P is connected
directly to the Mitel? Or to the Telco through a T1?

What I mean is are calls coming into the Mitel from the telco and then from
there going into * or are calls going into * first and then being fed into
the Mitel?

If your T100P is connected to the telco then the clocking source should be
the telco as their clocks are going to be a LOT more accurate than your PC's
interrupt timers...

If your T100P is connected to the Mitel, then you've got it right... Just
checking, I wasn't sure from your description...

Occasional interrupt misses are pretty normal although in a perfect world
with a good mobo they should not happen at all... If you're seeing multiple
misses per second (e.g. everytime you do cat /proc/interrupts you see more)
then there's a problem...

-Chris

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] T100P No D-channels

2004-08-31 Thread Pliva, Josef
Hi
Last week I installed Asterisk (release1) with digium t100p single span T1
(wct1xxp) board on Dell GX270 pc configured for PRI. Asterisk/t100p is
currently the only user of the t1 line. All worked well for about a half a
day, PSTN to SIP phones to non-SIP IP phones etc. Alas, since then I
consistently get multitudes of blue alarms on all b-channels followed by a
loss of d-channel:

Aug 31 16:33:49 WARNING[98316]: chan_zap.c:5286 handle_init_event:
Detected alarm on channel 1: Blue Alarm
Aug 31 16:33:49 WARNING[98316]: chan_zap.c:5286 handle_init_event:
Detected alarm on channel 2: Blue Alarm

...etc, intermixed with 

Aug 31 16:33:49 NOTICE[90123]: chan_zap.c:6920 pri_dchannel: PRI got
event: 4 on Primary D-channel of span 1
Aug 31 16:33:49 WARNING[90123]: chan_zap.c:1899 pri_find_dchan: No
D-channels available!  Using Primary on channel anyway 24!
...and back to reset
Aug 31 16:33:54 NOTICE[98316]: chan_zap.c:5281 handle_init_event:
Alarm cleared on channel 1...
...
Aug 31 16:33:54 NOTICE[90123]: chan_zap.c:6920 pri_dchannel: PRI got
event: 5 on Primary D-channel of span 1
...

I found a few hits on VoIP.org and asterisk user forums usually mentioning
PCI/BIOS IRQ sharing/conflict, but although I certainly see IRQ misses in
zttool as well as /proc/zaptel/1, I cannot "see" any conflicts -  zttool
shows blue alarm, recovery and increasing IRQ misses right after
zaptel/wct1xxp modprobe and ztcfg. During this search-for-the-truth I
disabled all legacy devices (IRQs) I dared, including USB, but to no avail.
On Dell GX270, BIOS does not seem to present the option of PCI IRQ line
sharing/selection - just a disable/enable option.

Mitel 3300 CU (part of 3300 IP-PBX) is set as pri_CPE and * t100p is
pri_NET, using esf framing and b8zs code. Wildcard T100P shows green light,
our 3300 Mitel CU light on the port I use ranges from yellow (during event
recovery) to green (cleared). The telco rep sees nothing wrong with the
Mitel - but did reset it several times since this problem started to happen,
just to appease me.
Zaptel.conf sets t100p to be the primary sync source for the only span, as
suggested by many Asterisk users.

No changes to Asterisk/Zaptel code has been done since the initial build
from the Rel1 FTP site. 

After spending several days searching on internet, I found a lot of
discussion about Digium PRI support which was not totally encouraging.
However I am certain it is something simple since I am totally new to
Asterisk environment and suspect I am missing something somewhere :(

I would welcome any suggestions you may have.


Thanks in advance
Regards
Josef





[EMAIL PROTECTED] proc]# cat interrupts
   CPU0
  0:6640846 XT-PIC  timer
  1:196 XT-PIC  keyboard
  2:  0 XT-PIC  cascade
  8:  1 XT-PIC  rtc
  9:  43296 XT-PIC  eth0
 10:   12708545 XT-PIC  t1xxp
 12:   1422 XT-PIC  PS/2 Mouse
 14:  84025 XT-PIC  ide0
 15: 256596 XT-PIC  ide1
NMI:  0
ERR:  1



[EMAIL PROTECTED] proc]# cat pci
PCI devices found:
  Bus  0, device   0, function  0:
Host bridge: PCI device 8086:2570 (Intel Corp.) (rev 2).
  Prefetchable 32 bit memory at 0xe800 [0xefff].
  Bus  0, device   1, function  0:
PCI bridge: PCI device 8086:2571 (Intel Corp.) (rev 2).
  Master Capable.  Latency=64.  Min Gnt=8.
  Bus  0, device  30, function  0:
PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 194).
  Master Capable.  No bursts.  Min Gnt=2.
  Bus  0, device  31, function  0:
ISA bridge: PCI device 8086:24d0 (Intel Corp.) (rev 2).
  Bus  0, device  31, function  1:
IDE interface: PCI device 8086:24db (Intel Corp.) (rev 2).
  IRQ 9.
  I/O at 0x1f0 [0x1f7].
  I/O at 0x3f6 [0x3f6].
  I/O at 0x170 [0x177].
  I/O at 0x376 [0x376].
  I/O at 0xffa0 [0xffaf].
  Non-prefetchable 32 bit memory at 0xfebffc00 [0xfebf].
  Bus  0, device  31, function  2:
IDE interface: PCI device 8086:24d1 (Intel Corp.) (rev 2).
  IRQ 9.
  I/O at 0xfe00 [0xfe07].
  I/O at 0xfe10 [0xfe13].
  I/O at 0xfe20 [0xfe27].
  I/O at 0xfe30 [0xfe33].
  I/O at 0xfea0 [0xfeaf].
  Bus  0, device  31, function  3:
SMBus: PCI device 8086:24d3 (Intel Corp.) (rev 2).
  IRQ 5.
  I/O at 0xefe0 [0xefff].
  Bus  1, device   0, function  0:
VGA compatible controller: PCI device 10de:0181 (nVidia Corporation)
(rev 162).
  IRQ 11.
  Master Capable.  Latency=64.  Min Gnt=5.Max Lat=1.
  Non-prefetchable 32 bit memory at 0xfd00 [0xfdff].
  Prefetchable 32 bit memory at 0xf000 [0xf7ff].
  Bus  2, device  10, function  0:
Network controller: Tiger Jet Network Inc. Model 300 128k (rev 0).
  IRQ 10.
  Master