Using Session Initiation Protocol (SIP) can help eliminate inbound telecom fees and share Invoca data with your call center system in real time.
Using Session Initiation Protocol (SIP) can help eliminate inbound telecom fees and share Invoca data with your call center system in real time, as part of the Invoca PreSense package.
Before you begin: Your phone system must be SIP-compatible, and you’ll need to set up SIP on that system independently — check with your IT representative or call center software admin if you’re not sure. Invoca only supports SIP integrations using RFC 2833 for DTMF.
Step 1: Choose which calls to connect through SIP
- Profile-level integration: sets default SIP settings for an entire Profile, applying to all calls across all campaigns it manages.
- Campaign-level integration: connects calls from a specific campaign to particular SIP endpoints, overriding any Profile-level defaults for that campaign.
To set up at the Profile level: log in, use the account switcher to select the Advertiser or Profile (if you’re a Network user), click Integrations in the sidebar, then SIP Integration, then Activate SIP Integration if it isn’t already active. If you don’t see this option, contact Invoca Support to have it enabled.
To set up for a single campaign: click Campaigns, then Manage Campaigns, and check the SIP Integrated column for the campaign you want to configure. If you don’t see this column, contact Invoca Support to enable it. Use the Actions menu to select Update SIP Integration; if a Profile-level SIP setup already exists, you’ll be asked to confirm overriding it for this campaign.
Step 2: Specify your SIP endpoints
A SIP endpoint is the IP address or domain name that receives inbound call requests from Invoca. Only one primary endpoint is required, but multiple endpoints add redundancy. You can configure up to four endpoints as a mix of:
- Primary (active) endpoints — the preferred routing paths. With more than one, Invoca round-robins between them; failed calls go to a failover endpoint rather than another primary.
- Failover (passive) endpoints — only receive calls when the primary is unavailable.
We recommend at least two primary endpoints and one failover endpoint for redundancy and easier failure monitoring.
If using a domain name: enter the hostname only (for example, yourcompany.com), with no protocol prefix or path. Invoca’s SIP integration doesn’t support SRV records. Using the same domain for a primary and its failover(s) still provides redundancy, since Invoca re-resolves the domain’s IP on failover.
Step 3: Choose your SIP transport and RTP profile
- UDP (default) — limited to 1500-byte datagrams, which caps how many data headers you can safely send.
- TCP — supports unlimited data in SIP headers.
- TLS over TCP — also supports unlimited header data, and adds a layer of security. Your SIP endpoint needs a certificate signed by Amazon Trust Service, DigiCert, GlobalSign, GoDaddy, Verisign, or Google Trust Services; Invoca’s own certificate is signed by GoDaddy Root CA G2, so your endpoint must accept that CA as well.
TCP or TLS over TCP is recommended over UDP if your call center software supports it. Secure RTP (SRTP) is only available with TLS over TCP, and is recommended when available. If using TLS over TCP, make sure your call center provider isn’t negotiating a session timer on the Invoca SIP invite — doing so forces a re-invite with a new encryption key that Invoca won’t accept, terminating the call.
Set the format for the “From” (Caller ID) and “To” (destination number) fields — for example, From: <sip:+18055551234@example.com>. By default, numbers include a ”+” prefix (E.164 format); uncheck the related option to remove it.
Step 5: Add Invoca to your call center’s allow list
Work with your IT representative or call center software admin to:
- Allow SIP INVITE traffic from
sip.invoca.net on ports UDP/5060, TCP/5060, and TCP/5061. If your infrastructure can’t allow-list a DNS record, allow-list Invoca’s SIP IP addresses instead — contact Invoca Support for the current list, and allow-list both active and reserved IPs so future changes don’t disrupt traffic.
- Allow RTP audio traffic from any IP address over UDP ports 16384–32768.
Step 6: Pass Invoca data to your SIP endpoint
Any data added in the SIP Headers section is captured and sent with each call. Each header has a Name (the data category, conventionally prefixed with “X-”) and a Value — either a static string sent for every call, or a dynamic value selected via the < > button that pulls from the triggering call.
A few things to keep in mind:
- SIP headers are sent at the start of the call, so data only available after the call ends (like duration) can’t be included.
- If Invoca has no captured value for a dynamic header on a given call, that header is omitted from the request entirely. Contact Invoca Support if you need a header to always be present, even blank.
- If sending over UDP, keep the number and length of headers minimal to avoid errors.
Step 7: Verify your SIP endpoints
- Open your SIP integration settings and click Verify on the SIP endpoints tile.
- Enter the destination phone number or extension for the “To” field and click the checkmark.
- Select the endpoint to verify from the dropdown.
- Call the generated test phone number from another phone.
- If the call connects, stay on the line for at least 15 minutes to rule out SIP timeout issues, confirming clear two-way audio. Have the call center agent hang up first, then wait for Invoca’s success prompt before hanging up yourself.
- Return to your browser and click Done. Repeat for each endpoint.
Step 8: Test and activate
Consider testing your full configuration on a new profile with test calls before going live. Once satisfied, return to your main profile and click Activate SIP Integration — all calls for that profile will now route through SIP.
Deactivating SIP
Return to your SIP integration settings and click Deactivate SIP Integration. Calls will route to your Campaign’s destination numbers via the standard method (PSTN) instead.
Where to go next
Last modified on September 25, 2026
