New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Via branch non RFC 3261 compliant #145
Comments
Since this is an options packet it will not need to be re-transmitted so i generated a random 7 digit number for each option packet and appended it to the RFC 3261 string "z9hG4bK". My C skills are not great but this is what i did to fix this for myself, if someone can come up with a better method and commit to the code that will be great. In modules/nathelper/sip_pinger.h Line 31:
Line 145:
Line 180:
Line 185:
|
2013/12/2 Varun notifications@github.com
Yes, that 's a bug in OpenSIPS as it sets ;branch=0 which is not RFC 3261 Iñaki Baz Castillo |
Point taken ! varunvairavan idea is ok, I will integrate it into the code. Thank too all for report and comments. |
FWIW, I think nat_traversal does the same. @ibc shouldn't OverSIP be gentle in what it accepts? ;-) |
I have not tested the code, but looks good to me :-) |
1f18541 The int2bstr took a fews mins to wrap around my head. Looks good. Thank you for the fast turn around. |
Backport done, closing.... |
Options packet sent from opensips to oversip,
Response from oversip to opensips,
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.
The text was updated successfully, but these errors were encountered: