MYLINEHUB Architecture & Technology Stack

If you are building your own telecom + CRM product, the hardest part is not features — it’s keeping the system scalable, maintainable, and vendor-independent.

MYLINEHUB was designed as a decoupled telecom control layer + omnichannel CRM. Unlike tight-coupled dialers (legacy setups where Asterisk and dialer must live together), MYLINEHUB separates responsibilities so you can scale each part independently.

High-Level Architecture (What Connects to What)

1. Agents / Applications use the MYLINEHUB UI (Angular) or directly call APIs
2. MYLINEHUB Backend (Spring Boot) is the orchestration brain (CRM + workflows + dialer logic via AMI)
3. >MYLINEHUB Whatsapp is within MYLINEHUB Backend code. It is to build whats app AI chatbot, other automation needs
4. Asterisk / FreePBX handles real telephony (SIP, trunks, inbound/outbound call control)
5. VoiceBridge connects to Asterisk via ARI/Stasis for media/control (IVR, AI calling, click-to-call)
6. MYLINEHUB Email handles inbox polling + automation replies (works with any SMTP/IMAP)

This separation lets you run multiple Asterisk servers under one CRM, and avoids the “single-machine dialer” limitation common in older systems.

Why MYLINEHUB Is Different from Tight-Coupled Dialers (VICIdial-style)

Problem with tight coupling

• Asterisk and dialer logic are often installed together on the same box
• Scaling means “bigger server” instead of “more servers”
• Harder upgrades, harder failover, harder multi-tenant setup

MYLINEHUB approach (decoupled)

• Telephony stays telephony (Asterisk/FreePBX remains clean and stable)
• Business logic stays in CRM backend (campaigns, retries, callbacks, rules, reporting)
• Media/control extensions via ARI/Stasis (VoiceBridge adds IVR + AI calling + automation)
• Multi-Asterisk scaling becomes straightforward (add more boxes, bind from CRM)

Repository / Folder Structure (Technology Stack)

MYLINEHUB is organized as multiple projects so each part can evolve independently:

1) MYLINEHUB Backend (Java + Spring Boot)

• Purpose: CRM data, APIs, campaign logic, scheduling, workflow automation, reporting
• Why Spring Boot: stable production runtime, easy deployments, strong ecosystem
• Works with: PostgreSQL (and PGVector for AI features where needed)

2) MYLINEHUB Frontend (Angular + ngx-admin)

• Purpose: user UI for agents, admins, reporting, dashboards
• Base UI: ngx-admin (open-source admin framework)
• Why Angular: component structure + enterprise-friendly patterns for large UI

3) MYLINEHUB VoiceBridge (ARI / Stasis Media + Control)

• Purpose: IVR calling, click-to-call, AI calling, real-time media pipelines
• Integration: connects to Asterisk using ARI/Stasis
• Used for: AI conversations, bot audio streaming, custom call flows, automation triggers

4) MYLINEHUB Email Automation

• Purpose: connect to any SMTP/IMAP, poll inbox, trigger workflows, reply automatically
• Pattern: scheduled checks + queue processing + CRM logging

Asterisk / FreePBX Integration (ARI + AMI)

MYLINEHUB interacts with Asterisk using official interfaces:

• ARI (Asterisk REST Interface): modern call control + Stasis app integration
• AMI (Asterisk Manager Interface): operational events + control actions (where required)
• FreePBX: can be used as the management layer for Asterisk while MYLINEHUB stays non-intrusive

This keeps your PBX clean: you can still use IVR, queues, ring groups, and time conditions normally — while MYLINEHUB adds orchestration, reporting, and automation on top.

Omnichannel Concept (Not Just Dialing)

MYLINEHUB is not “only autodialer”. It’s an omnichannel CRM where calls, WhatsApp, email, and workflows can live in one customer timeline.

• Calls: inbound/outbound + recordings + reporting
• AI calling: VoiceBridge + bots for interviews, IVR automation, data collection
• Email: inbox polling + automated replies + CRM activity logging
• Workflows: scheduling, callbacks, retry logic, and custom API automations

Deployment Model (Why This Scales)

You can deploy in a clean scalable way:

• Backend + DB on one machine (or separate DB server for heavy loads)
• One or more Asterisk/FreePBX servers (scale horizontally)
• VoiceBridge near telephony servers (low latency for media/control)
• Frontend served via NGINX (or CDN)

As your customer base grows, you add more telephony servers without rewriting the CRM or workflows. This is exactly where tight-coupled dialers become painful — and decoupled architecture stays stable.

Who This Architecture Is For

• Businesses building their own telecom stack instead of renting vendor-only CPaaS
• Call centers that need scaling, data ownership, and stable call routing
• Teams that want to extend into AI calling, IVR automation, and omnichannel workflows
• Companies that want FreePBX simplicity + enterprise-grade orchestration

Next Steps

If you are setting up MYLINEHUB in production, follow the install series in the Knowledge Hub (Ubuntu install → PostgreSQL/PGVector → SSL → NGINX reverse proxy → systemd → logs/JMX/ulimit troubleshooting).

MYLINEHUB is designed to be extended: new channels, custom workflows, integrations, and AI pipelines can be added while keeping telephony stable and clean.