please do not write personal emails :((
--------------------------------------
You are right, connection to "rtmp://localhost:1935/openmeetings" was not
rejected :(
Will be rejected since now, only connections to 'hibernate' scope are
allowed for unauthorized users :)))
It's success in OM 4.0.0, and then you can make video chat :)
But I don't think it's good, Have you any suggestion? Thanks!
This is expected, you can use OM in case you are authorized user :)))
On Sat, Sep 30, 2017 at 4:04 PM, xs zhong <xians...@gmail.com> wrote:
> Hi Maxim,
>
> Thank you for your patient:)
>
> Here are steps that how I connect to OM 4.0.0 using flex:
>
> First, login to OM:
> connect("rtmp://localhost:1935/openmeetings"); // success.
> call mobile.loginUser //get "sid", success in 4.0.0, failed in 3.3.x
> call mobile.getRooms //get "id", "type", "name" etc.. can't get these
> things in 3.3.x
>
> Second, connect to a room:
> //prepare parameters
> param.parentSid = sid;
> param.mobileClient = true;
> roomId = id;
> url = "rtmp://localhost:1935/openmeetings/" + roomId;
> ...
> //connection
> connect(url, param);
>
> It's success in OM 4.0.0, and then you can make video chat :)
> But I don't think it's good, Have you any suggestion? Thanks!
>
> WBR
>
> 2017-09-30 12:22 GMT+08:00 Maxim Solodovnik <solomax...@gmail.com>:
>
>> I'll double check Flex connect using 4.0.0 code, but I'm very much sure
>> connection attempt will be rejected
>>
>> Actually the call order should be:
>> 1) connect
>> 2) get connection success
>> 3) call mobile.login
>>
>> this is actually the way mobile client works
>>
>>
>> On Sat, Sep 30, 2017 at 11:13 AM, xs zhong <xians...@gmail.com> wrote:
>>
>>> Hi Maxim,
>>>
>>> I am sure that my client will be rejected in 3.3.x , but will connect
>>> successfully in 4.0.0(the same code you provided), due to the source code
>>> of login method in MobileService.java is different between them.
>>> 4.0.0:
>>> [image: 内嵌图片 1]
>>> 3.3.x:
>>> [image: 内嵌图片 2]
>>>
>>> It will create a stream client in 4.0.0 when I login OM server through
>>> by MobileService (rtmp connection), then I can connect to a room next step.
>>>
>>> So I'm curiously why your mobile client can connect successfully, I
>>> guess your client didn't use the MobileService to login OM server,right? If
>>> yes, why the OM still have the MobileService ?
>>>
>>> Sorry for my poor English, I have try my best to make you understand
>>> what I mean:(((
>>>
>>> WBR
>>>
>>> 2017-09-30 10:38 GMT+08:00 Maxim Solodovnik <solomax...@gmail.com>:
>>>
>>>> Hello xiansh,
>>>>
>>>> I have created new thread
>>>>
>>>> please check this code: https://github.com/apach
>>>> e/openmeetings/blob/master/openmeetings-core/src/main/java/o
>>>> rg/apache/openmeetings/core/remote/ScopeApplicationAdapter.java#L186
>>>>
>>>> I believe your client is being rejected
>>>> You have to provide additional connection parameters
>>>>
>>>> On Fri, Sep 29, 2017 at 3:26 PM, xs zhong <xians...@gmail.com> wrote:
>>>>
>>>>> Hello Maxim,
>>>>>
>>>>> Well, My mobile client connect to OM like this simple way:
>>>>>
>>>>> var nc:NetConnection = new NetConnection();
>>>>> nc.connect("rtmp://localhost:1935/openmeetings");
>>>>> nc.call("mobile.loginUser", response, login, password);
>>>>>
>>>>> The callback is {status=-1.0} in OM 3.3.x, but correct result
>>>>> returned in 4.0.0.
>>>>> Is my code in this way wrong?
>>>>>
>>>>> WBR
>>>>>
>>>>> 2017-09-29 15:47 GMT+08:00 Maxim Solodovnik <solomax...@gmail.com>:
>>>>>
>>>>>> Hello xiansh,
>>>>>>
>>>>>> I just have checked Mobile client can successfully connect to OM 3.3.x
>>>>>> OM 4.0.0 has some issues on disconnect and receiving video but now it
>>>>>> is fixed.
>>>>>>
>>>>>> What is your issue?
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 28, 2017 at 3:59 PM, xs zhong <xians...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi, Maxim,
>>>>>>>
>>>>>>> I have used 4.0.0 snapshot for Android app testing since 18th Sep.
>>>>>>> The connection between mobile and OM is OK now, and I found it's OK
>>>>>>> also in
>>>>>>> 3.0.7, but it's rejected in 3.3.0, 3.3.1 or 3.3.2 , Does OM support
>>>>>>> mobile
>>>>>>> client from 4.0.0? The source code of MobileService.java are different
>>>>>>> among them.
>>>>>>>
>>>>>>> According to the MobileService.java, the first step is landing OM,
>>>>>>> as the code "IConnection conn = Red5.getConnectionLocal();" in login
>>>>>>> method, is the only way to connect from mobile to OM for user login
>>>>>>> using
>>>>>>> NetConnection class in flash?
>>>>>>>
>>>>>>> But when the next step to connect to one room, it still have to use
>>>>>>> NetConnection again, it's duplicated, there will be two clients and
>>>>>>> connections. Or is there another way to login OM from Flash/AIR
>>>>>>> environment?
>>>>>>>
>>>>>>> Greetings xiansh
>>>>>>>
>>>>>>>
>>>>>>> 2017-09-22 20:07 GMT+08:00 Maxim Solodovnik <solomax...@gmail.com>:
>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> I need help with testing upcoming 4.0.0 release.
>>>>>>>> I believe it can be released as soon as Apache Wicket will release
>>>>>>>> next stable version of 8.0.0
>>>>>>>>
>>>>>>>> Could you please test most recent 4.0.0 snapshot
>>>>>>>> You can use our demo servers:
>>>>>>>>
>>>>>>>> https://om.alteametasoft.com:8443/next (powerfull server)
>>>>>>>> https://demo-openmeetings.apache.org/openmeetings (server
>>>>>>>> without enough resources :) the SLOW one :)) )
>>>>>>>>
>>>>>>>> Or test locally using nightly build: https://builds.apache.o
>>>>>>>> rg/view/M-R/view/OpenMeetings/job/openmeetings/
>>>>>>>>
>>>>>>>> Here is the testing plan you can use: http://openmeetings.apach
>>>>>>>> e.org/ManualTesting.html
>>>>>>>>
>>>>>>>> Thanks in advance!
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> WBR
>>>>>>>> Maxim aka solomax
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> WBR
>>>>>> Maxim aka solomax
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
