I’ve read the README files for both and they appear to be two different approaches for implementing ss7 functionality in Asterisk as they have similar configuration parameters that you would expect for implementing ss7 links. Is this correct? I did some additional reseraching over at voip-info.org and this is the impression I get. I have used libss7 successfully but came across chan_ss7 and was curious as to which is a better platform to start with.
I’ll have to experiment in the near future, but does anyone have experience with chan_ss7 and does it support a greater set of ISUP messages compared to libss7?
chan_ss7 has more life years, when i started work on asterisk - ss7 3 years ago, libss7 was not mature enough. i used chan_ss7 and it worked for me. Later on i have seen much improvements in libss7. but i have not used it at all. you can see my work on itdiscussiongroup.com/2007/categ … 7-traffic/
Let me know if you need any help.
I’ve noticed that chan_ss7 has its own configuration file called ss7.conf to set up the signaling links, voice channels, signaling channel, etc. In contrast, libss7 allows this to be built into chan_dahdi.conf. The two SS7 links I’ve set up before were fully associated links so the signaling and data channels were parallel, i.e. took the same path. I did not break it up into signaling links toward an STP as I had no STP to test that functionality. I’m curious how this is done in libss7, and perhaps it is done much the same way as it is in ss7.conf but I’ll have to research that a bit more. If you have input on that I would appreciate hearing from you! I do plan on testing this with an STP in the future but I can foresee running out of spans on my Digium TE420 4 port E1/T1 card quickly. I can at least run the two data/speech trunks to spans 1 and 2 of the E1 card and the signaling link from the STP to span 3 and have a small scale set-up that more closely simulates a real world set-up. Thanks in advance for any input!