asterisk users - Jan 2005 - Wildcard x100p and Redhat 9.0: Unable to get parameters

Hi folks

Seems really simple but run out of ideas:

1. Used Redhat 9 Packages for Asterisk

2. Zaptel one didn't work so recompiled zaptel from cvs against my kernel
2.4.20-8

3. Compile is fine no depmod problems/ugly message etc.

4. lsmod:
wcusb                  20064   0  (unused)
wcfxo                   9376   0
zaptel                179168   0  [wcusb wcfxo]

5. start up messages on boot all [OK]

6. But when I define channel 1 as follows:

   signalling=fxs_ks
   language=en
   context=incoming
   channel => 1

7. I get:

Jan  8 10:58:13 WARNING[1076232832]: Unable to open /dev/dsp: No such device
Jan  8 10:58:13 ERROR[1076232832]: Unable to get parameters
Jan  8 10:58:13 ERROR[1076232832]: Unable to register channel '1'
Jan  8 10:58:13 WARNING[1076232832]: chan_zap.so: load_module failed,
returning -1
Jan  8 10:58:13 WARNING[1076232832]: Loading module chan_zap.so failed!
Jan  8 10:58:35 WARNING[1076232832]: Unable to open /dev/dsp: No such device
Jan  8 10:58:35 ERROR[1076232832]: Unable to get parameters
Jan  8 10:58:35 ERROR[1076232832]: Unable to register channel '1'
Jan  8 10:58:35 WARNING[1076232832]: chan_zap.so: load_module failed,
returning -1
Jan  8 10:58:35 WARNING[1076232832]: Loading module chan_zap.so failed!
Jan  8 10:59:02 WARNING[1076232832]: Unable to open /dev/dsp: No such device

8. Haven't got a sound card in the system, this is perhaps causing the dsp
message? Otherwise very
grateful for any ideas!

Best regards Hugh

http://hughbarnard.org

I'm running RH9 on an old HP Vectra, was stuck with:

Jan  8 10:58:35 ERROR[1076232832]: Unable to get parameters
Jan  8 10:58:35 ERROR[1076232832]: Unable to register channel '1'
Jan  8 10:58:35 WARNING[1076232832]: chan_zap.so: load_module failed,
returning -1
Jan  8 10:58:35 WARNING[1076232832]: Loading module chan_zap.so failed!

for about two days after installing RH9 Asterisk packages + a re-compile of
zaptel.

I checked -everything- out of the Asterisk CVS this morning, recompiled it
all
against 2-4.20-8 and it runs (could be detail problems but these are
probably smaller) OK. Hope this is helpful for others because the reporting
on it looks like a file parameter error.

Best regards Hugh Barnard

http://hughbarnard.org

http://hughbarnard.org