We commented this part out, because this way it was connecting
directly to the correct port (it is not trying out the port which is
blocked in our case). But as you write, there is a cleaner solution to
this.
The problem with the timing out of the conversion was another one.
When calling the method "setUserObjectAndGenerateRoomHash", we
specified the externalUserId to be 0. This caused the user not to be
logged in correctly, with the consequence of not getting the needed
rights for the conversion (this is what I suspect). I guess the
externalUserId should be null or really an external number.
Thanks for your time and help, Sebastian!
Best wishes,
eu
On 8 Jul., 22:37, "
seba.wag...@gmail.com" <
seba.wag...@gmail.com>
wrote:
> where do you have got the documentation from to *comment out* things
> out of the config.xml?
> None of the params in the config.xml should be commented out.
>
> And leave <rtmphostlocal>XXX</rtmphostlocal> empty. That way the app
> connects automatically to the domain it has been loading from (Which
> actually might fix your media-timeout problem).
>
> Sebastian
>
> 2011/7/8 eu <
eugen.st...@gmail.com>:
>
>
>
>
>
>
>
>
>
> > And we commented out the rtmpport...
> > <!-- <rtmpport>1935</rtmpport> -->
>
> > On 8 Jul., 15:26, eu <
eugen.st...@gmail.com> wrote:
> >> In the config.xml we configured the tunnel port to be 80:
> >> <rtmphostlocal>XXX</rtmphostlocal>
> >> <rtmpTunnelport>80</rtmpTunnelport>
> >> <rtmpsslport>443</rtmpsslport>
> >> <red5httpport>80</red5httpport>
>
> >> We left all other settings in the config.xml untouched...
>
> >> I'm connecting to the webservice via:
http://XXX:80/openmeetings/services/RoomServicehttp://XXX:80/openmeet...
> Sebastian Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://
www.wagner-sebastian.com
>
seba.wag...@gmail.com