from http://www.voip-info.org/wiki/view/Broadsoft

"Broadsoft develops and sells carrier grade VOIP software solutions to major ISPs, phone companies, cable companies, and wireless operators. If measured by numbers of users, Broadsoft is likely the largest VOIP application provider in the world. "

If you search around, there are definitely many large providers that are using it to provide trunks. I don't know if the port limitations are from the product or from engineers running. My guess would be it is with the telco, not the product. Just my guess though.

On 7/23/2010 8: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.

    If I had a separate SBC, rather than sipxbridge, it would run on a
    seperate computer, its own ip address, etc.
    since sipx does this on one computer, it uses a different port for
    trunking.  udp port 5080.

Correct. sipxbridge sits behind a firewall and "needs to know" the public IP address the firewall is using.

    (* note: firewalls won't normally do sip translations for traffic
    on port 5080.  they won't associate the rtp traffic with voice,
    and will mangle the ports and traffic)

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.


    so, sip trunking:
    sipx.domain.com:5080 <http://sipx.domain.com:5080> REGISTER->
    itsp.example.com:5060 <http://itsp.example.com:5060>
    itsp.example.com:5060 <http://itsp.example.com:5060> 200 OK ->
    sipx.domain.com:5080 <http://sipx.domain.com:5080>

    sip uri dialing, to and from?
    sipx.domain.com:5060-> [email protected]:5060
    <mailto:[email protected]:5060>

As long as your firewall rules say send to a specific port for the ITSP based on an IP ACL, or outbound rule, it should be able to achieve this.

    if you had a separate  sbc,( including using port forwarding/pat,
    etc) and the itsp could not figure out how to send to port 5080.

    sip trunking:
    sbc.domain.com:5060 <http://sbc.domain.com:5060> REGISTER
    ->itsp.example.com:5060 <http://itsp.example.com:5060>
    itsp.example.com:5060 <http://itsp.example.com:5060> 200 OK
    ->sbc.domain.com:5060 <http://sbc.domain.com:5060>

    sip uri dialing the same?
    sipx.domain.com:5060-> [email protected]:5060
    <mailto:[email protected]:5060>

    so, if I used a different public ip address to listen to port
    5080, and translate their inbound 5060 (or in the case of
    broadsoft, 5070) to and from the internal sipx on port 5080,
    leaving everything else the same, would that make life easier on
    the big fella's?


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.

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®.
    For Information please see http://www.secnap.com/products/spammertrap/

    ------------------------------------------------------------------------


    _______________________________________________
    sipx-users mailing list [email protected]
    <mailto:[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/




--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected] <mailto:[email protected]>
Fax: 434.984.8431

Email: [email protected] <mailto:[email protected]>

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected] <mailto:[email protected]>
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 [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/

_______________________________________________
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