BinTec Communications AG                                   Nuremberg, 2001/07/09

This document contains history of release 5.2.3.


Release 5.2.3 beta 1 2001/04/10:

This release basically is a release 5.2.1 with add-on of new TAPI functionality
"Enhanced TAPI control of system phones CS300".
That allows for system phones as the only ISDN phones to control call answering,
hold/retrieve of calls, 3-party conferences and call initiation via TAPI.
The latter - if invoked in state on-hook - causes system phone to automatically
enter hands-free calling mode and - after termination of call - idle mode again.
Like for release 5.2.1 system phone functionalities are only available for
full and correct configuration on system phone as well as on XCentric.


Release 5.2.3 2001/07/09:

PABX related modifications/bug fixes:

  o dial informations during connection no longer garble calling/called party
    number in isdnCallTable and isdnCallHistoryTable
  o MSN configuration problems in system phone now reported as syslog messages
  o fixed bug in concurrent PABX tracing (more than one "trace -P ..." a time)
    that could lead to a panic eventually

Miscellaneous Modifications and Fixes:

  o X.31 within D channel now works
  o CAPI: fixed problem of refused supplementary services after certain number
    of invocations
  o TAPI: under some circumstances TAPI calls weren't associated with the right
    extension, thereby confusing TSP on PC
  o errors in ISDN layer 2 drivers fixed that could lead to a system panic


VERY IMPORTANT:
===============

1. System phone firmware version 1.16 or newer is needed in addition to this
   XCentric release to take advantage of new feature. It can be found on BinTec
   web site www.bintec.net: get file cs300v116.zip unpack it and apply cs300.hex
   to CS300 via download center.

2. XCentric checks system phone status upon TAPI registration of PC. If either
   system phone is not correctly configured (on XCentric or phone) or hadn't
   completely registered at XCentric at that point of time, XCentric would not
   signal enhanced features towards PC and, hence, system phone would be TAPI
   controllable only as restricted as a normal ISDN phone.
   In case configuration is completely and correctly done on XCentric it might
   be necessary to reinitiate TAPI registration on that PC by invocation of
   "Remote Clients Configuration" tool. Confirmation of TAPI settings there
   (tab "Remote TAPI") will result in re-registration and bring PC up-to-date
   concerning TAPI settings.



Known issues:

  o ISDN three party conference is not available if one or more CAPI connections
    were participating
  o ISDN feature ECT (explicit call transfer) doesn't work properly when
    transferring to a CAPI connection (transfer itself will succeed, but CAPI
    connection won't receive any B-channel data afterwards)