Author Topic: Repeated connection difficulties  (Read 9250 times)

randomandy

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
    • View Profile
Repeated connection difficulties
« on: September 17, 2005, 04:24:31 AM »
I'm trying to get my first copy of CAM running for my client. Configuring was really simple and it works great but after a few hours keeps diisconnecting somehow. I'm not exactly sure what it is disconnecting from though.

What happens is that the CAM server keeps running just fine. I can view, report, search, etc. But the SMDR data stops being recorded without any warning as if no more calls were taking place even though they actually are.

We are connecting CAM to the phone switch (a Mitel SX200ICP(M2)) using the telnet option. So when this problem arose again today, I opened a command shell and did a raw telnet to the Mitel and had no problem connecting. The Mitel gave me the warning that the connection had been lost previously, and then dumped all the collected SMDR data in its buffer. So I think we rule out a problem with the Mitel.

While trying to get it running again today, we were interrupted by an extended power outage. When the systems started up again, CAM started working again too. A few hours later it stopped again. (by "working", I am still referring to the stopping of SMDR data reception.)

I'm not sure where the problem lies. It's possible there's some intermittant network issue on the host machine, but I am just as suspicious that CAM might be freezing up.

I'd like your assistance in understanding the log file in greater detail.
See my main log appended below:

After my initial successful launch, the SMDR stream stopped at around  09/14 07:43P
After about 09/16/05 16:35:45, following a power cycle, the SMDR stream was working again.
It stopped around 09/16/05 19:02

The lines I wonder about and would like to know the meaning of:
"The system cannot find the file specified."  What file is it looking for that it can't find?

I notice that when it doesn't work, what I get is "No connection could be made because the target machine actively refused it." I -would- think that meant telnet troubles except that when it -does- work, I see at the equivalent position in order the phrase "Database has been initialized successfully", leading me to wonder if the refused connection is actually referring to connecting to the CAM internal database rather than to another machine.

So please help me deduce what this could indicate.

Thank you

------------------------------
Code: [Select]
09/14/05 10:02:13 Starting...
09/14/05 10:02:13 2.6.1.95
09/14/05 10:02:13 Global\{270653-4249-A1A5-18ED0AF938FF}
09/14/05 10:02:13 SMDR library has been loaded successfully.
09/14/05 10:02:13 HTTP engine has been started.
09/14/05 10:02:14 Database has been initialized successfully.
09/14/05 10:02:14 Only one usage of each socket address (protocol/network address/port) is normally permitted.

09/14/05 10:02:14 Trying other port
09/14/05 10:02:14 Port 3771 has been opened successfully
09/14/05 10:02:14 Web service has been started successfully.
09/14/05 10:02:14 Intialization has been done.
09/14/05 10:02:14 The system cannot find the file specified.

09/14/05 16:26:58 Requested driver settings:
09/14/05 16:26:58 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/14/05 16:26:58 commport = Telnet
09/14/05 16:26:58 commxonxoff = 15
09/14/05 16:26:58 commdtrdsr = 10.100.0.5
09/14/05 16:26:58 exprops = Min
09/14/05 16:26:58 commbaud = 61321
09/14/05 16:26:58 commrowlimit = 13,10
09/14/05 16:26:58 drivername = Mitel SX-200 ICP(M2).js
09/14/05 16:26:58 driverrootpath = SMDR
09/14/05 16:26:58 pbxid = 1
09/14/05 16:26:58 driverdurcor = 0
09/14/05 16:26:58 Communication thread for Telnet has been started.
09/14/05 16:26:58 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/14/05 16:26:58 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/14/05 16:26:58 WARNING! Data after request done:

09/14/05 16:27:16 Driver library global.jsl[V.3.2] loaded.
09/14/05 16:27:16 Mitel SX-200 ICP(M2) [V1.0] driver loaded.
09/14/05 22:41:07 Port 3771 has been opened successfully
09/14/05 22:41:46 Port 3771 has been opened successfully
09/15/05 00:06:25 Driver library global.jsl[V.3.2] loaded.
09/15/05 00:06:25 Mitel SX-200 ICP(M2) [V1.0] driver loaded.
09/16/05 15:05:58 Driver library global.jsl[V.3.2] loaded.
09/16/05 15:05:58 Mitel SX-200 ICP(M2) [V1.0] driver loaded.
09/16/05 15:16:04 Communication thread for Telnet has been stopped: no extra error information available.
09/16/05 15:16:04 Requested driver settings:
09/16/05 15:16:04 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.6;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 15:16:04 commport = Telnet
09/16/05 15:16:04 commxonxoff = 15
09/16/05 15:16:04 commdtrdsr = 10.100.0.6
09/16/05 15:16:04 exprops = Min
09/16/05 15:16:04 commbaud = 61321
09/16/05 15:16:04 commrowlimit = 13,10
09/16/05 15:16:04 drivername = Mitel SX-200 ICP(M2).js
09/16/05 15:16:04 driverrootpath = SMDR
09/16/05 15:16:04 pbxid = 1
09/16/05 15:16:04 driverdurcor = 0
09/16/05 15:16:04 Communication thread for Telnet has been started.
09/16/05 15:16:04 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 15:16:04 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 15:16:05 No connection could be made because the target machine actively refused it.

09/16/05 15:17:50 Communication thread for Telnet has been stopped: no extra error information available.
09/16/05 15:17:50 Requested driver settings:
09/16/05 15:17:50 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 15:17:50 commport = Telnet
09/16/05 15:17:50 commxonxoff = 15
09/16/05 15:17:50 commdtrdsr = 10.100.0.5
09/16/05 15:17:50 exprops = Min
09/16/05 15:17:50 commbaud = 61321
09/16/05 15:17:50 commrowlimit = 13,10
09/16/05 15:17:50 drivername = Mitel SX-200 ICP(M2).js
09/16/05 15:17:50 driverrootpath = SMDR
09/16/05 15:17:50 pbxid = 1
09/16/05 15:17:50 driverdurcor = 0
09/16/05 15:17:50 Communication thread for Telnet has been started.
09/16/05 15:17:50 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 15:17:50 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 15:17:51 No connection could be made because the target machine actively refused it.

09/16/05 15:17:58 Communication thread for Telnet has been stopped: no extra error information available.
09/16/05 15:17:58 Requested driver settings:
09/16/05 15:17:58 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 15:17:58 commport = Telnet
09/16/05 15:17:58 commxonxoff = 15
09/16/05 15:17:58 commdtrdsr = 10.100.0.5
09/16/05 15:17:58 exprops = Min
09/16/05 15:17:58 commbaud = 61321
09/16/05 15:17:58 commrowlimit = 13,10
09/16/05 15:17:58 drivername = Mitel SX-200 ICP(M2).js
09/16/05 15:17:58 driverrootpath = SMDR
09/16/05 15:17:58 pbxid = 1
09/16/05 15:17:58 driverdurcor = 0
09/16/05 15:17:58 Communication thread for Telnet has been started.
09/16/05 15:17:58 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 15:17:58 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 15:17:59 No connection could be made because the target machine actively refused it.

09/16/05 15:21:04 Communication thread for Telnet has been stopped: no extra error information available.
09/16/05 15:21:04 Requested driver settings:
09/16/05 15:21:04 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 15:21:04 commport = Telnet
09/16/05 15:21:04 commxonxoff = 15
09/16/05 15:21:04 commdtrdsr = 10.100.0.5
09/16/05 15:21:04 exprops = Min
09/16/05 15:21:04 commbaud = 61321
09/16/05 15:21:04 commrowlimit = 13,10
09/16/05 15:21:04 drivername = Mitel SX-200 ICP(M2).js
09/16/05 15:21:04 driverrootpath = SMDR
09/16/05 15:21:04 pbxid = 1
09/16/05 15:21:04 driverdurcor = 0
09/16/05 15:21:04 Communication thread for Telnet has been started.
09/16/05 15:21:04 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 15:21:04 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 15:21:05 No connection could be made because the target machine actively refused it.

09/16/05 15:26:47 Port 3771 has been opened successfully
09/16/05 15:26:52 Port 3771 has been opened successfully
09/16/05 15:32:19 Communication thread for Telnet has been stopped: no extra error information available.
09/16/05 15:32:19 Requested driver settings:
09/16/05 15:32:19 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 15:32:19 commport = Telnet
09/16/05 15:32:19 commxonxoff = 15
09/16/05 15:32:19 commdtrdsr = 10.100.0.5
09/16/05 15:32:19 exprops = Min
09/16/05 15:32:19 commbaud = 61321
09/16/05 15:32:19 commrowlimit = 13,10
09/16/05 15:32:19 drivername = Mitel SX-200 ICP(M2).js
09/16/05 15:32:19 driverrootpath = SMDR
09/16/05 15:32:19 pbxid = 1
09/16/05 15:32:19 driverdurcor = 0
09/16/05 15:32:19 Communication thread for Telnet has been started.
09/16/05 15:32:19 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 15:32:19 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 15:32:19 No connection could be made because the target machine actively refused it.

09/16/05 15:41:34 Communication thread for Telnet has been stopped: no extra error information available.
09/16/05 15:41:34 Requested driver settings:
09/16/05 15:41:34 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 15:41:34 commport = Telnet
09/16/05 15:41:34 commxonxoff = 15
09/16/05 15:41:34 commdtrdsr = 10.100.0.5
09/16/05 15:41:34 exprops = Min
09/16/05 15:41:34 commbaud = 61321
09/16/05 15:41:34 commrowlimit = 13,10
09/16/05 15:41:34 drivername = Mitel SX-200 ICP(M2).js
09/16/05 15:41:34 driverrootpath = SMDR
09/16/05 15:41:34 pbxid = 1
09/16/05 15:41:34 driverdurcor = 0
09/16/05 15:41:34 Communication thread for Telnet has been started.
09/16/05 15:41:34 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 15:41:34 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 15:41:35 No connection could be made because the target machine actively refused it.

09/16/05 15:56:56 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

09/16/05 16:35:45 Starting...
09/16/05 16:35:45 2.6.1.95
09/16/05 16:35:45 Global\{270653-4249-A1A5-18ED0AF938FF}
09/16/05 16:35:45 SMDR library has been loaded successfully.
09/16/05 16:35:45 HTTP engine has been started.
09/16/05 16:35:45 Requested driver settings:
09/16/05 16:35:45 id = 1;pbxid = 1;pbxname = Mitel%20SX200-ICP;pbxdesc = ;drivername = Mitel SX-200 ICP(M2).js;driverrootpath = SMDR;driveriddthreshold = 8;driverdurcor = 0;commport = Telnet;commbaud = 61321;commdatabits = 8;commparity = 0;commstopbits = 10;commdtrdsr = 10.100.0.5;commrtscts = ;commxonxoff = 15;exprops = Min;isdeleted = ;commrowlimit = ;
09/16/05 16:35:45 commport = Telnet
09/16/05 16:35:45 commxonxoff = 15
09/16/05 16:35:45 commdtrdsr = 10.100.0.5
09/16/05 16:35:45 exprops = Min
09/16/05 16:35:45 commbaud = 61321
09/16/05 16:35:45 commrowlimit = 13,10
09/16/05 16:35:45 drivername = Mitel SX-200 ICP(M2).js
09/16/05 16:35:45 driverrootpath = SMDR
09/16/05 16:35:45 pbxid = 1
09/16/05 16:35:45 driverdurcor = 0
09/16/05 16:35:45 Communication thread for Telnet has been started.
09/16/05 16:35:45 TTYINFO {bByteSize:0;bFlowCtrl:0;bParity:0;bStopBits:0;dwBaudRate:61321;fConnected:1;fXonXoff:0;}
09/16/05 16:35:45 DCB {BaudRate:0;ByteSize:0;DCBlength:28;EofChar:0;ErrorChar:0;EvtChar:0;fAbortOnError:0;fBinary:0;fDsrSensitivity:0;fDtrControl:0;fDummy2:0;fErrorChar:0;fInX:0;fNull:0;fOutX:0;fOutxCtsFlow:0;fOutxDsrFlow:0;fParity:0;fRtsControl:0;fTXContinueOnXoff:0;Parity:0;StopBits:0;wReserved:0;wReserved1:0;XoffChar:0;XoffLim:0;XonChar:0;XonLim:0;}
09/16/05 16:35:45 Database has been initialized successfully.
09/16/05 16:35:45 Port 3771 has been opened successfully
09/16/05 16:35:45 Web service has been started successfully.
09/16/05 16:35:45 Intialization has been done.
09/16/05 16:35:45 The system cannot find the file specified.

09/16/05 16:36:06 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

09/16/05 16:51:09 Driver library global.jsl[V.3.2] loaded.
09/16/05 16:51:09 Mitel SX-200 ICP(M2) [V1.0] driver loaded.
09/16/05 16:51:09 Call parsing failed for call below:
09/16/05 16:51:09
09/16/05 16:51:09   ******  Check printout for possible data loss  ******

« Last Edit: September 19, 2005, 06:54:22 PM by randomandy »

sergey

  • Moderator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 48
    • View Profile
Re: Repeated connection difficulties
« Reply #1 on: September 17, 2005, 08:36:13 AM »
This is should be network related problem, meaning that the telnet connection goes down sometimes. The file related and database related messages in the log files has noting with the SMDR/CDR collection engine. They are usually logged at the system startup. The first one is logged when system can't find pipe for the tray icon utility and creates the default one, which is usual procedure on startup, and the second means that the system has connected to the main database and checked data integrity.

It would be really helpful if you could send us request for support from within CAM. To send it please do as follows:
- open Support/Send Log Files page
- fill fields on the page as necessary
- specify Extended Request for Support in the Request type field on the page
- press Submit request button to issue the request

Having the request data, we'll model the situation and fix the telnet listener to make it work in your environment.

Thank you for the feedback!

randomandy

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
    • View Profile
Re: Repeated connection difficulties
« Reply #2 on: September 17, 2005, 01:39:16 PM »
Some further information: In port settings I've set
"on lost connection, reconnect every ..." to 15 minutes and this does not help.
When it's in this disconnected state, I've gone and manually tried to reestablish the connection by saving a different port number and then changing it back again, but it doesn't fix anything.

I didn't understand your answer very well. Were you saying that the messages I asked about were normal and not indicators of what the problem was?


randomandy

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
    • View Profile
Changing port type works
« Reply #3 on: September 17, 2005, 09:43:01 PM »
I guess as mentioned in the last post, changing the port number and changing it back again did not reestablish connection. But this time I tried changing the port type to "TCP" (arbitrary), saving, and changing back to "Telnet" with the same settings as before, saving, at which time the connection immediately came back up again successfully. While this is a workaround, it is obviously unsatisfactory as a long term solution.

So to begin with, CAM seemed unable to recognize that it had lost connection or unable to do anything about it on its own. So the "auto reconnect" is of no use, really.

Which leads me to suggest a feature I think would be very valuable. Since call data can be of critical importance to some clients, it would be useful if there was a way to detect an absence of data during a specified time window - or better yet, some way to detect with more certainty that the connection to the data stream has broken. And then in the event alerts section, have it be able to automatically send an alert to the admin warning that the link may be down so s/he can at least do something about it before the PBXs CDR buffer overflows and the call data is lost permanently.

My client is liking this software with the exception of it being pretty useless if it can't stay connected for more than an hour at a time. So I appreciate any help you can give me in getting this resolved soon so I can close the sale and send you some money!

randomandy

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
    • View Profile
Re: Repeated connection difficulties
« Reply #4 on: September 19, 2005, 06:59:30 PM »
It dropped again. Later, I noticed that the stop had occurred right about the same time I was using the administrative interface. I had picked a different parser script and saved it. I don't know if that provides any more clues.

sergey

  • Moderator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 48
    • View Profile
Re: Repeated connection difficulties
« Reply #5 on: September 28, 2005, 07:45:51 AM »
Log files you sent us look clear, which means there is no any specific errors logged that may affect the telnet client. Sure, it may be disconnected from a PBX time to time, because network environment is just like that, but it should reconnet after loosing the connection in time specified in the 'Reconnect Every' field.

Maybe the reason is that you expect it to reconnect immediately after loosing the connection, but it actually waits the time specified in the above field. Please try to put in the 'Reconnect Every' field '1 Min' so it will attemnt to reconnect every 1 min in case of lost connection.

Also every time you press Save button on the Configuration/PBX Communication page system reinitializes data collection subsystem, that's why in case there is no connection to the PBX you get error message on changing driver/parser.

In next release we'll put there 'Reconnect immediately option'.

Thank you very much for the feedback! Every one of them is greatly appreciated.

randomandy

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
    • View Profile
Re: Repeated connection difficulties
« Reply #6 on: October 08, 2005, 06:06:59 PM »
No I definitely waited longer. In the first case it was stopped for two days before I noticed. In the second case I was more attentive, and noticed it after a few hours. My auto reconnect was set to only one hour, at most.

It's been working ever since (a couple weeks by now), so who knows what happened.

Regardless, the experience showed me how important it would be to have a feature that would send an alarm email if no SMDR events log for a specified duration of time.  For example, with this customer, I know that if no events log on a weekday for more than 30 minutes, there is definitely a problem. This is for a call center that needs call records for liability reasons, so it is very important we don't miss the data.

Regardless of where in the system chain the failure occurs (CAM software, network stack, ethernet, PBX, etc), the alarm feature is needed. Since CAM is doing the logging, it is the only piece that will detect the failure.

sergey

  • Moderator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 48
    • View Profile
Re: Repeated connection difficulties
« Reply #7 on: October 10, 2005, 09:02:24 AM »
Thank you for the feedback!

We'll implement this feature in one of next releases of Call Accounting Mate.