nmos-cpp icon indicating copy to clipboard operation
nmos-cpp copied to clipboard

Change sender configuration after activation

Open puscas opened this issue 5 years ago • 3 comments

Hi!

I need some guidance in understand how should I proceed when is necessary to change the destination_port and destination_ip after a successful first configuration.

After I configure the node with the bulk control interface (/bulk/senders via POST) the node is properly configured and enable. If I want to stop and reconfigure the node with a different transport_params, what REST API call(s) should I do?

Kind Regards, puscas

puscas avatar Oct 14 '20 22:10 puscas

It is the same. Use either the /bulk/senders POST endpoint or the /single/senders/{senderId}/staged PATCH endpoint to update the parameters and activate the new configuration.

garethsb avatar Oct 16 '20 06:10 garethsb

Hi Gareth,

thank you very much for your comment.

I tried your suggestion, but unfortunately I receive the status code 400.

{ "code": 400, "error": "Bad Request", "debug": "schema validation failed at /transport_params/0/destination_ip - no subschema has succeeded, but one of them is required to validate JSON - "232.105.26.177"" }

I see it is related with the values set in the /constraints, after the first valid configuration and activation.

Kind Regards, puscas

puscas avatar Oct 16 '20 08:10 puscas

I've just tried to replicate the scenario and it works OK for me, so I must be doing something different. I'd like to try to help. Please would you share what the /constraints and /staged endpoints return for you, and exactly what request you are making?

garethsb avatar Oct 16 '20 17:10 garethsb