Hi
tracing is quite
easy - just start gnugk with the option -ttttt. Than it logs all its output to a
logfile in your gnugk directory.
Understandy the
trace is not that easy. At basic knowhow of h323 would be very usefull.
Nevertheless, you could search the logfile for the CDR record of the call
that gets disconnected. Just before the CDR record in the log you might find a
DRQ or a DRJ (with a release or a reject reason) or any other kind of error
message.
If you manage to
log a call dropping then send the log to the list (it would be very useful to
see the whole call, from call setup to tear down).
-
Frank
From: openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Code Nirmata
Sent: Saturday, December 10, 2005 7:09 AM
To: GnuGK User Forum
Subject: To Frank Fischer about dropping calls automaticallyHI Frank Fischer,
As your opinion, I debuged tarce level 5 and I also visited previous mails
on this mailing list about dropping calls,you said there to send you the
accurate part of log file to find out the problem but I can't identified that
part (as I am a newbie). Please describe me that how can I find out
the problems from my log file,i.e, from where and how I can trace who
and where and how dropped the calls-the dialer,GnuGK or quintum.
Please....and....Thanks.....
Yahoo! Shopping
Find Great Deals on Holiday Gifts at Yahoo! Shopping
