DAHDI Spans Not Registered In 3.0.0


#1

I have just deployed DAHDI 3.0.0 (https://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-3.0.0+3.0.0.tar.gz) to a CentOS 6 system and I am struggling to get the spans registered.

Starting the init script calls “/usr/share/dahdi/dahdi_auto_assign_compat”.

In DAHDI 2.11.1 this just ran the following at the end:

Now handle Astribanks

LC_ALL=C dahdi_registration -Rv on

but in DAHDI 3.0.0, it now runs:

Now handle Astribanks

unmatched="dahdi_span_assignments unmatched"
if [ -n “$unmatched” ]; then
# Only if astribanks are not matched in span-assignments.conf
# TODO: have dahdi_registration run only on “$unmatched”
LC_ALL=C dahdi_registration -Rv on
fi

No parameter is passed to “dahdi_span_assignments” and so the $DEVICES variable is set to the results of:
ls -d /sys/bus/dahdi_devices/devices/* 2>/dev/null

which is nothing, and therefore the $unmatched variable has a length of zero and the “dahdi_registration” command does not get run.

How should I get the spans to be registered?

Thanks.

Below are some details from the system:

lsusb:
Bus 001 Device 027: ID e4e4:1162 Xorcom Ltd. Astribank 2 series

dahdi_hardware -v
usb:001/027 xpp_usb+ e4e4:1162 Astribank-modular FPGA-firmware
LABEL=[usb:X1082477] CONNECTOR=@usb-0000:00:14.0-13
XBUS-00/XPD-00: E1 (31) Unregistered
XBUS-00/XPD-01: E1 (31) Unregistered
XBUS-00/XPD-40: ECHO (0) Unregistered

ls -al /sys/bus/dahdi_devices/devices
total 0
drwxr-xr-x 2 root root 0 Jan 4 19:18 .
drwxr-xr-x 4 root root 0 Jan 4 19:17 …

cat /etc/dahdi/assigned-spans.conf

Autogenerated by /usr/sbin/dahdi_span_assignments on Fri Jan 4 18:52:02 SAST 2019

Map devices + local spans to span + base channel number

Device: [usb:X1082477] @usb-0000:00:14.0-13 /sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/xbus-00/astribanks:xbus-00

usb:X1082477 1:1:1
usb:X1082477 2:2:32


#2

In testing against the supported Digium hardware devices, we didn’t run into this issue. If this is specific to the Xorcom equipment, you’ll need to engage them - we don’t have any to test against.


#3

Check the change-log of DAHDI 3.0.0, I read that some modules were deprecated: http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary


#4

Thanks for the responses.

I have spoken to Xorcom and they have advised that we should source the DAHDI software from them if we are using Xorcom hardware. They have not yet released a version of DAHDI 3.0.0, so I will be replacing the installation of 3.0.0 sourced from Digium with 2.11.1 sourced from Xorcom.