janis/aes67-daemon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixes to documentation

Browse Source
This commit is contained in:
Andrea Bondavalli 2020-03-06 11:16:39 -08:00
parent d99bf3ed4a
commit 27bee43c20
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -20,7 +20,7 @@ The daemon can be cross-compiled for multiple platforms and implements the follo
* control and configuration of up to 64 sources and sinks using the ALSA RAVENNA/AES67 driver via netlink * control and configuration of up to 64 sources and sinks using the ALSA RAVENNA/AES67 driver via netlink
* session handling and SDP parsing and creation * session handling and SDP parsing and creation
* HTTP REST API for control and configuration * HTTP REST API for control and configuration
* SAP discovery protocol implementation and SAP browser implementation * SAP discovery protocol and SAP browse
* IGMP handling for SAP, RTP and PTP multicast traffic * IGMP handling for SAP, RTP and PTP multicast traffic
The directory also contains the daemon regression tests in the [tests](daemon/tests) subdirectory. To run daemon tests install the ALSA RAVENNA/AES67 kernel module enter the [tests](daemon/tests) subdirectory and run *./daemon-test -l all* The directory also contains the daemon regression tests in the [tests](daemon/tests) subdirectory. To run daemon tests install the ALSA RAVENNA/AES67 kernel module enter the [tests](daemon/tests) subdirectory and run *./daemon-test -l all*

4
daemon/README.md
View File

@ -7,7 +7,7 @@ The daemon is responsible for:
* communication and configuration of the device driver * communication and configuration of the device driver
* provide an HTTP REST API for the daemon control and configuration * provide an HTTP REST API for the daemon control and configuration
* session handling and SDP parsing and creation * session handling and SDP parsing and creation
* SAP discovery protocol implementation and SAP browser * SAP discovery protocol and SAP browser
* IGMP handling for SAP and RTP sessions * IGMP handling for SAP and RTP sessions
## Configuration file ## ## Configuration file ##
@ -543,6 +543,7 @@ Example:
"source": "SAP", "source": "SAP",
"id": "d00000a611d", "id": "d00000a611d",
"name": "ALSA Source 2", "name": "ALSA Source 2",
"address": "10.0.0.13",
"sdp": "v=0\no=- 2 0 IN IP4 10.0.0.13\ns=ALSA Source 2\nc=IN IP4 239.1.0.3/15\nt=0 0\na=clock-domain:PTPv2 0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.1.0.3/15\na=rtpmap:98 L16/48000/2\na=sync-time:0\na=framecount:48\na=ptime:1\na=mediaclk:direct=0\na=ts-refclk:ptp=IEEE1588-2008:00-10-4B-FF-FE-7A-87-FC:0\na=recvonly\n", "sdp": "v=0\no=- 2 0 IN IP4 10.0.0.13\ns=ALSA Source 2\nc=IN IP4 239.1.0.3/15\nt=0 0\na=clock-domain:PTPv2 0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.1.0.3/15\na=rtpmap:98 L16/48000/2\na=sync-time:0\na=framecount:48\na=ptime:1\na=mediaclk:direct=0\na=ts-refclk:ptp=IEEE1588-2008:00-10-4B-FF-FE-7A-87-FC:0\na=recvonly\n",
"last_seen": 2768, "last_seen": 2768,
"announce_period": 30 "announce_period": 30
@ -551,6 +552,7 @@ Example:
"source": "SAP", "source": "SAP",
"id": "d00000a8dd5", "id": "d00000a8dd5",
"name": "ALSA Source 1", "name": "ALSA Source 1",
"address": "10.0.0.13",
"sdp": "v=0\no=- 1 0 IN IP4 10.0.0.13\ns=ALSA Source 1\nc=IN IP4 239.1.0.2/15\nt=0 0\na=clock-domain:PTPv2 0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.1.0.2/15\na=rtpmap:98 L16/48000/2\na=sync-time:0\na=framecount:48\na=ptime:1\na=mediaclk:direct=0\na=ts-refclk:ptp=IEEE1588-2008:00-10-4B-FF-FE-7A-87-FC:0\na=recvonly\n", "sdp": "v=0\no=- 1 0 IN IP4 10.0.0.13\ns=ALSA Source 1\nc=IN IP4 239.1.0.2/15\nt=0 0\na=clock-domain:PTPv2 0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.1.0.2/15\na=rtpmap:98 L16/48000/2\na=sync-time:0\na=framecount:48\na=ptime:1\na=mediaclk:direct=0\na=ts-refclk:ptp=IEEE1588-2008:00-10-4B-FF-FE-7A-87-FC:0\na=recvonly\n",
"last_seen": 2768, "last_seen": 2768,
"announce_period": 30 "announce_period": 30