[OpenSIPS-Devel] [opensips] Via branch non RFC 3261 compliant (#145)

[Varun]

Options packet sent from opensips to oversip,

    OPTIONS sip:1001 at 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 at 10.0.0.161:10080;transport=ws;lr;ovid=3869ae8a;ob>
    From: sip:pinger at XXX.XXX.XXX.XXX;tag=c1c23161
    To: sip:1001 at df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=ws;ov-ob=6bce984846
    Call-ID: 11693e73-d6... at 10.238.201.229
    CSeq: 1 OPTIONS
    Max-Forwards: 70
    Content-Length: 0

Response from oversip to opensips,

    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 at XXX.XXX.XXX.XXX;tag=c1c23161
    To: sip:1001 at df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=ws;ov-ob=6bce984846;tag=a360ead4.29d19ef0
    Call-ID: 11693e73-d6... at 10.238.201.229
    CSeq: 1 OPTIONS
    Content-Length: 0
    Server: OverSIP/1.4.1

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/145
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20131202/67294b54/attachment.htm>