Lines Report Busy

gsd · **Joined:** Wed Jan 18, 2006 2:10 pm **Posts:** 2

Gurmit Dhaliwal wrote: We have a customer who is experiencing lines reporting busy. The customer has a 4 port telelow 2003 which connects to a Progress database. The customer is using a Dialogic D4PCIU voice card. The customer has had the lines tested and they seem to be OK. Once Teleflow is re-booted the busy line problem go away (for awhile) When we check the log for Teleflow we see the following: Dec 19 09:23:13.82: [29] Set Local Variable Dec 19 09:23:13.82: Setting local variable '@TELEDATE' to '12' Dec 19 09:23:13.82: [25] Math Dec 19 09:23:13.82: @TELEDATE = @TELEDATE CAT /@DATEDAY Dec 19 09:23:13.82: @TELEDATE = 12 CAT /18 Dec 19 09:23:13.82: Setting local variable '@TELEDATE' to '12/18' Dec 19 09:23:13.82: [26] Math Dec 19 09:23:13.82: @TELEDATE = @TELEDATE CAT /@DATEYEAR Dec 19 09:23:13.82: @TELEDATE = 12/18 CAT /2005 Dec 19 09:23:13.82: Setting local variable '@TELEDATE' to '12/18/2005' Dec 19 09:23:13.82: [2] FINISH Dec 19 09:23:13.82: Defaults<==ChangeDate Dec 19 09:23:13.82: Setting global variable '@YESTERDAY' to '12/18/2005' Dec 19 09:23:13.82: [2] FINISH Dec 19 09:23:13.82: Main<==Defaults Dec 19 09:23:13.82: [7] DB Connect Dec 19 09:23:13.82: ConnectString: DSN=GXP30;UID=sysprogress;pwd=sysprogress Dec 19 09:23:14.75: ERROR: Connect: SQLConnect failed. Dec 19 09:23:14.75: SQL Error State: HY000 Native Error Code: FFFFB10C ODBC Error: [DataDirect-Technologies][ODBC PROGRESS driver][PROGRESS]Error in Network Daemon Dec 19 09:23:14.75: FAILURE Dec 19 09:23:14.75: ERROR: Missing next step Dec 19 09:23:14.75: FATAL Dec 19 09:23:14.75: Attempting to jump to Fatal Error Global Event label: 'BIGEND' Dec 19 09:23:14.75: [19] Label Dec 19 09:23:14.75: Label: BIGEND Dec 19 09:23:14.75: [218] Hang Up Dec 19 09:23:14.75: [21] DB Disconnect Dec 19 09:23:14.75: [60] Write Text Dec 19 09:23:14.75: FATAL ERROR DETECTED! (2005/12/19, 09:23:14) Dec 19 09:23:14.75: Dec 19 09:23:14.75: [116] Wait Dec 19 09:23:14.75: Waiting 60000 milliseconds Dec 19 09:24:14.75: [22] FINISH Dec 19 09:24:14.75: End of application. Dec 19 09:24:14.75: XMLList destructor done Dec 19 09:24:17.76: One possibility is that an error is causing the ODBC connection between Telflow and the database to be lost. Therefore, when this error occurs, a line is lost (reports as busy). Teleflow monitor though shows all 4 lines as available. Do you have any idea of what the problem might be?

Chris · **Posted:** Wed Jan 18, 2006 5:07 pm

From the log, it appears that for some reason, your DB Connect step is failing. If it is doing this each time the line starts, TeleFlow never gets to Wait For Call, and that line remains busy. It appears that when an error is generated in your application, your have a 60 second wait. Since you have hung up before that Wait, that line is available as far as the Telco is concerned, but is not waiting for a call. This would cause busy signals for that 60 second time period. Are you hitting the DB Connect step prior to every Wait for Call? This may be causing problems. Connect once, and stay connected, even between calls. Optionally, use a DB Disconnect before your DB Connect to ensure it is successful. (Well, unless there is an external factor creating a problem with the database connection, of course)