Running nccxfer

nccxfer demonstrates rerouting an incoming call.

Usage

nccxfer [options]

where options are:

Option

Description

-A xxxmgr

Specifies the NaturalAccess manager to use for the ADI API. Default is ADIMGR.

-b n

Specifies the board number n. Default is 0.

-s n:m

Specifies the MVIP stream and timeslot for the first channel. Default is 0:0.

-p protocol

Specifies the protocol to run. Default is lps0.

-i n

Specifies the number of call iterations (0=infinite).

-m n

Specifies the method of transfer. Valid values for n:

Value	Description
1	Transfer on PROCEEDING (after dial) (default)
2	Transfer on ALERTING (ringing)
3	Transfer on CONNECTED (first voice or signal)
4	Manual (call screening)

Featured functions

nccAutomaticTransfer, nccTransferCall

Description

Party A calls party B (which is the demonstration program) and requests a transfer to party C. nccxfer (party B) then calls party C. It reports success or failure at one of several stages, depending on the selected transfer method. If -m 4 is specified on the command line, nccxfer asks party C whether it should complete the transfer, or report failure.

Procedure

Begin with three telephone lines: two (A and C) with two 2500-type telephone sets, and one (B) connected to the board. Lines B and C must be connected to a common PBX.

Complete the following steps to run nccxfer:

Step	Action
1	Specify the proper board and MVIP stream, and start the configuration utility.
2	Start nccxfer by entering the following at the prompt: nccxfer [ -b n -s n:m -p protocol -i n -m n ] Make sure to specify a transfer method.
3	From line A, call line B. The demonstration answers.
4	When the program requests an extension to try, dial the extension of line C. The demonstration calls line C.
5	Answer line C.

With transfer method 4, the demonstration offers you a chance to refuse the call. The other transfer modes report success or failure at earlier stages, sometimes before the transfer is actually completed.