On Feb 1, 2008, at 6:17 PM, Mike Jagdis wrote:

> On Wed, Jan 30, 2008 at 02:38:46PM -0500, Daniel Melnechuk wrote:
>> Using callweaver RC5 with a Linksys PAP2T-NA ata on a PowerMac G4
>> dual processor 500MHz, 1.5GB RAM, gigabit enet.
>>
>> [...]
>>
>> CallWeaver sip.conf is set to use dtmfmode=rfc2833 for calls to the
>> outside world via my SIP provider. The sip.conf entry for the PAP2T
>> lines have dtmfmode=rfc2833 set as well.
>
> There were significant changes to rfc2833 signalling post-RC5. Current
> SVN, nightly snapshot or RC6 (when released) get it right. Or at least
> vastly better :-)
>
> Mike
>
>

Hi Mike,

I downloaded 20080201 snapshot and tried to build and when i run  
configure i get these messages:

checking vale.h usability... no
checking vale.h presence... no
checking for vale.h... no
configure: error: Vale version 0.0.1 or newer is required to compile  
Callweaver.

My configure command on mac os x 10.4.11:

$ CFLAGS="-I/usr/local/callweaver/include" LDFLAGS="-L/usr/local/ 
callweaver/lib" \
  \
  ./configure \
    --enable-iax-trunking=yes \
    --enable-t38=yes \
    --prefix=/usr/local/callweaver \
    --enable-mysql=yes \
    --with-app_dtmftotext \
    --enable-jabber=yes \
    --enable-javascript=yes \
    --enable-srtp=yes

My set of commands to build vale are:

$ curl -O http://www.soft-switch.org/downloads/vale/vale-0.0.2.tgz
$ tar zxf vale-0.0.2.tgz
$ cd vale-0.0.1
$ CFLAGS="-I/usr/local/callweaver/include" LDFLAGS="-L/usr/local/ 
callweaver/lib" \
  ./configure --prefix=/usr/local/callweaver
$ make
$ sudo make install

The vale lib and the vale headers are in the correct place. The 1.2.0- 
RC5 configure worked fine but it didn't need vale.

Is anyone else a bit curious as to why vale-0.0.2.tgz when unpacked  
makes a dir called vale-0.0.1???

Any thoughts on why configure for callweaver can't find what is there?

Peace,
Dan
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to