<div>Hi folks,</div>
<div> </div>
<div>Im not sure if its the best choice but i think it might be a standard way to terminate a sig channel in one box and make it talk MGCP to other boxes. As far as i could remember Mathew was after adding MGCP to chan_zap sometimes before. Whats your opinion guys?</div>
<div> </div>
<div>Regards.</div>
<div>--</div>
<div>M. Shokuie Nia<br><br> </div>
<div><span class="gmail_quote">On 13/01/2009, <b class="gmail_sendername">Matthew Fredrickson</b> <<a href="mailto:creslin@digium.com">creslin@digium.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Amish Chana wrote:<br>> Hi,<br>>>> Hi Matthew,<br>>>><br>>>> In this case, if the point code is distributed across more than one box,<br>
>>> how do you manage SS7 link (and linkset) failures, where the messages<br>>>> need to be re-routed via another link (or linkset) during failure scenarios?<br>>> Well, to have a fully redundant setup, you would have separate boxes<br>
>> terminating each signaling link. These routing machines can masquerade<br>>> ISUP traffic over to other machines via IP protocol based links. Each<br>>> of these IP connected boxes has an IP link to each box with a physical<br>
>> signaling link. If a machine with a physical link goes down, it reports<br>>> it to the IP links that are hooked up to it and the machines using those<br>>> IP links use their alternate IP links instead of that link, providing<br>
>> for redundancy in times of link failure.<br>> Have you looked at the RSerPool<br>> (<a href="http://www.ietf.org/html.charters/rserpool-charter.html">http://www.ietf.org/html.charters/rserpool-charter.html</a>). It may be one<br>
> method of addressing these requirements.<br><br>I actually have seen a number of different projects like this for<br>cluster distribution, management, and synchronization.<br><br>><br>>> There are going to be other problems to think about as well, but I think<br>
>> that the basic logic is sound and will work.<br>>><br>>> I actually just got masqueraded ISUP messages passing correctly back and<br>>> forth over IP, but I still have some technical hurdles as far as what to<br>
>> do as IP links go in and out of service. This list will definitely know<br>>> what I have something I'm interested in testing :-)<br>> What about using M3UA to address the requirement of having one point<br>
> code across more than one box? The Routing Key registration method<br>> provided for in M3UA will allow each box to register the CIC values for<br>> which they want to receive ISUP messages. See the example architecture<br>
> with M3U1 below. Box1 (ASP1) would register a routing key for CIC 1..93,<br>> Box2 (ASP2) would register a routing key for CIC 94..186, and Box3<br>> (ASP3) would register a routing key for CIC 187..279. The E1s/T1s from<br>
> each SEP to each Box/ASP would still exist, however we would terminate<br>> the SS7 on a Signalling Gateway and route M3UA between the SG and each<br>> ASP. (The example below shows one SG but at least 2 will be necessary).<br>
><br>> ----<br>> / \<br>> /---+ ASP1 |<br>
> / \ /<br>> SG / ----<br>> +---------------+ /<br>> | | |---/ ----<br>
> +-------+ SS7 links | | | / \<br>> | SEP +--------------| SS7 Ntwk.|M3UA+-----------+ ASP2 |<br>> +-------+ | | | \ /<br>
> | | | ----<br>> | | |---\<br>> +---------------+ \ ----<br>> \ / \<br>
> \----+ ASP3 |<br>> \ /<br>> ----<br>
<br>Although I am not using true M3UA and sigtran protocols right now,<br>conceptually, this is almost exactly what we are doing, except we will<br>support multiple SGs to each ASP as well.<br><br>Matthew Fredrickson<br>Digium, Inc.<br>
<br>_______________________________________________<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">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">http://lists.digium.com/mailman/listinfo/asterisk-ss7</a><br></blockquote></div><br>