Mitel 5624 Wireless SIP Connection Issue

[Felix]

Hi,

I am having issues with a customer and their 5624 handsets. The connection to the Mitel seems to drop quite frequently on all the handsets with the message on the handsets saying "no network".

I know this points to an issue with their network but once I reset the phones the connection is restored. The signal strength is pretty good and when I am actually in a call roaming around the building the calls do not seem to drop.

They are also having issues with battery life which I think is relating to the phones roaming for a signal.

The customer user Ruckus wifi.

I have noticed in the WLAN info that the DTIM value is 1 and the docs say this needs to be 5 which does improve battery life but would this point to the phones constantly losing connection with the Mitel.

Has anyone else had any issues with this? Any advice would be much appreciated.

[MitelEndUser]

This isn't what you are going to want to hear, but I'll say it anyway!

We have never managed to get our 5624 wireless phones stable.  We have spent 14 months trying different solutions.  So many people have been in to investigate it, we have lost count!  Every time we have our hopes raised thinking we have found a solution, the 5624s say "no channel available".

My only comment to you would be - look at your network traffic.  We were convinced that somehow, the traffic from the 5624 was sometimes not getting to the 3300, or vice versa.  At sites where there was less network traffic, there were far less occurrences of "no channel available".

Ours were on HP at multiple sites, and the wireless coverage was excellent.

If you have someone who can use WireShark, I would start there.

[MitelKw]

Hi,
I have recently installed the Mitel 5624 SIP phones. All seems to be fine. My Only problem is the Call gets dropped exactly after 30seconds. @Felix... I have tried the easy deployment method. There's no network issue or No Channel lost issues.

Basic Config:
SSID: AWS-INIT
Security key: WPA-PSK / WPA2-PSK
WPA-PSK passphrase: AWS-INIT

DHCP mode: On
802.11 protocol: 802.11b/g/n
802.11b/g/n channels: 1,6,11
World mode regulatory domain: World mode (802.11d)

Check for these values in the Handsets and Templates . Change the values to match. Hope it will help you .
Later on, You can change the passphrase for security.

[Felix]

Thanks for all your suggestions. This seems to be happening to another site I have just installed these 5624 handsets. It looks like a roaming issue between AP's as I can see the signal strength dropping when switching from AP to AP in the site survey mode.

I will keep digging.

[Felix]

These are the type of information I am seeing the 5624 syslog.


2016-02-04 14:00:35.282,125 - System status: WLAN authentication timed out
2016-02-04 14:00:40.290,375 - System status: No network
2016-02-04 14:00:41.143,250 - Battery level: 4156 mV
2016-02-04 14:00:41.147,375 - AP: 00:00:00:00:00:00 - RSSI: 0 - Channel: 0 - QoS: None - DSCP voice: 0x2e signaling: 0x18
2016-02-04 14:00:46.725,000 - System status: WLAN authentication timed out
2016-02-04 14:00:47.109,000 - Configuring WLAN driver
2016-02-04 14:00:47.112,625 - ESSID: ****** (length: 7)
2016-02-04 14:00:47.113,250 - Voice power save mode: active
2016-02-04 14:00:47.215,500 - Security mode: WPA-PSK / WPA2-PSK
2016-02-04 14:00:47.216,000 - Association: WPA / WPA2
2016-02-04 14:00:47.216,375 - Authentication: PSK
2016-02-04 14:00:47.216,750 - Encryption: TKIP / AES-CCMP

[Dogbreath]

I have deployed ~10 of these at a site with a Ruckus WLAN [ZD1112 version 9.4, zf7363 APs], and they appear to be working fine - deployment was 2.5 years ago. This is quite a small deployment with low traffic volume, however.

In that time the only thing we've had to do is supply replacement batteries for a few of the more heavily-used handsets.

I wouldn't bother with 5624s again. They were a pain to program - having to use a cradle and some bit of Windows software? c'mon, it's the 21st century! Despite being Mitel-branded, the handsets can't access the directory on the phone system.

[Felix]

Thanks for this. Could you let me know the parameters you have set via the WinPDM?

I have chopped and changed so many of these now I have lost count!

[Felix]

Think I may have solved the issue, the connection problem was when the phone was in idle and was roaming through the WiFi network. The connection dropped and then had to wait for 5 seconds to reconnect to the AP.

I changed the 802.11 protocol from 802.11b/g/n to 802.11b/g.

This seemed to have worked and when carrying out further testing I could not replicate the fault after this.

If anyone else is getting stuck I would give that a try.

[Fraser-H]

Think I may have solved the issue, the connection problem was when the phone was in idle and was roaming through the WiFi network. The connection dropped and then had to wait for 5 seconds to reconnect to the AP.

I changed the 802.11 protocol from 802.11b/g/n to 802.11b/g.

This seemed to have worked and when carrying out further testing I could not replicate the fault after this.

If anyone else is getting stuck I would give that a try.

Hi Felix,

I'm having similar issues with our 5624's. Where did you disable the N option? On the Ruckus?

[Felix]

Hi,

This was on the WinPDM software.