Fix list for WebSphere Voice Response for AIX, Version 4.2

Technote (FAQ)


Question

What PTFs have been released for IBM Websphere Voice Response for AIX, Version 4.2?

Answer

The following is a complete listing of PTF updates for WebSphere Voice Response for AIX, Version 4.2 and the fixes included within them, with the most recent PTF updates at the top.

PTF updates can be ordered via your IBM representative OR downloaded from Fix Central (for more details go to How to obtain PTFs for WebSphere Voice Response for AIX )

Back to WVR support


Base changes:

Features:




Fix Level 4.2.0.594 (PTF U859888 )
Fix release date: 06 Jun 2013
Status: Current (devices)
APAR Description
IV41217 Fix potential AIX crash when reading last RTP packet of a call once the call has actually been terminated. The vnaio driver will attempt to do a read on a blocking socket in an interrupt handler which is not allowed.
IV43395 Fix a problem concerning outbound DTMFs. In some situations the DTMF current outbound can become stuck and never finish sending. This causes all future outbound DTMFs to never be sent.


Fix Level 4.2.0.593 (PTF U858601 U858602 )
Fix release date: 05 Apr 2013
Status: Current (dirTalk.DT)
APAR Description
IV36695 Fixed VAGIO buffer leak when using the dtimport command.
Internal Defect fix
  • This PTF contains changes to the help text associated with the VOIP proxy mode parameter. These changes clarify the support and operation of the Automatic Service Lookup:DNSSRV method.


Fix Level 4.2.0.591 (PTF U858423)
Fix release date: 11 Mar 2013
Status: Superseded
APAR Description
IV37151 Set RFC2833 RTP DTMF marker bit in first packet of each DTMF to fix a problem where DTMFs are not detected on outbound SIP calls that use the DTNA.


Fix Level 4.2.0.587 (PTF U854140 U854141 )
Fix release date: 26 Sep 2012
Status: Superseded
APAR Description
IV27669 Fixed an issue with a customer who needed to register to a proxy added the Proxy= line to master.ini parsing, which allows a user to set a target to set a proxy address. This is an optional field that, if set, specifies an IP address to register to for the registrar. The Registrar will be used in all TO, FROM and CONTACT headers in the message but the message will be sent to the proxy address.


Fix Level 4.2.0.582 (PTF U851834 U851837 )
Fix release date: 28 Jun 2012
Status: Superseded
APAR Description
IV20221 Update the CNAME entry in RTCP packets to correctly follow the CNAME specification. This is formatted as aappcc@ip. Where aa is adapter number, pp is packet number, cc is channel number and ip is the ip address of the WVR machine.


Fix Level 4.2.0.578 (PTF U851650 U851651 )
Fix release date: 24 Apr 2012
Status: Superseded
APAR Description
IV19055 Fixed a problem where vae.setuser incorrectly reverted any changes made by the dtjes script. This caused the system to revert back to using an earlier ECMAScript version.
Internal Defect fix
  • Fixed 3 problems in the SIP REGISTER mechanism:
    1. Fixed the CSEQ to increase by 1 for each new message rather than incorrectly remain at 1.
    2. Corrected the code to recognise an expiration length if received within the contact header rather than in an expires header.
    3. Added a RegisterAs option for those registrars that do not deal with hostnames, only IP addresses. By default, WVR will use its hostname contact address.
      RegisterAs is used to specify an IP address or hostname to override the default value on a per-host basis in the master.ini file. See the description in $SYS_DIR/voip/master.ini.orig for more details.


Fix Level 4.2.0.575 (PTF U850311 )
Fix release date: 22 Feb 2012
Status: Superseded

APAR Description
IV15416 Fix SIP INFO DTMFs not being correctly sent from the DTNA to WVR. This occurs if the SIP call hasn't negotiated RFC2833.


Fix Level 4.2.0.569 (PTF U844523)
Fix release date: 30 Sep 2011
Status: Superseded

APAR Description
IV07731 Fix a problem with loopback RTP packets from the vnaio to the vnaio. The receiving code can leak a data buffer. This eventually causes AIX to run out of buffers. The problem ONLY occurs when the vnaio sends to itself via a direct loopback. As SIP doesn't allow this is it requires and external endpoint to terminate two SIP calls. Once the two SIP calls have been created the RTP flow has to be negotiated away from the terminating endpoints so WVR streams to itself.
IV07894 Update the DTNA/vnaio driver to handle badly constructed RFC2833 DTMF packets. The DTMFs are now placed at the same timestamp as the audio and maintain and set length and gap. This will stop DTMFs with the wrong timestamp and/or duration being placed "correctly" but then ignored by the DTNA.


Fix Level 4.2.0.568 (PTF U844496 U844498 U844499 U844500 )
Fix release date: 12 Sep 2011
Status: Superseded

APAR Description
IV06036 Added a new DTMF algorithm variant 2 that will only report DTMFs that are on for at least 60ms (Note, this is a Field access level system parameter). This should only be used if double detections are occuring for DTMFs and the audio stream contains a smaller clipped DTMF before the real DTMF. This can occur when TDM voice is converted to VoIP and then back to TDM before entering the DTXA/DTTA. The gateway doing the TDM to VoIP conversion can end up leaving a little bit of the original tone before declaring an RFC2833 DTMF. When the stream is converted back into TDM the RFC2833 generates a new tone sometime after the original tone. Thus two DTMFs appear in the audio stream.

Internal Defect fix
  • Updates to the dtProblem script to collect information about WVR licence acceptance.


Fix Level 4.2.0.565 (PTF U844286 U844288 U844290 U844291)
Fix release date: 29 Jul 2011
Status: Preventative Maintenance

APAR Description
IV03204 Updated WVR V4.2 licenses for ECMAScript 1.7 support.

Fix Level 4.2.0.563 (PTF U844097 U844098 U844099 )
Fix release date: 8 Jul 2011
Status: Superseded

APAR Description
IV02049 Added support for tromboning between:
1) RFC2833 to SIP INFO DTMF
2) SIP INFO DTMF to RFC2833
3) SIP INFO DTMF tp SIP INFO DTMF
4) RFC2833 to RFC2833 (support already present)

Add support for two SIP INFO DTMF content types:
1) dtmf-relay
2) vnd.nortelnetworks.digits

Internal Defect fixes
  • Add support for full software TDM in the DTNA. The original support only allowed either normal or full trombone operation on the DTNA. The custom server CA_TDM_Connect subroutine now allows all TDM combinations to be altered on DTNA (as per DTXA and DTTA). This change allows recording of other channels, DSP (WVR) and Line (customer).
  • Add socket state information in DTNA to make the socket handling more robust. This will stop situations where sockets can not be bound but are then used potentially resulting in a system crash.


Fix Level 4.2.0.560 (PTF U843406 )
Fix release date: 24 May 2011
Status: Superseded

APAR Description
IZ96849 Prevents AIX crashes with DTNA when ports cannot be bound and allows port ranges to be configured above 32000.
IZ96603 Fixed problems with missing DTMFs when using RFC2833 on the DTNA. This can occur when the far end leaves gaps in the RTP stream between DTMF end and audio start.



Fix Level 4.2.0.559 (PTF U842218 )
Fix release date: 18 Apr 2011
Status: Current (DT)

APAR Description
IZ96410 Add auto restarting of DBHEALTH should the code stop running. This will stop the WVR database being stuck in the not running/down state.
IZ96634 Fixed an issue which would result in a 0 length duration being reported for recordings that ran until the maximum duration edge was returned.

Internal Defect fix
  • Fixed a problem to ensure that the VXML2 termchar shadow variable is set after a <record> is terminated by a DTMF key.


Fix Level 4.2.0.552 (PTF U839807 )
Fix release date: 2 Dec 2010
Status: Current (artic960.ucode)

APAR Description
IZ88941 This fix overcomes a possible yellow alarm 17035 error (Network does not respond) at first startup of WVR when configured as T1 CAS e.g. T1 FXS/LS. Previously with trunks set to auto-enable at startup (i.e. Enabled and InService) the error could occasionally occur when first starting up.


Fix Level 4.2.0.550 (PTFs U838610 U839169 U839170 U839182 )
Fix release date: 9 Nov 2010
Status: Preventative Maintenance

APAR Description
IZ85719 New features contained in this PTF:
  • Enhanced VoiceXML and CCXML application support for call information - Provide protocol specific tagging information in VXML and CCXML.
  • VRBE Expire Resource Tool - allows a system administrator to manually expire a resource in the VXML, CCXML or Audio caches.
  • Support for SIP Registration - provides support for the SIP registration method described in RFC 3261.
  • New VoIP Signalling - Inbound Call Channel Allocation Method. A new Inbound Call Channel allocation option called "Allocate calls for D2IS" has been added to system configuration to control the channel used for DTNA based calls. This option is for use when using the Genesys-supplied D2IS custom server in a behind-the-switch Genesys Framework implementation.
  • Trombone Custom Server Enhancement - allow called party to pass back a termination value to calling party.
  • VRBE problem determination utility - enables a system administrator to collect a dtbeProblem output (or run any other command) automatically when an error or other message is reported in VRBE.

For further information on the Fix Pack 2 features please refer to the TechNote at the following URL:

http://www.ibm.com/support/docview.wss?rs=761&uid=swg21449523
IZ85721 Fixed a device driver problem involving freeing invalid memory when unconfiguring devices. On AIX6 this generates GEN_XMDBG errors in errpt.

Internal Defect fixes
  • Usability updates to the DTcheck_bin utility.
  • Report back correct error code when attempting to log into the same mailbox simultaneously.
  • Fixed auto restart scripts for the DTNA adapter.
  • Fixed incorrect message length reported when pausing the message during recording. The length used to just contain the last segment of the message rather than all segments.
  • Fixed a potential problem with vae.setuser when changing the default WVR user from dtuser to another AIX user id. Before the fix there was a chance that any new executables shipped as a result of fixes etc would not have their file ownership changed to the new user.


Fix Level 4.2.0.528 (PTFs U837317 U837318 )
Fix release date: 14 Sep 2010
Status: Superseded

APAR Description
IZ84481 Fixed a machine crash due to a race condition where the DTNA sends trunk information to the WVR device driver during a shutdown. The WVR device driver attempts to access the trunk information from the DTNA via an internal structure which has since been freed.

Internal Defect fix
  • Fixed a problem with restarting WVR devices if WVR was still runningwhen the machine was rebooted. If the dtline devices end up in the defined state then WVR doesn't recover the devices correctly. This results in script errors appearing in DTstatus.out and trunks failing to appear in WVR.


Fix Level 4.2.0.527 (PTF U836883)
Fix release date: 3 Sep 2010
Status: Superseded

APAR Description
IZ83272 Fixed a problem with message deletion. If the receiving mailbox deletes the message without listening to it the sender is getting an acknowledgment without the actual voice message. When the sender listens to the acknowledgement an error is generated.


Fix Level 4.2.0.521 (PTF U836466)
Fix release date: 12 Jul 2010
Status: Superseded

APAR Description
IZ77313 Fixed a DTNA problem whereby it is possible for two packets to arrive on each socket and deadlock the system as the packets are sent of the opposite/partner sockets. The fix is to unlock channel sockets before sending out RTP packet, to allow for the race condition with two tromboned channels attempting to send packets to, using each others socket.


Fix Level 4.2.0.520 (PTFs U835668 U835670 )
Fix release date: 10 Jun 2010
Status: Superseded

APAR Description
IZ75932 Fixed a system crash that can occur during the main WVR device driver processing of an adapter pack DMA whilst the adapter is crashing. This is a very small timing window as the adapter has to be crashing during DMA processing. Any adapter crash can cause this system crash.


Fix Level 4.2.0.517 (PTF U835664)
Fix release date: 7 May 2010
Status: Superseded

APAR Description
IZ75007 A new internal tool has been shipped to check that any IBM supplied state tables are installed correctly. The tool runs automatically when WVR is started and will output messages into DTstatus.out if any user action is required.


Fix Level 4.2.0.516 (PTF U833983)
Fix release date: 14 Apr 2010
Status: Superseded

APAR Description
IZ74126 Encapsulate voice codec functions into a more usable form and support for new UM libraries.


Fix Level 4.2.0.515 (PTF U833727)
Fix release date: 5 Mar 2010
Status: Superseded

APAR Description
IZ69787 When a pack was in equipped or defined state the SNMP vPackType request returned the pack type (e.g. "T Pack T1") while the documentation stated that when the pack was in either of these states a vPackType request should return "Unassigned". This fix brings the vPackType request inline with the documentation.


Fix Level 4.2.0.513 (PTF U832497)
Fix release date: 10 Feb 2010
Status: Superseded

APAR Description
IZ67757 This fix enhances sample state table applicaton IBMTromboneCall to enable the calling application (e.g. IBMTromboneXmp) to distinguish between original caller hangup both before and after a successful trombone transfer. Previously the same error was returned for both cases and this prevented accurate statistics collection of successful verses failed trombone transfers.




Fix level 510

APAR IZ67478
PTF U832489 U832213 U832187 U832186 U832212
  • Update 4.2.0.510


    APAR IZ67478

    PTF U832489 U832213 U832187 U832186 U832212


    1.This PTF contains the consolidatation of fixes shipped since
      the last premaint level.
      (APAR IZ67478)

  • Update 4.2.0.499


    APAR IZ60801

    PTF U829118

    1.This PTF level is mandatory to allow system to be migrated
      from WVR 4.2.3 to WVR 6.1
      The option to save to tape using direct write and to save
      individual files have been removed and are unsupported
      by WVR version 6.1 restoreDT.
      (APAR IZ60801)

  • Update 4.2.0.474


    APAR IZ60109

    PTF U828064

    1.Modified the DTNA code to prevent an error_id 29800
      from occuring if the "Inbound DTMF Method Override"
      system parameter is set to "DTMF via SIP info".
      (APAR IZ60109)

  • Update 4.2.0.465


    APAR IZ54200

    PTF U827376

    1.Updates to PD scripts.
      (IZ54200)

    2.Corrected the file permission of $SYS_DIR/ipcid.log so that
      it is no longer world writeable.
      (Defect 36809)

  • Update 4.2.0.463


    APAR IZ52978 IZ52950 IZ52854

    PTF U826173 U825884

    1.This fix allows WVR to receive DTNA RTP (VoIP) data sent
      from the same machine, a condition which previously resulted
      in a 29801 error.
      (APAR IZ52978)

    2.Fix a device driver crash during the setup of a remote record.
      The crash most likely occurs when used with MRCP as this heavily
      uses remote record. When the crash occurs the machine will lock
      up during a reco attempt.
      (APAR IZ52854)

    3.This fix corrects a DTMF detection issue with DTNA when using the
      Siemens OptiPoint 420 Advance S phone.
      (APAR IZ52950)

    4.Stop freeing DMA chains on the DTNA. This causes error entries to
      be reported in errpt concerning xmfree and "General xmalloc debug
      error (Defect 36718)

  • Update 4.2.0.457


    APAR IZ48300

    PTF U824647 U824648

    1.This fix corrects a DTNA DTMF defection problem which may
      have caused the first DTMF of a call to be lost.
      (APAR IZ48300)

    2.This PTF also updates trace template required by VOIP_SIP ptf
      Fix level 4.2.0.456)
      (Defect 36655)

  • Update 4.2.0.451


    APAR IZ44906

    PTF U824350 U824351 U824352

    1.Fix a memory freeing error on the DTTA adapter support.
      (APAR IZ44906)

    2.This fix corrects a problem in the WVR main device driver
      which could potentially cause a system crash.
      (Defect 36524)

    3.The contents of the dtsnmpd.my MIB definition file have
      been changed to fully document the meaing of the possible
      values for the vpackType variable. The possbile values are:

    vpackType OBJECT-TYPE
      SYNTAX INTEGER
      ACCESS read-only
      STATUS mandatory
      DESCRIPTION
        "Shows the type of each of the packs installed. This value
         is not set if the pack is in the 'Defined' or 'Equipped'
         state. Possible values are:
          o 0 - Unassigned (pack is in 'Defined' or 'Equipped' state)
          o 1 - VPACK T1 (no longer supported)
          o 2 - VPACK E1 (no longer supported)
          o 3 - RPACK (no longer supported)
          o 4 - SPACK E1 (no longer supported)
          o 5 - Wrap Plug (no longer supported)
          o 6 - VPACK (no longer supported)
          o 7 - SPACK T1 (no longer supported)
          o 8 - XPACK E1
          o 9 - XPACK T1
          o 10 - XPACK OTHER (DTXA base only or DTXA with Wrap Plug)
          o 11 - TPACK E1 (DTTA)
          o 12 - TPACK T1 (DTTA)
          o 13 - EPACK E1 (DTEA)
          o 14 - EPACK T1 (DTEA)
          o 15 - NPACK E1 (DTNA)
          o 16 - NPACK T1 (DTNA)"
        Note (Last line is double : ) = { vpackEntry 2 }
      (Defect 36529)

  • Update 4.2.0.449


    APAR IZ44408

    PTF U824348

    1.This fix corrects a problem which could result in a
      system crash.
      (APAR IZ44408)

  • Update 4.2.0.448


    APAR IZ43471

    PTF U824347


    1.This fix corrects a deadlock situation with DTNA which
      could cause a system hangup.
      (APAR IZ43471)

  • Update 4.2.0.446


    APAR IZ40264

    PTF U823638

    1..This fix corrects a DTNA DTMF defection problem in WVR.
      (IZ42540)

  • Update 4.2.0.444


    APAR IZ40264

    PTF U823635 U823636

    1.Change the 10 seconds auto reset/retrieval of mailbox
      information to also ensure schedule information is auto
      retrieved. This will stop schedule information in system
      variables disappearing after 10 seconds.
      (APAR IZ40264)

    2.This fix corrects a problem which could cause a system
      crash under unusual condititons.
      (Defect 36548)

  • Update 4.2.0.441


    APAR IZ37083 IZ37889

    PTF U822403

    1.This fix corrects an intermittent DTMF detection problem
      with DTNA.
      (APAR IZ37083)

    2.This fix corrects a tromboning deadlock situation with DTNA.
      (APAR IZ37889)

  • Update 4.2.0.439


    APAR IZ37662

    PTF U822400 U822399

    1.This PTF fixes corrects a problem that has potential to
      cause a system crash (but not so far seen)
      (APAR IZ37662)

    2.This fix corrects a problem in the WVR main device driver
      which could potentially cause a system crash.
      (Defect 36489)

  • Update 4.2.0.433


    APAR IZ35009 IZ33121 IZ34658

    PTF U821505 U821506

    1.This PTF fixes a potential race condition and resulting core
      when an TDM abort is issued by the client, and the client
      disappears before the response can be sent.
      (APAR IZ35009)

    2.This fix corrects a problem in DTNA with RFC2833-encoded
      DTMF handling where keys were being ignored.
      (APAR IZ34658)

    3.This fix makes wvrtrunk more robust when interrupted by
      e.g. cntrl-C
      and also added additional error messages.
      (APAR IZ33121)



Fix level 430

APAR IZ33638
PTF U821408 U821409 U821410 U821411 U821412 U821413
  • Update 4.2.0.430


    APAR IZ33638

    PTF U821408 U821409 U821410 U821411 U821412 U821413

    1.This PTF corrects a problem which can happen on systems
      with the country in an unassigned state.
      (APAR IZ33638)

  • Update 4.2.0.425


    APAR IZ33141

    PTF U819609 U819863 U819864


    1..This PTF adds India country support for Pack and
      System Configuration.
      (APAR IZ33141)

  • Update 4.2.0.421


    APAR IZ30063 IZ30264 IZ30765

    PTF U819609 U819863 U819864


     This PTF was withdrawn and is replaced by fix level 4.2.0.430

     All fixes detailed below can be found in 4.2.0.430


    1.This fix corrects an occasional problem where wvrtrunk
      gets into an internal permanent error state
      (until WVR is restarted) if wvrtrunk is interrupted
      before completion (e.g. with cntrl-break).
      (APAR IZ30063)

    2.This fix allows WVR to correctly receive RTP payload
      DTMF keys (RFC2833) when far end delays (does not stop)
      voice RTP during DTMF sequences
      (APAR IZ30765)

    3.This PTF fixes a race condition between a CA_Close_CHP_Link
      followed by a CA_Open_CHP_Link from a different custom server
      (or different process within the same custom server).
      The race condition results in a CHP becoming unusable by
      the custom server and a CA_LINK_NOT_OPEN being returned.
      (APAR IZ30264)

    4.Fix a problem with incorrectly reported adapter loading
      with the 64 bit operating system. The problem caused
      occasional spikes in reported adapter loading resulting
      in errors being generated in WVR.
      (Defect 36418)

    5.Change access authority on G711 echo cancellation span
      in DTEA/DTNA System Parameter group to admin to allow
      user to increase echo canc span to 32ms for G711 only.
      (Defect 36417)

  • Update 4.2.0.417


    APAR IZ24049 IZ26968

    PTF U819504

    1.This fix corrects two locking problems which could
      cause occasional system crashes when using DTNA.
      (APAR IZ24049)

    2.This fix corrects a problem with DTNA (VoIP) where voice
      recorded from particular SIP phones resulted in empty voice
      recordings.
      (APAR IZ26968)

    3.This fix corrects an extremely rare red alarm on some
      systems which indicated that the DTNA interrupt handling
      time had exceeded 20ms. This was due to the Network
      Time Protocol daemon in AIX updating the system clock to get
      it in sync with other machines in the same network.
      (Defect 36380)

  • Update 4.2.0.414


    APAR IZ25964

    PTF U819344 U819345

    1.This PTF provides a fix to CHPM crashes when attempting
      to report an error.
      (APAR IZ24446)

  • Update 4.2.0.410


    APAR IZ25964

    PTF U819344 U819345


     This PTF was withdrawn and is replaced by fix level 4.2.0.430

     All fixes detailed below can be found in 4.2.0.430


    1.This PTF adds base support required by ISDN progress
      Indicator Information Element ( IE ).
      (APAR IZ25964)


Fix level 400

APAR IZ23274
PTF U818269 U818270 U818271 U818272 U8181294 U8181295 U818296
  • Update 4.2.0.400


    APAR IZ23274

    PTF U818269 U818270 U818271 U818272 U8181294 U8181295 U818296  

    1.Premaintence level WVR correct system crash with
      64bit driver System can crash at shutdown.
      (APAR IZ23274)

    2.Fix up a 32/64 problem between DTNA and DTDD on
      power 6 machines.
      (Defect 36369)

    3.Tighten requsite filesets.
      (36370)

  • Update 4.2.0.369


    APAR IZ21032

    PTF U818264 U818266

    1..This fix corrects a bug in the debugmon tool when DTNA
      devices are not in the normal order.
      Also contains the 'debugrec' voice recording
      tool (simplified debugmon)
      The debugrec voice recording tool considerably simplifies
      what is required to take a diagnostic voice recording or
      adapter trace (currently done using the debugmon tool).

      Usage:  debugrec <trunk> <channel> <option>

      <trunk> is the WVR trunk number in the range 1 to 16 and
      <channel> is the WVR channel number (both as displayed on
                the WVR System Monitor).

      All other parameters (e.g. adapter type, trunk type) are
      taken from WVR internal configuration information.

      debugrec can operate in one of 3 modes:

       1) Default (no options) .. recording is continuous
          (until stopped) and a stereo wav file is created where
          the left channel is 'line out' i.e. what WVR is playing
          to the line and the right channel is 'line in' ie.
          what WVR is receiving from the line.
          File name is /tmp/vrec_line_stereo.wav.

       2) Option -v .. debugmon option 'v' compatibility.
          Recording is continous (until stopped) to three(DTXA/DTTA)
          or four (DTNA) files in /tmp/.
          File names are of the form vrec*.

       3) Option -a ... debugmon options '8' and '9' compatibility.
          Recording is done to a 25 second circular buffer on the
          adapter. Also records adapter DSP commands and status.
          Creates files in /tmp/ of the form trace_rec*.
      (APAR IZ21032)

    2.This PTF adds support for DTTA and DTEA on a 64-bit AIX Kernel.
      (Defect 36358)

    3.Corrected test in diagnostic routine DT6_check_db2
      (Defect 36357)

    4.Updated dtProblem to collect crontab and atJob entries.
      (Defect 36361)

  • Update 4.2.0.365


    APAR IZ19324

    PTF U817181

    1.Correction to DTEA/DTTA driver problem.
      (APAR IZ19324)

  • Update 4.2.0.364


    APAR IZ17987

    PTF U817178

    1.Integrating late DMA write times before logging a 27404
      error.
      (APAR IZ19363)

    2.Updated dtProblem to preserve dates on collected data.
      (Defect 36348)

  • Update 4.2.0.362


    APAR IZ17987

    PTF U817178

    1.Provides recovery when a DTEA DSP VOIP ports occassionally
      goes out of service.
      (APAR IZ17987)

  • Update 4.2.0.360


    APAR IZ17685

    PTF U817031 U817037 U817038

    1.This PTF adds support for DTNA on a 64-bit AIX Kernel.
      NOTE: Only DTNA is supported in 64-bit operation.
      (APAR IZ17685)

  • Update 4.2.0.351


    APAR IZ15552

    PTF U816334

    1.This PTF Modifies the socket handling code in TSLOT and the
      MRCP CS to prevent errno 72 (ECONNABORTED) from
      terminating the processes.
      This PTF contains the TSLOT changes. If you have
      dirTalk.SpeechClient installed on the system, it must be at
      level 4.2.0.350 which contains the MRCP CS changes.
      (IZ15445)

  • Update 4.2.0.349


    APAR IZ15369

    PTF U816102 U816103


    1.This fix allows WVR to recover from DTEA port 'Out of Service'
      conditions which may result from a message timing condition
      at call hangup.
      NOTE This fix also requires dirTalk.VOIP_SIP to be at fix
           level 4.2.0.348
      (APAR IZ15369)

    2.Report reason for Custom Server build failure if the total
      number of arguments exceeds the allowed limit.
      (Defect 36297)

  • Update 4.2.0.343


    APAR IZ12489

    PTF U815931 U815932 U815933 U815937


    1.This PTF adds additional utility functions to Batch Voice
      Import (BVI) custom server to easily import and export audio
      data between the WVR voice segment database and 'wav' files.
      New utilities are called bvi_wav_exp and bvi_wav_imp
      (use utility without any parameters for help information).

      Refer to the 'The Batch Voice Import process' in the 'WVR
      for AIX V4.2
    - Application Development using State Tables'
      manual
     for more details.
      Link to the
    WVR for AIX, V4.2 library here.
      (APAR IZ12489)

    2.Adds base functions required to support SIP enhancements
      (See fix level 4.2.0.344 and 4.2.0.345)
      (Feature 36151)

    3.Prevent Voice Table "Save As" from generating error if source
      is from the Default Application.
      (Defect 36266)

    4.Update diagnostic utility DTmon to show language for Voice
      Map Table.
      (Defect 36265)

  • Update 4.2.0.341


    APAR IZ11250 IZ08450

    PTF U815635

    1.Correct PlayPrompt operation with Large Voice Tables which
      could lead to error 800 (Voice Table not Found).
      (APAR IZ11250)

    2.The configuration parameter Number of Non Swap State Tables
      in the Application Server Interface can now be used to
      increase the amount of shared memory allocated to prompt
      directories and voice tables. Prior to this fix, customers
      with a very large number of prompt directories or voice
      tables, or those running multiple languages on a system
      may have encountered problems accessing prompt or
      voice tables.
      (APAR IZ08450)

    3.Update diagnostic utility DTmon to provide more detailed
      information on prompts and Voice Tables.
      (Defect 36263)

  • Update 4.2.0.338


    APAR IZ09678 IZ10879

    PTF U815452 U815453 U815457

    1.Corrected a problem in vae.setuser when used on a WVR server
      with the dirTalk.VRBE filesets installed.
      (APAR IZ09678)

    2.Corrected the TTL and TOS settings for DTNA RTP packets.
      (APAR IZ010879)

    3.In AIX 5.3 and later, the compiler flag _MSGQSUPPORT must be
      defined in order to use message queues. As message queues are
      a common thing to use in with custom servers, this fix defines
      the above flag permanently on so that custom servers will function
      as before.
      (Defect 36261)

  • Update 4.2.0.335


    APAR IZ09662

    PTF U815181 U815182

    1.Allow the LogEvent action to write logs which are
      greater than 2GB on Large File Enabled file systems.
      (APAR IZ09662)


Fix level 321

APAR IZ09215 IZ06395
PTF U814700 U814701 U814702 U814703 U814704 U814705 U814706 U814707 U814708
  • Update 4.2.0.321


    APAR IZ09215 IZ06395

    PTF U814700 U814701 U814702 U814703 U814704 U814705 U814706 U814707 U814708

    1.This fix corrects a problem shipped in level 4.2.0.301 of
      devices.dirTalk.artic960.rte where silence was being received
      from VoIP devices when using DTNA.
      (APAR IZ09215)

    2.This PTF fixes a problem where CA_Record_Voice could return
      a dBm level of zero on the first usage of a channel.
      (APAR IZ06395)

  • Update 4.2.0.311


    APAR IZ06113 IZ06535 IZ06585

    PTF U814346

    1.This fix corrects the dBm level calculation for
      imported voice segments (including the playing of wav
      files using vxml where multiple files played sequentially
      could be played at different levels prior to this fix).
      (APAR IZ06113)

    2.Stop potential application import problem involving
      removing incorrect files.
      (APAR IZ06585)

    3.This fix corrects the handling of data and stack limits by
      startDT, invoked on re-boot by vaeinit.pre, for limits of
      4GB and over. Prior to this fix large limits may have
      been misinterpreted or ignored due to integer overlows.
      It is advisable to check that the limits specified for
      dtuser in /etc/security/limits are correct as detailed in AIX
      files reference.
      (APAR IZ06535)

  • Update 4.2.0.310


    APAR IZ06590

    PTF U814344 U814345

    1.Fix IBM Trombone custom server to stop the 1000 and 1001 errors
       Note: Importing IBM_Trombone.imp will revert the IBMTrombone
             state Tables to their original forms. If any custom
             changes have been made these changes will need to
             be reapplied.
      (APAR IZ06590)


Fix level 301

APAR IZ05697
PTF U813549 U813755 U813756 U813887 U813888
  • Update 4.2.0.301


    APAR IZ05697

    PTF U813549 U813755 U813756 U813887 U813888

    1.Fixes problem with DTNA sending outbound DTMF digits
      immediately after receiving inbound digits.
      (APAR IZ05697)

  • Update 4.2.0.298


    APAR IZ05312

    PTF U813381

    1.Prevent error 20503 with Internal error
      error_id = TROMBONE013 being generated if the Incoming
      Caller hangs up during the connection of the Outbound Call.
      Note: Importing IBM_Trombone.imp will revert the IBMTrombone
            state Tables to their original forms. If any custom
            changes have been made these changes will need to
            be reapplied.
      (APAR IZ05312)

  • Update 4.2.0.296


    APAR IZ04782 IZ05055

    PTF U813379 U813380

    1.Allow Audio Adapter FC8244 to operate with Ultimedia
      Voice Control and Batch Voice Import (BVI).
      (APAR IZ04782)

    2.Prevent error 1000 being generated if the Incoming Caller
      hangs up before the Outbound Call is answered.
      Note: Importing IBM_Trombone.imp will revert the
       IBMTrombone state Tables to their original forms.
       If any custom changes have been made these changes
       will need to be reapplied.
      (APAR IZ05055)

    3.Updated diagnostics tests to handle full hostname when
      checking db2 settings.
      (Defect 36182)

  • Update 4.2.0.295


    APAR IY99278 IZ04045

    PTF U813377 U813378

    1.Fixed a problem concerning respawned CHP's deleteing voice
      messages before they can be sent.
      (APAR IY99278)

    2.This fix resolves a problem where a long hostname in
      the file /home/dtdb23in/sqllib/db2nodes.cfg prevented
      the WVR system from starting.
      (APAR IZ04045)

    3.Added call to db2level to diagnostic routines.
      (Defect 36168)

    4.Updated help text for DTMF variant 1.
      (Defect 36141)

    5.Corrected path for lsdev in diagnostic routines.
      (Defect 36158)

  • Update 4.2.0.294


    APAR IZ03459

    PTF U812855 U812856 U812857

    1.Correct occasional loss of voice when tromboning
      between DTTA and DTEA.
      (APAR IZ03459)

    2.This defect corrects the operation of DTMF detection
      'Algorithm Variant 1'
      (Defect 36165)

  • Update 4.2.0.292


    APAR IZ01903

    PTF U812852

    1.This PTF stops CHP's ending up in an infinite loop during
      multiple WaitEvent actions after a call has dropped.
      (APAR IZ01903)

  • Update 4.2.0.285


    APAR IY99497

    PTF U811971

    1.This PTF updates help information concerning enhanced VOIP
      functions.
      (APAR IY99497)

  • Update 4.2.0.283


    APAR IY97868

    PTF U811969

    1.This fix allows an SS7 E1 WVR client to be
      configured with a trunk interface E1 Framing Mode
      of E1 multiframe (CRC4) instead of the default of
      double frame.
      Previously a red alarm error 27010 (Pack enablement
      failed) would occur when the trunk was enabled.
      Leaving a double frame setting when the attached switch
      expects multiframe could lead to red alarm RAI errors
      17007 (E1 remote alarm indicator qualified alarm)
      at trunk startup.
      (APAR IY97868)

  • Update 4.2.0.279


    APAR IY98269

    PTF U811644 U811645

    1.This fix modifies the $LANG environment variable if the
      base AIX system language is set to ja_JP and sets
      it to en_US
      (APAR IY98269)

    2.Correct ISDN Layer 4 trace entries.
      (Defect 36123)

    3.Updated help text for latest trunk types.
      (Defect 33983)

  • Update 4.2.0.275


    APAR IY97474

    PTF U811639 U811640


    1.This fix corrects clocking operation for mixed DTTA/DTEA systems
      a) DTTA(s) are are always used as source of the main system clock
         (on H.100 bus) with DTEAs always being slaves on the bus,
      b) The DTEA echo canceller is periodically reset every 10 seconds to
         allow it to continue to operate even if slip is occurring in the
         TDM network.
      NOTE If fileset dirTalk.VOIP_SIP is installed on the system, it will
           need updating to fix level 4.2.0.276.
      (APAR IY97474)


Fix level 270

APAR IY96222
PTF U811271 U811339 U811340 U811341 U811342 U811343
  • Update 4.2.0.270

    APAR IY96222

    PTF U811271 U811339 U811340 U811341 U811342 U811343

    1.dtProblem now collects information on 3270 sessions
      configured.
      (APAR IY96222)

    2.dtSummary will now report machine processor speeds, and
      check for the presence of UM.
      (Defect 36057)

    3.Correct trace formatting for ISDN.
      (Defect 36070)

    4.Add extra trace entries for error conditions.
      (Defect 36073)

  • Update 4.2.0.254


    APAR IY94296

    PTF U810945


    1.This PTF changes the handling of VoIP DTMF packets
      (RFC2833) to improve the reliability of detection when
       used with Cisco equipment.
      (APAR IY94296)

  • Update 4.2.0.251


    APAR IY93740

    PTF U810929

    1.This change will recover pool buffers in the case of
      a suspended X-Server or X-Server death.
      (APAR IY93740)

  • Update 4.2.0.250


    APAR IY93551

    PTF U810928

    1.Fixed a problem in MWISERVER that caused spurious
      error_id 5103 to be reported.
      (APAR IY93551)

    2.Corrected import checking phase in utility
      DT6_check_files.
      Prior to this fix, DT6_check_files always
      reported not imported.
      (Defect 36056)

  • Update 4.2.0.243


    APAR IY92925

    PTF U810595

    1.This adds function to SDIEXEC required by SS7 feature.
      (APAR IY92925)

  • Update 4.2.0.241


    APAR IY92374

    PTF U810591 U810592

    1.Add new column to "DTmon -l" output to show fixed in
      memory State Tables.
      (APAR IY92374)

    2.Prevent "DTmon -l" core dumping in case where State Table
      is partially loaded.
      (Defect 36048)

    3.Updated diagnostic code.
      (Defect 36051)

    4.Minor correction to ISDN trace formatting to show
      the L3 messages correctly.
      (Defect 36052)

    5. This update will change the way that packetized DTMF
      keys (RFC2833 encoded) are handled by WVR to improve robustness
      and compatibility with different VoIP phones.
      (Defect 36053)

  • Update 4.2.0.238


    APAR IY91591

    PTF U810397 U810588

    1.This feature adds a special case to the GetPassword state table
      action such that if it is called with a timeout parameter of 0 and
      a timeouts allowed parameter of 20 then the caller will not be prompted
      for a password, but the mailbox will be locked.
      (APAR IY91591)

    2.Corrects missing text in System Configuration parameters
      (SIP Signalling -> Use Request Header) and DTNA Media->Overload.
      See online help text on this parameters for more details.
      Note that for the SIP parameter, as well as selecting the header
      to be used for the Called Number, it also controls whether the
      Request Header is extracted to the Tagged String or not.
      (Defect 35946)

  • Update 4.2.0.236


    APAR IY91328

    PTF U810394

    1.Fixed UPSERVER (and VAGSERVER)  so that they deliver
      acknowledgements to listened messages to the correct
      sending profile, rather than a random profile.
      (APAR IY91328)

    2.Updated diagnostic routines
      (Defect 36035)

  • Update 4.2.0.233


    APAR IY90681

    PTF U809890

    1.The fix corrects a problem with DTEA adapter (VoIP/SIP only) when
      the first channel on a DTEA can get locked in a 'dead air' (i.e.
      not sending or receiving VoIP packets) state due to ICMP
      'Destination Unreachable' messages flooding a queue.
      (APAR IY90681)

  • Update 4.2.0.231


    APAR IY90466 IY90110 IY89379

    PTF U809682 U809791

    1.Fixes a CHP preformance issue which would be especially apparant
      when using a fair number (>5) nested state tables with a largeish
      (>50) number of variables.
      (But it should improve performance of all state table applications)
      (APAR IY90466)

    2.Changed library routine Notify_appl to prevent core dump when passed
      a negative value. This could cause PROMPTM and other components to
      core dump.
      (APAR IY90110)

    3.Updated firmware for DTEA cards.
      This corrects a fault which could cause
      'LOSS OF DTMF FOR INBOUND VOIP CALLS'
      (APAR IY89379)

    4.Added a check to DTst so that specifying a State Table name greater
      than 15 characters will cause it to exit with rc=1.
      (Defect 36024)

    5.Updated diagnostic aids
      (Defect 36010)

  • Update 4.2.0.229


    APAR IY88950

    PTF U809562

    1.Fixes problem where the same file imported twice (using dtjplex)
      was measured at a different db level each time.
      (APAR IY88950)

  • Update 4.2.0.228


    APAR IY89482

    PTF U809402 U809403

    1.This fix provides SS7 loopback support for T1.
      (APAR IY89482)

    2.A utility has been added called DT6_check_all.
      This utility runs underlying utilities which check db2, devices,
      files and space availability and produce a report.
      This utility has been added to dtProblem.
      NOTE: these utilities must be run as user root and are
      diagnostic aids.
      (Defect 35999)

  • Update 4.2.0.225


    APAR IY87920

    PTF U809396 U809397

    1.Increase the tolerance on Cadence Hangup tone detection.
      (APAR IY87920)

  • Update 4.2.0.223


    APAR IY87497

    PTF U808885

    1.Increase the size of additional_call_info1 to allow
      more information to be passed to the outbound trombone leg.

      Note, importing IBM_Trombone.imp will revert the
      IBMTrombone state tables back to their original forms.
      If any custom changes have been made these changes
      will need to be reapplied.
      (APAR IY87497)

  • Update 4.2.0.222


    APAR IY87242 IY87413

    PTF U808883 U808884

    1.Prevent ISDN error 29212 being generated if a Java
      Application is called from a State Table afer a MakeCall.
      (APAR IY87242)

    2.Fix a problem with TDM connection requests where the
      connection id is 0. This primarily affects faxes.
      (APAR IY87413)

    3.This problem corrects a timing problem on the DTTA and DTEA
      adapters which could cause failures on a small number
      of adapters.
      (Defect 35980)

    4.Improvement to dtProblem to detect DTNA adapter settings.

      (Defect 35978)

    5.Correct trace formatting for BufPool entries.

      (Defect 35976)

  • Update 4.2.0.219


    APAR IY85040

    PTF U808520

    1.Allow the Signalling channel to display on the System
      Monitor when less than 24 channels are configured on
      an T1 ISDN trunk.
      (APAR IY85040)

  • Update 4.2.0.216


    APAR IY86011 IY86049 IY85883

    PTF U808515 U808514

    1.Add extra boundary checking when sending strings from
      state tables to custom servers.
      (APAR IY86011)

    2.Correct a very rare problem with AC and the System Monitor
      which can incorrectly report zero Pool Buffers resulting in a
      negative number for Pool Buffers in use on the AC
      Operations Menu.
      (APAR IY86049)

    3.A fix has been applied that will cause the failure to
      locate .vaeprofile when checking db2_support to notifiy
      user of the error.
      (APAR IY85883)

  • Update 4.2.0.211


    APAR IY84166 IY83966 IY84366

    PTF U807571 U807570

    1.Correct debugmon option "v" (voice record) for DTTA adapter
      to prevent buffer overrun errors.
      (APAR IY84166)

    2.Stop EDGE_ABORT and technical difficulty message being played
      during a WaitEvent that has the event cleared as its being
      read. This very small timing window can be found if the
      WaitEvent detects something at exactly the same time an
      external custom server clears the event.
      (APAR IY84366)

    3.Correct dtProblem script to allow non-numeric PMR numbers
      to be entered.
      (APAR IY83966)

    4.Remove a timing window in trying to connect channels on the
      TDM as calls are going away. Before this fix there is a chance
      of ending up with one-way audio on the next call.
      (Defect 35942)

    5.Add pending TDM connection states to TSLOT to handle timing
      window whilst hanging up a call as its being tromboned.
      (Defect 35938)

    6.Add throttling code to the DTNA and SIP stack. This is to
      prevent the DTNA using more than (theoretically) 15ms of
      the 20ms processing cycle. At 15ms and above the SIP stack
      will start rejecting incoming SIP calls. Every 1000 rejected
      calls a warning will be generated to inform that this is
      happening. Ideally the system should not be driven at a call
      load higher than is possible to process.
      NOTE
      dirTalk.VOIP_SIP fileset must be at fix level 4.2.0.212 as well
      (Defect 35922)

  • Update 4.2.0.209

    APAR IY83694

    PTF U807395

    1.This fix corrects a problem where VPD (Vital Product Data)
      information such as serial number could be stale
      i.e. it could refer to a previous adapter.
      (APAR IY83694)

  • Update 4.2.0.207

    APAR IY82580 IY82257 IY81776

    PTF U807392 U807393

    1.Improve the general robustness of TSLOT
      (cores during error handling).
      Stop TSLOT starting connection servers that are not
      required due to hardware.  Stop TSLOT looping and
      filling up the trace.
      (APAR IY82580  APAR IY82257 APAR IY81776)

    2.The IBM_Trombone custom server has been altered to allow
      the outbound call to be aborted before the actual MakeCall
      is made. To implement this the IBMTromboneOut state table has
      been altered. A WaitEvent has been added just before the
      MakeCall to test for EDGE_HUP.

      If you wish to allow the outbound call to be aborted before the
      MakeCall and have altered (or copied) the IBMTromboneOut state
      table then the same change needs to be applied to the altered
      (or copied) version. If the state table is left alone
      everything will function exactly as before.

      Please note, importing the IBM_Trombone import file will
      overwrite the IBMTrombone state tables.
      (Defect 35920)


Fix level 200

APAR IY81504
PTF U806911 U806921 U806922 U806924 U806925 U806929 U806930
  • Update 4.2.0.200

    APAR IY81504

    PTF U806911 U806921 U806922 U806924 U806925 U806929 U806930

    1.Add support for Virtual Adapter ( adapterless DTNA) solution.
      (APAR IY81504)

  • Update 4.2.0.195

    APAR IY81360

    PTF U806897

    1.Voice Message attachments would not be deleted correctly
      when using the System Configuration General parameter
      "Set Real Time Migrate Voice Files - ON latest formats".
      Note: You can check and correct sny undeleted message
        attachments by using the "vm_integrity -v -f" command .
      (APAR IY81360)

    2.Changed DBCLNUP to remove empty Voice Message Attachment
      directories so that empty Voice Message directories will
      be deleted.
      (Defect 35893)

  • Update 4.2.0.192

    APAR IY81135

    PTF U806885

    1.Prevent a very rare occurence of VAGSERVER closing down
      due to a corrupted message queue.
      (APAR IY81135)

    2.Corrected a problem on AC which can cause it to core dump
      during password entry if backspace is used.
      (Defect 35844)


Fix level 190

APAR IY80213
PTF U806532
  • Update 4.2.0.190

    APAR IY80213

    PTF U806532

    1.This PTF corrects a problem seen only on newly installed
      systems after fix level 4.2.0.181. The problem was
      reported as RC=11.
      (APAR IY80213)

  • Update 4.2.0.184

    APAR IY79984 IY79931

    PTF U806377 U806378

    1.Correct a problem using Import with Preview which would
      sometimes fail with error SQL0117N on Subscriber Classes.
      (APAR IY79984)

    2.Correct a theoretical timing problem in the DTTA
      adapter microcode which could cause cause the
      adapter to crash.
      (APAR IY79931)

    3.The interval of polling for the System Paramters Database
      Availablity Check Timeout and File Availablity Check Timeout
      is now one quarter of the timeout as descibed in
      Configuring the System.
      (Defect 35836)

    4.Corrected message generated when running DTsnmpd.cfg
      (Defect 35830)

    5.This fix provides more comprehensive error message reporting
      for restoreDT utility
      (Defect 35750)

    6.Improvements to error reporting in .vaeprofile
      (Defect 35749)


Fix level 181

APAR IY78830
PTF U806179 U806184 U806186 U806188 U806189 U806194 U806290
  • Update 4.2.0.181

    APAR IY78830

    PTF U806179 U806184 U806186 U806188 U806189 U806194 U806290

    1.This PTF extends support to the following:

      Support for AIX 5.3 ML02

      Support for LPAR with some limitations. See the Book "General
      Information and Planning" GC34-6380-05 for more details.

      The following pSeries servers are now supported by WVR 4.2.2
      with the DTXA, DTTA and DTEA adapters or in any attached D20
      I/O drawer.
         eServer p5 520 (9111-520)
         eServer p5 550 (9113-550)

      Note: The following adapters are supported in these systems
            or in any attached D20 I/O drawer, but not if LPAR is
            being used.
               The DTXA adapter
               The SS8 (vendor) SS7 adapter
               The Brooktrout (vendor) TR1034 FAX adapter

      Note: The older Brooktrout TR114 FAX adapter is NOT supported
            in these machines.

      The following pSeries server is now supported by WVR 4.2.2
      with the DTTA and DTEA adapters or in any attached D20 I/O
      drawer.
         eServer p5 570 (9115-570)

      Note: The following adapters are supported in this system
            or in any attached D20 I/O drawer, but not if LPAR is
            being used.
               The SS8 (vendor) SS7 adapter
               The Brooktrout (vendor) TR1034 FAX adapter

      Note: The older Brooktrout TR114 FAX adapter is NOT supported
            in these machines.

      Support for ISA (IBM Support Assistant)
      (APAR IY78830)

    2.dtProblem has been enhanced to prompt the user to enter the
      PMR number if known.
      If provided the PMR number will be appended to the start of
      the output filename ready for transmission to IBM.
      (Defect 35782)

  • Update 4.2.0.169

    APAR IY78592

    PTF U805959

    1.Corrects a problem handling adapter EEH errors in which
      an error hitting one adapter might affect others.
      (APAR IY78592)

  • Update 4.2.0.168

    APAR IY78530

    PTF U805955

    1.Correct a rare buffer leak on DTXA and DTTA adapters
      when using CCS signalling processes.
      This would eventually lead to an adapter crash.
      (APAR IY78539)

  • Update 4.2.0.166

    APAR IY78257

    PTF U805948

    1.This fix corrects a problem where the execution of
      vae.setuser caused the MRCP Custom Server to fail to
      start and give no failure indication. Now vae.setuser will
      not affect the MRCP Custom Server.
      (APAR IY78257)

  • Update 4.2.0.164

    APAR IY78074

    PTF U805946

    1.If an adapter crashes when calls are in progress and
      the State Table application has non-telephony actions
      such as DoNothing it is possible that recovery may fail.
      This fix will retry for up to 60 seconds while waiting
      for the State Table application to complete.
      (APAR IY78074)

  • Update 4.2.0.163

    APAR IY77767

    PTF U805772 U805928 U805929

    1.Add FXS Loop Start and FXS Ground Start to default
      switch type in Pack Configuration for Japan.
      (APAR IY77767)

    2.Allows WVR to recover if a DTTA adapter error
      (e.g. PCI bus parity error or timeout) occurs on an
      adapter other than rpqio0 when operating in an LPAR
      environment
      (Defect 35800)

    3.Change startup scripts to prevent an SSI DB Server without
      adapters reporting adapter errors.
      (Defect 35790)


Fix level 160

APAR IY77163 IY77220
PTF U805632 U805633 U805634 U805635 U805641 U805706 U805707
  • Update 4.2.0.160

    APAR IY77163 IY77220

    PTF U805632 U805633 U805634 U805635 U805641 U805706 U805707

    1.Corrected spelling in Color.res file to prevent errors.
      (APAR IY77163)

    2.Removed single quote characters from comments in all
      $DB/resources/.res files to prevent errors on WVR startup.

      Note: If any of these files have been changed then please
      backup the changes before installing this PTF and then insert
      the changes back into the .res files again afterwards.
      (APAR IY77220)

    3.Change user help text for error 30510 and also startup
      error message to aid user problem determination.
      (Defect 35751)

  • Update 4.2.0.150

    APAR IY75990

    PTF U804885 U804884

    1.This PTF adds to WVR the ability to record and playback
      voice messages in uncompressed form (prior to this change,
      all messages were compressed using the built-in 5:1
      algorithm).

      This feature is controlled via a new System Parameter
      in the ASI (Application Server Interface) group known
      as 'Voice Message Compression Type'.
       Note that WVR must be restarted for
       'Voice Message Compression Type' to take effect.

      Setting this variable to 'Uncompressed' means that the
      Voice Messaging state table actions (Record and Play Voice
      Message) will not compress (or decompress) voice messages
      between the telephone line and the database. It also means
      that the voice messaging custom server actions must specify
      uncompressed voice as the data type when the system is set
      to use uncompressed messages. The current setting is
      available to custom servers in the new global variable
      CA_MSG_COMP which will be set to UNCOMPRESSED_VOICE
      or COMPRESSED_VOICE depending upon the setting of
      'Voice Message Compression Type'.

      NOTE that a WVR System (either standalone, Single System
      Image (SSI) or (SSI) with UM Inter Node Messaging)
      CAN NOT mix compressed and uncompressed messages.
      The new system parameter must only be changed when the
      voice database is empty if not using IBM Unified Messaging.
      IBM Unified Messaging will ship with a utility to migrate
      between compressed and uncompressed messages which will
      allow a change to an existing IBM Unified Messaging
      system without requiring the entire voice message
      database to be deleted.
      (APAR IY75990)

    2.Change user help text for error 17984.
      (Defect 35733)

    3.Change user help text for error 26003.
      (Defect 35732)

  • Update 4.2.0.145

    APAR IY75802

    PTF U804883

    1.This fix prevents VAGSERVER core dumping if a
      LANGUAGE is corrupt
      (APAR IY75802)

    2.This fix prevents VAGSERVER or STPDSERVER core dumping
      if the database is corrupted with a blank name.
      (Defect 35727)

  • Update 4.2.0.144

    APAR IY75681

    PTF U804881

    1.Fix the VOX_CTI custom server to solve occasional
      timeout problems.
      Installing this custom server will replace the
      VOX_CTI.ini file in
      /usr/lpp/dirTalk/db/current_dir/ca/VOX_CTI_dir
      This must be backed up, or recreated after installing
      the custom server
      (APAR IY75681)

  • Update 4.2.0.141

    APAR IY74955

    PTF U804576

    1.Fix the make call response when the inbound call hangs
      up whilst an outbound trombone call is being made.
      This fix stops the white 1001 error from IBM_Trombone
      being generated.
      (APAR IY74955)

  • Update 4.2.0.139

    APAR IY74564 IY74501

    PTF U804310 U804311

    1.Corrects a problem tromboning between channels
      (APAR IY74564)

    2.This PTF chamges four system variables to read/write.
      The System variables are SV186, SV187, SV188 and SV189
      (APAR IY74501)

  • Update 4.2.0.137

    APAR IY74036

    PTF U804303

    1.Improve handling of an incorrect/malformed port set in
      a CA_TDM_Connect API call.
      (APAR IY74036)

  • Update 4.2.0.134

    APAR IY73949

    PTF U804243

    1.Increased the maximum number of Custon Servers that
      the ASCII Console (AC) can display from 80 to 150.
      (APAR IY73949)

  • Update 4.2.0.127

    APAR IY68504 IY73016

    PTF U803997

    1.This fix will now pass To and From header SIP URI's from
      and inbound call on to the vxml browser.
      Pack configuration must be configured with the Channel
      ID's value set to 0, otherwise the Channel ID number
      will be passed to vxml instead of the sip uri.
      The To and From URI's will be present in the following
      session variables :
            session.connection.local.uri
            session.connection.remote.uri
      (APAR IY68504)

    2.This change checks that the DB/2 file db2nodes.cfg has the
      correct hostname configured.
      (APAR IY73016)

  • Update 4.2.0.123

    APAR IY73539

    PTF U803963

    1.This fix corrects a problem in the DTTA adapter microcode
      which resulted in either
      1) occasional dead air problems (one way audio) when doing
         a trombone between channels on two DTTA adapters.
      2) Brroktrout fax problems where it appears that the fax
         card is not receiving audio from the line
      (APAR IY73539)

  • Update 4.2.0.121

    APAR IY72979

    PTF U803957

    1.This fixes a problem where local variables may not be
      reset to zero on repeated calls of the same state table.
      (APAR IY72979)

  • Update 4.2.0.117

    APAR IY71878 IY72670

    PTF U803948 U803949 U803950 U803952


    1.Corrected the cleanup of the db2start log files to prevent
      spurious errors.
      Before applying the fix you must change the permissions on the
      directory to allow uneccessary files to be deleted.

      su root
      cd /home/dtdb23in/sqllib
      chmod g-t log
      chmod a-t log
      (APAR IY71878)

    2.Correction to error that prevents multiple mailbox messages
      being deleted though GUI.
      (APAR IY72670)

    3.This ptf fixes a problem encountered because pSeries firmware
      added additional checking.
      (Defect 35583)

    4.Minor changes to DTTA device driver to fix system test issues
      which will not affect WVR normal operation.
      (Defect 35464)


Fix level 102

APAR IY71660
PTF U803641 U803642 U803643 U803644 U803645
  • Update 4.2.0.102

    APAR IY71660

    PTF U803641 U803642 U803643 U803644 U803645

    1.This PTF supplies enhancements required by the SpeechClient
      fileset which supports interfaces to IBM WVS 5.xx systems.
      (APAY IY71660)

    2.This fix adds a new level of detail to the tracing provided.
      Included are more tracepoints, and now the Java layer CallID
      is given in the trace output.
      (Defect 35546)

  • Update 4.2.0.85

    APAR IY71431

    PTF U803586

    1.This PTF increases the number of supported notification
      schedules from 5 to 10.
      (APAR IY71431)

    2.This defect fixes a problem where data from a single function
      was incorrectly sent to the trace file for formatting, resulting
      in the trace for this function showing an incorrect id value.
      (Defect 35655)

  • Update 4.2.0.84

    APAR IY70771 IY71271 IY71337

    PTF U803585

    1.This fix prevents large numbers of db2start error log files
      collecting in the /home/dtdb23in/sgllib/log directory.
      Before starting the system after applying the fix you must change
      the permissions on the directory to allow uneccessary files to
      be deleted.

      Please perform the following commands

      su root
      cd /home/dtdb23in/sqllib
      rm -r log
      mkdir log
      chown dtdb23in:staff log
      chmod u+rwx
      chmod g+rws
      chmod a+rx

      NOTE You MUST PERFORM the above statements as root
      (APAR IY70771)

    2.Corrected a problem when excluding custom servers from an
      application import.
      (APAR IY71337)

    3.This fix stops VAGSERVER from coring if it receives corrupt content
      when trying to open a state table in the GUI.
      (APAR IY71271)

  • Update 4.2.0.82

    APAR IY70756 IY70758

    PTF U803321 U803322 U803323

    1.Correct the situation where sometimes an adapter problem would
      not reliably recycle the adapter.
      Note: An adapter problem which previously reported four 17301
      errors with "PACK INT,CNF ER" will now report a single 17302
      error.
      (APAR IY70576)

    2.Prevent su authentication errors from OAM occuring when
      starting WVR.
      (APAR IY70578)

    3.This corrects a problem where an 'interrupts have drifted' yellow
      warning message 27078 was generated when the adapter performed an
      internal resynchonization when the built-in self-test diagnostics
      detected that a time-slot slippage had occurred. The changed code
      will still perform the rescynchronization operation but in such a
      way that interrupt timing is unaffected.
      (Defect 35632)

  • Update 4.2.0.80

    APAR IY69881

    PTF U803312

    1.Enhancements to support QSIG feature as shipped in fix levels
      4.2.0.78 and 4.2.0.79
      NOTE slsigpr.h has been shipped in this PTF.
           If this file has been used in any privately generated
           code, the objects created should be re-compiled using the
           latest version shipped in this PTF.
      (APAR IY69881)

  • Update 4.2.0.77

    APAR IY69692

    PTF U802840

    1.This change limits the notification schedule ids to function in
      the range of 0 to 4.
      A previous increase in the range enabled by PTF 4.2.0.71 was
      found to be unsatisfactory and may cause buffer corruptions.
      (APAR IY69692)

  • Update 4.2.0.76

    APAR IY69689

    PTF U802839

    1.This ptf fixes a problem encountered because pSeries firmware
      added additional checking
      (APAR IY69689)

  • Update 4.2.0.72

    APAR IY68286 IY68860

    PTF U802511

    1.Show Application Voice Segment list in numerical
      sequence (GUI).
      (APAR IY68286)

    2.This corrects a problem where SDIEXEC could core dump
      during trunk enable after restarting a signalling process.
      (APAR IY68860)

  • Update 4.2.0.71

    APAR IY68588

    PTF U802489

     IT IS STRONGLY RECOMMENDED THAT THIS PTF BE APPLIED ASAP

    1.WVR has been modified to allow notification schedule ids in
      the range 0-9 inclusive, up from the previous range of 0-4.
      (APAR IY68588)

    2.Fix a potential loop when hanging up in the middle of a
      multiple TSLOT connections
      (Defect 35578)

  • Update 4.2.0.70

    APAR IY68242 IY68377

    PTF U802269

    1.This defect fixes an error where a voice segment created by saving
      an existing segment with a new ID from the GUI was saved in the
      database with the wrong compression type.
      (APAR IY68242)

    2.This corrects a problem where a signalling process sending a
      SL_CALL_RECONNECT_CNF with a parameter of SL_REPLY_CALLER_HUNG_UP
      would cause the signalling process to become unregisterd.
      (APAR IY68377)

    3.This update modifies the database constraints on MAILBOX_NFY
      to allow up to 10 notification schedules to be configured for
      an individual subscriber. The previous limit was 4 notification
      schedules
      (Defect 35560)

  • Update 4.2.0.69

    APAR IY67801

    PTF U802267

    1.Correct a problem to ensure that TSLOT resets all connections
      on a given call when hang-up occurs.
      (APAR IY67801)

    2.Correct one of the TSLOT exceptions to stop a core dump occuring
      (Defect 35545)

  • Update 4.2.0.68

    APAR IY67558 IY67320 IY67557

    PTF U802159 U802264

    1.Sometimes using wvrtrunk to enable all trunks can result in
      "dead aid" on the the channels. This has been corrected.
      (APAR IY67558)

    2.vm_integrity: scan for duplicate database entries removed for
      single mailbox entry checks. ( option -e ).
      (APAR IY67320)

    3.During a short DBHEALTH outage, if the system parameter
      "System Response during Server Outage" is set to
      "Busy-out all telephony channels", then sometimes on a system with a
      large number of trunks some channels will not automatically
      re-enable. This corrects the problem.
      (APAR IY67557)


Fix level 65

APAR IY66084 IY67175
PTF U802149 U802150 U802151 U802152
  • Update 4.2.0.65

    APAR IY66084 IY67175

    PTF U802149 U802150 U802151 U802152

    1.Script to perform basic db2 runstats against the WVR tables
      and indices.
      (APAR IY66084)

    2.Correct message count decrements to prevent inappropriate
      5200 alarms.
      (APAR IY67175)

    3.Prevent erroneous error message concerning boston.cfg
      from appearing.
      (Defect 35519)

  • Update 4.2.0.60

    APAR IY65586

    PTF U801250

    1.Error message definitions have been updated and corrected
      where required.
      (APAR IY65586)

  • Update 4.2.0.58

    APAR IY65256

    PTF U801247

    1.Fix time slot code to handle 0 sinks (unidirectional TDM
      connections)
      (APAR IY65256)

    2.This fix ensures that members can be deleted from distribution
      lists with IDs greater than 32767.
      (Defect 35479)

    3.This fix allows distribution list IDs up to 65532 to be used
      with state tables.
      (Defect 35477)

  • Update 4.2.0.57

    APAR IY65253

    PTF U801076

    1.DB2 licence daemon (db2licd) stopped on DT_shutdown.
      (APAR IY65253)

  • Update 4.2.0.51

    APAR IY64563

    PTF U800854

    1.This allows a semi-colon ';' to be added to Referal Extension
      when using UpdateProfile.
      (APAR IY64563)

    2.Adds "ls -lRL" listing of DTJ_HOME to collected diagnostics.
      (Defect 35459)

  • Update 4.2.0.50

    APAR IY64223

    PTF U800779

    1.This PTF adds support for new devices required by Fax sub system.
      (APAR IY64223)
      Base sub-system support

  • Update 4.2.0.49

    APAR IY64184

    PTF U800778

    1.This PTF adds support for new devices required by Fax sub system.
      (APAR IY64184)
      Device driver support

  • Update 4.2.0.45

    APAR IY63949

    PTF U800677

    1.This PTF updates message files required for multiple ISDN.
      (APAR IY63949)

  • Update 4.2.0.42

    APAR IY63810

    PTF U800670 U800671

    1.Fixes problem causing occasional voice distortion when adapter
      does an internal TDM resync.
      (APAR IY63810)

    2.When testing fax it was found the TDM user connected slots
      were not being reset to system connected slots when packs
      were disabled.
      The failure would cause outbound CAS calls to fail because
      DTMF keys would not be transmitted.
      This has now been corrected.
      (Defect 35410)


Fix level 40

APAR IY62888
PTF U800501 U800500 U800459 U800458 U800460 U800499
  • Update 4.2.0.40

    APAR IY62888

    PTF U800501 U800500 U800459 U800458 U800460 U800499

    1.A code change has been made to prevent spurious error_id 5200
      from occurring.
      (APAR IY62888)

    2.FIx to allow echo cancellation work on inbound java calls.
      (APAR IY62894)

    3.Fixed incorrect setting of SV573 for SaveVoiceMessage
      (APAR IY62883)

    4.This fix stops DTmon raising 25032 alarms when it is running at very close
      intervals.
      (APAR IY62884)

    5.Fixes Java assert when processing recognition response in VoiceXML2
      when DTMF input is not expected and caller presses DTMF key immediately
      after saying a recognised phrase.
      (APAR IY62918)

    6.Fixed message creation with sent time of 0
      (APAR IY62821)

    7.Fixes a problem with the quality of the G.723.1 VoIP codec on
      the DTEA adapter
      (Defect 34875)

  • Update 4.2.0.30

    APAR IY62658

    PTF U800454

    1.Fix to imrpove extended error handling (EEH) recovery
     (APAR IY62658)

  • Update 4.2.0.29

    APAR IY62619

    PTF U800453

    1.This PTF fixes a problem which could cause a DTXA adapter to
      freeze under extremely unusual circumstances.
      (APAR IY62619)

  • Update 4.2.0.28

    APAR IY61730

    PTF U800261

    1.This PTF fix will make the DTXA and DTTA adapter code more
      tolerant to short system glitches caused by unexpected device
      activity. The error log entry produced as a result of such errors
      will now be logged as a yellow warning '17971', rather than a
      red error '17302'.
      (APAR IY61730)

  • Update 4.2.0.27

    APAR IY61270

    PTF U800259

    1.This fix stops wvrtrunk raising 25032 alarms when it is
      running at very close intervals to monitor the system.
      (APAR IY61270)

  • Update 4.2.0.24

    APAR IY61485

    PTF U800143

    1.This fixes a problem where the WVR Java API and CCXML api's could not
      pass SIP URI's on an out bound make call to the SIP stack.
      (APAR IY61485)

    2.This PTF fixes the path to mount_retry in HAstartDT
      (Defect 35203)

  • Update 4.2.0.22

    APAR IY60950

    PTF U800027

    1.This PTF fixes an error burst generated by the SIP MEDIA
      control process when re-cycling trunks.
      (APAR IY60950)

  • Update 4.2.0.15

    APAR IY59123

    PTF U499535

    1.If 3270 is not installed and the Pack or System configuration
      is open in Change mode then it is not possible to start WVR
      from another telnet session.
      The following error displayed
      'Error: failed to run "RDSET3270 disabled" - RC=1'
      This has now been corrected.
      (APAR IY59123)

    2.This PTF fixes a VOIP/SIP configuration in wvrteleconf
      problem.
      (Defect 35178)

    3.Add partial migration support to DTdatabase
      (Defect 35177)

    4.This PTF fixes TSLOT memory leaks
      (Defect 35157)

    5.This PTF fixes EDL setting in wvrteleconf
      (Defect 35149)

    6.Ship wvrteleconf and wvrsysconf .cat file for en_GB
      (Defect 35080)

    7.This PTF fixes channel group allocation in wvrteleconf
      (Defect 35038)

    8.SIP Adaptor configuration fixed for wvrteleconf
      (Defect 35028)

  • Update 4.2.0.14

    APAR IY58969 IY58960 IY58928

    PTF U498990

    1.In some cases starting the WVR GUI using vaeinit when WVR is
      already running can result in performance problems.
      This is especially noticeable when running Message Center.
      This has been corrected.
      (APAR IY58928)

    2.This fix resolves a problem with the registration of an
      MWI signalling process on a machine that does not have any
      telephony adapters installed.
      (APAR IY58960)

    3.This fixes a problem which can give a core dump from SDIEXEC
      on system shutdown.
      (APAR IY58969)

    4.This causes WVR to try again on voice file open if stale NFS file
      handle returned
      (Defect 35141)

    5.This fixes a problem which can occasionally cause fetching of
      messages from the database to fail due to the message id becoming
      corrupt. This problem will not cause the database to become
      unstable - simply just fail for a single call.
      (Defect 35139)

    6.This changes the error codes from wvrsysconf to be positive.
      (Defect 35084)

    7.Fixes a possible core in wvrsysconf when rd.data is unavailable.
      (Defect 35083)

    8.Fixed DTdatabase -m failure on non-networked machine
      (Defect 34922)

    9.This fixes a maintenance issue with wvrtrunk.
      (Defect 33663)

  • Update 4.2.0.13

    APAR IY58574

    PTF U498798

    1.Fixed setmwi triggers in DT_Patch_Database
      (APAR IY58574)

    2.This fixes a problem in the umount_retry script used on systems
      with HA. The umount command can hang on nfs mounts when the server
      cannot be contacted because the network is down. This enforces a
      timeout so that the system will still failover in this
      state - rather than hanging at the umount command.
      HA Customers should copy the umount_retry script to their own i
      location where other HA scripts are located.
      (Defect 35085)

    3.License information for Unifed Messaging customers.
      (Defect 35063)

  • Update 4.2.0.10

    APAR IY58326

    PTF U498785 U498786

    1.This fix resolves a problem where DTstatus archive files
      are not cleaned up in the $OAM_LOG_PATH directory.
      They can then potentially fill the filesystem and stop WVR
      running. This problem was seen when large numbers of
      errorlog and oamtrace archives were allowed to accumulate in
      the $OAM_LOG_PATH directory.
      (APAR IY58326)

    2.Prior to this fix, the pack config GUI may not have worked
      correctly when adapters were removed, reordered or set to the
      'defined' state. For example when a DTTA or DTXA card which had
      been position between two DTEA cards was physically removed or
      taken out of service by relinquishing ownership with the
      'dt_setowner -x -u1' command, the VoIP adapter pack config of
      the second DTEA did not associate with the correct adapter.
      The IP address, subnet mask and default router values were not
      displayed at all and the labels for these fields were not
      arranged correctly within the dialog box.
      (Defect 34888)

    3.This fixes a problem in pack configuration which could lead
      to incorrectly configured trunks
      (Defect 34889)

    4.This fixes a problem with wvrtrunk attempting to enable
      unconfigured channels.
      (Defect 34867)

    5.DBHEALTH now detects DB file system full condition
      (Defect 32090)

    6.This fixes a problem with core dumping when application objects
      are copied to another object with the same name.
      (Defect 34167)

    7.Fixed various minor wvrteleconf problems.
      (Defect 34941)


3270 Fixes


  • Update 4.2.0.500

    APAR IZ60542

    PTFs U829858

    1.This PTF fixes a problem with 3270 peeker sessions using
      up all the buffers up due to a spining loop.
      This can occur when the 3270 peeker sessions are being
      used on a remote X server, for example Exceed.
      If the remote X server connection drops requests are made
      for window id 0 which causes the peeker code to loop.
      (APAR IZ60542)

  • Update 4.2.0.282

    APAR IY99360

    PTFs U811968


    1.Prevent CTRL3270 core dumping in certain circumstances.
      (APAR IY99360)

  • Update 4.2.0.171

    APAR IY78780

    PTFs U806142

    1.This PTF changes software requirements for dirTalk.3270
      when operating on AIX version 5.3.
      (APAR IY78780)

  • Update 4.2.0.122

    APAR IY72354

    PTFs U803959

    1.The 3270 Script editor GUI could not enter valid values
      into the String and Numeric fields using the Put Field
      Term Definition GUI.
      (APAR IY72354)



ISDN Fixes


  • Update 4.2.0.577

    APAR IV16543

    PTF
    U850414

    1.
    Remove a race condition in ES services used by ISDN. This race
      condition caused error 29106 from es_queue.c
      (APAR IV16543)

  • Update 4.2.0.574

    APAR IV12944

    PTF U849731

    1.Fix prevents ISDN_MONITOR from core dumping if /tmp is cleared.
      (APAR IV12944)


  • Update 4.2.0.524

    APAR IZ77685

    PTF U836469

    1.This fix overcomes a possible 29213 error (ISDN channel state
      machine invalid primitive) when a outbound/inbound call clash
      occurs (glare) on a QSIG ISDN channel. Previously after such
      a clash the error could occur on the first inbound call received
      on the channel.
      (APAR IZ77685)

  • Update 4.2.0.505 to 509

    APAR IZ67224 IZ67386 IZ67412 IZ67432 IZ67435

    PTF U831602 U831603 U831874 U831875 U831876

    1.This fix overcomes possible ISDN errors 29109
      (ISDN ES buffer pool low) and 29615
      (ISDN Layer 1 discarding incoming messages) seen with
      2BCT transfer calls on T1 ISDN DMS100 National.  
      Previously the loss of environment services buffers
      associated with these errors could result in failure to
      handle any new ISDN calls (inbound or outbound) until
      WVR was restarted.  
      (APAR IZ67224   505  ISDN DMS)
      (APAR IZ67386   506  ISDN ATT)
      (APAR IZ67412   507  ISDN Euro)
      (APAR IZ67432   508  ISDN INS1500)
      (APAR IZ67435   509  ISDN com)


  • Update 4.2.0.475

    APAR IZ60261

    PTF U828271



    1.This fix helps overcome repetitive 1201 (Line problem/Glare
      occurred > 20 times) errors seen occasionally during
      QSIG ISDN transfer calls on certain Hicom switches.
      Previously when this error occurred the 1201 error would
      repeat on each and every follow-on outbound call until
      the failing channel was reset at the switch end.
      The fix overcomes the problem by setting the channel
      disabled to prevent further call attempts.
      (APAR IZ60261)

  • Update 4.2.0.464

    APAR IZ52334 IZ53254

    PTF U827375


    1.This fix overcomes a possible failure of T1 ISDN blind transfer
      (seen on DMS National ISDN). Previously the Transfer Call
      action would sometimes return EDGE_OK to the application
      despite the CO switch failing to complete the transfer.
      (APAR IZ52334)

    2.This fix corrects the handling of an outbound ISDN call
      when the switch returns a PROGRESS message with
      CAUSE = #34 (No circuit/channel available). Previously the
      Make Call action would return EDGE_MK_NO_ANSWER rather than
      EDGE_MK_NO_LINES_AVAILABLE.  The fix also corrects a similar
      mishandling of 'user busy'
      (PROGRESS with CAUSE = #17 - User busy) i.e. return of
      EDGE_MK_PHONE_BUSY rather than EDGE_MK_NO_ANSWER.
      (APAR IZ53254)

  • Update 4.2.0.450

    APAR IZ44739

    PTF U824349


    1.This fix overcomes a problem with E1 QSIG ISDN, where the
      optional parameter CLGN (Calling Party Number) is not
      always correctly handled for inbound and outbound calls.
      If byte 3 (octet 3) of the CLGN information element is
      set to a value 0x20 (number type = national, numbering
      plan = unknown) the number is ignored and not presented
      to the application (in the CLGN tag).  Furthermore, if
      an outbound call is attempted with a CLGN byte 3 value
      of 0x20 (tag values CLGN.NUMBER_TYPE = 2,
      CLGN.NUMBER_PLAN = 0) the call should go through to the
      network and not be rejected with a return edge = 6
      (OUTBOUND_LINE_PROBLEM). The fix extends support for
      CLGN byte 3 values of 0x10, 0x20, 0x30, and 0x40
      i.e.
        number types of international, national, network
        specified and subscriber respectively with numbering
        plan unknown.
      (APAR IZ44739)

  • Update 4.2.0.447

    APAR IZ42693

    PTF U824345

    1.This fix overcomes a possible failure of T1 ISDN 2B-channel blind
      transfer.
      Previously the Transfer Call action would sometimes unexpectedly
      return OUTBOUND_LINE_PROBLEM to the application and transfer would
      fail  to complete.
      (APAR IZ42693)

  • Update 4.2.0.442

    APAR IZ37058

    PTF U822816

    1.This fix overcomes a possible CHP core when quiescing
      trunks on a T1 ISDN/DMS National system when transfers
      are active.  Previously errors 1201 (Line Problem) and
      29212 (ISDN call state machine invalid primitive)
      could also occur.
      (IZ37058)

  • Update 4.2.0.431

    APAR IZ33164

    PTF U821503

    1.This fix overcomes a regression, specific to E1 Euro
      ISDN, which was introduced by APAR IZ26091
      (dirTalk.ISDN.Euro-ISDN version 4.2.0.412).
      An outbound call (e.g. trombone transfer) with optional
      CLPN (Calling Party Number) set by the application may
      return OUTBOUND_LINE_PROBLEM despite the
      CLPN being valid.
      (APAR IZ33164)

  • Update 4.2.0.422 to 424

    FIX LEVEL / APAR / PTF : 4.2.0.422 / IZ32663 / U820402

    FIX LEVEL / APAR / PTF : 4.2.0.423 / IZ32664 / U820473

    FIX LEVEL / APAR / PTF : 4.2.0.424 / IZ32705 / U820760


    1.The addition of a Progress Indicator IE for EuroISDN required
      a change for a common ISDN header file and therefore the Layer
      3 executables have been updated.
      (APAR  IZ32663 IZ32664 IZ32705)


  • Update 4.2.0.411 to 412

    FIX LEVEL / APAR / PTF : 4.2.0.411 / IZ26090 / U819346

    FIX LEVEL / APAR / PTF : 4.2.0.412 / IZ26091 / U819347

    1.This change adds support for sending a Progress Indicator
      Information Element (IE) with an outgoing ALERTING message
      for E1 EuroISDN and QSIG trunks. A new Trunk Interface
      Group parameter (Send ISDN Progress Indicator value
      on Alerting) defines the description value to be sent
      (in octet 4 of Progress Indicator IE).
      The default value (of -1) disables sending of
      Progress Indicator.
      Details of this fix are also documented in TechNote
     
    http://www.ibm.com/support/docview.wss?rs=761&uid=swg21313315
      (APAR IZ26090 IZ26091)


  • Update 4.2.0.403 to 406

    FIX LEVEL / APAR / PTF : 4.2.0.403 / IZ24030 / U818967

    FIX LEVEL / APAR / PTF : 4.2.0.404 / IZ24046 / U818968

    FIX LEVEL / APAR / PTF : 4.2.0.405 / IZ24048 / U818969

    FIX LEVEL / APAR / PTF : 4.2.0.406 / IZ24029 / U818970

    1.Tighten requisite for filesets.
      (APAR IZ24030 IZ24046 IZ24048 IZ24029)

  • Update 4.2.0.402

    APAR IZ24148

    PTF U818966

    1.This fix overcomes a failure with some outbound calls
      (transfers) on T1 ISDN DMS100 National.
      If during the outbound call setup the switch returns
      a NOTIFY message with optional IE's (Information Elements)
      then a STATUS was previously returned with a Cause value
      of #96 (Mandatory IE is missing). As a result of this the
      switch would not progress the call though to a
      CONNECTED state.
      (APAR IZ24148)

    2.Tighten requisite for filesets.
      (Defect 36375)



  • Update 4.2.0.370

    APAR IZ21397

    PTF U818267

    1.This fix overcomes a possible 29205 error
      (ISDN signalling process signalling library error)
      during setup of an outbound ISDN call in which a
      PROGRESS message is received.
      (APAR IZ21397)

  • Update 4.2.0.355

    APAR IZ16837

    PTF U816492


    1.Correct calculation so that ISDN starts if
      /var/tmp has greater than 4GB of free space.
      (APAR IZ16837)

  • Update 4.2.0.354

    APAR IZ15405

    PTF U816491

    1,Prevent hangup if a STATUS message with a CAUSE code of #96 is
      received.
      (APAR IZ15405)

  • Update 4.2.0.353

    APAR IZ15553 IZ15755 IZ16048 IZ16070

    PTF U816490

    1.When making an outbound call, if a PROGRESS mesaage
      is received with a CAUSE code of #34
      'No circuit/channel available', then an edge of
      'EDGE_MK_NETWORK_BUSY' will be returned to a State
      Table rather than allowing the action to timeout.
      (APAR IZ15553)

    2.Prevent error 29212 being generated during ISDN Call
      Transfer.
      (APAR IZ15755)

    3.The ISDN call Tag in SV542 will now correctly report the
      PROTOCOL VARIANT if overridden by Multiple ISDN setup.
      (APAR IZ16070)

    4.Correct leak on QSIG MWI which could cause failure after
      a long period of time.
      (APAR IZ16048)

  • Update 4.2.0.344

    APAR IZ12491

    PTF U815935

    1.Add ability to specify the trunk or trunks on which MWI
      is sent using a new parameter 'MWI Trunk' in the
      'ISDN Signalling' parameter group.
      This new parameter allows selection of a single or
      multiple trunks on which MWI requests are to be sent.
      Specify the trunk(s) using a comma delimited list of trunk
      numbers in the range 1 to 16, or enter 0 to retain the
      original operation.

      Refer to the WVR publications to see a description of the change.
      (APAR IZ12491)

     


  • Update 4.2.0.330 - 334

    APAR IZ09288 IZ09317 IZ09324 IZ09326 IZ09329

    PTF U815176 U815177 U815178 U815179 U815180

    IZ09288   U815176  4.2.0.330  dirTalk.ISDN.com fileset
    IZ09317   U815177  4.2.0.331  dirTalk.ISDN.ATT fileset
    IZ09324   U815178  4.2.0.332  dirTalk.ISDN.DMS100 fileset
    IZ09326   U815179  4.2.0.333  dirTalk.ISDN.Euro-ISDN fileset
    IZ09329   U815180  4.2.0.334  dirTalk.ISDN.INS1500 fileset

    1.When "Send RESTART on Channel Enable = Yes" the code did
      not retry if the switch failed to respond to the RESTART
      with an acknowledgement.
      This has now been corrected so that RESTART will be
      retried two more times before timing out.
      (APAR  See above)

  • Update 4.2.0.289

    APAR IZ00020

    PTF U812202

    1.Correct ISDN layer 4 to correctly obey the Presentation
      Restricted attribute of the Calling Number.
      (APAR IZ00020)

  • Update 4.2.0.287

    APAR IY99811

    PTF U812107

    1.Remove unnecessary error reporting during 2 B-Channel
      and RLT Transfer.
      (APAR IY99811)

    2.Correct a problem on ISDN Trunk 16 where it may fail
      to manually enable after being disabled.
      (Defect 36146)

  • Update 4.2.0.280

    APAR IY99346

    PTF U811965


    1.Correct ISDN DMS call transfer code to prevent
      error 29200 with the descriptions "Could not stop
      the facility timer" and also "Did not start the
      FACILITY timer: timer alreary running"
      (APAR IY99346)

    2.Improve ISDN layer error reporting.
      (Defect 36124)

  • Update 4.2.0.264

    APAR IY96220

    PTF U811214

    1.Correct variables and messages used by import check
      routines.
      (APAR IY96220)

  • Update 4.2.0.263

    APAR IY96216

    PTF U811208

    1.Update variables and messages used by import check
      routines.
      (APAR IY96216)

  • Update 4.2.0.262

    APAR IY96154

    PTF U811207

    1.Correct variables and messages used by import check
      routines.
      (APAR IY96154)

  • Update 4.2.0.261

    APAR IY96142

    PTF U811206

    1.Corrects variables and path information used during
      import check routines.
      (APAR IY96142)

  • Update 4.2.0.260

    APAR IY95505

    PTF U811205

    1.Corrected memory leak on QSIG which would cause MWI to
      fail after many thousand MWI messages had been sent.
      (APAR IY95505)

    2.Add extra Trace entries for internal ISDN routines.
      (Defect 36072)

    3.Correct Trace entry for internal ISDN routine.
      (Defect 36071)

  • Update 4.2.0.247

    APAR IY93040

    PTF U810661

    1.Add Single Step Transfer custom server for ISDN.
       (APAR IY93040)

  • Update 4.2.0.244

    APAR IY92625

    PTF U810596

    1.Modifications to QSIG handling of STATUS messages to prevent
      call being dropped when forwarded.
      (APAR IY92625)

  • Update 4.2.0.237

    APAR IY91556

    PTF U810396

    1.Change to 2 B-Channel Transfer so that a Proceeding IE will
      no longer initiate a transfer in conformance with Bellcore
      GR-2865-CORE.
      (APAR IY91556)

  • Update 4.2.0.221

    APAR IY87181

    PTF U808661

    1.Add Text strings to some ISDN internal error messages.
      (APAR IY87181)

  • Update 4.2.0.220

    APAR IY85983

    PTF U808660


    1.Updated Nortel DMS 100 and DMS 250 protocols to support
      REDIRN Call Tags on Inbound and Outbound calls.
      Also on 2B-Channel Transfer if a "Redirecting Number" IE
      exists it will be automatically copied to the outbound call,
      and an Original Called Party number will no longer be
      generated.
     (APAR IY85983)

  • Update 4.2.0.206

    APAR IY81142

    PTF U807391

    1.Allow greater than 16 digits in Calling and Called Party Numbers
      as part of an outbound SETUP message.
      (APAR IY81142)

  • Update 4.2.0.202

    APAR IY81678

    PTF U806946

    1.Add support for Virtual Adapter ( adapterless DTNA) solution.
      For ISDN fileset.
      (APAR IY81678)

  • Update 4.2.0.194

    APAR IY80909

    PTF U806888

    1.Correct allowable values of PROGRESS INDICATOR and also
      allow PROGRESS before ALERTING on outbound calls.
      (APAR IY80909)

  • Update 4.2.0.143

    APAR IY75430

    PTF U804592

    1.Allow Redirecting Number octet 3 of the SETUP message to
      be FF with octets 3a and 3b not present.
      This is to allow SV542 to be populated with the
      Redirecting Number.
      (APAR IY75430)

  • Update 4.2.0.142

    APAR IY75375

    PTF U804589

    1.Allow Redirecting Number octet 3 of the SETUP message to
      be FF with octets 3a and 3b not present on ISDN versions T1
      National 2 and TR41449/41459.
      This is to allow SV542 to be populated with the
      Redirecting Number.
      (APAR IY75375)

  • Update 4.2.0.132

    APAR IY73948

    PTF U804240

    1.This fix completes changes required for DISPLAY.TYPES
      (APAR IY73948)

  • Update 4.2.0.131

    APAR IY73946

    PTF U804239

    1.Updated due to changes in ISDN.com fileset
      (APAR IY73946)

  • Update 4.2.0.130

    APAR IY73945

    PTF U804238

    1.Updated due to changes in ISDN.com fileset
      (APAR IY73945)

  • Update 4.2.0.129

    APAR IY73911

    PTF U804237

    1.Updated due to changes in ISDN.com fileset
      (APAR IY73911)

  • Update 4.2.0.128

    APAR IY73903

    PTF U804235

    1.Further enhancements to signalling ISDN National
      NA007-NA0017.
      (APAR IY73903)

  • Update 4.2.0.112

    APAR IY72461

    PTF U803654

    1.This fix prevents erroneous status messages being sent
      from WVR in response to receipt of a progress IE within a
      message when configured as QSIG.
      This fix also has added the NFE part of the MWI ASN.1 rose PDU.
      The NFE has been defined  as  sourceEntity = endPINX and
      destinationEntity = endPINX only.
      (APAR IY72461)

  • Update 4.2.0.111

    APAR IY72457

    PTF U803653

    1.A new ISDN tag has been added to provide sending and
      receiving of the DISPLAY IE tag, plus support for tag
      attributes DISPLAY.INF and DISPLAY.TYPES.
      Call transfers type RLT and Two B Channel Transfer will
      now automatically foreward a DISPLAY IE to the transferee
      if it was present on the original incoming call
      Note: Currently only the switch type NT DMS100 with Line
      Signalling ISDN National NA007-NA0017 configuration supports
      the DISPLAY IE.
      (APAR IY72457)

  • Update 4.2.0.110

    APAR IY72456

    PTF U803652

    1.This fix adds support for ISDN.com to allow fixes in
      fix level 4.2.0.111 and 4.2.0.112 to operate correctly.
      (APAR IY72456)

  • Update 4.2.0.79

    APAR IY69878

    PTF U803311

    1.This problem occured with WVR configured as QSIG.
      When an SL_STATION_SET_MWI_REQ was sent to activate a
      Message waiting indicator it could potentially result in
      unstable behavoiur in ISDN call control.
      This has been corrected.
      (APAR IY69878)

    2.ISDNDL3_QSIG and ISDNDL4 have been enhanced to allow qsig
      to receive raw setup, facility and connect messages at the
      FE interface. This provides QSIG apps with asn.1 pdu's etc
      allowing rose features to be developed.
      This feature is only available using QSIG.
      (Defect 35561)

  • Update 4.2.0.78

    APAR IY69817

    PTF U803310

    1.This problem occured with WVR configured as QSIG.
      When an SL_STATION_SET_MWI_REQ was sent to activate a
      Message waiting indicator it could potentially result in
      unstable behavoiur in ISDN call control.
      This has been corrected.
      (APAR IY69817)

    2.ISDNDL3_QSIG and ISDNDL4 have been enhanced to allow qsig
      to receive raw setup, facility and connect messages at the
      FE interface. This provides QSIG apps with asn.1 pdu's etc
      allowing rose features to be developed.
      This feature is only available using QSIG.
      (Defect 35561)

  • Update 4.2.0.74

    APAR IY68830

    PTF U802554

    1.Corrects problem where HSF Transfer for New Zealand would
      not work for concurrent calls.
      (APAR IY68830)

  • Update 4.2.0.67

    APAR IY66646

    PTF U802158

    1.This code update fixes an es_buffer leak caused when invoking
      a FH type ISDN call transfer.
      This feature is currently used in New Zealand.
      (APAR IY66646)

  • Update 4.2.0.55

    APAR IY64700

    PTF U800858

    1.WVR was sending RESTARTS enbloc to bring channels in to
      service during trunk enablement. This is not the correct
      procedure and channel restarts should be sent sequentially,
      ie one at a time channel by channel.
      This defects fixes this problem. ISDN INS1500 version
      (APAR IY64700)

  • Update 4.2.0.54

    APAR IY64663

    PTF U800857

    1.WVR was sending RESTARTS enbloc to bring channels in to
      service during trunk enablement. This is not the correct
      procedure and channel restarts should be sent sequentially,
      ie one at a time channel by channel.
      This defects fixes this problem. ISDN Euro version
      (APAR IY64663)

  • Update 4.2.0.53

    APAR IY64651

    PTF U800856

    1.WVR was sending RESTARTS enbloc to bring channels in to
      service during trunk enablement. This is not the correct
      procedure and channel restarts should be sent sequentially,
      ie one at a time channel by channel.
      This defects fixes this problem. ISDN DMS version
      (APAR IY64651)

  • Update 4.2.0.52

    APAR IY64617

    PTF U800855

    1.WVR was sending RESTARTS enbloc to bring channels in to
      service during trunk enablement. This is not the correct
      procedure and channel restarts should be sent sequentially,
      ie one at a time channel by channel.
      This defects fixes this problem. ISDN ATT version
      (APAR IY64617)

  • Update 4.2.0.44

    APAR IY63903

    PTF U800676

    1.Tech Doc Note for Multiple ISDN support for WVR AIX.
      12 October 2004

      The following is an explanation and some useful information
      about how to use the isdn.ini.sample file which is provided
      with the dirTalk.ISDN.com file set to allow the ISDN system
      configuration to be overridden. It is primarily made available
      to allow ISDN configurations of WVR AIX to allow multiple Q931
      protocols to be run on the same P-series machine.
      For example the  TR41459 module could be configured on some
      packs and DMSNAT can now be configured on other packs.

      1.  The isdn.ini.sample is installed when the dirTalk.ISDN.com
          is installed or upgraded.
      2.  The isdn.ini.sample is installed in to the following
          directory /usr/lpp/dirTalk/db/sys_dir/isdn
      3.  The feature is available when an isdn.ini file exists in
          this directory; this can be created by copying
          isdn.ini.sample to isdn.ini and changing permissions
          to writeable.
      4.  Changes can be made to any or all of the supported
          parameters on a PACK basis. These parameters do not override
          the description of how WVR supports ISDN as defined in the
          General Information Planning Book.
      5.  Alternative ISDN modules can be configured by setting the
          SignalProcessNumber parameter to the required signal process
          number. The signal process numbers are defined in the
          slcommon.h file which contains the definition of the
          SL_PROT_TYPE structure. The slcommom.h file can be
          found in /usr/lpp/dirTalk/include.
      6.  Changes take affect when a trunk is enabled.
      7.  Packs that have been updated generate a white notification
          alarm number 29618 which states that
          "The trunk ISDN configuration as been updated" and indicates
          the Trunk number.
      8.  There are no other console changes. The Custom Sever Manager
          will continue to indicate the originally configured ISDN
          custom sever.
      Note: It is important to set the Run status of any overridden
            ISDN custom servers that may also be installed to the Stop
            state and the set their IPL status to be INSTALLED by
            selecting Auto-Start Off.  The primary ISDN custom sever
            will control both the original primary ISDN modules and
            the overridden ISDN modules, and must be the only ISDN
            custom server indicating Run status = WAITING and
            IPL status = AUTOEXEC.
      9.  T309Enabled is usually enabled by the system configuration
          should not normally be changed.
      10. SendRestartMsgOnChannelEnable parameter can be
          enabled/disabled. If this is disabled  the switch will
          provide the channel restart messages rather than WVR.
      11. BChanServiceMessagesEnabled can be enabled/disabled to
          control the sending of B channel service messages, which
          are used to enable the bearer channels.
      12. DChanServiceMessagesEnabled can be enabled/disabled to
          control the sending of D channel service messages which are
          used to provide D channel backup.
      13. MaintenanceProtDisc is used in conjunction with D channel
          and B channel service messages and can be set to 3 or 43.
      14. The numbering type set in the ISDN system configuration
          can be overridden on a pack basis.
           NumberingType
           a.  0 = unknown
           b.  1 = international
           c.  2 = national
           d.  3 = network-specific
           e.  4 = subscriber
           f.  5 = abbreviated
      15. The numbering plan set in the ISDN system configuration
          can be overridden on a pack basis.
           NumberingPlan
           a.  0 = unknown
           b.  1 = ISDN
           c.  2 = national
           d.  9 = private
      16. The signal process selected in pack configuration can be
          overridden by setting the ISDNSignalProcess.Number.
          The valid numbers are
            a.  SL_PROC_EUROISDN      = 24
                ( Preferred for E1 ISDN )
            a.  SL_PROC_5ESS_5E8      = 25
            b.  SL_PROC_5ESS_5E9      = 26
            c.  SL_PROC_DMS100_BCS34  = 27
            d.  SL_PROC_TR41449       = 28
                ( Preferred also includes TR41459 4ESS )
            e.  SL_PROC_T1_NATIONAL   = 29
                ( Preferred for Lucent 5ESS switches )
            f.  SL_PROC_DMS_NATIONAL  = 30
                ( Preferred for Nortel DMS 100 switches )
            g.  SL_PROC_DMS_250       = 32
                ( Preferred for Nortel DMS250 switches )
            h.  SL_PROC_ISDN_INS      = 35
                ( Preferred for Japan INS 1500 )
            i.  SL_PROC_ISDN_QSIG     = 37
                ( Preferred for E1 QSIG )

      17. The ISDN Q.931 signal modules that are started by WVR
          when a trunk is enabled can be seen by typing the following
          command
             ps -eaf | grep ISDNDL3
          For example  ISDNDL3_EUROISDN 13
      18. There is only one ISDN Q.931 signal module per signalling
          group, which means for example that an NFAS group of eight
          trunks will only require one signalling module.


    ; File : isdn.ini.sample
    ;
    ; Licensed Materials - Property of IBM 5765-001 (C)
    ;          Copyright IBM Corp.
    ; 1990, 1997. All rights reserved.  US Government Users
    ;          Restricted
    ; Rights - Use, duplication or disclosure restricted by
    ;          GSA ADP Schedule
    ; Contract with IBM Corp.
    ;
    ; Change History:
    ;
    ;
    ; Purpose :
    ;   This file contains a limited number of isdn configuration
    ;   parameters that can be used to override the original
    ;   configuration set up from the WVR pack and system configuration.
    ;   Its main purpose is to allow different types of isdn q931
    ;   code to co-reside and execute on the same WVR.
    ;   This can be useful for attaching a WVR to different switch
    ;   manufacturers such as Nortel and Lucent.
    ;   For example this file will allow the ISDNDL3_T1NAT signalling
    ;   process to be configured at the time as ISDNDL3_DMSNAT running.
    ;
    ;
    ; Syntax :
    ;   The file must reside in a directory called isdn located
    ;   in $SYS_DIR.
    ;   The actual directory is /usr/lpp/dirTalk/db/sys_dir/isdn.
    ;   The name of the file must be isdn.ini
    ;   Comments within the isdn.ini file start with ;
    ;   This file can be used as a template, copy it to a new file
    ;   called isdn.ini,
    ;   For Example: copy the file by typing
    ;   cp isdn.ini.sample  isdn.ini
    ;   Then change the file to be read/write by typing
    ;   chmod +w isdn.ini
    ;
    ;   Note: T1 and E1 protocols cannot be mixed.
    ;         Different configurations cannot be applied within an
    ;         NFAS group, all packs in that group must use the same
    ;         signal process.
    ;         Each NFAS group can be configured differently, for
    ;         example one group could be T1NAT another group could
    ;         be DMSNAT.
    ;         When overriding the SignalProcssNumber for an NFAS group
    ;         it is only necessary to specify an entry for the primary
    ;         signalling PACK.
    ;
    ;
    ; Tags:
    ;    The tags supported within the isdn.ini file must reside in
    ;    the context of a [PACK_xx] entry. There can be up to
    ;    16 [PACK_xx] entries present in the file starting from
    ;    [PACK_1] through to [PACK_16].
    ;
    ;    Not all tags need be present, values not present in isdn.ini
    ;    will be taken from the WVR System Configuration.
    ;
    ;    The example below shows all supported tag values.
    ;    Remove the ; comment to use an example like this.
    ;
    ;[PACK_1]
    ;   T309Enabled                   = y  ; This tag value can y or n
    ;   SendRestartMsgOnChannelEnable = n  ; This tag value can y or n
    ;   BChanServiceMessagesEnabled   = y  ; This tag value can y or n
    ;   DChanServiceMessagesEnabled   = n  ; This tag value can y or n
    ;   MaintenanceProtDisc           = 3  ; tag value only be 3 or 43
    ;   NumberingPlan                 = 7  ; value only between 0 of 15
    ;   NumberingType                 = 3  ; value only between 0 of 15
    ;   SignalProcessNumber           = 29 ; tag value can only be set
    ;                                      ; to one of the ISDN signal
    ;                                      ; process numbers
    ;                                      ; which are defined in
    ;                                      ; slcommon.h
    ;
    ;
    ; Further information about system configuration can be found in
    ; the WVR AIX "Configuring the System" book. Information about
    ; specific Signal Process Numbers can be found in the SL_PROC_TYPE
    ; structure which is defined in the slcommon.h file located in
    ; $VAE/include or /usr/lpp/dirTalk/include directory.
    ;
    ;
    ;
    ;
    ;
    ; A simple example for overriding the signal process.
    ;
    ;[PACK_5]
    ;   SignalProcessNumber = 29  ; This tag will set pack 5 to
    ;                               execute the Lucent  T1 National
    ;                               isdn variant. The override does
    ;                               not appear on the Custom Server
    ;                               Manager window which will continue
    ;                               to show the original default
    ;                               signal process which must be left
    ;                               running. All other ISDN Custom Server
    ;                               signal processes that appear in the
    ;                               Custom Server Manager should be set
    ;                               to INSTALLED by selecting  the
    ;                               "Auto-Start Off" option.



    Example 1
    The following example sets PACK 1 (trunk 1) to run the signal
    process number 29, which is the Lucent variant of T1 National, and
    is typically required for a 5ESS switch. This will run the
    ISDNDL3_T1NAT module for pack1, or the primary signalling pack of
    an NFAS group which has been configure as pack 1.

    [PACK_1]
       SignalProcessNumber           = 29

    Example 2
    The following example sets PACK 2 (trunk 2) to run the signal
    process number 30, which is the Nortel variant of T1 National, and
    is typically required for a DMS100 switch. This will run the
    ISDNDL3_DMSNAT module for pack2. The Maintenance Protocol
    Discriminator is set to 3 for support of B channel and D channel
    Service Messages.


    [PACK_2]
      MaintenanceProtDisc           = 3
      SignalProcessNumber           = 30




    Example 3
    The following example sets PACK 3 and PACK 16 to run the signal
    process number 32, which is the Nortel variant of T1 National, and
    is typically required for a DMS250 switch. This will run the
    ISDNDL3_DMS250 module for pack 3 and pack 16. The Maintenance
    Protocol Discriminator is set to 43 for support of B channel Service
    Messages. The SendRestartMsgOnChannelEnable parameter is set to n
    which relies on the switch to provide restart messages rather
    than WVR. D Channel service message support required has been
    disabled.


    [PACK_3]
      SendRestartMsgOnChannelEnable = n
      DChanServiceMessagesEnabled   = n
      MaintenanceProtDisc           = 43
      SignalProcessNumber           = 32

    [PACK_16]
      SendRestartMsgOnChannelEnable = n
      DChanServiceMessagesEnabled   = n
      MaintenanceProtDisc           = 43
      SignalProcessNumber           = 32



      (APAR IY63903)

    2.This feature provides call Tansfer using Euro ISDN based on
      the hook flash feature. This function was requested
      specifically by New Zealand.
      (Defect 35389)


  • Update 4.2.0.43

    APAR IY63891

    PTF U800672

    1.See details in Update 4.2.0.44
      (APAR IY63891)

  • Update 4.2.0.25

    APAR IY61573

    PTF U800144

    1.This ISDN ptf fixes an ISDN call transfer problem in the 4.2 version
      of WVR.
      (APAR IY61573)

  • Update 4.2.0.19

    APAR IY60499

    PTF U499203

    1.Updated valid combinations of "Screening Indicator" and
      "Presentation Indicator" for Original Calling Number and
      Calling Party Number.
      (APAR IY60499)


BrooktroutFax Fixes

  • Update 4.2.0.550

    APAR
    IZ85737

    PTF
    U839630

    1.
    Improved initial fax channel allocation during Brooktrout fax
      startup.
       (APAR IZ85737)

     2.Corrected path information for import check.
      (Defect 36079)

    APAR
    IZ85979

    PTF
    U839632

     1.Remove excess debug information from the TR1034 Brooktrout
      Fax boston device driver
      (Defect 35941)

  • Update 4.2.0.208

    APAR IY83693

    PTF U807394

    1.This PTF wil stop infinite loop and core in logging code.
      (APAR IY83693)

  • Update 4.2.0.153

    APAR IY77050

    PTF U805630

    1.Enhance error handling at the end of a fax call.
      This change will stop a partially received FAX from being
      deleted if there is a problem during FAX transmission.

      The following return codes have been implemented
      0 -    As before, the FAX is completely successful
      100 -  The far end hung up during the end of fax negotiation.
             Valid FAX present
      101 -  Another error occured during the end of fax negotiation.
             Valid FAX present
      -490 - As before, FAX failed
      (APAR IY77050)

  • Update 4.2.0.115

    APAR IY72463

    PTF U803795

    1.This fix ensures that the Brooktrout Fax device retains
      the correct permissions after a system reboot.
      (APAR IY72463)

  • Update 4.2.0.114

    APAR IY70584

    PTF U803766

    1.Changes to the BTFAX_1000 custom server to ensure it uses
      the correct configuration file
      (APAR IY70584)

    2.Changes to the logging process to allow users to move the
      current BrooktroutFax.log file without stopping further logging.
      A new log file will be created to continue recording log data.
      (Defect 35671)

  • Update 4.2.0.48

    APAR IY64060

    PTF U800737

    1.This PTF adds support for the new Brooktrout Fax TR1034 Fax
      board. Information concerning configuration and use can be
      found in  "Fax using Brooktrout" manual.
      (APAR IY64060)
      Device driver

  • Update 4.2.0.47

    APAR IY64041

    PTF U800681

    1.This PTF adds support for the new Brooktrout Fax TR1034 Fax
      board. Information concerning configuration and use can be
      found in  "Fax using Brooktrout" manual.
      (APAR IY64041)
      Base sub-system

  • Update 4.2.0.12

    APAR IY47312

    PTF U495891

    1.This PTF corrects the requisite software required by the
      dirTalk.BrooktroutFax fileset.
      (APAR IY58381)




SP Fixes

There no SP Fix Updates on WVR for AIX, V4.2.





GEOTEL Fixes



Fix Level 4.2.0.588 (PTF U854196)
Fix release date: 14 Sep 2012
Status: Current
APAR Description
IV27694 Fixed a GeoTel custom server problem concerning trace. This occurs if the custom server fails to trace after reading a message from the message queue. The custom server will incorrectly report that the message queue has failed.
Internal Defect fix
  • Fixed a problem where the GeoTel custom server incorrectly shutdown during a message read. The message read actually works however the trace returned an error. This is misinterpreted as a message read error. Note: Importing the GeoTel custom server will overwrite the $CUR_DIR/service.def in ca/GeoTel_dir. This should be backed up first.



  • Update 4.2.0.337

    APAR IZ09273 IZ06415

    PTF U815451

    1.Preserve the tag values in the GeoTel custom server to
      ensure ECC vars do not disappear or move.
      (APAR IZ09723)

    2.Changed the Improve the socket read code to check earlier
      for ECONNRESET
      (APAR IZ06415)

  • Update 4.2.0.291

    APAR IZ00740

    PTF U812851

    1.Catch all cases of the GeoTel ICM socket connection
      dropping and reconnect the socket. Note, back up the
      service.def file before importing the GeoTel.imp
      (APAR IZ00740)

  • Update 4.2.0.288

    APAR IY99834

    PTF U812108

    1.Allow CHPs greater than 480 to use the GeoTel custom server.
      (APAR IY99834)

  • Update 4.2.0.258

    APAR IY95504

    PTF U811204

    1.Improved the handling of trailing whitespace in parameter
      definition files.
      (APAR IY95504)

  • Update 4.2.0.232

    APAR IY90691

    PTF U809889

    1.Fix a problem with ROUTE_SELECT, ROUTE_END and ROUTE_END_EVENT
      messages, which ware incorrectly interpreting returned information.
      Importing GeoTel.imp will remove all files in the
      /usr/lpp/dirTalk/db/current_dir/ca/GeoTel_dir and reset the flags
      passed to the custom server. If these have been changed then this
      information will need to be backed up before importing the
      GeoTel.imp file.
      (APAR IY90691)

  • Update 4.2.0.218

    APAR IY86095

    PTF U808518

    1.This defect resolves an issue whereby ECC data could
      get lost or overwritten when under load.
      (APAR IY86095)

    2.Added files to allow import check during WVR start up.
      (Defect 35954)

    3.Improve the socket read functions to handle fragmented packets.
      (Defect 35979)

    4.Make the socket read code not block if there is no
      message to read.
      (Defect 35988)

  • Update 4.2.0.191

    APAR IY81034

    PTF U806882

    1.This defect resolves an issue whereby if the custom server
      is running high load utilising ECC Variables then there
      is a possibility of a buffer over-run occuring, causing
      the custom server to terminate unexpectedly.
      (APAR IY81034)

  • Update 4.2.0.167

    APAR IY75755

    PTF U805954

    1.This fix corrects a problem where the delivered message
      sent to the Cisco ICM Peripheral Gateway used an incorrect
      logical trunk group number if the -c command line
      parameter is used and the Channel Group ID of the trunk
      group is other than 01.
      (APAR IY75755)

    2.This feature adds support for up to 30 ECC array indices
      spread across the existing five ECC arrays as well as allowing
      multiple instances of the custom server to be run.
      The support for up to 30 ECC array indices is only available
      through the state table interface, the Java interface retains
      the current limit of 5.
      The existing array support was flawed in that if multiple
      arrays were utilised then the data would be stored in the
      incorrect locations.
      This PTF modifies the behaviour to place the data in the
      return parameters in the order in which it is received as
      opposed to the custom server attempting to place it in the
      order it believed to be correct. The existing custom server
      functions remain the same in allowing only up to the first
      five array entries to be received. In order to work around
      this limit three new functions has been added to the state
      table custom server interface.

      Retrieve_Index_Value

      The Request_Index_Value is issued by the state table
      application in order to retrieve the value of a specific array
      index which has been sent by the ICM. This command must be
      issued by the application after the variables have been
      received from the ICM in a message which contains the ECC
      variables and before any other messages are picked up by the
      state table application. For example, this could be issued
      directly after a Run_Script_Request has been issued.

      This function can be called repeatedly to retrieve multiple
      index values.

      If the value of the array index cannot be found then a null
      string will be returned.

      If the DialogueID cannot be found then
      E_INVALID_DIALOGUEID will be returned.

      SendData

      DialogueID (number)
      Obtained using the Create_DialogueID function.

      ECCVarArrayTag (number)
      The numeric tag value by which this variable is identified.

      ECCVarArrayIndex (number)
      The numeric array index identifier, the value of which
      you wish to retrieve.

      ReceiveData

      ECCVarArrayString(string[210])
      The call related data stored in the specified tag and index.

      New_Call_Extended

      The New_Call_Extended function provides a way from the state
      table interface to send up to 30 array values.
      The required parameters are the same as for New_Call (and
      the resultant message to ICM is a New_Call) but with the
      ability to set more ECC Array values.

      SendData
      DialogueID (number)
              Obtained using the Create_DialogueID function.

      TrunkGroupID (number)
              The ID of the trunk group on which the call arrived.
              Set to SV177 (Current Channel Group) if the -c is
              specified as one of the custom server parameters.
              Otherwise set to SV166 (Physical Card Number).
              When using SV177 as the TrunkGroupID, use the Assign
              Data state table action to assign the value of SV177
              to a numeric variable. This variable should then be
              used as the value that is passed as TrunkGroupID.
              TrunkNumber (number) The number of the trunk on which
              the call arrived. Set to SV165 (Logical Channel Number)
              if the -c is specified as one of the custom server
              parameters. Otherwise set to SV167
              (Physical Channel Number).
      ServiceID (number)
              The ID of the service to which this call is assigned.

      DialedNumber (string[32])
              The number that is used to determine the ICM call type.

      ANI (string[40])(optional)
              The Calling line ID of the caller.

      UserToUserInfo (string[131])(optional)
              The ISDN user-to-user information element.

      CalledNumber (string[32])(optional)
              The complete called number from the network.

      DNIS (string[32])(optional)
              The DNIS that is provided with the call.

      CallVariable1 (string[40])(optional)
              Additional VRU information that is to be used
              when the ICM script is run.

      CallVariable... (string[40])(optional)
              Additional VRU information that is to be used
              when the ICM script is run.

      CallVariable10 (string[40])(optional)
              Additional VRU information that is to be used
              when the ICM script is run.

      ECCVarValueTag1 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarValueString1(string[210])(optional)
              Call-related data.

      ECCVarValueTag... (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarValueString... (string[210])(optional)
              Call-related data.

      ECCVarValueTag5 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarValueString5(string[210])(optional)
              Call-related data.

      ECCVarArrayTag1 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarArrayIndex1 (number)(optional)
              A numeric array index identifier.

      ECCVarArrayString1(string[210])(optional)
              Call-related data.

      ECCVarArrayTag... (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarArrayIndex... (number)(optional)
              A numeric array index identifier.

      ECCVarArrayString... (string[210])(optional)
              Call-related data.

      ECCVarArrayTag30 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarArrayIndex30 (number)(optional)
              A numeric array index identifier.

      ECCVarArrayString30 (string[210])(optional)
              Call-related data.

      ReceiveData
      Status (number)
              A value from the list of status codes that
              describes the result of this request.

      Run_Script_Result_Extended

      The Run_Script_Result_Extended function provides a way
      from the state table interface to send up to 30 array values.
      The required parameters are the same as for Run_Script_Request
      (and the resultant message to ICM is a Run_Script_Request) but
      with the ability to set more ECC Array values.

      SendData
      DialogueID (number)
              Obtained using the Create_DialogueID function.

      InvokeID (number)
              Set to the InvokeID returned by Run_Script_Request.

      ResultCode (number)
              Set to true (1) if no errors were found actually
              running the script. Set to false (0) if an error
              was found.

      CallerEnteredDigits (string[40])
              Digits that the caller enters.

      NewTransaction (number)
              Set to true (1) if the VRU PIM should write a
              Call Termination record into the database
              immediately after processing this message.

      CallVariable1 (string[40])(optional)
              Additional information that is related to the call.

      CallVariable... (string[40])(optional)
              Additional information that is related to the call.

      CallVariable10 (string[40])(optional)
              Additional information that is related to the call.

      ECCVarValueTag1 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarValueString1(string[210])(optional)
              Call-related data.

      ECCVarValueTag... (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarValueString... (string[210])(optional)
              Call-related data.

      ECCVarValueTag5 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarValueString5(string[210])(optional)
              Call-related data.

      ECCVarArrayTag1 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarArrayIndex1 (number)(optional)
              A numeric array index identifier.

      ECCVarArrayString1 (string[210])(optional)
              Call-related data.

      ECCVarArrayTag... (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarArrayIndex... (number)(optional)
              A numeric array index identifier.

      ECCVarArrayString... (string[210])(optional)
              Call-related data.

      ECCVarArrayTag30 (number)(optional)
              The numeric tag value by which this variable is
              identified.

      ECCVarArrayIndex30 (number)(optional)
              A numeric array index identifier.

      ECCVarArrayString30 (string[210])(optional)
              Call-related data

      Using multiple instances of the Cisco ICM custom server

      The capability of running multiple instances of the custom
      server has been added. In order to utilise this new capability
      two new custom server parameters have been added:

      -n<number of instances>
      The number of instances of the Cisco ICM custom server which
      you wish to run. See the section "Running multiple instance
      of the Cisco ICM custom server" for more information.

      -g<parameter definition file>
      The fully qualified name of the parameter definition which
      you wish to use as the configuration parameters for the custom
      server. See the section "Running multiple instance of the
      Cisco ICM custom server" for more information.

       In some scenarios customers may wish to run multiple instances
      of the Cisco ICM custom server on the same WVR system.
      In order to do this the system should be started with
      only the -n and -g parameters as described above.
      The parameter definition file then contains all of the
      attributes required for the different custom server instances.
      The format of this file is similar to the attributes which you
      specify on the command line, however the instance number must
      also be specified for each parameter.
      For example, to specify the debug level for an instance the
      file would list -d<instance number>lt;debug level>

      An example definition file is below:

      -d11
      -d20
      -d31
      -f1/home/dirTalk/current_dir/ca/GeoTel_dir/services1.def
      -f2/home/dirTalk/current_dir/ca/GeoTel_dir/services2.def
      -f3/home/dirTalk/current_dir/ca/GeoTel_dir/services3.def
      -B11
      -B22
      -B33
      -K1
      -K2
      -K3
      -U1
      -U2
      -U3
      -V1
      -V2
      -V3
      -W1
      -W2
      -W3
      -X1
      -X2
      -X3
      -Y1
      -Y2
      -Y3
      -Z1
      -Z2
      -Z3
      (Feature 35807)

  • Update 4.2.0.135

    APAR IY73954

    PTF U804259

    1.Fix a GeoTel crash when 480 channels are disabled at
      the same time. Note installing this PTF will replace
      the service.def file.
      (APAR IY73954)

    2.A new parameter has been added to the custom server.

      -e <seconds>
      Indicates that trunk group status messages should be
      sent every <seconds> seconds. The time interval must
      be in the range 1-600 seconds, default value is 60 seconds.
      Applying this flag modifies the behaviour of the trunk
      group status message such that trunks are considered out
      of service if they are busy as well as out of service
      (blocked or unavailable). In addition it also allows the
      user to modify the frequency at which this check is made.
      This parameter should be used in environments where trunk
      availability data is critical to the performance of the
      platform and it is not possible to achieve the same
      results using data on the Cisco ICM platform.

      IT IS RECOMMENDED THAT DEBUG LEVEL IS SET TO 0 (-d 0) ON
      PRODUCTION SYSTEMS DUE TO INCREASED LOG SIZE AND
      PERFORMANCE IMPACT.
      (Feature 35572)

    3.The GeoTel custom server is now certified as functioning
      fully with Cisco ICM version 6.
      (Feature 35572)

  • Update 4.2.0.116

    APAR IY72521

    PTF U803796

    1.The GeoTel custom server has been modified such that during
      failover of a Peripheral Gateway, state tables will now
      receive the correct status code.
      (APAR IY72521)

  • Update 4.2.0.26

    APAR IY61713 IY61714 IY61716 IY61717

    PTF U800163

    1.This PTF fixes core dump from GeoTel custom server when it runs
      in Java mode. Sometimes the Java subsystem was releasing a Dialogue
      ID after the phone call had already been hung up.
      This situation is now handled correctly.
      (APAR IY61713)

    2.Updates to the GeoTel custom server to enhance performance
      (APAR IY61716)

    3.Modifies the handling of the TCP/IP socket from Java to the
      custom server so that if the Java client is recycled the custom
      server automaticaly re-establishes the connection.
      (APAR IY61717)

    4.This fix prevents previous ECC Vars from persisting if they
      are not overwritten. ECC Vars are now properly reset if they are
      not explicitly used.
      (APAR IY61714)

  • Update 4.2.0.16

    APAR IY59538

    PTF U499718

    1.Correct handling of ECC Array Variables.
      (APAR IY59538)


ADSI Fixes



There no ADSI Fix Updates on WVR for AIX, V4.2.


TDD Fixes



There no TDD Fix Updates on WVR for AIX, V4.2.



DVT Fixes



There no TDD Fix Updates on WVR for AIX, V4.2.



SS7_D7 Fixes

  • Update 4.2.0.553

    APAR
    IZ89192 

    PTF
    U839821

    1.
    This fix overcomes a possible SS7 30013 error (Invalid Data Item /
      Attempt to access Message Register when not loaded) with an outbound
      call attempt when 16 Channel Groups are configured for use (e.g. 1
      Channel Group for each of 16 T1/E1 SS7 voice trunks).  
      (APAR IZ89192)


  • Update 4.2.0.550

    APAR IZ85776

    PTF U839631

    1.Improve error condition handling.
      (APAR IZ85776)


  • Update 4.2.0.502

    APAR IZ63867

    PTF U829863

    1.This fix provides support for AIX 64-bit kernel working
      of the device driver (artic8260) for the SS7 signalling
      card (SS8/NewNet quad T1/E1 HAX50PCGEN).
      The fix includes the D7 1.3.1.19 update package for the
      D7 1.3.1.0 base install package. Also corrected in the
      update is a possible system crash associated with the
      D7 etmod device driver.
      (APAR IZ63867)

  • Update 4.2.0.436

    APAR IZ21900

    PTF U821509


    1.This fix corrects a problem sometimes seen when
      re-introducing a WVR client into a SS7 cluster.
      A D7 MAJOR error would sometimes occur (dsmd MAJOR Delaying
      dsmd_svc_mtc_syncsegdata_req due to
      EDESTBLKD : Destination blocked [211]) and the whole SS7
      cluster would crash preventing further calls.

      The fix (replacement of D7 1.3.1.17 with version 1.3.1.18)
      also corrects some minor D7 related problems
       e.g. D7 AccessStatus utility can be invoked from more
      than 2 machines in the SS7 cluster.
      (APAR IZ21900)

  • Update 4.2.0.366

    APAR IZ18163

    PTF U817183


    1.This fix overcomes a possible SS7_D7 custom server core
      dump (Error12305 with core file in
      /var/adm/ras/dirTalk/core.SS7_D7) when SS7 calls are
      ended by the voice application
      (APAR IZ18163)

  • Update 4.2.0.284

    APAR IY97404 IY94586

    PTF U811970

    1.This fix corrects the recovery from lost SS7 Server
      signalling links.

      Previously when at least 1 signalling link recovered after
      all SS7 ISUP signalling links were lost in a SS7 cluster,
      the trunk circuits of a WVR client would recover (become
      unblocked, as viewed through 'ss7view -circuit') but this
      was not reflected through to the System Monitor GUI
      (which remained blocked). As a result, all inbound calls
      after this recovery would be rejected (with SS7 error;
      "sl_send_indication failed" in ../oamlog/SS7/Errorsxx file).
      The fix corrects a regression introduced by the fix for
      APAR IY92573 (SS7 PTF U810594 fileset
      dirTalk.SS7_D7.Enablement version 4.2.0.242).
      (APAR IY97404)

    2.This fix prevents the reporting of errors 30028
      (DTXA/DTTA Loopback) and 30105 (SS7 Continuity test failed)
      if an SS7 Continuity (COT) test call on a previous circuit
      is abandoned by the network.  Previously this pair of
      errors would occur (in errorlog file) if this type of
      test call was released (abandoned) by the network rather
      than sending a COT success or COT failure as conclusion
      of the test.
      (APAR IY94586)

  • Update 4.2.0.278

    APAR IY85051

    PTF U811643

    1.This fix address a startup problem seen on some
      SS7 E1 WVR client systems.

      Where a connecting switch sends CGU
      (Circuit Group Unblock) ISUP messages as part of the
      SS7_D7 custom server start up sequence and when trunks
      are enabled, Some circuits fail to become available
      (unblocked). Outbound calls are then prevented and
      generate the error;

      30114 SS7 Error while in SEIZE state

      The fix (i.e. replacing D7 1.3.1.15 with version 1.3.1.17)
      corrects this problem by ensuring the correct handling of
      the CGU ISUP message from the switch.
      (APAR IY85051)

       You will need to remove any existing .toc file before
       trying to upgrade to latest fix level. Please perform
       the following command as user  root
       rm /usr/lpp/dirTalk/sw/ss7/update/.toc
       If the .toc file did not exist, it is not a problem.

  • Update 4.2.0.248

    APAR IY93215

    PTF U810899

    1.This fix allows the optional ISUP/IAM parameters
      Jurisdiction Information (0xC4) and Party Information
      (0xFC) for an inbound SS7 T1 call to be presented in the
      system variable SV542 (as Tags JINFO and PINFO).
      This then allows an application to determine call
      charging and redirecting party information.

      For an SS7 T1 inbound call application, the
      Jurisdiction Information is presented as the value of
      Tag JINFO. For Party Information the Tag value is
      zero but with string attributes PINFO.CALLING_NAME
      and PINFO.REDIRECTING_NAME.

      For an SS7 T1 outbound call, this fix also allows
      an application to set in SV541 the Tags JINFO and
      PINFO for presentation to the remote switch in
      an IAM (Initial Address Message).

      Support for both new optional parameters is enabled
      in configuration file
      /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/
      AnyMachine/Service.cfg

     (APAR IY93215)

  • Update 4.2.0.242

    APAR IY92573 IY85973 IY89932 IY89598 IY91384 IY90726 IY90782

    PTF U808886

    1.This fix corrects an inconsistency sometimes seen when viewing
      an SS7 circuit (CIC) within the SS7 utility 'ss7view -circuit'
      verses the System Monitor/Channels GUI. A ss7view CIC state
      of 'Far End Service state = Blk' is not always reflected in the
      System Monitor which should show the channel as 'Bl' (Blocked)
      coloured BLACK and not 'Id' (Idle) coloured BLUE. Previously
      relying on the System Monitor could suggest a circuit was available
      to handle calls when actually blocked at the network.
      (APAR IY92573)

    2.This fix overcomes a SS7_D7 custom server core dump or
      'segment violation' error (in SS7_D7 Errorsxx log file) on
      a WVR client machine when a SS7 Server is shutdown in a
      large (at least 60 trunk) SS7 cluster.
      (APAR IY90782)

    3.This fix allows for the configuring of a T1 SS7 cluster
      so that the SS7 signalling link(s) run at 56k bps
      (rather than the default of 64k bps). The SS7itty configuration
      utility supports this through user selection of either the
      Bell Canada or Verizon/MCI SS7 Configuration Pack
      (rather than the Standard Configuration Pack) when configuring
      for SS7 T1.
      (APAR IY85973)

    4.This fix helps ensure after a system reboot that
      the SS7_D7 custom server automatically start when WVR is
      started (assuming AUTOEXEC is set in Custom Server Manager).
      Previously an auto restart of SS7_D7 after reboot could result
      in failure to start and the error;
      A second parent start - now stopped
         in the SS7/Errorsxx file.
      (APAR IY91384)

    5.This fix allows an inbound SS7 T1 or E1 Continuity
      (COT) test call on a DTTA type card to proceed as expected without
      immediately terminating with error 30028 (Invalid card).
      Previously COT tests would only proceed on DTXA cards.
      (APAR IY89598)

    6.This fix corrects the failure of the SS7_D7 custom server to
      acknowledge a CGB (Circuit Group Block) or CGU (Circuit Group
      Unblock)  message sent from a SS7 switch when the 'Circuit group
      supervision  message type' is set to 'hardware oriented' rather than
      'maintenance oriented'. Previously this would result in a D7 error
      of $890117 (ISUP: Unexpected primitive [mod=10 prim=0x90a
      Astate=0x0] in  AccessAlarms error log.  The effect of the error was
      to prevent  trunks from becoming available at startup and could
      result in the  switch reporting 'C7SF' signalling failures.
      (APAR IY90726)

    7.This fix corrects the handling of partial trunk SS7 Circuit
      Group Blocks (CGBs) and Circuit Group Unblocks (CGUs) received from
      the switch (sometimes sent by SS7 switches at startup). Previously
      the  error 30114 (SS7 Error while in FAREND_BLOCK/UNBLOCK state)
      could occur  if the CGB or CGU was directed at only part of a trunk
      i.e. not starting at the first circuit in the trunk and not for
      the whole of the trunk (24 circuits T1, 30 circuits E1)
      (APAR IY89932)

  • Update 4.2.0.224

    APAR IY85984 IY81336 IY83502 IY83751 IY85331 IY85721 IY86603 IY85975 IY85972

    PTF U808886

    1.This fix corrects the handling of a Circuit Group
      Reset (GRS) ISUP message received from a SS7 network for
      a SS7 T1 or E1 trunk.
      Previously a GRS did not always unblock all circuits
      (CIC's) in the trunk and in turn this could prevent an
      outbound call being made on each circuit.
      (APAR IY85984)

    2.This fix overcomes an input field restriction with
      the SS7 configuration utility SS7itty. When adding a
      Route Set, the input field 'SS7 Bearer Trunks associated
      with this Route Set' was previously restricted to
      16 characters. This has been extended to 256 characters
      and therefore allows for more complex Route Set
      definitions.
      (APAR IY86603)

    3.This fix corrects the failure to handle an SS7 inbound
      call which includes the optional ISUP parameters 0xfc
      (PTY_INFO_PARM) and 0xfe (NT proprietary
      supplementary end-to-end information request).
      Previously such calls were not presented to an application
      and therefore could not be answered.
      (APAR IY85975)

    4.This fix provides automatic handling of SS7 voice trunk
      circuits (CICs) when a loss of signal occurs
      e.g. a voice trunk is disconnected when the trunk is in
      service.
      Previously, although a loss of signal alarm was
      reported (SL_ALARM_SL on E1, SL_ALARM_LOS on T1)
      the trunk CICs would remain locally unblocked.
      An inbound call from the switch would then get 'dead air'
      (no voice circuit).
      The fix also prevents CICs being enabled if a loss of signal
      condition is present at startup.
      Additionally, this fix provides automatic handling of SS7
      voice trunk circuits when a loss of signal condition is
      recovered i.e. when SL_ALARM_CLEAR occurs.
      If the voice trunk is enabled and loss of signal has
      previously been detected the CICs will automatically
      become locally unblocked (available for calls) when
      the alarm clears e.g. when voice trunk is reconnected.
      (APAR IY85972)

    5.This fix allows existing SS7 E1/T1 voice calls to continue
      (both parties can still hear voice) after all SS7 signalling
      links have been disconnected from the SS7 cluster.
      Previously existing voice calls would be dropped when the
      last SS7 signalling link was disconnected.
      As before, new calls are still prevented until a SS7
      signalling link is re-established.
      (APAR IY85721)

    6.This fix corrects the handling of inbound T1 SS7 calls
      when 'Continuity check performed on a previous circuit'
      is included in the call setup message (IAM).
      Previously the call was immediately released on receipt
      of 'Continuity check successful' instead of proceeding
      in the normal way to an answered state.
      (APAR IY85331)

    7.This fix corrects the failure to reject a SS7 inbound
      call when received without a USI parameter (T1 only) or
      without a CDPN parameter (E1 and T1) present in the IAM.
      Previously such calls were accepted and could result in a core
      dump of the SS7_D7 custom server.
      (APAR IY83751)

    8.This fix overcomes a problem where shutdown of a SS7
      server can cause the other SS7 ISUP server to shutdown
      and in turn prevent handling of subsequent SS7 calls by
      the SS7 cluster.  The problem has been seen to occur only
      when the first 7 characters of the WVR client host name
      are not unique in a cluster with at least 2 WVR clients.
      (APAR IY83502)

    9.This fix overcomes the error 30032 (Internal component
      failure) when a SS7 outbound call is made with the
      optional Tag GENERICADDR set in system variable
      SV541.  Prior to the fix an outbound call with this
      parameter set would not proceed.
      (APAR IY81336)

  • Update 4.2.0.193

    APAR IY77307 IY80720

    PTF U806886

    1.This fix overcomes the problem of changing on a per call
      basis the ISUP/USI (User Service Information) parameter
      bytes in an outbound SS7 call. Previously an alteration
      using the PUT_TAG/PUT_ATTRIBUTE (e.g. USI.OCTET_2) method
      would result in an error 30033 (Attribute USI.OCTET_2 has
      invalid number list format).
      Also, using the alternative ISUPPARM Tag method was
      ineffective i.e. default values (as defined in ISUPParms.cfg)
      were still used instead of the cloned set values.
      (APAR IY77307)

    2.This fix allows, if enabled in Service.cfg, the optional
      ISUP/IAM parameter Charge Number (0xEB) for an inbound SS7
      T1 call to be presented in system variable SV542
      (as Tag value CHARGEN). This then allows an application to
      know or control which party is charged for the call.
      An additional fix is presenting in system variable SV542
      the correct value in Tag REDIRN (Redirecting Number) for
      an inbound SS7 call (both T1 and E1).
      Previously Redirection Number (0x0C) was presented instead
      of Redirecting Number (0x0B). This prevented an inbound
      application from correctly determining from where a redirected
      call had come from.
      (APAR IY80720)

  • Update 4.2.0.182

    APAR IY77646 IY76175 IY78300 IY78816 IY79085 IY79191 IY74954

    PTF U806299

    1.This fix addresses a server restart problem after stopping
      a working SS7 server in a dual server SS7 cluster.
      Stopping then restarting D7 could result in the error;

      upmd MAJOR spm_bind() failure: System call timed out [119]

      in D7 Mlog error log (/usr/ss8/d7/access/RUN/mlog directory).
      Previously this error would prevent new calls from being
      handled.
      The fix (i.e. replacing D7 1.3.1.11 with version 1.3.1.15)
      also corrects the failure to configure D7 with an SS8 adapter
      on a Power5 series machine e.g. a 520.
      (APAR IY79191 IY74954)

    2.This fix overcomes a problem found with SS7_MAINT when
      stopping the SS7_D7 custom server whilst StayAlive=Disabled
      set in the Service.cfg configuration file.
      Previously the shell script would terminate unexpectedly
      and leave the SS7_D7 custom server still running.
      Using SS7_MAINT to restart the SS7_D7 custom server would
      result in the error CA_ALREADY_STARTED.

      The Level 3 PD utility ss7Problem has been enhanced to
      collect SS7itty Route_Set data (if present). Also, if SS7itty
      has not been run on the machine (and directory
      /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/data is empty)
      no error is reported.
      (APAR IY79085)

    3.This fix corrects a problem found with SS7 configuration when
      using SS7itty to configure a SS7 Server. For a configuration
      with separate STP's (Signal Transfer Point) and SSP's
      (Service Switching Point) the generated mml-ss7 configuration
      file (used by the D7 software stack) previously lacked an
      ADD-ROUTE statement needed for each named RouteSet. Although
      this does not result in an error when loading the SS7 mml
      in SS7_MAINT, the voice switching paths are not defined and
      therefore cannot be used in calls.
      (APAR IY78816)

    4.This fix corrects the problem of seeing errors 30008
      (Unhandled State Table, state FAREND_INIT stimulus SS7_BLO)
      on a WVR client when another WVR client with enabled trunks
      in the SS7 cluster is shutdown.
      (APAR IY78304)

    5.This fix corrects the value in System Variable SV23 (Call Type)
      when a redirected (forwarded) inbound call includes the
      Tag REDINFO (Redirection Information). Previously SV23 was
      inconsistent with the value in REDINFO.REASON
      e.g.  REDINFO.REASON = User busy,
      SV23 = Direct dialed to WebSphere Voice Response.
      (APAR IY77648)

    6.This fix corrects an auto trunk startup problem seen on
      some installations. Also, the possible error 30029
      (D7 SS7 Timer problem - Timer Expired for First CGBA timer)
      is avoided.
      (APAR IY76175)

  • Update 4.2.0.161

    APAR IY77166 IY77384 IY76762 IY77600 IY77475

    PTF U805745

    1.This fix corrects the behaviour of the SS7 MakeCall action
      when the network immediately returns 'User Busy'
      or 'Network Busy'.
      Previously 'No Answer' was returned for both these cases.
      (APAR IY77166)

    2.This fix prevents the SS7 error 30008 (Unhandled State Table:
      State ANSW and Stimulus SL_CALL_ANSWER_REQ) when an application
      performs a redundant AnswerCall while an outbound call is
      already connected.
      (APAR IY77600)

    3.This fix overcomes the failure to present to an application
      the REDINFO tag in SV542 for a SS7 inbound call which is received
      from the network containing the optional ISUP IAM parameter
      REDI (Redirection Information).
      (APAR IY77475)

    4.This fix prevents an error (30017 - Configuration Translation
      failure)  when enabling an ISDN trunk in a mixed ISDN and SS7 trunk
      configuration when the SS7_D7 custom server is active.
      (APAR IY77384)

    5.Modifications to the SS7 AutoStart script to ensure that
      the correct environment is set for the WVR user
      before starting SS7.
      (APAR IY76762)

      NOTE file SS7_D7.imp must be imported after installing
      this fix for the fix to be activated.
      After installing the fix, copy the default version of
      Service.cfg (in
       /usr/lpp/dirTalk/sw/ss7/defcfg/SS7_D7_cfg/AnyMachine)
      to the active directory
      (/usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/AnyMachine).
      Repeat any network specific changes made to Service.cfg
      at the time of initial installation.

      NOTE 2
      Perform the following
      as user dtuser or equivalent user

      cp -p /usr/lpp/dirTalk/sw/ss7/ss7itty/*.dat
       $CUR_DIR/ca/SS7_D7_cfg/AnyMachine/.

      Restart the SS7_D7 and the D7WVRErrorReport custom servers.

  • Update 4.2.0.151

    APAR IY76152

    PTF U805238

    1.This fix overcomes the restriction of not being able
      to include bytes 3, 4, and 5 in the USI
      (User Service Information) parameter of an outbound
      SS7 IAM message (outbound call).
      Despite being enabled in file ISUPParms.cfg only
      bytes 1 and 2 of the USI parameter could be sent
      previously.  On certain SS7 switches, the lack of USI
      byte 3 can result in an outbound call being rejected.
      NOTE file SS7_D7.imp must be imported after installing
      this fix for the fix to be activated.
      After installing the fix, copy the default version of
      ISUPParms.cfg (in
       /usr/lpp/dirTalk/sw/ss7/defcfg/SS7_D7_cfg/AnyMachine)
      to the active directory
      (/usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/AnyMachine).
      Repeat any network specific changes made to ISUPParms.cfg
      at the time of initial installation.
      Restart the SS7_D7 custom server.
      (APAR IY76152)

  • Update 4.2.0.118

    APAR IY72689

    PTF U803951

    1.This fix addresses the failure to match inbound SS7 calls
      with the desired application. Some switches
        e.g. Ericcson MD110 include an 'F' (ST) termination digit in
        the Called Number parameter for a call setup (IAM) message.
      The fix strips the 'F' digit from the Called Number instead of
      converting it to an '?' character which then prevents an
      Application Profile match.
      This fix also added the configuration option of appending
      an 'F' (ST) termination digit to the Called Number parameter of
      an outbound SS7 call. Some switches,
        e.g. Ericcson MD110 will reject a call to a number that is not
        terminated with ST in the Called Number parameter.
      Documentation for this new option is included in the
      ISUPParms.cfg user configuration file.
      (APAR IY72687 IY70997)

    2.If after installing this PTF you are informed when start WVR that
      d7.xxx filesets are down level, you should shut down WVR and perform
      the following
        Logon as root
        cd /usr/lpp/dirTalk/sw/ss7/update
           This directory will contain all d7.xxx updates required.
        smitty update_all
      (Defect 35704)

    3.Tests have been added to ensure that when using SS7 the correct
      version of filesets are loaded and the post installation activation
      has been performed.
      WVR will start regardless but will issue warnings in DTstatus.out
      (Defect 35593)

    4.This fix overcomes the failure of the SS7 utility SS7_MAINT to
      stop the SS7_D7 custom server. Previously the SS7_D7 custom server
      would be stopped but would then be automatically restarted
      after a period of 30 seconds.
      (Defect 35521)

    5.The ISUPParm.cfg has the following corrections:-
      1: The SS7 REL message will generate the correct IE format
         for Cause Ind. (see "REL:Cause").
      2: The CVR IE parameters are now configurable.

      N.B. This file will be installed into
        /usr/lpp/dirTalk/sw/ss7/defcfg/SS7_D7_cfg/AnyMachine directory,
        if this is not part of a fresh installation then copy this file to
      the following directory
        /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/AnyMachine/ISUPPparms
      be aware that customized modification may have been performed to the
      original destination file and those changes may need to be
      transferred  to its replacement.
      (Defect 35488)

    6.This fix addresses several E1 ITU Q.784 Compatibility test failures
      when attached to an E1 SS7 switch and using the SS7_D7 custom server.

      In relation to the failing ITU tests, the following problems are
      now corrected in the following ITU test numbers:-

      1.3.1.1; Range/Status parameter in CGUA
       (Circuit Group Unblock Acknowledge) message is now correctly
       set (Status bits were previously set to zero)

      1.4.1; Avoids white notify alarm 30005 (Unhandled SS7 message)

      1.4.5; Avoids getting stuck in 'call state = TRLC' which then i
      cannot be removed by a RSC (Reset) message

      1.5.2; Avoids yellow alarm 30203 (D7 major alert/ISUP
      Unexpected primitive 0x905)

      2.3.1; Avoids white notify alarm 30005 (Unhandled SS7
      message/unknown message for ISUP_ALERT)

      2.3.3; Avoids white notify alarm 30005 (Unhandled SS7
      message/unknown message for ISUP_SETUP)

      5.2.4; Support is now included for SUS (Suspend) message
      when received from the network during a call)

      5.2.9; Avoids a burst of 11 yellow alarms of 30008
      (Unhandled State Table)

      6.3.1; Avoids yellow alarm 30008 (Unhandled State Table/No
      state entry found to match state SACM and stimulus SS7_ERROR)


      In addition to the above corrections, several spelling
      errors have been corrected in SS7 specific System Monitor
      error messages.
      (Defect 35473)

    7.This fix overcomes the failure of the SS7 utility SS7_MAINT
      to delete a SS7 trace file
      (/usr/lpp/dirTalk/db/current_dir/oamlog/SS7/SS7-Trace) when using
      either the H/A or H/T housekeeping options.
      (Defect 35451)

    8.This fix addresses a server fail over problem found in dual
      server SS7 cluster configurations. Stopping then restarting D7 on
      one of the SS7 servers could result in failure to recover and D7
      alarm errors on the remaining machines. The fix
      (i.e. replacing D7 1.3.1.7 with 1.3.1.11) also overcomes a D7
      startup  problem found on some combinations of AIX and security
      APAR fixes e.g. AIX 5.2 + Maintenance Level 3 with APAR IY64355.
      (Defect 35434)

    9.This fix corrects an error seen when configuring a SS7
      server at the point of loading the D7 SS7 mml configuration
      (SS7_MAINT options C and S).  Previously the error;

        RTSET MO instance does not exist

      was being reported in the configuration log file;

     /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/log/mml.log

      corresponding with the ADD-ROUTE statement in the
      configuration script file;

     /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/log/mml.mtp.script.
      (Defect 35706)

  • Update 4.2.0.66

    APAR IY67279

    PTF U802154

    1.When starting the SS7_D7 customer server an information error
      (30015 Configuration Error Detected ), which may not have
      occurred previously should no longer appear in the errorlog.
      (APAR IY67279)

    2.This fix addresses several problems when attached to an SS7
      switch and using the SS7_D7 custom server;

      If the attached SS7 switch issues a 'Circuit Group Block' or
      'Circuit Group Unblock' request then only the specified circuits
      rather than all of the circuits within the trunk will be blocked
      or unblocked.
      (Defect 35314)

  • Update 4.2.0.59

    APAR IY65548

    PTF U801249

    1.SS7itty Configurator now support the configuration of
      RouteSet for STPs.
      (APAR IY65548)

    2.The SS7 Message CVR is now supported.
      (Defect 35469)

    3.Voice bearer traffic loopback can not be initiated from
      the ss7view program.
      (Defect 35468)

    4.SS7itty configurator now supports the HAX44PCGEN card.
      (Defect 35452)

    5.The SS7itty configurator now support different type of SS7
      adaptor on the same machine.
      (Defect 35435)

    6.The SS7 support WVR Alarm message have been improved.
      (Defect 35398)

  • Update 4.2.0.46

    APAR IY63951

    PTF U800680

      This PTF provides support for E1 signalling with SS7.
      Other defects have also been corrected.

    1.Corrects the fault in E1 mode when outbound calls failed with
      no lines available when a number were available.
      (APAR IY63951)

    2.The fault where by SS7_MAINT in option F/2 incorrectly declared
      the ISUP process was down has been corretly
      (Defect 35243)

    3.SS7_MAINT on handle cases where the root password has been
      given incorrectly has been corrected.
      (Defect 35286)

    4.The report of available remove D7 database files on D7 start up
      has been corrected.
      (Defect 35287)

    5.The incorrect detection of SSI system in SSI has been corrected.
      Custom server imports will no longer occur on WVR connected to
      SSI systems.
      (Defect 35303)

    6.The help text for SS7itty under the RouteSet menu has been
      corrected.
      (Defect 35310)

    7.A problem when an SS7 Server failed in a 2 server configuration
      has been corrected. Previously ISUP trunk would be allocated
      to the wrong WVRs.
      (Defect 35313)

    8.The incorrect extension bit in the Release message has been
      corrected. Previously the bit indicate there was more when
      there was not.
      (Defect 35319)

    9.SS7_MAINT now handles multiple Distriubted7 and allows for
      selection.
      (Defect 35326)

    10.When COT (Continuity Test) are now performed the relevant
      voice bearer will have loop back asserted.
      Previous this would report failure.
      (Defect 35332)

    11.On rare condition the SS7itty would fail with a memory
      violation has been corrected.
      (Defect 35350)

    12.The situation on outbound calls where the network is not
      responding, but D7 is reporting timeout. The problem where
      circuit become invisibility allocate has been corrected.
      (Defect 35387)

    13.SS7_MAINT under housekeep menu option can now delete
      SS7-Trace files
      (Defect 35391)

    14.SS7_MAINT can now process i-Fix files.
      (Defect 35393)

    15.General typos and correction sto the SS7itty F1 help text
      have been performed.
      (Defect 35397)

    16.General typos and corrections to the WVR alarm message for
      SS7 have been performed.
      (Defect 35398)

    17.The incorrect reference to Line in the SS7itty help text was
      corrected.
      (Defect 35411)

    18.SS7itty now detects duplication in usage of the Trunks when
      generating.
      (Defect 35413)

    19.SS7itty now detects duplication of Point Code with RouteSets
      and LinkSets
      (Defect 35414)

    20.D7 no longer rejects the old style PQ cards with a 75ohm interface.
      (Defect 35418)

    21.SS7_MAINT will now compare Enablement release with active D7
      release and report incompatibilities.
      (Defect 35430)

    22.SS7_MAINT can now locate the oam log directory in a SS7 Server
      configuration.
      (Defect 35431)

    23.The internal readme has been updated
      (Defect 35433)



SpeechClient Fixes


Fix Level 4.2.0.595 (PTF U861068 )
Fix release date: 20 Sep 2013
Status: Current
APAR Description
IV47993 Corrected a potential NullPointerException when using MRCP recognition, which starts with the following stack trace:
com.ibm.telephony.directtalk.mrcp.MRCPReco.sendSetParams
   at com.ibm.telephony.directtalk.mrcp.MRCPReco.vxml2StopReco(2960)
   at com.ibm.wvr.vxml2.VXML2SpeechSupport.stopReco(457)
   at com.ibm.wvr.vxml2.VXML2TurnCoordImpl.doField(1281)
   at com.ibm.wvr.vxml2.VXML2TurnCoordImpl.doTurn(294)


Fix Level 4.2.0.592 (PTF U858449 )
Fix release date: 11 Mar 2013
Status: Superseded
APAR Description
IV37340 Fixed issue with MRCP zip packaging introduced in PTF Level 589. Some files are not included that results in a failure to install the MRCP custom server on a clean install of WebSphere Voice Response V4.2.3.


Fix Level 4.2.0.589 (PTF U856720 )
Fix release date: 29 Nov 2012
Status: Superseded
APAR Description
IV32742 Moved some excess MRCP tracing to trace level 9. This reduces the extra unwanted trace at level 2, allowing better problem diagnosis.


Fix Level 4.2.0.581 (PTF U851999 )
Fix release date: 11 Jun 2012
Status: Superseded
APAR Description
IV21358 Fixed an internal error that was caused when MRCP servers do not respond within timeout window. This error would cause an OutOfMemory Exception in the VRBE error logs.


Fix Level 4.2.0.573 (PTF U848097 )
Fix release date: 12 Dec 2012
Status: Superseded
APAR Description
IV12571 Fixed to ensure that all attributes required by a Nuance server are included in a TTS <speak> request.
IV12573 Fixed a timing related defect that could result in a "com.ibm.telephony.directtalk.PlugInException: (102) INVALID_STATE:MRCPCSLink request error" being reported in the VRBE logs.
IV12580 Fixed a potential leak of filedescriptors when using the VXML2 recordutterance property with a Nuance speech server.
Internal Defect Fixes
  • Ensure logging of Speech related connection problems at startup.
  • Fixed internal system monitor functionality.
  • Move some CPU intensive tracing from trace level 8 to trace level 9.


  • Update 4.2.0.557

    APAR IZ96532

    PTF U842073

    1.Fixed an issue where VXML2 hotword recognition would not work if a
      Nuance speech server was used.  The RECOGNIZE request would fail
      with a 403 completion code indicating an unsupported parameter.
      (APAR IZ96532)

    2.Fixed an issue with MRCP not honouring the negotiated RTSP port on
      SETUP  messages, which would instead stream to the default port.
      (Defect 37063)

    3.Fixed an issue where the following error would appear under heavy
      call load:
         Unhandled exception occurred during MRCP message receive.
         Details: java.lang.NullPointerException at
         com.ibm.telephony.directtalk.mrcp.ReceiverThread.run(Receiveri
            Thread.java:197)
      (Defect 7500)

  • Update 4.2.0.551

    APAR IZ86864

    PTF U839805

    1.Increase amount of voice data buffered by the device driver to allow
     for CPU glitches to be handled better by MRCP. With a smaller buffer
     a CPU glitch can cause the voice recognition to stop.
     (APAR IZ86864)

  • Update 4.2.0.550

    APAR
    IZ85224

    PTF
    U839635

    1.There is a minor race condition in the MRCP custom server that can
     occur during stopping TTS. If the MRCP custom server is stopping due
     to a DTMF then it carries on processing incoming voice from the TTS
     engine but doesn't stream it to the line. If during this stop a Speak
     complete comes back from the TTS engine the custom server is told to
     immediately stop. The custom server ignores this due to stopping
     because of the DTMF. Unfortunately this causes the TTS to never
     actually stop. A problem occurs when the next TTS is started as this
     fails to be setup correctly complaining that the custom server is
     already streaming.
     (APAR IZ85224)


  • Update 4.2.0.529

    APAR IZ80913 IZ84682

    PTF U837320

    1.Fixed a problem with the MRCP custom server hanging at startup,
        potentially with 100% CPU.
        (APAR IZ84682)

    2.Fixed an issue that can cause a MRCP PluginException
        (completion-cause 006) if a caller hung up just after a recognition
        attempt was started.
        (APAR IZ80913)

  • Update 4.2.0.526

    APAR IZ80094

    PTF U836784

    1.The code fixes the confidence-threshold, sensitivity
       threshold and speedVSaccuracy setting in WVR. With
       the fix, if you define a decimal fraction for these 3
       properties in a voicexml application, WVR will
       convert it to a integer value more accurately.
       (APAR IZ80094)


  • Update 4.2.0.522

    APAR IZ78453 IZ78489

    PTF U836467

    1.Fixed a problem whereby a no-input event will be reported the a VXML
      application as a no-match. The problem only occurs when using Nuance
      as the speech server.
      (APAR IZ78453)

    2.Fixed the handling of RTSP 454 "Session not found" responses when
      attempting recognition or TTS.  Prior to the fix, the application
      would terminate if such a response was received. After installing the
      fix, the code will correctly try to re-establish a session to the
      speech server.
      (APAR IZ78489)


  • Update 4.2.0.511

    APAR IZ63384 IZ64798 IZ6579

    PTF U832491


    1.Corrected a potential problem when setting up a connection to an MRCP
      server if the response message uses uppercase characters for the
      audio format section.
      (APAR IZ63384)

    2.Corrected a problem that can cause the system to report an "MRCP
      Plugin not initialised" message in the wvrtrace files.
      (APAR IZ65796)

    3.Improved the MRCP plugin import code so that the custom server will
      start regardless of the ulimit value set on the machine.
      (APAR IZ64798)
  • Update 4.2.0.503

    APAR IZ63087 IZ63872

    PTF U829864



    1.Fix a potential timing window in the MRCP distributor thread.
      When the problem occurs the MRCP custom server will stop
      delivering packets to WVS. This causes the 006 error return
      from WVS (no audio streamed). The sleep time in the MRCP
      can be on the order of hours, so all reco will fail for
      every channel during this time. The timing window can only
      occur if act of reading the time between two neighbouring
      lines of code is greater than 100ms. Normally this would
      happen if the CPU were heavy loaded and the custom server
      swapped out for some reason.
      (APAR IZ63087)

    2.Fix a timing window when stopping reco/tts whilst the system
      is very busy. If the state table times out whilst waiting for
      the stop and closes the MRCP custom server link then when the
      custom server finally responds it results in an exception and
      the custom server stopping.
      (APAR IZ63872)

  • Update 4.2.0.472

    APAR IZ59740

    PTF U828060


    1.Fixed a potential BufferUnderflowException in the MRCP plugin
      that could occur when using the recordutterance VXML property.
      (APAR IZ59740)

    2.Fix a potential null pointer exception which can occur as a
      MRCP CSLink message is responded to whilst the MRCP plugin
      is checking the validity of the message.
      (Defect 7342)

  • Update 4.2.0.468

    APAR IZ55504 IZ55522

    PTF U827379


    1.If the TTS being played contains no audio (break tag) and
      the TTS engine is Nuance the engine won't stream any audio.
      This causes the DDOEP to become upset due to no data being
      present for it to write out. The DDOEP needs to be force
      cleaned up, however this can not happen if there are no
      other channels being used.
      So the code now always force cleans up any DDOEP's irrelevant
      of whether there are other calls present.
      (APAR IZ55504)

    2.If the call hangs up just as a start of speech occurs and the
      reco thread is attempting to stop the TTS thread an error is
      generated. Treat this error as a hangup rather than an error.
      (APAR IZ55522)

    3.Propagate the hang up occurring during start of speech into
      the following reco attempt. Otherwise the VXML browser may
      not correctly detect hang up.
      (Defect 7324)

    4.Fix a race condition between MRCP responses clashing with the
      MRCP request being written. This can occur when the system
      "pauses" and java halts for a few seconds.  The write/timeout
      code clashes with the response handling code.
      (Defect 7319)

  • Update 4.2.0.467

    APAR IZ53932

    PTF U827378



    1.Perform a VXML 2.1 speech recognition using WVS 6.1
      (reproducable on Linux version) with recordutternance
      property set to true. Fetch timeouts may incorrectly
      occur if the packet buffer is 100% utilised
      (APAR IZ53932)

  • Update 4.2.0.462

    APAR IZ52549

    PTF U825881



    1.Corrected a code defect that could result in a
      "PlugInException (102) Set-params failed" error message
       being reported.
      (APAR IZ52549)

    2.Corrected the code logic to prevent the spurious logging
      of the following messages:

      WVS is configured for pcma, but the telephony network is pcmu.
         To improve performace configure WVS for pcmu.

      and

      WVS is configured for pcmu, but the telephony network is pcma.
         To improve performace configure WVS for pcma.
      (Defect 7262)

  • Update 4.2.0.453

    APAR IZ44983

    PTF U824384


    1.Improve force clean up code for TTS prompts which start
      and stop before any audio is streamed.
      The original force clean code had a race condition which
      can cause the MRCP custom server to crash.
      (APAR IZ44983)

  • Update 4.2.0.438

    APAR IZ36550

    PTF U822395


    1.Modified the behaviour of TTS enabled VXML applications
      so that they honour the bargein section of the VXML2
      specification correctly.
      (APAR IZ36550)

  • Update 4.2.0.435

    APAR IZ35027

    PTF U821508


    1.This PTF fixes a problem with the MRCP custom server when
      stopping streaming on a TTS prompt which is for an
      unconfigured language.
      (APAR IZ35027)

  • Update 4.2.0.416

    APAR IZ24155

    PTF U819377


    1.Modified MRCP plugin code to prevent the following error:
        Event: error.internal, Error: PlugInException:
        LINK_NOT_CONNECTED:MRCPCSLink.checkStatus Link
        not connected
      (APAR IZ24155)

    2.This PTF corrects a problem with CSEQs not matching due to
      multiple requests. This happens when a teardown is sent due to
      a timeout on a previous request. The teardown causes the
      previous request to get a response.
      (APAR IZ27918)

    3.Stop the MRCP custom server from allowing multiple endpoint
      connections.
      (APAR IZ27919)

  • Update 4.2.0.401

    APAR IZ23710

    PTF U818800


    1.Tighten checks on connected speech technologies.
      (APAR IZ23710)

  • Update 4.2.0.371

    APAR IZ22317

    PTF U818268


    1.Corrected a NullPointerException that can occur in
      the MRCP plugin code if a RECOGNITION-COMPLETE message
      is received at the same time as a caller HUP.
      (APAR IZ22317)

  • Update 4.2.0.368

    APAR IZ20931 IZ21095

    PTF U817986


    1.Modified the MRCP message handling code to improve the
      stability under load. Specifically this change prevents
      the MRCP custom server from leaking file descriptors.
      (IZ20931)

    2.Prevented the MRCP plugin from spuriously reporting
      DTJ7583 when using TTS from a Nuance server.
      (APAR IZ21095)

  • Update 4.2.0.330

    APAR IZ15445

    PTF U816233


    1.This PTF Modifies the socket handling code in TSLOT and the
      MRCP CS to prevent errno 72 (ECONNABORTED) from
      terminating the processes.
      This PTF contains the MRCP CS changes. You must also
      install fix level dirTalk.DT.rte at level 4.2.0.351
      which contains the TSLOT changes.
      (IZ15445)

  • Update 4.2.0.347

    APAR IZ14725

    PTF U816100


    1.Corrected an ArrayIndexOutOfBounds exception that could
      occur when using an application with inline grammars
      with MRCP on Nuance.
      (APAR IZ14725)

    2.Corrected the ulaw/alaw handling for both recognition and
      tts when the SpeechClient is used with Nuance.
      (Defect 7026)

  • Update 4.2.0.297

    APAR IZ05665

    PTF U813382


    1.Improved the handling of grammars that use empty
      strings in the result tags.
      (APAR IZ05665)

    2.Modified the error message text for a failed plugin
      installation to improve the end user experience.
      (Defect 7015)

    3.Fixes internal problem with trace values.
      (Defect 36172)

  • Update 4.2.0.293

    APAR IZ01170 IZ01175 IZ03238

    PTF U812854



    1.Fixes rare NullPointerException during far end
      disconnect processing.
      (APAR IZ01170)

    2.Correct a serialisation problem that can result in
      NullPointerException or ConcurrentModificationException
      when MRCP messaging is stressed.
      (APAR IZ01175)

    3.Modified the MRCP plugin code to check that a
      RECOGNNITION-COMPLETE or START-OF-SPEECH event is for the
      correct RECOGNIZE request. This prevents us from sending a
      spurious second RECOGNIZE request on the same session.
      (APAR IZ03238)

  • Update 4.2.0.290

    APAR IZ00978

    PTF U812203



    1.This PTF corrects grammar scope order so that if an
      utterance is matched in both field level and a higher
      grammar (form or link) the field match is reported.
      (APAR IZ00978)

  • Update 4.2.0.256

    APAR IY94941

    PTF U811201



    1.Modified the MRCP plugin to remove some spurious
      debug output.
      (APAR IY94941)

  • Update 4.2.0.246

    APAR IY92939

    PTF U810626



    1.Configuration changes for SpeechClient.
     (APAR IY92939)

  • Update 4.2.0.235

    APAR IY91009 IY87064

    PTF U810391


    1.Modified the MRCP plugin to alter the confidence score into
      the VXML2 range if this parameter is set to true in dtj.ini
      A new parameter has been added to /var/dirTalk/DTBE/dtj.ini:
      wvr.use.vxml2.confidencerange.
      This controls whether, in an MRCP configured system, the
      confidence scores are returned to the VXML2 application
      in the range
      0 - 100 or 0 - 1.
      To use 0 - 100 use the value of false for the new parameter.
      To use 0 - 1 use the value of true for the parameter.
      Note that the default value is false.
     (APAR IY91009)

    2.When utterance duration exceeds the maxspeechtimeout property
      value a "noinput" event is thrown.
      This should be a "maxspeechtimeout" event.
      After the installation of this APAR when the utterance
      duration exceeds the value set a "maxspeechtimeout" event
      will be thrown.
      (APAR IY87064)

  • Update 4.2.0.227

    APAR IY87541

    PTF U809400


    1.Updated an error message reported when the SpeechClient
      import fails
      (APAR IY87541)

    2.SpeechClient Custom Server MRCP has been added to
      the import checker.
      (Defect 35952)

  • Update 4.2.0.214

    APAR IY85213

    PTF U807982

    1.Changes made to ensure that the correct error event is
      thrown when the ASR and TTS servers are unavailable.
      NOTE after installation of this PTF you must perform the
      following steps.
         1) Start Websphere Voice Response for AIX but ensure that
            custom server DTJ_VV_Logger is not running.
         2) Stop VRBE if running ( dtjstop + dtjshost -exit )
         3) Stop DTJ_VV_Logger if running
         4) cd /var/dirTalk/DTBE/plugins
         5) dtjplgin dtjmrcp.zip
         6) Start VRBE ( dtjshost + dtjstart )

     (APAR IY85213)

  • Update 4.2.0.205

    APAR IY82417

    PTF U806979

    1.Modifications have been made to the configurable options
      for SpeechClient voice recognition.
      (APAR IY82417)

  • Update 4.2.0.165

    APAR IY78255

    PTF U805947

    1.This fix corrects a problem where the execution of
      vae.setuser caused the MRCP Custom Server to fail to
      start and give no failure indication. Now if the MRCP
      Custom Server fails to start because of insufficient
      authority then a RED user alarm is raised in the
      system monitor window.
      vae.setuser is corrected in fix level 4.2.0.166
      PTF  U805948
      (APAR IY78255)

  • Update 4.2.0.162

    APAR IY77053

    PTF U805747

    1.This PTF fixes a problem in the Speech Connector such
      that outbound MRCP messages were suffering from packet
      fragmentation, adding extra delays before receiving the
      response from the MRCP server.
      (APAR IY77053)

  • Update 4.2.0.138

    APAR IY74389

    PTF U804306

    1.This PTF contains extra SpeechClient fixes required for
      the static / crash problem.
      (APAR IY74389)

  • Update 4.2.0.136

    APAR IY74146

    PTF U804302

    1.This PTF uses the correct comfort noise data when the
      system has no packets of real data.
      (APAR IY74146)

  • Update 4.2.0.125

    APAR IY73561

    PTF U803995

    1.Support multiple language reco using MRCP
      (APAR IY73561)

    2.This fix enables hotword bargein with WVS version 5.1.3
      or later
      (Defect 6906)

    3.This fixes a problem with multilanguage vxml scripts
      that gives rise to high network loading, caused be
      redundant streaming of voice data
      (Defect 6910)

  • Update 4.2.0.120

    APAR IY72984

    PTF U803955

    1.Remove extra logging to the DTstatus.out from the
      MRCP_Log custom server
      (APAR IY72984)

    2.Stop occasional white alarms being generated by the
      MRCP custom server
      (Defect 35701)



VRBE_XML Fixes



Fix Level 4.2.0.597 (PTF U861172 U861378 )
Fix release date: 02 Oct 2013
Status: Current
APAR Description
IV48454 Fixed an issue that prevented POST data from reaching the CCXML HTTP server. The server will now accept parameters delivered both in POST data and on the URL as GET-parameters.
Internal Defect Fix
  • Fixed an issue where dtjlogmon would fail to realise that the condition that it was searching for had occurred due to either hanging on the dtjflog read or failing to read a large enough part of the log file to actually make a full trace line.


Fix Level 4.2.0.590 (PTF U858091 )
Fix release date: 11 Mar 2013
Status: Superseded
APAR Description
IV37133 Fixed issue where config.cfd from before VRBE PTF 585 would cause InvalidClassException and/or SerializableException on VRBE startup and dtjconf would also throw this exception.


Fix Level 4.2.0.585 (PTF U853622 )
Fix release date: 07 Sep 2012
Status: Superseded
APAR Description
IV21356 Implemented a fix to reset VRBE tracing using the trcserv command. Previously, when resetting VRBE tracing after removing some trace options from trcserv.ini, the value for the removed option would not revert to the default. This only affected a couple of the trace options, including trace.output.dir. This has now been fixed so that if the option is no longer present in trcserv.ini, the default option value is used.
IV25871 Fixed a potential deadlock in Audio fetching present in VRBE levels 4.2.580 - 4.2.584. With those levels, Audio fetches would stop being processed but VoiceXML would otherwise operate should this deadlock occur.


Fix Level 4.2.0.584 (PTF U851838 )
Fix release date: 28 Jun 2012
Status: Superseded
APAR Description
IV20911 Fix to voiceXML <goto> element to correctly handle blank next attribute after evaluation. Previously would throw StringIndexOutOfBoundsException.


Fix Level 4.2.0.580 (PTF U851653 )
Fix release date: 12 Apr 2012
Status: Current
APAR Description
IV17301 Fixed a memory leak in the audio cache which would occur only for dynamically generated audio file URIs. A Hashmap grows with each new request that doesn't have the same URI as a previously fetched resource.
Internal Defect Fixes
  • Improve error reporting when attempting to parse an invalid VXMLdocument. The trace and log will contain URI (including attributes), line number, column number and XML parsing error. The logging showing the semi parsed VXML document as been removed as this was confusing and unhelpful.
  • Fixed a rare NullPointerException. The NullPointerException was reported as:
    (DTJ1008046) FAILURE:  VXML2TurnCoordImpl.doField Caught a RuntimeException: java.lang.NullPointerException
         at com.ibm.wvr.vxml2.VXML2TurnCoordImpl.doField
    (VXML2TurnCoordImpl.java:1359)
         at com.ibm.wvr.vxml2.VXML2TurnCoordImpl.doTurn
    (VXML2TurnCoordImpl.java:269)
         at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)





  • Update 4.2.0.572

    APAR IV12552 IV12570

    PTF U848096

    1.The error message: "com.ibm.ccx.browser.CCXParser parse() Got    
      SAXException (Error in <ccxml> element: Document has more than  
      one  <ccxml>" appears despite the document being fetched not    
      having multiple ccxml elements.
      CCXML then refuses to load any more documents with the same error.
      (APAR IV12552)

    2.Fixed to ensure connection.transfer.disconnect is not thrown to
      quickly after a CTI transfer.
      (APAR IV12570)

    3.Fixed an issue where WVR would fail to fetch certain Nuance builtin
      URIs reporting a FileNotFoundException.
      (Defect 7581)

    4.Fixed the universals help grammar to work with various speech site
      documents.
      (Defect 7588)

    6.Fixed internal system monitor functionality.
      (Defect 7591)

    7.Move some CPU intensive tracing from trace level 8 to trace level 9.
      (Defect 7592)

    8.Increased the default trace buffer size and reduce time waiting if
      there are no more trace buffers. This does not change the amount of
      trace written to disk or the size of the trace files on the disk. The
      change is to handle situations when a lot of trace is being generated
      and the internal trace system can not keep up. When this happens the
      tracing routines will slow down causing VRBE to also slow down.
      (Defect 7595)

  • Update 4.2.0.570

    APAR IV06611

    PTF U848089

    1.Changes to ensure that the correct connection.disconnect.hangup
      event is returned if a caller HUPs before a transfer is started.
      (APAR IV06611)

    2.Fixed caching mechanism to allow VXML Browsers to continue
      operation after failing to  cache a successfully fetched document.
      Warnings will still be logged to the log files and it is recommended
      that these errors be fixed or they may affect your performance but
      VRBE should recover without user intervention.
      (Defect 7574)

    3.Improved application error logging and inclusion of document name
      where missing to VoiceXML and Javascript parsing and runtime errors.
      (Defect 7551)

  • Update 4.2.0.566

    APAR IV01546 IV02976

    PTF U844287

    1.Corrected a potential exception within the dtjstop command that can
      VRBE cause nodes to remain running after dtjstop is executed.
      (APAR IV01546)

    2.Code changes made to ensure that the correct "termtimeout" is used
      for a nomatch when using a DTMF grammar.
      (APAR IV02976)

    3.Fix to enable the passing of the VoiceXML <mark> element to a speech
      server in a VoiceXML version 2.0 application.
      (Defect 7546)

    4.Fix NullPointer Exception when using <initial> element in VXML.
      (Defect 7517)

    5.ECMAScript version 1.7 now available to configure via the dtjes
      script.
      (Defect 7542)

    6.Fixed an issue resolving specific NumToApps for CCXML services
      which overlaps wildcarded non-CCXML application NumToApp definitions.
      (Defect 7540)

  • Update 4.2.0.562

    APAR IZ99396 IZ99397 IV00011

    PTF U843719

    1.
    Provide parameters to allow a system administrator to limit the
      number of threads WVR will use when fetching resources on system
      startup.  The following parameters have been added:

         wvr.vxml2.fetchthreads.limit
         wvr.vxml2.fetchthreads.limit.timer

      Where wvr.vxml2.fetchthreads.limit is the maximum number of threads
      to use (default is 500) and wvr.vxml2.fetchthreads.limit.timer is the
      time in minutes to apply the limit (default 10 minutes). After this
      time, WVR will revert to the default maximum thread limit.  Setting
      wvr.vxml2.fetchthreads.limit.timer to 0 applies the limit
      permanently.
      (APAR IZ99396)

    2.Fixed an issue where VRBE would repeatedly fail to load corrupted
      items in the cache to automatically reload the corrupt items from
      their source. This would typically be caused by running out of space
      on the filesystem.
      (APAR IZ99397)

    3.Fixed an issue with caching long URIs that did not contain a '?',
      and would instead throw an IOException.
      (APAR IV00011)

    4.Fixed an issue where CCXML would not use the default port on an
      outbound <send> HTTP post.
      (Defect 7520)

    5.Fixed default CCXML HTTP Server port number which incorrectly
      specified port 80. The correct default CCXML HTTP Server port number
      is 1971.
      (Defect 7530)

  • Update 4.2.0.556

    APAR IZ94402 IZ95648

    PTF U842072


     1.Fixed a NotSerializableException possible with caching Audio files.
      (APAR IZ95648)

    2.Fixed an issue where VoiceXML2 applications invoked from the Java API
      could fail with a NullPointerException.
      (APAR IZ94402)

  • Update 4.2.0.554

    APAR IZ91373

    PTF U840694


     1.Fixed a potential "No Reco or TTS plugin found error" when using
      CCXML applications.
      (APAR IZ91373)

    2.Fixed an issue where CCXML wildcard NumToApp mappings would take
      precedence over specific VoiceXML or Java API applications. For
      example, using the following NumToApp mappings:
        NumToApp=111,VXMLApp
        NumToApp=1*,CCXMLService
      (Defect 7466)

    3.Fixed an MRCP resource problem that can result when multiple VXML
      documents are called from one CCXML document during a single call.
      (Defect 7467)

    4.Fixed a potential StringIndexOutOfBoundsException that could occur
      is there was an error when using dtjcache to list items.
      (Defect 7468)

    5.Fixed the VoiceXML caching to allow long URIs to be stored
      (Previously, AIX would prevent any URI longer than 254 characters
      being stored)
      (Defect 7470)

    6.Fixed an issue which would cause a second instance of
      connection.connected events to be generated when being moved from
      one session to another using <move>
      (Defect 7474)

    7.Fixed an issue where return values from a VoiceXML <exit> would be
      preserved for a second VoiceXML document used on the same call.
      (Defect 7475)

    8.Fixed CCXML-controlled VoiceXML transfers to be more descriptive in
      errors. Also fixed dialog.transfer events to contain .uri as per
      spec, the .URI parameter has been kept for backwards compatibility.
      (Defect 7476)

    9.Fixed an issue where a NullPointerExcception would be seen on making
      an outbound call from CCXML's <createcall> tag.
      (Defect 7477)

    10.Fixed an issue where dynamic browsers were not released for five
      minutes when VoiceXML made a transfer using CCXML.
      (Defect 7480)

    11.Fixed an issue with CCXML <move> that could lead the
      session.connections entry of a connection to have an
    inconsistent
      input and dialogid entry.
      (Defect 7481)

  • Update 4.2.0.550 - Fix Pack 2

    APAR IZ85999

    PTF U839633


    New features contained in this PTF
    * Enhanced VoiceXML and CCXML application support for call
      information - Provide protocol specific tagging information in
      VXML and CCXML.
    * VRBE Expire Resource Tool - allows a system administrator to
      manually expire a resource in the VXML, CCXML or Audio caches.
    * VRBE problem determination utility - enables a system
      administrator to collect a dtbeProblem output (or run any
      other command) automatically when an error or other message is
      reported in VRBE.

    For further information on the Fix Pack 2 features please
    refer to the TechNote at the following URL:

     
    http://www.ibm.com/support/docview.wss?rs=761&uid=swg21449523

    New fixes contained in this PTF

    1.Introduced a new dtj.ini paramter 'wvr.vxml2.grammar.external.fetch'
      to provide an override in WVR for unnecessary grammar
      fetching/caching when using SpeechServer.

      If wvr.vxml2.grammar.external.fetch=false, then http/https/builtin
      grammars will no longer be fetched by WVR (either at prefetch or
      during document execution), but they still will be fetched by the
      speech server. Only file: grammars will continue to be fetched by
      WVR.

      By default this is set to true (current behavior) ie all grammars
      are fetched by WVR.
      (Defect 7449)

    2.Fixed an issue where cached VoiceXML files would remain in the cache
      (but be unused ) when the cache control headers were changed to
      nocache or to have an expires value of 0.
      (Defect 7447)

    3.Fixed a potential NullPointerException when executing a dialogprepare
      element in CCXML.
      Note that this would not occur with a straight dialogstart.
      (Defect 7441)

    4.Remove erroneous file from vxi.jar.
      (Defect 7437)

    5.Allow non W3C defined builtin grammars to be referenced within VXML2
      documents as supported by Nuance. e.g. CreditCard.
      (Defect 7424)

    6.Fixed an incompatibility issue with Nuance recognition and WVR which
      could cause an "ERROR: NLSMLException" to be reported in the VRBE
      log files.
      (Defect 7422)

  • Update 4.2.0.530

    APAR IZ84683

    PTF U837322


    1.Fixed an issue that can cause a MRCP PluginException
       (completion-cause 006) if a caller hung up just
       after a recognitionattempt was started.
       (APAR IZ84683)

  • Update 4.2.0.525

    APAR IZ81207

    PTF U836783


    1.Corrected a potential NullPointerException when starting VRBE.
       The error results in the named application failing to start. The
       error text is as follows:
     
       DTJ3027 The request to start application <application name> on
       node <node name> at host LocalHost failed.
       java.lang.NullPointerException

       (APAR IZ81207)

    2.When using Java 1.5, <object> element calls to java classes may
       fail due to tighter rules on class name definitions. This fix
       ensures that java classes are invoked correctly   internally and
       requires no change to the customers VXML application.
       (Defect 7431)

  • Update 4.2.0.523

    APAR IZ78465

    PTF U836468


     1.Corrected a potential deadlock when fetching VXML resources that can
      cause a memory leak and eventual OutOfMemory error.
      (APAR IZ78465)

  • Update 4.2.0.518

    APAR IZ73213 IZ74903

    PTF U835663 U835665

    1.Fixed a VarScope error which can occur when a grammar result returned
       from a Nuance server includes empty strings. The VarScope error will
       look like the following:

       (VXI00000) FAILURE: 654322449181048843-0:VarScope::eval:syntax
       error:error executing:function evalSI ()

       (APAR IZ73213)

    2.Fixed an issue that can cause a delay in a speech enabled VXML
       application if the caller does not provide any input to the prompt.
       (APAR IZ74903)

    3.Fixed a problem where the VXML Transfer tag fails to transfer call
       when transfer destination is a SIP number.

       NOTE: After installation of the PTF a new version of DTJConsult.st
       state table installed on the system, which has not been imported.
       To import this state table follow the instructions below:

       a) Ensure WVR is running.
       b) As WVR user (normally dtuser) run:
           DTst -export -f $DTJ_DIR/DTJConsult.st.backup -o DTJConsult
       c) cd $DTJ_DIR
       d) dtjstimp DTJConsult.st
           Note: a non zero result means failure

       If you have customised DTJConsult state table, you will need to
       restore those changes. The modified state table was backed up in
       step b) to the file $DTJ_DIR/DTJConsult.st.backup. Changes to the
       DTJConsult state table for this fix are:

       * add a local variable sipnumber:

         LOCAL      STRING sipnumber;

       * and then add the following code:

         AssignData (sipnumber, "LEFT", numberToCall,4);
         IF (sipnumber = "sip:")
         THEN
           AssignData(SV541, "PUT_TAG", "TO_HDR", numberToCall)
            ;
          TransferCall("", "", 0, 0, 0)
            edge EDGE_TC_SUCCESSFUL:            success
            edge EDGE_TC_INVALID_PHONE_NO:      invalid_num
            edge EDGE_TC_PHONE_BUSY:            busy
            edge EDGE_TC_NETWORK_BUSY:          network_busy
            edge EDGE_TC_NO_ANSWER:             no_answer
            edge EDGE_TC_OUTBOUND_LINE_PROBLEM: failed
            edge EDGE_TC_UNEXPECTED_TONE:       failed
            edge EDGE_HUP:                      hup
          ;

        ENDIF

       * before the line that checks that ringTime = 0:

         IF (ringTime = 0)

       (Defect 7361)

    4.Fixed an issue where CCXML was loading the incorrect VXML document
       when many VXML documents are being loaded from CCXML at once.
       This was due to accidental sharing of objects that hold the
       parameters to be passed to VoiceXML from CCXML. The fix ensures
       that the objects are not shared between threads.
       (Defect 7400)

    5.Fixed an issue with CCXML that would occasionally cause a
       CCXThread.run() message in the logs reporting a NullPointerException,
       and CCXML wouldn't start up. This is due to a timing error in
       sending  messages before the internal queues are set up completely.
       (Defect 7409)

  • Update 4.2.0.512

    APAR IZ68012

    PTF U832493

    1.Fixed a StringIndexOutOfBoundsException raised by the VXML browser
      which could cause the browser instance to terminate.
      (APAR IZ68012)

  • Update 4.2.0.504

    APAR IZ64150

    PTF U830462 U830463 U830606

    1.This fix corrects an out of memory cache problem which
      can occur when fetching large numbers of CCXML documents.
      (APAR IZ64150)

  • Update 4.2.0.471

    APAR IZ59164 IZ59310

    PTF U828058

    1.Fixed a potential NullPointerException within the VXML2
      browser which could occur after a VarScope error was caught.
      (APAR IZ59164)

    2.Maxspeechtimeout events did not generate an
      application.lastresult$ variable. However, with the
      introduction of recordutterance it is useful for them
      to do so in order to access the recording subproperty.
      (APAR IZ59310)

  • Update 4.2.0.470

    APAR IZ56749

    PTF U828057

    1.Fix potential abnormal termination of dtjflog.
      (APAR IZ56749)

    2.Help for dtjtrcmod now updated to include the -status
      parameter.
      (Defect 7322)

  • Update 4.2.0.469

    APAR IZ56285

    PTF U828056

    1.Corrected the code to prevent this error from occurring
      during a recognition attempt:

        (6001195)  com.ibm.telephony.directtalk.mrcp.MRCPReco run()
         ERROR: Unexpected bargeinType 0
      (APAR IZ56285)

  • Update 4.2.0.466

    APAR IZ53945 IZ53309

    PTF U827377


    1.Corrected a potential problem when using the
      invokeApplication method to move between VXML and
      Java applications which could result in the VXML
      application remaining active even after the caller has
      hung up.
      (APAR IZ53945)

    2.Add reference locking to handling of the audio cache.
      This is to stop the cache handling code leaking memory
      when lots of different audio files are used.
      (APAR IZ53309)

  • Update 4.2.0.461

    APAR IZ51751

    PTF U825880

    1.Fix a timing window with the audio import/playing code.
      If two calls attempts to play audio which hasn't been
      cached the first call will import the audio. The second
      call then incorrectly attempts to play the audio before
      its finished importing.
      (APAR IZ51751)

  • Update 4.2.0.460

    APAR IZ50041 IZ50786

    PTF U825878


    1.WVR Audio cache directives are case sensitive and do
      not allow for multiple directives as described within the
      W3C specification. This fix allows for multiple directive
      and recognised directives can occur anywhere within the
      CacheControl directive string.
      Improved checking of the Cache-Control directives for audio
      file.
      (APAR IZ50041)

    2.This fixes an emergent scenario where delayed CCXML messages
      could be lost if they had exactly the same end timeout value.
      This is more likely to happen on systems with a less fine
      grained time representation. Outside of CCXML, this change
      should have no impact.
      (APAR IZ50786)

  • Update 4.2.0.458

    APAR IZ49889

    PTF U825876

    1.This PTF corrects a potential Java memory leak within the
      VRNode JVM when using VXML2 applications.
      (APAR IZ49889)

  • Update 4.2.0.455

    APAR IZ46787 IZ48373

    PTF U824564 U824565


    1.Modified the code to enable sharing of cookies between VXML
      and audio fetches.  Before applying this fix, any cookies set
      on a VXML fetch response would not be sent on an audio
      fetch request.
      (APAR IZ46787)

    2.Improved error handling for VoiceXML bargein detection when
      hardware grunt detection has overriden the VoiceXML
      document via a statetable call and enablement via SV217=1.
      Additional logging has also been include to highligh
      this as an unsupported configuration
      (APAR IZ48373)

    3.Prevents exceptions during CCXML call cleanup and
      resulting log messages.
      (Defect 6981)

    4.When the "dtjconf -action export" command was being run,
      the following parameters were not being exported if present
      in any TelephonySevice definition within the exported
      configuration:
        ClientName
        AAIKeys
        CallIDRange
      (Defect 7136)

    5.Provides a sample to customers on how to use CCXML.
      Set up default.cff to point to the Sample7.ccxml file and
      run dtjconf to import the default.cff. Then run the code.
      The file Sample7.ccxml contains many examples on how to use
      ccxml and how it interacts with VoiceXML, and is heavily
      commented to explain itself. Thus it is recommended that
      customers examine the file themselves to get a better
      understanding of the functionality.
      (Defect 7077)

  • Update 4.2.0.454

    APAR IZ45853

    PTF U824562

    1.This fix removes expired audio cache directories to stop excess
      directories existing, which led to a situation where the system
      ran out of links in a directory, and an AIX error occured when
      creating a new cached file.

      After installing this PTF, in order to get the full effect
      you should remove the current audio cache manually.  To do
      this, perform the following:
       1) Ensure that VRBE is stopped (dtjstop followed by dtjshost -exit)
       2) cd into $CUR_DIR/voice/ext/v2c
       3) Remove the "ip address" named directory.
       4) Restart VRBE
     (APAR IZ45853)

  • Update 4.2.0.443

    APAR IZ38758

    PTF U822817


    1.This fix addresses a problem that can cause a plugin to
      leak resources. Specifically the MRCP plugin would leak
      file descriptors leading to a complete failure of both
      reco and TTS.
      (APAR IZ38758)

  • Update 4.2.0.437

    APAR IZ36575

    PTF U822398


    1.Fixed a NullPointerException that could occur if a
      CCXML application calls out to a second VXML dialog
      during a single call.
      (APAR IZ36575)

  • Update 4.2.0.434

    APAR IZ35025

    PTF U821507

    1.Improve HTTP server incoming and outgoing requests in CCXML.
      (APAR IZ35025)

  • Update 4.2.0.420

    APAR IZ29245

    PTF U819608

    1.When running ISDN/SIP with CCXML it is possible that
      the connection.alerting transition does not present
      values for connection.local and connection.remote.
      The values were available during connection.connected
      Fix is to present the information during
      connection.alerting state
      (APAR IZ29245)

  • Update 4.2.0.419

    APAR IZ27144

    PTF U819375


    1.Removed a small timing window which could result in
      a NoSuchElementException from the dtjmrcp plugin code.
      (APAR IZ28793)

  • Update 4.2.0.415

    APAR IZ27144

    PTF U819375

    1.Handle HTTP requests which don't have responses,
      ie HTTP server closing the socket
      (APAR IZ27144)

    2.Fix up namelist handling, and the loss of original
      variables when building up the namelist
      (Defect 7041)

    3.Handle various socket errors for badly constructed HTTP servers
      (Defect 7044)

    4.Add support for appendix K of the CCXML spec. Allowing
      applications to POST events to the CCXML browser, and the
      CCXML browser to send HTTP POST requests.
      (Defect 7040)

  • Update 4.2.0.407

    APAR IZ24444

    PTF U818973 U818974


    1.Tighten requisite filesets.
      (APAR IZ24444)

  • Update 4.2.0.363

    APAR IZ17301

    PTF U817179


    1.Fix to CCXML browser code to ensure that the connection
      class attribute "originator" is correctly set to "local"
      for oubound calls and "remote" for inbound calls
      (APAR IZ17301)

    2.Correct handling of Timer Already Cancelled state in fetch
      to prevent exception.
      (Defect 7032)

  • Update 4.2.0.352

    APAR IZ15492

    PTF U816335

    1.Modified the handling of semantic interpretation or tag
      strings in the VXML2 browser code to prevent WVR from
      altering the string that the recognizer returns.
      (APAR IZ15492)

  • Update 4.2.0.346

    APAR IZ14702

    PTF U816098 U816099

    1.Modified the WVR VXML2 audio cache so that it correctly performs
      a get-if-modified on expired resources. The behaviour before
      this change was to delete expired resources and so force a
      re-fetch from the webserver.

      In order to use the original behaviour after installing
      this fix the following parameter can be set
      in $DTBE_HOME/dtj.ini:

      wvr.audiocache.no.expiry=false

      (APAR IZ14702)

  • Update 4.2.0.342

    APAR IZ11272

    PTF U815930

    1.This APAR fixes an intermittent problem that can result
      in: DTJ7588 Problem with MRCP Custom Server messages when
      first TTS prompt of a call is null string.
      (APAR IZ11272)

  • Update 4.2.0.340

    APAR IZ11252

    PTF U815634


    1.This PTF expands the Computer Telephony Integration (CTI)
      support to include Genesys Framework V7 from the VoiceXML
      2.1 and CCXML development environments.
      Further details on configuration and usage can be found in
      the following technote
     
    http://www.ibm.com/support/docview.wss?rs=761&uid=swg21289489
      (APAR IZ11252)

  • Update 4.2.0.339

    APAR IZ10989

    PTF U815458

    1.This APAR fix adds limited validation to the Classpath
      entries when a VRBE node is started. If any entries cannot
      be located or are not readable message DTJ2009 will be
      output to the node.out file.
      (APAR IZ10989)

  • Update 4.2.0.336

    APAR IZ10136

    PTF U815450

    1.Corrects handling of Timer Already Cancelled state in
      fetch to prevent exception.
      (APAR IZ10136)

  • Update 4.2.0.320

    APAR IZ06705

    PTF U814349 U814350 U814351 U814352 U814509 U814510 U814610 U814687 U814688 U814697 U814698 U814699



    1.Fix ensures that exact NumToApp mapping will always be
      selected over a mapping which contains a wildcard
      as documented in GC34-6378.
      (APAR IZ06705)

    2.Corrects minor problem with vrbeProblem data collection.
      (Defect 7018)

    3.This fix improves hangup detection during a single step
      transfer and prevents a potential browser hang.
      (Defect 7020)

  • Update 4.2.0.300

    APAR IZ05722

    PTF U813383 U813384


    1.Consolidation of previous PTFs covering WVR VRBE_XML filesets.
      (APAR IZ05722)

  • Update 4.2.0.277

    APAR IY97197 IY97219

    PTF U811642

    1.Corrected the default behaviour of the system when a
      maxspeechtimeout event is triggered in a VXML2 application so
      that it now conforms to the VXML2 specification.
      (APAR IY97197)

    2.This fix corrects a problem with the vxml browser so that
      it now accepts the recordutterancetype property in vxml2.1
      (APAR IY97219)

  • Update 4.2.0.266

    APAR IY95820 IY89776

    PTF U811222 U811255

    1.Made a change to ensure that a maxspeechtimeout event can get
      thrown when executing a hotword bargein prompt.
      (APAR IY95820)

    2.This fixes a problem compiling sub rules in dtmf
      grammars.
      The DTMF grammar chache must be cleared once installed.
      rm -fr /var/dirTalk/DTBE/native/aix/dtmfGrammarCache
      and then
      mkdir /var/dirTalk/DTBE/native/aix/dtmfGrammarCache
      (APAR IY89776)

    3.Corrects trace entry to aid problem determination.
      No user visible chnages.
      (Defect 7004)

    4.Prevents ASSERT in VXML2SpeechSupport.speechStarted()
      after IY95820.
      (Defect 7008)


  • Update 4.2.0.257

    APAR IY94963

    PTF U811202

    1.Fixed a NullPointerException that could occur when using
      the VXML2 <if> statement.
      (APAR IY94963)

  • Update 4.2.0.255

    APAR IY94931

    PTF U811200

    1.Updates vrbeProblem to pick up log and trace files
      from non-default locations.
      (APAR IY94931)

  • Update 4.2.0.253

    APAR IY94397

    PTF U810932


    1.This update creates the session.ibm.callID session
      variable for new incoming calls.
      (APAR IY94397)

  • Update 4.2.0.252

    APAR IY93783

    PTF U810930

    1.Fixed a problem with transfer type="consultation"
      in VXML2.
      (APAR IY93783)

  • Update 4.2.0.245

    APAR IY91534 IY92134

    PTF U810623

    1.Fixes a problem with duplicate application instances
      being displayed by dtjqapps.
      (APAR IY91534)

    2.Fixed problem when running vrbeProblem script with a relative
      output path. Also fixed a problem where a file called
      '{OUTPUTFILE}' would be created in the output directory.
      (APAR IY92134)

    3.Reports unknown errors from the SpeechClient plugin to
      browser/application as error.internal
      (Defect 6989)

  • Update 4.2.0.239

    APAR IY91660

    PTF U810589

    1.Fixed a problem with transfer type="consultation" in VXML2.
      (APAR IY91660)


    2.Added diagnostic utilities for VRBE environment.
      (Defect 6967)


    3.Corrected problem with diagnostic routines.
      (Defect 6982)

  • Update 4.2.0.234

    APAR IY90841 IY90627 IY91308

    PTF U810390

    1.Improved the handling of grammars that use empty strings
      in the result tags.
      (APAR IY90841)

    2.Fixes NullPointerException terminating VXML2 browser when
      <dialogterminate> tag is used in CCXML.
      (APAR IY90627)

    3.Correct problem caused by timeout handling looping in
      browser.
     (APAR IY91308)

  • Update 4.2.0.230

    APAR IY90005 IY89358

    PTF U809680

    1.Corrected the "dtjconf -action export" command so that the
      correct value for the AIXPortNumber parameter is displayed
      in the resulting output file.
      (APAR IY90005)

    2.Fixes NullPointerException when application transitions
      through multiple documents using fetchaudio and no audio
      has been output to caller.
      (APAR IY89358)

  • Update 4.2.0.226

    APAR IY87079 IY87777 IY88142

    PTF U809398 U809399

    1.This APAR resolves a problem with Italian scansoft
      TTS engines when used with multi-lingual applications
      where the text '`l5' for the language code is read out by
      the scansoft engines before the text in the application.
     (APAR IY87079)

    2.Added a new parameter so that the default 5 minute timeout
      for a CCXML controlled VXML dialog can be modified by the
      administrator. The parameter should be set in
      $DTBE_HOME/dtj.ini like so:

        wvr.ccxml.dialog.timeout=<value in minutes>

      Where <value in minutes> is the required timeout value
      specified in minutes.
     (APAR IY97777)

    3.Updated the DTMF grammar compiler to fix a problem.
      (APAR IY88142)

    4.Fix adds additional trace entry. No user visible changes.
      (Defect 6961)

  • Update 4.2.0.217

    APAR IY85799

    PTF U808516

    1.Modified order of CCXML transitions when a far end
      disconnect is reported to a CCXML document. The new
      order should be to receive a connection.disconnected
      prior to a dialog.exit
      (APAR IY85799)

  • Update 4.2.0.213

    APAR IY81735

    PTF U807981

    1.VoiceXML browser caches results of fetch requests when
      method="post". This is incorrect as RFC2616 states that
      post results should not be cached. Browser corrected to
      conform with RFC.
      (APAR IY81735)

  • Update 4.2.0.210

    APAR IY84110 IY82726 IY83674 IY84378

    PTF U807567

    1.Corrected a parse error when using the http-equiv attribute of
      the meta tag in a CCXML application.
      (APAR IY84110)

    2.Fixes to consulted transfer requests issued via CCXML
      (APAR IY83674)

    3.Fixed "can't find active ConnectionItem" failures reported in
      log.1.log when trying to use Genesys T-Server with CCXML
      (APAR IY82726)

    4.The default reason applied when a CCXML <disconnecte> call is made
      without an application supplied reason, will now result in a
      connection.disconnect being generated with a default value
      of "near_end_disconnect"
      (APAR IY84378)

    5.Creates es_MX site documents to override the default Spanish
      to replace two character locale information with 5 character
      locale required by WVS version 5.
      (Defect 6941)

    6.Corrected spurious error.notallowed events in the CCXML processor.
      (Defect 6951)

    7.Fixed an infinite loop when running certain CCXML applications.
      (Defect 6946)

  • Update 4.2.0.204

    APAR IY82081

    PTF U806978

    1.Site documents for German updated for use with
      WVS version 5.
      (APAR IY82081)

  • Update 4.2.0.203

    APAR IY81629

    PTF U806976

    1.Corrected a problem with recording caller utterances when
      using WVS 4.2.
      (APAR IY81629)

  • Update 4.2.0.183

    APAR IY78441 IY78450 IY78503

    PTF U806354

    1.The problem when a VXML2 document had Cache-Control header
      set to public and there was no max-age property set, the
      browser would still fetch the resource from the server
      each time rather than correctly caching it has been
      corrected.
      (APAR IY78503)

    2.The VXML2 fetch problem when performing root to root
      transition has been corrected.
      (APAR IY78441)

    3.The problem where HTTP redirects were not handled correctly
      by the VXML2 browser, specifically when an application
      used relative URIs has been corrected.
      (APAR IY78450)

  • Update 4.2.0.180

    APAR IY78792

    PTF U806177 U806178

    1.Enhancements to vrbeProblem to include
      - Prompt user to include PMR (if known) and include
        in output filename
      - Collect system name and date/timestamp in output
        filename
      - Collect all logs and trace files rather than a subset
      (APAR IY78792)

    2.Problem gathering routines updated to work in silent mode
      (Defect 6932)

  • Update 4.2.0.170

    APAR IY78582

    PTF U805960

    1.Fixed a memory leak/high memory consumption issue
      when running DirectTalk beans applications.
      (APAR IY78582)

  • Update 4.2.0.152

    APAR IY76967 IY75319 IY72495

    PTF U805629

    1.Corrects DTJ6300 Error when fetching document and
      content length header not set by the server.
      (APAR IY76967)

    2.Under some conditions the VXML2 file cache can
      become corrupted. This usually occurs when updates
      and cache cleanup are occuring in parallel.
      Updates are performed when self describing content
      like grammars use the meta tag to update cache
      properties like Expires.x.  Cache cleanup occurs, by
      default, when the cache exceeds 80% of it's capacity.
      This PTF includes a fix that allows this parallel
      activity to occur without causing cache inconsistency.
      Cache inconsistency is usually found when cache entries
      are zero length.
      (APAR IY72495)

    3.When using non default value for VXML fetchtimeout a
      Memory leak could occur causing timer tasks to be held by
      the timer. This has been corrected.
      (APAR IY75319)

  • Update 4.2.0.133

    APAR IY73577

    PTF U804242

    1.A fix has been made to ensure that VXML2 log data
      appears in the correct output location rather than
      going to stdout.
      (APAR IY73577)

  • Update 4.2.0.124

    APAR IY73555

    PTF U803993

    1.This fix will now pass To and From header SIP URI's from
      and inbound call on to the vxml browser.
      Pack configuration must be configured with the Channel ID's
      value set to 0, otherwise the Channel ID number will be
      passed to vxml instead of the sip uri.
      The To and From URI's will be present in the following
      session variables :
         session.connection.local.uri
         session.connection.remote.uri
      (APAR IY73555)

  • Update 4.2.0.119

    APAR IY72982 IY72688

    PTF U803954

    1.Removed the following spurious message from output logs:

        WARNING:  WARNING: ASR during tranfer
        not available...application will continue without.

       which was output even when there's no ASR defined.
      (APAR IY72982)

    2.Fixed a problem with speech recognition grammars where
      an external grammar rule reference was being used, but
      the grammar rule was not being activated.
      (APAR IY72688)

  • Update 4.2.0.113

    APAR IY72464

    PTF U803681

    1.This PTF corrects a cache replacement problem caused in
      fix level 4.2.0.101
      Any existing VXML2 cache directories will be removed during
      the installation of this PTF.
      When using WVR SpeechClient ensure that WVS 5.1 / 5.2
      accumulative fix package have been applied.
      This fix package is available from the WVS support web site.
     
    http://www.ibm.com/software/pervasive/voice_server/support/
      (APAR IY72464)

  • Update 4.2.0.101

    APAR IY71555

    PTF U803589 U803590 U803591 U803592 U803612 U803613 U803614 U803636 U803637 U803638 U803639 U803640

    1.This PTF adds support in VRBE_XML for IBM WVS 5.x
      speech client enabling use of the latest WVS server
      with WVR VoiceXML applications.
      Support has been added for VoiceXML 2.1 applications
      when used in conjunction with IBM WVS 5.x
      Various fixes and updates to VoiceXML and CCXML
      browser have also been made.
      KNOWN limitations:
      'hotword' bargintype is not supported on WVS 5.1.1 or WVS 5.1.2
      VoiceXML 2.1 <mark> tag is not supported on WVS 5.1.1 or WVS 5.1.2

      There is a known problem when returning ECMA variables such as true
      and false (for example in the built-in boolean grammar).
      This is being addressed and will be resolved in the near future.
      In the mean time, please contact a member of the IBM support
      team if you have questions relating to this issue.
      (APAR IY71555)

  • Update 4.2.0.83

    APAR IY71216

    PTF U803583

    1.This PTF removes a spurious message from logs.
      (APAR IY71216)

  • Update 4.2.0.81

    APAR IY68418 IY70360

    PTF U803317

    1.This fix corrects a NullPointerException when using
      cache-control=private for audio resources.
      Also includes a fix to correct a problem when using
      fetchaudiominimum property in vxml2 could cause the system
      to hang if the document is returned before the
      fetchaudiominimum completes.
      (APAR IY68418)

    2.This fix prevents an application from terminating with an
      error if a file in the VXML2 filecache is found to be zero
      bytes.
      (APAR IY70360)

    3.This fix prevents a URISyntaxException from occurring when
      Cache-Control=private is set for audio resources.
      (Defect 6859)

  • Update 4.2.0.75

    APAR IY69104 IY68788 IY69052

    PTF U802834 U802835

    1.A change has been made to subdialog handling to prevent an
      error being thrown when handling a hangup event.
      (APAR IY69104)

    2.A fix has been made to prevent a
      StringIndexOutOfBoundsException from occurring when
      transferring to a short destination number.
      (APAR IY68788)

    3.This fix corrects a problem when using the VXML2 transfer
      feature, using the VXML2 standard characters for Pause (P) and
      Wait for dialtone (W). Websphere Voice Response uses "," and "."
      respectively, and the VXML2 standard characters were not
      previously translated into this syntax.
      Applying this fix will allow "P" and "W" in VXML 2 documents
      to be executed correctly by Websphere Voice Response.
      (APAR IY69057)

    4.Correct problem when using bargein and multiple prompts.
      (Defect 6785)

  • Update 4.2.0.63

    APAR IY67121 IY67164

    PTF U802147 U802148

    1.Additional code added to aid problem debug routines.
      (APAR IY67121)

    2.Correct problem caused by fix level 4.2.0.56.
      Ensures decoding of escaped URI's conforms to VXML standards.
      (APAR IY67164)

  • Update 4.2.0.62

    APAR IY65015

    PTF U801600

    1.Fixes exception when audio file URI ending with trailing slash
      is encountered.
      (APAR IY65015)

  • Update 4.2.0.61

    APAR IY66063 IY66026 IY65511 IY66108

    PTF U801255 U801306

    1.A code fix has been made to address a memory leak from
      the waitForCall method.
      (APAR IY66063)

    2.A fix has been made to ensure that errors from fetchaudio
      do not result in the termination of the application node.
      (APAR IY66026)

    3.Fixed a problem in the ViaVoice Reco plugin that generated
      a class cast exception when running under CCXML.
      (APAR IY65511)

    4.Fixed a memory leak that could occur in a VXML2 application
      which uses lots of unique audio files.
      (APAR IY66108)

  • Update 4.2.0.56

    APAR IY64878 IY64747

    PTF U801062

    1.This PTF allows <submit> of audio file to web server when
      audio file is zero length.
      (APAR IY64878)

    2.A change has been made to ensure that the URI in any fetch
      request is passed as-is to the webserver without any
      characters being removed.
      Also modifications have been made to the VXML2 cache
      implementation to ensure that the filesystem usage is
      properly managed.
      (APAR IY64747)

    3.A fix has been applied to the speech recognition event
      queuing mechanism.
      (Defect 6728)

    4.Fixes possible timing issue on Windows platform where outbound
      dialer application can invoke makeCall() before system fully
      intitialised and cause startup sequence to enter a wait which
      will never complete.
      (Defect IC41850)

    5.This PTF improves tracing in audio import code
      (Defect 6735)

    6.Fixed the dtjconf export option to ensure that it does not
      generate a NullPointerException.
      (Defect 6736)

    7.Adds "ls -lRL $DTJ_HOME" to vrbeProblem collected files.
      (Defect 6737)

  • Update 4.2.0.31

    APAR IY59118 IY62794 IY62795 IY62796

    PTF U800456

    1.Correct a problem where process would incorrectly end initial
      tag processing
      (APAR IY59118)

    2.Correct browser cache management thread failing with
      java.lang.StringIndexOutOfBoundsException when zero length
      files found in cache. Without cache management cache may continue
      to grow in size.
      (APAR IY62796)

    3.Correct problem caused by cache filling up and process looping.
      (APAR IY62794)

    4.Correct problem where ArrayIndexOutOfBoundsException was
      incorrectly generated.
      (APAR IY62795)

  • Update 4.2.0.23

    APAR IY61425

    PTF U800030

    1.VXML2 voice reco error message has been corrected to prevent the
      possibility of a core dump.
      (APAR IY61425)

  • Update 4.2.0.17

    APAR IY60351 IY60355 IY60356 IY60358 IY603259

    PTF U499198 U499199

    1.This PTF fixes an issue with short timeouts in fetching a
      new page in VoiceXML 1.0.
      (APAR IY60351)

    2.Fixed an abnormal termination of the VRNode during a recognition
      engine failure.
      (APAR IY60355)

    3.Fixed a problem with the audio cache getting out of step with the
      file system where files were being deleted out of step on expiry.
      (APAR IY60356)

    4.Correct regression in browser
      (APAR IY60358)

    5.Improvements made to audio handling in VXML2 for zero length
      files.
      (APAR IY60359)

    6.This fix corrects a problem with activity monitoring in
      DTJ_VV_Logger
      (Defect 5137)

    7.This PTF fixes a very small timing window that allowed a VRBE
      application node to get stuck in a 100% CPU cycle, locking out
      other VoiceXML 2 applications running.
      (Defect 6679)

    8.Added a check to validate the requested number of NBest results
      is in bounds in the WVR Java API.
      (Defect 5679)

    9.Fixes java.lang.IndexOutOfBoundsException dump in Cisco Java API
      (Defect 6631)

    10.Cleaned up the error message presented when trying to run a
      VoiceXML2 application on the command line before the Node had
      been started.
      (Defect 5063)

    11.Fixed a reintroduced defect when using grammars in WVS which
      lead to unexpected browser termination
      (Defect 6637)

    12.Catch and correctly managing of a previously uncaught exception
      which occured when retreiving problematic voice or wav recordings.
      These recording are typically 0 bytes in length or simply do not
      exist. The browser will now receive SeverStateError controlled
      exceptions rather than the unmanaged exception.
      (Defect 6650)

    13.Fixed a very small timing window that allowed a VRBE application
      node to get stuck in a 100% CPU cycle, locking out other
      VoiceXML 2 applications running on that node.
      (Defect 6676)

    14.The Enabled=<Yes|No> flag in a CCXService definition in
      default.cff is now correctly read.
      (Defect 6536)

    15.This change corrects a problem where the CCXML session variable
      "startupmode" was not being set to "newcall" if the CCXService
      had been configured for singlecall mode.(i.e. when a new CCXML
      session is created for each new call arrival).
      (Defect 6585)

    16.This change fixes the condition where the phone context is being
      removed from the destination URI of a dialog.transfer CCXML message
      when a transfer is initiated from a VXML2 document.
      (Defect 6612)

    17.Added processing to support the callerid attribute on the
      CCXML <createcall> tag for the SIP protocol. Other protocols
      do not support this attribute.
      (Defect 6618)

    18.Fixed a problem where the hints attribute in CCXML document tags
      was being truncated when it was sent to the CHP process.
      (Defect 6648)

    19.Corrected a situation where far end hangup was not being
      detected in CCXML when a VoiceXML 2 dialog was waiting for
      user input.
      (Defect 6664)

    20.Fixed a problem with placing calls through CCXML in a SIP
      telephony environment where the destination URI was not being
      passed through correctly.
      (Defect 6691)

    21.Fixed a problem where phone number pattern matching in the NumToApp
      statement in default.cff was not working for non-CCXML applications.
     (Defect 6711)



VOIP_SIP Fixes



Fix Level 4.2.0.596 (PTF U861071 )
Fix release date: 20 Sep 2013
Status: Current
APAR Description
IV47994 Fixed a problem where the SIP stack was accepting calls with media properties that are unsupported. This causes WVR to attempt to stream to an invalid IP address/port.


Fix Level 4.2.0.586 (PTF U854154 )
Fix release date: 29 Aug 2012
Status: Superseded
APAR Description
IV25703 WVR was rejecting VoIP invites with a=sendonly in the SDP.
Internal Defect fixes
  • Fixed a problem where an unnecesssary 29805 VoIP SIP signalling process Internal Warning error was raised when setting the record route header. The error occurs in function SIPDialogImpl::setRecordRoute with an Unknown Error.
  • Fixed a problem that prevented MWI blind notification from working when using VoIP/SIP. The error seen is a 29805 VoIP SIP signalling process Internal Warning error from the DtSipNotify::createNotifyRequest with the message "Unable to create NOTIFY TO header" in DtSipNotify.C


Fix Level 4.2.0.583 (PTF U852417 )
Fix release date: 28 Jun 2012
Status: Superseded
APAR Description
IV22224 Fixed a problem where VOIP believes the record route information has been updated. This can cause the route headers to appear in the wrong order, which then leads to the SIP transfer operation failing.


Fix Level 4.2.0.579 (PTF U851652 )
Fix release date: 24 Apr 2012
Status: Superseded

APAR Description
IV18686 Fixed to allow for larger SDP sizes (now up to 2048 chars).


Fix Level 4.2.0.576 (PTF U850312 )
Fix release date: 15 Feb 2012
Status: Superseded

APAR Description
IV15423 Fixed an installation problem with the srv.init file so now it gets installed in the /home/dirTalk/sys_dir directory correctly. Before it installed in the /usr/lpp/dirTalk.VOIP_SIP/inst_root/home/dirTalk/sys_dir directory.

Internal Defect fixes
  • Some tracing of NOTIFY used some information from the SIP transaction. If the NOTIFY occurs without a proper transaction this can cause a crash. The trace now only occurs if the transaction is valid.
  • Stop MEDIA_CTRL_DTNA dropping into the wrong code path when VOIP is shutdown. This was causing error 29800 to be raised.
  • Remove a race condition in ES services used by VoIP. This race condition caused error 29106 from es_queue.
  • Remove 100rel from Supported header in outbound INVITE. This can cause the UAS to require 100rel and reliable responses. WVR currently doesn't support this. The result is the 101-199 response is resent until WVR CANCEL's the call.
  • Fixed a problem where WVR reports 29805 SIP signalling process error on setRecordRoute for messages that do not have a record route defined. This fix removes the erroneous warnings.


Fix Level 4.2.0.571 (PTF U848095 )
Fix release date: 11 Jan 2012
Status: Superseded

APAR Description
IV12531 Removed extraneous warning about No Content-Length Header, error ID 29805 when SIP is used UDP to transport RTSP messages.
IV09376 Fix MGCP error reporting in MEDIA_CTRL_DTNA to use base WVR rather than SIP.
IV11874 If during an attempted VOIP Consult call transfer, the original caller disconnects during a certain time period while the outbound call is being established then the following errors are logged and the channel used for the outbound call can become useable for subsequent incoming or outbound calls.

errorid 29806 sequence 40911 YELLOW errno 0
parms='voip_callfn.c'
'CLSgTransferCallInConsult' '11197' '1' '1' '6' 'Outbound Transfer Call not found.' '0'

followed by :

errorid 29815 sequence 40912 YELLOW errno 0
parms='voip_callfn.c'
'CLInvalidPrim' '6283' '1' '1' '6' '14' 'Invalid layer 3 primitive for this state/event combination' '11'

Over a period of time this may manifest itself as transfer failing to work as these unusable channels increase in number and are selected for transfer outbound call establishment.

Internal Defect fix
  • Fix prevents VOIP_MONITOR from coredumping if /tmp is cleared.


Fix Level 4.2.0.567 (PTF U844292 )
Fix release date: 9 Aug 2011
Status: Superseded

APAR Description
IV03693 Fix a problem with MakeCall to a IP address that exists but isn't running SIP. If the MakeCall is then stopped the SIP CANCEL request also can't be sent. This causes a loop of INVITE and CANCEL requests to be sent. If a CANCEL fails to send then this will be assumed to also cancel the original request. This problem is most likely to occur if the MakeCall is via a trombone.

Internal Defect fixes
  • Fix a problem on a 16 trunk system that can result in the following error:

    VoIP Media (UPA) Internal Failure
        sequence  = 372372  csec      = 30      error_id  = 29800  
        asi_id    = 1       appl_id   = 56      error_no  = -1    
        severity  = RED     vpd_discr = VAE     module_id = GENVAE
        assoc_cls = NONE    alarm_thr = 0       assoc_alm = 0      
        appl name = VOIP_SVC                                      

        parameter             type        parameter value
       --------------------  ----------  --------------------
       Function              string      main
       Message               string      undecoded (invalid) es primitive
       File                  string      dtnamain.c
       Line                  string      1242
       Parm1                 string      undecoded primitive 0xffffffff
       Parm2                 string
       Parm3                 string
       Parm4                 string

    and a subsequent failure to enable the trunks.
  • Fixed provisional responses for calls with a Require: 100rel.




  • Update 4.2.0.567

    APAR IV03693

    PTF U844292

    1.Fix a problem with MakeCall to a IP address that exists but isn't
      running SIP. If the MakeCall is then stopped the SIP CANCEL request
      also can't be sent. This causes a loop of INVITE and CANCEL requests
      to be sent. If a CANCEL fails to send then this will be assumed to
      also cancel the original request. This problem is most likely to
      occur if the MakeCall is via a trombone.  
      (APAR IV03693)

    2.Fix a problem on a 16 trunk system that can result in the following
      error:

      VoIP Media (UPA) Internal Failure
        sequence  = 372372  csec      = 30      error_id  = 29800  
        asi_id    = 1       appl_id   = 56      error_no  = -1    
        severity  = RED     vpd_discr = VAE     module_id = GENVAE
        assoc_cls = NONE    alarm_thr = 0       assoc_alm = 0      
        appl name = VOIP_SVC                                    

        parameter             type        parameter value          
       --------------------  ----------  --------------------            
       Function              string      main                            
       Message               string      undecoded (invalid) es primitive
       File                  string      dtnamain.c                      
       Line                  string      1242                            
       Parm1                 string      undecoded primitive 0xffffffff  
       Parm2                 string                                    
       Parm3                 string                                      
       Parm4                 string

      and a subsequent failure to enable the trunks.
      (Defect 37178)

    3.Fixed provisional responses for calls with a Require: 100rel.
      (Defect 37152)

  • Update 4.2.0.564

    APAR IV02064

    PTF U844100

    1.Added VOIP SIP support for tromboning between:
      1) RFC2833 to SIP INFO DTMF
      2) SIP INFO DTMF to RFC2833
      3) SIP INFO DTMF tp SIP INFO DTMF
      4) RFC2833 to RFC2833 (support already present)

      Add support for two SIP INFO DTMF content types:
      1) dtmf-relay
      2) vnd.nortelnetworks.digits
      (APAR IV02064)

    2.Register removed from ALLOW as we ignore it, INFO added to ALLOW as
      we support it, and 100rel added to Supported as we support it.
      (Defect 37141)

    3.Added Accept and Accept-encoding headers and in OPTIONS responses
      while in a call, as required in RFC 3261.
      (Defects 37143 37162)

    4.Now reject INVITES with no acceptable media types as 488 - not
      acceptable here, as per RFC 3261.
      (Defect 37144)

    5.Correctly report that we are busy with SIP messages when we have no
      channels available and in inbound call is attempted.
      (Defect 37145)

  • Update 4.2.0.561

    APAR IZ99472

    PTF U843516

    1.Allows "#" in FROM headers in VOIP SIP calls.
      (APAR IZ99472)


     2.Prevents WVR from including REFER in the ALLOW header when system is
      configured to not accept incoming transfer requests.
      (Defect 37084)

    3.Prevents WVR from attempting an INVITE when making calls to an
      invalid address.
      (Defect 37082)

    4.Refers with a Replaces parameter in the Refer-To header URI now
      return a SIP not implemented message rather than address incomplete
      message.
      (Defect 37080)


  • Update 4.2.0.558

    APAR IZ93175

    PTF U842217

    1.Fixed a issue where VOIPL3_SIP core dumped when under high load.
      (APAR IZ93175)

    2.Fixed an error causing SIP_RESPONSE_ADDRESS_INCOMPLETE to be sent
      unnecessarily when processing a REFER message.
      (Defect 37081)

    3.Fixed incorrect SDP messages when SIP OPTIONS received, and prevents
      errors being rasied when an OPTIONS message is received
    before a call
      is established.
      (Defect 37077)

  • Update 4.2.0.555

    APAR
    IZ91778 IZ92660 IZ92510

    PTF
    U840695

     1.This fix overcomes a 29806 error (VOIP signalling process call state
      machine error/Invalid phone number for called party IE) for a VOIP
      outbound call StateTable application if any of the the digits
      '*#ABCD' is set in the Phone Number parameter for a MakeCall action.
      Previously the outbound call would fail to proceed despite the Phone
      Number being unused in the call setup (for VOIP outbound calls the
      TO_HDR tag set by the application is used).  
      (APAR IZ91778)

    2.This fix overcomes a problem found with outbound VOIP_SIP calls when
      the target endpoint is reached via a single outbouund proxy. In some
      cases (e.g. if endpoint is using secure SIP i.e. transport=tls) an
      outbound call would fail to be established (because SIP ACK response
      to 200 OK was directed to the wrong ip address).
      (APAR IZ92510)

    3.Fix a problem when using the VOIP SIP stack against a specific
      ethernet adapter and that adapter is not the first adapter in the
      machine. The contact header is always filled out with the ip address
      of the first adapter in the machine. With the fix the contact is
      filled out with the ip address for configured adapter.
      (APAR IZ92660)


  • Update 4.2.0.550 - Fix Pack 2

    APAR IZ85734 IZ85731

    PTF U839629

    1.New features contained in this PTF
      * Support for SIP Registration - provides support for the SIP
        registration method described in RFC 3261.
      * New VoIP Signalling - Inbound Call Channel Allocation Method.
        A new Inbound Call Channel allocation option called "Allocate
        calls for D2IS" has been added to system configuration to control
        the channel used for DTNA based calls. This option is for use
        when using the Genesys-supplied D2IS custom server in a
        behind-the-switch Genesys Framework implementation.

      For further information on the Fix Pack 2 features please
      refer to the TechNote at the following URL:
         
    http://www.ibm.com/support/docview.wss?rs=761&uid=swg21449523

    2.This fix overcomes a possible VOIP yellow alarm 29805 error (VOIP SIP
      signalling process Internal Warning / Failed to create new
      callProvider object) which then leads to a failure to handle all
      subsequent inbound and outbound VOIP calls until WVR is restarted.
      Also fixed is a possible 29806 error (VOIP signalling process call
      state machine error / Could not add FINAL_RESPONSE tag to
      SL_CALL_DISCONNECT_IND: Too big) which can occur during a VOIP blind
      transfer.  
      (APAR IZ85731)


  • Update 4.2.0.519

    APAR
    IZ75568 IZ76479

    PTF
    U835666

    1.
    This fix overcomes a problem found with outbound VOIP SIP calls when
      the target endpoint is reached via two or more outbound proxies. In
      some cases (e.g. if endpoint is using secure SIP i.e. transport=tls)
      an outbound call would fail to be established (because SIP ACK
      response to 200 OK was directed to the wrong ip address)
      (APAR IZ76479).

    2.This fix overcomes an occasional 29805 error (VoIP SIP signalling
      process Internal Warning/connid not found) found during VOIP call
      transfers despite the transfer to the third party being successful.  
      (APAR IZ75568)

  • Update 4.2.0.514

    APAR
    IZ65932

    PTF
    U832498

     1.Fixed a problem in the construction of the 200 message in response to
      an incoming INVITE. The 200 media attributes can be incorrect if
      the last attribute present in the INVITE happens to be rejected.
      For example if the INVITE asks for audio and video. This was
      causing the video to be rejected (correctly) followed by the video
      being rejected a second time (incorrectly) and the audio being
      ignored (also incorrectly).

      In the failing case, the invite message would have included content
      like this when viewed in a network trace:

    Content-Length: 210

        v=0
        o=user1 53655765 2353687637 IN IP4 9.146.171.66
        s=-
        c=IN IP4 9.146.171.66
        t=0 0
        m=audio 6000 RTP/AVP 0
        a=rtpmap:0 PCMU/8000
        m=video 30000 RTP/AVP 34 99
        a=rtpmap:34 H263/90000
        a=rtpmap:99 H264/90000

      (APAR IZ65932)

  • Update 4.2.0.501

    APAR IZ62638

    PTF U829860

    1.This fix modifies the behaviour of a VOIP_SIP blind transfer if the
      called third party fails to answer (a timeout occurs waiting for a
      NOTIFY 200 SIP message). The Transfer Call action now returns
      SL_REPLY_NO_ANSWER instead of SL_REPLY_OUTBOUND_LINE_PROBLEM.
      After terminating the transfer (with TerminateCall action) an
      application transfer retry should behave as expected without
      generating a 29808 error (VOIP signalling process trunk state
      machine error - Could not get trunk initial state from the trunk
      SIT).
     (APAR IZ62638)


  • Update 4.2.0.473

    APAR IZ60116

    PTF U828063

    1.This PTF fixes a core dump in the DTNA code along with
      improvements to the DTMF detection.
      (APAR IZ60116)

  • Update 4.2.0.459

    APAR IZ50720 IZ52323

    PTF U825877

    1.This fix removes a problem which when making a TCP non blocking
      connect could, in rare circumstances, cause a VOIP crash.
      (APAR IZ50720)

    2.This fix restores the fix previously provided by APAR IZ43589
      (fileset dirTalk.VOIP_SIP version 4.2.0.452) but regressed by
      the fix for APAR IZ47300 (fileset dirTalk.VOIP_SIP version
      4.2.0.456).
      (APAR IZ52323)

  • Update 4.2.0.456

    APAR IZ42421 IZ47300

    PTF U824646

    1.This fix prevents a possible 29806 error with a VOIP blind transfer
      retry which follows a previous transfer that failed with
      OUTBOUND_LINE_PROBLEM because of a 30 second 'ring-no-answer'
      Atimeout. lso fixed is a possible 29815 error as a result of a
      caller hanging up  immediately before a VOIP transfer is attempted.
      (APAR IZ42421)

    2.This fix implements the following changes in WVR SIP support:
      a) Makes TCP socket access non-blocking to prevent permanent hangups
         if TCP session hangs
      b) Prevent hangup in state machine if switch does not respond
         with 200 OK
      (APAR IZ47300)

  • Update 4.2.0.452

    APAR IZ43589

    PTF U824353

    1.This fix helps prevent a possible hangup (HUP) return
      code with the Transfer Call action used with a blind or
      attended VOIP transfer.  Previously, depending on
      machine and application timings the return edge could
      vary between OK and HUP despite the transfer being
      successful.
      (APAR IZ43589)

  • Update 4.2.0.445

    APAR IZ40641

    PTF U823637

    1.This fix adds -a option to VOIP_MONITOR to allow SIP trace
      to be put to AIX trace.
      (APAR IZ40641)

  • Update 4.2.0.440

    APAR IZ37950

    PTF U822402

    1.This fix adds additional SIP URI parsing for outbound calls.
      (APAR IZ37950)

  • Update 4.2.0.432

    APAR IZ33913

    PTF U821504

    1.This fix adds support for the SIP OPTIONS message in an
      out of call context where it is used as a 'heartbeat'
      message or to query media capabilities. An SDP body
      containing the current media (i.e. codec) settings is
      returned on the OPTIONS as per RFC3261.
      This fix also adds a couple of additional valid formats
      to the URI parser for outbound SIP messages.
      (APAR IZ33913)

  • Update 4.2.0.418

    APAR IZ26674 IZ25818

    PTF U819605

    1.This fix adds additional formats to the SIP URI parser.
      (APAR IZ26674)

    2.This fix correct WVR SIP operation when a Notify 487 is
      received during a SIP transfer operation.
      (APAR IZ25818)

    3.This fix corrects a problem handling the maddr parameter
      when received on a SIP Route header. Also corrects handling
      of Record-Route and Route headers for loose and strict
      routing.
      (Defect 36405)

  • Update 4.2.0.413

    APAR IZ24154

    PTF U819348

    1.This PTF corrects a problem which could have led to
      an incorrect RTP address being used in a SIP call.
      It also adds the ability to reject a call if less than a
      certain number of CHPS are available and also the
      ability to allocate incoming calls to WVR internal
      channels 'round robin' rather than using the highest
      available channel.
      Details of this fix are also documented in TechNote
     
    http://www.ibm.com/support/docview.wss?rs=761&uid=swg21313406
      (APAR IZ24154)

  • Update 4.2.0.408

    APAR IZ24001

    PTF U818988


    1.Tighten requisite filesets.
      (APAR IZ24001)

  • Update 4.2.0.367

    APAR IZ21161 IZ21283

    PTF U817185

    1.Corrects a problem which can cause a SIP Layer 3 core dump
      if a SIP CANCEL is received whilst still processing the
      corresponding INVITE.
      (APAR IZ21161)

    2.This defect corrects some warning errors which occurred
      when doing call transfers using SIP REFER/REPLACES with
      Cisco CallManager 6.1
      (APAR IZ21283)

  • Update 4.2.0.361

    APAR IZ17691

    PTF U817082


    1.This PTF contains updates for future enhancements to DTTA
      operation.
      (APAR IZ17691)

  • Update 4.2.0.357

    APAR IZ17310

    PTF U817030

    1.This PTF fixes memory leak in SIP Blind Notify
      (used for Message Waiting Indications)
      (APAR IZ17310)

    2.This PTF fixes core dump processing ACK to SIP CANCEL
      (Defect 36339)

  • Update 4.2.0.356

    APAR IZ16616

    PTF U816799

    1.Correct calculation so that VOIP starts if
      /var/tmp has greater than 4GB of free space.
      (APAR IZ16616)

  • Update 4.2.0.348

    APAR IZ14870

    PTF U816101

    1.This fix allows WVR to recover from DTEA port 'Out of Service'
      conditions which may result from a message timing condition at
      call hangup.
      NOTE This fix requires fix level 4.2.0.349 also.
      (APAR IZ14870)

  • Update 4.2.0.345

    APAR IZ12639

    PTF U815936

    1.SIP Enhancements

      Adds following funtionality to WVR SIP support as follows;

      a) Support SIP Session Timer as defined in RFC 4028. Several
         new System Parameters in SIP group are provided to enable
         and configure Session Timer.

      b) Support outbound DTMF using SIP Info method. Configured using
         new value for 'Outbound DTMF Method' in DTEA/DTNA Media system
         parameter group.

      c) Support SIP Subscribe/Notify for UM Message Waiting notification.
         Requires UM 'IMC_Subscribe' custom server to be activated.

      d) Various other minor enhancements to improve softswitch and gateway
         support

      Refer to the 'SIP-specific section' in the 'WVR for AIX V4.2 -
      Voice over IP using Session Initiation Protocol' manual for more
      details.
      Link to the
    WVR for AIX, V4.2 library here.
      (APAR IZ12639)


  • Update 4.2.0.322

    APAR IZ08694

    PTF U815175

    1.The fix allows WVR to accept SIP re-Invites with delayed
      media within a call. It also corrects the processing
      of RecordRoute and Route headers.
      (APAR IZ08694)

    2.This fix corrects a problem where the RFC2833 (RTP Payload)
      payload type (usually 101) was missing on the SDP offer
      for an outboung SIP invite.
      (APAR IZ09225)

    3.Corrects problem in generated SDP when adding annexb=no
      for g729, no vad on outbound SIP invite.
      (Defect 36240)

  • Update 4.2.0.286

    APAR IY99568

    PTF U811972

    1.This update enhances WVR SIP by adding support for the following:

       - P-Asserted-ID Header : used to pass proxy-authenticated
         'calling' number
       - Remote-Party-ID : ditto (older alternative to P-Asserted-ID)
       - Privacy header : used to indicate suppression of calling
         party number
       - Handling of multiple diversion headers to pass Original Called
         and Last Redirecting numbers in SV187 and SV188
       - Support for system parameter to allow presentation of
         calling number when restricted
       - Extraction of above headers into SV542 tagged string on
         incoming calls
       - Generation of headers from SV541 tagged string on outbound
         calls
       - Support for latest SIP 'caller on hold' method
       - Configurable removal of E164 leading digits (starting with '+')
       - Support for SIP early media (no SDP offer on incoming INVITE,
         WVR responds with offer on 200 OK).
      (APAR IY99568)

  • Update 4.2.0.276

    APAR IY97735

    PTF U811641


    1.This fix contains the VOIP part to correct clocking operation
      for mixed DTTA/DTEA systems.
      See fix level 4.2.0.275 for full details of fix.
      (APAR IY97735)

  • Update 4.2.0.265

    APAR IY94651 IY96336

    PTF U811215

    1.This fix will add a line a:fmtp:18 annex=no to any
      SIP SDP generated by WVR (send offer or answer) for
      the G729A codec (currently only on DTEA) when Voice
      Activity Detection is set OFF for G729A. This will
      partially prevent a mismatch of G729A anexb
      (voice activity detection) between WVR and the
      remote SIP endpoint
      (APAR IY94651)

    2.This defect adds support for the maddr parameter on
      SIP URI's as per RFC3261.
      It also allows a non-numeric parameter to be present in
      the user part of a SIP URI when extracting called and calling
      numbers for passing in SV185/186.
     (APAR IY96336)

    3.Correct variables and messages used by import check
      routines.
      (Defect 36074)

  • Update 4.2.0.249

    APAR IY92940

    PTF U810900

    1.The fix allow the version (v=) field to be located in any
      line of the SDP. This is needed because some ISDN/SS7 gatweways
      insert ISUP information prior to the SDP itself.
      (APAR IY92940)

  • Update 4.2.0.240

    APAR IY92115

    PTF U810590

    1.This fix corrects a problem with WVR SIP support where a
      re-invite to put media on hold caused a SIP BYE to be sent.
      (APAR IY92115)

    2.This defect will change SIP behaviour to always extract the
      SIP Request Header (REQ_HDR) into tagged string and SV542 on
      an incoming call regardless of the setting of the
      'Use Request Header' sysparm.
      (Defect 36046)

  • Update 4.2.0.215

    APAR IY85995

    PTF U808513

    1.Improve relibility of voip trunk disable during heavy
      call load.
      Improve SIP tracing with inclusion of message direction
      and corrected timestamps.
      Ability to extract SIP request header and select app profile
      based on it.
      (APAR IY85995)

    2.Added files to allow import check during WVR start up.
      (Defect 35953)

  • Update 4.2.0.212

    APAR IY84995

    PTF U807572

    1.Remove potential deadlock from SIP stack during a timeout
      (APAR IY84995)

    2.Add throttling code to the DTNA and SIP stack. This is to
      prevent the DTNA using more than (theoretically) 15ms of
      the 20ms processing cycle. At 15ms and above the SIP stack
      will start rejecting incoming SIP calls. Every 1000 rejected
      calls a warning will be generated to inform that this is
      happening. Ideally the system should not be driven at a call
      load higher than is possible to process.
      NOTE
       dirTalk.DT.rte fileset must be at fix level 4.2.0.211 as well
      (Defect 35922)

    3.This fix adds the EVENT header to outbound NOTIFY messages
      for MWI EVENT: message-summary.
      (Defect 35909)

    4.Stop auto forcing the signalling to VoIP if the signalling
      type is not CAS for DTEA/DTNA trunks.
      (Defect 35908)

  • Update 4.2.0.201

    APAR IY81677

    PTF U806945

    1.Add support for Virtual Adapter ( adapterless DTNA) solution.
      For VOIP fileset.
      (APAR IY81677)

  • Update 4.2.0.140

    APAR IY74570

    PTF U804343

    1.This fix improves the return codes passed back to
      applications making a VoIP supervised transfer call,
      allowing application to manage errors such as no answer,
      busy etc.
      (APAR IY74570)

  • Update 4.2.0.126

    APAR IY72487 IY72841

    PTF U803996

    1.This fix corrects an error where the branch ID on an
      ACK message confirming a 2XX response to an INVITE was
      not unique.
      (APAR IY72841)

    2.Modify the INVITE so that we don't add our own Route header.
      Any existing route informaiton will be retained.
      (APAR IY72487)

  • Update 4.2.0.73

    APAR IY68498

    PTF U802526

    1.This fix now allows voip numeric tel numbers to
      conatain a +.
      Eg +12345@bob.uk.ibm.com   will arrive in the application
      called number as  +12345. This will allow vxml applications
      to be selected based on a number type of +23445 using the
      NumtoApp field.
      (APAR IY68498)

  • Update 4.2.0.41

    APAR IY63806

    PTF U800662

    1.Problem found with VOIP call transfer, the referred-by header did
      not have the "sip:" string at the start of the header.
      (APAR IY63806)

  • Update 4.2.0.21

    APAR IY60974

    PTF U800024

    1.This PTF fixes a SIP attended transfer problem found after running a
      long term test.
      (APAR IY60974)

    2.This PTF fixes a SIP blind transfer problem found after running a
      long term test.
      (Defect 35223)

    3.Fix to ensure w1 timer stop occurs in request failure for on-hold,
      and fix invite failure in farend-hup.
      (Defect 35201)

    4.This PTF problem which stops channels being occasionally left in a
      blocked state when a quiesce command is issued.
      (Defect 35172)

    5.This PTF fixes a SIP attended transfer problem found after running a
      long term test.
      (Defect 35110)

    6.This PTF fixes an error burst generated by the SIP
      MEDIA control process when re-cycling trunks.
      (Defect 34957)

    7.Fixed a bug affecting SIP over TCP where if the far end unexpectedly
      closes the connection then the WVR SIP signalling process can
      terminate unexpectedly.
      (Defect 34940a)

    8.Fixed a bug which sometimes caused quiescing of VOIP channels
      to fail.
      (Defect 34826)

    9.Fixed a memory leak which could occur if WVR fails to send a
      blind MWI NOTIFY message.
      (Defect 34715)

  • Update 4.2.0.18

    APAR IY60260

    PTF U499201

    1.Fix to correct passing up of SIP headers to WVR Applications
      when diversion header is included.
     (APAR IY60360)

  • Update 4.2.0.11

    APAR IY58368

    PTF U498796

    1.This fixes a number of problems found in the SIP
      attended transfer feature. SIP attended transfer is based
      on the refer replaces method.
      (APAR IY58368)

    2.This fixes a problem when running SIP without a proxy.
      The FROM header was overwriting the request header.
      (Defect 35057)

    3.This fixes a problem in pack configuration which could lead
      to incorrectly configured trunks.
      (Defect 34889)

    4.Fixed a problem where two instances of VOIP_MONITOR could be
      run concurrently.
      (Defect 34921)


Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Voice Response for AIX
WebSphere Voice Response

Software version:

4.2

Operating system(s):

AIX

Software edition:

All Editions

Reference #:

1253844

Modified date:

2013-11-07

Translate my page

Machine Translation

Content navigation