[Asterisk-bsd] Status on *BSD, particularly NetBSD?

Michael G. Petry petry at NetMasters.Com
Thu Oct 14 20:41:55 CDT 2004


Jeff,
	I've seen similar error messages on an TDM400 with FXS modules
when the auxiliary power connector on the board isn't plugged in. The
molex connector provides the +12/+5 that the SLIC modules need to power up. 

> Well, since the card I ordered just came, I decided to test it out with 
> FreeBSD 5.2.1-release, and the TDM400 FXS module.  Here's the console 
> log when I load the drivers:
> 
> 
> (ten-finger copy, sorry... not sure what's up with my cut&paste)
> 
> WARNING: driver "zaptel" used unreserved major device number 196
> Zapata Telephony Interface Registered on major 196
> FXS device: vendor=e159 device=1 subvendor=b100
> wcfxs0: <Wildcard TDM400P REV E/F> port 0xe800-0xe8ff mem 
> 0xfebff000-0xfebfffff
> irq 27 at device 2.0 on pci1
> FXS attach for wcfxs0: deviceID: 0xe159
> Freshmaker version: 71
> Freshmaker passed register test
> ProSLIC on module 0 failed to powerup within 510 ms (0 mV only)
> Unable to do INITIAL ProSLIC powerup on module 0
> ProSLIC on module 0 failed to powerup within 510 ms (0 mV only)
> Unable to do INITIAL ProSLIC powerup on module 0
> Module 0: FAILED FXS
> Module 1: Installed -- AUTO FXO
> Module 2: Not installed
> Module 3: Not installed
> Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)
> 
> 
> So it would appear that the TDM400 FXS doesn't work with FreeBSD at this 
> point...
> 
> +j
> 
> Chris Stenton wrote:
> 
> > Current state of FreeBSD port
> >
> >    ZTDummy    yes
> >    X100P - yes
> >    TDM400 FXO - yes
> >    TDM400 FXS - have it but, but has not been tested yet.
> >    T100P - in but very alpha
> >
> > You need some form of timer for meetme and IAX2 trunking. Other 
> > functions will work without a timer but perform more reliably with a 
> > timer.
> >
> > I believe someone is looking at a netbsd port.
> >
> > Chris
> >
> >
> >
> > ----- Original Message ----- From: "Jeff Rizzo" 
> > <riz+asterisk at boogers.sf.ca.us>
> > To: "Asterisk on BSD discussion" <asterisk-bsd at lists.digium.com>
> > Sent: Thursday, October 14, 2004 7:07 PM
> > Subject: [Asterisk-bsd] Status on *BSD, particularly NetBSD?
> >
> >
> >> I'm coming into this as a relative newbie on asterisk, having been 
> >> playing around with it seriously for about a week.  I'm using the cvs 
> >> HEAD from about that time, with the patch that Tom Ivar Helbemekko 
> >> posted to this list a few days ago, and things seem to be working 
> >> relatively well with an all-SIP configuration on NetBSD-2.0_RC4.  I'm 
> >> convinced that asterisk is a solid piece of software, and I want to 
> >> go ahead with plans to use it both in my business and at home.
> >>
> >> My preferred platform is NetBSD;  a second choice would be FreeBSD, 
> >> but I'm willing (if not anywhere near eager) to run Linux if it's 
> >> necessary. I am going to need to integrate with the PSTN using both 
> >> FXS and FXO ports, and will also need to run IAX2 and meetme. From 
> >> everything I've read over the last week, the Wildcard boards seem to 
> >> be the best bet, but there's some confusion about the state of BSD 
> >> support.  This leads me to a few questions:
> >>
> >> 1)  Are any of the zaptel drivers being ported to NetBSD?  Am I 
> >> correct in assuming that even if I don't need Zaptel hardware, I'd 
> >> need to use the "ztdummy" driver for the hardware timers necessary 
> >> for IAX2 and meetme?
> >>
> >> 2)  Do the zaptel drivers which have been ported to FreeBSD support 
> >> the TDM400P?  Since I need 1 FXO and 1 FXS port in a 1U form factor, 
> >> this card is my best bet... (plus, I've already ordered one for 
> >> testing!  :) Preferably also support the TDM400P in the cvs HEAD of 
> >> the asterisk code, since that's what I've started using already...
> >>
> >> 3)  If there is _not_ already an effort underway to port the zaptel 
> >> drivers to NetBSD, can anyone suggest a place to start?  I would 
> >> assume starting with the FreeBSD code is best, but it's kind of hard 
> >> to tell even what the current state of affairs with that code is.
> >>
> >> Thanks for all the effort!
> >>
> >> +j
> >>
> >>
> >>
> >> _______________________________________________
> >> Asterisk-BSD mailing list
> >> Asterisk-BSD at lists.digium.com
> >> http://lists.digium.com/mailman/listinfo/asterisk-bsd
> >>
> >
> > _______________________________________________
> > Asterisk-BSD mailing list
> > Asterisk-BSD at lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-bsd
> 
> 
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
> 

Michael Petry




More information about the Asterisk-BSD mailing list