When you define an ephone-dn (extension number instance) using the ephone-dn command, the Cisco CME system automatically creates a POTS dial peer with the ephone-dn endpoint as a destination. The default behavior is for the Cisco CME system to create a single POTS dial peer for each ephone-dn. If the dialplan-pattern command is set and matches against the ephone-dn number, two POTS dial peers are created, one for the local extension and one for the complete E.164 direct-dial telephone number. For example, an ephone-dn extension number is 1234, and the dial-plan pattern is "dialplan-pattern 1 4085551... extension-length 4." One POTS dial peer is created for "1234" and a second POTS dial peer is created for "4085551234." A third POTS dial peer is created if an ephone-dn secondary number is defined, and a fourth dial peer is created for this number if the secondary number also matches a dial-plan pattern. When the PSTN connects a DID call for "4085551234" to the Cisco CME system, it also forwards the extension digits "1234" to allow the system to route the call. Dial peers that are created by the ephone-dn command can be reviewed using the show telephony-service dial-peer command
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.