1 Answer
- Newest
- Most votes
- Most comments
1
Thinking of the call flow that you refer to, in step 6 you got the meeting ID and attendee ID that you needed for the JoinChimeMeeting action. At that step, when you send the JoinChimeMeeting action, you could also store those IDs in TransactionAttributes. Those transaction attributes will be stored with that session so you'll be able use them for the deleteAttendee API call in step 8 when you get the Hangup event.
Transaction attributes: https://docs.aws.amazon.com/chime-sdk/latest/dg/transaction-attributes.html
answered 4 months ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thanks for taking a look - I'd attempted this, and wasn't receiving the TransactionAttributes back on the Hangup call when received - I'd assumed they didn't last that long. I'll take a look and see if I've accidentally cleared them down on another response.
Thanks again for the response - looks like the TransactionAttributes I'd set were getting cleared (possibly when handling the ACTION_SUCCESSFUL events). I've updated our code to go a little more overboard with ensuring TransactionAttributes are carefully returned in full each time, and that's now feeding through the actions to the Hangup event as expected.