Skip to content

v3.3.0

Choose a tag to compare

View all tags
@stackia stackia released this 12 Nov 17:20
· 659 commits to main since this release
v3.3.0
482a64b

新功能

  • 支持华为 FCC 协议
    • 国内有四种 FCC 协议：电信（中兴）、华为 v1、华为 v2、烽火。此前 rtp2httpd 只实现了电信协议，这个版本新增了华为 v1 协议。
    • 华为协议有更好的稳定性和 NAT 穿透能力。有些省份必须依赖 NAT 穿透才能使用 FCC（例如山西电信、山西联通）。
    • 华为 IPTV 平台同时支持电信协议和华为协议。从这个版本开始，对所有 8027 端口 FCC 服务器都默认使用华为 v1 协议交互。
    • 如果你遇到问题，可以使用 fcc-type 参数手动指定协议类型，见文档 fcc-type 参数说明
  • 支持 wget 作为 curl / uclient-fetch 不存在时的替代工具
  • 优化 Docker 镜像大小，用 alpine 作为 base，从 90 MB 缩减到 9 MB

问题修复

  • 改进 M3U/EPG 更新失败时的重试逻辑，现在将会尝试尽快重试，而不是等下一个更新周期
    • 解决了之前 rtp2httpd 随开机启动时，经历短暂无网状态导致无法及时拉取 M3U/EPG 问题
  • 修复长时间运行可能随机崩溃问题
    • 这个问题由 v3.2.0 引入，仅在使用外部 M3U 时发生
  • 修复 /epg.xml.gz 在一些播放器无法识别问题（例如酷9）
  • 修复状态面板的"断开"、"修改日志等级"有概率失败报错问题
  • 调整网页播放器 RTSP 回放时的片段长度，改善对一些源的兼容性

New Features

  • Huawei FCC protocol support
    • There are four FCC protocols in China: Telecom (ZTE), Huawei v1, Huawei v2, and FiberHome. Previously rtp2httpd only implemented the Telecom protocol; this version adds Huawei v1.
    • The Huawei protocol offers better stability and NAT traversal capability. Some provinces require NAT traversal to use FCC (e.g., Shanxi Telecom, Shanxi Unicom).
    • Huawei IPTV platforms support both Telecom and Huawei protocols. Starting from this version, all FCC servers on port 8027 default to using the Huawei v1 protocol.
    • If you encounter issues, you can manually specify the protocol type using the fcc-type parameter. See fcc-type parameter documentation
  • Support for wget as a fallback when curl / uclient-fetch is not available
  • Optimized Docker image size using alpine as base, reduced from 90 MB to 9 MB

Bug Fixes

  • Improved retry logic when M3U/EPG updates fail — now retries as soon as possible instead of waiting for the next update cycle
    • Resolves the issue where rtp2httpd started at boot could not fetch M3U/EPG in time due to brief network unavailability
  • Fixed potential random crash during long-running operation
    • This issue was introduced in v3.2.0 and only occurs when using an external M3U
  • Fixed /epg.xml.gz not being recognized by some players (e.g., Ku9)
  • Fixed intermittent failures when using "Disconnect" or "Change Log Level" in the status panel
  • Adjusted RTSP playback segment length in the web player to improve compatibility with some sources
Assets 54
Loading