4620 & User Hot desking 2

[gjbrown]

Hi,

I have a user using a 4620 phone across a LAN to LAN VPN. My IPO 2.0 is configured to automatically create extensions. When My user first boots the 4620 an extension is created and they can use the phone perfectly. If the user reboots the 4620 the user is told the extension is busy. The only way to rectify this is to download the IPO config delete the extension, push the configuration back to the IPO and reboot it.

Any ideas would be greatly appreciated.
Thank you
Gary

 

[IPGuru]

IIRC when the 4620 says already in use or somthing similar press the hash key a couple of times & it will resynch with the IPO.

Morrac can probably tell you the exact wording on the display, I have not got access to mine at present.

 

[gjbrown]

Thank you IPGuru for your response.
Resync I suspect would happen as a matter of course with the 4620.

This issue does seem to be linked directly with the existence of the extension rather than synchronisation. On login (Post initial extension creation) completion the 4620 displays 'No User :B' or something to that effect rather than the User name.

FYI:
The user is a hot desk user.
The extension number moves with the user.
An incoming call route points a specific number to this user.
Each time a new hot desk user extension is entered on the 4620 the phone works perfectly. Every subsequent login for any user extension results in extension busy issue.

Does anyone know how long it would take to resync itself?

Thanks
Gary

 

[Morrack]

You are probably seeing "Extension in use, press # to continue". Press #, then you should see "Deregister user? * Yes # No" (or possibly vice-versa). Select yes, then you should be good to go. If you don't get the deregister user option I suspect your hardphones are using old firmware.

Peter

 

[gjbrown]

Thanks guys. I will ensure I have the latest firmware on the IP 4620 phone. Deregistering the user currently has no effect.

 

[gjbrown]

Updating the firmware and mashing the '#' key causes it to re-registar. Thanks Guys

 

[gjbrown]

Issue was an incompatibility in the Netscreen.

Juniper Technote:
There are a few known issues with using Avaya VoIP phones to communicate across a NetScreen firewall device. Avaya phones use a special format within the H.323 payload for which the ALG does not accommodate. Avaya operates in Routed Gatekeeper mode, which is not supported in ScreenOS 5.0.0 (only Gatekeeper Direct Mode is supported).

The workaround for this is to either disable or ignore the H.323 ALG. For this to work, the policy must use H.323 as a service, and specify Application - Ignore.

Full support for Avaya Gatekeeper is supported in ScreenOS 5.1.0

Fix:
Version 5.1 code will be released on the 29th Oct 2004 or so I'm told