On Wed, 22 Sep 2004 10:13:58 -0500, Bob Klepfer <[EMAIL PROTECTED]> wrote:
>
> 3) It could be the motherboard. We're on the cheap here and used
> available components to make our server...worked fine with two x100's,
> then the boss wanted another line. Once I got the damn thing to accept
> them
--- Brent Franks <[EMAIL PROTECTED]> wrote:
>
> Hi Mark,
>
> We had a similar issue about a year ago. We eventually
> figured out that
> our Promise Array (ATA RAID) Controller cards were
> causing the X100P
> card to go into RedAlarm. It would come out on its own
> sometimes,
> others not.
3) It could be the motherboard. We're on the cheap here and used
available components to make our server...worked fine with two x100's,
then the boss wanted another line. Once I got the damn thing to accept
them all on different IRQs, two would red alarm nearly every night at
random times. C
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:asterisk-users-
> [EMAIL PROTECTED] On Behalf Of Mark C. Thomas
> Subject: Re: [Asterisk-Users] Red Alarm on X100P
>
> I haven't tried disconnecting the phone line, I'll try that
> next time.
> If it
I haven't tried disconnecting the phone line, I'll try that
next time.
If it was a co problem, I wouldn't think reloading the
wcfxo module would have fixed it - or would it?
Thanks for the info...
--- Lyle Giese <[EMAIL PROTECTED]> wrote:
> 1) it could be the x100p. Have you tried merely
> di
1) it could be the x100p. Have you tried merely disconnecting the phone
line and plugging it back in?
2) it could be the phone line connected to the x100p. A red alarm is an
indicator of the co talk battery is missing on the line jack.
Lyle
- Original Message -
From: "Mark C. Thomas" <
