This content has been marked as final. Show 8 replies
Which client are you using. There are 2 - a JavaFX one that downloads a JNPL file and the full client that is downloaded and installed on the pc. The conferencing area of the bcentral page allows you to switch from one to the other. Try the one you are not using to see if it makes any difference. Timeouts can have lots of causes unfortunately so it is difficult to get a fix.
I am not sure which Java client customer is using.
I never requested customer to install any Java client, I am assuming customers will have a common Java installation, which is used by multiple softwares.
All of this unfortunately cannot happen while I am requesting customer to do owc with me. Perhaps there are some prerequisites needed which customers have to have
prior to joining a Beehive owc.
I am getting the same error message MX connection timed out.
(I am Oracle customer). My desktop running window 7, has latest JRE 7 update 21 installed. still getting the error.
Couldn't get beehive running, but no issue when using the old web conference RTC real-time collaboration from Oracle.
Any ideas what else I need to do to fix this. (Oracle customer support very much give up and frustrate too).
We found an issue when using the JavaFX web conference client settings - it requires a download and the system has a misconfigured URL - whcih we are scheduled to fix in the next maintenance window. Meantime, I suggest you download the client tool from the https://beehiveonline.orac.e.com/bcentral downloads page and use that as it des not require any download and therefor should be unaffected by the problem.
What I found is it looks like port 443 is open initially and then port 5224 is established to connect to the latest Oracle conferencing tool.
You can also use test page https://strtc.oracle.com/imtapp/app/nuf_sys.uix and then select the small run icon just under troubleshoot to test other issues.