[Asterisk-Users] no longer loading all config files?!?!?!?!?!!!!!!...

[Francesco Peeters]

On Thu, November 17, 2005 23:39, Francesco Peeters said:
> I have been testing with the issue I have when using 2 ISDN HFC-BRI cards
> with ZapHFC / BRIstuff. (Which *seems* to be working, but cannot test
> because of this new problem!)
>
> Everything was working fine until earlier this evening...
>
> Now it doesn't seem to execute anything beyond chan_skinny (the next one
> normally being pbx_config.so, which loads the dial-plan), which means it
> is about as useful for telephony as the paperweight on my desk!  :-(
>
> Reload info:
> [root at asterisk1 root]# asterisk -rx reload
> Verbosity is at least 28
>   == RTP Allocating from port range 10000 -> 20000
>     -- Reloading module 'res_adsi.so' (ADSI Resource)
>     -- Reloading module 'res_crypto.so' (Cryptographic Digital Signatures)
>     -- Reloading module 'res_indications.so' (Indications Configuration)
>     -- Unregistered indication country 'us'
>     -- Unregistered indication country 'au'
>     -- Unregistered indication country 'fr'
>     -- Unregistered indication country 'de'
>     -- Unregistered indication country 'nl'
>     -- Unregistered indication country 'uk'
>     -- Unregistered indication country 'fi'
>     -- Unregistered indication country 'no'
>     -- Unregistered indication country 'br'
>     -- Unregistered indication country 'za'
>     -- Unregistered indication country 'it'
>     -- Registered indication country 'us'
>     -- Registered indication country 'au'
>     -- Registered indication country 'fr'
>     -- Registered indication country 'de'
>     -- Registered indication country 'nl'
>     -- Registered indication country 'uk'
>     -- Registered indication country 'fi'
>     -- Registered indication country 'no'
>     -- Registered indication country 'br'
>     -- Registered indication country 'za'
>     -- Registered indication country 'it'
>     -- Setting default indication country to 'us'
>     -- Reloading module 'chan_sip.so' (Session Initiation Protocol (SIP))
>     -- Reloading module 'chan_agent.so' (Agent Proxy Channel)
>     -- Reloading module 'chan_mgcp.so' (Media Gateway Control Protocol
> (MGCP))
>     -- Reloading module 'chan_iax2.so' (Inter Asterisk eXchange (Ver 2))
>  Reloading SIP
>  Reloading MGCP
>   == Loaded firmware 'iaxy.bin'
>     -- Loaded provisioning template 'default'
>     -- Reloading module 'chan_local.so' (Local Proxy Channel)
>     -- Reloading module 'chan_skinny.so' (Skinny Client Control Protocol
> (Skinny))
>
>
> Any ideas/suggestions, apart from starting from scratch? (Which I will do
> if necessary, but I *am* trying to prevent rebuilding from scratch for the
> 4th time in 2 weeks!) :-(
>

UPDATE: It *still* has to do with the friggin' ZAPHFC BRIstuff drivers!!!

If I have bri_net_ptmp enabled for channels 4-5, it doesn't execute the
remainder of the system config, if I have it disabled (and thus revert to
bri_cpe_ptmp) for channels 4-5, then all works fine, except that it
wouldn't be running NT mode on the second card. (thus defeating the
purpose of the second card!)

lspci shows:
00:09.0 Network controller: Cologne Chip Designs GmbH ISDN network
controller [HFC-PCI] (rev 02)
        Subsystem: Advanced Integrations Research: Unknown device c101
        Flags: bus master, medium devsel, latency 16, IRQ 11
        I/O ports at c400 [disabled] [size=8]
        Memory at e3001000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1
00:11.0 Network controller: Cologne Chip Designs GmbH ISDN network
controller [HFC-PCI] (rev 02)
        Subsystem: Advanced Integrations Research: Unknown device c101
        Flags: bus master, medium devsel, latency 16, IRQ 11
        I/O ports at cc00 [disabled] [size=8]
        Memory at e3002000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1

Help please?...

-- 
Francesco Peeters
----
GPG Key = AA69 E7C6 1D8A F148 160C  D5C4 9943 6E38 D5E3 7704
If your program doesn't recognize my signature, please visit
http://www.CAcert.org/index.php?id=3 to retrieve the Root CA certificate.