| Summary: | ASTERISK-00380: [request] Documentation for Algorithm Details for Echo Cancellers | ||
| Reporter: | sbesch (sbesch) | Labels: | |
| Date Opened: | 2003-10-13 10:36:31 | Date Closed: | 2011-06-07 14:05:07 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Documentation |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Only one of the echo cancellers in * identifies itself (Mark's original canceller is Simple LMS with Doubletalk detection#), and then, the ID is only obtained by reading the source code. The rest - mark2, mark3, steve2, steve3 - have no ID of the algorithm at all. Proper selection of an echo canceller is dependent upon knowing the algorithm. You should include training performance (if known), tail length, weighting mechanism, microseconds/tap, adjustability of tap count, etc. Once they are identified, one could consult the literature for information about the conditions for which each algorithm is ideal: is it best for room echo associated with speaker phones, is it best for cancelling echo from hybrid imbalance, etc. | ||
| Comments: | By: Brian West (bkw918) 2004-04-17 22:58:17 I wish I knew where to get the info... thats more or less a trial and error thing to see what works and doesn't work. I will see if I can dig up something to put in the README bkw | ||