problem dahdi

Discussion in 'General' started by dontpntpool, Apr 24, 2009.

  1. dontpntpool

    Joined:
    Apr 24, 2009
    Messages:
    3
    Likes Received:
    0
    can't get fxo to answer or dialout I think there is a problem connecting the fxo to the pots

    dmg
    Code:
    dahdi: Telephony Interface Registered on major 196
    dahdi: Version: 2.1.0.4
    ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 193
    Found a Wildcard FXO: Generic Clone
    dahdi_echocan_oslec: Registered echo canceler 'OSLEC'
    dahdi: Registered tone zone 0 (United States / North America)
    lspci
    Code:
    02:09.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
            Subsystem: Intel Corporation Digium X100P/X101P analogue PSTN FXO interface
            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
            Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
            Latency: 64 (250ns min, 32000ns max)
            Interrupt: pin A routed to IRQ 193
            Region 0: I/O ports at e800 [size=256]
            Region 1: Memory at fdefe000 (32-bit, non-prefetchable) [size=4K]
            Capabilities: [40] Power Management version 2
                    Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
                    Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    cat /proc/interrupts
    Code:
    193:    1624185   IO-APIC-level  eth0, wcfxo
    dahdi_test
    Code:
    Opened pseudo dahdi interface, measuring accuracy...
    99.994% 99.987% 99.992% 99.992% 99.992% 99.992% 99.992% 99.992%
    99.991% 99.992% 99.989% 99.992% 99.992% 99.992% 99.992% 99.993%
    99.992% 99.991% 99.991% 99.992% 99.992% 99.992% 99.991% 99.991%
    99.991% 99.991% 99.992% 99.992% 99.991% 99.992% 99.992% 99.992%
    99.992% 99.992% 99.991% 99.992% 99.991% 99.992% 99.992% 99.991%
    --- Results after 40 passes ---
    Best: 99.994 -- Worst: 99.987 -- Average: 99.991500, Difference: 99.991500
    /etc/dahdi/system.conf
    Code:
    # Autogenerated by /usr/sbin/dahdi_genconf on Fri Apr 24 13:55:39 2009 -- do not hand edit
    # Dahdi Configuration File
    #
    # This file is parsed by the Dahdi Configurator, dahdi_cfg
    #
    # Span 1: WCFXO/0 "Generic Clone Board 1" (MASTER) RED
    fxsks=1
    echocanceller=oslec,1
    
    # Global data
    
    loadzone        = us
    defaultzone     = us
    /etc/asterisk/dahdi-channels.conf
    Code:
    ; Autogenerated by /usr/sbin/dahdi_genconf on Fri Apr 24 13:55:39 2009 -- do not hand edit
    ; Dahdi Channels Configurations (chan_dahdi.conf)
    ;
    ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
    ; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
    ;
    
    ; Span 1: WCFXO/0 "Generic Clone Board 1" (MASTER) RED
    ;;; line="1 WCFXO/0/0"
    signalling=fxs_ks
    callerid=asreceived
    group=0
    context=from-pstn
    channel => 1
    callerid=
    group=
    context=default
    dahdi_monitor
    Code:
    [root@elastix ~]Visual Audio Levels.
    --------------------
     Use chan_dahdi.conf file to adjust the gains if needed.
    
    ( # = Audio Level  * = Max Audio Hit )
    <----------------(RX <----------------(TX
     ###########################        *                                          Rx:  5182 (10661) Tx:     0 (    0)
    dahdi_hardware
    Code:
    pci:0000:02:09.0     wcfxo+       e159:0001 Wildcard X101P clone
    dahdi_scan
    Code:
    [1]
    active=yes
    alarms=RED
    description=Generic Clone Board 1
    name=WCFXO/0
    manufacturer=Digium
    devicetype=Generic Clone
    location=PCI Bus 02 Slot 10
    basechan=1
    totchans=1
    irq=193
    type=analog
    port=1,FXO
     
  2. dontpntpool

    Joined:
    Apr 24, 2009
    Messages:
    3
    Likes Received:
    0
    after reading a LOT of posts I think there may be a problem with the configuration.


    I am still very new to this so please help me get this right.

    This is what I have done like 20 times now:
    -------------------------------------------
    1. have 1 dahdi/zaptel generic clone x101p card in the linux box with only outside telephone line connected to line
    2. install os
    3. setup extension 201
    4. check my trunks and see trunk 1 in dahdi compatibility mode using identifier g0
    5. change trunk identifier to 1
    6. check my outbound routs and see 0 9_outside and its set to 0 ZAP/1
    7. add dial pattern 9|. to the outbound route 9_outside
    8. check inbound routes but it is empty
    9. add inboud route called "everything" and set it to ring extension 201
    10. install x-lite on other computer
    11. configure x-lite to connect to elastix box and make sure working to pbx
    12. dial 9 and then number on xlite but get response all circuits are busy
    13. dial my phone number to the pbx box from my cell phone and just get ring ring ring
    14. ...cry...
    15. try another distribution...go thru the process again...same result
    Am I forgetting a step?
    I think that maybe that there needs to be something done with the ZAP channel DIDs
    but none of the documentation I read has said anything about it

    I think from reading other posts that maybe the config files do not get configured right

    /etc/asterisk dahdi_channels.conf

    and I read a post it should be

    I don't have a "chan_dahdi.conf" file at all.


    But I am not sure what I am doing here
     
  3. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    In your dahdi_scan output you can see:

    alarms=RED

    This means the cable is not connected. Maybe you have a problem with the cable or the connector.
    Check it out.
     
  4. dontpntpool

    Joined:
    Apr 24, 2009
    Messages:
    3
    Likes Received:
    0
    thank you for your reply please read that I edited my 2nd post to contain more helpful information.

    Yes I can get the adapter to go from red to no alarm by plugging the cable in and out

    I would give you more info but it seems my elastix is now broke since I did "yum update" I get lots of errors with dahdi commands and the conf files seem to be set back to defaults.

    Code:
    [root@elastix ~]# dahdi_hardware
    Argument "dynamic-ethmf" isn't numeric in array element at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Span.pm line 180.
    Use of uninitialized value in pattern match (m//) at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Span.pm line 223, <F> line 1.
    Argument "dynamic-ethmf" isn't numeric in numeric comparison (<=>) at /usr/lib/perl5/site_perl/5.8.8/Dahdi.pm line 52.
    pci:0000:02:09.0     wcfxo+       e159:0001 Wildcard X101P clone
    
    Code:
    [root@elastix ~]# dahdi_genconf
    Argument "dynamic-ethmf" isn't numeric in array element at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Span.pm line 180.
    Use of uninitialized value in pattern match (m//) at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Span.pm line 223, <F> line 1.
    Argument "dynamic-ethmf" isn't numeric in numeric comparison (<=>) at /usr/lib/perl5/site_perl/5.8.8/Dahdi.pm line 52.
    Argument "dynamic-ethmf" isn't numeric in printf at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Config/Gen/System.pm line 122.
    Use of uninitialized value in printf at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Config/Gen/System.pm line 122.
    Use of uninitialized value in printf at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Config/Gen/System.pm line 122.
    Argument "dynamic-ethmf" isn't numeric in printf at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Config/Gen/Chandahdi.pm line 153.
    Use of uninitialized value in printf at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Config/Gen/Chandahdi.pm line 153.
    Use of uninitialized value in printf at /usr/lib/perl5/site_perl/5.8.8/Dahdi/Config/Gen/Chandahdi.pm line 153.
    
     
  5. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    I also get these perl errors after the last yum update, I still don't know why.

    Try to detect hardware in the Elastix interface. This should configure automatically the card. Or try with dahdi_cfg -vv
     
  6. luetzz

    Joined:
    Mar 1, 2008
    Messages:
    21
    Likes Received:
    0
    Hi

    I´m also getting this perl error with dahdi_genconf, after a today yum update.
    The Elastix (production) machine has 2 A104 Sangoma cards.

    1) FreePBX doesn´t detect the hardware, it was all ok before update.
    In other situations sometimes I have had problems with perl and don´t known how to solve.

    2) dhadi_cfg -vv returns nothing.

    Is there anything new about this problem?
     
  7. rafael

    Joined:
    May 14, 2007
    Messages:
    1,454
    Likes Received:
    1
    can you please report this at:http://bugs.elastix.org

    Regards,

    Rafael
     

Share This Page