Free Whitepapers
-
Sangoma SS7 Gateway Advantage
Excellent ROI, wide range of protocol variants, ultimate transcoding support, simple licensing, scalability, intuitive and easy
-
28 Ways Sangoma Makes Asterisk Better
Lear how Sangoma makes Asterisk more scalable, more reliable and more functional. Sangoma delivers where others fall short.
-
SBC - The Critical Component
SBC addresses key VoIP and UC issues around security, remote workers, firewalls, transcoding and SIP interoperability.
-
How to Respond to MVAS Demand and Increase Revenue
The Indian market has embraced Value Added Services igniting innovation and new business opportunities.
-
Bridging Open Source and Proprietary Telephony Environments
Today's Communications needs may not be well addressed by Open Source resources.
-
Enterprise Applications of Sangoma Vega Media Gateways
Branch Offices
SIP Trunking
PSTN Trunking
Hospitality -
Specialized Hardware Answers Booming VoIP Transcoding Demands
Transcoding voice calls between various networks is increasingly necessary.
-
Mobile Value-Added Services with Sangoma
Open source telephony platforms can deliver low-cost solutions for the lucrative Mobile Value Added Services market.
-
Effectively Bridging Lync and Legacy Communication Nodes in a Mixed Environment
Facilitate the migration from legacy through hybrid, to a fully Lync-optimized environment.
-
Contact Center Doubles Capacity and Expands Services
Increased Efficiency with VICIdial Call Center Platform and Sangoma Call Analyzer.
-
Increasing the Density of Asterisk systems by 300%
Asterisk can run up to forty-eight spans of Digital Telephony (1,440 simultaneous calls) without overloading the CPU.
-
VoIP Resiliency, Security and Availability
An Analysis of VoIP Networks, their Vulnerabilities and the Impact of VoIP Technology on Emergency Call Handling.
AsteriskNow
All RPMs compiled for AsteriskNow are dependent on the Kernel Version, the dahdi/zaptel version and the asterisk version that come with default AsteriskNow. If you change any of these versions you must Install Wanpipe from Source
- Wanpipe installation from Source (when an RPM is not available)
WANPIPE INSTALLATION THROUGH RPMS
The following list contains the Wanpipe Driver RPMS for the stock versions of AsteriskNow that support ALL Sangoma PRI,BRI and Analog cards. They are dependent on the specific Dahdi/Zaptel, Asterisk and Kernel versions:
AsteriskNOW 1.7
| DISTRIBUTION | Dahdi | Kernel | Asterisk | Wanpipe Version (Change Log) |
Driver RPM |
|
AsteriskNOW 1.7 (YUM UPDATE) |
2.4.1.2-1 | 2.6.18-238.9.1.el5 | 1.6.2.17.2-1 | 3.5.20 | Wanpipe Driver |
|
AsteriskNOW 1.7 (YUM UPDATE) |
2.4.0-1 | 2.6.18-194.32.1.el5 | 1.6.2.16-1 | 3.5.18 | Wanpipe Driver |
| DISTRIBUTION | Dahdi | Kernel | Asterisk | Wanpipe Version (Change Log) |
Wanpipe RPM | ||
|
AsteriskNOW 1.7 (YUM UPDATE) |
2.4.1.2-1 | 2.6.18-238.9.1.el5 | 1.4.40-2 | 3.5.20 | Wanpipe RPM Driver | ||
|
AsteriskNOW 1.7 (YUM UPDATE) |
2.4.0-1 | 2.6.18-194.32.1.el5 | 1.4.39.1-1 | 3.5.18 | Wanpipe RPM Driver | ||
|
AsteriskNOW 1.7 (Stock Version) |
2.3.0.1-1 | 2.6.18-194.3.1.el5 | 1.4.32-1 | 3.5.11.8 | wanpipe-modules-rpm | wanpipe-util-rpm | |
AsteriskNOW 1.5
| DISTRIBUTION | Dahdi | Kernel | Asterisk | Wanpipe Version (Change Log) |
Wanpipe Modules RPM | Wanpipe Utilities RPM | ||
| AsteriskNOW 1.5 (Stock Version) | 2.2.0.4 | 2.6.18-128.1.1.el5 | 1.4.24 | 3.5.11 | wanpipe-modules-rpm | wanpipe-util-rpm | ||
| AsteriskNOW 1.5 (YUM UPDATE) | 2.3.0 | 2.6.18-164.15.1.el5 | 1.4.30 | 3.5.11 | wanpipe-modules-rpm | wanpipe-util-rpm | ||
|
AsteriskNOW 1.5 (YUM UPDATE) |
2.3.0-1 | 2.6.18-194.3.1.el5 | 1.4.31-1 | 3.5.11.4 | wanpipe-modules-rpm | wanpipe-util-rpm | ||
How to find Kernel, Asterisk, Dahdi Version in Order to Download the correct RPM
1) To find out the kernel version type the command:
| uname -r |
example output : 2.6.18-164.11.1.el5
2) To find out your asterisk version:
| asterisk -V |
example output : Asterisk 1.6.0.22
3) To find out your dahdi/zaptel version
For Dahdi
| rpm -qa | grep dahd |
example output : DAHDI Tools Version - 2.2.0
DAHDI Version: 2.2.0
For Zaptel
| rpm -qa | grep zaptel |
example output : Zaptel Version: 1.4.12.9.svn.r4590-Xorcom-trunk-r7049
To download
*NOTE: You must download BOTH the corresponding Utility and Module RPMfor the Trixbox Version
-> Copy the URL for each utility and Module RPM, then run "wget URL" in the linux command line.
| wget <wanpipe module URL> wget <wanpipe utility URL> |
To install
-> run the "rpm -i" command with each of the downloaded Utility and Module RPM:
| rpm -i <wanpipe module rpm> rpm -i <wanpipe utility rpm> |
To verify that driver has been installed run the command:
| wanrouter hwprobe verbose |
The output should show something similar to the one below (different output for different cards)
| wanrouter hwprobe verbose |
| ----------------------------------------- | Wanpipe Hardware Probe Info (verbose) | ----------------------------------------- 1 . AFT-A200-SH : SLOT=4 : BUS=5 : IRQ=169 : CPU=A : PORT=PRI : HWEC=32 : V=12 +01:FXO: PCIe: PLX1 +02:FXO: PCIe: PLX1 +03:FXS: PCIe: PLX1 +04:FXS: PCIe: PLX |
If you have any issues with the above command, please contact techdesk@sangoma.com
Configuring the Sangoma Card
- Run the configuration script by typing:
setup-sangoma
The above script creates configuration files for:
-> Dahdi/Zaptel
-> Wanpipe in /etc/wanpipe
*Note: BRI is now integrated into Dahdi (Wanpipe 3.5.21 and newer)
*** If you upgrade to Wanpipe 3.5.21 and UP and want to continue to
use the deprecated BRI smg daemon, you must now run:
"setup-sangoma smg"
-> Proceed to the Operation section
SOURCE INSTALLATION
You must install the Wanpipe driver from source if your AsteriskNow system does not have the correct RPM requirements (kernel, dahdi, asterisk versions) as listed above. The instructions below describe how to install the Wanpipe driver from source, which entail:
-> Downloading the source for dahdi/zaptel currently installed on your system
-> compiling the source Wanpipe driver against the dahdi/zaptel sources
Requirements
Please run the follow commands to install the required packages needed for compiling wanpipe drivers from source:
| yum -y install kernel-devel-$(uname -r) libtool* gcc patch perl bison gcc-c++ ncurses-devel flex libtermcap-devel autoconf* automake* |
| ****Please not that if you are using Kernel 2.6.18-128.1.1.el5 then the kernel-devel package will not work and you must download it from here: kernel-devel-2.6.18-128.1.1.el5.i686.rpm**** |
Dahdi/Zaptel Download and Compile
The first step is to identify the version of Dahdi/Zaptel currently installed on the system:
Dahdi Steps (click HERE for Zaptel Steps):
1) Retrieve the version of dahdi currently installed on your system
Type the following command on your Linux CLI:
-> rpm -qa | grep dahdi
The following is an example output of the above command (the output on your system might display varying results):
dahdi-2.3.0.1-3_trixbox
dahdi-modules-2.3.0.1-3_trixbox.2.6.18_128.1.10.el5
The dahdi version is 2.3.0.1 in the above example, it is not 2.3.0.1-3 because the "-3" is a Trixbox version and we are just concerned about the dahdi version.
2) Download the source for the dahdi version found on your system
-> Go to the following website and search for your dahdi version:
-> http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/releases
-> Our search results using the above example would find dahdi-linux-2.3.0.1.tar.gz
-> In the location of your choice (typically /usr/src/) download the release:
-> wget http://downloads.asterisk.org/pub/telephony/dahdi-linux/releases/dahdi-linux-2.3.0.1.tar.gz *NOTE: the dahdi version will vary
3) untar and compile dahdi
-> tar xvfz dahdi-<version>.tar.gz
-> cd dahdi-<version>
-> make
4) The compiling is done, if there is any errors please contact techdesk@sangoma.com
Zaptel Version
Make sure to have all the package requirements installed:
-> http://wiki.sangoma.com/Package-requirements
1) Retrieve the version of Zaptel currently installed on your system
Type the following command on your Linux CLI:
-> rpm -qa | grep zaptel
The following is an example output of the above command (the output on your system might display varying results):
zaptel-1.4.12.1-1_trixbox
zaptel-modules-1.4.12.1-1_trixbox.2.6.18_128.1.10.el5
The Zaptel version is 1.4.12.1 in the aove example, it is not 1.4.12.1-1 because the "-1" is a Trixbox version and we are just concerned about the Zaptel version.
2) Download the source for the Zaptel version found on your system
-> Go to the following website and search for your Zaptel version:
-> http://downloads.asterisk.org/pub/telephony/zaptel/releases/
-> Our search results using the above example would find zaptel-1.4.12.1.tar.gz.
-> In the location of your choice (typically /usr/src/) download the release:
-> wget http://downloads.asterisk.org/pub/telephony/zaptel/releases/zaptel-1.4.12.1.tar.gz *NOTE: the Zaptel version will vary
3) untar and install zaptel
-> tar xvfz zaptel-<version>.tar.gz
-> cd zaptel-<version>
-> ./configure
-> make
4) The compiling is done, if there is any errors please contact techdesk@sangoma.com
Asterisk Download and Compile
DEPRECATED
*Note: This step is only required when using BRI Cards (A500/B700) with Wanpipe Driver 3.5.20 and below
BRI is now integrated into Dahdi in Wanpipe 3.5.21 and above (this step not required)
1. Find the version of Asterisk Currently installed:
#> asterisk -V
2. Go to http://downloads.asterisk.org/pub/telephony/asterisk/releases/ and search for your Asterisk version. If you have Asterisk 1.4.22 then the URL will be http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-1.4.22.tar.gz
3. Once you have the URL run the commands:
#> cd /usr/src/
and then
#> wget X with X being the URL
Once the download is complete run the command "
#>tar xfz asterisk-<version>.tar.gz
and then
#> cd asterisk-<version>
4. Once you are in the Asterisk source run the command
#> ./configure; make
this will configure and build the source.
Wanpipe Driver Download and Install
- Download the lastest Wanpipe Driver: Wanpipe Driver
- Untar wanpipe release in arbitrary directory (/usr/src/ is recommended).
#> tar xvfz wanpipe-<version>.tgz
#> cd wanpipe-<version>
Verifyasterisk and zaptel/dahdi are shutdown by using the commands:
Zaptel method
#> amportal stop
#> service zaptel stop
Dahdi method
#> asterisk -rx "stop now"
#> service dahdi stop
------------ - Install the Wanpipe Driver:
#>./Setup install
Proceed with installation Select "Y" for each option.f
Setup will ask you which compilation method you would like to choose to install the driver:
- For all PRI/BRI/ANALOG cards, choose Option 2
Setup will try to auto-detect dahdi sources in /usr/src directory
[By default Setup will look in /usr/src]
*Note: if you are running a production environment with BRI and Wanpipe using the deprecated smg daemon
and wish to continue using it, you must choose Option 6/7
--- - Proceed with Defaults for the rest of the compilation.
-- - Last step in installation will ask you to configure the Sangoma card(s) for Dahdi/Zaptel/
If any errors are encountered during the compilation of the utilities, click here for assistance.
Confirm Successful Wanpipe/Dahdi Installation
Confirm successful Wanpipe/Dahdi installation run:
#> wanrouter hwprobe
This command will load the wanpipe and Dahdi modules and will print out list of all Sangoma hardware installed on the system.
Configure Sangoma Cards
- Run the configuration script:
-> type: setup-sangoma
The above script creates configuration files for:
-> Dahdi/Zaptel
-> Wanpipe in /etc/wanpipe
*Note: BRI is now integrated into Dahdi (Wanpipe 3.5.21 and newer)
*** If you upgrade to Wanpipe 3.5.21 and UP and want to continue to
use the deprecated BRI smg daemon, you must now run:
"setup-sangoma smg"
Operation
To Start Wanpipe, Dahdi/zaptel and Asterisk, follow the steps below:
- start Wanpipe Ports
-> wanrouter start
- Check /var/log/messages for info or errors
--- - Configure DAHDI/ZAPTEL module
-> dahdi_cfg -vvv (dahdi)
or
-> ztcfg -vvv (zaptel)
*Note: this step is taken care of if you have chosen to perform dahdi_cfg automatically
during 'setup-sangoma'
--- - start Asterisk
-> amportal start -> asterisk -r
To stop the Wanpipe driver at any time, you must stop Asterisk first:
1-> amportal stop
2-> wanrouter stop
If using DEPRECATED BRI smg Installation you will need to add a "custom" trunk to dial out. If you go to http://wiki.sangoma.com/WoomeraFreepbx this details how to do this with Freepbx which is essentially the same as Trixbox.
