You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe your expectation.
To handle media service restart exceptions, it is requested to return the unique service_id instead of server_id. In previous versions, server_id was used to handle exceptions, but it has now been assigned as the unique ID for the machine and cannot be changed during service restarts. Therefore, it is preferred to use service_id and it is expected to be returned as well.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered:
winlinvip
changed the title
触发hook /api/v1/sessions 接口时,未将service_id回带过来
API: No service_id in body of HTTP callback. 触发hook /api/v1/sessions 接口时,未将service_id回带过来
Feb 15, 2023
winlinvip
changed the title
API: No service_id in body of HTTP callback. 触发hook /api/v1/sessions 接口时,未将service_id回带过来
API: No service_id in the body of the HTTP callback. When triggering the /api/v1/sessions interface, the service_id was not carried back.
Jul 29, 2023
Description
Please description your issue here
SRS Version: v5.0.141
SRS Log:
Replay
Please describe how to replay the bug?
Step 1: Configure the hook interface
Step 2: Hook callback data
Expect
Please describe your expectation.
To handle media service restart exceptions, it is requested to return the unique
service_id
instead ofserver_id
. In previous versions,server_id
was used to handle exceptions, but it has now been assigned as the unique ID for the machine and cannot be changed during service restarts. Therefore, it is preferred to useservice_id
and it is expected to be returned as well.TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: