We seem to have an issue with call forwards at the moment.
Running CM version 4.1(3), the call forwards wont work unless we specify the calling search space on the call forward setting. Even though this will be the same calling search space thats currently applied to the phone.
Is this a known issue? Or just the way its designed to work? Surely the forwards could look up the CSS of the phone and route calls via that, without having to apply the CSS on the call forward setting itself.
Line CSS is not considered when doing a Call Forward. CSS has to be configured under Call Forward settings.
The secondary CSS for CFA combines with the current CSS for CFA in order to allow the support of the alternate CSS system configuration. When CFA is activated, only the primary and secondary CSS for CFA get used to validate the CFA destination and redirect the call to the CFA destination. If these fields are empty, the null CSS gets used.
The combination of the line CSS and device CSS no longer gets used when the CSS for CFA is None. Only the CSS fields that are configured in the primary CSS for CFA and secondary CSS for CFA fields get used. If CFA is activated from the phone, the CFA destination gets validated by the use of the CSS for CFA and the secondary CSS for CFA, and the CFA destination gets written to the database. When the CFA is activated, the CFA destination always gets validated against the CSS for CFA and the secondary CSS for CFA.
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.