Switching to 1.6.0 did the trick. I tried to run 1.6.0.28 but I had the no audio issue. I'm not sure what you mean by there is no 1.6.0. I found it here:<br><br><a href="http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-addons-1.6.0.tar.gz">http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-addons-1.6.0.tar.gz</a><br>
<br>You're welcome to get with me out of band to see my specific setup. I am willing to post the traffic of the failing call with my asterisk 1.6.2 stack if anyone is interested.<br><br>-stephan<br><br><div class="gmail_quote">
On Tue, Oct 5, 2010 at 9:20 AM, Kevin P. Fleming <span dir="ltr"><<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 10/05/2010 09:02 AM, Stephan Ellis wrote:<br>
> Any specific point version of 1.6.0 i should use? Or just 1.6.0?<br>
<br>
</div>If the underlying problem is, as your switch technician suggests, lack<br>
of response to a particular SS7 message, then going back to an older<br>
version of Asterisk is not going to help. I know the author of the<br>
previous reply was trying to be helpful, but he posts the identical<br>
response to every thread where people are having issues with Asterisk<br>
and SS7... that does not mean he's actually analyzed the problem and<br>
knows that it will be resolved by using 1.6.0.x (there is no "1.6.0").<br>
<br>
Since you've determined that the problem only occurs when your Asterisk<br>
box is placing calls to specific remote destinations through your SS7<br>
switch, have you tried any other SS7 clients off that switch calling the<br>
same destinations? I know you've mentioned that you have an additional<br>
Asterisk box using ISDN PRI to that switch, but since that's a different<br>
protocol it's not really going to help (except to verify that your SS7<br>
switch does have a functional audio path between it and the remote<br>
destination).<br>
<br>
Most likely the message(s) involved here are related to some sort of<br>
SS7/ISDN (or SS7/PSTN) interworking, and chan_dahdi/libss7 just haven't<br>
taken those into account yet. In order to be able to debug the issue,<br>
you're going to have to post a debug log that shows the SS7 traffic<br>
being sent and received for this failing call, so that people who<br>
understand the protocol can try to figure out what is going wrong.<br>
<br>
--<br>
Kevin P. Fleming<br>
Digium, Inc. | Director of Software Technologies<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
skype: kpfleming | jabber: <a href="mailto:kfleming@digium.com">kfleming@digium.com</a><br>
Check us out at <a href="http://www.digium.com" target="_blank">www.digium.com</a> & <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a><br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-ss7 mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-ss7" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-ss7</a><br>
</div></div></blockquote></div><br>