Maybe NAT 2 external IPs to it. One that does 5060->5080 and one that doesn't.
Whatever needs to hit it on 5060 would use the IP with no translation.
-----Original Message-----
From: Michael Scheidell <[email protected]>
Date: Thu, 19 Aug 2010 21:43:55
To: <[email protected]>
Cc: [email protected] users<[email protected]>
Subject: Re: [sipx-users] port 5060/ port 5080, proxy why?
it can do port translation, as in if it sees ANYTHING hit port 5060 it
can translate it to an internal 5080.
it can't do this:
itsp.public hits sipxpublic:5060 it goes to sipxprivate:5080
everyone else hits port 5060 it goes to sipxprivate:5060
On 8/19/10 9:39 PM, Matthew Kitchin (Public) wrote:
> , but I would be surprised if pfsense couldn't do a port translation.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best in Email Security,2010: Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
