I recently upgraded from FreePBX 16 to 17, and I installed dahdi, but it does not show my Rhino FXO/FXS Card.
It is detected as hardware it I run sudo dahdi_hardware, but will not show in the gui.
The card was fully working with FreePBX 16
It’s been 8 days.
What did you find out?
I haven’t made it anywhere on my own, and no one on here has been of any help.
What card are you trying to use?
Many cards have been recently deprecated in the version of dahdi software that Sangoma ships with FreePBX17
You might probably need to manually compile dahdi in order to restore functionality
Thanks for the reply.
What are you going to do now? attempt a DAHDI compile or switch to an IP gateway product?
I realize this may not be a “FreePBX” problem and possibly an upstream DAHDI problem.
I don’t get the mentality of dropping functionality for hardware that’s out there and many people are still using and selling. “Just because it’s old” or whatever and it had been working just fine.
I could see this point if it were a buggy problematic piece of hardware, but not if it works just fine.
What’s the point of even keeping DAHDI when the whole point of DAHDI itself is to work with this “old” stuff or “old way of doing things” in the first place?
It is a R24FXX-EC Rhino Fxo/FXS card.
I have no knowledge on configuring dahdi manually, and I would appreciate any assistance if it is because the card is too old.
I’m not help as I do not have such a card to test here.
There’s some out there for sale used. One on eBay but $199
Might be able to offer $50 can’t hurt.
I also do not have any experience in doing this but could probably figure it out if I had a card.
I was hoping somebody here could help or point you to the instructions to build DAHDI for it
And make it work on '17.
That will of course put your PBX in a state where you can’t run Debian updates without it breaking DAHDI. (which is usually OK) once it’s working and if you do not have it exposed to the Internet.
Your call here on that.
I do not understand the mentality of removing support for working hardware that people still use.
It’s a freaking analog Interface.
Why is FreePBX even supporting DAHDI and analog with this mentality?
Analog FXO and FSX are “old” why is it supported?
Why kill hardware that works just fine for old stuff?
Do you know what the cost of an even moderately new FXO/FXS gateway is?
I just posted about this here:
How to define a pj_sip trunk to a Cisco ISR4321 - FreePBX / Endpoints - FreePBX Community Forums
You don’t need CUBE licensing. In fact you don’t even need an ISR4321 a ISR2800 will do.
Put ISR4321 4FXO into Ebay and you will get dozens of the following for under $100 such as this one:
Cisco ISR 4321 Gigabit Integrated Service Router IPBase 1xNIM-4FXO ISR4321/K9 #2 | eBay
You can get 2 of them one as a spare.
They are tanks and will run forever no matter how many updates to FreePBX and Debian you do.
And best of all that let’s you virtualize FreePBX on HyperV or KVM/QEMU or ESXi whatever your preferred hypervisor is.
This is truly one of the biggest reasons to go to an external gateway is it uncouples the dependency from specific hardware and operating system to FreePBX.
And if you want to know I am also very sympathetic to orphaned hardware. But the idea of plugging a phone line into a card that plugs into the server you’re running your PBX on is just faulty. Server hardware changes faster than most people change their underwear and it makes the one thing more complex which is a hinderance to troubleshooting.
I currently have a 24 port card, and I am actively using 15. I do not want to spend a few hundreds of dollars on a new card that will automatically work with FreePBX.
If anyone knows how to manually configure it, I would appreciate it.
You need to find out if your specific model has been deprecated. If so, you will need to edit DAHDI source files to re-include your specific model and manually compile DAHDI.
There are examples of this for other popular models that have also been deprecated, for example the Digium TDM410. You could use those examples as a guide.
If all else fails you could try this:
I have a raspberry pi5 with dahdi working on freepbx17, installed ass-backwards.
I used phreakscript to reinstall asterisk22, including dahdi after a regular freepbx17 install. It also can optionally install the"legacy" drivers purged by Sangoma.
The “dahdi channel DID” module is also now missing. I added the relevant info manually.
And had to set the default SR on conference calls to 8KHz to keep my PRI card clocking.
There is a whole world outside cubicle-land where the simplicity and robustness of POT technology is preferable; it shouldn’t be allowed to die.
And it isn’t - go to Ebay and for under $100 you can pick up a Cisco ISR4321 outfitted with FXO cards and have yourself a rock-solid POTS-to-SIP gateway.
The PBX software does not need to be conflated with the POTS connection hardware.
You can also build yourself a DAHDI with an antique POTS card in some old PC you rescued from the Dumpster, run an antique version of Asterisk on that, setup an inter-pbx trunk between that and the modern PBX - if you want to use the old pots card you still have in your scrap bin.