Patch account options from master (On-Premise) - Need documentation

API and Webhooks
1

Hi,

I’m trying to use
PATCH # /accounts/{accountId}/options

To set shared RC + MC for all subaccounts.
I can set RC without issues, but when I try to set MC it doesn’t select them, just enables the share option.

So “share_rc”: true + “room_coonectors”:“IP1,IP2” works just fine.
“share_mc”: true likewise. But something in the syntax of the meeting_connectors string doesn’t match what you find with GET # /accounts/{accountId}

Been testing wit variations on:
";pkgtcp://IP1:8802,pkg|ssl://IP1:443, ;pkgtcp://IP2:8802,pkg|ssl://IP2:443, "
“;pkgtcp://IP1:8802,pkg|ssl://IP1:443;pkgtcp://IP2:8802,pkg|ssl://IP2:443”
“pkgtcp://IP1:8802,pkg|ssl://IP1:443;pkgtcp://IP2:8802,pkg|ssl://IP2:443”
“;pkgtcp://IP1:8802,pkg|ssl://IP1:443”
“;pkgtcp://IP1:8802”
Even tried just “IP1,IP2”, “IP1:8802,IP1:443” and “all” with the same results.

So far I’ve been trying to figure this out with the webtools at (without CORS):

One thing I have noticed is that it returns “null” instead of the expected
{
“share_rc”: “boolean”,
“room_connectors”: “string”,
“share_mc”: “boolean”,
“meeting_connectors”: “string”,
“pay_mode”: “string”
}

So have anybody done this with an On-Premise setup or stumbled across the documentation of the values needed in:
“meeting_connectors”: {
“type”: “string”,
“description”: “Meeting Connector: multiple values separated by a comma.”
},

Regards,
Bo

2

Hi @bo.staahle,

Welcome to the Zoom Community. We will respond to your request shortly.

Thanks,
Ojus

3

Hi Ojus,

Still need this, your definition of shortly leaves room for improvement.

Rgs,
Bo

4

Hey @bo.staahle,

Can you try passing in the IPs like this:

{
"meeting_connectors": "12.13.20.45, 12.13.20.46"
}

Thanks,
Tommy

5

Hi Tommy,

That and many other combinations.

API Ref still returns Null (have a nice screenshot, but can only post 1 image pr post).

And the settings page looks like this afterwards, Share MC enabled, none selected

Screenshot 2020-03-15 at 11.26.00
Screenshot 2020-03-15 at 11.26.00754×242 9.74 KB

If I choose to set only share_mc: true it does select all of them, but I wish to split some stuff and we’re looking into having more than one pair of Zone Controllers with MMRs.
So I really need this in order to control who goes where.

Regards,
Bo

6

Hey @bo.staahle,

Thanks for trying that. We are looking into this and will get back to you asap. (ZOOM-144804)

Can you please share the {accountId} you are passing in?

-Tommy

7

Hi Tommy,

Any subaccount under 165526, don’t have one on me atm.

Will update later today.

Regards,

Bo S Ståhle
Media Services Engineer

8

Thanks, we are looking into it and will get back to you.

-Tommy

9

Hi Tommy,

Just did it (20:45 CET) on our test account.

nwwVhdJxTLS6LY2QnmcFww

PATCH https://api.zoom.us/v2/accounts/{accountId}/options
{
“share_mc”: true,
“meeting_connectors”: “185.174.117.61”
}
or
{
“share_mc”: true,
“meeting_connectors”: “185.174.117.61, 185.174.117.62”
}

Returns null
Sets Share Meeting Connector checked

WEB_335e8edd7bc540fa80d8b3e39429eea7

GET https://api.zoom.us/v2/accounts/{accountId}

{
“account_number”: 0,
“created_at”: “2020-01-15T11:51:58Z”,
“id”: “nwwVhdJxTLS6LY2QnmcFww”,
“options”: {
“meeting_connectors”: “;pkg|tcp://185.174.117.61:8802,pkg|ssl://185.174.117.61:443, ;pkg|tcp://185.174.117.62:8802,pkg|ssl://185.174.117.62:443,”,
“pay_mode”: “master”,
“room_connectors”: “”,
“share_mc”: true,
“share_rc”: false
},

After settings it with the webinterface to both test ZCs.

Then I tried setting it while they where set and got the same result (WEB_66ea62b827e863d5529929aecf1f5e13)

I set it back, it has its own pair of Zone Controllers :wink:

Regards,
Bo

1 Like
10

Great! Glad you got it working! :slight_smile:

Thanks,
Tommy

11

Hi Tommy,

No I did not get it to work, I can set them in the webinterface. That is not what I need.

I need to be able to set them via the API.

Regards,
Bo

12

Hey @bo.staahle,

Apologies, I misunderstood your post.

I will get back to you on a solution.

Thanks,
Tommy

13

Hi Tommy,

Any word on this, we’re racking up accounts and could really use this to split them into different zones.

Rgs,
Bo

14

Hey @bo.staahle,

Our engineers have suggested to try using one IP at a time:

"room_connectors": "10.13.19.54"

Thanks,
Tommy

15

Hi Tommy,

So the Room Connectors are not the problem, I can set those just fine.
The Meeting Connectors (aka Zone Controllers) is what I’m trying to set.
Doesn’t work.

Even tried using the eu API point as we’re hosted in the EU.
Tried misc. variations this morning…
9371 ./set_mc.sh ‘{“share_mc”:true}’ ; ./get_mc.sh
9372 ./set_mc.sh ‘{“share_mc”:false}’ ; ./get_mc.sh
9373 ./set_mc.sh ‘{“share_mc”:true,“meeting_connectors”:“185.174.117.51”}’ ; ./get_mc.sh
9374 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“185.174.117.51”}’ ; ./get_mc.sh
9375 ./set_mc.sh ‘{“share_mc”:false}’ ; ./get_mc.sh
9376 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“185.174.117.51”}’ ; ./get_mc.sh
9377 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";185.174.117.51"}’ ; ./get_mc.sh
9378 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";185.174.117.51:8802"}’ ; ./get_mc.sh
9379 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";185.174.117.51:8802,"}’ ; ./get_mc.sh
9380 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";pkg|tcp://185.174.117.51:8802,"}’ ; ./get_mc.sh
9381 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443,"}’ ; ./get_mc.sh
9382 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443, "}’ ; ./get_mc.sh
9383 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443,"}’ ; ./get_mc.sh
9384 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443"}’ ; ./get_mc.sh
9385 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“pkg|tcp://185.174.117.51:8802,pkg|ssl://185.174.117.51:443”}’ ; ./get_mc.sh
9386 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“pkg|ssl://185.174.117.51:443”}’ ; ./get_mc.sh
9387 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“pkg|ssl://185.174.117.51”}’ ; ./get_mc.sh
9388 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“185.174.117.51”}’ ; ./get_mc.sh
9389 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";185.174.117.51"}’ ; ./get_mc.sh
9390 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:";185.174.117.51,"}’ ; ./get_mc.sh
9391 ./set_mc.sh ‘{“share_mc”:true, “meeting_connectors”:“185.174.117.51,”}’ ; ./get_mc.sh
9393 ./set_mc.sh ‘{“meeting_connectors”:“185.174.117.51”}’ ; ./get_mc.sh

Interestingly enough the webinterface checks the tick by Share Meeting Connector
image

But the output from get options is
–snip–
“created_at”: “2020-01-15T11:51:58Z”,
“vanity_url”: “”,
“options”: {
“share_rc”: false,
“room_connectors”: “”,
“share_mc”: false,
“meeting_connectors”: “”,
“pay_mode”: “master”
}

PS: .61 isn’t turned on right now, so I just picked one of the others …

Regards,
Bo

16

Hey @bo.staahle,

Gotcha, we are looking into why this isn’t working.

Thanks,
Tommy

17

Hey @bo.staahle,

After talking with engineering, they said that there is no shared meeting connector, “share_mc” will be false.

Since there is a bug, if the meeting connector has more than one ip address, it can’t be shared yet.

I will keep you updated on the bug.

Thanks,
Tommy

18

Hi Tommy,

I don’t understand - each Meeting Connector doesn’t have more than one IP ?
The Zone Controllers have 2 ports listening on 1 IP, if there is an MMR on the ZC it needs an extra IP.

But there is a bug in setting what exactly ?
Can I set 1 IP ?
If so how ?

Can I get the number for the bug, so I can reference it to Zoom people ?
(Feel free to email it to me directly if it isn’t allowed to be public).

Rgs,
Bo

19

Hey @bo.staahle,

The bug reference is ZOOM-144804. We are working to fix it and will keep you updated.

Thanks,
Tommy

20

Hey @bo.staahle,

We will be fixing this bug by the end of the month.

Thanks,
Tommy