---
title: "Bring-In Call Party"
method: POST
path: "/restapi/v1.0/account/{accountId}/telephony/sessions/{telephonySessionId}/parties/bring-in"
tags: ["Call Control"]
---

# Bring-In Call Party

`POST /restapi/v1.0/account/{accountId}/telephony/sessions/{telephonySessionId}/parties/bring-in`

Adds a new party to the call session by bringing in an established
SIP call connection. The maximum number of parties to bring in is 10; only
1 call party can be added per request. Currently, the method is supported for
sessions of the `Conference` origin only.

## Path parameters

- `accountId` string, required
- `telephonySessionId` string, required

## Request body

- AddPartyRequest
  - `sessionId` string, required — Internal identifier of a call session
  - `partyId` string, required — Internal identifier of a party that should be added to the call session

## Response `201`

Created

- CallParty — Information on a party of a call session
  - `id` string — Internal identifier of a party
  - `status` CallStatusInfo — Status data of a call session
    - `code` 'Setup' | 'Proceeding' | 'Answered' | 'Disconnected' | 'Gone' | 'Parked' | 'Hold' | 'VoiceMail' | 'FaxReceive' | 'Tds' | 'VoiceMailScreening' — Status code of a call
    - `peerId` PeerInfo — Peer session/party details. Valid in 'Gone' state of a call
      - `sessionId` string
      - `telephonySessionId` string
      - `partyId` string
    - `reason` 'Pickup' | 'Supervising' | 'TakeOver' | 'Timeout' | 'BlindTransfer' | 'RccTransfer' | 'AttendedTransfer' | 'CallerInputRedirect' | 'CallFlip' | 'ParkLocation' | 'DtmfTransfer' | 'AgentAnswered' | 'AgentDropped' | 'Rejected' | 'Cancelled' | 'InternalError' | 'NoAnswer' | 'TargetBusy' | 'InvalidNumber' | 'InternationalDisabled' | 'DestinationBlocked' | 'NotEnoughFunds' | 'NoSuchUser' | 'CallPark' | 'CallRedirected' | 'CallReplied' | 'CallSwitch' | 'CallFinished' | 'CallDropped' — Reason for call termination. For 'Disconnected' code only
    - `description` string — Optional message
  - `muted` boolean — Specifies if a call participant is muted or not. **Note:** If a call is also controlled via Hard phone or RingCentral App (not only through the API by calling call control methods) then it cannot be fully muted/unmuted via API only, in this case the action should be duplicated via Hard phone/RC App interfaces
  - `standAlone` boolean — If `true` then the party is not connected to a session voice conference, `false` means the party is connected to other parties in a session
  - `park` ParkInfo — Call park information
    - `id` string — Call park identifier
  - `from` PartyInfo
    - `phoneNumber` string — Phone number of a party
    - `name` string — Displayed name of a party
    - `deviceId` string — Internal identifier of a device
    - `extensionId` string — Internal identifier of an extension
  - `to` PartyInfo
    - `phoneNumber` string — Phone number of a party
    - `name` string — Displayed name of a party
    - `deviceId` string — Internal identifier of a device
    - `extensionId` string — Internal identifier of an extension
  - `owner` OwnerInfo — Deprecated. Information on a call owner
    - `accountId` string — Internal identifier of an account that monitors a call
    - `extensionId` string — Internal identifier of an extension that monitors a call
  - `direction` 'Inbound' | 'Outbound' — Direction of a call
  - `conferenceRole` 'Host' | 'Participant' — A party's role in the conference scenarios. For calls of 'Conference' type only
  - `ringOutRole` 'Initiator' | 'Target' — A party's role in 'Ring Me'/'RingOut' scenarios. For calls of 'Ringout' type only
  - `ringMeRole` 'Initiator' | 'Target' — A party's role in 'Ring Me'/'RingOut' scenarios. For calls of 'Ringme' type only
  - `recordings` RecordingInfo[] — Active recordings list
    - `id` string — Internal identifier of a recording resource
    - `active` boolean — True if the recording is active. False if the recording is paused.

## Other responses

- `400` — General response with **HTTP 400 "Bad request"** status.<br> Reasons: unparsable request, path, query or body parameters are invalid. The error description may contain reference to particular parameter(s) which haven't passed the validation.
- `403` — General response with **HTTP 403 "Forbidden"** status.<br> Reasons: the requested operation is forbidden because of certain resource state, lack of permissions, feature unavailability, etc.
- `404` — General response with **HTTP 404 "Not found"** status.<br> Reasons: the entity with given ID (typically specified in a path parameter), is not found or inaccessible
- `409` — General response with **HTTP 409 "Conflict"** status.<br> Reasons: the requested modification operation causes a conflict (for example, unique constraint violation). The error definition may contain reference to particular parameter(s) which caused the conflict.
- `500` — General response with **HTTP 500 "Internal Server Error"** status.<br> Reasons: general server-side error.
- `503` — General response with **HTTP 503 "Service not available"** status.<br> Reasons: server cannot process the request because of being overloaded, misconfiguration or other issues.

---

[API](https://skmtc.net/ringcentral/apis/ringcentral-api.md) · [All operations](https://skmtc.net/ringcentral/apis/ringcentral-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringcentral/ringcentral-api/versions/8d602198ec97/schema)