Technical Specifications
Need to know what's under the hood? Here's a detailed look at the technical capabilities of your phone system - from supported audio formats to network requirements. Whether you're setting up integrations or just curious about the system's capabilities, you'll find all the technical details here.
Audio Codecs​
The system supports multiple audio codecs to ensure optimal call quality and compatibility:
| Codec | Sample Rate |
|---|---|
| OPUS | 48000/2 |
| G722 | 8000 |
| PCMU | 8000 |
| PCMA | 8000 |
| G729 | 8000 |
| GSM | 8000 |
The system also supports telephone-event for DTMF transport, ensuring reliable touch-tone functionality during calls.
DTMF Support & Third-Party Integration​
DTMF Tone Recognition​
The FlyNumber phone system fully supports DTMF (Dual-Tone Multi-Frequency) signaling through the telephone-event codec, which is essential for:
- Navigating IVR menus
- Entering PIN codes or passwords
- Confirming selections with button presses
- Responding to third-party service prompts
Third-Party Platform Requirements​
When integrating with third-party services that require DTMF input (like call verification systems or interactive platforms), ensure the following:
| Requirement | Description |
|---|---|
| Telephone-Event Codec | Must be enabled in the third-party's SDP (Session Description Protocol) signaling |
| Codec Negotiation | Third-party platform must properly negotiate DTMF codec during call setup |
| DTMF Transport Method | RFC 2833/RFC 4733 compliant telephone-event payload |
Troubleshooting DTMF Issues​
If button presses aren't working when receiving calls from third-party services:
- Verify the issue: Test DTMF tones with other services to confirm FlyNumber is sending tones correctly
- Contact third-party support: Provide them with this technical information:
- They need to add/enable the telephone-event codec in their SDP signaling
- The codec is required for DTMF tone recognition
- The issue must be fixed from their call origination point
- Common symptoms:
- Pressing buttons doesn't trigger expected actions
- IVR prompts repeat as if no input was received
- Call connects but button commands are ignored
If a third-party service cannot detect your button presses, the issue is typically on their end, not with your FlyNumber. The FlyNumber system correctly sends DTMF tones when the receiving platform is properly configured.