In addition to the demonstration programs presented in Section 13.2, Demonstration Programs, CT Access also provides the following utilities:

Utility	Description
ctaparm	Displays system parameter defaults if using the CT Access daemon.
ctavers	Verifies CT Access installation and displays the version information for CT Access components.
ctdaemon	Allows you to modify system global default parameters, set the global tracemask, and optionally, log trace messages to a file.
mkprompt	Creates a prompt rules table.
swish	A tool for interactive or text file driven control of MVIP switches. It provides a convenient way to manually try out connections during development to verify the commands that will be given to switches from within CT Access applications that use the Switching service.
testpmpt	Tests a prompt rules table.
voxinfo	Displays information about a VOX file.

ctaparm

Displays selected parameter definitions and values stored in shared memory from ctdaemon. Refer to Section 3.5, Managing Parameters for more information.

ctaparm [options]

where the options are:

Option	Description
-e	Displays the names of all parameter structures.
-s structnames	Displays all parameters in listed structures.
-f fieldnames	Displays all parameters matching listed field names.
-g	Generates a parameter file from the current values.
-l cfgfile	Configuration file defining services to initialize.

ctaparm reads parameters stored in system shared memory and displays them on the screen. Specify which parameter to retrieve on the command line.

To run ctaparm:

• Enter the following at the prompt:

ctaparm [-e -s structlist -f fieldlist -g]

To display the parameter structure names, use the -e option. The structure names displayed on the screen can then be used with the -s option to display all parameters for a given structure.

The lists generated by the -s and -f options are delimited by the `+' (plus) character. For example:

ctaparm -s adi.play+adi.record
ctaparm -f gain+dtmfabort

If the CT Access daemon is running, the parameters displayed are those resident in system shared memory; otherwise, they are the compile-time defaults.

ctavers

Verify CT Access installation and display version information for CT Access components. Refer to Section 3.7, Verifying Compatibility for more information.

ctavers

ctavers calls ctaInitialize with the services and service managers specified in the cta.cfg configuration file. (Refer to Section 13.3.3, CT Access Daemon: ctdaemon.) It then retrieves and displays the version information of all services and service managers that were registered during CT Access initialization. The version information for the CT Access dispatcher (cta.dll) is also displayed.

Call ctavers.exe from the command line or the icon in the CT Access folder. Ensure that CTA_DPATH includes the directory where the cta.cfg file can be found. The default file is located in the \nms\ctaccess\cfg directory.

ctdaemon

Allows developers to modify system global default parameters, set the global tracemask, and optionally log trace messages to a file. Refer to Section 3.5, Managing Parameters and to Section 3.6, CT Access Error Codes for more information.

ctdaemon [options]

-f filename Specifies an ASCII file containing statements for defining services and service managers and overriding default parameters. Usually this will be cta.cfg.

ctdaemon reads the configuration file specified on the command line or finds cta.cfg in CTA_DPATH which was set during installation. This file specifies, in the [ctasys] section, the services and service managers that are to be passed to the call to ctaInitialize by the daemon. Once the services have been registered with CT Access by ctaInitialize, their compile-time parameter values are placed in shared memory and can be modified by the daemon. After initializing services, ctdaemon reads the [ctapar] section of the configuration file and writes new parameter values into shared memory.

Any processes that use "system global" default parameters will retrieve default parameter values from shared memory instead of compile-time "process global" defaults from the process data area.

Applications must set the parmflags field of the CTA_INIT_PARMS structure passed to ctaInitialize to CTA_PARM_MGMT_SHARED to specify that they want to use the "system global" default parameters maintained by ctdaemon. The daemon can be used in interactive mode to retrieve and modify global default parameter values.
Type `s <parmname> = <value>' or `g <parmname>' to modify or retrieve the current default values.

To generate a list of parameters that can be used in the [ctapar] section of the configuration file, use the utility ctaparm. Refer to Section 13.3.1, CT Access Parameter Display: ctaparm. Selectively edit the parameters that should have different default values and place them in cta.cfg.

The ctdaemon also holds a shared memory segment for tracing. To enable tracing from applications, the daemon must be running and the traceflags field of the CTA_INIT_PARMS structure passed to ctaInitialize must be set to CTA_TRACE_ENABLE. To start displaying trace messages, type `t' on the daemon command line. Trace messages will only be displayed if the tracemask corresponding to the specific type of message is enabled. The daemon can set the global tracemask by using the `m <tracemask>' command from the daemon command line. This will set the tracemask in all processes that have enabled tracing via ctaInitialize. To be more selective in tracing, use ctaSetTraceLevel within the application itself, to set the tracemask for a specific context within a specific process.

ctdaemon can also write the trace messages to a log file. The `TraceFile' keyword in "cta.cfg" specifies the name of the trace file. Trace messages will be appended to the log file each time the daemon is started. It is up to the user to delete or archive this file as necessary.

Note: It is not possible to use ctdaemon and addaemon at the same time. ctdaemon manages parameters for the ADI Service in CT Access so this should not be a problem.

mkprompt

Creates a prompt rules table. Refer to Section 5.2.7, Prompt Builder for more information. Refer to Appendix C for information on adding or changing prompt rules.

mkprompt source[.ptx] [dest[.tbl]]

source[.ptx] - is the source text file to be compiled. If no extension is specified, .ptx is assumed.

[dest[.tbl]] - is an optional output file name. If no output file is specified, the source file name will be used with the .tbl extension. If no extension is specified, .tbl is assumed.

mkprompt compiles prompt rule source files (.ptx) into prompt rule tables (.tbl).

The .tbl file is created only if there are no errors during the compile. If there are errors, they are reported with the line number where the error occurred.

  mkprompt american

  SWISH       

  testpmpt american

Tests the prompt rules in american.tbl.

13.3.7 VOX File Information: voxinfo

Name

voxinfo

Purpose

Display information about a VOX file. Refer to Chapter 5 for more information about the Voice Message service. Refer to Appendix B for more information about the VOX file format.

Usage

voxinfo filename

Description

Displays information about a specified NMS VOX file, including the header fields and details about each message.

The unit of size in VOX files is the `frame'. A frame represents 20ms when speech is encoded with one of the Natural MicroSystems voice encodings, and 10 ms for other encodings.

Example

c:>voxinfo myprompt
NMS Voice File Information Utility   CT Access Version 1.00   Nov 7 1996         Copyright (c) 1996 Natural MicroSystems Corp.  All Rights Reserved.
File:                       MYPROMPT
Compression rate:               2   (NMS-24)
Maximum number of indices:     48
Number of active indices:       4
Number of freed indices:        0
Number of indices in use:       4
Number of available indices:         44
Highest message number:          3
Total number of frames:       228   (5 seconds)
Total number of bytes:      14648
Number of active messages:      3
        --------------------ACTIVE INDICES---------------------         Idx#  Msg#    Frames       Bytes      Start byte  End byte
0     0        0x3b       0xe4a      0x200       - 0x1049
1     1        0x40       0xf80      0x104a      - 0x1fc9
2     2        0x38       0xd90      0x1fca      - 0x2d59
3     3        0x31       0xbde      0x2d5a      - 0x3937
        -------------MESSAGE INFORMATION----------------
Msg#  Seconds   Index Cnt   Frame Cnt   Byte Cnt
1        1.2       1           64          3968
2        1.1       1           56          3472
3        0.9       1           49          3038

---

(Page 4 of 4 in this chapter)

---

Tech_Support@nmss.com

Copyright © 1996, Natural MicroSystems, Inc. All rights reserved.