Reference TAC case C207555. In trying to fix that problem, they had us change the IOS load on the router. As soon as we did that, it fixed the problem we were having, but it created a brand new problem. Now Unity is unable to transfer calls outside the office. Attempts to do so can be traced through the system (CDR is generated at the Call Manager v3.1.2(c)) and the debug logs on the router show the call attempt being made on the PRI span. The dial appears to be made (as the phone rings at the far end), but the caller ends up hearing dead air followed by a fast busy. The CDR shows a clearing code of 47 which according to the book means resource unavailable, unspecified. Don't get this as there are pleny of channels open and available. Doing a transfer from one of the phones (in the same call search space, etc) using the exact same dial string works perfectly. <br><br>I'm scratching my head as I don't understand why the change in the IOS load did this. Any help would be appreciated.<br><br>
Okay. I was just hoping maybe you guys might know what the issues where. Unity transfers worked fine with 12.2.4T, but that one was having massive failures due to something they called TDM Hairpinning (whatever that is).
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.