Enterprise Session Border Controller (SBC) - Sangoma
The Sangoma Enterprise SBC is designed for medium to large organizations demanding high scalability, security, and seamless interoperability across diverse voice and data networks. Supporting 25 to 250 concurrent calls, it supports secure SIP trunking, encryption, and disaster recovery, ensuring business continuity and preventing eavesdropping during SIP sessions.
Key Capabilities
- Supports 25-250 concurrent calls: Suitable for medium to large enterprises.
- Encryption: TLS and SRTP encryption to secure voice traffic, preventing eavesdropping.
- Secure communication: Between IP phones, SIP trunks, and IP PBX systems.
- Transition support: Seamlessly switch between phone systems or SIP trunks.
- High Availability: Designed to maintain service even during catastrophic network events.
- Remote access: Connects remote users securely without VPNs.
Prerequisites
Before deploying the Enterprise SBC, ensure the following:
- Compatibility with existing IP PBX or VoIP systems.
- Sufficient network infrastructure capacity (bandwidth, QoS).
- Proper certificates for TLS encryption, if applicable.
- Administrative access to the SBC device for configuration.
- Knowledge of SIP network topology and policy requirements.
Deployment and Configuration
Basic Setup
- Hardware Installation: Mount the SBC hardware in the data center or server room following manufacturer instructions.
- Network Configuration: Assign static IP addresses and network interfaces.
- Initial Access: Connect via web interface or CLI using default credentials.
- System Updates: Apply latest firmware or software updates for security and performance.
Configuring Secure SIP Support
- Generate or import necessary TLS certificates.
- Enable TLS and SRTP protocols for call encryption.
- Define trusted certificate authorities and security policies.
Transition Between Phone Systems or SIP Trunks
- Define SIP trunks in the configuration.
- Configure routing rules to direct traffic accordingly.
- Enable failover and disaster recovery strategies for seamless transition.
Connecting Remote Users Securely
- Configure VPN-less remote access.
- Enable secure tunneling protocols like TLS and SRTP.
- Set policies for authentication and authorizations.
API and Command Line Interface (CLI)
The SBC offers RESTful API endpoints for automation and integration.
Supported Features in Detail
| Feature | Description |
|---|---|
| Call concurrency | Supports 25-250 simultaneous calls |
| Encryption | TLS for signaling, SRTP for media |
| Failover & redundancy | Transition support for outages, disaster scenarios |
| Remote endpoint security | Connect remote users securely without VPNs |
| Protocol support | SIP, standard protocols with compatibility assurance |
Security Considerations
- Always update to latest firmware to patch vulnerabilities.
- Use strong, unique certificates for TLS encryption.
- Restrict management access via ACLs and secure passwords.
- Enable logging and monitoring for detection of anomalies.
- Deploy high availability configurations for disaster recovery.
Troubleshooting and Support
- Refer to the datasheet and technical specifications for capacity planning.
- Use the web interface’s diagnostic tools and logs for problem diagnosis.
- Consult Sangoma support or your partner for complex issues.
- Review the help center articles for common deployment challenges.
Summary
The Sangoma Enterprise SBC is a vital component for securing and ensuring high availability of enterprise voice and video communications. Proper deployment, security configurations, and integration will provide your organization with a resilient, secure, and scalable communications infrastructure.