9650 VPN "Discovering" issue 2

[zyx500]

Hi

I'm setting up a 9650C phone to operate remotely and connect to our HQ avaya.

We have setup the phone and firewall to connect using Cisco VPN client.

Avaya is a 500 v1 with R7.0(27) manager
IPSec using AES-128, MD5, DH Group is 2
IP and HTTP of Avaya unit is 192.168.1.252

Phone setup with 0.0.0.0 for most settings so it picks up local address. Gateway is the WAN firewall of HQ

So pretty standard setup, I think.

All authenticates OK, tunnel created etc.

Phone connects to the Avaya, says it is downloading 96xxupgrade.txt and then gets stuck at discovering 192.168.1.252 (our Avaya TFTP and HTTP address).

After trying to load the 96xx file it returned a message HTTP: 1 -905

I reset the phone connected to the network, all OK.

Re loaded all the VPN settings, went outside the network, authenticated the VPN tunnel etc again tunnel all OK.

Phone connects to the Avaya, says it is downloading 96xxupgrade.txt and then gets stuck at discovering 192.168.1.252

After trying to load the 96xx file it now returns a message HTTP: 1 7

I can't find what this message means and I'm a bit stuck as to what the issue is and I'm spending loads of time going round in cycles

Appreciate some guidance.
Thanks

 

[IPOLackey]

It's creating the tunnel but there's a routing issue there. It can't reach the 192.168.1.252 IP address through the tunnel. I'd check the firewall so that the VPN subnet can reach your IPO and check the routes on the IPO so it can reach the VPN subnet.

Hope that helps point you in the right direction.

 

[derfloh]

The settings file has parameters called NVMCIPADD and NVHTTPSRV to define the call server and file server IP address when connected through VPN.

 

[Pepp77]

Have you entered the protected net as 192.168.1.0/24?
What is the IP address of the local network the phone is connecting from? If this is also 192.168.1.x then it will not connect to a 192.168.1.x IP address across the VPN.

| ACSS SME |

 

[zyx500]

The IP addresses are the same on both networks, so that could well be the issue, i hadn't considered they should be different. I entered protected as 0.0.0.0/0, maybe should enter 192.168.1.0/24 I wanted the phone to be flexible to take to the remote site plug in & it would pickup local network. But if it is same as 192.168.1.x then That will be an issue. So does that mean I'd have to give the phone fixed settings on a different IP. Eg 192.168.0.x Or should changing the protected do the trick? Are there any other tricks I'd need to consider?

 

[intrigrant]

Use a different IP Address in the phone and create in IP Office a route towards that network with the VPN router as the gatweway.

 

[amriddle01]

The phone will only try to leave its own network if the address isn't local, with them being on the same network range it thinks it's local

 

[zyx500]

Ok that makes sense, I'll change the settings & hopefully it should start talking!