Skip to main content

SIP Trunk Targets

D
Written by Denise Abdullah
Updated over 2 months ago

[NEW FEATURE RELEASE]
SIP Trunk Targets
Location: Targets
Release Date: 2025-11-24
Overview
You can now route outbound calls through SIP trunks using SIP Targets. This allows campaigns and routing plans to send calls to any valid SIP endpoint, with support for authentication and custom SIP headers.

What’s New
Moja now supports SIP Trunk Targets as routable endpoints, allowing calls to be delivered directly to a buyer’s SIP infrastructure instead of PSTN or standard number targets.

  • SIP Target Type in UI:

  • When creating a Target, you can now select SIP Target and provide:

    • SIP URI (e.g., sip:[email protected]:5070)

    • Optional headers and auth credentials

    • Variable substitution for dynamic headers

  • Routing Plan Support:

    • Add SIP Targets as route actions via “Route to SIP Target”

    • Set priorities and weights just like traditional number-based targets

  • RTB Compatibility:

  • SIP Targets work with Real-Time Bidding allocations, including buyer-level routing.

Why This Matters
This release enables direct interoperability between Moja and enterprise buyers who rely on SIP trunks to receive call traffic. It:

  • Removes the dependency on PSTN delivery for SIP-native buyers.

  • Enables advanced routing configurations with header injection and credential management.

  • Unlocks a new segment of buyers previously constrained by infrastructure compatibility.

Example Use Cases

  • A VoIP provider delivers RTB calls to their SIP SBC using URI-based routing.

  • A buyer bypasses Moja’s default recording layer by routing directly to a SIP device.

  • A routing plan allocates a percentage of traffic to a SIP target with specific custom headers for testing or vendor segmentation.

Getting Started

  1. Go to: Targets > Create New and select SIP Target as the Target Type under the Routing Settings section.

  2. Fill out SIP URI, headers and credentials and save.

    • Required: sip_endpoint (e.g. sip:[email protected]:5070)

    • Optional: sip_username, sip_password, sip_headers

  3. Add to a routing plan, then assign the plan to a campaign

Did this answer your question?