[asterisk-users] 10.0.0-rc1: dahdi doesn't see card

[sean darcy]

On 11/11/2011 07:38 PM, Eric Wieling wrote:
> Show us /etc/asterisk/chan_dahdi.conf (and any #include'd files)
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of sean darcy
> Sent: Friday, November 11, 2011 5:51 PM
> To: asterisk-users at lists.digium.com
> Subject: [asterisk-users] 10.0.0-rc1: dahdi doesn't see card
>
>   From asterisk -cvvvvv
>
>     == Parsing '/etc/asterisk/chan_dahdi.conf':   == Found
>     == Parsing '/etc/asterisk/users.conf':   == Found
>       -- Automatically generated pseudo channel
> [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:
> Ignoring any changes to 'userbase' (on reload) at line 23.
> [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:
> Ignoring any changes to 'vmsecret' (on reload) at line 31.
> [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:
> Ignoring any changes to 'hassip' (on reload) at line 35.
> [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:
> Ignoring any changes to 'hasiax' (on reload) at line 39.
> [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:
> Ignoring any changes to 'hasmanager' (on reload) at line 47.
>     == Registered channel type 'DAHDI' (DAHDI Telephony Driver)
>     == Manager registered action DAHDITransfer
>     == Manager registered action DAHDIHangup
>     == Manager registered action DAHDIDialOffhook
>     == Manager registered action DAHDIDNDon
>     == Manager registered action DAHDIDNDoff
>     == Manager registered action DAHDIShowChannels
>     == Manager registered action DAHDIRestart
>    chan_dahdi.so =>  (DAHDI Telephony Driver)
> ......
>
> But, no dahdi.
>
> dahdi show channels shows nothing:
>
>      Chan Extension  Context         Language   MOH Interpret
> Blocked    State      Description
>    pseudo            default                    default
>          In Service
>
>
> dahdi_cfg -vvv
> DAHDI Tools Version - 2.4.1
>
> DAHDI Version: 2.5.0.1
> Echo Canceller(s): HWEC, OSLEC
> Configuration
> ======================
>
>
> Channel map:
>
> Channel 01: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 01)
> Channel 02: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 02)
> Channel 04: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 04)
>
> 3 channels to configure.
>
> Setting echocan for channel 1 to oslec
> Setting echocan for channel 2 to oslec
> Setting echocan for channel 4 to oslec
>
>   From dmesg:
> dahdi: Telephony Interface Registered on major 196
> [    9.849036] dahdi: Version: 2.5.0.1
> [    9.899531] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19
> [    9.899919] wctdm 0000:01:0a.0: PCI INT A ->  Link[LNKC] ->  GSI 19
> (level, low) ->  IRQ 19
> [    9.901845] Freshmaker version: 73
> [    9.902565] Freshmaker passed register test
> [   11.287170] Module 0: Installed -- AUTO FXS/DPO
> [   12.172362] Module 1: Installed -- AUTO FXS/DPO
> [   12.172795] Module 2: Not installed
> [   12.373273] Module 3: Installed -- AUTO FXO (FCC mode)
> [   12.374071] Found a Wildcard TDM: Wildcard TDM400P REV I (3 modules)
>
> Any help appreciated.
>
> sean
>
>
>

Thanks. That was it. The new install of 10.0.0 had overwritten 
chan_dahdi.conf with the sample. Reloading the old chan_dahdi.conf got 
it all to work.

What's puzzling is how dahdi_config knew how to configure the card 
without chan_dahdi.conf. I'd just assumed it had read chan_dahdi.conf. 
Live and learn.

sean