Hi @Vapi @Vapi Support Bot , I have an existing SIP trunk configured between Genesys and VAPI. Our goal is to send metadata from Genesys to VAPI using a UUID, which we pass during the SIP call. Could you please confirm: How can we receive this UUID on the VAPI side from the inbound SIP call? (Currently I have a dashboard assistant who is assigned to this inbound number) Is there a way to extract SIP headers (e.g., X-Context-ID) or any other method you support to retrieve such data?

To receive a UUID (e.g., from an

X-Context-ID

SIP header) on inbound SIP calls, configure your Vapi phone number to use a server URL instead of a static dashboard assistant. When a call arrives, Vapi will POST an

assistant-request

event to your server, including SIP headers in the payload. You can extract the UUID like this:

js
app.post("/api/assistant-selector", (req, res) => {
  const uuid = req.body.call?.sipHeaders?.['x-context-id'];
  // Use the UUID as needed
  res.json({ assistantId: "your-assistant-id" });
});

Note: This approach requires switching from a dashboard-assigned assistant to a server URL/webhook configuration. [See docs for details](https://docs.vapi.ai/advanced/sip#send-sip-headers-to-fill-template-variables) Sources: - [SIP integration documentation](https://docs.vapi.ai/advanced/sip) - [Personalization with user information](https://docs.vapi.ai/assistants/personalization)

Configure your Genesys SIP trunk to pass it in a custom SIP header X-Context-ID, use the “Get SIP Headers” action in the Architect inbound flow to extract it, then pass it to your VAPI assistant via participant data or API call..

SIP Call Issue – Inbound Going to Voicemail, Outbound Call Tool Not Found Hey everyone — I’m setting up SIP integration for my voice agent using Vapi and running into two key issues: ❌ What’s Happening: 1. Inbound calls to my SIP number are going to voicemail — they’re not reaching my voice agent 2. Outbound calls are failing with this error: "Outbound Call Failed. Couldn't Get Tool, toolid [some_tool_id] Does Not Exist." ✅ What I’ve Done: Integrated a SIP trunk from a local Caribbean provider Used standard settings (UDP, PCMU/PCMA codecs, RFC2833 DTMF) Created a voice agent and assigned the SIP connection Double-checked auth, domain, and credentials (all correct) 🧠 Questions: What might cause inbound calls to skip Vapi entirely? What does the “Tool ID does not exist” error mean? Is it related to a missing config or voice agent? Appreciate any help or direction! – Andre

Inbound calls may go to voicemail if the SIP trunk isn’t correctly routed through Genesys Architect or if the

X-Context-ID

SIP header isn't extracted using the “Get SIP Headers” action; outbound calls fail with “Tool ID does not exist” if the VAPI assistant is referencing a tool ID that hasn’t been defined in its configuration..