The screen publishing (used the sample code provied) works for host with role 100 but not for guest (role 50, auto promote on). On the same machine, same browser when I swich to host , screen publishing works When the guest start the publish, the grey pop up comes up but stays on the toolbar. Does not show the options.
I also tried to upgrade guest to owner using room console but no difference. So it is not classic permissions issue. Please see below addin and flashlogs. I am on windows 7, premium, x64, firefox.
FLASHLOG
--
Mon Mar 21 04:46:59 GMT-0500 2011 LCCS SDK Version : 1.3.7.1 Player Version : WIN 10,2,152,32
04:46:59 GMT-0500 requestInfo https://collaboration.adobelivecycle.com/company1/room1?exx=eDpLYWMgS01NOjp2aWRlb3dhbGtpbjpLYWMgS01N...
Warning: Domain collaboration.adobelivecycle.com does not specify a meta-policy. Applying default meta-policy 'master-only'. This configuration is deprecated. See http://www.adobe.com/go/strict_policy_files to fix this problem.
04:47:01 GMT-0500 #TicketService# ticket received: echguubp0dfa
04:47:01 GMT-0500 Getting FMS at https://na2.collaboration.adobelivecycle.com/fms?ticket=echguubp0dfa&proto=rtmfp, attempt #1/3
04:47:01 GMT-0500 result: <fms>
<origin>fms2.acrobat.com</origin>
<proto_ports>rtmfp:1935,rtmps:443</proto_ports>
<retry_attempts>2</retry_attempts>
</fms>
04:47:01 GMT-0500 protocols: [object ProtocolPortPair],[object ProtocolPortPair]
04:47:01 GMT-0500 [attempt 1 of 2] Connecting to 0/1: rtmfp://fms2.acrobat.com/cocomo/na2-sdk-44ee8d22-631e-4191-b7c7-51cb0f21e8d4/room1 #startProtosConnect#
04:47:02 GMT-0500 tempNetStatusHandler 0/2,NetConnection.Connect.Success
04:47:02 GMT-0500 isTunneling? false
04:47:02 GMT-0500 is using RTMPS? false
04:47:02 GMT-0500 RECEIVED LOGIN AT SESSION
04:47:02 GMT-0500 .user descriptor from server [object]
04:47:02 GMT-0500 \\
04:47:02 GMT-0500 .role [number]= 5
04:47:02 GMT-0500 .userID [string]= EXT-company1-KAC KMM
04:47:02 GMT-0500 .displayName [string]= Kac KMM
04:47:02 GMT-0500 .affiliation [number]= 5
04:47:02 GMT-0500 RECEIVENODES UserManager
04:47:02 GMT-0500 receiveAllSynchData UserManager
04:47:02 GMT-0500 checkManagerSync:[object UserManager]
04:47:02 GMT-0500 RECEIVENODES FileManager
04:47:02 GMT-0500 receiveAllSynchData FileManager
04:47:02 GMT-0500 checkManagerSync:[object FileManager]
04:47:02 GMT-0500 RECEIVENODES AVManager
04:47:02 GMT-0500 receiveAllSynchData AVManager
04:47:02 GMT-0500 checkManagerSync:[object StreamManager]
04:47:02 GMT-0500 RECEIVENODES RoomManager
04:47:02 GMT-0500 receiveAllSynchData RoomManager
04:47:02 GMT-0500 checkManagerSync:[object RoomManager]
04:47:03 GMT-0500 RECEIVENODES company1_simplechat
04:47:03 GMT-0500 receiveAllSynchData company1_simplechat
04:47:03 GMT-0500 RECEIVENODES company1_note
04:47:03 GMT-0500 receiveAllSynchData company1_note
04:47:26 GMT-0500 RECEIVENODES company1_simplechat
04:47:26 GMT-0500 receiveAllSynchData company1_simplechat
04:47:26 GMT-0500 RECEIVENODES FileManager
04:47:26 GMT-0500 receiveAllSynchData FileManager
04:47:26 GMT-0500 RECEIVENODES AVManager
04:47:27 GMT-0500 receiveAllSynchData AVManager
04:47:27 GMT-0500 RECEIVENODES UserManager
04:47:27 GMT-0500 receiveAllSynchData UserManager
04:47:27 GMT-0500 RECEIVENODES RoomManager
04:47:27 GMT-0500 receiveAllSynchData RoomManager
04:47:27 GMT-0500 #UserQueue knocking_UserQueue# You do not have permission to manage the queue.
04:47:27 GMT-0500 mainNetStatusHandler: NetGroup.Connect.Success
04:47:27 GMT-0500 NetGroup Creation Successful
04:47:27 GMT-0500 NetGroup Creation Successful
04:47:27 GMT-0500 mainNetStatusHandler: NetGroup.Connect.Success
04:47:27 GMT-0500 NetGroup Creation Successful
04:47:27 GMT-0500 NetGroup Creation Successful
Mon Mar 21 04:49:20 GMT-0500 2011 LCCS SDK Version : 1.3.7.1 Player Version : WIN 10,2,152,32
04:49:20 GMT-0500 requestInfo https://collaboration.adobelivecycle.com/company1/room1?exx=eDpLYWMgS01NOjp2aWRlb3dhbGtpbjpLYWMgS01N...
Warning: Domain collaboration.adobelivecycle.com does not specify a meta-policy. Applying default meta-policy 'master-only'. This configuration is deprecated. See http://www.adobe.com/go/strict_policy_files to fix this problem.
04:49:21 GMT-0500 #TicketService# ticket received: jc20qa9lhkye
04:49:21 GMT-0500 Getting FMS at https://na2.collaboration.adobelivecycle.com/fms?ticket=jc20qa9lhkye&proto=rtmfp, attempt #1/3
04:49:21 GMT-0500 result: <fms>
<origin>fms2.acrobat.com</origin>
<proto_ports>rtmfp:1935,rtmps:443</proto_ports>
<retry_attempts>2</retry_attempts>
</fms>
04:49:21 GMT-0500 protocols: [object ProtocolPortPair],[object ProtocolPortPair]
04:49:21 GMT-0500 [attempt 1 of 2] Connecting to 0/1: rtmfp://fms2.acrobat.com/cocomo/na2-sdk-44ee8d22-631e-4191-b7c7-51cb0f21e8d4/room1 #startProtosConnect#
04:49:22 GMT-0500 tempNetStatusHandler 0/2,NetConnection.Connect.Success
04:49:22 GMT-0500 isTunneling? false
04:49:22 GMT-0500 is using RTMPS? false
04:49:22 GMT-0500 RECEIVED LOGIN AT SESSION
04:49:22 GMT-0500 .user descriptor from server [object]
04:49:22 GMT-0500 \\
04:49:22 GMT-0500 .affiliation [number]= 5
04:49:22 GMT-0500 .userID [string]= EXT-company1-KAC KMM
04:49:22 GMT-0500 .role [number]= 5
04:49:22 GMT-0500 .displayName [string]= Kac KMM
04:49:22 GMT-0500 RECEIVENODES UserManager
04:49:22 GMT-0500 receiveAllSynchData UserManager
04:49:22 GMT-0500 checkManagerSync:[object UserManager]
04:49:22 GMT-0500 RECEIVENODES FileManager
04:49:22 GMT-0500 receiveAllSynchData FileManager
04:49:22 GMT-0500 checkManagerSync:[object FileManager]
04:49:22 GMT-0500 RECEIVENODES AVManager
04:49:22 GMT-0500 receiveAllSynchData AVManager
04:49:22 GMT-0500 checkManagerSync:[object StreamManager]
04:49:22 GMT-0500 RECEIVENODES RoomManager
04:49:22 GMT-0500 receiveAllSynchData RoomManager
04:49:22 GMT-0500 checkManagerSync:[object RoomManager]
04:49:23 GMT-0500 RECEIVENODES company1_simplechat
04:49:23 GMT-0500 receiveAllSynchData company1_simplechat
04:49:23 GMT-0500 RECEIVENODES company1_note
04:49:23 GMT-0500 receiveAllSynchData company1_note
04:49:31 GMT-0500 RECEIVENODES company1_simplechat
04:49:31 GMT-0500 receiveAllSynchData company1_simplechat
04:49:31 GMT-0500 RECEIVENODES FileManager
04:49:31 GMT-0500 receiveAllSynchData FileManager
04:49:31 GMT-0500 RECEIVENODES AVManager
04:49:31 GMT-0500 receiveAllSynchData AVManager
04:49:31 GMT-0500 RECEIVENODES UserManager
04:49:31 GMT-0500 receiveAllSynchData UserManager
04:49:31 GMT-0500 RECEIVENODES RoomManager
04:49:31 GMT-0500 mainNetStatusHandler: NetGroup.Connect.Success
04:49:31 GMT-0500 NetGroup Creation Successful
04:49:31 GMT-0500 NetGroup Creation Successful
04:49:31 GMT-0500 receiveAllSynchData RoomManager
04:49:31 GMT-0500 #UserQueue knocking_UserQueue# You do not have permission to manage the queue.
04:49:39 GMT-0500 #AddInLocalConnection# connected to Cocomo0
04:49:42 GMT-0500 #AddinLocalConnection# calling installService: domain:company1.com, _lcName:Cocomo0, fuzzedDomain:company1.com, url:https://collaboration.adobelivecycle.com/static/screenshare/screenshareshell_player9_sgn.swf, version:Windows
04:49:42 GMT-0500 #AddInLocalConnection# onStatus:null, status
04:49:42 GMT-0500 #AddInLocalConnection# InstallStatus: Open.Success, version:undefined
04:53:51.322:[DEBUG]:com.company2.company1.logs.Config:Logging - TraceTarget initialized, filters: [com.company2.company1.logs.Config,Array,com.company2.company1.applications.*,int]
04:53:51.429:[DEBUG]:com.company2.company1.applications.Chat_Host:Loading policy file from company1.com/crossdomain.xml
04:53:51.430:[DEBUG]:com.company2.company1.applications.Chat_Host:Loaded policy file
04:53:51.432:[DEBUG]:com.company2.company1.applications.Chat_Host:Flex variables fullName = Kac KMM
04:53:51.433:[DEBUG]:com.company2.company1.applications.Chat_Host:Flex variables emailID =
04:53:51.434:[DEBUG]:com.company2.company1.applications.Chat_Host:Flex variables roomURL = https://collaboration.adobelivecycle.com/company1/room1
04:53:51.436:[DEBUG]:com.company2.company1.applications.Chat_Host:Flex variables authToken = exx=eDpLYWMgS01NOjp2aWRlb3dhbGtpbjpLYWMgS01NOnNhY2g6NTpjODMzMjZlNDg3Nzg4NTNjY2FjNzE5YjgyMjg3MzlkMDQyM2I3Nzdk
04:53:51.437:[DEBUG]:com.company2.company1.applications.Chat_Host:Flex variables langauge =
04:53:51.614:[DEBUG]:com.company2.company1.applications.Chat_Host:Mon Mar 21 04:53:51 GMT-0500 2011 LCCS SDK Version : 1.3.7.1 Player Version : WIN 10,2,152,32
04:53:51.620:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:51 GMT-0500 requestInfo https://collaboration.adobelivecycle.com/company1/room1?exx=eDpLYWMgS01NOjp2aWRlb3dhbGtpbjpLYWMgS01N...
Warning: Domain collaboration.adobelivecycle.com does not specify a meta-policy. Applying default meta-policy 'master-only'. This configuration is deprecated. See http://www.adobe.com/go/strict_policy_files to fix this problem.
04:53:53.125:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 #TicketService# ticket received: ul1d27q66hkw
04:53:53.127:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 Getting FMS at https://na2.collaboration.adobelivecycle.com/fms?ticket=ul1d27q66hkw&proto=rtmfp, attempt #1/3
04:53:53.272:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 result: <fms>
<origin>fms2.acrobat.com</origin>
<proto_ports>rtmfp:1935,rtmps:443</proto_ports>
<retry_attempts>2</retry_attempts>
</fms>
04:53:53.277:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 protocols: [object ProtocolPortPair],[object ProtocolPortPair]
04:53:53.281:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 [attempt 1 of 2] Connecting to 0/1: rtmfp://fms2.acrobat.com/cocomo/na2-sdk-44ee8d22-631e-4191-b7c7-51cb0f21e8d4/room1 #startProtosConnect#
04:53:53.876:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 tempNetStatusHandler 0/2,NetConnection.Connect.Success
04:53:53.877:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 isTunneling? false
04:53:53.878:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:53 GMT-0500 is using RTMPS? false
04:53:54.064:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 RECEIVED LOGIN AT SESSION
04:53:54.066:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 .user descriptor from server [object]
04:53:54.067:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 \\
04:53:54.068:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 .affiliation [number]= 5
04:53:54.068:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 .role [number]= 5
04:53:54.069:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 .userID [string]= EXT-company1-KAC KMM/3
04:53:54.070:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 .displayName [string]= Kac KMM 3
04:53:54.426:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 RECEIVENODES UserManager
04:53:54.429:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 receiveAllSynchData UserManager
04:53:54.435:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 checkManagerSync:[object UserManager]
04:53:54.437:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 RECEIVENODES FileManager
04:53:54.438:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 receiveAllSynchData FileManager
04:53:54.441:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 checkManagerSync:[object FileManager]
04:53:54.442:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 RECEIVENODES AVManager
04:53:54.443:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 receiveAllSynchData AVManager
04:53:54.446:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 checkManagerSync:[object StreamManager]
04:53:54.591:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 RECEIVENODES RoomManager
04:53:54.604:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 receiveAllSynchData RoomManager
04:53:54.606:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 checkManagerSync:[object RoomManager]
04:53:54.994:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 RECEIVENODES company1_simplechat
04:53:54.995:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:54 GMT-0500 receiveAllSynchData company1_simplechat
04:53:55.021:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:55 GMT-0500 RECEIVENODES company1_note
04:53:55.032:[DEBUG]:com.company2.company1.applications.Chat_Host:04:53:55 GMT-0500 receiveAllSynchData company1_note
04:56:20.305:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:20 GMT-0500 #UserQueue knocking_UserQueue# You do not have permission to manage the queue.
04:56:24.558:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:24 GMT-0500 RECEIVENODES company1_simplechat
04:56:24.562:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:24 GMT-0500 receiveAllSynchData company1_simplechat
04:56:24.563:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:24 GMT-0500 RECEIVENODES FileManager
04:56:24.576:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:24 GMT-0500 receiveAllSynchData FileManager
04:56:25.074:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 RECEIVENODES AVManager
04:56:25.106:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 receiveAllSynchData AVManager
04:56:25.108:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 RECEIVENODES UserManager
04:56:25.137:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 mainNetStatusHandler: NetGroup.Connect.Success
04:56:25.139:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 NetGroup Creation Successful
04:56:25.140:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 NetGroup Creation Successful
04:56:25.141:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 mainNetStatusHandler: NetGroup.Connect.Success
04:56:25.142:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 NetGroup Creation Successful
04:56:25.143:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 NetGroup Creation Successful
04:56:25.144:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 mainNetStatusHandler: NetGroup.Connect.Success
04:56:25.145:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 NetGroup Creation Successful
04:56:25.145:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 NetGroup Creation Successful
04:56:25.258:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 receiveAllSynchData UserManager
04:56:25.259:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 RECEIVENODES RoomManager
04:56:25.261:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:25 GMT-0500 receiveAllSynchData RoomManager
04:56:34.958:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:34 GMT-0500 #AddInLocalConnection# connected to Cocomo0
04:56:37.731:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:37 GMT-0500 #AddinLocalConnection# calling installService: domain:company1.com, _lcName:Cocomo0, fuzzedDomain:company1.com, url:https://collaboration.adobelivecycle.com/static/screenshare/screenshareshell_player9_sgn.swf, version:Windows
04:56:37.766:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:37 GMT-0500 #AddInLocalConnection# onStatus:null, status
04:56:37.802:[DEBUG]:com.company2.company1.applications.Chat_Host:04:56:37 GMT-0500 #AddInLocalConnection# InstallStatus: Open.Success, version:undefined
Views
Replies
Total Likes
Hi JasonNYNY,
Taking a quick look at the logs, it seems that you are trying to share the screen with a role of 5 (Audience).
04:47:02 GMT-0500 RECEIVED LOGIN AT SESSION
04:47:02 GMT-0500 .user descriptor from server [object]
04:47:02 GMT-0500 \\
04:47:02 GMT-0500 .role [number]= 5
04:47:02 GMT-0500 .userID [string]= EXT-company1-KAC KMM
04:47:02 GMT-0500 .displayName [string]= Kac KMM
04:47:02 GMT-0500 .affiliation [number]= 5
Would you mind trying again and making sure that the role is set to 50 not 5?
You need to have a role of 100 (Host) or 50 (Participant) to share the screen.
Thanks,
Julien
LCCS Quality Engineering
Views
Replies
Total Likes
Hi Jason,
Usually, when you have a role of 5 coming in, it means you have
"guestsMustKnock" in the roomManager set to true - is this the case here?
thanks
nigel
Views
Replies
Total Likes
Julien: No, the role is 50. The log statements do not get updated with new role. I have auto promote as true so by the time I call publish(), the role is 50. I printed it and confirmed that it is 50.
Nigel: You are right. I am using knocking feature.
Here is the weird thing, when I hit the start button when the gray pop-up comes up, magically 2nd guest with the same name(with addition of 2 in the name) appears in the queue. I accept this guest but he/she does not show up in the room console. It is the ghost This happens only for the first time. When I hit stop then start again, the ghost does not appear. If I refresh, then for the first start the ghost appears.
I really do not understand what I can do next to debug this.
Views
Replies
Total Likes
Interesting. Unfortunately, it seems as though there's a bug in LCCS around
the knocking queue and screensharing. We'll take a look at it, but our next
release is coming relatively soon, and we might not have time to get this
in. In the meantime, could your host turn off knocking when the user comes
into the room, and see if it works?
thanks for bringing this to our attention - we take bugs very seriously,
and everything you guys do to report them really helps.
nigel
Views
Replies
Total Likes
Nigel,
Shoot..that is what I was afraid of. A bug!
I have to use the knocking feature and the way the code is structured, I can not just turn off the knocking and test the screensharing for the guest. I will end up using sample code from sdk and build a new client for the same room and test it. Well, in that case, you may be able to confirm me faster if the guest with role 50 is able to share the screen in your test set up. Does that work for sure? Has it been tested?
Now the bigger problem, is there a creative workaround to use knocking with screensharing for guest? Any workarounds? If I change the guest to owner in the code just before publishing and then change it back to guest after the screenshare.close(), will that work?
Views
Replies
Total Likes
Nigel,
When I make guestmustknock false the the guest is able to share the screen.
Although our whole use case is based on the guest knocking. In our inital prototype , we did not have guest queue implemented so we didn't thorughly test your product. Now we are comitted to using LCCS but the key feature is not workinng for us. Please either suggest a workaround and when you plan to fix the bug. I understand you must have a lot on your plate but we need to figure out how to proceed.
Thanks.
Views
Replies
Total Likes
Hi there,
We're definitely looking to try to fix this one. It would be a couple weeks
before you got the fix (unfortunately, this requires an update to the
service, not just the SDK), assuming we can get it in (right now, it looks
like we will). We'll let you know if anything changes on this front.
thanks
nigel
Views
Replies
Total Likes
Nigel,
Thanks for lot for taking this one more thing on your plate.
- Let me know if you need any help in testing, even if it is directly from engineering.
- How do you deliver this to me? You have a new release coming up in few weeks?
Views
Replies
Total Likes
Hi there,
Good news - as of Monday, the fix for your issue was checked into our
testing lab environment. So far so good - it seems to resolve the problem.
This is a fix to the service itself (and not the SWC) so unfortunately
you'll have to wait until the release happens (mid April, if all goes
according to schedule). At that point, your issue should just magically
vanish. =)
thanks again for taking the time to report this bug - this sort of
community feedback is vital to the strength of the service.
nigel
Views
Replies
Total Likes
This issue has been fixed in the latest build.
Thanks a lot LCCS team!
Views
Replies
Total Likes
w00t! Glad this worked for you. Thanks again for reporting.
nigel
Views
Replies
Total Likes
Views
Likes
Replies