recording-server-id must start with Recording-Server to be treated as a recording server by the rest of the platform. Each receiving core server writes its own lidf_lea_config row with its locally-resolved enabled, and queues a lidf_lea_update row so SiPbx applies the change.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/servers' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"recording-server-id": "Recording-Server2",
"name": "string",
"address": "string",
"contact": "string",
"phone": "string",
"email": "string",
"ccc-ip": "string",
"ccc-port": 0,
"cdc-url": "string",
"cdc-type": "string",
"enabled": "yes",
"enabled-hosts": {
"core1.example.com": "yes",
"core2.example.com": "no"
}
}'{
"code": 0,
"message": "string"
}