Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya IP Office 500 V2, 9608 IP Phone and Netgear FVS318 2

Status
Not open for further replies.

chicgal

Programmer
Nov 25, 2010
22
US
New Install

Having issues with hooking at remote location with Netgear FVs318 and 9608 IP Phone.

Main office is also using FVS318

Not using the 9608 VPN Client, it is a point to point VPN.

Provider is comcast.

The IP Phone cannot connect and cannot ping the IPO Office control unit. After a couple of hours, it started working and user can receive 1 call. Now it is still down.

I thought there was configuration problem with the control unit but since the user can receive 1 call, i assume it is not.

any idea?
 
The Netgear FVS is318 a bad router.
It is way too slow.

But can you ping the ipo from a pc connected to the router?


BAZINGA!

I'm not insane, my mother had me tested!
 
Yes I can ping it locally on their local network – at their main office – the only router we have there is the netgear FVs318.

At the remote location, I can ping everything but the pbx/control unit through the vpn
 
Do you have an iproute in the ipo to the remote network?
Normally the router should take care of this but you could try it.


BAZINGA!

I'm not insane, my mother had me tested!
 
Do you have a default gateway assigned on the IPO? No default route would give you that behavior (ping on same LAN, no ping from different subnet)

Is the VPN device seperate from the Internet router? Id so you need to build a route to the VPN appliance for whatever subnet is being used.
 
i have an IProute configured with IP Address

anything wrong with it?

192.198.1.0 ~ remote lan

IP Mask - 255.255.2555.0 ~ remote mask

gateway IP address - 10.10.1.254 ~ local gateway

Destination - LAN1

 
I would change the subnet mask to 255.255.255.0 :)

That iproute should work.

BAZINGA!

I'm not insane, my mother had me tested!
 
sorry that was my typo error on this forum - the subnet mask is 255.255.255.0
 
I know it is a type, the ipo won't allow that subnet mask :)
Can you ping both the routers from system status?

BAZINGA!

I'm not insane, my mother had me tested!
 
If your IPO is on the 10.10.1.0 network, the device that is 10.10.1.254 can route to the 192.168.1.0 technically you should be fine.

Is "192.198" a typo? It should probably be 192.168.1.0

Also if the remote LAN is 192.168.1.0 (very common default network) and the VPN subnet is 192.168.1.0 you have a conflict you need to resolve.
 
OK: No typo this time...

IP (Remote) 192.168.1.0
Subnet (Both) 255.255.255.0
Gateway (Local) 10.0.1.254
Local DNS 10.0.1.1
IPO 10.0.1.250
Phone is DHCP on remote network pointing to ipo for Call Server and HTTP server.

I can ping the IPO locally, but not through the tunnel. I can ping the local gateway, DNS server and other PC's through the tunnel.

Tunnel is Netgear on both ends ipsec, SHA-1, DH2, Shared secret. Tunnel seems to stay up when phone goes down. I stay connected to PC via RDP the entire time. I can run a continuous ping to the server through the tunnel without dropping any packets.

Phone connects for about 15 minutes at a time, then drops, cycles and goes to "Discover 10.0.1.250
 
A couple years ago I had issues with a Netgear VPN. Can't remember the model. I didn't do the VPN set up the IT vendor did. The specific issue was that one VPN phone would work but if I plugged in a second phone both would die as soon as the second started registering. The VPN routers had to be rebooted before even a single phone would register across the VPN again.

After 5 rounds with Netgear's engineers the IT guy swapped for an upgraded Netgear model which immediately resolved the issue. It was the Netgear messing with the h.323 traffic. I even found the exact issue in the patch notes 2 firmware versions before the one the routers were running.

Here's one with a FVS318 where a Firmware update solved the problem.

 
Both of the FVS318 are V3 3_0_28 firmware, which is the most recent. No updates available. I am ready to give up on Netgear...

Any suggestions on a replacement firewall that is economical? I am currently looking at a Cisco RV042-NA or SonicWall TZ-200, but don't want to swap out if it is not going to fix the problem...

Thanks!
 
Don't go for Sonicwalls, you will have no hair left if you do, Cisco all he way or if money is tight Draytek (on the right firmware) :)

NTE-wave-logo-for-a4-header.jpg
 
What router do you have.

The FVG318V1 or the V2? There will be a replacement for them, the FVG318N. The current routers have some DHCP problems, so you might need to add another dhcp server to make it work. The problem is that the lease won't be deleted after 8 days.

If you wan't to stay with Netgear try the SRX5308, i tested it with 5600 and the 9600 range and they all work. Except for the 9670 it has VPN firmware, but the keyboard is not moving away when you need to scrol down.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Just to conclude this tread - we switch to CISCO rv042 and it works!!!!!!!!!!!!!!!!!!!!!!!!!

Will no longer use netgear.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top