SA-Announce Notification Platform User Manual Version for Cisco Version Syn-Apps L.L.C.

Transcription

1 SA-Announce Notification Platform User Manual Version for Cisco 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 13 Part 3 Manual Conventions 17 Part 4 Information Center 19 Part 5 System Requirements 22 1 Application... Server Requirements 23 Window s Server 24 Window s Server 25 Disabling UAC Disabling Public... Firew all 26 Disabling IE... Enhanced Security 26 Creating ASPNET... User Account 27 Verifying IIS... Installation 27 Installing ASP.NET Window s Server 29 2 Cisco... Communications Manager Requirements 30 Com m unications... Manager 3.x 31 Com m unications... Manager 31 Adding Device... Pack 32 Com m unications... Manager Express 33 3 Network... Requirements 34 Firew all Ports Multicast Requirem... ents 35 Part 6 Installation Procedure 37 1 Updating... SA-Announce 38 Part 7 Configuration Utility 41 Part 8 Post Installation Instructions 45 1 Authentication... URL 46 2 Group... Creation 47 3 IP Phone... Services 48 4 Miscellaneous... Info 49 5 Configure... IP Phone Services 50 Notification Group... Directory 51 Web Dialer Directory Phone Message... Brow ser /25/26 - Push-to-Talk Phone Service... URL 55 3

4 4 SA-Announce User Guide Part 9 Initial Application Configuration 58 1 First Time... Login 59 2 Service... Configuration Options 60 Advanced Settings Phone Features Multicast... Configuration 66 4 User Management Troubleshooting... Tests 74 Part 10 Notification Group Configuration 77 1 Notification... Group Types 78 Ad-Hoc Auto Conference Em ergency Alert Holler Norm al RecordNPlay Respond Text Wokkie Tokkie Notification... Group Setup IP Phones Desktop... Clients Cloud... Services External IP Speakers Syn-Apps... Paging Relays Static... Streams Valcom Beacons Mass... Notification 114 Part 11 Creating Emergency Alert Groups 116 Part 12 SA-Announce Scheduler Creating... Schedules Using the Scheduler Tool Editing... A Schedule 128 Editing Associated... Scheduled Events Audio... Upload 130 Custom izing... Audio Feedback 131 Audio File... Descriptions 132 Part 13 Sending A Text Message Message... Browser 137

5 Contents Part 14 SA-Announce Reporting Notification... Activity Report Schedules... Activity Report Text... Activity Report Login... Activity Report Users... Report Notification... Group Report 145 Part 15 Syn-Apps Analytics 148 Part 16 Server Redundancy Creating... A Cluster Creating... Server Groups Associate... Server Groups 157 Part 17 Web Service (API) 160 Part 18 Settings 164 Part 19 AMBER Alert Settings 166 Part 20 Weather Alert Settings Weather... Alert Supported Events 173 Part 21 Background Music Settings 177 Part 22 Syn-Apps Paging Relay Configuration Supported... Paging Relays 181 Part 23 Syn-Apps Desktop Notification Client Configuration Supported... Desktop Notification Clients Syn-Apps... Desktop Notification Client Setup 184 Window s PC... Requirem ents 184 Mac OS Requirem... ents DNC... Configuration 186 Autom atic Configuration Manual Configuration Part 24 Syn-Apps IP Speaker Configuration Supported... Syn-Apps IP Speakers Syn-Apps... IP Speaker Setup 193 Part 25 Legacy Algo Speaker Configuration 197 5

6 6 SA-Announce User Guide 1 Legacy... Algo IP Speaker Setup 198 Part 26 AND IP Speaker Configuration Supported... AND IP Speakers AND... IP Speaker Setup 202 Part 27 Atlas IP Speaker Configuration Supported... Atlas IP Speakers Atlas... IP Speaker Setup 207 Part 28 CyberData IP Speaker Configuration Supported... CyberData Speakers CyberData... Speaker Setup 212 Part 29 Valcom IP Speaker Configuration Supported... Valcom Speakers Valcom... IP Speaker Setup 216 Part 30 Alertus Configuration Supported... Alertus Devices Alertus... Device Setup 221 Part 31 Everbridge Configuration Everbridge... Setup 224 Part 32 Twitter Configuration 227 Part 33 External Phone Integration Supported... Analog Systems Supported... Analog Interfaces 230 Part 34 Busy Detection Options XML... Busy Detection TAPI... Busy Detection 232 Create Application... User 233 Install and Configure... TSP 234 Part 35 Advanced Paging Configuration SA-Announce... Multicast Router/Switch Configuration Multi-Site... Centralized SA-Announce Server SA-Announce... High-Level Protocol Use 238 Part 36 Troubleshooting Guide Installation... / Configuration 241 Window s Env... Issues 241

7 Contents 7 Installation Issues Licensing Issues Configuration... Issues 243 Upgrade Procedure... Troubleshooting 246 Reconfigure... SQL Server Web... Interface (GUI) 252 GUI Log File Group Creation Text Message Other Broadcaster... Service 258 Service Start... Issues 259 Broadcaster... Log Files 260 End Point Com... m and Issues 262 Audio Issues Scheduler... Service Phone... Services 266 Groups Directory Web Dialer API Part 37 Help and Support Documentation Knowledge... Base Prepare... Report 271 7

8 SA-Announce Overview Part 1

9 SA-Announce Overview 1 9 SA-Announce Overview SA-Announce Notification System for Cisco The SA-Announce Notification System is a feature-rich notification system that couples with Cisco Unified Communications Manager 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 Cisco IP Phones, Syn-Apps' Paging Relay, Syn-Apps' IP speakers, Cloud Services, Legacy Overhead Systems, PC Desktops, AND IP speakers, Atlas IP speakers, Algo IP Speakers, CyberData IP speakers, Valcom IP speakers, , Alertus and Everbridge 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 System 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 includes unicast, server sourced multicast, Paging Relay assisted multicast, and phone sourced multicast. Recent feature additions for SA-Announce include: Version / Feature Description SA-Announce Bug Fixes & Software Maintenance General software maintenance, bug fixes, and performance enhancements made to SA-Announce. Regroup Notifier Regroup notifier is now supported by SA-Announce. Facebook Integration Discontinued support for Facebook integration. Updated Service Provider for AMBER Alerts SA-Announce now receives AMBER Alerts from the DOJ (Department of 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 SA-Announce 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

10 10 SA-Announce User Guide 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. Algo Speakers SA-Announce now supports legacy Algo speakers. Support for Algo IP speak ers coming soon! Cisco Phones SA-Announce now supports Cisco phone models 8811, 8831, 8841, 8851, and Paging Relay GPO Paging Relays can now be configured to activate their GPO (general purpose Emergency Alert Activation output) Contact Closure for a specified time on a per-group basis. SA-Announce CUCM 10 SA-Announce now supports CUCM 10.x Cisco Phones SA-Announce now supports Cisco phone models 7821, 7841, 7861, and Paging Relay Syn-Apps' Paging Relay can now be used to activate Emergency Alert groups using the Paging Relay GPIO (general purpose input/output). 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 [email protected] for further details. Active Directory Integration System users can now be authenticated against an Active Directory. SA-Announce Server Redundancy Join multiple SA-Announce servers into a cluster to facilitate automated failover. SA-Announce Weather Alerts Weather Alerts have been updated to use the 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 Assign custom audio files to serve as the notification group opening tone. AND Speaker Text Options Text messages now allow configuration of the text color, scroll speed and number of loops for AND IP speakers. Schedule Time Zone Schedules now have an associated time zone for large deployments. SA-Announce Auto Conference SA-Announce Auto Conference is a new feature that leverages the CUCM Meet Me conference to automatically create and join predefined users to a

11 SA-Announce Overview 11 conference. 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 to target PC desktops with live and stored audio messages, text messages, polls, s 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 you wish to sort on. 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.

12 Application Features Part 2

13 Application Features 2 13 Application Features The SA-Announce notification system offers its users a multitude of features. Define notification groups of end points which you can activate as simply as calling a phone number from any phone on the network including phones. 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 featuring Supervised Delivery. Cisco XML IP phones SA-Announce supports all Cisco XML enabled IP Phones Syn-Apps IP Speakers SA-Announce supports Syn-Apps IP Speakers offering plug and play integration. 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. Algo IP Speakers SA-Announce supports Algo 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. Overhead Paging Systems SA-Announce supports integration with all analog overhead paging systems. Analog Telephones SA-Announce supports external analog telephones. 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.

14 14 SA-Announce User Guide 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 and two way intercom. Stored Audio Stored audio notifications including scheduled events, such as school bells, and emergency alert notifications. Auto Conference Leverages the CUCM Meet Me conference to automatically create and join predefined users to a conference 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. Polls Polls can be sent to users. Response results can be viewed in real-time.

15 Application Features 15 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. Server Redundancy Multiple SA-Announce servers can be clustered together for automatic failover of a notification group. Cloud Services Send notifications to a variety of endpoints including: Apple ios and Android smartdevices, SMS, Instant Messaging using Cisco Jabber and Google Hangouts, and Cisco Digital Media. Dynamic Notification Groups Dynamically associate IP phones, IP speakers and Desktop Clients to a notification group using filters. Group Opening Tone Assign custom audio files to serve as the notification group opening tone. Notify from Speaker Initiate an intercom or emergency alert notification from Atlas IP Speakers. Emergency Alert notification groups Define groups for emergency notifications such as schools on lockdown or tornado warnings. Busy Detection SA-Announce monitors active calls and prevents conversations from being interrupted by paging. External Phones Interface Easily add virtual phones to integrate with overhead paging systems and other external resources. Extension Mobility Support SA-Announce supports extension mobility on CUCM 4/5/6/7/8+ Background Music Service Stream music to Cisco IP phones. A multicast streaming source, such as the Syn-Apps Paging Relay, is required. Enhanced User Management Create user based access with granular permissions and global administration access. Configurable Streaming Model Unicast and 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 broadcast 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.

16 Manual Conventions Part 3

17 Manual Conventions 3 17 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 a 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.

18 Information Center Part 4

19 Information Center 4 19 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.

20 20 SA-Announce User Guide The table below lists the Information Center menu options: Information Center Menu 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 SA-Announce. 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 SAAnnounce 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.

21 System Requirements Part 5

22 22 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. Cisco Communications Manager Requirements The Cisco Communications Manager requirements. Network Requirements Network port usage and multicast setup information.

23 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) or 2008 SP2 (32-bit or 64-bit versions) or 2008 R Note: 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)

24 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. 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 Security Configuration Internet Explorer Enhanced Security Configuration must be unchecked. 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.

25 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, which is 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..net 3.5 and be downloaded here. Note: 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 the following: Disabling IE Enhanced Security Configuration IE Enhanced Security Configuration must be disabled to allow the website to function properly. Creating ASPNET user account Create an ASPNET user account on the SA-Announce application server. 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.

26 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 Launch 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 Configuration 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 the Firewall State to Off. Finalize Changes Click OK. The Public Profile s Firewall should now be off 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.

27 System Requirements Creating ASPNET User Account Creating ASPNET user account To create the ASPNET user account on the SA-Announce application server (required) perform the following: Create ASPNET User Account Description Launch Server Manager Start >> Server Manager or Right-Click on Computer and select Manage. Add New User Under Server Manager expand the Configuration item and expand Local Users and Groups. Right click the Users folder and select New User. Configure New User In the New User dialog create user with User name ASPNET. All other fields are optional. ***Account does not need to be active. Disable account if desired. Click Create Click Create on the New User dialog to create the new user. Verifying IIS Installation 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 SA-Announce 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.

28 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, follow 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.

29 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 The 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.

30 SA-Announce User Guide Cisco Communications Manager Requirements Cisco Unified Communications Manager Support The following table describes the various Cisco Unified Communications Manager (CUCM) requirements: CUCM Requirement Description CUCM Version CUCM 4.x, 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, and Express are supported. Codec Support SA-Announce only supports the G.711 audio codec. IP Phone Web Access Web Access to IP phones must be enabled in Communications Manager. TAPI / TSP Cisco TSP is required if using TAPI busy detection (optional). Connectivity Proper IP access to Communications Manager and IP phones is required Cisco IP Phone Compatibility XML enabled Cisco 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, although some notification groups require activation by an XML enabled phone. Some models do not support images, as denoted below in the 'Img' column: Cisco IP Phone Model XML Img Cisco IP Phone Model Cisco IP Communicator Cisco 7940 Cisco 3905 Cisco 7941 Cisco 6901/6911 Cisco 7941 G-GE Cisco 6921 Cisco 7942 Cisco 6941 Cisco 7945 Cisco 6945 Cisco 7960 Cisco 6961 Cisco 7961 Cisco 7821 Cisco 7961 G-GE Cisco 7841 Cisco 7962 Cisco 7861 Cisco 7965 Cisco 7905 Cisco 7970 Cisco 7906 Cisco 7971 Cisco 7910/7902 Cisco 7975 Cisco 7911 Cisco 8811 Cisco 7912 Cisco 8831 Cisco 7920 Cisco 8841 Cisco 7921 Cisco 8851 Cisco 7925 Cisco 8861 Cisco 7926 Cisco 8941 Cisco 7931 Cisco 8945 Cisco 7935 / 7936 Cisco 8961 Cisco 7937 Conference Station Cisco 9951 XML Img Cisco 9971

31 System Requirements Communications Manager 3.x This section is provided for legacy installations. Communications Manager 3.x is no longer supported by SynApps. If using Communications Manager 3.x, users must be logged into the Syn-Apps application server with the same user name and password that exists on the Communications Manager. This must be the local Administrator account and must have the same password as the Administrator account on Communications Manager 3.x Communications Manager Communications Manager 4.x, 5.x, 6.x, 7.x, 8.x, 9.x, and 10.x require the following: CUCM Requirements Description Authentication URL The Authentication URL on CUCM must be changed to point to SA-Announce. See the Authentication URL section for complete details. AXL Web Service The Cisco AXL Web Service must be enabled on all CUCM listed in SAAnnounce configuration. Note: This setting can be found in Cisco Unified Serviceability, Database and Admin Services. IP Phones Web Access The Web Access setting must be enabled on all IP phones that are to receive SA-Announce notifications. Note: This setting can be edited for a specific phone in the Cisco Unified CM Administration. Navigate to Device >> Phone and search for a device. On the Phone Configuration page in the bottom section - Product Specific Configuration Layout. To change the default for this setting for all newly added IP phones, change the device common profile at ccmadmin - Device >> Device Settings >> Common Profile.

32 SA-Announce User Guide Adding Device Pack This section is not required, as it pertains to Cisco CM 5.x thru 10.x. Use the Syn-Apps device pack to avoid being charged Cisco license units (DLU's) for the virtual devices associated with notification groups on Cisco Unified Call Manager. By default, SA-Announce will add a virtual notification phone for each notification group created. This will consume 2 DLU's because the device type used is a 30-VIP. The Syn-Apps device pack will add a new device to the CUCM system. This allows SA-Announce to add its virtual paging phones as that special Syn-Apps device which consumes 0 DLU's. Two major steps must be done to complete the installation. First, install the Syn-Apps device pack on all Communications Managers in the cluster. After the device pack is successfully installed the CUCMs must be rebooted for the device to become available for use by SA-Announce. The second step is to set SA-Announce to use the new device by altering the registry (see details below). When SA-Announce is set to use the Syn-Apps device, any existing paging groups will become defunct. The old groups will need to be deleted and new ones created in their place. Only create new groups after completing both steps below: Device Pack Setup Description CUCM Device Pack Installation Install the device pack on all CUCM in the cluster. Locate Device Pack Media The Syn-Apps device installation file is located at C:\Program Files (x86) \Syn-Apps\SA-Announce\cmterm-Syn_Apps-sccpsip.cop.sgn. Prepare Device Pack Media The device pack file will need to be placed on an FTP server or CD media in order to supply it as an upgrade file for CUCM. Open CUCM OS Admin At the Cisco Unified OS Administration window, choose Software Upgrades -> Installation/Upgrade Select the Device Pack From the Source drop-down list, choose the source of the COP file. Software Location Source - DVD/CD or Remote Filesystem (FTP server) Directory - / for the root or /path for sub directory Server - IP Address of the ftp server User Name - FTP user name User Password - FTP password Transfer Protocol - SFTP or FTP Click Next Click Next. The Options/Upgrades window appears. Choose File Choose the COP file from the drop-down list and click Next. The system compiles a checksum value. Start Installation Click Save to accept the checksum value and start installation. The installation process can take several minutes. An on-screen log reports status of the installation. Once the COP file is installed the CUCM must be rebooted for the device to become available to SA-Announce. SA-Announce Configuration Configure SA-Announce to use the device pack. Manage Advanced Setting In the SA-Announce web interface, navigate to Services >> Broadcast Services >> Advanced Settings and edit the value usesynappsdevice to be true. Create Groups Create notification groups as usual. Note that any previously existing notification groups are now defunct and will need to be deleted.

33 System Requirements Communications Manager Express Communications Manager Express (CME) requires the following: CME Requirements Description Authentication URL The Authentication URL on CME must be changed to point to SA-Announce. See the Authentication URL section for complete details. CME API Access The following guide should be used to setup the CME API access: CME-API. Enable XML Test In addition, the xmltest variable on the CME must be enabled by typing the following in the CME command line interface (CLI): telephony-service xmltest exit wr mem

34 SA-Announce User Guide Network Requirements SA-Announce supports both unicast and multicast paging. Multicast is recommended for systems with paging groups of 100 or more endpoints Firewall Ports SA-Announce requires proper connectivity to/from the CUCM and end-point 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 CUCM Protocol description 2000 TCP - SCCP - Skinny Client Control Protocol. 80, 443, 8443 TCP - HTTP/SOAP - AXL UDP - RTP 2748 TCP - TAPI SA-Announce to IP Phones 80 TCP - HTTP UDP - RTP - unicast and multicast IP Phones to SA-Announce 80 TCP - HTTP UDP - RTP - unicast and multicast SA-Announce to IP Speakers 80 TCP - HTTP 6789 UDP - SynApps IP device protocol UDP - RTP - unicast and multicast

35 System Requirements Multicast Requirements If users choose to use multicast, which is strongly suggested with over 100 endpoints, then 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 network cannot be multicast enabled, or enabling multicast would require a large or recurring investment, 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 unicast stream into a multicast stream at the remote site. See SA-Announce Overview or contact Syn-Apps Sales for more information. Note: SA-Announce is configured for unicast by default. To enable multicast, refer to the Multicast Configuration section of this manual. Refer to your network support or your telephony partner for the best approach for implementing multicast on your network.

36 Installation Procedure Part 6

37 Installation Procedure 6 37 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 [email protected] 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

38 SA-Announce User Guide Updating SA-Announce This section explains updating SA-Announce to a newer release version. 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

39 Installation Procedure 39 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.

40 Configuration Utility Part 7

41 Configuration Utility 7 41 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. The program 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. 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. CUCM Settings SA-Announce requires the following information about the CUCM cluster: - CUCM Server IP Addresses Type the IP address of the Communications Manager Server (s). Input a maximum of five Communications Manager Servers. The first IP address field populated designates the primary Communications Manager server. List the Publisher first for multiple Communications Managers on a cluster. SA-Announce will use the primary server for CUCM data refresh unless it cannot be reached in which case SAAnnounce will try the next server in the list and so forth. The order described here does not affect the virtual notification group phones registration, those are handled using the CUCM groups configuration. - CUCM Version Select the appropriate version of the Communications Manager cluster. - CUCM Server Authentication Type the Communications Manager user name and password for CUCM data access. This user must have access to the Communications Manager AXL interface. If MLA is enabled on the Communications Manager this is the CCMAdministrator user name. - Sites Type Specify the Sites Type. This will define the way SAAnnounce partitions devices into sites to determine which streaming model to use (unicast / multicast). When an option is selected, SA-Announce will assume all phones within the Device Pool or Calling Search Space are located at the same site. This is useful for setting up multicast Screenshot

42 42 SA-Announce User Guide boundaries. 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. Application Admin Credentials 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. When using Communications Manager 3.x, log into the Syn-Apps application server with the same user name and password that exists on the Communications Manager. This must be an Administrator account and it must have the same user name and password as the Administrator account on Communications Manager 3.x. Click Next to proceed. Cloud Services To subscribe to Cloud Services, click the Enable Integration Subscriptions checkbox. Enter the Customer ID and Authorization values. After clicking on Configure, the background processing begins. Configuration Complete When the application is configured you will see a success window. An informational message will appear instructing the installer to change the CUCM authentication URL. Click OK to proceed.

43 Configuration Utility License Activation 43 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 Installation Instructions when configuration completes.

44 Post Installation Instructions Part 8

45 Post Installation Instructions 8 45 Post Installation Instructions Help >> Post Install Instructions >> Authentication URL Double click the SA-Announce shortcut on the desktop. The Help >> Post Install Instructions >> Authentication URL page should appear the first time the program is run. To access it at any time, click Help at the top of the user interface. Select the Post Install Instructions tab. The Help >> Post Install Instructions page also contains a quick start guide for the following: Page Name Description Authentication Information on configuring SA-Announce Authentication URL to avoid overloading the URL CallManager during a paging process. Group Creation Information on creating groups in the SA-Announce user interface. IP Phone Services Information on settings up SA-Announce phone service(s) in Communications Manager. Note: This feature is not required because it is a phone service that provides a directory of the groups that have been created. Misc. Info Information on enabling phone web access, phone software upgrades, and obtaining SynApps technical support. First time users should review the Cisco Communications Manager Requirements section for detailed Cisco system setup instructions. Review the Post Installation Instructions in the Authentication URL page after installing SA-Announce. These instructions will help users complete the setup process for Communications Manager Server(s) and Cisco IP phones. Once installation and configuration are complete, one final manual post-configuration step is required before Cisco IP phones can be activated by SA-Announce. Review the Authentication URL and IP Phone Services sections of the manual for detailed instructions.

46 SA-Announce User Guide Authentication URL Help >> Post Install Instructions >> Authentication URL The CUCM Authentication URL must be offloaded to the SA-Announce server to allow the IP phones to receive notifications. The following table describes the CUCM Authentication URL setup. The first section is for CUCM versions 5 and greater. The remaining section is for Call Manager Express (CME). Authentication URL Setup Description CUCM Version 5 and greater To avoid overloading the Communications Manager with authentication requests from the phones during the paging process, SA-Announce requires the Communications Manager Enterprise Parameter URL Authentication be offloaded to point to the SA-Announce server. CUCM 5+ Setup Process Open Communications Manager Administration (CCMADMN). Navigate to System >> Enterprise Parameters. Set the URL Authentication parameter to: aspx Press Update. Reset all phones. Note: CUCM version 8 has both secure and non-secure URL fields. When using CUCM version 8, set both the secure and non-secure Authentication URL fields to the same value. CUCM Express (CME) Define the Authentication URL under the telephony service in the CLI (command line interface) of CUCM Express in order for IP phones to authenticate properly. CME Setup Process Open the CME CLI. Login and enter the following commands: telephony-service url authentication PhoneServices/Authenticate.aspx exit wr mem *Note: IP phones will not be able to receive commands until these steps have been completed.

47 Post Installation Instructions Group Creation Help >> Post Install Instructions >> Group Creation The Group Creation tab is used to provide system users a basic understanding of how to configure notification groups and their various settings.

48 SA-Announce User Guide IP Phone Services Help >> Post Install Instructions >> IP Phone Services This chapter is not required. The IP Phone Services tab describes two of the basic IP phone services offered by SA-Announce. This tab provides a quick start guide for getting IP phones configured. See the IP Phone Services Configuration section for a complete list of IP phone services details. The IP Phone Services tab describes the following: 1. SA-Announce phone service - A directory of groups accessible on the IP phones (Notification Group Directory). 2. SA-Announce web dialer service - Phone sourced multicasting (Web Dialer Directory).

49 Post Installation Instructions Miscellaneous Info Help >> Post Install Instructions >> MISC Info The Misc Info tab is used to provide system users an easy navigation path to upgrading Cisco phone software and enabling web access settings for Cisco phones to receive SA-Announce notifications.

50 SA-Announce User Guide Configure IP Phone Services Services >> Broadcast Services >> Phone Services SA-Announce provides IP phone services and other advanced configuration options to facilitate phone-sourced multicasting. The following chapters describe these IP phone services and configuration options in detail. The following table briefly describes the phone service and configuration options: Phone Service or Option Description Notification Group Directory A directory of the notification groups that have been configured on the system. Web Dialer Directory This IP phone service is used to display and activate Normal, Holler, and Wokkie-Tokkie page groups. In this case, rather than calling a phone number, the group activation is done via web browser in the SA-Announce user interface to allow phone sourced multicasting from any supported Cisco phone. Note that in this mode, hooking the source phone will not shut down the group. The "End Page" soft-key must be pressed to properly shut down the notification group. Phone Message Browser Browse messages that have previously been sent to the phone. 7921/25/26 Push-to-Talk The 7921/25/26 wireless IP phones push-to-talk button can be used with SA-Announce Wokkie-Tokkie (walky talky emulator) notifications. The push-to-talk button can also be used to activate a standard notification. Phone Service URL This section describes the process of adding a Service URL to an IP Phone line button. It is possible to reconfigure the phone button template such that a line button, such as speed dial, becomes a Service URL (direct access to a web URL). The Service URL can be used to activate the Web Dialer directory or activate a specific group via the web. This is useful as it can provide phone-sourced local multicasting at a site located across the WAN from the main SAAnnounce server site.

51 Post Installation Instructions Notification Group Directory The SA-Announce Notification Group Directory is used to display a directory of the configured notification groups on Cisco IP Phones. In order to use SA-Announce group directory an IP phone service must be created in CUCM. Create a new IP phone service (CUCM Admin >> Device >> Device Settings >> Phone Services) using the following parameters: Service Name = SA-Announce Service URL = where server-ipaddress equals your SA-Announce servers' IP address. By default, the Group Directory provides a list of all groups. To show only groups that the accessing phone is a member of use the following Service URL: Service URL = Once the IP phone service has been created, subscribe the desired phone(s) to the service. Once phones are subscribed to the service, use the Services button on the phone and select the SA-Announce service to enter the directory. After accessing the service from a phone the following screen should appear: Select the desired page group and press Dial to initiate the page.

52 SA-Announce User Guide Web Dialer Directory The SA-Announce Web Dialer directory service is used to initiate phone sourced multicast notifications. In order to use the SA-Announce web dialer directory, an IP phone service must be created in CUCM. Create an IP phone service with the following parameters: Service Name = SA-Announce Web Dialer Service URL = where server-ip-address equals your SA-Announce servers 'IP address. By default, the Web Dialer Directory provides a list of all groups that can be web dialed. To show only groups that the accessing phone is a member of, use the following Service URL: Service URL = Once the IP Phone Service has been created subscribe the desired phone(s) to the service. After accessing the Services panel from a subscribed phone, the following should appear: Select the desired page group and press Select to initiate the page.

53 Post Installation Instructions Phone Message Browser The Phone Message Browser phone service allows previously sent messages to be viewed on IP phones. Create a new IP phone service CUCM Admin >> Device >> Device Settings >> Phone Services with the following parameters: Service Name = Message Browser Service URL = where server-ip-address equals your SA-Announce servers' IP address. Once the IP phone service has been created, subscribe the desired phone(s) to the service. Once phones are subscribed to the service, use the Services button on the phone and select the Message Browser service to begin viewing previous messages.

54 SA-Announce User Guide 7921/25/26 - Push-to-Talk To utilize the Push-to-Talk button on the 7921 / 7925 or 7926 wireless phones, setup an SA-Announce WokkieTokkie notification group and then activate it using the Web Dialer methodology. In this case, the Push-to-Talk button will control the audio stream originating from the 7921 / 7925 or For example, click the Push-to-Talk button to activate the group (see below). Next, hold the Push-to-Talk button down to talk. Release the button when finished speaking. Note: The source caller must end the page using the " End Page" soft-key provided on the source phone. It is possible to set the 7921/7925/7926 Push-to-Talk button to activate a specific group. In this case, you would set the Application URL of the 7921/7925/7926 using Communication Manager Admin >> Device >> Phone to point to the following URL: Where server-ip-address is the IP address of the SA-Announce server and <group-id> is the group-id as shown on the SA-Announce user interface Group(s) page.

55 Post Installation Instructions Phone Service URL This section describes the process of adding a Service URL to an IP phone line button. It is possible to reconfigure the phone button template such that a line button, such as speed dial, becomes a Service URL which provides direct access to a web URL. The Service URL can be used to activate an SAAnnounce notification group rather than using the traditional method by dialing the number. This is useful because it can provide phone sourced local multicasting at a site located across the WAN from the main SAAnnounce server site. Step 1: Create a new IP Phone Service that will be assigned to the Service URL button on the source phones: IP Phone Service Setting Description Service Name Name of the service. A generic name is recommended because this service can be used for all sites and multiple destination groups. Service Description Description for the service. Service URL - Make sure to replace the x.x.x.x with the ip address of your SA-Announce server. Service Parameter Settings Save the service and then add a Service Parameter with the following: Parameter Name id. Parameter Display Name Group-Id. Parameter Description The Id of the group to activate. Parameter is Required <true> - Enable this checkbox to signify that the parameter is required. **Lastly, click Update and Close at the top of the web page to save the changes to the new service. Step 2: Make sure that the phone button template on the target device has a Service URL defined. Step 3: Get the Group-Id for the target group from SA-Announce. Open the SA-Announce user interface. Navigate the Create / Edit Groups page. Select the desired target group from the drop-down box. Make sure the General tab is selected and look next to the group type for id = <n> Make a note of this ID you will need it in the next step. Step 4: Subscribe the phones to the IP phone service. Open the target phone in CCMADMIN. Click on the Subscribe/Unsubscribe Services hyperlink in the upper-right, Select the service created in the first step. Enter the ID noted in the previous step in the Group ID parameter. Save and Update. Continued on the following page

56 56 SA-Announce User Guide Step 5: Add the Service URL Button to the phone Navigate back to the device configuration page for the same phone above Click Add/Update Service URL Buttons and select the service name that you just subscribed to Save and Update and then restart the phone Once users complete these steps, they can use this service for all phones in the organization, regardless of the destination group. Replace the Group Id parameter with the Target Notification Group Id. Once the IP phone is restarted, users should see the service URL button configured with the Service Name. Important: Users must press the Service URL button to initiate the page prior to lifting the receiver or they will initiate a new call. Users must end the page by pressing the soft-key on the phone labeled End Page

57 Initial Application Configuration Part 9

58 58 9 SA-Announce User Guide Initial Application Configuration This section describes the basic settings in the SA-Announce notification system that should be understood for all installations. Application Basics Description Application Login Describes the login interface for SA-Announce. Service Configuration Options Describes the service configuration options for the SA-Announce broadcaster service. Multicast Configuration Describes the multicast configuration settings and tests contained in SA-Announce. User Accounts Describes the creation of user accounts in SA-Announce. IP Phone Tests Describes the IP phone configuration test tool in SA-Announce.

59 Initial Application Configuration 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.

60 SA-Announce User Guide Service Configuration Options Services >> Broadcast Services >>Settings The Settings Tab allows adjustment of the general system settings and contains the following service parameters: Setting Name Auto Conference Outbound Call Timeout (seconds) Default Description 30 The maximum time, (in seconds), to try and reach Auto Conference participants. If the participant has not confirmed after the designated time passes, then the attempt will be canceled. Busy Detection XML To prevent pages from interrupting active calls, XML Busy Detection is enabled by default. Some scenarios, such as shared lines may require TAPI Busy Detection. Refer to the TAPI Busy Detection chapter for detailed setup instructions. Application Server Device Pool (Site) Default Select the site where the SA-Announce server resides. This is used for the broadcaster to determine a local broadcast versus an inter-site broadcast. Servers authorized to use the SA-Announce API Enabled Enter the IP addresses of servers authorized to access the SA-Announce API in a comma delimited list. Check the Allow All Servers checkbox to allow all servers access. Page group busy if External Phone busy Unchecked When enabled, SA-Announce will notify the page initiator that the external dialer is busy and the page will end. DND in Use Enable (check) when using SA-DND (Do Not Disturb) or another ringer management system. Destination IP phones with disabled ringers will not be paged. If this option is selected, the automatic refresh timer setting will need to be changed. At two hours by default, it would take SA-Announce an hour (average) to discover that a ringer has been turned off. To change the setting go to Unchecked Services >> Broadcast Services >> Advanced Settings. Select refreshphonesettingsminutes. For installations of less than 500 phones, change the value to a minimum of 2. For installations of phones, change the minimum value of 4. For installations of phones, change the minimum value to Idle URL in Use Enable (check) when using the Idle URL feature on Cisco IP phones. Unchecked This will clear the phones' state prior to trying to page, avoiding the XML Busy State that the Idle URL creates. All Busy Detect Unchecked Extension Mobility Mode Enable For use with CUCM 5/6/7+ systems using extension mobility. Using Unchecked this option will reveal user device profiles in the Groups >> IP Phones section, which can then be added to groups. Register Devices Using CUCM Groups If checked, the group and dialer phones will be registered using the CUCM groups settings on the CUCM. By default this setting is Unchecked unchecked, meaning the group and dialer phones will be registered using the ordered list of CUCM's provided during SA-Announce configuration. Multicast Only This setting, when enabled, does not allow for unicast notifications. This is a useful setting when phone sourced multicast is the default Unchecked streaming model. With the newer server sourced model, the Broadcaster does not need to fail-over to unicast when a non-ip phone When enabled, the caller will be notified if all destinations of the group are busy.

61 Initial Application Configuration Setting Name Default 61 Description dials a live notification group. Required Phones Percent is used to determine when the originator of the page hears confirmation beeps. The beeps alert the user that it is safe to start talking. The default setting is 80%, so if a page group had 100 phones the confirmation tone would play when 80 phones are activated. With SA-Announce and greater, the confirmation threshold is dynamically applied in the following circumstance: 1) Group has an opening tone associated. 2) Group has Paging Relay(s) associated. Confirmation threshold when calling a broadcaster group 80 *This setting has been moved to Services >> Broadcast Services >> Advanced Settings >> RequiredPhonesPercent In this case, the confirmation threshold will not be met until all Paging Relays have been contacted with opening commands. Once 80% of devices have joined, if the group has Paging Relays that have not responded to their opening commands, the opening tone / confirmation tone will be delayed. The opening tone and confirmation tone will only be played once all Paging Relays associated with the group have responded.

62 62 SA-Announce User Guide Settings Tab (shown with defaults): Click the Save button to save settings changes.

63 Initial Application Configuration 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.

64 SA-Announce User Guide Phone Features Settings >> IP Endpoint Setup >> XML Phones By default, SA-Announce has all Cisco XML phone models enabled. However, if users implement a new model that is not within the default XML enabled models, the XML or Multicast tabs can be used to manually select phones. Use the XML Phones tab to identify those phones that will participate in XML control and communications. Use the >> and << arrows to move endpoints between the Available and Selected lists. Once new items have been added to the selected side, click Apply Changes.

65 Initial Application Configuration 65 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. Use the >> and << arrows to move endpoints between the Available and Selected lists. Once new items have been added to the selected side, click Apply Changes.

66 SA-Announce User Guide Multicast Configuration Settings >> Multicast >> Defaults The Multicast Settings page is used to enable or disable multicast notifications. By default, multicast notifications not enabled in SA-Announce. To enable or test multicast notifications, first verify the Multicast Enabled checkboxes are enabled (checked) and a Multicast IP Address exists. Click Save Defaults to save changes. The Multicast Settings page consists two main sections, multicast settings and multicast tests. Multicast Settings Description Multicast Settings Multicast Settings are used to Enable or Disable multicast notifications. Defaults On the Defaults tab, choose whether or not to enable WAN Multicast and/or Local Multicast globally. Select the Local Multicast Enabled checkbox to enable local multicast. For example, phones at the server site will have a multicast stream sent. Phones that are not at the server site will have unicast streams sent unless the Site to Site (WAN) Multicast Enabled checkbox is checked. Press the Save Defaults button. The default multicast addresses provided automatically should work for most implementations. If multicast boundaries (different multicast address for each sites' local multicast traffic) are required, use the Sites tab to configure them. Most implementations will not need to make changes on the sites tab.

67 Initial Application Configuration 67

68 68 Sites SA-Announce User Guide Use the Sites tab to set multicast boundaries for one or more sites. Choose which Calling Search Space or Device Pool site should be configured for WAN Multicast and/or Local Multicast. Once a site is selected from the drop down box, a list of the devices contained within that site will be listed in the grid to the right. The settings on the Sites tab override the settings on the Defaults tab. To set a site back to the Defaults or Global settings, use the Back to Defaults button. Note that pressing Save will cause the selected site to use the current settings on the page. The defaults will be overridden for that site until the Back to Defaults button is pressed. The multicast settings have different meanings depending on the mode of operation of the product. The mode of operation is determined by the method used to access the notification groups. If the notification groups are being dialed then the Multicast Server Mode is in use. If the notification groups are activated by the Web Dialer or SAAnnounce API, then the Web Dialer Mode is in use. These two modes have different streaming models. Multicast Server Mode uses the SA-Announce server to source multicast streams to the Cisco IP phone endpoints. The Web Dialer Mode uses the source Cisco IP phone to source the multicast stream to the other phones. If Multicast Server Mode is in use (the default notification mode) then the settings are applied using a combination of the server site setting and sites of the destination Cisco IP phones in the notification group. If all of the destination phones are in the same site then the destination phones site Local Multicast setting is applied. If all of the destination phones are not in the same site then the Server Site WAN Multicast setting is applied. The Server Site setting should be set to the site where the server resides by navigating to Services >> Broadcast Services >> Settings. If the Web Dialer Mode is in use then the settings are applied using the source, or caller's, Cisco IP phone. If all of the Cisco IP phone destinations in the group are in the same site as the caller, then the caller's site Local Multicast setting is applied. If all of the Cisco IP phone destinations in the group are not in the same site or not in the same site as the caller, then the caller's site WAN Multicast setting is applied.

69 Initial Application Configuration 69 Multicast Settings Description Multicast Tests The primary purpose of these tools is to determine whether multicast is functioning properly on the network. It is suggested to test 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 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 you hear a series of ascending tones, 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 Multicast Test Use the Server to Speaker Multicast Test tab to perform a server to speaker 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. See screenshot below.

70 70 SA-Announce User Guide Phone to Phone Multicast Test Use the Phone to Phone Multicast Test to perform a phone-to-phone multicast test. This test will verify the source phone's ability to source multicast to a test phone. Choose a destination phone on a different switch than the source phone. Enter the IP Address of the first phone to test in the first phone IP address field. Enter the IP Address of the second phone to test the second phone IP address field. Click the Start Transmission button to begin a multicast transmit and receive test. Verify that audio from the first phone can be heard from the second phone and vice versa. If you hear the audio clearly, then multicast is functioning properly between the two phones. To stop testing, press the Stop Transmission button.

71 Initial Application Configuration 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.

72 72 SA-Announce User Guide 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 a 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 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 Retype 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 changes. Delete a User Select a User Select the user to delete in the Select User drop down menu. Delete User Press Delete to delete the user from SA-Announce. Add Permission to User Add permissions to non-administrative users (required). ***Administrative 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.

73 Initial Application Configuration 73 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. Note that the Service Account credential fields should not be required unless the SAAnnounce 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.

74 SA-Announce User Guide Troubleshooting Tests Services >> Troubleshooting Tests The Services >> Troubleshooting Tests page contains a number of basic troubleshooting modules. The IP Phone Tests screen can be used to test the basic connectivity to IP phones. To access the IP Phone Tests page, navigate to the Services >> Troubleshooting Tests. The IP Phone Tests tab will be shown by default.

75 Initial Application Configuration 75 To run the IP Phone Tests perform the following: Phone XML Test Note: The Authentication URL must be configured on CUCM before the test will work. See the Authentication URL section for details. Test Phone Select an extension to test from the Test Phone drop-down menu. Use the Filter to list by extension or select an item in the drop-down list and type an extension. If no phones are visible then SA-Announce does not see any registered XML enabled phones. Verify the application Configuration. Run All Tests Click the Run All Tests button to perform the test. Verify Results on Server A message displays in the SA-Announce UI (user interface), confirming whether or not the database connection was successful. Verify Results on Target Phone Verify that the test phone shows Test on the display screen. Note: If the test does not complete successfully, verify the Authentication URL on the phone by accessing the Settings button on the phone(s). If the authentication URL appears to be correct, verify that the phone has access to the SA-Announce server on HTTP port 80. Lastly, verify that the phones Web Access setting is enabled. See Communications Manager Requirements for details.

76 Notification Group Configuration Part 10

77 Notification Group Configuration 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 setup. 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: Notification group sources and destinations: For every notification group users create, SA-Announce will automatically create a Syn-Apps virtual phone listed under Device >> Phones in Communications Manager. The virtual phone name will begin with SEPFFFF. This is also true for any external phone dialers. The name for external phone dialers will begin with SEPEEEE. When a user deletes notification groups in SA-Announce, the associated virtual phones and lines are NOT deleted from CUCM. After deleting notification groups in SA-Announce, delete the associated virtual phone and line in CUCM administration by searching Device >> Phone on the notification group line number or device name. If the Syn-Apps Device is in use, meaning the Syn-Apps device pack has been installed on your CUCM's, then the device will be named SYNFFFF or SYNEEEE depending on the device type.

78 SA-Announce User Guide Notification Group Types Groups >> Create / Edit Groups The SA-Announce notification system includes a number of notification group types each 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 play the callers live audio. Ad-Hoc A non-predefined group of end-points that play the callers live audio. Respond A predefined group of end-points that play the callers live audio. One listener can respond to the originator. Record-N-Play A predefined group of end-points that play 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 play stored or live audio and display 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 SAAnnounce user interface Conference Automatically start a conference. Auto Conference Automatically creates a MeetMe conference and joins the caller and predefined users at internal or external numbers by calling those users and waiting for confirmation. Intercom One to one, two way, live audio. Holler Dynamic one to one intercom notification. Destination is entered as DTMF by caller. Holler-RP Dynamic one to one intercom notification. Destination extension is part of the dial string. Insta-Holler Static one to one intercom notification. Destination device is predefined. Wokkie Tokkie Wokkie Tokkie emulation for many-to-many, live audio, and push-to-talk functionality. Wokkie Tokkie (Normal) A predefined group of IP phones that emulate a walky-talky when the notification group is activated. Wokkie Tokkie (Ad-Hoc) Non-predefined group of IP phones that emulate a walky-talky; when the notification group is dialed the destination extensions will be gathered from the caller. Text Send text, images, and polls. Text A predefined group of end-points that delivers a text messages, audio notifications and images when activated. Poll A predefined group of end-points that delivers a text message, audio notification and image when activated. IP phone recipients can answer the poll using soft-keys. Scheduled Scheduled stored audio / text event. Schedule Note: As of SA-Announce , Scheduler is no longer listed as a Notification Group Type. Scheduler has been moved to its own section in the user interface. Navigate to SAAnnounce >> Schedules >> Create/Edit to add and modify schedules. Group Compatibility Matrix The group compatibility matrix lists the compatible endpoint types per group. Phones attached to the network can call most group types by dialing a number, however, some group types require the caller endpoint be known

79 Notification Group Configuration 79 to support SA-Announce XML commands. For this reason, the matrix lists whether or not an XML enabled caller is required to access the group: Group Type XML Caller Em ail IP Desktop External IP Paging Legacy IP Beacons Mass Required Phones Clients Phones Speakers Relays Speakers Notification Normal Holler Insta-Holler Holler-RP Ad-Hoc Emergency Alert Wokkie Tokkie Record-N-Play Respond Auto-Conference Text NA NA XML Caller Compatibility Matrix The XML caller compatibility matrix lists the currently supported callers for each group type category that requires an XML caller. See Cisco Communications Manager Requirements for the list of supported Cisco XML enabled IP phones. Category XML Caller Required Holler Respond IP Phones Desktop Clients IP Speakers

80 80 SA-Announce User Guide Ad-Hoc An Ad-Hoc notification group is a non-predefined group of end-points that play the callers live audio. This group type is similar to a Normal notification group, except the end-point members are not associated when the group is created. They are entered as DTMF by calling the users to create a notification group on-the-fly. For example if a user wanted to page extensions 1000, 2000, 3000, they would activate the page group by dialing its directory number and when prompted, enter 1000#, 2000#, 3000#, then the # button again. This would activate extensions 1000, 2000 and 3000 for an Ad-Hoc one way audio page. Ad-Hoc 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/image. 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. See the Notification Group Setup section for more details.

81 Notification Group Configuration Auto Conference SA-Announce Auto Conference is a notification group type which leverages the CUCM Meet Me Conference to automatically create and join predefined users in a conference. The initiator calls the Auto Conference group number to begin the Auto Conference. Auto Conference then creates a Meet-Me conference and joins predefined users, either internal or external numbers, by calling those users and waiting for confirmation. An escalation number can be configured so IP phone participants can escalate the conference by pressing a soft-key. Users can be added to an ongoing conference by any IP phone listener. Up to 15 participants can join the Auto Conference. Additional Auto Conference features include: Feature Description Alert on Activation Automatically activate an SA-Announce Emergency Alert group or Schedule when the Auto Conference is activated. Events Send s to unique addresses for activation, escalation, participation, and error events. IP Phone Events IP phone participants initiate events using the soft-keys on their phone (default softkey names shown): Add User Call 911 Notify Escalate Add a user to the conference. Disconnect from the conference and auto dial 911 to notify them of the event. Activate an SA-Announce emergency alert group or schedule (generally to signify the end of the event to non conference participants). Add a super user to the conference. Auto conference automatically escalates if no participants join the conference. Requirements - Auto Conference has the following requirements that must be met: Requirement Description External Phone Dialers SA-Announce External Phone Dialer Requirements Dialer Configuration Auto Conference requires external phone dialers to facilitate dialing destination phones to join to a conference. It is recommended that users create at least as many dialers as destinations of the largest Auto Conference group. Auto conference can join a maximum of 13 destinations to a Meet-Me Conference. The maximum 13 destinations does not include the caller and possible escalated party. Add Dialers to MRGL The Auto Conference dialers must be in an appropriate Media Resource Group List. This parameter is not currently exposed on the Settings >> External Phone Setup page. After adding dialers using this page, an authorized user must manually edit them in CUCM in order to have an accurate Media Resource Group List. Dialer Pool The Auto Conference dialers are all members of a single "dialer pool", meaning all dialers must have the same settings, with the exception of their line number. Due to this feature, the Dialer Settings must allow the dialer to call any of the internal or external numbers programmed in Auto Conference, as well as the Meet-Me Conference numbers. While this may not be an issue for most users, those with advanced dial plans may need to make dial plan adjustments in order to accommodate Auto Conference at multiple sites.

82 82 SA-Announce User Guide Group Phone The Auto Conference Group Virtual Phone Requirements Group Phone CSS The Auto Conference group phone must be in a CSS that can reach the MeetMe number and busy transfer number for the group. When adding a new Auto Conference group type, SA-Announce will check the MeetMe and Busy Transfer numbers against the selected CSS to make sure a route is present. If authorized users have recently added the Meet-Me or Busy Transfer numbers, make sure to use the Refresh Data button in the SA-Announce user interface at Services >> Broadcast Services >> Services. CUCM Registration The Auto Conference group phone and callers must be registered to the same CUCM in order for the group to function properly. If CUCM registration groups are in use, the SA-Announce setting Broadcast Services >>Settings >> Register devices using CUCM Groups should be enabled (checked). This setting allows the Auto Conference group phone and callers to be in the same device pool in order for the group to function properly. Meet-Me Number CUCM MeetMe Conference Directory Number Requirements MeetMe Configuration The Auto Conference Meet-Me number must be manually created on CUCM at Call Routing >> Meet-Me Number / Pattern. Each Auto Conference group must have its own unique and reserved Meet-Me number. For example, do not manually activate the Meet-Me numbers set aside for Auto Conference. Groups >> Create / Edit Groups >> General These settings are only shown when an Auto Conference group type is selected. Refer to the Notification Group Setup section of the manual for details on basic group setup, such setting up the number used to activate an Auto Conference. Basic Auto Conference group settings are not discussed in this section.

83 Notification Group Configuration 83 Auto Conference Settings Descriptions: Setting Description General Settings Auto Conference Group General Settings Title Enter a title that will appear on the screen pops for this group. Meet-Me Number Enter the reserved Meet-Me conference number to be used for this Auto Conference group. Busy Xfer If the Meet-Me is busy when the group is called, transfer the caller to the given number. Tip: Use the Meet-Me number to join the caller to the Auto Conference, which is presumably in use. Confirmation Sound The sound file played on the users phone when being joined into the conference. Users must press the "one" DTMF key once they answer or they will not be joined to the conference. The default file AutoConfConfirm.wav informs those being called that they need to press 1 to enter the Auto Conference. If the Confirmation Sound file is changed (customized), it should certainly ask users to Press 1 at minimum. Activation Group Select an Emergency Alert group or Schedule to activate when this group is called. Escalation Settings Auto Conference Group Escalation Settings Escalation Number An escalation soft-key is provided on IP phone members of the conference. Pressing the soft-key will join the user at the given number to the auto conference. Soft Key Label The label used for the Escalation soft key/ The default is Escalate. Other Settings Auto Conference Soft-Key Group Activation Settings Soft Key Group Emergency Alert group or Schedule to activate when the IP phone user presses the Notify Soft-Key. For example, this could be a group to alert when the event ends. Soft Key Label The label used for the Soft Key Groups' soft key. The default is Notify. Auto Conference Settings Navigate to Groups >> Create / Edit Groups >> to see the tab on the groups page for the Auto Conference setup. The group Address (Activation) works the same as other group types. If populated, s will be sent when the group is activated. Additional fields will be displayed when an Auto Conference group type is selected. Auto Conference Setting Description Settings Auto Conference Settings Participation Address the participation results to review who joined the conference. Escalation Address when the group is escalated using the escalate soft-key. Error Address when errors occur in group processing. For information on the Activation Settings, refer to the section.

84 84 SA-Announce User Guide Adding Endpoints to the Group Navigate to Groups >> Create / Edit Groups >> IP Phones / External Phones tab to add endpoints to the Auto-Conference. Both phone types will be dialed by number but only IP phones will receive screen pops. When adding IP phone devices to the Auto Conference group in the IP Phones tab, note the device may contain multiple lines. Auto Conference will dial the primary line, line-1. Auto Conference Pop Up on a Cisco IP Phone: Auto Conference Troubleshooting Consult the below table if problems are experienced with Auto-Conference: Problem Likely Solutions - Assuming all requirements listed above have been verified. Caller Receives Silence If the Auto Conference caller is left with silence or on-hold after calling, then the most likely problem is an inter-digit timeout. Check for inter-digit timeouts for the group phone/line CSS when trying to reach the MeetMe line. This is generally the cause of this error. Caller Left on Hold SA-Announce allows 16000ms for a transfer by default. Just longer than the default inter-digit timeout on CUCM. Services >> Broadcast Services >> Advanced Settings >> autoconfmaxxferwaitms controls the maximum wait timer.

85 Notification Group Configuration 85 MeetMe Callers Max Adjusts the maximum number of Meet-Me callers that CUCM can handle at once. Refer to the following article for additional details: Control Maximum Number of Meet-Me Callers No IP Phone Screen Make sure a Media Termination Point (MTP) is not in use on the Cisco XML enabled IP phone. This will obscure the IP address of the IP phone and it will not receive screen pops.

86 86 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.

87 Notification Group Configuration 87 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 end-points that support text or image. 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.

88 88 SA-Announce User Guide Holler Holler is an intercom notification group type. Holler notification groups always target a single destination endpoint and open that end-point speaker (hands-free mode). The target of a Holler notification is determined in one of three ways corresponding to the three different Holler group types.

89 Notification Group Configuration 89 The three holler notification group types are described in the table below: Holler Type Activation Method - The method used to activate the intercom. Holler After calling a standard Holler notification group users are prompted for a destination extension followed by the # sign. Holler-RP Holler-RP uses a line number mask to allow direct intercom access to any extension. This allows users to prefix an extension to intercom with any key such as * or #. For example, in a four-digit dial plan using the Holler-RP group with line number #XXXX, dialing #2000 would intercom extension 2000, dialing #2003 would intercom extension 2003 and so on. Note: The extension used must end in a number of "X" characters equal to the length of the internal dial plan. Insta-Holler The Insta-Holler notification group provides a way to target a destination that does not have a unique line number configured on it, it should only be used for this case. An Insta-Holler group allows you to pre-define a single XML enabled IP phone that will receive a two-way audio intercom when the group is activated. This is a one-to-one group that delivers two-way audio. Holler and Holler-RP destinations are determined by number and must be unique, shared lines can cause issues here. If a shared line is the first line listed on only one phone then that phone will be activated for holler. If the shared line is the first line on more than one phone or the shared line is not the first line on any phone, then Holler will fail and notify the caller that the destination is a shared line. If this issue must be overcome add unique directory numbers to the phones or use the Insta-Holler group type. An XML enabled phone must be used to activate any Holler notification group. If a non-xml enabled phone calls a holler group they will receive an error stating that Holler is not possible from the current phone. Valid Holler and Holler-RP destinations consist of XML enabled IP phones and Syn-Apps or AND IP speakers. Holler 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 image. 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. Opening Tone Send a predefined audio notification tone to destination end-points as the group opens. Mute Destination at Start the destination of the holler notification as muted. By default, the option is Start disabled and the destination will start with its microphone open. See the Notification Group Setup section for more details.

90 90 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 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. 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.

91 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 when done. 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 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 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. DTMF Options Record-N-Play callers can use DTMF * to reset their message at any time. The recording can be ended by pressing DTMF # or by hanging up. See the Notification Group Setup section for more details.

92 92 SA-Announce User Guide Respond The Respond notification group type is much like a Normal notification group (one-way one-to-many audio), but the IP phone destinations of the group will have a text display presented that contains a "Respond" soft-key which when depressed will allow one user to respond to the source caller. Once a response begins all end-points but the caller and responder will close down and the caller / responder will be left in a one-to-one two-way conversation. Respond 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 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. See the Notification Group Setup section for more details.

93 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. The Group Phone area will not be visible with Text type notification groups because Text groups do not require a device in Communications Manager or activation via phone call. To use the Text notification group, navigate to Groups >> Send Text Message. See the Sending A Text Message section for complete details.

94 94 SA-Announce User Guide Wokkie Tokkie A Wokkie Tokkie notification group emulates a walky-talky, push-to-talk conference, on Cisco XML enabled IP phone end-points. There are two types of Wokkie Tokkie groups, Standard and Ad-Hoc. The Wokkie Tokkie notification group type requires multicast. Multicast must be configured on the network in order for Wokkie Tokkie to function. The Standard type allows group members to be predefined, while the Ad-Hoc type allows users to dynamically select destination endpoints. With Ad-Hoc, the caller enters participant directory numbers by DTMF and delimited by the pound sign. Wokkie Tokkie 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 image. Emergency Notify destination endpoints regardless of that endpoints busy state. Security Code Require the caller to enter a DTMF security code before the notification is allowed to proceed. Opening Tone Send a predefined audio notification tone to destination endpoints as the group opens. Volume Sets the page volume on IP speakers. See the Notification Group Setup section for more details. After dialing a Wokkie Tokkie group, the source and destination IP phones will be presented with the following

95 Notification Group Configuration popup notification: 1. Press and hold the Talk softkey to transmit, as with a walky-talky. 2. Press Shout to speak continuously and Stop when finished. 3. Press Exit to exit. 95

96 SA-Announce User Guide Notification Group Setup Groups >> Create / Edit Groups >> 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 Groups >> General

97 Notification Group Configuration 97 Click New Group near the bottom of the page then configure the following settings on the General tab: Notification Group Setting Description Enter a 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. Partition The partition the group phone should belong to. For example, phones must have a CSS containing this Partition to be able to dial the group. Device Pool Device pool the phone should belong to. The Device Pool must be set such that callers receive a G.711 codec lookup. Calling Search Space Select the CSS that the group phone should belong to. This field is only displayed for Auto Conference group types. 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. Volume The Volume drop-down menu allows users to adjust the volume of audio on IP phone speakers. The Default volume setting uses the setting of each phones' speaker individually. Other settings, such as 90% and 80%, override the current volume setting on the phone and forces the phone to play the audio at the percentage of maximum volume specified. IP speakers can be made to use the groups volume setting by adjusting the speakers volume to 0 in the IP Speaker configuration table Settings >> IP Endpoint Setup >>Syn-Apps IP. See Syn-Apps IP Speaker Configuration for more information. While this does affect the volume of phones, it does not affect the volume of External Phones, Legacy IP devices, or Alertus notifications. Group Opening Tone Group Opening Tone Send a predefined audio notification tone to destination endpoints. 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 endpoints have not been associated. Endpoints will be associated after saving the group. Click the Save Group button to save changes.

98 98 SA-Announce User Guide 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 savedi: Group Name has been Updated!

99 Notification Group Configuration Groups >> Create / Edit Groups >> 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.

100 SA-Announce User Guide IP Phones Groups >> Create / Edit Groups >> 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. Standard Windows Ctrl-click and Shift-click can be used to select items. Additionally, use the Filter column to filter the list.

101 Notification Group Configuration 101 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.

102 102 SA-Announce User Guide Excluded Targets For Holler and Holler-RP group types, users can select phones to be excluded as targets. Remember, in this case users are selecting phones that are not to be included in the group.

103 Notification Group Configuration Desktop Clients Groups >> Create / Edit Groups >> 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. 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.

104 SA-Announce User Guide Cloud Services Groups >> Create / Edit Groups >> 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 Cisco Digital Media System Global Cache Notifier Twilio Notifier Once Cloud Services has been setup via SA-Announce configuration, users are ready to configure Cloud Services notification groups.

105 Notification Group Configuration 105 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 (2) 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.

106 SA-Announce User Guide External Groups >> Create / Edit Groups >> External Add legacy overhead speaker systems, analog phone extensions, or other external phones to a notification group by selecting the External tab. Make sure the overhead system can be dialed from the digital phones. The number used to dial the overhead system is generally the same number used in the Number field on the External screen. External dialers must be setup before the external phone integration will work properly. Use the Settings >> External Phone Setup web page to configure external dialers. The analog paging system integration setup is described in more detail in the Analog Paging System Integration section. The user interface can be used to add External systems to the notification group: 1. Enter a description in the Description or Name field. 2. Enter the overhead systems extension, analog phones' extension, or the dialing number for external phones in the Number field. 3. In the Dial Code field, enter a DTMF zone code if one is required. 4. Press the Add button to add the external system to the selected notification group. To remove an External system from a group, select the line item from the list box on the right and press the Remove button. To update an existing External system in a group, select the line item. The current values will populate in the entry fields. Change the values and press the Update button.

107 Notification Group Configuration IP Speakers Groups >> Create / Edit Groups >> IP Speakers This section describes use of Syn-Apps IP Speakers, Algo, AND, and Atlas IP Speakers in 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. 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

108 108 SA-Announce User Guide Custom Filter option is selected, a message will appear that describes the column names used in the filter.

109 Notification Group Configuration Syn-Apps Paging Relays Groups >> Create / Edit Groups >> 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. 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.

110 110 SA-Announce User Guide 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 SAAnnounce site and the initiator must be in the same device pool (DP) or calling search space (CSS). No External Phones External phones must not be associated to the notification group. 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.

111 Notification Group Configuration Static Streams Groups >> Create / Edit Groups >> Static Steams 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.

112 112 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 Beacons Groups >> Create / Edit Groups >> 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.

113 Notification Group Configuration 113 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.

114 114 SA-Announce User Guide Mass Notification Groups >> Create / Edit Groups >> Mass Notification 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 Groups >> Mass Notification 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.

115 Creating Emergency Alert Groups Part 11

116 SA-Announce User Guide Creating Emergency Alert Groups Groups >> Create / Edit Groups 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.

117 Creating Emergency Alert Groups 117 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. Select Groups >> Create / Edit Groups >> 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. Partition The partition the group phone should belong to. For example, phones must have a CSS containing this Partition to be able to dial the group. Device Pool Device pool the phone should belong to. The Device Pool must be set such that callers receive a G.711 codec lookup.

118 118 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. Volume The Volume drop-down menu allows users to adjust the volume of audio on IP phone speakers. The Default volume setting uses the setting of each phones' speaker individually. Other settings, such as 90% and 80%, override the current volume setting on the phone and forces the phone to play the audio at the percentage of maximum volume specified. IP speakers can be made to use the groups volume setting by adjusting the speakers volume to 0 in the IP Speaker configuration table Settings >> IP Endpoint Setup >>Syn-Apps IP. See Syn-Apps IP Speaker Configuration for more information. While this does affect the volume of phones, it does not affect the volume of External Phones, Legacy IP devices, or Alertus notifications. 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 endpoints 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. The Weather alerts are merged with Emergency Alert groups for convenience. They do not activate when the group is called. Instead, they activate when a Weather alert is in effect. In some cases where emergency alert groups have a custom Wav file for situations such as "School on Lockdown," users will not want to integrate with Weather Alerts group. Instead, create a new group for Weather Alerts only.

119 SA-Announce Scheduler Part 12

120 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 (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. 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. 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. Default General Schedule View Use this view to edit schedule details such as schedule nam e, associated audio, and text.

121 SA-Announce Scheduler 121 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 Settings Description Enter a 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. Note: Select a Time Zone prior to scheduling events. All scheduled notification groups are associated with one time zone and will not work properly if the time zone is changed after associating events to the schedule. 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. 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 The Volume drop-down menu allows users to adjust the volume of audio on IP phone speakers. The Default volume setting uses the setting of each phones' speaker individually. Other settings, such as 90% and 80%, override the current volume setting on the phone and forces the phone to play the audio at the percentage of maximum volume specified. IP speakers can be made to use the groups volume setting by adjusting the speakers volume to 0 in the IP Speaker configuration table Settings >> IP Endpoint Setup >>Syn-Apps IP. See Syn-Apps IP Speaker Configuration for more information. While this does affect the volume of phones, it does not affect the volume of External Phones, Legacy IP devices, or Alertus notifications. Repeat The number of times to play the wave file when the schedule is active. Text to Send Enter the text to send all end-points that support text messages. Emergency Enable to send text and audio stream to busy phones. Click Add Schedule. The schedule can be saved although end-points 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.

122 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.

123 SA-Announce Scheduler 123 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.

124 124 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.

125 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 125

126 126 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

127 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. 127

128 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.

129 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 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.

130 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. 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.

131 SA-Announce Scheduler 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.

132 132 SA-Announce User Guide 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 description AdHoc Played before waiting for target destination numbers. "You have reached an Ad-Hoc paging group. Please enter the destination extensions, separated by the pound sign. Once you have completed entering your destinations please enter pound again to start your page." 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." Holler Played to the caller of a holler group. "You have reached a Hoot-n-Holler page group. Please enter destination extension followed by the pound sign." HollerDNDActive Played if the destination of a holler is in DND mode. "We're sorry but the destination is currently set to do not disturb, please try again later." HollerError Played when a holler destination number is invalid. For example, if there is no route from the source phone to the destination number. "We were unable to open the destination you requested. The destination extension was invalid." HollerErrorBusy Played when a holler destination number is currently busy. "The destination is busy, please try again later." HollerErrorNV Played when a holler destination number is invalid. For example, if there is no route from the source phone to the destination number. "We're sorry the destination numbers are not valid." HollerErrorShared Played when the destination of a holler is a shared line and more than one device uses the number as its primary line. "We were unable to open the extension you requested. The destination is a shared line." MulticastOnly Played when a group call will be unicast and the multicast only setting is on. "Paging is not possible from this phone." 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" OverheadBusy Played when an external destination is busy and when the Close group if overhead busy setting is enabled. "Overhead destinations are busy, please try again later." RecordNPlay Played to the caller of a RecordNPlay group when the Advanced Setting

133 SA-Announce Scheduler 133 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 Played when so many destinations are busy that a confirmation tone will not be sent. Some destinations are busy "[Paging Continues].

134 Sending A Text Message Part 13

135 Sending A Text Message Sending A Text Message Groups >> Send Text Message >> Send Text Message To send a text message, navigate to Groups >> Send Text Message >> Send Text Message. To send a text message or poll 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. Previously existing groups with endpoints can also be used. 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.

136 136 SA-Announce User Guide The Send Text Message page allows users to save message templates for predefined text message groups. A message template is not required for sending a text message, but it is required for sending polls. To send a text message or poll, 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. Sound Notification Select a sound notification from the dropdown list to accompany the text message. The sound will only be played on the Desktop Notification client and IP speaker endpoints. 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 AND and Atlas IP Speakers. This will only appear when the Poll checkbox is de-selected. 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. Poll Options Options to enable or disable the poll feature and poll answers. Poll Options checkbox Enable the Poll Options checkbox to send the message as a poll. Poll Answers Enter the desired poll answers in the Answer 1-4 fields. Message Template Select or save the message template to use. This is only required for polls. Click the Save Template button to save the template for polls. Press the Send Message button to send the message. Refer to the Poll Results Browser tab in the SA-Announce user interface to view the poll results in real-time.

137 Sending A Text Message 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.

138 SA-Announce Reporting Part 14

139 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. 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 interface to browse different pages of the report. in the user 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 Current Page button. Alternatively, use the Print to print the current report page.

140 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.

141 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.

142 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.

143 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.

144 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.

145 SA-Announce Reporting Notification Group Report Services >> Reports / Analytics To access the Groups Report, navigate to Services >> Reports / Analytics >> Groups Report button. The Groups Report lists current SA-Announce Notification Groups and Associated Endpoints. Groups are sorted by Group Name in the UI report. A timestamp will appear in the upper-right corner of the UI, notifying when the report was generated. Notification Group 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 Cisco. Device Pool Does not apply for SA-Announce Cisco. Emergency Indicates whether or not the Group Type was an Emergency Alert. Volume Volume associated with the notifications' endpoint(s). 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.

146 146 SA-Announce User Guide 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).

147 Syn-Apps Analytics Part 15

148 SA-Announce User Guide Syn-Apps Analytics Services >> Reports / Analytics >> Analytics To access the Syn-Apps Analytics user interface, navigate to Services >> Reports / Analytics >> Analytics button. Syn-Apps Analytics is asn 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. 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.

149 Syn-Apps Analytics Number of Errors 149 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.

150 150 SA-Announce User Guide 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 Cisco IP phone, 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. 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.

151 Server Redundancy Part 16

152 SA-Announce User Guide Server Redundancy The server redundancy feature facilitates automatic failover of notification groups. The feature allows multiple SAAnnounce servers to be clustered together to maintain notification group functionality during server fault scenarios. In the case of a server failover, call control is routed via SIP trunks where SA-Announce servers listen for calls. Call control varies per platform. Talk to your call control manager to determine which is option is the best for your organizations' needs. Server Redundancy Overview In redundancy mode, a publisher and subscriber relationship is maintained to provide data replication between servers. The Redundancy feature is activated by assigning a publisher and a minimum of one subscriber. The subscriber(s) will re-direct the appropriate SA-Announce management GUI requests to the publisher. SAAnnounce global data must be shared between servers. Any changes to the SA-Announce global data are performed on the publisher. The changes are then pulled down by the subscribers in the Cluster. Refer to the Creating A Cluster section for further details. Once a Cluster has been created, servers are assigned to a prioritized list called a Server Group. At this point, Server Groups can be assigned to notification groups to enable the Redundancy feature. A Server Group can contain two or three servers. Once a notification group has been assigned a Server Group, the notification group will begin to run on the priority-1 server. If the priority-1 server experiences a fault, then the priority-2 server will begin to run the group. If a third priority server exists and both the priority-1 and priority-2 servers experience a fault, then priority-3 server will begin to run the group. See the Creating Server Groups Section for further detail on creating and managing Server Groups. Once the Cluster has been defined and one or more Server Groups have been created, the final step to enabling the Redundancy feature is assigning a Server Group to notification groups and schedules. To enable the feature for notification groups, navigate in the SA-Announce UI to Groups >> Create / Edit Groups >> General. To enable the feature for scheduled broadcasts, navigate to Schedules >> Scheduled Broadcasts >> General tab. See the Associate Server Groups section for further detail. Server Redundancy Feature Requirements: Requirement Description SA-Announce Version At least two SA-Announce servers running on SA-Announce or greater. All servers should be running the same SA-Announce version. Server OS Version All servers must be running on the same OS and bitness in Redundancy mode. We plan to address this in an upcoming version and allow mixed OS's to be used. SA-Announce Local Database Each SA-Announce server must be configured to use an SQL 2008 R2 SP1 or greater database instance on the local server. Remote databases are not supported in redundancy mode. Note: Existing installations will be required to install SQL 2008 R2 SP1 and move the 'SA-Announce 2.0' database instance via backup and restore. Once the database instance has been upgraded and restored, re-run SA-Announce configuration and supply the new instance name if necessary, completing configuration will then setup the redundancy subsystem. SQL 2008 R2 SP1 download links: 32-bit OS: SQL 2008 R2 SP1 (x86) Download Link 64-bit OS: SQL 2008 R2 SP1 (x64) Download Link

153 Server Redundancy 153 SQL Installation Requirements: After installing SQL 2008 R2 SP1, the following requirements must be met: 1. TCP/IP control must be enabled for the instance. On the application server navigate to Start > Microsoft SQL Server 2008 R2 >Configuration Tools >SQL Server Configuration Manager. Expand SQL Server Network Configuration. Under protocols for the instance enable TCP/IP. 2. Mixed mode authentication (SQL server and Windows) must be used. CUCM Authentication URL The CUCM Authentication URL must point to a load balanced URL. The load balancer should be configured with the authentication URL for each SAAnnounce server so the IP phones will always be able to authenticate notification commands as long as one SA-Announce server is alive. SA-Announce Cluster A Cluster is a primary server, (publisher), and one or more secondary servers, (subscribers). A server cluster must be configured to run redundancy. Visit the Creating A Cluster section for details. SA-Announce Server Groups At least one Server Group must be created to run redundancy. Visit the Creating Server Groups section for details. Server Group Association Notification groups must be assigned to a Server Group. Visit the Associate Server Groups section for details. External Phones If external phones are being used, then each server must have its own pool of unique external phones setup in the standard manner. See the Analog Paging System Integration section for additional details. IP Endpoint Registration IP endpoints such as IP speakers or desktop clients that register with SAAnnounce must register with the publisher when in redundancy mode. Subscribers will not register end-points. API usage Any server can be used when activating a group via the SA-Announce API. If the contacted server is not running the group, it will forward the request to the other severs in the cluster. Note: The request cannot be forwarded if there is no connectivity between servers.

154 SA-Announce User Guide Creating A Cluster Services >> Server Redundancy >> Servers A publisher and subscriber relationship is maintained to allow for data replication between servers in Redundancy mode. A publisher must be created with at least one subscriber. When the Redundancy feature has been activated, the subscribers will redirect SA-Announce management GUI requests to the publisher. All of the changes to the SA-Announce global data are performed on the publisher. The changes are pulled down by the subscribers in the Cluster. Certain local based web pages are available on the subscriber management interfaces, including Multicast Tests, External phone setup, and other local based functions. The redundancy feature should be setup using the SA-Announce UI (User Interface). Navigate to Services >> Server Redundancy >> Servers on the proposed publisher to begin. Creating a Publisher The Servers tab will be shown by default. The current server information will be listed in the Publisher panel. 1. The Name and Description for the publisher are populated with the Server Name and Server IP address by default. They can be modified at any time. A single SA-Announce server can be marked as a publisher without adding subscribers, however, the redundancy feature will not be active without adding subscribers. The service monitoring will run and make verify the service was started automatically, if it has stopped unexpectedly. 2. To activate the current Server as an Active Publisher and create a new Subscriber, press the Create Publisher button to make the current server the publisher. The Subscriber panel should appear, (see the following page,) and the Active Publisher icon will replace the Create Publisher button. 3. Click the Save button in the Publisher panel. IMPORTANT: Existing SA-Announce implementations should use the existing SA-Announce server which contains the notification groups as the publisher. This is the preferred method because users avoid having to recreate groups and system settings. When a server is made a publisher, all of its existing data will be replicated to the subscribers in the cluster. Subscribers added to the cluster will have their data deleted before the publisher data is replicated.

155 Server Redundancy 155 Creating Subscribers Once a Publisher has been activated/created, the Subscribers panel will appear in Subscribers section of the Servers page. IMPORTANT: Any existing SA-Announce configuration data will be deleted when adding a subscriber. Existing Groups or Settings on the server will be deleted. The exception to this is the external phone dialer pool, this is a per server entity and as such any existing external phone configuration information will not be wiped when adding the server as a subscriber. 1. To add subscribers, (one or more additional SA-Announce servers), click the dropdown menu in the Subscribers field and select the server. 2. Enter a Name for the server. 3. Enter a Description for the server. 4. Enter the IP Address. 5. Press the Save button in the Subscribers section. The server will be added as a subscriber and all of its existing data will be replaced with the data that exists from the publisher. The cluster of servers have been created. Review the Create Server Groups section for information on the following step(s). Note: Servers should have their Server Site setting set before they are added as a subscriber. On the proposed Subscriber Servers SA-Announce management interface, navigate to Services >> Broadcast Services >> Settings and set the Server Site setting to the appropriate CUCM site, (DP or CSS). This setting can also be set by manually altering the registry on the subscriber server at HKLM >> Software >> SynApps >> SAAnnounce >> serversite. It's important to make sure the supplied name of the DP or CSS precisely matches the name of the Device Pool or Calling Search Space on the CUCM when manually configuring the subscriber server.

156 SA-Announce User Guide Creating Server Groups Services >> Server Redundancy >> Server Groups After a Cluster has been created, servers are assigned to a prioritized list called a Server Group. At this point, Server Groups can be assigned to notification groups to enable the Redundancy feature. A Server Group can contain two or three servers. Once a notification group has been assigned a Server Group, the notification group will begin to run on the priority-1 server. If the priority-1 server experiences a fault, then the priority-2 server will begin to run the group. If a third priority server exists and both the priority-1 and priority-2 servers experience a fault, then priority-3 server will begin to run the group. When a server comes back online after experiencing a fault, it will resume responsibility for its notification groups. This is the auto failover process. Whether a notification group is resuming on a server or failing over to another server, there will only be a brief outage while the notification groups' virtual phone registers using the newly responsible server. Navigate to the Services >> Server Redundancy >> Server Groups tab to configure Server Groups. 1. Select a Server Group from the <..Add a New Server Group..> field. Publisher and Subscriber servers can be used in Server Groups. 2. Enter a server Group Name and Description in the provided fields. 3. Select servers from the Available Servers list and move them to the Selected Servers list using the blue arrows between the two fields. It is important to understand the Selected Servers field are in a prioritized order (highest priority on the top). Use the blue arrows to the right of the Selected Servers field to reorder the server priority. 4. Click the Save button to create the Server Groups. Server Groups must now be assigned to notification groups to enable the server redundancy feature. See the Associate Server Groups section for detailed information.

157 Server Redundancy Associate Server Groups Assigning a Server Group to notification groups and schedules are the final step to enabling the redundancy feature. Creating a Cluster and at least one Server Group is a prerequisite to this step. Assigning a Server Group to a Notification Group Navigate to Groups >> Create / Edit Groups >> General tab. 1. Select a notification group from the Select Group To Edit field. 2. The Server Group field is now visible and editable. Note: the Text notification group will not enable the Server Group field. 3. Select the Server Group from the dropdown list. Selecting a Server Group enables redundancy by linking the Server Group to the designated Notification Group. Note: If <None> is the selected Server Group, then the associated Notification Group will only run on the publisher and not have any fail over subscriber servers. 4. Click the Save Group button to save the changes.

158 158 SA-Announce User Guide Assigning a Server Group to a Scheduled Event Navigate to Schedules >> Create/Edit >> General tab. 1. Select a schedule from the Select Schedule To Edit field. 5. After a Publisher and Subscriber have been created, the Server Group field will be visible and editable. 6. Select the Server Group from the dropdown list. Selecting a Server Group enables redundancy by linking the Server Group to the designated Schedule group. Note: If <None> is the selected Server Group, then the associated Schedule group will only run on the publisher and not have any failover subscriber servers. 7. Click the Save Schedule button to save the changes.

159 Web Service (API) Part 17

160 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.

161 Web Service (API) 161 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. DispatchGroupStoredAudioModeByGroupName 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 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.

162 162 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 (SA-Announce 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.

163 Settings Part 18

164 SA-Announce User Guide Settings Services >> Broadcast Service >> 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.

165 AMBER Alert Settings Part 19

166 SA-Announce User Guide AMBER Alert Settings Services >> Broadcast Services >> 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.

167 AMBER Alert Settings 167 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.

168 168 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.

169 Weather Alert Settings Part 20

170 SA-Announce User Guide Weather Alert Settings Groups >> Create/Edit >> General 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 Enable (check) the Weather Alerts check box to display the 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 codes. Enter a state FIPS code to monitor an entire state. State FIPS codes end in 000.

171 Weather Alert Settings Enable Events 171 Make sure Warning, Watches or Advisory events are enabled in the Services >> Broadcast Services >> Weather Alert section described on the following page. Services >> Broadcast Services >> Weather Alert The Weather Alert tab on the Services >> Broadcast Service >> Weather Alert page contains Interval Timer settings, as well as Warnings, Watches and Advisories for configuring alerts. The interval settings are described in the table below: 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. By default, all Weather Alerts are deactivated. Review the list and select alerts that may apply to the organizations' geographic location. 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.

172 172 SA-Announce User Guide Sample Weather Alert: The image will contain a 'details' soft-key. Pressing the soft-key will bring up the full description of the alert.

173 Weather Alert Settings 20.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 173

174 174 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

175 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 175

176 Background Music Settings Part 21

177 Background Music Settings Background Music Settings Services >> Broadcast Services >> Background Music Settings The Background Music Settings section is used to configure the background music service parameters. This service requires a multicast music streaming source, such as the Syn-Apps Paging Relay. The Background Music Settings section is used to configure the background music service parameters. This service requires a multicast music streaming source, such as the Syn-Apps Paging Relay. Refer to Music Configuration in the Paging Relay Admin Guide. Once the streaming source is active, add the settings on the Background Music Settings page and then add a phone service on CUCM with the following URL: BackgroundMusic.aspx. Finally, subscribe phones to the service. Subscribed phones can activate the background music by selecting Services and then the name used when adding the phone service. See the Configure IP Phone Services section for information on setting up the phone browser. The Background Music Settings section contains the following settings: Background Music Setting Description Music Stream Name This setting controls the display name of the music stream. It will appear on phones accessing the stream. Music Stream IP Address Enter the IP address of the multicast background music stream. Valid multicast addresses are: 224.X.X.X thru 239.X.X.X. Music Stream Port Enter the port of the multicast background music stream. Must be RTP ports only. Valid port ranges are: thru

178 Syn-Apps Paging Relay Configuration Part 22

179 Syn-Apps Paging Relay Configuration Syn-Apps Paging Relay Configuration 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.

180 180 SA-Announce User Guide Paging Relay Setting Description Name 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 device's 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.

181 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.

182 Syn-Apps Desktop Notification Client Configuration Part 23

183 Syn-Apps Desktop Notification Client Configuration Syn-Apps Desktop Notification Client Configuration 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 Description Setting 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 Port The IP Address of the Syn-Apps Desktop Notification Client. This is not editable. The client listen port. This is not editable. Last Heart Beat The date and time of the last registration or heartbeat message from the Syn-Apps 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.

184 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 PC 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 SAAnnounce server will need unrestricted access to the DNC on this port. Voice Ports: The DNC RTP port range will need to be accessible by SA-Announce ( ). 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 User Manual for complete installation details.

185 Syn-Apps Desktop Notification Client Configuration Mac OS 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 SAAnnounce server will need unrestricted access to the DNC on this port. Voice Ports: The DNC RTP port range will need to be accessible by SA-Announce ( ). Multicast: The DNC will need to be connected to a multicast enabled network if SA-Announce is configured for multicast. 185

186 SA-Announce User Guide 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 User Manual 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.

187 Syn-Apps Desktop Notification Client Configuration 187 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 Client 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:

188 188 SA-Announce User Guide Configuration Using SA-Announce Web-Interface 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. After the DNC has been configured, navigate in the SA-Announce UI to Services >> Broadcast Services >> Advanced Setting. Use the Select a Setting dropdown list and choose the desktopclientalwaysontop setting from the available list. Click the Save button.

189 Syn-Apps Desktop Notification Client Configuration 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 Client 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.

190 Syn-Apps IP Speaker Configuration Part 24

191 Syn-Apps IP Speaker Configuration Syn-Apps IP Speaker Configuration Settings >> IP Endpoint Setup >> Syn-Apps IP The 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. 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. Navigate to Create Edit Groups >> General tab to configure. Mic The microphone gain for this speaker if it is a talk back model (10-100, default 40).

192 192 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 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 Syn-Apps 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 Each GPIO input can be set to activate an intercom to a selected phone with (talk 1 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 IP Address The Firmware Update fields can be used with Syn-Apps IP speakers or Paging Relays. Firmware Update: Firmware Image 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.

193 Syn-Apps IP Speaker Configuration 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 ooption 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.

194 194 SA-Announce User Guide 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 the page.

195 Syn-Apps IP Speaker Configuration 195 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.

196 Legacy Algo Speaker Configuration Part 25

197 Legacy Algo Speaker Configuration 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 Configuring Multicast in the Algo IP Speaker control panel Legacy Algo 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.

198 SA-Announce User Guide Legacy Algo IP 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 IP 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.

199 AND IP Speaker Configuration Part 26

200 SA-Announce User Guide AND IP Speaker Configuration Settings >> IP Endpoint Setup >> Syn-Apps IP The 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. 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

201 AND IP Speaker Configuration 201 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.

202 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.

203 AND IP Speaker Configuration 203 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 table to be directed to the AND user interface.

204 Atlas IP Speaker Configuration Part 27

205 Atlas IP Speaker Configuration 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 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 Atlas IP speaker registration see Atlas IP Speaker Setup.

206 206 SA-Announce User Guide 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.

207 Atlas IP Speaker Configuration Supported Atlas IP Speakers SA-Announce supports all Atlas IP speakers Atlas IP Speaker Setup This section describes the configuration of Atlas IP Speakers. 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 ooption 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.

208 208 SA-Announce User Guide 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 table to be directed to the Atlas user interface:

209 CyberData IP Speaker Configuration Part 28

210 SA-Announce User Guide 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 legacy CyberData speakers. 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. 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.

211 CyberData IP Speaker Configuration 28.1 Supported CyberData Speakers SA-Announce supports a variety of CyberData IP devices. These include but are not limited to: CyberData IP Speaker Model 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 Supported 211

212 SA-Announce User Guide 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.

213 Valcom IP Speaker Configuration Part 29

214 SA-Announce User Guide 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.

215 Valcom IP Speaker Configuration 215 Valcom VIP-102B Setup Tool System >> Network Settings The Valcom speaker settings are shown in the Valcom VIP-102B IP Solutions tool under the [Valcom] System >> Network Settings option Supported Valcom Speakers SA-Announce supports the entire Valcom IP speaker platform. These speakers include: Valcom IP Speaker Model 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) Supported

216 SA-Announce User Guide 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 IP Speaker Integration. 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.

217 Valcom IP Speaker Configuration 217 The Valcom group can now be used in SA-Announce notification groups and schedules. Navigate to Groups >> Create / Edit Groups >> Legacy IP. Add the Dial Code to the Valcom input field of the Legacy IP tab of a notification group. For further instructions, see IP Speaker Integration.

218 Alertus Configuration Part 30

219 Alertus Configuration 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.

220 220 SA-Announce User Guide 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.

221 Alertus Configuration 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.

222 Everbridge Configuration Part 31

223 Everbridge Configuration 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. Retype the password to confirm. 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.

224 SA-Announce User Guide Everbridge Setup 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

225 Everbridge Configuration 225 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.

226 Twitter Configuration Part 32

227 Twitter Configuration 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.

228 External Phone Integration Part 33

229 External Phone Integration External Phone Integration Settings >> External Phones This section describes how to setup the dialers for analog paging system integration. Dialers are virtual phones added to the Cisco Unified Communications Manager. When necessary, SA-Announce virtually takes the dialers off-hook and dials the overhead system. Experience with Communications Manager is required to properly configure this section. Specifically, a strong understanding of Device Pool / Region, CSS, and Partition parameters should be understood prior to configuration. For information on adding analog systems to a paging group see the External Phones section. The Settings >> External Phone Setup page allows automatic creation of the dialers used in the analog paging system integration. It is recommended to add a dialer for each simultaneous overhead system activation that can occur plus two for busy detection purposes. For example, if four sites each have one overhead system: 4 sites + 2 extra = 6 dialers required. All Dialers should have the same Device Pool and Line CSS (Calling Search Space). The Dialers act as a pool, because the dialers act as a pool and any one may be used for a specific notification group. In other words all dialers must be able to dial any overhead systems integrated with SA-Announce.

230 230 SA-Announce User Guide Theses parameters are required in the External Phone Setup page: External Phone Parameter Description Line Number Enter a unique line number for the virtual dialer phone. Partition Select a partition for the line to reside in. Lines require partitions to make them unique and to add control mechanisms. This setting does not affect the dialer functionality. Line CSS Select a Calling Search Space for the line to reside in. The CSS must contain the partition of the destination numbers you wish to dial. Device Pool Select a Device Pool that will insure a G.711 codec lookup when the dialer dials the destination numbers you wish to dial. See CUCM Region for more information. Press the Add Phone button to add the virtual phone to Communications Manager. Repeat this process to add more dialers to Communications Manager. To Delete a dialer phone, navigate to Settings >> External Phone Setup. Gather the MAC addresses or Line Numbers of phones to delete. Next, use the CUCM Administration to search for the specific phones. Use the CUCM Administration page to delete the desired phones and lines Supported Analog Systems SA-Announce supports all analog paging systems that integrate with Cisco Communications Manager. SAAnnounce supports single and multi-zone systems. To integrate single-zone systems, use the Syn-Apps Paging Relay hardware. Refer to the Analog / IP Configuration topic in the Paging Relay Admin Guide for more information Supported Analog Interfaces SA-Announce can connect to paging systems that are integrated with analog phone ports. Analog dialers such as FXS, FXO, E&M interfaces hosted and ISR gateways, VG224, VG248, and ATA's are supported.

231 Busy Detection Options Part 34

232 SA-Announce User Guide Busy Detection Options SA-Announce offers two modes to determine whether or not IP phone members of a notification group are busy. It is important to remember that only Emergency Notifications are delivered to busy endpoints. Standard notifications are not delivered to busy endpoints. Refer to the remaining sections to learn more about XML and TAPI Busy Detection features. Use the following table to determine which busy detect mode should be used: 34.1 Busy Detection Mode Description XML Busy Detection This is the default busy detection mode. SA-Announce uses the Cisco IP phone priority scheme for to detect busy calls. XML Busy Detection mode accommodates most installations. No additional setup is required for the XML mode. TAPI Busy Detection In this mode SA-Announce will use TAPI and the Cisco TSP to determine if the phones are busy. This mode is useful when there are many phones with shared lines or many phones with one shared line. There is additional setup required for this mode described in the TAPI Busy Detection section. XML Busy Detection XML Busy Detection is the default method SA-Announce uses to determine whether an IP phone is busy or idle. All Cisco IP phones have a priority scheme that allows SA-Announce to send phones commands that will only be executed if the phone is idle. All standard paging groups respect a busy status and will not interrupt active phone calls unless the Emergency Alert checkbox is enabled TAPI Busy Detection TAPI Busy Detection is used in cases where several phone lines are shared. When shared lines are placed on hold, all phones sharing the line appear "XML Busy," which is a false positive. Contact Syn-Apps Technical Support for additional information. The following steps are necessary to properly configure the Cisco TSP for use with Syn-Apps applications: TAPI Busy Detection Setup Description Determine Lines to Monitor The number of phone lines being monitored is important to consider when using TSP with Syn-Apps applications. Older versions of CUCM TSP can only monitor a maximum of 2,000 lines. Newer versions of CUCM can monitor more than 2,000. First determine the number of phones/lines must be monitored and divide by 2,000 to determine the number of TSP instances required. Each TSP instance requires its own unique application user with a unique set of phone lines to monitor. If more than one TSP is required then phones/lines must be partitioned across multiple users. Create Application User(s) Create an application user for each required TSP and partition the devices to monitor across them. Install and Configure TSP Install the Cisco TSP on the Syn-Apps application server. The number of required instances and the user information will be required in this step.

233 Busy Detection Options Create Application User A new application user must be created on the CUCM system before configuring Cisco TSP. The user account is used for access control. It contains a list of associated phones/lines which can be monitored by the application. To create a new application user perform the following steps: Application User Configuration Description Open CCMAdmin Browse to the CUCM CCMAdmin web interface. Application User Select User Management >> Application User from the CCMAdmin menu. Add New Click the Add New button. Configure New User Configure the following fields User ID Enter a meaningful User ID, such as CallAlertTSP1 Password Enter a Password and Confirm Password. Note the password for later use when configuring the TSP. Device Information Add Devices from Available Devices to Controlled Devices for the application user. These are the devices that will be monitored. Permissions Information Add permissions for the following groups: Standard CTI roles Final Steps Save Click the Save button to finalize changes.

234 234 SA-Announce User Guide Install and Configure TSP Once Applications User(s) are created on CUCM, the Cisco TSP can be installed on the Syn-Apps Application Server. To install the Cisco TSP on the Application Server perform the following: TSP Installation Description Open CCMAdmin Browse to the CUCM CCMAdmin web interface. Plugins Navigate to Applications >> Plugins in the CCMAdmin interface. Find Click Find to list the available plugins. Download Locate the Cisco TAPI Client row and click Download to download the installation file. Note that newer versions of CUCM will have two versions of the TAPI Client, one for 32-bit and one for 64-bit. Choose the version which matches the bitness of the application server. Install Start the installation by double clicking on the downloaded file. Number of Instances Enter the number of instances to install, (from 1 to 10), depending on the number of phones to monitor. See TAPI Busy Detection section. Click Next to continue. User and Manager Enter the User Id and Password of the application user that was created for this instance (Create Application User). Enter the CTI Manager(s) for this user. The CTI Manager is a CUCM that is running the CTI service. CTI Manager 1 is required, CTI Manager 2 serves as a backup if the primary listed CTI Manager is down. Click Next to continue. Media Driver and Other Click Next to accept the defaults and begin installation. Restart Restart the system to apply the changes. To configure or reconfigure the TSP perform the following steps: TSP Configuration Description Open Control Panel Open the Windows Control Panel. Phone and Modem Find Phone and Modem. For Windows 2003 select Phone and Modem options on Windows Advanced Tab Select the Advanced tab in Windows Phone and Modem options. Select a TSP Double click the TSP to be configured. One will be listed for each instance that was installed, starting with CiscoTSP001.tsp. Configure the TSP Change options such as user name and password or CTI manager. Press OK or Apply to save changes. In most cases, restarting the Syn-Apps services using the TSP will push the settings changes into the Syn-Apps application.

235 Advanced Paging Configuration Part 35

236 SA-Announce User Guide Advanced Paging Configuration This section illustrates 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 IGPM or CGPM on switches.

237 Advanced Paging Configuration 35.2 Multi-Site Centralized SA-Announce Server 237

238 SA-Announce User Guide SA-Announce High-Level Protocol Use

239 Troubleshooting Guide Part 36

240 SA-Announce User 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 Broadcast 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. 5) Phone Services - Consult this section for Phone Service and API issues. Groups Directory - Issues with the SA-Announce groups directory phone service. Web Dialer - Issues with the SA-Announce web dialer phone service. API - Issues with the SA-Announce API.

241 Troubleshooting 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. The Installation / Configuration section is divided into the following subsections: 1. Windows Environment Issues: This subsection describes issues that commonly occur with the application servers Windows environment. 2. Installation Issues: This subsection describes issues that commonly occur when installing SAAnnounce. 3. Licensing Issues: This subsection describes issues that commonly occur with SA-Announce licensing. 4. Configuration Issues: This subsection describes issues that commonly occur when configuring SAAnnounce using the SA-Announce configuration utility 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.

242 242 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. SynApps.license.txt will not be seen as a license. 2) Using an Inactive 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 Technical Support. 3) Licensed Phone Count Exceeded: a) Phones Total Licensing Model: If the licensed phone count is exceeded in this licensing model then SAAnnounce sees more devices on the configured CUCM cluster than the license allows. Any other device or phone on the CUCM cluster will be counted towards the licensed phones. Removing unused devices in the CUCM, 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.

243 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) Communications Manager Authentication: The Communications Manager Authentication configuration page requires the user to enter CUCM credentials that have AXL API access. The AXL API is the interface used to gather data from CUCM. Recommended credentials are the top level ccmadmin credentials (usually administrator or ccmadministrator). The credentials are checked against all listed CUCMs, a basic AXL command is run and if any errors occur configuration will fail. Common reasons for errors include: AXL Web Service not running: All CUCMs listed in configuration must have the AXL Web Service running. Check this at CUCM Serviceability>Tools>Control Panel: Feature Services, the Cisco AXL Web Service must be running. No Connectivity: Firewall etc blocking access, see the Firewall Ports section of the manual. For new installs, this is the first time the application tries to connect to the CUCM or anywhere on the network for that matter. Wrong CUCM Version Selected: Make sure the proper CUCM version checkbox is checked on the first page of configuration. User Exists but has No Permission: The user must be an "application user" on CUCM 5+. The user must have "Standard AXL API Access" permissions assigned. 4) 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: 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

244 244 SA-Announce User Guide 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. SQL does NOT exist on Application Server: Install SQL on the application server, note the instance name you create. Any authentication mode is fine. Use a non-local DB Instance: The non-local SQL server must allow the application server access, (account used during configuration). Regedit HKLM >> Software >> SynApps >> SA-Announce >> sqlserver to the name of the server to use. Re-run configuration.

245 Troubleshooting Guide 245 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. Verify the following configuration properties of the SA-Announce virtual directory: Execute Permissions: scripts only or scripts and executables. ASP.NET is set to 2.0 (c) Web Service Extensions: ASP.NET 2.0 must be enabled under IIS Management >> Web Service Extensions. (d) Impersonation Error: If bad account credentials have been used to configure the application an ASP.NET error will occur on the website, a red highlighted line in the error will contain an "identity impersonate" tag. Re run configuration while logged on to the application server as an administrator and supply the credentials at Application Server Credentials page. If the password supplied during configuration had a typo this error will occur. 2) Service Will Not Start: See the Service Start Issues subsection. If errors occur in these areas, call Syn-Apps Technical Support at , Option 2.

246 246 SA-Announce User 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 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. Download the Universal

247 Troubleshooting Guide 247 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. 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 installed by SAAnnounce, continue with the SA-Announce Configuration. If the SYNAPPSENT instance is not installed, then the existing SQL will

248 248 SA-Announce User Guide 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.. 2. SA-Announce update process autom atically installing SQL Server 2008 R2.

249 Troubleshooting Guide 3. SQL Dow nload Com plete - SA-Announce is ready to install 249

250 250 SA-Announce User 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 Meet 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.

251 Troubleshooting Guide 251 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.

252 SA-Announce User 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 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. The default Log Level is Error, however, the logging level can be changed on the Services >> Broadcast Services >> Log Level >> Web Site Minimum Error Level setting. Sample log excerpts are shown below using the "ERROR" logging level. The samples show various errors that can occur along with a brief explanation. Comments are shown in Grey.

253 Troubleshooting Guide Com m on Errors: <log file excerpts and explanations> 253

254 254 SA-Announce User 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 Creation Errors If an error was encountered while creating a group, the error will be detailed in the GUI log file. A few of the common errors are listed below: 1) No Connectivity to CUCM: There must be connectivity to CUCM when adding an audio group line and device to the CUCM. Otherwise, a timeout will occur. 2) Out of device licenses on CUCM (version 5+): By default, a VIP-30 device is used on CUCM for each audio group created. The following error appears when adding a group: AXL returned an error in response. SOAP-ENV:ClientAllocated licenses consumed by used and pending. Please upload additional licenses (a new license file) and try again. If this error occurs, one of the following solutions must be used: (a) Remove unused devices from CUCM. (b) Purchase more DLU's form Cisco. (c) Install the Syn-Apps device pack: See the Adding Device Pack section of this manual for details. Groups will no longer require DLU's but all current audio groups will have to be recreated. 3) CUCM 4.X add device bug: Attempt to add a device with non-unique GUID. <CUCM Patch required, details...> When adding audio groups, a line and device are first added to CUCM. Next, the system data is refreshed. If there is an error when adding the device, the line will continue to exist on CUCM but SA-Announce will not know about it unless a refresh-data has been run manually. In this case, any attempts to add the group again with the same line will create an error: line exists. After the system refreshes and SA-Announce is aware of the line, a warning (line number in use in this partition) will be given if the line is used in a group. Enable the Force Use checkbox to continue and add the group. 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 service has not been started or restarted after the group was added. The service must be restarted after adding a group in order for the group to become active. 2) The group was added with an improper partition or device pool. To change the DP/CSS of a group that has already been added, use ccmadmin >> device >> phone. a) Partition: Notification group phones must be added in a partition that is contained in the CSS of calling phones. b) Device Pool: Notification groups must be added in a Device Pool that when called will yield a G.711 codec lookup. In some cases, for example customer uses G.729 online, it is necessary to create a new device pool / region that is G.711 only, and then put the paging groups in that Device Pool. c) Furthermore, if registration groups are in use on the CUCM, the group must be added in a Device Pool that is allowed to register with the primary listed CUCM in SA-Announce configuration. This problem shows as Error: DB Config in the broadcaster logs. 3) The group phone is not registered. Check CUCM ccmadmin >> device >> phone to see if the group

255 Troubleshooting Guide 255 phone is registered. The broadcaster logs can also be a resource. 4) 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. If some or all IP phones are missing from the IP phones tab then data has not been gathered from the CUCM or an error has occurred while gathering data. Consult the GUI log file after running a refresh to check for errors. If no errors occur see item 2 below. 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 or poll 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. In the case of Cisco 7940 and 7960 model phones, the Cisco IP phone services SDK must be installed on the application server in order for those types to receive images <link>. 2. Text messages only arrive at certain end point types: Text messages will only be sent to group devices that can receive text. 3. Polls only arrive at certain end point types: Polls will only be sent to IP phone group devices Other This subsection describes other common issues that can occur when using the SA-Announce user interface. External Phone Setup If errors occur while adding external phones on the Settings >> External Phones setup page, consult the Group Creation section for errors adding a group. The same actions are being performed here, adding a device and line to CUCM. Keep in mind that the settings for external dialers have slightly different requirements than group phones. The dialers will be used to virtually dial external numbers so they must have settings that allow them to dial this number with a G.711 codec. Common configuration problems include: 1. External phones must have unique lines attached to them. Do not add an external phone with the line number of a system you intend to call or any existing line. 2. External phones are utilized in a pool, you never know which dialer will be used to dial which external number. External phones must be able to reach all possible external destinations intended for integration. 3. External phones dial numbers, meaning CSS (Calling Search Space) rules apply. 4. External phones must get a G.711 codec lookup when dialing external systems. For example, the external phones Device Pool must be set so a G.711 region is obtained. If problems are experienced when trying to use external phones, such as connecting to an analog system, consult the Analog Paging System Integration section for full instructions on creating external dialers with the proper settings. 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. When a Site is altered in the Settings >> Multicast Settings >> Sites tab, the default settings will not apply to the Site unless the Back to Defaults button is pressed and the Site is saved. 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.

257 Troubleshooting Guide 257 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: This subsection describes common issues that occur when trying to start the SA-Announce Broadcaster service. Consult this subsection when the SA-Announce broadcaster service fails to start. 3. Phone Command Issues: This subsection describes common issues that occur when the broadcaster service sends commands to phones. Consult this subsection when phones are not receiving commands (IE not lighting up, HTTP timeout,..., etc..). 4. Audio Issues: This subsection describes common issues that occur when the broadcaster service sources audio to phones. Consult this subsection when phones (or other endpoints) are receiving commands (IE lighting 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 supposed to go off, 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 Broadcast 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 Broadcast 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 Broadcaster Log Files This subsection describes the Broadcaster Service log files. Consult this subsection when experiencing broadcaster service issues. The log files to consult for broadcaster issues are located at C:\Program Files\SynApps\SAAnnounce\Broadcaster\. There are 5 files named Trace*date-stamp*.txt one for each of the last 5 service starts. Sample log excerpts are shown below using the "SIGNIFICANT" logging level, this is the default logging level. The logging level can be changed on the Services >> Broadcast Services >> Service Log Level tab, File Minimum Error Level setting. The samples shows a basic page with no errors and with an error. If multiple pages are being sourced by the system at one time then the logs will become fragmented and very hard to read. The samples below are excerpts. The broadcaster log file will generally start with the service settings, followed by the registration of paging groups and finally the actual paging activity. Paging activity is always denoted by a Call Info message. Searching for Call Info will find the start of each page or external dialer call completing. Comments are shown in Grey. Areas of interest are commented or colored with notes below the samples. Good Page, no errors: 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : ->Received CallInfoMessage 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : Call Info: Calling Party Name: <Caller Name> Calling Party:5067 <Caller Number> Called Party Name: <Group Name> Called Party: 2308 <Group Number> 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : ->Received CallInfoMessage 02/15/10 18:14:26 : 7a8 4f9619c MulticastVirtualPhone : Sent StationOpenReceiveChannelAck 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : ->Received CallInfoMessage 02/15/10 18:14:27 : ef0 4f9619c MulticastVirtualPhone : Opening slave phones' RTP ports for send and receive 02/15/10 18:14:27 : ef0 4f9619c MulticastVirtualPhone : ~shouldmulticast broadcasttype = 2 02/15/10 18:14:27 : ef0 4f9619c MulticastVirtualPhone : multicasting started from [ ], receivingport= /15/10 18:14:27 : 115c 4fa0b9c ExecuteAsync : runsync results: total[38] success[36] busy[2] error[0] 02/15/10 18:14:34 : 7a8 4f95be0 SkinnyDispatcher : ->Received StationCloseReceiveChannelID 02/15/10 18:14:34 : 7a8 4f9619c MulticastVirtualPhone : onstationcallstate closing group 02/15/10 18:14:34 : 7a8 4f9619c MulticastVirtualPhone : Multicasting stopping 02/15/10 18:14:35 : fa0f2c ExecuteAsync : runsync results: total[38] success[38] busy[0] error[0] Page w ith one error: 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : ->Received CallInfoMessage 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : Call Info: Calling Party Name: <Caller Name> Calling Party:5067 <Caller Number> Called Party Name: <Group Name> Called Party: 2308 <Group Number> 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : ->Received CallInfoMessage 02/15/10 18:14:26 : 7a8 4f9619c MulticastVirtualPhone : Sent StationOpenReceiveChannelAck 02/15/10 18:14:26 : 7a8 4f95be0 SkinnyDispatcher : ->Received CallInfoMessage 02/15/10 18:14:27 : ef0 4f9619c MulticastVirtualPhone : Opening slave phones' RTP ports for send and receive 02/15/10 18:14:27 : ef0 4f9619c MulticastVirtualPhone : ~shouldmulticast broadcasttype = 2 02/15/10 18:14:27 : ef0 4f9619c MulticastVirtualPhone : multicasting started from [ ], receivingport=24588

261 Troubleshooting Guide /15/10 18:14:32 : bf604 AvvidHttp : ERROR post: Exception*: The operation has timed out STACK TRACE: at AVVID. PhoneControl.PhoneExecute.postXML(String phoneipaddress, String content, String username, String passw ord, TimeSpan w aittime, Int32 retrynumber) at AvvidHttp.post(basic_string<char\,std::char_traits<char>\,std::allocator<char> >*, basic_string<char\,std::char_traits<char>\, std::allocator<char> >* serveripaddress, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* content, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* username, basic_string<char\,std::char_traits<char>\,std:: allocator<char> >* passw ord, Int32 retriescount, Int32 retrydelay) 02/15/10 18:14:32 : fa2414 PhoneXml : ERROR [SEP001F9E26A392, ] runsync: exception&: [post: Exception*: The operation has timed out STACK TRACE: at AVVID.PhoneControl.PhoneExecute.postXML(String phoneipaddress, String content, String username, String passw ord, TimeSpan w aittime, Int32 retrynumber) at AvvidHttp.post(basic_string<char\,std::char_traits<char>\,std::allocator<char> >*, basic_string<char\,std::char_traits<char>\, std::allocator<char> >* serveripaddress, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* content, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* username, basic_string<char\,std::char_traits<char>\,std:: allocator<char> >* passw ord, Int32 retriescount, Int32 retrydelay) 02/15/10 18:14:32 : 115c 4fa0b9c ExecuteAsync : runsync results: total[38] success[35] busy[2] error[1] 02/15/10 18:14:34 : 7a8 4f95be0 SkinnyDispatcher : ->Received StationCloseReceiveChannelID 02/15/10 18:14:34 : 7a8 4f9619c MulticastVirtualPhone : onstationcallstate closing group 02/15/10 18:14:34 : 7a8 4f9619c MulticastVirtualPhone : Multicasting stopping 02/15/10 18:14:35 : fa0f2c ExecuteAsync : runsync results: total[38] success[38] busy[0] error[0] *Note: shouldmulticastbroadcasttype=n show s w hich multicast mode has been chosen for this group: 1) Broadcast type unicast: the page w ill be unicast. 2) Broadcast type multicast local: the page w ill use the local multicast address for the source site. 3) Broadcast type multicast site-to-site: the page w ill use the site-to-site multicast address for the source site. **Note: total[38] success[38] busy[0] error[0] results line is show n tw ice for each page, once for the page start commands and once for the page stop commands. In the case w here there is an error in the start commands like HTTP timeout that does not also occur in the stop commands it is safe to assume the netw ork has dropped the packet for the start but not the stop. ***Note: The operation has timed out is show n tw ice (from tw o different levels of the service). The second listing contains a phone name (MAC) and IP address. When an error like this occurs the Phone Command Issues section should be consulted. Note: The broadcaster service often instructs IP Phones to get an SA-Announce web page, if errors occur on this web page they will be contained in the GUI log file. Always consult the broadcaster logs first, but if no clues can be found it is a good idea to check the other log files, GUI log file and configuration log file.

262 262 SA-Announce User Guide End Point Command Issues This subsection describes common problems that occur when sending phones and other endpoints commands. Consult this section when endpoints are not responding properly to the commands they are being sent. For example, when sending a standard audio command to an Cisco 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 endpoint 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. Cisco IP Phones: There are a number of basic requirements that must be met in order for Cisco phones to receive commands properly, they are listed here: 1. Application server has access to port 80 on the phones (firewall / proxy). 2. Phones have the SA-Announce authentication URL and access to it (port 80 on the application server). See the Authentication URL section of the manual for details on setting up the authentication URL. Verify the authentication URL on the phones web page <IE browse to the phones IP address>. 3. Phone IP not known: The phone must be registered and SA-Announce must know its IP. Verify by navigating to Services >> Troubleshooting Tests >> IP Phone Tests, if the phone appears in the list, then its IP is known. If the phone is registered and the IP is not known try refreshing first. If the issue persists, check the GUI Log File for errors. One known error is CUCM 4.x AXL RiS Errors, the log file will show the following: "The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF StackTrace:" If this occurs even when using the top level ccmadministrator account, turn off MLA (Multi-LevelAdministrator) or CUCM patch required UCM Phones have web access enabled on the ccmadmin >> device >> phone settings page (or HTTP timeout will occur on all commands). 5. Phones must be XML enabled model types <link to list>. 6. Phones have a bad firmware (rare for basic connectivity). 7. Phones are in a bad state and need power off reboot (rare). The best way to test for basic connectivity of IP phones is by using the server-to-phone multicast test. Navigate to: Settings >> Multicast Settings >>Server to Phone Multicast Test. Even if multicast is not available, this test will exercise the command channels and show the response in the GUI. If CiscoIPPhoneError = 4 is returned by a command, an authentication error has occurred. Continued on the following page.

263 Troubleshooting Guide 263 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 S e ttings > > IP End P oint S e tup > > S yn-apps IP. See Syn-Apps IP Speaker Setup and the Installation topics in the Paging Relay Admin Guide for setup and manual registration details. 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.

264 264 SA-Announce User 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. Unicast Audio: Unicast audio will be used by default, if multicast has been enabled on the Settings >> Multicast Settings >> Default or Sites page then proceed to the multicast audio section below. When unicast audio is in use and end points are receiving commands but no audio is heard there are a few likely causes: 1. A firewall or other network security software is in use and blocking the audio ports. 2. The SA-Announce server does not have access to the voice VLAN. 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 Settings >> Server to Phone Multicast Test. See the Multicast Configuration section of the manual for more detail. Note: To determine whether issue is Network related or Application Server related, run a wire shark trace on the application server while paging. If the multicast audio appears in the trace, (Filter: ip.addr== or defaults), then the application server is sourcing the audio. The problem is likely due to multicast configuration on the network. If the audio does not appear, then a firewall is likely blocking it on the application server. Poor Audio Quality / Choppy Audio: Poor audio quality or choppy audio are generally due to the following: 1. Lack of bandwidth: This is the most common cause of poor audio quality, especially in unicast mode where 80kb/s bandwidth is required for each active endpoint. 2. Bad custom audio file: If a custom audio file is in use and there is poor audio quality, it is generally due to bad encoding on the audio file. The proper audio file format is: PCM 8kHz 8-bit mono. Test using a stock audio file or live audio to see if the issue persists. If not, it is certainly the audio file itself. 3. Bad device: In a small number of cases the issue could be due to a bad device. Try plugging a good device into the same port to verify that network issues are not the root cause.

265 Troubleshooting 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.

266 SA-Announce User Guide Phone Services This section describes common issues that can occur with the SA-Announce phone services and the SAAnnounce API. Consult this section when problems occur when using the SA-Announce phone services for Groups Directory, Web Dialer, or the SA-Announce API. Errors that occur in these areas will be logged to the GUI Log File or the Broadcaster Log Files depending on where the error occurs in the processing. If an error occurs in the phone service menu system or API, the GUI Log File will contain the error. If an error occurs in the paging functionality, the Broadcaster Log Files will contain the error. There are two subsections presented: 1. Groups Directory: Describes common problems that can occur with the groups directory phone service. 2. Web Dialer: Describes common problems that can occur with the web dialer phone service. 3. API: Describes common problems that can occur with the SA-Announce API Groups Directory The groups directory provides a phone service directory of the groups available on the system. Groups are listed along with their associated group phone number. Selecting a group will cause the phone to speed dial the group and the user will be connected with it. If the directory is not visible to phones make sure the setup procedure has been performed and the phone in question is subscribed to the service. See the Notification Group Directory section of the manual for details. If the groups directory itself functions okay and lists the groups and associated numbers but a problem exists when selecting an item, then see the Broadcaster Service section for troubleshooting info. Other common issues that can occur with the groups directory phone service are: 1. Broadcaster mot running: The broadcaster service must be running or dialing groups will give a fast busy. 2. All groups are shown to all users: This is the default mode of the directories. The accessing phone can be changed to show only its' membership to groups. To enable this setting, see the Notification Group Directory section of the manual.

267 Troubleshooting Guide Web Dialer The Web Dialer provides a phone service that lists the configured notification groups and allows them to be activated without making a phone call. This can be an important concept on CUCM systems because phones on a call cannot be made to transmit. The Web Dialer should be used to facilitate localized multicast paging when multicast is not available on the WAN. In this case, the source paging phone which activates the Web Dialer group, is instructed to transmit multicast audio to the destination phones which should all be local to the source. This allows for local multicast paging at sites that do not contain an SA-Announce paging server. For information of setting up the web dialer service see the Web Dialer Directory section of the manual. The main issues that can occur with this implementation are: 1. If the group is dialed the server multicast mode will be used. The group must be activated using the Web Dialer service or a Phone Service URL. 2. The group must be closed by the "caller" using the end-page softkey. For most phone models, an SAAnnounce Advanced Setting can be enabled that will allow the source caller to hang-up to end the page. Note that this will not work for Cisco models 7920/7921/7925. We have requested this feature be added to these phones. The setting can be changed at Services >> Broadcast Services >> Advanced Settings. Set the useciscostartmedia setting to true to enable the feature. 3. All groups are shown to all users: This is the default mode of the directories. It can be changed to show only groups that the accessing phone is a member of. To enable this setting, see the Web Dialer Directory section of the manual API The SA-Announce API provides a web service that can be accessed to perform many SA-Announce functions like sending text, initiating emergency alert notifications and manually registering IP speakers. The available methods can be enumerated by browsing to SAAnnounceAPI.asmx. The methods can also be invoked by selecting a method and then filling out the appropriate data and pressing the Invoke button. Note that methods can only be invoked in this manner when browsing from the application server. Use manual invocation to test the API or to manually register IP speakers. Errors that occur in the API will be logged to the GUI Log File or the Broadcaster Log Files depending on where the error occurs in the processing. If an error occurs in the API itself the GUI log file will contain the error. If an error occurs in the paging functionality the broadcaster log files will contain the error. Common issues that can occur when using the API include the following: 1. Bad Configuration: The server accessing the API is not a member of the Servers Allowed to Access the SA-Announce API. If this is the case the server will not be able to access secure methods like initiating an emergency alert. To add servers, navigate to: Services >> Broadcast Services >>Settings. 2. Broadcaster Service Not Running: The broadcaster must be running in order for methods that actuate the broadcaster to succeed. 3. Firewall / ACL: The server accessing the API does not have access to the SA-Announce server port 80.

268 Help and Support Part 37

269 Help and Support 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.

270 SA-Announce User Guide 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.

271 Help and Support 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.

272 2812 N Norwalk Suite 112 Mesa, AZ Phone: (866) Fax: (866) [email protected]