Aura calling diagram

Important: If a tenant is enabled for the “Avaya Cloud Calling” integration with Avaya Aura, then user will be able to make or receive Aura phone calls on Spaces. Therefore we also call this “Aura Calling”. Please note that only users with Spaces business or power licenses can be enabled for the Aura Calling features.

Comments:

1. App calls Create Endpoint Api
3. Spaces backend tracks the endpointApi with corresponding mediaSessionToken in store.
4. App receives endpointId and mediaSessionToken
5. App initializes JSCSDK, create/login User-Object. using the mediaSessionToken
8. App calls the new api "Create Call" api passing its endpointId in addition to other required payloads.
9. Spaces backend creates Active-Meeting with state as "calling" response the Call/Meeting object
10. App calls the new api "Create Call" api passing its endpointId in addition to other required payloads.
11. Spaces backend tracks the conversation response within the Active-Meeting object
12. After a success (200) response, the app shows out-going-call UI to the caller/sender
13. Spaces backend sends the "space.call.offer" to other party(s) "user-channel"
14. The callee app receives the "space.call.offer" event
18. Spaces backend sends "space.call.accepted" or "space.call.rejected" socket event to both caller and callee "user-channel".
19. Once Caller receives the callee socket event "space.call.accepted" event it would start JSCSDK preparation to connect the media.