<div>Hi,</div>
<div> </div>
<div>I think its the best solution because handling complexity of distributed MTP3 (specially network part) is a mess, even giant class 4/5 switch makers hadn't done it.</div>
<div> </div>
<div>Mathew, by "like they do with a real MTP2 link, except it's just over an IP based protocol" you mean M2UA or you have your own protocol?</div>
<div> </div>
<div>Regards.</div>
<div>--</div>
<div>M. Shokuie Nia<br><br></div>
<div class="gmail_quote">2009/1/14 Matthew Fredrickson <span dir="ltr"><<a href="mailto:creslin@digium.com">creslin@digium.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">Mehdi Shirazi wrote:<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>> For multiple SGs to each ASP support am I correct :<br>> "with M3UA we need one point code for each SG but with M2UA we need only one point code (assigned in ASP ?) and it seems implementing M2UA is easier than M3UA" (leaving MTP3 and ISUP part unchanged)<br>
<br></div>Like I said, this is basically what I'm doing. The way the links look<br>to the MTP3 on each box is exactly like they do with a real MTP2 link,<br>except it's just over an IP based protocol.<br><font color="#888888"><br>
Matthew Fredrickson<br>Digium, Inc.<br></font>
<div>
<div></div>
<div class="Wj3C7c"><br>_______________________________________________<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>