Table of Contents

Installing the Product from the CD-ROM
Contents
Introduction
System Requirements

Hardware Requirements
Software Requirements

New and Changed Information

Upgrading to a New Software Release

UM41 Application
OAM&P
CMA (TNT)

Feature Set Table

Caveats for Release 4.1S
Documentation Updates

General
Errors
Omissions

Service and Support
Cisco Connection Online

Release Notes for uOne for Release 4.1s

December 1999

These release notes support Cisco's uOne Release 4.1s. They describe new features, memory requirements, hardware support, software platform deferrals, and documentation changes, errors or omissions.

For a list of the software caveats that apply to Release 4.1s, see the Caveats section of this document. The caveats are updated for every maintenance release and are located on the uOne documentation site of CCO, as well as the uOne product CD-ROM.

Installing the Product from the CD-ROM

Prior to installation, verify that your system is configured with the proper partitioning, file systems and operating system packages and upgrades. This information can be found in the Gateserver Installation and Configuration Manual.

To install the software for the uOne product from the CD-ROM:

Step 1 Close all applications and active windows.

Step 2 Insert the uOne, 41S CD into the CD-ROM drive on your machine.

Step 3 Open a terminal window.

Step 4 Become superuser.

Step 5 Change directories to /cdrom/uone_411s

cd /cdrom/uone_411s

Step 6 Type the command ls at the command line to list the files in the current directory.

Step 7 Issue the following command as superuser:

sh uc-411s-install-solaris26.sh uc-411s-<mulaw>-solaris26.pkg

The following prompt displays:

Do you wish to continue with the installation of Cisco's Unified Communications Software? (yes/no)

Step 8 After confirming that you would like to continue with the installation process, the system will specify the locations where it will search for the software.

1. Local $REL bundle

2. CDROM bundle /mnt/$REL

(The /mnt/$REL file is actually /cdrom/uone_411s)

3. Local /var/spool/dist in pkg file system format

Step 9 After confirming, once again, that you would like to continue with the installation, you will be prompted to answer the following questions:

Do you wish to install Base Services plus UM? (yes/no) "

(If yes, answer the following)

- Will you be using ALAW or MULAW prompts?

- Will you be using North American Dialing prompts?

Which of the following applications do you wish to install

1. Subscriber Web Administration Packages (UMSA/PMA)

2. MWI Application

3. SMS Application

4. None of the above

Choices: 1 2 3

Hit return to continue or the interrupt key to exit installation.

Step 10 Upon completion, a summary of the packages installed and their status will appear.

Step 11 Exit superuser. At the command line, return to the root directory and type eject. Remove the CD and store it in a safe place.

Contents

These release notes discuss the following topics:

• Introduction

• System Requirements

• New and Changed Information

• Caveats

• Documentation Updates

• Service and Support

• Cisco Connection Online

Introduction

The Cisco uOne is a versatile Unified Communications solution that allows subscribers to send and retrieve messages anywhere, at any time, using any device. The solution is built on a three-tiered architectural model:

• Access Tier

• Application Tier

• Backend Tier

The Access Tier is composed of Cisco Remote Access Server hardware and Voice Gateways that handle incoming calls to the system. The Application Tier is composed of Cisco's uOne platform and software; the application tier performs all the messaging functions inherent in the solution. The Backend Tier provides database storage for subscriber information and messages.

For information on new features supported by Release 4.1s, refer to the "New and Changed Information" section.

System Requirements

This section describes the system requirement for Release 4.1s and includes the following topics:

• Hardware Requirements

• Software Requirements

Hardware Requirements

Table 1 lists the hardware requirements for the Access, Application and Backend Tiers of the uOne solution; the Gateway (AS5300), Gatekeeper (3620), Gateserver (uOne Platform and Applications), Ethernet switch, Directory (LDAP) and Messaging (IMAP) servers.

Component	Unit	Mode/Nomenclature
Gateway	Chassis	AS5300 Dial Shelf
	Modem Carrier	AS53-CC-MCOM Microcom Carrier Card - needed only when using fax
	Modem Module	AS53-12MCOM Microcom 12 Port Modem Module - needed only when using fax
	VoIP Feature Card	AS53-T1-24VOX Two (2) 24 VOX DSOs, 1VOX Carrier Card NOTE: Only 1 card is needed when using fax
	T1 or E1 Card	1 Quad T1/PRI (or E1) Card
Gatekeeper	Chassis	Cisco 3620 - Cisco 3600 2-slot Modular router-AC with IP software
	Memory	MEM3600-16FC 16MB Flash for the Cisco 3620
	Network Interface	NM-1FE-TX 1-Port Fast Ethernet Network module
Gateserver	CoreServer	N03-UEC2-9N-512AE Netra t 1125 Dual Processor 300 Mhz, 512MB, 9.1GB HD, Ac Internal Power Supply
	Rack Kit	X6901z 19" Rack Mount Kit OEM Ready
	CD-R Drive	X6166A 32X Internal Cd-R Drive
	Network Interface	NM-1FE-TX 1-Port Fast Ethernet Network module
Ethernet Switch (Hub)	Chassis	WS-C2924-XL-A24-port 10/100 Switch (standard edition)
Directory and Messaging Server	Core Server	A26-AA-R E250 Rack Version Server Base, CD, Power Supply 300 Mhz, 256 MB
	2nd Processor	1191A 300 Mhz Processor module w/2MB Cache
	Memory Expansion	7004A 256MB (2-128MB) Memory Expansion Kit
	HDD	5229A Internal 9.1GB 7200RPM Disk Drive
	Floppy	X6005A 3.5" Floppy Drive
	Network Interface	NM-1FE-TX 1-Port Fast Ethernet Network module

Software Requirements

Table 2 lists the software/firmware requirements for the Gateway, Gatekeeper, Gateserver and Backend Servers.

Component	Type	Version
Gateway	Modem	Microcom 5.2.30
	IOS image	C5300-js-mz.120-5T2
	VCWare	vcw-vfc-mz.c542.4.04.bin
Gatekeeper	IOS image	c3620-ix-mz.120-5.0.2.T2
Gateserver	Operating System	Solaris 2.6
	TTS/ASR	API- L&H Telecom TTS - Host V.100 Solaris Sparc P94941 Language Sets - American English, French, Spanish - Female 8Khz V1.00 Solaris Sparc
	SNMP Master Agent (optional)	Solstice Enterprise Agents Runtime V1.03
Directory and Messaging Servers	Directory	Netscape Directory Server 4.0
	Paging	Hylafax version 4.0 patch level 1
	Messaging	Netscape Messaging Server 4.1

New and Changed Information

This section describes the new and changed information for Release 4.1s, and includes the following topics:

• Upgrading to a New Software Release

• Feature Set Table

Upgrading to a New Software Release

This section discusses upgrade information for the software modules that comprise the uOne platform and application. Changes for each module will be listed in a separate table.

UM41 Application

OAM&P

CMA (TNT)

Release	Files Affected	Configuration Notes
4.1.1.0	TNT/parms/Samples/H323.ini	DTMFDetect has a default value of DEFAULT. This handles H245 and RTP DTMF simultaneously. Default: DEFAULT Valid Values: FFT, RTP, H245, DEFAULT
		New keyword LogServer has three options: 1. No (default): This LOGSUB will not be part of the centralized logging facility. 2. Yes: This iteration of LOGSUB is the server for the centralized logging facility. 3. <hostname>: This LOGSUB should connect to the LOGSUB server residing on hostname. LogServer must be spelled as shown, but No and Yes can be in any case and hostname is used as it is.
		The parameter values NET and LOCAL_NET are now valid for the following keywords: DestEvent DestShortage DestDetail DestBillResourc DestBillAPI
4.1.1.1	TNT/parms/Samples/H323.ini	Modified the H323.ini file to utilize DTMF Default parm value DTMFDetect=RTP --> DTMFDetect=DEFAULT
	TNT/parms/Samples/DialMap.ini	Eliminated the 411 rule [USDOMESTIC:Assistance] FromRegExp=^(804)$0(762)$1([0-9]{4})$2$ ToRegExp=^(411)$0 Contraint=None Return=($t0
	TNT/parms/vendor/Samples/Config_GK_DTMF TNT/parms/vendor/Samples/Config_NoGK_DTMF	Created two new Radvision configuration files (Config_GK_DTMF and Config_NoGK_DTMF). These can handle both H245 and RTP DTMF, and need to be used in place of Config_GK_RtpDTMF, and Config_NoGK_RtpDTMF respectively.
	apps/SMS_Notify/Samples/DialMap.ini	Created this dial map for SMS_Notify so that national numbers can be mapped to international numbers for the SMS-C. The file has the exact same format as the DialMap.ini for (CMA) TNT. The phone format "SMS-MAPPING" must be defined. The sample file that is provided defines this phone format and does not do any translations. To actually translate the destination number, the return value would need to modified as desired.

Feature Set Table

Table 6 lists the new software features available for Cisco's uOne Release 4.1s.

Component	Feature
UM41 Application	E-mail/Text to FAX.
	Inbound/Outbound Fax support.
	Billing Logging in UMSA: - Service Event Logs. - Disk Quota Change Event Log.
	Non-Subscriber E-mail address support in Distribution Lists.
	Forwarding of Fax Message with Voice Comment.
	Delete previous entry while addressing a message using *3.
Platform/CMA (TNT)	Expanded digit handling.
	SMS support.
	Enhancements for skipping/speed.
	Multi-language support in APIs (PlayDate/PlayNumber).
	International Dial Plan Enhancements (rules modifications).
	Hosted TTS resource
Scalability Tools	UC Manager.
	Quickconfig Installation tool.
	SNMP Mib enhancements.
	UMCli | Real Time Monitor Enhancements (Viewer).
	Y2K compliance.

Caveats for Release 4.1S

• CSCam00777

The possible values for the DestroyGroup option (TNT.ini) are OnIdle or OnCommand. When either of these values is misspelled, TNT continues as if "OnIdle" value was specified.

In 4.1 a warning message - "Incorrect option for DestroyGroup loading default - OnIdle" is logged (in TNT log files). If this message is observed in the log, DestroyGroup option needs to be modified appropriately.

In 4.2 TNT aborts when the value is misspelled. The value has to be either OnIdle or OnCommand.

• CSCam01031

Symptoms: Base level folder of administrator remains after UMSA deletes administrator. Messages in INBOX are deleted.

Conditions: UMSA deletes administrator.

Workaround: Determine if unsupported non-RFC2060 utility is provided by server to remove base level folders if determined cleanup is necessary.

Further problem description: Does not appear to affect performance.

• CSCam01753

Denial of service occurs due to Answercall timeout.

During a twelve port deposit, twelve port retrieve test, answercall timeout was observed in approximately 0.0056% of the calls (50 unanswered calls in 900,000).

The current release of 4.1 does not have a workaround for this problem.

• CSCam01756

Symptom:

PATH variable for user spmaster is not set correctly.

Condition:

Any version of the Unified Communications software.

Workaround:

The postinstall script of the dapacb package edits the .profile to contain the execution of our .spenv environmental file. The .spenv file modifies the PATH and LD_LIBRARY_PATH variables. If the default .profile sets PATH and/or LD_LIBRARY_PATH from scratch, it removes the values needed. The .profile needs to use $PATH and $LD_LIBRARY_PATH to set PATH and LD_LIBRARY_PATH.

• CSCdp00361

Symptom: In Unified Communication Software 4.1.1, CMA(TNT) must be stopped for any changes to TNT logging or DialMap to take affect. There does not appear to be anyway through umcli to dynamically reload these changes. Condition: Workaround: None, you must stop/restart CMA(TNT) if you make changes to TNT logging in TNT.ini or you make changes to DialMap.ini

• CSCdp01692

SMS_Notify goes to sleep and never wakes up. When this bug occurs, messages accumulate in the notification administrators mailbox and SMS_Notify does not clean them out.

The workaround is to restart SMS_Notify.

• CSCdp06709

Symptom:

The umcli program core dumps under a given sequence of commands.

Condition:

Under the Cisco UM Service Provider Release 4.1(0.9) product, the umcli program core dumps under the following sequence of commands:

1. start system 2. get system status 3. watch notify

Workaround:

Exit umcli after entering a "start system" command, then re-enter the program to issue any "get system status" or "watch notify" commands.

• CSCdp13067

Symptom: Bulktool utility not functioning.

Conditions: UMSA version 4.1.*, bulktool.ini version 4.1.*.

Workaround: Add subscribers individually through UMSA interface.

• CSCdp19438

Symptoms:

Not able to change a subscriber's telephone number through UMSA.

Conditions:

When a subscriber has UID based on the telephone number, UMSA is not able to change the IMAP folders to the new UID/telephone number.

Workaround:

The code has been modified so that an UMSA Administrator is no longer able to change a subscriber's telephone number. This also applies to modifying AMIS-A users as well as Administrators (Greeting, Fax and AMIS-A administrators).

• CSCdp22480

Symptom: On UCManager 4.1.1, some Web screens hang for an amount of time when the destination host is down or unreachable.

Condition: If the destination host for DataExtractor, Unix_Commands or Operations Screen is down or unreachable, then these functions will timeout (approx 3 minutes) before continuing. If the host is unresolvable or inappropriate permissions, then t

• CSCdp22510

Symptom: In Unified Communication 4.1.1, the server where UCManager is running runs out of memory and locks up the system.

Condition: If DataExtractDirector is schedule to run too often and there are a lot of logfiles (greater than free memory), then OS memory resources will run out.

Workaround: Care must be taken on how often to schedule DataExtractDirector. There are performance engineering notes in the UCManager User Documentation. Initially schedule DataExtractDirector to run once and see how long it takes and then adjust

• CSCdp23012

Symptom: In UCS 4.1.1, umcli does not allow CMA (TNT) to be quiesced. This allows active users time to exit while not allowing new users to call into the system. Condition: Workaround: None, this feature is currently not supported by CMA.

• CSCdp23033

The SMSI (MWI) logging from TNT is currently informational. As this logging is crucial in a deployment scenario, it is preferable to make it warning.

The current release does not have a workaround to make the logs warning.

• CSCdp26633

When recording a message and addressing by name, the user hears the prompt "Please enter the last name of the person you want to leave a message. . . ." After entering a last name and pressing the # key, the user hears the same prompt again. So, the user thinks the program is in a loop.

Found 4.1.0.10.

Workaround: Just press # key if you are finished addressing, and you will hear another prompt, "What is the message. . . ."

• CSCdp28123

Symptoms:

If a user is created on a 4.1S system and they try to access their mailbox through a 3.X front-end, the user may not be allowed to log in.

Conditions:

UMSA 4.1 could create a telephone password that UM 3.0 does not decrypt properly.

Work-around:

1. Upgrade the UM 3.x front-end to 4.1S. 2. Do not allow any 4.1S subscriber's to access their mailbox through a 3.x UM front-end.

• CSCdp31928

This release of the UM server does not properly handle Call redirections with redirect reason set to Network Busy or Unknown. The server plays the top level menu greeting to the caller since it is not able to distinguish between a caller and a subscriber.

• CSCdp34850

Symptom: In UC 4.1.1, reroute acb gives no error, yet the acb (app) route table does not take effect. This commonly would be done for app token routing of mwi requests to the proper CMA (TNT) Gateserver.

Condition: In UC 4.1.1, there is no pre-condition (it always fails).

Workaround: As spmaster, type /home2/spmaster/r410/bin/reloadroute APP form the command line. This will dynamically reload the acb (app) route table.

• CSCdp35559

Symptom: In 4.1.1 Unified Communications software, the auto-restart functionality of UCM software starting on reboot (as well as umcli start/stop functionality) will fail to work. Condition: This occurs on systems where there is a Solaris Master SNMP agent running as well as our SNMP agent running which has been configured as the master as well. Workaround: Reconfigure our SNMP agent to be a sub-agent of the Solaris Master agent as per the gateserver configuration doc OR Stop The Solaris Master Agent from running by killing and taking it out of the rc3.d startup directory.

• CSCdp36074

Symptom: UM may terminate when an English e-mail is played in French or Spanish. The subscriber must have the preferred language set to French or Spanish. This problem occurs occasionally.

Workaround : None

Further Problem Description : When UM terminates a core file is generated at /home2/spmaster/core Verify that the core file is for UM by typing file UM at the unix prompt. File will generate a line similar to

core: ELF 32-bit MSB core file SPARC Version 1, from 'UM'

If the last characters are UM, the core file may be deleted.

• CSCdp36210

Symptom : The attached body of a forwarded e-mail is not played when getting e-mail messages. The header (if selected) and any text of the e-mail (if any) are played followed by the phrase "Next Attachment", but any forwarded text is not played.

Workaround : There is no workaround for this problem.

• CSCdp37029

Symptoms:

User is not able to log into UM and not able to log into PMA.

Conditions: If a subscriber changes their telephone or e-mail password to a password with a length greater than six (6), it is possible that the new password will not work with UM or with PMA.

Workaround:

Only create e-mail and telephone passwords with length less than or equal to six (6).

If this still fails to produce a valid password, repeat until with a different password until one is acceptable.

• CSCdp37640

Symptom:

If a caller press 1 (replay or print an e-mail) during the play of an e-mail, the menu to select play or print is not announced. Instead, the message is replayed. After the message has been played completely or the message has been replayed once, the menu is played.

Workaround:

To print the e-mail either allow it to play completely or press 1 to replay it. Then press 1 again to access the replay or print menu.

• CSCdp37668

When a *5 command is entered to go to another mailbox after sending a broadcast message, the system logs you in to the new mail box but "loses" the message inventory and the Main Menu. The result is that after logging in to the new mailbox using the user ID and pin, the user hears the welcome message followed by a long blank (which is when the message inventory and Main Menu greeting should be heard).

• CSCdp39223

If a subscriber makes an error while logging in to a mailbox (i.e., enters the incorrect PIN), then follows that by either pressing *9 or hanging up, UM will terminate unexpectedly, creating a core file.

There is no effect visible to the subscriber, who is exiting the system. The only effect on the system is the occurrence of the core file.

• CSCdp39231

FaxPrint will not send any faxes after sending fax/e-mail to a fax machine that takes longer than 10 minutes to print or the FAXRetryTimeout setting in FaxPrint.ini is longer than 10 minutes.

User will get a returned message with "Fax number could not be resolved" as the reason.

• CSCdp39427

SMS_Notify is not properly truncating messages whose lengths are greater than 161 characters (160 text + NULL terminator). The packet that SMS_Notify sends to the SMS-C is invalid: the actual packet length is different from what the header says and the total length is too long.

Whether the SMS notification actually gets sent to the subscriber is dependent on which SMSC is used.

The workaround is to setup subscribers for Message Count notification only which results in a shorter message being sent to the SMSC.

• CSCdp40093

An idle FaxPrint can terminate unexpectedly.

Effect on user: The users will be able to queue faxes via UM, but they will not be printed (until FaxPrint is restarted).

Effect on operations: You should enable AutoRestart for FaxPrint, otherwise you must notice when it fails and manually restart it. Queued faxes will print once FaxPrint is restarted.

Found in 4.1.1.2

• CSCdp40108

LOGSUB process dies unexpectedly as the result of incorrect handling of a socket error.

This problem was reported after 61 hours of load testing.

The effects of this problem are:

1) all local/remote logging to Sof, Res and Eve files for current processes stops. The log messages for these processes are now logged to the stderr file for each process.

2) LOGSUB should be restarted as soon as possible. All new applications will log to the stderr file until this happens.

3) After LOGSUB is restarted, all new processes will log as they should. Processes that were running when LOGSUB terminated and new processes prior to LOGSUB being restarted will still be logging to stderr.

If full logging is required, the system will need to be restarted.

• CSCdp41218

SMS_Notify notify sends three packets to a SMSC for each SMS notification. The three packet are a bind, a submit and an unbind. The unbind packet has an invalid command then and thus in not a valid packet.

If the SMSC is rigid, then the unbind does not succeed so subsequent binds are not accepted. The result is that SMS_Notify only successfully get one notification to the SMSC and no other notification succeed.

There is no work around for this bug.

Documentation Updates

The following section lists any errors, changes or omissions in the uOne Release 4.1s documentation set. Documentation addendum, errata sheets and updates will be made available on CCO on an ongoing basis.

General

Release 4.1S represents a significant move forward for the uOne product, and the introduction of the uOne name. The terms UM, UM Plus, Unified Messaging Plus, and UC (Unified Communications) are all the equivalent of uOne in screen prints of code, references to UM administrators, in the Quick Configuration scripts, and other places where former iterations of the product name may appear.

Although it is not Cisco policy to reference direct URL links in documentation, exceptions can be found in the Backend Servers Reference Manual and the Gateserver Installation and Configuration Manual. Should these links become outdated or invalid, please contact your Account Representative or the Technical Assistance Center (TAC) for assistance.

Errors

Gateserver Installation and Configuration Manual:

• the required IOS release is listed as 12.0(5.0.2)T2. The correct release number for uOne 4.1s is 12.0(5)T2.

• Any references to outdialing features should be ignored. Outdialing is not available or supported in this release of uOne.

• The rules for Reloading New Dialing Rules are incorrect. To reload dialmap. ini:

1. Edit the dialmap.ini file as desired.

2. Using umcli, stop CMA.

3. Using umcli, start CMA.

Omissions

The following features are included in this release of the product, but are not outlined in the documentation:

• International Dial Plans

Currently, the documentation does not contain samples of international dial plans. Creating a dial plan requires the use of UNIX regular expressions. For information on using this command, please refer to the appropriate UNIX man pages.

Service and Support

If you experience any problems with this product, please contact Cisco's Technical Assistance Center through their web site at: www.cisco.com, Technical Assistance Center link.

Cisco Connection Online

Downloads for the software and documentation for this product require a CCO account, and a password. Please contact your Account Manager for additional information on downloading this product from CCO.

Posted: Mon Sep 25 19:26:26 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.