RBFS Operational State API
The RBFS Operational State API provides endpoints for enabling and disabling LI on a per-subscriber basis:
-
A HTTP POST request to
/subscribers/{subscriber_id}/enableLI? id={li_id}&direction={li_direction}&med_ip={med_ip}&med_instance={med_instance}&med_port={med_port}enables LI for the specified subscriber -
A HTTP POST request to
/subscribers/{subscriber_id}/disableLI?id={li_id}disable LI for the specified subscriber
The table below lists the request parameters:
| Parameter Name | Description |
|---|---|
|
Subscriber identifier that is generated by RBFS, for example, 72339069014638701. |
|
Identifier for Lawful Interception. This is a unique Identifier used by the mediation device to identify the intercepted subscriber. The range can be between 1 to 4194303. |
|
LI direction. Values are: INGRESS, EGRESS, BOTH. |
|
VRF instance through which the mediation device is reachable. |
|
IPv4 address of the mediation device |
|
UDP port(MD)(49152-65535), mirrored traffic is forwarded |
All parameters are mandatory to enable LI.
Request Examples
Enabling LI:
The example below shows a curl command to enable LI:
| Specify the element name of your system instead of {element_name} in the preceding command. |
curl -i -H "Content-Type: application/json" -X POST 'http://198.51.100.76:19091/api/v1/rbfs/elements/{element_name}/services/opsd/proxy/subscribers/72339069014639042/enableLI?id=66666&direction=BOTH&med_instance=libox&med_ip=10.0.0.1&med_port=49153'
Disabling LI:
The example below shows a curl command to disable LI.
| Specify the element name of your system instead of {element_name} in the preceding command. |
curl -i -H "Content-Type: application/json" -X POST 'http://198.51.100.76:19091/api/v1/rbfs/elements/{element_name}/services/opsd/proxy/subscribers/72339069014639042/disableLI?id=66666'
Response Output
The following is a sample output response for the curl command:
Output Response for enable & disable request:
HTTP/1.1 204 No Content Date: Wed, 17 Sep 2025 06:23:47 GMT Server: Python/3.10 aiohttp/3.8.1
In this example, the response code '204' is expected as LI request is successfully processed, but no return message will be received.