Just to let people know, this was fixed in 2.1 (it was triggered by
adding the new websocket protocol).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.03.2015 18:42, Satish Patel wrote:
I set debug=6 and here is the logs most of time error
I set debug=6 and here is the logs most of time error pop'ed up near tm
module
DBG:tm:run_trans_callbacks: trans=0x7f9570f06710, callback type 1024, id 1
entered
DBG:siptrace:trace_onreq_out: trace on req out
DBG:core:parse_headers: flags=40
DBG:siptrace:trace_msg_out: trace msg out
I am configuring siptrace with homer server and getting following error,
ERROR:siptrace:pipport2su: bad protocol
ERROR:siptrace:pipport2su: bad protocol
ERROR:siptrace:pipport2su: bad protocol
Razvan fix following patch but still getting above error in log
