OPENSER Integration –- USD$200.00
-
Okay I'll go with OpenSER for now as requested by sipster. Cause you stated that this is a drastically needed package (or feature even), I'll do a FreeBSD port of OpenSER 1.1 if someone is willing to put another USD $200 on top of the initially offered USD $200.
I'll have to setup a pfSense RELENG/1.0.1 developement system, because if I understood you correct you are going to use OpenSER on a pfSense 1.0.1 RELEASE system (correct me if I am wrong). So anybody interested in such a package/feature has some time to think about the additional USD $200.
OpenSER pfSense package details (as requested):
-
One HTML textarea field to be able to edit the OpenSER config file
-
One HTML textarea field to display OpenSER's log file (or an extra tab at Status->System logs)
-
Possibility to start/stop OpenSER at Status->Services
-
One HTML text input field that allows to provide a custom listen port on which OpenSER will listen on
-
FW rules are getting added on the fly if activating the package
Regards
Daniel S. Haischt -
-
That is correct. I will be using a 1.0.1 RELEASE system.
Your package checklist is exactly what I am looking for. Go for it.
-
openser 1.1 port is at:
http://openser.cvs.sourceforge.net/openser/sip-server/packaging/freebsd/?pathrev=rel_1_1_0 -
Great!
Daniel,
Does this help you integrate the OpenSER 1.1 package with PfSense?
I definitely prefer the 1.1 package. -
Daniel,
Does this help you integrate the OpenSER 1.1 package with PfSense?
I definitely prefer the 1.1 package.Yes, I guess I will move the port files over to the pfSense port repo, cause as it seems some files are still missing. But it's a beginning…
Regards
Daniel S. Haischtp. s. If the OpenSER 1.1 FreeBSD port author reads this: Please submit your port to the official FreeBSD ports repository ;)
-
extra, extra ;-)
regarding your p.s.
OpenSer port author: Jesus Rodriguez jesusr@voztele.com- Torsten/jesusr@voztele.com -
How are we doing on this one?
I, too, need either siproxd or better yet OpenSER so SIP will work reliably behind NAT. Many SIP clients do figure out how to work behind NAT but occasionally calls have one-way audio and such and we can't really rely on their built-in NAT traversal when dealing with business-class clients whose phones need to work reliably all the time.
-
@tog:
How are we doing on this one?
I, too, need either siproxd or better yet OpenSER so SIP will work reliably behind NAT. Many SIP clients do figure out how to work behind NAT but occasionally calls have one-way audio and such and we can't really rely on their built-in NAT traversal when dealing with business-class clients whose phones need to work reliably all the time.
Great! So commit to the bounty and raise the bar. I am not working on this one but this entire bounty thing was meant for MULTIPLE parties to show their support with their checkbook.
-
I'll work on this bounty! I can assure one think and I think any other dev can too: I won't spend my money on junk food or on a cruise or whatever but on test hard- and software and on books which may help to improve the pfSense product.
So if you need a particular feature too, start contributing money to the particular bounty. The money won't be wasted!!!
Cheers
Daniel S. Haischt -
Ok, I just wanted to put the question out and see how much you were looking for to get it done.
You said earlier an additional $200 would be enough for you to get going, is that still the case?
-
@tog:
You said earlier an additional $200 would be enough for you to get going, is that still the case?
Yes, including OpenSER 1.1 support.
Regards
Daniel S. Haischt -
Ok, I'm in. Let's do it.
I commit $200 to this bounty to get a nice basic working OpenSER package for pfSense to achieve my intended purpose of outbound proxying SIP clients located behind a pfSense NAT gateway.
-
So what's the protocol here, do I pay out the $200 via paypal after it's done or what?
-
@tog:
So what's the protocol here, do I pay out the $200 via paypal after it's done or what?
Yes via paypal, after it's done and you were able to aknowledge that the software works as expected and there are no bugs.
Regards
Daniel S. Haischt -
Remember that I am in for the other $200.
Daniel, have you started to work on this project? If so, do you have a tentative time-frame for completion?
Thanks.
-
Remember that I am in for the other $200.
Sure I do!
Daniel, have you started to work on this project? If so, do you have a tentative time-frame for completion?
I didn't start working on the project. I have to fix the FreeNAS NFS code this weekend and on monday, tuesday, wednesday I'll try to migrate my server to FreeBSD 6.2. After that I would be able to work on the project.
Regards
Daniel S. Haischt -
Daniel,
Maybe I can chip in here. Have a VMWare PFDev up and running and just completed the OpenSer 1.1.1 compile… with all modules and mySQL 4.1 support.
Oh, not looking for any of the bounty, by the way.//b
-
would you mind to try whether the MySQL 5.0 client is supported by OpenSER as well?
Thanks!
Cheers
Daniel S. Haischt -
Hi Daniel,
Once again wondering if you managed to make some progress on this. If so, any timetable for an alpha/beta
package release?Thanks.
-
Hello sipster,
in february 2007 I started working at IBM. ATM each open source projects for which I may contribute code - even if doing such a contribution in my personal time - needs a written permission from my manager.
Until I will get such a permission for pfSense, I think it does not make much sense to work on packages.
Anyway you may provide an answer about whether you will need MySQL support to be compiled into OpenSER? My current OpenSER setup does not contain MySQL support. Instead I made a decision to just support unixODBC.
Regards
Daniel S. Haischt