<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:10pt"><div style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-size: 10pt;">Looks like an Asterisk 1.4 option?<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Tilghman Lesher <tilghman@mail.jeffandtilghman.com><br>To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users@lists.digium.com><br>Sent: Wednesday, May 21, 2008 4:39:24 PM<br>Subject: Re: [asterisk-users] Asterisk Database Handling<br><br>On Wednesday 21 May 2008 17:02:07 Alex Balashov wrote:<br>> Douglas Garstang wrote:<br>> > We are sending CDR's to MySQL via odbc. It seems that Asterisk is<br>> > sometimes dropping CDR's, and they aren't being sent to the database<br>> > (they ARE in
the Master.csv file though). We suspect that when the MySQL<br>> > socket is idle, it gets disconnected, either by the MySQL server or by<br>> > our firewall, and when Asterisk goes to send the next CDR over the<br>> > socket, does not re-open the database, and drops that CDR. Possibly on<br>> > the next call, it connects ok and sends the next CDR.<br>><br>> Isn't there a keepalive option somewhere for cdr_mysql.conf, or failing<br>> that, a keepalive mechanism that can be enabled for TCP connections on<br>> the server side?<br><br>Please check the 'idlecheck' option in res_odbc.conf.<br><br>-- <br>Tilghman<br><br>_______________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a
href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></div></div></div><br>
</body></html>