I'm trying to dial the assistant into a conference room on my own SIP server using the "Create Call" endpoint (POST /call). The problem is that i'm required to enter customer.number even if i already filled out customer.sipUri. The customer.number regex is too restricted as i would like to use a destination in this format: "conference-{uuid}". When filling out customer.number with something and then starting the call, the call gets dispatched with customer.number and customer.sipUri is completely ignored. Is that possible somehow? Did i miss a required configuration?

You can't omit

customer.number

, but you can bypass the E164 restriction and use your conference format by setting

numberE164CheckEnabled: false

. Here’s an example payload:

json
{
  "assistantId": "3383f1a8-75b4-4358-b6d2-18a5482e92fc",
  "phoneNumberId": "00ba93af-065f-4156-b550-c2e8f0b34a0f",
  "customer": {
    "numberE164CheckEnabled": false,
    "number": "conference-{uuid}",
    "sipUri": "sip:conference-{uuid}@your-sip-server.com"
  }
}

This lets you use a custom identifier for the conference while still providing the SIP URI for routing. Note: The

number

field is still required, but it can now be your conference string as long as it matches the allowed pattern. [See docs for details](https://docs.vapi.ai/api-reference/calls/create?explorer=true) Source: - [Vapi API Reference: Create Call](https://docs.vapi.ai/api-reference/calls/create?explorer=true)

@Vapi Support Bot The numberE164CheckEnabled option only disables the e164 check, i still get this error: customer.number must match /^\\+?[a-zA-Z0-9]+$/ regular expression

Thanks for clarifying the regex issue. To help troubleshoot, could you share the exact value you are trying to use for

customer.number

(for example, the full "conference-{uuid}" string you attempted)? This will help determine if there's a way to adjust the format to fit the allowed pattern. Source: - [Vapi API Reference: Create Call](https://docs.vapi.ai/api-reference/calls/create?explorer=true)

@Vapi Support Bot For example "conference-6111686d-8826-4fdb-9c08-63cc33e3958d"

The

customer.number

field must only contain alphanumeric characters (and an optional leading

+

), even if

numberE164CheckEnabled

is set to

false

. Hyphens are not allowed. To resolve the error, remove the hyphens from your conference string. For example:

json
"customer": {
  "numberE164CheckEnabled": false,
  "number": "conference6111686d88264fdb9c0863cc33e3958d",
  "sipUri": "sip:conference-6111686d-8826-4fdb-9c08-63cc33e3958d@your-sip-server.com"
}

Use only letters and numbers in

customer.number

to meet the required pattern. [See documentation for details](https://docs.vapi.ai/api-reference/calls/call-controller-find-all-paginated?explorer=true) Source: - [Vapi API Reference: Call Controller Find All Paginated](https://docs.vapi.ai/api-reference/calls/call-controller-find-all-paginated?explorer=true)

@Vapi Support Bot Thanks! I see this error after creating the call: An error occurred in this call: call.in-progress.error-sip-outbound-call-failed-to-connect What does the error mean?

The error

call.in-progress.error-sip-outbound-call-failed-to-connect

means your SIP provider could not establish the outbound call connection. A common cause is an incorrect or unreachable SIP URI, or a misconfigured SIP trunk. Action: Double-check your

sipUri

and SIP trunk credentials, and ensure your SIP server is accessible from Vapi's network. [See more in the Vapi call ended reason docs](https://docs.vapi.ai/calls/call-ended-reason). Source: - [Vapi Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason)