Attendees
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. |
- PR#27 Flow Review
There isn't new comments, fixes Issues in the PR #18.
Santiago could provide some comments if is needed .
[Flow review - BYON by stroncoso-quobis · Pull Request #27 · camaraproject/WebRTC (github.com)]
- PR#28 update BYON-Callhandling-Service.yaml
The PUT response should return a 200 OK status code, with the response body reflecting the updated session object. No new session object is being created, and thus status code 201 Created is not applicable.
- PR#29 Updated BYON-Calling, BYON-RACM, BYON-Notification: ResourceURL to sessionID/channelId
Deepak modified the BYON-Notification-Channel.yalm.
Removal of {deviceId} from the URI will lead to WebRTC gw not associating channels to the deviceId
Pradeep prefer to retain the deviceIdin the Uri for associating notification channels wih WebRTC sessions. However Deepak propose removing it as a mandatory parameter.
Comments the both ideas and clarify the best way to update this parameter.
Open Issues:
- Emergency Call support for BYON (Issue#25) Emergency call support for BYON · Issue #25 · camaraproject/WebRTC (github.com)
- Included detailed status description in flow PR#27. (Issue#32) Include detailed status description · Issue #32 · camaraproject/WebRTC (github.com)
There is no clear explanation of the ENUM status for sessions. Expected to include a dedicated section on the webrtc_voice_api.md document and to formalize it on the API yaml: BYON-CallHandling-Service.yaml
- Review if this work has been done.