What Open Voice Shield does

A rule reads like a sentence: when probability is at or above a threshold and the recommendation is one you chose, block that calling number or divert it, for a window you set or permanently. The control applies at authorization, before routing, so a blocked ANI gets SIP 403 and shows in the CDR as blocked_by_rule. A controlled-numbers table lists every active control with its reason and expiry. One action releases it.

Rules match on minimum probability, category and recommendation, or on call quality, when the call's estimated MOS is at or below a ceiling you set, or on either. They deliver by e-mail to up to ten addresses, to a Slack channel in your own workspace, or both, throttle repeats and can attach the transcript. Every account is seeded with one enabled rule, probability 90 or above with a block recommendation, so the first dangerous call reaches you before you configure anything. Every attempt is recorded as sent, failed or skipped. How Slack alerts work.

Open a case from the call detail, title pre-filled from the analysis. Set severity, assign it to a user on your account, and work it through open, in review, resolved or dismissed with a comment thread. Creation, assignment and comments e-mail the people involved.

A completed analysis is POSTed to your endpoint, signed HMAC-SHA256 in X-OVS-Signature, with an X-OVS-Delivery id for idempotency. The payload carries call metadata, captured headers and the analysis, so you can drive your own switch from it.

A question, a problem, a feature you want, or a verdict you disagree with: open a ticket under Support, or press Report analysis on the call itself and the call comes attached, so a person can listen to it and check the verdict against the recording. Replies land in the portal and in your inbox, and the thread stays with the ticket.

The analysis checks the callee channel for a mid-call switch from interactive conversation to looping or non-responsive playback, the delayed-playback form of false answer supervision, where a vendor answers legitimately and later swaps the callee for a recording to keep minutes billing. A call showing that switch carries a route alert, distinct from the caller verdict, recommending the vendor serving that route be taken out of rotation.

Open Voice Shield is an ordinary SIP hop, so your dial plan can route a random share of traffic through it, one call in ten or twenty, instead of everything. Each sampled call is a complete evidence pack: recording, per-channel transcript, verdict, pcap and SIP ladder. How delayed-playback FAS detection works.

Match, modified (format, prefix or digits, so you know whether a carrier normalised the number or the route substituted it), withheld, missing, or not received when the route took the call but nothing reached the number. Beside it: post-dial delay, answer time, the SIP ladder and estimated audio quality of the call that carried the test. You pick a country and never see the number.

Repeat a check every few hours per route and country. A result other than match raises the Caller ID check failed alert by e-mail, Slack or webhook, so a route that starts stripping or rewriting caller ID is caught before your own customer complains. Countries not yet covered can be requested from the same page. How CLI verification works.

Coverage comes from real numbers in real countries, and the numbers can be yours. Point a number you own at the platform, prove it with one phone call, and every check that reaches it credits US$0.15 to your balance. Host a number.

Every INVITE is authorized by source IP against a per-tenant CIDR allow-list. There is no digest auth or registration, and REGISTER is answered 403. An unlisted source, a suspended account, an exhausted balance and a port limit each get their own SIP response code.

Routing rules match a leading prefix of the dialled number, longest match first, priority as tie-break. Each rule points at one of your destinations, which may carry a tech_prefix prepended to the Request-URI user before relay. With no rule: the whitelisted IP's destination, then the account default, then the source IP.

Named headers on the initial INVITE are captured onto the call. X-Customer-ID and X-Customer-Name ship configured, in indexed CDR columns you can filter by. Other configured headers go to a JSON map on the call, the webhook payload and the alert e-mail.

The authorization response carries a max_call_seconds computed from the prepaid balance. The proxy enforces it from the 200 OK and BYEs both sides on expiry, so a call cannot outrun the money that pays for it. Re-INVITEs cannot extend it.

Every ringing and answered call, live: ANI, dialled number, customer reference, routing, elapsed time, remaining credit. A port-bank faceplate shows one LED per licensed port. Click a lit port and a line inspector opens for that call: the SIP ladder as the proxy traces it, post-dial delay and codec the moment they are known, each media leg's packet rate, jitter, loss and reported MOS, and after hang-up the pipeline and the verdict landing in the same panel. Administrators see all tenants, with a per-customer summary.

A destination can be a voice AI agent reached as a SIP endpoint over TLS, so a screened call goes to an agent instead of a human queue. Two providers today, xAI and OpenAI, each with its own connection rules. An agent that challenges the call gets its own digest credential, stored sealed on the destination. Beta: exercised against test agents, and the agent leg is metered per second at a rate you can see on the call record. How to route to one.

Up to ten users on an account, as owners or members. Owners invite, deactivate and reactivate. An invited user gets a temporary password by e-mail and must change it at first sign-in. The audit log records the acting user, not just the account.

WebAuthn passkeys as an optional second factor. Register one or more, name them, see when each was last used, remove them. Removing the last turns two-factor off.

Every screen in the portal is a documented REST endpoint. Keys are bound to the user who minted them, revocable, and dead the moment that user is deactivated. The API reference lists every customer endpoint.

Recordings and captures stay on our disk, or move to an S3-compatible bucket we control after a set number of hours. Stored in Canada by default. An account can choose the United States instead, for storage and for the media relay, and Europe or another region on request (data location). Playback, download and export work the same either way.

Independent retention windows for recordings, pcaps and SIP logs. Zero means keep them. Expiry deletes the object, local or in the bucket. The call record keeps its metadata.

A scheduled gzipped database dump, written to a bucket or local disk at a time you set, keeping the last N. Backups list size and date, can be taken on demand, downloaded, and restored behind a typed confirmation.