Agenda

Antitrust Policy

• PRs to review:

  • #53 - Notification compliance

• 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 (link):

• #53 - Notification compliance

  • Code to be reviewed: remove protocols not supported

    • All agreed, latest commit already removes it

  • Review of commonalities compliance

    • Currently on 0.4.0. Relase 0.5.0 for Commonalities to be relased on March’25, most significan changes ready for Dec’24

    • Comments provided by @Rafal Artych at the PR in order to get ahead of changes

    • Probably RACM and CallHandling APIs require review for this 0.5.0 release. We will have time to review them.

  • Discussion: registration and session events types. To be replaced by:

    • SessionInvitationNotification : When a new WebRTC session is requested (e.g.: new incoming call)

    • SessionStatusNotification : When a live WebRTC session is updated (e.g.: Trasnsition from progressing to ringing)

    • End of IMS subscriber registration or administrative session revoke can be notified using the common subscription-ends event

    • No new events definitions seems to be needed.

  • Anybody is really happy with the webrtc-events name , it is just a temp name. To be changed soon, before merging.

Issues to discuss (link):

• #15 - Notification events

  • To be discussed on PR #53 review

• #25 - Emergency call support for BYON

  • On hold

• #50 - Spring25 Documentation requirements

  • Present where releases are documented (Release tracker) WebRTC API Release Tracking

  • Telco terms to be reviewed

• #51 - Spring25 API requirements

  • Test definition required TODO

• #52 - Branded Calls impact in WebRTC API

  • Refactor to enhancement request for branded apps

• #54 - Detected SessionStatusNotification and SessionInvitationNotification schemas not in use

  • Schemas are defined, not linked on the yaml. The functionality is expected to be included as event notifications

Other points

• Suggested to review documentation to do not include telco terms if the doc is not telco focused.

• There is a lack of developer documentation included on the RACM and CallHandling APIs embedded on the yaml.

Action items