The Alarm Station Portal streamlines the monitoring of numerous cameras, ensuring efficient and effective surveillance. Continuous manual viewing of camera feeds can consume significant data and increase the risk of missing critical events due to screen fatigue. The Alarm Station automates monitoring, reducing workload while enhancing event detection. When an event occurs, an image from the corresponding camera appears on-screen, accompanied by an audible alert. Playback begins automatically, enabling prompt responses. Alarm Station Modes: 1. Live Monitoring Mode When the Alarm Station is disarmed (indicated by an empty shield button), any displayed cameras will continue streaming without interruption. This mode functions similarly to the standard Video Portal but without inactivity timeouts, allowing indefinite streaming in live, archive, or paused states. The system can maintain streaming for extended durations, including days or months, if cameras remain on-screen. Note: Prolonged use of this mode generates high data traffic. Cameras on fixed plans may exceed traffic limits as outlined in the Fair Usage Policy, leading to automatic switching to a Pay-As-You-Go plan with charges based on actual data usage. To mitigate this, Smart Event Monitoring mode is recommended. 2. Smart Event Monitoring Mode To activate Smart Event Monitoring, the Alarm Station must be armed via the shield button in the top right corner. A red shield indicates an armed system, allowing event-based displays according to predefined rules, while an empty shield signifies disarmed status with no automatic event display. Each layout cell can be configured to display specific event types: - Any camera-side event (motion detection, line crossing, etc.) will appear. Cameras can also be manually locked in place, preventing automatic replacements. - Only display when servers detected persons. - Only display when servers recognize a car. Detected events automatically populate available layout cells based on assigned event filters. Events can be classified using a dropdown menu, creating log entries with timestamps and acknowledgment details. This functionality supports automation via webhook services for streamlined operational workflows. Alarm Station Event Handling The active layout cell remains unchanged until the event is reviewed and acknowledged. Other layout cells cycle through events based on configured filters. Event placement follows these rules: New events appear in the first available empty cell matching the filter criteria. The first occupied cell with an event becomes the primary display and is excluded from automatic rotation unless another cell is designated as primary. If all cells are occupied, new events replace older ones. Priority is given to event replacement as follows: If an event occurs on a camera already displayed, playback resets to the event’s start, an audible alert sounds, and the cell border blinks to indicate the update. If the event originates from a camera not currently displayed, the oldest event is replaced, with an audible alert and a blinking red cell border. Events that do not match the active filters remain in the Event Menu list but are not displayed on-screen. Additional Considerations Cameras can be manually opened in any layout cell, remaining fixed on-screen until manually closed, even if the cell is not set as primary. Archived footage can be reviewed, clips can be created, and object searches can be conducted on a selected camera while new events continue to be displayed. The screen configuration is fully customizable, allowing any number of manually opened or event-driven layout cells. Extended on-screen camera use can generate substantial traffic, potentially leading to additional data charges.

Missing or corrupted thumbnails typically occur when there is an issue with the camera stream, which causes the servers to require extra time for video processing and thumbnail generation. In cases where the video stream contains corrupt data, image processing may take longer than the event delivery, leading to a broken thumbnail. The correct thumbnail will appear once it's ready, usually within a few seconds. To minimize these issues, the following steps are recommended: Ensure the camera is not using a smart codec, variable frames per second (FPS), or an excessively long GOP (Group of Pictures) interval. Verify that the camera's time settings are correctly configured. Confirm the camera is within its bandwidth allowance. An excessively low bitrate limit may cause video stream issues, especially in complex scenes. If the camera exceeds its bitrate limit, frame drops can occur, resulting in corrupted video streams. Ensure the camera site has sufficient upload speed with a latency of 100 ms or less. High latency can corrupt video streams, and even with 15 FPS, a 100 ms latency may create issues due to the reduced time between frames. If the camera is connected to multiple VMSs or devices, ensure that each controlling entity uses distinct streaming channels or maintains consistent configurations. Ensure that AI features on the camera, such as WDR, Defog, and HDR, do not overload the CPU, as this can cause video streaming problems. Avoid enabling multiple smart features simultaneously, excluding server-side analytics.

The Alarm Monitoring Station can utilize IP speakers to enable monitoring personnel to transmit live or pre-recorded voice messages to specific areas for public address or security/surveillance purposes. This guide outlines the steps for setting up an IP speaker device in the Admin Portal and the Alarm Monitoring Station. 1. Connect the IP Speaker to the Network Begin by ensuring the IP speaker is properly connected to the existing IP network. If unsure about initializing the device, consult the system manufacturer's guide or documentation for detailed instructions, which will include step-by-step guidance and the required parameters for integration. Note: The audio compression codec for the IP speaker must be set to G.711U. 2. Add the IP Speaker in the Admin Portal In the Admin Portal, go to the Cameras menu tab and click the green "Add" button to register the IP speaker, following the same procedure as adding a camera device. Ensure that the Mic function is activated under the General tab of the newly added IP speaker device. After successfully adding and associating the device with a customer account, a description and specific instructions for the speaker can be added. These details will appear in the acknowledgment window of the Alarm Monitoring Station. Markup formatting can be used to customize the instructions. 3. Assign the IP Speaker to the Relevant Guard Roles If the IP speaker is to be used by multiple guard users, create the necessary guard roles and assign the appropriate permissions. In the customer account containing the IP speaker, go to the Roles menu and click the green "Add" button to create a new guard role. After creating the role, click on it to adjust the settings, ensuring the IP speaker is enabled by checking the corresponding box. 4. Set Up the IP Speaker in the Alarm Monitoring Station To use the IP speaker in the Alarm Monitoring Station, log in with the guard user assigned the created role. Navigate to the Cameras menu and search for the IP speaker by its assigned name in the search field, or locate it in the Offline tab. Drag the IP speaker into the layout. Open the camera controls for the IP speaker, click on the Microphone icon, and grant the browser permission to access the microphone through the Alarm Monitoring Station. The microphone can now be used to transmit audio through the IP speaker.

Step 1: Create a Customer Account A customer account serves as a container for all cameras and users associated with a specific client or multiple clients, depending on the integrator's needs. Steps to create a new customer: From the Customers menu, click the "Add" button and select "Customer." Fill in the customer's details. Set the default cloud recording settings for the customer account. Enter the customer's billing details. Click "Create" to finalize the customer account. If necessary, restrict access to specific features from the Account Profile. Step 2: Add Cameras To add a new camera, go to the Cameras tab and click the "Add" button. A popup window will appear where the connection method for the camera can be selected. Adding a P&P Camera: This method offers a straightforward and secure way to add a camera using a Plug & Play connection. Enter the registration code obtained from the camera and provide a camera name. Input the camera credentials. Click "Create" to automatically locate the camera and create a connection path. For ONVIF-compliant cameras, direct access to the camera settings is available through the Starllion admin portal. Adding an ONVIF Camera: Two methods are available for adding ONVIF cameras: the URL method and the Registration Code method. URL Method: This method requires manual port forwarding setup on the client side. Input the camera's information and click "Create" to add the camera. ONVIF features and camera analytics will be available. Registration Code Method: This method is suitable for P&P-compatible cameras with Starllion's Push Module firmware or if a Starllion gateway is installed at the camera site. Use the registration code to add a copy of the ONVIF camera, including those connected to multi-channel devices like NVRs. Adding a Generic Camera: Similar to ONVIF cameras, generic cameras can be added using the URL method or Registration Code method. URL Method: This method is for cameras that cannot be added using P2P or ONVIF methods. Create HTTP and RTSP port rules on the customer’s router. Input camera information, access URLs, and credentials, then click "Create" to add the camera. Registration Code Method: This method is for non-ONVIF compliant cameras connected to the gateway. Step 3: Add Users To create a new user in the Starllion Cloud system, follow these steps: Select the "Users" option from the menu. Click "Add" to create a new user. If the user’s role is available, assign it; if not, leave the Role field blank and assign the role later. A user can have multiple roles, but only one type of role (Admin or Guard) at a time. To change the user type, remove all Admin roles and assign Guard roles. To modify roles for a user, click on the user’s name in the Users table, go to the User Info tab, and update the roles. Creating a New Role: Select the customer for whom the role will be created. From the Customer menu, choose the "Roles" option. Click "Add" to create a new role. Provide a name for the role and select the role type (Admin or Guard). Choose whether to add all cameras or manually select specific cameras. To modify a role after creation, click the role from the Roles table and adjust camera assignments or permissions. Step 4: Configure Object Detection Push notifications require configuring object detection for selected cameras on the account. Steps to configure object detection: Enable Object Detection by choosing a plan with "+ Analytics." Create or edit a Detection Rule, selecting the trigger event. The "Act on" option activates server-side analytics. Select the objects to detect (multiple objects can be chosen per rule). Set the confidence level, determining the minimum certainty for an alert. Optimize the camera by adjusting detection zones/lines, image quality, trigger settings, and sensor alerts. Step 5: Create Alerts Alerts for sensor and system events can be created for users registered under selected customers. These alerts can be sent as email notifications or push alerts. To create or edit an alert: Open the Customers table and select the customer for whom the alert will be created. Go to the Alerts tab at the customer menu level. Click the "Create Sensor" button to create a new alert or select an existing one to edit. Name the alert and choose object detection as the alert type. Choose the desired objects and configure the alert’s schedule (active days and hours). Orange squares represent active times, while white squares represent disabled periods. After configuring the alert, click "Next" or go to the Cameras tab to add cameras. Add cameras and select the recipients for the alert. Choose users from the Available Contacts table or select all users. For push notifications to work, users must install the Starllion mobile app and log in using their credentials. Step 6: Install the App Starllion Cloud offers a mobile application for Android and iOS, designed for customers and their users (Admin or Guard roles). Integrators cannot access the mobile app or the video feed. To install the Starllion Cloud mobile app on an Android device: Visit the Google Play Store and search for 'Starllion Cloud.' After installation, the app will appear with the Starllion Cloud logo. Users can log in using their Guard, Admin, or owner credentials. Step 7: Review Push Notifications Ensure push notifications are enabled in the alert settings. When an event or alert is triggered, a push notification will be received on the smartphone. Open the app, go to the events panel, and review alerts and events. These steps may vary based on individual requirements and configurations.

With Starllion Cloud's Alarm Station, live camera feeds can be displayed continuously on a monitor, providing a visible reminder to store visitors that surveillance is in place. To disable the auto-pause feature, the alarm station needs to be armed. For a cobranded version of the alarm station without the Acknowledgement panel, submit a ticket requesting a modification to hide this panel in the interface. Use Case This feature is ideal for cameras not connected to an NVR/DVR, allowing all cameras to be viewed on one screen without heavily taxing the cameras themselves. Video streams are multiplied in the cloud rather than directly from the camera, ensuring smooth performance and reducing device strain. Traffic Consumption There is a difference in traffic usage between viewing cameras on the Alarm Station and the Video Portal. On the Video Portal, an inactivity popup stops camera streaming after a period of no activity to minimize traffic and avoid additional costs. However, this feature is disabled when the Alarm Station is armed, meaning live streams continuously pull from the cloud rather than the cameras. Users should monitor their data plans and account for potential increases in traffic when using the Alarm Station for prolonged streaming.

Introduction The Alarm Station is a specialized video portal provided by Stallion, designed for continuous 24/7 camera monitoring without interruptions, even during periods of inactivity. This feature is particularly beneficial for security personnel who require real-time site surveillance. A key aspect of the Alarm Station is its ability to display live events on-screen, enabling simultaneous viewing of multiple incidents across different cameras. Customization options allow specific event types to be displayed, ensuring that only relevant occurrences are highlighted for security monitoring. Access to the Alarm Station is available at [https://alarm.starllion.com], where the interface closely resembles the standard video portal. The primary distinction lies in the presence of the "Arm" button. When armed, the auto-pause function due to inactivity is disabled, ensuring continuous event cycling or maintaining an opened camera view indefinitely. In contrast, the regular video portal pauses all streams after 30 minutes of inactivity. It is essential to consider that enabling this feature may lead to increased data traffic costs associated with the account. Activating Alarm Mode To enable the Alarm Station, click on the shield icon next to the layout. Once activated, the icon changes to a red shield with a checkmark, indicating the system is armed. For on-screen event notifications to appear, at least one empty layout cell must be available. If all cells are occupied, notifications will not be displayed. When an empty cell is present, events populate that space, with the most recent event replacing older ones if the same camera feed is active. If all cells are occupied, events appear sequentially in available spaces. Selecting an event screen requires acknowledgment for its removal. Additionally, an audio alert is triggered whenever an event appears, ensuring security personnel receive notifications even when not actively monitoring the screen. Event Acknowledgment Detected events, such as motion detection of a person, appear on-screen with a red border, prompting acknowledgment. Classification options are available via a drop-down menu on the right side of the screen, allowing the system to respond accordingly. The acknowledgment menu can be repositioned and resized for a customized layout. Once an event is acknowledged, new incidents will continue populating the same layout cell. The Alarm Station offers configurable settings to display specific cameras and event types, allowing tailored monitoring solutions. Screen Configuration To configure the Alarm Station screen: Hover over the '+' sign in an empty layout cell. Arrows will appear, allowing selection of specific event types such as person or vehicle motion detection. Select the desired event type, and corresponding incidents will be displayed in that section. Additional customization includes adding live camera feeds from the camera menu, reviewing archived footage, dragging past events onto the layout, and acknowledging both past and current events. When an event appears, a notification bar at the bottom of the video provides quick acknowledgment options. Selecting 'OK!' dismisses normal events, while the 'Replay' button allows immediate review. Event types are marked with an icon at the bottom left of the event screen for easy identification. This level of customization ensures an optimized monitoring experience, making the Alarm Station a powerful tool for real-time event tracking and security response.

The Starllion platform provides a full suite of tools essential for launching a successful monitoring operation across multiple clients, including features to automate responses to common scenarios. To maximize the effectiveness of the platform, the following setup steps are recommended: Establish a separate Customer account for each client Set up a monitoring account Register the cameras that need monitoring Configure automation rules Example: Different cameras monitored at different times Step 1: Establish a separate Customer account for each client Add all the cameras the client wants monitored to their account. Configure the stream quality, recording duration, and any server-side analytics required. Set up any alerts the client wishes to receive personally. Step 2: Set up a monitoring account Create a distinct Customer account to house user accounts for all security personnel and automation rules needed for effective monitoring and incident response. Follow the same steps as for the client’s account when setting up this monitoring customer account. Step 3: Register cameras that require monitoring Identify the cameras to be monitored and their corresponding clients. Copy the sharing code from the monitoring customer and paste it into the "Activate sharing to another customer" field for the client whose cameras need to be shared. Repeat this process for all clients whose cameras need monitoring by the monitoring customer. For each client whose cameras are shared, a new role will appear in the Roles table listing all shared cameras. To grant security guards access to the shared cameras, one of the following actions can be taken: a. Add the shared role to the user’s role list (this can be done for both guards and admins). b. Create a new role and assign the shared cameras to it (this can be done by an integrator, manager, owner, or admin with permission to view the shared cameras). Choose the appropriate method based on the intended usage and access control needs. Step 4: Configure automation rules Define the automation rules required (for example, sending a signal to a store manager when more cashiers are needed at the register or dispatching first responders during an incident). Webhooks can be used to trigger devices and systems, such as smart outlets or integrating with platforms like Bold or IMMIX to activate rules set up in those systems. By utilizing webhooks, human error is reduced, and response times are improved. Example: A client requires all cameras to be monitored at night, but only specific cameras during the day. The optimal configuration would involve: Sharing all cameras with the monitoring customer. Using an integrator-level user to create a new role and adding cameras to be monitored during the day to that role. Creating separate users for the day and night shifts. Assigning the role created in step 2 to day shift users and the Shared role to night shift users to allow them access to all cameras. Assigning appropriate users to the alarm station to monitor the client’s cameras throughout the day. Setting up webhooks to automate responses based on expected events.

When an event is acknowledged in the alarm station using the OK! button, the event type will be automatically set to "Normal." To select a different event type, please use the side panel.

The option to choose between active and passive alarm stations is now available. Inactive Acknowledge side panels will be displayed, and the selected layout cell will not be replaced with a new event, providing the guard with ample time to process the current event. In passive mode, alarm station events will appear in the order they occurred, assuming passive viewing with little to no operator input required.