sip-router

SIP Router Project

Tasklist

FS#57 - Improving logging (show at least the transaction branch)

Attached to Project: sip-router
Opened by Iñaki Baz Castillo (ibc) - Tuesday, 30 March 2010, 14:08 GMT
Last edited by Daniel-Constantin Mierla (miconda) - Thursday, 11 September 2014, 10:07 GMT
Task Type Improvement
Category Core → logging
Status Closed
Assigned To Andrei Pelinescu-Onciul (andrei)
Operating System All
Severity Low
Priority Low
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Sometimes I inspect the log of SR/Kamailio and find errors like:

ERROR:nathelper:force_rtp_proxy: incorrect port 0 in reply from rtp proxy

or:

WARNING:dialog:dlg_onroute: unable to find dialog for BYE with route param '7b4.36497575' [1207:1465357411]

Of course in a server with high traffic such logs help nothing (even if I’m capturing all the SIP flow via pcap or ‘siptrace’ module).

It would be great if the logging core system would log always “something” related to the request or transaction, perhaps the branch, something as:

ERROR[recv 183 z9hG4bK6887.92b352f.0]:nathelper:force_rtp_proxy: incorrect port 0 in reply from rtp proxy
WARNING[sent BYE z9hG4bK68612qwre1h3]:dialog:dlg_onroute: unable to find dialog for BYE with route param '7b4.36497575' [1207:1465357411]

It would help a lot when debugging occasional issues (perhaps more related to a specific client rather than the SR/Kamailio server).

This task depends upon

Closed by  Daniel-Constantin Mierla (miconda)
Thursday, 11 September 2014, 10:07 GMT
Reason for closing:  Implemented
Comment by Daniel-Constantin Mierla (miconda) - Thursday, 11 September 2014, 10:07 GMT

This should be now possible via log_prefix core parameter/

Loading...