Prerequisites
Before calling any telephony methods:- Your Daily account must have a credit card on file.
- For dial-out, the room must have
enable_dialout: trueand your account must be approved for dial-out. - The local participant must join with an owner meeting token.
Dial-out
Starting a session
startDialOut() initiates an outbound call to a SIP URI or PSTN phone number. The called party joins the room as a regular participant.
- SIP
- Phone (PSTN)
sessionId identifies this telephony session. Hold onto it — you’ll need it for stopDialOut(), sendDTMF(), and transfer methods.
See startDialOut() for the full parameter reference, including videoSettings for SIP video calls (encoding and the layout the SIP participant sees) and codec defaults.
For SIP dial-out, pass provider: 'daily' to use the Daily SIP provider, the recommended choice for SIP; without it, the call goes through SignalWire, the default. PSTN dial-out always uses SignalWire, so leave provider out when you dial a phoneNumber. See SIP providers for what each provider supports.
Stopping a session
Sending DTMF tones
sendDTMF() sends touch-tone signals into an active session — commonly used to navigate IVR menus:
method parameter controls how tones are signaled:
'telephone-event': RTP telephone-event packets per RFC 4733 (most compatible)'sip-info': SIP INFO requests with anapplication/dtmf-relaybody'auto'(default): Daily uses'sip-info'when the remote SIP peer listsINFOin theAllowheader of its answer, and'telephone-event'when it does not
'sip-info' on a call where the far end does not allow INFO returns an error.
When you send more than one tone in a single sendDTMF() call over SIP INFO, Daily waits a fixed 100ms between tones. That gap is not configurable. digitDurationMs sets the duration Daily signals for each digit, not the gap between digits.
There is no queueing or ordering guarantee across separate sendDTMF() calls, so two that overlap can interleave their tones. Pass the whole sequence in one call when you can. If you have to send digits one at a time, wait for each call to finish before starting the next one and add your own pacing between them.
Dial-out events
Listen to these events to track the lifecycle of an outbound session:dialout-connected fires when the SIP/PSTN network acknowledges the call; dialout-answered fires when the remote party actually picks up. When and how far apart they fire depends on the SIP provider:
- SignalWire handles the call in two parts: Daily connects to SignalWire, and SignalWire then calls the destination.
dialout-connectedfires when Daily’s connection to SignalWire is established, which can be while the destination is still ringing.dialout-answeredfires later, when SignalWire reports that the remote party picked up. - The Daily SIP provider calls the destination directly, as a single call.
dialout-connectedis only sent once the remote party answers, sodialout-answeredfollows right after it.
provider and sipCallId. sipCallId holds the SIP Call-ID on the Daily SIP provider and, on SignalWire, SignalWire’s SID for the SIP leg between Daily and SignalWire. To match events for the same call, use sessionId. See the telephony events reference for full payload details.
Unanswered dial-outs by provider
Which event reports a callee that is busy, declines, or cannot be reached depends on the SIP provider of the dial-out:-
provider: "signalwire"(the default) sits between Daily and the callee. Daily’s leg is answered as soon as the dial-out is set up, sodialout-connectedfires before the callee is even tried. If the callee then fails, SignalWire ends Daily’s leg anddialout-stoppedfires withsipStatusCodeandsipReasonPhrasedescribing the callee’s SIP response:dialout-connected→dialout-stopped { sipStatusCode: 486, sipReasonPhrase: "Busy Here" } -
provider: "daily"connects Daily’s leg to the callee directly. A rejected call never reachesdialout-connected;dialout-errorfires with the same two fields indetails:dialout-error { details: { sipStatusCode: 486, sipReasonPhrase: "Busy Here" } }
dialout.stopped and dialout.error webhooks (sip_status_code, sip_reason_phrase). Neither field is set when the callee answered and later hung up, when stopDialOut() ended the session, or after a call transfer. With SignalWire both fields are best-effort: they can also be missing for an unanswered call when SignalWire’s call record is not available in time, so a missing code does not mean the callee answered. With SignalWire the reason phrase is the standard RFC 3261 text for the code, not the phrase the callee sent.
Dial-in
Dial-in allows external SIP or PSTN callers to join a Daily room. Configure it on the room with thesip property for SIP dial-in, or the dialin property for PSTN PIN dial-in. For setup details — including PIN dial-in, pinless dial-in, and SIP interconnect — see the dial-in/dial-out guide.
Dial-in events
provider. dialin-ready, dialin-connected, dialin-stopped, dialin-warning, and details on dialin-error carry the endpoint as sipEndpoint and also as sipEndPoint, which will be deprecated; older daily-js versions send only sipEndPoint. See sipEndpoint and sipEndPoint.
dialin-connected always includes sipCallId, and dialin-stopped, dialin-warning, and dialin-error include it when a call leg exists. It holds the SIP Call-ID on the Daily SIP provider and, on SignalWire, SignalWire’s SID for the SIP leg between Daily and SignalWire. To match events for the same call, use sessionId. See the telephony events reference for full payload details.
Call transfers
To transfer an active SIP or PSTN session to another destination, usesipCallTransfer() or sipRefer(). See the call transfers guide for a full explanation of when to use each method, including a decision table and scenario examples.