This file describes the changes made to the TeleButler Runtime since version 04.10.17 : (Release TeleButler 4.0) -------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.23 dd 26/02/2001 (update of TB 4.0) - problem concerning the use of a pager in a digital environment is solved - reconnect to the database after an error in the execution of a stored procedureplay uninterruptable is corrected - transfer-problem Hicom PBX solveddial-out on lines specified via entry OutboundLines in Telebutl.ini (also for pager, voicemail, dial-out start, ...) - possibility to run as a service under system account (also dynamic updates). Now, the path were the product is installed must be entered manually in the registry. In the future, this will be done with the following installation procedure. - on-hook detection with the digit entered to stop a recording - if after a dial-out, the line is disconnected very fast, the dial-out database is set in the right state - date-format problem solved - some dial-out problems are solved - problems concerning project names, containing a dot are solved ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.27 dd 02/03/2001 (update of TB 4.0) - dial-out problem with database error concerning unique_id solved - long username and password accepted - memory problem + hanging program caused by SQLDescribeCol is solved - more dial-outs in one backtask, configurable with parameter MaxDialouts in telebutl.ini ([ODBC]) - dial-outs possible for more than 32 lines now ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.30 dd 02/04/2001 (update of TB 4.0) - a list of e-mail addresses can be used now - not found branch added for odbc-actions (can be used with gui 4.1) - some memory leaks are removed (ODBC) - dependencies for running as a service is reviewed (dependency of fbase and of sentinel) - new sc and tl resolve crash by big projects - new isdn-libs for transfer in dial-out sheet ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.35 dd 08/05/2001 (update of TB 4.0) - when working with variable databases, blocking lines before reconnect is removed - clear pending digits before play internal/external announcement. Due to pending digits, the announcement could be interrupted immediately. - when working with more than 1 variable database, problem connecting to the right database solved - new entry maxlogfilesize added to telebutl.ini to maximize the size of the TR-logfiles - the total time to get the dial tone after sending a hook flash by a transfer has become 5s (before : 2s) - crash serial communication PBX solved, some buffer sizes are adapted - exported function RT_GetODBCErrorFlag(int line) added to check if database-actions have failed on a certain line. This function has to be used via an axxium-dll in the call termination sheet. - date and time registers adjusted when passing midnight - forward and rewind problem while listening to voicemail messages is solved - limit of maximum 96 lines is removed. There's still a limit due to restrictions of the runtime screen, a new runtime screen is developed. - problem voicemail database recover procedure is solved ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.46 dd 22/06/2001 (update of TB 4.0) - Avoid double call to CreateObject of an X-icon. - if a voicemail message is not recorded, no notification will be sent. Also the logging changed in this situation. Before getting the file length of the message, there's a check if the message is really recorded. no more logging of 'VoicemailToEmail succeeded' if no e-mail is sent. - new speakf and config libs (crash solved) - if running as a service, the lines will be blocked before stopping the application. - there are 2 new call_types, auto reply and answer auto reply to reply on a PBX command with dtmf-signals - the expiry date and company name of the registration key is checked - memory leak removed out of ODBCDialout (backtask) - in free_sql, it's now possible to execute functions with variables as argument ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.50 dd 13/07/2001 (update of TB 4.0) - the constant DDI_LAYOUT is increased to 50 (it was 30), which determined the maximum number of ddi_layout_entries - memory leak out of ATP_BEGCALL, concerning initializing MWI - memory leak solved by working with variable databases (with username and password) - memory leaks solved in the ODBCDialout - reorganization of ODBC Dialout part, f.i. for working with SQL database, for automatic reconnect after connection failure. - bug solved, concerning blocking lines problem - configuration files for Ericsson PBX added ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.62 dd 31/08/2001 (update of TB 4.0) - ASR problems (could not find ini file rc152 for Capi) fixed - buffers for dtmf-signals by the start of a call are made bigger to resolve a crash (f.i. Nato Izmir) - logging of 'VoicemailToEmail failed' has become an errorlogging (it used to be tracelogging) - invalid mailboxes or extensions : the range with mailbox 0 is now also taken into account - the time-out message or the errormessage in the language-state is spoken out in the default language now. - a call, that is in the play state, is now stopped immediately after a disconnect. - the asr for namedialing works now under Win2000, also the new dll's are necessary - problem in backup voicemail database is solved ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.79 dd 22/10/2001 (update of TB 4.0) - 2 dial out problems solved that caused crashes ; by dial out database and no connection, an incoming call caused a crash. - disabling all lines is possible again - some extra checking is used in the voicemail to avoid a crash when the voicemail database is not ok - Error solved concerning odbc. This error occurred when a new project was launched without odbc dial out & the current project did have ODBC-dial out after a record, the timeout counter has been reset, so the record-state can be used in a loop - Pronunciation of dates where year-format is y or yy, is now ok. - Voicemail problem solved, when editing more than 1 mailbox during one call. The consequence was that the mailbox stayed 'in use'. After restart of the runtime, this could lead to "Error in VMGetMsg" and the sentence "due to a technical problem ..." - support the choice between ignoring and refusing an incoming call (e.g. Trius) and support of multiple event dll's - audio-files in e-mails don't contain echo or noise anymore at the end ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.83 dd 31/10/2001 (update of TB 4.x) - review of date/time functionality, possibility to use a Date/Time field from a database and speak out this date/time !! Pay attention concerning the time format !! 'h' means now 12-hour format and 'H' means 24-hour format, so if you use time-format hhmmss, you should change this to HHmmss to stay compatible. This can be set by Options - Date\Time format in the user interface. - problem sending e-mails in Win95/98/Me is solved - problem in generating the files for name dialing on analogue boards is solved - calculation state with negative numbers is fixed ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.95 dd 29/01/2002 (update of TB 4.x) - avoid playing of a file (wait music) after a transfer connect (Trius) - possibility to activate fast outgoing calls by parameter fast_outgoing_calls in telebutl.ini (under [PBX]), only on analogue lines - timeout problem solved while playing data on non-AvM boards (capi) - free sql statement (UPDATE/INSERT or DELETE) ok with query-lengths > 256 characters - 'if' state with positive and negative numbers as values and as variables is corrected - fixes hanging runtime when caller disconnects just at the beginning of the beep that announces recording (capi) - menu state : with multiple digits, 2 digits and follow branch immediately can the variable be 1#, the # was not removed. - when somebody listens to a message in his mailbox and goes on hook, it was possible that the MWI was switched on (capi) ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.10.99 dd 06/03/2002 (update of TB 4.x) - problem when using multiple odbc-states with a 'No records found' branch, is solved - sql-functions, that don't return rows can be used - more logging, concerning voicetoemail - deathlock after blind transfer is avoided (CAPI) - call releases outgoing calls under heavy load are working ok (CAPI) ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.11.69 dd 10/01/2003 (update of TB 4.x) - fixes a deadlock at a blind call transfer on CAPI - fixes following problems for dialogic digital hardware * improved state machine to obtain stable behaviour under load * solved crash at blind transfer to busy extension * handle facility information element containing call diversion inforamtion - some modifications in transfer via dtmf call control to make the on-hook detection better (analogue hardware) - memory leak in ODBC solved when the connection to the database could not be established - also fixes endless loop of MWI requests based on cause code from PBX (Hicom 150 problem VDE, MWI was switched off at 2nd message instead of on) - play-back of a speech file with variable content in the dial out state (transfer state with dialout option) is working now - loggingtype concerning X-icon has changed to 'p' - problem that the actions in the termination sheet are sometimes not executed is solved (Dialogic digital and CAPI hardware) - warning logged when mailbox is full - improved DTMF stripping algorithm after recording (CAPI hardware) - fixed bug in call transfer via tromboning when using multiple controllers (CAPI hardware) - Calling number is set on Dialogic digital hardware - there has been a problem that no more files are played after stopping a the playing of a file with a digit; this is solved - terminating character for stored procedures is now configurable with the parameters EnableStoredProcTermChar and StoredProcTermChar in telebutl.ini [ODBC], the default terminating character is ; f.i. if EnableStoredProcTermChar=1 and StoredProcTermChar=! - the mailbox that is linked to the calling or called number is now determined by taking the last digits of this number. the number of digits taken, is now equal to the number of digits in extension, with a maximum of 4 digits - new feature on CAPI : Calling party number for Blind call transfer has been made configurable - Bug: unrecorded voicemail (none of the voicemails was stored) is solved. - Timeout by call screening is now interpreted as a no answer for the caller - fixed bug dynamic update (old project was still used) - fixed bug when recording is terminated with a digit during the pre-recording beep (CAPI hardware) - implementation of single line license by disabling line notification through configuration - problem with stopping message recording project is solved - faster switching from one project to another - blocking lines problem solved when dialing out from queue element, like a pager, a voicemail dial out, a normal dial out,... - crash solved when more than 16 msn-numbers were selected - improved DTMF recognizer (for CAPI) - loggings changed concerning saving and deleting of messages; there was confusion when the welcome message was saved or not, when keeping the message was not confirmed by the caller. Not confirmed is not saved. - problems solved with speaking out of dates (problem concerning daylight savings time) - dumping the content of the variables for a line could crash when a variable contained > 256 characters, solved, but there's a maximum on 1024 - problem solved using CLI with the retrieve of the calling number (ANIS) (analogue hardware) - crash solved during supervised call transfer (CAPI hardware) - bug solved when using a timed action with an annual period that includes the year boundary - use of projects with a long path is working now, the path can now contain up to 256 characters - leading zero's are removed from the voice mail dial-out number (when only zero's, they are not removed). When somebody enters the number 0013, 13 is called now when a message arrives instead of 0013 - new feature on ISDN hardware (CAPI or Dialogic digital) : overlap receiving - CAPI : made Bearer Capability and High Layer Compatibility information elements of MWI SETUP message configurable - CAPI : only taken first cause value into account when a PBX sends two cause values. - new feature on CAPI : new synchronisation mechanism to play speechfiles when using remote CAPI hardware (Bintec, TheBox, ...) - CAPI : fixed bug in channel identification detection algorithm ------------------------------------------------------------------------------------------------------------------------------------------- TeleButler Runtime version 04.11.83 dd 16/04/2003 (update of TB 4.x) - Transfer state with dial out option: playing a combination of variables in an outgoing call. - Projects with long pathnames - Timed action state with an annual period, containing the bridge between two years - A call, created via call tromboning is now stopped when reaching the maximum call duration. - Database reconnection is avoided for the indicated SqlState errors for which no reconnection should happen - Free SQL statement: input variables can be used on the right side of arithmetic operators (^,+,-,*,/,%) - Free SQL statement: database reconnection happens when the execution of a free SQL statement fails (if it is configured to do so) - Possibility to record to a vox-file (for Dialogic) or cal-file (for CAPI) with a chosen filename. This name (with the extension) must be delivered via a variable. Such a file can also be played in the play state. - Asynch play on analogue and CAPI platform - When simultaneously transferring two calls it is possible that some PBXes refuse to set up the second consultation / blind call with cause 'channel not available'. Now Axxium / TeleButler automatically retries to set up this call again after a while, until the PBX accepts it. ****************************************************************************************************************************************** In case you want to report problems to our support team please do the following : Add under Options/Logging the following logging type : Debug Information If you can reproduce the problem, you should delete old logfiles and reproduce the problem after setting LogType to the correct value. If you cannot reproduce the problem, you should simply follow the following advise. If a problem needs investigation you should send us : 1) Log files from the LOGGING directory - if it is a problem that occurred a few days ago it is wise to send all logfiles. - if you know on what day the problem occurred, the logfiles of that day might be enough. 2) Often it is wise to send all project files too (all files from project directory), for example if it has to do with the intelligent start state. 3) The TELEBUTL.INI file is always nice to have. 4) !!!! Very important is also a very clear and complete description of the problem. It is better to send us too much details than not enough details. You can also send a collect-file of course. The problem might be that the file is too big. I think in most cases sending a collect file is not necessary. If it turns out that a problem is very difficult to solve we can always ask for it. It is always wise to make the collect as soon as possible even if you do not send it yet, because logfiles older than 10 days are deleted. You make a collect file by executing "collect" in the TeleButler directory. Mail the collected information to support.europe@voxtron.com.