• Skip to Search
  • Skip to Content
  • Skip to Side Navigation
Getting StartedSDK ReferenceGlossary
  • Home
  • Getting Started
  • SDK Reference
  • Portal
  • How-To
  • Troubleshooting
  • FAQs
  • Reference
  • Glossary
FAQs
  • How is Phenix real-time streaming different from off the shelf WebRTC?
  • How does Phenix scale WebRTC to millions?
  • What is the difference between a CDN and Phenix?
  • What is the difference between a Channel and a Room?
  • Does Phenix encrypt its Real-Time streams?
  • How does Phenix define Real-Time vs Low Latency?
  • How does Phenix compare with technologies such as CMAF?
  • On which cloud platforms is the Phenix platform deployed?
  • What is the recommended minimum hardware spec for devices to publish from a web browser to Phenix?
  • What WebSocket reconnect mechanisms are built into the Web SDK?
  • What are the benefits of the Phenix hardware encoder?
  • How does Phenix multi-bitrate transcoding work and how do I enable it?
  • What bitrates are used for encoding and publishing?
  • How does Phenix adapt to challenging network connections?
  • How does Phenix handle rapid join rates and broadcast size audiences?
  • Where can I see the status of the Phenix system?
  • When do sessions and sessionIds expire?
  • What is the digest field portion of the Auth token?
  • Which video players support Phenix?
  • Which capture devices are compatible with Phenix?
  • Where can I find documentation of the text chat feature?
  • What size and bitrate should I use for publishing?
  • Does Phenix provide a video player?
  • What effects will 5G have on Phenix?

When do sessions and sessionIds expire?

What happens to the session and sessionId if the Client never joins the room for which a token was issued? Does the Client need to perform clean up of the session?

The session does not have a timeout. The platform will continue to honor a session after it has been established and maintained (via heartbeats). This means that the sessionId will be valid until such time the Client's Phenix SDK stops sharing heartbeats with the Phenix platform. This may happen if, for example, a connection is interrupted due to a network change or the Client app is closed.

If the connection is broken for a short period of time, the Phenix platform will attempt to re-associate the Client to the session. If the connection is broken for a longer period of time, the SDK will attempt to authenticate again using the token it was provided. If the token has expired, the session will not be authenticated and the application will need to obtain a new token.

Page Content
    Copyright 2023 © Phenix RTS
    Privacy Policy | Terms of Service
    v2023-01-31T21:25:10