Anveo Direct SIP trunking: IP identity, SIP-URI failover and direct carrier media

Model outbound and inbound identity independently

Anveo Direct states that it does not support SIP REGISTER. Outbound call termination uses source-IP authentication, and each configured trunk can have its own authorized address and LCR controls. Inbound DID calls are sent to a configured SIP URI. Record the outbound trunk, authorized public address, DID, primary URI and PBX listener as separate objects.

A successful outbound call proves that one source address and route were accepted. It does not prove that a DID targets the intended URI, that an inbound INVITE reached the PBX or that the optional backup URI is eligible.

Separate signaling sources from direct carrier media

The FAQ publishes four signaling source addresses and says Anveo Direct does not proxy RTP. Its network and inbound pages describe media going directly from the underlying carrier or Voxbone path to the customer destination. A signaling allowlist is therefore not an RTP allowlist.

Preserve the INVITE source, SDP connection address and ports, observed RTP source and destination, PBX media address, negotiated codec and decoded two-way audio independently. Do not assume that a packet from an unfamiliar carrier address is hostile or that opening every Internet RTP source is safe; derive a bounded policy from current account and incident evidence.

Treat backup SIP URI as an optional provider route

The FAQ says a Failover Add-on can forward an inbound call to a backup SIP URI when the main server is down. That proves the product exists, not that every DID has it, that one specific failure qualifies, or that the provider attempted the backup. Export the affected DID, add-on state, primary URI and backup URI before testing.

The reviewed pages do not publish one universal health signal, final-response list, timer, retry count or restoration interval. Record the primary attempt or absence, response, elapsed time, backup attempt, customer-edge receipt and caller outcome instead of importing another carrier’s failover rules.

Keep inbound failover apart from outbound LCR

The outbound termination page describes selectable carriers, route blocks and outbound failover controls inside LCR. Those are not the same as a DID moving from a primary to backup SIP URI. Identify the direction, object and selected carrier policy before interpreting a second attempt.

The current FAQ and termination page publish different carrier-count snapshots. Preserve that disagreement as dated marketing language rather than a stable route inventory, capacity measure or quality result.

Read codec, fax and channel statements narrowly

Anveo Direct says media codec is negotiated directly between the customer server and the selected carrier and that most carriers support G.711 and G.729. Its inbound page marks T.38 in most countries and describes ten dedicated incoming channels on the per-minute plan while Prime separates numbers and channels.

These statements do not prove one route’s codec, fax result, call-start capacity or universal concurrency. Preserve offer and answer SDP, selected route, fax mode, active calls and new-call rate separately.

Test without inventing resilience or weakening trust

Run one authorized inbound control call to the primary URI, one bounded qualifying-failure test and one restoration test. Correlate provider-side identifiers, every signaling attempt, customer-edge packets, PBX match, answer, SDP and two-way audio. Confirm that the backup URI does not share the same power, network or PBX dependency if independence is required.

Do not enable registration, trust arbitrary SIP sources, open all UDP ports or add a broad inbound catch-all merely to make the test pass. A successful new call does not prove established-call survival, universal availability, compatibility, price, emergency behavior or future routing. No Anveo Direct service, route, media path or call was tested for this guide.

Diagnose signaling, direct RTP and backup URI together

Use the Anveo Direct diagnostic to keep DID routing, signaling sources, direct carrier RTP and optional backup-URI advancement separate.