Hello Daniel,
When you change ports from its default 5080/1935 to something else, you might
want to change it in four places, wherever applicable:
1. Firewall hardware: policy
2. OS firewall: policy
OpenMeetings: 3. config.xml and 4. red5.properties
Thank you.
Sincerely,
Hemant K. Sabat
Cos
I just changed the port 5080 to 80 in config.xml which caused the
network testing to stop working. It looks like it is always searching
for port 5080 to do the tests.
When I went back to port 5080 it started working again.
Thanks,
Dan
On 09/30/2016 11:30 AM, Maxim Solodovnik wrote:
Actua
Actually NetworkTesting should read config.xml to be able to check the
exact ports/paths as OM will use
so I would appreciate detailed configuration to reprobuce the issue
On Fri, Sep 30, 2016 at 11:27 AM, Daniel Baker
wrote:
> Yes I changed the config.xml file.
>
>
> Since port forwarding is w
Yes I changed the config.xml file.
Since port forwarding is working ok now I just changed it back to 5080.
I could see from the error report it was looking for port 5080.
So the Connection testing is working as expected now.
Thanks,
Dan
On 09/29/2016 11:00 PM, Maxim Solodovnik wrote
Great!
Thanks for sharing :)
On Thu, Sep 29, 2016 at 12:33 PM, Peter Wallace
wrote:
> Hi
>
> No Worries, we worked out a Plan B.
>
> You just open a second browser instance to the same meeting room on the
> second screen with no video or audio, it then becomes the whiteboard screen
> and the fir
have you changed ports in config.xml?
On Thu, Sep 29, 2016 at 9:33 PM, Daniel Baker
wrote:
> Hi,
>
>
> I'm using OpenMeetings Version:3.1.2 Revision1756072
>
>
>
> When I perform a test of the ping, jitter,download and upload they fail.
>
>
> The RTMP port test works ok.
>
>
> Are th
Hi,
I'm using OpenMeetings Version:3.1.2 Revision1756072
When I perform a test of the ping, jitter,download and upload they fail.
The RTMP port test works ok.
Are the ping, jitter,download and upload ports always working over port
5080.
I have changed the default port 50
Great
Thanks for the feedback
WBR, Maxim
(from mobile, sorry for the typos)
On Sep 29, 2016 17:00, "Daniel Baker" wrote:
> It turns out the problem was when port forwarding from the router I had
> to enable TCP/UDP then it worked.
>
>
> There are a couple of other problems but will write th
It turns out the problem was when port forwarding from the router I had
to enable TCP/UDP then it worked.
There are a couple of other problems but will write those up in
another thread.
Thanks,
Dan
On 09/28/2016 07:48 AM, Maxim Solodovnik wrote:
In case of option 1 you don't need
