SIP Trunking FAQ
Technical FAQ for Apeiron Enterprise SIP Trunking deployments.
Calling and Numbering
How do we place outbound calls using Apeiron?
Outbound calls can be initiated through:
- SIP interface to an Apeiron SIP trunk group
- API-driven voice workflows where applicable
Apeiron can validate route behavior during onboarding and test windows.
How do we receive inbound calls?
Inbound call delivery is supported through provisioned DIDs and toll-free numbers. Calls can be routed to:
- SIP trunk endpoints
- SBC instances or virtual ports
- Feature services (for example voicemail or forwarding scenarios)
- API/web service-controlled logic where configured
Which dialing formats are accepted?
Apeiron prefers E.164 for outbound dialing. Depending on configuration, 1+ and 10-digit formats can also be accepted.
Default inbound presentation is typically 10-digit DNIS/ANI for North American routing unless custom normalization is configured.
Protocol and Media Support
Does Apeiron support TLS and SRTP?
Yes. SIP signaling encryption via TLS is supported, and secure media options (including SRTP) are available based on trunk configuration.
Does Apeiron support T.38 faxing?
Yes. T.38 can be enabled on compatible trunk groups. For mixed voice/fax environments, Apeiron often recommends a dedicated T.38 trunk group to simplify routing and quality tuning.
Which codecs are supported?
Common supported codecs include:
If you require additional codecs, review that requirement with Apeiron engineering during solution design.
Is transcoding supported?
Yes. Transcoding options are available and should be aligned to your interop and quality requirements during provisioning.
Which DTMF methods are supported?
Apeiron supports:
- Inband
- RFC-2833 (RTP events)
- SIP INFO
Testing and Implementation
Will Apeiron test with our team during deployment?
Yes. Apeiron supports technical validation before production cutover, including integration checks and targeted failover/DR testing windows when needed.
What should we provide before onboarding?
Typical onboarding details include:
- Source signaling IPs/FQDNs and target endpoints
- Preferred transport and security profile (UDP/TCP/TLS, SRTP)
- Codec and DTMF expectations
- Call routing policy (inbound/outbound patterns, failover behavior)
Providing these early reduces turn-up time and rework.
Operations and Support
How do we request changes or support?
Use the Apeiron Dashboard support workflow for:
- Configuration changes
- Incident reporting
- Capacity and routing updates
- Scheduled testing coordination
Does Apeiron support failover and resilience testing?
Yes. Planned resilience testing can be coordinated with Apeiron to validate trunk behavior under failover scenarios and maintenance events.
Related Resources