I have five hundred 7942 phones all of the with extension mobility service bound and enabled. The five hundred phones are distributed among 5 different departments. I need to constrain extension mobility within each department to avoid users from one department to login into a phone from another department and make calls. Is there a way to achieve this requirement? My CUCM version is 9.1.
I was trying to avoid any of the two options you described.
The reason is billiing, each department is charged by phone, by extensión and also by call. I know it sound like crazy but it is what it is. The problem is that user from department -let say- A is able to log into a phone of department B then call is charged to B instead of A.
I tested disabling multiple logins, but this did not solve the problem.
How are you pulling the billing data? It should show user A's extension so the billing could be associated to the correct department that way. Does each department go out a different circuit or something?
You could put in a feature enhancement request through your account team to possibly have this feature added in a future release if you can make enough of a business case for it. It may still take a long time before it gets added to CUCM though.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.