News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Receiving 409 Error when initiating call monitoring
Tags: call recording, call monitoring
Oct 9, 2023 at 8:24am   •   1 replies  •  0 likes
Michelle Garber

I'm setting up call monitoring using Python and the RingCentral API.

As specified in the API documentation, I need the supervisors device ID, agents extension, and the telephony session ID to do this.

The supervisors device ID looked up using the following endpoint:


The supervisor is using a softphone and is registered as "Can Monitor" in the call monitoring group. I can successfully pull this ID.

The extensionNumber is the three digit extension number of the person I'm looking to monitor. They are added as "Can be monitored" to the same call monitoring group as the supervisor above. The extension number lookup is done by using the extensionId. I can successfully look up the extension ID.


Websockets are operating correctly. I can subscribe and act on telephony events in real-time. I'm pulling the telephony sessionId using websockets. The URL to initiate the supervise call is:

url = (f'/restapi/v1.0/account/~/telephony/sessions/{

The final API call to start call monitoring is:

data = {'mode': 'Listen', 'deviceId': '############', 'extensionNumber': '###'}

url = (f'/restapi/v1.0/account/~/telephony/sessions/{telephony_session_id}/supervise')

response =, data)


deviceId = 12-digit device ID of the softphone of the supervisor.

extensionNumber = 3-digit extension number of person to monitor

telephony_session_id = ID of the phone call (s-a0e7a....)

The response back is: ringcentral.http.api_exception.ApiException: HTTP409

1 Answer
answered on Oct 9, 2023 at 9:11am  

You body params are incorrect. It is not the agent extension number. It is the agent extension id. And the 'supervisorDeviceId' not just the 'deviceId'

Try this

var data = {
             'mode': 'Listen', 
             'supervisorDeviceId': '############', 
             'agentExtensionId': '#############'

And remember that you can only call the API to supervise a call after the call is connected/answered.

on Nov 1, 2023 at 4:29pm   •  0 likes

Hello @Phong Vu , I'm the engineer working on resolving this. Can you send a message request so we can sync? Thank you.


on Nov 1, 2023 at 4:30pm   •  0 likes

Unfortunately, I am traveling this week. Will get back to you next week.

on Nov 21, 2023 at 10:06am   •  0 likes

Please let me know when your available. Can you sync today/tomorrow?

on Nov 21, 2023 at 10:41am   •  0 likes

How about today 12:30PM or after 2:00PM PST?

on Nov 21, 2023 at 1:15pm   •  0 likes

Could you do 2:30 PST?

on Nov 21, 2023 at 1:24pm   •  0 likes

Yes. And your email? You use the RC app, right?

on Nov 21, 2023 at 1:34pm   •  0 likes

That's correct. My email is ---. I will edit this email reference once you see it.

on Oct 9, 2023 at 10:09am   •  0 likes

I will test this. Note that the RinCentral API documentation clearly states Extension number for the agent:

{ "mode": "Listen", "extensionNumber": "108", "deviceId": "60727004"}

on Oct 9, 2023 at 10:50am   •  0 likes

Sorry for the confusion in our documentation. I believed that the dev guide doc was too old (alpha phase) and it was not updated since. I will alert the documentation team later.

But for now, please use the API reference instead

Back to the 409 error, can you check the following

- Is the device online? Can you make a normal call to the supervisor device?

- Can you confirm that the call is connected? Can you cause a little delay after the call is connected before calling the /supervise API.

on Oct 11, 2023 at 7:07am   •  0 likes

Hello Phong, I did confirm I can call the supervisors numbers. I also added a slight delay. Same results. Most of the time it's a 409 error. Sometimes a 403. Is there a way to setup a quick call between us?

on Oct 11, 2023 at 7:29am   •  0 likes

I invite you the a RC Team Messaging chat. Check your email and join the chat and we can have a look at the issue.

on Oct 11, 2023 at 9:28am   •  0 likes

Thank you! We have not received the email. Can you please confirm?

on Oct 11, 2023 at 11:24am   •  0 likes

Is your RingCentral extension's email the one you use in this community? If so, just login the RC app and you should see the direct chat.

on Oct 9, 2023 at 1:16pm   •  0 likes

Thanks for the extra details. I will work through your suggestions.

on Oct 9, 2023 at 10:23am   •  0 likes

Getting the same response (409) with:

{'mode': 'Listen', 'supervisorDeviceId': '80460166####', 'agentExtensionId': '293466####'}

A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

Developer Platform
Integrated Apps
App Gallery
Developer support
Games and rewards

Resource center
Product Releases
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us