Syslog suggestions

Started by oleg, March 21, 2011, 06:59:38 PM

Previous topic - Next topic

oleg

I have already mentioned lack of logging in some situations, but would repeat and add more...

I have running build 1892 and syslog configured at level 7 (supposedly most verbose) and I miss the following:
- STUN server request: both attempt and failure (no response)
- Digit Maps processing / transformations / errors might be more detailed
- call phases (including destination phone number) when using GoogleVoice would be useful
- IPs are being printed in binary form (sendto 42368c2e) – traditional 12.23.34.45 notation might simplify troubleshooting.
- In general any "bad" situation ought to be logged – that may greatly simplify setup and troubleshooting.
- syslog facility may be used to monitor Obi device, someone may want setup a script to notify about problems via email. It just needs to be verbose enough to tell about problems.

---oleg