GB: Support enabling media forwarding through API instead of SIP.

[duiniuluantanqin]

Support external signaling service, SRS only acts as a media server. Simply push RTP directly.

for #3369

---

TRANS_BY_GPT3

[winlinvip]

External signaling is certainly needed.

I took a quick look and have a question: Is it generally allocated in SDP to determine if the incoming SSRC is valid?

It seems that there is currently no API available, so it is assumed that all are accepted by default. The URL used is the SSRC instead of the device ID. It would be better to provide an HTTP API to set the device ID corresponding to the SSRC for better consistency.

Of course, an HTTP API would be more complex. We can consider if there are any better solutions available.

TRANS_BY_GPT3

[duiniuluantanqin]

Add a new API, gb/v1/publish.

First, you can use Postman or a similar tool to send an HTTP POST request, as shown below.

POST /gb/v1/publish/
{
    "clientip": "192.168.1.100",
    "stream": "testname",
    "ssrc": "1234567890"
}

• ssrc is randomly generated, typically a 10-digit number, and you should ensure its global uniqueness.
• stream is the name of the stream, which you can use to pull the stream.

Then, you should recieve the response like:

{"port":9000, "is_tcp": true}

This indicates that the srs listening port is 9000.

currently srs only supports TCP transmission.

Now, you can use srs_bench to push RTP over TCP. The usage is as follows:

srs_bench -sfu gb28181 -mr tcp://127.0.0.1:9000 -ssrc 1234567890 -sa avatar.aac -sv avatar.h264 -fps 25

Finally, you can test the stream with:

rtmp://127.0.0.0/live/testname

TRANS_BY_GPT4

[duiniuluantanqin]

add gb_test func TestGbPublishWithApi
you can just test it with the commond

srs_gb28181_test --test.run TestGbPublishWithApi

[duiniuluantanqin]

https://github.com/ossrs/srs-sip
An external SIP signaling server that accompanies the SRS package.

TRANS_BY_GPT4

[duiniuluantanqin]

Please refer to the following GitHub pull request: #4101

TRANS_BY_GPT4