<div dir="ltr">I'm seeing a weird, intermittent error. The most common occurrence is with a 200OK returned by Mid-Registrar on a re-REGISTER using registration throttling, but we see it elsewhere. It appears that the 200OK message is getting garbled.<div><br></div><div>We have a bit of a weird setup to overcome issues we were having with Mid-Registrar and WebSocket addressing. Mid-Registrar is looping back 200OK to OpenSIPS before it then gets sent down the WebSocket. 90+% of the time it's absolutely fine, but occasionally the 200OK seems to be corrupted. </div><div><br></div><div>Here's an example. What we are seeing in this message is...</div><div><br></div><div>    Contact: <<a href="http://sip:1234@abc.def.com:5060">sip:1234@abc.def.com:5060</a>></div><div>    User-Agent: MWWRTC 3.4.21042#015#012Accept: application/sdp,application/dtmf-relay,text/plain</div><div><br></div><div>...preceding...</div><div><br></div><div>    SIP/2.0 200 OK</div><div>    Via: SIP/2.0/TCP 192.168.1.23:5060;received=192.168.1.23;rport=42385;branch=z9hG4bK22a8.4fa6d127.0;i=b4986fe4</div><div>    ...etc...</div><div><br></div><div>...so OpenSIPS is failing to parse the message.</div><div><br></div><div>What I'd like to know is, is this a sign of SIP message fragmentation?</div><div><br></div><div><br></div><div><br></div><div>Log entries (IP addresses, domains, and extensions changed to protect the innocent!):</div><div><br></div><div>ERROR:core:parse_method: invalid character :<br>DBG:core:tcp_read_req: tcp_read_req end<br>INFO:core:parse_first_line: failed to parse the method<br>INFO:core:parse_first_line: bad message<br>DBG:core:parse_msg: invalid message<br>ERROR:core:parse_msg: message=<Contact: <<a href="http://sip:1234@abc.def.com:5060">sip:1234@abc.def.com:5060</a>>#015#012User-Agent: MWWRTC 3.4.21042#015#012Accept: application/sdp,application/dtmf-relay,text/plain#015#012SIP/2.0 200 OK#015#012Via: SIP/2.0/TCP 192.168.1.23:5060;received=192.168.1.23;rport=42385;branch=z9hG4bK22a8.4fa6d127.0;i=b4986fe4#015#012Via: SIP/2.0/WSS 98kaag0xmybq.invalid;received=4.56.78.110;branch=z9hG4bKU6O3fJQGeLvuACMTXTArJgJW73rOD5dU;rport=52570#015#012From: <<a href="mailto:sip%3A1234@abc.def.com">sip:1234@abc.def.com</a>>;tag=Lyk010G476K7xcKrE84M#015#012To: <<a href="mailto:sip%3A1234@abc.def.com">sip:1234@abc.def.com</a>>;tag=af78-6213d386c3edcd02707b0c0aa8423d3a#015#012Call-ID: 666b5e7c-cef3-f306-4b79-60d3160dc5d0#015#012CSeq: 28825 REGISTER#015#012Contact: <sips:1234@98kaag0xmybq.invalid;transport=wss>;expires=60;received="sip:<a href="http://4.56.78.110:52570">4.56.78.110:52570</a>"#015#012Server: OpenSIPS (3.1.1 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012><br>ERROR:core:receive_msg: Unable to parse msg received from [<a href="http://192.168.1.23:5060">192.168.1.23:5060</a>]<br>ERROR:core:tcp_handle_req: receive_msg failed<br>DBG:core:tcp_read_req: tcp_read_req end<br></div></div>