Our institution has been slowly migrating from Avaya to CUCM. One of the many features that our users are reluctant to loosing is being able to forward and unforward remote phones. That is, we have 15 users that can forward and unforward any DN from their own station. On Avaya this is done via feature access codes. I inquired about a similar feature on CUCM to TAC and they told me that it does not exist. The manager of those users does not want them to have access to CUCM admin page even if they only had limited permissions. I then thought that if there is a way that UCCX can write to the CUCM database I can write a script that will collect an Extension from the caller and a forwarding number. Is this possible? If so, what do I need to set up to be able to be able to modify the ForwardAll of any DN on CUCM from UCCX?
In my view if you do it from CUCM web portal via an end user ( asssociate all 15 phones to one ). This way only one user login can make changes which can be shared with all.
It will make it alot easier to manage then creating another script etc.Also when migrating from avaya there are few features that they will loose however gains are much higher so they will have to live with it.
The thing is that those users do not only privileges to forward a single phone, but every single phone on the system.
I do share your opinion that they do have to get used to the new features. The only issue is that if the users do not get this feature it means that we will be on-call 24/7 just to forward phones. lol.
If they're going to have jabber, they can look into MRA and they can adjust the forward settings that way.
In my opinion, this gets to the heart of the differences in security models between Avaya UC and Cisco UC. Why should a user be able to adjust the CFwdAll setting of any DN in the system without having some sort of right or ownership to do so?
Reading your last reply, I'm curious why someone would need to be on call 24/7 to forward phones? I realize this extends the conversation into the organization's business process which you may not be able to reveal. However, if perhaps you can provide some context around why any DN may need CFwdALL at any random time, we may be able to help you address the issue through different methods.
(.. Please rate helpful posts ..)
Thank you for responding Ryan. Your questions are crucial to finding the right solution for our dilemma.
Why should a user be able to adjust the CFwdAll setting of any DN in the system without having some sort of right or ownership to do so?
The users that will have right to do this are the Phone Operators for the entire institution. They are under the same manager as Telecomm. There are operators for all 3 shifts. Our entire institution is used to calling the operators to forward their phones or remove forwarding in case that they forgot to do so.
Reading your last reply, I'm curious why someone would need to be on call 24/7 to forward phones?
If the Operators do not have the capability to forward or unForward the DN, the only people that would be able to do so would be CUCM admins (3 of us). Anytime a person forgot to CFwALL their DN because their calls need to be routed elsewhere for the night or weekend they would need to page the person on call so that they do not have to drive back and forward their phones. We typically do not grant end users access to the Self Care portal.
I think your solution may be found in a variety of ways, up to and including some process changes for end users. When you make such a significant platform change, some end user change is just unavoidable.
Here are four ways that I feel could be of benefit to your scenario.
For single user lines
For group / department lines
(.. Please rate helpful posts ..)