Agenda

Antitrust Policy

• PRs to review:

  • n/a

• Issues to discuss:

  • #15 - Notify event

  • #25 - Emergency call support for BYON

  • #50 - Spring25 Documentation requirements

  • #51 - Spring25 API requirements

Minutes

Open PRs to review:

• n/a

Issues to discuss:

• #15 - Notify event

  • Agreement found on separate the WebRTC GW for an external notification service: The WebRTC GW will be limited to webhooks, and this Notification Service will cover other notification mechanisms.

  • Notification Service will be an optional component needed to support WS communication systems (eg.: web based clients), WebRTC GW will be CAMARA compliant and will implement only webhooks as it is the only notification mechanism possible (Commonalities - section 12).

  • So the notification endpoint should be converted to an optional endpoint where a WS notification process is defined. We will write a Confluence page about this topinc since is fundamental for browser WebRTC (BYON) use cases.

  • Additionaly, other formal considerations must be taken for CAMARA compliance

  • Seems to be all agree on this approach 🤝

  • Action points: Create new diagrams, create PR with changes, create Confluence webpage

• #25 - Emergency call support for BYON

  • The main issue to address is that location is not included on the current API features, this is needed for emergency call routing

  • Deepak shared comments at https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14549591/Emergency+Calling+in+WebRTC?focusedCommentId=23134224 , the main idea is to use estandarized location format (already used on other CAMARA APIs to provide RAW location to GW. This will be used by internal telco software to route emergency calls to the corresponding PSAP (Public-Safety Access Point). As a result, an extra field is proposed on the session POST to include location.

  • Action points: Create PR with changes

• #50 - Spring25 Documentation requirementsFlow & description documentation migration in progress

  • no time for discussion

  • Action points: Pending migrate doc and review telco terms

• #51 - Spring25 API requirementsReviewing notification as main work in progress pointRemove current tag, align and move to r0.1.1 format

  • Partially discussed on #15 regarding notifications CAMARA compliance

  • Action points: Pending release tracker, API versioning and Security & interop profile

Action items

•  #15 - Create new diagrams, purpose PR with changes, create Confluence webpage
•  #25 - Purpose PR with changes
•  #50 - Migrate doc
•  #51 - Release tracker & API versioning review