| Summary: | ASTERISK-02065: Over amplified echo at start of call | ||
| Reporter: | glendale2x (glendale2x) | Labels: | |
| Date Opened: | 2004-07-19 12:28:02 | Date Closed: | 2011-06-07 14:05:24 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When a call rings on a zap channel for 15 seconds or more, the echo canceler seems to "turn up the volume" to such a level that when an extension is answered, there is extremely loud echo fed back to the ext that answered the call. As it trains itself during the first 30 seconds of the call, the volume is reduced to less painful levels. However, it is so loud at the beginning, the audio is clipped and it is impossible to hear anything. Using the ztmonitor tool, I can see that both RX and TX values are pegged to maximum for the duration of the loud echo. It seems the RX volume creeps up a little more with each progressive ring that is sent down the line (i.e. after going through an IVR), until maximum RX volume is reached. I have been able to reproduce this problem consistently after letting the call ring for 15 seconds or more before picking up an extention. Setting the number of taps to 64 or less removes the problem, however, the echo cancellation never takes effect and echo is present throughout the call. Settings for echotraining did not make a difference. This also only happens on inbound calls, not outbound calls. Maybe the solution is to disable the echo canceler while a ringtone is detected. I'm using the mark2 canceler, no aggressive. If any further information is needed, I'll be happy to provide it. | ||
| Comments: | By: Olle Johansson (oej) 2004-07-19 12:48:44 Version of Asterisk? Operating system? See the instructions on how to report bugs on the front page for more questions. THank you. /Olle By: glendale2x (glendale2x) 2004-07-19 12:59:18 Present on all versions I can get my hands on, although I only have three different versions of Linux. The primary machine is a Red Hat Linux 9 box. I walked back through CVS up to a month with no luck, too. I've tried custom kernels, different CPU's and boards, more memory, moved interrupts around, ran * by itself, and tried every combination of echo cancelers and zapata.conf settings I could think of. I've been working on this for about a month, and I've run out of hardware and settings to play with, so I thought I'd try the bugtracker next. Unfortunately I don't have the resources at the moment to build another machine to test this on, so I'm going to stick with the RH9 box. It's AMD based, if that makes a difference. (It really shouldn't.) By: glendale2x (glendale2x) 2004-07-19 13:44:27 This is what ztmonitor looks like when the line is ringing: ( # = Audio Level * = Max Audio Hit ) <----------------(RX)----------------> <----------------(TX)----------------> ###################################* ##################################* extentions.conf: exten => s,1,Answer exten => s,2,Wait(2) exten => s,3,Dial(SIP/204,30) By: Mark Spencer (markster) 2004-07-19 14:03:55 As this is a tech support issue, please pursue this through Digium technical support first. If you are for any reason unable to find a satisfactory solution through them, you may contact me directly. | ||