-
Notifications
You must be signed in to change notification settings - Fork 82
Live Streaming
- Real-time media streaming over an RTMP endpoint that can be played using any player supporting the RTMP stream.
- Stereo Stream Support.
- The feature would be available on-demand and can be enabled/disabled using an HTTP API.
- It would be enabled/disabled based on the call segment UUID (this is not the call UUID).
- It may be possible to do this via alternate identifiers if passed in sip headers, but this would be a future development task.
- Each call would have a unique RTMP URL while streaming, which would be provided in the enable/disable HTTP call.
- There would be no transcoding done by the streaming service, and the receiver would have to transcode if any.
Orkaudio provides a Filter Interface. A Filter is a black box that takes media chunks as input and produces media chunks as output. It can be translating between two encodings (codec) or just procession the signal. Implementation for Filter can be written and plugged in via Orkaudio's configuration file.
LiveStreamFilter is an implementation of Orkaudio's Filter Interface. It captures the incomming audio chunks, processes them to stereo stream chunks, and ingests them to an RTMP server. For every live call, an object of LiveStreamFilter is instantiated. The RTMP server then exposes a unique RTMP URL [rtmp://:/live/] for each call that can be used to live-stream audio on any RTMP-supported player.
LiveStreamFilter Module Components
- LiveStreamServer
- LiveStreamSession
- LiveStreamFilter
Generally speaking, if you have 2 channels, let's call them L for left and R for right, and you want to transmit or store 20 samples, then:
Interleaved = LRLRLRLRLRLRLRLRLRLR
Downmixing refers to combining multiple audio channels into a single stereo output. Audio packets from both channels are received as a continuous mono stream. They are interleaved to convert from Mono channel buffer to Stereo/Multi-Channel buffer
<!-- LiveStreamFilter Configuration -->
<CapturePortFilters>LiveStreamFilter</CapturePortFilters>
<!-- RTMP Endpoint to which the streams would be published. Refer to nginx config for example -->
<RTMPServerEndPoint>127.0.0.1</RTMPServerEndPoint>
<RTMPServerPort>1935</RTMPServerPort>
<LiveStreamingServerPort>59160</LiveStreamingServerPort>
<LiveStreamingQueueFlushThresholdSeconds>30</LiveStreamingQueueFlushThresholdSeconds>
<!-- End of LiveStreamFilter Configuration -->
events {}
rtmp {
server {
listen 1935;
chunk_size 4096;
# Stream mode: one publisher, many subscribers
application live {
live on;
record off;
}
}
}
# HTTP can be used for accessing RTMP stats
http {
server {
listen 9091;
# This URL provides RTMP statistics in XML
location /stat {
rtmp_stat all;
# Use this stylesheet to view XML as web page
# in browser
rtmp_stat_stylesheet stat.xsl;
}
}
}
- Ping Check
$ curl http://{recorderIp}:59160/hi
{
"message": "Hi!"
}
- Start Stream
$ curl -X POST 'http://{recorderIp}:59160/livestream/start' \
-H 'Content-Type: application/json' --data-raw '{ "nativeCallId":"139b90ff-36e4-44f1-a581-9184b3988bdf" }'
{
"url": "rtmp://172.16.176.65:1935/live/139b90ff-36e4-44f1-a581-9184b3988bdf"
}
- Stop Stream
$ curl -X POST 'http://{recorderIp}:59160/livestream/stop' \
-H 'Content-Type: application/json' --data-raw '{ "nativeCallId":"98c5fac6-25fb-4f73-a224-31c6135cd679" }'
{
"callId": "98c5fac6-25fb-4f73-a224-31c6135cd679",
"status": "stopped"
}
- Get List of Current Live Calls
$ curl http://{recorderIp}:59160/livestream/livecalls
{
"liveCalls": [
"98c5fac6-25fb-4f73-a224-31c6135cd679"
]
}
- Get List of Currently Streamed Calls
$ curl http://{recorderIp}:59160/livestream/streamcalls
{
"streamCalls": [
"98c5fac6-25fb-4f73-a224-31c6135cd679",
" 23fdd9cd-b048-4baa-8003-767d51a937b0"
]
}