Caller cannot reconnect without restarting listener in SRTConnection

[noho501]

Question

Hi,

I have a question regarding the reconnect behavior with streamid.

My understanding is that setting a streamid should allow a caller to disconnect and reconnect without needing to restart the listener.
However, in my current implementation, once the caller disconnects, I must stop and restart the listener before the caller can connect again.

Is this the expected behavior, or is there a proper way to configure streamid to allow seamless reconnects?

Background / Tried Steps

URLs used:

Listener:

srt://192.168.2.39:9991?mode=listener&latency=500&streamid=myapp&rcvbuf=8388608&pkt_size=1316&tsbpd=1&sndbuf=8388608

Caller:

srt://192.168.2.39:9991?mode=caller&latency=500&streamid=myapp&rcvbuf=8388608&pkt_size=1316&tsbpd=1&sndbuf=8388608

---

Caller code snippet:

private func startStream() async throws {
    Task.detached(priority: .userInitiated) { [weak self] in
        guard let self else { return }
        try await self.connection.connect(streamURL)
        await self.stream.play()
    }
}

func stopPlayer() async {
    await stream.close()
    await removeAllOutput()
}

After calling stopPlayer(), I am unable to connect again. I must stop and restart the listener before the caller can reconnect.
The only log output when attempting to reconnect is:

18:13:12.342666/ D:SRT.sm: generateSocketID: : @677351440
18:13:22.382021/ D:SRT.sm: generateSocketID: : @677351439

Environment

iPad mini 7 - iOS 26
iPhone 16 Pro - iOS 26
Haishinkit main branch

Could you advise if there is a correct way to allow the caller to reconnect without restarting the listener?

Thank you for your guidance.

[shogo4405]

RTMP works that way, but I thought SRT might behave differently.
In the following table, the “Restrict” column for the SRTO_STREAMID section is set to pre.
https://github.com/Haivision/srt/blob/master/docs/API/API-socket-options.md#list-of-options

I understand that pre means the option must be configured before the connection is established.
So once the connection is established, it can no longer be changed — which matches the behavior I mentioned above.

Of course, it’s possible that I’m misunderstanding the specification, so if you have documentation on this, I’d appreciate it if you could share it.