Nearly always, rewriting source port on SIP breaks it so it's not done
by default. Enable AON and it will be.


On Wed, Mar 18, 2009 at 6:11 AM,  <[email protected]> wrote:
>
> Hi
>
> I know this issue have been raised before, but I haven't really found a
> satisfying answer, so here I go again...
>
> My problem is related to sip-nat.
>
> I'm running a network with approximately 2000 home users.
> I have choosen pfsense back in the 1.0.1 days, and is still very satisfied
> with it's performance and stability.
> At the moment I have four machines running pfsense.
> One working as router only (disabled the firewall under advanced). - pfsense
> v. 1.2
> Two working as nat-routers for Internet-access. - pfsense v. 1.2
> One working as a nat-router for Audiocodes MP124 sip boxes. - pfsense v.
> 1.0.1
>
> When pfsense 1.2 came out, I upgraded every machine. But quickly I had to
> roll the "sip-router" back to 1.0.1, since it
> stopped rewriting the source port for the MP124 boxes.
>
> My problem is that many costumers choose to set up there own sip-boxes on
> the internet-connection, and therefore get connected with one of the routers
> thats running pfsense 1.2. And it just does not rewrite the source port, and
> as a result of that only one sip-box per provider gets connected. As soon as
> I throw them on another vlan, so they get connected to the machine running
> pfsense 1.0.1, it rewrites the ports just fine, and I can have as many boxes
> from the same provider behind one single public ip.
>
> Does anyone have an explanation to this behavior, or even better, a
> solution!?
>
> Kind regards
>
> Anders Dahl
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> Commercial support available - https://portal.pfsense.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Reply via email to