Documentation

Data location

Recordings and media captures are stored in Canada by default. Under Account > Data location an account can choose the United States instead, for storage and for the media relay that carries its calls. Call records, transcripts and analyses stay in the platform database in Canada whatever the choice.

What the choice covers#

The hosted service runs in Canada, and the media of your calls is stored there by default. Data location lets an account choose the United States instead, for two independent things:

• Recordings storage: the region the two-channel recording and the media capture of each call are written to. Canada (Central Canada, Montréal) or the United States (US East, Northern Virginia).
• Media relay: the region whose media relay carries the audio of your calls. Canada, or the United States. The portal shows which regions are available.

Other regions. Europe, or any other region our cloud runs in, can be enabled on request for both the media relay and storage: write to support@telecomsxchange.com. Once a region is enabled it appears on the card like the others, selectable per account.

Whatever you choose, call records, transcripts and analyses stay in the platform database in Canada. The choice is about the media of your calls, not about the account. Each call keeps the regions it was made with on its record, so a later change never moves a call's media.

How to choose#

Sign in to the portal, open Account from the left navigation, then Data location. The card shows the two choices with the region each is set to:

• Recordings storage: Canada or the United States, or another region enabled for your account on request.
• Media relay: Canada or the United States, or another region enabled for your account on request.

Pick a region for each and press Save. A region the platform cannot serve yet, because there is no storage or no relay there, is listed but cannot be picked, and the API refuses it with a 422. The change is written to the account's audit log with the acting user, like every other account setting.

What changes, and when#

• Storage applies from the moment you save. Calls authorized after the save write their recording and capture to the chosen region. Recordings already stored stay where they are: they play back, download and export as before, and expire on their normal retention windows in the region they were written to.
• The relay applies to new calls. A call already up finishes on the relay it started on. From the next call, the media is anchored on the relay of the chosen region.
• Your SIP ingress address does not change. Your switch keeps sending calls to the same address. The media address is offered in the SDP of each call as it is today. If your firewall restricts where RTP may go, allow the relay range of the chosen region as well.
• Nothing else changes. Retention windows, playback, the evidence bundle, share links and the API work the same in both regions.

What stays in Canada#

The platform database is in Canada, and it holds everything about a call that is not its media:

• Call records: numbers, addresses, timings, the route and the billing of each call.
• Transcripts and analyses: the conversation text, the verdict, the red flags and the quality figures.
• The ledger: every charge and top-up on the account.
• The audit log: every administrative action, including the data location change itself.

Where a stage of the analysis is sent to a cloud speech-to-text or analysis provider, the call record marks that stage as cloud, as described on the security page. The data location choice does not change that.

The API#

The same choice is one endpoint: GET /customer/data-location reads it, PUT /customer/data-location changes it. Both answer the current data_region (storage) and media_region (relay), "ca" or "us", and a regions list that says what each region can do today. GET /auth/me carries the two fields as well.

# what the account is set to, and which regions are available
curl -s https://ovs.telecomsxchange.com/api/customer/data-location -H "X-API-Key: $OVS_KEY"

{
  "data_region": "ca",
  "media_region": "ca",
  "default_region": "ca",
  "regions": [
    {"code": "ca", "label": "Canada", "detail": "Central Canada (Montréal)",
     "storage_available": true, "media_available": true},
    {"code": "us", "label": "United States", "detail": "US East (N. Virginia)",
     "storage_available": true, "media_available": false}
  ]
}

# a partial update: storage to the United States, the relay unchanged
curl -s -X PUT https://ovs.telecomsxchange.com/api/customer/data-location \
  -H "X-API-Key: $OVS_KEY" -H "Content-Type: application/json" \
  -d '{"data_region":"us"}'

A region whose storage_available or media_available is false is refused with 422 data_region_unavailable or 422 media_region_unavailable. The API reference lists the endpoint with the rest of the account group.

Frequently asked questions#