[OpenSIPS-Users] Problem with sip_trace storage, maybe a bug?
    opensipslist at encambio.com 
    opensipslist at encambio.com
       
    Fri Feb  4 11:20:29 CET 2011
    
    
  
Hello list,
I'm using:
  Solaris 11 x86 (nv-b91)
  OpenSIPS 1.6.4 with TLS
...and am logging dialogs with the siptrace module.
The problem is that every time I want to look at the traced messages
in the sip_trace table, I do:
  $ psql opensips opensips
  opensips=> select * from sip_trace where fromip = 'tcp:1.2.3.4:5678';
  id | time_stamp | callid | traced_user | msg | method | ...
  1234 | 2011-02-03 | ... | | \x494e56495445207369703a...
As you can see, the 'msg' column ASCII text is stored as hex values.
The next thing I do is use my mouse to cut and paste the message
(extremely long and tedious) to the window in:
  http://www.dolcevie.com/js/converter.html
...which translates '\x494e56495445207369703a' to 'INVITE sip:'.
This way of debugging is not acceptable at all, and I want to
see the ASCII text of the SIP message directly (without converting.)
How can I read the siptrace logs in this way?
Is it a bug that OpenSIPS stores the ASCII message text in hex?
Regards,
Brian
    
    
More information about the Users
mailing list