Is this Unity system dual-swith by any chance? Was it ever? The MM will try to dial-out on a port that has the same switch ID as the Unity account your logged on with (not necessarily the person's page you're on).
So if you are logged in as Eadmin (that for whatever reason is assigned to switch 0) and you're trying to do a MM record for TestUser1 (that's assigned to switch 1), Unity is going to try to dial out with a port that belongs to switch 0.
I see this a lot with systems that were dual switch at one point and are not now.
The trick is if you're logging into the SA with an account mapped via the GrantUnityAccess tool, you're most likely coming in "as" the install account which is hidden in the SA so you can't change it's switch ID to match properly as Steve was mentioning.
The latest version of dbWalker out on www.CiscoUnityTools.com (aka AnswerMonkey.net) will help by reassigning invalid switch IDs to "0" if necessary... this often helps with systems that were originally configured for dual switch (many times not deliberately) and then converted to single switch integrations later.
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.