quickstart

multi-line Adjunct Communication Server

Quick Start for Quicknet hardware:

Install Quicknet driver:

	follow the directions for installing the Quicknet driver.  You will
	want to use the latest gpl driver with isapnp support.

Unpack the sources and configure:

use:	cd ACS
	./configure

	The /dev/phone api should be detected during configure.

Make all directories:

use:	make

	The ACS source tree should build to completion without errors.

Activate Quicknet driver(s):

use:	su root
	mknod /dev/phone0 c 100 0
	insmod isapnp.o
	insmod phonedev.o
	insmod ixj.o

	If all goes well, you should be able to examine /proc/ixj and see
	at least one active Quicknet card.

Test "umd" for phone:
	
use:	su root
	cd phone
	./umd_phone -t playrec

	This will start ACS in "test" mode.  In test mode, ACS
	will look in the "distribution" directory for all runtime
	scripts and data files rather than the "install" directory.
	Using "playrec" overrides the scheduler, and assures the
	playrec script is ran.  Just plug in a phone line and call
	your LineJack.

Test "TGI" support:

use:	su root
	cd utils
	./testtgi.sh

	This will start a dummy call and test the entire TGI subsystem.

Quick Start for PIKA hardware and MonteCarlo API:

Unpack the sources and configure:

use:	cd ACS
	./configure

	You may need to review options in the Install File.

Make all directories:

use:	make

	The ACS source tree should build if you have the appropriate
	API libraries based on your configure options.

Test "umd" for Pika:

use:	su root
	cd pika
	./umd_pika -t playrec

	This will start ACS in "test" mode.  In test mode, ACS will
	look for the files in the "distribution" directory for scripts,
	config files, etc, rather than in the installed locations.  The
	"playrec" option forces umd to ignore the scheduler and start
	the "playrec" script on any answered port.  Also review the
	etc/umd.conf file.

	You will need PIKA_DIR set to /usr/pika and PIKA_REGISTRY set
	to the Pika config file you are using.

Install and run...

use:	make install
	/usr/sbin/umd

	The umd script will start umd_pika.  If the prior test fails
	it may be because there is no PIKA_DIR or PIKA_REGISTRY set.
	The umd script will make sure these are set to rational
	defaults before starting umd_pika.