Configuration scope
Noise suppression can be configured at two levels:- Connection level: Applied to all phone numbers associated with the SIP connection. This setting overrides individual number configurations.
- Number level: Applied to specific phone numbers for granular control.
Connection-level settings take precedence over number-level configurations, simplifying management and ensuring consistent audio quality across all calls.
Configuration via API
Configure at connection level
PATCH /v2/ip_connections/ with thenoise_suppression object:
Configure at number level
PATCH /v2/phone_numbers//voice with thenoise_suppression object:
Supported engines
Use thenoise_suppression_engine parameter to select an engine. If omitted, Denoiser is used.
For SIP trunking, Denoiser and Krisp Viva Tel Lite are the most common choices. Use
Krisp Viva Tel Lite when you need to isolate the primary speaker from background voices.
Direction options
Thedirection parameter controls which audio streams are processed:
Codec compatibility
Noise suppression works with standard SIP trunking codecs including:- G.711 (μ-law and A-law)
- G.722
- Opus
Performance considerations
- Each direction (inbound/outbound) is processed and billed independently
- Processing adds minimal latency (typically < 20ms)
- Noise suppression is applied in real-time during the call
- Connection-level configuration provides consistent behavior across all numbers
Best practices
- Use connection-level configuration for consistent audio quality across all phone numbers
- Enable bidirectional suppression (
both) for optimal results in noisy environments - Test with your specific use case to balance noise reduction with audio naturalness
- Monitor call quality metrics to validate the impact on your application