Currently it has no other effect other than identifying that person as the owner of the handler/object in question on reports and the like. You can change it to another subscriber/public DL if you want.
this property is going to be used to determine who can fiddle with this handler/object over the phone at some point (i.e. allowing someone to call in and rerecord the opening greeting over the phone instead of having to call in via the SA). I believe this is planned for 3.1 but I'm not sure what the final feature cut will be.
Note, however, that you ALWAYS want to have both a valid owner and a valid message recipient for all handlers in the system. When we load the handler we go fetch both the owner and the recipient objects and if one or both of them are invalid (i.e. you toasted Mr. Example Administrator from the system) you will get sent to the fail safe conversation and we'll hang up on you. Not cool.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...