
CA Nortel Changelog -- Branch CANortel_Rel_1_0_1
====================================================================================================


Restrictions:
=============
* CSTA Call Control and Forwarding/DND Services require a monitor in order to be requested. 

* MakeCall Service:
  All MakeCall requests are handled as doNotPrompt request, the autoOriginate parameter in the
  request will be ignored.

* SetForwarding Service:
  forwardImmediate is the only supported forward type. Requests containing other forwardingTypes
  will be rejected with an operation/invalidForwardingType CSTA Error message.

* SnapshotDevice Service:
  SnapshotDevice always replys with an empty response, even if a forward is actually set. This is,
  because some clients do not work in some features if SnapshotDevice is not supported at all, but
  do work if SnapshotDevice is supported but does not retrieve any device information.
  
* Transfer Service:
  No events will be generated for a monitored 'Transferred Device'.
  

History:
========


--- !!! ------------------------------------------------------------ !!! ---
--- !!!                                                              !!! ---
--- !!! PLEASE NOTE:                                                 !!! ---
--- !!! This file is located on branch "CANortel_Rel_1_0_1".         !!! ---
--- !!! This is the branch on which current development takes place. !!! ---
--- !!! The trunk is currently not in use.                           !!! ---
--- !!!                                                              !!! ---
--- !!! ------------------------------------------------------------ !!! ---


Version 1.0.3.2 (tag: CANortel_Rel_1_0_3_2, built: March 23, 2016)
- #8465: (Resolved): blockiertes Callmodell nach Rückfrage auf besetzte Nebenstelle mit
         auto-hangup nach 15 Sekunden.


Version 1.0.3.0 (tag: CANortel_1_0_3_0, built: -)
- #6779: Support for Alternate, Hold, Retrieve.


Version 1.0.2.0 (tag: CANortel_1_0_2_0, built: December 9, 2015)
- #8057: (Resolved) nach beendeter Consultation blocked call model wegen fehlendem
         ConnectionCleared: State Modell wurde erweitert, dass bereits bei ST_DISCONNECT ein
         ConnectionCleared event gesendet und der Call aus dem Model entfernt wird.
- Synchrone Meridian-Link-Responses werden nun auch im Log dekodiert protokolliert.


Version 1.0.1.10 (tag: CANortel_1_0_1_10, built: June 24, 2015)
- #7852: FEAT: Sikom prefers signaling of DeliveredEvent instead of QueuedEvent for ACD Queue.
         To activate this feature, use Java System Property:
         de.ilink.cti.meridianlink.ca.masqueradeQueuedAsDelivered=true
         Under Windows, the CA Nortel service takes its parameters from the registry, so this
         value should be set there.
       - Corrected logic: fMasqueradeQueuedAsDelivered.


Version 1.0.1.9 (tag: CANortel_1_0_1_9, built: April 22, 2015)
- Added comments, minor changes in debug output.
- #7479 / #7724: Corrected bugfix: Die Änderung hatte einen Seiteneffekt auf andere Call Flows,
         mindestens ReconnectCall. Nun ist die Änderung scharf auf das fehlerhafte Kundenszenario
         beschränkt.
- #7367: Set Eclipse project to use JRE 4 compiler compliance.


Version 1.0.1.8 (tag: CANortel_1_0_1_8, built: April 21, 2015)
- #7479: Corrected bugfix: used containsKey() (correct) instead of contains() (wrong).


Version 1.0.1.7 (tag: CANortel_1_0_1_7, built: April 21, 2015)
- Minor code formatting.
- Added comments.
- Fixed typo in readable description of ST_TRANSFER_COMPLETE state.
- Fixed typos in debug output.
- #7479: Fixed a bug that caused calls to hang if their end was signaled only by a Meridian
         ST_DISCONNECT event without a previous ST_ONHOOK event.


Version 1.0.1.6 (tag: CANortel_1_0_1_6, built: March 24, 2015)
- #7417: Added support for queued events in outbound calls. A call state change to the Nortel state
         CONN_STAT_WAITING_IN_ACD_QUEUE will now cause a CSTA Queued event to be generated.
- Minor code formatting.


Version 1.0.1.5 (tag: CANortel_1_0_1_5, built: May 9, 2014)
- Minor build process change to adapt to renamed Changelog.txt.
- Added UnitTest to verify conference scenario.
- #7132: fixed - [CallModel] Fehler nach Auflegen von ConferenceCall.


Version 1.0.1.4 (tag: CANortel_Rel_1_0_1_4, built: January 7, 2014)
- #6824: fixed - RedirectOnNoAnswer after TransferOnAlerting causes calls to remain in the call
         model.
- #6779: ConsultationCall mit ConsultOption conferenceOnly fuer ConferenceCall Request.
- Renamed Release Notes.txt to Changelog.txt.


Version 1.0.1.3 (built July 26, 2013)
- #6823: fixed - Transfer on alerting can't be executed.


Version 1.0.1.2 (built March 3, 2009)
- Issue 4335 fixed: SF responses to CF System Status Request services and 
  SF System Status notifications are synchronized now.
  This issue has been solved by extending the lock scope of CAState methods 
  (that trigger the sending of CSTA XML messages to the Client) to a message 
  queue (according to RFC 182 Option 4a for further details).
  ilink_csta_xml_server.jar has been upgraded to version 1.0.0.0, which 
  includes a message queue.
  

Version 1.0.1.1 (built October 16, 2008)
- JUnit Testenvironment (CATests.jar) upgraded to CATests_Rel_2_2_0_0,
  nigthly tests with testreport generation using luntbuild is supported now


Version 1.0.1.0 (built September 9, 2008)
- Forwarding and DND support implemented according to RFC 172
- Meridian Link Codec library (meridianlink.jar) upgraded to 1.4.1.0
- CSTABean library (CSTABean.jar) upgraded to 4.2.2.6


Version 1.0.0.23
- Generic transport layer updated to version TransportLayer_Rel_0_9_4_1

Version 1.0.0.22
- Upgraded to MeridianLink.jar 1.1.0.2 - this fixes several bugs:
  * CallOffered event InformationElements are not supposed to come in a 
    certain order any more
  * CallIds will be marshaled as 4 bytes 
- Upgraded to TCPIPComponents 0.5.0.0
- Upgraded to CATests 1.0.0.3
- Fixed NPE.
- Exceptions redirected to log4j (and not System.err).
- Added constraint that method shutdownCA() of CAStarter mustn't be obfuscated
  (now stop method can be called when CA service will be shut down).
- Bug fixed: sending messages to the csta client from different threads causes
             crunched messages sometimes  
- Refactored handling for putting data into CSTA messages.
- Changed calls in primary and secondary call tags in TransferredEvent for
  transfer controller.

Version 1.0.0.21 
- Documentation added.

Version 1.0.0.20 
- Bug fixed: Installation problem

Version 1.0.0.19 
- Bug fixed: Some "operation generic errors" have been signaled as  
  "operation service not supported" error

Version 1.0.0.18
- Installation routine changed 
   * VM exchanged to 1.4.2_10
   * no Java VM is needed at installation time anymore
   * installation log file will always be created
   * linux installation improved

Version 1.0.0.17
- CallIDs now in decimal format
- Bug fixed: in some cases System status normal was not signaled properly at 
  startup time

Version 1.0.0.16
- MR FNN4945 fixed: 
  TransferCalls do not provoke a zombie calls in the call model any longer.
  Two (or more) TransferCalls are now possible with the same monitor open.  
- AnswerCall, ClearConnection, ConsultationCall, ReconnectCall and TransferCall
  services with invalid connection call id parameters will result in a
  CSTAError response from now on

Version 1.0.0.15
- JRE 1.3 compatibility reassured

Version 1.0.0.14
- In conferenced Event 3 instead of 4 connections in connectionItemList
- In conferenced Event cause changed to conference

Version 1.0.0.13
- MR G45731(4) fixed: TransferCallResponse.transferredCall.deviceID filled
- MR G47046 fixed: CA now registered with unique (random) application id
- MonitoringStop now uses the coding type MonitorStart succeeded with

Version 1.0.0.12
- Install problem fixed: now it uses the 'reg.exe' provided by the install 
  package (addUninstaller.bat, removeUninstaller.bat) and removeUninstaller.bat 
  will be parsed (see izpack_installer.xml)

Version 1.0.0.11
- Missing Originated event added in manual dialing scenario
- Missing Delivered event (remote connection) added in manual dialing scenario
- Missing ServiceInitiated event added in consulting scenario
- localConnection state of a alerting connection is 'alerting' instead of 
  'connected' in the ConnectionCleared event now
- Dynamic device identifiers will only be used as Connection Device ID format. 
  No more Device Identifiers of the type 'dynamic'.

Version 1.0.0.10
- MR G43069 (extra DeliveredEvt and EstablishedEvt in MakeCall) fixed 

Version 1.0.0.9
- clean ML ApplicationRelease if CA shuts down implemented
- ML ApplicationReleaseIndication support added
- ML ApplicationReleaseResp which was not requested by the client will now be
  handled like a ML ApplicationReleaseIndication
- proprietary handling of pbx behaviour removed

Version 1.0.0.8
- SnapShotDevice (not officially supported) connection device id format changed 

Version 1.0.0.7
- Optional handling of some defined pbx behaviour added 

Version 1.0.0.6
- Bug fixed: CA initiated SystemStatus will no longer be sent before CSTA client
  is successfully authenticated 

Version 1.0.0.5
- CSTABean upgraded to 4.0.4.2
- CAP library renamed to ca_meridian1.jar
- Release notes and linux install scripts added 
- MR 3880: CA now reports SystemStatus (normal, initializing and enabled) to 
           the client

Version 1.0.0.0
- "1" will now accepted as valid activateForward attribute in the SetForwarding
  request (additionally to "true"). This fixes the SetForward problem in
  newer ComAssistant versions.
- CA state recovery improved: State will be corrected after missing events (e.g.
  after second line calls)
- CAP installation configuration files: jar file will now be copied from
  the distribution lib directory to the local lib directory
- standalone version with scc association now logs version information too

Version 0.2.3.0
- Now we only wait for really existent mediators to disappear 
- Message queue synchronization improved
- Bug fixed: reconnecting now possible when the lower layer goes out of service
             while waiting for a response of a connection attempt request
- CAP Installation: CAP Management Diagnostic Agent snapshot request will be 
  handled correctly now            

Version 0.2.2.0
- Bug fixed: CA should now reconnect after network problems 
- Bug fixed: Empty callback at connection layer now possible

Version 0.2.1.0
- SCC-CA association added for CAP version 
- CA logs it's version at loading time

Version 0.2.0.0
- CA is now startable as CAP service

Version 0.1.0.1
- cap commandline support (don't use this version!)

Version 0.1.0.0
- initial release


