[cisco-voip] Using Unity Greetings Administrator question...

[Tim Reimers]

yeah, I think that's what I've done---
 
made them the admins... don't recall the button config...
 
I know I did that for the guy who does our 'school open/closed/delay'
messages.. Lelio was a HUGE help on that  (go Lelio!)
 
I did seem to recall that there's no way to give programmatic control of
the buttons...
 
T

________________________________

From: Voll, Scott [mailto:Scott.Voll at wesd.org] 
Sent: Tuesday, August 01, 2006 10:34 AM
To: Tim Reimers; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Using Unity Greetings Administrator
question...



Tim-

 

You just need to make them the owner of the CH.  Then as a button
push... I use 9 they get the greetings administrator.  They enter the CH
extension and there user ID / Pin then they can change all the
greetings.  You can also add a distribution list and everyone in the
Distribution list can change the greetings for the CH.  They would not
have button config options to my knowledge.  I think you're still going
to have to do the button thing for them.

 

Scott

 

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Reimers
Sent: Tuesday, August 01, 2006 7:12 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Using Unity Greetings Administrator question...

 

 

hey-- 

I seem to recall that there is a way to set up Greetings Administrator 
to allow people to change the recorded greeting on a Call Handler
they're given control of--- 

Is there documentation on how that should be set up and how it works for
end users? 

And --- 
what about the administration of the button config? 
I don't really want users having admin access to Unity--- 
I'd love it if they could only see their own button selections, or
change them from the phone as well as re-record the greeting??

Tim 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060801/f5d36cae/attachment.html