loud crackling noise on calls/one way audio on calls

[tangodelta]

Since the day one roll out of our 3300MXe we have been experiencing loud crackling noises on calls. At first it was reported on external calls so naturally the problem was said to be TDM trunks. Soon ater the problem was identified on in house calls some on the same VLAN. Today and yesterday I experienced this myself on calls from the same router, a different router in the same building, calls over IP trunks to another 3300 in the cluster and calls over T1/D4 E&M trunks. It seems to be getting worse.

Any thoughts/suggestions other than going back to the old reliable for 20 years CBX? Perhaps making all telephones attached to the 3300 analogs and buying cheap phones at something-mart?

TD

 

[RotaryDialTommy]

Nothing like a old ROLM 8000 or 9000 !

 

[LoopyLou]

How about carrier pigeons! Smoke signals!

Seriously the key point is that you are getting it on a variety of call types. If it was TDM i.e loop trunk or PRI channel then you could legitimately say it might be an issue with the carrier or even the Mitel hardware. However if it is true you get it IP set to IP set then you have to look at the network. Once an IP set to IP set call is setup audio streams directly between the IP of phone A and phone B, There is no involvement of the Mitel controller(s). That says network. One way audio is network. The only other possibility I can think of on IP set to IP set is the possibility that the firmware that got downloaded to the phone is corrupted some how or whatever is powering the sets is screwed up.

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[danramirez]

Noise on internal calls??? From ip phone to ip phone?

What kind of switches are there?

Any alarms on the 3300?

Have you opened a ticket with the mitel support?

http://www.hatkana.com

http://www.wtelecom.com

 

[Lundah]

Sounds like a network (maybe QoS?) problem since it's even happening between IP sets on the same network. The RSTP stream on set-to-set calls doesn't touch the 3300 at all.

 

[kwbMitel]

Check your maintenance logs for E2T errors, lost packets and/or jitter.

QOS is your friend.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[tangodelta]

I think I knew that IP-IP calls no longer touch the 3300 after setup. There is a very nice PDF document showing exactly how different types of calls work. I just need to find it amongst all the other very nice PDF documents and make a shortcut to it. I was actually looking at it a week or so ago before the next crises came up.

Yeah, I am whining a little here but will get it all sorted out eventually. Management is having a little problem wrapping their heads around telephones growing from an additional duty requiring 5% of one techs time to a job requiring 25% of five team members time. Some of that time is spent actually implementing the work arounds necessary to get the system to do what is required. A lot is spent chasing problems until told not to until the problem comes up again. Then back to the original work around. One of the largest problems has been the Oasis voice recorder. It was advertised as being able to record any Dn or trunk we wanted. Turns out it will not record an individual trunk using DTS and you have to fool it in to thinking the trunk is a Dn. Since users insist that an individual button on an IP phone ring when a call comes in on a trunk and be used to make outgoing calls on that trunk, it requires trunk intercept Dns and doing a directory translation from the intercept Dn to the speed dial that does a ARD route select through a trunk group of one trunk. All to make Oasis record. We would be better off running copper to an analog recorder except that we need to buy more hardware for that.

That 25% of the team member's time is spent as needed depending on the crisis de jour. Plus no one is sure who is working on what problem.

I believe that a ticket has been opened with Mitel but it has probably been buried under many other tickets opened with our tech support person about issues that are "in the book". I would have to check to see who opened the ticket and what the status is.

The switches are all Cisco and the local ones were upgraded to PoE in anticipation of the switch to VoIP. QoS is supposed to be implemented but every so often we find a switch was overlooked. There are at least 10 switches involved in the local facility. One of the the solutions to individual problems has been to reboot the phone (mostly 5360s) which can cure a problem that may no longer be there as this noise comes and goes seemingly randomly. I think users are getting used to the problem and just accepting that this is the way magic jack is going to work. I also suspect looking at logs that they are rebooting their own phones. Maintenance logs don't show E2T errors, lost packets and/or jitter. At least I don't think so but the logs are huge as this system has many many problems.

Well, thanks for pointing me back to the network and for listening. Assuming anyone still is reading at this point. I am newly motivated to make a list of all the problems and confront those in charge with making some priorities.

TD

 

[RotaryDialTommy]

I had been working on the Mitel line of PBX since the early 1980's . I liked their switches all the way thru the 2000 dark & light . When they brought out the 3300 , that's when I started to plan my retirement . It is very difficult to maintain if you cannot have access to the network it resides on . RIP telecom techs .

 

[LoopyLou]

Once the network is setup you don't really need to touch it again and there should not be a lot of issues. I have customers who have had VoIP for up to 10 years without any real problems.

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[tangodelta]

Thanks for the words of encouragement LoopyLou. What you say may be true but many hands touch this network daily implementing varoius patches and upgrades. Non of the touchers are phone people. The joys of sharing the network with "THE network