freeswitch/libs/portaudio/build/dev-cpp
Anthony Minessale 39a9e94305 New mod_portaudio (sponspred by eWorldCom http://www.eworldcom.hu/)
This updates mod_portaudio to use the new v19 api and also contains
major behavioural changes.  This initial check-in should be tested to find
any obscure use cases that lead to crashes etc...

All of the old api interface commands are now depricated and any attempt to
use them should cause a polite warning asking you to try the new single "pa" command.

New Features:
*) Mulitiple calls with hold/call switching.
*) Inbound calls can play a ring file on specified device. (global and per call)
*) Optional hold music for backgrounded calls. (global and per call)


Example dialplan usage:

<extension name="2000">
  <condition field="destination_number" expression="^2000$">
    <!--if the next 3 lines are omitted the defaults will be used from portaudio.conf-->
    <action application="set" data="pa_ring_file=/sounds/myring.wav"/>
    <action application="set" data="pa_hold_file=/sounds/myhold.wav"/>
    <action application="set" data="export_vars=pa_ring_file,pa_hold_file"/>
    <action application="bridge" data="portaudio"/>
  </condition>
</extension>


Example API interface usage:

call extension 1000
> pa call 1000

call extension 1001 putting the other call on hold
> pa call 1001

swap the calls between hold and active
> pa switch

view the current calls
> pa list

forground the call with id 1 
> pa switch 1

background all calls
> pa switch none

send a dtmf string (1234) to the current call
> pa dtmf 1234

answer the oldest unanswered inbound call
> pa answer

answer the call with id 1
> pa answer 1

hangup the active call
> pa hangup

hangup the call with id 1
> pa hangup 1

get device info
> pa dump

print usage summary
> pa help


USAGE:
--------------------------------------------------------------------------------
pa help
pa dump
pa call <dest> [<dialplan> <cid_name> <cid_num> <rate>]
pa answer [<call_id>]
pa hangup [<call_id>]
pa list
pa switch [<call_id>|none]
pa_dtmf <digit string>
--------------------------------------------------------------------------------

The source of the portaudio v19 library will also be checked in for the 
sake of the build system.




git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@3981 d0543943-73ff-0310-b7d9-9358b9ac24b2
2007-01-17 19:10:03 +00:00
..
Makefile-dll New mod_portaudio (sponspred by eWorldCom http://www.eworldcom.hu/) 2007-01-17 19:10:03 +00:00
Makefile-static New mod_portaudio (sponspred by eWorldCom http://www.eworldcom.hu/) 2007-01-17 19:10:03 +00:00
portaudio-dll.dev New mod_portaudio (sponspred by eWorldCom http://www.eworldcom.hu/) 2007-01-17 19:10:03 +00:00
portaudio-static.dev New mod_portaudio (sponspred by eWorldCom http://www.eworldcom.hu/) 2007-01-17 19:10:03 +00:00
readme.txt New mod_portaudio (sponspred by eWorldCom http://www.eworldcom.hu/) 2007-01-17 19:10:03 +00:00

From: "Peter L Jones" 
Sent: Wednesday, September 17, 2003 5:18 AM
Subject: Dev-C++ project files

I attach two project files intended for portaudio/pa_win/dev-cpp (i.e. in
parallel with the msvc directory), if you want them.  One is for a static
library build and one for a DLL.  I've used the static library (in building
a single monolithic DLL) but I can't guarantee the DLL version will build a
working library (I think it's mostly there, though!).

I also attach the resulting makefiles, which may be of use to other MinGW
users.

They're rooted in the directory given above and drop their object and
library files in the same place.  They assume the asiosdk2 files are in the
same directory as portaudio/ in a sub-directory called asiosdk2/.  Oh!  The
DLL is built against a static asiosdk2.a library... maybe not the best way
to do it...  I ought to figure out how to link against a "home made" dll in
Dev-C++, I guess ;-)

Cheers,

-- Peter