Recommended profile
Configure the inbound Vonage route to the platform SIP FQDN. Keep the exact DID in +E.164 and choose Provider source IPs in the platform. Vonage documents digest/ACL controls for customer-to-Vonage traffic, not digest from Vonage toward the customer SIP URI.
Vonage recommends allowing both primary platform subnets because SIP traffic can originate from either:
Vonage documents UDP/TCP on 5060 and TLS on 5061. Use the same transport at both ends and keep RTP/media rules separate from SIP signaling authentication. Recipient and caller identity use E.164.
Vonage does not support SIP REFER, so a cold transfer fails over a Vonage trunk. Configure any assistant transfer on this trunk as a warm transfer instead.
Validate
Call the routed DID externally and confirm a new inbound platform call, the assigned assistant, and two-way audio. If no inbound record appears, verify the Vonage destination URI and source subnet before changing number matching.
Sources: Vonage SIP dashboard, Vonage technical details, Vonage allowlist. Accessed 22 August 2026.
