DAHDI PRI Issues on Rocky Linux 9

Asterisk Asterisk Hardware
1

I have installed the latest, Asterisk 22.4.1 with DAHDI 3.4.0 on Rocky Linux 9.6. I know I’ve had to change my channel format for PJSIP (from chan_sip), but not sure if there is some difference I am not aware of with the new version..

Some details: I have 2 PRIs connected within the same card (Digium TE420 T1 card). One is set to pri_cpe and the other to pri_net.

Ultimately I need to get this to work via AMI. When I try to make the outdial is seems to create the outgoing channel on the CPE side, but the inbound call never seems to come in on the network side. Here is the error following an attempt via AMI, as shown on CLI:

[Jul 16 10:07:28] WARNING[144731][C-00000020]: chan_dahdi.c:5302 dahdi_confmute: DAHDI confmute(0) failed on channel 4: Invalid argument
[Jul 16 10:07:28] WARNING[144732]: chan_dahdi.c:5302 dahdi_confmute: DAHDI confmute(0) failed on channel 4: Invalid argument
[Jul 16 10:07:28] WARNING[144732]: chan_dahdi.c:5245 restore_gains: Unable to restore gains: Invalid argument
[Jul 16 10:07:28] WARNING[144732]: chan_dahdi.c:4908 reset_conf: Failed to reset conferencing on channel 4: Invalid argument
– Hungup ‘DAHDI/4-1’
– Executing [failed@smailboxes:1] Verbose(“OutgoingSpoolFailed”, “1,Inbound: OutgoingSpoolFailed,failed”) in new stack

Here are my AMI logs:

2025-07-16 09:40:39.263173 ><<<<<<< Action: Originate
2025-07-16 09:40:39.263173 ><<<<<<< Channel: DAHDI/2/7770001
2025-07-16 09:40:39.263173 ><<<<<<< Exten: onenumber
2025-07-16 09:40:39.263173 ><<<<<<< Priority: 7
2025-07-16 09:40:39.263173 ><<<<<<< Timeout: 90000
2025-07-16 09:40:39.263173 ><<<<<<< CallerID: Rocky Dev Sys <5146307878>
2025-07-16 09:40:39.263173 ><<<<<<< Async: yes
2025-07-16 09:40:39.263173 ><<<<<<< Context: smailboxes
2025-07-16 09:40:39.263173 ><<<<<<< Variable: audch=1
2025-07-16 09:40:39.263173 ><<<<<<< ActionID: 145737925

2025-07-16 09:40:39.265400 <>>>>>>> Response: Success
2025-07-16 09:40:39.265400 <>>>>>>> ActionID: 145737925
2025-07-16 09:40:39.265400 <>>>>>>> Message: Originate successfully queued

2025-07-16 09:40:39.265400 <>>>>>>> Event: Newchannel
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22

2025-07-16 09:40:39.265400 <>>>>>>> Event: DAHDIChannel
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> DAHDIGroup: 2049
2025-07-16 09:40:39.265400 <>>>>>>> DAHDISpan: 1
2025-07-16 09:40:39.265400 <>>>>>>> DAHDIChannel: 2

2025-07-16 09:40:39.265400 <>>>>>>> Event: DeviceStateChange
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Device: DAHDI/2
2025-07-16 09:40:39.265400 <>>>>>>> State: INUSE

2025-07-16 09:40:39.265400 <>>>>>>> Event: Newexten
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: dialplan,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Extension: s
2025-07-16 09:40:39.265400 <>>>>>>> Application: AppDial2
2025-07-16 09:40:39.265400 <>>>>>>> AppData: (Outgoing Line)

2025-07-16 09:40:39.265400 <>>>>>>> Event: VarSet
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: dialplan,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Variable: audch
2025-07-16 09:40:39.265400 <>>>>>>> Value: 1

2025-07-16 09:40:39.265400 <>>>>>>> Event: NewCallerid
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: 5146307878
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: Rocky Dev Sys
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> CID-CallingPres: 0 (Presentation Allowed, Not Screened)

2025-07-16 09:40:39.265400 <>>>>>>> Event: NewConnectedLine
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: 5146307878
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: Rocky Dev Sys
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: 5146307878
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: Rocky Dev Sys
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22

2025-07-16 09:40:39.265400 <>>>>>>> Event: Hangup
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: DAHDI/2-1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 1
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Rsrvd
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: 5146307878
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: Rocky Dev Sys
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: 5146307878
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: Rocky Dev Sys
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: phones-custom
2025-07-16 09:40:39.265400 <>>>>>>> Exten: s
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.22
2025-07-16 09:40:39.265400 <>>>>>>> Cause: 0
2025-07-16 09:40:39.265400 <>>>>>>> Cause-txt: Unknown

2025-07-16 09:40:39.265400 <>>>>>>> Event: Newchannel
2025-07-16 09:40:39.265400 <>>>>>>> Privilege: call,all
2025-07-16 09:40:39.265400 <>>>>>>> Channel: OutgoingSpoolFailed
2025-07-16 09:40:39.265400 <>>>>>>> ChannelState: 0
2025-07-16 09:40:39.265400 <>>>>>>> ChannelStateDesc: Down
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDNum: 5146307878
2025-07-16 09:40:39.265400 <>>>>>>> CallerIDName: Rocky Dev Sys
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineNum: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> ConnectedLineName: <unknown>
2025-07-16 09:40:39.265400 <>>>>>>> Language: en
2025-07-16 09:40:39.265400 <>>>>>>> AccountCode:
2025-07-16 09:40:39.265400 <>>>>>>> Context: smailboxes
2025-07-16 09:40:39.265400 <>>>>>>> Exten: failed
2025-07-16 09:40:39.265400 <>>>>>>> Priority: 1
2025-07-16 09:40:39.265400 <>>>>>>> Uniqueid: 1752684039.23
2025-07-16 09:40:39.265400 <>>>>>>> Linkedid: 1752684039.23

Why am I getting this “DAHDI confmute(0)” error and why is the inbound call going to some “failed” “OutgoingSpoolFailed” extension/channel?

If I try to initiate the outdial via the Asterisk CLI I get the same problem:

server*CLI> channel originate DAHDI/4/7770001 extension onenumber
[Jul 16 09:18:27] WARNING[140800][C-00000010]: chan_dahdi.c:5302 dahdi_confmute: DAHDI confmute(0) failed on channel 4: Invalid argument
[Jul 16 09:18:27] WARNING[140859]: chan_dahdi.c:5302 dahdi_confmute: DAHDI confmute(0) failed on channel 4: Invalid argument
[Jul 16 09:18:27] WARNING[140859]: chan_dahdi.c:5245 restore_gains: Unable to restore gains: Invalid argument
[Jul 16 09:18:27] WARNING[140859]: chan_dahdi.c:4908 reset_conf: Failed to reset conferencing on channel 4: Invalid argument

Originally libpri was installed via dnf (rpm of libpri-1.6.1-6.el9.x86_64), but I tried to install it from libpri-1.6.1 source (per your suggestions in the above URL, where I found your name) and it made no difference.

Running “lsdahdi” in bash and “dahdi show channels” within Asterisk CLI both return my card channels (also: “dahdi show status” shows PRIs connected “OK”). Note, however, that after I installed libpri from source and rebooted, “asterisk show status” returns OK but “asterisk show channels” did NOT show channels until I ran “dahdi restart” first.

Neither “pri show spans” nor “pri show channels” work, but from another web search it seems they’ve removed or support was lost for this. It seems that as a result the ONLY pri commands I can run are: “pri intense..” commands.

I also noticed an absence of libpri in list when I run ldd on dahdi:

…Here’s what I got when I ran this on Rocky Linux 9 with DAHDI 3.4.0:

[root@server asterisk]# ldd /usr/lib64/asterisk/modules/chan_dahdi.so
linux-vdso.so.1 (0x00007ffe1cbf2000)
libtonezone.so.2 => /lib/libtonezone.so.2 (0x00007fd50cc93000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd50ca00000)
libm.so.6 => /lib64/libm.so.6 (0x00007fd50c925000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd50cd32000)

..and here’s what it looked like on CentOS 7 with DAHDI 2.11.1:

linux-vdso.so.1 =>(0x00007ffc5ccd0000)
libtonezone.so.2.0 => /lib/libtonezone.so.2.0 (0x00007f33eb6b0000)
libpri.so.1.4 => /lib/libpri.so.1.4 (0x00007f33eb430000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f33eb210000)
libc.so.6 => /lib64/libc.so.6 (0x00007f33eae48000)
libm.so.6 => /lib64/libm.so.6 (0x00007f33eab40000)
/lib64/ld-linux-x86-64.so.2 (0x00007f33ebbb8000)

However, also from what I’ve read this may be since DAHDI no longer depends on libpri but Asterisk does.

Would anyone be able to help me figure out the problem and correct?

Thank You

2

What do you get when you run : dahdi_cfg -vvvvvvvvv ??

3

[root@server linux]# dahdi_cfg -vvvvvvvvv
DAHDI Tools Version - 3.4.0-rc1

DAHDI Version: 3.4.0-rc1
Echo Canceller(s): MG2
Configuration

SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 3: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 4: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 02)
Channel 03: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 03)
Channel 04: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 04)
Channel 05: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 05)
Channel 06: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 06)
Channel 07: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 07)
Channel 08: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 08)
Channel 09: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 09)
Channel 10: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 10)
Channel 11: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 11)
Channel 12: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 12)
Channel 13: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 13)
Channel 14: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 14)
Channel 15: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 15)
Channel 16: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 16)
Channel 17: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 17)
Channel 18: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 18)
Channel 19: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 19)
Channel 20: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 20)
Channel 21: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 21)
Channel 22: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 22)
Channel 23: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 23)
Channel 24: D-channel (Default) (Echo Canceler: none) (Slaves: 24)
Channel 25: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 25)
Channel 26: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 26)
Channel 27: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 27)
Channel 28: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 28)
Channel 29: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 29)
Channel 30: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 30)
Channel 31: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 31)
Channel 32: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 32)
Channel 33: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 33)
Channel 34: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 34)
Channel 35: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 35)
Channel 36: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 36)
Channel 37: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 37)
Channel 38: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 38)
Channel 39: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 39)
Channel 40: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 40)
Channel 41: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 41)
Channel 42: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 42)
Channel 43: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 43)
Channel 44: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 44)
Channel 45: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 45)
Channel 46: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 46)
Channel 47: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 47)
Channel 48: D-channel (Default) (Echo Canceler: none) (Slaves: 48)
Channel 49: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 49)
Channel 50: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 50)
Channel 51: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 51)
Channel 52: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 52)
Channel 53: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 53)
Channel 54: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 54)
Channel 55: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 55)
Channel 56: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 56)
Channel 57: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 57)
Channel 58: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 58)
Channel 59: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 59)
Channel 60: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 60)
Channel 61: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 61)
Channel 62: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 62)
Channel 63: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 63)
Channel 64: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 64)
Channel 65: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 65)
Channel 66: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 66)
Channel 67: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 67)
Channel 68: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 68)
Channel 69: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 69)
Channel 70: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 70)
Channel 71: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 71)
Channel 72: D-channel (Default) (Echo Canceler: none) (Slaves: 72)
Channel 73: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 73)
Channel 74: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 74)
Channel 75: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 75)
Channel 76: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 76)
Channel 77: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 77)
Channel 78: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 78)
Channel 79: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 79)
Channel 80: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 80)
Channel 81: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 81)
Channel 82: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 82)
Channel 83: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 83)
Channel 84: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 84)
Channel 85: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 85)
Channel 86: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 86)
Channel 87: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 87)
Channel 88: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 88)
Channel 89: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 89)
Channel 90: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 90)
Channel 91: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 91)
Channel 92: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 92)
Channel 93: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 93)
Channel 94: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 94)
Channel 95: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 95)
Channel 96: D-channel (Default) (Echo Canceler: none) (Slaves: 96)
Channel 97: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 97)
Channel 98: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 98)
Channel 99: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 99)
Channel 100: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 100)
Channel 101: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 101)
Channel 102: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 102)
Channel 103: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 103)
Channel 104: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 104)

104 channels to configure.

Setting echocan for channel 1 to mg2
Setting echocan for channel 2 to mg2
Setting echocan for channel 3 to mg2
Setting echocan for channel 4 to mg2
Setting echocan for channel 5 to mg2
Setting echocan for channel 6 to mg2
Setting echocan for channel 7 to mg2
Setting echocan for channel 8 to mg2
Setting echocan for channel 9 to mg2
Setting echocan for channel 10 to mg2
Setting echocan for channel 11 to mg2
Setting echocan for channel 12 to mg2
Setting echocan for channel 13 to mg2
Setting echocan for channel 14 to mg2
Setting echocan for channel 15 to mg2
Setting echocan for channel 16 to mg2
Setting echocan for channel 17 to mg2
Setting echocan for channel 18 to mg2
Setting echocan for channel 19 to mg2
Setting echocan for channel 20 to mg2
Setting echocan for channel 21 to mg2
Setting echocan for channel 22 to mg2
Setting echocan for channel 23 to mg2
Setting echocan for channel 24 to none
Setting echocan for channel 25 to mg2
Setting echocan for channel 26 to mg2
Setting echocan for channel 27 to mg2
Setting echocan for channel 28 to mg2
Setting echocan for channel 29 to mg2
Setting echocan for channel 30 to mg2
Setting echocan for channel 31 to mg2
Setting echocan for channel 32 to mg2
Setting echocan for channel 33 to mg2
Setting echocan for channel 34 to mg2
Setting echocan for channel 35 to mg2
Setting echocan for channel 36 to mg2
Setting echocan for channel 37 to mg2
Setting echocan for channel 38 to mg2
Setting echocan for channel 39 to mg2
Setting echocan for channel 40 to mg2
Setting echocan for channel 41 to mg2
Setting echocan for channel 42 to mg2
Setting echocan for channel 43 to mg2
Setting echocan for channel 44 to mg2
Setting echocan for channel 45 to mg2
Setting echocan for channel 46 to mg2
Setting echocan for channel 47 to mg2
Setting echocan for channel 48 to none
Setting echocan for channel 49 to mg2
Setting echocan for channel 50 to mg2
Setting echocan for channel 51 to mg2
Setting echocan for channel 52 to mg2
Setting echocan for channel 53 to mg2
Setting echocan for channel 54 to mg2
Setting echocan for channel 55 to mg2
Setting echocan for channel 56 to mg2
Setting echocan for channel 57 to mg2
Setting echocan for channel 58 to mg2
Setting echocan for channel 59 to mg2
Setting echocan for channel 60 to mg2
Setting echocan for channel 61 to mg2
Setting echocan for channel 62 to mg2
Setting echocan for channel 63 to mg2
Setting echocan for channel 64 to mg2
Setting echocan for channel 65 to mg2
Setting echocan for channel 66 to mg2
Setting echocan for channel 67 to mg2
Setting echocan for channel 68 to mg2
Setting echocan for channel 69 to mg2
Setting echocan for channel 70 to mg2
Setting echocan for channel 71 to mg2
Setting echocan for channel 72 to none
Setting echocan for channel 73 to mg2
Setting echocan for channel 74 to mg2
Setting echocan for channel 75 to mg2
Setting echocan for channel 76 to mg2
Setting echocan for channel 77 to mg2
Setting echocan for channel 78 to mg2
Setting echocan for channel 79 to mg2
Setting echocan for channel 80 to mg2
Setting echocan for channel 81 to mg2
Setting echocan for channel 82 to mg2
Setting echocan for channel 83 to mg2
Setting echocan for channel 84 to mg2
Setting echocan for channel 85 to mg2
Setting echocan for channel 86 to mg2
Setting echocan for channel 87 to mg2
Setting echocan for channel 88 to mg2
Setting echocan for channel 89 to mg2
Setting echocan for channel 90 to mg2
Setting echocan for channel 91 to mg2
Setting echocan for channel 92 to mg2
Setting echocan for channel 93 to mg2
Setting echocan for channel 94 to mg2
Setting echocan for channel 95 to mg2
Setting echocan for channel 96 to none
Setting echocan for channel 97 to none
Setting echocan for channel 98 to none
Setting echocan for channel 99 to none
Setting echocan for channel 100 to none
Setting echocan for channel 101 to none
Setting echocan for channel 102 to none
Setting echocan for channel 103 to none
Setting echocan for channel 104 to none

4

lspci
sudo yum -y install pciutils
yum -y install kernel-devel kernel-headers

cd /usr/src/
wget http://downloads.asterisk.org/pub/telephony/dahdi-linux/dahdi-linux-current.tar.gz
wget http://downloads.asterisk.org/pub/telephony/dahdi-tools/dahdi-tools-current.tar.gz
tar -zxvf dahdi-linux-current.tar.gz
tar -zxvf dahdi-tools-current.tar.gz

cd dahdi-linux-*
make
make install

cd /usr/src/dahdi-tools-*
./bootstrap.sh
./configure

If ./bootstrap.sh generates the error "Generating the configure script ...
configure.ac:82: error: possibly undefined macro: AC_PROG_LIBTOOL" means that you need to install the libtool package and run the ./bootstrap.sh command again

yum -y install libtool

libtoolize
aclocal
automake --add-missing
autoconf

After successfully executing ./bootstrap.sh and ./configure
make all
make install
make install-config

If everything went without errors, we can now use a whole set of commands, such as: dahdi_cfg, dahdi_genconf, dahdi_hardware, dahdi_maint, dahdi_monitor, dahdi_registration, dahdi_scan, dahdi_span_assignments, dahdi_span_types, dahdi_speed, dahdi_test, dahdi_tools and dahdi_waitfor_span.

Then recompile Asterisk and chan_dahdi.so
cd /usr/src/asterisk-*
./configure --libdir=/usr/lib64 --with-pjproject-bundled --with-jansson-bundled
make menuselect
(there make sure under Channel Drivers – You have chan_dahdi checked)
make
make install
make samples
make config

Then: reboot

5

The driver is attached to the card, as shown by lspci -v :

02:04.0 Communication controller: Digium, Inc. Wildcard TE405P/TE407P quad-span T1/E1/J1 card 5.0V (rev 02)
Subsystem: Device 0003:0000
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at df400000 (32-bit, non-prefetchable) [size=128]
Kernel driver in use: wct4xxp
Kernel modules: wct4xxp

I can try your instructions/sources, as I never installed pciutils and I downloaded dahdi-linux-complete-3.4.0+3.4.0.tar.gz instead of separate dahdi-linux and dahdi-tools (so no bootstrap, etc).

I will keep you posted on the result..

Thank You

6

Key is to have the right Kernel Version build, as sometimes the “debug” gets in the mix.
So watch out for that.

7

Did you try your steps on Rocky Linux 9?

I’m asking as I got the same error with your dahdi-linux-3.4.0 as I did when I tried to compile. i.e.:

{{{
In file included from ./include/linux/srcu.h:21,
from ./include/linux/notifier.h:16,
from ./arch/x86/include/asm/uprobes.h:13,
from ./include/linux/uprobes.h:49,
from ./include/linux/mm_types.h:16,
from ./include/linux/buildid.h:5,
from ./include/linux/module.h:14,
from /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wct4xxp/base.c:32:
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wct4xxp/base.c: In function ‘free_wc’:
./include/linux/workqueue.h:737:9: warning: call to ‘__warn_flushing_systemwide_wq’ declared with attribute warning: Please avoid flushing system-wide workqueues. [-Wattribute-warning]
737 | __warn_flushing_systemwide_wq();
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wct4xxp/base.c:2030:9: note: in expansion of macro ‘flush_scheduled_work’
2030 | flush_scheduled_work();
| ^~~~~~~~~~~~~~~~~~~~
CC [M] /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wct4xxp/vpm450m.o
LD [M] /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wct4xxp/wct4xxp.o
CC [M] /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctc4xxp/base.o
LD [M] /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctc4xxp/wctc4xxp.o
CC [M] /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.o
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c:233:27: error: macro “DEFINE_SEMAPHORE” requires 2 arguments, but only 1 given
233 | DEFINE_SEMAPHORE(ifacelock);
| ^
In file included from ./include/linux/fs.h:25,
from ./include/linux/compat.h:17,
from ./arch/x86/include/asm/ia32.h:8,
from ./arch/x86/include/asm/elf.h:10,
from ./include/linux/elf.h:6,
from ./include/linux/module.h:19,
from /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c:43:
./include/linux/semaphore.h:34: note: macro “DEFINE_SEMAPHORE” defined here
34 | #define DEFINE_SEMAPHORE(_name, _n)
|
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c:233:1: warning: data definition has no type or storage class
233 | DEFINE_SEMAPHORE(ifacelock);
| ^~~~~~~~~~~~~~~~
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c:233:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_SEMAPHORE’ [-Werror=implicit-int]
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c: In function ‘wait_access’:
/home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c:1519: warning: “MAX” redefined
1519 | #define MAX 10 /* attempts */
|
In file included from ./include/linux/kernel.h:18,
from /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.c:41:
./include/linux/minmax.h:343: note: this is the location of the previous definition
343 | #define MAX(a,b) __cmp(max,a,b)
|
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:249: /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp/base.o] Error 1
make[2]: *** [scripts/Makefile.build:478: /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi/wctdm24xxp] Error 2
make[1]: *** [Makefile:1947: /home/daniel/test-community-suggestion/dahdi-linux-3.4.0/drivers/dahdi] Error 2
make[1]: Leaving directory ‘/usr/src/kernels/5.14.0-570.25.1.el9_6.x86_64’
make: *** [Makefile:74: modules] Error 2
}}}

This is just the first of a few errors. I found some patches online that I applied to get everything compiled. I guess I will try to apply my patches to your source code and see if that works..

Thank You

8

What did you mean by Debug? How do I know if it’s in the mix and how do I avoid it?

9

uname -r
will give you the Kernel in which your build will install sometimes but sometimes --debug kernel gets build (not sure what causes this.)

10

Why don’t we use AnyDesk I can run through it and get you Dahdi installed properly you can find me on teams as Frank Macias email frankmac073@gmail.com

11

Gotcha. Check uname -r and make sure the installed kernel does not have the --debug hyphen. Thank you for the tip. Never noticed that, but I will watch out for that.

12

Ok, thank you for the AnyDesk offer. I don’t currently have it installed, but will if it comes to that..

I just finished patching those dahdi-linux files. Basically, just adjusting DEFINE_SEMAPHORE() and *_uevent() calls (via defines) to have the same number/type of arguments that the c-libraries on Rocky Linux 9.5 have.

Besides the patches, I followed your approach to the ‘T’ and got dahdi-linux installed:

###################################################

DAHDI installed successfully.

If you have not done so before, install the package

dahdi-tools.

###################################################

I then hit issue trying to install dahdi-tools-3.4.0:

./boostrap ran without the error you spoke of, but perhaps that’s since I already had libtool installed. ./configure complained about no auxdir, which I then found out was created when I ran libtoolize

I continued following your instructions and got dahdi-tools installed.

I’m re-compiling Asterisk as I type this. Let me finish this, re-configure the PRI and see if it works now..i.e.: Before moving onto AnyDesk. I will keep you posted..

Thank You

1 Like
13

You’re welcome hope this fixes your issue over all!

14

Good news is that yes it did! I was just able to make a call out 1 PRI span and into the other. I guess you seeing “3.4.0-rc1” (in the dahdi_cfg -vvvv output) was what clue’d you into the problem.

I did notice a couple of errors though:

Systemd status dahdi complains of the following:

{{{
Jul 16 15:16:29 proimg6 sh[2652]: cut: ‘/sys/bus/dahdi_devices/devices/pci:0000:02:04.0/spantype’: No such file or directory
Jul 16 15:16:29 proimg6 sh[2653]: /usr/sbin/dahdi_cfg: Symbol `dahdi_tools_version’ has different size in shared object, consider re-linking
}}}

For the first, seems the filename should be dahdi_spantype. Guess an adjustment is needed in the code (or it’s just a of warning before trying other name). The 2nd error is obviously due to the different version of DAHDI tools, which is also shown in the following output:

{{{
[root@server ~]# dahdi_cfg -vv
dahdi_cfg: Symbol `dahdi_tools_version’ has different size in shared object, consider re-linking
DAHDI Tools Version - 2.11.1

DAHDI Version: 3.4.0
Echo Canceller(s): MG2
}}}

Strange that http://downloads.asterisk.org/pub/telephony/dahdi-tools/dahdi-tools-current.tar.gz would contain an old version of dahdi-tools! Hopefully someone reads this & corrects this :wink:

I will check that URL’s directory for a newer version and/or see if I can find a non-rc1 version of dahdi-linux-complete to fix the dahdi-tools version issue, while keeping the PRIs working :wink:

I’m working remotely today, but will also need to test my analog card to make sure it works when I am hands on..

Thank you again Frank!

15

Good news! It did fix my issue! I was able to make an call out via 1 PRI and into the other PRI :wink:

I guess what clue’d you into the problem was when you saw "3.4.0-rc1’ in the dahdi_cfg -vvvvvvvvv output :wink:

I did notice some issues though. First of all, when I run systemd status dahdi I see the following errors:

{{{
Jul 16 15:16:29 server sh[2652]: cut: ‘/sys/bus/dahdi_devices/devices/pci:0000:02:04.0/spantype’: No such file or directory
Jul 16 15:16:29 server sh[2653]: /usr/sbin/dahdi_cfg: Symbol `dahdi_tools_version’ has different size in shared object, consider re-linking
}}}

For the first error, seems the filename should actually be dahdi_spantype. Don’t know if there needs to be a change made in the code or if it’s just a warning, before checking for other filename. As for the second error, it’s obviously due to the older dahdi-tools version..as I see here:

{{{
[root@server ~]# dahdi_cfg -vv
dahdi_cfg: Symbol `dahdi_tools_version’ has different size in shared object, consider re-linking
DAHDI Tools Version - 2.11.1

DAHDI Version: 3.4.0
}}}

Strange that the dahdi-linux version at http://downloads.asterisk.org/pub/telephony/dahdi-tools/dahdi-tools-current.tar.gz URL is an old version. Maybe someone will read this and correct that. I will check for a newer version in directory of that URL and/or try to find a non-rc1 version of dahdi-linux-complete to see if that fixes it, while keeping my PRIs working.

I am working remotely today, but once I’ve got that straightened out I will also have to test that my analog cards are working when I am hands on..

Thank you for all your help Frank!

16

FYI:

  1. Sorry for the double post. I re-typed shortly after 5pm (thinking it was a timeout and I lost the message), only to notice a notification afterwards that “Akismet has temporarily hidden your post”. Someone appears to have reviewed and then the post was un-hidden at 3am.

  2. I just checked and seems someone read my post and uploaded a new version of dahdi-tools-3.4.0 and current at around the same time (3am). I will be trying to install that version first, which I assume will fix the version issue.

As for dahdi-linux-complete. Seems there is a newer non-rc1 version now.

I do see some discrepancies though. Seems a new “current” and “3.4.0” versions were uploaded to replace older version on July 1st, but the check sums are for some other version uploaded on June 18th as they don’t match the new version!

Well, chances are there are no issues with my download so I will try that copy later as well to see if the PRI works with it (which would simplify my install).

..and maybe someone will read this & correct the checksum files in the meantime as well! :wink: ..lol

Hope this helps

17

I have tried installing the recently updated new version of dahdi-linux-3.4.0 and dahdi-tools-3.4.0 and then re-tried with dahdi-linux-complete-3.4.0. Unfortunately, in both cases I get the following error when I run dahdi_cfg -vvvvv:

{{{
dahdi_cfg: Symbol `dahdi_tools_version’ has different size in shared object, consider re-linking
DAHDI Tools Version - 2.11.1

DAHDI Version: 3.4.0
}}}

Any idea why it would give me this error and show “DAHDI Tools Version - 2.11.1” when I am installing from version 3.4.0?

Thank You

18

I can help you install / Configure Dahdi first thing tomorrow morning. I am leaving the office now. If you want to do AnyDesk where I can show you the steps to it’s fix

19

Hello Frank,

Sorry for the delay in responding. I went to office yesterday and was going to respond to you, but was unable to since I was working on an old CentOS 7 computer on which I could not upgrade Chrome to a version that these web pages support (and on which I have an older complete DAHDI/Asterisk install, so I don’t want to upgrade the kernel and have to re-install drivers)! Either way, even if I did installing AnyDesk without possibly newer dependencies would have been another issue and I’m not running X-Windows on the Rocky Linux 9 server I am trying to get this DAHDI install straightened out on.

I did test out my DAHDI install and seems both my PRI and Analog card are working (I was able to get calls across both). I’m just questioning whether or not it’s normal to see the shared object warning and DAHDI Tools Version 2.11.1 in the output below (especially since I saw DAHDI Tools Version 3.4.0 when I was originally installing from the -rc1 version!), when I installed it from file I just retrieved last week using dahdi-tools-3.4.0.tar.gz (from:

http://downloads.asterisk.org/pub/telephony/dahdi-tools/dahdi-tools-3.4.0.tar.gz

)

[root@rocky8 ~]# dahdi_cfg -vv
dahdi_cfg: Symbol `dahdi_tools_version' has different size in shared object, consider re-linking
DAHDI Tools Version - 2.11.1

DAHDI Version: 3.4.0
Echo Canceller(s): MG2
Configuration
======================

Rather than setting up AnyDesk, etc, I’m thinking it might be easier if you could tell me where I went wrong. In order to avoid previous versions causing this, I first performed the following steps to uninstall old DAHDI:

systemctl stop dahdi
cd dahdi-linux-3.4.0/
make uninstall
cd ../dahdi-tools-3.4.0/
make uninstall

(since dahdi-linux-complete-3.4.0 for some reason does NOT support make uninstall, I also executed a sequence of lsmod | grep ‘dahdi|wct’ and modprobe -r commands to unload all drivers, then ran the following to remove files manually:

mv /etc/dahdi/ /etc/dahdi-old
rm /etc/rc.d/init.d/dahdi
rm /etc/bash_completion.d/dahdi
rm /etc/udev/rules.d/dahdi.rules
rm -fR /usr/include/dahdi/

rm /usr/lib/dracut/dracut.conf.d/50-dahdi.conf

rm -fR /usr/lib/firmware/.dahdi*
rm -fR /usr/lib/firmware/dahdi*
rm -fR /usr/lib/modules/5.14.0-570.25.1.el9_6.x86_64/dahdi/
rm -fR /usr/sbin/dahdi_*
rm -fR /usr/sbin/lsdahdi
rm -fR /usr/share/dahdi

rm /usr/local/share/perl5/Dahdi/Config/Gen/Chandahdi.pm
}

I then rebooted the server.

I more or less followed the instructions you sent me, with the ONLY difference is that I modified code within dahdi-linux to eliminate compile time errors and be able to compile on Rocky Linux 9.5 (basically adding if conditions to redefine DEFINE_SEMAPHORE and call class_create(), span_uevent(), device_uevent() and astribank_uevent() functions differently according due to function argument & struct differences in this version of linux), but no changes were made to dahdi-tools-3.4.0 itself.

In summary, here are the EXACT steps I took when I installed:

cd dahdi-linux-3.4.0
make
make install

cd dahdi-tools-3.4.0
./bootstrap.sh

yum -y install libtool
libtoolize
aclocal
automake --add-missing
autoconf
./configure

make all
make install
make install-config

cd asterisk-22.4.1
./configure --libdir=/usr/lib64 --with-pjproject-bundled --with-jansson-bundled
make menuselect
make
make install

Note: I even tried and got the same results when installing:

https://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-3.4.0+3.4.0.tar.gz

So is seeing the following normal? :

dahdi_cfg: Symbol `dahdi_tools_version' has different size in shared object, consider re-linking
DAHDI Tools Version - 2.11.1

Thank You

20

If I understand this correctly you’re still using Centos 7, which is way out of date, Gotta move on to maybe Rocky Linux or Alma Linux. I currently run a few asterisk Servers on Rocky Linux 9 and they are working like a charm.
Tell me what output do you get when you run :
dahdi_genconf -v
modprobe dahdi
modprobe dahdi_dummy
modprobe wcb4xxp

dahdi_cfg -vvvvvvvvv