> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daily.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Telephony events (SIP/PSTN)

> Events for SIP and PSTN dial-in and dial-out session lifecycle.

These events fire during SIP/PSTN telephony sessions started with [`startDialOut()`](https://docs.daily.co/reference/react-native/instance-methods/start-dial-out) or triggered by inbound SIP dial-in. See the [dial-in/dial-out guide](https://docs.daily.co/docs/guides/features/dial-in-dial-out) for setup.

***

## Dial-in Events

> [!NOTE]
>
> **`sipEndpoint` and `sipEndPoint`**
>
> Current react-native-daily-js versions send the dial-in endpoint as `sipEndpoint`, the spelling in the TypeScript type definitions, and also under the old spelling `sipEndPoint`. `sipEndPoint` will be deprecated, so prefer `sipEndpoint`. Older versions send only `sipEndPoint`, so `sipEndpoint` is `undefined` there. This applies to `dialin-ready`, `dialin-connected`, `dialin-stopped`, `dialin-warning`, and `details` on `dialin-error`.
>
> To support both, read `sipEndpoint` and fall back to `sipEndPoint`:
>
> ```javascript theme={null}
> call.on('dialin-ready', (ev) => {
>   const sipEndpoint = ev.sipEndpoint ?? ev.sipEndPoint;
> });
> ```
>
> In TypeScript, the types declare only `sipEndpoint`, so read the fallback with a cast: `(ev as { sipEndPoint?: string }).sipEndPoint`. Drop the fallback once your app no longer runs on older versions.
>
> The value starts with `sip:`, for example `sip:my-room.0@my-domain.sip-us.daily.co`. The room's [`sip_uri.endpoint`](https://docs.daily.co/reference/rest-api/rooms/get-room#response-config-sip-uri) is the same address without the `sip:` prefix. Webhooks are not affected: they always use `sip_endpoint`.

### dialin-ready

Fires once for each of the room's SIP endpoints when it is ready to receive a call. Only emitted when the room has [SIP dial-in](https://docs.daily.co/docs/guides/features/dial-in-dial-out/sip.md) configured.

**action** `string`

Always `"dialin-ready"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sipEndpoint** `string`

The SIP endpoint URI ready to receive calls (e.g. `"sip:room-name.0@your-domain.sip-us.daily.co"`). Also sent as `sipEndPoint`, which will be deprecated, and the only key on older react-native-daily-js versions; see [`sipEndpoint` and `sipEndPoint`](#dial-in-events).

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

```json theme={null}
// Example event object
{
  "action": "dialin-ready",
  "callClientId": "17225364729060.9442072768918943",
  "sipEndpoint": "sip:room-name.0@your-domain.sip-us.daily.co",
  "sipEndPoint": "sip:room-name.0@your-domain.sip-us.daily.co",
  "provider": "daily"
}
```

***

### dialin-connected

Fires when a SIP or PSTN caller has connected to the Daily room and both endpoints are negotiating media.

> [!NOTE]
>
> `dialin-connected` does not mean media has started flowing — it means the connection request was received and media negotiation is underway.

**action** `string`

Always `"dialin-connected"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sessionId** `string`

Session ID of the dial-in participant.

**sipCallId** `string`

The call ID of the call leg. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**userId** `string`

Optional user ID associated with the session.

**sipFrom** `string`

Optional SIP `From` address of the caller.

**sipEndpoint** `string`

Optional SIP endpoint that received the call. Also sent as `sipEndPoint`, which will be deprecated; see [`sipEndpoint` and `sipEndPoint`](#dial-in-events).

**sipHeaders** `object`

Optional SIP headers from the incoming request.

**actionTraceId** `string`

Optional trace ID for debugging.

```json theme={null}
// Example event object
{
  "action": "dialin-connected",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "a64d30f4-5216-4481-a2ef-515d6dd7dfc6",
  "userId": "user_123",
  "sipFrom": "sip:caller@example.com",
  "sipEndpoint": "sip:room-name.0@your-domain.sip-us.daily.co",
  "sipEndPoint": "sip:room-name.0@your-domain.sip-us.daily.co",
  "sipCallId": "abc123@sip.daily.co",
  "provider": "daily"
}
```

***

### dialin-stopped

Fires when a SIP or PSTN session ends — either the remote end disconnected or the call was terminated.

**action** `string`

Always `"dialin-stopped"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sessionId** `string`

Session ID of the participant whose session ended.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**userId** `string`

Optional user ID associated with the session.

**sipFrom** `string`

Optional SIP `From` address of the caller.

**sipEndpoint** `string`

Optional SIP endpoint that received the call. Also sent as `sipEndPoint`, which will be deprecated; see [`sipEndpoint` and `sipEndPoint`](#dial-in-events).

**sipHeaders** `object`

Optional SIP headers.

**sipCallId** `string`

The call ID of the call leg, if available. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**actionTraceId** `string`

Optional trace ID for debugging.

```json theme={null}
// Example event object
{
  "action": "dialin-stopped",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "a64d30f4-5216-4481-a2ef-515d6dd7dfc6",
  "sipCallId": "abc123@sip.daily.co",
  "provider": "daily"
}
```

***

### dialin-error

Fires when a fatal error occurs in the dial-in pipeline — for example, an SDP negotiation failure.

**action** `string`

Always `"dialin-error"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**errorMsg** `string`

Human-readable error description.

**sessionId** `string`

Session ID of the affected participant. Absent when `type` is `'start-failed'`, because no session was created.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**type** `string`

Optional error classification. Currently only `'start-failed'`.

**userId** `string`

Optional user ID.

**sipCallId** `string`

The call ID of the call leg, if available. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**details** `object`

Optional details object. May contain `sipEndpoint` (also sent as `sipEndPoint`, which will be deprecated; see [`sipEndpoint` and `sipEndPoint`](#dial-in-events)), plus `sipStatusCode` (number) and
`sipReasonPhrase` (string): the status code and reason phrase of the rejected SIP request
(for dial-in, the REGISTER). Present only when the failure was a SIP rejection. A `408` or `503` may be generated locally on a timeout or transport failure rather than sent by the far end.

**actionTraceId** `string`

Optional trace ID for debugging.

```json theme={null}
// Example event object
{
  "action": "dialin-error",
  "callClientId": "17225364729060.9442072768918943",
  "errorMsg": "Dialin failed with error: SIP registration failed. status code: 403 Forbidden.",
  "sessionId": "a64d30f4-5216-4481-a2ef-515d6dd7dfc6",
  "details": {
    "sipEndpoint": "sip:my-room.0@my-domain.sip-us.daily.co",
    "sipEndPoint": "sip:my-room.0@my-domain.sip-us.daily.co",
    "sipStatusCode": 403,
    "sipReasonPhrase": "Forbidden"
  },
  "provider": "daily"
}
```

```json theme={null}
// Example event object when dial-in fails to start
{
  "action": "dialin-error",
  "callClientId": "17225364729060.9442072768918943",
  "errorMsg": "sip dialin start failed",
  "type": "start-failed",
  "details": {
    "sipEndpoint": "sip:my-room.0@my-domain.sip-us.daily.co",
    "sipEndPoint": "sip:my-room.0@my-domain.sip-us.daily.co"
  },
  "provider": "daily"
}
```

***

### dialin-warning

Fires for non-fatal dial-in errors, such as when a requested codec is unavailable and a fallback is applied.

**action** `string`

Always `"dialin-warning"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**errorMsg** `string`

Human-readable description of the warning.

**sessionId** `string`

Session ID of the affected participant.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**userId** `string`

Optional user ID associated with the session.

**sipFrom** `string`

Optional SIP `From` address of the caller.

**sipEndpoint** `string`

Optional SIP endpoint that received the call. Also sent as `sipEndPoint`, which will be deprecated; see [`sipEndpoint` and `sipEndPoint`](#dial-in-events).

**sipCallId** `string`

The call ID of the call leg, if available. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

```json theme={null}
// Example event object
{
  "action": "dialin-warning",
  "callClientId": "17225364729060.9442072768918943",
  "errorMsg": "Requested codec unavailable, using fallback",
  "sessionId": "a64d30f4-5216-4481-a2ef-515d6dd7dfc6",
  "provider": "daily"
}
```

***

## Dial-out Events

### dialout-connected

Fires when Daily's SIP leg for the dial-out is connected. With SignalWire, that is Daily's leg to SignalWire, so the callee may still be ringing; wait for [`dialout-answered`](#dialout-answered). With the Daily SIP provider, it is the call to the callee itself, so it fires only once the callee answers.

**action** `string`

Always `"dialout-connected"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sessionId** `string`

Session ID of the dial-out participant.

**sipCallId** `string`

The call ID of the call leg. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**destination** `string`

Optional. Phone number in E.164 format or SIP URI of the remote party.

**origin** `string`

Optional. Originating address — phone number in E.164 or SIP URI.

**callerId** `string`

Optional. The `callerId` passed to `startDialOut()`: the ID of a purchased phone number. The number presented to the remote party is in `origin`.

**userId** `string`

Optional user ID associated with the session.

**actionTraceId** `string`

Optional trace ID for debugging.

```json Phone (E.164) theme={null}
{
  "action": "dialout-connected",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "destination": "+12098888888",
  "origin": "+13977888822",
  "callerId": "99ae8efd-d32c-4786-9bb4-77735a4e7d22",
  "sipCallId": "c6a9f2d4-1b3e-4f7a-9d2c-5e8b0a1f3c47",
  "provider": "signalwire"
}
```

```json SIP URI theme={null}
{
  "action": "dialout-connected",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "destination": "sip:callee@example.com",
  "origin": "sip:myroom.dialout.0@your-domain.sip-us.daily.co",
  "sipCallId": "abc123@sip.daily.co",
  "provider": "daily"
}
```

***

### dialout-answered

Fires when the remote party answers the outbound call. With SignalWire, it fires when the carrier reports the call answered. With the Daily SIP provider, it fires right after [`dialout-connected`](#dialout-connected), because that event is only sent once the SIP INVITE is answered.

**action** `string`

Always `"dialout-answered"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sessionId** `string`

Session ID of the dial-out participant.

**sipCallId** `string`

The call ID of the call leg. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**destination** `string`

Optional. Phone number in E.164 format or SIP URI of the remote party.

**origin** `string`

Optional. Originating address.

**callerId** `string`

Optional. The `callerId` passed to `startDialOut()`: the ID of a purchased phone number. The number presented to the remote party is in `origin`.

```json Phone (E.164) theme={null}
{
  "action": "dialout-answered",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "destination": "+12098888888",
  "origin": "+13977888822",
  "callerId": "99ae8efd-d32c-4786-9bb4-77735a4e7d22",
  "sipCallId": "c6a9f2d4-1b3e-4f7a-9d2c-5e8b0a1f3c47",
  "provider": "signalwire"
}
```

```json SIP URI theme={null}
{
  "action": "dialout-answered",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "destination": "sip:callee@example.com",
  "origin": "sip:myroom.dialout.0@your-domain.sip-us.daily.co",
  "sipCallId": "abc123@sip.daily.co",
  "provider": "daily"
}
```

***

### dialout-stopped

Fires when the dial-out session ends — the remote party hung up, the callee never answered (busy, declined, unreachable), or [`stopDialOut()`](https://docs.daily.co/reference/react-native/instance-methods/stop-dial-out) was called.

With the default `"signalwire"` provider an unanswered dial-out ends here, carrying the callee's SIP status; with `"daily"` it fires [`dialout-error`](#dialout-error) instead. See [unanswered dial-outs by provider](https://docs.daily.co/docs/daily-js/features/dialin-dialout.md#unanswered-dial-outs-by-provider).

**action** `string`

Always `"dialout-stopped"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sessionId** `string`

Session ID of the dial-out participant.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**destination** `string`

Optional. Destination phone number or SIP URI.

**origin** `string`

Optional. Originating address.

**sipCallId** `string`

The call ID of the call leg, if available. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**sipStatusCode** `number`

Optional, `"signalwire"` provider only. The SIP status code with which the callee ended the
call before answering, e.g. `486` (busy), `603` (declined), `404` (not found). Absent when the
callee answered and later hung up, when the session was stopped through the API, and after a
call transfer. Best-effort: it can also be absent for an unanswered call when SignalWire's call
record is not available in time, so a missing code does not mean the callee answered.

**sipReasonPhrase** `string`

Optional. The standard reason phrase for `sipStatusCode` (RFC 3261), e.g. `"Busy Here"`. It is
derived from the code, not the phrase the callee sent. Present only with `sipStatusCode`.

```json theme={null}
// Example event object: remote party hung up
{
  "action": "dialout-stopped",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "destination": "+12098888888",
  "origin": "+13977888822",
  "provider": "signalwire"
}
```

```json theme={null}
// Example event object: callee declined (SignalWire)
{
  "action": "dialout-stopped",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "destination": "+12098888888",
  "origin": "+13977888822",
  "provider": "signalwire",
  "sipCallId": "3adfe67d-c976-446a-80a3-6d95f5c2755e",
  "sipStatusCode": 603,
  "sipReasonPhrase": "Decline"
}
```

***

### dialout-error

Fires when a fatal error occurs in the dial-out pipeline.

**action** `string`

Always `"dialout-error"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**errorMsg** `string`

Human-readable error description.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**sessionId** `string`

Optional session ID.

**userId** `string`

Optional user ID.

**sipCallId** `string`

The call ID of the call leg, if available. On the Daily SIP provider this is the SIP `Call-ID`; on SignalWire it is SignalWire's SID for the SIP leg between Daily and SignalWire. To match events for the same call, use `sessionId`.

**details** `object`

Optional details object. May contain `destination`; `sipStatusCode` (number) and
`sipReasonPhrase` (string), the status code and reason phrase of the rejected SIP request
(INVITE, or REGISTER for providers that register before dialing), present only when the
failure was a SIP rejection (a `408` or `503` may be generated locally on a timeout or transport failure rather than sent by the far end); and `sipHeaders`, a map of the custom `X-` SIP headers returned
by the remote SIP endpoint when it rejected the dial-out, useful for debugging and error
interpretation.

**actionTraceId** `string`

Optional trace ID for debugging.

```json theme={null}
// Example event object
{
  "action": "dialout-error",
  "callClientId": "17225364729060.9442072768918943",
  "errorMsg": "DialOut failed with error: SIP dial out failed. status code: 486 Busy Here",
  "sessionId": "22b32b65-cd65-42b2-9665-db05ef3e1255",
  "details": {
    "destination": "+12098888888",
    "sipStatusCode": 486,
    "sipReasonPhrase": "Busy Here",
    "sipHeaders": { "X-Reason": "user busy" }
  },
  "provider": "signalwire"
}
```

***

### dialout-warning

Fires for non-fatal dial-out errors, such as when a requested codec is unavailable and a fallback is applied.

**action** `string`

Always `"dialout-warning"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**errorMsg** `string`

Human-readable description of the warning.

**provider** `string`

The SIP provider: `'signalwire'` or `'daily'`. See [SIP providers](https://docs.daily.co/docs/guides/features/dial-in-dial-out#sip-providers).

**sessionId** `string`

Optional session ID of the affected participant.

```json theme={null}
// Example event object
{
  "action": "dialout-warning",
  "callClientId": "17225364729060.9442072768918943",
  "errorMsg": "Requested codec unavailable, using fallback",
  "sessionId": "7d208e2a-520b-4a8d-a2c9-3a36dfa0d342",
  "provider": "daily"
}
```

***

## DTMF events

### dtmf-event

Fires when a SIP or PSTN participant presses a key, on dial-in and dial-out legs alike. Every participant in the room receives it. See [receiving DTMF](https://docs.daily.co/docs/guides/features/dial-in-dial-out#receiving-dtmf) for which SIP legs can deliver tones. There is no webhook for received tones.

**action** `string`

Always `"dtmf-event"`.

**callClientId** `string`

The ID of the call client instance that emitted this event.

**sessionId** `string`

Session ID of the SIP or PSTN participant that sent the tone.

**tone** `string`

The key pressed: `0`–`9`, `*`, `#`, or `A`–`D`.

**method** `string`

How the tone arrived: `'telephone-event'` (RTP telephone event, Daily SIP provider only) or `'sip-info'`.

**volume** `number`

The volume reported with the tone: the RFC 4733 volume for a telephone event, or the `Volume` field of the SIP INFO body (`10` when the body has none).

```json theme={null}
// Example event object
{
  "action": "dtmf-event",
  "callClientId": "17225364729060.9442072768918943",
  "sessionId": "a64d30f4-5216-4481-a2ef-515d6dd7dfc6",
  "tone": "5",
  "method": "telephone-event",
  "volume": 10
}
```

***

## See also

> [card] Methods
>
> * [startDialOut()](https://docs.daily.co/reference/react-native/instance-methods/start-dial-out.md)
> * [stopDialOut()](https://docs.daily.co/reference/react-native/instance-methods/stop-dial-out.md)

> [card] Guides
>
> * [Events](https://docs.daily.co/docs/daily-js/concepts/events.md)
> * [Dial-in/Dial-out Overview](https://docs.daily.co/docs/guides/features/dial-in-dial-out)
> * [daily-js: Dial-in and dial-out](https://docs.daily.co/docs/daily-js/features/dialin-dialout.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.