On Tuesday 10 January 2006 10:06, Boris Benko wrote:
>
> 1. I have used GRANDSTREAM BUDGETONE 101 phones. They are declaring,
> they have implement G.168 cancellation measures, I at first I decided to
> go with them.

You still don't understand the echo question. The echo canceller inside VoIP 
phones cancels the echo introduced *BY* the phone, not the echo coming from 
the line. Let alone that the phone should use an acoustic echo canceller so, 
g.167, not g.168.

> I have tested them and it seems they quite effectively 
> nullify echo from most (analog) systems I have tested.

So, your test is wrong, since you cannot cancel the remote echo with an echo 
canceller that cancels local echo.

> 2. I searched for some kind of boards or whatever, for me to put them
> in, in order to nullify echo. No luck. Boards were either quite
> expensive (and not ment for * at all), or I was quite doubtfull, that
> they accually do the work. I'm pretty amazed, that no such solution
> exists.

The solution is to wait few days, I don't know in which other way to say it.

> I'm aware, the problem of echo must be solved as much as close 
> to the source channel (ISDN BRI in this case). But this way, every
> driver have to have their own echo cancelling measures supported and I
> think this is not the most optimal way.

The optimal way is to convince all the telcos to cancel echo at the CO and to 
convince all ISDN users to use echo cancelling PBXs and terminals. Good luck.

> 4. And yes, I have looking to use the echo cancellation in vocodec. iLBC
> guys are declaring

Cancelling echo at codec level is already too late...

> This works.I have not tested *international* TDM calls - where I presume a
> bit more of the delay will enter the game.

Again... compared to the delay introduce by the voip path it does not make any 
difference.

> I know that this is the vISDN list, but...  I will stay on vISDN list
> and will be ready to test the echo canceller, implemented in vISDN. But
> that echo problem bothered me quite a lot and finally I got the
> solution. Pheeewww....

...

-- 
  Daniele Orlandi
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to