A test IMMIX webhook can be created using IMMIX test servers. This requires using a specific endpoint and camera payload. Follow these steps to create a test IMMIX webhook: Input the constant "TEST_IMMIX_SERVER" as the ExtraText payload for the role of choice. Visit [IMMIX Test Server] (https://testmydevice.immixprotect.com/AlarmTest) and select UDP as the test alarm type. Then, press "Create Alarm Station." On the IMMIX test page, copy the Device ID. This ID is found as the numbers following the letter "S" in the email address. Use the copied Device ID as the Payload for the camera on which the webhook test will be performed. Create a new webhook by selecting SMTP as the delivery method and inputting the SMTP server address from the IMMIX test page as the target. Select the event type as either Motion or Analytic. Other event types are not supported by the IMMIX test server. Choose the role that was modified in step 1. Click "Create" to finalize the webhook creation. The webhook may take up to 10 minutes to become active. Notes: Longer event durations increase the chances of detecting multiple objects of different types. In the Starllion Cloud UI, all objects will be displayed on the timeline, thumbnails, and in the event list, allowing searches by object type and area. IMMIX does not support this functionality, submitting only a single event clip, thumbnail, and event code. For a push RTSP URL for IMMIX live view, submit a ticket with the camera ID, and a push RTSP URL will be generated. Events are sent after the Event Stop (when no more object movement is detected) or after a maximum of a 2-minute timer. There is a delay between the initial movement (Event Start) and the event being delivered to IMMIX (Event End). If immediate notification at Event Start is required, IMMIX currently does not support Event Start/Stop, but Starllion Cloud Alarm Station can be used for start and end event notifications. IMMIX accepts only a single thumbnail, so bounding boxes for all detected objects during the event are not available. In such cases, the operator will need to review the entire event.

Introduction To activate audio playback on Sunell speakers using webhooks, follow the instructions outlined below. This process includes uploading audio files, configuring alarm settings, and creating webhooks to trigger audio playback remotely. By completing these steps, audio playback can be controlled via webhooks effectively. Step 1: Enable ONVIF Log in to the Sunell speaker’s web UI. Navigate to the ONVIF Menu. Ensure that ONVIF Enable is checked to activate the ONVIF user. Enter the Username and Password for the ONVIF user, which will be used later during webhook configuration. Click Save to save the settings. Step 2: Upload Audio Files to the Speaker Access the Sunell speaker’s interface. Go to the Media menu. Click **Choose File** and select the audio file to upload. Ensure that the file is in MP3 or WAV format, with a filename consisting only of letters and numbers. Step 3: Enable the Alarm In the Alarm menu, create a pattern for the alarm. Select the audio file uploaded in Step 2. Set the duration and cycle mode for the audio playback when triggered. Check Play URL Enable to enable HTTP playback, which is required for webhook creation. Step 4: Create a Webhook In the Starllion Cloud Admin Portal, go to the Alerts menu and select the Webhooks tab. Click on Create Webhook. Choose Push Gateway as the Delivery Method. Enter the Registration Code for the Sunell speaker, using port 80. If the speaker is integrated using a gateway with P&P firmware, use the speaker’s own registration code. If integrated via a gateway, use the registration code generated by the gateway. In the Path, paste the link generated from the previous step. Ensure it starts with "/api" after the IP address. Select GET as the HTTP method. Enter the Username and Password for the speaker credentials. Step 5 (Optional): Test the Speaker To test the speaker and webhook functionalities, two options are available: Wait for the event type to occur naturally. Add an Acknowledgment event type to the "Event Types" list and use the alarm station to trigger the webhook. Testing Process: Open the alarm station and log in with a user who has access to the camera associated with the webhook role. Arm the alarm station. Wait for an event to occur or drag and drop a past event from the Menu events into the layout. Select the same event type as the webhook from the Acknowledgment dropdown list (e.g., “Normal”). Click OK to acknowledge the event. After completing these steps, the Sunell speaker should playback the audio file triggered by the webhook.

Sunell IP speakers can be integrated seamlessly using the Plug-and-Play method, similar to P&P-compatible cameras. This integration enables the speaker to be used for direct communication with visitors or intruders through the video portal and/or alarm station using the "Microphone" button. The following steps outline the process of integrating a Sunell IP speaker: Step 1: Upgrade the Speaker with P&P-Enabled Firmware Download the P&P-enabled firmware from the provided link. Connect the speaker to the same local network as the computer and allow it time to boot up. Identify the speaker's IP address and open it in a web browser. Log in to the speaker's web interface, navigate to the System menu, click Choose File, and select the downloaded firmware. Click Upgrade to initiate the firmware update process. Step 2: Configure the ONVIF User on the Speaker After the firmware update, if necessary, access the speaker's web interface by adding port 6226 to the IP address (e.g., `http://<IP_Address>:6226`). In the ONVIF menu, enable the ONVIF protocol, create a username and password for the ONVIF user, and click Save to apply the changes. Step 3: Verify the Network Configuration of the Speaker Ensure that the speaker can access the internet and resolve DNS names. It is recommended to use DHCP for automatic network configuration, but if manual configuration is needed, enter the correct Subnet Mask, Gateway, and Primary DNS servers to enable internet connectivity. Step 4: Obtain the Speaker's Registration Code On the speaker’s Status page, copy the MAC address. Remove any colons (":") from the MAC address and prepend SNLL to the string. Example: If the MAC address is A2:C0:A4:20:03:B2, the registration code is: SNLLA2C0A42003B2 Step 5: Register the Speaker in the Admin Portal In the Admin portal, select the customer to whom the speaker will be assigned from the Customers table. Navigate to the Cameras menu and click Add to integrate the speaker. In the pop-up window, select the P&P Camera option. Enter the registration code from Step 4 and the ONVIF user credentials created in Step 2. Choose the billing plan and click Create. Step 6: Activate the Speaker's Audio Feature Open the speaker in the Admin portal, go to the General tab, and enable the "Mic" feature by sliding the Mic button to the On position. This activates the audio feature, allowing communication through the speaker. Step 7: Use the Speaker in the Video Portal or Alarm Station In the Video portal or Alarm station, open the speaker. Since the speaker does not provide a video stream, it will appear under the "Offline" tab in the Cameras menu. Click the Offline tab or search for the speaker, then click to open it or drag it into one of the layout cells. In the camera toolbar, click the Microphone button. A histogram will appear, allowing real-time audio transmission through the speaker. If prompted by the browser, grant microphone access to the portal site. Billing Note The speaker will be billed according to the minimum monthly camera charge. By following these steps, the Sunell IP speaker can be successfully integrated and used for audio communication within the video portal or alarm station.

Edge recording can currently be enabled only on a per-camera basis. To activate this feature, a support ticket must be submitted with the relevant camera IDs. Additionally, certain requirements must be met to ensure proper functionality of edge recording recovery. General Requirements: The device must comply with ONVIF Profile G. The device clock should be accurately configured for the camera's location, preferably using NTP synchronization. The same streaming channel must be used for both cloud and locally stored data. The upload speed must be at least double the bandwidth required by the current device configuration. For example, with five cameras streaming at 1 Mbps each, the upload speed must exceed 10 Mbps to prevent issues with live streams during edge recovery. Camera-Specific Requirements: The camera must save the same stream to the SD card as the one used for cloud storage. The SD card should have sufficient capacity to store recordings for the maximum expected duration of internet outages. NVR-Specific Requirements: The camera must integrate with the NVR using the ONVIF protocol. The NVR, rather than individual cameras, must connect to the cloud, with the cloud configuration using the same streaming channel as the NVR storage. Once these requirements are met, the camera ID can be provided to enable the Edge recording feature. Recovery Process: The edge recovery process duration depends on the size of the gap in the archive. Recovery speed is set to 1X, meaning it will take at least one hour to recover one hour of missing footage and one day for a full day of footage. Additional time is required to initiate the recovery process. For instance, even a one-minute gap in the cloud archive will take approximately one hour to recover.

Introduction The ONVIF Registration Code method can be utilized to add a copy of an ONVIF-compliant camera to the system for specific purposes, such as using a different streaming profile for time-lapse or when a camera is connected to a multi-channel device like an NVR/DVR or a multi-sensor camera. This method is applicable for cameras that are P&P compatible with Starllion Cloud's Push Module firmware or already added via the P&P method through a Gateway. Steps to Add a Camera to the Starllion Cloud Service Step 1. Selecting the Customer and Camera Addition Method Choose the relevant customer for the camera. Navigate to the Camera tab and click the Add button. Step 2. Selecting the Registration Method After selecting the ONVIF Camera option, a popup window will appear. Set the Connection Mode to Registration Code. Step 3. Entering Camera Information Input the camera’s Registration Code, which can be retrieved from the camera's WebUI or copied from the Gateway interface if the camera is connected to one. Select the appropriate Video Protocol (RTSP or RTMP) and HTTP Protocol from the dropdown menu. Enter the camera's ONVIF user credentials (Username and Password). If the camera has a dedicated ONVIF user, use those credentials. Click Get Channels to retrieve available channel profiles, then select the desired profile. Provide a name and short description for the camera. Use the Quality Preset slider to configure quality settings. The system will adjust the camera’s streaming profiles based on its resolution list and presets. Click Create to finalize the addition of the camera. Step 4. Adjusting Streaming Quality Post-Integration Once integration is complete, review and adjust settings if necessary: Click the camera name in the Cameras table to access the configuration page. In the Quality tab, modify streaming profiles, resolution, image quality, and target bitrate. Adjust the archive duration in the Recording tab as needed. By default, it follows the customer’s standard settings. If ONVIF event configuration is supported, motion detection, line crossing, and other analytics can be managed from the Analytics tab. Server-side analytics can also be enabled here.

To integrate cameras into the Starllion Cloud Admin Portal account using the API, follow these steps: Step 1: Register for a Free Account on Postman Register on the Postman platform by visiting https://web.postman.co/. The process is free and straightforward. Follow the prompts on their website to create an account. Step 2: Import the Starllion API Library into Postman Use the Run in Postman button available on the admin portal to import the Starllion Cloud API library into Postman. During the import process, select the desired workspace to save the library. Step 3: Obtain the API Key To create cameras, a token is required. Obtain this token using the method listed at the bottom of the API methods. Log in with integrator user credentials and an integrator API key, which can be found on the same page as the Run in Postman button. Step 4: Use the Generated Token After successfully generating a token, a success message will display the token details. If an environment is configured in Postman, the token will be automatically applied to subsequent requests until it expires. The token's expiration time is included in the response. For unauthorized errors, manually copy the token and paste it as the Bearer token value in the relevant field, ensuring no quotes surround the token. Step 5: Add Cameras via API Use the Register ONVIF Camera method to add cameras: In the Headers tab, provide the API key and token if they are not auto-applied. In the Body tab, enter the camera details and click Send. To add additional cameras, modify the necessary fields and repeat the process by clicking Send again. Automating Token Management with an Environment Step 6: Create a New Environment Simplify token and variable management by creating a new environment in Postman. This setup allows automatic updates to variable values, streamlining API workflows. Step 7: Add Variables to the Environment Add variables and values to the environment in one of two ways: Manually entering the variable and its value. Using the key-value pair method. By following these steps, the integration process becomes efficient and seamless, enabling quick setup and management of cameras in the Starllion Cloud Admin Portal.

Triggering audio files on TAO speakers via webhooks involves configuring a pattern on the speaker and creating a webhook to activate it. Follow these steps: Step 1: Upload Audio Files to the Speaker Navigate to the Media menu and click the Upload button to upload audio files. This action opens a popup where a file can be selected from the computer. Supported formats include MP3 and WAV. Ensure the filename contains only letters and numbers, as certain symbols may cause errors. Step 2: Create a Pattern To enable audio playback, create a pattern in the Pattern menu. Choose one of the 20 available patterns and rename it for better organization if desired. Assign an audio file to the selected pattern, configure playback options (e.g., repeat count and delay between repeats), and adjust the volume as needed. Step 3: Set Up a Path to the Speaker Establish a port forwarding rule on the router connected to the speaker, enabling access to the speaker's HTTP port via the internet. Step 4: Create a Webhook Access the Webhooks tab in the Alerts menu and click Create Webhook. Use the router's WAN address and the public port created in the previous step as the URL. Include a specific path to indicate the pattern number to trigger. The URL format is as follows: http://WAN_IP:port/api/v1/pattern/play?pattern_number=1&playcount=1&interval=1&volume=0 Replace WAN_IP with the router's actual WAN IP address, port with the public port, and 1 (in pattern number) with the desired pattern number. Adjust playback parameters such as repeat count and volume if needed. Click Next to assign triggering events and specify roles for cameras included in the alert. Note: In the platform, Analytics refers to object detection events generated by either the platform or smart cameras. Selecting Analytics as an event trigger during webhook setup corresponds to enabling object detection alerts.

Webhooks enable real-time notifications for specific events within camera feeds, streamlining surveillance workflows. Follow these steps to set up webhooks for IMMIX integration: Step 1: Configure Payload for Each Camera Define the data to be included in payload fields for each camera. Access the Camera Properties and fill in the payload field for the IMMIX payload type. Step 2: Configure a Role To create a webhook for a specific group of cameras, create a role and assign cameras to it. Roles can be admin or guard-type, requiring only the "View" permission; other permissions are optional. Alternatively, use existing roles, such as the Owner role, to include all cameras for a particular customer. Each role includes an Integrations tab for configuring associated payload fields. Note: Payloads are tied to roles, so if a camera is reassigned to a different role, it will move on the IMMIX map accordingly. Ensure role configurations and camera assignments align with the intended setup to maintain accurate representations on the IMMIX platform. Step 3: Create a Webhook Note: Webhooks originate from the IP address 52.44.13.105. Add this address to the whitelist if required by network security. Go to the Alerts menu, select the Webhooks tab, and click Create Webhook. Specify delivery details, including the destination address. If the endpoint requires authentication, enable credentials and provide a username and password. Click Next to associate the webhook with specific roles and event types. Note: Changes to a webhook may take up to 10 minutes to become active. Step 4: Configure IMMIX for Live Camera Streams To enable live streams on IMMIX, provide the RTSP URL for each camera. Submit a support ticket with the camera IDs to receive unique RTSP URLs for the cameras. Use these URLs to configure IMMIX: In IMMIX, select the Generic Stream option and input the provided RTSP URL. Adjust alarm configurations based on monitoring station requirements. For post-recording setups: Retrieve the camera IDs from the Summary section. Enter these IDs into the Starllion Cloud Admin Panel under the respective Camera > Integrations > Device ID section. Note: The webhooks originating IP address is 52.44.13.105. Add it to the whitelist if necessary. These steps ensure a seamless integration of webhooks with IMMIX, enhancing surveillance capabilities.

Introduction For ONVIF-compatible cameras, the Info tab in the camera properties window displays a section indicating which analytical modules comply with the ONVIF protocol. These modules can be configured using ONVIF commands. In the screenshot example: Modules showing Available in green comply with the ONVIF protocol and can be configured directly from the Admin Panel. Modules showing Not Available in red require configuration through the camera's native Web UI. Steps to Configure Modules For ONVIF-Compatible Modules When modules are available through the ONVIF protocol: Access the camera settings in the Admin Panel. Navigate to the Analytics tab, where different tabs for each available module will be displayed. Configure the modules as needed. For Modules Not Compatible with ONVIF Protocol If the modules are not compatible with the ONVIF protocol, configuration must be performed through the camera's native Web UI. Determine if the camera was added to the Admin Portal as P&P or ONVIF by filtering the camera type under the Cameras tab. Configuring Through Native Web UI For ONVIF Cameras Open the camera settings in the Admin Panel and wait for the ONVIF protocol to load. Verify that the ONVIF indicator is green. Navigate to the Troubleshooting tab and copy the HTTP access URL from the provided box. Paste the URL into a web browser to access the camera’s native Web UI. Log in using web access credentials and configure the detector using the tools available in the native interface. For P&P Cameras Open the camera settings in the Admin Panel and wait for the ONVIF protocol to load. Confirm that the P&P indicator is green under the camera name, signaling that ONVIF protocols are fully loaded. Navigate to the Troubleshooting tab and click the Generate URL button. Copy the generated link or use the Open button to access the camera’s native Web UI directly. Log in using web access credentials and configure the detector through the native tools. For additional guidance on adding a camera using the ONVIF method, refer to the relevant support page.

Sound files stored on Axis IP speakers can be triggered via webhook functionality, allowing the playback of uploaded MP3 files when specific events occur. Follow these steps to set up a webhook for triggering sound files: Step 1: Create a Webhook Navigate to the Alerts menu and select the Webhooks tab. Click Create Webhook to begin the setup process. Step 2: Configure the Webhook URL 1. Determine the WAN Address Create a port forwarding rule on the router to enable connections to the speaker's HTTP port (default: port 80). Connect a computer or laptop to the same router and search for "What is my IP address" on Google. Use the displayed IPv4 address as the WAN address along with the public port created on the router. 2. Find the Speaker Audio File Path Access the Axis speaker web interface via the Axis Dashboard. Navigate to Device Online to view a list of connected speakers. Select the desired speaker and go to Advanced Device Settings. Open the Audio Clips menu to upload new audio files or copy the URL of existing files. 3. Combine the Parts The webhook URL consists of the WAN address (IPv4 + public port) and the specific path to the audio file from the speaker's interface. Step 3: Configure HTTP Method and Credentials Select POST as the HTTP Method. Provide the speaker's login credentials (the same username and password used for the speaker's web interface). Step 4: Set Trigger Events and Assign Roles Specify the types of events that will activate the webhook. Assign a role to determine which cameras will trigger the webhook. This setup enables efficient integration of sound notifications with surveillance events, leveraging the Axis IP speaker's functionality.

Android phones can be connected to the Starllion Cloud platform by utilizing third-party Android applications that transform the phone into an ONVIF-compliant camera. These applications are available for free or as paid versions on the Google Play Store. Note: Starllion is not affiliated with any third-party applications. Use them at your discretion, as the examples mentioned are simply tested options compatible with the platform. Step 1: Setting Up the Mobile Application Install the chosen application on the phone and launch it. Navigate to the Connection Settings and select Local Broadcasting. Configure a login and password for the camera, then set the HTTP and RTSP port numbers. Enable the ONVIF support option under the ONVIF Support section. Go to Service Control and select Start Server to activate the service. Step 2: Adding the Camera Using Port Forwarding Configure port forwarding for the HTTP and RTSP ports to access the device remotely. Add the phone camera to the Starllion Cloud portal using the ONVIF method. Follow the instructions in the video tutorial or the step-by-step ONVIF camera addition manual for guidance. Using the Starllion Cloud Gateway Open the Gateway URL in a web browser. In the web interface, select Discovery to locate the mobile camera. Once detected, click the plus button to add the camera to the gateway. If the camera is not discovered automatically, use an IP discovery tool such as Advanced IP Scanner to locate it. Then, manually add the camera using the Add Camera button. Final Step: Adding the Camera to the Starllion Cloud Platform Add the phone camera to the Starllion Cloud platform using the P&P method. Use the registration code from the gateway, along with the username and password created in Step 1. Once the setup is complete, the live video feed from the phone camera will be accessible through the Starllion Cloud Video Portal, similar to other connected cameras.

On Hikvision cameras, adjusting the video stream settings is necessary to enable the microphone functionality. Additionally, ensure the camera is configured to use the G.711u codec or any compatible variations, such as G.711ulaw.

To activate the speaker on the camera and enable communication, press the microphone button in the video portal. A histogram will appear, confirming the audio connection and displaying the microphone's audio level. (Mic Button) (Histogram) Conditions for Using Dual Audio 1. The camera must support dual audio and have both a microphone and speaker connected. 2. The microphone should be enabled in the admin portal. 3. The audio compression codec should be set to G.711U. Troubleshooting Common Dual Audio Issues 1. No "Talk" Button in the Video Portal Verify that the camera supports dual audio mode and that a speaker is connected and enabled in the camera's web interface. Ensure the "Mic" toggle in the admin portal is enabled (green). After enabling the necessary settings, reboot the camera. 2. No Activity on the Histogram This issue often arises from a problem with the microphone connected to the computer. Check the system settings to ensure the microphone is functioning correctly. Ensure the browser is not blocking access to the microphone. For instance, in Google Chrome, click the lock icon in the address bar and allow microphone access for the video portal website. If the microphone is still not active, check for other programs using the microphone, such as an active Skype call or another open webpage. 3. Sound Level Issues If sound is clear from the camera but not audible on the other end (or vice versa), the sensitivity of the microphone or the output level of the speaker may be too low. Adjust the input/output gain levels of the camera as necessary to resolve the issue.

For newer Axis cameras, navigate to System > Plain Config. Scroll down to the Properties section. Look for the System subsection and Architecture line. Select the push module with a name that matches the symbols found in the Architecture line. For older cameras with the previous version of the web interface, go to System Options > Advanced > Plain Config. From the dropdown menu, select the Properties option. Scroll down to the Properties System section and find the Architecture line there. Choose the push module with a name ending in the symbols found in the Architecture line.

Two possible configurations exist for including an NVR in the surveillance project. The preferred setup involves a direct connection of the cameras to the cloud, with the NVR connected in parallel to the cloud. In this arrangement, the two systems remain fully independent: cameras stream directly to the cloud, while the NVR serves as a backup device for scenarios where internet connectivity is disrupted. If implementing the recommended configuration is not feasible, the following steps outline how to integrate an NVR into the system: Step 1: Enable and Configure ONVIF Access on the NVR To enable ONVIF access, navigate to the Security or Network settings page of the NVR and locate the ONVIF menu. For some models, an ONVIF user account may need to be created first. Refer to the NVR manufacturer’s user manual for detailed instructions. If the NVR lacks a separate ONVIF user/service but supports ONVIF protocols, proceed to Step 2. Step 2: Configure Port Forwarding for HTTP and RTSP Ports Set up port forwarding for the HTTP and RTSP ports on the NVR. Consult the router’s user manual for specific instructions on configuring port forwarding. Step 3: Add NVR-Connected Cameras to the System In the system menu, navigate to Customers, select the relevant customer, and open the Cameras tab to view the list of cameras. The NVR and any connected cameras will appear here. Click Add and choose the ONVIF Camera option to add each camera connected to the NVR. This will create multiple entries of the NVR on the list, one for each connected camera. Step 4: Configure Streaming Channels for Each Camera Open each camera entry created in Step 3 and select the appropriate streaming channel under the Quality tab. This ensures that the desired camera is displayed in the portal under the specified name. Step 5: Verify NVR Encoder Settings When a camera sends video streams to multiple devices (e.g., the cloud platform and the NVR), ensure that each device uses a different stream channel. Sharing the same stream channel across devices can lead to conflicts, resulting in dropped connections or other issues. If the NVR is configured to use the H.265 codec, compatible streaming channels may not appear in ONVIF, making it impossible to select cameras in the admin portal. Switching the NVR to the H.264 codec through its web interface resolves this issue and makes the channels visible. Note: For NVRs that use proprietary protocols such as plug-and-play, P2P, or other native communication methods, ensure that the ONVIF protocol is used instead. Failure to switch to ONVIF may lead to connectivity problems, such as video loss or unexpected changes to camera resolution or quality settings in the admin portal.

For certain cameras, enabling a separate ONVIF user and the ONVIF protocol is necessary to ensure proper operation within the environment. Cameras from manufacturers such as Axis, Hikvision, and others often require an additional step during configuration for use with cloud monitoring services. If ONVIF services are not enabled on the camera, an error message will appear in the Troubleshooting tab of the camera: Even when the correct username and password combination is used, this error will persist if the ONVIF service is not configured. To resolve this issue, enable ONVIF services and create an ONVIF user through the camera's native web interface. For P2P-enabled cameras, the Generate Link button can be used to access the camera remotely. For cameras added using the ONVIF option, the HTTP link and port used during setup should be utilized. The exact procedure for enabling ONVIF will vary depending on the camera model and is typically found under the Security or Network Security menus. Axis Cameras: For modern Axis cameras, navigate to the System menu and select the ONVIF option. In the ONVIF menu, click Add to create a new ONVIF user. The same username and password used for accessing the camera’s web interface can be utilized. Ensure that the new user has Administrator access. Once the ONVIF user is created, ONVIF services will be enabled. These credentials should then be used in the Admin portal to add the camera. For older-generation Axis cameras, navigate to the System Options menu and select ONVIF. Click the Add button to create a new user with Administrator access. This action will enable ONVIF services, and the credentials for this user can be used to integrate the camera into the Admin portal. Hikvision Cameras: For Hikvision cameras, access the Network menu and select Advanced Settings. Under the Integration Protocol tab, check the box to Enable ONVIF. Then, click Add to create a new user. The same username and password used for logging into the camera’s web interface can be applied. Ensure that the new user is assigned the Administrator level. Save the changes to activate ONVIF services.

**Confidential Material – To be used by Permitted Parties Only** Ensure all cameras have the latest firmware updates installed before starting configuration. Steps: Update all cameras to the latest firmware. Configure each camera's IP address and general settings. Verify that an ONVIF user is configured. Check the availability of an ONVIF profile and create a separate one if necessary for use with Starllion Cloud or other services/devices. Add cameras to the Starllion Cloud service. Integrate cameras with other services or devices. Important: Assign a different streaming channel for each service or device connected to the camera to avoid conflicts. Camera IP Address Setup P2P mode is the recommended connection method. Detailed instructions for each manufacturer can be found in the Welcome Package under the Push Module folder. DHCP mode is preferred in most cases. For static IP address configuration, verify the default gateway and preferred DNS server under Network > DNS. Configure the camera clock and other parameters but avoid adjusting image quality at this stage. Note: Stream quality settings will be automatically adjusted during integration into the platform. ONVIF User Setup Some camera models require an ONVIF user to be configured before external services or devices can connect using the ONVIF protocol. for Axis Cameras: Navigate to the System tab and select ONVIF. Confirm the presence of an ONVIF user. If no user is listed, create one with Administrator rights. Important: The ONVIF user must be created before activating the Push Module on the camera. Manufacturer-specific tutorials are available in the Welcome Package. ONVIF Streaming Channel Configuration Consult the manufacturer’s manual for instructions on configuring ONVIF streaming profiles. Using Axis cameras as an example: Ensure at least two streaming profiles (channels) are available. For devices like NVRs from different manufacturers, the first streaming profile in alphabetical order is often selected. Use the second or subsequent profiles for Starllion Cloud streaming. If the second service allows manual channel selection, ensure different channels are used for each connected service or device. Note: Ensure Starllion Cloud and other services or devices use different streaming profiles (channels). Overlapping configurations can cause conflicts, leading to performance issues. Push Installer Setup Install the Starllion Cloud Push Installer by following manufacturer-specific instructions provided in the Welcome Package. Using Uniview cameras as an example: Launch the Starllion Cloud Push Installer utility. Enter the local IP address of the camera and click Start. Upon successful installation, a Register Code will appear, which can be used to add the camera to Starllion Cloud. Note: The installation process varies by manufacturer. Refer to the Welcome Package for detailed instructions. Connect Camera to Starllion Cloud Access the Starllion Cloud admin panel and open the Camera Menu. Add the camera using the preferred method. Manufacturer-specific tutorials are available in the Welcome Package. Once connected, navigate to the Quality tab to select the desired streaming channel. Adjust other camera properties as needed. These settings will automatically sync with the camera. Save the settings. Connect Camera to Other Services To integrate the camera with other services or devices, follow the manufacturer’s specific instructions, which are typically available on the service provider’s or device manufacturer’s website. For Uniview NVRs: Go to the Camera Menu and select the Encoding submenu. Check the Storage Mode to determine the streaming channel used by the NVR. In some cases, this menu allows the selection of a different channel. Adjust stream quality settings based on storage and viewing requirements. Note: Ensure the streaming channel used for NVR storage is different from the one used for Starllion Cloud to prevent conflicts.

There are two methods for adding a camera using the Generic option. The first method involves using the URL, which requires configuring port forwarding. The second method uses the camera's registration code, applicable if the Starllion push firmware is installed on the camera. 1. Adding a Generic Camera Using the URL Method Any IP camera with an RTSP stream can be added to the system through this method. This requires configuring a port forwarding rule to enable the server to access the camera's RTSP stream. The steps for setting up port forwarding depend on the router or modem model. Administrator-level access to the router at the camera's location is necessary. In the router's web interface, locate the Port Forwarding option. Create a port forwarding rule specifying Public (or External) and Local (or Inbound) ports. For the Public port, use any unused port, and for the Local port, use the camera's RTSP port (default is 554). Ensure the protocol is set to TCP/UDP or "Dual" on some routers. Include the local IP address of the camera and assign a Static IP address to prevent invalidation of the port forwarding rule if the camera's local IP changes due to DHCP. Once the port forwarding rule is saved, navigate to the Admin portal, select a customer, and open the Cameras menu. Click the "Add" button and choose the Generic option. Select "URL" as the connection mode. For the Video Source URL, input the camera's location IP address along with the Public port created in the router. Dynamic DNS services are recommended to account for changing IP addresses often assigned by internet service providers. To find the IP address of the camera's location, connect a device to the same network as the camera and search online for "What is my IP." If the camera requires a username and password to access the video stream, enter those credentials; otherwise, leave the fields empty. 2. Adding a Generic Camera Using the Registration Code This method is suitable for non-ONVIF compliant cameras connected to a gateway or for cases where an ONVIF camera is to be added as Generic, provided the Starllion Cloud push module is enabled on the camera.

Any ONVIF-compliant device, such as a camera or NVR, can be added through the ONVIF option. Adding a device via this method requires setting up port forwarding for the device's HTTP and RTSP ports. The following sequence of steps is recommended for adding a device using the ONVIF option: 1. Ensure the Camera Has the Latest Firmware Installed Follow the manufacturer's instructions for updating the firmware to the latest version. 2. Configure the Camera's Network and General Settings Set up the camera's network settings, ensuring appropriate Gateway and DNS configurations for the local network. Verify the HTTP and RTSP port settings. Assigning the camera a Static IP address is recommended to prevent the Port Forwarding rule from becoming invalid if the DHCP service reassigns the camera's IP address. 3. Verify ONVIF User Configuration For some camera models, it may be necessary to create a separate ONVIF user. 4. Set Up Port Forwarding on the Router The process for creating a port forwarding rule depends on the router or modem model. Administrator access to the router at the camera’s location is required. Access the router’s web interface and navigate to the Port Forwarding menu. Create a port forwarding rule that specifies Public (or External) ports and Local (or Inbound/Private) ports. Use any unused port for the Public ports. For the Local ports, use the RTSP port (default is 554) for the first rule and the HTTP port (default is 80) for the second rule. Set the protocol to TCP/UDP (or "Dual" on some routers) for both rules. Provide the camera's local IP address. 5. Add the Camera to the AVYCON Cloud Service After completing the camera and router configuration, add the camera to the system through the Admin portal. In the Admin portal, select a customer and open the Cameras menu. Click the "Add" button and choose the ONVIF option. Select "URL" as the connection mode. Using a DNS service is recommended to map the camera's path, as it ensures continuous access even if the IP address changes. If DNS is unavailable, the direct IP address of the location can be used. To find the location's IP address, connect a computer to the same router as the camera and search online for "What is my IP." The first result typically displays the IPv4 address; copy this address for the HTTP access URL. Enter the PUBLIC port numbers configured on the router for HTTP and RTSP access. Provide the camera’s ONVIF username and password. If the camera requires a separate ONVIF user, use those credentials instead. Click "Get Channels" to load available channel profiles from the camera and select the desired profile from the dropdown menu. Adjust the Quality Preset slider to configure the preferred settings, and the system will adapt the camera’s streaming profile accordingly. Click "Create" to finalize the addition of the camera to the system. 6. Adjust Streaming Quality After Integration After integration, the camera settings can be reviewed and adjusted if needed. Access the configuration page by selecting the camera name in the Cameras table, then navigate to the Quality tab. Modify the streaming profile, resolution, image quality, and target bitrate as required. Archive duration defaults to the customer’s settings but can be changed from the Recording tab. For cameras supporting ONVIF event configuration, motion detection, line crossing, and other analytics modules can be managed from the Analytics tab. Server-side analytics can also be enabled here. For ONVIF cameras, only the Pay-as-you-go billing option is available. The monthly bill for each camera includes storage used by archives and traffic generated when the camera is viewed via the Video portal or mobile application.

To change the user credentials for an ONVIF camera, even if the current credentials remain valid, the process can be completed through the Starllion Cloud account using the following steps: Step 1: Log in to the Starllion Cloud Account Access the Starllion Cloud account and select the camera requiring updates to its IP address or ONVIF username and password. Step 2: Update the Camera IP Address After selecting the camera from the Camera Tab, navigate to the Network Tab within the camera settings. To modify the IP address, input the new address in the HTTP access URL field along with the port number. Test the connection by clicking "Ping." If successful, a confirmation message will appear. If no changes to the IP address are required, proceed to the next step. Step 3: Update the Camera Credentials Within the Network Tab, click "Change credentials" to access the fields for updating the ONVIF user credentials. Enter the new username and password, then click "Check connection." Upon verification, the updated credentials will be saved in the system. Step 4: Confirm Camera Settings After saving the updated settings, the system will prompt for confirmation of the camera's configuration. Select the appropriate stream profile, resolution, FPS, image quality, and bitrate. By following these steps, the user credentials for an ONVIF camera can be successfully updated in the Starllion Cloud account, even if the existing credentials are still functional.