SA-Announce Notification System User Manual Version 8.0.0 ©2009 Syn-Apps L.L.C

Syn-Apps L.L.C. was founded in 2000 as a consulting firm focused on developing software for IP telephony. Since that time Syn-Apps has more than tripled in size and has expanded its consulting services to include enterprise application development. We believe that our relatively small firm is able to fulfill the needs of our customers more efficiently and inexpensively than our larger competitors.

Syn-Apps has an extensive knowledge base in numerous technologies, including .NET, C#, VB.Net, SQL Server, Java, C++ and other mainstream development tools. Syn-Apps additionally 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 employs one of the Cisco Systems Engineers that was responsible for the network development and design 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 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. Contents 3 Table of Contents

Part 1 SA-Announce Overview 9 Part 2 Application Features 12 Part 3 Manual Conventions 15 Part 4 System Requirements 17 1 Applic..a..t.i.o..n.. .S..e..r..v.e..r.. .R..e..q..u..i.r.e..m...e..n..t.s...... 18 Window s 2003.. .S..e...r.v..e...r...... 19 Window s 2008.. .S..e...r.v..e...r...... 20 Disabling U.A...C...... 21 Disabling P.u..b..l.ic.. .F..i.r.e..w....a..ll...... 22 Disabling IE.. .E..n..h..a..n..c..e..d.. .S..e..c..u..r.i.t.y...... 23 Creating A.S..P..N..E..T.. .U...s..e..r. .A...c..c..o..u..n..t...... 24 Installing IIS...... 25 Installing A.S..P....N...E..T...... 26 2 Cisco. .C..o..m...m...u..n..i.c..a..t.i.o..n..s. .M...a..n..a..g..e..r. .R..e..q..u..i.r..e..m...e..n..t.s...... 27 Communicatio...n..s.. .M....a..n..a..g..e...r. .3....x...... 28 Communicatio...n..s.. .M....a..n..a..g..e...r. .4....x..,. .5....x.. .,. .6....x..,. .7....x..,. .8....x...... 28 Adding Dev..i.c..e.. .P..a..c..k.. .(.C..M... .5....x..,. .6....x..,. .7....x..,. .8....x..)...... 29 Communicatio...n..s.. .M....a..n..a..g..e...r. .E..x..p...r.e...s..s...... 30 3 Netwo..r.k.. .R..e..q..u..i.r..e..m...e..n..t.s...... 31 Firew all Ports...... 31 Multicast Req.u..i.r..e..m....e..n..t..s...... 32 Part 5 Installation Procedure 34 Part 6 Configuration Utility 36 Part 7 Post Configuration Steps 39 1 Authe.n..t.i.c..a..t.i.o..n.. .U..R...L...... 40 2 IP Ph.o..n..e.. .S..e..r.v..i.c..e..s...... 41 Part 8 Initial Application Configuration 43 1 Applic..a..t.i.o..n.. .L..o..g..i.n...... 44 2 Servic..e.. .C..o..n..f.i.g..u..r..a..t.i.o..n.. .O..p..t.i.o..n..s...... 45 Advanced Set.t.i.n...g..s...... 47 Phone Feature...s...... 48 3 Multic..a..s.t. .C..o..n..f.i.g..u..r..a..t.i.o..n...... 49 4 User M...a..n..a..g..e..m...e..n..t...... 52 5 IP Ph.o..n..e.. .T..e..s.t.s...... 55 Part 9 Notification Group Configuration 58 1 Notific..a..t.i.o..n.. .G...r.o..u..p.. .T..y..p..e..s...... 59

3 4 SA-Announce User Guide

Ad Hoc ...... 61 Auto Confere.n..c..e...... 62 Emergency Al.e...r.t...... 66 Holler ...... 67 Normal ...... 68 RecordNPlay ...... 69 Respond ...... 70 Schedule ...... 71 Text ...... 72 Wokkie Tokki.e...... 73 2 Notific..a..t.i.o..n.. .G...r.o..u..p.. .S..e..t.u..p...... 74 3 Email...... 76 4 IP Ph.o..n..e..s...... 77 5 Deskt.o..p.. .C..l.i.e..n..t.s...... 78 6 Extern..a..l. .P...h..o..n..e..s...... 79 7 IP Sp.e..a..k.e..r..s...... 80 8 Pagin.g.. .R...e..l.a..y.s...... 81 9 Legac..y.. .I.P.. .S..p..e..a..k..e..r.s...... 82 10 Beaco..n..s...... 83 11 Mass .N..o..t.i.f.i.c..a..t.i.o..n...... 84 Part 10 Creating Emergency Alert Groups 86 Part 11 Creating Schedules 90 1 Sched..u..l.e.. .O...v.e..r..r.i.d..e..s...... 92 Part 12 Sending A Text Message 94 1 Messa..g..e.. .B..r.o..w...s..e..r...... 96 Part 13 Server Redundancy 98 1 Creat.i.n..g.. .A.. .C..l.u..s..t.e..r...... 99 2 Crea.t.i.n..g.. .S...e..r.v..e..r. .G..r..o..u..p..s...... 102 3 Asso.c..i.a..t.e.. .S..e..r.v..e..r. .G...r.o..u..p..s...... 103 Part 14 Web Service (API) 105 Part 15 Email Settings 109 Part 16 Amber Alert Settings 111 Part 17 Weather Alert Settings 114 1 Wea.t.h..e..r. .A...l.e..r.t. .S..u..p..p..o..r.t.e..d.. .E..v..e..n..t.s...... 116 Part 18 Background Music Settings 120 Part 19 IP Phone Services Configuration 122

1 Notif.i.c..a..t.i.o..n.. .G..r..o..u..p.. .D..i.r.e..c..t.o..r.y...... 123 2 Web. .D..i.a..l.e..r.. .D..i.r.e..c..t.o..r.y...... 124 3 Phon..e.. .M...e..s.s..a..g..e.. .B..r.o..w...s..e..r...... 126 4 7921./.2..5./.2..6.. .-. .P..u..s..h..-.t.o..-.T..a..l.k...... 127 5 Phon..e.. .S..e..r..v.i.c..e.. .U..R...L...... 128 Part 20 Paging Relay Configuration 131 1 Supp..o..r.t.e..d.. .P...a..g..i.n..g.. .R..e..l.a..y..s...... 133 2 Pagi.n..g.. .R..e..l.a..y.. .S..e..t.u..p...... 133 Part 21 Syn-Apps IP Speaker Configuration 137 1 Supp..o..r.t.e..d.. .S...y.n..-.A...p..p..s. .I.P.. .S...p..e..a..k.e..r..s...... 139 2 Syn-.A..p..p..s.. .I.P.. .S..p..e..a..k..e..r. .S..e..t.u..p...... 139 Part 22 Desktop Notification Client Configuration 143 Part 23 AND IP Speaker Configuration 145 1 Supp..o..r.t.e..d.. .A...N..D.. .I.P.. .S...p..e..a..k.e..r..s...... 147 2 AND. .I.P.. .S..p..e..a..k..e..r. .S..e..t.u..p...... 147 Part 24 Valcom IP Speaker Configuration 151 1 Supp..o..r.t.e..d.. .V...a..l.c.o..m... .S...p..e..a..k.e..r..s...... 152 2 Valc.o..m... .I.P.. .S..p..e..a..k..e..r. .S...e..t.u..p...... 153 Part 25 CyberData IP Speaker Configuration 156 1 Supp..o..r.t.e..d.. .C...y.b..e..r..D..a..t.a.. .S..p..e..a..k..e..r.s...... 157 2 Cybe..r.D..a..t.a.. .S...p..e..a..k.e..r.. .S..e..t.u..p...... 158 Part 26 Alertus Configuration 161 1 Supp..o..r.t.e..d.. .A...l.e..r.t.u..s. .D...e..v.i.c..e..s...... 163 2 Alert.u..s.. .D..e..v..i.c..e.. .S..e..t.u..p...... 163 Part 27 Everbridge Configuration 165 1 Ever.b..r.i.d..g..e.. .S..e..t.u..p...... 166 Part 28 Facebook Configuration 168 Part 29 Twitter Configuration 170 Part 30 Analog Paging System Integration 172 1 Supp..o..r.t.e..d.. .A...n..a..l.o..g.. .S..y..s.t.e..m...s...... 174 2 Supp..o..r.t.e..d.. .A...n..a..l.o..g.. .I.n..t.e..r.f.a..c..e..s...... 174 Part 31 Busy Detection Options 176

5 6 SA-Announce User Guide

1 XML. .B..u..s..y. .D...e..t.e..c.t.i.o..n...... 176 2 TAPI. .B...u..s.y.. .D..e..t.e..c..t.i.o..n...... 176 Create Appli.c..a..t.i.o..n... .U..s..e...r...... 178 Install and Co...n..f.i.g...u..r..e.. .T..S...P...... 179 Part 32 Information Center 181 Part 33 Custom Wave File Upload 184 Part 34 Customizing Audio Feedback 187 1 Audi.o.. .F..i.l.e.. .D..e..s..c..r.i.p..t.i.o..n..s...... 187 Part 35 Advanced Paging Configuration 191 1 SA-A..n..n..o..u..n..c.e.. .M...u..l.t.i.c..a..s.t. .R...o..u..t.e..r./.S..w...i.t.c..h.. .C..o..n..f.i.g..u..r.a..t.i.o..n...... 191 2 Mult.i.-.S..i.t.e.. .C..e..n..t.r.a..l.i.z..e..d.. .S..A...-.A..n..n..o..u..n..c..e.. .S..e..r.v..e..r...... 192 3 SA-A..n..n..o..u..n..c.e.. .H...i.g..h..-.L..e..v.e..l. .P...r.o..t.o..c..o..l. .U..s.e...... 193 Part 36 Troubleshooting Guide 195 1 Insta.l.l.a..t.i.o..n.. ./. .C...o..n..f.i.g..u..r.a..t.i.o..n...... 196 Window s Env.. .I.s...s..u..e...s...... 197 Installation Is..s...u..e..s...... 198 Licensing Iss...u..e..s...... 199 Configuratio.n.. .I.s..s...u..e..s...... 200 2 Web. .I.n..t.e..r.f.a..c..e.. .(.G...U..I.)...... 203 GUI Log File ...... 204 Group Creati.o...n...... 205 Text Messag..e...... 207 Other ...... 208 3 Broa.d..c..a..s..t.e..r. .S..e..r.v..i.c..e...... 209 Broadcaster .L...o..g.. .F..i.l.e...s...... 210 Service Start. .I.s...s..u..e...s...... 212 End Point Co.m....m...a..n...d.. .I.s..s...u..e..s...... 213 Audio Issues...... 215 4 Sche..d..u..l.e..r. .S..e..r..v.i.c..e...... 216 5 Phon..e.. .S..e..r..v.i.c..e..s...... 217 Groups Direc..t.o...r.y...... 218 Web Dialer ...... 219 API ...... 220 Part 37 Help and Support 222 1 Docu..m...e..n..t.a..t.i.o..n...... 222 2 Know...l.e..d..g..e.. .B..a..s..e...... 223 3 Prep.a..r..e.. .R..e..p..o..r.t...... 224 4 Cont.a..c..t. .S..y..n..-.A..p..p..s.. .S..u..p..p..o..r.t...... 225

7 SA-Announce Overview

Part 1 SA-Announce Overview 9 1 SA-Announce Overview

SA-Announce Notification System [8.3.14]

The SA-Announce Notification System is a feature-rich notification system that couples to Cisco Unified Communications Manager to provide text and audio notifications across an enterprise. The notifications can be real time, such as emergency alerts and live audio notifications (IE paging / intercom), or they can be scheduled via the scheduling system. SA-Announce integrates the phone system with a large number of disparate end points such as Cisco IP Phones, Legacy Overhead Systems, PC Desktops, AND IP Speakers, Syn-Apps IP Speakers, Valcom IP Speakers, CyberData IP Speakers, Email, Mass Notificaiton, Syn-Apps Paging Relay, and Alertus beacon devices.

Notifications can be made by simply 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. With the addition of the Syn-Apps Paging Relay (a unicast to multicast device) even non-multicast enabled wide-area networks can provide notification to all remote sites using one centralized SA-Announce server. Streaming models include Unicast, Server Sourced Multicast, Relay assisted multicast and Phone Sourced Multicast.

Recent feature additions for SA-Announce include: Feature Description SA-Announce8.3.14 Server Redundancy Join multiple SA-Announce servers into a cluster to facilitate automated failover. SA-Announce 8.3.13 Weather Alerts Weather Alerts have been updated to use the new NWS CAP feed. Short duration events such as Tornado Warning can now be monitored. Many other interesting events such as Civil Warnings and 911 Telephone Outage are also available. SA-Announce 8.2.0 Group Opening Tone Assign custom audio files to serve as the notification group opening tone. AND Speaker Text Text messages now allow configuration of the text color, scroll speed and number of Options loops for AND IP speakers. Schedule Time Zone Schedules now have an associated time zone for large deployments. SA-Announce 8.0.0 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 conference. AND IP Speaker SA-Announce now supports AND IP Speakers. Support Desktop Notification SA-Announce now supports the Syn-Apps Desktop Notification Client allowing users Client of SA-Announce to target PC desktops with live and stored audio messages as well as text messages, polls, amber alerts and weather alerts.

The SA-Announce Notification System has been created using ASP.NET 3.5 to provide a rich user interface. Menus and lists that contain multiple items are searchable, simply 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.

Part 2 12 SA-Announce User Guide 2 Application Features

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 analog phones. Extends existing phone systems to notification systems with minimal installation and management

Endpoint Support - SA-Announce supports notifications to the following endpoint types: Endpoint Description 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 Atlas/AND IP Speakers SA-Announce supports the full line of Atlas/AND IP Speakers featuring Supervised Delivery Syn-Apps Desktop Target the PC Desktop with audio and text notifications featuring Supervised Notification Client Delivery Overhead Systems SA-Announce supports integration with all analog overhead paging systems Analog Telephones SA-Announce supports intercom from Atlas IP speakers to analog phones Email SA-Announce supports email notifications per notification group Alertus Integrate with Alertus beacons providing ADA compliance and a more comprehensive coverage model Everbridge Integrate with Everbridge to allow MASS external notifications like SMS, Text-to- Speech, and E-mail Facebook Integrate with your Facebook account, this can be useful for delivering campus events to students, etc. Twitter Integrate with your Twitter account and automatically update your Twitter status when a notification group is activated

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 (IE school bells) and emergency alert notifications Auto Conference Leverages the CUCM Meet Me conference to automatically create and join predefined users to a conference Amber Alerts Integrate with CodeAmber.org to deliver Amber Alerts and Endangered Child Alerts Weather Alerts Integrate with the National Weather Service and deliver localized weather alerts (Watches, Warnings, Advisories) Text Messages and Polls Text messages can be sent to all endpoint types that support text. Polls can also be sent and gathered results can be viewed in real-time.

Other Features - SA-Announce offers its users the following features: Feature Description Server Redundancy Multiple SA-Announce servers can be clustered together for automatic fail over of notification groups. Dynamic Notification Dynamically associate IP Phones, IP speakers and Desktop Clients to a Groups notification group using filters Group Opening Tone Assign custom audio files to serve as the notification group opening tone Notify from Speaker Initiate an intercom or emergency alert notification from Atlas IP Speakers Emergency Alert Define groups for emergency notification (IE school on lockdown / tornado notification groups warning / etc) Busy Detection SA-Announce monitors active calls and prevents conversations from being interrupted by paging External Phones Easily add virtual phones to integrate with overhead paging systems and other Interface external resources Background Music Stream music to your Cisco IP Phones. *A multicast streaming source such as Service the Syn-Apps paging relay is required Extension Mobility SA-Announce now supports extension mobility on CUCM 4/5/6/7/8+ Support Enhanced User Create user based access with granular permissions and global administration Management access Configurable Streaming Unicast and Multicast support to all digital audio endpoint types Model Paging Relay A hardware solution for non-multicast enabled wide area networks, sources multicast streams from the local site Secure Notification Any notification group can be secured with a DTMF security code Groups System Information View notification history, Login history, Scheduled broadcast history, Text history Center and all relevant system information Troubleshooting Automatically create a trouble report and send relevant data to Atlas via FTP Multicast Enhanced multicast tests to determined if your network is properly configured Troubleshooting

Part 3 Manual Conventions 15 3 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 tab, page and in some cases secondary tab identifier of the web page begin referred to. For example the notification group configuration section refers to the main tab "Groups", page "Create / Edit Groups" and in most cases the secondary tab (e.g. "General"), this would be presented at the top of the manual page being viewed as " Groups>>Create / Edit Groups: General".

Bold text is generally used to signify items in the configuration / management interface that need to be or can be configured.

The Notification Group Configuration chapter of the manual describes each of the Create / Edit Groups tabs in detail, other chapters like Creating Emergency alert Groups do not repeat this information.

First time users should start with the System Requirements chapter and follow the sections through to Notification Group Configuration.

Part 4 System Requirements 17 4 System Requirements

In order for SA-Announce to function properly there are some system requirements that need to be met. Please review the system requirements 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 The Cisco Communications Manager Requirements. Requirements Network Requirements Network port usage and multicast setup information.

The SA-Announce Notification System application server must meet the following requirements:

Server Requirement Description Software Requirements Supported Versions Operating System Windows 2003 (32-bit only) or Windows 2008 SP2 (32-bit or 64-bit versions) or Windows 2008 R2

Note: See the following for server operating system requirement setup specifics : Windows 2003 Server Windows 2008 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).

Note: MSDE / SQL 2000 is no longer supported. The SA-Announce installer and configuration programs will assist with DB upgrades for customers on MSDE.

*SQL Express 2008 R2 SP1 is automatically installed if the server has internet access (or download here: 64-bit or 32-bit) Hardware Requirements Server hardware minimum requirements listed below CPU Intel Core-2 Duo (minimum recommended) Memory 2 GB of system memory (minimum requirement) Hard Drive 10 GB of hard drive space (minimum requirement)

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

ASP.NET Under Application Server the ASP.NET check box must be checked.

Internet Information Services Under Application Server>Internet Information Services>World Wide Web Service: Active Server Pages and World Wide Web Service must be checked.

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 Please make sure that Windows 2008 SP2 has been installed, required for automatic configuration. Microsoft .NET 3.5 If the application server does not have internet access make sure .net 3.5 has been installed (download here).

Note: If the application server does have internet access then the SA-Announce configuration utility will automatically download and install ASP.NET 3.5.

The following are required for all Windows 2008 servers:

Server Requirement Description Manual Setup Requirement These require manual setup. Disabling Public Firewall Firewall must be disabled or set to allow access on the required ports (see Firewall Ports). Auto-Setup Requirement The installer should automatically complete these. Disabling IE Enhanced Security Configuration IE Enhanced Security Configuration must be disabled to allow the website to function properly. Creating ASPNET user account 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) We recommend disabling UAC.

4.1.2.1 Disabling UAC

Disabling User Account Control (UAC)

To disable User Account Control on the SA-Announce application server (recommended) perform the following:

Disabling User Account Control Description Launch Control Panel Lauch Start>>Control Panel on the application server. Launch User Accounts Under Control Panel, launch User Accounts. Turn User Account Control on or off Under User Accounts select Turn User Account Control on or off. Disable UAC Uncheck the Use User Account Control (UAC)... checkbox. Click OK Click OK to accept the changes. Reboot Windows will require a reboot. Please reboot the system.

4.1.2.2 Disabling Public Firewall

Disabling Public Firewall

To disable Public Firewall on the SA-Announce application server (required) perform the following:

Disabling Public Firewall Description Launch Server Manager Start>>Server Manager or Right-Click on Computer and select Manage. Select Windows Firewall In Server Manager expand the Configuration item and select Windows Firewall. Select Go to Windows Firewall. Select Windows Firewall Properties In Windows Firewall Configuration click the Windows Firewall Properties link at the bottom of the page. Switch Firewall Off In Windows Firewall Properties click the Public Profile Tab. Switch Firewall State to Off. Finalize Changes Click OK. Public Profile’s Firewall should now be off.

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

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

4.1.2.5 Installing IIS

Installing Internet Information Service (IIS)

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 Web Server (IIS) role. Select Role Services In the Add Roles Wizard (or Add Role Services Wizard if the Role was already installed) select ALL Role Services for the Web Server role:

Click Next when all items have been selected to complete the installation.

4.1.2.6 Installing ASP.NET

Installing the ASP.NET feature on Windows 2008

To install the ASP.NET Feature on the SA-Announce application server (required) perform the following: 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 and then click Next. The features will be installed.

Note: on Windows 2008 R1 the feature is ".NET Framework 3.0 Features", on Windows 2008 R2 the feature is ".NET Framework 3.5.1 Features".

This completes the Windows 2008 Server requirements section.

Cisco Unified Communications Manager Support

The following table describes the various Cisco Unified Communications Manager (CUCM) requirements:

CUCM Requirement Description CUCM Version CUCM versions 4.x, 5.x, 6.x, 7.x, 8.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 required if using TAPI busy detection (optional). Connectivity Proper IP access to Communications Manager and IP phones required

Cisco IP Phone Compatibility

XML enabled Cisco IP phone models are supported as destinations and can receive commands from SA- Announce. In most cases any phone can be used to dial into the system though some notification groups require activation by an XML enabled phone. Note that some models do not support images as denoted below in the 'Img' column-

Cisco IP Phone Model XML Img Cisco IP Phone Model XML Img Cisco 9971 Cisco 7937 Conference Station Cisco 9951 Cisco 7931 Cisco 8961 Cisco 7926 Cisco 8945 Cisco 7925 Cisco 8941 Cisco 7921 Cisco 7975 Cisco 7920 Cisco 7971 Cisco 7912 Cisco 7970 Cisco 7911 Cisco 7965 Cisco 7906 Cisco 7962 Cisco 7905 Cisco 7961G-GE Cisco 6961 Cisco 7961 Cisco 6945 Cisco 7960 Cisco 6941 Cisco 7945 Cisco 6921 Cisco 7942 Cisco IP Communicator Cisco 7941G-GE Cisco 7910 / 7902 Cisco 7941 Cisco 6911 / 6901 Cisco 7940 Cisco 7936 / 7935

This section is provided for legacy installations, Communications Manager 3.x is no longer supported by Syn- Apps.

If you are using Communications Manager 3.x, you 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.

4.2.2 Communications Manager 4.x, 5.x , 6.x, 7.x, 8.x

Communications Manager 4.x, 5.x, 6.x, 7.x and 8.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 SA- Announce 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 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.

4.2.2.1 Adding Device Pack (CM 5.x, 6.x, 7.x, 8.x)

This section is not required.

Use the Syn-Apps device pack to avoid being charged Cisco license units (DLU's) for the virtual devices associated with the 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 becuase the device type used is a 30-VIP. The Syn-Apps device pack will add a new device to the CUCM system. This will allow SA-Announce to add its virtual paging phones as that special Syn-Apps device which consumes 0 DLU's.

To complete the installation two major steps must be completed. 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).

Note: When SA-Announce is set to use the Syn-Apps device the currently created 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 onscreen 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 go 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.

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

SA-Announce supports both unicast and multicast paging. For systems that will have page groups with more than 100 endpoints, we recommend the use of multicast.

4.3.1 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 20480 - 32767 UDP - RTP 2748 TCP - TAPI SA-Announce to IP Phones 80 TCP - HTTP 20480 - 32767 UDP - RTP - unicast and multicast IP Phones to SA-Announce 80 TCP - HTTP 20480 - 32767 UDP - RTP - unicast and multicast SA-Announce <-> IP Speakers 80 TCP - HTTP 6789 UDP - SynApps IP device protocol 20480 - 32767 UDP - RTP - unicast and multicast

If you choose to use multicast (strongly suggested with over 100 phones) you must have a multicast enabled network. All interfaces between the SA-Announce server and the destination phones need to have IP PIM enabled and the switches should have IGMP/CGMP enabled.

If either the network cannot be multicast enabled or enabling multicast would require a large or recurring investment then the Syn-Apps Paging Relay should be deployed at the site to allow SA-Announce to send a single unicast stream over the wan connection and have the Paging Relay convert the stream into a multicast stream at the remote site. See SA-Announce Overview or contact Syn-Apps for more information.

Please refer to Cisco TAC or your Telephony partner for the best approach for implementing multicast on your network.

A Cisco Multicast Quick Start guide can be found at:

http://www.cisco.com/warp/public/105/48.html or http://www.syn-apps.com/Download.aspx?download_guid=494b78a5-007b-423a-9110-d4bae6f120b1

Note: By default SA-Announce is configured for unicast, to enable multicast refer to the Multicast Configuration section of this manual.

Part 5 34 SA-Announce User Guide 5 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).

You must be logged onto the application server as an administrator (local or domain) to properly complete the installation.

Installation Procedure Description Screenshot Start the Installer Start the SA-Announce setup program. The SA- Announce setup program welcome screen should appear.

Click Next to proceed.

Note: Download SA-Announce here - a license is required contact [email protected] to request one. Accept License The License Agreement page should appear. Read Agreement 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.

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.

Part 6 36 SA-Announce User Guide 6 Configuration Utility

The following section describes the configuration utility for the SA-Announce notification system. The SA- Announce configuration utility will automatically run at the end of installation. The program can be run on the application server at anytime by going to: Start>Programs>Syn-Apps>SA-Announce>Configuration.

Config Step Description Screenshot License In order to use the SA-Announce software, a valid license key Selection must be obtained. Contact [email protected] to obtain a license. If the license file has already obtained, click Browse to locate it.

The license file screen will only appear if the license file "Syn-Apps. license" does not exist in the program base directory (C:\Program Files\Syn-Apps\SA-Announce\). If you encounter problems with the browser below simply place your license in the program base directory and make sure it is copied there with the precise filename Syn-Apps.license.

Click Next to proceed. CUCM SA-Announce requires the following information about the Settings 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, if you have multiple Communications Managers on the cluster generally list the publisher first.

SA-Announce will use the primary server for CUCM data refresh unless it cannot be reached in which case SA-Announce 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 SA-Announce 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 boundaries.

Click Next to proceed.

Database If SQL Express was installed along with this installation leave Instance 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 will allow users to backup and restore their current SA-Announce database to a new SQL Server instance, simply select the new instance to use and press the Upgrade DB to Selected Instance button..

Note: SQL 2000 is no longer supported, installations using such an instance will be required to upgrade it.

Only local databases are supported though remote databases can be used by changing the registry key HKLM>Software>Syn-Apps>SA- Announce>sqlServerName to the name or IP address of the server you would like to use. Trusted authentication is required to use this model (the administrator credentials of the application server and database server machines must match).

Click Next to proceed. Application Setup the SA-Announce application administrator user account Admin credentials. This will be the system admin user for the SA- Credentials Announce notification system. This can be a fictitious user.

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 must have the same user name and password as the Administrator account on Communications Manager 3.x.

Click Configure to configure the product. Configuration When the application is configured you will see a success Complete window. Click OK to proceed.

An informational message will appear instructing the installer to change the CUCM authentication URL. Click OK to proceed.

License If the license has not been activated the Activation Wizard will Activation appear.

Select Online if the SA-Announce server has access to the Internet. Click Next to activate the license.

Select By Email 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. You can also access the SA- Announce administration web pages form any machine on the network, simply browse to http:///SA-Announce.

The SA-Announce web page should be displayed automatically when the configuration program completes. Proceed to the Post Configuration Steps section to complete the application configuration.

Part 7 Post Configuration Steps 39 7 Post Configuration Steps

Help>>Post Install Instructions: Authentication URL

Once installation and configuration are completed one manual post-configuration step using Communications Manager administration is required before Cisco IP Phones can be activated by SA-Announce.

Double click on the SA-Announce shortcut that was created on your desktop. The Help>>Post Install Instructions: Authentication URL page should appear the first time the program is run. To access it at any time, simply click on the tab labeled Help at the top of the page and select the Post Install Instructions. Or see the Authentication URL section of the manual for detailed instructions.

The page also contains a quick start guide for setting up groups, a section with instructions for setting up the SA-Announce phone service in Communications Manager (Not Required: this is a phone service that provides a directory of the groups that have been created, one of the most interesting features of SA-Announce is the ability to simply dial notification groups by number), and other information.

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 setup of the CUCM authentication URL. 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 (ccmadmin). Navigate to System / Enterprise Parameters. Set the URL Authentication parameter to: http:///SA-Announce/PhoneServices/Authenticate. 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) In order for IP phones to authenticate properly define the authentication URL under the telephony-service in the CLI (command line interface) of CME. CME Setup Process Open the CME CLI. Login and enter the following commands:

telephony-service url authentication http:///SA-Announce/ PhoneServices/Authenticate.aspx

exit wr mem

*Note: IP phones will not be able to receive commands until these steps have been completed.

Help>>Post Install Instructions: IP Phone Services

This chapter is not required.

The Post Install Instructions: IP Phone Services tab describes two of the basic IP Phone services offered by SA- Announce and provides a quick start guide for getting them configured. For a complete listing of offered IP phone services with full details see IP Phone Services Configuration.

The IP Phone Services tab describes the following IP phone services:

SA-Announce phone service - A directory of groups accessible on the IP Phones (Notification Group Directory). SA-Announce web dialer service - Phone sourced multicasting (Web Dialer Directory).

Part 8 Initial Application Configuration 43 8 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.

After starting the application (or browsing away from the post installation page if it’s the first time the program has run) you will be prompted to enter the application user name and password before SA-Announce allows access to the application.

The default user name and password are the same as the administrator account supplied during configuration.

Enter the User name and Password and click the Login button or press Enter..

[SA-Announce Web Administration Login]

Services>>Broadcast Services: Settings

The Settings Tab allows adjustment of the general system settings and contains the following settings: Setting Name Defaul Description t The maximum time in seconds to try and reach auto conference participants. If the Auto Conference Outbound 30 participant has not confirmed after this amount of time passes then the attempt w ill be Call Timeout (seconds) canceled. To prevent pages from interrupting phones that are on active calls, XML Busy Detection is Busy Detection XML enabled by default. Some scenarios like shared lines may require TAPI busy detection. Please refer to the TAPI Busy Detection chapter for detailed setup instructions. Select the site that the SA-Announce server resides at (so the broadcaster can determine Application Server Site Default a local broadcast versus a inter-site broadcast). Servers authorized to use Enter the IP Addresses of servers authorized to access the SA-Announce API (comma the SA-Announce API delimited list). Check the "Allow all servers" checkbox to allow all servers access. Page group busy if External When enabled, SA-Announce w ill notify the page originator that the external destination False Phone busy (IE analog paging system) is busy, and the page w ill end. Check w hen you are using SA-DND Do Not Disturb or another ringer management system and destinations w ith disabled ringers w ill not be paged. If this option is selected the automatic refresh timer setting w ill need to be changed, at tw o hours by default it w ould take SA-Announce an hour (average) to discover that a ringer had been turned off. To SA-DND in Use False change the setting go to Services>Broadcast Services: Advanced Settings, select refreshPhoneSettingsMinutes and change the value to a minimum of 2 (installations under 500 phones), 4 (installations w ith 501-1500 phones), 5-10 (installations w ith over 1501 phones). Check w hen you are using the Idle URL feature on the Cisco IP Phones, this w ill clear the Idle URL in Use False phone state prior to trying to page and avoid the xml busy state that the Idle URL creates. All Busy Detect False If checked, the caller w ill be notified if all destinations of the group are busy. Extension Mobility Mode For use w ith CUCM 5/6/7+ systems using extension mobility. Using this option w ill reveal False Enable user device profiles in the Groups>IP Phones section w hich can then be added to groups. If checked the group and dialer phones w ill be registered using the CUCM groups settings Register Devices Using False on the CUCM. If unchecked (default) the group and dialer phones w ill be registered using CUCM Groups the ordered list of CUCM's provided in SA-Announce configuration. When checked do not allow unicast notifications. A useful setting w hen phone sourced multicast w as the default streaming model, w ith the new er server sourced model the Multicast Only False broadcaster does not need to fail over to unicast w hen a non Cisco phone dials a live notification group. For use w ith Communications Manager 3.x and 4.x only. When checked use deviceListX Force Web Lookup False rather than the AXL API to lookup phone IP's. Only enable this option w hen requested by Syn-Apps Support Confirmation threshold w hen Confirmation threshold is used to determine w hen the originator of the page hears calling a broadcaster group confirmation beeps w hich 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 w ould play w hen 80 phones are activated.

With SA-Announce 8.3.10 and greater the confirmation threshold is dynamically applied in 80 the follow ing circumstance: 1) Group has an opening tone associated. 2) Group has Paging Relay(s) associated. In this case the confirmation threshold w ill not be met until all Paging Relays have been contacted w ith opening commands. Once 80% of devices have joined, if the group has *This setting has been paging relays that have not responded to their opening commands, the opening tone / moved to the Advanced confirmation tone w ill be delayed. The opening tone and confirmation tone w ill only be Settings area. played once all paging relays associated w ith the group have responded.

Settings Tab (shown with defaults):

Click the Save button to save settings changes.

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 SA- Announce manual or Syn-Apps support.

To change a setting, Select a Setting, the description and default value for the setting will be shown. Alter the Setting Value and then press save.

Some changes require that further action be taken in order for the setting change to take affect (IE Broadcaster Service Restart), these will be noted in the setting description.

Settings>>IP Endpoint Setup: XML Phones / Multicast Phones

SA-Announce generally has all Cisco XML phone models enabled by default. But sometimes a customer may implement a new model that is not in the default XML enabled models list of SA-Announce. In this case the XML Phones and Multicast Phones editors can be used to select models known to be XML / Multicast capable.

Use the XML Phones tab to identify those phones that will participate in XML control and communications. Once new items have been added to the selected side, click Apply. (All supported phones are selected by default)

Use the Multicast Phones tab to identify those phone models that will be allowed to participate in multicast phone features. Once new items have been added to the selected side, click Apply. (All supported phones are selected by default)

Settings>>Multicast Settings: Defaults

The Multicast Settings page is used primarily to enable or disable multicast notifications, by default multicast notifications are not enabled in SA-Announce. To enable multicast notifications or to test them navigate to Settings>>Multicast Settings in the SA-Announce web administration interface.

The Multicast Settings page consists two main sections, multicast settings and multicast tests. The following tables describes each section in detail:

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 (IE phones at the server site will have a multicast stream sent, phone that are not at the server site will have unicast streams sent unless Site to Site (WAN) Multicast Enabled checkbox is checked). Press the Save Defaults button to save any settings changes on the Defaults tab.

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.

[Multicast Settings: Defaults tab settings]

Sites Use the Sites tab to set multicast boundaries for one or more sites. Choose which Calling Search Space/Device Pool (site) you wish to configure 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 (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 meaning 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 Multicast Server Mode is in use and if the notification groups are being activated by the Web Dialer or SA-Announce 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 end-points while 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 that the server resides at in Services>>Broadcast Services: Settings.

If the Web Dialer Mode is in use then the settings are applied using the source (caller's) Cisco IP Phone. If all of the Cisco IP Phone destinations of 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 of the group are either not in the same site or not in the same site as the caller then the caller's site WAN Multicast setting is applied.

[Multicast Settings: Sites tab settings]

Multicast Settings Description Multicast Tests Note: The primary purpose of these tools are 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 Use the Server to Phone Multicast Test tab to perform a server to phone multicast Multicast Test test. This test will verify the server's ability to source multicast to a test phone (choose a phone on different switch than the server).

Select a phone to test from the Test phone drop down menu (use the Filter button to filter the entries in the menu). Click the Start Transmission button to begin a multicast transmit/receive test. Verify that a test audio clip is being played on the test phone. If you hear the audio clearly then multicast is functioning properly between the server and that phone. To stop the testing, press the Stop Transmission button.

Server to Speaker Use the Server to Speaker Multicast Test tab to perform a server to speaker Multicast Test multicast test. This test will verify the server's ability to source multicast to a test speaker (choose a phone on different switch than the server).

Select a speaker to test from the Test speaker drop down menu (use the Filter button to filter the entries in the menu). Click the Start Transmission button to begin a multicast transmit/receive test. Verify that a test audio clip is being played on the test speaker. If you hear the audio clearly then multicast is functioning properly between the server and that speaker. To stop the testing, press the Stop Transmission button.

Phone to Phone Use the Phone to Phone Multicast Test tab to perform a phone to phone multicast Multicast Test test. This test will verify the source phones ability to source multicast to a test phone (choose a destination phone on different switch than the source phone).

Enter the IP Address of the first phone to test in designated area. Enter the IP Address of the second phone to test in designated area. Click the Start Transmission button to begin a multicast transmit/receive test. Verify that audio from the first phone is being played on the second phone and vice versa. If you hear the audio clearly then multicast is functioning properly between the two phones. To stop the testing, press the Stop Transmission button.

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

[Continued on following page...]

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 users User Name. New users must be given a unique User Name. Password Enter or Edit the users password in the Password field and again in the 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 new user or user 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-admin users (required). ***Administrator users do not require additional permissions. Select a User Select an existing user in the Select User drop down menu. Add Permission Press Add Permission to create a new permission for the user. Select Group Select the group name of the group to give the user permission to in the Group Name drop down menu. Select Permissions Select Send Text to grant the user rights to send text messages to the selected group.

Select Modify Group to grant the user rights to modify the selected group in the SA-Announce web administration interface. Insert Permission Press the Insert link in the Edit Command column of the permissions table to save the new permission.

Edit a Users Permissions Select a User Select an existing user in the Select User drop down menu. Select Permission to Edit In the User Permissions table press the Edit link in the Edit Command column of the row to be edited. Edit Permission Make the required changes to the permission. Update Permission Press the Update link to update the permission. Delete a User Permission Select a User Select an existing user in the Select User drop down menu. Delete Permission Press the Delete link to delete the permission.

[Settings>>User Management]

8.5 IP Phone Tests

Services>>Troubleshooting Tests

The Services>>Troubleshooting Tests page contains a number of basic troubleshooting modules.

The IP Phone Tests module can be used to test the basic connectivity to IP phone devices. To access the IP Phone Tests module click on the Services>>TroubleshootingTests menu option, the IP Phone Tests tab will be shown by default.

[Continued on following page...]

To run the IP Phone Tests (Phone XML Test) 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 field and button to filter the list by extension or simply select an item in the list and begin to type an extension.

Note: 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 confirming if the database connection was successful or not. Verify Results on Target Verify that the test phone shows Test on the display screen. Phone

Note: If the test does not complete successfully verify the Authentication URL on the phone by accessing the phones settings button. IF the authentication URL appears to be correct verify that the phone has access to the SA-Announce server on HTTP port 80. Also, verify that the phones Web Access setting is enabled, see Communications Manager Requirements for details.

Part 9 58 SA-Announce User Guide 9 Notification Group Configuration

This section describes the types of notification groups that users interact with and how to configure them.

Refer to the Notification Group Types section of this manual for details on notification group types. Refer to the Notification Group Setup section of this manual for details on notification group configuration.

The diagram below shows possible sources and destinations for SA-Announce notifications. Not all source / destination combinations apply to all notification group types, see the Notification Group Types section, Group Compatibility Matrix for details.

Notification group sources and destinations:

**Please note that for every notification group you 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 the external phone dialers (the name here begins with SEPEEEE). When you delete notification groups in SA-Announce the associated virtual phones and lines will NOT be deleted from CUCM. After deleting notification groups in SA-Announce please 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 (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.

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 activate. The event is activated by calling the notification group line number or by API and other methods. 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 number is part of the dial string. Insta-Holler Static one to one intercom notification. Destination device is predefined. Walky Talky Walky Talky emulation. Many to many, live audio, push-to-talk. Wokkie Tokkie A predefined group of IP phones that emulate a walky-talky when the notification group (Normal) is activated. Wokkie Tokkie Non-predefined group of IP phones that emulate a walky-talky; when the notification (Ad-Hoc) 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 message, audio notification and image 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 A stored audio event that is scheduled to occur on certain days/times. At the scheduled times the groups associated end-points will play a predefined audio tone. Text / image also displayed on end-points that support it.

Group Compatibility Matrix

The group compatibility matrix lists the compatible end-point types per group. Keep in mind that any phone attached to the network can call most group types by number, but some group types require the caller end-point be known 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 Email 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 IP Desktop IP Required Phones Clients Speakers Holler Respond

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, rather they are entered as DTMF by calling 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#, and # 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. 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.

SA-Announce Auto Conference is a notification group type that leverages the CUCM Meet Me conference to automatically create and join predefined users to a conference.

The initiator simply calls the Auto Conference group number to begin the Auto Conference. Auto Conference then creates a Meet-Me conference and joins predefined users (at 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 (adding a supervisor or head of security etc). It is also possible to add any user to the ongoing conference from any IP Phone listener (up to the maximum of 15 total conference participants).

Additional Auto Conference features include: Feature Description Alert on Activation Automatically activate an SA-Announce emergency alert group or schedule w hen the Auto Conference is activated. Email Events Send emails 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 soft-key names show n): Add User Add a user to the conference. Call 911 Disconnect from the conference and auto dial 911 to notify them of the event. Notify Activate an SA-Announce emergency alert group or schedule (generally to signify the end of the event to non conference participants). Escalate 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 SA-Announce External Phone Dialer Requirements Dialers Dialer Configuration Auto Conference requires external phone dialers to facilitate the dialing of destinations to join to the conference, it is recommended that you 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 (not including the caller and the 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 so after adding dialers using this page you must manually edit them on CUCM to have an appropriate Media Resource Group List. Dialer Pool The Auto Conference dialers are all members of a single "dialer pool" so all dialers must have the same settings (other than line number). Due to this the dialer settings must allow the dialer to call any of the internal or external numbers you plan to program Auto Conference to dial as w ell as the Meet-Me numbers. While this may not be an issue for most users, those w ith advanced dial plans may need to make dial plan adjustments in order to accommodate Auto Conference at multiple sites. 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 Meet-Me number and busy transfer number for the group. When adding a new Auto Conference group type SA-Announce w ill check the MeetMe and Busy Transfer numbers against the selected CSS to make sure a route is present. If you have recently added the MeetMe or Busy Transfer DN's you w ill likely need to Refresh Data in SA-Announce at Services>Broadcast Services: Service. CUCM Registration The Auto Conference group phone and callers must be registered to the same CUCM in order for the group to function porperly. If CUCM registration groups are in use the SA-Announce setting Broadcast Services>Settings: respect CUCM groups should be enabled. In this case the Auto Conference group phone and callers need only be in the same device pool in order for the group to function properly. MeetMe 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 ow n unique and reserved Meet-Me number (IE do not manually activate the Meet-Me numbers you set aside for auto conference).

Auto Conference Settings Descriptions (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, like the number you will use to activate the auto conference. Those basic items are not discussed here.

Setting Description General Settings Auto Conference Group General Settings Title Enter the title that should appear on the screen pops for this group. MeetMe 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 to play to the users being joined to 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 you customize the file used here you should certainly ask the users to press 1 at minimum. Activation Group Emergency Alert group or Schedule to activate when this group is called/activated. 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 to be used for the escalate soft key (Default: 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 (IE a group to alert when the event ends). Soft Key Label The label to be used for the Soft Key Group soft key (Default: Notify).

[Auto Conference Settings]

Auto Conference Email Options (Groups>>Create / Edit Groups: Email):

***See the email tab on the groups page for the Auto Conference Email setup. The group Email Address (Activation) works the same as other group types, if populated email will be sent when the group is activated. When an Auto Conference group type is selected additional fields are displayed on this tab. Those fields are: Participation Email Address: Email the participation results (who joined the conference). Escalation Email Address: Email when the group is escalated using the escalate soft-key. Error Email Address: Email when errors occur in group processing.

***For information on the activation email settings see the Email section of the manual.

[Auto Conference Email Settings]

Adding End-Points to the group (Groups>>Create / Edit Groups: IP Phones / External Phones):

Add end-points to the Auto Conference using the "IP Phones" and "External Phones" tabs. Both phone types will be dialed by number but only IP Phones will receive screen pops. Note that when you add an IP Phone device to the Auto Conference group (IP Phones tab), that device may contain multiple lines; Auto Conference will dial the primary line (line-1).

[Auto Conference IP Phone Screen Pop]

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 If the caller of Auto Conference is left with silence or on hold after calling then the most Slikely problem is an inter-digit timeout. Check for inter-digit timeouts for the group i phone/line CSS when trying to reach the MeetMe line. This is generally the cause of l this error. e n SA-Announce allows 16000ms for a transfer by default. Just longer than the default c inter-digit timeout on CUCM. e Services>>Broadcast Services: Advanced Settings autoConfMaxXferWaitMs Caller Left on Hold controls this maximum wait timer. MeetMe Callers Max To adjust the maximum number of MeetMe callers that CUCM can handle at once see the following guide:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/ products_configuration_example09186a0080b2cd07.shtml No IP Phone Screen Make sure a Media Termination Point (MTP) is not in use on the Cisco XML enabled IP phones. This will obscure the IP address of the IP phone and it will not receive screen pops.

Emergency Alert provides the ability to send alert tones across predefined groups (Alert, Voice, and Timed Modes). Emergency Alert groups are meant for use in emergency situations, and as such they override busy detection (phones on a call will still receive the text and audio associated with the group activation). For example: a school on lockdown alert, tornado warning, fire, etc..

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 activated. The event is activated by calling the notification group line number or by API and other methods. The event is deactivated in different ways depending on the mode selected during configuration:

EA Modes Description - Alert Mode First call activates the emergency event. The event is canceled by the next call. Timed / Repeat First call activates the emergency event, it will continue until the configured number of Mode stored audio message repeats has occurred. Voice Mode First call activates the emergency event, a stored audio opening tone is played and then the caller speaks live audio, when the caller hangs up the event is canceled.

Emergency Alert notification groups have a number of optional features: Feature Description Send Caller-Id1 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. Facebook Automatically update Facebook status and email friends when the alert activates. Twitter Automatically update Twitter 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. Amber Alerts Group member end-points can receive Amber Alerts and endangered child alerts from http://CodeAmber.org. See Amber Alert Settings for details. 1 Selecting the “send caller id to destinations” checkbox on the create / edit groups page is especially interesting here since it w ill send the originators caller-id to all destinations of the emergency that can display text.

***See Creating Emergency Alert Groups for complete details on creating emergency alert notification groups.

Holler is an intercom notification group type. Holler notification groups always target a single destination endpoint and open that end-point in hands-free mode. The target of a holler notification is determined in one of three ways corresponding to the three different holler group types. The three holler notification group types are described in the below table.

Holler Type Activation Method - The method used to activate the intercom. Holler1 After calling a standard Holler notification group users are prompted for a destination extension followed by the # sign. Holler-RP1 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 like * 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. 1 Holler and Holler-RP groups use the CSS of the calling line/phone to search for the destination line. In other w ords, if the calling phone can dial the destination phone normally then it w ill be able to holler to it as long as the destination is not a shared line (see the next paragraph). You can exclude phones from Holler and Holler-RP groups by selecting them in the IP Phones tab or the create edit groups interface, note that in this case you are selecting phones that are NOT to be included w hich is the opposite of the other group types.

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 w ill 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 w ill 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.

Note: 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 SynApps/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/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 muted. By default the option is off and Start the destination will start with its microphone open.

***See the Notification Group Setup section for more details.

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. When the caller hangs up the notification will terminate.

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

***See the Notification Group Setup section for more details.

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 and/or the chance of audio feedback with a live page.

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

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

***See the Notification Group Setup section for more details.

The Schedule notification group type allows scheduled events such as school bell tones to be scheduled for reception by a group of end-points. Schedules are a server-to-many, one way, stored audio notification

Scheduled notification groups have a number of optional features: Feature Description Disable Schedule If the Disable Schedule checkbox is checked the schedule will be disabled and will not activate. Repeat The number of times to repeat the wave file when the schedule is activated. Text / Image The text / image will be sent to all end-points that support text messages. Override Override the schedule so it does not play during a specified timeframe.

***See the Creating Schedules section for complete details.

The Text notification group type allows users to send a text message to a predefined group of end-points. Any notification group type that contains an end-point association can be targeted on the Groups>>Send a Message page when send text messages.

Note: Text groups do not require a device in Communications Manager.

Text notification groups have a number of optional features: Feature Description Alert Image Images can be attached to the message. Alert Sound Sound notifications alert recipients of text message delivery. Poll Option Text messages can be sent as polls and responses can be viewed in real-time. Speaker Text AND IP Speakers have the following options when receiving a message: Options Scroll Speed - Message scroll speed. Number of Loops - The number of times to loop the scrolled message. Pause Seconds - The number of seconds to pause the message between loops.

***See the Sending A Text Message section for complete details.

A Wokkie Tokkie notification group emulates a walky-talky (push-to-talk conference) on Cisco XML enabled IP phone end-points only. There are two types of Wokkie Tokkie groups, standard and Ad-Hoc. The standard type allows group members to be predefined, while the Ad-Hoc type allows users to dynamically select destination end-points. 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/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.

***See the Notification Group Setup section for more details.

Note: The Wokkie Tokkie noritifcation group type requires multicast. Multicast must be configured on the network in order for Wokkie Tokkie to function.

After dialing a Wokkie Tokkie group the source and destination phones will be presented with the following:

Press and hold the Talk softkey to transmit, as with a walky-talky. Press Shout to speak continuously and Stop when finished. Press Exit to exit.

Groups>>Create / Edit Groups: General

The standard notification group setup process is described in the following sections. This section describes the General tab of the Create / Edit Groups page, it represents the basic settings for the notification group like the group type and line number. The sections immediately following this one describe the remaining tabs on the page, these tabs represent the end-points you can associate with the notification group.

To create a new group select Groups>>Create / Edit Groups :

Click New Group near the bottom of the page then configure the following settings on the General tab: Notification Group Setting Description Group Name Enter a descriptive name for the group. Group Type Select a group type, a Normal notification group type is usually the best to begin with (for a listing of group types see the SA-Announce: Group Types section of this manual). Server Group Select the server group that this notification group should be a member of. Select to run the group on the publisher only. **This field will only be displayed if the redundancy subsystem has been configured, see Server Redundancy for details. Group Phone Settings The settings for the virtual phone that facilitates group activation. Line Number This is the extension that you will use 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 (IE 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 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. Callers will then need to enter the security code before they are allowed to page. 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. Volume The Volume drop down menu allows you 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%, 80% etc override the current volume setting on the phone and forces the phone to play the audio at the ©2009 Syn-Apps L.L.C. Notification Group Configuration 75

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

Please note that while this does affect the volume of phones it does not affect the volume of External Phones / Legacy IP / Alertus Endpoints (Beacons). Group Opening Tone Group opening tone setting. Group Opening Tone Select an opening tone to be played to the group end-points. For live audio group types the caller confirmation tone will be played once the opening tone completes.

[It is now possible to add the group even though end-points have not been associated yet, this can be done after adding the group (as presented in this manual) or before adding the group.]

Click Add Group.

[Group General Settings] Note: The group phone area will not be visible with Text type groups as text groups do not require activation via phone call.

9.3 Email

Groups>>Create / Edit Groups

The Email tab on the Create / Edit Groups page allows email(s) to be sent when a group is activated.

To use this feature you must first setup the email parameters at Services>>Broadcaster Services>>Email Settings, see the Email Settings chapter of this manual for more information.

Once the feature has been setup add one or many email addresses to the group using the Email Address (Activation) interface. Use email aliases when there are many emails to be sent (more than 10) to avoid overloading the SA-Announce system. To add custom text to the email message use the Custom Email Text (Activation) text box. The custom text will appear at the beginning of the email body after the statement "Group has been activated by ".

***Note: Mass SMS messaging (50 or more messages sent to the same provider) must be done using an aggregator service such as 3n (National Notification Network). Otherwise, sending too many SMS messages to a specific cellular provider might result in all messages being treated as Spam.

[Groups>>Create / Edit Groups: Email tab]

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

Select the phones you would like to add by clicking the items and adding them using the ">>" button. You can use standard ctrl-click and shift-click to select items, or use the Filter column to filter the list.

The Dynamic Group checkbox will dynamically lock the group to use the phones that match the specified Filter . When using the dynamic group option there will be no need to manage the devices in the SA-Announce notification groups as devices are added to the system . For example, enabling the dynamic group checkbox, arranging by Device Pool and entering "ABC" into the filter column will associate all phones that have an Device Pool containing "ABC" to the notification group.

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 to be used in the filter.

Note: For Holler and Holler-RP group types you can now select phones to be disallowed as targets of Holler and Holler-RP. Remember, in this case you are selecting phones that are not to be included in the group.

9.5 Desktop Clients

Groups>>Create / Edit Groups: Desktop Clients

Add desktop notification clients to a notification group by selecting the Desktop Clients tab. Use the Arrange List By drop down menu to resort the list on the selected item. Desktop Notification Clients that have registered with SA-Announce will be shown. To change desktop client settings and see current registration status see the Desktop Notification Client Configuration section of the manual.

Select the clients you would like to add by clicking the items and adding them using the ">>" button. You can use standard ctrl-click and shift-click to select items, or use the Filter column to filter the list.

The Dynamic Group checkbox will dynamically lock the group to use the clients that match the specified Filter. When using the dynamic group option there will be no need to manage the devices in the SA-Announce notification groups as devices are added to the system . For example, enabling the dynamic group checkbox, arranging by Description and entering "ABC" into the filter column will associate all clients that have an Description containing "ABC" to the notification group.

9.6 External Phones

Groups>>Create / Edit Groups: External Phones

Add legacy overhead systems or other dial-able numbers to a notification group by selecting the External Phones tab. First make sure the overhead system in question can be dialed from the digital phones, the number used by the digital phones is generally the number that will be used to configure the notification group to use the overhead system in question.

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 setup is described in detail in the Analog Paging System Integration section.

Use the interface on the page to add external systems to the notification group. Enter a description in the Description or Name field, enter the number that the overhead system exists at in the Number field and enter any DTMF zone code if one is required in the Dial Code field. 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 the entry fields, change the values and press the Update button.

Groups>>Create / Edit Groups: IP Speakers

This section describes use of Atlas,AND and SynApps IP Speakers in SA-Announce notification groups. These IP Speakers must be added to the system using the DHCP option 72 as described in the AND IP Speaker Configuration section of this manual before they will be visible in the groups or schedules interface.

To add an IP Speaker to a particular notification group, first select the group in question on the Groups>>Create / Edit Groups page. On the IP Speakers tab select the IP Speaker(s) to add to the group from the Available side of the list box and add them to the Selected side using the ">>" button.

The Dynamic Group checkbox will dynamically lock the group to use the speakers that match the specified Filter. When using the dynamic group option there will be no need to manage the devices in the SA-Announce notification groups as devices are added to the system . For example, enabling the dynamic group checkbox, arranging by Description and entering "ABC" into the filter column will associate all speakers that have an Description containing "ABC" to the notification group.

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 the DHCP option 72 as described in the Paging Relay Setup section of this manual before they will be visible in the groups or schedules interface.

To add a Syn-Apps Paging Relay to a particular notification group, first select the group in question on the Groups>>Create / Edit Groups page. On the Paging Relays tab select the Paging Relay(s) to add to the group from the Available side of the list box and add them to the Selected side using the ">>" button.

Note: In some cases the Paging Relay will be able to remove the SA-Announce server from the audio path, in this case notifications are made without any audio streams to/from the SA-Announce server. If all below requirements are met a Paging Relay will act as the audio termination point for the notification group call: Requirement Description Live Audio Group The notification group must be a live audio type notification group other than holler and record-n-play. One Paging Relay There must be one and only one Paging Relay associated to the group. IP Phones Local The IP phones associated to the notification group must all be in the same SA-Announce site (DP/CSS). No External Phones External phones must not be associated to the notification group. No Opening Tone Opening tone must not be associated to the notification group. No Legacy IP Legacy IP end-points must not be associated to the group.

[Create / Edit Groups: Paging Relays]

Groups>>Create / Edit Groups: IP Speakers

This section describes how to add Valcom or CyberData IP speakers into desired notification groups.

Use the Valcom section to assign Valcom IP speakers to the group you are currently editing, simply add the speakers’ group number(s) to the text entry box. To assign multiple Valcom IP speakers to a group delimit the group numbers with commas. Verify the Valcom IP Speaker setup using the Settings>>IP Endpoints: Valcom section.

CyberData IP Speaker groups must first be setup using the Settings>>IP Endpoint Setup: CyberData section. Use the CyberData section to assign CyberData IP Speaker groups to the paging group. Simply 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: Prerequisite required, see Valcom IP Speaker Configuration and CyberData IP Speaker Configuration.

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.

To add Alertus Beacon Groups to a SA-Announce notification group or schedule simply select the group in question, select an Alert Profile for the alert and select one or more Beacon Groups using the provided interface.

Groups>>Create / Edit Groups: Mass Notification

This section describes the process of adding Everbridge Scenarios to SA-Announce notification groups. SA- Announce 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 SA-Announce has been configured with the Everbridge system particulars you can add Everbridge Scenarios to a SA-Announce paging group by selecting the group in question on the Groups>>Create / Edit Groups page. Select the Mass Notification tab and 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 ">>" button to add them to the Selected side.

Part 10 86 SA-Announce User Guide 10 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 (e.g. Tornado Warning, School on Lockdown, etc). Emergency alert groups play wave files (which can be customized, use the Schedules>>Wav File Upload page) and send text to supported devices (Cisco IP Phones, Alertus and 3n end-points support text messages). With the inclusion of the Send Caller-Id checkbox the group becomes a very powerful emergency notification system as the security monitoring members can see who activated the emergency and respond accordingly.

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 check boxes in the emergency alert Settings area of the General tab (only one mode 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 (or via the web service possibly), the group will then send the text message to the supported devices and begin to play the wave file for 1000 cycles unless the group is called back. Calling an active emergency alert group in alert mode will cancel the emergency. Voice Mode Activates when called and plays the selected wave file once at which point 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 simply 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 devices. Timed Mode Selecting Timed Mode will expose a Repeat Number entry box, set the repeat number to the desired number of times to repeat the audio alert file before closing the group.

To create an Emergency Alert notification group perform the following: Select Groups>>Create / Edit Groups and then click 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 Select the server group that this notification group should be a member of. Select to run the group on the publisher only. **This field will only be displayed if the redundancy subsystem has been configured, see Server Redundancy for details. Group Phone Settings The settings for the virtual phone that facilitates group activation. Line Number This is the extension that you will use 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 (IE 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 anyone calling the group receives a G.711 codec lookup). 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. Volume1 The volume of the IP Phone end-points in the group. Tweet when activated Check this checkbox to send a status update to your Twitter account (See Twitter Configuration for setup details). Notify Facebook Friends Check this checkbox to send a notification to Facebook friends who have authorized the ControlKom Facebook application (See Facebook Configuration for setup details). Emergency Alert Services Emergency Alert based services. Amber Alerts2 Check this checkbox to send Amber Alerts to the groups IP Phones, Email, Beacons and Mass Notification. A Zip Code is required but may or may not be used depending on the system settings. See Amber Alert Settings for setup details. Weather Alerts2 Check this checkbox to send Weather Alerts to the groups IP Phones, Email, Beacons and Mass Notification. A FIPS Code is required as weather alerts are localized. See Weather Alert Settings for setup details. Emergency Alert Settings Emergency Alert based settings. Modes Alert Mode, Voice Mode, Play Once, Timed Mode. The modes are described at the top of this page. Wav File to Play Select the wave file to play when the group is activated. Add custom wave files to the system using the Schedules>>Wav File Upload page described here. Text to Send Enter the text to be sent with the emergency alert. The text will be sent to all end-points that support text messages. 1 The Volume drop dow n menu allow s you to adjust the volume of the audio played on the phone speaker. The Default volume setting uses the setting of each phones speaker individually, other settings such as 90%, 80% etc override the current volume setting on the phone and forces the phone to play the audio at the percentage of maximum volume specified. **Please note that w hile this does affect the volume of phones it does not affect the volume of Valcom IP Speakers / CyberData IP Speakers / Legacy Overhead Systems / Alertus Endpoints.**

2 The Amber Alerts and Weather Alerts features w ill try to play the selected Wav File w hen sending the alert to IP Phones, but this Wav File may not be present on the CM TFTP server, in this case no sound w ill play along w ith the Amber Alert or Weather Alert, move the file to the TFTP server to allow it to play on the phones (this does not mean the sound w ill not play for an actual emergency alert, it w ill since it is streamed from our server). The Amber/Weather alerts are merged w ith emergency alert groups for convenience, they do not activate w hen you call the group to activate the alert, they activate w hen an Amber or Weather alert is in effect. In some cases w here your emergency alert group has a custom w av file like "school on lockdow n" you w ill not w ant to integrate the Amber Alerts and Weather Alerts w ith the group, instead create a new group for the Amber Alerts and Weather Alerts only.

[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.]

Click Add Group.

[Create / Edit Groups page, General tab, Emergency Alert group type selected]

Part 11 90 SA-Announce User Guide 11 Creating Schedules

Schedules>>Scheduled Broadcasts: General

This section describes the creation of SA-Announce schedules. Schedules are used to broadcast audio/text to predefined end-points at predefined times (e.g. school bell schedules, manufacturing break bells, etc). It is important to note that for schedules to function properly both the Scheduler service and the Broadcaster service must be running (See Services>>Broadcast Services). Also be aware that the scheduler is licensed separately from the broadcaster, contact [email protected] for details.

To create a schedule perform the following: Select Schedules>>Scheduled Broadcasts: General from the main menu:

Click New Schedule near the bottom of the page and configure the following items: Schedule Setting Description Schedule Name Enter a descriptive name for the schedule. Time Zone Select a time zone for the schedule (the servers time zone is selected by default). Server Group Select the server group that this notification group should be a member of. Select to run the group on the publisher only. **This field will only be displayed if the redundancy subsystem has been configured, see Server Redundancy for details. Disable Schedule If the Disable Schedule checkbox is checked the schedule will be disabled and will not activate. Days Days to Play Select the days to play the schedule, one or more days may be selected. Times Times to Play Enter the times to play the schedule in 24 hour format (e.g. 4:00 pm >> 16:00) Sound and Other Settings Schedule sound notification and other settings. Sound to Play Select the wave file to play when the schedule is activated. Add custom wave files to the system using the Schedules>>Wav File Upload page Volume1 The volume of the audio played by the IP Phone end-points in the schedule. Repeat The number of times to repeat the wave file when the schedule is activated. Text to Send Enter the text to be sent with the schedule. The text will be sent to all end- points that support text messages. Emergency Busy detection overridden for this group, agents on a call will also receive the notification audio stream and or text message. 1 The Volume drop dow n menu allow s you to adjust the volume of the audio played on the phone speaker. The Default volume setting uses the setting of each phones speaker individually, other settings such as 90%, 80% etc override the current volume setting on the phone and forces the phone to play the audio at the percentage of maximum volume specified. **Please note that w hile this does affect the volume of phones it does not affect the volume of Valcom IP Speakers / CyberData IP Speakers / Legacy Overhead Systems / Alertus Endpoints.

[It is now possible to add the schedule even though end-points have not been associated yet, this can be done after adding the schedule or before adding the schedule.]

Click Add Schedule.

11.1 Schedule Overrides

Schedules>>Scheduled Broadcasts: Overrides

The Schedules>>Scheduled Broadcasts: Overrides tab is used to override the selected schedule for a given time span. If the schedule is overridden it will not play, this can be used to silence bells during vacation. Use the provided interface to add overrides, press the Add Override button to add a new override row which will appear in the table, press the Edit link for the row and use the provided calendars to select a Start Date and End Date for the override. Press the Update link to update the row changes.

[Schedule Overrides]

Part 12 94 SA-Announce User Guide 12 Sending A Text Message

Groups>>Send Text Message: Send Text Message

This section describes how to send text messages. To send a text message to a notification group users must first create a notification group that contains the required end-points. This can be an existing notification group of any type as long as that type allows you to select end-points (e.g. holler and ad-hoc group types cannot be used for sending text messages). That is to say, even though Text type groups are only used on the Send a Message page, any group type that contains end-point associations will be listed on the send a message page and can be used to send text messages and polls.

To send a text message or poll navigate to Groups>>Send Text Message: Send Text Message:

The Send Text Message page supports saving message templates (predefined text message groups). A message template is not required for sending a text message but is required for sending polls.

Note: Text messages do not activate Facebook, Twitter or Mass Notification scenarios. Text messages only send emails when the group type being used is a Text group type. If the group you select contains end-points that cannot display text, such as IP speakers that don't have text displays, they will not receive the text.

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 Select the notification group to send the message to. Group Sound Notification Select a sound notification to accompany the text message. The sound w ill only be played on the Cisco IP Phone, Desktop Notification Client and AND IP Speaker end-points. Image Select an image to send w ith the text message (for supported end-points). Message to Send Enter the text message or poll question to be sent. Speaker Text Options Text options for AND IP Speakers. **Only visible when Poll Options are off. Text Color The color of the message text on the speaker. Scroll Speed The scroll speed of the message (1-10). Number of Loops The number of times to loop the scrolled message (0-n). Pause Seconds The number of seconds to pause the message betw een loops. Poll Options Options to enable / disable the poll feature and canned poll answers. Poll Options Checkbox Select the Poll Options checkbox to send the message as a poll. Poll Answ ers Enter the canned poll answ ers in the Answ er 1-4 fields. Message Template To Edit Select or save the message template to use. ***This is only required for polls.

Press the Send Message button to send the message. Tab to the Poll Results Browser tab to view poll results in real-time.

[Send Text Message]

Note: Speaker Text Options only appear when Poll is not selected.

Groups>>Message Browser

The Groups>>Message Browser page provides a table for viewing recently sent text messages. The message browser contains a row for each message that has been sent to a particular phone. The columns of each row contain the following information:

Column Description Message Message Body: The message text 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 phones. Sent To Desc: The description field of the phone 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.

To sort the list click on the column to sort by. To group items by a column, drag the column header (for the column to group on) into the light blue table header.

By default the last 30 days worth of messages are retained on the system. To change the retention value go to Services>Broadcast Services: Advanced Settings and edit messageRetentionDays to the number of days you would like to retain messages.

Part 13 98 SA-Announce User Guide 13 Server Redundancy

The server redundancy feature facilitates automated fail over of notification groups. The feature allows multiple SA-Announce servers to be clustered together to maintain notification group functionality during server fault scenarios.

Server Redundancy Overview

In redundancy mode a publisher and subscriber relationship is maintained to allow for data replication between servers. When the redundancy feature has been activated by assigning a publisher and at least one subscriber the subscriber(s) will redirect appropriate SA-Announce management GUI requests to the publisher. In other words all changes to the SA-Announce global data, which must be shared between servers, are performed on the publisher. The changes are then pulled down by the subscribers in the Cluster. See the Creating A Cluster section for further detail.

Once a Cluster has been created servers are assigned to a prioritized list called a Server Group which can then be assigned to notification groups to enable the redundancy feature. A Server Group can contain two or three servers. When 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 the priority-1 and priority-2 servers both experience a fault then the priority-3 server will begin to run the group (if a priority-3 server exists). 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 enable the redundancy feature is to assign a Server Group to notification groups and or schedules. This is done on the Groups>>Create / Edit Groups and Schedules>>Scheduled Broadcasts pages, 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 SA-Announce 8.3.14 or greater. All servers should be running the same SA-Announce version. Server OS Version In redundancy mode all servers must be running the same OS and bitness. 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

SQL Install Requirements: When configuring the SQL 2008 R2 SP1 install the following requirements must be met: 1. TCP/IP control must be enabled for the instance. On the application server Start> Microsoft SQL Server 2008 R2>Configuration Tools>Sql Server Configuration Manager, under protocols for the instance enable TCP/IP. 2. Mixed mode authentication (SQL server and Windows) must be used. This must be done when installing the instance.

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 SA-Announce 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 server cluster (publisher and one or more subscribers) must be configured (see Creating A Cluster). SA-Announce Server Groups At least one Server Group must be created (see Creating Server Groups). Server Group Association Notification groups must be assigned to a Server Group (see Associate Server Groups). External Phones If SA-Announce external phones are being used then each server must have its own pool of unique external phones setup in the standard manner (see Analog Paging System Integration). IP Endpoint Registration IP end-points such as IP speakers or desktop clients that register with SA- Announce 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: If there is no connectivity between servers then the request cannot be forwarded. For this reason it is a good idea to make sure load balancing URL's used for the SA-Announce API are set in the same prioritized order as the server group in SA-Announce. 13.1 Creating A Cluster

In redundancy mode a publisher and subscriber relationship is maintained to allow for data replication between servers. When the redundancy feature has been activated by assigning a publisher and at least one subscriber the subscriber(s) will redirect SA-Announce management GUI requests to the publisher. In other words all changes to the SA-Announce global data are performed on the publisher. The changes are then pulled down by the subscribers in the Cluster. Certain local based web pages are still available on subscriber management interfaces including multicast tests, external phone setup and other local based functions.

The redundancy feature should be setup using the web management GUI on the proposed publisher server. Navigate to Services>>Server Redundancy: Servers on the proposed publisher to begin:

Create Publisher -

The Server tab will be shown by default. The current server information will be listed in the Publisher panel. The Name and Description for the publisher will be auto filled with the server name and server IP by default, they can be changed at any time.

IMPORTANT: Existing SA-Announce implementations should use the existing server (that contains the notification groups) as the publisher in order to 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. Furthermore, subscribers added to the cluster will have their data deleted before the publisher data is replicated.

Note: A single SA-Announce server can be marked as a publisher without adding subscribers. In this case the redundancy feature will not be active but the service monitoring will run and make sure the service is started automatically if it is stopped unexpectedly.

Press the Create Publisher button to make the current server the publisher. After doing so the subscriber panel should appear (see next image).

Create Subscribers -

Once a publisher has been created the Subscribers panel will appear on the Servers tab.

IMPORTANT: When adding a subscriber any existing SA-Announce configuration data will be deleted. If groups or any setting changes exist on the server they 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.

Note: Servers should have their server site setting set before they are added as a subscriber. On the proposed subscriber servers SA-Anounce 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>SA-Announce: serverSite. When manually altering this setting it is important to make sure the supplied name of the Device Pool or Calling Search Space matches precisely (including case) the name of the Device Pool or Calling Search Space on CUCM.

To add subscribers (other SA-Announce servers) select <..Add a New Subscriber..> in the Subscriber field then enter a Name, Description and IP Address in the provided fields and press the Save button. The server will be added as a subscriber and all of its existing data will be replaced with the data that exists on the publisher.

Now that a cluster of servers has been created it is possible to Create Server Groups, see the next section for detailed information.

When a server that has experienced a fault comes back online it will resume responsibility for any notification groups it should be running (auto fail back). Wether a notification group is resuming on a server or failing over to a server there will only be a brief outage while the notification group virtual phone registers using the newly responsible server.

Navigate to the Services>>Server Redundancy page, Server Groups tab to configure Server Groups.

First select <..Add a New Server Group..> from the Server Group field. Next enter a server Group Name and Description in the provided fields. Finally select servers in the Available Servers list and move them to the Selected Servers list using the arrows between the two lists. The Selected Servers are ordered by priority (highest on top). You can rearrange the order of the servers by using the arrows to the right of the Selected Servers list.

Note: Publisher and subscriber servers can be used in Server Groups.

Now that Server Group(s) have been created they must be assigned to notification groups to enable the server redundancy feature. See the Associate Server Groups section for detailed information.

Once the Cluster has been defined and one or more Server Groups have been created the final step to enable the redundancy feature is to assign a Server Group to notification groups and or schedules. This is done on the Create / Edit Groups and Schedules pages, general tab. A new field Server Group has been exposed. Select the server group that the notification group should be a member of to enable redundancy on that group. If the server group is selected for a notification group then that group will run on the publisher only without any fail over servers.

Part 14 Web Service (API) 105 14 Web Service (API)

The SA-Announce web service (API) exposes methods that can be used to perform operations like 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 http:///SA-Announce/API/SAAnnounceAPI.asmx. A list of available methods will be shown with descriptions, clicking on one of the method names will navigate to the methods full description page which allows the method to be tested and shows sample request and response formats.

Programmers can access the web service description language file at http:///SA- Announce/API/SAAnnounceAPI.asmx?WSDL.

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.

Note: 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. 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. Information 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 SEP001122334455). 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 SEP001122334455). 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. 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. 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 (SA- Announce 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.

Part 15 Email Settings 109 15 Email Settings

Services>>Broadcaster Service: Email Settings

In order for SA-Announce to send emails when notification groups are activated the Services>>Broadcaster Service: Email Settings tab must be filled out.

Enter an SMTP Server in the provided text box and a Mailer from address and press the Save button to save the changes.

SA-Announce will now be able to send emails when groups that have email destinations are activated.

Part 16 Amber Alert Settings 111 16 Amber Alert Settings

Services>>Broadcaster Service: Amber Alert The AMBER Alert Program is a voluntary partnership between law-enforcement agencies, broadcasters, transportation agencies, and the wireless industry, to activate an urgent bulletin in the most serious child- abduction cases. The goal of an AMBER Alert is to instantly galvanize the entire community to assist in the search for and the safe recovery of the child. AMBER Alerts require the SA-Announce server have internet access to www.codeamber.org.

The AMBER Alert service runs inside the broadcaster 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 Alerts do not activate as a result of calling the emergency alert group, in this case the normal emergency alert functionality is carried out. Once you have activated AMBER Alerts by checking the Amber Alert checkbox for a particular group and saving the changes, alerts will be active as long as the broadcaster service is running. The service checks for new alerts immediately as the service is restarted and then checks again when the "new alert" interval setting is reached. It is important to have a low "new alert" interval setting so you will be notified of new alerts shortly after they occur. The "resend alert" interval setting controls how often active alerts are resent to the group endpoints.

The settings for the Amber Alert service are listed on the Amber Alert Settings tab. Amber Alert Setting Description Check for new alerts every This setting controls how often the service checks for Amber Alerts. 10 (minutes) minutes is the minimum and the default. Resend active alerts (minutes) This setting controls how often alerts are resent. 0 minutes is the default which means you will only receive AMBER Alerts once per update, the alert will not be resent while active unless a duration is entered here. IE to send alerts every 4 hours while they are active enter 240 for the resend value. Note that emails are never resent. Send alerts regardless of zip This setting controls the localization of Amber Alerts. If the setting is code unchecked you will only receive Amber Alerts that originated in your state. The setting is on by default which means you will receive all Amber Alerts regardless of the state they originated in. Send endangered children This setting controls wether Code Amber News Service (CANS) endangered "CANS" alerts children alerts are sent. These are missing or endangered children alerts that have not been deemed AMBER Alerts. The default setting is checked (on).

Sample Amber Alert:

*Press the Details button to see the complete text message, or visit http://codeamber.com in a web browser.

Part 17 114 SA-Announce User Guide 17 Weather Alert Settings

Services>>Broadcaster Service: Weather Alert Settings

The Weather Alert feature uses the National Weather Service to gather active alert data. Weather Alerts require the SA-Announce server have internet access to alerts.weather.gov.

The Weather Alert feature runs with the SA-Announce broadcaster 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 below table, alerts will be active as long as the broadcaster 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 expose the weather alerts check box. Select Weather Alerts Check the Weather Alerts check box, this will expose a FIPS entry field. Enter the FIPS code(s) Enter the FIPS codes for the counties you would like 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.

Note: You can enter a state FIPS code to monitor an entire state, state FIPS codes end in 000. Enable Events Make sure that events are enabled per the settings section described in the remainder of this section.

The Weather Alert tab on the Broadcaster Service page contains interval timer settings as well as the ability to select which events to trigger on. 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. 2 minutes is the minimum and 5 minutes is the default. Resend active alerts (minutes) This setting controls how often alerts are resent, 20 minutes is the default which means you will receive a weather alert every two hours while the alert is in effect. To disable the resend enter 0. Note that emails are never resent.

The Weather Alert Settings section also contains an area to configure which weather Watches, Warnings and Advisories to send alerts for. By default all alerts are deactivated. Please look the list over and select any alerts that may apply to your geographical location (simply select the item from the available side of the list and press the >> button to move the item to the selected side). See Weather Alert Supported Events for the list of all supported events.

Sample Weather Alert (9951 phone model):

***Note that the image will contain a 'details' soft-key. Pressing the soft-key will bring up the full description of the alert.

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

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

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

Part 18 120 SA-Announce User Guide 18 Background Music Settings

Services>>Broadcaster Service: Background Music Settings

The Background Music Settings section is used to configure the background music service parameters. Use of this service requires a multicast music streaming source (IE Syn-Apps Paging Relay or similar). 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: http://sa-announce-server-address/sa-anounce/phoneservices/ BackgroundMusic.aspx. Finally, subscribe phones to the service. Subscribed phones can activate the background music by selecting Services and then the name you used when adding the phone service.

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 (224.X.X.X - > 239.X.X.X). Music Stream Port Enter the port of the multicast background music stream (RTP ports only 24000 -> 36000).

Part 19 122 SA-Announce User Guide 19 IP Phone Services Configuration

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 This IP phone service provides an on phone directory of notification groups defined within SA-Announce. In this case the selected group is activated by programmatic dialing of the group phone. 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 the web 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 This IP phone service is used to display previously received messages. 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 (e.g. 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 (SA-Announce server) site.

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) with the following parameters: Service Name = SA-Announce Service URL = http://server-ip-address/SA-Announce/phoneservices/groupsdirectory.aspx where server-ip- address equals your SA-Announce server's IP address.

*Note: 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 = http://server-ip-address/SA-Announce/phoneservices/groupsdirectory.aspx?showAll=false.

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.

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 = http://server-ip-address/SA-Announce/phoneservices/webgroups.aspx where server-ip-address equals your SA-Announce server's IP address.

*Note: 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 = http://server-ip-address/SA-Announce/phoneservices/webgroups.aspx?showAll=false.

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.

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 = http://server-ip-address/SA-Announce/phoneservices/GetMessage.aspx where server-ip-address equals your SA-Announce server's 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 past messages.

To utilize the push-to-talk button on the 7921 / 7925 or 7926 wireless phone setup an SA-Announce Wokkie- Tokkie 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 7926.

For example, click the push-to-talk button to activate the group (see below), then hold the push-to-talk button down to talk. Release the button when done speaking. Note: The source caller must end the page using the " End Page" soft-key provided on the source phone.

Note: 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 (Communication Manager Admin>Device>Phone) to point to the following URL: http://server-ip-address/SA-Announce/PhoneServices/GetParams.aspx?id= Where server-ip-address is the IP address of the SA-Announce server and is the group-id as shown on the SA-Announce web administration groups page.

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 (e.g. speed dial) becomes a Service URL (direct access to a web URL). The Service URL can be used to activate an SA-Announce notification group (rather than dialing the number). This is useful as it can provide phone sourced local multicasting at a site located across the WAN from the main (SA-Announce 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 as this service can be used for all sites and multiple destination groups. Service Description Description for the service. Service URL http://x.x.x.x/SA-Announce/PhoneServices/GetParams.aspx - 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 - check this checkbox to signify that the parameter is required.

***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 web 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 = ” 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

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 you complete the steps above you can use this service for all phones in the company regardless of the destination group. Simply 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”

Part 20 Paging Relay Configuration 131 20 Paging Relay Configuration

Settings>>IP Endpoint Setup: Syn-Apps IP

The Settings>>IP Endpoint Setup: Syn-Apps IP tab is used to view and configure Paging Relay parameters. For information on adding Paging Relays to a 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 Syn-Apps IP area on the Settings>>IP Endpoint Setup: Syn-Apps IP tab. For details on Paging Relay registration see Paging Relay Setup.

Edit the following information for each of the paging relays (press Edit to begin editing a row and Update to finish): Paging Relay Setting Description Name Enter a name for the paging relay (default: MAC). Description Enter a description for the paging relay (default: device type). Firmware (Not Editable) The firmware version of the Syn-Apps IP Device. 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 (Not Editable) The Syn-Apps IP devices model name. IP Address (Not Editable) The IP Address of the Syn-Apps IP Device. Last (Not Editable) The date and time of the last registration or heartbeat message from the Syn-Apps IP Device. Clock Attached (Not Editable) True if the Syn-Apps IP Device has a clock attached.

Notes: The Syn-Apps device Control Port 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 devices in use (Paging Relays and Syn-Apps IP speakers). To change the Control Port SA-Announce uses to send commands edit the field at the bottom of the page and press Save to set the new control port.

The Firmware Update option 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 Update to begin the update on all registered devices that match the type of firmware specified.

[Settings>>IP Endpoint Setup: Syn-Apps IP]

SA-Announce supports all Syn-Apps Paging Relays with firmware version 2.2.1 or greater.

20.2 Paging Relay Setup

This section describes the configuration of the Syn-Apps Paging Relay.

Auto-Registration Setup:

Once you plug the Syn-Apps Paging Relay in it will use DHCP for network settings by default, this is the recommended configuration. The new Syn-Apps Paging Relays can be easily configured to auto register with SA-Announce so no further setup is required:

Set DHCP option 72 to the IP Address of your SA-Announce server:

IF you are using your routers to server DHCP you will want to add the option 72 command to the scope that is providing the speakers with IP address information:

ip dhcp pool Voice network 10.0.12.0 255.255.255.0 default-router 10.0.12.1 option 150 ip 10.0.0.21 dns-server 10.0.0.2 option 72 ip 10.0.5.38 lease 8 23 59

For Windows Server you would perform the following: http://www.cisco.com/en/US/products/sw/ voicesw/ps556/products_tech_note09186a00800942f4.shtml

Manual Registration Setup:

If DHCP cannot be used or option 72 cannot be set then the relay must be manually registered with SA- Announce. To manually register a Syn-Apps Paging Relay open a web browser on the SA-Announce host machine and perform the following:

1. Browse to http://localhost/SA-Announce/API/SAAnnounceAPI.asmx a list of the API methods will be shown. 2. Click on RegisterIPSpeaker, the following form will be shown:

3. Fill in the fields as shown in the above screen shot and then press the Invoke button. You may need to access the relays web page to gather the MAC and firmware version. 4. Verify the relay has registered by going to the SA-Announce web interface Settings>IP Endpoint Setup: Syn-Apps IP, the relay should show in the table.

Note: As of SA-Announce release 7.0.60 older paging relays are no longer supported and will need a firmware update to version 2.2.1 or greater to function properly with SA-Announce.

Paging Relay Web Page:

Once the relay has registered with the SA-Announce server (see above, setting DHCP option 72) you can find its IP address by going to Settings>>IP Endpoint Setup: Syn-Apps IP. Click on the devices IP address in the table to be directed to the relays web page.

The default login credentials for the device are: User Name: admin Password: admin

After logging into the web page you will see the home page and the basic device settings. To change the network and other settings of the device use the Admin Setup button.

[Syn-Apps Paging Relay web interface: Admin Setup page]

Part 21 Syn-Apps IP Speaker Configuration 137 21 Syn-Apps IP Speaker Configuration

Settings>>IP Endpoint Setup: Syn-Apps IP

The Settings>>IP Endpoint Setup: Syn-Apps IP tab is used to view and configure Syn-Apps IP Speaker parameters. For information on adding Syn-Apps (CyberData V2) 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.

Edit the following information for each of the speakers (press Edit to begin editing a row and Update to finish): IP Speaker Setting Description Name Enter a name for the speaker (default: MAC). Description Enter a description for the speaker (default: device type). Firmware (Not Editable) The firmware version of the Syn-Apps IP Device. 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 talkback 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 (Not Editable) The Syn-Apps IP devices model name. IP Address (Not Editable) The IP Address of the Syn-Apps IP Device. Last (Not Editable) The date and time of the last registration or heartbeat message from the Syn-Apps IP Device. Clock Attached (Not Editable) True if the Syn-Apps IP Device has a clock attached.

[Settings>>IP Endpoint Setup: Syn-Apps IP]

SA-Announce supports all Syn-Apps (CyberData V2) IP Speakers with firmware version 1.0.0 or greater.

21.2 Syn-Apps IP Speaker Setup

This section describes the configuration of Syn-Apps IP Speakers.

Auto-Registration Setup:

Once you plug the Syn-Apps IP Speaker in it will use DHCP for network settings by default, this is the recommended configuration. The new Syn-Apps IP Speakers can be easily configured to auto register with SA- Announce so no further setup is required:

Set DHCP option 72 to the IP Address of your SA-Announce server:

IF you are using your routers to server DHCP you will want to add the option 72 command to the scope that is providing the speakers with IP address information:

ip dhcp pool Voice network 10.0.12.0 255.255.255.0 default-router 10.0.12.1 option 150 ip 10.0.0.21 dns-server 10.0.0.2 option 72 ip 10.0.5.38 lease 8 23 59

For Windows Server you would perform the following: http://www.cisco.com/en/US/products/sw/ voicesw/ps556/products_tech_note09186a00800942f4.shtml

Manual Registration Setup:

If DHCP cannot be used or option 72 cannot be set then the speaker must be manually registered with SA- Announce. To manually register a Syn-Apps IP Speaker open a web browser on the SA-Announce host machine and perform the following:

1. Browse to http://localhost/SA-Announce/API/SAAnnounceAPI.asmx a list of the API methods will be shown. 2. Click on RegisterIPSpeaker, the following form will be shown:

3. Fill in the fields as shown in the above screen shot and then press the Invoke button. You may need to access the speakers web page to gather the MAC and firmware version. 4. Verify the speaker has registered by going to the SA-Announce web interface Settings>IP Endpoint Setup: Syn-Apps IP, the speaker should show in the table.

Syn-Apps IP Speaker Web Page:

Once the speaker has registered with the SA-Announce server (see above, setting DHCP option 72) you can find its IP address by going to Settings>>IP Endpoint Setup: Syn-Apps IP. Click on the devices IP address in the table to be directed to the relays web page.

The default login credentials for the device are: User Name: admin Password: admin

After logging into the web page you will see the home page and the default device settings. To change the basic device settings use the Device Config button, to change the network and other settings of the device use the Networking button (Not Required when using DHCP).

[Syn-Apps IP Speaker web interface: Home page]

Part 22 Desktop Notification Client Configuration 143 22 Desktop Notification Client Configuration

Settings>>IP Endpoint Setup: Desktop Client

The Settings>>IP Endpoint Setup: Desktop Client tab is used to view and configure the desktop notification client parameters. For information on adding desktop notification clients to a SA-Announce notification group see the Desktop Clients section of this manual.

Each Syn-Apps desktop client you plan to use with the system must be registered in the Desktop Clients area on the Settings>>IP Endpoint Setup: Desktop Client tab. Edit the following information for each of the clients (press Edit to begin editing the row and Update to finish): Desktop Client Setting Description Name Enter a name for the client (default: client user name). Description Enter a description for the speaker (default: client machine name). IP Address (Not Editable) The IP Address of the Syn-Apps Desktop Notificaiton Client. Version (Not Editable) The version of the Syn-Apps Desktop Notification Client. D.N. Enter a directory number for the client (Talk-Back only), this will be used for holler (intercom) addressing in a future release. Port (Not Editable) The client listen port. Last Heart Beat (Not Editable) The date and time of the last registration or heartbeat message from the Syn-Apps IP Device.

[Settings>>IP Endpoint Setup: Desktop Client]

Part 23 AND IP Speaker Configuration 145 23 AND IP Speaker Configuration

Settings>>IP Endpoint Setup: Syn-Apps IP

The Settings>>IP Endpoint Setup: Syn-Apps IP tab is used to view and configure AND IP Speaker parameters. For information on adding AND IP Speakers to a SA-Announce notification group see the Group IP Speakers section.

Each AND 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 AND IP Speaker registration see AND IP Speaker Setup.

Edit the following information for each of the speakers (press Edit to begin editing the row and Update to finish): AND IP Speaker Setting Description Name Enter a name for the speaker (default: MAC). Description Enter a description for the speaker (default: device type). Firmware (Not Editable) The firmware version of the speaker. 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 talkback 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 (Not Editable) The speakers model name. IP Address (Not Editable) The IP Address of the speaker. Last (Not Editable) The date and time of the last registration or heartbeat message from the speaker. Clock Attached (Not Editable) True if the speaker has a clock attached. GP Input 0/1 Each GPIO input can be set to activate an intercom to a selected phone (talkback speaker only) or to activate an emergency alert group. The GPIO button will both activate and deactivate the selected function.

Notes: The Control Port setting is not applicable to AND speakers. The control port is always HTTP port 80.

The Firmware Update panel is also not applicable to AND speakers, AND IP Speaker firmware must be updated using the ipspeaker. cfg file.

[Settings>>IP Endpoint Setup: Syn-Apps IP]

SA-Announce supports all AND IP Speakers with firmware version 796 or greater.

23.2 AND IP Speaker Setup

This section describes the configuration of AND IP Speakers.

Auto-Registration Setup:

Once you plug the AND IP Speaker in it will use DHCP for network settings by default, this is the recommended configuration. The new AND IP Speakers can be easily configured to auto register with SA-Announce so no further setup is required:

Set DHCP option 72 to the IP Address of your SA-Announce server:

IF you are using your routers to server DHCP you will want to add the option 72 command to the scope that is providing the speakers with IP address information (Example):

ip dhcp pool Voice network 10.0.12.0 255.255.255.0 default-router 10.0.12.1 option 150 ip 10.0.0.21 dns-server 10.0.0.2 option 72 ip 10.0.5.38 lease 8 23 59

For Windows Server you would perform the following: http://www.cisco.com/en/US/products/sw/ voicesw/ps556/products_tech_note09186a00800942f4.shtml

Manual Registration Setup:

If DHCP cannot be used or option 72 cannot be set then the speaker must be manually registered with SA- Announce. To manually register an AND IP Speaker open a web browser on the SA-Announce host machine and perform the following:

1. Browse to http://localhost/SA-Announce/API/SAAnnounceAPI.asmx a list of the API methods will be shown. 2. Click on RegisterIPSpeaker, the following form will be shown:

AND IP Speaker Web Page:

[AND IP Speaker web interface: Home page]

Part 24 Valcom IP Speaker Configuration 151 24 Valcom IP Speaker Configuration

Settings>>IP Endpoint Setup: Valcom:

The Valcom IP Speaker settings are located at Settings>>IP Endpoint Setup: Valcom. In most cases the settings will not need to be changed (when using Valcom version 2.x firmware, recommended). If using Valcom version 1.x firmware or non default multicast control and audio addresses for the Valcom speakers it will be necessary to match the SA-Announce settings to the speaker settings.

The Valcom speaker settings are shown in the Valcom VIP-102B IP Solutions tool under the System>>Network Settings option.

[Valcom VIP-102B Setup Tool (System>>Network Settings)]

24.1 Supported Valcom Speakers

SA-Announce supports the entire Valcom IP Speaker platform. These speakers include:

Valcom IP Speaker Model Supported Valcom VIP 130-L (one-way outdoor horn) Valcom VIP 402 (lay-in ceiling speaker) Valcom VIP 140 (wall speaker) Valcom VIP 411 DS (wall mount w/ digital clock) Valcom VIP 412 DF (wall surface mount w/ digital clock) Valcom VIP 430 (wall mount talk-back) Valcom VIP 821 (enhanced network trunk port) Valcom VIP 822 (duel enhanced network trunk port) Valcom VIP 824 (quad enhanced network trunk port)

This section describes how to setup your Valcom IP Speakers into groups for use with SA-Announce. For information on how to add these Valcom groups to a SA-Announce notification group please see the section IP Speaker Integration.

See the section Valcom IP Speaker Configuration for details on setting up the Valcom audio and control address/ port.

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 your 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 finally 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 and then add speakers to the group by marking the Device checkbox.

The group can now be used in SA-Announce notification groups and schedules (by adding the Dial Code to the Valcom input area of the IP Speakers tab of a group, see IP Speaker Integration)

[Valcom VIP-102B Setup Tool: System>>Audio Groups]

[Valcom VIP-102B Setup Tool: System>>Audio Group Membership]

Part 25 156 SA-Announce User Guide 25 CyberData IP Speaker Configuration

Settings>>IP Endpoint Setup: CyberData

The Settings>>IP Endpoint Setup: CyberData page is used to configure SA-Announce with the required CyberData speaker group parameters. The CyberData speaker groups are setup using the CyberData speakers' web page (use the CyberData discovery tool to discover the CyberData speakers on your network and web to their IP address). The speakers must be setup with multicast groups (MGroup mode) in order to function properly with SA-Announce, see the CyberData Speaker Setup section for details. Multicast is required from the SA-Announce application server to the CyberData speakers.

SA-Announce supports the entire IP Speaker platform from CyberData. These speakers include:

CyberData IP Speaker Model Supported VoIP Ceiling Speaker VoIP Paging Gateway VoIP Multicast Gateway VoIP Loudspeaker Amplifier, PoE VoIP Loudspeaker Amplifier, AC VoIP Loudspeaker Amplifier Wireless VoIP Paging Amplifier VoIP Intercom VoIP Paging Server VoIP 4-Port Zone Controller VoIP Talk-back Speaker

This section describes how to setup your CyberData Speakers into multicast groups for use with SA-Announce. See the section CyberData IP Speaker Configuration for details on adding these groups to the SA-Announce Interface.

First make sure the speakers are in MGROUPS mode. Browse to the web page of the speaker (default login: admin, admin) and select the Speaker Setup link button. On the Speaker Setup page set the speaker function to MGROUPS and press the Save Settings button.

Next browse to the MGROUPS Setup page by pressing the MGROUPS Setup button. Add groups to the speaker by adding a multicast address and port, priority and name for the group. Add the same group to all other speakers that are to be part of the group.

Part 26 Alertus Configuration 161 26 Alertus Configuration

Settings>>IP Endpoint Setup: Alertus

The Settings>>IP Endpoint Setup: Alertus tab is used to configure SA-Announce with the required Alertus parameters. For information on adding Alertus Beacon Groups to a SA-Announce notification group see the Alertus section.

Alertus Server Configuration

The Alertus Server must be network accessible from the SA-Announce Server. If a firewall is setup on the Alertus Server to block port 8280, an exception must be added to allow access from the server hosting the SA- Announce software.

In addition, the Alertus Server Software configuration must be modified to allow the SA-Announce application to communicate. This can be performed by connecting to the server hosting the Alertus Software and editing the AlertusMiddleware.impl.properties file located in the C:\Alertus\conf directory. Change the line that starts with the text "soap.alertusMiddlewareBasic.allowableIPs" to the following where [SA-ANNOUNCE IP ADDRESS] is the IP Address of the server running the SA-Announce software:

soap.alertusMiddlewareBasic.allowableIPs = 127.0.0.1;[SA-ANNOUNCE IP ADDRESS]

If this line does not exist simply add it anywhere in the file. You must restart the Alertus application for this change to take affect.

SA-Announce Configuration

To setup the Alertus integration the Alertus Web Service URL must be configured. Type the URL into the Alertus Web Service URL text box and press the Save button to save the changes. The URL will be verified and if it appears valid the Alertus settings will be extracted for use in SA-Announce.

The Message Duration (Seconds) entry box controls the default Alertus alert duration. For groups like Emergency Alert and schedules this setting is not used (the alert will be activated with the Emergency Alert / Schedule and it will be deactivated with the Emergency Alert / Schedule). For groups like Normal and Text the message duration setting will be used, the Alertus beacons will carry the message for the specified amount of time.

SA-Announce supports all Alertus Beacons.

26.2 Alertus Device Setup

This section describes how SA-Announce integrates with the Alertus System.

SA-Announce can automatically activate Alertus Beacon Groups that you have defined in the Alertus web configuration pages. Alertus Alert Profiles are also used by SA-Announce, the Alert Profile defines the way the Alert Beacons behave during an event (how the lights flash, which sound is played etc).

For proper operation SA-Announce requires that the Alertus system have at least one alert profile and one beacon group.

[The Alertus web configuration interface]

Part 27 Everbridge Configuration 165 27 Everbridge Configuration

Settings>>IP Endpoint Setup: Everbridge

The Settings>>IP Endpoint Setup: Everbridge tab is used to configure SA-Announce with the required Everbridge parameters. For information on adding Everbridge Scenarios to a SA-Announce notification group see the Everbridge section. Provide the following Everbridge web service information in the provided interface:

Everbridge Settings Description Web Service URL Enter the Everbridge web service url in the provided entry box. The default URL is https://www.everbridge.net/nns/3nWebServices. User ID Enter your Numeric Everbridge User ID. Organization Name Enter your Everbridge organization name. Password Enter your numeric Everbridge password.

Press the Save button to save the changes to the Everbridge web service settings. After pressing save the URL will be contacted so connectivity can be checked, if problems are encountered an error message will appear. The most likely cause of error would be that the server has no connectivity to internet.

After setting up the web service parameters enter the Everbridge Scenarios by Scenario Id and Name and press the Add button. The Scenario ID must be the same as found on the Everbridge Scenarios page. See the Everbridge Setup section for details on finding existing scenario Id's and creating new scenarios.

This section describes how SA-Announce integrates with the Everbridge System.

SA-Announce can automatically activate Everbridge Scenarios that you have defined in the Everbridge web configuration pages when a SA-Announce group is activated.

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 the scenario title and number are listed (enter the scenario title/number of scenarios you would like to use in SA-Announce by browsing to SA-Announce: Settings>>IP Endpoint Setup: Everbridge tab. This process is described in the Everbridge Configuration section.

To create new scenarios in the Everbridge system you must first create an unscheduled notification (Send Notification) and then use the Scenario Manager>>Create Scenario to create a scenario using that unscheduled notification.

[The Everbridge web configuration interface: Scenario Manager>>Manage Scenario]

Part 28 168 SA-Announce User Guide 28 Facebook Configuration

Settings>>IP Endpoint Setup: Facebook

The Settings>>IP Endpoint Setup: Facebook tab is used to integrate SA-Announce with your Facebook account.

The setup process must be preformed on the application server. The application server must have access to www.facebook.com at all times to provide this service.

From the application server open the SA-Announce administration interface and browse to Settings>>IP Endpoint Setup: Facebook. Push the Setup Facebook button to perform the setup procedure. You will be directed to Facebook.com, sign in using your account credentials and click allow on any requests for authorization.

After the setup completes for the first time you are ready to update your Facebook status automatically by pressing the button again as instructed by the message shown below the button. This will add a new status post to your Facebook wall which will instruct your friends to visit a link to allow the application access to send notifications. Only friends who visit the link and allow access will be able to receive the notification from SA- Announce. We recommend that you notify your friends (IE students on a campus) by other means as well to visit the link added to your profile wall to make sure they have allowed access, otherwise they will not receive notifications.

Once the setup is complete you will be able to use the "Notify Facebook Friends" checkbox on the Create Edit Groups page (for text and emergency alert group types only). Checking the checkbox for a particular text or emergency alert group will integrate that group with your Facebook account. Friends who have allowed the application access will receive a Facebook notification whenever the group is activated. The notification will consist of the text or emergency alert group message text.

Part 29 170 SA-Announce User Guide 29 Twitter Configuration

Settings>>IP Endpoint Setup: Twitter

The Settings>>IP Endpoint Setup: Twitter tab is used to integrate SA-Announce with your Twitter account.

Simply enter your Twitter user name and password in the provided fields and press the Save button to save any changes. After saving the credentials you are ready to integrate Twitter with an emergency alert group.

Part 30 172 SA-Announce User Guide 30 Analog Paging System Integration

Settings>>External Phone Setup

This section describes how to setup the dialers that facilitate the analog paging system integration. The dialers are virtual phones that will be added to your Cisco Unified Communications Manager, when needed SA-Announce will virtually take them off-hook and dial the overhead system in question. Communications Manager expertise is required to properly configure the section (IE Device Pool / Region, CSS, and Partition should be well understood parameters of the Communications Manager in question).

For information on adding analog systems to a paging group see the External Phones section.

The Settings>>External Phone Setup page allow automatic creation of the dialers used in the analog paging system integration. It is recommended you add a dialer for each simultaneous overhead system activation that can occur plus two for busy detection purposes (IE if four sites each have one overhead system [4 + 2] add 6 dialers).

All dialers should have the same Device Pool and CSS (Calling Search Space) since 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 and all of the overhead systems that are to be integrated with the SA-Announce system.

The following parameters are requested in the add phone interface: 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 (this setting does not affect the dialer functionality, lines simply require partitions to make them unique and to add control mechanisms). CSS Select a Calling Search Space for the line to reside in, the calling search space 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).

Once the parameters are filled out press the Add Phone button to add the virtual phone to Communications Manager. Repeat to add all of the necessary dialers.

Note: To delete a dialer phone use the table on the Settings>>External Phone Setup page to gather the MAC addresses or Line Numbers of the Phones. Then use CUCM administration to search out and delete the phones and lines in question.

SA-Announce supports all analog paging systems that integrate to Communications Manager.

If you can dial your paging system from an IP phone, SA-Announce will be able to access the system. SA- Announce supports single and multi zone systems.

30.2 Supported Analog Interfaces

SA-Announce can connect to paging systems that are integrated with FXS, FXO, E&M interfaces hosted and ISR gateways, VG224, VG248, and ATA's.

Part 31 176 SA-Announce User Guide 31 Busy Detection Options

SA-Announce offers two modes of determining if IP phone members of a notification group are busy. Standard notifications are not delivered to busy end-points, only emergency notifications are. The two modes are described briefly below and in more detail in the following sections. Use the following table to determine which busy detect mode should be used.

Busy Detection Mode Description XML Busy Detection This is the default busy detection mode. In this mode SA-Announce will use the Cisco IP phone priority scheme for busy detect. This mode should accommodate most installations. There is no additional setup required in this 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. 31.1 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 Syn-Apps to send phones commands that will only be executed if the phone is idle.

All standard page groups will respect your busy status and will not interrupt active phone calls with a page unless the emergency checkbox is checked.

31.2 TAPI Busy Detection

TAPI integration is necessary for proper busy detection in some implementations where many phone lines are shared. This is because when those shared lines are placed on hold, all phones sharing the line will appear "XML busy", a false positive.

Please 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 lines that are to be monitored is an important consideration when using the TSP with Syn-Apps applications. This is because each TSP can only monitor 2000 lines1 maximum.

Therefore it is first necessary to determine how many lines must be monitored and divide by 2000 to find the number of TSP instances that will be required.

Each TSP instance requires its own unique application user with a unique set of phones/lines to monitor. If more than one TSP is required it will be necessary to partition the phones/lines 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. 1This limit has increased in recent versions of CUCM.

To configure the Cisco TSP it is necessary to create a new application user on the CUCM system. The user is used for access control and contains a list of associated phones/lines that represent the lines that will 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 this application user. These are the devices that will be monitored. Permissions Information Add permissions for the following groups: Standard CTI Allow Call Monitoring. Standard CTI Allow Call Park Monitoring Standard CTI Allow Calling Number Modification Standard CTI Enabled Finalize Save Click the Save button to finalize changes.

After the Application User(s) have been 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 version of CUCM will have two versions of the TAPI Client, one for 32-bit and one for 64-bit, choose the version that 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 Userid 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 (or select Phone and Modem options on Windows 2003). 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.

Part 32 Information Center 181 32 Information Center

SA-Announce 7.x introduces a new information center that provides quick access to the following items:

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

All of this information can be accessed by clicking on the Syn-Apps head graphic located in the upper left corner of the administration interface. To stop viewing the data click on the Exit Menu button in the lower right corner or simply click on the main SA-Announce web page to close the information window.

Please note that all data in the information center is retained for 90 days by default. To adjust the retention period modify the activityRetentionDays setting at Services>Broadcast Services: Advanced Settings.

Part 33 184 SA-Announce User Guide 33 Custom Wave File Upload

Schedules>>Wav File Upload

It is possible to add custom wave files to the SA-Announce notification system, for use with schedules and emergency alert group types. Browse to the Schedules>>Wav File Upload page to upload new wave files to the system.

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 the sound recorder bundled with windows 2003 (or other audio conversion utility) or record a message with Unity Voice Mail to create a custom audio file.

Using Windows Sound Recorder to convert or create a custom audio file: Custom Audio File Description Launch Sound Recorder Start\Programs\Accessories\Entertainment\Sound Recorder Open File Open the File menu and select New to create a new file for recording or select Open to open an existing file. Record If recording a new file click the Record button to begin recording. Click the Stop button when recording is complete. Save As Open the file menu and select Save As and then select the format change option. Set the format to CCITT u-Law, 8KHz, 8bit, mono.

To add a new wave file to the SA-Announce system: Add Custom Audio File Description Navigate Navigate to SA-Announce Schedules>>Wav File Upload Browse Press the Browse button to add a file to upload. Add Add more files to upload using the Add File button. Upload Press the Upload button to complete the process and upload the wave file(s) to the system.

The newly added wave files are now available for association to emergency alert groups and schedules.

Part 34 Customizing Audio Feedback 187 34 Customizing Audio Feedback

You can customize SA-Announce audio prompts by modifying the wave files included with SA-Announce. The prompts you hear 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\Wav directory. A brief description of each of the files is contained in the next section Audio File Descriptions.

[See the chapter Custom Wave File Upload to add custom wave files for use with emergency alert groups and schedules]

SA-Announce 2.0 Voice Prompts

Audio files 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.

You can use the sound recorder bundled with windows or record a message with Unity Voice Mail to create a custom audio file.

Use Windows Sound Recorder to convert or create a custom audio file: Custom Audio File Description Launch Sound Recorder Start\Programs\Accessories\Entertainment\Sound Recorder Open File Open the File menu and select New to create a new file for recording or select Open to open an existing file. Record If recording a new file click the Record button to begin recording. Click the Stop button when recording is complete. Save As Open the file menu and select Save As and then select the format change option. Set the format to CCITT u-Law, 8KHz, 8bit, mono.

34.1 Audio File Descriptions

The prompts you hear 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\Wav directory. A brief description of each of the files is contained in the below table:

Audio File Description - 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." AutoConfCallerFeedback Played to the caller of an auto conference group as it is starting up. "Please stand by while users are added to the conference." ConfBusy Played to the caller of an auto conference group when the target MeetMe number already active. "The MeetMe conference could not be started, make sure the conference is not in use." ©2009 Syn-Apps L.L.C. 188 SA-Announce User Guide

ConfXferError Played to the caller of an auto conference group when the caller cannot be transferred to the MeetMe. "There was an error transferring to the MeetMe conference please verify settings." dtmf_0 - dtmf_star *Do not edit the DTMF files they are used when in-band DTMF is required. EAActivated Played to the caller of an inactive emergency alert group (alert mode or timed mode). "Emergency Alert notification has been activated." EACanceled Played to the caller of an active emergency alert group (alert mode) . "Emergency Alert notification has been canceled." GroupActive Played to the caller of an active record-n-play group . "We're sorry but the group you have dialed is currently active." Holler Played to 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 call 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 (IE 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 (IE 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 with it. "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 the "close group if overhead busy" setting is on. "Overhead destinations are busy, please try again later." RecordNPlay Played to the caller of a RecordNPlay group when the setting rnpCallerAnnouncement is on. "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 who's paging relay has failed to open properly. "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 wrong, before hanging up. “You have entered an incorrect security code, please call back and try again. Goodbye."

SomeDestBusy When so many destinations are busy that a confirmation tone would not otherwise be sent. “Some destinations are busy…"[Paging Continues].

Part 35 Advanced Paging Configuration 191 35 Advanced Paging Configuration

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

For more information please refer to the Cisco Multicast Quick- Start Configuration Guide (http://www.cisco.

com/warp/public/105/48.pdf).

35.2 Multi-Site Centralized SA-Announce Server

Part 36 Troubleshooting Guide 195 36 Troubleshooting Guide

This chapter will attempt to explain the troubleshooting of issues with 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 (IE Configuration or Broadcaster Service). Each subcategory explains the proper approach to use to troubleshoot the issue. Each subcategory may also contain details of specific known issues and their resolution.

Note that upgrades of SA-Announce require running the configuration utility to completion. It is a common mistake to upgrade SA-Announce and then uncheck the "run configuration" checkbox on the final page of the installation. Make sure configuration has been run to completion successfully if you have recently upgraded the product.

It is also a good idea to run the configuration utility to try to resolve or expose any major issues. Examples include: ccmadmin credentials have changed, database instance is not running, missing virtual directory, etc. See the Configuration Utility section of the manual for details on running the configuration utility. If a problem does arise during configuration consult the Configuration Issues section of this troubleshooting guide.

Problem Categories Overview

1) Installation / Configuration - Consult this section if installation or configuration fails. (a)Windows Environment Issues - Issues due to Windows Environment. (b)Installation Issues - Issues encountered during installation. (c)Licensing Issues - Issues with SA-Announce licensing. (d)Configuration Issues - Issues encountered while running the SA-Announce configuration utility; Web page does not display after configuration.

2) Web Interface (GUI) - Consult this section if the SA-Announce web interface does not display or functions incorrectly. (a)GUI Log File - Location and description of the GUI log file. (b)Group Creation - Errors creating a group, errors calling a group, IP phones not listed. (c)Text Messaging - Errors sending text messages using the send a message page. (d)Other - External Phones, Multicast Settings, GUI graphical issues.

3) Broadcaster Service (Paging) - Consult this section if the broadcaster service fails to start or notifications fail in some manner. (a)Broadcaster Log Files - Location and description of the broadcaster log files. (b)Service Start Issues - Broadcaster service will not start. (c)End Point Command Issues - End points do not respond to notification commands. (d)Audio Issues - End points respond to notification commands but do not broadcast audio or 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. (a)Groups Directory - Issues with the SA-Announce groups directory phone service. (b)Web Dialer - Issues with the SA-Announce web dialer phone service. (c)API - Issues with the SA-Announce API.

This section describes troubleshooting techniques for issues that commonly occur during the installation and configuration of SA-Announce. Consult this section if you experience problems with the installtion or 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 SA- Announce. 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 SA- Announce using the SA-Announce configuration utility.

This subsection describes common issues that can occur on the SA-Announce application server Windows environment. Consult this subsection when Windows environment issues exist after checking the basic Windows setup instructions in the Application Server Requirements section of the manual.

Types of windows issues that can occur include installation / configuration program failure (doesn't run) and event log errors.

Windows 2003 Common Issues:

No known issues at this time.

Windows 2008 Common Issues:

No known issues at this time.

This subsection describes common issues that can occur during the installation of SA-Announce. Consult this subsection when installation fails. Consult the Configuration Issues subsection if the SA-Announce configuration utility fails.

If the installation of SA-Announce fails there are a few common reasons why this might 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 (rare).

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 here there configuration utility will be pre-empted by a license file selector, configuration cannot be run without a valid license file.

Common Licensing Issues:

1) No License in Base Directory: Make sure the "Syn-Apps.license" exists in the program base directory. "Syn-Apps.license.txt" will not be seen as a license. 2) Use of Unactivated Version of a Previously Activated License: If a license is activated the unactivated license in the program base directory is replaced with the activated license. In many cases customers change SA-Announce servers and try to use the unactivated license they were originally sent, this will not work. The activated license needs to be obtained from the old program base directory or Syn-Apps support. 3) Licensed Phone Count Exceeded: a) Phones Total Licensing Model: If the licensed phone count is exceeded in this licensing model then SA-Announce sees more devices on the configured CUCM cluster than the license allows. Syn- Apps paging devices are not counted towards license usage. Any other Device>Phone on the CUCM cluster will be counted towards the licensed phones. Removing unused devices on CUCM, followed by SA-Announce Services>Broadcast Services: Service, Refresh Data will update the count. b) Phones in Use Licensing Model: If the licensed phone count is exceeded in this licensing model then devices must be removed from notification groups until the unique devices used in all groups meets the requirement.

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\SA-Announce\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: The Application Server Credentials configuration page requires the user to enter the Windows credentials they are currently logged on with. This user must be an administrator of the system (local administrator account recommended). These credentials are also used for the web site impersonation account, if an impersonation error occurs when opening the website after configuration then the account entered is not appropriate.

3) Application Database Instance: The Application 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 "SynApps" database instance and an error will occur at this point in configuration. Common solutions include: (a) 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 are "SQLExpress" for SQLExpress manual installs and blank for SQL enterprise installs. There is always a chance that the user defined some instance name during manual configuration of SQL, this instance name must be used or another instance must be created. The instance name can generally be determined by going to the Windows services panel and looking for services like "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. (b) SQL does Not Exist on Application Server: Install SQL on the application server, note the instance name you create. Any authentication mode is fine. (c) 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.

4) 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:

(a) 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. (b) 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. (c) Wrong CUCM Version Selected: Make sure the proper CUCM version checkbox is checked on the first page of configuration. (d) 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.

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 Misconfigured: 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: (i) Execute Permissions: scripts only or scripts and executables. (ii)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.

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 or polls via the GUI. 4. Other: This subsection describes common issues that occur in other areas of the GUI (External Phones, Multicast Settings, ...).

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. For paging (IE broadcaster service) issues consult the Broadcaster Service section first.

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.

Sample log excerpts are shown below using the "ERROR" logging level, this is the default logging level. At this level only errors will be shown. The logging level can be changed on the Services>Broadcast Services>Service Log Level tab, "Web Site Minimum Error Level" setting. The samples show various errors that can occur along with a brief explanation. Comments are shown in Grey.

Common Errors:

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 should be detailed in the GUI log file and on screen in the GUI. A few of the common errors are listed here:

1) No Connectivity to CUCM: When adding an audio group a line and device are added to the CUCM system, if there is no connectivity to the CUCM 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.

When adding an audio group a line and device are added to CUCM in that order and then the system data is refreshed. If there is an error 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 be met with an error: line exists. Once the system is refreshed and SA-Announce knows about the line and a warning (line number in use in this partition) will be given if the line is used in a group, check the force use checkbox to continue and add the group.

Group is Fast Busy

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/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 (note: 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 (IE custom uses G.729 only) it will be 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 phone is registered. The broadcaster logs can also be consulted. 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

If some or all IP Phones are missing from the IP Phones tab there are a few likely causes:

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.

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

This subsection describes other common issues that can occur when using the SA-Announce web interface (GUI).

External Phone Setup

If errors occur while adding external phones on the settings>external phone 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 some external number so they must have settings that allow them to dial this number with a G.711 codec lookup. Common misconfigurations 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, so all external phones must be able to reach all possible external destinations you intend to integrate with. 3. External phones dial numbers so the usual Calling Search Space rules apply. 4. External phones must get a G.711 codec lookup when dialing external systems (IE 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 (IE to connect 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 page, Default and Sites tabs, is where multicast is turned on / off. The default tab contains the global settings that are applied to all sites as long as the sites have not been previously altered. When a site is altered on the Sites tab the default settings will not apply to that 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 as it pertains to notification groups see the Audio Issues section.

GUI 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 (Firefox and Safari work reasonably well). When using Internet Explorer version 8 there can be some graphical issues, please activate compatibility mode for the SA-Announce web site on IE 8.

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.

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\SA- Announce\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; note that 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: Calling Party:5067 Called Party Name: Called Party: 2308 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 [230.20.20.21], receivingPort=24588 02/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 : 1038 4fa0f2c ExecuteAsync : runSync results: total[38] success[38] busy[0] error[0]

Page w ith one error:

02/15/10 18:14:32 : 1090 78bf604 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\,std::allocator >* , basic_string\, std::allocator >* serverIpAddress, basic_string\,std::allocator >* content, basic_string\,std::allocator >* userName, basic_string\,std:: allocator >* passw ord, Int32 retriesCount, Int32 retryDelay)

02/15/10 18:14:32 : 1090 4fa2414 PhoneXml : ERROR [SEP001F9E26A392, 172.21.3.112] 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\,std::allocator >* , basic_string\, std::allocator >* serverIpAddress, basic_string\,std::allocator >* content, basic_string\,std::allocator >* userName, basic_string\,std:: allocator >* 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 : 1038 4fa0f2c 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.

This subsection describes common problems that occur when trying to start the SA-Announce broadcaster service. If the service will not start one of the following issues is most likely the cause:

1. Service Install Issues: Open the windows services panel, find the SA-Announce Broadcaster service, right click it and select properties. On the properties page select the Log On tab, make sure the account credentials being used are valid by retyping 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 remoting 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...

This subsection describes common problems that occur when sending phones and other end points commands. Consult this section when end points are not responding properly to the commands they are being sent. For example, when sending a standard audio command to a Cisco IP Phone the phone will lite up its speaker and mute lights and make a "boop" sound when the command is properly received. If this does not occur then this is the proper section to consult, if the phone or end point 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 try and understand if the issue occurs intermittently and/or if the issue occurs when a single endpoint is tested versus many at the same time. Network configuration issues are generally to blame for intermittent command delivery especially when under a heavy load.

Note: When troubleshooting an end point command issue as it pertains to a particular notification group it is always best to first verify that the end point(s) 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 . 3. Phone IP not Known: The phone must be registered and SA-Announce must know its IP. Verify by going 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-Level-Administrator) or CUCM patch required UCM 4.3.2-168. 4. 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 . 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 (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.

ShoreTel IP Phones:

There are a number of basic requirements that must be met in order for ShoreTel phones to receive commands properly, they are listed here:

1. Application server has access to port 80 on the phones (firewall / proxy). 2. Phones customNN.txt file has TrustedServers as in setup . 3. Phones must have API access enabled on the ShorewareDirector>device>phone settings page (or HTTP timeout will occur on all commands). 4. Phone IP not Known: The phone must be registered and SA-Announce must know its IP. Verify by going 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. 5. Phones must be XML enabled model types . 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 (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 PAPIError=4 is returned by a command an authentication error has occurred.

Syn-Apps IP Speakers and Paging Relay:

Syn-Apps IP Devices must be registered with the SA-Announce server in order to receive commands properly. If the devices are registered they will show in the Syn-Apps IP device table (Settings>IP End Point Setup::Syn- Apps IP).

See Syn-Apps IP Speaker Setup and Paging Relay Setup for setup and manual registration details.

There are a few basic requirements that must be met in order for Syn-Apps IP Devices to receive commands properly, they are listed here:

1. Application server must have access to port 6789 (default) on the devices. 2. Consult broadcaster logs for other errors.

Other Devices:

Consult the SA-Announce manual for detailed setup info for other compatible devices. Common issues may be listed here at a later date.

This subsection describes common problems that can occur with audio arriving at end points. 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 (similar to above).

Multicast Audio:

When multicast audio has been enabled and end points are responding well to commands yet not broadcasting audio the most likely cause is that multicast is not properly enabled on the network between the SA-Announce server and the end points. See the Multicast Requirements section of the manual for more information on configuring multicast on the network.

Note: To determine if the issue is network related or application server related, run a wireshark trace on the application server while paging, if the multicast audio shows up in the trace (filter: ip.addr==230.20.20.20 or 230.20.20.21 defaults) then the application server is sourcing the audio, the problem is likely multicast configuration on the network. If the audio does not show up then a firewall is likely blocking it on the application server.

The best way to test multicast connectivity of IP Phones is by using the server to phone multicast test (Settings>Multicast Settings>Server to Phone Multicast Test). See the Multicast Configuration section of the manual for more detail.

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 (PCM 8kHz 8-bit mono is the proper format). 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.

This section will explain 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 playing.

The SA-Announce Scheduler service log file is located at C:\Program Files\SynApps\SA- Announce\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:

There are a few reasons why the scheduler service would fail to start:

1. No Schedules to Serve: There must be a schedule configured or the service will not start, has a schedule been created? 2. Service Install Issues: Open the windows services panel, find the SA-Announce Scheduler service, right click it and select properties. On the properties page select the Log On tab, make sure the account credentials being used are valid by retyping 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 make sure the schedule is set to play for the day and time you are testing, failing to notice that 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 fire according to the application servers clock, it should be synchronized with a NTP.

This section describes common issues that can occur with the SA-Announce phone services and the SA- Announce API. Consult this section when problems occur when using the SA-Announce phone services (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 three 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.

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 ok 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 Not 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, it can be changed to only show groups that the accessing phone is a member of. To enable this setting see the Notification Group Directory section of the manual.

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 (that activated the web dialer group) will be instructed to transmit multicast audio to the destination phones which should all be local to the source. This will allow 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 SA- Announce 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 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, select useCiscoStartMedia, setting it to true will enable the feature. 3. All groups are shown to all users: This is the default mode of the directories, it can be changed to only show groups that the accessing phone is a member of. To enable this setting see the Web Dialer Directory section of the manual.

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 http://SA-Announce-Server-IP/SA-Announce/API/ 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" (Services>Broadcast Services>Settings). If this is the case the server will not be able to access secure methods like initiating an emergency alert. 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.

Part 37 222 SA-Announce User Guide 37 Help and Support

The following sections describe the Help section of the SA-Announce interface. 37.1 Documentation

Help>>Documentation

The Help>>Documentation page contains the SA-Announce User Guide in PDF format.

Help>>Request Support: Knowledge Base

The Request Support page contains a Knowledge Base tab that can be used to look at known issues and to add feature requests. Please consult the knowledge base for solutions to known problem before proceeding to the Prepare Report tab to enter a new trouble ticket.

Help>>Request Support: Prepare Report

The Request Support page contains a Prepare Report tab that can be used to generate a Syn-Apps support request. This is the preferred method of obtaining support as all log files will be automatically sent to Syn-Apps Support and a trouble ticket will be created. FTP and email access is required for the process to work fully automatically (See Email Settings to setup the email system before requesting support).

To request support please fill out the following information in the interface provided on the page: Prepare Report Field Description Contact Email Address Enter the email 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. 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.

[Help>>Request Support: Prepare Report]

Please feel free to contact Technical Support directly with any issues you may have.

[email protected] or 866-664-6071, option 2.