After much head banging in bringing up an SS7 link with SAM support, I am documented what worked here.
Firstly, what is SAM support? One end of an SS7 link initialises a new call by sending an Initial Address Message (IAM). All SS7 software stacks support this and usually it’s enough. One case where it’s not enough is when one wants to address a phone number with more than the E.164 standard max length of 16 Â (usually to pass additional information tacked on the start, end of or even replacing an A or B number). In this scenario, SS7 uses a Subsequent Address Message (SAM)Â to send the additional digits. Most / all mainstream Asterisk SS7 software stacks do not support this.
The platform and software used is as follows:
- Ubuntu 10.04 LTS standard CLI install;
- dahdi-linux-complete-2.4.0 from the archives (direct link);
- a patched version of libss7 supporting SAM via SVN (see below);
- a patched version of chan-dahdi via SVN (see below);
- Asterisk 126.96.36.199 from the archives (direct link);
- Asterisk Addons 188.8.131.52 from the archives (direct link);
- Sangoma Wanpipe 3.5.24 (direct link).
Yes, I know some of the above areÂ obsolete. Unfortunately it’s what’s required for everything to play nicely together. And, guess what, it works!
Before You Start
Ensure you have all the necessary packages for building the packages:
apt-get install build-essential libnewt-dev subversion \ libsqlite3-dev libsnmp-dev bison libtool flex \ autoconf2.13 libmysqlclient-dev
You can assume the working directory isÂ /usr/local/srcÂ in the following.
Download and extract dahdi-linux-complete into /usr/local/src. Then, in the same directory, create some symbolic links:
ln -s dahdi-linux-complete-2.4.0+2.4.0/linux dahdi-linux ln -s dahdi-linux-complete-2.4.0+2.4.0/tools dahdi-tools
Now build dahdi-linux:
cd dahdi-linux make make install
Now move onto dahdi-tools:
cd dahdi-tools ./configure make menuconfig # (and select tools or accept defaults) make make install make config
There is a patched version of Digium’s libss7 referred to as Attila’s libss7 available via SVN. Download and install it:
svn co https://observer.router.hu/repos_pub/libss7/trunk alibss7 cd alibss7 make make install
Download and extract the Asterisk 184.108.40.206 package reference above.
Now this next bit is very important and easy to missÂ – you also need a patched version of chan_dahdi.c that is compatible with the patched version of libss7. This is also available from SVN:
svn co https://observer.router.hu/repos_pub/chan_dahdi/trunk achan_dahdi
Then copy it to your Asterisk source:
cp achan_dahdi/chan_dahdi.c asterisk-220.127.116.11/channels/chan_dahdi.c
Now continue with the Asterisk installation:
./configure make menuconfig make make install make samples make config
Install Asterisk Addons (optional)
Download and unpack the above referenced add ons package and build and install:
cd asterisk-addons-18.104.22.168 ./configure make menuconfig make make install make samples
I’m using one of Sangoma’s E1 / T1 interface cards and so I need Wanpipe also. I’m using version 3.5.24 and preceed as follows after unpacking:
cd wanpipe-3.5.24./Setup install
During the install, follow these prompts:
- select option 2 => Asterisk/Dahdi Support;
- enter path /usr/local/src/dahdi-linux (for Zaptel path prompt);
- select defaults for everything else;
- you DO want to install start-up scripts;
- you DOÂ to configure wanpipe devices for DAHDI;
- you DO wantÂ to generate /etc/asterisk/chan_dahdi.conf and:
- select E1 / T1 as appropriate;
- select line framing and encoding;
- choose clock source;
- selectÂ Zaptel/Dahdi – PRI CPE as signalling;
- selectÂ National ISDN 2 as switch type;
- do not enable hardware DTMF detection;
- use all channels;
- select dial plan context as appropriate;
- and continue for other ports as necessary;
- finally, chooseÂ Save cfg:Â Stop Asterisk & Wanpipe now
- you wouldÂ like wanrouter to start on system boot;
- and you wouldÂ like to execute ‘dahdi_cfg’ each time wanrouter starts.
We now need to set various options in Wanpipe, Dahdi and Asterisk for SS7 as it’s PRI/ISDN by default.
Edit allÂ /etc/wanpipe/wanpipeX.conf files asÂ necessaryÂ and change:
Â TDMV_DCHAN Â Â Â Â Â Â Â = 16
TDMV_DCHAN Â Â Â Â Â Â Â = 0
Now editÂ /etc/dahdi/system.confÂ and change (for example):
span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 echocanceller=mg2,1-15,17-31 hardhdlc=16
span=1,1,0,ccs,hdb3,crc4 bchan=2-31 echocanceller=mg2,2-31 mtp2=1
which of course assumes signalling is on channel 1. If you have voice only links, you might need something like:
Lastly, we need to configure Asterisk. Replace lines such as:
;Sangoma A102 port 1 [slot:4 bus:5 span:1] switchtype=national context=from-pstn group=0 echocancel=yes signalling=pri_cpe channel =>1-15,17-31
with an appropriate configuration.Â Mine follows below with some edits andÂ some important notes at the end:
;Sangoma A102 port 1 [slot:4 bus:5 span:1] switchtype=national context=from-pstn group=0 echocancel=yes signaling=ss7 ss7type=itu ss7_called_nai=dynamic ss7_calling_nai=dynamic ss7_internationalprefix=00 ss7_nationalprefix=0 ss7_subscriberprefix= ss7_unknownprefix= linkset=1 pointcode=1 adjpointcode=2 defaultdpc=3 networkindicator=national_spare cicbeginswith=2 channel=2-31 sigchan=1
- SetÂ pointcode, adjpointcode and defaultdpcÂ as appropriate;
- setÂ networkindicatorÂ as appropriate and ensure it matches the other end (you can see what youâ€™re being sent and what youâ€™re sending viaÂ ss7 debug;
- cicsbeginwithÂ is normally 1 but the telco on my end are starting at 2 â€“ this wasÂ groping in the darkÂ diagnostics and issues such as no audio, CICs not in service when both sides claim they are, etc may point to misaligned CICs;
- make sure you have configuredÂ from-pstnÂ or the appropriate context in yourextensions.conf.
Confirming Your Link Is Up
Now start wanrouterÂ (/etc/init.d/wanrouter start); dahdiÂ (/etc/init.d/dahdi start);Â and AsteriskÂ (/etc/init.d/asterisk start). You should see your link come up via logs available with theÂ dmesgÂ command. Launch the Asterisk console and check the status of your links:
ast-deg1-1*CLI> ss7 show cics 1 CIC DPC DAHDI STATE BLOCKING 2 3 2 Idle 3 3 3 Idle 4 3 4 Idle 5 3 5 Idle 6 3 6 Idle 7 3 7 Idle 8 3 8 Idle 9 3 9 Idle 10 3 10 Idle 11 3 11 Idle 12 3 12 Idle 13 3 13 Idle 14 3 14 Idle 15 3 15 Idle 16 3 16 Idle 17 3 17 Idle 18 3 18 Idle 19 3 19 Idle 20 3 20 Idle 21 3 21 Idle 22 3 22 Idle 23 3 23 Idle 24 3 24 Idle 25 3 25 Idle 26 3 26 Idle 27 3 27 Idle 28 3 28 Idle 29 3 29 Idle 30 3 30 Idle 31 3 31 Idle
You should now be okay to make test calls.
Do You Need Professional Support / Consultancy?
While I will try to respond to comments and questions on this blog, I donâ€™t have the time to provide one on one assistance pro-bono. Professional consultancy on Asterisk and SS7 is available worldwide through my company,Â Open SolutionsÂ withÂ contact details here.
For posterity, I have addedÂ Domjan Attila patched libss7 and chan_dahdi to GitHub: