Dahdi Saga continues
So when the dahdi config is left empty, just defaultzone=us and loadzone=us, it works except obviously there is no echo canceller. Once I add an echo canceller and set fxsks=1 then callerid fails, it just says OpenZap on the handsets and the audio doesn't start working after some time after the call is answered. Any ideas? Thanks! jlc
Joseph L. Casale wrote:
Once I add an echo canceller and set fxsks=1 then callerid fails,
You could try building DAHDI with OSLEC. Don't put any echo cancel statements in the config file. The steps you want are under "Install OSLEC with DAHDI". http://www.rowetel.com/ucasterisk/oslec.html -- Russell Mosemann
You could try building DAHDI with OSLEC. Don't put any echo cancel statements in the config file. The steps you want >are under "Install OSLEC with DAHDI".
You still need to specify the echo canceller w/ oslec as well though. What do you think the lack of configuration making it work is indicative of? I think for for the price, I might just buy an SPA3102 and be done w/ this nightmare...
"Joseph L. Casale" <jcasale@activenetwerx.com> said:
You still need to specify the echo canceller w/ oslec as well though.
Are you sure? I was under the impression that OSLEC was built in and that there was no choice to turn it on or off. -- Russell Mosemann ________________________________________________________ Concordia University, Nebraska See http://www.cune.edu/ for the latest news and events!
Are you sure? I was under the impression that OSLEC was built in and that there was no choice to turn it on or off.
All the digium dahdi docs and my previous experience with it reference it being activated like any other canceller. Dahdi specifically states all echo cancellers must be manually activated per channel where dahdi_echocan_* => echocanceller=*,1... and the oslec module builds with the same naming convention...
participants (3)
-
Joseph L. Casale
-
Russell Mosemann
-
Russell.Mosemann＠cune.org