Vonage servers ip addresses

Author	All Replies
rizwan602 join:2004-03-20 Gilbert, AZ	Vonage servers ip addresses Hello, We run a very secure network at our office where only certain type of outbound traffic is allowed through the firewall: TCP/25 (SMTP) UDP/53 (DNS) TCP/80 (HTTP) TCP/110 (POP3) TCP/443 (HTTPS) etc... and everything else is blocked. (this configuration makes sure that no unauthorized activity is allowed; such as CHAT, or IRC, or BitTorrent activity. We would like to use a Vonage ATA behind this firewall on our network. I would like to grant access to UDP 10000-20000 for Vonage RTP traffic along with standard SIP ports. But I only want to allow this traffic to Vonage's IP address ranges. The reason is that the above range is a LARGE range where a Bittorrent client can access peers through those ports. So where can I get a list of Vonage servers' ip address so that we can open up our firewall to those ip addresses? I have tried to Google this information but have had no results. Other than monitoring what the ATA is trying to do at the firewall level I have no other information. Any ideas? Thank you, Rizwan
	to forum · permalink · 2011-10-19 14:12:22 ·
NetFixer Freedom is NOT free Premium join:2004-06-24 The 'Boro Reviews: ·Vonage ·Cingular Wireless ·Comcast ·AT&T Southeast	Does your firewall allow you to limit the opened ports to only the IP address and/or MAC address used by the Vonage adapter's WAN interface? Even if you monitored your firewall for connections from/to the Vonage adapter, there is no guarantee that the IP address(es) used by the Vonage servers might not change. FWIW, shown below are the syslog entries showing a Vonage adapter being rebooted twice (I wanted to see if the IP addresses might change), followed by a brief outgoing call. The IP address 192.168.9.11 belongs to my Vonage VT2442 adapter, and the IP address 192.168.9.254 belongs to my Cisco RV082 router/firewall. You will note that you may also need to allow tftp (UDP port 69) and ntp (UDP port 123) for your Vonage adapter. Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] udhcpc: Router 192.168.9.254 obtained Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] udhcpc: DNS Server 192.168.9.2 obtained Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] : MXP module loading Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] MXP_TMR: CPUFREQ=162500000 Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] MXP_TMR: No need to start linux timer Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] MXP_TMR: Calibrating MXP Timer... Ticks/sec=200 Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] MXP_TMR: MIPS Timer start_count=1249316337, end_count=1249722587, current_count=1249722597 Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] MXP_TMR: Calibrated Timer16 count = 19527 Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] : MXP module loaded Oct 19 22:22:46 192.168.9.11 [00159AC6CADB] : MXP memory module loaded Oct 19 22:22:47 192.168.9.11 [00159AC6CADB] HW_DSP: interrupt mode 0, enable_isr 0 Oct 19 22:22:47 192.168.9.11 [00159AC6CADB] udhcpc: Lease of 192.168.9.11 obtained, lease time 604800 Oct 19 22:22:47 192.168.9.11 [00159AC6CADB] : putting dsp in tight loop status=1 Oct 19 22:22:47 192.168.9.11 [00159AC6CADB] : HW_DSP module loaded Oct 19 22:22:47 192.168.9.11 [00159AC6CADB] DSP mult: 10 Input clock: 12288000, final DSP speed: 122880000 Oct 19 22:22:48 192.168.9.254 Oct 19 22:22:48 2011 gw1 RGFW-OUT: ACCEPT (TCP 192.168.9.11:2049->204.13.248.112:80 on ixp1) [0,0] Oct 19 22:22:49 192.168.9.11 [00159AC6CADB] : TIUHW module start loading Oct 19 22:22:57 192.168.9.254 Oct 19 22:22:56 2011 gw1 RGFW-OUT: ACCEPT (TCP 192.168.9.100:3786->209.123.109.175:80 on ixp1) [0,0] Oct 19 22:22:57 192.168.9.11 [00159AC6CADB] DSP mult: 10 Input clock: 12288000, final DSP speed: 122880000 Oct 19 22:22:57 192.168.9.11 [00159AC6CADB] : putting dsp in tight loop status=1 Oct 19 22:22:57 192.168.9.11 [00159AC6CADB] DEBUG: Registering port 554. Oct 19 22:22:57 192.168.9.11 [00159AC6CADB] DEBUG: Socket 94db1a80 has service_class 0. Oct 19 22:22:59 192.168.9.11 [00159AC6CADB] DEBUG: Registering port 4000. Oct 19 22:22:59 192.168.9.11 [00159AC6CADB] DEBUG: Socket 94cf8da0 has service_class 0. Oct 19 22:23:04 192.168.9.254 Oct 19 22:23:03 2011 gw1 RGFW-OUT: ACCEPT (UDP 192.168.9.11:10000->69.59.234.33:10000 on ixp1) [0,0] Oct 19 22:23:04 192.168.9.11 [00159AC6CADB] DEBUG: Deregistering port 4000. Oct 19 22:23:06 192.168.9.254 Oct 19 22:23:05 2011 gw1 RGFW-OUT: ACCEPT (UDP 192.168.9.11:2054->69.59.252.63:69 on ixp1) [0,0] Oct 19 22:23:13 192.168.9.254 Oct 19 22:23:12 2011 gw1 RGFW-OUT: ACCEPT (UDP 192.168.9.11:2055->216.115.23.76:123 on ixp1) [0,0] Oct 19 22:24:24 192.168.9.254 Oct 19 22:24:23 2011 gw1 RGFW-IN: ACCEPT (IGMP 192.168.9.254->224.0.0.1 on ixp2) [30,0] Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] udhcpc: Router 192.168.9.254 obtained Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] udhcpc: DNS Server 192.168.9.2 obtained Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] : MXP module loading Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] MXP_TMR: CPUFREQ=162500000 Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] MXP_TMR: No need to start linux timer Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] MXP_TMR: Calibrating MXP Timer... Ticks/sec=200 Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] MXP_TMR: MIPS Timer start_count=1274661555, end_count=1275067805, current_count=1275067822 Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] MXP_TMR: Calibrated Timer16 count = 19528 Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] : MXP module loaded Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] : MXP memory module loaded Oct 19 22:24:28 192.168.9.11 [00159AC6CADB] udhcpc: Lease of 192.168.9.11 obtained, lease time 604800 Oct 19 22:24:29 192.168.9.11 [00159AC6CADB] HW_DSP: interrupt mode 0, enable_isr 0 Oct 19 22:24:29 192.168.9.11 [00159AC6CADB] : putting dsp in tight loop status=1 Oct 19 22:24:29 192.168.9.11 [00159AC6CADB] : HW_DSP module loaded Oct 19 22:24:29 192.168.9.11 [00159AC6CADB] DSP mult: 10 Input clock: 12288000, final DSP speed: 122880000 Oct 19 22:24:30 192.168.9.254 Oct 19 22:24:29 2011 gw1 RGFW-OUT: ACCEPT (TCP 192.168.9.11:2049->204.13.248.112:80 on ixp1) [0,0] Oct 19 22:24:30 192.168.9.11 [00159AC6CADB] : TIUHW module start loading Oct 19 22:24:39 192.168.9.254 Oct 19 22:24:38 2011 gw1 RGFW-OUT: ACCEPT (ICMP type 8 code 0 75.146.8.41->68.87.20.69 on ixp1) [31,0] Oct 19 22:24:39 192.168.9.11 [00159AC6CADB] DSP mult: 10 Input clock: 12288000, final DSP speed: 122880000 Oct 19 22:24:39 192.168.9.11 [00159AC6CADB] : putting dsp in tight loop status=1 Oct 19 22:24:39 192.168.9.11 [00159AC6CADB] DEBUG: Registering port 554. Oct 19 22:24:39 192.168.9.11 [00159AC6CADB] DEBUG: Socket 94cb63e0 has service_class 0. Oct 19 22:24:39 192.168.9.254 Oct 19 22:24:38 2011 gw1 RGFW-OUT: ACCEPT (ICMP type 8 code 0 75.146.8.41->208.82.196.25 on ixp1) [31,0] Oct 19 22:24:40 192.168.9.11 [00159AC6CADB] DEBUG: Registering port 4000. Oct 19 22:24:40 192.168.9.11 [00159AC6CADB] DEBUG: Socket 94cb70e0 has service_class 0. Oct 19 22:24:45 192.168.9.254 Oct 19 22:24:45 2011 gw1 RGFW-OUT: ACCEPT (UDP 192.168.9.11:10000->216.115.20.77:10000 on ixp1) [0,0] Oct 19 22:24:46 192.168.9.11 [00159AC6CADB] DEBUG: Deregistering port 4000. Oct 19 22:24:48 192.168.9.254 Oct 19 22:24:47 2011 gw1 RGFW-OUT: ACCEPT (UDP 192.168.9.11:2054->216.115.21.201:69 on ixp1) [0,0] Oct 19 22:24:55 192.168.9.254 Oct 19 22:24:54 2011 gw1 RGFW-OUT: ACCEPT (UDP 192.168.9.11:2055->69.59.240.76:123 on ixp1) [0,0] Oct 19 22:25:04 192.168.9.11 [00159AC6CADB] DEBUG: Registering port 10050. Oct 19 22:25:04 192.168.9.11 [00159AC6CADB] DEBUG: Socket 94db1a80 has service_class 0. Oct 19 22:25:04 192.168.9.11 [00159AC6CADB] DEBUG: Registering port 10051. Oct 19 22:25:04 192.168.9.11 [00159AC6CADB] DEBUG: Socket 94963100 has service_class 0. Oct 19 22:25:05 192.168.9.254 Oct 19 22:25:04 2011 gw1 RGFW-IN: BLOCK-RULES (UDP 69.59.241.14:16226->192.168.9.11:10050 on ixp1) [1406,92143629] Oct 19 22:25:09 192.168.9.254 Oct 19 22:25:08 2011 gw1 RGFW-RATELIMIT: 13 messages of type BLOCK-SYNFLOOD reported 4 second(s) ago Oct 19 22:25:09 192.168.9.254 Oct 19 22:25:08 2011 gw1 RGFW-IN: BLOCK-RULES (UDP 69.59.241.14:16227->192.168.9.11:10051 on ixp1) [1406,92143629] Oct 19 22:25:18 192.168.9.11 [00159AC6CADB] DEBUG: Deregistering port 10050. Oct 19 22:25:18 192.168.9.11 [00159AC6CADB] DEBUG: Deregistering port 10051. Based on the above information, if I wanted to only allow access to Vonage IP addresses used by my VT2442, I would allow the IP address ranges shown below: NetRange: 216.115.16.0 - 216.115.31.255 CIDR: 216.115.16.0/20 OriginAS: NetName: DATACENTER NetHandle: NET-216-115-16-0-1 Parent: NET-216-0-0-0-0 NetType: Direct Assignment RegDate: 2003-07-18 Updated: 2009-04-28 Ref: http://whois.arin.net/rest/net/NET-216-115-16-0-1 OrgName: Vonage Holdings, Inc. OrgId: VONAG Address: 23 Main St City: Holmdel StateProv: NJ PostalCode: 07733 Country: US NetRange: 69.59.224.0 - 69.59.255.255 CIDR: 69.59.224.0/19 OriginAS: NetName: VONAGE-BLOCK-2 NetHandle: NET-69-59-224-0-1 Parent: NET-69-0-0-0-0 NetType: Direct Assignment RegDate: 2005-06-14 Updated: 2009-04-28 Ref: http://whois.arin.net/rest/net/NET-69-59-224-0-1 OrgName: Vonage Holdings, Inc. OrgId: VONAG Address: 23 Main St City: Holmdel StateProv: NJ PostalCode: 07733 Country: US I also use my RV082 to switch between my primary ISP (Comcast) and a backup AT&T connecton if there is a problem with the Comcast connection. Therefore, I run a DDNS client on my VT2442 so that I can easily access it remotely if needed by using the same hostname no matter which ISP is being used, so I would also have to include the IP address(es) that belong to Dynamic Network Services in addition to those belonging to Vonage. NetRange: 204.13.248.0 - 204.13.251.255 CIDR: 204.13.248.0/22 OriginAS: AS33517 NetName: DNSINC-1 NetHandle: NET-204-13-248-0-1 Parent: NET-204-0-0-0-0 NetType: Direct Assignment Comment: Dynamic Network Services, Inc. http://www.dyndns.org RegDate: 2005-05-10 Updated: 2008-01-03 Ref: http://whois.arin.net/rest/net/NET-204-13-248-0-1 OrgName: Dynamic Network Services, Inc. OrgId: DNS-33 Address: 150 Dow St. City: Manchester StateProv: NH PostalCode: 03101 Country: US -- A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
	to forum · permalink · 2011-10-20 00:20:56 ·
rizwan602 join:2004-03-20 Gilbert, AZ	Thank you -- this is GREAT information. I am unwilling to allow the Vonage ATA full access because someone could theoretically place a computer on the NAT side of the ATA and have full access therefore. And we will have more than 1 ATA connecting to Vonage; therefore its better for us to open up all traffic (or at least RTP traffic on ports 10000-20000 UDP to Vonage netblocks.) Thanks again; that was great information!!
	to forum · permalink · 2011-10-20 03:11:54 ·
NetFixer Freedom is NOT free Premium join:2004-06-24 The 'Boro Reviews: ·Vonage ·Cingular Wireless ·Comcast ·AT&T Southeast	said by rizwan602: I am unwilling to allow the Vonage ATA full access because someone could theoretically place a computer on the NAT side of the ATA and have full access therefore. And we will have more than 1 ATA connecting to Vonage; therefore its better for us to open up all traffic (or at least RTP traffic on ports 10000-20000 UDP to Vonage netblocks.) I can't guarantee that all Vonage ATAs have the "block all LAN traffic" feature, but mine does. Activating that feature makes the Vonage router function as only an ATA, and nothing physically connected to the LAN should be able to access anything through the Vonage adapter's WAN interface. You may want to activate that feature if your ATAs have it even if you do limit access to only Vonage server IP addresses. -- A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
	to forum · permalink · 2011-10-20 04:24:14 ·
rizwan602 join:2004-03-20 Gilbert, AZ	That would work; I'll have to check to see if our ATA supports the block all traffic function. Thank you!
	to forum · permalink · 2011-10-20 11:32:37 ·

VOIP etc > Voice Over IP - VOIP > Vonage > Vonage servers ip addresses