Re: Zaptel on Debian Lenny

2009-11-02 Thread Tzafrir Cohen
On Mon, Nov 02, 2009 at 12:13:19PM -0800, eliyahu cohen wrote:
> --- On Mon, 11/2/09, Tzafrir Cohen  wrote:
> 
> > From: Tzafrir Cohen 
> > Subject: Re: Zaptel on Debian Lenny
> > To: linux-il@cs.huji.ac.il
> > Date: Monday, November 2, 2009, 2:32 PM
> > On Sun, Nov 01, 2009 at 03:01:08PM
> > -0800, eliyahu cohen wrote:
> > > --- On Sun, 11/1/09, ik 
> > wrote:
> > > 
> > > > I recommend you to download the sources, and
> > create
> > > > packages for Debian on your own.
> > > 
> > > Hi Ido,
> > > 
> > > Advice taken. I installed Asterisk
> > SVN-branch-1.4-r226531. 
> > 
> > Note that the version of Asterisk from the package works
> > with Zaptel and
> > not with DAHDI.
> > 
> 
> Hi Tzafrir,
> 
> That's odd. According to:
> 
> http://www.asterisk.org/developer/resources/svn
> 
> which is where I downloaded that version of asterisk, your supposed
> to download DAHDI. Which versions of asterisk work with DAHDI instead
> of Zaptel?

Asterisk 1.4.x , for x > 21 , can be built to support either Zaptel or
DAHDI. This is a build-time decision. 1.6.0 and above only support
DAHDI. 1.4.21 and below only support Zaptel.

As a very practical test:

  strings /usr/sbin/asterisk | grep /dev | egrep 'zap|dahdi'

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
ICQ# 16849754 || friend

___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-02 Thread eliyahu cohen
--- On Mon, 11/2/09, Tzafrir Cohen  wrote:

> From: Tzafrir Cohen 
> Subject: Re: Zaptel on Debian Lenny
> To: linux-il@cs.huji.ac.il
> Date: Monday, November 2, 2009, 2:32 PM
> On Sun, Nov 01, 2009 at 03:01:08PM
> -0800, eliyahu cohen wrote:
> > --- On Sun, 11/1/09, ik 
> wrote:
> > 
> > > I recommend you to download the sources, and
> create
> > > packages for Debian on your own.
> > 
> > Hi Ido,
> > 
> > Advice taken. I installed Asterisk
> SVN-branch-1.4-r226531. 
> 
> Note that the version of Asterisk from the package works
> with Zaptel and
> not with DAHDI.
> 

Hi Tzafrir,

That's odd. According to:

http://www.asterisk.org/developer/resources/svn

which is where I downloaded that version of asterisk, your supposed to download 
DAHDI. Which versions of asterisk work with DAHDI instead of Zaptel?

- EC


  

___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-02 Thread Tzafrir Cohen
On Sun, Nov 01, 2009 at 03:01:08PM -0800, eliyahu cohen wrote:
> --- On Sun, 11/1/09, ik  wrote:
> 
> > I recommend you to download the sources, and create
> > packages for Debian on your own.
> 
> Hi Ido,
> 
> Advice taken. I installed Asterisk SVN-branch-1.4-r226531. 

Note that the version of Asterisk from the package works with Zaptel and
not with DAHDI.

> When I start the dahadi service I get:
> 
> Unloading DAHDI hardware modules: done
> Loading DAHDI hardware modules:
> FATAL: Error inserting dahdi (/lib/modules/2.6.26-2-686/dahdi/dahdi.ko): 
> Device or resource busy
>wcfxo: error
> Error: missing /dev/dahdi!
> 
> dmesg reports:
> [49.154776]  ===
> [49.154776] dahdi: Unable to register DAHDI character device handler on 
> 196

I suspect you have the module zaptel loaded. Both register the same
major number.

lsmod | grep 'zaptel|dahdi'

Try:

  rmmod zaptel

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
ICQ# 16849754 || friend

___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-01 Thread eliyahu cohen
--- On Sun, 11/1/09, ik  wrote:

> I recommend you to download the sources, and create
> packages for Debian on your own.

Hi Ido,

Advice taken. I installed Asterisk SVN-branch-1.4-r226531. When I start the 
dahadi service I get:

Unloading DAHDI hardware modules: done
Loading DAHDI hardware modules:
FATAL: Error inserting dahdi (/lib/modules/2.6.26-2-686/dahdi/dahdi.ko): Device 
or resource busy
   wcfxo: error
Error: missing /dev/dahdi!

dmesg reports:
[49.154776]  ===
[49.154776] dahdi: Unable to register DAHDI character device handler on 196
[49.154782] wcfxo: Unknown symbol dahdi_alarm_notify
[49.155002] wcfxo: Unknown symbol dahdi_transmit
[49.158784] wcfxo: Unknown symbol dahdi_register
[49.158784] wcfxo: Unknown symbol dahdi_hooksig
[49.158784] wcfxo: Unknown symbol dahdi_receive
[49.158784] wcfxo: Unknown symbol dahdi_unregister
[49.158784] wcfxo: Unknown symbol dahdi_ec_chunk

dahdi_scan reports:
Unable to open /dev/dahdi/ctl: No such file or directory

> 
> Also please note that Dahadi/Zaptel are also kernel
> modules, so make sure they are loaded properly prior on
> running Asterisk.

I started the dahadi service before starting asterisk. Based on the error 
messages above, what am I missing?

Thanks,
EC

> 
> 
> 
> Ido
> 
> http://ik.homelinux.org/
> 
> 
> 
> On Sun, Nov 1, 2009 at 3:19 PM,
> eliyahu cohen 
> wrote:
> 
> 
> I installed a X101P card on my Debian Lenny box, along with
> the native Debian asterisk and zaptel packages (asterisk
> 1:1.4.21.2~dfs, zaptel 1:1.4.11~dfsg-). When I run the zap
> command at the asterisk CLI I get a "no such command:
> 
> 
> 
> 
> 
> lab*CLI> zap
> 
> No such command 'zap' (type 'help zap' for
> other possible commands)
> 
> 
> 
> when I try to manually load the chan_zap.so module I get:
> 
> 
> 
> lab*CLI> module load chan_zap.so
> 
> [Nov  1 08:07:54] WARNING[3242]: pbx.c:2981
> ast_register_application: Already have an application
> 'ZapSendKeypadFacility'
> 
>   == Parsing '/etc/asterisk/zapata.conf': Found
> 
> [Nov  1 08:07:54] WARNING[3242]: chan_zap.c:957 zt_open:
> Unable to specify channel 1: Device or resource busy
> 
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:7414 mkintf:
> Unable to open channel 1: Device or resource busy
> 
> here = 0, tmp->channel = 1, channel = 1
> 
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:11900
> build_channels: Unable to register channel '1'
> 
> 
> 
> my zapata.conf file contains:
> 
> [trunkgroups]
> 
> [channels]
> 
> switchtype=national
> 
> signalling=fxo_ks
> 
> rxwink=300
> 
> usecallerid=yes
> 
> hidecallerid=no
> 
> callwaiting=yes
> 
> usecallingpres=yes
> 
> callwaitingcallerid=yes
> 
> threewaycalling=yes
> 
> transfer=yes
> 
> canpark=yes
> 
> cancallforward=yes
> 
> callreturn=yes
> 
> echocancel=yes
> 
> echocancelwhenbridged=yes
> 
> rxgain=0.0
> 
> txgain=0.0
> 
> group=1
> 
> callgroup=1
> 
> pickupgroup=1
> 
> immediate=no
> 
> context=default
> 
> group=0
> 
> channel => 1
> 
> 
> 
> I installed the asterisk package after the zaptel package.
> How can I get zaptel support in the Debian asterisk
> package?
> 
> 
> 
> Thanks,
> 
> EC
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> 
> Linux-il mailing list
> 
> Linux-il@cs.huji.ac.il
> 
> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
> 
> 
> 
> 


  

___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-01 Thread ik
Something is using your device.

If you write:
$ lsmod | grep wcfxo

Do you see any module ?

It usually means what Oron stated: something is using that device, or
blocking it (like a non TIME_OUT process that opened it and locked it out
without releasing it).

Ido

http://ik.homelinux.org/


On Mon, Nov 2, 2009 at 1:01 AM, eliyahu cohen wrote:

> --- On Sun, 11/1/09, ik  wrote:
>
> > I recommend you to download the sources, and create
> > packages for Debian on your own.
>
> Hi Ido,
>
> Advice taken. I installed Asterisk SVN-branch-1.4-r226531. When I start the
> dahadi service I get:
>
> Unloading DAHDI hardware modules: done
> Loading DAHDI hardware modules:
> FATAL: Error inserting dahdi (/lib/modules/2.6.26-2-686/dahdi/dahdi.ko):
> Device or resource busy
>   wcfxo: error
> Error: missing /dev/dahdi!
>
> dmesg reports:
> [49.154776]  ===
> [49.154776] dahdi: Unable to register DAHDI character device handler on
> 196
> [49.154782] wcfxo: Unknown symbol dahdi_alarm_notify
> [49.155002] wcfxo: Unknown symbol dahdi_transmit
> [49.158784] wcfxo: Unknown symbol dahdi_register
> [49.158784] wcfxo: Unknown symbol dahdi_hooksig
> [49.158784] wcfxo: Unknown symbol dahdi_receive
> [49.158784] wcfxo: Unknown symbol dahdi_unregister
> [49.158784] wcfxo: Unknown symbol dahdi_ec_chunk
>
> dahdi_scan reports:
> Unable to open /dev/dahdi/ctl: No such file or directory
>
> >
> > Also please note that Dahadi/Zaptel are also kernel
> > modules, so make sure they are loaded properly prior on
> > running Asterisk.
>
> I started the dahadi service before starting asterisk. Based on the error
> messages above, what am I missing?
>
> Thanks,
> EC
>
> >
> >
> >
> > Ido
> >
> > http://ik.homelinux.org/
> >
> >
> >
> > On Sun, Nov 1, 2009 at 3:19 PM,
> > eliyahu cohen 
> > wrote:
> >
> >
> > I installed a X101P card on my Debian Lenny box, along with
> > the native Debian asterisk and zaptel packages (asterisk
> > 1:1.4.21.2~dfs, zaptel 1:1.4.11~dfsg-). When I run the zap
> > command at the asterisk CLI I get a "no such command:
> >
> >
> >
> >
> >
> > lab*CLI> zap
> >
> > No such command 'zap' (type 'help zap' for
> > other possible commands)
> >
> >
> >
> > when I try to manually load the chan_zap.so module I get:
> >
> >
> >
> > lab*CLI> module load chan_zap.so
> >
> > [Nov  1 08:07:54] WARNING[3242]: pbx.c:2981
> > ast_register_application: Already have an application
> > 'ZapSendKeypadFacility'
> >
> >   == Parsing '/etc/asterisk/zapata.conf': Found
> >
> > [Nov  1 08:07:54] WARNING[3242]: chan_zap.c:957 zt_open:
> > Unable to specify channel 1: Device or resource busy
> >
> > [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:7414 mkintf:
> > Unable to open channel 1: Device or resource busy
> >
> > here = 0, tmp->channel = 1, channel = 1
> >
> > [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:11900
> > build_channels: Unable to register channel '1'
> >
> >
> >
> > my zapata.conf file contains:
> >
> > [trunkgroups]
> >
> > [channels]
> >
> > switchtype=national
> >
> > signalling=fxo_ks
> >
> > rxwink=300
> >
> > usecallerid=yes
> >
> > hidecallerid=no
> >
> > callwaiting=yes
> >
> > usecallingpres=yes
> >
> > callwaitingcallerid=yes
> >
> > threewaycalling=yes
> >
> > transfer=yes
> >
> > canpark=yes
> >
> > cancallforward=yes
> >
> > callreturn=yes
> >
> > echocancel=yes
> >
> > echocancelwhenbridged=yes
> >
> > rxgain=0.0
> >
> > txgain=0.0
> >
> > group=1
> >
> > callgroup=1
> >
> > pickupgroup=1
> >
> > immediate=no
> >
> > context=default
> >
> > group=0
> >
> > channel => 1
> >
> >
> >
> > I installed the asterisk package after the zaptel package.
> > How can I get zaptel support in the Debian asterisk
> > package?
> >
> >
> >
> > Thanks,
> >
> > EC
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> >
> > Linux-il mailing list
> >
> > Linux-il@cs.huji.ac.il
> >
> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
> >
> >
> >
> >
>
>
>
>
___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-01 Thread Tzafrir Cohen
On Sun, Nov 01, 2009 at 05:19:50AM -0800, eliyahu cohen wrote:
> I installed a X101P card on my Debian Lenny box, along with the native Debian 
> asterisk and zaptel packages (asterisk 1:1.4.21.2~dfs, zaptel 
> 1:1.4.11~dfsg-). When I run the zap command at the asterisk CLI I get a "no 
> such command:
> 
> lab*CLI> zap
> No such command 'zap' (type 'help zap' for other possible commands)
> 
> when I try to manually load the chan_zap.so module I get:
> 
> lab*CLI> module load chan_zap.so
> [Nov  1 08:07:54] WARNING[3242]: pbx.c:2981 ast_register_application: Already 
> have an application 'ZapSendKeypadFacility'
>   == Parsing '/etc/asterisk/zapata.conf': Found
> [Nov  1 08:07:54] WARNING[3242]: chan_zap.c:957 zt_open: Unable to specify 
> channel 1: Device or resource busy
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:7414 mkintf: Unable to open channel 
> 1: Device or resource busy
> here = 0, tmp->channel = 1, channel = 1
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:11900 build_channels: Unable to 
> register channel '1'
> 
> my zapata.conf file contains:
> [trunkgroups]
> [channels]
> switchtype=national
> signalling=fxo_ks
> rxwink=300 
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> context=default
> group=0
> channel => 1
> 
> I installed the asterisk package after the zaptel package. How can I get 
> zaptel support in the Debian asterisk package?

As suggested in README.Debian of the package zaptel:

Install the package zaptel-source , and then run:

  m-a a-i zaptel

After which which you should get the zaptel modules available.

Then try:

  modprobe wcfxo
  zapconf

And then:

  /etc/init.d/zaptel start
  /etc/init.d/asterisk restart

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
ICQ# 16849754 || friend

___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-01 Thread Oron Peled
On Sunday, 1 בNovember 2009 15:19:50 eliyahu cohen wrote:
> lab*CLI> module load chan_zap.so
> [Nov  1 08:07:54] WARNING[3242]: pbx.c:2981 ast_register_application: 
Already have an application 'ZapSendKeypadFacility'
>   == Parsing '/etc/asterisk/zapata.conf': Found
> [Nov  1 08:07:54] WARNING[3242]: chan_zap.c:957 zt_open: Unable to specify 
channel 1: Device or resource busy
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:7414 mkintf: Unable to open 
channel 1: Device or resource busy
> here = 0, tmp->channel = 1, channel = 1
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:11900 build_channels: Unable to 
register channel '1'

Since you get a "device busy" error, the first thing to check is which
process keep this channel open. It may be another asterisk process
running in the background, or a zttool you forgot open on another
terminal.

For the definitive answer, simple user fuser(1). For example:
  fuser -v /dev/zap/*

Also, as noted by IK in another reply the zaptel drivers are in the process
of being phased out for DAHDI.

However, I would suggest the opposite from Ido -- try to avoid
building asterisk/DAHDI yourself. You are new to this subject
and so you are bound to make many more mistakes in the process
than the Debian maintainers.

You should try to build your own, only AFTER you have gained experience
with a WORKING asterisk/DAHDI for some time.

Bye,

-- 
Oron Peled Voice: +972-4-8228492
o...@actcom.co.il  http://users.actcom.co.il/~oron
"Linux: like the air you breathe, ubiquitous and free"

___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il


Re: Zaptel on Debian Lenny

2009-11-01 Thread ik
Eliyahu,

Please do not use the default asterisk packages from debian.
They are Unmaintained and old.

Zaptel was changed to Dahadi, and many many changes where made to Asterisk
since 1.4.11.
I recommend you to download the sources, and create packages for Debian on
your own.

Also please note that Dahadi/Zaptel are also kernel modules, so make sure
they are loaded properly prior on running Asterisk.

Ido

http://ik.homelinux.org/


On Sun, Nov 1, 2009 at 3:19 PM, eliyahu cohen wrote:

> I installed a X101P card on my Debian Lenny box, along with the native
> Debian asterisk and zaptel packages (asterisk 1:1.4.21.2~dfs, zaptel
> 1:1.4.11~dfsg-). When I run the zap command at the asterisk CLI I get a "no
> such command:
>
> lab*CLI> zap
> No such command 'zap' (type 'help zap' for other possible commands)
>
> when I try to manually load the chan_zap.so module I get:
>
> lab*CLI> module load chan_zap.so
> [Nov  1 08:07:54] WARNING[3242]: pbx.c:2981 ast_register_application:
> Already have an application 'ZapSendKeypadFacility'
>  == Parsing '/etc/asterisk/zapata.conf': Found
> [Nov  1 08:07:54] WARNING[3242]: chan_zap.c:957 zt_open: Unable to specify
> channel 1: Device or resource busy
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:7414 mkintf: Unable to open
> channel 1: Device or resource busy
> here = 0, tmp->channel = 1, channel = 1
> [Nov  1 08:07:54] ERROR[3242]: chan_zap.c:11900 build_channels: Unable to
> register channel '1'
>
> my zapata.conf file contains:
> [trunkgroups]
> [channels]
> switchtype=national
> signalling=fxo_ks
> rxwink=300
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> context=default
> group=0
> channel => 1
>
> I installed the asterisk package after the zaptel package. How can I get
> zaptel support in the Debian asterisk package?
>
> Thanks,
> EC
>
>
>
>
>
> ___
> Linux-il mailing list
> Linux-il@cs.huji.ac.il
> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
>
___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il