<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi All!<div>I have a rock solid 1.4 Freeswitch installation for which I decided to save CDRs directly into a MongoDB "database" (2.6).</div><div><br></div><div>What I found is that sometimes some CDRs are not written to the DB and I do not have any alert log...scary! </div><div>How did I found that some CDRs are not written? Because I was making some test calls tracing with Wireshark and later on I was checking those CDRs into the MongoDB database...but no CDRs found for 2 calls on my tests...again scary!</div><div><br></div><div><br></div><div><br></div><div>I've read some documentation regarding the Mongo way to ACK and notify the client making insert about succesful/failed insert (in this case Mod_cdr_mongodb), but is there a way for having the Mod_cdr_mongodb to log failed insert into a text file so I can check/insert them later?</div><div>For example something like that:</div><div><br></div><div><font class="Apple-style-span" face="Courier"># cat mongo.failed.log</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier">db.cdr.insert([{ _id: 20, sip_call_id: "b3fc6282-c584-1232-5b8e-782bcb67544e", billsec: 50, duration: 65 ............................. },], { ordered: true })</font></div><div><br></div><div><br></div><div>For a failed log like this I can simply run a batch script to import failed insert.</div><div><br></div><div><br></div><div><br></div><div><br></div><div>At the moment I found that other methods for writing CDRs give less informations (CDR_CSV) or much back work to process CDRs (CURL or XML)</div><div><br></div><div><br></div><div>Thank you</div><div>Max</div></body></html>