Asterisk PBX Asterisk is a full-featured, open source PBX system. 1.1 My talk on Fun with Asterisk and Perl See [Talk - Fun with Asterisk and Perl]. 1.1 My Asterisk RPMS You can download my RPMs for Red Hat Linux 9 from the {link:community download area for Asterisk|http://community.moertel.com/asterisk/}. ~~These RPMs are now outdated.~~ Luckily, there is now a stable branch for Asterisk development, and other folks are making RPMs available. See {link:Asterisk RPM|http://www.voip-info.org/tiki-index.php?page=Asterisk%20RPM} on {link:voip-info.org|http://www.voip-info.org/}. 1.1 Troubleshooting Here are some problems that I am working on. 1.1.1 NMI issues w/ Wildcard X100P cards Something funny is going on when Asterisk loads the wcfxo driver: {code:none} ... Zapata Telephony Interface Registered on major 196 Uhhuh. NMI received. Dazed and confused, but trying to continue You probably have a hardware problem with your RAM chips wcfxo: DAA mode is 'FCC' Found a Wildcard FXO: Wildcard X101P Registered tone zone 0 (United States / North America) ... {code} Note the "Dazed and confused" part. This is with the normal SMP kernel and SMP-build Zaptel driver. On the suggestion from folks from Digium, I tried building a non-SMP driver and using it under a non-SMP kernel (Linux version 2.4.20-20.9 (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Mon Aug 18 11:45:58 EDT 2003). The results of __modprobe wcfxo__ under this kernel/driver combo: {code:none} ... Zapata Telephony Interface Registered on major 196 PCI: Assigned IRQ 10 for device 00:04.0 Uhhuh. NMI received. Dazed and confused, but trying to continue You probably have a hardware problem with your RAM chips wcfxo: DAA mode is 'FCC' Found a Wildcard FXO: Wildcard X101P Registered tone zone 0 (United States / North America) ... {code} Note that bit about "PCI: Assigned IRQ 10". What else is on 10? Well, __cat /proc/interrupts__ says: {code:none} CPU0 0: 35874 XT-PIC timer 1: 4 XT-PIC keyboard 2: 0 XT-PIC cascade 3: 0 XT-PIC usb-ohci 5: 7 XT-PIC advansys 8: 1 XT-PIC rtc 10: 200367 XT-PIC 3ware Storage Controller, wcfxo 11: 1713 XT-PIC ioc0, eth0 12: 41 XT-PIC PS/2 Mouse 14: 14 XT-PIC ide0 15: 26 XT-PIC ide1 NMI: 1 ERR: 0 {code} Hmmm... I don't like that the wcfxo driver is sharing an interrupt w/ the 3ware RAID controller. Similarly, and more concerning, my server (a Dell PowerEdge 1600SC (ServerWorks chipset)) locked up w/ a kernel oops. While none of the oops diagnostics managed to make it to the logs, I was able to take a {link:photograph of the oops output|http://community.moertel.com/ss/space/Asterisk+PBX/wcfxo-oops.png}. 1.1 Links - {link:Asterisk|http://www.asterisk.org/} is the project home page - {link:Digium|http://www.digium.com/} supports Asterisk development, sells telephony hardware, provides professional Asterisk support 2004-04-06 12:55:03.947 2003-11-18 16:35:08.512 Thu Mar 18 20:37:57 EST 2004