dahdi installation and configuration

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

DAHDI Installation and Configuration

Author: Redfone Communications

Created On: 30 Nov 2008 10:20 PM

DAHDI Installation and Configuration Instructions forAsterisk-1.4.22 and Asterisk-1.6

Applies to the following foneBRIDGE2 Models: 750-5000, 750-5000-EC, 750-5050, 750-5050-EC,750-5050-Single, 750-5050-EC-Single

Updated December 1, 2008

Asterisk-1.6 no longer supports Zaptel. It only contains support for DAHDI.See the following link for complete details;http://www.asterisk.org/node/48539 General update instructions for migrating from Zaptel to DAHDI can befound here;http://svn.digium.com/svn/dahdi/tools/tags/2.0.0/UPGRADE.txt The Redfone TDMoE driver has been ported to the new DAHDI frameworkand can be installed using the following instructions. Download and Install Dahdi

1. Download and untar dahdi-linux and dahdi-tools# wget http://support.red-fone.com/downloads/dahdi/dahdi-linux-redfone-2.1.0.4.tar.gz

Page 1/8Powered By Kayako SupportSuite


# wget http://support.red-fone.com/downloads/dahdi/dahdi-tools-redfone-2.0.0.tar.gz# tar -xzvf dahdi-linux-redfone-2.1.0.4.tar.gz# tar -xzvf dahdi-tools-2.0.0.tar.gz2. Patch dahdi-tools# cd dahdi-tools# wget 'http://bugs.digium.com/file_download.php?file_id=20121&type=bug' -O - | patch -p03. Build dahdi-linux# cd dahdi-linux-2.1.0.4# make clean# make# make install 4. Build dahdi-tools# cd dahdi-tools-2.0.0# ./configure# make# make install# make config

Download and Install fonulator (RPM) configuration utility

The following instructions explain how to install the fonulator for Redhat basedsystems such as CentOS, Fedora Core and others.1. Download rpm# wget http://support.red-fone.com/downloads/fonulator/fonulator-2.0.0-36.i386.rpm2. Install RPM# rpm -ivh fonulator-2.0.0-36.i386.rpm

3. Confirm fonulator has been installed properly by executing it from thecommand line# fonulator -Vfonulator 2.0.0Copyright (C) 2007 Redfone Communications, LLC. Build Number: 36For advanced fonulator command line options execute with the --help flag.# fonulator --help

Configuring foneBRIDGE

Redfone.conf1. Download sample redfone.conf file to your /etc/ directory;# cd /etc/



# wget http://support.red-fone.com/downloads/fonulator/redfone.conf

2. The Fonebridge MOD-B firmware now uses IP based communication forsending updates to the device. The default IP address of FB1 and FB2are as follows:

a. FB1=192.168.1.254b. FB2=192.168.1.253

3. Configure the server's Ethernet interface used to communicate withthe Fonebridge with an IP address from the same 192.168.1.X range.Ex;

# ifconfig eth1 192.168.1.200Alternatively an alias IP address can be assigned to an existing IP interface;# ifconfig eth1:0 192.168.1.200

NOTE: This IP should be made permanent and done with your Linux distro's normal utilities for setting IP addresses.

4. Edit the redfone.conf file with your favorite text editor (nano,pico,vi, etc.) 5. Under the [globals] section change the server= MAC address toreflect the MAC address of your server's Ethernet card that will becommunicating with the Fonebridge. You can determine the MAC addressof your interface by issuing the ifconfig ethN command in Linux.Ex;

# ifconfig eth1eth1 Link encap:Ethernet HWaddr 00:16:36:76:09:91

6. The port= parameter designates which foneBRIDGE Ethernet port will beusedto communicate with your Asterisk server. Valid options are 1 or 2 andcorrespond to FB1 and FB2 on the device Ex;port=1

7. [spanN] parameters are used to set the individual configurations ofeach T1/E1 port on the Fonebridge. Options per span include;

framing= ccs,esf,sf,casencoding=b8zs,hdb3crc4= (used on some E1 lines)rbs= Used for CAS/RBS type lines on Channel Banks, E&M, etc.shorthaul=0-4longhaul=0-3 (See LBO explanation at end of document)



loopback= Loopback to far end telco equipment for line testingNOTE: MFC/R2 requires 'framing=cas'

A sample Quad T1 PRI redfone.conf might look like this;

[globals]fb=192.168.1.254port=1server=00:11:22:33:44:55

[span1]framing=esfencoding=b8zs



[span4]framing=esfencoding=b8zsA sample Quad E1 PRI redfone.conf might look like this;

[globals]fb=192.168.1.254port=1server=00:11:22:33:44:55

[span1]framing=ccsencoding=hdb3






Advanced Settings

Longhaul and Shorthaul LBO OverviewThe 'longhaul' and 'shorthaul' parameters can be added under the [spanN]block of each span. These values should only be changed under advise fromyour TELCO. Aything with longhaul means the Adaptive Equalizer is ON! You can only choose longhaul or shorthaul, you cannot have both.

Longhaul Values (longhaul='value')0 => 0dB (No Attenuation, just turns on Adaptive Equalizer) 1 => -7.5dB 2 => -15.0dB 3 => -22.5dB

Shorthaul Values (shorthaul='value')0 => 0-133 feet 1 => 133-266 feet 2 => 266-399 feet 3 => 399-533 feet 4 => 533-655 feet

LoopbackThe 'loopback' parameter, placed under the [spanN] block places that span in aloopbackmode to be utilized by the Telco to test the T1/E1 circuit all the way to thefonebridge device. It is not useful for testing or debugging the Asterisk side ofthe connection or for running a local loopback.

Echo CancellationOn EC enabled foneBRIDGE2 the Echo Cancellation hardware is automaticallyconfigured based on the span information in redfone.conf. If it is an E1, it willbe configured for EC on E1 lines and the same for T1. The foneBRIDGE2normally ships with the uLaw companding mode enabled in the DSP. Whenconfiguring E1 spans the first time it may cycle power to the foneBRIDGE2 core



in order to reset the DSP to aLaw companding which is the default for E1. Thisis a one-time occurrence.

8. Power on the fonebridge and once your redfone.conf file is complete youwill update the fonebridge by executing the fonulator utility. Thefonulator utility will read the information contained in yourredfone.conf and provided all IP addressing is correct, send it to thefonebridge which will configure all of its spans as per yourparameters, come on line and begin transmitting TDMoE traffic.

Execute the fonulator utility from the Linux command line. Ex;

# fonulator

By default the fonulator will look for /etc/redfone.conf. You canspecify an alternative file name by affixing the full file namepath after fonulator. Ex;

# fonulator /etc/redfone2.conf

You can also query the device with fonulator todetermine what the current running configs are. Ex;

# fonulator -vq

Please note that if power is cycled to the fonebridge it willloose its current configuration and you will need to fonulateagain.

Configuring /etc/dahdi/system.conf

The system.conf file follows all standard rules and syntax as otherzaptel based hardware with the only exception being the use of thedynamic= parameter.

NOTE: If using a Quad port Fonebridge you must always specify 4 dynamicspans in system.conf even if you have only configured a single span onthe device. The same applies on the Dual port. Two dynamic spans mustalways be specified even if only 1 span has been configured inredfone.conf.

dynamic=ethmf,,/,/,,



A sample 4x T1 PRI configuration would like the following;

dynamic=ethmf,eth1/00:50:C2:65:D0:70/0,24,0dynamic=ethmf,eth1/00:50:C2:65:D0:70/1,24,0dynamic=ethmf,eth1/00:50:C2:65:D0:70/2,24,0dynamic=ethmf,eth1/00:50:C2:65:D0:70/3,24,1#bchan=1-23dchan=24bchan=25-47dchan=48bchan=49-71dchan=72bchan=73-95dchan=96#loadzone = usdefaultzone=us

In the above example, the Asterisk server is communicating on its eth1with the fb address of 00:50:C2:65:D0:70. Span numbers start at 0. Ithas 24 channels (E1 would be 31) and timing begins at 4.A sample 2x E1 PRI configuration would look like the following;

dynamic=ethmf,eth1/00:50:C2:65:D0:70/0,31,2dynamic=ethmf,eth1/00:50:C2:65:D0:70/1,31,1#bchan=1-15,17-31dchan=16bchan=32-46,48-62dchan=47## NOTE: Most E1 use alaw codec and this must be specified.alaw=1-62 #loadzone = usdefaultzone=us

Starting dahdi

After successfully installing dahdi, configuring redfone.conf andsystem.conf you can now load the necessary dahdi modules.

1. Load modules# modprobe dahdi# modprobe dahdi_dynamic_ethmf



2. Confirm modules loaded properly with dahdi_tool# dahdi_tool

If you do not see any spans you may need to execute 'dahdi_cfg' and thencheck 'dahdi_tool'.

Once the Fonebridge device has been configured via the fonulator toolyou should see a YEL alarm (as shown above) at a minimum in dahdi_tool. Ifyour PRI or othertelco equipment is already cabled and the Fonebridge has been updatedwith the proper configuration parameters then you should see an OKstate in dahdi_tool.

6. Download and Install libpri and Asterisk 1.67. Edit /etc/dahdi/system.conf8. Edit redfone.conf


dahdi installation and configuration

Documents