[Openh323gk-developer] Logging and tracing

[Andreas S. <and...@ri...>]

Hi,

At the Free software / open source telephony summit, Michal, Jan=20
and I discussed ways of making the logging and tracing of GNUgk=20
much better. I have now tried to make RasSrv.cxx and=20
ProxyChannel.cxx a little more consistent in the way information=20
is being traced.

I have worked a little on it yesterday evening and I'm still not=20
100% satisfied with it, but here's at least a first shot at the=20
levels at which information is being traced:

Level		Information
1		errors
2 		CDR
3 		ingoing/outgoing message summary and policy decisions
4 		network traffic (H.225/H.245/RADIUS) message detail
5 		minor stuff

At the moment I'm thinking of moving CDR to level 5 or 6, because=20
this is already available via either RADIUS or writing to a=20
seperate file. Policy decisions is stuff like, rejecting a call=20
because password is incorrect, replacing one registration with=20
another, because endpoint got new IP adress, etc. The application=20
level decisions in general.

It would then be possible to split level 3 into two, with policy=20
decisions at level 2 and network summary at level 3.

This would make the levels like this:

Level		Information
1		errors
2 		policy decisions
3 		ingoing/outgoing message summary
4 		network traffic (H.225/H.245/RADIUS) message detail
5 		minor stuff

Levels 1-3 are one liners, level 4 or 5 can be more than one line.


Examples (these are more or less bogus):
1	Cannot connect to H.245 port at <ip>:<port>
1	Could not find Call Identifer in CONNECT from <endpoint id>
2	Exceeded call limit for endpoint <endpoint id>
2	Rewriting e.164 <number> to <number>
3	H.245	masterSlaveDetermination from <ip>:<port>
3	RAS	AdmissionRequest from <ip>:port>
4	RAS	admissionRequest {
		sequenceID : 1
		call identifier : jsadhvhfwae8034q
	}
4	H.245 UserInputInformation {
		string : "0"
	}
5	CDR|342153246|q345|<ip>|whatever
5	Trying ParentPolicy
5	Couldn't find call id, but CRV was avalailable, so no problem

My main goal is here to see which messages an endpoint sent, because it =
is=20
at the moment almost impossible to find out using grep. Also why certain =

decisions are being taken.

--=20
Andreas Sikkema "A program that has not been specified cannot be =
incorrect; it can only be surprising ." Proving a Computer System Secure