Courts & Justice
Secure remote hearings on infrastructure you own
Real-time audio and video for remote hearings, attorney–client visits, mediation and legal consultation. Runs entirely inside the court network, bridges isolated networks, and embeds into existing case-management systems through SDKs and APIs.
Challenges
What we deliver
Remote hearings
Judges, parties and lawyers join from desktop, browser or mobile; the whole session is recorded.
Cross-network bridging
Paired internal/external gateways relay media through a one-way data diode, keeping networks physically separated.
Attorney visits
Remote attorney–client video visits with full audio/video recording.
Online mediation
Parties join from a browser link — no install required.
Device integration
RTSP / GB28181 cameras and SIP / H.323 room systems join through the device gateway.
Workflow integration
Server APIs and client SDKs let your case-management system schedule, admit and archive sessions.
Why SRTC
Customer stories
Customer names are withheld for confidentiality.
Justice
20+courts and procuratorates across China
Who
Use cases
- Remote hearings that bridge the court intranet and the internet through data diodes or codec boards — one deployment cut its case backlog by 50%
- Public live streaming of hearings to web and mobile viewers
- Hearings with speech-to-text transcripts generated automatically
A provincial procuratorate
Video conferencing + VOD on a fully isolated private cloud
FAQ
How can external parties join when the court network is isolated?
A media gateway is deployed on each side of the network boundary and they exchange media through a data diode (or codec board). External participants connect to the outside gateway, court staff stay on the inside, and both sides share the same session without a direct network link.
Can we keep our existing courtroom equipment?
Yes. SIP / H.323 room systems and RTSP / GB28181 cameras join sessions through the device gateway and interoperate with software clients.
Where are recordings stored?
The recording service runs inside your network and writes to your own disks or object storage. Nothing is sent to the public internet or to us.
Ready to build?
Get a self-hosted trial, SDK access and hands-on help from our engineers