Shivinder Singh | Anil/Akanksha, I’m having difficulty understanding the roles – specifically Mailbox Access Delegate - and their intended use/audience. From your response it seems I’m not making sense in the Cisco universe. I’ll try to explain little better:
I’m developing some very basic reports for call records (called/received/unanswered/unreturned etc. etc.). I’m aware there are 3rd party software that do that but for sake of simplicity let’s assume they don’t exist. The reporting app will use a service account to get the job done. And will need certain permissions/roles.
Please help me out here understand the roles here:
1. /vmrest/mailbox (CUMI) can return voicemail records of *anyone*, if, ALL THREE of the following are true:
a) Service account is created using voicemailusertemplate template
b) Mailbox Access Delegate role is assigned to the service account
c) User Object Id is provided
2. /vmrest/users (CUNI) can return User Object Id of *anyone*, if, following is true:
a) System Administrator role is assigned to the service account
So at the end of the day – the service account needs to have mailbox delegate role as well as sysdamin role. Why in the world would I want to give a little service account, whose job is to give me voicemail records (just an extension of CDR call log), the *All Powerful* System Administrator Role? The account does not need to LISTEN to voice messages (which I’d assume will require some God role). All it needs is called party, calling party and time received.
Please understand I’m a programmer and need to convince my CUCM sysadmin to give my little service account this role, so I’d appreciate some insight as to why Cisco chose to design roles in this manner? I’m definitely missing some point ☺ Thanks for your continued responses! |
| Please sign in to flag this as inappropriate. |