-
The SIPSorcery.Net.SDP parser currently expects the announcement version in the o= line to be a 32bit Integer.
However there are a number of UAs that use much larger sizes.
For example rtpengine…
-
Commit 1c1ca9f2b7 introduced a `a=rtcp-fb:PT goog-remb` attribute when parsing SDP that does not exist in the SDP content being parsed.
This appears to be because it adds a SupportedRtcpFeedbackMes…
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…
-
I think it would make sense to decouple the SDP parser from the SIP parser. @moggle-mog already saw it here
https://github.com/jart/gosip/pull/9#issuecomment-650869750
@jart , @moggle-mog what do …
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…
-
```
These are my SDP outputs:
LOCAL:
v=0
o=3686278856 0 0 IN IP4 10.0.0.27
s=Session SIP/SDP
c=IN IP4 10.0.0.27
t=0 0
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCM…