You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support more values for the bandwidth types when parsing b= attributes, namely the ones described in RFC3890 and RFC3556.
Motivation
Implementation of protocols using SDP (whether it's SIP, WebRTC or others) might want or need to use values for the bandwidth type other than the two values defined in RFC4566. Currently using anything other than CT or AS in the b= attribute of a SDP payload (either for the session or a media) and attempting to unmarshal it with pion/sdp results in an "invalid syntax" error. Because parsing this attribute happens in an unexported function in the unmarshal code, this support can't be added by the VoIP implementation using this library, so it needs to happen in this library itself.
The text was updated successfully, but these errors were encountered:
Summary
Support more values for the bandwidth types when parsing
b=
attributes, namely the ones described in RFC3890 and RFC3556.Motivation
Implementation of protocols using SDP (whether it's SIP, WebRTC or others) might want or need to use values for the bandwidth type other than the two values defined in RFC4566. Currently using anything other than
CT
orAS
in theb=
attribute of a SDP payload (either for the session or a media) and attempting to unmarshal it with pion/sdp results in an "invalid syntax" error. Because parsing this attribute happens in an unexported function in the unmarshal code, this support can't be added by the VoIP implementation using this library, so it needs to happen in this library itself.The text was updated successfully, but these errors were encountered: