Avaya 9620 Stuck at Discovering xxx.xxx.xxx.xxx

[Cabbagetoe]

I've seen quite a few posts referencing this same error, but none that specifically touches on my particular scenario (unless I've missed it).

IPO Subnet: 192.168.0.x
Remote Subnet: 192.168.1.x
Static IP in ADDR: 192.168.0.50
Static Call Server in ADDR: 192.168.0.252
Static Router in ADDR: 192.168.0.254
Static HTTP in ADDR: 192.168.0.252
Static HTTPS in ADDR: 192.168.0.252

Protected Network in VPN Settings on 9620 192.168.0.0/24

It seems as though I enter this static info into the phone, but it is still getting a DHCP address from my local network and when it registers the VPN connection and connects, it is trying to find the IPO on 192.168.0.0 while the phone has an IP of 192.168.1.103, which it is getting from the remote side router. No matter how many times I put the static info in, it still reverts back to DHCP. I've done everything I can think of - I've tried changing the Protected Network settings to 0.0.0.0/24 and also put in bogus HTTP and HTTPS settings inside the phone to make sure the 96xx files aren't overwriting my static value, but still every time I reboot it is getting a DHCP from my remote network.

I also have a phone at another remote location that works without issue. I've compared settings for that phone, and it appears as though I have everything set correctly on this one that won't work but still no go.

Suggestions? I hope someone has a solution. I'm about to pull my hair out with this one.

Thanks

 

[holdmusic34]

Your VPN phone should always have a local IP address.

 

[Cabbagetoe]

Your post doesn't put me any closer to solving this problem. Any other insight you might want to give?

 

[amriddle01]

The advice given is accurate, if you tried it and it didn't work just means you have multiple things wrong including that.

 

[derfloh]

Your remote subnet is 192.168.1.0 but you gave the phone 192.168.0.50?

Make sure the remote subnet is not the same as a local subnet and use DHCP die the remote phone.