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

  • Review of commonalities compliance

    Status
    colour Blue title IN PROGRESS

    • Some changes made, waiting Rafal Artych comments on current purposal to keep adapting changes.

  • Review of event types

    Status
    colour Blue title IN PROGRESS

    • Renamed to comply with Kebapcase

    • org.camaraproject.webrtc-events.session-invitation : When a new WebRTC session is requested (e.g.: new incoming call)

    • org.camaraproject.webrtc-events.session-status : When a live WebRTC session is updated (e.g.: Transition from progressing to ringing)

    • org.camaraproject.webrtc-events.subscription-ends : End of event subscriber registration or administrative session revoke.

    • Both subscripition types (session-invitation and session-status) generate CloudEvents with data defined by SessionEvent

      • SessionEvent is a combination RACM and CallHandling schemas for:

        • VvoipSessionInformation

        • SessionInvitiationNotification

        • SessionStatusNotification

        • ReceiverSessionStatus

      • All these events serve the same information with same data type and data identifiers. Some are optional fields mostly correlators and Ids.

        • Agreeing this change we require a dedicated change to update RACM and CallHandling.
          We need to merge and rename to SessionNotification or SessionInformation

Issues to discuss (link):

• #15 - Notification events

  Status
  colour Blue title IN PROGRESS

  • To be discussed on PR #53 review

• #25 - Emergency call support for BYON

  • On hold

• #50 - Spring25 Documentation requirements

  Status
  colour Blue title IN PROGRESS

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

  • Telco terms to be reviewed

• #51 - Spring25 API requirements

  • Test definition required

    Status
    colour Red title TODO

• #52 - Branded Calls impact in WebRTC API

  • On hold

• #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

  • Per this meeting, these schemas should be updated to Sesson

Other points

• Naming convention agreement. It must be consistent on all APIs

  • vvoipSessionId:

    • type: string - example: 0AEE1B58BAEEDA3EABA42B32EBB3DFE07E9CFF402EAF9EED8EF

      The VVOIP session ID created by WebRTC Gateway. It will be included in the notifications from the WebRTC GW to client and will be the UUID for an active WebRTC media session.

  • racmSessionId

    • type: string - example: xsmcaum3z4zw4l0cu4w115m0

      The RACM session ID created by WebRTC Gateway. Obtained via RACM API.

• Release scope agreement:

  • We will include RACM, CallHandling and webrtc-events on release

  • NotificationService or implicit notifications will be enhances for next releases

Action items

•  #53 - Keep working on comms fixes and event re-definition
•  #51 - Tests still needed