<div dir="ltr">Easiest way to achieve this is simply to change the request URI as the SIP travels through the "middleman" instance:<div><br></div><div>e.g.</div><div><br></div><div>$ru = "sip:"+$rU+"@main-opensips.server:5060";</div><div>t_relay();</div><div><br></div><div>If you want to keep the request uri unchanged, you can change the destination instead:</div><div>$du = "sip:main-opensips-server:5060";</div><div>t_relay();</div><div><br></div><div>And to do it in a more managed fashion, you could use the dispatcher module which lets you change the IP of the "main" server on the fly should you wish to.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 2 March 2015 at 15:59, Mert Yazgart <span dir="ltr"><<a href="mailto:efes9999@hotmail.com" target="_blank">efes9999@hotmail.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 dir="ltr">We would like to have some of the sip clients connect to a "middleman" opensips instance which will relay the SIP requests to our "main" opensips server (after some security related filtering) and relay the responses from the "main" server back to the clients.<br><br>There will be no NAT involved. RTP doesn't need to be relayed, just the SIP.<br><br>What is the simplest way of achieving this on the opensips instance in the middle? t_relay with an IP specified? Other options? Does this need to be stateful?<br><br>Thanks.<br> </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></div>