A SIP trace would be much more useful. You can make them for example
with Wireshark and configure Wireshark with the private kay of the
certificate - then Wireshark can decode TLS.
http://www.routerzone.eu/wiki/index.php/Using_Wireshark_to_Decrypt_SSL/TLS_…
regards
klaus
Am 27.03.2010 08:05, schrieb Hemanshu Patel:
Mar 27 12:36:36 [5492] DBG:core:destroy_avp_list:
destroying list (nil)
Mar 27 12:36:36 [5492] DBG:core:receive_msg: cleaning up
Mar 27 12:36:42 [5492] DBG:core:tcp_receive_timeout: 0x7fd335f04798 expired (50, 51)
lt=0
Mar 27 12:36:42 [5492] DBG:core:io_watch_del: io_watch_del (0x74efe0, 18, -1, 0x10)
fd_no=2 called
Mar 27 12:36:42 [5492] DBG:core:release_tcpconn: releasing con 0x7fd335f04798, state 0,
fd=18, id=3
Mar 27 12:36:42 [5492] DBG:core:release_tcpconn: extra_data 0x7fd335f017b8
Mar 27 12:36:42 [5499] DBG:core:handle_tcp_child: reader response= 7fd335f04798, 0 from
0
Mar 27 12:36:42 [5499] DBG:core:io_watch_add: io_watch_add(0x74ee80, 24, 2,
0x7fd335f04798), fd_no=17
Mar 27 12:36:42 [5499] DBG:core:handle_tcp_child: cmd CONN_RELEASE 0x7fd335f04798
refcnt= 0
Mar 27 12:36:45 [5499] DBG:core:handle_tcpconn_ev: data available on 0x7fd335eddc18 23
Mar 27 12:36:45 [5499] DBG:core:io_watch_del: io_watch_del (0x74ee80, 23, -1, 0x0)
fd_no=18 called
Mar 27 12:36:45 [5499] DBG:core:send2child: to tcp child 0 0(549