< Back To CSTADLL Support
CSTADLL Change Log
CSTADLL 2.5.0
- New functional release. See the Release Notes or the README.html file for descriptions of the
functional enhancements included in this release.
CSTADLL 2.4.0
- New functional release. See the Release Notes or the README.html file for descriptions of the
functional enhancements included in this release.
CSTADLL 2.3.4
- Added a MonitorStart() signature and a MonitorStopAtNumericDevice() method
for BER phase 3 that accept a longword device number.
- Fixed an issue that could cause invalid license denials when using a floating
license.
CSTADLL 2.3.3
- Fixed a problem where a connection to an RLM license server was not cleanly
terminated.
- Fixed a couple of problems that could potentially cause unpredictable
behavior in regard to license checking.
- Fixed a looping problem when trying to connect to a Unify OpenScape Voice.
- Dealt with invalid XML in the Unify OpenScape Voice's responses to session
management messages.
- Corrected a flaw in the format of SystemStatusResponse messages.
- Fixed a problem in which CSTADLL would not send SystemStatusResponse messages
to XML Edition 5 or XML Edition 6 PBX devices.
- Changed the logging of the SystemStatusResponse message that is sent to XML PBX
devices that send a SystemStatus immediately after a connection so the message
is logged as XML text rather than hex bytes.
- Fixed a problem in which the PBX model would sometimes be incorrect in the log
file.
- Changed the logging of the two-byte XML header so it's logged as two hex bytes
instead of two ASCII characters.
CSTADLL 2.3.2
- CSTADLL will now search for an osyslic.txt file if it doesn't find a .lic
file.
- Fixed a problem where a .lic file would not be found even though it was in
the same folder as the .exe file.
CSTADLL 2.3.1
- Fixed a problem that caused invalid license check failures to occur.
- Fixed a false positive that would be returned by the GenericCSTA classes if the
MakeACSEAssociation() method was called and the length of the response message was zero.
- Fixed a problem that caused documentation for the Constants class not to get
generated.
- Fixed a problem that could cause a "no such host is known" exception to be thrown when
sending a message to the PBX or UA.
- Fixed a problem that caused some assembly version numbers shown in the Details tab of the
file Properties display to be either incorrect or all zeroes.
CSTADLL 2.3.0
- New functional release. See the Release Notes or the README.html file for descriptions of the
functional enhancements included in this release.
CSTADLL 2.2.4
- Added a phase 1 DivertCall() signature that takes a ConnectionID as an argument.
- Added a phase 1 QueryDevice() signature that takes a QueryDeviceFeature as an argument.
- Added a Connected property to PBXSession that indicates whether a connection is active.
CSTADLL 2.2.3
- Fixed a problem that could cause invalid license check failures.
- Modified the XML MonitorStartStop sample so it shows how the event message can be
decoded.
CSTADLL 2.2.2
- Fixed a problem that could cause "invalid call id" errors to be returned when using the
SingleStepTransfer() method that accepts a SingleStepTransferInfo object. The error
would be returned with Siemens Hipath 3000 or Unify OpenScape X5 PBX devices if the
TransferringCallID member of the SingleStepTransferInfo object contained the hex digit F.
- Modified unlimited distribution kits so deploying a special license file to unlock the
software for unlimited use is no longer necessary.
- Fixed a potential licensing problem that could occur if callers used just the generated
classes and not the helper classes.
- Fixed a problem in the C# client and the CallMan application in which a response from a
Snapshot Device operation would be incorrectly decoded.
- Added an AlternateCall() helper method for phase 3.
- Added a ConferenceCall() helper method for phase 3.
- Added GetLogicalDevInfo() and GetPhysicalDevInfo() helper methods for phase 3 BER.
- Added the ability to define a system status callback that will be called if a System
Status Request message is received from the PBX. The invocation of the callback is just
for notification purposes. The client application should not send a System Status Response
message; that message is sent automatically by CSTADLL.
- Added the ability to define an asynchronous exception callback that will be called if the
asynchronous I/O handling code detects an exception condition. If this callback isn't defined,
the I/O handling code will throw an exception, which was always the behavior before.
CSTADLL 2.2.1
- Fixed a null reference exception in the GUI VB client that could occur with unifyopenscapex5
PBX devices.
- Handle the situation where a PBX sends a system status request immediately upon receiving
a connection from an application.
CSTADLL 2.2.0
- New functional release. See the Release Notes or the README.html file for descriptions of the
functional enhancements included in this release.
CSTADLL 2.1.3
- Added three new MakeACSEAssociation() signatures to the SiemensCap class.
- Added a new MonitorStart() signature that accepts a ConnectionID object.
- Added two new SetAgentState() signatures for phase 3.
CSTADLL 2.1.2
- Fixed a problem that would cause an exception to be thrown if an ACSE message was received
after CSTA communication had started.
- Added a SnapshotCall() signature for phase 3.
- Fixed an exception in the Open() method for Panasonic PBX devices.
- Fixed a problem where the VB client would not identify the Alcatel OXO as a phase 1
device.
- Added support for the Philips Sopho PBX device.
- Fixed a problem that could cause an exception in CallMan if the configuration is
changed.
CSTADLL 2.1.1
- Added the AlcatelOXE class, which was documented as part of v2.1.0 but was not included.
- Added the DebugClientCallback property to the PBXSession class. If set to true, this property
will enable easier debugging of client callback methods by delaying the read for the next
message from the PBX until after the client callback has completed. The default value is
false, meaning the read for the next message will occur before the client callback is executed.
- Added the MaxReceiveTimeout property to the PBXSession class. This property specifies the amount
of time (in milliseconds) to wait for a response to come back from the PBX. The default is 5,000
milliseconds (5 seconds).
- Fixed a bug that could cause a deadlock if a monitor event message arrived while the same thread
was waiting for a synchronous response to another monitor start request.
- Fixed a bug that could cause an exception if a PBX rejected a message.
- Added the GetAgentState() method for phase 3.
- Added a MakeACSEAssociation() signature that accepts a username and password to the
SiemensHipath3000p3 and UnifyOpenscapeX5 classes.
CSTADLL 2.1.0
- New functional release. See the Release Notes or the README.html file for descriptions of the
functional enhancements included in this release.
CSTADLL 2.0.5
- Fixed an exception that could occur if the PBX sends a Route Request message.
CSTADLL 2.0.4
- Changed MakeCall() for Alcatel so it specifies the (vendor-specific) autoOriginate option.
- Changed the sample clients so the Answer Call functionality works properly if the response
to MakeCall() includes a ConnectionID with a dynamic deviceID.
CSTADLL 2.0.3
- Fixed a problem where the AnswerCall() method might not properly format the message.
- Fixed a problem where partially complete network read requests were not properly handled.
- Performance improvement. Some processing specific to logging was being done every time a
monitor packet was received, regardless of whether logging was enabled. This processing is now
done only if logging is enabled.
- Fixed a problem where phase 2 Make Call Result messages may not be properly decoded by the C# and VB
sample clients.
CSTADLL 2.0.2
- Fixed a problem where the Makefile provided with the samples was not copying required DLLs into
the sample folder so the .exe built by the sample could run.
- Fixed a problem where the logging of a CSTA message's ROSE header showed the CSTA payload as
being the entire message, including the ROSE header, instead of just the CSTA portion of the
message.
CSTADLL 2.0.1
- Fixed a problem with the ACSE Make Association operation for Siemens Hipath 4000 PBX devices.
- Fixed a problem in which the response to an ACSE Make Association request was mis-identified in
the log file with the label "ROSEHeader".
- Revised the DLLCsMakeCall sample so it shows how to isolate the connection id of the call that
was made.
- Fixed a problem in which the response to an ACSE Release Association request was incorrectly
logged, and a garbage message was returned as the response. The connection with the PBX is
now closed immediately after a Release Association message is sent, and the ReleaseACSEAssociation()
methods now return null.
CSTADLL 2.0.0
- New functional release. See the Release Notes or the README.html file for descriptions of the
functional enhancements included in this release.
CSTADLL 1.3.3
- Added an AlcatelOXOp1 class to allow phase 1 communication with an Alcatel OXO.
- Added a ConsultationCall() method to the GenericCSTAp3 class.
- Added a TransferCallAfterConsult() method to the GenericCSTAp3 class.
CSTADLL 1.3.2
- Fixed a problem with the ACSE Make Association message for Alcatel 4400 devices.
- Fixed an exception in the DLLCsMonitorStartStop sample.
- Renamed the existing DLLCsMonitorStartStop sample to DLLCsMonitorStartStopPhase2.
- Added a new DLLCsMonitorStartStopPhase3 sample.
CSTADLL 1.3.1
- Corrected some problems that could cause the phase 3 TransferCall() method not to work.
- Corrected some problems that could cause the phase 3 AnswerCall() method not to work.
- Corrected some problems that could cause the phase 3 GetSFDevices() method not to work,
particularly with Panasonic PBX devices.
- Changed the sample VB and C# clients so phase 3 stop monitor works against the most recently
started monitor, and phase 3 answer call and transfer call work against the most recently
made call (done with make call).
CSTADLL 1.3.0
- Corrected a problem in which the MakeCall() method would not work properly with Panasonic
PBX devices.
- Corrected a problem that could cause log file corruption and/or key not found exceptions.
CSTADLL 1.2.2
- Corrected a problem in which the call id field of a Single Step Transfer message sent to a
Siemens Hipath 3000 PBX was improperly formatted.
- Changed the TCP/IP connecting logic so it ensures it's making an IPv4 connection.
- Corrected a problem in which an exception would occur if a PBX rejected a Get Switching
Function Devices operation.
- Corrected a problem in which an exception could occur if a PBX closed a session
immediately after sending a response message.
CSTADLL 1.2.1
- Corrected a missing source file problem in the CSTAAllPhasesConsole C# project.
- Corrected a memory management bug that could cause a TCP/IP receive buffer to be too small.
- Corrected a bug with the MonitorStartStop sample.
CSTADLL 1.2.0
- Corrected a bug with the ACSE Make Association message format for Panasonic devices.
- Corrected a bug with the phase 3 GetSFDevices() method's handling of the responses.
- Added a MonitorStartStop sample.
- Added a MonitorStop signature that takes a MonitorCrossRefID object instead of an int.
CSTADLL 1.1.3
- Added missing file Common.cs to the product kits in the csharpclient folder.
- Added a PanasonicNCP convenience class for the Panasonic NCP PBX device.
CSTADLL 1.1.2
- Fixed a problem in the console-mode client that would cause it to specify the
same device for both the calling device and the called device when doing a
MakeCall.
- Added a LoggingFolder property to the PBXSessionHelper class that allows the
caller to specify a folder to receive log files. If no value is specified for
this property, the behavior is as before; i.e., a log file gets placed into the
same folder as the .exe that is using the all-phases DLL.
- Modified the formatting of the ROSE header for CSTA messages so the integer
imbedded within the InvokeId object is incremented each time a message is sent
out, within the life of the control object.
CSTADLL 1.1.1
- Improved the sample clients so they detect if an ACSE connection has not yet been
made when a CSTA operation is attempted.
- Incorporated Panasonic ASN.1 definitions into the Panasonic support.
CSTADLL 1.1.0
- Added support for sending text to a telephony device controlled by a phase 3 PBX.
- Added support for ringing a telephony device controlled by a phase 3 PBX.
- Added support for manipulating the message waiting indicator of a telephony device
controlled by a phase 3 PBX.
- Added support for acquiring and releasing the right to control a telephony device
to the Panasonic KX-TDA and KX-TDE classes.
- Added phase 3 support for starting a data path, stopping a data path, and sending
data using a data path.
- Fixed a couple of bugs in the logging mechanism that could cause incomplete message
logging.
CSTADLL 1.0.5
- Improved the "no response received from PBX" message.
- Fixes to the formatting of the ACSE make association message for the Siemens Hipath 3000.
CSTADLL 1.0.4
- Improved license exception handling.
- Fixed a problem with the encoding of the monitor stop message.
CSTADLL 1.0.3
- Changed C# console so quit works even if release ACSE association fails.
- Improved handling of asynchronous system status requests.
- Improved handling of several specific PBX devices.
CSTADLL 1.0.2
- Enhanced the logging to log the PBX device type.
- Improvements in the support for Alcatel and Siemens Hipath 3000 devices.
- Improvements to license checking for users who want to use only the generated classes.
CSTADLL 1.0.1
- Changed the Alcatel 4400 device from a phase 3 device to a phase 2 device.
- Improved the handling of license exceptions.
- Improved error handling in the C# client.
- Improved timeout handling.
- Added a logging mechanism.
CSTADLL 1.0.0