External Platform SIP Routing for Buyers
IntegrationsWhy SIP Beats DID for Buyer Delivery
When TrackDrive forwards a call to a Buyer by DID, the consumer's caller ID is presented as the calling number. The Buyer's carrier sees a number TrackDrive does not own and applies Stir/Shaken signing rules. Most providers sign these calls B-Level (the carrier vouches for the originator but does not own the number), and downstream carriers increasingly treat B-Level traffic with suspicion: endless ringing, immediate voicemail, or silent failures.
Sending the call SIP-to-SIP avoids the public PSTN entirely and bypasses carrier reputation handling. SIP delivery is faster, more reliable, and immune to most B-Level degradation patterns.
SIP to TrackDrive
Traffic Source can be provided this link to SIP route to TrackDrive. No whitelisting of IP addresses is required in TrackDrive sip:real_td_number@sip.trackdrive.com
External Platform
For Buyers on other call tracking platforms with a published SIP endpoint, configure an external platform record. The SIP endpoint field requires:
- Must start with
sip: - Must contain a placeholder for the number to dial
- Must contain
@followed by a domain or IP
When SIP routing is enabled on the platform and a Buyer is associated with that platform, the dialer substitutes the buyer's phone number into the endpoint template and routes the call SIP-to-SIP. Inquire if the external platform requires whitelisting of IP address and provide those to ensure a seamless experience in call connectivity.
Why a Centralized Table
SIP endpoints change. When a destination platform updates its SIP host, every Buyer pointing at that platform must follow. Defining the endpoint once on the external platform record means the change is applied centrally rather than edited on every buyer record.
