thr3ads.net - asterisk users - [asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard [Sep 2006]

If this information is useful, please help other people find it:
Share via:

Morten Isaksen

2006-Sep-23 12:23 UTC

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

Hi!

I was trying to upgrade my Asterisk 1.2.1 at home (not the Asterisk@homte dist)
to 1.4b2 but ran into problems with zaptel. The OS is Fedora Core 3.

When I start zaptel it fails with this error:


[root@mythtv zaptel-1.4.0-beta1]# service zaptel start
Loading zaptel framework:                                  [  OK  ]
Waiting for zap to come online...OK
Loading zaptel hardware modules: tor2 wct4xxp wct1xxp wcfxo wctdmRunning
ztcfg:  ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device
(25)
                                                           [FAILED]
[root@mythtv zaptel-1.4.0-beta1]# ztcfg -vvv
Notice: Configuration file is /etc/zaptel.conf
line 235: Unable to read Zaptel version information.

Zaptel Version: $??P?0
Echo Canceller:
Configuration
=====================

Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)

1 channels configured.

ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device (25)


Zaptel version 1.2.1 worked fine on this computer and I have not changed the
zaptel.conf.






-- 
Morten Isaksen
http://www.misak.dk/blog/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060923/a019ffb7/attachment.htm

Tzafrir Cohen

2006-Sep-25 00:42 UTC

head link

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

On Sat, Sep 23, 2006 at 09:22:50PM +0200, Morten Isaksen
wrote:> Hi!
> 
> I was trying to upgrade my Asterisk 1.2.1 at home (not the Asterisk@homte 
> dist)
> to 1.4b2 but ran into problems with zaptel. The OS is Fedora Core 3.
> 
> When I start zaptel it fails with this error:
> 
> 
> [root@mythtv zaptel-1.4.0-beta1]# service zaptel start
> Loading zaptel framework:                                  [  OK  ]
> Waiting for zap to come online...OK
> Loading zaptel hardware modules: tor2 wct4xxp wct1xxp wcfxo wctdmRunning
> ztcfg:  ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device
> (25)
>                                                           [FAILED]
> [root@mythtv zaptel-1.4.0-beta1]# ztcfg -vvv
> Notice: Configuration file is /etc/zaptel.conf
> line 235: Unable to read Zaptel version information.
> 
> Zaptel Version: $??P?0
> Echo Canceller:
> Configuration
> =====================> 
> 
> Channel map:
> 
> Channel 01: FXS Kewlstart (Default) (Slaves: 01)
> 
> 1 channels configured.
> 
> ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device (25)
What exactly is channel 1? Maybe you got the wrong number?

cat /proc/zaptel/*

-- 
Tzafrir Cohen         sip:tzafrir@local.xorcom.com
icq#16849755          iax:tzafrir@local.xorcom.com
+972-50-7952406          jabber:tzafrir@jabber.org
tzafrir.cohen@xorcom.com     http://www.xorcom.com

Morten Isaksen

2006-Sep-25 12:27 UTC

head link

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

On 9/25/06, Tzafrir Cohen <tzafrir.cohen@xorcom.com>
wrote:>
> > [root@mythtv zaptel-1.4.0-beta1]# ztcfg -vvv
> > Notice: Configuration file is /etc/zaptel.conf
> > line 235: Unable to read Zaptel version information.
> >
> > Zaptel Version: $??P?0
> > Echo Canceller:
> > Configuration
> > =====================> >
> >
> > Channel map:
> >
> > Channel 01: FXS Kewlstart (Default) (Slaves: 01)
> >
> > 1 channels configured.
> >
> > ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device (25)
>
> What exactly is channel 1? Maybe you got the wrong number?
>
> cat /proc/zaptel/*


[root@mythtv zaptel-1.4.0-beta1]# service zaptel start
Loading zaptel framework:                                  [  OK  ]
Waiting for zap to come online...OK
Loading zaptel hardware modules:Running ztcfg:  ZT_CHANCONFIG failed on
channel 1: Inappropriate ioctl for device (25)
                                                           [FAILED]
[root@mythtv zaptel-1.4.0-beta1]# cat /proc/zaptel/*
Span 1: WCFXO/0 "Wildcard X101P Board 1"

           1 WCFXO/0/0

The same configuration works perfect with zaptel 1.2.1

-- 
Morten Isaksen
http://www.misak.dk/blog/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060925/0a5e4a95/attachment.htm

Tzafrir Cohen

2006-Sep-26 01:07 UTC

head link

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

On Mon, Sep 25, 2006 at 09:27:20PM +0200, Morten Isaksen
wrote:> On 9/25/06, Tzafrir Cohen <tzafrir.cohen@xorcom.com> wrote:
> >
> >> [root@mythtv zaptel-1.4.0-beta1]# ztcfg -vvv
> >> Notice: Configuration file is /etc/zaptel.conf
> >> line 235: Unable to read Zaptel version information.
> >>
> >> Zaptel Version: $??P?0
> >> Echo Canceller:
> >> Configuration
> >> =====================> >>
> >>
> >> Channel map:
> >>
> >> Channel 01: FXS Kewlstart (Default) (Slaves: 01)
> >>
> >> 1 channels configured.
> >>
> >> ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device
(25)
> >
> >What exactly is channel 1? Maybe you got the wrong number?
> >
> >cat /proc/zaptel/*
> 
> 
> 
> [root@mythtv zaptel-1.4.0-beta1]# service zaptel start
> Loading zaptel framework:                                  [  OK  ]
> Waiting for zap to come online...OK
> Loading zaptel hardware modules:Running ztcfg:  ZT_CHANCONFIG failed on
> channel 1: Inappropriate ioctl for device (25)
>                                                           [FAILED]
> [root@mythtv zaptel-1.4.0-beta1]# cat /proc/zaptel/*
> Span 1: WCFXO/0 "Wildcard X101P Board 1"
> 
>           1 WCFXO/0/0
> 
> The same configuration works perfect with zaptel 1.2.1
Next thing to do, I guess, is to run:

strace ztcfg

to see which device exactly is accessed . Though /dev/zap/ctl is the
usual suspect.

-- 
Tzafrir Cohen         sip:tzafrir@local.xorcom.com
icq#16849755          iax:tzafrir@local.xorcom.com
+972-50-7952406          jabber:tzafrir@jabber.org
tzafrir.cohen@xorcom.com     http://www.xorcom.com

Morten Isaksen

2006-Sep-26 12:32 UTC

head link

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

On 9/26/06, Tzafrir Cohen <tzafrir.cohen@xorcom.com>
wrote:>
> Next thing to do, I guess, is to run:
>
> strace ztcfg
>
> to see which device exactly is accessed . Though /dev/zap/ctl is the
> usual suspect.


[root@mythtv zaptel-1.4.0-beta1]# strace ztcfg
execve("/sbin/ztcfg", ["ztcfg"], [/* 25 vars */]) = 0
uname({sys="Linux", node="mythtv", ...}) = 0
brk(0)                                  = 0x8779000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=87164, ...}) = 0
old_mmap(NULL, 87164, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf6fea000
close(3)                                = 0
open("/lib/tls/libm.so.6", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\363C"...,
512) 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=215248, ...}) = 0
old_mmap(0x43c000, 139424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0x43c000
old_mmap(0x45d000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x20000) = 0x45d000
close(3)                                = 0
open("/lib/tls/libc.so.6", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0
\0372\000"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1512400, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xf6fe9000
old_mmap(0x30d000, 1207532, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0x30d000
old_mmap(0x42e000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x120000) = 0x42e000
old_mmap(0x432000, 7404, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x432000
close(3)                                = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xf6fe8000
mprotect(0x42e000, 8192, PROT_READ)     = 0
mprotect(0x45d000, 4096, PROT_READ)     = 0
mprotect(0x309000, 4096, PROT_READ)     = 0
set_thread_area({entry_number:-1 -> 6, base_addr:0xf6fe86c0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
munmap(0xf6fea000, 87164)               = 0
open("/dev/zap/ctl", O_RDWR)            = 3
brk(0)                                  = 0x8779000
brk(0x879a000)                          = 0x879a000
open("/etc/zaptel.conf", O_RDONLY)      = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=9532, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
0xf6fff000
read(4, "#\n# Zaptel Configuration File\n#\n"..., 4096) = 4096
read(4, "he list remains idle\n# \"clear\"  "..., 4096) =
4096
read(4, "le is a single tone DCS transmit"..., 4096) = 1340
read(4, "", 4096)                       = 0
close(4)                                = 0
munmap(0xf6fff000, 4096)                = 0
ioctl(3, 0x80844a05, 0xfef3aad0)        = -1 EINVAL (Invalid argument)
ioctl(3, 0x404c4a13, 0x807a7cc)         = -1 ENOTTY (Inappropriate ioctl for
device)
write(2, "ZT_CHANCONFIG failed on channel "..., 71ZT_CHANCONFIG failed
on
channel 1: Inappropriate ioctl for device (25)
) = 71
close(3)                                = 0
exit_group(1)                           = ?

/Morten
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060926/045fd888/attachment.htm

asterisk users - Sep 2006 - Problem with zaptel 1.4b2 and X101P Wildcard

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard

[asterisk-users] Problem with zaptel 1.4b2 and X101P Wildcard