cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
828
Views
0
Helpful
1
Replies

Cisco Meeting Server api call question

owengerig
Level 1
Level 1

We have 2 CMS systems

Both are linked and syncing with AD however 1 of them doesnt auto generate co spaces

We manually assign these cospaces to users setting the ownerId and ownerJID fields

 

After this is done we retrieve the cospace and verify these 2 fields have the proper owner id and jid values.  

Later in the call flow we retreive UserCoSpaces (retrieves all co space id for user id)

		UserCoSpaces userCoSpaces = cmsClient.listAllObjects(UserCoSpaces.class, User.class, userId, null, null);

the problem is that this api call only seems to work on the auto generated cospaces.  It always returns null/empty for the cms which isnt auto generating.  any ideas as to why?

1 Accepted Solution

Accepted Solutions

owengerig
Level 1
Level 1

it is due to the autogeneration

 

whatever cisco is doing in the background when they generate users doesnt happen when you manually associate a user with a cospace (by setting the ownerid and ownerjid fields).  Auto generated cospaces dont even have ownerid and ownerjid fields populated so it must be some other field entirely and im not sure its exposed.

Whatever piece is missing here must be relied upon when making the call to list 

UserCoSpaces 

 

 

The main fix for this however was to save a coSpaceUser see api doc

6.4.2 Adding and modifying a coSpace member n Adding: POST method to a “/coSpaces//coSpaceUsers” node

 

After creating the coSpaceUser entry, then listing UserCoSpace will list that cospace id

View solution in original post

1 Reply 1

owengerig
Level 1
Level 1

it is due to the autogeneration

 

whatever cisco is doing in the background when they generate users doesnt happen when you manually associate a user with a cospace (by setting the ownerid and ownerjid fields).  Auto generated cospaces dont even have ownerid and ownerjid fields populated so it must be some other field entirely and im not sure its exposed.

Whatever piece is missing here must be relied upon when making the call to list 

UserCoSpaces 

 

 

The main fix for this however was to save a coSpaceUser see api doc

6.4.2 Adding and modifying a coSpace member n Adding: POST method to a “/coSpaces//coSpaceUsers” node

 

After creating the coSpaceUser entry, then listing UserCoSpace will list that cospace id

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: