Search results

  1. Max

    WCS 5.3.502 — safely confirming SIP/RTMP cleanup before creating a replacement stream

    You could use /rest-api/v3/call/find query to check if the SIP call is active or not. If callId is unique and never reused after completion, you may be sure the call is successfully terminated if you cannot find any call with this callId.
  2. Max

    WCS 5.3.502 — safely confirming SIP/RTMP cleanup before creating a replacement stream

    The mediaSessionId is unique, so the termination query affects only one session Both APIs do the same operations under the hoods. But REST API v3 offers more correct asynchronous operations handling and auto-generated API documentation based on OpenAPI specification.
  3. Max

    WCS 5.3.502 — safely confirming SIP/RTMP cleanup before creating a replacement stream

    Good day. All the termination requests are synchronous. HTTP 200 response means RTMP republishing is terminated. 404 means there no the republishing session with this mediaSessioId. This confirms the session is terminated The stream replacement is not implemented: the old stream should be...
  4. Max

    WCS Log4j obsolete version

    Good day. There is still no updates on the ticket WCS-2521.
  5. Max

    webRTC Stream "FAILED: Session does not exist"

    Good day. VOD streaming is an asynchronous operation, so 200 OK response to /rest-api/vod/startup means the request is accepted only. There is a new REST API v3 in WCS 5.3 branch returning 202 Accepted response in this case. Please update to the latest WCS build 5.3.500 (or 5.2.2317 if you still...
  6. Max

    Stream Not Starting After Successful Response from rest-api/vod/startup

    Good day. VOD streaming is an asynchronous operation, so 200 OK response to /rest-api/vod/startup means the request is accepted only. There is a new REST API v3 in WCS 5.3 branch returning 202 Accepted response in this case. Please update to the latest WCS build 5.3.500 (or 5.2.2317 if you still...
  7. Max

    WebRTC over TCP and the channel queue limits

    Good day. These are the default values And these are the recommended values for that case. Note that they are half as much as defaults. ice_tcp_channel_high_water_mark = 104857600, ice_tcp_channel_low_water_mark = 10485760 Yes If the number of bytes queued in the TCP outgoing channel write...
  8. Max

    Audio-only publish fails with "Failed by ICE keep alive" on a good connection

    Good day. Yes, ICE keep alive controls STUN binding requests and responses timeout. Please see a detalied WebRTC description here. The parameter is ice_keep_alive_timeout=15 The timeout is 15 seconds by default. If no responce received to the STUN binding request in this interval, the ICE...
  9. Max

    Service account renamed + directory permissions tightened, breaking non-root deployments

    We fixed the issue in build 5.3.494. Please update and check.
  10. Max

    Service account renamed + directory permissions tightened, breaking non-root deployments

    Good day. We do not rename the user account. Seems like user addition inside the container is broken. We raised the ticket WCS-5144 to investigate, will let you know about results.
  11. Max

    Has anyone integrated Flashphoner with Outlook for call/meeting notifications?

    Goos day. Outlook uses SIP to make a calls. WCS offers WebRTC-SIP gateway functions to make a SIP calls, and may capture a media stream from a SIP call to republish it at a third party server. So WCS and Outlook may be integrated at a SIP PBX level: for example, a SIP conference call may be...
  12. Max

    RTSP port pool exhaustion ("No free ports available") - port leak on failed/dead camera reconnects

    We fixed the issue in WCS build 5.3.492. Please update and check.
  13. Max

    RTSP port pool exhaustion ("No free ports available") - port leak on failed/dead camera reconnects

    Good day. We reproduced the issue and raised the ticket WCS-5122. Will let you know about fix.
  14. Max

    WCS Log4j obsolete version

    Good day. The log4j version currently used is working on modern operating systems icluding CentOS 9. The well-known vulnerabilities cannot be exploited by WCS design. So current log4j version can be surely used in production. There is the ticket WCS-2521 to upgrade log4j to 2.x version, but it...
  15. Max

    CDN configuration not working with the latest version (CDN 2.17)

    Good day. About the ticket WCS-4953. Since build 5.3.470 a viewers may stay connected to the reserved SRT stream: when publisher accidentaly stops streaming, subscribers will see a last frame played (new subscribers do not see anything), and when publisher resumes streaming, the stream should...
  16. Max

    CDN configuration not working with the latest version (CDN 2.17)

    About the ticket WCS-5026. We fixed the cdn_nodes_timeout > -1 issue in build 5.3.469. Please update and check. About the playback issue. There is the ticket WCS-4953 that may affect the CDN playback case when SRT publisher stops and starts again. As workaround, try the following: 1. Reduce SRT...
  17. Max

    CDN configuration not working with the latest version (CDN 2.17)

    Please check the following: 1. Publishing keyframe interval should be stable. For example, in OBS settings it should not be 0 (auto): 2. WebRTC/UDP ports (30000-33000 by default) should be opened in private network between origin and edges If this does not help, reproduce the issue and collect...
  18. Max

    CDN configuration not working with the latest version (CDN 2.17)

    Good day. We reproduced the issue in our test environment. You should set cdn_nodes_timeout=-1 (the default value) on all the nodes. We raised the ticket WCS-5026 to investigate the side effect of non-default values of this parameter.
  19. Max

    MPEG-TS RTP stream publishing via reserved ports

    We fixed the issue in build 5.3.466. Please update and check.
  20. Max

    MPEG-TS RTP stream publishing via reserved ports

    We reproduced the issue in obfuscated 5.3.465 build. Raised the ticket WCS-5013, will let you know about progress.
Top