You need to get rid of zaptel and the zaptel config file in /etc/asterisk and add

chan_dahdi.conf    with the following -


[channels]
signalling=em_txrx
group=9
channel=pseudo

;
; End of file
;


73 Doug
WA3DSP
http://www.crompton.com/hamradio




Date: Tue, 27 Jan 2015 15:18:09 -0500
From: szingman@msgstor.com
To: Bryan@bryanfields.net; app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] compile on Debian

From what I see in chan_dahdi.c zapata.conf is replaced by chan_dahdi.conf
 
On 1/27/2015 3:07 PM, Bryan Fields wrote:
My understanding is that Dahdi replaces zaptel on the new kernels.  If you read the docs on Dahdi it says to remove all zaptel stuff.

On 1/27/15, 2:50 PM, Steve Zingman wrote:
I would put the files in anyway. Zaptel or not unless there is a dahdi version the kernel module may still be looking for the file.

On 1/27/2015 2:35 PM, Bryan Fields wrote:
No, this is a 3.2 kernel (needed it for the server) so it's dahdi, my old box is running the old stable debian, and its the zaptel drivers which work.

I'll update in a few once I get in front of a pc

On January 27, 2015 2:19:24 PM EST, Steve Zingman <szingman@msgstor.com> wrote:
The node I am running a PCI card is still Squeeze, so it's zaptel but,
Are the config files for the PCI card installed?
zapata.conf in /etc/asterisk
zaptel.conf in /etc

also try to add  "options pciradio debug=1" in /etc/modprobe.conf

longshot, but worth asking.

Steve

On 1/27/2015 2:08 PM, Bryan Fields wrote:
Pciradio. I am going to write a longer bug report once I pull it into gdb later today

On January 27, 2015 2:00:59 PM EST, Steve Zingman <szingman@msgstor.com> wrote:
Bryan,
Do you get the crash when you start dahdi or when you modprobe pciradio?

Steve

On 1/27/2015 9:51 AM, app_rpt-users-request@ohnosec.org wrote:
Message: 2 Date: Tue, 27 Jan 2015 03:38:27 -0500 From: Bryan Fields<Bryan@bryanfields.net> To:"app_rpt-users@ohnosec.org" <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] compile on debian (was More than 4 nodes on a PC) Message-ID:<54C74E83.60203@bryanfields.net> Content-Type: text/plain; charset=ISO-8859-1 On 1/27/15, 1:04 AM, Doug Crompton wrote:
Bryan, Yes you will need Dahdi source. You need to remove Zaptel stuff. I would suggest getting it from the BBB image at hamvoip.org. It already has the Allstar patches in it. It is located in /usr/src/utils/dahdi-linux-complete-2.9.1.1+2.9.1 If not you need to download that version of the code from Digium and apply the patches from the Allstar svn site.
I've got Dahdi from Digium (dahdi-linux-complete-2.10.0.1+2.10.0.1) and applied the patches from ohnosec svn. hunk 3 on patch 2 needed to be applied by hand, the rest went fine. Dahdi is compiled and installed. I have the ohnosec svn asterisk compiled as well. Copied the sounds in place and started to configure asterisk. I've run into a bit of a problem while loading the pciradio module however. I don't know enough about kernel coding in linux to know where to begin debugging this. does your version of dahdi on the hamvoip.org site work ok? perhaps it's new bug in the Digium code, and I should go with yours in place of it.

--
Bryan Fields
727-409-1194
http://bryanfields.net

-- 
"Anything is possible if you don't know what you are talking about."
1st Law of Logic 

--
Bryan Fields
727-409-1194
http://bryanfields.net

-- 
"Anything is possible if you don't know what you are talking about."
1st Law of Logic 


-- 
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

-- 
"Anything is possible if you don't know what you are talking about."
1st Law of Logic 

_______________________________________________ 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.