Product: Corepoint Telephony SwitchServer/2 Seimens 9006
       Version: 6.2.0
         Level: V1863
      Platform: OS/2
          Date: 4 August 2000
  Service File: r6ss2.exe
          Size: 955106  (0.9Mb)
 
 
  Installation Instructions:
  --------------------------
    Download the self-extracting file, r6ss2.exe, into a temporary directory.
    Execute it from the command line and follow the prompts.
 
    If you answered "Yes" to the backup query and wish to
    undo the service update, issue the following commands:
 
      <installdrive>:
      cd \
      <backupexe> -Qdr
 
    where <installdrive> is the drive letter on which product is installed
      and <backupexe> is the full path name of the backup self-extracting file.
 
 
  Fixes contained in this Service Package:
  ----------------------------------------
 
       Name: PMR 66270
    Symptom: Calling party of a Routed event is empty.
    Problem: Incorrect logic if a call arrives at a RCG over a CorNet
             trunk, is transferred by the (CorNet) caller and then is
             queued by the RCG at more than 1 ACD queue.
   Solution: Code changes have been made to handle this case.
 
       Name: PMR 49671
    Symptom: Switch.exe crashes, msg 6003 (ERR_REQUEST_COMMBFR) in error
             log.
    Problem: If a call queues to more than 14 queues in parallel and the
             caller then clears, switch.exe tried to use more PCBs
             (PartyControlBlocks) than had been allocated.
   Solution: Allocate enough PCBs to handle this case.
 
       Name: PMR 16702
    Symptom: Events are missing when a hold-on-hold call recalls.
    Problem: It is possible for a call to have both parties holding each
             other (hold-on-hold). If one party then gets recall (starts to
             alert because another call they were on hung up), no events
             were sent.
   Solution: Code changes have been made to handle this case and send
             appropriate events.
 
       Name: Defect 7864
    Symptom: Originators phone doesn't autoanswer even though the Call
             profile as been set.
    Problem: An application can use the STLSAA (Set_Automatic_Answer) API
             to set the automatic_answer characteristic of a call profile
             to STL_ANSWER. This will cause party_one of a Make_call
             request to go off-hook automatically. A default was being
             assumed that is correct for CallBridge/CSA 3.1 and beyond, but
             not true for earlier versions of CallBridge/CSA.
   Solution: Code changes have been made to handle this case.
 
       Name: Defect 7945
    Symptom: The connect_reason is STL_CONNECT_NOT_SPECIFIED but should be
             STL_RECONNECT.
    Problem: When a connection moves from Held to Connect (i.e. is
             retrieved), a Call_Connected event flows, and should have a
             connect_reason of STL_RECONNECT.
   Solution: Code changes have been made to handle this case.
 
       Name: Defect 7909
    Symptom: Insufficient information in events to correctly track silent
             monitor calls
    Problem: When a supervisor silent monitors a connected agent, the
             Call_Connected event should have a connect_reason of
             STL_ADD_PARTY_RCV_ONLY. If the Agent is idle at the time the
             silent monitor is started, an extra Call_Connected event (with
             a connect_reason of STL_ADD_PARTY_RCV_ONLY) containing only
             the supervisor should be generated - it should flow after the
             supervisors' Setup event, and before the Held event. In both
             cases, when the Supervisor clears the silent monitor call, a
             Disconnected event should be generated for the agents'
             Connection_ID.
   Solution: Code changes have been made to handle these cases.
 
       Name: PMR 16513
    Symptom: Corrupt Program Data on incoming calls and trace/server crash
     Detail: If UUI (user-user-information) is received from the switch, it
             is presented to an application as ProgramData. This data is
             optional but if the data is received with zero length (unusual
             but legal), 2 problems occur:
              1. The Call will get 512 bytes of random
                 (probably all hex zeros) program-data
              2. If a switch trace is being displayed, either in realtime
                 or later, the attempt to format the data will fail
                 and crash the server.
   Solution: Code changes have been made to handle this case.
 
 
  Files contained in this Service Package:
  ----------------------------------------
    asn1.dll
    csacrcrt.dll
    hm.exe
    libcmnr.dll
    libpicom.dll
    prodinfo.msg
    readme.txt
    stt.dll
    switch.exe
    r6ss2.icf
    csm.exe
    engdebug.exe
    erarcsem.dll
    erarcut2.dll
    libasn1a.dll
    swchgr6.dll