SA-Announce Notification Platform User Manual for Avaya Version

Transcription

1 SA-Announce Notification Platform User Manual for Avaya Version

2 About Syn-Apps Syn-Apps L.L.C. was founded in 2001 as a consulting firm focused on developing software for IP telephony platforms. Since that time, Syn-Apps has evolved as a market leader in enterprise-wide paging and notification solutions designed to improve business processes, increase safety, and streamline internal and external communication. Since 2001, over 2,000 organizations have integrated our notification software with phones, paging systems, IP speakers, and hundreds of other internal systems and services. Syn-Apps has an extensive knowledge base in numerous development technologies. In addition, Syn-Apps has a strong background in network design and networking fundamentals. We believe this combination of experience in a broad range of technologies allows us to offer our customers an end-to-end application development solution. We believe that in order to have a successful application deployment, one should not only understand the development environment, but also understand how the application will interact with the rest of network. Syn-Apps has extensive networking experience based on a number of network development and design projects for many Fortune 100 companies. We believe that this enables us to become a valuable asset to any development team. Syn-Apps developers have a wide variety of development experience in many diverse industries. Our developers have been employed by, or consulted for companies such as Oracle, Microsoft, Cisco, General Motors, General Dynamics, Bloomberg, and many others. All of our developers have a keen understanding of the software development life cycle and know how to develop successful applications. At Syn-Apps we understand the importance of a team environment and are comfortable developing and sharing information to ensure that the best of breed product is produced.

3 Contents 3 Table of Contents Part 1 SA-Announce Overview 9 Part 2 Application Features 12 Part 3 Manual Conventions 15 Part 4 Information Center 17 Part 5 System Requirements 20 1 Application... Server Requirements 21 Window s Server 22 Window s Server 23 Disabling UAC Disabling Public... Firew all 24 Disabling IE... Enhanced Security 25 Verifying IIS Installing ASP.NET Window s Server 27 2 AVAYA... Requirements 28 Configure AVAYA... Aura 29 Setup of Avaya... 96xx Series Phones 29 Configure Avaya... Aura Utility Server 31 Configure Avaya... Aura Communication Manager 34 Configure IP Netw... ork Region 35 Administer IP Codec... Set 35 Administer IP Node... Names 36 Administer SIP Signaling... Group 36 Administer SIP Trunk... Group 37 Administer Route... Pattern 38 Administer Private... Numbering 38 Administer AAR Analysis Administer Stations Configure Avaya... Aura Session Manager 40 Add SIP Domain Add Location Add SIP Entity - Communication... Manager 44 Add Adaptation Add SIP Entity - SA-Announce Add Entity Link - Communication... Manager 47 Add Entity Link - SA-Announce Add Time Ranges Add Routing Policy Add Dial Patterns Configure AVAYA... IP Office 52 SIP Trunk Configuration... for IP Office 53 Enable SIP Trunks Administer SIP Line Administer Incoming... Call Route 62 Administer Short... Code 64 3

4 4 SA-Announce User Guide Configure AVAYA and 96x1 Series IP Deskphones 65 SA-Announce... >> Initial Application Configuration for IP Office 71 3 Network... Requirements 72 Firew all Ports Multicast Requirem... ents 73 Part 6 Installation Procedure 75 1 Update... Procedure 76 Part 7 Configuration Utility 80 Part 8 Post Configuration Steps 83 1 Avaya... Endpoint Configuration 84 2 SIP Trunk... Setup 84 3 IP Speaker... Setup 86 4 Group... Creation 86 Part 9 Initial Application Configuration 89 1 First Time... Login 89 2 Broadcast... Service Settings 90 Avaya Aura Advanced... Settings 91 Avaya IP Office... Advanced Settings 92 Verification... Steps 94 Phone Features Multicast... Configuration 97 4 User... Management 100 Part 10 Notification Group Configuration SA-Announce... Notification Group Types 105 Em ergency Alert Norm al RecordNPlay Text Notification... Group Setup IP Phones Desktop... Clients Cloud... Services IP Speakers Syn-Apps... Paging Relay Static... Streams Valcom Beacons Mass... Notification 128

5 Contents 5 Part 11 Creating Emergency Alert Groups 130 Part 12 SA-Announce Scheduler Creating... Schedules Using the Scheduler Tool Editing... A Schedule 142 Editing Associated... Scheduled Events Audio... Upload 144 Custom izing... Audio Feedback 146 Audio File... Descriptions 147 Part 13 Sending A Text Message Message... Browser 151 Part 14 SA-Announce Reporting Notification... Group Report Notification... Activity Report Schedules... Activity Report Text... Activity Report Login... Activity Report Users... Report 160 Part 15 Syn-Apps Analytics 162 Part 16 Web Service (API) 166 Part 17 Settings 170 Part 18 AMBER Alert Settings 172 Part 19 Weather Alert Settings Weather... Alert Supported Events 179 Part 20 Syn-Apps Paging Relay Configuration Supported... Paging Relays 185 Part 21 Syn-Apps Desktop Notification Client Configuration Supported... Desktop Notification Clients Syn-Apps... Desktop Notification Client Setup 188 Window s Requirem... ents 188 Macintosh Requirem... ents 188 DNC Configuration Automatic... Configuration 189 Manual Configuration

6 6 SA-Announce User Guide Part 22 Syn-Apps IP Speaker Configuration Supported... Syn-Apps IP Speakers Syn-Apps... IP Speaker Setup 196 Part 23 Legacy Algo Speaker Configuration Legacy... Algo Speaker Setup 202 Part 24 AND IP Speaker Configuration Supported... AND IP Speakers AND... IP Speaker Setup 208 Part 25 Atlas IP Speaker Configuration Supported... Atlas IP Speakers Atlas... IP Speaker Setup 214 Part 26 CyberData IP Speaker Configuration Supported... CyberData Speakers CyberData... Speaker Setup 219 Part 27 Valcom IP Speaker Configuration Supported... Valcom Speakers Valcom... IP Speaker Setup 223 Part 28 Alertus Configuration Supported... Alertus Devices Alertus... Device Setup 228 Part 29 Everbridge Configuration Everbridge... Setup 231 Part 30 Twitter Configuration 234 Part 31 Analog Paging System Integration 236 Part 32 Advanced Paging Configuration SA-Announce... Multicast Router/Switch Configuration Multi-Site... Centralized SA-Announce Server 239 Part 33 Troubleshooting Guide Installation... / Configuration 242 Window s Env... Issues 243 Installation Issues Licensing Issues Configuration... Issues 245

7 Contents 7 Upgrade Procedure... Troubleshooting 247 Reconfigure... SQL Server Web... Interface (GUI) 253 GUI Log File Group Creation Text Message Other Broadcaster... Service 258 Service Start... Issues 259 Endpoint Com... m and Issues 260 Audio Issues Scheduler... Service 262 Part 34 Help and Support Documentation Knowledge... Base Prepare... Report 266 7

8 SA-Announce Overview Part 1

9 SA-Announce Overview 1 9 SA-Announce Overview SA-Announce Notification System for Avaya The SA-Announce Notification System is a feature-rich notification system that couples with Avaya Aura Communication Manager and Avaya IP Office to provide text and audio notifications across an enterprise. The notifications can be in real time, such as emergency alerts and live audio notifications, or they can be scheduled via the scheduling system. SA-Announce integrates the phone system with a large number of disparate endpoints such as Avaya 9600 Series IP phones, Syn-Apps Paging Relay, Cloud Services, PC desktops, SynApps IP speakers, Algo IP speakers, Atlas IP speakers, AND IP speakers, CyberData IP speakers, Valcom IP speakers, alerts, Everbridge, and Alertus devices. Notifications can be made by picking up the phone and dialing the notification group directory number (as well as other methods such as automated via a relay or web).the SA-Announce Notification Platform has numerous audio streaming models that can be used to accommodate almost any notification requirements from one centralized server. Non-multicast enabled wide-area networks (WAN), can provide notifications to all remote sites using one centralized SA-Announce server with the addition of the Syn-Apps Paging Relay appliance. Streaming models include server sourced multicast, Paging Relay assisted multicast, and phone sourced multicast. Recent feature additions for SA-Announce include: Feature Description SA-Announce Bug Fixes & Software Maintenance General software maintenance, bug fixes, and performance enhancements made to SA-Announce. Facebook Integration Discontinued support for Facebook integration. Regroup Support Regroup notifier is now supported by SA-Announce. Updated Service Provider SA-Announce now receives AMBER Alerts from the DOJ (Department of for AMBER Alerts Justice). SA-Announce Bug Fixes & Software Maintenance General software maintenance, bug fixes, and performance enhancements made to SA-Announce. SA-Announce Bug Fixes & Software Maintenance General software maintenance, bug fixes, and performance enhancements made to SA-Announce. SA-Announce New User Interface Updated UI with a fresh color scheme and improved navigation. SA-Announce Scheduler SA-Announce Scheduler has been redesigned to use a new graphical scheduler tool that allows for easy scheduled event creation, including recurring events. New Calendar-Based Event Scheduler - Easily create and manage customizable events. All events per schedule are now visible in one centralized location, providing users with a simplified management experience. Users have the option to view events by day, week, or month Recurring Events - Schedule event frequencies and duration Customized Labels - Color-code specific scheduled events for better organization Note: The Overrides tab is no longer available, (formerly found by navigating to: Schedules >> Scheduled Broadcasts >> Overrides), as the graphical scheduler tool can be easily manipulated to create schedule overrides. The SA

10 10 SA-Announce User Guide Announce Configuration Utility will update any existing schedules, including their overrides, to the new format required by the graphical scheduler tool. Algo Speakers Now supports legacy Algo speaker integration. Refer to Legacy Algo Speaker Configuration for details. Algo IP speak er support coming soon! Paging Relay GPIO Emergency Alert Activation Paging Relays can now be configured to activate their GPO (general purpose output) Contact Closure for a specified time on a per-group basis. SA-Announce Paging Relay Syn-Apps' Paging Relay can now be used to activate SA-Announce Emergency Alert groups using Paging Relay GPIO. SA-Announce Reporting Built-in reports gather and export detailed information regarding notification group configuration data and system user permissions. Syn-Apps Analytics Provides a holistic view of all notification activity including both on and offpremise services. Generates complete activity reports including: Group name, Activation date/time, Initiator, Associate Endpoints, etc. SA-Announce Windows 2012 Server Syn-Apps SA-Announce now supports Windows 2012 server. SA-Announce Cloud Services Syn-Apps Cloud Services is now in beta and can be used to send notifications to mobile devices, internet messengers, SMS and Cisco Digital Media signage. Contact sales@syn-apps.com for further details. Active Directory Integration System users can now be authenticated against an Active Directory. SA-Announce Weather Alerts Weather Alerts have been updated to use the new NWS CAP feed. Short duration events such as Tornado Warnings can now be monitored. Additional events such as Civil Warnings and 911 Telephone Outage are also available. SA-Announce Group Opening Tone AND Speaker Text Assign custom audio files to serve as the notification group opening tone. Text messages now allow configuration of the text color, scroll speed and Option number of loops for AND IP speakers. s Schedule Time Zone Schedules now have an associated time zone for large deployments. SA-Announce AND IP Speaker Support SA-Announce now supports AND IP speakers. Desktop Notification Client SA-Announce now supports the Syn-Apps Desktop Notification Client allowing users of SA-Announce to target PC desktops with live and stored audio messages as well as text messages, AMBER Alerts, and Weather Alerts. The SA-Announce Notification System has been created using ASP.NET 3.5 to provide a rich user interface. Menus and lists that contain multiple items are searchable, highlight the menu or list in question and begin to type, the selection indicator will select the first matching item in the list. Tables and grids are sortable by clicking on the column header or the column to be sorted. All entries in the GUI are validated on the client side to prevent typographical errors. Tables and grids that can contain thousands of entries use a client side caching model that will allow for good performance without overloading the client or server system.

11 Application Features Part 2

12 12 2 SA-Announce User Guide Application Features The SA-Announce Notification System offers users a multitude of features. Define notification group endpoints which users can easily activate by calling a phone number from any phone on the network. Extends existing phone systems to become a notification system, requiring minimal installation and management. Endpoint Support - SA-Announce supports notifications to the following endpoint types: Endpoint Description Syn-Apps Paging Relay SA-Announce integrates with the Syn-Apps Paging Relay hardware device. Cloud Services SA-Announce integrates with a variety of endpoints to send notifications to registered users on and off-premise. Syn-Apps Desktop Notification Client Target the PC Desktop with audio and text notifications. Avaya IP multicast SA-Announce supports most Avaya 96xx series phones. supported phones Syn-Apps IP Speakers SA-Announce supports Syn-Apps IP Speakers offering plug and play integration. Algo IP Speakers SA-Announce supports Algo IP and legacy speakers. Valcom IP Speakers SA-Announce supports both version 1 and version 2 of the Valcom IP Speakers. CyberData IP Speakers SA-Announce supports the full line of CyberData IP speakers. AND IP Speakers SA-Announce supports all AND IP speakers with firmware version 796 or greater. Atlas IP Speakers SA-Announce supports the full line of Atlas IP speakers. Analog Paging Systems SA-Announce integrates with analog paging systems using the Paging Relay's various outputs. SA-Announce supports notifications per notification groups. Beacons Integrate with Alertus beacons to provide ADA compliance and a more comprehensive coverage model. Mass Notifications Integrate with Everbridge to allow Mass external notifications like SMS, Text-toSpeech, and . Twitter Integrate with your Twitter account and automatically update your Twitter feed when a notification group is activated.

13 Application Features 13 Notification Types - SA-Announce supports the following types of notification: Notification Type Description Live Audio Live audio notification groups including one-to-many one-way notification groups. Stored Audio Stored audio notifications include scheduled events, such as school bells and emergency alert notifications. Weather Alerts Integrate with the National Weather Service to deliver localized weather alerts for Watches, Warnings and Advisories. AMBER Alerts Integrate with AMBER Alerts to deliver localized missing child(ren) alerts. Text Messages Text messages can be sent to all endpoint types that support text. Other Features - SA-Announce supports the following features: Feature Description Syn-Apps Paging Relay A hardware solution that enables transmission of multicast from one site to another without requiring a multicast enabled WAN. It is also used to integrate external systems, such as analog paging systems. Cloud Services Send notifications to a variety of endpoints including: Apple ios and Android smartdevices, SMS, Instant Messaging using Jabber and Google Hangouts, Digital Media Signage, and more! Reporting Built-in reports gather and export detailed information regarding notification group configuration data and system user permissions. Syn-Apps Analytics Provides a holistic view of all notification activity including both on and off-premise services. Generates complete activity reports including: Group name, Activation date/time, Initiator, Associate Endpoints, etc. Dynamic Notification Dynamically associate IP phones, IP speakers and Desktop Clients to a Groups notification group using filters. Group Opening Tone Assign custom audio files to serve as the notification group opening tone. Emergency Alert notification groups Define groups for emergency notifications such as schools on lockdown or tornado warnings. Enhanced User Management Create user based access with granular permissions and global administration access. Configurable Streaming Model Multicast support to all digital audio endpoint types. Secure Notification Groups Any notification group can be secured with a DTMF security code. System Information Center View notification history, login history, scheduled history, text history, and all relevant system information. Troubleshooting Automatically create a trouble report and send relevant data to Syn-Apps Technical Support via FTP. Multicast Troubleshooting Enhanced multicast tests to determine if the network is properly configured. Active Directory Integration System users can be authenticated against an Active Directory.

14 Manual Conventions Part 3

15 Manual Conventions 3 15 Manual Conventions This manual describes installation, configuration, administration and use of the SA-Announce Notification System. Chapters of the manual that refer to the application web administration interface will have the main page and in some cases secondary tab identifier of the web page being referred to. For example the Notification Group Configuration section refers to the Groups tab under the Create / Edit Groups page. An example of a secondary tab is General. Groups >> Create / Edit Groups >> General is an example of the navigation used throughout this manual. Bold text is also used to designate a navigation path and denote direction. The Notification Group Configuration chapter of the manual describes each of the Create / Edit Groups tabs in detail. Other chapters, such as Creating Emergency Alert Groups do not necessarily repeat this information. First time installations should start with the System Requirements chapter and continue through the Notification Group Configuration section.

16 Information Center Part 4

17 Information Center 4 17 Information Center SA-Announce 7.x and above offers an information center that provides quick access to the items in the table below. All of this information can be accessed by clicking on the Syn-Apps icon located in the upper-left corner of the administration user interface: All data retained in the Information Center is stored for 90 days by default. To adjust the retention period, modify the activityretentiondays setting in Services >> Broadcast Services >> Advanced Settings. When done viewing the data, click on the Exit Menu button in the lower right corner or click on the main SAAnnounce web page to close the window.

18 18 SA-Announce User Guide The table below lists the Information Center menu options: Information Center Menu Item Description General General information about the product Changes Displays the SA-Announce change log. Refer to this section to learn about application enhancements and bug fix information. Info Displays the application registry settings. Use this section to quickly verify system settings. License Provides access to the currently installed license information including your maintenance contract number and start/end dates. Licenses can also be updated on this page using the interface at the bottom. Lists User and group configuration lists Groups Displays a detailed list of all notification groups configured within SAAnnounce. Information displayed includes Name, Type, Number, Partition, and Device Pool. Users Displays a list of all users that have been provisioned for access to the SA-Announce web interface. The values displayed are Username and if the user has been provisioned as a global administrator. Activity Recent system activity logs Login Act Displays a list of recent logins to the SA-Announce web interface. Username, Login time and the IP address of the machine that the user logged into the system from are displayed. Page Act Displays a historical view of the recent notification activity on the system. Text Act Displays a historical view of recent text messages that have been dispatched via SA-Announce. Sched Act Displays a historical view of all scheduled notifications.

19 System Requirements Part 5

20 20 5 SA-Announce User Guide System Requirements In order for SA-Announce to function properly, system requirements need to be met. Review this section before installing the product. The SA-Announce system requirements are organized into the following categories: SA-Announce System Requirement Description Application Server Requirements The hardware and software requirements for the server SA-Announce is to be installed on. Avaya Communication Manager Requirements The Avaya Aura Communication Manager and Avaya IP Office requirements. Network Requirements Network port usage and multicast setup information.

21 System Requirements Application Server Requirements The SA-Announce Notification System application server must meet the following requirements: Server Requirement Description Software Requirements Supported Versions Operating System Windows Windows Windows Windows 2003 (32-bit only) **Does not support Cloud Services 2008 SP2 (32-bit or 64-bit versions) 2008 R See the following for server operating system requirement setup specifics: Windows 2003 Server Windows 2008 Server Windows 2012 Server Microsoft.NET Microsoft.NET 3.5 *Automatically installed if the server has internet access (or download here) [Included with Windows 2008 R2] Microsoft SQL Server Microsoft SQL Server 2008 R2 SP1 or greater (required for redundancy subsystem, SQL Server 2005 is still supported for non-redundancy installs). *SQL Express 2008 R2 SP1 is automatically installed if the server has internet access (or download here: 64-bit or 32-bit) **If using your own Local SQL Server instance, then Mixed Mode Authentication (SQL and Windows) is required for the target SQL server instance. Note: MSDE / SQL 2000 is no longer supported. The SA-Announce installer and configuration programs will assist with DB upgrades for customers on MSDE. Hardware Requirements Server hardware minimum requirements listed below CPU Any dual core processor (minimum recommended) Memory 2 GB of system memory (minimum requirement) Hard Drive 10 GB of hard drive space (minimum requirement)

22 SA-Announce User Guide Windows 2003 Server Windows 2003 Server Requirements A number of Windows Components are required to be installed on Windows 2003 operating systems. The SA-Announce installer will attempt to enable all required options. If problems occur after installation then the installed components should be verified using the method below. Note that Syn-Apps' Cloud Services are not supported on Windows 2003 operating systems. To install the required components open Windows Components on the application server. Navigate to Start >> Control Panel >> Add Remove Programs. In the Add Remove Programs window, select the Windows Components button. When the Windows Components window appears, configure the following components as described: Windows Component Description Internet Explorer Enhanced Internet Explorer Enhanced Security Configuration must be unchecked. Security Configuration ASP.NET Under Application Server the ASP.NET check box must be checked. Internet Information Services Under Application Server >> Internet Information Services >> World Wide Web Service >> Active Server Pages and World Wide Web Service must be checked.

23 System Requirements Windows 2008 Server Windows 2008 Server Requirements The following tables describe the Windows 2008 server requirements for the SA-Announce Notification System. Windows 2008 R1 systems only: Windows 2008 R1 Req. Description Windows 2008 SP2 Make sure that Windows 2008 SP2 has been installed, required for automatic configuration. Microsoft.NET 3.5 If the application server does not have internet access make sure.net 3.5 has been installed (download here). \If the application server does have internet access then the SAAnnounce configuration utility will automatically download and install ASP.NET 3.5. The following are required for all Windows 2008 servers: Server Requirement Description Manual Setup Requirement These require manual setup. Disabling Public Firewall Firewall must be disabled or set to allow access on the required ports (see Firewall Ports). Auto-Setup Requirement The installer should automatically complete these. Disabling IE Enhanced Security Configuration IE Enhanced Security Configuration must be disabled to allow the website to function properly. Installing Internet Information Service IIS is required for the product to function. (IIS) Installing ASP.NET ASP.NET 3.5 is required for the product to function. Recommended These are recommended items. Disabling User Account Control (UAC) We recommend disabling UAC.

24 SA-Announce User Guide Disabling UAC Disabling User Account Control (UAC) To disable User Account Control on the SA-Announce application server (recommended) perform the following: Disabling User Account Control Description Launch Control Panel Lauch Start >> Control Panel on the application server. Launch User Accounts Under Control Panel, launch User Accounts. Turn User Account Control on or off Under User Accounts select Turn User Account Control on or off. Disable UAC Uncheck the Use User Account Control (UAC)... checkbox. Click OK Click OK to accept the changes. Reboot Windows will require a reboot. Reboot the system Disabling Public Firewall Disabling Public Firewall To disable Public Firewall on the SA-Announce application server (required) perform the following: Disabling Public Firewall Description Launch Server Manager Start >> Server Manager or right-click on Computer and select Manage. Select Windows Firewall In Server Manager expand the Configuration item and select Windows Firewall. Select Go to Windows Firewall. Select Windows Firewall Properties In Windows Firewall Configuration click the Windows Firewall Properties link at the bottom of the page. Switch Firewall Off In Windows Firewall Properties click the Public Profile Tab. Switch Firewall State to Off. Finalize Changes Click OK. Public Profile s Firewall should now be off.

25 System Requirements Disabling IE Enhanced Security Disabling IE Enhanced Security Configuration To disable IE Enhanced Security Configuration on the SA-Announce application server (required) perform the following: Disabling IE Enhanced Security Description Launch Server Manager Start >> Server Manager or right-click on Computer and select Manage. Select Configure IE ESC Select the Configure IE ESC option at the bottom right. Turn IE ESC Off Click Off for both Administrators and Users. Finalize Changes Click OK Verifying IIS Verifying Internet Information Service (IIS) The SA-Announce application installer will install and configure IIS automatically. If there are any issues during installation, this data can be used to verify the settings. To install the IIS Role and required Features on the SAAnnounce application server (required) perform the following: Installing the IIS Role Description Launch Server Manager Start >> Server Manager or right-click on Computer and select Manage. Go to Roles In Server Manager with Server Manager selected, select Go to Roles. Select Server Roles In the Add Roles Wizard select the Web Server (IIS) role and click Next. Add Required Features In the Add Roles Wizard click Add Required Features. The Add Roles Wizard will appear again, click Next to begin adding the required features. Adding Role Services The required Role Services for the IIS role. Select Role Services In the Add Roles Wizard, select All Role Services for the Web Server role. Alternatively, the Add Role Services Wizard will appear if the role was previously installed. Click Next when all items have been selected to complete the installation.

26 SA-Announce User Guide Installing ASP.NET Installing the ASP.NET feature on Windows 2008 The SA-Announce application installer will install and configure ASP.NET and features automatically. If there are any issues during installation, this data can be used to verify the settings. To install the ASP.NET feature manually on the SA-Announce application server, perform the directions in the table. Note that ASP.NET is required. Install ASP.NET Feature Description Launch Server Manager Start >> Server Manager or right-click on Computer and select Manage. Add Features In Server Manager with Server Manager selected, select Add Features. Select Features In the Add Features Wizard, select the.net Framework 3.X feature and all sub-features. Click Next. The features will be installed. On Windows 2008 R1, the feature is.net Framework 3.0 Features, on Windows 2008 R2 the feature is.net Framework Features. This completes the Windows 2008 Server requirements section.

27 System Requirements Windows 2012 Server Windows 2012 Server Requirements The following table describes Windows 2012 Server Requirements for the SA-Announce Notification System. Server Requirement Description Manual Setup Requirement These require manual setup. Disabling Public Firewall Firewall must be disabled or set to allow access on the required ports (see Firewall Ports). Auto-Setup Requirement The installer should automatically complete these. Disabling IE Enhanced Security Configuration IE Enhanced Security Configuration must be disabled to allow the website to function properly. Installing Internet Information Service (IIS) IIS is required for the product to function Installing ASP.NET ASP.NET 3.5 is required for the product to function. Recommended These are recommended items. Disabling User Account Control (UAC) Syn-Apps recommends disabling UAC.

28 SA-Announce User Guide AVAYA Requirements The following table describes the various Avaya Aura Communication Manager requirements: Avaya Aura CM Requirement Description Avaya CM Version Avaya Aura Communication Manager versions 5.x with media processor. Codec Support SA-Announce only supports the G.711 audio codec. Configure Avaya Aura Utility Server Configure Avaya Aura Utility Server. Connectivity Proper IP access to Communication Manager and IP phones. Avaya Push Push API enabled on Avaya phones that are to be included as endpoints. The following table describes the various Avaya IP Office requirements: Avaya IP Office Requirements Description Avaya IP Office Version Avaya IP Office versions 9.x with media processor. Codec Support SA-Announce only supports the G.711 audio codec. Connectivity Proper IP access to IP Office and IP phones. Avaya Push Push API enabled on Avaya phones that are to be included as endpoints. Advanced Settings SA-Announce requires changes to the default Advanced Settings to support Avaya IP Office. Avaya IP Phone Compatibility XML enabled Avaya IP phone models are supported as destinations and can receive commands from SAAnnounce. In most cases any phone can be used to dial into the system, though some notification groups require activation by an XML enabled phone. Note that some models do not support images as denoted below in the Img column. Avaya IP Phone Model XML Img Compatible with Avaya Aura & SA-Announce Compatible with Avaya IP Office & SA-Announce Avaya 9670G Avaya 9650/C Avaya 9641G Avaya 9640/G Avaya 9630G Avaya 9621G Avaya 9620L/C Avaya 9611G Avaya 9610 Avaya 9608 Avaya 9601

29 System Requirements Configure AVAYA Aura This section explains the configuration process for Avaya Aura Configure Avaya Aura Process Configure Avaya Aura Utility Server Configure Avaya Aura Communication Manager Configure Avaya Aura Session Manager Setup of Avaya 96xx Series Phones Avaya phone settings are controlled by a file that is downloaded and parsed each time the phone resets/reboots. In order to interact with the phones, SA-Announce needs to be "trusted" by the phones and the phones need to "subscribe" to SA-Announce. Furthermore, in order for a phone to receive and display content on the screen from a remote source, it needs to be setup for WML. Ensure the following values are set in the configuration file for your phones (typically 46xxsettings.txt or 96xxsettings.txt, depending on your implementation). Trusted Push Server List: (SET TPSLIST) This setting configures a phone to allow an external server to send commands to the phone. This setting can have more than one server listed on the same line with multiple servers separated by commas. NOTE: it is required to have a port after the server name/ip address if the Trusted Push Server's content is not being server on port 80. For example, if your server serves content on port 8081, you will need to add the server like this: SET TPSLIST servernameorip:8081 Recommended Setting: SET TPSLIST x.x.x.x < This should be the IP address of SA-Announce Subscription Server List: (SET SUBSCRIBELIST) This setting configures a phone to 'subscribe' to a 3rd party subscription service. SA-Announce requires this to be configured in order to present the list of available phones that can be added to a notification group. This setting can have multiple values separated by commas and each value should be a fully qualified URL to the subscription server as defined by the vendor. The feature of an Avaya phone to subscribe to a service only occurs once during its startup. In order to see Avaya phones in the SA-Announce database, the phone must be reset after setting the SUBSCRIBELIST value. Recommended Setting: SET SUBSCRIBELIST PhoneServices/AvayaPhoneRegistration.aspx WML Home Page: (SET WMLHOME) This setting configures a phone's WML home page. Setting this value allows the phone to present WML content (text and images) and internally 'turns on' the web browser applet in the phone. If this value is not set or is commented out the phone will not show any WML content, meaning it will not show alerts that are generated by SA-Announce. Recommended Setting: SET WMLHOME -- OR -SET WMLHOME

30 30 SA-Announce User Guide Push Capabilities: (SET PUSHCAP) Avaya IP phones allow for the individual enabling of specific features that relate to pushing content to the phones (for example, allowing the phone to show WML content or receive audio). It is recommended that all of the push capabilities be enabled on your phones in order to receive the full benefit of SA-Announce's features. Often this setting is done on a phone model basis in your settings file. Be sure to apply this setting for all of the phone types that will integrate with SA-Announce. PUSHCAP Settings Avaya Aura Communication Manager Description SET PUSHCAP Reboot Phones: After making changes to the settings file(s) for your endpoints, you need to reset/reboot all the phones in order for the settings to be pushed to the devices. Avaya endpoints only send subscription requests during startup and as such will not appear in the SAAnnounce database until such happens. If you feel that a device or devices are missing, please reboot the phone first and then refresh the appropriate page.

31 System Requirements Configure Avaya Aura Utility Server Avaya 9600 Series IP Endpoints settings are controlled by 46xxsettings.txt file that is downloaded and parsed each time a phone resets or reboots. In order to interact with the phones, SA-Announce needs to be "trusted" by the phones and the phones need to "subscribe" to SA-Announce. Furthermore, in order for a phone to receive and display content on the screen from a remote source, it needs to be setup for WML (Wireless Mark-up Language). In the Interoperability Lab, Avaya Aura Utility Server is used to manage Avaya 9600 Series IP Endpoints. All changes to 46xxsetting.txt are made via, Avaya Aura Utility Services System Management Interface (SMI). Utility Service SMI can be reached via a web browser, where IP-address is the IP Address of Avaya Aura Utility Services. On the logon page, log in using appropriate credentials. Once logged in, navigate to IP Phone Tools IP Phone Settings Editor.

32 32 SA-Announce User Guide On the IP Phone Settings Editor, Select Proceed with Selected Values. Enable the following options by selecting the check box in front of the options and setting their fields as follows: TPSLIST: Set it to the IP Address of SA-Announce SUBSCRIBELIST: Set it to the following URL o Note: IP-Address is the IP Address of SA-Announce WMLHOME: Configure with any URL as a home page PUSHCAP: Set it to Below is a screen capture of configuring TPSLIST, other options are not shown. Once finished, select Save New Setting File at the bottom of the page.

33 System Requirements 33 Verify the values of the options above on the Output Screen, and select Save 46xxsetting.txt file to this server. On the next page, select Continue. Reboot the Avaya 9600 Series IP Endpoints to update the settings.

34 SA-Announce User Guide Configure Avaya Aura Communication Manager Avaya Aura Communication manager allows for routing calls to a SIP trunk to SA-Announce via Avaya Aura Session Manager. In order for Avaya 9600 Series IP Endpoints to be able to dial a number to activate an SAAnnounce group, a SIP trunk must be created that communicates with Session Manager. Another SIP trunk will be created on Session Manager to communicate to SA-Announce. The following information allows for a SIP connection between the Communication Manager and Session Manager. Refer to the table below to re-direct readers to the following sections of the manual: Configuration settings for Avaya Aura Communication Manager Configure IP Network Region Administer IP Codec Set Administer IP Node Names Administer SIP Signaling Group Administer SIP Trunk Group Administer Route Pattern Administer Private Numbering Administer AAR Analysis Administer Stations

35 System Requirements Configure IP Netw ork Region Use the change ip-network-region n command to configure a network region, where n is an existing network region. Configure this network region as follows: Set Location to 1 Set Codec Set to 1 Set Intra-region IP-IP Direct Audio to yes Set Inter-region IP-IP Direct Audio to yes Enter and Authoritative Domain, e.g. Avaya.com Administer IP Codec Set Use the change ip-codec-set n command to configure IP codec set, where n is an existing codec set number. Configure this codec set as follows, on Page 1: Set Audio Codec 1 to G.711MU

36 36 SA-Announce User Guide Administer IP Node Names Use the change node-names ip command to add and entry for Session Manager. For compliance testing, sm and entry was added Administer SIP Signaling Group Use the add signaling-group n command to add a new signaling group, where n is an available signaling group number. Configure this signaling group as follows: Set Group Type to sip Set Near-end Node Name to procr Set Far-end Node Name to the configured Session Manager in the Administer IP Node Names section, i.e. sm Set Far-end Network region to the configured region in the Configure IP Network Region section, i. e. 1 Enter a Far-end Domain, e.g. Avaya.com

37 System Requirements Administer SIP Trunk Group Use the add trunk-group n command to add a trunk group, where n is an available trunk group number. Configure this trunk group as follows, on Page 1: Set Group Type to sip Enter a Group Name Enter a valid TAC, e.g. *010 Set Service Type to tie Enter Signaling Group value to the signaling group configured in the Administer SIP Signaling Group section, i.e. 10 Enter a desired number in Number of Member field On Page 3: Set Number Format to private.

38 38 SA-Announce User Guide Administer Route Pattern Use the change route-pattern n command to configure a route pattern, where n is an available route patterns. Configure this route pattern as follows: Type a name in Pattern Name field For line 1, set Grp No to the trunk group configured in the Administer SIP Trunk Group section, i.e. 10 For line 1, set FRL to Administer Private Numbering Use the change private-numbering 1 command to define the calling party number to send to Session Manager. Configure private numbering as follows: Add entries for trunk group configured in the Administer SIP Trunk Group section.

39 System Requirements Administer AAR Analysis Use the change AAR analysis n command to configure routing for extensions starting with n. For compliance testing, extensions starting with 26 were used to route calls to SA-Announce: Set Dialed String to starting digits of extensions that will be used, e.g. 26 Set Min and Max to 5 for 5 digit extensions Set Route Pattern to pattern configured in the Administer Route Pattern section, i.e. 10 Set Call Type to AAR Note: An entry to dial plan will need to be added for extension range used in this step Administer Stations Administration of Avaya Stations/Extensions in Communication Manager and Session Manager is not shown in this document. Product documentation for Avaya products may be found at [1] Administering Avaya Aura Communication Manager, Release 6.3, Document , Issue 7.0, December 2012 [2] Administering Avaya Aura Session Manager, Release 6.3, Document , July 2012

40 SA-Announce User Guide Configure Avaya Aura Session Manager This section of the manual is dedicated to configuring settings for your Avaya Aura Session Manager. To begin configuring the Avaya Aura Session Manager: Access the Session Manager Administration web interface by entering URL in a web browser, where <ip-address> is the IP address of System Manager. Log in using appropriate credentials.

41 System Requirements Refer to the table below to re-direct you to specific pages within this section: Configuration settings for Avaya Aura Session Manager Add Sip Domain Add Location Add SIP Entity - Communication Manager Add Adaptation Add SIP Entity - SA-Announce Add Entity Link - Communication Manager Add Entity Link - SA-Announce Add Time Ranges Add Routing Policy Add Dial Patterns 41

42 42 SA-Announce User Guide Add SIP Domain Navigate to Home Elements Routing Domains, click on New button (not shown) and configure as follows: In Name field type in a domain (authoritative domain used for configuration in the Configure IP Network Region section) i.e. Avaya.com Set Type to sip Click Commit to save changes.

43 System Requirements Add Location Navigate to Home follows: Elements Routing Location, click on New button (not shown) and configure as Under General: Type in a descriptive Name Under Location Pattern click on New (not shown): Type in an IP Address Pattern, e.g * Click Commit to save changes. Refer to the screen shot shown below.

44 44 SA-Announce User Guide Add SIP Entity - Communication Manager Add Communication Manager as a SIP Entity. Navigate to Home Elements Routing SIP Entities, click on New (no shown) and configure as follows: Type in a descriptive name in Name field Type in the IP address of FQDN of Communication Manager in FQDN or IP Address field. Set Type to CM Set Location to the location configured in the Add Location section. Click Commit to save changes Note: It is assumed that SIP Entity for Session Manager has been already configured.

45 System Requirements Add Adaptation Navigate to Home Elements Routing Adaptation, click New (not shown) and configure as follows: Type in a descriptive name in Adaptation Name field Type in DigitConversionAdapter in New Module Name field In the Module Parameter field type in the following: o iodstd=avaya.com odstd=ip-address fromto=true Note: ip-address is the IP Address of SA-Announce.

46 46 SA-Announce User Guide Add SIP Entity - SA-Announce Add SA-Announce as a SIP Entity. Navigate to Home Elements Routing SIP Entities, click on New (no shown) and configure as follows: Type in a descriptive name in Name field Type in the IP address of FQDN of SA-Announce in FQDN or IP Address field. Set Type to SIP Trunk Set Adaptation to the one configured in previous section Set Location to the location configured in the Add Location section. Click Commit to save changes.

47 System Requirements Add Entity Link - Communication Manager Navigate to Home Elements Routing Entity Links, click on New (not shown) and configure as follows: Type in a descriptive name in Name field Set SIP Entity 1 to the name of Session Manager SIP Entity Set SIP Entity 2 to Communication Manager SIP Entity configured in the Add SIP Entity Communication Manager section. Click Commit to save changes. 47

48 48 SA-Announce User Guide Add Entity Link - SA-Announce Navigate to Home Elements Routing Entity Links, click on New (not shown) and configure as follows: Type in a descriptive name in Name field Set SIP Entity 1 to the name of Session Manager SIP Entity Set Protocol to TCP Set SIP Entity 2 to Communication Manager SIP Entity configured in the Add SIP Entity - SAAnnounce section. Click Commit to save changes.

49 System Requirements Add Time Ranges Navigate to Home Elements Routing Time Ranges, click on New (now shown) and configure as follows: Type in a descriptive name in Name field Click Commit to save changes.

50 50 SA-Announce User Guide Add Routing Policy Navigate to Home Elements Routing Routing Policies, click on New (not shown) and configure as follows: Type in a descriptive name in Name field Under SIP Entity as Destination, click on Select (not shown): o Select SA-Announce SIP entity added in the Add SIP Entity - SA-Announce section. Under Time of Day, click on Add (not shown): o Select time range added in previous step. Click Commit to save changes.

51 System Requirements Add Dial Patterns Navigate to Home follows: Elements Routing Dial Patterns, click on New (not shown) and configure as Under General: Set Pattern to prefix of dialed number Set Min to minimum length of dialed number Set Max to maximum length of dialed number Under Originating Locations and Routing Policies: Click Add and select originating location and SA-Announce routing policy as configured in the Add Routing Policy section. Click Commit to save changes. 51

52 SA-Announce User Guide Configure AVAYA IP Office This section explains the configuration process for Avaya IP Office Platform. Avaya IP Office Configuration Process Prerequisite Steps Verify IP Office License Obtain LAN IP Address Configuration Process SIP Trunk Configuration Avaya 9600 and 96x1 Series IP Deskphone endpoint settings are controlled by 46xxsettings.txt file that is downloaded and parsed each time a phone resets or reboots. In order to interact with the phones, SA-Announce needs to be "trusted" by the phones and the phones need to "subscribe" to SA-Announce. Furthermore, in order for a phone to receive and display content on the screen from a remote source, it needs to be setup for WML (Wireless Mark-up Language). In the Interoperability Lab, AvayaTM IP Office Manager is used to manage endpoints running from Avaya IP Office. All changes to 46xxsetting.txt are made via, Avaya IP Office Manager. This chapter provides detail on how to configure Avaya IP Office for SA-Announce. It is broken down into three sections: Push Parameters, SIP Trunks, and SIP Endpoints.

53 System Requirements SIP Trunk Configuration for IP Office This section describes how to configure SIP Trunks for Avaya IP Office. Configure SIP Trunks Description Prerequisites Verify Valid License First, verify licenses by navigating to IP Office R9 Manager screen >> License >> SIP Trunk Channel. From the configuration tree in the left pane, select License. Verify that the SIP Trunk Channels license is Valid, and that the Instances value is sufficient for the desired maximum number of simultaneous faxes. Obtain LAN IP Address From the configuration tree in the left pane, select System to display the System screen for the IP Office 500 V2 in the right pane. Select the LAN1 tab >> LAN Settings sub-tab in the right pane. Note that IP Office can support SIP trunks on the LAN1 and/or LAN2 interfaces. Enable SIP Trunk Process Incoming Call Route

54 54 SA-Announce User Guide Add Incoming Call Route Navigate to IP Office Manager Application >> [Your IP Office Name] >> Incoming Call Route 1. Add a new Incoming Call Route by right-clicking Incoming Call Route >> New. 2. Change the Line Group ID to 17 (group line number previously created). 3. Click the OK button to save the new Incoming Call Route settings. Destinations 1. Click the Destinations tab. 2. Modify the default Destination entry by typing a. (period) to allow any incoming digits. 3. Click the OK button to save the Destination changes. Short Code Add New Short Code Navigate to IP Office Manager Application >> [Your IP Office Name] >> Short Code

55 System Requirements 55 Add a new Short Code by right-clicking Short Code >> New. Configure the following Short Code settings: 1. Code - Type 610N; 1. Feature - Select Dial from the dropdown list.. 2. Telephone Number - Type (period) in the text box. 3. Line Group ID - Type the Line Number (previously configured). In this example, Line Number was 17 in the text box. 4. Locale - Leave blank. 5. Click OK button to save the Short Code settings. Refresh Settings Source Numbers Navigate to IP Office Manager Application >> [Your IP Office Name] >> System >> USER >> NoUser >> Source Numbers 1. Click the Add button to add a new source number for NoUser. 2. Type SIP_OPTIONS_PERIOD= Click the OK button to save your changes.

56 56 SA-Announce User Guide Binding Refresh Time (Seconds) Navigate to IP Office Manager Application >> [Your IP Office Name] >> System >> LAN1 >> Network Topology 1. Change the Binding Refresh Time (Seconds) option to This is 1 hour (seconds). 2. Click the OK button to save changes. This completes the SIP Trunk Configuration for Avaya IP Office.

57 System Requirements Enable SIP Trunks Enable SIP Trunk Process VoIP Settings >> Enable SIP Trunk Navigate to IP Office Manager Application >> [Your IP Office Name] >> System >> LAN1 >> VoIP Verify the following checkboxes are enabled (checked): H323 Gatekeepker Enable Auto-create Extn SIP Trunks Enable SIP Registrar Enable Auto-create Extn/User UDP TCP Enable RTCP Monitoring on Port 5005

58 58 SA-Announce User Guide Administer SIP Line Administer SIP Line Add SIP Line Navigate to IP Office Manager Application >> [Your IP Office Name] >> Line. Add a new Line by right-clicking on Line >> New >> SIP Line Configure SIP Line By default, creating a new SIP Line in IP Office Manager will auto-generate the next available SIP Line number. Note: Line 17 will be created by default if Line 17 if this is the first time creating a new line. 1. Keep all default settings, except for Check OOS. 2. Disable (uncheck) the Check OOS checkbox. SA-Announce does not respond to SIP Options messages, so disabling this setting allows IP Office would not take down the SIP Trunk if a response to the SIP Options message is not received. the Avaya phones to not take down a SIP Trunk if Avaya does not receive a response from SA-Announce. (See the Help button for additional details on Check OOS setting). 3. Click OK to create the new SIP Line and continue.

59 System Requirements 59 Transport Settings Click on the Transport tab. 1. Enter in the SA-Announce IP Address in the ITSP Proxy Address textbox. Note that SIP transport protocol and Port are specified in this screen. 2. Keep all default settings. 3. Click OK to continue. SIP URI Click the SIP URI tab. 1. Click the Add button to display the New Channel section add a new SIP URI entry. 2. Set the Local URI to: * (asterisk) for a wildcard match. 3. Set the Contact to: Use Internal Data

60 60 SA-Announce User Guide Set Display Name to: Use Internal Data Set PAI to: <None> Set Registration to: 0: <None> Set the Incoming Group to: SIP Line number previously configured, (this example is 17). 8. Set the Outgoing Group to: SIP Line number previously configured, (this example is 17). 9. Set Max Calls Per Channel to: Desired number of calls to support. This example is Click the OK button to create the SIP URI. VoIP Click on the VoIP tab to select the Codec. 1. Select Custom from the Codec Selection dropdown list. 2. Select the applicable G.711 codec variant in the Selected list. Move all remaining codec's to the Unused list using the << arrows. 3. Enable (check) the Re-Invite Supported parameter checkbox. 4. Disable the Allow Direct Media Path checkbox. 5. Click the OK button to save the VoIP settings.

61 System Requirements 61

62 62 SA-Announce User Guide Administer Incoming Call Route Incoming Call Route Add Incoming Call Route Navigate to IP Office Manager Application >> [Your IP Office Name] >> Incoming Call Route 1. Add a new Incoming Call Route by right-clicking Incoming Call Route >> New. 2. Change the Line Group ID to the Incoming Group Number, which corresponds with the SIP Line created in the previous section, Administer SIP Line. This example is Click the OK button to save the new Incoming Call Route settings. Destinations 1. Click the Destinations tab. 2. Modify the default Destination entry by typing a. (period) to allow any incoming digits. 3. Click the OK button to save the Destination changes.

63 System Requirements 63

64 64 SA-Announce User Guide Administer Short Code Administer Short Code Add New Short Code Navigate to IP Office Manager Application >> [Your IP Office Name] >> Short Code 1. Add a new Short Code for calls to SA-Announce by right-clicking Short Code >> New. Configure the following Short Code settings: 1. Code - Type 610N; 2. Feature - Select Dial from the dropdown list. 3. Telephone Number - Type. (period) ("." allows the system to match any number). 4. Line Group ID - Type the outgoing group number which corresponds to the SIP Line previously configured in the Administer SIP Line section. In this example, Line Number was 17 in the text box. 5. Locale - Leave blank. 6. Click OK button to save the Short Code settings.

65 System Requirements Configure AVAYA 9600 and 96x1 Series IP Deskphones SA-Announce uses the Avaya Push Interface API to send audio, text, and graphic notifications to Avaya IP deskphones. To authorize SA-Announce as a Trusted Push Server, the Push Interface settings in the 46xxsettings.txt file must be configured properly. In turn, the Avaya IP desk phones must retrieve those settings during start-up. Configure PUSH Parameters Description Prerequisites Avaya IP Office Manager From the PC running the Avaya IP Office Manager application, navigate to Start >> Programs >> IP Office >> Manager. Launch Manager. Select the appropriate IP Office system and log in with the appropriate credentials. 46xxsettings.txt File Backup From IP Office Manager, navigate to File >> Advanced >> Embedded File Management >> System >> Primary >> 46xxsettings.txt file 1. Right-click on the file >> Download the file to the PC to create a backup copy. Open 46xxsettings.txt Open the 46xxsettings.txt file from IP Office Manager. Push Interface Settings Configure the following settings: TPSLIST Settings Set TPSLIST Set TPSLIST to: SET TPSLIST [SA-Announce IP address that corresponds to your network ]. This setting configures a phone to allow an external server to send commands to the phone. This setting can have more than one server listed on the same line with multiple servers separated by commas. *Tip - Click "Control + F" to search for "TPSLIST" quickly in the 46xxsettings.txt file.

66 66 SA-Announce User Guide SUBSCRIBELIST Settings Set SUBSCRIBELIST Set SUBSCRIBELIST to: SET SUBSCRIBELIST [SA-Announce URL that corresponds to your network ]. The feature of an Avaya phone to subscribe to a service only occurs once during its startup. In order to see Avaya phones in the SA-Announce database, the phones must be reset after setting the SUBSCRIBELIST value.

67 System Requirements 67 PUSHCAP Settings Set PUSHCAP 222 Set PUSHCAP to: SET PUSHCAP 222 Avaya IP phones allow for the individual enabling of specific features that relate to pushing content to the phones. For example, allowing the phone to show WML content or receive audio. WMLHOME Settings SET WMLHOME IMPORTANT: The WMLHOME parameter may be configured on a per phone type basis in the 46xxsettings.txt file. Mak e sure that the

68 68 SA-Announce User Guide WMLHOME parameter is set under each phone type in the 46xxsettings.txt file or set the parameter in a section of the file where it would apply to all phone types, (as shown below). In other words, if the WMLHOME parameter is only set for 9650 phone type, the parameter would not be set for all other phone types, therfore text and graphic notifications would not be pushed to those phones. 1. Set the PUSH INTERFACE SETTINGS >> WMLHOME to: SET WMLHOME This example is set to: SET WMLHOME Avaya.com/elmodocs2/Avayaip/9600/home.wml 2. Set every registered phone WMLHOME setting to: SET WMLHOME

69 System Requirements 69 Final Steps Save Upload 46xxsettings.txt Save the modified 46xxsettings.txt file after changes have been made. 1. Open Avaya IP Office Manager application. 2. Upload the modified 4600settings.txt file in IP Office Manager so it is available to read from the memory card. Upload the modified 46xxsettings.txt file into Avaya IP Office Manager >> File>> Advanced >> Embedded File Management >> System SD >> System >> Primary >> File >> Upload File >> 46xxsettings.txt file. 3. Click Save to save the uploaded 46xxsettings.txt file into the IP Office Manager application. 4. Set the HTTP server on the Avaya IP deskphones to the IP Address of IP Office. 5. After making these changes, click File >> Save Configuration from the Manager application for changes to take effect in IP Office.

70 70 SA-Announce User Guide The 46xxsettings.txt file is show n here, after it w as uploaded into the System >> Prim ary folder. Reboot Avaya Phones After making changes to the settings file(s) for the Avaya endpoints, reboot all of the phones in order for the settings to be pushed to the devices. Avaya endpoints only send subscription requests during startup and as such will not appear in the SA-Announce database until such happens. Note: After the phone reboots, the Avaya phone display will show an HTTP request for the upgrade script on the phone's screen.right after the line where it gets the upgrade script, the next line you'll see will show HTTP Verify Phones Get Upgrade Script Verify the 96xx series phones get the upgrade script from the 46xxsettings. txt file. Navigate to Computer >> Program Files >> Avaya >> IP Office >> Manager >> 96xxupgrade.txt and 96x1Hupgrade.txt. Open the 96xxupgrade and 96x1Hupgrade files to verify they read the 46xxsettings.txt file.

71 System Requirements 71 Open each Avaya phone file and scroll to the bottom to verify the phone(s) read: GET 46xxsettings.txt Screenshot show s the 96xxupgrade successfully gets the upgrade script from the 46xxsettings.txt file from the PUSH interface. The PUSH parameters have been configured. Continue to the following section SA-Announce >> Initial Application Configuration for IP Office To complete the remaining SA-Announce configuration for IP Office, navigate to the Avaya IP Office Advanced Settings section.

72 SA-Announce User Guide Network Requirements SA-Announce supports multicast paging with Avaya Firewall Ports SA-Announce requires proper connectivity to and from the Communication Manager and endpoint devices in order to deliver notifications. Consult the below table to determine which ports need to be opened to allow proper operation. Firewall requirements/port usage: Port Description SA-Announce to Communication Manager Protocol description 5060 SIP TCP 80, 443, 8443 HTTP/SOAP/AXL TCP Real-Time Protocol (RTP) UDP SA-Announce Server to IP Phones 80 TCP - HTTP Real-Time Protocol (RTP) UDP Multicast Real-Time Protocol (RTP) UDP IP Phones to SA-Announce Server 80 TCP - HTTP Real-Time Protocol (RTP) UDP Multicast Real-Time Protocol (RTP) UDP SA-Announce Server to IP Speakers 80 TCP - HTTP 6789 UDP - SynApps IP device protocol UDP - RTP - unicast and multicast Refer to the Avaya Communication Manager port usage guide and treat Syn-Apps SA-Announce just like a standard IP phone.

73 System Requirements Multicast Requirements Multicast must be enabled on the network. All interfaces between the SA-Announce server and the destination endpoints need to have IP PIM enabled. The switches should have IGMP/CGMP enabled. If the WAN cannot be multicast enabled, or enabling multicast would require a large or recurring investment, then the Syn-Apps Paging Relay should be deployed at the remote site. This allows SA-Announce to send a single unicast stream over the WAN connection. The Paging Relay converts the stream into a multicast stream at the remote site. See SA-Announce Overview or contact Syn-Apps Sales for more information. Refer to the network support or the telephony network partner for the best approach for implementing multicast on the network.

74 Installation Procedure Part 6

75 Installation Procedure 6 75 Installation Procedure If the application server that SA-Announce will be installed on does not have internet access then please make sure the required components ASP.NET 3.5 and SQL Express 2008 R2 SP1 have been installed. See the Application Server Requirements section for the download URLs. Users must be logged onto the application server as an administrator, (local or domain), to properly complete the installation. Installation Procedure Description Start the Installer Start the SA-Announce setup program. The SAAnnounce setup program Welcome screen should appear. Click Next to proceed. Download SA-Announce here - a license is required. Contact Syn-Apps Sales to request one. Accept License Agreement The License Agreement page should appear. Read and accept the license terms by selecting the I accept the agreement radio button. Click Next to proceed. Requirement Information Review and verify the server requirements. The server requires internet access during installation. Click Next to proceed. The system requirements will now be validated. Missing components will be downloaded and installed if necessary. This could take some time depending on the system. Ready to Install Click Install to start the product installation. Install Complete The installation is now complete. Make sure the Launch SA-Announce Configuration checkbox is checked. Click Finish to begin the SA-Announce Configuration program. Screenshot

76 SA-Announce User Guide Update Procedure T h i s s e c t i o n e x p l a i n s u p d a t i n g S A A n n o u n c e t o a n e w e r r e l e a s e

77 Installation Procedure 77 v e r s i o n. Users must be logged onto the application server as an administrator, (local or domain), to properly complete the installation.direct internet access is required for downloading the OS updates and the new SQL 2008 R2 SP1 (SYNAPPSENT) instance. Update Procedure Prerequisites Description 1. Check the OS KBs (Knowledge Base articles) to make sure the OS meets minimum specs for the upgrade or visit the System Requirements section. 2. Verify the server SA-Announce is running on has direct internet access. 3. Mixed Mode Authentication (SQL and Windows) is required for the target SQL server instance. 4. Verify Syn-Apps Core Components is NOT installed. Visit the Upgrade Procedure Troubleshooting section for additional details. 5. Recommended: Backup SA-Announce prior to moving forward. Visit the Backup and Restore KB for additional information. Open Add/Remove Programs Navigate to Start >> Control Panel >> Add/Remove Programs. Run the Upgrade Utility 1. The SA-Announce Update Utility is recommended. Launch the SAAnnounce Upgrade Utility by navigating to Start >> search for SAAnnounce Upgrade Utility. Continue through the upgrade screens. OR Download the Universal Installer Searching for the SA-Announce Update utility using Window s Alternatively, download the SA-Announce Universal Installer from

78 78 SA-Announce User Guide Dow nload the SA-Announce Universal Installer. Start the Installer Start the SA-Announce setup program and go through the installation process, as directed in the Installation Procedure section. Once the installation is complete, SA-Announce will continue to the SA-Announce Configuration. Note: Windows Installer 4.5 Powershell 2.0 and.net may be installed by the SA-Announce upgrade, if it's not already installed. An automatic OS reboot will occur for Windows Installer 4.5, but should not for 3.5 and.net. Verify SQL ENT Instance Installed Prior to running the SA-Announce configuration, verify the SQL Instance. To verify the SQL Installation: 1. Launch Start >> Run >> services.msc. 2. Scroll down to find the SQL Server (SYNAPPSENT) service If SQL Server 2008 R2 SP1 SYNAPPSENT instance is installed by SAAnnounce, then continue with the SA-Announce Configuration. If the SYNAPPSENT instance is not installed, then the existing SQL will have to be reconfigured. See the the Reconfigure SQL Server section for details on how to reconfigure SQL.

79 Configuration Utility Part 7

80 80 7 SA-Announce User Guide Configuration Utility The following section describes the configuration utility for the SA-Announce Notification System. The SAAnnounce Configuration Utility will automatically run at the end of installation. Configuration can be run on the application server at anytime by navigating to: Start >> Programs >> Syn-Apps >> SA-Announce >> Configuration. Config Step Description License Selection In order to use the SA-Announce software, a valid license key must be obtained. Contact Syn-Apps Sales to obtain a license. Screenshot The Syn-Apps.License must exist in the program base directory in C:\ProgramFiles\Syn-Apps\SA-Announce in order to be recognized by the application. Verify the license file has the exact file name of Syn-Apps.License. Click Next to proceed. Database Instance If SQL Express was installed during this installation, leave the default instance name as SynAppsEnt. If an existing local SQL server instance is to be used select the instance name. The Database Instance page allows users to select a different Instance Name, if applicable. Select the new Instance Name from the Instance drop-down list. Press the Upgrade DB to Selected Instance button if available. SQL 2000 is no longer supported. Installations using SQL 2000 will be required to upgrade. Only local databases are supported. Remote databases can be used by changing the registry key HKLM >> Software >> Syn-Apps >> SAAnnounce >> sqlservername to the name or the IP address of the off-box SQL server. SQL trusted authentication is required to use this model. The administrator credentials of the application server and database server must match. Click Next to proceed. Cloud Services Integration To enable Cloud Services, click the Enable Subscriptions checkbox. Enter the Customer ID and Authorization values. After clicking on Configure, the background processing begins. **SA-Announce Cloud Services are not supported on Windows 2003.

81 Configuration Utility Application Admin Credentials 81 Setup the SA-Announce application administrator user account credentials. This will be the system admin user for the SAAnnounce notification system. Click Configure to configure the product. The credentials are required to login to the application. Configuration When the application is configured, users will see a Success window. Click OK to proceed. Complete License Activation If the license has not been activated the Activation Wizard will appear. Select Online if the SA-Announce server has access to the Internet. Click Next to activate the license. Activation Successful will appear. Click OK. Select By if the SA-Announce server does not have access to the Internet. Click Next. Further instructions will be provided in this case. When the Configuration Wizard has completed the installation, a shortcut will be placed on the desktop labeled SA-Announce. Use it to access the SA-Announce web administration program. Users can also access the SAAnnounce administration web pages from any machine on the network, browse to SA-Announce. The SA-Announce web page should be displayed automatically when the configuration program completes. Proceed to the Post Configuration Steps when configuration completes.

82 Post Configuration Steps Part 8

83 Post Configuration Steps 8 83 Post Configuration Steps Help >> Post Install Instructions Double click on the SA-Announce shortcut on the desktop. The Help >> Post Install Instructions page should appear the first time the program is run. Use the same navigation path to access at any time. First time users should see the Avaya Requirements section of the manual for detailed Avaya system setup instructions. Review the post-installation instructions after installation to setup the Avaya Aura or IP Office Communication Manager and endpoints.

84 SA-Announce User Guide Avaya Endpoint Configuration Help >> Post Install Instructions >> Avaya Endpoint Configuration The Avaya Endpoint Configuration tab provides quick information on how to configure Avaya IP Office and Avaya Aura systems with SA-Announce. Refer to the Avaya Requirements section for detailed information. 8.2 SIP Trunk Setup Help >> Post Install Instructions >> SIP Trunk Setup The SIP Trunk Setup tab provides quick information on how to configure SIP Trunks speaker endpoints with SAAnnounce.

85 Post Configuration Steps 85

86 SA-Announce User Guide IP Speaker Setup Help >> Post Install Instructions >> IP Speaker Setup The IP Speaker Configuration tab provides quick information on how to configure IP speaker endpoints with SA-Announce. 8.4 Group Creation Help >> Post Install Instructions >> Group Creation The Group Creation tab provides quick information on how to configure notification groups within SA-Announce after all phones and endpoints have been configured.

87 Post Configuration Steps 87

88 Initial Application Configuration Part 9

89 Initial Application Configuration 9 89 Initial Application Configuration This section describes the basic settings in the SA-Announce notification system that should be understood for all installations. 9.1 First Time Login After starting the application, users will be prompted to enter the User name and Password. Use the User name and Password created during configuration on the Application Admin Credentials screen. Refer to the Configuration Utility >> Application Admin Credentials section in the table. Press the Login button to continue.

90 SA-Announce User Guide Broadcast Service Settings Services >> Broadcast Services >> Settings The Settings tab allows adjustment of the general system settings and contains the following service parameters: Setting Name Default Description Blank Enter the IP Addresses of servers authorized to access the SA-Announce API (comma delimited list). Enable the Allow all servers checkbox to allow all servers access. Allow All Servers Unchecked Enable the Allow all servers checkbox to allow all servers access. Multicast Only Unchecked Multicast is the only broadcast method supported for Avaya. Servers authorized to use the SA-Announce API Settings tab (shown with defaults): Click the Save button to save changes.

91 Initial Application Configuration Avaya Aura Advanced Settings Services >> Broadcast Services >> Advanced Settings The Advanced Settings tab contains an editable view of the system settings that are not changeable elsewhere in the SA-Announce user interface. These settings should not be altered except when directed by the SAAnnounce manual or Syn-Apps Technical Support. To change a setting, click the drop-down list from the Select a Setting field. The description and default value for the setting will be shown. Alter the Setting Value and then press Save. Some changes require further action be taken in order for the setting change to take affect. Changes requiring further action will be noted in the Setting Description.

92 SA-Announce User Guide Avaya IP Office Advanced Settings Avaya IP Office Advanced Settings Note that Avaya IP Office systems require a few changes to SA-Announce Advanced Settings to allow the SIP processing to function correctly. Navigate to Services >> Broadcast Services >> Advanced Settings. Use the Select a Setting drop-down list and modify the following values to False: Setting Name Default Setting Required Description Setting After selecting this field, change the Setting Value textbox by typing False. Alter the Setting Value and then press Save. sipstartmediaonanswer True False After selecting this field, change the Setting Value textbox by typing False. Alter the Setting Value and then press Save. sipstartmediaonsecondans wer True False

93 Initial Application Configuration Setting Name Default Setting 93 Required Description Setting After selecting this field, change the Setting Value textbox by typing udp, (case-sensitive). Alter the Setting Value and then press Save. siptransporttype tcp udp Make sure to change these settings individually and clicking the Save button after changing each of these settings.

94 SA-Announce User Guide Verification Steps This section provides actions that can be taken to verify proper configuration between Avaya IP Office and SynApps' SA-Announce. SA-Announce Broadcast Services Verify Broadcast Services and Scheduler Services are running in SA-Announce: 1. Navigate to SA-Announce UI >> Services >> Broadcast Services >> Services 2. Verify Broadcaster Service and Scheduler Services are running. See Avaya IP Office Advanced Settings for additional details. IP Office System Status Launch Avaya IP Office System Status. Login using appropriate credentials. The IP Office System Status screen is displayed Expand Trunks (from the left-pane) >> Select the SIP Line configured from Administer SIP Line section. Verify the SIP trunks are in the Idle state.

95 Initial Application Configuration Phone Features Settings >> IP Endpoint Setup >> XML Phones Use the XML Phones tab to identify the phones that will participate in XML control and communications. Once new items have been added to the selected side, click Apply Changes.

96 96 SA-Announce User Guide Settings >> IP Endpoint Setup >> Multicast Phones Use the Multicast Phones tab to identify the phone models that will be allowed to participate in multicast phone features. Once new items have been added to the selected side, click Apply Changes.

97 Initial Application Configuration Multicast Configuration Settings >> Multicast >> Defaults The Multicast Settings page is used to enter the Multicast IP address. By default, multicast notifications are enabled in SA-Announce for Avaya. Verify the Multicast Enabled checkbox is checked and a Multicast IP Address exists. Click Save Defaults to save changes. The Multicast Settings page consists of two main sections, multicast settings and multicast tests. Multicast Settings Description Multicast Settings Multicast Settings are used to enable multicast notifications. Defaults The default multicast addresses provided automatically should work for most implementations. The Multicast Test table (shown below) describes each section in detail: Multicast Settings Description Multicast Tests The primary purpose of these tools is to determine whether multicast is functioning properly on the network. Syn-Apps suggests testing phones from each IP subnet. This ensures that multicast routing is functioning on all subnets. Server to Phone Multicast Test Use the Server to Phone Multicast Test tab to perform a server to phone multicast test. This test will verify the server's ability to source multicast to a phone. Test with a

98 98 SA-Announce User Guide phone on a different switch than the server. Select a phone from the Test phone drop down menu. Use the Filter button to select a specific phone from the list. Click the Start Transmission button to begin a multicast transmit and receive test. Verify that a series of ascending tones can be heard from the test phone. If a series of ascending tones is heard, then multicast is functioning properly between the server and the phone. There is a "beep" tone played before the ascending tones. Do not confuse the "beep" tone with the ascending series of tones. To stop testing, press the Stop Transmission button. Server to Speaker Use the Server to Speaker Multicast Test tab to perform a server to speaker Multicast Test multicast test. This test will verify the server's ability to source multicast to a speaker. Choose a speaker on a different switch than the server. Select a speaker from the Test speaker drop down menu. Use the Filter button to select a specific speaker from the list. Click the Start Transmission button to begin a multicast transmit and receive test. Verify that a series of ascending tones can be heard from the test speaker. If you hear a series of ascending tones, then multicast is functioning properly between the server and the speaker. There is a "beep" tone played before the ascending tones. Do not confuse the "beep" tone with the ascending series of tones. To stop testing, press the Stop Transmission button.

99 Initial Application Configuration 99

100 SA-Announce User Guide User Management Settings >> User Management The User Management page allows administrators to create new users in the SA-Announce notification system and assign them various permissions. To access the User Management page, navigate to Settings >> User Management in the SA-Announce web administration interface. The following table describes the process of creating users and assigning them permissions: User Management Description Create or Edit a User Create a new user or select a user to edit. Select User Select an existing user using the Select User drop-down menu or add a new user using the New User button. User Name Enter or edit the users User Name. New users must be given a unique User Name. Password Enter or edit the users password in the Password field and again in the Re-Type Password field. Administrator Select the Administrator checkbox if the user is to be an administrator of the system. Save User Press Save to save the new user or user changes. Delete a User Select a User Select the user to delete in the Select User drop down menu.

101 Initial Application Configuration 101 Delete User Press Delete to delete the user from SA-Announce. Add Permission to User Add permissions to non-administrative users (required). *Administrator users do not require additional permissions. Select a User Select an existing user in the Select User drop down menu. Add Permission Press Add Permission to create a new permission for the user. Select Group Select the group name of the group to give the user permission to in the Group Name drop down menu. Select Permissions Select Send Text to grant the user rights to send text messages to the selected group. Select Modify Group to grant the user rights to modify the selected group in the SA-Announce web administration interface. Insert Permission Press the Insert link in the Edit Command column of the permissions table to save the new permission. Edit a Users Permissions Select a User Select an existing user in the Select User drop down menu. Select Permission to Edit In the User Permissions table press the Edit link in the Edit Command column of the row to be edited. Edit Permission Make the required changes to the permission. Update Permission Press the Update link to update the permission. Delete a User Permission Select a User Select an existing user in the Select User drop down menu. Delete Permission Press the Delete link to delete the permission.

102 102 SA-Announce User Guide Active Directory Integration Settings >> User Management >> Active Directory Integration The Active Directory Integration tab can be used to set the user integration mode. Select the Active Directory Integration Mode radio button to enable Active Directory (AD). In the Active Directory Integration mode, all users are authenticated against the configured AD source, excluding the root admin user created during configuration. The Service Account credential fields should not be required unless the SA-Announce application server is not a member of the domain. When changing modes, all existing users and permissions will be deleted from the local data store. A confirmation dialog will appear when changing modes.

103 Notification Group Configuration Part 10

104 SA-Announce User Guide Notification Group Configuration This section describes the types of notification groups that users interact with and how to configure them. Refer to the Notification Group Types section of this manual for details on notification group types. Refer to the Notification Group Setup section of this manual for details on notification group configuration. The diagram below shows possible sources and destinations for SA-Announce notifications. Not all source and destination combinations apply to all notification group types. For more information, visit the Group Compatibility Matrix in the Notification Group Types section. Notification group sources and destinations: It is up to the customer to properly implement both a SIP trunk and proper dial routing in order for Avaya phones to activate a group.

105 Notification Group Configuration SA-Announce Notification Group Types Groups >> Create / Edit Groups The SA-Announce notification system includes a number of notification group types which serve their own purpose. The notification group types are described in the following tables and arranged by notification category: Group Type Description Normal One-to-many, one way, live audio. Normal A predefined group of end-points that plays the callers' live audio. Record-N-Play A predefined group of end-points that plays the callers recorded audio in order to eliminate feedback. Emergency Alert Stored or live audio and text. Emergency Alert A predefined group of end-points that plays stored or live audio and displays text while the emergency alert event is active. The event is activated by calling the notification group line number, enabling the API, pushing panic buttons, or clicking the Test button in the SA-Announce user interface. Text Send text and images. Text A predefined group of end-points that delivers a text messages, audio notifications and images when activated. Scheduled Scheduled stored audio and text event. Schedule A stored audio event that is scheduled to occur on certain days and times. At the scheduled time, the groups associated end-points will play a predefined audio tone. Text and images will also be displayed on supported endpoints. Group Compatibility Matrix The group compatibility matrix lists the compatible end-point types per group. Group Type Em ail IP Desktop IP Paging Legacy IP Beacons Mass Phones Clients Speakers Relays Speakers Notification Normal Emergency Alert Record-N-Play Text NA

106 106 SA-Announce User Guide Emergency Alert An Emergency Alert notification group is a predefined group of end-points that play stored or live audio and display text while the emergency alert event is active. The Emergency Alert group is designed to override active calls, which is a feature that cannot be changed. People on active calls will hear the emergency notification. This group type is ideal for schools on lockdown, tornado warnings, fires or other emergency scenarios.

107 Notification Group Configuration 107 The Emergency Alert group provides the ability to send notifications using different settings such as Alert, Voice, and Timed Mode. The event is activated by calling the notification group line number, enabling the API, pushing panic buttons, or clicking the Test button in the SA-Announce user interface. The event is deactivated in different ways depending on the mode selected during configuration: Emergency Alert Settings Description Alert Mode The first call activates the emergency alert. A second call cancels the emergency alert. Voice Mode The first call activates the emergency alert. A stored audio opening tone is played and then the caller speaks live audio. When the caller hangs up the event is canceled. Play Once The first call activates the emergency alert. The alert is canceled after playing once. Timed Mode The first call activates the emergency alert. It will continue until the configured number of times set in the Timed Mode field has occurred. Emergency Alert notification groups have a number of optional features: Feature Description Send Caller-Id Send the caller-id to the destination endpoints that supports texts or images. Emergency Notify destination end-points regardless of that end-points busy state. Security Code Require the caller to enter a DTMF security code before the notification is allowed to proceed. Twitter Automatically update the Twitter feed when the alert activates. Alert Services External alert services that integrate with Emergency Alert. Weather Alerts Group member end-points can receive National Weather Service weather alerts. See Weather Alert Settings for details. See Creating Emergency Alert Groups for complete details on creating emergency alert notification groups.

108 108 SA-Announce User Guide Normal A Normal notification group is a one-to-many one-way notification group that delivers a callers live audio to predefined end-points. The notification group is activated by dialing the group phone directory number. The notification will terminate when the caller hangs up the phone. Normal notification groups have a number of optional features: Feature Description Send Caller-Id Send the caller-id to the destination end-points that support text or images. Emergency Notify destination endpoints regardless of that end-points busy state. Security Code Require the caller to enter a DTMF security code before the notification is allowed to proceed. Group Opening Tone Send a predefined audio notification tone to destination end-points as the group opens. See the Notification Group Setup section for more details.

109 Notification Group Configuration RecordNPlay The Record-N-Play notification group allows users to predefine a group of end-points the will receive a recorded broadcast. A user calls the group and is prompted to record their message and then hangs up the call. The system will then broadcast the message after the caller has terminated the call. This notification group type is useful in areas that have a lot of background noise or the chance of audio feedback with a live page. Record-N-Play can be configured three ways: Alert Modes Description - See the Notification Group Setup section for more details. Standard The traditional legacy mode which plays the recording once. After it is finished playing, the notification ends. Alert Mode Enable this checkbox to configure the alert to repeat back-to-back until the group is called back to finish the alert. Repeat Recording Changes the number of times the notification is repeated before ending. Record-N-Play has a number of additional features: Feature Description - See the Notification Group Setup section for more details. Send Caller-Id Send the caller-id to the destination end-points that support text or images. Emergency Notify destination end-points regardless of that end-points busy state. Security Code Require the caller to enter a DTMF security code before the notification is allowed to proceed. Group Opening Tone Send a predefined audio notification tone to destination end-points as the group opens. Additional Option

110 110 SA-Announce User Guide DTMF Options Record-N-Play callers can use DTMF* to reset their message at any time. The recording during a Record- can be ended by pressing DTMF # or by hanging up. N-Play Call

111 Notification Group Configuration Text The Text notification group type allows users to send a text message to a predefined group of end-points. To create a Text notification group, navigate to Groups >> Create / Edit Groups >> New Group button at the bottom of the page. Enter a name in the Enter a Group Name field, then click the Group Type drop-down and select Text. To use the Text notification group, navigate to Groups >> Send Text. See the Sending A Text Message section for complete details.

112 SA-Announce User Guide Notification Group Setup Groups >> Create / Edit >> General The standard notification group setup process is described in the following sections. The following sections describe the remaining tabs on the page. These tabs represent the available endpoints which can be associated with a notification group. To create a new group select Groups >> Create / Edit >> General

113 Notification Group Configuration 113 Click New Group near the bottom of the page then configure the following settings on the General tab: Notification Group Setting Description Group Name Enter a descriptive name for the group. Group Type Select a group type. A Normal notification group type is recommended. See the SA-Announce: Group Types section for details on additional group types. Server Group Use with the Redundancy feature. Select the server group where this notification should reside. Select <None> to run the group on the publisher. This field will only be editable if the redundancy subsystem has been configured, see Server Redundancy for details. Group Phone Settings Line Number Dial the extension to activate the notification group. SA-Announce will suggest the next available line number however users must ensure that their call manager is configured to route this line number to SA-Announce. An alternative method would be entering a unique number to generate a specific line number. Misc Settings Use Security Code When checked, an additional field is presented. Enter a DTMF security code to secure the group. Initiators are required to enter the DTMF security code before the notification can continue. Send Caller-ID IP phone screens within the selected group will receive the initiators' caller ID. Emergency Enable to send text and audio stream to busy phones. Group Opening Tone Group Opening Tone Send a predefined audio notification tone to destination end-points. Select an opening tone to be played. For live audio group types, the caller confirmation tone will be played once the opening tone completes. Click Add Group. The group can be saved although end-points have not been associated. Endpoints will be associated after saving the group.click the Save Group button to save changes. To edit an existing Group Name, click on the Group Name dropdown list arrow and select a group to edit: Once the group is selected, the cursor will begin blinking. Start typing to replace or add onto the existing group name. A message displaying Rename Mode: press enter with the cursor on name to rename will appear, indicating the name has been modified. When finished editing the name, place the mouse cursor back on the text box and press the Enter key on the keyboard to finalize the changes. A message will appear at the bottom of the U, indicating the name has been successfully saved: Group Name has been Updated!

114 SA-Announce User Guide Groups >> Create / Edit >> The tab on the Create / Edit Groups page allows to be sent when a group is activated. To use this feature, first setup the parameters at Services >> Broadcast Services >> Settings. See the Settings chapter of this manual for more information. Add one or many addresses to the group using the Address (Activation) field. When available, use aliases. Mass messaging, 50 or more messages sent to the same provider, must be done using a third-party marketing service such as 3n (National Notification Network). Otherwise, sending too many messages to a specific provider might result in all messages being treated as spam.

115 Notification Group Configuration IP Phones Groups >> Create / Edit >> IP Phones Add phones to a notification group by selecting the IP Phones tab. Use the Arrange List By drop down menu to sort the list on the selected criteria. Select phones from the Available list by clicking to highlight. Then use the double-right arrow button >> to move the highlighted phones to the Selected list. Use the double-left arrows << to remove selected phones and put back into the Available list. Standard Windows Ctrl-click and Shift-click can be used to select items. Additionally, use the Filter column to run a search to filter the list of endpoints.

116 116 SA-Announce User Guide Enable Dynamic Groups The Dynamic Group checkbox will populate the Selected field with phones that match the specified Filter. Management of group members is not necessary when the Dynamic Group checkbox is in use because the Filter will manage group members automatically. For example, enable the Dynamic Group checkbox. Add sorting criteria to the Filter field. Click the Filter button to display results. Only phones meeting the filter criteria should be displayed. Dynamic Group now has a new filter option, Custom Filter in the Arrange List By menu. This selection will only appear when Dynamic Group is enabled. Custom Filter allows any valid SQL filter to be applied to the group. In this case, multiple filters can be logically combined to pull any combination of devices. When the Custom Filter option is selected, a message will appear that describes the column names used in the filter.

117 Notification Group Configuration Desktop Clients Groups >> Create / Edit >> Desktop Clients Add a Desktop Notification client to a notification group by selecting the Desktop Clients tab. Select desktop clients from the Available list by clicking to highlight. Then use the double-right arrow button >> to move the highlighted desktop clients to the Selected list. Standard Windows Ctrl-click and Shift-click can be used to select items. Additionally, use the Filter column to filter the list. To change desktop client settings and see current registration status, visit the Desktop Notification Client Configuration section. Desktop Notification Clients that have registered with SA-Announce will be shown in the Available field. Use the Arrange List By drop down menu to sort the list. The Dynamic Group checkbox will populate the Selected field with desktop clients that match the specified Filter. Management of group members is not necessary when the Dynamic Group checkbox is in use because the Filter will manage group members automatically. For example, enable the Dynamic Group checkbox. Add sorting criteria to the Filter field. Click the Filter button to display results. Only desktop clients meeting the filter criteria should be displayed.

118 118 SA-Announce User Guide Dynamic Group now has a new filter option - Custom Filter in the Arrange List By menu. This selection will only appear when Dynamic Group is enabled. Custom Filter allows any valid SQL filter to be applied to the group. In this case, multiple filters can be logically combined to pull any combination of devices. When the Custom Filter option is selected, a message will appear that describes the column names used in the filter.

119 Notification Group Configuration Cloud Services Groups >> Create / Edit >> Cloud Services The Cloud Services tab is only available on SA-Announce systems where Cloud Services have been enabled through configuration. The following Cloud Services modules are currently supported: Module Mobile (ios/android) SMS Notifier Google Hangout Cisco Jabber Digital Media System (DMS) Global Cache Notifier Twilio Notifier Note: SA-Announce Cloud Services are not supported on Windows 2003.

120 120 SA-Announce User Guide Once Cloud Services has been setup via SA-Announce configuration, users are ready to configure Cloud Services notification groups. The list of Available Recipient Modules allows users to associate devices to the selected service. Each subscribed module will show the current number of devices associated for the selected notification group. For example, the screenshot below shows there are two devices associated with the SMS Notifier. Associate Cloud Services to Devices Refer to the specific Cloud Services User Manual(s) for detailed information pertaining to each service.

121 Notification Group Configuration IP Speakers Groups >> Create / Edit >> IP Speakers This section describes the use of Syn-Apps IP speakers, Algo IP speakers, Atlas IP speakers, and AND IP speakers in an SA-Announce notification groups. IP speakers must be added to the system using DHCP option 72, as described in each brand's setup section before they are visible in the Groups or Schedules interface. IP Speaker Navigation Links Syn-Apps IP Speaker Setup Algo IP Speaker Setup AND IP Speaker Setup Atlas IP Speaker Setup Legacy IP Speaker Navigation Links CyberData IP Speaker Setup Valcom IP Speaker Setup To add an IP speaker to a particular notification group, first select the group from the Groups >> Create / Edit Groups page. On the IP Speakers tab, select the IP speakers to add to the group from the Available side of the list box and add them to the Selected side using the double arrow >> button. The Dynamic Group checkbox will populate the Selected field with phones that match the specified Filter. Management of group members is not necessary when the Dynamic Group checkbox is in use because the Filter will manage group members automatically. For example, enable the Dynamic Group checkbox. Add sorting criteria to the Filter field. Click the Filter button to display results. Only IP speakers meeting the filter criteria should be displayed.

122 122 SA-Announce User Guide Dynamic Group now has a new filter option - Custom Filter in the Arrange List By menu. This selection will only appear when Dynamic Group is enabled. Custom Filter allows any valid SQL filter to be applied to the group. In this case, multiple filters can be logically combined to pull any combination of devices. When the Custom Filter option is selected, a message will appear that describes the column names used in the filter.

123 Notification Group Configuration Syn-Apps Paging Relay Groups >> Create / Edit >> Paging Relays This section describes use of Syn-Apps Paging Relays in SA-Announce notification groups. Paging Relays must be added to the system using DHCP option 72, as described in the Paging Relay Setup section, before they are visible in the groups or schedules interface. To add a Syn-Apps Paging Relay to a particular notification group, first select the group from the Groups >> Create / Edit Groups page. On the Paging Relays tab, select the Paging Relays to add to the group from the Available side of the list box and add them to the Selected side using the double arrows >> button. You can make some configurations to the Paging Relay from within SA-Announce. However, to fully understand these configurations, refer to the Paging Relay Admin Guide. Click on the device, and then make the following configurations. Paging Relay Options Set individual Paging Relay options Line Out Enabled (check) to use your existing analog paging system. See Analog/IP Integration in the Paging Relay Admin Guide. Relay Action Used with relay contact closure scenarios. See Relay Contact Closures in the Paging Relay Admin Guide. On Seconds Used in conjunction with the Relay Action. Whether to set this depends on the relay contact closure use case. See Relay Contact Closures in the Paging Relay Admin Guide.

124 124 SA-Announce User Guide Set Options Click to save the above Paging Relay configurations. In some cases the Paging Relay will be able to remove the SA-Announce server from the audio path. This feature removes the need for notifications to be sent across the WAN. In this case, notifications are made without any audio streams to or from the SA-Announce server. If all the requirements below are met, a Paging Relay will act as the audio transmission point for the notification group call. Requirement Description Live Audio Group The notification group must be a live audio notification group such as a Normal or Emergency Alert group. One Paging Relay There must be one and only one Paging Relay associated to the group. IP Phones Local The IP phones associated to the notification group must all be in the same SA-Announce site and the initiator must be in the same device pool (DP) or calling search space (CSS). No Opening Tone An opening tone must not be associated to the notification group. No Legacy IP Legacy IP end-points must not be associated to the group.

125 Notification Group Configuration Static Streams Groups >> Create / Edit >> Static Streams This section describes how to add CyberData speakers into desired notification groups. Select the CyberData speaker group from the Available side of the list box and press the >> button to add the CyberData group to the Selected side of the list box. Note a prerequisite is required: CyberData IP Speakers must first be setup before adding CyberData endpoints to notification groups.refer to the CyberData IP Speak er Configuration for details. Note: The SA-Announce UI has changed for versions and above. To add legacy CyberData speak ers to notification groups for versions and above, use the Groups >> Create/Edit >> Static Streams tab.for SA-Announce and below, use the Groups >> Create/Edit >> Legacy IP tab.

126 126 SA-Announce User Guide Valcom Groups >> Create/Edit >> Valcom This section describes how to add Valcom speakers into desired notification groups. Add the speaker(s) Group Dial Code to the Valcom textbox. To assign multiple Valcom speakers to a group, delimit the group numbers with commas. If unsure of the Group Dial Code(s), visit the Valcom VIP-102B IP Solutions Setup Tool to find the specific Group Dial Code(s). Note: The SA-Announce UI has changed for versions and above. To add Valcom speak ers to notification groups for versions and above, use the Groups >> Create/Edit >> Valcom tab. For SA-Announce and below, use the Groups >> Create/Edit >> Legacy IP tab. Note a prerequisite is required: Valcom speakers must first be setup before adding Valcom endpoints to notification groups.refer to the Valcom IP Speak er Configuration for details. In addition, verify the Valcom speak er setup using the Settings >> IP Endpoints >> Valcom section.

127 Notification Group Configuration Beacons Groups >> Create / Edit >> Beacons This section describes how to add Alertus Beacon Groups to a SA-Announce notification group. The section Alertus Configuration must be completed before the Alertus tab will show configured Alert Profiles and Beacon Groups. Once Alertus been configured, Alertus Beacon Groups can be added to an SA-Announce paging group. Navigate to the Groups >> Create / Edit Groups >> Beacons tab. Use the provided interface to add Beacons to the notification group. Select an Alert Profile from the dropdown list menu. Select one or more Beacon Groups from the Available side of the list box and use the double arrows >> button to add to the Selected side.

128 128 SA-Announce User Guide Mass Notification Groups >> Create / Edit >> Mass Notify This section describes the process of adding Everbridge Scenarios to SA-Announce notification groups. SAAnnounce must be configured with the necessary parameters to contact the Everbridge system as described in the Everbridge Configuration section of this manual before the Everbridge Scenarios will appear on the groups page. Once Everbridge been configured, Everbridge Scenarios can be added to an SA-Announce paging group. Navigate to Groups >> Create / Edit >> Mass Notify tab. Use the provided interface to add Scenarios to the notification group. Select one or more scenarios from the Available side of the list box and use the double arrows >> button to add to the Selected side.

129 Creating Emergency Alert Groups Part 11

130 SA-Announce User Guide Creating Emergency Alert Groups Groups >> Create / Edit This section describes the creation of SA-Announce Emergency Alert notification groups. The Emergency Alert group type is designed to be used for emergency notifications such as Tornado Warnings or Schools on Lockdown. Emergency Alert groups play audio wave files and send text to supported devices. The inclusion of the Send Caller-Id checkbox, the group becomes a very powerful emergency notification system as security monitoring members can see who activated the emergency and respond accordingly.

131 Creating Emergency Alert Groups 131 The Emergency Alert notification group type has a number of different configuration options that are unique. The mode of an Emergency Alert group can be changed by selecting the provided checkbox's in the Emergency Alert Settings area of the General tab. Only one mode at a time can be selected. Emergency Alert Mode Description Alert Mode This is the default mode. In this mode,the Emergency Alert group is activated when called. The group will send the text message to the supported devices and begin playing the wave file until the group is called back. The maximum length of an Alert Mode is 1,000 cycles. Calling an active Emergency Alert group in alert mode will cancel the notification alert. Voice Mode Activates when called and plays the selected wave file once. When the wave file finishes, the source caller can begin to send further instructions by speaking into their handset. When the source caller hangs up the group terminates and text is cleared from the notification group end-points. Play Once This mode sets the duration of the Emergency Alert to one repeat of the wave file. After the wave file plays once the group will terminate and text will be cleared from the notification group endpoints. Timed Mode Selecting Timed Mode will expose a Time to Repeat field. Use the arrows to set the number of times the audio will repeat before group closes. To create a new Notification Group, select Groups >> Create / Edit >> New Group and configure the following settings: Emergency Alert Setting Description Group Name Enter a descriptive name for the group. Group Type Select the Emergency Alert group type. Server Group This field will only be displayed if the redundancy subsystem has been configured, see Server Redundancy for details. Select a server group for this notification group. Select <None> to run the group on the publisher only. Group Phone Settings The settings for the virtual phone that facilitates group activation. Line Number This is the extension used to call (activate) the notification group. The next available line is placed in the field by default. Enter a unique line number here.

132 132 SA-Announce User Guide Misc Settings Miscellaneous settings for the notification group. Use Security Code To secure the group check this checkbox and enter a DTMF code to associate to the group. Send Caller-ID IP speakers within the selected group will receive the caller ID associated with the source phone line. Emergency Busy detection overridden for this group, agents on a call will also receive the notification audio stream and/or text message. Tweet when activated Check this checkbox to send a status update to the Twitter account. See Twitter Configuration for setup details. Emergency Alert Services Emergency Alert services description. Weather Alerts Check this checkbox to send Weather Alerts to the groups IP Phones, , Beacons and Mass Notification. A Zip Code is required as weather alerts are localized. See Weather Alert Settings for setup details. AMBER Alerts Check this box to send AMBER Alerts to configured endpoints. A Zip Code is required to activate localize alerts. See AMBER Alert Settings for setup details. Emergency Alert Settings Emergency Alert settings description. Modes Alert Mode, Voice Mode, Play Once, Timed Mode. The modes are described at the top of this page. Wav File to Play Select the wave file to play when the group is activated. Add custom wave files to the system using the Schedules > >Wav File Upload page described here. Text to Send Enter the text to be sent with the emergency alert. The text will be sent to all end-points that support text messages. Click Add Group. It is now possible to add the group even though end-points have not yet been associated. This can be done after adding the group (as presented in this manual) or before adding the group.

133 SA-Announce Scheduler Part 12

134 SA-Announce User Guide SA-Announce Scheduler Schedules >> Create/Edit This section describes how to create scheduled notifications in SA-Announce. Scheduled notifications are used to broadcast audio and text to endpoints at predefined times.for example, school bells and manufacturing break bells set to ring at a specified time. The SA-Announce Scheduler tab (Schedules >> Create/Edit >> Scheduler), is a helpful tool used to assign scheduled events with their associated scheduled notifications. The Scheduler tool displays all scheduled events per schedule group associated with the scheduled notifications using various calendar-views, providing greater visibility for users. Note: As of SA-Announce , SA-Announce Scheduler has been redesigned to use a new graphical scheduler tool that allows for easy scheduled event creation, including recurring events. For versions and above, the Overrides tab is no longer available, (formerly found by navigating to: Schedules >> Scheduled Broadcasts >> Overrides), as the graphical scheduler tool can be easily manipulated to create schedule overrides. The SA-Announce Configuration Utility will update any existing schedules, including their overrides, to the new format required by the graphical scheduler tool. Note: In order for schedules to function properly, both the Scheduler Service and Broadcast Service must be running. See Services >> Broadcast Services for additional details.

135 SA-Announce Scheduler 135 The Schedules >> Create/Edit >> General tab provides a place to add and modify Schedule Notification names, associated audio, text, and disable schedules. Click New Schedule near the bottom-left side of the page and configure the following items: Schedule Setting Description Schedule Name Enter a descriptive name for the schedule. Time Zone Select a time zone for the schedule. By defaults, the servers time zone is selected. Server Group Use with the Redundancy feature. Select the server group where this notification should reside. Select <None> to run the group on the publisher only. This field will only be displayed if the redundancy sub-system has been configured. See Server Redundancy for details. Disable Schedule When checked, the schedule will be disabled and will not activate. Days Days to Play Select the days to play the schedule by clicking the check-boxes to activate. One or more days may be selected. Times Times to Play Enter the times to play using the 24 hour format. For example, 4:00 pm = 16:00. Sound and Other Settings Schedule sound notification and other settings. Sound to Play Select the wave file to play when the schedule is activated. Add custom wave files to the system using the Schedules >> Wav File Upload page. Volume Avaya does not currently support this feature on their phones. Repeat The number of times to play the wave file when the schedule is active. Text to Send Enter the text to send all endpoints that support text messages. Emergency Enable to send text and audio stream to busy phones. Click Add Schedule. The schedule can be saved although endpoints have not been associated. Endpoints can be associated after saving the schedule. As of SA-Announce version , active schedules are listed first, (above inactive schedules) to provide an easier, more user-friendly experience.

136 SA-Announce User Guide Creating Schedules Using the Scheduler Tool Schedules >> Create/Edit >> Scheduler This section describes how to edit scheduled notifications in SA-Announce. Navigate to the Schedules >> Create/Edit >> General tab. The SA-Announce Scheduler (Schedules >> Create/Edit >> Scheduler), is a helpful tool used to assign scheduled events with their associated scheduled notifications. The Scheduler tool displays all scheduled events associated with the scheduled notifications using various calendar-views, providing greater visibility for users. See the Creating Schedules Using the Scheduler Tool section for details. SA-Announce and great includes a Calendar Scheduler. The Scheduler tool allows users to view, edit, and create schedule events. The SA-Announce Scheduler displays the calendar using five different views: Day, Work Week, Week, Month, and Timeline. Select the preferred view using the appropriate calendar buttons located in the top-right corner of the Scheduler tool. Note**: The graphical calendar tool only displays scheduled events associated with the currently selected scheduled notification. Users must first select an existing Scheduled Notification from the Select Schedule to Edit dropdown list, or click the New Schedule button located at the bottom of the page to create a new Scheduled Notification.

137 SA-Announce Scheduler 137 SA-Announce Scheduler - Useful Tools Scheduler Tools Description Schedule Group Select a Schedule Group to view, add, modify, and delete scheduled events. Select Schedule to Edit Use the Select Schedule to Edit dropdown list to choose display all associated scheduled events associated with the currently selected scheduled notification.** Page Navigation Use the Page Navigation buttons, denoted: interface to browse different Calendar days or months:, provided in the user Down Arrow Use the Down arrow, denoted:, to open a Calendar pop-up. Click on a day to isolate schedules on a particular day. Right Arrow Left Arrow Use the Right arrow, denoted: Use the Left arrow, denoted:, to view the next month., to view the previous month. View Schedule Event Note**: The graphical calendar tool only displays scheduled events associated with the currently selected scheduled notification. Event Details Any associated Scheduled Events will be displayed different, depending on the selected Calendar View (Day, Week, Month, Timeline, etc.). To isolate the Scheduled Event (using any view), right-click on the event and choose Open, Edit Series (Recurring Events only), Show Time As >> [... ], Label As >> [... ], or Delete.

138 138 SA-Announce User Guide SA-Announce Scheduler tool displays scheduled events according to the selected Calendar View. This exam ple show s the Day view.

139 SA-Announce Scheduler Creating Schedules using the Scheduler Tool Create A New Event Description Calendar View Make sure to select a Schedule group from theselect Schedule to Edit dropdown list before beginning. Then, select a Calendar view button to begin. Select a Day Place a cursor over the calendar day and right-click. A dropdown list will appear with various options: 1. New Scheduled Event - Create a new scheduled event. 2. New Recurring Event** - Create a new, recurring scheduled event. 3. Go to This Day - Scheduler zooms in on the selected day to view, edit, add, and delete scheduled events on a particular day. 4. Go to Today - Scheduler takes viewers to the calendar date to view, edit, add, and delete scheduled events on the current calendar date. 5. Go to Date - Choose a Date and Calendar View to view, edit, add, and delete scheduled events. 6. Change View To >> [Available Calendar Views] Select a view to continue. Directions Subject 1. Provide a Subject - Type a descriptive subject to describe the Schedule. For example, "Summer Schedule Morning School Bells." Location 2. (Optional) Provide a Location - Type a descriptive location to help identify the area the schedule affects. For example, " High School, Buildings 1 & 2." Screenshot 139

140 140 SA-Announce User Guide Label 3. (Optional) Choose a Label - Select a label to categorize the schedule. The default is <None>. Start Time 4. Select a Start Time for the schedule to take effect. Details Box 5. (Optional) Add detailed notes about the schedule in the details textbox located below Start Time. Click OK to continue or Cancel to exit without saving the schedule. Optional Features Recurrence 6. Recurrence checkbox is disabled by default. Enable (check) the Recurrence checkbox if the schedule needs to repeat more than once. Additional fields will populate once the feature is enabled: Use the radio-button list to select how often the schedule should repeat; choose Daily, Weekly, Monthly, Yearly, Every [ X ] Day (s), or Every Weekday. Note: Each available option has its own properties, that by default are hidden unless selected. For example - Week ly provides check boxes for each day of the week. Use the radio-button list to choose when to end the schedule recurrences; choose No end date (default), End after [X] occurrences, or End By [DATE]. Click OK to save the scheduled event(s) and close out of the detail screen. To close out of the detail screen, click Cancel. **Note: Selecting New Recurring Event button from the available options is an alternative method to creating recurring schedule events. This feature is also

141 SA-Announce Scheduler available by click ing the Recurrence check box located within the New Scheduled Event option. The Recurrence check box can be enabled at any time for existing scheduled events. Learn more by visiting Editing a Schedule. 141

142 SA-Announce User Guide Editing A Schedule Schedules >> Create/Edit >> General This section describes how to edit a Schedule Notification using the General tab. 1. To edit a Scheduled Notification, navigate to Schedules >> Create / Edit >> General tab. 2. Select an existing Scheduled Notification from the Select Schedule to Edit dropdown list. 3. To edit the Scheduled Notification name, position the cursor in the Select Schedule to Edit dropdown list and click. A blinking cursor will appear, indicating users can change the schedule name. Press the Enter key to save the name when finished. 4. Modify any of the available Schedule Settings. Click the Save Schedule button at the bottom to save changes.

143 SA-Announce Scheduler Editing Associated Scheduled Events Schedules >> Create/Edit >> Scheduler To edit a Scheduled Notification's associated scheduled events, navigate to Schedules >> Create/Edit >> Scheduler tab. 1. Right-click on the Scheduled Event in the calendar view. A pop-up window will appear displaying different options. 2. Select either: Option #1 - Open to edit the specific Scheduled Event. Option #2 - Edit Series to edit the entire Scheduled Event. 3. The Scheduled Event window will appear. Make the necessary changes. 4. Click OK to return the the calendar view. Click Cancel to exit the window, without saving any changes, or click Delete to remove the event. Note: Deleting a recurring scheduled event using Option #1 - Open (see above), will only delete the scheduled event on the selected day. To delete an entire series, use Option #2 - Edit Series >> Delete or right-click on the event in the calendar view and click Delete. A pop-up window will appear, asking whether or not to delete the entire series or just the selected occurrence. 5. Click the Save Schedule button to save the Scheduled Event with its associated Scheduled Notification. Note**: The graphical calendar tool only displays scheduled events associated with the currently selected scheduled notification. Users must first select an existing Scheduled Notification from the Select Schedule to Edit dropdown list, or click the New Schedule button located at the bottom of the page to create a new Scheduled Notification.

144 SA-Announce User Guide Audio Upload Schedules >> Audio Upload Custom.Wav files can be added to the SA-Announce notification system to use with Schedules and Emergency Alert group types. Navigate to the Schedules >> Audio Upload page to upload new.wave files to SA-Announce. Audio files being added to the application must meet the following requirements: Audio File Requirement Description CODEC - G.711 u-law The audio file compression algorithm (CODEC). Sample Rate - 8k The audio file sample rate. Sample Size - 8bit The audio file sample size. Channels - mono The number of audio channels.

145 SA-Announce Scheduler 145 Use an audio conversion utility, such as Sony Sound Forge Audio Studio, Audacity, or Adobe Audition, to meet the requirements above. Consult your audio editing program's documentation for details saving to the required format. To add a new wave file to the SA-Announce system: Add Custom Audio File Description Navigate Navigate to Schedules >> Audio Upload Browse Press the Browse button to add a file to upload. Remove Press the Remove button to remove a selected audio file. Add File Add more files to upload using the Add File button. Upload Press the Upload button to complete the process and upload the wave file to the system. The newly added wave files are now available to be used with Emergency Alert groups and Schedules.

146 146 SA-Announce User Guide Customizing Audio Feedback Customize SA-Announce audio prompts by modifying the.wav files included in SA-Announce. The prompts heard when dialing an SA-Announce notification group can be found in the SA-Announce application server at: C:\program files\syn-apps\sa-announce\broadcaster\wav directory. A brief description of each of the files is contained in the following section Audio File Descriptions. See the chapter Audio Upload to add custom wave files for use with Emergency Alert groups and Schedules.

147 SA-Announce Scheduler Audio File Descriptions SA-Announce 2.0 Voice Prompts The prompts heard when dialing a SA-Announce notification group can be found on the SA-Announce application server at: C:\program files\syn-apps\sa-announce\broadcaster\wavdirectory. A brief description of each of the files is contained in the below table: Audio File Wave file descriptions dtmf_0 - dtmf_star *Do not edit the DTMF files they are used when in-band DTMF is required. EAActivated Played to the caller when activating an emergency alert group when alert mode or timed mode is selected. "Emergency Alert notification has been activated." EACanceled Played to the caller of an active Emergency Alert group when in alert mode. "Emergency Alert notification has been canceled." GroupActive Played to the caller of an active RecordNPlay group. "We're sorry but the group you have dialed is currently active." NoLiveAudio Played when a group has no valid end-points associated. "The group has no live audio end-points. Your message is being delivered to any non-audio recipients" RecordNPlay Played to the caller of a RecordNPlay group when the Advanced Setting rnpcallerannouncement is set to True. "Begin recording after the beep, press * to reset the recording, press # or hang-up to send the recording." RelayError Played to the caller of a group whose paging relay is not communicating. "Paging relay error, notification has been aborted. Try again or contact your system administrator." SecurityCode Played before waiting for the security code. "This is a secure page group, Please enter the DTMF security code." SecurityCodeWrong Played when security code is entered incorrectly. You have entered an incorrect security code, please call back and try again. Goodbye." SomeDestBusy Used when so many destinations are busy that a confirmation tone will not be sent. Some destinations are busy "[Paging Continues].

148 Sending A Text Message Part 13

149 Sending A Text Message Sending A Text Message Groups >> Send Text >> Send Text Message To send a text message to a notification group, users must first create a notification group with designated endpoints. This can be an existing notification group of any type, as long as the group type allows users to select the end-points. The Send Text Message page allows users to create the message. Text messages do not activate Twitter. Text messages will only send s when Text notification group types are used. If the group selected contains end-points that cannot display text, such as IP speakers that don't have text displays, they will not receive the text.

150 150 SA-Announce User Guide To send a text message, fill in the following fields: Setting Description General Settings Send text message general settings. Use End-Points from Group Use the dropdown list to select a notification group whose endpoints will receive the text message. Speaker Alert Tone A sound notification alerts the recipients of a text message notification. The sound will be played on the Desktop Notification Client and IP speaker endpoints. (Avaya phones will not play this tone). Image Select an image to send with the text message. The image will be displayed on supported endpoints. Message to Send Enter the text message in the blank textbox. Speaker Text Options Text options for IP Speakers that support Text. Text Color Choose the text color. Scroll Speed Message scroll speed. Max Duration Sec The number of times to loop the scrolled message. Pause Seconds The number of seconds to pause the message between loops. Press the Send Message button to send the message.

151 Sending A Text Message Message Browser Groups >> Message Browser The Groups >> Message Browser page provides a table for viewing recently sent text messages. The message browser contains a row for each message that was sent to a particular endpoint. The columns of each row contain the following information: Column Description Message Message Body: The message that was sent. Sender: The user that sent the text message followed by the group it was sent to. Posted Posted: The date and time the message was posted to the endpoints. Sent To Desc: The description field of the endpoint the message was sent to. Phone: The name of the phone the message was sent to. IP: The IP address of the phone the message was sent to. Click on the column name to sort the Message Browser data. To sort items by a column in a ascending or descending order, click on the column header. Messages sent within the last 30 days are retained in the Message Browser by default. To change the retention value, navigate to Services >> Broadcast Services >> Advanced Settings. Edit 'messageretentiondays' to change the number of days the system will retain messages.

152 SA-Announce Reporting Part 14

153 SA-Announce Reporting SA-Announce Reporting Services >> Reports / Analytics SA-Announce includes built-in reports, which gather and export detailed information regarding notification group configuration data and system user permissions. Available Reports Notification Group Report Notification Activity Report Schedules Activity Report Text Activity Report Login Activity Report Users Report Refer to the Report Tools table below to understand how to use the available Reporting tools: Report Tools Page Navigation Export Format Export Method Description Use the Page Navigation buttons browse different pages of the report. in the user interface to To download a report, first use the Export Format dropdown list next to the button to change the report format. Reports can be downloaded in a variety of formats including: PDF, Excel, RTF, MHT, HTML, Text, CSV, and Image. By default, reports will be exported to PDF. Second, choose the export method. Users can download and save the report to disk by clicking the Save button in the user interface, Alternatively, users can export the report and view in a new window by using the Save in New Window button Printing To print an entire report, use the Print button Page button to print the current report page.. Alternatively, use the Print Current

154 SA-Announce User Guide Notification Group Report Services >> Reports / Analytics To access the Notification Group Report, navigate to Services >> Reports / Analytics >> Notification Group Report. Select the Notification Group Report from the dropdown list. This report lists every activated notification in chronological order; starting with the most recent notification at the top. The report lists a timestamp of all SA-Announce notifications, their group name, Caller ID, and Duration the Notification was run. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Notification Groups Report Description Group Name Provides the current SA-Announce Notification Group(s) Type The Notification Group Type, set by the Notification Group creator. Number This column displays any specific user permissions associated to a specific user. Partition Does not apply for SA-Announce Avaya. Device Pool Does not apply for SA-Announce Avaya. Emergency Indicates whether or not the Group Type was an Emergency Alert. Volume Volume associated with the notifications' endpoint(s).

155 SA-Announce Reporting 155 Security Code Lists the security code set by the group creator. Send Caller ID Lists whether the notification included the Initiators' Caller ID. True = Caller ID included; False = Did not include Caller ID. Stored Audio Lists any audio associated with the notification. Text Lists the text associated with the notification. Repeat Lists the number of times the notification is repeated before ending. Associated Endpoints Associated Endpoint (Name) Lists the associated endpoints by name. Type Lists the type of endpoint (IP phone, IP speaker, analog device, Desktop Notification Client, etc). Description Gives a description of the associated endpoint(s). IP Address Lists the IP Address of the associated endpoint(s).

156 SA-Announce User Guide Notification Activity Report Services >> Reports / Analytics To access the Notification Activity Report, navigate to Services >> Reports / Analytics >> Notification Activity Report button. This report lists every activated notification in chronological order; starting with the most recent notification at the top. The report lists a timestamp of all SA-Announce notifications, their group name, Caller ID, and Duration the Notification was run. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Notification Activity Report Description Notification Start Date Notification Start Date provides a timestamp for every activated notification. Group Name Group ID identifies that name of the notification (group) activated. Caller ID Caller ID identifies the user who activated the notification. Duration (Seconds) The duration, in seconds, that the notification was active.

157 SA-Announce Reporting Schedules Activity Report Services >> Reports / Analytics To access the Schedules Activity Report, navigate to Services >> Reports / Analytics >> Schedules Activity Report button. This report lists every activated notification in chronological order; starting with the most recent notification at the top. The report lists a timestamp of all SA-Announce Schedules, their group name, and Duration the schedule was run. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Schedules Activity Report Description Notification Start Date Notification Start Date provides a timestamp for every activated notification. Group Name Group ID identifies that name of the notification (group) activated. Duration (Seconds) The duration, in seconds, that the notification was active.

158 SA-Announce User Guide Text Activity Report Services >> Reports / Analytics To access the Text Activity Report, navigate to Services >> Reports / Analytics >> Text Activity Report button. This report lists every activated notification in chronological order; starting with the most recent notification at the top. The report lists a timestamp of all SA-Announce text notifications, their group name, the system name the notification was Sent By. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Text Activity Report Description Notification Start Date Notification Start Date provides a timestamp for every activated notification. Group Name Group ID identifies that name of the notification (group) activated. Sort By SA-AnnounceAPI is the standard default option.

159 SA-Announce Reporting Login Activity Report Services >> Reports / Analytics To access the Login Activity Report, navigate to Services >> Reports / Analytics >> Login Activity Report button. The report lists a timestamp of all users logging into the SA-Announce system, their client's IP Address, and User Name used to login to the system. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Login Activity Report Description Login Date Timestamp of users' SA-Announce system activity (login) listed in chronological order with the most current login activity listed first. IP Address The IP Address of the client (device) used to login to SA-Announce. User Name Identifies the user who logged into SA-Announce.

160 SA-Announce User Guide Users Report Services >> Reports / Analytics To access the Users Report, navigate to Services >> Reports / Analytics >> Users Report button. The Users Report data lists current SA-Announce users and system user permissions if they exist. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Users Report Columns Description User Name Provides the current SA-Announce users. Administrator The report will state True if a user is an administrator or False if they are not. Permissions This column displays any specific user permissions associated to a specific user.

161 Syn-Apps Analytics Part 15

162 SA-Announce User Guide Syn-Apps Analytics Services >> Reports / Analytics >> Analytics button To access the Syn-Apps Analytics user interface, navigate to Services >> Reports / Analytics >> Analytics button. Syn-Apps Analytics is an optional module available for purchase. When installed, it provides a holistic view of all notification activity including both on and off-premise services. Generates complete activity reports including: Group name, Activation date/time, Initiator, Associate Endpoints, etc. The following table provides information on the available export tools and page navigation: Analytics Report Tools Description Page Navigation Export Method Use the Page Navigation buttons interface to browse different pages of the report. in the user Choose the export method using one of the following buttons: The first table, All Notifications, provides a list of all notifications historically ever sent. To view more information on a specific notification, click on a notification to select in the All Notifications table. The top Selected Details pane, located to the right of All Notifications table, will populate with quick information such as the Instance ID, Number of Endpoints associated with the notification, and the number of different endpoint types.

163 Syn-Apps Analytics 163 All Notifications Table Description Time Provides a timestamp of when the notification was sent. Initiator Lists the type of device the notification was initiated from. Notification Type Lists the notification type (normal, scheduled, text, emergency, etc). Notification Name Lists the notifications' name. Number of Errors Lists the number of errors encountered when sending the notification. Selected Details Pane Description of the details pane associated with the All Notifications Table Instance ID The ID associated with the notification Number of Endpoints Lists the number of endpoints assigned to the notification. Different Types of Endpoints Lists the number of different endpoint types, such as Mobile, IP phones, IP speakers, etc. The second table, Endpoint Events Table, provides detailed insight on an individual's endpoint activity. To view more information on a specific endpoint, click on a endpoint to select in the Endpoint Events table. The bottom Selected Details pane, to the right of Endpoint Events table, will populate with additional information on a specific endpoint. It is important to note that the level of Endpoint Event granularity depends upon the endpoint type. Some types may include more or less information than others. Endpoint Events Table Description Endpoint Lists a specific endpoint Endpoint Type Lists the type of endpoint (by brand), such as Avaya IP phones, Syn-Apps Desktop Client, Syn-Apps Paging Relay, IP Speaker, etc. Time The most recent activity timestamp sent to or received by the endpoint. Event Type Describes the most recent activity associated with the endpoint. Event types may include: Received Notification, Sending Command, Command Sent, Error. Note: The level of Endpoint Event granularity depend upon the endpoint type. Some types may include more or less information than others. Selected Details Pane Description Endpoint Details Provides details about the Endpoint Type. These details vary according to the Endpoint Type. Each Endpoint Event is color-coded according to its notification status.

164 164 SA-Announce User Guide Endpoint Event Notification Status Description and Row Color Intermediate Step (White) This is the intermediate step before a notification becomes a Success. The row color is white when it's in an Intermediate Step. Success (Green) This step represents the notification has become a successful event. The row color is green when the notification meets the endpoint successfully. Note, some modules, such as Mobile Notifier, have more than one success event. Success is not necessarily limited to the last event in the life-cycle. For example, Mobile Notifier considers both Notification Opened and Notification Ack nowledged as a Success. Error (Red) This step represents there was an error when attempting to deliver the notification. The row color is red when an Error has occurred.

165 Web Service (API) Part 16

166 SA-Announce User Guide Web Service (API) The SA-Announce web service (API) provides methods that can be used to perform operations such as activating or deactivating an emergency alert group or dispatching a text message. The methods are accessed via HTTP (standard or SOAP encapsulated) GET/POST to the SA-Announce web service. To browse the available methods, open Internet Explorer on the application server and navigate to A list of available methods will be shown with descriptions. Clicking on one of the method names will display the methods full description page. This page allows the method to be tested and shows sample request and response formats. Programmers can access the web service description language file at While the web service description page can only be accessed from the application server, the web service methods can be accessed from any authorized server. To configure authorized servers see Service Configuration Options, Servers authorized to use the SA-Announce API setting. Methods with user name and password parameters only require the user name and password if the requesting server is not a server authorized to use the SA-Announce API. Important: Most methods require a group-id to activate the notification group. The group-id can be found on the Create / Edit Groups page. The group-id for the selected group will appear to the right of the Group Type drop down list. The various methods are described in the following table: API Method Description Dispatch Methods Methods that activate notification group functionality. DispatchEmergencyAlert Invoke this method to activate or deactivate an emergency alert group. Parameters id [int] - the group-id of the emergency alert group to activate.. username [string] - the SA-Announce user name of the requesting user. passw ord [string] - the SA-Announce passw ord for the requesting user. start [bool] - true to start the emergency, false to end it (for alert mode only). (optional) securitycode [string] - the group security code, if one exists. DispatchEAOverride Invoke this method to activate or deactivate an emergency alert group with overridden text. Parameters id [int] - the group-id of the emergency alert group to activate. username [string] - the SA-Announce user name of the requesting user. passw ord [string] - the SA-Announce passw ord for the requesting user. start [bool] - true to start the emergency, false to end it (for alert mode only). overridetext [string] - the new text to attach to the group. (optional)securitycode [string] - the group security code, if one exists. DispatchGroupStoredAudioMode Invoke this method to activate a normal group type in stored audio mode. In this mode the group end-points will play the specified audio file for a number of repeats and then end. This method does not support EA groups, use DispatchEmergencyAlert instead. Parameters id [int] - the group-id of the normal group to activate.

167 Web Service (API) 167 w avfile [string] - the name of the SA-Announce alert w av file. text [string] - the text to send to end-points (255 char max). repeatnumber [int] - the number of times to repeat the audio file. cancelbutton [bool] - true to send a cancel button to IP phone end-points. (optional)securitycode [string] - the group security code, if one exists. DispatchGroupStoredAudioModeByGroupNam Invoke this method to activate a normal group type in stored audio e mode. In this mode the group end-points will play the specified audio file for a number of repeats and then end. This method does not support EA groups, use DispatchEmergencyAlert instead. Parameters group_name [string] - the group name of the normal group to activate. w avfile [string] - the name of the SA-Announce alert w av file. text [string] - the text to send to end-points (255 char max). repeatnumber [int] - the number of times to repeat the audio file. cancelbutton [bool] - true to send a cancel button to IP phone end-points. (optional)securitycode [string] - the group security code, if one exists. DispatchImageURL Invoke this method to send an image to the end-points in a target group. A text parameter is required for end-points that do not support images. Parameters id [int] - the group-id of the emergency alert group to activate. text [string] - the text to send to end-points that do not support images. soundtoplay [string] - the TFTP sound to play upon delivery IE analog1.raw. imageurl [string] - the URL of the.png image to display in the message. username [string] - the SA-Announce user name of the requesting user. passw ord [string] - the SA-Announce passw ord for the requesting user. DispatchTextMessage Invoke this method to send a text message to the end-points in a target group. Images must be located in the SA-Announce\Images\ directory. Parameters id [int] - the group-id of the emergency alert group to activate. text [string] - the text to send to end-points that do not support images. soundtoplay [string] - the TFTP sound to play upon delivery IE analog1.raw. imagefilename [string] - the name of the image to display in the message. username [string] - the SA-Announce user name of the requesting user. passw ord [string] - the SA-Announce passw ord for the requesting user. Inform ation Methods Methods that return SA-Announce configuration information. GetDeviceByDN Invoke this method to get a list of available IP phone devices with the given directory number. Use % as a wildcard (this is a LIKE statement). Returned Parameters name [string] - the device name (IE SEP ). ip [string] - the device IP address. description [string] - the device description. display [string] - the line display (caller-id). dn [string] - the directory number attached to the device. xmlenabled [bool] - true if the device is an XML enabled IP phone. GetDeviceByUserName Invoke this method to get a list of available IP phone devices with the given user name in the line display field (caller-id). Use % as a wildcard (this is a LIKE statement). Returned Parameters name [string] - the device name (IE SEP ). ip [string] - the device IP address.

168 168 SA-Announce User Guide description [string] - the device description. display [string] - the line display (caller-id). dn [string] - the directory number attached to the device. xmlenabled [bool] - true if the device is an XML enabled IP phone. GetEmergencyAlertGroups Invoke this method to get a listing of emergency alert groups. Returned Parameters name [string] - the group name. groupid [int] - the group-id. type [string] - the group type (EmergencyAlert). alertmode [bool] -true if this is an alert mode group. repeatmode [bool] - true if this is a repeat mode group. GetGroupListing Invoke this method to get a list of groups the given user is allowed to access. Returned Parameters name [string] - the group name. groupid [int] - the group-id. type [string] - the group type (EmergencyAlert). alertmode [bool] -true if this is an alert mode group. repeatmode [bool] - true if this is a repeat mode group. securitycode [string] - the groups security code, if one exists. isactive [bool] - true if the group is currently active. GetImageList Invoke this method to get a list of available image files (SAAnnounce image files are located in the SA-Announce/Images directory and must be.png). Returned Parameters name [string] - the image file name. url [string] - the HTTP URL of the image file. size [long] - the size of the image file in bytes. GetSoundList Invoke this method to get a list of available audio alert files (SAAnnounce audio alert files are located in the SA-Announce/ Broadcaster/AlertWav directory and must be encoded properly). Returned Parameters name [string] - the w av file name. url [string] - the HTTP URL of the w av file. size [long] - the size of the w av file in bytes. End-Point Registration and Heart Beat Methods to register and keep-alive IP end-points. RegisterDesktopClient Syn-Apps Desktop Client Register Method. DesktopClientHeartBeat Syn-Apps Desktop Client Heart Beat Method. RegisterIpSpeaker Syn-Apps IP Speaker Register Method. See Syn-Apps IP Speaker Setup for details. IpSpeakerHeartBeat Syn-Apps IP Speaker Heart Beat Method. Other Methods Methods not intended for public use There are a number of methods listed as not intended for public use, please refrain from using these unless directed by Syn-Apps support.

169 Settings Part 17

170 SA-Announce User Guide Settings Services >> Broadcast Services >> Settings settings must be configured prior to SA-Announce sending s when groups are activated. Navigate to the Services >> Broadcast Service >> Settings tab to fill out the settings. Enter an SMTP Server and a Mailer from address in the provided text boxes. Click the Save button to save changes. SA-Announce will now be able to send s to configured endpoints when the notification is activated.

171 AMBER Alert Settings Part 18

172 SA-Announce User Guide AMBER Alert Settings Services >> Broadcast Service >> AMBER Alert The AMBER AlertTM Program is a voluntary partnership between law-enforcement and transportation agencies, broadcasters and wireless carriers to activate an urgent bulletin in the most serious child-abduction cases. The goal of an AMBER AlertTM is to instantly galvanize the entire community to assist in the search for and the safe recovery of the child. AMBER AlertTM requires the SA-Announce server to have internet access to The AMBER AlertTM service runs inside the broadcast service as it is coupled to emergency alert groups. This coupling is for multiple reasons but primarily due to the need to have an endpoint association for notifications. It is important to understand that the AMBER AlertTM do not activate as a result of calling the Emergency Alert group. When calling the Emergency Alert group, the normal emergency alert functionality is carried out. Once a user has activated an AMBER AlertTM, alerts will be active as long as the Broadcast Service is running. The service checks for new alerts immediately as the service is restarted and checks for new AMBER AlertTM every 'x' minutes. It is important to have a low "new alert" interval setting so recipients will be notified of new alerts shortly after they occur.

173 AMBER Alert Settings 173 The settings for the AMBER AlertTM service are listed on the AMBER Alert Settings tab: AMBER AlertTM Settings Description Check for new alerts every (minutes) This setting controls how often the service checks for AMBER AlertTM. The default minimum setting is every 10 minutes. Resend active alerts (minutes) This setting controls how often alerts are re-sent. 0 minutes is the default setting, which means users will only receive AMBER Alerts once per update. The alert will not be re-sent while active unless a duration is entered here. For example, to send alerts every 4 hours while they are active, enter '240' for the re-send value. Please note that s are never re-sent. Send alerts regardless of zip code This checkbox setting controls the localization of AMBER Alerts. If the setting is unchecked, users will only receive AMBER Alerts that originated in their state. By default, this setting is always checked (on), meaning users will receive all AMBER Alerts regardless of the state they originate in. Sample AMBER Alert: Visit the URL in the AMBER Alert notification for more information.

174 174 SA-Announce User Guide Apply AMBER Alert Settings to a Paging Group Navigate to Groups >> Create/Edit Groups >> General tab and select an Emergency Alert group from the Select Group to Edit dropdown list. To activate an AMBER AlertTM, check the AMBER Alert checkbox. This will open an additional field to enter zip code(s). Multiple zip codes can be used when comma delimited. Click the Save Group button after entering all information. AMBER Alerts TM for the specified criteria are now active.

175 Weather Alert Settings Part 19

176 SA-Announce User Guide Weather Alert Settings Services >> Broadcast Services >> Weather Alert Settings The Weather Alert feature uses the National Weather Service to gather active alert data. Weather Alerts require the SA-Announce server have internet access to alerts.weather.gov. The Weather Alert feature runs with the SA-Announce broadcast service as it is coupled to emergency alert groups. This coupling is for multiple reasons but primarily due to the need to have an endpoint association for notifications. It is important to understand that the Weather Alerts do not activate as a result of calling the emergency alert group, in this case the normal emergency alert functionality is carried out. To activate Weather Alerts for a particular notification group follow the instructions in the table below. Alerts will be active as long as the Broadcast Service is running. Weather Alert Activation Description Select Notification Group From the Groups >> Create Edit Groups page, select an existing emergency alert group or create a new one to display the weather alerts check box. Select Weather Alerts Check the Weather Alerts check box, this will display a FIPS entry field. Enter the FIPS code(s) Enter the FIPS codes for the counties to monitor in a comma delimited list. Use the FIPS link next to the entry field to bring up a searchable table of FIPS

177 Weather Alert Settings 177 codes. Enter a state FIPS code to monitor an entire state. State FIPS codes end in 000. Enable Events Make sure Warning, Watches or Advisory events are enabled in the settings section described in the remainder of this section.

178 178 SA-Announce User Guide Services >> Broadcast Services >> Weather Alert The Weather Alert tab also contains an area to configure which weather Watches, Warnings and Advisories to alert. By default all alerts are deactivated. Review the list and select alerts that may apply to the organizations' geographic location. Weather Alert Settings Description Check for new alerts (minutes) This setting controls how often the service checks for Weather Alerts. Two minutes is the minimum and five minutes is the default. Resend active alerts (minutes) This setting controls how often alerts are resent. By default, alerts are resent every 20 minutes until the event ends. To disable the resend enter '0'. s are never resent. Select alerts from the Available lists by clicking to highlight. Then use the double-right arrow buttons >> to move the highlighted alerts to the Selected lists. Standard Windows Ctrl-click and Shift-click can be used to select items. See Weather Alert Supported Events for the list of all supported events.

179 Weather Alert Settings 19.1 Weather Alert Supported Events The following events are currently supported by the weather alerts CAP feed at alerts.weather.gov: Weather Alert Events 911 Telephone Outage Administrative Message Air Quality Alert Air Stagnation Advisory Ashfall Advisory Ashfall Warning Avalanche Warning Avalanche Watch Beach Hazards Statement Blizzard Warning Blizzard Watch Blowing Dust Advisory Blowing Snow Advisory Brisk Wind Advisory Child Abduction Emergency Civil Danger Warning Civil Emergency Message Coastal Flood Advisory Coastal Flood Statement Coastal Flood Warning Coastal Flood Watch Dense Fog Advisory Dense Smoke Advisory Dust Storm Warning Earthquake Warning Evacuation Immediate Excessive Heat Warning Excessive Heat Watch Extreme Cold Warning Extreme Cold Watch Extreme Fire Danger Extreme Wind Warning Fire Warning Fire Weather Watch Flash Flood Statement Flash Flood Warning Flash Flood Watch Flood Advisory Flood Statement Flood Warning Flood Watch Freeze Warning Freeze Watch Freezing Drizzle Advisory Freezing Fog Advisory Freezing Rain Advisory Freezing Spray Advisory Frost Advisory Gale Warning 179

180 180 SA-Announce User Guide Gale Watch Hard Freeze Warning Hard Freeze Watch Hazardous Materials Warning Hazardous Seas Warning Hazardous Seas Watch Hazardous Weather Outlook Heat Advisory Heavy Freezing Spray Warning Heavy Freezing Spray Watch Heavy Snow Warning High Surf Advisory High Surf Warning High Wind Warning High Wind Watch Hurricane Force Wind Warning Hurricane Force Wind Watch Hurricane Statement Hurricane Warning Hurricane Watch Hurricane Wind Warning Hurricane Wind Watch Hydrologic Advisory Hydrologic Outlook Ice Storm Warning Lake Effect Snow Advisory Lake Effect Snow and Blowing Snow Advisory Lake Effect Snow Warning Lake Effect Snow Watch Lakeshore Flood Advisory Lakeshore Flood Statement Lakeshore Flood Warning Lakeshore Flood Watch Lake Wind Advisory Law Enforcement Warning Local Area Emergency Low Water Advisory Marine Weather Statement Nuclear Power Plant Warning Radiological Hazard Warning Red Flag Warning Rip Current Statement Severe Thunderstorm Warning Severe Thunderstorm Watch Severe Weather Statement Shelter In Place Warning Sleet Advisory Sleet Warning Small Craft Advisory Snow Advisory Snow and Blowing Snow Advisory Special Marine Warning Special Weather Statement Storm Warning Storm Watch

181 Weather Alert Settings Test Tornado Warning Tornado Watch Tropical Storm Warning Tropical Storm Watch Tropical Storm Wind Warning Tropical Storm Wind Watch Tsunami Advisory Tsunami Warning Tsunami Watch Typhoon Statement Typhoon Warning Typhoon Watch Volcano Warning Wind Advisory Wind Chill Advisory Wind Chill Warning Wind Chill Watch Winter Storm Warning Winter Storm Watch Winter Weather Advisory 181

182 Syn-Apps Paging Relay Configuration Part 20

183 Syn-Apps Paging Relay Configuration Syn-Apps Paging Relay Configuration Settings >> IP Endpoint Setup >> Syn-Apps IP The Settings >> IP Endpoint Setup >> Syn-Apps IP tab contains Paging Relay configuration information. For information on how to add Paging Relays to an SA-Announce notification group, see the Group Paging Relays section. Each Paging Relay to be used with the system must be registered. Once the Paging Relay has registered, it will appear in the Settings >> IP Endpoint Setup >> Syn-Apps IP tab. For details on Paging Relay registration see Paging Relay Setup. To edit the following information for each of the Paging Relays, press the Edit link on the device line item to begin editing the row. Then press the Update link on the device line item to save.

184 184 SA-Announce User Guide Paging Relay Setting Description Name (MAC) Enter a name for the Paging Relay. The default name will be the Paging Relays' MAC address. Description Enter a description for the Paging Relay. The default description will display the device type, Paging Relay. Best practice method is to add the devices' location in the description field. Firmware The firmware version of the Syn-Apps IP Device. This is not editable. D.N. Not applicable to the Paging Relay. vol Setting the volume here, overrides any volume setting in the Paging Relay interface. mic Not applicable to the Paging Relay. Selected Device Detail Clicking on a devices' line-item will display the device details in the 'Selected Device Detail' right pane. Model The Syn-Apps IP devices model name. This is not editable. IP Address The IP Address of the Syn-Apps IP Device. This is not editable. Last The date and time of the last registration or heartbeat message from the SynApps IP Device. This is not editable. Clock Attached True if the Syn-Apps IP Device has a clock attached. This is not editable. GPIO See Activating Emergency Alert section for more detail. GP Input 0 and GP Input 1 Used with Sensor Contact Closure use case scenarios. See Sensor Contact Closure Configuration in the Paging Relay Admin Guide. Activate Used to select the Emergency Alert group type that the Paging Relay belongs to for use with the GPIO. See Sensor Contact Closure Configuration in the Paging Relay Admin Guide. The Syn-Apps device Control Port field is set to 6789 by default. Generally this will not need to be changed. If the control port must be changed, then it must be the same for all Syn-Apps Paging Relays and IP speakers in use. To change the Control Port SA-Announce uses to send commands, edit the field at the bottom of the page and press the Save button to set the new control port. The Firmware Update fields can be used with Syn-Apps IP Speakers or Paging Relays. Provide a valid firmware image name and the IP address of the TFTP server it exists on. Press the Update button to begin the update on all registered devices that match the type of firmware specified.

185 Syn-Apps Paging Relay Configuration Supported Paging Relays SA-Announce supports all Syn-Apps Paging Relays with firmware version or greater. However, Syn-Apps recommends running the latest firmware version, which can be found on our Documents & Downloads page on the Syn-Apps web site. Refer to the Paging Relay Admin Guide for instructions on how to register and configure the device.

186 Syn-Apps Desktop Notification Client Configuration Part 21

187 Syn-Apps Desktop Notification Client Configuration Syn-Apps Desktop Notification Client Configuration Settings >> IP Endpoint Setup >> Desktop Client The Settings >> IP Endpoint Setup >> Desktop Client tab is used to view and configure the desktop notification client parameters. For information on adding desktop notification clients to an SA-Announce notification group, see the Desktop Clients section of this manual. Each Syn-Apps Desktop Notification Client used with the system must be registered in the Settings >> IP Endpoint Setup >> Desktop Client tab. To edit the following information for each of the Desktop Clients, press the Edit link on the device line item to begin editing the row. Then press the Update link on the device line item to save. Click the Delete link on the device line item to delete the endpoint. Desktop Client Setting Description Name Enter a name for the client. The default name will be the clients' user name. Description Enter a description for the client. The default description will display the device type. A best practice method is to add the devices' location in the description field. Version The version of the Syn-Apps Desktop Notification Client. This is not editable. IP Address The IP Address of the Syn-Apps Desktop Notification Client. This is not editable. Port The client listen port. This is not editable. Last Heart Beat The date and time of the last registration or heartbeat message from the SynApps IP Device. This is not editable. D.N. Enter a directory number for the client (Talk-Back only), this will be used for holler (intercom) addressing in a future release.

188 SA-Announce User Guide Supported Desktop Notification Clients The Syn-Apps Desktop Client runs on both Windows and Mac platforms. Syn-Apps Desktop Notification Client integrates with SA-Announce version 8.0 and higher. Refer to the Syn-Apps Desktop Notification Client User Manual for complete installation and configuration details Syn-Apps Desktop Notification Client Setup The following sections describe the installation requirements and installation of the Desktop Notification Client Windows Requirements DNC Requirements Running on Windows PC Platforms Windows Version XP, 2003, Vista, 2008, Win-7 (x86 or x64)..net 4.5 or greater. A Windows audio device. SA-Announce Version: 8.0+ Administrative Access to client machine. Network Requirements Http Port: The DNC runs on port 8282 by default. The SA-Announce server will need unrestricted access to the DNC on this port. Voice Ports: The DNC RTP port range will need to be accessible by SAAnnounce ( ). Multicast: The DNC will need to be connected to a multicast enabled network if SA-Announce is configured for multicast. Refer to the Syn-Apps Desktop Notification Client Install & User Guide for complete installation details Macintosh Requirements DNC Requirements Running on Macintosh Platforms MAC OS X 10.4 and greater Java installed 64-bit OS SA-Announce Version: 8.0+ MAC audio enabled Administrative access to client machine Network Requirements Http Port: The DNC runs on port 8282 by default. The SA-Announce server will need unrestricted access to the DNC on this port. Voice Ports: The DNC RTP port range will need to be accessible by SAAnnounce ( ).

189 Syn-Apps Desktop Notification Client Configuration 189 Multicast: The DNC will need to be connected to a multicast enabled network if SA-Announce is configured for multicast. Refer to the Syn-Apps Desktop Notification Client Install & User Guide for complete installation details DNC Configuration The Desktop Notification Client can be configured in two ways: Automatic and Manual configuration. Automatic Configuration is performed on the SA-Announce server and propagates to all of the Desktop Notification Clients in your network. This creates a single, secure, centralized location for provisioning the Desktop Notification Clients on your network. Automatic Configuration requires all of the Desktop Notification Clients to have the same configuration settings. The second configuration option is to perform a Manual Configuration on each Desktop Notification Client. This is less convenient to manage, but allows for unique customization of each Desktop Notification Client Automatic Configuration The Desktop Notification Client offers the ability for SA-Announce to automatically configure the Desktop Notification Client. There is no need to manually configure the Desktop Notification Client. When the Desktop Notification Client runs for the first time, it will attempt to retrieve configuration parameters from the SA-Announce server automatically. The SA-Announce server becomes a central location for configuring all of the Desktop Notification Clients in your network. There are two requirements for Automatic Configuration : 1. The IP Address of SA Announce must be made available to the Desktop Notification Client. 2. An administrator must define configuration parameters for the Desktop Notification Clients using the SAAnnounce web interface. SA-Announce IP Address To provide the SA-Announce IP Address to the Desktop Notification Client there are three options: 1. DHCP - A DHCP server may be configured to serve up the SA-Announce IP address using Option-72. The Desktop Notification Client will automatically poll the DHCP server for the SA-Announce IP address on startup. Using this option makes configuration completely automatic. When the Desktop Notification Client first starts up, it will obtain the SA-Announce IP address from the DHCP server and then register with SA-Announce automatically. 2. Installation - During installation of the Desktop Notification Client, the installer allows for the SAAnnounce IP address to be specified on the command line. An administrator can use this feature to write an install script that includes the SA-Announce IP address. This enables an administrator to mass deploy the Desktop Notification Client with the SA-Announce IP address. Please see Installation >> Setup Wizard in the Syn-Apps Desktop Notification Client Install & User Guide for more details on using the command line option. 3. Manual - After installation, users can visit the DNC Settings page (using the icon in the UI) and enter the IP address of SA-Announce manually (screenshot below). Once the Desktop Notification Client connects to SA-Announce, SA-Announce is then capable of sending configuration parameters to the Desktop Notification Client. This approach is not preferred because it involves a manual step of entering the IP address.

190 190 SA-Announce User Guide To verify whether or not the DNC's manual configuration was successful, click on the Open SA-Announce button. If required, login using the appropriate credentials. From the SA-Announce UI, navigate to Settings >> IP Endpoint Setup >> Desktop Clients tab. Properly registered DNC's will automatically populate the table (shown below). Verify the correct user's DNC is connected to SA-Announce. Another way to view the configuration success is to view the DNC connection status found in the DNC GUI bottom-left corner. If connected, the globe will glow green and blue and state Connected to SA-Announce: If it is not connected, the globe will be gray and state Not Connected:

191 Syn-Apps Desktop Notification Client Configuration 191 Configuration Using SA-Announce Web-Interface After the DNC has been configured, navigate in the SA-Announce UI to Services >> Broadcast Services >> Advanced. Use the Select a Setting dropdown list and choose from the available Desktop Client settings. Click the Save button. The Advanced Settings page allows administrators to update DNC settings at any time. The DNC's do not need to be restarted to reflect the new setting changes because the SA-Announce server dynamically pushes the settings to the DNC.

192 192 SA-Announce User Guide Manual Configuration The DNC Settings page allows a local user to manually configure their DNC settings. However, it is recommended to use Automatic Configuration because configuration is easier, more secure, centralized and concurrent across all Desktop Notification Clients within the network. Unique Settings Manual configuration is required if each DNC installation requires unique settings. If an administrator wishes to allow individual users the ability to customize the DNC notifications' behavior(s), then manual configuration must be performed individually on each DNC. Automatic Setup requires all of the DNC's on a network to be configured the same. IP Restraints Manual configuration is required when the Desktop Notification Client does not automatically detect the IP address of SA-Announce. The Desktop Notification Client will be unable to automatically detect the IP address if DHCP is not enabled, or when the IP address was not specified during installation. In either case, a user must manually enter the IP address of the SA-Announce on the DNC Settings Page. Manually type the SA-Announce Server IP into the corresponding text box. Click the Save Changes button. To verify whether or not the DNC's manual configuration was successful, click on the Open SA-Announce button. If required, login using the appropriate credentials. From the SA-Announce UI, navigate to Settings >> IP Endpoint Setup >> Desktop Clients tab. Properly registered DNC's will automatically populate the table (shown below). Verify the correct user's DNC is connected to SA-Announce. Another way to view the configuration success is to view the DNC connection status found in the DNC GUI bottom-left corner. If connected, the globe will glow green and blue and state Connected to SA-Announce: If it is not connected, the globe will be gray and state Not Connected:. Once the DNC can communicate with SA-Announce, SA-Announce may begin sending configuration parameters to the DNC automatically.

193 Syn-Apps IP Speaker Configuration Part 22

194 SA-Announce User Guide Syn-Apps IP Speaker Configuration Settings >> IP Endpoint Setup >> Syn-Apps IP The Settings >> IP Endpoint Setup >> Syn-Apps IP tab is used to view and configure Syn-Apps IP Speaker parameters. For information on adding Syn-Apps IP Speakers to a SA-Announce notification group, see the Group IP Speakers section. Each Syn-Apps IP speaker to be used with the system must be registered. Once the speaker has registered it will appear in the Syn-Apps IP area on the Settings >> IP Endpoint Setup >> Syn-Apps IP tab. For details on Syn-Apps IP speaker registration see Syn-Apps IP Speaker Setup. To edit the following information for each of the IP Speakers, press the Edit link on the device line item to begin editing the row. Then press the Update link on the device line item to save. IP Speaker Setting Description Name Enter a name for the Speaker. The default name will be the Speakers' MAC address. Description Enter a description for the Speaker. The default description will display the device type, Speaker. Best practice method is to add the devices' location in the description field. Firmware The firmware version of the Speaker. This is not editable. D.N. Not applicable for Avaya.

195 Syn-Apps IP Speaker Configuration 195 Vol The volume for this speaker (0-100, default 80). Mic Not applicable for Avaya. Selected Device Detail To view extended details select the device row in the table. The Selected Device Detail panel to the right will be populated. Model The Syn-Apps IP speaker device model name. This is not editable. IP Address The IP address of the Syn-Apps IP speaker device. This is not editable. Last The date and time of the last registration or heartbeat message from the SynApps IP speaker device. This is not editable. Clock Attached True if the Syn-Apps IP speaker device has a clock attached. This is not editable. GPIO Note: This setting is not available for Syn-Apps IP Speak ers at the time. GP Input 0 or GP Input 1 Each GPIO input can be set to activate an intercom to a selected phone with (talk back speaker enabled) or used to activate an Emergency Alert group. The GPIO button will both activate and deactivate the selected function. Activate Use the Activate dropdown list to select a notification to activate. Phone Filter Use the Phone Filter text box to quickly filter through phone numbers in the available Dest. Phone list. Dest. Phone Use the Dest. Phone dropdown list to select a phone to send the notification to. Users can 1) Activate a Paging Group or 2) Activate a dedicated two-way intercom functionality for speakers with connected microphones. Additional Settings Control Port The Syn-Apps device Control Port field is set to 6789 by default. Generally this will not need to be changed. If the Control Port must be changed, then it must be the same for all Syn-Apps Paging Relays and IP Speakers in use. To change the Control Port SA-Announce uses to send commands, edit the field at the bottom of the page and press the Save button to set the new control port. Firmware Update: TFTP The Firmware Update fields can be used with Syn-Apps IP speakers or Paging IP Address Relays. Firmware Update: Firmware Image Provide a valid firmware image name and the IP address of the TFTP server it exists on.

196 SA-Announce User Guide Supported Syn-Apps IP Speakers SA-Announce supports all Syn-Apps (CyberData V2) IP Speakers with firmware version or greater Syn-Apps IP Speaker Setup This section describes the configuration of Syn-Apps IP Speakers. Auto-Registration Setup: The new Syn-Apps IP Speakers can be easily configured to auto register with SA-Announce. Plug the Syn-Apps IP speaker into a PoE (power over ethernet) switch or router. DHCP option 72 is required for auto-registration to SA-Announce and is the recommended configuration option. Set DHCP option 72 to the IP Address of the SA-Announce server: If using routers to serve DHCP, add the Option 72 command to the scope that is providing the Paging Relay with IP address information. DHCP Configuration ip dhcp pool Voice network default-router option 150 ip dns-server option 72 ip lease Consult the MSDN (Microsoft Developer Network) for instructions on configuring DHCP Servers on supported versions of Windows.

197 Syn-Apps IP Speaker Configuration 197 Manual Registration Setup: If DHCP cannot be used or option 72 cannot be set then the speaker must be manually registered with SAAnnounce. If DHCP can not be used or option 72 can not be set, the speakers must be manually registered with SAAnnounce. To manually register a Syn-Apps IP Speakers, open a web browser on the SA-Announce host machine and enter the IP Speakers' default IP address of The default credentials are: User Name = admin Password = admin In the IP Speaker firmware, navigate to the Device Config tab. Enter the SA-Announce server IP address in the SA-Announce IP Address** field. Save the changes. Next, navigate to the Networking tab. Click the Static radio button and enter the IP Address for the IP Speaker. Populate the remaining fields and save the changes. The DNS Server fields will accept if necessary. Reboot the IP Speaker by clicking the Reboot button at the bottom of this page.

198 198 SA-Announce User Guide After the system reboots, the IP speaker information should be available in the SA-Announce user interface on the Settings >> IP Endpoint Setup >> Syn-Apps IP tab. The IP Speaker web interface is now available by browsing to the Static IP Address configured in the previous section.

199 Legacy Algo Speaker Configuration Part 23

200 SA-Announce User Guide Legacy Algo Speaker Configuration Settings >> IP Endpoint Setup >> Static Streams The Settings >> IP Endpoint Setup >> Static Streams page is used to configure SA-Announce with the legacy Algo speakers. The Algo speakers Multicast Settings must first be configured in order to function properly with SA-Announce. See Legacy Algo Speaker Setup for details. Multicast is required from the SA-Announce application server to the Algo speakers. Configure Legacy Algo Speakers in the SA-Announce Static Stream s tab

201 Legacy Algo Speaker Configuration Configuring Multicast in the Algo Speaker control panel Legacy Algo IP Speaker Setting Description Name (Description) Enter a descriptive name for the speaker in this textbox. Multicast IP Type the Multicast IP address in this textbox. This IP address is found in the Algo User Interface >> Zone Configuration textbox. Port Type the Port number in the Port textbox. This Port is found in the Algo User Interface >> Zone Configuration textbox. The Port is the number followed by the colon in the Zone Configuration Multicast IP Address. For example: "XXX.X.X.XX: 50006" is the Port number. Buttons Add Use the Add button to add the speaker to the Selected list on the right-side. Remove To remove a speaker, click on the speaker's name from the Selected List. Once highlighted, use the Remove button. Update To update Speakers Name, Multicast IP, or Port, click on the speaker from the Selected List. Its information will populate in the Name/Multicast IP/Port fields on the left. Update the information and click the Update button to save changes. 201

202 SA-Announce User Guide Legacy Algo Speaker Setup This section describes how to configure multicast settings for legacy Algo speakers with SA-Announce. These settings must be configured prior to registering the legacy Algo speakers with SA-Announce. See Algo Speaker Configuration for details on adding these groups to the SA-Announce user interface. 1. First, navigate to the web page control panel of the Algo speaker. To do so, use a web browser and type the IP Address of the Algo speaker. 2. Next, login using the default credentials: User Name = algo Password = algo 3. Select the Basic Settings >> Multicast button. 4. On the Multicast Settings page, select the Multicast Mode >> Master/Sender radio-button. 5. Obtain the Multicast IP Address and Port number from the Zone Definition textbox. Use this information to configure the legacy speaker with SA-Announce using the Static Streams page. 6. Press the Save Settings button.

203 AND IP Speaker Configuration Part 24

204 SA-Announce User Guide AND IP Speaker Configuration Settings >> IP Endpoint Setup >> Syn-Apps IP The Settings >> IP Endpoint Setup >> Syn-Apps IP tab is used to view and configure AND IP speaker settings. For information on how to add AND IP speakers to an SA-Announce notification group, see the IP Speakers section. Each AND IP speaker to be used with the system must be registered. Once the AND IP speaker has registered it will appear in the Settings >> IP Endpoint Setup >> Syn-Apps IP tab. For details on AND IP speaker registration see AND IP Speaker Setup. To edit the following information for each of the speakers, press the Edit link on the device line item to begin editing the row. Then press the Update link on the device line item to save. AND IP Speaker Setting Description Name Enter a name for the AND IP speaker. The default name will be the Speakers' MAC address. Description Enter a description for the Speaker. The default description will display the device type, Speaker. Best practice method is to add the devices' location in the description field. Firmware The firmware version of the Speaker. This is not editable. D.N. Not applicable for Avaya. Vol The volume for this speaker (0-100, default 80). Mic Not applicable for Avaya.

205 AND IP Speaker Configuration 205

206 206 SA-Announce User Guide Selected Device Detail To view extended details select the device row in the table. The Selected Device Detail panel to the right will be populated. Model The AND IP speaker device model name. This is not editable. IP Address The IP address of the AND IP speaker device. This is not editable. Last The date and time of the last registration or heartbeat message from the AND IP speaker device. This is not editable. Clock Attached True if the AND IP speaker device has a clock attached. This is not editable. GPIO GP Input 0 or GP Input 1 Each GPIO input can be set to activate an intercom to a selected phone (talk back speaker only) or to activate an emergency alert group. The GPIO button will both activate and deactivate the selected function. Activate Use the Activate dropdown list to select a notification to activate. Phone Filter Use the Phone Filter text box to quickly filter through phone numbers in the available Dest. Phone list. Dest. Phone Use the Dest. Phone dropdown list to select a phone to send the notification to. Users can 1) Activate a Paging Group or 2) Activate a dedicated two-way intercom functionality for speakers with connected microphones. Additional Settings Control Port This is feature is only available to Syn-Apps IP speakers. It is not applicable to AND IP speakers. Firmware Update: TFTP IP Address This is feature is only available to Syn-Apps IP speakers. It is not applicable to AND IP speakers. Firmware Update: Firmware Image This is feature is only available to Syn-Apps IP speakers. It is not applicable to AND IP speakers.

207 AND IP Speaker Configuration 207 The Control Port field is not applicable to AND speakers. The control port is always HTTP port 80. The Firmware Update field is also not applicable to AND speakers. AND IP Speaker firmware must be updated using the ipspeaker.cfg file.

208 SA-Announce User Guide Supported AND IP Speakers SA-Announce supports all AND IP Speakers with firmware version 796 or greater AND IP Speaker Setup This section describes the configuration of AND IP Speakers. Auto-Registration Setup: The new AND IP Speaker can be easily configured to auto register with SA-Announce. Plug the AND IP speaker into a POE (power over ethernet) switch or router. DHCP option 72 is required for auto-registration to SAAnnounce and is the recommended configuration option. Set DHCP option 72 to the IP Address of the SA-Announce server: If using routers to serve DHCP, add the Option 72 command to the scope that is providing the AND IP Speaker with IP address information. DHCP Configuration ip dhcp pool Voice network default-router option 150 ip dns-server option 72 ip lease Consult the MSDN (Microsoft Developer Network) for instructions on configuring DHCP Servers on supported versions of Windows. Manual Registration Setup: If DHCP cannot be used or option 72 cannot be set then the speaker must be manually registered with SAAnnounce. Refer to the manufacturer for technical support on manually setting a static IP address on the AND IP speakers.

209 AND IP Speaker Configuration 209 AND IP Speaker Web Page: Once the speaker has registered with the SA-Announce server, (see above, setting DHCP option 72), find its IP address by navigating in the SA-Announce user interface to Settings >> IP Endpoint Setup >> Syn-Apps IP. Click on the devices' IP address in the Selected Device Detail column to be directed to the AND web interface:

210 210 SA-Announce User Guide

211 Atlas IP Speaker Configuration Part 25

212 SA-Announce User Guide Atlas IP Speaker Configuration Settings >> IP Endpoint Setup >> Syn-Apps IP The Settings >> IP Endpoint Setup >> Syn-Apps IP tab is used to view and configure Atlas IP speaker settings. For information on how to add Atlas IP speakers to an SA-Announce notification group, see the IP Speakers section. Each Atlas IP speaker to be used with the system must be registered. Once the Atlas IP speaker has registered it will appear in the Settings >> IP Endpoint Setup >> Syn-Apps IP tab. For details on Atlas IP speaker registration see Atlas IP Speaker Setup.

213 Atlas IP Speaker Configuration 213 To edit the following information for each of the speakers, press the Edit link on the device line item to begin editing the row. Then press the Update link on the device line item to save. Atlas IP Speaker Setting Description Name Enter a name for the Atlas IP speaker. The default name will be the speakers' MAC address. Description Enter a description for the speaker. The default description will display the device type, speaker. Best practice method is to add the devices' location in the description field. Firmware The firmware version of the speaker. This is not editable. D.N. Enter a directory number for the speaker (Talk-Back only), this will be used for Holler (intercom) addressing. Vol The volume for this speaker (0-100, default 80). If the speaker volume is set to 0, the groups volume setting will be used (Create Edit Groups, general tab). Mic The microphone gain for this speaker if it is a talk-back model (10-100, default 40). Selected Device Detail To view extended details select the device row in the table. The Selected Device Detail panel to the right will be populated. Model The Atlas IP speaker device model name. This is not editable. IP Address The IP address of the Atlas IP speaker device. This is not editable. Last The date and time of the last registration or heartbeat message from the Atlas IP speaker device. This is not editable. Clock Attached True if the Atlas IP speaker device has a clock attached. This is not editable. GPIO GP Input 0 or GP Input 1 Each GPIO input can be set to activate an intercom to a selected phone (talk back speaker only) or to activate an emergency alert group. The GPIO button will both activate and deactivate the selected function. Activate Use the Activate dropdown list to select a notification to activate. Phone Filter Use the Phone Filter text box to quickly filter through phone numbers in the available Dest. Phone list. Dest. Phone Use the Dest. Phone dropdown list to select a phone to send the notification to. Users can 1) Activate a Paging Group or 2) Activate a dedicated two-way intercom functionality for speakers with connected microphones. Additional Settings Control Port This is feature is only available to Syn-Apps IP speakers. It is not applicable to Atlas IP speakers. Firmware Update: TFTP IP Address This is feature is only available to Syn-Apps IP speakers. It is not applicable to Atlas IP speakers. Firmware Update: Firmware Image This is feature is only available to Syn-Apps IP speakers. It is not applicable to Atlas IP speakers.

214 SA-Announce User Guide Supported Atlas IP Speakers SA-Announce supports all Atlas IP speakers Atlas IP Speaker Setup This section describes the configuration of Atlas IP speakers with SA-Announce. Auto-Registration Setup The new Atlas IP speaker can be easily configured to auto register with SA-Announce. Plug the Atlas IP speaker into a POE (power over ethernet) switch or router. DHCP option 72 is required for auto-registration to SAAnnounce and is the recommended configuration option. Set DHCP option 72 to the IP Address of the SA-Announce server If using routers to serve DHCP, add the Option 72 command to the scope that is providing the AND IP speaker with IP address information. DHCP Configuration ip dhcp pool Voice network default-router option 150 ip dns-server option 72 ip lease Consult the MSDN (Microsoft Developer Network) for instructions on configuring DHCP servers on supported versions of Windows. Manual Registration Setup If DHCP cannot be used or option 72 cannot be set then the speaker must be manually registered with SAAnnounce. Refer to the manufacturer for technical support on manually setting a static IP address on the Atlas IP speakers.

215 Atlas IP Speaker Configuration 215 Atlas IP Speaker Web Page Once the speaker has registered with the SA-Announce server, (see above: setting DHCP option 72), find its IP address by navigating in the SA-Announce user interface to Settings >> IP Endpoint Setup >> Syn-Apps IP. Click on the devices' IP address in the Selected Device Detail column to be directed to the Atlas web interface.

216 CyberData IP Speaker Configuration Part 26

217 CyberData IP Speaker Configuration CyberData IP Speaker Configuration Settings >> IP Endpoint Setup >> Static Streams The Settings >> IP Endpoint Setup >> Static Streams page is used to configure SA-Announce with the required CyberData speaker group parameters. The CyberData speaker groups are setup using the CyberData speakers' web page. Use the CyberData Discovery tool to discover the CyberData speakers on the network. After acquiring the speaker IP address, login to the CyberData user interface. The speakers must be setup using multicast groups, MGroup mode, in order to function properly with SA-Announce. See CyberData Speaker Setup for details. Multicast is required from the SA-Announce application server to the CyberData speakers. CyberData Speaker Setting Description Name (Description) Enter a descriptive name for the speakers in this textbox. Multicast IP Type the Multicast IP address in this textbox. Port Type the Port number in the Port textbox. Buttons Add Use the Add button to add the speaker to the Selected list on the right-side. Remove To remove a speaker, click on the speaker's name from the Selected List. Once highlighted, use the Remove button.

218 218 SA-Announce User Guide Update 26.1 To update Speakers Name, Multicast IP, or Port, click on the speaker from the Selected List. Its information will populate in the Name/Multicast IP/Port fields on the left. Update the information and click the Update button to save changes. Supported CyberData Speakers SA-Announce supports a variety of CyberData IP devices. These include but are not limited to: CyberData IP Speaker Model Supported VoIP Ceiling Speaker VoIP Paging Gateway VoIP Multicast Gateway VoIP Loudspeaker Amplifier, PoE VoIP Loudspeaker Amplifier, AC VoIP Loudspeaker Amplifier Wireless VoIP Paging Amplifier VoIP Intercom VoIP 4-Port Zone Controller VoIP Talk-back Speaker

219 CyberData IP Speaker Configuration CyberData Speaker Setup This section describes how to setup CyberData speakers for multicast groups, (MGroups), with SA-Announce. See CyberData IP Speaker Configuration for details on adding these groups to the SA-Announce user interface. Browse to the web page of the speaker. The default credentials are: User Name = admin Password = admin Select the Speaker Setup button. In the Select Speaker Function field, select the 'MGROUPS' radio button. Press the Save Settings button. Next, press the MGROUPS Setup button. Add groups to the speaker by adding a Multicast IP Address, Port, Priority, and Name for the group. Add the same group to all other speakers that are to be part of the group.

220 Valcom IP Speaker Configuration Part 27

221 Valcom IP Speaker Configuration Valcom IP Speaker Configuration Settings >> IP Endpoint Setup >> Valcom The Valcom IP Speaker settings are located at Settings >> IP Endpoint Setup >> Valcom. Valcom firmware version 2.x is recommended because in most cases, the settings will not need to change. Valcom Speaker Setting Description Multicast Control Address Type the Multicast Control Address address in this textbox.. Multicast Audio Address Type the Multicast Audio Address address in this textbox. Port Type the Port number using the Port textbox. Checkboxes & Buttons Save Use the Save button to add the speaker. Enable Valcom Integration Use this checkbox to enable Valcom speaker integration. Valcom Version 2 Use this checkbox if using speaker version 2.x or greater. This setting is enabled by default. Should users use speaker versions 1. x or non-default multicast control and audio addresses, users must match the SA-Announce settings to the Valcom Speaker settings.

222 222 SA-Announce User Guide Valcom VIP-102B Setup Tool System >> Network Settings The Valcom speaker settings are shown in the Valcom VIP-102B IP Solutions tool under the System >> Network Settings option Supported Valcom Speakers SA-Announce supports the entire Valcom IP Speaker platform. These speakers include: Valcom IP Speaker Model Supported Valcom VIP 130-L (one-way outdoor horn) Valcom VIP 402 (lay-in ceiling speaker) Valcom VIP 140 (wall speaker) Valcom VIP 411 DS (wall mount w/ digital clock) Valcom VIP 412 DF (wall surface mount w/ digital clock) Valcom VIP 430 (wall mount talk-back) Valcom VIP 821 (enhanced network trunk port) Valcom VIP 822 (duel enhanced network trunk port) Valcom VIP 824 (quad enhanced network trunk port)

223 Valcom IP Speaker Configuration Valcom IP Speaker Setup This section describes the configuration of Valcom IP Speakers with SA-Announce. For information on how to add these Valcom groups to a SA-Announce notification group, see the Valcom Speaker Integration section. See Valcom IP Speaker Configuration for details on setting up Valcom audio and control addresses and ports. To add Valcom IP speakers to groups for use with SA-Announce first open the VIP-102B IP Solutions Setup Tool from Valcom and scan for the speakers. Select System >> Audio Groups from the main menu bar. A new window will appear. Add a Dial Code, the unique group number, select a Priority and give the group a Name. Press the Add button to add the group to the Valcom system. Next select System >> Audio Group Membership from the main menu bar. Select a speaker group form the Audio Group drop down menu, then add speakers to the group by checking the Device checkbox.

224 224 SA-Announce User Guide The Valcom group can now be used in SA-Announce notification groups and schedules. Add the Dial Code to the Valcom input field of the Legacy IP tab of a notification group. For further instructions, see see the Valcom Speaker Integration section.

225 Alertus Configuration Part 28

226 SA-Announce User Guide Alertus Configuration Settings >> IP Endpoint Setup >> Alertus The Settings >> IP Endpoint Setup >> Alertus tab is used to configure SA-Announce with the required Alertus settings. For information on adding Alertus Beacon Groups to an SA-Announce notification group, see the Beacons section. Alertus Server Configuration The Alertus Server must be network accessible from the SA-Announce server. Port 8280 must be accessible from the SA-Announce server. If a firewall is setup on the Alertus server, port 8280 must allow access to the SAAnnounce server. The Alertus server software configuration must be modified to allow the SA-Announce application to communicate: From the server hosting the Alertus software, edit the AlertusMiddleware.impl.properties file located in the C: \Alertus\conf directory. Change the soap.alertusmiddlewarebasic.allowableips to include the SA-ANNOUNCE IP ADDRESS as shown below: soap.alertusmiddlewarebasic.allowableips = ;[SA-ANNOUNCE IP ADDRESS] If this line does not exist, add it anywhere in the file. Users must restart the Alertus application for this change to take affect.

227 Alertus Configuration 227 Configure SA-Announce for Alertus To setup the Alertus integration, the Alertus Web Service URL must first be configured. Alertus Setup Description Message Duration (Seconds) Type a whole number into the textbox to configure the duration (in seconds) for an SA-Announce alert to remain active on the Alertus device. For groups such as Normal and Text, the Message Duration Setting will be used and the Alertus beacons will carry the message for the specified amount of time. Note: For notification groups such as Emergency Alerts and Schedules, this setting is not used. The Alertus alert will be activated when an Emergency Alert or Schedule is activated in SA-Announce in the usual manner. The Alertus alert is deactivated when the Emergency Alert or Schedule ends in SA-Announce. Alertus Web Service URL Type the URL into the Alertus Web Service URL text box. The URL will be verified. If the URL is valid, the Alertus settings will be extracted for use in SA-Announce. Save Use the Save button to configure your changes.

228 SA-Announce User Guide Supported Alertus Devices SA-Announce supports all Alertus Beacons Alertus Device Setup This section describes how SA-Announce integrates with the Alertus System. SA-Announce can automatically activate Alertus Beacon Groups that have been defined in the Alertus web configuration page, as shown below. Alertus Alert Profiles are also used by SA-Announce. The Alert Profile defines the way Alert Beacons behave during an event. For example, how the lights flash and which sound is played during the event. For proper operation, SA-Announce requires the Alertus system to have at least one alert profile and one beacon group.

229 Everbridge Configuration Part 29

230 SA-Announce User Guide Everbridge Configuration Settings >> IP Endpoint Setup >> Everbridge The Settings >> IP Endpoint Setup >> Everbridge tab is used to configure SA-Announce using the required Everbridge settings. For information on adding Everbridge Scenarios to an SA-Announce notification group, see the Everbridge section. Provide the following Everbridge web service information in the SA-Announce interface: Everbridge Settings Description Web Service URL Enter the Everbridge web service URL in the provided text box. The default URL is User ID Enter the Numeric Everbridge User ID. Organization Name Enter the organizations' Everbridge organization name. Password Enter the organizations' numeric Everbridge password. Press the Save button to save the changes. After pressing Save, the URL will be contacted to check connectivity. If problems are encountered, an error message will appear. The most common cause of an error is due to the server lacking internet connectivity. After setting up the Web Service parameters, enter the Everbridge Scenarios Scenario Id and Description. Press the Add button. The data must be the same as found on the Everbridge Scenario Manager user interface page. See the Everbridge Setup section for details on Scenario Ids and creating new scenarios.

231 Everbridge Configuration Everbridge Setup This section describes how SA-Announce integrates with Everbridge. SA-Announce can automatically activate an SA-Announce notification group using Everbridge Scenarios that have been pre-defined in the Everbridge web configuration page. For proper integration, SA-Announce requires that the Everbridge system have at least one scenario defined. To view currently created Everbridge Scenarios, browse to the Everbridge Management interface Scenario Manager >> Manage Scenario, as shown below. The Scenario Title and Scenario Number are listed here. To create new scenarios in the Everbridge system, first create an unscheduled notification (Send Notification) and then use the Scenario Manager >> Create Scenario to create a scenario using the unscheduled notification.

232 232 SA-Announce User Guide Next, enter the Everbridge Scenario Id and Description in the SA-Announce user interface by navigating to Settings >> IP Endpoint Setup >> Everbridge tab. From the Everbridge user interface, navigate to the Scenario Manager >> Manage Scenario link and locate the Scenario Title and Scenario Number. Enter the exact data from the Scenario Title into the SA-Announce user interface Description field and the Scenario Number into the Scenario Id field. Press the Add button. This process is described in the Everbridge Configuration section.

233 Twitter Configuration Part 30

234 SA-Announce User Guide Twitter Configuration Settings >> IP Endpoint Setup >> Twitter The Settings >> IP Endpoint Setup >> Twitter tab is used to integrate SA-Announce with an organizations' Twitter account. Enter the Twitter user name and password in the provided fields and press the Save button to save changes. After saving the credentials, Twitter is ready to be integrated with SA-Announce Emergency Alert group notifications.

235 Analog Paging System Integration Part 31

236 SA-Announce User Guide Analog Paging System Integration SA-Announce supports all analog paging systems that integrate to Avaya Aura Communication Manager or Avaya IP Office. SA-Announce supports both single and multi-zone systems. To integrate single-zone systems, use the Syn-Apps Paging Relay hardware. Refer to the Paging Relay Configuration and Enable Features using the Syn-Apps Paging Relay sections for more information.

237 Advanced Paging Configuration Part 32

238 SA-Announce User Guide Advanced Paging Configuration This section illustrates the Advanced Network Configuration for Multicast SA-Announce Multicast Router/Switch Configuration Configuring multicast on a network includes: Enabling Multicast Routing on routers, configuring PIM on routed interfaces, and enabling IGMP or CGMP on switches.

239 Advanced Paging Configuration 32.2 Multi-Site Centralized SA-Announce Server 239

240 Troubleshooting Guide Part 33

241 Troubleshooting Guide Troubleshooting Guide This chapter explains the troubleshooting issues that have the highest level of occurrence. At the top level the chapter is divided into functional categories that match the area of the product where problems might occur. For example, Configuration or Broadcaster Service. Each subcategory explains the proper approach to use to troubleshoot the issue. Each subcategory may also contain details of specific known issues and their resolution. Make sure configuration completes successfully when upgrading SA-Announce. It is a common mistake to upgrade SA-Announce and then uncheck the Run Configuration checkbox on the final page of the installation. It is also a good idea to run the configuration utility to try to resolve or expose any major issues. Examples include: admin credentials have changed, database instance is not running or a missing virtual directory. See the Configuration Utility section of the manual for details on running the configuration utility. If a problem arises during configuration, consult the Configuration Issues section of this troubleshooting guide. Problem Categories Overview 1) Installation / Configuration - Consult this section if the installation or configuration fails. Windows Environment Issues - Issues due to the Windows Environment. Installation Issues - Issues encountered during the installation. Licensing Issues - Issues with SA-Announce licensing. Configuration Issues - Issues encountered while running the SA-Announce configuration utility. Web page does not display after the configuration. 2) Web Interface (GUI) - Consult this section if the SA-Announce web interface does not display or functions incorrectly. GUI Log File - Location and description of the GUI log file. Group Creation - Errors creating a group, errors calling a group, IP phones are not listed. Text Messaging - Errors sending text messages using the send a message page. Other - External Phones, Multicast Settings, or GUI graphical issues. 3) Broadcaster Service (Paging) - Consult this section if the broadcaster service fails to start or notifications fail in some manner. Broadcaster Log Files - Location and description of the broadcaster log files. Service Start Issues - Broadcaster service will not start. End Point Command Issues - End points do not respond to the notification commands. Audio Issues - End points respond to notification commands but do not broadcast audio or the broadcast has poor quality. 4) Scheduler Service - Consult this section if the scheduler service fails to start or schedules fail to play.

242 SA-Announce User Guide Installation / Configuration This section describes troubleshooting techniques for issues that commonly occur during the installation and configuration of SA-Announce. The majority of all issues in this section stem from System Requirements not being met in some way. Consult this section if the installation or configuration fails: (a)windows Environment Issues - This subsection describes issues that commonly occur with the application servers Windows environment. (b)installation Issues -This subsection describes issues that commonly occur when installing SAAnnounce. (c)licensing Issues - This subsection describes issues that commonly occur with SA-Announce licensing. (d)configuration Issues - This subsection describes issues that commonly occur when configuring SAAnnounce using the SA-Announce configuration utility.

243 Troubleshooting Guide Windows Env Issues This subsection describes common issues that can occur on the SA-Announce application servers' Windows environment. Refer to Application Server Requirements section of the manual for additional details. Types of Windows issues that can occur include installation and configuration program failure and event log errors. Windows 2003 Common Issues: No known issues at this time. Windows 2008 Common Issues: No known issues at this time. Windows 2012 Common Issues: No known issues at this time.

244 244 SA-Announce User Guide Installation Issues This subsection describes common issues that can occur during the installation of SA-Announce. Consult the Configuration Issues subsection if the SA-Announce configuration utility fails. There are a few common reasons installation issues may occur: 1. The Application Server Requirements are not met. 2. The installation was not performed by an administrator. 3. The application installer, SA-Announce.exe, is a bad version or possibly corrupt. This occurrence is rare Licensing Issues This subsection describes issues that commonly occur with SA-Announce licensing. The SA-Announce license must exist in the program base directory (C:\Program Files\SynApps\SA-Announce\) as Syn-Apps.license. If no license exists there, the configuration utility will be pre-empted by a license file selector. Configuration cannot run without a valid license file. Common Licensing Issues: 1) No License in Base Directory: Make sure the Syn-Apps.license exists in the program base directory. Syn-Apps.license.txt will not be seen as a license. 2) Using an Inactivate Version of a Previously Activated License: If a license is activated, the inactivate license in the program base directory is replaced with the activate license. In many cases, customers change SA-Announce servers and try to use the same license they were originally sent. This will not work. A new license needs to be obtained from Syn-Apps Support. 3) Licensed Phone Count Exceeded: a) Phones Total Licensing Model: If the licensed phone count is exceeded in this licensing model then SA-Announce sees more devices on the configured Avaya Aura Communication Manager than the license allows. Any other device or phone on the Avaya Aura Communication Manager will be counted towards the licensed phones. Removing unused devices in the Avaya Aura Communication Manager, followed by refreshing the data will update the count. To refresh the data, navigate to: SA-Announce Services >> Broadcast Services >> Service >> Refresh Data. b) Phones Used Licensing Model: If the licensed phone count is exceeded in this licensing model, the application could become unresponsive. Devices must be removed from notification groups until the unique devices used in all groups meet the requirements.

245 Troubleshooting Guide Configuration Issues This subsection describes common issues that can occur when running the SA-Announce Configuration utility. Consult this subsection when configuration fails or the web site fails to open properly. For basic information on running the SA-Announce configuration utility see the Configuration Utility section of the manual. The SA-Announce configuration utility can fail for a number of reasons. Most errors will be shown to the user configuring the product as a text pop when the error occurs. All errors will be listed in the SA-Announce configuration log file. The majority of all configuration issues stem from System Requirements not being met in some way. The SA-Announce configuration log file is located at C:\Program Files\Syn-Apps\SAAnnounce\Configuration\log.txt. By default the log file will only show errors. The logging level for this file is controlled by the "Web Site Logging Level" setting. Errors During Configuration: Common failures that occur while running the configuration utility are listed below by the configuration page they occur on: 1) License Not Found: If the license selector appears then no license exists in the program base directory. Select one using the provided interface or install the license manually as described in Licensing Issues. 2) Application Server Credentials: This user must be an administrator of the system (local administrator account recommended). 3) Database Instance: The Database configuration page requires the user to enter a valid local database instance name (SynApps default). If the application server does not have internet access then SQLExpress will not have been automatically downloaded and installed. In this case, the server will likely not have a SYNAPPSENT database instance and an error will occur at this point in configuration. Common solutions include: 1) SQL does Not Exist on the Application Server: Install SQL on the application server, note the instance name you create. SQL mixed mode authentication is required. 2) SQL Exists on Application Server: If the server already has some form of SQL installed, then a valid instance name must be entered. Common instance names include SYNAPPSENT for SQL instances installed by SA-Announce, SQLExpress for SQLExpress manual installs, and Blank for SQL Enterprise installs. There is always a chance that the user defined some instance name during manual configuration of SQL. This instance name must be used or another instance must be created. The instance name can generally be determined by going to the Windows services panel and looking for services such as MSSQL$SYNAPPS or SQL Server (SYNAPPS). In both cases, SYNAPPS is the instance name. If you have the right instance name and issues persist, chances are the SQL service is not running.

246 246 SA-Announce User Guide Errors After Configuration: Common issues that occur after running the configuration utility are listed below: 1) Web Site Failure: If the web site fails to display properly after configuration completes, the error given in the browser should help to determine the problem. It is also a good idea to check the configuration log file for errors that may have occurred when creating the SA-Announce virtual directory. Common issues are listed below: (a) IIS not installed or default web site not running: IIS must be installed and the default web site must be running on Port 80. (b) Virtual Directory missing or not configured: Verify the Virtual Directory has been created at IIS Management >> Web Sites >> Default Web Site >> SA-Announce. 2) Service will not start: If an audio notification group has been created and the service will not start, see the Service Start Issues subsection. If errors occur in these areas, call Syn-Apps Technical Support at , Option 2.

247 Troubleshooting Guide Upgrade Procedure Troubleshooting This section expands on the Upgrading SA-Announce section process in greater detail. This section is primarily for users who meet the following criteria prior to upgrading to a newer version of SAAnnounce: 1. Syn-Apps Core Component is installed but should not be installed prior to upgrading. 2. SQL ENT Instance is not installed but should be installed prior to upgrading. Users must be logged onto the application server as an administrator, (local or domain), to properly complete the installation.direct internet access is required for downloading the OS updates and the new SQL 2008 R2 SP1 (SYNAPPSENT) instance. Update Procedure Prerequisites Description 1. Check the OS KBs (Knowledge Base articles) to make sure the OS meets minimum specs for the upgrade or visit the System Requirements section. 2. Verify the server SA-Announce is running on has direct internet access. 3. Mixed Mode Authentication (SQL and Windows) is required for the target SQL server instance. 4. Recommended: Backup SA-Announce prior to moving forward.visit the Backup and Restore KB for additional information. Open Add/Remove Programs Navigate to Start >> Control Panel >> Add/Remove Programs. Syn-Apps Core Components **Note: Verify Syn-Apps Core Component is NOT installed. Note: If it Core Component is installed, navigate com/support/kb and use the following KB Article Install SQL 2008 R2 Manually KB. Run the Upgrade Utility OR Download the Universal 1. The SA-Announce Update Utility is recommended. Launch the SAAnnounce Upgrade Utility by navigating to Start >> search for SA-Announce Upgrade Utility. Continue through the upgrade screens.

248 248 SA-Announce User Guide Installer Searching for the SA-Announce Update utility using Window s Alternatively, download the SA-Announce Universal Installer from Start the Installer Start the SA-Announce setup program and go through the installation process, as directed in the Installation Procedure section. Once the installation is complete, SA-Announce will continue to the SA-Announce Configuration. Note: Windows Installer 4.5 Powershell 2.0 and.net may be installed by the SA-Announce upgrade, if it's not already installed. An automatic OS reboot will occur for Windows Installer 4.5, but should not for 3.5 and.net.

249 Troubleshooting Guide Verify SQL ENT Instance Installed 249 Prior to running the SA-Announce configuration, verify the SQL Instance. To verify the SQL Installation: 1. Launch Start >> Run >> services.msc. 2. Scroll down to find the SQL Server (SYNAPPSENT) service If SQL Server 2008 R2 SP1 SYNAPPSENT instance installed by SAAnnounce, continue with the SA-Announce Configuration. If the SYNAPPSENT instance is not installed, then the existing SQL will have to be reconfigured. See the following section, Reconfigure SQL Server, for details. 1. The SQL Installation w indow w ill be visible during installation, provided the installation runs properly..

250 250 SA-Announce User Guide 2. SA-Announce update process autom atically installing SQL Server 2008 R2. 3. SQL Dow nload Com plete - SA-Announce is ready to install

251 Troubleshooting Guide Reconfigure SQL Server The following steps are only required if the SQL Server SYNAPPSENT Service was not installed correctly during the update procedure. Verify Local SQL Instance on the SA-Announce Server meets the following requirements: Verify Local SQL Instance meets the following: SQL 2005/2008 R1/2008 R2 Open SQL Management Studio: Start >> Programs >> Microsoft SQL Server 200x >> SQL Management Studio. Mixed Mode Authentication Enabled Verify Mixed Mode Authentication is selected. 1. Right-click on the SQL Server Instance at the top of the left pane. 2. Select Properties. 3. Click Security to verify Server Authentication is SQL Server and Windows Authentication mode. 4. Restart of Microsoft SQL Server Service will be required if changed.

252 252 SA-Announce User Guide SQL Server Configuration Manager is configured to accept TCP connections Valid SQL User Rights Verify the user performing the upgrade has appropriate SQL rights. Valid SQL SA Account Password The SA-Announce upgrade will prompt for the SQL SA Account Password. If the SA password is not known, update the password.

253 Troubleshooting Guide Web Interface (GUI) This section will explain troubleshooting techniques for common problems that can occur with the SA-Announce web management interface (GUI). The SA-Announce web management interface (GUI) facilitates control of the SA-Announce settings and group configurations. Consult this section if you experience problems while using the GUI. If the GUI will not load properly or has never loaded properly see the Web Site Failure portion of the Configuration Issues subsection. There are four subsections that divide the major categories of the web interface (GUI), each subsection is explained briefly below: 1. GUI Log File: This subsection describes the GUI log file which is used to troubleshoot problems in this section. 2. Group Creation: This subsection describes common issues that occur when trying to create notification groups in SA-Announce. 3. Text Message: This subsection describes common issues that occur when sending text messages via the GUI. 4. Other: This subsection describes common issues that occur in other areas of the GUI.

254 254 SA-Announce User Guide GUI Log File This subsection describes the GUI log file. Consult this subsection when experiencing GUI issues, most GUI errors will appear in the log. Everything to do with the website is contained in this log so API logging and some paging logging is also contained in this log file. Consult the Broadcaster Service section first for paging issues. The log file to consult for GUI issues is located at C:\Program Files\SynApps\SA-Announce\Log.txt. In most cases, errors generated in the GUI will be shown to the user of the GUI as red text as well as being logged. It is important to note that major web site errors will only be detailed in the web browser when browsing from the application server.

255 Troubleshooting Guide Group Creation This subsection describes common errors that can occur during group creation. Consult this section when problems occur while adding a group, adding IP phones to a group, or if you cannot call a group after adding it. Group is Fast Busy or does not activate If a group was created without error but the group is not active (calling the group yields a fast busy) there a few likely causes: 1) The broadcaster service is not running. Check the status of the SA-Announce Broadcaster Service in the service control manager. 2) The SIP trunk is not configured properly. Check the IP address at which the SIP trunk points and ensure it is the IP address of the SA-Announce server. 3) The dial plan and routing is not configured properly to route calls to the SIP trunk. Review your dial plan to ensure that calls made to the group line numbers can actually be routed to the SIP trunk. 4) The line number for a group might be reserved for some other feature/extension on the Avaya Aura CM already. Page through 'list extension-type' and make sure that the group line number is not reserved by some other object. 5) The group might be in use by someone else, this would usually be indicated by the GUI in the upper right hand corner, if not check the broadcaster logs to see if the group has ever been called. IP Phones Not Visible Listed below are the likely causes of some or all IP phones missing from the IP phones tab: 1. The phone(s) were powered on while the SA-Announce Broadcaster was stopped. Avaya phones will register with SA-Announce as an available endpoint when configured to do so. If the Broadcaster service is not running when a phone is powered on or rebooted, it will fail to register. If the phone settings have been changed, but the phone has not been reset, the details will not appear in SA-Announce because SA-Announce only receives updates about a phone when it is booting up. 2. If all IP phones of a certain model are missing from the IP phones tab, then that model type might not be added to Services >> Broadcast Services >> XML Enabled Phones.

256 256 SA-Announce User Guide Text Message This subsection describes common problems that can occur when sending a text message from the send a message page. When phones fail to receive their text messages or polls please see the Phone Command Issues section as it describes the issues that can occur. Other issues that commonly occur with text messages and polls include the following: 1. Phones do not receive an image with the text message: Only phones that support images will receive images. 2. Text messages only arrive at certain endpoint types: Text messages will only be sent to group devices that can receive text.

257 Troubleshooting Guide Other This subsection describes other common issues that can occur when using the SA-Announce user interface. Multicast Settings: The Settings >> Multicast Settings >> Defaults tab, is where multicast is turned on or off. The defaults tab contains the global settings that are applied to the system. See the Multicast Configuration section of the manual for further details on the multicast settings page. For issues with multicast audio pertaining to notification groups, see the Audio Issues section. As of this release, SA-Announce only supports multicast audio to Avaya IP phones. Unicast audio sent to Avaya IP phones is currently not supported. GUI (Graphical User Interface) Display Issues: If the GUI graphics are misaligned or hard to read it is likely that an unsupported browser is being used to browse the interface. Internet Explorer 7+ is the only fully supported browser, however Firefox and Safari work reasonably well. If using Internet Explorer version 8 and 9, please activate the compatibility mode on the SA-Announce website to resolve graphical issues.

258 SA-Announce User Guide Broadcaster Service This section will explain troubleshooting techniques for common problems that can occur with the SA-Announce Broadcaster Service. The SA-Announce Broadcaster Service controls paging notifications and other features that interact with end points. Consult this section when the broadcaster service fails to start or if end points are not receiving commands or audio. There are four subsections that divide the major categories of the broadcaster service, each subsection is explained briefly below: 1. Broadcaster Log Files: This subsection describes the broadcaster log files which are used to troubleshoot problems in this section. 2. Service Start Issues: Consult this subsection when the SA-Announce broadcaster service fails to start. 3. Phone Command Issues: Consult this subsection when phones are not receiving commands such as phones mute and speaker button lights do not turn on. 4. Audio Issues: Consult this subsection when phones or other endpoints are receiving commands such as lighting the mute and speaker button up, but no audio is heard. Keep in mind that the Scheduler service uses the broadcaster engine to execute schedules. If the broadcaster trace log shows a "Call Info" message for the schedule at the time a schedule was scheduled for activation, then the scheduler did its job and any problem is likely broadcaster related.

259 Troubleshooting Guide Service Start Issues This subsection describes common problems that occur when trying to start the SA-Announce Broadcaster Service. If the service will not start one of the following issues is most likely the cause: 1. Service Install Issues: Open the windows services panel. Find the SA-Announce Broadcaster Service, right click, and select Properties. On the Properties page, select the Log On tab. Verify the account credentials being used are valid by re-typing the password. The account in use must be an administrator of the system. 2. Port in Use: The Broadcaster trace log will show this error near the bottom if port 8087 is in use on the application server. This is the hard coded remote port used by the API. Port 8087 must not be in use on the application server. 3. Other: Check the Broadcaster trace logs for error messages.

260 260 SA-Announce User Guide Endpoint Command Issues This subsection describes common problems that occur when sending phones and other end points commands. Consult this section when end points are not responding properly to the commands they are being sent. For example, when sending a standard audio command to an Avaya IP phone, the phones speaker and mute buttons will light and the phone will play a sound when the command is properly received. If the phone or endpoint does react to the command but audio is not heard, then consult the Audio Issues subsection. When troubleshooting these types of issues, it is important to understand if the issue occurs intermittently or when a single endpoint is tested versus testing many endpoints at the same time. Network configuration issues are generally to blame for intermittent command delivery especially when under a heavy load. When troubleshooting an end point command issue as it pertains to a particular notification group, it is always best to first verify the endpoints in question are actually members of the group. This is a common issue due to the complexity of some integrations. Avaya 96xx IP Phones: There are several basic requirements that must be met in order for Avaya IP phones to receive commands properly. 1. The SA-Announce server must be 'trusted' by the phone. This is configured by a settings file specific to the Avaya system and is detailed in Setup of Avaya 96xx Series Phones and/or Configure AVAYA 9600 and 96x1 Series IP Deskphones. 2. The Avaya IP Phones must be allowed to receive push commands. This is also configured in the settings file and is detailed in Setup of Avaya 96xx Series Phones and/or Configure AVAYA 9600 and 96x1 Series IP Deskphones. 3. The Avaya IP phones must be reachable via Port 80 from the SA-Announce server. Firewalls and security software can impede such connectivity. 4. The Avaya IP phones must be in a 'push-able' state, meaning that the phone is in a state that allows for commands. For instance if an Avaya phone is on, but does not have an extension logged in, it cannot be activated by any commands. Syn-Apps IP Speakers and Paging Relay: Syn-Apps IP Devices must be registered with the SA-Announce server in order to receive commands properly. If the devices are registered they will show in the Syn-Apps IP device table Settings >> IP End Point Setup >> Syn-Apps IP. See Syn-Apps IP Speaker Setup and Paging Relay Setup for setup and manual registration details. There are a few basic requirements that must be met in order for Syn-Apps IP Devices to receive commands properly, they are listed here: 1. Application server must have access to Port 6789 (default) on the devices. 2. Consult broadcaster logs for other errors.

261 Troubleshooting Guide Audio Issues Consult this subsection when end points are reacting properly to commands but no audio is heard, or for poor audio quality issues. Consult the Phone Command Issues subsection if you are not sure if an end point is reacting properly to commands. Multicast Audio: When multicast audio has been enabled and endpoints are responding well to commands, yet not broadcasting audio, the most likely cause is that multicast is not properly enabled. Multicast must be enabled on the network between the SA-Announce server and the endpoints. See the Multicast Requirements section of the manual for more information on configuring multicast on the network. The best way to test multicast connectivity of IP phones is by using the server to phone multicast test under Settings >> Multicast >> Server to Phone Multicast Test. See the Multicast Configuration section of the manual for more detail. Unicast Audio: Unicast audio is not currently supported for Avaya endpoints.

262 SA-Announce User Guide Scheduler Service This section explains troubleshooting techniques for common problems that can occur with the SA-Announce Scheduler service. The SA-Announce Scheduler service controls scheduled notifications. Consult this section when the Scheduler service fails to start or if schedules are not working. The SA-Announce Scheduler service log file is located at C:\Program Files\SynApps\SAAnnounce\SABroadcastScheduler\Log.txt. The Scheduler service logging level is the same as the Broadcaster service logging level, SIGNIFICANT by default and is controlled by the File Minimum Logging Level. Scheduler Service Fails to Start: These are common reasons why the Scheduler Service may fail to start: 1. No Schedules to Serve: There must be a schedule configured or the service will not start. Verify a schedule been created. 2. Service Install Issues: Open the Windows Services panel. Find the SA-Announce Scheduler service, right click, and select Properties. On the Properties page, select the Log On tab. Verify the account credentials being used are valid by re-typing the password. The account in use must be an administrator of the system. 3. Other: Check the Scheduler trace logs for error messages. Schedules Do Not Play: Always verify a schedule is set to play for the day and time being tested. Failing to notice the current day is not selected for the schedule is a common mistake. There are a few other reasons why schedules would fail to play at the scheduled time: 1. Scheduler Service Error: Check the scheduler service logs for any errors. The log is at C:\Program Files\SynApps\SA-Announce\SABroadcastScheduler\Log.txt 2. Broadcaster Service Error: Keep in mind that the Scheduler service uses the Broadcaster engine to execute schedules. If the Broadcaster trace log shows a "Call Info" message for the schedule at the time a schedule was supposed to go off, then the scheduler did its job and any problem is likely broadcaster related. See the Broadcaster Service section in this case. 3. Application Server Clock: Schedules are triggered according to the application servers clock, which should be synchronized using a NTP.

263 Help and Support Part 34

264 SA-Announce User Guide Help and Support The following sections describe the Help section of the SA-Announce user interface. Contact Syn-Apps Technical Support on the web at or call >> Select option Documentation Help >> Manual The Help >> Manual page contains the SA-Announce User Guide in a PDF format.

265 Help and Support Knowledge Base Help >> Request Support >> Knowledge Base The Request Support page contains a Knowledge Base and Prepare Report links. Consult the Knowledge Base tab to find articles pertaining to current issues. Feature requests can also be submitted here. To add Feature Requests, click the Request Support link in the left pane. A new page will open. In the Problem Type drop-down list, select Feature Request. Fill in the remaining required fields and then click the Send Support Request button.

266 SA-Announce User Guide Prepare Report Help >> Request Support >> Prepare Report The Request Support page contains a Prepare Report tab that can be used to generate a Syn-Apps Technical Support request. This is the preferred method to obtain support because all the log files will be automatically sent to Syn-Apps Support. A Support Ticket will be generated for the case. FTP access is required for the process to work automatically. Refer to the Settings to setup the system before requesting Technical Support. To request support please fill out the following information in the interface provided on the page: Prepare Report Field Description Contact Address Enter the address of the person Syn-Apps Support should contact in response to this trouble ticket. Contact Phone Number Enter the phone number of the person Syn-Apps Support should contact in response to this trouble ticket. Detailed Description Enter a detailed description of the problem in the provided text box, provide as much detail as possible as to how the problem is occurring.