Telephony Servers Module Documentation
Table of Contents
- Module Overview (Technical)
- Module Overview (Commercial/Business)
- Module Overview (End User/Administrator)
- Configuration Sections
- Settings Reference
- Common Scenarios & Examples
- Limitations & Important Notes
- Troubleshooting Tips
- Glossary
---
1. Module Overview (Technical)
What Are Telephony Servers?
Telephony Servers is a FreeSWITCH server management module that configures connections to one or more telephony servers. It supports SSH authentication (password or key-based) and periodic health monitoring.
Architecture
Key Tables
| Table | Purpose |
|---|---|
public.telephony_servers | Server configurations |
Key Files
| File | Description |
|---|---|
modules/telephonyServers/ | Frontend module |
2. Module Overview (Commercial/Business)
Business Value
Telephony Servers provides multi-server management:
| Without Telephony Servers | With Telephony Servers | |
|---|---|---|
| Single server | Multiple servers | |
| Manual SSH | Automated connection | |
| Password auth | Key-based security | |
| No monitoring | Health checks |
Use Cases
- Multi-Server Cluster
- Distributed architecture
- Remote Servers
- Geographically distributed
- Server Monitoring
- Status dashboard
- Secure Access
- Passwordless operation
Feature Highlights
| Feature | Benefit | |
|---|---|---|
| Multi-Server | Manage cluster | |
| SSH Key Auth | Secure, automated | |
| Auto Key Install | One-click setup | |
| Health Checks | Monitor uptime | |
| Status Display | Online/Offline/Error | |
| Quick List | Fast server switching |
3. Module Overview (End User/Administrator)
What Can You Do?
- Add telephony servers
- Configure SSH connection details
- Generate and install SSH keys
- Enable/disable monitoring
- Set health check intervals
- View server status
- Check FreeSWITCH version
Telephony Servers Interface
Add/Edit Server
SSH Key Generation
Quick Tips
TIP
SSH Keys: Use key-based auth for automated operations.TIP
Monitoring: Enable to track server uptime.NOTE
Local Server: Local servers cannot be deleted.---
4. Configuration Sections
Basic Information
| Field | Description | |
|---|---|---|
| Server Name | Identifier (e.g., "FS Node 01") | |
| Description | Purpose notes | |
| Host | IP or hostname | |
| SSH Port | SSH port (default 22) | |
| SSH Username | Login user | |
| SSH Password | Optional password |
SSH Key Authentication
| Field | Description | |
|---|---|---|
| Generate & Install | Create and deploy SSH key | |
| Status | Key installation status |
Monitoring
| Field | Description | |
|---|---|---|
| Enable Monitoring | Periodic health checks | |
| Health Check Interval | Seconds between checks |
5. Settings Reference
Server Status Values
| Status | Icon | Description | |
|---|---|---|---|
| Online | ● Green | Server responding | |
| Offline | ○ Gray | Not reachable | |
| Error | ● Red | Connection error | |
| Unknown | ○ Gray | Not checked |
SSH Authentication Methods
| Method | Use Case | |
|---|---|---|
| Password | Initial setup | |
| SSH Key | Production (recommended) |
Health Check Intervals
| Interval | Use Case | |
|---|---|---|
| 30 sec | High availability | |
| 60 sec | Standard monitoring | |
| 300 sec | Low priority servers |
6. Common Scenarios & Examples
Scenario 1: Add Production Server
- Click "Add Server"
- Name = "FS Prod 01"
- Host = production server IP
- SSH Port = 22
- SSH Username = root
- Click "Generate & install SSH key"
- Enable Monitoring
- Health Check = 30 seconds
- Save
Scenario 2: Manual SSH Key
- Add server with password first
- Generate SSH key
- If auto-install fails, copy key
- Manually add to server's authorized_keys
- Clear password field
- Save
Scenario 3: Disable Monitoring
- Edit server
- Uncheck "Enable Monitoring"
- Save
- Server won't be health-checked
Scenario 4: Change Health Interval
- Edit server
- Set Health Check Interval = 60
- Save
- Checks now every 60 seconds
---
7. Limitations & Important Notes
Technical Notes
NOTE
Network Access: Server must be reachable from admin panel.NOTE
SSH Access: User needs appropriate permissions.WARNING
Local Server: Cannot be deleted (system server).Best Practices
- Use SSH Keys: More secure than passwords
- Enable Monitoring: Track uptime
- Descriptive Names: "FS-Prod-US-East-01"
- Dedicated User: Use non-root when possible
- Firewall Rules: Allow SSH from admin panel
SSH Key Benefits
| Benefit | Description | |
|---|---|---|
| Security | No password exposure | |
| Automation | Passwordless scripts | |
| Rotation | Easy key replacement | |
| Audit | Track key usage |
8. Troubleshooting Tips
Common Issues
| Symptom | Possible Cause | Solution | |
|---|---|---|---|
| Offline status | Server down | Check server | |
| SSH connection failed | Wrong credentials | Verify user/password | |
| Key install failed | SSH blocked | Check firewall | |
| Can't delete | Local server | Local cannot be deleted |
Test SSH Connection
Check Server Status
FreeSWITCH Status
---
9. Glossary
| Term | Definition | |
|---|---|---|
| Telephony Server | FreeSWITCH host | |
| SSH | Secure Shell protocol | |
| SSH Key | Public/private key pair | |
| Health Check | Periodic status verification | |
| Cluster | Multiple connected servers | |
| fs_cli | FreeSWITCH command line |
Lua Script Status ℹ️
Infrastructure Module
| Component | Status |
|---|---|
| Telephony Servers | ℹ️ Server management - no Lua handler required |
---
Documentation last updated: January 2026