Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IP Hardphone Echo
- Thread starter gbwall63
- Start date
Review the tech tips on the Docs CD (or support.avaya.com) a few of them address echo. Could be headsets, analog trunk related, etc.
If you don't find your answer there post more specific info on your setup - analog/digital trunks, what kind of headsets if any, etc.
Peter
If you don't find your answer there post more specific info on your setup - analog/digital trunks, what kind of headsets if any, etc.
Peter
- Thread starter
- #3
The gain settings are in the line form, under the analog tab.
Are you getting echo from the users voice, or from DTMF digits when dialing?
Peter
PS Sorry about the delay in responding, I've been out of town replacing a definity with an IP office *grin*
Are you getting echo from the users voice, or from DTMF digits when dialing?
Peter
PS Sorry about the delay in responding, I've been out of town replacing a definity with an IP office *grin*
- Thread starter
- #5
- Thread starter
- #7
Well... I think I spoke too quickly.
My hope that this was a BellSouth analog trunk problem was not well placed. They have tested all of the lines and have not found anything wrong. It turns out that the ‘trouble’ that they reported on Monday night was because they did not detect a 2500 set at the end of the line. Meanwhile, our echo problem continues.
Here is a more detailed description of this problem:
1. The echo occurs when the person on the 46xx set speaks. They hear a somewhat garbled echo of their voice that inhibits their ability to hear the other party.
2. The problem occurs on outside calls (inbound or outbound). It does not occur between internal extensions.
3. The problem occurs frequently but not always. Some outside calls are clear. This observation is what led me to believe the problem was on specific trunk lines.
I'm running out of ideas. HELP!!!
My hope that this was a BellSouth analog trunk problem was not well placed. They have tested all of the lines and have not found anything wrong. It turns out that the ‘trouble’ that they reported on Monday night was because they did not detect a 2500 set at the end of the line. Meanwhile, our echo problem continues.
Here is a more detailed description of this problem:
1. The echo occurs when the person on the 46xx set speaks. They hear a somewhat garbled echo of their voice that inhibits their ability to hear the other party.
2. The problem occurs on outside calls (inbound or outbound). It does not occur between internal extensions.
3. The problem occurs frequently but not always. Some outside calls are clear. This observation is what led me to believe the problem was on specific trunk lines.
I'm running out of ideas. HELP!!!
- Thread starter
- #9
- Thread starter
- #11
Here is the results of my changes:
Outside calls on the 6408 are always clear. No echo occurs.
I changed the compression on all IP phones to G.711 rather than G.729. I was thinking this may help since the algorithimic delay for G.711 is half that of G.729. However, the echo problem on outside calls still occurs.
The echo problem does not occur every time. Some calls are perfectly clear.
Other suggestions from the experts?
Outside calls on the 6408 are always clear. No echo occurs.
I changed the compression on all IP phones to G.711 rather than G.729. I was thinking this may help since the algorithimic delay for G.711 is half that of G.729. However, the echo problem on outside calls still occurs.
The echo problem does not occur every time. Some calls are perfectly clear.
Other suggestions from the experts?
You could try toying with the DB levels on the suspect line.
When an incoming echo is too loud or too latent, echo cancellers have trouble dealing with it. You can try to mitigate the "too loud" part by adjusting outbound DB levels, this will make the outbound signal quieter, and by extension the inbound echo as well.
The latent part is solved by having QOS implementations on the network. That however is a many faceted issue.
When an incoming echo is too loud or too latent, echo cancellers have trouble dealing with it. You can try to mitigate the "too loud" part by adjusting outbound DB levels, this will make the outbound signal quieter, and by extension the inbound echo as well.
The latent part is solved by having QOS implementations on the network. That however is a many faceted issue.
I had this problem an I solved it by taking two measures.
Putting the db gain level of the trunk lines down and experiment with these values until you get the expected quality.
Choosing G.711 ALAW 64Kbps codec for your IP Phone will improve the quality of the voice considerably.
Hope you find this helpful
Putting the db gain level of the trunk lines down and experiment with these values until you get the expected quality.
Choosing G.711 ALAW 64Kbps codec for your IP Phone will improve the quality of the voice considerably.
Hope you find this helpful
crashtest1000
Vendor
Make sure they are not using headsets with an amp this will cause echo.
You may find the problem is only to particular locations. In this case the issue is the far end handsets. You may need to go to the new VCM this has improved echo cancellation and helps compensate
![[cheers]](/data/assets/smilies/cheers.gif "[cheers] [cheers]")
You may find the problem is only to particular locations. In this case the issue is the far end handsets. You may need to go to the new VCM this has improved echo cancellation and helps compensate
- Status
