On 7/23/10 9:22 AM, Tony Graziano wrote:


On Fri, Jul 23, 2010 at 9:10 AM, Michael Scheidell <[email protected] <mailto:[email protected]>> wrote:

    Mostly for those who know sipx and might be using a separate sbc.
    (for broadsoft customers, this might life easier to explain to
    them, and for those who insist their firewall can do sip
    translations, this is why it can't)

Broadsoft is not a trunking platform, rather it is a user platform as I understand it. So JUST like sipx, it wants to connect to users on port 5060... because it is treating sipx like a user.
(or port 5070 as seen by posters trying verison, att and level3)


Firewalls yes. SBC's (depending on the platform) can be told to listen on manually assigned ports because SBC's are supposed to be more flexible.


could I set up a 'non sipxbridge' as a SBC and use their ip address?

It might be easier if you could have a list of the gateway IP's or blocks that are sending to you in order to make the port translation easier. i.e. If source is "4.5.6.0/24 <http://4.5.6.0/24>" (the itsp block) and port is 5060, then send to sipx on port 5080... etc. You might find the gateways sending to you is MUCH more diverse than the gateways you send to them. So you probably need to get them to provide you with this.

could not figure out how to limit this to just their block on pfsense.

The same thing for outbound, if they want you to send them calls on a specific port, you would simply need to know the destination gateway ip('s) you are sending to and should be able to PAT them at the firewall.


--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *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
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to