SOLVED IncrediblePBX 2020 with TDM800P (was IncrediblePBX 2021 with TDM800P)

[faixbp]

I'd like to upgrade to IncrediblePBX 2021 from IncrediblePBX 2020, however I'm using a Digium TDM800P analog card for FXO and FXS ports.

Is the TDM800P supported on IncrediblePBX 2021 for Debian 10?

To get it to work with IncrediblePBX 2020 required surgery on IncrediblePBX2020.sh (replacing dahdi-linux-complete v2.11.1 with v2.8.0).

Thanks.

--faixbp

 

[hawk#1]

I do not use the outdated cards, and I doubt that Ward is going to start adding support for outdated hardware. You can always try a backup of current system, restore to a temp system, then update it to IncrediblePBX 2021 for Debian 10 and see if it still works. Then you will know if it works or not.

 

[kenn10]

The biggest problem with using analog cards is the version of Dahdi and the drivers needed for the card. Most people have moved to a small channel bank to feed the analog lines into and have them come out as SIP trunks to the PBX. Check out the Grandstream GW4108 which will accept 8 telephone lines and interface them with your pbx.

GXW4104/GXW4108 | Grandstream Networks

The GXW4104/GXW4108 FXO gateways enables businesses of all sizes to create and deploy a VoIP and analog hybrid solution.

www.grandstream.com

 

[dicko]

In 2022 it would be appropriate to look at the energy cost of running any computer with a PCI slot of any flavor 24/7. Almost certainly a PSTN gateway/ATA for "copper" trunks paired with cloud/Raspberry will be a huge money saver in your first year.

(Get your calculator out . . .)

 

[faixbp]

OK, I've given up on upgrading to IncrediblePBX2021--this is about my IncrediblePBX2020 system...

My PBX is built in a mini-PCI system which burns about 40W, but I get your point. I've looked at analog gateways, and those with 4 FXS and 4 FXO ports and good echo cancellation are pricey.

For the past two years, I've been running IncrediblePBX2020 and the TDM800P analog telephony card with the fix that Andy suggested (editing IncrediblePBX2020.sh to replace dahdi-linux-complete v2.11.1 with v2.8.0).

However the Centos7 OS hasn't been updated since then. I just ran yum check-update, and there are about 240 updates listed (see attached)

I know that if I install *all* the updates (yum update), DAHDI will stop working, because I tried doing that and had to roll back the sustem to the Clonezilla backup I made.

I imagine that one of the problems with doing the full Centos7 update is that the kernel gets updated from 3.10.0-1160.25.1.el7.x86_64 to 3.10.0-1160.62.1.el7.x86_64, and the DAHDI modules aren't carried forward to /lib/modules.

Question: which of these Centos7 updates can I install without interfering with DAHDI?

Or is there a DAHDI workaround? I tried copying the dahdi modules directory from the old module directory /lib/modules/3.10.0-1160.25.1.el7.x86_64 to the new one, but that didn't help.

Thanks!

--faixbp

 

[faixbp]

Well, I think I've solved the problem: I changed the grub2 boot selection to the 3.10.0-1160.25.1.el7.x86_64 kernel.

I had to implement the knockd fix per https://www.voip-info.org/forum/threads/port-knocker-not-starting.25381/#post-155200.

If I find any problems, I'll let you know.

--faixbp