Telecom

We do buy them, and that would be easy enough to check. The reach in 94 countries is wholesale capacity we carry under our own contracts. What is ours is the switch: the PBX runs on our own machines, signalling and media both terminate there, and because we never hand two endpoints off to talk directly, the audio passes through our platform on every call. The record of it lands in our own database rather than a supplier portal. DIVERSITY is a European company with no parent company, US or otherwise, so there is no entity above us for an order from outside the EU to be served on. A call that reaches the public network is on the public network, and nobody can sell you sovereignty over that part.

94, counted from the inventory we actually hold, not from a marketing page. Local, national, mobile, toll-free, shared cost and UIFN, depending on what each country offers. If the country you need is not one of the 94, we will tell you that on the call rather than after the contract.

In 41 of those 94 countries. The gap is the kind of thing you want before you plan a cutover, not during one. Requirements vary by country, from an ID document to a company stamp on the letter of authority, and some countries will only port to a business entity. Porting is self-service, handles up to 50,000 numbers in one request, and runs in a window you pick within each country's lead time, with an alert at each stage.

If they speak SIP over TLS, yes. We run G.722 and A-law, with RFC 4733 for DTMF, and each extension registers one device at a time. Desk phones, softphones and mobile clients all register the same way. Bring the handsets to the call and we will tell you before you order, not after.

An auto-attendant with as many levels as the call flow needs, retries that fall through to voicemail instead of a dead line, and ring groups that ring together or one after another across desk phones and mobiles. Queues with the distribution strategy you pick rather than the one on our own switchboard, music on hold, wait and position announcements, and an overflow destination when the wait runs long. Opening hours, out-of-hours and a holiday calendar set per number, plus language and timezone per number, which is what lets numbers in several countries answer correctly from one system. Blind and attended transfer, call forwarding, and busy-lamp presence so a handset shows who is on a call. Voicemail lights the message-waiting indicator and arrives as an email with the audio attached. Conference rooms and T.38 fax are both available on request, and neither is switched on by default. Ask for them at the point you need them rather than assuming they are there.

Three ways in. Your application connects to our SMSC over SMPP, which is the path for volume; we connect to yours over SMPP, mainly for inbound; or you use the JSON API over HTTP, which is rate limited and is the wrong path for bulk. Ask us for the exact rate before you size a campaign. We can group SMS trunks for redundancy and load balancing. Sender IDs are a long code, an alphanumeric name, or a carrier sender ID for time-sensitive alerts and one-time passcodes, and A2P traffic needs the sender ID registered first, which for a short code can take up to a month. Delivery receipts come back by callback with the carrier status and timings. A message is 160 characters in GSM-7, or 70 in UCS-2 when the text uses characters GSM-7 does not cover, including some accented letters. We support US 10DLC campaign registration if you need it. Opt-out is yours to run: an opt-out reply such as STOP reaches you as an inbound message like any other, and we do not suppress the number on your behalf, so wire it into your own send path before you start.

Recordings are files on our own storage. Call records are rows in our own database, written as each call ends rather than batched overnight, and unanswered calls are written too, so a missed call is in the data within seconds and a queue that is losing people is visible the same day. There is no vendor portal in between that we log into on your behalf.

We capture RTCP statistics per call leg, including the estimated MOS, and log them against the call's linked ID. So when somebody says Tuesday afternoon sounded bad, the question is which leg and how bad rather than a request for a description.

99.9% product availability, by contract, with automatic credits if we miss it. It is a company-wide figure covering every product we tie to an SLA, and we will not borrow a supplier uptime figure to make it look better. What it measures is the product being available. It does not cover the public telephone network past our handoff, because no single operator runs it end to end, and nobody can promise it.

2 to 35 days, and it is a per-country fact rather than one number: a single published figure would be wrong in both directions. The fastest countries turn round in under a week and the slowest run past a month, so the date you plan the cutover on comes from the specific numbers you hold. Tell us the list and you get the dates before you commit to anything.

Porting in is free today, in most of the countries we port in. A few countries and some mobile ranges are quoted instead, and a complex port is always quoted, so ask before you plan around it. That is a current offer rather than a contract term: we are choosing to make it and we will say so plainly if it changes. Porting out carries a standard per-number processing fee.

Yes. Porting out is possible at a standard per-number processing fee, and requirements vary by country the same way they do on the way in. The argument for moving to us only works if moving away again is easy. A number you cannot take with you is a number you would have to ask every customer to update.

Yes, on every leg. Every endpoint we operate is SIP over TLS, and the media is SRTP with SDES keying: your phones to our platform, our platform to the carrier. It is not end to end, and that is a design decision rather than a gap. We are in the media path on every call by design, which is what lets us record, queue and route one at all, so the encryption runs to us and from us. SDES also carries its keys in the session description, which is why the TLS underneath is not optional: it is what protects them.

The US CLOUD Act lets American authorities compel any provider under US jurisdiction to hand over data in its possession, custody or control, wherever it is stored, without notifying you. On a phone system the data in question is who called whom, when, for how long, and sometimes the recording itself. DIVERSITY has no US parent: no US company owns or controls us, so there is no entity above us for such an order to be served on.

We can, under European law, on a European order, and that is the whole list. The records are in a database we run in our own datacenters, not in a platform we resell, so there is no second company holding a copy of these records and no portal operator who could be asked first.

The numbering path does not. We consume it through Amsterdam and nowhere else, so the route between our platform and the public network stays in Europe. Calls between your own extensions stay on our platform and never reach the public telephone network. What obviously does leave is a call to a number outside Europe, because that is where the person is, and no provider can honestly claim otherwise. What we can promise is that the leg we operate, and everything we record about the call, stays here.