I'm not sure this will be possible. Any DN in the same partition will be a shared line and you cannot assign them two different calling search spaces.
I can't recall if with extension mobility the device calling search space changes, but that might be one option.
An alternative is if you have the CCM version with forward unregistered, you can forward the EM extension to another extension. That other extension can be the same extension in a different partition with different calling search space. The forwarding CSS of the EM extension will need to be able to dial that other partition.
I'm guessing this is a matter of convenience that if someone forgets to log in they still receive calls?
i think also the best workaround is to have 2 extensions (100 and 101)with same the partition (or None partition) if it does not matter having different extensions since one of them (101) is for receive only in case of employee does not log in...
but u have to forward unregistered to 101 if u have 4.2 or forward no coverage to 101 if u have 5.x with appropriate CSS with each.
1) CSSs - either use a 'device' CSS that permits all calling, then have a CSS assigned to the line on the device that blocks all calls (except for perhaps internal and emergency calls). You can then create the UDP with the same DN, but in another new partition.
2) Alternatively, set no CSS on the device. Set a CSS on the line assigned to the device that permits whatever you like. In the UDP, assign a CSS that permits whatever dialling the logged in user will have. Agian, you will need to create the UDP line in a seperate partition to the device line to allow different CSSs.
The final step in either of these cases is to ensure that the partition holding the UDP lines is higher in all CSSs than the partition containing lines on the logged out devices.
You will then need to set CFNA on the UDP line to a CSS that includes only the lines associated with logged out devices, and forward to it's own number.
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.