DAHDI struggles and getting an analog Sangoma A200 to work

FreePBX Hardware
1

Running PBX 17.0.19.23, Asterisk 21.6.0
Trying to run this on Debian 12 Kernel 6.1.0-27-amd64 because that was the version that is compatible with Dahdi config. It seems when the system first boots my card shows in the web gui. But whenever I try to make a change and then restart DHADI and asterisk it seems to fail and then my cards do not show up in DAHDI configuration analog cards. It also shows that wanpipe is compatible with that Kernel as well but I am having issues. When I manually start wanpipe in the cli I get a kernel error in the message. I want to start over with a fresh load on an older kernel.

I want to start with a fresh PBX install. If I keep all the same hardware but reload the system will I have activation problems? It says not to deactivate if I am using the same hardware but pretty new to this.

2

Hi @jt-tech

Have you tried to check dahdi status at Linux CLI side ? If you not, you can start checks from dmesg and dahdi_hardware side.

Edit: Also have you did upgrade Debian Kernel version after Dahdi Software instalation?

Thanks.

Shahin

3

Hello!

On restart dmesg seems to show normal.
I have wanpipe1: Module 1: FXO Line connected!
module 2 - 8 say FXO Line is disconnected!

EDIT
Locking closer at dmesg there is this line
[ 5.031734] dahdi: Warning: Span WRTDM/0 didn't specify a spantype. Please fix driver!

Would you like the full output?

All accurate for now, I’ll use more of them in prod but we aren’t there yet.

dahdi_hardware result:
pci:0000:04:04.0 wanpipe- 1923:0040 Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card

I installed everything with Kernel 6.1.0-27-amd64 but after having stability issues and when running the dahdi config from command line somewhere in the result of wanpipe it said not compatible with firmware, i’ve since installed and booted with kernel 6.1.0-23-amd64. I can go back to 6.1.0-27-amd64

If I make any changes in the PBX console it DAHDI will not restart and I am not sure how to get it running even with the CLI commands. wanrouter start wanpipe1 fails. I believe if I just run wanrouter restart wanpipe1 it fails as well.

4

I will suggest you if you are changed kernel you have to re-install dahdi driver, Try to remove and re-install dahdi module.

The Run this command

/usr/sbin/wancfg_dahdi

Screenshot 2025-02-07 at 14.50.04

5

OK, I ran /usr/sbin/wancfg_dahdi and followed the prompts.

Dahdi and Wanpipe configuration complete: choose action
 1. Save cfg: Restart Asterisk & Wanpipe now
 2. Save cfg: Restart Asterisk & Wanpipe when convenient
 3. Save cfg: Stop Asterisk & Wanpipe now
 4. Save cfg: Stop Asterisk & Wanpipe when convenient
 5. Save cfg: Save cfg only (Not Recommended!!!)
 6. Do not save cfg: Exit
[1-6]:1
Stopping Asterisk...
Waiting for asterisk to stop when convenient...
Waiting for asterisk to stop when convenient...
Waiting for asterisk to stop when convenient...

It seems that asterisk will not stop or the script does not recognize it as stopped. I did select 1 so it shouldn’t have waited for convenience. There are many more of the waiting for listed and has not proceeded past this.

6

seems to me this is a bug for FreePBX-17. I do have Sangoma TDM card attached at FreePBX-16 with Asterisk 20 is running,
@slobera, do you have any idea for that case… pls?

7

Sorry, just saw this.
Did you install with the --dahdi option ? It should work, do you have a case with us to take a look at your system ?

8

Yes, I installed with the --dahdi option. it does see the card on the first boot and seems to partially work but anytime i restart asterisk or make a change it won’t start again. I do have a case, would you like the #? I haven’t seen action on it for a bit.

9

Yes please, give me the case number so I can take a look.

Thanks =)

10

Of course, right when you asked I did get a message that they are troubleshooting but case: 01799906 - Let me know if you have any questions about the system. Just a fresh load of Debian and followed the install scripts.

Edit - the server is not in production so stop and start items as much as you want.

11

It should be working now @jt-tech
Make some tests, reboot your server, and let me know please =)

Here is what I did:

wanrouter hwprobe --verbose
wancfg_dahdi

At the end, I selected option 3 to stop it.
Then checked if wanrouter.service is enabled (systemctl is-enabled wanrouter.service)

That’s it.

1 Like
12

Does this disable the Dahdi Config menu option in the FreePBX GUI? I don’t see this LINK.

It’s OK if I’m not supposed to use it, I am just not sure what to do next. I have one analog line in port 1 of the Sangoma card. Should I just be able to make a TRUNK now that has a dahdi identifier of g0 in dahdi settings and then use an outbound route that uses that Trunk and I should be able to make a call out? It doesn’t work but I am sure I am missing something.