Introduction
The Zapper channel lineup can be managed through the EELM Server. It allows the Zapper channel lineup to be managed programmatically without inputting the channel manually. In addition, it allows the operator to perform channel change programmatically. For more details on the EELM Server, please refer to this article.
Note: This will not work for 3rd party apps
Enabling the EELM feature
To enable the EELM feature, please add the following INI parameter
- eelm.enable=1
NB: The device needs to be rebooted after the configuration change
Using the EELM API for the Zapper Lineup
This section shows some useful examples of editing the channel through the EELM Server. In my example, I am using an H200 STB with IP 10.0.7.82
Create a channel "101"
curl -X 'POST' \
'http://10.0.7.82:8090/api/v2/zapper/channels' \
-H 'accept: */*' \
-H 'Content-Type: application/json' \
-d '{
"addr": "233.22.133.1",
"desc": "UDP 1",
"drm_session_type": "persistent",
"encrypting_server": "string",
"encryption_request_header": {},
"encryption_type": "string",
"igmpv3_addr_list": [
"198.51.100.42"
],
"igmpv3_mode": "asm",
"name": "101",
"port": 8110,
"starting": false,
"type": "udp"
}'
hint: set the "starting" to specify the 1st channel being played after boot
Get the channel "101" info
curl -X'GET' 'http://10.0.7.82:8090/api/v2/zapper/channels/101' -H 'accept: application/json'
Sample output
{
"addr": "233.22.133.1",
"desc": "UDP 1",
"drm_session_type": "persistent",
"encrypting_server": "string",
"encryption_request_header": {},
"encryption_type": "string",
"igmpv3_addr_list": [
"198.51.100.42"
],
"igmpv3_mode": "asm",
"name": "101",
"port": 8110,
"starting": false,
"type": "udp"
}
Return complete channel lineup
curl -X 'GET' 'http://10.0.7.82:8090/api/v2/zapper/channels' -H 'accept: application/json'
Sample output
{
"channels": [
{
"addr": "233.1.1.20",
"desc": "UDP 20",
"drm_session_type": "persistent",
"encrypting_server": "string",
"encryption_request_header": {},
"encryption_type": "string",
"igmpv3_addr_list": [
"198.51.100.42"
],
"igmpv3_mode": "asm",
"name": "20",
"port": 8110,
"starting": false,
"type": "udp"
},
{
"addr": "233.22.133.1",
"desc": "UDP 1",
"drm_session_type": "persistent",
"encrypting_server": "string",
"encryption_request_header": {},
"encryption_type": "string",
"igmpv3_addr_list": [
"198.51.100.42"
],
"igmpv3_mode": "asm",
"name": "101",
"port": 8110,
"starting": true,
"type": "udp"
}
]
}
Create or change the channel info of channel "101"
curl -X 'PUT' \
'http://10.0.7.82:8090/api/v2/zapper/channels/101' \
-H 'accept: */*' \
-H 'Content-Type: application/json' \
-d '{
"addr": "233.22.133.1",
"desc": "UDP 1",
"drm_session_type": "persistent",
"encrypting_server": "string",
"encryption_request_header": {},
"encryption_type": "string",
"igmpv3_addr_list": [
"198.51.100.42"
],
"igmpv3_mode": "asm",
"name": "101",
"port": 8110,
"starting": false,
"type": "udp"
}'
Tune in to channel 101
curl -X 'POST' 'http://10.0.7.82:8090/api/v2/zapper/changeChannel' -H 'accept: */*' -H 'Content-Type: application/json' -d '{ "name": "101" }'
Delete channel 101
curl -X'DELETE' 'http://10.0.7.82:8090/api/v2/zapper/channels/101' -H 'accept: */*'
Comments
0 comments
Article is closed for comments.