CallKit-first voice
Incoming, ringing, and active calls map to a native iPhone experience instead of a bolted-on softphone shell.
Informational Surface / iPhone + VoIP Stack
A private voice system built for iPhone, blending native calling, secure messaging, and tenant-managed telephony into one operational stack. The public site is informational only.
CallKit and PushKit keep the iPhone experience close to the system phone surface.
WebRTC media, secure signaling, and tenant-aware server controls keep routing separated from the app shell.
`prismvox.app` stays informational while production API and WebSocket traffic live on dedicated public edge hosts.
Capabilities
The site now explains the product clearly instead of acting like a sign-up funnel. The emphasis is on what prismVox is, how it is shaped, and where the live system boundaries sit.
Incoming, ringing, and active calls map to a native iPhone experience instead of a bolted-on softphone shell.
Outbound SMS and calling flows honor explicit line selection so tenant routing stays legible and predictable.
WebRTC handles client media while the server side isolates signaling and RTP responsibilities across dedicated services.
The public website remains informational. The live API and WebSocket edge stay on their own hostnames to avoid blurred responsibilities.
Call history, conversation management, and DID ownership stay bounded to the active tenant context.
SwiftUI, PushKit, Speech, and a global in-app call surface keep the product aligned with the platform instead of fighting it.
Operations
prismVox has to read cleanly both as an app and as a controlled network service. The site now reflects that split instead of inviting generic sign-up traffic.
`prismvox.app` is the informational front door: product summary, policy pages, and support contact. No public sign-up path, no crossover with live API routing.
The shipping app targets dedicated public hosts for HTTP and WebSocket traffic, leaving the marketing site free of signaling concerns and deployment ambiguity.
Architecture
The product story matters, but the boundary design matters more. The site should make that architecture legible in a few seconds.
prismVox is intentionally split so the Node.js controller orchestrates the call experience without linking to GPL media code. Drachtio handles SIP signaling. RTPengine handles media. The app speaks to the controller and the controller speaks across sockets, not shared code boundaries.
SwiftUI iPhone app with CallKit, PushKit, WebRTC, and Speech-backed voicemail direction.
Tenant-aware Node.js controller for auth, routing, messaging, and signaling orchestration.
Drachtio for SIP signaling and provider integration.
RTPengine for packet handling and transcoding, isolated behind the service boundary.
Support
Use the policy links below or contact LaClair Technologies directly. This site is a product and policy surface, not a public sign-up page.