TAK Integration

Use TAK Integration to send selected RC500 operational data from your Telisky organization to a TAK destination your team is authorized to use. Start only after the router is online in the cloud portal and the destination operator has approved the connection.

Before you begin

TAK Integration is available only when it has been enabled for your organization. View TAK integrations (tak:read) lets you open and read integrations. Manage TAK integrations (tak:write) lets you create or change customer-owned destinations. Owners and Admins receive both permissions by default, but custom access may grant them. You also need authorization from the destination operator. For a Telisky-managed destination, contact Telisky Support; managed provisioning is not a self-service tenant control.

Choose the destination model before entering any credentials:

Destination	Use it when	You provide or manage
Customer-owned	Your organization operates its own TAK service or has permission from its operator.	The destination host, connection settings, and its approved client credentials. Your team remains responsible for the destination’s access policy and availability.
Telisky-managed or operator-provisioned	Telisky or an authorized operator has arranged a managed destination for your organization.	The details and access requested by the service owner. Provisioning may require Telisky Support and is not available as a self-service tenant setting.

Caution

Location publishing is an explicit consent decision. Do not enable it until your organization has confirmed which devices may share location, with which destination, and for what operational purpose.

Connect a destination

1. Open TAK Integration and choose the destination model.
2. For a customer-owned destination, enter the values supplied by its operator:
   • Host and port for the TAK service.
   • TLS server name: the name that must match the server certificate. Do not substitute an address or a different name unless the destination operator confirms it is valid.
   • The destination’s CA certificate or trust chain.
   • An approved client certificate and its matching private key for mutual TLS.
3. Select the RC500 devices that may use this destination. Keep the scope as small as the operational need allows. A device outside the selected scope cannot publish to this destination.
4. Run the connection test before enabling any publishing option. The test must succeed before you continue.

Caution

A private key is a secret. Obtain it from the destination operator through an approved secure method. Never post, email, or include it in a support request, chat, screenshot, or public document. If a key may have been exposed, revoke it with the destination operator and replace it before testing again.

A failed test normally means the host, port, TLS server name, CA, or client credentials do not match the destination, or the router cannot reach it. Correct the connection first; do not enable publishing to work around a failed test.

Choose what to publish

Each publish option applies only to the selected device scope and destination. Turn on only the data your organization has approved:

Option	What it does	Privacy and operating notes
Location	Publishes the device’s location at the configured interval.	This is explicit consent to send location for the scoped devices to this destination. Enabling this integration option cannot enable or override the RC500’s separate location-sharing policy; both gates must permit location before it is published. Disable it or remove a device from scope to stop future location publishing.
Health	Publishes operational health independently of location.	Health can remain enabled when location is disabled or unavailable. Health messages use a bounded zero-point location rather than a device GPS position, so health does not reveal location.
Alerts	Publishes the alerts selected for the scoped devices.	Confirm that the destination is authorized to receive those operational alerts. Review delivery status if an expected alert is not present.
Video	Registers approved video information with the destination.	Video integration is registration metadata only. Telisky does not transcode, relay, or carry the video stream. The video source and destination must provide their own compatible stream path and access.

Set a reporting interval that meets the operational need without collecting or sending location more often than necessary. Set a clear callsign, team, and role so TAK users can identify the device and its intended operating group. Use organization-approved names; do not use a person’s identity in a callsign unless your policy permits it.

Note

Turning on health does not turn on location. Turning off location does not prevent health from being delivered. Each option remains an independent choice.

Monitor delivery

After enabling the approved options, use the integration’s delivery status and history to confirm that the destination is receiving current publications. Check the device scope, enabled options, last delivery result, and recent history when reviewing an incident or a planned change.

A successful delivery result records the integration’s delivery outcome; it does not prove that a particular TAK user saw or acted on the information. Review the destination with its operator when end-user visibility matters.

Disable or revoke access

To stop a single data type, turn off its publish option. To stop one device, remove that device from the integration scope. To stop all future publishing to a destination, disable the integration.

If the destination credential is no longer authorized or may be compromised:

1. Revoke the client certificate or access at the destination.
2. Disable the integration in Telisky while you investigate.
3. Obtain a replacement client certificate, private key, and CA details if the destination operator requires them.
4. Update the connection settings and run the connection test before enabling any publish options again.

Troubleshooting

Problem	What to check
TLS or connection test fails	Confirm the host, port, TLS server name, CA/trust chain, and matching client certificate and private key with the destination operator. Verify the certificate is current and authorized for this destination.
The destination cannot be reached	Confirm the selected RC500s have normal Telisky cloud connectivity; they do not need direct access to the TAK host or port. Confirm the Telisky MDM gateway can reach the configured host and port. For a private or tunnel-only destination, contact Telisky Support to confirm the approved organization-specific network path. Do not weaken network controls just to make the test pass.
The page, save action, or settings are unavailable	Confirm TAK Integration is enabled for your organization. You need View TAK integrations (tak:read) to open and read integrations, and Manage TAK integrations (tak:write) to create or change customer-owned destinations. Owners and Admins receive both by default, but custom access may grant them. Contact Telisky Support for managed-provisioning questions; managed provisioning is not self-service.
The test passes but no data appears	Confirm the device is in scope, online, and permitted to publish; then check the relevant publish option, interval, delivery status, and history. For location, confirm both consent and a usable location source. Health can publish without a location source.
An expected alert is missing	Confirm alerts are enabled for the device and destination, then review the integration delivery status and history. Ask the destination operator to verify its alert handling.
Video is not playing in TAK	Confirm that video registration metadata is enabled and accepted. Then troubleshoot the video source, stream compatibility, and viewer authorization with the video and destination operators. Telisky does not relay or transcode the stream.

For help, use Contact Telisky Support. Include the organization, affected device label, approximate time, destination type, and the visible status or error. Do not send private keys, passwords, raw credentials, or unnecessary exact location information.