如何在RingCentral API的RingOut中正确使用extensionId？

Let’s break down why you’re hitting the CMN-102 error when specifying an extensionId in your RingOut request—even though you confirmed the ID is valid:

1. Check if your authenticated user has permission to RingOut on behalf of others #

By default, regular users can only initiate RingOut for their own extension. To trigger RingOut for another extension, your authenticated user needs the "RingOut on behalf of others" permission enabled in their role.

To verify this:

• Head to the RingCentral Admin Portal
• Navigate to the authenticated user’s details page
• Go to the Permissions tab
• Ensure the RingOut on behalf of others option is checked under the Calling section

2. Confirm the target extension belongs to the same account #

The ~/ in /account/~/ refers to the account linked to your authenticated user. Make sure the extensionId 279580017 is part of this exact account. If you fetched the ID from a different account’s API response, that’s almost certainly why you’re seeing the "resource not found" error.

3. Verify your access token has the right scopes #

Your access token needs the correct scopes to perform RingOut for other extensions. At minimum, it should include ringout. For accessing extensions outside the authenticated user’s own, you may also need extension:read and extension:ringout scopes.

You can check your token’s scopes by decoding it (using a tool like jwt.io) or by calling this endpoint:

GET /restapi/v1.0/account/~/extension/~/auth-info

4. Double-check you’re using extensionId, not extension number #

Even though you said you fetched the ID from the API, it’s easy to mix up the numeric extensionId (like 279580017) with the user-friendly extension number (like 101). Using the extension number in the extensionId path parameter will definitely throw a resource not found error.

5. Ensure the target extension is active #

A valid extensionId might still fail if the extension has been deactivated, deleted, or suspended. Confirm its status by calling:

GET /restapi/v1.0/account/~/extension/279580017

Look for the status field in the response—it should be Enabled. If it’s Disabled or Suspended, you won’t be able to initiate RingOut for it.

If you’ve checked all these boxes and still run into the error, try testing with an extension you know the authenticated user has access to, or reach out to RingCentral support with your request details (timestamp, extensionId, accountId) for deeper investigation.

内容的提问来源于stack exchange，提问作者SurferJoe