1. Manuals
  2. Brands
  3. Savant Manuals
  4. Server
  5. PAV-SMS2001
  6. Deployment manual

Savant PAV-SMS2001 Series Deployment Manual

Ip audio music server
Hide thumbs Also See for PAV-SMS2001 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
Savant® IP Audio Music Server
Deployment Guide
Document Number:
009-1602-02
Document Date:
December 2019
Document Supports:
da Vinci 8.8 or higher
This document will guide the installer through the process of installing, configuring, and adding Savant IP Audio Music Server to a RacePoint Blueprint™
configuration.
–
IP Audio Music Server [PAV-SMS2001-XX]
Copyright © 2019 Savant Systems, LLC
- 1 -
45 Perseverance Way, Hyannis, MA 02601
Savant.com
| 508.683.2500

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PAV-SMS2001 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Savant PAV-SMS2001 Series

Summary of Contents for Savant PAV-SMS2001 Series

  • Page 1 Document Date: December 2019 Document Supports: da Vinci 8.8 or higher This document will guide the installer through the process of installing, configuring, and adding Savant IP Audio Music Server to a RacePoint Blueprint™ configuration. – IP Audio Music Server [PAV-SMS2001-XX] Copyright ©...

  • Page 2: Table Of Contents

    Managing IP Addresses ....................14 Blueprint Configuration....................6 5.1. Basic Blueprint Layout ..................6 Network Changes ......................14 5.2. Adding a Savant Music Server to a Configuration ........7 Appendix B: Setting Static IP Address ................15 Expansion ..........................8 Appendix C: DNS (Add, Remove, Query) ............... 16 6.1.
  • Page 3 Important Safety Information - Read First Safety Statements Before installing, configuring, or operating any equipment, Savant recommends All safety instructions below should be read, understood, and applied under all that each dealer, integrator, installer, etc. access and read all relevant technical relevant circumstances when working with this equipment.

  • Page 4: Before You Begin

    (System Monitor) 2. Deployment Steps To successfully deploy a Savant IP Audio Music Server, follow the steps listed below. This page can be used as a checklist to track progress as items are completed. Review product specifications and connection details ................................

  • Page 5: Wiring And Connections

    4. Installation The Savant IP Audio Music Server (PAV-SMS2001) can be placed on any solid flat surface such as a table or shelf, or can be installed in any 1U NEMA rack shelf. Savant IP Audio Music Server Deployment Guide Copyright ©...
  • Page 6 5. Blueprint Configuration 5.1. Basic Blueprint Layout The image below shows a simplified example of a basic RacePoint Blueprint layout for the Savant IP Audio Music Server: Winespring Inn Host SIPA50SM Living Room Speakers Inputs Assigned Inputs Assigned Inputs Assigned Outputs...
  • Page 7 5.2. Adding a Savant Music Server to a Configuration To add a Savant IP Audio Music Server to a RacePoint Blueprint configuration, follow the steps outlined below. The basic process is the same for all IP Audio devices. Within the open Blueprint configuration for the site: Click Show Library.
  • Page 8 6. Expansion Up to 45 Savant IP Audio devices can be connected using any compatible AVB/TSN certified switch. The example below shows a simplified Blueprint layout using multiple IP Audio devices connected via AVB switch. 6.1. AVB Blueprint Layout Winespring Inn Host...
  • Page 9 AVB_A Ethernet Port (AVB (A)) AVB_B Ethernet Port (AVB... All Savant IP Audio devices in a multi-source AVB deployment of this type must be connected to the AVB switch via their Data/Ethernet ports as shown above. Savant IP Audio Music Server Deployment Guide Copyright ©...
  • Page 10 7. Web User Interface (Web UI) Savant IP Audio devices have an available Web UI, which includes options for control and real-time management of audio connections, as well as a number of device settings. This can be especially useful for troubleshooting potential issues in the field.
  • Page 11 Apply & Restart NOTE: Setting the IP Address with a Static Address from the WebUI will automatically set the device’s DNS to 8.8.8.8 and 8.8.4.4 (Google). Savant IP Audio Music Server Deployment Guide Copyright © 2019 Savant Systems, LLC 009-1602-02 | 191218...

  • Page 12: Savant Music Trim

    The service is generated in Blueprint. The streaming services are managed in the Savant Pro App. HELPFUL INFO: The Host must be connected to the Savant Cloud with a valid Host Binding in order to add streaming services to the system via the Savant Pro App.
  • Page 13 9.2. Savant Music Trim Input trim of the Savant Music 2.0 service can be adjusted from within System Monitor. The trim adjustment is from 0 dB to -12 dB. Below is an image of the Music Service System Monitor screen.

  • Page 14: Appendix A: Network Requirements

    Managing IP Addresses To ensure that the IP Address will not change due to a power outage, a static IP Address or DHCP reservation should be configured. Savant recommends using DHCP reservation within the router. By using this method, IP Addresses for all devices can be managed from a single UI, avoiding the need to access devices individually.

  • Page 15: Appendix B: Setting Static Ip Address

    Appendix B: Setting Static IP Address To assign a static IP address for a Savant IP Audio device, follow the steps outlined below: Open System Monitor. Double click the Host. Select Controller Info. Select the PAV-SMS2001. Copy the IP address.

  • Page 16: Appendix C: Dns (Add, Remove, Query)

    Appendix C: DNS (Add, Remove, Query) Manually setting DNS at the component level is generally not required, and is only sometimes relevant for devices utilizing a built-in Savant Music stream. Follow the steps shown below to add, remove, or query the configured DNS server(s) for IP Audio devices.
  • Page 17 Savant Systems, LLC. shall not be liable for any technical or editorial errors or omissions contained herein or for incidental or consequential damages resulting from the performance, furnishing, reliance on, or use of this material.

Table of Contents