update_attendee_capabilities
¶
update_attendee_capabilities(
meeting_id: GuidString,
attendee_id: GuidString,
capabilities: AttendeeCapabilities,
*,
config_overrides: Optional[ChimeSDKMeetingsClientConfig] = None,
) -> UpdateAttendeeCapabilitiesResponse
The capabilities that you want to update.
You use the capabilities with a set of values that control what the capabilities can do, such as SendReceive data. For more information about those values, see .
When using capabilities, be aware of these corner cases:
-
If you specify
MeetingFeatures:Video:MaxResolution:Nonewhen you create a meeting, all API requests that includeSendReceive,Send, orReceiveforAttendeeCapabilities:Videowill be rejected withValidationError 400. -
If you specify
MeetingFeatures:Content:MaxResolution:Nonewhen you create a meeting, all API requests that includeSendReceive,Send, orReceiveforAttendeeCapabilities:Contentwill be rejected withValidationError 400. -
You can't set
contentcapabilities toSendReceiveorReceiveunless you also setvideocapabilities toSendReceiveorReceive. If you don't set thevideocapability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set yourvideocapability to receive and you set yourcontentcapability to not receive. -
If meeting features is defined as
Video:MaxResolution:NonebutContent:MaxResolutionis defined as something other thanNoneand attendee capabilities are not defined in the API request, then the default attendee video capability is set toReceiveand attendee content capability is set toSendReceive. This is because contentSendReceiverequires video to be at leastReceive. -
When you change an
audiocapability fromNoneorReceivetoSendorSendReceive, and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants. -
When you change a
videoorcontentcapability fromNoneorReceivetoSendorSendReceive, and if the attendee turned on their video or content streams, remote attendees can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.
Parameters:
-
meeting_id(GuidString) –The ID of the meeting associated with the update request.
-
attendee_id(GuidString) –The ID of the attendee associated with the update request.
-
capabilities(AttendeeCapabilities) –The capabilities that you want to update.
Raises:
-
BadRequestException–The input parameters don't match the service's restrictions.
-
ConflictException–Multiple instances of the same request have been made simultaneously.
-
ForbiddenException–The client is permanently forbidden from making the request.
-
NotFoundException–One or more of the resources in the request does not exist in the system.
-
ServiceFailureException–The service encountered an unexpected error.
-
ServiceUnavailableException–The service is currently unavailable.
-
ThrottlingException–The number of customer requests exceeds the request rate limit.
-
UnauthorizedException–The user isn't authorized to request a resource.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_chime_sdk_meetings/_services/chime_sdk_meetings.py
1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 | |