MoM - 240618- WebRTC Working group.

Owned by Javier Villa
Last updated: Jun 19, 2024
2 min read

Attendees - TBD

  • Ricardo Serrano (TEF)

  • Javier Villa (TEF)

  • Deepak Jaiswal (TMUS)

  • Santiago Troncoso (Quobis)

  • Rafal Artych (DT)

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Below, I attach the agenda for this week

1) Review of the support document 'Emergency call info'. Review of the support document 'Emergency call info'. If necessary, we should review the different scenarios to work on. [Issue#25]. Support documentย Here

2) Review ifย PR#27ย flow was merged after participants review. Merged if not

3) PR#40ย to be merged after correcting POST Method of the Notification Channel and after review. Note that there are still a couple of loose ends, which we can address in subsequent cleanup PRs.

E.g.,

  1. ย 

    1. a) Remove ObjectResponse schema

    2. b) Add 204 (no response body) and 200 (with response body) for PUT /vvoip/..../status API

    3. c) 200 OK response for vvoipSession create

    4. d) Add examples

Review It.

ย 

ย 

  • ย 

    • Remember that from now on we will use the toolย ZOOMย for meetings.

    • Meetings will be 30 minutes long.

Discussion.

Item

Who

Description

Item

Who

Description

Review PR27

Ricardo and Santiago

Santiago comments the updated flow documentation.ย 

  • Included more detailed and accourate (v0.1.2) info about notification channels

  • Included more detail about UPDATE / PRACK on pre-ringing stages for IMS

Merged PR27 - flow documentation.

ย 

Flow diagrams Reviewย 

Santiago

Open a new ย PR#42 to review the diagram document.

  • It covers the detailed BYON flow, separated on three main use cases: notification channel, registration and call handling.

  • It provides a necessary asset to attract developers and to fully understand the API mechanisms.

Merged PR40 and PR 41ย 

Open PR#43

Ricardoย 

Merged PR40 and 41 related with linting rules.

Discuss de emergency call scenariosย 

Deepak and Ricardo

Emergency Calling in WebRTC - CAMARA Project - Confluence

ย 

Action points

Actions

Who

Actions

Who

Review diagram flow documentation PR#42.

Complete new version including a separate 200/204 in response to PUT actions

Santiago

Review emergency calling info and provide new solution for the scenarios

Emergency Calling in WebRTC - CAMARA Project - Confluence

All

ย 

AOB

  • Next meeting will be the 2nd of July

  • Next meeting will be at 16h CEST 30minutes longย 

  • The next meetings will be held by theย LFX Zoomย platform.

  • From then to now the minutes will be uploaded toย Confluence