Avaya 9620L VPN VOIP Stuck at Discovering

[dailen]

I am trying to set up an Avaya 9620L to function using VPN.

I used this document as a guide to initially set it up (

http://downloads.avaya.com/css/P8/documents/100019199)

but had to make some minor adjustments in order to use it because the router we have is the same model but v2. I believe I have been able to establish a VPN connection because the Netgear router configuration reports the phone "user" as being connected.

The phone boots up, connects to the VPN, gets a network IP, then goes to the "Discovering 192.168.2.XX" screen and never changes. The phone was originally configured and functional inside the building on our intranet so I know it works.

Not quite sure what the problem is or where to start. Any ideas?

 

[tlpeter]

What is your protected network set to on the phone?
It should be like

192.168.2.0/24


BAZINGA!

I'm not insane, my mother had me tested!

 

[hairlessupportmonkey]

and make sure the two networks aren't on the same subnets

ACSS - SME
General Geek

 

[dailen]

@tlpeter - confirmed that's the setting

@hairlesssupportmonkey - Not sure what you mean. The VPN network is on a separate IP range per Avaya's technical guide

 

[tlpeter]

If the local ip range (VPN phone site) is the same as the call server ip range then a VPN does not work.
And i do not mean the virtual ip range but the actual range used by any device on both sites.


BAZINGA!

I'm not insane, my mother had me tested!

 

[dailen]

To clarify, the IP of the outside network the phone is connected to is in the 192.168.1.XX range, the virtual IP range is 172.16.22.XX, the internal network is in the 192.168.2.XX range. The VPN connection is successful according to my router which registers the device as being connected.

 

[dailen]

Any suggestions or something else I can verify?

 

[intrigrant]

Does the IPO has a route to the ip phones local ip address and the gateway set to the vpn touter?

A simple mind delivers great solutions

 

[dailen]

According to page 2 of this Avaya document (

http://downloads.avaya.com/css/P8/documents/100019199)

I'm supposed to set it to 172.16.22.0 which is what I've done. I've been reading through the IP Office Administrator manual and it's got some instructions I haven't seen yet so working through that to see if that helps.

 

[dailen]

Alright so no gravy, I still get a "Discovering 192.168.2.XX" message that never goes away

 

[intrigrant]

This means that either the phone cannot find the IP Office or the IP Office cannot find the phone.
In sysmonitor turn on the interface filters.

If you don't see packets coming from the phone then you have a problem in the phone config if you see packets coming from the phone then IPO should send packets back which can be seen in monitor as well, check if these packets are send to the right IP address on the right LAN via the right gateway.

A simple mind delivers great solutions

 

[dailen]

Alright I'll take a look, suggestions for how to identify packets from the phone since I don't think the extension is logging in?

 

[intrigrant]

You must see ip packets from the phone, they can be identified by ip addresses or mac address.
The phone will send H.323 regstration packet which can be seen using the H.323 filter ( which produce less data as the interface filter )

A simple mind delivers great solutions

 

[dailen]

The lack of appropriate useful output and the lack of proper documentation in one place to utilize the VPN with an IP phone is staggering. I was referencing 6 different resources and manuals to get this working. Of course we made a bit of a jump going from nothing but 5420s to adding all the equipment for an IP phone then trying out the VPN so lack of experience was also against us.

Problem ended up being a variety of things. First of all, Avaya's documentation fails to mention that there are feature options that have to be enabled in IP Office Administration/Manager on top of all this not only for the entire network but for the VOIP line...that appears to have been my primary problem.

To make matters worse, when switching between networks (i.e. 192.168.2.X network then 192.168.1.X networks or if any other DHCP data changed), the phone didn't clear it's DHCP data properly I guess because once I got it working I would have to disconnect and reconnect the phone (twice seems to be the magic number thusfar) and suddenly it will connect to the network and function properly.