Winlin
04b88e889f
AI: Improve coverage of app by utest ( #4494 )
...
Co-authored-by: OSSRS-AI <winlinam@gmail.com>
2025-09-17 21:51:07 -04:00
Winlin
35e2808f0c
Support IPv6 for all protocols: RTMP, HTTP/HTTPS, WebRTC, SRT, RTSP. v7.0.67 ( #4457 )
...
This PR adds comprehensive IPv6 support to SRS for all major protocols,
enabling dual-stack (IPv4/IPv6) operation across the entire streaming
server.
Key Features:
* RTMP/RTMPS: IPv6 support for streaming ingestion and playback
* HTTP/HTTPS: IPv6 support for HTTP-FLV streaming and API endpoints
* WebRTC: IPv6 support for UDP/TCP media transport (WHIP/WHEP)
* SRT: IPv6 support for low-latency streaming
* RTSP: IPv6 support for standards-based streaming
For config, see `conf/console.ipv46.conf` for example.
Publish RTMP or RTMPS via IPv6:
```bash
ffmpeg -re -i ./doc/source.flv -c copy -f flv 'rtmp://[::1]:1935/live/livestream'
ffmpeg -re -i ./doc/source.flv -c copy -f flv 'rtmps://[::1]:1443/live/livestream'
```
Play RTMP or RTMPS stream via IPv6 by ffplay:
```bash
ffplay 'rtmp://[::1]:1935/live/livestream'
ffplay 'rtmps://[::1]:1443/live/livestream'
```
Play by IPv6 via HTTP streaming:
* HTTP-FLV:
[http://[::1]:8080/live/livestream.flv ](http://[::1]:8080/players/srs_player.html )
* HTTPS-FLV:
[https://[::1]:8088/live/livestream.flv ](https://[::1]:8088/players/srs_player.html )
To access HTTP API via IPv6:
* HTTP API: `curl 'http://[::1]:1985/api/v1/versions '`
* HTTPS API: `curl -k 'https://[::1]:1990/api/v1/versions '`
```json
{
"code": 0,
"data": {
"major": 7,
"minor": 0,
"revision": 66,
"version": "7.0.66"
}
}
```
Using HTTP API, publish by IPv6 WHIP via
[HTTP](http://[::1]:8080/players/whip.html ), and play by
[WHEP](http://[::1]:8080/players/whep.html )
* WHIP: `http://[::1]:1985/rtc/v1/whip/?app=live&stream=livestream `
* WHEP: `http://[::1]:1985/rtc/v1/whep/?app=live&stream=livestream `
Using HTTPS API, publish by IPv6 WHIP via
[WHIP](https://[::1]:8088/players/whip.html ), and play by
[WHEP](https://[::1]:8088/players/whep.html )
* WHIP: `https://[::1]:1990/rtc/v1/whip/?app=live&stream=livestream `
* WHEP: `https://[::1]:1990/rtc/v1/whep/?app=live&stream=livestream `
Publish SRT stream by FFmpeg via IPv6:
```bash
ffmpeg -re -i ./doc/source.flv -c copy -pes_payload_size 0 -f mpegts \
'srt://[::1]:10080?streamid=#!::r=live/livestream,m=publish'
```
Play SRT stream by ffplay via IPv6:
```bash
ffplay 'srt://[::1]:10080?streamid=#!::r=live/livestream,m=request'
```
Play RTSP stream by ffplay via IPv6:
```bash
ffplay -rtsp_transport tcp -i 'rtsp://[::1]:8554/live/livestream'
```
---------
Co-authored-by: OSSRS-AI <winlinam@gmail.com>
2025-08-30 08:52:21 -04:00
Winlin
6e1134fe9b
Use clang format. v7.0.52 ( #4433 )
...
---------
Co-authored-by: ChenGH <chengh_math@126.com>
2025-08-11 23:19:19 -04:00
ChenGH
13597d1b7f
update copyright to 2025. v5.0.218 v6.0.159 v7.0.21 ( #4271 )
...
update copyright to 2025
---------
Co-authored-by: john <hondaxiao@tencent.com>
Co-authored-by: winlin <winlinvip@gmail.com>
2025-01-14 17:35:18 +08:00
winlin
2a2da2253f
Switch to 2013-2024. v6.0.109
2024-01-01 10:51:24 +08:00
winlin
29eff1a242
Refine LICENSE.
2023-10-23 14:33:19 +08:00
Winlin
cf46dae80f
Support include empty config file. v5.0.173 v6.0.68 ( #3768 )
...
SRS supports including another configuration in the include package.
When generating configurations, we can only generate the changed
configurations, while the unchanged configurations are in the fixed
files, for example:
```nginx
listen 1935;
include server.conf;
```
In `server.conf`, we can manage the changing configurations with the
program:
```nginx
http_api { enabled on; }
```
However, during system initialization, we often create an empty
`server.conf`, and the content is generated only after the program
starts, so `server.conf` might be an empty file. This also makes it
convenient to use a script to confirm the existence of this file:
```bash
touch server.conf
```
Currently, SRS does not support empty configurations and will report an
error. This PR is to solve this problem, making it more convenient to
use include.
`TRANS_BY_GPT4`
---------
Co-authored-by: Haibo Chen <495810242@qq.com>
2023-08-28 10:53:27 +08:00
