Remote handset loses connection to local network after boot.

[Prestoncole]

I have an IPO 500 with a number of local 9620 handsets. All are good.
The local network is protected by a Cisco ASA 5505 and there are a few site-to-site VPNs set up.
Local network is 192.168.1.X/24
IPO 500 is 192.168.1.2
Remote networks are 192.168.70.X/24 and 192.168.71.X/24
Both remote networks have 9620 handsets, and other devices such as PC's. Both networks are protected by the same kind of firewall, and are set up identically, other than their local IP address ranges.

On one of the networks, the 9620 boots and gets stuck on Discover 192.168.1.2
I have set the IP address details in the handset via DHCP and statically, but no joy. When set staically, they are:
Phone - 192.168.71.55
Call server - 192.168.1.2
Router - 192.168.71.1
Mask - 255.255.255.0
HTTP: 192.168.1.2
The rest is left default.

During boot of the handset I run a continuous ping from a local PC (192.168.71.10) and a server sitting next to the IPO (192.168.1.250). After the handset starts its networking I see the replies on both the local PC and the remote server, until the phone asks for the extension number and password. At this stage the ping running from the server stops, yet the ping running from the PC next to the handset continues. The PC is able to communicate with the server. In fact the entire networks are able to talk, with the exception of the handset and the network where the IPO lives.
If I enter extension details, the handset displays "Discover 192.168.1.2".
Rebooting the phone now does not ask for the extension, just goes to the Discover message.
If I do reboot the handset, I see the ping start up again, then stop when it gets to the Discover message.

I have a PC connected to the handset, and that does NOT lose connection to the network with the IPO, in fact it can ping the IPO no problem.

I have cleared the settings in the handset and started a fresh.
I have taken this handset to the network where the IPO is, and it works fine.

Any ideas? I'm stuck.


Cheers

 

[janni78]

Do you have service-inspection enabled for H.323 and RAS on the Cisco ASA?
If you do disable that.

"Trying is the first step to failure..." - Homer

 

[Prestoncole]

Hi Janni78

Thanks for the advice.

I have just tried that, but it has made no difference.

The odd thing is I have another 9620 handset at another remote network that connects up and works. Both remote networks use the same hardware to create the VPN to the local Cisco ASA.

I have just set up another remote network with the same hardware, 192.168.52.X/24
I have just failed to connect a 5621SW and a 9620 as they do the same thing.
The most interesting part is that for a short while I can ping the handset from the main network, then when the boot of the handset finishes, pings die.

Confused