Release Notes
May 10, 2017
www.xcapi.de
Release Notes
General Notices
Download
The current release of XCAPI can be found in the community under:
http://www.te-systems.de/community
Software Upgrade Service
In May 2012 we introduced our Software Upgrade Service (SUS) .
From XCAPI release 3.3.249 onwards licenses are now checked for a valid Software Upgrade Service.
Please find more information on our website XCAPI Software Upgrade Service respectively in the
XCAPI Price List.
Installation
During the first XCAPI installation only the voice-over-IP infrastructure needs to be configured
accordingly and can then be used straight away.
The latest XCAPI release can be installed on systems with older releases via the update function.
The existing configuration will not be changed and can be used as before after a system restart.
Technical Support
Should any problems or errors occur during the use of the current release, please send an
e-mail including an XCAPI trace and a detailed description of the technical environment to
[email protected].
How to create a XCAPI trace, will be shown in our video „XCAPI 08 - Create a trace“ on our
YouTube channel.
From XCAPI release 3.3.249 onwards licenses are now checked for
a valid Software Upgrade Service.
Please find more information on our website www.xcapi.de „Software Upgrade Service“ respectively in the XCAPI Price List.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
2
Release Notes
XCAPI Alterations
XCAPI Version 3.6.49 (March 14, 2017)
àà Internal release
XCAPI Version 3.6.48 (March 10, 2017)
àà Internal release
XCAPI Version 3.6.47 (February 20, 2017)
àà Internal release
XCAPI Version 3.6.46 (February 09, 2017)
àà Internal release
XCAPI Version 3.6.45 (February 07, 2017)
àà Internal release
XCAPI Version 3.6.44 (February 02, 2017)
àà Internal release
XCAPI Version 3.6.43 (February 01, 2017)
àà Internal release
XCAPI Version 3.6.42 (January 31, 2017)
àà Internal release
XCAPI Version 3.6.41 (January 16, 2017)
àà Internal release
XCAPI Version 3.6.40 (January 13, 2017)
àà Using G.729 audio codec does not require a licence anymore.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
3
Release Notes
XCAPI Version 3.6.39 (Dezember 22, 2016)
àà Fixed erroneous sending of process indicators and a possible error with reinitializing the driver.
XCAPI Version 3.6.38 (Dezember 01, 2016)
àà Internal release
XCAPI Version 3.6.37 (November 30, 2016)
àà Fixed a possible system crash that could occur with certain invalid registry entries.
XCAPI Version 3.6.36 (November 29, 2016)
àà Under certain circumstances the tranport protocol was reset to UDP during SIP sessions. Fixed.
XCAPI Version 3.6.35 (November 17, 2016)
àà CAPI applications now receive a Progress Indicator information element as soon as SDP is
received from a remote party for the first time.
XCAPI Version 3.6.34 (October 24, 2016)
àà Support for the line parameter in SIP URIs, improved handling of CANCEL requests.
XCAPI Version 3.6.33 (September 06, 2016)
àà Internal release
XCAPI Version 3.6.32 (September 05, 2016)
àà Improved robustness of the proxy failover mechanism.
XCAPI Version 3.6.31 (August 22, 2016)
àà Internal release
XCAPI Version 3.6.30 (August 05, 2016)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
4
Release Notes
XCAPI Version 3.6.29 (July 26, 2016)
àà Improved System ID detection in Azure Environments.
XCAPI Version 3.6.28 (July 25, 2016)
àà Internal release
XCAPI Version 3.6.27 (July 25, 2016)
àà Internal release
XCAPI Version 3.6.26 (July 04, 2016)
àà Internal release
XCAPI Version 3.6.25 (June 14, 2016)
àà Fixed an error, that inhibited Discontinued Transmission of media data with SIP connections.
XCAPI Version 3.6.24 (June 09, 2016)
àà Internal release
XCAPI Version 3.6.23 (June 07, 2016)
àà Internal release
XCAPI Version 3.6.22 (June 01, 2016)
àà New configuration value: Min-SE
XCAPI Version 3.6.21 (May 26, 2016)
àà Internal release
XCAPI Version 3.6.20 (May 10, 2016)
àà Improved DTMF recognition.
XCAPI Version 3.6.19 (May 02, 2016)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
5
Release Notes
XCAPI Version 3.6.18 (April 29, 2016)
àà Internal release
XCAPI Version 3.6.17 (April 21, 2016)
àà Improved detection of CED/ANSAM tone.
XCAPI Version 3.6.16 (April 14, 2016)
àà Internal release
XCAPI Version 3.6.15 (April 12, 2016)
àà A change introduced in version 3.6.9 could lead to a memory leak. This has been fixed.
XCAPI Version 3.6.14 (April 11, 2016)
àà Internal release
XCAPI Version 3.6.13 (April 04, 2016)
àà Internal release
XCAPI Version 3.6.12 (April 01, 2016)
àà Internal release
XCAPI Version 3.6.11 (April 01, 2016)
àà New tweak „FORCE_ASSERTED“
XCAPI Version 3.6.10 (March 31, 2016)
àà Under certain conditions the situation could arise that XCAPI wouldn‘t correctly send ACK
messages to remote devices. This has been fixed.
XCAPI Version 3.6.9 (March 23, 2016)
àà Internal release
XCAPI Version 3.6.8 (March 22, 2016)
àà Fixed a possible system crash in monitor mode.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
6
Release Notes
XCAPI Version 3.6.7 (March 17, 2016)
àà Customer-specific special behaviour.
XCAPI Version 3.6.6 (March 10, 2016)
àà Fixed an error with checking certain hold conditions.
XCAPI Version 3.6.5 (February 18, 2016)
àà With certain versions of Alcatel PBXs some difficulties in negotiating T.38 channels via H.323
could occur. This has been fixed.
XCAPI Version 3.6.4 (February 16, 2016)
àà Improved compatibility of SIP authentication.
XCAPI Version 3.6.3 (January 04, 2016)
àà Rely on SIP loose routing by default.
XCAPI Version 3.6.2 (December 23, 2015)
àà A change introduced in version 3.6.0 could lead to high system load. This has been fixed.
XCAPI Version 3.6.1 (December 17, 2015)
àà A change introduced in version 3.6.0 could lead to a system crash (BSOD). This has been fixed.
XCAPI Version 3.6.0 (December 10, 2015)
àà Extended recognition of virtualization solutions: VMWARE, Hyper-V, Azure
àà massively extended licencing output in the trace
àà extended information from the configuration utility: LOD key, controller wizard
àà fax quality information for the XCAPI SDK and diagnostic utilities
àà diagnostic applications can terminate calls now
àà considerably improved hierarchic organization of trace output
àà fixed an error with FAX gateway failover (standard gateway list instead of fax gateway list)
XCAPI Version 3.5.74 (December 09, 2015)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
7
Release Notes
XCAPI Version 3.5.73 (December 08, 2015)
àà Internal release
XCAPI Version 3.5.72 (December 08, 2015)
àà For SIP controllers now unconditionally signal availability of media channels after posting a
CONNECT_CONF message.
XCAPI Version 3.5.71 (December 04, 2015)
àà New configuration option for SIP controllers: „Disonnect on reception of Progress messages
containing Reason header fields“.
XCAPI Version 3.5.70 (December 02, 2015)
àà Fixed a minor issue related to sending SETUP ACKNOWLEDGE messages on H.323 connections. This could lead to failure to establish H.245 tunnels.
XCAPI Version 3.5.69 (November 24, 2015)
àà Internal release
XCAPI Version 3.5.68 (November 06, 2015)
àà Marginally improved robustness of Softfax/G.711 passthrough fax transmissens over lines
with bad quality, packet loss or jitter.
XCAPI Version 3.5.67 (November 04, 2015)
àà Internal release
XCAPI Version 3.5.66 (Oktober 28, 2015)
àà Internal release
XCAPI Version 3.5.65 (Oktober 21, 2015)
àà Internal release
XCAPI Version 3.5.64 (Oktober 16, 2015)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
8
Release Notes
XCAPI Version 3.5.63 (Oktober 16, 2015)
àà Internal release
XCAPI Version 3.5.62 (Oktober 15, 2015)
àà Internal release
XCAPI Version 3.5.61 (Oktober 09, 2015)
àà Internal release
XCAPI Version 3.5.60 (Oktober 06, 2015)
àà Internal release
XCAPI Version 3.5.59 (September 11, 2015)
àà Fixed a minor issue concerning the delayed switching to facsimile operation.
XCAPI Version 3.5.58 (September 10, 2015)
àà Internal release
XCAPI Version 3.5.57 (August 26, 2015)
àà A new tweak was introduced: FAX_FAILOVER_ON_488
àà Minor improvements on SIP protocol implementation
XCAPI Version 3.5.56 (August 17, 2015)
àà When there‘s no CAPI 2.0 application registered, XCAPI responds with the 503 status code to
received SIP OPTIONS messages.
XCAPI Version 3.5.55 (August 14, 2015)
àà Improved compatibility with Windows 10.
XCAPI Version 3.5.54 (August 12, 2015)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
9
Release Notes
XCAPI Version 3.5.53 (August 11, 2015)
àà Internal release
XCAPI Version 3.5.52 (July 20, 2015)
àà Internal release
XCAPI Version 3.5.51 (July 21, 2015)
àà A new tweak was introduced: REREGISTER_EARLY
XCAPI Version 3.5.50 (July 20, 2015)
àà A new tweak was introduced: FAX_FAILOVER_ON_488
XCAPI Version 3.5.49 (June 24, 2015)
àà After the maximum duration an outgoing INVITE message may take applications will we
notified with a „User Not Responding“ message under the condition that a 180/183 response
messages was received before. Earlier versions wrongly notified applications with a „Protocol
Error“ message.
XCAPI Version 3.5.48 (June 18, 2015)
àà Upon reception of „Session Progress“ messages containing a „Reason“ header field the session will be terminated with the reason contained therein.
XCAPI Version 3.5.47 (June 17, 2015)
àà Internal release.
XCAPI Version 3.5.46 (May 21, 2015)
àà Fixed an error parsing From and To header fields.
XCAPI Version 3.5.45 (May 04, 2015)
àà On reception of certain malformed SIP messages high load situations could occur. This has
been fixed.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
10
Release Notes
XCAPI Version 3.5.44 (April 30, 2015)
àà Robustness of generation of Refer-To header fields on SIP controllers with selected „Cisco“
profile was improved considerably.
XCAPI Version 3.5.43 (April 15, 2015)
àà Generate RFC3555 compliant SDP for negotiation of G.729.
XCAPI Version 3.5.42 (March 05, 2015)
àà Improved support for running in Azure environments.
XCAPI Version 3.5.41 (February 16, 2015)
àà The timeout after which XCAPI considers a specific media negotiation task failed has been
made configurable. On both H.323 and SIP controllers it‘s set to a default of six seconds. This
improves reliability with T.38 to Softfax failover.
XCAPI Version 3.5.40 (January 20, 2015)
àà When transfering calls via XCAPI SIP Security Additions some PBXes failed to process the generated Refer-To header field. This has been fixed with this version.
XCAPI Version 3.5.39 (January 20, 2015)
àà After reception of SDP packets the internal audio processing queue is not necessarily reestablished. This behaviour together with CAPI applications which transmitted audio in early
stages of the call could lead to short drops in the audio channel.
XCAPI Version 3.5.38 (January 15, 2015)
àà XCAPI now suppresses sending of BYE messages in call situations which do not require it.
XCAPI Version 3.5.37 (November 21, 2014)
àà XCAPI now generates a CAPI ECT notification message when receiving SIP INVITEs containing
Replaces header fields.
XCAPI Version 3.5.36 (November 19, 2014)
àà The XCAPI SDK can now determine the fax operating mode (T.38/softfax) of an NCCI.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
11
Release Notes
XCAPI Version 3.5.35 (November 19, 2014)
àà After a fallback from T.38 to softfax reception of certain INVITE messages could lead to the
T.38 mode being reestablished. This is now inhibited.
XCAPI Version 3.5.34 (November 03, 2014)
àà Minor corrections with processing received SIP status codes and translation into CAPI compliant behaviour.
XCAPI Version 3.5.33 (October 27, 2014)
àà Functional improvements of an internal API supporting certain functions of the XCAPI SDK.
XCAPI Version 3.5.32 (October 21, 2014)
àà Internal release.
XCAPI Version 3.5.31 (October 08, 2014)
àà Internal release.
XCAPI Version 3.5.30 (September 29, 2014)
àà Small improvements with T.38-Softfax-Fallback mechanism.
XCAPI Version 3.5.29 (September 25, 2014)
àà Now it is possible to let XCAPI determine the state of the proxies to use by sending OPTIONS
messages.
XCAPI Version 3.5.28 (September 23, 2014)
àà Internal release
XCAPI Version 3.5.27 (September 12, 2014)
àà Internal release
XCAPI Version 3.5.26 (September 09, 2014)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
12
Release Notes
XCAPI Version 3.5.25 (September 05, 2014)
àà Internal release
XCAPI Version 3.5.24 (August 27, 2014)
àà The XCAPI now supports evaluation of received „P-Called-Party-ID“ header fields (RFC3455).
XCAPI Version 3.5.23 (August 26, 2014)
àà Improved compatibility with PBXes from Huawei, when no session timer is active
XCAPI Version 3.5.22 (August 21, 2014)
àà A minor error with parsing phone numbers inside Diversion- and History-Infor header fields
was fixed.
XCAPI Version 3.5.21 (August 21, 2014)
àà For numbered trace file generation the upper limit now is 999 files.
XCAPI Version 3.5.20 (July 15, 2014)
àà New configuration options and tweak settings permit to adapt parsing of Diversion and History-Info Header fields to the peculiarities of an even greater number of PBXs.
XCAPI Version 3.5.19 (July 04, 2014)
àà Internal release
XCAPI Version 3.5.18 (June 27, 2014)
àà Under certain preconditions SIP registrations could be renewed (much) too early. This has
been fixed.
XCAPI Version 3.5.17 (June 24, 2014)
àà A new manufacturer specific B3 protocol permits CAPI applications to select sample rates
deviating from the default 8 kHz.
XCAPI Version 3.5.16 (June 23, 2014)
àà The feature V.34 does not require additional licences when operating in T.38 mode.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
13
Release Notes
XCAPI Version 3.5.15 (June 16, 2014)
àà Internal release
XCAPI Version 3.5.14 (June 12, 2014)
àà Internal release
XCAPI Version 3.5.13 (June 04, 2014)
àà Transmitting facsimile messages with higher resolutions now supports rendering a fax headline for all extended resolutions.
XCAPI Version 3.5.12 (June 04, 2014)
àà For transmitting and receiving facsimile messages with high resolutions some internal buffers
were enlarged. This enables CAPI applications to reliably transfer fax messages even if they
are extraordinarily large.
XCAPI Version 3.5.11 (May 27, 2014)
àà XCAPI contains an optional feature to automatically reduce the resolution of facsimile documents whenever an application tries to send a high resolution document and the connected
party only supports lower resolutions. This feature is now also applicable to documents that
contain pages with resolutions differing from each other.
XCAPI Version 3.5.10 (May 26, 2014)
àà In the course of supporting higher facsimile resolutions now higher K values for two-dimensional encoding according to ITU-T T.4 are supported correctly.
XCAPI Version 3.5.9 (May 22, 2014)
àà When establishing a T.38/T.30 protocol stack on H.323 connections a timeout condition could
arise under certain circumstances resulting in a failure to establish that connection. For slower
connected devices the respective timeout was increased.
XCAPI Version 3.5.8 (May 16, 2014)
àà When receiving facsimile documents with different horizontal and vertical resolutions invalid
SFF page header structures could be sent to CAPI applications. With this version of XCAPI this
has been fixed.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
14
Release Notes
XCAPI Version 3.5.7 (May 15, 2014)
àà CAPI applications can now set information pertaining to call diversion for outgoing calls by
utilizing and extension to the CAPI specification.
XCAPI Version 3.5.6 (May 14, 2014)
àà XCAPI now supports sending and receiving facsimilie documents using higher resolutions
than specified by CAPI.
XCAPI Version 3.5.5 (May 12, 2014)
àà Internal release
XCAPI Version 3.5.4 (May 08, 2014)
àà For H.323 controllers a new tweak (H4503_DIVLEG2_SWAP_NUMBERS) was introduced. It
takes effect whenever a DivertingLegInformation2 information element is received via the
H.450.3 protocol. If the tweak is set the OriginalCalledNumber and DivertingNumber data
fields within the information element are swapped for further processing. This leads to CAPI
applications receiving the original number where they would have received the diverting
number and vice versa. This new tweak should not be applied generally as it only serves to
implement a special customer request.
XCAPI Version 3.5.3 (May 05, 2014)
àà Whenever in previous versions of XCAPI sending SIP request messages (especially initial INVITE messages used to establish a call) failed due to a DNS request that was responded to with
an error message or missing SIP resonse messages, internally the error code „404 (Not Found)“
was generated. Due to XCAPI immanent mapping rules this was converted to the Q.850 status
code „1 (Unallocated Number)“.
àà This could cause issues for CAPI applications which don‘t rely on XCAPI provided failover functionality but implement some sort of failover themselves. The given Q.850 status code most
often occurs in situations which cannot be recovered from by failing over.
àà The SIP status that is generated internally was changed to „500 (Server Error)“ which maps to
Q.850 status code „111 (Protocol Error“).
XCAPI Version 3.5.2 (April 29, 2014)
àà This version of XCAPI introduces line bases licensing for the new V.34 fax mode of operation.
Using this it is now possible to exactly and granularly align fax licencing to ones demands.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
15
Release Notes
àà Additionally, using a manufacturer specific API (application programming interface), CAPI
applications can be provided with all messages sent and received on a V.34 control channel.
Until now this API was applicable to non-V.34 fax connections only. This new addition enables
applications to realize extended fax services even in high speed modes of operation.
XCAPI Version 3.5.1 (April 09, 2014)
àà Internal release
XCAPI Version 3.5.0 (April 03, 2014)
àà Beginning with XCAPI Version 3.5.0 the XCAPI supports transmitting and receiving facsimile
messages via V.34. This is a T.38 Fax only feature, Softfax (Fax Modem) is not supported. Additionally, fallback to Softfax procedures is supported, should T.38 negotiation fail for some
reason. Within the XCAPI configuration utility all fax related settings can now be carried out
in a new controller-specific fax dialog.
XCAPI Version 3.4.31
àà Internal release
XCAPI Version 3.4.30
àà Internal release
XCAPI Version 3.4.29
àà Internal release
XCAPI Version 3.4.28
àà Internal release
XCAPI Version 3.4.27
àà Internal release
XCAPI Release 3.4.26
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
16
Release Notes
XCAPI Release 3.4.25 (March 05, 2014)
àà Improved fallback behavior from V.34 to T.30 fax with Cisco gateways.
àà Fixed a minor error in communicating with Avaya WEBLM servers.
XCAPI Release 3.4.24 (March 05, 2014)
àà The topmost Via header field is now copied to response messages verbatim.
àà Introducted the new PERMIT_HASH_SIGN_IN_USER_PART tweak.
XCAPI Release 3.4.23 (March 03, 2014)
àà When communicating with the Avaya WEBLM server the XCAPI now identifies itself with the
name of the system it is running on.
XCAPI Release 3.4.22 (February 26, 2014)
àà Initial support for V.8 and V.34 fax - currently disabled by default.
àà Integrated new Avaya WEBLM interface.
XCAPI Release 3.4.21 (February 25, 2014)
àà Internal release
XCAPI Release 3.4.20 (February 12, 2014)
àà An error parsing certain MIME types was fixed.
XCAPI Release 3.4.19 (January 28, 2014)
àà m=video lines within SDP packets are now ignored.
XCAPI Release 3.4.18 (January 22, 2014)
àà The XCAPI now uses different CSEQ intervals for incoming and outgoing calls. This is neccessary to support the scenario XCAPI -> PBX -> XCAPI with some PBX devices. XCAPI Release
XCAPI Release 3.4.17 (December 17, 2014)
àà Fixed an error that could cause the XCAPI being unable to decode well-formed SIP messages
received via TCP.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
17
Release Notes
XCAPI Release 3.4.16 (November 29, 2013)
àà Fixed an error that could - given certain circumstances - lead to singular lines not being usable
anymore.
XCAPI Release 3.4.15 (November 12, 2013)
àà CAPI applications now can pre-select the audio codec that will be used on a SIP connection.
àà RTP quality information packets sent to applications now also contain information on the
used codec.
XCAPI Release 3.4.14 (November 05, 2013)
àà Fixed a possible system crash with the call transfer supplementary service.
àà Fixed a possible system crash when enumerating system ids with windows 8.1.
àà Fixed a minor issue with fax transmission.
XCAPI Release 3.4.13 (October 24, 2013)
àà Internal release
XCAPI Release 3.4.12 (October 24, 2013)
àà Internal release
XCAPI Release 3.4.11 (October 24, 2013)
àà Internal release
XCAPI Release 3.4.10 (October 17, 2013)
àà A counter part of RTP quality information was increased on a wrong base.
XCAPI Release 3.4.9 (October 15, 2013)
àà Deliver interval based RTP quality information to diagnostics applications.
XCAPI Release 3.4.8 (September 20, 2013)
àà The new „NO_PRIVATE_HEADER“ tweak can be used to disable sending of any P- and X header fields on SIP controllers.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
18
Release Notes
XCAPI Release 3.4.7 (September 02, 2013)
àà Fixed problems negotiating T.38 with some endpoints.
XCAPI Release 3.4.6 (August 30, 2013)
àà Fixed counter deviations in RTP quality information.
XCAPI Release 3.4.5 (August 28, 2013)
àà When switching from Fax to Speech operation mode sometimes no telephone event capabilities were negotiated with remote SIP devices. This has been fixed.
XCAPI Release 3.4.4 (August 28, 2013)
àà Trasnmit RTP Quality Information to interested diagnostics/CAPI applications at the end of
the call.
XCAPI Release 3.4.3 (July 18, 2013)
àà Increased delay between SIP Registration attempts.
XCAPI Release 3.4.2 (July 03, 2013)
àà Removed a race condition in module capi2032.dll causing calls to GET_MESSAGE/PUT_MESSAGE not to return.
XCAPI Release 3.4.1 (July 02, 2013)
àà The new SIP tweak „DISABLE_TIMER“ deactivates the „timer“ extension and thus suppresses
a session refresh.
XCAPI Release 3.4.0 (July 02, 2013)
àà First release of the 3.4. branch. No changes.
XCAPI Release 3.3.305 (June 25, 2013)
àà Internal release
XCAPI Release 3.3.304 (June 25, 2013)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
19
Release Notes
XCAPI Release 3.3.303 (June 19, 2013)
àà Fixed an error with message Center numbers and MD-110 style MWI.
XCAPI Release 3.3.302 (June 07, 2013)
àà Fixed an error with message Center numbers and MD-110 style MWI.
XCAPI Release 3.3.301 (June 05, 2013)
àà Extended support for some SIP protocol elements concerning Registration.
XCAPI Release 3.3.300 (June 04, 2013)
àà Fixed an error with SIP authentication and certain PBXs. Added Extended T.38 Parameters to
prolong certain timeouts.
XCAPI Release 3.3.299 (May 27, 2013)
àà Included numerous extensions to the diagnostics system of XCAPI. Extended call information
as well as Information concerning certain error conditions are now forwarded to diagnostic
utilities.
XCAPI Release 3.3.298 (May 15, 2013)
àà Included numerous extensions to the diagnostics system of XCAPI. Extended call information
as well as Information concerning certain error conditions are now forwarded to diagnostic
utilities.
XCAPI Release 3.3.297 (May 05, 2013)
àà Internal release
XCAPI Release 3.3.296 (April 29, 2013)
àà Multiple SIP session with identical Call-IDs could under certain circumstances not be processed
correctly. This has been fixed.
XCAPI Release 3.3.295 (April 26, 2013)
àà Under certain conditions it was not always possible to establish SIP calls from XCAPI to itself
without an intermediate gateway. This problem has been fixed.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
20
Release Notes
àà Fixed issued with SIP Proxy Authentication together with some not quite standards compliant
SIP devices.
àà Default „Type of Number“ and „Numbering Plan“ parameters are now configurable.
XCAPI Release 3.3.294 (February 13, 2013)
àà A possible system crash occuring in high load situations when processing incoming INVITE
messages containing a Replaces header field was fixed.
XCAPI Release 3.3.293 (February 08, 2013)
àà Internal release
XCAPI Release 3.3.292 (February 07, 2013)
àà By utilizing a specially crafted FACILITY_REQ message data paths within a PLCI can be reconfigured without having established a conference.
XCAPI Release 3.3.291 (January 31, 2013)
àà A possible system crash was fixed. Failed SIP registration caused a too high rate of re-registration attempts.
àà Introduced new tweaks for certain PBX systems.
XCAPI Release 3.3.290 (January 30, 2013)
àà Internal release
XCAPI Release 3.3.289 (January 30, 2013)
àà Internal release
XCAPI Release 3.3.288 (January 30, 2013)
àà Internal release
XCAPI Version 3.3.287 (Januar 29, 2013)
àà Internal release
XCAPI Release 3.3.285 (January 18, 2013)
àà This version contains changes to the internal diagnostics interface.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
21
Release Notes
XCAPI Release 3.3.284 (January 17, 2013)
àà The XCAPI now evaluates a „Called Party Subaddress“ transmitted by Avaya in a private SIP
Header.
XCAPI Release 3.3.283 (January 17, 2013)
àà Implemented a possible workaround for a problem concerning Avaya-Tenovis-Licensing.
XCAPI Release 3.3.282 (January 16, 2013)
àà Enhanced the implementation of the SIP Timer RFC by sending refresher information (UAS/
UAC).
XCAPI Release 3.3.281 (January 15, 2013)
àà Forwarding of opaque parameters in Via, Route, and Record-Route header fields.
XCAPI Release 3.3.280 (December 18, 2012)
àà After a DISCONNECT_REQ message from a CAPI application unsent but queued fax data is
now processed correctly. In previous versions errors could occur in some specific cases.
àà Fixed an error with gateway failover operating in round robin mode.
XCAPI Release 3.3.279 (December 18, 2012)
àà Internal release
XCAPI Release 3.3.278 (November 27, 2012)
àà With certain controller settings, it could happen that calls conducted from and on the XCAPI
itself were not established. This has been fixed.
XCAPI Release 3.3.277 (November 26, 2012)
àà An error which could lead to interrupted connections when executing a call transfer or a call
deflect operation on a connected call was fixed.
XCAPI Release 3.3.276 (November 09, 2012)
àà XCAPI now processes incoming INVITE messages which contain a Replaces header field. This
can be utilized for incoming call transfers especially together with Alcatel PBX devices.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
22
Release Notes
XCAPI Release 3.3.275 (November 05, 2012)
àà XCAPI now supports authentication of REFER messages.
XCAPI Release 3.3.274 (November 01, 2012)
àà Fixed an error parsing concatenated SIP Diversion headers.
XCAPI Release 3.3.273 (October 17, 2012)
àà Internal release
XCAPI Release 3.3.272 (October 16, 2012)
àà With the newly added Tweak NO_ROUTE_HEADER one can disable sending any RouteHeader.
àà Added a manufacturer specific CAPI FAX extension.
XCAPI Release 3.3.271 (October 15, 2012)
àà Fixed parsing of SDP messages.
XCAPI Release 3.3.270 (October 11, 2012)
àà Internal release
XCAPI Release 3.3.269 (October 05, 2012)
àà Fixed an issue processing SDP messages.
àà Fixed a possible system crash when switching to unsupported b protocol combinations.
àà Added QSIG_CLEAR_DISCARD tweak.
àà Correctly processing T.30 NSC messages.
àà Processing the volume parameter of received RTP event packages.
XCAPI Release 3.3.268 (September 26, 2012)
àà Internal release
XCAPI Release 3.3.267 (September 21, 2012)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
23
Release Notes
XCAPI Release 3.3.266 (September 19, 2012)
àà Internal release
XCAPI Release 3.3.265 (September 10, 2012)
àà With the newly added QSIG_CLEAR_DISCARD-Tweak one can prevent the call from being
cleared upon reception of unknown QSIG messages, even if call clearing is explicitly requested
by the remote party.
XCAPI Release 3.3.264 (August 24, 2012)
àà During proxy failover, XCAPI used to sent two To headers in outbound SIP messages. From
now on the XCAPI will send only one To header.
XCAPI Release 3.3.263 (July 27, 2012)
à à On H.323 controllers a CAPI application can now signal the early availability of tones and announcements on an incoming call by including a specially crafted
PROGRESS_INDICATOR information element within the FacilityDataArray parameter of
an ALERT_REQ message. Coupled with the Early-B3 mechanism this can be used to
implement cost-free waiting queues.
XCAPI Release 3.3.262 (July 26, 2012)
àà Internal release
XCAPI Release 3.3.261 (July 12, 2012)
àà Internal release
XCAPI Release 3.3.260 (July 03, 2012)
àà Fixed an error with reception of CANCEL messages and made configurable whether SDP will
be included in transmitted provisional SIP response messages.
XCAPI Release 3.3.259 (July 03, 2012)
àà Internal release
XCAPI Release 3.3.258 (June 19, 2012)
àà The timeout towards the reception of provisional SIP response messages has been made configurable.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
24
Release Notes
XCAPI Release 3.3.257 (June 13, 2012)
àà The MEDIATRIX_HOTFIX and REJECT_UNACCEPTABLE_SDP tweaks has been added.
XCAPI Release 3.3.256 (June 11, 2012)
àà An error in SDP offer answer processing has been fixed.
XCAPI Release 3.3.255 (June 04, 2012)
àà T.38 redundancy information can now be transmitted optionally.
àà Rollover between multiple trace files.
XCAPI Release 3.3.254 (May 25, 2012)
àà Internal release
XCAPI Release 3.3.253 (May 21, 2012)
àà Cause code to SIP status mappings adapted to the industry standards. Smaller error corrections regarding the interoperability of H.245 negotiations.
XCAPI Release 3.3.252 (May 11, 2012)
àà Internal release
XCAPI Release 3.3.251 (May 11, 2012)
àà Internal release
XCAPI Release 3.3.250 (May 09, 2012)
àà The LRU allocation mode for B channel numbers can now be disabled by a CAPI option.
XCAPI Release 3.3.249 (April 25, 2012)
àà The driver was adapted to the new licencing options that are available. From XCAPI release
3.3.249 onwards licenses are now checked for a valid Software Upgrade Service. Please find
more information on our website www.xcapi.de „Software Upgrade Service“ respectively in
the XCAPI Price List.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
25
Release Notes
XCAPI Release 3.3.248 (April 18, 2012)
àà A new configuration setting determines whether DTMF are forwarded between parties of an
ECT that is simulated by call tromboning. With previous versions this was the case unconditionally.
XCAPI Release 3.3.247 (April 16, 2012)
àà When using the TCP policy setting “Trunk” TCP streams were sometimes disconnected early
by XCAPI. This could lead to problems with certain PBX devices and is fixed with this version.
XCAPI Release 3.3.246 (April 04, 2012)
àà Should the numbers of a calling SIP entity change during the call establishment phase, these
are now posted to CAPI applications by the means of an early call transfer notification message even if these applications are still in the broadcast state.
XCAPI Release 3.3.245 (March 12, 2012)
àà CAPI applications will receive a Call Transfer Notification if the calling number of the remote
station changes due to a SIP call transfer.
XCAPI Release 3.3.244 (March 05, 2012)
àà The maximum size of the jitter buffer used in SIP calls is now adjustable via tweaks.
XCAPI Release 3.3.243 (February 24, 2012)
àà CAPI applications being informed about incoming calls without having accepted them yet will
now - on the premise of having registered for such events - be informed about call transfers
by means of a transfer notification indication message.
XCAPI Release 3.3.242 (February 23, 2012)
àà Internal release
XCAPI Release 3.3.241 (February 14, 2012)
àà Internal release
XCAPI Release 3.3.240 (February 01, 2012)
àà If all SIP lines are occupied, incoming calls will be rejected with an adjustable reason of error.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
26
Release Notes
XCAPI Release 3.3.239 (January 06, 2012)
àà A switch in the configuration application can be applied now, so that the configured
SIP domain is used for registrations.
XCAPI Release 3.3.238 (January 06, 2012)
àà Internal release
XCAPI Release 3.3.237 (January 06, 2012)
àà Internal release
XCAPI Release 3.3.236 (January 06, 2012)
àà The CANCEL management has been improved. Privacy header are now supported.
XCAPI Release 3.3.235 (January 06, 2012)
àà An error regarding the parsing of P-Asserted-Identity header has been fixed and the CANCEL
management has been improved.
XCAPI Release 3.3.234 (December 05, 2011)
àà If remote numbers change during a SIP session they are signalled as an ECT notification to
CAPI applications.
XCAPI Release 3.3.233 (November 30, 2011)
àà With SIP controllers the authentication user can now be set separately.
XCAPI Release 3.3.232 (November 17, 2011)
àà Error corrections regarding the expiration of some protocol timers. Support for changing
IP addresses within active T.38 connections.
XCAPI Release 3.3.231 (November 10, 2011)
àà Controllers with more than 127 lines now pass B channel numbers in a different format to
CAPI applications.
XCAPI Release 3.3.230 (October 20, 2011)
àà By default the XCAPI refrains from sending SDP messages within provisional SIP responses.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
27
Release Notes
XCAPI Release 3.3.229 (October 10, 2011)
àà Internal release
XCAPI Release 3.3.228
àà Internal release
XCAPI Release 3.3.227 (September 15, 2011)
àà REGISTER failover is supported now.
XCAPI Release 3.3.226 (September 09, 2011)
àà By using the CONNECT_WAIT tweak one can introduce a short pause and fix some problems
with certain SIP PBXes.
XCAPI Release 3.3.225
àà Internal release
XCAPI Release 3.3.224
àà Internal release
XCAPI Release 3.3.223
àà Internal release
XCAPI Release 3.3.222
àà Internal release
XCAPI Release 3.3.221 (August 05, 2011)
àà By utilizing the DIVERSION_INFO-Tweak one can disable transmission of diversion numbers to
CAPI applications when they are equal to the actual called party number.
XCAPI Release 3.3.220 (July 26, 2011)
àà Falling back to the builtin demo license can be disabled in the XCAPI configuration utility.
This way having a time limited license expire does not cause the demo limitiations to become
active.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
28
Release Notes
XCAPI Release 3.3.219 (July 15, 2011)
àà SIP messages containing a „message/sipfrag“ body were sometimes rejected with an error
message. This has been fixed.
XCAPI Release 3.3.218 (July 11, 2011)
àà Internal release
XCAPI Release 3.3.217 (July 06, 2011)
àà SIP MWI transmitted via NOTIFY now contain the Message-Account parameter.
XCAPI Release 3.3.216 (June 23, 2011)
àà Missing URL encoding added when sending SIP URIs.
XCAPI Release 3.3.215 (June 20, 2011)
àà In the Overlap-Sending state a CANCEL message was mistakenly sent when terminating
the call.
XCAPI Release 3.3.214 (June 08, 2011)
àà Unknown Reject values in CONNECT_RESP messages are mapped to „Normal Call Clearing“
now.
XCAPI Release 3.3.213 (June 06, 2011)
àà The XCAPI mistakenly replied to erroneous SDP with „Unsupported Media Type“. Now the
correct „Not Acceptable“ message is sent.
XCAPI Release 3.3.212 (June 01, 2011)
àà Erroneous sending of ACK messages for cancelled INVITEs was fixed.
XCAPI Release 3.3.211 (May 25, 2011)
àà For playing DMTF tones that have been received on a connected call via signalling into audio
streams the DTMF volume that has been set in the configuration is now regarded correctly.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
29
Release Notes
XCAPI Release 3.3.210 (May 17, 2011)
àà Using a tweak one can now switch between sending and receiving P-Asserted-Identity or
P-Preferred-Identity header fields.
XCAPI Release 3.3.209 (May 13, 2011)
àà SIP display names set up with the XConfig tool were sometimes not transmitted in every
SIP message. This Problem is fixed now.
XCAPI Release 3.3.208 (May 06, 2011)
àà The „Follow Me“ supplementary service is now implemented for MD110 PBX devices.
XCAPI Release 3.3.207 (April 21, 2011)
àà Internal release
XCAPI Release 3.3.206 (April 19, 2011)
àà Internal release
XCAPI Release 3.3.205 (April 18, 2011)
àà A problem with processing certain license files was fixed.
XCAPI Release 3.3.204 (April 14, 2011)
àà Internal release
XCAPI Release 3.3.203 (April 12, 2011)
àà A new tweak (SDP_IGNORE_HOLD) was introduced. This fixes problems with certain PBXes.
XCAPI Release 3.3.202 (March 28, 2011)
àà A possible crash when using music on hold with SIP controllers was fixed. Certain ACK
messages where transmitted with an invalid branch id. This Problem ist fixed now.
XCAPI Release 3.3.201 (March 21, 2011)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
30
Release Notes
XCAPI Release 3.3.200 (March 10, 2011)
àà Internal release
XCAPI Release 3.3.199 (March 07, 2011)
àà Internal release
XCAPI Release 3.3.198 (February 22, 2011)
àà Integration of Microsoft Lync 2010 into the configuration.
XCAPI Release 3.3.197 (February 14, 2011)
àà Fixed an error creating SIP contact header fields.
XCAPI Release 3.3.196 (January 26, 2011)
àà A tweak was added to support transmitting call transfer information with Siemens HiPath
3000 PBX devices.
XCAPI Release 3.3.195 (January 19, 2011)
àà Proxy Failover can now be used together with XCAPI SIP Security Additions.
XCAPI Release 3.3.194 (December 17, 2010)
àà The behaviour of the Second Calling Party Number is configurable now to assist unassuming
applications which do not support sending/receiving this field.
XCAPI Release 3.3.193 (December 16, 2010)
àà Internal release
XCAPI Release 3.3.192 (December 14, 2010)
àà Internal release
XCAPI Release 3.3.191 (December 07, 2010)
àà Setting and evaluating the SIP P-Asserted-Identity header field is now possible via the CAPI
feature „Calling Party Number“ together with „Second Calling Party Number“.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
31
Release Notes
XCAPI Release 3.3.190 (December 01, 2010)
àà The fax headline can be prepended to transmitted pages via a new XFaxtune option. The
topmost scanlines do not get overwritten.
XCAPI Release 3.3.189
àà Internal release
XCAPI Release 3.3.188 (November 26, 2010)
àà Under certain conditions no response was sent for an INVITE message when receiving
a CANCEL. This has been fixed.
XCAPI Release 3.3.187 (November 12, 2010)
àà An error with the H.245 negotiation of Softfax via G.711 together with retransmissions of
TerminalCapabilitySets was fixed.
XCAPI Release 3.3.186 (October 13, 2010)
àà Introduced new tweaks for performing a failover between gateways in different SIP domains.
XCAPI Release 3.3.185 (October 05, 2010)
àà If multiple SIP Diversion header fields are received a new config option decides which of those
is forwarded to CAPI applications.
XCAPI Release 3.3.184
àà Internal release
XCAPI Release 3.3.183 (September 21, 2010)
àà Enlarged jitter buffer for SIP softfax connections.
XCAPI Release 3.3.182 (September 20, 2010)
àà Some SIP encoding mishaps have been fixed.
XCAPI Release 3.3.181
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
32
Release Notes
XCAPI Release 3.3.180 (September 06, 2010)
àà When holding SIP sessions the SDP attributes „sendonly“, „recvonly“ and „inactive“ are
transmitted in a standards compliant fashion.
XCAPI Release 3.3.179 (August 30, 2010)
àà The character set for strings transmitted within CAPI messages is now configurable. Smaller
encoding problems within SIP have been fixed.
XCAPI Release 3.3.178
àà Internal release
XCAPI Release 3.3.177 (August 17, 2010)
àà The SIP-REFER behaviour with Cisco Unified Communications Managers was improved.
XCAPI Release 3.3.176 (August 12, 2010)
àà SIP-Diversion-Headers sent by XCAPI did not always contain the proper Diversion-Reason
parameter as set by CAPI applications. This is now fixed.
XCAPI Release 3.3.175 (August 05, 2010)
àà A new timer value for a pause after receiving TCF on a T.30 connection is now configurable
via XFaxtune.
XCAPI Release 3.3.174 (July 27, 2010)
àà A new tweak for formatting SIP phone numbers was added.
XCAPI Release 3.3.173 (June 30, 2010)
àà A possible system crash when activating the echo canceller was fixed.
XCAPI Release 3.3.172 (May 25, 2010)
àà Unknown SIP Reason header fields are now ignored. An error regarding the
RTP_IGNORE_AUDIO_TIMESTAMP tweak has been fixed.
XCAPI Release 3.3.171
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
33
Release Notes
XCAPI Release 3.3.170 (May 20, 2010)
àà An error has been fixed in the fax module. Now fax polling is possible with all remote
terminals.
XCAPI Release 3.3.169
àà Internal release
XCAPI Release 3.3.168 (May 06, 2010)
àà The configured packetization interval is now honored when sending RTP packets.
XCAPI Release 3.3.167 (May 03, 2010)
àà QSIG Name Identification now uses the character set latin1 instead of UTF-8.
àà Fixed CAPI_REGISTER problems (CAPI2032.DLL) introduced in version 3.3.164.
XCAPI Release 3.3.166
àà Internal release
XCAPI Release 3.3.165 (April 23, 2010)
àà Fixed problems concerning QSIG Name Identification in combination with a Siemens HiPath
PBX.
XCAPI Release 3.3.164
àà Internal release
XCAPI Release 3.3.163 (March 22, 2010)
àà Sending periodic re-INVITE messages to prevent SIP sessions from timing out.
XCAPI Release 3.3.162 (March 16, 2010)
àà New MPA encoder (twolame) added. The old encoder had some quality issues.
XCAPI Release 3.3.161 (February 24, 2010)
àà When receiving fax transmissions XCAPI sometimes would append an additional ‚0‘ byte
to SFF line data.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
34
Release Notes
XCAPI Release 3.3.160 (February 15, 2010)
àà When using XCAPI on virtual environments the hardlock software protection system
sometimes caused a very high processor load. To avoid this the hardlock software protection
system is only used when a license requiring the hardlock system is installed.
àà When connecting to some H.323-based PBXes sometimes no H.245 channel would be
established. This has been fixed.
XCAPI Release 3.3.159
àà Internal release
XCAPI Release 3.3.158
àà Internal release
XCAPI Release 3.3.157
àà Internal release
XCAPI Release 3.3.156
àà Internal release
XCAPI Release 3.3.155
àà Internal release
XCAPI Release 3.3.154
àà Internal release
XCAPI Release 3.3.153 (December 04, 2009)
àà Internal release
XCAPI Release 3.3.152 (December 03, 2009)
àà Internal release
XCAPI Release 3.3.151 (December 01, 2009)
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
35
Release Notes
XCAPI Release 3.3.150 (November 27, 2009)
àà Internal release
XCAPI Release 3.3.149 (November 26, 2009)
àà It has been made possible to configure a message center number for a SIP controller.
XCAPI Release 3.3.148 (November 25, 2009)
àà Calls are now unconditionally disconnected whenever a gatekeeper unregistration operation
is completed. Prior versions only did so if the unregistration was initiated by the gatekeeper.
XCAPI Release 3.3.147 (November 25, 2009)
àà The selectivity range of the XCAPI-builtin DTMF recognizer was broadened. By default the
highest selectivity value is used now.
XCAPI Release 3.3.146 (November 23, 2009)
àà Internal release
XCAPI Release 3.3.145 (November 23, 2009)
àà Fixed an SDP parser error with fax media descriptions.
XCAPI Release 3.3.144 (November 18, 2009)
àà Internal release
XCAPI Release 3.3.143 (November 12, 2009)
àà Internal release
XCAPI Release 3.3.142 (November 11, 2009)
àà Internal release
XCAPI Release 3.3.141 (October 26, 2009)
àà A possible system crash that could occur when shutting down H.323 gatekeeper registrations
was fixed.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
36
Release Notes
XCAPI Release 3.3.140 (October 12, 2009)
àà With a new option XCAPI can be configured so that VoIP calls are taken out of the hold state
automatically before a call transfer.
XCAPI Release 3.3.139 (October 09, 2009)
àà It‘s now possible for CAPI applications, by using a MANUFACTURER_REQ-API, to dynamically
register and unregister phone numbers with a H.323 gatekeeper.
XCAPI Release 3.3.138 (October 08, 2009)
àà Internal release
XCAPI Release 3.3.137 (September 24, 2009)
àà If XCAPI is being operated in softfax mode and a REINVITE message is received which attempts to swith to the T.38 protocol this message is acknowledged without actually changing
the operating mode. In order to disable this behaviour on demand the new SOFTFAX_REJECT_T38 tweak was added. If this tweak is enabled such a message is rejected with the SIP
reason code 415 Unsupported Media Type.
XCAPI Release 3.3.136 (September 21, 2009)
àà If XCAPI was being executed inside a virtual machine a high load situation on the executing
physical system could lead to loss of signal quality for individual connections. Especially with
softfax connections this could lead to retransmissions, severely prolonged transmission times,
or even the failure to transmit the document at all. This XCAPI version introduces a number
of measures to compensate for those situations.
àà On 64-bit systems the installation routine and the configuration application did not write all
vital information into the registry.
XCAPI Release 3.3.135
àà Internal release
XCAPI Release 3.3.134 (September 14, 2009)
àà Internal release
XCAPI Release 3.3.133 (September 09, 2009)
àà On fax transmissions using the error correction mode (ECM) a short but severe distortion of
the audio signal could lead to the transmission being terminated too early. This has been
fixed.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
37
Release Notes
XCAPI Release 3.3.132 (September, 08 2009)
àà When using multiple codecs with different sample rates together with SIP controllers sometimes a fatal system error could occur. This has been fixed with the current version.
àà The name identification supplementary service can now be signalled via ECMA-164 (QSIG) on
H.323 controllers.
àà When disconnecting media channels sometimes a contextually invalid disconnect reason code
was transmitted to CAPI applications.
àà When using the Softfax mode a initially bad line could lead to the fax handshake failing or
being delayed. This is fixed now.
XCAPI Release 3.3.131
àà Internal release
XCAPI Release 3.3.130
àà Internal release
XCAPI Release 3.3.129 (August 07, 2009)
àà With previous versions of XCAPI every INVITE message received on SIP connected lead to an
internal reset of already established audio streams. This is the case even when such an INVITE
is transmitted only to stop the call from timing out.
While in principle such behaviour isn’t problematic it could seldom and with low probability
lead to transmission errors on SoftFAX connections. Those transmission errors are usually
compensated by the error correction mode (ECM) but still lead to higher transmission times.
With the current version this behaviour has been rectified.
XCAPI Release 3.3.128 (July 31, 2009)
àà XCAPI now by default uses a larger jitter buffer for Softfax connections established via SIP. By
using an enlarged jitter buffer irregularities occurring in the audio stream can be compensated. Such irregularities often occur in networks with low quality of service or when using
virtual machines. The change leads to the error correction mode (ECM) becoming active less
often and such reduces fax transmission times a little.
àà XCAPI can be configured to always recognise DTMF tones in audio streams – even if the
remote device signals it will transmit then in the signalling stream. This compensates technical
misbehaviour of some SIP gateways when tunnelling ISDN calls via SIP.
XCAPI Release 3.3.127
àà Internal release
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
38
Release Notes
XCAPI Release 3.3.126 (July 23, 2009)
àà Previous versions of XCAPI did not handle SFF files correctly that contained some specific
encoding errors. When encountering such a file XCAPI sometimes did not clear the fax call
immediately but had it time out. This behaviour has been corrected now and such calls are
cleared immediately.
XCAPI Release 3.3.125 (July 20, 2009)
àà When XCAPI receives an incoming SIP call and has no CAPI application registered that could
accept this call, XCAPI has to release the call. Previous versions did so by signalling a User Busy
condition to the remote party. With the current version the error condition to signal is configurable. This permits differentiated configuration for failover purposes.
àà If DTMF were signalled by utilizing RFC 2833 sometimes DTMF couldn’t be received properly.
This was the case with some SIP provides (such as QSC) when the DTMF were transmitted in
separate RTP streams. This has been corrected.
XCAPI Release 3.3.124 (July, 17 2009)
àà Previous versions of XCAPI initiate SIP proxy failover procedures as soon as a low level network error is detected for a SIP controller. The current version has been extended to also
initiate failover procedures when a SIP proxy is reachable but rejects SIP messages with the
500 (Server Error) or 503 (Service Unavailable) response codes.
XCAPI Release 3.3.123 (July 09, 2009)
àà The SIP branch parameter wasn’t set conforming to the SIP specification in all cases. This
would only happen if a remote SIP device rejects SIP calls relatively early in the establishment phase. While it did not cause noticeable problems, such behaviour was still technically
incorrect and has been fixed.
XCAPI Release 3.3.122 (July 02, 2009)
àà XCAPI supports signalling Message Waiting Indications (MWI) via the QSIG Protocol
(ECMA-242). In order to be able to use this with Siemens HiPath PBXes a proprietary protocol
extension is needed. This extension has been supported by XCAPI since version 3.3.85. It has
been noticed that this extension would cause an Avaya Communication Manager 2.0 to reject
MWI signalling. The current version of XCAPI now only includes this extension when the remote device is positively identified to be a HiPath PBX.
XCAPI Release 3.3.121 (June 26, 2009)
àà XCAPI now includes a proprietary extension header field with outgoing SIP INVITE messages.
This header field improves compatibility with Alcatel-Lucent devices and causes such PBXes to
reliably log call detail records.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
39
Release Notes
XCAPI Release 3.3.120
àà Internal release
XCAPI Release 3.3.119 (June 17, 2009)
àà If SoftFAX has been enabled for a SIP controller XCAPI now will reject any attempt by a
remote device to swith to T.38. This generally will lead to the intended behaviour of keeping
already established audio streams and reusing them for a Softfax session.
àà The controller wizard within the configuration utility now supports special settings for controllers connecting to LANCOM VoIP routers and SwyxWare servers.
XCAPI Release 3.3.118 (June 10, 2009)
àà Under certain circumstances an unintended system shutdown could occur if a SIP controller
had multiple codecs configured utilizing different sample rates. This never was the case with
the standard configurations set up by the controller wizard and generally has been fixed with
the current version.
àà With prior version the configuration utility wasn’t always able to correctly set up the firewall
settings for Windows 2003 servers. This has been corrected.
XCAPI Release 3.3.117 (June 05, 2009)
àà Seldom it could occur that XCAPI mistranslated presentation indicator fields it received for
redirection numbers. For CAPI applications it seemed as if the presentation of the redirection
number was restricted, while in reality it was not. This has been corrected.
XCAPI Release 3.3.116 (June 03, 2009)
àà Due to an error in the CAPI2064.DLL file installed by XCAPI 64-bit CAPI applications sometimes
would be terminated involuntarily. Due to most CAPI applications still being 32-bit programs
this doesn’t occur in practice very often and has been rectified with this version of XCAPI.
XCAPI Release 3.3.115
àà Internal release
XCAPI Release 3.3.114 (May 26, 2009)
àà This version of XCAPI has been prepared for being used with the new XCAPI SIP Security
Additions module. By installing this extension module it’s possible to use SIP via secure TLS
connections.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
40
Release Notes
àà Now using the Name Identification supplementary service in the outgoing direction is supported for SIP controllers. CAPI applications can use this supplementary service in order to take
influence on the free text field in every SIP “From” header field XCAPI transmits.
XCAPI Release 3.3.108 - 113
àà Internal releases
XCAPI Release 3.3.107 (April 23, 2009)
àà Processing of E.164 numbers has been improved for SIP controllers. Whenever a CAPI application transmits numbers marked as international number it is converted to a SIP URI with
a leading plus sign.
XCAPI Release 3.3.106 (April 15, 2009)
àà When using ISDN controllers the silence recognition feature seldom would work incorrectly. As the comfort noise generation feature is based on silence recognition it was possible
that comfort noise wasn’t generated properly for ISDN calls. With the current version both
features work correctly in all cases.
XCAPI Release 3.3.105 (April 15, 2009)
àà To match the changes made to XCAPI 3.3.103 now also unregistering from a H.323 gatekeeper is processed with an internal delay. Using this version should not induce high processor
load on gatekeepers when unregistering a large amount of numbers.
XCAPI Release 3.3.104 (April 14, 2009)
àà This version of XCAPI maps the SIP response code 503 (Service Unavailable) to Q.850 cause
code 41 (Temporary Failure) when signalling to CAPI applications. Prior versions mapped the
same response code to a clearly incorrect 27 (Destination Out of Order) value. This possibly
hindered applications with special failover capabilities from redialling properly.
XCAPI Release 3.3.103 (April 09, 2009)
àà If XCAPI registers a large amount of phone numbers with a H.323 gatekeeper it does so
simultaneously. With some gatekeepers of small scale H.323 gateways this may lead to an
unintended high processor load on those devices. With this version a small delay is inserted
between individual registrations reducing this effect.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
41
Release Notes
XCAPI Release 3.3.102 (April 06, 2009)
àà For the call transfer supplementary services that is signalled via QSIG tunnelled over H.323 a
default local phone number can be configured. If a CAPI application restricts presentation of
its own phone number this configured number is inserted instead.
This works around problems with some Siemens HiPath PBXes which will not allow a call
transfer to take place with a restricted phone number.
XCAPI Release 3.3.101 (April 06, 2009)
àà Internal release
XCAPI Release 3.3.100 (March 27, 2009)
àà When XCAPI received a SIP response code 481 (Adddress Incomplete) it converted it to a
Q.850 cause code No User Responding when forwarding it to a CAPI application. This was
incorrect. The current version correctly maps it to Invalid Number Format.
àà If incoming SIP URIs contain a leading plus sign it is removed before converting the URI to a
phone number for internal processing.
XCAPI Release 3.3.99 (March 19, 2009)
àà Some Cisco gateways tend to re-establish RTP media streams from time to time. While this
behaviour is technically correct and unproblematic it still could lead to difficulties together
with SoftFAX operations. Such a re-establishment of media streams was interpreted as a small
gap in audio data which in turn caused the T.30 error correction mode (ECM) to become active. This unnecessarily lengthened fax transmission times. This behaviour has been corrected.
XCAPI Release 3.3.98 (March 16, 2009)
àà A new tweak setting has been added which allows an administrator to configure XCAPI in
such a way that it does not signal a call transfer having taken place to remote devices if
(and only if) at least one of the now connected parties has its phone number presentation
suppressed. This works around some issues with Siemens PBXes not supporting a call transfer
with restricted phone numbers.
XCAPI Release 3.3.97 (March 12, 2009)
àà XCAPI has been modified to enable it to transfer faxes which are available in high resolution
to devices only supporting low resolution without involving any actions on part of the CAPI
application.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
42
Release Notes
XCAPI Release 3.3.96 (March 11, 2009)
àà Inernal release
XCAPI Release 3.3.95 (February 24, 2009)
àà XCAPI now does not send any periodic SIP re-INVITE messages while in T.38 mode. Doing so
could cause fax transmissions to be interrupted when connected to certain SIP gateways.
XCAPI Release 3.3.94 (February 18, 2009)
àà When simulating a call transfer inside XCAPI an informational packet was transmitted to
remote devices informing them about the changed identity of the connected party.
Erroneously phone numbers that had been marked restricted by the CAPI application and/or
remote devices were transmitted within these packets with the restriction marker removed.
The current version changed this.
XCAPI Release 3.3.93 (February 16, 2009)
àà Prior XCAPI versions did not handle the SIP Session-Expires header field correctly in all cases.
It could occur that an INVITE message that was requested by such a header field was sent too
late by the XCAPI causing the call to time out. The current version does handle this correctly.
XCAPI Release 3.3.92 (February 12, 2009)
àà XCAPI 3.3.92 improves the mapping of CAPI functionality to SIP services and introduces the
possibility of restricting phone numbers with SIP controllers. Complying to RFC 3261 a free
text field with the value of Anonymous is sent in “From” header fields and a “Privacy” header
field is included with every SIP message.
XCAPI Release 3.3.91 (January 30, 2009)
àà This version permits CAPI applications evaluating the free text field from the “From”
header field by means of the Name Identification supplementary service.
XCAPI Release 3.3.90 (January 27, 2009)
àà If algorithmic DTMF recognition was enabled on audio data streams under some conditions
not all DTMF tones specified by Q.23 and Q.24 could be recognized properly. The recognition
rate was improved by changing the parameterization of the recognition algorithm.
This change applies to H.323, SIP and ISDN controllers all at once.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
43
Release Notes
XCAPI Release 3.3.89 (January 23, 2009)
àà Some SIP devices periodically send OPTIONS messages as a means to check whether XCAPI is
still up and responding. Prior versions of XCAPI sent and error message as a reply which could
lead to error conditions being signaled by the remote SIP device or even to failover taking
place. This version of XCAPI now responds to those messages properly.
XCAPI Release 3.3.88 (January 16, 2009)
àà The method used to count fax pages that have been transmitted without applying the error
correction mode (ECM) has been adapted to comply with the T.30 standard. The page counter
now is incremented only if the remote fax device acknowledges page reception. Prior versions incremented the counter after page transmission but before acknowledgement of reception. This generally improves robustness and enables applications to resume fax transmissions
that have been interrupted by bad line quality in the right place.
XCAPI Release 3.3.87 (January 16, 2009)
àà This version rectifies an issue that was caused by the previous version when used together
with Siemens HiPath 4000 PBXes. The changes applied there and the broader support
for the QSIG protocol could cause overlap dialing information to be interpreted incorrectly
by XCAPI.
XCAPI Release 3.3.86 (January 15, 2009)
àà When using both QSIG and H.245 Tunneling with Siemens HiPath 4000 PBXes XCAPI could
under circumstances generate invalid H.323 protocol messages. This was caused by some
Siemens specific protocol extension XCAPI supports and did not occur with other devices.
www.xcapi.de
Phone +49 5363 8195-0
Fax +49 5363 8195-999
44
Release Notes
Exclusion of Liability
Copyright © 2017 TE-SYSTEMS GmbH
All rights reserved
This document, in part or in its entirety, may not be reproduced in any form without the prior consent of TE-SYSTEMS GmbH.
The information contained in this document was correct at the time of writing. TE-SYSTEMS GmbH reserves the right to make
any alterations without prior notice.
The utmost care was applied during the compilation of texts and images, as well as during the creation of the software. Nevertheless, no responsibility can be taken for the content being accurate, up to date or complete, nor for the efficient or error-free
operation of the software for a particular purpose. Therefore, TE-SYSTEMS GmbH cannot be held liable for any damages resulting directly or indirectly from the use of this document.
Trademarks
All names of products or services used are trademarks or registered trademarks (also without specified indication) of the respective private or legal persons and are therefore subject to legal regulations.
Third Party Disclaimer and Limitations
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
This product includes cryptographic software written by Eric Young ([email protected]).
This product includes software written by Tim Hudson ([email protected]).
This product includes source code derived from the RSA Data Security, Inc. MD2, MD4 and MD5 Message Digest Algorithms.
This product includes source code derived from the RFC 4634 Secure Hash Algorithm software.
Copyright-Notices
All files included in this sample are copyrighted by TE-SYSTEMS GmbH.
All samples and the SDK may only be used in combination with the XCAPI-product.
The SDK contains code from libtiff with the following copyright-notice:
Copyright (c) 1988-1997 Sam Leffler
Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted
without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and
related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity
relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED „AS-IS“ AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING
WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER
OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
TE-SYSTEMS GmbH
Managing DirectorsAndreas Geiger
Oliver Körber
AddressMax-von-Laue-Weg 19
38448 Wolfsburg
Germany
www.xcapi.de
Phone +49 5363 8195-0
Tel.+49 5363 8195-0
Fax+49 5363 8195-999
[email protected]
Internetwww.te-systems.de
www.xcapi.de
Fax +49 5363 8195-999
45