This document was generated from CDN thread
Created by: Raymond Ng on 01-12-2010 10:33:49 AM
Hello,
Since Codian API version 2.6 I have been using the uniqueId the codians returns when doing a conference.enumerate as a reference to the room.
This uniqueId was a api request from VisionsConnected so that when a room name changes the id remains the same.
This morning we restarted the Codian media2 blade because we installed new ssl certificates (old ones expired) and noticed that all the rooms got a different uniqueId!
All the references in the application still points to the rooms old uniqueId's.
We search through the configuration.xml and the uniqueId is not saved with the conferencerooms.
Is this a known issue?
Is it on a roadmap to fix this?
Because if the uniqueId is not consistent after a reboot than it's not usefull to use the uniqueId and renders it useless.
