By Simon Woodhead
We have a lot of new features in the pipeline and therefore rather than manage access to each one individually, we’re launching a beta programme. Accounts enrolled will see all services which have been made available in beta for early access. Requesting access for your account just requires a simple form, which is here.
First out the door is call recording, carrier-side. As mentioned before, we do not want your data, and therefore from day-one we’re enabling you to configure off-net AWS S3 storage. We’ll record your calls and push them immediately and securely to your storage. If it isn’t available, we’ll queue it and push it as soon as it is.
So, the first thing you’ll notice in the portal is a new ‘External Storage’ option where various end-points can be configured. We’re going to use these for way more than just call-recording so this is an important addition.
Settings should be pretty intuitive for anyone who has configured S3 before. When you configure your buckets AWS side, remember we only want basic write access though – we do not want to be able read your files or do anything else with them! You can create as many storage objects as you need, and give them meaningful names. We have only enabled AWS for now, but other S3-compatible destinations will follow soon and other protocols will be considered subject to demand.
Having set up some storage, you’re ready to enable call recording. In the portal, when configuring a trunk you’ll see a new checkbox ‘enable call recording’. Ticking this will require the selection of one of your storage buckets and trigger the recording of all calls in and out of that trunk. Simples.
As with other features, you can map as much traffic or as many numbers as you like to a trunk. A trunk will be mapped to a single storage bucket.
Give it a whirl and you should see files appear in your S3 bucket(s). They’ll also have rich meta-data about the recording.
All of this is of course API-first and documentation will be updated shortly. Likewise, we anticipate some rich webhook events for storage and recording which’ll be coming soon.
For the purposes of the beta we are not charging for call-recording but any trunks or numbers added for your testing will be charged in the usual way, as of course will calls. Needless to say, please use the beta features at your own risk and don’t build production services on this until it is out of beta! However, do please give it a whirl and let us have your feedback.
