Ip Phone 1608 on Customer VPN unregisters every 6 mins

[desphoneguy]

We have a customer with an IPO 500V2 current release 7 software running.

They have a Cisco and a Netgear router configured for VPN.

They have 2 1608 IP phones located at netgear router and the IP office located at the cisco router.

VPN is established and stays established. The ip phone will register to the IP office and will work for exactly 6 minutes and whether they are idle or on a call they will unregister and reboot.

HTTP server is the IPO.

Can anyone help?

 

[Darby123]

This may be down to a setting on the VPN. E.g if there is no traffic being presented over the VPN the VPN may drop out. There maybe a setting on the Cisco to enable ping keep alive over the VPN.

APSS
PASMI

Aastra Accredited Expert

 

[desphoneguy]

The VPN appears to stay up, it is not going down. The phone even resets during a conversation.

 

[amriddle01]

It IS a timer on the VPN, even though the VPN stays up there are timers that renogotiate the link and it drops the handsets link even though the tunnel itself stays up, it has been posted here several times and every time it is the VPN lifetime timer (or similarly named depending on router). It can be proved by placing the handset local and it will not drop out, the handset and system don't know a VPN is involved to treat the traffic any differently

Not happy with Avaya ATM....

http://www.ipoffice.tel

 

[desphoneguy]

We have a bit more info.

During the Bootup sequence we are getting an error message on the phone saying "BAD SVR"

 

[latitude12]

I suspect the problem is the TCP keepalives from the phone are not reaching the IPO, the IPO then sends an unregister request (URQ) to the phone that causes it to reset. You can check this by running a sysmon trace (with H323 enabled)and capturing a phone reset. What is the Cisco device being used? Cisco inspection features have been known to interfere with Avaya H323 traffic.

Re the "BAD SVR" message, sounds like the file server address is incorrect/unconfigured, that wouldn't cause this problem.

 

[desphoneguy]

We got the "BAD SVR" sorted out. It seemed to be a one time thing because customer made changes on the phone.

We are getting the customer to ship the phones to us so we can try them locally.

I will keep things updated