Hi team,

Good news, PR is ready for a first review.

Main elements to consider:

• API works based on two kind of susbcriptions: registration and session. One is designed to keep the device reachable, and the other to track a session in progress.
• regsitration
  • Event when the network requires to refresh register
  • Event when a new session is requested (incoming call)
• session
  • Event to update and define participants on the call
  • Event to update session status (ringing, progressing, accepting, cancel, cleared, …)
  • Event to update SDP information (new candidates, network updates, track bw update, ...)

Use a Swagger rendered view appending https://editor.swagger.io/?url= to the RAW commint file.

• https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fcamaraproject%2FWebRTC%2Fdc87f0cb305a8fdc37d8c33ce0f8b0508ea49e5e%2Fcode%2FAPI_definitions%2FBYON-Webrtc-Events.yaml

The file is big, I know, so I will track your attention to:

• Initial description, check texts and provide comments about general approach
• SubscriptionRequest schema: It is the payload for a new subscription
  • registration event subscription requires a the subscriber information, while session event subscription requires both, the user information and the sessionId to subscribe to.
  • Have in mind that, per CloudEvents+CAMARA specs, our WebRTC details are included into SubscriptionDetail that is included into config.
• CloudEvent schema: It is the payload of the event received for any case
  • Our WebRTC relevant information is placed into the data property that could be one of the two possible events: EventRegistration and EventSession.
  • The SubscriptionEnds event is a CAMARA requirement
• EventRegistration schema: Brand new object
  • To inform about re-registration or a new incomming session.
  • Tries to map to the BYON-RACM session info, but including an optional new session structure (call incoming)
  • Included a hook for future branded calls with a subject field
• EventSession: Event about session updates
  • It is mapped to the vvoipSessionInformation schema of the BYON-CallHandling API
  • Tries to unify a couple of duplicated schemas like the SubscriberUser info or the SDP descriptor

Please, @deepakjaiswal1 , share with your team and provide some feedback, while I clean the linter errors and try to create some documentation for this update (workflows are not valida anymore) and document some bugs detected on other files.

Best regards,

Hi all,

An update about today's commit. I fixed all linter errors and also reviewed the examples for a better comprehension of the events. Reviewing the examples, I found that sessionId was missing on the new_session_event, so I included it as part of the EventRegistration / sessionRequest . Without it, it is not possible to grant a valid suscription for session events.

Waiting for comments and reviews