User manual POLYCOM SR12 DESIGN GUIDE REV E

[. . . ] Design Guide for the Polycom SoundStructure C16, C12, C8, and SR12 Revision E | January 2011 | 1725-33186-001 Design Guide for SoundStructure C16, C12, C8, and SR12 ii Polycom, Inc. Trademark Information Polycom®, the Polycom "Triangles" logo, and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc. , and are registered and/or common-law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U. S. and foreign patents and/or pending patent applications held by Polycom, Inc. [. . . ] When multiple devices are linked over OBAM, only one ethernet interface or RS-232 port is required to be used, although any of the ports may be used. LAN Interface SoundStructure devices include a rear-panel LAN interface, shown in the following figure, that supports 10/100 Mbps communication with Auto-MDIX (medium dependent interface crossover) capability. Auto-MDIX enables the use of either a standard CAT5e cable or cross-over cable to connect to an Ethernet network. The SoundStructure device will detect either connection and work properly. PIN 2: TXD PIN 3: RXD PIN 5: GROUND PIN 7: CTS PIN 8: RTS 1 2 RS-232 REMOTE CONTROL 1 1 2 LAN C-LINK2 IN OBAM OUT IR 12V REMOTE CONTROL 2 LAN 10 - 1 Design Guide for the Polycom SoundStructure C16, C12, C8, and SR12 Dynamic IP Addresses By default, the SoundStructure device accepts an IP address from a DHCP server. Once assigned, IP addresses can be determined with the SoundStructure Studio software via the SoundStructure device discovery method. To determine the IP address, connect to the device using the Search for Devices option as shown in the following figure. SoundStructure Studio will display a list of systems found on the network interface specified by the Search Network option. The SoundStructure systems that are found will be shown with their system name, IP addresses, MAC addresses, and firmware version as shown in the following figure. 10 - 2 Network Management By default the system name is set to "SoundStructure System" as shown in the next figure. The system name is used to easily identify units and can be set with the SoundStructure Studio as shown in the previous figure by entering the name and pressing the Apply button or by using the sys_name API command as shown below. set sys_name "Room 475B" the system will respond with the command acknowledgement val sys_name "Room 475B" Now the system name has been set to "Room 475B" and that's how it will be identified during the next time Connect to Devices is selected. Save the project to disk with the File Save or File Save As option from SoundStructure Studio to save the file to disk and also when working online to force the SoundStructure device to store the system name permanently. Link-Local IP Addresses SoundStructure devices configured for DHCP and running version 1. 3 or later firmware will default to the link-local IP address of 169. 254. 1. 1 when there are no DHCP servers available to provide an IP address when the SoundStructure device powers up. The link local addressing makes it possible to connect to a computer directly to a SoundStructure device with either a straight-through or crossover Ethernet cable without either having to set a static IP address or having a DHCP server available. 10 - 3 Design Guide for the Polycom SoundStructure C16, C12, C8, and SR12 Assuming the computer that is running SoundStructure Studio also does not have an IP address provided by a DHCP server, the local computer will also have a link-local address of the form 169. 254. abc. def. The computer may be connected either directly to the SoundStructure device or connected through a network to the SoundStructure device, and then SoundStructure Studio will be able to automatically discover and connect to the SoundStructure device. When connected directly to the device, the local computer may use either with a straight-through or cross-over Cat5 cable. The following figure shows how the SoundStructure device gets its IP address. If there is a static IP address assigned to SoundStructure, then that address will be used. If there is a DHCP server, then the SoundStructure device will use the address provided by the DHCP server. If there is no DHCP server, then the SoundStructure device will use a locally generated link-local IP address which will default to 169. 254. 1. 1 assuming this does not create a conflict with a different device on the network. Please note that when the SoundStructure device has a link-local IP address, if a DHCP server comes online at a later time, the SoundStructure device will accept an IP address provided by the DHCP server and will no longer have the link-local IP address. Need an IP address Static IP Set ?N Y Use Static IP address DHCP Server?N Y Use DHCP server supplied IP address Use Link-Local address 169. 254. 1. 1 (if that creates a conflict the system will continue until it finds an available address) Static IP Addresses SoundStructure devices may also be assigned a static IP address directly from SoundStructure Studio or manually via the API and a terminal session. 10 - 4 Network Management Assigning A Static IP Address Via Ethernet Over the network interface, first connect the device to the network and accept the dynamic IP address from a DHCP server. Once connected to the device, the static IP address may be set directly from the wiring page within SoundStructure Studio. Hit the apply button to change the IP address. Changing the IP address will force SoundStructure Studio to lose connection to the device. Reconnect to the SoundStructure device using the new IP address and save the settings to a file using the File Save or File Save As which when working online will also force the SoundStructure device to store the IP address permanently in the device. The project must be saved to ensure the IP address is set permanently - otherwise upon the next reboot of the device, the IP address will revert to the previous settings. [. . . ] If the local listeners are farther away than the critical distance form the local talker, some form of voice lift may be required for adequate intelligibility. For rooms smaller than approximately 20 feet x 20 feet, the voice lift application is really not necessary and is just starting to be of some benefit in rooms 30-feet (9 meters) square. Just as adding gain to a microphone to try to compensate for a critical distance issue does not work, adding sound reinforcement to compensate for a noisy room doesn't work well either. The microphones that pick up the noise will reinforce that noise into the room, adding to the noise rather than making it easier to be heard. [. . . ]