Nortel CTI ToolKit, User Manual

Page: 58 / 108

PeriProducer CTI Toolkit User’s Guide for M1
Page 58 Nortel Networks Confidential # P0606089 Ver: 1.1
CTI Initialize
Device Parameter Data
Register Device
App. # Example Application Name, Location, Function, and Usage
CI-1
/samples/SCCS-integrate/tapi_da_ivr_agent.ppr
1. In container Library.GetCTIRes, the CTI.ResourceStatus.CTIIsOk tells the CTI Init block
that the calling application wants to get the CTI resource.
2. In the container Startup.Inits. Check immediately following the call to the CTI Init block,
the value CTI.status is checked to see if it is 0 and the value CTI.ResourceStatus.CTIIsOk
is checked to see if it is true. If both conditions are met, then the code proceeds,
otherwise it exits the application.
3. Later, after the application concludes, it’s work in the Wrapup container, the resource is
freed and the Library.GetCTIRes is called again before the application starts at the
Answer block again to wait for a new call.
4. Note that this application uses a Resource block in the Wrapup container to free the CTI
resource, since the application requires that the resource is freed after every cycle.
CI-2
/samples/SCCS-integrate/acdagentwithcalldata.ppr
1. In the container, Initiate, the CTI Init block is called to set the condition handling.
2. In the container, Initiate.GetCTI, the application uses the Resource block to get the CTI
resource on it’s own, without help from the CTI Init block.
3. Note that this application allows the termination of the application to automatically free the
CTI resource.
App. # Example Application Name, Location, Function, and Usage
DP-1
/samples/CS-AD/Nortel-iccm/GetACDGroupStatus.ppr
1. CTI init; config file read; but not used except for logging purposes
2. CTI resource gotten
3. A hard coded DN is used to get ACDGroupStatus information
4. The CTI.EventData.paramname and the CTI.EventData.paramvalue are ignored while
the CTI.EventData.tlinkdata.datakey() and CTI.EventData.tlinkdata.datavalue() arrays are
logged.
DP-2
/samples/CS-AD/testrequestdeviceparams.ppr
1. Error trapping is set up, cti resource is obtained and this device is registered.
2. A loop is started that sends each type of Param Name to cti for the same Device Number.
3. The loop exits and the cti resource is freed as the application terminates. Note that at the
end of an IVR application’s execution, the cti resource is freed automatically.
App. # Example Application Name, Location, Function, and Usage
RD-1
/samples/CS-AD/testrequestdeviceparams.ppr
1. Error trapping is set up, cti resource is obtained and this device is registered.
2. A loop is started that sends each type of Param Name to cti for the same Device Number.
3. The loop exits and the cti resource is freed as the application terminates. Note that at the
end of an IVR application’s execution, the cti resource is freed automatically.