From: "Wojciech Tryc" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 24, 2004 7:27 PM
Subject: Re: [Asterisk-Users] tdm (and x100p?) echo - fix is coming!
> I have similar problem with outbound calls...
> Wojtek
> - Original Message -
> From:
I have similar problem with outbound calls...
Wojtek
- Original Message -
From: "Brent Franks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 24, 2004 7:16 PM
Subject: RE: [Asterisk-Users] tdm (and x100p?) echo - fix is coming!
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:asterisk-users-
> [EMAIL PROTECTED] On Behalf Of Rich Adamson
> Sent: Thursday, June 24, 2004 5:01 PM
> Be careful with that thought... here's the three lines that were
> manually changed for testing purposes only (these would have bee
> > > I don't think that I'd play around with other values though. There were
> > > three lines of code changed in chan_zap.c and two of those lines were
> > > dependent on values from each other. Example: changing from 400
> (default)
> > > to 800 required another statement change from "w" to "ww"
> On Thursday 24 June 2004 11:01, Rich Adamson wrote:
> > Per the doc in the configs samples, you have to implement
> > echotraining=800 (instead of "yes")
> > to take advantage of the new code from yesterday.
>
> 800ms -- that's quite a delay between pickup and being able to speak; was that
> t
> > I don't think that I'd play around with other values though. There were
> > three lines of code changed in chan_zap.c and two of those lines were
> > dependent on values from each other. Example: changing from 400
(default)
> > to 800 required another statement change from "w" to "ww". I'd have
On Thursday 24 June 2004 11:01, Rich Adamson wrote:
> Per the doc in the configs samples, you have to implement
> echotraining=800 (instead of "yes")
> to take advantage of the new code from yesterday.
800ms -- that's quite a delay between pickup and being able to speak; was that
the default whe
---snip---
> I don't think that I'd play around with other values though. There were
> three lines of code changed in chan_zap.c and two of those lines were
> dependent on values from each other. Example: changing from 400 (default)
> to 800 required another statement change from "w" to "ww". I'd
On 25/06/2004, at 12:57 AM, Andrew Yager wrote:
I'll see what setting echotraining=800 does for me...
It still sounds good. There was no noticeable echo on the three calls
we tried. Difficult to say whether it is a greater improvement or not,
but I'm sure I'll have a feel for it after tomorrow.
> On Thursday 24 June 2004 09:01, Rich Adamson wrote:
>
> > Per the doc in the configs samples, you have to implement
> > echotraining=800 (instead of "yes")
> > to take advantage of the new code from yesterday.
>
> Just to be clear, to take advantage of the enhancement, do we need to pull the
> > > I am curious did you play with the echotraining flag
> > > echotraining=yes or use the delay values for echotraining=some ms ?
> >
> > Per the doc in the configs samples, you have to implement
> > echotraining=800 (instead of "yes") to take advantage of the new code
> from >yesterday.
> I'd
Ryan Courtnage wrote:
Just to be clear, to take advantage of the enhancement, do we need to pull the
latest Zaptel, or Asterisk ... or both?
Anytime you update Asterisk you should always get a new Zaptel and
libpri (if you are using it).
I always do make clean install's everywhere too, just for
The change is only to chan_zap.c
... Since the changes were only to chan_zap.c, I'll have
to guess it will improve the historic x100p echo issues as well, and
...
So you should just need to pull the latest version of asterisk,
depending on the age of your zaptel driver.
Andrew
___
> > Per the doc in the configs samples, you have to implement
> echotraining=800 (instead of
> > "yes") to take advantage of the new code from yesterday.
>
> Was this in the new samples from the CVS?
Yes. I did a full Head checkout this morning, and the comments
were included in the /usr/src/aste
Well there you go...
No I hadn't done that.
And it still sounded OK. Which is quite bizzare. Yesterday I has having
terrible echo issues. Today none at all.
*sigh*
I'll see what setting echotraining=800 does for me...
Andrew
_
Andrew Yager
Real World Technology Solutions
R
On Thursday 24 June 2004 09:01, Rich Adamson wrote:
> Per the doc in the configs samples, you have to implement
> echotraining=800 (instead of "yes")
> to take advantage of the new code from yesterday.
Just to be clear, to take advantage of the enhancement, do we need to pull the
latest Zaptel,
> > I am curious did you play with the echotraining flag
> > echotraining=yes or use the delay values for echotraining=some ms ?
>
> Per the doc in the configs samples, you have to implement
> echotraining=800 (instead of "yes") to take advantage of the new code
from >yesterday.
I'd suggest that o
> Per the doc in the configs samples, you have to implement
echotraining=800 (instead of
> "yes") to take advantage of the new code from yesterday.
Was this in the new samples from the CVS?
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.
> > I've just done the upgrade on my test asterisk system. On a series of
> > outgoing PSTN calls via our TDM31B there was no detectable echo.
> I am curious did you play with the echotraining flag
> echotraining=yes or use the delay values for echotraining=some ms ?
Per the doc in the configs s
> I've just done the upgrade on my test asterisk system. On a series of
> outgoing PSTN calls via our TDM31B there was no detectable echo.
I am curious did you play with the echotraining flag
echotraining=yes or use the delay values for echotraining=some ms ?
_
Just to further update this issue:
Three simple source code changes (testing-only at this point) resulted
in zero detectable echo on all incoming and outgoing tdm pstn calls,
even in the first second or two. I've not noticed any unusual side
effects at all. Since the changes were only to chan_zap.c
The echo fix went into Head cvs late yesterday (CDT). I don't have an
x100p installed right now, but I'd strongly suggest doing a new
checkout and test it. Greater than 70% chance its fixed.
> Beside of problem of CallerID not working in several countries, what
> special
I'm excited.
At the moment we're using aggressive echo cancellation - which is nice,
and works - but it would be great to not have to complete kill the
other person's voice when speak.
Looking forward to trying it a bit later...
Andrew
_
On 24/06/2004, at 11:54 AM, Isamar
Beside of problem of CallerID not working in several countries, what
specially I still don't know if it's a X100P's limitation or Zap driver
limitation, the major problem with this devices is no doubt the echo.
If you guys can solve this with tdms and x100ps, it's gonna be a big
step.
On Wed, 23
24 matches
Mail list logo
