GB28181: I'm thinking about saying goodbye.

[winlinvip]

The consensus we have currently reached is: to remove GB's SIP support from SRS and only support the media processing part.

What I am currently considering is: whether it is possible to go further and completely not support the access of GB28181.

Reasons are:

• The monitoring scenario mainly involves RTSP, using FFmpeg to pull RTSP and convert it to RTMP for SRS pushing. Refer to FAQ: RTSP

• The GB scenario is very small and can be completed with other open-source projects for protocol conversion, such as ZLM

• Even if SRS supports GB, it only supports the media part of GB. It would still require a significant amount of time to integrate with the SIP project, maintain documentation, and provide future updates support.

• Currently, we have too many directions, such as API improvement, RTC improvement, QUIC, JS virtual machine, slice protocol improvement, and so on.

• After asking around, everyone still wants to continue supporting, so let's create a new repository. The owners will be @xialixin and @duiniuluantanqin. The repository address is ossrs/srs-gb28181.

• Let GB develop independently, let the bullets fly for a while, maybe they will fly quite well.

TRANS_BY_GPT3

[648540858]

Please keep the media section.

TRANS_BY_GPT3

[1024mg]

Spend your energy in the direction you believe is right.

TRANS_BY_GPT3

[winlinvip]

@1024mg Makes sense.

We initially thought that supporting surveillance was definitely the way to go because IoT's audio and video definitely need support. Later, we found that IoT's audio and video are still based on RTSP, which falls under the scope of FFmpeg pulling RTSP. After realizing this, we found that streaming can be supported by GB, but we didn't expect there to be so many challenges and so few applications (which also leads to few developers) and contributions.

These factors have resulted in a small number of SRS users who have raised most of the issues but are still unable to resolve them. Undoubtedly, this represents that something is not right. After thinking it over, it may be a matter of direction. Our main focus is not here.

TRANS_BY_GPT3

[zhOrange]

Do not forget the original intention. After clarifying the ultimate goal of the project, you will know what can be abandoned and what can be retained with limited resources.

TRANS_BY_GPT3

[winlinvip]

Um, thank you everyone. Let's let everyone maintain it first, and after the maturity level is higher, we can merge it back into the main project.

TRANS_BY_GPT3

[hejinenPrivate]

May I ask if this new repository is migrated based on the SRS 4.0 version or the 5.0 version?

TRANS_BY_GPT3

[ghostsf]

Merging is a problem, huh.

TRANS_BY_GPT3