Session-terminate and support-session-restart clarifications

Hi,
i developed a custom webrtc client that communicate with Jitsi ecosystem. I can read and write the jitsi jingle, presence and others message and i can establish a working communication with peers.
But in random way i receive a jingle and a presence message like these:

<iq type='set' from='654@muc.meet.jitsi/focus' xmlns='jabber:client' id='ZTM1NjRkYmEtNTBiOC00NGY3LWJhYTEtMzU3ODZmM2JjYWUyQG1lZXQuaml0c2kvUThNVG91NGQANGRxUVItMzU0ODg5AH0woAvbu4tWGr+r3rCiV8U=' to='e3564dba-50b8-44f7-baa1-35786f3bcae2@meet.jitsi/Q8MTou4d'>
    <jingle action='session-terminate' sid='d0b11afm6g3gk' xmlns='urn:xmpp:jingle:1'>
        <reason>
            <expired />
            <text>Idle session timeout</text>
        </reason>
    </jingle>
</iq>
<presence xmlns='jabber:client' from='654@muc.meet.jitsi/focus' id='4dqQR-354891' to='e3564dba-50b8-44f7-baa1-35786f3bcae2@meet.jitsi/Q8MTou4d'>
    <etherpad xmlns='http://jitsi.org/jitmeet/etherpad'>654</etherpad>
    <versions xmlns='http://jitsi.org/jitmeet'>
        <component name='focus'>1.0.784</component>
    </versions>
    <conference-properties xmlns='http://jitsi.org/protocol/focus'>
        <property value='true' key='support-terminate-restart' />
        <property value='0' key='bridge-count' />
    </conference-properties>
    <c hash='sha-1' ver='Lg0vhCNhxjoeKJi2/hukdsizNWA=' node='http://jitsi.org/jicofo' xmlns='http://jabber.org/protocol/caps' />
    <x xmlns='http://jabber.org/protocol/muc#user'>
        <item affiliation='owner' role='moderator' jid='focus@auth.meet.jitsi/focus' />
    </x>
</presence>

And about 5-7 seconds later, jitsi close the websocket with the peer.

What exactly is meant by the “Idle session timeout” message and what should I do to avoid closing the websocket?

This is when you have a single participant in the room for more than 20 seconds, jicofo terminates the jingle session to stop the client from sending media to the conference as there is no point in doing that.

O, thanks for your reply.
I will find a solution with your information. :wink: