Components

The overal architecture is made of several individual components that need to be defined or connected to have and end to end feature. For instance, you need to define a zoom component in order to be able to place/receive calls through zoom phone.

In the rest of this documentation we usually talk about "core component" to talk about alphacom components while "external component" are component which must be defined and connected together with other components but are not developed by alphacom

CAS

CAS stand for Console Admin Service. This core component is administrative piece of the architecture and is made of 2 sub service.

CAS Backend

This is a REST/JSON service to wich all Nomad clients and other core components connect to in order to grab their configuration. As this component is bacisally an API, it can be leveraged by customers/third party product for automatic provisioning purpose.

CAS Console

CAS console is a simple admin user interface used to manually configure anything in the solution. This interface call CAS Backend API in order to populate the configuration in the CAS database. Nothing else than human administrators connect to the CAS console, no components use it directly.

CLB

CLB stand for Common Lamping Bridge. CLB is a core component sharing slots status and voice with Nomad PC and Nomad mobile. There may be more than one CLB in the architecture depending of Nomad user spread across multiple regions or for load/business continuity reasons. A CLB is made of 2 sub components

CLB service

The service dealing with signalisation, whatever the signalisation nature (SIP, SIPREC, etc.)

CLB matrix

The voice processing unit. A CLB can spawn as many matrix as needed by the load.

CLB Web Proxy

The Proxy service allowing the Nomads to reach out to the CLB directly from Internet without the risk of exposing the CLB on the Internet.

Note

When the Alphacom System is deployed behind an Application Gateway + WAF for added security, the App GW can play the role of CLB Web Proxy

Recording service

This external component can be either a SIPREC recorder or Cloud based recording service.

Communication service

This external component is used for routed or persistant slot type in order to integrate with an external voice platform. This communication service can be either a standard IP-PBX like Asterisk or more modern voice cloud based platform like Zoom or Microsoft Teams. This Communication service component would also be used to define a private wire gateway (SBC or Vega physical gateway)

DMR

This external component is used for radio integration. This component would use DMR as the main way to communicate with gateway allowing to reach out to Tetra, DMR or VHF/UHF radio handsets.

Precept

Precept groups together a serie of services bringing high added value to the Nomad. These services are not directly configured in the CAS but can be enabled via settings linked to the User Profile/template.

CLB Activity

Mandatory Precept Service that will process the CLB Activity events and provide the info/details to the other Precept Services.

History

Optional Precept Service providing the "History" feature to Nomad.

Presence Service

Optional Precept Service providing the "Presence" feature to Nomad.

Slots Service

Mandatory Precept Service providing the Slots status to the Nomad

Location Service

Optional Precept Service providing the "Location" feature to Nomad. Each user can then be tagged on the map.

Transcription Service

Optional Precept Service providing the "AI Monitoring Transcription" feature to Nomad.

Components requirements

Different components have some minimum requirements dependant on the environement in which they run (Azure vs on premises) or depending of underlying platform beeing used (iOS, android, windows)

Nomad

• Nomad PC need to run over windows 10 or 11. 64 bits OS.
• Nomad Android need to run on at least Android 9

Authentication

• Azure Active Directory is the main user authentication provider
• Alternativly a windows server 2019 or above can be used