1&1
1&1
Status:
sip.1und1.de is normally a registrar/termination host, not evidence of external FQDN forwarding. No verified global source list is included. Action: confirm product support, sent DID format, and all signaling sources with 1&1.Plusnet / Fonial
Plusnet / Fonial
Status: supported, with a dedicated setup that splits outbound (a Fonial SIP user) from inbound (SIP-URI forwarding), and requires Fonial’s paid PLUS plan. See the Fonial guide for the full walkthrough.
Localphone
Localphone
Status: a
localphone.com endpoint alone is not a verified inbound profile. Action: confirm external SIP-URI routing, DID format, transport, and signaling sources with Localphone.i-pbx
i-pbx
Status: the hostname can identify a PBX or reseller; no global list is verified. Action: identify the actual operator and obtain account-specific public signaling addresses.
DIDWW
DIDWW
Use the DIDWW guide to assign a DID to an inbound SIP trunk and configure the separate outbound trunk.
Zadarma
Zadarma
See the Zadarma guide for API keys, automatic import, manual direct SIP and PBX forwarding. Use the signaling list for the selected path.
sipcall
sipcall
RingCentral
RingCentral
Amazon Chime SDK Voice Connector
Amazon Chime SDK Voice Connector
Follow the Amazon Chime SDK Voice Connector guide for AWS number assignment, encryption, and regional signaling sources.
Placetel
Placetel
Peoplefone
Peoplefone
Sipgate
Sipgate
Voxbi / Mixvoip
Voxbi / Mixvoip
Status: no current provider-to-platform authentication profile is documented here. Action: identify the exact product and region, then obtain the current FQDN-routing method and complete signaling sources from the provider or account portal.
TeamFON / TeamsIP
TeamFON / TeamsIP
Status: a saved hostname or credential mode is not proof of downstream Digest support. Action: confirm the account’s external SIP destination support, DID format, transport, and current public signaling sources.
Required confirmation
Ask whether the DID can be delivered to an external FQDN without REGISTER; the exact DID format in the Request-URI; whether the provider authenticates toward the destination with Digest and where those origination credentials are set; otherwise all signaling CIDRs and failover regions; TCP 5060 or TLS 5061; and whether SRTP is required. Only an external call with a platform inbound record, the assigned assistant, and two-way audio confirms the integration. Reject allowlist entries that contain prose, placeholders, hostnames, or unrelated public resolvers such as8.8.8.8. A provider network written without its CIDR prefix is only one host and must not be silently expanded or corrected.
Sources: DIDWW, Fonial, Amazon Chime, Zadarma, sipcall, RingCentral, Placetel, Peoplefone, NFON, Sipgate. Accessed 22 August 2026.