Siproxd info?



  • Hi All,

    I'm using 1.2.1 embedded… I am trying to find information on how to setup + use siproxd. Any advice appreciated (where do I go for more info).  I have searched the docos + google... All I can find that it is a feature, and that some have had success.

    Thanks,
    Andrew



  • Well siproxd should really be moved to base pfSense till the VoIP issues are solved directly into pf.
    Though i do not see work going on it in near time without some backing.



  • @ermal:

    Well siproxd should really be moved to base pfSense till the VoIP issues are solved directly into pf.
    Though i do not see work going on it in near time without some backing.

    All, thanks for that - I might just setup the phones to run over my vpn link then (so I can have multiple behind a single nat).  I haven't done any research on the need for this, does BSD have this limitation?  I was running a Linux 2.6 kernel with 4 phones behind a single nat (no proxy needed).  I didn't actually realise that anything special was going on in the background with linux to avoid the problems. (SIP connection tracking?)

    Will a newer version of BSD address the need to have a SIP proxy in the first place?



  • siproxd is a package, which are not possible to run on embedded.

    @aray:

    Will a newer version of BSD address the need to have a SIP proxy in the first place?

    No, there is no interest from pf developers to extend NAT to support NAT broken protocols like SIP. If it's ever done without a proxy it'll probably be something Ermal does patched for our code base specifically.



  • Quote Ermal:
    Well siproxd should really be moved to base pfSense till the VoIP issues are solved directly into pf.
    Though i do not see work going on it in near time without some backing.

    We would like to do the coding work, Ermal. What do we do? Who do we talk to?
    How can we make it available in a stable branch asap?
    We had to move to m0n0 with some devices and we would rather stick to a homogenous environment. ;-)



  • @bill:

    We had to move to m0n0 with some devices and we would rather stick to a homogenous environment. ;-)

    m0n0 is worse for VoIP than pfSense, siproxd works around issues that can't be worked around with m0n0 and for everything else there is no difference. You probably just need static port if m0n0 works. http://doc.pfsense.org/index.php/Static_Port



  • I will second the 'Static port' suggestion under Firewall -> NAT -> Outbound NAT -> Manual Outbound NAT -> Static Port. This solved my Problems with NAT.

    Please leave siproxd as a package at least for the Full Install on non embedded. I have created a pfSense package FreeSWITCH which can also run as a SIP proxy or PBX. So now there are two choices for those that want a SIP proxy. There has also been requests on the forum for some time of an openSER package. I think siproxyd in the base of pfSense would actually limit pfSense.

    Before Firefox there was Mozilla bloated with many features many people didn't want. Internet Explorer also suffered from upgrades with features that very few people wanted. The concept behind Firefox was to make the additional features optional for those that want it. The 'Add-ons' in Firefox have grown immensely and many of them are very good.

    pfSense's packages is a feature that can help keep the base system from getting bloated which will help keep it fast and its requirements for system resources lower. pfSense package list is growing and I expect that the growth of it is just beginning.


Log in to reply