<span class="Apple-style-span" style="border-collapse: collapse; ">Hi Julien,<div><br></div><div>For such scenarios you would need a B2BUA ( I personally use B2bua.org but Yate, Freeswitch, Asterisk can do it too).</div><div>
One more concern with carrier traffic would be the SDP body, which can reveal information about the originator too.</div><div><br></div><div>Cheers,</div><div>DanB</div></span><br><div class="gmail_quote">On Wed, Jul 1, 2009 at 7:08 AM, Julien Chavanton <span dir="ltr"><<a href="mailto:jc@atlastelecom.com">jc@atlastelecom.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<div><font face="Verdana" size="2">Hi, I have a business usage security concern.</font></div>
<div> </div>
<div><font face="Verdana" size="2">If we take this scenario :</font></div>
<div><font face="Verdana" size="2"></font> </div>
<div><font face="Verdana" size="2">carrierA --SIP--> carrierB --SIP--> carrierC</font></div>
<div><font face="Verdana" size="2"></font> </div>
<div><font face="Verdana" size="2">CarrierB may not want carrierC to find out about carrierA (IP address)</font></div>
<div><font face="Verdana" size="2"></font> </div>
<div><font face="Verdana" size="2">I beleive "record-routing" and "via header" can provide unwanted information,</font></div>
<div><font face="Verdana" size="2">any suggestion/options on how we can deal with such requirements using a SIP proxy as openSIPS ? </font></div>
<div><font face="Verdana" size="2"></font> </div>
<div><font face="Verdana" size="2">Regards,</font></div>
<div><font face="Verdana" size="2">Julien</font></div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>