* Muddy voice sound - like people have their hands over their mouths when they talk. It is unbearable when on a conference call. My cell phone sounded 5x better.
* Drop outs - while the call is dropped out, there is a quiet hiss for 1-2 seconds. When the call continues, it has a "sped up" version of what I missed (unintelligible) and then the call continues normally. I have to ask the caller to repeat what they said.
My Technical Deployment
I am trying to use QOS engine on my DLink wireless router because the InsightBB cable modem will not work with the ideal QOS wiring recommendation. I have InsightBB Business Class Cable Internet 10MB/1MB.
My Test Results:
VoIP test statistics
Jitter: you --> server: 1.8 ms
Jitter: server --> you: 3.5 ms
Packet loss: you --> server: 1.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 3.8
Speed test statistics
Download speed: 4561928 bps
Upload speed: 857632 bps
Download quality of service: 55 %
Upload quality of service: 98 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 388 ms
Average download pause: 4 ms
Minimum round trip time to server: 69 ms
Average round trip time to server: 71 ms
Estimated download bandwidth: 7600000bps
Route concurrency: 1.6659623
Download TCP forced idle: 4 %
Maximum route speed: 7598256bps
Anyone else made their way through these problems?
Many females have voice characteristics that cause a touchtone decoder to falsely detect a touchtone. It is suspected that there is a touchtone decoder on the incoming audio path that totally blocks the path when a touchtone is detected. In tests that I have run it does sound like a hiss when a touchtone is received. They are supposed to be investigating to determine why touchtones are being blocked.
If the people at the other end of the conference call are using a speakerphone and they have a high background noise level in the room, that can make it difficult to understand what is being said.
Do your evaluation with normal phones at both ends.
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
Callers are not using a speaker phone. These are call-in conferences where everyone is using a regular phone.
But the problem happens even on 1:1 calls where we're both using a regular phone.
I just had Ooma drop my first call ever (completely) - it went to the Ooma dialtone. Sigh.
Are you setting it using a service priority or by MAC address?
What level of priority did you set the OOMA to?
What other QOS settings have you made and what are the priority's?
Lower the number in you QoS engine until you can get it to 90% or better.