29 Oct
2004
29 Oct
'04
1:55 p.m.
Use xlog to dump the Contact (%ct) and then you can see it in the logs
(the dumped contact and the error message will have the same process
number). xlog does not parse the body of the Contact header field so it
should work.
Jan.
On 29-10 09:10, Java Rockx wrote:
Will do.
How can I best determine the exact message that is causing the error? If I use
ngrep on port 5060 I'm not sure how to synchronize the ngrep output with
/var/log/messages entries.
Is there a way to dump the full sip message from withing ser.cfg? I know about
the xlog module, but I've never seen a way to write the raw sip messages to
/var/log/message from within ser.cfg.
Regards,
Paul
--- Jan Janak <jan(a)iptel.org> wrote:
Either the SIP message is malformed or there is a
bug in the parser. If
you have the dump of the request that causes the log message then send
it to me, please.
Jan.
On 28-10 16:12, Java Rockx wrote:
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now.
http://messenger.yahoo.com Hi all.
I occasionally get this message in /var/log/messages
get_contact_uri: Error while parsing Contact body
Should I be concerned with this? If so, what is the recommended action I
should
take to deal with this?
Regards,
Paul
__________________________________
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now.
http://messenger.yahoo.com
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers