asterisk users - Apr 2004 - TDM400P Issues

Hi,

I just got my TDM400P card (2 modules) and i installed it no probs. The 
card is detected fine, but for some reason when I add the card to 
zaptel.conf i get the following error:

--snip--
ZT_CHANCONFIG failed on channel 2: Invalid argument (22)
Did you forget that FXS interfaces are configured with FXO signalling
and that FXO interfaces use FXS signalling?
--snip--

My /etc/zaptel.conf looks like:

--snip--
fxsks=1-2
fxoks=3-4
loadzone=au
defaultzone=au
--snip--

I currently have 2 x X100P cards that work no problem.

Running a ztcfg -vvvv I get:

Zaptel Configuration
=====================

Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)
Channel 03: FXO Kewlstart (Default) (Slaves: 03)
Channel 04: FXO Kewlstart (Default) (Slaves: 04)

4 channels configured.

ZT_CHANCONFIG failed on channel 2: Invalid argument (22)
Did you forget that FXS interfaces are configured with FXO signalling
and that FXO interfaces use FXS signalling?


Anyone have any ideas? I tried doing a search but couldn't really find 
anything.

Thanks!

-- 
jeremy bogan    [ jeremy@segpub.com.au ]
segment publishing - design.develop.host

G'day Jeremy,

On Tue, 13 Apr 2004, Jeremy Bogan wrote:
> --snip--
> ZT_CHANCONFIG failed on channel 2: Invalid argument (22)
> Did you forget that FXS interfaces are configured with FXO signalling
> and that FXO interfaces use FXS signalling?
> --snip--
> 
> My /etc/zaptel.conf looks like:
> 
> --snip--
> fxsks=1-2
> fxoks=3-4
> loadzone=au
> defaultzone=au
> --snip--
> 
> I currently have 2 x X100P cards that work no problem.
> 
> Running a ztcfg -vvvv I get:
> 
> Zaptel Configuration
> =====================> 
> 
> Channel map:
> 
> Channel 01: FXS Kewlstart (Default) (Slaves: 01)
> Channel 02: FXS Kewlstart (Default) (Slaves: 02)
> Channel 03: FXO Kewlstart (Default) (Slaves: 03)
> Channel 04: FXO Kewlstart (Default) (Slaves: 04)
> 
> 4 channels configured.
> 
> ZT_CHANCONFIG failed on channel 2: Invalid argument (22)
> Did you forget that FXS interfaces are configured with FXO signalling
> and that FXO interfaces use FXS signalling?
This is your clue...  Do exactly what it says...

At a guess, I'd say you've loaded the wcfxs module before wcfxo.  This 
will push your existing X100P interfaces out to channels 3 and 4.  Either 
change your zaptel.conf to suit, or load wcfxo prior to wcfxs to have your 
FXO cards appear where they used to.

Cheers,
Vic Cross

Fixed it, had to modify my config, it now reads:

fxsks=1
fxoks=2-3
fxsks=4
loadzone=au
defaultzone=au

-- 
jeremy bogan    [ jeremy@segpub.com.au ]
segment publishing - design.develop.host