Scott Lawrence wrote:
On Thu, 2010-03-11 at 17:44 +0530, Archana wrote:
Hi All,
Pre-condition:
Create a conference 'Conf' with extn 12345, and blank PIN
Assign a owner as '300' and enable auto-record
Steps:
1) Establish a conference between 2 users and verify that, the end
user UI of user 300 contains the recorded conference
2) Now login as a superadmin user and unassign '300' as conference
owner
3) Now drop a voice mail to user '300' from user 303
4) Navigate to end user UI of user 300, and move the inbox message to
conference page by using 'Move To' drop down menu.
Result:
User 300 can able to move the inbox message to conference page and
vice versa
Note :
1) This Issue occurs only when the user has accessed 'conference' page
at least once, by recording a conference call as a owner.
2) Also issue when I cleared the cache and verified with a different
browser
3) If the user never had recorded a conference then he can not move
the inbox message to conference page
Now my question is when the user '300' is unassigned as a owner, he is
same as a normal user other than the fact that he was a conference
owner once and recorded a conference call.
When the normal user can not be able to move his voice messages to
conference folder, why does the user '300' has an access?
I suspect that what's happening is that when you remove the ownership of
the conference from 300, in effect you're converting the conference
folder in the 300 user portal into just another mailbox folder.
Did you assign ownership of the conference to some other user, and if so
did subsequent calls get recorded in the correct folder under that user?
If I assign the ownership to another user then the conference calls get
recorded in the correct folder under that user.
I suppose in theory it would be good if when you move ownership from one
user to another, the recordings folder would move with the ownership...
I don't see it as a very big deal, though.
Yes, it would be nice if the user has been removed from the conference
ownership, then the recordings folder should not be accessible.
--
Regards,
Archana
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
