actually, if you are using 1:1 NAT, you might find the configuration much
easier using a recent pfsense 2.0 snapshot, where you have much more
granular control in outbound rules, etc.

On Fri, Aug 20, 2010 at 3:14 AM, Tony Graziano <tgrazi...@myitdepartment.net
> wrote:

> I don't think you would need a second system "just" for this. Adding a
> second system also means instituting HA mode, both would have to be proxies
> (which is not a bad thing). Having asked the dev team before, it is not
> possible to run sipxbridge as a standalone system "just" for SBC purposes,
> it has to be HA.
>
> Patton and Audiocodes gateways both have survivability features. Please
> also remember the "cost" of bandwidth for remote branches calling voicemail,
> etc. There are certainly efficiencies in both type of deployments, I don't
> pretend to suggest which one is better for a particular environment, as
> everyone's needs are different. If your internet connection goes down, how
> much functionality do the remote branches need?
>
> There should be no reason pfsense can't translate what you want:
>
> 1. Find out what Ip or CIDR's the ITSP will be communicating on.
> 2. If source is <ITSP RANGE> and on port 5060, then send to sipx on port
> 5080
> 3. If destination is <ITSP range> then make sure you use ip address
> dedicated for itsp.
> 4. Users come and go on different ip on port 5060, so they are not
> affected,a and that is the public ip you assign dns records to.
>
> If you called voip.ms or did an online chat, you would also find that they
> can do an IP based ACL in lieu of registration, but you cannot do this
> online, they have always been flexible though we do not use them for any
> other method except registration, though we use ITSP's that use IP based
> ACL's only.
>
>
> On Thu, Aug 19, 2010 at 10:32 PM, Michael Scheidell <
> michael.scheid...@secnap.com> wrote:
>
>>  THANKS!  possibly if I have the cisco rule I can transliterate it to
>> pfsense or pf.
>>
>>
>>
>>
>> On 8/19/10 10:31 PM, Matthew Kitchin (Public) wrote:
>>
>> I will have to ask my network engineer tomorrow what he did. Not my area
>> of expertise.
>>
>>
>> --
>> 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®.
>> For Information please see http://www.secnap.com/products/spammertrap/
>> ------------------------------
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>>
>> sipx-users@list.sipfoundry.org
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
> ======================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: tgrazi...@voice.myitdepartment.net
> Fax: 434.984.8431
>
> Email: tgrazi...@myitdepartment.net
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: helpd...@voice.myitdepartment.net
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> Why do mathematicians always confuse Halloween and Christmas?
> Because 31 Oct = 25 Dec.
>
>


-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to