<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I used another scheme. No editional socket. Spce will send packets through private interface. But all SIP packets will have public IP. So, on another host you need a route to public interface through private.<br><br><br></div><div><br>14 окт. 2014 г., в 15:06, George Mason <<a href="mailto:george.mason@xoomtalk.com">george.mason@xoomtalk.com</a>> написал(а):<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div class="moz-cite-prefix"><font size="-1">Hi Andrew<br>
<br>
Many thanks, unfortunately in this case the provider will do
nothing over the public network, so both SIP signalling and RTP
need to be sent over the private interface. On balance I think I
will wait for mr3.5.1 as that sounds like it addresses the
problem with the least messing about.<br>
</font>
<div class="moz-signature">
<font style="font-family: Arial;" face="Arial" size="2">
<br>
<font color="7b7979" size="2"><b>George Mason</b></font><b><br>
<font color="62a1d6" size="2">Technical Director</font></b>
<br>
<br>
<table border="0">
<tbody>
<tr>
<td valign="middle" width="235"><a href="http://www.xoomtalk.com" target="_blank"><xoomtalk-email-logo.jpg></a> </td>
<td><font style="font-family: Arial;" font="" color="#7b7979" face="Arial" size="2"><b> Tel:<br>
Mob:<br>
Fax:<br>
Web:</b> </font></td>
<td><font style="font-family: Arial;" color="#62a1d6" face="Arial" size="2"> +44 (0)1273 900090<br>
+44 (0)7966 403353<br>
+44 (0)1273 900091<br>
<a style="text-decoration:none; color:#62a1d6" href="http://www.xoomtalk.com/" target="_blank">www.xoomtalk.com</a>
</font></td>
</tr>
</tbody>
</table>
</font></div>
On 14/10/14 13:54, Andrew Pogrebennyk wrote:<br>
</div>
<blockquote cite="mid:543D1D0E.6020407@sipwise.com" type="cite">
<pre wrap="">Hi George,
you should configure that interface as extra_socket in config.yml:
<a class="moz-txt-link-freetext" href="https://www.sipwise.com/doc/mr3.4.2/spce/ar01s05.html#_extra_sip_listening_ports">https://www.sipwise.com/doc/mr3.4.2/spce/ar01s05.html#_extra_sip_listening_ports</a>
After that select that socket in the outbound_socket peer preference.
Please note that the rtpengine is still going to use the default
interface. This is not a problem I guess if the carrier is able to send
RTP traffic to the internet.
If not you need to look into the new rtpengine interface bridging
feature. It's available and documented on
<a class="moz-txt-link-freetext" href="https://github.com/sipwise/rtpengine">https://github.com/sipwise/rtpengine</a> and will be included in mr3.5.1
that will be released within a week. The integration in kamailio config
is rather trivial.
Andrew
On 13/10/14 15:23, George Mason wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I have a situation where I need to connect a separate interface on a
SPCE box with a private IP, to a carrier that will only accept calls
down this channel and from that IP. So basically I need a setup where
the server is accessible on its public IP on one interface, but can also
communicate on its private interface, with a route to the supplier's
network.
What will need to be done on SPCE to make this work? I'm fine with the
layer 3 aspect of this but not sure about the changes needed in the
application.
Thanks in advance
George
</pre>
</blockquote>
<pre wrap=""></pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Spce-user mailing list</span><br><span><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a></span><br><span><a href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a></span><br></div></blockquote></body></html>