Our client want to restrict outgoing calls with some pin or password.
I suggested FAC (Force Authorization Code) but it won't fit as required because fac are defined on authorization level not to specific user. e.g. if one user know other's fac, he can use it on any phone to misuse it and in monthly bill genuine user will be in problem.
Is there any solution available in Call Manager 11.0 ?
There is no straight forward solution for this. FAC/CMC protection is implemented per route-pattern for all users matching the route pattern.
The only way I see it is to duplicate the route-pattern and assign each to separate PT/CSS. Then each user will have this own CSS to access the route-pattern. Now each route-pattern for each user will have separate FAC.
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out t...
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...
Parsec's Cisco UCCE/PCCE CC Connector application for CRM works as a bridge between the CRM and Cisco UCCE/PCCE CC solution.The CRM can be any cloud based CRM like Salesforce (SFDC), ServiceNow ,MS Dynamics or a 3rd party CRM.The CRM user/Agent will have ...
It’s a feature which allows CUCM to determine whether the phone is in its home location or a roaming station.By enabling this feature users can roam from one site to another site and acquire the site-specific settings such as Codecs, MRGL, Call rout...