Agenda

PRs to review:
- #53 - Notification compliance - WIP
Issues to discuss:
- #15 - Notification events
- #25 - Emergency call support for BYON
- #50 - Spring25 Documentation requirements
- #51 - Spring25 API requirements
- #52 - Branded Calls impact in WebRTC API

Minutes

PRs to review:
- #53 - Notification compliance - WIP
  - Brief overview of the description section. Agreed to cover this event notification features based on cloudevent.
  - Drop NotificationChannel concept right now, to recover back when added endpoint to create WS or others.
  - Two types of events: session-related and endpoint registration-related. This will cover most of the use cases and open the ability to create external observers and endpoint listeners to react to session establishment async process.
Issues to discuss:
- #15 - Notification events
  - In progress. Check PR53 notes
- #25 - Emergency call support for BYON
  - On hold right now
- #50 - Spring25 Documentation requirements
  - No news, work in progress
- #51 - Spring25 API requirements
  - Notification compliance in progress
  - Extra requirements kindly added by Tanja de Groot . Thanks!
- #52 - Branded Calls impact in WebRTC API
  - Initial discussion lead the WebRTC a clear approach to cover the datachannel integration. As it is natural part of the SDP negotiated on the WebRTC channel, it is something to cover by the WebRTC API. Of course, right now focusing on notifications and compliante to hit fall release as stable, but we want to include negotiation capabilities on the WebRTC API to support the datachannel connection.

#15 - Continue working on PR53 based on the guidelines established (session and registration events)
#51 - Release tracker & API versioning review