Overview

SMS Authentication connects your Cloud-PBX to external SMS providers (Twilio, Vonage, etc.) using API credentials. This allows your system to send and receive SMS messages through the provider's network.

What You'll Need:

• SMS provider account (Twilio, Vonage, Bandwidth, Plivo, or MessageBird)
• API credentials (Account SID, Auth Token, API Key)
• SMS-enabled phone number from provider
• Webhook URL access for inbound messages

Authentication Flow:

1. Create account with SMS provider
2. Obtain API credentials
3. Purchase/provision SMS phone number
4. Configure authentication in Cloud-PBX
5. Set up webhooks for inbound messages
6. Test sending and receiving

Supported Providers

Configuration Steps

1. Go to "Phone Numbers" section
2. Click "Buy a Number"
3. Select country/region
4. Filter by SMS capability
5. Choose number
6. Complete purchase
7. Note phone number (with country code: +15551234567)

Provider: Twilio
Account SID: AC1234567890abcdef1234567890abcdef
Auth Token: ••••••••••••••••••••••••••••••••
Phone Numbers: +15551234567, +15559876543
Status: ✅ Connected

https://your-pbx-domain.com/api/messaging/sms/inbound

Security Best Practices

Credential Management:

• Never Hardcode: Don't commit credentials to code repositories
• Use Environment Variables: Store credentials securely
• Rotate Regularly: Change credentials periodically
• Limit Access: Only authorized personnel can view
• Use Test/Production Keys: Separate credentials for environments

Webhook Security:

• Signature Verification: Validate requests from provider
• HTTPS Only: Never use HTTP for webhooks
• IP Whitelisting: Restrict to provider IP ranges (if available)
• Rate Limiting: Prevent webhook abuse
• Logging: Monitor webhook activity

Message Security:

• Encrypt at Rest: Store message history encrypted
• Encrypt in Transit: Use TLS/HTTPS for all API calls
• Access Control: Role-based access to messaging
• Audit Logs: Track who sends what
• Content Filtering: Prevent sensitive data in SMS

Provider Comparison

Troubleshooting

Authentication Fails:

• Verify credentials copied correctly (no extra spaces)
• Check account status (suspended, billing issue)
• Confirm API permissions enabled
• Test credentials via provider's API explorer
• Check for IP restrictions on API access

Phone Number Not Working:

• Verify SMS capability enabled on number
• Check number is active (not released)
• Confirm webhook configured correctly
• Test by sending from provider console directly
• Review number compliance (A2P registration may be required)

Webhook Not Receiving Messages:

• Verify webhook URL publicly accessible
• Check HTTPS certificate valid
• Review firewall rules (allow provider IPs)
• Test webhook endpoint with curl/Postman
• Check webhook URL configured in provider dashboard
• Review provider webhook logs

High Latency:

• Check provider status page
• Verify geographic routing (use local numbers)
• Review network connectivity
• Test with different provider
• Check for rate limiting

Advanced Configuration

Multiple Providers (Failover): Configure backup providers for redundancy:

• Primary provider for normal traffic
• Secondary provider if primary fails
• Automatic failover on errors
• Load balancing across providers

Number Pooling: Use multiple numbers for high volume:

• Distribute sends across number pool
• Avoid carrier rate limits
• Better deliverability
• Geographic coverage

Custom Sender IDs (International): Some countries allow alphanumeric sender IDs:

• "YourBrand" instead of phone number
• Better brand recognition
• Check country support
• May require registration

Next Steps

1. Configure Settings: Set up phone numbers, routing, and preferences in SMS Settings
2. Create Queues: Route SMS to appropriate teams in Message Queues
3. Test Thoroughly: Send test messages to various carriers
4. Train Team: Familiarize agents with SMS interface
5. Launch: Start customer communication via SMS