asterisk users - May 2004 - TDM11B - 2nd channel is not detected

Hello all,

This is my first post to this mailing list.  I've been following the
development (not as a developer, but as an interested user) of Asterisk
for over a year now.  It's only in the last month that we've decided to
give it a try (hey, might as well...everything else we use is open
source).

We ordered a TDM11B (1 FXS, and 1 FXO).  The card and Asterisk install
was uneventful.  I've been able to load the modules, and the lights on
the jacks (on the card) are green.  I've run ztcfg, and it's reporting
that 1 FXO channel and 1 FXS channel have been configured.

I've set up in my zapata.conf file two channels: one for the analog
phone (fxo_ks), and one for the POTS line (fxs_ks) that is coming into
the office.

The problem is when I test my setup with "asterisk -vvvgc", asterisk
pukes and reports the following:

[chan_zap.so] => (Zapata Telephony)
  == Parsing '/etc/asterisk/zapata.conf': Found
May 13 17:19:49 DEBUG[-1220444032]: chan_zap.c:1077 update_conf: Updated
conferencing on 1, with 0 conference users
    -- Registered channel 1, FXO Kewlstart signalling
May 13 17:19:49 WARNING[-1220444032]: chan_zap.c:665 zt_open: Unable to
specify channel 2: No such device
May 13 17:19:49 ERROR[-1220444032]: chan_zap.c:5326 mkintf: Unable to
open channel 2: No such device
here = 0, tmp->channel = 2, channel = 2
May 13 17:19:49 ERROR[-1220444032]: chan_zap.c:7362 setup_zap: Unable to
register channel '2'
May 13 17:19:49 WARNING[-1220444032]: loader.c:313 ast_load_resource:
chan_zap.so: load_module failed, returning -1
  == Unregistered channel type 'Tor'
  == Unregistered channel type 'Zap'
Segmentation fault (core dumped)

If I comment out the lines for the second channel (which is the POTS
line), Asterisk starts without error, but of course I then cannot make
any calls on the POTS line.

Any ideas?  I've searched up and down Google, but no luck so far. I can
post the relevant sections of my config files here if needed.

Thanks in advance,

Kanwar
Systems Aligned Inc.
www.systemsaligned.com

Hi everyone,

On Thu, 2004-05-13 at 18:36, M3 Freak wrote:
> The problem is when I test my setup with "asterisk -vvvgc",
asterisk
> pukes and reports the following:
> 
> [chan_zap.so] => (Zapata Telephony)
>   == Parsing '/etc/asterisk/zapata.conf': Found
> May 13 17:19:49 DEBUG[-1220444032]: chan_zap.c:1077 update_conf: Updated
> conferencing on 1, with 0 conference users
>     -- Registered channel 1, FXO Kewlstart signalling
> May 13 17:19:49 WARNING[-1220444032]: chan_zap.c:665 zt_open: Unable to
> specify channel 2: No such device
> May 13 17:19:49 ERROR[-1220444032]: chan_zap.c:5326 mkintf: Unable to
> open channel 2: No such device
> here = 0, tmp->channel = 2, channel = 2
> May 13 17:19:49 ERROR[-1220444032]: chan_zap.c:7362 setup_zap: Unable to
> register channel '2'
> May 13 17:19:49 WARNING[-1220444032]: loader.c:313 ast_load_resource:
> chan_zap.so: load_module failed, returning -1
>   == Unregistered channel type 'Tor'
>   == Unregistered channel type 'Zap'
> Segmentation fault (core dumped)
[snip]

I figured out what was causing Asterisk to break.  I'd like to post what
I did, so here's my off-list message to a reply I received earlier:

Hi Mitchell,

On Thu, 2004-05-13 at 19:05, Mitchell S. Sharp wrote:
> [off-list]
> 
> Hello,
> 
> >From the error, it doesn't look like your specifying your signaling
> right in zapata.conf.  You specify fxo_ks for the first one,
> (Registered channel 1, FXO Kewlstart signalling) but it doesn't say
> anything about the signaling on the second channel.
What you said just made me confirm that I must have made a mistake in
the way the channels were configured.  I've been at this the whole day,
but your email finally turned the bulb on in my head.

In my /etc/zaptel.conf file, I had this:

fxoks = 1               ; use FXO signalling for FXS devices
fxsks = 2               ; use FXS signalling for FXO devices

I just realized that the FXO module is plugged into the PCI card on
port 4, and the FXS module is connected at port 1.  

That being the case, it's fairly obvious why Asterisk wouldn't work on
the POTS line.  And, to make things worse, I continued this error into
the zapata.conf file as well.  This is why Asterisk wasn't finding a
DEVICE at channel 2 - there isn't one there!  Man, do I feel dumb.

So, I made the following change in zaptel.conf:

fxoks = 1               ; use FXO signalling for FXS devices
fxsks = 4               ; use FXS signalling for FXO devices

And, I made sure I used the same channel config in zapata.conf.

Now Asterisk starts without the error.  Ya!  On to getting the rest of
the system working.

HTH someone in the future.  It's a pretty obvious mistake on my part,
now that I've solved it.

Thanks,

Kanwar
Systems Aligned Inc.
www.systemsaligned.com