CDR does not provide disconnect cause, but if you compile sources with HAS_ACCT=1 and have some basic skills in programming, you can manually add to CallRec::GenerateCDR function printing of disconnect cause - it is stored in member variable CallRec::disconnectCause. Be aware that changing CDR output may break compatibility for some existing scripts that process CDRs from status line (if you are using any). ----- Original Message ----- From: "Nir Simionovich" <nirs@m-wise.com> Sent: Thursday, September 04, 2003 10:04 AM Subject: [Openh323gk-users] CDR Question > Is there a way to know the reason for disconnection of a call via the > CDRs ? > I know that I can run a 'debug trc 4' or run gnugk with -tttt options, > but I don't > want to save logs from here to honololo. Does the CDR of an unconnected call > provide that kind of information? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
