Answers from our carrier team

A DID (Direct Inward Dialing) number is a real telephone number assigned to your organisation without requiring a dedicated physical line for each number. Calls placed to the DID are picked up by our network and delivered to your SIP endpoint, PBX, or contact centre over an IP trunk. This lets you present a local presence in a market without any physical infrastructure in that country.

We provision local, national, and mobile-range DIDs across 90+ countries, with toll-free numbering available in a further set of major markets. Coverage depth varies by country — some markets offer city-level area codes, others are national-only. Send us your target city list and we will confirm exact availability and the number type available in each.

For markets with no regulatory documentation requirement, numbers are typically activated within a few hours of order confirmation. Markets that require address proof or a local presence declaration usually complete in two to five business days, depending on how quickly the regulator or underlying carrier processes the submission.

Yes. We support number portability in every market where the local regulator permits it. You will need to supply a recent invoice from your losing carrier, a signed letter of authorisation, and the account details held by that carrier. Porting windows are set by the local regulator and generally run from a few days to several weeks.

In many markets yes — we can enable two-way SMS on eligible DID and mobile-range numbers. SMS capability is country-specific and is not universally available on landline-range numbers. We will flag SMS eligibility per number range at the quoting stage.

Requirements are set by each national regulator, not by us. Common requirements include a company registration certificate, a proof of address in the country or region of the number, and an end-user declaration. A number of markets have no documentation requirement at all. We provide a per-country checklist before you place the order so there are no surprises.

By default each DID carries two concurrent channels, which suits most inbound use cases. Higher concurrency is available on request and is provisioned at the trunk level rather than per number, so a contact centre pointing hundreds of DIDs at one trunk can burst well beyond the per-number default.

Premium routes terminate directly on tier-1 operators or their nominated wholesale arms, with full CLI delivery, low post-dial delay, and contractual quality commitments. Standard routes traverse additional wholesale hops to reach a lower price point, trading some ASR and CLI consistency for cost. Most customers run a blended profile — premium for retail-facing traffic, standard for price-sensitive volume.

On premium corridors we target post-dial delay under two seconds and answer-seizure ratios in line with the destination's natural rate. Actual figures depend heavily on destination and your own dialling patterns — a market with high mobile penetration behaves very differently from a rural fixed-line market. We publish per-destination quality profiles to active customers.

We support full CLI-guaranteed routes and will pass your presented calling line identity end to end where the destination operator accepts it. Non-CLI and CLI-random routes are available on selected destinations, subject to the regulatory position in that market and to our acceptable use policy.

Each destination prefix carries a ranked list of carrier options scored on price, recent ASR, recent PDD, and current capacity. Our switch selects the highest-ranked route that meets the quality profile assigned to your account, and automatically fails over to the next option when a route degrades or rejects. You can pin specific destinations to a quality tier rather than accepting the default ranking.

G.711 (A-law and µ-law) and G.729 are supported across the network, with G.722 and Opus available on selected IP-to-IP corridors. We transcode where an intermediate carrier requires it, though we prefer to negotiate a pass-through codec to preserve voice quality and reduce latency.

A SIP trunk is an IP connection between your telephony system and our network that carries voice calls in place of traditional ISDN or PRI circuits. Any organisation running an IP PBX, a UCaaS platform, or a contact centre dialler needs one. It replaces fixed physical circuits with capacity you can scale up and down on demand.

There is no hard architectural ceiling. Trunks are commonly provisioned from 10 channels for a small office up to several thousand for a dialler operation, and burst capacity can be arranged for campaign peaks. We size the trunk against your busy-hour call attempts rather than your headcount.

Yes. Signalling can be secured with SIP over TLS 1.2 or 1.3, and media with SRTP. We also support IP access control lists and digest authentication. Encryption is available on all trunks at no additional charge, and we recommend it for any trunk traversing the public internet.

Trunks terminate on geographically separated session border controllers, so the loss of one point of presence does not take your service down. On your side we support multiple registered endpoints or a DNS SRV record with weighted targets, and we will re-route inbound traffic to a secondary destination automatically if the primary stops responding.

Yes. We interoperate with all mainstream session border controllers and softswitches, and we are happy to work through the interop with your vendor's support team during turn-up. If you would rather not run an SBC at all, we can deploy and manage one on your behalf as part of a custom infrastructure engagement.

A2P (application-to-person) messaging is sent by a system to an end user — marketing, alerts, and notifications. P2P is conventional person-to-person messaging. OTP is a subset of A2P carrying one-time passcodes, which is latency-sensitive and routed over dedicated high-priority corridors. Operators price and filter these categories differently, so declaring your traffic type accurately matters.

Both. High-volume senders typically take direct SMPP 3.4 binds with configurable transmit, receive, and transceiver sessions. For lower volumes or simpler integrations, our HTTP REST API covers submission, delivery receipts, and inbound message retrieval without any persistent connection to maintain.

Delivery receipts are returned on the same SMPP bind that submitted the message, or delivered to a webhook URL you nominate when using the HTTP API. We pass through the operator's final status where available and normalise intermediate states so you get a consistent view across corridors.

Sender ID rules are set nationally and vary widely. Some markets allow free alphanumeric sender IDs, some require pre-registration of every sender ID with the regulator, and some overwrite whatever you send with a shortcode. We maintain a live per-country sender ID matrix and will register IDs on your behalf in markets that require it.

There is no universal minimum. Wholesale voice interconnects are usually structured around a monthly commitment that unlocks a rate tier, while enterprise SIP and DID services are typically sold without a volume floor. We will size the commercial model around the traffic you actually expect rather than pushing you into a tier you cannot fill.

New accounts generally start on prepay with real-time balance monitoring and configurable low-balance alerts. Established customers with a payment history can move to postpaid billing on weekly, fortnightly, or monthly cycles subject to a credit review. Invoices are itemised down to destination level with full CDR access.

From signed agreement to live traffic is usually two to five business days. That covers commercial setup, IP whitelisting, trunk provisioning, and a joint test window. Deployments requiring regulatory documentation, number porting, or a bespoke SBC build take longer and we will give you a dated plan up front.

Every account has access to our 24×7 Network Operations Centre. Wholesale and enterprise accounts are additionally assigned a named account manager and an escalation path into senior engineering. We target a sub-15-minute first response on service-affecting incidents at any hour.

Traffic is monitored continuously for the usual fraud signatures — international revenue share, Wangiri call-back patterns, sudden destination shifts, and abnormal short-duration ratios. Suspicious patterns trigger an automatic route block and an alert to both sides. Billing disputes are worked against matched CDRs, and we will credit confirmed errors on the next invoice rather than arguing them out over months.