InformaCast Advanced Notification is a software solution developed by Singlewire Software that enables Cisco telephone systems and connected appliances to broadcast notifications via audio message and text message. InformaCast allows messaging an unlimited number of Cisco IP Phones, IP Speakers. Messages can be via text message, live audio, pre-recorded audio or text to speech audio.
The software manages lists of users who can send broadcasts, and devices to send broadcasts to. Users and devices can be sorted into groups depending on situations and who needs to see the message. Messages can be pre-built with text audio and images, or built when needed. Then with the press of a button, messages are sent to groups of users via SMS text, email, phone calls and on-premises devices such as desk phones, IP speakers, desktop computers and more for maximum reach.
In the context of Cisco Unified Communications Manager, 2 different licenses are available: Basic Paging is supplied through an OEM agreement with Cisco, and this can be upgraded to the Advanced Notification package. With the basic license, access to configuration information is heavily reduced. We are unable to provide a complete report.
This configuration report lists all configuration settings for the Singlewire InformaCast setup.
The Home section provides essential system information and status for the InformaCast server deployment. This includes comprehensive platform health monitoring, version details, and licensing information that enables administrators to quickly verify system configuration and operational status.
This section contains:
1 Report Information
1.1 Report Generation
Report Info Report Date Report generated for Description Server Info InformaCast Version InformaCast License Type InformaCast IP Report Settings Report Type Visual Style Report Content Template HTML Template Word Report Tool Info Report Tool Version Report Tool License 2 Home
2.1 Overview
The Platform Overview provides a comprehensive system status dashboard showing InformaCast server health and configuration across multiple components. This includes server version information, licensing status, backup configuration, SLP and LDAP integration status, SIP user agent status, multicast port allocation, and JTAPI settings.
The section also displays phone update schedules and statistics (rebuild/refresh status, phones retrieved, phones used versus licensed), configured Cisco Unified CM clusters with their CTI provider details, active CTI ports and route points, SIP account status, and speaker registration statistics. This centralized view summarizes the overall platform health and configuration status.
| Platform Overview | |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
2.2 Platform
The Platform Overview displays essential system information about the InformaCast server installation including product name, version, build number, and version bundle hash. This section provides quick identification of the deployed InformaCast platform version and build details.
| Platform | |
| Product | |
| Full Name | |
| Application | |
| Version | |
| Build | |
| Version Build | |
| Version Build Hash | |
2.3 License
The Licensing section displays comprehensive InformaCast license information including license mode (Purchased, Subscription, Sales Demo, or Basic Paging), licensee details, expiration dates, and application parameters. This includes limits on phones, IP speakers, bell schedules, and feature codes such as Audio and Message Confirmation capabilities.
For v15 systems, plugin licenses are also displayed showing the licensing status for all available plugins including CallAware, Conference Call, LPI (Legacy Paging Interface), Night Bell, Park and Page, and others. Each plugin license shows maximum triggers or instances allowed and expiration dates where applicable.
| Licensing | |
| Overview | |
| Application | |
| Licensee | UPLINX Software Demo InformaCast EX Non-Subscription + LPI Contract Number: 00020749 |
| Issuer | |
| License ID | |
| Created | |
| License Manager URL | |
| License Manager Available | |
| License Renewal Status | |
| Server IP Address | |
| License Terms | |
| License Mode | |
| In Trial Mode | |
| Expiration | |
| In Grace Period | |
| Grace Expiration | |
| Feature Codes | |
| Feature Codes | MessageConfirmation |
| Application Parameters | |
| Functionality | |
| Maintenance Contract | |
| Max Bell Schedules | |
| Max IP Speakers | |
| Max Phones | |
| Plugin Licenses | |
| CallAware | |
| ConferenceCall | |
| InboundEmail | |
| InboundCAP | |
| LPI | |
| M2M | |
| NightBell | |
| OutboundEmail | |
| ParkAndPage | |
| PrayerTimes | |
| QuickURL | |
| InboundRSS | |
| Script | |
| WordPress | |
3 Broadcasts
The Broadcasts section contains all message configurations that can be sent to recipients through InformaCast. Messages are the core content templates used for emergency notifications, scheduled announcements, and routine communications delivered to phones, speakers, desktop notifiers, and other connected devices.
This section contains:
- Messages - Configured broadcast messages with audio files, text content, priority levels, and customization settings
3.1 Messages
The Broadcast Messages section displays all configured InformaCast messages including their descriptions, content type (audio, text, or both), duration, priority levels, and associated audio files. Each message shows its short text, long text, text-to-speech (TTS) settings, and whether it is customizable for dynamic content insertion during broadcast.
Messages can be audio-only, text-only, or contain both components, and may include message confirmation requirements, panic button functionality, and icon assignments for visual display on compatible devices.
| Messages | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 Broadcast Triggers
Broadcast Triggers enable automatic message delivery based on various event sources and scheduled activities. These triggers monitor external systems, phone events, and time-based schedules to initiate InformaCast broadcasts without manual intervention, providing automated emergency response, routine announcements, and scheduled notifications.
This section contains:
- Event Sources - Plugin-based triggers that monitor external events and phone activities to automatically initiate broadcasts
- Bells - Scheduled broadcast automation including bell schedules, ring lists, and time-based announcement delivery LI>Broadcast Schedules enable the automated delivery of InformaCast messages at specific dates and times
4.1 Event Sources
Event Sources provide plugin-based integrations that automatically trigger InformaCast broadcasts based on monitored events from external systems and telephony activities. Each plugin monitors specific event types and initiates configured message broadcasts to designated recipient groups when trigger conditions are met.
Available event source plugins include:
- CallAware - Call recording and call redirection triggers for emergency call monitoring and routing
- DialCast - Dial-in triggers that send broadcasts when specific SIP numbers are dialed
- Inbound CAP - Common Alerting Protocol message reception for external alert integration
- Inbound Email - Email-triggered broadcasts based on monitored email accounts
- Inbound RSS - RSS feed monitoring for automated content-based notifications
- M2M Contact Closures - Hardware contact closure monitoring for physical switch integration
- Night Bell - CTI port monitoring for after-hours call handling and redirection
- Park and Page - Call park code monitoring for overhead paging initiation
4.1.1 CallAware
CallAware is primarily used to detect when a 911 call has been dialed, which then triggers an InformaCast broadcast. It can also be used to detect calls to numbers other than 911, monitor calls that have been detected, and record those calls. For example, you could use it to trigger an InformaCast broadcast whenever someone calls the Front Desk, and a supervisor could elect to monitor those calls for quality assurance or record them for review at a later date.
In this section you will find:
- Call Redirects
- Routing Requests
- Locations
- Configuration
4.1.1.1 Call Redirects
Before CallAware can begin routing calls to Cisco IP phones for Unified CM, you must create call redirects. You only need to work with call redirects if you have configured Cisco Unified CM to use CTI; that use Route Point Name and the DN field. If you want to use routing requests, go to Manage Routing Requests.
The following call redirects are configured:
| Groups | |||||||||||||||||||||
| |||||||||||||||||||||
4.1.1.2 Routing Requests
A routing request contains routing instructions for calls observed on a particular transformed called DN, and it specifies the type of broadcast that should be triggered (and its customization, if allowed), and designates whether the call is recorded.
There are two ways of configuring Cisco Unified Communications Manager for use with CallAware: Computer Telephony Integration (CTI) and/or External Call Control (ECC). You only need to work with routing requests if you have configured Cisco Unified CM to use ECC. If you want to use call redirects, go to Manage Call Redirects.
The following routing requests are configured:
| CallAware Routing Requests | |||||||||||||||||||||
| |||||||||||||||||||||
4.1.1.3 Locations
CallAware locations allow you to add geographical or situational details to aid in identifying the whereabouts of a phone that triggered a CallAware broadcast, e.g. Madison Office or Reception Desk.
A location can identify a single phone or multiple phones, e.g. the Reception Desk's phone or all of the Madison office's phones, and the number of phones affects your location's configuration:
- A single-phone location consists of a description and an IPv4 address.
- Multiple-phone locations consist of a description, an IPv4 subnet, and CIDR notation.
The following CallAware locations are configured:
4.1.1.4 Configuration
After you've configured CallAware’s Cisco Unified Communications Manager environment, you’ll need to configure its communication with Cisco Unified CM, set the amount of time for which CallAware will retain call history, and set your default location.
| Configuration | |
| CallAware Configuration | |
| Call History Retention Period (days) | |
| Default Location | |
| CallAware CUCM Configuration | |
| Application User | |
| CUCM IP Address Location | |
| CUCM Cluster Role | |
4.1.2 DialCast
DialCasts allow you to dial a SIP number to trigger an InformaCast broadcast. This SIP number is matched with a configured dialing pattern that also determines the InformaCast message to be sent and the recipient groups to receive it. Once you have dialing configurations set up, you can also selectively exempt some/many of them from your global settings through phone exceptions.
In this section you will find:
- Dialing Configurations
- Phone Exceptions
4.1.2.1 Dialing Configurations
DialCast Dialing Configurations define the SIP dialing patterns that trigger automated InformaCast broadcasts. Each configuration maps a specific dialed number or number pattern to an InformaCast message and recipient groups, enabling users to initiate pre-configured notifications by simply dialing a designated extension from any SIP-enabled phone.
| Groups | |||||||||||||||||
| |||||||||||||||||
4.1.2.2 Phone Exceptions
Phone exceptions selectively exempt some/many of them from your DialCasts settings.
The following Phone exceptions are configured:
| Groups | |||||||||||
| |||||||||||
4.1.3 Inbound CAP
Inbound CAP (Common Alerting Protocol) allows you to trigger broadcasts when CAP alerts that match rules you define are sent by data sources you configure. InformaCast monitors your configured data sources, e.g. CAP feeds from public safety organizations. When these organizations send a CAP alert that matches a data source being monitored, InformaCast "sees" the alert and compares its information with the criteria you have configured within your inbound CAP message rules, e.g. the text CAP alerts must contain along with their language, location, and category. If the CAP alert matches your rule's criteria, the message assigned to your message rule is sent out to its recipients.
In this section you will find:
- Message Rules
- Data Sources
- Configuration and Inbound CAP Message Service
4.1.3.1 Message Rules
Message Rules pull in every single current CAP alert they can find. It is unlikely that you want to create an InformaCast broadcast for every CAP alert received; instead, you can create message rules including filters to define the CAP alerts InformaCast will rebroadcast.
The following Message Rules are configured:
| Message Rules | |||||||||||||||||||
| |||||||||||||||||||
4.1.3.2 Data Sources
Data sources allow you to define the RSS/ATOM feeds you want Inbound CAP to poll for CAP alerts. Every 60 seconds, each data source will be polled to see if there are any new alerts that must be processed, and you can configure Inbound CAP to poll as many feeds as you like. If the same CAP alert is received from multiple data sources, it will only become part of an InformaCast broadcast once to avoid duplicating broadcasts.
The following Data sources are configured:
4.1.3.3 Configuration
The areas from which you receive CAP messages can be defined by latitude/longitude coordinates on the globe. Geographic definitions are a way for you to define this area of interest in Inbound CAP.
Inbound CAP polls data sources to see if there are new alert messages that need to be processed. This is referred to as a polling method for getting CAP alerts into InformaCast. Another method, using the Inbound CAP Message Service (ICMS), is referred to as a push method of getting CAP alerts into InformaCast. If you have a device that generates CAP messages and can POST them via HTTPS, you can start the ICMS and listen for messages that other devices push to it.
| Inbound CAP > Configuration | |
| Geographic Definition | |
| Language | |
| Default Language | |
| Language | |
| Inbound CAP Message Service (ICMS) | |
| Username | |
| Status | |
| Port | |
4.1.4 Inbound Email
Inbound Email events send a broadcast when an email is received by a monitored email account.
In this section you will find:
- Email Accounts
- Inbound Email Broadcasts
4.1.4.1 Email Accounts
Inbound Email allows you to initiate InformaCast broadcasts upon receipt of an email from a monitored email account. Once you have an email account set up, you can configure email broadcasts, which contain rules for how emails sent to your account should be filtered, the message to send, and the recipient groups to receive the broadcast.
The following Inbound Email accounts are configured:
| Email Accounts | |||||||||||||||||||||||||
| |||||||||||||||||||||||||
4.1.4.2 Email Broadcasts
Inbound Email broadcasts consist of the InformaCast message to send when new emails arrive to the configured Inbound Email account, the Subject, From address, and Body filters (optional) that narrow down the emails that would trigger an InformaCast broadcast, the treatment of the InformaCast message’s or inbound email’s text and audio components, and the recipient group(s) that will receive the broadcast.
Inbound Email supports the following message types: Text, Text and Pre-recorded Audio, and Pre-recorded Audio.
The following Inbound Email broadcasts are configured:
| Email Broadcasts | |||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
4.1.5 Inbound Email
RSS feed configuration includes linking an RSS feed with a message and recipient group(s). Once linked, broadcasts will be triggered whenever new feed information becomes available.
In this section you will find:
- Settings
- RSS Feeds
4.1.5.1 Settings
The following Inbound RSS settings are configured:
| Inbound RSS > Settings | |
| Debug Traces Enabled | |
| Poll Interval (minutes) | |
4.1.5.2 RSS Feeds
RSS feed configuration includes linking an RSS feed with a message and recipient group(s). Once linked, broadcasts will be triggered whenever new feed information becomes available.
Inbound RSS supports the following message types: Pre-recorded Audio, Text, and Text and Pre-recorded Audio; however, these messages must "customizable," i.e. have their Allow users to customize the message at send time checkbox selected on the Create/Edit Message page. Messages that aren't customizable are not available for selection when adding/editing an RSS feed.
The following RSS feeds are configured:
| RSS Feeds | |||||||||||
| |||||||||||
| |||||||||||
4.1.6 M2M Contact Closures
Machine-to-Machine (M2M) allows you to send InformaCast broadcasts when a contact closure has been triggered or trigger a contact closure when a specific broadcast has been sent. M2M uses a device, such as a contact closure, to capture an event, e.g. a doorbell ringing as input port will allow you to trigger InformaCast broadcasts when they’re activated, and output ports can be added as recipients to InformaCast’s messages so that when they’re sent as broadcasts, the contact closure’s output port(s) is activated.
The following M2M input and output ports are configured:
| M2M Contact Closures | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
4.1.7 Night Bell
Night Bell monitors specific directory numbers (DNs), and when a call comes in on a monitored DN, Night Bell triggers a broadcast that will repeat until the call is answered or the DN returns to an idle state. As long as a call is ringing, InformaCast is broadcasting.
For example, a call comes in to your central reception desk late at night, but your attendant is away, possibly checking the security of the building. Since the DN at the central reception desk has been configured with Night Bell, an InformaCast broadcast of a tone begins repeating through your overhead IP speakers. The attendant hears the tone, returns to the desk to answer the call or remotely dials into that DN, and the broadcast ceases.
In this section you will find:
- Night Bell Triggers
- Configuration
4.1.7.1 Triggers
Night Bell triggers are comprised of CTI ports, InformaCast messages, and recipient groups. When a call comes in on a monitored DN, the trigger contains all the necessary information for a broadcast.
The following Night Bell triggers are configured:
| Night Bell Triggers | |||||||||||||||||||
| |||||||||||||||||||
4.1.7.2 Configuration
The Configuration area of the Night Bell page allows you to set up Night Bell's connection to Cisco Unified Communications Manager and enter a value for the amount of time (in minutes) that a broadcast should persist if a call isn’t answered.
| Night Bell > Configuration | |
| Default Max Broadcast Duration (minutes) | |
4.1.8 Park and Page
Park and Page allows you to park calls and send out InformaCast broadcasts to announce their arrival to interested parties. Using destinations and triggers, you combine a CTI port and recipient group, i.e. a destination, with a DN tied to a message, i.e. a trigger. With a destination comprised of the Cisco IP phones for Unified CM and/or IP speakers in the Electronics department and a trigger's message that says, “Electronics, you have a call on XXXX,” when a customer calls you, listens to your Interactive Voice Response (IVR) menu, and selects the Electronics department, Park and Page will park their call and broadcast the message you've configured. Someone in the Electronics department can then dial the number announced in the broadcast and talk to the caller. You can also control what happens when a call isn’t answered and the amount of time an announcement will repeat itself.
In this section you will find:
- Park and Page Destinations
- Park and Page Triggers
- Configuration
4.1.8.1 Destinations
Park and Page destinations are comprised of CTI ports that are linked to recipient groups; they tell triggers where to send a broadcast. You must create destinations before you can create triggers.
The following Park and Page destinations are configured:
| Destinations | |
| License Status | |
4.1.8.2 Triggers
Park and Page observes route points and directs the calls these observed route points receive to the DNs you've established. You will want to create one route point DN for each unique trigger that you establish in Park and Page.
The following Park and Page triggers are configured:
| Triggers | |
| License Status | |
4.1.8.3 Configuration
Setting Park and Page's configuration parameters includes establishing its connection to Cisco Unified Communications Manager and entering a few default values for where calls will be routed in case of an error, how long to wait for a call to be answered before announcing it again, how long to wait before canceling an unanswered call, etc.
| Park and Page > Configuration | |
| License Status | |
4.1.9 Bells
Bells allow you to send patterns of scheduled messages (usually brief tones) to Cisco IP phones for Unified CM and IP speakers.
Bells consist of:
- Ring tone. A message that can be used with bells. Messages can only be used with bells when they have their Ring Tone checkbox selected and a message type of Pre-recorded Audio or Text and Pre-recorded Audio. InformaCast provides you with a small selection of ring tones, and you can create more as needed.
- Ring list. A series of ring tones to be played at specific times of day and the set of recipient groups that will play each tone.
- Bell schedule. The ring list that's used each day, which is mapped to a repeating weekly pattern on the calendar.
- Exception. An alternative ring list that plays on a particular date or range of dates that overrides the normal weekly pattern, i.e. bell schedule.
In this section you will find:
- Bells Schedules
- Bells Ring List
4.1.9.1 Schedules
Bell schedule define the ring list that is used each day, which is mapped to a repeating weekly pattern on the calendar.
The following Bell schedules are configured:
4.1.9.2 Ring List
Ring lists are a series of ring tones to be played at specific times of day and the set of recipient groups that will play each tone.
The following Ring lists are configured:
4.2 Schedules
Broadcast Schedules enable the automated delivery of InformaCast messages at specific dates and times, supporting one-time future broadcasts and recurring scheduled announcements. Schedules can be configured with start times, end times, recurrence patterns (daily, weekly, monthly), and associated messages and recipient groups for automated communication delivery without manual intervention.
Scheduled broadcasts are useful for routine announcements such as daily reminders, weekend notifications, holiday messages, maintenance alerts, and any time-based communication that needs to occur automatically at predetermined intervals.
In this section you will find:
- Islamic Prayer Times
- M2M Schedules
- Scheduled Broadcasts
4.2.1 Islamic Prayer Times
Islamic Prayer Times calculations allow you to determine the call-to-prayer times for locations around the world and create scheduled broadcasts that correspond to those times. Once you have selected locations based on latitude and longitude and time zone, you can select your calculation method, make any necessary time adjustments, and assign the recipients and messages that will receive the call-to-prayer scheduled broadcasts.
The following Islamic Prayer Times are configured:
4.2.2 M2M Schedules
Machine-to-Machine (M2M) uses a device, such as a contact closure, to capture an event, e.g. a doorbell ringing, which is relayed through a network to an application, such as InformaCast
Schedules are an optional feature that allow you to set times when a contact closure is considered active. Active contact closures will trigger/be triggered by broadcasts; inactive contact closures will not, e.g. a weekend schedule would trigger a strobe light when the front doorbell is pressed, while pressing that doorbell during the work week would not trigger the strobe light.
The following M2M Schedules are configured:
4.2.3 Scheduled Broadcasts
Scheduled broadcasts allow you to send a message at a prearranged time in the future, either once or on a recurring basis.
Tip: Bells offer a more sophisticated scheduling process with more options and finer-grained control.
The following Scheduled broadcasts are configured:
5 Recipients
The Recipients section manages all destination endpoints and contact information for InformaCast broadcasts. This includes organizational groupings, individual endpoints across multiple communication channels, and hardware devices that can receive notifications. Recipients can be phones, speakers, desktop computers, email addresses, mobile devices, social media accounts, and external systems.
This section contains:
- Groups - Recipient Groups organize devices and contacts into logical collections, with customizable tags for filtering and targeted message delivery
- Endpoints - Individual contact points including Conference Calls, InformaCast Mobile users, Outbound Email recipients, Quick URL webhooks, School Messenger integration, Twitter accounts, WordPress sites, and Script endpoints
- Hardware - Physical devices including IP Speakers with network parameters and statistics, Desktop Notifier settings, SIP Speaker Parameters, and Legacy Paging Interface (LPI) configurations with paging devices and SIP server groups
5.1 Groups
Recipient Groups organize phones, speakers, contacts, and other endpoints into logical collections for targeted message delivery. Groups can contain mixed device types and support hierarchical structures with tags for advanced filtering and dynamic recipient selection based on location, department, or other organizational criteria.
This section contains:
- Recipients Groups - Configured groups with member devices and contacts
- Tags - Categorization labels for organizing and filtering recipient groups
5.1.1 Recipient Groups
Recipient groups and exclusionary recipient groups allow you to organize your recipients into groups that will either receive the broadcasts sent to them (recipient groups) or never receive broadcasts (exclusionary recipient groups).
By default, InformaCast initially creates an 'All Recipients' group, which contains all the recipients that can be discovered. However, you may find it helpful to send to smaller groups of recipients (or exclude some recipients from ever receiving broadcasts).
The following Recipient groups are configured:
| Recipient Groups | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||
5.1.2 Tags
Recipient group tags allow you finer control over the display results for recipient groups throughout InformaCast's recipient-specific features. For example, enter a tag's name in the Recipient Groups dropdown menu of a dialing configuration, scheduled broadcast, CallAware call redirect, or ring list entry to only see the recipient groups assigned that tag.
The following Recipient group tags are configured:
| Recipients > Tags | |
5.2 Endpoints
Endpoints define individual contact points and integration channels for message delivery beyond traditional phone and speaker hardware. These include conference call systems, mobile applications, email distribution, web services, social media platforms, and custom script integrations that extend InformaCast's notification reach.
Available endpoint types include:
- Conference Calls - Dynamic conference bridge configurations with contact lists for automated call-out notifications
- Contacts - Individual contact records for Conference Call participant management
- Groups - Conference Call group configurations
- General Settings - Global Conference Call parameters
- Configuration - Conference Call system settings
- InformaCast Mobile - Mobile application user registrations and device tokens
- Outbound Email - Email recipient configurations and SMTP settings
- Quick URL - Webhook endpoints for HTTP/HTTPS notification delivery to external systems
- School Messenger - Integration settings for School Messenger notification service
- Wordpress - WordPress site integration for automated blog post notifications
- Script - Custom script endpoints for programmatic notification handling
5.2.1 Conference Call
Conference Call recipients allow you to group users’ Cisco IP phones for Unified CM and pull those phones into a conference call session when the conference call group is assigned as a recipient to an InformaCast broadcast. You can also dial a directory number (DN) associated with that particular conference call group and launch a conference call session.
In this section you will find:
- Contacts
- Groups
- General Settings
- Configuration
5.2.1.1 Contacts
Conference Call contacts are the individuals with Cisco IP phones for Unified CM who could be the potential recipients of a conference call broadcast.
The following Conference Call contacts are configured:
| Contacts | ||||
5.2.1.2 Groups
Once you have added Conference Call contacts, you can place these contacts into Conference Call groups, optionally assign them a dial-in DN (which allows them to either dial into an existing conference call session once it’s started or kick off a new conference call session by dialing it), and then assign these groups as recipients to InformaCast broadcasts.
The following Conference Call groups are configured:
| Conference Call > Groups | |||||||||||||||||
| |||||||||||||||||
5.2.1.3 General Settings
The following Conference Call Setting are configured:
| Conference Call - General Settings | |
| General Settings | |
| No Answer Timeout (sec) | |
| Transfer CTI Debug | |
| Conference CTI Debug | |
5.2.1.4 Configuration
Setting Conference Call configuration parameters includes establishing a connection to Cisco Unified Communications Manager, determining whether the InformaCast-provided IVR audio is sufficient or uploading new audio, setting the length of time InformaCast will let a phone ring before hanging up the call, and enabling several debug logging settings (optional).
The following Conference Call configuration is configured:
| Configuration | ||
5.2.2 Outbound Email
Send a broadcast’s contents to an email account. Outbound Email settings configures a Simple Mail Transport Protocol (SMTP) server. It can then be used by the 'Outbound Email references' to send email.
In this section you will find:
- Outbound Email Settings (i.e. Email server configuration)
- Outbound Email references
5.2.2.1 Settings
Outbound Email settings configures a Simple Mail Transport Protocol (SMTP) server. It can then be used by the 'Outbound Email references' to send email.
Caution: If an email account is used in multiple InformaCast recipients and/or event sources, it increases the potential for inadvertent InformaCast broadcasts. Please be aware of the accounts that are configured in each recipient.
The following Simple Mail Transport Protocol (SMTP) server is configured:
| Outbound Email Configuration | |
| SMTP Server | |
| SMTP Server Port | |
| Username | |
| Authentication Method | |
| From Address | |
| From Name | |
| Reply To Address | |
| Message Footer | |
5.2.2.2 Email References
Outbound Email recipients allow you to send the contents of a message's Short Text and Long Text fields, and optionally its audio content, in an email to listed email addresses. Once you have created Outbound Email references, which contain the email addresses that will receive InformaCast's broadcast content, InformaCast will treat them as new recipients that can be assigned to a recipient group just as you would a Cisco IP phone for Unified CM or an IP speaker.
The following Outbound Email recipients are configured:
| Email References | |||||||||||||||
| |||||||||||||||
| |||||||||||||||
5.2.3 Quick URL
Quick URL enables InformaCast to send broadcast notifications to external web services and systems through HTTP/HTTPS webhook endpoints. This integration allows message text content to be delivered to third-party applications, monitoring systems, paging services, and other network resources by posting Short Text and Long Text fields to configured URLs, extending InformaCast's notification reach beyond traditional devices.
This section contains:
- URL Devices - Configured webhook endpoints that receive broadcast text content via HTTP/HTTPS POST requests
5.2.3.1 URL Devices
URL Devices define individual webhook endpoints that receive InformaCast broadcast text through HTTP/HTTPS POST requests. Each URL device specifies a destination web address, authentication credentials if required, and can be assigned to recipient groups just like physical devices. URL devices enable integration with external notification services, paging systems, digital signage, facility management platforms, and custom applications that consume InformaCast message content.
The following Quick URL Recipients are configured:
| URL Devices | |||||||||||||||||
| |||||||||||||||||
5.2.4 School Messenger
The SchoolMessenger plugin allows you to include SchoolMessenger jobs as eligible recipients of an InformaCast broadcast. Once you have an active account on the SchoolMessenger hosted server, you can configure InformaCast to treat SchoolMessenger jobs as new recipients that can be assigned to a recipient group just as you would a phone or a speaker.
SchoolMessenger recipients are not included in InformaCast by default; they must be explicitly included in your license's functionality.
In this section you will find:
- SchoolMessenger Settings (i.e. SchoolMessenger server configuration)
- SchoolMessenger recipients
5.2.4.1 Settings
You must configure a connection between InformaCast and your hosted SchoolMessenger server so that InformaCast may access your SchoolMessenger jobs.
The following are the SchoolMessenger server configuration settings:
5.2.4.2 Jobs
SchoolMessenger Jobs define notification templates synchronized with the SchoolMessenger cloud service for delivering broadcasts through their multi-channel notification platform. Each job represents a pre-configured notification workflow in SchoolMessenger that can be triggered from InformaCast, specifying whether the job is available to InformaCast Mobile app users and whether message content can be overridden when initiating the notification.
5.2.5 Wordpress
WordPress recipients allow you to send a message's text components from InformaCast to WordPress instances (wordpress.org). Once you have created a WordPress instance, you can configure InformaCast to treat the destination WordPress instance as a new recipient, called a WordPress reference in InformaCast, that can be assigned to a recipient group just as you would a Cisco IP phone for Unified CM or an IP speaker.
The following WordPress recipients are configured:
| Wordpress References | |||||||||||
| |||||||||||
5.2.6 Script
Script recipients allow Java and JavaScript programmers to build a custom integration by creating code that can participate at various phases of an InformaCast broadcast and attaching it as a script to an InformaCast broadcast. The integration can be deep or simple depending on how much code is written and how much of the exposed interface is used.
A typical task for a Script recipient is to integrate or communicate with other systems, and those systems can be internal to your network or external. Such systems usually have a REST or HTTP interface that allows JavaScript to perform HTTP GET and HTTP POST requests.
The following Script recipients are configured:
| Scripts | |||||
| |||||
| |||||
5.3 Hardware
The Hardware section manages physical devices that receive InformaCast broadcasts including IP speakers, desktop computers running InformaCast Desktop Notifier, and legacy analog paging systems integrated through SIP gateways. These devices provide on-premises audio and visual notification delivery across facilities.
This section contains:
- Speakers - IP speaker devices with network parameters, registration status, and Desktop Notifier configurations
- Legacy Paging Interface - SIP-to-analog gateway integration for connecting existing overhead paging infrastructure
5.3.1 Speakers
IP Speakers and Desktop Notifiers are network-connected devices that receive audio broadcasts and text notifications from InformaCast. IP speakers provide overhead paging capabilities with various audio quality levels and display features, while Desktop Notifier runs on Windows and Mac computers to deliver pop-up notifications with audio, text, and images directly to user desktops.
This section contains:
- IP Speakers - Individual speaker configurations showing registration status, MAC addresses, IP addresses, volume settings, and device capabilities
- Network Speaker Parameters - Global parameters including SLP configuration, auto-registration settings, session timeouts, and keepalive intervals
- SIP Speaker Parameters - SIP telephony settings for speakers including transport protocols, registration intervals, DNS SRV configuration, and line-side connection parameters
- Desktop Notifier Parameters - Configuration for desktop application including menu options (clear, exit, start/stop) and custom logo settings
- Speakers Statistics - Summary counts of configured, registered, new, expired, and not-registered speakers and desktop notifiers
5.3.1.1 Speakers
IP Speakers are network-connected devices that receive and play audio broadcasts from InformaCast, with many models also supporting text display capabilities. Broadcasts activate speakers via HTTP and deliver audio content through multicast RTP streams, enabling simultaneous message delivery to multiple devices with minimal network overhead.
InformaCast supports multiple speaker types including hardware IP speakers (network-attached loudspeakers), SIP speakers for full-duplex intercom calls, Legacy Paging Interface (LPI) zones for analog paging integration, and InformaCast Desktop Notifier instances running on computers. Speakers obtain configuration from the InformaCastSpeaker.cfg file which defines server location, registration intervals, volume settings, and remote logging parameters.
This section displays individual speaker configurations including registration status, MAC addresses, IP addresses, volume levels, dial codes, scroll speed adjustments, SIP intercom settings, and device capabilities such as display support, recording ability, and message response features.
The following IP speakers are configured:
| Speakers | |||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
5.3.1.2 Network Speaker Parameters
Network Speaker Parameters configure global settings for IP speaker registration and communication including SLP (Service Location Protocol) configuration, auto-registration behavior, session timeouts, keepalive intervals, default volume levels, and SNMP community names for network device management.
| Speaker Parameters | |
| Automatically Add Hardware IP Speakers | |
| Speaker Default Volume | |
| Automatically Add IDN Instances and LPI Plugin Paging Zones | |
| IDN/LPI Paging Zone Default Volume | |
| Automatically Remove Unregistered IDN Instances (days) | |
| Registration Interval (seconds) | |
5.3.1.3 SIP Speaker Parameters
SIP Speaker Parameters define global SIP telephony settings for IP speakers including transport protocols, registration intervals, call ring time, DNS SRV configuration, and line-side connection parameters for UCaaS provider integration. These settings control how SIP-enabled speakers register with and communicate through the telephony infrastructure.
| SIP Speaker Parameters | |
| Require Numeric SIP Speaker DN | |
| Configure with DNS SRV | |
| Telephony Providers | |
| Transport Protocol | |
| OPTIONS Ping Interval (seconds) | |
| Registration Interval (seconds) | |
| Call Ring Time (seconds) | |
5.3.1.4 Desktop Notifier Parameters
Desktop Notifier Parameters configure the InformaCast Desktop Notifier (IDN) application behavior on Windows and Mac computers. Settings control which menu options are available to end users including the ability to clear messages, exit the application, or start/stop the service, and allow customization of the application logo displayed on compatible devices.
| InformaCast Desktop Notifier Parameters | |
| Clear Menu Option | |
| Exit Menu Option | |
| Start/Stop Menu Option | |
| Logo | |
5.3.1.5 Speakers Statistics
As long as DHCP and DNS SRV records or multicast and SLP are correctly configured on your network, your IP speakers and InformaCast will establish communication. Once communication is established, all IP speaker types register directly with InformaCast.
Registration is only part of the process, however. In order for IP speakers to be available for inclusion in recipient groups and eligible for receipt of InformaCast broadcasts, they have to be added. You may also want to configure them with more detailed information. Some definitions of IP speaker states will help you with your configuration:
- Registered. These are IP speakers with which InformaCast has established communication.
- Added. If IP speakers are configured to be automatically added via the Network Speaker Parameters area, they will appear in the table on the Speakers page as soon as they establish communication with InformaCast. These are considered added, but until you assign them a name, description, dial code (optional), etc. on the Edit Speaker page, they are not yet configured.
- Unadded. If IP speakers are not configured to be automatically added.Unadded, registered IP speakers cannot be included in recipient groups and will not receive broadcasts.
- Configured. These are IP speakers that have registered with InformaCast.
- Unconfigured. These are registered IP speakers that have not yet been assigned a name, description, dial code (optional), etc.
- Unregistered. InformaCast had been able to communicate with these added and previously registered IP speakers, but can’t anymore.
| Speakers Statistics | |
| IP Speakers | |
| Registered | |
| Not Registered | |
| New | |
| Expired | |
| Desktop Notifier | |
| Registered | |
| Not Registered | |
| New | |
| Expired | |
5.3.2 Legacy Paging
The Legacy Paging Interface (LPI) plugin enables integration with existing analog overhead paging systems and zone controllers by converting InformaCast SIP calls to analog audio signals. This allows organizations to leverage their installed paging infrastructure while gaining InformaCast's advanced notification capabilities including scheduled announcements, emergency alerts, and automated triggers.
This section contains:
- Paging Devices - Individual paging gateway configurations with SIP server groups, user credentials, DTMF settings, and associated paging zones
- SIP Server Groups - Collections of SIP servers used by paging devices with hierarchical or round-robin distribution schemes
- Configuration - Global LPI settings including test tone configuration, TCP timeouts, MAC address prefixes, and transport protocols
5.3.2.1 Paging Devices
A paging device is a physical unit that allows broadcasts via one or several groups of loudspeakers that are collected into paging zones. Paging zones are groups of loudspeakers to which a paging device provides access. InformaCast recognizes each paging zone as an IP speaker.
A DTMF tone (or code) is assigned to each paging zone. When InformaCast sends a broadcast to one or more of the LPI’s paging zones, the LPI will place a call with the paging device, dial the DTMF code for its zones, and broadcast to them. Some types of paging devices allow the combining of paging zones so that a single DTMF tone can be used for accessing several zones at once.
The following paging devices are configured:
| Paging Devices | |||||||||||||||||||||||||
| |||||||||||||||||||||||||
5.3.2.2 SIP Server Groups
During a broadcast, the LPI makes a call to a SIP server in order to reach a paging device. To facilitate failover to another SIP server if the main server is unavailable, the LPI uses SIP server groups that are comprised of one or more SIP servers.
You’ll need to add one SIP server group with at least one SIP server in order for the LPI to work, and two SIP servers if you’d like failover to occur between them.
The following SIP server groups are configured:
| SIP Server Groups | |||||||||||||||||
| |||||||||||||||||
5.3.2.3 Configuration
The LPI’s Configuration area allows you to modify the parameters that affect its behavior. All of the parameters have default values and do not need to be changed, but you may want to tweak them based on your specific needs.
The following Legacy Paging Interfac settings are configured:
| Legacy Paging Interface > Config | |
| Use Custom Test Tone | |
| Request Wait Period (seconds) | |
| TCP Connection Timeout (ms) | |
| MAC Address Prefix (6 digits) | |
| SIP Transport Protocol | |
| SIP OPTIONS Ping Interval (seconds) | |
6 System Administration
System Administration provides comprehensive configuration and management of InformaCast's core infrastructure including telephony integration, SIP connectivity, user access control, and platform settings. These settings control how InformaCast connects to Cisco Unified Communications Manager, manages SIP-based communication, authenticates users, and configures system-wide operational parameters.
This section contains:
- Telephony - Cisco Unified CM cluster integration, phone updates, CTI certificates, and external call control configuration
- SIP - Session Initiation Protocol settings including access configuration, accounts, certificates, security, speaker parameters, stack settings, credentials, registrations, DNS SRV records, and server groups
- User Management - User accounts, groups, roles, and session timeout configuration for InformaCast access control
- General Configuration - System-wide settings including broadcast parameters, licensing, SLP configuration, network parameters, and LDAP integration
6.1 Telephony
The Telephony section manages integration with Cisco Unified Communications Manager (CUCM) clusters for phone-based notification delivery. This includes CTI (Computer Telephony Integration) configuration, phone device synchronization, certificate management for secure connections, and external call control profile settings that enable InformaCast to monitor and control Cisco phones for emergency broadcasts and paging.
This section contains:
- Cisco Unified CM Clusters - CUCM cluster configurations with provider settings, IP addresses, credentials, JTAPI parameters, and secure connection options
- Phone Updates - Scheduled rebuild and refresh operations for synchronizing phone lists from CUCM, including intervals and last execution timestamps
- CUCM External Call Control - External Call Control Profile settings for web service URLs and keepalive monitoring
6.1.1 Cisco Unified CM Cluster
List of Cisco Unified Communications Manager clusters whose phones will receive InformaCast broadcasts. One Cisco Unified CM cluster must be your primary cluster.
| CUCM Clusters | |||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||
6.1.2 CUCM Phone Updates
Phone Updates manages the synchronization of Cisco phone device information from Unified Communications Manager into InformaCast. The Rebuild operation performs a complete phone list reconstruction from CUCM using AXL queries, while the Refresh operation updates existing phone data. This section displays the schedule configuration, last attempted and successful execution timestamps, phone retrieval counts, and refresh intervals for maintaining accurate phone inventory.
| Phone Updates | |
| Build List of Registered Phones | |
| Description | |
| Note | |
| Hour (0-23) | |
| Minute | |
| Second | |
| Month | |
| Day | |
| Week Day | |
| Refresh List of Registered Phones | |
| Description | |
| Note | |
| Refresh Interval (minutes) | |
6.1.3 CUCM External Call Control
CUCM External Call Control displays the External Call Control Profile configuration on Cisco Unified Communications Manager that enables CUCM to communicate with InformaCast for emergency notification features. This section shows the primary and secondary web service URLs configured in CUCM's External Call Control Profile, secure HTTPS URLs if configured, and the last keepalive timestamp indicating the most recent successful health check from CUCM to InformaCast.
| CUCM External Call Control | |
| Description | |
| Web Service URLs | |
| Primary Web Service | |
| Secure Primary Web Service | |
| Keep-Alive Status | |
| Last Keep-Alive Received | |
6.1.4 CTI Certificates
SIP Certificates manages SSL/TLS certificates used for secure SIP signaling (SIPS) and encrypted media streams. This section displays imported certificates with their aliases, subject common names, and full certificate contents in PEM format. Certificates enable secure SIP connections using TLS transport protocol and SRTP for encrypted audio, ensuring confidential communication between InformaCast and external SIP providers or telephony systems.
6.1.5 SIP
The Telephony section manages integration with Cisco Unified Communications Manager (CUCM) clusters for phone-based notification delivery. This includes CTI (Computer Telephony Integration) configuration, phone device synchronization, certificate management for secure connections, and external call control profile settings that enable InformaCast to monitor and control Cisco phones for emergency broadcasts and paging.
This section contains:
- Cisco Unified CM Clusters - CUCM cluster configurations with provider settings, IP addresses, credentials, JTAPI parameters, and secure connection options
- Phone Updates - Scheduled rebuild and refresh operations for synchronizing phone lists from CUCM, including intervals and last execution timestamps
- CUCM External Call Control - External Call Control Profile settings for web service URLs and keepalive monitoring
6.1.5.1 Access
This section shows whether SIP access is allowed or denied, and a list of exceptions that can be configured by subnet or host.
| SIP Access | |||||
| Incoming SIP calls | |||||
| Subnet Exceptions |
| ||||
6.1.5.2 Accounts
SIP Accounts configure InformaCast's registration with external SIP providers or PBX systems for outbound SIP connectivity. Each account defines the SIP user credentials, host address, outbound proxy servers, transport protocol (UDP/TCP/TLS), and optional realm authentication settings that enable InformaCast to register as a SIP endpoint and establish secure connections for features like DialCast and Legacy Paging Interface.
| SIP Accounts | |||||||||||||||||||||
| |||||||||||||||||||||
6.1.5.3 Call Security
SIP Security configures authentication and access control policies for incoming SIP connections to InformaCast. This section defines security settings including SIP realm authentication requirements, allowed IP address ranges for SIP traffic, digest authentication challenges, and policies that prevent unauthorized SIP devices or systems from connecting to InformaCast services.
| SIP Call Security | |
| Secure Signaling Required | |
| Secure RTP Allowed | |
| Authenticate Incoming Requests | |
| Realm | |
| Authentication Username | |
| Nonce Duration | |
6.1.5.4 SIP Certificates
Certificates used when establishing secure SIP connections between InformaCast and other SIP devices. Used in conjunction with secure signalling, enables the exchange of RTP packets and DTMF tones in a secure fashion by using Secure Real-time Transport Protocol (SRTP).
| SIP Certificates | ||
SerialNumber: 444626923492311221341950456022583447956727380926 IssuerDN: EMAILADDRESS=support@uplinx.com, CN=ic158.lab.uplinx.com, OU=test, O=Test, L=test, ST=test, C=AD Start Date: Thu Dec 04 12:08:53 CST 2025 Final Date: Tue Dec 03 12:08:53 CST 2030 SubjectDN: EMAILADDRESS=support@uplinx.com, CN=ic158.lab.uplinx.com, OU=test, O=Test, L=test, ST=test, C=AD Public Key: RSA Public Key [99:66:dc:7c:3d:ed:09:89:55:4f:01:4b:6c:af:69:29:48:22:49:ca],[56:66:d1:a4] modulus: d64f969ab66d54b71a00ea2b0236966333b510f689b428551b966a1b857c7bb1f1649d062b843d0b983f0f663d0c9b302df13e219a7eb3a49c12df842545cfb33f1fc5f2ddcd8bac7e58345a4 bcd5ce0f13051eb5a607821af1c0a7ca1274a9db3c4a0437c759307d339d6f7498da3bf4b429cf5fb4b073eab5ba6e09c690606201120c2c8b321c0079eb02f884f84b51e06d5e2598a1db8cb03f9608a2fdcb8d32 1290fe2b5d717643d0a2cf813502d892e7b3b1121c50c6114bec5fbbcbeab39fba45e66093bd2cfa854f4b3b1ad4a16511acc3c2f2240e21abca57e226435d80836fa0c357d5b81eefa129fc8512ab5c4940d0009f 21f77f2d007de38ebf1 public exponent: 10001 Signature Algorithm: SHA256WITHRSA Signature: d4d905fac5905cfffcbf4442a90fda58f5d1e8b1 b49142f09e912ec793343b391a318f1d22650627 fc3cbff302ae4003aa8f95cd3a16f74d36e10402 68891319a39d47d80f9c9389586bd2f6b23d6b85 3fe9c71d54459d19df6cf7c31ad1e234a884f44e 57761ba3a6ec732512e10bdaef9d34fee4bbf4d7 b83d9614f6b33afdb140da6511cc18ddabd0ab39 a1f1354762cbd3c00055d44d265ff1e42671c078 214a0fea462ec1cfa478a784ad457e283d7666f4 3ba7d83122939cc9d010321594c6a53d0cd47259 0afa2f69a1afb34a71764c4f4dcc69952fddfd29 e1a6800130c7042148d366f35dff71d51d9a43b6 643c9aa60ca4611d02c9f689044c7647 Extensions: critical(false) 2.5.29.37 value = Sequence ObjectIdentifier(1.3.6.1.5.5.7.3.1) ObjectIdentifier(1.3.6.1.5.5.7.3.2) critical(false) 2.5.29.14 value = DER Octet String[20] critical(false) KeyUsage: 0xb4 critical(true) BasicConstraints: isCa(false) critical(false) 2.5.29.17 value = Sequence Tagged [2] IMPLICIT DER Octet String[20] Tagged [2] IMPLICIT DER Octet String[10] | ||
6.1.5.5 SIP Speaker Parameters
SIP Speaker Parameters define global SIP telephony settings for IP speakers including transport protocols, registration intervals, call ring time, DNS SRV configuration, and line-side connection parameters for UCaaS provider integration. These settings control how SIP-enabled speakers register with and communicate through the telephony infrastructure.
| SIP Speaker Parameters | |
| Require Numeric SIP Speaker DN | |
| Use DNS SRV | |
| Telephony Providers (IPv4/DNS) | |
| Options Ping Interval (seconds) | |
| Registration Interval (seconds) | |
| Call Ring Time (seconds) | |
6.1.5.6 Stack
Various low/level parameters for the SIP stack. InformaCast uses the National Institute of Standards and Technology (NIST) SIP stack to provide it with basic SIP functionality. The SIP stack provides InformaCast with fundamental low-level SIP functionality such as transaction handling, dialogs, utilities for SIP headers, maintenance of SIP timers, etc.
| SIP Speaker Parameters | |
| Enable Detailed Logging | |
| Max Forwards | |
| Read Timeout | |
| Cache Client Connections | |
| Cache Server Connections | |
6.1.5.7 SIP User Credentials
SIP peers may challenge InformaCast to provide valid credentials for its SIP realm when registering or terminating a SIP call. Lack of valid credentials for a challenging realm means that requests to it will be rejected. You should enter valid credentials for each SIP realm where you expect InformaCast to be challenged.
This section is optional depending on the security of your environment.
The following SIP credentials are present:
| SIP User Credentials | |
6.1.5.8 DNS SRV Records
DNS SRV Records configure Service Location through DNS for automatic SIP server discovery. This section displays the DNS SRV records that InformaCast queries to locate SIP services, showing the service domain, priority, weight, port, and target server addresses returned by DNS lookups for SIP connectivity.
| DNS SRV Records | |||||||
| Service: _sips._tcp.test.lab.uplinx.com. | |||||||
| Service Users | |||||||
6.2 User Management
User Management controls authentication, authorization, and access to InformaCast functionality through user accounts, groups, and role-based permissions. Administrators can create internal users, integrate with LDAP directories, assign granular permissions through roles, and apply message/device filters to limit what users can access and broadcast to.
This section contains:
- Users - Individual user accounts with login credentials, assigned roles, group memberships, and access filters
- User Groups - Logical collections of users with shared role assignments and permission filters
- Roles - Permission templates defining what actions users can perform (send broadcasts, manage devices, configure system, etc.)
- Session Timeout - Automatic logout settings for inactive user sessions
6.2.1 Users
This section shows the list of users currently set up to use InformaCast. Users can be added and deleted, and roles can be set for each user.
| Users | |||||||||||||||||||||
| |||||||||||||||||||||
| |||||||||||||||||||||
6.2.2 User Groups
This section shows the list of user groups currently set up to use InformaCast. User Groups can be added and deleted, users can be added or removed from groups, and roles can be set for each group.
| Groups | |||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
6.2.3 Roles
Roles are broad, predefined sets of capabilities. For example, there could be one role that only allows a user to send messages and another role that allows a user to create, send, and cancel messages. All roles are predefined, and editing a role simply consists of adding or removing groups assigned to the role.
This section shows a list of the predefined roles. Each role shows which users or groups are assigned to it.
| Roles | |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
| |||||||||||||
6.2.4 Session Timeout
Session timeout values, which affect how often credentials must be provided when using InformaCast. These fields are system-wide; they control the session timeouts of all users and Cisco IP phones for Unified CM.
- Session Timeout: The Session Timeout page appears.
- Phone Session Timeout: This field controls when sessions between Cisco IP phones for Unified CM and InformaCast will be closed after a certain amount of inactivity. By default, this field is set to 60 seconds, i.e. one minute.
| Session Timeouts | |
| General Session Timeout (seconds) | |
| Phone Session Timeout (seconds): | |
6.3 General Configuration
General Configuration manages system-wide operational parameters that affect InformaCast's core behavior including broadcast settings, licensing information, network service discovery, platform parameters, and directory integration. These settings control how InformaCast operates at the platform level and integrates with enterprise infrastructure.
This section contains:
- System Settings - Core platform configuration including automatic restart policy and system-level operational parameters
- Broadcast Parameters - Default settings for message delivery including maximum broadcast duration and confirmation timeouts
- License - License key information, expiration dates, feature codes, and capacity limits
- SLP Parameters - Service Location Protocol configuration for IP speaker auto-discovery and service advertisement
- Network Parameters - Network interface settings, multicast configuration, and communication parameters
- LDAP - LDAP directory integration for user authentication and phone synchronization from corporate directories
6.3.1 System Settings
General Configuration manages system-wide operational parameters that affect InformaCast's core behavior including broadcast settings, licensing information, network service discovery, platform parameters, and directory integration. These settings control how InformaCast operates at the platform level and integrates with enterprise infrastructure.
This section contains:
- System Settings - Core platform configuration including automatic restart policy and system-level operational parameters
- Broadcast Parameters - Default settings for message delivery including maximum broadcast duration and confirmation timeouts
- License - License key information, expiration dates, feature codes, and capacity limits
- SLP Parameters - Service Location Protocol configuration for IP speaker auto-discovery and service advertisement
- Network Parameters - Network interface settings, multicast configuration, and communication parameters
- LDAP - LDAP directory integration for user authentication and phone synchronization from corporate directories
6.3.1.1 Backup
This section shows InformaCast system configuration parameters and includes settings for:
- Backup
- System Scripts
- System Certificates
- Pre-Login Banner
- Post-Login Banner
| System > Backup | |
| Job Description | |
| Backup functionality activated | |
| Second | |
| Minute | |
| Hour | |
6.3.1.2 System Scripts
This section shows InformaCast system configuration parameters and includes settings for:
- Backup
- System Scripts
- System Certificates
- Pre-Login Banner
- Post-Login Banner
| System > Scripting | |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
6.3.1.3 System Certificates
This section shows InformaCast system configuration parameters and includes settings for:
- Backup
- System Scripts
- System Certificates
- Pre-Login Banner
- Post-Login Banner
| Server Certificate | |
| Certificate | SerialNumber: 306321653342346578521808068316688315951452158208 IssuerDN: EMAILADDRESS=support@uplinx.com, CN=ic158.lab.uplinx.com, OU=test, O=Test, L=test, ST=test, C=AD Start Date: Thu Dec 04 12:04:56 CST 2025 Final Date: Tue Dec 03 12:04:56 CST 2030 SubjectDN: EMAILADDRESS=support@uplinx.com, CN=ic158.lab.uplinx.com, OU=test, O=Test, L=test, ST=test, C=AD Public Key: RSA Public Key [91:a9:b0:a7:1e:86:fe:c5:8c:01:65:34:df:20:d3:06:ac:d2:e3:d6],[56:66:d1:a4] modulus: b04bfed105f6c24c773ccd40d5a7357c7ddbb610b791efe0bd948f6a98d82dd3af7c6cef9cc75b6e1b2cbd8ca5dea5cc96cfbee4a345d187fa88c813e9b2720f91443bdc5cec3e85d0b7108f5 30573de6af24510b8e3a3ede453bca65a6b9ab8d71d891d205de2544082d7ccbc7464075bf7d8317628f6cdc933402a51012c7b343784645610265785fe8746981bf8da31f9d58da187c7511679b36d1d8ed507c74 6fd9f33a984522e46574f4438017f88a3eb89aceb2b1cb14af81315aa1acd8be4e55e88815eaf4d830ef8ae81b3d22799e46da53e2906aaa8f989cae6b71c95e08158f414205356f8d3c3e1fe4aa2714dae641266a 3584a861830fabf0a33 public exponent: 10001 Signature Algorithm: SHA256WITHRSA Signature: 4cc8ecce932ce0181fcc307262fa0089b9fefe66 d2db5ec293fa1430aaf8fce9a827c73bdacad296 4afb4e61b699d40bda2b682f37ebb5cd68372d32 7be9c851e72a2fd300162ddb245a18da88c1a71b 1e13783c2749f656dadd33f9995c8df6378d2045 c4b689797ff1db9e9b5f7b112fb39ec99a9c71d1 2d7ff9b6c58b2de2596cd37744569a8778adb31c 2d51544ee01a6fe15f090dbd3b045e6e0e25f9fc e5f4ceb8a4f87c763b2bde16ab2490e828884553 25d2541aac0f86af427b57e9612e13c7be9c36ac f3b63e22e2af1f0b533d73542d5adf5c3947e0e4 cd44a58092ce327a065f6ec6bd81a2dcc0c3112b f872dffd8878fba492b22ac0bf8b4b85 Extensions: critical(false) 2.5.29.37 value = Sequence ObjectIdentifier(1.3.6.1.5.5.7.3.1) ObjectIdentifier(1.3.6.1.5.5.7.3.2) critical(false) 2.5.29.14 value = DER Octet String[20] critical(false) KeyUsage: 0xb4 critical(true) BasicConstraints: isCa(false) critical(false) 2.5.29.17 value = Sequence Tagged [2] IMPLICIT DER Octet String[20] Tagged [2] IMPLICIT DER Octet String[10] |
6.3.1.4 Pre-Login Banner
This section shows InformaCast system configuration parameters and includes settings for:
- Backup
- System Scripts
- System Certificates
- Pre-Login Banner
- Post-Login Banner
| Pre-Login Banner | |
| Text | |
6.3.1.5 Post-Login Banner
This section shows InformaCast system configuration parameters and includes settings for:
- Backup
- System Scripts
- System Certificates
- Pre-Login Banner
- Post-Login Banner
| Post-Login Banner | |
| Text | |
6.3.1.6 Post-Login Banner
This section shows InformaCast system configuration parameters and includes settings for:
- Backup
- System Scripts
- System Certificates
- Pre-Login Banner
- Post-Login Banner
| Automatic Restart Policy | |
| Restart Policy | |
6.3.2 Broadcast Parameters
Set your preferences for InformaCast's handling of the audio parameters for Cisco IP phones for Unified CM, IP speakers, and InformaCast Desktop Notifier instances, as well as the phone vibration and backlight display period for Cisco IP phones, several queued ad-hoc broadcast parameters, and the DN and authentication method for canceling broadcasts through a Cisco IP phone.
| Broadcast Parameters | |
| Phone | |
| Enable Phone Vibration | |
| Vibration On Duration (milliseconds) | |
| Vibration Off Duration (milliseconds) | |
| Vibration Repetitions | |
| Backlight Display Period (minutes) | |
| Multicast | |
| Starting Multicast IP Address | |
| Ending Multicast IP Address | |
| Multicast TTL | |
| Broadcast Settings | |
| Enable Message Blending | |
| Number of Priority Levels | |
| Broadcast History Retention Period (days) | |
| Recording Limit (seconds) | |
| Live Broadcast Limit (seconds) | |
| Queued Broadcast Maximum Wait Time (seconds) | |
| Queued Broadcast Retry Interval (seconds) | |
| Queued Broadcast Send Threshold | |
| Send Silence with DialCast IVR | |
| Cancel Broadcasts Directory Number: | |
| Cancel Broadcasts Authentication Method | |
6.3.3 SLP Parameters
SLP (Service Location Protocol) parameters, which affect interactions between InformaCast and IP speakers, as well as between InformaCast and other applications.
| SLP Parameters | |
| Enable SLP | |
| Publish Configuration File Service | |
| Publish SOAP Service | |
| SLP Scope | |
| URL of Configuration File Server | |
6.3.4 Voice Menus
The general voice menu governs InformaCast's behavior during live broadcasts and audio recording. Stall tones and Go tones can be set, as well as the 'No Active Recipients' audio message. The recording Prompt audio message can be set, and the Accept key and the Cancel key configured.
| Voice > General | |
| --- Live Broadcast Parameters --- | |
| Stall Tone Audio | |
| Audio File | |
| Audio File Duration [ms] | |
| Stall Tone Interval (seconds) | |
| Go Tone Audio | |
| Audio File | |
| Audio File Duration [ms] | |
| No Active Recipients Audio | |
| Audio File | |
| Audio File Duration [ms] | |
| Recording Parameters | |
| --- Recording Prompt Audio --- | |
| Audio File | |
| Audio File Duration [ms] | |
| Accept Key | |
| Cancel Key | |
6.3.5 LDAP
Shows parameters for LDAP integration of InformaCast, including General, Authentication and Grouping parameters.
| System > LDAP Integration | |