Skip to content

xtofuub/Sentinel-VOIP

Repository files navigation

Sentinel VOIP logo

Sentinel VOIP

Prank calls, on command.

Choose a localized scenario, preview the setup, launch an authorized call, and follow the recording and request trail from one focused console.

React 19 · Vite 8 · 2,129 scenarios · 64 locales

Sentinel VOIP control room

One console, start to finish

Sentinel turns the existing call flow into a clear browser workspace. The catalog, session composer, returned recordings, and request diagnostics stay connected instead of living in separate tools.

Sentinel session flow

Built for the full session

Sentinel language and region selector Sentinel API log console
Language-first discovery
Search 64 localized collections, then browse and preview the matching prank scenarios.
Readable request diagnostics
Filter outcomes, scan latency, expand sanitized payloads, and copy the event you need.
  • Scenario library — Search titles and descriptions, filter by language and region, preview audio, and carry a selection into the session workspace.
  • Session workbench — Review the scenario, recipient, country code, and dial ID before sending one backend task.
  • Live activity and recordings — Auto-refresh browser-linked calls, follow each status timeline, and open a focused recording page with playback, rename, copy, and download actions.
  • API logs — Keep the latest 120 requests in session memory with status filters, timing summaries, expandable payloads, and recursive recipient-field redaction.
  • Motion controls — Use the full visual treatment or switch to the reduced-motion experience at any time.

Quick start

Requirements

  • Node.js 20.19+ or 22.12+
  • pnpm via Corepack
git clone https://github.com/xtofuub/Sentinel-VOIP.git
cd Sentinel-VOIP
corepack enable
pnpm install
pnpm dev

Open http://localhost:5173.

Commands

Command Purpose
pnpm dev Start the Vite development server
pnpm lint Run the ESLint checks
pnpm build Create the production bundle
pnpm preview Preview the production build on port 4173

How it works

  1. The local catalog is normalized into 64 locale collections and 2,129 scenario records.
  2. A session creates and synchronizes an identity through the existing API flow.
  3. Sentinel submits the selected scenario and recipient task through the /api proxy.
  4. Activity automatically refreshes returned records and available audio for identities saved in this browser.
  5. API logs keep a sanitized, in-memory trace of request outcomes and payloads.

The frontend keeps the current service contract intact. Vite proxies /api during development, while the production rewrite is configured in vercel.json.

Current boundaries

  • Calls launch immediately. Delayed scheduling is not exposed because the current backend contract does not document reliable future-time execution.
  • Identities and recipient context are browser-local and can be cleared with site data.
  • API logs are session-only and disappear on reload.
  • Scenario images, audio previews, and live API behavior depend on their remote services.
  • Country flag images are served by FlagCDN / Flagpedia.

Responsible use

Use Sentinel only where you have permission and a lawful purpose. Comply with consent, privacy, recording, telecommunications, and anti-harassment rules that apply to you and the recipient.

Author

Built by xtofuub.

About

Reverse-engineering of the Juasapp VoIP protocol using a jailbroken iOS device. Unlimited / cracked signaling flows were extracted through dynamic runtime analysis and rebuilt in JavaScript with device spoofing, handshake replication, and resilient API orchestration.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors