Release Notes for Patch 2 of uOne 4.2s

These release notes support Patch 2 of Cisco's uOne Release 4.2s. Information in this document supplements the prior uOne 4.2s Release Notes (document number 78-10986-02).

Note Patches to the uOne product are cumulative, meaning that this patch contains all fixes in previous patches (Patch 0 and Patch 1). Note that Patch 2 is the first generally available patch, as Patch 0 had limited distribution (2 sites), and Patch 1 was not released. Therefore, this document is the first Release Notes document for any uOne 4.2s patch.

For a list of the software caveats that apply to this patch, see the "Caveats" section. Caveats are updated for every maintenance release and are located on the uOne documentation site of CCO, as well as the Cisco Documentation CD-ROM.

The following main sections are included in these release notes:

Patch Installation

Instructions for installing this patch are included in a readme file that accompanies the patch file. In addition, you should obtain the Patch 2 prompt file and install it, following its readme file instructions.

Note It is recommended that you read the next section, "New and Changed Information", for information about configuration changes that may be required.

New and Changed Information

If this is a new installation of uOne (without a previous configuration), then you should install this patch (plus the prompt patch) after installing the other uOne packages, and then run Quick Config. In this case, configuration changes discussed below are not necessary.

If you are installing this patch on an existing uOne system, you would typically make the configuration changes described below, as needed, before restarting uOne. A summary list of the changes includes:

H.323 Stack Config Simplification (Required)
Codec Support (Required)
H.323 Inbound/Outbound Port Separation (Required)
Dynamic Codec Switching (Optional)

H.323 Stack Config Simplification

These changes are required for any uOne system running as a CMA (TNT) server. Configuration of H.323 audio capabilities is now enabled from the H323.ini file, using an AudioCapabilities parameter. Audio capability entries in H.323 stack config files are no longer needed, as CMA (TNT) now builds the audio capability portion of the terminalCapabilitySet at start up. This eliminates the need for different H.323 stack config files based on the use of different codecs.

The number of H.323 stack config files has been reduced by putting all user input capabilities (DTMF detection) in each config file. Moreover, there is no need for the channel entries as the stack will open any type of channel using defaults. You only need to configure channels if you need to use some non-default setting. If needed, that could be driven by the H323.ini file as described above.

The H.323 stack config file that remains essential is in the directory $TNTHOME/parms/vendor, and depending on your system's configuration, is either:

Config_GK (with gatekeeper), or
Config_NoGK (without gatekeeper)

Configuration Steps

Perform the following steps after installing the patch and logging in as spmaster:

Step 1 Copy the necessary file (Config_GK or Config_NoGK) from the $TNTHOME/parms/vendor/Samples/ directory into the $TNTHOME/parms/vendor directory.

Step 2 Edit the copied Config_GK or Config_NoGK file to set the maxCalls entry to 3 times the value of MaxPorts in the H323.ini file. For example, with a 24-port configuration, the Config_GK or Config_NoGK file includes these lines:

1 system = 0
 + maxCalls = 72

1 Q931 = 0
 maxCalls = 72

Step 3 If using the Config_GK file (with gatekeeper), change the parameters below as follows:

e164 = '(tech prefix)'
h323-ID = '(H323 End point name)'
+ defaultGatekeeper = 0
+  ipAddress = 0
+   ip = <(gatekeeper IP address)>

Note Use the same tech prefix, H323 End point name, and gatekeeper IP address that were used in the previous TNT Radvision configuration file (Config_GK_RtpDTMF, Config_GK_DTMF, or Config_GK_DTMF_729).

Step 4 Save and close the Config_GK or Config_NoGK file.

Step 5 In the H323.ini file, edit in the proper VendorConfig parameter value, either

VendorConfig=Config_GK

: or

VendorConfig=Config_NoGK

Codec Support

These changes are required for any uOne system running as a CMA (TNT) server. Note that G.729 codecs support is available. G.729 provides an eight-fold savings in bandwidth and message file size as compared to G.711 (U law) codecs, as shown in the comparison below.

G.711 types - 64Kbps (8KBps), where a 1-minute message uses approximately 640KB of message server space.
G.729 or G.729a - 8Kbps (1KBps), where a 1-minute message uses approximately 80KB of message server space.

Patch 2 provides support for Sipro G.729 wav files, providing you make the necessary Gateserver configuration changes to use G.729 in the H323.ini file, the TNT.ini file, and the gateway dial-peer.

Configuration Steps

As spmaster, perform the following steps (whether configuring for G.711 or G.729 codec):

Step 1 In the H323.ini file, add a new AudioCapabilities parameter specifying either g711Ulaw64k or g729.

[H323]
AudioCapabilities=g711Ulaw64k

: or

[H323]
AudioCapabilities=g729

Step 2 In the TNT.ini file edit this parameter as follows (from the default value of 1000):

[MEDIARATE]
WAV=8000

G.729 Support Steps

As spmaster, perform these additional steps if configuring for G.729:

Step 1 In the H323.ini file, edit these parameters as follows:

[H323]
SilenceCompression=Off
DTMFDetect=DEFAULT

Step 2 In the TNT.ini file, edit these parameters as follows (omit notes in parenthesis):

[CONTAINER]
RECORDFORMAT=G729 (default for SIPRO, or)
RECORDFORMAT=G729_CISCO
 
[MEDIAENCODING]
WAV=G729 1000
 
[MEDIABYTESPERSEC]
WAV=1000

Step 3 Set up codec class features on the gateway dial-peer with "g729r8" and "g711Ulaw".

Note Ensure the gateway's dial-peer has the g729r8 codec defined and has vad disabled (no vad).

H.323 Inbound/Outbound Port Separation

This H323.ini file change is required for any uOne system running as a CMA (TNT) server. The MaxPorts parameter now allows logical H.323 resources to be reserved as inbound or outbound. The H.323 resource module looks for outbound resources when doing a MAKECALL, which can be designated as inbound/outbound/bidirectional. The default is for H.323 resources to be bidirectional (used for inbound calls or outbound calls).

Note The total number of H.323 resources is equal to 3 times the number given as MaxPorts. For example if MaxPorts=24, there are 72 total H.323 resources.

Configuration Steps

As spmaster, perform the following steps:

Step 1 In the H323.ini file, add new values (PortDirectionInbound and PortDirectionOutbound) under the existing Maxports parameter. To prevent "Glare" (inbound and outbound calls trying to use the same resource), we recommend setting 2/3 of the H.323 resources for inbound calls and 1/3 for outbound calls.

For example, using the 2/3-inbound and 1/3-outbound recommendation:

[H323]
MaxPorts=24
PortDirectionInbound=48
PortDirectionOutbound=24

Note More resources are recommended reserved for inbound than outbound calls because some inbound-call resources may become inactive, but not immediately available for reuse.

Dynamic Codec Switching

Dynamic codec switching is required if either of the following applies:

TTS (Text-to-Speech) is needed for G.729 messages.
Both G.729 and G.711 messages need to be played.

Configuration Steps

To configure for dynamic codec switching, perform the following as spmaster:

Step 1 Follow the previous "Configuration Steps" section for using G.729 codec, with the following exception:

In the H323.ini file, edit the AudioCapabilities parameter to include both G.729 and G.711, using a single space between them as follows:

[H323]
AudioCapabilities=g729 g711Ulaw64k

Note The gateway's dial-peer must be set to "no vad" and the dtmf-relay to "h245-signal".

uOne 4.2s Serviceability

Patch 1 provides MIB fixes to support number of ports > 48. Files affected are listed in Table 1.

Table 1: Seviceability Information for Release 4.2s Patch 1

Files Affected Configuration Notes

$PARMLIB/SNMP/mibs/amteva.txt

$PARMLIB/SNMP/mibs/spSnmpTrap.txt

$PARMLIB/SNMP/mibs/umApp.txt

$PARMLIB/SNMP/mibs/umAppSchedule.txt

$PARMLIB/SNMP/mibs/umGen.txt

$PARMLIB/SNMP/mibs/umH323.txt

$PARMLIB/SNMP/mibs/umLogMonitor.txt

$PARMLIB/SNMP/mibs/umMwiFax.txt

$PARMLIB/SNMP/mibs/umMwiNotify.txt

$PARMLIB/SNMP/mibs/umRadRtp.txt

$PARMLIB/SNMP/mibs/umSMSNotify.txt

$PARMLIB/SNMP/mibs/umSnmpLog.txt

$PARMLIB/SNMP/mibs/umTnt.txt

$PARMLIB/SNMP/mibs/umXGCP.txt

$PARMLIB/SNMP/mibs/umTrap.txt

On the SNMP Manager, unload the current uOne SNMP MIBS and reload the new MIBs provided with the patch.

Files Affected	Configuration Notes
$PARMLIB/SNMP/mibs/amteva.txt $PARMLIB/SNMP/mibs/spSnmpTrap.txt $PARMLIB/SNMP/mibs/umApp.txt $PARMLIB/SNMP/mibs/umAppSchedule.txt $PARMLIB/SNMP/mibs/umGen.txt $PARMLIB/SNMP/mibs/umH323.txt $PARMLIB/SNMP/mibs/umLogMonitor.txt $PARMLIB/SNMP/mibs/umMwiFax.txt $PARMLIB/SNMP/mibs/umMwiNotify.txt $PARMLIB/SNMP/mibs/umRadRtp.txt $PARMLIB/SNMP/mibs/umSMSNotify.txt $PARMLIB/SNMP/mibs/umSnmpLog.txt $PARMLIB/SNMP/mibs/umTnt.txt $PARMLIB/SNMP/mibs/umXGCP.txt $PARMLIB/SNMP/mibs/umTrap.txt	On the SNMP Manager, unload the current uOne SNMP MIBS and reload the new MIBs provided with the patch.

Caveats

The following sections list both open (unresolved) caveats and caveats resolved by this patch.

Open Caveats

The following caveats include all known unresolved issues.

CSCdp51347

: Symptoms: Same as in CSCam01031. Base level folder of administrator remains after UMSA deletes administrator. Messages in INBOX are deleted.
: In "UMSA: Delete Administrator", if an administrator (of any of the 3 available types) is modified, an error is reported when attempting to delete the modified administrator.
: Greeting Admin: retry folder
: FAX Admin : faxretry folder
: AMIS-A Admin : AwaitTrans folder
: Sample error message: ==== Application Error
: The following error has occurred that prevents the application from processing your request. Error: deleteAdmin | The folder: faxretry was not deleted from the message server. Please report this to Customer Support. We apologize for the inconvenience.
====
: Conditions: In "UMSA: Delete Administrator", if an administrator (of any of the 3 available types) has been modified, an error is reported when attempting to delete the modified administrator. This error does not affect deleting non-modified administrators.
: Workaround: Determine if an unsupported non-RFC2060 utility is provided by server to remove base level folders if it is determined that cleanup is necessary.
: Further problem description: The ability to rename a folder is not permitted in the design of IMAP as provided in RFC 2060. This problem does not appear to affect performance.

CSCdp51872

: Symptom: In uOne 4.2.1, uOne Manager reports based on COI (Communities of Interest) or COI group selection criteria may show inaccurate data. In this case, the uOne Manager canned reports may reflect too much or extra information in the report that is associated with another COI that wasn't selected for the report.
: Condition: If there are multiple COI log records being recorded for uOne Manager to process and one COI's name is a subset of another COI's name, then the problem will occur. For example if there is a COI defined as o=cisco.com and another COI defined as ou=customer1,o=cisco.com, then the problem will occur. In this example, uOne Manager reports that select o=cisco.com only, will actually report on both COIs defined above. Selecting ou=customer1,o=cisco.com will report correctly only on the ou=customer1,o=cisco.com community.
: Workaround: If the activity for these two communities occurs on separate uOne servers, then central logging could be turned off for one community and Event logs could be manually transferred to the uOne Manager server where the oam.ini setup for each community's log source could be defined. Communities could also be reconfigured so that their names don't overlap completely. Keeping communities on the same level would accomplish this.

CSCdp53611

: When an e-mail created in Outlook Express is accessed by uOne, it will have one attachment even when composed using plain text. This occurs because Outlook Express formats and sends the message in "text/plain" format as well as "text/html" format. Outlook Express defaults to this behavior, and it is not a configurable parameter.

CSCdp65494

: After recording 180 seconds of silence, the caller is not allowed to send the message but hears "Sorry your message was not recorded" instead.
: uOne allows a silent message to be recorded and then notifies the caller that it is silent and that the message will not be delivered.

CSCdp76203

: The Charge Number field for the outbound calls in the watch h323 entries screen in umcli will always be empty whether calls are gateway routed or gatekeeper routed. There is no workaround for this problem.

CSCdp76412

: Symptom: A year entered in the message body as 00 is read as "1900". A year entered as 2000 is read as "twenty zero".
: Condition: This is caused by L&H TTS3000 version 1 software.
: Workaround: None.

CSCdp89570

: After leaving a message, while hearing "Message Sent", press *9, uOne does not exit. The same thing happens after a subscriber saves a message and presses *9 while hearing "Message saved".

CSCdp94660

: Symptom: A voice message sent to a subscriber is logged as VoiceBroadcast if the subscriber is added to a TO list which contains a broadcast list.
: Condition: When a broadcast voice message is sent to a broadcast list plus a subscriber with uOne 4.2, the message is recorded in the event logs as a broadcast message to the list and a broadcast message to the lone subscriber.

CSCdr05963

: Symptom: Cannot use "start system" in umcli to start all objects.
: Condition: This occurs if the hostname is greater than 15 characters.
: Workaround: Make sure the hostname is less than 15 characters.

CSCdr06297

: Symptom: SNR is not ringing a cellular phone.
: Condition: Some cellular services do not connect fast enough and the system times out before actually ringing the phone.
: Workaround: The administrator should set the # of rings to 6 in the modify subscriber screen.

CSCdr10872

: Symptom: uOne Manager reports that are selected by COI or COI group may show "no data available" even though their logs are on the uOne Manager server.
: Condition: If special characters are used in the naming of Directory Server Communities (e.g. ou=Company's Community1,o=Organization), then this problem will occur if this is the community to be reported on. Other special characters used cause the same problems: ' ! $ ^ * < \Q | *
: Workaround: Rename the community without using special characters, otherwise uOne Manager reporting will not be available for this community.

CSCdr13475

: Symptom: When a message is left for a subscriber by dialing the subscriber's Personal Access number, the caller is not able to leave a message for another subscriber, but is only allowed to leave another message for the same subscriber.
: Conditions: In the UM.ini configuration file the following line must exist in the UMConfig section SNAMode=Enabled. Also, a subscriber must have a Personal Access number configured and the caller must call the Personal Access number to leave a message.
: Workaround: There is no workaround if a Personal Access is desired. If a caller dials a non-Personal Access number (the subscriber's telephone number) and leaves a message, the caller is able to leave a message for another subscriber.

CSCdr14660

: Symptoms: (A) The umcli watch h323 states screen can be cluttered with transport address (e.g. TA: ###.##.###.##:xxxx where #'s represent the IP address and x's represent the port number).
(B) SNR Paging will not read back to the caller a paging source.
: Condition: These symptoms occur when a call comes into the system from a phone with no ANI.
: Workaround: Include the following lines in the H225CALLINGPARTY section of DialMap.ini.
: [H225CALLINGPARTY:StripTransportAddress] Input=^TA([A-Za-z0-9:.]*)(.*)$
Return=

CSCdr15239

: Symptom: If the SMTP server it uses malfunctions, uOne will hang.
: Condition: An SMTP server can malfunction (for example, due to disk space) such that it does not properly provide SMTP service. It can accept TCP connections to the SMTP port, but may not respond to requests sent over the connection. When the SMTP server is in this state, UM agent processes that are sending messages to the SMTP server at that time may hang indefinitely.
: Workaround: Prevent SMTP malfunctions.

CSCdr15934

: Symptom: UMSA: Add/Mod Sub displays COS with first character truncated of COS name.
: Conditions: UMSA: Add/Mod of COS with COS name beginning with a lowercase letter causes truncation of the letter.
: Workaround: Use an uppercase letter to begin COS name in UMSA: Add/Mod COS.
: Further problem description: Does not affect value selected or value stored, cosmetic error only.

CSCdr17788

: Symptom: Customers will notice that names of variables in FaxPrint.src are the same as UM.src (Starting with UM).
: Condition: FaxPrint and UM use the same code generating tool to generate source code.
: Workaround: Whenever you get traps for tokens in UM.src file, you have to manually check whether it is from UM or FaxPrint.

CSCdr19143

: Symptom: None.
: Condition: Speak TTS API causes extra event to placed in the uOne applications event queue that is never processed. There are no outward symptoms that a user / OEM may see. This is an internal issue only.
: Workaround: None.

CSCdr20423

: Symptom: In uOne 4.2.1, the umcli "watch acb" and "watch cma" screens can show information about the ACB(APP) and CMA(TNT) agents even though they are not running. This information are things like the state of h323 channels and the last time a reload route has occurred.
: Condition: This can occur if umcli is run on a uOne system where ACB or CMA had once run but currently are no longer running (and a reboot hasn't happened).
: Workaround: umcli get system status will always show the true state of the uOne systems critical agents. Watch acb and cma will show the last known state of those agents. If the uOne system was shutdown orderly, then that information will reflect no currently activity. If the uOne system had stopped abruptly, then that information will reflect the last known state of ACB and CMA.

CSCdr24540

: Symptom: TNT stdout file can contain error messages generated by the H.323 stack.
: Condition: The messages that are being logged to the TNT stdout file are generated by the H323 stack used by the CMA. Currently we have no control over the generation of these logs. We are working with the third party vendor to resolve this issue. These messages are more abundant when running a gatekeeper. These messages have not been identified as being indicative of any problems occurring on the uOne system.
: Workaround: None.

CSCdr24864

: Symptom: In uOne Manager, there exists a link called "UM_Process_Acitivity" under Operations, which when clicked says "selected link has no entries".
: Condition: The problem occurs when 4.2.0 uOne Manager has been upgraded to 4.2.1 uOne Manager because of left over files.
: Workaround: The UM_Process_Activity Web page has been replaced by Operations/State_Information. To remove the UM_Process_Activity link, recursively remove the following directory: /home2/spmaster/ummgr/Web/Operations/UM_Process_Activity:
: cd /home2/spmaster/ummgr/Web/Operations
: rm -r UM_Process_Activity
: Then reload the web page through the browser.

CSCdr26740

: Symptom: UM can hang and its call be abnormally terminated after 2 hours of hold time.
: Condition: With extremely long calls (hours in duration), the call may be dropped causing UM process to hang.
: Workaround: There is no workaround.

CSCdr26760

: Symptom: Occasionally, when a subscriber logins into his mailbox and outdials to another number, the UM session hangs.
: Condition: This occurs if the called party hangs up.
: Workaround: The subscriber must hang up, dial uOne back, and login again.

CSCdr27208

: Symptom: UM may terminate when an e-mail is played in any language other than the language in which it was written. This problem occurs occasionally.
: Conditions: UM terminates only if the Lernout and Hauspie (L & H) TTS 3000 product is installed as the Text To Speech service.
: Workaround: None. Contact Lernout and Hauspie for further assistance.
: Further Problem Description: When UM terminates, a core file is generated at /home2/spmaster/r410/logs/cfiles/directoryname. Verify that the core file is for UM by typing "file core" 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.

CSCdr27547

: Symptom: Customer will see erroneous data on watch screens in umcli.
: Condition: This will happen when the customer looses connectivity.
: Workaround: The workaround for this problem is to stop and start CMA.

CSCdr27667

: Symptom: Caller is put to attendant's mail box when attendant doesn't answer the phone.
: Condition: 1. Subscriber has attendant coverage set up. 2. Attendant has a mail box on the same message server as the subscriber. 3. Caller leaves a message for a subscriber with attendant coverage. 4. While listening to the subscriber's mail box greeting, caller presses 0 to transfer to the attendant coverage person. 5. The attendant coverage person does not answer the phone. The caller will hear the attendant coverage person's greeting and the message goes to the attendant's mail box.
: Workaround: None.

CSCdr28215

: Symptom: An administrator receives an error when attempting to modify subscriber.
: Condition: If the administrator enters a '$' as the last character of the Last Name the system will accept the name but future modifications of the record will error out. The administrator will also notice on re-enter the modify subscriber field that the word with the $ now has {} surrounding it.
: Workaround: Do not use $ in the name of a subscriber.

CSCdr28998

: Symptom: CMA may fail to start after initial configuration.
: Condition: If a uOne system with no prompt packages has been loaded and has been set up using quickconfig with the intention that this uOne server is to only run MWI, FaxPrint or SMS_Notify, then CMA will fail to start. This is due to a missing prompt that CMA requires that was never installed.
: Workaround: Install the prompt package on the uOne server and restart CMA.

CSCdr29079

: Symptom: Outbound calls that use gateway bridging (SNR, *T) may take 4-5 seconds to establish full-duplex voice after the call is connected.
: Condition: This issue is related to the IOS version running in the gateway. A fix that resolves this issue will be in IOS 12.1(2)T.
: Workaround: Do not use Gateway Bridging for Outbound calls. This is done by setting RTPBridgeType=GateServer in the H323.ini file located in $TNTHOME/parms.

CSCdr29789

: When sending a message using the dial by name feature for multi line subscribers, uOne may not recognize the names entered. The system prompts for entering more letters or says that the name could not be found, although there was only one subscriber with the last name entered.
: Condition: The entered last name (for example, John) matches other last names (for example, Loin) because of the way a telephone keypad associates multiple letters with a single digit.
: Workaround: In UM.ini section AutoAttendant set MaxListEntries to 5-9. 9 is the maximum allowable value. This parameter determines the number of matching names that are presented to the caller. For example, if we have John Doe, Tom Doe, & Richard Doe as subscriber (assume no other similar names) and the caller entered 3(D) 6(O) 3(E) the caller would hear Press 1 to reach John Doe, Press 2 to reach Tom Doe, Press 3 to reach Richard Doe. If a 4th Doe existed and MaxListEnties is the default (3), the caller would be required enter more of the name to narrow the search. If the MaxListEntries value is set to 9, all 4 names would be presented.
: Further Information: John & Loin match for the following reason: Each DTMF digit represents 3 or 4 letters of the alphabet. For example, 2 represents A, B, or C while 7 represents P, Q, R, or S. Therefore, John & Loin both are represented by 5646. In this case, the caller would be required to select from a list or continue by spelling the first name.

CSCdr33647

: Symptom: Cannot use "start system" in umcli to start all objects.
: Condition: This will only occur if the host name is greater than 15 characters.
: Workaround: Make sure the host name is less than 15 characters.

CSCdr36596

: Symptoms: A. Spoken names, greetings, or voice messages sound garbled, or
B. On systems employing G.729, TTS output sounds garbled.
: Condition: Symptom A is due to codec mismatch. This results because the system is not fully configured for codec switching and there is a codec mismatch between the phrase and phone connection. Symptom B occurs only when the system is configured for using G.729. This is because TTS output is G.711 and the connection expects G.729, resulting in a codec mismatch.
: Workaround: The workaround for both symptoms is to use dynamic codec switching.

CSCdr47634

: Symptom: PMA Distribution List error when using the "Add More" button.
: Conditions: Distribution list was created prior to Patch 2 installation. Does not affect distribution lists created after Patch 2 is installed.
: Workaround: Delete then re-add information for distribution lists created prior to Patch 2 to update the LDAP record with new schema attributes.
: Further problem description: PMA distribution lists are not backwards compatible. Error log located in /home2/spmaster/ADMIN/logs/subAdmin.err will show data similar to:
: May 31 2000|21:21:08 EDT | subAdmin | PMA ERROR: [9202] Can not LDAP modify for the following reason: "modifying entry mail=12test@cisco.com, uniqueidentifier=Cisco0000000000000995, ou=Developer's Community,o=cisco.com ldap_modify: Type or value exists."

CSCdr48527

: Symptom: The subscriber can log into the system using multiple e-mail addresses.
: Condition: If the backend messaging server is software.com Mx5.1 and a subscriber's e-mail address is changed by the administrator, the subscriber will be able to log in to WebEdge using both the original e-mail address and the new e-mail address.
: Workaround: If you need to change an e-mail address, delete the subscriber and re-add the subscriber with the new address.
: Workaround: None.

CSCdr49719

: Symptom: No prompt tells users nothing is recorded when recording name.
: Condition: When recording the name of a mailbox, if user does not press "Mute" button, there is no prompt to tell the user that nothing is being recorded. The background noise is recorded as the name of a mailbox.
: Workaround: Press "Mute" button when recording, then at the end of recording, uOne will say "Sorry, the name is not recorded."

CSCdr49722

: Symptom: No prompt tells users nothing is recorded when recording a greeting.
: Condition: When recording a greeting of a mailbox, if user does not press "Mute" button, there is no prompt to tell the user that nothing is being recorded. The background noise is recorded as the greeting of a mailbox.
: Workaround: Press "Mute" button when recording, then at the end of recording, uOne will say "Sorry, the greeting is not recorded."

CSCdr49724

: Symptom: No prompt tells users nothing is recorded when leaving a message.
: Condition: When recording a message, if user does not press "Mute" button, there is no prompt to tell the user that nothing is being recorded. The background noise is recorded as the message.
: Workaround: Press "Mute" button when recording. When user sends the message, uOne will say "Sorry, the message is not recorded."

Resolved Caveats

The caveats below were previously assigned release notes and are now resolved with this patch. Additional issues are also resolved by the patch—see the readme file with the patch for a complete list.

CSCdp67454

: Symptom: uOne Manager reports don't show current information even though DataCollector has run recently. For example, when generating a report at 3pm, uOne Manager may show data for today's report only up to noon.

Note Refer also to DataCollector notes in the Documents, "Changes" section.

CSCdp72858

: 1. In UMSA, add a subscriber and add pager information for this subscriber. 2. In UMSA, edit this subscriber, set Single Number Reach Enabled to no, set Single Number Reach Pager Enabled to no, check Pager Bus. Hrs., then submit. 3. Login as this subscriber in uOne. 4. At the main menu, press 6, then press 1 to enable single number reach feature. 5. Press 1 to reuse existing number. 6. Go back to UMSA, you will see Single Number Reach Enabled is changed to yes, but Single Number Reach Pager Enabled is still no. In this case, the subscriber will not be paged.

CSCdp79972

: Symptom: The system beep sounds like a faint noise and lasts 4 seconds. A subscriber might start leaving their message before this 4 seconds of playing is done and the leading edge of the message would not get recorded.

CSCdp91639

: Subscriber has attendant coverage defined and SNR off. Caller comes in to uOne and gets subscriber mailbox greeting. Pushes 0 for attendant coverage. Attendant cover calls the cover number and the two parties are connected. Attendant coverage person hangs up the call. The original caller gets the leave message beep. If they just talked to the coverage person they should either get no beep and the "... leave a message for someone else..." prompt or get the subscriber mailbox greeting again. Just getting the leave message beep after going out to attendant coverage is confusing.

CSCdp94625

: Symptom: Netscape cannot find a valid e-mail address. Administrator receives the message: Invalid e-mail address uid must be in lower case..."

CSCdr08059

: The most common problem encountered will be that of a corrupt LOG.Network.Data file that is located in the $HOME/logs/netlogs directory. The usual result of trying to start the system with a corrupt Network.Data file is that the LOGSUB process will core.

CSCdr09785

: Symptom: When the main subscriber access number is called you are placed in a subscribers mailbox.

CSCdr24954

: Symptom: In the UMSA modify/delete subscriber search field, searching on location can neglect to return all possible entries.

CSCdr27194

: Symptom: Call in to a subscriber with 1 SNR number and 1 SNR Pager setup. When uOne asks the caller to record their name, the caller records a name and presses 1 to end recording. Then the SNR sequence starts and the SNR number reached is answered. Once answered, the system says I have a call for "subscriber" from "caller", to take the call press 1 (etc...). Called party presses a 2 and then hangs up.
: Original caller only hears "Do you want to be reached at (number that caller is calling from (ANI))". This call should return the caller to the menu says I was unable to reach "subscriber", press 1 to page or press # to leave a message.

CSCdr28344

: Symptom: Approximately 1 in 1500 calls to uOne will not be answered because of inbound/outbound call collisions.

Note Refer to the "H.323 Inbound/Outbound Port Separation" section for more details.

CSCdr30876

: Symptom: There are no help topics available for adding, modifying, and deleting secondary telephone numbers in UMSA.

CSCdr30891

: Symptom: When printing email, press *1 goes to get message menu instead of main menu.

CSCdr30919

: Symptom: Pressing *9 starts outdialing instead of canceling an outbound call.

CSCdr31046

: Symptom: DTMF detection can fail under certain configuration combinations.

CSCdr31274

: Symptom: The "BRIDGE SILENT", unbridge, for H323 GateWay Bridging was not working properly.

CSCdr31565

: Symptom: The uOne snmpd daemon can fail under certain conditions, thus future snmp requests will not respond and applications (eg. uOne Manager) that use the SNMP MIBswill show no data.

CSCdr31878

: Symptom: A subscriber modifies their PIN password via PMA and can no longer log into secondary phone lines.

CSCdr31979

: Symptom: On a system running SMS_Notify, system memory loss is detected over time.

CSCdr32000

: Symptom: MWI_OnOff does not process a DROP record if its FROM field is missing.

CSCdr32248

: Symptom: An incoming call from an H.323 endpoint more than 2 IP hops from the Gateserver is disconnected without being accepted by uOne.

Note The fix was to remove the line below from the /etc/rc2.d/S99uonetune file.

ndd -set /dev/ip ip_def_ttl 2

CSCdr32784

: Symptom: When running the bulkload tool, errors occurred due to missing attributes (inboundfaxno and snaphonenumber).

CSCdr32976

: Symptom: umcli watch acb entries shows connections between MWI_OnOff and TNT that are no longer present.

CSCdr39883

: Symptom: Dial-by-name doesn't work for transferring calls.

CSCdr44704

: Inbound/Outbound resource separation enhanced to use round-robin selection of outbound call resources. See CSCdr28344.

CSCdr49066

: Symptom: In attempting to add secondary phone number, the administrator receives the following message: "The following error has occurred that prevents the application from processing your request. Error: addSecPhone | The folder: ######## was not added to the messaging server. Please report this to Customer Support. We apologize for the inconvenience."

CSCdr49076

: Symptom: Attempts to use UMSA to delete secondary phone number fail.

CSCdr49082

: Symptom: The user is unable to add a single SNR number in PMA.

CSCdr51431

: Symptom: No up-to-date report data is available through uOne Manager Report Selection criteria. This includes missing recent date selections for all the reports.

Documentation Updates

The following documentation updates have been identified since the FCS release of uOne 4.2s.

Changes

The uOne 4.2s Gateserver Installation and Configuration Manual includes a "Data Extract Director" section on page 14-8 of Chapter 14 that provides some worst-case data collection times. Improvements included in this patch contribute to some revised estimates, as follows:

A worst-case DataExtractDirector collection period for a 24-hour loaded system with no call-inactivity time is approximately 8 minutes (previously 45 minutes).
DataCollector time to process 2000MB of log files is approximately 1 hour (previously 550MB).

In addition, information previously provided in the "workaround" section of a related caveat (CSCdp67454) is still applicable. This information deals with ways to improve data collection rates, and is as follows:

Running DataCollector again (when reports are delayed) will not speed up the availability of reports, because it will wait to finish the existing DataCollector run first. Setting HOWMANY_DAYS=2 will not cause DataCollector to have to reprocess any old files, thus increasing its performance. Turning off Informational Logging in UM.ini will cause DataCollector to run 4 times faster, however session trace records like phrases played and DTMF entered will be lost for troubleshooting purposes. Turning DestBillResource on all gateservers to LOCAL will cause DataCollector to run 1/10th faster, at the expense of losing the UM Application Summary Report. Engineering how many central log servers are deployed may need to be revised to increase performance. Possibly, multiple uOne Manager domains could be created.

Table of Contents