Problem joining the same Room twice with the same name while hooking RoomApp

[sangsoo]

Hi there.
I am hooking the RoomApp ConnectionStatusEvent to handle abnormal termination (chrome tab closing) while joining a conference (Room).
Basically, it works fine, but there is a problem when joining the same Room twice with the same name.
-----Version info-----
wcs_version=5.2.1616-fec542757a11bdc923ce635ffbbc73bde42092fa
wcs_client_version=2.0.228-2e846abc648713a73952eab99b4f5fc458edac77

1. when joining the same Room 2 times with the same name, the OnDataEvent send rest object call throws an exception internally with an http 500 error.
2. eventually, the receive rest object is not received after OnDataEvent proxy, so I can't proceed further.

- If something went wrong - server log processing the rest hook :

- When it's OK - Using default RoomApp server log :

What is the problem?
Thanks.

 

[Max]

Hello

Do you have similar issues with built in RoomApp without custom proxy?
Please do the following.

1. Launch tcpdump command before all the tests.
tcpdump -i any -B 10000 - w log.pcap
2. Make all tests and press CTRL+C to stop dumping.
3. Open log.pcap file in the Wireshark, filter HTTP traffic and make sure all HTTP traffic has been recorded properly.

Therefore you can find differences between your proxy implementation and built-in RoomApp.

Please send us two dump files via the Private form. We will also check.
1) log-built-in.pcap - when you test built-in RoomApp
2) log-proxy.pcap - when you test your proxy implementation

 

[sangsoo]

Thanks for the reply.
I was incorrectly handling the response body data after post processing during the hooking process.
It works fine now. Thanks.