Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: MitelAvayaNortel on August 30, 2011, 02:51:44 PM
-
Hi,
Has anyone had experience of distortion only on the inbound audio on a IP 5550 console telephone, no other users report any issues.
THe distortion occurs on both internal & external calls.
We have swapped the DSP card in the MXE II but the fault still exists.
Thanks
-
Anything else that the console goes through like SRC?
-
Sorry to sound silly but whats a SRC?
Thanks
-
Not silly figured it would be asked it is Secure Recording Connector by Mitel used in call recording and encryption. That is one time I have seen distorted sound that is why I ask.
-
Hi,
We have no call recording in place at all. As a trial today I have set the Switch Port for the 2 consoles to Full Duplex 100mb to see if this has any effect (a theory was raised in the office that the port might be trying to renegotiate at the time.)
-
As a further change it was suggested I swap the PC to be on a seperate port than the phone. The phone is on VLAN2 and the PC is now on VLAN1. The distortion still occurs.
-
Did you already tried the sound quality through the other handset/headset port.
I don't know how your network setup is, but you could try to connect the console straight to the 2nd LAN port of the MXe. If you still have audio problems, then you could exclude that the problem is within your network (like router, switches; or even QoS, Vlan config).
-
I have a concern about setting the port to be 100 meg full rather that auto neg.
The problem is, since you can't set the 5550 console to be 100 meg full, the auto neg on the console will go to 100 meg half creating collisions. This by it self can create distortion.
I'd set it back to auto neg and then look at the switch port to be sure it did auto neg to 100 meg full.
Ralph
-
Just thinking ahead, would having both LAN ports on the MXE II cause any problems, port 1 goes to 1 HP 2810 & the 2nd to a 2nd 2810 so that in the case of failure of either hp switch the network can continue to function?
-
That can work but has a potential of a routing loop if not setup correctly.
-
I've just checked - the HP switches are all running STP. Does the Mitel need to be running STP as well?
-
I have come across this issue, but it was only on random calls, and the speech was garbled to the point that you could not understand the caller. Is this what you are finding as well?
If so I'll go in to more details, but as it's a long explanation I'll save it for if it's the case!
-
Yes that kind of fits, I wouldn't say perhaps garbled to the point of not being understandable but the receptionists describe the voice as sounding like a Dr Who Darlek.
-
Ah ok, sounds like a slightly different issue.
Anywho, did you change the DSP card out for a DSP or a DSP II ?
If you do a wireshark capture of the keypad does it indicate any errors?
Also what version of MCD are you running?
-
Hi
DSP Card was swapped out like for like (I didn't perform the swap myself but that's what I'm told)
I will have to try to setup a wireshark capture as soon as I can (I will need to configure some port mirroring on the dataswitches.)
We are running MCD 4.0 SP2.
Thanks for your help.
-
Hi
DSP Card was swapped out like for like (I didn't perform the swap myself but that's what I'm told)
I will have to try to setup a wireshark capture as soon as I can (I will need to configure some port mirroring on the dataswitches.)
We are running MCD 4.0 SP2.
Thanks for your help.
We had to change the DSP I card out for a DSP II, as well as upgrading to a newer keypad firmware. I believe (though not 100% sure) that the firmware upgrade that we did was later included in 4.2 SP2.
-
Thanks martyn.
I've been asked by our VAR now to collect a wireshark trace at the time of the distortion on the console, as Mitel suspect there will be an "ARP Broadcast flood" probably from a printer. So far I've only seen the 3300 making ARP requests, but then the distortion hasn't happened today.
How can I check the firmware version of the Keypad?
Thanks
-
What was the solution? Or is it still an issue?
-
Hi,
I meant to post a follow-up the other day. We finally (thanks to another issue that occured) tracked the distortion down to our Enterprise Manager doing a device discovery. Having turned off AutoDiscover the receptionists have never mentioned it again.
Stephen
-
That's interesting.
What other problem pointed you to the issue?
Ralph
-
We found it mostly by chance. A java update stopped the Enterprise Manager service from starting. It was whilst reinstalling the software we got a call from reception complaining of the distortion, then again as the server restarted. From that (and much head scratching) we took a chance that the server performed a discovery on startup. Having turned it off reception have not complained again of distortion.
-
Check your network switch for dscp value 44.
Has this value a priority in your switch?
-
I'm reading all this late, but have you tried plugging the console directly in the 2nd LAN port on the MXe? Just to eliminate the network completely and see if directly console to 3300 you are still having this distortion?
-
Hi
We never did try that because of the intermitent nature of the distortion and the problem that the 3300 & our receptionists are on different floors of the building. It was more our action of last resort if we couldn't find anything else.
It will be my first port of call however if it ever comes back, but with MCD 5 which we should upgrade to next year I'm thinking that the Enterprise Manager server becomes redundant so hopefully we will never have it autodiscover again?
Thanks
Stephen
-
Had this issue turned out to be Java needed an update.