Hi,
Discovery has some questions about the Prism integration in Dataminder. Bernard Pichot and Thomas Gunkel are aware of it.
best regards
Yannick
the end user would like to get the SDP fromthe Prism.
Why not using the NMOS API to get?
Hi Yannick. Our current connector is using the Prism REST API only. I have some questions to you:
* Can you share more info on the NMOS specs that are supported by Prism, e.g. the supported IS-04 and IS-05 version. Then we can have a closer look and check how those commands can be added to our existing connector.
* What are the expectations the customer has with the SDP file on DataMiner? Just display the SDP info? Or is the customer after a NMOS IS-05 based routing solution and wants to use the SDP to patch on destinations?
* Does the customer have an IS-04 registry? If that is the case, we could connect DataMiner to the IS-04 registry and get IS-04 info (plus the SDP) from there.
Hi Thomas,
Prism supports IS04 IS05
the NMOS API is available from the unit
the easiest will to discuss with:
-Alberto De Luca
-bernard.pichot@skyline.be
they are leading this.
best regards
Yannick
Yannick, can't see any benefit in asking the same questions here - we have already an email thread shared with Skyline and Telestream.
Hi Alberto. Thanks for looking into this as well! We are trying to share such information with the whole Skyline team and our customers via Dojo that more people can contribute.
There are also other customers asking for something very similar. If you don’t mind we would like to take this further on Dojo instead of emails to make sure everybody in the Skyline and Telestream team can contribute.
Hi Thomas, hope you’re fine – I’m sure there’s a lot of interest in the industry about NMOS 🙂 Happy to facilitate the conversation from Discovery, so we had already put Telestream in touch with Skyline – I had not posted anything on the DOJO yet as I was verifying what is still under NDA for this specific project.
In short, I was brought to think that any specific parameter value that is a KPI to assess a state (let’s say “ON/OFF”, for simplicity) would need to be exposed via the API already integrated: the fact that a parameter is set via IS-05 would be not relevant from my point of view – intercepting the value in the nmos command would not give any actual info about the state of the device.
Any thoughts?
Hi Yannick,
Can you formulate the questions you have, so that the community can support you with the right answers?