Talk to a person

Contact Open Voice Shield

Email support@telecomsxchange.com to reach the team that builds and runs Open Voice Shield: volume or custom pricing, a security or vendor review, invoices or annual terms, private connectivity, or a walkthrough on a call.

Open Voice Shield is built and operated by TelecomsXChange. The same team answers this address.

Fifteen minutes

Book a setup call

We add your route with you, place a test call, and you see the first verdict before we hang up.

Or e-mail support@telecomsxchange.com with the switch you run and a time that suits you.

Five reasons operators write first

What to write about

Each link opens a mail to the same address with the subject already set, so it lands with the right person reading it.

Volume or custom pricing

The published plans on pricing run to a fixed number of concurrent ports and a fixed included-minute allowance. Beyond that, the rate and the port count are a conversation. Pilots are available on request rather than automatically.

Email us about volume pricing

A security or vendor review

The controls we operate are written out on security and in the security documentation. If your review needs a questionnaire completed, a data-flow description or a call with whoever owns the architecture, ask.

Email us about a security review

Procurement and invoicing

Self-serve billing is prepaid against a balance. A purchase order, an invoice, annual terms or a signed contract is handled by people, not by the sign-up form. Tell us which of those your process needs.

Email us about procurement

An on-premises licence

For operators whose call content cannot leave their own network. The platform runs on hardware you operate and you bring everything else: your own speech-to-text and analysis providers under your own keys, or models on your own hardware, your own storage and retention. Our part is the software and its upkeep. Licensed and priced per operator. Say where the hardware lives, which providers you intend to use, your peak concurrent calls and what your security review needs.

Email sales about an on-premises licence

Network, regions and connectivity

Questions about private connectivity instead of the public internet, about which region carries your media, or about several sites sending to one account, are answered case by case. The default path is described on how it works.

Email us about connectivity

Anything else, including a walkthrough of the console on a call, ask for a walkthrough.

Make the first reply useful

What to put in the mail

We can quote and scope from these five facts. Without them the first reply is a list of questions instead of an answer.

Expected concurrent calls
Peak simultaneous calls you want screened, and roughly how many analyzed minutes a month. Concurrency sets the port count, and minutes set the rate.
What sends the calls
The switch, SBC or platform the trunk leaves from, and whether a B2BUA sits in front of it. Open Voice Shield is an additional SIP hop, so it works either side of one.
Where the traffic is
The regions your calls originate and terminate in, and the source IP ranges the INVITEs come from. Authentication is by source-IP whitelist.
Your timeline
When you want traffic flowing, and whether a security review or a purchase order has to clear first. Those run in parallel with the technical setup.
Anything already decided
An AI provider you are required to use, a retention window you have to meet, or a destination the screened calls must land on. All three are account settings.

Or start without us

The product is self-serve. You do not need a call to put a real call through it.

Creating an account needs no card, and there is nothing to install. You whitelist the IP your switch sends from, point a trunk at the ingress and place one test call.