Echo on PRI after upgrading to Asterisk 1.6.2 from 1.2

Home » Asterisk Users » Echo on PRI after upgrading to Asterisk 1.6.2 from 1.2
Asterisk Users 5 Comments

I’ve recently upgraded an Asterisk system from 1.2 to 1.6.2 (did a
full reformat and recompile) and I started getting echo over the PRI.

I’ve tried the default settings for echo in the system.conf file as
well as I’ve compiled OSLEC to try and see if thats any better.

I’m not sure what to try next. Does anyone have any suggestions?

5 thoughts on - Echo on PRI after upgrading to Asterisk 1.6.2 from 1.2

  • [root@voice ~]# cat /etc/dahdi/system.conf
    # Autogenerated by /usr/sbin/dahdi_genconf on Fri Sep 24 21:44:03 2010
    # If you edit this file and execute /usr/sbin/dahdi_genconf again,
    # your manual changes will be LOST.
    # Dahdi Configuration File
    #
    # This file is parsed by the Dahdi Configurator, dahdi_cfg
    #
    # Span 1: WCT1/0 “Wildcard TE120P Card 0” (MASTER)
    span=1,1,0,esf,b8zs
    # termtype: te
    bchan=1-23
    dchan=24
    echocanceller=OSLEC,1-23

    # Global data

    loadzone = us
    defaultzone = us

    ****This might be my problem?***
    [root@voice ~]# grep -E “^echo” /etc/asterisk/chan_dahdi.conf
    *
    *So I added this under [channels]:
    echocancel=yes
    echocancelwhenbridged=no
    echotraining=800*

    [root@voice ~]# dahdi_scan
    [1]
    active=yes
    alarms=OK
    description=Wildcard TE120P Card 0
    name=WCT1/0
    manufacturer=Digium
    devicetype=Wildcard TE120P
    location=PCI Bus 03 Slot 12
    basechan=1
    totchans=24
    irq=217
    type=digital-T1
    syncsrc=1
    lbo=0 db (CSU)/0-133 feet (DSX-1)
    coding_opts=B8ZS,AMI
    framing_opts=ESF,D4
    coding=B8ZS
    framing=ESF

    [root@voice ~]# lsmod | grep dahdi
    dahdi_echocan_oslec 6912 27
    echo 9600 1 dahdi_echocan_oslec
    dahdi_transcode 12164 1 wctc4xxp
    dahdi_voicebus 45760 2 wctdm24xxp,wcte12xp
    dahdi 196552 78
    dahdi_echocan_oslec,xpp,dahdi_transcode,wcb4xxp,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,wct4xxp
    crc_ccitt 6337 2 wctdm24xxp,dahdi

  • Most likely (unless you were including another file that included that
    definition). Did this resolve your problem?

  • I did an update on a server last year, had the same problem. I needed
    to explicitly set echocancel=yes in my configs, before 1.6 it was
    enabled by default.

  • I haven’t heard if this fixed it yet. However I was seeing the echo
    cancelers loaded before so I never realized I’d have to do this. Its a
    FreePBX install also so I checked all the include files and didn’t see a
    reference to these values anywhere.

    Thanks everyone for the input, I should know soon if it is the fix.

    ~Jared

    On Fri, Oct 15, 2010 at 3:56 PM, Paul Belanger paul.belanger@polybeacon.com | IRC: pabelanger (Freenode)