Table of Contents
Release Notes for uOne 4.2s
April 27, 2000
 |
Note This revision of uOne 4.2s Release Notes differs from the original FCS Release Notes in the addition of a new caveat, CSCdr36596, concerning dynamic CODEC switching. Another entry in the "Documentation, Omissions" section covers a gateway config topic. |
These release notes support Cisco's uOne Release 4.2s. For a list of the software caveats that apply to this release, see the "Caveats for Release 4.2s" 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.
|
Note Platform requirements and installation instructions for uOne 4.2s are covered completely in the uOne GateServer Installation and Configuration Manual, Release 4.2s. |
These release notes discuss the following topics:
This uOne 4.2s release passed comprehensive feature and load testing between the dates of 10/25/1999 and 04/18/2000. All major problems were resolved. Both Software.com and Netscape backend servers were used in testing, although uOne was tested with Netscape the most.
This release consists of software for the uOne application tier as well as plugins for Netscape Messaging Server 4.x when it is used as part of the backend tier.
- For more information on uOne see the uOne 4.2s product documentation.
- For information on new features supported by Release 4.2s, refer to the section "New and Changed Information".
This section describes the new and changed information for uOne Release 4.2s, and includes the following topics:
New software features in Release 4.2s of uOne are listed in Table 1.
Table 1: Selected Features Supported by Cisco's uOne Release 4.2s
| Component
| Feature
|
|---|
UM Agent
| Multi-line mailbox.
|
| Compatibility with Software.com MX 5.1 backend servers.
|
| Deposit/Retrieval Session mode (DRS) for cellular users.
|
Platform/CMA (TNT)
| G.729 and G.729a audio CODEC support.
|
| Dynamic CODEC switching.
|
| Empty Capability Set mechanism available for H.323 call bridging in gateway, reducing resource consumption in all forms of outdialing.
|
| RAI/RAC support
|
| Fast Start (H323 Fast Connect) for outbound calls
|
| Dialmap simplification.
|
| Optional SIP1 (Session Initiation Protocol) support.
|
| Optional XGCP2 (MGCP, SGCP) support.
|
Serviceability Tools
| Enhanced umcli tool monitoring and additional uOne Manager reports.
|
| Quick Configuration tool enhancements.
|
| SNMP enhancements (MIB and traps).
|
1SIP support option available through Cisco Pro Services.
2XGCP support option available through Cisco Pro Services.
|
This section discusses updates to product functions for the software modules that comprise the 4.2s uOne platform and application. This information is divided in the following subsections:
If you are upgrading from uOne 4.2s EFT to the FCS of uOne 4.2s, there are some addressing and dialing changes of which you need to be aware.
|
Note Be sure to read the "Addressing and Dialing Rules Configuration" section of the uOne Gateserver Installation and Configuration Manual for more complete information on how uOne handles addressing and dialing. Note that the document does not cover the Extra and Constraint parameters in an effort to simplify the configuration process for most integrators, particularly those who have not used prior releases or those using the uOne product in an enterprise environment. Despite not being covered in the document, the parameters are still honored by the software in order to ease your migration from earlier releases and allow complex configuration with the assistance of technical support representatives. |
DialMap.ini Format Change
The DialMap.ini file now has a simplified format to minimize the complexity for rules that do not require extra token information or constraints in order to perform the desired mapping. If you need extra information or constraints, you can still use them.
|
Note We encourage you to leave out the Extra and Constraint parameters if you do not need them. This will make your file more readable and quicker for the system to process. If you do not need to keep the existing addressing and dialing rules you currently have in your Rules.<hostname> or DialMap.ini files, we recommend creating a totally new DialMap.ini file using the Quick Configuration tool and then modifying it to meet your needs. |
For each type of rule you currently have, convert it to the new format following these guidelines. This information applies to the following:
- Subscriber dialing conversion (for example, USDOMESTIC).
- Caller access dialing conversion (for example, CALLERACCESS).
- Address expansion (for example, DialPlan and including sections named in the LoginExpandSection UM.ini parameter).
- Fax Offramp Gateway Conversion (for example, GWHOSTS and including sections named in the SMTPHostSection FaxPrint.ini parameter).
- SMS-MAPPING section (for SMS_Notify).
Rules within format sections of the areas above now require these changes:
Table 2: Format Section DialMap.ini Changes (for sections listed above)
| From: (Previous uOne Format)
| To: (New uOne 4.2s FCS Format)
|
|---|
- [<format>:<rule>]
FromRegExp=<from>
ToRegExp=<to>
Constraint=<constraint>
Return=<return>
| - [<format>:<rule>]
Input=<to>
Extra=<from>
Constraint=<constraint>
Return=<return>
|
XGCPCallingParty, XGCPCalledParty, H225CALLINGPARTY, and H225CALLEDPARTY sections may be converted within the format sections as follows:
Table 3: Format Section DialMap.ini Changes (for sections listed above)
| From: (Previous uOne Format)
| To: (New uOne 4.2s FCS Format)
|
|---|
- [<format>:<rule>]
FromRegExp=<from>
ToRegExp=<to>
Constraint=<constraint>
Return=<return>
| - [<format>:<rule>]
Input=<from>
Extra=<to>
Constraint=<constraint>
Return=<return>
|
Once again, for readability and performance reasons, we highly recommend that you omit the optional Extra and Constraint parameters of a rule if you do not need them.
SMS_Notify's DialMap.ini File Eliminated
Another change is that SMS_Notify's DialMap.ini file ($PARMLIB/apps/SMS_Notify/DialMap.ini) has been eliminated in favor of using the CMA (TNT) DialMap.ini file. Move any existing SMS-MAPPING rules to the SMS-MAPPING section in the $TNTHOME/parms/DialMap.ini file, creating the section if it does not yet exist.
See the "Combine DialMap.ini file from SMS and CMA (TNT)" entry in Table 4 for more information.
Files listed below provide configuration file upgrade information since the EFT uOne 4.2s release (4.2.1.0). Changes prior to the EFT release are not listed.
Table 4: Application and Platform Upgrade Information for Release 4.2s
| Files Affected
| Configuration Notes
|
|---|
cisco-schema.conf
| Added attribute "MWIEnable" to the COS. Default value is "no". Now, the UM agent does not attempt to turn off MWI even when it is not configured.
|
cisco-schema.conf
| Two new attributes, secondaryphonenumber and phonetype are added to the LIP and conf_msgbox entries, respectively.
|
cisco-schema.conf
| A new LDAP attribute supports a new feature in PMA: Distribution List.
Attribute "memberdescr" added to "objectclass=distributionlist".
|
TTSP.ini
| Tunables for early play and default audio file length.
StartDelay=nn where nn is how large (in seconds) to allow the resulting tts audio file to become before we start the play of the audio file. The limits are 2 and 20 inclusively and the default is 10.
DefaultLength=nnnn where nnnn is the maximum size audio file (in seconds) that tts will produce regardless of the size of the incoming text file. The limits are 60 to 1200 inclusively and the default is 180.
|
<none>
| Enable dynamic switching between codecs.
The dial-peer on the gateway needs to be set according to the following specification:
A. Create a voice class codec with desired codecs and their preferences.
B. Use the above voice class codec instead of the "normal" codec command in the dial-peer config.
C. If one of the codecs is g729, then have "no vad" and "dtmf-relay h245-signal" in the dial-peer config.
Example:
gw1z4#config terminal
gw1z4(config)#voice class codec 1221
gw1z4(config-class)#codec preference 1 g729r8
gw1z4(config-class)#codec preference 2 g711ulaw
gw1z4(config-class)#exit
gw1z4(config)#dial-peer voice 1223 voip
gw1z4(config-dial-peer)#destination-pattern xxxxxxxxxx
gw1z4(config-dial-peer)#voice-class codec 1221
gw1z4(config-dial-peer)#dtmf-relay h245-signal
gw1z4(config-dial-peer)#no vad
gw1z4(config-dial-peer)#session target ipv4:yyy.yyy.yyy.yyy
gw1z4(config-dial-peer)#exit
gw1z4(config)#exit
gw1z4#
|
XGCP.ini
| Telcordia CA 2.0 requires notify on separate port. There is now a new configurable that designates the Notification port for the Call Agent:
CallAgentNotifyPort, the default value is 2427.
For Call Agents that do not use separate ports, the Listen and Notify ports should have the same value.
|
H323.ini
| H323 Bridging on Gateway w/ Empty Capability Set
Configuration:
RTPBridgeType=Gateway (default: Gateway)
There is a noticeable (4-5 second) delay after the GW Bridge is completed before the two calls can be heard over the Telephones. This appears to only occur if the inbound and outbound calls both go through the same Gateway. If the two calls use different GWs, the delay is minimal. This is a known AS5300 Gateway IOS bug.
|
H323.ini
| Configuration Affected - Allows CMA (TNT) to use the fast start (H.323 fast connect) procedure for outbound calls. Note that currently load testing reveals a 2% failure rate for *T transfers where the outbound call was fast started.
[H323]
FastStartOutbound=[On/Off]
Default is Off.
If FastStartOutbound is set to On, the RADVision stack config file (referred to by the VendorConfig setting in H323.ini) must also be changed as follows. At the end of the Q931 section (starts with "1 Q931 = 0") the following line should be added:
h245Tunneling = 1
|
H323.ini
| The beep phrase location has changed.
RecordBeepContainer=file:////home2/spmaster/r410/prompts/voice1/SY/USENGLISH/440beep.wav.
|
TNT/parms/Samples/DialMap.ini
| Combine DialMap.ini file from SMS and CMA (TNT).
$PARMLIB/apps/SMS_Notify/DialMap.ini
is now obsolete (no longer used).
This change combines the DialMap.ini file for $PARMLIB/apps/SMS_Notify and $PARMLIB/TNT/parms into one unit, where the latter file is the only one used.
Sections affected (showing old format):
[PhoneFormat]
SMS-MAPPING
[SMS-MAPPING]
International
[SMS-MAPPING:International]
FromRegExp=.*
ToRegExp=^(804)$0(762)$1([0-9]{4})$2$
Constraint=None
Return=$t0$t1$t2
|
FaxPrint.ini
| New attribute EnvelopeFrom is added to FaxPrint.ini [FAX] section. Legislative value is billing_number or email. FaxPrint uses this value to set the From field when sending a fax to a fax machine.
[FAX]
EnvelopeFrom=billing_number
|
UM.ini
| New configurable in UMConfig section, MailServer. Valid values are Netscape and swc_mx51. (Software.com Kx is not supported in uOne 4.2s). Sample file defaults to Netscape.
[UMConfig]
MailServer=swc_mx51
|
MWI_OnOff.ini
| Added _FROM_ as specified in Text Paging design.
The configurables are of the following format. The section name is the language supported
[language]
VoiceUrgentMessage=<Text>
VoiceNormalMessage=<Text>
UrgentMessage=<Text>
FaxNormalMessage=<Text>
EmailUrgentMessage=<Text>
EmailNormalMessage=<Text>
<Text> may include the string FROM which is replaced with either the name or e-mail address of the sender of the message.
For Example, for English:
[eng]
VoiceUrgentMessage=You have received an Urgent Voice Message from _FROM_
VoiceNormalMessage=You have received a Voice Message from _FROM_
FaxUrgentMessage=You have received an Urgent Fax Message from _FROM_
FaxNormalMessage=You have received a Fax Message from _FROM_
EmailUrgentMessage=You have received an Urgent Email Message from _FROM_
EmailNormalMessage=You have received an Email Message from _FROM_
|
MWI_OnOff.ini
| A new configurable was added to MWI_OnOff.ini, UnknownSender, is used to replace the from address/name in the MWI text page message if the from address is the same as the to address as in a voice message from an unknown caller.
"You have received an Urgent Voice Message from an Unknown Sender."
This configurable should be added for each language supported by MWI.
[eng]
VoiceUrgentMessage=You have received an Urgent Voice Message from _FROM_
VoiceNormalMessage=You have received a Voice Message from _FROM_
FaxUrgentMessage=You have received an Urgent Fax Message from _FROM_
FaxNormalMessage=You have received a Fax Message from _FROM_
EmailUrgentMessage=You have received an Urgent Email Message from _FROM_
EmailNormalMessage=You have received an Email Message from _FROM_
--UnknownSender=an Unknown Sender
[dut]
VoiceUrgentMessage=DUTCHYou have received an Urgent Voice Message from _FROM_
VoiceNormalMessage=DUTCHYou have received a Voice Message from _FROM_
FaxUrgentMessage=DUTCHYou have received an Urgent Fax Message from _FROM_
FaxNormalMessage=DUTCHYou have received a Fax Message from _FROM_
EmailUrgentMessage=DUTCHYou have received an Urgent Email Message from _FROM_
EmailNormalMessage=DUTCHYou have received an Email Message from _FROM_ --UnknownSender=DUTCHan Unknown Sender
|
schemaConfig.ini
| Add userSecFolderName=secondaryphonenumber to [specialAttrNames] section.
|
TNT RADvision files
| Refer to samples for changes.
|
Table 5: Seviceability Upgrade Information for Release 4.2s
| 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 SNMP MIBS and reload the new MIBs provided with uOne 4.2s.
|
ADMIN/cgi-bin/oam.ini
| For TNT reports and SNMP statistics, make the following changes to the oam.ini:
A. Add H323 to Event Log section at end of pattern= line.
B. Add new Community section:
[community_String]
tag=APP
communityString:hostname1:public:public
communictyString:*:public:public
|
SPsnmp.ini
| Add following section:
[TrapCommunityString]
TRAPCOMMUNITY=public
Remove TNT from MANAGEDOBJECTLIST parameter.
MANAGEDOBJECTLIST=APP
|
- Symptoms: A. The spoken name, greetings, voice messages sound garbled, or
B. On systems employing G.729, TTS output sounds garbled.
- Conditions: 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.
Symptom B occurs only when the system is configured for using G.729. This is because TTS output is G.711 and the system expects G.729, resulting in codec mismatch.
- The quickconfig tool does not configure the dynamic codec switching completely, nor should you attempt to do this manually.
- Workaround: The workaround for Symptom A is to ensure that codecs match, by rerecording the garbled audio using uOne. The workaround for Symptom B is to use G.711 only for systems configured with TTS.
- Symptom: In uOne 4.2, the snmpd daemon can fail under certain conditions, thus future snmp requests will not respond and applications (eg. uOne Manager) that use the snmp mibs will show no data.
- Condition: If the uOne server is running under heavy load there exists more than 48 applications agents (eg. UM, FaxPrint, MWI_Notify, MWI_OnOff, TNTOBJECT, LogRemover, SMS_Notify), and snmp requests are made for the agent run table (eg. uOne@ Manager State Information Screen), then snmp will core dump.
- Workaround: There is no workaround, except to restart snmpd after a failure.
- 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
- This error does not affect deleting non-modified administrators.
- 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) is modified, an error is reported when attempting to delete the modified administrator. This error does not affect deleting non-modified administrators.
- Workaround: Determine if unsupported non-RFC2060 utility is provided by server to remove base level folders if determined cleanup is necessary.
- Further problem description:
- Ability to rename admin folder not permitted in design of IMAP as provided in RFC 2060. Does not appear to affect performance.
- Symptom: In uOne 4.2.1, uOne Manager reports based on COI(Comunity's 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 1 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 COI's defined above. Selecting ou=customer1,o=cisco.com will correctly only report on the ou=customer1,o=cisco.com community.
- Workaround: If the activity for these two community's 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 over lap completely. Keeping community's on the same level would accomplish this.
- When an email 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.
- After recording 180 seconds of silence, the caller is not allowed to send it 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.
- Symptom: In 4.2.1 uOne, uOne Manager reports don't show current information even though DataCollector has run recently. eg. uOne Manager may show data for today's report up to noon, even though DataCollector ran at 3pm today.
- Condition: If activity is high and the uOne Manager server's DataCollector can not process all of the log files in a timely manner, then reports will be delayed.
- Workaround: Running DataCollector again will not speed up the availability of the 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 Information Logging in UM 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 fast, at the expense of losing the UM Application Summary Report. Re-engineering how many central log servers are deployed may need to be revisited to increase performance. Possibly multiple uOne Manager domains could be created.
- Charge Number field for the outbound calls in watch h323 entries screen in umcli will always be empty whether call is gateway routed or gatekeeper routed. There is no workaround for this problem.
- 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.
- After leaving a message, while hearing "Message Sent", press *9, uOne does not exit. Same thing happens after subscriber saves a message and presses *9 while hearing "Message saved".
- Add a new user in UMSA. Enter the user e-mail address in upper and lower case JamesJones@cisco.com. Submit and all is ok. Go in to Netscape to admin the user account and Netscape comes back with "Invalid e-mail address uid must be in lower case etc. As far as has been determined this has no negative effect on PMA/UMSA/UM.
- Symptom: Netscape cannot find a valid email address. Administrator receives the message: Invalid e-mail address uid must be in lower case..."
- Condition: Subscriber email address was entered into UMSA with upper and lower case such as JamesJones@company.com.
- Workaround: Make sure all email addresses are entered in lower case.
- Symptom: A voice message sent a subscriber is logged as VoiceBroadcast if the subscriber is added to a TO list which contains a broadcast list.
- Condition: Send a broad voice message 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.
- From enclosure: Release-note3
- 1. Run command "stop system", then "start system" in umcli. 2. MWI_OnOff takes 17 minutes to resume processing.
- From enclosure: Release-note
- Symptom: MWI_OnOff can take 17 minutes to recover from MWI server cycle.
- Condition: When MWI_OnOff (MWI client) is communicating with a TNT with SMDI on another host (MWI server), if the processes on the MWI server host are cycled (i.e. "stop system" followed by a "start system" using umcli), if the MWI_OnOff is connected to the MWI server, MWI_OnOff stops sending MWI "set indicator on" requests to the MWI server. There is a 17 minute timeout before processing resumes.
- Workaround: The workaround is to cycle MWI_Notify and MWI_OnOff on the MWI client host.
- Symptom: Cannot use "start system" in UMCLI to start all objects.
- Condition: This will only occur if the hostname is greater than 15 characters.
- Workaround: Make sure the hostname is less than 15 characters.
- 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.
- 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. This can be circumvented by either moving the file (renaming it) or by removing it (the former is preferred). Then when the system is started, LOGSUB will see that there is no Network.Data file and will create one in an initial state.
- The corrupt Network.Data file can be created whenever a Gateserver running as a LogClient is aborted externally (ie kill -9) or is brought down by a power failure or the like. Remember that a Gateserver running as a LogServer is also running as a LogClient, so the problem can happen on a LogServer as well.
- There is currently no way to view the Network.Data file to determine if the file is corrupt, so if LOGSUB cores during the attempt to start the Gateserver, try the above to determine if that is the problem that you are encountering.
- Symptom: When the main subscriber access number is called you are placed in a subscribers mailbox.
- Condition: A subscriber has been setup with a phone number the same as the subscriber access number.
- Workaround: Change the subscribers phone number to another number.
- Symptom: In 4.2.1 uOne, 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 (eg. 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.
- 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.
- Symptoms: (1) SNR Paging will not read back to the caller a paging source.
- (2) The UMCLI watch h323 states screen is cluttered with transport address (eg. TA: ###.##.###.##:xxxx where #'s represent the ip address and x's represent the port number).
- Condition: This condition occurs when a call comes into the system from a phone with no ANI.
- Workaround: None.
- If SMTP server malfunctions, uOne will hang.
- During a load test, the SMTP server malfunctioned (due to disk space) such that it could not properly provide SMTP service. It would accept TCP connections to the SMTP port, but would not response to requests sent over the connection. When the SMTP server is in this state, I noticed several uOne processes that had been in a hung state for hours. The hanging processes were sending messages to SMTP server at that time.
- Workaround: Prevent SMTP malfunctions.
- Release-note:
- Symptom: UMSA: Add/Mod Sub displays COS with first character truncated of COS name.
- Conditions: UMSA: Add/Mod COS with COS name beginning with lowercase letter.
- Workaround: Use 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.
- 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. This will be noted in the Operations Guide Document also.
- Symptom: In uOne 4.2.1, umcli watch acb and watch cma screens 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.
- Symptom: In 4.2.1 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 sight of 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
- reload web page thru browser
- Symptom: In the UMSA modify/delete subscriber search field, searching on location can neglect to return all possible entries.
- Condition: The search filter for Subscriber Location expects a numerical value rather than the text-based description of the location.
- Workaround: Search on the numerical value associated with the location.
- Symptom: UM hangs and calls (inbound/outbound) got cut after 2 hours.
- Condition: With extremely long calls (hours in duration), the call may be dropped causing UM process to hang.
- Workaround: There is no workaround.
- 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 much hang up, dial uOne back and login again.
- Call in to a subscriber with 1 SNR number and 1 SNR Pager setup. When uOne asks the caller to record name, caller records a name and press 1 to end recording. Then SNR sequence starts, 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 that end 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.
- This only happens when: 1. The caller presses 1 after recording his name. 2. The called party picks up the phone and presses 2 to end the call after a while or does not press any key.
- Workaround: When the caller records his name, don't press any key to end the recording. uOne ends it by itself.
- Symptom: UM may terminate when an email 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 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.
- Customer will see erroneous data on watch screens in umcli. This will happen when the customer looses connectivity. The workaround for this problem is to stop and start cma.
- Symptom: If subscriber has attendant coverage on, and the attendant coverage person does not answer the call, uOne plays "Your party is not answering. Please leave a message after the tone". Although the message will goes to the subscriber's mail box, this prompt misleads the caller to think the message to be recorded will goes to the attendant coverage person's mail box.
- Condition: 1. Caller leaves a message for a subscriber with attendant coverage. 2. While listening to the subscriber's mail box greeting, caller presses 0 to transfer to the attendant coverage person. 3. The attendant coverage person does not answer the phone. The caller will hear "Your party is not answering. Please leave a message after the tone". This prompt is not clear on who's mail box the message will goes to.
- If the caller records a message and sends, the message goes to the subscriber's mail box.
- Symptom: Call does not receive 30 second warning that he/she is running out of time to leave the message.
- Condition: When COS attribute "Max. Len. of Voice Messages" is greater than 300 seconds, the caller does not receive a 30 second warning.
- Workaround: Set the value to less than 300 seconds.
- Symptom: 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.
- Symptom: In uOne 4.2, TNTOBJECT may fail to start after initial configuration.
- Condition: If a uOne system with no prompt packages has been loaded and has been setup using quickconfig with the intention of this uOne server to only run MWI, FaxPrint or SMS_Notify, then TNTOBJECT will fail to start. This is due to a missing prompt that TNTOBJECT requires that was never installed.
- Workaround: Install the prompt package on this uOne server and reset the server.
- When sending message using the dial by name feature for multi line subscribers, uOne would not recognize the names entered. The system kept prompting for entering more letters or that the name could not be found although there was only one subscriber with the last name entered.
- Condition: The entered last name (John) matches other last names (Kohnke or Loinny) because of the way a telephone keypad works.
- Symptom: Pressing *9 starts outdialing instead of canceling call.
- Condition: If the subscriber is attempting to reply to a message and presses *9 to cancel the call, the system starts outdialing instead of canceling the call.
- Workaround: None.
- Symptom: In uOne 4.2, DTMF detection will fail under certain configuration combinations.
- Condition: If the uOne server was setup with quickconfig and RTP DTMF Detect was selected, then outbound DTMF detection will fail.
- Workaround: Configure RTPBridgeType=GateServer in /home2/spmaster/r410/TNT/parms/H323.ini and restart TNT(CMA).
- Symptom: A subscriber modifies their email password via PMA and can no longer log into secondary phone lines.
- Condition: If the subscriber uses PMA to change their email password, the password is not sync'd between primary phone line and secondary phone lines. Thus the secondary phone lines will have the old password and the primary phone lines will have the new password.
- Workaround: 1) The subscriber can change his/her password via the TUI to resync the passwords. 2) The administrator can change the password via UMSA to resync the passwords.
- Symptom: In uOne 4.2, system memory loss is detected under a constant load.
- Condition: If umcli interactive screens have been left open, then a umcli memory growth will occur. This will happen on the watch cma groups, watch cma sessions, and watch cma entries screens.
- Workaround: The memory lost will be freed once the umcli session is exited. To use these screen interactively without causing memory loss, umcli -s (non-interactive) could be used in a recursive script.
- Symptom: Call is disconnected without being accepted by uOne GateServer.
- Condition: When routers exists between GateServers and other components and ttl is equal to 2, IP packets expire after two hops. After the second hop the IP drops causing the GateServer to never reply to the GateWay that it accepted the call. Therefore the call is disconnected.
- Workaround: Comment the following line out of the /etc/rc2.d/S99uonetune:
- ndd -set /dev/ip ip_def_ttl 2
- Symptom: umcli watch acb entries shows connections between MWI_OnOff and TNT that are no longer present.
- Condition: When the connection from MWI_OnOff to TNT times out, the memory mapped file is not getting updated with the removal of the connection from MWI_OnOff's section.
- Workaround: Ignore the connections to TNT in the MWI_OnOff section.
The following section lists errors, changes, or omissions in the uOne Release 4.2s documentation set. Documentation addendum, errata sheets, and updates are made available on CCO on an ongoing basis.
Although it is not Cisco policy to reference direct URL links in documentation, exceptions are made here to support other uOne documents. Should these links become outdated or invalid, please contact your Account Representative or the Technical Assistance Center (TAC) for assistance.
Errors in uOne 4.2s documents, if any, are to be covered in this section.
In the Gateserver Installation and Configuration Manual, some example start-up configuration entries for a gateway (AS 5300) are shown in Appendix A, "Case Studies - Gateway and Gatekeeper". An important entry was omitted in Example A-2, "Sample gateway startup-config for outbound calls", starting on page A-7. The missing entry is a dial-peer voip type.
The missing dial-peer is required to support VoIP outbound calls (for example, SNR).
dial-peer voice 201 voip
incoming called-number 6.........
dtmf-relay h245-signal
codec g711ulaw
!
This dial-peer opens a call-control channel for the outbound call. It is very similar to a POTS dial-peer from the PSTN side of the 5300. Without this entry to establish an incoming voip dial-peer, the 5300 defaults to a dial-peer 0, which lacks the necessary codec and DTMF relay mechanism to support uOne outbound calls.
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.
Posted: Mon Sep 25 20:30:49 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
