MoM - 240227 - WebRTC Working group

Date:ย 27/Feb/2024

ย 

Attendees

ย 

  • Ricardo Serrano (Telefรณnica)

  • Javier Villa (Telefรณnica)

  • Rafaล‚ Artych (Deutsche Telekom)

  • Deepak Jaiswal (T-Mobile USA)

  • Santiago Troncoso (Quobis)

ย 

Agenda

WebRTC working group CAMARA Meeting. Review the diferrents Pull Request

Discussion

Item

Who

Description

Item

Who

Description

Issue 1: Update BYON-CallHandling Session

Ricardo and Javier

Reviwed and updated the BYON-CallHandling code. Add 201 (created) response as indicated in HTTP guidelines for a 201 in the PUT session .

Issue 2: Update BYON flow doc

Santiago

To be added some missing arrows. Include POST and DELETE of the notification channel flow in the Channel URL (RACM API).
Add autonumbers in the UML format. Review the updated flow doc. Suggest to close the last doc open by Javier and continue with the new one. Separate the doc in two files.

Issue 3: Review API response

Ricardo and Deepak

PUT response to comply with JSON formatย Issue#24. Fix description and provide some samples for the clarification. Provide a sample in POST too

Issue 4: RACM Session

Deepak

Change session names because some session id names may lead into confusion and URL return -> Session id.
The idea is not to create different channels as an app so to the Web RTC gateway we provide this channel and the Web RTC would deliver this notification to this notification channel either using the web book. If the webook web RTC is aware internally about the channel it could use the ID and get how to deliver to the channel. PNS to be explored

Action points

ย 

Description

Who

Description

Who

1. Review BYON PlantUML flowย PR#27

all

2. Review and accept the minutesย PR#20

Sushanth and Padreep

3. Keep on working in call flow. To be added some missing arrows.ย PR#27

Ricardo and Santiago

4. Disccuss Emergency callsย Issue#25

all

5. Correct 201 response (status)ย Issue#24

Ricardo

6. RACM session names Pull Request and url to SessionIdย PR#29

Deepak

ย 

AOB

ย 

  • Next meeting will be theย 12th of March