Depending on what you are trying to accomplish with the syslog you might try running my
obisyslogd.pl perl script as your syslog server for the Obi. You could modify the script to look at each incoming log message using text substrings and ignore certain messages or write them to a different log file.
I posted the script as an attachment in
http://www.obitalk.com/forum/index.php?topic=185.msg9107#msg9107The script can be used as an actual syslog server (it monitors a port for messages, and writes them to a file) and is not just for "pop up" messages.
The majority of messages I see are level <7>, so I doubt a message level filter is going to be much help. Or it could be I just don't understand message levels.
[2011.09.02 20:23:27] [192.168.0.40] <7> SPREG:Subst Contact w/ via-rport 32953
[2011.09.02 20:23:27] [192.168.0.40] <7> SPREG:Subst Contact w/ via-rport 32953
[2011.09.02 20:23:27] [192.168.0.40] <7> REG:OK(30)
The above messages are "raw" right from the Obi beginning with the first "<". The script prepends the [date time], and [source IP address].