Minimal Versions:
ACDBar_1_0_299_2012_10_11
ACDBar_1_0_284_2012_07_20 - this version can't edit ReadOnly flag in ACD_Groups.
ACDBar_1_0_223_2012_06_26 - no user status visible on ACDBar.
ASP_CTI_Journal_1_0_2_2010_10_04 - does not work, network messages changed. See TeliWeb position now.
BCI_CAP_1_0_12_2010_03_17
BCI_RefIdent_2_0_354_2012_05_17
BCI_RefIdent_2_0_352_2011_12_23 - no accepts chars * and # in CompleteNumber function
BCI_TAXA_2_0_15_2011_08_17
BCI_TAXA_2_0_6_2011_05_26 – read pbinisrv.mdb when search
CCU_1_0_1429_2013_08_20
CCU_1_0_1018_2013_01_15 – If CLIP no screening is active, calls with a restricted phone number from CCU will have a CCU’s MSN as Caller ID instead of an empty number. A wrong Called ID will be used in such case as well.
CCU_1_0_951_2012_12_13 – no service multiple (for user) VoiceBox messages management
CCU_1_0_938_2012_11_29 – no service TeliRemote type CCU; no service VoiceMessage(replay recorded file)  when PlayMsg_CallDirection=incoming; no service RecordMessage when PlayMsg_CallDirection=incoming 
CCU_1_0_918_2012_11_20 - problem with TeliRemote calling +49nnn, problem with protocol details
CCU_1_0_856_2012_11_09 - no service TeliRemote CallBack
CCU_1_0_763_2012_06_15 - no Random redirection possible with WaitingQueue (numbers will not be shuffled by CCU).
CCU_1_0_655_2012_06_03 - While redirecting to waitingQueue or VoiceBox CTI_Server will not parse destination number sent to CCU (wont remove "A","T", "R" signs, wont create LCR number, wont add "[]" for VPN users)
CCU_1_0_652_2012_04_18  - WaitingQueue does not work
CCU_1_0_650_2012_04_05 – does not send CalledId for replace in consult call protocol record
CCU_1_0_644_2012_03_24 - no service view TryAndConnect calls in CTI_Journal in properly colors.
CCU_1_0_487_2011_12_23 – no service FallBack type “Transfer” so all FallBack will VoiceBox type.
CCU_1_0_458_2011_12_13 – doesn’ t use default voicebox message from user property
CCU_1_0_403_2011_05_06 – Default: does not work with Play recorded messages (“VoiceBox/PlayMsg_CallDirection=<incomming>”) – possible to configure and will be work as outgoing: [HKLM_CTIS]\VoiceBox "PlayMsg_CallDirection"="<outgoing>"
TeliBar_2_0_5248_2013_06_27
TeliBar_2_0_5068_2013_03_25 - TeliBar/TeliMan will not update the info displayed on buttons when another user logs in in the multi-user mode. TeliBar/TeliMan will not update its status rights when they change during another user’s login.
TeliBar_2_0_5059_2013_03_19 - The user will not be able to log in by user name when there are several lines assigned to them.
TeliBar_2_0_4573_2012_11_19 - This version of TeliBar will not be able to send status enable request and respond and will not update database with new required columns. It may cause a lot of problems during client buttons management
TeliBar_2_0_4547_2012_11_13 - This version of TeliBar will not be able to automatically configure SIP softphone when receiving messages from CTI_Server.
TeliBar_2_0_4536_2012_10_29 - This version of TeliBar will not be able to automatically configure TeliVideo when receiving messages from CTI_Server.
TeliBar_2_0_4520_2012_10_22 - TeliBar will ask for active ACDAgents count for ACD groups, but CTI_Server will log error about not know network message.
TeliBar_2_0_4501_2012_10_11 - TeliBar will not be informed about TeliRemote changes made in other clients (TeliWeb). This may cause it to display out-of-date properties on the TeliRemote button.
TeliBar_2_0_4464_2012_10_02 - ACD Group tray will not work in Client (group list in CTI_Client tray will be always empty - new network message). New ReadOnly mechanism for ACD Groups will not work.
TeliBar_2_0_4407_2012_09_11 - No TeliRemote VirtualCall mechanism, if mechanism is turned on in CTI_Server it can cause problems (virtual busy state, no protocol call, not visible call button)
TeliBar_2_0_4243_2012_06_18 - doesn't work Ctrl+X, ExtraField with ;
TeliBar_2_0_4238_2012_06_08 - CTI_Client does not contain ACDGroups tray menu. Not possible to change active state on groups by CTI_Client.
TeliBar_2_0_3999_2012_05_15 - no accepts chars * and # in CompleteNumber function
TeliBar_2_0_3995_2012_05_09 - TeliBar will not be able to delete user external absence even though CTI Server supports that.
TeliBar_2_0_3994_2012_05_09 - TeliBar does not delete the logged user's external absence when the Outlook MAPI feature is switched off.
TeliBar_2_0_3991_2012_04_05 - When several users are assigned to the same line number (using the LoginExceptions registry key of CTI_Server) and the Windows-integrated authentication mode is active, then CTI Server will not update user credentials (user name, name1, name2, e-mail) in the database and in its memory after a successful login.
TeliBar_2_0_3935_2012_04_05 - CTI_Server renamed Client SQL database columns, this Client will not work with SQL database (New columns: UserSpeedDials, UserPlaner, UserDesktops, UserDesktopsGroups)
TeliBar_2_0_3896_2012_03_28 - If server authentication mode is changed to the domain authentication mode, this TeliBar version will not be allowed to log in.
TeliWeb 2_0_972 / 13.08.2013
TeliWeb 2_0_645 / 31.01.2013 - TeliWeb users will not be able to log in.
TeliWeb 1_0_39 / 17.10.2012 - TeliWeb will not be able to set user absence status and TeliRemote configuration.
TeliWeb 1_0_37 / 27.09.2012 - TeliWeb will not be informed about TeliRemote changes made in other clients (TeliBar/TeliMan). This may cause it to display out-of-date settings in the TeliRemote page.
TeliWeb 1_0_36 / 27.09.2012 - This is a temporary TeliWeb version. Incompatible network messages. Communication between CTI-Server and TeliWeb will be impossible.
TeliWeb 1_0_29 / 20.08.2012 - Incompatible network messages. Communication between CTI-Server and TeliWeb will be impossible.
TeliWeb 1_0_24 / 11.07.2012 - It will be impossible to log in because CTI-Server expects a hashed passwords.