Cards
Ans: When running the “LSPCI” command in Linux terminal, and if it doesn’t find the output with the name “Sangoma” then please follow below procedures for troubleshooting the issue.
Troubleshooting Steps:
- 1.Physical situation: Make sure card is not physically damaged and not having loose connection with PCI slot (or riser board).
- 2.Enable the PCI slot, on BOIS: Ensure the PCI slot in BIOS settings is enabled, in which the card is installed in, otherwise this may result in card not detected. For example - if card is installed on PCI slot X then need to make sure PCI slot X is enabled because we might have many slots in system.
- 3.Reseating the card on PCI Slot: Try reseating (Plug out and plug back the card) the card in the same PCI slot and then run LSPCI command to see if the card comes back up again. This will rule out the possibilities of card not properly seated in the PCI slot.
- 4.Riser board settings:
- A.Reseat Riser i.e. make sure card and riser connectivity proper and then again connect with PCI slot to see if it gets detect.
- B.Change the riser board and check if the card shows up in LSPCI.
- C.Connect the card directly to PCI slot to see if it detect.
- 5.Trying with different PCI slot: Try to reseat the card on a different PCI slot on same server.
- 6.Testing with different server: Place the card into a different server and see if the card shows up in LSPCI.
- If Card is detecting in LSPCI Slot, but E1/T1 span is not coming up, follow the below testing procedure, wanrouter status
-
- wanpipemon -i wXg1 -c Ta (replace X in "wXg1" with the wanpipe number in question).
Sangoma Linux Driver (Wanpipe) require a list of packages on your system prior to install. The following packages must also be installed if upgrading Wanpipe for Trixbox/Elastix/AsteriskNow from source (.tgz):
Redhat Distributions YUM Packages (i.e. Centos, Trixbox/Elastix source (.tgz) install )
yum -y install kernel-devel-$(uname -r) libtool* make gcc patch perl bison gcc-c++ ncurses-devel flex flex-devel libtermcap-devel autoconf* automake* autoconf
Ubuntu/Debian 6 Distributions Apt-get Packages
apt-get -y install gcc g++ automake autoconf libtool make libncurses5-dev flex bison patch libtool autoconf linux-headers-$(uname -r) sqlite3 libsqlite3-dev
Redhat Distributions YUM Packages (i.e. Centos, Trixbox/Elastix source (.tgz) install )
yum -y install kernel-devel-$(uname -r) libtool* make gcc patch perl bison gcc-c++ ncurses-devel flex flex-devel libtermcap-devel autoconf* automake* autoconf
apt-get -y install gcc g++ automake autoconf libtool make libncurses5-dev flex bison patch libtool autoconf linux-headers-$(uname -r) sqlite3 libsqlite3-dev
The following instructions will guide you through the Installation of the Sangoma Wanpipe driver on your server that contains all required software pacakges already installed(i.e. Asterisk, DAHDI, Libpri).
Download the latest official release of the Sangoma Wanpipe Driver
wget ftp://ftp.sangoma.com/linux/current_wanpipe/wanpipe-current.tgz "
Un-compress the download Wanpipe driver (.tgz file) located in /usr/src
1. tar xvfz wanpipe-current.tgz
2. cd wanpipe-/
• Install the Sangoma Wanpipe driver by typing the following in the newly created wanpipe- directory:
-> ./Setup install
Download the latest official release of the Sangoma Wanpipe Driver
wget ftp://ftp.sangoma.com/linux/current_wanpipe/wanpipe-current.tgz "
Un-compress the download Wanpipe driver (.tgz file) located in /usr/src
1. tar xvfz wanpipe-current.tgz
2. cd wanpipe-
• Install the Sangoma Wanpipe driver by typing the following in the newly created wanpipe-
- DAHDI chunk size can be configured for the following units:
- • 8 bytes (default 1ms)
- • 16 bytes (2ms)
- • 40 bytes (5ms)
- • 80 bytes (10ms)
- • Type the following:
- ./Setup install --dahdi-chunk=
IP Phones
- Audio Code - admin/1234
- Yealink - admin/admin
- Sangoma - admin/admin
- Grandstream - admin/admin
- ESCENE - root/root
menu--status--network status à then show ip
menu---administration--enter password – factory reset
Check the SIP Server address in phone gui. If it’s the right one then check the Authentication password for the account used in IP-Phone. Still if your are facing the same error then check the Firewall status of SIP Server. All the UDP ports should be opened at SIP Server for smooth running.
Disable VLAN on GUI after login.