<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Dear Matthew,<br>
<br>
I updated my asterisk and libss7 to the latest trunk version and
signaling now is ok.<br>
<br>
I also updated my SS7 OPC and EC patches on bug 11779 (including new
CQM/FAA events and block_cics function).<br>
<br>
Thanks.<br>
<br>
Daniel<br>
<br>
<br>
Matthew Fredrickson escreveu:
<blockquote cite="mid47950E37.9000608@digium.com" type="cite">
<pre wrap="">Daniel Bichara wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear Matthew,
Should this new release fix the crash problem I reported on bug ID 11805
(running 2 signaling links)?
</pre>
</blockquote>
<pre wrap=""><!---->
I'm not sure. I did not see anything in your back trace that directly
linked it to libss7, making me wonder if it might be an Asterisk bug,
but I still have not made any conclusions yet.
Matthew Fredrickson
</pre>
<blockquote type="cite">
<pre wrap="">[]'s
Daniel
Matthew Fredrickson escreveu:
</pre>
<blockquote type="cite">
<pre wrap="">Daniel Bichara wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear,
Running 2 signaling links on the same linkset connected to different DPC
produces wrong SLS on STD_TEST and second link did not align:
- Port#1 (PC 1000) <- (quasi-associated) -> SPS 1201
asterisk (PC 333) -+
- Port#2 (PC 2000) <- (quasi-associated) -> SPS 1202
SPS 1201 and 1202 are quasi-associated mode SPS. Signaling channels are
on channel 16 on link #1 and #2. SPS 1201 and 1202 are adjacent PC.
During alignment tests, asterisk sends MSU message (STD_TEST) with SLS=1
to PC 1202. Although, to this PC, SLS should be zero (the same as 1201)
because they are running different PCs.
If we run second PC as a different linkset (linkset #2), everything goes
fine but we can not start calls on CICs from the other link.
We are patching libss7 and chan_zap to relate CIC's (PVTs) to the OPC
(333 this case) and not to the linkset. This way, the 2 different
linksets can communicate to the CIC on both links because they run same
OPC (333).
Any comment or feedback is appreciated.
</pre>
</blockquote>
<pre wrap="">I just put in a provisional fix related to this in libss7. The problem
is that when I did the linkset association in libss7, I had assumed that
when hooking up via multiple redundant links, that they would be within
the same linkset and simply have different SLC codes.
To support this configuration in libss7 you must update to the most
recent version which provides a way to support this type of
configuration. The way it is setup in zapata.conf is the same as if
they were both in the same linkset (so probably the same configuration
as you had before).
</pre>
</blockquote>
<pre wrap="">
------------------------------------------------------------------------
_______________________________________________
--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>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
<br>
</body>
</html>