Skip to main content

Release Notes: 2026-01-23 — Routing — SIP Trunk Targets

sip, outbound sip, call transfers, routing

E
Written by Eric Gardona

Location: Targets → RTB Targets
​Release Date: 11-24-2025

📝 Overview

You can now route outbound calls through SIP trunks using SIP Targets. This enables campaigns and routing plans to send calls directly to any valid SIP endpoint — with full support for authentication, custom SIP headers, and dynamic metadata injection.

✨ What’s New

🎯 SIP Trunk Targets as Routable Endpoints

Moja now supports SIP Targets as first-class routing destinations, allowing calls to be delivered straight into a buyer’s SIP infrastructure (instead of PSTN or standard number targets).

🆕 SIP Target Type in the UI

When creating a Target, you can now choose SIP Target and configure:

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

  • 🔐 Optional authentication credentials (username/password)

  • 🏷️ Custom SIP headers

  • 🔄 Dynamic variable substitution for header values

🔀 Routing Plan Support

You can now:

  • Add SIP Targets as actions inside routing plans using “Route to SIP Target”

  • Configure priorities, weights, and fallback logic like any other target type

⚡ RTB Compatibility - COMING SOON

Future release will enable SIP Targets to be fully supported within Inbound RTB flows, enabling:

  • Dynamic SIP target assignment (upcoming release)

  • SIP-level delivery to RTB auction winners (upcoming release)

  • Real-time endpoint allocation via RTB logic (upcoming release)

🟦 Note: In a future release, SIP Targets will work everywhere number-based targets do — including RTB, campaigns, and routing plans.

🎯 Why This Matters

This release enables direct SIP interoperability between Moja and enterprise buyers that rely on SIP trunks.

It:

  • 🚫 Removes dependency on PSTN for SIP-native buyers

  • 🧩 Enables advanced routing with header injection & credential control

  • 🔓 Unlocks new buyer segments previously limited by infrastructure compatibility

💡 Example Use Cases

  • A routing plan allocates a percentage of traffic to a SIP endpoint using unique headers for testing, segmentation, or vendor separation - Available now

  • A VoIP provider receives RTB calls directly into their SIP SBC via URI routing - Coming soon

  • A buyer in an RTB auction is assigned a SIP Target with credentials and custom headers; if they win, Moja securely dials their SIP trunk - Coming soon

🚀 Getting Started

1️⃣ Create a SIP Target

  1. Go to Targets → Create New

  2. Under Routing Settings, select SIP Target

  3. Fill out the SIP configuration fields:

    • Required:

    • Optional:

      • sip_username

      • sip_password

      • sip_headers

🟩 Tip: Headers support dynamic variables like campaign_id, buyer_id, or RTB metadata.

2️⃣ Add the SIP Target to a Routing Plan

  • Open a routing plan → select Route to SIP Target

  • Configure priority/weight

  • Save the plan

3️⃣ Assign the Routing Plan to a Campaign

  • Go to your campaign settings

  • Choose the routing plan containing your SIP Target

  • Save and activate

🟧 Reminder: SIP-targeted calls originate from Moja’s SIP infrastructure — ensure your SIP firewall/SBC accepts our IPs.

Did this answer your question?