Paul Mossman wrote:
Sipxconfig associates the private phonebook with the user
behind the scene, so there is no need to add the user in any
group. The main reason for displaying private phonebooks in
admin portal was to give the possibility to remove them if
needed. Since this seems to be confusing we can hide private
phonebooks in admin portal (private phonebook gets deleted
when the user is deleted)
It would be good to show private phonebooks, but they should be given
special treatment. For example:
- Show that they are "private", beyond just the naming scheme.
- Have a hard-link to the owner, which would handle changing the user's
ID.
- Suppress the Member/Consumer user group selections.
So yes, for now I think it would be best to simply hide private
phonebooks from the admin portal.
After the private phone book is hidden, what if Admin wants to add few
more contacts(either through Gmail or csv) to that particular user for
whom the phone book existed.
Had the private phone book existed, the admin could have easily done
that using the users private phone book.
But now that if the phone book is hidden, the admin will not be able add
a few contacts only to a particular user.
Vani, I think there is a JIRA to be raised though....
- Admin portal: Create a user 200.
- 200's User portal: Import Gmail contacts, then logout.
- Admin portal: Change user 200 to 600, then create a new user 200.
- (the new) 200's User portal: Attempt to import Gmail contacts.
The last step should work, but it actually fails. (Probably because
there's already a "privatePhonebook_200" being used by user 600.)
-Paul
[email protected]
Issue raised http://track.sipfoundry.org/browse/XX-7442
Thanks,
Vani
_______________________________________________
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/
