[Asterisk-bsd] RE: Asterisk - zaptel 0.5

[Dr. Rich Murphey]

Yep, the FreeBSD ports driver is not yet in sync with asterisk-current, but
my understanding is that that's on the roadmap for those doing the work
currently.

This brings up some tricky release engineering choices - how/where do we
test the integrated FreeBSD and Linux drivers -- as a single set of sources.
Drivers demand a minimum level of stability that's higher in some ways than
the servers -- in that crashing a server is much less painful than panicking
a kernel.

I have a hunch that there is a path of least resistance for testing.

This seems to beg for testing of the integrated driver *before* such code is
committed to the asterisk cvs.  Given the need for stability of
asterisk-current, I suspect it would cause much less discomfort if the
integrated driver were stabilized enough that the impact of committing it to
asterisk-current were bearable in terms of support resources.

Cheers,
Rich

> -----Original Message-----
> From: Richard Neese [mailto:rneese@adelphia.net]
> Sent: Friday, June 18, 2004 7:27 PM
> To: Dr. Rich Murphey
> Cc: asterisk-bsd@lists.digium.com
> Subject: Asterisk - zaptel 0.5
> 
> channel.c:49:2: #error "You need newer zaptel!  Please cvs update zaptel"
> channel.c: In function `ast_channel_alloc':
> channel.c:303: error: `ZT_TIMERPONG' undeclared (first use in this
> function)
> channel.c:303: error: (Each undeclared identifier is reported only once
> channel.c:303: error: for each function it appears in.)
> channel.c: In function `ast_queue_frame':
> channel.c:412: error: `ZT_TIMERPING' undeclared (first use in this
> function)
> channel.c: In function `ast_read':
> channel.c:1185: error: `ZT_EVENT_TIMER_EXPIRED' undeclared (first use in
> this
> function)
> channel.c:1187: error: `ZT_EVENT_TIMER_PING' undeclared (first use in this
> function)
> channel.c:1196: error: `ZT_TIMERPONG' undeclared (first use in this
> function)
> gmake: *** [channel.o] Error 1
> mypbx#
> 
> this is with -head and and fbsd 5.2.1-p8
>