This page gives an overview of the Streaming Media Service, describing its current status, where and
how it's developed and deployed, and who is responsible for maintaining it.
## Service Description
The Streaming Media Service (SMS) provides a video and audio transcoding and hosting service.
## Service Status
The Streaming Media Service is currently live/decommissioning.
-[Webpage with details of closure](https://help.uis.cam.ac.uk/news/sms-future-feb2021)
## Contact
Technical queries and support should be directed to [sms-support@uis.cam.ac.uk](mailto:sms-support@uis.cam.ac.uk) and will be picked up by a member of the team working on the service. To ensure that you receive a response, always
direct requests to [sms-support@uis.cam.ac.uk](mailto:sms-support@uis.cam.ac.uk) rather than reaching out to team members directly.
Issues discovered in the service or new feature requests should be opened as GitLab issues
The Streaming Media Service application is deployed using RPM packages. These are built by Gitlab CI in the [Application Server repository](https://gitlab.developers.cam.ac.uk/uis/sysdev/devgroup/sms/sms). These can be copied to the [Bes RPM package repository](https://bes.csi.cam.ac.uk) run by infra-sas@uis by following these [instructions](https://wiki.cam.ac.uk/ucs/Bes_-_Managed_Installation_Service#How_to_add_SLES_10.2F11_or_RHEL_.28S.29RPMS_to_Bes). As a last resort RPMs can be manually copied and installed.
Once the RPM packages are added to the [Bes RPM package repository](https://bes.csi.cam.ac.uk) installation is simply a matter of running `zypper up` as root.
Documentation
-------------
### Monitoring
The streaming Media Service is monitored by [nagios](https://nagios.uis.cam.ac.uk/nagios/)
There is also a [status page](https://sms.cam.ac.uk/adm/status) that checks the various components of the service and returns 200 if everything is functioning normally.