[#DEV-3198] Attendees not able to join a meeting that is open. ROOMNAME not unique in portal db in production.

Dev

Attendees not able to join a meeting that is open. ROOMNAME not unique in portal db in production.

Created: 01/Jun/09 12:21 PM Updated: 29/Jul/09 06:00 AM

Component/s:

Operations

Affects Version/s:

None

Fix Version/s:

None

Component-Tag:

Portal

Description

« Hide

Please refer http://support.dimdim.com/browse/CARE-1530

The host starts the meeting with room name formadordigital.
Attendee tries to join the meeting and gets the 'Meeting room does not exist' error.

Rajesh has traced the cause to multiple rows in the portal database with the same ROOM_NAME but different USER_IDs.

Dimdim ID- formadordigital has ROOMNAME formadordigital and has the conference server pointing to promeeting. (which is correct)

Dimdim ID-elisavetsky@fibertel.com.ar also has ROOMNAME formadordigital and has the conference server pointing to freemeeting. causing the error.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Uday - 02/Jun/09 05:46 AM

This must have been done manually in the early days of portal - when users could have a different roomname.
e.g khaud01.dimdim has khaud01

I think the approach for this is to
1) find all these anomlaies - Select USER_ID from USERS WHERE USER_ID<>ROOM_NAME;
2) Modify them all so that the ROOM_NAME Is the same as the USER_ID

[ Permlink | « Hide ]

Subhash - 02/Jun/09 05:54 AM

Assigning to OPS

The following 3 USER_ID rows in the USERS table in portaldb were having rooname as formadordigital.

elisavetsky@fibertel.com.ar
elisavetsky
formadordigital

First 2 have been updated to have their ROOMNAME=Dimdim id