no dahdi calls after last elastix update

Discussion in 'General' started by witekprytek, Jun 28, 2010.

  1. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    I have made an elastix update (using yum)

    I'm not able to make outbound and inbound calls via E1 trunk (Sangoma A101DE card)
    Card status looks OK, dahdi module are loaded

    I have tried remove zap(dahdi compatibility mode) trunk from elastix and created it again without success.
    (as described in http://www.elastix.org/en/component/kun ... calls.html
    but I do not see "dahdi channel")

    No dahdi channels are registered in asterisk.
    I'm not able to do "dahdi show channels" too under asterisk cli

    Any suggestions?
    Is any way to go back to downgrade the system?
    help me please


    Everything looks good - card is up no errors. Carrier don't see any errors on trunk all channels are up, but during calling I have a message "
    Dial("SIP/898-0000031f", "DAHDI/g0/655999001|300|wW") in new stack
    == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [s@macro-dialout-trunk:20] Goto("SIP/898-0000031f", "s-CHANUNAVAIL|1") in new stack
    -- Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
    -- Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] GotoIf("SIP/898-0000031f", "1?noreport") in new stack
    -- Goto (macro-dialout-trunk,s-CHANUNAVAIL,3)
    -- Executing [s-CHANUNAVAIL@macro-dialout-trunk:3] NoOp("SIP/898-0000031f", "TRUNK Dial failed due to CHANUNAVAIL (hangupcause: 66)

    Asterisk 1.4.33.1 built by root @ rpmbuild32.elastix.palosanto.com on a i686 running Linux on 2010-06-23 16:17:01 UTC
    The 'show version' command is deprecated and will be removed in a future release. Please use 'core show version' instead.

    show modules like dahdi
    Module Description Use Count
    chan_dahdi.so DAHDI Telephony w/PRI 0
    app_dahdiscan.so Scan Zap channels application 0
    app_dahdiras.so DAHDI RAS Application 0
    codec_dahdi.so Generic DAHDI Transcoder Codec Translato 0
    app_dahdibarge.so Barge in on channel application 0


    dahdi_scan show
    [1]
    active=yes
    alarms=OK
    description=wanpipe1 card 0
    name=WPE1/0
    manufacturer=
    devicetype=
    location=
    basechan=1
    totchans=31
    irq=0
    type=digital-
    syncsrc=0
    lbo=0 db (CSU)/0-133 feet (DSX-1)
    coding_opts=HDB3
    framing_opts=CCS,CRC4
    coding=HDB3
    framing=CCS
     
  2. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    It's seems to be some system inconsistence after upgrade

    I have found something like this in the system logs:
    [Jun 28 14:40:35] VERBOSE[3069] logger.c: == Parsing '/etc/asterisk/dahdi-channels.conf': [Jun 28 14:40:35] VERBOSE[3069] logger.c: Found
    [Jun 28 14:40:35] ERROR[3069] chan_dahdi.c: Unable to get span status: Inappropriate ioctl for device
    [Jun 28 14:40:35] ERROR[3069] chan_dahdi.c: Unable to register channel '1-15,17-31'

    on some forums this error is reported when we have some kernel modules version mismatch, but I did not find any way to fix or check it :-(

    kernel-module-dahdi-2.2.0.2-6_2.6.18_164.el5
    dahdi-2.2.0.2-6
    kernel-module-dahdi-xen-2.2.0.2-6_2.6.18_164.el5
    dahdi-devel-2.2.0.2-6
     
  3. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    Re:no dahdi calls after last elastix update -bug!

    this is an "internal" discussion :)
    but I have found that this issue is just reported as a bug:
    http://bugs.elastix.org/view.php?id=375

    the only question is - when we can expect new dahdi rpm to fix it? I thing that many elastix 1.6 system which uses dahdi seems to be broken after last upgrade.
     
  4. rafael

    Joined:
    May 14, 2007
    Messages:
    1,454
    Likes Received:
    1
    Re: Re:no dahdi calls after last elastix update -bug!

    witekprytek, please ask that question in the bug report. There is where you are going to get a direct answer fro developers.

    regards,

    rafael
     
  5. finisproductions

    Joined:
    May 4, 2010
    Messages:
    8
    Likes Received:
    0
    I am running Elastix with a Rhino R2T1 card and dual PRI's from my telco. My sys admin ran yum updates over the weekend and we are also unable to make or receive voice calls. I get an error

    "Error [3800]: chan_dahdi.c:8760 mkintf: Unable to get span status: Inappropriate ioctl for device"

    as well as

    "Error [3800]: chan_dahdi.c:13000 build_channels: Unable to register channel '1-23'"

    Tried setting up a new Zap trunk as recommended with no result.

    Any help or suggestions are much appreciated, employees are milling around with nothing to do here (call center).
     
  6. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    There is still no info about fix for this bug in bugtracker.
    Maybe manually compiling dahdi from the digium sources is the right way for now?
    What do you guys think about this idea?

    This is the worst bug I had in system from 1.1 version. It has destroyed production system functionality at all - almost ;-)
     
  7. dkmortensen

    Joined:
    Jun 29, 2010
    Messages:
    10
    Likes Received:
    0
    I have successfully downgraded my system, and it is fully functional again. I have tried to retrace all of my steps. I am pasting the commands below. You can put them in a bash script, or just paste them straight into your ssh session. I'd suggest doing them one-by-one, or making sure that you have a large enough scroll-back buffer so that you can look at them and make sure that there were no errors.

    Also, I take absolutely NO responsibility for you further messing up your system by following these commands. However, this worked for me. I am running Elastix 1.5.2-2. I do not know whether this will work with 1.6.

    Just one tid-bit is that after I downgraded the packages, I did actually have to rebuild my /etc/asterisk/chan_dahdi.conf. I'm not sure whether this is because the initial update yesterday wiped it out, or whether I jacked it up after all of my initial troubleshooting and tinkering yesterday.

    Best of luck. I do expect that they'll have a bug-fix for the upgrade in a day or so (maybe sooner). But I can't wait for that with my production system.

    Also, before you execute these commands, look for any line-breaks that the forum may have forced in. These are all pretty basic linux commands, and if the formatting does look right, it probably isn't. :)

    Here it is:

    Code:
    #Stop asterisk & dahdi
    amportal stop
    /etc/init.d/dahdi stop
    
    cd /tmp
    mkdir asterisk-downgrade
    
    #Make a temporary backup of your configs for safe keeping.
    tar -cf etc-backup-of-dahdi-and-asterisk.tar /etc/asterisk /etc/dahdi
    
    #Download the previous (working) versions of the packages we'll be downgrading
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/dahdi-2.1.0.4-7.i386.rpm
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/dahdi-2.1.0.4-7.i386.rpm
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/dahdi-devel-2.1.0.4-7.i386.rpm
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/kernel-module-dahdi-2.1.0.4-7_2.6.18_92.1.22.el5.i386.rpm
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/asterisk-1.4.24-1.i386.rpm
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/libopenr2-1.1.0-1.i386.rpm
    wget http://repo.elastix.org/elastix/1.5/base/i386/RPMS/asterisk-devel-1.4.24-1.i386.rpm
    wget http://repo.elastix.org/elastix/1.3/base/RPMS/spandsp-0.0.4-2.i386.rpm
    wget http://repo.elastix.org/elastix/1.3/base/RPMS/spandsp-devel-0.0.4-2.i386.rpm
    wget http://repo.elastix.org/elastix/1.3/base/RPMS/libpri-1.4.3-5.i386.rpm
    wget http://repo.elastix.org/elastix/1.3/base/RPMS/libpri-devel-1.4.3-5.i386.rpm
    
    #Remove new packages that are cauisng the problem
    rpm -e asterisk asterisk-devel dahdi dahdi-devel kernel-module-dahdi libopenr2 libpri libpri-devel spandsp spandsp-devel --nodeps
    
    rpm -i *.rpm
    
    #Then to restore your configs:
    cd /etc/asterisk
    
    mv asterisk.conf asterisk.conf.rpmnew-1
    mv chan_dahdi.conf chan_dahdi.conf.rpmnew-1
    mv enum.conf enum.conf.rpmnew-1
    mv extensions.conf extensions.conf.rpmnew-1
    mv features.conf features.conf.rpmnew-1
    mv iax.conf iax.conf.rpmnew-1
    mv indications.conf indications.conf.rpmnew-1
    mv logger.conf logger.conf.rpmnew-1
    mv manager.conf manager.conf.rpmnew-1
    mv meetme.conf meetme.conf.rpmnew-1
    mv modules.conf modules.conf.rpmnew-1
    mv musiconhold.conf musiconhold.conf.rpmnew-1
    mv phone.conf phone.confe.rpmnew-1
    mv queues.conf queues.conf.rpmnew-1
    mv rtp.conf rtp.conf.rpmnew-1
    mv sip.conf sip.conf.rpmnew-1
    mv sip_notify.conf sip_notify.conf.rpmnew-1
    mv voicemail.conf voicemail.conf.rpmnew-1
    
    cp	asterisk.conf.rpmsave		asterisk.conf
    cp	chan_dahdi.conf.rpmsave		chan_dahdi.conf
    cp	enum.conf.rpmsave		enum.conf
    cp	extensions.conf.rpmsave		extensions.conf
    cp	features.conf.rpmsave		features.conf
    cp	iax.conf.rpmsave		iax.conf
    cp	indications.conf.rpmsave		indications.conf
    cp	logger.conf.rpmsave		logger.conf
    cp	manager.conf.rpmsave		manager.conf
    cp	meetme.conf.rpmsave		meetme.conf
    cp	modules.conf.rpmsave		modules.conf
    cp	musiconhold.conf.rpmsave		musiconhold.conf
    cp	phone.conf.rpmsave		phone.confe
    cp	queues.conf.rpmsave		queues.conf
    cp	rtp.conf.rpmsave		rtp.conf
    cp	sip.conf.rpmsave		sip.conf
    cp	sip_notify.conf.rpmsave		sip_notify.conf
    cp	voicemail.conf.rpmsave		voicemail.conf
    
    cd /etc/dahdi
    
    mv modules modules.rpmnew-1
    mv system.conf system.conf.rpmnew-1
    
    cp modules.rpmsave modules
    cp system.conf system.conf.rpmsave
    
    #If all went well, you should be able to start back up now
    /etc/init.d/dahdi start
    amportal start
    
    -
    Doug Mortensen
    Impala Networks Inc
    doug@impalanetworks.com
     
  8. dkmortensen

    Joined:
    Jun 29, 2010
    Messages:
    10
    Likes Received:
    0
    Please let me know if this doesn't work for you, as I could have forgotten something. Still, I think/hope that I didn't.
     
  9. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    Doug: This downgrade it is not good idea for me. As I remember some bugs regarding queue handling in asterisk were fixed in 1.3x.
    I have temporary moved all outgoing calls to backup VoIP trunk and forward all incoming calls on E1 trunk to the VoIp one (on carrier side)

    I have lost all incoming routes of course, so I had to build new IVR with additional menu and forward all incoming calls to it.
     
  10. dkmortensen

    Joined:
    Jun 29, 2010
    Messages:
    10
    Likes Received:
    0
    I'm not sure what you mean regarding 1.3. My method was to downgrade to asterisk-1.4.24.

    I downloaded all packages I could find from the 1.5 repository. Then there were the 4 that I had to grab from the 1.3 repository (spandsp & libpri).

    I determined which versions of each RPM to grab by noting which version of asterisk & dahdi I was running before I initially did the problematic update yesterday. Then after downloading those same RPMs (the versions I had before the updated), I learned which versions they wanted for the dependency packages. There definitely is the possibility that you could go with a newer version of one of these dependency RPMs, and still be fine. But I haven't tried, so I can't tell you.

    We don't use Queues here, so I can't confirm any potential issues there either.

    Anyway, best of luck.
     
  11. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    dkmortensen :
    I have just tested fresh update. Unfortunately it still does not work as it should work. dahdi reportds D-channel errors and chan-dahdi is unable to create channel:
    Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)

    so i don't recommend to use this update in any production enviroment.
    I think that bug is still present because developer use wanpipe version which not correctly support dahdi2.3 - i have reported it on bugtrack.

    So i'm almost decided to use your method to downgrade the system, or I will try to use some "sip e1 gateway" between elastix and e1 carrier.

    This bugs is not acceptable for production version of elastix or any other systems - I do not understand how it could pass tests before the upgraded rpms had been published.
     
  12. dkmortensen

    Joined:
    Jun 29, 2010
    Messages:
    10
    Likes Received:
    0
    I got it working with their new builds/packages. Initially I it was not working for me. But then I discovered that I wasn't booting into the newer kernel which I had installed via yum. After fixing that, I was then able to update the dahdi & rhino kernel modules, and now all is working well.

    You can see my exact steps over in the bug tracker: http://bugs.elastix.org/view.php?id=375

    Hopefully this will work for you too. Best of all, this fixed the issue w/ Ring Group - Confirm Calls, which was why I wanted to update asterisk Monday anway. :)

    -
    Doug
     
  13. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    Doug: what kernel version should be the right one to get it work?
     
  14. dkmortensen

    Joined:
    Jun 29, 2010
    Messages:
    10
    Likes Received:
    0
    I am using 2.6.18-164.el5

    That is the version I got by doing a 'yum update kernel' last night.

    More details, FYI:

    [root@voipserv1 ~]# cat /proc/version

    Linux version 2.6.18-164.el5 (mockbuild@builder16.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Thu Sep 3 03:33:56 EDT 2009


    [root@voipserv1 ~]# rpm -qi kernel

    Name : kernel Relocations: (not relocatable)
    Version : 2.6.18 Vendor: CentOS
    Release : 92.1.22.el5 Build Date: Tue 16 Dec 2008 12:23:38 PM MST
    Install Date: Thu 13 Aug 2009 12:13:47 AM MDT Build Host: builder16.centos.org
    Group : System Environment/Kernel Source RPM: kernel-2.6.18-92.1.22.el5.src.rpm
    Size : 39058276 License: GPLv2
    Signature : DSA/SHA1, Tue 16 Dec 2008 03:57:01 PM MST, Key ID a8a447dce8562897
    URL : http://www.kernel.org/
    Summary : The Linux kernel (the core of the Linux operating system)
    Description :
    The kernel package contains the Linux kernel (vmlinuz), the core of any
    Linux operating system. The kernel handles the basic functions
    of the operating system: memory allocation, process allocation, device
    input and output, etc.

    Name : kernel Relocations: (not relocatable)
    Version : 2.6.18 Vendor: CentOS
    Release : 164.el5 Build Date: Thu 03 Sep 2009 04:08:43 AM MDT
    Install Date: Tue 29 Jun 2010 10:54:14 PM MDT Build Host: builder16.centos.org
    Group : System Environment/Kernel Source RPM: kernel-2.6.18-164.el5.src.rpm
    Size : 43435228 License: GPLv2
    Signature : DSA/SHA1, Mon 28 Sep 2009 11:18:17 AM MDT, Key ID 4bfe99f4d05c057c
    URL : http://www.kernel.org/
    Summary : The Linux kernel (the core of the Linux operating system)
    Description :
    The kernel package contains the Linux kernel (vmlinuz), the core of any
    Linux operating system. The kernel handles the basic functions
    of the operating system: memory allocation, process allocation, device
    input and output, etc.



    Just for clarification, the last command's output here shows both the RPM for the compiled kernel, as well as the source rpm for it. That's why it is returning two responses for that RPM (confused me at first :).

    -
    Doug
     
  15. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    Doug:
    All the same.
    In my opinion the problem is now located in winpipe package - the updated version has been build from wanpipe 3.5.11.6, but sangoma reports, that they have fixed dahdi 2.3 support from 3.5.12 version.
    I have asked at bugtracker to build an beta rmp from winpipe 3.5.12 or 3.5.14 (current wanpipe driver)

    Outdated Wanpipe module, as I remember, has always been a problem in Elastix. ;-)
     
  16. dkmortensen

    Joined:
    Jun 29, 2010
    Messages:
    10
    Likes Received:
    0
    So are you guys still down? Very sorry to hear. I could hardly tolerate being down for 3 hours on Monday.

    Best wishes

    -
    Doug
     
  17. witekprytek

    Joined:
    Dec 19, 2007
    Messages:
    145
    Likes Received:
    0
    Now my systems is up and running :)
    I have removed everything regarding dahdi and wanpipe from the system. I have remove all card config files and modules, and after reboot made fresh install from the latest packages.

    Card now working as should work, but dahdi_tools seems to be broken.
     
  18. ricsne2010

    Joined:
    Oct 17, 2011
    Messages:
    4
    Likes Received:
    0
    Good evening all

    I spent about a week attempting to determine why my Elastix box's DAHDI channel driver no longer loads. It looks like the CHAN_DAHDI driver fails to locate the actual drivers for the card you have installed. It had another box that I installed with the current "stable" load from Elastix's website (64bit), and re-installed the software. The DAHDI driver loads with no issue. Upon running the command "YUM UPDATE" and allowing the DAHDI driver to upgrade along with all the other services, the DAHDI driver installs, but again does not show any signs of compile failure.

    If you need to stay at the latest version of Elastix, along with keeping the Kernal and PHP up to date, but don't want to deal with DAHDI (until resolved in Bugs) - you have a few options

    1) Perform yum --exclude=dahdi* update

    2) you can load a yum version that allows you to downgrade to the previous version of DAHDI (I was not as successful in this....)

    If you upgrade, be forewarned.... the YUM servers show the previous versions of DAHDI available, but you cannot download it.

    Either way, I hope this is fixed soon.... as of right now, I have performed a clean install from ISO, and performed the upgrade using option 1 above.

    Cheers.
     

Share This Page