Hi Anca, 

I set debug=6 but it does not appear to print any more detailed information to 
my log (/var/log/messages). 

I reviewed the sip trace I posted at 
http://www.woollum.com/temp/opensips_trace.html and I still cannot find any 
packets that are missing the header. The error log I posted at 
http://www.woollum.com/temp/opensips.txt says that the To field, From field, 
and RR field could not be parsed. It seems as though the B2BUA module tried to 
open a new leg but didn't send the information along? Does that make sense? 
>From the log earlier: 
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE STARTING INVITE 
<null> sip:[email protected]
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:rr:record_route: 
From parsing failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:new_t: no valid 
From in INVITE
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:t_newtran: new_t 
failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_to: 
unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: 
ERROR:b2b_entities:b2b_tm_cback: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE 8 ENDING INVITE 
<null> sip:[email protected]:5062
Oct 12 19:34:17 sip01 /usr/local/sbin/opensips[5168]: 
ERROR:b2b_entities:b2b_prescript_f: No dialog found, callid= [B2B.50.3250981], 
method=REFER Brett Woollum 

[email protected] 


----- Original Message ----- 
From: "Anca Vamanu" <[email protected]> 
To: [email protected] 
Sent: Thursday, October 14, 2010 12:45:19 AM GMT -08:00 US/Canada Pacific 
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not 
Working (Bug?) 

Hi Brett, 

You need to run a network trace and catch the message for which you get this 
error: 

ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> 

You can run opensips in debug mode ( set 'debug=6' ) to see info from the 
message and be able to find it in the network trace. 

>From the logs it seems that a message ( possibly REFER ) has a bad From header 
>and OpenSIPS is not able to process right. 

Regards, 
-- 
Anca Vamanu www.voice-system.ro 
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to