Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 3 subscribers
  • Views 21820 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

Vonage configuration

manipal

Hi 

I just built and configured my UTM with the home license. I use vonage at home and it stopped working after implementing UTM9. Vonage box is getting the IP address ( I am using DHCP server in the UTM). What VoIP rules do I need to setup to let the traffic through for vonage?  If someone can please give me step by step instructions as I am still learning about the UTM's.

Thanks



This thread was automatically locked due to age.
  • 0

    Hi Manipal,

    Please refer the link to configure SIP protocol in UTM.

    https://www.sophos.com/support/knowledgebase/120284.aspx

    Hope that helps.

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0

    I saw that article . But it doesn't give anything specific about vonage. I don't know what the server network is for vonage ? In the client network , j am assuming I will put in my entire home network?

  • 0 in reply to sachingurung

    Unknown said:

    Please refer the link to configure SIP protocol in UTM.

    https://www.sophos.com/support/knowledgebase/120284.aspx

    Please note:  The KB references SIP signalling on 5060, Vonage uses 5061.

    -- From Vonage --

    SIP: Port 5061 UDP (Used to send and receive SIP information)

    RTP: Ports 10000-20000 UDP. (Used to send and receive RTP traffic) When a call is made, random ports between 10000 and 20000 are used to carry the conversation. If any of these ports are blocked, you may experience one way or no audio.

  • 0 in reply to manipal

    Hi Manipal,

    As suggested by , please include port 5061 for SIP signalling. In the client network section, you can either configure your home network or Any.

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0

    If you have a firewall rule like 'Internal (Network) -> Any -> Internet : Allow', you won't need anything else for Vonage.  Otherwise, start with #1 in Rulz.  The only ports I've seen used for Vonage were HTTP and UDP 21, 53, 67, 69, 123, 2400, 10000:20000 and 62265.

    Cheers - Bob

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

    There is an easier solution I have found. Per Vonage website , Vonage adapter can be placed between cable modem and the router/firewall. I tried it and it works well. Basically you connect Cable modem Eth port to the WAN port of vonage adapter and LAN port of vonage adapter to the WAN port or router/firewall. Vonage adapter if a 1 port router and it gives my router the WAN address of 192.168.15.2 . And the router is giving DHCP for the clients connected to the LAN side of the router (192.168.1.1/24 range). The Vonage router management page can be accessed via 192.168.15.1 from my local network ( it has basic firewall, port forwarding settings etc , which I have left them untouched for most part).

    Is there anything wrong in using this configuration security wise?

    Thanks

  • 0 in reply to manipal

    You are creating a double NAT, so there are some issues with IPsec and L2TP/IPsec Remote Access.  It's better to have the public IP on the UTM's external interface.

    Cheers - Bob

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