Readme for system software 6.3.3 PATCH 2
========================================
========================================

The following changes have been made to our software since the release of system software 6.3.1. They have been included in system software 6.3.3 PATCH 2 which is available from BinTec's web server for all X-Generation Routers.


1. STAC and MPPC License
========================

With System Software Releases 6.3.3 and 6.3.4, the STAC and MPPC licenses are no longer included and activated by default in the delivery status of all BinTec routers. You can, however, obtain a free (combined) license from www.bintec.net. You will find the respective webpage in the Service/Support section.

2. IPSec - Pre Shared Key not Saved
===================================
After modification of a peer's pre shared key (PSK) in the menu IPSEC CONFIGURE PEERS EDIT and after saving the changes, the new PSK occasionally was not saved to the MIB.
The problem has been solved.


3. IPSec - Wrong Setting in ipsecDialTable
==========================================
Every time an IPSec peer was created with the Setup Tool, and ISDN Callback was activated for that peer during the initial configuration, a wrong interface index (0) was stored in the corresponding entry of the ipsecDialTable.
This problem has been solved.


4. IPSec - Peers Loaded twice from RADIUS
=========================================
The IPSec peers stored on a RADIUS server are retrieved every time, the router reboots or the IPSec daemon is reset (e.g. caused by a reconfiguration). The reset deletes all IPSec/RADIUS peers from the router so that upon the next retrieval all entries are stored only once. In a single case the IPSec/RADIUS peers were not deleted: If you reset the IPSec daemon with the command kill -10, the peers already stored were not deleted and double entries were created upon the retrieval from the RADIUS.
This problem has been solved.


5. IPSec - Field Descriptions
=============================
When editing an existing IPSec peer ( IPSEC CONFIGURE PEERS EDIT),the field descriptions of the menu could be focused with the cursor.
This problem has been solved.


6. SIF - Wrong Index Numbers assigned
=====================================
When adding or deleting entries of the ipSifAliasAddressTable or ipSifAliasServiceTable, the indices assigned were unpredictable. This occasionally lead to inoperative configurations.
This problem has been solved.


7. TAF - Authentication Freezes Router
======================================
In very specific cases a TAF authentication occasionally lead to a freeze of X8500. This occurred either if X8500 expected a client to perform a TAF authentication, but the client did not run the TAF application, or if the PPP shorthold was activated before the client had answered the TAF Keepalive message from the router.
This problem has been solved.


8. CAPI -  First Attempt to Send a Fax fails
============================================
Sending faxes basically works correctly, but occasionally the first attempt to send a fax fails. This occurs if a Remote Access Service (RAS) connection has been terminated or a data file transfer has been completed immediately before. A second attempt at sending the fax will be successful. 
This problem has been solved.


9. X.25 over CAPI - File Transfer Fails
========================================
When sending data across an X.25 over CAPI or over RCAPI connection, the file transfer sometimes files. This happens with specific clients only.
This problem has been solved.