Skip to main content
Register an inbound call that your telephony already holds, then bridge it to the SIP destination BlackBox returns. The agent answers with the variables you registered, and the call ID you stored is the correlation key on every webhook and result. What you’ll learn: When to use registration instead of linked phone numbers, how the register-then-bridge flow works, and how to handle results.

When to use it

Use Register Call when:
  • Your telephony (PBX, SIP provider, contact-center platform) receives the call first.
  • You decide per call which agent should answer and which variables it needs.
  • You need one call ID shared between your system and BlackBox for the complete call lifecycle.
Use Inbound Calls instead when a phone number should always route to the same agent.

How it works

  1. Your telephony receives the inbound call.
  2. You register the call: POST /api/v1/calls/register?agentId=….
  3. BlackBox creates the call record and returns callId and sipUri (sip:{callId}@sip-reg.blackbox.dasha.ai).
  4. You store callId and bridge the live call to sipUri.
  5. BlackBox recognizes the registered call and starts the agent with your variables.
  6. The result reaches the agent’s result webhook with the same callId.
The registration stays valid until callDeadline (default 10 minutes, maximum 24 hours). If the call is not bridged by then, it is canceled and reported through the result webhook with status: "Canceled".

Register a call

Response:

Bridge the call

Point your telephony at sipUri. Any system that can transfer or bridge a live call to a SIP URI works.
Bridge each registration exactly once. A second INVITE for the same call ID is rejected with SIP 410 Gone.
BlackBox answers the INVITE with a SIP status when it cannot take the call:

Receive the result

Configure a result webhook on the agent. The payload carries the same callId, your additionalData as callAdditionalData, the transcript, the recording URL and callType: "InboundAudio".

Webhook Events

Complete webhook payload reference

Use your own domain

Registered calls can use a hostname you own instead of sip-reg.blackbox.dasha.ai, so the URI you hand to your telephony or your customers reads sip:{callId}@calls.yourcompany.com. DNS sends the call directly to Dasha; you do not need a SIP proxy in the path.
1

Add the domain

Go to Phone Numbers → SIP Domains, click Add Domain and enter the hostname, for example calls.yourcompany.com.
2

Create the DNS records

The domain details list two kinds of records. Create them at your DNS provider.SIP phones and PBXs resolve the host with A records, which the CNAME provides. Use a dedicated hostname for the domain: a CNAME cannot share its name with other records, so calls.yourcompany.com must not carry any other record. The TXT record lives at _dasha-verify.calls.yourcompany.com, which is fine next to the CNAME.
3

Verify

Click Verify on the domain. It becomes Active when the TXT record is found. The details also show whether the routing records already point at Dasha.
DNS changes can take a few minutes to propagate; verify again if the record is not found yet.
4

Register calls on the domain

Custom SIP domains are enabled per organization. A hostname can belong to one organization only, and ownership is proven by the TXT record, so any hostname you control works. Names starting with sip under dasha.ai are reserved by the Dasha platform and fail verification.

Check a registered call

To cancel a registration before it is bridged, delete the call: DELETE /api/v1/calls/{callId}.