Question


What Fix Updates have been released for Unified Messaging for BVR?


Answer


The following is a complete listing of Fix Updates for Unified Messaging for Blueworx Voice Response, and the fixes included within them, with the most recent Fix updates at the top.


Fix updates can be downloaded from the Blueworx FTP site. For more information go to How to obtain fixes for Unified Messaging for BVR.


UM changes:



 






 




Fix Level 4.2.0.162

Fix release date: 23 Nov 2018
Status: Current




Ticket#ProblemResolution
1523The moveprofile command does not copy the aliases to the new subscriber number.

The IMC_MoveProfile custom server did not previously have code to load/add aliases but did unload the details of those aliases in the intcnphn database field.


The IMC_MoveProfile custom server has been enhanced to also load aliases which were unloaded.

The installation of the new custom server will replace the existing directories which you may have data within from previous use of the command. If you have a lot of data for profiles and mailboxes within
/home/dirTalk/current_dir/ca/IMC_MoveProfile_dir or
/home/dirTalk/current_dir/ca/IMC_MoveProfile_dir/utils, please move (or copy and/or delete) it before using UM_ptf_mgr, to backup the old custom server and import the new one. This will both reduce the size of the backup and safeguard your data. The files to move (or copy and/or delete) will start with numbers rather than letters.


  Weak password security.Enhancements have been made to the UM password logon security. For details of these, refer to the following Help Center article:
/hc/en-us/articles/360012481594


 














Fix Level 4.2.0.161

Fix release date: 05 Jul 2017
Status: Current





























Ticket#ProblemResolution
1089The IMC_SMDI_Client custom server, in addition to logging into IMC_SMDI_Client.log, is also logging to DTstatus.out and this causes unnecessary utilization of space and makes the DTstatus.out file unusable.Modified IMC_SMDI_Client custom server so that it will write to DTstatus.out only when the LoggingLevel is greater than 3.
1017MWI is not being sent for aliases upon message deletion and therefore it is possible it could be out-of-sync with the database.The mwi_config command can now be used to verify triggers are working correctly with the -c option which must be followed by a test number.
The mwi_config command also now supports the -C option to check that counts in the application profile table match those in the mailbox table and the -reset option to run a general reset on all message waiting indicators.
For further details please use:
mwi_config -h
to see the new options and syntax.
1195The moveprofile command has never had code added to support MR_SCHED table.The IMC_MoveProfile custom server and the moveprofile command has been enhanced to also unload and load enhanced menu routing schedules for enhanced menu routing applications.
1287Using the moveprofile -l on SurveyForms subscriber receives the message "Error: loading profile" due to the use of a semicolon in a database field (referral_number).Fixed IMC_MoveProfile (via the moveprofile command) to support Survey mailboxes and the use of semicolon.


 














Fix Level 4.2.0.160 

Fix release date: 12 Jan 2016
Status: Current














APARDescription
IV78756Fixed a problem that caused a discrepancy of the times in the email notification header and in the body. In IMC_NOTIFY (notify) State table we changed the following:
1)
    SSV545=SV545;
    SV545=SV485;

    "Send notification data to IMC_Sendmail Custom Server"

to
     SSV545=SV545;
     IF SV485!="" THEN
        SV545=SV485;
     ENDIF

     "Send notification data to IMC_Sendmail Custom Server"

2) further down the code:
	
     SSV545=SV545;
     SV545=SV485;

     "Send notification data to IMC_Notify Custom Server"

to
     SSV545=SV545;
     IF SV485!="" THEN
        SV545=SV485;
     ENDIF

     "Send notification data to IMC_Notify Custom Server"

We also found the same bug in IMC_NOTIFY_VPIM code and fixed as below:
     "Set TimeZone"
     IF SV415!="" THEN
        SV545=SV415;


 














Fix Level 4.2.0.159 

Fix release date: 25 Feb 2015
Status: Current














APARDescription
IV68661Fixed IMC_Sendmail to prevent a coredump which could occur after sending a number of genuine e-mails with voice messages attached if it then received details of a voice message which did not exist or was somehow inaccessible.


 














Fix Level 4.2.0.158 

Fix release date: 23 Dec 2014
Status: Preventative Maintenance














APARDescription
IV61428This Fix Update includes the following Unified Messaging enhancements:


 














Fix Level 4.2.0.157 

Fix release date: 30 May 2014
Status: Preventative Maintenance














APARDescription
IV56319Added the -R flag to the mwi_config utility so when mwi_config -R is issued this will make sure mailboxes with vpim_msg_del_pref set to 1 do not have mwi set.

For more details, refer to the following article:
/hc/en-us/articles/216697317


 














Fix Level 4.2.0.156 

Fix release date: 19 Nov 2013
Status: Preventative Maintenance














APARDescription
IV48024Fixed a problem that was caused by a space at the end the changed password so it meant they would not match. It was resolved by removing the space.


 














Fix Level 4.2.0.155 

Fix release date: 26 Jun 2013
Status: Superseded














APARDescription
IV40787Improved reconnection of IMC_MR_Retrieve to DB2 after a temporary interruption of DB2 connectivity.


 














Fix Level 4.2.0.154 

Fix release date: 21 Feb 2013
Status: Superseded


















APARDescription
IV32857Fixed a problem where passwords longer than the maximum password length that was set in the .ini file could be set.
IV33866Fixed a problem where messages that were longer than the maximum message length were able to be left.


Internal Defect fix



  • Enhancement and clean-up of IMC_Pager, IMC_Notify and IMC_Sendmail logging at LoggingLevel=5 to aid in easier diagnosis of potential issues with cached notification templates and partial matching logic.


 














Fix Level 4.2.0.153 

Fix release date: 4 Apr 2012
Status: Preventative Maintenance














APARDescription
IV15308MRCP TTS capability has been added to remote email functionality of Unified Messaging with WebSphere Voice Response V6.1. This will allow the configuration of the MRCP for State Tables feature in WVR V6.1 to point at any supported MRCP technology with Text-to-Speech (TTS) for the reading of remote emails.

For further details, refer to the Help Center article:
/hc/en-us/articles/216697137


 














Fix Level 4.2.0.152 

Fix release date: 12 May 2011
Status: Preventative Maintenance














APARDescription
IZ98077Resolved problem where broadcast and distribution list messages to VPIM destinations (particularly where VPIM addressing uses LDAP server rather than remote systems configuration) are not sent.


 














Fix Level 4.2.0.151 

Fix release date: 22 Nov 2010
Status: Preventative Maintenance














APARDescription
IZ81497Fixed two problems with VPIM ingoing/outging mail:

  1. some incoming VPIM mail did not include 'To' headers but instead the sendmail program was told the recipient using the SMTP RCPT command only, this resulted in the mail not being processed unless sendmail.cf also had the following setting:

    # action to take if there are no recipients in the message
    O NoRecipientAction=add-to

    However when multiple recipients were given as SMTP RCPT commands they would not all appear in the mail headers (the original aliases configuration did not have this problem). To overcome this limitation of AIX sendmail with the use of regex, if your system is subject to receiving VPIM mail with multiple recipients specified by SMTP RCTP command only it is now recommended that a unique masqueraded name be used for the system (eg, one with begins with "vpim") for vpim mail and a rule be added to sendmail.cf as follows under ruleset 0, in this example the hostname is "jupiter":

    R$+< @ vpim . jupiter . uk . ibm . com >           $#vpim$:$1

    Ensure there is a tab between the > and the rest of the entry. You then need to add the custom vpim mailer as follows under the mailer definitions:

    #####################################
    ###   VPIM Mailer specification   ###
    #####################################
    Mvpim,   P=/home/dirTalk/current_dir/ca/IMC_Getmail_dir/dtmailin2,
                    F=lsFn, S=10, R=20, A=dtmailin2 $u $h,
                    D=/home/dirTalk/current_dir/ca/IMC_Getmail_dir,
                    U=dtuser:staff

    (again, ensure there is a tab between Mvpim and the rest of the entry as for other mailers).

    This uses a new variant of the original dtmailin program called dtmailin2 (shipped in this PTF) which prevents duplicate mails from being received for the same message, which is otherwise a side-effect of the new configuration. Please ensure that dtmailin2 has the same permissions as dtmailin did, eg, with:

    chmod ug+s $CUR_DIR/ca/IMC_Getmail_dir/dtmailin2

  2. all outgoing VPIM mail was also sent to the alias_id and hence was not transmitted, this can be fixed by adding the hostname to the numeric regex definition in sendmail.cf (see technote referenced below), for example if the hostname is "jupiter" then the regex definition would be:

    Knumeric regex -aalias_id ^[0-9 <>]+@jupiter.*


For further details refer to the TechNote at the following:
/hc/en-us/articles/219841187


Internal Defect fixes



  • Fixed an issue which resulted in bad conversion of data to au format of audio files.

  • Fixed a problem with UM Web Interface when logging in with an encrypted password.


 














Fix Level 4.2.0.150 

Fix release date: 18 Jun 2010
Status: Preventative Maintenance






















APARDescription
IZ73950Fixed a problem with creating notification schedules for pager types other than 0 or 1.
IZ73951Fixed a problem with reading back a remote list member in a Distribution list.
IZ76181The code to enable password encryption in the Telephone User Interface (TUI) when appropriate configuration is present has now been shipped.

(The code to enable the same functionality in other interfaces was already shipped in PTF 4.2.0.139.)

This does not encrypt passwords unless a setting PasswordEncryption=yes is present under the [Passwords] section of IMC_MessageCenter.ini.

If password encryption is configured (PasswordEncryption=yes is present under the [Passwords] section of IMC_MessageCenter.ini) then passwords changed by users (in TUI or web interface) will be encrypted.

The TUI code shipped is based on the PTF README for 4.2.0.139 but also includes the following fixes/changes:

  • the validation of passwords always checks against both encryptedand unencrypted passwords when PasswordEncryption=yes or PasswordEncryption=no so that if password encryption is turned off users with encrypted passwords do not need to have their passwords reset, hence PasswordEncryption=yes refers only to whether an entered password will be encrypted, not to whether the validation includes the possibility of the password being encrypted.

  • the mailbox is properly set to be "in use" to prevent two users from logging into the same mailbox at the same time.

  • password encryption and password history are supported by the first time user feature as well as regular password entry / password change.

  • STCallIdent 51 is used to call IMC_GETSTRG to obtain a password so that customizations to modify user entered with STCallIdent 50 will not be used to modify the password.



As per the PTF README for 4.2.0.139 the following still applies:

Note that passwords entered by an administrator will continue to be unencrypted and in some circumstances retrievable by an administrator - it is recommended that users be forced to change their passwords as soon as they log on after having their passwords reset by an administrator by the administrator also setting the password_change_date to a date in the past.

Note that this encrypted password support is not at present compatible with the UniquePwds=yes setting for shared numbers with sub-mailboxes. If you use shared numbers with sub-mailboxes and the UniquePwds=yes setting then you will not be able to use PasswordEncryption=yes.

However a note included in the PTF README for 4.2.0.139 which indicated that if the user id is changed (for example by moveuser, makeshared, makealias or moveprofile) the encrypted password could no longer be used and the password would have to be reset was incorrect as measures have been taken to preserve a detail of the original user id used in the encryption algorithm.


Internal Defect fix



  • Fixed a problem with searching email on Web Interface as Subscriber type 1 and Telephony Portal. The system was only searching in LDAP but now it has been modified to search in the UM system also.


 














Fix Level 4.2.0.149 

Fix release date: 15 Apr 2010
Status: Preventative Maintenance


















APARDescription
IZ74146Unified Messaging has been modified and thoroughly re-tested to work correctly on BVR 6.1 as well as BVR 4.2. All Unified Messaging features are supported on BVR 6.1 with the following exceptions:
1) Simple Message Desk Interface (SMDI)
2) Use of the state table driven telephony user interface with text-to-speech (TTS) and speech recognition servers such as Websphere Voice Server. The VoiceXML driven Voice Interface is supported however.
3) Because of item 2 above, the ability to access email from the telephony user interface.
The features listed above are not currently supported when used with BVR 6.1, but are still fully supported on BVR 4.2.

For the details of the new level of support, refer to the Technote article:
/hc/en-us/articles/216122518
IZ73406When subscriber type 1 sends a voice message to an e-mail address of another subscriber and selects urgent or private message attributes the Sensitivity and Importance e-mail headers were not always being set. This has been fixed.


 














Fix Level 4.2.0.148 

Fix release date: 11 Mar 2010
Status: Superseded


















APARDescription
IZ70299A problem where using a TTS engine to read the e-mail address of survey mailbox subscribers on the telephone resulted in an error_id100 and technical difficulties message has been resolved.

Also, fixed a problem where a subscriber type 12 could not select a different TTS_Engine or no TTS_Engine using a partition or subscriber type INI file setting.
IZ70330Fixed a problem where a subscriber type 12 mailbox logon via web interface would report the error "Error 500: Unable to compile class for JSP" using WAS V5.1.


Internal Defects fixes



  • Fixed .au voice mail attachments which were generated as 0 byte attachments.

  • Fixed a problem where a pager number for subscriber type 0, that has just been set, does not get replayed.

  • Subscriber type 1 control menu returns to main menu when pressing *1 and *2.

  • Fixed a problem where voice segments for IMC_RECORDCOMP2 were recorded incorrectly. They now have the correct contents.

  • Fixed a problem with the uncompress_messages utility which reported "No such file or directory".

  • Removed option to select IMAP4 client voice type as UM 4.2 does not support Real Audio.

  • Fixed a problem where web interface would allow an existing password be used again.

  • Fixed a problem on the web interface where subscriber type 1 and 4 mailboxes that contain messages that have been read are still displayed in bold text instead if normal text.

  • Voice segment 10040 "We apologize that this survey is still under construction." was omitted from PTF 146. It has now been included.


 














Fix Level 4.2.0.147 

Fix release date: 18 Feb 2010
Status: Superseded














APARDescription
IZ66406IBM Unified Messaging now supports playback and recording of uncompressed distribution list names. Simply set CompressionType=0 under the [XXX_DlistNames] heading in IMC_MessageCenter.ini to use this. IBM Unified Messaging now also has more consistent support for playing back audio names from other IBM Unified Messaging systems in both compressed and uncompressed formats.


Internal Defects fixes



  • This fix allows IMC_TRMBONECALL and IMC_XFER_DO (and therefore IMC_Stats.log) to correctly identify a successful transfer when the original caller hangs up after a successful trombone.


 














Fix Level 4.2.0.146 

Fix release date: 19 Nov 2009
Status: Superseded














APARDescription
IZ65039A new way of using UM to automate surveys has been added. This uses a new subscriber type, 12, Survey Mailboxes. Simply create a subscriber of type 12 and log in via the telephone or web interface to configure surveys which callers can answer.

Full documentation for this new feature is available in the UM Information Center and can be accessed at the following URL:

http://publib.boulder.ibm.com/infocenter/umaix/v4r2m0/index.jsp



 














Fix Level 4.2.0.145 

Fix release date: 11 Nov 2009
Status: Preventative Maintenance


























APARDescription
IZ60572A fix to prevent IMC_IMAP4_Server coredumping under certain circumstances when a mailbox is accessed using Outlook via IMAP4.
IZ60742Findme functionality is working properly with the shared mailboxes. The system prompts the caller to record their name as it works in the private mailboxes.
IZ62643If a user's password ends in one or more zeros, they can actually enter their password without the trailing trailing zeros and still get authenticated. Now user authentication works as designed when [Passwords]/PasswordEncryption field is set to Yes.
IZ63664Remote members can now be added to distribution lists for users in partitions with partition visibility (PartitionVisb) of "inter". For this to work the [XXX_MessageCenterAPI] setting AddRemoteMembers=yes must be set in IMC_MessageCenter.ini.


Internal Defects fixes



  • Spelling mistake in usage information for UM_ptf_mgr - spelt 'argument' as 'arguement'.


 














Fix Level 4.2.0.144 

Fix release date: 5 Oct 2009
Status: Preventative Maintenance


























APARDescription
IZ55990Retrieving a message via web interface now sends an acknowledgement as designed.
IZ58431A problem with adding aliases which are substrings of other aliases has been fixed. Such aliases can now be added without problems (if they are not duplicates of existing aliases or mailbox numbers).
IZ58674An acknowledged message on the web interface now shows subject field as a more appropriate subject ie. "Voice message acknowledgement".
IZ58675Several issues with Enhanced Menu Routing have been fixed:

  • Transfer numbers can be correctly set for option 0 on TUI.

  • Can return to schedule choice menu from holiday menu by pressing # key.

  • No longer receive abnormal termination alarms when callers hang up.

  • Backup Number ring time is now set correctly according to ini file parameter MRBupRingTime.



Other Features and Internal Defects fixes



  • The IMC_DlistReview custom server will now be imported in the AUTOEXEC state in this PTF.

  • The UM_ptf_mgr tool can now install more than one PTF automatically. If you run UM_ptf_mgr with the -l flag, eg.
    UM_ptf_mgr -l
    it will attempt to import all unimported PTFs in sequence. PTFs can still be imported individually using the PTF fix level number if required.


 














Fix Level 4.2.0.143 

Fix release date: 23 Jun 2009
Status: Superseded


































APARDescription
IZ49498When sending a message to a distribution list not everyone on the distribution list received the message. This problem was caused by a logic error in the IMC_SEND_MSG_CB state table and has now been fixed.
IZ49657A change has been made so that for subscribers of types 1, 2 and 3 (and derivatives thereof) UM need not transfer callers to an operator after the mailbox is full. To use this either ensure that no OperatorNum is set in the INI files and that the subscriber's operator_number is also empty or set DisableOperator=yes in the INI file. (Subscriber types 5, 6, 7 and 8 already did not transfer to an operator when a mailbox was full.)
IZ49702Rules for allowed/forbidden numbers in barring.rules for the menurouting type were being used on the telephone user interface (via the IMC_CHK_MR state table) but a different type ("transfer") was being used on the web interface. This has been fixed so that both the telephone and the web interface use the same type ("menurouting") and hence both allow/forbid numbers in the same way (as long as IMC_CHK_MR has not been customized).
IZ52002A fix for subscriber type 1 mailboxes ("local and remote") to play the audioname of a sender to which a reply is being sent when the choice is offered to send the reply to the sender's e-mail or voice mailbox.
IZ52250The TUI for enhanced menu routing now allows the ring time before trying the backup number to be set.
IZ52712Occurrences of stray characters in menu routing number fields in the web interface should have been eliminated with this fix.


Other Features and Internal Defects fixes



  • Password encryption is working fine now with the MinTimeReuse=0 setting.

  • A change has been made to calls transferred by trombone for the benefit of customers whom transfer incoming fax calls to a fax server which expects the profile to which the fax message is to be sent to be set as the calling number.

    As with existing UM tromboning support for ISDN support this change assumes that the North American Numbering Plan is in use and hence that the calling number (the profile in this case) should be 10 digits, using a number type of 2 (national) and a number plan of 1 (ISDN). Screening is set to 3 (network provided) and presentation is set to 0 (allowed). If the system's environment is different to this then customization of this would be required as for other ISDN support in IMC_TRMBONEOUT.

    This change does not affect customers using the Brooktrout fax adapters for sending and receiving fax.


 














Fix Level 4.2.0.142 

Fix release date: 6 Apr 2009
Status: Superseded


























APARDescription
IZ42845A problem with the web interface being sometimes unable to make calls to play messages requested via a phone has been corrected.
IZ44101The ResetGreeting customization setting in IMC_STARTUP failed to allow greeting numbers above 12. This has now been corrected to allow the full range up to 255.
IZ44876VPIM rejected email messages will be placed in the correct path.
IZ45694A fix to prevent defunct (zombie) processes not being cleaned up by IMC_Pager after use of its silence detection for notification schedules which use a pager protocol of VRU1 or VRU2.


Internal Defects fixes



  • Subscriber type 0-3 caller menus have been updated to handle the NoVoiceKey case where a caller presses a key during or immediatelyafter the recording beep and no voice was recorded. Unhandled this could lead to the system playing the technical difficulties message and hanging up under this condition.

  • A problem wherein if a preferred name contained an apostrophe IMC_MoveProfile would not be able to set the name correctly during a load operation has been corrected.

  • A problem with MCIT setting AMIS Setup information when some fields are blank has been corrected.

  • Problems with configuring remote nodes in MCIT have been resolved, including the lifting of the requirement to enter an IP address which did not apply to AMIS nodes.

  • A situation where WVR could reject a password as invalid but an entry could still be entered in the table of old passwords has been corrected. This avoids the possibility of the invalid password being said at one time to not be valid and subsequently being said to have been used recently.

  • When a caller is recording their name for Find-me/Follow-me if theypressed # to end the recording then the system would play a beep and start recording a message (which for subscriber type 6 there is no escape from) without explanation. This has been corrected so that pressing # to end the recording simply allows the original Find-me/Follow-me operation to complete normally (unless a key is pressed to abort that).

  • A situation where a misconfiguration could result in a misleading error prompt but no error in the errorlog to track the problem to its cause has been patched so that an error appears in the errorlog and the error prompt is more useful.

  • A situation where a mailbox full condition could result in a potentially "infinite" (until the caller hangs up) number of transfer attempts to the operator has been corrected. Now a maximum of three attempts to the operator will be attempted when the mailbox is full, after which the call will be politely disconnected.

  • A case where the SIP From header wasn't correctly preserved when a call was tromboned in a SIP environment has been corrected.

  • A problem with vm_backup not backing up partition data and vm_restore not being able to restore mailboxes which are in partitions which are not already on the destination system has been corrected.

  • The command UM_ver will now produce alphabetically sorted output making it easier to compare different systems.

  • The changeuser command has been corrected so that it does not create unnecessary entries in the table of old passwords it now only creates such entries when the password is updated, reducing the size of the table and reducing the load that changeuser exerts.

  • Before Password Encryption if one person logged in to a mailbox, and then someone else on another channel also tried to log in to the same mailbox, the system would return a prompt indicating the mailbox was already in use and the second person logging in would have to press a special key if they still wanted to log in.
    The above behaviour stops working once activated password encryption. This is fixed now.

  • The moveprofile command stops truncating encrypted password.


 














Fix Level 4.2.0.141 

Fix release date: 10 Dec 2008
Status: Preventative Maintenance


























APARDescription
IZ35946VPIM messages sent using the LDAP lookup mechanism were being sent in WAV format instead of in 32KADPCM format since PTF 134 -
IZ13888 MESSAGES SENT TO AS AN EMAIL ARE NOT IN WAV FORMAT was applied. This fix ensures that all VPIM messages sent to VPIM destinations using LDAP or Remote Systems Administration methods are sent in 32KADPCM format.
IZ36321It is now possible (as it was before e-mail notification templates were introduced, but not since that time) to send VPIM messages by setting up a mailbox with vpim_address set to a VPIM address, vpim_msg_del_pref set to 1 or 2 and vpim_voice_type set to 2. This will not use an e-mail notification template but will instead use the standard VPIM format. This is obviously not recommended for large scale VPIM integrations, where Remote Systems Administration (RSA) and LDAP integration should continue to be used but may be used for testing or small scale integrations.
IZ37264Sample TUI menus to set ReachMe PIN have been provided for subscribe types 1, 2, 7 and 8.

To activate the sample menus (segments for which have been provided in the U.S. English text to speech voice) edit a copy of the new sbr_mnu_sch state table found in:

  • /usr/lpp/dirTalk/sw/MessageCenter/st_src


as indicated at the #TO ACTIVATE RECOMMENDED REACHME PIN MENUS comments - note that there are also #TO ACTIVATE ALTERNATIVE REACHME
PIN MENUS comments - the differences are:

The RECOMMENDED menus do not allow users to listen to the ReachMe PIN, do not play back the ReachMe PIN when it is being set and ask that the user enter the ReachMe PIN twice when attempting to set it, the second time as a verification of the PIN in a similar way to changing a password. This is considered a "secure" approach to setting ReachMe PIN.

The ALTERNATIVE menus are follow the design of the way the rest of the "number management" menus work, allowing a user to listen to the PIN entered as well as playing back the ReachMe PIN when it is being set and asking for confirmation that the number played back is correct. This is considered an "unsecure" approach to setting ReachMe PIN which may be preferable if users prefer the design to match the existing "number management" (call handling) menus.

The sample voice segments provided, namely:





























































6867To listen to your ReachMe number, press 1. To set your ReachMe number, press 2. To delete your ReachMe number, press 3. To set your ReachMe PIN, press 5. To delete your ReachMe PIN, press 6. To return, press 7.
6868Your ReachMe PIN is set to...
6869Please enter your ReachMe PIN, followed by #.
6870ReachMe PIN will be set to...
6871To confirm your ReachMe PIN, press 2. To cancel, press 7.
6872ReachMe PIN has been set.
6873Your ReachMe PIN has been deleted.
6874Please enter the new PIN again, followed by #, for verification
6875Your entry is not valid.
6876Your two entries were not the same.
6877Your ReachMe PIN has not been set.
6878You are entering your ReachMe PIN.
7867ReachMe menu
8867To listen to your ReachMe number, press 1. To set your ReachMe number, press 2. To delete your ReachMe number, press 3. To set your ReachMe PIN, press 5. To delete your ReachMe PIN, press 6. To return, press 7.


...have menus 6867 (and help 8867) designed for the RECOMMENDED
approach - in order to use the ALTERNATIVE approach these menus could
have the following added:

"To listen to your ReachMe PIN, press 4."

There is also scope to have an entire menu for ReachMe PIN, similar to the menu for ReachMe Number such as (RECOMMENDED approach):

"To set your ReachMe PIN, press 2. To delete your ReachMe PIN,
press 3. To return, press 7."

or (ALTERNATIVE approach):

"To listen to your ReachMe PIN, press 1, set your ReachMe PIN,
press 2. To delete your ReachMe PIN, press 3. To return, press 7."

...no sample segment(s) have been provided for such menus but example code is provided in sbr_mnu_sch under the ReachMePw label. In order for a higher level menu (such as IMC_SBR_MENU_02) to reach such a menu it would return code 304 in SV74 (menu_rc). No sample is provided for this as it is considered the sample placing the menu items in the existing reachme number menu is a more elegant way of introducing the feature.
IZ37038Enhanced menu routing has been fixed so that a prompt which says a caller can press a key to leave a message when a transfer is being attempted does not play when there is no mailbox for the caller to leave a message in.


Internal Defects fixes



  • An error message is now displayed when you try to run vm_backup as root.

  • Enhanced Menu Routing applications previously allowed number of menu repeats to be set up to 5 but values above 2 were always treated as a value of 2. Enhanced Menu Routing applications now correctly use number of menu repeats above 2.


 














Fix Level 4.2.0.140 

Fix release date: 31 Oct 2008
Status: Superceded


















APARDescription
IZ33338The "transfer to backup" / "terminate call" setting for enhanced menu routing on the web interface was giving the reverse of the expected behaviour on the TUI (so "terminate call" resulted in a transfer to backup and vice versa). The TUI has been corrected so that the correct behaviour according to the web interface setting is used.
IZ33447IMC_Broadcast doesn't core dump when the profile length of an alias is larger than MAX_PROFILE_LEN.


 














Fix Level 4.2.0.139 

Fix release date: 11 Sep 2008
Status: Preventative Maintenance






















APARDescription
IZ28478Fixed a problem where IMC_LDAP_Client would not timeout for 120 seconds if no LDAP configuration file is present in the system.

Now UM throws an error immediately if it can't find a LDAP configuration file.
IZ28183Fixed adjustment to pauses used in AMIS Analog reception of messages to ensure the sending system does not miss response to the end of message frame.
IZ29789It is now possible to specify custom Content-Type and Content-Disposition fields in template files for e-mails with attachments by adding these at the end of the file following a second --MessageBoundary. The following new fields are now supported in template files:
(primarily for IMC_Sendmail for e-mails with attachments, however IMC_Notify for e-mails without attachments and IMC_Pager for pager/SMS messages also support the msg_key and msg_create_time fields)

  • <content_type> - this will be audio/wav for WAV, audio/basic for AU and image/tiff for TIFF, if you want to have custom types you can specify them with a colon and a separator of a pipe character like this:
    <content_type:audio/x-wav; codec=31;|application/octet-stream|image/tiff>
    <file_type> - this will be wav for WAV, au for AU and tif for TIFF
    <msg_key> - this is the message key from the database
    <msg_create_time> - this is the message create time (seconds since 1970) from the database



For example you can change the default Content-Disposition from inline to attachment with a template file as follows:

From: non-mail-user@yourcompany.com
To: <receiver e-mail>
Subject: New <type>mail Message
 
--MessageBoundary
 
Simply open the attachment to this email, to receive the <type>mail.
 
<Day> <DD> <Mon> <YYYY> <HH>:<mm> <am/pm> <TZ>
 
You now have <new> New Messages and <saved> Saved Messages.
 
This is a system generated message. Please do not reply.
 
--MessageBoundary
Content-Type: <content_type>
Content-Disposition: attachment;
 filename="<msg_key><msg_create_time>.<file_type
>"
(note that the last line needs to end with a newline)


Other Features and Internal Defects fixes



  • The encrypted password information in an internal database table may now be used instead of the unencrypted password for mailboxes which is under some conditions retrievable by an adminstrator.

    The web and IMAP4 interfaces now support encrypting passwords the user enters and using the encrypted password if there is a PasswordEncryption=yes setting under the [Passwords] section in IMC_MessageCenter.ini.

    In order for the TUI to use encrypted passwords the following changes must be made:

    To IMC_LOGON:
    add the following LOCAL STRING : UsePWEncryption
    add the following code under the EnterPW: label








    OpenHostServerLink(CUSTOM_SERVER, IMC_GlobalVariables)
        edge EDGE_OPEN_HOST_UNSUCCESSFUL: Problems
       ;

       SendData(CUSTOM_SERVER, IMC_GlobalVariables, 10, GetSubVariable, "",
         SV20, SV149, SV102, SV396, Passwords, PasswordEncryption)
        edge EDGE_SEND_DATA_HOST_NOT_OPEN: Problems
       ;

       ReceiveData(CUSTOM_SERVER, IMC_GlobalVariable, 20, GetSubVariable,
                 UsePWEncryption)
        edge EDGE_RECEIVE_DATA_HOST_PROB: Problems
        edge EDGE_RECEIVE_DATA_HOST_NOT_OPEN: Problems
       ;

       CloseHostServerLink(CUSTOM_SERVER, IMC_GlobalVariables);

       AssignData(UsePWEncryption,TO_LOWERCASE,UsePWEncryption);

       IF UsePWEncryption="yes" THEN

        "Enter Password"
        PlayPrompt(FALSE, IMC_Prompt, 6104)
         edge EDGE_PP_LINE_PROBLEM: Problems
         edge EDGE_PP_NOTHING_PLAYED: Problems
         edge EDGE_HUP: Problems
        ;

        "Set GetKeyBuffer = NULL"
        GetKeyBuffer = "";

        "Set StrStopKey = NULL"
        StrStopKey = "";

        "Invoke GetString"
        InvokeStateTable(VIA_VARIABLE, IMC_GETSTRG, Start, 6,
         GetKeyBuffer,
         StrStopKey,
         21,
         1,
         50,
         GetString_rc)
        ;
        CASE GetString_rc OF
         WHEN 10: GOTO CheckPW; # Succeeded
         WHEN 20: GOTO NOT_OK;  # TooShort
         WHEN 30: GOTO NOT_OK;  # TooLong
         WHEN 50: GOTO GetPW;   # TimeOut
         WHEN 60: GOTO NO_RESULT;  # LastTimeOut
         WHEN 70: GOTO Close;   # CallerHup
         WHEN 80: GOTO Problems;# Problems
         OTHERWISE: GOTO Problems;
        ENDCASE

       CheckPW:
        rc = -1;

        OpenHostServerLink(CUSTOM_SERVER, IMC_Password)
        ;

        "Send to IMC_Password to check if the password is correct"
        SendData(CUSTOM_SERVER, IMC_Password, 60, CheckPassword,
                 MCSelectedProfile, GetKeyBuffer)
        ;

        ReceiveData(CUSTOM_SERVER, IMC_Password, 120, CheckPassword, rc)
         edge EDGE_RECEIVE_DATA_HOST_PROB:       Problems
        ;

        CloseHostServerLink(CUSTOM_SERVER, IMC_Password);

        IF (rc =  0) THEN #PASS_SUCCESS
          GOTO OK ;
        ELSE
          GOTO NOT_OK ;
        ENDIF

       ENDIF



    To IMC_STATS :
    add the following LOCAL STRING : UsePWEncryption
    add the following code under the Append: label :









       IF StatsID="CP" THEN # if the user has changed their password
        OpenHostServerLink(CUSTOM_SERVER, IMC_GlobalVariables)
         edge EDGE_OPEN_HOST_UNSUCCESSFUL: Problems
        ;
        SendData(CUSTOM_SERVER, IMC_GlobalVariables, 10, GetSubVariable, "",
          SV20, SV149, SV102, SV396, Passwords, PasswordEncryption)
         edge EDGE_SEND_DATA_HOST_NOT_OPEN: Problems
        ;

        ReceiveData(CUSTOM_SERVER, IMC_GlobalVariable, 20, GetSubVariable,
                       UsePWEncryption)
         edge EDGE_RECEIVE_DATA_HOST_PROB: Problems
         edge EDGE_RECEIVE_DATA_HOST_NOT_OPEN: Problems
        ;

        CloseHostServerLink(CUSTOM_SERVER, IMC_GlobalVariables);

        AssignData(UsePWEncryption,TO_LOWERCASE,UsePWEncryption);

        IF UsePWEncryption="yes" THEN

         OpenHostServerLink(CUSTOM_SERVER, IMC_Password)
         ;

         "Tell IMC_Password to encrypt the password"
         SendData(CUSTOM_SERVER, IMC_Password, 60, EncryptPassword,
                 SV20, "")
         ;

         ReceiveData(CUSTOM_SERVER, IMC_Password, 120, EncryptPassword, rc)
          edge EDGE_RECEIVE_DATA_HOST_PROB:       Problems
         ;

         CloseHostServerLink(CUSTOM_SERVER, IMC_Password);

        ENDIF

       ENDIF


    Note that passwords entered by an administrator will continue to be unencrypted and in some circumstances retrievable by an administrator - it is recommended that users be forced to change their passwords as soon as they log on after having their passwords reset by an administrator by the administrator also setting the password_change_date to a date in the past.

    Note that the encryption algorithm depends on the user id (extension/phone number) - so if this changes (for example by moveuser or makeshared or makealias or moveprofile) then the encrypted password can no longer be used and the password will have to be reset.

    Note that this encrypted password support is not at present compatible with the UniquePwds=yes setting for shared numbers with sub-mailboxes. If you use shared numbers with sub-mailboxes and the UniquePwds=yes setting then you will not be able to use PasswordEncryption=yes.

  • Ensured memory is reallocated more strictly in IMC_Barring to prevent coredumps when updating barring.rules.

  • Prevented a coredump in IMC_RemoteSystems when uncompressed audionames are used in the context of inter-node messaging with real-time retrieval and playback of remote audio names.

  • LDAP server configuration files no longer have to use the hostname of the LDAP server in the filename, instead they can use a Host field under the [Server] section inside the file to specify the hostname or IP address of the LDAP server.


 














Fix Level 4.2.0.138 

Fix release date: 8 Aug 2008
Status: Superceded


























APARDescription
IZ23275Enhanced Menu Routing will now use the following INI file settings:

  • MRGenRingTime - The duration in seconds for a transfer number to ring before the call is answered by the mailbox for the transfer number (if there is one) if there is no backup number defined. The value must be an integer in the range 5-60 or 0 for blind transfer (for a trombone this would equate to 120 seconds). The default value is 20.
    MRBupRingTime - The duration in seconds for a backup number to ring before the call is answered by the mailbox for the transfer number (if there is one). The value must be an integer in the range 5-60 or 0 for blind transfer (for a trombone this would equate to 120 seconds). The default value is 20.


Prior to this change an enhanced menu routing transfer where there was no backup defined or a transfer to a backup number would be a blind transfer (for a trombone this would equate to 120 seconds).

Enhanced Menu Routing will no longer play a technical difficulties message if a transfer attempt returns "outbound line problems".
IZ24717The UM Web Interface allows a user to forward message to another e-mail address. The user can search for a person's details including e-mail address in the corporate LDAP server as configured in IMC_MessageCenter.ini file.
IZ26961AMIS failure handling improvements including retransmitting the start frame when requested.
IZ27560Fixed a problem with subscriber type 1 attempting to dial by name where more than 10 matches are found - previously this could result in a WVR error being logged and the "We are unable to continue with this function at present..." prompt.


Other Features and Internal Defects fixes



  • The IMC_Subscribe custom server is required to be able to notify Message Waiting Indications over SIP using the SIP Subscribe/Notify methods.
    Subscribe/Notify is automatically enabled by starting the IMC_Subscribe custom server, which takes over the role of handling MWI notifications from the standard WVR MWISERVER process.

  • The caller interface has been updated to allow a custom greeting header (played before the recorded greeting) to be inserted at the AsgnGStopKeys entry point in IMC_CLR_SMEN(_0x) state tables which handles key presses in the same way as DTMFs are handled in GreetStopKey / GreetStopKeySub.

  • Correct a problem with extraction of voice messages from UM (e.g via IMC_MessageCenterAPI and IMC_SendMail) where level of voice varies considerably.


 














Fix Level 4.2.0.137 

Fix release date: 9 Jun 2008
Status: Preventative Maintenance


























APARDescription
IZ19368IMC_Stats.log now logs the MN stats code when sending a message and more than one message attribute set.
IZ21992Fixed a problem where enhanced menu routing greetings with force-play did not play.
IZ22077When a subscriber of type 5,6,7, or 8, with subscriber class of IMC_INFO, dials into UM and logs in the user won't hear the following segment "Your message queue is full. Please deal with your messages as a matter of urgency".
IZ22435Previously IMC_Broadcast would wait 5 minutes with a random variation of around 2 minutes before processing any distribution list or broadcast. There are now some additional settings to alter this behaviour:

PauseTime - how long IMC_Broadcast waits before processing any distribution list or broadcast (defaults to 300 seconds = 5 minutes).

PauseVariation - the random variation of how long IMC_Broadcast waits before processing any distribution list or broadcast (defaults to 127 seconds).

ImmediateSend - if set to "yes" allows a send to a personal distribution list under StaggerThreshold entries to be sent to immediately while the sender waits as long as there is another free IMC_Broadcast list server process other than the one which would process this immediate send or as long as QueueDir is set (see below) (ImmediateSend defaults to "no", note that StaggerThreshold now has a default of 100 and StaggerMailboxes now has a default of 95 according to the recommended values in the Admin guide, the number of list server processes is NumProcessServers which defaults to 1 - note that with only one list server process ImmediateSend will not work unless QueueDir is set)

QueueDir - if this contains the path of an existing local directory (for example /home/dtuser/broadcastqueue if this has been created - note that on an SSI server you must use a local directory which have been created on all SSI clients and servers - do not use a shared directory such as one in /home/dirTalk/current_dir/ca) then broadcast requests which arrive while all available IMC_Broadcast list server processes are busy are temporarily queued to this directory instead of being rejected - the requests are de-queued when list servers are freed up. This allows an immediate send (see above) to occur even when there is not another free IMC_Broadcast list server process other than the one which would process the immediate send - in other words immediate sends can always occur (for personal distribution lists under StaggerThreshold members) even when NumProcessServers is the default of 1.

Please be aware that setting PauseTime too low or using ImmediateSend with a high StaggerThreshold on a busy system could impact system performance - and if there are too few list server processes to process the number of personal distribution list requests sent simultaneously then some users will either have to wait a long time (if QueueDir is set) or (if QueueDir is not set) they will be told that the send has occurred but it will in fact occur several minutes later (as is the current behaviour).


 














Fix Level 4.2.0.136 

Fix release date: 9 May 2008
Status: Preventative Maintenance














APARDescription
IZ20593Provides selected Unified Messaging functionality via a generic voicemail API for use in a Web Services environment. For more information refer to the Unified Messaging: Web Services Voicemail API manual (SC34-6975-00).


 














Fix Level 4.2.0.135 

Fix release date: 10 Apr 2008
Status: Preventative Maintenance


















APARDescription
IZ16444This fix corrects a problem with automatic volume adjustment when exporting messages from UM.
IZ17989Production systems will not throw excessive amount of 20503 errors when unknown event happens.


 














Fix Level 4.2.0.134 

Fix release date: 14 Mar 2008
Status: Superceded






















APARDescription
IZ13888Subscriber type 1 profile can now send messages to an email as .wav format, where as before they were sent as .pcm format.
IZ14681The names of the TTS engines used by default in Unified Messaging have changed to match those used by default in WebSphere Voice Server 4.2 as shown below:

TTS engine language              Old name   New name
-------------------------------  ---------  --------
U.S. English TTS engine name     en_US_TTS  ttsen_US
U.K. English TTS engine name     en_GB_TTS  ttsen_GB
French TTS engine name           fr_FR_TTS  ttsfr_FR
German TTS engine name           de_DE_TTS  tssde_DE

In addition it is now possible to use a custom TTS engine state table by specifying the state table you wish to invoke for TTS in the TTS_Engine GlobalVariables setting in IMC_MessageCenter.ini. This state table will be invoked in the same way as IMC_SPEAK_STRNG with the following entry points:

Start - initialize, play a string and then release TTS resources
Init - just initialize
Play - just play a string if initialized
Terminate - just release TTS resources

Like IMC_SPEAK_STRNG the state table will be passed the following variables:

  • STRING TTSString - the string to play when the Play or Start entry points are used, or the calling state table name

  • NUMBER return_code - a return code which may be returned to the calling application (usually 0 for success)


IZ15406The prompts now play correctly in the TUI notification schedule when the user entered wrong stop time.


 














Fix Level 4.2.0.133 

Fix release date: 07 Feb 2008
Status: Partly Superseded (dirTalk.UM.rte)






































APARDescription
IZ06782Previously, when a calling number had Presentation Restricted (CLGN.PRESENT=1 in ISDN flags) set and WVR passed through full details of the calling number UM would not use the calling number field at all as Presentation Restricted was set - it would treat the calling number as unknown. This was correct behaviour for leaving messages but incorrect for retrieving messages, where it was desirable to use the calling number as the mailbox number for logging on even though Presentation Restricted was set.

Now it is possible to use the calling number as the mailbox number for logging on even though Presentation Restricted is set when UM is set up so that a call to the logon number will not require mailbox entry - for example when the state table entry point is PINOnly or NoPIN or the called number matches AltVmailExt1, AltVmailExt2 or AltVmailExt3.
IZ08809Fixed a problem so that successive IMAP4 'examine' requests will not increase the UID.
IZ10799Sends to personal distribution lists will now ignore exclude files such as:
LocalExcludeFile
RemoteExcludefile
as was the case before PTF 104 - exclude files are for broadcasts and system distribution lists only.
IZ11500This fix resolves a problem in the IOBI_MSG_CHG database trigger which could cause a problem when trying to update the IOBI_Eventstore table. This fix only applies to customers running the IMC_IOBI_EventSvr custom server.

NOTE:
The WVR/UM Administator needs to drop and re-instate the triggers:
a) Shutdown WVR
b) cd to $CUR_DIR/ca/IMC_IOBI_EventSvr_dir
c) Drop the existing triggers by running
createEventNotificationTriggers.sh -d
d) Recreate triggers by running createEventNotificationTriggers.sh
IZ12950In order to increase the resilience of broadcast messaging and sending to distribution lists even in the case of a failure of a WVR component PROMPTM state tables IMC_STATS and IMC_AMIS_VN have been updated to not require prompt directories as the absence of PROMPTM causes attempts to invoke state tables with prompt directories to fail.

In the case of IMC_AMIS_VN it will call another new state table, IMC_AMIS_VP if it needs to play any prompts.
IZ13119Fixed a problem with subscriber type 1 sending to system distribution lists since the changes in PTF 104.
IZ13801Fixed a problem whereby QueryByEmployeeNumber in IMC_LDAP_Client which was not returning the correct results.


Other Features and Internal Defects fixes



  • The unlocked state Table IMC_PROCESS_KEY has been added to allow alternative/enhanced dtmf key processing during message playback. This state table can be invoked by the locked IMC_PLAY_MSG state table to handle dtmf key collection. If the IMC_PROCESS_KEY state table is not present then IMC_PLAY_MSG will process dtmf keys without change. For full operational information on this feature, refer to the Help Center article:
    /hc/en-us/articles/21669702

  • Fixed an 'ArrayOutOfBoundsException' error in the UM Web Interface. The problem would occur after dealing with expired messages and trying to read the first unexpired message in 'Inbox'.

  • Fixed a problem whereby the after dialling into a subscriber that has expired msgs, and selecting '1' to hear the first expired msg, it loops playing the msg, with the only valid option of deteling the msg (by pressing 3).
    The problem only occurs when the IMC_MessageCenter.ini setting for SimplePlay is set 'true'.

  • Fixed a problem whereby the expert prompt was played for the expired menu instead of normal prompt even though the Prompt Level = 0.


 














Fix Level 4.2.0.132 

Fix release date: 18 Jan 2008
Status: Preventative Maintenance






















APARDescription
IZ04403Implemented support for pager_types files using partition names as well as language codes, as promised in PTF 104.
IZ04829IMC_Password is using MinReuseTime correctly.
IZ06192Fixed an issue where a recorded greeting for a shared number could not be interrupted to select a sub-mailbox and after the greeting played if no key was pressed, the system greeting would play even if it had been disabled. Note that IMC_CLR_SHARED has been updated - if you have a customized version of IMC_CLR_SHARED you should re-customize it after applying this update.


Feature changes



  • Find-Me Follow-Me Caller Screening preference is a feature available to Subscriber Types 6 and 7. For information on the FMFM Screening preference, refer to this Help Center article:
    /hc/en-us/articles/216696997

  • Confirmation of Message Deletion (CMD) is a feature that will warn certain subscribers that new or saved voice messages have expired, and enable them to listen to those messages before deletion occurs. For further information on CMD, refer to this Help Center article:
    /hc/en-us/articles/216122498


 














Fix Level 4.2.0.131 

Fix release date: 21 Sep 2007
Status: Preventative Maintenance






























































APARDescription
IZ01081Distribution list message can be sent as public (forwardable) andprivate (unforwardable), but broadcast message to subscribers belonging to a particular partition can only be sent as private.
IZ01191Improvements to IMC_STATS logging to show the main mailbox number as well as the alias number when calls are received for alias numbers or users log on using alias numbers.
IZ01864Fixed the XMLProvisioning custom server so it won't coredump when username length is less than telephone number.
IZ01928Fixed deleted messages to play in 24 hour time format if the clock preference for the mailbox has been set for 24 hour clock.
IZ02711LDAP server configuration files no longer have to use the hostname of the LDAP server in the filename, instead they can use a Host field under the [Server] section inside the file to specify the hostname or IP address of the LDAP server.
IZ02728Fixed an IMC_Pager coredump which occurred when a notification schedule specified a template which did not exist (this can occur if details of a schedule which has paging configured are removed but the schedule is left active, in which case IMC_Pager may try to find an entry for a template called PHONE, based on the default entries in the pager_types file).
IZ02750Fixed the enhanced menu routing TUI interface to permit menu routing numbers not on the local system. Prior to this fix, attempting to enter such numbers could result in "we are unable to continue with this function at present".
IZ03818Fixed a regression in the code which was introduced when reach-me PIN support for tromboned calls was added (IY96386), this regression resulted in the called party's audioname not playing when a find-me/follow-me call was announced to the called party.
IZ03871Fix to clear a fax event before it can reach IMC_TRMBONECALL in the case that a fax call is being transferred to an external fax server, to prevent IMC_TRMBONECALL from exiting or looping on its WaitEvent when the fax event reaches it.
IZ04017The mwi_config command now works correctly when using the -every option.
IZ04169Fixed a abnormal termination of call / "Sorry we are unable to continue with this function at present" for new enhanced menu routing profiles which have not been configured with an active or emergency schedule.
IZ04226Fixed a problem where menu routing applications were not playing greetings. The following default prompts and language 1 prompts have changed to include subscribe type 10 in the case statement for SV293 (SubTypeLike) for the UpdGrtType feature, you should check to see if you need to recustomize them and should save the changed prompts for any custom languages you have:

  • PlayGreeting
    AOSysGreet
    CurrGrtSel
    DescGreet


IZ02710Documented how to avoid updating /etc/aliases every time users are added or deleted from the system for VPIM. For details, refer to the following Help Center article:
/hc/en-us/articles/219841187


Other Defect fixes



  • Ship and make available the DISTAUTH file for the IMC_Broadcast custom server.







  • Update 4.2.0.130

    APAR IZ00377 IZ01082 IZ01159 IZ01780 IZ02074 IZ02080

    PTF U812853

    1.Prevented memory leak and coredump in IMC_XMLProvisioning at
      DBLookupTime after a number of days on a system with a very large
      number of profiles.
      (APAR IZ00377)

    2.Restored the behaviour of the greeting header which was broken in
      PTF 125, so that the system greeting does not play after the greeting
      header if the selected greeting does not exist and keys pressed
      during the greeting header have the same effect as if the selected
      greeting did exist.
      (APAR IZ01082)

    3.IMC_SCHEDULE has been enhanced to allow customizers to:
       - verify pager reference numbers entered are valid using new state
         table IMC_CHK_PFMT
       - bypass the default pager selection menus in the case that no
         pagers are selectable or other special requirements. This is
         achieved by using the SelectMainType and SelectBackupType entry
         points to IMC_SBR_MENU_NS or IMC_SBR_MNU_SNS, from which the
         return code (in SV74) can indicate the selected pager type (or 0
         for telephone outcalling). If SV74 is blank then the default pager
         selection menus will be used.
      (APAR IZ01159)

    4.After adding several application profiles (mailboxes) or aliases
      it was possible for aliases of mailboxes which already had messages
      to not have a field set correctly for setting MWI. This problem has
      been resolved.
      (APAR IZ01780)

    5.vm_restore -u could corrupt maximum values in subscriber classes
      when they were updated. This problem has now been corrected.
      (APAR IZ02074)

    6.When [GlobalVariables] MsgUndeletion=2 and [XXX_DeleteVoiceMessage]
      PurgeTime were used to allow messages to be undeleted after the call
      in which the messages were deleted, if a subscriber went directly to
      the deleted messages area and undeleted the messages then the
      messages would still have an expiry time set according to the
      PurgeTime instead of an expiry time set appropriately for a saved
      (ie, undeleted) message. This has been corrected.

      In addition, IMC_DeleteVoiceMessage has been updated so that the INI
      file setting for PurgeTime would be picked up correctly and the
      list_messages utility in $CUR_DIR/ca/IMC_DeleteMsg_dir/utils would
      show deleted messages and their expiry times.
      (APAR IZ02080)

    7.This fix updates the IMC_STARTUP state table to add support for the
      SIP Privacy header (other headers such as P-Asserted-ID will have
      been processed by the WVR SIP stack into Called, Calling and Last
      Redirecting numbers).
      (Defect 36039L)

    8.Calls to shared and alias numbers now refresh the global variables
      from type/partition ini files.
      (Defect 36094)

    9.Fixed a problem with cacheing of e-mail templates in IMC_Sendmail
      which could cause it to stop sending e-mail notifications.
      (Defect IY94543a)


  • Update 4.2.0.129

    APAR IY97787 IY99024 IY98561 IY98685 IZ00002 IZ00004 IZ00007

    PTF U812204

    1.XMLProvisioning GetSubscriber response message now shows the
      pin_security field and other changeuser command fields that were
      previously missing.
      (APAR IY97787)

    2.The vm_restore -r command did not previously rename or delete
      directories containing voice messages, greetings, audionames or
      distribution list names prior to restoring files to them. The
      vm_restore -r command will now by default rename these directories
      and let the user know the renamed directory names for later manual
      removal.

      vm_restore has the following new options if this behaviour is not
      desired:
         -d will delete the directories (this may take a long time for
            directories with a large number of subdirectories and files)
         -n will neither rename nor delete the directories (the original
            behaviour up to this point)
      (APAR IY99024)

    3.The finduser command now works in accordance to the Administrator's
      Guide. Executing finduser with no parameters will now output a list
      of users.
      (APAR IY98561)

    4.Fixed a problem where the subscriber type 7 and 8 system greeting
      would go to the operator instead of the dynamic caller menu when a
      caller pressed 0.
      (APAR IY98685)

    5.Relaxation of VPIM2 support to increase interoperability with other
      vendor VPIM2 systems.

      Specifically, allow no hostname in the To: header for incoming VPIM2
      messages and put the address in the From: header into the From in the
      SMTP envelope too for outgoing VPIM2 messages.
      (APAR IZ00002)

    6.Tromboned fax calls will now not drop when the inbound leg detects a
      fax tone.
      (APAR IZ00004)

    7.Fixed IMC_START_MR to explicitly specify what happens when a called
      number is not on the system and is busy, so that the caller is told
      that the number is busy rather than that there is a problem.
      (APAR IZ00007)

    8.IMC_Broadcast will create $CUR_DIR/ca/spool directory if not already
      exists in the system.
      (Defect 35899)

    9.IMC_Broadcast custom server now works in accordance to the
      Administator's Guide. It will not coredump when the configuration
      files are not in the system.
      (Defect 35903)





Fix level 128

APAR IY99572
PTF U811980




  • Update 4.2.0.128

    APAR IY99572

    PTF U811980

    1.Extra configuration parameters have been added to
      IMC_MessageCenter.ini to provide more flexibility when generating the
      TO email address of a fax gateway.

      The Administrator can now specify the following parameters:

      StartSendFaxFormat=[Start]
      MidSendFaxFormat=[Mid]
      EndSendFaxFormat=[End]

      where [Start], [Mid] and [End] are concatenated into the TO email
      address as follows:

      [Start]5551234[Mid]faxgateway@mytelco.com[End]

      For example, for a fax to be sent to number 5551234 via a Fax Gateway
      that requires the TO: email address to be in the following format:

      /Fax=5551234/ <faxgateway@mytelco.com>

      The Administrator would configure the following in the
      IMC_MessageCenter.ini:

      StartSendFaxFormat=/Fax=
      MidSendFaxFormat=/ <
      EndSendFaxFormat=>

      If the parameters are missing, existing default behaviour will be used.

      (APAR IY99572)


  • Update 4.2.0.127

    APAR IY94543 IY96779 IY97417 IY95217

    PTF U811646

    1.IMC_Sendmail can now operate using template files in the same manner
      as IMC_Notify and IMC_Pager, namely it will search for
      EMAILATT.<partition name>.<language> then
      EMAILATT.<partition name> then
      EMAILATT.<partial partition name>.<language> then
      EMAILATT.<partial partition name> then
      EMAILATT.<language> and then simply
      EMAILATT
      or for sending to e-mail and not keeping a local copy
      (vpim_msg_del_pref=1)
      REMEMAILATT.<partition name>.<language> then
      REMEMAILATT.<partition name> then
      REMEMAILATT.<partial partition name>.<language> then
      REMEMAILATT.<partial partition name> then
      REMEMAILATT.<language> and then simply
      REMEMAILATT
      for further details see documentation on IMC_Notify and IMC_Pager.
      (APAR IY94543)

    2.This APAR corrects an issue with enhanced menu routing subscribers
      where if the system was configured for trombone call forwarding then
      the call transfer would fail for incoming callers.

      This fix only affects customers using IOBI.

      It fixes a slight problem the IOBI connector in which the CallerID
      was not sent, and system numbers could be revealed in an IOBI
      notification.

      After installation of this PTF, you must execute:
        createEventNotificationTriggers.sh
      in the
        current_dir/ca/IMC_IOBI_EventSvr_dir
      directory.
      (APAR IY95217)

    3.Administrator can change both email_address and vpim_address in the
      same changeuser command and it will not produce any corrupted user
      profile as earlier. Also email and vpim address fields can have up to
      255 characters in length.
      (APAR IY96779)

    4.The pin_security setting can now be used in IMCdefaults.file.
      Prior to this PTF pin_security had to be specified as access_mode in
      IMCdefaults.file. (Now both access_mode and pin_security work.)
      (APAR IY97417)

    5.File cacheing in IMC_Pager and IMC_Notify has been fixed (it ceased
      to function when partial pattern matching was introduced).
      (Defect 35912)

    6.System will not cause any abnormal termination when we enter invalid
      jumpout number consecutively.
      (Defect 36108)

    7.Fixed a coredump due to rewritten partial pattern matching in
      IMC_Pager, IMC_Notify and IMC_Sendmail.
      (Defect 36137)

    8.Resolved a problem where non-partition based template files such
      as EMAIL or EMAILATT.1 would not get picked up when
      PartialMatching=yes and PartialMatchingLength were set for
      IMC_Notify, IMC_Pager and IMC_Sendmail.
      (Defect 36139)






Fix level 126

APAR IY94998 IY96386 IY96446 IY96449
PTF U811345




  • Update 4.2.0.126


    APAR IY94998 IY96386 IY96446 IY96449

    PTF U811345

    1.Sample code has been provided to show how talkoff can be prevented
      by  disabling all DTMF during recording. This can be found in
      $VAE/sw/MessageCenter/st_src/clr_smen_05
       - see the two blocks of code marked "TALKOFF PREVENTION", saying
      this code can be uncommented to prevent talkoff in subscriber type 5
      or similar code copied to other subscriber type caller menus to
      prevent talkoff.
      (APAR IY94998)

    2.Support for Reach-me PIN on tromboned calls added.
      (APAR IY96386)

    3.The prompt "Call forwarding has been set" will not longer play when
      you log into a menu routing application if the first transfer
      number is set.
      (APAR IY96446)

    4.Ensured that menu routing direct to mailbox works and does not play
      a prompt saying a transfer will occur.
      (Applies to regular and enhanced menu routing. Ensure the option to
      route direct to the mailbox has been selected when configuring the
      menu routing application.)

      Ensured that menu routing to a mailbox after a transfer works.
      (Applies to enhanced menu routing where this previously did not
      work.)
      (APAR IY96449)

    5.A discrepancy resulting in subscriber type 7 being able to
      enter an unlimited number of (invalid) destinations when
      UniqueDlists = 0 has been fixed.
      (Defect 36065b)

    6.Copied subscriber types can now modify ReachMe PIN in the web
      interface.
      (Defect 36065c)

    7.Valid external number can be used as backup or operator number in
      enhanced menu routing.
      (Defect 36085)

    8.Increased looping prevention added in IMC_XFER_DO, to look at
      original called number information as well as the current called
      number information.
      (Defect 36114)



  • Update 4.2.0.125


    APAR IY95215 IY94888

    PTF U811203

    1.Fix the ability to copy existing subscriber type menus to a new
      subscriber type number and have the new subscriber type act the same
      as the original - for example:

      cp sbr_menu_02 sbr_menu_52
      cp ctl_menu_02 ctl_menu_52
      cp clr_smen_02 clr_smen_52
      cp firstime_02 firstime_52
      DTst -import -f sbr_menu_52 -o IMC_SBR_MENU_52
      DTst -import -f ctl_menu_52 -o IMC_CTL_MENU_52
      DTst -import -f clr_smen_52 -o IMC_CLR_SMEN_52
      DTst -import -f firstime_52 -o IMC_FIRSTIME_52

      ...in this case subscriber type 52 would act the same as subscriber
      type 2. This is achieved in a basic form by ensuring any existing
      behaviours for subscriber types which are not already within editable
      menus now reference a "SubscriberTypeLike" variable (SV293) which if
      the new subscriber type is above 19 (values up to 19 are reserved)
      will be the remainder after dividing the new subscriber type number
      by 10.
      (An ability to change these existing behaviours and "mix and match"
      some behaviours has also been introduced, but full details of this
      are not being released at this point due to its complexity and a
      large number of limitations and caveats. If you require further
      details on this, please contact your IBM representative.)
      (APAR IY95215)

    2.Corrects a discrepancy in the timestamp and timezone of messages
      retreived via IMAP and some methods of message notification.
      (APAR IY94888)





Fix level 124

APAR IY93625 IY94319 IY94614
PTF U810957




  • Update 4.2.0.124


    APAR IY93625 IY94319 IY94614

    PTF U810957

    1.Prompts and prompt directories are now backed up by UM_ptf_mgr if
      the PTF import  contains prompts.
      (APAR IY93625)

    2.Enhanced Menu Routing:
       - support added for tromboning
       - support added for MRCallerIDSend INI file setting when tromboning
      (APAR IY94319)

    3.Customers can now edit the state table IMC_XFORM_NUM.
      (APAR IY94614)


  • Update 4.2.0.123


    APAR IY92147 IY91786 IY92060 IY9277

    PTF U810593

    1.Where voice messages are uncompressed but not all segments are
      uncompressed, IMC_Attachment was unable to create an uncompressed
      voice segment saying "this message is a fax" to use as an
      uncompressed voice message. This fix corrects this issue.
      (APAR IY92147)

    2.Correction of Broadcast/Extension Dialing code so that an attempt
      to send to 8888 or 9999 is not treated as a broadcast attempt.

      Only destinations of 8 digits starting with 8888 or 9999 will be
      treated as broadcast attempts, and only after checking they are not
      otherwise defined as extensions or profiles on the system.
      (APAR IY91786)

    3.This fix corrects a problem whereby XML Provisioning response
      messages don't always follow the schema causing <Errors> to appear
      before <Successes> sometimes. Now the Succeses tag gets inserted
      before the Errors tag if one existed.
      (APAR IY92060)

    4.This fix ensures that all responses from the IMAP4 server are
      terminated correctly with newline characters. In very rare
      situations, the remote client could fail when we didn't send newline.
      (APAR IY92773)


  • Update 4.2.0.122


    APAR IY90473 IY91309 IY91450

    PTF U810586 U810587

    1.Fixed the type of the variable expertPrompts to be boolean (B)
      in $CUR_DIR/ca/IMC_GlobalVariables_dir/GlobalVariables.ini.
      (APAR IY90473)

    2.XMLProvisiong or delPartition script can be used to delete a
      partition and to update the partition.info file.
      (APAR IY91309)

    3.Fixed a problem when there is a big difference between loud and
      quiet parts of a voice message e.g. when voice in a message  is
      relatively quiet but there is, say, a large click at the end
      resulting  from, for example, a line hangup. The original code did
      not make any volume  adjustments to the message volume.
      The new code applies a dynamic gain control to the message which
      effectively makes everything within a voice message to be the same
      volume.
      (APAR IY91450)

    4.Fixed an issue in the IMC_MR_Retrieve custom server whereby the
      incorrect error return code is sent by the custom server when
      attempting to save invalid time data.
      (Defect 36011)

    5.Prevented a coredump which could occur in IMC_Sendmail when sending
      VPIM messages on a system using uncompressed messages.
      (Defect 36015)

    6.Prevention of a possible loop in IMC_AMIS_VN and IMC_AMIS_SCH when
      performing an LDAP lookup.
      (Defect 36016)

    7.When using ReverseID with IMC_ByNumber the setting of MailboxDigits
      was being ignored in some circumstances so that if you had profiles
      of varying lengths you could match these despite MailboxDigits
      specifying only one length should match. This has been corrected.
      (Defect 36025)

    8.Fixed an issue in the web interface for enhanced Menu Routing
      subscribers whereby after selecting the tab to change the PIN the
      user could then not return to the menu routing configuration page.
      (Defect 36026)

    9.Fixed the behaviour of the mailbox busy database field such that
      irrespective of the log-in method (whether or not the user is
      prompted for a password) the mailbox busy state is set correctly.
      (Defect 36028)

    10.Fixed some slightly misleading text in the web NLS strings for
      Enhanced Menu Routing subscribers.
      (Defect 36030)


  • Update 4.2.0.121


    APAR IY88102 IY89287 IY90014 IY90035

    PTF U809681

    1.Fixed moveprofile so now works for files of up to and over 2000
      users.
      (APAR IY88102)

    2.Fixed the output of the IMC_XMLProvisioning getSubscriber command so
      it now includes the <GetSubscriberResponse> tag.
      (APAR IY89287)

    3.Changing ForwardKey, BackKey, PauseKey, FastKey, SlowKey,
      LoudKey and QuietKey in subscriber type and partition INI
      files now works.

      Changing ForwardKey, BackKey, PauseKey, FastKey, SlowKey,
      LoudKey and QuietKey in subscriber type and partition INI
      files now works.

      NOTE: This PTF contains updates to the customizable state tables
      IMC_STARTUP, IMC_OCALL_START, IMC_START_AA, IMC_START_MR and
      IMC_START_QMG to remove the setting of ForwardKey, BackKey,
      PauseKey, FastKey, SlowKey, LoudKey and QuietKey in these state
      tables. These keys no longer have to be set in these state tables
      as they are now set closer to the point where they are used.

      Importing these state tables may remove customizations you have
      made to them. Be sure to back up your customizations and either
      restore them after installing the PTF (the versions which set
      these keys will still work, so your customizations will work
      without any changes) or re-customize the latest versions to be
      found in /usr/lpp/dirTalk/sw/MessageCenter/st_src - or alter
      your customized versions by removing the setting of these keys
      in the same way as this has been done in the latest versions.
      (APAR IY90014)

    4.Fixed a bug in IMC_Getmail which resulted in it rejecting faxes
      unless a legacy behaviour was enabled. IMC_Getmail will now also
      not check that a fax is in a valid TIFF-F format if the INI file
      setting CheckFaxFormat=no is set under [XXX_Getmail] in
      IMC_MessageCenter.ini.
      (APAR IY90035)





Fix level 120

APAR IY87587
PTF U808972 U809552




  • Update 4.2.0.120


    APAR IY87587

    PTF U808972 U809552

    1. Addition of a capability for an external LDAP directory to be used
      to discover the AMIS-A or VPIM2 destination of a message. It is now
      possible to specify InteroperabilityServer and Interopdigits in the
      LDAP_Server section of an INI file (system-side, per subscriber type
      or per partition) so that a number which is not on the local system
      will be looked up in the LDAP directory using fields AMISAddressField
      and VPIMAddressField in LDAP server INI files. For further details,
      refer to the Unified Messaging Administration Guide at the following
      URL:
      http://www.blueworx.com/TD/UnifiedMessaging/UM42-Admin-Guide-c3463995.pdf

    2. Addition of extension dialling. It is now possible to specify
      MailboxDigits and ExtensionDialing in an INI file (system-wide, per
      subscriber type or per partition) so that only the last few digits of
      a number need to be dialed. For further details, refer to the Unified
      Messaging Administration Guide at the following URL:
      http://www.blueworx.com/TD/UnifiedMessaging/UM42-Admin-Guide-c3463995.pdf

    3. Adds support for the Verizon IOBI interface. Refer to the latest
      product documentation for information on how to implement this
      service.

    4. Adds scheduling capabilities to the Menu Routing application such
      that multiple schedules can be configured by the mailbox owner for
      different times such that the caller receives different call handling
      dependent on when they make the call. In order to utilise this
      capability the administrator should create a menu routing subscriber
      (type 10) in the normal manner but in addition they should then
      configure the noticeboard_password field to have a '1' in the third
      character of this field:

      changeuser -e <subscrbr phone num> -u noticeboard_password -v 'XX1'

      Where 'XX' are either the existing values of this field or '00'.

      In addition, multiple voice segments have been added to enable this
      function:

      10001   To work with your transfer options, press 2. To work with
              your greeting, press 3.  To change your password, press 4.
              To exit, press 7.
      10002   To call
      10003   The number you have selected is not available at present.
              Please try again later.
      10004   now
      10005   The following transfer options are active
      10006   No transfer options are active.
      10007   To listen to the transfer option, press 1. To change the
              transfer option, press 2. To delete the transfer option,
              press 3. To go to the previous transfer option, press 4. To
              go to any transfer option, press 5. To go the next transfer
              option, press 6. To return to the previous option, press 7.
      10008   Please enter the phone number for this transfer option
              followed by the  pound key or press  star to cancel.
      10009   This option transfers to
      10010   Please key in the transfer option you would like to work with
              or press  star to return.
      10011   The transfer option has been deleted.
      10012   No number has been set for this transfer option.
      10013   I am sorry, the phone number you entered is not valid.
      10014   Transfer option number
      10015   Sorry  no transfer numbers have been set.
      10016   To listen to the transfer option, press 1. To change the
              transfer option, press 2. To delete the transfer option,
              press 3. To go to the previous transfer option, press 4.
              To go to any transfer option, press 5. To go to the next
              transfer option, press 6. To set the transfer type, press 8.
              To return to the previous option, press 7.
      10017   If you wish to transfer to the subscriber's telephone,
              press 1. If you wish this option to transfer directly to the
              destination mailbox, press 2. To return, press 7.
      10021   To work with the transfer options, press 2. To work with the
              greeting, press 3.  To change your password, press 4.  To
              exit, press 7.
      10022   The caller currently hears the recorded greeting.
      10023   The caller currently hears the system greeting.
      10024   The caller currently hears the recorded greeting followed by
              the system greeting.
      10025   To change the caller greeting to the recorded greeting,
              press 1.
      10026   To change the caller greeting to the system greeting,
              press 2.
      10027   To change the caller greeting to the recorded greeting
              followed by the system greeting, press 3.
      10028   To listen to the system greeting, press 4.
      10029   To listen to the recorded greeting, press 5.
      10030   To record the greeting, press 6.
      10031   To delete the recorded greeting, press 9.
      10033   Sorry, to change to this greeting you must first record the
              greeting.
      11000   To work with the main welcome greeting, press 9.
      11001   To enable or disable the system greeting from playing after
              your recorded welcome greeting, press 3.
      11002   To enable the playing of the system prompt after the recorded
              greeting, press 1, to disable the playing, press 2, to return
              press 7.
      11003   The greeting you have selected does not exist. You must now
              record that greeting.
      11004   To play this greeting, press 1. To rerecord this greeting,
              press 2. To delete this greeting, press 3. To enable or
              disable the system greeting from playing after your recorded
              welcome greeting, press 4. To return, press 7.
      11005   To work with the scheduled transfer options, press 2, to
              change your PIN, press 4.
      11006   To work with the business hours schedule, press 1, to work
              with the out of hours schedule, press 2, to work with the
              emergency schedule, press 3, to work with holiday schedules,
              press 4.
      11007   holiday schedules. Enter the number of the schedule you
              wish to modify.
      11008   To set the business hours, press 1.
      11009   To set the holiday dates and times, press 1.
      11010   To set the transfer options for this schedule, press 2, To
              work with the greeting for this schedule, press 3. To work
              with the configuration settings for this schedule, press 4.
      11011   To configure the application behaviour when a caller fails
              to enter valid data after all repeats have been completed,
              press 1, To configure the backup number capability, press 2,
      11012   To configure the number of times the menu is repeated, press
              1, To configure the action upon completion of all repeats of
              the menu, press 2.
      11013   The application is currently configured to repeat the menu
      11014   times.
      11015   Enter the number of times to repeat the menu.
      11016   The number of repeats must be between 1 and 5.
      11017   The application is currently configured to
      11018   terminate the call when the user makes no valid entries.
      11019   transfer to the operator when the user makes no valid
              entries.
      11020   To set the application to terminate the call when the user
          & nbsp;   makes no valid entries, press 1.
      11021   To configure the application to transfer the call to the
              operator when the user makes no valid entries, press 2.
      11022   To listen to the business hours, press 1.
      11023   To modify the business hours or days, press 2.
      11024   The business hours are between
      11025   The business days are incorrectly configured. Please
              configure them now.
      11026   Enter the business hours start time.
      11027   Enter the business hours end time.
      11028   Use the keypad to enter the hours and minutes using the 24
              hour clock format.
      11029   The time of day can be entered using the twenty four hour
              clock format. Times must be entered by keying both hours
              and minutes. For example five thirty pm is 1 7 3 0. Valid
              times are between 0 0 0 0 and 23 59.
      11030   To configure the business hours, press 1, to configure the
              business days, press 2.
      11031   There are currently no business days configured.
      11032   Business hours are currently configured for
      11033   To activate
      11034   as a business day
      11035   To deactivate
      11036   To listen to the currently configured holiday dates and
              times, press 1.
      11037   To configure the holiday dates and times, press 2.
      11038   The start time is
      11039   The start date is
      11040   The end time is
      11041   The end date is
      11042   Enter the start date for the holiday as
              day day month month year year year year.
      11043   Use the keypad to enter the date as
              day day month month year year year year using zeros as
              required
      11044   Enter the end date for the holiday as
              day day month month year year year year.
      11045   Enter the start time for the holiday.
      11046   To configure the backup number, press 1. To configure
              the time for which the primary number will be attempted
              before trying the backup number, press 2.
      11047   The backup number is currently set to
      11048   To set the backup number, press 1
      11049   Please enter the new backup number
      11050   To disable this option from transferring to the backup
              number if the transfer fails, press 9.
      11051   The application will ring the primary number for
      11052   seconds before trying the backup number
      11053   To change the length of time before trying the backup
              number, press 1
      11054   Please enter the new length of time in seconds.
      11055   The time must be between 5 and 60 seconds
      11056   To listen to the transfer option, press 1. To change
              the transfer option, press 2. To delete the transfer
              option, press 3. To go to the previous transfer option,
              press 4. To go to any transfer option, press 5. To go to
              the next transfer option, press 6.
      11057   To set the transfer type, press 8.
      11058   To enable this option to transfer to the backup number if
              the transfer fails, press 9.
      11059   To move to the destination menu routing mailbox, press 0.
      11060   To return to the previous option, press 7.
      11061   To
      11062   Activate
      11063   Deactivate
      11064   This schedule, press 3
      11065   To set the recorded greeting as interruptible, press 4.
      11066   To set the recorded greeting as non-interruptible,
              press 4.
      11067   A backup number is not currently configured.
      11068   The schedule cannot be activated at this time because it
              is not valid. Fully configure the schedule and you can
              then activate it.
      11069   There was no answer from the requested option number.
              Please hold while we try the backup number.
      11070   The configured phone number for this option is invalid.
              Please hang up and try again later.
      11071   The telephone number is currently busy.
              Please hang up and try again later.
      11072   The telephone network is currently busy.
              Please hang up and try again later.
      11073   There was no reply from the backup number.
              Please hang up and try again later.
      11074   Enter the end time for the holiday.
      (APAR IY87587)



  • Update 4.2.0.119


    APAR IY87215 IY86016

    PTF U808957

    1.An account with 15 digits and subscriber type 5 can send broadcast
      message to a partition without any problem.
      (APAR IY87215)

    2.Adding a partition using XML provisioning can now use both
      department and partition tags.
      (APAR IY86016)


  • Update 4.2.0.118


    APAR IY84658 IY86149

    PTF U808559

    1.The weekday, month fields in the email/pager notification will show
      full names  and won't truncate to four characters.
      (APAR IY84658)

    2.Fixed IMC_Admin and utilities to support remote requests properly
      using the -H parameter.
      (APAR IY86149)





Fix level 117

APAR IY85243
PTF U808511




  • Update 4.2.0.117


    APAR IY85243

    PTF U808511

    1.Subscribers of type 6, 7 & 8 shared mailboxes are now able to provide
      their callers with a personalised greeting as well as or instead of
      the current system greeting.
      See /usr/lpp/dirTalk/sw/MessageCenter/README.117 for more details.
      (APAR IY85243)


  • Update 4.2.0.116

    APAR IY83821 IY81874 IY82283 IY82643 IY82774 IY82828 IY82835

    PTF U807396 U807397

      1.IMC_Dlist creating distribution lists correctly over XML and
      command line.
      (APAR IY81874)

     2.Following WVR 4.2 PTF level 4.2.0.207, added support for cancelling
      the outbound leg of a trombone before the call is actually made.
      (APAR IY82283)

     3.The JavaTimeZones.txt and JavaTimeZones_05.txt files shipped with
      IMC_MessageCenterAPI custom server have been modified so that the
      entries now appear in ascending order of GMT offset.  Some daylight
      saving time rules have been modified to make them current for this
      year.  Customers should be reminded that daylight saving time rules
      do vary slightly from year to year in some countries,  the timezone
      files should be checked annually to ensure that the rules are
      current.
      If you have customised the JavaTimeZones.txt or JavaTimeZones_05.txt
      files on your system you will need to backup these files before you
      run the UM PTF manager import tool. When restoring them, you should
      also check that the entries are in ascending order of GMT offset to
      ensure that all fields are visible in the GUI.

     4.Since PTF 104 distribution list names for system distribution lists
      did not play.  The code to play names for system distribution lists
      has been restored.
      (APAR IY82774)

     5.Fixed a problem reading JavaTimeZones text files if the file does
      not end in a newline. Prior to this fix this resulted in a wrong
      time zone value for the last entry in the file.
      (APAR IY82828)

     6.When attempting to perform a 'makeshared' or 'moveuser' on an
      account whose name contains an apostrophe, the action failed with
      "Action failed. CA_FUNC_FAILED CA_errno = 65". This has been
      corrected.
      (APAR IY82835)

     7.FindMe call function is working according to the design. Only hash
      (#) key can be used to interrupt the call and to leave message.
      (APAR IY83821)

     8.The UM web interface Inbox and Message Content pages will show the
      right value for subject field in Mozilla Firefox browser.
      (Defects 35835 & 35835a)


  • Update 4.2.0.115

    APAR IY81134 IY81392 IY80948 IY81390

    PTF U806977

    1.The LDAP client and server binding problem has been solved
      by upgrading the openLDAP libraries
      to the latest level (2.3.17).
      (APAR IY80948)

    2.A fix to the uncompress_messages to ensure a database flag
      indicating the compression type is set. This flag affected
      the CA_Get_Voice_Msg_Info routine which is used in UM by
      IMC_MoveProfile - hence IMC_MoveProfile can now unload all
      messages which uncompress_messages migrates.
      (APAR IY81134)

    3.Support for custom locales and other custom strings for
      different languages has been added to IMC_Notify (e-mail),
      IMC_Sendmail (e-mail with attachment) and IMC_Pager
      (pager notifications).

      To use a custom locale, simply add an entry like:
      <locale:de_DE>
      to the template file used by the custom server, for example,
      in EMAILATT.7 you could add
      <locale:sv_SE>
      at the start of the file.

      To use a custom string for "an Unknown Caller" enter the
      string after a / within the <caller name> tag - for example:
      <caller name/a caller whose name is not known>

      To use a custom string for an unknown number (which otherwise
      shows as ?) enter the string after a / within the
      <caller number> tag - for example:
      <caller number/number unknown>

      To use a custom string for an unknown sender e-mail address
      enter the string after a / within the <sender e-mail> tag -
      for example:
      <sender e-mail/unknown address>

      To use a custom string for the message type (voice or fax)
      enter the alternatives separated by / after a : within the
      <type> tag - for example:
      <type:VOICE/FAX>

      To use a custom string for the status (new or saved) enter the
      alternatives separated by / after a : within the <status> tag -
      for example:
      <status:NEW/SAVED>

      To use a custom string for the message privacy enter the
      alternatives separated by / after a : within the <privacy> tag -
      for example:
      <privacy:normal /private >
      ...note that if you want nothing to display for normal privacy
      then you can use just:
      <privacy:private >

      To use a custom string for the priority enter the
      alternatives separated by / after a : within the <priority> tag -
      for example:
      <priority:normal /urgent /emergency >
      ...note that if you want nothing to display for normal priority
      and have no emergency priority then you can use just:
      <priority:urgent >

      To use a custom string for the acknowledgement enter the
      alternatives separated by / after a : within the
      <acknowledgement> tag - for example:
      <acknowledgement:normal /acknowledgement >
      ...note that if you want nothing to display for no
      acknowledgement then you can use just (for example):
      <acknowledgement:This message is an acknowledgement.>
      (APAR IY81390)

    4.XMLProvisioning custom server will shtudown properly when
      running a csstop command.
      (APAR IY81392)

    5.IMC_MoveProfile updated to pass information about problems
      loading audio names, greetings and voice messages back to the
      moveprofile command.
      (Defect 35304)

    6.Fixed a problem with Quick Message application when system
      profile 888888 has subscriber type 1
      (Defect 35520b)

    7.Since PTF 104, stats logging concerning sending messages to
      distribution lists has not worked.
      (Defect 35623)

    8.The uncompress_messages -r (recompress/reverse) operation
      has been fixed.
      (Defect 35872)

    9.The check_message utility in $CUR_DIR/ca/IMC_DeleteMsg_dir/utils
      has been updated to check for uncompressed message files as
      well as compressed message files.
      (Defect 35873)

    10.IMC_MoveProfile has been fixed to allow dumping voice
      messages to WAV files when the system is set to use uncompressed
      voice messages.
      (Defect 35874)

    11.IMC_RemoteSystems now supports LoggingLevel, logging appropriate
      levels of detail to IMC_RemoteSystems.log depending upon the
      LoggingLevel set.
      Output sent to DTM_D.log will not be duplicated in DTstatus.out
      (the WebSphere Voice Response status window).
      (Defect 34421)





Fix level 114

APAR IY80006 IY80114 IY80120 IY80603 IY81139
PTF U806887




  • Update 4.2.0.114

    APAR IY80006 IY80114 IY80120 IY80603 IY81139

    PTF U806887

    1.Fixed a problem whereby distribution lists with id lengths greater
      that 3 digits have not worked.
      (APAR IY80006)

    2.Distribution lists with members with lengths above 11 digits, that
      have previously not worked, have been fixed.
      (APAR IY80114)

    3.The use of distribution lists or broadcasts could cause the buffer
      pool to fill up and the system to become unusable. This has been
      fixed.
      (APAR IY80120)

    4.This fix resolves the issue where the IMC_XMLProvisioning custom
      server will not create the .db files from a database lookup if the
      temporary directory has not been previously manually created with the
      correct permissions by the administrator.
      (APAR IY80603)

    5.Adding a partition via XML Provisioning could fail if WVR was started
      automatically, such as if WVR was running before a system restart, or
      via HACMP. It could also fail if the PATH was not set in the .profile
      for dtuser. This has now been fixed.
      (APAR IY81139)

    6.Misleading errors when a profile gets loaded or unloaded have been
      corrected.
      (Defect 35312)

    7.Fix to prevent rare case where IMC_CA_Monitor erroneously kills other
      custom servers, which were started before CA_CNTL.
      (IMC_CA_Monitor will still correctly kill custom servers which really
      were started before CA_CNTL as if any exist they are from a previous
      WVR startup.)
      (Defect 35768)

    8.Enhance error handling at the end of a fax transmission.
      This change will stop a partially received FAX from being
      deleted if there is a problem during FAX transmission.
      (Defect 35778)


  • Update 4.2.0.113

    APAR IY78601 IY78525 IY78630 IY79416

    PTF U806295 U806296

    1.An IMC_XMLProvisioning process previously could wait a long time
      after a malformed XML provisioning request was received. This wait
      has been reduced to 60 seconds by default and can be altered in the
      INI file by adding a line such as the following to the [XMLGeneral]
      stanza:

         UponFailureDelay=30

      (this would change the wait to 30 seconds)
      (APAR IY78601)

    2.This change to start_aa and start_mr State Tables is for the
      AutoAttendant and Menu Routing applications. It has no observable
      change in behaviour, it is merely to bring the code inline with the
      startup State Table that was modified in a previous PTF to request 2
      more System Variables from the GlobalVariables Custom Server.
      (APAR IY78525)

    3.A fix to prevent files queueing in /var/spool/smdi/socket and not
      being delivered to IP addresses above 127.255.255.255.
      (APAR IY78630)

    4.Calls into submailbox accounts that do not hang up properly used to
      loop through and fill up the first submailbox. This problem has been
      fixed now.
      (APAR IY79416)



  • Update 4.2.0.112

    APAR IY77254 IY75349 IY77258 IY77362 IY77464 IY77870 IY78331 IY78378

    PTF U805949 U805951

    1.This fix resolves a problem whereby if the partition.info file does
      not exist then the db lookup function in IMC_XMLProvioning did not
      run. This has been resolved such that if the file is missing it will
      now be created in a default form and an error logged to highlight
      the issue to the system administrator.
      (APAR IY75349)

    2.The system won't coredump when uploading a corrupted or truncated wav
      file from web.
      (APAR IY77254)

    3.SM now displays only one connection with up to 256 ports, rather than
      two servers each with 128 ports.
      The position on the screen of ports above 128 has been corrected.
      (APAR IY77258)

    4.A fix to mwi_config for MWI to come on for aliases as well as the
      shared number for submailboxes. You will need to re-run mwi_config
      during a maintenance window after running UM_ptf_mgr in order to put
      this fix to the database triggers onto your system. It is recommended
      you use the parameters:
         mwi_config -first -any
      (APAR IY77362)

    5.The smdi_server coredumped when used with multiple LNP servers due to
      use of a non-threadsafe routine (scandir). This has now been
      resolved.
      (APAR IY77464)

    6.A problem with IMC_MessageCenterAPI not responding when a mailbox
      logged onto via the web has over 100 new or saved messages has been
      resolved.

      (Only the first 100 new or saved messages will be displayed on the
      web interface: this is a current limitation of
      IMC_MessageCenterAPI.)
      (APAR IY78378)

    7.The Admin utility adduser command will pick the right default values
      from IMCdefaults.file after this fix.
      (APAR IY77870)

    8.This fix changes the way in which prompts and voice segments are
      imported to WVR using the UM_ptf_mgr tool. Prompts and voice
      segments are now merged with the existing directories to ensure
      that any customer specific files are not overwritten.
      (APAR IY78331)

    9.A fix to mwi_config for MWI to come on for aliases and the main
      number. After feature 35498/PTF 104 the MWI for the main number did
      not come on. If you ran mwi_config following feature 35498/PTF 104
      you will need to re-run mwi_config during a maintenance window
      after running UM_ptf_mgr in order to put this fix to the database
      triggers onto your system.  It is recommended you use the parameters:
         mwi_config -first -any
      (Defect IY77362a)


  • Update 4.2.0.111

    APAR IY76105 IY77315 IY75321

    PTF U805708

    1.This change fixes a deprication in IMC_XMLProvisioning's
      handling of the specification of the department field in
      an XML request.
      (APAR IY76105)

    2.Fixed the resetting to zero of the count of the number of
      notification schedules when performing a moveuser. The
      counter of the number of notification schedules after a
      moveuser will now be the same as before the moveuser.
      (APAR IY77315)

    3.Fix to moveprofile not loading mailbox messages after an unload,
      when no user defined greeting is present.
      (APAR IY75321)

    4.Removal of VoiceRite Client-specific customization in IMC_STATS.

      For customers who do not have VoiceRite Client this will eliminate
      errors which appear indicating that the VR_ASST_NOTIFY state table
      does not exist.

      For customers who do have VoiceRite Client, note that this PTF has
      removed the VoiceRite Client customizations and you or VoiceRite will
      need to re-apply these in order for VoiceRite Client to work again.
      (Defect 35720)

    5.Fixed a typo in the help for the uncompress_messages utility.
      (Defect 35736)

    6.Improvement to the error message which appears in the event that
      there is an attempt to listen to a message where the compression type
      for voice messages was changed but messages had not been migrated.
      (Defect 35739)

    7.Removal of VoiceRite Client-specific customization in IMC_CLR_SMEN
      state tables.

      For customers who do not have VoiceRite Client this will eliminate
      errors upon importing the ASCII source for these state tables (found
      in $VAE/sw/st_src) which say that VR_INTERRUPT does not exist.

      For customers who do have VoiceRite Client, note that this PTF has
      removed the VoiceRite Client customizations and you or VoiceRite will
      need to re-apply these in order for VoiceRite Client to work again.
      (Defect 35777)





Fix level 110

APAR IY73536 IY74961
PTF U804886




  • Update 4.2.0.110

    APAR IY73536 IY74961

    PTF U804886

    1.This feature implements uncompressed voice messaging for
      Unified Messaging making the following changes:
        : Change to allow IMC_PlayMsg to play uncompressed messages
        : Change to allow IMC_Sendmail to get uncompressed messages
           out of the database for sending as e-mail attachments and
           VPIM messages
        : Change to allow IMC_Getmail to put uncompressed messages
           into the database when receiving VPIM messages
        : Change to allow IMC_MoveProfile to extract (unload) and
           insert (load) uncompressed messages
        : Change to IMC_IMAP4_Server to allow e-mail clients to
           retrieve uncompressed messages
        : Change to IMC_RemoteSystems to support uncompressed
           messages: particularly for DTM-D/inter-node messaging
        : Change to IMC_Broadcast to get and send uncompressed
           messages
        : Change to IMC_Attachment to create uncompressed messages
           for fax
        : New utility to convert compressed messages to uncompressed
           called uncompress_messages:
             uncompress_messages [-d] [-r] [-v] -A|-U
               -d : delete originals of migrated messages
               -v : verbose operation
               -r : reverse operation: create compressed messages
               -A : convert to A-law (E1) uncompressed format
               -U : convert to u-law (T1) uncompressed format

      (Features 35709UM, 35725)

    2.A problem with IMC_SMDI_Client correctly processing its connection to
      LNP servers: resulting in an inability to send some requests to LNP
      servers.
      (APAR IY74961)

    3.This PTF fixes an issue where the addPartition command can fail to
      add a partition due to the required directories not existing. It
      also corrects an issue where in the event of an error the system
      was not correctly cleaned up.
      (APAR IY73536)


  • Update 4.2.0.109

    APAR IY71877 IY72748 IY73537

    PTF U804304 U804305

    1.Reinstated SIP handling code into IMC_STARTUP.
      (APAR IY71877)

    2.SMDI Server has now been fixed to allow more than one connection
      from LNP Server.
      (APAR IY72748)

    3.Fixed problems in the aliases field when attempting to add an alias
      of the profile number itself. This prevented IMC_XMLProvisioning
      deleting the profile number subsequently as it appeared to be an
      alias of itself.
      (APAR IY73537)

    4.Fixed problem so now can log onto mailbox of 1 digit when dialling
      log-on number.
      (Defect 35442)

    5.Fixed problem so users added by the adduser utility (in IMC_Admin
      custom server), after the first one, will now appear in GUI, or in
      output of listuser.
      (Defect 35493)

    6.The system won't log any error, when the caller hangs up (before or
      after) while listening to a message.
      (Defect 35617)





Fix level 108

APAR IY71006 IY72170
PTF U803649 U803650




  • Update 4.2.0.108

    APAR IY71006 IY72170

    PTF U803649 U803650

    1.If a Residential subscriber (Type 3) requests their PIN to be emailed
      to them using the Web Interface, they are now presented with a
      message informing them that this feature is not available to them,
      and that they should contact Customer Services.

      The feature is not available to these subscribers because they cannot
      specify their email address using the Web Interface. If the System
      Administrator has added an email address to their profile, however,
      the feature will be available to them.  In this case, if the email
      address they enter matc hes the one in the database, their PIN will
      be emailed to them, otherwise they will be informed that the details
      they entered do not match the records.
      (APAR IY71006)

    2.This PTF fixes the incorrect behaviour of MWI, when converting a
      Private mailbox with new message to a Shared mailbox.
      (APAR IY72170)


  • Update 4.2.0.107

    APAR IY71213

    PTF U803587 U803588

    1.System Administrator's can now configure the system to allow
      subscribers to have up to 10 configurable notification schedules.
      The Administrator should add a new parameter called "NumSchedules"
      to the "GlobalVariables" section and give this a value of between 1
      and 10. The default value for this parameter is 3. This new
      functionality is only applicable to subscribers of types 5, 6, 7
      and 8.
      (APAR IY71213)


  • Update 4.2.0.106

    APAR IY69722

    PTF U803313 U803314

    1.This PTF removes the capability for an Administrator to configure
      the number of notification schedules for subscriber types 5, 6, 7 &
      8. This functionality was introduced in PTF 105 but due to an
      outstanding defect this causes problems.  This feature is being
      withdrawn until the underlying defect can be resolved.
      (APAR IY69722)

    2.Unknown callers are now shown as number ? (question mark) and name
      'Unknown Caller' rather than number 'Unknown Caller' and name 999999
      in e-mail notifications.
      (Defect 35535)

    3.The word 'urgent' in the email/pager notification message should have
      an upper case 'U' as in 'Urgent'.
      (Defect 35539)

    4.XML PROVISIONING

      A new command called GetPartition has been added to the XML
      Provisioning custom server to allow administrators to retrieve a
      list of subscribers from a partition.

      A new configuration parameter DBLookupTime should be added to the
      XMLGeneral section of the IMC_MessageCenter.ini file. This parameter
      should be given a four digit integer value, where the first two digits
      represent the hour and the second two digits represent the minutes at
      which the database lookup is performed to retrieve partition
      information.

      For example a value of 0215 would cause the database lookup to be
      started at 2:15am every day. Failure to provide a valid time value
      using DBLookupTime causes the database lookup to run at the default
      time of 2:00am.

      When the database lookup is performed, the data is stored in a new
      directory called $CUR_DIR/ca/partition. In this directory there is
      a single file that contains details of the partition names and their
      associated id numbers, together with a single file for each
      partition on the system.

      There are two methods of retrieving information from XML Provisioning.
      The first method is to supply a partition name, in which case all
      subscribers within that partition are returned.
      Note that the time stamp in the response message indicates the
      time at which the database lookup was performed.
      The second method is to supply a subscriber telephone number. Using
      this method, the system finds which partition contains that subscriber
      and returns a list of subscribers within that same partition.
      An example of both methods is given below:

       <?xml version="1.0" encoding="UTF-8" ?>

       <ProvisioningRequest xmlns="http://www.ibm.com">
        <MessageHeader>
         <MessageId>12345</MessageId>
         <Security userId="id" password="pw"/>
         <Sender name="Company"/>
         <TimeStamp> 2002-08-12T12:00:00</TimeStamp>
         <MessageType version="1.0">GetPartition</MessageType>
        </MessageHeader>

        <MessageBody>
         <SubscriberList>
          <GetPartition>
           <Subscriber telephoneNumber="8005551212"
                          accountId="8888888888"/>
          </GetPartition>
          <GetPartition>
           <Partition name="PartitionName"/>
          </GetPartition>
         </SubscriberList>
        </MessageBody>
       </ProvisioningRequest>

       GetPartition() response message example:

       <?xml version="1.0" encoding="UTF-8" ?>

       <ProvisioningResponse>
        <MessageHeader>
         <MessageId>12345</MessageId>
         <Security userId="id" password="pw"/>
         <Sender name="MC"/>
         <TimeStamp> 2002-08-12T12:00:00</TimeStamp>
         <MessageType version="1.0"<GetPartitionResponse</MessageType>
        </MessageHeader>

        <MessageBody>
         <Successes>
          <GetPartitionResponse>
           <Partition name="PartitionName" id="0006"/>
           <TimeStamp>2005-01-25T02:00:00</TimeStamp>
           <Subscriber telephoneNumber="8005551212"
                          aliases="8002221313;8005557777"/>
           <Subscriber telephoneNumber="8001111212"/>
           <Subscriber telephoneNumber="8002221211"/>
           <Subscriber telephoneNumber="8004441212"/>
           <Subscriber telephoneNumber="8005551111" mailboxes="3"/>
           <Subscriber telephoneNumber="8005551211"/>
           <Subscriber telephoneNumber="8005551213"/>
           <Subscriber telephoneNumber="8005551215"/>
           <Subscriber telephoneNumber="8005552222"/>
           <Subscriber telephoneNumber="8005557348"/>
           <Subscriber telephoneNumber="8005559826"/>
          </GetPartitionResponse>
          <GetPartitionResponse>
           <Partition name="PartitionName" id="0006"/>
           <TimeStamp>2005-01-25T02:00:00</TimeStamp>
           <Subscriber telephoneNumber="8005551212"
                          aliases="8002221313;8005557777"/>
           <Subscriber telephoneNumber="8001111212"/>
           <Subscriber telephoneNumber="8002221211"/>
           <Subscriber telephoneNumber="8004441212"/>
           <Subscriber telephoneNumber="8005551111" mailboxes="3"/>
           <Subscriber telephoneNumber="8005551211"/>
           <Subscriber telephoneNumber="8005551213"/>
           <Subscriber telephoneNumber="8005551215"/>
           <Subscriber telephoneNumber="8005552222"/>
           <Subscriber telephoneNumber="8005557348"/>
           <Subscriber telephoneNumber="8005559826"/>
          </GetPartitionResponse>
         </Successes>
        </MessageBody>
       </ProvisioningResponse>

       GetPartition error codes

      The following table lists the possible error return codes for
      the message:
       Code Message
       GP001 Invalid telephone number
       GP002 Subscriber does not exist
       GP003 Failed to get subscriber information due to internal
             Unified Messaging error
       GP004 Message Length exceeded due to number of subscribers in
             the partition

      (Defect 35549)

    6.IMC_Stats and FormatStats have been updated to support flags added
      in Unified Messaging Version 3.1 Fix ID 6.4.0.2000, including SS
      (message was saved).
      (Defect 35557)

    7.The custom server IMC_BroadcastCLI has been added to allow an
      administrator to send a broadcast message from the command line.

      IMC_BroadcastCLI provides a method for sending a broadcast to either
      a distribution list or partition from the AIX command line interface.
      It creates a broadcast control file which will be used by the
      IMC_Broadcast custom server to send the broadcast.  Authorisation for
      the sending of messages to a distribution list or partition is via
      the same authorisation file used by IMC_Broadcast.

      Syntax:
      The syntax of the command line function is:
      IMC_BroadcastCLI -f <filename> -o <originator> -d <destination>
                  -a <A | M>  [-u <n | u | e>] -t <timestamp>
      where:
      &n bsp;  -f <filename>  = the full path & filename of the .wav file that
                          will be imported as a voice message and sent as
                          message of the broadcast.
         -o <originator> = the profile number of the originator of the
                           broadcast
         -d <destination> = the destination that the broadcast will be
                            sent to. This can be either a distribution list
                            or a partition and are defined by Dxxxx and
                            Pxxxx respectively and where xxxx is the id of
                            the system distribution list or partition.
         -a <A | M> = the audio format that the .wav file will be imported
                      as. The format is <A | M> A = alaw and M = mulaw.
         -u <n | u | e > = the urgency of the Broadcast.  Where n=normal,
                           u=urgent and e=emergency. This parameter is
                           optional and the default is n (for normal).
         -t <timestamp> = the date/time that the message will be sent. The
                          timestamp is in the format YYYYMMDDHHMMSS. This
                          parameter is optional and the default is that
                          the message will be sent immediately.

      (Defect 35584)

    8.Performance enhancements for the IMC_Broadcast custom server.
      (Defect 35586)

    9.This fix resolves the issue whereby if the system is set to observe
      daylight savings time then the database lookup of the IMC_Broadcast
      custom server will be undertaken at the incorrect time.
      (Defect 35614)

    10.This defect resolves an issue with the IMC_XMLProvisioning custom
      server whereby the custom server will fail to correctly terminate
      the database lookup child process upon closing down.
      (Defect 35615)


  • Update 4.2.0.105

    APAR IY67846 IY68540

    PTF U802271 U802487

    1.A problem where after playing the last 9 seconds of a message the
      option to playback the entire message would only play the last 9
      seconds has been resolved.
      (APAR IY67846)

    2.A problem with IMC_LDAP_Client coredumping when copying its log
      file once it reached 2MB has been resolved.
      (APAR IY68540)

    3.The Quick Message function has been fixed.
      (Defect 35520)

    4.A problem where sometimes an e-mail notification would not be
      sent for new fax messages has been resolved.
      (Defect 35532)

    5.Problems associated with transferring a fax to the log-on
      prompt have now been resolved.
      (Defect 35533)

    New feature enhancements contained in this PTF

    1Modified the call flow for subscriber types 6 and 7 such that the
      save and un-delete verbiage are more terse after the first iteration
      of the call flow.
      (Feature 35550)

    2.Added capability for subscribers of type 6 and 7 to toggle between
      expert and normal prompts in the TUI.
      (Feature 35551)

    3.Added support for aliases to menu routing mailboxes.
      (Features 35552)

    4.Added support for a configurable number of notification schedules for
      susbcribers of types 5, 6, 7 and 8. This allows the administrator to
      configure the system such that subscribers can utilise between 1 and
      10 schedules.
      (Feature 35553)

    5.Made modifications to base Unified Messaging to allow VoiceRite
      Client to function correctly.
      (Feature 35556)


  • Update 4.2.0.104

    APAR IY66359 IY66367

    PTF U801311 U801312

    1.Modified the behaviour of the caller experience when subscribers are
      configured as types 5, 6, 7 & 8 with a subscriber class of IMC_INFOX,
      where X is a single digit or blank. The clr_smen state tables have
      been modified to check before playing segment "The message queue is
      full for the person you have called. You will now be disconnected.
      Thank you for calling. Good-bye." whether the subscriber class is
      IMC_INFO. If it is then the segment will be suppressed and the call
      disconnected.
      (Feature 35402)

    2.Added the capability for subscribers of type 5 to select the language
      that they wish to use in the TUI on the web page. This feature is
      available on other subscriber types and the code for it was taken
      from there.  The languages that are available were altered to meet
      specific requirements.
      (Feature 35405)

    3.Added the capability to subscribers of types 6 & 7 with shared
      mailboxes to log-out from the web or TUI interfaces without having to
      hang-up or select log-off. In the TUI this used existing code from
      other subscriber types to offer this option from the control menu.
      For the web interface this was done by adding a text box to the
      website to allow subscribers to enter the PIN of another mailbox and
      select a GO button. This button then attempts to log them on as it
      would if they had opted to log-out and log back in again. The new
      text box has been added to sideBar.jsp which in turn calls a new jsp
      called changeMailbox which performs the required log-off and log-on
      under the covers.
      (Feature 35419)

    4.Modified IMC_STARTUP to add additional entry points to allow the
      system administrator to configure IMC_STARTUP behaviour by setting
      the entry point rather than configuring an ini file to determine the
      ID/PIN requirements for subscribers logging in on platform access
      numbers.
      (Feature 35420)

    5.Modified the clr_dynmenu state table to allow subscribers of type 7
      to give their callers the option of transfering to the attendant/
      operator.  This change is basically just enabling the function that
      other subscriber types already had.
      (Feature 35423)

    6.Modified the behaviour of the XML Provisioning custom server to allow
      better control of which XML Groups could modify which users and also
      to extend the number of XML Groups which could be configured, thus
      giving administrators more flexibility in their configuration. The
      changes were made to the main and Messages files to check which XML
      Groups are required to enforce this new security as well as making
      the modification to allow any number of XML Groups to be configured.
      (Feature 35425)

    7.Modified the Menu Routing application to allow subscribers and
      administrators to configure whether a call was transferred to the
      subscribers telephone or whether it is transferred directly to the
      mailbox. IN order to achieve this the manage_tran state table was
      modified to read an extra config parameter from the db which
      indicated the intended destination type. The sbr_menu_10 state table
      was modified to allow subscribers to configure the setting. The
      transfer_options.c component of MessageCenterAPI was modified to
      allow the web interface to receive the correct information and allow
      configuration through that channel and the chk_mr state table was
      modified to continue to allow correct validation of the transfer
      numbers entered.
      (Feature 35439)

    8.Modified the IMC_Pager and IMC_Notify custom servers to allow
      greater control of which notification and template files were used
      by which subscriber.
      (Feature 35455)

    9.Modified the start_mr state table such that when transferring a call
      to an auto-attendant from the menu routing application the segment
      "Please hold while we transfer you..." is suppressed. This is because
      the auto-attendant is just a local profile, so will take zero time to
      transfer to, so the segment is in this case non-sensical.
      (Feature 35496)

    10.Broadcast messaging functionality has been enhanced to allow greater
      control of the impact of sending wide scale broadcasts.
      (Feature 35497)

    11.Added support for aliases to shared mailboxes. The majority of
      changes here were to Admin and XML code to support the configuration
      of these settings.  The IMC_GET_DEST state table needed to be
      modified to support sending of messages to these aliases, but all
      other state tables were correct as is. The get_dest change was done
      under feature 35497.
      (Feature 35498)

    12.The web interface was modified to correctly display information in
      the Apple Safari browser for subscriber types 5, 6, 7 & 8. All JSPs
      for these subscriber types had to be modified to correct the layout
      of nested tables which were handled differently to how they are in
      MS IE. Switching code based on browser type was implemented to allow
      the necessary format to be displayed.
      (Feature 35499)

    13.Added support for nested distribution lists. This allows the
      existing limit of 90 members in a distribution list to be overcome.
      The Dlist custom server was modified to support the creation of
      these lists and the state tables were enhanced to allow the nesting
      to be transparent to the caller. The MessageCenterAPI custom server
      was also modified to allow the nesting to be transparent to web
      users.
      (Feature 35500)

    For more information about the above features please read
    /usr/lpp/dirTalk/sw/MessageCenter/PTF104.README.

    New fixes contained in this PTF:

    1.Fixed deletion of Shared Numbers so that aliases were updated
      correctly.
      (APAR IY66359)

    2.Additional processes used by IMC_Pager did not always cache pager
      format files correctly, resulting in failures to format and send
      pager messages where more than one pager format was being used and
      more than one IMC_Pager process was responsible for formatting and
      sending messages.
      (APAR IY66367)





Fix level 103

APAR IY65549 IY65944 IY65949 IY65952
PTF U801253 U801254




  • Update 4.2.0.103

    APAR IY65549 IY65944 IY65949 IY65952

    PTF U801253 U801254

    1.Fixed the following problem:-
      : Forward a voice message to another subscriber WITHOUT a comment
      : The recipient should then listen to, and delete the message
      : Forward the same voice message again, to the same subscriber,
         WITHOUT a comment
      : The recipient should then listen to, and try to delete the
         message
      : The message will not be deleted
      (APAR IY65944)

    2.A fix to IMC_Admin to ensure that the MWI of an alias has the correct
      state after an alias is added to a mailbox which already has new
      messages.
      (APAR IY65949)

    3.This fix ensures that 2 character locale strings specifying language
      only can be used on the Web Interface.
      (APAR IY65952)

    4.A fix to prevent looping in IMC_OCALL_MAKE when the main and backup
      pager numbers are configured in a notification schedule.
      (APAR IY65549)

    5.This fix prevents the VoiceXML2 browser from attempting to prefetch
      obsolete grammars for the voice interface.
      (Defect 35224)

    7.This fix ensures that when a user ID other than dtuser is used to
      run WebSphere Voice Response, it will not be deleted if it is set
      as the administrator of a partition if the partition is deleted.
      (Defect 35295)

    8.This fix ensures that MCIT can be used to create remote nodes whose
      numbers start with #.
      (Defect 35376)

    9.This fix ensures that callers can attempt to reach or page Standard
      subscribers when using:-
        : the System announce-only greeting
        : a remote System greeting
        : the System greeting and the caller requests help
      (Defect 35377)


  • Update 4.2.0.102

    APAR IY62192 IY62201 IY63139

    PTF U800388 U800389

    New features contained in this PTF

    1.The Barring functionality allows the UM administrator to define
      which numbers subscribers are permitted to set as transfer numbers,
      and which numbers are disallowed, by editing a simple configuration
      file. The barring rules may be varied depending on transfer function
      and Class of Service.

    New fixes contained in this PTF

    1.Resolved problem with downloading very large messages files using
      the web interface (eg, 10 minutes using AU format, 50 minutes using
      MS-GSM format).
      (APAR IY63139)

    2.Enable forwarding of Faxes with Voice comments added.
      (APAR IY62201)

    3.This fix ensures that subscribers' mailbox_busy flags can be set
      or unset using the XML Provisioning interface.
      (Defect 35210)

    4.This fix ensures that subscribers' business hours can be changed
      using XML Provisioning.
      (Defect 35211)

    5.This fix ensures that a subscriber's outgoing message count can
      be set using the XML Provisioning Interface.  This is useful if
      the message count is incorrect due to a previous error.
      (Defect 35212)

    6.This fix ensures that the XML Provisioning interface will recognise
      the attribute name 'partition' instead of the deprecated
      'department'.
      (Defect 35213)

    7.This fix ensures that subscribers' message counts can be changed
      using XML Provisioning.
      (Defect 35216)

    8.This fix ensures that subscribers' business hours can be changed
      using XML Provisioning.
      (Defect 35209)

    9.This fix allows the subcriber type to be changed using the
      'subscriber_type' attribute.
      (Defect 35198)

    10.The smdi_tty process in /home/smdi/bin has been modified to allow
      it's parent process time to initialize before exiting if it cannot
      open all the resources it needs. The extra time prevents a race
      condition occuring in the parent process' signal handling code.
      (Defect 35126)

    11.Comments were added to the lnp_servers file in /home/smdi/bin
      detailing file format and giving some examples.
      (Defect 35127)

    12.A mechanism was added to detect reliably when the IMC_SMDI_Client
      custom server disconnects from the lnp_server process and close
      the LNP server's end of the connection correctly.
      (Defect 35160)

    13.The start_smdi.rc script in the /home/smdi/bin directory was modified
      to detect if another instance of the script is running. The script
      now displays a warning message and exits if invoked more than once.
      (Defect 35158)

    14.This fix ensures that callers can attempt to reach or page Standard
      subscribers who are using the System greeting, and listen to their
      noticeboards.
      (Defect 35250)

    15.This fix ensures that nodes whose numbers start with a # can be
      selected from a list in MCIT.
      (Defect 35236)

    16.This fix ensures that, in the graphical version of MCIT, when
      changing and showing subscriber details:

      a. The language code is shown and can be selected if it is 2 or 3
         digits long
      b. The subscriber type is shown and can be selected if it is 10
         (Menu Routing) or 11 (Auto Attendant)

      and that in both versions of MCIT, subscriber type 9
      (Telephony Portal) is not included in the list of options, since
      these subscribers do not have profiles on the WVR system, but use
      an LDAP server instead.
      (Defect 35348)

    17.This fix ensures that the Custom Server Summary File is created with
      the correct filename when installing PTFs.
      (Defect 35334)

    18.This fix ensures that IMC_Barring is always started, and the IPL
      status set to AUTOEXEC, when PTF 102 is installed using UM_ptf_mgr.
      This custom server is now used by default by state tables that check
      whether setting this number is allowed at this location.
      (Defect 35335)

    19.This fix ensures that when the graphical version of MCIT is used to
      list all remote nodes, or all subscriber authorizations, the table
      headers are correctly displayed.
      (Defect 35238)

    20.Ensure IMC_Barring observes Class of Service (COS) values correctly.
      (Defect 35174)

    21.This fix ensures that incomplete barring rules in the barring.rules
      file are ignored.
      (Defect 35349)


  • Update 4.2.0.101

    APAR IY60641 IY60692 IY60709 IY60737 IY60738 IY60740 IY60742 IY60743

    PTF U800007 U800017

    1.Sending a test email from the web interface caused
      IMC_MessageCenterAPI custom server to leave a defunct process.
      (APAR IY60641)

    2.Created new Notifcation Template files to be used for Remote Message
      Delivery Subscribers which do not mention the number of New and Saved
      messages.
      (APAR IY60692)

    3.A fix to make IMC_STARTUP correctly report the absence of a mailbox
      on the number called.
      (APAR IY60709)

    4.This fix allows outbound phone numbers of up to 20 digits in length.
      (APAR IY60737)

    5.Temporary Reach-me code has been re-instated for subscriber type 0
      only.
      (APAR IY60738)

    6.This fix ensure the MCMainControl=-2 setting suppresses the new
      message beep for all logon scenarios.
      (APAR IY60740)

    7.Fixed a problem wheereby if IMC_Admin's configuration file
      IMCdefaults.file contained "password_change_date = xxxxx" then the
      value specified was being used as the default password instead of
      default password change date.
      (APAR IY60742)

    8.A fix to moveuser to ensure greetings and audionames are moved
      correctly if a subdirectory
      for the greetings does not already exist.
      (APAR IY60743)

    9.For fax messages, the message heard using the voice interface is
      corrected and refers the caller to use the web interface to access
      the message.
      (Defect 31586)

    10.Callers to voice interface can now use the 'backup' command
      (accessed using the * key) during the login prompt to try
      re-entering login information.
      (Defect 31626)

    11.This fix ensures the backup key (*) works correctly while changing
      password using the voice interface.
      (Defect 31628)

    12.This fix allows customers who use the Voice Interface
      to bypass the Add Sender prompt by pressing the # key.
      (Defect 31702)

    13.This fix improves performance by not initialising a parameter for
      bargeIn when it is not used (other than for inputModes, which is
      initialised separately), and when it is used, by using a boolean
      parameter instead of the string that was previously used, and by
      hardcoding instead of using variables in jsp files that are only
      visited when barge-in has a certain value.
      (Defect 34494)

    14.This fix ensures the Voice Interface jsp files can compile on
      WebSphere Application Server V5.1.
      (Defect 35190)

    15.This fix adds a <NewLanguage> XML element to allow the language of
      the main number of a shared mailbox to be changed.
      (Defect IY58015a)

    16.This fix ensures XSD validation works correctly using the
      xml4c_5_4_0 parser libraries.
      (Defect 35199)

    17.This fix adds the <LanguageType> definition to the XSD.
      (Defect 35206)