Any Reason code within 1-9 will go through successfully, but Event Reason code 10 will not reach AES. The CTI-link configuration is enabled with Two-digit Aux Work Reason code --Y. ( According to Avaya DOC )
This was proved by following call flow ( with Cisco ICM ).
Sniffer traces on PG, will show all the reason codes from 1 -- 9 but for the reason Code 10, Frame itself on sniffer is not identified.
I believe there is a registry setting on PG some thing like ( EnableTwoDigitEventReasonCode set 1 :-) ... but i am not sure. Simillar to EnableSevenDigitExtension under HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<cus01>\<PGXX>\PG\CurrentVersion\PIMS\pim1\ATTData\Config\
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.