<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Matthew Fredrickson a écrit :Well, I am quite happy with libss7, no
real reasons to change for me.<br>
But, I can't be sure and this is another problem, since I use
chan_dadhi, I have big echo problems, it wans't the case with zaptel.<br>
I am buying E1 cards with hardware echo canceller to avoid this problem
because I didn't find any solution with Dahdi.<br>
Tuning by rxgain/txgain makes the echo a bit better, but an echo still
remain.<br>
<br>
Dunno if I am the only to have that problem.<br>
<br>
Kind regards,<br>
<br>
Olivier<br>
<blockquote cite="mid:48CA8644.9030400@digium.com" type="cite">
<pre wrap="">Krzysztof Drewicz wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Oakland, Alan napisa³(a):
</pre>
<blockquote type="cite">
<pre wrap="">To further clarify, libss7 is developed by Digium, where chan_ss7 is
developed by a company called Dicea, more information on chan_ss7 can be
found on it's voip-info page
<a class="moz-txt-link-freetext" href="http://www.voip-info.org/wiki/view/Asterisk+ss7+channels">http://www.voip-info.org/wiki/view/Asterisk+ss7+channels</a>
</pre>
</blockquote>
<pre wrap="">Also:
chan_ss7 by Dicea has a cluster/failover capability where you have one
SPC for you asterisk (one point code in SS7, just like one IP), and if
used with 2 hosts, each one having at least one E1 to your SS7 peer ,
then (if your peer understands changeover and emergency changeover
messages it's 99.99%) one of your asterisk machines could do a reboot,
and a second one will go on.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">libss7 has (am i correct) no official support, in other words: you
cannot expect Digium Support (even with Asterisk Premium Edition) to
solve your problems with libss7, they will help, but the response time
etc... for ss7 is not in the contract.
</pre>
</blockquote>
<pre wrap=""><!---->
Regarding the current "official" support channel for libss7, this is
certainly no worse off than the lack of an official support channel for
chan_ss7. And with libss7 you get the benefit that the original author
(myself) is still actively maintaining and supporting it, as well as
working with many of you in the community with any problems you run into.
There are still some policies and decisions we have to make about how
we're going to officially support libss7 though. I believe that when we
make the official release of Asterisk-1.6.0 (Open source) installation
support will be something you can call support about (although it'll
probably end up coming back to me for a while, while the technical
support staff are learning how to support it).
With regards to BE, I was asked a while ago about including libss7
support in it. At the time (this was probably a year or year and half
ago), I thought it wouldn't be a good idea, due to maturity issues. Now
though, I feel that libss7 is to the point where I would feel good about
putting it in BE since, IMHO, it has been proven as far as stability and
performance goes.
If there is enough interest in getting support for libss7 (i.e. people
would be willing to buy copies of it to use with libss7) I can look into
what it would take to get it in.
--
Matthew Fredrickson
Digium, Inc.
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a>--
asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-ss7">http://lists.digium.com/mailman/listinfo/asterisk-ss7</a>
</pre>
</blockquote>
</body>
</html>