Open Source Sip: PfSense>OpenSBC ...

Print

Up to Discussions in OpenSBC

This Question is Not Answered

1 "correct" answer available (5 pts) 2 "helpful" answers available (1 pts)

4 Replies Last post: Nov 13, 2009 11:59 AM by mparadis

mparadis

95 posts since
Oct 2, 2009

Nov 12, 2009 5:39 PM

PfSense>OpenSBC

I had a setup that Mike Picher helped me with which was vyatta with opensbc on it.

What I liked about that setup was that incomingconnections were balanced across the two WANs which I have. This put our two WAN connections to good use, while also giving us some redundancy. There were problems however, which we had not resolved and not being able to wait any more, I decided to try a parallel setup using pfsense only to the pbx which worked right off the bat.

I think the problems were related to having multiple gateways. The two vyatta servers with opensbc on them each had a public IP on the WAN side connected direcly to the router and the private side was a 192.168.1.x IP but we have a juniper firewall which is actually handling that 192.168.1.x network.

Anyhow, the pfsense setup is working fine but now I need that redundancy again but without the gateway problems on the LAN side.

What are my options? Could I build two stand alone opensbc servers, each talking with one of the pfsense servers and the other side talking with my pbx. If this is ok, then how would I deal with the issue of having multiple gateways? In effect, the only servers/IP's that pfsense would see would be from the opensbc servers. The opensbc servers would only need to talk with my pbx. However, I would need access to the opensbc servers on the lan side, in order to maintain them.

If all of this soudns confusing, perhaps I'm not explaining it well but it's a start and am more than willing to give additional input.

Thanks.

Mike

mparadis

95 posts since
Oct 2, 2009

1. Nov 13, 2009 12:11 AM

in response to: mparadis

Re: PfSense>OpenSBC

Rather than start another thread, here's a related question about installing opensbc on Centos.

Are there any special dependancies which need to be installed on centos in order to gain all opensbc features. I've pulled thesource using cvsand am able to configure without errors but am not sure if I need anything else.

mpicher

40 posts since
Dec 28, 2008

2. Nov 13, 2009 3:47 AM

in response to: mparadis

Re: PfSense>OpenSBC

The one question I have to get this working is can OpenSBC be run on a single ethernet interface or do we still need an inside and outside?

Mike

mparadis

95 posts since
Oct 2, 2009

3. Nov 13, 2009 11:54 AM

in response to: mpicher

Re: PfSense>OpenSBC

Here's what I've done, I hope I got the steps right.

First, after building it (below), I fired it up. I do see it running in the tasks but there's no port 9999 available.

root 14892 0.0 0.1 33164 3868 pts/0 Sl 10:45 0:00 ./opensbc -d -p /var/run/opensbc.pid -H 65536 -C 1024000
---

The following will compile OpenSIPStack and OpenSBC
(instead of make bothnoshared, you may want to do a 'make clean' and 'make
install')

So does this mean in place of 'make bothnoshared' for each?

1. su
2. cd /usr/src/opensipstack
3. chmod +x ./configure
4. ./configure --enable-gpllibs

5. make bothnoshared

If I replace the above with 'make clean; make install', I get;

make install

make: *** No rule to make target `install'. Stop.

Of course, I had not run 'make' yet so figure there's nothing to install so ran 'make' on
it's own first, then 'make install' works.

6. cd ../opensbc
7. chmod +x ./configure
8. ./configure --enable-gpllibs

9. make bothnoshared

Did the same as above and it compiled, completed.

10. make distrib

Completed.

Relocate Executables
Copy the executables to a more acceptable location on the server.
1. cp /usr/src/opensbc/distrib/* /usr/local/bin

Done.

Fix Shell Scripts

Done.

mparadis

95 posts since
Oct 2, 2009

4. Nov 13, 2009 12:31 PM

in response to: mparadis

Re: PfSense>OpenSBC

Ooops, new server, iptables turned on by default. Works. Waiting on input about running opensbc stand alone now. I also forgot to mention that I built this as a VMWARE ESX guest for testing. I can put a physical box together if we really should be using a two NIC server.

Go to original post