[Asterisk-bsd] Zaptel for 1 port TDM400P

[Chris Willis]

Thanks for your reponse, Chris. It helped a lot but also caused another
problem. While the TDM card now appears ok (I cannot test it remotely just
now), the new software caused a RED alarm on the X101P card. So it looks
like I now have phones but no line. Any suggestions are appreciated as
always.

thanks
cw

On Wed, 30 Jun 2004, Chris Stenton wrote:

> I Think you will find that the latest zaptel FreeBSD port (0.5)  has some
> TDM support however its interface is for the ports version of asterisk. If
> you try and run the asterisk CVS-head then it will panic your machine as the
> zaptel interface has changed.
>
> I am not sure what is happening with the zaptel driver for the
> asterisk-head. Maybe Rich or Olle can bring some light to the matter.
>
> The X101P messages that you see from the driver are fine.
>
> Chris
>
> ----- Original Message -----
> From: "Chris Willis" <chris@mokum.org>
> To: <asterisk-bsd@lists.digium.com>
> Sent: Tuesday, June 29, 2004 10:38 PM
> Subject: [Asterisk-bsd] Zaptel for 1 port TDM400P
>
>
> > Perhaps someone can help me with this. I read at
> > http://www.voip-info.org/wiki-FreeBSD+zaptel that the current Zaptel
> > drivers for FreeBSD support the TDM400P in beta at least. I have a
> > FreeBSD system installed (5.2.1) and the X101P card works well enough
> > but I cannot get my system to even -see- the TDM card. And yes, the
> > 12V power supply is connected.
> >
> > I also read in the archives a message from the middle of this month
> > saying that the drivers for the TDM were being worked on so maybe I
> > just have to wait but I'm wondering if anyone has been able to
> > successfully get things up and running.
> >
> > To be honest, I'm quite new to all this but really have read all the
> > manuals and references I can find on it.
> >
> > FYI the info below came at the end of the last boot. I don't think it
> > has anything to do with the TDM card as only the X101P is mentioned
> > but thought I'd include it to be on the safe side.
> >
> > Jun 29 23:10:20 vuur kernel: WARNING: driver "zaptel" used unreserved
> major device number 196
> > Jun 29 23:10:20 vuur kernel: Zapata Telephony Interface Registered on
> major 196
> > Jun 29 23:10:20 vuur kernel: ZapTel device: vendor=e159 device=1
> subvendor=8085
> > Jun 29 23:10:20 vuur kernel: wcfxo0: <Wildcard X101P> port 0xe800-0xe8ff
> mem 0xfe123000-0xfe123fff irq 25 at device 6.0 on pci0
> > Jun 29 23:10:20 vuur kernel: ZapTel Attach for wcfxo0: deviceID : 0xe159
> > Jun 29 23:10:20 vuur kernel: Wildcard X101P Board 1
> > Jun 29 23:10:21 vuur kernel: NMI ISA 30, EISA ff
> > Jun 29 23:10:21 vuur kernel: wcfxo: DAA mode is 'FCC'
> > Jun 29 23:10:21 vuur kernel: Found a Wildcard FXO: Wildcard X101P
> > Jun 29 23:10:21 vuur kernel: ZapTel device loaded.
> > Jun 29 23:10:48 vuur kernel: Recalculating slaves on WCFXO/0/0
> > Jun 29 23:10:48 vuur kernel: Done Recalculating slaves on WCFXO/0/0 (last
> is WCFXO/0/0)
> > Jun 29 23:10:48 vuur kernel: Configured channel WCFXO/0/0, flags 0201, sig
> 2004
> >
> > Thanks for any help.
> >
> > Chris
> >
> > --
> > Chris Willis                          mailto:chris@mokum.org
> >
> >
> >
> > _______________________________________________
> > Asterisk-BSD mailing list
> > Asterisk-BSD@lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-bsd
> >
>
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>