Cees de Groot
2004-Feb-24 12:40 UTC
[Asterisk-Users] Echo on Diva Server 2M with melware CAPI
Above says all - I have echocancel=yes in capi.conf's [interfaces], but
this week someone called (analog cordless handset on ISDN TA through
ISDN PSTN to Diva card in * box, then to my Grandstream) and I had a
terrible echo.
AFAIK, echosquelch/echotail are for the built-in chan_capi echo
suppression logic, and only echocancel=yes is needed with the Server 2M,
not?
00:0c.0 Network controller: Eicon Technology Corporation DIVA Server
BRI-2M (rev 01)
CAPI-driver Rev 1.7: loaded
kcapid: thread started with pid 235
capifs: Rev 1.6
capi20: started up with major 68
kcapi: capi20 attached
capi20: Rev 1.14: started up with major 68 (middleware+capifs)
Eicon DIVA - DIDD table (http://www.melware.net)
divadidd: Rel:2.0 Rev:1.13 Build:102-51(local)
Eicon DIVA Server driver (http://www.melware.net)
divas: Rel:2.0 Rev:1.47 Build: 102-52(local)
divas: support for: BRI/PCI adapters
divas: Diva Server BRI-2M PCI bus: 00000000 fn: 00000060 insertion.
PCI: Found IRQ 9 for device 00:0c.0
PCI: Setting latency timer of device 00:0c.0 to 64
divas: bus: 00000000 fn: 00000060 fix latency.
divas: thread started with pid 315
divas: Diva Server BRI-2M PCI IRQ:9 SerNo:411
divas: started with major 254
Real Time Clock Driver v1.10e
Eicon DIVA - CAPI Interface driver (http://www.melware.net)
divacapi: Rel:2.0 Rev:1.24 Build: 102-28(local)
kcapi: driver divacapi attached
kcapi: Controller 1: Diva Server BRI-2M PCI attached
kcapi: card 1 "Diva Server BRI-2M PCI" ready.
kcapi: notify up contr 1
capi: controller 1 up
chan_capi version is 0.3.1
--
Cees de Groot http://www.tric.nl <cg@tric.nl>
tric, the new way helpdesk/ticketing software, VoIP/CTI,
web applications, custom development