Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 6 subscribers
  • Views 3316 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Star2Star VOIP - UTM Setup

Phreeze

My question / dilemma may require several steps.  I apologize in advance.

 

Star2Star is a VOIP provider in which it is somewhat proprietary / closed / locked down.  I inherited it and must live with it for a while.  They require their little "black box" have a Public IP address and sit at the edge of the network.  I'd rather not have a switch in front of my UTM/s in order to "Split" the internet connection.  They of course want their box in front with everything running through their box.. no thanks ...

So how do I make this work?

1. Physically - Can I just plug the box into any port on my SG210 and configure an interface and give it one of our Public Static IP's .

2. How do I let the connection to the Starbox be Open so it can communicate with Star2Star's systems ? 

3. Internally all the phones must be on VLAN 41 (Tagged) to work.  The Starbox hands out the DHCP address to the phones.  How do I let this happen/ work ?

 

Let's start there. 



This thread was automatically locked due to age.
Parents
  • +1

    I helped another Sophos reseller with this with a client of his last year and all traffic passed through the UTM and the *2* box was "behind" the UTM.  One of the tricks we had to use was that one connection between the *2* and the UTM was an untagged VLAN connection.  They have documentation explaining how to do this, but most (my impression) *2* installers don't know how to do what you want and will resist trying it.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • +1

    I helped another Sophos reseller with this with a client of his last year and all traffic passed through the UTM and the *2* box was "behind" the UTM.  One of the tricks we had to use was that one connection between the *2* and the UTM was an untagged VLAN connection.  They have documentation explaining how to do this, but most (my impression) *2* installers don't know how to do what you want and will resist trying it.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson

    Do you recall with this "untagged vlan"  what you entered for IP address  etc ... am I correct in my thinking that an "Ethernet" interface on the UTM is "Untagged"  but if you choose Interface type Ethernet VLAN  and enter the Tag ID then it is "Tagged"

  • 0 in reply to Phreeze

    That's my recollection of the experiments we did with the *2* and UTM at the time - they don't use the same terminology, so one of their installers would be confused by the UTM and would give a local UTM admin "incorrect" instructions.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Unfiltered HTML