|
|
This chapter discusses the relevant .ini files that you can view and edit to determine and set operational parameters for the uOne system. The .ini files reside in the <uOne directory>\parms directory. This chapter discusses the following .ini files:
The SSMWI resource module provides message waiting notification behind the Cisco CallManager. This configuration file specifies information about the devices to be managed by the resource module, as well as stations serviced by those devices. This file is found in the following location: C:\CiscoSystems\uOne\parms\SSMWI.ini.
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 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.
[SSMWI]Step 1 Manually modify the SSMWI.ini file in the uOne\parms directory with values applicable to your installation.
| Attribute | Description | Valid Values and Defaults |
|---|---|---|
Specifies the number of devices to be managed by the resource module. | Default: none Valid values: 1-8 Example: 2 | |
Section name entry for each supported device. | Number is 0 based (i.e., MaxDevices=2 =>Device0, Device1) | |
Name of the CiscoVoice Mail device as configured in the respective CallManager. | Default: none Example: CiscoMWI-VI1 Note Not the same device as the UM access device. | |
Name of the CallManager host to which the device should be connected. | Default: none Example: CiscoHost | |
The number to be dialed to turn on the message waiting indicator as configured in the respective CallManager. | Default: 9001 Example: 8047629001 | |
The number to be dialed to turn off the message waiting indicator as configured in the respective CallManager. | Default: 9002 Example: 8047629002 | |
Enables remapping of the station number prior to delivery of the MWI request, via regexp/DialMap functionality. Note The DialMap.ini configuration file should contain an MWI configuration section to use this feature. | Default: Off Valid values: Off, On Example: On | |
A range of stations for which a specific device services MWI requests is identified by this entry. Two stations, a start and a stop station, are to be identified with a white space separator. The numbers may be any sequence of numbers (up to 33 digits) made up of the signals [0123456789]. The number of digits in the start and stop numbers must be identical. Multiple station entries may be specified for each device. | Default: 1000 9999 Examples: 8047625000 8047626000 7625000 7626000 5000 6000 |
The information you enter in this file is also used when you configure Call Manger devices using the Device Wizard. It is extremely important that the information in both places matches.
Step 1 Open the SS.ini file in the C:\CiscoSystems\uOne\parms directory.
Step 2 Scroll to the bottom of the file and check the following parameters:
| Attribute | Description | Valid Values and Defaults |
|---|---|---|
The number of ports (DS0s) to be supported by the resource module. | Default: none Valid values: encrypted code Example: UD2S45HI73GB | |
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: none Example: SS.Radvision.ini | |
The starting port number used for establishing RTP connections. | Default: none Valid values: 1000 - 9999 Example: 7000 | |
Interval at which RTP transmissions occur (msec) for silence compressed encoding (SilenceCompression=On). Note that the VendorConfig file, as well as the gateway, will need to be configured accordingly. | Default: 20 Valid values: 20 - 200 Example: 30 | |
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). | Default: 0 Valid values: 0 - 5000 (msec) Example: 100 | |
URL for the container used for 'beep' functionality in record operations. Notes:
| Default: none Example: file:///system/440beep.wav | |
Identifies whether silence compression will be used in processing RTP data. This setting needs to be coordinated with the codec setting on the gateways in which the server will be deployed (i.e., for Cisco - VAD/NoVAD). | Default: none Valid values: On, Off | |
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/ | Default: None Valid values: None, CalledParty, CallingParty, CallType Example: CalledParty CallingParty |
Step 3 Save the file and close it.
uTel logs can be found at: <uOne directory>\logs. The files include: uTel.dbg and uTel.err, and can be viewed using Notepad.
Step 1 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 following lines:
[DBG]| Attribute | Description | Example |
The system will log informational messages for the specific modules listed. It can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DLFcns, DLS, DM, EXE, GAMMA, GRP, H323, ISUP, LHTTSB, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SAMPLE, SCBUS, SCR, SES, SM, SSMWI, SOCK, SRV, TIMERS, TNTMAIN, TRAN, VCS ALL can be used to log informational data on all available modules. | SS SSMWI | |
The system will log warning messages for the specific modules listed. It can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DLFcns, DM, EXE, GRP, H323, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SCR, SES, SM, SSMWI, SOCK, SRV, TIMERS, TNTMAIN, TRAN ALL can be used to log informational data on all available modules. | ALL | |
The system will log error messages for the specific modules listed. It can list multiple modules consecutively and delimit them by spaces. The modules include: CNT, CON, DIG, DLFcns, DM, EXE, GRP, H323, MEDIA, MON, PKTBUS, QUEUE, RES, ROUTING, RSP, RTC, SCR, SES, SM, SSMWI, SOCK, SRV, TIMERS, TNTMAIN, TRAN ALL can be used to log informational data on all available modules. | ALL |
Step 2 Save the file and close it.
It is important to check that the LDAP configurations in the file are correct.
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 the sample below:
[UM4Config]| Attribute | Description | Valid Values and Defaults |
|---|---|---|
BillingLogging | Logs call details into the BillInfo.<yymmdd> file. | On, Off Default = Off |
Debug | Sets debug logging level. Set to 0 for no debug logging; set to 15 for highest level of logging. | 0 - 15 Default = 0 |
MailProtocolDebug | Sets mail protocol debug logging. | On, Off Default = On |
The Notifier section is aimed at debugging uLite. The values for the Debug key 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 cases. The Notifier section look like:
[Notifier]The next listing shows a sample uOne log file. The file's lines contain the following information:
Here is the sample uOne log file:
14:13:00.859000|TEL|SENT| [1 LOGIN UM4 pass]The DialMap.ini file contains the dialing plans for your installation. Check the file as follows:
Step 1 Change the Return Values to your 3-digit area code and 3-digit exchange.
Step 2 In the [SKINNYCALLTYPE:VoiceMail] section, change FromRegEx to the pilot number for voice mail for your system to reflect the 4-digit or 5-digit dialing plan.
Step 3 In the [SKINNYCALLTYPE:Forwarded] section, change Constraint to the pilot number for your system to reflect the 4-digit or 5-digit dialing plan.
Step 4 Save the file and close it.
Example for 4-digit dialing plan:
[SKINNYCALLTYPE:VoiceMail]Example for 5-digit dialing plan:
[SKINNYCALLTYPE:VoiceMail]
Posted: Wed Jun 21 03:57:20 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.