The other day I was having Sangoma A102D D channel problems. The PRI would lose connectivity after a few hours. We would have to restart asterisk to make the PRI come up again. We were getting the following errors.
[Mar 16 04:02:08] WARNING[3117] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
[Mar 16 04:02:12] WARNING[3117] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
[Mar 16 04:02:16] WARNING[3117] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
[Mar 16 04:02:20] WARNING[3117] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
[Mar 16 04:02:24] WARNING[3117] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
[Mar 16 04:02:28] WARNING[3117] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
We fixed this issue by doing a firmware upgrade. We were running firmware verison 29 and the latest was 37. Maybe there was something in the driver the firmware did not like.
Wanpipe Linux AFT Firmware Update
AFT Firmware Update Instructions
Latest AFT Firmware Files: ftp.sangoma.com/firmware
To determine your current firmware version: Firmware Version Instructions
–> wanrouter hwprobe
NOTICE: If you are using Netborder Express Gateway, the wanpipe directory is located in the sangoma/ directory inside your setup .tar.gz. Also, since Netborder express does not use the wanpipe configuration files to start the drivers (but instead its own pstn-config.xml file) in order to stop manually all devices before proceeding with the firmware update you may need to execute: “wanrouter stop force”, that will stop all devices even if there is no wanpipex.conf in /etc/wanpipe
The Firmware Update utility is located in: wanpipe/util/wan_aftup
directory which was created by untaring the wanpipe release.
If you are running under Trixbox, this utility is located in: /etc/wanpipe/firmware/wan_aftup
eg: cd wanpipe/util/wan_aftup or cd /etc/wanpipe/firmware/wan_aftup
- Download and Save the latest BIN file from ftp.sangoma.com/firmware into wanpipe/util/wan_aftup or /etc/wanpipe/firmware/wan_aftup(for Trixbox) directory.
- Make sure wanpipe modules are unloaded
#>wanrouter stop
#>wanrouter modules #Check for loaded wanpipe modules - Start update program
./update_aft_firm.sh
- Specify interface name that corresponds to your AFT card, based on the hw probe list displayed. (you must write the actual interface name, and not just press enter)
- Specify the desired firmware version from the list displayed.
- At this point firmware update will begin…
- Once the flashing is done, select Y to reload firmware.
(This step only reloads flash, not your machine!)IMPORTANT:
If you select N for this step, you will have to reboot the machine for the new firmware to take effect.
- End of firmware update
All AFT cards contain DUAL Firmware flash devices. The primary flash device, is used to bootstart the AFT card on boot up. During AFT card flashing, the new firmware is stored into the primary flash device.
If a machine crashed during card flashing or for some reason flashing failes that causes primary flash device to become corrupted, the card would be rendered useless. In this scenario the secondary flash device can be selected to boot the card, which would allow a user to re-flash the primary device again.
In order to select the secondary flash device, one must boot the AFT card with firmware recovery jumpers set. Please refer to sections below for firmware jumper settings of each AFT card.
- Shutdown the machine and take out the AFT card
- Set the Firmware recover jumper. Refer to here for each AFT card.
- Restart the machine with firmware recover jumpers set.
- Proceed to re-flash the card, as described above.
- Once re-flashing is completed, shutdown the machine and remove flash recover jumpers.
- Restart the machine with new card firmware.
