Tags: pion/sdp
Tags
Add lenient parsing for incomplete origin lines Support non-compliant SDP origin lines missing address type or unicast address fields, commonly found in security cameras. - Add fallback to default values when fields are missing - Maintain RFC4566 compliance for complete origin lines - Add comprehensive test coverage for edge cases Fixes compatibility with Uniview and other camera manufacturers that generate non-compliant SDP. Handle missing AddressType/UnicastAddress fields in SDP from IP cameras by setting RFC-compliant defaults (IP4/0.0.0.0, IP6/::). Maintains strict error handling for unexpected failures. Fixes compatibility with Uniview and similar cameras. - Extract handleAddressType/handleUnicastAddress helpers
Add support for rtcp-fb:* According to Chrome PSA: https://groups.google.com/g/discuss-webrtc/c/Y_h2B-NOzW0 rtcp-fb:* might start getting sent by chrome in M112. This was rolled back but may land again in M114 according to maintainers. Also, according to https://webrtc.googlesource.com/src.git/+/8155227/#F0 Chrome may plan on sending both rtcp-fb:* and rtcp-fb:<int> variants for some time to allow migration in downstream projects. This change correctly parses the wildcard case to add the feedback to all payload types found in the SDP, to maintain compatibility with Pion. Resolves #172
PreviousNext