...
- No reporting to identify unused conferences
- No process for deleting unused conferences
- No convention for naming endpoints or conference
- No DNS name for the Codian or Telepresence Management Suite
- Endpoints on public IPs (mobile endpoints) can be spammed
- AD integration for the Codian bridge
- Cisco TelePresence Content Servers (uit-content1 and uit-content2) should have signed SSL certificates
Content Server
content server notes:
- Investigate error playing recordings via silverlight or flash on content server: "cannot play recording. An error has occured."
- Need live enabled mpeg-4 media server for livestreaming mpeg4
- Switch storage to \\titan\ from
spooky - Should default to SIP when calling from the "create recording" page
- Add a max length for calls
- Change gatekeeper to dns name
- Change DNS name of oontent server to recordings.uit.tufts.edu or something
- Find out tufts\tcsnasuser (aka UIT-CONTENT1\tcsnasuser) password, local admin, and add them to password safe
- Get rdp/admin on uit-content1.uit.tufts.edu
- Document that tufts\tts_videoconferencing_admins has admin, remove individually configured users
- Expand licensing (2 live streams and 5 recorded calls aren't enough for production service)