Requirements
Prepare the provider account, permissions, and camera access before opening the integration in GuardDog.
Credentials
RoscoLive email
RequiredThe email address for a dedicated RoscoLive account that can access the fleet.
RoscoLive password
RequiredThe password for the dedicated RoscoLive account.
Company name
OptionalRequired when the account can access more than one fleet. Enter the company name exactly as it appears in RoscoLive.
Provider account checklist
- A RoscoLive account with access to the intended fleet and cameras.
- Permission to list fleet devices, retrieve recorded media, start live video, and manage company webhooks.
- At least one active DV4 or DV6 camera assigned to a vehicle.
- Outbound access from the camera platform to the GuardDog HTTPS webhook URL.
Capabilities
Device discovery
Supported
Sync Rosco cameras and match them to units by stable device identifiers.
Safety events
Supported
Receive Rosco Events and Alerts through an automatically managed webhook.
Incident video
Supported
Retrieve road- and driver-facing footage attached to Rosco events.
Live video
Supported
Start road- and cab-facing HLS streams from an assigned camera.
Setup guide
- 1
Create a dedicated RoscoLive account
Use an account with the minimum fleet, camera, media, live-video, and company-webhook permissions GuardDog needs.
- 2
Open the Rosco Vision integration
In GuardDog, go to Integrations, choose Rosco Vision, and enter the RoscoLive email and password.
- 3
Identify the fleet company
If the account is a partner or multi-fleet account, enter the company name exactly as shown in RoscoLive.
- 4
Test and save the connection
GuardDog verifies the account, binds the resolved Rosco company ID to your organization, and registers the Events and Alerts webhook.
- 5
Discover and assign cameras
Run device discovery, then assign the correct Rosco camera to each GuardDog unit.
- 6
Verify events and video
Generate a controlled provider-side event or use a recent demo event, then confirm the event, recorded clips, and live road/cab feeds in GuardDog.
Provider configuration
- The resolved Rosco company is locked to the GuardDog organization after connection to protect tenant boundaries.
- GuardDog creates and maintains the provider webhook automatically; do not replace its tenant-specific callback URL with a generic endpoint.
- Closing the GuardDog live-video viewer stops the provider session when Rosco supports cleanup for the active channel.
Verify the integration
Complete each check before enabling the provider for production alerting.
- CheckThe integration page reports a successful connection and webhook registration.
- CheckDevice discovery lists the expected camera serial/device identifiers.
- CheckA Rosco safety event appears under the correct GuardDog unit.
- CheckRoad- and driver-facing event clips load when media is available.
- CheckBoth available live feeds start and stop without leaving a provider session open.
Before generating a test event: verify the GuardDog organization, branch, contacts, call settings, and provider demo account. A real event can start texts and paid calls when alerting is enabled.
Troubleshooting
The company cannot be resolved+
Confirm the company name exactly matches RoscoLive. Partner accounts must identify one unambiguous fleet.
Webhook registration is denied+
Use an account role that can manage company webhooks, then test and save the integration again.
A camera is missing+
Confirm the account can see the device in RoscoLive and that the camera is active in the selected company.
Video is unavailable+
Confirm the account can view recorded and live video in RoscoLive and that the camera was online at the requested time.