Table of Contents

The SSMWI.ini File

Modifying the SSMWI.ini File.

The SS.ini file

Modifying the SS.ini File

The uTel.ini File

Modifying the uTel.ini File
Logging

The uOne.ini File

Modifying the uOne.ini File

The DialMap.ini File

Sections of the DialMap.ini File
Modifying the DialMap.ini File

The LogRemover.ini file

Modifying the LogRemover.ini File

The .ini Files

This chapter discusses the relevant configuration files utilized by the uOne system for the purpose of administration and operational tasks. During the uOne installation, you were required to configure uOne by editing the SS.ini, SSMWI.ini, and DialMap.ini files to work with your system. The configuration files for uOne can be viewed and edited to determine and set operational parameters to further administer the uOne system. The .ini files reside in the C:\CiscoSystems\uOne\parms directory. The following .ini files are discussed in this chapter.

• The SSMWI.ini file.

• The SS.ini file.

• The uTEL.ini file.

• The uOne.ini file.

• The DialMap.ini file.

• The LogRemover.ini file.

The .ini configuration files specify information about the devices to be managed by the resource module, as well as stations serviced by those devices. A device refers to an Internet Protocol-enabled resource that can communicate with the IP-PBX (CallManager). This resource includes IP telephones, gateways, specialized devices such as Media Termination Point, or H.323 devices like Cisco AS5300 Access Server.

The SSMWI.ini File

The SSMWI resource module provides message waiting indicator (MWI) notification behind the Cisco CallManager. This file is found in the C:\CiscoSystems\uOne\parms\ directory.

A sample file appears below and shows the configuration information within a hierarchy of sections, denoted by [SectionName] headers. The top level section [SSMWI] specifies the number of devices to be managed by the resource module.

Each device section represents a Cisco voice mail device connected to a CallManager IP PBX. Multiple devices/multiple CallManagers are supported by the resource module. For each device specified, there is a mandatory section specifying configuration information for that device.

Modifying the SSMWI.ini File.

To open the C:\CiscoSystems\uOne\parms\SSMWI.ini file, use the following steps. Table 1-1 lists the attributes for this file. The "Configuring uOne" chapter of the uOne Installation and Configuration, Corporate Edition 4.1 guide gives the exact procedures for modifying the SSMWI.ini file.

Step 2 Select the Run menu in the popup menu.

Step 3 Type in Wordpad, and press OK.

Step 4 From within Wordpad, select Open from the File menu, and navigate to C:\CiscoSystems\uOne\parms\SSMWI.ini.

Step 5 After reviewing or editing the file, click the Save button and close the file.

Table 1-1: SSMWI.ini File Attributes

Attribute	Description	Valid Values and Default
MaxDevices	Specifies the number of devices to be managed by the resource module.	Valid values: 1 - 8 Default: 1 Example: 2
[DeviceX]	Section name entry for each supported device.	Number is zero based. Example: MaxDevices=2 =>Device0, Device1
CMDeviceName	Name of the MWI Cisco Voice Mail device as configured in Cisco CallManager.	Default: CiscoMWI-VI1 Example: CiscoMWI-VI1
CMHostName	Name of the CallManager Server for which the given device provides message waiting notification services. This name is entered during the uOne installation process.	Default: none Example: CallManagerHost
CMMWIOnNumber	The number to be dialed to turn on the message waiting indicator as configured in the respective CallManager.	Default: 9001 Example: 2198
CMMWIOffNumber	The number to be dialed to turn off the message waiting indicator as configured in the respective CallManager.	Default: 9002 Example: 2199
Stations	A range of stations for which a specific device services MWI requests. Two stations, a start and a stop station, must be identified, with a white space separator. The number of digits in the start and stop numbers must be identical. Multiple station entries may be specified for each device.	Valid values: Any sequence of numbers (up to 33 digits), made up of the signals [0123456789] Default: 0000000000 9999999999 Example: 8045558989 8045557878
MWIMapping=On	Enables remapping of the station number prior to delivery of the MWI request, via regexp/DialMap functionality. Note The DialMap.ini configuration file contains an MWI configuration section to use this feature.	Valid value: On, Off Default: On Example: On

The SS.ini file

The information you enter in the SS.ini file is also used when you configure CallManager devices using the Device Wizard.

Note It is extremely important that the information for the CMHostName and CMDeviceName values in the C:\CiscoSystems\uOne\parms\SS.ini file match the comparable settings in the CallManager Device Wizard.

Modifying the SS.ini File

To open the C:\CiscoSystems\uOne\parms\SS.ini file, use the following steps. Table 1-2 lists the attributes for this file. The "Configuring uOne" chapter of the uOne Installation and Configuration, Corporate Edition 4.1 guide gives the exact procedures for modifying the SS.ini file.

Step 2 Select the Run menu in the popup menu.

Step 3 Type in Wordpad, and press OK.

Step 4 From within Wordpad, select Open from the File menu, and navigate to C:\CiscoSystems\uOne\parms\SS.ini.

Step 5 After reviewing or editing the file, click the Save button and close the file.

Table 1-2: SS.ini File Attributes

Attribute	Description	Valid Values and Defaults
CMHostName	Network host name for the CallManager system used for uOne. This value is inserted during installation.	Example: CallMgrBox
CMDeviceName	"Base name" for CallManager devices supported by the SS.ini resource module. This setting needs to be coordinated with names used in CallManager Device Wizard. A CallManager device will be created for each configured uOne port using the base name and a numeric value. For example, if uOne is configured for four ports and CMDeviceName=CiscoUM, then the CallManager devices created are CiscoUM-VI1, CiscoUM-VI2, CiscoUM-VI3, CiscoUM-VI4.	Default: CiscoUM
MaxPorts	The number of ports (DS0s) to be supported by the resource module. This value is inserted in encrypted code during installation and should not be edited. If the MaxPorts is not a valid value, uTel will not start and calls will not be answered by uOne.	Default: 5d452f3R2U3C1C38 Valid values: encrypted code Example: UD2S45HI73GB
StateDef	Identifies the name of the state machine script used for signaling control of the SS interface. These files are located in $Cisco/parms/state.	Default: SS.SkinnyState.ini Example: SS.SkinnyState.ini
RtpStartPort	The starting port number used for establishing RTP connections.	Valid values: 10000 - 99999 Default: 18000 Example: 7000
SilenceCompression	Identifies whether silence compression will be used in processing RTP data. This setting needs to be coordinated with the SilenceSuppressionWide/ SilenceSuppressionWithGateways settings on CallManager. (For example, for SilenceSuppression=On, set CallManager settings to SilenceSuppressionSystemWide=T and SilenceSuppressionWithGateways=T.)	Valid values: On, Off Default: On
RecordTrim	Amount of time to trim off the end of recorded phrases terminated by DTMF (via hangup or end of data). Intended to squelch DTMF energy which may pass in the audio stream before the tone is detected (seconds).	Valid values: 0 - 5000 (msec) Default: 200 Example: 100
RecordBeepContainer	URL for the container used for beep functionality in record operations. Note Only .WAV file formats are currently supported for this feature. Note This file should also be present in the [CONTAINER] section of the uTel.ini file as a system cached file.	Default: file:///system/1kbeep_c.wav Example: file:///system/440beep.wav
SkinnyCallInfoMapping	Enables remapping of the Skinny Client Protocol CalledParty, CallingParty, CallType fields via regexp/DialMap functionality. Note that the DialMap.ini configuration file should contain SKINNYCALLEDPARTY/ SKINNYCALLINGPARTY/ SKINNYCALLTYPE configuration sections to use this feature.	Valid values: None, CalledParty, CallingParty, CallType Default: CallingParty, CalledParty, CallType Example: CalledParty CallingParty
DNISToken	Value used as a flag when debugging the uTel service.	10-digit number Default: 0000000000

The uTel.ini File

The uTel.ini file indicates the level of logging which is being performed. uTel logs can be found at C:\CiscoSystems\uOne\logs. The files include uTel.dbg, uTel.XXXXXXXX.out, and uTel.XXXXXXX.err, each of which can be viewed using Wordpad. The log level for the uOne system can be set or cleared through the [DBG] section of the uTel.ini file.

Caution Use caution when setting the logging for the various components of uOne since logging can directly impact the performance of the messaging system. Logging should only be used for a short term to troubleshoot issues or problems with the uOne system. The logging should be returned to a false state after troubleshooting your system.

Modifying the uTel.ini File

To open the C:\CiscoSystems\uOne\parms\uTel.ini file, use the following steps. Table 1-3 lists the attributes for this file.

Step 2 Select the Run menu in the popup menu.

Step 3 Type in Wordpad, and press OK.

Step 4 From within Wordpad, select Open from the File menu, and navigate to C:\CiscoSystems\uOne\parms\uTel.ini.

Step 5 After reviewing or editing the file, click the Save button and close the file.

You can change the log level by editing the C:\CiscoSystems\uOne\parms\uTEL.ini file. The default log level provides no logging. If you want logging, edit the lines shown in Figure 1-3 below.

The parameters available for setting the level of logging in the uTel.ini file are listed in Table 1-3.

Table 1-3: uTel.ini File Attributes

Attribute	Description	Example
TRACE	The system logs all function entry and exit points with associated arguments and/or return values. Because the Trace settings utilize the maximum debugging options, use extreme caution when setting the debug value. Be sure to return the Trace value to nothing after troubleshooting to avoid problems with your system resources, such as disk space consumption and extra processing for logging leading to poor system performance. You can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DM, EXE, GRP, MAP, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SCHEMEFILE, SCR, SES, SM, SS, SS_RTP, SSMWI, SOCK, SRV, TIMERS, TRAN, URLPARSE	SS
INFO	The system logs informational messages for the specific modules listed. You can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DM, EXE, GRP, MAP, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SCHEMEFILE, SCR, SES, SM, SS, SS_RTP, SSMWI, SOCK, SRV, TIMERS, TRAN, URLPARSE The value ALL can be used to log informational data on all available modules.	SS SSMWI DM
WARN	The system logs warning messages for the specific modules listed. You can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DM, EXE, GRP, MAP, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SCHEMEFILE, SCR, SES, SM, SS, SS_RTP, SSMWI, SOCK, SRV, TIMERS, TRAN, URLPARSE The value ALL can be used to log informational data on all available modules.	ALL
ERROR	The system logs error messages for the specific modules listed. You can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DM, EXE, GRP, MAP, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SCHEMEFILE, SCR, SES, SM, SS, SS_RTP, SSMWI, SOCK, SRV, TIMERS, TRAN, URLPARSE The value ALL can be used to log informational data on all available modules.	ALL

Logging

The uTel server is comprised of many different modules. Each module has its own independent log setting, configurable by listing its 'debug token name' in one of the four key entries above. For instance, to see all informational logging for the uTel System Call Router, or SCR, the DBG section should be

Any number of modules may be listed for a given key entry, separated by a space. The token ALL signifies all uTel modules for the given key entry. The recommended run-time deployment configuration is all warning/error messages turned on as shown in Figure 1-3 .

A list of the possible modules which might be included in one of the four key entries is shown in Table 1-4.

Table 1-4: uTel Debugging Modules

Debug Module	Description
CNT	Container Manager. In accordance with S100, the Container Manager provides a file abstraction layer for the telecom server. Directories/files are referred to as containers. All audio files used for play/record purposes are handled by the container manager. In order to track processing of audio files, turn on MEDIA, CNT, and SCHEMEFILE.
CON	Connection Manager. Individual resources/resource types are connected together in a group under control of the connection manager in accordance with S100.
DIG	Digit Manager. Once a call reaches the connected state, all detected DTMF tones are passed to the digit manager for processing. Turn this module on to see what is happening with DTMF collection requests, or you suspect DTMF tones are not getting through to the application.
DM	Dial Map. The DialMap facility is used for remapping of tokens (primarily call tokens) as configured in the DialMap.ini file. Turn this module on if you are experiencing 'upper level menu', and/or having problems executing outdial requests.
EXE	Execution Manager. This module governs the overall processing loop of the telecom server.
GRP	Group Manager. Resources are allocated to a group as necessary to provide a given functionality (i.e play, record, digit collection) in accordance with S100. Once resources are allocated to a group, telephony requests are executed against it under control of the group manager. Scarce resource types (i.e. text to speech) may be dynamically added/removed from a group while a call is active. A group is typically destroyed/resources freed at the end of a given call.
MAP	Memory Map facility. Memory mapped files are used by the uTel server for reading/writing of audio files. They are also used for mapping of internal data structures to enable monitoring of these structures by an external 'viewing' process.
MEDIA	Media Manager. The media manager is used for management of audio related containers, i.e. create a container for recording, set .wav header information, etc. In order to track processing of audio files, turn on MEDIA, CNT, and SCHEMEFILE.
MON	Monitor Manager. This module manages memory mapping of link lists (specifically sessions/groups) for external viewing.
*PKTBUS	Packet Bus Resource Module. This is the plugin which enables connecting of resources within a group.
QUEUE	Queue Manager. TAP requests to be processed internally within the server may be placed in a queue for execution. One example of this is in group destruction, in which requests to 'stop' each of the resources within a group are queued prior to freeing the resources/destroying the group. Turn this module on if you suspect problems in freeing resources/destroying groups.
RES	Resource Manager. All resources (play, record, call channel, dtmf detectors, message waiting notification, etc) are registered with the resource manager at system initialization. As calls are processed, resources are 'checked out' of the resource manager and allocated to groups as required. Turn on this module to track allocation of resources to groups during call processing.
ROUTING	Routing Facility. Call tokens are used to find a given application (application service identifier) for processing a call via the routing facility.
RSP	Response Block Facility. TAP is the protocol used for submitting application client requests to the uTel server. TAP is also used internally within the server for various modules to communicate with one another. For each TAP request to be processed, a response block is created, in which response return code/status/data is stored. Turn this module on to track TAP transaction processing.
RTC	Run Time Control. Run time controls enable specific actions to be taken on detection of a given condition within a group in accordance with S100. A good example would be stop a play (action) on dtmf detection ( condition). Run time controls are 'installed' by the application client at the beginning of and/or throughout the duration of a call. Turn this module on to track RTC condition/action processing.
SCHEMEFILE	File access for URLs with file scheme. This module implements operating system specific file calls, i.e. fstat(), open(), read(), etc. In order to track processing of audio files, turn on MEDIA, CNT, and SCHEMEFILE.
SCR	System Call Router. The system call router is used to manage call processing in the uTel server. The SCR is responsible for creating groups on detection of inbound calls, and may also be used for group creation for placing of outbound calls. Additionally all call processing related requests (answercall, dropcall, transfercall, etc) are preprocessed by SCR. Far end drop events are managed by the SCR as well. Turn this module on to track call processing in the uTel server.
SES	Session Manager. Applications create a session for interacting with the server after login. Groups are created with the desired resources and placed in the session. Groups contain all the resources necessary to process a given call; one or more groups may be allocated to a given session (two groups in a given session are used for call bridging functionality). Turn this module on to track closely an application's interaction with a given session - SES logs provide uTel control layer timing for any given task
SM	State Machine Facility. Call processing events/requests are handled by a state machine built from a text file description. Turn this module on if you are experiencing call processing problems, or suspect a 'hung channel' problem.
SOCK	Sockets. The application client interface is a string based protocol, TAP (telephony access protocol), carried over TCP sockets. Each client connects to the uTel server port 5000 for client/server interaction. Turn this module on to monitor client transactions. Additional modules to turn on for monitoring transactions are TRAN and SRV.
SRV	Server Module. Interface module from which client requests are read, client responses written. Turn this module on to get a 'black box' view of an application's interaction with the server.
SS	Skinny Station Resource Module. This is the uTel server plugin which implements the Skinny Station Protocol. All uOne/CallManager signaling messages originate/are received from this module.
SSMWI	Skinny Station Message Waiting Indicator Module.
SS_RTP	Skinny Station Resource Module Real Time Protocol. All RTP read/writes may be logged by turning on this module. This module generates a gargantuan amount of log traffic - keep an eye on your hard disk with this module turned on.
TIMERS	Timer Facility. A timer facility is provided to manage api timeouts, client inactivity timeouts, dtmf collection timeouts, and more.
TRAN	Transport Layer. Module used by the SRV module to interface with sockets transport. Turn this module on to monitor client transactions. Additional modules to turn on for monitoring transactions are SOCK and SRV.
URLPARSE	URL Parsing Facility. Audio files to be played/recorded are referenced by URLs. Turn this module on if you suspect invalid URLs are causing problems with play/record operations.

The uOne.ini File

The uOne.ini file contains the preferences and settings for the uOne messaging application. The only sections of the uOne.ini file which should be manually reviewed or revised are the [LDAPConfig] and the [UM4Config] sections.

It is important to check the LDAP configurations found in the [LDAPConfig] section of the uOne.ini file for accuracy to your system setup.

You can edit the uOne.ini file to turn on debug logging and to log Call Details. The default log level provides no logging. The system logs Call Details into the BillInfo.<yymmdd> file. If there is a problem found, edit the following lines in the [UM4Config] section, as shown in Figure 1-5.

[UM4Config]

BillingLogging=On

Debug=15

MailProtocolDebug=On

The Notifier section of the uOne.ini file focuses on debugging uLite. The values for the Debug attribute range from 0 to 15. The setting of 1 is the minimal (yet quite useful for most cases). The setting of 15 gives maximum debug information at the cost of significantly slowing down the system. The setting of 1 should be adequate for most debugging purposes. When debugging uLite, the Notifier section is shown as:

[Notifier]

Debug=1

---

Note Using the Debug logs in uOne.ini typically resolves 80% of the problems with the system. If you still do not resolve the problem, use the debug logs in uTel and then uLite.

---

Modifying the uOne.ini File

To open the C:\CiscoSystems\uOne\parms\uOne.ini file, use the following steps. Table 1-5 lists the attributes for this file which can be adjusted for debugging purposes.

Step 2 Select the Run menu in the popup menu.

Step 3 Type in Wordpad, and press OK.

Step 4 From within Wordpad, select Open from the File menu, and navigate to C:\CiscoSystems\uOne\parms\uOne.ini.

Step 5 After reviewing or editing the file, click the Save button and close the file.

Table 1-5: uOne.ini Attributes

Attribute	Description	Valid Values and Default
BillingLogging	Logs call details into the BillInfo.<yymmdd>file.	Valid values: On, Off Default: On
Debug	Sets debug logging level. Set to 0 for no debug logging; set to 15 for highest level of logging.	Valid values: 0 - 15 Default: 0
MailProtocolDebug	Sets mail protocol debug logging.	Valid values: On, Off Default: Off.

The DialMap.ini File

The DialMap.ini file contains the dialing plan configurations for your installation of uOne. Since default settings are placed in the DialMap.ini file for pilot numbers and some return values, you need to modify this file to conform to your dial plan. See the "Configure uOne" chapter of the uOne Installation and Configuration, Corporate Edition 4.1 manual for specific instructions.

The uOne installation includes sample .ini files for use in configuring 4-digit or 5-digit dialing plans. These sample .ini files can be found in the C:\CiscoSystems\uOne\parms directory. The default DialMap.ini file for uOne is configured for 4-digit dialing. The following information describes the sections of the Dialmap.ini file and their purpose.

Sections of the DialMap.ini File

The DialMap.ini file consists of a hierarchy of sections used in determining the mapping of calls for the uOne system. The title of each section reflects the purpose of the section and lists the rules to be used for that section as separate expressions. These expressions call the sections using the same title along with the rule name describing the particular procedure that the section performs. The body of the section contains multiple lines of expressions requiring a value to be utilized by the uOne system during operation.

Calls which utilize the DialMap utility typically provide two values---a From and a To value. You should use the Unix syntax expression format when implementing or manipulating specific values. The following Table 1-6 describes in detail the expressions used in a section.

Table 1-6: Description of DialMap Settings

Expression	Description	Example Values1
FromRegExp	The From value received from a call to the DialMap utility.	.* ^([0-9]{10})$0$ ^(1001)$0$
ToRegExp	The To value received from a call to the DialMap utility. Since not all sections require a To expression, "None" should be used as the value for the attribute.	None ^([0-9]{10})$0$
Constraint	Unix syntax expression typically against subexpressions from FromRegExp or ToRegExp. If no constraint is desired, enter None. $f0 refers to $0 in the FromRegExp $t0 refers to the $0 in ToRegExp Valid subexpression range is $f0 to $f9, and $t0 to $t9	None ($f0 !=1001)
Return	Return value to be supplied to the caller consisting of a freeform string (size 64). Subexpressions from FromRegExp and ToRegExp may be used in constructing return strings. Valid return values for SkinnyCallType sections are: D - Direct call (subscriber access) A - Send all calls B - Busy N - No answer	804762$f0 A

1This value differs depending upon the particular procedure the DialMap is performing. Examples given are not necessarily representative of default values to be used.

Modifying the DialMap.ini File

The "Configuring uOne" chapter of the uOne Installation and Configuration, Corporate Edition 4.1 guide gives the exact procedures for modifying the DialMap.ini file. The information in Figure 1-6 lists only partial examples of the file.

The LogRemover.ini file

The LogRemover.ini file contains the settings to schedule the periodic cleaning of log files from your uOne system. The LogRemover.ini file is located in the C:\CiscoSystems\uOne\parms\ directory.

Modifying the LogRemover.ini File

To open the LogRemover.ini file in C:\CiscoSystems\uOne\parms, use the following steps. Table 1-14 lists sample attributes to check for this file.

Step 2 Select the Run menu in the popup menu.

Step 3 Type in Wordpad, and press OK.

Step 4 From within Wordpad, select Open from the File menu, and navigate to C:\CiscoSystems\uOne\parms\LogRemover.ini.

Step 5 After reviewing or editing the file, click on the Save button and close the file.

Posted: Tue Jun 13 11:49:03 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.