[Asterisk-Users] module load order for Junghanns qozap and TDMcard
Olivier Krief
olivier.krief at gmail.com
Fri Mar 17 01:54:28 MST 2006
Hello,
I would be delighted to know if you successfully bridged fax calls between
both cards, as I suppose :
- the Junghanns QuadBRI is connected to PSTN,
- at least, one analog fax is connected to the Digium TDM card.
Personnally, I had ongoing problems with fax calls crossing Junghanns BRI
card (from one port to another) :
5 to 15% of fax (incoming or outgoing) are interrupted.
I don't know if that comes from excessive server load or any missing
ressource (PCI bus, ...).
I was thinking about :
- directly connecting faxes on Digium TDM card instead,
- use Junghanns BRI card as a pure access system,
- and bet that voice and fax calls safely use PCI bus.
I couldn't get any clue (nor reply) from Junghanns stating that this card
correctly "switches" ISDN calls.
Learning from your experience would be great for me.
Regards
----- Original Message -----
From: "Chris Earle (CBL)" <cearle at cbltech.ca>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
<asterisk-users at lists.digium.com>
Sent: Thursday, March 16, 2006 6:40 PM
Subject: Re: [Asterisk-Users] module load order for Junghanns qozap and
TDMcard
> Okay
>
> think I finally figured this out
>
> it's the modules.conf post-install lines that run ztcfg
>
> You're not supposed to run ztcfg more than once with the multiple zaptel
> cards in there .... I kept running it manually (ztcfg -vvvv) not realizing
> that after modprobe wcfxs the ztcfg was being run.
>
> So the order that works is
>
> zaptel
> qozap
> wcfxs (which runs ztcfg, and readies asterisk to run)
>
>
> If anyone has any comments about this, please post
>
>
> --
> Chris
>
>
> ----- Original Message -----
> From: "Chris Earle (CBL)" <cearle at cbltech.ca>
> To: "'Asterisk Users Mailing List - Non-Commercial Discussion'"
> <asterisk-users at lists.digium.com>
> Sent: Thursday, March 16, 2006 11:30 AM
> Subject: Re: [Asterisk-Users] module load order for Junghanns qozap and
> TDMcard
>
>
>> Maybe this will shed some light about what I'm trying to do:
>>
>> This is some output from dmesg after this load order:
>>
>> modprobe zaptel
>> insmod wcfxs
>> insmod qozap
>> ----
>> Zapata Telephony Interface Registered on major 196
>> Freshmaker version: 73
>> Freshmaker passed register test
>> Module 0: Installed -- AUTO FXS/DPO
>> Module 1: Installed -- AUTO FXS/DPO
>> Module 2: Installed -- AUTO FXS/DPO
>> Module 3: Installed -- AUTO FXS/DPO
>> Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)
>> PCI: Enabling device 02:01.0 (0000 -> 0003)
>> qozap: Junghanns.NET quadBRI card configured at mem 0xf889b000 IRQ 17 HZ
> 100
>> CardID 0
>> qozap: S/T ports: 4 [ TE TE TE TE ]
>> qozap: 1 multiBRI card(s) in this box, 4 BRI ports total.
>>
>>
>> Zaptel Configuration
>> ======================
>>
>> SPAN 1: CCS/ AMI Build-out: 399-533 feet (DSX-1)
>> SPAN 2: CCS/ AMI Build-out: 399-533 feet (DSX-1)
>> SPAN 3: CCS/ AMI Build-out: 399-533 feet (DSX-1)
>> SPAN 4: CCS/ AMI Build-out: 399-533 feet (DSX-1)
>>
>> Channel map:
>>
>> Channel 01: Individual Clear channel (Default) (Slaves: 01)
>> Channel 02: Individual Clear channel (Default) (Slaves: 02)
>> Channel 03: D-channel (Default) (Slaves: 03)
>> Channel 04: Individual Clear channel (Default) (Slaves: 04)
>> Channel 05: Individual Clear channel (Default) (Slaves: 05)
>> Channel 06: D-channel (Default) (Slaves: 06)
>> Channel 07: Individual Clear channel (Default) (Slaves: 07)
>> Channel 08: Individual Clear channel (Default) (Slaves: 08)
>> Channel 09: D-channel (Default) (Slaves: 09)
>> Channel 10: Individual Clear channel (Default) (Slaves: 10)
>> Channel 11: Individual Clear channel (Default) (Slaves: 11)
>> Channel 12: D-channel (Default) (Slaves: 12)
>> Channel 13: FXO Kewlstart (Default) (Slaves: 13)
>> Channel 14: FXO Kewlstart (Default) (Slaves: 14)
>> Channel 15: FXO Kewlstart (Default) (Slaves: 15)
>> Channel 16: FXO Kewlstart (Default) (Slaves: 16)
>>
>> 16 channels configured.
>>
>> ZT_SPANCONFIG failed on span 1: Invalid argument (22)
>>
>>
>>
>>
>> any thoughts?
>>
>>
>>
>>
>> Chris
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Chris Earle (CBL)" <cearle at cbltech.ca>
>> To: "'Asterisk Users Mailing List - Non-Commercial Discussion'"
>> <asterisk-users at lists.digium.com>
>> Sent: Thursday, March 16, 2006 10:09 AM
>> Subject: [Asterisk-Users] module load order for Junghanns qozap and TDM
> card
>>
>>
>> > Hi all,
>> >
>> > I'm trying to get a junghanns QuadBRI to coexist in the same machine as
> a
>> > Digium TDM400P card (so I can run the ISDN lines in and bridge with
>> analog
>> > phones plugged into the TDM).
>> >
>> > I'm having a problem loading the modules. If I follow the BRIstuff
>> > (0.3.0-pre-1l) install method.... it's to modprobe zaptel, then insmod
>> > qozap.o
>> > I'm on Debian 2.4.31.
>> > That works.
>> > But then I still need the Digium module. (modprobe wctdm)
>> > I've tried a few different orders. Sometimes I can get the digium to
>> load,
>> > and the qozap.
>> > but then I get an error on the ztcfg about Span invalid argument
>> > (could
>> be
>> > my zaptel.conf I realize...)
>> >
>> > *If* I try loading the wctdm after the zaptel and qozap, the server
>> freezes!
>> > Some loop about qozap - dropped audio card....
>> >
>> > I don't know if the quadBRI and the TDM are conflicting/sharing the
> zaptel
>> > module, or if I need to modprobe zaptel before each of them? and in
>> > what
>> > order?
>> >
>> > Any suggestions appreciated... I haven't even got to figuring out what
>> > I
>> can
>> > do with chan_capi, just want to get the BRI card on and stuff.
>> >
>> > Thanks for any ideas!
>> >
>> >
>> > --
>> > Chris Earle
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
More information about the asterisk-users
mailing list