What your problem sounds like is some conflict on the hardware level, perhaps with interrupt handling or buffering. The zaptel cards generate a lot of interrupts for timing purposes, so perhaps your motherboard can't cope?
I suppose it's possible that you got a bad zap card, but I'd call that the rarest of the various potential causes.
If it's any help, I have an older Dell 500MHz system (upgraded to 1GHz) here with 256MB of RAM, one IDE drive, one DVD-ROM, and a X100P and TDM400P with one FXS. The system has been up for 40+ days without issue.
On Oct 12, 2004, at 11:23 AM, Michael Loftis wrote:
Yup it's official, the box is now a brick thanks to the zaptel drivers. What madness they're doing I have no idea, but the filesystems are all pretty much corrupted, with the drives being totally fine, both sides of the mirrored set which pretty much rules out the drives themselves.
Pending any other findings I'm inclined to warn people away from atleast my specific hardware combination and the Zaptel 1.0 drivers with 2.4.25 and ext3.
Kernel runs fine on everything here in the shop, atleast 15 other machines, most of them pretty heavily worked, some IDE, some SCSI.
I'm going to give it another try on this new hardware, but if that nosedives again then I'm not sure what to do, I do not have time to fix Digiums hardware for them, nor the drivers.
_______________________________________________
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
