Thanks bogdan for your input so far. But, this...
Hi Ben,
-d Debugging mode (multiple -d increase the level)
-E Log to stderr
you can get the same from cfg with
debug = 9
log_stderror = yes
so your openser will not use syslog, but standard error for logging.
...will not actually work for me. After the default wasn't working, that's the
first thing I tried to change in my config and it didn't do anything for me.
And I'm not sure exactly what you mean here... It sounds like you are asking if
I've tried the default setup...
now, regarding syslog logging - have you tried not to use the log
facility stuff? do not set it in either in cfg, neither in syslog.cfg
....openser should normally log to the default log file.
regards,
bogdan
Thanks,
Ben
>Ben Ferguson -
backcountry.com wrote:
> Hmmmm. Interestingly, if i:
>
> #openser -E -dddddddddddddd
>
> I get all sorts of good logging sent to my console:
>
>
> 3(990) version: <SIP/2.0>
> 3(990) parse_headers: flags=2
> 3(990) Found param type 232, <branch> = <z9hG4bK40b3.2f0d0803.0>;
state=16
> 3(990) end of header reached, state=5
> 3(990) parse_headers: Via found, flags=2
> 3(990) parse_headers: this is the first via
> 3(990) After parse_msg...
> 3(990) preparing to run routing scripts...
> 3(990) parse_headers: flags=8
> 3(990) DEBUG: add_param: tag=329cfeaa6ded039da25ff8cbb8668bd2.d88a
> 3(990) DEBUG:parse_to:end of header reached, state=29
> 3(990) DBUG:parse_to: display={}, ruri={sip:1001@192.168.1.105}
> 3(990) DEBUG: get_hdr_field: <To> [67]; uri=[sip:1001@192.168.1.105]
> 3(990) DEBUG: to body [<sip:1001@192.168.1.105>]
> 3(990) parse_headers: flags=100
> 3(990) get_hdr_field: cseq <CSeq>: <43365> <ACK>
> 3(990) DEBUG: get_hdr_body : content_length=0
> 3(990) found end of header
> 3(990) DEBUG: is_maxfwd_present: max_forwards header not found!
> 3(990) DEBUG: add_param: tag=1142574036
> 3(990) DEBUG:parse_to:end of header reached, state=29
>
> Now just to figure out how to pass the -E and -dddddddd options to openserctl and
redirect it to a text file... I may be on to >>something here that'll work for
my setup
>
> -Ben-