Problem description
The current specification defines that once a registration expires, initiating new incoming or outgoing calls is no longer possible. However, the expected behavior for existing active resources at the moment of expiration is not documented.
Specifically,
- If a voice or video call is active when the registrationId expires, should the network disconnect the media session, or should it allow the session to continue until terminated?
- Should the WebRTC event subscription resources (webrtc-events API) associated with the deviceId be automatically deleted or ?
No intention to limit the implementation. Rather, we would first like to seek a group consensus on whether these scenarios should be address in the specification.
Expected action
Add informational descriptions to clarifiy the expected lifecycle behavior.
Problem description
The current specification defines that once a registration expires, initiating new incoming or outgoing calls is no longer possible. However, the expected behavior for existing active resources at the moment of expiration is not documented.
Specifically,
No intention to limit the implementation. Rather, we would first like to seek a group consensus on whether these scenarios should be address in the specification.
Expected action
Add informational descriptions to clarifiy the expected lifecycle behavior.