How media server supports http notify?
Modify the media server configuration file to enable HTTP notifications by setting the <http_notify> parameter under <rtsp>,<rtmp>,<srt>,<http flv> tag.
<on_onnect> :
Sets HTTP connection callback. When clients issues connect command an HTTP request is issued and command processing is suspended until it returns result code. If HTTP 200 code is returned then the session continues.
HTTP request receives a number of arguments. POST method is used with application/x-www-form-urlencoded MIME type. The following arguments are passed to caller:
protocol=rtsp/rtmp/srt/httpflv
call=connect
addr - client IP address
app - application name
url - URL requested by the client
name – stream name
clientid – session id
<on_play> :
Sets HTTP play callback. Each time a clients issues play command an HTTP request is issued and command processing is suspended until it returns result code. If HTTP 200 code is returned then the session continues.
HTTP request receives a number of arguments. POST method is used with application/x-www-form-urlencoded MIME type. The following arguments are passed to caller:
protocol=rtsp/rtmp/srt/httpflv
call=play
addr - client IP address
app - application name
tcurl – tcUrl
name – stream name
clientid – session id
<on_publish> :
The same as on_play above with the only difference that this node sets callback on publish command. Instead of remote pull push is performed in this case.
<on_done> :
Sets play/publish terminate callback. All the above applies here. However HTTP status code is not checked for this callback.
<notify_method>
Sets HTTP method for notifications. Default is POST with application/x-www-form-urlencoded content type.
Support GET and POST method.