Zaptel BSD 1.4 for Asterisk 1.4

As 6.2 was recently launched, I thought I'd try the latest
stuff for
Zaptel-BSD.

The latest asterisk 1.2 compatible code (from the /trunk of
zaptel-bsd dir
tree) was broken, but the suggested fix for the ports
(remove zaptel.h
from /usr/local/include) solves this.

I thought I'd give 1.4 a shot, and so I tried the code
under
"branches-1.4". This died looking for
ZAPTEL_VERSION at 944 of zaptel.c. A
quick grep doesn't turn up any reference to this.

I'm just wondering if anyone has gotten this compiled, and
if so, what svn
revision number are you using? I'd love to test it out.

Thanks,
J
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

On Fri, 26 Jan 2007, Jerry wrote:

> As 6.2 was recently launched, I thought I'd try the
latest stuff for
> Zaptel-BSD.
>
> The latest asterisk 1.2 compatible code (from the
/trunk of zaptel-bsd dir
> tree) was broken, but the suggested fix for the ports
(remove zaptel.h
> from /usr/local/include) solves this.
>
> I thought I'd give 1.4 a shot, and so I tried the code
under
> "branches-1.4". This died looking for
ZAPTEL_VERSION at 944 of zaptel.c. A
> quick grep doesn't turn up any reference to this.
>
> I'm just wondering if anyone has gotten this compiled,
and if so, what svn
> revision number are you using? I'd love to test it
out.

I had this and a couple of other errors (don't have my notes
in front of
me, they were somewhere around line 685 if memory serves)
and when I 
deleted /usr/local/include/zaptel.h it compiled fine.  You
may want to
make sure there isn't another zaptel.h somewhere that you
missed.

Once it compiled and I loaded it, zttool showed no alarms on
my x100p
(or x101p, whatever it is).  But asterisk fails configure
saying my 
version of zaptel is too old - I just got it from svn, so
there's still
another problem.

Strangely enough, during configure it gives me this:

checking for ZT_TONE_DTMF_BASE in zaptel.h... no
checking for ZT_DIAL_OP_CANCEL in zaptel.h... yes

right before it errors and a grep of
/usr/local/include/zaptel shows
ZT_TONE_DTMF_BASE in there and set - probably a #define
taking it out
'cuze there is not another zaptel.h anywhere it'd look.  If
anyone has
a fix for that before I find it, it'd be appreciated.

Vince.
-- 
   Michigan VHF Corp.   http://www.nobucks.net/  
http://www.coloser.com/
            Bringing the world a little coloser to your
business


_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

Hello.

On Mon, Jan 29, 2007 at 07:24:13AM -0500, Vince Vielhaber
wrote:
> 
> On Fri, 26 Jan 2007, Jerry wrote:
> 
> >As 6.2 was recently launched, I thought I'd try the
latest stuff for
> >Zaptel-BSD.
> >
> >The latest asterisk 1.2 compatible code (from the
/trunk of zaptel-bsd dir
> >tree) was broken, but the suggested fix for the
ports (remove zaptel.h
> >from /usr/local/include) solves this.
> >
> >I thought I'd give 1.4 a shot, and so I tried the
code under
> >"branches-1.4". This died looking for
ZAPTEL_VERSION at 944 of zaptel.c. A
> >quick grep doesn't turn up any reference to this.
> >
> >I'm just wondering if anyone has gotten this
compiled, and if so, what svn
> >revision number are you using? I'd love to test it
out.
> 
> I had this and a couple of other errors (don't have my
notes in front of
> me, they were somewhere around line 685 if memory
serves) and when I 
> deleted /usr/local/include/zaptel.h it compiled fine. 
You may want to
> make sure there isn't another zaptel.h somewhere that
you missed.

Asterisk 1.4.0 search for zaptel.h and tonezone.h in
/usr/local/include/zaptel, instead of /usr/local/include.

In linux zaptel 1.4.0 also added version.h header file,
w/ZAPTEL_VERSION
defination. I move this defination in zaptel.h header file
in zaptel-1.4 svn
branch and trunk.
 
> Once it compiled and I loaded it, zttool showed no
alarms on my x100p
> (or x101p, whatever it is).  But asterisk fails
configure saying my 
> version of zaptel is too old - I just got it from svn,
so there's still
> another problem.
> 
> Strangely enough, during configure it gives me this:
> 
> checking for ZT_TONE_DTMF_BASE in zaptel.h... no
> checking for ZT_DIAL_OP_CANCEL in zaptel.h... yes
> 
> right before it errors and a grep of
/usr/local/include/zaptel shows
> ZT_TONE_DTMF_BASE in there and set - probably a #define
taking it out
> 'cuze there is not another zaptel.h anywhere it'd look.
 If anyone has
> a fix for that before I find it, it'd be appreciated.

 That svn revision You use? In old revision (may be prior
94) defination
of ZT_TONE_DTMF_BASE was masked from asterisk by #ifdef
_KERNEL directive.
Now I compile asterisk-1.4.0 w/zaptel from trunk and
zaptel-1.4 branch 
without any problem.

 But make sure, that You have new header files zaptel.h and
tonezone.h in
/usr/local/include/zaptel directory. And use new ztcfg from
./ztcfg
directory. 

-- 
Best Regards, Yuri.
	Yuri Saltikov
	mailto: yurirus.net
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

On Mon, 29 Jan 2007, Yuri wrote:

>> Once it compiled and I loaded it, zttool showed no
alarms on my x100p
>> (or x101p, whatever it is).  But asterisk fails
configure saying my
>> version of zaptel is too old - I just got it from
svn, so there's still
>> another problem.
>>
>> Strangely enough, during configure it gives me
this:
>>
>> checking for ZT_TONE_DTMF_BASE in zaptel.h... no
>> checking for ZT_DIAL_OP_CANCEL in zaptel.h... yes
>>
>> right before it errors and a grep of
/usr/local/include/zaptel shows
>> ZT_TONE_DTMF_BASE in there and set - probably a
#define taking it out
>> 'cuze there is not another zaptel.h anywhere it'd
look.  If anyone has
>> a fix for that before I find it, it'd be
appreciated.
>
> That svn revision You use? In old revision (may be
prior 94) defination
> of ZT_TONE_DTMF_BASE was masked from asterisk by #ifdef
_KERNEL directive.
> Now I compile asterisk-1.4.0 w/zaptel from trunk and
zaptel-1.4 branch
> without any problem.
>
> But make sure, that You have new header files zaptel.h
and tonezone.h in
> /usr/local/include/zaptel directory. And use new ztcfg
from ./ztcfg
> directory.

I got it compiled but after further review I noticed that
chan-zap wasn't
built.  I then created the dir /usr/local/include/zaptel and
moved both
zaptel.h and tonezone.h into it.  Did a distclean and
configure on 
asterisk and all appeared to be well.

Then I started compiling and got about 40 errors for
codec-zap.c that
looks like at least most of them are caused by struct
zt_transcode_header
not being declared anywhere.  A recursive grep did find it
in at least
one zaptel.h in a branch but not in trunk or the installed
zaptel.h.

Should I be using something other than trunk or should I add
the missing
struct declaration to zaptel.h?

Vince.
-- 
   Michigan VHF Corp.   http://www.nobucks.net/  
http://www.coloser.com/
            Bringing the world a little coloser to your
business


_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

On Mon, 29 Jan 2007, Vince Vielhaber wrote:

> On Mon, 29 Jan 2007, Yuri wrote:
>
>>> Once it compiled and I loaded it, zttool showed
no alarms on my x100p
>>> (or x101p, whatever it is).  But asterisk fails
configure saying my
>>> version of zaptel is too old - I just got it
from svn, so there's still
>>> another problem.
>>> 
>>> Strangely enough, during configure it gives me
this:
>>> 
>>> checking for ZT_TONE_DTMF_BASE in zaptel.h...
no
>>> checking for ZT_DIAL_OP_CANCEL in zaptel.h...
yes
>>> 
>>> right before it errors and a grep of
/usr/local/include/zaptel shows
>>> ZT_TONE_DTMF_BASE in there and set - probably a
#define taking it out
>>> 'cuze there is not another zaptel.h anywhere
it'd look.  If anyone has
>>> a fix for that before I find it, it'd be
appreciated.
>> 
>> That svn revision You use? In old revision (may be
prior 94) defination
>> of ZT_TONE_DTMF_BASE was masked from asterisk by
#ifdef _KERNEL directive.
>> Now I compile asterisk-1.4.0 w/zaptel from trunk
and zaptel-1.4 branch
>> without any problem.
>> 
>> But make sure, that You have new header files
zaptel.h and tonezone.h in
>> /usr/local/include/zaptel directory. And use new
ztcfg from ./ztcfg
>> directory.
>
> I got it compiled but after further review I noticed
that chan-zap wasn't
> built.  I then created the dir
/usr/local/include/zaptel and moved both
> zaptel.h and tonezone.h into it.  Did a distclean and
configure on asterisk 
> and all appeared to be well.
>
> Then I started compiling and got about 40 errors for
codec-zap.c that
> looks like at least most of them are caused by struct
zt_transcode_header
> not being declared anywhere.  A recursive grep did find
it in at least
> one zaptel.h in a branch but not in trunk or the
installed zaptel.h.
>
> Should I be using something other than trunk or should
I add the missing
> struct declaration to zaptel.h?

Ok, answering myself, branch seems to be what I should've
been building
instead of trunk.  With the exception of a problem in the
makefile in
oct612s (it didn't know how to make install) all went well!

Vince.
-- 
   Michigan VHF Corp.   http://www.nobucks.net/  
http://www.coloser.com/
            Bringing the world a little coloser to your
business


_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

> On Mon, 29 Jan 2007, Vince Vielhaber wrote:
> Ok, answering myself, branch seems to be what I
should've been building
> instead of trunk.  With the exception of a problem in
the makefile in
> oct612s (it didn't know how to make install) all went
well!

Is this 1.2 or 1.4 zaptel you are building?

I think if you are building branch, you are building 1.2.

I could be wrong though, and if so I am making the same
mistake you are. 

Thanks,
J.
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

On Mon, 29 Jan 2007, Jerry wrote:

>> On Mon, 29 Jan 2007, Vince Vielhaber wrote:
>> Ok, answering myself, branch seems to be what I
should've been building
>> instead of trunk.  With the exception of a problem
in the makefile in
>> oct612s (it didn't know how to make install) all
went well!
>
> Is this 1.2 or 1.4 zaptel you are building?

1.4

> I think if you are building branch, you are building
1.2.
>
> I could be wrong though, and if so I am making the same
mistake you are. 

That's what threw me, I thought branch would be the current
code but * 
wouldn't compile with it.  In the branches directory is a
subdirectory
called zaptel-1.4 and all went well with that.  Even had a
telemarketer
call on it a little while ago - gonna fix that little
problem real quick!

Vince.
-- 
   Michigan VHF Corp.   http://www.nobucks.net/  
http://www.coloser.com/
            Bringing the world a little coloser to your
business


_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd