Containerized Application Components

This table shows a list of the available containers in the jtel Container Stack.

CategoryContainerFunctionComments
DevOpsacd-task-runnerStack startup

The acd-task-runner is responsible for:

  • Making sure the file system is ready, installing a new file system for a new installation or retrieving new files for an existing installation when it is updated
  • Making sure the database is ready, installing a clean database for a new installation or retrieving and executing update scripts for an existing installation when it is updated
  • Performing tasks such as file system maintenance and database record deletion according to the retention policies setup on the customer system
  • Making the daily system backup and uploading this either to the azure WORM storage (jtel Cloud SaaS Infrastructure) or the customers SMB or NFS (On Premise installation)
DevOpsacd-vscodeVisual Code Server

Provides file system acccess for service personell

Databaseacd.dbmDatabase MasterThe master database container.
Databaseacd-dbsDatabase SlaveThe slave database container.
Web Accessacd-haproxyReverse Web Proxy ServerThe proxy server providing the https certificate and https offloading and load balancing / routing to the webservers and other https servers in the instance.
Web Accessacd-web-1 ... acd-web-NWebservers Portal Versions up to 3.xxThe webservers for portal versions 3.xx
Web Accessacd-portalWebservers Portal Versions from 4.xx

The webserver for portal version 4.xx

Telephonyacd-fs1FreeSWITCH Telephony Stack

This contains the SIP and RTP handling stack for the system:

  • Uses a modified FreeSWITCH version with some jtel specific code in the core
  • Contains jtel specific modules providing ASR and TTS functionality
  • Uses a jtel specific configuration with a very simple dialplan which allows the jtel Blazar application server to make all call handling and routing decisions
Telephony and Applicationacd-tel1jtel Blazar Application Server

This contains the application server software which:

  • Controls the FreeSWITCH (acd-fs1) instance handling all incoming and outgoing calls
  • Runs several background processes such as reporting subscriptions, sending emails, uploading files to FTP servers
Application acd-presPresence Connector and Aggregator

This container is responsible for monitoring extensions, users and presence in connected voice infrastructure:

  • Microsoft Teams Connector
  • NFON Connector
  • WellCOM Connector
  • Cisco Connector
Applicationacd-chatChat Server

The chat server application container providing web-chat and LLM chat functionality.

Applicationacd-imap-mail-daemonE-Mail Connector

The email connector application which retrieves emails from IMAP(S) and Office 365 / Exchange mailboxes.

Applicationacd-connector-innovaphoneInnovaphone Connector

Provides monitoring, presence and control functions for the Innovaphone PBX System.

AI and Botsacd-ai-pipeline-botAI Pipeline

Provides routing and pipelines to AI components in the infrastructure.

AI and Botsacd-summary-botCall Summarization

Provides call summarization services using LLM

AI and Botsacd-sentiment-botSentiment Analysis

Provides sentiment analysis using a custom model

AI and Botsacd-ragbotRetrieval Augmented Generation Bot and Vector Database

Provides a vector database and query endpoint for knowledge base documents and data used in the AI pipelines of the system.

APIacd-restREST API

Provides the jtel REST API endpoints.

Monitoringacd-dbm-exporterDatabase Monitoring

Monitors the database master and provides information to the central jtel monitoring and alarming system on the health and state of the database.

Monitoringnode_exporterHost Monitoring

Monitors the host system and provides performance metrics including:

  • CPU
  • RAM
  • disk and filesystem 
  • network
  • hardware statistics
  • process statistics

to the central jtel monitoring and alarming system.

MonitoringcadvisorContainer Monitoring

Monitors the containers in the stack and provides performance metrics per container including:

  • CPU
  • RAM
  • disk i/o 
  • network

to the central jtel monitoring and alarming system.

Monitoringdocker_state_exporterContainer Orchestration Monitoring

Monitors the state of docker objects:

  • Containers
  • Images
  • Volumes
  • Networks

providing the following metrics:

  • Running
  • Stopped
  • Restarted
  • Labels and Exit Codes

focusing on what exists and in what state and providing this information the the central jtel monitoring and alarming system.

Identity Managementoauth2-proxyIdentity Management and SSO

Provides single sign on capability to the following managment containers using Entra ID:

  • Visual Code Server
  • haproxy web front end

Not Containerizable Application Components

The following software components are not containerizable and must be run on a dedicated Windows VM in enviroments which require them:

CategoryApplicationFunctionComments
ApplicationTAPI MonitorPresence Connector and Aggregator for Legacy PBX Systems

TAPI is a legacy interface for monitoring and controlling old PBX systems and is only provided in a windows environment. 

Running the TAPI monitor application requires a dedicated windows machine to provide this functionality.



  • No labels