Dear community,

I have a question related to SRM and the “Quarantine” feature.  Here is the context.  Let’s say there is a “contributing” booking in the DataMiner system that matches a “contributing” resource which has certain capabilities.  Another “main” booking in the system is making use of this contributing resource.  The contributing resource was selected and added to the main booking because of the required capability that matches the one of the contributing resource.
Now outside of the DataMiner system some changes were done on the contributing booking.
To match the real life situation, it was needed to update the capabilities of the contributing resource.  Due to a mismatch between the required capabilities of the main booking (still the original ones) and the updated capabilities of the contributing resource included in the booking, the main booking has been “quarantined”.  So far the system behaves as expected.
Due to the quarantine status, this booking can also not be finished for the time being.

Now some questions:

• What is the best way to “fix” this situation to get the main booking out of quarantine without re-creation the booking?  Somehow it should be possible to update the required capabilities of the existing main booking so that it matches again with the included resource.  How could this be done?
• Once done, will the booking be automatically taken out of quarantine? Or is an extra push needed?

To further explain the real life use case.  The contributing booking/resource represents a satellite demodulator tuned to a certain frequency.  The frequency is one of the capabilities on the contributing resource which has been updated to a new value.  The main booking represents an individual Transport stream carrying a single service (SPTS) out of the demodulator device tuned to this transponder/frequency.