Voice

A Class 5 softswitch, with a portal built around it

Voice on SWITCH/T isn’t a thin layer over someone else’s switch. The platform’s core is a Class 5 softswitch: it terminates calls, applies your access and routing rules, and runs the call-handling logic you build for each number, while the portal gives you live visibility into every call as it happens.

Live monitoring and call records

Every call is visible while it’s happening and afterwards. Live calls show caller, destination, duration, and current state; CDRs let you investigate inbound and outbound traffic after the fact, including disconnect and reason-code detail.

  • Live call monitoring with caller, destination, duration, and current state
  • Inbound and outbound CDR investigation
  • Missed-call tracking, with export
  • Call recordings where configured

Extensions and call centres

Extensions register directly with the softswitch, and their state — online, offline, on a call — is visible from the portal. Call-centre agents and queues sit alongside extensions, with their own reporting.

  • SIP extension management and registration state
  • Call-centre agents and queues
  • Agent, call-centre, and outbound reporting
Access control

Inbound and outbound rules

Before a call reaches your call-handling logic, it passes through access control: IP and source-based restrictions, number and pattern matching, blacklists, and time-of-day behaviour, so traffic that shouldn’t reach a number never gets the chance to.

  • Inbound and outbound access rules
  • IP and source-based controls
  • Number and pattern restrictions
  • Blacklists
  • Time-of-day service behaviour
  • Audio and announcement asset management
Service builder

Call-handling logic, built visually

A service is a reusable definition assembled on a node-based canvas, then assigned to any number of provisioned numbers. It’s a genuine visual programming surface for telecoms logic — not a form with a few dropdowns. Updating the service updates behaviour everywhere it’s assigned, while number allocation and billing stay managed separately in number inventory.

  • Create and manage reusable telecom services
  • Assemble call-handling logic by connecting nodes on a canvas
  • Reference customer records, extensions, and call-centre agents from within a node
  • Attach audio files for announcements, IVR menus, and on-hold audio
  • Reuse other services as building blocks
  • Save, clone, load, and reorganise service definitions
  • Assign a completed service to one or more provisioned numbers

Node types available on the canvas

Each node is a discrete piece of call behaviour. They range from simple building blocks, like a timed delay, to genuinely advanced capability like live transcription and managed-list operations that most call-flow builders don’t offer at all.

Start

Entry point for the service, with auto-answer and timeout options.

DTMF

Collects a fixed number of digits from the caller.

Menu

Plays an audio file and branches on the digit pressed, with configurable loop count and duration — the core of an IVR.

Playback

Plays a single announcement or audio file to the caller.

Audiocast

Streams a Shoutcast/Icecast station to the caller, for branded on-hold audio.

Record call

Starts call recording and can notify a given email address.

Transcribe

Transcribes a portion of the call and can watch for a keyword.

Agents

Routes to a call-centre agent drawn from your extensions.

Call centre

Routes into a call-centre queue.

Route

Routes the call to an allocated client or station.

Route (by client)

Routes to a specific customer record and DDI.

Checklist

Checks the caller against a managed list and branches on the result.

List add / delete / load / pause

Adds, removes, loads, or pauses entries on a managed list from within the call flow.

Results

Captures a value collected earlier in the flow for later use.

Sleep

Introduces a timed delay before the next node runs.

Notation

A note on the canvas for documenting the service — not executed.