TAS-106 on /telephony/sessions/{conferenceId}/parties/bring-in during merge; conference create works

I tried this a long time ago so I don’t really remember the exact steps to setup a conference call.

I am not sure where you got the /call-control/merge endpoint that you said it returns 409 conflict.

You can read and follow the instructions from this dev guide and try it again.

Thanks for the pointer. We reviewed the official conference guide and our flow is aligned with it:

• https://developers.ringcentral.com/guide/voice/conference
• https://developers.ringcentral.com/guide/voice/call-control
• https://developers.ringcentral.com/guide/voice/finding-active-calls

Clarification: /api/r/call-control/merge is our internal backend wrapper route. Inside it we call official RingCentral APIs:

1. POST /restapi/v1.0/account/~/telephony/conference (works, 200)
2. POST /restapi/v1.0/account/~/telephony/sessions/{conferenceSessionId}/parties/bring-in (fails with 403 TAS-106)

We also establish the SIP host leg before bring-in. Conference creation + host join works, but bring-in is rejected (TAS-106 Operation is not allowed) for both -1 and -2 party IDs.

Can you confirm whether this indicates account/role/call-leg restrictions for bring-in/merge on these sessions?

Can you simply test your account/extension with this webphone demo app to see if conference call works with the user you want to start the conference.

https://ringcentral.github.io/web-phone-demo/

Thanks for the guidance. I want to clearly separate what we tested in WebPhone Demo vs our Laravel integration.

What we tested in WebPhone Demo
- We tested with the same account/extension.
- Conference creation works.
- “Invite to conference” (Bring-in flow) also works in that demo scenario.
- The demo is useful to validate conference + bring-in behavior, but it is not our full app merge wrapper flow.

What we implemented in our Laravel app
- We use official RingCentral APIs (no unofficial endpoint):
  1) POST /restapi/v1.0/account/~/telephony/conference
  2) POST /restapi/v1.0/account/~/telephony/sessions/{conferenceSessionId}/parties/bring-in
- Our `/api/r/call-control/merge` endpoint is only an internal wrapper that orchestrates these official API calls for two active calls.
- So “merge” in our app = create conference + bring-in call A + bring-in call B.

Important technical note
- Conference API itself is working in our app.
- Bring-in also works in some conference scenarios.
- The blocking issue is specific merge scenarios where bring-in for certain live call legs returns TAS-106 (Operation is not allowed), even after trying party-id variants (-1 and -2).

Request for confirmation
Can you confirm whether there is any issue in this approach, or if TAS-106 here indicates account/extension/call-leg restrictions for these specific calls?
If restricted, please share the exact required role/feature/call conditions to allow this merge path.
 

The issue appears to be somewhere in your code. I recommend submitting a developer support ticket and providing the code where you handle conference calls. Specifically where you start a conference, create a new call, and call the bring-in endpoint. Without reviewing the code directly, it's difficult to pinpoint the exact cause.