Which Devices Can Connect to CMSV6: A JT/T 808 and JT/T 1078 Checklist
Fleet Platform Guide
For a vehicle terminal to connect to the AlwayCare CMSV6 platform, the device needs to support JT/T 808 and JT/T 1078. JT/T 808 carries registration, location and alarm data. JT/T 1078 carries audio and video. This guide shows what each one is used for, what to ask a device supplier before you buy and how to trace the most common docking problems.
What each protocol carries
| Protocol | Carries | What you see on the platform |
|---|---|---|
| JT/T 808 | Terminal registration and authentication, location reports, alarms, parameter settings, text messages and snapshot commands | Vehicles on the map, status, alarms, track history, remote settings |
| JT/T 1078 | Real-time video, video playback, audio for two-way intercom and video file upload | Live preview, playback, intercom, video evidence for alarms |
A device that supports only JT/T 808 can report position and alarms, but it will not give you platform video. A device that has video but does not follow JT/T 1078 needs a private protocol or an adapter, which is a project of its own.
Questions to ask the device supplier
| Question | Why it matters |
|---|---|
| Which JT/T 808 version does the device use, 2011 or 2019? | CMSV6 handles both, but the two versions need separate batches for some platform tasks, such as sending text messages. |
| Does the device support JT/T 1078 for live video and playback? | This is what lets the platform open the camera channels. |
| How many video channels, and which audio format does the intercom use? | The platform setting for the audio format must match the device, or the intercom has no sound or distorted sound. |
| Does it support main stream and sub stream? | Main stream needs an extra TCP port open on the server. See the checklist below. |
| Does it report alarm attachments such as photos and video? | Alarm evidence depends on the device answering the attachment request. |
| Does it use any extended items, such as IO status, collision or rollover alarms? | Extended items follow an agreement with the platform. Ask for the extension document, because standard JT/T 808 alone may not show them. |
| Can it upload video files by FTP? | FTP upload is only for JT/T 1078 devices, and it is how recorded video moves from the device to the server. |
Which functions work depends on the device model, its firmware and its configuration. Test one unit on your platform before you order a batch.
What to check on the server side
- Ports. The platform documentation lists the TCP and UDP ports used for location, video and storage. If live video opens but the main stream does not, check that port 6630 (TCP) is open. See Can't see the main stream video.
- Audio format. In device management, select the audio format that the device supports. See No sound or abnormal sound on two-way intercom device.
- Server version. Some preview problems on certain channels are fixed in later server versions. See Some channels of real-time video cannot be previewed.
- Communication logs. The administrator can switch on device communication logs to see what the platform sent and how the terminal answered. See Platform logging and download.
Common docking problems and where to look
| Symptom | First check | Reference |
|---|---|---|
| Live video does not show, or only some channels show | Log of the preview request, the terminal answer and the platform answer | Real-time video docking log analysis |
| Picture stutters or freezes | Whether the timestamps of the video frames are continuous and the gaps are steady | Video stutter analysis |
| Playback search returns nothing | Log of the file search request and the terminal answer | Video search log analysis |
| Alarm has no photo or video attached | The order of messages: alarm report, platform reply, attachment request, terminal answer | Active safety docking log analysis |
| Snapshot does not arrive | Log of the snapshot request and the terminal answer | 808 snapshot log analysis |
| Recorded video must reach the server | Add an FTP upload task for a JT/T 1078 device, then download the file from the server | FTP upload of video files |
Extended items and special functions
Some functions go beyond the standard messages and rely on items agreed between the device and the platform. Examples in the platform documentation are collision, rollover, start, stop and IO alarms, IO status in the position report, forward and reverse rotation reports, and automatic file download over Wi-Fi for JT/T 1078 devices. See collision, rollover and IO alarms, IO status report, forward and reverse state report and Wi-Fi automatic download.
If you use a device from another supplier, ask them to confirm which of these they support. A function that is not in the standard messages will not appear just because the device connects.
A simple acceptance test
- Register one device on the platform and check that the vehicle appears and reports position.
- Open live video on every channel, main stream and sub stream.
- Test two-way intercom in both directions.
- Trigger an alarm and check that the alarm and its photo or video arrive.
- Search and play back a recorded clip, and upload a file by FTP if you need it.
- Leave it running for a shift and check the logs for repeated errors.
For wiring and testing on the vehicle, read Mobile DVR Installation: A Fleet Wiring and Test Checklist. For connecting devices to a platform you already run, read Integrating AI Dashcams with Your Existing Telematics Platform.
Limits to plan for
- Supporting the protocols is the entry condition. Functions beyond the standard messages depend on the device and agreed extensions.
- Different device versions and firmware can behave differently on the same platform.
- Video quality depends on the network as well as the protocol.
- Always confirm the exact functions in writing with the device supplier before a large order.
Questions fleets ask about connecting devices
Which protocols must a device support to connect to CMSV6?
JT/T 808 for registration, location and alarms, and JT/T 1078 for audio and video.
Can a device that supports only JT/T 808 connect?
It can report position and alarms. Platform live video and playback need JT/T 1078.
Does AlwayCare hardware connect to CMSV6?
Ask us to confirm protocol support and functions for the exact model you plan to use, and put them in your quotation.
Why can I see the live video but not the main stream?
Check that port 6630 (TCP) on the server is open and that the device supports main stream.
Why is there no sound on the intercom?
Select the audio format your device supports in the platform device management.
How do I find out why a device will not connect properly?
Ask the administrator to switch on communication logs, repeat the action and read what the platform sent and how the device answered.
Summary
- A device needs JT/T 808 and JT/T 1078 to connect to CMSV6 with location, alarms and video.
- Ask the supplier about versions, channels, audio format, main stream, attachments and extended items.
- Check ports, audio format and server version on the platform side.
- Test one unit with the acceptance steps before you order a batch.
Read the source documentation at docs.alwaycare.com, or send an inquiry with your device model and we will help you check it.
For fleet management, tracking and video platform options in one place, see the fleet management solution.
