Anyone know of a discussion or support group for Mitel 5220 IP Phones?
Handsets on the same switch are experiencing noises, like a helicopter chopping noise, between each other? I've seen similiar issues with Cisco CallManager in the past that were software bugs in the handsets, app load, VAD, etc.
Any suggestions? Our local Mitel installler doesn't know VAD from DAD and isn't helpful. He has to call Canada for support every time. This guy swears the network QoS is the problem, but I disagree. Two L2 ports on the same 3550 switch don't need QoS for VoIP to work without problems. There is no routing. I think he might have VAD problems with handset firmware.
That would be OK as long as they are arriving without jitter, drops, etc. Again, a sniffer capture would tell you a great deal about what is happening here including whether the stream is between phone or the phone and the server.
http://ethereal.com/ has a free sniffer with great analysis tools for RTP traffic. You can even play it out as audio to see if the stream or the phone is the problem.
Have you tried to contact Mitel at the link I provided to see if they could shed some light on the issue?
We are in the process of implementing about 60 5220 phones here on their 3300 pbx. We encountered a lot of problems with the PBX software which was initially blamed on the network/QoS setup. The way I proved them wrong was by plugging 2 phones directly to the PBX (use a power brick so they don't blame the Power over Ethernet source like they did with me) and make phone calls. If you still get problems. It's definintly the PBX. Let me know how it turns out because are install is a nightmare.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.