« Back to Discussion

RE: USR_JOIN event provides incorrect values

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
USR_JOIN event provides incorrect values
meetingplace api usr_join eventservice usruid subscribeforallresources
Answer
1/6/12 11:04 AM
I am using the MeetingPlace EventService, I have Subscribed using subscribeForAllResources to the resourceType USER_BASED events specifically to
the eventType USR_JOIN.
 
I am successfully receiving the events when a user joins a meeting however the uniqueUserId is always 3 - for all meetings and for all users that join the meeting.
 
See example notification that i am receiving below - (see usrUId element)
<evt id="11871ccb-25cf-4309-a724-51b03f97601e" subId="5d77e68a-f5e5-4d5e-ba5c-5d4e74acc541" evtType="USR_JOIN" time="2011-12-08T16:27:39.003Z" mtgUId="694" ani="0123456987" usrUId="3" ability="SPEAKERPLUS" devId="6" partId="1" partName="Outdial(123456789542):987654321:JOE BLOGGS"/>
 
If i query MeetingPlace I can see that users have unique user Ids i.e. in the above example Joe Bloggs has a usrUId of 123, I would expect the above event to contain the element usrUId="123"
 
Any ideas of why the usrUId="3", i would expect that this would contain the unique userId of the user that trigger the event thereby enabling my application to use this value to get specific details on the user.
 
Thanks,

Hi Enda,

Is your usrUID = 3?

Thanks,
Adrienne

Hi Edna,

Are the meeting place events being created through your app or through the GUI?

Thanks,
Adrienne

Hi Enda,

Is your usrUID = 3?

Thanks,
Adrienne

 
Hi Adrienne,
 
Yes the usrUID is always been returned as 3 regardless of the user that has joined the meeting.
 
Thanks,
Enda

Hi Edna,

Are the meeting place events being created through your app or through the GUI?

Thanks,
Adrienne

 
Hi Adrienne,
 
I am subscribing to events on a meetingPlace node using the following 
 

ArrayOfShortEventTypeEnum eventTypes = enObjFactory.createArrayOfShortEventTypeEnum();
eventTypes.getShortEventTypeEnum().add(ShortEventTypeEnum.USR_JOIN);
eventTypes.getShortEventTypeEnum().add(ShortEventTypeEnum.USR_LEAVE);
SubscriptionInfo response = eventService.subscribeForAllResources(ResourceTypeEnum.USER_BASED, eventTypes, callbackInfo, expirationCalendarXML);

 
When an end user then either dials into a WebEx meeting or accepts a callback from the meeting the USR_JOIN event is raised by meetingPlace and sent to the URL specified in the callbackInfo object.
 
However the usrUID=3 for every user, Any ideas of what the issue is?
 
Thanks,
Enda

How are the users joining events?

They could be using the guest account to allow the app authentication.

How are the users joining events?

They could be using the guest account to allow the app authentication.

 
A meeting is created on WebEx by the host using their WebEx username and password.
The Host signs in to the meeting with his/her credentials.
 
Invited Users can then sign into the meeting by providing a name and an email address.
The WebEx meeting then callsback the user

Hi Adrienne,

Some further information that may help in the analysis of this scenario is detailed below.

I noted that If I programmatically generate a callback from a WebEx Meeting using the API Method ¿ outDialUser(), when the call is answered I am asked to enter my profile PIN, when I do this I successfully join the call and an event is sent with a correct uniqueUserId of 123 (see xml below)
.
<evt id="660c4849-fb80-4d72-8fef-c56b9632aa2d" subId="2bc49c40-4a44-45bc-86ee-645fd7de5138" evtType="USR_JOIN" time="2012-01-13T14:11:26.007Z" mtgUId="116" ani="35322412251" usrId="00099999999" usrUId="123" ability="SPEAKERPLUS" devId="2" partId="0" partName="JOE SMITH"/>

The code I used to programmatically generate the callback is: meetingService.outdialUser(116, "00099999999", "35322412251");

Thanks,
Enda

Hi Enda,

What version of MP are you using?

Thanks,
Adrienne

Hi Enda,

What version of MP are you using?

Thanks,
Adrienne

 
Hi Adrienne,
 
Version 8.5.2.8.
 
Thanks,
Enda

Hi Enda,

We have created defect CSCtx48756 for this issue. DE's are in the process of fixing this.

Thanks,
Adrienne

Hi Enda,

We have created defect CSCtx48756 for this issue. DE's are in the process of fixing this.

Thanks,
Adrienne

 
Many Thanks Adrienne, Is there a URL/Website where i can track the progress of this defect\patch?

Bug Toolkit:
http://www.cisco.com/cisco/psn/bssprt/bss