Welcome to FreeSWITCH! Comments inline...<br>-MC<br><br><div class="gmail_quote">On Wed, Feb 8, 2012 at 3:50 PM, Josh <span dir="ltr"><<a href="mailto:mojo1736@privatedemail.net">mojo1736@privatedemail.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am considering using FreeSWITCH as a replacement of our (rather<br>
crappy, outdated and buggy) sip proxy system, and have the following<br>
system setup on the server:<br>
<br>
* eth0 faces the external Internet interface, *but* it does not have a<br>
public IP address (it has a private one given to it by my ISP's DHCP<br>
server);<br>
* eth1 faces our internal network (say <a href="http://10.1.1.0/24" target="_blank">10.1.1.0/24</a>);<br>
* tun0 serves all mobile smartphones and connects to the internal<br>
network (it has a different ip range, say <a href="http://10.1.2.0/24" target="_blank">10.1.2.0/24</a>) - they are all<br>
connected via the Internet using OpenVPN;<br>
<br>
I would like to configure FreeSWITCH as a local registrar and ask it to<br>
handle internal calls between ourselves (eth1<->tun0). I would also like<br>
to use one external VOIP provider to which FreeSWITCH registers on<br>
startup. This also needs to have all NAT-related issues dealt with as<br>
well (hopefully by FreeSWITCH, if possible). I would also need to<br>
emphasise that FreeSWITCH *cannot* just listen on any (public-facing)<br>
interface port in order to receive calls from the external provider,<br>
simply because my ISP won't allow it (i.e. I can't just "open" that port<br>
and hope that someone will contact me - the connection needs to be<br>
initiated by our server for incoming call to get routed through).<br></blockquote><div>But calls will be sent to FreeSWITCH by some device, correct? If it's good old-fashioned SIP then FreeSWITCH will handle it just fine.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The purpose of registering this external account is so that both the<br>
smart phones (tun0) and the internal net (eth1) users could use this<br>
account to make external calls (starting with "0"). Obviously, I need<br>
these calls to be routed properly via the external VOIP account. In<br>
addition to that, I would also need to receive calls from that external<br>
account to a nominated internal one (say on extension 20).<br>
<br>
Could this be done relatively easily in FreeSWITCH?<br></blockquote><div>"Relatively?" Of course! It's relatively easy for someone with some experience. I highly recommend that you ask <a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a> for professional assistance if you are not comfortable doing this all by yourself.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
A question about binding: in order to be able to use both tun0 and eth1<br>
interfaces so that FreeSWITCH serves the calls from both eth1 and tun0<br>
devices/networks, is it possible to instruct it to bind on different IP<br>
addresses (on tun0 and eth1 respectively) in order to serve calls<br>
to/from these networks? I do *not* wish to bind to 0.0.0.0 - just use<br>
the interfaces I am interested in - tun0 and eth1 in my case.<br></blockquote><div>Yes, FreeSWITCH can bind to multiple interfaces. In FreeSWITCH lingo
that would mean that you set up a separate SIP profile for each
interface. (In fact, you can have more than one SIP profile on a given
interface since the profile is a unique combo of IP addr and port
number.)<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
If all of the above is possible, do I have to mess about and configure<br>
SNAT/DNAT separately and use sip kernel module "helpers" etc (I *do*<br>
have the routing set up properly though - that I am sure works 100%) or<br>
is FreeSWITCH perfectly capable of setting it all up for me?<br></blockquote><div>"Some assembly required." :D<br>FreeSWITCH can do some stuff for you, but you definitely need to make sure that your NAT is not behaving badly, like having a SIP ALG.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
One final query: is there a decent distribution source package of<br>
FreeSWITCH, which I could take and then use it to build a binary package<br>
(I use Fedora on all of our machines). I need this, because all of our<br>
images are built using the rpm packaging system and I cannot just "fetch<br>
the latest git", compile and install FreeSWITCH - I need it packaged, so<br>
that the image builder picks it up and distributes it to the machine<br>
concerned. I checked the SUSE repository (as instructed on the<br>
FreeSWITCH wiki), but found 2 packages, both of which cannot be build<br>
due to errors!<br></blockquote><div>I'll have to defer to Ken Rice on this one. I know he's working on RPMs for FreeSWITCH but I think it's all RedHat right now.<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Many thanks in advance!<br>
<br><br></blockquote></div>