Copyright: Copyright 1999 Dialogic, an Intel company


Help Contents
Contents

About this guide

1.  CT Media - The Administrator's View

2.  Installing CT Media

3.  Starting and Stopping the Server

4.  Working with Resource Hardware and Software

5.  Installing and Running Applications

6.  Controlling Call Routing

7.  Interpreting Application Profiles

8.  Diagnostics

Appendix A - Example Profiles

Appendix B - Stand-Alone Self Hosted Systems

Appendix C - The CT Server Administration Application User Interface

Appendix D - The Generic Profile Editor

Appendix E - The Container Manager User Interface

Appendix F - The Server Start Stop Utility User Interface

Appendix G - CT Media Event Viewer User Interface

Appendix H - Troubleshooting

Legal Information


About this guide

This Guide is for...

This Guide Tells You...

Other CT Media Documents


1.  CT Media - The Administrator's View

1.1.  A Brief Introduction to CT Media

1.2.  Applications Supplied With CT Media

1.3.  Managed Server Components

1.4.  The Administrator's Toolkit


2.  Installing CT Media

2.1.  Running the CT Media Installation Application

2.2.  The Default Server Configuration

2.3.  Verifying the Installation of the CT Server

2.4.  Viewing Documentation

2.5.  Uninstalling CT Media


3.  Starting and Stopping the Server

3.1.  Starting the Server

3.2.  Stopping the Server

3.3.  Levels of the Server


4.  Working with Resource Hardware and Software

4.1. Overview

4.2.  Installing Resource Hardware and Software

4.3.  Checking Board Installation

4.4.  Starting Boards

4.5.  Stopping Boards

4.6.  Removing Boards

4.7.  Replacing Boards

4.8.  Uninstalling Boards

4.9.  Working With the Simulated D/41E


5.  Installing and Running Applications

5.1.  Application Overview

5.2.  Installing Applications

5.3.  Checking Application Profile Installation

5.4.  Routing Calls To and From a New Application

5.5.  Starting Applications

5.6.  Stopping Applications

5.7.  Uninstalling Applications


6.  Controlling Call Routing

6.1.  Using Profiles to Control Call Routing

6.2.  Handing Off Calls Between Applications

6.3.  Inbound Call Routing

6.4.  Outbound Call Routing

6.5.  The Device Name

6.6.  Modifying Profiles


7.  Interpreting Application Profiles

7.1.  Examining Application Profiles

7.2.  The Structure of an Application Profile


8.  Diagnostics

8.1.  Error and Event Logging

8.2.  System Snapshot Utility

8.3.  Statistics

8.4.  Available Statistics

8.5.  Using Statistics - Monitoring Scenarios

8.6.  Tuning Timeouts for CT Media Services

8.7.  Processor Affinity


Appendix A - Example Profiles

ASI Map Profile

Routing Rules Profile

AutoAttendant Profile

FaxBack Profile

Operator Profile


Appendix B - Stand-Alone Self Hosted Systems

Introduction

Installing a Loopback Driver


Appendix C - The CT Server Administration Application User Interface

How the CT Server Administration Application Works

Making and Breaking the Admin/Server Application Link

Client/Server Link Configuration

Configuring the Server for Multinode

View Options

Working With Profiles

Checking a Profile

Accessing the Profile Checker

Managing CT Media Services


Appendix D - The Generic Profile Editor

Introduction

Starting the Generic Profile Editor

Editing a Profile

Saving a Profile


Appendix E - The Container Manager User Interface

Introduction

Using the Container Manager

Creating a new Container

Data Objects

Container Backup and Restore

View Options


Appendix F - The Server Start Stop Utility User Interface

How The Server Start Stop Utility Works

Starting Up the CT Server

Shutting Down the CT Server


Appendix G - CT Media Event Viewer User Interface

About the CT Media Event Viewer

Starting the Event Viewer

Event Information

Filtering Events

Changing Event Log Settings


Appendix H - Troubleshooting

Puzzling Symptoms - Possible Causes


Legal Information

Copyright notice

Trademarks


This Guide is for...

This guide is intended for CT Media administrators. It is the responsibility of the Server administrator to:

•	Install CT Media

•	Install and maintain

•	the CT Server

•	a System Call Router

•	signal processing and telephony boards and associated software

•	client applications

•	Configure the Server to

•	handle inbound and outbound telephone calls

•	transfer calls appropriately between applications when required


This Guide Tells You...

This guide will tell you how to manage CT Media by:

•	installing and uninstalling the CT Server

•	starting and stopping the CT Server

•	installing, replacing, and removing signal processing and computer telephony boards and associated software

•	installing and running applications

•	installing and running a System Call Router

•	specifying how inbound and outbound calls are routed within the CT Server

•	writing your own custom administration utility applications

•	helping you to identify common problems


Other CT Media Documents

The documentation set supplied with CT Media also includes

•	CT Media QuickStart

•	CT Media Application Developer's Guide for Windows NT

•	CT Media API Reference for Windows NT, Volumes 1 and 2

•	CT Media Resource Configuration Guide for Windows NT

•	CT Media Resource Reference for Windows NT


1.1.  A Brief Introduction to CT Media

The Dialogic Computer Telephony Media (CT Media) product consists of the CT Server and its associated Software Development Kit.  CT Media enables the development of computer telephony applications and core signal processing technologies, such as speech recognition and audio compression, in an object oriented, client-server environment.  Furthermore, the Server architecture allows systems integrators to readily assemble run time systems that use applications and core technologies from different vendors.

The CT Server simplifies application development by hiding low level resource and call management tasks from the client application and by providing a uniform interface to core technologies, independent of their implementation. The Server achieves this by allowing client applications access to Server resident components that provide specialist call processing services. These services include:

•	call routing using the System Call Router (SCR) and the SCR routing rules

•	Server configuration management using application profiles

•	data storage management

•	core technology resource management

•	a Server wide messaging service

Figure 1.  The Components of a CT Server Based Call Processing System

The CT Server complies with the ECTF S.100 Revision 1.0 specification, and supports S.100 compliant application programming interfaces (APIs) including, but not limited to, the following Server components:

•	Session

•	System Call Router

•	Logical Connection Management

•	Container Management

•	Automatic Speech Recognition

•	Player/Recorder

•	Tone Generation/Detection.

More:


Figure 1.  The Components of a CT Server Based Call Processing System


1.2.  Applications Supplied With CT Media

CT Media provides a number of utility and demonstration applications which are available in Dialogic CT Media Applications. These applications are briefly described in Table 1:  CT Media Applications.

Table 1:  CT Media Applications

More:


Table 1:  CT Media Applications

AnswerDemo	Simple telephone answering machine demo
Container Manager	GUI application for managing CT Media Containers
ConnSrve	Utility for editing Server connections This is only installed with the Client Runtime
CT Server Administration	GUI application for administering the CT Server, Profiles, Services, etc.
CT Sim	Simulation utility for CT Media API testing.  Used as interface to the simulated Resources.
Server Start Stop Utility	GUI application for starting up and shutting down the CT Server
Uninstall Server	Uninstallation for CT Media
WinVote demo	Graphical voting demo


1.3.  Managed Server Components

The components of the CT Server that the Server Administrator will have to work with are:

•	CT Media Services. These are collections of Service Providers with a common interface which provide the functionality of the Server. Some CT Media Services must be present if the Server is to start correctly. These are referred to as Mandatory Services, and are installed during the Server installation. Other Service Providers are Optional, and may be added or removed from the Server to modify its functionality. Vendor-supplied Service Provider packages (i.e., one or more Service Providers that must be installed and run together) are also referred to as optional CT Media Services.

•	Typically, CT Media Services are Service Providers which support telephony or signal processing boards, however there are software-only CT Media Services.

The Server Administrator will have to install, start, stop and uninstall CT Media Services.

•	Profiles. These are configuration files. Profiles are associated with boards (telephony or signal processing hardware and software) and with applications. The System Call Router application uses two important profiles - one which contains application configuration information and one which describes the routing of inbound and outbound calls, and the transfer of calls between applications running on the Server.

The Server Administrator will have to add, remove, import, export, and modify profiles.


1.4.  The Administrator's Toolkit

CT Media provides the CT Server Administrator with a number of utility applications for monitoring and configuring the Server. These utilities may be found in Dialogic CT Media Applications and include:

More:

1.4.1.  The CT Server Administration Application

1.4.2.  ConnSrve - Server Connection Management

1.4.3.  CT Sim - The Resource Simulator and Client Shell

1.4.4.  Server Start Stop - The Startup/Shutdown Utility

1.4.5.  The Container Manager

1.4.6.  The Uninstall Utility

1.4.7.  The Simulated D/41E Package


1.4.1.  The CT Server Administration Application

The CT Server Administration Application is a Windows NT application which may be run either on the same machine that hosts the CT Server (self hosted) or on a remote machine. The CT Server Administration Application allows the Administrator to:

•	view the status of various Server components

•	install and run CT Media Services

•	create, modify and install profiles

For a description of the CT Server Administration Application user interface see Appendix C - The CT Server Administration Application User Interface.


1.4.2.  ConnSrve - Server Connection Management

This utility allows a Client Runtime installation (which does not include the Administration Application) to create and maintain Server connections.


1.4.3.  CT Sim - The Resource Simulator and Client Shell

CT Sim is a Windows NT application which runs on the same machine that hosts the CT Server. CT Sim allows the user to:

•	simulate signal processing and telephony hardware and software

•	interactively emulate an application

•	create scripts to simulate hardware and emulate software

For a description of how to use CT Sim refer to the Other CT Media Documents.


1.4.4.  Server Start Stop - The Startup/Shutdown Utility

Server Start Stop is a Windows NT applet which runs on the same machine that hosts the CT Server. Stop/Go allows the Administrator to:

•	start the CT Server

•	stop the CT Server

For a description of the Stop/Go user interface see Appendix F - The Server Start Stop Utility User Interface.


1.4.5.  The Container Manager

The Container Manager allows manipulation of Containers and Data Objects, similar to the Container API functions, through a GUI interface.

For a description of the Container Manager user interface see Appendix E - The Container Manager User Interface.


1.4.6.  The Uninstall Utility

The Uninstall utility is a Windows NT applet that runs on the same machine that hosts the CT Server.

NOTE:	You cannot uninstall resource packages (e.g. D41E-SC) after uninstalling CT Media.  CT Media must be present in order to uninstall these packages.

To uninstall the CT Server

1.	Stop all CT Media applications.

2.	Use the Uninstall application to remove all the CT system files from the server.


1.4.7.  The Simulated D/41E Package

CT Media provides software for simulating D/41E boards. The Dialogic D/41E is a voice processing board with four analog loop-start channels.

This software is automatically installed when CT Media is installed, and allows the System Call Router (SCR) to start without the need for physical line interface devices to be installed in the Server.

The default setting of the software and profiles simulates one D41E board but by changing the profiles you can simulate as many channels as you need.


2.1.  Running the CT Media Installation Application

2.1.1.  What You Need to Install CT Media

2.1.2.  How to Install CT Media

2.1.3.  Instructions

2.1.4.  If the Installation Does Not Complete...

2.1.5.  Different Installation Choices

2.1.6.  Multinode Installation

2.1.7.  KVSet Versions


2.1.1.  What You Need to Install CT Media

You will need:

•	Microsoft's Windows NT operating system, version 4.0 or later, installed as network-capable; i.e., NT with

1.	a network interface card and

2.	TCP/IP protocol stack

NOTE:	If the host machine is not connected to a network a "loopback" driver will have to be installed before CT Media is installed. See Appendix B - Stand-Alone Self Hosted Systems for details.

Suggested hardware requirements are:

•	a Pentium 200 (minimum 133) processor

•	64 Mb (32 minimum) of RAM

NOTE:	CT Media may work with lower hardware configurations, but this is unsupported.

The installation program will check that you have sufficient available hard disk space to install.


2.1.2.  How to Install CT Media

IMPORTANT

You must have Administrator privileges to install CT Media.

HINT:	Having active applications running in the background during installation of the Server may cause the installation to fail. The user should ensure that all other applications are stopped for the period of installation.


2.1.3.  Instructions

NOTE:	If you are installing over CT Media 1.0 or 1.1, this will upgrade CT Media.  Note that if you also have the 1.0 or 1.1 versions of the CT Media Resources installed, you must first uninstall the CT Media Resources before the CT Media upgrade can happen.

1.	Put the CT Media installation CD-ROM into the CD-ROM drive and click on the CD-ROM drive in Explorer.

2.	Run setup.exe.

3.	Follow the instructions in the installation program, for a single-node installation.  Further instructions for multinode installations can be found in Section 2.1.6.  Multinode Installation.

The installation will create "Dialogic CT Media Applications".

NOTE:	The CT Media installation will leave files in your designated \temp directory.  These files can be deleted if you wish.


2.1.4.  If the Installation Does Not Complete...

•	Make sure you have Administrator privileges and access rights to the installation directory

•	Make sure you have sufficient disk space

NOTE:	The installation program will not be able to set itself up if you do not have at least 2.8 M of memory available in your specified \temp directory, and the installation will fail ungracefully.

•	Make sure you are running a supported version of Windows NT.

If the install terminates abnormally, run the uninstal.exe program. before trying to install again.


2.1.5.  Different Installation Choices

During installation, you will have seen that different components are installed depending upon your choices.  This is also reflected in different applications in CT Media Applications for each installation choice

Application Developer	Server Runtime
• Documents (Admin, Application SDK, and Container Developer) • AnswerDemo • Container Manager • CT Server Administration • CT Sim • Event Viewer • Server Start Stop Utility • Uninstall CTMedia • WinVote demo	• Documents (Administration) • Container Manager • CT Server Administration • CT Sim • Server Start Stop Utility • Uninstall CTMedia
Client Node/Resource Node	Administrator
• Documents (QuickStart; optional for Client) • ConnSrve Utility (see help file for usage) • Uninstall CTMedia	• Documents (Administration) • Container Manager • CT Server Administration • Uninstall CTMedia
Custom
• As specified by expert user
CAUTION

The behavior of CT Media is undefined if any installed files or directories are changed using methods other than those provided by the CT Media product.


2.1.6.  Multinode Installation

CT Media includes the option for multinode installation (i.e., the CT Media Server runs on one machine while CT Media Services accessible by that server run on a remote machine).  For this release, a multinode setup will include one Server and one remote Resource Node only.

More:

Set up NT Service Account

Installation onto Server Machine

Installation onto Resource Machine


Set up NT Service Account

In order to run CT Media in a multinode configuration under NT, the Server and Resource Nodes must use specially-configured NT user accounts; either:

1.	one global user account with a password that will not expire and cannot be changed by a user

NOTE:	An NT Administrator with Account Manager privileges will set up this account.  Full details are not provided for setting up this user account, since these will depend on the particular network.

2	or one local NT account on each of the Server and Resource machines, all with the same name and password

Privileges may then be assigned to this Service Account as required for security purposes on the network.


Installation onto Server Machine

1.	On the machine which is to be the Server, using the User Manager, give the Service Account:

a)	Administrator privileges (add the account to the Administrator Group)

b)	The advanced user right to "log on as a Service" to the Server machine.

2.	Install CT Media according to the instructions in Section 2.1.3.  Instructions.  You should choose the Server Runtime setup option.

3.	Once the installation has completed, configure the CT Media Server for multinode operation.

•	Stop the CT Server.  Click the Start button, choose Programs | Dialogic CT Media Applications | Server Start Stop, and use this utility to stop the Server.  See Appendix F - The Server Start Stop Utility User Interface for further description of this utility.

•	Click the Start button, choose Programs | Dialogic CT Media Applications |  CT Server Administration

•	From the Server menu, choose Configure for multinode.  The following dialog box will appear:

Field	Description
Account	Enter the domain and name of the Service Account you set up in the previous section.
Password	Enter the password for that account
Container Path	Enter the UNC path where Containers will be located.   • This should be \\ResourceComputer\CTServer\server\cont.  You cannot browse for this directory, since the Resource Machine does not yet have CT Media installed.
4.	Share the CTServer directory (e.g., Machine\CTServer)

•	In Explorer, right-click on the CTServer directory.  Choose Sharing…

•	Click on the Shared As... radio button.  Do not make any other changes.

•	Click OK.


Installation onto Resource Machine

1.	On the machine which will run remote Services, using the User Manager, give the Service Account:

a)	Administrator privileges (add the account to the Administrator Group)

b)	The advanced user right to "log on as a Service" to the Resource machine.

2.	Install CT Media according to the instructions in Section 2.1.3.  Instructions.  You should choose the Resource Node setup option.  During the installation, you must supply the following information (specific to the multinode setup):

•	The location of the Server, which will be the name of the computer you have just installed the Server on.

•	The domain and user name of the Service Account, and the password.

3.	Share the CTServer directory ( e.g., Machine\CTServer) on the Resource Node.

•	In Explorer, right-click on the CTServer directory.  Choose Sharing…

•	Click on the Shared As... radio button.  Do not make any other changes.

•	Click OK.

4.	Reboot the Resource Node machine.  This will ensure the CT Server Service is started correctly.

5.	Start the CT Server on the Server Node machine using the Server Start Stop utility.

CAUTION

The Resource Node installation does not include the simulated D/41E Resource and CT Sim.  To install these, you must copy files from the Server machine onto the Resource machine:

1	Change the Server Level to 1 using the CT Server Administration application (see Changing the Server Level for instructions)

2.	Create a new folder on \\ResourceMachine\CTServer\Server\Services.

3.	Copy \\ServerMachine\CTServer\Server\Services\CTSim into the new Services folder on the Resource Node.

4.	Copy \\ServerMachine\CTServer\Server\bin\reskit.dll to \\ResourceMachine\CTServer\Server\Services\CTSim.

5.	From the Server Machine, using the CT Server Administration Application, from the View menu, choose CT Media Services.  Double-click on the DLGC_SimD4x service

•	Change Command Line to point to the full path for the CT Sim executable (e.g., C:\CTServer\Server\Services\CTSim\simd4x.exe)

•	Change Computer Name to "ResourceMachine"

•	Click OK.

6.	Change the Server Level to 5.


2.1.7.  KVSet Versions

All the runtime installation options will install the release version of KVSets.

The Application Developer installation option will default to the debug version of KVSets, which is slower but gives an application developer useful KVSet runtime debugging capabilities.

If a Developer subsequently needs to use the release version of KVSets, an administrator should:

1.	Run Control Panel

2.	Run System

3.	Change the System PATH variable from …\client\sdk\bin to …\server\bin

NOTE:	If you change between the release and debug versions of KVSets, remember that you can only run applications that have been built with the appropriate KVSet versions.  E.g., if you have an application that was built using the debug version, you must rebuild it if you want to run the application with the release version.


2.2.  The Default Server Configuration

2.2.1.  The Default Server Name

2.2.2.  The Default CT Server


2.2.1.  The Default Server Name

During the installation procedure the installation application will automatically determine the name of the CT Server host machine. This will become the default server for locally hosted (self hosted) clients, and may be identified by the name "Default_Server" during session creation.

For example, if CT Media is being installed on a machine called "Kea"then the installation procedure will create an entry in the Windows NT Registry with an item name:

Default_Server

and a value

tcp:Kea:2020

Where:

tcp	indicates that the supported communication protocol is TCP/IP. This is the only communication protocol supported by CT Media.
2020	is the default port used by the CT Server for administration Sessions
You can view and modify these Registry entries through the Administration Application.  See Client/Server Link Configuration for details.


2.2.2.  The Default CT Server

When the CT Server is installed and started, it establishes several different links and creates several different building blocks. These are shown in Figure 2.  CT Server Overview.

NOTE:	The default Server installation includes a simulated Dialogic D/41E package. This simulated board is drawn with a dotted outline in Figure 2.  CT Server Overview.

Figure 2.  CT Server Overview


Figure 2.  CT Server Overview


2.3.  Verifying the Installation of the CT Server

The existence and status upon startup of the key Server components can be examined using the CT Server Administration Application, which is provided by Dialogic as part of CT Media. The CT Server Administration Application is installed on the Server host machine when the Server software is installed.

If you have chosen to install the CT Server, it should be running from the CT Media installation procedure.  Perform the following steps to verify that the CT Server has been successfully installed.

NOTE:	These steps can also be used to verify an Administrator installation of CT Media, by connecting to a remote CT Server as described.

More:

2.3.1.  Start The CT Server Administration Application

2.3.2.  Log On to the Server

2.3.3.  Check the Installed Profiles

2.3.4.  Check the CT Media Services

2.3.5.  Check the Service Providers


2.3.1.  Start The CT Server Administration Application

on the Server host machine:

1.	Click on the Start button

2.	Choose Programs | Dialogic CT Media Applications | CT Server Administration


2.3.2.  Log On to the Server

NOTE:	If you have installed the Administrator option for CT Media, then there will be no Server to connect to.

1.	From the Client menu, choose Edit Server Entries…

2.	Define a Server Entry for the remote CT Server that will be administered as described in Client/Server Link Configuration.

For a locally-hosted CT Server installation, or once you have defined a Server Entry for a remote CT Server, connect to the CT Server using the following steps:

1.	Click on the Connect icon in the CT Server Administration Application toolbar or choose Server | Connect to Server....

2.	Choose the Server to administer (Default_Server, or the name of a different  Server you want to administer).

3.	Select "OK".

The host machine is automatically registered as the default CT Server during system installation.


2.3.3.  Check the Installed Profiles

Select View|Profiles from the CT Server Administration Application menu. The following Profiles, at least, should be listed:

Figure 3.  Installed Profiles

Table 2.  Description of Installed Profiles


Figure 3.  Installed Profiles


Table 2.  Description of Installed Profiles

Profile Name	Description
SampleProfile	AnswerDemo Application Profile - Configuration information for AnswerDemo demonstration application
SCR_AppProfile	System Call Router Application Profile - Configuration information for the SCR
WinVoteProfile	WinVote Application Profile - Configuration information for WinVote demonstration application
SCR_ASIMap	ASI Map Profile - Configuration information for transferring calls between applications
SimD41	SimD41 Resource Profile - Configuration information for the simulated Resource package
SCR_RoutingRules	Routing Rules Profile - Configuration information for routing telephone calls to and from line interfaces


2.3.4.  Check the CT Media Services

Select View|CT Media Services from the CT Server Administration Application menu.

Figure 4.  Installed CT Media Services

Table 3.  Description of Installed Services


Figure 4.  Installed CT Media Services


Table 3.  Description of Installed Services

Service Name	Description
DLGC_CoreService DLGC_ISE	Dialogic CT Media Services - These will be running if the CT Server is at Level 2 or above.
DLGC_SimD4x	Simulated Resource package - This simulates a single D/41ESC board.


2.3.5.  Check the Service Providers

Use the CT Server Administration Application to see which Core Service Providers are available.

NOTE:	In addition to installing Core Service Providers, the CT Media installation application will also install a simulated D/41E package. The Service Providers implemented by this package are also shown in Figure 5.  Service Providers.

Select View|Service Providers.

Figure 5.  Service Providers

Some SPs are internal only and will be listed as Not Available (i.e., not able to be allocated to a Group by RAS).  This does not mean that CT Media is malfunctioning.

Table 4.  Description of Installed Service Providers


Figure 5.  Service Providers


Table 4.  Description of Installed Service Providers

SP Name	Description
NIS[...]	For internal CT Media use
dxxxBnCm	Channel Service Providers - Simulated D/41E channel SPs
DLGC_SimD4x	Vendor process Service Provider - D/41E package parent SP
ISE[1,3,2] DLGC_ISE	Intelligent Switch Extension - works in conjunction with SCR
ECTF_SessionManager	Session Manager - Authenticates users and creates Sessions
DLGC_SPRPackage	Switch Port Resources - this Resource package supplies Switch Port resources
ECTF_SCR	System Call Router - Controls telephone call routing and application interaction
ECTF_ContainerManager	Container Manager -Allows access to containers
ECTF_GroupFactory	Group Factory - Creates Groups as requested by Sessions
DLGC_SCBus_1	Switch Fabric Controller - Controls low level switch fabric manipulation
DLGC_LCM	Logical Connection Manager - Controls high level Resource interconnection
DLGC_RAS	Resource Allocation Service - Manages Services
DLGC_CoreService	Core Process SP - CT Server parent SP
DLGC_AdminSessionManager DLGC_AdminContainerManager DLGC_StatisticsMasterControl	Administration SPs - For Administration Sessions
ECTF_ConfigurationManager	Configuration Manager - Manages the profiles and services
DLGC_RootService	The Root SP -  the initial CT Media Service: not user configurable
DLGC_DLLEventSP DLGC_FacadeEventSP	Event SP - used to receive events from CT Media Services


2.4.  Viewing Documentation

Some of the CT Media documentation is available as help files, but the rest is in .pdf format.  If you install CT Media without Acrobat Reader and then find that you need it, you can:

1.	re-run setup.exe.  Make no changes to existing components and at the end of the install you will be given the opportunity to install the Acrobat Reader.

2.	run \CTServer\1.2\relfiles\ar32e30.exe.  This will install Acrobat Reader 3.0.

NOTE:	If you have already installed Dialogic Resources, you cannot use Option 1 and should use Option 2.


2.5.  Uninstalling CT Media

Before uninstalling CT Media, stop any applications running under CT Media.

2.5.1.  Standard Installation Uninstall

2.5.2.  Multinode Installation Uninstall


2.5.1.  Standard Installation Uninstall

To uninstall the CT Media Server package from a standalone machine

1.	Uninstall the Dialogic Resource Package first, if it is installed.

2.	Click on the Start button.

3.	Choose Programs | Dialogic CT Media Applications | Uninstall Server

CAUTION

Uninstalling CT Media will delete your containers, scripts, and profiles.  Ensure that these are all backed up beforehand if you wish to retain them for a future installation.

If you need to uninstall due to a failed install, run the uninstal.exe program.


2.5.2.  Multinode Installation Uninstall

1.	Uninstall the Dialogic Resource Package on the Resource Node, if it is installed.

2.	On the Resource Node, remove the Sharing from the CT Server directory.

3.	On the Resource Node, click on the Start button.  Choose Programs | Dialogic CT Media Applications | Uninstall Server and follow the prompts to uninstall.

4.	On the Server Node, remove the Sharing from the CT Server directory.

5.	On the Server Node, click on the Start button.  Choose Programs | Dialogic CT Media Applications | Uninstall Server and follow the prompts to uninstall.

NOTE:	If you do not remove the sharing from the CT Server directories, the CT Server directory will be deleted by the uninstall program, but the directory will still appear as shared on your network.  Also, a reinstallation of CT Media will result in a CT Server directory which is shared by default, instead of Not Shared by default.


3.1.  Starting the Server

3.1.1.  Standalone Installation Startup

3.1.2.  Multinode Installation Startup


3.1.1.  Standalone Installation Startup

To start the Server:

1.	The Server will be started automatically when Windows NT is booted.

2.	or if the Server has been halted but Windows NT is still running, then

•	Click the Start button

•	Choose Programs | Dialogic CT Media Applications | Server Start Stop, and use this utility to start the Server.  See Appendix F - The Server Start Stop Utility User Interface for a description of this utility.

3.	or, if the Server has been halted but Windows NT is still running, then

•	Click the Start button

•	Choose Settings | Control Panel, and double-click on the Services icon.

•	Select CTMS Server as the Service and then click on the Start button.


3.1.2.  Multinode Installation Startup

Section 3.1.1.  Standalone Installation Startup applies to starting the Server Node in a multinode installation.

Given a successful multinode installation, if both Server and Resource Nodes are shut down (either the machines are turned off, or the CTMS Server NT service is stopped on both machines), it does not matter which is started up first.

On bootup, the CTMS Server NT service will be started automatically for both the Server and Resource Node machines.  The CTMS Server NT service on the Resource Node will reach the Started state on bootup, even if it is still polling to find a Server because the Server Node is not yet started.

NOTE:	Upon a restart of the Server after a shutdown, the CTMS Server NT service on the Resource Node will not start automatically; you must manually restart it.

The multinode connection will be established once the Server on the Server Node reaches Level 1 and the Resource Node machine is started.  Once the Server reaches Level 3, the remote CT Media Services on the Resource Node will be started automatically.


3.2.  Stopping the Server

3.2.1.  Standalone Installation Shutdown

3.2.2.  Multinode Installation Shutdown


3.2.1.  Standalone Installation Shutdown

To stop the Server:

1.	Follow the vendor-supplied instructions to stop all applications.

2.	Use the "Server Start Stop" utility to stop the Server.

•	Click the Start button

•	Choose Programs | Dialogic CT Media Applications | Server Start Stop, and use this utility to stop the Server.  See Appendix F - The Server Start Stop Utility User Interface for a description of this utility.

3.	or

•	Click the Start button

•	Choose Settings | Control Panel, and double-click on the Services icon.

•	Select CTMS Server as the Service and then click on the Stop button.


3.2.2.  Multinode Installation Shutdown

Section 3.2.1.  Standalone Installation Shutdown applies to shutting down the Server Node in a multinode installation.

Shutting down the Server in a multinode installation will also cause the CTMS Server NT service on the Resource Node to shut down.  In a subsequent restart of the Server, you will also need to manually restart the CTMS Server NT service on the Resource Node

The CTMS Server NT service on the Resource Node can also be shut down using the method described in Step 3 in Section 3.2.1.  Standalone Installation Shutdown.  This will not affect the CTMS Server NT service on the Server Node.  This will stop any remote CT Media Services that are running on the Resource Node, and on the Server Node, the Services dialog in Control Panel will show that these Services have stopped.


3.3.  Levels of the Server

The CT Server has defined levels at which it functions.  The Server level can be changed using the Administration Application (see Changing the Server Level), or through the Administration API function CTadm_SetTargetServerLevel().  Changing Server Levels will start and stop CT Media Services as appropriate.

NOTE:	If you need to start and stop services in the Administration Application, it is recommended that you use the server level to do this.  You can use the Start and Stop Service functionality, but you may get unexpected behavior if you mix the two methods.

Level	Description
1	Configurable - Can change the profiles and move the CT Server to a higher level. NOTE: The Root Service provides all Level 1 functionality.
2	Mandatory Services Running - Mandatory Services will start when you move to Level 2. NOTE: The Mandatory Services are the Core Service, DLGC_CoreService, and the ISE Service, DLGC_ISE.
3	Optional Services Running - Optional Services will be started when you move to Level 3. The CT Server has moved to Level 3 when all Optional Services are in either the 'Failed' or 'Running' state.
4	Connections Enabled The CT Server can handle client connections (Sessions). NOTE: Depending on your hardware, inbound calls may also be possible at Level 4.  Generally, it is assumed that inbound calls will be possible at Level 5.
5	Calls Enabled The CT Server can handle inbound calls.
To change Server levels, use the Administration Application.  See Changing the Server Level.


4.1. Overview

Vendors who supply hardware for use with the CT Server should supply the CT Server Administrator with:

•	Hardware and appropriate internal and external connectors

•	Software

•	A Windows NT-style board-software installation and deinstallation application

•	Documentation that includes -

•	Installation instructions

•	Names of any CT Media Services (i.e., Service Provider packages) and Resource-specific profiles that will be installed

•	Names of any proprietary non-S.100 standard features that the board provides

•	The Call Control API used by any line interfaces the board may support


4.2.  Installing Resource Hardware and Software

Shut down the server. Follow the PC hardware vendor's instructions for turning off the server PC. Install the resource's boards and software according to the board vendor's instructions.

Restart the host machine and boot Windows NT. The CT Server will be started automatically when Windows NT is booted.

If the simulated D/41E package is currently installed and the newly installed boards support physical line interface devices, then the simulated D/41E CT Media Service should be disabled. See 4.9.2.  Removing the Simulated D/41E for details.


4.3.  Checking Board Installation

After a board has been installed and started, the name of the CT Media Service that the board's software package was installed under will appear in the CT Server Administration Application under one or more of any of the following component types:

•	CT Media Service

•	Profile

Table 5.  Viewing Vendor Boards in the Administration Application

The board vendor should provide a list of these components. Use the CT Server Administration Application to view them.

If the board vendor has supplied a diagnostic application for the board and its associated software, it is suggested that it be run at this point.

More:

4.3.1.  Checking the Installation of a CT Media Service

4.3.2.  Checking the Installation of Resource Profiles


Table 5.  Viewing Vendor Boards in the Administration Application

	is displayed in this view...
this installed component	Service Providers	CT Media Services	Profiles
Core Services	X	X
System Call Router	X	X	X
Vendor-supplied boards	X	X	X
Vendor-supplied applications			X
the Administrator can:	view only	add, remove, stop, start	add, remove, import, export, update


4.3.1.  Checking the Installation of a CT Media Service

To view CT Media Services on a CT Server select:

Menu	Quick key(s)	Toolbar
View|CT Media Services	F3	-
If the installation process has failed to add the new CT Media Service, the Administrator should add it manually.

1.	Change the Server Level to 1, using the Server | Change Server Level option.

2.	Then add the CT Media Service (see  Adding a CT Media Service).


4.3.2.  Checking the Installation of Resource Profiles

In addition to installing a vendor-supplied board's software and hardware components, the Administrator may also have to install a board's Resource Profile. These profiles may contain board configuration and other information necessary to ensure proper board operation.

To check if the Resource's profile has been added to the Server use the CT Server Administration Application and select:

View|Profiles

If the installation application provided by the vendor did not automatically add the necessary profiles, the Administrator should add them manually using the CT Server Administration Application.

NOTE:	Further details of Resource Profiles are included in the CT Media RDK Guide.

More:

Adding IEF Formatted Profiles

Adding Text Formatted Profiles


Adding IEF Formatted Profiles

If the profile is in Import/Export Format (*.ief):

Select:

Menu	Quick key(s)	Toolbar
Profile|Import	-
2.	Specify the file name of the profile (including the full path name) and the name it will have in the Server.


Adding Text Formatted Profiles

If the profile is an unparsed file in ASCII text format (*.prf):

1.	Start the appropriate Profile Editor by selecting:

Menu	Quick key(s)	Toolbar
Profile|New	Ctrl+P
Enter the type of profile to be edited in the dialog box.

2.	In the Profile Editor window, import the profile text by selecting:

Menu	Quick key(s)	Toolbar
Profile|Import from Text File...	-
Enter the name of the profile text file, and select "Open"

3.	In the Profile Editor window, store the imported profile on the Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store	Ctrl+S
Enter the name of the profile on the Server and select "OK".

4.	Close the Profile Editor.


4.4.  Starting Boards

If the vendor's resource installation routine has not already done so, use the CT Server Administration Application to start the services (software) associated with the board. The board vendor should provide you with a list of the services the board provides.

To start the CT Media Service for a board software package:

Change the Server Level to 5, using the Server | Change Server Level option (see Changing the Server Level).  (If the Server Level is already at 5 and the Services are not running, then change the Server Level to 1 first.)  This should start all installed Services that are not disabled.

You can use the Service | Start method to start Services, but it should not be necessary.  It is also not recommended to mix starting and stopping Services via changing Server Levels with starting and stopping them via the Service menu.


4.5.  Stopping Boards

Use the CT Server Administration Application to stop the services associated with the board.

Using the Server | Change Server Level option (see Changing the Server Level):

•	If the Service is Optional, then change the Server Level to 2

•	If the Service is Mandatory, change the Server Level to 1

You can use the Service | Stop method to stop Services, but it should not be necessary.  It is also not recommended to mix starting and stopping Services via changing Server Levels with starting and stopping them via the Service menu.


4.6.  Removing Boards

Stop the boards, stop the Server, shut down the server PC, then remove the boards.. Follow the steps described in:

•	4.5.  Stopping Boards

•	3.2.  Stopping the Server

Follow the PC hardware vendor's instructions for turning off the server PC. Remove the boards according to the board vendor's instructions.


4.7.  Replacing Boards

Follow the steps described in:

•	4.6.  Removing Boards

•	4.2.  Installing Resource Hardware and Software


4.8.  Uninstalling Boards

Board vendors should provide an uninstallation routine so that all software associated with a board can be easily removed from the Server. If the Administrator is required to perform a manual deinstallation:

1.	Select:

Menu	Quick Key(s)	Toolbar
View|CT Media Services	F3	-
2.	Select the CT Media Service(s) to be stopped, and then select:

Menu	Quick Key(s)	Toolbar
Service|Stop	-
3.	In order to check that the CT Media Service's status has changed from "Running" to "Idle", use F5 to update the window.

4.	Select:

Menu	Quick key(s)	Toolbar
View|CT Media Services	F3	-
Select the CT Media Service to be removed.

5.	Select:

Menu	Quick Key(s)	Toolbar
Service|Remove	Del
Any previously installed board software can now be removed from the Server.


4.9.  Working With the Simulated D/41E

4.9.1.  Adding the Simulated D/41E

4.9.2.  Removing the Simulated D/41E


4.9.1.  Adding the Simulated D/41E

The simulated D/41E package is installed by default when CT Media is installed. If the package has been removed from the Configuration Manager's CT Media Services list it can be re-added in the normal way. See 4.3.1.  Checking the Installation of a CT Media Service for details.

The executable for the package is:

\ctserver\server\services\ctsim\simd4x.exe

The package provides four simulated line interface devices:

•	dxxxB1C1

•	dxxxB1C2

•	dxxxB1C3

•	dxxxB1C4


4.9.2.  Removing the Simulated D/41E

To remove the simulated D/41E package follow the instructions for stopping and removing CT Media Services in 4.8.  Uninstalling Boards. DO NOT delete the executable or remove the SimD41 Resource Profile unless you are certain you will not need them again.


5.1.  Application Overview

If you are administering applications, you need to know how to:

•	Install the application executable, and any required data files, on the client

•	Configure a client to connect to the host

•	Add Application Profiles to the CT Server

•	Determine the application's call routing requirements

•	Modify the Routing Rules Profile and the ASI Map Profile so that calls are routed correctly to and from the application, and so that calls can be properly transferred between applications.

•	Start the application


5.2.  Installing Applications

Applications should come with their own installation, uninstallation, diagnostic, and other utilities. The installation utility should create an appropriate Windows NT Program Group, Program Icons, and use the appropriate Administration API functions to add any necessary Application Profiles to the CT Server. The application vendor should supply the Administrator with the following information:

•	Instructions on how to install the Application

•	A description of any utility applications

•	The name and description of any Application Profiles

•	Indicate whether or not the profiles are automatically added to the Server by the application installation routine

•	Instructions on how to modify the ASI Map and Call Routing Profiles to accommodate the application, if this is not done automatically when the application is installed.

If the application has been installed on a remote client machine see Appendix B - Stand-Alone Self Hosted Systems for instructions on how to configure Windows NT to recognize the host machine.


5.3.  Checking Application Profile Installation

After installing an application, you can use the CT Server Administration Application to see if the Application Profile has been added to the CT Server.

NOTE:	Details of the contents of Application Profiles are covered in Chapter 1, Volume 1, Other CT Media Documents.

Table 6.  Viewing Vendor Applications in the Administration Application

To check if the necessary profile(s) have been added, use the CT Server Administration Application and select:

Viewing Profiles

If the install process has failed to add the new Application Profile, the Administrator should add it manually.

More:

5.3.1.  Profile Formats

5.3.2.  Adding IEF Formatted Profiles

5.3.3.  Adding Text Formatted Profiles


Table 6.  Viewing Vendor Applications in the Administration Application

	is displayed in this view...
this installed component	Service Providers	CT Media Services	Profiles
Core Services	X	X
System Call Router	X	X	X
Vendor-supplied boards	X	X	X
Vendor-supplied applications			X
the Administrator can:	view only	add, remove, stop, start	add, remove, import, export, update


5.3.1.  Profile Formats

There are two defined Profile formats:

Text (*.prf)	This is effectively the same as a *.txt file.  A Profile saved in .prf format could be an invalid profile.
Import/Export (*.ief)	This format is intended for the interchange of Profiles between Servers (or for Profile backup).  Thus a Profile saved in .ief format will be parsed for consistency and validity before being stored.


5.3.2.  Adding IEF Formatted Profiles

If the profile is in Import/Export Format (*.ief):

1.	Select:

Menu	Quick key(s)	Toolbar
Profile|Import	-
2.	Specify the file name of the profile (including the full path name) and the name it will have in the Server.


5.3.3.  Adding Text Formatted Profiles

If the profile is an unparsed file in ASCII text format (*.prf):

1.	Start the appropriate Profile Editor by selecting:

Menu	Quick key(s)	Toolbar
Profile|New	Ctrl+P
Enter the type of profile to be edited in the dialog box.

2.	In the Profile Editor window, import the profile text by selecting:

Menu	Quick key(s)	Toolbar
Profile|Import from Text File...	-
Enter the name of the profile text file, and select "Open"

3.	In the Profile Editor window, store the imported profile on the Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store	Ctrl+S
Enter the name of the profile on the Server and select "OK".

4.	Close the Profile Editor.


5.4.  Routing Calls To and From a New Application

For call routing purposes, applications are identified in the CT Server by their Application Service Identifier(s) (ASI), which are defined in an application's associated Application Profile. If the newly installed application expects to receive incoming calls from the System Call Router (SCR) or from other applications, or hand-off calls to other applications, then the new application's ASI(s) must be entered into the ASI Map Profile, and optionally the Routing Rules Profile.

If the application vendor does not provide a mechanism for modifying these two profiles at application installation time, then the Administrator will have to modify the profiles manually. In this case, the application vendor should document the application's ASIs and descriptions of the applications that it expects to receive calls from or hand-off calls to.

For information on how to:

•	hand-off or receive calls from any application, including the SCR, see 6.2.  Handing Off Calls Between Applications.

•	route incoming calls see 6.3.  Inbound Call Routing.

•	route outbound calls, see 6.4.  Outbound Call Routing.

If the application vendor has not provided sufficient documentation for the Administrator to make routing decisions, the Administrator should view the vendor-supplied Application Profile for the newly installed application. See 7.  Interpreting Application Profiles for details.


5.5.  Starting Applications

Start the application according to the vendor's instructions.

NOTE:	If you have set up a CT Media client application to run as an NT Service, you also have the option of making that NT Service dependent on the CT Server startup.  (See the appropriate documentation in MSDN for details).  This will start the client application while the Server is still at Level 1 (i.e., it cannot support a Session to a client application).  There are two ways to handle this:

1.	Continually attempt to create a Client Session with appropriate handling of failure.  When the Client Session is successfully created, the CT Server is available.

2.	Create an Admin Session and continually request the Server Level until the level reaches 4. Then create the Client Session.

NOTE:	It is best to start at Level 4, not 5, so that the Application will be ready to handle inbound calls as soon as possible.  Depending on your hardware, inbound calls  could be generated by the hardware once the CT Server reaches Level 4, so it is still possible to have inbound calls not handled.


5.6.  Stopping Applications

Stop the application according to the vendor's instructions.


5.7.  Uninstalling Applications

If you wish to remove the application from the system,

1.	Uninstall the application according to the vendor's instructions.

2.	Remove the application's Application Service Identifier(s) from the ASI Map Profile.

3.	Remove the application's Application Service Identifier(s) from the Routing Rules Profile.


6.1.  Using Profiles to Control Call Routing

The Administrator is able to control call routing by modifying two profiles associated with the System Call Router (SCR):

•	the ASI Map Profile - named SCR_ASIMap

•	the Routing Rules Profile - named SCR_RoutingRules

These profiles are files that contain configuration and routing rules information, and which will interact with vendor supplied Application Profiles to ensure that applications function correctly.  The Administrator will generally have to modify one or both of these profiles when a new Application is added to the system.

In addition, the Administrator will have to ensure that the line interface devices available in the system are of the correct type for the SCR. This information must be documented by the SCR vendor. If the vendor documentation is inadequate the Administrator will have to examine SCR's Application Profile. See 7.  Interpreting Application Profiles for details.

Table 7.  System Call Router Profiles

CAUTION

It is not obligatory for an application to use the SCR to make and receive calls. The Administrator should bear in mind that applications which bypass the SCR are not subject to the SCR's routing rules.

More:

6.1.1.  The Function of the ASI Map Profile

6.1.2.  The Function of the Routing Rules Profile


Table 7.  System Call Router Profiles

Profile Name	Class	Purpose
SCR_ASIMap	ASIMap	Controls call hand-off
SCR_RoutingRules	RoutingRules	Controls call routing
SCR_AppProfile	Application	Selects line interface devices


6.1.1.  The Function of the ASI Map Profile

The ASI Map Profile maps the ASIs defined in one client-application's Application Profile to ASIs defined in one or more other client-application Application Profiles.

If a client application expects to hand-off calls to or receive calls from other client applications, then the systems Administrator must create entries in the ASI Map profile linking each source-application/target-application pair.

The syntax for the ASI Map Profile is described in 6.2.  Handing Off Calls Between Applications.


6.1.2.  The Function of the Routing Rules Profile

The Routing Rules Profile defines rules for :

•	routing inbound calls to particular classes of applications.

•	routing outbound calls to particular types of network interfaces.

Figure 6.  Outline of a Routing Rules Profile

The Routing Rules Profile contains:

•	an INBOUNDRULES statement

•	an optional OUTBOUNDRULES statement

The INBOUNDRULES statement defines rules for routing inbound calls to client applications on the basis of call features such as:

•	the number dialed

•	the number calling from

•	the date

•	the time

The optional OUTBOUNDRULES statement defines rules for routing outbound calls placed by client applications to line interface devices on the basis of call features such as:

•	the number dialed

•	the date

•	the time

The Application Service Identifiers used in the routing rules are declared in each application's Application Profile.

The syntax for the INBOUNDRULES statement is described 6.3.  Inbound Call Routing.

The syntax for the OUTBOUNDRULES statement is described in 6.4.  Outbound Call Routing.


Figure 6.  Outline of a Routing Rules Profile


6.2.  Handing Off Calls Between Applications

Figure 7.  ASI Mapping During Call Hand-off

Handing off calls  (that is, transferring the control of a call) from one application to another is one of the basic functions of the CT Server and is the purpose of the System Call Router (SCR).

The SCR is responsible for:

•	accepting a call, and its associated signal processing resources, from a source application.

•	determining a suitable target application, based on the ASI Map Profile.

•	if required, adjusting the mix of signal processing resources associated with the call so that it will satisfy the needs of the target application (as declared in the target application's Application Profile).

•	passing control of the call to the target application.

Call routing during hand-off is achieved by mapping the ASI of the target application, as it is declared in the source application, to the ASI or ASIs of potential target applications, as they are declared in the target applications' Application Profile. Hand-off will occur when the applicable mapping statement is encountered in the ASI Map.

It is the responsibility of the source application vendor to adequately document the ASIs that will be used during hand-off and the characteristics of the target applications they identify.

The mapping of ASIs for hand-off is the function of the ASI Map Profile.

The syntax of the ASI Map Profile is:

   <SourceAppProfile1>:<SourceASI1> =

            <TargetAppProfile1>:<TargetASI1>

            [,<TargetAppProfile2>:<TargetASI2>, ...]

   [<SourceAppProfile2>:<SourceASI2> =

            <TargetAppProfile3>:<TargetASI3>

            [,<TargetAppProfile4>:<TargetASI4>, ...]

:

:

NOTE:	If multiple target ASIs are supplied for one source ASI, then the list of target ASIs will be tried in order until one is available. If multiple ASIs are mapped to in an ASIMap, the SCR will still only choose one appropriate ASI.  If that fails, then the SCR will not try the next of the multiple ASIs to hand off to.

SourceASI1 does not have to be a defined ASI for SourceAppProfile1.  It may be defined, or it may be an arbitrary tag used for handoff (e.g.; in the CTgrp_HandOff() function) which the application writer expects the Systems Administrator to resolve to a valid target ASI in a valid Application Profile, using the appropriate line in the ASI Map Profile.

An example ASI Map Profile is given in Appendix A - Example Profiles. This example ASI Map Profile enables the hand-off of calls:

•	from an SCR, using the Application Profile SCR_AppProfile, to an auto-attendant application, using the Application Profile AutoAttendantProfile.

•	from an SCR, using the Application Profile SCR_AppProfile, to an "operator" application, using the Application Profile OperatorProfile.

•	from an auto-attendant application, using the Application Profile AutoAttendantProfile, to a fax-back application using the Application Profile FaxBackProfile.

//* AutoAttendant can receive a call from SCR                    */

SCR_AppProfile:Target1_ASI = AutoAttendantProfile:AA_ASI;

//* Operator can receive a call from SCR                         */

SCR_AppProfile:Target1_ASI = OperatorProfile:Oper_ASI;

//* AutoAttendant can hand off to FaxBack using "AA_HandoffTag"  */

AutoAttendantProfile:AA_HandOffTag = FaxBackProfile:FB_ASI;

More:


Figure 7.  ASI Mapping During Call Hand-off


6.3.  Inbound Call Routing

NOTE:	Please see 6.2.  Handing Off Calls Between Applications for a description of call hand-off before proceeding with the material in this section.

Figure 8.  Inbound Call Routing

All calls into the CT Server will be received by the System Call Router. Therefore, inbound call routing is a matter of ensuring that the SCR is able to hand-off calls to the applications that must process them. This procedure takes place in four stages:

•	the SCR applies inbound routing rules to the call to determine a suitable target ASI.

•	the SCR uses the ASI Map Profile to select a valid target application.

•	if required, the SCR adjusts the mix of signal processing resources associated with the call to meet the needs of the target application.

•	the SCR hands off the call and its associated signal processing resources to the selected target application.

It is the responsibility of the application vendor to document the ASIs of any applications that are designed to receive inbound calls.

The inbound routing rules are defined by the INBOUNDRULES statement in the Routing Rules Profile. The syntax for the INBOUNDRULES statement is:

INBOUNDRULES {

   <App1ASI> =

        [ Date(<date/time spec>) ]    /* relevant dates for app   */

        [, ExcludeDate( <date/time spec> ) ] /* dates to exclude  */

        [, CallerID(<phone number>) ] /* If call has the right    */

        [, CalledID(<phone number>) ] /* CallerID, CalledID, or   */

        [, LineID(<device name>)];    /* LineID, then send to app */

   [<App2ASI> =

        :

        :

}

NOTE:	No particular condition is required for the inbound rules; however you must use at least one condition, or the Profile Parser will return an error when you try to store the Profile.

Table 8.  Call Info Arguments in the Inbound Rules Statement describes the arguments that each of the entries in the INBOUNDRULES statement may take.

Table 8.  Call Info Arguments in the Inbound Rules Statement

Table 9.  Date/Time Spec Parameters

NOTE:	The start value of Time ranges may not be greater than the end range. Therefore
   time( 23:00 - 2:00 )
is not a valid range. This should be represented by
   time( 23:00 - 23:59 ), time( 0:00 - 2:00 )

NOTE:	Some Date Parameters may not be combined in one DateTime specification:

1.	DayOfMonth may not be combined with DayOfWeek, PositionInMonth or WeekOfYear

2.	PositionInMonth may not be combined with DayOfMonth or WeekOfYear

If there is more than one application receiving incoming calls, the inbound routing rules are applied in the order in which they appear in the inboundrules statement. The SCR will run down the list of rules and the call will be routed to the first application whose rule conditions are satisfied.

NOTE:	The SCR will route a call only once.  If the call cannot be successfully routed to the first appropriate application ASI in the inbound routing rules, then the call will result in an error.  The SCR will not consult the rules for another appropriate application ASI listed later.

Some applications have multiple entry points, with each entry point having its own Application Service Identifier. Refer to the application vendor's documentation to establish which Application Service Identifiers (if any) should appear in the inboundrules statement.

An example INBOUNDRULES statement is given in Appendix A - Example Profiles. These rules state:

•	any call coming in on 08001001 will be handed off to any application with an ASI of AA_ASI. If there is more than one application with that ASI, then the ultimate target application will depend on the order of ASI Map Profile entries.

•	any call coming in during working hours on any line, other than 08001001, will be handed off to any application with an ASI of Oper_ASI. If there is more than one application with that ASI, then the ultimate target application will depend on the order of ASI Map Profile entries.

•	otherwise all calls will be handed off to any application with an ASI of AA_ASI. If there is more than one application with that ASI, then the ultimate target application will depend on the order of ASI Map Profile entries.

INBOUNDRULES {

//* AutoAttendant can only receive calls that are dialed in on 08001001 */

AA_ASI =

Date( Time(00:00-23:59) ),

CalledID( 08001001 );

//* Operator will receive any other calls during working hours            */

Oper_ASI =

Date( Time(08:00-18:00));

//* ... otherwise AutoAttendant will get any call                        */

AA_ASI =

Date( Time(00:00-23:59) );

}

Once the SCR has applied the inbound routing rules, it will map the resultant ASI to valid target ASIs using the ASI Map and perform a hand-off. In this case the entries used in the ASI Map Profile will have the syntax:

<SCR Application Profile name>:

<ASI provided by inbound routing rules> =

<TargetAppProfile>:<TargetASI>;

See 6.1.1.  The Function of the ASI Map Profile for a description of the ASI Map Profile.

More:


Figure 8.  Inbound Call Routing


Table 8.  Call Info Arguments in the Inbound Rules Statement

Argument	Syntax
Phone number	CallerID(<phone number>)  or  CalledID(<phone number>) where <phone number> can be any combination of • Alphanumeric characters (A-Z, a-z, 0-9) • - , # or * • +++ (ending wildcard), e.g. 0800+++, will match 08001, 08001234567, etc. It can also be NONE: CallerID(NONE)
Device Name	LineID(<device name>) where <device name> is the installed device name. It can be a single device, or a contiguous group of channels: dxxxB1C1 or dxxxB1C1 ... ... dxxxB1C4 See Section 6.5.  The Device Name for details about device names.
Date/Time Spec	Syntax: (<parm1>(<value1>, <value2>-<value3>...),     (<parm2>(<value4>, <value5>-<value6>...),     ...) E.g.;   ( Time( 00:00 - 05:00 ), DayOfMonth( 12 ) ) See Table 9.  Date/Time Spec Parameters for the possible date/time parameters.


Table 9.  Date/Time Spec Parameters

Parameter	Syntax	Possible Values
Time	nn:nn-NN:NN	24-hour clock time from 00:00 to 23:59. For example, (08:30-17:00)
DayOfMonth	n or n-n	1-31
MonthOfYear	month  or month-month	JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
DayOfWeek	day or day-day	SUN MON TUE WED THU FRI SAT
WeekOfYear	n or n-n	1-53
PositionInMonth	(position)	FIRST SECOND THIRD FOURTH FIFTH LAST


6.4.  Outbound Call Routing

NOTE:	Please see 6.2.  Handing Off Calls Between Applications for a description of call hand-off before proceeding with the material in this section.

Figure 9.  Outbound Call Routing

All outbound calls from the CT Server are placed by the SCR, at the request of a client application. This procedure takes place in three stages:

•	the SCR applies outbound routing rules to determine the line interface device that the call will be placed on, and makes the call.

•	if required, the SCR adjusts the mix of the signal processing resources associated with the call to meet the needs of the target application.

•	the SCR hands off the call and its associated signal processing resources to the target application. Because the SCR was explicitly requested to make the call by a known application, call hand-off, in this case, does not require the use of the ASI Map Profile.

The outbound routing rules are defined by the OUTBOUNDRULES statement in the Routing Rules Profile. The syntax for the OUTBOUNDRULES statement is:

OUTBOUNDRULES {

     < device name 1 >=

[ Address( <phone number> ),]

[ prefix( <phone number prefix> ),]

[ Date(<date/time spec>),]

[ ExcludeDate(<date/time spec>)];

     [<device name 2>=

          ...   ]

   }

NOTE:	No particular condition is required for the outbound rules; however you must use at least one condition.

NOTE:	The RoutingRules profile parser doesn't allow ranges of device names; i.e., dxxxB1C1-4.  Each device must have its own name line entry.

<phone number>, <phone number prefix> and <date/time spec> are defined as in Table 10.  Call Info Arguments in the Outbound Rules Statement.

Table 10.  Call Info Arguments in the Outbound Rules Statement

If there is more than one outbound routing rule, each rule is applied in the order in which it appears in the outboundrules statement. The SCR will run down the list of rules and the call will be placed on the first line interface device whose rule conditions are satisfied.

An example OUTBOUNDRULES statement is given in Appendix A - Example Profiles. These rules state:

•	if possible, the line interface device dxxxB1C1 will be used for any outbound calls placed between 8am and 6pm.

•	at any other time, or if "dxxxB1C1" is busy, outbound calls will be placed on the line interface device a_vendor_channel. (This is not a real line interface device.)

OUTBOUNDRULES {

//* The line interface device "dxxxB1C1" will be preferentially selected  */

//* for outbound calls between 8am and 6pm                                */

dxxxB1C1 =

Date( Time(08:00-18:00) );

//* The line interface device "a_vendor_channel" can be used for outbound */

//* calls at any time                                                      */

a_vendor_channel =

Date( Time(00:00-23:59) );

}

More:


Figure 9.  Outbound Call Routing


Table 10.  Call Info Arguments in the Outbound Rules Statement

Argument	Syntax
Device name	<device name> where <device name> is the installed device name. It can be a single device, or a contiguous group of channels: dxxxB1C1 or dxxxB1C1 ... ... dxxxB1C4 See Section 6.5.  The Device Name for details about device names.
Phone number	Address(<phone number>) <phone number> is matched against the dial string supplied with CTscr_MakeCall() to select a device to make the outbound call on <phone number> can be any combination of Alphanumeric characters (A-Z, a-z, 0-9) - , # or * +++ (ending wildcard), e.g. 0800+++, will match 08001, 08001234567, etc.
Prefix	prefix (<phone number prefix>) <phone number prefix>, if supplied, will always be dialed before the dial string supplied with CTscr_MakeCall() when making an outbound call on this device.<phone number prefix> can be any combination of • Alphanumeric characters (A-Z, a-z, 0-9) • - , # or * Supported prefixes will be documented in vendor hardware documentation. • For example, you could use prefix (9) to dial "9" for an external line on all outbound calls.
Date/Time Spec	Syntax: (<parm1>(<value1>, <value2>-<value3>...),     (<parm2>(<value4>, <value5>-<value6>...),     ...) E.g.;   ( Time( 00:00 - 05:00 ), DayOfMonth( 12 ) ) See Table 9.  Date/Time Spec Parameters for the possible date/time parameters.


6.5.  The Device Name

Where a device name, or channel name, is required for a profile, the device name will be vendor-dependent.

More:

6.5.1.  For Simulated Dialogic Resources

6.5.2.  For Real Dialogic Resources

6.5.3.  For Other Resources


6.5.1.  For Simulated Dialogic Resources

 The device names will have the form:

dxxxBnCm

where:

•	n is the board number. Boards are numbered in the order of their board locator settings, with board 1 being assigned to the board having the lowest board locator setting.

•	m is the channel number. All boards have four channels, numbered 1 to 4. Boards with more than 4 channels, will be represented by virtual boards, i.e., a board with 16 channels will have 4 board names assigned to it, one for each 4 channel virtual device it supports.


6.5.2.  For Real Dialogic Resources

The device name will be of the form:

DialogicB<board locator ID>[TrunkN]<Prefix><Channel number>

where

•	The board locator ID corresponds to the piece of hardware in the machine's locator ID - the dial at the top of the card.

•	Trunk is applicable only for ISDN and Inband.  A Trunk is 1 span of a dual span board. It is one physical T1/E1 connection.

•	The Prefix will vary depending on the type of board in question:

1.	Analog   -  "LSI"

2.	MSI  -  "SI"

3.	Media only - "Media"

4.	ISDN  -  "PRI"

5.	T1 Inband - "Inband"

•	The Channel Number varies from 1..maxChannels.  maxChannels depends on board type (e.g. D/81SC = 8 channels).

E.g.;

•	DialogicB1LSI1 - 1st channel on Analog board

•	DialogicB1Trunk2PRI1 - Dual span ISDN board, 1st channel on second trunk (span)


6.5.3.  For Other Resources

Refer to the accompanying documentation from the vendor.


6.6.  Modifying Profiles

To modify an existing profile on the CT Server, Select:

Menu	Quick Key(s)	Toolbar
View|Profiles	F2	-
Double click on the profile to be modified, or choose Profile | Edit

Alternatively, you can edit an existing Profile by first starting a new Profile.

1.	Select

Menu	Quick key(s)	Toolbar
Profile|New	Ctrl+P
Enter a type of profile to be edited in the dialog box.

Once the Profile Editor window is open, retrieve the profile you want to edit from the CT Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Retrieve from server ...	Ctrl+R
Select the name of the CT Server the profile is stored on and click on "OK". Then select the profile to be retrieved and click on "Retrieve".

3.	In the Profile Editor window, edit the profile as appropriate.

4.	In the Profile Editor window, store the modified profile on the Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store	Ctrl+S
The Profile Checker (see "Checking a Profile" on page 116 ) will be automatically run.  If there is a syntax error in the profile, you will receive a message like the following:

5.	Fix the error.

6.	Store the Profile again.

7.	For an Application Profile, the Profile Checker does not check whether there is more than one Group Configuration of the same name in a GroupSet. The last one listed is the one that is actually used.

8.	Close the Profile Editor.

9.	The Profile Checker performs syntax checking only.  For example, the Attributes in a Resource Specification Expression are not parsed by the Profile Parser.  If you change Resource Attributes in a valid Profile, for safety you should check the e_cores log file to confirm that the CT Media Server accepted the Profile.


7.1.  Examining Application Profiles

7.1.1.  Default View

7.1.2.  KVSet View


7.1.1.  Default View

To view an installed Application Profile in the CT Server Administration Application:

1.	From the View menu, choose Profiles

2.	Double-click on the profile you want to view opened


7.1.2.  KVSet View

By default, an Application Profile opens using the Application Profile Editor, which is text-based for ease of editing.  If you want to view the underlying KVSet structure of an Application Profile, you can associate the Generic Profile Editor with Application Profiles.

1.	From the Profile menu, choose Associate

2.	As shown in the diagram, choose Application from the first drop-down list, and choose the prfedit.exe Profile Editor from the second drop-down list.

3.	Click on OK.

Now when you double-click on an Application Profile, it will open using the Generic Profile Editor.  See Appendix D - The Generic Profile Editor for details of the Generic Profile Editor.


7.2.  The Structure of an Application Profile

If the vendor has not provided sufficient documentation for the Administrator to make routing decisions, the Administrator will need to view the vendor-supplied Application Profile for the newly installed application. Figure 10.  An Outline of a Vendor Supplied Application Profile shows an outline of a vendor-supplied Application Profile.

Figure 10.  An Outline of a Vendor Supplied Application Profile

All client applications that need to use the System Call Router to acquire signal processing resources must install an Application Profile into the Configuration Manager. An Application Profile:

•	declares the signal processing resources required by the application in order to function correctly.

•	declares the Application Service Identifier(s) (ASIs) the application will use to identify itself to the CT Server.

•	documents the ASIs that the application will use to identify applications to hand-off calls to.

NOTE:	All of these sections are location-independent within the file.  I.e., the Resources block could appear at the end instead of the beginning with no effect on the meaning of the profile.

In particular, every application that will use the SCR to forward incoming calls, place outbound calls or hand-off calls must have at least one Application_Service statement in its Application Profile. This statement associates a vendor-supplied identifier, known as an Application Service Identifier, with:

•	an entry point into an application

•	the initial mix of signal processing resources used by that application

•	the call state required by the application

•	the need for other applications in the system

The syntax for the APPLICATION_SERVICE statement is:

APPLICATION_SERVICE <asi name>{

    GROUP_SET = <group set name>;

    DEFAULT_CONFIGURATION  = <config name>;

    [INBOUND_CALL_STATE = <CONNECTED|ALERTING>];

    [OUTBOUND_CALL_STATE =  <CONNECTED|ALERTING>];

    [HANDOFF = <target asi> [NORETURN|RETURN]];

    :

    :

}

The <asi name> entry in the APPLICATION_SERVICE line is the Application Service Identifier (ASI) for one particular entry point into the application associated with this Application Profile. The application's ASI must be declared in the ASI Map Profile if it is to receive calls handed off by other applications, including the SCR.

The <target asi> entry in the optional HANDOFF line documents the ASIs that will be used by the application to identify particular hand-off targets.  These ASIs must be declared in the ASI Map Profile, if hand-off by this application is to be successful.

Several example Application Profiles are given in Appendix A - Example Profiles. The following excerpt shows the only APPLICATION_SERVICE statement to appear in AutoAttendantProfile.

APPLICATION_SERVICE AA_ASI {

   GROUP_SET = AA_GroupSet;

   DEFAULT_CONFIGURATION = PRG;

   INBOUND_CALL_STATE = CONNECTED;

   OUTBOUND_CALL_STATE = CONNECTED;

   HANDOFF = AA_TargetASI RETURN;

};

This statement is interpreted to mean:

•	the application associated with this profile has only one entry point, identified by the ASI AA_ASI. This means that the ASI Map Profile must include a line that looks like:

<SCRProfileName>:<TargetASI> =
AutoAttendantProfile:AA_ASI

If the Administrator wishes to apply some inbound routing rule to this application the ASI AA_ASI must be associated with an INBOUNDRULES statement in the Routing Rules Profile.

•	the application expects to hand-off a call to another application at some stage. The target application is identified in the source application's code as AA_HandoffTag. This means that the ASI Map Profile must include a line that looks like:

AutoAttendantProfile:AA_HandoffTag =
<TargetAppProfile>:<TargetASI>

NOTE:	Appendix A - Example Profiles shows the example ASI Map Profile containing the relevant lines.

More details about the Application Profile can be found in Chapter 2, Volume 1, of the Other CT Media Documents.

More:


Figure 10.  An Outline of a Vendor Supplied Application Profile


8.1.  Error and Event Logging

8.1.1.  Overview

8.1.2.  CT Media Event Viewer

8.1.3.  CT Media Events in the NT Event Viewer

8.1.4.  Error Log Files


8.1.1.  Overview

CT Media supplies an Event Log where Error and Event information will be available to the Administrator.  This log is viewable using the CT Media Event Viewer.  See Section 8.1.2.  CT Media Event Viewer.

Errors and Events are also viewable in text-based Log Files which are created for each active service.  See Section 8.1.4.  Error Log Files.

The Windows NT Event Viewer shows CT Media Events sent during startup or shutdown of the CT Media Server, when the CT Media Event Viewer is not yet enabled to receive Events.  See Section 8.1.3.  CT Media Events in the NT Event Viewer.


8.1.2.  CT Media Event Viewer

CT Media's Event Management provides an Event Log which is a stored list of all events generated by CT Media components or applications.

Systems administrators will use the Event Viewer application to

•	view the event log

•	using a filter, select events of interest

•	print the event log

•	configure the event log

The Event Viewer can not

•	change the contents of the log.

For instructions on using the Event Viewer, see Appendix G - CT Media Event Viewer User Interface.


8.1.3.  CT Media Events in the NT Event Viewer

Events such as the starting and stopping of the CT Media Server NT Service will be logged in the Windows NT Event Log.  Use the Event Viewer in Administration Tools to access the events from Source: CTMS Server.

NOTE:	Events will be visible in the Windows NT Event Viewer in both the System and Application Logs.

There are two common types of CT Media Events reported here.

Type	Description	To continue...
Startup Error	This means that one of the necessary stages of the startup of the CT Server has failed.  The CT Server will not start.	You should try again to start the CT Server.  If that fails. contact Dialogic Tech Support.
Shutdown Error	This means that one of the stages of the shutdown of the CT Server has failed.  The CT Server will not be cleanly shut down.	You should try to start the CT Server when you want to use it again.  If that fails. contact Dialogic Tech Support.
Table 11.  CT Media Events lists the possible Events.  Note that many of them are of the two common types defined above.

Table 11.  CT Media Events


Table 11.  CT Media Events

ID	Severity	Description
0	Informational	"The Dialogic CT Server has started successfully."
1	Informational	"The Dialogic CT Server has stopped."
2	Error	"StartServiceCtrlDispatcher() failed." • Startup Error.
3	Error	"The stop events could not be created.' • Startup Error.
4	Warning	"SetServiceStatus() failed." • This means that the CT Server NT Service could not change status.  NT might not know the correct status of this Service, which could lead to undefined behavior. • Restart the CT Server if any problems occur.
5	Error	"SCproc_Deinitialize() failed." • Shutdown Error.
6	Error	"SCproc_Initialize() failed." • Startup Error.
7	Error	"The SMP Hub process could not be started." • Startup Error.
8	Error	"The SMP Hub stop event could not be created." • Startup Error.
9	Error	"A CTMS Server Registry value could not be read." • This means that NT could not access a required Registry value for CT Media.  The Registry entries are corrupt. • Reinstall CT Media.  If problem persists, contact Dialogic Tech Support.
10	Error	"A CTMS Server Registry key could not be read." • This means that NT could not access a required Registry key for CT Media.  The Registry entries are corrupt. • Reinstall CT Media.  If problem persists, contact Dialogic Tech Support.
11	Warning	"The SMP Hub had to be terminated forcefully." • This is a Shutdown Error.
12	Warning	"The message delivery thread had to be terminated forcefully." • This is a Shutdown Error.
13	Error	"The CTMS Server profile database could not be loaded." • This is a Startup Error.
14	Error	"The CTMS Server profile database could not be closed properly." • Shutdown Error.
15	Error	"The Root Service failed to start." • Startup Error.
16	Error	"The Root Service took too long to start." • Startup Error.
17	Error	"The Service Manager failed to change the Server level." • Restart the CT Server.
18	Error	"The Service Manager failed to initialise." • Startup Error.
19	Error	"The Service Manager failed to shutdown." • Shutdown Error
20	Error	"The CTMS Server entered an unknown state while at level X - Emergency shutdown to level Y initiated." • This means that CT Media is trying to recover by shutting the CT Server down to a lower level.   • Once the shutdown has occurred, CT Media should have recovered.  If not, then restart the CT Server.  If problem persists, contact Dialogic Tech Support.
21	Error	"Memory allocation error occurred while starting this Service." • Startup Error
22	Warning	"Tracing initialisation failed." • Startup Error
23	Error	"A fatal error has occurred in the component XXX  Description: YYY   File Name:ZZZ  Line Number: 00000" • Contact Technical Support with the details in the log
24	Error	"An internal system error has occurred!  To obtain technical support, please contact the supplier of the component XXX and provide the following details.   Component Name: XXX   Description:YYY   File Name: ZZZ   Line Number: 000"
25	Error	"Dialogic Event Management system initialization failed." • Startup Error


8.1.4.  Error Log Files

Any active service will have a text-based error log file in the \CTServer\server\logs\ directory, if the service

1.	performs error logging (this is controlled by the vendor), and

2.	has been set up by the Administrator with the correct logging switches in the command line (see Service Logging Switches and Log File Names.

For example, the following standard CT Media Services will have log files as listed.

Service	Log file
DLGC_CoreService	e_cores.01
DLGC_ISE	e_ise.01
DLGC_SimD4x	e_simd4.01
NOTE:	These log files will be stored in \CTServer\Server\Logs.

More:

Service Logging Switches and Log File Names

Multiple Log Files

Logged Message Examples


Service Logging Switches and Log File Names

To control which events and errors are logged for each service in the text-based log files, there are defined logging switches.

NOTE:	These switches do not control logging to the Event Log which is viewable using the CT Media Event Viewer,

These case-sensitive switches can be used when creating or editing a CT Media Service.  They are included within the Command Line of an executable Service, or supplied as arguments in a DLL Service.

Switch	Description
-F, /F	Outputs all failure or fatal errors for this service to <CTMSLogDir>\ e_srvNme.xx  where • srvNme is a string identifier supplied by the Service • xx is a 2 digit extension to allow for multiple logs) NOTE: See Multiple Log Files for details of multiple logging.
-f, /f	Outputs all failure or fatal errors for this service to cout. This option would be useful for a Resource Developer when debugging a service. NOTE: To view the output, you must • go to Settings | Control Panel | Services 1. select "CTMS Server" 2. in the Log On As section, choose "Allow Service to Interact with Desktop • be running the service from a console window.
NOTE:	<CTMSLogDir> is the CTMS log files path as indicated by the appropriate key in the NT registry.  On installation, this will be \CTServer\Server\Logs. If no key can be found, <CTMSLogDir> defaults to .\


Multiple Log Files

CT Media uses circular logging, with a default of two log files.

A new log file is generated because..

1.	The CT Server has just started and no log file existed.  In this case, an e_srvNme.01 log file will be created.

2.	The existing log file is full.

To alter the…	Edit the value of the Registry Key…
size of a log file (before it is considered full and a new log file created)	HKEY_LOCAL_MACHINE\SOFTWARE\Dialogic\CTMS Server\Environment\LogFileSize
number of log files (*.01, *.02, etc) that will be created before starting over with *.01	HKEY_LOCAL_MACHINE\SOFTWARE\Dialogic\CTMS Server\Environment\LogArraySize
directory in which log files are stored	HKEY_LOCAL_MACHINE\SOFTWARE\Dialogic\CTMS Server\Environment\LogDirPath


Logged Message Examples

Logged messages arrive in the form:

filename(line number) [time & date]: control message kvset

Some examples of non-error logged message examples follow, showing a Profile being parsed:

...

PROCACHE.cxx(65) [09:36:17 10/28/97]: Loading profile:__RAS_CONF_PROFILE__

APPPROF.cxx(490) [09:36:17 10/28/97]: Parsed resource MY_Conf from profile

__RAS_CONF_PROFILE__

APPPROF.cxx(408) [09:36:17 10/28/97]: Parsed resources from profile :

__RAS_CONF_PROFILE__

APPPROF.cxx(818) [09:36:17 10/28/97]: Parsed configuration CONFONLY from

profile __RAS_CONF_PROFILE__

...

Some logged error messages follow:

...

.\CCSReg\ccsreg.cxx(216) [09:54:55 10/28/97]: CCSRegistry::~CCSRegistry(): There were 7 CCS's left in the CCS Registry when shutdown

{

}spr.cxx(442) [09:55:06 10/28/97]: DL_SPR::CloseSDP(): Failed to deregister with RAS, error @23070740

...

NOTE:	The error code, as a CTsymbol, is listed with an error message.  In the above example, you can translate the error @23070740 by opening the file \CTServer\ctmssym.tbl and searching this file for 23070740.


8.2.  System Snapshot Utility

System Snapshot is an executable which will gather relevant information about your system.  System Snapshot will be run automatically when the CT Media Server or some other CT Media process terminates abnormally.  You can run it yourself at any time to provide Dialogic with information to aid in solving problems you are having.

The executable for System Snapshot is at CTServer\server\bin\SnapShot.exe (adjust this if you have installed under a different directory than the default of CTServer).

The output from System Snapshot will be found in a new directory which is:

•	at the same level as your CT Media installation directory

•	named after your installation directory (e.g.; CTServerSnapShot for a default installation)

The latest output from the last execution of System SnapShot will always be in a subdirectory named SSLatest (e.g.; \CTServerSnapShot\SSLatest\).  This directory is what should be zipped and sent to Dialogic Technical Support.

NOTE:	Older versions will be renamed when a new SSLatest is created (e.g.; SS1, SS2, etc., with SS1 being the oldest version).  You should delete old versions from this directory periodically, to save space.


8.3.  Statistics

CT Media returns operating statistics in a range of areas.  These statistics are accessed through symbol counters, which are returned from the CTadm_GetCounterInfo() and CTadm_GetCounterValues().  These statistics are also viewable using Windows NT's Performance Monitor.

More:

8.3.1.  Statistical Counters

8.3.2.  Counter Managers

8.3.3.  Instances

8.3.4.  Process Based


8.3.1.  Statistical Counters

A statistical counter, or counter, is a value that reflects the usage history of an operation,  or the current state of some object.  Counters record the status of a particular attribute that is controlled by their owning manager.  The values of the counters change over time as the attribute alters in response to requests and events on the server.

All counters are initially set to zero when they are registered.

Counters supported by the current API must be representable as a 32 bit number.  Each counter will have its own unique symbol that is defined by the creator and added to the ct_syms.h file.

Counters will have a symbol name that reflects the object they are associated with.  The following naming convention is used (Instance Types are defined below):

Object_Vendor_CounterNameByInstanceType

Some examples of possible counters are shown below

Container_DLGC_OpenObjectsByProcess

Session_DLGC_LoginsCreatedByProcess


8.3.2.  Counter Managers

A Counter Manager is the conceptual owner of a group of related statistical counters.  For example, the KVSet Counter Manager owns all counters that detail KVSet usage,  such as total KVSet creations and KVSet destructions.

A Counter Manager is identified by a unique symbol rather than a string so that it is language independent

All Counter Managers have a unique symbol that is placed in the ct_syms.h file so that client applications can request that manager's current counter values.  The following naming convention is used:

Object_Vendor_StatisticsManager

For example:

Container_DLGC_StatisticsManager

KVSet_DLGC_StatisticsManager

SCR_DLGC_StatisticsSDKManager


8.3.3.  Instances

The value for a counter may be broken down and spread over a number of instances of the same instance type.  An instance is a single item from a family of items of the same type.  For example,  the Inbound Requests counter maintained by the Session Manager could be spread over instances of an Application Instance Type.  This means that a single counter can have multiple values associated with it as shown in the example below:

Table 12.  Instance Type Example

Each Counter Manager is capable of supporting multiple instance classes.


Table 12.  Instance Type Example

Application Instances	Inbound Requests Values
"HIHI\\Ansr.exe (6E)"	125
"HIHI\\Ansr.exe (4F)"	465
"WEKA\\Winvote.exe (5F)"	12
"KUAKA\\Contmgr.exe (5F)"	3421


8.3.4.  Process Based

Statistical counters are collected on a process by process basis.  Because the CT Server and its resources may reside in separate processes,  Counter Managers are created on a process by process basis.  That means that there may be multiple versions of the same Counter Manager in the system - one on each process and another on the server itself.


8.4.  Available Statistics

8.4.1.  Collection Statistics

8.4.2.  Container Statistics

8.4.3.  Group Statistics

8.4.4.  ISE Statistics

8.4.5.  KVSet Statistics

8.4.6.  LCM Statistics

8.4.7.  SCR Statistics

8.4.8.  Session Statistics

8.4.9.  SMP Statistics

8.4.10.  SPCAS Statistics


8.4.1.  Collection Statistics

Manager Name	• Collect_DLGC_CollectionManager
Name	• CT Media Collections (Per Process)
Description	• This collection performance object records statistics pertaining to collection usage with the CT server.
These statistics are available and viewable through the NT Performance Monitor, but their values are not relevant to developers.


8.4.2.  Container Statistics

Manager Name	• Container_DLGC_StatisticsManager
Object Name	• CT Media Containers (Per Process)
Object Description	• Container Objects Statistics
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the cores or nodem instance is chosen, or any Resource process using media.

Statistics Symbol	Description
Container_DLGC_ReadBytesByProcess	Rate of bytes read
Container_DLGC_WriteBytesByProcess	Rate of bytes written
Container_DLGC_OperationsByProcess	Rate of container operations performed
Container_DLGC_CmdQueueSizeByProcess	Number of operations waiting to be processed in the container command queue
Container_DLGC_OpenObjectsByProcess	Number of data objects currently open
Container_DLGC_OpenObjectsReadByProcess	Number of data objects currently open for READ access
Container_DLGC_OpenObjectsWriteByProcess	Number of data objects currently open for WRITE access
Container_DLGC_OpenObjectsCopyByProcess	Number of data objects currently open for COPY access
Container_DLGC_MappedBytesByProcess	Number of file mapped bytes


8.4.3.  Group Statistics

Manager Name	• Group_DLGC_StatisticsManager
Object Name	• CT Media LCM (Per Process)
Object Description	• Logical Connection Manager
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the cores instance is chosen,.

Statistics Symbol	Description
Group_DLGC_CommandsIssuedByProcess	Rate of commands received by groups on the Server
Group_DLGC_ConfigurationFailuresByProcess	Rate of group configuration requests that failed on the Server
Group_DLGC_ConfigurationSuccessesByProcess	Rate of successful group configuration requests
Group_DLGC_CountByProcess	Rate of groups currently active on the Server
Group_DLGC_CreationsByProcess	Rate of groups created on the Server.
Group_DLGC_HandoffFailuresByProcess	Rate of Handoff failures received by groups on the Server from an application
Group_DLGC_HandoffSuccessesByProcess	Rate of successful Handoffs received by groups on the Server from an application.
Group_DLGC_MaximumByProcess	The maximum number of groups handled by the Server


8.4.4.  ISE Statistics

Manager Name	• ISE_DLGC_StatisticsManager
Object Name	• CT Media ISE (Per Process)
Object Description	• Intelligent Switch Extension
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the ise instance is chosen.

Statistics Symbol	Description
ISE_DLGC_InboundCallsByProcess	The rate of inbound calls received
ISE_DLGC_InboundCallFailuresByProcess	The total number of inbound call failures that have occurred since the server was started. Inbound calls will mostly fail because their was no application for the ISE to handoff to.
ISE_DLGC_AnsweredCallsByProcess	The rate of answered calls (including successful and unsuccessful)
ISE_DLGC_AnsweredCallFailuresByProcess	The number of answer calls that have failed since the server was started
ISE_DLGC_DroppedCallsByProcess	The rate of dropped calls (including successful and unsuccessful)
ISE_DLGC_DroppedCallFailuresByProcess	The number of drop calls that have failed since the server was started
ISE_DLGC_MakeCallsByProcess	The rate of make calls (including successful and unsuccessful)
ISE_DLGC_MakeCallFailuresByProcess	The number of make calls that have failed since the server was started
ISE_DLGC_MakeConsultationCallsByProcess	The rate of make consultation calls (including successful and unsuccessful)
ISE_DLGC_MakeConsultationCallFailuresByProcess	The number of make consultation calls that have failed since the server was started
ISE_DLGC_SendMessageByProcess	The rate of send messages (including successful and unsuccessful)
ISE_DLGC_SendMessageFailuresByProcess	The number of send messages that have failed since the server was started
ISE_DLGC_TransferredCallsByProcess	The rate of transfer calls (including successful and unsuccessful)
ISE_DLGC_TransferredCallFailuresByProcess	The number of transfer calls that have failed since the server was started
ISE_DLGC_DevicesByProcess	The number of line devices that are currently registered in service with the ISE
ISE_DLGC_CallsByProcess	The rate at which new calls are arriving in the system. A call arrives in the system when either an inbound call arrives on a line device, or an application makes a new call.
ISE_DLGC_CurrentCallsByProcess	The number of calls that are currently in the server.


8.4.5.  KVSet Statistics

Manager Name	• KVS_DLGC_StatisticsManager
Object Name	• CT Media KVSets (Per Process)
Object Description	• The CT Media KVSet object type includes those counters that apply to all KVSet operations on the CT Server
Statistics Symbol	Description
KVS_DLGC_CreatedByProcess	The rate of KVSets created
KVS_DLGC_DestroyedByProcess	The rate of KVSets destroyed
KVS_DLGC_CopiedByProcess	The rate of KVSets copied
KVS_DLGC_CopyOnWritesByProcess	The number of KVSet copies that were subsequently altered and required a copy on write to be performed
KVS_DLGC_ActiveKVSetsByProcess	The number of KVSets currently created but not yet destroyed


8.4.6.  LCM Statistics

Manager Name	• Conn_DLGC_StatisticsManager
Object Name	• CT Media LCM (Per Process)
Object Description	• Logical Connection Manager
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the cores instance is chosen.

Statistics Symbol	Description
Conn_DLGC_ConnectionsByProcess	Total number of Connections in the system. • Includes the internal Connections which make up Groups and Conferences as well as inter-Group/Conference connections.
Conn_DLGC_SetDataFlowByProcess	Total number of SetDataFlow requests currently running.
Conn_DLGC_LockedOutRequestsByProcess	Total number of requests which have ever been (temporarily) locked out by LCM..
Conn_DLGC_GroupsByProcess Total	Number of Groups currently registered with the LCM
Conn_DLGC_ConferencesByProcess	Total number of conferences currently registered with the LCM.
Conn_DLGC_SDPsByProcess	Total number of SDPs currently registered with the LCM.


8.4.7.  SCR Statistics

Manager Name	•  SCR_DLGC_StatisticsManager
Object Name	• CT Media SCR (Per Process)
Object Description	• System Call Router
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the "ise" instance is chosen.

Statistics Symbol	Description
SCR_DLGC_HandOffsByProcess	The rate at which groups are being handed off
SCR_DLGC_HandOffFailuresByProcess	The number of group handoffs that have failed since the server was started
SCR_DLGC_HandOffsInProgressByProcess	The number of group handoffs that are currently in progress in the server
SCR_DLGC_RequestGroupsByProcess	The rate at which groups are being requested
SCR_DLGC_RequestGroupFailuresByProcess	The number of RequestGroups that have failed since the server was started
SCR_DLGC_CCSsByProcess	The number of Call Control Stacks that are registered with SCR


8.4.8.  Session Statistics

Manager Name	•  Session_DLGC_StatisticsManager
Object Name	• CT Media Sessions (Per Process)
Object Description:	• The Session Performance Object has information about the sessions, communication connections and counts of requests, responses and events processed by the Server from an application point of view.
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the cores or nodem instance is chosen.

Statistics Symbol	Description
Session_DLGC_CreateRequestsByProcess	Rate of requests for sessions to be created on the Server
Session_DLGC_CreatedByProcess	Rate of sessions created on the Server
Session_DLGC_DestroyedByProcess	Rate of sessions destroyed on the Server
Session_DLGC_DestroyedByLinkFailureByProcess	Rate of sessions destroyed on the Server due to communications failure
Session_DLGC_LoginsCreatedByProcess	Rate of communications connections created on the Server
Session_DLGC_LoginsDestroyedByProcess	Rate of communications connections destroyed on the Server
Session_DLGC_LoginsFailedByProcess	Rate of communications connections lost on the Server
Session_DLGC_ServicesRegisteredByProcess	Number of session services registered on the Server
Session_DLGC_RequestsByProcess	Rate of requests received by the sessions on the Server from an application
Session_DLGC_ResponsesByProcess	Rate of responses with OK status received by applications from the sessions on the Server
Session_DLGC_EventsByProcess	Rate of events received by applications from the sessions on the Server
Session_DLGC_FailedResponsesByProcess	Rate of responses with failed status received by the applications from the Server
Session_DLGC_SessionCount	Rate of sessions currently created
Session_DLGC_ConnectionCount	Rate of communication connections currently created


8.4.9.  SMP Statistics

Manager Name	• SMP_DLGC_SMPManager
Object Name	• CT Media SMP (System Messaging Protocol) Comms (Per Process)
Object Description	• SMP communication
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the cores instance is chosen.

Statistics Symbol	Description
SMP_DLGC_InterprocessMessagesByProcess	The rate of messages sent to destinations in other processes
SMP_DLGC_IntraprocessMessagesByProcess	The rate of messages sent to destinations within the process (i.e. local destinations)
SMP_DLGC_BouncedMessagesByProcess	The number of messages that have been returned to sender due to a missing (or invalid) destination since the server was started
SMP_DLGC_DiscardedMessagesByProcess	The number of messages that have been discarded by SMP due to both the source and destination being missing
SMP_DLGC_QueueLengthByProcess	The total number of messages stored in the SMP input queue
SMP_DLGC_MaximumQueueLengthByProcess	The maximum number of messages that have been stored in the SMP input queue at any one time over the life span of the process


8.4.10.  SPCAS Statistics

Manager Name	• SPCAS_DLGC_StatisticsManager
Object Name	• CT Media Resource Allocation (Per Process)
Object Description	• The Resource Allocation Service Performance Object has information about the resource reconfiguration and allocation on the server
NOTE:	When using the Performance Monitor, remember that this Object will only show valid values when the cores instance is chosen.

Statistics Symbol	Description
SPCAS_DLGC_ReconfigsByProcess	The rate of reconfigurations occurring on the server
SPCAS_DLGC_ActiveReconfigsByProcess	The number of currently active reconfigurations
SPCAS_DLGC_StalledReconfigsByProcess	The number of currently active reconfigurations that cannot progress until other resources become available
SPCAS_DLGC_SuccessfulReconfigsByProcess	The rate of successful completed reconfigurations
SPCAS_DLGC_FailedReconfigsByProcess	The rate of reconfiguration failures. Note this does not include reconfigurations stopped by the user
SPCAS_DLGC_StoppedReconfigsByProcess	The rate of reconfigurations stopped by the user
SPCAS_DLGC_DestroyedGroupsByProcess	Groups destroyed is the rate of groups destroyed
SPCAS_DLGC_DestroyingGroupsByProcess	The number of groups currently being destroyed by the server
SPCAS_DLGC_RegisteredSPCsByProcess	The number of SPCs registered with the server
SPCAS_DLGC_UnavailableSPCsByProcess	The number of SPCs registered with the server, but unavailable for use in a group
SPCAS_DLGC_AllocatedSPCsByProcess	The number of SPCs registered with the server that are allocated to a group
SPCAS_DLGC_DeregisteredSPCsByProcess	The number of SPCs that have deregistered from the server but are still allocated to a group
SPCAS_DLGC_FailedAllocationsByProcess	The rate of server attempts to allocate an SPC to a group, but the SPC was not allocated
SPCAS_DLGC_FailedDeallocationsByProcess	The rate of server attempts to deallocate an SPC from a group, but the SPC was not deallocated


8.5.  Using Statistics - Monitoring Scenarios

Some possible areas that could be monitored using Administration Statistics are:

•	Call Activity

•	Disk Activity

•	Call Channel Utilization

•	CPU Drains

•	Failure Rate

More:

8.5.1.  Call Activity

8.5.2.  Disk Activity

8.5.3.  Call Channel Utilization

8.5.4.  CPU Drains

8.5.5.  Failure Rate


8.5.1.  Call Activity

To monitor call activity, the following statistics may be useful.

Using Admin API	Using Performance Monitor
ISE_DLGC_StatisticsManager	CTMS ISE (Per Process)
• ISE_DLGC_InboundCallsByProcess	• ISE Inbound Calls
• ISE_DLGC_AnsweredCallsByProcess	• ISE Answer Calls
• ISE_DLGC_MakeCallsByProcess	• ISE Make Calls
• ISE_DLGC_MakeConsultationCallsByProcess	• ISE Make Consultation Calls
• ISE_DLGC_TransferredCallsByProcess	• ISE Transferred Calls
Admin API	Performance Monitor
SCR_DLGC_StatisticsManager	CTMS SCR (Per Process)
• SCR_DLGC_HandOffsByProcess	• SCR Handoffs
• SCR_DLGC_HandOffsInProgressByProcess	• SCR Handoffs In Progress


8.5.2.  Disk Activity

To monitor disk activity, the following statistics may be useful.

Using Admin API	Using Performance Monitor
Container_DLGC_StatisticsManager	CTMS Containers (Per Process)
• Container_DLGC_ReadBytesByProcess	• Data Object Bytes Read
• Container_DLGC_WriteBytesByProcess	• Data Object Bytes Written
• Container_DLGC_OperationsByProcess	• Container Operations
• Container_DLGC_CmdQueueSizeByProcess	• Command Queue Size


8.5.3.  Call Channel Utilization

These Counters are visible using Instance: anlogspp

Using Admin API	Using Performance Monitor
SPCAS_DLGC_StatisticsManager	CTMS Resource Allocation (Per Process)
• SPCAS_AllocatedSPCsByProcess	• RAS Allocated SPCs
• SPCAS_RegisteredSPCsByProcess	• RAS Registered SPCs
• SPCAS_UnavailableSPCsByProcess	• RAS Unavailable SPCs
• SPCAS_StalledReconfigsByProcess	• RAS Stalled Reconfigurations


8.5.4.  CPU Drains

Using Admin API	Using Performance Monitor
SPCAS_DLGC_StatisticsManager	CTMS Resource Allocation (Per Process)
• SPCAS_ReconfigsByProcess	• RAS Reconfigurations
KVS_DLGC_StatisticsManager	CTMS KVSets (Per Process)
• KVS_DLGC_CreatedByProcess	• KVSets Created
• KVS_DLGC_DestroyedByProcess	• KVSets Destroyed
• KVS_DLGC_CopiedByProcess	• KVSets Copied
Session_DLGC_StatisticsManager	CTMS Sessions (Per Process)
• Session_DLGC_RequestsByProcess	• Session Requests Received
• Session_DLGC_SessionCount	• Sessions Active


8.5.5.  Failure Rate

Using Admin API	Using Performance Monitor
SPCAS_DLGC_StatisticsManager	CTMS Resource Allocation (Per Process)
• SPCAS_FailedReconfigsByProcess	• RAS Failed Reconfigurations
• SPCAS_FailedAllocationsByProcess	• RAS Failed Allocations
SCR_DLGC_StatisticsManager	CTMS KVSets (Per Process)
• SCR_DLGC_HandOffFailuresByProcess	• SCR Handoff Failures
• SCR_DLGC_RequestGroupFailuresByProcess	• SCR Request Group Failures
Session_DLGC_StatisticsManager	CTMS Sessions (Per Process)
• Session_DLGC_DestroyedByLinkFailureBy Process	• Session Destroyed By Link Failure
• Session_DLGC_LoginsFailedByProcess	• Connections Failed
• Session_DLGC_FailedResponseByProcess	• Session Responses Failed
ISE_DLGC_StatisticsManager	CTMS ISE (Per Process)
• ISE_DLGC_InboundCallFailuresByProcess	• ISE Inbound Call Failures
• ISE_DLGC_AnsweredCallFailuresByProcess	• ISE Answer Call Failures
• ISE_DLGC_MakeCallFailuresByProcess	• ISE Make Call Failures
• ISE_DLGC_MakeConsultationCallFailuresBy Process	• ISE Make Consultation Call Failures
• ISE_DLGC_TransferredCallFailuresByProcess	• ISE Transfer Call Failures
• ISE_DLGC_SendMessageFailuresByProcess	• ISE Send Message Failures


8.6.  Tuning Timeouts for CT Media Services

The available timeouts are:

PingInterval	Time (sec) to wait for a ping reply
CheckInterval	Time (sec) to wait before the next ping is issued
HangTimeout	Time (sec) to wait for a reply after the start of a ping request before regarding the Service as hung NOTE: This must always be larger then Ping Interval.
These timeouts can be tuned by entering the timeouts as DWORD keys in the Windows NT Registry under

HKEY_LOCAL_MACHINE\Software\Dialogic\CTMS Server\CTMSboot


8.7.  Processor Affinity

As shown in Adding a CT Media Service, you can set the processor that an executable Service should run on.  This is called Processor Affinity.

More:

8.7.1.  Node Manager and Hub

8.7.2.  Errors


8.7.1.  Node Manager and Hub

Processor Affinity can also be set for the two main CT Media Server Processes (Node Manager and Hub).  By default, these Processes run on the first processor.  To specify the processors for these Processes:

1.	Open the Registry Editor, and go to HKEY_LOCAL_MACHINE\Software\Dialogic\CTMS Server\CTMSboot

2.	Set the value of the DWORD keys named

•	NodemProcessor and/or

•	HubProcessor

(as appropriate) to the CT Media processor you want.

NOTE:	CT Media starts numbering processors at 1, whereas NT starts numbering at 0.  However, if you specify process 0, CT Media will default to the first processor rather than returning an error.

NOTE:	Changing these keys will not take effect until the CT Server has been stopped and restarted (a reboot will also achieve this.)


8.7.2.  Errors

If a process is unable to be bound to a specified processor, a warning message shall be logged.  If the process is a service, the message is logged to the e_ndmgr.txt log file, if the process is the Hub or Node Manager, then the message is logged to the NT event log.


ASI Map Profile

The ASI Map Profile maps ASIs, as used by a source application, onto ASIs as used by a target or destination application during call hand-off.

This example ASI Map Profile enables the hand-off of calls:

•	from an SCR, using the Application Profile SCR_AppProfile, to an auto-attendant application, using the Application Profile AutoAttendantProfile.

•	from an SCR, using the Application Profile SCR_AppProfile, to an "operator" application, using the Application Profile OperatorProfile.

•	from an auto-attendant application, using the Application Profile AutoAttendantProfile, to a fax-back application using the Application Profile FaxBackProfile.

//* AutoAttendant can receive a call from SCR                    */

SCR_AppProfile:Target1_ASI = AutoAttendantProfile:AA_ASI;

//* Operator can receive a call from SCR                         */

SCR_AppProfile:Target1_ASI = OperatorProfile:Oper_ASI;

//* AutoAttendant can hand off to FaxBack using "AA_HandoffTag"  */

AutoAttendantProfile:AA_HandOffTag = FaxBackProfile:FB_ASI;


Routing Rules Profile

The Routing Rules Profile:

•	defines call routing rules for inbound and outbound calls.

This example Routing Rules Profile:

•	route calls to either the application identified by the ASI AA_ASI or the application identified by the ASI Oper_ASI, depending on the line they come in on and the time of day.

•	route outbound calls to particular lines on the basis of time-of-day.

INBOUNDRULES {

//* AutoAttendant can only receive calls that are dialed in on 08001001 */

AA_ASI =

Date( Time(00:00-23:59) ),

CalledID( 08001001 );

//* Operator will receive any other calls during working hours            */

Oper_ASI =

Date( Time(08:00-18:00));

//* ... otherwise AutoAttendant will get any call                        */

AA_ASI =

Date( Time(00:00-23:59) );

}

OUTBOUNDRULES {

//* The line interface device "dxxxB1C1" will be preferentially selected  */

//* for outbound calls between 8am and 6pm                                */

dxxxB1C1 =

Date( Time(08:00-18:00) );

//* The line interface device "a_vendor_channel" can be used for outbound */

//* calls at any time                                                      */

a_vendor_channel =

Date( Time(00:00-23:59) );

}


AutoAttendant Profile

APPLICATION_SERVICE AA_ASI {

   GROUP_SET = AA_GroupSet;

   DEFAULT_CONFIGURATION = PRG;

   INBOUND_CALL_STATE = CONNECTED;

   OUTBOUND_CALL_STATE = CONNECTED;

   HANDOFF = AA_TargetASI RETURN;

};

GROUP_SET AA_GroupSet {

   PRIMARY_RESOURCE = MY_CCR;

   CCRONLY = NONE;

   PRD = MY_PLAYER + MY_SIGDETECTOR + MY_RECORDER;

   PRDG = MY_PLAYER + MY_SIGDETECTOR + MY_RECORDER + MY_SIGGENERATOR;

};

RESOURCES {

   MY_CCR = CCR_ECTF_ResClass : ( ANY );

   MY_PLAYER = Player_ECTF_ResClass : ( ANY );

   MY_SIGDETECTOR = SD_ECTF_ResClass : ( ANY );

   MY_SIGGENERATOR = SG_ECTF_ResClass : ( ANY );

   MY_RECORDER = Recorder_ECTF_ResClass : ( ANY );

};


FaxBack Profile

APPLICATION_SERVICE FB_ASI {

   GROUP_SET = FB_GroupSet;

   DEFAULT_CONFIGURATION = FAX;

   INBOUND_CALL_STATE = CONNECTED;

   OUTBOUND_CALL_STATE = CONNECTED;

 };

GROUP_SET FB_GroupSet {

   PRIMARY_RESOURCE = MY_CCR;

   CCRONLY = NONE;

   FAX = MY_FAX ;

   PRD = MY_PLAYER + MY_SIGDETECTOR + MY_RECORDER;

   PRDG = MY_PLAYER + MY_SIGDETECTOR + MY_RECORDER + MY_SIGGENERATOR;

};

RESOURCES {

   MY_CCR = CCR_ECTF_ResClass;

   MY_FAX = Fax_ECTF_ResClass;

   MY_PLAYER = Player_ECTF_ResClass;

   MY_SIGDETECTOR = SD_ECTF_ResClass;

   MY_SIGGENERATOR = SG_ECTF_ResClass;

   MY_RECORDER = Recorder_ECTF_ResClass;

};


Operator Profile

APPLICATION_SERVICE Oper_ASI {

   GROUP_SET = Oper_GroupSet;

   DEFAULT_CONFIGURATION = PLAYER_Only;

   INBOUND_CALL_STATE = CONNECTED;

   OUTBOUND_CALL_STATE = CONNECTED;

};

GROUP_SET Oper_GroupSet {

   PRIMARY_RESOURCE = MY_CCR;

   PLAYER_Only = MY_PLAYER;

};

RESOURCES {

   MY_CCR = CCR_ECTF_ResClass;

   MY_PLAYER = Player_ECTF_ResClass;

};


Appendix B - Stand-Alone Self Hosted Systems - Introduction
Introduction

The client/server communications mechanism for CT Server is based on WinSockets. WinSockets will be available in any client and host machine connected to a network. However, if the target platform is a stand-alone machine with no network connections a loopback driver must be installed.

IMPORTANT

A loopback driver must be installed in a stand-alone self hosted system prior to CT Media being installed.


Installing a Loopback Driver

To install a loopback driver:

1.	Click on the Start Button.  Choose Settings | Control Panel.

2.	Double-click on Network.  Click on the Adapters tab.

3.	Use the Remove function to remove all currently installed network adapter cards.

4.	Select "Add Adapter ..." and then select "MS Loopback Adapter" from the pulldown list of network adapter cards.

5.	Select "Continue".

After the loopback adapter has been installed, the Administrator must:

1.	Use Notepad to open the file \WINNT\System32\drivers\etc\hosts.

2.	Add the line:

127.0.0.1	<NameOfMachine>

For example:

127.0.0.1	TOROA

3.	Save the file, and exit Notepad.


How the CT Server Administration Application Works

This is a Windows NT application which allows the Server Administrator to monitor the status of the Server, and modify its configuration.

Start the CT Server Administration application:

1.	Click on the Start Button.

2.	Choose Programs | Dialogic CT Media Applications | CT Server Administration

Figure 11.  The Administration Application Window

More:


Figure 11.  The Administration Application Window


Making and Breaking the Admin/Server Application Link

Connecting to the Server (Logging on)

Disconnecting from the Server (Logging off)

Changing the Server Level

Server Level on Bootup


Connecting to the Server (Logging on)

Select:

Menu	Quick Key(s)	Toolbar
Server|Connect	Ctrl+C
and choose the name of the Server to connect to from the list. See Client/Server Link Configuration for instructions on how to add a remote Server entry to the list of Server connections.


Disconnecting from the Server (Logging off)

To disconnect from a CT Server select:

Menu	Quick key(s)	Toolbar
Server|Disconnect	Ctrl+D


Changing the Server Level

To change the operating level of the CT Server, select:

Menu	Quick key(s)	Toolbar
Server|Change Server Level	Ctrl+L	-

Table 13.  Server Levels

Select the level for the CT Server.

NOTE:	Changing the CT Server level is the recommended way to start and stop CT Media Services.  However, an Optional Service can fail to start up (and be marked as "Idle - Failed") and the Server Level will still move to the higher level.

You can choose Emergency Shutdown if the CT Server will not shut down to a lower level using a normal shutdown.

NOTE:	An Emergency Shutdown forces the shutdown regardless of the states of the Services and the CT Server, so it may be necessary to stop and restart the CT Server before you can change to a higher level.  If restarting the CT Server does not work, you may need to reboot.


Table 13.  Server Levels

Level	Description
1	Configurable - Can change the profiles and move the CT Server to a higher level. The Root Service provides all Level 1 functionality.
2	Mandatory Services Running - Mandatory Services will start when you move to Level 2. The Mandatory Services are the Core Service, DLGC_CoreService, and the ISE Service, DLGC_ISE.
3	Optional Services Running - Optional Services will be started when you move to Level 3. The CT Server has moved to Level 3 when all Optional Services are in either the 'Failed' or 'Running' state.
4	Connections Enabled The CT Server can handle client connections (Sessions). NOTE: Depending on your hardware, inbound calls may also be possible at Level 4.  Generally, it is assumed that inbound calls will be possible at Level 5.
5	Calls Enabled The CT Server can handle inbound calls.


Server Level on Bootup

When the CT Server starts up, it will automatically attempt to start to Level 5.  If you want to change the default bootup level, edit the value of the Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Dialogic\CTMS Server\CTMSboot\InitialLevel.

This key can be set from 1 to 5.


Client/Server Link Configuration

To connect to a remote server, you must configure your machine as a remote client.

NOTE:	You must have Administrator privileges to do this.

To configure the client/server link select:

Menu	Quick key(s)	Toolbar
Client|Edit Server Entries ...	-	-

The dialog box allows you to create a new Server Connection and shows all current Administration and Standard Connections, which can be edited or removed.

Administration Connection	a Server connection of this type can be administered using the Administration Application or the Administration APIs
Standard Connection	a Server connection of this type cannot be administered, but an application can use such a connection (Session) for call control, etc., via the CT Media APIs
To edit a current entry, select that entry in the list and choose Edit… or double-click on the entry.

NOTE:	You will get a similar interface when choosing New.

Server Name	The Server Name is arbitrary.  You can define your own Server connections. NOTE: All user-defined strings are case-insensitive, must start with an alphabetic character, and should be no more than 127 characters from the alphanumeric set and "_". The Server Name is also the name that the user must supply as an element of the KVSet OptArgs argument in the function CTses_Create( ). NOTE: CT Media applications use Default_Server by default.
Computer Name	Name of the machine hosting the CT Server.  This could be could be an IP address or resolvable host name
Port Number	Port number of the target CT Server Default values for CT Media: • 2020 = Administration Connection • 2019 = Standard Connection


Configuring the Server for Multinode

1.	Stop the CT Server.

•	Click the Start button

•	Choose Programs | Dialogic CT Media Applications | Server Start Stop, and use this utility to stop the Server.  See Appendix F - The Server Start Stop Utility User Interface for a description of this utility.

2.	In CT Server Administration, choose Server | Configure for multinode.  The following dialog box will appear:

Field	Description
Account	Enter the name of the Service account for the CT Server.
Password	Enter the password for that account
Container Path	Enter the UNC path where Containers will be located.   • Normally, the path will be \\ResourceComputer\cont


Appendix C - The CT Server Administration Application User Interface - View Options
View Options

Figure 12.  The View Menu

Table 14.  How CT Server Components are displayed by the Administration Application Table 14.  How CT Server Components are displayed by the Administration Application

Table 15.  CT Server Component Description

More:

Viewing Profiles

Viewing CT Media Services

Viewing Service Providers

Viewing the CT Server Status


Figure 12.  The View Menu


Table 14.  How CT Server Components are displayed by the Administration Application

	is displayed in this view...
this installed component	Service Providers	CT Media Services	Profiles
Core Services	X	X
System Call Router	X	X	X
Vendor-supplied boards (signal processing and telephony hardware and software)	X	X	X
Vendor-supplied applications			X
the Administrator can:	view only	add, remove, stop, start	add, remove, import, export, update


Table 15.  CT Server Component Description

Component	Purpose	Characteristics
Core Service Providers	Provide essential services to all applications.	Installed as part of the CT Server.
CT Media Services	Manages vendor-supplied software packages in support of a particular technology.	Can be installed and removed by the Administrator.
Profiles	Configuration information for boards and applications.	Provided by the creator of the board or application. Installed during board or application installation.


Viewing Profiles

To view installed profiles on a CT Server select:

Menu	Quick key(s)	Toolbar
View|Profiles	F2	-


Viewing CT Media Services

To view CT Media Services on a CT Server select:

Menu	Quick key(s)	Toolbar
View|CT Media Services	F3	-


Viewing Service Providers

To view Service Providers on a CT Server select:

Menu	Quick key(s)	Toolbar
View|Service Providers	F4	-


Viewing the CT Server Status

To view the status of a CT Server select:

Menu	Quick key(s)	Toolbar
View|Server Status	F10	-
The status will be displayed in the form of the Server Level, as defined in Section 3.3.  Levels of the Server.


Working With Profiles

This section deals with the mechanics of editing and maintaining Profiles.  Details of the contents of Application Profiles are covered in Chapter 1, Volume 1, Other CT Media Documents.Details of Resource Profiles are included in the CT Media RDK Guide.

NOTE:	Profile locking is not implemented in the current release; i.e., you could potentially change a profile simultaneously from two Administration Applications.  It is recommended that you avoid this, since the behavior is undefined.

Figure 13.  The Profile Menu

Figure 14.  A Profile Editor Window

Figure 15.  Profile Formats

NOTE:	When editing a profile, note that the text typed in may not have the same formatting and line length as the text which is seen after the profile has been parsed and then unparsed.

NOTE:	In profiles, any symbols that are not on the local client will be displayed as 32-bit numbers, not names.  The Symbol Table (\CTServer\ctmssym.tbl) is expected to be on the local machine.

More:

Creating New Profiles

Modifying Standard Profiles

Removing Profiles

Adding Profiles

Saving a Profile in IEF Format

Saving a Profile as Text

Managing Profile Editors

Associating an Editor With a Profile Class

Removing a Profile Editor

Selecting a Default Profile Editor


Figure 13.  The Profile Menu


Figure 14.  A Profile Editor Window


Figure 15.  Profile Formats


Creating New Profiles

NOTE:	These instructions are valid for profiles of type APPLICATION, ASIMap, or RoutingRules.  For other profile types, you will use the Generic Profile Editor.  See Appendix D - The Generic Profile Editor.

To create a new profile:

1.	Start the appropriate Profile Editor by selecting:

Menu	Quick key(s)	Toolbar
Profile|New	Ctrl+P
Choose the type of profile to be created from the drop-down list

2.	In the Profile Editor window, create the profile required.

3.	To clear the Profile Editor window, and begin editing a new profile, in the Profile Editor window select:

Menu	Quick key(s)	Toolbar
Profile|New profile	Ctrl+N
2.	In the Profile Editor window, store the new profile on the CT Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store	Ctrl+S
Enter the name of the profile on the Server and select "OK".

4.	Close the Profile Editor.

To create a new profile from an existing profile:

1.	Start a Profile Editor by selecting:

Menu	Quick Key(s)	Toolbar
View|Profiles	F2	-
and double clicking on the profile to be modified.

2.	In the Profile Editor window, edit the profile as required.

3.	In the Profile Editor window, store the modified profile on the Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store on server As...	-	-
Enter the name of the profile on the Server and select "OK".

4.	Close the Profile Editor.


Modifying Standard Profiles

NOTE:	These instructions are valid for profiles of type APPLICATION, ASIMap, or RoutingRules.  For other profile types, you will use the Generic Profile Editor.  See Appendix D - The Generic Profile Editor.

The easiest way to modify an existing profile on the CT Server is to:

Select:

Menu	Quick Key(s)	Toolbar
View|Profiles	F2	-
Double click on the profile to be modified, or choose Profile | Edit

NOTE:	Alternatively, you can edit an existing Profile by first starting a new Profile.

Select

Menu	Quick key(s)	Toolbar
Profile|New	Ctrl+P
Enter a type of profile to be edited in the dialog box.

Once the Profile Editor window is open, retrieve the profile you want to edit from the CT Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Retrieve from server ...	Ctrl+R
Select the name of the CT Server the profile is stored on and click on "OK". Then select the profile to be retrieved and click on "Retrieve".

2.	In the Profile Editor window, edit the profile as appropriate.

3.	In the Profile Editor window, store the modified profile on the Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store	Ctrl+S
NOTE:	The Profile Checker (see Checking a Profile ) will be automatically run.  If there is a syntax error in the profile, you will receive a message like the following:

a)	Fix the error.

b)	Store the Profile again.

NOTE:	For an Application Profile, the Profile Checker does not check whether there is more than one Group Configuration of the same name in a GroupSet. The last one listed is the one that is actually used.

4.	Close the Profile Editor.

The Profile Checker performs syntax checking only.  For example, the Attributes in a Resource Specification Expression are not parsed by the Profile Parser.  If you change Resource Attributes in a valid Profile, for safety you should check the e_cores log file to confirm that the CT Media Server accepted the Profile.


Removing Profiles

To remove (delete) a profile from the server:

1.	Select:

Menu	Quick Key(s)	Toolbar
View|Profiles	F2	-
Select the profile to be removed.

2.	Select:

Menu	Quick Key(s)	Toolbar
Profile|Remove ...	Del


Adding Profiles

If the profile is in Import/Export Format (*.ief):

1.	Select:

Menu	Quick key(s)	Toolbar
Profile|Import	-
2.	Specify the file name of the profile (including the full path name) and the name it will have in the Server.

If the profile is an unparsed file in ASCII text format (*.prf):

1.	Start the appropriate Profile Editor by selecting:

Menu	Quick key(s)	Toolbar
Profile|New	Ctrl+P
Enter the type of profile to be edited in the dialog box.

2.	In the Profile Editor window, import the profile text by selecting:

Menu	Quick key(s)	Toolbar
Profile|Import from Text File...	-
Enter the name of the profile text file, and select "Open"

3.	In the Profile Editor window, store the imported profile on the Server by selecting:

Menu	Quick key(s)	Toolbar
Profile|Store	Ctrl+S
Enter the name of the profile on the Server and select "OK".

4.	Close the Profile Editor.


Saving a Profile in IEF Format

To save an installed profile to disk in IEF format:

1.	Select:

Menu	Quick Key(s)	Toolbar
View|Profiles	F2	-
and select the profile to be saved.

2.	Select:

Menu	Quick Key(s)	Toolbar
Profile|Export Profile...	-
Select the drive, the directory and enter the file name to hold the profile text. Select "OK".


Saving a Profile as Text

NOTE:	These instructions are valid for profiles of type APPLICATION, ASIMap, or RoutingRules.  For other profile types, you will use the Generic Profile Editor.  See Appendix D - The Generic Profile Editor.

To save an installed profile to disk as text:

1.	Start a Profile Editor and view the profile by selecting:

Menu	Quick Key(s)	Toolbar
View|Profiles	F2	-
and double clicking on the profile to be saved.

2.	In the Profile Editor window select:

Menu	Quick Key(s)	Toolbar
Profile|Export as Text File	-
Select the drive, the directory and enter the file name to hold the profile text.

Select "Save".

3.	Close the Profile Editor.


Managing Profile Editors

The CT Server Administration Application provides 4 profile editors. By default, three of these editors are associated with the three basic profile classes, and will be started automatically when the user asks to edit a profile of that class. These are shown in Table 16.  The CT Server Administration Application Profile Editors.

Table 16.  The CT Server Administration Application Profile Editors


Table 16.  The CT Server Administration Application Profile Editors

Editor	Profile Class	Description
appedit.exe	Application	Application Profiles - text based
asimaped.exe	ASIMap	ASI Map Profiles - text based
routedit.exe	RoutingRules	Routing Rules Profile - text based
prfedit.exe	Any	Default editor - KVSet based


Associating an Editor With a Profile Class

To associate a profile class with a particular editor:

1.	Select:

Menu	Quick Key(s)	Toolbar
Profile|Associate ...	Ctrl+A	-
2.	Select a profile class.

3.	Select an editor from the list of current editors or use "Browse" to add a new editor.

4.	Select "OK".


Removing a Profile Editor

To remove a Profile Editor:

1.	Select:

Menu	Quick Key(s)	Toolbar
Profile|Associate ...	Ctrl+A	-
2.	Select an editor from the list of current editors.

3.	Select "Remove".


Selecting a Default Profile Editor

If a profile class is not associated with an editor, then when the user asks to edit it the default editor will be used. To change the default Profile Editor:

1.	Select:

Menu	Quick Key(s)	Toolbar
Profile|Change default editor ...	-	-
2.	Enter the full path name of the new default editor.

3.	Select "OK".


Checking a Profile

The CT Server Administration application includes a profile checker.   This checks both for incorrect syntax and unresolved references; e.g.; if the profile refers to a GroupSet which is not defined within that profile.


Accessing the Profile Checker

You can:

1.	check all profiles on the Server

2.	check a profile that you are editing

3.	check a profile that you are saving

More:

Checking all Profiles

Checking one profile

Automatic profile checking


Checking all Profiles

From the CT Server Administration application, you can check all profiles currently stored on the Server:

1.	Choose View | Profiles (if you are not already viewing profiles)

2.	Choose Profile | Check all profiles... (or the Check Profiles button on the Toolbar)

3.	Select the appropriate Server

The Profile Checker will display the results:


Checking one profile

While you are editing a profile, you can check it with the Profile Checker:

1.	Choose Edit | Check Profile...

2.	Select the appropriate Server

The Profile Checker will display the results, as in Checking all Profiles.


Automatic profile checking

The CT Server Administration Application will automatically run the Profile Checker whenever you store a profile.

If there is an error, you will see a Profile Checking Results window such as in Checking all Profiles.  If the profile is correct, no message will be displayed.

NOTE:	The Profile Checker checks a defined range of syntax errors in Profiles, but it cannot check all the errors which might cause CT Media to reject a Profile.  If you have added or modified a Profile and stored it, you may wish to check in the e_cores log file to confirm that the CT Media Server accepted the Profile.  Otherwise, if CT Media rejected the Profile, you will get CT_errorBadProfile when you try to build a Group using that Profile.


Managing CT Media Services

Figure 16.  The "CT Media Services" Menu Figure 16.  The "CT Media Services" Menu

More:

Adding a CT Media Service

Editing a CT Media Service

Removing a CT Media Service

Starting a CT Media Service

Stopping a CT Media Service


Figure 16.  The "CT Media Services" Menu


Adding a CT Media Service

To add a CT Media Service to the CT Server:

1.	Select:

Menu	Quick Key(s)	Toolbar
Service|New ...	Ctrl+S
There are two types of CT Media Service:

If you choose the Executable Service, you will see the following dialog box:

Field	Description
Service Name	The name the CT Media Service will be known by on the CT Server.  All user-defined strings are case-insensitive, must start with an alphabetic character, and should be no more than 127 characters from the alphanumeric set and "_". NOTE: The CT Media Service name is used to identify the profile used by the CT Media Service.  Thus, the CT Media Service name must be exactly the same as the Profile Name (specified in CTadm_AddProfile()), or the CT Media Service cannot start.
Command Line	The path and name of the CT Media Service executable, including any runtime arguments (see Section Service Logging Switches and Log File Names) NOTE: You can only browse for the executable name if you are logged into the "LOCAL" CT Server, not the default "Default_Server".
Machine Name	Defaults to the local machine. If multinode processing is desired, this field should be set to the name of the remote machine that this Service is to be run on.  The remote machine must be a Resource Node (i.e., set up as a Resource Node at installation of CT Media)..
Processor	The Processor this Service will be run on.  By default, any new Service will run on the first processor. NOTE: CT Media starts numbering processors at 1, whereas NT starts numbering at 0.  However, if you specify process 0, CT Media will default to the first processor rather than returning an error. If this Service is unable to be bound to a specified processor, a warning message shall be logged to the e_ndmgr.txt log file.
Service Type	The effect of different service types are defined in Section 3.3.  Levels of the Server
Start Timeout	The amount of time, in seconds, the Service has to start. If the timeout is exceeded, for all types of Services, the Service will go to a Fail State.  Further, for a mandatory Service, the CT Server will return to Level 1. Use any positive integer, or the following: • 0 to try once, but don't wait to try again • -1 to try forever NOTE: This timeout affects the Service when it is in Starting mode only.  If the Service has to wait for other dependencies in "Waiting" mode, CT Media will time out the Service in about 2-3 minutes.
Emergency Shutdown Timeout	The time, in seconds, that the Service has to perform an Emergency Shutdown.  If the timeout is exceeded, CT Media will shut down the Service. • -1 means that the timeout is infinite.
Exit Timeout	The amount of time, in seconds, the Service has to stop  Use any positive integer, or the following If the timeout is exceeded, CT Media will change the Service Status to Failed. • 0 to try once, but don't wait to try again • -1 to try forever.
Max Restarts	The number of times the EXE Service can be restarted after hangs or crashes.   Use any positive integer, or the following: • 0 means the EXE Service cannot be restarted • -1 means there is no limit to the number of restarts
If you choose the DLL Service,  you will see the following dialog box:

Field	Description
Service Name	The name the CT Media Service will be known by on the CT Server.  All user-defined strings are case-insensitive, must start with an alphabetic character, and should be no more than 127 characters from the alphanumeric set and "_". NOTE: The CT Media Service name is used to identify the profile used by the CT Media Service.  Thus, the CT Media Service name must be exactly the same as the Profile Name, or the CT Media Service cannot start.
DLL Path	The path to the DLL NOTE: You can only browse for the executable name if you are logged into the "LOCAL" CT Server, not the default "Default_Server".
Service Type	The effect of different service types are defined in Section 3.3.  Levels of the Server
Arguments	Any runtime arguments (see Section Service Logging Switches and Log File Names)
Process Name	The name of the process in which the service is to be run. Multiple DLL services can be run within the same process. • If Process Name is left empty, the DLL service will be added to a default DLL process.
Emergency Shutdown Timeout	The time, in seconds, that the Service has to perform an Emergency Shutdown.  If the timeout is exceeded, CT Media will shut down the Service. • -1 means that the timeout is infinite.
Link/Unlink DLL...	Optimizations which affect the speed of startup/shutdown of your DLL Service. • Link Early - if checked, the DLL is linked as soon as possible.  If unchecked, the DLL is linked just before the Service is started, which will slow down startup. • Unlink Late - if checked, the DLL is unlinked as late as possible.  If unchecked, the DLL is unlinked immediately after the Service is stopped, which will slow down shutdown. NOTE: To replace a DLL while the server is running, you must uncheck the Unlink Late checkbox before stopping the DLL Service.
CAUTION

The Service must be local to the Server.  The Administration Application will allow you to add a remote Service, but that Service cannot be run.


Editing a CT Media Service

NOTE:	Make sure that all CT Media Services are stopped (i.e. Ready, not Running) before you edit any CT Media Service.

To edit the information for a CT Media Service:

1.	Select:

Menu	Quick key(s)	Toolbar
View|CT Media Services	F3	-
Select the CT Media Service to be edited.

Either double-click on the CT Media Service, or select:

Menu	Quick key(s)	Toolbar
Service|Edit	-	-
The interface is like the one for Adding a CT Media Service.

Change any information that you need to change.

NOTE:	If you rename a CT Media Service, make sure you do not enter any spaces into the name, or an error will result and the CT Media Service will be removed.


Removing a CT Media Service

To remove a CT Media Service from the CT Server:

1.	Select:

Menu	Quick key(s)	Toolbar
View|CT Media Services	F3	-
Select the CT Media Service to be removed.

2.	Select:

Menu	Quick Key(s)	Toolbar
Service|Remove	Del


Starting a CT Media Service

CAUTION

It is strongly recommended that you use the Server Levels (see Changing the Server Level) to start CT Media Services, unless you know exactly what you are doing.

To start a CT Media Service:

1.	Select:

Menu	Quick Key(s)	Toolbar
View|CT Media Services	F3	-
2.	Select the CT Media Service to be started, and then select:

Menu	Quick Key(s)	Toolbar
Service|Start	-
3.	In order to check that the CT Media Service's status has changed from "Idle" to "Running", use F5 to update the window.

CAUTION

The Service must be local to the Server, or it will not start.


Stopping a CT Media Service

CAUTION

It is strongly recommended that you use the Server Levels (see Changing the Server Level) to stop CT Media Services, unless you know exactly what you are doing.

To stop a CT Media Service:

1.	Select:

Menu	Quick Key(s)	Toolbar
View|CT Media Services	F3	-
2.	Select the CT Media Service(s) to be stopped, and then select:

Menu	Quick Key(s)	Toolbar
Service|Stop	-
3.	In order to check that the CT Media Service's status has changed from "Running" to "Idle", use F5 to update the window.


Appendix D - The Generic Profile Editor - Introduction
Introduction

The Administration Application supplies specific Profile Editors for profiles of Application, RoutingRules, and ASIMap profile classes.  You can create your own profiles of other classes by using the Generic Profile Editor.

NOTE:	You cannot import/export a Generic Profile from the Generic Profile Editor.  If you need to do this, select the Generic Profile in the View | Profiles window in the Administration Application.


Starting the Generic Profile Editor

Open the Generic Profile Editor:

1.	Choose Profile | New.

2.	Overwrite the default profile class, typing in the class that you want.

3.	Choose the Server that this profile is meant to reside on.  This is important for checking the Symbols you use in your profile.

4.	Once you have chosen the Server, the Generic Profile Editor will open.

The "keys" icon at the top left in the editing window represents the KVSet which is the Profile that you are editing.  A full list of icons is in Table 17:  Generic Profile Icons.

Table 17:  Generic Profile Icons

More:


Table 17:  Generic Profile Icons

Symbol	Means…
	KVSet
	Key or CTsymbol Value
	String
	(Signed) Integer
	Unsigned integer
	Float
	Range
	Boolean
	Array


Editing a Profile

From the Profile menu, you can choose Retrieve Profile from Server to open an existing profile for editing, or you can choose New to create a new profile.

NOTE:	Whether you are creating a new profile or editing an existing profile, remember that the profile is simply a KVSet that you are adding CT Media values into.  This is indicated in the top left corner of the editing screen with the "master key" icon, which represents a KVSet.

HINT:	You can also access the Generic Profile Editor from the View | Profiles screen in the Administration Application by double-clicking on an existing Generic Profile; i.e., one not of class Application, RoutingRules, or ASIMap).

More:

Adding entries into a Generic Profile

Editing Current KVPairs

Cutting, Copying, Pasting

Copying to a text file

Deleting


Adding entries into a Generic Profile

1.	Select the object within which you want to add another object.

NOTE:	For a new profile, the KVSet which represents the profile is already selected.

2.	Choose Edit | Create Object…  (or right-click or double-click for the same result) and select the type of object you want to create.  For a definition of these types, see Section 8.2, CT Media API Reference, Volume 1.  For example, to add an integer:

3.	You will be prompted to enter the relevant values for the Key and Value of the KVPair that you are creating.  The Key must be a valid Symbol on the Server that you chose for this Profile.

4.	You can enter the Key and choose OK to edit the Value, or you can choose to edit the Value first using the Edit Value button, then go back to enter the Key.

5.	If you have entered a valid object, it will be added onto the profile display.

This display indicates that you have a profile (KVSet) with one KVPair in it.  This KVPair has Key Container_ECTF_WriteSize and Value 2345.


Editing Current KVPairs

You can edit KVPairs that you have already entered by

•	double-clicking either the Key or the Value, or

•	selecting a Key or Value and choosing  Edit | Properties

and changing the values as desired


Cutting, Copying, Pasting

You can save time when editing your profile by cutting, copying and pasting items by selecting them and using the appropriate commands in the Edit menu.

NOTE:	You cannot do a complete copy.  You will be prompted to re-enter the value of the Key for the KVPair you are copying.  In many cases this is advantageous, since you cannot have two KVPairs with the same Key in one KVSet.


Copying to a text file

If you select an item in your profile, you can copy it and paste it as text information into a text editor.

For example, if you select and copy the main profile KVSet icon (top left "master keys"), you can see the entire contents of your profile in KVSet form by pasting it into a text editor.


Deleting

You can delete items in the Profile by selecting the Key of the KVPair and using the Delete key or choosing Edit | Delete.


Saving a Profile

Once you are done editing a profile, you can store it on the Server.

1.	Choose Profile | Store on Server As… or the Store icon.

2.	Make sure that the information about the Profile is as you want it.

3.	Choose Store.

The profile will now be viewable from View | Profiles in the Administration Application.  (You may need to refresh the view.)


Appendix E - The Container Manager User Interface - Introduction
Introduction

Dialogic provides a utility for managing CT Media Containers.  See Chapter 5, CT Media API Reference, Volume 1, for more information on Containers.

More:

Description

Functional Overview


Description

The Container Manager has a GUI interface which is very similar to the File Manager in Windows™, making Container administration straightforward.

The Container Manager will allow you to create and otherwise manipulate Containers needed for your applications without having to use the Container API functions.

The Container Manager will also recognize and manipulate Containers and Data Objects of vendor-specific types if they have been implemented correctly as described in the CT Media Container Developer's Guide and Reference.


Functional Overview

The Container Manager will allow you to:

•	Create Containers

•	Delete Containers

•	Rename Containers (but not just by changing the case of the name)

•	Import files as Data Objects into Containers

•	Export Data Objects to files

•	Back up Containers

•	Restore from an existing backup


Using the Container Manager

NOTE:	These instructions assume that you have successfully installed CT Media, and that the CT Server is running.

To start the Container Manager application:

1.	Click on the Start Button.

2.	Choose Programs | Dialogic CT Media Applications | Container Manager

Choose Server | Connect to Server, or use the Connect icon, to connect to the CT Server.  We will connect to the default server, Default_Server.

NOTE:	For better performance when there are large numbers of Containers, the default view will be set to List.  Different views, including Details, are available; see the section on View Options.

You can see the contents of each Container by selecting it.

Double-click on the Root Container icon to expand the contents of Root.

NOTE:	When you have large numbers of Containers (i.e., greater than 100), some Container Manager procedures may take a noticeable amount of time.  In these cases, progress text will be displayed in the progress bar on the bottom right.  During these procedures, Container Manager is not multitasking.


Creating a new Container

You can create a new Container in any existing Container.

1.	Select the "Sample:" Container.

2.	Choose Edit | Create Container (or click on the Create icon on the toolbar).

3.	Enter the name of your new Container; i.e., "Test".  This will create a new Container within Sample, i.e., "Sample:Test:".


Data Objects

Copying/moving Data Objects between Containers

Putting Data Objects into Containers

Storing Data Objects

Data Object Details


Copying/moving Data Objects between Containers

You can copy Containers and Data Objects from one Container and paste them into another Container using Edit | Cut/Copy/Paste in the standard Windows™ Clipboard.

You can also "drag-and-drop" Containers and Data Objects between Containers.

•	Using the left mouse button to drag will move the Container/Data Object to its new location.  (Control + Left Mouse Button will copy.)

•	Using the right mouse button will give you a choice of moving or copying.

NOTE:	"Drag-and-drop" is faster for copying, but the Clipboard can be pasted between multiple Container Manager applications.

CAUTION

Keep your Container full names less than 128 characters.  Complex Container structures may crash the Server.


Putting Data Objects into Containers

You can import an existing file as a Data Object into a Container.

1.	Select the "Sample:Test:" Container that was created in Section Creating a new Container.

2.	Choose Media | Import or use the Import icon on the toolbar.

The Data Object will be created in the "Sample:Test:" Container.


Storing Data Objects

Data Objects can be exported from their Containers into a file.

1.	Select a Data Object in a Container.

2.	Choose Media | Export or use the Export icon on the toolbar.

3.	Select a filename, and choose OK.


Data Object Details

If you are viewing the data objects in a Container in List View and you want to see the details of one particular data object, you can:

1.	Select the Data Object

2.	Press Alt-Enter

This will show you the details for the selected object.

NOTE:	If you have a large number of Data Objects (i.e., greater than 100) this method will be quicker than switching to Details View, which will show the details of all Data Objects.


Container Backup and Restore

Backup

Restore


Backup

To store all the contents of a Container into a file:

1.	Select the Container

2.	Choose Media | Backup.

3.	Select the file in which the backup should be stored.


Restore

To restore the contents of a Container from a file:

1.	Select the Container to which you want to restore information.

2.	Choose Media | Restore.

3.	Select the file to restore.


Appendix E - The Container Manager User Interface - View Options
View Options

You can view the Containers and Data Objects at various levels of information.

From the View Menu (or the toolbar) you can choose from:

•	Large icon view

•	Small icon view

•	List view

•	Detail view

You can also sort the Data Objects within Containers by

•	Name

•	Type

•	Size

•	Date Created/Modified

NOTE:	The Container Manager view windows do not automatically update.  To update the view, on the View menu, choose Refresh, or press F5.

	This is a Windows NT applet which starts up and shuts down the CT Server.


How The Server Start Stop Utility Works

To start the Server Start Stop application

1.	Click on the Start Button.

2.	Choose Programs | Dialogic CT Media Applications | Server Start Stop

 This will cause one of the indicator icons shown below to be displayed.


Starting Up the CT Server

If the CT Server is stopped, the Server Start Stop application should show a red sign. If the sign is green, the CT Server is already started.

Click on the Start button. A dialog box will appear indicating the Server is starting. The Server will start to level 5, meaning that only disabled CT Media Services will not start.

Figure 17.  Server Starting

When startup is complete the sign will change to green, and the button will change to Stop.

More:


Figure 17.  Server Starting


Shutting Down the CT Server

If the CT Server is running, the Server Start Stop application should show  a green sign. If the sign is red, the CT Server is already stopped.

Click on the Stop button. A dialog box will appear, indicating that the CT Server is shutting down, and in a few seconds  the red sign should appear with the option to start the CT Server.

Figure 18.  Server Stopping

After 1 minute, if the CT Server has not stopped, you will be prompted either to wait or to force an emergency shutdown of the CT Server.

Generally, choosing to wait will soon result in a normal shutdown.  Otherwise, you can choose to use the Emergency Shutdown, which forces the shutdown regardless of the states of the Services and the CT Server.

More:


Figure 18.  Server Stopping


About the CT Media Event Viewer

The CT Media Event Viewer displays the contents of an Event Log which contains all Events sent by CT Media components while the CT Server is running.

NOTE:	Events regarding the CT Server itself are generally sent to the Windows NT Event Viewer.


Starting the Event Viewer

To start the Event Viewer:

1.	Click on the Start Button.

2.	Choose Programs | Dialogic CT Media Applications | Event Viewer

The Event Viewer Window (with some sample Events) is pictured below:

Events are initially listed in the order logged.  You can sort Events by category using the standard Microsoft convention of clicking in the column heading that you want to sort by.

NOTE:	Because the time stamping of an event is done independently by the different producers, events (when received by the logger) may be out of order in the Event Viewer.


Event Information

Each event that is logged has the following information on the Event Viewer window.

Date and Time	The Date and Time as stamped when the Event was produced
Source	The generator of the Event.  This will be identified by a string made up of processName, library ID and [SP address] of the Event generator
Severity	The severity of the Event: • Alarm -  Indicates unusual critical or fatal situations • Error -  Mainly operating system errors • Warning -  Indicates a problem but the software /hardware can continue operating • Informational -  Just to log a message. Each classification also has an icon at the left edge of the window.
Class	All events shall specify the class of that event.  The class is a user-defined string. Some examples of classes are: • Driver • Library • CT Media
Identifier	The Event ID. NOTE: Currently, the Event ID is simply assigned based on the Severity of the Event.  It is assumed that eventually Event generators will supply unique Event IDs.
Node	The name of the machine generating the Event. NOTE: This may not appear for all Events.
NOTE:	Additional data on an Event may be available by selecting the Event and pressing Enter or choosing View | Detail.  The details will look similar to the figure below.


Filtering Events

When Event Viewer is first started, all logged Events will display.  You can filter Events on particular criteria:

Choose View | Filter Events

Field	Description
From	Choose the range of Events you wish to display.  You can choose to display from the first logged Event to the last, or vary the start and end date.
Severity	Choose which level of Events to view
Source	You can sort on Events from one Source
EventID	You can sort on Events with a particular Event ID
Class	You can sort on Events with a particular Class


Changing Event Log Settings

You can change the settings of the Event Log itself by choosing File | Log Settings.

Field	Description
Maximum Log Size	Sets the maximum size in Kb for the Event Log.
Event Log Wrapping	Determines how overwriting of old Events will be handled.  Either 1. the oldest Events will be overwritten when the maximum size is reached; or 2. the oldest Events will be overwritten after a specified number of days (up to a maximum of 365)


Puzzling Symptoms - Possible Causes

Symptom	You may have...
You change your Application Profile, then calls fail to be connected	• forgotten to change the RoutingRules Profile and/or the ASIMap Profile to use the changes you made to your Application Profile
Your designated \temp directory has extra files in it after CT Media installs	• These files can be deleted or ignored.
CT Media fails to upgrade	• forgotten to uninstall Dialogic Resource Packages.  CT Media cannot be uninstalled while these packages are present.
CT Media fails to uninstall	• forgotten to uninstall Dialogic Resource Packages.  CT Media cannot be uninstalled while these packages are present.
In a multinode installation, DLGC_ISE Service fails to start but DLGC_CoreService starts successfully	• forgotten to give Administrator privileges to the CTMS service in the Server Node.
In a multinode installation, the Server Start Stop Utility fails to start the Server	• mistyped the account name or password for the CTMS Service account - check this in Control Panel | Services
In a multinode installation, DLGC_HardwareManager and all other hardware services fail to start up.	• mistyped the account name or password for the CTMS Service account - check this in Control Panel | Services • If CTMS service is running properly in the Resource Node, you may have forgotten to give Administrator privileges to the CTMS service. You need to add the access privilege to the account it is running on and start the service.
In a multinode installation, DLGC_HardwareManager started properly but some or all hardware services (e.g. Analog, Inband) failed to start.	• forgotten to share the Container directory on the Resource Node
In a multinode installation, during installation onto the Resource Node, a dialog reporting "The system log is full" appears.	• forgotten to share the CTServer directory on the Server Node • entered a wrong machine name for the Server Node during the installation.  Quit the install application and run "unintal.exe" provided in the CD install disk.  Rerun the installation.
Services hang, or do not start or stop as expected at the appropriate Server Level	• used the Service | Start or Service | Stop functions to stop a Mandatory Service without changing the Server levels appropriately.  To recover, you should shut down the Server to Level 1
The Server Level will not shut down below Level 4	• left CT Media Applications running
Symbols show up as numbers, not names	• forgotten to copy the Symbols to the local client
When adding a Service, you cannot browse for the path to the Service executable	• logged into the default "Default_Server", instead of the "LOCAL" CT Server
You cannot replace a DLL while the CT Server is running	• checked the Unlink Late checkbox in the Edit DLL Service dialog.  This must be unchecked.
You can view CT Media help files, but not the rest of the documents	• chosen not to install Adobe Acrobat.  See Section 2.4.  Viewing Documentation.
Your application, which is set to start automatically when the CT Server starts, always fails	• forgotten to handle the failure condition of a client application starting when the Server is at Level 1.  See Section 5.5.  Starting Applications.
Your inbound calls are always dropped	• defined an ASI in your inbound routing rules for an application that cannot take the inbound call.  If the inbound routing rules indicate the call should go to that application, no other application will get the call.
The Profile Parser returns an error	• forgotten to include at least one rule for each ASI in your InboundRules section and OutboundRules section • forgotten a semicolon at the end of a line or block • forgotten braces around a block in an Application Profile • misspelled a key word • entered an invalid value for a Date/Time parameter in the SCR_RoutingRules profile • used a range for a device name in the SCR_RoutingRules profile; i.e., dxxxB1C1-4
When using the Performance Monitor, an Object is not showing valid values	• selected an Object which requires that a particular instance to be chosen in order to show valid values
The CT Server will not move successfully to a higher level	• performed an Emergency Shutdown to a lower level.  This can leave the Server in a state which requires you to stop and restart the Server before continuing.
You cannot browse for the executable name when entering a Service	• logged onto a Server other than the "LOCAL" Server.  You can only browse if you are logged onto the local machine.
You have set the Start timeout for a Service, but it still takes several minutes to time out	• The Start timeout only applies to the Service in the Starting state.  If the Service has to wait for other dependencies in the Waiting state, only the CT Server can time the Service out.
CT Media runs very slowly, Services consistently time out on startup, or calls take a very long time to begin ringing	• insufficient hardware resources to run CT Media.  We recommend  • a Pentium 200 (minimum 133) processor • 64 Mb (32 minimum) of RAM
CT Media services crash for no apparent reason	• insufficient memory or disk space


Copyright notice

© Dialogic, an Intel company, 1999

This document is copyrighted and all rights are reserved by Dialogic. This document may not, in whole or in part, be reduced, reproduced, stored in a retrieval system, translated, or transmitted in any form or by any means, electronic or mechanical, without the express written consent of Dialogic. The contents of this document are subject to change without notice.  Every effort has been made to ensure the accuracy of this document.  However, due to ongoing Product improvements and revisions, Dialogic cannot guarantee the accuracy of printed material after the date of publication nor can it accept responsibility for errors or omissions.  Dialogic will publish updates and revisions to this document as needed.

The software referred to in this document is provided under a Software License Agreement.  Refer to the Software License Agreement for complete details governing the use of the software.


Trademarks

DIALOGIC ® is a registered trademark of Dialogic, an Intel company. D/41E, CT Media and CT Server are trademarks of Dialogic, an Intel company.
Windows NT and Notepad are registered trademarks of Microsoft Corporation.
Intel is a registered trademark of Intel Corporation.

Technical Support
Phone: 973-993-1443
Fax: 973-993-8387
BBS: 973-993-0864

Email: CustEng@dialogic.com

For Sales Offices and other contact information, visit our website at http://www.dialogic.com

Publication Date: October, 1999

CT Media Group,

Open Switch

Dialogic (NZ)


Glossary

 ACT

 ADSI

 AIA

 AnswerDemo

 Application

 Application Context Token

 Application Interface Adapter

 Application Profile

 Application Service Block

 Application Service ID

 ASI

 asynchronous mode

 Attribute

 Call Routing

 Catch tag

 Client/Server Link

 Completion Event

 Computer Telephony Media Services

 Computer Telephony Media Services SDK

 Computer Telephony Server

 Container

 CT Media SDK

 CT Media Service

 CT Server Database

 CT Server

 CTtranInfo

 Data Object

 DTMF

 Event

 Event handler

 Event queue

 first party call control

 glare

 Group

 Group handoff

 Group Information

 Group owner

 Group return

 Group Set Block

 Key

 Key Value Pair

 Key Value Set

 KVPair

 KVSet

 Object

 Parameter

 Phone address

 Primary Resource

 profile

 RAS

 Replaceable Service Provider

 Resource Allocation Service

 Resource

 Resource Attribute

 Resource Parameter

 Resource Profile

 Resources Template

 routing rules

 RTC

 runtime control

 SCR

 SCR Application Profile

 SCR Profile

 secondary Resource

 Service

 Session

 SMP

 Symbol

 synchronous mode

 System Call Router

 Telephony Service Provider

 third-party call control

 Time Varying Media

 TranInfo

 TTS

 TVM

 Unsolicited Event


 ACT

Application Context Token - This is a 32 bit value commonly used to store pointers to context information or indices into a context array.  The value of an ACT is user-defined.  There is a Session ACT, which is a standard KVPair in all Events, and there is a Group ACT, which can be attached by specifying the ACT when calling some of the Group API functions.


 ADSI

(Analog Display Services Interface) A Bellcore standard defining protocol on the flow of information between something (e.g., a switch, a server) and a subscriber's telephone, PC, or other communicating device with a screen.


 AIA

Application Interface Adapter - This is the interface and translation layer between the CT Media APIs and the CT Server.


 AnswerDemo

A sample application supplied with the CT Media SDK.  This application simulates the behavior of a simple answering machine.


 Application

A software program designed to perform a certain function.


 Application Context Token

See ACT.


 Application Interface Adapter

See AIA.


 Application Profile

A file to be created by the application developer which contains application configuration information. This profile will usually be supplied in text format.  Application profiles must be added to the CT Server before the application is started.  When these profiles are added, they are automatically parsed into a format which is readable by the CT Server.


 Application Service Block

The section of the Application Profile which specifies the call routing requirements of the application.  This information is used by the SCR for call routing.


 Application Service ID

See ASI.


 ASI

A CT Media-standard or user-defined string to identify an Application's services for Group handoff purposes.  The ASI is defined in the Application Service Template in the Application Profile.


 asynchronous mode

Interrupted functionality.  An application calling a function in asynchronous mode can call other functions before the first function completes.  Termination information on functions which are called asynchronously can be returned to the application via a handler function.  Alternatively, the application can poll for the termination events.


 Attribute

(or Resource Attribute) is a feature or capability of a CT Media Resource.  Specific Attributes can be requested when defining Resource requirements in the Application Profile.


 Call Routing

This can mean any of the following 1. Directing an inbound telephone call to a particular application. 2. Directing an outbound call from an application to a particular line on the telephone network. 3. Passing a call from one application to another.


 Catch tag

A user-defined identifier used in call handoff and return between cooperating applications.


 Client/Server Link

The communications path established between the client machine and the CT Server.


 Completion Event

This is an Event which is the direct result of an API function call.  Most commonly, this is a completion Event for a function which has been called asynchronously.  The completion Event for an asynchronous function will contain the same information as the TranInfo structure does for the same function called synchronously.


 Computer Telephony Media Services

(CT Media) - Dialogic's S.100 based computer telephony server product.


 Computer Telephony Media Services SDK

See CT Media SDK.


 Computer Telephony Server

See CT Server.


 Container

A logical vessel holding one or more Data Objects.  Analogous to a file system or directory.


 CT Media SDK

Dialogic's Software Development Kit for developing S.100-compliant applications and resources.


 CT Media Service

See Service


 CT Server Database

Configuration information stored on the CT Server. Includes Service configuration information, and board and resource profiles.


 CT Server

Dialogic's software platform for running Computer Telephony Applications in a client-server environment. The Dialogic CT Server enables the development of computer telephony applications and core signal processing technologies, such as speech recognition and audio compression, in an object oriented, client-server environment.


 CTtranInfo

This is a defined structure for encapsulating Event information for presentation to an application.  The standard Event information is extracted from its KVSet and made more accessible through the CTtranInfo structure.  See also TranInfo.


 Data Object

A Data Object consists of TVM data and a set of attributes (which describes the properties of the data).  Data Objects reside in Containers, in a manner analogous to a file within a file system or directory.


 DTMF

(Dual Tone Multi Frequency) Telephony term for tone dialing as opposed to rotary dialing.


 Event

A special type of message used to notify the application of a noteworthy occurrence.  Event information is delivered to and from the CT Server in a Key Value Set (KVSet), and is packaged into a CTtranInfo structure for presentation to applications.


 Event handler

Part of application code which handles received unsolicited Events.


 Event queue

Each application's Session has an Event queue where received Events wait to be processed.


 first party call control

The situation where an application issues call control commands while being a party in the "conversation."


 glare

Going offhook to make an outbound call, but instead of dial tone, there is an inbound call.


 Group

A logical collection of Resources.  CT Media Resources can only be accessed indirectly through the Group which contains them.


 Group handoff

The process which occurs when an application is finished with a Group and specifically directs the Group to another application.


 Group Information

This is a KVSet with specific information about a Group.  The KVPairs in the Group Information KVSet are entirely user-defined.


 Group owner

The owner of a Group is the Application (or Application's Session) who has control of the Group.   The original owner of a Group is the Session which created the Group.  The ownership will change if the Group is transferred, returned, or handed off.


 Group return

The process which occurs when an application is finished with a Group and allows it to return to another application (determined by the previous flow of control of this Group).


 Group Set Block

The section of the Application Profile which specifies the grouping of Resources required by the application.  This information is used by the SCR when the application requests a Group.


 Key

The identification portion of a Key Value Pair.  A Key is always a CTsymbol.


 Key Value Pair

See KVPair.


 Key Value Set

See KVSet.


 KVPair

A data structure consisting of a key and an associated value; similar to a variable.


 KVSet

A data structure consisting of an unordered list of Key Value Pairs.


 Object

In terms of CT Media and Object-Oriented Programming, an Object is one of the various "services" which is accessed using the CT Server.  This includes the System Services (e.g., Session) and the Resources (e.g., Player).  Thus, a CTsymbol is of format Object_VENDOR_Item, where Object is as defined here.


 Parameter

(or Resource Parameter)  This is a defined KVPair, the value of which may either be read to find out information about a Resource, or altered to modify the behavior of a Resource.


 Phone address

The phone number as specified in the SCR Profile. This can be a complete or partial number, without or without wildcard characters.


 Primary Resource

The Resource in a Group which carries out the communication within the Group.  Any secondary Resources in the Group can communicate with each other only through the primary Resource, not directly to each other.  The primary Resource must be specified in the Group Set section of the Application Profile.


 profile

A file that specifies an object's configuration and requirements. Profiles exist for the System Call Router, for applications, and for resources.  Profile information is parsed and added during installation.  The CT Server uses this information during runtime.


 RAS

See Resource Allocation Service.


 Replaceable Service Provider

A Service Provider that can be added or removed from the CT Server. Usually used to support a technology-specific board, or a particular type of application. See Service Provider.


 Resource Allocation Service

The System Service which handles the allocation of Resources.


 Resource

An abstraction of the standardized interfaces of a physical device used for call processing.  For example, a Signal Generator Object is a Resource.


 Resource Attribute

See Attribute.


 Resource Parameter

See Parameter.


 Resource Profile

A file containing configuration information for a board. Resource Profiles are added to the CT Server before the service that the board provides is started.


 Resources Template

The section of the Application Profile which specifies which Resources are required by the application and how those Resources are to be configured.  This information is used by the SCR when the application requests a Group.


 routing rules

The rules, maintained by the Systems Administrator, which instruct the SCR how to direct calls to applications.


 RTC

(or runtime control) is the mechanism by which one Resource can affect the behavior of another during runtime, using defined conditions and actions.


 runtime control

See RTC.


 SCR

The System Call Router is a  System Service which provides the basic necessities of inbound and outbound call processing and call sharing to client applications, without those applications needing to worry about the underlying telephony interface operations.


 SCR Application Profile

The file that contains configuration information for mapping types of boards to inbound and outbound telephone calls.


 SCR Profile

The file that contains configuration information for mapping inbound and outbound telephone calls to applications. It also contains information for transferring calls between applications.


 secondary Resource

A Resource in a Group which is not the Primary Resource.  The secondary Resource can only communicate with the Primary Resource, not with the other secondary Resources in the Group.


 Service

Unit of CT Media functionality - corresponds to an NT Service offering Operating System functionality


 Session

A Session is a logical binding between an application and the CT Media Services.  This binding provides a context for the delivery of CT Media Services.


 SMP

System Messaging Protocol - the message transport mechanism used within an S.100 Server.


 Symbol

An enumerated constant used for KVSet Keys and other identifiers.  A Symbol is of type CTsymbol and in format Object_VENDOR_Item.


 synchronous mode

Uninterrupted functionality.  An application calling a function in synchronous mode will not receive control back until the function completes.


 System Call Router

See SCR


 Telephony Service Provider

(TSP)  The TSP is the piece of software that provides a call control API which the SCR uses to perform call control on a network interface device.  The TSP is capable of communicating with the actual device to pass on requests from the SCR to the device and pass back events from the device to the SCR.


 third-party call control

Call control in which the controller of the call is not necessarily a party in the "conversation."


 Time Varying Media

See TVM.


 TranInfo

This is a standard argument passed with most of the CT API functions.  TranInfo is a structure of type CTtranInfo.  It is used to return information about the progress and status of the API function call.


 TTS

(Text to Speech) Conversion of textual (ASCII) information into synthetic speech output.


 TVM

TVMs are encapsulations of atomic pieces of time-varying media such as voice data.  When a CTrcdr_Record() is performed, the record goes into a TVM, which is stored in a Container.


 Unsolicited Event

Any Event which is not a Completion Event.  Unsolicited Events are not a direct result of a function call.