|
|
|
|
|
Service registration files are read by the iraAddADChannel and iraAddADDnisani functions and stored in an AD_APPL structure when an application is added to the AD tables. The information contained in the service registration files is used as arguments to the irExec or irSubProg functions when the application is started. The AD_APPL definition is:
typedef struct ad_appl {
char service[IRD_SERVICE_NAME_LEN]; /* name of the service */
char process[IRD_PROCESS_NAME_LEN];/* name of the process */
char register_file[IRD_MAX_FILE_LEN]; /* name of the registration file */
int type; /* type of application */
unsigned long attributes; /* attributes of application */
time_t modtime; /* modification time of registration file */
AD_APPL;
IRAPI application developers must create the service registration files for their applications and deliver the service registration files along with the application files. Service registration files are created by using the defService command.
The defService(1IRAPI) command is used by IRAPI application developers to create the service registration file for an IRAPI service. The service registration file is required to assign or delete a service to/from a channel or DNIS and/or ANI. For TSM scripts, the output of the TAS command serves as the service registration file for the script.
If it is successful, defService creates the service registration file /vs/trans/ service.T. If the command is called without options, defService prompts for all the necessary information. For example, to create the service registration file for the chantest service, enter:
defService -n -p chantest -t P chantest
