How to Tear Down a Single Stream Session

[bsriramprasad]

In the signaling flow, the Connect command carries a session expiration time. Additionally, there is an Extend mechanism that allows the device to send session renewal requests to the signaling service. Our question is about the session lifecycle management:

• When the session expiration time is reached, does the signaling service actively close the corresponding PeerConnection? Or is it the device's responsibility to detect the timeout and close the connection?
• If the signaling service is expected to close the PeerConnection upon session expiry, what is the exact mechanism or signaling message used to notify the device?
• Is there a dedicated signaling message for the client or device to explicitly tear down a specific stream (as opposed to waiting for the session to expire)?
• When a session is renewed via the Extend mechanism, is a new expiration time returned, or is the existing session simply marked as active without changing the timeout?

Understanding the expected session teardown flow is important for proper resource management on both the device and the signaling service.