Skip to content

Commit

Permalink
docs: add example of parsing SDP using any source multicast
Browse files Browse the repository at this point in the history
  • Loading branch information
andrewbonney committed Jul 22, 2019
1 parent b28b5da commit 9f10c6a
Showing 1 changed file with 25 additions and 1 deletion.
26 changes: 25 additions & 1 deletion docs/4.1. Behaviour - RTP Transport Type.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Senders and Receiver Connection Management endpoints must support a core paramet
* `rtcp_source_port`

## Interpretation of SDP Files
All Senders and Receivers should comply with RFC 4566 (Session Description Protocol) when creating and parsing SDP files. Multicast Senders and Receivers should additionally comply with RFC 4570 (SDP Source Filters). Two examples are given below, showing an SDP file and the transport parameters that would be presented at the `/staged` endpoint by a Receiver that has parsed the file.
All Senders and Receivers should comply with RFC 4566 (Session Description Protocol) when creating and parsing SDP files. Multicast Senders and Receivers should additionally comply with RFC 4570 (SDP Source Filters). Three examples are given below, showing an SDP file and the transport parameters that would be presented at the `/staged` endpoint by a Receiver that has parsed the file.

In the event that a receiver is presented with an SDP file and a set of transport parameters that
contradict each other in the same PATCH request, the transport parameters take priority
Expand Down Expand Up @@ -120,6 +120,30 @@ transport_params:[
]
```

### Any Source Multicast

```
v=0
o=- 1497010742 1497010742 IN IP4 172.29.226.24
s=SDP Example
t=2873397496 2873404696
m=video 5000 RTP/AVP 103
c=IN IP4 232.21.21.133/32
a=rtpmap:103 raw/90000
```

```javascript
transport_params:[
{
"source_ip": null,
"multicast_ip": "232.21.21.133",
"interface_ip": "auto",
"destination_port": 5000,
"rtp_enabled": true
}
]
```

## Operation with SMPTE 2022-5
SMPTE 2022-5 describes RTP streams with forward error correction (FEC), and is supported by the Connection Management Specification. This support take the form if the FEC transport parameter set described in [Parameter Sets](#parameter-sets). Note that Senders have additional parameters used to specify the type of FEC to be used and matrix rows and columns, which are not present on the Receiver side. In SMPTE 2022-5 this information is conveyed in the FEC stream headers, and as such does not need to be conveyed separately in Connection Management.

Expand Down

0 comments on commit 9f10c6a

Please sign in to comment.