Does anyone know the requirements/processes to get a 5624 WiFi handset working on a 3300.

I have a site running an MXe III with MCD 5.0 SP1 PR1. They have purchased a few Mitel 5624 handsets and although I can get past the WiFi authentication and pick up a DHCP lease from the voice VLAN, I cannot get the handset to register with the 3300.

We have created a few 5624 devices within the 'User & Device Configuration' form, they all have passcodes set and the correct sip device capabilities set as 69, COS as per the manual, etc.. if testing from a generic Sip phone, the numbers work fine.

There is a VOIP/SIP settings page on the handset config screen, which I have tried with various settings...but they just don't register.

There is no WSM or programmer cradle, as Mitel said this is not required for just a few handsets.

Any help would be appreciated.

I've never worked with a 5624 but did with a 5610...
Check on the wireless router/repeater, that your extension number you programmed on the controller is entered and assigned to the wireless phone(cant remember where off the top of my head)so that it registers with that extension.

As far as i read from your post it does everything (gets IP etc.) except register and as far as my logic goes it needs to be told with what number it should be registered on the controller.

Hope you get a lightbulb moment from something i said....

Chris

Did you ever get the 5624 to register with the 3300? I am deploying this very soon myself, does the 5624 just require the normal dhcp option 125? I couldn't find any specific dhcp requirements for these devices.

Thanks

Once you get an IP address you can browse to the handset and set up the 3300 controller information (IP address, extension number, PIN, etc.). This looks like an OEM version of the Polycom Spectralink 8440 for the EMEA area. If it is then there is a How To document on MOL in the Tech Support Knowledge Base. Select Mitel Communications Director and search for 8440.

Yes, I did manage to get them working in the end. We actually purchased the programming cradle/cable and set them up using the WinPDM software. This was a much better way of doing it and allowed for the amending of a lot more of the handset features and settings. It also allowed us to create profiles/policies, backup the data of each handset and set a secondary call server for resiliency. A worthwhile purchase for sure.

I've just remembered another point which may be worth mentioning... The site I was installing these handsets had a couple of vMCD user controllers and two MXe III trunking gateways. When I initially registered the 5624 handset on the vMCD, it seemed to work ok, but when I made an external call out through either MXe III trunking gateway, the person I was calling got a 2 second burst of 'NOISE'??? The only way I could get round this was to register the 5624 handset on the MXe Trunking gateway (with resilience to the second MXe gateway). This seemed to resolve the problem.