We are testing WCS 5.3.502 with this workflow:
SIP audio call → published stream → outgoing RTMP push
Our application needs to terminate an old call and its RTMP push, then safely allow a replacement. The replacement has a different callId and push mediaSessionId, but may reuse the same stream name and RTMP destination.
The difficult case is an uncertain cleanup result:
Could you clarify the following for this version?
If this requires a newer WCS version, an extension, or a different stream lifecycle design, please identify the supported option.
Thank you.
SIP audio call → published stream → outgoing RTMP push
Our application needs to terminate an old call and its RTMP push, then safely allow a replacement. The replacement has a different callId and push mediaSessionId, but may reuse the same stream name and RTMP destination.
The difficult case is an uncertain cleanup result:
- Our application sends call/terminate or push/terminate.
- WCS may receive and begin processing the request.
- The HTTP response is lost, times out, or our application restarts.
- A later lookup may return 404, but we need to establish whether any old teardown, callback or automatic retry could still affect a replacement.
Could you clarify the following for this version?
- Completion semantics: Does HTTP 200 from either termination endpoint mean teardown is fully complete, or can asynchronous cleanup continue afterward? What does a subsequent 404 establish?
- Supported completion mechanism: Is there an operation status, event, callback, Java API or other supported mechanism that confirms the original cleanup has finished—including relevant delayed callbacks and push-restoration activity?
- Replacement safety: What prevents delayed work associated with the old call/push from removing or interfering with a replacement that reuses the same stream name or RTMP destination? Are unique call and push identifiers sufficient, or is additional coordination required?
- Recovery after uncertainty: What is the recommended sequence after a lost response or application restart? We need to avoid blindly retrying a destructive operation or treating a fixed waiting period as proof of completion.
- Testing: Is there a supported way to delay teardown or its callbacks in a non-production installation so we can verify replacement safety and confirm that another active stream remains unaffected?
If this requires a newer WCS version, an extension, or a different stream lifecycle design, please identify the supported option.
Thank you.