Found the problem. Debian 10 splits up the kernel headers into two packages, linux-headers-4.19.0-20-amd64 and linux-headers-4.19.0-20-common. Solution is to create /usr/src/linux-headers and copy both directories to one
The Makefile in linux-headers-4.19.0-20-amd64 tries to accommodate the two directories with:
Note that the --with-linux directory /usr/src/linux-headers is the combination of the two debian headers packages, linux-headers-4.19.0-20-amd64 and linux-headers-4.19.0-20-common. This was required to compile the TDM driver.
Having overcome the compiler issues, we find that although “dahdi show channels” looks good with 48 digital and 4 analog lines, calls do not go through. When calling in, fast busy. When calling out, a DAHDI channel attempts the call then falls back to our SIP trunk. I’ve verified permissions on all /dev/dahdi nodes are asterisk.asterisk and match our old installation which uses kernel 4.x
I’ve been doing custom compiles and installation of Sangoma hardware since the mid 2000’s and never seen a condition where “wanrouter status” shows connected and no alarms are set when checked with “wanpipemon -i w1g1 -c Ta”.
Everything looks good otherwise. could the dial error be simply an incompatibility with the kernel?
Good point dicko… there not much to see. Just PRI status code 27 when trying to call out.
It’s been hard to find time but today I referred to this link → PRI- PRI Down - Telephony Cards - Documentation and going through the steps, found the interface RX/TX are not incrementing so I’m guessing there is a hardware incompatibility. The machine is an HP DL360 gen9…
If anyone with Sangoma has some insight, I’d appreciate it.
I would suggest opening a Support ticket with Sangoma as your issue isn’t FreePBX related and normally Sangoma staff here are just FreePBX team members.
Hi Tony, I’ll try but since Sangoma got so big I find tech support through the forum is much easier. I am – was – a reseller but don’t have my records in order when it comes to proving it. We didn’t register them and it’s been over 10 years… I NEVER thought I’d have a problem as a reseller or I would have registered them. My last query to support was not received well and was kicked around for over a year, back and forth with a lot of time wasted and no results. Then, out of the blue, someone posted here about the same issue and it was happily fixed in a couple days. That really left a bad taste in my mouth for contacting support! Times have changed since David Mandelstam answered the tech requests!
dicko, I read that 27 means out of order. The funny thing the line is not busy. It’s in production on an oooold server and when I switch to the new, wanrouter status shows connected, wanpipemon shows no alarms and dahdi show channels show all the channels configured. “pri show spans” shows “PRI span 1/0. Down, Active”. The only indicator that it’s not working is the RX/TX counters on w1g1 are stuck at 0. I’ve tried wanrouter on the host os (both proxmox 6x and 7x) and within the VM - same result on a HP DL360 Gen9.
I’ve verified the configuration works on a supermicro chassis - same host os and using the same VM so I figure it’s a problem in the HP. Maybe a BIOS update is needed or other special configuration. I can’t find anything so far. Monday we’ll try with Sangoma and HP
set pri set debug on . . . for the DAHDI side, you have a problem with your d -channel apparently being ‘down’ in DAHD,I it is very unlike;y to be a hardware problem, more a wanrouter/wanpipe to DAHDI thing , contact Sangoma
I have run myself ragged on this… though the patch I posted works to compile the kernel driver, there’s an issue in the tools so I’m removing it until Sangoma can fix it. The developer has been emailed with the error