[asterisk-dev] Stricter Logging Mechanism

[J. Oquendo]

Are the plans in the works to implement logging IP addresses along with 
entries? For example:

Original warnings:

chan_sip.c: Unknown SDP media type in offer: video 20000 RTP/AVP 31
chan_sip.c: Maximum retries exceeded on transmission 392 for seqno 392 
(Critical Response)
chan_sip.c: Missing Cseq. Dropping this SIP message, it's incomplete.
chan_sip.c: No closing bracket found in '926 <sip:

How about:

New warnings:
chan_sip.c: Unknown SDP media type in offer: video 20000 RTP/AVP 31 From 
IPADDRESS
chan_sip.c: Maximum retries exceeded on transmission 392 for seqno 392 
(Critical Response) From IPADDRESS
chan_sip.c: Missing Cseq. Dropping this SIP message From IPADDRESS, it's 
incomplete.
chan_sip.c: No closing bracket found in '926 <sip: From IPADDRESS

This would help admins, engineers, etc., in providing a stabler 
environment since we would be able to isolate issues more.

-- 
====================================================
J. Oquendo
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1383A743
sil . infiltrated @ net http://www.infiltrated.net 

The happiness of society is the end of government.
John Adams

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5157 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20061201/683ff91c/smime-0001.bin