List Info

Thread: ok we have it working




ok we have it working
country flaguser name
United States
2007-04-01 22:24:59
ok at this point we have asterisk 1.4.2 zaptel 1.4 libpri
1.4 and 
asterisk-addons 1.4 working . But there is a issue the patch
stops 
asterisk-h323c in the addons from building. The reason for
this is the 
configure fails to run. So I had to disable it.  I will work
this week on 
getting it all fixed.

we are looking to do a pr and get a porter to commit it to
the ports tree.

I am back to working on getting freepbx to work also. I am
down to the 
install_amp file and making its changes.

I hope to have it finished soon
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

Re: ok we have it working
country flaguser name
Netherlands
2007-04-02 04:40:16
Richard Neese wrote:
> ok at this point we have asterisk 1.4.2 zaptel 1.4
libpri 1.4 and 
> asterisk-addons 1.4 working . But there is a issue the
patch stops 
> asterisk-h323c in the addons from building. The reason
for this is the 
> configure fails to run. So I had to disable it.  I will
work this week on 
> getting it all fixed.
> 
> we are looking to do a pr and get a porter to commit it
to the ports tree.
> 
> I am back to working on getting freepbx to work also. I
am down to the 
> install_amp file and making its changes.
> 
> I hope to have it finished soon

Thx for the work done.
I upgraded one server this weekend to 1.4.2 with
asterisk-merge. I use
chan_capi for ISDN-2 support. I need zaptel just voor
ztdummy timing.

Compiling and installation was succesful. For
asterisk-addons I needed
to modify the Makefile to include -I/usr/local/include.

I have one issue, transcoding to/from GSM does not work. It
did work
with 1.2.13 from ports, with the gsm port. Now I have
silence. I
disabled it for now and use the alaw codec.

For the rest it seems ok now.

With kind regards,

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

Re: ok we have it working
country flaguser name
United States
2007-04-02 09:12:37
where did you put the include line. I also have a
-I/usr/local/include line 
but the asterisk-oh323c would not configure. avary thing
else worked fine.
_______________________________________________
Asterisk-BSD mailing list
Asterisk-BSDlists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-bsd

Re: ok we have it working
country flaguser name
Russian Federation
2007-04-04 07:01:30
On Mon, 2 Apr 2007 07:12:37 -0700, Richard Neese wrote
> where did you put the include line. I also have a -
> I/usr/local/include line but the asterisk-oh323c would
not 
> configure. avary thing else worked fine. 

1. Please update zaptel from svn
I have "link_elf: symbol calloc undefined". From
svn its work.
2.  Need correction in port net/asterisk
-BUILD_DEPENDS+=
$/include/zaptel.h:$/misc/zaptel 
+BUILD_DEPENDS+=
$/include/zaptel/zaptel.h:$/misc/zaptel


Thanks.
_______________________
Best regards, 
VipeR

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

Re: ok we have it working
country flaguser name
Chile
2007-04-04 09:17:37
El mié, 04-04-2007 a las 18:01 +0600, viper escribió:
> On Mon, 2 Apr 2007 07:12:37 -0700, Richard Neese wrote
> > where did you put the include line. I also have a
-
> > I/usr/local/include line but the asterisk-oh323c
would not 
> > configure. avary thing else worked fine. 
> 
> 1. Please update zaptel from svn
> I have "link_elf: symbol calloc undefined".
From svn its work.


It is wired.. becouse the two last changes in the zaptel-1.4
tree are:

2007-04-04 03:15:24 (Minor spacing/formatting)
2007-03-28 08:50:15

The last zaptel snapshot misc/zaptel uses is from 31 Marz.

I could bet you'r outdated. please re-run asterisk-merge



I think this is a good example, why zaptel-1.4 should be
having releases
(or tags..).. lets make some!!


> 2.  Need correction in port net/asterisk
> -BUILD_DEPENDS+=
$/include/zaptel.h:$/misc/zaptel 
> +BUILD_DEPENDS+=
$/include/zaptel/zaptel.h:$/misc/zaptel

> 

Woop.. thanks!

> Thanks.
> _______________________
> Best regards, 
> VipeR
> 
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSDlists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd

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

Re: ok we have it working
country flaguser name
Chile
2007-04-05 08:17:43
El jue, 05-04-2007 a las 19:03 +0600, viper escribió:
> 
> Sorry for noise, but i saw another problem (feature). 
> 
Wait.. it does compile only when you have the headers in
both places?




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

Re: ok we have it working
country flaguser name
Russian Federation
2007-04-05 08:30:33
On Thu, 05 Apr 2007 09:17:43 -0400, Phillip Neumann wrote
> El jue, 05-04-2007 a las 19:03 +0600, viper
[UTF-8?]escribió:
> > 
> > Sorry for noise, but i saw another problem
(feature). 
> > 
> Wait.. it does compile only when you have the headers
in both places?

Yes.
because configure run following check.
"checking for ZT_DIAL_OP_CANCEL in zaptel/zaptel.h...
no"

_______________________
Best regards, 
VipeR

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

Re: ok we have it working
country flaguser name
Russian Federation
2007-04-05 08:03:11
>2.  Need correction in port net/asterisk
>-BUILD_DEPENDS+=
$/include/zaptel.h:$/misc/zaptel 
>+BUILD_DEPENDS+=
$/include/zaptel/zaptel.h:$/misc/zaptel


Sorry for noise, but i saw another problem (feature). 

I run "make configure" in latest port
net/asterisk.

without zaptel.h in /usr/local/include/
checking zaptel/tonezone.h usability... no
checking zaptel/tonezone.h presence... no
checking for zaptel/tonezone.h... no
chan_zap don`t want compile.

with zaptel.h in /usr/local/include/ and
/usr/local/include/zaptel/
checking zaptel/tonezone.h usability... yes
checking zaptel/tonezone.h presence... yes
checking for zaptel/tonezone.h... yes
chan_zap compile.

_______________________
Best regards, 
VipeR

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

Re: ok we have it working
country flaguser name
Chile
2007-04-05 08:56:27
El jue, 05-04-2007 a las 19:30 +0600, viper escribió:
> > Wait.. it does compile only when you have the
headers in both
> places?
> 
> Yes.
> because configure run following check.
> "checking for ZT_DIAL_OP_CANCEL in
zaptel/zaptel.h... no"
> 

checking for ZT_DIAL_OP_CANCEL in zaptel/zaptel.h... yes
checking for ZT_EVENT_REMOVED in zaptel/zaptel.h... yes
checking for ZT_TCOP_ALLOCATE in zaptel/zaptel.h... yes

rootAsterisk14 /usr/ports/net/asterisk> ls
/usr/local/include/zaptel.*
ls: /usr/local/include/zaptel.*: No such file or directory
rootAsterisk14 /usr/ports/net/asterisk> ls
/usr/local/include/zaptel  
tonezone.h      zaptel.h

it seem to work over here...




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

Re: ok we have it working
country flaguser name
Russian Federation
2007-04-05 02:11:48
On Wed, 04 Apr 2007 10:17:37 -0400, Phillip Neumann wrote
> > 1. Please update zaptel from svn
> > I have "link_elf: symbol calloc
undefined". From svn its work.
> 
> It is wired.. becouse the two last changes in the
zaptel-1.4 tree are:
> 
> 2007-04-04 03:15:24 (Minor spacing/formatting)
> 2007-03-28 08:50:15
> 
> The last zaptel snapshot misc/zaptel uses is from 31
Marz.
> 
> I could bet you'r outdated. please re-run
asterisk-merge 
> 
> I think this is a good example, why zaptel-1.4 should
be having releases
> (or tags..).. lets make some!!
I use asterisk-merge yesterday. 
"PORTNAME=       zaptel
PORTVERSION=    1.4r20070331"
from ports trunk = wct4xxp.ko  806891 bytes
from svn  = wct4xxp.ko  806836 bytes
>From svn it works.
What is wrong??
_______________________
Best regards, 
VipeR

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

[1-10] [11-12]

about | contact  Other archives ( Real Estate discussion Medical topics )