Hi,Please notice that this time you've 'failed' very differently than
before. The debug log you supplied above does the redirect and retrieves
plenty of information from the LCCS service. For example:==== room list
for cprovider ====http_get:
https://na2.collaboration.adobelivecycle.com:443/app/content/accounts/jia/na2-sdk-a757f7e0-6ecf-450a-8959-3c08b63fdb84/meetings/?gak=cmVuZ2E
qbmExcioxMzM1ZWVlODNjOSpYMzg4TUJTVDc1N1EzMU5TSFRNNldEQzBXNA==myfirstroom::Wed,
14 Sep 11 07:03:11 -0400chatroom::Wed...
Hi Eric,Could you post the complete access_log line for that GET
request? I think that one on the items in the log line should be the
time it took the server to service the request. Furthermore, I think
that access_log will print out the line when it has completed servicing
the request so, at this point, we are looking at 15 minute download for
your 66Mb recording. I am not sure why your client debug log stopped,
but it could have been some timeout somewhere. Thanks,Nikola
Correct,The receiveLogin callback happens when LCCS service loads up the
archive zip and it's ready to go. There shouldn't be any substantial
delay in user experience after receiveLogin.Thanks,Nikola
Hi Eric,I suspect that on your previous tries archive zip was still not
fully downloaded by LCCS service from your WebDAV repository. Was this a
particularly large recording?In the client debug, you will see
"receiveLogin" only after the archive is ready on LCCS side.I will take
a peek at your logs on our servers and see if I can gather more valuable
information. In the meantime, I would suggest you look atyour WebDAV
server's logs; they may also contain some hints about what went
on.Thanks,Niko...
Hi Tilak,Ensure you are using the latest LCCS.php file. There was a
recent thread on it (http://forums.adobe.com/message/3975633#3975633),
to which I attached the latest revision file.Other than that, I am not
sure why your code throws the RTC. I just tried it and it worked for me
with PHP 5.3.8.Try with the latest LCCS.php and let us know how it
goes.Thanks,Nikola
If you send me an email with your playback url etc I could see if I can
find anything in our logs.15 minutes for 60Mb seems
excessive.Nikolanzezelj@adobe.com
Hi,There is not a whole lot we can do at this point.Please refer to the
following post for some ideas for getting around the
issue:http://forums.adobe.com/message/3916285?tstart=0#3916285Nikola
Hi there,Could you be more specific on "takes too long?" If playback
eventually starts then I doubt you are doing anything wrong.The only
"wrong" thing I could see is your WebDAV server. The question would be
how quickly LCCS service can download the recording file from your
server.Perhaps you could take some measurements on that front or compare
some log timestamps to estimate that time.Hope this helps,Nikola
Hi,Unfortunately, the answer to 2/ is no. Please refer to
http://learn.adobe.com/wiki/display/lccs/10.1+Overview for more
info.Essentially, LCCS service downloads the archive zip from your
WebDAV and serves it to your playback clients.Thanks,Nikola
Ah yes, I caught this one in July but somehow my fix didn't make its way
to the release branch. Again, good catch, I'll make sure it makes it out
in the next release.I am also attaching the latest version of our
lccs.php file to this thread. Thanks,Nikola
Thank you both on valuable input, and apologies on a delayed response.
We agree with you both and we will be looking to boost our error
checking with regards to the recording work flow. I am not sure when it
will happen but it is definitely on our radar.For now, if you have any
suggestions, ideas etc please reply to this thread.Thanks,Nikola
Not sure if I fully follow your "roles" question, but .... User roles
are already pre-defined, you only need to assign user a role via
authToken parameter. Please see
http://learn.adobe.com/wiki/display/lccs/5.3+Managing+room+settings#5.3Managingroomsettings-Changingauser%27srole
for more info on user roles.Hope this helps,Nikola
Hi, and welcome as well.You should check out 6.2. section of our online
wiki docs at
http://learn.adobe.com/wiki/display/lccs/6.2+Provisioning+roomsBut all
of it is a great read and it would be a nice introduction to LCCS.Nikola
Hi Jeff,Few things to note:1/ Your app snippet includes neither roomURL,
nor archiveID that you will find in our playback sample
(rtc:ConnectSessionContainer tag).2/ If you are just starting with a
playback implementation, I would begin with a guest playback approach
and get that working first. That would remove all this authentication
token stuff and make for a more simple code for you to debug.3/ Not sure
if I mentioned, we have some great recording docs at
http://learn.adobe.com/wiki/display/...
Hi,Recordings are completely independent from the rooms. You can even
delete a room and recordings will still work and be playable.You missed
my PlaybackAuthenticator question from my second post. I looked at the
logs and what I see is not looking like a proper request for recording
playback.Maybe posting a bit of your client code where you setup the
session container would help.Thanks,Nikola
Hi Jeff,On the second look through your logs I would question whether
you are using the PlaybackAuthenticator. Please note that the
PlaybackAuthenticator must be used instead of the usual
AdobeHSAuthenticator in playback applications.Hope this helps,Nikola
Hi Jeff,Have you checked the obvious stuff like:1/ is your repository
properly registered?2/ do you see this particular archive in your
repository?and 3/ is this a new archive? have you played it back
successfully before?Thanks,Nikola
Hi,Yes, autoLogin=false is a must for token authentication. Glad to be
of help.Invalid instance is yet another "not so helpful" error message.
I will look into it and see if we can fix it for next
release.Thanks,Nikola
Just curious why you have a null in the first debug line:09:10:30
GMT+0300 requestInfo
null?guk=ZzpudWxsOg==&mode=xml&x=0.2071044179610908Thanks,Nikola
Hi barisyesilcicek,In reference to the button that sets isRecording =
false, are you referring to the SDK's recording/playback demo
application? This client application is just a demo made as a reference
guide. Yes, isRecording is set to true to start a recording, and is set
to false to stop a recording, but this does not need to happen through
button clicks. It could be made 100% programmatic. Furthermore, if the
application is being recorded, the LCCS service will stop the recording
and publis...
Hi Davis,Your understanding of how the recording playback works is
fairly accurate.That said, we have never encountered as severe of a
dowload issue as "to make playback in this fashion impractical." Could
you be more specific? In particular, how large are your recording zip
files, and how long does it take to download them (or rather how long
does it take for you to see playback activity on the
client)?Thanks,Nikola
Hi Vishal,I just tried your WebDAV server and was able to publish a
recording of mine using authentication. Do let me know if you have been
successful as well.Looking forward to closing this thread Thanks,Nikola
Hi Vishal,Any luck with your WebDAV? Are you sure there are no logs on
your WebDAV for authentication use case? Did you use wireshark or any
other tool to sniff out the packets coming to your server?Thanks,Nikola
Hi Eyal,It's good to hear you got the digest authentication to work. I
hope that alleviates, at least a little, some of your security concerns.
The only thing I can offer at this time is for you to add an auth token
to your WebDAV url and change/validate it accordingly. It involves a bit
of work on your end but at this point is the only thing I can suggest.
Your original concern is definitely valid and has been taken note of on
our end. I am confident we will implement a fix in the medium-term t...
I have no idea why your WebDAV authentication would be failing. I am
using it for my testing all the time; we definitely support it. I would
strongly recommend you turn on as much verbose debugging on your WebDAV
server as possible and identify your problem in that manner. The only
suggestion I can think of is to try lower casing your authentication
credentials (just in case).Thanks,Nikola
Hi Vishal,I had a look at our production logs. I have several
suggestions:1/ I see "lots" of register-repository calls. You only need
to register-repository once; LCCS will store this information for any
subsequent recording usage. I would suggest registering somewhere in the
admin side of things. Perhaps you are already doing this and were just
sending repeat requests because recordings did not work yet. But I
thought it worth mentioning.2/ You are using both the WebDAV
authentication and a non...
