PBX & Softphone Setup
Welcome to the didlogic Connectivity Directory. Our global network is built on open standards, ensuring seamless compatibility with practically any enterprise Private Branch Exchange (PBX), session border controller (SBC), or software-based dialer.
By utilizing your didlogic SIP credentials or configuring authorized IP authentication, you can immediately route high-concurrency voice traffic through our low-latency regional gateways.
Choosing Your Authentication Method
When connecting your infrastructure to didlogic, you will choose between two primary methods. Select the architecture that best fits your security and traffic requirements:
| Digest Authentication | IP Authentication | |
|---|---|---|
| Best For... | Dynamic IPs, softphones, and smaller offices. | Static data center IPs, high-concurrency call centers. |
| Security Type | Username & Password (SIP Register). | Trusted public IP address tracking. |
| Inbound Routing | Routes directly via the registered SIP account. | Requires pointing DIDs to a specific SIP URI. |
| Performance | Standard signaling overhead. | Ultra-low signaling overhead (highly scalable). |
Global Signaling Requirements
Regardless of which PBX software you use, ensure your corporate network adheres to our core network requirements to prevent one-way audio or dropped packets:
- Dialing Format: All outbound traffic must be presented in the clean E.164 format (e.g., Country Code + Area Code + Number, such as
12125550000). Do not pass local country prefixes like00or+directly to our gateways unless your outbound trunk dialplan strips them first. - RTP Audio Ports: Ensure your local firewall allows incoming and outgoing UDP traffic on standard audio ranges (typically UDP 10000–20000).
- Codecs: We prioritize
ulaw(G.711u) andalaw(G.711a) for crystal-clear, uncompressed carrier quality. Ensure these codecs are at the top of your PBX priority list.
Need Help with a Custom Switch?
If your enterprise utilizes a proprietary system or an SBC not explicitly documented here (such as Kamailio, OpenSIPS, or Sonus), our trunking architecture will still support it. As long as your platform is SIP-compliant, it can interface with our network.
Reach out to our technical engineering team at [email protected] for custom interoperability specifications or custom IP allocations.