This FAQ is for the Telnyx Network IP range update that will phased in starting on November 1, 2026. Please see the Network Configuration support page for specific details. 

Questions & Answers

1. Why is this change being made, and what's the impact if we do nothing?

Telnyx is one of the voice communication vendors supporting Doximity Dialer. If your network already allows broad outbound traffic (not locked down to a strict allowlist), this change likely has no visible effect. If your network is strictly allowlisted, calls that route through Telnyx may already be experiencing intermittent connectivity issues without a clear cause — completing this update removes that risk going forward.

2. Is there a recommended validation or testing workflow after implementing the new IP ranges and ports?

This is an infrastructure allowlist update on your network side; Doximity and Telnyx are responsible for the reliability of the service itself. We recommend your team's standard change-validation process for firewall/allowlist updates (e.g., confirming the rule is live, then placing a few test Dialer voice calls). No special coordination with Doximity is required, but we're happy to hop on a call to validate together if useful.

3. Can these changes be applied live, or is a downtime window required?

No downtime window is required. This is an additive change — you're adding new entries to your existing allowlist, not removing or replacing anything. Your current Dialer setup will continue to function normally throughout.

4. Can you confirm whether the listed IP addresses/ports are outbound from us to you, inbound from you to us, or bidirectional?

Voice calls through Doximity Dialer are bidirectional by nature (audio needs to flow both ways between clinician and patient/caller). The listed IP ranges and ports should be allowed for outbound traffic from your network; return traffic on established connections is handled automatically by stateful firewalls in the standard way.

5. Which side initiates the connection — does our network initiate the session to Doximity/Telnyx, or does Doximity initiate a connection into our network?

Your network initiates the outbound connection to Telnyx's infrastructure. Doximity/Telnyx does not initiate inbound connections into your network. If your current setup already supports Dialer voice traffic, this update should be a straightforward addition to your existing outbound allowlist rather than a new category of firewall exception.

6. What services/functionality are impacted if this isn't completed before the deadline?

This affects Doximity Dialer voice calling specifically (Telnyx is used for voice, and in some configurations text messaging). Dialer Video (100ms/Twilio) is unrelated and unaffected by this update. If the allowlist isn't updated, the risk is degraded voice call reliability/connectivity — not a full outage, since existing traffic patterns may already be partially working — but we can't guarantee call quality or successful connection without the full allowlist in place.

7. Is there any flexibility on the deadline, or a way to get an exception while we go through our internal change control process?

We understand internal change-approval timelines vary. While we're setting ~Nov 15 as the target to ensure everyone completes this in a reasonable window, this is not a hard cutover like a vendor-mandated deadline — reach out to your CSM if your internal processes need more time and we'll work with you. That said, we'd recommend prioritizing it given the connectivity-reliability benefits.

8. Can you confirm the ports listed are necessary, and whether any PII/PHI risk is associated with them?

The required Telnyx ports (*.telnyx.com (HTTPS/443,3478 - UDP/443,3478 - TCP/443,3478) are used for real-time voice media transport. All Dialer voice traffic is encrypted in transit. No PII/PHI is transmitted in plaintext over any of the listed ports.