CSTAStub v1.2

Release Notes

Contents

• Latest changes
  • Enhancements
  • Bug fixes
• Summary of changes

Latest changes

The version provided is CSTAStub v1.2.7.

CSTAStub v1.2.7 brings the following changes :

Enhancements

Bug fixes

• the workingAfterCall event was built with the old ASN.1 definition. It is now built with :
  WorkingAfterCallEvent ::= SEQUENCE {agentDevice SubjectDeviceID, agentID [10] IMPLICIT AgentID OPTIONAL, agentGroup AgentGroup OPTIONAL, cause EventCause OPTIONAL}.
• A ConsultationCall is not accepted if there is already two calls (one active and one held) involved on the device.
• A forward feature with the phone itself as the forwarded to device is accepted but it will be ignored at runtime.

Summary of changes

CSTAStub v1.2.6 brings the following changes :

Enhancements

Bug fixes

• the transferCallResult.transferredCall component was containing an old connections present in the call, it now contains a new connection in the resulting call (actually the transferredTo connection). This is more compliant with the CSTA phase II protocol.

CSTAStub v1.2.5 brings the following changes :

Enhancements

Bug fixes

• If properties have been changed to non default values and removed while the stub is running, they are not set to their default values after updating properties.
• In some situations (such as a new call arriving while the current phone is in the dropped_ondropped state), the phone stays busy.

CSTAStub v1.2.4 brings the following changes :

Enhancements

• WARNING : CSTAStub requests a JVM 1.5 or later.

Bug fixes

• If a request is not handled by CSTAStub, it did not return a correct answer and let it fail in timeout. The answer is now a ReturnError with an 'Operations.objectNotKnown' failure.

CSTAStub v1.2.3 brings the following changes :

Enhancements

• The Failed_dropped_onCaller timeout has been added to allow the control of the automatic drop by the caller if the call fails on the called party (because it is busy for example).

Bug fixes

CSTAStub v1.2.2 brings the following changes :

Enhancements

• The automatic call generation can be randomized or not. The randomized generation chooses pairs of phone contexts randomly which may lead to Failed events.

Bug fixes

• In case, device D2 is involved in a call C1 with D1. Device D3 calls D2 which fails. When D1 releases the call C1, the timer on device D2 was broken by the failing call which was leading to incorrect behavior : the ConnectionCleared (local connection state = null) event may be missing on D2.

CSTAStub v1.2.1 brings the following changes :

Enhancements

• Correlator data set in the MakeCall and ConsultationCall will be reported in the Delivered, Established, Diverted events sent on behalf of the called device.

Bug fixes

• The stub running process stopped after receiving some messages containing bad content (a bad called directory number in a MakeCall for example).
• A superfluous DeliveredEvent was sent on behalf of the device requesting a DivertCall.

CSTAStub v1.2.0 brings the following changes :

Enhancements

• The SetFeature forward and doNotDisturb operation are accepted. Only a single forward at a time is accepted (the next forward, even if of a different type, overrides the existing one). The behavior of the phone respects the active forwarding type if any.
• The DivertCall, HoldCall, RetrieveCall, ConsultationCall, ReconnectCall, TransferCall, ConferenceCall operations are accepted.
• The default behavior can be defined on a regular expression basis applied on the dialing number. This allows user defined default behaviors in addition to the default one.
• The generated reports can now be CSV or HTML reports.
• The server now has the ability to generate dynamicID or staticID for each ConnectionID device component. This may help an application to handle the various ways a ConnectionID can be filled according to the CSTA protocol.

Bug fixes

• The call identifier in the FailedEvent, ConnectionClearedEvent when a phone is receiving a call while busy was wrong.
• The count of events are properly reported per phone contexts.

CSTAStub v1.1.1 brings the following changes :

Enhancements

Bug fixes

• The cross reference id returned for number 'xyz' and 'xyz0' is the same (byte[] 'xy', 'z0'). This is fixed adding a 'F' digit in case the number of digits is odd, thus the cross reference id for 'xyz' is byte[] 'xy' 'zF' and for 'xyz0' it is byte[] 'xy' 'z0'.

CSTAStub v1.1.0 brings the following changes :

Enhancements

• The server answers a QueryDeviceArgument/forward with a default result containing an empty list of forward devices.

Bug fixes

CSTAStub v1.0.0 brings the following changes :

• First release.