Ghost session after WCS 5.2.1109 update

[SLM]

After updating to WCS 5.2.1109 and checking the demo's in the admin console to see if everything works, a ghost session is left on the server which I cannot kill with /rest-api/connection/terminate

Session info is limited to the following:
{
"appKey": "defaultApp",
"sessionId": "xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx",
"sipRegisterRequired": false,
"sipLogin": "xxxxxxxxxxxx",
"sipPort": 0,
"width": 0,
"height": 0,
"supportedResolutions": "0x0",
"useDTLS": true,
"useWsTunnel": false,
"useWsTunnelPacketization2": false,
"msePacketizationVersion": 1,
"useBase64BinaryEncoding": false,
"mediaProviders": [
"WebRTC"
],
"authToken": "xxxxxx-xxxx-xxxxx-xxxx-xxxxx",
"keepAlive": false
}

Normal sessions also contain an authtoken with IP, client info, origin and other info.

This session does not time out, nor can it be terminated with the rest api (returns normal HTTP 200 code with empty response).

This is the case on both EC2 instances that have been successfully updated to 1109 version yesterday. Every other session is terminated normally.

 

[Max]

Try this setting in flashphoner.properties:

webrtc_pre_init=false

The pre initializing was added in 5.2.1105
This looks like pre-initializing issue.

Stream recording - Web Call Server 5.2 - EN - Flashphoner Documentation

docs.flashphoner.com

 

[Max]

We reproduced the issue and raised a ticket WCS-3407 to fix it. Will let you know results here. Use the workaround mentioned above as temporary solution.

 

[SLM]

Thanks Max

 

[Max]

WCS-3407 has been fixed in build 5.2.1141.

 

[SLM]

Unfortunately, this issue is back in FF version 1193.

 

[Max]

Good day.
We reproduced the issue and raised the ticket WCS-3481.
You have two options to workaround:
1. This session does not affect the server functions, so you can use the latest build
2. Or, if this concerns you, please downgrade to 5.2.1141.

 

[Max]

We fixed the issue in build 5.2.1202. Please update and check.