<p>Options packet sent from opensips to oversip,</p>
<pre><code>OPTIONS sip:1001@df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=ws;ov-ob=6bce984846 SIP/2.0
Via: SIP/2.0/UDP 10.238.201.229:5060;branch=0
Route: <sip:10.0.0.161:5060;transport=udp;lr;ovid=3869ae8a>,<sip:6bce984846@10.0.0.161:10080;transport=ws;lr;ovid=3869ae8a;ob>
From: sip:pinger@XXX.XXX.XXX.XXX;tag=c1c23161
To: sip:1001@df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=ws;ov-ob=6bce984846
Call-ID: 11693e73-d6...@10.238.201.229
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0
</code></pre>
<p>Response from oversip to opensips,</p>
<pre><code>SIP/2.0 400 Via branch non RFC 3261 compliant
Via: SIP/2.0/UDP 10.238.201.229:5060;branch=0;received=XXX.XXX.XXX.XXX
From: sip:pinger@XXX.XXX.XXX.XXX;tag=c1c23161
To: sip:1001@df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=ws;ov-ob=6bce984846;tag=a360ead4.29d19ef0
Call-ID: 11693e73-d6...@10.238.201.229
CSeq: 1 OPTIONS
Content-Length: 0
Server: OverSIP/1.4.1
</code></pre>
<p>When sending the options packet to non-webrtc clients there is no problem, but when sending it to webrtc clients through oversip, oversip expects the branch tag to have a value.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href='https://github.com/OpenSIPS/opensips/issues/145'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/cHRwG-eeZpfKR_UBFXzvRLiuI8LgSFFr8El3L9iq1LcqdioAYs6Ov8gAR1IdzzLg.gif' height='1' width='1'></p>