Skip to main content

Release Notes: 2026-06-08 — RTB Targets — RTB SIP Endpoint Support

RTB Targets can now be configured for SIP endpoint routing, including SIP URI, custom headers, and optional authentication guidance.

D
Written by Denise Abdullah

RTB SIP Endpoint Support

Release date: June 8, 2026

Location: RTB Targets → Response Mapping; Inbound RTB routing

What’s new

  • RTB Targets can now be configured as SIP endpoints instead of phone-number-only destinations.

  • Response Mapping now supports SIP URI, Headers, optional Username, and optional Password fields.

  • SIP authentication can be enabled only when needed, with username and password values supplied from mapped response fields or custom values.

  • RTB setup validates required SIP endpoint details before saving to help prevent incomplete SIP configurations.

  • Inbound RTB routing can dial SIP endpoint results while continuing to support standard phone-number RTB routing.

New fields

  • This is a SIP endpoint — switches the RTB Target from phone-number mapping to SIP endpoint mapping.

  • SIP URI — maps the SIP destination returned by the RTB response.

  • Headers — maps custom SIP headers from the RTB response when the buyer returns headers that need to be passed with the SIP call.

  • Enable Authentication — optional toggle for SIP endpoints that require authentication.

  • Username — used only when authentication is enabled; can be mapped from the RTB response or entered as a custom value.

  • Password — used only when authentication is enabled; can be mapped from the RTB response or entered as a custom value.

Getting started

  1. Create or edit an RTB Target.

  2. In Response Mapping, select This is a SIP endpoint.

  3. Map the SIP URI field from the buyer’s RTB response.

  4. Use Headers only when the buyer response includes custom headers that should be passed with the SIP call.

  5. Leave authentication off unless the SIP endpoint requires it.

  6. If authentication is required, turn on Enable Authentication, then map or enter the Username and Password.

  7. Save the RTB Target.

  8. Use normal phone-number RTB mapping when the buyer returns a phone number instead of a SIP endpoint.

Tip

Only configure Headers when you receive custom headers to pass through to the SIP destination. Authentication is optional — only enable it when the SIP endpoint requires username/password credentials.

Customer impact

  • Supports RTB buyers that return SIP endpoints for call routing.

  • Gives teams a clear setup path for SIP URI, custom headers, and optional authentication.

  • Reduces setup risk by validating required SIP endpoint details before the RTB Target is saved.

  • Preserves existing phone-number RTB behavior for non-SIP routes.

Did this answer your question?