How to fix Dahdi-Wanpipe Drivers in ScopTEL
If you have updated your ScopTEL PBX server to use a
new CentOS kernel, it can sometimes happen
that DAHDI/WANPIPE drivers need to be recompiled
manually.
To verify if dahdi is properly compiled and working:
From ssh do: timertest
You should see a test result, if not then dahdi is not properly compiled. In this result timertest is functional.
[root@sip ~]# timertest
Opened timer...
Set timer duration to 8000 samples (1000 ms)
Waiting...
Timer Expired (999 ms)!
Timer Expired (1998 ms)!
Timer Expired (2999 ms)!
Timer Expired (4000 ms)!
^C
[root@sip ~]#
You can also check if dahdi is compiled on the active kernel with 'dkms status' and 'uname -a'.
dkms status will print the installation status on all installed kernels.
uname -a will print the active kernel version.
[root@sip ~]# dkms status
dahdi, 2.11.1-11.el7.scopserv, 3.10.0-1127.el7.x86_64, x86_64: installed
wanpipe, 7.0.26-1.el7.scopserv, 3.10.0-1127.el7.x86_64, x86_64: installed
[root@sip ~]#
[root@sip ~]# uname -a
Linux hostname 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@sip ~]#
If you've been getting issues with Digital/Analog interfaces and drivers
refuse to start, here's how to fix it.
To fix the problem, we’ll need to remove current installed drivers. So open
an SSH connection to the server and execute the following
commands:
service asterisk stop
service dahdi stop
rpm -e dahdi wanpipe dkms-dahdi dkms-wanpipe
--nodeps
Now that drivers are cleaned, you must reinstall drivers, this step will
always download the latest version available on ScopServ RPM
repositories.
You must execute this command from SSH to reinstall packages:
scopserv_yum install dkms-dahdi dkms-wanpipe -y
Finally, from the ScopTEL GUI, you must Commit
configuration on the Telephony module.
Then it is recommended in SSH to do:
service dahdi start
service asterisk start
As you can see, the procedure for reinstalling the DAHDI
and Wanpipe drivers on your ScopTEL PBX is
relatively simple.
Related Articles
ScopTEL IP PBX Software - Basic Installation Hierarchy for Telephony Server
Basic Installation Hierarchy for Telephony Server Therefore the purpose of this document is to provide a visual walkthrough of a very basic but functional installation for one tenant. This tutorial does not include an overview of the overall network ...
Module 4 - ScopTEL IP PBX Software - PSTN Interfaces and Gateways
Gateways A VoIP gateway is as a bridge between: Interfaces: (T1/E1, FXO, FXS) Protocols: SIP, Cisco SCCP/Skinny, MGCP (legacy protocol), and H.323 (legacy protocol) CODECS (media): GSM (13 Kbps), iLBC (15 Kbps), G.711 (64 Kbps), G.722 (48/56/64 ...
Module 5 - ScopTEL IP PBX Software - Interface Groups and Outgoing Lines
Interfaces Card Detect If any analog FXO/FXS or T1/E1 or BRI cards are installed then you must do a “Card Detect” to recognize and configure that hardware before the drivers and configurations can be properly loaded. Configuration > Telephony > ...
Installing and Configuring a Sangoma Card on ScopTEL PBX
ScopServ Integration Full integration and support for Sangoma cards is included in ScopTEL PBX and includes a quick and easy way to configure all Sangoma cards directly from the ScopTEL PBX Web management interface. Sangoma Digital/Analog Cards ...
ScopTEL - Sangoma Transcoding Installation
Purpose of Document Depending on the Sangoma Hardware Transcoding SKU the solution can support between 30 and 4000 simultaneous G.729 sessions. Hardware transcoding off loads CPU cycles from the host CPU and does not require software G.729 licenses ...