RTCSession Error

### Description

Element Web is fine with video and voice
When using ElementX on a mobile device, an error occurs
Sometimes you can talk for a few minutes, sometimes you can't get in and report an error,
Web and mobile are in a network,5Gwifi network speed stability is very good,
synapse and elementX are the latest versions
synapse built it,elementX didn't build it
The server is 16C32GB

RTCSession Error
The MembershipManager shut down because of the end condition: Error: Could not restart delayed event, even though delayed events are supported. tw: error sending request for url (https://chat.bitdu.love/_matrix/client/unstable/org.matrix.msc4140/delayed_events/syd_YkZjZSYxmnyWEACerjAg)

2025-04-15T20:26:57.029Z WARN livekit.transport rtc/transport.go:830 error reading data channel {"room": "!pLJrBmFowOYaQYdeyC:chat.test123.com", "roomID": "RM_nsG6Rpoota4y", "participant": "@nick:chat.test123.com:YKIXTBGXNH", "pID": "PA_bhtJgZptc4L4", "remote": false, "transport": "PUBLISHER", "label": "_lossy", "error": "[0xc00325a780] abort chunk, with following errors: (User Initiated Abort: Close called)"}
2025-04-15T20:26:57.029Z WARN livekit.transport rtc/transport.go:830 error reading data channel {"room": "!pLJrBmFowOYaQYdeyC:chat.test123.com", "roomID": "RM_nsG6Rpoota4y", "participant": "@nick:chat.test123.com:YKIXTBGXNH", "pID": "PA_bhtJgZptc4L4", "remote": false, "transport": "PUBLISHER", "label": "_reliable", "error": "[0xc00325a780] abort chunk, with following errors: (User Initiated Abort: Close called)"}
2025-04-15T20:26:57.032Z INFO livekit rtc/participant.go:1036 participant closing {"room": "!pLJrBmFowOYaQYdeyC:chat.test123.com", "roomID": "RM_nsG6Rpoota4y", "participant": "@nick:chat.test123.com:YKIXTBGXNH", "pID": "PA_bhtJgZptc4L4", "remote": false, "sendLeave": true, "reason": "CLIENT_REQUEST_LEAVE", "isExpectedToResume": false}

### Steps to reproduce

When using ElementX on a mobile device, an error occurs
Sometimes you can talk for a few minutes, sometimes you can't get in and report an error,
Web and mobile are in a network,5Gwifi network speed stability is very good,
synapse and elementX are the latest versions
synapse built it,elementX didn't build it

### Homeserver

chat.***

### Synapse Version

latest

### Installation Method

Docker (matrixdotorg/synapse)

### Database

PostgreSQL

### Workers

Single process

### Platform

ubuntu
16c32g

### Configuration

_No response_

### Relevant log output

```shell
2025-04-15T20:26:57.029Z WARN livekit.transport rtc/transport.go:830 error reading data channel {"room": "!pLJrBmFowOYaQYdeyC:chat.test123.com", "roomID": "RM_nsG6Rpoota4y", "participant": "@nick:chat.test123.com:YKIXTBGXNH", "pID": "PA_bhtJgZptc4L4", "remote": false, "transport": "PUBLISHER", "label": "_lossy", "error": "[0xc00325a780] abort chunk, with following errors: (User Initiated Abort: Close called)"}
2025-04-15T20:26:57.029Z WARN livekit.transport rtc/transport.go:830 error reading data channel {"room": "!pLJrBmFowOYaQYdeyC:chat.test123.com", "roomID": "RM_nsG6Rpoota4y", "participant": "@nick:chat.test123.com:YKIXTBGXNH", "pID": "PA_bhtJgZptc4L4", "remote": false, "transport": "PUBLISHER", "label": "_reliable", "error": "[0xc00325a780] abort chunk, with following errors: (User Initiated Abort: Close called)"}
2025-04-15T20:26:57.032Z INFO livekit rtc/participant.go:1036 participant closing {"room": "!pLJrBmFowOYaQYdeyC:chat.test123.com", "roomID": "RM_nsG6Rpoota4y", "participant": "@nick:chat.test123.com:YKIXTBGXNH", "pID": "PA_bhtJgZptc4L4", "remote": false, "sendLeave": true, "reason": "CLIENT_REQUEST_LEAVE", "isExpectedToResume": false}
```

### Anything else that would be useful to know?

_No response_

Start by tracing the RTCSession failure and the delayed_events request, then compare it with the referenced rtc/transport.go:830 and rtc/participant.go:1036 log entries. The report does not name an Element Call source file or test, so first establish a reproducible failure and identify whether the delayed event or LiveKit transport closes the session. Done means the failure cause is isolated and a regression test or clear reproduction confirms the fix.

Written by the indexing model from the issue text.