Add Emergency Calling support (callType + PIDF-LO location) by deepakjaiswal1 · Pull Request #120 · camaraproject/WebRTC

deepakjaiswal1 · 2025-10-06T23:07:55Z

Summary

Introduces callType on MediaSessionInformation with values REGULAR | EMERGENCY.
Adds locationDetails to MediaSessionInformation (required when callType=EMERGENCY).
Provides new schemas under components/schemas:
• LocationDetails (PIDF-LO style container)
• CircleCoordinates
• EllipsoidCoordinates

Rationale

Enable emergency call flows and regulatory handling.
Align location payloads with PIDF-LO concepts (3GPP TS 24.229, RFC 4119/5139/5491).

Change Details

webrtc-call-handling.yaml:
• MediaSessionInformation.properties: +callType (enum: REGULAR|EMERGENCY).
• MediaSessionInformation.properties: +locationDetails ($ref: #/components/schemas/LocationDetails).
• components/schemas: +LocationDetails, +CircleCoordinates, +EllipsoidCoordinates.

Compatibility

Backward compatible: if callType is omitted, treat as REGULAR.
locationDetails is recommended when callType=EMERGENCY.
No changes to existing endpoints, existing examples, or the existing description formatting.

Which issue(s) this PR fixes:

Fixes #25

Changelog input

 release-note
- webrtc-call-handling: Add Emergency Calling support (callType + PIDF-LO location)

Summary - Introduces `callType` on MediaSessionInformation with values `REGULAR | EMERGENCY`. - Adds `locationDetails` to MediaSessionInformation (required when `callType=EMERGENCY`). - Provides new schemas under components/schemas: • `LocationDetails` (PIDF-LO style container) • `CircleCoordinates` • `EllipsoidCoordinates`

Updated indentation Summary - Introduces `callType` on MediaSessionInformation with values `REGULAR | EMERGENCY`. - Adds `locationDetails` to MediaSessionInformation - Provides new schemas under components/schemas: • `LocationDetails` (PIDF-LO style container) • `CircleCoordinates` • `EllipsoidCoordinates` Rationale - Enable emergency call flows and regulatory handling. - Align location payloads with PIDF-LO concepts (3GPP TS 24.229, RFC 4119/5139/5491). Change Details - webrtc-call-handling.yaml: • MediaSessionInformation.properties: +`callType` (enum: REGULAR|EMERGENCY). • MediaSessionInformation.properties: +`locationDetails` ($ref: `#/components/schemas/LocationDetails`). • components/schemas: +`LocationDetails`, +`CircleCoordinates`, +`EllipsoidCoordinates`. Compatibility - Backward compatible: if `callType` is omitted, treat as `REGULAR`. - No changes to existing endpoints, existing examples, or the existing description formatting.

Removed errors

Added URN addressing

deepakjaiswal1 · 2025-10-07T01:36:16Z

@stroncoso-quobis @teikuran @pradeepachar-mavenir Please review the Emergency calling CR and provide feedback.

teikuran · 2025-10-09T11:45:32Z

Just a clarification. With this proposal, the API client can set callType to "REGULAR" while setting receiverAddress to e.g., "urn:service:sos.police". Correct?

teikuran · 2025-10-10T10:58:08Z

Don't have detail proposal yet, but perhaps, we should define an error response in case GW(NW) does not support calltype "EMERGENCY". And API client should consider that emergency call is not suupported upon reception of the error response.

deepakjaiswal1 · 2025-10-14T00:47:31Z

Just a clarification. With this proposal, the API client can set callType to "REGULAR" while setting receiverAddress to e.g., "urn:service:sos.police". Correct?

If the SOS service is invoked, callType must be set to EMERGENCY. In cases where the client application sets it to REGULAR, the network may override this setting to ensure the call does not fail.

deepakjaiswal1 · 2025-10-14T00:51:42Z

Don't have detail proposal yet, but perhaps, we should define an error response in case GW(NW) does not support calltype "EMERGENCY". And API client should consider that emergency call is not suupported upon reception of the error response.

This is good feedback. In the United States, emergency calling support is mandatory if the application is capable of placing regular PSTN calls.

stroncoso-quobis

Hi @deepakjaiswal1 ,

Thanks for the PR, and sorry for my late review
Technically, the specs are ok, but I will require some changes in order to help to organize the info.

PR Description updates

PR description must include:

The lines with the fixes:
- Fixes #25
The release notes box
- For each affected APIs, a change line into a code box. Similar to what you have on the Change Details section, but following the template :) .

This is needed to generate the release notes later next year. In general, it will help if the PR descriptions adhere to the PR template. Template here, and example here

In-YAML-doc updates

I'm going to request changes on the description field. The Authorization and authentication and the Additional CAMARA error responses are mandatory texts on the commonalities, and are expected to be at the end. I will leave them as the last ones. Including the Emergency calling section before them. My suggestion is to include it as part of section 3: Like 3.4. Emergency Calling

Overview

Technically the specs are ok. Minor fixes on description and in-yaml doc.
Not really qualified to understand all the complexities of the LAW referring to EMERGENCY CALLING, so I can't really help there. I will comment with some colleagues, maybe they can provide extra feedback
I love the PIDF-LO specs usage. I will use for other use cases. Good work!

--

Thanks for your contribution
Best regards

stroncoso-quobis · 2025-10-28T06:26:25Z

code/API_definitions/webrtc-call-handling.yaml

    As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible
    error response if it is explicitly documented in the API.

+    # Emergency Calling


Suggested to include this info as part of section 3: Like 3.4. Emergency Calling.

We can cover this on the final release review.

teikuran · 2025-10-30T09:57:26Z

As we mentiond during conference call. Here is the proposal for the case that emergency call feature is not supported.

paths:
  /sessions:
    post:
      tags:
        - Call handling
      summary: Creates voice and/or video session
      description: Creates a voice and/or video session
      operationId: createSession
      parameters:
        - $ref: "#/components/parameters/x-correlator"
        - $ref: '#/components/parameters/hdrRegistrationId'
      security:
        - openId:
            - webrtc-call-handling:sessions:create
      requestBody:
        description: Provide the information required for session creation
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/MediaSessionInformation'
            examples:
              Media session request:
                $ref: '#/components/examples/exampleMediaSessionRequest'
              EmergencyMediaSessionRequest:
                $ref: '#/components/examples/exampleEmergencyMediaSessionRequest'
      responses:
        '201':
          description: Created
          headers:
            x-correlator:
              $ref: "#/components/headers/x-correlator"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MediaSessionInformation'
              examples:
                SessionCreated:
                  $ref: '#/components/examples/exampleMediaSessionResponse'
        '400':
          $ref: '#/components/responses/Generic400'
        '401':
          $ref: "#/components/responses/Generic401"
        '403':
          $ref: '#/components/responses/Generic403'
+        '501':
+          description: Not Implemented
+          headers:
+            x-correlator:
+              $ref: '#/components/headers/x-correlator'
+          content:
+            application/json:
+              schema:
+                allOf:
+                  - $ref: '#/components/schemas/ErrorInfo'
+                  - type: object
+                    properties:
+                      status:
+                        enum:
+                          - 501
+                      code:
+                        enum:
+                          - CALLTYPE_EMERGENCY_NOT_SUPPORTED
+              examples:
+                501_CALLTYPE_EMERGENCY_NOT_SUPPORTED:
+                  description: The implementation of API provider does not support the `callType` of `EMERGENCY`.
+                  value:
+                    status: 501
+                    code: CALLTYPE_EMERGENCY_NOT_SUPPORTED
+                    message: Server does not support call type EMERGENCY.

Enhances the emergency calling API specification by introducing a 501 Not Implemented response for cases where callType = EMERGENCY is not supported by the provider.

Resolve conflicts with base changes (e.g., clientCorrelator)

…/WebRTC into emergency-calling

stroncoso-quobis

LGTM!
I updated the description to include the fix issue relationship and the release notes.
Ready to merge

stroncoso-quobis · 2026-01-11T13:10:22Z

code/API_definitions/webrtc-call-handling.yaml

    As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible
    error response if it is explicitly documented in the API.

+    # Emergency Calling


We can cover this on the final release review.

deepakjaiswal1 requested review from pradeepachar-mavenir, stroncoso-quobis and teikuran as code owners October 6, 2025 23:07

deepakjaiswal1 added 3 commits October 6, 2025 17:38

Update webrtc-call-handling.yaml

0faf26d

Removed errors

Update webrtc-call-handling.yaml

2973c4c

Added URN addressing

stroncoso-quobis suggested changes Oct 28, 2025

View reviewed changes

deepakjaiswal1 added 7 commits November 17, 2025 18:10

Add 501 Not Implemented response for unsupported EMERGENCY callType

3b3ff88

Enhances the emergency calling API specification by introducing a 501 Not Implemented response for cases where callType = EMERGENCY is not supported by the provider.

Resolve conflicts with base changes (e.g., clientCorrelator)

84e2b22

Resolve conflicts with base changes (e.g., clientCorrelator)

Resolve conflicts with base changes (e.g., clientCorrelator etc)

557052a

Rebase

99de43f

Merge branch 'main' into emergency-calling

755327c

Resolve lint error

8cae94c

Merge branch 'emergency-calling' of https://github.com/deepakjaiswal1…

0908897

…/WebRTC into emergency-calling

deepakjaiswal1 requested a review from stroncoso-quobis January 2, 2026 17:28

stroncoso-quobis approved these changes Jan 11, 2026

View reviewed changes

stroncoso-quobis merged commit 8de632a into camaraproject:main Jan 13, 2026
2 checks passed

stroncoso mentioned this pull request Jan 27, 2026

[Sync26] WebRTC APIs meta-release scope r3.x (DRAFT) #137

Open

stroncoso mentioned this pull request Feb 24, 2026

Provide location for call creation process #142

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Emergency Calling support (callType + PIDF-LO location)#120

Add Emergency Calling support (callType + PIDF-LO location)#120
stroncoso-quobis merged 11 commits intocamaraproject:mainfrom
deepakjaiswal1:emergency-calling

deepakjaiswal1 commented Oct 6, 2025 •

edited by stroncoso-quobis

Loading

Uh oh!

deepakjaiswal1 commented Oct 7, 2025

Uh oh!

teikuran commented Oct 9, 2025

Uh oh!

teikuran commented Oct 10, 2025

Uh oh!

deepakjaiswal1 commented Oct 14, 2025

Uh oh!

deepakjaiswal1 commented Oct 14, 2025

Uh oh!

stroncoso-quobis left a comment

Uh oh!

stroncoso-quobis Oct 28, 2025

Uh oh!

stroncoso-quobis Jan 11, 2026

Uh oh!

teikuran commented Oct 30, 2025

Uh oh!

stroncoso-quobis left a comment

Uh oh!

stroncoso-quobis Jan 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

deepakjaiswal1 commented Oct 6, 2025 • edited by stroncoso-quobis Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Which issue(s) this PR fixes:

Changelog input

Uh oh!

deepakjaiswal1 commented Oct 7, 2025

Uh oh!

teikuran commented Oct 9, 2025

Uh oh!

teikuran commented Oct 10, 2025

Uh oh!

deepakjaiswal1 commented Oct 14, 2025

Uh oh!

deepakjaiswal1 commented Oct 14, 2025

Uh oh!

stroncoso-quobis left a comment

Choose a reason for hiding this comment

Uh oh!

stroncoso-quobis Oct 28, 2025

Choose a reason for hiding this comment

Uh oh!

stroncoso-quobis Jan 11, 2026

Choose a reason for hiding this comment

Uh oh!

teikuran commented Oct 30, 2025

Uh oh!

stroncoso-quobis left a comment

Choose a reason for hiding this comment

Uh oh!

stroncoso-quobis Jan 11, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

deepakjaiswal1 commented Oct 6, 2025 •

edited by stroncoso-quobis

Loading