Hi Mark, Yes. It is indeed the Dell PowerEdge Server at the colo facility. I took another shot at it before completely giving up. After having eliminated most everything else, it came down to hardware. That's when I started exploring other, less obvious and arguably less likely solutions. The disabling of ACPI was nothing more than a guess in a list of things I began to try, one at a time. I can't explain how ACPI would interfere with zaptel but it does, at least on my server. Pretty strange. I'm just glad I figured it out and it's working now! --- Rob Pectol - AH2S AllStar Node 2147 On 2014-04-27 18:20, Mark Guibord wrote:

Hi Rob,

I take it you are talking about your Dell 64 bit machine at the colocation right? If so congratulations, I'm amazed that the Advanced Configuration and Power Interface (ACPI) would interfere with the Zaptel driver.

Mark - K7IZA

-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of AH2S Sent: Saturday, April 26, 2014 10:25 PM To: App_rpt Users Subject: [App_rpt-users] this may help others with zaptel issues on some hardware

In case there are others that have come across issues getting an ACID server up and running where the zaptel driver is misbehaving, this one little gem of info might make all the difference in the world! I had previously tried everything I could think of, including a dozen different kernels and associated build environments, each time recompiling Asterisk and associated drivers (zaptel being one of them, of course). But nothing worked. The zaptel driver refused to function even though it appeared to load up just fine. I just couldn't get it to work no matter what I did. In frustration I put it aside for a few weeks. Well, I just recently got back to it but this time I found success! Here's my solution:

Disable acpi at boot up. You can do this by appending, "acpi=off" to the kernel boot parameters in the grub boot loader. For example on my CentOS 5.1 system I modified the /boot/grub/menu.lst entry for my kernel boot parameters as follows:

kernel /boot/vmlinuz-2.6.18-348.12.1.el5PAE ro root=LABEL=/ acpi=off

Save the file and reboot. This one little thing made the difference between having a useless ACID install on hardware at a colocation facility 8,000 miles away, to a fully functional AllStar Server handling several remote RTCMs! I had all but given up hope on getting the zaptel driver to work properly on this hardware until I tried this on a whim! Since I haven't seen this info posted anywhere yet, I thought I'd offer it up to the group in the hopes that it might help someone else.

-- Rob Pectol - AH2S AllStar Node 2147

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.