Thanks
Will double-check

On Fri, Apr 13, 2018 at 5:23 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Please file JIRA :)
>
> On Fri, Apr 13, 2018 at 5:22 PM, Peter Dähn <da...@vcrp.de> wrote:
>
>> unfortunately yes....
>>
>>
>> Am 13.04.2018 um 11:34 schrieb Maxim Solodovnik:
>>
>>> Is it reproducible using latest 4.0.3 version?
>>>
>>> On Fri, Apr 13, 2018 at 4:20 PM, Peter Dähn <da...@vcrp.de> wrote:
>>>
>>> Hi Maxim,
>>>>
>>>> this helped Stephan so far. Thank you.
>>>>
>>>> There is one thing left...
>>>>
>>>> We try to use kick-funktion in roomWebService...
>>>>
>>>> By now (OM 3.0.7) we use a function in the integration to kick a
>>>> specific
>>>> user out of the room. Now (OM 4.0.2) kick-function seems to kick out all
>>>> users. This would be ok, but it isn't working. We get "sucess", but
>>>> users
>>>> stay in room. Is it the right function or do we miss something else?
>>>>
>>>> See also "kick"-part of openmeetings.log
>>>>
>>>> /--------------------------------------//
>>>> // INFO 04-13 11:07:33.226 o.a.c.s.o.a.o.w.R.R.RoomWebService:276
>>>> [0.0-5080-exec-1] - Inbound Message//
>>>> //----------------------------//
>>>> //ID: 949//
>>>> //Address: http://HOST:5080/openmeetings/services/RoomService?wsdl//
>>>> //Http-Method: GET//
>>>> //Content-Type: //
>>>> //Headers: {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*;
>>>> q=.2],
>>>> cache-control=[no-cache], connection=[keep-alive], Content-Type=[null],
>>>> host=[HOST:5080], pragma=[no-cache], user-agent=[Java/1.8.0_161]}//
>>>> //--------------------------------------//
>>>> // INFO 04-13 11:07:33.390 o.a.c.s.o.a.o.w.R.R.RoomWebService:276
>>>> [0.0-5080-exec-2] - Inbound Message//
>>>> //----------------------------//
>>>> //ID: 950//
>>>> //Address: http://HOST:5080/openmeetings/services/RoomService//
>>>> //Encoding: UTF-8//
>>>> //Http-Method: POST//
>>>> //Content-Type: text/xml; charset=utf-8//
>>>> //Headers: {Accept=[text/xml, multipart/related],
>>>> cache-control=[no-cache], connection=[keep-alive], Content-Length=[265],
>>>> content-type=[text/xml; charset=utf-8], host=[HOST:5080],
>>>> pragma=[no-cache], SOAPAction=[""], user-agent=[JAX-WS RI 2.2.6b21
>>>> svn-revision#12959]}//
>>>> //Payload: <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="
>>>> http://schemas.xmlsoap.org/soap/envelope/";><S:Body><ns2:*kick*
>>>> xmlns:ns2="
>>>> http://webservice.openmeetings.apache.org/";><sid>SOME
>>>> NUMBER</sid><id>5</id></ns2:kick></S:Body></S:Envelope>//
>>>> //--------------------------------------//
>>>> //DEBUG 04-13 11:07:33.449 o.a.o.d.u.AuthLevelUtil:42 [0.0-5080-exec-2]
>>>> -
>>>> Level Soap :: [GRANTED]//
>>>> // INFO 04-13 11:07:33.459 o.a.c.s.o.a.o.w.R.R.RoomWebService:276
>>>> [0.0-5080-exec-2] - Outbound Message//
>>>> //---------------------------//
>>>> //ID: 950//
>>>> //Response-Code: 200//
>>>> //Encoding: UTF-8//
>>>> //Content-Type: text/xml//
>>>> //Headers: {}//
>>>> //Payload: <soap:Envelope xmlns:soap="http://schemas.xml
>>>> soap.org/soap/envelope/"><soap:Body><ns2:*k**ickResponse* xmlns:ns2="
>>>> http://webservice.openmeetings.apache.org/";><retu
>>>> rn><message>*Kicked*</message><type>*SUCCESS*</type></
>>>> return></ns2:kickResponse></soap:Body></soap:Envelope>//
>>>> //--------------------------------------//
>>>> /
>>>>
>>>> Greetings Peter
>>>>
>>>> Am 11.04.2018 um 18:27 schrieb Maxim Solodovnik:
>>>>
>>>> you need "special" url
>>>>> please check moodle plugin sources: https://github.com/openmeeting
>>>>> s/openmeetings-moodle-plugin/blob/master/mod_form.php#L215
>>>>>
>>>>> Ps please do not write personal emails ...
>>>>>
>>>>> WBR, Maxim
>>>>> (from mobile, sorry for the typos)
>>>>>
>>>>> On Wed, Apr 11, 2018, 23:20 Stephan Clemenz <clem...@vcrp.de <mailto:
>>>>> clem...@vcrp.de>> wrote:
>>>>>
>>>>>      Hi Maxim,
>>>>>
>>>>>      I am the guy who is working on the integration for OpenOLAT. The
>>>>>      integration is nearly complete besides the possibility to show and
>>>>>      download the recordings of a room. Your hint worked but the answer
>>>>>      from the server is not that what we need. When I call the
>>>>>      generated URL a whole HTML site is displayed. What we need (and
>>>>>      how it was in the past) is a direct link to the mp4 file.
>>>>>
>>>>>      The integration looks like this:
>>>>>
>>>>>      Here you get a list of all recordings of a room (works with 4.0).
>>>>>      If you click on "View" you can view the recording in OpenOLAT
>>>>>      (works only on 3.0):
>>>>>
>>>>>      Clicking on download the user can download the recording directly:
>>>>>
>>>>>      We need this functionality absolutely.
>>>>>
>>>>>      I did not get very deep in the webservice code of Openmeetings. So
>>>>>      I ask you if this functionality can be implemented more or less
>>>>>      easily?
>>>>>
>>>>>      Cheers,
>>>>>
>>>>>      Stephan
>>>>>
>>>>>      Am Mittwoch, 11. April 2018, 16:39:13 CEST schrieben Sie:
>>>>>
>>>>>      > -------- Weitergeleitete Nachricht --------
>>>>>
>>>>>      > Betreff: Re: Hint where to get recordings via webservice
>>>>>
>>>>>      > Datum: Wed, 11 Apr 2018 21:27:29 +0700
>>>>>
>>>>>      > Von: Maxim Solodovnik <solomax...@gmail.com
>>>>>      <mailto:solomax...@gmail.com>>
>>>>>
>>>>>      > Antwort an: dev@openmeetings.apache.org
>>>>>      <mailto:dev@openmeetings.apache.org>
>>>>>
>>>>>      > An: dev <dev@openmeetings.apache.org
>>>>>      <mailto:dev@openmeetings.apache.org>>
>>>>>
>>>>>      >
>>>>>
>>>>>      >
>>>>>
>>>>>      >
>>>>>
>>>>>      > You need to call
>>>>>
>>>>>      >
>>>>>      http://openmeetings.apache.org/openmeetings-webservice/apido
>>>>> cs/org/apache/op
>>>>>      <http://openmeetings.apache.org/openmeetings-webservice/apid
>>>>> ocs/org/apache/op>
>>>>>
>>>>>      >
>>>>>      enmeetings/webservice/UserWebService.html#getRoomHash-java.
>>>>> lang.String-org.a
>>>>>
>>>>>      >
>>>>>      pache.openmeetings.db.dto.user.ExternalUserDTO-org.apache.
>>>>> openmeetings.db.dt
>>>>>
>>>>>      > o.room.RoomOptionsDTO-
>>>>>
>>>>>      >
>>>>>
>>>>>      > method and pass recordingId instead of roomId
>>>>>
>>>>>      >
>>>>>
>>>>>      >
>>>>>      http://openmeetings.apache.org/openmeetings-db/apidocs/org/
>>>>> apache/openmeeti
>>>>>      <http://openmeetings.apache.org/openmeetings-db/apidocs/org/
>>>>> apache/openmeeti>
>>>>>
>>>>>      > ngs/db/dto/room/RoomOptionsDTO.html?is-external=true
>>>>>
>>>>>      > On Wed, Apr 11, 2018 at 9:22 PM, Peter Dähn <da...@vcrp.de
>>>>>      <mailto:da...@vcrp.de>> wrote:
>>>>>
>>>>>      > > Hi Maxim,
>>>>>
>>>>>      > >
>>>>>
>>>>>      > > old api (here 3.0.7) returned an url to get recordings from
>>>>>      rooms. We
>>>>>
>>>>>      > > could
>>>>>
>>>>>      > > not figure out, how this should work now (4.0.2). Any hint
>>>>>      about this?
>>>>>
>>>>>      > >
>>>>>
>>>>>      > > Greetings Peter
>>>>>
>>>>>
>>>>>
>>>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Reply via email to